This is python.info, produced by makeinfo version 7.1 from python.texi.

     Python 3.13.0rc2, 9月 18, 2024

     Author name not set

     Copyright © 2001-2024, Python Software Foundation

INFO-DIR-SECTION Miscellaneous
START-INFO-DIR-ENTRY
* python: (python.info). One line description of project
END-INFO-DIR-ENTRY


   Generated by Sphinx 8.0.2.


File: python.info,  Node: Top,  Next: Python 有什麼新功能？,  Up: (dir)

Python
******

     Python 3.13.0rc2, 9月 18, 2024

     Author name not set

     Copyright © 2001-2024, Python Software Foundation

* Menu:

* Python 有什麼新功能？::
* Python 教學::
* Python 的設置與使用::
* Python 語言參考手冊::
* Python 標準函式庫 (Standard Library): Python 標準函式庫 Standard Library.
* 擴充和嵌入 Python 直譯器::
* Python/C API 參考手冊::
* 安裝 Python 模組::
* Python 如何達成任務::
* Python 常見問題::
* 已棄用項目::
* 術語表::
* 關於這些說明文件::
* 處理錯誤 (Bug): 處理錯誤 Bug.
* 版權宣告::
* 沿革與授權::
* Python 模組索引::
* 索引::

 -- The Detailed Node Listing --

Python 有什麼新功能？

* What's New In Python 3.13: What's New In Python 3 13.
* Python 3.12 有什麼新功能: Python 3 12 有什麼新功能.
* Python 3.11 有什麼新功能: Python 3 11 有什麼新功能.
* Python 3.10 有什麼新功能: Python 3 10 有什麼新功能.
* Python 3.9 有什麼新功能: Python 3 9 有什麼新功能.
* Python 3.8 有什麼新功能: Python 3 8 有什麼新功能.
* Python 3.7 有什麼新功能: Python 3 7 有什麼新功能.
* Python 3.6 有什麼新功能: Python 3 6 有什麼新功能.
* Python 3.4 有什麼新功能: Python 3 4 有什麼新功能.
* Python 3.4 有什麼新功能: Python 3 4 有什麼新功能<2>.
* Python 3.3 有什麼新功能: Python 3 3 有什麼新功能.
* Python 3.2 有什麼新功能: Python 3 2 有什麼新功能.
* Python 3.1 有什麼新功能: Python 3 1 有什麼新功能.
* Python 3.0 有什麼新功能: Python 3 0 有什麼新功能.
* Python 2.7 有什麼新功能: Python 2 7 有什麼新功能.
* Python 2.6 有什麼新功能: Python 2 6 有什麼新功能.
* Python 2.5 有什麼新功能: Python 2 5 有什麼新功能.
* Python 2.4 有什麼新功能: Python 2 4 有什麼新功能.
* Python 2.3 有什麼新功能: Python 2 3 有什麼新功能.
* Python 2.2 有什麼新功能: Python 2 2 有什麼新功能.
* Python 2.1 有什麼新功能: Python 2 1 有什麼新功能.
* Python 2.0 有什麼新功能: Python 2 0 有什麼新功能.
* Changelog（更動日誌）::

What's New In Python 3.13

* Summary: Summary -- Release Highlights. Release Highlights
* New Features::
* Other Language Changes::
* New Modules::
* Improved Modules::
* Optimizations::
* Removed Modules And APIs::
* New Deprecations::
* CPython Bytecode Changes::
* C API Changes::
* Build Changes::
* Porting to Python 3.13: Porting to Python 3 13.
* Regression Test Changes::

New Features

* A better interactive interpreter::
* Improved error messages::
* Free-threaded CPython::
* An experimental just-in-time (JIT) compiler: An experimental just-in-time JIT compiler.
* Defined mutation semantics for locals(): Defined mutation semantics for locals.
* Support for mobile platforms::
* Incremental garbage collection::

Improved Modules

* argparse::
* array::
* ast::
* asyncio::
* base64::
* compileall::
* configparser::
* concurrent.futures: concurrent futures.
* configparser: configparser<2>.
* copy::
* dbm::
* dis::
* doctest::
* email::
* fractions::
* gc::
* glob::
* importlib::
* io::
* ipaddress::
* itertools::
* marshal::
* math::
* mimetypes::
* mmap::
* multiprocessing::
* os::
* os.path: os path.
* pathlib::
* pdb::
* queue::
* random::
* re::
* shutil::
* site::
* sqlite3::
* ssl::
* statistics::
* subprocess::
* sys::
* tempfile::
* time::
* tkinter::
* traceback::
* types::
* typing::
* unicodedata::
* venv::
* warnings::
* xml::
* zipimport::

Removed Modules And APIs

* PEP 594; Remove "dead batteries" from the standard library: PEP 594 Remove "dead batteries" from the standard library.
* 2to3::
* builtins::
* configparser: configparser<3>.
* importlib.metadata: importlib metadata.
* locale::
* opcode::
* pathlib: pathlib<2>.
* re: re<2>.
* tkinter.tix: tkinter tix.
* turtle::
* typing: typing<2>.
* unittest::
* urllib::
* webbrowser::

New Deprecations

* Pending Removal in Python 3.14: Pending Removal in Python 3 14.
* Pending Removal in Python 3.15: Pending Removal in Python 3 15.
* Pending Removal in Python 3.16: Pending Removal in Python 3 16.
* Pending Removal in Future Versions::

C API Changes

* New Features: New Features<2>.

Porting to Python 3.13

* Changes in the Python API::
* Changes in the C API::
* Removed C APIs::
* Deprecated C APIs::

Deprecated C APIs

* Pending Removal in Python 3.14: Pending Removal in Python 3 14<2>.
* Pending Removal in Python 3.15: Pending Removal in Python 3 15<2>.
* Pending Removal in Future Versions: Pending Removal in Future Versions<2>.

Python 3.12 有什麼新功能

* 發布重點摘要::
* 新增特性::
* New Features Related to Type Hints::
* 其他語言更動::
* 新增模組::
* 改進的模組::
* 最佳化::
* CPython 位元組碼變更::
* Demos and Tools::
* 已棄用::
* 已移除::
* Porting to Python 3.12: Porting to Python 3 12.
* 建置變更::
* C API 變更::

新增特性

* PEP 695：型別參數語法::
* PEP 701; Syntactic formalization of f-strings: PEP 701 Syntactic formalization of f-strings.
* PEP 684; A Per-Interpreter GIL: PEP 684 A Per-Interpreter GIL.
* PEP 669; Low impact monitoring for CPython: PEP 669 Low impact monitoring for CPython.
* PEP 688; Making the buffer protocol accessible in Python: PEP 688 Making the buffer protocol accessible in Python.
* PEP 709; Comprehension inlining: PEP 709 Comprehension inlining.
* Improved Error Messages::

New Features Related to Type Hints

* PEP 692; Using TypedDict for more precise **kwargs typing: PEP 692 Using TypedDict for more precise **kwargs typing.
* PEP 698; Override Decorator for Static Typing: PEP 698 Override Decorator for Static Typing.

改進的模組

* array: array<2>.
* asyncio: asyncio<2>.
* calendar::
* csv::
* dis: dis<2>.
* fractions: fractions<2>.
* importlib.resources: importlib resources.
* inspect::
* itertools: itertools<2>.
* math: math<2>.
* os: os<2>.
* os.path: os path<2>.
* pathlib: pathlib<3>.
* pdb: pdb<2>.
* random: random<2>.
* shutil: shutil<2>.
* sqlite3: sqlite3<2>.
* statistics: statistics<2>.
* sys: sys<2>.
* tempfile: tempfile<2>.
* threading::
* tkinter: tkinter<2>.
* tokenize::
* types: types<2>.
* typing: typing<3>.
* unicodedata: unicodedata<2>.
* unittest: unittest<2>.
* uuid::

已棄用

* Python 3.13 中待移除的項目: Python 3 13 中待移除的項目.
* Python 3.14 中待移除的項目: Python 3 14 中待移除的項目.
* Python 3.15 中待移除的項目: Python 3 15 中待移除的項目.
* Python 3.16 中待移除的項目: Python 3 16 中待移除的項目.
* 未來版本中的待移除項目::

已移除

* asynchat 和 asyncore::
* configparser: configparser<4>.
* distutils::
* ensurepip::
* enum::
* ftplib::
* gzip::
* hashlib::
* importlib: importlib<2>.
* imp::
* io: io<2>.
* locale: locale<2>.
* smtpd::
* sqlite3: sqlite3<3>.
* ssl: ssl<2>.
* unittest: unittest<3>.
* webbrowser: webbrowser<2>.
* xml.etree.ElementTree: xml etree ElementTree.
* zipimport: zipimport<2>.
* 其他::

Porting to Python 3.12

* Python API 的變更::

C API 變更

* 新增特性: 新增特性<2>.
* Porting to Python 3.12: Porting to Python 3 12<2>.
* 已棄用: 已棄用<2>.
* 已移除: 已移除<2>.

已棄用

* Python 3.14 中待移除的項目: Python 3 14 中待移除的項目<2>.
* Python 3.15 中待移除的項目: Python 3 15 中待移除的項目<2>.
* 未來版本中的待移除項目: 未來版本中的待移除項目<2>.

Python 3.11 有什麼新功能

* 發布重點摘要: 發布重點摘要<2>.
* 新增特性: 新增特性<3>.
* 型別提示相關的新特性::
* 其他語言更動: 其他語言更動<2>.
* 其他 CPython 實作更動::
* 新增模組: 新增模組<2>.
* 改進的模組: 改進的模組<2>.
* 最佳化: 最佳化<2>.
* 更快的 CPython::
* CPython 位元組碼變更: CPython 位元組碼變更<2>.
* 已棄用: 已棄用<3>.
* Python 3.12 中待決議的移除項目: Python 3 12 中待決議的移除項目.
* 已移除: 已移除<3>.
* 移植至 Python 3.11: 移植至 Python 3 11.
* 建置變更: 建置變更<2>.
* C API 變更: C API 變更<2>.
* Notable changes in 3.11.4: Notable changes in 3 11 4.
* Notable changes in 3.11.5: Notable changes in 3 11 5.

新增特性

* PEP 657：回溯 (traceback) 中更細緻的錯誤位置: PEP 657：回溯 traceback 中更細緻的錯誤位置.
* PEP 654：例外群組與 except*::
* PEP 678：運用例外註解使其更加詳盡::
* Windows py.exe 啟動程式 (launcher) 的改進: Windows py exe 啟動程式 launcher 的改進.

型別提示相關的新特性

* PEP 646：可變參數泛型 (variadic generics): PEP 646：可變參數泛型 variadic generics.
* PEP 655：標記獨立 TypedDict 項目為必要或不必要::
* PEP 673：Self 型別::
* PEP 675：任意的文本字串型別 (Arbitrary literal string type): PEP 675：任意的文本字串型別 Arbitrary literal string type.
* PEP 681：資料類別轉換 (Data class transforms): PEP 681：資料類別轉換 Data class transforms.
* PEP 563 可能不是未來::

改進的模組

* asyncio: asyncio<3>.
* contextlib::
* dataclasses::
* datetime::
* enum: enum<2>.
* fcntl::
* fractions: fractions<3>.
* functools::
* gzip: gzip<2>.
* hashlib: hashlib<2>.
* IDLE 與 idlelib::
* inspect: inspect<2>.
* locale: locale<3>.
* logging::
* math: math<3>.
* operator::
* os: os<3>.
* pathlib: pathlib<4>.
* re: re<3>.
* shutil: shutil<3>.
* socket::
* sqlite3: sqlite3<4>.
* string::
* sys: sys<3>.
* sysconfig::
* tempfile: tempfile<3>.
* threading: threading<2>.
* time: time<2>.
* tkinter: tkinter<3>.
* traceback: traceback<2>.
* typing: typing<4>.
* unicodedata: unicodedata<3>.
* unittest: unittest<4>.
* venv: venv<2>.
* warnings: warnings<2>.
* zipfile::

更快的 CPython

* 更快的啟動::
* 更快的運行程式::
* 雜項::
* FAQ::
* 關於::

更快的啟動

* 凍結引入 (Frozen imports) / 靜態程式碼物件 (Static code objects): 凍結引入 Frozen imports / 靜態程式碼物件 Static code objects.

更快的運行程式

* 所需資源更少 (cheaper) 且惰性的 (lazy)) Python 幀 (frame): 所需資源更少 cheaper 且惰性的 lazy Python 幀 frame.
* 行內 Python 函式呼叫::
* PEP 659：特化的適應性直譯器::

FAQ

* 我該如何在程式碼中獲取這些加速？::
* Python 3.11 會不會使用更多記憶體？: Python 3 11 會不會使用更多記憶體？.
* 我在我的程式當中沒感覺到任何加速，為什麼？::
* 有用到 JIT 編譯器嗎？::

CPython 位元組碼變更

* 新增 opcode::
* 被取代的操作碼 (opcode): 被取代的操作碼 opcode.
* 有更動/被移除的 opcode::

已棄用

* 語言/內建::
* 模組::
* 標準函式庫::

C API 變更

* 新增特性: 新增特性<4>.
* 移植至 Python 3.11: 移植至 Python 3 11<2>.
* 已棄用: 已棄用<4>.
* Python 3.12 中待決議的移除項目: Python 3 12 中待決議的移除項目<2>.
* 已移除: 已移除<4>.

Notable changes in 3.11.4

* tarfile::

Notable changes in 3.11.5

* OpenSSL::

Python 3.10 有什麼新功能

* 摘要: 摘要 -- 發布重點. 發布重點
* 新功能::
* 與型別提示相關的新功能::
* 其他語言更動: 其他語言更動<3>.
* 新模組::
* 改進的模組: 改進的模組<3>.
* 最佳化: 最佳化<3>.
* 已棄用: 已棄用<5>.
* 已刪除::
* 移植到 Python 3.10: 移植到 Python 3 10.
* CPython 位元組碼變更: CPython 位元組碼變更<3>.
* 建置變更: 建置變更<3>.
* C API 變更: C API 變更<3>.
* Notable security feature in 3.10.7: Notable security feature in 3 10 7.
* Notable security feature in 3.10.8: Notable security feature in 3 10 8.
* Notable changes in 3.10.12: Notable changes in 3 10 12.

新功能

* 帶括號的情境管理器::
* 更好的錯誤訊息::
* PEP 626：用於除錯和其他工具的精確列號::
* PEP 634：結構模式匹配::
* 可選的 EncodingWarning 和 encoding="locale" 選項::

更好的錯誤訊息

* SyntaxErrors::
* IndentationErrors::
* AttributeErrors::
* NameErrors::

PEP 634：結構模式匹配

* 語法和操作::
* 宣告式方法 (Declarative approach): 宣告式方法 Declarative approach.
* 簡單模式：與字面值匹配::
* 具有字面值和變數的模式::
* 模式和類別::
* 巢狀模式::
* 複雜模式和萬用字元::
* Guard::
* 其他主要功能::

簡單模式：與字面值匹配

* 沒有萬用字元 (wildcard) 的行為: 沒有萬用字元 wildcard 的行為.

模式和類別

* 具有位置參數的模式::

與型別提示相關的新功能

* PEP 604：新型聯集運算子::
* PEP 612：參數規範變數::
* PEP 613：型別別名 (TypeAlias): PEP 613：型別別名 TypeAlias.
* PEP 647：使用者定義的型別防護::

改進的模組

* asyncio: asyncio<4>.
* argparse: argparse<2>.
* array: array<3>.
* asynchat, asyncore, smtpd: asynchat asyncore smtpd.
* base64: base64<2>.
* bdb::
* bisect::
* codecs::
* collections.abc: collections abc.
* contextlib: contextlib<2>.
* curses::
* dataclasses: dataclasses<2>.
* distutils: distutils<2>.
* doctest: doctest<2>.
* encodings::
* enum: enum<3>.
* fileinput::
* faulthandler::
* gc: gc<2>.
* glob: glob<2>.
* hashlib: hashlib<3>.
* hmac::
* IDLE 和 idlelib::
* importlib.metadata: importlib metadata<2>.
* inspect: inspect<3>.
* itertools: itertools<3>.
* linecache::
* os: os<4>.
* os.path: os path<3>.
* pathlib: pathlib<5>.
* platform::
* pprint::
* py_compile::
* pyclbr::
* shelve::
* statistics: statistics<3>.
* site: site<2>.
* socket: socket<2>.
* ssl: ssl<3>.
* sqlite3: sqlite3<5>.
* sys: sys<4>.
* _thread::
* threading: threading<3>.
* traceback: traceback<3>.
* types: types<3>.
* typing: typing<5>.
* unittest: unittest<5>.
* urllib.parse: urllib parse.
* xml: xml<2>.
* zipimport: zipimport<3>.

dataclasses

* __slots__::
* 僅限關鍵字欄位 (Keyword-only fields): 僅限關鍵字欄位 Keyword-only fields.

移植到 Python 3.10

* Python 語法的變化::
* Python API 的變化::
* C API 中的改動::

C API 變更

* PEP 652：維護穩定 ABI::
* 新功能: 新功能<2>.
* 移植到 Python 3.10: 移植到 Python 3 10<2>.
* 已棄用: 已棄用<6>.
* 已刪除: 已刪除<2>.

Notable changes in 3.10.12

* tarfile: tarfile<2>.

Python 3.9 有什麼新功能

* Summary: Summary -- Release highlights. Release highlights
* You should check for DeprecationWarning in your code::
* New Features: New Features<3>.
* 其他語言更動: 其他語言更動<4>.
* 新模組: 新模組<2>.
* 改進的模組: 改進的模組<4>.
* 最佳化: 最佳化<4>.
* 已棄用: 已棄用<7>.
* 已移除: 已移除<5>.
* Porting to Python 3.9: Porting to Python 3 9.
* 建置變更: 建置變更<4>.
* C API 變更: C API 變更<4>.
* Python 3.9.1 中顯著的變更: Python 3 9 1 中顯著的變更.
* Python 3.9.2 中顯著的變更: Python 3 9 2 中顯著的變更.
* Python 3.9.3 中顯著的變更: Python 3 9 3 中顯著的變更.
* Python 3.9.5 中顯著的變更: Python 3 9 5 中顯著的變更.
* Notable security feature in 3.9.14: Notable security feature in 3 9 14.
* Notable changes in 3.9.17: Notable changes in 3 9 17.

New Features

* Dictionary Merge & Update Operators::
* New String Methods to Remove Prefixes and Suffixes::
* Type Hinting Generics in Standard Collections::
* New Parser::

新模組

* zoneinfo::
* graphlib::

改進的模組

* ast: ast<2>.
* asyncio: asyncio<5>.
* compileall: compileall<2>.
* concurrent.futures: concurrent futures<2>.
* curses: curses<2>.
* datetime: datetime<2>.
* distutils: distutils<3>.
* fcntl: fcntl<2>.
* ftplib: ftplib<2>.
* gc: gc<3>.
* hashlib: hashlib<4>.
* http::
* IDLE and idlelib::
* imaplib::
* importlib: importlib<3>.
* inspect: inspect<4>.
* ipaddress: ipaddress<2>.
* math: math<4>.
* multiprocessing: multiprocessing<2>.
* nntplib::
* os: os<5>.
* pathlib: pathlib<6>.
* pdb: pdb<3>.
* poplib::
* pprint: pprint<2>.
* pydoc::
* random: random<3>.
* signal::
* smtplib::
* socket: socket<3>.
* time: time<3>.
* sys: sys<5>.
* tracemalloc::
* typing: typing<6>.
* unicodedata: unicodedata<4>.
* venv: venv<3>.
* xml: xml<3>.

Porting to Python 3.9

* Changes in the Python API: Changes in the Python API<2>.
* C API 中的改動: C API 中的改動<2>.
* CPython 位元組碼變更: CPython 位元組碼變更<4>.

C API 變更

* New Features: New Features<4>.
* Porting to Python 3.9: Porting to Python 3 9<2>.
* 已移除: 已移除<6>.

Python 3.9.1 中顯著的變更

* typing: typing<7>.
* macOS 11.0 (Big Sur) and Apple Silicon Mac support: macOS 11 0 Big Sur and Apple Silicon Mac support.

Python 3.9.2 中顯著的變更

* collections.abc: collections abc<2>.
* urllib.parse: urllib parse<2>.

Python 3.9.5 中顯著的變更

* urllib.parse: urllib parse<3>.

Notable changes in 3.9.17

* tarfile: tarfile<3>.

Python 3.8 有什麼新功能

* Summary: Summary -- Release highlights<2>. Release highlights
* New Features: New Features<5>.
* 其他語言更動: 其他語言更動<5>.
* 新增模組: 新增模組<3>.
* 改進的模組: 改進的模組<5>.
* 最佳化: 最佳化<5>.
* Build and C API Changes::
* 已棄用: 已棄用<8>.
* API and Feature Removals::
* Porting to Python 3.8: Porting to Python 3 8.
* Python 3.8.1 中顯著的變更: Python 3 8 1 中顯著的變更.
* Python 3.8.2 中顯著的變更: Python 3 8 2 中顯著的變更.
* Python 3.8.3 中顯著的變更: Python 3 8 3 中顯著的變更.
* Python 3.8.8 中顯著的變更: Python 3 8 8 中顯著的變更.
* Python 3.8.9 中顯著的變更: Python 3 8 9 中顯著的變更.
* Python 3.8.10 中顯著的變更: Python 3 8 10 中顯著的變更.
* Python 3.8.10 中顯著的變更: Python 3 8 10 中顯著的變更<2>.
* Python 3.8.12 中顯著的變更: Python 3 8 12 中顯著的變更.
* Notable security feature in 3.8.14: Notable security feature in 3 8 14.
* Notable changes in 3.8.17: Notable changes in 3 8 17.

New Features

* Assignment expressions::
* Positional-only parameters::
* Parallel filesystem cache for compiled bytecode files::
* Debug build uses the same ABI as release build::
* f-strings support = for self-documenting expressions and debugging::
* PEP 578; Python Runtime Audit Hooks: PEP 578 Python Runtime Audit Hooks.
* PEP 587; Python Initialization Configuration: PEP 587 Python Initialization Configuration.
* PEP 590; Vectorcall; a fast calling protocol for CPython: PEP 590 Vectorcall a fast calling protocol for CPython.
* Pickle protocol 5 with out-of-band data buffers::

改進的模組

* ast: ast<3>.
* asyncio: asyncio<6>.
* builtins（內建）::
* collections::
* cProfile::
* csv: csv<2>.
* curses: curses<3>.
* ctypes::
* datetime: datetime<3>.
* functools: functools<2>.
* gc: gc<4>.
* gettext::
* gzip: gzip<3>.
* IDLE and idlelib: IDLE and idlelib<2>.
* inspect: inspect<5>.
* io: io<3>.
* itertools: itertools<4>.
* json.tool: json tool.
* logging: logging<2>.
* math: math<5>.
* mmap: mmap<2>.
* multiprocessing: multiprocessing<3>.
* os: os<6>.
* os.path: os path<4>.
* pathlib: pathlib<7>.
* pickle::
* plistlib::
* pprint: pprint<3>.
* py_compile: py_compile<2>.
* shlex::
* shutil: shutil<4>.
* socket: socket<4>.
* ssl: ssl<4>.
* statistics: statistics<4>.
* sys: sys<6>.
* tarfile: tarfile<4>.
* threading: threading<4>.
* tokenize: tokenize<2>.
* tkinter: tkinter<4>.
* time: time<4>.
* typing: typing<8>.
* unicodedata: unicodedata<5>.
* unittest: unittest<6>.
* venv: venv<4>.
* weakref::
* xml: xml<4>.
* xmlrpc::

Porting to Python 3.8

* Changes in Python behavior::
* Changes in the Python API: Changes in the Python API<3>.
* C API 中的改動: C API 中的改動<3>.
* CPython 位元組碼變更: CPython 位元組碼變更<5>.
* Demos and Tools: Demos and Tools<2>.

Python 3.8.10 中顯著的變更

* macOS 11.0 (Big Sur) and Apple Silicon Mac support: macOS 11 0 Big Sur and Apple Silicon Mac support<2>.

Python 3.8.10 中顯著的變更

* urllib.parse: urllib parse<4>.

Python 3.8.12 中顯著的變更

* Changes in the Python API: Changes in the Python API<4>.

Notable changes in 3.8.17

* tarfile: tarfile<5>.

Python 3.7 有什麼新功能

* Summary: Summary -- Release Highlights<2>. Release Highlights
* New Features: New Features<6>.
* 其他語言更動: 其他語言更動<6>.
* 新模組: 新模組<3>.
* 改進的模組: 改進的模組<6>.
* C API 變更: C API 變更<5>.
* 建置變更: 建置變更<5>.
* 最佳化: 最佳化<6>.
* Other CPython Implementation Changes::
* Deprecated Python Behavior::
* Deprecated Python modules, functions and methods: Deprecated Python modules functions and methods.
* Deprecated functions and types of the C API::
* Platform Support Removals::
* API and Feature Removals: API and Feature Removals<2>.
* Module Removals::
* Windows-only Changes::
* Porting to Python 3.7: Porting to Python 3 7.
* Python 3.7.1 中顯著的變更: Python 3 7 1 中顯著的變更.
* Python 3.7.2 中顯著的變更: Python 3 7 2 中顯著的變更.
* Python 3.7.6 中顯著的變更: Python 3 7 6 中顯著的變更.
* Python 3.7.10 中顯著的變更: Python 3 7 10 中顯著的變更.
* Python 3.7.11 中顯著的變更: Python 3 7 11 中顯著的變更.
* Notable security feature in 3.7.14: Notable security feature in 3 7 14.

New Features

* PEP 563; Postponed Evaluation of Annotations: PEP 563 Postponed Evaluation of Annotations.
* PEP 538; Legacy C Locale Coercion: PEP 538 Legacy C Locale Coercion.
* PEP 540; Forced UTF-8 Runtime Mode: PEP 540 Forced UTF-8 Runtime Mode.
* PEP 553; Built-in breakpoint(): PEP 553 Built-in breakpoint.
* PEP 539; New C API for Thread-Local Storage: PEP 539 New C API for Thread-Local Storage.
* PEP 562; Customization of Access to Module Attributes: PEP 562 Customization of Access to Module Attributes.
* PEP 564; New Time Functions With Nanosecond Resolution: PEP 564 New Time Functions With Nanosecond Resolution.
* PEP 565; Show DeprecationWarning in __main__: PEP 565 Show DeprecationWarning in __main__.
* PEP 560; Core Support for typing module and Generic Types: PEP 560 Core Support for typing module and Generic Types.
* PEP 552; Hash-based .pyc Files: PEP 552 Hash-based pyc Files.
* PEP 545：Python 文件翻譯::
* Python Development Mode (-X dev): Python Development Mode -X dev.

新模組

* contextvars::
* dataclasses: dataclasses<3>.
* importlib.resources: importlib resources<2>.

改進的模組

* argparse: argparse<3>.
* asyncio: asyncio<7>.
* binascii::
* calendar: calendar<2>.
* collections: collections<2>.
* compileall: compileall<3>.
* concurrent.futures: concurrent futures<3>.
* contextlib: contextlib<3>.
* cProfile: cProfile<2>.
* crypt::
* datetime: datetime<4>.
* dbm: dbm<2>.
* decimal::
* dis: dis<3>.
* distutils: distutils<4>.
* enum: enum<4>.
* functools: functools<3>.
* gc: gc<5>.
* hmac: hmac<2>.
* http.client: http client.
* http.server: http server.
* idlelib and IDLE::
* importlib: importlib<4>.
* io: io<4>.
* ipaddress: ipaddress<3>.
* itertools: itertools<5>.
* locale: locale<4>.
* logging: logging<3>.
* math: math<6>.
* mimetypes: mimetypes<2>.
* msilib::
* multiprocessing: multiprocessing<4>.
* os: os<7>.
* pathlib: pathlib<8>.
* pdb: pdb<4>.
* py_compile: py_compile<3>.
* pydoc: pydoc<2>.
* queue: queue<2>.
* re: re<4>.
* signal: signal<2>.
* socket: socket<5>.
* socketserver::
* sqlite3: sqlite3<6>.
* ssl: ssl<5>.
* string: string<2>.
* subprocess: subprocess<2>.
* sys: sys<7>.
* time: time<5>.
* tkinter: tkinter<5>.
* tracemalloc: tracemalloc<2>.
* types: types<4>.
* unicodedata: unicodedata<6>.
* unittest: unittest<7>.
* unittest.mock: unittest mock.
* urllib.parse: urllib parse<5>.
* uu::
* uuid: uuid<2>.
* warnings: warnings<3>.
* xml: xml<5>.
* xml.etree: xml etree.
* xmlrpc.server: xmlrpc server.
* zipapp::
* zipfile: zipfile<2>.

Deprecated Python modules, functions and methods

* aifc::
* asyncio: asyncio<8>.
* collections: collections<3>.
* dbm: dbm<3>.
* enum: enum<5>.
* gettext: gettext<2>.
* importlib: importlib<5>.
* locale: locale<5>.
* macpath::
* threading: threading<5>.
* socket: socket<6>.
* ssl: ssl<6>.
* sunau::
* sys: sys<8>.
* wave::

Porting to Python 3.7

* Changes in Python Behavior::
* Changes in the Python API: Changes in the Python API<5>.
* C API 中的改動: C API 中的改動<4>.
* CPython 位元組碼變更: CPython 位元組碼變更<6>.
* Windows-only Changes: Windows-only Changes<2>.
* Other CPython implementation changes::

Python 3.6 有什麼新功能

* Summary: Summary -- Release highlights<3>. Release highlights
* New Features: New Features<7>.
* 其他語言更動: 其他語言更動<7>.
* 新模組: 新模組<4>.
* 改進的模組: 改進的模組<7>.
* 最佳化: 最佳化<7>.
* Build and C API Changes: Build and C API Changes<2>.
* Other Improvements::
* 已棄用: 已棄用<9>.
* 已移除: 已移除<7>.
* Porting to Python 3.6: Porting to Python 3 6.
* Python 3.6.2 中顯著的變更: Python 3 6 2 中顯著的變更.
* Python 3.6.4 中顯著的變更: Python 3 6 4 中顯著的變更.
* Python 3.6.5 中顯著的變更: Python 3 6 5 中顯著的變更.
* Python 3.6.7 中顯著的變更: Python 3 6 7 中顯著的變更.
* Python 3.6.10 中顯著的變更: Python 3 6 10 中顯著的變更.
* Python 3.6.13 中顯著的變更: Python 3 6 13 中顯著的變更.
* Python 3.6.14 中顯著的變更: Python 3 6 14 中顯著的變更.

New Features

* PEP 498; Formatted string literals: PEP 498 Formatted string literals.
* PEP 526; Syntax for variable annotations: PEP 526 Syntax for variable annotations.
* PEP 515; Underscores in Numeric Literals: PEP 515 Underscores in Numeric Literals.
* PEP 525; Asynchronous Generators: PEP 525 Asynchronous Generators.
* PEP 530; Asynchronous Comprehensions: PEP 530 Asynchronous Comprehensions.
* PEP 487; Simpler customization of class creation: PEP 487 Simpler customization of class creation.
* PEP 487; Descriptor Protocol Enhancements: PEP 487 Descriptor Protocol Enhancements.
* PEP 519; Adding a file system path protocol: PEP 519 Adding a file system path protocol.
* PEP 495; Local Time Disambiguation: PEP 495 Local Time Disambiguation.
* PEP 529; Change Windows filesystem encoding to UTF-8: PEP 529 Change Windows filesystem encoding to UTF-8.
* PEP 528; Change Windows console encoding to UTF-8: PEP 528 Change Windows console encoding to UTF-8.
* PEP 520; Preserving Class Attribute Definition Order: PEP 520 Preserving Class Attribute Definition Order.
* PEP 468; Preserving Keyword Argument Order: PEP 468 Preserving Keyword Argument Order.
* New dict implementation::
* PEP 523; Adding a frame evaluation API to CPython: PEP 523 Adding a frame evaluation API to CPython.
* PYTHONMALLOC environment variable::
* DTrace and SystemTap probing support::

新模組

* secrets::

改進的模組

* array: array<4>.
* ast: ast<4>.
* asyncio: asyncio<9>.
* binascii: binascii<2>.
* cmath::
* collections: collections<4>.
* concurrent.futures: concurrent futures<4>.
* contextlib: contextlib<4>.
* datetime: datetime<5>.
* decimal: decimal<2>.
* distutils: distutils<5>.
* email: email<2>.
* encodings: encodings<2>.
* enum: enum<6>.
* faulthandler: faulthandler<2>.
* fileinput: fileinput<2>.
* hashlib: hashlib<5>.
* http.client: http client<2>.
* idlelib and IDLE: idlelib and IDLE<2>.
* importlib: importlib<6>.
* inspect: inspect<6>.
* json::
* logging: logging<4>.
* math: math<7>.
* multiprocessing: multiprocessing<5>.
* os: os<8>.
* pathlib: pathlib<9>.
* pdb: pdb<5>.
* pickle: pickle<2>.
* pickletools::
* pydoc: pydoc<3>.
* random: random<4>.
* re: re<5>.
* readline::
* rlcompleter::
* shlex: shlex<2>.
* site: site<3>.
* sqlite3: sqlite3<7>.
* socket: socket<7>.
* socketserver: socketserver<2>.
* ssl: ssl<7>.
* statistics: statistics<5>.
* struct::
* subprocess: subprocess<3>.
* sys: sys<9>.
* telnetlib::
* time: time<6>.
* timeit::
* tkinter: tkinter<6>.
* traceback: traceback<4>.
* tracemalloc: tracemalloc<3>.
* typing: typing<9>.
* unicodedata: unicodedata<7>.
* unittest.mock: unittest mock<2>.
* urllib.request: urllib request.
* urllib.robotparser: urllib robotparser.
* venv: venv<5>.
* warnings: warnings<4>.
* winreg::
* winsound::
* xmlrpc.client: xmlrpc client.
* zipfile: zipfile<3>.
* zlib::

已棄用

* 新關鍵字::
* Deprecated Python behavior::
* Deprecated Python modules, functions and methods: Deprecated Python modules functions and methods<2>.
* xml: xml<6>.
* Deprecated functions and types of the C API: Deprecated functions and types of the C API<2>.
* Deprecated Build Options::

Deprecated Python modules, functions and methods

* asynchat::
* asyncore::
* dbm: dbm<4>.
* distutils: distutils<6>.
* grp::
* importlib: importlib<7>.
* os: os<9>.
* re: re<6>.
* ssl: ssl<8>.
* tkinter: tkinter<7>.
* venv: venv<6>.

已移除

* API and Feature Removals: API and Feature Removals<3>.

Porting to Python 3.6

* Changes in 'python' Command Behavior::
* Changes in the Python API: Changes in the Python API<6>.
* C API 中的改動: C API 中的改動<5>.
* CPython 位元組碼變更: CPython 位元組碼變更<7>.

Python 3.6.2 中顯著的變更

* New make regen-all build target::
* Removal of make touch build target::

Python 3.4 有什麼新功能

* Summary: Summary -- Release highlights<4>. Release highlights
* New Features: New Features<8>.
* 其他語言更動: 其他語言更動<8>.
* 新增模組: 新增模組<4>.
* 改進的模組: 改進的模組<8>.
* Other module-level changes::
* 最佳化: 最佳化<8>.
* Build and C API Changes: Build and C API Changes<3>.
* 已棄用: 已棄用<10>.
* 已移除: 已移除<8>.
* Porting to Python 3.5: Porting to Python 3 5.
* Python 3.5.4 中顯著的變更: Python 3 5 4 中顯著的變更.

New Features

* PEP 492 - Coroutines with async and await syntax::
* PEP 465 - A dedicated infix operator for matrix multiplication::
* PEP 448 - Additional Unpacking Generalizations::
* PEP 461 - percent formatting support for bytes and bytearray::
* PEP 484 - Type Hints::
* PEP 471 - os.scandir() function: PEP 471 - os scandir function -- a better and faster directory iterator. a better and faster directory iterator
* PEP 475; Retry system calls failing with EINTR: PEP 475 Retry system calls failing with EINTR.
* PEP 479; Change StopIteration handling inside generators: PEP 479 Change StopIteration handling inside generators.
* PEP 485; A function for testing approximate equality: PEP 485 A function for testing approximate equality.
* PEP 486; Make the Python Launcher aware of virtual environments: PEP 486 Make the Python Launcher aware of virtual environments.
* PEP 488; Elimination of PYO files: PEP 488 Elimination of PYO files.
* PEP 489; Multi-phase extension module initialization: PEP 489 Multi-phase extension module initialization.

新增模組

* typing: typing<10>.
* zipapp: zipapp<2>.

改進的模組

* argparse: argparse<4>.
* asyncio: asyncio<10>.
* bz2::
* cgi::
* cmath: cmath<2>.
* code::
* collections: collections<5>.
* collections.abc: collections abc<3>.
* compileall: compileall<4>.
* concurrent.futures: concurrent futures<5>.
* configparser: configparser<5>.
* contextlib: contextlib<5>.
* csv: csv<3>.
* curses: curses<4>.
* dbm: dbm<5>.
* difflib::
* distutils: distutils<7>.
* doctest: doctest<3>.
* email: email<3>.
* enum: enum<7>.
* faulthandler: faulthandler<3>.
* functools: functools<4>.
* glob: glob<3>.
* gzip: gzip<4>.
* heapq::
* http: http<2>.
* http.client: http client<3>.
* idlelib and IDLE: idlelib and IDLE<3>.
* imaplib: imaplib<2>.
* imghdr::
* importlib: importlib<8>.
* inspect: inspect<7>.
* io: io<5>.
* ipaddress: ipaddress<4>.
* json: json<2>.
* linecache: linecache<2>.
* locale: locale<6>.
* logging: logging<5>.
* lzma::
* math: math<8>.
* multiprocessing: multiprocessing<6>.
* operator: operator<2>.
* os: os<10>.
* pathlib: pathlib<10>.
* pickle: pickle<3>.
* poplib: poplib<2>.
* re: re<7>.
* readline: readline<2>.
* selectors::
* shutil: shutil<5>.
* signal: signal<3>.
* smtpd: smtpd<2>.
* smtplib: smtplib<2>.
* sndhdr::
* socket: socket<8>.
* ssl: ssl<9>.
* sqlite3: sqlite3<8>.
* subprocess: subprocess<4>.
* sys: sys<10>.
* sysconfig: sysconfig<2>.
* tarfile: tarfile<6>.
* threading: threading<6>.
* time: time<7>.
* timeit: timeit<2>.
* tkinter: tkinter<8>.
* traceback: traceback<5>.
* types: types<5>.
* unicodedata: unicodedata<8>.
* unittest: unittest<8>.
* unittest.mock: unittest mock<3>.
* urllib: urllib<2>.
* wsgiref::
* xmlrpc: xmlrpc<2>.
* xml.sax: xml sax.
* zipfile: zipfile<4>.

ssl

* Memory BIO Support::
* Application-Layer Protocol Negotiation Support::
* Other Changes::

已棄用

* New Keywords::
* Deprecated Python Behavior: Deprecated Python Behavior<2>.
* Unsupported Operating Systems::
* Deprecated Python modules, functions and methods: Deprecated Python modules functions and methods<3>.

已移除

* API and Feature Removals: API and Feature Removals<4>.

Porting to Python 3.5

* Changes in Python behavior: Changes in Python behavior<2>.
* Changes in the Python API: Changes in the Python API<7>.
* C API 中的改動: C API 中的改動<6>.

Python 3.5.4 中顯著的變更

* New make regen-all build target: New make regen-all build target<2>.
* Removal of make touch build target: Removal of make touch build target<2>.

Python 3.4 有什麼新功能

* Summary: Summary -- Release Highlights<3>. Release Highlights
* New Features: New Features<9>.
* 新模組: 新模組<5>.
* 改進的模組: 改進的模組<9>.
* CPython 實作變更::
* 已棄用: 已棄用<11>.
* 已移除: 已移除<9>.
* Porting to Python 3.4: Porting to Python 3 4.
* 3.4.3 中的變更: 3 4 3 中的變更.

New Features

* PEP 453; Explicit Bootstrapping of PIP in Python Installations: PEP 453 Explicit Bootstrapping of PIP in Python Installations.
* PEP 446; Newly Created File Descriptors Are Non-Inheritable: PEP 446 Newly Created File Descriptors Are Non-Inheritable.
* Improvements to Codec Handling::
* PEP 451; A ModuleSpec Type for the Import System: PEP 451 A ModuleSpec Type for the Import System.
* 其他語言更動: 其他語言更動<9>.

PEP 453: Explicit Bootstrapping of PIP in Python Installations

* Bootstrapping pip By Default::
* Documentation Changes::

新模組

* asyncio: asyncio<11>.
* ensurepip: ensurepip<2>.
* enum: enum<8>.
* pathlib: pathlib<11>.
* selectors: selectors<2>.
* statistics: statistics<6>.
* tracemalloc: tracemalloc<4>.

改進的模組

* abc::
* aifc: aifc<2>.
* argparse: argparse<5>.
* audioop::
* base64: base64<3>.
* collections: collections<6>.
* colorsys::
* contextlib: contextlib<6>.
* dbm: dbm<6>.
* dis: dis<4>.
* doctest: doctest<4>.
* email: email<4>.
* filecmp::
* functools: functools<5>.
* gc: gc<6>.
* glob: glob<4>.
* hashlib: hashlib<6>.
* hmac: hmac<3>.
* html::
* http: http<3>.
* idlelib 與 IDLE::
* importlib: importlib<9>.
* inspect: inspect<8>.
* ipaddress: ipaddress<5>.
* logging: logging<6>.
* marshal: marshal<2>.
* mmap: mmap<3>.
* multiprocessing: multiprocessing<7>.
* operator: operator<3>.
* os: os<11>.
* pdb: pdb<6>.
* pickle: pickle<4>.
* plistlib: plistlib<2>.
* poplib: poplib<3>.
* pprint: pprint<4>.
* pty::
* pydoc: pydoc<4>.
* re: re<8>.
* resource::
* select::
* shelve: shelve<2>.
* shutil: shutil<6>.
* smtpd: smtpd<3>.
* smtplib: smtplib<3>.
* socket: socket<9>.
* sqlite3: sqlite3<9>.
* ssl: ssl<10>.
* stat::
* struct: struct<2>.
* subprocess: subprocess<5>.
* sunau: sunau<2>.
* sys: sys<11>.
* tarfile: tarfile<7>.
* textwrap::
* threading: threading<7>.
* traceback: traceback<6>.
* types: types<6>.
* urllib: urllib<3>.
* unittest: unittest<9>.
* venv: venv<7>.
* wave: wave<2>.
* weakref: weakref<2>.
* xml.etree: xml etree<2>.
* zipfile: zipfile<5>.

CPython 實作變更

* PEP 445; Customization of CPython Memory Allocators: PEP 445 Customization of CPython Memory Allocators.
* PEP 442; Safe Object Finalization: PEP 442 Safe Object Finalization.
* PEP 456; Secure and Interchangeable Hash Algorithm: PEP 456 Secure and Interchangeable Hash Algorithm.
* PEP 436; Argument Clinic: PEP 436 Argument Clinic.
* Other Build and C API Changes::
* Other Improvements: Other Improvements<2>.
* 顯著最佳化::

已棄用

* Deprecations in the Python API::
* 已棄用功能::

已移除

* Operating Systems No Longer Supported::
* API 與功能的移除::
* 程式碼的清除::

Porting to Python 3.4

* Changes in 'python' Command Behavior: Changes in 'python' Command Behavior<2>.
* Python API 的變更: Python API 的變更<2>.
* C API 中的改動: C API 中的改動<7>.

3.4.3 中的變更

* PEP 476; Enabling certificate verification by default for stdlib http clients: PEP 476 Enabling certificate verification by default for stdlib http clients.

Python 3.3 有什麼新功能

* Summary: Summary -- Release highlights<5>. Release highlights
* PEP 405：虛擬環境::
* PEP 420; Implicit Namespace Packages: PEP 420 Implicit Namespace Packages.
* PEP 3118; New memoryview implementation and buffer protocol documentation: PEP 3118 New memoryview implementation and buffer protocol documentation.
* PEP 393; Flexible String Representation: PEP 393 Flexible String Representation.
* PEP 397：適用於 Windows 的 Python 啟動器::
* PEP 3151; Reworking the OS and IO exception hierarchy: PEP 3151 Reworking the OS and IO exception hierarchy.
* PEP 380; Syntax for Delegating to a Subgenerator: PEP 380 Syntax for Delegating to a Subgenerator.
* PEP 409; Suppressing exception context: PEP 409 Suppressing exception context.
* PEP 414; Explicit Unicode literals: PEP 414 Explicit Unicode literals.
* PEP 3155; Qualified name for classes and functions: PEP 3155 Qualified name for classes and functions.
* PEP 412; Key-Sharing Dictionary: PEP 412 Key-Sharing Dictionary.
* PEP 362：函式簽名物件::
* PEP 421：新增 sys.implementation: PEP 421：新增 sys implementation.
* 使用 importlib 作為 import 的實作::
* 其他語言更動: 其他語言更動<10>.
* A Finer-Grained Import Lock::
* 內建函式和型別::
* 新模組: 新模組<6>.
* 改進的模組: 改進的模組<10>.
* 最佳化: 最佳化<9>.
* 建置和 C API 更改::
* 已棄用: 已棄用<12>.
* 移植到 Python 3.3: 移植到 Python 3 3.

PEP 3118: New memoryview implementation and buffer protocol documentation

* 功能::
* API 變更::

PEP 393: Flexible String Representation

* 功能性::
* 性能和資源使用情況::

PEP 421：新增 sys.implementation

* SimpleNamespace::

使用 importlib 作為 import 的實作

* 新 API::
* 明顯的變更::

新模組

* faulthandler: faulthandler<4>.
* ipaddress: ipaddress<6>.
* lzma: lzma<2>.

改進的模組

* abc: abc<2>.
* array: array<5>.
* base64: base64<4>.
* binascii: binascii<3>.
* bz2: bz2<2>.
* codecs: codecs<2>.
* collections: collections<7>.
* contextlib: contextlib<7>.
* crypt: crypt<2>.
* curses: curses<5>.
* datetime: datetime<6>.
* decimal: decimal<3>.
* email: email<5>.
* ftplib: ftplib<3>.
* functools: functools<6>.
* gc: gc<7>.
* hmac: hmac<4>.
* http: http<4>.
* html: html<2>.
* imaplib: imaplib<3>.
* inspect: inspect<9>.
* io: io<6>.
* itertools: itertools<6>.
* logging: logging<7>.
* math: math<9>.
* mmap: mmap<4>.
* multiprocessing: multiprocessing<8>.
* nntplib: nntplib<2>.
* os: os<12>.
* pdb: pdb<7>.
* pickle: pickle<5>.
* pydoc: pydoc<5>.
* re: re<9>.
* sched::
* select: select<2>.
* shlex: shlex<3>.
* shutil: shutil<7>.
* signal: signal<4>.
* smtpd: smtpd<4>.
* smtplib: smtplib<4>.
* socket: socket<10>.
* socketserver: socketserver<3>.
* sqlite3: sqlite3<10>.
* ssl: ssl<11>.
* stat: stat<2>.
* struct: struct<3>.
* subprocess: subprocess<6>.
* sys: sys<12>.
* tarfile: tarfile<8>.
* tempfile: tempfile<4>.
* textwrap: textwrap<2>.
* threading: threading<8>.
* time: time<8>.
* types: types<7>.
* unittest: unittest<10>.
* urllib: urllib<4>.
* webbrowser: webbrowser<3>.
* xml.etree.ElementTree: xml etree ElementTree<2>.
* zlib: zlib<2>.

decimal

* 功能: 功能<2>.
* API 變更: API 變更<2>.

email

* Policy Framework::
* Provisional Policy with New Header API::
* 其他 API 變更::

已棄用

* 不支援的作業系統::
* 已棄用的 Python 模組、函式和方法::
* C API 中已棄用的函式和型別::
* 已棄用的功能::

移植到 Python 3.3

* 移植 Python 程式碼::
* Porting C code::
* Building C extensions::
* 命令列開關更改::

Python 3.2 有什麼新功能

* PEP 384; Defining a Stable ABI: PEP 384 Defining a Stable ABI.
* PEP 389; Argparse 命令列剖析模組: PEP 389 Argparse 命令列剖析模組.
* PEP 391; Dictionary Based Configuration for Logging: PEP 391 Dictionary Based Configuration for Logging.
* PEP 3148：concurrent.futures 模組: PEP 3148：concurrent futures 模組.
* PEP 3147; PYC Repository Directories: PEP 3147 PYC Repository Directories.
* PEP 3149; ABI Version Tagged .so Files: PEP 3149 ABI Version Tagged so Files.
* PEP 3333; Python Web Server Gateway Interface v1.0.1: PEP 3333 Python Web Server Gateway Interface v1 0 1.
* 其他語言更動: 其他語言更動<11>.
* New, Improved, and Deprecated Modules: New Improved and Deprecated Modules.
* Multi-threading::
* 最佳化: 最佳化<10>.
* Unicode::
* 編解碼器::
* 文件::
* IDLE::
* Code Repository::
* Build and C API Changes: Build and C API Changes<4>.
* Porting to Python 3.2: Porting to Python 3 2.

New, Improved, and Deprecated Modules

* email: email<6>.
* elementtree::
* functools: functools<7>.
* itertools: itertools<7>.
* collections: collections<8>.
* threading: threading<9>.
* datetime 和 time::
* math: math<10>.
* abc: abc<3>.
* io: io<7>.
* reprlib::
* logging: logging<8>.
* csv: csv<4>.
* contextlib: contextlib<8>.
* decimal and fractions::
* ftp::
* popen::
* select: select<3>.
* gzip 和 zipfile::
* tarfile: tarfile<9>.
* hashlib: hashlib<7>.
* ast: ast<5>.
* os: os<13>.
* shutil: shutil<8>.
* sqlite3: sqlite3<11>.
* html: html<3>.
* socket: socket<11>.
* ssl: ssl<12>.
* nntp::
* certificates::
* imaplib: imaplib<4>.
* http.client: http client<4>.
* unittest: unittest<11>.
* random: random<5>.
* poplib: poplib<4>.
* asyncore: asyncore<2>.
* tempfile: tempfile<5>.
* inspect: inspect<10>.
* pydoc: pydoc<6>.
* dis: dis<5>.
* dbm: dbm<7>.
* ctypes: ctypes<2>.
* site: site<4>.
* sysconfig: sysconfig<3>.
* pdb: pdb<8>.
* configparser: configparser<6>.
* urllib.parse: urllib parse<6>.
* mailbox::
* turtledemo::

Python 3.1 有什麼新功能

* PEP 372：有序字典::
* PEP 378; Format Specifier for Thousands Separator: PEP 378 Format Specifier for Thousands Separator.
* 其他語言更動: 其他語言更動<12>.
* New, Improved, and Deprecated Modules: New Improved and Deprecated Modules<2>.
* 最佳化: 最佳化<11>.
* IDLE: IDLE<2>.
* Build and C API Changes: Build and C API Changes<5>.
* Porting to Python 3.1: Porting to Python 3 1.

Python 3.0 有什麼新功能

* Common Stumbling Blocks::
* 語法變更概要::
* Changes Already Present In Python 2.6: Changes Already Present In Python 2 6.
* 函式庫變更::
* PEP 3101; A New Approach To String Formatting: PEP 3101 A New Approach To String Formatting.
* Changes To Exceptions::
* Miscellaneous Other Changes::
* Build and C API Changes: Build and C API Changes<6>.
* Performance::
* Porting To Python 3.0: Porting To Python 3 0.

Common Stumbling Blocks

* Print Is A Function::
* Views And Iterators Instead Of Lists::
* Ordering Comparisons::
* 整數::
* Text Vs. Data Instead Of Unicode Vs. 8-bit: Text Vs Data Instead Of Unicode Vs 8-bit.

語法變更概要

* New Syntax::
* 語法變更::
* 已被移除的語法::

Miscellaneous Other Changes

* Operators And Special Methods::
* Builtins::

Python 2.7 有什麼新功能

* Python 2.x 的未來: Python 2 x 的未來.
* Changes to the Handling of Deprecation Warnings::
* Python 3.1 Features: Python 3 1 Features.
* PEP 372; Adding an Ordered Dictionary to collections: PEP 372 Adding an Ordered Dictionary to collections.
* PEP 378; Format Specifier for Thousands Separator: PEP 378 Format Specifier for Thousands Separator<2>.
* PEP 389; The argparse Module for Parsing Command Lines: PEP 389 The argparse Module for Parsing Command Lines.
* PEP 391; Dictionary-Based Configuration For Logging: PEP 391 Dictionary-Based Configuration For Logging.
* PEP 3106; Dictionary Views: PEP 3106 Dictionary Views.
* PEP 3137; The memoryview Object: PEP 3137 The memoryview Object.
* 其他語言更動: 其他語言更動<13>.
* New and Improved Modules::
* Build and C API Changes: Build and C API Changes<7>.
* Other Changes and Fixes::
* Porting to Python 2.7: Porting to Python 2 7.
* New Features Added to Python 2.7 Maintenance Releases: New Features Added to Python 2 7 Maintenance Releases.
* 致謝::

其他語言更動

* Interpreter Changes::
* 最佳化: 最佳化<12>.

New and Improved Modules

* New module; importlib: New module importlib.
* New module; sysconfig: New module sysconfig.
* ttk; Themed Widgets for Tk: ttk Themed Widgets for Tk.
* Updated module; unittest: Updated module unittest.
* Updated module; ElementTree 1.3: Updated module ElementTree 1 3.

Build and C API Changes

* Capsules::
* Port-Specific Changes; Windows: Port-Specific Changes Windows.
* Port-Specific Changes; Mac OS X: Port-Specific Changes Mac OS X.
* Port-Specific Changes; FreeBSD: Port-Specific Changes FreeBSD.

New Features Added to Python 2.7 Maintenance Releases

* Two new environment variables for debug mode::
* PEP 434; IDLE Enhancement Exception for All Branches: PEP 434 IDLE Enhancement Exception for All Branches.
* PEP 466; Network Security Enhancements for Python 2.7: PEP 466 Network Security Enhancements for Python 2 7.
* PEP 477; Backport ensurepip (PEP 453) to Python 2.7: PEP 477 Backport ensurepip PEP 453 to Python 2 7.
* PEP 476; Enabling certificate verification by default for stdlib http clients: PEP 476 Enabling certificate verification by default for stdlib http clients<2>.
* PEP 493; HTTPS verification migration tools for Python 2.7: PEP 493 HTTPS verification migration tools for Python 2 7.
* New make regen-all build target: New make regen-all build target<3>.
* Removal of make touch build target: Removal of make touch build target<3>.

PEP 477: Backport ensurepip (PEP 453) to Python 2.7

* Bootstrapping pip By Default: Bootstrapping pip By Default<2>.
* Documentation Changes: Documentation Changes<2>.

Python 2.6 有什麼新功能

* Python 3.0: Python 3 0.
* Changes to the Development Process::
* PEP 343; The 'with' statement: PEP 343 The 'with' statement.
* PEP 366; Explicit Relative Imports From a Main Module: PEP 366 Explicit Relative Imports From a Main Module.
* PEP 370; Per-user site-packages Directory: PEP 370 Per-user site-packages Directory.
* PEP 371; The multiprocessing Package: PEP 371 The multiprocessing Package.
* PEP 3101; Advanced String Formatting: PEP 3101 Advanced String Formatting.
* PEP 3105; print As a Function: PEP 3105 print As a Function.
* PEP 3110; Exception-Handling Changes: PEP 3110 Exception-Handling Changes.
* PEP 3112; Byte Literals: PEP 3112 Byte Literals.
* PEP 3116; New I/O Library: PEP 3116 New I/O Library.
* PEP 3118：修訂緩衝協定::
* PEP 3119; Abstract Base Classes: PEP 3119 Abstract Base Classes.
* PEP 3127; Integer Literal Support and Syntax: PEP 3127 Integer Literal Support and Syntax.
* PEP 3129; Class Decorators: PEP 3129 Class Decorators.
* PEP 3141; A Type Hierarchy for Numbers: PEP 3141 A Type Hierarchy for Numbers.
* 其他語言更動: 其他語言更動<14>.
* New and Improved Modules: New and Improved Modules<2>.
* Deprecations and Removals::
* Build and C API Changes: Build and C API Changes<8>.
* Porting to Python 2.6: Porting to Python 2 6.
* 致謝: 致謝<2>.

Changes to the Development Process

* New Issue Tracker; Roundup: New Issue Tracker Roundup.
* New Documentation Format; reStructuredText Using Sphinx: New Documentation Format reStructuredText Using Sphinx.

PEP 343: The 'with' statement

* Writing Context Managers::
* contextlib 模組::

PEP 3141: A Type Hierarchy for Numbers

* The fractions Module::

其他語言更動

* 最佳化: 最佳化<13>.
* Interpreter Changes: Interpreter Changes<2>.

New and Improved Modules

* ast 模組::
* future_builtins 模組::
* The json module; JavaScript Object Notation: The json module JavaScript Object Notation.
* The plistlib module; A Property-List Parser: The plistlib module A Property-List Parser.
* ctypes Enhancements::
* Improved SSL Support::

Build and C API Changes

* Port-Specific Changes; Windows: Port-Specific Changes Windows<2>.
* Port-Specific Changes; Mac OS X: Port-Specific Changes Mac OS X<2>.
* Port-Specific Changes; IRIX: Port-Specific Changes IRIX.

Python 2.5 有什麼新功能

* PEP 308; Conditional Expressions: PEP 308 Conditional Expressions.
* PEP 309; Partial Function Application: PEP 309 Partial Function Application.
* PEP 314; Metadata for Python Software Packages v1.1: PEP 314 Metadata for Python Software Packages v1 1.
* PEP 328; Absolute and Relative Imports: PEP 328 Absolute and Relative Imports.
* PEP 338; Executing Modules as Scripts: PEP 338 Executing Modules as Scripts.
* PEP 341; Unified try/except/finally: PEP 341 Unified try/except/finally.
* PEP 342; New Generator Features: PEP 342 New Generator Features.
* PEP 343：'with' 陳述式::
* PEP 352; Exceptions as New-Style Classes: PEP 352 Exceptions as New-Style Classes.
* PEP 353; Using ssize_t as the index type: PEP 353 Using ssize_t as the index type.
* PEP 357; The '__index__' method: PEP 357 The '__index__' method.
* 其他語言更動: 其他語言更動<15>.
* New, Improved, and Removed Modules: New Improved and Removed Modules.
* Build and C API Changes: Build and C API Changes<9>.
* Porting to Python 2.5: Porting to Python 2 5.
* 致謝: 致謝<3>.

PEP 343：'with' 陳述式

* Writing Context Managers: Writing Context Managers<2>.
* contextlib 模組: contextlib 模組<2>.

其他語言更動

* Interactive Interpreter Changes::
* 最佳化: 最佳化<14>.

New, Improved, and Removed Modules

* ctypes 套件::
* ElementTree 套件::
* hashlib 套件::
* sqlite3 套件::
* wsgiref 套件::

Build and C API Changes

* Port-Specific Changes::

Python 2.4 有什麼新功能

* PEP 218; Built-In Set Objects: PEP 218 Built-In Set Objects.
* PEP 237; Unifying Long Integers and Integers: PEP 237 Unifying Long Integers and Integers.
* PEP 289; Generator Expressions: PEP 289 Generator Expressions.
* PEP 292; Simpler String Substitutions: PEP 292 Simpler String Substitutions.
* PEP 318; Decorators for Functions and Methods: PEP 318 Decorators for Functions and Methods.
* PEP 322; Reverse Iteration: PEP 322 Reverse Iteration.
* PEP 324; New subprocess Module: PEP 324 New subprocess Module.
* PEP 327; Decimal Data Type: PEP 327 Decimal Data Type.
* PEP 328; Multi-line Imports: PEP 328 Multi-line Imports.
* PEP 331; Locale-Independent Float/String Conversions: PEP 331 Locale-Independent Float/String Conversions.
* 其他語言更動: 其他語言更動<16>.
* New, Improved, and Deprecated Modules: New Improved and Deprecated Modules<3>.
* Build and C API Changes: Build and C API Changes<10>.
* Porting to Python 2.4: Porting to Python 2 4.
* 致謝: 致謝<4>.

PEP 327: Decimal Data Type

* Why is Decimal needed?::
* Decimal 型別::
* Context 型別::

其他語言更動

* 最佳化: 最佳化<15>.

New, Improved, and Deprecated Modules

* cookielib::
* doctest: doctest<5>.

Build and C API Changes

* Port-Specific Changes: Port-Specific Changes<2>.

Python 2.3 有什麼新功能

* PEP 218; A Standard Set Datatype: PEP 218 A Standard Set Datatype.
* PEP 255; Simple Generators: PEP 255 Simple Generators.
* PEP 263; Source Code Encodings: PEP 263 Source Code Encodings.
* PEP 273; Importing Modules from ZIP Archives: PEP 273 Importing Modules from ZIP Archives.
* PEP 277; Unicode file name support for Windows NT: PEP 277 Unicode file name support for Windows NT.
* PEP 278; Universal Newline Support: PEP 278 Universal Newline Support.
* PEP 279：enumerate(): PEP 279：enumerate.
* PEP 282; The logging Package: PEP 282 The logging Package.
* PEP 285; A Boolean Type: PEP 285 A Boolean Type.
* PEP 293; Codec Error Handling Callbacks: PEP 293 Codec Error Handling Callbacks.
* PEP 301; Package Index and Metadata for Distutils: PEP 301 Package Index and Metadata for Distutils.
* PEP 302; New Import Hooks: PEP 302 New Import Hooks.
* PEP 305; Comma-separated Files: PEP 305 Comma-separated Files.
* PEP 307; Pickle Enhancements: PEP 307 Pickle Enhancements.
* Extended Slices::
* 其他語言更動: 其他語言更動<17>.
* New, Improved, and Deprecated Modules: New Improved and Deprecated Modules<4>.
* Pymalloc; A Specialized Object Allocator: Pymalloc A Specialized Object Allocator.
* Build and C API Changes: Build and C API Changes<11>.
* Other Changes and Fixes: Other Changes and Fixes<2>.
* Porting to Python 2.3: Porting to Python 2 3.
* 致謝: 致謝<5>.

其他語言更動

* String Changes::
* 最佳化: 最佳化<16>.

New, Improved, and Deprecated Modules

* Date/Time Type::
* The optparse Module::

Build and C API Changes

* Port-Specific Changes: Port-Specific Changes<3>.

Python 2.2 有什麼新功能

* 簡介::
* PEPs 252 and 253; Type and Class Changes: PEPs 252 and 253 Type and Class Changes.
* PEP 234：疊代器::
* PEP 255; Simple Generators: PEP 255 Simple Generators<2>.
* PEP 237; Unifying Long Integers and Integers: PEP 237 Unifying Long Integers and Integers<2>.
* PEP 238; Changing the Division Operator: PEP 238 Changing the Division Operator.
* Unicode 變更::
* PEP 227; Nested Scopes: PEP 227 Nested Scopes.
* New and Improved Modules: New and Improved Modules<3>.
* 直譯器的變更與修正::
* 其他改動與修正::
* 致謝: 致謝<6>.

PEPs 252 and 253: Type and Class Changes

* Old and New Classes::
* Descriptors::
* Multiple Inheritance; The Diamond Rule: Multiple Inheritance The Diamond Rule.
* Attribute Access::
* 相關連結::

Python 2.1 有什麼新功能

* 簡介: 簡介<2>.
* PEP 227; Nested Scopes: PEP 227 Nested Scopes<2>.
* PEP 236; __future__ Directives: PEP 236 __future__ Directives.
* PEP 207; Rich Comparisons: PEP 207 Rich Comparisons.
* PEP 230; Warning Framework: PEP 230 Warning Framework.
* PEP 229; New Build System: PEP 229 New Build System.
* PEP 205; Weak References: PEP 205 Weak References.
* PEP 232; Function Attributes: PEP 232 Function Attributes.
* PEP 235; Importing Modules on Case-Insensitive Platforms: PEP 235 Importing Modules on Case-Insensitive Platforms.
* PEP 217; Interactive Display Hook: PEP 217 Interactive Display Hook.
* PEP 208; New Coercion Model: PEP 208 New Coercion Model.
* PEP 241; Metadata in Python Packages: PEP 241 Metadata in Python Packages.
* New and Improved Modules: New and Improved Modules<4>.
* Other Changes and Fixes: Other Changes and Fixes<3>.
* 致謝: 致謝<7>.

Python 2.0 有什麼新功能

* 簡介: 簡介<3>.
* What About Python 1.6?: What About Python 1 6?.
* New Development Process::
* Unicode: Unicode<2>.
* 串列綜合運算（List Comprehension）::
* Augmented Assignment::
* String Methods::
* Garbage Collection of Cycles::
* Other Core Changes::
* Porting to 2.0: Porting to 2 0.
* Extending/Embedding Changes::
* Distutils; Making Modules Easy to Install: Distutils Making Modules Easy to Install.
* XML 模組::
* 模組變更::
* 新增模組: 新增模組<5>.
* IDLE Improvements::
* Deleted and Deprecated Modules::
* 致謝: 致謝<8>.

Other Core Changes

* Minor Language Changes::
* Changes to Built-in Functions::

XML 模組

* SAX2 支援::
* DOM 支援::
* Relationship to PyXML::

Changelog（更動日誌）

* Python next::
* Python 3.13.0 release candidate 2: Python 3 13 0 release candidate 2.
* Python 3.13.0 release candidate 1: Python 3 13 0 release candidate 1.
* Python 3.13.0 beta 4: Python 3 13 0 beta 4.
* Python 3.13.0 beta 3: Python 3 13 0 beta 3.
* Python 3.13.0 beta 2: Python 3 13 0 beta 2.
* Python 3.13.0 beta 1: Python 3 13 0 beta 1.
* Python 3.13.0 alpha 6: Python 3 13 0 alpha 6.
* Python 3.13.0 alpha 5: Python 3 13 0 alpha 5.
* Python 3.13.0 alpha 4: Python 3 13 0 alpha 4.
* Python 3.13.0 alpha 3: Python 3 13 0 alpha 3.
* Python 3.13.0 alpha 2: Python 3 13 0 alpha 2.
* Python 3.13.0 alpha 1: Python 3 13 0 alpha 1.
* Python 3.12.0 beta 1: Python 3 12 0 beta 1.
* Python 3.12.0 alpha 7: Python 3 12 0 alpha 7.
* Python 3.12.0 alpha 6: Python 3 12 0 alpha 6.
* Python 3.12.0 alpha 5: Python 3 12 0 alpha 5.
* Python 3.12.0 alpha 4: Python 3 12 0 alpha 4.
* Python 3.12.0 alpha 3: Python 3 12 0 alpha 3.
* Python 3.12.0 alpha 2: Python 3 12 0 alpha 2.
* Python 3.12.0 alpha 1: Python 3 12 0 alpha 1.
* Python 3.11.0 beta 1: Python 3 11 0 beta 1.
* Python 3.11.0 alpha 7: Python 3 11 0 alpha 7.
* Python 3.11.0 alpha 6: Python 3 11 0 alpha 6.
* Python 3.11.0 alpha 5: Python 3 11 0 alpha 5.
* Python 3.11.0 alpha 4: Python 3 11 0 alpha 4.
* Python 3.11.0 alpha 3: Python 3 11 0 alpha 3.
* Python 3.11.0 alpha 2: Python 3 11 0 alpha 2.
* Python 3.11.0 alpha 1: Python 3 11 0 alpha 1.
* Python 3.10.0 beta 1: Python 3 10 0 beta 1.
* Python 3.10.0 alpha 7: Python 3 10 0 alpha 7.
* Python 3.10.0 alpha 6: Python 3 10 0 alpha 6.
* Python 3.10.0 alpha 5: Python 3 10 0 alpha 5.
* Python 3.10.0 alpha 4: Python 3 10 0 alpha 4.
* Python 3.10.0 alpha 3: Python 3 10 0 alpha 3.
* Python 3.10.0 alpha 2: Python 3 10 0 alpha 2.
* Python 3.10.0 alpha 1: Python 3 10 0 alpha 1.
* Python 3.9.0 beta 1: Python 3 9 0 beta 1.
* Python 3.9.0 alpha 6: Python 3 9 0 alpha 6.
* Python 3.9.0 alpha 5: Python 3 9 0 alpha 5.
* Python 3.9.0 alpha 4: Python 3 9 0 alpha 4.
* Python 3.9.0 alpha 3: Python 3 9 0 alpha 3.
* Python 3.9.0 alpha 2: Python 3 9 0 alpha 2.
* Python 3.9.0 alpha 1: Python 3 9 0 alpha 1.
* Python 3.8.0 beta 1: Python 3 8 0 beta 1.
* Python 3.8.0 alpha 4: Python 3 8 0 alpha 4.
* Python 3.8.0 alpha 3: Python 3 8 0 alpha 3.
* Python 3.8.0 alpha 2: Python 3 8 0 alpha 2.
* Python 3.8.0 alpha 1: Python 3 8 0 alpha 1.
* Python 3.7.0 final: Python 3 7 0 final.
* Python 3.7.0 release candidate 1: Python 3 7 0 release candidate 1.
* Python 3.7.0 beta 5: Python 3 7 0 beta 5.
* Python 3.7.0 beta 4: Python 3 7 0 beta 4.
* Python 3.7.0 beta 3: Python 3 7 0 beta 3.
* Python 3.7.0 beta 2: Python 3 7 0 beta 2.
* Python 3.7.0 beta 1: Python 3 7 0 beta 1.
* Python 3.7.0 alpha 4: Python 3 7 0 alpha 4.
* Python 3.7.0 alpha 3: Python 3 7 0 alpha 3.
* Python 3.7.0 alpha 2: Python 3 7 0 alpha 2.
* Python 3.7.0 alpha 1: Python 3 7 0 alpha 1.
* Python 3.6.6 final: Python 3 6 6 final.
* Python 3.6.6 release candidate 1: Python 3 6 6 release candidate 1.
* Python 3.6.5 final: Python 3 6 5 final.
* Python 3.6.5 release candidate 1: Python 3 6 5 release candidate 1.
* Python 3.6.4 final: Python 3 6 4 final.
* Python 3.6.4 release candidate 1: Python 3 6 4 release candidate 1.
* Python 3.6.3 final: Python 3 6 3 final.
* Python 3.6.3 release candidate 1: Python 3 6 3 release candidate 1.
* Python 3.6.2 final: Python 3 6 2 final.
* Python 3.6.2 release candidate 2: Python 3 6 2 release candidate 2.
* Python 3.6.2 release candidate 1: Python 3 6 2 release candidate 1.
* Python 3.6.1 final: Python 3 6 1 final.
* Python 3.6.1 release candidate 1: Python 3 6 1 release candidate 1.
* Python 3.6.0 final: Python 3 6 0 final.
* Python 3.6.0 release candidate 2: Python 3 6 0 release candidate 2.
* Python 3.6.0 release candidate 1: Python 3 6 0 release candidate 1.
* Python 3.6.0 beta 4: Python 3 6 0 beta 4.
* Python 3.6.0 beta 3: Python 3 6 0 beta 3.
* Python 3.6.0 beta 2: Python 3 6 0 beta 2.
* Python 3.6.0 beta 1: Python 3 6 0 beta 1.
* Python 3.6.0 alpha 4: Python 3 6 0 alpha 4.
* Python 3.6.0 alpha 3: Python 3 6 0 alpha 3.
* Python 3.6.0 alpha 2: Python 3 6 0 alpha 2.
* Python 3.6.0 alpha 1: Python 3 6 0 alpha 1.
* Python 3.5.5 final: Python 3 5 5 final.
* Python 3.5.5 release candidate 1: Python 3 5 5 release candidate 1.
* Python 3.5.4 final: Python 3 5 4 final.
* Python 3.5.4 release candidate 1: Python 3 5 4 release candidate 1.
* Python 3.5.3 final: Python 3 5 3 final.
* Python 3.5.3 release candidate 1: Python 3 5 3 release candidate 1.
* Python 3.5.2 final: Python 3 5 2 final.
* Python 3.5.2 release candidate 1: Python 3 5 2 release candidate 1.
* Python 3.5.1 final: Python 3 5 1 final.
* Python 3.5.1 release candidate 1: Python 3 5 1 release candidate 1.
* Python 3.5.0 final: Python 3 5 0 final.
* Python 3.5.0 release candidate 4: Python 3 5 0 release candidate 4.
* Python 3.5.0 release candidate 3: Python 3 5 0 release candidate 3.
* Python 3.5.0 release candidate 2: Python 3 5 0 release candidate 2.
* Python 3.5.0 release candidate 1: Python 3 5 0 release candidate 1.
* Python 3.5.0 beta 4: Python 3 5 0 beta 4.
* Python 3.5.0 beta 3: Python 3 5 0 beta 3.
* Python 3.5.0 beta 2: Python 3 5 0 beta 2.
* Python 3.5.0 beta 1: Python 3 5 0 beta 1.
* Python 3.5.0 alpha 4: Python 3 5 0 alpha 4.
* Python 3.5.0 alpha 3: Python 3 5 0 alpha 3.
* Python 3.5.0 alpha 2: Python 3 5 0 alpha 2.
* Python 3.5.0 alpha 1: Python 3 5 0 alpha 1.

Python next

* Core and Builtins::

Python 3.13.0 release candidate 2

* macOS::
* Windows::
* Tools/Demos::
* Tests::
* Security::
* Library::
* IDLE: IDLE<3>.
* Core and Builtins: Core and Builtins<2>.
* C API::
* Build::

Python 3.13.0 release candidate 1

* Tests: Tests<2>.
* Security: Security<2>.
* Library: Library<2>.
* IDLE: IDLE<4>.
* Core and Builtins: Core and Builtins<3>.
* C API: C API<2>.
* Build: Build<2>.

Python 3.13.0 beta 4

* Tests: Tests<3>.
* Library: Library<3>.
* IDLE: IDLE<5>.
* Documentation::
* Core and Builtins: Core and Builtins<4>.
* C API: C API<3>.
* Build: Build<3>.

Python 3.13.0 beta 3

* Core and Builtins: Core and Builtins<5>.
* Library: Library<4>.
* Build: Build<4>.
* C API: C API<4>.

Python 3.13.0 beta 2

* Security: Security<3>.
* Core and Builtins: Core and Builtins<6>.
* Library: Library<5>.
* Tests: Tests<4>.
* Build: Build<5>.
* Windows: Windows<2>.
* C API: C API<5>.

Python 3.13.0 beta 1

* Security: Security<4>.
* Core and Builtins: Core and Builtins<7>.
* Library: Library<6>.
* Documentation: Documentation<2>.
* Build: Build<6>.
* Windows: Windows<3>.
* macOS: macOS<2>.
* IDLE: IDLE<6>.
* C API: C API<6>.

Python 3.13.0 alpha 6

* Core and Builtins: Core and Builtins<8>.
* Library: Library<7>.
* Documentation: Documentation<3>.
* Tests: Tests<5>.
* Build: Build<7>.
* Windows: Windows<4>.
* C API: C API<7>.

Python 3.13.0 alpha 5

* Security: Security<5>.
* Core and Builtins: Core and Builtins<9>.
* Library: Library<8>.
* Documentation: Documentation<4>.
* Tests: Tests<6>.
* Build: Build<8>.
* Windows: Windows<5>.
* macOS: macOS<3>.
* IDLE: IDLE<7>.
* Tools/Demos: Tools/Demos<2>.
* C API: C API<8>.

Python 3.13.0 alpha 4

* Security: Security<6>.
* Core and Builtins: Core and Builtins<10>.
* Library: Library<9>.
* Documentation: Documentation<5>.
* Tests: Tests<7>.
* Build: Build<9>.
* Windows: Windows<6>.
* macOS: macOS<4>.
* IDLE: IDLE<8>.
* Tools/Demos: Tools/Demos<3>.
* C API: C API<9>.

Python 3.13.0 alpha 3

* Security: Security<7>.
* Core and Builtins: Core and Builtins<11>.
* Library: Library<10>.
* Documentation: Documentation<6>.
* Tests: Tests<8>.
* Build: Build<10>.
* Windows: Windows<7>.
* macOS: macOS<5>.
* IDLE: IDLE<9>.
* C API: C API<10>.

Python 3.13.0 alpha 2

* Core and Builtins: Core and Builtins<12>.
* Library: Library<11>.
* Tests: Tests<9>.
* Build: Build<11>.
* Windows: Windows<8>.
* macOS: macOS<6>.
* IDLE: IDLE<10>.
* Tools/Demos: Tools/Demos<4>.
* C API: C API<11>.

Python 3.13.0 alpha 1

* Security: Security<8>.
* Core and Builtins: Core and Builtins<13>.
* Library: Library<12>.
* Documentation: Documentation<7>.
* Tests: Tests<10>.
* Build: Build<12>.
* Windows: Windows<9>.
* macOS: macOS<7>.
* IDLE: IDLE<11>.
* Tools/Demos: Tools/Demos<5>.
* C API: C API<12>.

Python 3.12.0 beta 1

* Security: Security<9>.
* Core and Builtins: Core and Builtins<14>.
* Library: Library<13>.
* Documentation: Documentation<8>.
* Tests: Tests<11>.
* Build: Build<13>.
* Windows: Windows<10>.
* macOS: macOS<8>.
* IDLE: IDLE<12>.
* Tools/Demos: Tools/Demos<6>.
* C API: C API<13>.

Python 3.12.0 alpha 7

* Core and Builtins: Core and Builtins<15>.
* Library: Library<14>.
* Documentation: Documentation<9>.
* Tests: Tests<12>.
* Build: Build<14>.
* Windows: Windows<11>.
* Tools/Demos: Tools/Demos<7>.
* C API: C API<14>.

Python 3.12.0 alpha 6

* Security: Security<10>.
* Core and Builtins: Core and Builtins<16>.
* Library: Library<15>.
* Documentation: Documentation<10>.
* Tests: Tests<13>.
* Build: Build<15>.
* Windows: Windows<12>.
* macOS: macOS<9>.
* C API: C API<15>.

Python 3.12.0 alpha 5

* Security: Security<11>.
* Core and Builtins: Core and Builtins<17>.
* Library: Library<16>.
* Documentation: Documentation<11>.
* Tests: Tests<14>.
* Build: Build<16>.
* Windows: Windows<13>.

Python 3.12.0 alpha 4

* Core and Builtins: Core and Builtins<18>.
* Library: Library<17>.
* Documentation: Documentation<12>.
* Tests: Tests<15>.
* Build: Build<17>.
* Windows: Windows<14>.
* macOS: macOS<10>.
* Tools/Demos: Tools/Demos<8>.
* C API: C API<16>.

Python 3.12.0 alpha 3

* Security: Security<12>.
* Core and Builtins: Core and Builtins<19>.
* Library: Library<18>.
* Documentation: Documentation<13>.
* Tests: Tests<16>.
* Build: Build<18>.
* Windows: Windows<15>.
* macOS: macOS<11>.
* Tools/Demos: Tools/Demos<9>.
* C API: C API<17>.

Python 3.12.0 alpha 2

* Security: Security<13>.
* Core and Builtins: Core and Builtins<20>.
* Library: Library<19>.
* Documentation: Documentation<14>.
* Tests: Tests<17>.
* Build: Build<19>.
* Windows: Windows<16>.
* macOS: macOS<12>.
* C API: C API<18>.

Python 3.12.0 alpha 1

* Security: Security<14>.
* Core and Builtins: Core and Builtins<21>.
* Library: Library<20>.
* Documentation: Documentation<15>.
* Tests: Tests<18>.
* Build: Build<20>.
* Windows: Windows<17>.
* macOS: macOS<13>.
* IDLE: IDLE<13>.
* Tools/Demos: Tools/Demos<10>.
* C API: C API<19>.

Python 3.11.0 beta 1

* Security: Security<15>.
* Core and Builtins: Core and Builtins<22>.
* Library: Library<21>.
* Documentation: Documentation<16>.
* Tests: Tests<19>.
* Build: Build<21>.
* Windows: Windows<18>.
* macOS: macOS<14>.
* Tools/Demos: Tools/Demos<11>.
* C API: C API<20>.

Python 3.11.0 alpha 7

* Core and Builtins: Core and Builtins<23>.
* Library: Library<22>.
* Documentation: Documentation<17>.
* Tests: Tests<20>.
* Build: Build<22>.
* Windows: Windows<19>.
* macOS: macOS<15>.
* Tools/Demos: Tools/Demos<12>.
* C API: C API<21>.

Python 3.11.0 alpha 6

* Core and Builtins: Core and Builtins<24>.
* Library: Library<23>.
* Documentation: Documentation<18>.
* Tests: Tests<21>.
* Build: Build<23>.
* Windows: Windows<20>.
* IDLE: IDLE<14>.
* C API: C API<22>.

Python 3.11.0 alpha 5

* Core and Builtins: Core and Builtins<25>.
* Library: Library<24>.
* Documentation: Documentation<19>.
* Tests: Tests<22>.
* Build: Build<24>.
* Windows: Windows<21>.
* macOS: macOS<16>.
* IDLE: IDLE<15>.
* C API: C API<23>.

Python 3.11.0 alpha 4

* Core and Builtins: Core and Builtins<26>.
* Library: Library<25>.
* Documentation: Documentation<20>.
* Tests: Tests<23>.
* Build: Build<25>.
* Windows: Windows<22>.
* macOS: macOS<17>.
* C API: C API<24>.

Python 3.11.0 alpha 3

* Core and Builtins: Core and Builtins<27>.
* Library: Library<26>.
* Documentation: Documentation<21>.
* Tests: Tests<24>.
* Build: Build<26>.
* Windows: Windows<23>.
* macOS: macOS<18>.
* C API: C API<25>.

Python 3.11.0 alpha 2

* Core and Builtins: Core and Builtins<28>.
* Library: Library<27>.
* Documentation: Documentation<22>.
* Tests: Tests<25>.
* Build: Build<27>.
* Windows: Windows<24>.
* macOS: macOS<19>.
* IDLE: IDLE<16>.
* C API: C API<26>.

Python 3.11.0 alpha 1

* Security: Security<16>.
* Core and Builtins: Core and Builtins<29>.
* Library: Library<28>.
* Documentation: Documentation<23>.
* Tests: Tests<26>.
* Build: Build<28>.
* Windows: Windows<25>.
* macOS: macOS<20>.
* IDLE: IDLE<17>.
* Tools/Demos: Tools/Demos<13>.
* C API: C API<27>.

Python 3.10.0 beta 1

* Security: Security<17>.
* Core and Builtins: Core and Builtins<30>.
* Library: Library<29>.
* Documentation: Documentation<24>.
* Tests: Tests<27>.
* Build: Build<29>.
* Windows: Windows<26>.
* macOS: macOS<21>.
* IDLE: IDLE<18>.
* C API: C API<28>.

Python 3.10.0 alpha 7

* Security: Security<18>.
* Core and Builtins: Core and Builtins<31>.
* Library: Library<30>.
* Documentation: Documentation<25>.
* Tests: Tests<28>.
* Build: Build<30>.
* Windows: Windows<27>.
* IDLE: IDLE<19>.
* C API: C API<29>.

Python 3.10.0 alpha 6

* Security: Security<19>.
* Core and Builtins: Core and Builtins<32>.
* Library: Library<31>.
* Documentation: Documentation<26>.
* Tests: Tests<29>.
* Build: Build<31>.
* Windows: Windows<28>.
* macOS: macOS<22>.
* IDLE: IDLE<20>.
* C API: C API<30>.

Python 3.10.0 alpha 5

* Security: Security<20>.
* Core and Builtins: Core and Builtins<33>.
* Library: Library<32>.
* Documentation: Documentation<27>.
* Tests: Tests<30>.
* Build: Build<32>.
* Windows: Windows<29>.
* macOS: macOS<23>.
* IDLE: IDLE<21>.
* C API: C API<31>.

Python 3.10.0 alpha 4

* Core and Builtins: Core and Builtins<34>.
* Library: Library<33>.
* Documentation: Documentation<28>.
* Tests: Tests<31>.
* Build: Build<33>.
* macOS: macOS<24>.
* Tools/Demos: Tools/Demos<14>.
* C API: C API<32>.

Python 3.10.0 alpha 3

* Security: Security<21>.
* Core and Builtins: Core and Builtins<35>.
* Library: Library<34>.
* Documentation: Documentation<29>.
* Tests: Tests<32>.
* Build: Build<34>.
* Windows: Windows<30>.
* macOS: macOS<25>.
* IDLE: IDLE<22>.
* Tools/Demos: Tools/Demos<15>.
* C API: C API<33>.

Python 3.10.0 alpha 2

* Security: Security<22>.
* Core and Builtins: Core and Builtins<36>.
* Library: Library<35>.
* Documentation: Documentation<30>.
* Tests: Tests<33>.
* Build: Build<35>.
* Windows: Windows<31>.
* macOS: macOS<26>.
* IDLE: IDLE<23>.
* C API: C API<34>.

Python 3.10.0 alpha 1

* Security: Security<23>.
* Core and Builtins: Core and Builtins<37>.
* Library: Library<36>.
* Documentation: Documentation<31>.
* Tests: Tests<34>.
* Build: Build<36>.
* Windows: Windows<32>.
* macOS: macOS<27>.
* IDLE: IDLE<24>.
* C API: C API<35>.

Python 3.9.0 beta 1

* Security: Security<24>.
* Core and Builtins: Core and Builtins<38>.
* Library: Library<37>.
* Documentation: Documentation<32>.
* Tests: Tests<35>.
* Build: Build<37>.
* Windows: Windows<33>.
* macOS: macOS<28>.
* Tools/Demos: Tools/Demos<16>.
* C API: C API<36>.

Python 3.9.0 alpha 6

* Security: Security<25>.
* Core and Builtins: Core and Builtins<39>.
* Library: Library<38>.
* Documentation: Documentation<33>.
* Tests: Tests<36>.
* Build: Build<38>.
* Windows: Windows<34>.
* macOS: macOS<29>.
* IDLE: IDLE<25>.
* Tools/Demos: Tools/Demos<17>.
* C API: C API<37>.

Python 3.9.0 alpha 5

* Security: Security<26>.
* Core and Builtins: Core and Builtins<40>.
* Library: Library<39>.
* Documentation: Documentation<34>.
* Tests: Tests<37>.
* Build: Build<39>.
* Windows: Windows<35>.
* macOS: macOS<30>.
* IDLE: IDLE<26>.
* Tools/Demos: Tools/Demos<18>.
* C API: C API<38>.

Python 3.9.0 alpha 4

* Security: Security<27>.
* Core and Builtins: Core and Builtins<41>.
* Library: Library<40>.
* Documentation: Documentation<35>.
* Tests: Tests<38>.
* Build: Build<40>.
* Windows: Windows<36>.
* IDLE: IDLE<27>.
* C API: C API<39>.

Python 3.9.0 alpha 3

* Core and Builtins: Core and Builtins<42>.
* Library: Library<41>.
* Documentation: Documentation<36>.
* Build: Build<41>.
* IDLE: IDLE<28>.
* C API: C API<40>.

Python 3.9.0 alpha 2

* Security: Security<28>.
* Core and Builtins: Core and Builtins<43>.
* Library: Library<42>.
* Documentation: Documentation<37>.
* Tests: Tests<39>.
* Build: Build<42>.
* Windows: Windows<37>.
* macOS: macOS<31>.
* IDLE: IDLE<29>.
* C API: C API<41>.

Python 3.9.0 alpha 1

* Security: Security<29>.
* Core and Builtins: Core and Builtins<44>.
* Library: Library<43>.
* Documentation: Documentation<38>.
* Tests: Tests<40>.
* Build: Build<43>.
* Windows: Windows<38>.
* macOS: macOS<32>.
* IDLE: IDLE<30>.
* Tools/Demos: Tools/Demos<19>.
* C API: C API<42>.

Python 3.8.0 beta 1

* Security: Security<30>.
* Core and Builtins: Core and Builtins<45>.
* Library: Library<44>.
* Documentation: Documentation<39>.
* Tests: Tests<41>.
* Build: Build<44>.
* Windows: Windows<39>.
* macOS: macOS<33>.
* IDLE: IDLE<31>.
* Tools/Demos: Tools/Demos<20>.
* C API: C API<43>.

Python 3.8.0 alpha 4

* Security: Security<31>.
* Core and Builtins: Core and Builtins<46>.
* Library: Library<45>.
* Documentation: Documentation<40>.
* Tests: Tests<42>.
* Build: Build<45>.
* Windows: Windows<40>.
* macOS: macOS<34>.
* IDLE: IDLE<32>.
* Tools/Demos: Tools/Demos<21>.
* C API: C API<44>.

Python 3.8.0 alpha 3

* Security: Security<32>.
* Core and Builtins: Core and Builtins<47>.
* Library: Library<46>.
* Documentation: Documentation<41>.
* Tests: Tests<43>.
* Build: Build<46>.
* Windows: Windows<41>.
* IDLE: IDLE<33>.
* Tools/Demos: Tools/Demos<22>.
* C API: C API<45>.

Python 3.8.0 alpha 2

* Core and Builtins: Core and Builtins<48>.
* Library: Library<47>.
* Documentation: Documentation<42>.
* Tests: Tests<44>.
* Windows: Windows<42>.
* IDLE: IDLE<34>.

Python 3.8.0 alpha 1

* Security: Security<33>.
* Core and Builtins: Core and Builtins<49>.
* Library: Library<48>.
* Documentation: Documentation<43>.
* Tests: Tests<45>.
* Build: Build<47>.
* Windows: Windows<43>.
* macOS: macOS<35>.
* IDLE: IDLE<35>.
* Tools/Demos: Tools/Demos<23>.
* C API: C API<46>.

Python 3.7.0 final

* Library: Library<49>.
* C API: C API<47>.

Python 3.7.0 release candidate 1

* Core and Builtins: Core and Builtins<50>.
* Library: Library<50>.
* Documentation: Documentation<44>.
* Build: Build<48>.
* Windows: Windows<44>.
* IDLE: IDLE<36>.

Python 3.7.0 beta 5

* Core and Builtins: Core and Builtins<51>.
* Library: Library<51>.
* Documentation: Documentation<45>.
* Tests: Tests<46>.
* Build: Build<49>.
* macOS: macOS<36>.
* IDLE: IDLE<37>.

Python 3.7.0 beta 4

* Core and Builtins: Core and Builtins<52>.
* Library: Library<52>.
* Documentation: Documentation<46>.
* Tests: Tests<47>.
* Build: Build<50>.
* Windows: Windows<45>.
* macOS: macOS<37>.
* IDLE: IDLE<38>.
* Tools/Demos: Tools/Demos<24>.

Python 3.7.0 beta 3

* Security: Security<34>.
* Core and Builtins: Core and Builtins<53>.
* Library: Library<53>.
* Documentation: Documentation<47>.
* Tests: Tests<48>.
* Build: Build<51>.
* Windows: Windows<46>.
* macOS: macOS<38>.
* IDLE: IDLE<39>.
* Tools/Demos: Tools/Demos<25>.
* C API: C API<48>.

Python 3.7.0 beta 2

* Security: Security<35>.
* Core and Builtins: Core and Builtins<54>.
* Library: Library<54>.
* Documentation: Documentation<48>.
* Tests: Tests<49>.
* Build: Build<52>.
* Windows: Windows<47>.
* macOS: macOS<39>.
* IDLE: IDLE<40>.
* Tools/Demos: Tools/Demos<26>.

Python 3.7.0 beta 1

* Core and Builtins: Core and Builtins<55>.
* Library: Library<55>.
* Documentation: Documentation<49>.
* Tests: Tests<50>.
* Build: Build<53>.
* Windows: Windows<48>.
* macOS: macOS<40>.
* C API: C API<49>.

Python 3.7.0 alpha 4

* Core and Builtins: Core and Builtins<56>.
* Library: Library<56>.
* Documentation: Documentation<50>.
* Tests: Tests<51>.
* Windows: Windows<49>.
* Tools/Demos: Tools/Demos<27>.
* C API: C API<50>.

Python 3.7.0 alpha 3

* Core and Builtins: Core and Builtins<57>.
* Library: Library<57>.
* Documentation: Documentation<51>.
* Tests: Tests<52>.
* Build: Build<54>.
* Windows: Windows<50>.
* macOS: macOS<41>.
* IDLE: IDLE<41>.
* Tools/Demos: Tools/Demos<28>.
* C API: C API<51>.

Python 3.7.0 alpha 2

* Core and Builtins: Core and Builtins<58>.
* Library: Library<58>.
* Documentation: Documentation<52>.
* Build: Build<55>.
* IDLE: IDLE<42>.
* C API: C API<52>.

Python 3.7.0 alpha 1

* Security: Security<36>.
* Core and Builtins: Core and Builtins<59>.
* Library: Library<59>.
* Documentation: Documentation<53>.
* Tests: Tests<53>.
* Build: Build<56>.
* Windows: Windows<51>.
* IDLE: IDLE<43>.
* Tools/Demos: Tools/Demos<29>.
* C API: C API<53>.

Python 3.6.6 release candidate 1

* Core and Builtins: Core and Builtins<60>.
* Library: Library<60>.
* Documentation: Documentation<54>.
* Tests: Tests<54>.
* Build: Build<57>.
* Windows: Windows<52>.
* macOS: macOS<42>.
* IDLE: IDLE<44>.
* Tools/Demos: Tools/Demos<30>.
* C API: C API<54>.

Python 3.6.5 final

* Tests: Tests<55>.
* Build: Build<58>.

Python 3.6.5 release candidate 1

* Security: Security<37>.
* Core and Builtins: Core and Builtins<61>.
* Library: Library<61>.
* Documentation: Documentation<55>.
* Tests: Tests<56>.
* Build: Build<59>.
* Windows: Windows<53>.
* macOS: macOS<43>.
* IDLE: IDLE<45>.
* Tools/Demos: Tools/Demos<31>.
* C API: C API<55>.

Python 3.6.4 release candidate 1

* Core and Builtins: Core and Builtins<62>.
* Library: Library<62>.
* Documentation: Documentation<56>.
* Tests: Tests<57>.
* Build: Build<60>.
* Windows: Windows<54>.
* macOS: macOS<44>.
* IDLE: IDLE<46>.
* Tools/Demos: Tools/Demos<32>.
* C API: C API<56>.

Python 3.6.3 final

* Library: Library<63>.
* Build: Build<61>.

Python 3.6.3 release candidate 1

* Security: Security<38>.
* Core and Builtins: Core and Builtins<63>.
* Library: Library<64>.
* Documentation: Documentation<57>.
* Tests: Tests<58>.
* Build: Build<62>.
* Windows: Windows<55>.
* IDLE: IDLE<47>.
* Tools/Demos: Tools/Demos<33>.

Python 3.6.2 release candidate 2

* Security: Security<39>.

Python 3.6.2 release candidate 1

* Security: Security<40>.
* Core and Builtins: Core and Builtins<64>.
* Library: Library<65>.
* IDLE: IDLE<48>.
* C API: C API<57>.
* Build: Build<63>.
* Documentation: Documentation<58>.
* Tools/Demos: Tools/Demos<34>.
* Tests: Tests<59>.
* Windows: Windows<56>.

Python 3.6.1 final

* Core and Builtins: Core and Builtins<65>.
* Build: Build<64>.

Python 3.6.1 release candidate 1

* Core and Builtins: Core and Builtins<66>.
* Library: Library<66>.
* IDLE: IDLE<49>.
* Windows: Windows<57>.
* C API: C API<58>.
* Documentation: Documentation<59>.
* Tests: Tests<60>.
* Build: Build<65>.

Python 3.6.0 release candidate 2

* Core and Builtins: Core and Builtins<67>.
* Tools/Demos: Tools/Demos<35>.
* Windows: Windows<58>.
* Build: Build<66>.

Python 3.6.0 release candidate 1

* Core and Builtins: Core and Builtins<68>.
* Library: Library<67>.
* C API: C API<59>.
* Documentation: Documentation<60>.
* Tools/Demos: Tools/Demos<36>.

Python 3.6.0 beta 4

* Core and Builtins: Core and Builtins<69>.
* Library: Library<68>.
* Documentation: Documentation<61>.
* Tests: Tests<61>.
* Build: Build<67>.

Python 3.6.0 beta 3

* Core and Builtins: Core and Builtins<70>.
* Library: Library<69>.
* Windows: Windows<59>.
* Build: Build<68>.
* Tests: Tests<62>.

Python 3.6.0 beta 2

* Core and Builtins: Core and Builtins<71>.
* Library: Library<70>.
* Windows: Windows<60>.
* C API: C API<60>.
* Build: Build<69>.
* Tests: Tests<63>.

Python 3.6.0 beta 1

* Core and Builtins: Core and Builtins<72>.
* Library: Library<71>.
* IDLE: IDLE<50>.
* C API: C API<61>.
* Tests: Tests<64>.
* Build: Build<70>.
* Tools/Demos: Tools/Demos<37>.
* Windows: Windows<61>.

Python 3.6.0 alpha 4

* Core and Builtins: Core and Builtins<73>.
* Library: Library<72>.
* IDLE: IDLE<51>.
* Tests: Tests<65>.
* Windows: Windows<62>.
* Build: Build<71>.

Python 3.6.0 alpha 3

* Security: Security<41>.
* Core and Builtins: Core and Builtins<74>.
* Library: Library<73>.
* IDLE: IDLE<52>.
* C API: C API<62>.
* Build: Build<72>.
* Tools/Demos: Tools/Demos<38>.
* Documentation: Documentation<62>.
* Tests: Tests<66>.

Python 3.6.0 alpha 2

* Security: Security<42>.
* Core and Builtins: Core and Builtins<75>.
* Library: Library<74>.
* IDLE: IDLE<53>.
* Documentation: Documentation<63>.
* Tests: Tests<67>.
* Windows: Windows<63>.
* Build: Build<73>.
* C API: C API<63>.
* Tools/Demos: Tools/Demos<39>.

Python 3.6.0 alpha 1

* Security: Security<43>.
* Core and Builtins: Core and Builtins<76>.
* Library: Library<75>.
* IDLE: IDLE<54>.
* Documentation: Documentation<64>.
* Tests: Tests<68>.
* Build: Build<74>.
* Windows: Windows<64>.
* Tools/Demos: Tools/Demos<40>.
* C API: C API<64>.

Python 3.5.5 release candidate 1

* Security: Security<44>.
* Core and Builtins: Core and Builtins<77>.
* Library: Library<76>.

Python 3.5.4 final

* Library: Library<77>.

Python 3.5.4 release candidate 1

* Security: Security<45>.
* Core and Builtins: Core and Builtins<78>.
* Library: Library<78>.
* Documentation: Documentation<65>.
* Tests: Tests<69>.
* Build: Build<75>.
* Windows: Windows<65>.
* C API: C API<65>.

Python 3.5.3 release candidate 1

* Security: Security<46>.
* Core and Builtins: Core and Builtins<79>.
* Library: Library<79>.
* IDLE: IDLE<55>.
* C API: C API<66>.
* Documentation: Documentation<66>.
* Tests: Tests<70>.
* Tools/Demos: Tools/Demos<41>.
* Windows: Windows<66>.
* Build: Build<76>.

Python 3.5.2 final

* Core and Builtins: Core and Builtins<80>.
* Tests: Tests<71>.
* IDLE: IDLE<56>.

Python 3.5.2 release candidate 1

* Security: Security<47>.
* Core and Builtins: Core and Builtins<81>.
* Library: Library<80>.
* IDLE: IDLE<57>.
* Documentation: Documentation<67>.
* Tests: Tests<72>.
* Build: Build<77>.
* Windows: Windows<67>.
* Tools/Demos: Tools/Demos<42>.

Python 3.5.1 final

* Core and Builtins: Core and Builtins<82>.
* Windows: Windows<68>.

Python 3.5.1 release candidate 1

* Core and Builtins: Core and Builtins<83>.
* Library: Library<81>.
* IDLE: IDLE<58>.
* Documentation: Documentation<68>.
* Tests: Tests<73>.
* Build: Build<78>.
* Windows: Windows<69>.
* Tools/Demos: Tools/Demos<43>.

Python 3.5.0 final

* Build: Build<79>.

Python 3.5.0 release candidate 4

* Library: Library<82>.
* Build: Build<80>.

Python 3.5.0 release candidate 3

* Core and Builtins: Core and Builtins<84>.
* Library: Library<83>.

Python 3.5.0 release candidate 2

* Core and Builtins: Core and Builtins<85>.
* Library: Library<84>.

Python 3.5.0 release candidate 1

* Core and Builtins: Core and Builtins<86>.
* Library: Library<85>.
* IDLE: IDLE<59>.
* Documentation: Documentation<69>.
* Tests: Tests<74>.

Python 3.5.0 beta 4

* Core and Builtins: Core and Builtins<87>.
* Library: Library<86>.
* Build: Build<81>.

Python 3.5.0 beta 3

* Core and Builtins: Core and Builtins<88>.
* Library: Library<87>.
* Tests: Tests<75>.
* Documentation: Documentation<70>.
* Build: Build<82>.

Python 3.5.0 beta 2

* Core and Builtins: Core and Builtins<89>.
* Library: Library<88>.

Python 3.5.0 beta 1

* Core and Builtins: Core and Builtins<90>.
* Library: Library<89>.
* IDLE: IDLE<60>.
* Tests: Tests<76>.
* Documentation: Documentation<71>.
* Tools/Demos: Tools/Demos<44>.

Python 3.5.0 alpha 4

* Core and Builtins: Core and Builtins<91>.
* Library: Library<90>.
* Build: Build<83>.
* Tests: Tests<77>.
* Tools/Demos: Tools/Demos<45>.
* C API: C API<67>.

Python 3.5.0 alpha 3

* Core and Builtins: Core and Builtins<92>.
* Library: Library<91>.
* Build: Build<84>.
* Tests: Tests<78>.
* Tools/Demos: Tools/Demos<46>.

Python 3.5.0 alpha 2

* Core and Builtins: Core and Builtins<93>.
* Library: Library<92>.
* Build: Build<85>.
* C API: C API<68>.
* Windows: Windows<70>.

Python 3.5.0 alpha 1

* Core and Builtins: Core and Builtins<94>.
* Library: Library<93>.
* IDLE: IDLE<61>.
* Build: Build<86>.
* C API: C API<69>.
* Documentation: Documentation<72>.
* Tests: Tests<79>.
* Tools/Demos: Tools/Demos<47>.
* Windows: Windows<71>.

Python 教學

* 淺嘗滋味::
* 使用 Python 直譯器::
* 一個非正式的 Python 簡介::
* 深入了解流程控制::
* 資料結構::
* 模組 (Module): 模組 Module.
* 輸入和輸出::
* 錯誤和例外::
* Class（類別）::
* Python 標準函式庫概覽::
* Python 標準函式庫概覽——第二部份::
* 虛擬環境與套件::
* 現在可以來學習些什麼？::
* 互動式輸入編輯和歷史記錄替換::
* 浮點數運算：問題與限制::
* 附錄::

使用 Python 直譯器

* 啟動直譯器::
* 直譯器與它的環境::

啟動直譯器

* 傳遞引數::
* 互動模式::

直譯器與它的環境

* 原始碼的字元編碼 (encoding): 原始碼的字元編碼 encoding.

一個非正式的 Python 簡介

* 把 Python 當作計算機使用::
* 初探程式設計的前幾步::

把 Python 當作計算機使用

* 數字 (Number): 數字 Number.
* 文字::
* List（串列）::

深入了解流程控制

* if 陳述式::
* for 陳述式::
* range() 函式: range 函式.
* 迴圈內的 break 和 continue 陳述式及 else 子句::
* pass 陳述式::
* match 陳述式::
* 定義函式 (function): 定義函式 function.
* 深入了解函式定義::
* 間奏曲：程式碼風格 (Coding Style): 間奏曲：程式碼風格 Coding Style.

深入了解函式定義

* 預設引數值::
* 關鍵字引數::
* 特殊參數::
* 任意引數列表 (Arbitrary Argument Lists): 任意引數列表 Arbitrary Argument Lists.
* 拆解引數列表（Unpacking Argument Lists）::
* Lambda 運算式::
* 說明文件字串 (Documentation Strings): 說明文件字串 Documentation Strings.
* 函式註釋 (Function Annotations): 函式註釋 Function Annotations.

特殊參數

* 位置或關鍵字引數 (Positional-or-Keyword Arguments): 位置或關鍵字引數 Positional-or-Keyword Arguments.
* 僅限位置參數 (Positional-Only Parameters): 僅限位置參數 Positional-Only Parameters.
* 僅限關鍵字引數 (Keyword-Only Arguments): 僅限關鍵字引數 Keyword-Only Arguments.
* 函式範例::
* 回顧::

資料結構

* 進一步了解 List（串列）::
* del 陳述式::
* Tuples 和序列 (Sequences): Tuples 和序列 Sequences.
* 集合 (Sets): 集合 Sets.
* 字典（Dictionary）::
* 迴圈技巧::
* 深入了解條件 (Condition): 深入了解條件 Condition.
* 序列和其他資料類型之比較::

進一步了解 List（串列）

* 將 List 作為 Stack（堆疊）使用::
* 將 List 作為 Queue（佇列）使用::
* List Comprehensions（串列綜合運算）::
* 巢狀的 List Comprehensions::

模組 (Module)

* 深入了解模組::
* 標準模組::
* dir() 函式: dir 函式.
* 套件 (Package): 套件 Package.

深入了解模組

* 把模組當作腳本執行::
* 模組的搜尋路徑::
* 「編譯」Python 檔案::

套件 (Package)

* 從套件中 import *::
* 套件內引用::
* 多目錄中的套件::

輸入和輸出

* 更華麗的輸出格式::
* 讀寫檔案::

更華麗的輸出格式

* 格式化的字串文本 (Formatted String Literals): 格式化的字串文本 Formatted String Literals.
* 字串的 format() method: 字串的 format method.
* 手動格式化字串::
* 格式化字串的舊方法::

讀寫檔案

* 檔案物件的 method::
* 使用 json 儲存結構化資料::

錯誤和例外

* 語法錯誤 (Syntax Error): 語法錯誤 Syntax Error.
* 例外 (Exception): 例外 Exception.
* 處理例外::
* 引發例外::
* 例外鏈接 (Exception Chaining): 例外鏈接 Exception Chaining.
* 使用者自定的例外::
* 定義清理動作::
* 預定義的清理動作::
* 引發及處理多個無關的例外::
* 用註解使例外更詳細::

Class（類別）

* 關於名稱與物件的一段話::
* Python 作用域 (Scope) 及命名空間 (Namespace): Python 作用域 Scope 及命名空間 Namespace.
* 初見 class::
* 隨意的備註::
* 繼承 (Inheritance): 繼承 Inheritance.
* 私有變數::
* 補充說明::
* 疊代器 (Iterator): 疊代器 Iterator.
* 產生器 (Generator): 產生器 Generator.
* 產生器運算式::

Python 作用域 (Scope) 及命名空間 (Namespace)

* 作用域和命名空間的範例::

初見 class

* Class definition（類別定義）語法::
* Class 物件::
* 實例物件::
* Method 物件::
* Class 及實例變數::

繼承 (Inheritance)

* 多重繼承::

Python 標準函式庫概覽

* 作業系統介面::
* 檔案之萬用字元 (File Wildcards): 檔案之萬用字元 File Wildcards.
* 命令列引數::
* 錯誤輸出重新導向與程式終止::
* 字串樣式比對::
* 數學相關::
* 網路存取::
* 日期與時間::
* 資料壓縮::
* 效能量測::
* 品質控管::
* 標準模組庫::

Python 標準函式庫概覽——第二部份

* 輸出格式化 (Output Formatting): 輸出格式化 Output Formatting.
* 模板化 (Templating): 模板化 Templating.
* 二進制資料記錄編排 (Binary Data Record Layouts): 二進制資料記錄編排 Binary Data Record Layouts.
* 多執行緒 (Multi-threading): 多執行緒 Multi-threading.
* 日誌記錄 (Logging): 日誌記錄 Logging.
* 弱引用 (Weak References): 弱引用 Weak References.
* 使用於 List 的工具::
* 十進制浮點數運算 (Decimal Floating-Point Arithmetic): 十進制浮點數運算 Decimal Floating-Point Arithmetic.

虛擬環境與套件

* 簡介: 簡介<4>.
* 建立虛擬環境::
* 用 pip 管理套件::

互動式輸入編輯和歷史記錄替換

* Tab 鍵自動完成 (Tab Completion) 和歷史記錄編輯 (History Editing): Tab 鍵自動完成 Tab Completion 和歷史記錄編輯 History Editing.
* 互動式直譯器的替代方案::

浮點數運算：問題與限制

* 表示法誤差 (Representation Error): 表示法誤差 Representation Error.

附錄

* 互動模式: 互動模式<2>.

互動模式

* 錯誤處理::
* 可執行的 Python 腳本::
* 互動式啟動檔案::
* 客製化模組::

Python 的設置與使用

* 命令列與環境::
* 在 Unix 平臺上使用 Python::
* 配置 Python::
* 在 Windows 上使用 Python::
* 在 Mac 系統使用 Python::
* Using Python on iOS::
* 編輯器與 IDE::

命令列與環境

* 命令列::
* 環境變數::

命令列

* 介面選項::
* Generic options::
* Miscellaneous options::
* Controlling color::
* 你不該使用的選項::

環境變數

* 除錯模式變數::

在 Unix 平臺上使用 Python

* 獲得並安裝 Python 的最新版本::
* 建置 Python::
* 與 Python 相關的路徑和檔案::
* 雜項: 雜項<2>.
* 客製化 OpenSSL::

獲得並安裝 Python 的最新版本

* 在 Linux 上::
* 在 FreeBSD 和 OpenBSD 上::

配置 Python

* 建置需求::
* 產生的檔案::
* 設定選項::
* Python Build System::
* Compiler and linker flags::

產生的檔案

* 設定腳本::

設定選項

* 一般選項::
* C compiler options::
* Linker options::
* Options for third-party dependencies::
* WebAssembly 選項::
* 安裝選項::
* Performance options::
* Python Debug Build::
* Debug options::
* Linker options: Linker options<2>.
* 函式庫選項::
* Security Options::
* macOS 選項::
* iOS Options::
* Cross Compiling Options::

Python Build System

* Main files of the build system::
* 主要建置步驟::
* 主要 Makefile 目標::
* C 擴充模組::

主要 Makefile 目標

* make::
* make platform::
* make profile-opt::
* make clean::
* make distclean::
* make install::
* make test::
* make buildbottest::
* make regen-all::

Compiler and linker flags

* Preprocessor flags::
* 編譯器旗標::
* Linker flags::

在 Windows 上使用 Python

* The full installer::
* The Microsoft Store package::
* nuget.org 套件: nuget org 套件.
* The embeddable package::
* Alternative bundles::
* 設定 Python::
* UTF-8 模式::
* Python Launcher for Windows::
* 找尋模組::
* 額外的模組::
* 編譯 Python 在 Windows::
* 其他平台::

The full installer

* 安裝步驟::
* Removing the MAX_PATH Limitation::
* 安裝排除使用者介面::
* 當安裝時不下載::
* Modifying an install::
* Installing Free-threaded Binaries::

The Microsoft Store package

* Known issues::

Known issues

* Redirection of local data, registry, and temporary paths: Redirection of local data registry and temporary paths.

nuget.org 套件

* Free-threaded packages::

The embeddable package

* Python Application::
* 嵌入 Python::

設定 Python

* Excursus; Setting environment variables: Excursus Setting environment variables.
* Finding the Python executable::

Python Launcher for Windows

* 開始::
* Shebang Lines::
* Arguments in shebang lines::
* Customization::
* Diagnostics::
* Dry Run::
* 安裝隨選::
* Return codes::

開始

* From the command-line::
* 虛擬環境（Virtual environment）::
* From a script::
* 從檔案關聯::

Customization

* Customization via INI files::
* Customizing default Python versions::

額外的模組

* PyWin32::
* cx_Freeze::

在 Mac 系統使用 Python

* 取得和安裝 Python::
* 整合化開發工具 (IDE): 整合化開發工具 IDE.
* 安裝額外的 Python 套件::
* 開發 GUI 程式::
* 發行 Python 應用程式::
* 其他資源::

取得和安裝 Python

* 如何執行 Python 腳本::
* 透過 GUI 執行腳本::
* 設定::

發行 Python 應用程式

* App Store Compliance::

Using Python on iOS

* Python at runtime on iOS::
* Installing Python on iOS::
* App Store Compliance: App Store Compliance<2>.

Python at runtime on iOS

* iOS version compatibility::
* Platform identification::
* Standard library availability::
* Binary extension modules::
* Compiler stub binaries::

Installing Python on iOS

* Tools for building iOS apps::
* Adding Python to an iOS project::

Python 語言參考手冊

* 簡介: 簡介<5>.
* 詞法分析::
* 資料模型::
* 執行模型::
* 模組引入系統::
* 運算式::
* 簡單陳述式::
* 複合陳述式::
* 最高層級元件::
* 完整的語法規格書::

簡介

* Alternate Implementations::
* Notation::

詞法分析

* Line structure::
* Other tokens::
* Identifiers and keywords::
* Literals::
* Operators::
* Delimiters::

Line structure

* Logical lines::
* Physical lines::
* Comments::
* Encoding declarations::
* Explicit line joining::
* Implicit line joining::
* Blank lines::
* Indentation::
* Whitespace between tokens::

Identifiers and keywords

* 關鍵字::
* 軟關鍵字::
* Reserved classes of identifiers::

Literals

* String and Bytes literals::
* String literal concatenation::
* f-string（f 字串）::
* Numeric literals::
* Integer literals::
* 浮點數常數 (Floating-point literals): 浮點數常數 Floating-point literals.
* Imaginary literals::

String and Bytes literals

* 跳脫序列::

資料模型

* Objects, values and types: Objects values and types.
* 標準型別階層::
* Special method names::
* 協程::

標準型別階層

* None::
* NotImplemented::
* Ellipsis::
* numbers.Number: numbers Number.
* Sequences::
* Set types::
* Mappings::
* Callable types::
* 模組: 模組<2>.
* Custom classes::
* Class instances::
* I/O objects (also known as file objects): I/O objects also known as file objects.
* Internal types::

numbers.Number

* numbers.Integral: numbers Integral.
* numbers.Real (float): numbers Real float.
* numbers.Complex (complex): numbers Complex complex.

Sequences

* Immutable sequences::
* Mutable sequences::

Mappings

* 字典::

Callable types

* 自訂函式::
* Instance methods::
* Generator functions::
* Coroutine functions::
* Asynchronous generator functions::
* Built-in functions::
* Built-in methods::
* Classes::
* Class Instances::

自訂函式

* 特殊唯讀屬性::
* 特殊可寫屬性::

Internal types

* Code objects::
* Frame objects::
* Traceback objects::
* Slice objects::
* Static method objects::
* Class method objects::

Code objects

* 特殊唯讀屬性: 特殊唯讀屬性<2>.
* 用於程式碼物件的方法::

Frame objects

* 特殊唯讀屬性: 特殊唯讀屬性<3>.
* 特殊可寫屬性: 特殊可寫屬性<2>.
* Frame object methods::

Special method names

* Basic customization::
* Customizing attribute access::
* Customizing class creation::
* Customizing instance and subclass checks::
* Emulating generic types::
* Emulating callable objects::
* Emulating container types::
* Emulating numeric types::
* With Statement Context Managers::
* Customizing positional arguments in class pattern matching::
* Emulating buffer types::
* Special method lookup::

Customizing attribute access

* Customizing module attribute access::
* Implementing Descriptors::
* Invoking Descriptors::
* __slots__: __slots__<2>.

Customizing class creation

* Metaclasses::
* Resolving MRO entries::
* Determining the appropriate metaclass::
* Preparing the class namespace::
* Executing the class body::
* Creating the class object::
* Uses for metaclasses::

Emulating generic types

* The purpose of __class_getitem__::
* __class_getitem__ versus __getitem__::

協程

* Awaitable Objects::
* Coroutine Objects::
* Asynchronous Iterators::
* Asynchronous Context Managers::

執行模型

* Structure of a program::
* Naming and binding::
* 例外::

Naming and binding

* Binding of names::
* Resolution of names::
* Annotation scopes::
* Lazy evaluation::
* Builtins and restricted execution::
* Interaction with dynamic features::

模組引入系統

* importlib: importlib<10>.
* 套件::
* Searching::
* Loading::
* The Path Based Finder::
* Replacing the standard import system::
* Package Relative Imports::
* Special considerations for __main__::
* References::

套件

* Regular packages::
* Namespace packages::

Searching

* The module cache::
* Finders and loaders::
* Import hooks::
* The meta path::

Loading

* Loaders::
* 子模組::
* Module spec::
* Import-related module attributes::
* module.__path__: module __path__.
* Module reprs::
* Cached bytecode invalidation::

The Path Based Finder

* Path entry finders::
* Path entry finder protocol::

Special considerations for __main__

* __main__.__spec__: __main__ __spec__.

運算式

* Arithmetic conversions::
* Atoms::
* Primaries::
* Await expression::
* The power operator::
* Unary arithmetic and bitwise operations::
* Binary arithmetic operations::
* Shifting operations::
* Binary bitwise operations::
* Comparisons::
* Boolean operations::
* Assignment expressions: Assignment expressions<2>.
* Conditional expressions::
* Lambdas::
* Expression lists::
* Evaluation order::
* Operator precedence::

Atoms

* Identifiers (Names): Identifiers Names.
* Literals: Literals<2>.
* Parenthesized forms::
* Displays for lists, sets and dictionaries: Displays for lists sets and dictionaries.
* List displays::
* Set displays::
* Dictionary displays::
* Generator expressions::
* Yield expressions::

Identifiers (Names)

* Private name mangling::

Yield expressions

* Generator-iterator methods::
* 模組: 模組<3>.
* Asynchronous generator functions: Asynchronous generator functions<2>.
* Asynchronous generator-iterator methods::

Primaries

* Attribute references::
* Subscriptions::
* Slicings::
* Calls::

Comparisons

* Value comparisons::
* Membership test operations::
* Identity comparisons::

簡單陳述式

* Expression statements::
* Assignment statements::
* assert 陳述式::
* pass 陳述式: pass 陳述式<2>.
* del 陳述式: del 陳述式<2>.
* return 陳述式::
* yield 陳述式::
* raise 陳述式::
* break 陳述式::
* continue 陳述式::
* import 陳述式::
* global 陳述式::
* nonlocal 陳述式::
* type 陳述式::

Assignment statements

* Augmented assignment statements::
* Annotated assignment statements::

import 陳述式

* Future statements::

複合陳述式

* The if statement::
* The while statement::
* The for statement::
* The try statement::
* The with statement::
* The match statement::
* 函式定義::
* 類別定義::
* 協程: 協程<2>.
* Type parameter lists::

The try statement

* except clause::
* except* 子句::
* else clause::
* finally clause::

The match statement

* Overview::
* Guards::
* Irrefutable Case Blocks::
* Patterns::

Patterns

* OR Patterns::
* AS Patterns::
* Literal Patterns::
* Capture Patterns::
* Wildcard Patterns::
* Value Patterns::
* Group Patterns::
* Sequence Patterns::
* Mapping Patterns::
* Class Patterns::

協程

* 協程函式定義::
* async for 陳述式::
* async with 陳述式::

Type parameter lists

* Generic functions::
* Generic classes::
* Generic type aliases::

最高層級元件

* 完整的 Python 程式::
* 檔案輸入::
* 互動式輸入::
* 運算式輸入::

Python 標準函式庫 (Standard Library)

* 簡介: 簡介<6>.
* 內建函式::
* 內建常數::
* 內建型別::
* 內建的例外::
* 文本處理 (Text Processing) 服務: 文本處理 Text Processing 服務.
* 二進位資料服務::
* 資料型別::
* 數值與數學模組::
* 函式編程模組::
* 檔案與目錄存取::
* 資料持久性 (Data Persistence): 資料持久性 Data Persistence.
* 資料壓縮與保存::
* 檔案格式::
* 加密服務::
* 通用作業系統服務::
* 並行執行 (Concurrent Execution): 並行執行 Concurrent Execution.
* Networking and Interprocess Communication::
* 網際網路資料處理::
* Structured Markup Processing Tools::
* 網路協定 (Internet protocols) 及支援: 網路協定 Internet protocols 及支援.
* 多媒體服務::
* 國際化::
* 程式框架::
* 以 Tk 打造圖形使用者介面 (Graphical User Interfaces): 以 Tk 打造圖形使用者介面 Graphical User Interfaces.
* 開發工具::
* 除錯與效能分析::
* 軟體封裝與發布::
* Python Runtime 服務::
* 自訂 Python 直譯器::
* 引入模組::
* Python 語言服務::
* MS Windows 特有服務::
* Unix 特有服務::
* 模組命令列介面::
* 已被取代的模組::
* 安全性注意事項: 安全性注意事項<4>.

簡介

* 可用性之註釋::

可用性之註釋

* WebAssembly 平台::
* iOS::

內建常數

* 由 site module（模組）所添增的常數::

內建型別

* 真值檢測::
* Boolean（布林）運算: Boolean（布林）運算 --- and or not. and, or, not
* 比較運算::
* 數值型別: 數值型別 --- int、float、complex. int、float、complex
* Boolean 型別 - bool::
* 疊代器型別::
* Sequence Types: Sequence Types --- list tuple range. list, tuple, range
* Text Sequence Type: Text Sequence Type --- str. str
* Binary Sequence Types: Binary Sequence Types --- bytes bytearray memoryview. bytes, bytearray, memoryview
* Set Types: Set Types --- set frozenset. set, frozenset
* Mapping Types: Mapping Types --- dict. dict
* 情境管理器型別::
* 型別註釋的型別: 型別註釋的型別 --- 泛型別名 Generic Alias 、聯合 Union. 泛型別名 (Generic Alias)、聯合 (Union)
* Other Built-in Types::
* 特殊屬性::
* Integer string conversion length limitation::

數值型別 -- int、float、complex

* 整數型別的位元運算::
* 整數型別的附加 methods::
* 浮點數的附加 methods::
* 數值型別的雜湊::

疊代器型別

* Generator Types::

Sequence Types -- list, tuple, range

* Common Sequence Operations::
* Immutable Sequence Types::
* Mutable Sequence Types::
* List（串列）: List（串列）<2>.
* Tuples::
* Ranges::

Text Sequence Type -- str

* String Methods: String Methods<2>.
* printf-style String Formatting::

Binary Sequence Types -- bytes, bytearray, memoryview

* Bytes Objects::
* Bytearray Objects::
* Bytes and Bytearray Operations::
* printf-style Bytes Formatting::
* Memory Views::

Mapping Types -- dict

* 字典視圖物件::

型別註釋的型別 -- 泛型別名 (Generic Alias)、聯合 (Union)

* 泛型別名型別::
* 聯合型別 (Union Type): 聯合型別 Union Type.

泛型別名型別

* 標準泛型類別::
* GenericAlias 物件的特殊屬性::

Other Built-in Types

* 模組: 模組<4>.
* Classes and Class Instances::
* 函式::
* Methods::
* Code Objects::
* Type Objects::
* The Null Object::
* The Ellipsis Object::
* NotImplemented 物件::
* Internal Objects::

Integer string conversion length limitation

* 受影響的 API::
* 設定限制::
* 建議的配置::

內建的例外

* 例外的情境::
* 繼承自內建的例外::
* 基底類別 (base classes): 基底類別 base classes.
* 實體例外::
* 警告::
* 例外群組::
* 例外階層::

實體例外

* 作業系統例外::

文本處理 (Text Processing) 服務

* string: string --- 常見的字串操作. 常見的字串操作
* re: re --- 正規表示式 regular expression 操作. 正規表示式 (regular expression) 操作
* difflib: difflib --- 計算差異的輔助工具. 計算差異的輔助工具
* textwrap: textwrap --- 文字包裝與填充. 文字包裝與填充
* unicodedata: unicodedata --- Unicode 資料庫. Unicode 資料庫
* stringprep: stringprep --- 網際網路字串準備. 網際網路字串準備
* readline: readline --- GNU readline 介面. GNU readline 介面
* rlcompleter: rlcompleter --- GNU readline 的補全函式. GNU readline 的補全函式

string -- 常見的字串操作

* 字串常數::
* 自訂字串格式::
* 格式化文字語法::
* 模板字串::
* 輔助函式::

格式化文字語法

* 格式規格 (Format Specification) 迷你語言: 格式規格 Format Specification 迷你語言.
* 格式範例::

re -- 正規表示式 (regular expression) 操作

* 正規表示式語法::
* 模組內容::
* Regular Expression Objects::
* Match Objects::
* Regular Expression Examples::

模組內容

* 旗標::
* Functions::
* Exceptions::

Regular Expression Examples

* Checking for a Pair::
* 模擬 scanf(): 模擬 scanf.
* search() vs. match(): search vs match.
* Making a Phonebook::
* Text Munging::
* Finding all Adverbs::
* Finding all Adverbs and their Positions::
* Raw String Notation::
* Writing a Tokenizer::

difflib -- 計算差異的輔助工具

* SequenceMatcher 物件::
* SequenceMatcher 範例::
* Differ Objects::
* Differ Example::
* A command-line interface to difflib::
* ndiff 範例：::

readline -- GNU readline 介面

* Init file::
* Line buffer::
* History file::
* History list::
* Startup hooks::
* Completion::
* 範例::

二進位資料服務

* struct: struct --- 將位元組直譯為打包起來的二進位資料. 將位元組直譯為打包起來的二進位資料
* codecs: codecs --- 編解碼器註冊表和基底類別. 編解碼器註冊表和基底類別

struct -- 將位元組直譯為打包起來的二進位資料

* 函式與例外::
* Format Strings::
* Applications::
* Classes: Classes<2>.

Format Strings

* Byte Order, Size, and Alignment: Byte Order Size and Alignment.
* Format Characters::
* 範例: 範例<2>.

Applications

* Native Formats::
* Standard Formats::

codecs -- 編解碼器註冊表和基底類別

* Codec Base Classes::
* Encodings and Unicode::
* Standard Encodings::
* Python Specific Encodings::
* encodings.idna: encodings idna --- Internationalized Domain Names in Applications. Internationalized Domain Names in Applications
* encodings.mbcs: encodings mbcs --- Windows ANSI codepage. Windows ANSI codepage
* encodings.utf_8_sig: encodings utf_8_sig --- UTF-8 codec with BOM signature. UTF-8 codec with BOM signature

Codec Base Classes

* Error Handlers::
* Stateless Encoding and Decoding::
* Incremental Encoding and Decoding::
* Stream Encoding and Decoding::

Incremental Encoding and Decoding

* IncrementalEncoder 物件::
* IncrementalDecoder 物件::

Stream Encoding and Decoding

* StreamWriter 物件::
* StreamReader 物件::
* StreamReaderWriter 物件::
* StreamRecoder 物件::

Python Specific Encodings

* Text Encodings::
* Binary Transforms::
* Text Transforms::

資料型別

* datetime: datetime --- 日期與時間的基本型別. 日期與時間的基本型別
* zoneinfo: zoneinfo --- IANA 時區支援. IANA 時區支援
* calendar: calendar --- 日曆相關函式. 日曆相關函式
* collections: collections --- 容器資料型態. 容器資料型態
* collections.abc: collections abc --- 容器的抽象基底類別. 容器的抽象基底類別
* heapq: heapq --- 堆積佇列 heap queue 演算法. 堆積佇列 (heap queue) 演算法
* bisect: bisect --- 陣列二分演算法 Array bisection algorithm. 陣列二分演算法 (Array bisection algorithm)
* array: array --- 高效率的數值型陣列. 高效率的數值型陣列
* weakref: weakref --- 弱參照. 弱參照
* types: types --- 動態型別建立與內建型別名稱. 動態型別建立與內建型別名稱
* copy: copy --- 淺層 shallow 和深層 deep 複製操作. 淺層 (shallow) 和深層 (deep) 複製操作
* pprint: pprint --- 資料美化列印器. 資料美化列印器
* reprlib: reprlib --- repr 的替代實作. repr() 的替代實作
* enum: enum --- 對列舉的支援. 對列舉的支援
* graphlib —- 使用類圖 (graph-like) 結構進行操作的功能: graphlib —-- 使用類圖 graph-like 結構進行操作的功能.

datetime -- 日期與時間的基本型別

* Aware and Naive Objects::
* 常數::
* Available Types::
* timedelta 物件::
* date 物件::
* datetime 物件::
* time 物件::
* tzinfo 物件::
* timezone 物件::
* strftime() 與 strptime() 的行為: strftime 與 strptime 的行為.

Available Types

* 常見屬性::
* Determining if an Object is Aware or Naive::

timedelta 物件

* 用法範例：timedelta::

date 物件

* 用法範例：date::

datetime 物件

* 用法範例：datetime::

time 物件

* 用法範例：time::

strftime() 與 strptime() 的行為

* strftime() 與 strptime() 格式碼: strftime 與 strptime 格式碼.
* 技術細節::

zoneinfo -- IANA 時區支援

* Using ZoneInfo::
* Data sources::
* The ZoneInfo class::
* 函式: 函式<2>.
* Globals::
* Exceptions and warnings::

Data sources

* Configuring the data sources::

Configuring the data sources

* Compile-time configuration::
* Environment configuration::
* Runtime configuration::

The ZoneInfo class

* String representations::
* Pickle serialization::

calendar -- 日曆相關函式

* 命令列用法::

collections -- 容器資料型態

* ChainMap 物件::
* Counter 物件::
* deque 物件::
* defaultdict 物件::
* namedtuple() 擁有具名欄位之 tuple 的工廠函式: namedtuple 擁有具名欄位之 tuple 的工廠函式.
* OrderedDict 物件::
* UserDict 物件::
* UserList 物件::
* UserString 物件::

ChainMap 物件

* ChainMap 範例和用法::

deque 物件

* deque 用法::

defaultdict 物件

* defaultdict 範例::

OrderedDict 物件

* OrderedDict 範例與用法::

collections.abc -- 容器的抽象基底類別

* Collections Abstract Base Classes::
* Collections Abstract Base Classes: Collections Abstract Base Classes -- Detailed Descriptions. Detailed Descriptions
* Examples and Recipes::

heapq -- 堆積佇列 (heap queue) 演算法

* 基礎範例::
* 優先佇列實作細節::
* 原理::

bisect -- 陣列二分演算法 (Array bisection algorithm)

* 效能考量::
* 搜尋一個已排序的 list::
* 範例: 範例<3>.

weakref -- 弱參照

* 弱參照物件::
* 範例: 範例<4>.
* 最終化器物件::
* 最終化器與 __del__() 方法的比較: 最終化器與 __del__ 方法的比較.

types -- 動態型別建立與內建型別名稱

* Dynamic Type Creation::
* Standard Interpreter Types::
* Additional Utility Classes and Functions::
* Coroutine Utility Functions::

pprint -- 資料美化列印器

* 函式: 函式<3>.
* PrettyPrinter 物件::
* 範例: 範例<5>.

reprlib -- repr() 的替代實作

* Repr 物件::
* Subclassing Repr Objects::

enum -- 對列舉的支援

* 模組內容: 模組內容<2>.
* 資料型別: 資料型別<2>.
* 通用項目與裝飾器::
* 備註::

資料型別

* 支援 __dunder__ 名稱::
* 支援 _sunder_ 名稱::

graphlib —- 使用類圖 (graph-like) 結構進行操作的功能

* 例外: 例外<2>.

數值與數學模組

* numbers: numbers --- 數值的抽象基底類別. 數值的抽象基底類別
* math: math --- 數學函式. 數學函式
* cmath: cmath --- 複數的數學函式. 複數的數學函式
* decimal: decimal --- 十進位固定點和浮點運算. 十進位固定點和浮點運算
* fractions: fractions --- 有理數. 有理數
* random: random --- 生成偽隨機數. 生成偽隨機數
* statistics: statistics --- 數學統計函式. 數學統計函式

numbers -- 數值的抽象基底類別

* 數值的階層::
* 給型別實作者的註記::

給型別實作者的註記

* 加入更多數值 ABC::
* 實作算術操作::

math -- 數學函式

* 數論與表現函式::
* Power and logarithmic functions::
* Trigonometric functions::
* Angular conversion::
* Hyperbolic functions::
* Special functions::
* 常數: 常數<2>.

cmath -- 複數的數學函式

* 轉換到極座標和從極座標做轉換::
* 冪函數和對數函數::
* 三角函數::
* 雙曲函數::
* 分類函式::
* 常數: 常數<3>.

decimal -- 十進位固定點和浮點運算

* Quick-start Tutorial::
* Decimal objects::
* Context objects::
* 常數: 常數<4>.
* Rounding modes::
* Signals::
* Floating-Point Notes::
* Working with threads::
* Recipes::
* Decimal FAQ::

Decimal objects

* Logical operands::

Floating-Point Notes

* Mitigating round-off error with increased precision::
* 特殊值::

random -- 生成偽隨機數

* 簿記函式 (bookkeeping functions): 簿記函式 bookkeeping functions.
* 回傳位元組的函式::
* 回傳整數的函式::
* 回傳序列的函式::
* 離散分布::
* 實數分布::
* 替代產生器::
* 關於 Reproducibility（復現性）的注意事項::
* 範例: 範例<6>.
* 使用方案::
* Command-line usage::
* Command-line example::

statistics -- 數學統計函式

* 平均值與中央位置量數::
* 離度 (spread) 的測量: 離度 spread 的測量.
* 兩個輸入之間的關係統計::
* 函式細節::
* 例外: 例外<3>.
* NormalDist 物件::
* 範例與錦囊妙計::

範例與錦囊妙計

* 經典機率問題::
* 用於模擬的蒙地卡羅 (Monte Carlo) 輸入: 用於模擬的蒙地卡羅 Monte Carlo 輸入.
* 近似二項分布::
* 單純貝氏分類器 (Naive bayesian classifier): 單純貝氏分類器 Naive bayesian classifier.

函式編程模組

* itertools: itertools --- 建立產生高效率迴圈之疊代器的函式. 建立產生高效率迴圈之疊代器的函式
* functools: functools --- 可呼叫物件上的高階函式與操作. 可呼叫物件上的高階函式與操作
* operator: operator --- 標準運算子替代函式. 標準運算子替代函式

itertools -- 建立產生高效率迴圈之疊代器的函式

* Itertool 函式::
* Itertools 應用技巧::

functools -- 可呼叫物件上的高階函式與操作

* partial 物件::

operator -- 標準運算子替代函式

* 運算子與函式間的對映::
* 原地 (in-place) 運算子: 原地 in-place 運算子.

檔案與目錄存取

* pathlib: pathlib --- 物件導向檔案系統路徑. 物件導向檔案系統路徑
* os.path: os path --- 常見的路徑名操作. 常見的路徑名操作
* fileinput: fileinput --- 逐列疊代多個輸入串流. 逐列疊代多個輸入串流
* stat: stat --- 直譯 stat 的結果. 直譯 stat() 的結果
* filecmp: filecmp --- 檔案與目錄比較. 檔案與目錄比較
* tempfile: tempfile --- 生成臨時檔案和目錄. 生成臨時檔案和目錄
* glob: glob --- Unix 風格的路徑名稱模式擴展. Unix 風格的路徑名稱模式擴展
* fnmatch: fnmatch --- Unix 檔案名稱模式比對. Unix 檔案名稱模式比對
* linecache: linecache --- 隨機存取文字列. 隨機存取文字列
* shutil — 高階檔案操作::

pathlib -- 物件導向檔案系統路徑

* 基本用法::
* Exceptions: Exceptions<2>.
* 純路徑::
* 實體路徑::
* Pattern language::
* Comparison to the glob module::
* Comparison to the os and os.path modules: Comparison to the os and os path modules.

純路徑

* 通用屬性::
* 運算子::
* 對個別組成的存取::
* 方法與屬性::

實體路徑

* Parsing and generating URIs::
* Expanding and resolving paths::
* Querying file type and status::
* Reading and writing files::
* 讀取目錄::
* 建立檔案與目錄::
* Renaming and deleting::
* Permissions and ownership::

Comparison to the os and os.path modules

* Corresponding tools::

filecmp -- 檔案與目錄比較

* The dircmp class::

tempfile -- 生成臨時檔案和目錄

* 範例: 範例<7>.
* 已棄用的函式和變數::

glob -- Unix 風格的路徑名稱模式擴展

* Examples::

shutil — 高階檔案操作

* Directory and files operations::
* Archiving operations::
* Querying the size of the output terminal::

Directory and files operations

* Platform-dependent efficient copy operations::
* copytree example::
* rmtree 範例::

Archiving operations

* Archiving example::
* Archiving example with base_dir::

資料持久性 (Data Persistence)

* pickle: pickle --- Python 物件序列化. Python 物件序列化
* copyreg: copyreg --- 註冊 pickle 支援函式. 註冊 pickle 支援函式
* shelve: shelve --- Python object persistence. Python object persistence
* marshal: marshal --- 内部 Python 物件序列化. 内部 Python 物件序列化
* dbm: dbm --- Unix "databases" 的介面. Unix "databases" 的介面
* sqlite3: sqlite3 --- SQLite 資料庫的 DB-API 2 0 介面. SQLite 資料庫的 DB-API 2.0 介面

pickle -- Python 物件序列化

* 和其他 Python 模組的關係::
* Data stream format::
* 模組介面::
* What can be pickled and unpickled?::
* Pickling Class Instances::
* Custom Reduction for Types, Functions, and Other Objects: Custom Reduction for Types Functions and Other Objects.
* Out-of-band Buffers::
* Restricting Globals::
* Performance: Performance<2>.
* 範例: 範例<9>.

和其他 Python 模組的關係

* 和 marshal 的比較::
* 和 json 的比較::

Pickling Class Instances

* Persistence of External Objects::
* Dispatch Tables::
* Handling Stateful Objects::

Out-of-band Buffers

* Provider API::
* Consumer API::
* 範例: 範例<8>.

copyreg -- 註冊 pickle 支援函式

* 範例: 範例<10>.

shelve -- Python object persistence

* Restrictions::
* 範例: 範例<11>.

dbm -- Unix "databases" 的介面

* dbm.sqlite3: dbm sqlite3 --- SQLite backend for dbm. SQLite backend for dbm
* dbm.gnu: dbm gnu --- GNU 資料庫管理器. GNU 資料庫管理器
* dbm.ndbm: dbm ndbm --- 新資料庫管理器. 新資料庫管理器
* dbm.dumb: dbm dumb --- 可攜式 DBM 實作. 可攜式 DBM 實作

sqlite3 -- SQLite 資料庫的 DB-API 2.0 介面

* 教學::
* Reference::
* How-to guides::
* 解釋::

Reference

* Module functions::
* Module constants::
* Connection 物件::
* Cursor 物件::
* Row 物件::
* Blob 物件::
* PrepareProtocol 物件::
* 例外: 例外<4>.
* SQLite and Python types::
* Default adapters and converters (deprecated): Default adapters and converters deprecated.
* 命令列介面::

How-to guides

* How to use placeholders to bind values in SQL queries::
* How to adapt custom Python types to SQLite values::
* How to convert SQLite values to custom Python types::
* Adapter and converter recipes::
* How to use connection shortcut methods::
* How to use the connection context manager::
* How to work with SQLite URIs::
* How to create and use row factories::
* How to handle non-UTF-8 text encodings::

How to adapt custom Python types to SQLite values

* How to write adaptable objects::
* How to register adapter callables::

解釋

* Transaction control::

Transaction control

* Transaction control via the autocommit attribute::
* Transaction control via the isolation_level attribute::

資料壓縮與保存

* zlib: zlib --- 相容於 gzip 的壓縮. 相容於 gzip 的壓縮
* gzip: gzip --- gzip 檔案的支援. gzip 檔案的支援
* bz2: bz2 --- bzip2 壓縮的支援. bzip2 壓縮的支援
* lzma: lzma --- 使用 LZMA 演算法進行壓縮. 使用 LZMA 演算法進行壓縮
* zipfile: zipfile --- 處理 ZIP 封存檔案. 處理 ZIP 封存檔案
* tarfile: tarfile --- 讀取與寫入 tar 封存檔案. 讀取與寫入 tar 封存檔案

gzip -- gzip 檔案的支援

* 用法範例::
* 命令列介面: 命令列介面<2>.

命令列介面

* 命令列選項::

bz2 -- bzip2 壓縮的支援

* (De)compression of files: De compression of files.
* Incremental (de)compression: Incremental de compression.
* One-shot (de)compression: One-shot de compression.
* 用法範例: 用法範例<2>.

lzma -- 使用 LZMA 演算法進行壓縮

* Reading and writing compressed files::
* Compressing and decompressing data in memory::
* Miscellaneous::
* Specifying custom filter chains::
* 範例: 範例<12>.

zipfile -- 處理 ZIP 封存檔案

* ZipFile 物件::
* Path Objects::
* PyZipFile 物件::
* ZipInfo 物件::
* Command-Line Interface::
* Decompression pitfalls::

Command-Line Interface

* Command-line options::

Decompression pitfalls

* From file itself::
* File System limitations::
* Resources limitations::
* Interruption::
* Default behaviors of extraction::

tarfile -- 讀取與寫入 tar 封存檔案

* TarFile 物件::
* TarInfo 物件::
* Extraction filters::
* Command-Line Interface: Command-Line Interface<2>.
* 範例: 範例<13>.
* Supported tar formats::
* Unicode issues::

Extraction filters

* Default named filters::
* Filter errors::
* Hints for further verification::
* Supporting older Python versions::
* Stateful extraction filter example::

Command-Line Interface

* 命令列選項: 命令列選項<2>.

檔案格式

* csv: csv --- CSV 檔案讀取及寫入. CSV 檔案讀取及寫入
* configparser: configparser --- 設定檔剖析器. 設定檔剖析器
* tomllib: tomllib --- 剖析 TOML 檔案. 剖析 TOML 檔案
* netrc: netrc --- netrc 檔案處理. netrc 檔案處理
* plistlib: plistlib --- 產生和剖析 Apple plist 檔案. 產生和剖析 Apple .plist 檔案

csv -- CSV 檔案讀取及寫入

* 模組內容: 模組內容<3>.
* Dialect 與格式參數::
* 讀取器物件::
* 寫入器物件::
* 範例: 範例<14>.

configparser -- 設定檔剖析器

* Quick Start::
* Supported Datatypes::
* Fallback Values::
* Supported INI File Structure::
* Unnamed Sections::
* Interpolation of values::
* Mapping Protocol Access::
* Customizing Parser Behaviour::
* Legacy API Examples::
* ConfigParser 物件::
* RawConfigParser 物件::
* 例外: 例外<5>.

tomllib -- 剖析 TOML 檔案

* 範例: 範例<15>.
* 轉換表::

netrc -- netrc 檔案處理

* netrc 物件::

plistlib -- 產生和剖析 Apple .plist 檔案

* 範例: 範例<16>.

加密服務

* hashlib: hashlib --- 安全雜湊與訊息摘要. 安全雜湊與訊息摘要
* hmac: hmac --- 基於金鑰雜湊的訊息驗證. 基於金鑰雜湊的訊息驗證
* secrets: secrets --- 產生用於管理機密的安全亂數. 產生用於管理機密的安全亂數

hashlib -- 安全雜湊與訊息摘要

* 雜湊演算法::
* 用法::
* 建構函式::
* 屬性::
* 雜湊物件::
* SHAKE 可變長度摘要::
* 檔案雜湊::
* 密鑰的生成::
* BLAKE2::

BLAKE2

* 建立雜湊物件::
* 常數: 常數<5>.
* 範例: 範例<17>.
* 製作人員::

範例

* 簡單雜湊::
* 使用不同的摘要大小::
* 密鑰雜湊 (Keyed hashing): 密鑰雜湊 Keyed hashing.
* 隨機雜湊 (Randomized hashing): 隨機雜湊 Randomized hashing.
* 個人化::
* 樹狀模式::

secrets -- 產生用於管理機密的安全亂數

* 亂數::
* 產生權杖（token）::
* 其他函式::
* 應用技巧和典範實務（best practices）::

產生權杖（token）

* 權杖應當使用多少個位元組？::

通用作業系統服務

* os: os --- 各種作業系統介面. 各種作業系統介面
* io — 處理資料串流的核心工具::
* time: time --- 時間存取與轉換. 時間存取與轉換
* argparse: argparse --- Parser for command-line options arguments and sub-commands. Parser for command-line options, arguments and sub-
                        commands
* logging: logging --- Python 的日誌記錄工具. Python 的日誌記錄工具
* logging.config: logging config --- 日誌記錄配置. 日誌記錄配置
* logging.handlers: logging handlers --- 日誌紀錄處理器. 日誌紀錄處理器
* getpass: getpass --- 可攜式密碼輸入工具. 可攜式密碼輸入工具
* curses: curses --- 字元儲存格顯示的終端處理. 字元儲存格顯示的終端處理
* curses.textpad: curses textpad --- Text input widget for curses programs. Text input widget for curses programs
* curses.ascii: curses ascii --- ASCII 字元的工具程式. ASCII 字元的工具程式
* curses.panel: curses panel --- curses 的面板堆疊擴充. curses 的面板堆疊擴充
* platform: platform --- 對底層平臺識別資料的存取. 對底層平臺識別資料的存取
* errno: errno --- 標準 errno 系統符號. 標準 errno 系統符號
* ctypes: ctypes --- 用於 Python 的外部函式庫. 用於 Python 的外部函式庫

os -- 各種作業系統介面

* File Names, Command Line Arguments, and Environment Variables: File Names Command Line Arguments and Environment Variables.
* Python UTF-8 模式::
* 行程參數::
* File Object Creation::
* File Descriptor Operations::
* Files and Directories::
* 行程管理::
* Interface to the scheduler::
* Miscellaneous System Information::
* Random numbers::

File Descriptor Operations

* Querying the size of a terminal::
* Inheritance of File Descriptors::

Files and Directories

* Timer File Descriptors::
* Linux extended attributes::

io — 處理資料串流的核心工具

* 總覽::
* 文字編碼::
* 高階模組介面::
* 類別階層::
* Performance: Performance<3>.

總覽

* 文字 I/O::
* 二進位 (Binary) I/O: 二進位 Binary I/O.
* 原始 (Raw) I/O: 原始 Raw I/O.

文字編碼

* 選擇性加入的編碼警告::

類別階層

* I/O 基礎類別::
* 原始檔案 I/O::
* Buffered Streams::
* 文字 I/O: 文字 I/O<2>.

Performance

* 二進位 (Binary) I/O: 二進位 Binary I/O<2>.
* 文字 I/O: 文字 I/O<3>.
* Multi-threading: Multi-threading<2>.
* Reentrancy::

time -- 時間存取與轉換

* 函式: 函式<4>.
* Clock ID Constants::
* Timezone Constants::

argparse -- Parser for command-line options, arguments and sub-commands

* Core Functionality::
* Quick Links for add_argument(): Quick Links for add_argument.
* 範例: 範例<18>.
* ArgumentParser 物件::
* The add_argument() method: The add_argument method.
* The parse_args() method: The parse_args method.
* Other utilities::
* Upgrading optparse code::
* Exceptions: Exceptions<3>.

範例

* 建立一個剖析器::
* 增加引數::
* 剖析引數::

ArgumentParser 物件

* prog::
* usage::
* 描述::
* epilog::
* parents::
* formatter_class::
* prefix_chars::
* fromfile_prefix_chars::
* argument_default::
* allow_abbrev::
* conflict_handler::
* add_help::
* exit_on_error::

The add_argument() method

* name or flags::
* action::
* nargs::
* const::
* default::
* type::
* choices::
* required::
* 幫助::
* metavar::
* dest::
* deprecated::
* Action classes::

The parse_args() method

* Option value syntax::
* Invalid arguments::
* Arguments containing -::
* Argument abbreviations (prefix matching): Argument abbreviations prefix matching.
* Beyond sys.argv: Beyond sys argv.
* The Namespace object::

Other utilities

* Sub-commands::
* FileType 物件::
* Argument groups::
* Mutual exclusion::
* Parser defaults::
* Printing help::
* Partial parsing::
* Customizing file parsing::
* Exiting methods::
* Intermixed parsing::

logging -- Python 的日誌記錄工具

* Logger 物件::
* Logging Levels::
* Handler Objects::
* Formatter Objects::
* Filter Objects::
* LogRecord 物件::
* LogRecord attributes::
* LoggerAdapter 物件::
* Thread Safety::
* Module-Level Functions::
* Module-Level Attributes::
* Integration with the warnings module::

logging.config -- 日誌記錄配置

* Configuration functions::
* Security considerations::
* Configuration dictionary schema::
* Configuration file format::

Configuration dictionary schema

* Dictionary Schema Details::
* Incremental Configuration::
* Object connections::
* User-defined objects::
* Handler configuration order::
* Access to external objects::
* Access to internal objects::
* Import resolution and custom importers::
* Configuring QueueHandler and QueueListener::

logging.handlers -- 日誌紀錄處理器

* StreamHandler::
* FileHandler::
* NullHandler::
* WatchedFileHandler::
* BaseRotatingHandler::
* RotatingFileHandler::
* TimedRotatingFileHandler::
* SocketHandler::
* DatagramHandler::
* SysLogHandler::
* NTEventLogHandler::
* SMTPHandler::
* MemoryHandler::
* HTTPHandler::
* QueueHandler::
* QueueListener::

curses -- 字元儲存格顯示的終端處理

* 函式: 函式<5>.
* Window Objects::
* Constants::

curses.textpad -- Text input widget for curses programs

* Textbox objects::

curses.panel -- curses 的面板堆疊擴充

* 函式: 函式<6>.
* Panel Objects::

platform --  對底層平臺識別資料的存取

* 跨平台::
* Java 平台::
* Windows 平台::
* macOS 平台::
* iOS Platform::
* Unix 平台::
* Linux 平台::
* Android Platform::

ctypes -- 用於 Python 的外部函式庫

* ctypes 教學::
* ctypes reference::

ctypes 教學

* Loading dynamic link libraries::
* Accessing functions from loaded dlls::
* 呼叫函式::
* Fundamental data types::
* Calling functions, continued: Calling functions continued.
* Calling variadic functions::
* Calling functions with your own custom data types::
* Specifying the required argument types (function prototypes): Specifying the required argument types function prototypes.
* Return types::
* Passing pointers (or; passing parameters by reference): Passing pointers or passing parameters by reference.
* Structures and unions::
* Structure/union alignment and byte order::
* Bit fields in structures and unions::
* Arrays::
* Pointers::
* Type conversions::
* Incomplete Types::
* 回呼函式::
* Accessing values exported from dlls::
* Surprises::
* Variable-sized data types::

ctypes reference

* Finding shared libraries::
* Loading shared libraries::
* Foreign functions::
* Function prototypes::
* Utility functions::
* Data types::
* Fundamental data types: Fundamental data types<2>.
* Structured data types::
* Arrays and pointers::

並行執行 (Concurrent Execution)

* threading: threading --- 基於執行緒的平行性. 基於執行緒的平行性
* multiprocessing: multiprocessing --- 以行程為基礎的平行性. 以行程為基礎的平行性
* multiprocessing.shared_memory: multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取. 對於共享記憶體的跨行程直接存取
* concurrent 套件::
* concurrent.futures: concurrent futures --- 啟動平行任務. 啟動平行任務
* subprocess: subprocess --- 子行程管理. 子行程管理
* sched: sched --- 事件排程器. 事件排程器
* queue: queue --- 同步佇列 synchronized queue 類別. 同步佇列 (synchronized queue) 類別
* contextvars: contextvars --- 情境變數. 情境變數
* _thread: _thread --- 低階執行緒 API. 低階執行緒 API

threading -- 基於執行緒的平行性

* Thread-Local Data::
* Thread Objects::
* Lock Objects::
* RLock 物件::
* Condition Objects::
* Semaphore Objects::
* Event Objects::
* Timer Objects::
* Barrier Objects::
* Using locks, conditions, and semaphores in the with statement: Using locks conditions and semaphores in the with statement.

Semaphore Objects

* Semaphore 範例::

multiprocessing -- 以行程為基礎的平行性

* 簡介: 簡介<7>.
* Reference: Reference<2>.
* Programming guidelines::
* 範例: 範例<19>.

簡介

* Process 類別::
* Contexts and start methods::
* Exchanging objects between processes::
* Synchronization between processes::
* Sharing state between processes::
* Using a pool of workers::

Reference

* Process 與例外::
* Pipes and Queues::
* Miscellaneous: Miscellaneous<2>.
* Connection Objects::
* Synchronization primitives::
* 共享的 ctypes 物件::
* Managers::
* Proxy Objects::
* Process Pools::
* Listeners and Clients::
* Authentication keys::
* Logging::
* multiprocessing.dummy 模組: multiprocessing dummy 模組.

共享的 ctypes 物件

* multiprocessing.sharedctypes 模組: multiprocessing sharedctypes 模組.

Managers

* Customized managers::
* Using a remote manager::

Proxy Objects

* Cleanup::

Listeners and Clients

* Address Formats::

Programming guidelines

* All start methods::
* The spawn and forkserver start methods::

concurrent.futures -- 啟動平行任務

* Executor 物件::
* ThreadPoolExecutor::
* ProcessPoolExecutor::
* Future 物件::
* 模組函式::
* 例外類別::

ThreadPoolExecutor

* ThreadPoolExecutor 範例::

ProcessPoolExecutor

* ProcessPoolExecutor 範例::

subprocess -- 子行程管理

* Using the subprocess Module::
* 安全性注意事項::
* Popen Objects::
* Windows Popen Helpers::
* Older high-level API::
* Replacing Older Functions with the subprocess Module::
* Legacy Shell Invocation Functions::
* 註解::

Using the subprocess Module

* Frequently Used Arguments::
* Popen Constructor::
* 例外: 例外<6>.

Windows Popen Helpers

* Windows Constants::

Replacing Older Functions with the subprocess Module

* Replacing /bin/sh shell command substitution::
* Replacing shell pipeline::
* Replacing os.system(): Replacing os system.
* Replacing the os.spawn family: Replacing the os spawn family.
* Replacing os.popen(), os.popen2(), os.popen3(): Replacing os popen os popen2 os popen3.
* Replacing functions from the popen2 module::

註解

* Converting an argument sequence to a string on Windows::
* 停用 vfork() 或 posix_spawn(): 停用 vfork 或 posix_spawn.

sched -- 事件排程器

* 排程器物件::

queue -- 同步佇列 (synchronized queue) 類別

* 佇列物件::
* SimpleQueue 物件::

佇列物件

* Terminating queues::

contextvars -- 情境變數

* Context Variables::
* Manual Context Management::
* asyncio support::

Networking and Interprocess Communication

* asyncio: asyncio --- 非同步 I/O. 非同步 I/O
* socket: socket --- 低階網路介面. 低階網路介面
* ssl: ssl --- socket 物件的 TLS/SSL 包裝器. socket 物件的 TLS/SSL 包裝器
* select: select --- 等待 I/O 完成. 等待 I/O 完成
* selectors: selectors --- 高階 I/O 多工. 高階 I/O 多工
* signal: signal --- 設定非同步事件的處理函式. 設定非同步事件的處理函式
* mmap: mmap --- 記憶體映射檔案的支援. 記憶體映射檔案的支援

asyncio -- 非同步 I/O

* Runners (執行器): Runners 執行器.
* 協程與任務::
* 串流::
* 同步化原始物件 (Synchronization Primitives): 同步化原始物件 Synchronization Primitives.
* 子行程::
* 佇列 (Queues): 佇列 Queues.
* 例外: 例外<8>.
* 事件迴圈::
* Futures::
* 傳輸與協定::
* Policies::
* 平臺支援::
* 擴充::
* 高階 API 索引::
* 低階 API 索引::
* 使用 asyncio 開發::

Runners (執行器)

* 運行一個 asyncio 程式::
* Runner context manager::
* Handling Keyboard Interruption::

協程與任務

* 協程: 協程<3>.
* Awaitables::
* Creating Tasks::
* Task Cancellation::
* Task Groups::
* Sleeping::
* Running Tasks Concurrently::
* Eager Task Factory::
* Shielding From Cancellation::
* Timeouts::
* Waiting Primitives::
* Running in Threads::
* Scheduling From Other Threads::
* Introspection::
* Task Object::

串流

* StreamReader::
* StreamWriter::
* 範例: 範例<20>.

範例

* 使用串流的 TCP echo 客戶端::
* 使用串流的 TCP echo 伺服器::
* 獲取 HTTP 標頭::
* 註冊一個使用串流來等待資料的開放 socket::

同步化原始物件 (Synchronization Primitives)

* Lock::
* Event::
* Condition::
* Semaphore::
* BoundedSemaphore::
* Barrier::

子行程

* 建立子行程::
* 常數: 常數<6>.
* Interacting with Subprocesses::

Interacting with Subprocesses

* 子行程與線程::
* 範例: 範例<21>.

佇列 (Queues)

* Queue::
* Priority Queue（優先佇列）::
* LIFO Queue::
* 例外: 例外<7>.
* 範例: 範例<22>.

事件迴圈

* 事件迴圈方法::
* 回呼處理::
* Server 物件::
* 事件迴圈實作::
* 範例: 範例<23>.

事件迴圈方法

* 啟動和停止迴圈::
* 排程回呼函式::
* 排程延遲的回呼函式::
* 建立 Futures 和 Tasks::
* 打開網路連線::
* 建立網路伺服器::
* 傳輸檔案::
* TLS 升級::
* 監視檔案描述器::
* 直接使用 socket 物件::
* DNS::
* 使用管道::
* Unix 訊號::
* 在執行緒池或行程池中執行程式碼::
* 錯誤處理 API::
* 啟用除錯模式::
* 運行子行程::

範例

* 使用 call_soon() 的 Hello World 範例: 使用 call_soon 的 Hello World 範例.
* 使用 call_later() 顯示目前日期: 使用 call_later 顯示目前日期.
* 監聽檔案描述器以進行讀取事件::
* 設定 SIGINT 和 SIGTERM 的訊號處理程式::

Futures

* Future 函式::
* Future 物件: Future 物件<2>.

傳輸與協定

* Transports::
* Protocols::
* 範例: 範例<24>.

Transports

* Transports Hierarchy::
* Base Transport::
* Read-only Transports::
* Write-only Transports::
* Datagram Transports::
* Subprocess Transports::

Protocols

* Base Protocols::
* Base Protocol::
* Streaming Protocols::
* Buffered Streaming Protocols::
* Datagram Protocols::
* Subprocess Protocols::

範例

* TCP Echo Server::
* TCP Echo Client::
* UDP Echo Server::
* UDP Echo Client::
* Connecting Existing Sockets::
* loop.subprocess_exec() and SubprocessProtocol: loop subprocess_exec and SubprocessProtocol.

Policies

* Getting and Setting the Policy::
* Policy Objects::
* Process Watchers::
* Custom Policies::

平臺支援

* 所有平台::
* Windows: Windows<72>.
* macOS: macOS<45>.

Windows

* Windows 的子行程支援::

擴充

* Writing a Custom Event Loop::
* Future and Task private constructors::
* Task lifetime support::

高階 API 索引

* 任務 (Tasks): 任務 Tasks.
* 佇列 (Queues): 佇列 Queues<2>.
* 子行程 (Subprocesses): 子行程 Subprocesses.
* 串流 (Streams): 串流 Streams.
* 同步化 (Synchronization): 同步化 Synchronization.
* 例外: 例外<9>.

低階 API 索引

* 獲取事件迴圈::
* 事件迴圈方法: 事件迴圈方法<2>.
* 傳輸::
* 協定::
* 事件迴圈 Policies::

使用 asyncio 開發

* 除錯模式::
* 並行性和多執行緒 (Concurrency and Multithreading): 並行性和多執行緒 Concurrency and Multithreading.
* 執行阻塞的程式::
* 日誌記錄::
* 偵測從未被等待的 (never-awaited) 協程: 偵測從未被等待的 never-awaited 協程.
* 偵測從未被獲取的 (never-retrieved) 例外: 偵測從未被獲取的 never-retrieved 例外.

socket -- 低階網路介面

* Socket 系列家族::
* 模組內容: 模組內容<4>.
* Socket 物件::
* Notes on socket timeouts::
* 範例: 範例<25>.

模組內容

* 例外: 例外<10>.
* 常數: 常數<7>.
* 函式: 函式<7>.

函式

* 建立 sockets::
* 其他函式: 其他函式<2>.

Notes on socket timeouts

* Timeouts and the connect method::
* Timeouts and the accept method::

ssl -- socket 物件的 TLS/SSL 包裝器

* 函式、常數與例外::
* SSL Sockets::
* SSL Contexts::
* Certificates::
* 範例: 範例<26>.
* Notes on non-blocking sockets::
* Memory BIO Support: Memory BIO Support<2>.
* SSL session::
* Security considerations: Security considerations<2>.
* TLS 1.3: TLS 1 3.

函式、常數與例外

* Socket 建立::
* 語境建立::
* 例外: 例外<11>.
* 隨機產生::
* 認證處理::
* 常數: 常數<8>.

Certificates

* Certificate chains::
* CA certificates::
* Combined key and certificate::
* Self-signed certificates::

範例

* Testing for SSL support::
* Client-side operation::
* Server-side operation::

Security considerations

* Best defaults::
* 手動設定::
* Multi-processing::

手動設定

* 驗證憑證::
* 協定版本::
* Cipher selection::

select -- 等待 I/O 完成

* /dev/poll Polling Objects::
* Edge and Level Trigger Polling (epoll) Objects: Edge and Level Trigger Polling epoll Objects.
* Polling Objects::
* Kqueue Objects::
* Kevent Objects::

selectors -- 高階 I/O 多工

* 簡介: 簡介<8>.
* Classes: Classes<3>.
* 範例: 範例<27>.

signal -- 設定非同步事件的處理函式

* General rules::
* 模組內容: 模組內容<5>.
* 範例: 範例<28>.
* Note on SIGPIPE::
* Note on Signal Handlers and Exceptions::

General rules

* Execution of Python signal handlers::
* Signals and threads::

mmap -- 記憶體映射檔案的支援

* MADV_* Constants::
* MAP_* 常數::

網際網路資料處理

* email: email --- 郵件和 MIME 處理套件. 郵件和 MIME 處理套件
* json: json --- JSON 編碼器與解碼器. JSON 編碼器與解碼器
* mailbox: mailbox --- 以各種格式操作郵件信箱. 以各種格式操作郵件信箱
* mimetypes: mimetypes --- 將檔案名稱對映到 MIME 類型. 將檔案名稱對映到 MIME 類型
* base64: base64 --- Base16、Base32、Base64、Base85 資料編碼. Base16、Base32、Base64、Base85 資料編碼
* binascii: binascii --- 在二進位制和 ASCII 之間轉換. 在二進位制和 ASCII 之間轉換
* quopri: quopri --- 編碼和解碼 MIME 可列印字元資料. 編碼和解碼 MIME 可列印字元資料

email -- 郵件和 MIME 處理套件

* email.message：表示電子郵件訊息: email message：表示電子郵件訊息.
* email.parser：剖析電子郵件訊息: email parser：剖析電子郵件訊息.
* email.generator：產生 MIME 文件: email generator：產生 MIME 文件.
* email.policy; Policy Objects: email policy Policy Objects.
* email.errors：例外和缺陷類別: email errors：例外和缺陷類別.
* email.headerregistry：自訂標頭物件: email headerregistry：自訂標頭物件.
* email.contentmanager：管理 MIME 內容: email contentmanager：管理 MIME 內容.
* email：範例::
* email.message.Message; Representing an email message using the compat32 API: email message Message Representing an email message using the compat32 API.
* email.mime：從頭開始建立電子郵件和 MIME 物件: email mime：從頭開始建立電子郵件和 MIME 物件.
* email.header：國際化標頭: email header：國際化標頭.
* email.charset：表示字元集合: email charset：表示字元集合.
* email.encoders：編碼器: email encoders：編碼器.
* email.utils：雜項工具: email utils：雜項工具.
* email.iterators：疊代器: email iterators：疊代器.

email.parser：剖析電子郵件訊息

* FeedParser API::
* Parser API::
* Additional notes::

email.contentmanager：管理 MIME 內容

* Content Manager Instances::

json -- JSON 編碼器與解碼器

* 基本用法: 基本用法<2>.
* 編碼器與解碼器::
* 例外: 例外<12>.
* 合規性與互通性（Interoperability）::
* 命令列介面: 命令列介面<3>.

合規性與互通性（Interoperability）

* 字元編碼格式::
* 正負無限與非數值::
* 物件內重複的名稱::
* 位於頂層的非物件及非列表值::
* 實作限制::

命令列介面

* 命令列選項: 命令列選項<3>.

mailbox -- 以各種格式操作郵件信箱

* Mailbox 物件::
* Message 物件::
* 例外: 例外<13>.
* 範例: 範例<29>.

Mailbox 物件

* Mailbox 物件: Mailbox 物件<2>.
* mbox 物件::
* MH 物件::
* Babyl 物件::
* MMDF 物件::

Message 物件

* MaildirMessage 物件::
* mboxMessage 物件::
* MHMessage 物件::
* BabylMessage 物件::
* MMDFMessage 物件::

mimetypes -- 將檔案名稱對映到 MIME 類型

* MimeTypes 物件::

base64 -- Base16、Base32、Base64、Base85 資料編碼

* 安全性注意事項: 安全性注意事項<2>.

Structured Markup Processing Tools

* html: html --- 超連結標記語言 HTML 支援. 超連結標記語言 (HTML) 支援
* html.parser: html parser --- 簡單的 HTML 和 XHTML 剖析器. 簡單的 HTML 和 XHTML 剖析器
* html.entities: html entities --- HTML 一般實體的定義. HTML 一般實體的定義
* XML 處理模組::
* xml.etree.cElementTree: xml etree cElementTree --- ElementTree XML API. ElementTree XML API
* xml.dom: xml dom --- Document 物件模型 API. Document 物件模型 API
* xml.dom.minidom: xml dom minidom --- 最小的 DOM 實作. 最小的 DOM 實作
* xml.dom.pulldom: xml dom pulldom --- 支援建置部分 DOM 樹. 支援建置部分 DOM 樹
* xml.sax: xml sax --- SAX2 剖析器支援. SAX2 剖析器支援
* xml.sax.handler: xml sax handler --- SAX 處理函式的基本類別. SAX 處理函式的基本類別
* xml.sax.saxutils: xml sax saxutils --- SAX 工具程式. SAX 工具程式
* xml.sax.xmlreader: xml sax xmlreader --- XML 剖析器的介面. XML 剖析器的介面
* xml.parsers.expat: xml parsers expat --- 使用 Expat 進行快速 XML 剖析. 使用 Expat 進行快速 XML 剖析

html.parser -- 簡單的 HTML 和 XHTML 剖析器

* HTML 剖析器應用程式範例::
* HTMLParser 方法::
* 範例: 範例<30>.

XML 處理模組

* XML 漏洞::
* defusedxml 套件::

xml.etree.cElementTree -- ElementTree XML API

* 教學: 教學<2>.
* XPath 支援::
* Reference: Reference<3>.
* XInclude support::
* Reference: Reference<4>.

教學

* XML tree and elements::
* 剖析 XML::
* Pull API for non-blocking parsing::
* Finding interesting elements::
* 改動 XML 檔案::
* Building XML documents::
* Parsing XML with Namespaces::

XPath 支援

* 範例: 範例<31>.
* Supported XPath syntax::

Reference

* 函式: 函式<8>.

XInclude support

* 範例: 範例<32>.

Reference

* 函式: 函式<9>.
* Element 物件::
* ElementTree 物件::
* QName 物件::
* TreeBuilder 物件::
* XMLParser 物件::
* XMLPullParser 物件::
* 例外: 例外<14>.

xml.dom -- Document 物件模型 API

* 模組內容: 模組內容<6>.
* Objects in the DOM::
* Conformance::

Objects in the DOM

* DOMImplementation 物件::
* Node Objects::
* NodeList 物件::
* DocumentType 物件::
* Document Objects::
* Element Objects::
* Attr Objects::
* NamedNodeMap 物件::
* Comment Objects::
* Text and CDATASection Objects::
* ProcessingInstruction 物件::
* 例外: 例外<15>.

Conformance

* Type Mapping::
* Accessor Methods::

xml.dom.minidom -- 最小的 DOM 實作

* DOM 物件::
* DOM 範例::
* minidom and the DOM standard::

xml.dom.pulldom -- 支援建置部分 DOM 樹

* DOMEventStream 物件::

xml.sax -- SAX2 剖析器支援

* SAXException 物件::

xml.sax.handler -- SAX 處理函式的基本類別

* ContentHandler 物件::
* DTDHandler 物件::
* EntityResolver 物件::
* ErrorHandler 物件::
* LexicalHandler 物件::

xml.sax.xmlreader -- XML 剖析器的介面

* XMLReader 物件::
* IncrementalParser 物件::
* Locator Objects::
* InputSource 物件::
* The Attributes Interface::
* The AttributesNS Interface::

xml.parsers.expat -- 使用 Expat 進行快速 XML 剖析

* XMLParser 物件: XMLParser 物件<2>.
* ExpatError 例外::
* 範例: 範例<33>.
* Content Model Descriptions::
* Expat error constants::

網路協定 (Internet protocols) 及支援

* webbrowser: webbrowser --- 方便的網頁瀏覽器控制器. 方便的網頁瀏覽器控制器
* wsgiref: wsgiref --- WSGI 工具與參考實作. WSGI 工具與參考實作
* urllib: urllib --- URL 處理模組. URL 處理模組
* urllib.request: urllib request --- 用來開啟 URLs 的可擴充函式庫. 用來開啟 URLs 的可擴充函式庫
* urllib.response: urllib response --- Response classes used by urllib. Response classes used by urllib
* urllib.parse: urllib parse --- 將 URL 剖析成元件. 將 URL 剖析成元件
* urllib.error: urllib error --- urllib request 引發的例外類別. urllib.request 引發的例外類別
* urllib.robotparser: urllib robotparser --- robots txt 的剖析器. robots.txt 的剖析器
* http: http --- HTTP 模組. HTTP 模組
* http.client: http client --- HTTP 協定用戶端. HTTP 協定用戶端
* ftplib: ftplib --- FTP 協定用戶端. FTP 協定用戶端
* poplib: poplib --- POP3 協定用戶端. POP3 協定用戶端
* imaplib: imaplib --- IMAP4 協定客戶端. IMAP4 協定客戶端
* smtplib: smtplib --- SMTP 協定用戶端. SMTP 協定用戶端
* uuid: uuid --- RFC 4122 定義的 UUID 物件. RFC 4122 定義的 UUID 物件
* socketserver: socketserver --- 用於網路伺服器的框架. 用於網路伺服器的框架
* http.server — HTTP 伺服器: http server — HTTP 伺服器.
* http.cookies: http cookies --- HTTP 狀態管理. HTTP 狀態管理
* http.cookiejar: http cookiejar --- HTTP 客戶端的 Cookie 處理. HTTP 客戶端的 Cookie 處理
* xmlrpc: xmlrpc --- XMLRPC 伺服器與用戶模組. XMLRPC 伺服器與用戶模組
* xmlrpc.client: xmlrpc client --- XML-RPC 客戶端存取. XML-RPC 客戶端存取
* xmlrpc.server: xmlrpc server --- 基本 XML-RPC 伺服器. 基本 XML-RPC 伺服器
* ipaddress: ipaddress --- IPv4/IPv6 操作函式庫. IPv4/IPv6 操作函式庫

webbrowser -- 方便的網頁瀏覽器控制器

* Browser Controller Objects::

wsgiref -- WSGI 工具與參考實作

* wsgiref.util: wsgiref util -- WSGI 環境工具. WSGI 環境工具
* wsgiref.headers: wsgiref headers -- WSGI 回應標頭工具. WSGI 回應標頭工具
* wsgiref.simple_server: wsgiref simple_server -- 一個簡單的 WSGI HTTP 伺服器. 一個簡單的 WSGI HTTP 伺服器
* wsgiref.validate: wsgiref validate --- WSGI 符合性檢查. WSGI 符合性檢查
* wsgiref.handlers: wsgiref handlers -- 伺服器 / 閘道基本類別. 伺服器 / 閘道基本類別
* wsgiref.types: wsgiref types -- 用於靜態型別檢查的 WSGI 型別. 用於靜態型別檢查的 WSGI 型別
* 範例: 範例<34>.

urllib.request -- 用來開啟 URLs 的可擴充函式庫

* Request Objects::
* OpenerDirector 物件::
* BaseHandler 物件::
* HTTPRedirectHandler 物件::
* HTTPCookieProcessor 物件::
* ProxyHandler 物件::
* HTTPPasswordMgr 物件::
* HTTPPasswordMgrWithPriorAuth 物件::
* AbstractBasicAuthHandler 物件::
* HTTPBasicAuthHandler 物件::
* ProxyBasicAuthHandler 物件::
* AbstractDigestAuthHandler 物件::
* HTTPDigestAuthHandler 物件::
* ProxyDigestAuthHandler 物件::
* HTTPHandler 物件::
* HTTPSHandler 物件::
* FileHandler 物件::
* DataHandler 物件::
* FTPHandler 物件::
* CacheFTPHandler 物件::
* UnknownHandler 物件::
* HTTPErrorProcessor 物件::
* 範例: 範例<35>.
* Legacy interface::
* urllib.request Restrictions: urllib request Restrictions.

urllib.parse -- 將 URL 剖析成元件

* URL Parsing::
* URL parsing security::
* Parsing ASCII Encoded Bytes::
* Structured Parse Results::
* URL Quoting::

http -- HTTP 模組

* HTTP 狀態碼::
* HTTP 狀態分類::
* HTTP 方法::

http.client -- HTTP 協定用戶端

* HTTPConnection 物件::
* HTTPResponse 物件::
* 範例: 範例<36>.
* HTTPMessage 物件::

ftplib -- FTP 協定用戶端

* 參考::

參考

* FTP 物件::
* FTP_TLS 物件::
* 模組變數::

poplib -- POP3 協定用戶端

* POP3 物件::
* POP3 範例::

imaplib -- IMAP4 協定客戶端

* IMAP4 物件::
* IMAP4 範例::

smtplib -- SMTP 協定用戶端

* SMTP 物件::
* SMTP 範例::

uuid -- RFC 4122 定義的 UUID 物件

* 命令列的用法::
* 範例: 範例<37>.
* 命令列的範例::

socketserver -- 用於網路伺服器的框架

* Server Creation Notes::
* Server Objects::
* Request Handler Objects::
* 範例: 範例<38>.

範例

* socketserver.TCPServer 範例: socketserver TCPServer 範例.
* socketserver.UDPServer 範例: socketserver UDPServer 範例.
* Asynchronous Mixins::

http.server — HTTP 伺服器

* 安全性注意事項: 安全性注意事項<3>.

http.cookies -- HTTP 狀態管理

* Cookie 物件::
* Morsel 物件::
* 範例: 範例<39>.

http.cookiejar -- HTTP 客戶端的 Cookie 處理

* CookieJar 與 FileCookieJar 物件::
* FileCookieJar subclasses and co-operation with web browsers::
* CookiePolicy 物件::
* DefaultCookiePolicy 物件::
* Cookie 物件: Cookie 物件<2>.
* 範例: 範例<40>.

xmlrpc.client -- XML-RPC 客戶端存取

* ServerProxy 物件::
* 日期時間物件::
* Binary Objects::
* Fault Objects::
* ProtocolError 物件::
* MultiCall 物件::
* 便捷的函式::
* Example of Client Usage::
* Example of Client and Server Usage::

xmlrpc.server -- 基本 XML-RPC 伺服器

* SimpleXMLRPCServer 物件::
* CGIXMLRPCRequestHandler::
* Documenting XMLRPC server::
* DocXMLRPCServer 物件::
* DocCGIXMLRPCRequestHandler::

SimpleXMLRPCServer 物件

* SimpleXMLRPCServer 範例::

ipaddress -- IPv4/IPv6 操作函式庫

* Convenience factory functions::
* IP Addresses::
* IP Network definitions::
* Interface objects::
* Other Module Level Functions::
* Custom Exceptions::

IP Addresses

* Address objects::
* Conversion to Strings and Integers::
* Operators: Operators<2>.

Operators

* Comparison operators::
* Arithmetic operators::

IP Network definitions

* Prefix, net mask and host mask: Prefix net mask and host mask.
* Network objects::
* Operators: Operators<3>.

Operators

* Logical operators::
* Iteration::
* Networks as containers of addresses::

Interface objects

* Operators: Operators<4>.

Operators

* Logical operators: Logical operators<2>.

多媒體服務

* wave: wave --- 讀寫 WAV 檔案. 讀寫 WAV 檔案
* colorsys: colorsys --- 顏色系統間的轉換. 顏色系統間的轉換

wave -- 讀寫 WAV 檔案

* Wave_read 物件::
* Wave_write 物件::

國際化

* gettext: gettext --- 多語言國際化服務. 多語言國際化服務
* locale: locale --- 國際化服務. 國際化服務

gettext -- 多語言國際化服務

* GNU gettext API::
* Class-based API::
* Internationalizing your programs and modules::
* 致謝: 致謝<9>.

Class-based API

* The NullTranslations class::
* The GNUTranslations class::
* Solaris message catalog support::
* The Catalog constructor::

Internationalizing your programs and modules

* Localizing your module::
* Localizing your application::
* Changing languages on the fly::
* Deferred translations::

locale -- 國際化服務

* Background, details, hints, tips and caveats: Background details hints tips and caveats.
* For extension writers and programs that embed Python::
* Access to message catalogs::

程式框架

* turtle: turtle --- 龜圖學 Turtle graphics. 龜圖學 (Turtle graphics)
* cmd: cmd --- 以列為導向的指令直譯器支援. 以列為導向的指令直譯器支援
* shlex: shlex --- 簡單的語法分析. 簡單的語法分析

turtle -- 龜圖學 (Turtle graphics)

* 介紹::
* Get started::
* 教學: 教學<3>.
* How to...: How to.
* Turtle graphics reference::
* Methods of RawTurtle/Turtle and corresponding functions::
* Methods of TurtleScreen/Screen and corresponding functions::
* Public classes::
* 解釋: 解釋<2>.
* Help and configuration::
* turtledemo: turtledemo --- Demo scripts. Demo scripts
* Changes since Python 2.6: Changes since Python 2 6.
* Changes since Python 3.0: Changes since Python 3 0.

教學

* 啟動一個烏龜環境::
* 基本繪圖::
* Making algorithmic patterns::

基本繪圖

* Pen control::
* The turtle's position::

How to...

* Get started as quickly as possible::
* Use the turtle module namespace::
* Use turtle graphics in a script::
* Use object-oriented turtle graphics::

Turtle graphics reference

* Turtle methods::
* Methods of TurtleScreen/Screen::

Methods of RawTurtle/Turtle and corresponding functions

* Turtle motion::
* Tell Turtle's state::
* Settings for measurement::
* Pen control: Pen control<2>.
* Turtle state::
* Using events::
* Special Turtle methods::
* Compound shapes::

Pen control

* Drawing state::
* Color control::
* Filling::
* More drawing control::

Turtle state

* Visibility::
* Appearance::

Methods of TurtleScreen/Screen and corresponding functions

* Window control::
* Animation control::
* Using screen events::
* Input methods::
* Settings and special methods::
* Methods specific to Screen, not inherited from TurtleScreen: Methods specific to Screen not inherited from TurtleScreen.

Help and configuration

* How to use help::
* Translation of docstrings into different languages::
* How to configure Screen and Turtles::

cmd -- 以列為導向的指令直譯器支援

* Cmd 物件::
* Cmd Example::

shlex -- 簡單的語法分析

* shlex 物件::
* Parsing Rules::
* Improved Compatibility with Shells::

以 Tk 打造圖形使用者介面 (Graphical User Interfaces)

* tkinter: tkinter --- Tcl/Tk 的 Python 介面. Tcl/Tk 的 Python 介面
* tkinter.colorchooser: tkinter colorchooser --- 顏色選擇對話框. 顏色選擇對話框
* tkinter.font: tkinter font --- Tkinter 字型包裝器. Tkinter 字型包裝器
* Tkinter 對話框::
* tkinter.messagebox: tkinter messagebox --- Tkinter 訊息提示. Tkinter 訊息提示
* tkinter.scrolledtext: tkinter scrolledtext --- 捲動文字小工具. 捲動文字小工具
* tkinter.dnd: tkinter dnd --- 拖放支援. 拖放支援
* tkinter.ttk: tkinter ttk --- Tk 主題化小工具. Tk 主題化小工具
* IDLE: IDLE<62>.

tkinter -- Tcl/Tk 的 Python 介面

* Architecture::
* Tkinter Modules::
* Tkinter Life Preserver::
* Threading model::
* Handy Reference::
* File Handlers::

Tkinter Life Preserver

* A Hello World Program::
* Important Tk Concepts::
* Understanding How Tkinter Wraps Tcl/Tk::
* How do I...? What option does...?: How do I ? What option does ?.
* Navigating the Tcl/Tk Reference Manual::

Handy Reference

* Setting Options::
* The Packer::
* Packer Options::
* Coupling Widget Variables::
* The Window Manager::
* Tk Option Data Types::
* Bindings and Events::
* The index Parameter::
* Images::

Tkinter 對話框

* tkinter.simpledialog: tkinter simpledialog --- 標準 Tkinter 輸入對話框. 標準 Tkinter 輸入對話框
* tkinter.filedialog: tkinter filedialog --- File selection dialogs. File selection dialogs
* tkinter.commondialog: tkinter commondialog --- Dialog window templates. Dialog window templates

tkinter.filedialog -- File selection dialogs

* Native Load/Save Dialogs::

tkinter.ttk -- Tk 主題化小工具

* 使用 Ttk::
* Ttk Widgets::
* Widget::
* Combobox::
* Spinbox::
* Notebook::
* Progressbar::
* Separator::
* Sizegrip::
* Treeview::
* Ttk Styling::

Widget

* 標準選項::
* Scrollable Widget Options::
* Label Options::
* 相容性選項::
* Widget States::
* ttk.Widget: ttk Widget.

Combobox

* 選項::
* Virtual events::
* ttk.Combobox: ttk Combobox.

Spinbox

* 選項: 選項<2>.
* Virtual events: Virtual events<2>.
* ttk.Spinbox: ttk Spinbox.

Notebook

* 選項: 選項<3>.
* Tab Options::
* Tab Identifiers::
* 虛擬事件::
* ttk.Notebook: ttk Notebook.

Progressbar

* 選項: 選項<4>.
* ttk.Progressbar: ttk Progressbar.

Separator

* 選項: 選項<5>.

Sizegrip

* Platform-specific notes::
* Bugs::

Treeview

* 選項: 選項<6>.
* Item Options::
* Tag Options::
* Column Identifiers::
* 虛擬事件: 虛擬事件<2>.
* ttk.Treeview: ttk Treeview.

Ttk Styling

* Layouts::

IDLE

* 目錄::
* Editing and Navigation::
* Startup and Code Execution::
* Help and Preferences::
* idlelib::

目錄

* File menu (Shell and Editor): File menu Shell and Editor.
* Edit menu (Shell and Editor): Edit menu Shell and Editor.
* Format menu (Editor window only): Format menu Editor window only.
* Run menu (Editor window only): Run menu Editor window only.
* Shell menu (Shell window only): Shell menu Shell window only.
* Debug menu (Shell window only): Debug menu Shell window only.
* Options menu (Shell and Editor): Options menu Shell and Editor.
* Window menu (Shell and Editor): Window menu Shell and Editor.
* Help menu (Shell and Editor): Help menu Shell and Editor.
* Context menus::

Editing and Navigation

* Editor windows::
* Key bindings::
* Automatic indentation::
* Search and Replace::
* Completions::
* Calltips::
* Code Context::
* Shell window::
* Text colors::

Startup and Code Execution

* 命令列用法: 命令列用法<2>.
* Startup failure::
* Running user code::
* User output in Shell::
* Developing tkinter applications::
* Running without a subprocess::

Help and Preferences

* Help sources::
* Setting preferences::
* IDLE on macOS::
* Extensions::

開發工具

* typing: typing --- 支援型別提示. 支援型別提示
* pydoc: pydoc --- 文件產生器與線上幫助系統. 文件產生器與線上幫助系統
* Python 開發模式::
* doctest: doctest --- 測試互動式 Python 範例. 測試互動式 Python 範例
* unittest: unittest --- 單元測試框架. 單元測試框架
* unittest.mock — mock 物件函式庫: unittest mock — mock 物件函式庫.
* unittest.mock: unittest mock --- 入門指南. 入門指南
* test: test --- Python 的回歸測試 regression tests 套件. Python 的回歸測試 (regression tests) 套件
* test.support: test support --- Python 測試套件的工具. Python 測試套件的工具
* test.support.socket_helper: test support socket_helper --- 用於 socket 測試的工具. 用於 socket 測試的工具
* test.support.script_helper: test support script_helper --- 用於 Python 執行測試的工具. 用於 Python 執行測試的工具
* test.support.bytecode_helper: test support bytecode_helper --- 用於測試位元組碼能正確產生的支援工具. 用於測試位元組碼能正確產生的支援工具
* test.support.threading_helper: test support threading_helper --- Utilities for threading tests. Utilities for threading tests
* test.support.os_helper: test support os_helper --- 用於 os 測試的工具. 用於 os 測試的工具
* test.support.import_helper: test support import_helper --- 用於 import 測試的工具. 用於 import 測試的工具
* test.support.warnings_helper: test support warnings_helper --- 用於 warnings 測試的工具. 用於 warnings 測試的工具

typing -- 支援型別提示

* Python 型別系統的技術規範::
* 型別別名::
* NewType::
* 註釋 callable 物件::
* 泛型::
* 註釋元組 (tuple): 註釋元組 tuple.
* 類別物件的型別::
* Annotating generators and coroutines::
* 使用者定義泛型型別::
* Any 型別::
* 標稱 (nominal) 子型別 vs 結構子型別: 標稱 nominal 子型別 vs 結構子型別.
* 模組內容: 模組內容<7>.
* Deprecation Timeline of Major Features::

模組內容

* 特別型別原語 (primitive): 特別型別原語 primitive.
* 協定: 協定<2>.
* ABCs for working with IO::
* 函式與裝飾器::
* Introspection helpers::
* 常數: 常數<9>.
* 棄用的別名::

特別型別原語 (primitive)

* 特別型別::
* 特別型式::
* Building generic types and type aliases::
* Other special directives::

棄用的別名

* 內建型別的別名::
* collections 中型別的別名::
* Aliases to other concrete types::
* collections.abc 中容器 ABC 的別名: collections abc 中容器 ABC 的別名.
* Aliases to asynchronous ABCs in collections.abc: Aliases to asynchronous ABCs in collections abc.
* Aliases to other ABCs in collections.abc: Aliases to other ABCs in collections abc.
* contextlib ABC 的別名::

Python 開發模式

* Python 開發模式的影響::
* ResourceWarning 範例::
* 檔案描述器的錯誤範例::

doctest -- 測試互動式 Python 範例

* Simple Usage; Checking Examples in Docstrings: Simple Usage Checking Examples in Docstrings.
* Simple Usage; Checking Examples in a Text File: Simple Usage Checking Examples in a Text File.
* How It Works::
* 基礎 API::
* Unittest API::
* Advanced API::
* Debugging::
* Soapbox::

How It Works

* Which Docstrings Are Examined?::
* How are Docstring Examples Recognized?::
* What's the Execution Context?::
* What About Exceptions?::
* 可選旗標::
* Directives::
* 警告: 警告<2>.

Advanced API

* DocTest 物件::
* Example 物件::
* DocTestFinder 物件::
* DocTestParser 物件::
* TestResults objects::
* DocTestRunner 物件::
* OutputChecker 物件::

unittest -- 單元測試框架

* 簡單範例::
* 命令執行列介面 (Command-Line Interface): 命令執行列介面 Command-Line Interface.
* Test Discovery（測試探索）::
* Organizing test code::
* Re-using old test code::
* Skipping tests and expected failures::
* Distinguishing test iterations using subtests::
* Classes and functions::
* Class and Module Fixtures::
* Signal Handling::

命令執行列介面 (Command-Line Interface)

* 命令列模式選項::

Classes and functions

* Test cases::
* Grouping tests::
* Loading and running tests::

Loading and running tests

* load_tests Protocol::

Class and Module Fixtures

* setUpClass and tearDownClass::
* setUpModule and tearDownModule::

unittest.mock — mock 物件函式庫

* 快速導引::
* Mock 類別::
* Patchers::
* MagicMock 以及魔術方法支援::
* 輔助函式: 輔助函式<2>.
* side_effect、return_value 和 wraps 的優先順序::

Mock 類別

* 呼叫::
* 刪除屬性::
* Mock 名稱與名稱屬性::
* 如同屬性一般附加 mock::

Patchers

* patch::
* patch.object: patch object.
* patch.dict: patch dict.
* patch.multiple: patch multiple.
* patch 方法：啟動與停止::
* patch 內建函式::
* TEST_PREFIX::
* 巢狀使用 Patch 裝飾器::
* 該 patch 何處::
* Patch 描述器與代理物件 (Proxy Objects): Patch 描述器與代理物件 Proxy Objects.

MagicMock 以及魔術方法支援

* Mock 魔術方法::
* Magic Mock::

輔助函式

* sentinel（哨兵）::
* DEFAULT::
* call::
* create_autospec::
* ANY::
* FILTER_DIR::
* mock_open::
* Autospeccing（自動規格）::
* 密封 mock::

unittest.mock -- 入門指南

* 使用 Mock 的方式::
* Patch 裝飾器::
* 更多範例::

使用 Mock 的方式

* 使用 Mock 來 patching 方法::
* 對物件的方法呼叫使用 mock::
* Mock 類別: Mock 類別<2>.
* 命名你的 mock::
* 追蹤所有呼叫::
* 設定回傳值和屬性::
* 透過 mock 引發例外::
* Side effect 函式以及可疊代物件::
* Mock 非同步可疊代物件::
* Mock 非同步情境管理器::
* 從現有物件建立 mock::
* 使用 side_effect 回傳各別檔案內容::

更多範例

* Mock 鍊接呼叫::
* 部分 mocking::
* Mock 產生器方法::
* 對每個測試方法應用相同的 patch::
* Mock Unbound Methods （未繫結方法）::
* 使用 mock 檢查多個呼叫::
* 應對可變引數::
* 巢狀使用 Patch::
* 使用 MagicMock 來 mock 字典::
* Mock 子類別及其屬性::
* 使用 patch.dict 來 mock import: 使用 patch dict 來 mock import.
* 追蹤呼叫順序與更簡潔的呼叫斷言::
* 更複雜的引數匹配::

test -- Python 的回歸測試 (regression tests) 套件

* 撰寫 test 套件的單元測試::
* 使用命令列介面執行測試::

除錯與效能分析

* 稽核事件表::
* bdb: bdb --- 偵錯器框架. 偵錯器框架
* faulthandler: faulthandler --- 傾印 Python 回溯. 傾印 Python 回溯
* pdb: pdb --- The Python Debugger. The Python Debugger
* Python 的分析器::
* timeit: timeit --- 測量小量程式片段的執行時間. 測量小量程式片段的執行時間
* trace: trace --- 追蹤或追查 Python 陳述式執行. 追蹤或追查 Python 陳述式執行
* tracemalloc: tracemalloc --- 追蹤記憶體配置. 追蹤記憶體配置

faulthandler -- 傾印 Python 回溯

* Dumping the traceback::
* Fault handler state::
* Dumping the tracebacks after a timeout::
* Dumping the traceback on a user signal::
* Issue with file descriptors::
* 範例: 範例<41>.

pdb -- The Python Debugger

* Debugger Commands::

Python 的分析器

* Introduction to the profilers::
* Instant User's Manual::
* profile and cProfile Module Reference::
* The Stats Class::
* What Is Deterministic Profiling?::
* 限制::
* 校正::
* Using a custom timer::

timeit -- 測量小量程式片段的執行時間

* 基礎範例: 基礎範例<2>.
* Python 介面::
* 命令列介面: 命令列介面<4>.
* 範例: 範例<42>.

trace -- 追蹤或追查 Python 陳述式執行

* Command-Line Usage::
* Programmatic Interface::

Command-Line Usage

* Main options::
* Modifiers::
* Filters::

tracemalloc -- 追蹤記憶體配置

* 範例: 範例<43>.
* API::

範例

* Display the top 10::
* Compute differences::
* Get the traceback of a memory block::
* Pretty top::

Pretty top

* Record the current and peak size of all traced memory blocks::

API

* 函式: 函式<10>.
* DomainFilter::
* Filter::
* Frame::
* Snapshot::
* Statistic::
* StatisticDiff::
* Trace::
* Traceback::

軟體封裝與發布

* ensurepip: ensurepip --- pip 安裝器的初始建置 bootstrapping. pip 安裝器的初始建置 (bootstrapping)
* venv: venv --- 建立虛擬環境. 建立虛擬環境
* zipapp —-- 管理可執行的 Python zip 封存檔案::

ensurepip -- pip 安裝器的初始建置 (bootstrapping)

* 命令列介面: 命令列介面<5>.
* 模組 API::

venv -- 建立虛擬環境

* 建立虛擬環境: 建立虛擬環境<2>.
* 虛擬環境如何運作::
* API: API<2>.
* An example of extending EnvBuilder::

zipapp —- 管理可執行的 Python zip 封存檔案

* 基本範例::
* 命令執行列介面::
* Python API::
* 範例: 範例<44>.
* Specifying the Interpreter::
* Creating Standalone Applications with zipapp::
* The Python Zip Application Archive Format::

Creating Standalone Applications with zipapp

* Caveats::

Python Runtime 服務

* sys: sys --- 系統特定的參數與函式. 系統特定的參數與函式
* sys.monitoring: sys monitoring --- Execution event monitoring. Execution event monitoring
* sysconfig: sysconfig --- 提供 Python 設定資訊的存取. 提供 Python 設定資訊的存取
* builtins: builtins --- 內建物件. 內建物件
* __main__: __main__ --- 頂層程式碼環境. 頂層程式碼環境
* warnings: warnings --- 警告控制. 警告控制
* dataclasses: dataclasses --- Data Classes. Data Classes
* contextlib: contextlib --- Utilities for with-statement contexts. Utilities for with-statement contexts
* abc: abc --- 抽象基底類別. 抽象基底類別
* atexit: atexit --- 退出處理函式. 退出處理函式
* traceback: traceback --- 列印或取得堆疊回溯 stack traceback. 列印或取得堆疊回溯 (stack traceback)
* __future__: __future__ --- Future 陳述式定義. Future 陳述式定義
* gc: gc --- 垃圾回收器介面 Garbage Collector interface. 垃圾回收器介面 (Garbage Collector interface)
* inspect: inspect --- 檢視活動物件. 檢視活動物件
* site: site --- Site-specific configuration hook. Site-specific configuration hook

sys.monitoring -- Execution event monitoring

* Tool identifiers::
* 事件::
* Turning events on and off::
* 註冊回呼函式::

Tool identifiers

* Registering and using tools::

事件

* Local events::
* 輔助事件::
* 其他事件::
* The STOP_ITERATION event::

Turning events on and off

* Setting events globally::
* Per code object events::
* 停用事件::

註冊回呼函式

* 回呼函式引數::

sysconfig -- 提供 Python 設定資訊的存取

* Configuration variables::
* Installation paths::
* User scheme::
* Home scheme::
* Prefix scheme::
* 安裝路徑函式::
* 其他函式: 其他函式<3>.
* 將 sysconfig 作為腳本使用::

User scheme

* posix_user::
* nt_user::
* osx_framework_user::

Home scheme

* posix_home::

Prefix scheme

* posix_prefix::
* nt::

__main__ -- 頂層程式碼環境

* __name__ == '__main__'::
* Python 套件中的 __main__.py: Python 套件中的 __main__ py.
* import __main__::

__name__ == '__main__'

* 什麼是「頂層程式碼環境」？::
* 慣用 (Idiomatic) 用法: 慣用 Idiomatic 用法.
* 打包時須考慮的事情::

Python 套件中的 __main__.py

* 慣用 (Idiomatic) 用法: 慣用 Idiomatic 用法<2>.

warnings -- 警告控制

* Warning Categories::
* The Warnings Filter::
* Temporarily Suppressing Warnings::
* Testing Warnings::
* Updating Code For New Versions of Dependencies::
* Available Functions::
* Available Context Managers::

The Warnings Filter

* Describing Warning Filters::
* Default Warning Filter::
* Overriding the default filter::

dataclasses -- Data Classes

* 模組內容: 模組內容<8>.
* Post-init processing::
* 類別變數::
* Init-only variables::
* 凍結實例::
* 繼承::
* Re-ordering of keyword-only parameters in __init__(): Re-ordering of keyword-only parameters in __init__.
* 預設工廠函式::
* 可變預設值::
* Descriptor-typed fields::

contextlib -- Utilities for with-statement contexts

* Utilities::
* Examples and Recipes: Examples and Recipes<2>.
* Single use, reusable and reentrant context managers: Single use reusable and reentrant context managers.

Examples and Recipes

* Supporting a variable number of context managers::
* Catching exceptions from __enter__ methods::
* Cleaning up in an __enter__ implementation::
* Replacing any use of try-finally and flag variables::
* Using a context manager as a function decorator::

Single use, reusable and reentrant context managers

* Reentrant context managers::
* Reusable context managers::

atexit -- 退出處理函式

* atexit 範例::

traceback -- 列印或取得堆疊回溯 (stack traceback)

* TracebackException 物件::
* StackSummary 物件::
* FrameSummary 物件::
* Traceback Examples::

__future__ -- Future 陳述式定義

* 模組內容: 模組內容<9>.

inspect -- 檢視活動物件

* Types and members::
* 取得原始碼::
* Introspecting callables with the Signature object::
* 類別與函式::
* 直譯器堆疊::
* Fetching attributes statically::
* Current State of Generators, Coroutines, and Asynchronous Generators: Current State of Generators Coroutines and Asynchronous Generators.
* Code Objects Bit Flags::
* Buffer flags::
* 命令列介面: 命令列介面<6>.

site -- Site-specific configuration hook

* sitecustomize::
* usercustomize::
* Readline configuration::
* 模組內容: 模組內容<10>.
* 命令列介面: 命令列介面<7>.

自訂 Python 直譯器

* code: code --- 直譯器基底類別. 直譯器基底類別
* codeop: codeop --- 編譯 Python 程式碼. 編譯 Python 程式碼

code -- 直譯器基底類別

* Interactive Interpreter Objects::
* Interactive Console Objects::

引入模組

* zipimport: zipimport --- 從 Zip 封存檔案匯入模組. 從 Zip 封存檔案匯入模組
* pkgutil: pkgutil --- 套件擴充工具程式. 套件擴充工具程式
* modulefinder: modulefinder --- 搜尋腳本所使用的模組. 搜尋腳本所使用的模組
* runpy: runpy --- 定位並執行 Python 模組. 定位並執行 Python 模組
* importlib: importlib --- import 的實作. import 的實作
* importlib.resources: importlib resources -- Package resource reading opening and access. Package resource reading, opening and access
* importlib.resources.abc: importlib resources abc -- 資源的抽象基底類別. 資源的抽象基底類別
* importlib.metadata: importlib metadata -- 存取套件的元資料. 存取套件的元資料
* The initialization of the sys.path module search path: The initialization of the sys path module search path.

zipimport -- 從 Zip 封存檔案匯入模組

* zipimporter 物件::
* 範例: 範例<45>.

modulefinder -- 搜尋腳本所使用的模組

* ModuleFinder 的用法範例::

importlib -- import 的實作

* 簡介: 簡介<9>.
* 函式: 函式<11>.
* importlib.abc: importlib abc -- Abstract base classes related to import. Abstract base classes related to import
* importlib.machinery: importlib machinery -- Importers and path hooks. Importers and path hooks
* importlib.util: importlib util -- Utility code for importers. Utility code for importers
* 範例: 範例<46>.

範例

* Importing programmatically::
* Checking if a module can be imported::
* Importing a source file directly::
* Implementing lazy imports::
* Setting up an importer::
* Approximating importlib.import_module(): Approximating importlib import_module.

importlib.resources - Package resource reading, opening and access

* Functional API::

importlib.metadata - 存取套件的元資料

* Overview: Overview<2>.
* Functional API: Functional API<2>.
* Distributions::
* Distribution Discovery::
* Extending the search algorithm::

Functional API

* Entry points::
* Distribution metadata::
* Distribution versions::
* Distribution files::
* Distribution requirements::
* Mapping import to distribution packages::

Extending the search algorithm

* Example::

The initialization of the sys.path module search path

* Virtual environments::
* _pth files::
* Embedded Python::

Python 語言服務

* ast: ast --- 抽象語法樹 Abstract Syntax Trees. 抽象語法樹 (Abstract Syntax Trees)
* symtable: symtable --- 存取編譯器的符號表. 存取編譯器的符號表
* token: token --- 與 Python 剖析樹一起使用的常數. 與 Python 剖析樹一起使用的常數
* keyword: keyword --- 檢驗 Python 關鍵字. 檢驗 Python 關鍵字
* tokenize: tokenize --- Tokenizer for Python source. Tokenizer for Python source
* tabnanny: tabnanny --- 偵測不良縮排. 偵測不良縮排
* pyclbr: pyclbr --- Python 模組瀏覽器支援. Python 模組瀏覽器支援
* py_compile — 編譯 Python 來源檔案::
* compileall: compileall --- 位元組編譯 Python 函式庫. 位元組編譯 Python 函式庫
* dis: dis --- Python bytecode 的反組譯器. Python bytecode 的反組譯器
* pickletools: pickletools --- pickle 開發者的工具. pickle 開發者的工具

ast -- 抽象語法樹 (Abstract Syntax Trees)

* 抽象文法 (Abstract Grammar): 抽象文法 Abstract Grammar.
* 節點 (Node) 類別: 節點 Node 類別.
* ast 輔助程式::
* 編譯器旗標: 編譯器旗標<2>.
* 命令列用法: 命令列用法<3>.

節點 (Node) 類別

* 根節點::
* 文本 (Literals): 文本 Literals.
* 變數::
* 運算式: 運算式<2>.
* 陳述式::
* 流程控制::
* 模式匹配 (pattern matching): 模式匹配 pattern matching.
* 型別參數 (type parameters): 型別參數 type parameters.
* 函式和類別定義::
* async 和 await::

運算式

* 下標 (Subscripting): 下標 Subscripting.
* 綜合運算式 (comprehensions): 綜合運算式 comprehensions.

陳述式

* 引入 (imports): 引入 imports.

symtable -- 存取編譯器的符號表

* 產生符號表::
* 檢查符號表::
* Command-Line Usage: Command-Line Usage<2>.

tokenize -- Tokenizer for Python source

* Tokenizing Input::
* Command-Line Usage: Command-Line Usage<3>.
* 範例: 範例<47>.

pyclbr -- Python 模組瀏覽器支援

* 函式物件::
* Class Objects::

py_compile — 編譯 Python 來源檔案

* Command-Line Interface: Command-Line Interface<3>.

compileall -- 位元組編譯 Python 函式庫

* Command-line use::
* Public functions::

dis -- Python bytecode 的反組譯器

* Command-line interface::
* Bytecode analysis::
* Analysis functions::
* Python Bytecode Instructions::
* Opcode collections::

pickletools -- pickle 開發者的工具

* 命令列用法: 命令列用法<4>.
* 程式化介面::

命令列用法

* 命令列選項: 命令列選項<4>.

MS Windows 特有服務

* msvcrt: msvcrt --- MS VC++ runtime 提供的有用例程. MS VC++ runtime 提供的有用例程
* winreg: winreg --- Windows 註冊表存取. Windows 註冊表存取
* winsound: winsound --- Windows 的聲音播放介面. Windows 的聲音播放介面

msvcrt -- MS VC++ runtime 提供的有用例程

* File Operations::
* Console I/O::
* Other Functions::

winreg -- Windows 註冊表存取

* 函式: 函式<12>.
* 常數: 常數<10>.
* Registry Handle Objects::

常數

* HKEY_* Constants::
* Access Rights::
* Value Types::

Access Rights

* 64-bit Specific::

Unix 特有服務

* posix: posix --- 最常見的 POSIX 系統呼叫. 最常見的 POSIX 系統呼叫
* pwd: pwd --- 密碼資料庫. 密碼資料庫
* grp: grp --- 群組資料庫. 群組資料庫
* termios: termios --- POSIX 風格 tty 控制. POSIX 風格 tty 控制
* tty: tty --- 終端機控制函式. 終端機控制函式
* pty: pty --- 偽終端工具. 偽終端工具
* fcntl: fcntl --- fcntl 和 ioctl 系統呼叫. fcntl 和 ioctl 系統呼叫
* resource: resource --- 資源使用資訊. 資源使用資訊
* syslog: syslog --- Unix syslog 函式庫例程. Unix syslog 函式庫例程

posix -- 最常見的 POSIX 系統呼叫

* 對大檔案 (Large File) 的支援: 對大檔案 Large File 的支援.
* 值得注意的模組內容::

termios -- POSIX 風格 tty 控制

* 範例: 範例<48>.

pty -- 偽終端工具

* 範例: 範例<49>.

resource -- 資源使用資訊

* Resource Limits::
* Resource Usage::

syslog -- Unix syslog 函式庫例程

* 範例: 範例<50>.

範例

* 簡單範例: 簡單範例<2>.

已被取代的模組

* getopt: getopt --- 用於命令列選項的 C 風格剖析器. 用於命令列選項的 C 風格剖析器
* optparse: optparse --- 命令列選項剖析器. 命令列選項剖析器

optparse -- 命令列選項剖析器

* 背景::
* 教學: 教學<4>.
* Reference Guide::
* Option Callbacks::
* Extending optparse::
* 例外: 例外<16>.

背景

* 術語::
* What are options for?::
* What are positional arguments for?::

教學

* Understanding option actions::
* The store action::
* Handling boolean (flag) options: Handling boolean flag options.
* Other actions::
* Default values::
* Generating help::
* Printing a version string::
* How optparse handles errors::
* Putting it all together::

Generating help

* Grouping Options::

Reference Guide

* Creating the parser::
* Populating the parser::
* Defining options::
* Option attributes::
* Standard option actions::
* Standard option types::
* 剖析引數: 剖析引數<2>.
* Querying and manipulating your option parser::
* Conflicts between options::
* Cleanup: Cleanup<2>.
* 其他方法::

Option Callbacks

* Defining a callback option::
* How callbacks are called::
* Raising errors in a callback::
* Callback example 1; trivial callback: Callback example 1 trivial callback.
* Callback example 2; check option order: Callback example 2 check option order.
* Callback example 3; check option order (generalized): Callback example 3 check option order generalized.
* Callback example 4; check arbitrary condition: Callback example 4 check arbitrary condition.
* Callback example 5; fixed arguments: Callback example 5 fixed arguments.
* Callback example 6; variable arguments: Callback example 6 variable arguments.

Extending optparse

* Adding new types::
* Adding new actions::

擴充和嵌入 Python 直譯器

* 推薦的第三方工具::
* 不使用第三方工具建立擴充::
* 在更大的應用程式中嵌入 CPython 運行環境 (runtime): 在更大的應用程式中嵌入 CPython 運行環境 runtime.

不使用第三方工具建立擴充

* 以 C 或 C++ 擴充 Python::
* Defining Extension Types; Tutorial: Defining Extension Types Tutorial.
* Defining Extension Types; Assorted Topics: Defining Extension Types Assorted Topics.
* 建立 C 與 C++ 擴充套件::
* 建置 Windows 上的 C 和 C++ 擴充::

以 C 或 C++ 擴充 Python

* 一個簡單範例::
* Intermezzo; Errors and Exceptions: Intermezzo Errors and Exceptions.
* 回到範例::
* The Module's Method Table and Initialization Function::
* Compilation and Linkage::
* Calling Python Functions from C::
* Extracting Parameters in Extension Functions::
* Keyword Parameters for Extension Functions::
* Building Arbitrary Values::
* Reference Counts::
* Writing Extensions in C++::
* Providing a C API for an Extension Module::

Reference Counts

* Reference Counting in Python::
* Ownership Rules::
* Thin Ice::
* NULL 指標::

Defining Extension Types: Tutorial

* The Basics::
* Adding data and methods to the Basic example::
* Providing finer control over data attributes::
* Supporting cyclic garbage collection::
* Subclassing other types::

Defining Extension Types: Assorted Topics

* Finalization and De-allocation::
* Object Presentation::
* Attribute Management::
* Object Comparison::
* Abstract Protocol Support::
* Weak Reference Support::
* More Suggestions::

Attribute Management

* Generic Attribute Management::
* Type-specific Attribute Management::

建立 C 與 C++ 擴充套件

* Building C and C++ Extensions with setuptools::

建置 Windows 上的 C 和 C++ 擴充

* A Cookbook Approach::
* Differences Between Unix and Windows::
* Using DLLs in Practice::

在更大的應用程式中嵌入 CPython 運行環境 (runtime)

* 在其它 App 內嵌入 Python::

在其它 App 內嵌入 Python

* Very High Level Embedding::
* Beyond Very High Level Embedding; An overview: Beyond Very High Level Embedding An overview.
* Pure Embedding::
* Extending Embedded Python::
* Embedding Python in C++::
* Compiling and Linking under Unix-like systems::

Python/C API 參考手冊

* 簡介: 簡介<10>.
* C API 穩定性::
* The Very High Level Layer::
* 參照計數: 參照計數<2>.
* 例外處理::
* 工具::
* 抽象物件層 (Abstract Objects Layer): 抽象物件層 Abstract Objects Layer.
* 具體物件層::
* Initialization, Finalization, and Threads: Initialization Finalization and Threads.
* Python 初始化設定::
* 記憶體管理::
* Object Implementation Support::
* API 和 ABI 版本管理::
* Monitoring C API::
* Generating Execution Events::

簡介

* 編寫標準::
* 引入檔案 (include files): 引入檔案 include files.
* 有用的巨集::
* 物件、型別和參照計數::
* 例外: 例外<17>.
* 嵌入式Python::
* 除錯建置::

物件、型別和參照計數

* 參照計數::
* 型別::

參照計數

* 參照計數詳細資訊::

C API 穩定性

* 不穩定的 C API::
* 穩定的應用程式二進位介面::
* 平台注意事項::
* 受限 API 的內容::

穩定的應用程式二進位介面

* 受限 C API::
* 穩定 ABI::
* 受限 API 範圍和性能::
* 受限 API 注意事項::

例外處理

* Printing and clearing::
* Raising exceptions::
* Issuing warnings::
* Querying the error indicator::
* Signal Handling: Signal Handling<2>.
* 例外類別: 例外類別<2>.
* 例外物件::
* Unicode Exception Objects::
* Recursion Control::
* Standard Exceptions::
* Standard Warning Categories::

工具

* 作業系統工具::
* 系統函式::
* 行程控制::
* 引入模組: 引入模組<2>.
* 資料 marshal 的支援::
* 剖析引數與建置數值::
* 字串轉換與格式化::
* PyHash API::
* Reflection::
* 編解碼器註冊表和支援函式::
* PyTime C API::
* 對 Perf Map 的支援::

剖析引數與建置數值

* Parsing arguments::
* Building values::

Parsing arguments

* Strings and buffers::
* 數字::
* 其他物件::
* API 函式::

編解碼器註冊表和支援函式

* 編解碼器查找 API::
* 用於 Unicode 編碼錯誤處理程式的註冊 API::

PyTime C API

* Types::
* Clock Functions::
* Raw Clock Functions::
* Conversion functions::

抽象物件層 (Abstract Objects Layer)

* 物件協定::
* 呼叫協定 (Call Protocol): 呼叫協定 Call Protocol.
* 數字協定::
* 序列協定::
* 對映協定::
* 疊代器協議::
* 緩衝協定 (Buffer Protocol): 緩衝協定 Buffer Protocol.

呼叫協定 (Call Protocol)

* tp_call 協定::
* Vectorcall 協定::
* 物件呼叫 API::
* 呼叫支援 API::

Vectorcall 協定

* 遞迴控制::
* Vectorcall 支援 API::

緩衝協定 (Buffer Protocol)

* Buffer structure::
* Buffer request types::
* Complex arrays::
* Buffer-related functions::

Buffer request types

* request-independent fields::
* readonly, format: readonly format.
* shape, strides, suboffsets: shape strides suboffsets.
* contiguity requests::
* compound requests::

Complex arrays

* NumPy-style; shape and strides: NumPy-style shape and strides.
* PIL-style; shape, strides and suboffsets: PIL-style shape strides and suboffsets.

具體物件層

* 基礎物件::
* 數值物件::
* 序列物件::
* 容器物件::
* 函式物件: 函式物件<2>.
* 其他物件: 其他物件<2>.

基礎物件

* 型別物件::
* None 物件::

型別物件

* Creating Heap-Allocated Types::

數值物件

* 整數物件::
* Boolean（布林）物件::
* 浮點數（Floating-Point）物件::
* 複數物件::

浮點數（Floating-Point）物件

* Pack and Unpack functions::

Pack and Unpack functions

* Pack functions::
* Unpack functions::

複數物件

* 作為 C 結構的複數::
* 作為 Python 物件的複數::

序列物件

* 位元組物件 (Bytes Objects): 位元組物件 Bytes Objects.
* 位元組陣列物件 (Byte Array Objects): 位元組陣列物件 Byte Array Objects.
* Unicode 物件與編解碼器::
* Tuple（元組）物件::
* Struct Sequence Objects::
* List（串列）物件::

位元組陣列物件 (Byte Array Objects)

* 型別檢查巨集::
* 直接 API 函式::
* 巨集::

Unicode 物件與編解碼器

* Unicode 物件::
* Built-in Codecs::
* Methods and Slot Functions::

Unicode 物件

* Unicode Type::
* Unicode Character Properties::
* Creating and accessing Unicode strings::
* Locale Encoding::
* File System Encoding::
* wchar_t 支援::

Built-in Codecs

* Generic Codecs::
* UTF-8 編解碼器::
* UTF-32 編解碼器::
* UTF-16 編解碼器::
* UTF-7 編解碼器::
* Unicode-Escape Codecs::
* Raw-Unicode-Escape Codecs::
* Latin-1 編解碼器::
* ASCII 編解碼器::
* Character Map Codecs::
* MBCS codecs for Windows::
* Methods & Slots::

容器物件

* 字典物件::
* 集合物件::

函式物件

* 函式物件 (Function Objects): 函式物件 Function Objects.
* 實例方法物件 (Instance Method Objects): 實例方法物件 Instance Method Objects.
* 方法物件 (Method Objects): 方法物件 Method Objects.
* Cell 物件::
* 程式碼物件::
* Extra information::

其他物件

* 檔案物件 (File Objects): 檔案物件 File Objects.
* 模組物件::
* 疊代器（Iterator）物件::
* Descriptor（描述器）物件::
* 切片物件::
* MemoryView 物件::
* 弱參照物件: 弱參照物件<2>.
* Capsules: Capsules<2>.
* Frame 物件::
* 產生器 (Generator) 物件: 產生器 Generator 物件.
* Coroutine（協程）物件::
* 情境變數物件::
* DateTime 物件::
* 型別提示物件::

模組物件

* 初始化 C 模組::
* 模組查找::

初始化 C 模組

* Single-phase initialization::
* Multi-phase initialization::
* Low-level module creation functions::
* 支援的函式::

切片物件

* Ellipsis Object::

Frame 物件

* Internal Frames::

Initialization, Finalization, and Threads

* Python 初始化之前::
* Global configuration variables::
* Initializing and finalizing the interpreter::
* Process-wide parameters::
* Thread State and the Global Interpreter Lock::
* Sub-interpreter support::
* Asynchronous Notifications::
* Profiling and Tracing::
* Reference tracing::
* Advanced Debugger Support::
* Thread Local Storage Support::
* Synchronization Primitives::

Thread State and the Global Interpreter Lock

* Releasing the GIL from extension code::
* Non-Python created threads::
* Cautions about fork(): Cautions about fork.
* 高階 API::
* 低階 API::

Sub-interpreter support

* A Per-Interpreter GIL::
* Bugs and caveats::

Thread Local Storage Support

* Thread Specific Storage (TSS) API: Thread Specific Storage TSS API.
* 執行緒局部儲存 (Thread Local Storage, TLS) API：: 執行緒局部儲存 Thread Local Storage TLS API：.

Thread Specific Storage (TSS) API

* Dynamic Allocation::
* 方法::

Synchronization Primitives

* Python Critical Section API::

Python 初始化設定

* 範例: 範例<51>.
* PyWideStringList::
* PyStatus::
* PyPreConfig::
* Preinitialize Python with PyPreConfig::
* PyConfig::
* Initialization with PyConfig::
* Isolated Configuration::
* Python Configuration::
* Python Path Configuration::
* Py_RunMain(): Py_RunMain.
* Py_GetArgcArgv(): Py_GetArgcArgv.
* Multi-Phase Initialization Private Provisional API::

記憶體管理

* 總覽: 總覽<2>.
* Allocator Domains::
* Raw Memory Interface::
* 記憶體介面::
* Object allocators::
* Default Memory Allocators::
* Customize Memory Allocators::
* Debug hooks on the Python memory allocators::
* The pymalloc allocator::
* The mimalloc allocator::
* tracemalloc C API::
* 範例: 範例<52>.

The pymalloc allocator

* Customize pymalloc Arena Allocator::

Object Implementation Support

* 在 heap 上分配物件::
* 通用物件結構::
* 型別物件: 型別物件<2>.
* Number Object Structures::
* Mapping Object Structures::
* Sequence Object Structures::
* Buffer Object Structures::
* Async Object Structures::
* Slot Type typedefs::
* 範例: 範例<53>.
* 循環垃圾回收的支援::

通用物件結構

* Base object types and macros::
* 實作函式與方法::
* Accessing attributes of extension types::

Accessing attributes of extension types

* Member flags::
* Member types::
* Defining Getters and Setters::

型別物件

* Quick Reference::
* PyTypeObject Definition::
* PyObject Slots::
* PyVarObject Slots::
* PyTypeObject Slots::
* Static Types::
* Heap Types::

Quick Reference

* "tp slots"::
* sub-slots::
* slot typedefs::

循環垃圾回收的支援

* Controlling the Garbage Collector State::
* Querying Garbage Collector State::

Generating Execution Events

* Managing the Monitoring State::

安裝 Python 模組

* 關鍵術語::
* 基本用法: 基本用法<3>.
* 我該如何...？: 我該如何 ？.
* 常見的安裝問題::

我該如何...？

* ...在 Python 3.4 之前的 Python 版本中安裝 pip？: 在 Python 3 4 之前的 Python 版本中安裝 pip？.
* ...只為目前的使用者安裝套件？: 只為目前的使用者安裝套件？.
* ...安裝科學的 Python 套件？: 安裝科學的 Python 套件？.
* ...平行安裝多個 Python 版本並使用它們？: 平行安裝多個 Python 版本並使用它們？.

常見的安裝問題

* 在 Linux 上安裝套件至系統 Python::
* 未安裝 pip::
* 安裝二進制擴充 (binary extension): 安裝二進制擴充 binary extension.

Python 如何達成任務

* 遷移延伸模組到 Python 3::
* Curses Programming with Python::
* 描述器 (Descriptor) 指南: 描述器 Descriptor 指南.
* 使用 GDB 來為 C API 擴充功能和 CPython 內部偵錯::
* Enum HOWTO::
* 函式編程 HOWTO::
* 如何使用 Logging 模組::
* Logging Cookbook::
* 如何使用正規表示式::
* Socket 程式設計指南::
* 排序技法::
* Unicode HOWTO::
* 如何使用 urllib 套件取得網路資源::
* Argparse 教學::
* ipaddress 模組介紹::
* 使用 DTrace 和 SystemTap 檢測 CPython::
* Python 對 Linux perf 分析器的支援::
* 註釋 (annotation) 最佳實踐: 註釋 annotation 最佳實踐.
* 隔離擴充模組::
* timer file descriptor HOWTO::
* The Python 2.3 Method Resolution Order: The Python 2 3 Method Resolution Order.
* C API Extension Support for Free Threading::

Curses Programming with Python

* What is curses?::
* Starting and ending a curses application::
* Windows and Pads::
* Displaying Text::
* 使用者輸入::
* For More Information::

What is curses?

* Python curses 模組::

Displaying Text

* Attributes and Color::

描述器 (Descriptor) 指南

* Primer::
* Complete Practical Example::
* Technical Tutorial::
* Pure Python Equivalents::

Primer

* Simple example; A descriptor that returns a constant: Simple example A descriptor that returns a constant.
* Dynamic lookups::
* Managed attributes::
* Customized names::
* Closing thoughts::

Complete Practical Example

* Validator class::
* Custom validators::
* Practical application::

Technical Tutorial

* 摘要::
* Definition and introduction::
* 描述器協定::
* Overview of descriptor invocation::
* Invocation from an instance::
* Invocation from a class::
* Invocation from super::
* Summary of invocation logic::
* Automatic name notification::
* ORM 範例::

Pure Python Equivalents

* Properties::
* Functions and methods::
* Kinds of methods::
* Static methods::
* Class methods::
* Member objects and __slots__::

使用 GDB 來為 C API 擴充功能和 CPython 內部偵錯

* 先決條件::
* 使用偵錯建置與使用開發模式::
* 使用 python-gdb 擴充功能::
* 與 GDB 指令一起使用::

先決條件

* 使用從原始碼建置的 Python 進行設定::
* 從 Linux 發行版設定 Python::

使用 python-gdb 擴充功能

* 漂亮列印器::
* py-list::
* py-up 和 py-down::
* py-bt::
* py-print::
* py-locals::

Enum HOWTO

* Programmatic access to enumeration members and their attributes::
* Duplicating enum members and values::
* Ensuring unique enumeration values::
* Using automatic values::
* Iteration: Iteration<2>.
* 比較::
* Allowed members and attributes of enumerations::
* Restricted Enum subclassing::
* Dataclass support::
* Pickling::
* Functional API: Functional API<3>.
* Derived Enumerations::
* When to use __new__() vs. __init__(): When to use __new__ vs __init__.
* How are Enums and Flags different?::
* Enum Cookbook::
* Subclassing EnumType::

Derived Enumerations

* IntEnum::
* StrEnum::
* IntFlag::
* Flag::
* 其他: 其他<2>.

When to use __new__() vs. __init__()

* Finer Points::

Finer Points

* Supported __dunder__ names::
* Supported _sunder_ names::
* _Private__names::
* Enum member type::
* Creating members that are mixed with other data types::
* Boolean value of Enum classes and members::
* Enum classes with methods::
* Combining members of Flag::
* Flag and IntFlag minutia::

How are Enums and Flags different?

* Enum Classes::
* Flag Classes::
* Enum Members (aka instances): Enum Members aka instances.
* Flag Members::

Enum Cookbook

* Omitting values::
* OrderedEnum::
* DuplicateFreeEnum::
* MultiValueEnum::
* Planet::
* TimePeriod::

Omitting values

* 使用 auto::
* 使用 object::
* Using a descriptive string::
* Using a custom __new__(): Using a custom __new__.

函式編程 HOWTO

* 簡介: 簡介<11>.
* Iterators::
* Generator expressions and list comprehensions::
* Generators::
* 內建函式: 內建函式<2>.
* itertools 模組::
* functools 模組::
* Small functions and the lambda expression::
* Revision History and Acknowledgements::
* References: References<2>.

簡介

* Formal provability::
* Modularity::
* Ease of debugging and testing::
* Composability::

Iterators

* Data Types That Support Iterators::

Generators

* Passing values into a generator::

itertools 模組

* 建立新的疊代器::
* Calling functions on elements::
* Selecting elements::
* Combinatoric functions::
* Grouping elements::

functools 模組

* operator 模組::

References

* General::
* Python-specific::
* Python 說明文件::

如何使用 Logging 模組

* 基礎 Logging 指南::
* Advanced Logging Tutorial::
* Logging Levels: Logging Levels<2>.
* Useful Handlers::
* Exceptions raised during logging::
* Using arbitrary objects as messages::
* 最佳化: 最佳化<17>.
* 其他資源: 其他資源<2>.

基礎 Logging 指南

* 什麼時候使用 logging::
* 一個簡單範例: 一個簡單範例<2>.
* Logging to a file::
* Logging variable data::
* Changing the format of displayed messages::
* Displaying the date/time in messages::
* Next Steps::

Advanced Logging Tutorial

* Logging Flow::
* Loggers::
* Handlers::
* Formatters::
* Configuring Logging::
* What happens if no configuration is provided::
* Configuring Logging for a Library::

Logging Levels

* Custom Levels::

Logging Cookbook

* Using logging in multiple modules::
* Logging from multiple threads::
* Multiple handlers and formatters::
* Logging to multiple destinations::
* Custom handling of levels::
* Configuration server example::
* Dealing with handlers that block::
* Sending and receiving logging events across a network::
* Adding contextual information to your logging output::
* Use of contextvars::
* Imparting contextual information in handlers::
* Logging to a single file from multiple processes::
* Using file rotation::
* Use of alternative formatting styles::
* Customizing LogRecord::
* Subclassing QueueHandler and QueueListener- a ZeroMQ example::
* Subclassing QueueHandler and QueueListener- a pynng example::
* An example dictionary-based configuration::
* Using a rotator and namer to customize log rotation processing::
* A more elaborate multiprocessing example::
* Inserting a BOM into messages sent to a SysLogHandler::
* Implementing structured logging::
* Customizing handlers with dictConfig(): Customizing handlers with dictConfig.
* Using particular formatting styles throughout your application::
* Configuring filters with dictConfig(): Configuring filters with dictConfig.
* Customized exception formatting::
* Speaking logging messages::
* Buffering logging messages and outputting them conditionally::
* Sending logging messages to email, with buffering: Sending logging messages to email with buffering.
* Formatting times using UTC (GMT) via configuration: Formatting times using UTC GMT via configuration.
* Using a context manager for selective logging::
* A CLI application starter template::
* A Qt GUI for logging::
* Logging to syslog with RFC5424 support::
* How to treat a logger like an output stream::
* Patterns to avoid::
* Other resources::

Sending and receiving logging events across a network

* Running a logging socket listener in production::

Adding contextual information to your logging output

* Using LoggerAdapters to impart contextual information::
* Using Filters to impart contextual information::

Using LoggerAdapters to impart contextual information

* Using objects other than dicts to pass contextual information::

Logging to a single file from multiple processes

* Using concurrent.futures.ProcessPoolExecutor: Using concurrent futures ProcessPoolExecutor.
* Deploying Web applications using Gunicorn and uWSGI::

Subclassing QueueHandler and QueueListener- a ZeroMQ example

* Subclass QueueHandler::
* Subclass QueueListener::

Subclassing QueueHandler and QueueListener- a pynng example

* Subclass QueueListener: Subclass QueueListener<2>.
* Subclass QueueHandler: Subclass QueueHandler<2>.

Using particular formatting styles throughout your application

* Using LogRecord factories::
* Using custom message objects::

Patterns to avoid

* Opening the same log file multiple times::
* Using loggers as attributes in a class or passing them as parameters::
* Adding handlers other than NullHandler to a logger in a library::
* Creating a lot of loggers::

如何使用正規表示式

* 簡介: 簡介<12>.
* Simple Patterns::
* Using Regular Expressions::
* More Pattern Power::
* Modifying Strings::
* Common Problems::
* Feedback::

Simple Patterns

* Matching Characters::
* Repeating Things::

Using Regular Expressions

* Compiling Regular Expressions::
* The Backslash Plague::
* Performing Matches::
* Module-Level Functions: Module-Level Functions<2>.
* Compilation Flags::

More Pattern Power

* More Metacharacters::
* Grouping::
* Non-capturing and Named Groups::
* Lookahead Assertions::

Modifying Strings

* Splitting Strings::
* Search and Replace: Search and Replace<2>.

Common Problems

* Use String Methods::
* match() versus search(): match versus search.
* Greedy versus Non-Greedy::
* Using re.VERBOSE: Using re VERBOSE.

Socket 程式設計指南

* Sockets::
* 建立一個 Socket::
* 使用一個 Socket::
* 結束連線::
* 非阻塞的 Sockets::

Sockets

* 歷史::

建立一個 Socket

* IPC::

使用一個 Socket

* 二進位資料::

結束連線

* Sockets 何時銷毀::

排序技法

* 基礎排序::
* 鍵函式 (key functions): 鍵函式 key functions.
* Operator Module Functions and Partial Function Evaluation::
* 升冪與降冪::
* 排序穩定性與複合排序::
* 裝飾-排序-移除裝飾 (decorate-sort-undecorate): 裝飾-排序-移除裝飾 decorate-sort-undecorate.
* 比較函式 (comparison functions): 比較函式 comparison functions.
* 雜項說明::
* Partial Sorts::

Unicode HOWTO

* Introduction to Unicode::
* Python's Unicode Support::
* Reading and Writing Unicode Data::
* 致謝: 致謝<10>.

Introduction to Unicode

* 定義::
* Encodings::
* References: References<3>.

Python's Unicode Support

* The String Type::
* Converting to Bytes::
* Unicode Literals in Python Source Code::
* Unicode Properties::
* Comparing Strings::
* Unicode Regular Expressions::
* References: References<4>.

Reading and Writing Unicode Data

* Unicode filenames::
* Tips for Writing Unicode-aware Programs::
* References: References<5>.

Tips for Writing Unicode-aware Programs

* Converting Between File Encodings::
* Files in an Unknown Encoding::

如何使用 urllib 套件取得網路資源

* 簡介: 簡介<13>.
* 從 URL 取得資源::
* Handling Exceptions::
* info and geturl::
* Openers and Handlers::
* Basic Authentication::
* Proxies::
* Sockets and Layers::
* 註解: 註解<2>.

從 URL 取得資源

* Data::
* Headers::

Handling Exceptions

* URLError::
* HTTPError::
* Wrapping it Up::

HTTPError

* Error Codes::

Wrapping it Up

* Number 1::
* Number 2::

Argparse 教學

* 概念::
* 基本用法: 基本用法<4>.
* 位置引數的介紹::
* 可選引數的介紹::
* 組合位置引數和可選引數::
* 更進階一點::
* 如何翻譯 argparse 輸出::
* 結論::

可選引數的介紹

* 短選項::

更進階一點

* 指定不明確的引數::
* 相互衝突的選項::

ipaddress 模組介紹

* Creating Address/Network/Interface objects::
* Inspecting Address/Network/Interface Objects::
* Networks as lists of Addresses::
* Comparisons: Comparisons<2>.
* Using IP Addresses with other modules::
* Getting more detail when instance creation fails::

Creating Address/Network/Interface objects

* A Note on IP Versions::
* IP Host Addresses::
* 定義網路::
* Host Interfaces::

使用 DTrace 和 SystemTap 檢測 CPython

* 啟用靜態標記::
* 靜態 DTrace 探針::
* 靜態 SystemTap 標記::
* 可用的靜態標記::
* SystemTap Tapsets::
* 範例: 範例<54>.

Python 對 Linux perf 分析器的支援

* 如何啟用 perf 分析支援::
* 如何獲得最佳結果::
* How to work without frame pointers::

註釋 (annotation) 最佳實踐

* 在 Python 3.10 及更高版本中存取物件的註釋字典: 在 Python 3 10 及更高版本中存取物件的註釋字典.
* 在 Python 3.9 及更早版本中存取物件的註釋字典: 在 Python 3 9 及更早版本中存取物件的註釋字典.
* 手動取消字串化註釋::
* 任何 Python 版本中 __annotations__ 的最佳實踐::
* __annotations__ 奇異之處::

隔離擴充模組

* Who should read this::
* 背景: 背景<2>.
* Making Modules Safe with Multiple Interpreters::
* Heap Types: Heap Types<2>.
* Open Issues::

背景

* Enter Per-Module State::
* Isolated Module Objects::
* Surprising Edge Cases::

Making Modules Safe with Multiple Interpreters

* Managing Global State::
* Managing Per-Module State::
* Opt-Out; Limiting to One Module Object per Process: Opt-Out Limiting to One Module Object per Process.
* Module State Access from Functions::

Heap Types

* Changing Static Types to Heap Types::
* Defining Heap Types::
* Garbage-Collection Protocol::
* Module State Access from Classes::
* Module State Access from Regular Methods::
* Module State Access from Slot Methods, Getters and Setters: Module State Access from Slot Methods Getters and Setters.
* Lifetime of the Module State::

Garbage-Collection Protocol

* tp_traverse in Python 3.8 and lower: tp_traverse in Python 3 8 and lower.
* Delegating tp_traverse::
* Defining tp_dealloc::
* Not overriding tp_free::
* Avoiding PyObject_New::

Open Issues

* Per-Class Scope::
* Lossless Conversion to Heap Types::

timer file descriptor HOWTO

* Examples: Examples<2>.

The Python 2.3 Method Resolution Order

* The beginning::
* The C3 Method Resolution Order::
* 範例: 範例<55>.
* Bad Method Resolution Orders::
* The end::
* Resources::

C API Extension Support for Free Threading

* Identifying the Free-Threaded Build in C::
* Module Initialization::
* General API Guidelines::
* Borrowed References::
* Memory Allocation APIs::
* Thread State and GIL APIs::
* Protecting Internal Extension State::
* Building Extensions for the Free-Threaded Build::

Module Initialization

* Multi-Phase Initialization::
* Single-Phase Initialization::

General API Guidelines

* Container Thread Safety::

Container Thread Safety

* PyDict_Next::

Building Extensions for the Free-Threaded Build

* Limited C API and Stable ABI::
* Windows: Windows<73>.

Python 常見問題

* 一般的 Python 常見問答集::
* 程式開發常見問答集::
* 設計和歷史常見問答集::
* 函式庫和擴充功能的常見問題::
* 擴充/嵌入常見問題集::
* 在 Windows 使用 Python 的常見問答集::
* 圖形使用者介面常見問答集::
* 「為什麼 Python 被安裝在我的機器上？」常見問答集::

一般的 Python 常見問答集

* 一般資訊::
* 在真實世界中的 Python::

一般資訊

* 什麼是 Python？::
* 什麼是 Python 軟體基金會？::
* 使用 Python 時有任何版權限制嗎？::
* 當初為什麼 Python 會被創造出來？::
* 什麼是 Python 擅長的事情？::
* Python 的版本編號系統是如何運作的？::
* 我要如何得到 Python 的原始碼複本？::
* 我要如何取得 Python 的說明文件？::
* 我從來沒有寫過程式，有沒有 Python 的教學？::
* 有沒有 Python 專屬的新聞群組或郵件討論群？::
* 如何取得 Python 的 beta 測試版本？::
* 如何提交 Python 的錯誤報告和修補程式？::
* 是否有關於 Python 的任何已出版文章可供參考？::
* 有沒有關於 Python 的書？::
* www.python.org 的真實位置在哪裡？: www python org 的真實位置在哪裡？.
* 為什麼要取名為 Python？::
* 我需要喜歡「Monty Python 的飛行馬戲團」嗎？::

在真實世界中的 Python

* Python 的穩定性如何？::
* 有多少人在使用 Python？::
* 有沒有任何重要的專案使用 Python 完成開發？::
* Python 未來預期會有哪些新的開發？::
* 對 Python 提出不相容的變更建議是否適當？::
* Python 對於入門的程式設計師而言是否為好的語言？::

程式開發常見問答集

* 常見問題::
* 核心語言::
* 數字和字串::
* Performance: Performance<4>.
* Sequences (Tuples/Lists): Sequences Tuples/Lists.
* 物件::
* 模組: 模組<5>.

常見問題

* 是否有可以使用在程式碼階段,具有中斷點,步驟執行等功能的除錯器？: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？.
* 有沒有工具能夠幫忙找 bug 或執行靜態分析？::
* 如何從 Python 腳本建立獨立的二進位檔案？::
* Python 程式碼是否有編碼標準或風格指南？::

核心語言

* 為什麼當變數有值時，我仍得到錯誤訊息 UnboundLocalError？::
* Python 的區域變數和全域變數有什麼規則？::
* Why do lambdas defined in a loop with different values all return the same result?::
* 如何跨模組共享全域變數？::
* What are the "best practices" for using import in a module?::
* Why are default values shared between objects?::
* How can I pass optional or keyword parameters from one function to another?::
* 引數 (arguments) 和參數 (parameters) 有什麼區別？: 引數 arguments 和參數 parameters 有什麼區別？.
* 為什麼更改 list 'y' 也會更改 list 'x'？::
* How do I write a function with output parameters (call by reference)?: How do I write a function with output parameters call by reference ?.
* How do you make a higher order function in Python?::
* 如何在 Python 中複製物件？::
* 如何找到物件的方法或屬性？::
* 我的程式碼如何發現物件的名稱？::
* What's up with the comma operator's precedence?::
* 是否有等效於 C 的 "?;" 三元運算子？: 是否有等效於 C 的 "? " 三元運算子？.
* Is it possible to write obfuscated one-liners in Python?::
* What does the slash(/) in the parameter list of a function mean?: What does the slash / in the parameter list of a function mean?.

數字和字串

* 如何指定十六進位和八進位整數？::
* 為什麼 -22 // 10 回傳 -3？::
* How do I get int literal attribute instead of SyntaxError?::
* 如何將字串轉換為數字？::
* 如何將數字轉換為字串？::
* How do I modify a string in place?::
* How do I use strings to call functions/methods?::
* Is there an equivalent to Perl's chomp() for removing trailing newlines from strings?: Is there an equivalent to Perl's chomp for removing trailing newlines from strings?.
* Is there a scanf() or sscanf() equivalent?: Is there a scanf or sscanf equivalent?.
* 'UnicodeDecodeError' 或 'UnicodeEncodeErro' 錯誤是什麼意思？::
* Can I end a raw string with an odd number of backslashes?::

Performance

* 我的程式太慢了。我該如何加快速度？::
* What is the most efficient way to concatenate many strings together?::

Sequences (Tuples/Lists)

* How do I convert between tuples and lists?::
* What's a negative index?::
* How do I iterate over a sequence in reverse order?::
* How do you remove duplicates from a list?::
* How do you remove multiple items from a list::
* How do you make an array in Python?::
* How do I create a multidimensional list?::
* How do I apply a method or function to a sequence of objects?::
* Why does a_tuple[i] += ['item'] raise an exception when the addition works?::
* I want to do a complicated sort; can you do a Schwartzian Transform in Python?: I want to do a complicated sort can you do a Schwartzian Transform in Python?.
* How can I sort one list by values from another list?::

物件

* 什麼是類別 (class)？: 什麼是類別 class ？.
* 什麼是方法 (method)？: 什麼是方法 method ？.
* What is self?::
* How do I check if an object is an instance of a given class or of a subclass of it?::
* What is delegation?::
* How do I call a method defined in a base class from a derived class that extends it?::
* How can I organize my code to make it easier to change the base class?::
* How do I create static class data and static class methods?::
* How can I overload constructors (or methods) in Python?: How can I overload constructors or methods in Python?.
* I try to use __spam and I get an error about _SomeClassName__spam.: I try to use __spam and I get an error about _SomeClassName__spam.
* My class defines __del__ but it is not called when I delete the object.: My class defines __del__ but it is not called when I delete the object.
* How do I get a list of all instances of a given class?::
* Why does the result of id() appear to be not unique?: Why does the result of id appear to be not unique?.
* 我什麼時候可以依靠 is 運算子進行識別性測試？::
* 子類別如何控制不可變實例中存儲的資料？::
* 如何快取方法呼叫？::

模組

* 如何建立 .pyc 檔案？: 如何建立 pyc 檔案？.
* 如何找到當前模組名稱？::
* How can I have modules that mutually import each other?::
* __import__('x.y.z') 回傳 <module 'x'>，那我怎麼得到 z？: __import__ 'x y z' 回傳 <module 'x'>，那我怎麼得到 z？.
* 當我編輯需要引入的模組並重新引入它時，更動沒有反應出來。為什麼會這樣？::

設計和歷史常見問答集

* 為什麼 Python 使用縮排將陳述式進行分組？::
* 為什麼我會從簡單的數學運算得到奇怪的結果？::
* 為何浮點數運算如此不精確？::
* 為什麼 Python 字串不可變動？::
* 為何「self」在方法 (method) 定義和呼叫時一定要明確使用？: 為何「self」在方法 method 定義和呼叫時一定要明確使用？.
* 為何我不能在運算式 (expression) 中使用指派運算？: 為何我不能在運算式 expression 中使用指派運算？.
* 為何 Python 對於一些功能實作使用方法（像是 list.index()），另一些使用函式（像是 len(list)）？: 為何 Python 對於一些功能實作使用方法（像是 list index ），另一些使用函式（像是 len list ）？.
* 為何 join() 是字串方法而非串列 (list) 或元組 (tuple) 方法？: 為何 join 是字串方法而非串列 list 或元組 tuple 方法？.
* 例外處理有多快？::
* 為什麼 Python 內沒有 switch 或 case 陳述式？::
* 為何不能在直譯器上模擬執行緒，而要使用作業系統的特定實作方式？::
* 為何 lambda 運算式不能包含陳述式？::
* Python 可以被編譯成機器語言、C 語言或其他種語言嗎？::
* Python 如何管理記憶體？::
* 為何 CPython 不使用更多傳統的垃圾回收機制？::
* 當 CPython 結束時，為何所有的記憶體不會被釋放？::
* 為何要把元組 (tuple) 和串列 (list) 分成兩個資料型態？: 為何要把元組 tuple 和串列 list 分成兩個資料型態？.
* 串列 (list) 在 CPython 中是怎麼實作的？: 串列 list 在 CPython 中是怎麼實作的？.
* 字典 (dictionaries) 在 CPython 中是怎麼實作的？: 字典 dictionaries 在 CPython 中是怎麼實作的？.
* 為何字典的鍵一定是不可變的？::
* 為何 list.sort() 不是回傳排序過的串列？: 為何 list sort 不是回傳排序過的串列？.
* 如何在 Python 中指定和強制使用一個介面規範 (interface spec)？: 如何在 Python 中指定和強制使用一個介面規範 interface spec ？.
* 為何沒有 goto 語法？::
* 為何純字串 (r-string) 不能以反斜線結尾？: 為何純字串 r-string 不能以反斜線結尾？.
* 為何 Python 沒有屬性賦值的 with 陳述式？::
* 為何產生器 (generator) 不支援 with 陳述式？: 為何產生器 generator 不支援 with 陳述式？.
* 為何 if、while、def、class 陳述式裡需要冒號？::
* 為何 Python 允許在串列和元組末端加上逗號？::

函式庫和擴充功能的常見問題

* 常見函式問題::
* 常見課題::
* 執行緒::
* 輸入與輸出::
* 網路 (Network)/網際網路 (Internet) 程式: 網路 Network /網際網路 Internet 程式.
* 資料庫::
* 數學和數值::

常見函式問題

* 我如何找到執行任務 X 的模組或應用程式？::
* 哪裡可以找到 math.py (socket.py, regex.py, 等...) 來源檔案？: 哪裡可以找到 math py socket py regex py 等 來源檔案？.
* 我如何使 Python script 執行在 Unix？::
* 是否有適用於 Python 的 curses/termcap 套件？::
* Python 中是否有等同於 C 的 onexit() 的函式？: Python 中是否有等同於 C 的 onexit 的函式？.
* 為什麼我的信號處理程式不起作用？::

常見課題

* 如何測試 Python 程式或元件？::
* How do I create documentation from doc strings?::
* How do I get a single keypress at a time?::

執行緒

* 如何使用執行緒編寫程式？::
* 我的執行緒似乎都沒有運行：為什麼？::
* How do I parcel out work among a bunch of worker threads?::
* What kinds of global value mutation are thread-safe?::
* 不能擺脫全局直譯器鎖嗎？::

輸入與輸出

* 如何刪除檔案？（以及其他檔案問題...）: 如何刪除檔案？（以及其他檔案問題 ）.
* 如何複製檔案？::
* 如何讀取（或寫入）二進位制資料？::
* I can't seem to use os.read() on a pipe created with os.popen(); why?: I can't seem to use os read on a pipe created with os popen ; why?.
* 如何存取序列 (RS232) 連接埠？: 如何存取序列 RS232 連接埠？.
* 為什麼關閉 sys.stdout (stdin, stderr) 並沒有真正關閉它？: 為什麼關閉 sys stdout stdin stderr 並沒有真正關閉它？.

網路 (Network)/網際網路 (Internet) 程式

* Python 有哪些 WWW 工具？::
* 我應該使用什麼模組來輔助產生 HTML？::
* 如何從 Python 腳本發送郵件？::
* How do I avoid blocking in the connect() method of a socket?: How do I avoid blocking in the connect method of a socket?.

資料庫

* Python 中是否有任何資料庫套件的介面？::
* How do you implement persistent objects in Python?::

數學和數值

* 如何在 Python 中生成隨機數？::

擴充/嵌入常見問題集

* 我可以在 C 中建立自己的函式嗎？::
* 我可以在 C++ 中建立自己的函式嗎？::
* 寫 C 很難；還有其他選擇嗎？::
* 如何從 C 執行任意 Python 陳述式？::
* How can I evaluate an arbitrary Python expression from C?::
* 如何從 Python 物件中提取 C 值？::
* 如何使用 Py_BuildValue() 建立任意長度的元組？: 如何使用 Py_BuildValue 建立任意長度的元組？.
* 如何從 C 呼叫物件的方法？::
* 我如何捕捉 PyErr_Print() 的輸出（或任何印出到 stdout/stderr 的東西）？: 我如何捕捉 PyErr_Print 的輸出（或任何印出到 stdout/stderr 的東西）？.
* 如何從 C 存取用 Python 編寫的模組？::
* How do I interface to C++ objects from Python?::
* 我使用安裝檔案新增了一個模組，但 make 失敗了；為什麼？::
* 如何為擴充套件除錯？::
* 我想在我的 Linux 系統上編譯一個 Python 模組，但是缺少一些檔案。為什麼？::
* 如何從「無效輸入」區分出「不完整輸入」？::
* 如何找到未定義的 g++ 符號 __builtin_new 或 __pure_virtual？::
* Can I create an object class with some methods implemented in C and others in Python (e.g. through inheritance)?: Can I create an object class with some methods implemented in C and others in Python e g through inheritance ?.

在 Windows 使用 Python 的常見問答集

* 如何在 Windows 作業系統裡運行 Python 程式？::
* 如何使 Python 腳本可以執行？::
* 為什麼 Python 有時需要這麼長的時間才能開始？::
* 如何從 Python 腳本製作可執行檔？::
* *.pyd 檔是否與 DLL 相同？: * pyd 檔是否與 DLL 相同？.
* 如何將 Python 嵌入 Windows 應用程式中？::
* 如何防止編輯器在我的 Python 原始碼中插入 tab？::
* 如何在不阻塞的情況下檢查 keypress？::
* 如何解決遺漏 api-ms-win-crt-runtime-l1-1-0.dll 的錯誤？: 如何解決遺漏 api-ms-win-crt-runtime-l1-1-0 dll 的錯誤？.

圖形使用者介面常見問答集

* 圖形使用者介面 (GUI) 的常見問題: 圖形使用者介面 GUI 的常見問題.
* Python 有哪些 GUI 套件？::
* Tkinter 的問答::

Tkinter 的問答

* 如何凍結 Tkinter 應用程式？::
* 是否可以在等待 I/O 時處理 Tk 事件？::
* 我無法讓鍵繫結 (key binding) 在 Tkinter 中作用：為什麼？: 我無法讓鍵繫結 key binding 在 Tkinter 中作用：為什麼？.

「為什麼 Python 被安裝在我的機器上？」常見問答集

* 什麼是 Python？: 什麼是 Python？<2>.
* 為什麼 Python 被安裝在我的機器上?::
* 我能夠自行刪除 Python 嗎？::

已棄用項目

* Python 3.14 中待移除的項目: Python 3 14 中待移除的項目<3>.
* Python 3.15 中待移除的項目: Python 3 15 中待移除的項目<3>.
* Python 3.16 中待移除的項目: Python 3 16 中待移除的項目<2>.
* 未來版本中的待移除項目: 未來版本中的待移除項目<3>.
* C API 的棄用項目::

C API 的棄用項目

* Python 3.14 中待移除的項目: Python 3 14 中待移除的項目<4>.
* Python 3.15 中待移除的項目: Python 3 15 中待移除的項目<4>.
* 未來版本中的待移除項目: 未來版本中的待移除項目<4>.

關於這些說明文件

* Python 文件的貢獻者們::

處理錯誤 (Bug)

* 說明文件的錯誤::
* 使用 Python 問題追蹤系統::
* 開始讓自己貢獻 Python::

沿革與授權

* 軟體沿革::
* 關於存取或以其他方式使用 Python 的合約條款::
* 被收錄軟體的授權與致謝::

關於存取或以其他方式使用 Python 的合約條款

* 用於 PYTHON 3.13.0rc2 的 PSF 授權合約: 用於 PYTHON 3 13 0rc2 的 PSF 授權合約.
* 用於 PYTHON 2.0 的 BEOPEN.COM 授權合約: 用於 PYTHON 2 0 的 BEOPEN COM 授權合約.
* 用於 PYTHON 1.6.1 的 CNRI 授權合約: 用於 PYTHON 1 6 1 的 CNRI 授權合約.
* 用於 PYTHON 0.9.0 至 1.2 的 CWI 授權合約: 用於 PYTHON 0 9 0 至 1 2 的 CWI 授權合約.
* 用於 PYTHON 3.13.0rc2 說明文件內程式碼的 ZERO-CLAUSE BSD 授權: 用於 PYTHON 3 13 0rc2 說明文件內程式碼的 ZERO-CLAUSE BSD 授權.

被收錄軟體的授權與致謝

* Mersenne Twister::
* Sockets: Sockets<2>.
* 非同步 socket 服務::
* Cookie 管理::
* 執行追蹤::
* UUencode 與 UUdecode 函式::
* XML 遠端程序呼叫::
* test_epoll::
* Select kqueue::
* SipHash24::
* strtod 與 dtoa::
* OpenSSL: OpenSSL<2>.
* expat::
* libffi::
* zlib: zlib<3>.
* cfuhash::
* libmpdec::
* W3C C14N 測試套件::
* mimalloc::
* asyncio: asyncio<12>.
* Global Unbounded Sequences (GUS): Global Unbounded Sequences GUS.



File: python.info,  Node: Python 有什麼新功能？,  Next: Python 教學,  Prev: Top,  Up: Top

1 Python 有什麼新功能？
***********************

「Python 有什麼新功能」這系列的說明是讓使用者知道 Python 各個主要更新版
本之間的重大改變的地方。對於希望在新版本釋出時立即了解版本差異的使用者們
來說，這些說明被歸類為「必讀」的等級。

* Menu:

* What's New In Python 3.13: What's New In Python 3 13.
* Python 3.12 有什麼新功能: Python 3 12 有什麼新功能.
* Python 3.11 有什麼新功能: Python 3 11 有什麼新功能.
* Python 3.10 有什麼新功能: Python 3 10 有什麼新功能.
* Python 3.9 有什麼新功能: Python 3 9 有什麼新功能.
* Python 3.8 有什麼新功能: Python 3 8 有什麼新功能.
* Python 3.7 有什麼新功能: Python 3 7 有什麼新功能.
* Python 3.6 有什麼新功能: Python 3 6 有什麼新功能.
* Python 3.4 有什麼新功能: Python 3 4 有什麼新功能.
* Python 3.4 有什麼新功能: Python 3 4 有什麼新功能<2>.
* Python 3.3 有什麼新功能: Python 3 3 有什麼新功能.
* Python 3.2 有什麼新功能: Python 3 2 有什麼新功能.
* Python 3.1 有什麼新功能: Python 3 1 有什麼新功能.
* Python 3.0 有什麼新功能: Python 3 0 有什麼新功能.
* Python 2.7 有什麼新功能: Python 2 7 有什麼新功能.
* Python 2.6 有什麼新功能: Python 2 6 有什麼新功能.
* Python 2.5 有什麼新功能: Python 2 5 有什麼新功能.
* Python 2.4 有什麼新功能: Python 2 4 有什麼新功能.
* Python 2.3 有什麼新功能: Python 2 3 有什麼新功能.
* Python 2.2 有什麼新功能: Python 2 2 有什麼新功能.
* Python 2.1 有什麼新功能: Python 2 1 有什麼新功能.
* Python 2.0 有什麼新功能: Python 2 0 有什麼新功能.
* Changelog（更動日誌）::


File: python.info,  Node: What's New In Python 3 13,  Next: Python 3 12 有什麼新功能,  Up: Python 有什麼新功能？

1.1 What's New In Python 3.13
=============================


Editor: Thomas Wouters

This article explains the new features in Python 3.13, compared to 3.12.
Python 3.13 will be released on October 1, 2024.  For full details, see
the *note changelog: 122.

也參考
......

PEP 719(1) - Python 3.13 Release Schedule

     備註: Prerelease users should be aware that this document is
     currently in draft form.  It will be updated substantially as
     Python 3.13 moves towards release, so it's worth checking back even
     after reading earlier versions.

* Menu:

* Summary: Summary -- Release Highlights. Release Highlights
* New Features::
* Other Language Changes::
* New Modules::
* Improved Modules::
* Optimizations::
* Removed Modules And APIs::
* New Deprecations::
* CPython Bytecode Changes::
* C API Changes::
* Build Changes::
* Porting to Python 3.13: Porting to Python 3 13.
* Regression Test Changes::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0719/


File: python.info,  Node: Summary -- Release Highlights,  Next: New Features,  Up: What's New In Python 3 13

1.1.1 Summary - Release Highlights
----------------------------------

Python 3.13 will be 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 a new *note
interactive interpreter: 124., experimental support for running in a
*note free-threaded mode: 125.( PEP 703(1)), and a *note Just-In-Time
compiler: 126.( PEP 744(2)).

Error messages continue to improve, with tracebacks now highlighted in
color by default.  The *note locals(): 127. builtin now has *note
defined semantics: 128. for changing the returned mapping, and type
parameters now support default values.

The library changes contain removal of deprecated APIs and modules, as
well as the usual improvements in user-friendliness and correctness.
Several legacy standard library modules have now *note been removed:
129.following their deprecation in Python 3.11 ( PEP 594(3)).

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 *note Library Reference: 12a.
and *note Language Reference: 12b.  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 *note Porting
to Python 3.13: 12c. for guidance on upgrading from earlier versions of
Python.

__________________________________________________________________

Interpreter improvements:

   * A greatly improved *note interactive interpreter: 124. and *note
     improved error messages: 12d.

   * PEP 667(4): The *note locals(): 127. builtin now has *note defined
     semantics: 128. when mutating the returned mapping.  Python
     debuggers and similar tools may now more reliably update local
     variables in optimized scopes even during concurrent code
     execution.

   * PEP 703(5): CPython 3.13 has experimental support for running with
     the *note global interpreter lock: 12e. disabled.  See *note
     Free-threaded CPython: 125. for more details.

   * PEP 744(6): A basic *note JIT compiler: 126. was added.  It is
     currently disabled by default (though we may turn it on later).
     Performance improvements are modest - we expect to improve this
     over the next few releases.

   * Color support in the new *note interactive interpreter: 124, as
     well as in *note tracebacks: 12d. and *note doctest: 12f. output.
     This can be disabled through the *note PYTHON_COLORS: 130. and
     NO_COLOR(7) environment variables.

Python data model improvements:

   * *note __static_attributes__: 131. stores the names of attributes
     accessed through ‘self.X’ in any function in a class body.

   * ‘__firstlineno__’ records the first line number of a class
     definition.

Significant improvements in the standard library:

   * Add a new *note PythonFinalizationError: 132. exception, raised
     when an operation is blocked during *note finalization: 133.

   * The *note argparse: 5. module now supports deprecating command-line
     options, positional arguments, and subcommands.

   * The new functions *note base64.z85encode(): 134. and *note
     base64.z85decode(): 135. support encoding and decoding Z85 data(8).

   * The *note copy: 1e. module now has a *note copy.replace(): 136.
     function, with support for many builtin types and any class
     defining the *note __replace__(): 137. method.

   * The *note dbm.sqlite3: 2d. module is now the default *note dbm: 29.
     backend.

   * The *note os: 91. module has a *note suite of new functions: 138.
     for working with Linux's timer notification file descriptors.

   * The *note random: a6. module now has a *note command-line
     interface: 139.

Security improvements:

   * *note ssl.create_default_context(): 13a. sets *note
     ssl.VERIFY_X509_PARTIAL_CHAIN: 13b. and *note
     ssl.VERIFY_X509_STRICT: 13c. as default flags.

C API improvements:

   * The *note Py_mod_gil: 13d. slot is now used to indicate that an
     extension module supports running with the *note GIL: 13e.
     disabled.

   * The *note PyTime C API: 13f. has been added, providing access to
     system clocks.

   * *note PyMutex: 140. is a new lightweight mutex that occupies a
     single byte.

New typing features:

   * PEP 696(9): Type parameters (*note typing.TypeVar: 141, *note
     typing.ParamSpec: 142, and *note typing.TypeVarTuple: 143.) now
     support defaults.

   * PEP 702(10): The new *note warnings.deprecated(): 144. decorator
     adds support for marking deprecations in the type system.

   * PEP 705(11): *note typing.ReadOnly: 145. can be used to mark an
     item of a *note typing.TypedDict: 146. as read-only for type
     checkers.

   * PEP 742(12): *note typing.TypeIs: 147. provides more intuitive type
     narrowing behavior, as an alternative to *note typing.TypeGuard:
     148.

Platform support:

   * PEP 730(13): Apple's iOS is now an *note officially supported
     platform: 149, at tier 3(14).  Official Android support ( PEP
     738(15)) is in the works as well.

   * ‘wasm32-wasi’ is now supported as a tier 2(16) platform.

   * ‘wasm32-emscripten’ is no longer an officially supported platform.

Important removals:

   * *note PEP 594: 129.: The remaining 19 "dead batteries" have been
     removed from the standard library: ‘aifc’, ‘audioop’, ‘cgi’,
     ‘cgitb’, ‘chunk’, ‘crypt’, ‘imghdr’, ‘mailcap’, ‘msilib’, ‘nis’,
     ‘nntplib’, ‘ossaudiodev’, ‘pipes’, ‘sndhdr’, ‘spwd’, ‘sunau’,
     ‘telnetlib’, ‘uu’ and ‘xdrlib’.

   * Remove the ‘2to3’ tool and ‘lib2to3’ module (deprecated in Python
     3.11).

   * Remove the ‘tkinter.tix’ module (deprecated in Python 3.6).

   * Remove ‘locale.resetlocale()’.

   * Remove ‘typing.io’ and ‘typing.re’.

   * Remove chained *note classmethod: 14a. descriptors.

Release schedule changes:

PEP 602(17) ("Annual Release Cycle for Python") has been updated to
extend the full support ('bugfix') period for new releases to two years.
This updated policy means that:

   * Python 3.9-3.12 have one and a half years of full support, followed
     by three and a half years of security fixes.

   * Python 3.13 and later have two years of full support, followed by
     three years of security fixes.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0703/

   (2) https://peps.python.org/pep-0744/

   (3) https://peps.python.org/pep-0594/

   (4) https://peps.python.org/pep-0667/

   (5) https://peps.python.org/pep-0703/

   (6) https://peps.python.org/pep-0744/

   (7) https://no-color.org/

   (8) https://rfc.zeromq.org/spec/32/

   (9) https://peps.python.org/pep-0696/

   (10) https://peps.python.org/pep-0702/

   (11) https://peps.python.org/pep-0705/

   (12) https://peps.python.org/pep-0742/

   (13) https://peps.python.org/pep-0730/

   (14) https://peps.python.org/pep-0011/#tier-3

   (15) https://peps.python.org/pep-0738/

   (16) https://peps.python.org/pep-0011/#tier-2

   (17) https://peps.python.org/pep-0602/


File: python.info,  Node: New Features,  Next: Other Language Changes,  Prev: Summary -- Release Highlights,  Up: What's New In Python 3 13

1.1.2 New Features
------------------

* Menu:

* A better interactive interpreter::
* Improved error messages::
* Free-threaded CPython::
* An experimental just-in-time (JIT) compiler: An experimental just-in-time JIT compiler.
* Defined mutation semantics for locals(): Defined mutation semantics for locals.
* Support for mobile platforms::
* Incremental garbage collection::


File: python.info,  Node: A better interactive interpreter,  Next: Improved error messages,  Up: New Features

1.1.2.1 A better interactive interpreter
........................................

Python now uses a new *note interactive: 14d. shell by default, based on
code from the PyPy project(1).  When the user starts the *note REPL:
14e. from an interactive terminal, the following new features are now
supported:

   * Multiline editing with history preservation.

   * Direct support for REPL-specific commands like ‘help’, ‘exit’, and
     ‘quit’, without the need to call them as functions.

   * Prompts and tracebacks with *note color enabled by default: 14f.

   * Interactive help browsing using ‘F1’ with a separate command
     history.

   * History browsing using ‘F2’ that skips output as well as the *note
     >>>: 150. and *note ...: 151. prompts.

   * "Paste mode" with ‘F3’ that makes pasting larger blocks of code
     easier (press ‘F3’ again to return to the regular prompt).

To disable the new interactive shell, set the *note PYTHON_BASIC_REPL:
152. environment variable.  For more on interactive mode, see *note
互動模式: 153.

(Contributed by Pablo Galindo Salgado, Łukasz Langa, and Lysandros
Nikolaou in gh-111201(2) based on code from the PyPy project.  Windows
support contributed by Dino Viehland and Anthony Shaw.)

   ---------- Footnotes ----------

   (1) https://pypy.org/

   (2) https://github.com/python/cpython/issues/111201


File: python.info,  Node: Improved error messages,  Next: Free-threaded CPython,  Prev: A better interactive interpreter,  Up: New Features

1.1.2.2 Improved error messages
...............................

   * The interpreter now uses color by default when displaying
     tracebacks in the terminal.  This feature *note can be controlled:
     14f. via the new *note PYTHON_COLORS: 130. environment variable as
     well as the canonical NO_COLOR(1) and FORCE_COLOR(2) environment
     variables.  (Contributed by Pablo Galindo Salgado in gh-112730(3).)

   * A common mistake is to write a script with the same name as a
     standard library module.  When this results in errors, we now
     display a more helpful error message:

          $ python random.py
          Traceback (most recent call last):
            File "/home/me/random.py", line 1, in <module>
              import random
            File "/home/me/random.py", line 3, in <module>
              print(random.randint(5))
                    ^^^^^^^^^^^^^^
          AttributeError: module 'random' has no attribute 'randint' (consider renaming '/home/me/random.py' since it has the same name as the standard library module named 'random' and the import system gives it precedence)

     Similarly, if a script has the same name as a third-party module
     that it attempts to import and this results in errors, we also
     display a more helpful error message:

          $ python numpy.py
          Traceback (most recent call last):
            File "/home/me/numpy.py", line 1, in <module>
              import numpy as np
            File "/home/me/numpy.py", line 3, in <module>
              np.array([1, 2, 3])
              ^^^^^^^^
          AttributeError: module 'numpy' has no attribute 'array' (consider renaming '/home/me/numpy.py' if it has the same name as a third-party module you intended to import)

     (Contributed by Shantanu Jain in gh-95754(4).)

   * The error message now tries to suggest the correct keyword argument
     when an incorrect keyword argument is passed to a function.

          >>> "Better error messages!".split(max_split=1)
          Traceback (most recent call last):
            File "<python-input-0>", line 1, in <module>
              "Better error messages!".split(max_split=1)
              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^
          TypeError: split() got an unexpected keyword argument 'max_split'. Did you mean 'maxsplit'?

     (Contributed by Pablo Galindo Salgado and Shantanu Jain in
     gh-107944(5).)

   ---------- Footnotes ----------

   (1) https://no-color.org/

   (2) https://force-color.org/

   (3) https://github.com/python/cpython/issues/112730

   (4) https://github.com/python/cpython/issues/95754

   (5) https://github.com/python/cpython/issues/107944


File: python.info,  Node: Free-threaded CPython,  Next: An experimental just-in-time JIT compiler,  Prev: Improved error messages,  Up: New Features

1.1.2.3 Free-threaded CPython
.............................

CPython now has experimental support for running in a free-threaded
mode, with the *note global interpreter lock: 12e. (GIL) disabled.  This
is an experimental feature and therefore is not enabled by default.  The
free-threaded mode requires a different executable, usually called
‘python3.13t’ or ‘python3.13t.exe’.  Pre-built binaries marked as
'free-threaded' can be installed as part of the official *note Windows:
156. and *note macOS: 157. installers, or CPython can be built from
source with the *note -disable-gil: 158. option.

Free-threaded execution allows for full utilization of the available
processing power by running threads in parallel on available CPU cores.
While not all software will benefit from this automatically, programs
designed with threading in mind will run faster on multi-core hardware.
'The free-threaded mode is experimental' and work is ongoing to improve
it: expect some bugs and a substantial single-threaded performance hit.
Free-threaded builds of CPython support optionally running with the GIL
enabled at runtime using the environment variable *note PYTHON_GIL: 159.
or the command-line option *note -X gil: 15a.

To check if the current interpreter supports free-threading, *note
python -VV: 15b. and *note sys.version: 15c. contain "experimental
free-threading build".  The new ‘sys._is_gil_enabled()’ function can be
used to check whether the GIL is actually disabled in the running
process.

C-API extension modules need to be built specifically for the
free-threaded build.  Extensions that support running with the *note
GIL: 13e. disabled should use the *note Py_mod_gil: 13d. slot.
Extensions using single-phase init should use *note
PyUnstable_Module_SetGIL(): 15d. to indicate whether they support
running with the GIL disabled.  Importing C extensions that don't use
these mechanisms will cause the GIL to be enabled, unless the GIL was
explicitly disabled with the *note PYTHON_GIL: 159. environment variable
or the *note -X gil=0: 15a. option.  pip 24.1 or newer is required to
install packages with C extensions in the free-threaded build.

也參考
......

PEP 703(1) "Making the Global Interpreter Lock Optional in CPython"
contains rationale and information surrounding this work.

Porting Extension Modules to Support Free-Threading(2): A
community-maintained porting guide for extension authors.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0703/

   (2) https://py-free-threading.github.io/porting/


File: python.info,  Node: An experimental just-in-time JIT compiler,  Next: Defined mutation semantics for locals,  Prev: Free-threaded CPython,  Up: New Features

1.1.2.4 An experimental just-in-time (JIT) compiler
...................................................

When CPython is configured and built using the
‘--enable-experimental-jit’ option, a just-in-time (JIT) compiler is
added which may speed up some Python programs.  On Windows, use
‘PCbuild/build.bat --experimental-jit’ to enable the JIT or
‘--experimental-jit-interpreter’ to enable the Tier 2 interpreter.
Build requirements and further supporting information are contained
at(1) ‘Tools/jit/README.md’.

The ‘--enable-experimental-jit’ option takes these (optional) values,
defaulting to ‘yes’ if ‘--enable-experimental-jit’ is present without
the optional value.

   * ‘no’: Disable the entire Tier 2 and JIT pipeline.

   * ‘yes’: Enable the JIT. To disable the JIT at runtime, pass the
     environment variable ‘PYTHON_JIT=0’.

   * ‘yes-off’: Build the JIT but disable it by default.  To enable the
     JIT at runtime, pass the environment variable ‘PYTHON_JIT=1’.

   * ‘interpreter’: Enable the Tier 2 interpreter but disable the JIT.
     The interpreter can be disabled by running with ‘PYTHON_JIT=0’.

The internal architecture is roughly as follows:

   * We start with specialized 'Tier 1 bytecode'.  See *note What's new
     in 3.11: 15f. for details.

   * When the Tier 1 bytecode gets hot enough, it gets translated to a
     new purely internal intermediate representation (IR), called the
     'Tier 2 IR', and sometimes referred to as micro-ops ("uops").

   * The Tier 2 IR uses the same stack-based virtual machine as Tier 1,
     but the instruction format is better suited to translation to
     machine code.

   * We have several optimization passes for Tier 2 IR, which are
     applied before it is interpreted or translated to machine code.

   * There is a Tier 2 interpreter, but it is mostly intended for
     debugging the earlier stages of the optimization pipeline.  The
     Tier 2 interpreter can be enabled by configuring Python with
     ‘--enable-experimental-jit=interpreter’.

   * When the JIT is enabled, the optimized Tier 2 IR is translated to
     machine code, which is then executed.

   * The machine code translation process uses a technique called
     'copy-and-patch'.  It has no runtime dependencies, but there is a
     new build-time dependency on LLVM.

也參考
......

PEP 744(2)

(JIT by Brandt Bucher, inspired by a paper by Haoran Xu and Fredrik
Kjolstad.  Tier 2 IR by Mark Shannon and Guido van Rossum.  Tier 2
optimizer by Ken Jin.)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/blob/main/Tools/jit/README.md

   (2) https://peps.python.org/pep-0744/


File: python.info,  Node: Defined mutation semantics for locals,  Next: Support for mobile platforms,  Prev: An experimental just-in-time JIT compiler,  Up: New Features

1.1.2.5 Defined mutation semantics for ‘locals()’
.................................................

Historically, the expected result of mutating the return value of *note
locals(): 127. has been left to individual Python implementations to
define.  Starting from Python 3.13, PEP 667(1) standardises the
historical behaviour of CPython for most code execution scopes, but
changes *note optimized scopes: 161. (functions, generators, coroutines,
comprehensions, and generator expressions) to explicitly return
independent snapshots of the currently assigned local variables,
including locally referenced nonlocal variables captured in closures.

This change to the semantics of *note locals(): 127. in optimized scopes
also affects the default behaviour of code execution functions that
implicitly target ‘locals()’ if no explicit namespace is provided (such
as *note exec(): 162. and *note eval(): 163.).  In previous versions,
whether or not changes could be accessed by calling ‘locals()’ after
calling the code execution function was implementation-dependent.  In
CPython specifically, such code would typically appear to work as
desired, but could sometimes fail in optimized scopes based on other
code (including debuggers and code execution tracing tools) potentially
resetting the shared snapshot in that scope.  Now, the code will always
run against an independent snapshot of the local variables in optimized
scopes, and hence the changes will never be visible in subsequent calls
to ‘locals()’.  To access the changes made in these cases, an explicit
namespace reference must now be passed to the relevant function.
Alternatively, it may make sense to update affected code to use a higher
level code execution API that returns the resulting code execution
namespace (e.g.  *note runpy.run_path(): 164. when executing Python
files from disk).

To ensure debuggers and similar tools can reliably update local
variables in scopes affected by this change, *note FrameType.f_locals:
165. now returns a write-through proxy to the frame's local and locally
referenced nonlocal variables in these scopes, rather than returning an
inconsistently updated shared ‘dict’ instance with undefined runtime
semantics.

See PEP 667(2) for more details, including related C API changes and
deprecations.  Porting notes are also provided below for the affected
*note Python APIs: 166. and *note C APIs: 167.

(PEP and implementation contributed by Mark Shannon and Tian Gao in
gh-74929(3).  Documentation updates provided by Guido van Rossum and
Alyssa Coghlan.)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0667/

   (2) https://peps.python.org/pep-0667/

   (3) https://github.com/python/cpython/issues/74929


File: python.info,  Node: Support for mobile platforms,  Next: Incremental garbage collection,  Prev: Defined mutation semantics for locals,  Up: New Features

1.1.2.6 Support for mobile platforms
....................................

PEP 730(1): iOS is now a PEP 11(2) supported platform, with the
‘arm64-apple-ios’ and ‘arm64-apple-ios-simulator’ targets at tier 3
(iPhone and iPad devices released after 2013 and the Xcode iOS simulator
running on Apple silicon hardware, respectively).
‘x86_64-apple-ios-simulator’ (the Xcode iOS simulator running on older
‘x86_64’ hardware) is not a tier 3 supported platform, but will have
best-effort support.  (PEP written and implementation contributed by
Russell Keith-Magee in gh-114099(3).)

PEP 738(4): Android support is being actively worked on, but the
platform is not yet officially supported.  (PEP written and
implementation contributed by Malcolm Smith in gh-116622(5).)

也參考
......

PEP 730(6), PEP 738(7)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0730/

   (2) https://peps.python.org/pep-0011/

   (3) https://github.com/python/cpython/issues/114099

   (4) https://peps.python.org/pep-0738/

   (5) https://github.com/python/cpython/issues/116622

   (6) https://peps.python.org/pep-0730/

   (7) https://peps.python.org/pep-0738/


File: python.info,  Node: Incremental garbage collection,  Prev: Support for mobile platforms,  Up: New Features

1.1.2.7 Incremental garbage collection
......................................

The cycle garbage collector is now incremental.  This means that maximum
pause times are reduced by an order of magnitude or more for larger
heaps.

There are now only two generations: young and old.  When *note
gc.collect(): 16b. is not called directly, the GC is invoked a little
less frequently.  When invoked, it collects the young generation and an
increment of the old generation, instead of collecting one or more
generations.

The behavior of ‘gc.collect()’ changes slightly:

   * ‘gc.collect(1)’: Performs an increment of GC, rather than
     collecting generation 1.

   * Other calls to ‘gc.collect()’ are unchanged.

(Contributed by Mark Shannon in gh-108362(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/108362


File: python.info,  Node: Other Language Changes,  Next: New Modules,  Prev: New Features,  Up: What's New In Python 3 13

1.1.3 Other Language Changes
----------------------------

   * The compiler now strips common leading whitespace from every line
     in a docstring.  This reduces the size of the *note bytecode cache:
     16d. (such as ‘.pyc’ files), with reductions in file size of around
     5%, for example in ‘sqlalchemy.orm.session’ from SQLAlchemy 2.0.
     This change affects tools that use docstrings, such as *note
     doctest: 31.

          >>> def spam():
          ...     """
          ...         This is a docstring with
          ...           leading whitespace.
          ...
          ...         It even has multiple paragraphs!
          ...     """
          ...
          >>> spam.__doc__
          '\nThis is a docstring with\n  leading whitespace.\n\nIt even has multiple paragraphs!\n'

     (Contributed by Inada Naoki in gh-81283(1).)

   * *note Annotation scopes: 16e. within class scopes can now contain
     lambdas and comprehensions.  Comprehensions that are located within
     class scopes are not inlined into their parent scope.

          class C[T]:
              type Alias = lambda: T

     (Contributed by Jelle Zijlstra in gh-109118(2) and gh-118160(3).)

   * *note Future statements: 16f. are no longer triggered by relative
     imports of the *note __future__: 0. module, meaning that statements
     of the form ‘from .__future__ import ...’ are now simply standard
     relative imports, with no special features activated.  (Contributed
     by Jeremiah Gabriel Pascual in gh-118216(4).)

   * *note global: 170. declarations are now permitted in *note except:
     171. blocks when that global is used in the *note else: 172. block.
     Previously this raised an erroneous *note SyntaxError: 173.
     (Contributed by Irit Katriel in gh-111123(5).)

   * Add *note PYTHON_FROZEN_MODULES: 174, a new environment variable
     that determines whether frozen modules are ignored by the import
     machinery, equivalent to the *note -X frozen_modules: 15a.
     command-line option.  (Contributed by Yilei Yang in gh-111374(6).)

   * Add *note support for the perf profiler: 175. working without frame
     pointers(7) through the new environment variable *note
     PYTHON_PERF_JIT_SUPPORT: 176. and command-line option *note -X
     perf_jit: 15a.  (Contributed by Pablo Galindo in gh-118518(8).)

   * The location of a ‘.python_history’ file can be changed via the new
     *note PYTHON_HISTORY: 177. environment variable.  (Contributed by
     Levi Sabah, Zackery Spytz and Hugo van Kemenade in gh-73965(9).)

   * Classes have a new *note __static_attributes__: 131. attribute.
     This is populated by the compiler with a tuple of the class's
     attribute names which are assigned through ‘self.<name>’ from any
     function in its body.  (Contributed by Irit Katriel in
     gh-115775(10).)

   * The compiler now creates a ‘__firstlineno__’ attribute on classes
     with the line number of the first line of the class definition.
     (Contributed by Serhiy Storchaka in gh-118465(11).)

   * The *note exec(): 162. and *note eval(): 163. builtins now accept
     the 'globals' and 'locals' arguments as keywords.  (Contributed by
     Raphael Gaschignard in gh-105879(12))

   * The *note compile(): 178. builtin now accepts a new flag,
     ‘ast.PyCF_OPTIMIZED_AST’, which is similar to ‘ast.PyCF_ONLY_AST’
     except that the returned AST is optimized according to the value of
     the 'optimize' argument.  (Contributed by Irit Katriel in
     gh-108113(13)).

   * Add *note PythonFinalizationError: 132, a new exception derived
     from *note RuntimeError: 179. and used to signal when operations
     are blocked during *note finalization: 133.  The following
     callables now raise ‘PythonFinalizationError’, instead of *note
     RuntimeError: 179.:

        * *note _thread.start_new_thread(): 17a.

        * *note os.fork(): 17b.

        * *note os.forkpty(): 17c.

        * *note subprocess.Popen: 17d.

     (Contributed by Victor Stinner in gh-114570(14).)

   * Allow the 'count' argument of *note str.replace(): 17e. to be a
     keyword.  (Contributed by Hugo van Kemenade in gh-106487(15).)

   * Many functions now emit a warning if a boolean value is passed as a
     file descriptor argument.  This can help catch some errors earlier.
     (Contributed by Serhiy Storchaka in gh-82626(16).)

   * Added ‘name’ and ‘mode’ attributes for compressed and archived
     file-like objects in the *note bz2: f, *note lzma: 7e, *note
     tarfile: c8, and *note zipfile: 117. modules.  (Contributed by
     Serhiy Storchaka in gh-115961(17).)

   * Add a *note __name__: 17f. attribute on *note property: 180.
     objects.  (Contributed by Eugene Toder in gh-101860(18).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/81283

   (2) https://github.com/python/cpython/issues/109118

   (3) https://github.com/python/cpython/issues/118160

   (4) https://github.com/python/cpython/issues/118216

   (5) https://github.com/python/cpython/issues/111123

   (6) https://github.com/python/cpython/issues/111374

   (7) https://en.wikipedia.org/wiki/Call_stack

   (8) https://github.com/python/cpython/issues/118518

   (9) https://github.com/python/cpython/issues/73965

   (10) https://github.com/python/cpython/issues/115775

   (11) https://github.com/python/cpython/issues/118465

   (12) https://github.com/python/cpython/issues/105879

   (13) https://github.com/python/cpython/issues/108113

   (14) https://github.com/python/cpython/issues/114570

   (15) https://github.com/python/cpython/issues/106487

   (16) https://github.com/python/cpython/issues/82626

   (17) https://github.com/python/cpython/issues/115961

   (18) https://github.com/python/cpython/issues/101860


File: python.info,  Node: New Modules,  Next: Improved Modules,  Prev: Other Language Changes,  Up: What's New In Python 3 13

1.1.4 New Modules
-----------------

   * *note dbm.sqlite3: 2d.: An SQLite backend for *note dbm: 29.
     (Contributed by Raymond Hettinger and Erlend E. Aasland in
     gh-100414(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/100414


File: python.info,  Node: Improved Modules,  Next: Optimizations,  Prev: New Modules,  Up: What's New In Python 3 13

1.1.5 Improved Modules
----------------------

* Menu:

* argparse::
* array::
* ast::
* asyncio::
* base64::
* compileall::
* configparser::
* concurrent.futures: concurrent futures.
* configparser: configparser<2>.
* copy::
* dbm::
* dis::
* doctest::
* email::
* fractions::
* gc::
* glob::
* importlib::
* io::
* ipaddress::
* itertools::
* marshal::
* math::
* mimetypes::
* mmap::
* multiprocessing::
* os::
* os.path: os path.
* pathlib::
* pdb::
* queue::
* random::
* re::
* shutil::
* site::
* sqlite3::
* ssl::
* statistics::
* subprocess::
* sys::
* tempfile::
* time::
* tkinter::
* traceback::
* types::
* typing::
* unicodedata::
* venv::
* warnings::
* xml::
* zipimport::


File: python.info,  Node: argparse,  Next: array,  Up: Improved Modules

1.1.5.1 argparse
................

   * Add the 'deprecated' parameter to the *note add_argument(): 184.
     and ‘add_parser()’ methods, to enable deprecating command-line
     options, positional arguments, and subcommands.  (Contributed by
     Serhiy Storchaka in gh-83648(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/83648


File: python.info,  Node: array,  Next: ast,  Prev: argparse,  Up: Improved Modules

1.1.5.2 array
.............

   * Add the ‘'w'’ type code (‘Py_UCS4’) for Unicode characters.  It
     should be used instead of the deprecated ‘'u'’ type code.
     (Contributed by Inada Naoki in gh-80480(1).)

   * Register *note array.array: 186. as a *note MutableSequence: 187.
     by implementing the *note clear(): 188. method.  (Contributed by
     Mike Zimin in gh-114894(2).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/80480

   (2) https://github.com/python/cpython/issues/114894


File: python.info,  Node: ast,  Next: asyncio,  Prev: array,  Up: Improved Modules

1.1.5.3 ast
...........

   * The constructors of node types in the *note ast: 7. module are now
     stricter in the arguments they accept, with more intuitive
     behaviour when arguments are omitted.

     If an optional field on an AST node is not included as an argument
     when constructing an instance, the field will now be set to ‘None’.
     Similarly, if a list field is omitted, that field will now be set
     to an empty list, and if an ‘expr_context’ field is omitted, it
     defaults to *note Load(): 18a.  (Previously, in all cases, the
     attribute would be missing on the newly constructed AST node
     instance.)

     In all other cases, where a required argument is omitted, the node
     constructor will emit a *note DeprecationWarning: 18b.  This will
     raise an exception in Python 3.15.  Similarly, passing a keyword
     argument to the constructor that does not map to a field on the AST
     node is now deprecated, and will raise an exception in Python 3.15.

     These changes do not apply to user-defined subclasses of *note
     ast.AST: 18c. unless the class opts in to the new behavior by
     defining the *note AST._field_types: 18d. mapping.

     (Contributed by Jelle Zijlstra in gh-105858(1), gh-117486(2), and
     gh-118851(3).)

   * *note ast.parse(): 18e. now accepts an optional argument 'optimize'
     which is passed on to *note compile(): 178.  This makes it possible
     to obtain an optimized AST. (Contributed by Irit Katriel in
     gh-108113(4).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/105858

   (2) https://github.com/python/cpython/issues/117486

   (3) https://github.com/python/cpython/issues/118851

   (4) https://github.com/python/cpython/issues/108113


File: python.info,  Node: asyncio,  Next: base64,  Prev: ast,  Up: Improved Modules

1.1.5.4 asyncio
...............

   * *note asyncio.as_completed(): 190. now returns an object that is
     both an *note asynchronous iterator: 191. and a plain *note
     iterator: 192. of *note awaitables: 193.  The awaitables yielded by
     asynchronous iteration include original task or future objects that
     were passed in, making it easier to associate results with the
     tasks being completed.  (Contributed by Justin Arthur in
     gh-77714(1).)

   * *note asyncio.loop.create_unix_server(): 194. will now
     automatically remove the Unix socket when the server is closed.
     (Contributed by Pierre Ossman in gh-111246(2).)

   * *note DatagramTransport.sendto(): 195. will now send zero-length
     datagrams if called with an empty bytes object.  The transport flow
     control also now accounts for the datagram header when calculating
     the buffer size.  (Contributed by Jamie Phan in gh-115199(3).)

   * Add *note Queue.shutdown: 196. and *note QueueShutDown: 197. to
     manage queue termination.  (Contributed by Laurie Opperman and Yves
     Duprat in gh-104228(4).)

   * Add the *note Server.close_clients(): 198. and *note
     Server.abort_clients(): 199. methods, which more forcefully close
     an asyncio server.  (Contributed by Pierre Ossman in gh-113538(5).)

   * Accept a tuple of separators in *note StreamReader.readuntil():
     19a, stopping when any one of them is encountered.  (Contributed by
     Bruce Merry in gh-81322(6).)

   * Improve the behavior of *note TaskGroup: 19b. when an external
     cancellation collides with an internal cancellation.  For example,
     when two task groups are nested and both experience an exception in
     a child task simultaneously, it was possible that the outer task
     group would hang, because its internal cancellation was swallowed
     by the inner task group.

     In the case where a task group is cancelled externally and also
     must raise an *note ExceptionGroup: 19c, it will now call the
     parent task's *note cancel(): 19d. method.  This ensures that a
     *note CancelledError: 19e. will be raised at the next *note await:
     19f, so the cancellation is not lost.

     An added benefit of these changes is that task groups now preserve
     the cancellation count (*note cancelling(): 1a0.).

     In order to handle some corner cases, *note uncancel(): 1a1. may
     now reset the undocumented ‘_must_cancel’ flag when the
     cancellation count reaches zero.

     (Inspired by an issue reported by Arthur Tacca in gh-116720(7).)

   * When *note TaskGroup.create_task(): 1a2. is called on an inactive
     *note TaskGroup: 19b, the given coroutine will be closed (which
     prevents a *note RuntimeWarning: 1a3. about the given coroutine
     being never awaited).  (Contributed by Arthur Tacca and Jason Zhang
     in gh-115957(8).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/77714

   (2) https://github.com/python/cpython/issues/111246

   (3) https://github.com/python/cpython/issues/115199

   (4) https://github.com/python/cpython/issues/104228

   (5) https://github.com/python/cpython/issues/113538

   (6) https://github.com/python/cpython/issues/81322

   (7) https://github.com/python/cpython/issues/116720

   (8) https://github.com/python/cpython/issues/115957


File: python.info,  Node: base64,  Next: compileall,  Prev: asyncio,  Up: Improved Modules

1.1.5.5 base64
..............

   * Add *note z85encode(): 134. and *note z85decode(): 135. functions
     for encoding *note bytes: 1a5. as Z85 data(1) and decoding
     Z85-encoded data to ‘bytes’.  (Contributed by Matan Perelman in
     gh-75299(2).)

   ---------- Footnotes ----------

   (1) https://rfc.zeromq.org/spec/32/

   (2) https://github.com/python/cpython/issues/75299


File: python.info,  Node: compileall,  Next: configparser,  Prev: base64,  Up: Improved Modules

1.1.5.6 compileall
..................

   * The default number of worker threads and processes is now selected
     using *note os.process_cpu_count(): 1a7. instead of *note
     os.cpu_count(): 1a8.  (Contributed by Victor Stinner in
     gh-109649(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/109649


File: python.info,  Node: configparser,  Next: concurrent futures,  Prev: compileall,  Up: Improved Modules

1.1.5.7 configparser
....................

   * The *note configparser.ConfigParser: 1aa. now accepts unnamed
     sections before named ones if configured to do so.  (Contributed by
     Pedro Sousa Lacerda in gh-66449(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/66449


File: python.info,  Node: concurrent futures,  Next: configparser<2>,  Prev: configparser,  Up: Improved Modules

1.1.5.8 concurrent.futures
..........................

   * The default number of worker threads and processes is now selected
     using *note os.process_cpu_count(): 1a7. instead of *note
     os.cpu_count(): 1a8.  (Contributed by Victor Stinner in
     gh-109649(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/109649


File: python.info,  Node: configparser<2>,  Next: copy,  Prev: concurrent futures,  Up: Improved Modules

1.1.5.9 configparser
....................

   * *note ConfigParser: 1aa. now has support for unnamed sections,
     which allows for top-level key-value pairs.  This can be enabled
     with the new 'allow_unnamed_section' parameter.  (Contributed by
     Pedro Sousa Lacerda in gh-66449(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/66449


File: python.info,  Node: copy,  Next: dbm,  Prev: configparser<2>,  Up: Improved Modules

1.1.5.10 copy
.............

   * The new *note replace(): 136. function and the *note replace
     protocol: 137. make creating modified copies of objects much
     simpler.  This is especially useful when working with immutable
     objects.  The following types support the *note replace(): 136.
     function and implement the replace protocol:

        * *note collections.namedtuple(): 1ae.

        * *note dataclasses.dataclass: 1af.

        * *note datetime.datetime: 1b0, *note datetime.date: 1b1, *note
          datetime.time: 1b2.

        * *note inspect.Signature: 1b3, *note inspect.Parameter: 1b4.

        * *note types.SimpleNamespace: 1b5.

        * *note code objects: 1b6.

     Any user-defined class can also support *note copy.replace(): 136.
     by defining the *note __replace__(): 137. method.  (Contributed by
     Serhiy Storchaka in gh-108751(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/108751


File: python.info,  Node: dbm,  Next: dis,  Prev: copy,  Up: Improved Modules

1.1.5.11 dbm
............

   * Add *note dbm.sqlite3: 2d, a new module which implements an SQLite
     backend, and make it the default ‘dbm’ backend.  (Contributed by
     Raymond Hettinger and Erlend E. Aasland in gh-100414(1).)

   * Allow removing all items from the database through the new *note
     gdbm.clear(): 1b8. and *note ndbm.clear(): 1b9. methods.
     (Contributed by Donghee Na in gh-107122(2).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/100414

   (2) https://github.com/python/cpython/issues/107122


File: python.info,  Node: dis,  Next: doctest,  Prev: dbm,  Up: Improved Modules

1.1.5.12 dis
............

   * Change the output of *note dis: 30. module functions to show
     logical labels for jump targets and exception handlers, rather than
     offsets.  The offsets can be added with the new *note -O: 1bb.
     command-line option or the 'show_offsets' argument.  (Contributed
     by Irit Katriel in gh-112137(1).)

   * *note get_instructions(): 1bc. no longer represents cache entries
     as separate instructions.  Instead, it returns them as part of the
     *note Instruction: 1bd, in the new 'cache_info' field.  The
     'show_caches' argument to *note get_instructions(): 1bc. is
     deprecated and no longer has any effect.  (Contributed by Irit
     Katriel in gh-112962(2).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/112137

   (2) https://github.com/python/cpython/issues/112962


File: python.info,  Node: doctest,  Next: email,  Prev: dis,  Up: Improved Modules

1.1.5.13 doctest
................

   * *note doctest: 31. output is now colored by default.  This can be
     controlled via the new *note PYTHON_COLORS: 130. environment
     variable as well as the canonical NO_COLOR(1) and FORCE_COLOR(2)
     environment variables.  See also *note Controlling color: 14f.
     (Contributed by Hugo van Kemenade in gh-117225(3).)

   * The *note DocTestRunner.run(): 1bf. method now counts the number of
     skipped tests.  Add the *note DocTestRunner.skips: 1c0. and *note
     TestResults.skipped: 1c1. attributes.  (Contributed by Victor
     Stinner in gh-108794(4).)

   ---------- Footnotes ----------

   (1) https://no-color.org/

   (2) https://force-color.org/

   (3) https://github.com/python/cpython/issues/117225

   (4) https://github.com/python/cpython/issues/108794


File: python.info,  Node: email,  Next: fractions,  Prev: doctest,  Up: Improved Modules

1.1.5.14 email
..............

   * Headers with embedded newlines are now quoted on output.  The *note
     generator: 37. will now refuse to serialize (write) headers that
     are improperly folded or delimited, such that they would be parsed
     as multiple headers or joined with adjacent data.  If you need to
     turn this safety feature off, set *note verify_generated_headers:
     1c3.  (Contributed by Bas Bloemsaat and Petr Viktorin in
     gh-121650(1).)

   * *note getaddresses(): 1c4. and *note parseaddr(): 1c5. now return
     ‘('', '')’ pairs in more situations where invalid email addresses
     are encountered instead of potentially inaccurate values.  The two
     functions have a new optional 'strict' parameter (default ‘True’).
     To get the old behaviour (accepting malformed input), use
     ‘strict=False’.  ‘getattr(email.utils, 'supports_strict_parsing',
     False)’ can be used to check if the 'strict' parameter is
     available.  (Contributed by Thomas Dwyer and Victor Stinner for
     gh-102988(2) to improve the CVE-2023-27043(3) fix.)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/121650

   (2) https://github.com/python/cpython/issues/102988

   (3) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-27043


File: python.info,  Node: fractions,  Next: gc,  Prev: email,  Up: Improved Modules

1.1.5.15 fractions
..................

   * *note Fraction: 1c7. objects now support the standard *note format
     specification mini-language: 1c8. rules for fill, alignment, sign
     handling, minimum width, and grouping.  (Contributed by Mark
     Dickinson in gh-111320(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/111320


File: python.info,  Node: gc,  Next: glob,  Prev: fractions,  Up: Improved Modules

1.1.5.16 gc
...........

The cyclic garbage collector is now incremental, which changes the
meaning of the results of *note get_threshold(): 1ca. and *note
set_threshold(): 1cb. as well as *note get_count(): 1cc. and *note
get_stats(): 1cd.

   * For backwards compatibility, *note get_threshold(): 1ca. continues
     to return a three-item tuple.  The first value is the threshold for
     young collections, as before; the second value determines the rate
     at which the old collection is scanned (the default is 10, and
     higher values mean that the old collection is scanned more slowly).
     The third value is meaningless and is always zero.

   * *note set_threshold(): 1cb. ignores any items after the second.

   * *note get_count(): 1cc. and *note get_stats(): 1cd. continue to
     return the same format of results.  The only difference is that
     instead of the results referring to the young, aging and old
     generations, the results refer to the young generation and the
     aging and collecting spaces of the old generation.

In summary, code that attempted to manipulate the behavior of the cycle
GC may not work exactly as intended, but it is very unlikely to be
harmful.  All other code will work just fine.


File: python.info,  Node: glob,  Next: importlib,  Prev: gc,  Up: Improved Modules

1.1.5.17 glob
.............

   * Add *note translate(): 1cf, a function to convert a path
     specification with shell-style wildcards to a regular expression.
     (Contributed by Barney Gale in gh-72904(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/72904


File: python.info,  Node: importlib,  Next: io,  Prev: glob,  Up: Improved Modules

1.1.5.18 importlib
..................

   * The following functions in *note importlib.resources: 6f. now allow
     accessing a directory (or tree) of resources, using multiple
     positional arguments (the 'encoding' and 'errors' arguments in the
     text-reading functions are now keyword-only):

        * *note is_resource(): 1d1.

        * *note open_binary(): 1d2.

        * *note open_text(): 1d3.

        * *note path(): 1d4.

        * *note read_binary(): 1d5.

        * *note read_text(): 1d6.

     These functions are no longer deprecated and are not scheduled for
     removal.  (Contributed by Petr Viktorin in gh-106532(1).)

   * *note contents(): 1d7. remains deprecated in favor of the
     fully-featured *note Traversable: 1d8. API. However, there is now
     no plan to remove it.  (Contributed by Petr Viktorin in
     gh-106532(2).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/106532

   (2) https://github.com/python/cpython/issues/106532


File: python.info,  Node: io,  Next: ipaddress,  Prev: importlib,  Up: Improved Modules

1.1.5.19 io
...........

   * The *note IOBase: 1da. finalizer now logs any errors raised by the
     *note close(): 1db. method with *note sys.unraisablehook: 1dc.
     Previously, errors were ignored silently by default, and only
     logged in *note Python Development Mode: 1dd. or when using a *note
     Python debug build: 1de.  (Contributed by Victor Stinner in
     gh-62948(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/62948


File: python.info,  Node: ipaddress,  Next: itertools,  Prev: io,  Up: Improved Modules

1.1.5.20 ipaddress
..................

   * Add the *note IPv4Address.ipv6_mapped: 1e0. property, which returns
     the IPv4-mapped IPv6 address.  (Contributed by Charles Machalow in
     gh-109466(1).)

   * Fix ‘is_global’ and ‘is_private’ behavior in *note IPv4Address:
     1e1, *note IPv6Address: 1e2, *note IPv4Network: 1e3, and *note
     IPv6Network: 1e4.  (Contributed by Jakub Stasiak in gh-113171(2).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/109466

   (2) https://github.com/python/cpython/issues/113171


File: python.info,  Node: itertools,  Next: marshal,  Prev: ipaddress,  Up: Improved Modules

1.1.5.21 itertools
..................

   * *note batched(): 1e6. has a new 'strict' parameter, which raises a
     *note ValueError: 1e7. if the final batch is shorter than the
     specified batch size.  (Contributed by Raymond Hettinger in
     gh-113202(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/113202


File: python.info,  Node: marshal,  Next: math,  Prev: itertools,  Up: Improved Modules

1.1.5.22 marshal
................

   * Add the 'allow_code' parameter in module functions.  Passing
     ‘allow_code=False’ prevents serialization and de-serialization of
     code objects which are incompatible between Python versions.
     (Contributed by Serhiy Storchaka in gh-113626(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/113626


File: python.info,  Node: math,  Next: mimetypes,  Prev: marshal,  Up: Improved Modules

1.1.5.23 math
.............

   * The new function *note fma(): 1ea. performs fused multiply-add
     operations.  This computes ‘x * y + z’ with only a single round,
     and so avoids any intermediate loss of precision.  It wraps the
     ‘fma()’ function provided by C99, and follows the specification of
     the IEEE 754 "fusedMultiplyAdd" operation for special cases.
     (Contributed by Mark Dickinson and Victor Stinner in gh-73468(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/73468


File: python.info,  Node: mimetypes,  Next: mmap,  Prev: math,  Up: Improved Modules

1.1.5.24 mimetypes
..................

   * Add the *note guess_file_type(): 1ec. function to guess a MIME type
     from a filesystem path.  Using paths with *note guess_type(): 1ed.
     is now *note soft deprecated: 1ee.  (Contributed by Serhiy
     Storchaka in gh-66543(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/66543


File: python.info,  Node: mmap,  Next: multiprocessing,  Prev: mimetypes,  Up: Improved Modules

1.1.5.25 mmap
.............

   * *note mmap: 1f0. is now protected from crashing on Windows when the
     mapped memory is inaccessible due to file system errors or access
     violations.  (Contributed by Jannis Weigend in gh-118209(1).)

   * *note mmap: 1f0. has a new *note seekable(): 1f1. method that can
     be used when a seekable file-like object is required.  The *note
     seek(): 1f2. method now returns the new absolute position.
     (Contributed by Donghee Na and Sylvie Liberman in gh-111835(2).)

   * The new UNIX-only 'trackfd' parameter for *note mmap: 1f0. controls
     file descriptor duplication; if false, the file descriptor
     specified by 'fileno' will not be duplicated.  (Contributed by
     Zackery Spytz and Petr Viktorin in gh-78502(3).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/118209

   (2) https://github.com/python/cpython/issues/111835

   (3) https://github.com/python/cpython/issues/78502


File: python.info,  Node: multiprocessing,  Next: os,  Prev: mmap,  Up: Improved Modules

1.1.5.26 multiprocessing
........................

   * The default number of worker threads and processes is now selected
     using *note os.process_cpu_count(): 1a7. instead of *note
     os.cpu_count(): 1a8.  (Contributed by Victor Stinner in
     gh-109649(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/109649


File: python.info,  Node: os,  Next: os path,  Prev: multiprocessing,  Up: Improved Modules

1.1.5.27 os
...........

   * Add *note process_cpu_count(): 1a7. function to get the number of
     logical CPU cores usable by the calling thread of the current
     process.  (Contributed by Victor Stinner in gh-109649(1).)

   * *note cpu_count(): 1a8. and *note process_cpu_count(): 1a7. can be
     overridden through the new environment variable *note
     PYTHON_CPU_COUNT: 1f5. or the new command-line option *note -X
     cpu_count: 15a.  This option is useful for users who need to limit
     CPU resources of a container system without having to modify
     application code or the container itself.  (Contributed by Donghee
     Na in gh-109595(2).)

   * Add a *note low level interface: 138. to Linux's ‘timer file
     descriptors(3)’ via *note timerfd_create(): 1f6, *note
     timerfd_settime(): 1f7, *note timerfd_settime_ns(): 1f8, *note
     timerfd_gettime(): 1f9, *note timerfd_gettime_ns(): 1fa, *note
     TFD_NONBLOCK: 1fb, *note TFD_CLOEXEC: 1fc, *note TFD_TIMER_ABSTIME:
     1fd, and *note TFD_TIMER_CANCEL_ON_SET: 1fe. (Contributed by Masaru
     Tsuchiyama in gh-108277(4).)

   * *note lchmod(): 1ff. and the 'follow_symlinks' argument of *note
     chmod(): 200. are both now available on Windows.  Note that the
     default value of 'follow_symlinks' in ‘lchmod()’ is ‘False’ on
     Windows.  (Contributed by Serhiy Storchaka in gh-59616(5).)

   * *note fchmod(): 201. and support for file descriptors in *note
     chmod(): 200. are both now available on Windows.  (Contributed by
     Serhiy Storchaka in gh-113191(6).)

   * On Windows, *note mkdir(): 202. and *note makedirs(): 203. now
     support passing a 'mode' value of ‘0o700’ to apply access control
     to the new directory.  This implicitly affects *note
     tempfile.mkdtemp(): 204. and is a mitigation for CVE-2024-4030(7).
     Other values for 'mode' continue to be ignored.  (Contributed by
     Steve Dower in gh-118486(8).)

   * *note posix_spawn(): 205. now accepts ‘None’ for the 'env'
     argument, which makes the newly spawned process use the current
     process environment.  (Contributed by Jakub Kulik in gh-113119(9).)

   * *note posix_spawn(): 205. can now use the *note
     POSIX_SPAWN_CLOSEFROM: 206. attribute in the 'file_actions'
     parameter on platforms that support
     ‘posix_spawn_file_actions_addclosefrom_np()’.  (Contributed by
     Jakub Kulik in gh-113117(10).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/109649

   (2) https://github.com/python/cpython/issues/109595

   (3) https://manpages.debian.org/timerfd_create(2)

   (4) https://github.com/python/cpython/issues/108277

   (5) https://github.com/python/cpython/issues/59616

   (6) https://github.com/python/cpython/issues/113191

   (7) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-4030

   (8) https://github.com/python/cpython/issues/118486

   (9) https://github.com/python/cpython/issues/113119

   (10) https://github.com/python/cpython/issues/113117


File: python.info,  Node: os path,  Next: pathlib,  Prev: os,  Up: Improved Modules

1.1.5.28 os.path
................

   * Add *note isreserved(): 208. to check if a path is reserved on the
     current system.  This function is only available on Windows.
     (Contributed by Barney Gale in gh-88569(1).)

   * On Windows, *note isabs(): 209. no longer considers paths starting
     with exactly one slash (‘\’ or ‘/’) to be absolute.  (Contributed
     by Barney Gale and Jon Foster in gh-44626(2).)

   * *note realpath(): 20a. now resolves MS-DOS style file names even if
     the file is not accessible.  (Contributed by Moonsik Park in
     gh-82367(3).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/88569

   (2) https://github.com/python/cpython/issues/44626

   (3) https://github.com/python/cpython/issues/82367


File: python.info,  Node: pathlib,  Next: pdb,  Prev: os path,  Up: Improved Modules

1.1.5.29 pathlib
................

   * Add *note UnsupportedOperation: 20c, which is raised instead of
     *note NotImplementedError: 20d. when a path operation isn't
     supported.  (Contributed by Barney Gale in gh-89812(1).)

   * Add a new constructor for creating *note Path: 20e. objects from
     'file' URIs (‘file:///’), *note Path.from_uri(): 20f.  (Contributed
     by Barney Gale in gh-107465(2).)

   * Add *note PurePath.full_match(): 210. for matching paths with
     shell-style wildcards, including the recursive wildcard "‘**’".
     (Contributed by Barney Gale in gh-73435(3).)

   * Add the *note PurePath.parser: 211. class attribute to store the
     implementation of *note os.path: 92. used for low-level path
     parsing and joining.  This will be either ‘posixpath’ or ‘ntpath’.

   * Add 'recurse_symlinks' keyword-only argument to *note Path.glob():
     212. and *note rglob(): 213.  (Contributed by Barney Gale in
     gh-77609(4).)

   * *note Path.glob(): 212. and *note rglob(): 213. now return files
     and directories when given a pattern that ends with "‘**’".
     Previously, only directories were returned.  (Contributed by Barney
     Gale in gh-70303(5).)

   * Add the 'follow_symlinks' keyword-only argument to *note
     Path.is_file: 214, *note Path.is_dir: 215, *note Path.owner(): 216,
     and *note Path.group(): 217.  (Contributed by Barney Gale in
     gh-105793(6) and Kamil Turek in gh-107962(7).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/89812

   (2) https://github.com/python/cpython/issues/107465

   (3) https://github.com/python/cpython/issues/73435

   (4) https://github.com/python/cpython/issues/77609

   (5) https://github.com/python/cpython/issues/70303

   (6) https://github.com/python/cpython/issues/105793

   (7) https://github.com/python/cpython/issues/107962


File: python.info,  Node: pdb,  Next: queue,  Prev: pathlib,  Up: Improved Modules

1.1.5.30 pdb
............

   * *note breakpoint(): 219. and *note set_trace(): 21a. now enter the
     debugger immediately rather than on the next line of code to be
     executed.  This change prevents the debugger from breaking outside
     of the context when ‘breakpoint()’ is positioned at the end of the
     context.  (Contributed by Tian Gao in gh-118579(1).)

   * ‘sys.path[0]’ is no longer replaced by the directory of the script
     being debugged when *note sys.flags.safe_path: 21b. is set.
     (Contributed by Tian Gao and Christian Walther in gh-111762(2).)

   * *note zipapp: 116. is now supported as a debugging target.
     (Contributed by Tian Gao in gh-118501(3).)

   * Add ability to move between chained exceptions during post-mortem
     debugging in *note pm(): 21c. using the new *note exceptions
     [exc_number]: 21d. command for Pdb.  (Contributed by Matthias
     Bussonnier in gh-106676(4).)

   * Expressions and statements whose prefix is a pdb command are now
     correctly identified and executed.  (Contributed by Tian Gao in
     gh-108464(5).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/118579

   (2) https://github.com/python/cpython/issues/111762

   (3) https://github.com/python/cpython/issues/118501

   (4) https://github.com/python/cpython/issues/106676

   (5) https://github.com/python/cpython/issues/108464


File: python.info,  Node: queue,  Next: random,  Prev: pdb,  Up: Improved Modules

1.1.5.31 queue
..............

   * Add *note Queue.shutdown: 21f. and *note ShutDown: 220. to manage
     queue termination.  (Contributed by Laurie Opperman and Yves Duprat
     in gh-104750(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/104750


File: python.info,  Node: random,  Next: re,  Prev: queue,  Up: Improved Modules

1.1.5.32 random
...............

   * Add a *note command-line interface: 139.  (Contributed by Hugo van
     Kemenade in gh-118131(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/118131


File: python.info,  Node: re,  Next: shutil,  Prev: random,  Up: Improved Modules

1.1.5.33 re
...........

   * Rename ‘re.error’ to *note PatternError: 223. for improved clarity.
     ‘re.error’ is kept for backward compatibility.


File: python.info,  Node: shutil,  Next: site,  Prev: re,  Up: Improved Modules

1.1.5.34 shutil
...............

   * Support the 'dir_fd' and 'follow_symlinks' keyword arguments in
     *note chown(): 225.  (Contributed by Berker Peksag and Tahia K in
     gh-62308(1))

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/62308


File: python.info,  Node: site,  Next: sqlite3,  Prev: shutil,  Up: Improved Modules

1.1.5.35 site
.............

   * ‘.pth’ files are now decoded using UTF-8 first, and then with the
     *note locale encoding: 227. if UTF-8 decoding fails.  (Contributed
     by Inada Naoki in gh-117802(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/117802


File: python.info,  Node: sqlite3,  Next: ssl,  Prev: site,  Up: Improved Modules

1.1.5.36 sqlite3
................

   * A *note ResourceWarning: 229. is now emitted if a *note Connection:
     22a. object is not *note closed: 22b. explicitly.  (Contributed by
     Erlend E. Aasland in gh-105539(1).)

   * Add the 'filter' keyword-only parameter to *note
     Connection.iterdump(): 22c. for filtering database objects to dump.
     (Contributed by Mariusz Felisiak in gh-91602(2).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/105539

   (2) https://github.com/python/cpython/issues/91602


File: python.info,  Node: ssl,  Next: statistics,  Prev: sqlite3,  Up: Improved Modules

1.1.5.37 ssl
............

   * The *note create_default_context(): 13a. API now includes *note
     VERIFY_X509_PARTIAL_CHAIN: 13b. and *note VERIFY_X509_STRICT: 13c.
     in its default flags.

          備註: *note VERIFY_X509_STRICT: 13c. may reject pre- RFC
          5280(1) or malformed certificates that the underlying OpenSSL
          implementation might otherwise accept.  Whilst disabling this
          is not recommended, you can do so using:

               import ssl

               ctx = ssl.create_default_context()
               ctx.verify_flags &= ~ssl.VERIFY_X509_STRICT

     (Contributed by William Woodruff in gh-112389(2).)

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc5280.html

   (2) https://github.com/python/cpython/issues/112389


File: python.info,  Node: statistics,  Next: subprocess,  Prev: ssl,  Up: Improved Modules

1.1.5.38 statistics
...................

   * Add *note kde(): 22f. for kernel density estimation.  This makes it
     possible to estimate a continuous probability density function from
     a fixed number of discrete samples.  (Contributed by Raymond
     Hettinger in gh-115863(1).)

   * Add *note kde_random(): 230. for sampling from an estimated
     probability density function created by *note kde(): 22f.
     (Contributed by Raymond Hettinger in gh-115863(2).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/115863

   (2) https://github.com/python/cpython/issues/115863


File: python.info,  Node: subprocess,  Next: sys,  Prev: statistics,  Up: Improved Modules

1.1.5.39 subprocess
...................

   * The *note subprocess: c1. module now uses the *note posix_spawn():
     205. function in more situations.

     Notably, when 'close_fds' is ‘True’ (the default), *note
     posix_spawn(): 205. will be used when the C library provides
     ‘posix_spawn_file_actions_addclosefrom_np()’, which includes recent
     versions of Linux, FreeBSD, and Solaris.  On Linux, this should
     perform similarly to the existing Linux ‘vfork()’ based code.

     A private control knob ‘subprocess._USE_POSIX_SPAWN’ can be set to
     ‘False’ if you need to force *note subprocess: c1. to never use
     *note posix_spawn(): 205.  Please report your reason and platform
     details in the *note issue tracker: 233. if you set this so that we
     can improve our API selection logic for everyone.  (Contributed by
     Jakub Kulik in gh-113117(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/113117


File: python.info,  Node: sys,  Next: tempfile,  Prev: subprocess,  Up: Improved Modules

1.1.5.40 sys
............

   * Add the *note _is_interned(): 235. function to test if a string was
     interned.  This function is not guaranteed to exist in all
     implementations of Python.  (Contributed by Serhiy Storchaka in
     gh-78573(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/78573


File: python.info,  Node: tempfile,  Next: time,  Prev: sys,  Up: Improved Modules

1.1.5.41 tempfile
.................

   * On Windows, the default mode ‘0o700’ used by *note
     tempfile.mkdtemp(): 204. now limits access to the new directory due
     to changes to *note os.mkdir(): 202.  This is a mitigation for
     CVE-2024-4030(1).  (Contributed by Steve Dower in gh-118486(2).)

   ---------- Footnotes ----------

   (1) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-4030

   (2) https://github.com/python/cpython/issues/118486


File: python.info,  Node: time,  Next: tkinter,  Prev: tempfile,  Up: Improved Modules

1.1.5.42 time
.............

   * On Windows, *note monotonic(): 238. now uses the
     ‘QueryPerformanceCounter()’ clock for a resolution of 1
     microsecond, instead of the ‘GetTickCount64()’ clock which has a
     resolution of 15.6 milliseconds.  (Contributed by Victor Stinner in
     gh-88494(1).)

   * On Windows, *note time(): 239. now uses the
     ‘GetSystemTimePreciseAsFileTime()’ clock for a resolution of 1
     microsecond, instead of the ‘GetSystemTimeAsFileTime()’ clock which
     has a resolution of 15.6 milliseconds.  (Contributed by Victor
     Stinner in gh-63207(2).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/88494

   (2) https://github.com/python/cpython/issues/63207


File: python.info,  Node: tkinter,  Next: traceback,  Prev: time,  Up: Improved Modules

1.1.5.43 tkinter
................

   * Add *note tkinter: d9. widget methods: ‘tk_busy_hold()’,
     ‘tk_busy_configure()’, ‘tk_busy_cget()’, ‘tk_busy_forget()’,
     ‘tk_busy_current()’, and ‘tk_busy_status()’.  (Contributed by
     Miguel, klappnase and Serhiy Storchaka in gh-72684(1).)

   * The *note tkinter: d9. widget method ‘wm_attributes()’ now accepts
     the attribute name without the minus prefix to get window
     attributes, for example ‘w.wm_attributes('alpha')’ and allows
     specifying attributes and values to set as keyword arguments, for
     example ‘w.wm_attributes(alpha=0.5)’.  (Contributed by Serhiy
     Storchaka in gh-43457(2).)

   * ‘wm_attributes()’ can now return attributes as a *note dict: 23b,
     by using the new optional keyword-only parameter
     'return_python_dict'.  (Contributed by Serhiy Storchaka in
     gh-43457(3).)

   * ‘Text.count()’ can now return a simple *note int: 23c. when the new
     optional keyword-only parameter 'return_ints' is used.  Otherwise,
     the single count is returned as a 1-tuple or ‘None’.  (Contributed
     by Serhiy Storchaka in gh-97928(4).)

   * Support the "vsapi" element type in the *note element_create():
     23d. method of *note tkinter.ttk.Style: 23e.  (Contributed by
     Serhiy Storchaka in gh-68166(5).)

   * Add the ‘after_info()’ method for Tkinter widgets.  (Contributed by
     Cheryl Sabella in gh-77020(6).)

   * Add a new ‘copy_replace()’ method to ‘PhotoImage’ to copy a region
     from one image to another, possibly with pixel zooming,
     subsampling, or both.  (Contributed by Serhiy Storchaka in
     gh-118225(7).)

   * Add 'from_coords' parameter to the ‘PhotoImage’ methods ‘copy()’,
     ‘zoom()’ and ‘subsample()’.  Add 'zoom' and 'subsample' parameters
     to the ‘PhotoImage’ method ‘copy()’.  (Contributed by Serhiy
     Storchaka in gh-118225(8).)

   * Add the ‘PhotoImage’ methods ‘read()’ to read an image from a file
     and ‘data()’ to get the image data.  Add 'background' and
     'grayscale' parameters to the ‘write()’ method.  (Contributed by
     Serhiy Storchaka in gh-118271(9).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/72684

   (2) https://github.com/python/cpython/issues/43457

   (3) https://github.com/python/cpython/issues/43457

   (4) https://github.com/python/cpython/issues/97928

   (5) https://github.com/python/cpython/issues/68166

   (6) https://github.com/python/cpython/issues/77020

   (7) https://github.com/python/cpython/issues/118225

   (8) https://github.com/python/cpython/issues/118225

   (9) https://github.com/python/cpython/issues/118271


File: python.info,  Node: traceback,  Next: types,  Prev: tkinter,  Up: Improved Modules

1.1.5.44 traceback
..................

   * Add the *note exc_type_str: 240. attribute to *note
     TracebackException: 241, which holds a string display of the
     'exc_type'.  Deprecate the *note exc_type: 242. attribute, which
     holds the type object itself.  Add parameter 'save_exc_type'
     (default ‘True’) to indicate whether ‘exc_type’ should be saved.
     (Contributed by Irit Katriel in gh-112332(1).)

   * Add a new 'show_group' keyword-only parameter to *note
     TracebackException.format_exception_only(): 243. to (recursively)
     format the nested exceptions of a *note BaseExceptionGroup: 244.
     instance.  (Contributed by Irit Katriel in gh-105292(2).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/112332

   (2) https://github.com/python/cpython/issues/105292


File: python.info,  Node: types,  Next: typing,  Prev: traceback,  Up: Improved Modules

1.1.5.45 types
..............

   * *note SimpleNamespace: 1b5. can now take a single positional
     argument to initialise the namespace's arguments.  This argument
     must either be a mapping or an iterable of key-value pairs.
     (Contributed by Serhiy Storchaka in gh-108191(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/108191


File: python.info,  Node: typing,  Next: unicodedata,  Prev: types,  Up: Improved Modules

1.1.5.46 typing
...............

   * PEP 705(1): Add *note ReadOnly: 145, a special typing construct to
     mark a *note TypedDict: 146. item as read-only for type checkers.

   * PEP 742(2): Add *note TypeIs: 147, a typing construct that can be
     used to instruct a type checker how to narrow a type.

   * Add *note NoDefault: 247, a sentinel object used to represent the
     defaults of some parameters in the *note typing: ed. module.
     (Contributed by Jelle Zijlstra in gh-116126(3).)

   * Add *note get_protocol_members(): 248. to return the set of members
     defining a *note typing.Protocol: 249.  (Contributed by Jelle
     Zijlstra in gh-104873(4).)

   * Add *note is_protocol(): 24a. to check whether a class is a *note
     Protocol: 249.  (Contributed by Jelle Zijlstra in gh-104873(5).)

   * *note ClassVar: 24b. can now be nested in *note Final: 24c, and
     vice versa.  (Contributed by Mehdi Drissi in gh-89547(6).)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0705/

   (2) https://peps.python.org/pep-0742/

   (3) https://github.com/python/cpython/issues/116126

   (4) https://github.com/python/cpython/issues/104873

   (5) https://github.com/python/cpython/issues/104873

   (6) https://github.com/python/cpython/issues/89547


File: python.info,  Node: unicodedata,  Next: venv,  Prev: typing,  Up: Improved Modules

1.1.5.47 unicodedata
....................

   * Update the Unicode database to version 15.1.0(1).  (Contributed by
     James Gerity in gh-109559(2).)

   ---------- Footnotes ----------

   (1) https://www.unicode.org/versions/Unicode15.1.0/

   (2) https://github.com/python/cpython/issues/109559


File: python.info,  Node: venv,  Next: warnings,  Prev: unicodedata,  Up: Improved Modules

1.1.5.48 venv
.............

   * Add support for creating source control management (SCM) ignore
     files in a virtual environment's directory.  By default, Git is
     supported.  This is implemented as opt-in via the API, which can be
     extended to support other SCMs (*note EnvBuilder: 24f. and *note
     create(): 250.), and opt-out via the CLI, using
     ‘--without-scm-ignore-files’.  (Contributed by Brett Cannon in
     gh-108125(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/108125


File: python.info,  Node: warnings,  Next: xml,  Prev: venv,  Up: Improved Modules

1.1.5.49 warnings
.................

   * PEP 702(1): The new *note warnings.deprecated(): 144. decorator
     provides a way to communicate deprecations to a *note static type
     checker: 252. and to warn on usage of deprecated classes and
     functions.  A *note DeprecationWarning: 18b. may also be emitted
     when a decorated function or class is used at runtime.
     (Contributed by Jelle Zijlstra in gh-104003(2).)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0702/

   (2) https://github.com/python/cpython/issues/104003


File: python.info,  Node: xml,  Next: zipimport,  Prev: warnings,  Up: Improved Modules

1.1.5.50 xml
............

   * Allow controlling Expat >=2.6.0 reparse deferral
     (CVE-2023-52425(1)) by adding five new methods:

        * *note xml.etree.ElementTree.XMLParser.flush(): 254.

        * *note xml.etree.ElementTree.XMLPullParser.flush(): 255.

        * *note xml.parsers.expat.xmlparser.GetReparseDeferralEnabled():
          256.

        * *note xml.parsers.expat.xmlparser.SetReparseDeferralEnabled():
          257.

        * ‘xml.sax.expatreader.ExpatParser.flush()’

     (Contributed by Sebastian Pipping in gh-115623(2).)

   * Add the ‘close()’ method for the iterator returned by *note
     iterparse(): 258. for explicit cleanup.  (Contributed by Serhiy
     Storchaka in gh-69893(3).)

   ---------- Footnotes ----------

   (1) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-52425

   (2) https://github.com/python/cpython/issues/115623

   (3) https://github.com/python/cpython/issues/69893


File: python.info,  Node: zipimport,  Prev: xml,  Up: Improved Modules

1.1.5.51 zipimport
..................

   * Add support for ZIP64(1) format files.  Everybody loves huge data,
     right?  (Contributed by Tim Hatch in gh-94146(2).)

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Zip_(file_format)#ZIP64

   (2) https://github.com/python/cpython/issues/94146


File: python.info,  Node: Optimizations,  Next: Removed Modules And APIs,  Prev: Improved Modules,  Up: What's New In Python 3 13

1.1.6 Optimizations
-------------------

   * The new *note incremental garbage collector: 16a. means that
     maximum pause times are reduced by an order of magnitude or more
     for larger heaps.  (Contributed by Mark Shannon in gh-108362(1).)

   * Several standard library modules have had their import times
     significantly improved.  For example, the import time of the *note
     typing: ed. module has been reduced by around a third by removing
     dependencies on *note re: a7. and *note contextlib: 1c.  Other
     modules to enjoy import-time speedups include *note email.utils:
     47, *note enum: 4c, *note functools: 55, *note importlib.metadata:
     6e, and *note threading: d6.  (Contributed by Alex Waygood,
     Shantanu Jain, Adam Turner, Daniel Hollas, and others in
     gh-109653(2).)

   * *note textwrap.indent(): 25b. is now around 30% faster than before
     for large input.  (Contributed by Inada Naoki in gh-107369(3).)

   * The *note subprocess: c1. module now uses the *note posix_spawn():
     205. function in more situations, including when 'close_fds' is
     ‘True’ (the default) on many modern platforms.  This should provide
     a notable performance increase when launching processes on FreeBSD
     and Solaris.  See the *note subprocess: 232. section above for
     details.  (Contributed by Jakub Kulik in gh-113117(4).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/108362

   (2) https://github.com/python/cpython/issues/109653

   (3) https://github.com/python/cpython/issues/107369

   (4) https://github.com/python/cpython/issues/113117


File: python.info,  Node: Removed Modules And APIs,  Next: New Deprecations,  Prev: Optimizations,  Up: What's New In Python 3 13

1.1.7 Removed Modules And APIs
------------------------------

* Menu:

* PEP 594; Remove "dead batteries" from the standard library: PEP 594 Remove "dead batteries" from the standard library.
* 2to3::
* builtins::
* configparser: configparser<3>.
* importlib.metadata: importlib metadata.
* locale::
* opcode::
* pathlib: pathlib<2>.
* re: re<2>.
* tkinter.tix: tkinter tix.
* turtle::
* typing: typing<2>.
* unittest::
* urllib::
* webbrowser::


File: python.info,  Node: PEP 594 Remove "dead batteries" from the standard library,  Next: 2to3,  Up: Removed Modules And APIs

1.1.7.1 PEP 594: Remove "dead batteries" from the standard library
..................................................................

PEP 594(1) proposed removing 19 modules from the standard library,
colloquially referred to as 'dead batteries' due to their historic,
obsolete, or insecure status.  All of the following modules were
deprecated in Python 3.11, and are now removed:

   * ‘aifc’

   * ‘audioop’

   * ‘chunk’

   * ‘cgi’ and ‘cgitb’

        * ‘cgi.FieldStorage’ can typically be replaced with *note
          urllib.parse.parse_qsl(): 25e. for ‘GET’ and ‘HEAD’ requests,
          and the *note email.message: 3b. module or the multipart(2)
          library for ‘POST’ and ‘PUT’ requests.

        * ‘cgi.parse()’ can be replaced by calling *note
          urllib.parse.parse_qs(): 25f. directly on the desired query
          string, unless the input is ‘multipart/form-data’, which
          should be replaced as described below for
          ‘cgi.parse_multipart()’.

        * ‘cgi.parse_header()’ can be replaced with the functionality in
          the *note email: 32. package, which implements the same MIME
          RFCs.  For example, with *note email.message.EmailMessage:
          260.:

               from email.message import EmailMessage

               msg = EmailMessage()
               msg['content-type'] = 'application/json; charset="utf8"'
               main, params = msg.get_content_type(), msg['content-type'].params

        * ‘cgi.parse_multipart()’ can be replaced with the functionality
          in the *note email: 32. package, which implements the same
          MIME RFCs, or with the multipart(3) library.  For example, the
          *note email.message.EmailMessage: 260. and *note
          email.message.Message: 261. classes.

   * ‘crypt’ and the private ‘_crypt’ extension.  The *note hashlib: 5e.
     module may be an appropriate replacement when simply hashing a
     value is required.  Otherwise, various third-party libraries on
     PyPI are available:

        * bcrypt(4): Modern password hashing for your software and your
          servers.

        * passlib(5): Comprehensive password hashing framework
          supporting over 30 schemes.

        * argon2-cffi(6): The secure Argon2 password hashing algorithm.

        * legacycrypt(7): *note ctypes: 22. wrapper to the POSIX crypt
          library call and associated functionality.

        * crypt_r(8): Fork of the ‘crypt’ module, wrapper to the
          ‘crypt_r(3)(9)’ library call and associated functionality.

   * ‘imghdr’: The filetype(10), puremagic(11), or python-magic(12)
     libraries should be used as replacements.  For example, the
     ‘puremagic.what()’ function can be used to replace the
     ‘imghdr.what()’ function for all file formats that were supported
     by ‘imghdr’.

   * ‘mailcap’: Use the *note mimetypes: 82. module instead.

   * ‘msilib’

   * ‘nis’

   * ‘nntplib’: Use the nntplib(13) library from PyPI instead.

   * ‘ossaudiodev’: For audio playback, use the pygame(14) library from
     PyPI instead.

   * ‘pipes’: Use the *note subprocess: c1. module instead.

   * ‘sndhdr’: The filetype(15), puremagic(16), or python-magic(17)
     libraries should be used as replacements.

   * ‘spwd’: Use the python-pam(18) library from PyPI instead.

   * ‘sunau’

   * ‘telnetlib’, Use the telnetlib3(19) or Exscript(20) libraries from
     PyPI instead.

   * ‘uu’: Use the *note base64: a. module instead, as a modern
     alternative.

   * ‘xdrlib’

(Contributed by Victor Stinner and Zachary Ware in gh-104773(21) and
gh-104780(22).)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0594/

   (2) https://pypi.org/project/multipart/

   (3) https://pypi.org/project/multipart/

   (4) https://pypi.org/project/bcrypt/

   (5) https://pypi.org/project/passlib/

   (6) https://pypi.org/project/argon2-cffi/

   (7) https://pypi.org/project/legacycrypt/

   (8) https://pypi.org/project/crypt_r/

   (9) https://manpages.debian.org/crypt_r(3)

   (10) https://pypi.org/project/filetype/

   (11) https://pypi.org/project/puremagic/

   (12) https://pypi.org/project/python-magic/

   (13) https://pypi.org/project/nntplib/

   (14) https://pypi.org/project/pygame/

   (15) https://pypi.org/project/filetype/

   (16) https://pypi.org/project/puremagic/

   (17) https://pypi.org/project/python-magic/

   (18) https://pypi.org/project/python-pam/

   (19) https://pypi.org/project/telnetlib3/

   (20) https://pypi.org/project/Exscript/

   (21) https://github.com/python/cpython/issues/104773

   (22) https://github.com/python/cpython/issues/104780


File: python.info,  Node: 2to3,  Next: builtins,  Prev: PEP 594 Remove "dead batteries" from the standard library,  Up: Removed Modules And APIs

1.1.7.2 2to3
............

   * Remove the ‘2to3’ program and the ‘lib2to3’ module, previously
     deprecated in Python 3.11.  (Contributed by Victor Stinner in
     gh-104780(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/104780


File: python.info,  Node: builtins,  Next: configparser<3>,  Prev: 2to3,  Up: Removed Modules And APIs

1.1.7.3 builtins
................

   * Remove support for chained *note classmethod: 14a. descriptors
     (introduced in gh-63272(1)).  These can no longer be used to wrap
     other descriptors, such as *note property: 180.  The core design of
     this feature was flawed and led to several problems.  To
     "pass-through" a *note classmethod: 14a, consider using the
     ‘__wrapped__’ attribute that was added in Python 3.10.
     (Contributed by Raymond Hettinger in gh-89519(2).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/63272

   (2) https://github.com/python/cpython/issues/89519


File: python.info,  Node: configparser<3>,  Next: importlib metadata,  Prev: builtins,  Up: Removed Modules And APIs

1.1.7.4 configparser
....................

   * Remove the undocumented ‘LegacyInterpolation’ class, deprecated in
     the docstring since Python 3.2, and at runtime since Python 3.11.
     (Contributed by Hugo van Kemenade in gh-104886(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/104886


File: python.info,  Node: importlib metadata,  Next: locale,  Prev: configparser<3>,  Up: Removed Modules And APIs

1.1.7.5 importlib.metadata
..........................

   * Remove deprecated subscript (*note __getitem__(): 266.) access for
     *note EntryPoint: 267. objects.  (Contributed by Jason R. Coombs in
     gh-113175(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/113175


File: python.info,  Node: locale,  Next: opcode,  Prev: importlib metadata,  Up: Removed Modules And APIs

1.1.7.6 locale
..............

   * Remove the ‘locale.resetlocale()’ function, deprecated in Python
     3.11.  Use ‘locale.setlocale(locale.LC_ALL, "")’ instead.
     (Contributed by Victor Stinner in gh-104783(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/104783


File: python.info,  Node: opcode,  Next: pathlib<2>,  Prev: locale,  Up: Removed Modules And APIs

1.1.7.7 opcode
..............

   * Move ‘opcode.ENABLE_SPECIALIZATION’ to
     ‘_opcode.ENABLE_SPECIALIZATION’.  This field was added in 3.12, it
     was never documented, and is not intended for external use.
     (Contributed by Irit Katriel in gh-105481(1).)

   * Remove ‘opcode.is_pseudo()’, ‘opcode.MIN_PSEUDO_OPCODE’, and
     ‘opcode.MAX_PSEUDO_OPCODE’, which were added in Python 3.12, but
     were neither documented nor exposed through *note dis: 30, and were
     not intended to be used externally.  (Contributed by Irit Katriel
     in gh-105481(2).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/105481

   (2) https://github.com/python/cpython/issues/105481


File: python.info,  Node: pathlib<2>,  Next: re<2>,  Prev: opcode,  Up: Removed Modules And APIs

1.1.7.8 pathlib
...............

   * Remove the ability to use *note Path: 20e. objects as context
     managers.  This functionality was deprecated and has had no effect
     since Python 3.9.  (Contributed by Barney Gale in gh-83863(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/83863


File: python.info,  Node: re<2>,  Next: tkinter tix,  Prev: pathlib<2>,  Up: Removed Modules And APIs

1.1.7.9 re
..........

   * Remove the undocumented, deprecated, and broken ‘re.template()’
     function and ‘re.TEMPLATE’ / ‘re.T’ flag.  (Contributed by Serhiy
     Storchaka and Nikita Sobolev in gh-105687(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/105687


File: python.info,  Node: tkinter tix,  Next: turtle,  Prev: re<2>,  Up: Removed Modules And APIs

1.1.7.10 tkinter.tix
....................

   * Remove the ‘tkinter.tix’ module, deprecated in Python 3.6.  The
     third-party Tix library which the module wrapped is unmaintained.
     (Contributed by Zachary Ware in gh-75552(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/75552


File: python.info,  Node: turtle,  Next: typing<2>,  Prev: tkinter tix,  Up: Removed Modules And APIs

1.1.7.11 turtle
...............

   * Remove the ‘RawTurtle.settiltangle()’ method, deprecated in the
     documentation since Python 3.1 and at runtime since Python 3.11.
     (Contributed by Hugo van Kemenade in gh-104876(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/104876


File: python.info,  Node: typing<2>,  Next: unittest,  Prev: turtle,  Up: Removed Modules And APIs

1.1.7.12 typing
...............

   * Remove the ‘typing.io’ and ‘typing.re’ namespaces, deprecated since
     Python 3.8.  The items in those namespaces can be imported directly
     from the *note typing: ed. module.  (Contributed by Sebastian
     Rittau in gh-92871(1).)

   * Remove the keyword-argument method of creating *note TypedDict:
     146. types, deprecated in Python 3.11.  (Contributed by Tomas Roun
     in gh-104786(2).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/92871

   (2) https://github.com/python/cpython/issues/104786


File: python.info,  Node: unittest,  Next: urllib,  Prev: typing<2>,  Up: Removed Modules And APIs

1.1.7.13 unittest
.................

   * Remove the following *note unittest: ef. functions, deprecated in
     Python 3.11:

        * ‘unittest.findTestCases()’

        * ‘unittest.makeSuite()’

        * ‘unittest.getTestCaseNames()’

     Use *note TestLoader: 270. methods instead:

        * *note loadTestsFromModule(): 271.

        * *note loadTestsFromTestCase(): 272.

        * *note getTestCaseNames(): 273.

     (Contributed by Hugo van Kemenade in gh-104835(1).)

   * Remove the untested and undocumented ‘TestProgram.usageExit()’
     method, deprecated in Python 3.11.  (Contributed by Hugo van
     Kemenade in gh-104992(2).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/104835

   (2) https://github.com/python/cpython/issues/104992


File: python.info,  Node: urllib,  Next: webbrowser,  Prev: unittest,  Up: Removed Modules And APIs

1.1.7.14 urllib
...............

   * Remove the 'cafile', 'capath', and 'cadefault' parameters of the
     *note urllib.request.urlopen(): 275. function, deprecated in Python
     3.6.  Use the 'context' parameter instead with an *note SSLContext:
     276. instance.  The *note ssl.SSLContext.load_cert_chain(): 277.
     function can be used to load specific certificates, or let *note
     ssl.create_default_context(): 13a. select the operating system's
     trusted certificate authority (CA) certificates.  (Contributed by
     Victor Stinner in gh-105382(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/105382


File: python.info,  Node: webbrowser,  Prev: urllib,  Up: Removed Modules And APIs

1.1.7.15 webbrowser
...................

   * Remove the untested and undocumented ‘MacOSX’ class, deprecated in
     Python 3.11.  Use the ‘MacOSXOSAScript’ class (introduced in Python
     3.2) instead.  (Contributed by Hugo van Kemenade in gh-104804(1).)

   * Remove the deprecated ‘MacOSXOSAScript._name’ attribute.  Use the
     *note MacOSXOSAScript.name: 279. attribute instead.  (Contributed
     by Nikita Sobolev in gh-105546(2).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/104804

   (2) https://github.com/python/cpython/issues/105546


File: python.info,  Node: New Deprecations,  Next: CPython Bytecode Changes,  Prev: Removed Modules And APIs,  Up: What's New In Python 3 13

1.1.8 New Deprecations
----------------------

   * *note array: 6.: *note array: 6.'s ‘'u'’ format code, deprecated in
     docs since Python 3.3, emits *note DeprecationWarning: 18b. since
     3.13 and will be removed in Python 3.16.  Use the ‘'w'’ format code
     instead.  (Contributed by Hugo van Kemenade in gh-80480(1).)

   * *note ctypes: 22.: Deprecate undocumented ‘ctypes.SetPointerType()’
     function.  *note Soft-deprecate: 1ee. the *note ctypes.ARRAY():
     27b. function in favor of multiplication.  (Contributed by Victor
     Stinner in gh-105733(2).)

   * *note decimal: 2e.: Deprecate non-standard format specifier "N" for
     *note decimal.Decimal: 27c.  It was not documented and only
     supported in the C implementation.  (Contributed by Serhiy
     Storchaka in gh-89902(3).)

   * *note dis: 30.: The ‘dis.HAVE_ARGUMENT’ separator is deprecated.
     Check membership in *note hasarg: 27d. instead.  (Contributed by
     Irit Katriel in gh-109319(4).)

   * *note Frame objects: 27e.: Calling *note frame.clear(): 27f. on a
     suspended frame raises *note RuntimeError: 179. (as has always been
     the case for an executing frame).  (Contributed by Irit Katriel in
     gh-79932(5).)

   * *note getopt: 57. and *note optparse: 90. modules: They are now
     *note soft deprecated: 1ee.: the *note argparse: 5. module should
     be used for new projects.  Previously, the *note optparse: 90.
     module was already deprecated, its removal was not scheduled, and
     no warnings was emitted: so there is no change in practice.
     (Contributed by Victor Stinner in gh-106535(6).)

   * *note gettext: 59.: Emit deprecation warning for non-integer
     numbers in *note gettext: 59. functions and methods that consider
     plural forms even if the translation was not found.  (Contributed
     by Serhiy Storchaka in gh-88434(7).)

   * *note glob: 5a.: The undocumented ‘glob.glob0()’ and ‘glob.glob1()’
     functions are deprecated.  Use *note glob.glob(): 280. and pass a
     directory to its 'root_dir' argument instead.  (Contributed by
     Barney Gale in gh-117337(8).)

   * *note http.server: 68.: *note http.server.CGIHTTPRequestHandler:
     281. now emits a *note DeprecationWarning: 18b. as it will be
     removed in 3.15.  Process-based CGI HTTP servers have been out of
     favor for a very long time.  This code was outdated, unmaintained,
     and rarely used.  It has a high potential for both security and
     functionality bugs.  This includes removal of the ‘--cgi’ flag to
     the ‘python -m http.server’ command line in 3.15.

   * *note mimetypes: 82.: Passing file path instead of URL in *note
     guess_type(): 1ed. is *note soft deprecated: 1ee.  Use *note
     guess_file_type(): 1ec. instead.  (Contributed by Serhiy Storchaka
     in gh-66543(9).)

   * *note re: a7.: Passing optional arguments 'maxsplit', 'count' and
     'flags' in module-level functions *note re.split(): 282, *note
     re.sub(): 283. and *note re.subn(): 284. as positional arguments is
     now deprecated.  In future Python versions these parameters will be
     *note keyword-only: 285.  (Contributed by Serhiy Storchaka in
     gh-56166(10).)

   * *note pathlib: 93.: *note pathlib.PurePath.is_reserved(): 286. is
     deprecated and scheduled for removal in Python 3.15.  Use *note
     os.path.isreserved(): 208. to detect reserved paths on Windows.

   * *note platform: 98.: *note java_ver(): 287. is deprecated and will
     be removed in 3.15.  It was largely untested, had a confusing API,
     and was only useful for Jython support.  (Contributed by Nikita
     Sobolev in gh-116349(11).)

   * *note pydoc: a3.: Deprecate undocumented ‘pydoc.ispackage()’
     function.  (Contributed by Zackery Spytz in gh-64020(12).)

   * *note sqlite3: ba.: Passing more than one positional argument to
     *note sqlite3.connect(): 288. and the *note sqlite3.Connection:
     22a. constructor is deprecated.  The remaining parameters will
     become keyword-only in Python 3.15.

     Deprecate passing name, number of arguments, and the callable as
     keyword arguments for the following *note sqlite3.Connection: 22a.
     APIs:

        * *note create_function(): 289.

        * *note create_aggregate(): 28a.

     Deprecate passing the callback callable by keyword for the
     following *note sqlite3.Connection: 22a. APIs:

        * *note set_authorizer(): 28b.

        * *note set_progress_handler(): 28c.

        * *note set_trace_callback(): 28d.

     The affected parameters will become positional-only in Python 3.15.

     (Contributed by Erlend E. Aasland in gh-107948(13) and
     gh-108278(14).)

   * *note sys: c3.: The *note sys._enablelegacywindowsfsencoding():
     28e. function is deprecated.  Replace it with the *note
     PYTHONLEGACYWINDOWSFSENCODING: 28f. environment variable.
     (Contributed by Inada Naoki in gh-73427(15).)

   * *note tarfile: c8.: The undocumented and unused ‘tarfile’ attribute
     of *note tarfile.TarFile: 290. is deprecated and scheduled for
     removal in Python 3.16.

   * *note traceback: e7.: The field 'exc_type' of *note
     traceback.TracebackException: 241. is deprecated.  Use
     'exc_type_str' instead.

   * *note typing: ed.:

        * Creating a *note typing.NamedTuple: 291. class using keyword
          arguments to denote the fields (‘NT = NamedTuple("NT", x=int,
          y=int)’) is deprecated, and will be disallowed in Python 3.15.
          Use the class-based syntax or the functional syntax instead.
          (Contributed by Alex Waygood in gh-105566(16).)

        * When using the functional syntax to create a *note
          typing.NamedTuple: 291. class or a *note typing.TypedDict:
          146. class, failing to pass a value to the 'fields' parameter
          (‘NT = NamedTuple("NT")’ or ‘TD = TypedDict("TD")’) is
          deprecated.  Passing ‘None’ to the 'fields' parameter (‘NT =
          NamedTuple("NT", None)’ or ‘TD = TypedDict("TD", None)’) is
          also deprecated.  Both will be disallowed in Python 3.15.  To
          create a NamedTuple class with zero fields, use ‘class
          NT(NamedTuple): pass’ or ‘NT = NamedTuple("NT", [])’.  To
          create a TypedDict class with zero fields, use ‘class
          TD(TypedDict): pass’ or ‘TD = TypedDict("TD", {})’.
          (Contributed by Alex Waygood in gh-105566(17) and
          gh-105570(18).)

        * *note typing.no_type_check_decorator(): 292. is deprecated,
          and scheduled for removal in Python 3.15.  After eight years
          in the *note typing: ed. module, it has yet to be supported by
          any major type checkers.  (Contributed by Alex Waygood in
          gh-106309(19).)

        * *note typing.AnyStr: 293. is deprecated.  In Python 3.16, it
          will be removed from ‘typing.__all__’, and a *note
          DeprecationWarning: 18b. will be emitted when it is imported
          or accessed.  It will be removed entirely in Python 3.18.  Use
          the new *note type parameter syntax: 294. instead.
          (Contributed by Michael The in gh-107116(20).)

   * *note 自訂函式: 295.: Assignment to a function's *note __code__:
     296. attribute where the new code object's type does not match the
     function's type is deprecated.  The different types are: plain
     function, generator, async generator and coroutine.  (Contributed
     by Irit Katriel in gh-81137(21).)

   * *note wave: fb.: Deprecate the ‘getmark()’, ‘setmark()’ and
     ‘getmarkers()’ methods of the *note wave.Wave_read: 297. and *note
     wave.Wave_write: 298. classes.  They will be removed in Python
     3.15.  (Contributed by Victor Stinner in gh-105096(22).)

* Menu:

* Pending Removal in Python 3.14: Pending Removal in Python 3 14.
* Pending Removal in Python 3.15: Pending Removal in Python 3 15.
* Pending Removal in Python 3.16: Pending Removal in Python 3 16.
* Pending Removal in Future Versions::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/80480

   (2) https://github.com/python/cpython/issues/105733

   (3) https://github.com/python/cpython/issues/89902

   (4) https://github.com/python/cpython/issues/109319

   (5) https://github.com/python/cpython/issues/79932

   (6) https://github.com/python/cpython/issues/106535

   (7) https://github.com/python/cpython/issues/88434

   (8) https://github.com/python/cpython/issues/117337

   (9) https://github.com/python/cpython/issues/66543

   (10) https://github.com/python/cpython/issues/56166

   (11) https://github.com/python/cpython/issues/116349

   (12) https://github.com/python/cpython/issues/64020

   (13) https://github.com/python/cpython/issues/107948

   (14) https://github.com/python/cpython/issues/108278

   (15) https://github.com/python/cpython/issues/73427

   (16) https://github.com/python/cpython/issues/105566

   (17) https://github.com/python/cpython/issues/105566

   (18) https://github.com/python/cpython/issues/105570

   (19) https://github.com/python/cpython/issues/106309

   (20) https://github.com/python/cpython/issues/107116

   (21) https://github.com/python/cpython/issues/81137

   (22) https://github.com/python/cpython/issues/105096


File: python.info,  Node: Pending Removal in Python 3 14,  Next: Pending Removal in Python 3 15,  Up: New Deprecations

1.1.8.1 Pending Removal in Python 3.14
......................................

   * *note argparse: 5.: The 'type', 'choices', and 'metavar' parameters
     of ‘argparse.BooleanOptionalAction’ are deprecated and will be
     removed in 3.14.  (Contributed by Nikita Sobolev in gh-92248(1).)

   * *note ast: 7.: The following features have been deprecated in
     documentation since Python 3.8, now cause a *note
     DeprecationWarning: 18b. to be emitted at runtime when they are
     accessed or used, and will be removed in Python 3.14:

        * ‘ast.Num’

        * ‘ast.Str’

        * ‘ast.Bytes’

        * ‘ast.NameConstant’

        * ‘ast.Ellipsis’

     Use *note ast.Constant: 29a. instead.  (Contributed by Serhiy
     Storchaka in gh-90953(2).)

   * *note asyncio: 8.:

        * The child watcher classes *note MultiLoopChildWatcher: 29b,
          *note FastChildWatcher: 29c, *note AbstractChildWatcher: 29d.
          and *note SafeChildWatcher: 29e. are deprecated and will be
          removed in Python 3.14.  (Contributed by Kumar Aditya in
          gh-94597(3).)

        * *note asyncio.set_child_watcher(): 29f, *note
          asyncio.get_child_watcher(): 2a0, *note
          asyncio.AbstractEventLoopPolicy.set_child_watcher(): 2a1. and
          *note asyncio.AbstractEventLoopPolicy.get_child_watcher():
          2a2. are deprecated and will be removed in Python 3.14.
          (Contributed by Kumar Aditya in gh-94597(4).)

        * The *note get_event_loop(): 2a3. method of the default event
          loop policy now emits a *note DeprecationWarning: 18b. if
          there is no current event loop set and it decides to create
          one.  (Contributed by Serhiy Storchaka and Guido van Rossum in
          gh-100160(5).)

   * *note collections.abc: 17.: Deprecated *note ByteString: 2a4.
     Prefer ‘Sequence’ or *note Buffer: 2a5.  For use in typing, prefer
     a union, like ‘bytes | bytearray’, or *note collections.abc.Buffer:
     2a5.  (Contributed by Shantanu Jain in gh-91896(6).)

   * *note email: 32.: Deprecated the 'isdst' parameter in *note
     email.utils.localtime(): 2a6.  (Contributed by Alan Williams in
     gh-72346(7).)

   * *note importlib: 6b.: ‘__package__’ and ‘__cached__’ will cease to
     be set or taken into consideration by the import system
     (gh-97879(8)).

   * *note importlib.abc: 6c. deprecated classes:

        * ‘importlib.abc.ResourceReader’

        * ‘importlib.abc.Traversable’

        * ‘importlib.abc.TraversableResources’

     Use *note importlib.resources.abc: 70. classes instead:

        * *note importlib.resources.abc.Traversable: 1d8.

        * *note importlib.resources.abc.TraversableResources: 2a7.

     (Contributed by Jason R. Coombs and Hugo van Kemenade in
     gh-93963(9).)

   * *note itertools: 75. had undocumented, inefficient, historically
     buggy, and inconsistent support for copy, deepcopy, and pickle
     operations.  This will be removed in 3.14 for a significant
     reduction in code volume and maintenance burden.  (Contributed by
     Raymond Hettinger in gh-101588(10).)

   * *note multiprocessing: 86.: The default 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(11)).  Adding a
     runtime warning about this was deemed too disruptive as the
     majority of code is not expected to care.  Use the *note
     get_context(): 2a8. or *note set_start_method(): 2a9. APIs to
     explicitly specify when your code 'requires' ‘'fork'’.  See *note
     Contexts and start methods: 2aa.

   * *note pathlib: 93.: *note is_relative_to(): 2ab. and *note
     relative_to(): 2ac.: passing additional arguments is deprecated.

   * *note pkgutil: 97.: *note find_loader(): 2ad. and *note
     get_loader(): 2ae. now raise *note DeprecationWarning: 18b.; use
     *note importlib.util.find_spec(): 2af. instead.  (Contributed by
     Nikita Sobolev in gh-97850(12).)

   * *note pty: 9f.:

        * ‘master_open()’: use *note pty.openpty(): 2b0.

        * ‘slave_open()’: use *note pty.openpty(): 2b0.

   * *note sqlite3: ba.:

        * *note version: 2b1. and *note version_info: 2b2.

        * *note execute(): 2b3. and *note executemany(): 2b4. if *note
          named placeholders: 2b5. are used and 'parameters' is a
          sequence instead of a *note dict: 23b.

        * date and datetime adapter, date and timestamp converter: see
          the *note sqlite3: ba. documentation for suggested replacement
          recipes.

   * *note types.CodeType: 2b6.: Accessing *note co_lnotab: 2b7. was
     deprecated in PEP 626(13) since 3.10 and was planned to be removed
     in 3.12, but it only got a proper *note DeprecationWarning: 18b. in
     3.12.  May be removed in 3.14.  (Contributed by Nikita Sobolev in
     gh-101866(14).)

   * *note typing: ed.: *note ByteString: 2b8, deprecated since Python
     3.9, now causes a *note DeprecationWarning: 18b. to be emitted when
     it is used.

   * *note urllib: f1.: ‘urllib.parse.Quoter’ is deprecated: it was not
     intended to be a public API. (Contributed by Gregory P. Smith in
     gh-88168(15).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/92248

   (2) https://github.com/python/cpython/issues/90953

   (3) https://github.com/python/cpython/issues/94597

   (4) https://github.com/python/cpython/issues/94597

   (5) https://github.com/python/cpython/issues/100160

   (6) https://github.com/python/cpython/issues/91896

   (7) https://github.com/python/cpython/issues/72346

   (8) https://github.com/python/cpython/issues/97879

   (9) https://github.com/python/cpython/issues/93963

   (10) https://github.com/python/cpython/issues/101588

   (11) https://github.com/python/cpython/issues/84559

   (12) https://github.com/python/cpython/issues/97850

   (13) https://peps.python.org/pep-0626/

   (14) https://github.com/python/cpython/issues/101866

   (15) https://github.com/python/cpython/issues/88168


File: python.info,  Node: Pending Removal in Python 3 15,  Next: Pending Removal in Python 3 16,  Prev: Pending Removal in Python 3 14,  Up: New Deprecations

1.1.8.2 Pending Removal in Python 3.15
......................................

   * *note http.server.CGIHTTPRequestHandler: 281. will be removed along
     with its related ‘--cgi’ flag to ‘python -m http.server’.  It was
     obsolete and rarely used.  No direct replacement exists.
     'Anything' is better than CGI to interface a web server with a
     request handler.

   * *note locale: 7a.: *note locale.getdefaultlocale(): 2ba. was
     deprecated in Python 3.11 and originally planned for removal in
     Python 3.13 (gh-90817(1)), but removal has been postponed to Python
     3.15.  Use *note locale.setlocale(): 2bb, *note
     locale.getencoding(): 2bc. and *note locale.getlocale(): 2bd.
     instead.  (Contributed by Hugo van Kemenade in gh-111187(2).)

   * *note pathlib: 93.: *note pathlib.PurePath.is_reserved(): 286. is
     deprecated and scheduled for removal in Python 3.15.  Use *note
     os.path.isreserved(): 208. to detect reserved paths on Windows.

   * *note platform: 98.: *note java_ver(): 287. is deprecated and will
     be removed in 3.15.  It was largely untested, had a confusing API,
     and was only useful for Jython support.  (Contributed by Nikita
     Sobolev in gh-116349(3).)

   * *note threading: d6.: Passing any arguments to *note
     threading.RLock(): 2be. is now deprecated.  C version allows any
     numbers of args and kwargs, but they are just ignored.  Python
     version does not allow any arguments.  All arguments will be
     removed from *note threading.RLock(): 2be. in Python 3.15.
     (Contributed by Nikita Sobolev in gh-102029(4).)

   * *note typing.NamedTuple: 291.:

        * The undocumented keyword argument syntax for creating
          ‘NamedTuple’ classes (‘NT = NamedTuple("NT", x=int)’) is
          deprecated, and will be disallowed in 3.15.  Use the
          class-based syntax or the functional syntax instead.

        * When using the functional syntax to create a ‘NamedTuple’
          class, failing to pass a value to the 'fields' parameter (‘NT
          = NamedTuple("NT")’) is deprecated.  Passing ‘None’ to the
          'fields' parameter (‘NT = NamedTuple("NT", None)’) is also
          deprecated.  Both will be disallowed in Python 3.15.  To
          create a ‘NamedTuple’ class with 0 fields, use ‘class
          NT(NamedTuple): pass’ or ‘NT = NamedTuple("NT", [])’.

   * *note typing.TypedDict: 146.: When using the functional syntax to
     create a ‘TypedDict’ class, failing to pass a value to the 'fields'
     parameter (‘TD = TypedDict("TD")’) is deprecated.  Passing ‘None’
     to the 'fields' parameter (‘TD = TypedDict("TD", None)’) is also
     deprecated.  Both will be disallowed in Python 3.15.  To create a
     ‘TypedDict’ class with 0 fields, use ‘class TD(TypedDict): pass’ or
     ‘TD = TypedDict("TD", {})’.

   * *note wave: fb.: Deprecate the ‘getmark()’, ‘setmark()’ and
     ‘getmarkers()’ methods of the *note wave.Wave_read: 297. and *note
     wave.Wave_write: 298. classes.  They will be removed in Python
     3.15.  (Contributed by Victor Stinner in gh-105096(5).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/90817

   (2) https://github.com/python/cpython/issues/111187

   (3) https://github.com/python/cpython/issues/116349

   (4) https://github.com/python/cpython/issues/102029

   (5) https://github.com/python/cpython/issues/105096


File: python.info,  Node: Pending Removal in Python 3 16,  Next: Pending Removal in Future Versions,  Prev: Pending Removal in Python 3 15,  Up: New Deprecations

1.1.8.3 Pending Removal in Python 3.16
......................................

   * *note array: 6.: *note array.array: 186. ‘'u'’ type (‘wchar_t’):
     use the ‘'w'’ type instead (‘Py_UCS4’).

   * *note builtins: e.: ‘~bool’, bitwise inversion on bool.

   * *note symtable: c2.: Deprecate *note symtable.Class.get_methods():
     2c0. due to the lack of interest.  (Contributed by Bénédikt Tran in
     gh-119698(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/119698


File: python.info,  Node: Pending Removal in Future Versions,  Prev: Pending Removal in Python 3 16,  Up: New Deprecations

1.1.8.4 Pending Removal in Future Versions
..........................................

The following APIs will be removed in the future, although there is
currently no date scheduled for their removal.

   * *note argparse: 5.: Nesting argument groups and nesting mutually
     exclusive groups are deprecated.

   * *note array: 6.'s ‘'u'’ format code (gh-57281(1))

   * *note builtins: e.:

        * ‘bool(NotImplemented)’.

        * Generators: ‘throw(type, exc, tb)’ and ‘athrow(type, exc, tb)’
          signature is deprecated: use ‘throw(exc)’ and ‘athrow(exc)’
          instead, the single argument signature.

        * Currently Python accepts numeric literals immediately followed
          by keywords, for example ‘0in x’, ‘1or x’, ‘0if 1else 2’.  It
          allows confusing and ambiguous expressions like ‘[0x1for x in
          y]’ (which can be interpreted as ‘[0x1 for x in y]’ or ‘[0x1f
          or x in y]’).  A syntax warning is raised if the numeric
          literal is immediately followed by one of keywords *note and:
          2c2, *note else: 172, *note for: 2c3, *note if: 2c4, *note in:
          2c5, *note is: 2c6. and *note or: 2c7.  In a future release it
          will be changed to a syntax error.  (gh-87999(2))

        * Support for ‘__index__()’ and ‘__int__()’ method returning
          non-int type: these methods will be required to return an
          instance of a strict subclass of *note int: 23c.

        * Support for ‘__float__()’ method returning a strict subclass
          of *note float: 2c8.: these methods will be required to return
          an instance of *note float: 2c8.

        * Support for ‘__complex__()’ method returning a strict subclass
          of *note complex: 2c9.: these methods will be required to
          return an instance of *note complex: 2c9.

        * Delegation of ‘int()’ to ‘__trunc__()’ method.

        * Passing a complex number as the 'real' or 'imag' argument in
          the *note complex(): 2c9. constructor is now deprecated; it
          should only be passed as a single positional argument.
          (Contributed by Serhiy Storchaka in gh-109218(3).)

   * *note calendar: 10.: ‘calendar.January’ and ‘calendar.February’
     constants are deprecated and replaced by *note calendar.JANUARY:
     2ca. and *note calendar.FEBRUARY: 2cb.  (Contributed by Prince
     Roshan in gh-103636(4).)

   * *note codeobject.co_lnotab: 2b7.: use the *note
     codeobject.co_lines(): 2cc. method instead.

   * *note datetime: 28.:

        * *note utcnow(): 2cd.: use
          ‘datetime.datetime.now(tz=datetime.UTC)’.

        * *note utcfromtimestamp(): 2ce.: use
          ‘datetime.datetime.fromtimestamp(timestamp, tz=datetime.UTC)’.

   * *note gettext: 59.: Plural value must be an integer.

   * *note importlib: 6b.:

        * ‘load_module()’ method: use ‘exec_module()’ instead.

        * *note cache_from_source(): 2cf. 'debug_override' parameter is
          deprecated: use the 'optimization' parameter instead.

   * *note importlib.metadata: 6e.:

        * ‘EntryPoints’ tuple interface.

        * Implicit ‘None’ on return values.

   * *note logging: 7b.: the ‘warn()’ method has been deprecated since
     Python 3.3, use *note warning(): 2d0. instead.

   * *note mailbox: 7f.: Use of StringIO input and text mode is
     deprecated, use BytesIO and binary mode instead.

   * *note os: 91.: Calling *note os.register_at_fork(): 2d1. in
     multi-threaded process.

   * ‘pydoc.ErrorDuringImport’: A tuple value for 'exc_info' parameter
     is deprecated, use an exception instance.

   * *note re: a7.: 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(5).)

   * ‘sre_compile’, ‘sre_constants’ and ‘sre_parse’ modules.

   * *note shutil: b3.: *note rmtree(): 2d2.'s 'onerror' parameter is
     deprecated in Python 3.12; use the 'onexc' parameter instead.

   * *note ssl: bb. options and protocols:

        * *note ssl.SSLContext: 276. without protocol argument is
          deprecated.

        * *note ssl.SSLContext: 276.: *note set_npn_protocols(): 2d3.
          and ‘selected_npn_protocol()’ are deprecated: use ALPN
          instead.

        * ‘ssl.OP_NO_SSL*’ options

        * ‘ssl.OP_NO_TLS*’ options

        * ‘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’

   * *note sysconfig.is_python_build(): 2d4. 'check_home' parameter is
     deprecated and ignored.

   * *note threading: d6. methods:

        * ‘threading.Condition.notifyAll()’: use *note notify_all():
          2d5.

        * ‘threading.Event.isSet()’: use *note is_set(): 2d6.

        * ‘threading.Thread.isDaemon()’, *note
          threading.Thread.setDaemon(): 2d7.: use *note
          threading.Thread.daemon: 2d8. attribute.

        * ‘threading.Thread.getName()’, *note
          threading.Thread.setName(): 2d9.: use *note
          threading.Thread.name: 2da. attribute.

        * ‘threading.currentThread()’: use *note
          threading.current_thread(): 2db.

        * ‘threading.activeCount()’: use *note threading.active_count():
          2dc.

   * *note typing.Text: 2dd. (gh-92332(6)).

   * *note unittest.IsolatedAsyncioTestCase: 2de.: it is deprecated to
     return a value that is not ‘None’ from a test case.

   * *note urllib.parse: f3. deprecated functions: *note urlparse():
     2df. instead

        * ‘splitattr()’

        * ‘splithost()’

        * ‘splitnport()’

        * ‘splitpasswd()’

        * ‘splitport()’

        * ‘splitquery()’

        * ‘splittag()’

        * ‘splittype()’

        * ‘splituser()’

        * ‘splitvalue()’

        * ‘to_bytes()’

   * *note urllib.request: f4.: *note URLopener: 2e0. and *note
     FancyURLopener: 2e1. style of invoking requests is deprecated.  Use
     newer *note urlopen(): 275. functions and methods.

   * *note wsgiref: 100.: ‘SimpleHandler.stdout.write()’ should not do
     partial writes.

   * *note xml.etree.ElementTree: 10c.: Testing the truth value of an
     *note Element: 2e2. is deprecated.  In a future release it will
     always return ‘True’.  Prefer explicit ‘len(elem)’ or ‘elem is not
     None’ tests instead.

   * *note zipimport.zipimporter.load_module(): 2e3. is deprecated: use
     *note exec_module(): 2e4. instead.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/57281

   (2) https://github.com/python/cpython/issues/87999

   (3) https://github.com/python/cpython/issues/109218

   (4) https://github.com/python/cpython/issues/103636

   (5) https://github.com/python/cpython/issues/91760

   (6) https://github.com/python/cpython/issues/92332


File: python.info,  Node: CPython Bytecode Changes,  Next: C API Changes,  Prev: New Deprecations,  Up: What's New In Python 3 13

1.1.9 CPython Bytecode Changes
------------------------------

   * The oparg of ‘YIELD_VALUE’ is now ‘1’ if the yield is part of a
     yield-from or await, and ‘0’ otherwise.  The oparg of ‘RESUME’ was
     changed to add a bit indicating whether the except-depth is 1,
     which is needed to optimize closing of generators.  (Contributed by
     Irit Katriel in gh-111354(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/111354


File: python.info,  Node: C API Changes,  Next: Build Changes,  Prev: CPython Bytecode Changes,  Up: What's New In Python 3 13

1.1.10 C API Changes
--------------------

* Menu:

* New Features: New Features<2>.


File: python.info,  Node: New Features<2>,  Up: C API Changes

1.1.10.1 New Features
.....................

   * You no longer have to define the ‘PY_SSIZE_T_CLEAN’ macro before
     including ‘Python.h’ when using ‘#’ formats in *note format codes:
     2e8.  APIs accepting the format codes always use ‘Py_ssize_t’ for
     ‘#’ formats.  (Contributed by Inada Naoki in gh-104922(1).)

   * The 'keywords' parameter of *note PyArg_ParseTupleAndKeywords():
     2e9. and *note PyArg_VaParseTupleAndKeywords(): 2ea. now has type
     char *const* in C and const char *const* in C++, instead of char**.
     It makes these functions compatible with arguments of type const
     char *const*, const char** or char *const* in C++ and char *const*
     in C without an explicit type cast.  This can be overridden with
     the *note PY_CXX_CONST: 2eb. macro.  (Contributed by Serhiy
     Storchaka in gh-65210(2).)

   * Add *note PyImport_AddModuleRef(): 2ec.: similar to *note
     PyImport_AddModule(): 2ed, but return a *note strong reference:
     2ee. instead of a *note borrowed reference: 2ef.  (Contributed by
     Victor Stinner in gh-105922(3).)

   * Add *note PyWeakref_GetRef(): 2f0. function: similar to *note
     PyWeakref_GetObject(): 2f1. but returns a *note strong reference:
     2ee, or ‘NULL’ if the referent is no longer live.  (Contributed by
     Victor Stinner in gh-105927(4).)

   * Add *note PyObject_GetOptionalAttr(): 2f2. and *note
     PyObject_GetOptionalAttrString(): 2f3, variants of *note
     PyObject_GetAttr(): 2f4. and *note PyObject_GetAttrString(): 2f5.
     which don't raise *note AttributeError: 2f6. if the attribute is
     not found.  These variants are more convenient and faster if the
     missing attribute should not be treated as a failure.  (Contributed
     by Serhiy Storchaka in gh-106521(5).)

   * Add *note PyMapping_GetOptionalItem(): 2f7. and *note
     PyMapping_GetOptionalItemString(): 2f8.: variants of *note
     PyObject_GetItem(): 2f9. and *note PyMapping_GetItemString(): 2fa.
     which don't raise *note KeyError: 2fb. if the key is not found.
     These variants are more convenient and faster if the missing key
     should not be treated as a failure.  (Contributed by Serhiy
     Storchaka in gh-106307(6).)

   * Add fixed variants of functions which silently ignore errors:

        - *note PyObject_HasAttrWithError(): 2fc. replaces *note
          PyObject_HasAttr(): 2fd.

        - *note PyObject_HasAttrStringWithError(): 2fe. replaces *note
          PyObject_HasAttrString(): 2ff.

        - *note PyMapping_HasKeyWithError(): 300. replaces *note
          PyMapping_HasKey(): 301.

        - *note PyMapping_HasKeyStringWithError(): 302. replaces *note
          PyMapping_HasKeyString(): 303.

     New functions return not only ‘1’ for true and ‘0’ for false, but
     also ‘-1’ for error.

     (Contributed by Serhiy Storchaka in gh-108511(7).)

   * If Python is built in *note debug mode: 1de. or *note with
     assertions: 304, *note PyTuple_SET_ITEM(): 305. and *note
     PyList_SET_ITEM(): 306. now check the index argument with an
     assertion.  (Contributed by Victor Stinner in gh-106168(8).)

   * Add *note PyModule_Add(): 307. function: similar to *note
     PyModule_AddObjectRef(): 308. and *note PyModule_AddObject(): 309.
     but always steals a reference to the value.  (Contributed by Serhiy
     Storchaka in gh-86493(9).)

   * Add *note PyDict_GetItemRef(): 30a. and *note
     PyDict_GetItemStringRef(): 30b. functions: similar to *note
     PyDict_GetItemWithError(): 30c. but returning a *note strong
     reference: 2ee. instead of a *note borrowed reference: 2ef.
     Moreover, these functions return -1 on error and so checking
     ‘PyErr_Occurred()’ is not needed.  (Contributed by Victor Stinner
     in gh-106004(10).)

   * Added *note PyDict_SetDefaultRef(): 30d, which is similar to *note
     PyDict_SetDefault(): 30e. but returns a *note strong reference:
     2ee. instead of a *note borrowed reference: 2ef.  This function
     returns ‘-1’ on error, ‘0’ on insertion, and ‘1’ if the key was
     already present in the dictionary.  (Contributed by Sam Gross in
     gh-112066(11).)

   * Add *note PyDict_ContainsString(): 30f. function: same as *note
     PyDict_Contains(): 310, but 'key' is specified as a const char*
     UTF-8 encoded bytes string, rather than a *note PyObject: 311.*.
     (Contributed by Victor Stinner in gh-108314(12).)

   * Added *note PyList_GetItemRef(): 312. function: similar to *note
     PyList_GetItem(): 313. but returns a *note strong reference: 2ee.
     instead of a *note borrowed reference: 2ef.

   * Add *note Py_IsFinalizing(): 314. function: check if the main
     Python interpreter is *note shutting down: 133.  (Contributed by
     Victor Stinner in gh-108014(13).)

   * Add *note PyLong_AsInt(): 315. function: similar to *note
     PyLong_AsLong(): 316, but store the result in a C int instead of a
     C long.  Previously, it was known as the private function
     ‘_PyLong_AsInt()’ (with an underscore prefix).  (Contributed by
     Victor Stinner in gh-108014(14).)

   * Python built with ‘configure’ *note -with-trace-refs: 317. (tracing
     references) now supports the *note Limited API: 318.  (Contributed
     by Victor Stinner in gh-108634(15).)

   * Add *note PyObject_VisitManagedDict(): 319. and *note
     PyObject_ClearManagedDict(): 31a. functions which must be called by
     the traverse and clear functions of a type using *note
     Py_TPFLAGS_MANAGED_DICT: 31b. flag.  The pythoncapi-compat
     project(16) can be used to get these functions on Python 3.11 and
     3.12.  (Contributed by Victor Stinner in gh-107073(17).)

   * Add *note PyUnicode_EqualToUTF8AndSize(): 31c. and *note
     PyUnicode_EqualToUTF8(): 31d. functions: compare Unicode object
     with a const char* UTF-8 encoded string and return true (‘1’) if
     they are equal, or false (‘0’) otherwise.  These functions do not
     raise exceptions.  (Contributed by Serhiy Storchaka in
     gh-110289(18).)

   * Add *note PyThreadState_GetUnchecked(): 31e. function: similar to
     *note PyThreadState_Get(): 31f, but don't kill the process with a
     fatal error if it is NULL. The caller is responsible to check if
     the result is NULL. Previously, the function was private and known
     as ‘_PyThreadState_UncheckedGet()’.  (Contributed by Victor Stinner
     in gh-108867(19).)

   * Add *note PySys_AuditTuple(): 320. function: similar to *note
     PySys_Audit(): 321, but pass event arguments as a Python *note
     tuple: 322. object.  (Contributed by Victor Stinner in
     gh-85283(20).)

   * *note PyArg_ParseTupleAndKeywords(): 2e9. now supports non-ASCII
     keyword parameter names.  (Contributed by Serhiy Storchaka in
     gh-110815(21).)

   * Add *note PyMem_RawMalloc(): 323, *note PyMem_RawCalloc(): 324,
     *note PyMem_RawRealloc(): 325. and *note PyMem_RawFree(): 326. to
     the limited C API (version 3.13).  (Contributed by Victor Stinner
     in gh-85283(22).)

   * Add *note PySys_Audit(): 321. and *note PySys_AuditTuple(): 320.
     functions to the limited C API. (Contributed by Victor Stinner in
     gh-85283(23).)

   * Add *note PyErr_FormatUnraisable(): 327. function: similar to *note
     PyErr_WriteUnraisable(): 328, but allow customizing the warning
     message.  (Contributed by Serhiy Storchaka in gh-108082(24).)

   * Add *note PyList_Extend(): 329. and *note PyList_Clear(): 32a.
     functions: similar to Python ‘list.extend()’ and ‘list.clear()’
     methods.  (Contributed by Victor Stinner in gh-111138(25).)

   * Add *note PyDict_Pop(): 32b. and *note PyDict_PopString(): 32c.
     functions: remove a key from a dictionary and optionally return the
     removed value.  This is similar to *note dict.pop(): 32d, but
     without the default value and not raising *note KeyError: 2fb. if
     the key is missing.  (Contributed by Stefan Behnel and Victor
     Stinner in gh-111262(26).)

   * Add *note Py_HashPointer(): 32e. function to hash a pointer.
     (Contributed by Victor Stinner in gh-111545(27).)

   * Add *note PyObject_GenericHash(): 32f. function that implements the
     default hashing function of a Python object.  (Contributed by
     Serhiy Storchaka in gh-113024(28).)

   * Add PyTime C API:

        * *note PyTime_t: 330. type.

        * *note PyTime_MIN: 331. and *note PyTime_MAX: 332. constants.

        * Add functions:

             * *note PyTime_AsSecondsDouble(): 333.

             * *note PyTime_Monotonic(): 334.

             * *note PyTime_MonotonicRaw(): 335.

             * *note PyTime_PerfCounter(): 336.

             * *note PyTime_PerfCounterRaw(): 337.

             * *note PyTime_Time(): 338.

             * *note PyTime_TimeRaw(): 339.

     (Contributed by Victor Stinner and Petr Viktorin in gh-110850(29).)

   * Add *note PyLong_AsNativeBytes(): 33a, *note
     PyLong_FromNativeBytes(): 33b. and *note
     PyLong_FromUnsignedNativeBytes(): 33c. functions to simplify
     converting between native integer types and Python *note int: 23c.
     objects.  (Contributed by Steve Dower in gh-111140(30).)

   * Add *note PyType_GetFullyQualifiedName(): 33d. function to get the
     type's fully qualified name.  Equivalent to
     ‘f"{type.__module__}.{type.__qualname__}"’, or ‘type.__qualname__’
     if ‘type.__module__’ is not a string or is equal to ‘"builtins"’.
     (Contributed by Victor Stinner in gh-111696(31).)

   * Add *note PyType_GetModuleName(): 33e. function to get the type's
     module name.  Equivalent to getting the ‘type.__module__’
     attribute.  (Contributed by Eric Snow and Victor Stinner in
     gh-111696(32).)

   * Add support for ‘%T’, ‘%#T’, ‘%N’ and ‘%#N’ formats to *note
     PyUnicode_FromFormat(): 33f.: format the fully qualified name of an
     object type and of a type: call *note PyType_GetModuleName(): 33e.
     See PEP 737(33) for more information.  (Contributed by Victor
     Stinner in gh-111696(34).)

   * Add *note Py_GetConstant(): 340. and *note
     Py_GetConstantBorrowed(): 341. functions to get constants.  For
     example, ‘Py_GetConstant(Py_CONSTANT_ZERO)’ returns a *note strong
     reference: 2ee. to the constant zero.  (Contributed by Victor
     Stinner in gh-115754(35).)

   * Add *note PyType_GetModuleByDef(): 342. to the limited C API
     (Contributed by Victor Stinner in gh-116936(36).)

   * Add two new functions to the C-API, *note PyRefTracer_SetTracer():
     343. and *note PyRefTracer_GetTracer(): 344, that allow to track
     object creation and destruction the same way the *note tracemalloc:
     e8. module does.  (Contributed by Pablo Galindo in gh-93502(37).)

   * Add *note PyEval_GetFrameBuiltins(): 345, *note
     PyEval_GetFrameGlobals(): 346, and *note PyEval_GetFrameLocals():
     347. to the C API. These replacements for *note
     PyEval_GetBuiltins(): 348, *note PyEval_GetGlobals(): 349, and
     *note PyEval_GetLocals(): 34a. return *note strong references: 2ee.
     rather than borrowed references.  (Added as part of PEP 667(38).)

   * Add *note PyMutex: 140. API, a lightweight mutex that occupies a
     single byte.  The *note PyMutex_Lock(): 34b. function will release
     the GIL (if currently held) if the operation needs to block.
     (Contributed by Sam Gross in gh-108724(39).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/104922

   (2) https://github.com/python/cpython/issues/65210

   (3) https://github.com/python/cpython/issues/105922

   (4) https://github.com/python/cpython/issues/105927

   (5) https://github.com/python/cpython/issues/106521

   (6) https://github.com/python/cpython/issues/106307

   (7) https://github.com/python/cpython/issues/108511

   (8) https://github.com/python/cpython/issues/106168

   (9) https://github.com/python/cpython/issues/86493

   (10) https://github.com/python/cpython/issues/106004

   (11) https://github.com/python/cpython/issues/112066

   (12) https://github.com/python/cpython/issues/108314

   (13) https://github.com/python/cpython/issues/108014

   (14) https://github.com/python/cpython/issues/108014

   (15) https://github.com/python/cpython/issues/108634

   (16) https://github.com/python/pythoncapi-compat/

   (17) https://github.com/python/cpython/issues/107073

   (18) https://github.com/python/cpython/issues/110289

   (19) https://github.com/python/cpython/issues/108867

   (20) https://github.com/python/cpython/issues/85283

   (21) https://github.com/python/cpython/issues/110815

   (22) https://github.com/python/cpython/issues/85283

   (23) https://github.com/python/cpython/issues/85283

   (24) https://github.com/python/cpython/issues/108082

   (25) https://github.com/python/cpython/issues/111138

   (26) https://github.com/python/cpython/issues/111262

   (27) https://github.com/python/cpython/issues/111545

   (28) https://github.com/python/cpython/issues/113024

   (29) https://github.com/python/cpython/issues/110850

   (30) https://github.com/python/cpython/issues/111140

   (31) https://github.com/python/cpython/issues/111696

   (32) https://github.com/python/cpython/issues/111696

   (33) https://peps.python.org/pep-0737/

   (34) https://github.com/python/cpython/issues/111696

   (35) https://github.com/python/cpython/issues/115754

   (36) https://github.com/python/cpython/issues/116936

   (37) https://github.com/python/cpython/issues/93502

   (38) https://peps.python.org/pep-0667/

   (39) https://github.com/python/cpython/issues/108724


File: python.info,  Node: Build Changes,  Next: Porting to Python 3 13,  Prev: C API Changes,  Up: What's New In Python 3 13

1.1.11 Build Changes
--------------------

   * The ‘configure’ option *note -with-system-libmpdec: 34d. now
     defaults to ‘yes’.  The bundled copy of ‘libmpdecimal’ will be
     removed in Python 3.15.

   * Autoconf 2.71 and aclocal 1.16.4 are now required to regenerate the
     ‘configure’ script.  (Contributed by Christian Heimes in
     gh-89886(1).)

   * SQLite 3.15.2 or newer is required to build the *note sqlite3: ba.
     extension module.  (Contributed by Erlend Aasland in gh-105875(2).)

   * Python built with ‘configure’ *note -with-trace-refs: 317. (tracing
     references) is now ABI compatible with the Python release build and
     *note debug build: 1de.  (Contributed by Victor Stinner in
     gh-108634(3).)

   * Building CPython now requires a compiler with support for the C11
     atomic library, GCC built-in atomic functions, or MSVC interlocked
     intrinsics.

   * The ‘errno’, ‘fcntl’, ‘grp’, ‘md5’, ‘pwd’, ‘resource’, ‘termios’,
     ‘winsound’, ‘_ctypes_test’, ‘_multiprocessing.posixshmem’,
     ‘_scproxy’, ‘_stat’, ‘_statistics’, ‘_testconsole’,
     ‘_testimportmultiple’ and ‘_uuid’ C extensions are now built with
     the *note limited C API: 318.  (Contributed by Victor Stinner in
     gh-85283(4).)

   * ‘wasm32-wasi’ is now a PEP 11(5) tier 2 platform.  (Contributed by
     Brett Cannon in gh-115192(6).)

   * ‘wasm32-emscripten’ is no longer a PEP 11(7) supported platform.
     (Contributed by Brett Cannon in gh-115192(8).)

   * Python now bundles the mimalloc library(9).  It is licensed under
     the MIT license; see *note mimalloc license: 34e.  The bundled
     mimalloc has custom changes, see gh-113141(10) for details.
     (Contributed by Dino Viehland in gh-109914(11).)

   * On POSIX systems, the pkg-config (‘.pc’) filenames now include the
     ABI flags.  For example, the free-threaded build generates
     ‘python-3.13t.pc’ and the debug build generates ‘python-3.13d.pc’.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/89886

   (2) https://github.com/python/cpython/issues/105875

   (3) https://github.com/python/cpython/issues/108634

   (4) https://github.com/python/cpython/issues/85283

   (5) https://peps.python.org/pep-0011/

   (6) https://github.com/python/cpython/issues/115192

   (7) https://peps.python.org/pep-0011/

   (8) https://github.com/python/cpython/issues/115192

   (9) https://github.com/microsoft/mimalloc

   (10) https://github.com/python/cpython/issues/113141

   (11) https://github.com/python/cpython/issues/109914


File: python.info,  Node: Porting to Python 3 13,  Next: Regression Test Changes,  Prev: Build Changes,  Up: What's New In Python 3 13

1.1.12 Porting to Python 3.13
-----------------------------

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

* Menu:

* Changes in the Python API::
* Changes in the C API::
* Removed C APIs::
* Deprecated C APIs::


File: python.info,  Node: Changes in the Python API,  Next: Changes in the C API,  Up: Porting to Python 3 13

1.1.12.1 Changes in the Python API
..................................

   * An *note OSError: 350. is now raised by *note getpass.getuser():
     351. for any failure to retrieve a username, instead of *note
     ImportError: 352. on non-Unix platforms or *note KeyError: 2fb. on
     Unix platforms where the password database is empty.

   * The *note threading: d6. 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
     must provide ‘_is_main_interpreter()’, just like the module's other
     "private" attributes.  (See gh-112826(1).)

   * *note mailbox.Maildir: 353. now ignores files with a leading dot.
     (Contributed by Zackery Spytz in gh-65559(2).)

   * *note pathlib.Path.glob(): 212. and *note rglob(): 213. now return
     both files and directories if a pattern that ends with "‘**’" is
     given, rather than directories only.  Users may add a trailing
     slash to match only directories.

   * The value of the ‘mode’ attribute of *note gzip.GzipFile: 354. was
     changed from integer (‘1’ or ‘2’) to string (‘'rb'’ or ‘'wb'’).
     The value of the ‘mode’ attribute of the readable file-like object
     returned by *note zipfile.ZipFile.open(): 355. was changed from
     ‘'r'’ to ‘'rb'’.  (Contributed by Serhiy Storchaka in
     gh-115961(3).)

   * *note functools.partial: 356. now emits a *note FutureWarning: 357.
     when it is used as a method.  Its behavior will be changed in
     future Python versions.  Wrap it in *note staticmethod(): 358. if
     you want to preserve the old behavior.  (Contributed by Serhiy
     Storchaka in gh-121027(4).)

   * Calling *note locals(): 127. in an *note optimized scope: 161. now
     produces an independent snapshot on each call, and hence no longer
     implicitly updates previously returned references.  Obtaining the
     legacy CPython behaviour now requires explicit calls to update the
     initially returned dictionary with the results of subsequent calls
     to ‘locals()’.  Code execution functions that implicitly target
     ‘locals()’ (such as ‘exec’ and ‘eval’) must be passed an explicit
     namespace to access their results in an optimized scope.  (Changed
     as part of PEP 667(5).)

   * Calling *note locals(): 127. from a comprehension at module or
     class scope (including via ‘exec’ or ‘eval’) once more behaves as
     if the comprehension were running as an independent nested function
     (i.e.  the local variables from the containing scope are not
     included).  In Python 3.12, this had changed to include the local
     variables from the containing scope when implementing PEP 709(6).
     (Changed as part of PEP 667(7).)

   * Accessing *note FrameType.f_locals: 165. in an *note optimized
     scope: 161. now returns a write-through proxy rather than a
     snapshot that gets updated at ill-specified times.  If a snapshot
     is desired, it must be created explicitly with ‘dict’ or the
     proxy's ‘.copy()’ method.  (Changed as part of PEP 667(8).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/112826

   (2) https://github.com/python/cpython/issues/65559

   (3) https://github.com/python/cpython/issues/115961

   (4) https://github.com/python/cpython/issues/121027

   (5) https://peps.python.org/pep-0667/

   (6) https://peps.python.org/pep-0709/

   (7) https://peps.python.org/pep-0667/

   (8) https://peps.python.org/pep-0667/


File: python.info,  Node: Changes in the C API,  Next: Removed C APIs,  Prev: Changes in the Python API,  Up: Porting to Python 3 13

1.1.12.2 Changes in the C API
.............................

   * ‘Python.h’ no longer includes the ‘<ieeefp.h>’ standard header.  It
     was included for the ‘finite()’ function which is now provided by
     the ‘<math.h>’ header.  It should now be included explicitly if
     needed.  Remove also the ‘HAVE_IEEEFP_H’ macro.  (Contributed by
     Victor Stinner in gh-108765(1).)

   * ‘Python.h’ no longer includes these standard header files:
     ‘<time.h>’, ‘<sys/select.h>’ and ‘<sys/time.h>’.  If needed, they
     should now be included explicitly.  For example, ‘<time.h>’
     provides the ‘clock()’ and ‘gmtime()’ functions, ‘<sys/select.h>’
     provides the ‘select()’ function, and ‘<sys/time.h>’ provides the
     ‘futimes()’, ‘gettimeofday()’ and ‘setitimer()’ functions.
     (Contributed by Victor Stinner in gh-108765(2).)

   * On Windows, ‘Python.h’ no longer includes the ‘<stddef.h>’ standard
     header file.  If needed, it should now be included explicitly.  For
     example, it provides ‘offsetof()’ function, and ‘size_t’ and
     ‘ptrdiff_t’ types.  Including ‘<stddef.h>’ explicitly was already
     needed by all other platforms, the ‘HAVE_STDDEF_H’ macro is only
     defined on Windows.  (Contributed by Victor Stinner in
     gh-108765(3).)

   * If the *note Py_LIMITED_API: 35a. macro is defined,
     ‘Py_BUILD_CORE’, ‘Py_BUILD_CORE_BUILTIN’ and ‘Py_BUILD_CORE_MODULE’
     macros are now undefined by ‘<Python.h>’.  (Contributed by Victor
     Stinner in gh-85283(4).)

   * The old trashcan macros ‘Py_TRASHCAN_SAFE_BEGIN’ and
     ‘Py_TRASHCAN_SAFE_END’ were removed.  They should be replaced by
     the new macros ‘Py_TRASHCAN_BEGIN’ and ‘Py_TRASHCAN_END’.

     A ‘tp_dealloc’ function that has the old macros, such as:

          static void
          mytype_dealloc(mytype *p)
          {
              PyObject_GC_UnTrack(p);
              Py_TRASHCAN_SAFE_BEGIN(p);
              ...
              Py_TRASHCAN_SAFE_END
          }

     should migrate to the new macros as follows:

          static void
          mytype_dealloc(mytype *p)
          {
              PyObject_GC_UnTrack(p);
              Py_TRASHCAN_BEGIN(p, mytype_dealloc)
              ...
              Py_TRASHCAN_END
          }

     Note that ‘Py_TRASHCAN_BEGIN’ has a second argument which should be
     the deallocation function it is in.  The new macros were added in
     Python 3.8 and the old macros were deprecated in Python 3.11.
     (Contributed by Irit Katriel in gh-105111(5).)

   * Functions *note PyDict_GetItem(): 35b, *note
     PyDict_GetItemString(): 35c, *note PyMapping_HasKey(): 301, *note
     PyMapping_HasKeyString(): 303, *note PyObject_HasAttr(): 2fd, *note
     PyObject_HasAttrString(): 2ff, and *note PySys_GetObject(): 35d,
     which clear all errors which occurred when calling them, now report
     them using *note sys.unraisablehook(): 1dc.  You may replace them
     with other functions as recommended in the documentation.
     (Contributed by Serhiy Storchaka in gh-106672(6).)

   * ‘PyCode_GetFirstFree()’ is an unstable API now and has been renamed
     to *note PyUnstable_Code_GetFirstFree(): 35e.  (Contributed by
     Bogdan Romanyuk in gh-115781(7).)

   * The effects of mutating the dictionary returned from *note
     PyEval_GetLocals(): 34a. in an *note optimized scope: 161. have
     changed.  New dict entries added this way will now 'only' be
     visible to subsequent *note PyEval_GetLocals(): 34a. calls in that
     frame, as *note PyFrame_GetLocals(): 35f, *note locals(): 127, and
     *note FrameType.f_locals: 165. no longer access the same underlying
     cached dictionary.  Changes made to entries for actual variable
     names and names added via the write-through proxy interfaces will
     be overwritten on subsequent calls to *note PyEval_GetLocals():
     34a. in that frame.  The recommended code update depends on how the
     function was being used, so refer to the deprecation notice on the
     function for details.  (Changed as part of PEP 667(8).)

   * Calling *note PyFrame_GetLocals(): 35f. in an *note optimized
     scope: 161. now returns a write-through proxy rather than a
     snapshot that gets updated at ill-specified times.  If a snapshot
     is desired, it must be created explicitly (e.g.  with *note
     PyDict_Copy(): 360.) or by calling the new *note
     PyEval_GetFrameLocals(): 347. API. (Changed as part of PEP 667(9).)

   * ‘PyFrame_FastToLocals()’ and ‘PyFrame_FastToLocalsWithError()’ no
     longer have any effect.  Calling these functions has been redundant
     since Python 3.11, when *note PyFrame_GetLocals(): 35f. was first
     introduced.  (Changed as part of PEP 667(10).)

   * ‘PyFrame_LocalsToFast()’ no longer has any effect.  Calling this
     function is redundant now that *note PyFrame_GetLocals(): 35f.
     returns a write-through proxy for *note optimized scopes: 161.
     (Changed as part of PEP 667(11).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/108765

   (2) https://github.com/python/cpython/issues/108765

   (3) https://github.com/python/cpython/issues/108765

   (4) https://github.com/python/cpython/issues/85283

   (5) https://github.com/python/cpython/issues/105111

   (6) https://github.com/python/cpython/issues/106672

   (7) https://github.com/python/cpython/issues/115781

   (8) https://peps.python.org/pep-0667/

   (9) https://peps.python.org/pep-0667/

   (10) https://peps.python.org/pep-0667/

   (11) https://peps.python.org/pep-0667/


File: python.info,  Node: Removed C APIs,  Next: Deprecated C APIs,  Prev: Changes in the C API,  Up: Porting to Python 3 13

1.1.12.3 Removed C APIs
.......................

   * Remove many APIs (functions, macros, variables) with names prefixed
     by ‘_Py’ or ‘_PY’ (considered as private API). If your project is
     affected by one of these removals and you consider that the removed
     API should remain available, please open a new issue to request a
     public C API and add ‘cc @vstinner’ to the issue to notify Victor
     Stinner.  (Contributed by Victor Stinner in gh-106320(1).)

   * Remove functions deprecated in Python 3.9:

        * ‘PyEval_CallObject()’, ‘PyEval_CallObjectWithKeywords()’: use
          *note PyObject_CallNoArgs(): 362. or *note PyObject_Call():
          363. instead.  Warning: *note PyObject_Call(): 363. positional
          arguments must be a *note tuple: 322. and must not be ‘NULL’,
          keyword arguments must be a *note dict: 23b. or ‘NULL’,
          whereas removed functions checked arguments type and accepted
          ‘NULL’ positional and keyword arguments.  To replace
          ‘PyEval_CallObjectWithKeywords(func, NULL, kwargs)’ with *note
          PyObject_Call(): 363, pass an empty tuple as positional
          arguments using *note PyTuple_New(0): 364.

        * ‘PyEval_CallFunction()’: use *note PyObject_CallFunction():
          365. instead.

        * ‘PyEval_CallMethod()’: use *note PyObject_CallMethod(): 366.
          instead.

        * ‘PyCFunction_Call()’: use *note PyObject_Call(): 363. instead.

     (Contributed by Victor Stinner in gh-105107(2).)

   * Remove old buffer protocols deprecated in Python 3.0.  Use *note
     緩衝協定 (Buffer Protocol): 367. instead.

        * ‘PyObject_CheckReadBuffer()’: Use *note
          PyObject_CheckBuffer(): 368. to test if the object supports
          the buffer protocol.  Note that *note PyObject_CheckBuffer():
          368. doesn't guarantee that *note PyObject_GetBuffer(): 369.
          will succeed.  To test if the object is actually readable, see
          the next example of *note PyObject_GetBuffer(): 369.

        * ‘PyObject_AsCharBuffer()’, ‘PyObject_AsReadBuffer()’: *note
          PyObject_GetBuffer(): 369. and *note PyBuffer_Release(): 36a.
          instead:

               Py_buffer view;
               if (PyObject_GetBuffer(obj, &view, PyBUF_SIMPLE) < 0) {
                   return NULL;
               }
               // Use `view.buf` and `view.len` to read from the buffer.
               // You may need to cast buf as `(const char*)view.buf`.
               PyBuffer_Release(&view);

        * ‘PyObject_AsWriteBuffer()’: Use *note PyObject_GetBuffer():
          369. and *note PyBuffer_Release(): 36a. instead:

               Py_buffer view;
               if (PyObject_GetBuffer(obj, &view, PyBUF_WRITABLE) < 0) {
                   return NULL;
               }
               // Use `view.buf` and `view.len` to write to the buffer.
               PyBuffer_Release(&view);

     (Contributed by Inada Naoki in gh-85275(3).)

   * Remove the following old functions to configure the Python
     initialization, deprecated in Python 3.11:

        * ‘PySys_AddWarnOptionUnicode()’: use *note
          PyConfig.warnoptions: 36b. instead.

        * ‘PySys_AddWarnOption()’: use *note PyConfig.warnoptions: 36b.
          instead.

        * ‘PySys_AddXOption()’: use *note PyConfig.xoptions: 36c.
          instead.

        * ‘PySys_HasWarnOptions()’: use *note PyConfig.xoptions: 36c.
          instead.

        * ‘PySys_SetPath()’: set *note PyConfig.module_search_paths:
          36d. instead.

        * ‘Py_SetPath()’: set *note PyConfig.module_search_paths: 36d.
          instead.

        * ‘Py_SetStandardStreamEncoding()’: set *note
          PyConfig.stdio_encoding: 36e. instead, and set also maybe
          *note PyConfig.legacy_windows_stdio: 36f. (on Windows).

        * ‘_Py_SetProgramFullPath()’: set *note PyConfig.executable:
          370. instead.

     Use the new *note PyConfig: 371. API of the *note Python
     Initialization Configuration: 372. instead ( PEP 587(4)), added to
     Python 3.8.  (Contributed by Victor Stinner in gh-105145(5).)

   * Remove ‘PyEval_ThreadsInitialized()’ function, deprecated in Python
     3.9.  Since Python 3.7, ‘Py_Initialize()’ always creates the GIL:
     calling ‘PyEval_InitThreads()’ does nothing and
     ‘PyEval_ThreadsInitialized()’ always returned non-zero.
     (Contributed by Victor Stinner in gh-105182(6).)

   * Remove ‘PyEval_AcquireLock()’ and ‘PyEval_ReleaseLock()’ functions,
     deprecated in Python 3.2.  They didn't update the current thread
     state.  They can be replaced with:

        * *note PyEval_SaveThread(): 373. and *note
          PyEval_RestoreThread(): 374.;

        * low-level *note PyEval_AcquireThread(): 375. and *note
          PyEval_RestoreThread(): 374.;

        * or *note PyGILState_Ensure(): 376. and *note
          PyGILState_Release(): 377.

     (Contributed by Victor Stinner in gh-105182(7).)

   * Remove private ‘_PyObject_FastCall()’ function: use
     ‘PyObject_Vectorcall()’ which is available since Python 3.8 ( PEP
     590(8)).  (Contributed by Victor Stinner in gh-106023(9).)

   * Remove ‘cpython/pytime.h’ header file: it only contained private
     functions.  (Contributed by Victor Stinner in gh-106316(10).)

   * Remove ‘_PyInterpreterState_Get()’ alias to *note
     PyInterpreterState_Get(): 378. which was kept for backward
     compatibility with Python 3.8.  The pythoncapi-compat project(11)
     can be used to get *note PyInterpreterState_Get(): 378. on Python
     3.8 and older.  (Contributed by Victor Stinner in gh-106320(12).)

   * The *note PyModule_AddObject(): 309. function is now *note soft
     deprecated: 1ee.: *note PyModule_Add(): 307. or *note
     PyModule_AddObjectRef(): 308. functions should be used instead.
     (Contributed by Serhiy Storchaka in gh-86493(13).)

   * Remove undocumented ‘PY_TIMEOUT_MAX’ constant from the limited C
     API. (Contributed by Victor Stinner in gh-110014(14).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/106320

   (2) https://github.com/python/cpython/issues/105107

   (3) https://github.com/python/cpython/issues/85275

   (4) https://peps.python.org/pep-0587/

   (5) https://github.com/python/cpython/issues/105145

   (6) https://github.com/python/cpython/issues/105182

   (7) https://github.com/python/cpython/issues/105182

   (8) https://peps.python.org/pep-0590/

   (9) https://github.com/python/cpython/issues/106023

   (10) https://github.com/python/cpython/issues/106316

   (11) https://github.com/python/pythoncapi-compat/

   (12) https://github.com/python/cpython/issues/106320

   (13) https://github.com/python/cpython/issues/86493

   (14) https://github.com/python/cpython/issues/110014


File: python.info,  Node: Deprecated C APIs,  Prev: Removed C APIs,  Up: Porting to Python 3 13

1.1.12.4 Deprecated C APIs
..........................

   * Deprecate the old ‘Py_UNICODE’ and ‘PY_UNICODE_TYPE’ types: use
     directly the ‘wchar_t’ type instead.  Since Python 3.3,
     ‘Py_UNICODE’ and ‘PY_UNICODE_TYPE’ are just aliases to ‘wchar_t’.
     (Contributed by Victor Stinner in gh-105156(1).)

   * Deprecate old Python initialization functions:

        * *note PySys_ResetWarnOptions(): 37a.: clear *note
          sys.warnoptions: 37b. and ‘warnings.filters’ instead.

        * *note Py_GetExecPrefix(): 37c.: get *note sys.exec_prefix:
          37d. instead.

        * *note Py_GetPath(): 37e.: get *note sys.path: 37f. instead.

        * *note Py_GetPrefix(): 380.: get *note sys.prefix: 381.
          instead.

        * *note Py_GetProgramFullPath(): 382.: get *note sys.executable:
          383. instead.

        * *note Py_GetProgramName(): 384.: get *note sys.executable:
          383. instead.

        * *note Py_GetPythonHome(): 385.: get *note PyConfig.home: 386.
          or *note PYTHONHOME: 387. environment variable instead.

     Functions scheduled for removal in Python 3.15.  (Contributed by
     Victor Stinner in gh-105145(2).)

   * Deprecate the *note PyImport_ImportModuleNoBlock(): 388. function
     which is just an alias to *note PyImport_ImportModule(): 389. since
     Python 3.3.  Scheduled for removal in Python 3.15.  (Contributed by
     Victor Stinner in gh-105396(3).)

   * Deprecate the *note PyWeakref_GetObject(): 2f1. and *note
     PyWeakref_GET_OBJECT(): 38a. functions, which return a *note
     borrowed reference: 2ef.: use the new *note PyWeakref_GetRef():
     2f0. function instead, it returns a *note strong reference: 2ee.
     The pythoncapi-compat project(4) can be used to get *note
     PyWeakref_GetRef(): 2f0. on Python 3.12 and older.  (Contributed by
     Victor Stinner in gh-105927(5).)

   * Deprecate the *note PyEval_GetBuiltins(): 348, *note
     PyEval_GetGlobals(): 349, and *note PyEval_GetLocals(): 34a.
     functions, which return a *note borrowed reference: 2ef.  Refer to
     the deprecation notices on each function for their recommended
     replacements.  (Soft deprecated as part of PEP 667(6).)

* Menu:

* Pending Removal in Python 3.14: Pending Removal in Python 3 14<2>.
* Pending Removal in Python 3.15: Pending Removal in Python 3 15<2>.
* Pending Removal in Future Versions: Pending Removal in Future Versions<2>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/105156

   (2) https://github.com/python/cpython/issues/105145

   (3) https://github.com/python/cpython/issues/105396

   (4) https://github.com/python/pythoncapi-compat/

   (5) https://github.com/python/cpython/issues/105927

   (6) https://peps.python.org/pep-0667/


File: python.info,  Node: Pending Removal in Python 3 14<2>,  Next: Pending Removal in Python 3 15<2>,  Up: Deprecated C APIs

1.1.12.5 Pending Removal in Python 3.14
.......................................

   * The ‘ma_version_tag’ field in *note PyDictObject: 38c. for
     extension modules ( PEP 699(1); gh-101193(2)).

   * Creating *note immutable types: 38d. with mutable bases
     (gh-95388(3)).

   * Functions to configure Python's initialization, deprecated in
     Python 3.11:

        * ‘PySys_SetArgvEx()’: set *note PyConfig.argv: 38e. instead.

        * ‘PySys_SetArgv()’: set *note PyConfig.argv: 38e. instead.

        * ‘Py_SetProgramName()’: set *note PyConfig.program_name: 38f.
          instead.

        * ‘Py_SetPythonHome()’: set *note PyConfig.home: 386. instead.

     The *note Py_InitializeFromConfig(): 390. API should be used with
     *note PyConfig: 371. instead.

   * Global configuration variables:

        * *note Py_DebugFlag: 391.: use *note PyConfig.parser_debug:
          392. instead.

        * *note Py_VerboseFlag: 393.: use *note PyConfig.verbose: 394.
          instead.

        * *note Py_QuietFlag: 395.: use *note PyConfig.quiet: 396.
          instead.

        * *note Py_InteractiveFlag: 397.: use *note
          PyConfig.interactive: 398. instead.

        * *note Py_InspectFlag: 399.: use *note PyConfig.inspect: 39a.
          instead.

        * *note Py_OptimizeFlag: 39b.: use *note
          PyConfig.optimization_level: 39c. instead.

        * *note Py_NoSiteFlag: 39d.: use *note PyConfig.site_import:
          39e. instead.

        * *note Py_BytesWarningFlag: 39f.: use *note
          PyConfig.bytes_warning: 3a0. instead.

        * *note Py_FrozenFlag: 3a1.: use *note
          PyConfig.pathconfig_warnings: 3a2. instead.

        * *note Py_IgnoreEnvironmentFlag: 3a3.: use *note
          PyConfig.use_environment: 3a4. instead.

        * *note Py_DontWriteBytecodeFlag: 3a5.: use *note
          PyConfig.write_bytecode: 3a6. instead.

        * *note Py_NoUserSiteDirectory: 3a7.: use *note
          PyConfig.user_site_directory: 3a8. instead.

        * *note Py_UnbufferedStdioFlag: 3a9.: use *note
          PyConfig.buffered_stdio: 3aa. instead.

        * *note Py_HashRandomizationFlag: 3ab.: use *note
          PyConfig.use_hash_seed: 3ac. and *note PyConfig.hash_seed:
          3ad. instead.

        * *note Py_IsolatedFlag: 3ae.: use *note PyConfig.isolated: 3af.
          instead.

        * *note Py_LegacyWindowsFSEncodingFlag: 3b0.: use *note
          PyPreConfig.legacy_windows_fs_encoding: 3b1. instead.

        * *note Py_LegacyWindowsStdioFlag: 3b2.: use *note
          PyConfig.legacy_windows_stdio: 36f. instead.

        * ‘Py_FileSystemDefaultEncoding’: use *note
          PyConfig.filesystem_encoding: 3b3. instead.

        * ‘Py_HasFileSystemDefaultEncoding’: use *note
          PyConfig.filesystem_encoding: 3b3. instead.

        * ‘Py_FileSystemDefaultEncodeErrors’: use *note
          PyConfig.filesystem_errors: 3b4. instead.

        * ‘Py_UTF8Mode’: use *note PyPreConfig.utf8_mode: 3b5. instead.
          (see *note Py_PreInitialize(): 3b6.)

     The *note Py_InitializeFromConfig(): 390. API should be used with
     *note PyConfig: 371. instead.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0699/

   (2) https://github.com/python/cpython/issues/101193

   (3) https://github.com/python/cpython/issues/95388


File: python.info,  Node: Pending Removal in Python 3 15<2>,  Next: Pending Removal in Future Versions<2>,  Prev: Pending Removal in Python 3 14<2>,  Up: Deprecated C APIs

1.1.12.6 Pending Removal in Python 3.15
.......................................

   * The bundled copy of ‘libmpdecimal’.

   * *note PyImport_ImportModuleNoBlock(): 388.: use *note
     PyImport_ImportModule(): 389. instead.

   * *note PyWeakref_GET_OBJECT(): 38a.: use *note PyWeakref_GetRef():
     2f0. instead.

   * *note PyWeakref_GetObject(): 2f1.: use *note PyWeakref_GetRef():
     2f0. instead.

   * ‘Py_UNICODE_WIDE’ type: use ‘wchar_t’ instead.

   * *note Py_UNICODE: 3b8. type: use ‘wchar_t’ instead.

   * Python initialization functions:

        * *note PySys_ResetWarnOptions(): 37a.: clear *note
          sys.warnoptions: 37b. and ‘warnings.filters’ instead.

        * *note Py_GetExecPrefix(): 37c.: get *note sys.exec_prefix:
          37d. instead.

        * *note Py_GetPath(): 37e.: get *note sys.path: 37f. instead.

        * *note Py_GetPrefix(): 380.: get *note sys.prefix: 381.
          instead.

        * *note Py_GetProgramFullPath(): 382.: get *note sys.executable:
          383. instead.

        * *note Py_GetProgramName(): 384.: get *note sys.executable:
          383. instead.

        * *note Py_GetPythonHome(): 385.: get *note PyConfig.home: 386.
          or the *note PYTHONHOME: 387. environment variable instead.


File: python.info,  Node: Pending Removal in Future Versions<2>,  Prev: Pending Removal in Python 3 15<2>,  Up: Deprecated C APIs

1.1.12.7 Pending Removal in Future Versions
...........................................

The following APIs are deprecated and will be removed, although there is
currently no date scheduled for their removal.

   * *note Py_TPFLAGS_HAVE_FINALIZE: 3ba.: unneeded since Python 3.8.

   * *note PyErr_Fetch(): 3bb.: use *note PyErr_GetRaisedException():
     3bc. instead.

   * *note PyErr_NormalizeException(): 3bd.: use *note
     PyErr_GetRaisedException(): 3bc. instead.

   * *note PyErr_Restore(): 3be.: use *note PyErr_SetRaisedException():
     3bf. instead.

   * *note PyModule_GetFilename(): 3c0.: use *note
     PyModule_GetFilenameObject(): 3c1. instead.

   * *note PyOS_AfterFork(): 3c2.: use *note PyOS_AfterFork_Child():
     3c3. instead.

   * *note PySlice_GetIndicesEx(): 3c4.: use *note PySlice_Unpack():
     3c5. and *note PySlice_AdjustIndices(): 3c6. instead.

   * ‘PyUnicode_AsDecodedObject()’: use *note PyCodec_Decode(): 3c7.
     instead.

   * ‘PyUnicode_AsDecodedUnicode()’: use *note PyCodec_Decode(): 3c7.
     instead.

   * ‘PyUnicode_AsEncodedObject()’: use *note PyCodec_Encode(): 3c8.
     instead.

   * ‘PyUnicode_AsEncodedUnicode()’: use *note PyCodec_Encode(): 3c8.
     instead.

   * *note PyUnicode_READY(): 3c9.: unneeded since Python 3.12

   * ‘PyErr_Display()’: use *note PyErr_DisplayException(): 3ca.
     instead.

   * ‘_PyErr_ChainExceptions()’: use ‘_PyErr_ChainExceptions1’ instead.

   * ‘PyBytesObject.ob_shash’ member: call *note PyObject_Hash(): 3cb.
     instead.

   * ‘PyDictObject.ma_version_tag’ member.

   * Thread Local Storage (TLS) API:

        * *note PyThread_create_key(): 3cc.: use *note
          PyThread_tss_alloc(): 3cd. instead.

        * *note PyThread_delete_key(): 3ce.: use *note
          PyThread_tss_free(): 3cf. instead.

        * *note PyThread_set_key_value(): 3d0.: use *note
          PyThread_tss_set(): 3d1. instead.

        * *note PyThread_get_key_value(): 3d2.: use *note
          PyThread_tss_get(): 3d3. instead.

        * *note PyThread_delete_key_value(): 3d4.: use *note
          PyThread_tss_delete(): 3d5. instead.

        * *note PyThread_ReInitTLS(): 3d6.: unneeded since Python 3.7.


File: python.info,  Node: Regression Test Changes,  Prev: Porting to Python 3 13,  Up: What's New In Python 3 13

1.1.13 Regression Test Changes
------------------------------

   * Python built with ‘configure’ *note -with-pydebug: 3d8. now
     supports a *note -X presite=package.module: 15a. command-line
     option.  If used, it specifies a module that should be imported
     early in the lifecycle of the interpreter, before ‘site.py’ is
     executed.  (Contributed by Łukasz Langa in gh-110769(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/110769


File: python.info,  Node: Python 3 12 有什麼新功能,  Next: Python 3 11 有什麼新功能,  Prev: What's New In Python 3 13,  Up: Python 有什麼新功能？

1.2 Python 3.12 有什麼新功能
============================


編輯者: Adam Turner

本文介紹了 Python 3.12 與 3.11 相比的新功能。 Python 3.12 於 2023 年 10
月 2 日發布。完整詳請請見 *note changelog: 122.。

也參考
......

PEP 693(1) - Python 3.12 發佈時程

* Menu:

* 發布重點摘要::
* 新增特性::
* New Features Related to Type Hints::
* 其他語言更動::
* 新增模組::
* 改進的模組::
* 最佳化::
* CPython 位元組碼變更::
* Demos and Tools::
* 已棄用::
* 已移除::
* Porting to Python 3.12: Porting to Python 3 12.
* 建置變更::
* C API 變更::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0693/


File: python.info,  Node: 發布重點摘要,  Next: 新增特性,  Up: Python 3 12 有什麼新功能

1.2.1 發布重點摘要
------------------

Python 3.12 is the latest stable release of the Python programming
language, with a mix of changes to the language and the standard
library.  The library changes focus on cleaning up deprecated APIs,
usability, and correctness.  Of note, the ‘distutils’ package has been
removed from the standard library.  Filesystem support in *note os: 91.
and *note pathlib: 93. has seen a number of improvements, and several
modules have better performance.

The language changes focus on usability, as *note f-strings: 3dc. have
had many limitations removed and 'Did you mean ...'  suggestions
continue to improve.  The new *note type parameter syntax: 3dd. and
*note type: 3de. statement improve ergonomics for using *note generic
types: 3df. and *note type aliases: 3e0. with static type checkers.

This article doesn't attempt to provide a complete specification of all
new features, but instead gives a convenient overview.  For full
details, you should refer to the documentation, such as the *note
Library Reference: 12a. and *note Language Reference: 12b.  If you want
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.

__________________________________________________________________

新增語法特性：

   * *note PEP 695: 3dd.，型別參數語法和 *note type: 3de. 陳述式

新增語法特性：

   * *note PEP 701: 3e1, *note f-strings: 3dc. in the grammar

直譯器改進：

   * *note PEP 684: 3e2, a unique per-interpreter *note GIL: 12e.

   * *note PEP 669: 3e3, low impact monitoring

   * *note Improved 'Did you mean ...'  suggestions: 3e4.for *note
     NameError: 3e5, *note ImportError: 352, and *note SyntaxError: 173.
     exceptions

Python 資料模型改進：

   * *note PEP 688: 3e6, using the *note buffer protocol: 367. from
     Python

Significant improvements in the standard library:

   * *note pathlib.Path: 20e. 類別現在支援子類別化

   * The *note os: 91. module received several improvements for Windows
     support

   * 一個*note 命令列介面: 3e7.已被加入 *note sqlite3: ba. 模組中

   * *note isinstance(): 3e8. checks against *note runtime-checkable
     protocols: 3e9. enjoy a speed up of between two and 20 times

   * *note asyncio: 8. 套件進行了許多效能改進，一些基準測試顯示速度提高
     了 75%。

   * 一個*note 命令列介面: 3ea.已被加入 *note uuid: f8. 模組中

   * Due to the changes in *note PEP 701: 3e1, producing tokens via the
     *note tokenize: e4. module is up to 64% faster.

安全性改進：

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

C API 改進：

   * *note PEP 697: 3eb.，不穩定 C API 層

   * *note PEP 683: 3ec, immortal objects

CPython 實作改進：

   * *note PEP 709: 3ed, comprehension inlining

   * *note CPython support: 175. for the Linux ‘perf’ profiler

   * Implement stack overflow protection on supported platforms

新增型別特性：

   * *note PEP 692: 3ee.、使用 *note TypedDict: 146. 來標註 *note
     **kwargs: 3ef.

   * *note PEP 698: 3f0.、*note typing.override(): 3f1. 裝飾器

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

   * PEP 623(2): Remove ‘wstr’ from Unicode objects in Python's C API,
     reducing the size of every *note str: 3f2. object by at least 8
     bytes.

   * PEP 632(3): Remove the ‘distutils’ package.  See the migration
     guide(4) for advice replacing the APIs it provided.  The
     third-party Setuptools(5) package continues to provide ‘distutils’,
     if you still require it in Python 3.12 and beyond.

   * gh-95299(6): Do not pre-install ‘setuptools’ in virtual
     environments created with *note venv: f9.  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 *note activated: 3f3. virtual environment.

   * ‘asynchat’、‘asyncore’ 和 ‘imp’ 模組以及幾個 *note
     unittest.TestCase: 3f4. 的*note 方法別名: 3f5.已被刪除。

   ---------- Footnotes ----------

   (1) https://github.com/hacl-star/hacl-star/

   (2) https://peps.python.org/pep-0623/

   (3) https://peps.python.org/pep-0632/

   (4) https://peps.python.org/pep-0632/#migration-advice

   (5) 
https://setuptools.pypa.io/en/latest/deprecated/distutils-legacy.html

   (6) https://github.com/python/cpython/issues/95299


File: python.info,  Node: 新增特性,  Next: New Features Related to Type Hints,  Prev: 發布重點摘要,  Up: Python 3 12 有什麼新功能

1.2.2 新增特性
--------------

* Menu:

* PEP 695：型別參數語法::
* PEP 701; Syntactic formalization of f-strings: PEP 701 Syntactic formalization of f-strings.
* PEP 684; A Per-Interpreter GIL: PEP 684 A Per-Interpreter GIL.
* PEP 669; Low impact monitoring for CPython: PEP 669 Low impact monitoring for CPython.
* PEP 688; Making the buffer protocol accessible in Python: PEP 688 Making the buffer protocol accessible in Python.
* PEP 709; Comprehension inlining: PEP 709 Comprehension inlining.
* Improved Error Messages::


File: python.info,  Node: PEP 695：型別參數語法,  Next: PEP 701 Syntactic formalization of f-strings,  Up: 新增特性

1.2.2.1 PEP 695：型別參數語法
.............................

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

PEP 695(2) introduces a new, more compact and explicit way to create
*note generic classes: 3f8. and *note functions: 3f9.:

     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 *note type aliases:
3fa. using the *note type: 3de. statement, which creates an instance of
*note TypeAliasType: 3fb.:

     type Point = tuple[float, float]

型別別名也可以是*note 泛型: 3fc.：

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

The new syntax allows declaring *note TypeVarTuple: 143. and *note
ParamSpec: 142. parameters, as well as *note TypeVar: 141. 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 with bound
     type IntOrStrSequence[T: (int, str)] = Sequence[T]  # TypeVar with constraints

The value of type aliases and the bound and constraints of type
variables created through this syntax are evaluated only on demand (see
*note lazy evaluation: 3fd.).  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
*note Type parameter lists: 294. 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 *note annotation scope: 16e.  Annotation scopes behave
for the most part like function scopes, but interact differently with
enclosing class scopes.  In Python 3.13, *note annotations: 3fe. will
also be evaluated in annotation scopes.

詳情請見 PEP 695(3)。

(PEP written by Eric Traut.  Implementation by Jelle Zijlstra, Eric
Traut, and others in gh-103764(4).)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0484/

   (2) https://peps.python.org/pep-0695/

   (3) https://peps.python.org/pep-0695/

   (4) https://github.com/python/cpython/issues/103764


File: python.info,  Node: PEP 701 Syntactic formalization of f-strings,  Next: PEP 684 A Per-Interpreter GIL,  Prev: PEP 695：型別參數語法,  Up: 新增特性

1.2.2.2 PEP 701: Syntactic formalization of f-strings
.....................................................

PEP 701(1) lifts some restrictions on the usage of *note f-strings: 3dc.
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 *note SyntaxError: 173, 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 *note escape sequences: 400. (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(2)。

As a positive side-effect of how this feature has been implemented (by
parsing f-strings with the PEG parser(3)), 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 *note
SyntaxError: 173.:

     >>> 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(4).  PEP written
by Pablo Galindo, Batuhan Taskaya, Lysandros Nikolaou and Marta Gómez).

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0701/

   (2) https://peps.python.org/pep-0701/

   (3) https://peps.python.org/pep-0617/

   (4) https://github.com/python/cpython/issues/102856


File: python.info,  Node: PEP 684 A Per-Interpreter GIL,  Next: PEP 669 Low impact monitoring for CPython,  Prev: PEP 701 Syntactic formalization of f-strings,  Up: 新增特性

1.2.2.3 PEP 684: A Per-Interpreter GIL
......................................

PEP 684(1) introduces a per-interpreter *note GIL: 12e, so that
sub-interpreters may now be created with a unique GIL per interpreter.
This allows Python programs to take full advantage of multiple CPU
cores.  This is currently only available through the C-API, though a
Python API is anticipated for 3.13(2).

Use the new *note Py_NewInterpreterFromConfig(): 402. 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;
     }
     /* The new interpreter is now active in the current thread. */

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

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

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0684/

   (2) https://peps.python.org/pep-0554/

   (3) 
https://github.com/python/cpython/tree/3.13/Modules/_xxsubinterpretersmodule.c

   (4) https://github.com/python/cpython/issues/104210


File: python.info,  Node: PEP 669 Low impact monitoring for CPython,  Next: PEP 688 Making the buffer protocol accessible in Python,  Prev: PEP 684 A Per-Interpreter GIL,  Up: 新增特性

1.2.2.4 PEP 669: Low impact monitoring for CPython
..................................................

PEP 669(1) defines a new *note API: c4. 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 *note
sys.monitoring: c4. for details.

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

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0669/

   (2) https://github.com/python/cpython/issues/103082


File: python.info,  Node: PEP 688 Making the buffer protocol accessible in Python,  Next: PEP 709 Comprehension inlining,  Prev: PEP 669 Low impact monitoring for CPython,  Up: 新增特性

1.2.2.5 PEP 688: Making the buffer protocol accessible in Python
................................................................

PEP 688(1) introduces a way to use the *note buffer protocol: 367. from
Python code.  Classes that implement the *note __buffer__(): 405. method
are now usable as buffer types.

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

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0688/

   (2) https://github.com/python/cpython/issues/102500


File: python.info,  Node: PEP 709 Comprehension inlining,  Next: Improved Error Messages,  Prev: PEP 688 Making the buffer protocol accessible in Python,  Up: 新增特性

1.2.2.6 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(1) 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 *note symtable: c2. 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 *note locals(): 127. 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(2) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0709/

   (2) https://peps.python.org/pep-0709/


File: python.info,  Node: Improved Error Messages,  Prev: PEP 709 Comprehension inlining,  Up: 新增特性

1.2.2.7 Improved Error Messages
...............................

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

          >>> 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 *note NameError: 3e5. exceptions
     for instances.  Now if a *note NameError: 3e5. 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(2).)

          >>> 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 *note SyntaxError: 173. error message when the user
     types ‘import x from y’ instead of ‘from y import x’.  (Contributed
     by Pablo Galindo in gh-98931(3).)

          >>> 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?

   * *note ImportError: 352. 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(4).)

          >>> 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'?

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/98254

   (2) https://github.com/python/cpython/issues/99139

   (3) https://github.com/python/cpython/issues/98931

   (4) https://github.com/python/cpython/issues/91058


File: python.info,  Node: New Features Related to Type Hints,  Next: 其他語言更動,  Prev: 新增特性,  Up: Python 3 12 有什麼新功能

1.2.3 New Features Related to Type Hints
----------------------------------------

This section covers major changes affecting type hints(1) and the *note
typing: ed. module.

* Menu:

* PEP 692; Using TypedDict for more precise **kwargs typing: PEP 692 Using TypedDict for more precise **kwargs typing.
* PEP 698; Override Decorator for Static Typing: PEP 698 Override Decorator for Static Typing.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0484/


File: python.info,  Node: PEP 692 Using TypedDict for more precise **kwargs typing,  Next: PEP 698 Override Decorator for Static Typing,  Up: New Features Related to Type Hints

1.2.3.1 PEP 692: Using ‘TypedDict’ for more precise ‘**kwargs’ typing
.....................................................................

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

PEP 692(2) 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(3)。

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

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0484/

   (2) https://peps.python.org/pep-0692/

   (3) https://peps.python.org/pep-0692/

   (4) https://github.com/python/cpython/issues/103629


File: python.info,  Node: PEP 698 Override Decorator for Static Typing,  Prev: PEP 692 Using TypedDict for more precise **kwargs typing,  Up: New Features Related to Type Hints

1.2.3.2 PEP 698: Override Decorator for Static Typing
.....................................................

A new decorator *note typing.override(): 3f1. has been added to the
*note typing: ed. 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(1)。

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

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0698/

   (2) https://github.com/python/cpython/issues/101561


File: python.info,  Node: 其他語言更動,  Next: 新增模組,  Prev: New Features Related to Type Hints,  Up: Python 3 12 有什麼新功能

1.2.4 其他語言更動
------------------

   * The parser now raises *note SyntaxError: 173. when parsing source
     code containing null bytes.  (Contributed by Pablo Galindo in
     gh-96670(1).)

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

   * Octal escapes with value larger than ‘0o377’ (ex: ‘"\477"’),
     deprecated in Python 3.11, now produce a *note SyntaxWarning: 40c,
     instead of *note DeprecationWarning: 18b.  In a future Python
     version they will be eventually a *note SyntaxError: 173.
     (Contributed by Victor Stinner in gh-98401(3).)

   * 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(4).  (Contributed by Nikita Sobolev in
     gh-100581(5).)

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

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

   * 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 *note PyErr_CheckSignals():
     40d. 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(9).)

   * All builtin and extension callables expecting boolean parameters
     now accept arguments of any type instead of just *note bool: 40e.
     and *note int: 23c.  (Contributed by Serhiy Storchaka in
     gh-60203(10).)

   * *note memoryview: 40f. now supports the half-float type (the "e"
     format code).  (Contributed by Donghee Na and Antoine Pitrou in
     gh-90751(11).)

   * *note slice: 410. 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(12).)

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

   * *note ast.parse(): 18e. now raises *note SyntaxError: 173. instead
     of *note ValueError: 1e7. when parsing source code containing null
     bytes.  (Contributed by Pablo Galindo in gh-96670(14).)

   * The extraction methods in *note tarfile: c8, and *note
     shutil.unpack_archive(): 412, 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
     *note tarfile extraction filters: 413. for details.  In Python
     3.14, the default will switch to ‘'data'’.  (Contributed by Petr
     Viktorin in PEP 706(15).)

   * *note types.MappingProxyType: 414. instances are now hashable if
     the underlying mapping is hashable.  (Contributed by Serhiy
     Storchaka in gh-87995(16).)

   * Add *note support for the perf profiler: 175. through the new
     environment variable *note PYTHONPERFSUPPORT: 415. and command-line
     option *note -X perf: 15a, as well as the new *note
     sys.activate_stack_trampoline(): 416, *note
     sys.deactivate_stack_trampoline(): 417, and *note
     sys.is_stack_trampoline_active(): 418. functions.  (Design by Pablo
     Galindo.  Contributed by Pablo Galindo and Christian Heimes with
     contributions from Gregory P. Smith [Google] and Mark Shannon in
     gh-96123(17).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/96670

   (2) https://github.com/python/cpython/issues/98401

   (3) https://github.com/python/cpython/issues/98401

   (4) https://peps.python.org/pep-0572/

   (5) https://github.com/python/cpython/issues/100581

   (6) https://peps.python.org/pep-0678/

   (7) https://github.com/python/cpython/issues/77757

   (8) https://github.com/python/cpython/issues/103590

   (9) https://github.com/python/cpython/issues/97922

   (10) https://github.com/python/cpython/issues/60203

   (11) https://github.com/python/cpython/issues/90751

   (12) https://github.com/python/cpython/issues/101264

   (13) https://github.com/python/cpython/issues/100425

   (14) https://github.com/python/cpython/issues/96670

   (15) https://peps.python.org/pep-0706/

   (16) https://github.com/python/cpython/issues/87995

   (17) https://github.com/python/cpython/issues/96123


File: python.info,  Node: 新增模組,  Next: 改進的模組,  Prev: 其他語言更動,  Up: Python 3 12 有什麼新功能

1.2.5 新增模組
--------------

   * None.


File: python.info,  Node: 改進的模組,  Next: 最佳化,  Prev: 新增模組,  Up: Python 3 12 有什麼新功能

1.2.6 改進的模組
----------------

* Menu:

* array: array<2>.
* asyncio: asyncio<2>.
* calendar::
* csv::
* dis: dis<2>.
* fractions: fractions<2>.
* importlib.resources: importlib resources.
* inspect::
* itertools: itertools<2>.
* math: math<2>.
* os: os<2>.
* os.path: os path<2>.
* pathlib: pathlib<3>.
* pdb: pdb<2>.
* random: random<2>.
* shutil: shutil<2>.
* sqlite3: sqlite3<2>.
* statistics: statistics<2>.
* sys: sys<2>.
* tempfile: tempfile<2>.
* threading::
* tkinter: tkinter<2>.
* tokenize::
* types: types<2>.
* typing: typing<3>.
* unicodedata: unicodedata<2>.
* unittest: unittest<2>.
* uuid::


File: python.info,  Node: array<2>,  Next: asyncio<2>,  Up: 改進的模組

1.2.6.1 array
.............

   * The *note array.array: 186. class now supports subscripting, making
     it a *note generic type: 3df.  (Contributed by Jelle Zijlstra in
     gh-98658(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/98658


File: python.info,  Node: asyncio<2>,  Next: calendar,  Prev: array<2>,  Up: 改進的模組

1.2.6.2 asyncio
...............

   * The performance of writing to sockets in *note asyncio: 8. has been
     significantly improved.  ‘asyncio’ now avoids unnecessary copying
     when writing to sockets and uses *note sendmsg(): 41d. if the
     platform supports it.  (Contributed by Kumar Aditya in
     gh-91166(1).)

   * Add *note asyncio.eager_task_factory(): 41e. and *note
     asyncio.create_eager_task_factory(): 41f. 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(2), gh-104140(3), and gh-104138(4))

   * On Linux, *note asyncio: 8. uses *note asyncio.PidfdChildWatcher:
     420. by default if *note os.pidfd_open(): 421. is available and
     functional instead of *note asyncio.ThreadedChildWatcher: 422.
     (Contributed by Kumar Aditya in gh-98024(5).)

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

   * Add 'loop_factory' parameter to *note asyncio.run(): 423. to allow
     specifying a custom event loop factory.  (Contributed by Kumar
     Aditya in gh-99388(7).)

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

   * *note asyncio.iscoroutine(): 425. now returns ‘False’ for
     generators as *note asyncio: 8. does not support legacy
     generator-based coroutines.  (Contributed by Kumar Aditya in
     gh-102748(9).)

   * *note asyncio.wait(): 426. and *note asyncio.as_completed(): 190.
     now accepts generators yielding tasks.  (Contributed by Kumar
     Aditya in gh-78530(10).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/91166

   (2) https://github.com/python/cpython/issues/102853

   (3) https://github.com/python/cpython/issues/104140

   (4) https://github.com/python/cpython/issues/104138

   (5) https://github.com/python/cpython/issues/98024

   (6) https://github.com/python/cpython/issues/94597

   (7) https://github.com/python/cpython/issues/99388

   (8) https://github.com/python/cpython/issues/100344

   (9) https://github.com/python/cpython/issues/102748

   (10) https://github.com/python/cpython/issues/78530


File: python.info,  Node: calendar,  Next: csv,  Prev: asyncio<2>,  Up: 改進的模組

1.2.6.3 calendar
................

   * Add enums *note calendar.Month: 428. and *note calendar.Day: 429.
     defining months of the year and days of the week.  (Contributed by
     Prince Roshan in gh-103636(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/103636


File: python.info,  Node: csv,  Next: dis<2>,  Prev: calendar,  Up: 改進的模組

1.2.6.4 csv
...........

   * Add *note csv.QUOTE_NOTNULL: 42b. and *note csv.QUOTE_STRINGS: 42c.
     flags to provide finer grained control of ‘None’ and empty strings
     by *note reader: 42d. and *note writer: 42e. objects.


File: python.info,  Node: dis<2>,  Next: fractions<2>,  Prev: csv,  Up: 改進的模組

1.2.6.5 dis
...........

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

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

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/94216

   (2) https://github.com/python/cpython/issues/94216


File: python.info,  Node: fractions<2>,  Next: importlib resources,  Prev: dis<2>,  Up: 改進的模組

1.2.6.6 fractions
.................

   * Objects of type *note fractions.Fraction: 1c7. now support
     float-style formatting.  (Contributed by Mark Dickinson in
     gh-100161(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/100161


File: python.info,  Node: importlib resources,  Next: inspect,  Prev: fractions<2>,  Up: 改進的模組

1.2.6.7 importlib.resources
...........................

   * *note importlib.resources.as_file(): 434. now supports resource
     directories.  (Contributed by Jason R. Coombs in gh-97930(1).)

   * Rename first parameter of *note importlib.resources.files(): 435.
     to 'anchor'.  (Contributed by Jason R. Coombs in gh-100598(2).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/97930

   (2) https://github.com/python/cpython/issues/100598


File: python.info,  Node: inspect,  Next: itertools<2>,  Prev: importlib resources,  Up: 改進的模組

1.2.6.8 inspect
...............

   * Add *note inspect.markcoroutinefunction(): 437. to mark sync
     functions that return a *note coroutine: 438. for use with *note
     inspect.iscoroutinefunction(): 439.  (Contributed by Carlton Gibson
     in gh-99247(1).)

   * Add *note inspect.getasyncgenstate(): 43a. and *note
     inspect.getasyncgenlocals(): 43b. for determining the current state
     of asynchronous generators.  (Contributed by Thomas Krennwallner in
     gh-79940(2).)

   * The performance of *note inspect.getattr_static(): 43c. has been
     considerably improved.  Most calls to the function should be at
     least 2x faster than they were in Python 3.11.  (Contributed by
     Alex Waygood in gh-103193(3).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/99247

   (2) https://github.com/python/cpython/issues/79940

   (3) https://github.com/python/cpython/issues/103193


File: python.info,  Node: itertools<2>,  Next: math<2>,  Prev: inspect,  Up: 改進的模組

1.2.6.9 itertools
.................

   * Add *note itertools.batched(): 1e6. for collecting into even-sized
     tuples where the last batch may be shorter than the rest.
     (Contributed by Raymond Hettinger in gh-98363(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/98363


File: python.info,  Node: math<2>,  Next: os<2>,  Prev: itertools<2>,  Up: 改進的模組

1.2.6.10 math
.............

   * 新增 *note math.sumprod(): 43f. 以計算乘積總和。（由 Raymond
     Hettinger 於 gh-100485(1) 中貢獻。）

   * Extend *note math.nextafter(): 440. 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(2).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/100485

   (2) https://github.com/python/cpython/issues/94906


File: python.info,  Node: os<2>,  Next: os path<2>,  Prev: math<2>,  Up: 改進的模組

1.2.6.11 os
...........

   * Add *note os.PIDFD_NONBLOCK: 442. to open a file descriptor for a
     process with *note os.pidfd_open(): 421. in non-blocking mode.
     (Contributed by Kumar Aditya in gh-93312(1).)

   * *note os.DirEntry: 443. now includes an *note
     os.DirEntry.is_junction(): 444. method to check if the entry is a
     junction.  (Contributed by Charles Machalow in gh-99547(2).)

   * Add *note os.listdrives(): 445, *note os.listvolumes(): 446. and
     *note os.listmounts(): 447. functions on Windows for enumerating
     drives, volumes and mount points.  (Contributed by Steve Dower in
     gh-102519(3).)

   * *note os.stat(): 448. and *note os.lstat(): 449. 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(4).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/93312

   (2) https://github.com/python/cpython/issues/99547

   (3) https://github.com/python/cpython/issues/102519

   (4) https://github.com/python/cpython/issues/99726


File: python.info,  Node: os path<2>,  Next: pathlib<3>,  Prev: os<2>,  Up: 改進的模組

1.2.6.12 os.path
................

   * Add *note os.path.isjunction(): 44b. to check if a given path is a
     junction.  (Contributed by Charles Machalow in gh-99547(1).)

   * Add *note os.path.splitroot(): 44c. to split a path into a triad
     ‘(drive, root, tail)’.  (Contributed by Barney Gale in
     gh-101000(2).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/99547

   (2) https://github.com/python/cpython/issues/101000


File: python.info,  Node: pathlib<3>,  Next: pdb<2>,  Prev: os path<2>,  Up: 改進的模組

1.2.6.13 pathlib
................

   * Add support for subclassing *note pathlib.PurePath: 44e. and *note
     pathlib.Path: 20e, plus their Posix- and Windows-specific variants.
     Subclasses may override the *note pathlib.PurePath.with_segments():
     44f. method to pass information between path instances.

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

   * Add 'walk_up' optional parameter to *note
     pathlib.PurePath.relative_to(): 2ac. to allow the insertion of ‘..’
     entries in the result; this behavior is more consistent with *note
     os.path.relpath(): 452.  (Contributed by Domenico Ragusa in
     gh-84538(2).)

   * Add *note pathlib.Path.is_junction(): 453. as a proxy to *note
     os.path.isjunction(): 44b.  (Contributed by Charles Machalow in
     gh-99547(3).)

   * Add 'case_sensitive' optional parameter to *note
     pathlib.Path.glob(): 212, *note pathlib.Path.rglob(): 213. and
     *note pathlib.PurePath.match(): 454. for matching the path's case
     sensitivity, allowing for more precise control over the matching
     process.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/90385

   (2) https://github.com/python/cpython/issues/84538

   (3) https://github.com/python/cpython/issues/99547


File: python.info,  Node: pdb<2>,  Next: random<2>,  Prev: pathlib<3>,  Up: 改進的模組

1.2.6.14 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(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/103693


File: python.info,  Node: random<2>,  Next: shutil<2>,  Prev: pdb<2>,  Up: 改進的模組

1.2.6.15 random
...............

   * 新增 *note random.binomialvariate(): 457.。（由 Raymond Hettinger 於
     gh-81620(1) 中貢獻。）

   * 將預設值 ‘lambd=1.0’ 加入至 *note random.expovariate(): 458. 中。（
     由 Raymond Hettinger 在 gh-100234(2) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/81620

   (2) https://github.com/python/cpython/issues/100234


File: python.info,  Node: shutil<2>,  Next: sqlite3<2>,  Prev: random<2>,  Up: 改進的模組

1.2.6.16 shutil
...............

   * *note shutil.make_archive(): 45a. 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(1).)

   * *note shutil.rmtree(): 2d2. 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(2).)

   * *note shutil.which(): 45b. 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(3).)

     *note shutil.which(): 45b. 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(4).)

     *note shutil.which(): 45b. 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(5).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/74696

   (2) https://github.com/python/cpython/issues/102828

   (3) https://github.com/python/cpython/issues/103179

   (4) https://github.com/python/cpython/issues/103179

   (5) https://github.com/python/cpython/issues/103179


File: python.info,  Node: sqlite3<2>,  Next: statistics<2>,  Prev: shutil<2>,  Up: 改進的模組

1.2.6.17 sqlite3
................

   * 新增*note 命令列介面: 3e7.。（由 Erlend E. Aasland 於 gh-77617(1) 中
     貢獻。）

   * Add the *note sqlite3.Connection.autocommit: 45d. attribute to
     *note sqlite3.Connection: 22a. and the 'autocommit' parameter to
     *note sqlite3.connect(): 288. to control PEP 249(2)-compliant *note
     transaction handling: 45e.  (Contributed by Erlend E. Aasland in
     gh-83638(3).)

   * Add 'entrypoint' keyword-only parameter to *note
     sqlite3.Connection.load_extension(): 45f, for overriding the SQLite
     extension entry point.  (Contributed by Erlend E. Aasland in
     gh-103015(4).)

   * Add *note sqlite3.Connection.getconfig(): 460. and *note
     sqlite3.Connection.setconfig(): 461. to *note sqlite3.Connection:
     22a. to make configuration changes to a database connection.
     (Contributed by Erlend E. Aasland in gh-103489(5).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/77617

   (2) https://peps.python.org/pep-0249/

   (3) https://github.com/python/cpython/issues/83638

   (4) https://github.com/python/cpython/issues/103015

   (5) https://github.com/python/cpython/issues/103489


File: python.info,  Node: statistics<2>,  Next: sys<2>,  Prev: sqlite3<2>,  Up: 改進的模組

1.2.6.18 statistics
...................

   * Extend *note statistics.correlation(): 463. to include as a
     ‘ranked’ method for computing the Spearman correlation of ranked
     data.  (Contributed by Raymond Hettinger in gh-95861(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/95861


File: python.info,  Node: sys<2>,  Next: tempfile<2>,  Prev: statistics<2>,  Up: 改進的模組

1.2.6.19 sys
............

   * Add the *note sys.monitoring: c4. namespace to expose the new *note
     PEP 669: 3e3. monitoring API. (Contributed by Mark Shannon in
     gh-103082(1).)

   * Add *note sys.activate_stack_trampoline(): 416. and *note
     sys.deactivate_stack_trampoline(): 417. for activating and
     deactivating stack profiler trampolines, and *note
     sys.is_stack_trampoline_active(): 418. 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(2).)

   * Add *note sys.last_exc: 465. 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: *note sys.last_type: 466, *note sys.last_value: 467.
     and *note sys.last_traceback: 468.  (Contributed by Irit Katriel in
     gh-102778(3).)

   * *note sys._current_exceptions(): 469. 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(4).)

   * *note sys.setrecursionlimit(): 46a. and *note
     sys.getrecursionlimit(): 46b.  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.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/103082

   (2) https://github.com/python/cpython/issues/96123

   (3) https://github.com/python/cpython/issues/102778

   (4) https://github.com/python/cpython/issues/103176


File: python.info,  Node: tempfile<2>,  Next: threading,  Prev: sys<2>,  Up: 改進的模組

1.2.6.20 tempfile
.................

   * *note tempfile.NamedTemporaryFile: 46d. 函式新增了一個選擇性參數
     'delete_on_close' （由 Evgeny Zorin 於 gh-58451(1) 中貢獻。）

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

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/58451


File: python.info,  Node: threading,  Next: tkinter<2>,  Prev: tempfile<2>,  Up: 改進的模組

1.2.6.21 threading
..................

   * Add *note threading.settrace_all_threads(): 46f. and *note
     threading.setprofile_all_threads(): 470. 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(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/93503


File: python.info,  Node: tkinter<2>,  Next: tokenize,  Prev: threading,  Up: 改進的模組

1.2.6.22 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(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/94473


File: python.info,  Node: tokenize,  Next: types<2>,  Prev: tkinter<2>,  Up: 改進的模組

1.2.6.23 tokenize
.................

   * The *note tokenize: e4. module includes the changes introduced in
     PEP 701(1).  (Contributed by Marta Gómez Macías and Pablo Galindo
     in gh-102856(2).)  See *note Porting to Python 3.12: 473. for more
     information on the changes to the *note tokenize: e4. module.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0701/

   (2) https://github.com/python/cpython/issues/102856


File: python.info,  Node: types<2>,  Next: typing<3>,  Prev: tokenize,  Up: 改進的模組

1.2.6.24 types
..............

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

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/101827


File: python.info,  Node: typing<3>,  Next: unicodedata<2>,  Prev: types<2>,  Up: 改進的模組

1.2.6.25 typing
...............

   * *note isinstance(): 3e8. checks against *note runtime-checkable
     protocols: 3e9. now use *note inspect.getattr_static(): 43c. rather
     than *note hasattr(): 479. to lookup whether attributes exist.
     This means that descriptors and *note __getattr__(): 47a. 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(1).)

   * 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 *note isinstance(): 3e8.
     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)  # unchanged, even though HasX now also has a "y" attribute
          True

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

   * The performance profile of *note isinstance(): 3e8. checks against
     *note runtime-checkable protocols: 3e9. 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(2) and gh-103193(3).)

   * All *note typing.TypedDict: 146. and *note typing.NamedTuple: 291.
     classes now have the ‘__orig_bases__’ attribute.  (Contributed by
     Adrian Garcia Badaracco in gh-103699(4).)

   * 新增 ‘frozen_default’ 參數至 *note typing.dataclass_transform():
     47b.。（由 Erik De Bonte 於 gh-99957(5) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/102433

   (2) https://github.com/python/cpython/issues/74690

   (3) https://github.com/python/cpython/issues/103193

   (4) https://github.com/python/cpython/issues/103699

   (5) https://github.com/python/cpython/issues/99957


File: python.info,  Node: unicodedata<2>,  Next: unittest<2>,  Prev: typing<3>,  Up: 改進的模組

1.2.6.26 unicodedata
....................

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

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/96734


File: python.info,  Node: unittest<2>,  Next: uuid,  Prev: unicodedata<2>,  Up: 改進的模組

1.2.6.27 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(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/48330


File: python.info,  Node: uuid,  Prev: unittest<2>,  Up: 改進的模組

1.2.6.28 uuid
.............

   * 新增一個*note 命令列介面: 3ea.。（由 Adam Chhina 於 gh-88597(1) 中
     貢獻。）

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/88597


File: python.info,  Node: 最佳化,  Next: CPython 位元組碼變更,  Prev: 改進的模組,  Up: Python 3 12 有什麼新功能

1.2.7 最佳化
------------

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

   * 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(3) and tuned by Donghee Na in
     gh-101525(4))

   * Speed up the regular expression substitution (functions *note
     re.sub(): 283. and *note re.subn(): 284. and corresponding
     ‘re.Pattern’ methods) for replacement strings containing group
     references by 2-3 times.  (Contributed by Serhiy Storchaka in
     gh-91524(5).)

   * Speed up *note asyncio.Task: 480. creation by deferring expensive
     string formatting.  (Contributed by Itamar Oren in gh-103793(6).)

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

   * Speed up *note super(): 483. method calls and attribute loads via
     the new *note LOAD_SUPER_ATTR: 484. instruction.  (Contributed by
     Carl Meyer and Vladimir Matveev in gh-103497(9).)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0623/

   (2) https://github.com/python/cpython/issues/92536

   (3) https://github.com/python/cpython/issues/90536

   (4) https://github.com/python/cpython/issues/101525

   (5) https://github.com/python/cpython/issues/91524

   (6) https://github.com/python/cpython/issues/103793

   (7) https://peps.python.org/pep-0701/

   (8) https://github.com/python/cpython/issues/102856

   (9) https://github.com/python/cpython/issues/103497


File: python.info,  Node: CPython 位元組碼變更,  Next: Demos and Tools,  Prev: 最佳化,  Up: Python 3 12 有什麼新功能

1.2.8 CPython 位元組碼變更
--------------------------

   * Remove the ‘LOAD_METHOD’ instruction.  It has been merged into
     *note LOAD_ATTR: 486.  *note LOAD_ATTR: 486. will now behave like
     the old ‘LOAD_METHOD’ instruction if the low bit of its oparg is
     set.  (Contributed by Ken Jin in gh-93429(1).)

   * Remove the ‘JUMP_IF_FALSE_OR_POP’ and ‘JUMP_IF_TRUE_OR_POP’
     instructions.  (Contributed by Irit Katriel in gh-102859(2).)

   * Remove the ‘PRECALL’ instruction.  (Contributed by Mark Shannon in
     gh-92925(3).)

   * Add the *note BINARY_SLICE: 487. and *note STORE_SLICE: 488.
     instructions.  (Contributed by Mark Shannon in gh-94163(4).)

   * Add the *note CALL_INTRINSIC_1: 489. instructions.  (Contributed by
     Mark Shannon in gh-99005(5).)

   * Add the *note CALL_INTRINSIC_2: 48a. instruction.  (Contributed by
     Irit Katriel in gh-101799(6).)

   * Add the *note CLEANUP_THROW: 48b. instruction.  (Contributed by
     Brandt Bucher in gh-90997(7).)

   * Add the ‘END_SEND’ instruction.  (Contributed by Mark Shannon in
     gh-103082(8).)

   * Add the *note LOAD_FAST_AND_CLEAR: 48c. instruction as part of the
     implementation of PEP 709(9).  (Contributed by Carl Meyer in
     gh-101441(10).)

   * Add the *note LOAD_FAST_CHECK: 48d. instruction.  (Contributed by
     Dennis Sweeney in gh-93143(11).)

   * Add the *note LOAD_FROM_DICT_OR_DEREF: 48e, *note
     LOAD_FROM_DICT_OR_GLOBALS: 48f, and *note LOAD_LOCALS: 490. opcodes
     as part of the implementation of PEP 695(12).  Remove the
     ‘LOAD_CLASSDEREF’ opcode, which can be replaced with *note
     LOAD_LOCALS: 490. plus *note LOAD_FROM_DICT_OR_DEREF: 48e.
     (Contributed by Jelle Zijlstra in gh-103764(13).)

   * Add the *note LOAD_SUPER_ATTR: 484. instruction.  (Contributed by
     Carl Meyer and Vladimir Matveev in gh-103497(14).)

   * Add the *note RETURN_CONST: 491. instruction.  (Contributed by
     Wenyang Wang in gh-101632(15).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/93429

   (2) https://github.com/python/cpython/issues/102859

   (3) https://github.com/python/cpython/issues/92925

   (4) https://github.com/python/cpython/issues/94163

   (5) https://github.com/python/cpython/issues/99005

   (6) https://github.com/python/cpython/issues/101799

   (7) https://github.com/python/cpython/issues/90997

   (8) https://github.com/python/cpython/issues/103082

   (9) https://peps.python.org/pep-0709/

   (10) https://github.com/python/cpython/issues/101441

   (11) https://github.com/python/cpython/issues/93143

   (12) https://peps.python.org/pep-0695/

   (13) https://github.com/python/cpython/issues/103764

   (14) https://github.com/python/cpython/issues/103497

   (15) https://github.com/python/cpython/issues/101632


File: python.info,  Node: Demos and Tools,  Next: 已棄用,  Prev: CPython 位元組碼變更,  Up: Python 3 12 有什麼新功能

1.2.9 Demos and Tools
---------------------

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

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

   ---------- Footnotes ----------

   (1) https://github.com/gvanrossum/old-demos

   (2) https://github.com/python/cpython/issues/97681

   (3) https://github.com/gvanrossum/old-demos

   (4) https://github.com/python/cpython/issues/97669


File: python.info,  Node: 已棄用,  Next: 已移除,  Prev: Demos and Tools,  Up: Python 3 12 有什麼新功能

1.2.10 已棄用
-------------

   * *note argparse: 5.：‘argparse.BooleanOptionalAction’ 的 'type'、
     'choices' 和 'metavar' 參數已被棄用，將在 3.14 中移除。 (由 Nikita
     Sobolev 於 gh-92248(1) 貢獻。)

   * *note ast: 7.: The following *note ast: 7. features have been
     deprecated in documentation since Python 3.8, now cause a *note
     DeprecationWarning: 18b. to be emitted at runtime when they are
     accessed or used, and will be removed in Python 3.14:

        * ‘ast.Num’

        * ‘ast.Str’

        * ‘ast.Bytes’

        * ‘ast.NameConstant’

        * ‘ast.Ellipsis’

     請改用 *note ast.Constant: 29a.。（由 Serhiy Storchaka 於
     gh-90953(2) 貢獻。）

   * *note asyncio: 8.：

        * The child watcher classes *note asyncio.MultiLoopChildWatcher:
          29b, *note asyncio.FastChildWatcher: 29c, *note
          asyncio.AbstractChildWatcher: 29d. and *note
          asyncio.SafeChildWatcher: 29e. are deprecated and will be
          removed in Python 3.14.  (Contributed by Kumar Aditya in
          gh-94597(3).)

        * *note asyncio.set_child_watcher(): 29f.、*note
          asyncio.get_child_watcher(): 2a0.、*note
          asyncio.AbstractEventLoopPolicy.set_child_watcher(): 2a1. 和
          *note asyncio.AbstractEventLoopPolicy.get_child_watcher():
          2a2. 已被棄用並將在 Python 3.14 中移除。（由 Kumar Aditya 於
          gh-94597(4) 貢獻。）

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

   * *note calendar: 10.：‘calendar.January’ 和 ‘calendar.February’ 常數
     已被棄用並被 *note calendar.JANUARY: 2ca. 和 *note
     calendar.FEBRUARY: 2cb. 取代。 (由 Prince Roshan 於 gh-103636(6) 貢
     獻。)

   * *note collections.abc: 17.: Deprecated *note
     collections.abc.ByteString: 2a4.  Prefer ‘Sequence’ or *note
     collections.abc.Buffer: 2a5.  For use in typing, prefer a union,
     like ‘bytes | bytearray’, or *note collections.abc.Buffer: 2a5.
     (Contributed by Shantanu Jain in gh-91896(7).)

   * *note datetime: 28.: *note datetime.datetime: 1b0.'s *note
     utcnow(): 2cd. and *note utcfromtimestamp(): 2ce. are deprecated
     and will be removed in a future version.  Instead, use
     timezone-aware objects to represent datetimes in UTC: respectively,
     call *note now(): 494. and *note fromtimestamp(): 495. with the
     'tz' parameter set to *note datetime.UTC: 496.  (Contributed by
     Paul Ganssle in gh-103857(8).)

   * *note email: 32.：棄用 *note email.utils.localtime(): 2a6. 中的
     'isdst' 參數。（由 Alan Williams 於 gh-72346(9) 中貢獻。）

   * *note importlib.abc: 6c.：棄用下列類別，預定於 Python 3.14 中移除：

        * ‘importlib.abc.ResourceReader’

        * ‘importlib.abc.Traversable’

        * ‘importlib.abc.TraversableResources’

     請改用 *note importlib.resources.abc: 70. 類別：

        * *note importlib.resources.abc.Traversable: 1d8.

        * *note importlib.resources.abc.TraversableResources: 2a7.

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

   * *note itertools: 75.: 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(11).)

   * *note multiprocessing: 86.: In Python 3.14, the default *note
     multiprocessing: 86. 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(12)).  Adding a runtime warning
     about this was deemed too disruptive as the majority of code is not
     expected to care.  Use the *note get_context(): 2a8. or *note
     set_start_method(): 2a9. APIs to explicitly specify when your code
     'requires' ‘'fork'’.  See *note contexts and start methods: 2aa.

   * *note pkgutil: 97.: *note pkgutil.find_loader(): 2ad. and *note
     pkgutil.get_loader(): 2ae. are deprecated and will be removed in
     Python 3.14; use *note importlib.util.find_spec(): 2af. instead.
     (Contributed by Nikita Sobolev in gh-97850(13).)

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

   * *note os: 91.：

        * The ‘st_ctime’ fields return by *note os.stat(): 448. and
          *note os.lstat(): 449. 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(15).)

        * On POSIX platforms, *note os.fork(): 17b. can now raise a
          *note DeprecationWarning: 18b. 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 *note os.fork():
          17b. documentation for more details along with this discussion
          on fork being incompatible with threads(16) for 'why' we're
          now surfacing this longstanding platform compatibility problem
          to developers.

     When this warning appears due to usage of *note multiprocessing:
     86. or *note concurrent.futures: 1a. the fix is to use a different
     *note multiprocessing: 86. start method such as ‘"spawn"’ or
     ‘"forkserver"’.

   * *note shutil: b3.：*note shutil.rmtree(): 2d2. 的 'onerror' 引數已
     被棄用，請改用 'onexc'。（由 Irit Katriel 於 gh-102828(17) 中貢獻。
     ）

   * *note sqlite3: ba.：

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

        * In *note execute(): 2b3, *note DeprecationWarning: 18b. is now
          emitted when *note named placeholders: 2b5. are used together
          with parameters supplied as a *note sequence: 499. instead of
          as a *note dict: 23b.  Starting from Python 3.14, using named
          placeholders with parameters supplied as a sequence will raise
          a *note ProgrammingError: 49a.  (Contributed by Erlend E.
          Aasland in gh-101698(19).)

   * *note sys: c3.: The *note sys.last_type: 466, *note sys.last_value:
     467. and *note sys.last_traceback: 468. fields are deprecated.  Use
     *note sys.last_exc: 465. instead.  (Contributed by Irit Katriel in
     gh-102778(20).)

   * *note tarfile: c8.: Extracting tar archives without specifying
     'filter' is deprecated until Python 3.14, when ‘'data'’ filter will
     become the default.  See *note Extraction filters: 413. for
     details.

   * *note typing: ed.：

        * *note typing.Hashable: 49b. and *note typing.Sized: 49c,
          aliases for *note collections.abc.Hashable: 49d. and *note
          collections.abc.Sized: 49e. respectively, are deprecated.
          (gh-94309(21).)

        * *note typing.ByteString: 2b8, deprecated since Python 3.9, now
          causes a *note DeprecationWarning: 18b. to be emitted when it
          is used.  (Contributed by Alex Waygood in gh-91896(22).)

   * *note xml.etree.ElementTree: 10c.: The module now emits *note
     DeprecationWarning: 18b. when testing the truth value of an *note
     xml.etree.ElementTree.Element: 2e2.  Before, the Python
     implementation emitted *note FutureWarning: 357, and the C
     implementation emitted nothing.  (Contributed by Jacob Walls in
     gh-83122(23).)

   * The 3-arg signatures (type, value, traceback) of *note coroutine
     throw(): 49f, *note generator throw(): 4a0. and *note async
     generator throw(): 4a1. 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(24).)

   * *note DeprecationWarning: 18b. is now raised when ‘__package__’ on
     a module differs from ‘__spec__.parent’ (previously it was *note
     ImportWarning: 4a2.).  (Contributed by Brett Cannon in
     gh-65961(25).)

   * 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(26).)

   * 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(27).)

   * Accessing *note co_lnotab: 2b7. on code objects was deprecated in
     Python 3.10 via PEP 626(28), but it only got a proper *note
     DeprecationWarning: 18b. in 3.12, therefore it will be removed in
     3.14.  (Contributed by Nikita Sobolev in gh-101866(29).)

* Menu:

* Python 3.13 中待移除的項目: Python 3 13 中待移除的項目.
* Python 3.14 中待移除的項目: Python 3 14 中待移除的項目.
* Python 3.15 中待移除的項目: Python 3 15 中待移除的項目.
* Python 3.16 中待移除的項目: Python 3 16 中待移除的項目.
* 未來版本中的待移除項目::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/92248

   (2) https://github.com/python/cpython/issues/90953

   (3) https://github.com/python/cpython/issues/94597

   (4) https://github.com/python/cpython/issues/94597

   (5) https://github.com/python/cpython/issues/100160

   (6) https://github.com/python/cpython/issues/103636

   (7) https://github.com/python/cpython/issues/91896

   (8) https://github.com/python/cpython/issues/103857

   (9) https://github.com/python/cpython/issues/72346

   (10) https://github.com/python/cpython/issues/93963

   (11) https://github.com/python/cpython/issues/101588

   (12) https://github.com/python/cpython/issues/84559

   (13) https://github.com/python/cpython/issues/97850

   (14) https://github.com/python/cpython/issues/85984

   (15) https://github.com/python/cpython/issues/99726

   (16) https://discuss.python.org/t/33555

   (17) https://github.com/python/cpython/issues/102828

   (18) https://github.com/python/cpython/issues/90016

   (19) https://github.com/python/cpython/issues/101698

   (20) https://github.com/python/cpython/issues/102778

   (21) https://github.com/python/cpython/issues/94309

   (22) https://github.com/python/cpython/issues/91896

   (23) https://github.com/python/cpython/issues/83122

   (24) https://github.com/python/cpython/issues/89874

   (25) https://github.com/python/cpython/issues/65961

   (26) https://github.com/python/cpython/issues/65961

   (27) https://github.com/python/cpython/issues/103487

   (28) https://peps.python.org/pep-0626/

   (29) https://github.com/python/cpython/issues/101866


File: python.info,  Node: Python 3 13 中待移除的項目,  Next: Python 3 14 中待移除的項目,  Up: 已棄用

1.2.10.1 Python 3.13 中待移除的項目
...................................

模組（請見 PEP 594(1)）：

   * ‘aifc’

   * ‘audioop’

   * ‘cgi’

   * ‘cgitb’

   * ‘chunk’

   * ‘crypt’

   * ‘imghdr’

   * ‘mailcap’

   * ‘msilib’

   * ‘nis’

   * ‘nntplib’

   * ‘ossaudiodev’

   * ‘pipes’

   * ‘sndhdr’

   * ‘spwd’

   * ‘sunau’

   * ‘telnetlib’

   * ‘uu’

   * ‘xdrlib’

其他模組：

   * ‘lib2to3’ 和 ‘2to3’ 程式 (gh-84540(2))

API：

   * ‘configparser.LegacyInterpolation’ (gh-90765(3))

   * ‘locale.resetlocale()’ (gh-90817(4))

   * ‘turtle.RawTurtle.settiltangle()’ (gh-50096(5))

   * ‘unittest.findTestCases()’ (gh-50096(6))

   * ‘unittest.getTestCaseNames()’ (gh-50096(7))

   * ‘unittest.makeSuite()’ (gh-50096(8))

   * ‘unittest.TestProgram.usageExit()’ (gh-67048(9))

   * ‘webbrowser.MacOSX’ (gh-86421(10))

   * *note classmethod: 14a. 描述器鏈接 (gh-89519(11))

   * *note importlib.resources: 6f. 的已棄用方法：

        * ‘contents()’

        * ‘is_resource()’

        * ‘open_binary()’

        * ‘open_text()’

        * ‘path()’

        * ‘read_binary()’

        * ‘read_text()’

     請改用 *note importlib.resources.files(): 435.。請參閱
     importlib-resources: Migrating from Legacy(12) (gh-106531(13))

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0594/

   (2) https://github.com/python/cpython/issues/84540

   (3) https://github.com/python/cpython/issues/90765

   (4) https://github.com/python/cpython/issues/90817

   (5) https://github.com/python/cpython/issues/50096

   (6) https://github.com/python/cpython/issues/50096

   (7) https://github.com/python/cpython/issues/50096

   (8) https://github.com/python/cpython/issues/50096

   (9) https://github.com/python/cpython/issues/67048

   (10) https://github.com/python/cpython/issues/86421

   (11) https://github.com/python/cpython/issues/89519

   (12) 
https://importlib-resources.readthedocs.io/en/latest/using.html#migrating-from-legacy

   (13) https://github.com/python/cpython/issues/106531


File: python.info,  Node: Python 3 14 中待移除的項目,  Next: Python 3 15 中待移除的項目,  Prev: Python 3 13 中待移除的項目,  Up: 已棄用

1.2.10.2 Python 3.14 中待移除的項目
...................................

   * *note argparse: 5.：‘argparse.BooleanOptionalAction’ 的 'type'、
     'choices' 和 'metavar' 參數已被棄用，將在 3.14 中移除。 (由 Nikita
     Sobolev 於 gh-92248(1) 貢獻。)

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

        * ‘ast.Num’

        * ‘ast.Str’

        * ‘ast.Bytes’

        * ‘ast.NameConstant’

        * ‘ast.Ellipsis’

     請改用 *note ast.Constant: 29a.。（由 Serhiy Storchaka 於
     gh-90953(2) 貢獻。）

   * *note asyncio: 8.：

        * 已棄用並將在 Python 3.14 中移除的 child watcher 類別：*note
          MultiLoopChildWatcher: 29b.、*note FastChildWatcher: 29c.、
          *note AbstractChildWatcher: 29d. 和 *note SafeChildWatcher:
          29e.。 (由 Kumar Aditya 於 gh-94597(3) 貢獻。)

        * *note asyncio.set_child_watcher(): 29f.、*note
          asyncio.get_child_watcher(): 2a0.、*note
          asyncio.AbstractEventLoopPolicy.set_child_watcher(): 2a1. 和
          *note asyncio.AbstractEventLoopPolicy.get_child_watcher():
          2a2. 已被棄用並將在 Python 3.14 中移除。（由 Kumar Aditya 於
          gh-94597(4) 貢獻。）

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

   * *note collections.abc: 17.：已棄用 *note ByteString: 2a4.。請改用
     ‘Sequence’ 或 *note Buffer: 2a5.。在 typing 中使用時，請改用聯集，
     如 ‘bytes | bytearray’，或 *note collections.abc.Buffer: 2a5.。（由
     Shantanu Jain 於 gh-91896(6) 貢獻。）

   * *note email: 32.：已棄用 *note email.utils.localtime(): 2a6. 中的
     'isdst' 參數。（由 Alan Williams 於 gh-72346(7) 貢獻。）

   * *note importlib: 6b.：‘__package__’ 和 ‘__cached__’ 將不再被設定或
     被 import 系統考慮。 (gh-97879(8))

   * *note importlib.abc: 6c. 的已棄用類別：

        * ‘importlib.abc.ResourceReader’

        * ‘importlib.abc.Traversable’

        * ‘importlib.abc.TraversableResources’

     請改用 *note importlib.resources.abc: 70. 類別：

        * *note importlib.resources.abc.Traversable: 1d8.

        * *note importlib.resources.abc.TraversableResources: 2a7.

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

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

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

   * *note pathlib: 93.：已棄用 *note is_relative_to(): 2ab. 和 *note
     relative_to(): 2ac.：額外引數的傳遞已被棄用。

   * *note pkgutil: 97.：*note find_loader(): 2ad. 和 *note
     get_loader(): 2ae. 現在會引發 *note DeprecationWarning: 18b.；請改
     用 *note importlib.util.find_spec(): 2af.。 (由 Nikita Sobolev 於
     gh-97850(12) 貢獻。)

   * *note pty: 9f.：

        * ‘master_open()’：請用 *note pty.openpty(): 2b0.。

        * ‘slave_open()’：請用 *note pty.openpty(): 2b0.。

   * *note sqlite3: ba.：

        * *note version: 2b1. 和 *note version_info: 2b2.。

        * *note execute(): 2b3. 和 *note executemany(): 2b4.，如果使用
          *note named placeholders: 2b5. 且 'parameters' 是序列而不是
          *note dict: 23b.。

        * date 和 datetime 的適配器 (adapter)、date 和 timestamp 轉換器
          (converter)：請參閱 *note sqlite3: ba. 文件以獲得建議的替代方
          案。

   * *note types.CodeType: 2b6.：自 3.10 起，存取 *note co_lnotab: 2b7.
     已在 PEP 626(13) 中被棄用，並計劃在 3.12 中移除，但只在 3.12 中於適
     當時發出 *note DeprecationWarning: 18b.。可能在 3.14 中移除。（由
     Nikita Sobolev 於 gh-101866(14) 貢獻。）

   * *note typing: ed.：自 Python 3.9 起已被棄用的 *note ByteString:
     2b8. 現在在使用時會發出 *note DeprecationWarning: 18b.。

   * *note urllib: f1.：‘urllib.parse.Quoter’ 已被棄用：它並非預期的公開
     API。(由 Gregory P. Smith 於 gh-88168(15) 貢獻。)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/92248

   (2) https://github.com/python/cpython/issues/90953

   (3) https://github.com/python/cpython/issues/94597

   (4) https://github.com/python/cpython/issues/94597

   (5) https://github.com/python/cpython/issues/100160

   (6) https://github.com/python/cpython/issues/91896

   (7) https://github.com/python/cpython/issues/72346

   (8) https://github.com/python/cpython/issues/97879

   (9) https://github.com/python/cpython/issues/93963

   (10) https://github.com/python/cpython/issues/101588

   (11) https://github.com/python/cpython/issues/84559

   (12) https://github.com/python/cpython/issues/97850

   (13) https://peps.python.org/pep-0626/

   (14) https://github.com/python/cpython/issues/101866

   (15) https://github.com/python/cpython/issues/88168


File: python.info,  Node: Python 3 15 中待移除的項目,  Next: Python 3 16 中待移除的項目,  Prev: Python 3 14 中待移除的項目,  Up: 已棄用

1.2.10.3 Python 3.15 中待移除的項目
...................................

   * *note http.server.CGIHTTPRequestHandler: 281. 將會被移除，連同其相
     關的 ‘--cgi’ 旗標到 ‘python -m http.server’。它已經過時且很少被使用
     。沒有直接的替代方案。'任何東西'都比 CGI 更好的來介接一個帶有請求處
     理器的網頁伺服器。

   * *note locale: 7a.：*note locale.getdefaultlocale(): 2ba. 已在
     Python 3.11 中被棄用，原本計劃在 Python 3.13 中移除 (gh-90817(1))，
     但被延後至 Python 3.15。請改用 *note locale.setlocale(): 2bb.、
     *note locale.getencoding(): 2bc. 和 *note locale.getlocale(): 2bd.。
     (由 Hugo van Kemenade 於 gh-111187(2) 貢獻。)

   * *note pathlib: 93.: *note pathlib.PurePath.is_reserved(): 286. is
     deprecated and scheduled for removal in Python 3.15.  Use *note
     os.path.isreserved(): 208. to detect reserved paths on Windows.

   * *note platform: 98.：*note java_ver(): 287. 已被棄用並將在 3.15 中
     移除。它幾乎沒有被測試過，API 令人困惑並且只對 Jython 支援有用。 (由
     Nikita Sobolev 於 gh-116349(3) 貢獻。)

   * *note threading: d6.：對 *note threading.RLock(): 2be. 傳遞任何引數
     現在已被棄用。C 版本允許任意數量的引數和關鍵字引數，但它們會被忽略
     。Python 版本不允許任何引數。所有引數將在 Python 3.15 中從 *note
     threading.RLock(): 2be. 中移除。 (由 Nikita Sobolev 於 gh-102029(4)
     貢獻。)

   * *note typing.NamedTuple: 291.：

        * 用於建立 ‘NamedTuple’ 類別的未以文件記錄之關鍵字引數語法 (‘NT
          = NamedTuple("NT", x=int)’) 已棄用，並將在 3.15 中被禁止。請改
          用基於類別的語法或函式語法 (functional syntax)。

        * 當使用函式語法來建立 ‘NamedTuple’ 類別時，沒將值傳遞給
          'fields' 參數的方式 (‘NT = NamedTuple("NT")’) 已被棄用，將
          ‘None’ 傳遞給 'fields' 參數（‘NT = NamedTuple("NT", None)’）也
          已被棄用。這兩者將在 Python 3.15 中會被禁止。要建立一個沒有欄
          位的 ‘NamedTuple’ 類別，請使用 ‘class NT(NamedTuple): pass’ 或
          ‘NT = NamedTuple("NT", [])’。

   * *note typing.TypedDict: 146.：當使用函式語法來建立 ‘TypedDict’ 類別
     時，沒將值傳遞給 'fields' 參數的方式（‘TD = TypedDict("TD")’）已被
     棄用，將 ‘None’ 傳遞給 'fields' 參數（‘TD = TypedDict("TD", None)’）
     也已被棄用。這兩者將在 Python 3.15 中會被禁止。要建立一個沒有欄位的
     ‘TypedDict’ 類別，請使用 ‘class TD(TypedDict): pass’ 或 ‘TD =
     TypedDict("TD", {})’。

   * *note wave: fb.：已棄用 *note wave.Wave_read: 297. 和 *note
     wave.Wave_write: 298. 類別的 ‘getmark()’、‘setmark()’ 和
     ‘getmarkers()’ 方法。它們將在 Python 3.15 中被移除。 (由 Victor
     Stinner 於 gh-105096(5) 貢獻。)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/90817

   (2) https://github.com/python/cpython/issues/111187

   (3) https://github.com/python/cpython/issues/116349

   (4) https://github.com/python/cpython/issues/102029

   (5) https://github.com/python/cpython/issues/105096


File: python.info,  Node: Python 3 16 中待移除的項目,  Next: 未來版本中的待移除項目,  Prev: Python 3 15 中待移除的項目,  Up: 已棄用

1.2.10.4 Python 3.16 中待移除的項目
...................................

   * *note array: 6.：*note array.array: 186. ‘'u'’ 型別 (‘wchar_t’)：請
     改用 ‘'w'’ 型別 (‘Py_UCS4’)。

   * *note builtins: e.：‘~bool’，對 bool 進行位元反轉。

   * *note symtable: c2.：由於並沒有太多關注，已棄用 *note
     symtable.Class.get_methods(): 2c0.。 (由 Bénédikt Tran 於
     gh-119698(1) 貢獻。)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/119698


File: python.info,  Node: 未來版本中的待移除項目,  Prev: Python 3 16 中待移除的項目,  Up: 已棄用

1.2.10.5 未來版本中的待移除項目
...............................

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

   * *note argparse: 5.：已棄用巢狀引數群組和巢狀互斥群組。

   * *note array: 6. 的 ‘'u'’ 格式碼 (gh-57281(1))

   * *note builtins: e.：

        * ‘bool(NotImplemented)’。

        * 產生器：‘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]’）。如
          果數值字面值後立即接 *note and: 2c2.、*note else: 172.、*note
          for: 2c3.、*note if: 2c4.、*note in: 2c5.、*note is: 2c6. 和
          *note or: 2c7. 之一的關鍵字，則會引發語法警告。在未來版本中，
          它將被更改為語法錯誤。(gh-87999(2))

        * ‘__index__()’ 和 ‘__int__()’ 方法回傳非 int 型別的支援：這些方
          法將需要回傳 *note int: 23c. 的嚴格子類別實例。

        * 回傳 *note float: 2c8. 嚴格子類別 ‘__float__()’ 方法的支援：這
          些方法將需要回傳 *note float: 2c8. 的實例。

        * 回傳 *note complex: 2c9. 嚴格子類別 ‘__complex__()’ 方法的支援
          ：這些方法將需要回傳 *note complex: 2c9. 的實例。

        * 將 ‘int()’ 委派給 ‘__trunc__()’ 方法。

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

   * *note calendar: 10.：‘calendar.January’ 和 ‘calendar.February’ 常數
     已被棄用並被 *note calendar.JANUARY: 2ca. 和 *note
     calendar.FEBRUARY: 2cb. 取代。 (由 Prince Roshan 於 gh-103636(4) 貢
     獻。)

   * *note codeobject.co_lnotab: 2b7.：請改用 *note
     codeobject.co_lines(): 2cc. 方法。

   * *note datetime: 28.：

        * *note utcnow(): 2cd.：請改用
          ‘datetime.datetime.now(tz=datetime.UTC)’。

        * *note utcfromtimestamp(): 2ce.：請改用
          ‘datetime.datetime.fromtimestamp(timestamp, tz=datetime.UTC)’。

   * *note gettext: 59.：複數值必須是整數。

   * *note importlib: 6b.：

        * ‘load_module()’ method：請改用 ‘exec_module()’。

        * *note cache_from_source(): 2cf. 'debug_override' 參數已被棄用
          ：請改用 'optimization' 參數。

   * *note importlib.metadata: 6e.：

        * ‘EntryPoints’ 元組介面。

        * 回傳值上的隱式 ‘None’。

   * *note logging: 7b.: the ‘warn()’ method has been deprecated since
     Python 3.3, use *note warning(): 2d0. instead.

   * *note mailbox: 7f.：已棄用 StringIO 輸入和文本模式，請改用 BytesIO
     和二進位模式。

   * *note os: 91.：在多執行緒行程中呼叫 *note os.register_at_fork():
     2d1.。

   * ‘pydoc.ErrorDuringImport’：'exc_info' 參數的元組值已被棄用，請用例
     外實例。

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

   * ‘sre_compile’、‘sre_constants’ 和 ‘sre_parse’ 模組。

   * *note shutil: b3.：*note rmtree(): 2d2. 的 'onerror' 參數在 Python
     3.12 中已被棄用；請改用 'onexc' 參數。

   * *note ssl: bb. 選項和協定：

        * 不帶協定引數的 *note ssl.SSLContext: 276. 已被棄用。

        * *note ssl.SSLContext: 276.：*note set_npn_protocols(): 2d3. 和
          ‘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’

   * *note sysconfig.is_python_build(): 2d4. 的 'check_home' 參數已被棄
     用並被忽略。

   * *note threading: d6. 方法：

        * ‘threading.Condition.notifyAll()’：請用 *note notify_all():
          2d5.。

        * ‘threading.Event.isSet()’：請用 *note is_set(): 2d6.。

        * ‘threading.Thread.isDaemon()’、*note
          threading.Thread.setDaemon(): 2d7.：請用 *note
          threading.Thread.daemon: 2d8. 屬性。

        * ‘threading.Thread.getName()’、*note
          threading.Thread.setName(): 2d9.：請用 *note
          threading.Thread.name: 2da. 屬性。

        * ‘threading.currentThread()’：請用 *note
          threading.current_thread(): 2db.。

        * ‘threading.activeCount()’：請用 *note
          threading.active_count(): 2dc.。

   * *note typing.Text: 2dd. (gh-92332(6))。

   * *note unittest.IsolatedAsyncioTestCase: 2de.：從測試案例中回傳非
     ‘None’ 的值已被棄用。

   * *note urllib.parse: f3. 已棄用函式：請改用 *note urlparse(): 2df.。

        * ‘splitattr()’

        * ‘splithost()’

        * ‘splitnport()’

        * ‘splitpasswd()’

        * ‘splitport()’

        * ‘splitquery()’

        * ‘splittag()’

        * ‘splittype()’

        * ‘splituser()’

        * ‘splitvalue()’

        * ‘to_bytes()’

   * *note urllib.request: f4.：呼叫請求的 *note URLopener: 2e0. 和
     *note FancyURLopener: 2e1. 風格已被棄用。請改用更新的 *note
     urlopen(): 275. 函式和方法。

   * *note wsgiref: 100.：‘SimpleHandler.stdout.write()’ 不應該進行部分
     寫入。

   * *note xml.etree.ElementTree: 10c.：已棄用對 *note Element: 2e2. 的
     真值測試。在未來版本中，它將始終回傳 ‘True’。請改用明確的
     ‘len(elem)’ 或 ‘elem is not None’ 測試。

   * *note zipimport.zipimporter.load_module(): 2e3. 已被棄用：請改用
     *note exec_module(): 2e4.。

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/57281

   (2) https://github.com/python/cpython/issues/87999

   (3) https://github.com/python/cpython/issues/109218

   (4) https://github.com/python/cpython/issues/103636

   (5) https://github.com/python/cpython/issues/91760

   (6) https://github.com/python/cpython/issues/92332


File: python.info,  Node: 已移除,  Next: Porting to Python 3 12,  Prev: 已棄用,  Up: Python 3 12 有什麼新功能

1.2.11 已移除
-------------

* Menu:

* asynchat 和 asyncore::
* configparser: configparser<4>.
* distutils::
* ensurepip::
* enum::
* ftplib::
* gzip::
* hashlib::
* importlib: importlib<2>.
* imp::
* io: io<2>.
* locale: locale<2>.
* smtpd::
* sqlite3: sqlite3<3>.
* ssl: ssl<2>.
* unittest: unittest<3>.
* webbrowser: webbrowser<2>.
* xml.etree.ElementTree: xml etree ElementTree.
* zipimport: zipimport<2>.
* 其他::


File: python.info,  Node: asynchat 和 asyncore,  Next: configparser<4>,  Up: 已移除

1.2.11.1 asynchat 和 asyncore
.............................

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

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0594/

   (2) https://github.com/python/cpython/issues/96580


File: python.info,  Node: configparser<4>,  Next: distutils,  Prev: asynchat 和 asyncore,  Up: 已移除

1.2.11.2 configparser
.....................

   * Several names deprecated in the *note configparser: 1b. way back in
     3.2 have been removed per gh-89336(1):

        * *note configparser.ParsingError: 4ab. 不再具有 ‘filename’ 屬性
          或引數。請改用 ‘source’ 屬性和引數。

        * *note configparser: 1b. no longer has a ‘SafeConfigParser’
          class.  Use the shorter *note ConfigParser: 1aa. name instead.

        * *note configparser.ConfigParser: 1aa. no longer has a ‘readfp’
          method.  Use *note read_file(): 4ac. instead.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/89336


File: python.info,  Node: distutils,  Next: ensurepip,  Prev: configparser<4>,  Up: 已移除

1.2.11.3 distutils
..................

   * Remove the ‘distutils’ package.  It was deprecated in Python 3.10
     by PEP 632(1) "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(2).)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0632/

   (2) https://github.com/python/cpython/issues/92584


File: python.info,  Node: ensurepip,  Next: enum,  Prev: distutils,  Up: 已移除

1.2.11.4 ensurepip
..................

   * Remove the bundled setuptools wheel from *note ensurepip: 4b, and
     stop installing setuptools in environments created by *note venv:
     f9.

     ‘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(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/95299


File: python.info,  Node: enum,  Next: ftplib,  Prev: ensurepip,  Up: 已移除

1.2.11.5 enum
.............

   * Remove *note enum: 4c.'s ‘EnumMeta.__getattr__’, which is no longer
     needed for enum attribute access.  (Contributed by Ethan Furman in
     gh-95083(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/95083


File: python.info,  Node: ftplib,  Next: gzip,  Prev: enum,  Up: 已移除

1.2.11.6 ftplib
...............

   * 移除 *note ftplib: 54. 的 ‘FTP_TLS.ssl_version’ 類別屬性：請改用
     'context' 參數。（由 Victor Stinner 於 gh-94172(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/94172


File: python.info,  Node: gzip,  Next: hashlib,  Prev: ftplib,  Up: 已移除

1.2.11.7 gzip
.............

   * Remove the ‘filename’ attribute of *note gzip: 5d.'s *note
     gzip.GzipFile: 354, deprecated since Python 2.6, use the *note
     name: 4b2. attribute instead.  In write mode, the ‘filename’
     attribute added ‘'.gz'’ file extension if it was not present.
     (Contributed by Victor Stinner in gh-94196(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/94196


File: python.info,  Node: hashlib,  Next: importlib<2>,  Prev: gzip,  Up: 已移除

1.2.11.8 hashlib
................

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

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0644/

   (2) https://github.com/python/cpython/issues/94199


File: python.info,  Node: importlib<2>,  Next: imp,  Prev: hashlib,  Up: 已移除

1.2.11.9 importlib
..................

   * 現已完成清理 *note importlib: 6b. 中許多過去已經棄用的東西：

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

        * ‘importlib.util.set_package’, ‘importlib.util.set_loader’ and
          ‘importlib.util.module_for_loader’ have all been removed.
          (Contributed by Brett Cannon and Nikita Sobolev in gh-65961(2)
          and gh-97850(3).)

        * Support for ‘find_loader()’ and ‘find_module()’ APIs have been
          removed.  (Contributed by Barry Warsaw in gh-98040(4).)

        * ‘importlib.abc.Finder’, ‘pkgutil.ImpImporter’, and
          ‘pkgutil.ImpLoader’ have been removed.  (Contributed by Barry
          Warsaw in gh-98040(5).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/97850

   (2) https://github.com/python/cpython/issues/65961

   (3) https://github.com/python/cpython/issues/97850

   (4) https://github.com/python/cpython/issues/98040

   (5) https://github.com/python/cpython/issues/98040


File: python.info,  Node: imp,  Next: io<2>,  Prev: importlib<2>,  Up: 已移除

1.2.11.10 imp
.............

   * The ‘imp’ module has been removed.  (Contributed by Barry Warsaw in
     gh-98040(1).)

     To migrate, consult the following correspondence table:

          imp                                   importlib
                                                
          -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
                                                
          ‘imp.NullImporter’                    將 ‘None’ 插入 ‘sys.path_importer_cache’
                                                
                                                
          ‘imp.cache_from_source()’             *note importlib.util.cache_from_source(): 2cf.
                                                
                                                
          ‘imp.find_module()’                   *note importlib.util.find_spec(): 2af.
                                                
                                                
          ‘imp.get_magic()’                     *note importlib.util.MAGIC_NUMBER: 4b7.
                                                
                                                
          ‘imp.get_suffixes()’                  *note importlib.machinery.SOURCE_SUFFIXES: 4b8, *note importlib.machinery.EXTENSION_SUFFIXES: 4b9, and
                                                *note importlib.machinery.BYTECODE_SUFFIXES: 4ba.
                                                
                                                
          ‘imp.get_tag()’                       *note sys.implementation.cache_tag: 4bb.
                                                
                                                
          ‘imp.load_module()’                   *note importlib.import_module(): 4bc.
                                                
                                                
          ‘imp.new_module(name)’                ‘types.ModuleType(name)’
                                                
                                                
          ‘imp.reload()’                        *note importlib.reload(): 4bd.
                                                
                                                
          ‘imp.source_from_cache()’             *note importlib.util.source_from_cache(): 4be.
                                                
                                                
          ‘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)
              # The module is always executed and not cached in sys.modules.
              # Uncomment the following line to cache the module.
              # 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’。

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/98040


File: python.info,  Node: io<2>,  Next: locale<2>,  Prev: imp,  Up: 已移除

1.2.11.11 io
............

   * Remove *note io: 73.'s ‘io.OpenWrapper’ and ‘_pyio.OpenWrapper’,
     deprecated in Python 3.10: just use *note open(): 4c0. instead.
     The *note open(): 4c0. (*note io.open(): 4c1.) function is a
     built-in function.  Since Python 3.10, ‘_pyio.open()’ is also a
     static method.  (Contributed by Victor Stinner in gh-94169(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/94169


File: python.info,  Node: locale<2>,  Next: smtpd,  Prev: io<2>,  Up: 已移除

1.2.11.12 locale
................

   * Remove *note locale: 7a.'s ‘locale.format()’ function, deprecated
     in Python 3.7: use *note locale.format_string(): 4c3. instead.
     (Contributed by Victor Stinner in gh-94226(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/94226


File: python.info,  Node: smtpd,  Next: sqlite3<3>,  Prev: locale<2>,  Up: 已移除

1.2.11.13 smtpd
...............

   * The ‘smtpd’ module has been removed according to the schedule in
     PEP 594(1), having been deprecated in Python 3.4.7 and 3.5.4.  Use
     the aiosmtpd(2) PyPI module or any other *note asyncio: 8.-based
     server instead.  (Contributed by Oleg Iarygin in gh-93243(3).)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0594/

   (2) https://pypi.org/project/aiosmtpd/

   (3) https://github.com/python/cpython/issues/93243


File: python.info,  Node: sqlite3<3>,  Next: ssl<2>,  Prev: smtpd,  Up: 已移除

1.2.11.14 sqlite3
.................

   * The following undocumented *note sqlite3: ba. features, deprecated
     in Python 3.10, are now removed:

        * ‘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
     *note str: 3f2. 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(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/92548


File: python.info,  Node: ssl<2>,  Next: unittest<3>,  Prev: sqlite3<3>,  Up: 已移除

1.2.11.15 ssl
.............

   * Remove *note ssl: bb.'s ‘ssl.RAND_pseudo_bytes()’ function,
     deprecated in Python 3.6: use *note os.urandom(): 4c7. or *note
     ssl.RAND_bytes(): 4c8. instead.  (Contributed by Victor Stinner in
     gh-94199(1).)

   * 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(2).)

   * Remove the ‘ssl.wrap_socket()’ function, deprecated in Python 3.7:
     instead, create a *note ssl.SSLContext: 276. object and call its
     *note ssl.SSLContext.wrap_socket: 4c9. 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(3) (Improper Certificate
     Validation).  (Contributed by Victor Stinner in gh-94199(4).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/94199

   (2) https://github.com/python/cpython/issues/94199

   (3) https://cwe.mitre.org/data/definitions/295.html

   (4) https://github.com/python/cpython/issues/94199


File: python.info,  Node: unittest<3>,  Next: webbrowser<2>,  Prev: ssl<2>,  Up: 已移除

1.2.11.16 unittest
..................

   * 移除許多 *note unittest: ef. 中被棄用已久的功能：

        * 許多 *note TestCase: 3f4. 方法別名：

          已棄用的別名                     方法名稱                            已棄用於
                                                                               
          -----------------------------------------------------------------------------------------
                                                                               
          ‘failUnless’                     *note assertTrue(): 4cb.            3.1
                                                                               
                                                                               
          ‘failIf’                         *note assertFalse(): 4cc.           3.1
                                                                               
                                                                               
          ‘failUnlessEqual’                *note assertEqual(): 4cd.           3.1
                                                                               
                                                                               
          ‘failIfEqual’                    *note assertNotEqual(): 4ce.        3.1
                                                                               
                                                                               
          ‘failUnlessAlmostEqual’          *note assertAlmostEqual(): 4cf.     3.1
                                                                               
                                                                               
          ‘failIfAlmostEqual’              *note assertNotAlmostEqual(): 4d0.  3.1
                                                                               
                                                                               
          ‘failUnlessRaises’               *note assertRaises(): 4d1.          3.1
                                                                               
                                                                               
          ‘assert_’                        *note assertTrue(): 4cb.            3.2
                                                                               
                                                                               
          ‘assertEquals’                   *note assertEqual(): 4cd.           3.2
                                                                               
                                                                               
          ‘assertNotEquals’                *note assertNotEqual(): 4ce.        3.2
                                                                               
                                                                               
          ‘assertAlmostEquals’             *note assertAlmostEqual(): 4cf.     3.2
                                                                               
                                                                               
          ‘assertNotAlmostEquals’          *note assertNotAlmostEqual(): 4d0.  3.2
                                                                               
                                                                               
          ‘assertRegexpMatches’            *note assertRegex(): 4d2.           3.2
                                                                               
                                                                               
          ‘assertRaisesRegexp’             *note assertRaisesRegex(): 4d3.     3.2
                                                                               
                                                                               
          ‘assertNotRegexpMatches’         *note assertNotRegex(): 4d4.        3.5
                                                                               

          You can use ‘https://github.com/isidentical/teyit’ to
          automatically modernise your unit tests.

        * Undocumented and broken *note TestCase: 3f4. method
          ‘assertDictContainsSubset’ (deprecated in Python 3.2).

        * Undocumented *note TestLoader.loadTestsFromModule: 271.
          parameter 'use_load_tests' (deprecated and ignored since
          Python 3.5).

        * An alias of the *note TextTestResult: 4d5. class:
          ‘_TextTestResult’ (deprecated in Python 3.2).

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

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/89325


File: python.info,  Node: webbrowser<2>,  Next: xml etree ElementTree,  Prev: unittest<3>,  Up: 已移除

1.2.11.17 webbrowser
....................

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

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/102871


File: python.info,  Node: xml etree ElementTree,  Next: zipimport<2>,  Prev: webbrowser<2>,  Up: 已移除

1.2.11.18 xml.etree.ElementTree
...............................

   * Remove the ‘ElementTree.Element.copy()’ method of the pure Python
     implementation, deprecated in Python 3.10, use the *note
     copy.copy(): 4d8. function instead.  The C implementation of *note
     xml.etree.ElementTree: 10c. has no ‘copy()’ method, only a
     ‘__copy__()’ method.  (Contributed by Victor Stinner in
     gh-94383(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/94383


File: python.info,  Node: zipimport<2>,  Next: 其他,  Prev: xml etree ElementTree,  Up: 已移除

1.2.11.19 zipimport
...................

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

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0451/

   (2) https://github.com/python/cpython/issues/94379


File: python.info,  Node: 其他,  Prev: zipimport<2>,  Up: 已移除

1.2.11.20 其他
..............

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

   * Remove the 'keyfile' and 'certfile' parameters from the *note
     ftplib: 54, *note imaplib: 6a, *note poplib: 9a. and *note smtplib:
     b7. modules, and the 'key_file', 'cert_file' and 'check_hostname'
     parameters from the *note http.client: 65. module, all deprecated
     since Python 3.6.  Use the 'context' parameter ('ssl_context' in
     *note imaplib: 6a.) instead.  (Contributed by Victor Stinner in
     gh-94172(3).)

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

   * 移除 *note ctypes: 22. 模組中的
     ‘_use_broken_old_ctypes_structure_semantics_’ 旗標。（由 Nikita
     Sobolev 於 gh-99285(5) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://github.com/sphinx-contrib/sphinx-lint

   (2) https://github.com/python/cpython/issues/98179

   (3) https://github.com/python/cpython/issues/94172

   (4) https://github.com/python/cpython/issues/99482

   (5) https://github.com/python/cpython/issues/99285


File: python.info,  Node: Porting to Python 3 12,  Next: 建置變更,  Prev: 已移除,  Up: Python 3 12 有什麼新功能

1.2.12 Porting to Python 3.12
-----------------------------

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

* Menu:

* Python API 的變更::


File: python.info,  Node: Python API 的變更,  Up: Porting to Python 3 12

1.2.12.1 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(1).)

   * Remove ‘randrange()’ functionality deprecated since Python 3.10.
     Formerly, ‘randrange(10.0)’ losslessly converted to
     ‘randrange(10)’.  Now, it raises a *note TypeError: 4dd.  Also, the
     exception raised for non-integer values such as ‘randrange(10.5)’
     or ‘randrange('10')’ has been changed from *note ValueError: 1e7.
     to *note TypeError: 4dd.  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(2).)

   * *note argparse.ArgumentParser: 4de. changed encoding and error
     handler for reading arguments from file (e.g.
     ‘fromfile_prefix_chars’ option) from default text encoding (e.g.
     *note locale.getpreferredencoding(False): 4df.) to *note filesystem
     encoding and error handler: 4e0.  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 *note asyncio:
     8.-based aiosmtpd(3) PyPI module.

   * *note shlex.split(): 4e1.: Passing ‘None’ for 's' argument now
     raises an exception, rather than reading *note sys.stdin: 4e2.  The
     feature was deprecated in Python 3.9.  (Contributed by Victor
     Stinner in gh-94352(4).)

   * The *note os: 91. module no longer accepts bytes-like paths, like
     *note bytearray: 4e3. and *note memoryview: 40f. types: only the
     exact *note bytes: 1a5. type is accepted for bytes strings.
     (Contributed by Victor Stinner in gh-98393(5).)

   * *note syslog.openlog(): 4e4. and *note syslog.closelog(): 4e5. now
     fail if used in subinterpreters.  *note syslog.syslog(): 4e6. may
     still be used in subinterpreters, but now only if *note
     syslog.openlog(): 4e4. 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, *note
     syslog: c6. is a wrapper around process-global resources, which are
     best managed from the main interpreter.  (Contributed by Donghee Na
     in gh-99127(6).)

   * The undocumented locking behavior of *note cached_property(): 4e7.
     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.

   * *note sys._current_exceptions(): 469. 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(7).)

   * When extracting tar files using *note tarfile: c8. or *note
     shutil.unpack_archive(): 412, pass the 'filter' argument to limit
     features that may be surprising or dangerous.  See *note Extraction
     filters: 413. for details.

   * The output of the *note tokenize.tokenize(): 481. and *note
     tokenize.generate_tokens(): 482. functions is now changed due to
     the changes introduced in PEP 701(8).  This means that ‘STRING’
     tokens are not emitted any more for f-strings and the tokens
     described in PEP 701(9) 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(10).  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 *note
          tokenize.TokenError: 4e8. as incomplete multiline strings do.

        * Some incomplete or invalid Python code now raises *note
          tokenize.TokenError: 4e8. 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 *note TabError: 4e9.

   * The *note threading: d6. 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(11).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/91760

   (2) https://github.com/python/cpython/issues/86388

   (3) https://pypi.org/project/aiosmtpd/

   (4) https://github.com/python/cpython/issues/94352

   (5) https://github.com/python/cpython/issues/98393

   (6) https://github.com/python/cpython/issues/99127

   (7) https://github.com/python/cpython/issues/103176

   (8) https://peps.python.org/pep-0701/

   (9) https://peps.python.org/pep-0701/

   (10) https://peps.python.org/pep-0701/

   (11) https://github.com/python/cpython/issues/112826


File: python.info,  Node: 建置變更,  Next: C API 變更,  Prev: Porting to Python 3 12,  Up: Python 3 12 有什麼新功能

1.2.13 建置變更
---------------

   * 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(1).)

   * ‘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(2).)

   * 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(3).)

   * Add ‘COMPILEALL_OPTS’ variable in ‘Makefile’ to override *note
     compileall: 19. 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(4).)

   * Add platform triplets for 64-bit LoongArch:

        * loongarch64-linux-gnusf

        * loongarch64-linux-gnuf32

        * loongarch64-linux-gnu

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

   * ‘PYTHON_FOR_REGEN’ now require Python 3.10 or newer.

   * Autoconf 2.71 and aclocal 1.16.4 is now required to regenerate
     ‘!configure’.  (Contributed by Christian Heimes in gh-89886(6).)

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

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/93939

   (2) https://github.com/python/cpython/issues/93207

   (3) https://github.com/python/cpython/issues/89536

   (4) https://github.com/python/cpython/issues/99289

   (5) https://github.com/python/cpython/issues/90656

   (6) https://github.com/python/cpython/issues/89886


File: python.info,  Node: C API 變更,  Prev: 建置變更,  Up: Python 3 12 有什麼新功能

1.2.14 C API 變更
-----------------

* Menu:

* 新增特性: 新增特性<2>.
* Porting to Python 3.12: Porting to Python 3 12<2>.
* 已棄用: 已棄用<2>.
* 已移除: 已移除<2>.


File: python.info,  Node: 新增特性<2>,  Next: Porting to Python 3 12<2>,  Up: C API 變更

1.2.14.1 新增特性
.................

   * PEP 697(1): Introduce the *note Unstable C API tier: 4ed, 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(2))：

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

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

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

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

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

   * PEP 697(4): Add an API for extending types whose instance memory
     layout is opaque:

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

        - *note PyObject_GetTypeData(): 4ef. and *note
          PyType_GetTypeDataSize(): 4f0. added to allow access to
          subclass-specific instance data.

        - *note Py_TPFLAGS_ITEMS_AT_END: 4f1. and *note
          PyObject_GetItemData(): 4f2. added to allow safely extending
          certain variable-sized types, including *note PyType_Type:
          4f3.

        - *note Py_RELATIVE_OFFSET: 4f4. added to allow defining *note
          members: 4f5. in terms of a subclass-specific struct.

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

   * Add the new *note limited C API: 318. function *note
     PyType_FromMetaclass(): 4f6, which generalizes the existing *note
     PyType_FromModuleAndSpec(): 4f7. using an additional metaclass
     argument.  (Contributed by Wenzel Jakob in gh-93012(6).)

   * API for creating objects that can be called using *note the
     vectorcall protocol: 4f8. was added to the *note Limited API: 4f9.:

        * *note Py_TPFLAGS_HAVE_VECTORCALL: 4fa.

        * *note PyVectorcall_NARGS(): 4fb.

        * *note PyVectorcall_Call(): 4fc.

        * *note vectorcallfunc: 4fd.

     The *note Py_TPFLAGS_HAVE_VECTORCALL: 4fa. flag is now removed from
     a class when the class's *note __call__(): 4fe. method is
     reassigned.  This makes vectorcall safe to use with mutable types
     (i.e.  heap types without the immutable flag, *note
     Py_TPFLAGS_IMMUTABLETYPE: 38d.).  Mutable types that do not
     override *note tp_call: 4ff. now inherit the
     ‘Py_TPFLAGS_HAVE_VECTORCALL’ flag.  (Contributed by Petr Viktorin
     in gh-93274(7).)

     The *note Py_TPFLAGS_MANAGED_DICT: 31b. and *note
     Py_TPFLAGS_MANAGED_WEAKREF: 500. 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 *note the vectorcall protocol: 4f8.
     was added to the *note Limited API: 4f9.:

        * *note PyObject_Vectorcall(): 501.

        * *note PyObject_VectorcallMethod(): 502.

        * *note PY_VECTORCALL_ARGUMENTS_OFFSET: 503.

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

   * Add two new public functions, *note PyEval_SetProfileAllThreads():
     504. and *note PyEval_SetTraceAllThreads(): 505, 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(9).)

   * Add new function *note PyFunction_SetVectorcall(): 506. to the C
     API which sets the vectorcall field of a given *note
     PyFunctionObject: 507.  (Contributed by Andrew Frost in
     gh-92257(10).)

   * The C API now permits registering callbacks via *note
     PyDict_AddWatcher(): 508, *note PyDict_Watch(): 509. 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(11).)

   * Add *note PyType_AddWatcher(): 50a. and *note PyType_Watch(): 50b.
     API to register callbacks to receive notification on changes to a
     type.  (Contributed by Carl Meyer in gh-91051(12).)

   * Add *note PyCode_AddWatcher(): 50c. and *note
     PyCode_ClearWatcher(): 50d. APIs to register callbacks to receive
     notification on creation and destruction of code objects.
     (Contributed by Itamar Oren in gh-91054(13).)

   * Add *note PyFrame_GetVar(): 50e. and *note PyFrame_GetVarString():
     50f. functions to get a frame variable by its name.  (Contributed
     by Victor Stinner in gh-91248(14).)

   * Add *note PyErr_GetRaisedException(): 3bc. and *note
     PyErr_SetRaisedException(): 3bf. 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 *note PyErr_Fetch(): 3bb. and *note PyErr_Restore():
     3be.  This is less error prone and a bit more efficient.
     (Contributed by Mark Shannon in gh-101578(15).)

   * 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(16).)

   * Add *note PyException_GetArgs(): 510. and *note
     PyException_SetArgs(): 511. as convenience functions for retrieving
     and modifying the *note args: 512. passed to the exception's
     constructor.  (Contributed by Mark Shannon in gh-101578(17).)

   * Add *note PyErr_DisplayException(): 3ca, which takes an exception
     instance, to replace the legacy-api ‘PyErr_Display()’.
     (Contributed by Irit Katriel in gh-102755(18)).

   * PEP 683(19): 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’ An identifier for interned unicode objects

               that are immortal.

        - 
          ‘SSTATE_INTERNED_IMMORTAL_STATIC’ An identifier for interned unicode

               objects that are immortal and static

        - 
          ‘sys.getunicodeinternedsize’ This returns the total number of 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(20) 中貢獻。）

   * PEP 684(21): Add the new *note Py_NewInterpreterFromConfig(): 402.
     function and *note PyInterpreterConfig: 513, which may be used to
     create sub-interpreters with their own GILs.  (See *note PEP 684; A
     Per-Interpreter GIL: 3e2. for more info.)  (Contributed by Eric
     Snow in gh-104110(22).)

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

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0697/

   (2) https://peps.python.org/pep-0523/

   (3) https://github.com/python/cpython/issues/101101

   (4) https://peps.python.org/pep-0697/

   (5) https://github.com/python/cpython/issues/103509

   (6) https://github.com/python/cpython/issues/93012

   (7) https://github.com/python/cpython/issues/93274

   (8) https://github.com/python/cpython/issues/98586

   (9) https://github.com/python/cpython/issues/93503

   (10) https://github.com/python/cpython/issues/92257

   (11) https://github.com/python/cpython/issues/91052

   (12) https://github.com/python/cpython/issues/91051

   (13) https://github.com/python/cpython/issues/91054

   (14) https://github.com/python/cpython/issues/91248

   (15) https://github.com/python/cpython/issues/101578

   (16) https://github.com/python/cpython/issues/101578

   (17) https://github.com/python/cpython/issues/101578

   (18) https://github.com/python/cpython/issues/102755

   (19) https://peps.python.org/pep-0683/

   (20) https://github.com/python/cpython/issues/84436

   (21) https://peps.python.org/pep-0684/

   (22) https://github.com/python/cpython/issues/104110

   (23) https://github.com/python/cpython/issues/105387


File: python.info,  Node: Porting to Python 3 12<2>,  Next: 已棄用<2>,  Prev: 新增特性<2>,  Up: C API 變更

1.2.14.2 Porting to 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 *note PyArg_ParseTuple(): 517.
     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 *note PyTypeObject.tp_subclasses: 518. 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 *note
     __subclasses__(): 519. (using *note PyObject_CallMethod(): 366, 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 *note
     PyUnicode_FromFormat(): 33f. and *note PyUnicode_FromFormatV():
     51a.  (Contributed by Serhiy Storchaka in gh-98836(1).)

   * An unrecognized format character in *note PyUnicode_FromFormat():
     33f. and *note PyUnicode_FromFormatV(): 51a. now sets a *note
     SystemError: 51b.  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(2).)

   * Fix wrong sign placement in *note PyUnicode_FromFormat(): 33f. and
     *note PyUnicode_FromFormatV(): 51a.  (Contributed by Philip Georgi
     in gh-95504(3).)

   * Extension classes wanting to add a ‘__dict__’ or weak reference
     slot should use *note Py_TPFLAGS_MANAGED_DICT: 31b. and *note
     Py_TPFLAGS_MANAGED_WEAKREF: 500. 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(4)), and performance may be worse.
     Classes declaring *note Py_TPFLAGS_MANAGED_DICT: 31b. must call
     ‘_PyObject_VisitManagedDict()’ and ‘_PyObject_ClearManagedDict()’
     to traverse and clear their instance's dictionaries.  To clear
     weakrefs, call *note PyObject_ClearWeakRefs(): 51c, as before.

   * The *note PyUnicode_FSDecoder(): 51d. function no longer accepts
     bytes-like paths, like *note bytearray: 4e3. and *note memoryview:
     40f. types: only the exact *note bytes: 1a5. type is accepted for
     bytes strings.  (Contributed by Victor Stinner in gh-98393(5).)

   * The *note Py_CLEAR: 51e, *note Py_SETREF: 51f. and *note
     Py_XSETREF: 520. 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(6).)

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

   * ‘_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:

        * *note PyType_FromSpec(): 523.

        * *note PyType_FromSpecWithBases(): 524.

        * *note PyType_FromModuleAndSpec(): 4f7.

     Creating classes whose metaclass overrides *note tp_new: 525. 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 *note PyType_FromMetaclass(): 4f6. (added in Python 3.12)
     already disallows creating classes whose metaclass overrides
     ‘tp_new’ (*note __new__(): 526. 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 *note
               tp_init: 527. instead.

             - If the metaclass doesn't need to be instantiated from
               Python, set its ‘tp_new’ to ‘NULL’ using the *note
               Py_TPFLAGS_DISALLOW_INSTANTIATION: 528. 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
          *note calling: 529. the metaclass.

        - If you 'know' the ‘tp_new’ can be skipped safely, filter the
          deprecation warning out using *note warnings.catch_warnings():
          52a. from Python.

   * *note PyOS_InputHook: 52b. and *note PyOS_ReadlineFunctionPointer:
     52c. are no longer called in *note subinterpreters: 52d.  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(8) for more info.

   * *note PyLongObject: 52e. has had its internals changed for better
     performance.  Although the internals of *note PyLongObject: 52e.
     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 *note PyLongObject: 52e.s which fit into a single machine
     word:

        * *note PyUnstable_Long_IsCompact(): 52f.

        * *note PyUnstable_Long_CompactValue(): 530.

   * Custom allocators, set via *note PyMem_SetAllocator(): 531, 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’.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/98836

   (2) https://github.com/python/cpython/issues/95781

   (3) https://github.com/python/cpython/issues/95504

   (4) https://github.com/python/cpython/issues/95589

   (5) https://github.com/python/cpython/issues/98393

   (6) https://github.com/python/cpython/issues/98724

   (7) https://github.com/python/cpython/issues/101578

   (8) https://github.com/python/cpython/issues/104668


File: python.info,  Node: 已棄用<2>,  Next: 已移除<2>,  Prev: Porting to Python 3 12<2>,  Up: C API 變更

1.2.14.3 已棄用
...............

   * In accordance with PEP 699(1), the ‘ma_version_tag’ field in *note
     PyDictObject: 38c. 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(2).  PEP by Ken Jin.)

   * 棄用全域配置變數：

        * *note Py_DebugFlag: 391.: 請改用 *note PyConfig.parser_debug:
          392.

        * *note Py_VerboseFlag: 393.: 請改用 *note PyConfig.verbose:
          394.

        * *note Py_QuietFlag: 395.: 請改用 *note PyConfig.quiet: 396.

        * *note Py_InteractiveFlag: 397.: 請改用 *note
          PyConfig.interactive: 398.

        * *note Py_InspectFlag: 399.: 請改用 *note PyConfig.inspect:
          39a.

        * *note Py_OptimizeFlag: 39b.: 請改用 *note
          PyConfig.optimization_level: 39c.

        * *note Py_NoSiteFlag: 39d.: 請改用 *note PyConfig.site_import:
          39e.

        * *note Py_BytesWarningFlag: 39f.: 請改用 *note
          PyConfig.bytes_warning: 3a0.

        * *note Py_FrozenFlag: 3a1.: 請改用 *note
          PyConfig.pathconfig_warnings: 3a2.

        * *note Py_IgnoreEnvironmentFlag: 3a3.: 請改用 *note
          PyConfig.use_environment: 3a4.

        * *note Py_DontWriteBytecodeFlag: 3a5.: 請改用 *note
          PyConfig.write_bytecode: 3a6.

        * *note Py_NoUserSiteDirectory: 3a7.: 請改用 *note
          PyConfig.user_site_directory: 3a8.

        * *note Py_UnbufferedStdioFlag: 3a9.: 請改用 *note
          PyConfig.buffered_stdio: 3aa.

        * *note Py_HashRandomizationFlag: 3ab.: 請改用 *note
          PyConfig.use_hash_seed: 3ac. 和 *note PyConfig.hash_seed: 3ad.

        * *note Py_IsolatedFlag: 3ae.: 請改用 *note PyConfig.isolated:
          3af.

        * *note Py_LegacyWindowsFSEncodingFlag: 3b0.: 請改用 *note
          PyPreConfig.legacy_windows_fs_encoding: 3b1.

        * *note Py_LegacyWindowsStdioFlag: 3b2.: 請改用 *note
          PyConfig.legacy_windows_stdio: 36f.

        * ‘Py_FileSystemDefaultEncoding’: 請改用 *note
          PyConfig.filesystem_encoding: 3b3.

        * ‘Py_HasFileSystemDefaultEncoding’: 請改用 *note
          PyConfig.filesystem_encoding: 3b3.

        * ‘Py_FileSystemDefaultEncodeErrors’: 請改用 *note
          PyConfig.filesystem_errors: 3b4.

        * ‘Py_UTF8Mode’: 請改用 *note PyPreConfig.utf8_mode: 3b5.（參見
          *note Py_PreInitialize(): 3b6.）

     *note Py_InitializeFromConfig(): 390. API 應改為與 *note PyConfig:
     371. 一起使用。（由 Victor Stinner 於 gh-77782(3) 中貢獻。）

   * Creating *note immutable types: 38d. with mutable bases is
     deprecated and will be disabled in Python 3.14.  (gh-95388(4))

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

     Its contents are now available just by including ‘Python.h’, with a
     ‘Py’ prefix added if it was missing:

        - *note PyMemberDef: 4f5.、*note PyMember_GetOne(): 533. 和
          *note PyMember_SetOne(): 534.

        - Type macros like *note Py_T_INT: 535, *note Py_T_DOUBLE: 536,
          etc.  (previously ‘T_INT’, ‘T_DOUBLE’, etc.)

        - *note Py_READONLY: 537.（先前為 ‘READONLY’）和 *note
          Py_AUDIT_READ: 538.（先前全大寫）旗標

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

        - *note T_OBJECT: 539.（請改用 *note Py_T_OBJECT_EX: 53a.）

        - *note T_NONE: 53b.（先前未記錄於文件上，且相當古怪）

        - 不做任何事的巨集 ‘WRITE_RESTRICTED’。

        - ‘RESTRICTED’ 和 ‘READ_RESTRICTED’ 這兩個巨集，相當於 *note
          Py_AUDIT_READ: 538.。

        - 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.

     (Contributed in gh-47146(5) by Petr Viktorin, based on earlier work
     by Alexander Belopolsky and Matthias Braun.)

   * *note PyErr_Fetch(): 3bb. and *note PyErr_Restore(): 3be. are
     deprecated.  Use *note PyErr_GetRaisedException(): 3bc. and *note
     PyErr_SetRaisedException(): 3bf. instead.  (Contributed by Mark
     Shannon in gh-101578(6).)

   * ‘PyErr_Display()’ 已棄用，請改用 *note PyErr_DisplayException():
     3ca.。（由 Irit Katriel 於 gh-102755(7) 中貢獻。）

   * ‘_PyErr_ChainExceptions’ 已棄用，請改用 ‘_PyErr_ChainExceptions1’。
     （由 Irit Katriel 於 gh-102192(8) 中貢獻。）

   * Using *note PyType_FromSpec(): 523, *note
     PyType_FromSpecWithBases(): 524. or *note
     PyType_FromModuleAndSpec(): 4f7. to create a class whose metaclass
     overrides *note tp_new: 525. is deprecated.  Call the metaclass
     instead.

* Menu:

* Python 3.14 中待移除的項目: Python 3 14 中待移除的項目<2>.
* Python 3.15 中待移除的項目: Python 3 15 中待移除的項目<2>.
* 未來版本中的待移除項目: 未來版本中的待移除項目<2>.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0699/

   (2) https://github.com/python/cpython/issues/101193

   (3) https://github.com/python/cpython/issues/77782

   (4) https://github.com/python/cpython/issues/95388

   (5) https://github.com/python/cpython/issues/47146

   (6) https://github.com/python/cpython/issues/101578

   (7) https://github.com/python/cpython/issues/102755

   (8) https://github.com/python/cpython/issues/102192


File: python.info,  Node: Python 3 14 中待移除的項目<2>,  Next: Python 3 15 中待移除的項目<2>,  Up: 已棄用<2>

1.2.14.4 Python 3.14 中待移除的項目
...................................

   * *note PyDictObject: 38c. 中的 ‘ma_version_tag’ 欄位，用於擴充模組 (
     PEP 699(1)；gh-101193(2))。

   * 使用可變基底建立*note 不可變型別: 38d. (gh-95388(3))。

   * 設定 Python 初始化的函式，Python 3.11 中已被棄用：

        * ‘PySys_SetArgvEx()’：請改以 *note PyConfig.argv: 38e. 設定。

        * ‘PySys_SetArgv()’：請改以 *note PyConfig.argv: 38e. 設定。

        * ‘Py_SetProgramName()’：請改以 *note PyConfig.program_name:
          38f. 設定。

        * ‘Py_SetPythonHome()’：請改以 *note PyConfig.home: 386. 設定。

     *note Py_InitializeFromConfig(): 390. API 應該與 *note PyConfig:
     371. 一起使用。

   * 全域設定變數：

        * *note Py_DebugFlag: 391.：請改用 *note PyConfig.parser_debug:
          392.。

        * *note Py_VerboseFlag: 393.：請改用 *note PyConfig.verbose:
          394.。

        * *note Py_QuietFlag: 395.：請改用 *note PyConfig.quiet: 396.。

        * *note Py_InteractiveFlag: 397.：請改用 *note
          PyConfig.interactive: 398.。

        * *note Py_InspectFlag: 399.：請改用 *note PyConfig.inspect:
          39a.。

        * *note Py_OptimizeFlag: 39b.：請改用 *note
          PyConfig.optimization_level: 39c.。

        * *note Py_NoSiteFlag: 39d.：請改用 *note PyConfig.site_import:
          39e.。

        * *note Py_BytesWarningFlag: 39f.：請改用 *note
          PyConfig.bytes_warning: 3a0.。

        * *note Py_FrozenFlag: 3a1.：請改用 *note
          PyConfig.pathconfig_warnings: 3a2.。

        * *note Py_IgnoreEnvironmentFlag: 3a3.：請改用 *note
          PyConfig.use_environment: 3a4.。

        * *note Py_DontWriteBytecodeFlag: 3a5.：請改用 *note
          PyConfig.write_bytecode: 3a6.。

        * *note Py_NoUserSiteDirectory: 3a7.：請改用 *note
          PyConfig.user_site_directory: 3a8.。

        * *note Py_UnbufferedStdioFlag: 3a9.：請改用 *note
          PyConfig.buffered_stdio: 3aa.。

        * *note Py_HashRandomizationFlag: 3ab.：請改用 *note
          PyConfig.use_hash_seed: 3ac. 和 *note PyConfig.hash_seed:
          3ad.。

        * *note Py_IsolatedFlag: 3ae.：請改用 *note PyConfig.isolated:
          3af.。

        * *note Py_LegacyWindowsFSEncodingFlag: 3b0.：請改用 *note
          PyPreConfig.legacy_windows_fs_encoding: 3b1.。

        * *note Py_LegacyWindowsStdioFlag: 3b2.：請改用 *note
          PyConfig.legacy_windows_stdio: 36f.。

        * ‘Py_FileSystemDefaultEncoding’：請改用 *note
          PyConfig.filesystem_encoding: 3b3.。

        * ‘Py_HasFileSystemDefaultEncoding’：請改用 *note
          PyConfig.filesystem_encoding: 3b3.。

        * ‘Py_FileSystemDefaultEncodeErrors’：請改用 *note
          PyConfig.filesystem_errors: 3b4.。

        * ‘Py_UTF8Mode’：請改用 *note PyPreConfig.utf8_mode: 3b5.。（請
          見 *note Py_PreInitialize(): 3b6.）

     *note Py_InitializeFromConfig(): 390. API 應該與 *note PyConfig:
     371. 一起使用。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0699/

   (2) https://github.com/python/cpython/issues/101193

   (3) https://github.com/python/cpython/issues/95388


File: python.info,  Node: Python 3 15 中待移除的項目<2>,  Next: 未來版本中的待移除項目<2>,  Prev: Python 3 14 中待移除的項目<2>,  Up: 已棄用<2>

1.2.14.5 Python 3.15 中待移除的項目
...................................

   * ‘libmpdecimal’ 的打包副本 (bundled copy)。

   * *note PyImport_ImportModuleNoBlock(): 388.：請改用 *note
     PyImport_ImportModule(): 389.。

   * *note PyWeakref_GET_OBJECT(): 38a.: use *note PyWeakref_GetRef():
     2f0. instead.

   * *note PyWeakref_GetObject(): 2f1.: use *note PyWeakref_GetRef():
     2f0. instead.

   * ‘Py_UNICODE_WIDE’ type：請改用 ‘wchar_t’。

   * *note Py_UNICODE: 3b8. type：請改用 ‘wchar_t’。

   * Python 初始化函式：

        * *note PySys_ResetWarnOptions(): 37a.：請改為清除 *note
          sys.warnoptions: 37b. 和 ‘warnings.filters’。

        * *note Py_GetExecPrefix(): 37c.：請改用 *note sys.exec_prefix:
          37d.。

        * *note Py_GetPath(): 37e.：請改用 *note sys.path: 37f.。

        * *note Py_GetPrefix(): 380.：請改用 *note sys.prefix: 381.。

        * *note Py_GetProgramFullPath(): 382.：請改用 *note
          sys.executable: 383.。

        * *note Py_GetProgramName(): 384.：請改用 *note sys.executable:
          383.。

        * *note Py_GetPythonHome(): 385.：請改用 *note PyConfig.home:
          386. 或 *note PYTHONHOME: 387. 環境變數。


File: python.info,  Node: 未來版本中的待移除項目<2>,  Prev: Python 3 15 中待移除的項目<2>,  Up: 已棄用<2>

1.2.14.6 未來版本中的待移除項目
...............................

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

   * *note Py_TPFLAGS_HAVE_FINALIZE: 3ba.：自 Python 3.8 起不再需要

   * *note PyErr_Fetch(): 3bb.：請改用 *note PyErr_GetRaisedException():
     3bc.。

   * *note PyErr_NormalizeException(): 3bd.：請改用 *note
     PyErr_GetRaisedException(): 3bc.。

   * *note PyErr_Restore(): 3be.：請改用 *note
     PyErr_SetRaisedException(): 3bf.。

   * *note PyModule_GetFilename(): 3c0.：請改用 *note
     PyModule_GetFilenameObject(): 3c1.。

   * *note PyOS_AfterFork(): 3c2.：請改用 *note PyOS_AfterFork_Child():
     3c3.。

   * *note PySlice_GetIndicesEx(): 3c4.：請改用 *note PySlice_Unpack():
     3c5. 和 *note PySlice_AdjustIndices(): 3c6.。

   * ‘PyUnicode_AsDecodedObject()’：請改用 *note PyCodec_Decode(): 3c7.。

   * ‘PyUnicode_AsDecodedUnicode()’：請改用 *note PyCodec_Decode():
     3c7.。

   * ‘PyUnicode_AsEncodedObject()’：請改用 *note PyCodec_Encode(): 3c8.。

   * ‘PyUnicode_AsEncodedUnicode()’：請改用 *note PyCodec_Encode():
     3c8.。

   * *note PyUnicode_READY(): 3c9.：自 Python 3.12 起不再需要

   * ‘PyErr_Display()’：請改用 *note PyErr_DisplayException(): 3ca.。

   * ‘_PyErr_ChainExceptions()’：請改用 ‘_PyErr_ChainExceptions1’。

   * ‘PyBytesObject.ob_shash’ 成員：請改為呼叫 *note PyObject_Hash():
     3cb.。

   * ‘PyDictObject.ma_version_tag’ 成員。

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

        * *note PyThread_create_key(): 3cc.：請改用 *note
          PyThread_tss_alloc(): 3cd.。

        * *note PyThread_delete_key(): 3ce.：請改用 *note
          PyThread_tss_free(): 3cf.。

        * *note PyThread_set_key_value(): 3d0.：請改用 *note
          PyThread_tss_set(): 3d1.。

        * *note PyThread_get_key_value(): 3d2.：請改用 *note
          PyThread_tss_get(): 3d3.。

        * *note PyThread_delete_key_value(): 3d4.：請改用 *note
          PyThread_tss_delete(): 3d5.。

        * *note PyThread_ReInitTLS(): 3d6.：自 Python 3.7 起不再需要。


File: python.info,  Node: 已移除<2>,  Prev: 已棄用<2>,  Up: C API 變更

1.2.14.7 已移除
...............

   * Remove the ‘token.h’ header file.  There was never any public
     tokenizer C API. The ‘token.h’ header file was only designed to be
     used by Python internals.  (Contributed by Victor Stinner in
     gh-92651(1).)

   * Legacy Unicode APIs have been removed.  See PEP 623(2) 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(3) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/92651

   (2) https://peps.python.org/pep-0623/

   (3) https://github.com/python/cpython/issues/85858


File: python.info,  Node: Python 3 11 有什麼新功能,  Next: Python 3 10 有什麼新功能,  Prev: Python 3 12 有什麼新功能,  Up: Python 有什麼新功能？

1.3 Python 3.11 有什麼新功能
============================


編輯者: Pablo Galindo Salgado

此文章解釋了 Python 3.11 和 3.10 相比多了哪些新特性。Python 3.11 於 2022
年 10 月 24 日發布。完整細節請見 *note Changelog（更動日誌）: 122.。

* Menu:

* 發布重點摘要: 發布重點摘要<2>.
* 新增特性: 新增特性<3>.
* 型別提示相關的新特性::
* 其他語言更動: 其他語言更動<2>.
* 其他 CPython 實作更動::
* 新增模組: 新增模組<2>.
* 改進的模組: 改進的模組<2>.
* 最佳化: 最佳化<2>.
* 更快的 CPython::
* CPython 位元組碼變更: CPython 位元組碼變更<2>.
* 已棄用: 已棄用<3>.
* Python 3.12 中待決議的移除項目: Python 3 12 中待決議的移除項目.
* 已移除: 已移除<3>.
* 移植至 Python 3.11: 移植至 Python 3 11.
* 建置變更: 建置變更<2>.
* C API 變更: C API 變更<2>.
* Notable changes in 3.11.4: Notable changes in 3 11 4.
* Notable changes in 3.11.5: Notable changes in 3 11 5.


File: python.info,  Node: 發布重點摘要<2>,  Next: 新增特性<3>,  Up: Python 3 11 有什麼新功能

1.3.1 發布重點摘要
------------------

   * Python 3.11 比 Python 3.10 快了 10-60%。我們使用了標準基準量測套裝
     軟體 (benchmark suite) 測得平均加速了 1.25x。細節請見*note 更快的
     CPython: 544.。

新增語法特性：

   * *note PEP 654：例外群組與 except*: 545.

新增內建特性：

   * *note PEP 678：運用例外註解使其更加詳盡: 546.

新增標準函式庫模組：

   * PEP 680(1)：*note tomllib: e5. — 在標準函式庫中支援 TOML(2) 檔案的
     剖析

直譯器的改進：

   * *note PEP 657：回溯 (traceback) 中更細緻的錯誤位置: 547.

   * 新增 *note -P: 548. 命令列選項和 *note PYTHONSAFEPATH: 549. 環境變
     數以停用自動於 *note sys.path: 37f. 的開頭*note
     加上一個有潛在安全問題的路徑: 54a.

新增型別特性：

   * *note PEP 646：可變參數泛型 (variadic generics): 54b.

   * *note PEP 655：標記獨立 TypedDict 項目為必要或不必要: 54c.

   * *note PEP 673：Self 型別: 54d.

   * *note PEP 675：任意的文本字串型別 (Arbitrary literal string type):
     54e.

   * *note PEP 681：資料類別轉換 (Data class transforms): 54f.

重要的棄用、移除與限制：

   * PEP 594(3)：*note 許多標準函式庫中的遺留模組已被棄用: 550.且將於
     Python 3.13 移除

   * PEP 624(4)：*note Py_UNICODE 編碼器 API 已被移除: 551.

   * PEP 670(5)：*note 轉換為靜態行內函式的巨集: 552.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0680/

   (2) https://toml.io/

   (3) https://peps.python.org/pep-0594/

   (4) https://peps.python.org/pep-0624/

   (5) https://peps.python.org/pep-0670/


File: python.info,  Node: 新增特性<3>,  Next: 型別提示相關的新特性,  Prev: 發布重點摘要<2>,  Up: Python 3 11 有什麼新功能

1.3.2 新增特性
--------------

* Menu:

* PEP 657：回溯 (traceback) 中更細緻的錯誤位置: PEP 657：回溯 traceback 中更細緻的錯誤位置.
* PEP 654：例外群組與 except*::
* PEP 678：運用例外註解使其更加詳盡::
* Windows py.exe 啟動程式 (launcher) 的改進: Windows py exe 啟動程式 launcher 的改進.


File: python.info,  Node: PEP 657：回溯 traceback 中更細緻的錯誤位置,  Next: PEP 654：例外群組與 except*,  Up: 新增特性<3>

1.3.2.1 PEP 657：回溯 (traceback) 中更細緻的錯誤位置
....................................................

當要印出回溯，直譯器現在會指出造成錯誤的確切運算式，而非只說明是哪一行。
例如：

     Traceback (most recent call last):
       File "distance.py", line 11, in <module>
         print(manhattan_distance(p1, p2))
               ^^^^^^^^^^^^^^^^^^^^^^^^^^
       File "distance.py", line 6, in manhattan_distance
         return abs(point_1.x - point_2.x) + abs(point_1.y - point_2.y)
                                ^^^^^^^^^
     AttributeError: 'NoneType' object has no attribute 'x'

前一版本的直譯器只會標明是哪一行，無法辨認哪一個物件是 ‘None’。當處理多
層的巢狀 *note dict: 23b. 物件和多個函式呼叫時，這種強化錯誤提示也可能非
常有用：

     Traceback (most recent call last):
       File "query.py", line 37, in <module>
         magic_arithmetic('foo')
       File "query.py", line 18, in magic_arithmetic
         return add_counts(x) / 25
                ^^^^^^^^^^^^^
       File "query.py", line 24, in add_counts
         return 25 + query_user(user1) + query_user(user2)
                     ^^^^^^^^^^^^^^^^^
       File "query.py", line 32, in query_user
         return 1 + query_count(db, response['a']['b']['c']['user'], retry=True)
                                    ~~~~~~~~~~~~~~~~~~^^^^^
     TypeError: 'NoneType' object is not subscriptable

在複雜的計算運算式中也是：

     Traceback (most recent call last):
       File "calculation.py", line 54, in <module>
         result = (x / y / z) * (a / b / c)
                   ~~~~~~^~~
     ZeroDivisionError: division by zero

此外，強化回溯特性所使用的資訊可以透過一般的 API 來取得，以用來使 *note
bytecode: 16d. *note 指示 (instruction): 556.與原始碼位置相互關聯。此項
資訊可以用以下方式取得：

   - Python 中的 *note codeobject.co_positions(): 557. 方法。

   - C API 中的 *note PyCode_Addr2Location(): 558. 函式。

詳情請見 PEP 657(1)。（由 Pablo Galindo、Batuhan Taskaya 與 Ammar Askar
於 bpo-43950(2) 中所貢獻。）

     備註: 這個特性必須要將欄的位置 (column position) 儲存於 *note
     程式碼物件: 559.，這可能會導致直譯器用於編譯 Python 檔案的記憶體使
     用量與硬碟使用量增加。為了避免儲存多餘的資訊且停用印出多餘的回溯資
     訊，請用 *note -X no_debug_ranges: 15a. 命令列選項或是 *note
     PYTHONNODEBUGRANGES: 55a. 環境變數。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0657/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43950


File: python.info,  Node: PEP 654：例外群組與 except*,  Next: PEP 678：運用例外註解使其更加詳盡,  Prev: PEP 657：回溯 traceback 中更細緻的錯誤位置,  Up: 新增特性<3>

1.3.2.2 PEP 654：例外群組與 ‘except*’
.....................................

PEP 654(1) 引入了新的的語言特性，可讓程式同時引發並處理多個相互無關的例
外。內建型別 *note ExceptionGroup: 19c. 和 *note BaseExceptionGroup:
244. 使得程式可為多個例外組成群組並同時引發，新的 *note except*: 55c. 語
法也將 *note except: 171. 泛用化、能夠比對例外群組的子群組。

詳情請見 PEP 654(2)。

（由 Irit Katriel 於 bpo-45292(3) 中所貢獻。PEP 由 Irit Katriel、Yury
Selivanov 與 Guido van Rossum 撰寫。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0654/

   (2) https://peps.python.org/pep-0654/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=45292


File: python.info,  Node: PEP 678：運用例外註解使其更加詳盡,  Next: Windows py exe 啟動程式 launcher 的改進,  Prev: PEP 654：例外群組與 except*,  Up: 新增特性<3>

1.3.2.3 PEP 678：運用例外註解使其更加詳盡
.........................................

新增 *note add_note(): 55e. 方法到 *note BaseException: 55f.。當上下文資
訊在例外被引發時無法被取得，這個方法就可以用來為例外添加更多資訊。被添加
的註解會在預設回溯中出現。

詳情請見 PEP 678(1)。

（由 Irit Katriel 於 bpo-45607(2) 中所貢獻。PEP 由 Zac Hatfield-Dodds 所
撰寫）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0678/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=45607


File: python.info,  Node: Windows py exe 啟動程式 launcher 的改進,  Prev: PEP 678：運用例外註解使其更加詳盡,  Up: 新增特性<3>

1.3.2.4 Windows ‘py.exe’ 啟動程式 (launcher) 的改進
...................................................

Python 3.11 所包含的 *note Python Launcher for Windows: 562. 複製品有了
顯著的改善。它現在支援 PEP 514(1) 所定義的公司/標籤 (tag) 語法，可用
‘-V:<COMPANY>/<TAG>’ 引數來取代受限的 ‘-<MAJOR>.<MINOR>’。這允許了
python.org(2) 上的 ‘PythonCore’ 以外的發行版本發布。

使用 ‘-V:’ 選擇器時，可以省略公司或標籤，但會搜索所有安裝。例如，
‘-V:OtherPython/’ 將選擇 ‘OtherPython’ 註冊的「最佳」標籤，而 ‘-V:3.11’
或 ‘-V:/3.11’ 將選擇帶有 ‘3.11’ 標籤的「最佳」發行版。

當使用遺留的 ‘-<MAJOR>’、‘-<MAJOR>.<MINOR>’、‘-<MAJOR>-<BITNESS>’ 或
‘-<MAJOR>.<MINOR>-<BITNESS>’ 引數時，所有過去版本的行為都應該保留下來，
且只有 ‘PythonCore’ 中的發布版本會被選用。然而，‘-64’ 後綴現在暗示了「非
32-bit」（不用一定要是 x86-64），因為現在有多個支援 64-bit 的平台。
32-bit 運行程式會在檢查運行程式之標籤是否帶有 ‘-32’ 後綴時被偵測出來。所
有 Python 3.5 以後發布版本的 32-bit 建置中都有這個行為。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0514/

   (2) https://www.python.org


File: python.info,  Node: 型別提示相關的新特性,  Next: 其他語言更動<2>,  Prev: 新增特性<3>,  Up: Python 3 11 有什麼新功能

1.3.3 型別提示相關的新特性
--------------------------

這個部分涵蓋影響 PEP 484(1) 型別提示 (type hints) 與 *note typing: ed. 模
組的重大變更。

* Menu:

* PEP 646：可變參數泛型 (variadic generics): PEP 646：可變參數泛型 variadic generics.
* PEP 655：標記獨立 TypedDict 項目為必要或不必要::
* PEP 673：Self 型別::
* PEP 675：任意的文本字串型別 (Arbitrary literal string type): PEP 675：任意的文本字串型別 Arbitrary literal string type.
* PEP 681：資料類別轉換 (Data class transforms): PEP 681：資料類別轉換 Data class transforms.
* PEP 563 可能不是未來::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0484/


File: python.info,  Node: PEP 646：可變參數泛型 variadic generics,  Next: PEP 655：標記獨立 TypedDict 項目為必要或不必要,  Up: 型別提示相關的新特性

1.3.3.1 PEP 646：可變參數泛型 (variadic generics)
.................................................

PEP 484(1) 先前引入了 *note TypeVar: 141.，開啟了帶有單一型別的泛型參數
化。 PEP 646(2) 新增 *note TypeVarTuple: 143.，開啟了帶有'任意'數量型別
的參數化 (parameterisation)。換句話說，*note TypeVarTuple: 143. 是'可變
的'型別變數，啟用了'可變的'泛型。

這使其有非常多用例，特別是它允許了像是 NumPy 和 Tensorflow 的數值運算函
式庫中類似陣列結構的型別可用 'shape' 陣列來被參數化。靜態型別檢查工具現
在也能夠為使用這些函式庫的程式捕捉到維度相關的錯誤。

詳情請見 PEP 646(3)。

（由 Matthew Rahtz 於 bpo-43224(4) 中所貢獻，由 Serhiy Storchaka 與
Jelle Zijlstra 協助。PEP 由 Mark Mendoza、Matthew Rahtz、Pradeep Kumar
Srinivasan 與 Vincent Siles 所撰寫）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0484/

   (2) https://peps.python.org/pep-0646/

   (3) https://peps.python.org/pep-0646/

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43224


File: python.info,  Node: PEP 655：標記獨立 TypedDict 項目為必要或不必要,  Next: PEP 673：Self 型別,  Prev: PEP 646：可變參數泛型 variadic generics,  Up: 型別提示相關的新特性

1.3.3.2 PEP 655：標記獨立 ‘TypedDict’ 項目為必要或不必要
........................................................

*note Required: 568. 與 *note NotRequired: 569. 提供了標記一個獨立項目在
*note TypedDict: 146. 中是否必須存在的直覺方法。在這之前，這只有透過繼承
才有可能做得到。

所有欄位都預設為是必要的，除非 'total' 參數有被設為 ‘False’，那麼所有欄
位就會是非必要的。例如，這個範例指定了要有一個必要鍵與一個非必要鍵的
‘TypedDict’：

     class Movie(TypedDict):
        title: str
        year: NotRequired[int]

     m1: Movie = {"title": "Black Panther", "year": 2018}  # OK
     m2: Movie = {"title": "Star Wars"}  # OK (year is not required)
     m3: Movie = {"year": 2022}  # ERROR (missing required field title)

以下定義等同於：

     class Movie(TypedDict, total=False):
        title: Required[str]
        year: int

詳情請見 PEP 655(1)。

（由 David Foster 與 Jelle Zijlstra 於 bpo-47087(2) 中所貢獻。PEP 由
David Foster 所撰寫）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0655/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=47087


File: python.info,  Node: PEP 673：Self 型別,  Next: PEP 675：任意的文本字串型別 Arbitrary literal string type,  Prev: PEP 655：標記獨立 TypedDict 項目為必要或不必要,  Up: 型別提示相關的新特性

1.3.3.3 PEP 673：‘Self’ 型別
............................

新的 *note Self: 56b. 標註提供了一種簡單直觀的方法來標註那些會回傳其類別
實例的方法。這與 PEP 484(1) 中指定的基於 *note TypeVar: 141. 的方法相同
，但更簡潔且更易於遵循。

常見用例包括作為 *note classmethod: 14a. 的替代建構函式和會回傳 ‘self’ 的
*note __enter__(): 56c. 方法：

     class MyLock:
         def __enter__(self) -> Self:
             self.lock()
             return self

         ...

     class MyInt:
         @classmethod
         def fromhex(cls, s: str) -> Self:
             return cls(int(s, 16))

         ...

*note Self: 56b. 也可用於標註與其封閉類類別 (enclosing class) 相同的方法
參數或屬性。

詳情請見 PEP 673(2)。

（由 James Hilton-Balfe 於 bpo-46534(3) 中所貢獻。PEP 由 Pradeep Kumar
Srinivasan 與 James Hilton-Balfe 所撰寫）

   ---------- Footnotes ----------

   (1) 
https://peps.python.org/pep-0484/#annotating-instance-and-class-methods

   (2) https://peps.python.org/pep-0673/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=46534


File: python.info,  Node: PEP 675：任意的文本字串型別 Arbitrary literal string type,  Next: PEP 681：資料類別轉換 Data class transforms,  Prev: PEP 673：Self 型別,  Up: 型別提示相關的新特性

1.3.3.4 PEP 675：任意的文本字串型別 (Arbitrary literal string type)
...................................................................

新的 *note LiteralString: 56e. 標註可用於標示一個函式參數可為任何文本字
串型別 (literal string type)。這允許函式接受任意的文本字串型別，以及從其
他文本字串建立的字串。型別檢查器就可以強制需審慎處理的函式（例如會執行
SQL 陳述式或 shell 命令的函式）僅會以靜態引數呼叫，從而提供針對注入攻擊
的保護。

例如一個 SQL 查詢函式 (query function) 可以被標註為：

     def run_query(sql: LiteralString) -> ...
         ...

     def caller(
         arbitrary_string: str,
         query_string: LiteralString,
         table_name: LiteralString,
     ) -> None:
         run_query("SELECT * FROM students")       # ok
         run_query(query_string)                   # ok
         run_query("SELECT * FROM " + table_name)  # ok
         run_query(arbitrary_string)               # type checker error
         run_query(                                # type checker error
             f"SELECT * FROM students WHERE name = {arbitrary_string}"
         )

詳情請見 PEP 675(1)。

（由 Jelle Zijlstra 於 bpo-47088(2) 中所貢獻。PEP 由 Pradeep Kumar
Srinivasan 與 Graham Bleaney 所撰寫）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0675/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=47088


File: python.info,  Node: PEP 681：資料類別轉換 Data class transforms,  Next: PEP 563 可能不是未來,  Prev: PEP 675：任意的文本字串型別 Arbitrary literal string type,  Up: 型別提示相關的新特性

1.3.3.5 PEP 681：資料類別轉換 (Data class transforms)
.....................................................

*note dataclass_transform: 47b. 可以用來裝飾一個類別、元類別
(metaclass)、或是一個本身就是裝飾器的函式。‘@dataclass_transform()’ 的存
在會讓一個靜態型別檢查器知道被裝飾物件會在運行程式做出轉換類別的「魔法」
，賦予其類似 *note dataclass: 1af. 的行為。

舉例來說：

     # The create_model decorator is defined by a library.
     @typing.dataclass_transform()
     def create_model(cls: Type[T]) -> Type[T]:
         cls.__init__ = ...
         cls.__eq__ = ...
         cls.__ne__ = ...
         return cls

     # The create_model decorator can now be used to create new model classes:
     @create_model
     class CustomerModel:
         id: int
         name: str

     c = CustomerModel(id=327, name="Eric Idle")

詳情請見 PEP 681(1)。

（由 Jelle Zijlstra 於 gh-91860(2) 中所貢獻。PEP 由 Erik De Bonte 與
Eric Traut 所撰寫）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0681/

   (2) https://github.com/python/cpython/issues/91860


File: python.info,  Node: PEP 563 可能不是未來,  Prev: PEP 681：資料類別轉換 Data class transforms,  Up: 型別提示相關的新特性

1.3.3.6 PEP 563 可能不是未來
............................

PEP 563(1) 標註的推遲求值 (Postponed Evaluation of Annotations)（‘from
__future__ import annotations’ *note future 陳述式: 16f.）最初計劃在
Python 3.10 中發布，但已被無限期擱置。請參閱來自指導委員會 (Steering
Counsil) 的訊息(2)以獲得更多資訊。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0563/

   (2) 
https://mail.python.org/archives/list/python-dev@python.org/message/VIZEBX5EYMSYIJNDBF6DMUMZOCWHARSO/


File: python.info,  Node: 其他語言更動<2>,  Next: 其他 CPython 實作更動,  Prev: 型別提示相關的新特性,  Up: Python 3 11 有什麼新功能

1.3.4 其他語言更動
------------------

   * 星號拆解 (starred unpacking) 運算式現在可以在 *note for: 2c3. 陳述
     式中使用。（詳情請見 bpo-46725(1)。）

   * 非同步*note 綜合運算 (comprehension): 574. 現在允許在*note
     非同步函式中的內部綜合運算 (inside comprehension): 575.。在這種情況
     下，外部綜合運算 (outer comprehension) 隱晦地變成了非同步的了。（由
     Serhiy Storchaka 在 bpo-33346(2) 中貢獻。）

   * 現在在不支援 *note context manager: 576. 協議的物件上使用 *note
     with: 577. 陳述式和 *note contextlib.ExitStack.enter_context():
     578. 或在不支援 *note asynchronous context manager: 579. 協議的物件
     上使用 *note async with: 57a. 陳述式和 *note
     contextlib.AsyncExitStack.enter_async_context(): 57b.，會引發 *note
     TypeError: 4dd. 而不是 *note AttributeError: 2f6.。（由 Serhiy
     Storchaka 在 bpo-12022(3) 和 bpo-44471(4) 中貢獻。）

   * Added *note object.__getstate__(): 57c, which provides the default
     implementation of the ‘__getstate__()’ method.  *note copy: 1e.ing
     and *note pickle: 95.ing instances of subclasses of builtin types
     *note bytearray: 4e3, *note set: 57d, *note frozenset: 57e, *note
     collections.OrderedDict: 57f, *note collections.deque: 580, *note
     weakref.WeakSet: 581, and *note datetime.tzinfo: 582. now copies
     and pickles instance attributes implemented as *note slots: 583.
     This change has an unintended side effect: It trips up a small
     minority of existing Python projects not expecting *note
     object.__getstate__(): 57c. to exist.  See the later comments on
     gh-70766(5) for discussions of what workarounds such code may need.
     (Contributed by Serhiy Storchaka in bpo-26579(6).)

   * 新增了一個 *note -P: 548. 命令列選項和一個 *note PYTHONSAFEPATH:
     549. 環境變數，它們禁用了當使用 *note -c: 584. 和 *note -m: 585. 以
     在運行腳本或當前目錄時自動添加到腳本目錄的 *note sys.path: 37f.。這
     確保只有 stdlib 和已安裝的模組會被 *note import: 586. 取用，以避免
     不小心或被惡意地將模組與本地（通常是使用者可寫入的）目錄中的模組重
     疊。（由 Victor Stinner 在 gh-57684(7) 中貢獻。）

   * ‘"z"’ 選項被新增到 *note 格式規格 (Format Specification) 迷你語言:
     1c8.，它會強迫負的 0 在進位到格式精度後成為正的。更多詳情請見 PEP
     682(8)。（由 John Belmonte 於 gh-90153(9) 中貢獻。）

   * *note sys.path: 37f. 不再接受位元組。支援已在 Python 3.2 和 3.6 之
     間的某個時間停止，直到 Python 3.10.0 發布後才引起人們的注意。此外，
     由於混合使用 *note str: 3f2. 和 *note bytes: 1a5. 鍵時 *note -b:
     587. 和 *note sys.path_importer_cache: 588. 會出現的交互作用，恢復
     這項支援會出現問題。（由 Thomas Grainger 在 gh-91181(10) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46725

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33346

   (3) https://bugs.python.org/issue?@action=redirect&bpo=12022

   (4) https://bugs.python.org/issue?@action=redirect&bpo=44471

   (5) https://github.com/python/cpython/issues/70766

   (6) https://bugs.python.org/issue?@action=redirect&bpo=26579

   (7) https://github.com/python/cpython/issues/57684

   (8) https://peps.python.org/pep-0682/

   (9) https://github.com/python/cpython/issues/90153

   (10) https://github.com/python/cpython/issues/91181


File: python.info,  Node: 其他 CPython 實作更動,  Next: 新增模組<2>,  Prev: 其他語言更動<2>,  Up: Python 3 11 有什麼新功能

1.3.5 其他 CPython 實作更動
---------------------------

   * 為支援 *note typing.SupportsComplex: 58b. 與 *note
     typing.SupportsBytes: 58c. 協定，實作了 *note complex: 2c9. 與
     *note bytes: 1a5. 的特殊方法 *note __complex__(): 58d. 與 *note
     __bytes__(): 58e.。（由 Mark Dickinson 和 Donghee Na 於
     bpo-24234(1) 中所貢獻。）

   * 新增 ‘siphash13’ 以作為內部的雜湊演算法，它有與 ‘siphash24’ 相似的
     安全特性，但是在處理較長的輸入時會更快一些。現在是 *note str: 3f2.、
     *note bytes: 1a5. 和一些其他型別的 *note hash(): 58f. 預設演算法。
     PEP 552(2) *note 基於雜湊的 .pyc 檔案: 590. 現在也使用 ‘siphash13’。
     （由 Inada Naoki 於 bpo-29410(3) 中貢獻。）

   * 當一個仍有效的例外被 *note raise: 591. 陳述式在沒有參數的情況下重新
     引發，被附於該例外的追蹤資訊現在都會是
     ‘sys.exc_info()[1].__traceback__’。這代表對於當前 *note except:
     171. 子句的追蹤上做的改動會反映在被重複引發的例外上。（由 Irit
     Katriel 於 bpo-45711(4) 中貢獻。）

   * 有被處理的例外在直譯器狀態的表示（也就是 ‘exc_info’ 或
     ‘_PyErr_StackItem’）現在只會有 ‘exc_value’ 欄位；‘exc_type’ 和
     ‘exc_traceback’ 已被移除，現在只能透過 ‘exc_value’ 來取得它們。（由
     Irit Katriel 於 bpo-45711(5) 中貢獻。）

   * 新增*note 命令列選項: 592. ‘AppendPath’，已增加於 Windows 安裝程式
     。它的行為類似於 ‘PrependPath’，但在安裝和腳本目錄後面附加而非新增
     於它們前面。（由 Bastian Neuburger 在 bpo-44934(6) 中貢獻。）

   * 初始化中若是要用 *note PyConfig.module_search_paths: 36d. 來初始化
     *note sys.path: 37f.，則現在 *note
     PyConfig.module_search_paths_set: 593. 必須被設為 1。否則，初始化會
     重新計算路徑並取代所有被加到 ‘module_search_paths’ 的值。

   * *note -help: 594. 選項的輸出現在會在 50 列、80 欄的大小之內，*note
     Python 環境變數: 595.和 *note -X: 15a. 選項的資訊現在能夠分別透過
     *note -help-env: 596. 和 *note -help-xoptions: 597. 旗標與 *note
     -help-all: 598. 一起使用來取得。（由 Éric Araujo 於 bpo-46142(7) 中
     貢獻。）

   * 在除 2（binary、二進制）、4、8（octal、八進制）、16（hexadecimal、
     十六進制）或 32 以外的基數中，例如以 10（decimal、十進制）為基數，
     進行 *note int: 23c. 和 *note str: 3f2. 之間的轉換且字串形式的位數
     超過限制，現在會引發 *note ValueError: 1e7.，以避免由於演算法複雜性
     而導致的潛在阻斷服務攻擊 (denial of service attacks)。這是針對
     CVE-2020-10735(8) 的緩解措施，可以透過環境變數、命令列旗標或 *note
     sys: c3. API 來設定或禁用此限制。請參閱*note 整數字串轉換長度限制:
     599. 文件。預設限制為字串形式的 4300 位數字。

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24234

   (2) https://peps.python.org/pep-0552/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=29410

   (4) https://bugs.python.org/issue?@action=redirect&bpo=45711

   (5) https://bugs.python.org/issue?@action=redirect&bpo=45711

   (6) https://bugs.python.org/issue?@action=redirect&bpo=44934

   (7) https://bugs.python.org/issue?@action=redirect&bpo=46142

   (8) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10735


File: python.info,  Node: 新增模組<2>,  Next: 改進的模組<2>,  Prev: 其他 CPython 實作更動,  Up: Python 3 11 有什麼新功能

1.3.6 新增模組
--------------

   * *note tomllib: e5.：用於剖析 TOML(1)。詳情請見 PEP 680(2)。（由
     Taneli Hukkinen 於 bpo-40059(3) 中所貢獻。）

   * *note wsgiref.types: 104.： WSGI(4) 限定型別，用於靜態型別檢查。（
     Sebastian Rittau 於 bpo-42012(5) 中所貢獻。）

   ---------- Footnotes ----------

   (1) https://toml.io/

   (2) https://peps.python.org/pep-0680/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=40059

   (4) https://peps.python.org/pep-3333/

   (5) https://bugs.python.org/issue?@action=redirect&bpo=42012


File: python.info,  Node: 改進的模組<2>,  Next: 最佳化<2>,  Prev: 新增模組<2>,  Up: Python 3 11 有什麼新功能

1.3.7 改進的模組
----------------

* Menu:

* asyncio: asyncio<3>.
* contextlib::
* dataclasses::
* datetime::
* enum: enum<2>.
* fcntl::
* fractions: fractions<3>.
* functools::
* gzip: gzip<2>.
* hashlib: hashlib<2>.
* IDLE 與 idlelib::
* inspect: inspect<2>.
* locale: locale<3>.
* logging::
* math: math<3>.
* operator::
* os: os<3>.
* pathlib: pathlib<4>.
* re: re<3>.
* shutil: shutil<3>.
* socket::
* sqlite3: sqlite3<4>.
* string::
* sys: sys<3>.
* sysconfig::
* tempfile: tempfile<3>.
* threading: threading<2>.
* time: time<2>.
* tkinter: tkinter<3>.
* traceback: traceback<2>.
* typing: typing<4>.
* unicodedata: unicodedata<3>.
* unittest: unittest<4>.
* venv: venv<2>.
* warnings: warnings<2>.
* zipfile::


File: python.info,  Node: asyncio<3>,  Next: contextlib,  Up: 改進的模組<2>

1.3.7.1 asyncio
...............

   * 添加了 *note TaskGroup: 19b. 類別，為一個會持有任務群組並在退出時等
     待全部完成的*note 非同步情境管理器 (asynchronous context manager):
     5a0.。對於新程式碼，建議直接使用 *note create_task(): 5a1. 和 *note
     gather(): 5a2.。（由 Yury Selivanov 和其他人在 gh-90908(1) 中貢獻。
     ）

   * 新增 *note timeout(): 5a3.，是一個用來為一個非同步操作設置超時的非
     同步情境管理器，新的程式建議直接使用它以取代 *note wait_for():
     5a4.。（由 Andrew Svetlov 於 gh-90927(2) 貢獻。）

   * 新增 *note Runner: 5a5. 類別，它會對外公布了 *note run(): 423. 的使
     用機制。（由 Andrew Svetlov 於 gh-91218(3) 貢獻。）

   * 於 asyncio 函式庫的同步化原始物件中新增 *note Barrier: 5a6. 類別與
     和其相關的 *note BrokenBarrierError: 5a7. 例外。（由 Yves Duprat 和
     Andrew Svetlov in gh-87518(4) 貢獻。）

   * 在 *note asyncio.loop.create_connection(): 5a8. 新增關鍵字引數
     'all_errors'，這樣多個連接錯誤就可以一起用一個 *note
     ExceptionGroup: 19c. 來引發。

   * 新增 *note asyncio.StreamWriter.start_tls(): 5a9. 方法，用來將已存
     在的串流連線升級至 TLS。（由 Ian Good 於 bpo-34975(5) 中貢獻。）

   * 在事件迴圈增加原始資料元 (raw datagram) socket 函式：*note
     sock_sendto(): 5aa.、*note sock_recvfrom(): 5ab. 和 *note
     sock_recvfrom_into(): 5ac.。以上在 *note SelectorEventLoop: 5ad. 和
     *note ProactorEventLoop: 5ae. 中都有實作。（由 Alex Grönholm 在
     bpo-46805(6) 中貢獻。）

   * 於 *note Task: 480. 新增 *note cancelling(): 1a0. 和 *note
     uncancel(): 1a1. 方法。這些預期是只用於內部，尤其是 *note
     TaskGroup: 19b.。

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/90908

   (2) https://github.com/python/cpython/issues/90927

   (3) https://github.com/python/cpython/issues/91218

   (4) https://github.com/python/cpython/issues/87518

   (5) https://bugs.python.org/issue?@action=redirect&bpo=34975

   (6) https://bugs.python.org/issue?@action=redirect&bpo=46805


File: python.info,  Node: contextlib,  Next: dataclasses,  Prev: asyncio<3>,  Up: 改進的模組<2>

1.3.7.2 contextlib
..................

   * 添加了非平行安全的 *note chdir(): 5b1. 情境管理器來更改當前工作目錄
     ，然後在退出時恢復它。*note chdir(): 5b2. 的簡單包裝器。（由 Filipe
     Laíns 在 bpo-25625(1) 中貢獻）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25625


File: python.info,  Node: dataclasses,  Next: datetime,  Prev: contextlib,  Up: 改進的模組<2>

1.3.7.3 dataclasses
...................

   * 更改欄位預設的可變性檢查 (mutability check)，僅允許預設值是 *note
     hashable: 5b5. 而不是任何非 *note dict: 23b.、*note list: 5b6. 或
     *note set: 57d. 實例的物件。（由 Eric V. Smith 在 bpo-44674(1) 中貢
     獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=44674


File: python.info,  Node: datetime,  Next: enum<2>,  Prev: dataclasses,  Up: 改進的模組<2>

1.3.7.4 datetime
................

   * 新增 *note datetime.UTC: 496.，一個 *note datetime.timezone.utc:
     5b9. 的方便別名。（由 Kabir Kwatra 於 gh-91973(1) 所貢獻。）

   * *note datetime.date.fromisoformat(): 5ba.、*note
     datetime.time.fromisoformat(): 5bb. 和 *note
     datetime.datetime.fromisoformat(): 5bc. 現在可以用來剖析大部分的
     ISO 8601 格式（除了那些支援分數形式的小時與分鐘）。（由 Paul
     Ganssle 於 gh-80010(2) 中所貢獻。）

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/91973

   (2) https://github.com/python/cpython/issues/80010


File: python.info,  Node: enum<2>,  Next: fcntl,  Prev: datetime,  Up: 改進的模組<2>

1.3.7.5 enum
............

   * ‘EnumMeta’ 更名為 *note EnumType: 5bf.（‘EnumMeta’ 保留為別名）。

   * 增加 *note StrEnum: 5c0.，列舉 (enum) 內的成員必須是字串。

   * 新增 *note ReprEnum: 5c1.，它只修改成員的 *note __repr__(): 5c2.，
     同時回傳成員的文本值 (literal value)（而不是名稱），以用於（為
     *note str(): 3f2.、*note format(): 5c3. 和 *note f-string: 3dc. 所
     使用的）*note __str__(): 5c4. 和 *note __format__(): 5c5.。

   * 改變了 *note Enum.__format__(): 5c6. （被 *note format(): 5c3.、
     *note str.format(): 5c7. 和 *note f-string: 3dc. 預設使用），以使其
     與 *note enum.Enum.__str__: 5c8. 產生相同結果：對於繼承自 *note
     ReprEnum: 5c1. 的列舉，這會是成員之值；而其他的列舉會是列舉與成員名
     稱（例如 ‘Color.RED’）。

   * 新增 'boundary' 類別參數與其選項到 *note Flag: 5c9. 列舉和 *note
     FlagBoundary: 5ca. 列舉以控制處理超出範圍旗標數值的方法。

   * 新增了 *note verify(): 5cb. 列舉裝飾器和 *note EnumCheck: 5cc. 列舉
     及其選項，以根據幾個特定限制檢查列舉類別。

   * 新增 *note member(): 5cd. 與 *note nonmember(): 5ce. 裝飾器以確保被
     裝飾的物件會/不會被轉換成一個列舉成員。

   * 新增 *note property(): 5cf. 裝飾器，它的作用類似 *note property():
     180. 但是是用於列舉，用以替代 *note types.DynamicClassAttribute():
     5d0.。

   * 新增 *note global_enum(): 5d1. 列舉裝飾器，用來調整 *note
     __repr__(): 5c2. 和 *note __str__(): 5c4. 以模組成員形式而非列舉類
     別來顯示值。例如，*note re.RegexFlag: 5d2. 的 *note ASCII: 5d3. 成
     員的 ‘'re.ASCII'’，而非 ‘'RegexFlag.ASCII'’。

   * 強化 *note Flag: 5c9. 以支援使用 *note len(): 5d4.、疊代
     (iteration) 和 *note in: 2c5./*note not in: 5d5. 於其成員。例如，以
     下程式現在能夠作用了：‘len(AFlag(3)) == 2 and list(AFlag(3)) ==
     (AFlag.ONE, AFlag.TWO)’

   * 更改了 *note Enum: 5d6. 和 *note Flag: 5c9. 以在呼叫 *note
     __init_subclass__(): 5d7. 之前就定義成員；*note dir(): 5d8. 現在包
     括來自混合資料型別的方法。

   * 更改 *note Flag: 5c9. 以僅考慮主要值（2 的次方）規範，而複合值（
     ‘3’、‘6’、‘10’ 等）被視為別名；倒置旗標 (inverted flags) 會被強制轉
     換為正等價的值。


File: python.info,  Node: fcntl,  Next: fractions<3>,  Prev: enum<2>,  Up: 改進的模組<2>

1.3.7.6 fcntl
.............

   * FreeBSD 上，‘F_DUP2FD’ 和 ‘F_DUP2FD_CLOEXEC’ 旗標分別有被支援，前者
     等同於 ‘dup2’ 用法，而後者設定了 ‘FD_CLOEXEC’ 旗標。


File: python.info,  Node: fractions<3>,  Next: functools,  Prev: fcntl,  Up: 改進的模組<2>

1.3.7.7 fractions
.................

   * 支援有 PEP 515(1) 風格的 *note Fraction: 1c7. 以字串初始化。（
     Sergey B Kirpichev 於 bpo-44258(2) 中所貢獻。）

   * *note Fraction: 1c7. 現在有實作了一個 ‘__int__’ 方法，因此
     ‘isinstance(some_fraction, typing.SupportsInt)’ 的檢查會通過。（由
     Mark Dickinson 在 bpo-44547(3) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0515/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=44258

   (3) https://bugs.python.org/issue?@action=redirect&bpo=44547


File: python.info,  Node: functools,  Next: gzip<2>,  Prev: fractions<3>,  Up: 改進的模組<2>

1.3.7.8 functools
.................

   * *note functools.singledispatch(): 5df. 現在支援 *note
     types.UnionType: 5e0. 和 *note typing.Union: 5e1. 作為調度
     (dispatch) 引數的標註。

          >>> from functools import singledispatch
          >>> @singledispatch
          ... def fun(arg, verbose=False):
          ...     if verbose:
          ...         print("Let me just say,", end=" ")
          ...     print(arg)
          ...
          >>> @fun.register
          ... def _(arg: int | float, verbose=False):
          ...     if verbose:
          ...         print("Strength in numbers, eh?", end=" ")
          ...     print(arg)
          ...
          >>> from typing import Union
          >>> @fun.register
          ... def _(arg: Union[list, set], verbose=False):
          ...     if verbose:
          ...         print("Enumerate this:")
          ...     for i, elem in enumerate(arg):
          ...         print(i, elem)
          ...

     （由 Yurii Karabas 於 bpo-46014(1) 中所貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46014


File: python.info,  Node: gzip<2>,  Next: hashlib<2>,  Prev: functools,  Up: 改進的模組<2>

1.3.7.9 gzip
............

   * The *note gzip.compress(): 5e4. function is now faster when used
     with the 'mtime=0' argument as it delegates the compression
     entirely to a single *note zlib.compress(): 5e5. operation.  There
     is one side effect of this change: The gzip file header contains an
     "OS" byte in its header.  That was traditionally always set to a
     value of 255 representing "unknown" by the *note gzip: 5d. module.
     Now, when using *note compress(): 5e4. with 'mtime=0', it may be
     set to a different value by the underlying zlib C library Python
     was linked against.  (See gh-112346(1) for details on the side
     effect.)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/112346


File: python.info,  Node: hashlib<2>,  Next: IDLE 與 idlelib,  Prev: gzip<2>,  Up: 改進的模組<2>

1.3.7.10 hashlib
................

   * *note hashlib.blake2b(): 5e8. 與 *note hashlib.blake2s(): 5e9. 現在
     偏好使用 libb2(1) 多於 Python 自發行版的複製。（由 Christian Heimes
     於 bpo-47095(2) 中所貢獻。）

   * 帶有 SHA3 和 SHAKE 演算法的內部 ‘_sha3’ 模組現在使用 'tiny_sha3' 而
     不是 'Keccak 程式碼套件'來減少程式碼和二進位檔案大小。*note
     hashlib: 5e. 模組更喜歡來自 OpenSSL 的 SHA3 和 SHAKE 最佳化實作。此
     更改僅影響沒有 OpenSSL 支援的安裝。（由 Christian Heimes 在
     bpo-47098(3) 中貢獻。）

   * 新增 *note hashlib.file_digest(): 5ea.，是個能夠為檔案或類檔案物件
     做高效率雜湊的幫助函式。（由 Christian Heimes 於 gh-89313(4) 中貢獻
     。）

   ---------- Footnotes ----------

   (1) https://www.blake2.net/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=47095

   (3) https://bugs.python.org/issue?@action=redirect&bpo=47098

   (4) https://github.com/python/cpython/issues/89313


File: python.info,  Node: IDLE 與 idlelib,  Next: inspect<2>,  Prev: hashlib<2>,  Up: 改進的模組<2>

1.3.7.11 IDLE 與 idlelib
........................

   * 在 ‘.pyi’ 檔案施用語法突顯 (syntax highlight)。（由 Alex Waygood 與
     Terry Jan Reedy 於 bpo-45447(1) 中所貢獻。）

   * 當帶有輸入與輸出地儲存 Shell 時，也會包含提示字元。（由 Terry Jan
     Reedy 於 gh-95191(2) 中所貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45447

   (2) https://github.com/python/cpython/issues/95191


File: python.info,  Node: inspect<2>,  Next: locale<3>,  Prev: IDLE 與 idlelib,  Up: 改進的模組<2>

1.3.7.12 inspect
................

   * 添加 *note getmembers_static(): 5ef. 以回傳所有成員，而不會通過描述
     器協議 (descriptor protocol) 觸發動態查找。（由 Weipeng Hong 在
     bpo-30533(1) 中貢獻。）

   * 新增 *note inspect.ismethodwrapper(): 5f0.，用來檢查一個物件的型別
     是否為 *note MethodWrapperType: 5f1.。（由 Hakan Çelik 於
     bpo-29418(2) 中所貢獻。）

   * 更改 *note inspect: 72. 模組中與幀相關的函式以回傳新的 *note
     FrameInfo: 5f2. 和 *note Traceback: 5f3. 類別實例（向後相容之前類似
     於 *note named tuple: 5f4. 的介面），包括擴充的 PEP 657(3) 位置資訊
     （結束行號、欄和結束欄）。受影響的功能是：

        * *note inspect.getframeinfo(): 5f5.

        * *note inspect.getouterframes(): 5f6.

        * *note inspect.getinnerframes(): 5f7,

        * *note inspect.stack(): 5f8.

        * *note inspect.trace(): 5f9.

     （由 Pablo Galindo 於 gh-88116(4) 中所貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30533

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29418

   (3) https://peps.python.org/pep-0657/

   (4) https://github.com/python/cpython/issues/88116


File: python.info,  Node: locale<3>,  Next: logging,  Prev: inspect<2>,  Up: 改進的模組<2>

1.3.7.13 locale
...............

   * 新增 *note locale.getencoding(): 2bc. 以取得當前的區域編碼 (locale
     encoding)。和 ‘locale.getpreferredencoding(False)’ 類似但不考慮
     *note Python UTF-8 模式: 5fc.。


File: python.info,  Node: logging,  Next: math<3>,  Prev: locale<3>,  Up: 改進的模組<2>

1.3.7.14 logging
................

   * 新增 *note getLevelNamesMapping(): 5ff. 以回傳一個日誌級別名稱（例
     如 ‘'CRITICAL'’）指到對應的 *note Logging Levels: 600. 數值（例如，
     預設為 ‘50’）的映射。（由 Andrei Kulakovin 於 gh-88024(1) 中貢獻。
     ）

   * 添加了一個 *note createSocket(): 601. 方法到 *note SysLogHandler:
     602.，以匹配 *note SocketHandler.createSocket(): 603. 。如果沒有已
     啟用的 socket，它會在處理程式初始化期間和發出一個事件時自動呼叫。（
     由 Kirill Pinchuk 在 gh-88457(2) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/88024

   (2) https://github.com/python/cpython/issues/88457


File: python.info,  Node: math<3>,  Next: operator,  Prev: logging,  Up: 改進的模組<2>

1.3.7.15 math
.............

   * 新增 *note math.exp2(): 606.：回傳 2 的 x 次方。（由 Gideon
     Mitchell 於 bpo-45917(1) 中所貢獻。）

   * 新增 *note math.cbrt(): 607.：回傳 x 的立方根。（由 Ajith
     Ramachandran 於 bpo-44357(2) 中所貢獻。）

   * 為了與 IEEE 754 規範保持一致，更改了兩個 *note math.pow(): 608. 邊
     角案例 (corner case) 的行為。‘math.pow(0.0, -math.inf)’ 和
     ‘math.pow(-0.0, -math.inf)’ 現在回傳 ‘inf’，之前它們會引發 *note
     ValueError: 1e7.。（由 Mark Dickinson 在 bpo-44339(3) 中貢獻。）

   * *note math.nan: 609. 現為隨時可用。（由 Victor Stinner 於
     bpo-46917(4) 中所貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45917

   (2) https://bugs.python.org/issue?@action=redirect&bpo=44357

   (3) https://bugs.python.org/issue?@action=redirect&bpo=44339

   (4) https://bugs.python.org/issue?@action=redirect&bpo=46917


File: python.info,  Node: operator,  Next: os<3>,  Prev: math<3>,  Up: 改進的模組<2>

1.3.7.16 operator
.................

   * 新增 ‘operator.call’ 函式，使得 ‘operator.call(obj, *args,
     **kwargs) == obj(*args, **kwargs)’。（由 Antony Lee 於 bpo-44019(1)
     中所貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=44019


File: python.info,  Node: os<3>,  Next: pathlib<4>,  Prev: operator,  Up: 改進的模組<2>

1.3.7.17 os
...........

   * 在 Windows 上，*note os.urandom(): 4c7. 現在使用
     ‘BCryptGenRandom()’ 以取代被棄用的 ‘CryptGenRandom()’。（由 Donghee
     Na 於 bpo-44611(1) 中所貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=44611


File: python.info,  Node: pathlib<4>,  Next: re<3>,  Prev: os<3>,  Up: 改進的模組<2>

1.3.7.18 pathlib
................

   * 如果 'pattern' 以路徑名稱元件分隔符號 *note sep: 610. 或 *note
     altsep: 611. 結尾，*note glob(): 212. 和 *note rglob(): 213. 只回傳
     目錄。（由 Eisuke Kawasima 於 bpo-22276(1) 與 bpo-33392(2) 中所貢獻
     。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22276

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33392


File: python.info,  Node: re<3>,  Next: shutil<3>,  Prev: pathlib<4>,  Up: 改進的模組<2>

1.3.7.19 re
...........

   * 現在規則運算式 (regular expression) 是有支援原子性群組 (atomic
     grouping) (‘(?>...)’) 和佔有性量詞 (possessive quantifier) (‘*+’,
     ‘++’, ‘?+’, ‘{m,n}+’) 的。（由 Jeffrey C. Jacobs 和 Serhiy
     Storchaka 在 bpo-433030(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=433030


File: python.info,  Node: shutil<3>,  Next: socket,  Prev: re<3>,  Up: 改進的模組<2>

1.3.7.20 shutil
...............

   * 新增 *note shutil.rmtree(): 2d2. 的可選參數 'dir_fd'。（由 Serhiy
     Storchaka 於 bpo-46245(1) 中所貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46245


File: python.info,  Node: socket,  Next: sqlite3<4>,  Prev: shutil<3>,  Up: 改進的模組<2>

1.3.7.21 socket
...............

   * 新增 NetBSD 對於 CAN Socket 的支援。（由 Thomas Klausner 於
     bpo-30512(1) 中所貢獻。）

   * 當連接失敗時，*note create_connection(): 618. 有個選項可以引發一個
     包含所有錯誤的 *note ExceptionGroup: 19c.，而非只引發最後一個錯誤。
     （由 Irit Katriel 於 bpo-29980(2) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30512

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29980


File: python.info,  Node: sqlite3<4>,  Next: string,  Prev: socket,  Up: 改進的模組<2>

1.3.7.22 sqlite3
................

   * 現在可以透過將 *note None: 61b. 傳遞給 *note set_authorizer(): 28b.
     來停用 authorizer。（由 Erlend E. Aasland 於 bpo-44491(1) 中貢獻。
     ）

   * 定序 (collation) 名稱 *note create_collation(): 61c. 現在可以包含任
     何 Unicode 字元。帶有無效字元的定序名稱現在會引發 *note
     UnicodeEncodeError: 61d. 而不是 *note sqlite3.ProgrammingError:
     49a.。（由 Erlend E. Aasland 在 bpo-44688(2) 中貢獻。）

   * *note sqlite3: ba. 例外現在包含 SQLite 擴充錯誤碼和 SQLite 錯誤名稱
     （分別為 *note sqlite_errorcode: 61e. 和 *note sqlite_errorname:
     61f.）。（由 Aviv Palivoda、Daniel Shahaf 和 Erlend E. Aasland 在
     bpo-16379(3) 和 bpo-24139(4) 中貢獻。）

   * 將 *note setlimit(): 620. 和 *note getlimit(): 621. 新增到 *note
     sqlite3.Connection: 22a. 以根據連線來設定和取得 SQLite 限制。（由
     Erlend E. Aasland 在 bpo-45243(5) 中貢獻。）

   * *note sqlite3: ba. 現在會基於底層 SQLite 函式庫編譯時所使用的預設執
     行緒模式來設定 *note sqlite3.threadsafety: 622.。（由 Erlend E.
     Aasland 在 bpo-45613(6) 中貢獻。）

   * *note sqlite3: ba. 如果啟用回呼回溯 (callback traceback)，C 回呼現
     在使用無法被引發的例外。使用者現在可以註冊一個*note
     無法被引發的掛鈎處理程式 (unraisable hook handler): 1dc. 來改善他們
     的除錯體驗。（由 Erlend E. Aasland 在 bpo-45828(7) 中貢獻。）

   * 跨越不同回滾 (rollback) 的拿取動作不再引發 *note InterfaceError:
     623.，我們將其留給 SQLite 函式庫來處理這些情況。（由 Erlend E.
     Aasland 在 bpo-44092(8) 中貢獻。）

   * 將 *note serialize(): 624. 和 *note deserialize(): 625. 新增到
     *note sqlite3.Connection: 22a. 以用於序列化和反序列化資料庫。（由
     Erlend E. Aasland 在 bpo-41930(9) 中貢獻。）

   * 於 *note sqlite3.Connection: 22a. 加入 *note
     create_window_function(): 626. 已建立聚合視窗函式 (aggregate window
     function)。（由 Erlend E. Aasland 於 bpo-34916(10) 中貢獻。）

   * 在 *note sqlite3.Connection: 22a. 新增 *note blobopen(): 627.。
     *note sqlite3.Blob: 628. 允許對 blob 進行增量 I/O 操作 (incremental
     I/O operations)。（由 Aviv Palivoda 和 Erlend E. Aasland 在
     bpo-24905(11) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=44491

   (2) https://bugs.python.org/issue?@action=redirect&bpo=44688

   (3) https://bugs.python.org/issue?@action=redirect&bpo=16379

   (4) https://bugs.python.org/issue?@action=redirect&bpo=24139

   (5) https://bugs.python.org/issue?@action=redirect&bpo=45243

   (6) https://bugs.python.org/issue?@action=redirect&bpo=45613

   (7) https://bugs.python.org/issue?@action=redirect&bpo=45828

   (8) https://bugs.python.org/issue?@action=redirect&bpo=44092

   (9) https://bugs.python.org/issue?@action=redirect&bpo=41930

   (10) https://bugs.python.org/issue?@action=redirect&bpo=34916

   (11) https://bugs.python.org/issue?@action=redirect&bpo=24905


File: python.info,  Node: string,  Next: sys<3>,  Prev: sqlite3<4>,  Up: 改進的模組<2>

1.3.7.23 string
...............

   * 新增 *note get_identifiers(): 62b. 和 *note is_valid(): 62c. 於
     *note string.Template: 62d.，分別能夠回傳所有合格的預留位置
     (placeholder) 與是否有任何不合格的預留位置存在。（由 Ben Kehoe 於
     gh-90465(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/90465


File: python.info,  Node: sys<3>,  Next: sysconfig,  Prev: string,  Up: 改進的模組<2>

1.3.7.24 sys
............

   * *note sys.exc_info(): 630. 現在從 ‘value’（例外實例）衍生出 ‘type’
     和 ‘traceback’ 欄位，因此當例外在處理過程中被修改時，變更會反映在
     ‘exc_info()’ 後續呼叫的結果中。（由 Irit Katriel 在 bpo-45711(1) 中
     貢獻。）

   * 新增會回傳活躍例外實例 (active exception instance) 的 *note
     sys.exception(): 631.（等價於 ‘sys.exc_info()[1]’）。（由 Irit
     Katriel 於 bpo-46328(2) 中所貢獻。）

   * 新增 *note sys.flags.safe_path: 632. 旗標。（由 Victor Stinner 於
     gh-57684(3) 中所貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45711

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46328

   (3) https://github.com/python/cpython/issues/57684


File: python.info,  Node: sysconfig,  Next: tempfile<3>,  Prev: sys<3>,  Up: 改進的模組<2>

1.3.7.25 sysconfig
..................

   * 新增了三個*note 安裝方案: 635.（'posix_venv'、'nt_venv' 和 'venv'）
     ，它們在 Python 建立新的虛擬環境或在虛擬環境中執行環境使用。前兩個
     方案（'posix_venv' 和 'nt_venv'）是非 Windows 和 Windows 作業系統所
     特有的，'venv' 本質上會根據 Python 運行的操作系統來做為其中之一的別
     名。這對修改 *note sysconfig.get_preferred_scheme(): 636. 的下游發
     布者很有用。建立新虛擬環境的第三方程式碼應該使用新的 'venv' 安裝方
     案來確定路徑，就像 *note venv: f9. 一樣。（由 Miro Hrončok 在
     bpo-45413(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45413


File: python.info,  Node: tempfile<3>,  Next: threading<2>,  Prev: sysconfig,  Up: 改進的模組<2>

1.3.7.26 tempfile
.................

   * *note SpooledTemporaryFile: 639. 物件現在完整實作了 *note
     io.BufferedIOBase: 63a. 或 *note io.TextIOBase: 63b. 的方法（取決於
     檔案模式），這使它們能夠正確地使用需要類檔案物件的 API，例如壓縮模
     組。（由 Carey Metcalfe 在 gh-70363(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/70363


File: python.info,  Node: threading<2>,  Next: time<2>,  Prev: tempfile<3>,  Up: 改進的模組<2>

1.3.7.27 threading
..................

   * 在 Unix 上，如果 ‘sem_clockwait()’ 函式在 C 函式庫（glibc 2.30 與其
     更新的版本）中可被使用，則 *note threading.Lock.acquire(): 63e. 方
     法現在會使用單調時鐘 (‘time. CLOCK_MONOTONIC’) 用於超時 (timeout)，
     而不是使用系統時鐘 (*note time.CLOCK_REALTIME: 63f.)，以免受系統時
     鐘變化的影響。 由 Victor Stinner 在 bpo-41710(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41710


File: python.info,  Node: time<2>,  Next: tkinter<3>,  Prev: threading<2>,  Up: 改進的模組<2>

1.3.7.28 time
.............

   * 在 Unix 上，如果可用的話，*note time.sleep(): 642. 現在會使用
     ‘clock_nanosleep()’ 或 ‘nanosleep()’ 函式，其解析度為 1 納秒（10^-9
     秒），而不是使用解析度為 1 微秒（10^-6 秒）的 ‘select()’。（由
     Benjamin Szőke 和 Victor Stinner 在 bpo-21302(1) 中貢獻。）

   * 在 Windows 8.1 或更新的平台上，*note time.sleep(): 642. 現在使用了
     一個基於高解析度計時器(2)的可等待 (waitable) 計時器，解析度為 100 奈
     秒（即 10^-7 秒）。在這之前，它只有 1 微秒（10^-3 秒） 的解析度。（
     由 Benjamin Szőke、Donghee Na、Eryk Sun 和 Victor Stinner 於
     bpo-21302(3) 與 bpo-45429(4) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21302

   (2) 
https://docs.microsoft.com/en-us/windows-hardware/drivers/kernel/high-resolution-timers

   (3) https://bugs.python.org/issue?@action=redirect&bpo=21302

   (4) https://bugs.python.org/issue?@action=redirect&bpo=45429


File: python.info,  Node: tkinter<3>,  Next: traceback<2>,  Prev: time<2>,  Up: 改進的模組<2>

1.3.7.29 tkinter
................

   * 新增了 ‘info_patchlevel()’ 方法，它會回傳 Tcl 函式庫的確切版本以作
     為類似於 *note sys.version_info: 645. 的附名元組。（由 Serhiy
     Storchaka 在 gh-91827(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/91827


File: python.info,  Node: traceback<2>,  Next: typing<4>,  Prev: tkinter<3>,  Up: 改進的模組<2>

1.3.7.30 traceback
..................

   * 新增 *note traceback.StackSummary.format_frame_summary(): 648. 以允
     許使用者覆蓋回溯中出現的幀及它們的格式。（由 Ammar Askar 在
     bpo-44569(1) 中貢獻。）

   * 新增 *note traceback.TracebackException.print(): 649.，它會印出格式
     化的 *note TracebackException: 241. 實例至一個檔案。（由 Irit
     Katriel 在 bpo-33809(2) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=44569

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33809


File: python.info,  Node: typing<4>,  Next: unicodedata<3>,  Prev: traceback<2>,  Up: 改進的模組<2>

1.3.7.31 typing
...............

重大變更請見 *note 型別提示相關的新特性: 563.。

   * 新增 *note typing.assert_never(): 64c. 和 *note typing.Never: 64d.。
     *note typing.assert_never(): 64c. 可用於要型別檢查器確認某行程式碼
     是否不可觸及。在執行環境，它會引發 *note AssertionError: 64e.。（由
     Jelle Zijlstra 在 gh-90633(1) 中貢獻。）

   * 新增 *note typing.reveal_type(): 64f.，這可用於請求型別檢查器為給定
     運算式推斷出什麼型別。在執行環境它會印出接收到的值的型別。（由
     Jelle Zijlstra 在 gh-90572(2) 中貢獻。）

   * 新增 *note typing.assert_type(): 650.，這可用於要型別檢查器確認它為
     給定運算式推斷的型別是否與給定型別相符。在執行環境，它只會回傳接收
     到的值。（由 Jelle Zijlstra 在 gh-90638(3) 中貢獻。）

   * *note typing.TypedDict: 146. 型別現可為泛型。（由 Samodya
     Abeysiriwardane 於 gh-89026(4) 中所貢獻。）

   * *note NamedTuple: 291. 型別現可為泛型。（由 Serhiy Storchaka 於
     bpo-43923(5) 中所貢獻。）

   * 允許繼承 *note typing.Any: 651.，這能有效避免與高度動態類別（例如
     mock）相關的型別檢查器錯誤。（由 Shantanu Jain 在 gh-91154(6) 中貢
     獻。）

   * *note typing.final(): 652. 裝飾器現在會在被裝飾的物件上設定
     ‘__final__’ 屬性。（由 Serhiy Storchaka 於 gh-90500(7) 中所貢獻。）

   * *note typing.get_overloads(): 653. 函式可用於自我檢查 (introspect)
     一個函式的過載 (overload)。*note typing.clear_overloads(): 654. 可
     用於清除一個函式的所有已註冊過載。（由 Jelle Zijlstra 在
     gh-89263(8) 中貢獻。）

   * *note Protocol: 249. 子類別的 *note __init__(): 655. 方法現在被保留
     。（由 Adrian Garcia Badarasco 在 gh-88970(9) 中貢獻。）

   * 空元組型別 (‘Tuple[()]’) 的表示法得到簡化，這會影響自我檢查
     (introspection)，例如 ‘get_args(Tuple[()])’ 的求值現在會是 ‘()’ 而
     不是 ‘((),)’。（由 Serhiy Storchaka 在 gh-91137(10) 中貢獻。）

   * 通過刪除私有 ‘typing._type_check’ 函式中的可呼叫檢查，放寬型別標註
     的執行環境要求。（由 Gregory Beauregard 在 gh-90802(11) 中貢獻。）

   * 作為*note PEP 585 泛化別名: 656.中的前向參照，*note
     typing.get_type_hints(): 657. 現支援了為字串求值 (evaluate)。（由
     Niklas Rosenstein 在 gh-85542(12) 中貢獻。）

   * *note typing.get_type_hints(): 657. 不再將 *note Optional: 658. 新
     增到預設為 ‘None’ 的參數中。（由 Nikita Sobolev 在 gh-90353(13) 中
     貢獻。）

   * *note typing.get_type_hints(): 657. 現在支援為無修飾 (bare) 字串化
     (stringified) 的 *note ClassVar: 24b. 標註來求值。（由 Gregory
     Beauregard 在 gh-90711(14) 中貢獻。）

   * *note typing.no_type_check(): 659. 不再修改外部類別和函式。它現在也
     正確地將類別方法標記為不需進行型別檢查。（由 Nikita Sobolev 在
     gh-90729(15) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/90633

   (2) https://github.com/python/cpython/issues/90572

   (3) https://github.com/python/cpython/issues/90638

   (4) https://github.com/python/cpython/issues/89026

   (5) https://bugs.python.org/issue?@action=redirect&bpo=43923

   (6) https://github.com/python/cpython/issues/91154

   (7) https://github.com/python/cpython/issues/90500

   (8) https://github.com/python/cpython/issues/89263

   (9) https://github.com/python/cpython/issues/88970

   (10) https://github.com/python/cpython/issues/91137

   (11) https://github.com/python/cpython/issues/90802

   (12) https://github.com/python/cpython/issues/85542

   (13) https://github.com/python/cpython/issues/90353

   (14) https://github.com/python/cpython/issues/90711

   (15) https://github.com/python/cpython/issues/90729


File: python.info,  Node: unicodedata<3>,  Next: unittest<4>,  Prev: typing<4>,  Up: 改進的模組<2>

1.3.7.32 unicodedata
....................

   * Unicode 資料庫被更新為 14.0.0 版本。（Benjamin Peterson 於
     bpo-45190(1) 中所貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45190


File: python.info,  Node: unittest<4>,  Next: venv<2>,  Prev: unicodedata<3>,  Up: 改進的模組<2>

1.3.7.33 unittest
.................

   * 新增 *note TestCase: 3f4. 類別的 *note enterContext(): 65e. 與
     *note enterClassContext(): 65f. 方法、 *note
     IsolatedAsyncioTestCase: 2de. 類別 的 *note enterAsyncContext():
     660. 方法、*note unittest.enterModuleContext(): 661. 函式。（由
     Serhiy Storchaka 於 bpo-45046(1) 貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45046


File: python.info,  Node: venv<2>,  Next: warnings<2>,  Prev: unittest<4>,  Up: 改進的模組<2>

1.3.7.34 venv
.............

   * 建立新的 Python 虛擬環境時，'venv' *note sysconfig 安裝方案: 635.會
     被用於確定環境內的路徑。當 Python 在虛擬環境中運行時，預設使用相同
     的安裝方案。這意味著下游發布者可以在不改變虛擬環境行為的情況下更改
     預設的 sysconfig 安裝方案。建立新虛擬環境的第三方程式碼也應該這樣做
     。（由 Miro Hrončok 在 bpo-45413(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45413


File: python.info,  Node: warnings<2>,  Next: zipfile,  Prev: venv<2>,  Up: 改進的模組<2>

1.3.7.35 warnings
.................

   * *note warnings.catch_warnings(): 52a. 現在接受 *note
     warnings.simplefilter(): 666. 的引數，提供了一種更簡潔的方法來在本
     地端忽略警告或將它們轉換為錯誤。（由 Zac Hatfield-Dodds 在
     bpo-47074(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=47074


File: python.info,  Node: zipfile,  Prev: warnings<2>,  Up: 改進的模組<2>

1.3.7.36 zipfile
................

   * 新增了對指定成員名稱編碼的支援，以便在 *note ZipFile: 669. 的目錄和
     檔案標頭中讀取元資料 (metadata)。（由 Stephen J. Turnbull 和 Serhiy
     Storchaka 在 bpo-28080(1) 中貢獻。）

   * 新增 *note ZipFile.mkdir(): 66a. 以在 ZIP 歸檔中建立新的目錄。（由
     Sam Ezeh 於 gh-49083(2) 貢獻。）

   * 於 *note zipfile.Path: 66b. 新增 *note stem: 66c.、*note suffix:
     66d. 和 *note suffixes: 66e.。（由 Miguel Brito 於 gh-88261(3) 貢獻
     。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28080

   (2) https://github.com/python/cpython/issues/49083

   (3) https://github.com/python/cpython/issues/88261


File: python.info,  Node: 最佳化<2>,  Next: 更快的 CPython,  Prev: 改進的模組<2>,  Up: Python 3 11 有什麼新功能

1.3.8 最佳化
------------

這個部分會涵蓋到特定的最佳化，但獨立於擁有自己一個說明的*note 更快的
CPython: 544. 計畫。

   * 編譯器現在對僅包含格式程式碼 ‘%s’、‘%r’ 和 ‘%a’ 的字串文本 (string
     literal) 進行簡單的 *note printf 風格 % 格式化 (printf-style %
     formatting): 671. 最佳化並使其與相應的 *note f-string: 3dc. 運算式
     一樣快。（由 Serhiy Storchaka 在 bpo-28307(1) 中貢獻。）

   * 整數除法 (‘//’) 為了編譯器最佳化而被調校過。現在將 *note int: 23c.
     除以小於 ‘2**30’ 的值時，在 x86-64 上快了大約 20%。（由 Gregory P.
     Smith 和 Tim Peters 在 gh-90564(2) 中貢獻。）

   * 針對小於 ‘2**30’ 的整數，*note sum(): 411. 現在快了將近 30%。（由
     Stefan Behnel 於 gh-68264(3) 中所貢獻。）

   * 調整 list 大小在常見情況下增進了效能，為 ‘list.append()’ 加快了約
     15% 並為簡單的 *note list comprehension: 672. 加快了高達 20-30%（由
     Dennis Sweeney 在 gh-91165(4) 中貢獻。）

   * 當所有鍵都是 Unicode 物件時，字典不存儲雜湊值，減少了 *note dict:
     23b. 的大小。例如，‘sys.getsizeof(dict.fromkeys("abcdefg"))’ 在
     64-bit 平台上從 352 位元組減少到 272 位元組（減少 23%）。（由 Inada
     Naoki 在 bpo-46845(5) 中貢獻。）

   * 使用 *note asyncio.DatagramProtocol: 673. 以透過 UDP 傳輸大文件時，
     現在速度提高了幾個數量級，傳輸 ≈60 MiB 檔案的速度提高了 100 多倍。
     （由 msoxzw 在 gh-91487(6) 中貢獻。）

   * *note math: 81. 函式 *note comb(): 674. 和 *note perm(): 675. 針對
     較大引數現在快了 ≈10 倍（對於更大的 'k' 有更大的加速）。（由 Serhiy
     Storchaka 在 bpo-37295(7) 中貢獻。）

   * *note statistics: bd. 函式 *note mean(): 676.、*note variance():
     677. 和 *note stdev(): 678. 現在會一次性的消耗疊代器，而不是先將它
     們轉換為 *note list: 5b6.，這讓速度提升為兩倍並可以節省大量記憶體空
     間。（由 Raymond Hettinger 在 gh-90415(8) 中貢獻。）

   * *note unicodedata.normalize(): 679. 現在在常數時間內規範化
     (normalize) 純 ASCII 字串。（由 Donghee Na 在 bpo-44987(9) 中貢獻。
     ）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28307

   (2) https://github.com/python/cpython/issues/90564

   (3) https://github.com/python/cpython/issues/68264

   (4) https://github.com/python/cpython/issues/91165

   (5) https://bugs.python.org/issue?@action=redirect&bpo=46845

   (6) https://github.com/python/cpython/issues/91487

   (7) https://bugs.python.org/issue?@action=redirect&bpo=37295

   (8) https://github.com/python/cpython/issues/90415

   (9) https://bugs.python.org/issue?@action=redirect&bpo=44987


File: python.info,  Node: 更快的 CPython,  Next: CPython 位元組碼變更<2>,  Prev: 最佳化<2>,  Up: Python 3 11 有什麼新功能

1.3.9 更快的 CPython
--------------------

當使用基準量測套裝軟體 pyperformance(1) 量測並以 GCC 於 Ubuntu Linux 上
編譯，Python 3.11 平均比 Python 3.10 快了 25%(2)。根據程式工作量可能有所
不同，整體加速程度可達 10-60%。

此計畫專注在 Python 的 *note 更快的啟動: 67b. 和 *note 更快的運行程式:
67c.。不在此專案內的最佳化被獨立列出在 *note 最佳化: 670.。

* Menu:

* 更快的啟動::
* 更快的運行程式::
* 雜項::
* FAQ::
* 關於::

   ---------- Footnotes ----------

   (1) https://github.com/python/pyperformance

   (2) https://github.com/faster-cpython/ideas#published-results


File: python.info,  Node: 更快的啟動,  Next: 更快的運行程式,  Up: 更快的 CPython

1.3.9.1 更快的啟動
..................

* Menu:

* 凍結引入 (Frozen imports) / 靜態程式碼物件 (Static code objects): 凍結引入 Frozen imports / 靜態程式碼物件 Static code objects.


File: python.info,  Node: 凍結引入 Frozen imports / 靜態程式碼物件 Static code objects,  Up: 更快的啟動

1.3.9.2 凍結引入 (Frozen imports) / 靜態程式碼物件 (Static code objects)
........................................................................

Python 將*note 位元組碼: 16d.於 *note __pycache__: 680. 目錄中存為快取來
加速模組的載入。

在先前的 3.10 中，執行 Python 模組會像是這樣：

     Read __pycache__ -> Unmarshal -> Heap allocated code object -> Evaluate

在 Python 3.11 中，核心模組在 Python 啟動時必須被「凍結」，這意味著它們
的*note 程式碼物件: 559.（和位元組碼）是由直譯器靜態分配的。這將模組執行
過程中的步驟減少為：

     Statically allocated code object -> Evaluate

在 Python 3.11 中直譯器啟動速度快了 10-15%。這對於使用 Python 所撰寫的短
暫程式有著巨大影響。

（由 Eric Snow、Guido van Rossum 與 Kumar Aditya 於多個 issue 中貢獻。）


File: python.info,  Node: 更快的運行程式,  Next: 雜項,  Prev: 更快的啟動,  Up: 更快的 CPython

1.3.9.3 更快的運行程式
......................

* Menu:

* 所需資源更少 (cheaper) 且惰性的 (lazy)) Python 幀 (frame): 所需資源更少 cheaper 且惰性的 lazy Python 幀 frame.
* 行內 Python 函式呼叫::
* PEP 659：特化的適應性直譯器::


File: python.info,  Node: 所需資源更少 cheaper 且惰性的 lazy Python 幀 frame,  Next: 行內 Python 函式呼叫,  Up: 更快的運行程式

1.3.9.4 所需資源更少 (cheaper) 且惰性的 (lazy)) Python 幀 (frame)
.................................................................

每當 Python 呼叫 Python 函式時，就會建立保存執行資訊的 Python 幀。以下是
針對幀而做的新最佳化：

   - 使幀的建立過程更有效率。

   - 在 C 堆疊 (stack) 中盡量重複利用幀的空間來避免記憶體分配。

   - 讓內部幀結構只包含必要資訊，使其更加精簡。在過去，幀必須帶有額外的
     偵錯與記憶體管理的資訊。

舊式*note 幀物件: 27e.現在僅在除錯器或 Python 自我檢查函式（例如 *note
sys._getframe(): 684. 或 *note inspect.currentframe(): 685.）請求時才建
立。對於大多數使用者程式碼，根本不會建立任何幀物件。結果幾乎所有 Python
函式呼叫都顯著加速。我們以 pyperformance 測得了 3-7% 的加速。

（由 Mark Shannon 於 bpo-44590(1) 中所貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=44590


File: python.info,  Node: 行內 Python 函式呼叫,  Next: PEP 659：特化的適應性直譯器,  Prev: 所需資源更少 cheaper 且惰性的 lazy Python 幀 frame,  Up: 更快的運行程式

1.3.9.5 行內 Python 函式呼叫
............................

在 Python 函式呼叫期間，Python 將呼叫一個正在求值的 C 函式來直譯該函式的
程式碼，這有效地將純 Python 遞迴限制在對 C 堆疊的安全範圍內。

在 3.11 中，當 CPython 檢測到 Python 程式碼呼叫另一個 Python 函式時，它
會設立一個新框架 (frame)，並「跳轉」到新框架內的新程式碼，這避免了呼叫整
個 C 直譯函式。

現在大多數 Python 函式的呼叫因為不會佔用 C 堆疊空間而被加速。在斐波那契
(fibonacci) 或階乘等簡單遞迴函式中，觀察到 1.7 倍的加速。這也意味著遞迴
函式可以遞迴得更深（如果使用者有增加*note 遞迴限制: 46a.）。我們在
pyperformance 測得 1-3% 的改進。

（由 Pablo Galindo 與 Mark Shannon 於 bpo-45256(1) 中所貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45256


File: python.info,  Node: PEP 659：特化的適應性直譯器,  Prev: 行內 Python 函式呼叫,  Up: 更快的運行程式

1.3.9.6 PEP 659：特化的適應性直譯器
...................................

PEP 659(1) 是加速 CPython 專案的關鍵部分之一。一般的想法是，雖然 Python
是一種動態語言，但大多數程式碼都有物件和型別很少去更改的區域。這個概念被
稱為'型別穩定 (type stability)'。

在執行環境，Python 將嘗試在執行中的程式碼內尋找常用模式和型別穩定，然後
Python 將用更特化的操作替換當前操作。這種特化操作運用了僅適用於那些用例
/型別的快速路徑，這通常優於它們的泛用對應 (generic counterparts)。這也引
入了另一個稱為'行內快取 (inline caching)'的概念，其中 Python 將繁重操作
的結果直接快取在*note 位元組碼: 16d.中。

特化程式 (specializer) 還將某些常用指示 (common instruction) 組合成一個
超級指示 (superinstruction)，這減少了執行期間的開銷。

Python 只會在看到「熱」（被多次執行的）程式碼時特化，這可以防止 Python 將
時間浪費在只運行一次的程式碼上。當程式碼過於動態或用途發生變化時，Python
也可以去特化 (de-specialize)。特化會定期被嘗試執行，而嘗試的成本也不會太
高，這讓特化得以適應新的環境。

（PEP 由 Mark Shannon 撰寫、概念啟發自 Stefan Brunthaler。詳情請見 PEP
659(2)。由 Mark Shannon 和 Brandt Bucher 實作，Irit Katriel 和 Dennis
Sweeney 亦提供了額外的幫助。）

操作                形式                     特化                                                        操作加速程度（上限）    貢獻者
                                                                                                                                 
---------------------------------------------------------------------------------------------------------------------------------------------------------
                                                                                                                                 
二元操作            ‘x + x’                  常見型別如 *note int: 23c.、*note float: 2c8. 與            10%                     Mark Shannon, Donghee
                                             *note str: 3f2. 的二元加法、乘法與減法，為底層型別採取了                            Na, Brandt Bucher,
                    ‘x - x’                  特製的快速路徑。                                                                    Dennis Sweeney
                                                                                                                                 
                    ‘x * x’
                    
                                                                                                                                 
下標                ‘a[i]’                   下標容器型別如 *note list: 5b6.、*note tuple: 322. 和       10-25%                  Irit Katriel, Mark
                                             *note dict: 23b. 直接索引底層的資料結構。                                           Shannon
                                                                                                                                 
                                             下標自定義 *note __getitem__(): 266. 也是行內的，類似於
                                             *note 行內 Python 函式呼叫: 686.。
                                             
                                                                                                                                 
儲存下標            ‘a[i] = z’               類似於上面的下標特化。                                      10-25%                  Dennis Sweeney
                                                                                                                                 
                                                                                                                                 
呼叫                ‘f(arg)’                 常見內建 (C) 函式和型別的呼叫，例如 *note len(): 5d4. 和    20%                     Mark Shannon, Ken Jin
                                             *note str: 3f2.，會直接呼叫它們的 C 版本底層，這避免了通                            
                    ‘C(arg)’                 過內部呼叫的慣例。
                                             
                                                                                                                                 
載入全域變數        ‘print’                  全域/內建之命名空間內的物件索引被快取起來。載入全域與內建   (3)                     Mark Shannon
                                             變數不需要任何命名空間的查找。                                                      
                    ‘len’                    
                    
                                                                                                                                 
載入屬性            ‘o.attr’                 和載入全域變數類似，類別/物件之命名空間內的屬性索引被快取   (4)                     Mark Shannon
                                             起來。在大部分情況中，載入屬性不需要任何命名空間的查找。                            
                                             
                                                                                                                                 
載入要呼叫的方法    ‘o.meth()’               方法的真實記憶體地址被快取 (cache) 起來，方法的載入現在不   10-20%                  Ken Jin, Mark Shannon
                                             需要命名空間的查找 - 即便有很長繼承鏈結的類別也是。                                 
                                             
                                                                                                                                 
儲存屬性            ‘o.attr = z’             和載入屬性的最佳化相似。                                    2% 於 pyperformance 中  Mark Shannon
                                                                                                                                 
                                                                                                                                 
拆解 (unpack) 序    ‘*seq’                   為像是 *note list: 5b6. 和 *note tuple: 322. 的常見容器所   8%                      Brandt Bucher
列                                           特化，避免了內部呼叫慣例。                                                          
                                             

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0659/

   (2) https://peps.python.org/pep-0659/

   (3) 類似的最佳化自從 Python 3.8 就存在。3.11 特別處理了更多形式並減少
效能開銷 (overhead)。

   (4) 類似的最佳化自從 Python 3.10 就存在。3.11 特別處理了更多形式。此
外，所有屬性載入也被 bpo-45947
(https://bugs.python.org/issue?@action=redirect&bpo=45947) 所加速。


File: python.info,  Node: 雜項,  Next: FAQ,  Prev: 更快的運行程式,  Up: 更快的 CPython

1.3.9.7 雜項
............

   * 物件現在因為使用了惰性建立的物件命名空間所以需要更少的記憶體。它們
     的命名空間字典現在也更自由地共享鍵。（由 Mark Shannon 於
     bpo-45340(1) 和 bpo-40116(2) 貢獻。 ）

   * 實作了「無代價 (Zero-cost)」的例外，消除了在沒有例外被引發時的
     *note try: 68c. 陳述式開銷。（由 Mark Shannon 於 bpo-40222(3) 貢獻
     。）

   * 在直譯器內使用更簡潔的例外表示法將捕獲一個例外所需的時間減少了大約
     10%。 由 Irit Katriel 在 bpo-45711(4) 中貢獻。）

   * *note re: a7. 的正規表示式比對引擎部分被重構，且現在會有支援的平台
     上使用 computed gotos（或者「執行緒程式碼 (threaded code)」），因此
     Python 3.11 在執行 pyperformance 正規表示式基準量測(5)的表現上比起
     Python 3.10 快了 10%。（由 Brandt Bucher 於 gh-91404(6) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45340

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40116

   (3) https://bugs.python.org/issue?@action=redirect&bpo=40222

   (4) https://bugs.python.org/issue?@action=redirect&bpo=45711

   (5) https://pyperformance.readthedocs.io/benchmarks.html#regex-dna

   (6) https://github.com/python/cpython/issues/91404


File: python.info,  Node: FAQ,  Next: 關於,  Prev: 雜項,  Up: 更快的 CPython

1.3.9.8 FAQ
...........

* Menu:

* 我該如何在程式碼中獲取這些加速？::
* Python 3.11 會不會使用更多記憶體？: Python 3 11 會不會使用更多記憶體？.
* 我在我的程式當中沒感覺到任何加速，為什麼？::
* 有用到 JIT 編譯器嗎？::


File: python.info,  Node: 我該如何在程式碼中獲取這些加速？,  Next: Python 3 11 會不會使用更多記憶體？,  Up: FAQ

1.3.9.9 我該如何在程式碼中獲取這些加速？
........................................

撰寫符合 Python 風格 (Pythonic) 且依循常見最佳實踐的程式碼就好，你不需要
改變你的程式碼。CPython 加速計畫中，我們為所觀察到的常見程式編寫模式來做
最佳化。


File: python.info,  Node: Python 3 11 會不會使用更多記憶體？,  Next: 我在我的程式當中沒感覺到任何加速，為什麼？,  Prev: 我該如何在程式碼中獲取這些加速？,  Up: FAQ

1.3.9.10 Python 3.11 會不會使用更多記憶體？
...........................................

也許不會。我們預期不會有超出 3.10 20% 的記憶體使用量。這數字會和上述禎物
件與物件字典的記憶體最佳化而有所偏差。


File: python.info,  Node: 我在我的程式當中沒感覺到任何加速，為什麼？,  Next: 有用到 JIT 編譯器嗎？,  Prev: Python 3 11 會不會使用更多記憶體？,  Up: FAQ

1.3.9.11 我在我的程式當中沒感覺到任何加速，為什麼？
...................................................

某些程式中不會有顯著的好處。如果你的程式花了大部分的時間在 I/O 操作上，
或已經將大部分計算用像是 numpy 的 C 擴充函式庫處理，那就不會有明顯的加速
。這個計畫是對純 Python 的工作負荷最有幫助。

此外，pyperformance 數值為一個幾何平均數 (geometric mean)。即便在
pyperformance 基準量測中，某些測試稍微慢了一些，但其他加快了將近兩倍！


File: python.info,  Node: 有用到 JIT 編譯器嗎？,  Prev: 我在我的程式當中沒感覺到任何加速，為什麼？,  Up: FAQ

1.3.9.12 有用到 JIT 編譯器嗎？
..............................

沒有，我們還在探索其他最佳化方式。


File: python.info,  Node: 關於,  Prev: FAQ,  Up: 更快的 CPython

1.3.9.13 關於
.............

CPython 加速計畫探索了各種 *note CPython: 699. 最佳化的可能性。主要團隊
由微軟 (microsoft) 所資助以全職發展該計畫，Pablo Galindo Salgado 亦由彭
博有限合夥企業 (Bloomberg LP) 資助來兼職開發，更有許許多多來自社群的自發
性貢獻者。


File: python.info,  Node: CPython 位元組碼變更<2>,  Next: 已棄用<3>,  Prev: 更快的 CPython,  Up: Python 3 11 有什麼新功能

1.3.10 CPython 位元組碼變更
---------------------------

位元組碼現在包含行內快取條目，它們採用新添加的 *note CACHE: 69c. 指示的
形式。許多操作碼預期後面要有確切數量的快取，並指示直譯器在執行環境跳過它
們。傳遞的 (populated) 快取看起來像任意指示，因此在讀取或修改包含加速資
料的原始且適應 (adaptive) 位元組碼時應格外小心。

* Menu:

* 新增 opcode::
* 被取代的操作碼 (opcode): 被取代的操作碼 opcode.
* 有更動/被移除的 opcode::


File: python.info,  Node: 新增 opcode,  Next: 被取代的操作碼 opcode,  Up: CPython 位元組碼變更<2>

1.3.10.1 新增 opcode
....................

   * ‘ASYNC_GEN_WRAP’、*note RETURN_GENERATOR: 69f. 和 *note SEND: 6a0.
     被用於產生器與協程。

   * *note COPY_FREE_VARS: 6a1.，避免了為閉包 (closure) 而生的特殊呼叫方
     (caller-side) 程式碼的需求。

   * *note JUMP_BACKWARD_NO_INTERRUPT: 6a2.，用於某些不需要處理中斷的循
     環。

   * *note MAKE_CELL: 6a3. 被用於建立 *note Cell 物件: 6a4.。

   * *note CHECK_EG_MATCH: 6a5. 和 ‘PREP_RERAISE_STAR’，處理 PEP 654(1)
     所加入的*note 新增例外群組和 except*: 545.。

   * *note PUSH_EXC_INFO: 6a6. 被用於例外處理函式。

   * *note RESUME: 6a7.，為無操作 (no-po)，用於內部追查、除錯和最佳化檢
     查。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0654/


File: python.info,  Node: 被取代的操作碼 opcode,  Next: 有更動/被移除的 opcode,  Prev: 新增 opcode,  Up: CPython 位元組碼變更<2>

1.3.10.2 被取代的操作碼 (opcode)
................................

被取代的操作碼                           新的操作碼                               註記
                                                                                  
--------------------------------------------------------------------------------------------------------------------------------
                                                                                  
     ‘BINARY_*’                          *note BINARY_OP: 6aa.                    以單一一個操作碼來取代所有數值的、二進位/原
     ‘INPLACE_*’                                                                  位 (in-place) 操作碼
                                                                                  
                                                                                  
     ‘CALL_FUNCTION’                          *note CALL: 6ab.                    將方法的引數搬移 (argument shifting) 與關鍵
     ‘CALL_FUNCTION_KW’                       ‘KW_NAMES’                          字引數的處理分離開來；允許更好的呼叫特化
     ‘CALL_METHOD’                            ‘PRECALL’                           
                                              *note PUSH_NULL: 6ac.
                                         
                                                                                  
     ‘DUP_TOP’                                *note COPY: 6ad.                    堆疊操作指示
     ‘DUP_TOP_TWO’                            *note SWAP: 6ae.                    
     ‘ROT_TWO’                           
     ‘ROT_THREE’
     ‘ROT_FOUR’
     ‘ROT_N’

     ‘JUMP_IF_NOT_EXC_MATCH’                  *note CHECK_EXC_MATCH: 6af.         現在執行檢查但不跳位 (jump)
                                                                                  
                                                                                  
     ‘JUMP_ABSOLUTE’                          *note JUMP_BACKWARD: 6b0.           參見 (1)；每個方向的 ‘TRUE’、‘FALSE’、
     ‘POP_JUMP_IF_FALSE’                      ‘POP_JUMP_BACKWARD_IF_*’            ‘NONE’ 和 ‘NOT_NONE’ 變體
     ‘POP_JUMP_IF_TRUE’                       ‘POP_JUMP_FORWARD_IF_*’             
                                         
                                                                                  
     ‘SETUP_WITH’                        *note BEFORE_WITH: 6b1.                  *note with: 577. 區塊設置
     ‘SETUP_ASYNC_WITH’                                                           

   ---------- Footnotes ----------

   (1) 所有跳位操作碼 (jump opcode) 現在都是相對的，包括現有的
‘JUMP_IF_TRUE_OR_POP’ 和 ‘JUMP_IF_FALSE_OR_POP’。該引數現在是當前指示
(instruction) 的偏移量而不是絕對位置。


File: python.info,  Node: 有更動/被移除的 opcode,  Prev: 被取代的操作碼 opcode,  Up: CPython 位元組碼變更<2>

1.3.10.3 有更動/被移除的 opcode
...............................

   * 更改了 *note MATCH_CLASS: 6b6. 和 *note MATCH_KEYS: 6b7. ，不再推送
     一個額外的布林值來表示成功/失敗。取而代之的是會在失敗時推送 ‘None’，
     而非一個包含提取值的元組。

   * 更改了運作於例外的操作碼以反映它們現在在堆疊中的表示為一項而不是三
     項（請參閱 gh-89874(1)）。

   * 刪除 ‘COPY_DICT_WITHOUT_KEYS’、‘GEN_START’、‘POP_BLOCK’、
     ‘SETUP_FINALLY’ 和 ‘YIELD_FROM’。

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/89874


File: python.info,  Node: 已棄用<3>,  Next: Python 3 12 中待決議的移除項目,  Prev: CPython 位元組碼變更<2>,  Up: Python 3 11 有什麼新功能

1.3.11 已棄用
-------------

這個部分列出了在 Python 3.11 中棄用的 Python API。

被棄用的 C API 被*note 獨立列出: 6bb.。
* Menu:

* 語言/內建::
* 模組::
* 標準函式庫::


File: python.info,  Node: 語言/內建,  Next: 模組,  Up: 已棄用<3>

1.3.11.1 語言/內建
..................

   * 鏈接 *note classmethod: 14a. 描述器（在 bpo-19072(1) 中引入）現已棄
     用。它不能再用於包裝其他描述器，例如 *note property: 180.。此功能的
     核心設計存在缺陷，並導致了許多下游問題。要「傳遞通過
     (pass-through)」*note classmethod: 14a.，請考慮使用 Python 3.10 中
     添加的 ‘__wrapped__’ 屬性。（由 Raymond Hettinger 在 gh-89519(2) 中
     貢獻。）

   * 值大於 ‘0o377’（十進位為 255）的字串和位元組文本值 (bytes literal)
     中的八進位跳脫 (octal escape) 現在會產生 *note DeprecationWarning:
     18b.。在未來的 Python 版本中，他們將引發一個 *note SyntaxWarning:
     40c. 並最終引發一個 *note SyntaxError: 173.。（由 Serhiy Storchaka
     在 gh-81548(3) 中貢獻。）

   * *note int(): 23c. 到 *note __trunc__(): 6bf. 的授權 (delegation) 現
     已棄用。當 ‘type(a)’ 有實作 ‘__trunc__()’ 但沒有 *note __int__():
     6c0. 或 *note __index__(): 6c1.，呼叫 ‘int(a)’ 現在會引發一個 *note
     DeprecationWarning: 18b.。（由 Zackery Spytz 在 bpo-44977(4) 中貢獻
     。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=19072

   (2) https://github.com/python/cpython/issues/89519

   (3) https://github.com/python/cpython/issues/81548

   (4) https://bugs.python.org/issue?@action=redirect&bpo=44977


File: python.info,  Node: 模組,  Next: 標準函式庫,  Prev: 語言/內建,  Up: 已棄用<3>

1.3.11.2 模組
.............

   * PEP 594(1) 引領下列模組的棄用，並排訂於 Python 3.13 移除：

     ‘aifc’                    ‘chunk’                   ‘msilib’                  ‘pipes’                   ‘telnetlib’
                                                                                                             
                                                                                                             
     ‘audioop’                 ‘crypt’                   ‘nis’                     ‘sndhdr’                  ‘uu’
                                                                                                             
                                                                                                             
     ‘cgi’                     ‘imghdr’                  ‘nntplib’                 ‘spwd’                    ‘xdrlib’
                                                                                                             
                                                                                                             
     ‘cgitb’                   ‘mailcap’                 ‘ossaudiodev’             ‘sunau’
                                                                                   

     （由 Brett Cannon 和 Victor Stinner 分別於 bpo-47061(2) 與
     gh-68966(3) 中所貢獻。）

   * ‘asynchat’、‘asyncore’ 和 ‘smtpd’ 至少在 Python 3.6 以前就被棄用，
     它們的文件與棄用警告現在已被更新為會提示它們即將於 Python 3.12 中移
     除。（由 Hugo van Kemenade 於 bpo-47022(4) 中貢獻。）

   * The ‘lib2to3’ package and ‘2to3’ tool are now deprecated and may
     not be able to parse Python 3.10 or newer.  See PEP 617(5),
     introducing the new PEG parser, for details.  (Contributed by
     Victor Stinner in bpo-40360(6).)

   * 未被記錄於文件中的 ‘sre_compile’、‘sre_constants’ 和 ‘sre_parse’ 模
     組現在已被棄用。（由 Serhiy Storchaka 在 bpo-47152(7) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0594/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=47061

   (3) https://github.com/python/cpython/issues/68966

   (4) https://bugs.python.org/issue?@action=redirect&bpo=47022

   (5) https://peps.python.org/pep-0617/

   (6) https://bugs.python.org/issue?@action=redirect&bpo=40360

   (7) https://bugs.python.org/issue?@action=redirect&bpo=47152


File: python.info,  Node: 標準函式庫,  Prev: 模組,  Up: 已棄用<3>

1.3.11.3 標準函式庫
...................

   * 以下 *note configparser: 1b. 相關項目已在 Python 3.2 中棄用，它們的
     棄用警告現在會提示它們即將於 Python 3.12 中移除：

        * ‘configparser.SafeConfigParser’ 類別

        * ‘configparser.ParsingError.filename’ 屬性

        * ‘configparser.RawConfigParser.readfp()’ 方法

     （由 Hugo van Kemenade 於 bpo-45173(1) 中所貢獻。）

   * ‘configparser.LegacyInterpolation’ 自 Python 3.2 起已在文件字串中棄
     用，並且未在 *note configparser: 1b. 文檔中列出。它現在會發出一個
     *note DeprecationWarning: 18b. 並將在 Python 3.13 中刪除。請改用
     *note configparser.BasicInterpolation: 6c6. 或 *note
     configparser.ExtendedInterpolation: 6c7.。（由 Hugo van Kemenade 在
     bpo-46607(2) 中貢獻。）

   * 舊的 *note importlib.resources: 6f. 函式集因為不支援定位套件子目錄
     中的資源而被棄用、並將在未來的 Python 版本中刪除，取而代之的是在
     Python 3.9 中添加的替代方案：

        * ‘importlib.resources.contents()’

        * ‘importlib.resources.is_resource()’

        * ‘importlib.resources.open_binary()’

        * ‘importlib.resources.open_text()’

        * ‘importlib.resources.read_binary()’

        * ‘importlib.resources.read_text()’

        * ‘importlib.resources.path()’

   * *note locale.getdefaultlocale(): 2ba. 函式已被棄用且將於 Python
     3.15 中移除。請改用 *note locale.setlocale(): 2bb.、*note
     locale.getpreferredencoding(False): 4df. 和 *note
     locale.getlocale(): 2bd.。（Victor Stinner 於 gh-90817(3) 中所貢獻
     。）

   * The ‘locale.resetlocale()’ function is deprecated and will be
     removed in Python 3.13.  Use ‘locale.setlocale(locale.LC_ALL, "")’
     instead.  (Contributed by Victor Stinner in gh-90817(4).)

   * 現在將對*note 規則運算式: 6c8.中的數值群組參照 (numerical group
     references) 和群組名稱套用更嚴格的規則。現在只接受 ASCII 數字序列作
     為數值參照，並且 *note bytes: 1a5. 模式 (pattern) 的群組名稱和替換
     字串中只能包含 ASCII 字母、數字和底線。目前，會針對違反這些規則的語
     法發出棄用警告。（由 Serhiy Storchaka 在 gh-91760(5) 中貢獻。）

   * 在 *note re: a7. 模組中，‘re.template()’ 函式和相應的 ‘re.TEMPLATE’
     和 ‘re.T’ 旗標被棄用，因為它們沒被記錄於文件中並且缺乏明顯的目的。
     它們將在 Python 3.13 中被刪除。（由 Serhiy Storchaka 和 Miro
     Hrončok 在 gh-92728(6) 中貢獻。）

   * ‘turtle.settiltangle()’ has been deprecated since Python 3.1; it
     now emits a deprecation warning and will be removed in Python 3.13.
     Use *note turtle.tiltangle(): 6c9. instead (it was earlier
     incorrectly marked as deprecated, and its docstring is now
     corrected).  (Contributed by Hugo van Kemenade in bpo-45837(7).)

   * 僅用於支援 Python 2 和 Python 3 程式碼間相容性的 *note typing.Text:
     2dd. 現已棄用。目前未計劃刪除它，但鼓勵用戶盡可能使用 *note str:
     3f2. 代替。（由 Alex Waygood 在 gh-92332(8) 中貢獻。）

   * 用於建構 *note typing.TypedDict: 146. 型別的關鍵字引數語法現已棄用
     。將在 Python 3.13 中停止支援。（由 Jingchen Ye 在 gh-90224(9) 中貢
     獻。）

   * ‘webbrowser.MacOSX’ 已被棄用且將於 Python 3.13 中移除。它並沒有被測
     試過、沒紀錄於文件、也沒有被 *note webbrowser: fd. 本身使用。（由
     Donghee Na 於 bpo-42255(10)。）

   * 回傳從 *note TestCase: 3f4. 和 *note IsolatedAsyncioTestCase: 2de.
     測試方法（預設的 ‘None’ 值除外）給定值的行為現已棄用。

   * 棄用以下並沒有正式紀錄於文件中的 *note unittest: ef. 函式，並預計於
     Python 3.13 中移除：

        * ‘unittest.findTestCases()’

        * ‘unittest.makeSuite()’

        * ‘unittest.getTestCaseNames()’

     改用 *note TestLoader: 270. 方法：

        * *note unittest.TestLoader.loadTestsFromModule(): 271.

        * *note unittest.TestLoader.loadTestsFromTestCase(): 272.

        * *note unittest.TestLoader.getTestCaseNames(): 273.

     （由 Erlend E. Aasland 於 bpo-5846(11) 中所貢獻。）

   * ‘unittest.TestProgram.usageExit()’ 被標記為已棄用，即將在 3.13 中移
     除（由 Carlos Damázio 在 gh-67048(12) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45173

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46607

   (3) https://github.com/python/cpython/issues/90817

   (4) https://github.com/python/cpython/issues/90817

   (5) https://github.com/python/cpython/issues/91760

   (6) https://github.com/python/cpython/issues/92728

   (7) https://bugs.python.org/issue?@action=redirect&bpo=45837

   (8) https://github.com/python/cpython/issues/92332

   (9) https://github.com/python/cpython/issues/90224

   (10) https://bugs.python.org/issue?@action=redirect&bpo=42255

   (11) https://bugs.python.org/issue?@action=redirect&bpo=5846

   (12) https://github.com/python/cpython/issues/67048


File: python.info,  Node: Python 3 12 中待決議的移除項目,  Next: 已移除<3>,  Prev: 已棄用<3>,  Up: Python 3 11 有什麼新功能

1.3.12 Python 3.12 中待決議的移除項目
-------------------------------------

下列 API 已在先前的 Python 發布版本中棄用，並將於 Python 3.12 中移除。

待定的 C API 移除項目為*note 獨立列出的: 6cd.。

   * ‘asynchat’ 模組

   * ‘asyncore’ 模組

   * *note 整個 distutils 套件: 6ce.

   * ‘imp’ 模組

   * *note typing.io: 6cf. 命名空間

   * *note typing.re: 6d0. 命名空間

   * ‘cgi.log()’

   * ‘importlib.find_loader()’

   * ‘importlib.abc.Loader.module_repr()’

   * ‘importlib.abc.MetaPathFinder.find_module()’

   * ‘importlib.abc.PathEntryFinder.find_loader()’

   * ‘importlib.abc.PathEntryFinder.find_module()’

   * ‘importlib.machinery.BuiltinImporter.find_module()’

   * ‘importlib.machinery.BuiltinLoader.module_repr()’

   * ‘importlib.machinery.FileFinder.find_loader()’

   * ‘importlib.machinery.FileFinder.find_module()’

   * ‘importlib.machinery.FrozenImporter.find_module()’

   * ‘importlib.machinery.FrozenLoader.module_repr()’

   * ‘importlib.machinery.PathFinder.find_module()’

   * ‘importlib.machinery.WindowsRegistryFinder.find_module()’

   * ‘importlib.util.module_for_loader()’

   * ‘importlib.util.set_loader_wrapper()’

   * ‘importlib.util.set_package_wrapper()’

   * ‘pkgutil.ImpImporter’

   * ‘pkgutil.ImpLoader’

   * ‘pathlib.Path.link_to()’

   * ‘sqlite3.enable_shared_cache()’

   * ‘sqlite3.OptimizedUnicode()’

   * ‘PYTHONTHREADDEBUG’ 環境變數

   * *note unittest: ef. 中被棄用的別名：

          已棄用的別名                     方法名稱                            棄用於
                                                                               
          -----------------------------------------------------------------------------------------
                                                                               
          ‘failUnless’                     *note assertTrue(): 4cb.            3.1
                                                                               
                                                                               
          ‘failIf’                         *note assertFalse(): 4cc.           3.1
                                                                               
                                                                               
          ‘failUnlessEqual’                *note assertEqual(): 4cd.           3.1
                                                                               
                                                                               
          ‘failIfEqual’                    *note assertNotEqual(): 4ce.        3.1
                                                                               
                                                                               
          ‘failUnlessAlmostEqual’          *note assertAlmostEqual(): 4cf.     3.1
                                                                               
                                                                               
          ‘failIfAlmostEqual’              *note assertNotAlmostEqual(): 4d0.  3.1
                                                                               
                                                                               
          ‘failUnlessRaises’               *note assertRaises(): 4d1.          3.1
                                                                               
                                                                               
          ‘assert_’                        *note assertTrue(): 4cb.            3.2
                                                                               
                                                                               
          ‘assertEquals’                   *note assertEqual(): 4cd.           3.2
                                                                               
                                                                               
          ‘assertNotEquals’                *note assertNotEqual(): 4ce.        3.2
                                                                               
                                                                               
          ‘assertAlmostEquals’             *note assertAlmostEqual(): 4cf.     3.2
                                                                               
                                                                               
          ‘assertNotAlmostEquals’          *note assertNotAlmostEqual(): 4d0.  3.2
                                                                               
                                                                               
          ‘assertRegexpMatches’            *note assertRegex(): 4d2.           3.2
                                                                               
                                                                               
          ‘assertRaisesRegexp’             *note assertRaisesRegex(): 4d3.     3.2
                                                                               
                                                                               
          ‘assertNotRegexpMatches’         *note assertNotRegex(): 4d4.        3.5
                                                                               


File: python.info,  Node: 已移除<3>,  Next: 移植至 Python 3 11,  Prev: Python 3 12 中待決議的移除項目,  Up: Python 3 11 有什麼新功能

1.3.13 已移除
-------------

此部分列出 Python 3.11 中移除的 Python API。

被移除的 C API 被*note 獨立列出: 6d4.。

   * 刪除了 ‘@asyncio.coroutine()’ *note decorator: 6d5. 使遺留的基於生
     成器的協程 (generator-based coroutine) 與 *note async: 6d6. / *note
     await: 19f. 程式碼相容。該函式自 Python 3.8 起已被棄用，計劃於
     Python 3.10 刪除。請改用 *note async def: 575.。（由 Illia Volochii
     在 bpo-43216(1) 中貢獻。）

   * 移除除錯模式中用於包裝遺留基於產生器之協程物件的
     ‘asyncio.coroutines.CoroWrapper’。（由 Illia Volochii 於
     bpo-43216(2) 中貢獻。）

   * 因為有重大的安全性考量，Python 3.9 中停用的 *note
     asyncio.loop.create_datagram_endpoint(): 6d7. 之 'reuse_address' 參
     數目前已經移除。這是因為 UDP socket 選項 ‘SO_REUSEADDR’ 的行為所致
     。（由 Hugo van Kemenade 於 bpo-45129(3) 中貢獻。）

   * 移除 Python 3.9 中棄用的 ‘binhex’ 模組，與其相關且相似的 *note
     binascii: c. 函式也一併被移除：

        * ‘binascii.a2b_hqx()’

        * ‘binascii.b2a_hqx()’

        * ‘binascii.rlecode_hqx()’

        * ‘binascii.rldecode_hqx()’

     *note binascii.crc_hqx(): 6d8. 維持可用。

     （由 Victor Stinner 於 bpo-45085(4) 中所貢獻。）

   * 移除 Python 3.9 中棄用的 ‘distutils’ ‘bdist_msi’ 命令。請改用
     ‘bdist_wheel’（wheel 套件）。（由 Hugo van Kemenade 於 bpo-45124(5)
     中貢獻。）

   * 將 *note xml.dom.pulldom.DOMEventStream: 6d9.、*note
     wsgiref.util.FileWrapper: 6da. 和 *note fileinput.FileInput: 6db. 自
     Python 3.9 中棄用的 *note __getitem__(): 266. 方法移除。(由 Hugo
     van Kemenade 在 bpo-45132(6) 中貢獻。)

   * 刪除了已棄用的 *note gettext: 59. 函式 ‘lgettext()’、
     ‘ldgettext()’、‘lngettext()’ 和 ‘ldngettext()’，也刪除了
     ‘bind_textdomain_codeset()’ 函式、
     ‘NullTranslations.output_charset()’ 和
     ‘NullTranslations.set_output_charset()’ 方法，以及 ‘translation()’
     和 ‘install()’ 的 'codeset' 參數，因為它們僅被用於 ‘l*gettext()’ 函
     式。（由 Donghee Na 和 Serhiy Storchaka 在 bpo-44235(7) 中貢獻。）

   * 於 *note inspect: 72. 模組中移除：

        * Python 3.0 中棄用的 ‘getargspec()’；改用 *note
          inspect.signature(): 6dc. 或 *note inspect.getfullargspec():
          6dd.。

        * Python 3.5 中棄用的 ‘formatargspec()’ 函式；請直接用 *note
          inspect.signature(): 6dc. 函式或 *note inspect.Signature: 1b3.
          物件。

        * Python 3.5 中停用且沒有被紀錄於文件上的
          ‘Signature.from_builtin()’ 和 ‘Signature.from_function()’ 方法
          ；改用 *note Signature.from_callable(): 6de. 方法。

     （由 Hugo van Kemenade 於 bpo-45320(8) 中所貢獻。）

   * 自 *note pathlib.PurePath: 44e. 中移除 *note __class_getitem__():
     6df. 方法，因為它是前一版本中誤加且沒被使用。（由 Nikita Sobolev 於
     bpo-46483(9) 中所貢獻。）

   * 移除 ‘smtpd’ 模組中的 ‘MailmanProxy’ 類別，因為它無法獨立於外部套件
     ‘mailman’ 使用。（由 Donghee Na 於 bpo-35800(10) 貢獻。）

   * 移除 ‘_tkinter.TkappType’ 已被棄用的 ‘split()’ 方法。（由 Erlend E.
     Aasland 於 bpo-38371(11) 貢獻。）

   * 從 *note unittest: ef. 中刪除了命名空間套件支援。它在 Python 3.4 中
     引入，但自 Python 3.7 以來已無法運作。（由 Inada Naoki 在
     bpo-23882(12) 中貢獻。）

   * 將未被記錄於文件中的私有方法 ‘float.__set_format__()’ 移除，它過去
     是 Python 3.7 中的 ‘float.__setformat__()’。它的文件字串
     (docstring) 說到：「你大概不會想要使用這個函式，它只為了讓 Python 測
     試系列套件 (suite) 使用而存在。」（由 Victor Stinner 於
     bpo-46852(13) 中貢獻。）

   * 移除 ‘--experimental-isolated-subinterpreters’ 配置旗標（與對應的
     ‘EXPERIMENTAL_ISOLATED_SUBINTERPRETERS’ 巨集）。

   * Pynche(14) -- Python 風格的自然色彩與色調編輯器 -- 已被移出
     ‘Tools/scripts’，獨立開發(15)於 Python 原始碼之外。

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43216

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43216

   (3) https://bugs.python.org/issue?@action=redirect&bpo=45129

   (4) https://bugs.python.org/issue?@action=redirect&bpo=45085

   (5) https://bugs.python.org/issue?@action=redirect&bpo=45124

   (6) https://bugs.python.org/issue?@action=redirect&bpo=45132

   (7) https://bugs.python.org/issue?@action=redirect&bpo=44235

   (8) https://bugs.python.org/issue?@action=redirect&bpo=45320

   (9) https://bugs.python.org/issue?@action=redirect&bpo=46483

   (10) https://bugs.python.org/issue?@action=redirect&bpo=35800

   (11) https://bugs.python.org/issue?@action=redirect&bpo=38371

   (12) https://bugs.python.org/issue?@action=redirect&bpo=23882

   (13) https://bugs.python.org/issue?@action=redirect&bpo=46852

   (14) https://pypi.org/project/Pynche/

   (15) https://gitlab.com/warsaw/pynche/-/tree/main


File: python.info,  Node: 移植至 Python 3 11,  Next: 建置變更<2>,  Prev: 已移除<3>,  Up: Python 3 11 有什麼新功能

1.3.14 移植至 Python 3.11
-------------------------

本部分列出了之前描述的 Python API 中可能需要你去更改 Python 程式碼的變更
和其他錯誤修復。

C API 的移植被*note 獨立列出: 6e3.。

   * *note open(): 4c0.、*note io.open(): 4c1.、*note codecs.open():
     6e4. 和 *note fileinput.FileInput: 6db. 不再接受 ‘'U'’（"universal
     newline"，通用換行符）文件模式。在 Python 3 中，每當以文本模式
     (text mode) 打開檔案時，預設情況下會使用「通用換行符」模式，並且自
     Python 3.3 以來就不推薦使用 ‘'U'’ 旗標。這些函式的 *note newline
     參數: 6e5.控制了通用換行符的作用方式。（由 Victor Stinner 在
     bpo-37330(1) 中貢獻。）

   * *note ast.AST: 18c. 節點位置現在會在提供給 *note compile(): 178. 和
     其他相關函式時被驗證。如果檢測到無效位置，則會引發 *note
     ValueError: 1e7.。（由 Pablo Galindo 在 gh-93351(2) 中貢獻）

   * 在 Python 3.8 中棄用後，禁止將非 *note
     concurrent.futures.ThreadPoolExecutor: 6e6. 執行器傳遞給 *note
     asyncio.loop.set_default_executor(): 6e7.。（由 Illia Volochii 在
     bpo-43234(3) 中貢獻。）

   * *note calendar: 10.：*note calendar.LocaleTextCalendar: 6e8. 和
     *note calendar.LocaleHTMLCalendar: 6e9. 類別如果沒有指定語言環境，
     現在會使用 *note locale.getlocale(): 2bd. 而非 *note
     locale.getdefaultlocale(): 2ba.。（由 Victor Stinner 在
     bpo-46659(4) 中貢獻。）

   * *note pdb: 94. 模組現在會讀取 ‘'UTF-8'’ 編碼的 ‘.pdbrc’ 配置檔案。
     （Srinivas Reddy Thatiparthy (శ్రీనివాస్ రెడ్డి తాటిపర్తి) 於 bpo-41137(5) 貢獻
     。）

   * *note random.sample(): 6ea. 的 'population' 參數必須是一個序列，不
     再支援 *note set: 57d. 到 *note list: 5b6. 的自動轉換。此外，如果抽
     樣大小大於總體大小，則會引發 *note ValueError: 1e7.。（由 Raymond
     Hettinger 在 bpo-40465(6) 中貢獻。）

   * 刪除了 *note random.shuffle(): 6eb. 的 'random' 可選參數。它以前是
     用於隨機排列 (shuffle) 的任意隨機函式；現在都會使用 *note
     random.random(): 6ec.（這是它以前的預設值）。

   * 在 *note re: a7. *note 正規表示式語法: 6c8. 中，全域行內旗標（例如
     ‘(?i)’）現在只能在規則運算式的開頭使用。自 Python 3.6 以來，在其他
     地方使用它們已被棄用。（由 Serhiy Storchaka 在 bpo-47066(7) 中貢獻
     。）

   * 在 *note re: a7. 模組中修復了幾個長期存在的錯誤，在極少數情況下，這
     些錯誤可能會導致捕獲群組 (capture group) 得到錯誤的結果。因此，這可
     能會在這些情況下更改捕獲的輸出。（Ma Lin 在 bpo-35859(8) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=37330

   (2) https://github.com/python/cpython/issues/93351

   (3) https://bugs.python.org/issue?@action=redirect&bpo=43234

   (4) https://bugs.python.org/issue?@action=redirect&bpo=46659

   (5) https://bugs.python.org/issue?@action=redirect&bpo=41137

   (6) https://bugs.python.org/issue?@action=redirect&bpo=40465

   (7) https://bugs.python.org/issue?@action=redirect&bpo=47066

   (8) https://bugs.python.org/issue?@action=redirect&bpo=35859


File: python.info,  Node: 建置變更<2>,  Next: C API 變更<2>,  Prev: 移植至 Python 3 11,  Up: Python 3 11 有什麼新功能

1.3.15 建置變更
---------------

   * CPython 現在有 PEP 11(1) Tier 3 支援(2) 以用於交叉編譯至
     WebAssembly(3) 平台 Emscripten(4)（‘wasm32-unknown-emscripten’，即
     瀏覽器中的 Python）和 WebAssembly 系統介面 (WASI)(5)
     (‘wasm32-unknown-wasi’)。這個靈感來自過往的貢獻，例如 Pyodide(6)。
     這些平台提供了有限的 POSIX API 子集；Python 標準函式庫功能和與網路
     、行程、執行緒、訊號、mmap、用戶/群組相關的模組不開放使用或無法正常
     使用。（Emscripten 由 Christian Heimes 和 Ethan Smith 在
     gh-84461(7) 貢獻，WASI 由 Christian Heimes 在 gh-90473(8) 貢獻；平
     台在 gh-95085(9) 中推廣）

   * 建置 CPython 現在必須要有：

        * C11(10) 編譯器與標準函式庫。可選的 C11 特性(11) 並非必要。（由
          Victor Stinner 於 bpo-46656(12)、bpo-45440(13) 和
          bpo-46640(14) 中貢獻。）

        * 對 IEEE 754(15) 浮點數的支援（由 Victor Stinner 於
          bpo-46917(16) 中所貢獻。）

   * ‘Py_NO_NAN’ 巨集已被移除。因為 CPython 現在需要 IEEE 754 浮點數，
     NaN 數值皆為可得的。（由 Victor Stinner 在 bpo-46656(17) 中貢獻。）

   * *note tkinter: d9. 套件現在必須要有 Tcl/Tk(18) 8.5.12 或更新的版本
     。（由 Serhiy Storchaka 於 bpo-46996(19) 中所貢獻。）

   * 大多數 stdlib 擴充模組的依賴套件、編譯器旗標 (compiler flag) 和鏈接
     器旗標 (linker flags) 現在可以透過 ‘configure’ 檢測出來。（當可用時
     ）pkg-config(20) 會檢測出 libffi、libnsl、libsqlite3、zlib、bzip2、
     liblzma、libcrypt、Tcl/Tk 和 uuid 旗標。*note tkinter: d9. 現在需要
     一個 pkg-config 命令來檢測 Tcl/Tk(21) 標頭檔和函式庫的開發設定。（
     由 Christian Heimes 和 Erlend Egeberg Aasland 在 bpo-45847(22)、
     bpo-45747(23) 和 bpo-45763(24) 中貢獻。）

   * libpython 不再鏈接到 libcrypt。（由 Mike Gilbert 在 bpo-45433(25) 中
     貢獻。）

   * CPython 現在可以透過將 ‘thin’ 傳遞給 *note -with-lto: 6ef.（也就是
     ‘--with-lto=thin’）來以 ThinLTO(26) 選項建置。（由 Donghee Na 與
     Brett Holman 於 bpo-44340(27) 中所貢獻。）

   * Freelists for object structs can now be disabled.  A new
     ‘configure’ option *note -without-freelists: 6f0. can be used to
     disable all freelists except empty tuple singleton.  (Contributed
     by Christian Heimes in bpo-45522(28).)

   * ‘Modules/Setup’ 和 ‘Modules/makesetup’ 已得到改進和綁定。現在可以通
     過 ‘makesetup’ 建置擴充模組。除了一些測試模組外，所有模組都可以靜態
     鏈接到主要的二進制文件或函式庫中。（由 Brett Cannon 和 Christian
     Heimes 在 bpo-45548(29)、bpo-45570(30)、bpo-45571(31) 和
     bpo-43974(32) 中貢獻。）

          備註: 使用環境變數 ‘TCLTK_CFLAGS’ 和 ‘TCLTK_LIBS’ 以手動指定
          Tcl/Tk 標頭檔和函式庫的位置。‘configure’ 選項
          ‘—with-tcltk-includes’ 和 ‘—with-tcltk-libs’ 已被刪除。

          RHEL 7 和 CentOS 7 上的開發套件並無提供 ‘tcl.pc’ 和 ‘tk.pc’；
          要使用 ‘TCLTK_LIBS="-ltk8.5 -ltkstub8.5 -ltcl8.5"’。目錄
          ‘Misc/rhel7’ 包含 ‘.pc’ 檔案與如何使用 RHEL 7 和 CentOS 7 的
          Tcl/Tk 與 OpenSSL 建置 Python 的指示。

   * CPython 現在預設使用 30-bit 數字來實作 Python *note int: 23c.。以前
     ，在 ‘SIZEOF_VOID_P >= 8’ 的平台上預設使用 30-bit 數字，否則使用
     15-bit 數字，但仍能通過配置腳本的 *note -enable-big-digits: 6f1. 選
     項或（於 Windows）‘PC/pyconfig.h’ 中的 ‘PYLONG_BITS_IN_DIGIT’ 變數
     來明確請求使用 15-bit 數字，但此選項可能會在將來的某個時候被刪除。
     （由 Mark Dickinson 在 bpo-45569(33) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0011/

   (2) https://peps.python.org/pep-0011/#tier-3

   (3) https://webassembly.org/

   (4) https://emscripten.org/

   (5) https://wasi.dev/

   (6) https://pyodide.org/

   (7) https://github.com/python/cpython/issues/84461

   (8) https://github.com/python/cpython/issues/90473

   (9) https://github.com/python/cpython/issues/95085

   (10) https://en.cppreference.com/w/c/11

   (11) 
https://en.wikipedia.org/wiki/C11_(C_standard_revision)#Optional_features

   (12) https://bugs.python.org/issue?@action=redirect&bpo=46656

   (13) https://bugs.python.org/issue?@action=redirect&bpo=45440

   (14) https://bugs.python.org/issue?@action=redirect&bpo=46640

   (15) https://en.wikipedia.org/wiki/IEEE_754

   (16) https://bugs.python.org/issue?@action=redirect&bpo=46917

   (17) https://bugs.python.org/issue?@action=redirect&bpo=46656

   (18) https://www.tcl.tk

   (19) https://bugs.python.org/issue?@action=redirect&bpo=46996

   (20) https://www.freedesktop.org/wiki/Software/pkg-config/

   (21) https://www.tcl.tk

   (22) https://bugs.python.org/issue?@action=redirect&bpo=45847

   (23) https://bugs.python.org/issue?@action=redirect&bpo=45747

   (24) https://bugs.python.org/issue?@action=redirect&bpo=45763

   (25) https://bugs.python.org/issue?@action=redirect&bpo=45433

   (26) https://clang.llvm.org/docs/ThinLTO.html

   (27) https://bugs.python.org/issue?@action=redirect&bpo=44340

   (28) https://bugs.python.org/issue?@action=redirect&bpo=45522

   (29) https://bugs.python.org/issue?@action=redirect&bpo=45548

   (30) https://bugs.python.org/issue?@action=redirect&bpo=45570

   (31) https://bugs.python.org/issue?@action=redirect&bpo=45571

   (32) https://bugs.python.org/issue?@action=redirect&bpo=43974

   (33) https://bugs.python.org/issue?@action=redirect&bpo=45569


File: python.info,  Node: C API 變更<2>,  Next: Notable changes in 3 11 4,  Prev: 建置變更<2>,  Up: Python 3 11 有什麼新功能

1.3.16 C API 變更
-----------------

* Menu:

* 新增特性: 新增特性<4>.
* 移植至 Python 3.11: 移植至 Python 3 11<2>.
* 已棄用: 已棄用<4>.
* Python 3.12 中待決議的移除項目: Python 3 12 中待決議的移除項目<2>.
* 已移除: 已移除<4>.


File: python.info,  Node: 新增特性<4>,  Next: 移植至 Python 3 11<2>,  Up: C API 變更<2>

1.3.16.1 新增特性
.................

   * 新增 *note PyType_GetName(): 6f6. 函式來取得型別的短名。（由 Hai
     Shi 於 bpo-42035(1) 中所貢獻。）

   * 新增 *note PyType_GetQualName(): 6f7. 函式來取得型別的合格名稱
     (qualified name)。（由 Hai Shi 於 bpo-42035(2) 中所貢獻。）

   * 在受限 C API (limited C API) 中新增 *note
     PyThreadState_EnterTracing(): 6f8. 和 *note
     PyThreadState_LeaveTracing(): 6f9. 函式來中止和繼續追蹤 (tracing) 和
     性能分析 (profiling)。（由 Victor Stinner 於 bpo-43760(3) 中貢獻。
     ）

   * 添加了 *note Py_Version: 6fa. 常數，其值與 *note PY_VERSION_HEX:
     6fb. 相同。（由 Gabriele N. Tornetta 在 bpo-43931(4) 中貢獻。）

   * *note Py_buffer: 6fc. 與 API 目前是受限 API 與穩定 ABI 中的一部分：

        * *note PyObject_CheckBuffer(): 368.

        * *note PyObject_GetBuffer(): 369.

        * *note PyBuffer_GetPointer(): 6fd.

        * *note PyBuffer_SizeFromFormat(): 6fe.

        * *note PyBuffer_ToContiguous(): 6ff.

        * *note PyBuffer_FromContiguous(): 700.

        * *note PyObject_CopyData(): 701.

        * *note PyBuffer_IsContiguous(): 702.

        * *note PyBuffer_FillContiguousStrides(): 703.

        * *note PyBuffer_FillInfo(): 704.

        * *note PyBuffer_Release(): 36a.

        * *note PyMemoryView_FromBuffer(): 705.

        * *note bf_getbuffer: 706. 與 *note bf_releasebuffer: 707. 型別
          插槽 (type slot)

     （由 Christian Heimes 於 bpo-45459(5) 中所貢獻。）

   * 新增 *note PyType_GetModuleByDef(): 342. 函式，它將被用於取得定義一
     個方法的模組，以免這項資訊無法直接被取得（透過 *note PyCMethod:
     708.）。（由 Petr Viktorin 於 bpo-46613(6) 中所貢獻。）

   * 新增函式以打包 (pack) 和取出 (unpack) C double（序列化和反序列化）
     ：*note PyFloat_Pack2(): 709.、*note PyFloat_Pack4(): 70a.、*note
     PyFloat_Pack8(): 70b.、*note PyFloat_Unpack2(): 70c. , *note
     PyFloat_Unpack4(): 70d. 和 *note PyFloat_Unpack8(): 70e.。（由
     Victor Stinner 在 bpo-46906(7) 中貢獻。）

   * 新增取得幀物件屬性的函式：*note PyFrame_GetBuiltins(): 70f.、*note
     PyFrame_GetGenerator(): 710.、*note PyFrame_GetGlobals(): 711.、
     *note PyFrame_GetLasti(): 712.。

   * 添加了兩個新函式來獲得和設置仍在作用的例外實例：*note
     PyErr_GetHandledException(): 713. 和 *note
     PyErr_SetHandledException(): 714.。這些是 *note PyErr_SetExcInfo():
     715. 和 *note PyErr_GetExcInfo(): 716. 的替代品，它們與例外的遺留三
     元組表示法一起作用。（由 Irit Katriel 在 bpo-46343(8) 中貢獻。）

   * 新增 *note PyConfig.safe_path: 717. 成員。（由 Victor Stinner 於
     gh-57684(9) 中所貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42035

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42035

   (3) https://bugs.python.org/issue?@action=redirect&bpo=43760

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43931

   (5) https://bugs.python.org/issue?@action=redirect&bpo=45459

   (6) https://bugs.python.org/issue?@action=redirect&bpo=46613

   (7) https://bugs.python.org/issue?@action=redirect&bpo=46906

   (8) https://bugs.python.org/issue?@action=redirect&bpo=46343

   (9) https://github.com/python/cpython/issues/57684


File: python.info,  Node: 移植至 Python 3 11<2>,  Next: 已棄用<4>,  Prev: 新增特性<4>,  Up: C API 變更<2>

1.3.16.2 移植至 Python 3.11
...........................

   * 一些巨集已轉換為行內靜態函式以避免巨集陷阱 (macro pitfalls)(1)。這
     種變化對用戶來說應該是透明的，因為替換函式會將它們的引數轉換為預期
     的型別，以避免由於靜態型別檢查而產生的編譯器警告。但是，當受限 C
     API 設置為 >=3.11 時，這些轉換不會完成，使用者需要將引數轉換為他們
     期望的型別。有關更多詳細資訊，請參閱 PEP 670(2)。（由 Victor
     Stinner 和 Erlend E. Aasland 在 gh-89653(3) 中貢獻。）

   * *note PyErr_SetExcInfo(): 715. 不再使用 ‘type’ 和 ‘traceback’ 引數
     ，直譯器現在從例外實例（‘value’ 引數）中獲得這些值。該函式仍會偷用
     這三個引數的參照。（由 Irit Katriel 在 bpo-45711(4) 中貢獻。）

   * *note PyErr_GetExcInfo(): 716. 現在從例外實例的結果（‘value’ 欄位）
     中導出 ‘type’ 和 ‘traceback’ 欄位。（由 Irit Katriel 在
     bpo-45711(5) 中貢獻。）

   * *note _frozen: 719. 有一個新的 ‘is_package’ 欄位來表示凍結模組是否
     為一個套件。以前 ‘size’ 欄位中的負值是指標，現在只有非負值可用於
     ‘size’。（由 Kumar Aditya 在 bpo-46608(6) 中貢獻。）

   * *note _PyFrameEvalFunction(): 71a. 現在將 ‘_PyInterpreterFrame*’ 作
     為其第二個參數，而不是 ‘PyFrameObject*’。有關如何使用此函式指標型別
     的更多詳細資訊，請參閱 PEP 523(7)。

   * ‘PyCode_New()’ 和 ‘PyCode_NewWithPosOnlyArgs()’ 現在採用額外的
     ‘exception_table’ 引數。如果可能的話應該避免使用這些函式。要獲取自
     定義程式碼物件，使用編譯器建立一個程式碼物件，然後使用 ‘replace’ 方
     法來得到修改後的版本。

   * *note PyCodeObject: 71b. 不再會有 ‘co_code’、‘co_varnames’、
     ‘co_cellvars’ 和 ‘co_freevars’ 欄位。分別被改為透過 C API 的 *note
     PyCode_GetCode(): 71c.、*note PyCode_GetVarnames(): 71d.、*note
     PyCode_GetCellvars(): 71e. 和 *note PyCode_GetFreevars(): 71f. 來存
     取。（由 Brandt Bucher 在 bpo-46841(8)、Ken Jin 在 gh-92154(9) 與
     gh-94936(10) 中貢獻。）

   * 舊的回收筒巨集 (trashcan macro)
     (‘Py_TRASHCAN_SAFE_BEGIN’/‘Py_TRASHCAN_SAFE_END’) 現在已經被棄用，
     它們應被新的巨集 ‘Py_TRASHCAN_BEGIN’ 和 ‘Py_TRASHCAN_END’ 所取代。

     一個用到老舊巨集的 tp_dealloc 函式，像是：

          static void
          mytype_dealloc(mytype *p)
          {
              PyObject_GC_UnTrack(p);
              Py_TRASHCAN_SAFE_BEGIN(p);
              ...
              Py_TRASHCAN_SAFE_END
          }

     應該要搬遷到新的巨集，如下所示：

          static void
          mytype_dealloc(mytype *p)
          {
              PyObject_GC_UnTrack(p);
              Py_TRASHCAN_BEGIN(p, mytype_dealloc)
              ...
              Py_TRASHCAN_END
          }

     請注意 ‘Py_TRASHCAN_BEGIN’ 有第二個引數，它應該是它所在的釋放函式
     (deallocation function)。

     為支援舊版 Python 在同一份程式碼中，你可以定義以下巨集並在程式碼中
     使用它們（要歸功於 ‘mypy’ 程式碼，這些是從那邊複製過來的）：

          #if PY_VERSION_HEX >= 0x03080000
          #  define CPy_TRASHCAN_BEGIN(op, dealloc) Py_TRASHCAN_BEGIN(op, dealloc)
          #  define CPy_TRASHCAN_END(op) Py_TRASHCAN_END
          #else
          #  define CPy_TRASHCAN_BEGIN(op, dealloc) Py_TRASHCAN_SAFE_BEGIN(op)
          #  define CPy_TRASHCAN_END(op) Py_TRASHCAN_SAFE_END(op)
          #endif

   * 如果一個型別是以 *note Py_TPFLAGS_HAVE_GC: 720. 旗標來定義，但卻沒
     有遍歷函式 (traverse function) (*note PyTypeObject.tp_traverse:
     721.)，那 *note PyType_Ready(): 722. 函式現在會引發一個錯誤。（由
     Victor Stinner 於 bpo-44263(11) 中貢獻。）

   * 帶有 *note Py_TPFLAGS_IMMUTABLETYPE: 38d. 旗標的堆積型別現在可以繼
     承 PEP 590(12) 向量呼叫協定 (vectorcall protocol)。以前這僅適用於
     *note static types: 723.。（由 Erlend E. Aasland 在 bpo-43908(13) 中
     貢獻）。

   * 由於 *note Py_TYPE(): 724. 更改為行內靜態函式 (inline static
     function)，因此 ‘Py_TYPE(obj) = new_type’ 必須替換為
     ‘Py_SET_TYPE(obj, new_type)’：參見 *note Py_SET_TYPE(): 725. 函式（
     自 Python 3.9 起可用）。為了向後相容，可以使用這個巨集：

          #if PY_VERSION_HEX < 0x030900A4 && !defined(Py_SET_TYPE)
          static inline void _Py_SET_TYPE(PyObject *ob, PyTypeObject *type)
          { ob->ob_type = type; }
          #define Py_SET_TYPE(ob, type) _Py_SET_TYPE((PyObject*)(ob), type)
          #endif

     （由 Victor Stinner 於 bpo-39573(14) 中所貢獻。）

   * 由於 *note Py_SIZE(): 726. 更改為行內靜態函式，因此 ‘Py_SIZE(obj) =
     new_size’ 必須替換為 ‘Py_SET_SIZE(obj, new_size)’：參見 *note
     Py_SET_SIZE(): 727. 函式（自 Python 3.9 起可用）。為了向後相容，可
     以使用這個巨集：

          #if PY_VERSION_HEX < 0x030900A4 && !defined(Py_SET_SIZE)
          static inline void _Py_SET_SIZE(PyVarObject *ob, Py_ssize_t size)
          { ob->ob_size = size; }
          #define Py_SET_SIZE(ob, size) _Py_SET_SIZE((PyVarObject*)(ob), size)
          #endif

     （由 Victor Stinner 於 bpo-39573(15) 中所貢獻。）

   * 當 ‘Py_LIMITED_API’ 巨集被設定為 ‘0x030b0000’（Python 3.11）或以上
     ，‘<Python.h>’ 不再會包含標頭檔 ‘<stdlib.h>’、‘<stdio.h>’、
     ‘<errno.h>’ 和 ‘<string.h>’。C 擴充程式應該要清楚的在 ‘#include
     <Python.h>’ 之後引入標頭檔案。（由 Victor Stinner 於 bpo-45434(16)
     中貢獻。）

   * 非受限 API (non-limited API) 檔案 ‘cellobject.h’、‘classobject.h’、
     ‘code.h’、‘context.h’、‘funcobject.h’、‘genobject. h’ 和
     ‘longintrepr.h’ 已移至 ‘Include/cpython’ 目錄。此外，‘eval.h’ 標頭
     檔已被刪除。不能直接引入這些文件，因為它們已被包含在 ‘Python.h’ 中
     ：*note 引入檔案: 728.。如果它們已被直接引入，請考慮改為引入
     ‘Python.h’。 （由 Victor Stinner 在 bpo-35134(17) 中貢獻。）

   * ‘PyUnicode_CHECK_INTERNED()’ 巨集已從受限 C API 中移出，它從來沒辦
     法被使用，因為它使用了受限 C API 不提供的內部結構。（由 Victor
     Stinner 於 bpo-46007(18) 中所貢獻。）

   * 以下用於幀 (frame) 的函式與型別現在可直接透過 ‘#include <Python.h>’
     來使用，不必再加上 ‘#include <frameobject.h>’：

        * *note PyFrame_Check(): 729.

        * *note PyFrame_GetBack(): 72a.

        * *note PyFrame_GetBuiltins(): 70f.

        * *note PyFrame_GetGenerator(): 710.

        * *note PyFrame_GetGlobals(): 711.

        * *note PyFrame_GetLasti(): 712.

        * *note PyFrame_GetLocals(): 35f.

        * *note PyFrame_Type: 72b.

     （由 Victor Stinner 於 gh-93937(19) 中所貢獻。）

   * *note PyFrameObject: 72d. 結構成員已經從公開的 C API 中移除。

     雖然文件指出 *note PyFrameObject: 72d. 欄位隨時可能發生變化，但它們
     已經穩定了很長時間，並被用於幾個流行的擴充套件中。

     Python 3.11 中，幀的結構被重新編制來為性能做最佳化，有些作為舊版實
     作細節的欄位被整個移除。

     *note PyFrameObject: 72d. 欄位：

        * ‘f_back’：使用 *note PyFrame_GetBack(): 72a.。

        * ‘f_blockstack’：已移除。

        * ‘f_builtins’：使用 *note PyFrame_GetBuiltins(): 70f.。

        * ‘f_code’：使用 *note PyFrame_GetCode(): 72e.。

        * ‘f_gen’：使用 *note PyFrame_GetGenerator(): 710.。

        * ‘f_globals’：使用 *note PyFrame_GetGlobals(): 711.。

        * ‘f_iblock’：已移除。

        * ‘f_lasti’：使用 *note PyFrame_GetLasti(): 712.。程式碼中
          ‘f_lasti’ 有與 ‘PyCode_Addr2Line()’ 同時使用的部分應該改用
          *note PyFrame_GetLineNumber(): 72f.；它可能會更快。

        * ‘f_lineno’：使用 *note PyFrame_GetLineNumber(): 72f.

        * ‘f_locals’：使用 *note PyFrame_GetLocals(): 35f.。

        * ‘f_stackdepth’：已移除。

        * ‘f_state’：無公開 API（重新命名為 ‘f_frame.f_state’）。

        * ‘f_trace’：無公開 API。

        * ‘f_trace_lines’：使用
          ‘PyObject_GetAttrString((PyObject*)frame, "f_trace_lines")’。

        * ‘f_trace_opcodes’：使用
          ‘PyObject_GetAttrString((PyObject*)frame, "f_trace_opcodes")’。

        * ‘f_localsplus’：無公開 API（重新命名為 ‘f_frame.localsplus’）
          。

        * ‘f_valuestack’：已移除。

     Python 幀物件的建立現為惰性的 (lazily)，一個副作用是 *note f_back:
     730. 成員不能被直接存取，因為其職的計算也是惰性的，要改呼叫 *note
     PyFrame_GetBack(): 72a.。

     直接存取 *note f_locals: 165. 的除錯器'必須'改為呼叫 *note
     PyFrame_GetLocals(): 35f.。他們不再需要呼叫
     ‘PyFrame_FastToLocalsWithError()’ 或 ‘PyFrame_LocalsToFast()’，事實
     上他們不應該呼叫這些函式。框架的必要更新現在由虛擬機管理。

     ‘PyFrame_GetCode()’ 在 Python 3.8 以前的程式定義：

          #if PY_VERSION_HEX < 0x030900B1
          static inline PyCodeObject* PyFrame_GetCode(PyFrameObject *frame)
          {
              Py_INCREF(frame->f_code);
              return frame->f_code;
          }
          #endif

     ‘PyFrame_GetBack()’ 在 Python 3.8 以前的程式定義：

          #if PY_VERSION_HEX < 0x030900B1
          static inline PyFrameObject* PyFrame_GetBack(PyFrameObject *frame)
          {
              Py_XINCREF(frame->f_back);
              return frame->f_back;
          }
          #endif

     或是使用 pythoncap_compat 計畫(20)來在舊版 Python 函式中取得這兩個
     函式。

   * *note PyThreadState: 731. 結構成員的改動：

        * ‘frame’：已移除，改用 *note PyThreadState_GetFrame(): 732.（
          bpo-40429(21) 於 Python 3.9 新增的函式）。警告：會回傳 *note
          strong reference: 2ee. 的函式必須呼叫 *note Py_XDECREF():
          733.。

        * ‘tracing’：已變更，改用 *note PyThreadState_EnterTracing():
          6f8. 和 *note PyThreadState_LeaveTracing(): 6f9.（
          bpo-43760(22) 於 Python 3.11 中新增的函式）。

        * ‘recursion_depth’：已移除，請改用 ‘(tstate->recursion_limit -
          tstate->recursion_remaining)’。

        * ‘stackcheck_counter’：已移除。

     ‘PyThreadState_GetFrame()’ 在 Python 3.8 以前的程式定義：

          #if PY_VERSION_HEX < 0x030900B1
          static inline PyFrameObject* PyThreadState_GetFrame(PyThreadState *tstate)
          {
              Py_XINCREF(tstate->frame);
              return tstate->frame;
          }
          #endif

     ‘PyThreadState_EnterTracing()’ 與 ‘PyThreadState_LeaveTracing()’ 在
     Python 3.10 以前的程式定義：

          #if PY_VERSION_HEX < 0x030B00A2
          static inline void PyThreadState_EnterTracing(PyThreadState *tstate)
          {
              tstate->tracing++;
          #if PY_VERSION_HEX >= 0x030A00A1
              tstate->cframe->use_tracing = 0;
          #else
              tstate->use_tracing = 0;
          #endif
          }

          static inline void PyThreadState_LeaveTracing(PyThreadState *tstate)
          {
              int use_tracing = (tstate->c_tracefunc != NULL || tstate->c_profilefunc != NULL);
              tstate->tracing--;
          #if PY_VERSION_HEX >= 0x030A00A1
              tstate->cframe->use_tracing = use_tracing;
          #else
              tstate->use_tracing = use_tracing;
          #endif
          }
          #endif

     或是使用 pythoncap-compat 計畫(23)來在舊版 Python 函式中取得它們。

   * 鼓勵發布者們使用最佳化過的 Blake2 函式庫 libb2(24) 來建置 Python。

   * 初始化中若是要用 *note PyConfig.module_search_paths: 36d. 來初始化
     *note sys.path: 37f.，則現在 *note
     PyConfig.module_search_paths_set: 593. 必須被設為 1。否則，初始化會
     重新計算路徑並取代所有被加到 ‘module_search_paths’ 的值。

   * *note PyConfig_Read(): 734. 不再計算初始搜索路徑，並且不會將任何值
     填充到 *note PyConfig.module_search_paths: 36d. 中。若要計算預設路
     徑然後修改它們，完成初始化並使用 *note PySys_GetObject(): 35d. 以取
     得 *note sys.path: 37f. 作為 Python 列表物件並直接修改它。

   ---------- Footnotes ----------

   (1) https://gcc.gnu.org/onlinedocs/cpp/Macro-Pitfalls.html

   (2) https://peps.python.org/pep-0670/

   (3) https://github.com/python/cpython/issues/89653

   (4) https://bugs.python.org/issue?@action=redirect&bpo=45711

   (5) https://bugs.python.org/issue?@action=redirect&bpo=45711

   (6) https://bugs.python.org/issue?@action=redirect&bpo=46608

   (7) https://peps.python.org/pep-0523/

   (8) https://bugs.python.org/issue?@action=redirect&bpo=46841

   (9) https://github.com/python/cpython/issues/92154

   (10) https://github.com/python/cpython/issues/94936

   (11) https://bugs.python.org/issue?@action=redirect&bpo=44263

   (12) https://peps.python.org/pep-0590/

   (13) https://bugs.python.org/issue?@action=redirect&bpo=43908

   (14) https://bugs.python.org/issue?@action=redirect&bpo=39573

   (15) https://bugs.python.org/issue?@action=redirect&bpo=39573

   (16) https://bugs.python.org/issue?@action=redirect&bpo=45434

   (17) https://bugs.python.org/issue?@action=redirect&bpo=35134

   (18) https://bugs.python.org/issue?@action=redirect&bpo=46007

   (19) https://github.com/python/cpython/issues/93937

   (20) https://github.com/python/pythoncapi-compat

   (21) https://bugs.python.org/issue?@action=redirect&bpo=40429

   (22) https://bugs.python.org/issue?@action=redirect&bpo=43760

   (23) https://github.com/python/pythoncapi-compat

   (24) https://www.blake2.net/


File: python.info,  Node: 已棄用<4>,  Next: Python 3 12 中待決議的移除項目<2>,  Prev: 移植至 Python 3 11<2>,  Up: C API 變更<2>

1.3.16.3 已棄用
...............

   * 棄用以下用來配置 Python 初始化的函式：

        * ‘PySys_AddWarnOptionUnicode()’

        * ‘PySys_AddWarnOption()’

        * ‘PySys_AddXOption()’

        * ‘PySys_HasWarnOptions()’

        * ‘PySys_SetArgvEx()’

        * ‘PySys_SetArgv()’

        * ‘PySys_SetPath()’

        * ‘Py_SetPath()’

        * ‘Py_SetProgramName()’

        * ‘Py_SetPythonHome()’

        * ‘Py_SetStandardStreamEncoding()’

        * ‘_Py_SetProgramFullPath()’

     請改用 *note Python 初始化配置: 372.中新的 *note PyConfig: 371.
     API。（由 Victor Stinner 於 gh-88279(1) 中所貢獻。）

   * 棄用 *note PyBytesObject: 736. 中的 ‘ob_shash’ 成員。請改用 *note
     PyObject_Hash(): 3cb.。（由 Inada Naoki 於 bpo-46864(2) 中所貢獻。
     ）

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/88279

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46864


File: python.info,  Node: Python 3 12 中待決議的移除項目<2>,  Next: 已移除<4>,  Prev: 已棄用<4>,  Up: C API 變更<2>

1.3.16.4 Python 3.12 中待決議的移除項目
.......................................

以下 C API 已於先前 Python 發布版本中棄用，並將於 Python 3.12 中移除。

   * ‘PyUnicode_AS_DATA()’

   * ‘PyUnicode_AS_UNICODE()’

   * ‘PyUnicode_AsUnicodeAndSize()’

   * ‘PyUnicode_AsUnicode()’

   * ‘PyUnicode_FromUnicode()’

   * ‘PyUnicode_GET_DATA_SIZE()’

   * ‘PyUnicode_GET_SIZE()’

   * ‘PyUnicode_GetSize()’

   * ‘PyUnicode_IS_COMPACT()’

   * ‘PyUnicode_IS_READY()’

   * *note PyUnicode_READY(): 3c9.

   * ‘PyUnicode_WSTR_LENGTH()’

   * ‘_PyUnicode_AsUnicode()’

   * ‘PyUnicode_WCHAR_KIND’

   * *note PyUnicodeObject: 738.

   * ‘PyUnicode_InternImmortal()’


File: python.info,  Node: 已移除<4>,  Prev: Python 3 12 中待決議的移除項目<2>,  Up: C API 變更<2>

1.3.16.5 已移除
...............

   * ‘PyFrame_BlockSetup()’ and ‘PyFrame_BlockPop()’ have been removed.
     (Contributed by Mark Shannon in bpo-40222(1).)

   * 移除以下使用到 ‘errno’ 變數的數學巨集：

        * ‘Py_ADJUST_ERANGE1()’

        * ‘Py_ADJUST_ERANGE2()’

        * ‘Py_OVERFLOWED()’

        * ‘Py_SET_ERANGE_IF_OVERFLOW()’

        * ‘Py_SET_ERRNO_ON_MATH_ERROR()’

     （由 Victor Stinner 於 bpo-45412(2) 中所貢獻。）

   * 移除在 Python 3.3 中棄用的 ‘Py_UNICODE_COPY()’ 和
     ‘Py_UNICODE_FILL()’。請改用 ‘PyUnicode_CopyCharacters()’ 或
     ‘memcpy()’（‘wchar_t*’ 字串）和 ‘PyUnicode_Fill()’ 函式。（由
     Victor Stinner 於 bpo-41123(3) 中所貢獻。）

   * 移除 ‘pystrhex.h’ 標頭檔案。它只有包含私有函式。C 的擴充應該只要引
     入主要的 ‘<Python.h>’ 標頭檔案。（由 Victor Stinner 於 bpo-45434(4)
     中所貢獻。）

   * 移除 ‘Py_FORCE_DOUBLE()’ 巨集。它先前被用於 ‘Py_IS_INFINITY()’ 巨集
     。（由 Victor Stinner 於 bpo-45440(5) 中所貢獻。）

   * 當 *note Py_LIMITED_API: 35a. 有被定義時，以下項目將無法被取得：

        * *note PyMarshal_WriteLongToFile(): 73a.

        * *note PyMarshal_WriteObjectToFile(): 73b.

        * *note PyMarshal_ReadObjectFromString(): 73c.

        * *note PyMarshal_WriteObjectToString(): 73d.

        * ‘Py_MARSHAL_VERSION’ 巨集

     These are not part of the *note limited API: 73e.

     （由 Victor Stinner 於 bpo-45474(6) 中所貢獻。）

   * 將 *note PyWeakref_GET_OBJECT(): 38a. 排除於受限 C API 之外，它因為
     ‘PyWeakReference’ 結構在受限 C API 中過於晦澀而從未運作。（由
     Victor Stinner 於 bpo-35134(7) 中所貢獻。）

   * 移除 ‘PyHeapType_GET_MEMBERS()’ 巨集，它是不小心才被放到公開的 C
     API 中，應該只能被 Python 內部所使用。請改用
     ‘PyTypeObject.tp_members’。（由 Victor Stinner 於 bpo-40170(8) 中所
     貢獻。）

   * 移除 ‘HAVE_PY_SET_53BIT_PRECISION’ 巨集（移動至內部 C API）。（由
     Victor Stinner 於 bpo-45412(9) 中所貢獻。）

   * 移除 *note Py_UNICODE: 3b8. 編碼器 API，它們自從 Python 3.3 就被棄
     用，非常少用且和推薦的替代方案已無太大關聯。

     被移除的函式為：

        * ‘PyUnicode_Encode()’

        * ‘PyUnicode_EncodeASCII()’

        * ‘PyUnicode_EncodeLatin1()’

        * ‘PyUnicode_EncodeUTF7()’

        * ‘PyUnicode_EncodeUTF8()’

        * ‘PyUnicode_EncodeUTF16()’

        * ‘PyUnicode_EncodeUTF32()’

        * ‘PyUnicode_EncodeUnicodeEscape()’

        * ‘PyUnicode_EncodeRawUnicodeEscape()’

        * ‘PyUnicode_EncodeCharmap()’

        * ‘PyUnicode_TranslateCharmap()’

        * ‘PyUnicode_EncodeDecimal()’

        * ‘PyUnicode_TransformDecimalToASCII()’

     詳情請見 PEP 624(10) 與 搬遷指南(11)。（由 Inada Naoki 於
     bpo-44029(12) 中所貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40222

   (2) https://bugs.python.org/issue?@action=redirect&bpo=45412

   (3) https://bugs.python.org/issue?@action=redirect&bpo=41123

   (4) https://bugs.python.org/issue?@action=redirect&bpo=45434

   (5) https://bugs.python.org/issue?@action=redirect&bpo=45440

   (6) https://bugs.python.org/issue?@action=redirect&bpo=45474

   (7) https://bugs.python.org/issue?@action=redirect&bpo=35134

   (8) https://bugs.python.org/issue?@action=redirect&bpo=40170

   (9) https://bugs.python.org/issue?@action=redirect&bpo=45412

   (10) https://peps.python.org/pep-0624/

   (11) https://peps.python.org/pep-0624/#alternative-apis

   (12) https://bugs.python.org/issue?@action=redirect&bpo=44029


File: python.info,  Node: Notable changes in 3 11 4,  Next: Notable changes in 3 11 5,  Prev: C API 變更<2>,  Up: Python 3 11 有什麼新功能

1.3.17 Notable changes in 3.11.4
--------------------------------

* Menu:

* tarfile::


File: python.info,  Node: tarfile,  Up: Notable changes in 3 11 4

1.3.17.1 tarfile
................

   * The extraction methods in *note tarfile: c8, and *note
     shutil.unpack_archive(): 412, 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
     *note Extraction filters: 413. for details.  In Python 3.12, use
     without the 'filter' argument will show a *note DeprecationWarning:
     18b.  In Python 3.14, the default will switch to ‘'data'’.
     (Contributed by Petr Viktorin in PEP 706(1).)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0706/


File: python.info,  Node: Notable changes in 3 11 5,  Prev: Notable changes in 3 11 4,  Up: Python 3 11 有什麼新功能

1.3.18 Notable changes in 3.11.5
--------------------------------

* Menu:

* OpenSSL::


File: python.info,  Node: OpenSSL,  Up: Notable changes in 3 11 5

1.3.18.1 OpenSSL
................

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


File: python.info,  Node: Python 3 10 有什麼新功能,  Next: Python 3 9 有什麼新功能,  Prev: Python 3 11 有什麼新功能,  Up: Python 有什麼新功能？

1.4 Python 3.10 有什麼新功能
============================


編輯者: Pablo Galindo Salgado

本文介紹了 Python 3.10 與 3.9 相比的新功能。Python 3.10 於 2021 年 10 月
4 日發布。有關完整詳細資訊，請參閱 *note changelog: 122.。

* Menu:

* 摘要: 摘要 -- 發布重點. 發布重點
* 新功能::
* 與型別提示相關的新功能::
* 其他語言更動: 其他語言更動<3>.
* 新模組::
* 改進的模組: 改進的模組<3>.
* 最佳化: 最佳化<3>.
* 已棄用: 已棄用<5>.
* 已刪除::
* 移植到 Python 3.10: 移植到 Python 3 10.
* CPython 位元組碼變更: CPython 位元組碼變更<3>.
* 建置變更: 建置變更<3>.
* C API 變更: C API 變更<3>.
* Notable security feature in 3.10.7: Notable security feature in 3 10 7.
* Notable security feature in 3.10.8: Notable security feature in 3 10 8.
* Notable changes in 3.10.12: Notable changes in 3 10 12.


File: python.info,  Node: 摘要 -- 發布重點,  Next: 新功能,  Up: Python 3 10 有什麼新功能

1.4.1 摘要 - 發布重點
---------------------

新增語法特性：

   * PEP 634(1)，結構模式匹配 (Structural Pattern Matching)：規範

   * PEP 635(2)，結構模式匹配：動機和基本原理

   * PEP 636(3)，結構模式匹配：教學

   * bpo-12782(4)，現在正式允許帶括號的情境管理器 (context manager)。

標準函式庫中的新功能：

   * PEP 618(5)，新增可選的長度檢查到 zip。

直譯器改進：

   * PEP 626(6)，用於除錯和其他工具的精確列號。

新的 typing 功能：

   * PEP 604(7)，允許將聯集型別 (union types) 寫為 X | Y

   * PEP 612(8)，參數規範變數 (Parameter Specification Variables)

   * PEP 613(9)，顯式型別別名 (Explicit Type Aliases)

   * PEP 647(10)，使用者定義的型別防護 (User-Defined Type Guards)

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

   * PEP 644(11)，需要 OpenSSL 1.1.1 或更高版本

   * PEP 632(12)，棄用 distutils 模組。

   * PEP 623(13)，棄用並準備刪除 PyUnicodeObject 中的 wstr 成員。

   * PEP 624(14)，刪除 Py_UNICODE 編碼器 API

   * PEP 597(15)，新增可選的 EncodingWarning

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0634/

   (2) https://peps.python.org/pep-0635/

   (3) https://peps.python.org/pep-0636/

   (4) https://bugs.python.org/issue?@action=redirect&bpo=12782

   (5) https://peps.python.org/pep-0618/

   (6) https://peps.python.org/pep-0626/

   (7) https://peps.python.org/pep-0604/

   (8) https://peps.python.org/pep-0612/

   (9) https://peps.python.org/pep-0613/

   (10) https://peps.python.org/pep-0647/

   (11) https://peps.python.org/pep-0644/

   (12) https://peps.python.org/pep-0632/

   (13) https://peps.python.org/pep-0623/

   (14) https://peps.python.org/pep-0624/

   (15) https://peps.python.org/pep-0597/


File: python.info,  Node: 新功能,  Next: 與型別提示相關的新功能,  Prev: 摘要 -- 發布重點,  Up: Python 3 10 有什麼新功能

1.4.2 新功能
------------

* Menu:

* 帶括號的情境管理器::
* 更好的錯誤訊息::
* PEP 626：用於除錯和其他工具的精確列號::
* PEP 634：結構模式匹配::
* 可選的 EncodingWarning 和 encoding="locale" 選項::


File: python.info,  Node: 帶括號的情境管理器,  Next: 更好的錯誤訊息,  Up: 新功能

1.4.2.1 帶括號的情境管理器
..........................

現在支援使用成對的括號來將多個情境管理器以數行表示。這允許了與過去的引入
陳述式 (import statement) 類似的方法來格式化一組多行的情境管理器集合。例
如，以下範例現在都是有效的：

     with (CtxManager() as example):
         ...

     with (
         CtxManager1(),
         CtxManager2()
     ):
         ...

     with (CtxManager1() as example,
           CtxManager2()):
         ...

     with (CtxManager1(),
           CtxManager2() as example):
         ...

     with (
         CtxManager1() as example1,
         CtxManager2() as example2
     ):
         ...

也可以在封閉群組的末尾使用逗號：

     with (
         CtxManager1() as example1,
         CtxManager2() as example2,
         CtxManager3() as example3,
     ):
         ...

此新語法使用新剖析器的非 LL(1) 功能。檢查 PEP 617(1) 了解更多詳細資訊。

（由 Guido van Rossum、Pablo Galindo 和 Lysandros Nikolaou 在
bpo-12782(2) 和 bpo-40334(3) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0617/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=12782

   (3) https://bugs.python.org/issue?@action=redirect&bpo=40334


File: python.info,  Node: 更好的錯誤訊息,  Next: PEP 626：用於除錯和其他工具的精確列號,  Prev: 帶括號的情境管理器,  Up: 新功能

1.4.2.2 更好的錯誤訊息
......................

* Menu:

* SyntaxErrors::
* IndentationErrors::
* AttributeErrors::
* NameErrors::


File: python.info,  Node: SyntaxErrors,  Next: IndentationErrors,  Up: 更好的錯誤訊息

1.4.2.3 SyntaxErrors
....................

當剖析包含未成對括號或方括號的程式碼時，直譯器現在會包含未成對括號的位置
，而不是顯示 'SyntaxError: unexpected EOF while parsing' 或指向某些不正
確的位置。例如，以下程式碼（注意未閉合的 ‘{’ ）：

     expected = {9: 1, 18: 2, 19: 2, 27: 3, 28: 3, 29: 3, 36: 4, 37: 4,
                 38: 4, 39: 4, 45: 5, 46: 5, 47: 5, 48: 5, 49: 5, 54: 6,
     some_other_code = foo()

以前版本的直譯器會在奇怪的地方顯示有語法錯誤：

     File "example.py", line 3
         some_other_code = foo()
                         ^
     SyntaxError: invalid syntax

但在 Python 3.10 中，會發出一個資訊更豐富的錯誤：

     File "example.py", line 1
         expected = {9: 1, 18: 2, 19: 2, 27: 3, 28: 3, 29: 3, 36: 4, 37: 4,
                    ^
     SyntaxError: '{' was never closed

同樣地，涉及未成對字串字面值（單引號和三引號）的錯誤現在會指向字串的開頭
，而不是報告 EOF/EOL。

這些改進是受到 PyPy 直譯器的啟發。

（由 Pablo Galindo 在 bpo-42864(1) 和 Batuhan Taskaya 在 bpo-40176(2) 中
貢獻。）

直譯器引發的 *note SyntaxError: 173. 例外現在會突顯 (highlight) 構成語法
錯誤之運算式的完整錯誤範圍，而不僅是檢測到問題的位置。如此一來，過去（像
Python 3.10 之前）的：

     >>> foo(x, z for z in range(10), t, w)
       File "<stdin>", line 1
         foo(x, z for z in range(10), t, w)
                ^
     SyntaxError: Generator expression must be parenthesized

現在 Python 3.10 則會將例外顯示為：

     >>> foo(x, z for z in range(10), t, w)
       File "<stdin>", line 1
         foo(x, z for z in range(10), t, w)
                ^^^^^^^^^^^^^^^^^^^^
     SyntaxError: Generator expression must be parenthesized

此改進由 Pablo Galindo 在 bpo-43914(3) 中貢獻。

已合併了大量針對 *note SyntaxError: 173. 例外的新專用訊息。一些最值得注
意的如下：

   * 在區塊之前缺少 ‘:’:

          >>> if rocket.position > event_horizon
            File "<stdin>", line 1
              if rocket.position > event_horizon
                                                ^
          SyntaxError: expected ':'

     （由 Pablo Galindo 在 bpo-42997(4) 中貢獻。）

   * 綜合運算目標中未加括號的元組：

          >>> {x,y for x,y in zip('abcd', '1234')}
            File "<stdin>", line 1
              {x,y for x,y in zip('abcd', '1234')}
               ^
          SyntaxError: did you forget parentheses around the comprehension target?

     （由 Pablo Galindo 在 bpo-43017(5) 中貢獻。）

   * 容器字面值 (collection literals) 中和運算式之間缺少逗號：

          >>> items = {
          ... x: 1,
          ... y: 2
          ... z: 3,
            File "<stdin>", line 3
              y: 2
                 ^
          SyntaxError: invalid syntax. Perhaps you forgot a comma?

     （由 Pablo Galindo 在 bpo-43822(6) 中貢獻。）

   * 不帶括號的多個例外型別：

          >>> try:
          ...     build_dyson_sphere()
          ... except NotEnoughScienceError, NotEnoughResourcesError:
            File "<stdin>", line 3
              except NotEnoughScienceError, NotEnoughResourcesError:
                     ^
          SyntaxError: multiple exception types must be parenthesized

     （由 Pablo Galindo 在 bpo-43149(7) 中貢獻。）

   * 字典字面值中缺少 ‘:’ 和值：

          >>> values = {
          ... x: 1,
          ... y: 2,
          ... z:
          ... }
            File "<stdin>", line 4
              z:
               ^
          SyntaxError: expression expected after dictionary key and ':'

          >>> values = {x:1, y:2, z w:3}
            File "<stdin>", line 1
              values = {x:1, y:2, z w:3}
                                  ^
          SyntaxError: ':' expected after dictionary key

     （由 Pablo Galindo 在 bpo-43823(8) 中貢獻。）

   * 沒有 ‘except’ 或 ‘finally’ 區塊的 ‘try’ 區塊：

          >>> try:
          ...     x = 2
          ... something = 3
            File "<stdin>", line 3
              something  = 3
              ^^^^^^^^^
          SyntaxError: expected 'except' or 'finally' block

     （由 Pablo Galindo 在 bpo-44305(9) 中貢獻。）

   * 於比較中使用 ‘=’ 而非 ‘==’：

          >>> if rocket.position = event_horizon:
            File "<stdin>", line 1
              if rocket.position = event_horizon:
                                 ^
          SyntaxError: cannot assign to attribute here. Maybe you meant '==' instead of '='?

     （由 Pablo Galindo 在 bpo-43797(10) 中貢獻。）

   * f 字串中使用 ‘*’：

          >>> f"Black holes {*all_black_holes} and revelations"
            File "<stdin>", line 1
              (*all_black_holes)
               ^
          SyntaxError: f-string: cannot use starred expression here

     （由 Pablo Galindo 在 bpo-41064(11) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42864

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40176

   (3) https://bugs.python.org/issue?@action=redirect&bpo=43914

   (4) https://bugs.python.org/issue?@action=redirect&bpo=42997

   (5) https://bugs.python.org/issue?@action=redirect&bpo=43017

   (6) https://bugs.python.org/issue?@action=redirect&bpo=43822

   (7) https://bugs.python.org/issue?@action=redirect&bpo=43149

   (8) https://bugs.python.org/issue?@action=redirect&bpo=43823

   (9) https://bugs.python.org/issue?@action=redirect&bpo=44305

   (10) https://bugs.python.org/issue?@action=redirect&bpo=43797

   (11) https://bugs.python.org/issue?@action=redirect&bpo=41064


File: python.info,  Node: IndentationErrors,  Next: AttributeErrors,  Prev: SyntaxErrors,  Up: 更好的錯誤訊息

1.4.2.4 IndentationErrors
.........................

許多 *note IndentationError: 74c. 例外現在支援更多關於哪種區塊需要縮進的
情境，包括陳述式的位置：

     >>> def foo():
     ...    if lel:
     ...    x = 2
       File "<stdin>", line 3
         x = 2
         ^
     IndentationError: expected an indented block after 'if' statement in line 2


File: python.info,  Node: AttributeErrors,  Next: NameErrors,  Prev: IndentationErrors,  Up: 更好的錯誤訊息

1.4.2.5 AttributeErrors
.......................

當印出 *note AttributeError: 2f6. 時，‘PyErr_Display()’ 將提供引發例外的
物件中類似屬性名稱的建議：

     >>> collections.namedtoplo
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     AttributeError: module 'collections' has no attribute 'namedtoplo'. Did you mean: namedtuple?

（由 Pablo Galindo 在 bpo-38530(1) 中貢獻。）

     警告: 請注意，如果未呼叫 ‘PyErr_Display()’ 來顯示錯誤（可能為了要使
     用其他自定義錯誤顯示函式），則此操作將不起作用。這是 IPython 等某些
     REPL 中的常見狀況。

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38530


File: python.info,  Node: NameErrors,  Prev: AttributeErrors,  Up: 更好的錯誤訊息

1.4.2.6 NameErrors
..................

當印出直譯器引發的 *note NameError: 3e5. 時，‘PyErr_Display()’ 將在引發
例外的函式中提供類似變數名稱的建議：

     >>> schwarzschild_black_hole = None
     >>> schwarschild_black_hole
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     NameError: name 'schwarschild_black_hole' is not defined. Did you mean: schwarzschild_black_hole?

（由 Pablo Galindo 在 bpo-38530(1) 中貢獻。）

     警告: 請注意，如果未呼叫 ‘PyErr_Display()’ 來顯示錯誤，則此操作將不
     起作用，如果使用其他自定義錯誤顯示函式，則可能會發生這種情況。這是
     IPython 等某些 REPL 中的常見場景。

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38530


File: python.info,  Node: PEP 626：用於除錯和其他工具的精確列號,  Next: PEP 634：結構模式匹配,  Prev: 更好的錯誤訊息,  Up: 新功能

1.4.2.7 PEP 626：用於除錯和其他工具的精確列號
.............................................

PEP 626 為除錯、分析 (profiling) 和覆蓋 (coverage) 工具帶來了更精確、更
可靠的列號 (line numbers)。為所有已執行的程式碼列且僅針對已執行的程式碼
行產生具有正確列號的追蹤事件。

影格 (frame) 物件的 *note f_lineno: 750. 屬性總會包含預期的列號。

*note 程式碼物件: 1b6.的 *note co_lnotab: 2b7. 屬性已棄用，並將在 3.12 中
刪除。需要從偏移量轉換為列號的程式碼應使用新的 *note co_lines(): 2cc. 方
法。


File: python.info,  Node: PEP 634：結構模式匹配,  Next: 可選的 EncodingWarning 和 encoding="locale" 選項,  Prev: PEP 626：用於除錯和其他工具的精確列號,  Up: 新功能

1.4.2.8 PEP 634：結構模式匹配
.............................

已新增結構模式匹配 (structural pattern matching)，其形式為具有關聯操作之
模式的 'match 陳述式' 和 'case 陳述式'。模式由序列、對映、原始資料型別
(primitive data types) 以及類別實例組成。模式匹配使程式能夠從複雜的資料
型別中提取資訊，在資料結構上進行分支，並根據不同形式的資料應用特定的操作
。

* Menu:

* 語法和操作::
* 宣告式方法 (Declarative approach): 宣告式方法 Declarative approach.
* 簡單模式：與字面值匹配::
* 具有字面值和變數的模式::
* 模式和類別::
* 巢狀模式::
* 複雜模式和萬用字元::
* Guard::
* 其他主要功能::


File: python.info,  Node: 語法和操作,  Next: 宣告式方法 Declarative approach,  Up: PEP 634：結構模式匹配

1.4.2.9 語法和操作
..................

模式匹配的通用語法是：

     match subject:
         case <pattern_1>:
             <action_1>
         case <pattern_2>:
             <action_2>
         case <pattern_3>:
             <action_3>
         case _:
             <action_wildcard>

match 陳述式採用一個運算式，並將其值與作為一個或多個 case 區塊給出的連續
模式進行比較。具體來說，模式匹配是透過以下方式進行操作：

  1. 使用具有型態 (type) 和特徵 (shape) 的資料 (主語 ‘subject’)

  2. ‘match’ 陳述式中 ‘subject’ 的求值 (evaluating)

  3. 從上到下將主語與 ‘case’ 陳述式中的每個模式進行比較，直到確認匹配。

  4. 執行與已確認匹配模式對應的操作

  5. 如果未確認完全匹配，則最後一種情況，即萬用字元 ‘_’ （如果有提供）將
     作為匹配到的情況。如未有任何匹配且不存在萬用字元的 case，則整個
     match 區塊會是個無操作 (no-op)。


File: python.info,  Node: 宣告式方法 Declarative approach,  Next: 簡單模式：與字面值匹配,  Prev: 語法和操作,  Up: PEP 634：結構模式匹配

1.4.2.10 宣告式方法 (Declarative approach)
..........................................

讀者可能會透過使用 C、Java 或 JavaScript（以及許多其他語言）中的 switch
陳述式將主語（資料物件）與字面值 (literal)（模式）進行匹配的簡單範例來了
解模式匹配。 switch 語句通常用於將物件/運算式與包含字面值的 case 陳述式
進行比較。

更強大的模式匹配範例可以在 Scala 和 Elixir 等語言中找到。對於結構模式匹
配，該方法是「宣告式的 (declarative)」，並且明確地說明了資料匹配的條件（
模式）。

雖然使用巢狀 "if" 陳述式的「命令式 (imperative)」指令系列可用於完成類似
於結構模式匹配的操作，但它不如「聲明式 (declarative)」方法清晰。相反地，
「聲明式」方法規定了匹配所需滿足的條件，並且因其明確表達模式而更具可讀性
。雖然結構模式匹配可以用其最簡單的形式達成，將變數與 case 陳述式中的字面
值進行比較，但它對 Python 的真正價值在於它對主語的型態和特徵的處理。


File: python.info,  Node: 簡單模式：與字面值匹配,  Next: 具有字面值和變數的模式,  Prev: 宣告式方法 Declarative approach,  Up: PEP 634：結構模式匹配

1.4.2.11 簡單模式：與字面值匹配
...............................

讓我們將此範例視為最簡單形式的模式匹配：一個值（主語）與多個文字（模式）
匹配。在下面的範例中，‘status’ 是匹配陳述式的主語。這些模式是每個 case 陳
述式，其中文字表示請求狀態程式碼。與案例相關的操作在匹配後執行：

     def http_error(status):
         match status:
             case 400:
                 return "Bad request"
             case 404:
                 return "Not found"
             case 418:
                 return "I'm a teapot"
             case _:
                 return "Something's wrong with the internet"

如果上面的函式傳遞了 418 ‘status’，則回傳 "I'm a teapot"。如果上面的函式
傳遞了 500 ‘status’，則帶有 ‘_’ 的 case 語句將作為萬用字元進行匹配，並回
傳 "Something's wrong with the internet"。請注意最後一個區塊：變數名稱
‘_’ 充當 '萬用字元' 並確保主語始終匹配。‘_’ 的使用是可選的。

你可以使用 ‘|’ ("or") 將多個字面值組合在一個模式中：

     case 401 | 403 | 404:
         return "Not allowed"

* Menu:

* 沒有萬用字元 (wildcard) 的行為: 沒有萬用字元 wildcard 的行為.


File: python.info,  Node: 沒有萬用字元 wildcard 的行為,  Up: 簡單模式：與字面值匹配

1.4.2.12 沒有萬用字元 (wildcard) 的行為
.......................................

如果我們透過刪除最後一個 case 區塊來修改上面的範例，則範例將變為：

     def http_error(status):
         match status:
             case 400:
                 return "Bad request"
             case 404:
                 return "Not found"
             case 418:
                 return "I'm a teapot"

如果在 case 陳述式中不使用 ‘_’，則可能不存在匹配項目。如果不存在匹配項目
，則該行為是無操作 (no-op)。例如，如果 ‘status’ 為 500，則不會有任何操作
。


File: python.info,  Node: 具有字面值和變數的模式,  Next: 模式和類別,  Prev: 簡單模式：與字面值匹配,  Up: PEP 634：結構模式匹配

1.4.2.13 具有字面值和變數的模式
...............................

模式看起來就像解包賦值 (unpacking assignment)，並且模式可用於繫結 (bind)
變數。在此範例中，可以將資料點解包為其 x 坐標和 y 坐標：

     # point is an (x, y) tuple
     match point:
         case (0, 0):
             print("Origin")
         case (0, y):
             print(f"Y={y}")
         case (x, 0):
             print(f"X={x}")
         case (x, y):
             print(f"X={x}, Y={y}")
         case _:
             raise ValueError("Not a point")

第一個模式有兩個字面值 ‘(0, 0)’，並且可以被認為是上面顯示的字面值模式的
擴充。接下來的兩個模式組合了一個字面值和一個變數，並且變數'繫結'來自主語
（‘point’）的值。第四個模式捕獲兩個值，這使得它在概念上類似於解包賦值
‘(x, y) = point’。


File: python.info,  Node: 模式和類別,  Next: 巢狀模式,  Prev: 具有字面值和變數的模式,  Up: PEP 634：結構模式匹配

1.4.2.14 模式和類別
...................

如果你使用類別來建構資料，則可以用類別名稱與後面的引數列表組合成的建構函
式作為模式。該模式能夠將類別屬性捕獲到變數中：

     class Point:
         x: int
         y: int

     def location(point):
         match point:
             case Point(x=0, y=0):
                 print("Origin is the point's location.")
             case Point(x=0, y=y):
                 print(f"Y={y} and the point is on the y-axis.")
             case Point(x=x, y=0):
                 print(f"X={x} and the point is on the x-axis.")
             case Point():
                 print("The point is located somewhere else on the plane.")
             case _:
                 print("Not a point")

* Menu:

* 具有位置參數的模式::


File: python.info,  Node: 具有位置參數的模式,  Up: 模式和類別

1.4.2.15 具有位置參數的模式
...........................

你可以將位置參數與一些會為其屬性排序的內建類別（例如 dataclasses）一起使
用。你還可以通過在類別中設定 ‘__match_args__’ 特殊屬性來定義模式中屬性的
特定位置。如果它被設定為 ("x", "y")，則以下模式都是等效的（且都將 ‘y’ 屬
性繫結到 ‘var’ 變數）：

     Point(1, var)
     Point(1, y=var)
     Point(x=1, y=var)
     Point(y=var, x=1)


File: python.info,  Node: 巢狀模式,  Next: 複雜模式和萬用字元,  Prev: 模式和類別,  Up: PEP 634：結構模式匹配

1.4.2.16 巢狀模式
.................

模式可以任意巢套。例如，如果我們的資料是一個簡短的座標點列表，則可以這樣
匹配：

     match points:
         case []:
             print("No points in the list.")
         case [Point(0, 0)]:
             print("The origin is the only point in the list.")
         case [Point(x, y)]:
             print(f"A single point {x}, {y} is in the list.")
         case [Point(0, y1), Point(0, y2)]:
             print(f"Two points on the Y axis at {y1}, {y2} are in the list.")
         case _:
             print("Something else is found in the list.")


File: python.info,  Node: 複雜模式和萬用字元,  Next: Guard,  Prev: 巢狀模式,  Up: PEP 634：結構模式匹配

1.4.2.17 複雜模式和萬用字元
...........................

到目前為止，範例在最後一個 case 陳述式中單獨使用了 ‘_’。萬用字元可以用在
更複雜的模式中，像是 ‘('error', code, _)’。例如：

     match test_variable:
         case ('warning', code, 40):
             print("A warning has been received.")
         case ('error', code, _):
             print(f"An error {code} occurred.")

在上述情況下，值像是 ('error', code, 100) 和 ('error', code, 800) 的
‘test_variable’ 將會成功匹配。


File: python.info,  Node: Guard,  Next: 其他主要功能,  Prev: 複雜模式和萬用字元,  Up: PEP 634：結構模式匹配

1.4.2.18 Guard
..............

我們可以在模式中新增一個 ‘if’ 子句，稱為 "guard"。如果 guard 為 false，
則 ‘match’ 會繼續嘗試下一個 case 區塊。請注意，值的捕獲發生在 guard 的求
值 (evaluate) 之前：

     match point:
         case Point(x, y) if x == y:
             print(f"The point is located on the diagonal Y=X at {x}.")
         case Point(x, y):
             print(f"Point is not on the diagonal.")


File: python.info,  Node: 其他主要功能,  Prev: Guard,  Up: PEP 634：結構模式匹配

1.4.2.19 其他主要功能
.....................

其他幾個主要功能：

   - 與賦值的解包一樣，tuple 和 list 模式具有完全相同的含義，並且實際上
     匹配任意序列。從技術上來說，主語必須是一個序列。因此，一個重要的例
     外是模式不會去匹配疊代器。另外，為了防止常常出錯，序列模式也不會去
     匹配字串。

   - 序列模式支援萬用字元：‘[x, y, *rest]’ 和 ‘(x, y, *rest)’ 與解包賦值
     中的萬用字元類似。 ‘*’ 後面的名稱也可能是 ‘_’，因此 ‘(x, y, *_)’ 會
     匹配至少兩個項目的序列，且不繫結其餘項目。

   - 對映模式： ‘{"bandwidth": b, "latency": l}’ 從字典中捕獲
     ‘"bandwidth"’ 和 ‘"latency"’ 值。與序列模式不同，額外的鍵將被忽略。
     也支援萬用字元 ‘**rest’。（但是 ‘**_’ 是多餘的，所以是不允許的。）

   - 可以使用 ‘as’ 關鍵字捕獲子模式：

          case (Point(x1, y1), Point(x2, y2) as p2): ...

     這將繫結 x1、y1、x2、y2，如同沒有 ‘as’ 子句的情況下所預期的，並將
     p2 繫結到主語的整個第二項目。

   - 大多數字面值都是通過相等進行比較的。然而，單例 ‘True’、‘False’ 和
     ‘None’ 是按標識值 (identity) 來進行比較的。

   - 附名常數 (named constant) 可以在模式中使用。這些附名常數必須有帶有
     點的名稱 (dotted name)，以防止常數被直譯為捕獲的變數：

          from enum import Enum
          class Color(Enum):
              RED = 0
              GREEN = 1
              BLUE = 2

          color = Color.GREEN
          match color:
              case Color.RED:
                  print("I see red!")
              case Color.GREEN:
                  print("Grass is green")
              case Color.BLUE:
                  print("I'm feeling the blues :(")

有關完整規範，請參閱 PEP 634(1)。動機和基本原理位於 PEP 635(2) 中，較完
整的教學位於 PEP 636(3) 中。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0634/

   (2) https://peps.python.org/pep-0635/

   (3) https://peps.python.org/pep-0636/


File: python.info,  Node: 可選的 EncodingWarning 和 encoding="locale" 選項,  Prev: PEP 634：結構模式匹配,  Up: 新功能

1.4.2.20 可選的 ‘EncodingWarning’ 和 ‘encoding="locale"’ 選項
.............................................................

*note TextIOWrapper: 75f. 和 *note open(): 4c0. 的預設編碼取決於平台和區
域設定。由於大多數 Unix 平台都使用 UTF-8，因此在打開 UTF-8 檔案（例如
JSON、YAML、TOML、Markdown）時省略 ‘encoding’ 選項是個常見的 bug，例如：

     # BUG: "rb" mode or encoding="utf-8" should be used.
     with open("data.json") as f:
         data = json.load(f)

為了發現這種錯誤，新增了一個可選的 ‘EncodingWarning’。當 *note
sys.flags.warn_default_encoding: 632. 為 true 且使用特定於語言環境的預設
編碼時，會發出該信號。

新增 ‘-X warn_default_encoding’ 選項和 *note PYTHONWARNDEFAULTENCODING:
760. 來啟用警告。

更多資訊請見 *note 文字編碼: 761.。


File: python.info,  Node: 與型別提示相關的新功能,  Next: 其他語言更動<3>,  Prev: 新功能,  Up: Python 3 10 有什麼新功能

1.4.3 與型別提示相關的新功能
----------------------------

本節介紹影響 PEP 484(1) 型別提示和 *note typing: ed. 模組的主要更改。

* Menu:

* PEP 604：新型聯集運算子::
* PEP 612：參數規範變數::
* PEP 613：型別別名 (TypeAlias): PEP 613：型別別名 TypeAlias.
* PEP 647：使用者定義的型別防護::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0484/


File: python.info,  Node: PEP 604：新型聯集運算子,  Next: PEP 612：參數規範變數,  Up: 與型別提示相關的新功能

1.4.3.1 PEP 604：新型聯集運算子
...............................

引入了一種新的聯集運算子，該運算子啟用像是 ‘X | Y’ 的語法。這提供了一種
在型別提示中更清晰的方式來表達「型別 X 或型別 Y」，來取代使用 *note
typing.Union: 5e1.。

在以前版本的 Python 中，要使用接受多種型別參數之型別提示的函式，要使用
*note typing.Union: 5e1.：

     def square(number: Union[int, float]) -> Union[int, float]:
         return number ** 2

現在可以用更簡潔的方式編寫型別提示：

     def square(number: int | float) -> int | float:
         return number ** 2

這種新語法也接受作為 *note isinstance(): 3e8. 和 *note issubclass():
765. 的第二個引數：

     >>> isinstance(1, int | str)
     True

更多資訊請見 *note 聯合型別 (Union Type): 766. 與 PEP 604(1)。

（由 Maggie Moss 和 Philippe Prados 在 bpo-41428(2) 中貢獻，由 Yurii
Karabas 和 Serhiy Storchaka 在 bpo-44490(3) 中補充。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0604/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=41428

   (3) https://bugs.python.org/issue?@action=redirect&bpo=44490


File: python.info,  Node: PEP 612：參數規範變數,  Next: PEP 613：型別別名 TypeAlias,  Prev: PEP 604：新型聯集運算子,  Up: 與型別提示相關的新功能

1.4.3.2 PEP 612：參數規範變數
.............................

*note typing: ed. 模組中新增了兩個新選項，用於改進為 PEP 484(1)
‘Callable’ 的靜態型別檢查器 (static type checker) 所提供的資訊。

第一個是參數規範變數 (parameter specification variable)。它們用於將一個
可呼叫物件的參數型別轉發到另一個可呼叫物件 - 這是高階函式和裝飾器中常見
的模式。使用範例可以在 *note typing.ParamSpec: 142. 中找到。在過去是沒有
簡單的方法可以如此精確地來為參數型別的依賴關係做型別註釋。

第二個選項是新的 ‘Concatenate’ 運算子。它與參數規範變數結合使用，來對一
個高階、會新增或刪除另一個可呼叫物件參數的可呼叫物件進行型別註釋。使用範
例可以在 *note typing.Concatenate: 768. 中找到。

請參閱 *note typing.Callable: 769.、*note typing.ParamSpec: 142.、*note
typing.Concatenate: 768.、*note typing.ParamSpecArgs: 76a.、*note
typing.ParamSpecKwargs: 76b. 和 PEP 612(2) 以了解更多詳情。

（由 Ken Jin 在 bpo-41559(3) 中貢獻、Jelle Zijlstra 在 bpo-43783(4) 中進
行了小幅改進。PEP 由 Mark Mendoza 編寫。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0484/

   (2) https://peps.python.org/pep-0612/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=41559

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43783


File: python.info,  Node: PEP 613：型別別名 TypeAlias,  Next: PEP 647：使用者定義的型別防護,  Prev: PEP 612：參數規範變數,  Up: 與型別提示相關的新功能

1.4.3.3 PEP 613：型別別名 (TypeAlias)
.....................................

PEP 484(1) 引入了型別別名 (type aliases) 的概念，只要求它們是最高階、未
註釋的賦值 (top-level unannotated assignments)。這種簡單性有時使型別檢查
器難以區分型別別名和普通賦值，尤其是在涉及傳遞參照 (reference) 或無效型
別時。比較如下：

     StrCache = 'Cache[str]'  # a type alias
     LOG_PREFIX = 'LOG[DEBUG]'  # a module constant

現在 *note typing: ed. 模組有一個特殊值 *note TypeAlias: 76d.，它可以讓
你更明確地宣告型別別名：

     StrCache: TypeAlias = 'Cache[str]'  # a type alias
     LOG_PREFIX = 'LOG[DEBUG]'  # a module constant

更多資訊請見 PEP 613(2)。

（由 Mikhail Golubev 在 bpo-41923(3) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0484/

   (2) https://peps.python.org/pep-0613/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=41923


File: python.info,  Node: PEP 647：使用者定義的型別防護,  Prev: PEP 613：型別別名 TypeAlias,  Up: 與型別提示相關的新功能

1.4.3.4 PEP 647：使用者定義的型別防護
.....................................

*note TypeGuard: 148.（型別防護）已新增到 *note typing: ed. 模組中，用以
註釋型別防護函式並改進在型別窄縮 (type narrowing) 期間提供給靜態型別檢查
器的資訊。有關更多資訊，請參閱 *note TypeGuard: 148. 的文件和 PEP
647(1)。

（由 Ken Jin 和 Guido van Rossum 在 bpo-43766(2) 中貢獻。PEP 由 Eric
Traut 編寫。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0647/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43766


File: python.info,  Node: 其他語言更動<3>,  Next: 新模組,  Prev: 與型別提示相關的新功能,  Up: Python 3 10 有什麼新功能

1.4.4 其他語言更動
------------------

   * *note int: 23c. 型別有一個新方法 *note int.bit_count(): 770.，回傳
     給定整數的二進位展開式中 1 的數量，也稱為總體計數 (population
     count)。（由 Niklas Fiekas 在 bpo-29882(1) 中貢獻。）

   * *note dict.keys(): 771.、*note dict.values(): 772. 和 *note
     dict.items(): 773. 回傳的視圖 (view) 現在都有一個 ‘mapping’ 屬性，
     該屬性提供 *note types.MappingProxyType: 414. 包裝原始的字典物件。
     （由 Dennis Sweeney 在 bpo-40890(2) 中貢獻。）

   * PEP 618(3)：*note zip(): 774. 函式現在有一個可選的 ‘strict’ 旗標，
     用於要求所有可疊代物件具有相同的長度。

   * 採用整數引數的內建函式和擴充函式不再接受 *note Decimal: 27c.、*note
     Fraction: 1c7. 以及其他只能在有損失的情況下轉換為整數的物件（例如有
     *note __int__(): 6c0. 方法，但沒有 *note __index__(): 6c1. 方法）。
     （由 Serhiy Storchaka 在 bpo-37999(4) 中貢獻。）

   * 如果 *note object.__ipow__(): 775. 回傳 *note NotImplemented: 776.，
     則該運算子將按預期正確回退到 *note object.__pow__(): 777. 和 *note
     object.__rpow__(): 778. 。（由 Alex Shkop 在 bpo-38302(5) 中貢獻。
     ）

   * 現在可以在集合字面值 (set literals) 和集合綜合運算 (set
     comprehensions) 以及序列索引（但不能是切片）中使用不帶括號的賦值運
     算式 (assignment expressions)。

   * 函式有一個新的 ‘__builtins__’ 屬性，用於在執行函式時查找內建符號，
     而不是查找 ‘__globals__['__builtins__']’ 。如果
     ‘__globals__["__builtins__"]’ 存在，則屬性會以此做初始化，否則從當
     前內建物件 (builtins) 初始化。（由 Mark Shannon 在 bpo-42990(6) 中
     貢獻。）

   * 新增兩個內建函式 - *note aiter(): 779. 和 *note anext(): 77a.，分別
     為 *note iter(): 77b. 和 *note next(): 77c. 提供非同步的對應函式。
     （由 Joshua Bronson、Daniel Pope 和 Justin Wang 在 bpo-31861(7) 中
     貢獻。）

   * 靜態方法 (*note @staticmethod: 358.) 和類別方法 (*note
     @classmethod: 14a.) 現在繼承方法屬性 (‘__module__’, ‘__name__’,
     ‘__qualname__’, ‘__doc__’, ‘__annotations__’) 並有一個新的
     ‘__wrapped__’ 屬性。此外，靜態方法現在可以像是常規函式般呼叫。（由
     Victor Stinner 在 bpo-43682(8) 中貢獻。）

   * 複雜目標（除 PEP 526(9) 定義的 ‘simple name’ 目標之外的所有內容）的
     註釋不再使用 ‘from __future__ import comments’ 造成任何執行環境
     (runtime) 影響。（由 Batuhan Taskaya 在 bpo-42737(10) 中貢獻。）

   * 類別和模組物件現在會根據需求來延遲建立 (lazy-create) 空的註釋字典
     (annotations dicts)。註釋字典存儲在物件的 ‘__dict__’ 中以達成向後相
     容性。這改進了 ‘__annotations__’ 使用方式的最佳實踐方法；有關更多資
     訊，請參閱 *note 註釋 (annotation) 最佳實踐: 77d.。（由 Larry
     Hastings 在 bpo-43901(11) 中貢獻。）

   * 附名運算式或由 ‘yield’、‘yield from’、‘await’ 組成的註釋現在在
     ‘from __future__ import comments’ 下被禁止，因為它們有些不預期的行
     為。（由 Batuhan Taskaya 在 bpo-42725(12) 中貢獻。）

   * 未繫結變數 (unbound variable)、‘super()’ 和其他可能會改變處理註釋之
     符號表 (symbol table) 的運算式，現在在 ‘from __future__ import
     comments’ 下變得無效。（由 Batuhan Taskaya 在 bpo-42725(13) 中貢獻
     。）

   * *note float: 2c8. 型別和 *note decimal.Decimal: 27c. 型別的 NaN 值
     的雜湊值現在取決於物件的標識值 (identity)。以前即使 NaN 值彼此不相
     等，它們也總是被雜湊為 ‘0’。由於在建立包含多個 NaN 的字典和集合時出
     現過多的雜湊衝突 (hash collision)，可能導致潛在的二次方執行環境行為
     (quadratic runtime behavior)。（由 Raymond Hettinger 在
     bpo-43475(14) 中貢獻。）

   * 刪除 *note __debug__: 77e. 常數時將引發 *note SyntaxError: 173. （
     而不是 *note NameError: 3e5.）。（由 Donghee Na 在 bpo-45000(15) 中
     貢獻。）

   * *note SyntaxError: 173. 例外現在具有 ‘end_lineno’ 和 ‘end_offset’ 屬
     性。如果未被決定，它們將會是 ‘None’。（由 Pablo Galindo 在
     bpo-43914(16) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29882

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40890

   (3) https://peps.python.org/pep-0618/

   (4) https://bugs.python.org/issue?@action=redirect&bpo=37999

   (5) https://bugs.python.org/issue?@action=redirect&bpo=38302

   (6) https://bugs.python.org/issue?@action=redirect&bpo=42990

   (7) https://bugs.python.org/issue?@action=redirect&bpo=31861

   (8) https://bugs.python.org/issue?@action=redirect&bpo=43682

   (9) https://peps.python.org/pep-0526/

   (10) https://bugs.python.org/issue?@action=redirect&bpo=42737

   (11) https://bugs.python.org/issue?@action=redirect&bpo=43901

   (12) https://bugs.python.org/issue?@action=redirect&bpo=42725

   (13) https://bugs.python.org/issue?@action=redirect&bpo=42725

   (14) https://bugs.python.org/issue?@action=redirect&bpo=43475

   (15) https://bugs.python.org/issue?@action=redirect&bpo=45000

   (16) https://bugs.python.org/issue?@action=redirect&bpo=43914


File: python.info,  Node: 新模組,  Next: 改進的模組<3>,  Prev: 其他語言更動<3>,  Up: Python 3 10 有什麼新功能

1.4.5 新模組
------------

   * 無。


File: python.info,  Node: 改進的模組<3>,  Next: 最佳化<3>,  Prev: 新模組,  Up: Python 3 10 有什麼新功能

1.4.6 改進的模組
----------------

* Menu:

* asyncio: asyncio<4>.
* argparse: argparse<2>.
* array: array<3>.
* asynchat, asyncore, smtpd: asynchat asyncore smtpd.
* base64: base64<2>.
* bdb::
* bisect::
* codecs::
* collections.abc: collections abc.
* contextlib: contextlib<2>.
* curses::
* dataclasses: dataclasses<2>.
* distutils: distutils<2>.
* doctest: doctest<2>.
* encodings::
* enum: enum<3>.
* fileinput::
* faulthandler::
* gc: gc<2>.
* glob: glob<2>.
* hashlib: hashlib<3>.
* hmac::
* IDLE 和 idlelib::
* importlib.metadata: importlib metadata<2>.
* inspect: inspect<3>.
* itertools: itertools<3>.
* linecache::
* os: os<4>.
* os.path: os path<3>.
* pathlib: pathlib<5>.
* platform::
* pprint::
* py_compile::
* pyclbr::
* shelve::
* statistics: statistics<3>.
* site: site<2>.
* socket: socket<2>.
* ssl: ssl<3>.
* sqlite3: sqlite3<5>.
* sys: sys<4>.
* _thread::
* threading: threading<3>.
* traceback: traceback<3>.
* types: types<3>.
* typing: typing<5>.
* unittest: unittest<5>.
* urllib.parse: urllib parse.
* xml: xml<2>.
* zipimport: zipimport<3>.


File: python.info,  Node: asyncio<4>,  Next: argparse<2>,  Up: 改進的模組<3>

1.4.6.1 asyncio
...............

新增缺少的 ‘connect_accepted_socket()’ 方法。（由 Alex Grönholm 在
bpo-41332(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41332


File: python.info,  Node: argparse<2>,  Next: array<3>,  Prev: asyncio<4>,  Up: 改進的模組<3>

1.4.6.2 argparse
................

argparse 幫助中的誤導性用詞「可選引數 (optional arguments)」已被替換為「
選項 (options)」。某些依賴於精確輸出匹配的測試可能需要進行調整。（由
Raymond Hettinger 在 bpo-9694(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=9694


File: python.info,  Node: array<3>,  Next: asynchat asyncore smtpd,  Prev: argparse<2>,  Up: 改進的模組<3>

1.4.6.3 array
.............

*note array.array: 186. 的 *note index(): 784. 方法現在具有可選的
'start' 和 'stop' 參數。（由 Anders Lorentsen 和 Zackery Spytz 在
bpo-31956(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31956


File: python.info,  Node: asynchat asyncore smtpd,  Next: base64<2>,  Prev: array<3>,  Up: 改進的模組<3>

1.4.6.4 asynchat, asyncore, smtpd
.................................

自 Python 3.6 起，這些模組在其文件中被標記為已棄用。引入時的 *note
DeprecationWarning: 18b. 現已新增到這三個模組中。


File: python.info,  Node: base64<2>,  Next: bdb,  Prev: asynchat asyncore smtpd,  Up: 改進的模組<3>

1.4.6.5 base64
..............

新增 *note base64.b32hexencode(): 787. 和 *note base64.b32hexdecode():
788. 以支援擴充十六進位字母的 Base32 編碼 (Base32 Encoding with Extended
Hex Alphabet)。


File: python.info,  Node: bdb,  Next: bisect,  Prev: base64<2>,  Up: 改進的模組<3>

1.4.6.6 bdb
...........

新增 ‘clearBreakpoints()’ 來重置所有設定的斷點。（由 Irit Katriel 在
bpo-24160(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24160


File: python.info,  Node: bisect,  Next: codecs,  Prev: bdb,  Up: 改進的模組<3>

1.4.6.7 bisect
..............

新增向 *note bisect: d. 模組 API 提供 'key' 函式的可能性。（由 Raymond
Hettinger 在 bpo-4356(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=4356


File: python.info,  Node: codecs,  Next: collections abc,  Prev: bisect,  Up: 改進的模組<3>

1.4.6.8 codecs
..............

新增 *note codecs.unregister(): 78c. 函式來取消註冊 (unregister) 一個編
解碼器的搜索功能。（Hai Shi 在 bpo-41842(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41842


File: python.info,  Node: collections abc,  Next: contextlib<2>,  Prev: codecs,  Up: 改進的模組<3>

1.4.6.9 collections.abc
.......................

*note collections.abc.Callable: 78e. 的*note 參數化泛型 (parameterized
generic): 656. 的 ‘__args__’ 現在與 *note typing.Callable: 769. 一致。
*note collections.abc.Callable: 78e. 泛型現在會將型別參數攤平，類似於
*note typing.Callable: 769. 目前的做法。這意味著
‘collections.abc.Callable[[int, str], str]’ 將具有 ‘(int, str, str)’ 的
‘__args__’；在以前這是 ‘([int, str], str)’。為了允許此更改，現在可以對
*note types.GenericAlias: 78f. 進行子類別化，並且在下標 (subscript)
*note collections.abc.Callable: 78e. 型別時將回傳子類別。請注意，對於無
效形式的 *note collections.abc.Callable: 78e. 參數化可能會引發 *note
TypeError: 4dd.，而在 Python 3.9 中該參數可能會無引發例外地傳遞。（由
Ken Jin 在 bpo-42195(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42195


File: python.info,  Node: contextlib<2>,  Next: curses,  Prev: collections abc,  Up: 改進的模組<3>

1.4.6.10 contextlib
...................

新增 *note contextlib.aclosing(): 791. 情境管理器以安全地關閉非同步產生
器和表示非同步釋放資源的物件。（由 Joongi Kim 和 John Belmonte 在
bpo-41229(1) 中貢獻。）

向 *note contextlib.nullcontext(): 792. 新增非同步情境管理器支援。（由
Tom Gringauz 在 bpo-41543(2) 中貢獻。）

新增 *note AsyncContextDecorator: 793.，用於支援將非同步情境管理器作為裝
飾器使用。

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41229

   (2) https://bugs.python.org/issue?@action=redirect&bpo=41543


File: python.info,  Node: curses,  Next: dataclasses<2>,  Prev: contextlib<2>,  Up: 改進的模組<3>

1.4.6.11 curses
...............

ncurses 6.1 中新增的擴充顏色函式將由 *note curses.color_content(): 795.、
*note curses.init_color(): 796.、*note curses.init_pair(): 797. 和 *note
curses.pair_content(): 798. 透明地使用。新函式 *note
curses.has_extended_color_support(): 799. 表示了底層的 ncurses 函式庫是
否支援擴充顏色。（由 Jeffrey Kintscher 和 Hans Petter Jansson 在
bpo-36982(1) 中貢獻。）

如果 ‘BUTTON5_*’ 常數是由底層 *note curses: 23. 函式庫提供的，那麼它們現
在會在 curses 模組中公開。（由 Zackery Spytz 在 bpo-39273(2) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36982

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39273


File: python.info,  Node: dataclasses<2>,  Next: distutils<2>,  Prev: curses,  Up: 改進的模組<3>

1.4.6.12 dataclasses
....................

* Menu:

* __slots__::
* 僅限關鍵字欄位 (Keyword-only fields): 僅限關鍵字欄位 Keyword-only fields.


File: python.info,  Node: __slots__,  Next: 僅限關鍵字欄位 Keyword-only fields,  Up: dataclasses<2>

1.4.6.13 __slots__
..................

在 *note dataclasses.dataclass(): 1af. 裝飾器中新增了 ‘slots’ 參數。（由
Yurii Karabas 在 bpo-42269(1) 中貢獻）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42269


File: python.info,  Node: 僅限關鍵字欄位 Keyword-only fields,  Prev: __slots__,  Up: dataclasses<2>

1.4.6.14 僅限關鍵字欄位 (Keyword-only fields)
.............................................

dataclasses 現在支援在產生的 __init__ 方法中包含僅限關鍵字的欄位。有多種
方法可以指定僅限關鍵字欄位。

你可以說每個欄位都是關鍵字：

     from dataclasses import dataclass

     @dataclass(kw_only=True)
     class Birthday:
         name: str
         birthday: datetime.date

‘name’ 和 ‘birthday’ 都是產生的 __init__ 方法的僅限關鍵字參數。

你可以在每個欄位的基礎上指定僅限關鍵字：

     from dataclasses import dataclass, field

     @dataclass
     class Birthday:
         name: str
         birthday: datetime.date = field(kw_only=True)

這裡只有 ‘birthday’ 是僅限關鍵字。如果你在各個欄位上設定 ‘kw_only’，請注
意，由於僅限關鍵字欄位需要遵循非僅限關鍵字欄位，因此會有欄位重新排序的相
關規則。詳細資訊請參閱完整的 dataclasses 文件。

你還可以指定 KW_ONLY 標記後面的所有欄位均為僅限關鍵字欄位。這可能是最常
見的用法：

     from dataclasses import dataclass, KW_ONLY

     @dataclass
     class Point:
         x: float
         y: float
         _: KW_ONLY
         z: float = 0.0
         t: float = 0.0

這裡的 ‘z’ 和 ‘t’ 是僅限關鍵字參數，而 ‘x’ 和 ‘y’ 則不是。（由 Eric V.
Smith 在 bpo-43532(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43532


File: python.info,  Node: distutils<2>,  Next: doctest<2>,  Prev: dataclasses<2>,  Up: 改進的模組<3>

1.4.6.15 distutils
..................

整個 ‘distutils’ 套件已被棄用，將在 Python 3.12 中刪除。它指定套件建置的
功能已經完全被第三方套件 ‘setuptools’ 和 ‘packaging’ 所取代，並且大多數
其他常用的 API 都可以在標準函式庫的其他地方被找到（例如 *note platform:
98. 、*note shutil: b3.、*note subprocess: c1. 或 *note sysconfig: c5.）
。目前沒有將 ‘distutils’ 遷移任何其他地方的計畫，且使用其他功能的應用程
式應該開始規劃如何取得程式碼的私有副本。請參閱 PEP 632(1) 的討論。

Python 3.8 中不推薦使用的 ‘bdist_wininst’ 命令已被刪除。現在建議使用
‘bdist_wheel’ 命令來在 Windows 上發布二進位套件。（由 Victor Stinner 在
bpo-42802(2) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0632/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42802


File: python.info,  Node: doctest<2>,  Next: encodings,  Prev: distutils<2>,  Up: 改進的模組<3>

1.4.6.16 doctest
................

當模組未定義 ‘__loader__’ 時，回退到 ‘__spec__.loader’ 。（由 Brett
Cannon 在 bpo-42133(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42133


File: python.info,  Node: encodings,  Next: enum<3>,  Prev: doctest<2>,  Up: 改進的模組<3>

1.4.6.17 encodings
..................

‘encodings.normalize_encoding()’ 現在會忽略非 ASCII 字元。（Hai Shi 在
bpo-39337(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39337


File: python.info,  Node: enum<3>,  Next: fileinput,  Prev: encodings,  Up: 改進的模組<3>

1.4.6.18 enum
.............

*note Enum: 5d6. *note __repr__(): 5c2. 現在會回傳
‘enum_name.member_name’ 、*note __str__(): 5c4. 現在會回傳 ‘member_name’
。可用作模組常數的標準函式庫列舉會有 ‘module_name.member_name’ 的 *note
repr(): 7a1.。（由 Ethan Furman 在 bpo-40066(1) 中貢獻。）

新增 *note enum.StrEnum: 5c0.，為所有成員都是字串的列舉。（由 Ethan
Furman 在 bpo-41816(2) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40066

   (2) https://bugs.python.org/issue?@action=redirect&bpo=41816


File: python.info,  Node: fileinput,  Next: faulthandler,  Prev: enum<3>,  Up: 改進的模組<3>

1.4.6.19 fileinput
..................

在 *note fileinput.input(): 7a3. 和 *note fileinput.FileInput: 6db. 中新
增 'encoding' 和 'errors' 參數。（由 Inada Naoki 在 bpo-43712(1) 中貢獻
。）

當 'mode' 為 "r" 並且檔案有被壓縮時，*note fileinput.hook_compressed():
7a4. 現在會回傳 *note TextIOWrapper: 75f. 物件（和未壓縮檔案一樣）。（由
Inada Naoki 在 bpo-5758(2) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43712

   (2) https://bugs.python.org/issue?@action=redirect&bpo=5758


File: python.info,  Node: faulthandler,  Next: gc<2>,  Prev: fileinput,  Up: 改進的模組<3>

1.4.6.20 faulthandler
.....................

*note faulthandler: 4e. 模組現在可以檢測垃圾收集器 (garbage collector) 在
收集期間是否發生嚴重錯誤。（由 Victor Stinner 在 bpo-44466(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=44466


File: python.info,  Node: gc<2>,  Next: glob<2>,  Prev: faulthandler,  Up: 改進的模組<3>

1.4.6.21 gc
...........

為 *note gc.get_objects(): 7a7.、*note gc.get_referrers(): 7a8. 和 *note
gc.get_referents(): 7a9. 新增稽核掛鉤 (audit hooks)。（由 Pablo Galindo
在 bpo-43439(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43439


File: python.info,  Node: glob<2>,  Next: hashlib<3>,  Prev: gc<2>,  Up: 改進的模組<3>

1.4.6.22 glob
.............

在 *note glob(): 280. 和 *note iglob(): 7ab. 中新增 'root_dir' 和
'dir_fd' 參數，允許指定搜索的根目錄。（由 Serhiy Storchaka 在
bpo-38144(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38144


File: python.info,  Node: hashlib<3>,  Next: hmac,  Prev: glob<2>,  Up: 改進的模組<3>

1.4.6.23 hashlib
................

hashlib 模組需要 OpenSSL 1.1.1 或更高版本。（由 Christian Heimes 在 PEP
644(1) 和 bpo-43669(2) 中貢獻。）

hashlib 模組初步支援 OpenSSL 3.0.0。（由 Christian Heimes 在
bpo-38820(3) 和其他問題中貢獻。）

純 Python 的 *note pbkdf2_hmac(): 4b4. 回退已被棄用。將來只有在有
OpenSSL 支援的建置 Python 中才能夠使用 PBKDF2-HMAC。（由 Christian
Heimes 在 bpo-43880(4) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0644/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43669

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38820

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43880


File: python.info,  Node: hmac,  Next: IDLE 和 idlelib,  Prev: hashlib<3>,  Up: 改進的模組<3>

1.4.6.24 hmac
.............

hmac 模組現在在內部使用 OpenSSL 的 HMAC 實作。（由 Christian Heimes 在
bpo-40645(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40645


File: python.info,  Node: IDLE 和 idlelib,  Next: importlib metadata<2>,  Prev: hmac,  Up: 改進的模組<3>

1.4.6.25 IDLE 和 idlelib
........................

讓 IDLE 調用 *note sys.excepthook(): 7af. （在沒有 ‘-n’ 的情況下啟動時）
。使用者掛鉤 (user hooks) 在以前是被忽略的。（由 Ken Hilton 在
bpo-43008(1) 中貢獻。）

重新排列設定對話框。將 General 分頁拆分為 Windows 和 Shell/Ed 分頁。將擴
充 Help 選單的幫助來源移至 Extensions 分頁。為新選項騰出空間並縮短對話框
，而後者使對話框更好地適應較小的螢幕。（由 Terry Jan Reedy 在
bpo-40468(2) 中貢獻。）將縮排空間設定從 Font 分頁移至新的 Windows 分頁。
（由 Mark Roseman 和 Terry Jan Reedy 在 bpo-33962(3) 中貢獻。）

上述更改已向後移植到 3.9 維護版本。

新增 Shell 側邊欄。將主要提示字元 (‘>>>’) 移至側邊欄。將輔助提示字元（
‘...’）新增到側邊欄。點擊左鍵再拖動能夠選擇一行或多行文字，和編輯器列號
側邊欄操作一樣。選擇文字列後點擊右鍵會顯示帶有「一併複製提示字元 (copy
with prompts)」的情境選單，這會將側邊欄中提示字元與所選文字並排，此選項
也會出現在文字的情境選單上。（由 Tal Einat 在 bpo-37903(4) 中貢獻。）

使用空格而不是製表符號 (tab) 來縮進交互式程式碼。這能夠使交互式程式碼條
目「看起來正確」。新增 shell 側邊欄的主要動機是實現這一點。（由 Terry
Jan Reedy 在 bpo-37892(5) 中貢獻。）

突顯 (highlight) 模式匹配陳述式中的新*note 軟關鍵字 (soft keywords):
7b0. *note match: 7b1.、*note case: 7b1. 和 *note _: 7b2.。然而這種突顯
並不完美，並且在某些罕見的情況下會出錯，包括 ‘case’ 模式中的一些 ‘_’。（
由 Tal Einat 在 bpo-44010(6) 中貢獻。）

3.10 維護版本中的新增功能。

將語法突顯 (syntax highlighting) 應用於 ‘.pyi’ 檔案。（由 Alex Waygood 和
Terry Jan Reedy 在 bpo-45447(7) 中貢獻。）

保存帶有輸入和輸出的 Shell 時，會包含提示字元。（由 Terry Jan Reedy 在
gh-95191(8) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43008

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40468

   (3) https://bugs.python.org/issue?@action=redirect&bpo=33962

   (4) https://bugs.python.org/issue?@action=redirect&bpo=37903

   (5) https://bugs.python.org/issue?@action=redirect&bpo=37892

   (6) https://bugs.python.org/issue?@action=redirect&bpo=44010

   (7) https://bugs.python.org/issue?@action=redirect&bpo=45447

   (8) https://github.com/python/cpython/issues/95191


File: python.info,  Node: importlib metadata<2>,  Next: inspect<3>,  Prev: IDLE 和 idlelib,  Up: 改進的模組<3>

1.4.6.26 importlib.metadata
...........................

與 ‘importlib_metadata’ 4.6 功能相同（歷史(1)）。

*note importlib.metadata 入口點: 267.現在透過新的 *note
importlib.metadata.EntryPoints: 267. 類別提供了以群組和名稱選擇入口點的
更好體驗。有關棄用與用法的更多資訊，請參閱文件中的相容性說明。

新增了 *note importlib.metadata.packages_distributions(): 7b4. 用於將頂
階 Python 模組和套件解析出 *note importlib.metadata.Distribution: 7b5.。

   ---------- Footnotes ----------

   (1) https://importlib-metadata.readthedocs.io/en/latest/history.html


File: python.info,  Node: inspect<3>,  Next: itertools<3>,  Prev: importlib metadata<2>,  Up: 改進的模組<3>

1.4.6.27 inspect
................

當模組未定義 ‘__loader__’ 時，回退到 ‘__spec__.loader’ 。（由 Brett
Cannon 在 bpo-42133(1) 中貢獻。）

新增 *note inspect.get_annotations(): 7b7.，它可以安全地計算物件上定義的
註釋。它是存取各種型別物件註釋的怪作法 (quirks) 的變通解法 (work
around)，並且對其檢查的物件做出很少的假設。 *note
inspect.get_annotations(): 7b7. 也可以正確地取消字串化註釋 (stringized
annotations)。 *note inspect.get_annotations(): 7b7. 現在被認為是存取任
何 Python 物件上定義的註釋字典的最佳實踐；有關使用註釋的最佳實踐的更多資
訊，請參閱 *note 註釋 (annotation) 最佳實踐: 77d.。相關地，*note
inspect.signature(): 6dc.、*note inspect.Signature.from_callable(): 6de.
和 ‘inspect.Signature.from_function()’ 現在呼叫 *note
inspect.get_annotations(): 7b7. 來檢索註釋。這意味著 *note
inspect.signature(): 6dc. 和 *note inspect.Signature.from_callable():
6de. 現在也可以取消字串化註釋。（由 Larry Hastings 在 bpo-43817(2) 中貢
獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42133

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43817


File: python.info,  Node: itertools<3>,  Next: linecache,  Prev: inspect<3>,  Up: 改進的模組<3>

1.4.6.28 itertools
..................

新增 *note itertools.pairwise(): 7b9.。（由 Raymond Hettinger 在
bpo-38200(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38200


File: python.info,  Node: linecache,  Next: os<4>,  Prev: itertools<3>,  Up: 改進的模組<3>

1.4.6.29 linecache
..................

當模組未定義 ‘__loader__’ 時，回退到 ‘__spec__.loader’ 。（由 Brett
Cannon 在 bpo-42133(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42133


File: python.info,  Node: os<4>,  Next: os path<3>,  Prev: linecache,  Up: 改進的模組<3>

1.4.6.30 os
...........

為 VxWorks RTOS 新增 *note os.cpu_count(): 1a8. 支援。（由 Peixing Xin 在
bpo-41440(1) 中貢獻。）

新增函式 *note os.eventfd(): 7bc. 和相關幫助程式來包裝 Linux 上的
‘eventfd2’ 系統呼叫。（由 Christian Heimes 在 bpo-41001(2) 中貢獻。）

新增 *note os.splice(): 7bd. 以允許在兩個檔案描述器 (file descriptor) 之
間移動資料，而無需在核心地址空間 (kernel address space) 和使用者地址空間
(user address space) 之間進行複製，其中檔案描述器之一必須是個 pipe。（由
Pablo Galindo 在 bpo-41625(3) 中貢獻。）

為 macOS 新增 *note O_EVTONLY: 7be.、*note O_FSYNC: 7bf.、*note
O_SYMLINK: 7c0. 和 *note O_NOFOLLOW_ANY: 7c1.。（由 Donghee Na 在
bpo-43106(4) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41440

   (2) https://bugs.python.org/issue?@action=redirect&bpo=41001

   (3) https://bugs.python.org/issue?@action=redirect&bpo=41625

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43106


File: python.info,  Node: os path<3>,  Next: pathlib<5>,  Prev: os<4>,  Up: 改進的模組<3>

1.4.6.31 os.path
................

*note os.path.realpath(): 20a. 現在接受一個 'strict' 僅限關鍵字引數。當
設定為 ‘True’ 時，如果路徑不存在或遇到符號鏈接循環 (symlink loop)，則會
引發 *note OSError: 350.。（由 Barney Gale 在 bpo-43757(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43757


File: python.info,  Node: pathlib<5>,  Next: platform,  Prev: os path<3>,  Up: 改進的模組<3>

1.4.6.32 pathlib
................

新增 *note PurePath.parents: 7c4. 對於切片的支援。 （由 Joshua Cannon 在
bpo-35498(1) 中貢獻。）

向 *note PurePath.parents: 7c4. 新增負索引支援。（由 Yaroslav Pankovych
在 bpo-21041(2) 中貢獻。）

新增替代 ‘link_to()’ 的 *note Path.hardlink_to: 7c5. 方法。新方法與
*note symlink_to(): 7c6. 具有相同的引數順序。（由 Barney Gale 在
bpo-39950(3) 中貢獻。）

*note pathlib.Path.stat(): 7c7. 和 *note chmod(): 7c8. 現在接受
'follow_symlinks' 僅限關鍵字引數，以與 *note os: 91. 模組中的相應函式保
持一致。（由 Barney Gale 在 bpo-39906(4) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35498

   (2) https://bugs.python.org/issue?@action=redirect&bpo=21041

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39950

   (4) https://bugs.python.org/issue?@action=redirect&bpo=39906


File: python.info,  Node: platform,  Next: pprint,  Prev: pathlib<5>,  Up: 改進的模組<3>

1.4.6.33 platform
.................

Add *note platform.freedesktop_os_release(): 7ca. to retrieve operation
system identification from freedesktop.org os-release(1) standard file.
(Contributed by Christian Heimes in bpo-28468(2).)

   ---------- Footnotes ----------

   (1) https://www.freedesktop.org/software/systemd/man/os-release.html

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28468


File: python.info,  Node: pprint,  Next: py_compile,  Prev: platform,  Up: 改進的模組<3>

1.4.6.34 pprint
...............

*note pprint.pprint(): 7cc. 現在接受新的 ‘underscore_numbers’ 關鍵字引數
。（由 sblondon 在 bpo-42914(1) 中貢獻。）

*note pprint: 9c. 現在可以漂亮地印出 *note dataclasses.dataclass: 1af. 實
例。（由 Lewis Gaul 在 bpo-43080(2) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42914

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43080


File: python.info,  Node: py_compile,  Next: pyclbr,  Prev: pprint,  Up: 改進的模組<3>

1.4.6.35 py_compile
...................

將 ‘--quiet’ 選項新增到 *note py_compile: a1. 的命令列界面。（由 Gregory
Schevchenko 在 bpo-38731(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38731


File: python.info,  Node: pyclbr,  Next: shelve,  Prev: py_compile,  Up: 改進的模組<3>

1.4.6.36 pyclbr
...............

將 ‘end_lineno’ 屬性新增到 *note pyclbr.readmodule(): 7cf. 和 *note
pyclbr.readmodule_ex(): 7d0. 回傳的樹中的 ‘Function’ 和 ‘Class’ 物件。它
與現有的（開始） ‘lineno’ 匹配。（由 Aviral Srivastava 在 bpo-38307(1) 中
貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38307


File: python.info,  Node: shelve,  Next: statistics<3>,  Prev: pyclbr,  Up: 改進的模組<3>

1.4.6.37 shelve
...............

現在，*note shelve: b1. 模組在建立 shelve 時預設使用 *note
pickle.DEFAULT_PROTOCOL: 7d2.，而不是 *note pickle: 95. 的協議 ‘3’。（由
Zackery Spytz 在 bpo-34204(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=34204


File: python.info,  Node: statistics<3>,  Next: site<2>,  Prev: shelve,  Up: 改進的模組<3>

1.4.6.38 statistics
...................

新增 *note covariance(): 7d4.、Pearson *note correlation(): 463. 和簡單
*note linear_regression(): 7d5. 函式。（由 Tymoteusz Wołodźko 在
bpo-38490(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38490


File: python.info,  Node: site<2>,  Next: socket<2>,  Prev: statistics<3>,  Up: 改進的模組<3>

1.4.6.39 site
.............

當模組未定義 ‘__loader__’ 時，回退到 ‘__spec__.loader’ 。（由 Brett
Cannon 在 bpo-42133(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42133


File: python.info,  Node: socket<2>,  Next: ssl<3>,  Prev: site<2>,  Up: 改進的模組<3>

1.4.6.40 socket
...............

*note socket.timeout: 7d8. 例外現在是 *note TimeoutError: 7d9. 的別名。
（由 Christian Heimes 在 bpo-42413(1) 中貢獻。）

新增使用 ‘IPPROTO_MPTCP’ 建立 MPTCP socket 的選項（由 Rui Cunha 在
bpo-43571(2) 中貢獻。）

新增 ‘IP_RECVTOS’ 選項以接收服務型別 (type of service, ToS) 或 DSCP/ECN
欄位（由 Georg Sauthoff 在 44077 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42413

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43571


File: python.info,  Node: ssl<3>,  Next: sqlite3<5>,  Prev: socket<2>,  Up: 改進的模組<3>

1.4.6.41 ssl
............

ssl 模組需要 OpenSSL 1.1.1 或更高版本。（由 Christian Heimes 在 PEP
644(1) 和 bpo-43669(2) 中貢獻。）

ssl 模組初步支援 OpenSSL 3.0.0 和新選項 *note OP_IGNORE_UNEXPECTED_EOF:
7db.。（由 Christian Heimes 於 bpo-38820(3)、bpo-43794(4)、
bpo-43788(5)、bpo-43791(6)、bpo-43799(7)、bpo-43920(8)、bpo-43789(9) 和
bpo-43811(10) 貢獻。)

已棄用函式和使用已棄用常數現在會導致 *note DeprecationWarning: 18b.。
*note ssl.SSLContext.options: 7dc. 預設設定有 *note OP_NO_SSLv2: 7dd. 和
*note OP_NO_SSLv3: 7de.，因此無法再次發出設定該旗標的警告。*note
棄用部分: 7df.包含已棄用功能的列表。（由 Christian Heimes 在
bpo-43880(11) 中貢獻。）

ssl 模組現在具有更安全的預設設定。預設情況下禁用沒有前向保密或 SHA-1 MAC
的密碼。安全級別 2 禁止安全性低於 112 位元的弱 RSA、DH 和 ECC 密鑰。
*note SSLContext: 276. 預設為最低協議版本 TLS 1.2。設定基於 Hynek
Schlawack 的研究。（由 Christian Heimes 在 bpo-43998(12) 中貢獻。）

不再正式支援已棄用的協議 SSL 3.0、TLS 1.0 和 TLS 1.1。 Python 不會主動阻
止它們。然而，OpenSSL 建置選項、發行版配置、發行商補丁和密碼套件可能會阻
止交握的成功。

向 *note ssl.get_server_certificate(): 7e0. 函式新增 'timeout' 參數。（
由 Zackery Spytz 在 bpo-31870(13) 中貢獻。）

ssl 模組使用堆疊類型 (heap-types) 和多階段初始化 (multi-phase
initialization)。（由 Christian Heimes 在 bpo-42333(14) 中貢獻。）

新增驗證旗標 *note VERIFY_X509_PARTIAL_CHAIN: 13b.。（由 l0x 在
bpo-40849(15) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0644/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43669

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38820

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43794

   (5) https://bugs.python.org/issue?@action=redirect&bpo=43788

   (6) https://bugs.python.org/issue?@action=redirect&bpo=43791

   (7) https://bugs.python.org/issue?@action=redirect&bpo=43799

   (8) https://bugs.python.org/issue?@action=redirect&bpo=43920

   (9) https://bugs.python.org/issue?@action=redirect&bpo=43789

   (10) https://bugs.python.org/issue?@action=redirect&bpo=43811

   (11) https://bugs.python.org/issue?@action=redirect&bpo=43880

   (12) https://bugs.python.org/issue?@action=redirect&bpo=43998

   (13) https://bugs.python.org/issue?@action=redirect&bpo=31870

   (14) https://bugs.python.org/issue?@action=redirect&bpo=42333

   (15) https://bugs.python.org/issue?@action=redirect&bpo=40849


File: python.info,  Node: sqlite3<5>,  Next: sys<4>,  Prev: ssl<3>,  Up: 改進的模組<3>

1.4.6.42 sqlite3
................

新增 ‘connect/handle()’、*note enable_load_extension(): 7e2. 和 *note
load_extension(): 45f. 的稽核事件。（由 Erlend E. Aasland 在
bpo-43762(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43762


File: python.info,  Node: sys<4>,  Next: _thread,  Prev: sqlite3<5>,  Up: 改進的模組<3>

1.4.6.43 sys
............

新增 *note sys.orig_argv: 7e4. 屬性：傳遞給 Python 可執行檔案的原始命令
列引數列表。（由 Victor Stinner 在 bpo-23427(1) 中貢獻。）

新增 *note sys.stdlib_module_names: 7e5.，其中包含標準函式庫模組的名稱列
表。 （由 Victor Stinner 在 bpo-42955(2) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23427

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42955


File: python.info,  Node: _thread,  Next: threading<3>,  Prev: sys<4>,  Up: 改進的模組<3>

1.4.6.44 _thread
................

*note _thread.interrupt_main(): 7e7. 現在需要一個可選的信號編號來進行模
擬（預設值仍然是 *note signal.SIGINT: 7e8.）。（由 Antoine Pitrou 在
bpo-43356(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43356


File: python.info,  Node: threading<3>,  Next: traceback<3>,  Prev: _thread,  Up: 改進的模組<3>

1.4.6.45 threading
..................

新增 *note threading.gettrace(): 7ea. 和 *note threading.getprofile():
7eb. 分別取得 *note threading.settrace(): 7ec. 和 *note
threading.setprofile(): 7ed. 設定的函式。（由 Mario Corchero 在
bpo-42251(1) 中貢獻。）

新增 *note threading.__excepthook__: 7ee. 以允許取得 *note
threading.excepthook(): 7ef. 的原始值，以防它被設定為損壞或不同的值。（
由 Mario Corchero 在 bpo-42308(2) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42251

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42308


File: python.info,  Node: traceback<3>,  Next: types<3>,  Prev: threading<3>,  Up: 改進的模組<3>

1.4.6.46 traceback
..................

*note format_exception(): 7f1.、*note format_exception_only(): 7f2. 和
*note print_exception(): 7f3. 函式現在可以將例外物件作為僅限位置引數。（
由 Zackery Spytz 和 Matthias Bussonnier 在 bpo-26389(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26389


File: python.info,  Node: types<3>,  Next: typing<5>,  Prev: traceback<3>,  Up: 改進的模組<3>

1.4.6.47 types
..............

重新引入 *note types.EllipsisType: 7f5.、*note types.NoneType: 7f6. 和
*note types.NotImplementedType: 7f7. 類別，提供一組易於型別檢查器直譯的
新型別。（由 Bas van Beek 在 bpo-41810(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41810


File: python.info,  Node: typing<5>,  Next: unittest<5>,  Prev: types<3>,  Up: 改進的模組<3>

1.4.6.48 typing
...............

有關重大更改，請參閱*note 與型別提示相關的新功能: 762.。

*note typing.Literal: 7f9. 的行為已更改為符合 PEP 586(1) 並匹配 PEP 中指
定的靜態型別檢查器的行為。

  1. ‘Literal’ 現在可以刪除重複參數。

  2. ‘Literal’ 物件之間的相等性比較現在與順序無關。

  3. 現在型別的比較會優先於 ‘Literal’ 的比較。例如，‘Literal[0] ==
     Literal[False]’ 先前之求值為 ‘True’，但現在它是 ‘False’。為了支援此
     更改，內部使用的型別快取現在支援了型別的辨認。

  4. 如果 ‘Literal’ 物件的任ㄧ參數不是*note 可雜湊的: 5b5.，那麼它們現在
     將在相等性比較期間引發 *note TypeError: 4dd. 例外。請注意，使用不可
     雜湊的參數宣告 ‘Literal’ 不會引發錯誤：

          >>> from typing import Literal
          >>> Literal[{0}]
          >>> Literal[{0}] == Literal[{False}]
          Traceback (most recent call last):
            File "<stdin>", line 1, in <module>
          TypeError: unhashable type: 'set'

（由 Yurii Karabas 在 bpo-42345(2) 中貢獻。）

新增函式 *note typing.is_typeddict(): 7fa. 來自我審查 (introspect) 註釋
是否為 *note typing.TypedDict: 146.。（由 Patrick Reader 在 bpo-41792(3)
中貢獻。）

僅宣告了資料變數的 ‘typing.Protocol’ 子類別現在在使用 ‘isinstance’ 檢查
時會引發 ‘TypeError’ ，除非它們用 *note runtime_checkable(): 3e9. 裝飾。
此前，這些檢查都是悄無聲息地通過的。如果使用者需要執行環境協議 (runtime
protocol)，則應該使用 ‘runtime_checkable()’ 裝飾器來裝飾其子類別。（由
Yurii Karabas 在 bpo-38908(4) 中貢獻。）

從 ‘typing.io’ 和 ‘typing.re’ 子模組引入現在將發出 *note
DeprecationWarning: 18b.。這些子模組自 Python 3.8 起已被棄用，並將在未來
版本的 Python 中刪除。屬於這些子模組的任何內容都應該直接從 *note typing:
ed. 引入。 （由 Sebastian Rittau 在 bpo-38291(5) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0586/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42345

   (3) https://bugs.python.org/issue?@action=redirect&bpo=41792

   (4) https://bugs.python.org/issue?@action=redirect&bpo=38908

   (5) https://bugs.python.org/issue?@action=redirect&bpo=38291


File: python.info,  Node: unittest<5>,  Next: urllib parse,  Prev: typing<5>,  Up: 改進的模組<3>

1.4.6.49 unittest
.................

新增方法 *note assertNoLogs(): 7fc. 以補足現有的 *note assertLogs():
7fd.。（由 Kit Yan Choi 在 bpo-39385(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39385


File: python.info,  Node: urllib parse,  Next: xml<2>,  Prev: unittest<5>,  Up: 改進的模組<3>

1.4.6.50 urllib.parse
.....................

Python versions earlier than Python 3.10 allowed using both ‘;’ and ‘&’
as query parameter separators in *note urllib.parse.parse_qs(): 25f. and
*note urllib.parse.parse_qsl(): 25e.  Due to security concerns, and to
conform with newer W3C recommendations, this has been changed to allow
only a single separator key, with ‘&’ as the default.  This change also
affects ‘cgi.parse()’ and ‘cgi.parse_multipart()’ as they use the
affected functions internally.  For more details, please see their
respective documentation.  (Contributed by Adam Goldschmidt, Senthil
Kumaran and Ken Jin in bpo-42967(1).)

The presence of newline or tab characters in parts of a URL allows for
some forms of attacks.  Following the WHATWG specification that updates
RFC 3986(2), ASCII newline ‘\n’, ‘\r’ and tab ‘\t’ characters are
stripped from the URL by the parser in *note urllib.parse: f3.
preventing such attacks.  The removal characters are controlled by a new
module level variable ‘urllib.parse._UNSAFE_URL_BYTES_TO_REMOVE’.  (See
gh-88048(3))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42967

   (2) https://datatracker.ietf.org/doc/html/rfc3986.html

   (3) https://github.com/python/cpython/issues/88048


File: python.info,  Node: xml<2>,  Next: zipimport<3>,  Prev: urllib parse,  Up: 改進的模組<3>

1.4.6.51 xml
............

新增 *note LexicalHandler: 800. 類別到 *note xml.sax.handler: 111. 模組
。（由 Jonathan Gossage 和 Zackery Spytz 在 bpo-35018(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35018


File: python.info,  Node: zipimport<3>,  Prev: xml<2>,  Up: 改進的模組<3>

1.4.6.52 zipimport
..................

新增與 PEP 451(1) 相關的方法：*note find_spec(): 802.、*note
zipimport.zipimporter.create_module(): 803. 和 *note
zipimport.zipimporter.exec_module(): 2e4.。（由 Brett Cannon 在
bpo-42131(2) 中貢獻。）

新增 *note invalidate_caches(): 804. 方法。（由 Desmond Cheong 在
bpo-14678(3) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0451/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42131

   (3) https://bugs.python.org/issue?@action=redirect&bpo=14678


File: python.info,  Node: 最佳化<3>,  Next: 已棄用<5>,  Prev: 改進的模組<3>,  Up: Python 3 10 有什麼新功能

1.4.7 最佳化
------------

   * 建構函式 *note str(): 3f2.、*note bytes(): 1a5. 和 *note
     bytearray(): 4e3. 現在更快了（對於小型物件大約快了 30-40%）。（由
     Serhiy Storchaka 在 bpo-41334(1) 中貢獻。）

   * *note runpy: ac. 模組現在引入更少的模組。‘python3 -m module-name’ 指
     令啟動時間平均快了 1.4 倍。在 Linux 上，‘python3 -I -m module-name’
     在 Python 3.9 上引入 69 個模組，而在 Python 3.10 上僅引入 51 個模組
     (-18)。（由 Victor Stinner 在 bpo-41006(2) 和 bpo-41718(3) 中貢獻。
     ）

   * ‘LOAD_ATTR’ 指令現在使用新的「操作碼快取 (per opcode cache)」機制。
     現在一般屬性的速度提高了約 36%，槽位 (slot) 的速度提高了 44%。（由
     Pablo Galindo 和 Yury Selivanov 在 bpo-42093(4) 中以及 Guido van
     Rossum 在 bpo-42927(5) 中貢獻，基於最初在 PyPy 和 MicroPython 中實
     作的想法。）

   * 當使用 *note -enable-optimizations: 806. 建置 Python 時，現在
     ‘-fno-semantic-interposition’ 被新增到編譯和鏈接列 (link line) 中。
     這使得使用 *note -enable-shared: 807. 和 ‘gcc’ 建立的 Python 直譯器
     的建置速度提高了 30%。請參閱本文(6) 以了解詳情。（由 Victor Stinner
     和 Pablo Galindo 在 bpo-38980(7) 中貢獻。）

   * 對 *note bz2: f. / *note lzma: 7e. / *note zlib: 119. 模組使用新的
     輸出緩衝區管理程式碼，並將 ‘.readall()’ 函式新增到
     ‘_compression.DecompressReader’ 類別。 bz2 解壓縮速度提高了 1.09x ~
     1.17x，lzma 解壓縮速度提高了 1.20x ~ 1.32x，‘GzipFile.read(-1)’ 速
     度提高了 1.11x ~ 1.18x。（由 Ma Lin 於 bpo-41486(8) 貢獻、由
     Gregory P. Smith 審閱）

   * 使用字串化註釋時，建立函式時不再建立函式的註釋字典。取而代之的是它
     們被存儲為字串元組，且函式物件會根據需求才將其延遲轉換 (lazily
     convert) 為註釋字典。此最佳化將定義帶有註釋的函式所需的 CPU 時間減
     少了一半。（由 Yurii Karabas 和 Inada Naoki 在 bpo-42202(9) 中貢獻
     。）

   * 像是 ‘str1 in str2’ 和 ‘str2.find(str1)’ 之類的子字串搜索函式現在有
     時會使用 Crochemore & Perrin 的「雙向」字串搜索演算法來避免作用於長
     字串上時發生二次方行為 (quadratic behavior)。（由 Dennis Sweeney 在
     bpo-41972(10) 中貢獻）

   * 向 ‘_PyType_Lookup()’ 新增微最佳化以提高快取命中的常見情況下的型別
     屬性快取查找性能。這使得直譯器平均速度提高了 1.04 倍。（由 Dino
     Viehland 在 bpo-43452(11) 中貢獻。）

   * 以下內建函式現在支援更快的 PEP 590(12) vectorcall 呼叫慣例：*note
     map(): 808.、*note filter(): 809.、*note reversed(): 80a.、*note
     bool(): 40e. 和 *note float(): 2c8.。（由 Donghee Na 和 Jeroen
     Demeyer 在 bpo-43575(13)、bpo-43287(14)、bpo-41922(15)、
     bpo-41873(16) 和 bpo-41870(17) 中貢獻。）

   * 通過刪除內部 ‘RLock’，*note BZ2File: 80b. 的性能得到了改進。這使得
     ‘BZ2File’ 在面對多個同時的讀取器或寫入器時執行緒不安全，就像 *note
     gzip: 5d. 和 *note lzma: 7e. 中的等效類別一樣。（由 Inada Naoki 在
     bpo-43785(18) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41334

   (2) https://bugs.python.org/issue?@action=redirect&bpo=41006

   (3) https://bugs.python.org/issue?@action=redirect&bpo=41718

   (4) https://bugs.python.org/issue?@action=redirect&bpo=42093

   (5) https://bugs.python.org/issue?@action=redirect&bpo=42927

   (6) 
https://developers.redhat.com/blog/2020/06/25/red-hat-enterprise-linux-8-2-brings-faster-python-3-8-run-speeds/

   (7) https://bugs.python.org/issue?@action=redirect&bpo=38980

   (8) https://bugs.python.org/issue?@action=redirect&bpo=41486

   (9) https://bugs.python.org/issue?@action=redirect&bpo=42202

   (10) https://bugs.python.org/issue?@action=redirect&bpo=41972

   (11) https://bugs.python.org/issue?@action=redirect&bpo=43452

   (12) https://peps.python.org/pep-0590/

   (13) https://bugs.python.org/issue?@action=redirect&bpo=43575

   (14) https://bugs.python.org/issue?@action=redirect&bpo=43287

   (15) https://bugs.python.org/issue?@action=redirect&bpo=41922

   (16) https://bugs.python.org/issue?@action=redirect&bpo=41873

   (17) https://bugs.python.org/issue?@action=redirect&bpo=41870

   (18) https://bugs.python.org/issue?@action=redirect&bpo=43785


File: python.info,  Node: 已棄用<5>,  Next: 已刪除,  Prev: 最佳化<3>,  Up: Python 3 10 有什麼新功能

1.4.8 已棄用
------------

   * 目前 Python 接受緊跟關鍵字的數字字面值 (numeric literals)，例如
     ‘0in x’、‘1or x’、‘0if 1else 2’。它允許了令人困惑和不明確的運算式，
     例如 ‘[0x1for x in y]’ （可以直譯為 ‘[0x1 for x in y]’ 或 ‘[0x1f or
     x in y]’ ）。從此版本開始，如果數字字面值後緊跟關鍵字 *note and:
     2c2.、*note else: 172.、*note for: 2c3.、*note if: 2c4.、*note in:
     2c5.、*note is: 2c6. 與 *note or: 2c7. 其中之一，則會引發棄用警告。
     在未來的版本中，它將被變更為語法警告，最後成為為語法錯誤。（由
     Serhiy Storchaka 在 bpo-43833(1) 中貢獻。）

   * 從這個版本開始，我們將齊心協力開始清理為相容 Python 2.7 而保留的舊
     引入語義。具體來說， ‘find_loader()’/‘find_module()’ （被 *note
     find_spec(): 80d. 取代）、*note load_module(): 80e. （被 *note
     exec_module(): 80f. 取代）、 ‘module_repr()’ （引入系統負責處理你）
     、‘__package__’ 屬性（由 ‘__spec__.parent’ 取代）、 ‘__loader__’ 屬
     性（由 ‘__spec__.loader’ 取代）和 ‘__cached__’ 屬性（由
     ‘__spec__.cached’ 取代）將慢慢被刪除（以及 *note importlib: 6b. 中
     的其他類別和方法）。將酌情引發 *note ImportWarning: 4a2. 和/或
     *note DeprecationWarning: 18b. 以幫助識別在此轉換期間需要更新的程式
     碼。

   * 整個 ‘distutils’ 命名空間已棄用，將在 Python 3.12 中刪除。請參閱
     *note 模組更改: 6ce. 以獲取更多資訊。

   * *note random.randrange(): 810. 的非整數引數已棄用。*note
     ValueError: 1e7. 已被棄用，取而代之的是 *note TypeError: 4dd.。（由
     Serhiy Storchaka 和 Raymond Hettinger 在 bpo-37319(2) 中貢獻。）

   * *note importlib: 6b. 的各種 ‘load_module()’ 方法自 Python 3.6 起已
     被記錄為已棄用，但現在也會觸發 *note DeprecationWarning: 18b.。請改
     用 *note exec_module(): 80f.。（由 Brett Cannon 在 bpo-26131(3) 中
     貢獻。）

   * ‘zimport.zipimporter.load_module()’ 已被棄用，請用 *note
     exec_module(): 2e4.。（由 Brett Cannon 在 bpo-26131(4) 中貢獻。）

   * 引入系統使用 *note load_module(): 80e. 現在會觸發 *note
     ImportWarning: 4a2.，因為 *note exec_module(): 80f. 是當前首選。（
     由 Brett Cannon 在 bpo-26131(5) 中貢獻。）

   * 引入系統使用 ‘importlib.abc.MetaPathFinder.find_module()’ 和
     ‘importlib.abc.PathEntryFinder.find_module()’ 現在會觸發 *note
     ImportWarning: 4a2.，因為 *note
     importlib.abc.MetaPathFinder.find_spec(): 80d. 和 *note
     importlib.abc.PathEntryFinder.find_spec(): 811. 分別是替代方案的首
     選。你可以使用 *note importlib.util.spec_from_loader(): 812. 來幫助
     移植。（由 Brett Cannon 在 bpo-42134(6) 中貢獻。）

   * 引入系統使用 ‘importlib.abc.PathEntryFinder.find_loader()’ 現在會觸
     發 *note ImportWarning: 4a2.，因為 *note
     importlib.abc.PathEntryFinder.find_spec(): 811. 是首選。你可以使用
     *note importlib.util.spec_from_loader(): 812. 來幫助移植。（由
     Brett Cannon 在 bpo-43672(7) 中貢獻。）

   * ‘importlib.abc.MetaPathFinder.find_module()’ 的各種實作（
     ‘importlib.machinery.BuiltinImporter.find_module()’、
     ‘importlib.machinery.FrozenImporter.find_module()’、
     ‘importlib.machinery.WindowsRegistryFinder.find_module()’、
     ‘importlib.machinery.PathFinder.find_module()’、
     ‘importlib.abc.MetaPathFinder.find_module()’ )、
     ‘importlib.abc.PathEntryFinder.find_module()’
     (‘importlib.machinery.FileFinder.find_module()’ ) 和
     ‘importlib.abc.PathEntryFinder.find_loader()’
     (‘importlib.machinery.FileFinder.find_loader()’ ) 現在引發 *note
     DeprecationWarning: 18b. 並計劃在 Python 3.12 中刪除（之前它們已在
     Python 3.4 中被記錄為已棄用）。（由 Brett Cannon 在 bpo-42135(8) 中
     貢獻。）

   * ‘importlib.abc.Finder’ 已被棄用（包括其唯一方法 ‘find_module()’）。
     *note importlib.abc.MetaPathFinder: 813. 和 *note
     importlib.abc.PathEntryFinder: 814. 都不再從該類別繼承。使用者應該
     根據需求來選擇其一以繼承。（由 Brett Cannon 在 bpo-42135(9) 中貢獻
     。）

   * 棄用 ‘imp’、‘importlib.find_loader()’、
     ‘importlib.util.set_package_wrapper()’、
     ‘importlib.util.set_loader_wrapper()’、
     ‘importlib.util.module_for_loader()’、‘pkgutil.ImpImporter’ 和
     ‘pkgutil.ImpLoader’ 均已更新，將於 Python 3.12 列為預定的刪除版本（
     它們開始在過去版本的 Python 中引發 *note DeprecationWarning: 18b.）
     。（由 Brett Cannon 在 bpo-43720(10) 中貢獻。）

   * 引入系統現在在模組上使用 ‘__spec__’ 屬性，然後才會回退使用
     ‘module_repr()’ 作為模組的 ‘__repr__()’ 方法。計劃在 Python 3.12 中
     刪除 ‘module_repr()’ 的使用。（由 Brett Cannon 在 bpo-42137(11) 中
     貢獻。）

   * ‘importlib.abc.Loader.module_repr()’、
     ‘importlib.machinery.FrozenLoader.module_repr()’ 和
     ‘importlib.machinery.BuiltinLoader.module_repr()’ 已棄用並計劃在
     Python 3.12 中刪除。（由 Brett Cannon 在 bpo-42136(12) 中貢獻。）

   * 自 Python 3.3 起，‘sqlite3.OptimizedUnicode’ 就沒有文件記錄並且已過
     時，當時它被用作 *note str: 3f2. 的別名。它現已被棄用，並計劃在
     Python 3.12 中刪除。（由 Erlend E. Aasland 在 bpo-42264(13) 中貢獻
     。）

   * 未記錄於說明文件的內建函式 ‘sqlite3.enable_shared_cache’ 現已棄用，
     計劃在 Python 3.12 中刪除。SQLite3 文件強烈建議不去使用它。有關更多
     詳細資訊，請參閱 SQLite3 文件(14)。如果必須使用共享快取，請使用
     ‘cache=shared’ 查詢參數以 URI 模式打開資料庫。（由 Erlend E.
     Aasland 在 bpo-24464(15) 中貢獻。）

   * 以下 ‘threading’ 方法現已棄用：

        * ‘threading.currentThread’ => *note threading.current_thread():
          2db.

        * ‘threading.activeCount’ => *note threading.active_count():
          2dc.

        * ‘threading.Condition.notifyAll’ => *note
          threading.Condition.notify_all(): 2d5.

        * ‘threading.Event.isSet’ => *note threading.Event.is_set():
          2d6.

        * ‘threading.Thread.setName’ => *note threading.Thread.name:
          2da.

        * ‘threading.thread.getName’ => *note threading.Thread.name:
          2da.

        * ‘threading.Thread.isDaemon’ => *note threading.Thread.daemon:
          2d8.

        * ‘threading.Thread.setDaemon’ => *note threading.Thread.daemon:
          2d8.

     （由 Jelle Zijlstra 在 gh-87889(16) 中貢獻。）

   * ‘pathlib.Path.link_to()’ 已棄用並計劃在 Python 3.12 中刪除。請改用
     *note pathlib.Path.hardlink_to(): 7c5.。（由 Barney Gale 在
     bpo-39950(17) 中貢獻。）

   * ‘cgi.log()’ 已棄用並計劃在 Python 3.12 中刪除。（由 Inada Naoki 在
     bpo-41139(18) 中貢獻。）

   * 自 Python 3.6、Python 3.7 或 OpenSSL 1.1.0 起，以下 *note ssl: bb.
     功能已被棄用，並將在 3.11 中刪除：

        * ‘OP_NO_SSLv2’、‘OP_NO_SSLv3’、‘OP_NO_TLSv1’、‘OP_NO_TLSv1_1’、
          ‘OP_NO_TLSv1_2’、和 ‘OP_NO_TLSv1_3’ 已被替換為
          ‘minimum_version’ 和 ‘maximum_version’。

        * ‘PROTOCOL_SSLv2’、‘PROTOCOL_SSLv3’、‘PROTOCOL_SSLv23’、
          ‘PROTOCOL_TLSv1’、‘PROTOCOL_TLSv1_1’、‘PROTOCOL_TLSv1_2’ 和
          ‘PROTOCOL_TLS’ 已棄用，取而代之的是 *note PROTOCOL_TLS_CLIENT:
          815. 和 *note PROTOCOL_TLS_SERVER: 816.

        * ‘wrap_socket()’ 被替換為 *note ssl.SSLContext.wrap_socket():
          4c9.

        * ‘match_hostname()’

        * ‘RAND_pseudo_bytes()’, ‘RAND_egd()’

        * NPN 功能如 *note ssl.SSLSocket.selected_npn_protocol(): 817. 和
          *note ssl.SSLContext.set_npn_protocols(): 2d3. 已被 ALPN 取代
          。

   * 執行緒除錯（‘PYTHONTHREADDEBUG’ 環境變數）在 Python 3.10 中已棄用，
     並將在 Python 3.12 中刪除。此功能需要一個 *note Python
     的除錯用建置版本: 1de.。（由 Victor Stinner 在 bpo-44584(19) 中貢獻
     。）

   * 從 ‘typing.io’ 和 ‘typing.re’ 子模組引入現在將發出 *note
     DeprecationWarning: 18b.。這些子模組將在 Python 的未來版本中刪除。
     屬於這些子模組的任何內容都應該直接從 *note typing: ed. 引入。（由
     Sebastian Rittau 在 bpo-38291(20) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43833

   (2) https://bugs.python.org/issue?@action=redirect&bpo=37319

   (3) https://bugs.python.org/issue?@action=redirect&bpo=26131

   (4) https://bugs.python.org/issue?@action=redirect&bpo=26131

   (5) https://bugs.python.org/issue?@action=redirect&bpo=26131

   (6) https://bugs.python.org/issue?@action=redirect&bpo=42134

   (7) https://bugs.python.org/issue?@action=redirect&bpo=43672

   (8) https://bugs.python.org/issue?@action=redirect&bpo=42135

   (9) https://bugs.python.org/issue?@action=redirect&bpo=42135

   (10) https://bugs.python.org/issue?@action=redirect&bpo=43720

   (11) https://bugs.python.org/issue?@action=redirect&bpo=42137

   (12) https://bugs.python.org/issue?@action=redirect&bpo=42136

   (13) https://bugs.python.org/issue?@action=redirect&bpo=42264

   (14) https://sqlite.org/c3ref/enable_shared_cache.html

   (15) https://bugs.python.org/issue?@action=redirect&bpo=24464

   (16) https://github.com/python/cpython/issues/87889

   (17) https://bugs.python.org/issue?@action=redirect&bpo=39950

   (18) https://bugs.python.org/issue?@action=redirect&bpo=41139

   (19) https://bugs.python.org/issue?@action=redirect&bpo=44584

   (20) https://bugs.python.org/issue?@action=redirect&bpo=38291


File: python.info,  Node: 已刪除,  Next: 移植到 Python 3 10,  Prev: 已棄用<5>,  Up: Python 3 10 有什麼新功能

1.4.9 已刪除
------------

   * 刪除了 *note complex: 2c9. 類別的特殊方法 ‘__int__’、‘__float__’、
     ‘__floordiv__’、‘__mod__’、‘__divmod__’、‘__rfloordiv__’、
     ‘__rmod__’ 和 ‘__rdivmod__’ 。它們都會引發 *note TypeError: 4dd.。
     （由 Serhiy Storchaka 在 bpo-41974(1) 中貢獻。）

   * ‘_markupbase’ 模組中私有、未於文件記錄的 ‘ParserBase.error()’ 方法
     已被刪除。*note html.parser.HTMLParser: 81a. 是 ‘ParserBase’ 的唯一
     子類別，它的 ‘error()’ 實作已在 Python 3.5 中刪除。（由 Berker
     Peksag 在 bpo-31844(2) 中貢獻。）

   * 刪除了 ‘unicodedata.ucnhash_CAPI’ 屬性，該屬性是內部 PyCapsule 物件
     。相關的私有 ‘_PyUnicode_Name_CAPI’ 結構已移至內部 C API。（由
     Victor Stinner 在 bpo-42157(3) 中貢獻。）

   * 刪除了由於切換到新的 PEG 剖析器而在 3.9 中被棄用的 ‘parser’ 模組。
     僅由舊剖析器使用的所有 C 原始碼和標頭檔也已被刪除，包括 ‘node.h’、
     ‘parser.h’、‘graminit.h’ 和 ‘grammar.h’。

   * 刪除了公開 C API 函式 ‘PyParser_SimpleParseStringFlags’、
     ‘PyParser_SimpleParseStringFlagsFilename’、
     ‘PyParser_SimpleParseFileFlags’ 和 ‘PyNode_Compile’，這些函式由於切
     換到新的 PEG 剖析器而在 3.9 中被棄用。

   * 刪除了 ‘formatter’ 模組，該模組在 Python 3.4 中已棄用。它有些過時、
     很少被使用，也沒有經過測試。它最初計劃在 Python 3.6 中刪除，但此類
     別的刪除被推遲到 Python 2.7 EOL 之後。現有使用者應該將他們使用的任
     何類別複製到他們的程式碼中。（由 Donghee Na 和 Terry J. Reedy 在
     bpo-42299(4) 中貢獻。）

   * 刪除了 ‘PyModule_GetWarningsModule()’ 函式，該函式現在無用，因為
     ‘_warnings’ 模組在 2.6 中已轉換為內建模組。（由 Hai Shi 在
     bpo-42599(5) 中貢獻。）

   * 從 *note collections: 16. 模組中刪除已棄用的、對 *note Collections
     Abstract Base Classes: 81b. 的別名。（由 Victor Stinner 在
     bpo-37324(6) 中貢獻。）

   * 在 Python 3.8 中棄用後，‘loop’ 參數已從大多數 *note asyncio: 8. 的
     *note 高階 API: 81c. 中刪除。這一變化的背後動機是多方面的：

       1. 這簡化了高階 API。

       2. 自 Python 3.7 以來，高階 API 中的函式一直隱式獲取當前執行緒正
          在運行的事件循環。在大多數正常用例中，不需要將事件循環傳遞給
          API。

       3. 事件循環的傳遞很容易出錯，尤其是在處理在不同執行緒中運行的循環
          時。

     請注意，低階 API 仍會接受 ‘loop’。有關如何替換現有程式碼的範例，請
     參閱 *note Python API 的變化: 81d.。

     （由 Yurii Karabas、Andrew Svetlov、Yury Selivanov 和 Kyle Stanley
     在 bpo-42392(7) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41974

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31844

   (3) https://bugs.python.org/issue?@action=redirect&bpo=42157

   (4) https://bugs.python.org/issue?@action=redirect&bpo=42299

   (5) https://bugs.python.org/issue?@action=redirect&bpo=42599

   (6) https://bugs.python.org/issue?@action=redirect&bpo=37324

   (7) https://bugs.python.org/issue?@action=redirect&bpo=42392


File: python.info,  Node: 移植到 Python 3 10,  Next: CPython 位元組碼變更<3>,  Prev: 已刪除,  Up: Python 3 10 有什麼新功能

1.4.10 移植到 Python 3.10
-------------------------

本節列出了前面描述的更改以及可能需要更改程式碼的其他錯誤修復。

* Menu:

* Python 語法的變化::
* Python API 的變化::
* C API 中的改動::


File: python.info,  Node: Python 語法的變化,  Next: Python API 的變化,  Up: 移植到 Python 3 10

1.4.10.1 Python 語法的變化
..........................

   * 如果數字字面值後面緊跟關鍵字（如 ‘0in x’），在以前是有效的語法，但
     現在在編譯時會發出棄用警告。在未來的版本中，它將更改為語法警告，最
     後更改為語法錯誤。要消除警告並使程式碼與未來版本相容，只需在數字字
     面值和以下關鍵字之間新增一個空格即可。（由 Serhiy Storchaka 在
     bpo-43833(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43833


File: python.info,  Node: Python API 的變化,  Next: C API 中的改動,  Prev: Python 語法的變化,  Up: 移植到 Python 3 10

1.4.10.2 Python API 的變化
..........................

   * *note format_exception(): 7f1.、*note format_exception_only(): 7f2.
     和 *note traceback: e7. 模組中的 *note print_exception(): 7f3. 函式
     的 'etype' 參數已重命名為 'exc'。（由 Zackery Spytz 和 Matthias
     Bussonnier 在 bpo-26389(1) 中貢獻。）

   * *note atexit: 9.：在 Python 退出時，如果一個使用 *note
     atexit.register(): 821. 註冊的回呼 (callback) 失敗，該例外現在會被
     記錄下來。在以前只記錄一些例外，並且最後一個例外總是被默默地忽略。
     （由 Victor Stinner 在 bpo-42639(2) 中貢獻。）

   * *note collections.abc.Callable: 78e. 泛型現在會攤平型別參數，類似於
     *note typing.Callable: 769. 目前的做法。這意味著
     ‘collections.abc.Callable[[int, str], str]’ 將具有 ‘(int, str,
     str)’ 的 ‘__args__’；以前這是 ‘([int, str], str)’。透過 *note
     typing.get_args(): 822. 或 ‘__args__’ 存取參數的程式碼需要考慮此變
     更。此外，對於無效形式的參數化 *note collections.abc.Callable:
     78e.，可能會引發 *note TypeError: 4dd.，而在 Python 3.9 中，該參數
     可能已被默默地傳遞。（由 Ken Jin 在 bpo-42195(3) 中貢獻。）

   * 如果給定參數不適合 16 位元無符號整數 (16-bit unsigned integer)，
     *note socket.htons(): 823. 和 *note socket.ntohs(): 824. 現在會引發
     *note OverflowError: 825. 而不是 *note DeprecationWarning: 18b.。（
     由 Erlend E. Aasland 在 bpo-42393(4) 中貢獻。）

   * 在 Python 3.8 中棄用後，‘loop’ 參數已從大多數 *note asyncio: 8. 的
     *note 高階 API: 81c. 中刪除。

     目前如下所示的協程：

          async def foo(loop):
              await asyncio.sleep(1, loop=loop)

     應替換為：

          async def foo():
              await asyncio.sleep(1)

     如果 ‘foo()’ 被專門設計為 '不' 在當前執行緒的事件循環中運行（例如在
     另一個執行緒的事件循環中運行），請考慮改用 *note
     asyncio.run_coroutine_threadsafe(): 826.。

     （由 Yurii Karabas、Andrew Svetlov、Yury Selivanov 和 Kyle Stanley
     在 bpo-42392(5) 中貢獻。）

   * 如果 'globals' 字典沒有 ‘"__builtins__"’ 鍵，則 *note
     types.FunctionType: 827. 建構函式現在會繼承當前的內建物件，而不是使
     用 ‘{"None": None}’：相同行為如 *note eval(): 163. 和 *note exec():
     162. 函式。在 Python 中使用 ‘def function(...): ...’ 定義函式不受影
     響，全域變數不能用此語法覆蓋：它也繼承當前的內建物件。（由 Victor
     Stinner 在 bpo-42990(6) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26389

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42639

   (3) https://bugs.python.org/issue?@action=redirect&bpo=42195

   (4) https://bugs.python.org/issue?@action=redirect&bpo=42393

   (5) https://bugs.python.org/issue?@action=redirect&bpo=42392

   (6) https://bugs.python.org/issue?@action=redirect&bpo=42990


File: python.info,  Node: C API 中的改動,  Prev: Python API 的變化,  Up: 移植到 Python 3 10

1.4.10.3 C API 中的改動
.......................

   * 由於切換到新的 PEG 剖析器，C API 函式
     ‘PyParser_SimpleParseStringFlags’、
     ‘PyParser_SimpleParseStringFlagsFilename’、
     ‘PyParser_SimpleParseFileFlags’、‘PyNode_Compile’ 和被這些函式使用
     的型別 ‘struct _node’ 被刪除。

     現在應該將源程式碼直接（例如透過 *note Py_CompileString(): 829.）編
     譯為程式碼物件。然後可以（例如透過 *note PyEval_EvalCode(): 82a.）
     為產生的程式碼物件求值 (evaluated)。

     具體來說：

        * 後跟有 ‘PyNode_Compile’ 呼叫的
          ‘PyParser_SimpleParseStringFlags’ 呼叫，可以替換為呼叫 *note
          Py_CompileString(): 829.。

        * 沒有 ‘PyParser_SimpleParseFileFlags’ 的直接替代品。要從 ‘FILE
          *’ 引數編譯程式碼，你需要用 C 讀取檔案並將結果緩衝區傳遞給
          *note Py_CompileString(): 829.。

        * 要編譯給定 ‘char *’ 檔案名稱的檔案，請顯式打開該檔案，讀取它並
          編譯結果。一種方法是使用 *note io: 73. 模組和 *note
          PyImport_ImportModule(): 389.、*note PyObject_CallMethod():
          366.、*note PyBytes_AsString(): 82b. 和 *note
          Py_CompileString(): 829.，如下所示。（宣告和錯誤處理在此被省略
          。）：

               io_module = Import_ImportModule("io");
               fileobject = PyObject_CallMethod(io_module, "open", "ss", filename, "rb");
               source_bytes_object = PyObject_CallMethod(fileobject, "read", "");
               result = PyObject_CallMethod(fileobject, "close", "");
               source_buf = PyBytes_AsString(source_bytes_object);
               code = Py_CompileString(source_buf, filename, Py_file_input);

        * 對於 ‘FrameObject’ 物件，*note f_lasti: 82c. 成員現在表示了字
          碼偏移量 (wordcode offset)，而不是位元組碼字串的簡單偏移量。這
          意味著這個數字需要乘以 2 才能與需要位元組偏移量的 API 一起使用
          （例如 *note PyCode_Addr2Line(): 82d.）。還要注意，
          ‘FrameObject’ 物件的 ‘f_lasti’ 成員不被認為是穩定的：請改用
          *note PyFrame_GetLineNumber(): 72f.。


File: python.info,  Node: CPython 位元組碼變更<3>,  Next: 建置變更<3>,  Prev: 移植到 Python 3 10,  Up: Python 3 10 有什麼新功能

1.4.11 CPython 位元組碼變更
---------------------------

   * ‘MAKE_FUNCTION’ 指令現在接受字典或字串元組作為函式的註釋。（由
     Yurii Karabas 和 Inada Naoki 在 bpo-42202(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42202


File: python.info,  Node: 建置變更<3>,  Next: C API 變更<3>,  Prev: CPython 位元組碼變更<3>,  Up: Python 3 10 有什麼新功能

1.4.12 建置變更
---------------

   * PEP 644(1)：Python 現在需要 OpenSSL 1.1.1 或更高版本。不再支援
     OpenSSL 1.0.2。（由 Christian Heimes 在 bpo-43669(2) 中貢獻。）

   * 現在需要 C99 函式 ‘snprintf()’ 和 ‘vsnprintf()’ 來建置 Python。 （
     由 Victor Stinner 在 bpo-36020(3) 中貢獻。）

   * *note sqlite3: ba. 需要 SQLite 3.7.15 或更新版本。（由 Sergey
     Fedoseev 和 Erlend E. Aasland 在 bpo-40744(4) 和 bpo-40810(5) 中貢
     獻。）

   * *note atexit: 9. 模組現在必須都被建置為內建模組。（由 Victor
     Stinner 在 bpo-42639(6) 中貢獻。）

   * 將 *note -disable-test-modules: 830. 選項新增到 ‘configure’ 腳本中
     ：不建置也不安裝測試模組。（由 Xavier de Gaye、Thomas Petazzoni 和
     Peixing Xin 在 bpo-27640(7) 中貢獻。）

   * 將 *note -with-wheel-pkg-dir=PATH 選項: 831. 新增到 ‘./configure’ 腳
     本中。如果有指定，*note ensurepip: 4b. 模組會在此目錄中查找
     ‘setuptools’ 和 ‘pip’ wheel 套件：如果兩者都存在，則使用這些 wheel
     套件而不是 ensurepip 捆綁的 wheel 套件。

     一些 Linux 發行版的打包策略建議不要一併包入依賴項目。例如，Fedora 在
     ‘/usr/share/python-wheels/’ 目錄中安裝 wheel 套件，並且不安裝
     ‘ensurepip._bundled’ 套件。

     （由 Victor Stinner 在 bpo-42856(8) 中貢獻。）

   * 新增 *note configure -without-static-libpython 選項: 832. 以不建置
     ‘libpythonMAJOR.MINOR.a’ 靜態函式庫且不安裝 ‘python.o’ 目標檔案。

     （由 Victor Stinner 在 bpo-43103(9) 中貢獻。）

   * 如果可用，‘configure’ 腳本現在使用 ‘pkg-config’ 工具程式 (utility)
     來檢測 Tcl/Tk 標頭檔和函式庫的位置。和以前一樣，可以使用
     ‘--with-tcltk-includes’ 和 ‘--with-tcltk-libs’ 配置選項顯式指定這些
     位置。（由 Manolis Stamatogiannakis 在 bpo-42603(10) 中貢獻。）

   * 將 *note -with-openssl-rpath: 833. 選項新增到 ‘configure’ 腳本中。
     該選項簡化了使用自定義 OpenSSL 安裝建置 Python 的過程，例如
     ‘./configure --with-openssl=/path/to/openssl
     --with-openssl-rpath=auto’。（由 Christian Heimes 在 bpo-43466(11)
     中貢獻。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0644/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43669

   (3) https://bugs.python.org/issue?@action=redirect&bpo=36020

   (4) https://bugs.python.org/issue?@action=redirect&bpo=40744

   (5) https://bugs.python.org/issue?@action=redirect&bpo=40810

   (6) https://bugs.python.org/issue?@action=redirect&bpo=42639

   (7) https://bugs.python.org/issue?@action=redirect&bpo=27640

   (8) https://bugs.python.org/issue?@action=redirect&bpo=42856

   (9) https://bugs.python.org/issue?@action=redirect&bpo=43103

   (10) https://bugs.python.org/issue?@action=redirect&bpo=42603

   (11) https://bugs.python.org/issue?@action=redirect&bpo=43466


File: python.info,  Node: C API 變更<3>,  Next: Notable security feature in 3 10 7,  Prev: 建置變更<3>,  Up: Python 3 10 有什麼新功能

1.4.13 C API 變更
-----------------

* Menu:

* PEP 652：維護穩定 ABI::
* 新功能: 新功能<2>.
* 移植到 Python 3.10: 移植到 Python 3 10<2>.
* 已棄用: 已棄用<6>.
* 已刪除: 已刪除<2>.


File: python.info,  Node: PEP 652：維護穩定 ABI,  Next: 新功能<2>,  Up: C API 變更<3>

1.4.13.1 PEP 652：維護穩定 ABI
..............................

用於擴充模組或嵌入 Python 的穩定 ABI（應用程式二進位介面）現已明確定義。
*note C API 穩定性: 4f9. 描述了 C API 和 ABI 穩定性保證以及使用穩定 ABI
的最佳實踐。

（由 Petr Viktorin 在 PEP 652(1) 和 bpo-43795(2) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0652/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43795


File: python.info,  Node: 新功能<2>,  Next: 移植到 Python 3 10<2>,  Prev: PEP 652：維護穩定 ABI,  Up: C API 變更<3>

1.4.13.2 新功能
...............

   * *note PyNumber_Index(): 837. 的結果現在都具有精確的 *note int: 23c.
     型別。在以前，結果可能是 ‘int’ 子類別的實例。（由 Serhiy Storchaka
     在 bpo-40792(1) 中貢獻。）

   * 將新的 *note orig_argv: 838. 成員新增到 *note PyConfig: 371. 結構：
     傳遞給 Python 可執行檔案的原始命令列參數列表。（由 Victor Stinner 在
     bpo-23427(2) 中貢獻。）

   * 新增了 *note PyDateTime_DATE_GET_TZINFO(): 839. 和 *note
     PyDateTime_TIME_GET_TZINFO(): 83a. 巨集，用於存取 *note
     datetime.datetime: 1b0. 和 *note datetime.time: 1b2. 物件的
     ‘tzinfo’ 屬性。（由 Zackery Spytz 在 bpo-30155(3) 中貢獻。）

   * 新增 *note PyCodec_Unregister(): 83b. 函式來取消註冊編解碼器搜索函
     式。（由 Hai Shi 在 bpo-41842(4) 中貢獻。）

   * 新增了 *note PyIter_Send(): 83c. 函式，以允許將值發送到疊代器中，而
     不會引發 ‘StopIteration’ 例外。（由 Vladimir Matveev 在
     bpo-41756(5) 中貢獻。）

   * 將 *note PyUnicode_AsUTF8AndSize(): 83d. 新增到受限 C API (limited
     C API) 中。（由 Alex Gaynor 在 bpo-41784(6) 中貢獻。）

   * 新增 *note PyModule_AddObjectRef(): 308. 函式：類似於 *note
     PyModule_AddObject(): 309. 但成功時不竊取對值的參照。（由 Victor
     Stinner 在 bpo-1635741(7) 中貢獻。）

   * 新增 *note Py_NewRef(): 83e. 和 *note Py_XNewRef(): 83f. 函式來增加
     物件的參照計數並回傳物件。（由 Victor Stinner 在 bpo-42262(8) 中貢
     獻。）

   * *note PyType_FromSpecWithBases(): 524. 和 *note
     PyType_FromModuleAndSpec(): 4f7. 函式現在接受單個類別作為 'bases' 引
     數。（由 Serhiy Storchaka 在 bpo-42423(9) 中貢獻。）

   * *note PyType_FromModuleAndSpec(): 4f7. 函式現在接受 NULL ‘tp_doc’ 槽
     位。（由 Hai Shi 在 bpo-41832(10) 中貢獻。）

   * *note PyType_GetSlot(): 840. 函式可以接受*note 靜態型別 (static
     type): 723.。（由 Hai Shi 和 Petr Viktorin 在 bpo-41073(11) 中貢獻
     。）

   * 向 C-API 新增 *note PySet_CheckExact(): 841. 函式，以檢查物件是否是
     *note set: 57d. 的實例而不是子型別的實例。（由 Pablo Galindo 在
     bpo-43277(12) 中貢獻。）

   * 新增 *note PyErr_SetInterruptEx(): 842.，它允許傳遞信號編號來進行模
     擬。（由 Antoine Pitrou 在 bpo-43356(13) 中貢獻。）

   * 如 *note Python 是在除錯模式 (debug mode): 1de. 下建置的（如果有定
     義 ‘Py_DEBUG’ 巨集），現在會支援受限 C API。在受限 C API 中，如果
     Python 是在除錯模式下建置的，並且 ‘Py_LIMITED_API’ 巨集的目標是
     Python 3.10 或更新版本，*note Py_INCREF(): 514. 和 *note
     Py_DECREF(): 515. 函式現在的實作是不透明函式呼叫，而不是直接存取
     *note PyObject.ob_refcnt: 843. 成員。在除錯模式下支援受限 C API 成
     為可能，因為自 Python 3.8 以來，*note PyObject: 311. 結構在發布和除
     錯模式下是相同的（請參閱:issue:‘36465’）。

     *note -with-trace-refs: 317. 特殊建置（‘Py_TRACE_REFS’ 巨集）仍不支
     援受限 C API。（由 Victor Stinner 在 bpo-43688(14) 中貢獻。）

   * 新增 *note Py_Is(x, y): 844. 函式來測試 'x' 物件是否為 'y' 物件，與
     Python 中的 ‘x is y’ 相同。還新增 *note Py_IsNone(): 845.、*note
     Py_IsTrue(): 846.、*note Py_IsFalse(): 847. 函式來分別測試物件是否
     為 ‘None’ 單例、 ‘True’ 單例或 ‘False’ 單例。（由 Victor Stinner 在
     bpo-43753(15) 中貢獻。）

   * 新增函式以從 C 程式碼控制垃圾收集器：*note PyGC_Enable(): 848.、
     *note PyGC_Disable(): 849.、*note PyGC_IsEnabled(): 84a.。這些函式
     使得能夠從 C 程式碼啟用、停用和查詢垃圾收集器的狀態，而無需引入
     *note gc: 56. 模組。

   * 新增 *note Py_TPFLAGS_DISALLOW_INSTANTIATION: 528. 型別旗標以禁止建
     立型別實例。（由 Victor Stinner 在 bpo-43916(16) 中貢獻。）

   * 新增 *note Py_TPFLAGS_IMMUTABLETYPE: 38d. 型別旗標用於建立不可變型
     別物件：無法設定或刪除型別屬性。（由 Victor Stinner 和 Erlend E.
     Aasland 在 bpo-43908(17) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40792

   (2) https://bugs.python.org/issue?@action=redirect&bpo=23427

   (3) https://bugs.python.org/issue?@action=redirect&bpo=30155

   (4) https://bugs.python.org/issue?@action=redirect&bpo=41842

   (5) https://bugs.python.org/issue?@action=redirect&bpo=41756

   (6) https://bugs.python.org/issue?@action=redirect&bpo=41784

   (7) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (8) https://bugs.python.org/issue?@action=redirect&bpo=42262

   (9) https://bugs.python.org/issue?@action=redirect&bpo=42423

   (10) https://bugs.python.org/issue?@action=redirect&bpo=41832

   (11) https://bugs.python.org/issue?@action=redirect&bpo=41073

   (12) https://bugs.python.org/issue?@action=redirect&bpo=43277

   (13) https://bugs.python.org/issue?@action=redirect&bpo=43356

   (14) https://bugs.python.org/issue?@action=redirect&bpo=43688

   (15) https://bugs.python.org/issue?@action=redirect&bpo=43753

   (16) https://bugs.python.org/issue?@action=redirect&bpo=43916

   (17) https://bugs.python.org/issue?@action=redirect&bpo=43908


File: python.info,  Node: 移植到 Python 3 10<2>,  Next: 已棄用<6>,  Prev: 新功能<2>,  Up: C API 變更<3>

1.4.13.3 移植到 Python 3.10
...........................

   * 現在必須定義 ‘PY_SSIZE_T_CLEAN’ 巨集以使用 *note
     PyArg_ParseTuple(): 517. 和 *note Py_BuildValue(): 84c. 格式，這些
     格式使用 ‘#’: ‘es#’, ‘et#’、‘s#’、‘u#’、‘y#’、‘z#’、‘U#’ 和 ‘Z#’。
     請參閱 *note 剖析引數與建置數值: 84d. 和 PEP 353(1)。（由 Victor
     Stinner 在 bpo-40943(2) 中貢獻。）

   * 由於 *note Py_REFCNT(): 84e. 更改為行內靜態函式 (inline static
     function)，因此 ‘Py_REFCNT(obj) = new_refcnt’ 必須替換為
     ‘Py_SET_REFCNT(obj, new_refcnt)’ ：參見 *note Py_SET_REFCNT(): 84f.
     （自 Python 3.9 起可用）。為了向後相容，可以使用該巨集：

          #if PY_VERSION_HEX < 0x030900A4
          #  define Py_SET_REFCNT(obj, refcnt) ((Py_REFCNT(obj) = (refcnt)), (void)0)
          #endif

     （由 Victor Stinner 在 bpo-39573(3) 中貢獻。）

   * 由於過去的種種原因，過去在不持有 *note GIL: 13e. 的情況下呼叫 *note
     PyDict_GetItem(): 35b. 是被允許的。目前已被禁止。（由 Victor
     Stinner 在 bpo-40839(4) 中貢獻。）

   * ‘PyUnicode_FromUnicode(NULL, size)’ 和
     ‘PyUnicode_FromStringAndSize(NULL, size)’ 現在會引發
     ‘DeprecationWarning’。請改用 *note PyUnicode_New(): 850. 來分配沒有
     初始資料的 Unicode 物件。（由 Inada Naoki 在 bpo-36346(5) 中貢獻。
     ）

   * PyCapsule API ‘unicodedata.ucnhash_CAPI’ 的私有
     ‘_PyUnicode_Name_CAPI’ 結構已移至內部 C API。（由 Victor Stinner 在
     bpo-42157(6) 中貢獻。）

   * 如果在 *note Py_Initialize(): 851. 之前（Python 初始化之前）被呼叫
     ，*note Py_GetPath(): 37e.、*note Py_GetPrefix(): 380.、*note
     Py_GetExecPrefix(): 37c.、*note Py_GetProgramFullPath(): 382.、
     *note Py_GetPythonHome(): 385. 和 *note Py_GetProgramName(): 384. 現
     在會回傳 ‘NULL’。使用新的 *note Python 初始化設定: 372. API 來獲取
     *note Python Path Configuration: 852.。（由 Victor Stinner 在
     bpo-42260(7) 中貢獻。）

   * *note PyList_SET_ITEM(): 306.、*note PyTuple_SET_ITEM(): 305. 和
     *note PyCell_SET(): 853. 巨集不能再用作左值 (l-value) 或右值
     (r-value)。例如，‘x = PyList_SET_ITEM(a, b, c)’ 和
     ‘PyList_SET_ITEM(a, b, c) = x’ 現在會失敗並出現編譯器錯誤。它可以防
     止如 ‘if (PyList_SET_ITEM (a, b, c) < 0) ...’ 測試之類的錯誤。（由
     Zackery Spytz 和 Victor Stinner 在 bpo-30459(8) 中貢獻。）

   * 非受限 API 檔案 ‘odictobject.h’、‘parser_interface.h’、
     ‘picklebufobject.h’、‘pyarena.h’、‘pyctype.h’、‘pydebug.h’、
     ‘pyfpe.h’ 和 ‘pytime.h’ 已移至 ‘Include/cpython’ 目錄。這些檔案不得
     直接被引入，因為它們已於 ‘Python.h’ 中引入；請參閱 *note 引入檔案
     (include files): 728.。如果直接引入它們，請考慮改為引入 ‘Python.h’。
     （由 Nicholas Sim 在 bpo-35134(9) 中貢獻。）

   * 使用 *note Py_TPFLAGS_IMMUTABLETYPE: 38d. 型別旗標來建立不可變型別
     物件。不要依賴 *note Py_TPFLAGS_HEAPTYPE: 854. 來決定型別物件是否可
     變；應改為檢查是否設定了 *note Py_TPFLAGS_IMMUTABLETYPE: 38d.。（由
     Victor Stinner 和 Erlend E. Aasland 在 bpo-35134(10) 中貢獻。）

   * 未以說明文件記錄的函式 ‘Py_FrozenMain’ 已從受限 API 中刪除。該函式
     主要用於 Python 的自定義建置。（由 Petr Viktorin 在 bpo-26241(11) 中
     貢獻。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0353/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40943

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39573

   (4) https://bugs.python.org/issue?@action=redirect&bpo=40839

   (5) https://bugs.python.org/issue?@action=redirect&bpo=36346

   (6) https://bugs.python.org/issue?@action=redirect&bpo=42157

   (7) https://bugs.python.org/issue?@action=redirect&bpo=42260

   (8) https://bugs.python.org/issue?@action=redirect&bpo=30459

   (9) https://bugs.python.org/issue?@action=redirect&bpo=35134

   (10) https://bugs.python.org/issue?@action=redirect&bpo=35134

   (11) https://bugs.python.org/issue?@action=redirect&bpo=26241


File: python.info,  Node: 已棄用<6>,  Next: 已刪除<2>,  Prev: 移植到 Python 3 10<2>,  Up: C API 變更<3>

1.4.13.4 已棄用
...............

   * ‘PyUnicode_InternImmortal()’ 函式現已棄用，並將在 Python 3.12 中刪
     除：請改用 *note PyUnicode_InternInPlace(): 856.。（由 Victor
     Stinner 在 bpo-41692(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41692


File: python.info,  Node: 已刪除<2>,  Prev: 已棄用<6>,  Up: C API 變更<3>

1.4.13.5 已刪除
...............

   * 刪除了操作 ‘Py_UNICODE*’ 字串的 ‘Py_UNICODE_str*’ 函式。（由 Inada
     Naoki 在 bpo-41123(1) 中貢獻。）

        * ‘Py_UNICODE_strlen’：使用 *note PyUnicode_GetLength(): 858. 或
          *note PyUnicode_GET_LENGTH: 859.

        * ‘Py_UNICODE_strcat’：使用 *note PyUnicode_CopyCharacters():
          85a. 或 *note PyUnicode_FromFormat(): 33f.

        * ‘Py_UNICODE_strcpy’、‘Py_UNICODE_strncpy’：使用 *note
          PyUnicode_CopyCharacters(): 85a. 或 *note
          PyUnicode_Substring(): 85b.

        * ‘Py_UNICODE_strcmp’：使用 *note PyUnicode_Compare(): 85c.

        * ‘Py_UNICODE_strncmp’：使用 *note PyUnicode_Tailmatch(): 85d.

        * ‘Py_UNICODE_strchr’、‘Py_UNICODE_strrchr’：使用 *note
          PyUnicode_FindChar(): 85e.

   * 刪除了 ‘PyUnicode_GetMax()’。請改用新的 ( PEP 393(2)) API。（由
     Inada Naoki 在 bpo-41103(3) 中貢獻。）

   * 刪除了 ‘PyLong_FromUnicode()’。請改用 *note
     PyLong_FromUnicodeObject(): 85f.。（由 Inada Naoki 在 bpo-41103(4)
     中貢獻。）

   * 刪除了 ‘PyUnicode_AsUnicodeCopy()’。請改用 *note
     PyUnicode_AsUCS4Copy(): 860. 或 *note PyUnicode_AsWideCharString():
     861. （由 Inada Naoki 在 bpo-41103(5) 中貢獻。）

   * 刪除了 ‘_Py_CheckRecursionLimit’ 變數：它已被 *note
     PyInterpreterState: 862. 結構的 ‘ceval.recursion_limit’ 取代。（由
     Victor Stinner 在 bpo-41834(6) 中貢獻。）

   * 刪除了未被說明文件記錄的巨集 ‘Py_ALLOW_RECURSION’ 和
     ‘Py_END_ALLOW_RECURSION’ 以及 *note PyInterpreterState: 862. 結構的
     ‘recursion_ritic’ 欄位。（由 Serhiy Storchaka 在 bpo-41936(7) 中貢
     獻。）

   * 刪除了未被說明文件記錄的 ‘PyOS_InitInterrupts()’ 函式。初始化
     Python 已經隱式安裝信號處理程式：請參閱 *note
     PyConfig.install_signal_handlers: 863.。（由 Victor Stinner 在
     bpo-41713(8) 中貢獻。）

   * 刪除 ‘PyAST_Validate()’ 函式。不再可能使用公開 C API 來建置 AST 物
     件（‘mod_ty’ 類型）。該函式已被排除在受限 C API 之外 ( PEP 384(9))。
     （由 Victor Stinner 在 bpo-43244(10) 中貢獻。）

   * 刪除 ‘symtable.h’ 標頭檔和未被說明文件記錄的函式：

        * ‘PyST_GetScope()’

        * ‘PySymtable_Build()’

        * ‘PySymtable_BuildObject()’

        * ‘PySymtable_Free()’

        * ‘Py_SymtableString()’

        * ‘Py_SymtableStringObject()’

     ‘Py_SymtableString()’ 函式錯誤地成為穩定 ABI 的一部分，但它因為
     ‘symtable.h’ 標頭檔被排除在受限 C API 之外而無法使用。

     請改用 Python *note symtable: c2. 模組。（由 Victor Stinner 在
     bpo-43244(11) 中貢獻。）

   * 從受限 C API 標頭和 ‘python3.dll’ （在 Windows 上提供穩定 ABI 的函
     式庫）中刪除 *note PyOS_ReadlineFunctionPointer(): 52c.。由於該函式
     採用 FILE* 引數，因此無法保證其 ABI 穩定性。（由 Petr Viktorin 在
     bpo-43868(12) 中貢獻。）

   * 刪除 ‘ast.h’、‘asdl.h’ 和 ‘Python-ast.h’ 標頭檔。這些函式沒有文件記
     錄，並且被排除在受限 C API 之外。這些標頭檔定義的大多數名稱都沒有前
     綴 ‘Py’，因此可能會產生名稱衝突。例如，‘Python-ast.h’ 定義了一個
     ‘Yield’ 巨集，它與 Windows ‘<winbase.h>’ 標頭使用的 ‘Yield’ 有名稱
     衝突。請改用 Python *note ast: 7. 模組。（由 Victor Stinner 在
     bpo-43244(13) 中貢獻。）

   * 刪除編譯器和使用 ‘struct _mod’ 的剖析器函式，因為公開 AST C API 已
     被刪除：

        * ‘PyAST_Compile()’

        * ‘PyAST_CompileEx()’

        * ‘PyAST_CompileObject()’

        * ‘PyFuture_FromAST()’

        * ‘PyFuture_FromASTObject()’

        * ‘PyParser_ASTFromFile()’

        * ‘PyParser_ASTFromFileObject()’

        * ‘PyParser_ASTFromFilename()’

        * ‘PyParser_ASTFromString()’

        * ‘PyParser_ASTFromStringObject()’

     這些函式沒有文件記錄，並且被排除在受限 C API 之外。（由 Victor
     Stinner 在 bpo-43244(14) 中貢獻。）

   * 刪除包含以下函式的 ‘pyarena.h’ 標頭檔：

        * ‘PyArena_New()’

        * ‘PyArena_Free()’

        * ‘PyArena_Malloc()’

        * ‘PyArena_AddPyObject()’

     這些函式沒有文件記錄、被排除在受限 C API 之外，並僅被編譯器於內部使
     用。（由 Victor Stinner 在 bpo-43244(15) 中貢獻。）

   * 為了 Python 最佳化，已刪除 ‘PyThreadState.use_tracing’ 成員。（由
     Mark Shannon 在 bpo-43760(16) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41123

   (2) https://peps.python.org/pep-0393/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=41103

   (4) https://bugs.python.org/issue?@action=redirect&bpo=41103

   (5) https://bugs.python.org/issue?@action=redirect&bpo=41103

   (6) https://bugs.python.org/issue?@action=redirect&bpo=41834

   (7) https://bugs.python.org/issue?@action=redirect&bpo=41936

   (8) https://bugs.python.org/issue?@action=redirect&bpo=41713

   (9) https://peps.python.org/pep-0384/

   (10) https://bugs.python.org/issue?@action=redirect&bpo=43244

   (11) https://bugs.python.org/issue?@action=redirect&bpo=43244

   (12) https://bugs.python.org/issue?@action=redirect&bpo=43868

   (13) https://bugs.python.org/issue?@action=redirect&bpo=43244

   (14) https://bugs.python.org/issue?@action=redirect&bpo=43244

   (15) https://bugs.python.org/issue?@action=redirect&bpo=43244

   (16) https://bugs.python.org/issue?@action=redirect&bpo=43760


File: python.info,  Node: Notable security feature in 3 10 7,  Next: Notable security feature in 3 10 8,  Prev: C API 變更<3>,  Up: Python 3 10 有什麼新功能

1.4.14 Notable security feature in 3.10.7
-----------------------------------------

Converting between *note int: 23c. and *note str: 3f2. in bases other
than 2 (binary), 4, 8 (octal), 16 (hexadecimal), or 32 such as base 10
(decimal) now raises a *note ValueError: 1e7. if the number of digits in
string form is above a limit to avoid potential denial of service
attacks due to the algorithmic complexity.  This is a mitigation for
CVE-2020-10735(1).  This limit can be configured or disabled by
environment variable, command line flag, or *note sys: c3. APIs.  See
the *note integer string conversion length limitation: 599.
documentation.  The default limit is 4300 digits in string form.

   ---------- Footnotes ----------

   (1) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10735


File: python.info,  Node: Notable security feature in 3 10 8,  Next: Notable changes in 3 10 12,  Prev: Notable security feature in 3 10 7,  Up: Python 3 10 有什麼新功能

1.4.15 Notable security feature in 3.10.8
-----------------------------------------

The deprecated ‘mailcap’ module now refuses to inject unsafe text
(filenames, MIME types, parameters) into shell commands.  Instead of
using such text, it will warn and act as if a match was not found (or
for test commands, as if the test failed).  (Contributed by Petr
Viktorin in gh-98966(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/98966


File: python.info,  Node: Notable changes in 3 10 12,  Prev: Notable security feature in 3 10 8,  Up: Python 3 10 有什麼新功能

1.4.16 Notable changes in 3.10.12
---------------------------------

* Menu:

* tarfile: tarfile<2>.


File: python.info,  Node: tarfile<2>,  Up: Notable changes in 3 10 12

1.4.16.1 tarfile
................

   * The extraction methods in *note tarfile: c8, and *note
     shutil.unpack_archive(): 412, 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
     *note Extraction filters: 413. for details.  In Python 3.12, use
     without the 'filter' argument will show a *note DeprecationWarning:
     18b.  In Python 3.14, the default will switch to ‘'data'’.
     (Contributed by Petr Viktorin in PEP 706(1).)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0706/


File: python.info,  Node: Python 3 9 有什麼新功能,  Next: Python 3 8 有什麼新功能,  Prev: Python 3 10 有什麼新功能,  Up: Python 有什麼新功能？

1.5 Python 3.9 有什麼新功能
===========================


編輯者: Łukasz Langa

This article explains the new features in Python 3.9, compared to 3.8.
Python 3.9 was released on October 5, 2020.  For full details, see the
*note changelog: 122.

也參考
......

PEP 596(1) - Python 3.9 Release Schedule

* Menu:

* Summary: Summary -- Release highlights. Release highlights
* You should check for DeprecationWarning in your code::
* New Features: New Features<3>.
* 其他語言更動: 其他語言更動<4>.
* 新模組: 新模組<2>.
* 改進的模組: 改進的模組<4>.
* 最佳化: 最佳化<4>.
* 已棄用: 已棄用<7>.
* 已移除: 已移除<5>.
* Porting to Python 3.9: Porting to Python 3 9.
* 建置變更: 建置變更<4>.
* C API 變更: C API 變更<4>.
* Python 3.9.1 中顯著的變更: Python 3 9 1 中顯著的變更.
* Python 3.9.2 中顯著的變更: Python 3 9 2 中顯著的變更.
* Python 3.9.3 中顯著的變更: Python 3 9 3 中顯著的變更.
* Python 3.9.5 中顯著的變更: Python 3 9 5 中顯著的變更.
* Notable security feature in 3.9.14: Notable security feature in 3 9 14.
* Notable changes in 3.9.17: Notable changes in 3 9 17.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0596/


File: python.info,  Node: Summary -- Release highlights,  Next: You should check for DeprecationWarning in your code,  Up: Python 3 9 有什麼新功能

1.5.1 Summary - Release highlights
----------------------------------

新增語法特性：

   * PEP 584(1), union operators added to ‘dict’;

   * PEP 585(2), type hinting generics in standard collections;

   * PEP 614(3), relaxed grammar restrictions on decorators.

New built-in features:

   * PEP 616(4), string methods to remove prefixes and suffixes.

New features in the standard library:

   * PEP 593(5), flexible function and variable annotations;

   * *note os.pidfd_open(): 421. added that allows process management
     without races and signals.

直譯器的改進：

   * PEP 573(6), fast access to module state from methods of C extension
     types;

   * PEP 617(7), CPython now uses a new parser based on PEG;

   * a number of Python builtins (range, tuple, set, frozenset, list,
     dict) are now sped up using PEP 590(8) vectorcall;

   * garbage collection does not block on resurrected objects;

   * a number of Python modules (‘_abc’, ‘audioop’, ‘_bz2’, ‘_codecs’,
     ‘_contextvars’, ‘_crypt’, ‘_functools’, ‘_json’, ‘_locale’, *note
     math: 81, *note operator: 8f, *note resource: aa, *note time: d7,
     ‘_weakref’) now use multiphase initialization as defined by PEP
     489;

   * a number of standard library modules (‘audioop’, *note ast: 7,
     *note grp: 5c, ‘_hashlib’, *note pwd: a0, ‘_posixsubprocess’, *note
     random: a6, *note select: af, *note struct: c0, *note termios: ca,
     *note zlib: 119.) are now using the stable ABI defined by PEP 384.

New library modules:

   * PEP 615(9), the IANA Time Zone Database is now present in the
     standard library in the *note zoneinfo: 11a. module;

   * an implementation of a topological sort of a graph is now provided
     in the new *note graphlib: 5b. module.

Release process changes:

   * PEP 602(10), CPython adopts an annual release cycle.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0584/

   (2) https://peps.python.org/pep-0585/

   (3) https://peps.python.org/pep-0614/

   (4) https://peps.python.org/pep-0616/

   (5) https://peps.python.org/pep-0593/

   (6) https://peps.python.org/pep-0573/

   (7) https://peps.python.org/pep-0617/

   (8) https://peps.python.org/pep-0590/

   (9) https://peps.python.org/pep-0615/

   (10) https://peps.python.org/pep-0602/


File: python.info,  Node: You should check for DeprecationWarning in your code,  Next: New Features<3>,  Prev: Summary -- Release highlights,  Up: Python 3 9 有什麼新功能

1.5.2 You should check for DeprecationWarning in your code
----------------------------------------------------------

When Python 2.7 was still supported, a lot of functionality in Python 3
was kept for backward compatibility with Python 2.7.  With the end of
Python 2 support, these backward compatibility layers have been removed,
or will be removed soon.  Most of them emitted a *note
DeprecationWarning: 18b. warning for several years.  For example, using
‘collections.Mapping’ instead of ‘collections.abc.Mapping’ emits a *note
DeprecationWarning: 18b. since Python 3.3, released in 2012.

Test your application with the *note -W: 86c. ‘default’ command-line
option to see *note DeprecationWarning: 18b. and *note
PendingDeprecationWarning: 86d, or even with *note -W: 86c. ‘error’ to
treat them as errors.  *note Warnings Filter: 86e. can be used to ignore
warnings from third-party code.

Python 3.9 is the last version providing those Python 2 backward
compatibility layers, to give more time to Python projects maintainers
to organize the removal of the Python 2 support and add support for
Python 3.9.

Aliases to *note Abstract Base Classes: 81b. in the *note collections:
16. module, like ‘collections.Mapping’ alias to *note
collections.abc.Mapping: 86f, are kept for one last release for backward
compatibility.  They will be removed from Python 3.10.

More generally, try to run your tests in the *note Python Development
Mode: 1dd. which helps to prepare your code to make it compatible with
the next Python version.

Note: a number of pre-existing deprecations were removed in this version
of Python as well.  Consult the *note 已移除: 870. section.


File: python.info,  Node: New Features<3>,  Next: 其他語言更動<4>,  Prev: You should check for DeprecationWarning in your code,  Up: Python 3 9 有什麼新功能

1.5.3 New Features
------------------

* Menu:

* Dictionary Merge & Update Operators::
* New String Methods to Remove Prefixes and Suffixes::
* Type Hinting Generics in Standard Collections::
* New Parser::


File: python.info,  Node: Dictionary Merge & Update Operators,  Next: New String Methods to Remove Prefixes and Suffixes,  Up: New Features<3>

1.5.3.1 Dictionary Merge & Update Operators
...........................................

Merge (‘|’) and update (‘|=’) operators have been added to the built-in
*note dict: 23b. class.  Those complement the existing ‘dict.update’ and
‘{**d1, **d2}’ methods of merging dictionaries.

範例：

     >>> x = {"key1": "value1 from x", "key2": "value2 from x"}
     >>> y = {"key2": "value2 from y", "key3": "value3 from y"}
     >>> x | y
     {'key1': 'value1 from x', 'key2': 'value2 from y', 'key3': 'value3 from y'}
     >>> y | x
     {'key2': 'value2 from x', 'key3': 'value3 from y', 'key1': 'value1 from x'}

See PEP 584(1) for a full description.  (Contributed by Brandt Bucher in
bpo-36144(2).)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0584/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36144


File: python.info,  Node: New String Methods to Remove Prefixes and Suffixes,  Next: Type Hinting Generics in Standard Collections,  Prev: Dictionary Merge & Update Operators,  Up: New Features<3>

1.5.3.2 New String Methods to Remove Prefixes and Suffixes
..........................................................

*note str.removeprefix(prefix): 874. and *note str.removesuffix(suffix):
875. have been added to easily remove an unneeded prefix or a suffix
from a string.  Corresponding ‘bytes’, ‘bytearray’, and
‘collections.UserString’ methods have also been added.  See PEP 616(1)
for a full description.  (Contributed by Dennis Sweeney in
bpo-39939(2).)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0616/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39939


File: python.info,  Node: Type Hinting Generics in Standard Collections,  Next: New Parser,  Prev: New String Methods to Remove Prefixes and Suffixes,  Up: New Features<3>

1.5.3.3 Type Hinting Generics in Standard Collections
.....................................................

In type annotations you can now use built-in collection types such as
‘list’ and ‘dict’ as generic types instead of importing the
corresponding capitalized types (e.g.  ‘List’ or ‘Dict’) from ‘typing’.
Some other types in the standard library are also now generic, for
example ‘queue.Queue’.

範例：

     def greet_all(names: list[str]) -> None:
         for name in names:
             print("Hello", name)

See PEP 585(1) for more details.  (Contributed by Guido van Rossum,
Ethan Smith, and Batuhan Taşkaya in bpo-39481(2).)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0585/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39481


File: python.info,  Node: New Parser,  Prev: Type Hinting Generics in Standard Collections,  Up: New Features<3>

1.5.3.4 New Parser
..................

Python 3.9 uses a new parser, based on PEG(1) instead of LL(1)(2).  The
new parser's performance is roughly comparable to that of the old
parser, but the PEG formalism is more flexible than LL(1) when it comes
to designing new language features.  We'll start using this flexibility
in Python 3.10 and later.

The *note ast: 7. module uses the new parser and produces the same AST
as the old parser.

In Python 3.10, the old parser will be deleted and so will all
functionality that depends on it (primarily the ‘parser’ module, which
has long been deprecated).  In Python 3.9 'only', you can switch back to
the LL(1) parser using a command line switch (‘-X oldparser’) or an
environment variable (‘PYTHONOLDPARSER=1’).

See PEP 617(3) for more details.  (Contributed by Guido van Rossum,
Pablo Galindo and Lysandros Nikolaou in bpo-40334(4).)

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Parsing_expression_grammar

   (2) https://en.wikipedia.org/wiki/LL_parser

   (3) https://peps.python.org/pep-0617/

   (4) https://bugs.python.org/issue?@action=redirect&bpo=40334


File: python.info,  Node: 其他語言更動<4>,  Next: 新模組<2>,  Prev: New Features<3>,  Up: Python 3 9 有什麼新功能

1.5.4 其他語言更動
------------------

   * *note __import__(): 879. now raises *note ImportError: 352. instead
     of *note ValueError: 1e7, which used to occur when a relative
     import went past its top-level package.  (Contributed by Ngalim
     Siregar in bpo-37444(1).)

   * Python now gets the absolute path of the script filename specified
     on the command line (ex: ‘python3 script.py’): the ‘__file__’
     attribute of the *note __main__: 1. module became an absolute path,
     rather than a relative path.  These paths now remain valid after
     the current directory is changed by *note os.chdir(): 5b2.  As a
     side effect, the traceback also displays the absolute path for
     *note __main__: 1. module frames in this case.  (Contributed by
     Victor Stinner in bpo-20443(2).)

   * In the *note Python Development Mode: 1dd. and in *note debug
     build: 1de, the 'encoding' and 'errors' arguments are now checked
     for string encoding and decoding operations.  Examples: *note
     open(): 4c0, *note str.encode(): 87a. and *note bytes.decode():
     87b.

     By default, for best performance, the 'errors' argument is only
     checked at the first encoding/decoding error and the 'encoding'
     argument is sometimes ignored for empty strings.  (Contributed by
     Victor Stinner in bpo-37388(3).)

   * ‘"".replace("", s, n)’ now returns ‘s’ instead of an empty string
     for all non-zero ‘n’.  It is now consistent with ‘"".replace("",
     s)’.  There are similar changes for *note bytes: 1a5. and *note
     bytearray: 4e3. objects.  (Contributed by Serhiy Storchaka in
     bpo-28029(4).)

   * Any valid expression can now be used as a *note decorator: 6d5.
     Previously, the grammar was much more restrictive.  See PEP 614(5)
     for details.  (Contributed by Brandt Bucher in bpo-39702(6).)

   * Improved help for the *note typing: ed. module.  Docstrings are now
     shown for all special forms and special generic aliases (like
     ‘Union’ and ‘List’).  Using *note help(): 87c. with generic alias
     like ‘List[int]’ will show the help for the correspondent concrete
     type (‘list’ in this case).  (Contributed by Serhiy Storchaka in
     bpo-40257(7).)

   * Parallel running of *note aclose(): 87d. / *note asend(): 87e. /
     *note athrow(): 4a1. is now prohibited, and ‘ag_running’ now
     reflects the actual running status of the async generator.
     (Contributed by Yury Selivanov in bpo-30773(8).)

   * Unexpected errors in calling the ‘__iter__’ method are no longer
     masked by ‘TypeError’ in the *note in: 2c5. operator and functions
     *note contains(): 87f, *note indexOf(): 880. and *note countOf():
     881. of the *note operator: 8f. module.  (Contributed by Serhiy
     Storchaka in bpo-40824(9).)

   * Unparenthesized lambda expressions can no longer be the expression
     part in an ‘if’ clause in comprehensions and generator expressions.
     See bpo-41848(10) and bpo-43755(11) for details.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=37444

   (2) https://bugs.python.org/issue?@action=redirect&bpo=20443

   (3) https://bugs.python.org/issue?@action=redirect&bpo=37388

   (4) https://bugs.python.org/issue?@action=redirect&bpo=28029

   (5) https://peps.python.org/pep-0614/

   (6) https://bugs.python.org/issue?@action=redirect&bpo=39702

   (7) https://bugs.python.org/issue?@action=redirect&bpo=40257

   (8) https://bugs.python.org/issue?@action=redirect&bpo=30773

   (9) https://bugs.python.org/issue?@action=redirect&bpo=40824

   (10) https://bugs.python.org/issue?@action=redirect&bpo=41848

   (11) https://bugs.python.org/issue?@action=redirect&bpo=43755


File: python.info,  Node: 新模組<2>,  Next: 改進的模組<4>,  Prev: 其他語言更動<4>,  Up: Python 3 9 有什麼新功能

1.5.5 新模組
------------

* Menu:

* zoneinfo::
* graphlib::


File: python.info,  Node: zoneinfo,  Next: graphlib,  Up: 新模組<2>

1.5.5.1 zoneinfo
................

The *note zoneinfo: 11a. module brings support for the IANA time zone
database to the standard library.  It adds *note zoneinfo.ZoneInfo: 884,
a concrete *note datetime.tzinfo: 582. implementation backed by the
system's time zone data.

範例：

     >>> from zoneinfo import ZoneInfo
     >>> from datetime import datetime, timedelta

     >>> # Daylight saving time
     >>> dt = datetime(2020, 10, 31, 12, tzinfo=ZoneInfo("America/Los_Angeles"))
     >>> print(dt)
     2020-10-31 12:00:00-07:00
     >>> dt.tzname()
     'PDT'

     >>> # Standard time
     >>> dt += timedelta(days=7)
     >>> print(dt)
     2020-11-07 12:00:00-08:00
     >>> print(dt.tzname())
     PST

As a fall-back source of data for platforms that don't ship the IANA
database, the tzdata(1) module was released as a first-party package -
distributed via PyPI and maintained by the CPython core team.

也參考
......

PEP 615(2) - Support for the IANA Time Zone Database in the Standard Library

     由 Paul Ganssle 撰寫 PEP 與實作

   ---------- Footnotes ----------

   (1) https://pypi.org/project/tzdata/

   (2) https://peps.python.org/pep-0615/


File: python.info,  Node: graphlib,  Prev: zoneinfo,  Up: 新模組<2>

1.5.5.2 graphlib
................

A new module, *note graphlib: 5b, was added that contains the *note
graphlib.TopologicalSorter: 886. class to offer functionality to perform
topological sorting of graphs.  (Contributed by Pablo Galindo, Tim
Peters and Larry Hastings in bpo-17005(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=17005


File: python.info,  Node: 改進的模組<4>,  Next: 最佳化<4>,  Prev: 新模組<2>,  Up: Python 3 9 有什麼新功能

1.5.6 改進的模組
----------------

* Menu:

* ast: ast<2>.
* asyncio: asyncio<5>.
* compileall: compileall<2>.
* concurrent.futures: concurrent futures<2>.
* curses: curses<2>.
* datetime: datetime<2>.
* distutils: distutils<3>.
* fcntl: fcntl<2>.
* ftplib: ftplib<2>.
* gc: gc<3>.
* hashlib: hashlib<4>.
* http::
* IDLE and idlelib::
* imaplib::
* importlib: importlib<3>.
* inspect: inspect<4>.
* ipaddress: ipaddress<2>.
* math: math<4>.
* multiprocessing: multiprocessing<2>.
* nntplib::
* os: os<5>.
* pathlib: pathlib<6>.
* pdb: pdb<3>.
* poplib::
* pprint: pprint<2>.
* pydoc::
* random: random<3>.
* signal::
* smtplib::
* socket: socket<3>.
* time: time<3>.
* sys: sys<5>.
* tracemalloc::
* typing: typing<6>.
* unicodedata: unicodedata<4>.
* venv: venv<3>.
* xml: xml<3>.


File: python.info,  Node: ast<2>,  Next: asyncio<5>,  Up: 改進的模組<4>

1.5.6.1 ast
...........

Added the 'indent' option to *note dump(): 889. which allows it to
produce a multiline indented output.  (Contributed by Serhiy Storchaka
in bpo-37995(1).)

Added *note ast.unparse(): 88a. as a function in the *note ast: 7.
module that can be used to unparse an *note ast.AST: 18c. object and
produce a string with code that would produce an equivalent *note
ast.AST: 18c. object when parsed.  (Contributed by Pablo Galindo and
Batuhan Taskaya in bpo-38870(2).)

Added docstrings to AST nodes that contains the ASDL signature used to
construct that node.  (Contributed by Batuhan Taskaya in bpo-39638(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=37995

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38870

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39638


File: python.info,  Node: asyncio<5>,  Next: compileall<2>,  Prev: ast<2>,  Up: 改進的模組<4>

1.5.6.2 asyncio
...............

Due to significant security concerns, the 'reuse_address' parameter of
*note asyncio.loop.create_datagram_endpoint(): 6d7. is no longer
supported.  This is because of the behavior of the socket option
‘SO_REUSEADDR’ in UDP. For more details, see the documentation for
‘loop.create_datagram_endpoint()’.  (Contributed by Kyle Stanley,
Antoine Pitrou, and Yury Selivanov in bpo-37228(1).)

Added a new *note coroutine: 438. *note shutdown_default_executor():
88c. that schedules a shutdown for the default executor that waits on
the *note ThreadPoolExecutor: 6e6. to finish closing.  Also, *note
asyncio.run(): 423. has been updated to use the new *note coroutine:
438.  (Contributed by Kyle Stanley in bpo-34037(2).)

Added *note asyncio.PidfdChildWatcher: 420, a Linux-specific child
watcher implementation that polls process file descriptors.
(bpo-38692(3))

Added a new *note coroutine: 438. *note asyncio.to_thread(): 88d.  It is
mainly used for running IO-bound functions in a separate thread to avoid
blocking the event loop, and essentially works as a high-level version
of *note run_in_executor(): 88e. that can directly take keyword
arguments.  (Contributed by Kyle Stanley and Yury Selivanov in
bpo-32309(4).)

When cancelling the task due to a timeout, *note asyncio.wait_for():
5a4. will now wait until the cancellation is complete also in the case
when 'timeout' is <= 0, like it does with positive timeouts.
(Contributed by Elvis Pranskevichus in bpo-32751(5).)

*note asyncio: 8. now raises *note TypeError: 4dd. when calling
incompatible methods with an *note ssl.SSLSocket: 88f. socket.
(Contributed by Ido Michael in bpo-37404(6).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=37228

   (2) https://bugs.python.org/issue?@action=redirect&bpo=34037

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38692

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32309

   (5) https://bugs.python.org/issue?@action=redirect&bpo=32751

   (6) https://bugs.python.org/issue?@action=redirect&bpo=37404


File: python.info,  Node: compileall<2>,  Next: concurrent futures<2>,  Prev: asyncio<5>,  Up: 改進的模組<4>

1.5.6.3 compileall
..................

Added new possibility to use hardlinks for duplicated ‘.pyc’ files:
'hardlink_dupes' parameter and -hardlink-dupes command line option.
(Contributed by Lumír 'Frenzy' Balhar in bpo-40495(1).)

Added new options for path manipulation in resulting ‘.pyc’ files:
'stripdir', 'prependdir', 'limit_sl_dest' parameters and -s, -p, -e
command line options.  Added the possibility to specify the option for
an optimization level multiple times.  (Contributed by Lumír 'Frenzy'
Balhar in bpo-38112(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40495

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38112


File: python.info,  Node: concurrent futures<2>,  Next: curses<2>,  Prev: compileall<2>,  Up: 改進的模組<4>

1.5.6.4 concurrent.futures
..........................

Added a new 'cancel_futures' parameter to *note
concurrent.futures.Executor.shutdown(): 892. that cancels all pending
futures which have not started running, instead of waiting for them to
complete before shutting down the executor.  (Contributed by Kyle
Stanley in bpo-39349(1).)

Removed daemon threads from *note ThreadPoolExecutor: 6e6. and *note
ProcessPoolExecutor: 893.  This improves compatibility with
subinterpreters and predictability in their shutdown processes.
(Contributed by Kyle Stanley in bpo-39812(2).)

Workers in *note ProcessPoolExecutor: 893. are now spawned on demand,
only when there are no available idle workers to reuse.  This optimizes
startup overhead and reduces the amount of lost CPU time to idle
workers.  (Contributed by Kyle Stanley in bpo-39207(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39349

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39812

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39207


File: python.info,  Node: curses<2>,  Next: datetime<2>,  Prev: concurrent futures<2>,  Up: 改進的模組<4>

1.5.6.5 curses
..............

Added *note curses.get_escdelay(): 895, *note curses.set_escdelay():
896, *note curses.get_tabsize(): 897, and *note curses.set_tabsize():
898. functions.  (Contributed by Anthony Sottile in bpo-38312(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38312


File: python.info,  Node: datetime<2>,  Next: distutils<3>,  Prev: curses<2>,  Up: 改進的模組<4>

1.5.6.6 datetime
................

The *note isocalendar(): 89a. of *note datetime.date: 1b1. and *note
isocalendar(): 89b. of *note datetime.datetime: 1b0. methods now returns
a *note namedtuple(): 1ae. instead of a *note tuple: 322.  (Contributed
by Donghee Na in bpo-24416(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24416


File: python.info,  Node: distutils<3>,  Next: fcntl<2>,  Prev: datetime<2>,  Up: 改進的模組<4>

1.5.6.7 distutils
.................

The ‘upload’ command now creates SHA2-256 and Blake2b-256 hash digests.
It skips MD5 on platforms that block MD5 digest.  (Contributed by
Christian Heimes in bpo-40698(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40698


File: python.info,  Node: fcntl<2>,  Next: ftplib<2>,  Prev: distutils<3>,  Up: 改進的模組<4>

1.5.6.8 fcntl
.............

Added constants ‘F_OFD_GETLK’, ‘F_OFD_SETLK’ and ‘F_OFD_SETLKW’.
(Contributed by Donghee Na in bpo-38602(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38602


File: python.info,  Node: ftplib<2>,  Next: gc<3>,  Prev: fcntl<2>,  Up: 改進的模組<4>

1.5.6.9 ftplib
..............

*note FTP: 89f. and *note FTP_TLS: 8a0. now raise a *note ValueError:
1e7. if the given timeout for their constructor is zero to prevent the
creation of a non-blocking socket.  (Contributed by Donghee Na in
bpo-39259(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39259


File: python.info,  Node: gc<3>,  Next: hashlib<4>,  Prev: ftplib<2>,  Up: 改進的模組<4>

1.5.6.10 gc
...........

When the garbage collector makes a collection in which some objects
resurrect (they are reachable from outside the isolated cycles after the
finalizers have been executed), do not block the collection of all
objects that are still unreachable.  (Contributed by Pablo Galindo and
Tim Peters in bpo-38379(1).)

Added a new function *note gc.is_finalized(): 8a2. to check if an object
has been finalized by the garbage collector.  (Contributed by Pablo
Galindo in bpo-39322(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38379

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39322


File: python.info,  Node: hashlib<4>,  Next: http,  Prev: gc<3>,  Up: 改進的模組<4>

1.5.6.11 hashlib
................

The *note hashlib: 5e. module can now use SHA3 hashes and SHAKE XOF from
OpenSSL when available.  (Contributed by Christian Heimes in
bpo-37630(1).)

Builtin hash modules can now be disabled with ‘./configure
--without-builtin-hashlib-hashes’ or selectively enabled with e.g.
‘./configure --with-builtin-hashlib-hashes=sha3,blake2’ to force use of
OpenSSL based implementation.  (Contributed by Christian Heimes in
bpo-40479(2))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=37630

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40479


File: python.info,  Node: http,  Next: IDLE and idlelib,  Prev: hashlib<4>,  Up: 改進的模組<4>

1.5.6.12 http
.............

HTTP status codes ‘103 EARLY_HINTS’, ‘418 IM_A_TEAPOT’ and ‘425
TOO_EARLY’ are added to *note http.HTTPStatus: 8a5.  (Contributed by
Donghee Na in bpo-39509(1) and Ross Rhodes in bpo-39507(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39509

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39507


File: python.info,  Node: IDLE and idlelib,  Next: imaplib,  Prev: http,  Up: 改進的模組<4>

1.5.6.13 IDLE and idlelib
.........................

Added option to toggle cursor blink off.  (Contributed by Zackery Spytz
in bpo-4603(1).)

Escape key now closes IDLE completion windows.  (Contributed by Johnny
Najera in bpo-38944(2).)

Added keywords to module name completion list.  (Contributed by Terry J.
Reedy in bpo-37765(3).)

New in 3.9 maintenance releases

Make IDLE invoke *note sys.excepthook(): 7af. (when started without
'-n').  User hooks were previously ignored.  (Contributed by Ken Hilton
in bpo-43008(4).)

The changes above have been backported to 3.8 maintenance releases.

Rearrange the settings dialog.  Split the General tab into Windows and
Shell/Ed tabs.  Move help sources, which extend the Help menu, to the
Extensions tab.  Make space for new options and shorten the dialog.  The
latter makes the dialog better fit small screens.  (Contributed by Terry
Jan Reedy in bpo-40468(5).)  Move the indent space setting from the Font
tab to the new Windows tab.  (Contributed by Mark Roseman and Terry Jan
Reedy in bpo-33962(6).)

Apply syntax highlighting to ‘.pyi’ files.  (Contributed by Alex Waygood
and Terry Jan Reedy in bpo-45447(7).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=4603

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38944

   (3) https://bugs.python.org/issue?@action=redirect&bpo=37765

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43008

   (5) https://bugs.python.org/issue?@action=redirect&bpo=40468

   (6) https://bugs.python.org/issue?@action=redirect&bpo=33962

   (7) https://bugs.python.org/issue?@action=redirect&bpo=45447


File: python.info,  Node: imaplib,  Next: importlib<3>,  Prev: IDLE and idlelib,  Up: 改進的模組<4>

1.5.6.14 imaplib
................

*note IMAP4: 8a8. and *note IMAP4_SSL: 8a9. now have an optional
'timeout' parameter for their constructors.  Also, the *note open():
8aa. method now has an optional 'timeout' parameter with this change.
The overridden methods of *note IMAP4_SSL: 8a9. and *note IMAP4_stream:
8ab. were applied to this change.  (Contributed by Donghee Na in
bpo-38615(1).)

*note imaplib.IMAP4.unselect(): 8ac. is added.  *note
imaplib.IMAP4.unselect(): 8ac. frees server's resources associated with
the selected mailbox and returns the server to the authenticated state.
This command performs the same actions as *note imaplib.IMAP4.close():
8ad, except that no messages are permanently removed from the currently
selected mailbox.  (Contributed by Donghee Na in bpo-40375(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38615

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40375


File: python.info,  Node: importlib<3>,  Next: inspect<4>,  Prev: imaplib,  Up: 改進的模組<4>

1.5.6.15 importlib
..................

To improve consistency with import statements, *note
importlib.util.resolve_name(): 8af. now raises *note ImportError: 352.
instead of *note ValueError: 1e7. for invalid relative import attempts.
(Contributed by Ngalim Siregar in bpo-37444(1).)

Import loaders which publish immutable module objects can now publish
immutable packages in addition to individual modules.  (Contributed by
Dino Viehland in bpo-39336(2).)

Added *note importlib.resources.files(): 435. function with support for
subdirectories in package data, matching backport in
‘importlib_resources’ version 1.5.  (Contributed by Jason R. Coombs in
bpo-39791(3).)

Refreshed ‘importlib.metadata’ from ‘importlib_metadata’ version 1.6.1.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=37444

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39336

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39791


File: python.info,  Node: inspect<4>,  Next: ipaddress<2>,  Prev: importlib<3>,  Up: 改進的模組<4>

1.5.6.16 inspect
................

*note inspect.BoundArguments.arguments: 8b1. is changed from
‘OrderedDict’ to regular dict.  (Contributed by Inada Naoki in
bpo-36350(1) and bpo-39775(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36350

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39775


File: python.info,  Node: ipaddress<2>,  Next: math<4>,  Prev: inspect<4>,  Up: 改進的模組<4>

1.5.6.17 ipaddress
..................

*note ipaddress: 74. now supports IPv6 Scoped Addresses (IPv6 address
with suffix ‘%<scope_id>’).

Scoped IPv6 addresses can be parsed using *note ipaddress.IPv6Address:
1e2.  If present, scope zone ID is available through the *note scope_id:
8b3. attribute.  (Contributed by Oleksandr Pavliuk in bpo-34788(1).)

Starting with Python 3.9.5 the *note ipaddress: 74. module no longer
accepts any leading zeros in IPv4 address strings.  (Contributed by
Christian Heimes in bpo-36384(2)).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=34788

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36384


File: python.info,  Node: math<4>,  Next: multiprocessing<2>,  Prev: ipaddress<2>,  Up: 改進的模組<4>

1.5.6.18 math
.............

Expanded the *note math.gcd(): 8b5. function to handle multiple
arguments.  Formerly, it only supported two arguments.  (Contributed by
Serhiy Storchaka in bpo-39648(1).)

Added *note math.lcm(): 8b6.: return the least common multiple of
specified arguments.  (Contributed by Mark Dickinson, Ananthakrishnan
and Serhiy Storchaka in bpo-39479(2) and bpo-39648(3).)

Added *note math.nextafter(): 440.: return the next floating-point value
after 'x' towards 'y'.  (Contributed by Victor Stinner in bpo-39288(4).)

Added *note math.ulp(): 8b7.: return the value of the least significant
bit of a float.  (Contributed by Victor Stinner in bpo-39310(5).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39648

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39479

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39648

   (4) https://bugs.python.org/issue?@action=redirect&bpo=39288

   (5) https://bugs.python.org/issue?@action=redirect&bpo=39310


File: python.info,  Node: multiprocessing<2>,  Next: nntplib,  Prev: math<4>,  Up: 改進的模組<4>

1.5.6.19 multiprocessing
........................

The *note multiprocessing.SimpleQueue: 8b9. class has a new *note
close(): 8ba. method to explicitly close the queue.  (Contributed by
Victor Stinner in bpo-30966(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30966


File: python.info,  Node: nntplib,  Next: os<5>,  Prev: multiprocessing<2>,  Up: 改進的模組<4>

1.5.6.20 nntplib
................

‘NNTP’ and ‘NNTP_SSL’ now raise a *note ValueError: 1e7. if the given
timeout for their constructor is zero to prevent the creation of a
non-blocking socket.  (Contributed by Donghee Na in bpo-39259(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39259


File: python.info,  Node: os<5>,  Next: pathlib<6>,  Prev: nntplib,  Up: 改進的模組<4>

1.5.6.21 os
...........

Added *note CLD_KILLED: 8bd. and *note CLD_STOPPED: 8be. for ‘si_code’.
(Contributed by Donghee Na in bpo-38493(1).)

Exposed the Linux-specific *note os.pidfd_open(): 421. (bpo-38692(2))
and *note os.P_PIDFD: 8bf. (bpo-38713(3)) for process management with
file descriptors.

The *note os.unsetenv(): 8c0. function is now also available on Windows.
(Contributed by Victor Stinner in bpo-39413(4).)

The *note os.putenv(): 8c1. and *note os.unsetenv(): 8c0. functions are
now always available.  (Contributed by Victor Stinner in bpo-39395(5).)

Added *note os.waitstatus_to_exitcode(): 8c2. function: convert a wait
status to an exit code.  (Contributed by Victor Stinner in
bpo-40094(6).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38493

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38692

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38713

   (4) https://bugs.python.org/issue?@action=redirect&bpo=39413

   (5) https://bugs.python.org/issue?@action=redirect&bpo=39395

   (6) https://bugs.python.org/issue?@action=redirect&bpo=40094


File: python.info,  Node: pathlib<6>,  Next: pdb<3>,  Prev: os<5>,  Up: 改進的模組<4>

1.5.6.22 pathlib
................

Added *note pathlib.Path.readlink(): 8c4. which acts similarly to *note
os.readlink(): 8c5.  (Contributed by Girts Folkmanis in bpo-30618(1))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30618


File: python.info,  Node: pdb<3>,  Next: poplib,  Prev: pathlib<6>,  Up: 改進的模組<4>

1.5.6.23 pdb
............

On Windows now *note Pdb: 8c7. supports ‘~/.pdbrc’.  (Contributed by Tim
Hopper and Dan Lidral-Porter in bpo-20523(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=20523


File: python.info,  Node: poplib,  Next: pprint<2>,  Prev: pdb<3>,  Up: 改進的模組<4>

1.5.6.24 poplib
...............

*note POP3: 8c9. and *note POP3_SSL: 8ca. now raise a *note ValueError:
1e7. if the given timeout for their constructor is zero to prevent the
creation of a non-blocking socket.  (Contributed by Donghee Na in
bpo-39259(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39259


File: python.info,  Node: pprint<2>,  Next: pydoc,  Prev: poplib,  Up: 改進的模組<4>

1.5.6.25 pprint
...............

*note pprint: 9c. can now pretty-print *note types.SimpleNamespace: 1b5.
(Contributed by Carl Bordum Hansen in bpo-37376(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=37376


File: python.info,  Node: pydoc,  Next: random<3>,  Prev: pprint<2>,  Up: 改進的模組<4>

1.5.6.26 pydoc
..............

The documentation string is now shown not only for class, function,
method etc, but for any object that has its own ‘__doc__’ attribute.
(Contributed by Serhiy Storchaka in bpo-40257(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40257


File: python.info,  Node: random<3>,  Next: signal,  Prev: pydoc,  Up: 改進的模組<4>

1.5.6.27 random
...............

Added a new ‘random.Random.randbytes’ method: generate random bytes.
(Contributed by Victor Stinner in bpo-40286(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40286


File: python.info,  Node: signal,  Next: smtplib,  Prev: random<3>,  Up: 改進的模組<4>

1.5.6.28 signal
...............

Exposed the Linux-specific *note signal.pidfd_send_signal(): 8cf. for
sending to signals to a process using a file descriptor instead of a
pid.  (bpo-38712(1))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38712


File: python.info,  Node: smtplib,  Next: socket<3>,  Prev: signal,  Up: 改進的模組<4>

1.5.6.29 smtplib
................

*note SMTP: 8d1. and *note SMTP_SSL: 8d2. now raise a *note ValueError:
1e7. if the given timeout for their constructor is zero to prevent the
creation of a non-blocking socket.  (Contributed by Donghee Na in
bpo-39259(1).)

*note LMTP: 8d3. constructor now has an optional 'timeout' parameter.
(Contributed by Donghee Na in bpo-39329(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39259

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39329


File: python.info,  Node: socket<3>,  Next: time<3>,  Prev: smtplib,  Up: 改進的模組<4>

1.5.6.30 socket
...............

The *note socket: b8. module now exports the *note CAN_RAW_JOIN_FILTERS:
8d5. constant on Linux 4.1 and greater.  (Contributed by Stefan
Tatschner and Zackery Spytz in bpo-25780(1).)

The socket module now supports the *note CAN_J1939: 8d6. protocol on
platforms that support it.  (Contributed by Karl Ding in bpo-40291(2).)

The socket module now has the *note socket.send_fds(): 8d7. and *note
socket.recv_fds(): 8d8. functions.  (Contributed by Joannah Nanjekye,
Shinya Okano and Victor Stinner in bpo-28724(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25780

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40291

   (3) https://bugs.python.org/issue?@action=redirect&bpo=28724


File: python.info,  Node: time<3>,  Next: sys<5>,  Prev: socket<3>,  Up: 改進的模組<4>

1.5.6.31 time
.............

On AIX, *note thread_time(): 8da. is now implemented with
‘thread_cputime()’ which has nanosecond resolution, rather than
‘clock_gettime(CLOCK_THREAD_CPUTIME_ID)’ which has a resolution of 10
milliseconds.  (Contributed by Batuhan Taskaya in bpo-40192(1))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40192


File: python.info,  Node: sys<5>,  Next: tracemalloc,  Prev: time<3>,  Up: 改進的模組<4>

1.5.6.32 sys
............

Added a new *note sys.platlibdir: 8dc. attribute: name of the
platform-specific library directory.  It is used to build the path of
standard library and the paths of installed extension modules.  It is
equal to ‘"lib"’ on most platforms.  On Fedora and SuSE, it is equal to
‘"lib64"’ on 64-bit platforms.  (Contributed by Jan Matějek, Matěj Cepl,
Charalampos Stratakis and Victor Stinner in bpo-1294959(1).)

Previously, *note sys.stderr: 8dd. was block-buffered when
non-interactive.  Now ‘stderr’ defaults to always being line-buffered.
(Contributed by Jendrik Seipp in bpo-13601(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1294959

   (2) https://bugs.python.org/issue?@action=redirect&bpo=13601


File: python.info,  Node: tracemalloc,  Next: typing<6>,  Prev: sys<5>,  Up: 改進的模組<4>

1.5.6.33 tracemalloc
....................

Added *note tracemalloc.reset_peak(): 8df. to set the peak size of
traced memory blocks to the current size, to measure the peak of
specific pieces of code.  (Contributed by Huon Wilson in bpo-40630(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40630


File: python.info,  Node: typing<6>,  Next: unicodedata<4>,  Prev: tracemalloc,  Up: 改進的模組<4>

1.5.6.34 typing
...............

PEP 593(1) introduced an *note typing.Annotated: 8e1. type to decorate
existing types with context-specific metadata and new ‘include_extras’
parameter to *note typing.get_type_hints(): 657. to access the metadata
at runtime.  (Contributed by Till Varoquaux and Konstantin Kashin.)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0593/


File: python.info,  Node: unicodedata<4>,  Next: venv<3>,  Prev: typing<6>,  Up: 改進的模組<4>

1.5.6.35 unicodedata
....................

The Unicode database has been updated to version 13.0.0.
(bpo-39926(1)).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39926


File: python.info,  Node: venv<3>,  Next: xml<3>,  Prev: unicodedata<4>,  Up: 改進的模組<4>

1.5.6.36 venv
.............

The activation scripts provided by *note venv: f9. now all specify their
prompt customization consistently by always using the value specified by
‘__VENV_PROMPT__’.  Previously some scripts unconditionally used
‘__VENV_PROMPT__’, others only if it happened to be set (which was the
default case), and one used ‘__VENV_NAME__’ instead.  (Contributed by
Brett Cannon in bpo-37663(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=37663


File: python.info,  Node: xml<3>,  Prev: venv<3>,  Up: 改進的模組<4>

1.5.6.37 xml
............

White space characters within attributes are now preserved when
serializing *note xml.etree.ElementTree: 10c. to XML file.  EOLNs are no
longer normalized to "n".  This is the result of discussion about how to
interpret section 2.11 of XML spec.  (Contributed by Mefistotelis in
bpo-39011(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39011


File: python.info,  Node: 最佳化<4>,  Next: 已棄用<7>,  Prev: 改進的模組<4>,  Up: Python 3 9 有什麼新功能

1.5.7 最佳化
------------

   * Optimized the idiom for assignment a temporary variable in
     comprehensions.  Now ‘for y in [expr]’ in comprehensions is as fast
     as a simple assignment ‘y = expr’.  For example:

          sums = [s for s in [0] for x in data for s in [s + x]]

     Unlike the ‘:=’ operator this idiom does not leak a variable to the
     outer scope.

     （由 Serhiy Storchaka 在 bpo-32856(1) 中貢獻。）

   * Optimized signal handling in multithreaded applications.  If a
     thread different than the main thread gets a signal, the bytecode
     evaluation loop is no longer interrupted at each bytecode
     instruction to check for pending signals which cannot be handled.
     Only the main thread of the main interpreter can handle signals.

     Previously, the bytecode evaluation loop was interrupted at each
     instruction until the main thread handles signals.  (Contributed by
     Victor Stinner in bpo-40010(2).)

   * Optimized the *note subprocess: c1. module on FreeBSD using
     ‘closefrom()’.  (Contributed by Ed Maste, Conrad Meyer, Kyle Evans,
     Kubilay Kocak and Victor Stinner in bpo-38061(3).)

   * *note PyLong_FromDouble(): 8e6. is now up to 1.87x faster for
     values that fit into long.  (Contributed by Sergey Fedoseev in
     bpo-37986(4).)

   * A number of Python builtins (*note range: 8e7, *note tuple: 322,
     *note set: 57d, *note frozenset: 57e, *note list: 5b6, *note dict:
     23b.) are now sped up by using PEP 590(5) vectorcall protocol.
     (Contributed by Donghee Na, Mark Shannon, Jeroen Demeyer and Petr
     Viktorin in bpo-37207(6).)

   * Optimized ‘difference_update()’ for the case when the other set is
     much larger than the base set.  (Suggested by Evgeny Kapun with
     code contributed by Michele Orrù in bpo-8425(7).)

   * Python's small object allocator (‘obmalloc.c’) now allows (no more
     than) one empty arena to remain available for immediate reuse,
     without returning it to the OS. This prevents thrashing in simple
     loops where an arena could be created and destroyed anew on each
     iteration.  (Contributed by Tim Peters in bpo-37257(8).)

   * *note floor division: 8e8. of float operation now has a better
     performance.  Also the message of *note ZeroDivisionError: 8e9. for
     this operation is updated.  (Contributed by Donghee Na in
     bpo-39434(9).)

   * Decoding short ASCII strings with UTF-8 and ascii codecs is now
     about 15% faster.  (Contributed by Inada Naoki in bpo-37348(10).)

Here's a summary of performance improvements from Python 3.4 through
Python 3.9:

     Python version                       3.4     3.5     3.6     3.7     3.8    3.9
     --------------                       ---     ---     ---     ---     ---    ---

     Variable and attribute read access:
         read_local                       7.1     7.1     5.4     5.1     3.9    3.9
         read_nonlocal                    7.1     8.1     5.8     5.4     4.4    4.5
         read_global                     15.5    19.0    14.3    13.6     7.6    7.8
         read_builtin                    21.1    21.6    18.5    19.0     7.5    7.8
         read_classvar_from_class        25.6    26.5    20.7    19.5    18.4   17.9
         read_classvar_from_instance     22.8    23.5    18.8    17.1    16.4   16.9
         read_instancevar                32.4    33.1    28.0    26.3    25.4   25.3
         read_instancevar_slots          27.8    31.3    20.8    20.8    20.2   20.5
         read_namedtuple                 73.8    57.5    45.0    46.8    18.4   18.7
         read_boundmethod                37.6    37.9    29.6    26.9    27.7   41.1

     Variable and attribute write access:
         write_local                      8.7     9.3     5.5     5.3     4.3    4.3
         write_nonlocal                  10.5    11.1     5.6     5.5     4.7    4.8
         write_global                    19.7    21.2    18.0    18.0    15.8   16.7
         write_classvar                  92.9    96.0   104.6   102.1    39.2   39.8
         write_instancevar               44.6    45.8    40.0    38.9    35.5   37.4
         write_instancevar_slots         35.6    36.1    27.3    26.6    25.7   25.8

     Data structure read access:
         read_list                       24.2    24.5    20.8    20.8    19.0   19.5
         read_deque                      24.7    25.5    20.2    20.6    19.8   20.2
         read_dict                       24.3    25.7    22.3    23.0    21.0   22.4
         read_strdict                    22.6    24.3    19.5    21.2    18.9   21.5

     Data structure write access:
         write_list                      27.1    28.5    22.5    21.6    20.0   20.0
         write_deque                     28.7    30.1    22.7    21.8    23.5   21.7
         write_dict                      31.4    33.3    29.3    29.2    24.7   25.4
         write_strdict                   28.4    29.9    27.5    25.2    23.1   24.5

     Stack (or queue) operations:
         list_append_pop                 93.4   112.7    75.4    74.2    50.8   50.6
         deque_append_pop                43.5    57.0    49.4    49.2    42.5   44.2
         deque_append_popleft            43.7    57.3    49.7    49.7    42.8   46.4

     Timing loop:
         loop_overhead                    0.5     0.6     0.4     0.3     0.3    0.3

These results were generated from the variable access benchmark script
at: ‘Tools/scripts/var_access_benchmark.py’.  The benchmark script
displays timings in nanoseconds.  The benchmarks were measured on an
Intel® Core™ i7-4960HQ processor(11) running the macOS 64-bit builds
found at python.org(12).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32856

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40010

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38061

   (4) https://bugs.python.org/issue?@action=redirect&bpo=37986

   (5) https://peps.python.org/pep-0590/

   (6) https://bugs.python.org/issue?@action=redirect&bpo=37207

   (7) https://bugs.python.org/issue?@action=redirect&bpo=8425

   (8) https://bugs.python.org/issue?@action=redirect&bpo=37257

   (9) https://bugs.python.org/issue?@action=redirect&bpo=39434

   (10) https://bugs.python.org/issue?@action=redirect&bpo=37348

   (11) 
https://ark.intel.com/content/www/us/en/ark/products/76088/intel-core-i7-4960hq-processor-6m-cache-up-to-3-80-ghz.html

   (12) https://www.python.org/downloads/macos/


File: python.info,  Node: 已棄用<7>,  Next: 已移除<5>,  Prev: 最佳化<4>,  Up: Python 3 9 有什麼新功能

1.5.8 已棄用
------------

   * The distutils ‘bdist_msi’ command is now deprecated, use
     ‘bdist_wheel’ (wheel packages) instead.  (Contributed by Hugo van
     Kemenade in bpo-39586(1).)

   * Currently *note math.factorial(): 8eb. accepts *note float: 2c8.
     instances with non-negative integer values (like ‘5.0’).  It raises
     a *note ValueError: 1e7. for non-integral and negative floats.  It
     is now deprecated.  In future Python versions it will raise a *note
     TypeError: 4dd. for all floats.  (Contributed by Serhiy Storchaka
     in bpo-37315(2).)

   * The ‘parser’ and ‘symbol’ modules are deprecated and will be
     removed in future versions of Python.  For the majority of use
     cases, users can leverage the Abstract Syntax Tree (AST) generation
     and compilation stage, using the *note ast: 7. module.

   * The Public C API functions ‘PyParser_SimpleParseStringFlags()’,
     ‘PyParser_SimpleParseStringFlagsFilename()’,
     ‘PyParser_SimpleParseFileFlags()’ and ‘PyNode_Compile()’ are
     deprecated and will be removed in Python 3.10 together with the old
     parser.

   * Using *note NotImplemented: 776. in a boolean context has been
     deprecated, as it is almost exclusively the result of incorrect
     rich comparator implementations.  It will be made a *note
     TypeError: 4dd. in a future version of Python.  (Contributed by
     Josh Rosenberg in bpo-35712(3).)

   * The *note random: a6. module currently accepts any hashable type as
     a possible seed value.  Unfortunately, some of those types are not
     guaranteed to have a deterministic hash value.  After Python 3.9,
     the module will restrict its seeds to *note None: 61b, *note int:
     23c, *note float: 2c8, *note str: 3f2, *note bytes: 1a5, and *note
     bytearray: 4e3.

   * Opening the *note GzipFile: 354. file for writing without
     specifying the 'mode' argument is deprecated.  In future Python
     versions it will always be opened for reading by default.  Specify
     the 'mode' argument for opening it for writing and silencing a
     warning.  (Contributed by Serhiy Storchaka in bpo-28286(4).)

   * Deprecated the ‘split()’ method of ‘_tkinter.TkappType’ in favour
     of the ‘splitlist()’ method which has more consistent and
     predictable behavior.  (Contributed by Serhiy Storchaka in
     bpo-38371(5).)

   * The explicit passing of coroutine objects to *note asyncio.wait():
     426. has been deprecated and will be removed in version 3.11.
     (Contributed by Yury Selivanov and Kyle Stanley in bpo-34790(6).)

   * binhex4 and hexbin4 standards are now deprecated.  The ‘binhex’
     module and the following *note binascii: c. functions are now
     deprecated:

        * ‘b2a_hqx()’、‘a2b_hqx()’

        * ‘rlecode_hqx()’、‘rledecode_hqx()’

     （由 Victor Stinner 在 bpo-39353(7) 中貢獻。）

   * *note ast: 7. classes ‘slice’, ‘Index’ and ‘ExtSlice’ are
     considered deprecated and will be removed in future Python
     versions.  ‘value’ itself should be used instead of ‘Index(value)’.
     ‘Tuple(slices, Load())’ should be used instead of
     ‘ExtSlice(slices)’.  (Contributed by Serhiy Storchaka in
     bpo-34822(8).)

   * *note ast: 7. classes ‘Suite’, ‘Param’, ‘AugLoad’ and ‘AugStore’
     are considered deprecated and will be removed in future Python
     versions.  They were not generated by the parser and not accepted
     by the code generator in Python 3.  (Contributed by Batuhan Taskaya
     in bpo-39639(9) and bpo-39969(10) and Serhiy Storchaka in
     bpo-39988(11).)

   * The ‘PyEval_InitThreads()’ and ‘PyEval_ThreadsInitialized()’
     functions are now deprecated and will be removed in Python 3.11.
     Calling ‘PyEval_InitThreads()’ now does nothing.  The *note GIL:
     13e. is initialized by *note Py_Initialize(): 851. since Python
     3.7.  (Contributed by Victor Stinner in bpo-39877(12).)

   * Passing ‘None’ as the first argument to the *note shlex.split():
     4e1. function has been deprecated.  (Contributed by Zackery Spytz
     in bpo-33262(13).)

   * ‘smtpd.MailmanProxy()’ is now deprecated as it is unusable without
     an external module, ‘mailman’.  (Contributed by Samuel Colvin in
     bpo-35800(14).)

   * The ‘lib2to3’ module now emits a *note PendingDeprecationWarning:
     86d.  Python 3.9 switched to a PEG parser (see PEP 617(15)), and
     Python 3.10 may include new language syntax that is not parsable by
     lib2to3's LL(1) parser.  The ‘lib2to3’ module may be removed from
     the standard library in a future Python version.  Consider
     third-party alternatives such as LibCST(16) or parso(17).
     (Contributed by Carl Meyer in bpo-40360(18).)

   * The 'random' parameter of *note random.shuffle(): 6eb. has been
     deprecated.  (Contributed by Raymond Hettinger in bpo-40465(19))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39586

   (2) https://bugs.python.org/issue?@action=redirect&bpo=37315

   (3) https://bugs.python.org/issue?@action=redirect&bpo=35712

   (4) https://bugs.python.org/issue?@action=redirect&bpo=28286

   (5) https://bugs.python.org/issue?@action=redirect&bpo=38371

   (6) https://bugs.python.org/issue?@action=redirect&bpo=34790

   (7) https://bugs.python.org/issue?@action=redirect&bpo=39353

   (8) https://bugs.python.org/issue?@action=redirect&bpo=34822

   (9) https://bugs.python.org/issue?@action=redirect&bpo=39639

   (10) https://bugs.python.org/issue?@action=redirect&bpo=39969

   (11) https://bugs.python.org/issue?@action=redirect&bpo=39988

   (12) https://bugs.python.org/issue?@action=redirect&bpo=39877

   (13) https://bugs.python.org/issue?@action=redirect&bpo=33262

   (14) https://bugs.python.org/issue?@action=redirect&bpo=35800

   (15) https://peps.python.org/pep-0617/

   (16) https://libcst.readthedocs.io/

   (17) https://parso.readthedocs.io/

   (18) https://bugs.python.org/issue?@action=redirect&bpo=40360

   (19) https://bugs.python.org/issue?@action=redirect&bpo=40465


File: python.info,  Node: 已移除<5>,  Next: Porting to Python 3 9,  Prev: 已棄用<7>,  Up: Python 3 9 有什麼新功能

1.5.9 已移除
------------

   * The erroneous version at ‘unittest.mock.__version__’ has been
     removed.

   * ‘nntplib.NNTP’: ‘xpath()’ and ‘xgtitle()’ methods have been
     removed.  These methods are deprecated since Python 3.3.
     Generally, these extensions are not supported or not enabled by
     NNTP server administrators.  For ‘xgtitle()’, please use
     ‘nntplib.NNTP.descriptions()’ or ‘nntplib.NNTP.description()’
     instead.  (Contributed by Donghee Na in bpo-39366(1).)

   * *note array.array: 186.: ‘tostring()’ and ‘fromstring()’ methods
     have been removed.  They were aliases to ‘tobytes()’ and
     ‘frombytes()’, deprecated since Python 3.2.  (Contributed by Victor
     Stinner in bpo-38916(2).)

   * The undocumented ‘sys.callstats()’ function has been removed.
     Since Python 3.7, it was deprecated and always returned *note None:
     61b.  It required a special build option ‘CALL_PROFILE’ which was
     already removed in Python 3.7.  (Contributed by Victor Stinner in
     bpo-37414(3).)

   * The ‘sys.getcheckinterval()’ and ‘sys.setcheckinterval()’ functions
     have been removed.  They were deprecated since Python 3.2.  Use
     *note sys.getswitchinterval(): 8ed. and *note
     sys.setswitchinterval(): 8ee. instead.  (Contributed by Victor
     Stinner in bpo-37392(4).)

   * The C function ‘PyImport_Cleanup()’ has been removed.  It was
     documented as: "Empty the module table.  For internal use only."
     (Contributed by Victor Stinner in bpo-36710(5).)

   * ‘_dummy_thread’ and ‘dummy_threading’ modules have been removed.
     These modules were deprecated since Python 3.7 which requires
     threading support.  (Contributed by Victor Stinner in
     bpo-37312(6).)

   * ‘aifc.openfp()’ alias to ‘aifc.open()’, ‘sunau.openfp()’ alias to
     ‘sunau.open()’, and ‘wave.openfp()’ alias to *note wave.open():
     8ef. have been removed.  They were deprecated since Python 3.7.
     (Contributed by Victor Stinner in bpo-37320(7).)

   * The ‘isAlive()’ method of *note threading.Thread: 8f0. has been
     removed.  It was deprecated since Python 3.8.  Use *note
     is_alive(): 8f1. instead.  (Contributed by Donghee Na in
     bpo-37804(8).)

   * Methods ‘getchildren()’ and ‘getiterator()’ of classes *note
     ElementTree: 8f2. and *note Element: 2e2. in the *note ElementTree:
     10c. module have been removed.  They were deprecated in Python 3.2.
     Use ‘iter(x)’ or ‘list(x)’ instead of ‘x.getchildren()’ and
     ‘x.iter()’ or ‘list(x.iter())’ instead of ‘x.getiterator()’.
     (Contributed by Serhiy Storchaka in bpo-36543(9).)

   * The old *note plistlib: 99. API has been removed, it was deprecated
     since Python 3.4.  Use the *note load(): 8f3, *note loads(): 8f4,
     *note dump(): 8f5, and *note dumps(): 8f6. functions.
     Additionally, the 'use_builtin_types' parameter was removed,
     standard *note bytes: 1a5. objects are always used instead.
     (Contributed by Jon Janzen in bpo-36409(10).)

   * The C function ‘PyGen_NeedsFinalizing’ has been removed.  It was
     not documented, tested, or used anywhere within CPython after the
     implementation of PEP 442(11).  Patch by Joannah Nanjekye.
     (Contributed by Joannah Nanjekye in bpo-15088(12))

   * ‘base64.encodestring()’ and ‘base64.decodestring()’, aliases
     deprecated since Python 3.1, have been removed: use *note
     base64.encodebytes(): 8f7. and *note base64.decodebytes(): 8f8.
     instead.  (Contributed by Victor Stinner in bpo-39351(13).)

   * ‘fractions.gcd()’ function has been removed, it was deprecated
     since Python 3.5 (bpo-22486(14)): use *note math.gcd(): 8b5.
     instead.  (Contributed by Victor Stinner in bpo-39350(15).)

   * The 'buffering' parameter of *note bz2.BZ2File: 80b. has been
     removed.  Since Python 3.0, it was ignored and using it emitted a
     *note DeprecationWarning: 18b.  Pass an open file object to control
     how the file is opened.  (Contributed by Victor Stinner in
     bpo-39357(16).)

   * The 'encoding' parameter of *note json.loads(): 8f9. has been
     removed.  As of Python 3.1, it was deprecated and ignored; using it
     has emitted a *note DeprecationWarning: 18b. since Python 3.8.
     (Contributed by Inada Naoki in bpo-39377(17))

   * ‘with (await asyncio.lock):’ and ‘with (yield from asyncio.lock):’
     statements are not longer supported, use ‘async with lock’ instead.
     The same is correct for ‘asyncio.Condition’ and
     ‘asyncio.Semaphore’.  (Contributed by Andrew Svetlov in
     bpo-34793(18).)

   * The ‘sys.getcounts()’ function, the ‘-X showalloccount’ command
     line option and the ‘show_alloc_count’ field of the C structure
     *note PyConfig: 371. have been removed.  They required a special
     Python build by defining ‘COUNT_ALLOCS’ macro.  (Contributed by
     Victor Stinner in bpo-39489(19).)

   * The ‘_field_types’ attribute of the *note typing.NamedTuple: 291.
     class has been removed.  It was deprecated since Python 3.8.  Use
     the ‘__annotations__’ attribute instead.  (Contributed by Serhiy
     Storchaka in bpo-40182(20).)

   * The ‘symtable.SymbolTable.has_exec()’ method has been removed.  It
     was deprecated since 2006, and only returning ‘False’ when it's
     called.  (Contributed by Batuhan Taskaya in bpo-40208(21))

   * The ‘asyncio.Task.current_task()’ and ‘asyncio.Task.all_tasks()’
     have been removed.  They were deprecated since Python 3.7 and you
     can use *note asyncio.current_task(): 424. and *note
     asyncio.all_tasks(): 8fa. instead.  (Contributed by Rémi Lapeyre in
     bpo-40967(22))

   * The ‘unescape()’ method in the *note html.parser.HTMLParser: 81a.
     class has been removed (it was deprecated since Python 3.4).  *note
     html.unescape(): 8fb. should be used for converting character
     references to the corresponding unicode characters.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39366

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38916

   (3) https://bugs.python.org/issue?@action=redirect&bpo=37414

   (4) https://bugs.python.org/issue?@action=redirect&bpo=37392

   (5) https://bugs.python.org/issue?@action=redirect&bpo=36710

   (6) https://bugs.python.org/issue?@action=redirect&bpo=37312

   (7) https://bugs.python.org/issue?@action=redirect&bpo=37320

   (8) https://bugs.python.org/issue?@action=redirect&bpo=37804

   (9) https://bugs.python.org/issue?@action=redirect&bpo=36543

   (10) https://bugs.python.org/issue?@action=redirect&bpo=36409

   (11) https://peps.python.org/pep-0442/

   (12) https://bugs.python.org/issue?@action=redirect&bpo=15088

   (13) https://bugs.python.org/issue?@action=redirect&bpo=39351

   (14) https://bugs.python.org/issue?@action=redirect&bpo=22486

   (15) https://bugs.python.org/issue?@action=redirect&bpo=39350

   (16) https://bugs.python.org/issue?@action=redirect&bpo=39357

   (17) https://bugs.python.org/issue?@action=redirect&bpo=39377

   (18) https://bugs.python.org/issue?@action=redirect&bpo=34793

   (19) https://bugs.python.org/issue?@action=redirect&bpo=39489

   (20) https://bugs.python.org/issue?@action=redirect&bpo=40182

   (21) https://bugs.python.org/issue?@action=redirect&bpo=40208

   (22) https://bugs.python.org/issue?@action=redirect&bpo=40967


File: python.info,  Node: Porting to Python 3 9,  Next: 建置變更<4>,  Prev: 已移除<5>,  Up: Python 3 9 有什麼新功能

1.5.10 Porting to Python 3.9
----------------------------

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

* Menu:

* Changes in the Python API: Changes in the Python API<2>.
* C API 中的改動: C API 中的改動<2>.
* CPython 位元組碼變更: CPython 位元組碼變更<4>.


File: python.info,  Node: Changes in the Python API<2>,  Next: C API 中的改動<2>,  Up: Porting to Python 3 9

1.5.10.1 Changes in the Python API
..................................

   * *note __import__(): 879. and *note importlib.util.resolve_name():
     8af. now raise *note ImportError: 352. where it previously raised
     *note ValueError: 1e7.  Callers catching the specific exception
     type and supporting both Python 3.9 and earlier versions will need
     to catch both using ‘except (ImportError, ValueError):’.

   * The *note venv: f9. activation scripts no longer special-case when
     ‘__VENV_PROMPT__’ is set to ‘""’.

   * The *note select.epoll.unregister(): 8fe. method no longer ignores
     the *note EBADF: 8ff. error.  (Contributed by Victor Stinner in
     bpo-39239(1).)

   * The 'compresslevel' parameter of *note bz2.BZ2File: 80b. became
     keyword-only, since the 'buffering' parameter has been removed.
     (Contributed by Victor Stinner in bpo-39357(2).)

   * Simplified AST for subscription.  Simple indices will be
     represented by their value, extended slices will be represented as
     tuples.  ‘Index(value)’ will return a ‘value’ itself,
     ‘ExtSlice(slices)’ will return ‘Tuple(slices, Load())’.
     (Contributed by Serhiy Storchaka in bpo-34822(3).)

   * The *note importlib: 6b. module now ignores the *note PYTHONCASEOK:
     900. environment variable when the *note -E: 901. or *note -I: 902.
     command line options are being used.

   * The 'encoding' parameter has been added to the classes *note
     ftplib.FTP: 89f. and *note ftplib.FTP_TLS: 8a0. as a keyword-only
     parameter, and the default encoding is changed from Latin-1 to
     UTF-8 to follow RFC 2640(4).

   * *note asyncio.loop.shutdown_default_executor(): 88c. has been added
     to *note AbstractEventLoop: 903, meaning alternative event loops
     that inherit from it should have this method defined.  (Contributed
     by Kyle Stanley in bpo-34037(5).)

   * The constant values of future flags in the *note __future__: 0.
     module is updated in order to prevent collision with compiler
     flags.  Previously ‘PyCF_ALLOW_TOP_LEVEL_AWAIT’ was clashing with
     ‘CO_FUTURE_DIVISION’.  (Contributed by Batuhan Taskaya in
     bpo-39562(6))

   * ‘array('u')’ now uses ‘wchar_t’ as C type instead of ‘Py_UNICODE’.
     This change doesn't affect to its behavior because ‘Py_UNICODE’ is
     alias of ‘wchar_t’ since Python 3.3.  (Contributed by Inada Naoki
     in bpo-34538(7).)

   * The *note logging.getLogger(): 904. API now returns the root logger
     when passed the name ‘'root'’, whereas previously it returned a
     non-root logger named ‘'root'’.  This could affect cases where user
     code explicitly wants a non-root logger named ‘'root'’, or
     instantiates a logger using ‘logging.getLogger(__name__)’ in some
     top-level module called ‘'root.py'’.  (Contributed by Vinay Sajip
     in bpo-37742(8).)

   * Division handling of *note PurePath: 44e. now returns *note
     NotImplemented: 776. instead of raising a *note TypeError: 4dd.
     when passed something other than an instance of ‘str’ or *note
     PurePath: 44e.  This allows creating compatible classes that don't
     inherit from those mentioned types.  (Contributed by Roger Aiudi in
     bpo-34775(9)).

   * Starting with Python 3.9.5 the *note ipaddress: 74. module no
     longer accepts any leading zeros in IPv4 address strings.  Leading
     zeros are ambiguous and interpreted as octal notation by some
     libraries.  For example the legacy function *note
     socket.inet_aton(): 905. treats leading zeros as octal notatation.
     glibc implementation of modern *note inet_pton(): 906. does not
     accept any leading zeros.  (Contributed by Christian Heimes in
     bpo-36384(10)).

   * *note codecs.lookup(): 907. now normalizes the encoding name the
     same way as ‘encodings.normalize_encoding()’, except that *note
     codecs.lookup(): 907. also converts the name to lower case.  For
     example, ‘"latex+latin1"’ encoding name is now normalized to
     ‘"latex_latin1"’.  (Contributed by Jordon Xu in bpo-37751(11).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39239

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39357

   (3) https://bugs.python.org/issue?@action=redirect&bpo=34822

   (4) https://datatracker.ietf.org/doc/html/rfc2640.html

   (5) https://bugs.python.org/issue?@action=redirect&bpo=34037

   (6) https://bugs.python.org/issue?@action=redirect&bpo=39562

   (7) https://bugs.python.org/issue?@action=redirect&bpo=34538

   (8) https://bugs.python.org/issue?@action=redirect&bpo=37742

   (9) https://bugs.python.org/issue?@action=redirect&bpo=34775

   (10) https://bugs.python.org/issue?@action=redirect&bpo=36384

   (11) https://bugs.python.org/issue?@action=redirect&bpo=37751


File: python.info,  Node: C API 中的改動<2>,  Next: CPython 位元組碼變更<4>,  Prev: Changes in the Python API<2>,  Up: Porting to Python 3 9

1.5.10.2 C API 中的改動
.......................

   * Instances of *note heap-allocated types: 909. (such as those
     created with *note PyType_FromSpec(): 523. and similar APIs) hold a
     reference to their type object since Python 3.8.  As indicated in
     the "Changes in the C API" of Python 3.8, for the vast majority of
     cases, there should be no side effect but for types that have a
     custom *note tp_traverse: 721. function, ensure that all custom
     ‘tp_traverse’ functions of heap-allocated types visit the object's
     type.

          範例：

               int
               foo_traverse(foo_struct *self, visitproc visit, void *arg) {
               // Rest of the traverse function
               #if PY_VERSION_HEX >= 0x03090000
                   // This was not needed before Python 3.9 (Python issue 35810 and 40217)
                   Py_VISIT(Py_TYPE(self));
               #endif
               }

     If your traverse function delegates to ‘tp_traverse’ of its base
     class (or another type), ensure that ‘Py_TYPE(self)’ is visited
     only once.  Note that only *note heap type: 909. are expected to
     visit the type in ‘tp_traverse’.

          For example, if your ‘tp_traverse’ function includes:

               base->tp_traverse(self, visit, arg)

          then add:

               #if PY_VERSION_HEX >= 0x03090000
                   // This was not needed before Python 3.9 (bpo-35810 and bpo-40217)
                   if (base->tp_flags & Py_TPFLAGS_HEAPTYPE) {
                       // a heap type's tp_traverse already visited Py_TYPE(self)
                   } else {
                       Py_VISIT(Py_TYPE(self));
                   }
               #else

     （更多資訊請見 bpo-35810(1) 與 bpo-40217(2)。）

   * The functions ‘PyEval_CallObject’, ‘PyEval_CallFunction’,
     ‘PyEval_CallMethod’ and ‘PyEval_CallObjectWithKeywords’ are
     deprecated.  Use *note PyObject_Call(): 363. and its variants
     instead.  (See more details in bpo-29548(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35810

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40217

   (3) https://bugs.python.org/issue?@action=redirect&bpo=29548


File: python.info,  Node: CPython 位元組碼變更<4>,  Prev: C API 中的改動<2>,  Up: Porting to Python 3 9

1.5.10.3 CPython 位元組碼變更
.............................

   * The *note LOAD_ASSERTION_ERROR: 90b. opcode was added for handling
     the *note assert: 90c. statement.  Previously, the assert statement
     would not work correctly if the *note AssertionError: 64e.
     exception was being shadowed.  (Contributed by Zackery Spytz in
     bpo-34880(1).)

   * The *note COMPARE_OP: 90d. opcode was split into four distinct
     instructions:

        * ‘COMPARE_OP’ for rich comparisons

        * ‘IS_OP’ for 'is' and 'is not' tests

        * ‘CONTAINS_OP’ for 'in' and 'not in' tests

        * ‘JUMP_IF_NOT_EXC_MATCH’ for checking exceptions in
          'try-except' statements.

     （由 Mark Shannon 在 bpo-39156(2) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=34880

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39156


File: python.info,  Node: 建置變更<4>,  Next: C API 變更<4>,  Prev: Porting to Python 3 9,  Up: Python 3 9 有什麼新功能

1.5.11 建置變更
---------------

   * Added ‘--with-platlibdir’ option to the ‘configure’ script: name of
     the platform-specific library directory, stored in the new *note
     sys.platlibdir: 8dc. attribute.  See *note sys.platlibdir: 8dc.
     attribute for more information.  (Contributed by Jan Matějek, Matěj
     Cepl, Charalampos Stratakis and Victor Stinner in bpo-1294959(1).)

   * The ‘COUNT_ALLOCS’ special build macro has been removed.
     (Contributed by Victor Stinner in bpo-39489(2).)

   * On non-Windows platforms, the ‘setenv()’ and ‘unsetenv()’ functions
     are now required to build Python.  (Contributed by Victor Stinner
     in bpo-39395(3).)

   * On non-Windows platforms, creating ‘bdist_wininst’ installers is
     now officially unsupported.  (See bpo-10945(4) for more details.)

   * When building Python on macOS from source, ‘_tkinter’ now links
     with non-system Tcl and Tk frameworks if they are installed in
     ‘/Library/Frameworks’, as had been the case on older releases of
     macOS. If a macOS SDK is explicitly configured, by using *note
     -enable-universalsdk: 90f. or ‘-isysroot’, only the SDK itself is
     searched.  The default behavior can still be overridden with
     ‘--with-tcltk-includes’ and ‘--with-tcltk-libs’.  (Contributed by
     Ned Deily in bpo-34956(5).)

   * Python can now be built for Windows 10 ARM64.  (Contributed by
     Steve Dower in bpo-33125(6).)

   * Some individual tests are now skipped when ‘--pgo’ is used.  The
     tests in question increased the PGO task time significantly and
     likely didn't help improve optimization of the final executable.
     This speeds up the task by a factor of about 15x.  Running the full
     unit test suite is slow.  This change may result in a slightly less
     optimized build since not as many code branches will be executed.
     If you are willing to wait for the much slower build, the old
     behavior can be restored using ‘./configure [..] PROFILE_TASK="-m
     test --pgo-extended"’.  We make no guarantees as to which PGO task
     set produces a faster build.  Users who care should run their own
     relevant benchmarks as results can depend on the environment,
     workload, and compiler tool chain.  (See bpo-36044(7) and
     bpo-37707(8) for more details.)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1294959

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39489

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39395

   (4) https://bugs.python.org/issue?@action=redirect&bpo=10945

   (5) https://bugs.python.org/issue?@action=redirect&bpo=34956

   (6) https://bugs.python.org/issue?@action=redirect&bpo=33125

   (7) https://bugs.python.org/issue?@action=redirect&bpo=36044

   (8) https://bugs.python.org/issue?@action=redirect&bpo=37707


File: python.info,  Node: C API 變更<4>,  Next: Python 3 9 1 中顯著的變更,  Prev: 建置變更<4>,  Up: Python 3 9 有什麼新功能

1.5.12 C API 變更
-----------------

* Menu:

* New Features: New Features<4>.
* Porting to Python 3.9: Porting to Python 3 9<2>.
* 已移除: 已移除<6>.


File: python.info,  Node: New Features<4>,  Next: Porting to Python 3 9<2>,  Up: C API 變更<4>

1.5.12.1 New Features
.....................

   * PEP 573(1): Added *note PyType_FromModuleAndSpec(): 4f7. to
     associate a module with a class; *note PyType_GetModule(): 912. and
     *note PyType_GetModuleState(): 913. to retrieve the module and its
     state; and *note PyCMethod: 708. and *note METH_METHOD: 914. to
     allow a method to access the class it was defined in.  (Contributed
     by Marcel Plch and Petr Viktorin in bpo-38787(2).)

   * Added *note PyFrame_GetCode(): 72e. function: get a frame code.
     Added *note PyFrame_GetBack(): 72a. function: get the frame next
     outer frame.  (Contributed by Victor Stinner in bpo-40421(3).)

   * Added *note PyFrame_GetLineNumber(): 72f. to the limited C API.
     (Contributed by Victor Stinner in bpo-40421(4).)

   * Added *note PyThreadState_GetInterpreter(): 915. and *note
     PyInterpreterState_Get(): 378. functions to get the interpreter.
     Added *note PyThreadState_GetFrame(): 732. function to get the
     current frame of a Python thread state.  Added *note
     PyThreadState_GetID(): 916. function: get the unique identifier of
     a Python thread state.  (Contributed by Victor Stinner in
     bpo-39947(5).)

   * Added a new public *note PyObject_CallNoArgs(): 362. function to
     the C API, which calls a callable Python object without any
     arguments.  It is the most efficient way to call a callable Python
     object without any argument.  (Contributed by Victor Stinner in
     bpo-37194(6).)

   * Changes in the limited C API (if ‘Py_LIMITED_API’ macro is
     defined):

        * Provide *note Py_EnterRecursiveCall(): 917. and *note
          Py_LeaveRecursiveCall(): 918. as regular functions for the
          limited API. Previously, there were defined as macros, but
          these macros didn't compile with the limited C API which
          cannot access ‘PyThreadState.recursion_depth’ field (the
          structure is opaque in the limited C API).

        * ‘PyObject_INIT()’ and ‘PyObject_INIT_VAR()’ become regular
          "opaque" function to hide implementation details.

     （由 Victor Stinner 在 38644 和 39542 中貢獻。）

   * The *note PyModule_AddType(): 919. function is added to help adding
     a type to a module.  (Contributed by Donghee Na in bpo-40024(7).)

   * Added the functions *note PyObject_GC_IsTracked(): 91a. and *note
     PyObject_GC_IsFinalized(): 91b. to the public API to allow to query
     if Python objects are being currently tracked or have been already
     finalized by the garbage collector respectively.  (Contributed by
     Pablo Galindo Salgado in bpo-40241(8).)

   * Added ‘_PyObject_FunctionStr()’ to get a user-friendly string
     representation of a function-like object.  (Patch by Jeroen Demeyer
     in bpo-37645(9).)

   * Added *note PyObject_CallOneArg(): 91c. for calling an object with
     one positional argument (Patch by Jeroen Demeyer in bpo-37483(10).)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0573/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38787

   (3) https://bugs.python.org/issue?@action=redirect&bpo=40421

   (4) https://bugs.python.org/issue?@action=redirect&bpo=40421

   (5) https://bugs.python.org/issue?@action=redirect&bpo=39947

   (6) https://bugs.python.org/issue?@action=redirect&bpo=37194

   (7) https://bugs.python.org/issue?@action=redirect&bpo=40024

   (8) https://bugs.python.org/issue?@action=redirect&bpo=40241

   (9) https://bugs.python.org/issue?@action=redirect&bpo=37645

   (10) https://bugs.python.org/issue?@action=redirect&bpo=37483


File: python.info,  Node: Porting to Python 3 9<2>,  Next: 已移除<6>,  Prev: New Features<4>,  Up: C API 變更<4>

1.5.12.2 Porting to Python 3.9
..............................

   * ‘PyInterpreterState.eval_frame’ ( PEP 523(1)) now requires a new
     mandatory 'tstate' parameter (‘PyThreadState*’).  (Contributed by
     Victor Stinner in bpo-38500(2).)

   * Extension modules: *note m_traverse: 91e, *note m_clear: 91f. and
     *note m_free: 920. functions of *note PyModuleDef: 921. are no
     longer called if the module state was requested but is not
     allocated yet.  This is the case immediately after the module is
     created and before the module is executed (*note Py_mod_exec: 922.
     function).  More precisely, these functions are not called if *note
     m_size: 923. is greater than 0 and the module state (as returned by
     *note PyModule_GetState(): 924.) is ‘NULL’.

     Extension modules without module state (‘m_size <= 0’) are not
     affected.

   * If *note Py_AddPendingCall(): 925. is called in a subinterpreter,
     the function is now scheduled to be called from the subinterpreter,
     rather than being called from the main interpreter.  Each
     subinterpreter now has its own list of scheduled calls.
     (Contributed by Victor Stinner in bpo-39984(3).)

   * The Windows registry is no longer used to initialize *note
     sys.path: 37f. when the ‘-E’ option is used (if *note
     PyConfig.use_environment: 3a4. is set to ‘0’).  This is significant
     when embedding Python on Windows.  (Contributed by Zackery Spytz in
     bpo-8901(4).)

   * The global variable *note PyStructSequence_UnnamedField: 926. is
     now a constant and refers to a constant string.  (Contributed by
     Serhiy Storchaka in bpo-38650(5).)

   * The ‘PyGC_Head’ structure is now opaque.  It is only defined in the
     internal C API (‘pycore_gc.h’).  (Contributed by Victor Stinner in
     bpo-40241(6).)

   * The ‘Py_UNICODE_COPY’, ‘Py_UNICODE_FILL’, ‘PyUnicode_WSTR_LENGTH’,
     ‘PyUnicode_FromUnicode()’, ‘PyUnicode_AsUnicode()’,
     ‘_PyUnicode_AsUnicode’, and ‘PyUnicode_AsUnicodeAndSize()’ are
     marked as deprecated in C. They have been deprecated by PEP 393(7)
     since Python 3.3.  (Contributed by Inada Naoki in bpo-36346(8).)

   * The *note Py_FatalError(): 927. function is replaced with a macro
     which logs automatically the name of the current function, unless
     the ‘Py_LIMITED_API’ macro is defined.  (Contributed by Victor
     Stinner in bpo-39882(9).)

   * The vectorcall protocol now requires that the caller passes only
     strings as keyword names.  (See bpo-37540(10) for more
     information.)

   * Implementation details of a number of macros and functions are now
     hidden:

        * *note PyObject_IS_GC(): 928. macro was converted to a
          function.

        * The ‘PyObject_NEW()’ macro becomes an alias to the *note
          PyObject_New: 929. macro, and the ‘PyObject_NEW_VAR()’ macro
          becomes an alias to the *note PyObject_NewVar: 92a. macro.
          They no longer access directly the *note
          PyTypeObject.tp_basicsize: 92b. member.

        * ‘PyObject_GET_WEAKREFS_LISTPTR()’ macro was converted to a
          function: the macro accessed directly the *note
          PyTypeObject.tp_weaklistoffset: 92c. member.

        * *note PyObject_CheckBuffer(): 368. macro was converted to a
          function: the macro accessed directly the *note
          PyTypeObject.tp_as_buffer: 92d. member.

        * *note PyIndex_Check(): 92e. is now always declared as an
          opaque function to hide implementation details: removed the
          ‘PyIndex_Check()’ macro.  The macro accessed directly the
          *note PyTypeObject.tp_as_number: 92f. member.

     （更多資訊請見 bpo-40170(11)。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0523/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38500

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39984

   (4) https://bugs.python.org/issue?@action=redirect&bpo=8901

   (5) https://bugs.python.org/issue?@action=redirect&bpo=38650

   (6) https://bugs.python.org/issue?@action=redirect&bpo=40241

   (7) https://peps.python.org/pep-0393/

   (8) https://bugs.python.org/issue?@action=redirect&bpo=36346

   (9) https://bugs.python.org/issue?@action=redirect&bpo=39882

   (10) https://bugs.python.org/issue?@action=redirect&bpo=37540

   (11) https://bugs.python.org/issue?@action=redirect&bpo=40170


File: python.info,  Node: 已移除<6>,  Prev: Porting to Python 3 9<2>,  Up: C API 變更<4>

1.5.12.3 已移除
...............

   * Excluded ‘PyFPE_START_PROTECT()’ and ‘PyFPE_END_PROTECT()’ macros
     of ‘pyfpe.h’ from the limited C API. (Contributed by Victor Stinner
     in bpo-38835(1).)

   * The ‘tp_print’ slot of *note PyTypeObject: 931. has been removed.
     It was used for printing objects to files in Python 2.7 and before.
     Since Python 3.0, it has been ignored and unused.  (Contributed by
     Jeroen Demeyer in bpo-36974(2).)

   * Changes in the limited C API (if ‘Py_LIMITED_API’ macro is
     defined):

        * Excluded the following functions from the limited C API:

             * ‘PyThreadState_DeleteCurrent()’ (Contributed by Joannah
               Nanjekye in bpo-37878(3).)

             * ‘_Py_CheckRecursionLimit’

             * ‘_Py_NewReference()’

             * ‘_Py_ForgetReference()’

             * ‘_PyTraceMalloc_NewReference()’

             * ‘_Py_GetRefTotal()’

             * The trashcan mechanism which never worked in the limited
               C API.

             * ‘PyTrash_UNWIND_LEVEL’

             * ‘Py_TRASHCAN_BEGIN_CONDITION’

             * ‘Py_TRASHCAN_BEGIN’

             * ‘Py_TRASHCAN_END’

             * ‘Py_TRASHCAN_SAFE_BEGIN’

             * ‘Py_TRASHCAN_SAFE_END’

        * Moved following functions and definitions to the internal C
          API:

             * ‘_PyDebug_PrintTotalRefs()’

             * ‘_Py_PrintReferences()’

             * ‘_Py_PrintReferenceAddresses()’

             * ‘_Py_tracemalloc_config’

             * ‘_Py_AddToAllObjects()’ (specific to ‘Py_TRACE_REFS’
               build)

     （由 Victor Stinner 在 38644 和 39542 中貢獻。）

   * Removed ‘_PyRuntime.getframe’ hook and removed
     ‘_PyThreadState_GetFrame’ macro which was an alias to
     ‘_PyRuntime.getframe’.  They were only exposed by the internal C
     API. Removed also ‘PyThreadFrameGetter’ type.  (Contributed by
     Victor Stinner in bpo-39946(4).)

   * Removed the following functions from the C API. Call *note
     PyGC_Collect(): 932. explicitly to clear all free lists.
     (Contributed by Inada Naoki and Victor Stinner in bpo-37340(5),
     bpo-38896(6) and bpo-40428(7).)

        * ‘PyAsyncGen_ClearFreeLists()’

        * ‘PyContext_ClearFreeList()’

        * ‘PyDict_ClearFreeList()’

        * ‘PyFloat_ClearFreeList()’

        * ‘PyFrame_ClearFreeList()’

        * ‘PyList_ClearFreeList()’

        * ‘PyMethod_ClearFreeList()’ and ‘PyCFunction_ClearFreeList()’:
          the free lists of bound method objects have been removed.

        * ‘PySet_ClearFreeList()’: the set free list has been removed in
          Python 3.4.

        * ‘PyTuple_ClearFreeList()’

        * ‘PyUnicode_ClearFreeList()’: the Unicode free list has been
          removed in Python 3.3.

   * Removed ‘_PyUnicode_ClearStaticStrings()’ function.  (Contributed
     by Victor Stinner in bpo-39465(8).)

   * Removed ‘Py_UNICODE_MATCH’.  It has been deprecated by PEP 393(9),
     and broken since Python 3.3.  The *note PyUnicode_Tailmatch(): 85d.
     function can be used instead.  (Contributed by Inada Naoki in
     bpo-36346(10).)

   * Cleaned header files of interfaces defined but with no
     implementation.  The public API symbols being removed are:
     ‘_PyBytes_InsertThousandsGroupingLocale’,
     ‘_PyBytes_InsertThousandsGrouping’, ‘_Py_InitializeFromArgs’,
     ‘_Py_InitializeFromWideArgs’, ‘_PyFloat_Repr’, ‘_PyFloat_Digits’,
     ‘_PyFloat_DigitsInit’, ‘PyFrame_ExtendStack’,
     ‘_PyAIterWrapper_Type’, ‘PyNullImporter_Type’, ‘PyCmpWrapper_Type’,
     ‘PySortWrapper_Type’, ‘PyNoArgsFunction’.  (Contributed by Pablo
     Galindo Salgado in bpo-39372(11).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38835

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36974

   (3) https://bugs.python.org/issue?@action=redirect&bpo=37878

   (4) https://bugs.python.org/issue?@action=redirect&bpo=39946

   (5) https://bugs.python.org/issue?@action=redirect&bpo=37340

   (6) https://bugs.python.org/issue?@action=redirect&bpo=38896

   (7) https://bugs.python.org/issue?@action=redirect&bpo=40428

   (8) https://bugs.python.org/issue?@action=redirect&bpo=39465

   (9) https://peps.python.org/pep-0393/

   (10) https://bugs.python.org/issue?@action=redirect&bpo=36346

   (11) https://bugs.python.org/issue?@action=redirect&bpo=39372


File: python.info,  Node: Python 3 9 1 中顯著的變更,  Next: Python 3 9 2 中顯著的變更,  Prev: C API 變更<4>,  Up: Python 3 9 有什麼新功能

1.5.13 Python 3.9.1 中顯著的變更
--------------------------------

* Menu:

* typing: typing<7>.
* macOS 11.0 (Big Sur) and Apple Silicon Mac support: macOS 11 0 Big Sur and Apple Silicon Mac support.


File: python.info,  Node: typing<7>,  Next: macOS 11 0 Big Sur and Apple Silicon Mac support,  Up: Python 3 9 1 中顯著的變更

1.5.13.1 typing
...............

The behavior of *note typing.Literal: 7f9. was changed to conform with
PEP 586(1) and to match the behavior of static type checkers specified
in the PEP.

  1. ‘Literal’ now de-duplicates parameters.

  2. Equality comparisons between ‘Literal’ objects are now order
     independent.

  3. ‘Literal’ comparisons now respect types.  For example, ‘Literal[0]
     == Literal[False]’ previously evaluated to ‘True’.  It is now
     ‘False’.  To support this change, the internally used type cache
     now supports differentiating types.

  4. ‘Literal’ objects will now raise a *note TypeError: 4dd. exception
     during equality comparisons if any of their parameters are not
     *note hashable: 5b5.  Note that declaring ‘Literal’ with mutable
     parameters will not throw an error:

          >>> from typing import Literal
          >>> Literal[{0}]
          >>> Literal[{0}] == Literal[{False}]
          Traceback (most recent call last):
            File "<stdin>", line 1, in <module>
          TypeError: unhashable type: 'set'

（由 Yurii Karabas 在 bpo-42345(2) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0586/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42345


File: python.info,  Node: macOS 11 0 Big Sur and Apple Silicon Mac support,  Prev: typing<7>,  Up: Python 3 9 1 中顯著的變更

1.5.13.2 macOS 11.0 (Big Sur) and Apple Silicon Mac support
...........................................................

As of 3.9.1, Python now fully supports building and running on macOS
11.0 (Big Sur) and on Apple Silicon Macs (based on the ‘ARM64’
architecture).  A new universal build variant, ‘universal2’, is now
available to natively support both ‘ARM64’ and ‘Intel 64’ in one set of
executables.  Binaries can also now be built on current versions of
macOS to be deployed on a range of older macOS versions (tested to 10.9)
while making some newer OS functions and options conditionally available
based on the operating system version in use at runtime ("weaklinking").

（由 Ronald Oussoren 和 Lawrence D'Anna 在 bpo-41100(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41100


File: python.info,  Node: Python 3 9 2 中顯著的變更,  Next: Python 3 9 3 中顯著的變更,  Prev: Python 3 9 1 中顯著的變更,  Up: Python 3 9 有什麼新功能

1.5.14 Python 3.9.2 中顯著的變更
--------------------------------

* Menu:

* collections.abc: collections abc<2>.
* urllib.parse: urllib parse<2>.


File: python.info,  Node: collections abc<2>,  Next: urllib parse<2>,  Up: Python 3 9 2 中顯著的變更

1.5.14.1 collections.abc
........................

*note collections.abc.Callable: 78e. generic now flattens type
parameters, similar to what *note typing.Callable: 769. currently does.
This means that ‘collections.abc.Callable[[int, str], str]’ will have
‘__args__’ of ‘(int, str, str)’; previously this was ‘([int, str],
str)’.  To allow this change, *note types.GenericAlias: 78f. can now be
subclassed, and a subclass will be returned when subscripting the *note
collections.abc.Callable: 78e. type.  Code which accesses the arguments
via *note typing.get_args(): 822. or ‘__args__’ need to account for this
change.  A *note DeprecationWarning: 18b. may be emitted for invalid
forms of parameterizing *note collections.abc.Callable: 78e. which may
have passed silently in Python 3.9.1.  This *note DeprecationWarning:
18b. will become a *note TypeError: 4dd. in Python 3.10.  (Contributed
by Ken Jin in bpo-42195(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42195


File: python.info,  Node: urllib parse<2>,  Prev: collections abc<2>,  Up: Python 3 9 2 中顯著的變更

1.5.14.2 urllib.parse
.....................

Earlier Python versions allowed using both ‘;’ and ‘&’ as query
parameter separators in *note urllib.parse.parse_qs(): 25f. and *note
urllib.parse.parse_qsl(): 25e.  Due to security concerns, and to conform
with newer W3C recommendations, this has been changed to allow only a
single separator key, with ‘&’ as the default.  This change also affects
‘cgi.parse()’ and ‘cgi.parse_multipart()’ as they use the affected
functions internally.  For more details, please see their respective
documentation.  (Contributed by Adam Goldschmidt, Senthil Kumaran and
Ken Jin in bpo-42967(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42967


File: python.info,  Node: Python 3 9 3 中顯著的變更,  Next: Python 3 9 5 中顯著的變更,  Prev: Python 3 9 2 中顯著的變更,  Up: Python 3 9 有什麼新功能

1.5.15 Python 3.9.3 中顯著的變更
--------------------------------

A security fix alters the *note ftplib.FTP: 89f. behavior to not trust
the IPv4 address sent from the remote server when setting up a passive
data channel.  We reuse the ftp server IP address instead.  For unusual
code requiring the old behavior, set a ‘trust_server_pasv_ipv4_address’
attribute on your FTP instance to ‘True’.  (See gh-87451(1))

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/87451


File: python.info,  Node: Python 3 9 5 中顯著的變更,  Next: Notable security feature in 3 9 14,  Prev: Python 3 9 3 中顯著的變更,  Up: Python 3 9 有什麼新功能

1.5.16 Python 3.9.5 中顯著的變更
--------------------------------

* Menu:

* urllib.parse: urllib parse<3>.


File: python.info,  Node: urllib parse<3>,  Up: Python 3 9 5 中顯著的變更

1.5.16.1 urllib.parse
.....................

The presence of newline or tab characters in parts of a URL allows for
some forms of attacks.  Following the WHATWG specification that updates
RFC 3986(1), ASCII newline ‘\n’, ‘\r’ and tab ‘\t’ characters are
stripped from the URL by the parser in *note urllib.parse: f3.
preventing such attacks.  The removal characters are controlled by a new
module level variable ‘urllib.parse._UNSAFE_URL_BYTES_TO_REMOVE’.  (See
gh-88048(2))

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc3986.html

   (2) https://github.com/python/cpython/issues/88048


File: python.info,  Node: Notable security feature in 3 9 14,  Next: Notable changes in 3 9 17,  Prev: Python 3 9 5 中顯著的變更,  Up: Python 3 9 有什麼新功能

1.5.17 Notable security feature in 3.9.14
-----------------------------------------

Converting between *note int: 23c. and *note str: 3f2. in bases other
than 2 (binary), 4, 8 (octal), 16 (hexadecimal), or 32 such as base 10
(decimal) now raises a *note ValueError: 1e7. if the number of digits in
string form is above a limit to avoid potential denial of service
attacks due to the algorithmic complexity.  This is a mitigation for
CVE-2020-10735(1).  This limit can be configured or disabled by
environment variable, command line flag, or *note sys: c3. APIs.  See
the *note integer string conversion length limitation: 599.
documentation.  The default limit is 4300 digits in string form.

   ---------- Footnotes ----------

   (1) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10735


File: python.info,  Node: Notable changes in 3 9 17,  Prev: Notable security feature in 3 9 14,  Up: Python 3 9 有什麼新功能

1.5.18 Notable changes in 3.9.17
--------------------------------

* Menu:

* tarfile: tarfile<3>.


File: python.info,  Node: tarfile<3>,  Up: Notable changes in 3 9 17

1.5.18.1 tarfile
................

   * The extraction methods in *note tarfile: c8, and *note
     shutil.unpack_archive(): 412, 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
     *note Extraction filters: 413. for details.  In Python 3.12, use
     without the 'filter' argument will show a *note DeprecationWarning:
     18b.  In Python 3.14, the default will switch to ‘'data'’.
     (Contributed by Petr Viktorin in PEP 706(1).)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0706/


File: python.info,  Node: Python 3 8 有什麼新功能,  Next: Python 3 7 有什麼新功能,  Prev: Python 3 9 有什麼新功能,  Up: Python 有什麼新功能？

1.6 Python 3.8 有什麼新功能
===========================


編輯者: Raymond Hettinger

This article explains the new features in Python 3.8, compared to 3.7.
Python 3.8 was released on October 14, 2019.  For full details, see the
*note changelog: 122.

* Menu:

* Summary: Summary -- Release highlights<2>. Release highlights
* New Features: New Features<5>.
* 其他語言更動: 其他語言更動<5>.
* 新增模組: 新增模組<3>.
* 改進的模組: 改進的模組<5>.
* 最佳化: 最佳化<5>.
* Build and C API Changes::
* 已棄用: 已棄用<8>.
* API and Feature Removals::
* Porting to Python 3.8: Porting to Python 3 8.
* Python 3.8.1 中顯著的變更: Python 3 8 1 中顯著的變更.
* Python 3.8.2 中顯著的變更: Python 3 8 2 中顯著的變更.
* Python 3.8.3 中顯著的變更: Python 3 8 3 中顯著的變更.
* Python 3.8.8 中顯著的變更: Python 3 8 8 中顯著的變更.
* Python 3.8.9 中顯著的變更: Python 3 8 9 中顯著的變更.
* Python 3.8.10 中顯著的變更: Python 3 8 10 中顯著的變更.
* Python 3.8.10 中顯著的變更: Python 3 8 10 中顯著的變更<2>.
* Python 3.8.12 中顯著的變更: Python 3 8 12 中顯著的變更.
* Notable security feature in 3.8.14: Notable security feature in 3 8 14.
* Notable changes in 3.8.17: Notable changes in 3 8 17.


File: python.info,  Node: Summary -- Release highlights<2>,  Next: New Features<5>,  Up: Python 3 8 有什麼新功能

1.6.1 Summary - Release highlights
----------------------------------


File: python.info,  Node: New Features<5>,  Next: 其他語言更動<5>,  Prev: Summary -- Release highlights<2>,  Up: Python 3 8 有什麼新功能

1.6.2 New Features
------------------

* Menu:

* Assignment expressions::
* Positional-only parameters::
* Parallel filesystem cache for compiled bytecode files::
* Debug build uses the same ABI as release build::
* f-strings support = for self-documenting expressions and debugging::
* PEP 578; Python Runtime Audit Hooks: PEP 578 Python Runtime Audit Hooks.
* PEP 587; Python Initialization Configuration: PEP 587 Python Initialization Configuration.
* PEP 590; Vectorcall; a fast calling protocol for CPython: PEP 590 Vectorcall a fast calling protocol for CPython.
* Pickle protocol 5 with out-of-band data buffers::


File: python.info,  Node: Assignment expressions,  Next: Positional-only parameters,  Up: New Features<5>

1.6.2.1 Assignment expressions
..............................

There is new syntax ‘:=’ that assigns values to variables as part of a
larger expression.  It is affectionately known as "the walrus operator"
due to its resemblance to the eyes and tusks of a walrus(1).

In this example, the assignment expression helps avoid calling *note
len(): 5d4. twice:

     if (n := len(a)) > 10:
         print(f"List is too long ({n} elements, expected <= 10)")

A similar benefit arises during regular expression matching where match
objects are needed twice, once to test whether a match occurred and
another to extract a subgroup:

     discount = 0.0
     if (mo := re.search(r'(\d+)% discount', advertisement)):
         discount = float(mo.group(1)) / 100.0

The operator is also useful with while-loops that compute a value to
test loop termination and then need that same value again in the body of
the loop:

     # Loop over fixed length blocks
     while (block := f.read(256)) != '':
         process(block)

Another motivating use case arises in list comprehensions where a value
computed in a filtering condition is also needed in the expression body:

     [clean_name.title() for name in names
      if (clean_name := normalize('NFC', name)) in allowed_names]

Try to limit use of the walrus operator to clean cases that reduce
complexity and improve readability.

完整敘述請見 PEP 572(2)。

（由 Emily Morehouse 在 bpo-35224(3) 中貢獻。）

   ---------- Footnotes ----------

   (1) 
https://en.wikipedia.org/wiki/Walrus#/media/File:Pacific_Walrus_-_Bull_(8247646168).jpg

   (2) https://peps.python.org/pep-0572/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=35224


File: python.info,  Node: Positional-only parameters,  Next: Parallel filesystem cache for compiled bytecode files,  Prev: Assignment expressions,  Up: New Features<5>

1.6.2.2 Positional-only parameters
..................................

There is a new function parameter syntax ‘/’ to indicate that some
function parameters must be specified positionally and cannot be used as
keyword arguments.  This is the same notation shown by ‘help()’ for C
functions annotated with Larry Hastings' Argument Clinic(1) tool.

In the following example, parameters 'a' and 'b' are positional-only,
while 'c' or 'd' can be positional or keyword, and 'e' or 'f' are
required to be keywords:

     def f(a, b, /, c, d, *, e, f):
         print(a, b, c, d, e, f)

The following is a valid call:

     f(10, 20, 30, d=40, e=50, f=60)

However, these are invalid calls:

     f(10, b=20, c=30, d=40, e=50, f=60)   # b cannot be a keyword argument
     f(10, 20, 30, 40, 50, f=60)           # e must be a keyword argument

One use case for this notation is that it allows pure Python functions
to fully emulate behaviors of existing C coded functions.  For example,
the built-in *note divmod(): 945. function does not accept keyword
arguments:

     def divmod(a, b, /):
         "Emulate the built in divmod() function"
         return (a // b, a % b)

Another use case is to preclude keyword arguments when the parameter
name is not helpful.  For example, the builtin *note len(): 5d4.
function has the signature ‘len(obj, /)’.  This precludes awkward calls
such as:

     len(obj='hello')  # The "obj" keyword argument impairs readability

A further benefit of marking a parameter as positional-only is that it
allows the parameter name to be changed in the future without risk of
breaking client code.  For example, in the *note statistics: bd. module,
the parameter name 'dist' may be changed in the future.  This was made
possible with the following function specification:

     def quantiles(dist, /, *, n=4, method='exclusive')
         ...

Since the parameters to the left of ‘/’ are not exposed as possible
keywords, the parameters names remain available for use in ‘**kwargs’:

     >>> def f(a, b, /, **kwargs):
     ...     print(a, b, kwargs)
     ...
     >>> f(10, 20, a=1, b=2, c=3)         # a and b are used in two ways
     10 20 {'a': 1, 'b': 2, 'c': 3}

This greatly simplifies the implementation of functions and methods that
need to accept arbitrary keyword arguments.  For example, here is an
excerpt from code in the *note collections: 16. module:

     class Counter(dict):

         def __init__(self, iterable=None, /, **kwds):
             # Note "iterable" is a possible keyword argument

完整敘述請見 PEP 570(2)。

（由 Pablo Galindo 在 bpo-36540(3) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://devguide.python.org/development-tools/clinic/

   (2) https://peps.python.org/pep-0570/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=36540


File: python.info,  Node: Parallel filesystem cache for compiled bytecode files,  Next: Debug build uses the same ABI as release build,  Prev: Positional-only parameters,  Up: New Features<5>

1.6.2.3 Parallel filesystem cache for compiled bytecode files
.............................................................

The new *note PYTHONPYCACHEPREFIX: 947. setting (also available as *note
-X: 15a. ‘pycache_prefix’) configures the implicit bytecode cache to use
a separate parallel filesystem tree, rather than the default
‘__pycache__’ subdirectories within each source directory.

The location of the cache is reported in *note sys.pycache_prefix: 948.
(*note None: 61b. indicates the default location in ‘__pycache__’
subdirectories).

（由 Carl Meyer 在 bpo-33499(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33499


File: python.info,  Node: Debug build uses the same ABI as release build,  Next: f-strings support = for self-documenting expressions and debugging,  Prev: Parallel filesystem cache for compiled bytecode files,  Up: New Features<5>

1.6.2.4 Debug build uses the same ABI as release build
......................................................

Python now uses the same ABI whether it's built in release or debug
mode.  On Unix, when Python is built in debug mode, it is now possible
to load C extensions built in release mode and C extensions built using
the stable ABI.

Release builds and *note debug builds: 1de. are now ABI compatible:
defining the ‘Py_DEBUG’ macro no longer implies the ‘Py_TRACE_REFS’
macro, which introduces the only ABI incompatibility.  The
‘Py_TRACE_REFS’ macro, which adds the ‘sys.getobjects()’ function and
the *note PYTHONDUMPREFS: 94a. environment variable, can be set using
the new *note ./configure -with-trace-refs: 317. build option.
(Contributed by Victor Stinner in bpo-36465(1).)

On Unix, C extensions are no longer linked to libpython except on
Android and Cygwin.  It is now possible for a statically linked Python
to load a C extension built using a shared library Python.  (Contributed
by Victor Stinner in bpo-21536(2).)

On Unix, when Python is built in debug mode, import now also looks for C
extensions compiled in release mode and for C extensions compiled with
the stable ABI. (Contributed by Victor Stinner in bpo-36722(3).)

To embed Python into an application, a new ‘--embed’ option must be
passed to ‘python3-config --libs --embed’ to get ‘-lpython3.8’ (link the
application to libpython).  To support both 3.8 and older, try
‘python3-config --libs --embed’ first and fallback to ‘python3-config
--libs’ (without ‘--embed’) if the previous command fails.

Add a pkg-config ‘python-3.8-embed’ module to embed Python into an
application: ‘pkg-config python-3.8-embed --libs’ includes
‘-lpython3.8’.  To support both 3.8 and older, try ‘pkg-config
python-X.Y-embed --libs’ first and fallback to ‘pkg-config python-X.Y
--libs’ (without ‘--embed’) if the previous command fails (replace ‘X.Y’
with the Python version).

On the other hand, ‘pkg-config python3.8 --libs’ no longer contains
‘-lpython3.8’.  C extensions must not be linked to libpython (except on
Android and Cygwin, whose cases are handled by the script); this change
is backward incompatible on purpose.  (Contributed by Victor Stinner in
bpo-36721(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36465

   (2) https://bugs.python.org/issue?@action=redirect&bpo=21536

   (3) https://bugs.python.org/issue?@action=redirect&bpo=36722

   (4) https://bugs.python.org/issue?@action=redirect&bpo=36721


File: python.info,  Node: f-strings support = for self-documenting expressions and debugging,  Next: PEP 578 Python Runtime Audit Hooks,  Prev: Debug build uses the same ABI as release build,  Up: New Features<5>

1.6.2.5 f-strings support ‘=’ for self-documenting expressions and debugging
............................................................................

Added an ‘=’ specifier to *note f-string: 3dc.s.  An f-string such as
‘f'{expr=}'’ will expand to the text of the expression, an equal sign,
then the representation of the evaluated expression.  For example:

     >>> user = 'eric_idle'
     >>> member_since = date(1975, 7, 31)
     >>> f'{user=} {member_since=}'
     "user='eric_idle' member_since=datetime.date(1975, 7, 31)"

The usual *note f-string format specifiers: 94d. allow more control over
how the result of the expression is displayed:

     >>> delta = date.today() - member_since
     >>> f'{user=!s}  {delta.days=:,d}'
     'user=eric_idle  delta.days=16,075'

The ‘=’ specifier will display the whole expression so that calculations
can be shown:

     >>> print(f'{theta=}  {cos(radians(theta))=:.3f}')
     theta=30  cos(radians(theta))=0.866

（由 Eric V. Smith 和 Larry Hastings 在 bpo-36817(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36817


File: python.info,  Node: PEP 578 Python Runtime Audit Hooks,  Next: PEP 587 Python Initialization Configuration,  Prev: f-strings support = for self-documenting expressions and debugging,  Up: New Features<5>

1.6.2.6 PEP 578: Python Runtime Audit Hooks
...........................................

The PEP adds an Audit Hook and Verified Open Hook.  Both are available
from Python and native code, allowing applications and frameworks
written in pure Python code to take advantage of extra notifications,
while also allowing embedders or system administrators to deploy builds
of Python where auditing is always enabled.

完整細節請見 PEP 578(1)。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0578/


File: python.info,  Node: PEP 587 Python Initialization Configuration,  Next: PEP 590 Vectorcall a fast calling protocol for CPython,  Prev: PEP 578 Python Runtime Audit Hooks,  Up: New Features<5>

1.6.2.7 PEP 587: Python Initialization Configuration
....................................................

The PEP 587(1) adds a new C API to configure the Python Initialization
providing finer control on the whole configuration and better error
reporting.

New structures:

   * *note PyConfig: 371.

   * *note PyPreConfig: 950.

   * *note PyStatus: 951.

   * *note PyWideStringList: 952.

New functions:

   * *note PyConfig_Clear(): 953.

   * *note PyConfig_InitIsolatedConfig(): 954.

   * *note PyConfig_InitPythonConfig(): 955.

   * *note PyConfig_Read(): 734.

   * *note PyConfig_SetArgv(): 956.

   * *note PyConfig_SetBytesArgv(): 957.

   * *note PyConfig_SetBytesString(): 958.

   * *note PyConfig_SetString(): 959.

   * *note PyPreConfig_InitIsolatedConfig(): 95a.

   * *note PyPreConfig_InitPythonConfig(): 95b.

   * *note PyStatus_Error(): 95c.

   * *note PyStatus_Exception(): 95d.

   * *note PyStatus_Exit(): 95e.

   * *note PyStatus_IsError(): 95f.

   * *note PyStatus_IsExit(): 960.

   * *note PyStatus_NoMemory(): 961.

   * *note PyStatus_Ok(): 962.

   * *note PyWideStringList_Append(): 963.

   * *note PyWideStringList_Insert(): 964.

   * *note Py_BytesMain(): 965.

   * *note Py_ExitStatusException(): 966.

   * *note Py_InitializeFromConfig(): 390.

   * *note Py_PreInitialize(): 3b6.

   * *note Py_PreInitializeFromArgs(): 967.

   * *note Py_PreInitializeFromBytesArgs(): 968.

   * *note Py_RunMain(): 969.

This PEP also adds ‘_PyRuntimeState.preconfig’ (*note PyPreConfig: 950.
type) and ‘PyInterpreterState.config’ (*note PyConfig: 371. type) fields
to these internal structures.  ‘PyInterpreterState.config’ becomes the
new reference configuration, replacing global configuration variables
and other private variables.

See *note Python Initialization Configuration: 372. for the
documentation.

完整敘述請見 PEP 587(2)。

（由 Victor Stinner 在 bpo-36763(3) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0587/

   (2) https://peps.python.org/pep-0587/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=36763


File: python.info,  Node: PEP 590 Vectorcall a fast calling protocol for CPython,  Next: Pickle protocol 5 with out-of-band data buffers,  Prev: PEP 587 Python Initialization Configuration,  Up: New Features<5>

1.6.2.8 PEP 590: Vectorcall: a fast calling protocol for CPython
................................................................

*note Vectorcall 協定: 4f8. is added to the Python/C API. It is meant to
formalize existing optimizations which were already done for various
classes.  Any *note static type: 723. implementing a callable can use
this protocol.

This is currently provisional.  The aim is to make it fully public in
Python 3.9.

完整敘述請見 PEP 590(1)。

（由 Jeroen Demeyer、Mark Shannon 和 Petr Viktorin 在 bpo-36974(2) 中貢
獻。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0590/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36974


File: python.info,  Node: Pickle protocol 5 with out-of-band data buffers,  Prev: PEP 590 Vectorcall a fast calling protocol for CPython,  Up: New Features<5>

1.6.2.9 Pickle protocol 5 with out-of-band data buffers
.......................................................

When *note pickle: 95. is used to transfer large data between Python
processes in order to take advantage of multi-core or multi-machine
processing, it is important to optimize the transfer by reducing memory
copies, and possibly by applying custom techniques such as
data-dependent compression.

The *note pickle: 95. protocol 5 introduces support for out-of-band
buffers where PEP 3118(1)-compatible data can be transmitted separately
from the main pickle stream, at the discretion of the communication
layer.

完整敘述請見 PEP 574(2)。

（由 Antoine Pitrou 在 bpo-36785(3) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3118/

   (2) https://peps.python.org/pep-0574/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=36785


File: python.info,  Node: 其他語言更動<5>,  Next: 新增模組<3>,  Prev: New Features<5>,  Up: Python 3 8 有什麼新功能

1.6.3 其他語言更動
------------------

   * A *note continue: 96d. statement was illegal in the *note finally:
     96e. clause due to a problem with the implementation.  In Python
     3.8 this restriction was lifted.  (Contributed by Serhiy Storchaka
     in bpo-32489(1).)

   * The *note bool: 40e, *note int: 23c, and *note fractions.Fraction:
     1c7. types now have an *note as_integer_ratio(): 96f. method like
     that found in *note float: 2c8. and *note decimal.Decimal: 27c.
     This minor API extension makes it possible to write ‘numerator,
     denominator = x.as_integer_ratio()’ and have it work across
     multiple numeric types.  (Contributed by Lisa Roach in bpo-33073(2)
     and Raymond Hettinger in bpo-37819(3).)

   * Constructors of *note int: 23c, *note float: 2c8. and *note
     complex: 2c9. will now use the *note __index__(): 6c1. special
     method, if available and the corresponding method *note __int__():
     6c0, *note __float__(): 970. or *note __complex__(): 58d. is not
     available.  (Contributed by Serhiy Storchaka in bpo-20092(4).)

   * Added support of ‘\N{NAME}’ escapes in *note regular expressions:
     a7.:

          >>> notice = 'Copyright © 2019'
          >>> copyright_year_pattern = re.compile(r'\N{copyright sign}\s*(\d{4})')
          >>> int(copyright_year_pattern.search(notice).group(1))
          2019

     （由 Jonathan Eunice 和 Serhiy Storchaka 在 bpo-30688(5) 中貢獻。）

   * Dict and dictviews are now iterable in reversed insertion order
     using *note reversed(): 80a.  (Contributed by Rémi Lapeyre in
     bpo-33462(6).)

   * The syntax allowed for keyword names in function calls was further
     restricted.  In particular, ‘f((keyword)=arg)’ is no longer
     allowed.  It was never intended to permit more than a bare name on
     the left-hand side of a keyword argument assignment term.
     (Contributed by Benjamin Peterson in bpo-34641(7).)

   * Generalized iterable unpacking in *note yield: 971. and *note
     return: 972. statements no longer requires enclosing parentheses.
     This brings the 'yield' and 'return' syntax into better agreement
     with normal assignment syntax:

          >>> def parse(family):
                  lastname, *members = family.split()
                  return lastname.upper(), *members

          >>> parse('simpsons homer marge bart lisa maggie')
          ('SIMPSONS', 'homer', 'marge', 'bart', 'lisa', 'maggie')

     （由 David Cuthbert 和 Jordan Chapman 在 bpo-32117(8) 中貢獻。）

   * When a comma is missed in code such as ‘[(10, 20) (30, 40)]’, the
     compiler displays a *note SyntaxWarning: 40c. with a helpful
     suggestion.  This improves on just having a *note TypeError: 4dd.
     indicating that the first tuple was not callable.  (Contributed by
     Serhiy Storchaka in bpo-15248(9).)

   * Arithmetic operations between subclasses of *note datetime.date:
     1b1. or *note datetime.datetime: 1b0. and *note datetime.timedelta:
     973. objects now return an instance of the subclass, rather than
     the base class.  This also affects the return type of operations
     whose implementation (directly or indirectly) uses *note
     datetime.timedelta: 973. arithmetic, such as *note astimezone():
     974.  (Contributed by Paul Ganssle in bpo-32417(10).)

   * When the Python interpreter is interrupted by Ctrl-C (SIGINT) and
     the resulting *note KeyboardInterrupt: 975. exception is not
     caught, the Python process now exits via a SIGINT signal or with
     the correct exit code such that the calling process can detect that
     it died due to a Ctrl-C. Shells on POSIX and Windows use this to
     properly terminate scripts in interactive sessions.  (Contributed
     by Google via Gregory P. Smith in bpo-1054041(11).)

   * Some advanced styles of programming require updating the *note
     types.CodeType: 2b6. object for an existing function.  Since code
     objects are immutable, a new code object needs to be created, one
     that is modeled on the existing code object.  With 19 parameters,
     this was somewhat tedious.  Now, the new ‘replace()’ method makes
     it possible to create a clone with a few altered parameters.

     Here's an example that alters the *note statistics.mean(): 676.
     function to prevent the 'data' parameter from being used as a
     keyword argument:

          >>> from statistics import mean
          >>> mean(data=[10, 20, 90])
          40
          >>> mean.__code__ = mean.__code__.replace(co_posonlyargcount=1)
          >>> mean(data=[10, 20, 90])
          Traceback (most recent call last):
            ...
          TypeError: mean() got some positional-only arguments passed as keyword arguments: 'data'

     （由 Victor Stinner 在 bpo-37032(12) 中貢獻。）

   * For integers, the three-argument form of the *note pow(): 976.
     function now permits the exponent to be negative in the case where
     the base is relatively prime to the modulus.  It then computes a
     modular inverse to the base when the exponent is ‘-1’, and a
     suitable power of that inverse for other negative exponents.  For
     example, to compute the modular multiplicative inverse(13) of 38
     modulo 137, write:

          >>> pow(38, -1, 137)
          119
          >>> 119 * 38 % 137
          1

     Modular inverses arise in the solution of linear Diophantine
     equations(14).  For example, to find integer solutions for ‘4258𝑥 +
     147𝑦 = 369’, first rewrite as ‘4258𝑥 ≡ 369 (mod 147)’ then solve:

          >>> x = 369 * pow(4258, -1, 147) % 147
          >>> y = (4258 * x - 369) // -147
          >>> 4258 * x + 147 * y
          369

     （由 Mark Dickinson 在 bpo-36027(15) 中貢獻。）

   * Dict comprehensions have been synced-up with dict literals so that
     the key is computed first and the value second:

          >>> # Dict comprehension
          >>> cast = {input('role? '): input('actor? ') for i in range(2)}
          role? King Arthur
          actor? Chapman
          role? Black Knight
          actor? Cleese

          >>> # Dict literal
          >>> cast = {input('role? '): input('actor? ')}
          role? Sir Robin
          actor? Eric Idle

     The guaranteed execution order is helpful with assignment
     expressions because variables assigned in the key expression will
     be available in the value expression:

          >>> names = ['Martin von Löwis', 'Łukasz Langa', 'Walter Dörwald']
          >>> {(n := normalize('NFC', name)).casefold() : n for name in names}
          {'martin von löwis': 'Martin von Löwis',
           'łukasz langa': 'Łukasz Langa',
           'walter dörwald': 'Walter Dörwald'}

     （由 Jörn Heissler 在 bpo-35224(16) 中貢獻。）

   * The *note object.__reduce__(): 977. method can now return a tuple
     from two to six elements long.  Formerly, five was the limit.  The
     new, optional sixth element is a callable with a ‘(obj, state)’
     signature.  This allows the direct control over the state-updating
     behavior of a specific object.  If not 'None', this callable will
     have priority over the object's ‘__setstate__()’ method.
     (Contributed by Pierre Glaser and Olivier Grisel in bpo-35900(17).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32489

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33073

   (3) https://bugs.python.org/issue?@action=redirect&bpo=37819

   (4) https://bugs.python.org/issue?@action=redirect&bpo=20092

   (5) https://bugs.python.org/issue?@action=redirect&bpo=30688

   (6) https://bugs.python.org/issue?@action=redirect&bpo=33462

   (7) https://bugs.python.org/issue?@action=redirect&bpo=34641

   (8) https://bugs.python.org/issue?@action=redirect&bpo=32117

   (9) https://bugs.python.org/issue?@action=redirect&bpo=15248

   (10) https://bugs.python.org/issue?@action=redirect&bpo=32417

   (11) https://bugs.python.org/issue?@action=redirect&bpo=1054041

   (12) https://bugs.python.org/issue?@action=redirect&bpo=37032

   (13) https://en.wikipedia.org/wiki/Modular_multiplicative_inverse

   (14) https://en.wikipedia.org/wiki/Diophantine_equation

   (15) https://bugs.python.org/issue?@action=redirect&bpo=36027

   (16) https://bugs.python.org/issue?@action=redirect&bpo=35224

   (17) https://bugs.python.org/issue?@action=redirect&bpo=35900


File: python.info,  Node: 新增模組<3>,  Next: 改進的模組<5>,  Prev: 其他語言更動<5>,  Up: Python 3 8 有什麼新功能

1.6.4 新增模組
--------------

   * The new *note importlib.metadata: 6e. module provides (provisional)
     support for reading metadata from third-party packages.  For
     example, it can extract an installed package's version number, list
     of entry points, and more:

          >>> # Note following example requires that the popular "requests"
          >>> # package has been installed.
          >>>
          >>> from importlib.metadata import version, requires, files
          >>> version('requests')
          '2.22.0'
          >>> list(requires('requests'))
          ['chardet (<3.1.0,>=3.0.2)']
          >>> list(files('requests'))[:5]
          [PackagePath('requests-2.22.0.dist-info/INSTALLER'),
           PackagePath('requests-2.22.0.dist-info/LICENSE'),
           PackagePath('requests-2.22.0.dist-info/METADATA'),
           PackagePath('requests-2.22.0.dist-info/RECORD'),
           PackagePath('requests-2.22.0.dist-info/WHEEL')]

     （由 Barry Warsaw 和 Jason R. Coombs 在 bpo-34632(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=34632


File: python.info,  Node: 改進的模組<5>,  Next: 最佳化<5>,  Prev: 新增模組<3>,  Up: Python 3 8 有什麼新功能

1.6.5 改進的模組
----------------

* Menu:

* ast: ast<3>.
* asyncio: asyncio<6>.
* builtins（內建）::
* collections::
* cProfile::
* csv: csv<2>.
* curses: curses<3>.
* ctypes::
* datetime: datetime<3>.
* functools: functools<2>.
* gc: gc<4>.
* gettext::
* gzip: gzip<3>.
* IDLE and idlelib: IDLE and idlelib<2>.
* inspect: inspect<5>.
* io: io<3>.
* itertools: itertools<4>.
* json.tool: json tool.
* logging: logging<2>.
* math: math<5>.
* mmap: mmap<2>.
* multiprocessing: multiprocessing<3>.
* os: os<6>.
* os.path: os path<4>.
* pathlib: pathlib<7>.
* pickle::
* plistlib::
* pprint: pprint<3>.
* py_compile: py_compile<2>.
* shlex::
* shutil: shutil<4>.
* socket: socket<4>.
* ssl: ssl<4>.
* statistics: statistics<4>.
* sys: sys<6>.
* tarfile: tarfile<4>.
* threading: threading<4>.
* tokenize: tokenize<2>.
* tkinter: tkinter<4>.
* time: time<4>.
* typing: typing<8>.
* unicodedata: unicodedata<5>.
* unittest: unittest<6>.
* venv: venv<4>.
* weakref::
* xml: xml<4>.
* xmlrpc::


File: python.info,  Node: ast<3>,  Next: asyncio<6>,  Up: 改進的模組<5>

1.6.5.1 ast
...........

AST nodes now have ‘end_lineno’ and ‘end_col_offset’ attributes, which
give the precise location of the end of the node.  (This only applies to
nodes that have ‘lineno’ and ‘col_offset’ attributes.)

New function *note ast.get_source_segment(): 97b. returns the source
code for a specific AST node.

（由 Ivan Levkivskyi 在 bpo-33416(1) 中貢獻。）

The *note ast.parse(): 18e. function has some new flags:

   * ‘type_comments=True’ causes it to return the text of PEP 484(2) and
     PEP 526(3) type comments associated with certain AST nodes;

   * ‘mode='func_type'’ can be used to parse PEP 484(4) "signature type
     comments" (returned for function definition AST nodes);

   * ‘feature_version=(3, N)’ allows specifying an earlier Python 3
     version.  For example, ‘feature_version=(3, 4)’ will treat *note
     async: 6d6. and *note await: 19f. as non-reserved words.

（由 Guido van Rossum 在 bpo-35766(5) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33416

   (2) https://peps.python.org/pep-0484/

   (3) https://peps.python.org/pep-0526/

   (4) https://peps.python.org/pep-0484/

   (5) https://bugs.python.org/issue?@action=redirect&bpo=35766


File: python.info,  Node: asyncio<6>,  Next: builtins（內建）,  Prev: ast<3>,  Up: 改進的模組<5>

1.6.5.2 asyncio
...............

*note asyncio.run(): 423. has graduated from the provisional to stable
API. This function can be used to execute a *note coroutine: 438. and
return the result while automatically managing the event loop.  For
example:

     import asyncio

     async def main():
         await asyncio.sleep(0)
         return 42

     asyncio.run(main())

這'大致'等價於：

     import asyncio

     async def main():
         await asyncio.sleep(0)
         return 42

     loop = asyncio.new_event_loop()
     asyncio.set_event_loop(loop)
     try:
         loop.run_until_complete(main())
     finally:
         asyncio.set_event_loop(None)
         loop.close()

The actual implementation is significantly more complex.  Thus, *note
asyncio.run(): 423. should be the preferred way of running asyncio
programs.

（由 Yury Selivanov 在 bpo-32314(1) 中貢獻。）

Running ‘python -m asyncio’ launches a natively async REPL. This allows
rapid experimentation with code that has a top-level *note await: 19f.
There is no longer a need to directly call ‘asyncio.run()’ which would
spawn a new event loop on every invocation:

     $ python -m asyncio
     asyncio REPL 3.8.0
     Use "await" directly instead of "asyncio.run()".
     Type "help", "copyright", "credits" or "license" for more information.
     >>> import asyncio
     >>> await asyncio.sleep(10, result='hello')
     hello

（由 Yury Selivanov 在 bpo-37028(2) 中貢獻。）

The exception *note asyncio.CancelledError: 19e. now inherits from *note
BaseException: 55f. rather than *note Exception: 97d. and no longer
inherits from *note concurrent.futures.CancelledError: 97e.
(Contributed by Yury Selivanov in bpo-32528(3).)

On Windows, the default event loop is now *note ProactorEventLoop: 5ae.
(Contributed by Victor Stinner in bpo-34687(4).)

*note ProactorEventLoop: 5ae. now also supports UDP. (Contributed by
Adam Meily and Andrew Svetlov in bpo-29883(5).)

*note ProactorEventLoop: 5ae. can now be interrupted by *note
KeyboardInterrupt: 975. ("CTRL+C"). (Contributed by Vladimir Matveev in
bpo-23057(6).)

Added *note asyncio.Task.get_coro(): 97f. for getting the wrapped
coroutine within an *note asyncio.Task: 480.  (Contributed by Alex
Grönholm in bpo-36999(7).)

Asyncio tasks can now be named, either by passing the ‘name’ keyword
argument to *note asyncio.create_task(): 5a1. or the *note
create_task(): 980. event loop method, or by calling the *note
set_name(): 981. method on the task object.  The task name is visible in
the ‘repr()’ output of *note asyncio.Task: 480. and can also be
retrieved using the *note get_name(): 982. method.  (Contributed by Alex
Grönholm in bpo-34270(8).)

Added support for Happy Eyeballs(9) to *note
asyncio.loop.create_connection(): 5a8.  To specify the behavior, two new
parameters have been added: 'happy_eyeballs_delay' and 'interleave'.
The Happy Eyeballs algorithm improves responsiveness in applications
that support IPv4 and IPv6 by attempting to simultaneously connect using
both.  (Contributed by twisteroid ambassador in bpo-33530(10).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32314

   (2) https://bugs.python.org/issue?@action=redirect&bpo=37028

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32528

   (4) https://bugs.python.org/issue?@action=redirect&bpo=34687

   (5) https://bugs.python.org/issue?@action=redirect&bpo=29883

   (6) https://bugs.python.org/issue?@action=redirect&bpo=23057

   (7) https://bugs.python.org/issue?@action=redirect&bpo=36999

   (8) https://bugs.python.org/issue?@action=redirect&bpo=34270

   (9) https://en.wikipedia.org/wiki/Happy_Eyeballs

   (10) https://bugs.python.org/issue?@action=redirect&bpo=33530


File: python.info,  Node: builtins（內建）,  Next: collections,  Prev: asyncio<6>,  Up: 改進的模組<5>

1.6.5.3 builtins（內建）
........................

The *note compile(): 178. built-in has been improved to accept the
‘ast.PyCF_ALLOW_TOP_LEVEL_AWAIT’ flag.  With this new flag passed, *note
compile(): 178. will allow top-level ‘await’, ‘async for’ and ‘async
with’ constructs that are usually considered invalid syntax.
Asynchronous code object marked with the ‘CO_COROUTINE’ flag may then be
returned.  (Contributed by Matthias Bussonnier in bpo-34616(1))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=34616


File: python.info,  Node: collections,  Next: cProfile,  Prev: builtins（內建）,  Up: 改進的模組<5>

1.6.5.4 collections
...................

The *note _asdict(): 985. method for *note collections.namedtuple():
1ae. now returns a *note dict: 23b. instead of a *note
collections.OrderedDict: 57f.  This works because regular dicts have
guaranteed ordering since Python 3.7.  If the extra features of
‘OrderedDict’ are required, the suggested remediation is to cast the
result to the desired type: ‘OrderedDict(nt._asdict())’.  (Contributed
by Raymond Hettinger in bpo-35864(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35864


File: python.info,  Node: cProfile,  Next: csv<2>,  Prev: collections,  Up: 改進的模組<5>

1.6.5.5 cProfile
................

The *note cProfile.Profile: 987. class can now be used as a context
manager.  Profile a block of code by running:

     import cProfile

     with cProfile.Profile() as profiler:
           # code to be profiled
           ...

（由 Scott Sanderson 在 bpo-29235(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29235


File: python.info,  Node: csv<2>,  Next: curses<3>,  Prev: cProfile,  Up: 改進的模組<5>

1.6.5.6 csv
...........

The *note csv.DictReader: 989. now returns instances of *note dict: 23b.
instead of a *note collections.OrderedDict: 57f.  The tool is now faster
and uses less memory while still preserving the field order.
(Contributed by Michael Selik in bpo-34003(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=34003


File: python.info,  Node: curses<3>,  Next: ctypes,  Prev: csv<2>,  Up: 改進的模組<5>

1.6.5.7 curses
..............

Added a new variable holding structured version information for the
underlying ncurses library: *note ncurses_version: 98b.  (Contributed by
Serhiy Storchaka in bpo-31680(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31680


File: python.info,  Node: ctypes,  Next: datetime<3>,  Prev: curses<3>,  Up: 改進的模組<5>

1.6.5.8 ctypes
..............

On Windows, *note CDLL: 98d. and subclasses now accept a 'winmode'
parameter to specify flags for the underlying ‘LoadLibraryEx’ call.  The
default flags are set to only load DLL dependencies from trusted
locations, including the path where the DLL is stored (if a full or
partial path is used to load the initial DLL) and paths added by *note
add_dll_directory(): 98e.  (Contributed by Steve Dower in bpo-36085(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36085


File: python.info,  Node: datetime<3>,  Next: functools<2>,  Prev: ctypes,  Up: 改進的模組<5>

1.6.5.9 datetime
................

Added new alternate constructors *note datetime.date.fromisocalendar():
990. and *note datetime.datetime.fromisocalendar(): 991, which construct
*note date: 1b1. and *note datetime: 1b0. objects respectively from ISO
year, week number, and weekday; these are the inverse of each class's
‘isocalendar’ method.  (Contributed by Paul Ganssle in bpo-36004(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36004


File: python.info,  Node: functools<2>,  Next: gc<4>,  Prev: datetime<3>,  Up: 改進的模組<5>

1.6.5.10 functools
..................

*note functools.lru_cache(): 993. can now be used as a straight
decorator rather than as a function returning a decorator.  So both of
these are now supported:

     @lru_cache
     def f(x):
         ...

     @lru_cache(maxsize=256)
     def f(x):
         ...

（由 Raymond Hettinger 在 bpo-36772(1) 中貢獻。）

Added a new *note functools.cached_property(): 4e7. decorator, for
computed properties cached for the life of the instance.

     import functools
     import statistics

     class Dataset:
        def __init__(self, sequence_of_numbers):
           self.data = sequence_of_numbers

        @functools.cached_property
        def variance(self):
           return statistics.variance(self.data)

（由 Carl Meyer 在 bpo-21145(2) 中貢獻）

Added a new *note functools.singledispatchmethod(): 994. decorator that
converts methods into *note generic functions: 995. using *note single
dispatch: 996.:

     from functools import singledispatchmethod
     from contextlib import suppress

     class TaskManager:

         def __init__(self, tasks):
             self.tasks = list(tasks)

         @singledispatchmethod
         def discard(self, value):
             with suppress(ValueError):
                 self.tasks.remove(value)

         @discard.register(list)
         def _(self, tasks):
             targets = set(tasks)
             self.tasks = [x for x in self.tasks if x not in targets]

（由 Ethan Smith 在 bpo-32380(3) 中貢獻）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36772

   (2) https://bugs.python.org/issue?@action=redirect&bpo=21145

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32380


File: python.info,  Node: gc<4>,  Next: gettext,  Prev: functools<2>,  Up: 改進的模組<5>

1.6.5.11 gc
...........

*note get_objects(): 7a7. can now receive an optional 'generation'
parameter indicating a generation to get objects from.  (Contributed by
Pablo Galindo in bpo-36016(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36016


File: python.info,  Node: gettext,  Next: gzip<3>,  Prev: gc<4>,  Up: 改進的模組<5>

1.6.5.12 gettext
................

Added *note pgettext(): 999. and its variants.  (Contributed by Franz
Glasner, Éric Araujo, and Cheryl Sabella in bpo-2504(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=2504


File: python.info,  Node: gzip<3>,  Next: IDLE and idlelib<2>,  Prev: gettext,  Up: 改進的模組<5>

1.6.5.13 gzip
.............

Added the 'mtime' parameter to *note gzip.compress(): 5e4. for
reproducible output.  (Contributed by Guo Ci Teo in bpo-34898(1).)

A *note BadGzipFile: 99b. exception is now raised instead of *note
OSError: 350. for certain types of invalid or corrupt gzip files.
(Contributed by Filip Gruszczyński, Michele Orrù, and Zackery Spytz in
bpo-6584(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=34898

   (2) https://bugs.python.org/issue?@action=redirect&bpo=6584


File: python.info,  Node: IDLE and idlelib<2>,  Next: inspect<5>,  Prev: gzip<3>,  Up: 改進的模組<5>

1.6.5.14 IDLE and idlelib
.........................

Output over N lines (50 by default) is squeezed down to a button.  N can
be changed in the PyShell section of the General page of the Settings
dialog.  Fewer, but possibly extra long, lines can be squeezed by right
clicking on the output.  Squeezed output can be expanded in place by
double-clicking the button or into the clipboard or a separate window by
right-clicking the button.  (Contributed by Tal Einat in
bpo-1529353(1).)

Add "Run Customized" to the Run menu to run a module with customized
settings.  Any command line arguments entered are added to sys.argv.
They also re-appear in the box for the next customized run.  One can
also suppress the normal Shell main module restart.  (Contributed by
Cheryl Sabella, Terry Jan Reedy, and others in bpo-5680(2) and
bpo-37627(3).)

Added optional line numbers for IDLE editor windows.  Windows open
without line numbers unless set otherwise in the General tab of the
configuration dialog.  Line numbers for an existing window are shown and
hidden in the Options menu.  (Contributed by Tal Einat and Saimadhav
Heblikar in bpo-17535(4).)

OS native encoding is now used for converting between Python strings and
Tcl objects.  This allows IDLE to work with emoji and other non-BMP
characters.  These characters can be displayed or copied and pasted to
or from the clipboard.  Converting strings from Tcl to Python and back
now never fails.  (Many people worked on this for eight years but the
problem was finally solved by Serhiy Storchaka in bpo-13153(5).)

New in 3.8.1:

Add option to toggle cursor blink off.  (Contributed by Zackery Spytz in
bpo-4603(6).)

Escape key now closes IDLE completion windows.  (Contributed by Johnny
Najera in bpo-38944(7).)

The changes above have been backported to 3.7 maintenance releases.

Add keywords to module name completion list.  (Contributed by Terry J.
Reedy in bpo-37765(8).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1529353

   (2) https://bugs.python.org/issue?@action=redirect&bpo=5680

   (3) https://bugs.python.org/issue?@action=redirect&bpo=37627

   (4) https://bugs.python.org/issue?@action=redirect&bpo=17535

   (5) https://bugs.python.org/issue?@action=redirect&bpo=13153

   (6) https://bugs.python.org/issue?@action=redirect&bpo=4603

   (7) https://bugs.python.org/issue?@action=redirect&bpo=38944

   (8) https://bugs.python.org/issue?@action=redirect&bpo=37765


File: python.info,  Node: inspect<5>,  Next: io<3>,  Prev: IDLE and idlelib<2>,  Up: 改進的模組<5>

1.6.5.15 inspect
................

The *note inspect.getdoc(): 99e. function can now find docstrings for
‘__slots__’ if that attribute is a *note dict: 23b. where the values are
docstrings.  This provides documentation options similar to what we
already have for *note property(): 180, *note classmethod(): 14a, and
*note staticmethod(): 358.:

     class AudioClip:
         __slots__ = {'bit_rate': 'expressed in kilohertz to one decimal place',
                      'duration': 'in seconds, rounded up to an integer'}
         def __init__(self, bit_rate, duration):
             self.bit_rate = round(bit_rate / 1000.0, 1)
             self.duration = ceil(duration)

（由 Raymond Hettinger 在 bpo-36326(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36326


File: python.info,  Node: io<3>,  Next: itertools<4>,  Prev: inspect<5>,  Up: 改進的模組<5>

1.6.5.16 io
...........

In development mode (*note -X: 15a. ‘env’) and in *note debug build:
1de, the *note io.IOBase: 1da. finalizer now logs the exception if the
‘close()’ method fails.  The exception is ignored silently by default in
release build.  (Contributed by Victor Stinner in bpo-18748(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=18748


File: python.info,  Node: itertools<4>,  Next: json tool,  Prev: io<3>,  Up: 改進的模組<5>

1.6.5.17 itertools
..................

The *note itertools.accumulate(): 9a1. function added an option
'initial' keyword argument to specify an initial value:

     >>> from itertools import accumulate
     >>> list(accumulate([10, 5, 30, 15], initial=1000))
     [1000, 1010, 1015, 1045, 1060]

（由 Lisa Roach 在 bpo-34659(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=34659


File: python.info,  Node: json tool,  Next: logging<2>,  Prev: itertools<4>,  Up: 改進的模組<5>

1.6.5.18 json.tool
..................

Add option ‘--json-lines’ to parse every input line as a separate JSON
object.  (Contributed by Weipeng Hong in bpo-31553(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31553


File: python.info,  Node: logging<2>,  Next: math<5>,  Prev: json tool,  Up: 改進的模組<5>

1.6.5.19 logging
................

Added a 'force' keyword argument to *note logging.basicConfig(): 9a4.
When set to true, any existing handlers attached to the root logger are
removed and closed before carrying out the configuration specified by
the other arguments.

This solves a long-standing problem.  Once a logger or 'basicConfig()'
had been called, subsequent calls to 'basicConfig()' were silently
ignored.  This made it difficult to update, experiment with, or teach
the various logging configuration options using the interactive prompt
or a Jupyter notebook.

(Suggested by Raymond Hettinger, implemented by Donghee Na, and reviewed
by Vinay Sajip in bpo-33897(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33897


File: python.info,  Node: math<5>,  Next: mmap<2>,  Prev: logging<2>,  Up: 改進的模組<5>

1.6.5.20 math
.............

Added new function *note math.dist(): 9a6. for computing Euclidean
distance between two points.  (Contributed by Raymond Hettinger in
bpo-33089(1).)

Expanded the *note math.hypot(): 9a7. function to handle multiple
dimensions.  Formerly, it only supported the 2-D case.  (Contributed by
Raymond Hettinger in bpo-33089(2).)

Added new function, *note math.prod(): 9a8, as analogous function to
*note sum(): 411. that returns the product of a 'start' value (default:
1) times an iterable of numbers:

     >>> prior = 0.8
     >>> likelihoods = [0.625, 0.84, 0.30]
     >>> math.prod(likelihoods, start=prior)
     0.126

（由 Pablo Galindo 在 bpo-35606(3) 中貢獻。）

Added two new combinatoric functions *note math.perm(): 675. and *note
math.comb(): 674.:

     >>> math.perm(10, 3)    # Permutations of 10 things taken 3 at a time
     720
     >>> math.comb(10, 3)    # Combinations of 10 things taken 3 at a time
     120

（由 Yash Aggarwal、Keller Fuchs、Serhiy Storchaka 和 Raymond Hettinger
在 bpo-37128(4)、bpo-37178(5) 和 bpo-35431(6) 中貢獻。）

Added a new function *note math.isqrt(): 9a9. for computing accurate
integer square roots without conversion to floating point.  The new
function supports arbitrarily large integers.  It is faster than
‘floor(sqrt(n))’ but slower than *note math.sqrt(): 9aa.:

     >>> r = 650320427
     >>> s = r ** 2
     >>> isqrt(s - 1)         # correct
     650320426
     >>> floor(sqrt(s - 1))   # incorrect
     650320427

（由 Mark Dickinson 在 bpo-36887(7) 中貢獻。）

The function *note math.factorial(): 8eb. no longer accepts arguments
that are not int-like.  (Contributed by Pablo Galindo in bpo-33083(8).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33089

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33089

   (3) https://bugs.python.org/issue?@action=redirect&bpo=35606

   (4) https://bugs.python.org/issue?@action=redirect&bpo=37128

   (5) https://bugs.python.org/issue?@action=redirect&bpo=37178

   (6) https://bugs.python.org/issue?@action=redirect&bpo=35431

   (7) https://bugs.python.org/issue?@action=redirect&bpo=36887

   (8) https://bugs.python.org/issue?@action=redirect&bpo=33083


File: python.info,  Node: mmap<2>,  Next: multiprocessing<3>,  Prev: math<5>,  Up: 改進的模組<5>

1.6.5.21 mmap
.............

The *note mmap.mmap: 1f0. class now has an *note madvise(): 9ac. method
to access the ‘madvise()’ system call.  (Contributed by Zackery Spytz in
bpo-32941(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32941


File: python.info,  Node: multiprocessing<3>,  Next: os<6>,  Prev: mmap<2>,  Up: 改進的模組<5>

1.6.5.22 multiprocessing
........................

Added new *note multiprocessing.shared_memory: 8b. module.  (Contributed
by Davin Potts in bpo-35813(1).)

On macOS, the 'spawn' start method is now used by default.  (Contributed
by Victor Stinner in bpo-33725(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35813

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33725


File: python.info,  Node: os<6>,  Next: os path<4>,  Prev: multiprocessing<3>,  Up: 改進的模組<5>

1.6.5.23 os
...........

Added new function *note add_dll_directory(): 98e. on Windows for
providing additional search paths for native dependencies when importing
extension modules or loading DLLs using *note ctypes: 22.  (Contributed
by Steve Dower in bpo-36085(1).)

A new *note os.memfd_create(): 9af. function was added to wrap the
‘memfd_create()’ syscall.  (Contributed by Zackery Spytz and Christian
Heimes in bpo-26836(2).)

On Windows, much of the manual logic for handling reparse points
(including symlinks and directory junctions) has been delegated to the
operating system.  Specifically, *note os.stat(): 448. will now traverse
anything supported by the operating system, while *note os.lstat(): 449.
will only open reparse points that identify as "name surrogates" while
others are opened as for *note os.stat(): 448.  In all cases,
‘stat_result.st_mode’ will only have ‘S_IFLNK’ set for symbolic links
and not other kinds of reparse points.  To identify other kinds of
reparse point, check the new ‘stat_result.st_reparse_tag’ attribute.

On Windows, *note os.readlink(): 8c5. is now able to read directory
junctions.  Note that *note islink(): 9b0. will return ‘False’ for
directory junctions, and so code that checks ‘islink’ first will
continue to treat junctions as directories, while code that handles
errors from *note os.readlink(): 8c5. may now treat junctions as links.

（由 Steve Dower 在 bpo-37834(3) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36085

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26836

   (3) https://bugs.python.org/issue?@action=redirect&bpo=37834


File: python.info,  Node: os path<4>,  Next: pathlib<7>,  Prev: os<6>,  Up: 改進的模組<5>

1.6.5.24 os.path
................

*note os.path: 92. functions that return a boolean result like *note
exists(): 9b2, *note lexists(): 9b3, *note isdir(): 9b4, *note isfile():
9b5, *note islink(): 9b0, and *note ismount(): 9b6. now return ‘False’
instead of raising *note ValueError: 1e7. or its subclasses *note
UnicodeEncodeError: 61d. and *note UnicodeDecodeError: 9b7. for paths
that contain characters or bytes unrepresentable at the OS level.
(Contributed by Serhiy Storchaka in bpo-33721(1).)

*note expanduser(): 9b8. on Windows now prefers the ‘USERPROFILE’
environment variable and does not use ‘HOME’, which is not normally set
for regular user accounts.  (Contributed by Anthony Sottile in
bpo-36264(2).)

*note isdir(): 9b4. on Windows no longer returns ‘True’ for a link to a
non-existent directory.

*note realpath(): 20a. on Windows now resolves reparse points, including
symlinks and directory junctions.

（由 Steve Dower 在 bpo-37834(3) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33721

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36264

   (3) https://bugs.python.org/issue?@action=redirect&bpo=37834


File: python.info,  Node: pathlib<7>,  Next: pickle,  Prev: os path<4>,  Up: 改進的模組<5>

1.6.5.25 pathlib
................

*note pathlib.Path: 20e. methods that return a boolean result like *note
exists(): 9ba, *note is_dir(): 215, *note is_file(): 214, *note
is_mount(): 9bb, *note is_symlink(): 9bc, *note is_block_device(): 9bd,
*note is_char_device(): 9be, *note is_fifo(): 9bf, *note is_socket():
9c0. now return ‘False’ instead of raising *note ValueError: 1e7. or its
subclass *note UnicodeEncodeError: 61d. for paths that contain
characters unrepresentable at the OS level.  (Contributed by Serhiy
Storchaka in bpo-33721(1).)

Added ‘pathlib.Path.link_to()’ which creates a hard link pointing to a
path.  (Contributed by Joannah Nanjekye in bpo-26978(2)) Note that
‘link_to’ was deprecated in 3.10 and removed in 3.12 in favor of a
‘hardlink_to’ method added in 3.10 which matches the semantics of the
existing ‘symlink_to’ method.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33721

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26978


File: python.info,  Node: pickle,  Next: plistlib,  Prev: pathlib<7>,  Up: 改進的模組<5>

1.6.5.26 pickle
...............

*note pickle: 95. extensions subclassing the C-optimized *note Pickler:
9c2. can now override the pickling logic of functions and classes by
defining the special *note reducer_override(): 9c3. method.
(Contributed by Pierre Glaser and Olivier Grisel in bpo-35900(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35900


File: python.info,  Node: plistlib,  Next: pprint<3>,  Prev: pickle,  Up: 改進的模組<5>

1.6.5.27 plistlib
.................

Added new *note plistlib.UID: 9c5. and enabled support for reading and
writing NSKeyedArchiver-encoded binary plists.  (Contributed by Jon
Janzen in bpo-26707(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26707


File: python.info,  Node: pprint<3>,  Next: py_compile<2>,  Prev: plistlib,  Up: 改進的模組<5>

1.6.5.28 pprint
...............

The *note pprint: 9c. module added a 'sort_dicts' parameter to several
functions.  By default, those functions continue to sort dictionaries
before rendering or printing.  However, if 'sort_dicts' is set to false,
the dictionaries retain the order that keys were inserted.  This can be
useful for comparison to JSON inputs during debugging.

In addition, there is a convenience new function, *note pprint.pp():
9c7. that is like *note pprint.pprint(): 7cc. but with 'sort_dicts'
defaulting to ‘False’:

     >>> from pprint import pprint, pp
     >>> d = dict(source='input.txt', operation='filter', destination='output.txt')
     >>> pp(d, width=40)                  # Original order
     {'source': 'input.txt',
      'operation': 'filter',
      'destination': 'output.txt'}
     >>> pprint(d, width=40)              # Keys sorted alphabetically
     {'destination': 'output.txt',
      'operation': 'filter',
      'source': 'input.txt'}

（由 Rémi Lapeyre 在 bpo-30670(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30670


File: python.info,  Node: py_compile<2>,  Next: shlex,  Prev: pprint<3>,  Up: 改進的模組<5>

1.6.5.29 py_compile
...................

*note py_compile.compile(): 9c9. now supports silent mode.  (Contributed
by Joannah Nanjekye in bpo-22640(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22640


File: python.info,  Node: shlex,  Next: shutil<4>,  Prev: py_compile<2>,  Up: 改進的模組<5>

1.6.5.30 shlex
..............

The new *note shlex.join(): 9cb. function acts as the inverse of *note
shlex.split(): 4e1.  (Contributed by Bo Bayles in bpo-32102(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32102


File: python.info,  Node: shutil<4>,  Next: socket<4>,  Prev: shlex,  Up: 改進的模組<5>

1.6.5.31 shutil
...............

*note shutil.copytree(): 9cd. now accepts a new ‘dirs_exist_ok’ keyword
argument.  (Contributed by Josh Bronson in bpo-20849(1).)

*note shutil.make_archive(): 45a. now defaults to the modern pax
(POSIX.1-2001) format for new archives to improve portability and
standards conformance, inherited from the corresponding change to the
*note tarfile: c8. module.  (Contributed by C.A.M. Gerlach in
bpo-30661(2).)

*note shutil.rmtree(): 2d2. on Windows now removes directory junctions
without recursively removing their contents first.  (Contributed by
Steve Dower in bpo-37834(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=20849

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30661

   (3) https://bugs.python.org/issue?@action=redirect&bpo=37834


File: python.info,  Node: socket<4>,  Next: ssl<4>,  Prev: shutil<4>,  Up: 改進的模組<5>

1.6.5.32 socket
...............

Added *note create_server(): 9cf. and *note has_dualstack_ipv6(): 9d0.
convenience functions to automate the necessary tasks usually involved
when creating a server socket, including accepting both IPv4 and IPv6
connections on the same socket.  (Contributed by Giampaolo Rodolà in
bpo-17561(1).)

The *note socket.if_nameindex(): 9d1, *note socket.if_nametoindex():
9d2, and *note socket.if_indextoname(): 9d3. functions have been
implemented on Windows.  (Contributed by Zackery Spytz in bpo-37007(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=17561

   (2) https://bugs.python.org/issue?@action=redirect&bpo=37007


File: python.info,  Node: ssl<4>,  Next: statistics<4>,  Prev: socket<4>,  Up: 改進的模組<5>

1.6.5.33 ssl
............

Added *note post_handshake_auth: 9d5. to enable and *note
verify_client_post_handshake(): 9d6. to initiate TLS 1.3 post-handshake
authentication.  (Contributed by Christian Heimes in bpo-34670(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=34670


File: python.info,  Node: statistics<4>,  Next: sys<6>,  Prev: ssl<4>,  Up: 改進的模組<5>

1.6.5.34 statistics
...................

Added *note statistics.fmean(): 9d8. as a faster, floating-point variant
of *note statistics.mean(): 676.  (Contributed by Raymond Hettinger and
Steven D'Aprano in bpo-35904(1).)

新增 *note statistics.geometric_mean(): 9d9.（由 Raymond Hettinger 在
bpo-27181(2) 中貢獻。）

Added *note statistics.multimode(): 9da. that returns a list of the most
common values.  (Contributed by Raymond Hettinger in bpo-35892(3).)

Added *note statistics.quantiles(): 9db. that divides data or a
distribution in to equiprobable intervals (e.g.  quartiles, deciles, or
percentiles).  (Contributed by Raymond Hettinger in bpo-36546(4).)

Added *note statistics.NormalDist: 9dc, a tool for creating and
manipulating normal distributions of a random variable.  (Contributed by
Raymond Hettinger in bpo-36018(5).)

     >>> temperature_feb = NormalDist.from_samples([4, 12, -3, 2, 7, 14])
     >>> temperature_feb.mean
     6.0
     >>> temperature_feb.stdev
     6.356099432828281

     >>> temperature_feb.cdf(3)            # Chance of being under 3 degrees
     0.3184678262814532
     >>> # Relative chance of being 7 degrees versus 10 degrees
     >>> temperature_feb.pdf(7) / temperature_feb.pdf(10)
     1.2039930378537762

     >>> el_niño = NormalDist(4, 2.5)
     >>> temperature_feb += el_niño        # Add in a climate effect
     >>> temperature_feb
     NormalDist(mu=10.0, sigma=6.830080526611674)

     >>> temperature_feb * (9/5) + 32      # Convert to Fahrenheit
     NormalDist(mu=50.0, sigma=12.294144947901014)
     >>> temperature_feb.samples(3)        # Generate random samples
     [7.672102882379219, 12.000027119750287, 4.647488369766392]

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35904

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27181

   (3) https://bugs.python.org/issue?@action=redirect&bpo=35892

   (4) https://bugs.python.org/issue?@action=redirect&bpo=36546

   (5) https://bugs.python.org/issue?@action=redirect&bpo=36018


File: python.info,  Node: sys<6>,  Next: tarfile<4>,  Prev: statistics<4>,  Up: 改進的模組<5>

1.6.5.35 sys
............

Add new *note sys.unraisablehook(): 1dc. function which can be
overridden to control how "unraisable exceptions" are handled.  It is
called when an exception has occurred but there is no way for Python to
handle it.  For example, when a destructor raises an exception or during
garbage collection (*note gc.collect(): 16b.).  (Contributed by Victor
Stinner in bpo-36829(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36829


File: python.info,  Node: tarfile<4>,  Next: threading<4>,  Prev: sys<6>,  Up: 改進的模組<5>

1.6.5.36 tarfile
................

The *note tarfile: c8. module now defaults to the modern pax
(POSIX.1-2001) format for new archives, instead of the previous
GNU-specific one.  This improves cross-platform portability with a
consistent encoding (UTF-8) in a standardized and extensible format, and
offers several other benefits.  (Contributed by C.A.M. Gerlach in
bpo-36268(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36268


File: python.info,  Node: threading<4>,  Next: tokenize<2>,  Prev: tarfile<4>,  Up: 改進的模組<5>

1.6.5.37 threading
..................

Add a new *note threading.excepthook(): 7ef. function which handles
uncaught *note threading.Thread.run(): 9e0. exception.  It can be
overridden to control how uncaught *note threading.Thread.run(): 9e0.
exceptions are handled.  (Contributed by Victor Stinner in
bpo-1230540(1).)

Add a new *note threading.get_native_id(): 9e1. function and a *note
native_id: 9e2. attribute to the *note threading.Thread: 8f0. class.
These return the native integral Thread ID of the current thread
assigned by the kernel.  This feature is only available on certain
platforms, see *note get_native_id: 9e1. for more information.
(Contributed by Jake Tesler in bpo-36084(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1230540

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36084


File: python.info,  Node: tokenize<2>,  Next: tkinter<4>,  Prev: threading<4>,  Up: 改進的模組<5>

1.6.5.38 tokenize
.................

The *note tokenize: e4. module now implicitly emits a ‘NEWLINE’ token
when provided with input that does not have a trailing new line.  This
behavior now matches what the C tokenizer does internally.  (Contributed
by Ammar Askar in bpo-33899(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33899


File: python.info,  Node: tkinter<4>,  Next: time<4>,  Prev: tokenize<2>,  Up: 改進的模組<5>

1.6.5.39 tkinter
................

Added methods ‘selection_from()’, ‘selection_present()’,
‘selection_range()’ and ‘selection_to()’ in the ‘tkinter.Spinbox’ class.
(Contributed by Juliette Monsel in bpo-34829(1).)

Added method ‘moveto()’ in the ‘tkinter.Canvas’ class.  (Contributed by
Juliette Monsel in bpo-23831(2).)

The ‘tkinter.PhotoImage’ class now has ‘transparency_get()’ and
‘transparency_set()’ methods.  (Contributed by Zackery Spytz in
bpo-25451(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=34829

   (2) https://bugs.python.org/issue?@action=redirect&bpo=23831

   (3) https://bugs.python.org/issue?@action=redirect&bpo=25451


File: python.info,  Node: time<4>,  Next: typing<8>,  Prev: tkinter<4>,  Up: 改進的模組<5>

1.6.5.40 time
.............

Added new clock *note CLOCK_UPTIME_RAW: 9e6. for macOS 10.12.
(Contributed by Joannah Nanjekye in bpo-35702(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35702


File: python.info,  Node: typing<8>,  Next: unicodedata<5>,  Prev: time<4>,  Up: 改進的模組<5>

1.6.5.41 typing
...............

The *note typing: ed. module incorporates several new features:

   * A dictionary type with per-key types.  See PEP 589(1) and *note
     typing.TypedDict: 146.  TypedDict uses only string keys.  By
     default, every key is required to be present.  Specify
     "total=False" to allow keys to be optional:

          class Location(TypedDict, total=False):
              lat_long: tuple
              grid_square: str
              xy_coordinate: tuple

   * Literal types.  See PEP 586(2) and *note typing.Literal: 7f9.
     Literal types indicate that a parameter or return value is
     constrained to one or more specific literal values:

          def get_status(port: int) -> Literal['connected', 'disconnected']:
              ...

   * "Final" variables, functions, methods and classes.  See PEP 591(3),
     *note typing.Final: 24c. and *note typing.final(): 652.  The final
     qualifier instructs a static type checker to restrict subclassing,
     overriding, or reassignment:

          pi: Final[float] = 3.1415926536

   * Protocol definitions.  See PEP 544(4), *note typing.Protocol: 249.
     and *note typing.runtime_checkable(): 3e9.  Simple ABCs like *note
     typing.SupportsInt: 9e8. are now ‘Protocol’ subclasses.

   * New protocol class *note typing.SupportsIndex: 9e9.

   * New functions *note typing.get_origin(): 9ea. and *note
     typing.get_args(): 822.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0589/

   (2) https://peps.python.org/pep-0586/

   (3) https://peps.python.org/pep-0591/

   (4) https://peps.python.org/pep-0544/


File: python.info,  Node: unicodedata<5>,  Next: unittest<6>,  Prev: typing<8>,  Up: 改進的模組<5>

1.6.5.42 unicodedata
....................

The *note unicodedata: ee. module has been upgraded to use the Unicode
12.1.0(1) release.

New function *note is_normalized(): 9ec. can be used to verify a string
is in a specific normal form, often much faster than by actually
normalizing the string.  (Contributed by Max Belanger, David Euresti,
and Greg Price in bpo-32285(2) and bpo-37966(3)).

   ---------- Footnotes ----------

   (1) https://blog.unicode.org/2019/05/unicode-12-1-en.html

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32285

   (3) https://bugs.python.org/issue?@action=redirect&bpo=37966


File: python.info,  Node: unittest<6>,  Next: venv<4>,  Prev: unicodedata<5>,  Up: 改進的模組<5>

1.6.5.43 unittest
.................

Added *note AsyncMock: 9ee. to support an asynchronous version of *note
Mock: 9ef.  Appropriate new assert functions for testing have been added
as well.  (Contributed by Lisa Roach in bpo-26467(1)).

Added *note addModuleCleanup(): 9f0. and *note addClassCleanup(): 9f1.
to unittest to support cleanups for ‘setUpModule()’ and *note
setUpClass(): 9f2.  (Contributed by Lisa Roach in bpo-24412(2).)

Several mock assert functions now also print a list of actual calls upon
failure.  (Contributed by Petter Strandmark in bpo-35047(3).)

*note unittest: ef. module gained support for coroutines to be used as
test cases with *note unittest.IsolatedAsyncioTestCase: 2de.
(Contributed by Andrew Svetlov in bpo-32972(4).)

範例：

     import unittest


     class TestRequest(unittest.IsolatedAsyncioTestCase):

         async def asyncSetUp(self):
             self.connection = await AsyncConnection()

         async def test_get(self):
             response = await self.connection.get("https://example.com")
             self.assertEqual(response.status_code, 200)

         async def asyncTearDown(self):
             await self.connection.close()


     if __name__ == "__main__":
         unittest.main()

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26467

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24412

   (3) https://bugs.python.org/issue?@action=redirect&bpo=35047

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32972


File: python.info,  Node: venv<4>,  Next: weakref,  Prev: unittest<6>,  Up: 改進的模組<5>

1.6.5.44 venv
.............

*note venv: f9. now includes an ‘Activate.ps1’ script on all platforms
for activating virtual environments under PowerShell Core 6.1.
(Contributed by Brett Cannon in bpo-32718(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32718


File: python.info,  Node: weakref,  Next: xml<4>,  Prev: venv<4>,  Up: 改進的模組<5>

1.6.5.45 weakref
................

The proxy objects returned by *note weakref.proxy(): 9f5. now support
the matrix multiplication operators ‘@’ and ‘@=’ in addition to the
other numeric operators.  (Contributed by Mark Dickinson in
bpo-36669(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36669


File: python.info,  Node: xml<4>,  Next: xmlrpc,  Prev: weakref,  Up: 改進的模組<5>

1.6.5.46 xml
............

As mitigation against DTD and external entity retrieval, the *note
xml.dom.minidom: 109. and *note xml.sax: 110. modules no longer process
external entities by default.  (Contributed by Christian Heimes in
bpo-17239(1).)

The ‘.find*()’ methods in the *note xml.etree.ElementTree: 10c. module
support wildcard searches like ‘{*}tag’ which ignores the namespace and
‘{namespace}*’ which returns all tags in the given namespace.
(Contributed by Stefan Behnel in bpo-28238(2).)

The *note xml.etree.ElementTree: 10c. module provides a new function
‘–xml.etree.ElementTree.canonicalize()’ that implements C14N 2.0.
(Contributed by Stefan Behnel in bpo-13611(3).)

The target object of *note xml.etree.ElementTree.XMLParser: 9f7. can
receive namespace declaration events through the new callback methods
‘start_ns()’ and ‘end_ns()’.  Additionally, the *note
xml.etree.ElementTree.TreeBuilder: 9f8. target can be configured to
process events about comments and processing instructions to include
them in the generated tree.  (Contributed by Stefan Behnel in
bpo-36676(4) and bpo-36673(5).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=17239

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28238

   (3) https://bugs.python.org/issue?@action=redirect&bpo=13611

   (4) https://bugs.python.org/issue?@action=redirect&bpo=36676

   (5) https://bugs.python.org/issue?@action=redirect&bpo=36673


File: python.info,  Node: xmlrpc,  Prev: xml<4>,  Up: 改進的模組<5>

1.6.5.47 xmlrpc
...............

*note xmlrpc.client.ServerProxy: 9fa. now supports an optional 'headers'
keyword argument for a sequence of HTTP headers to be sent with each
request.  Among other things, this makes it possible to upgrade from
default basic authentication to faster session authentication.
(Contributed by Cédric Krier in bpo-35153(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35153


File: python.info,  Node: 最佳化<5>,  Next: Build and C API Changes,  Prev: 改進的模組<5>,  Up: Python 3 8 有什麼新功能

1.6.6 最佳化
------------

   * The *note subprocess: c1. module can now use the *note
     os.posix_spawn(): 205. function in some cases for better
     performance.  Currently, it is only used on macOS and Linux (using
     glibc 2.24 or newer) if all these conditions are met:

        * 'close_fds' is false;

        * 'preexec_fn', 'pass_fds', 'cwd' and 'start_new_session'
          parameters are not set;

        * the 'executable' path contains a directory.

     （由 Joannah Nanjekye 和 Victor Stinner 在 bpo-35537(1) 中貢獻。）

   * *note shutil.copyfile(): 9fc, *note shutil.copy(): 9fd, *note
     shutil.copy2(): 9fe, *note shutil.copytree(): 9cd. and *note
     shutil.move(): 9ff. use platform-specific "fast-copy" syscalls on
     Linux and macOS in order to copy the file more efficiently.
     "fast-copy" means that the copying operation occurs within the
     kernel, avoiding the use of userspace buffers in Python as in
     "‘outfd.write(infd.read())’".  On Windows *note shutil.copyfile():
     9fc. uses a bigger default buffer size (1 MiB instead of 16 KiB)
     and a *note memoryview(): 40f.-based variant of *note
     shutil.copyfileobj(): a00. is used.  The speedup for copying a 512
     MiB file within the same partition is about +26% on Linux, +50% on
     macOS and +40% on Windows.  Also, much less CPU cycles are
     consumed.  See *note Platform-dependent efficient copy operations:
     a01. section.  (Contributed by Giampaolo Rodolà in bpo-33671(2).)

   * *note shutil.copytree(): 9cd. uses *note os.scandir(): a02.
     function and all copy functions depending from it use cached *note
     os.stat(): 448. values.  The speedup for copying a directory with
     8000 files is around +9% on Linux, +20% on Windows and +30% on a
     Windows SMB share.  Also the number of *note os.stat(): 448.
     syscalls is reduced by 38% making *note shutil.copytree(): 9cd.
     especially faster on network filesystems.  (Contributed by
     Giampaolo Rodolà in bpo-33695(3).)

   * The default protocol in the *note pickle: 95. module is now
     Protocol 4, first introduced in Python 3.4.  It offers better
     performance and smaller size compared to Protocol 3 available since
     Python 3.0.

   * Removed one *note Py_ssize_t: a03. member from ‘PyGC_Head’.  All GC
     tracked objects (e.g.  tuple, list, dict) size is reduced 4 or 8
     bytes.  (Contributed by Inada Naoki in bpo-33597(4).)

   * *note uuid.UUID: a04. now uses ‘__slots__’ to reduce its memory
     footprint.  (Contributed by Wouter Bolsterlee and Tal Einat in
     bpo-30977(5))

   * Improved performance of *note operator.itemgetter(): a05. by 33%.
     Optimized argument handling and added a fast path for the common
     case of a single non-negative integer index into a tuple (which is
     the typical use case in the standard library).  (Contributed by
     Raymond Hettinger in bpo-35664(6).)

   * Sped-up field lookups in *note collections.namedtuple(): 1ae.  They
     are now more than two times faster, making them the fastest form of
     instance variable lookup in Python.  (Contributed by Raymond
     Hettinger, Pablo Galindo, and Joe Jevnik, Serhiy Storchaka in
     bpo-32492(7).)

   * The *note list: 5b6. constructor does not overallocate the internal
     item buffer if the input iterable has a known length (the input
     implements ‘__len__’).  This makes the created list 12% smaller on
     average.  (Contributed by Raymond Hettinger and Pablo Galindo in
     bpo-33234(8).)

   * Doubled the speed of class variable writes.  When a non-dunder
     attribute was updated, there was an unnecessary call to update
     slots.  (Contributed by Stefan Behnel, Pablo Galindo Salgado,
     Raymond Hettinger, Neil Schemenauer, and Serhiy Storchaka in
     bpo-36012(9).)

   * Reduced an overhead of converting arguments passed to many builtin
     functions and methods.  This sped up calling some simple builtin
     functions and methods up to 20-50%.  (Contributed by Serhiy
     Storchaka in bpo-23867(10), bpo-35582(11) and bpo-36127(12).)

   * ‘LOAD_GLOBAL’ instruction now uses new "per opcode cache"
     mechanism.  It is about 40% faster now.  (Contributed by Yury
     Selivanov and Inada Naoki in bpo-26219(13).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35537

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33671

   (3) https://bugs.python.org/issue?@action=redirect&bpo=33695

   (4) https://bugs.python.org/issue?@action=redirect&bpo=33597

   (5) https://bugs.python.org/issue?@action=redirect&bpo=30977

   (6) https://bugs.python.org/issue?@action=redirect&bpo=35664

   (7) https://bugs.python.org/issue?@action=redirect&bpo=32492

   (8) https://bugs.python.org/issue?@action=redirect&bpo=33234

   (9) https://bugs.python.org/issue?@action=redirect&bpo=36012

   (10) https://bugs.python.org/issue?@action=redirect&bpo=23867

   (11) https://bugs.python.org/issue?@action=redirect&bpo=35582

   (12) https://bugs.python.org/issue?@action=redirect&bpo=36127

   (13) https://bugs.python.org/issue?@action=redirect&bpo=26219


File: python.info,  Node: Build and C API Changes,  Next: 已棄用<8>,  Prev: 最佳化<5>,  Up: Python 3 8 有什麼新功能

1.6.7 Build and C API Changes
-----------------------------

   * Default *note sys.abiflags: a07. became an empty string: the ‘m’
     flag for pymalloc became useless (builds with and without pymalloc
     are ABI compatible) and so has been removed.  (Contributed by
     Victor Stinner in bpo-36707(1).)

     Example of changes:

        * Only ‘python3.8’ program is installed, ‘python3.8m’ program is
          gone.

        * Only ‘python3.8-config’ script is installed,
          ‘python3.8m-config’ script is gone.

        * The ‘m’ flag has been removed from the suffix of dynamic
          library filenames: extension modules in the standard library
          as well as those produced and installed by third-party
          packages, like those downloaded from PyPI. On Linux, for
          example, the Python 3.7 suffix
          ‘.cpython-37m-x86_64-linux-gnu.so’ became
          ‘.cpython-38-x86_64-linux-gnu.so’ in Python 3.8.

   * The header files have been reorganized to better separate the
     different kinds of APIs:

        * ‘Include/*.h’ should be the portable public stable C API.

        * ‘Include/cpython/*.h’ should be the unstable C API specific to
          CPython; public API, with some private API prefixed by ‘_Py’
          or ‘_PY’.

        * ‘Include/internal/*.h’ is the private internal C API very
          specific to CPython.  This API comes with no backward
          compatibility warranty and should not be used outside CPython.
          It is only exposed for very specific needs like debuggers and
          profiles which has to access to CPython internals without
          calling functions.  This API is now installed by ‘make
          install’.

     （由 Victor Stinner 在 bpo-35134(2) 和 bpo-35081(3) 中貢獻，該工作
     由 Eric Snow 在 Python 3.7 中發起。）

   * Some macros have been converted to static inline functions:
     parameter types and return type are well defined, they don't have
     issues specific to macros, variables have a local scopes.
     Examples:

        * *note Py_INCREF(): 514, *note Py_DECREF(): 515.

        * *note Py_XINCREF(): a08, *note Py_XDECREF(): 733.

        * ‘PyObject_INIT()’, ‘PyObject_INIT_VAR()’

        * Private functions: ‘_PyObject_GC_TRACK()’,
          ‘_PyObject_GC_UNTRACK()’, ‘_Py_Dealloc()’

     （由 Victor Stinner 在 bpo-35059(4) 中貢獻。）

   * The ‘PyByteArray_Init()’ and ‘PyByteArray_Fini()’ functions have
     been removed.  They did nothing since Python 2.7.4 and Python
     3.2.0, were excluded from the limited API (stable ABI), and were
     not documented.  (Contributed by Victor Stinner in bpo-35713(5).)

   * The result of ‘PyExceptionClass_Name()’ is now of type ‘const char
     *’ rather of ‘char *’.  (Contributed by Serhiy Storchaka in
     bpo-33818(6).)

   * The duality of ‘Modules/Setup.dist’ and ‘Modules/Setup’ has been
     removed.  Previously, when updating the CPython source tree, one
     had to manually copy ‘Modules/Setup.dist’ (inside the source tree)
     to ‘Modules/Setup’ (inside the build tree) in order to reflect any
     changes upstream.  This was of a small benefit to packagers at the
     expense of a frequent annoyance to developers following CPython
     development, as forgetting to copy the file could produce build
     failures.

     Now the build system always reads from ‘Modules/Setup’ inside the
     source tree.  People who want to customize that file are encouraged
     to maintain their changes in a git fork of CPython or as patch
     files, as they would do for any other change to the source tree.

     （由 Antoine Pitrou 在 bpo-32430(7) 中貢獻。）

   * Functions that convert Python number to C integer like *note
     PyLong_AsLong(): 316. and argument parsing functions like *note
     PyArg_ParseTuple(): 517. with integer converting format units like
     ‘'i'’ will now use the *note __index__(): 6c1. special method
     instead of *note __int__(): 6c0, if available.  The deprecation
     warning will be emitted for objects with the ‘__int__()’ method but
     without the ‘__index__()’ method (like *note Decimal: 27c. and
     *note Fraction: 1c7.).  *note PyNumber_Check(): a09. will now
     return ‘1’ for objects implementing ‘__index__()’.  *note
     PyNumber_Long(): a0a, *note PyNumber_Float(): a0b. and *note
     PyFloat_AsDouble(): a0c. also now use the ‘__index__()’ method if
     available.  (Contributed by Serhiy Storchaka in bpo-36048(8) and
     bpo-20092(9).)

   * Heap-allocated type objects will now increase their reference count
     in *note PyObject_Init(): a0d. (and its parallel macro
     ‘PyObject_INIT’) instead of in *note PyType_GenericAlloc(): a0e.
     Types that modify instance allocation or deallocation may need to
     be adjusted.  (Contributed by Eddie Elizondo in bpo-35810(10).)

   * The new function ‘PyCode_NewWithPosOnlyArgs()’ allows to create
     code objects like ‘PyCode_New()’, but with an extra
     'posonlyargcount' parameter for indicating the number of
     positional-only arguments.  (Contributed by Pablo Galindo in
     bpo-37221(11).)

   * ‘Py_SetPath()’ now sets *note sys.executable: 383. to the program
     full path (*note Py_GetProgramFullPath(): 382.) rather than to the
     program name (*note Py_GetProgramName(): 384.).  (Contributed by
     Victor Stinner in bpo-38234(12).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36707

   (2) https://bugs.python.org/issue?@action=redirect&bpo=35134

   (3) https://bugs.python.org/issue?@action=redirect&bpo=35081

   (4) https://bugs.python.org/issue?@action=redirect&bpo=35059

   (5) https://bugs.python.org/issue?@action=redirect&bpo=35713

   (6) https://bugs.python.org/issue?@action=redirect&bpo=33818

   (7) https://bugs.python.org/issue?@action=redirect&bpo=32430

   (8) https://bugs.python.org/issue?@action=redirect&bpo=36048

   (9) https://bugs.python.org/issue?@action=redirect&bpo=20092

   (10) https://bugs.python.org/issue?@action=redirect&bpo=35810

   (11) https://bugs.python.org/issue?@action=redirect&bpo=37221

   (12) https://bugs.python.org/issue?@action=redirect&bpo=38234


File: python.info,  Node: 已棄用<8>,  Next: API and Feature Removals,  Prev: Build and C API Changes,  Up: Python 3 8 有什麼新功能

1.6.8 已棄用
------------

   * The distutils ‘bdist_wininst’ command is now deprecated, use
     ‘bdist_wheel’ (wheel packages) instead.  (Contributed by Victor
     Stinner in bpo-37481(1).)

   * Deprecated methods ‘getchildren()’ and ‘getiterator()’ in the *note
     ElementTree: 10c. module now emit a *note DeprecationWarning: 18b.
     instead of *note PendingDeprecationWarning: 86d.  They will be
     removed in Python 3.9.  (Contributed by Serhiy Storchaka in
     bpo-29209(2).)

   * Passing an object that is not an instance of *note
     concurrent.futures.ThreadPoolExecutor: 6e6. to *note
     loop.set_default_executor(): 6e7. is deprecated and will be
     prohibited in Python 3.9.  (Contributed by Elvis Pranskevichus in
     bpo-34075(3).)

   * The *note __getitem__(): 266. methods of *note
     xml.dom.pulldom.DOMEventStream: 6d9, *note
     wsgiref.util.FileWrapper: 6da. and *note fileinput.FileInput: 6db.
     have been deprecated.

     Implementations of these methods have been ignoring their 'index'
     parameter, and returning the next item instead.  (Contributed by
     Berker Peksag in bpo-9372(4).)

   * The *note typing.NamedTuple: 291. class has deprecated the
     ‘_field_types’ attribute in favor of the ‘__annotations__’
     attribute which has the same information.  (Contributed by Raymond
     Hettinger in bpo-36320(5).)

   * *note ast: 7. classes ‘Num’, ‘Str’, ‘Bytes’, ‘NameConstant’ and
     ‘Ellipsis’ are considered deprecated and will be removed in future
     Python versions.  *note Constant: 29a. should be used instead.
     (Contributed by Serhiy Storchaka in bpo-32892(6).)

   * *note ast.NodeVisitor: a10. methods ‘visit_Num()’, ‘visit_Str()’,
     ‘visit_Bytes()’, ‘visit_NameConstant()’ and ‘visit_Ellipsis()’ are
     deprecated now and will not be called in future Python versions.
     Add the *note visit_Constant(): a11. method to handle all constant
     nodes.  (Contributed by Serhiy Storchaka in bpo-36917(7).)

   * The ‘asyncio.coroutine()’ *note decorator: 6d5. is deprecated and
     will be removed in version 3.10.  Instead of ‘@asyncio.coroutine’,
     use *note async def: 575. instead.  (Contributed by Andrew Svetlov
     in bpo-36921(8).)

   * In *note asyncio: 8, the explicit passing of a 'loop' argument has
     been deprecated and will be removed in version 3.10 for the
     following: *note asyncio.sleep(): a12, *note asyncio.gather(): 5a2,
     *note asyncio.shield(): a13, *note asyncio.wait_for(): 5a4, *note
     asyncio.wait(): 426, *note asyncio.as_completed(): 190, *note
     asyncio.Task: 480, *note asyncio.Lock: a14, *note asyncio.Event:
     a15, *note asyncio.Condition: a16, *note asyncio.Semaphore: a17,
     *note asyncio.BoundedSemaphore: a18, *note asyncio.Queue: a19,
     *note asyncio.create_subprocess_exec(): a1a, and *note
     asyncio.create_subprocess_shell(): a1b.

   * The explicit passing of coroutine objects to *note asyncio.wait():
     426. has been deprecated and will be removed in version 3.11.
     (Contributed by Yury Selivanov in bpo-34790(9).)

   * The following functions and methods are deprecated in the *note
     gettext: 59. module: ‘lgettext()’, ‘ldgettext()’, ‘lngettext()’ and
     ‘ldngettext()’.  They return encoded bytes, and it's possible that
     you will get unexpected Unicode-related exceptions if there are
     encoding problems with the translated strings.  It's much better to
     use alternatives which return Unicode strings in Python 3.  These
     functions have been broken for a long time.

     Function ‘bind_textdomain_codeset()’, methods ‘output_charset()’
     and ‘set_output_charset()’, and the 'codeset' parameter of
     functions *note translation(): a1c. and *note install(): a1d. are
     also deprecated, since they are only used for the ‘l*gettext()’
     functions.  (Contributed by Serhiy Storchaka in bpo-33710(10).)

   * The ‘isAlive()’ method of *note threading.Thread: 8f0. has been
     deprecated.  (Contributed by Donghee Na in bpo-35283(11).)

   * Many builtin and extension functions that take integer arguments
     will now emit a deprecation warning for *note Decimal: 27c.s, *note
     Fraction: 1c7.s and any other objects that can be converted to
     integers only with a loss (e.g.  that have the *note __int__():
     6c0. method but do not have the *note __index__(): 6c1. method).
     In future version they will be errors.  (Contributed by Serhiy
     Storchaka in bpo-36048(12).)

   * Deprecated passing the following arguments as keyword arguments:

        - 'func' in *note functools.partialmethod(): a1e, *note
          weakref.finalize(): a1f, *note profile.Profile.runcall(): a20,
          ‘cProfile.Profile.runcall()’, *note bdb.Bdb.runcall(): a21,
          *note trace.Trace.runfunc(): a22. and *note curses.wrapper():
          a23.

        - 'function' in *note unittest.TestCase.addCleanup(): a24.

        - 'fn' in the *note submit(): a25. method of *note
          concurrent.futures.ThreadPoolExecutor: 6e6. and *note
          concurrent.futures.ProcessPoolExecutor: 893.

        - 'callback' in *note contextlib.ExitStack.callback(): a26,
          ‘contextlib.AsyncExitStack.callback()’ and *note
          contextlib.AsyncExitStack.push_async_callback(): a27.

        - 'c' and 'typeid' in the ‘create()’ method of
          ‘multiprocessing.managers.Server’ and
          ‘multiprocessing.managers.SharedMemoryServer’.

        - 'obj' in *note weakref.finalize(): a1f.

     In future releases of Python, they will be *note positional-only:
     a28.  (Contributed by Serhiy Storchaka in bpo-36492(13).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=37481

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29209

   (3) https://bugs.python.org/issue?@action=redirect&bpo=34075

   (4) https://bugs.python.org/issue?@action=redirect&bpo=9372

   (5) https://bugs.python.org/issue?@action=redirect&bpo=36320

   (6) https://bugs.python.org/issue?@action=redirect&bpo=32892

   (7) https://bugs.python.org/issue?@action=redirect&bpo=36917

   (8) https://bugs.python.org/issue?@action=redirect&bpo=36921

   (9) https://bugs.python.org/issue?@action=redirect&bpo=34790

   (10) https://bugs.python.org/issue?@action=redirect&bpo=33710

   (11) https://bugs.python.org/issue?@action=redirect&bpo=35283

   (12) https://bugs.python.org/issue?@action=redirect&bpo=36048

   (13) https://bugs.python.org/issue?@action=redirect&bpo=36492


File: python.info,  Node: API and Feature Removals,  Next: Porting to Python 3 8,  Prev: 已棄用<8>,  Up: Python 3 8 有什麼新功能

1.6.9 API and Feature Removals
------------------------------

The following features and APIs have been removed from Python 3.8:

   * Starting with Python 3.3, importing ABCs from *note collections:
     16. was deprecated, and importing should be done from *note
     collections.abc: 17.  Being able to import from collections was
     marked for removal in 3.8, but has been delayed to 3.9.  (See
     bpo-36952(1).)

   * The ‘macpath’ module, deprecated in Python 3.7, has been removed.
     (Contributed by Victor Stinner in bpo-35471(2).)

   * The function ‘platform.popen()’ has been removed, after having been
     deprecated since Python 3.3: use *note os.popen(): a2a. instead.
     (Contributed by Victor Stinner in bpo-35345(3).)

   * The function ‘time.clock()’ has been removed, after having been
     deprecated since Python 3.3: use *note time.perf_counter(): a2b. or
     *note time.process_time(): a2c. instead, depending on your
     requirements, to have well-defined behavior.  (Contributed by
     Matthias Bussonnier in bpo-36895(4).)

   * The ‘pyvenv’ script has been removed in favor of ‘python3.8 -m
     venv’ to help eliminate confusion as to what Python interpreter the
     ‘pyvenv’ script is tied to.  (Contributed by Brett Cannon in
     bpo-25427(5).)

   * ‘parse_qs’, ‘parse_qsl’, and ‘escape’ are removed from the ‘cgi’
     module.  They are deprecated in Python 3.2 or older.  They should
     be imported from the ‘urllib.parse’ and ‘html’ modules instead.

   * ‘filemode’ function is removed from the *note tarfile: c8. module.
     It is not documented and deprecated since Python 3.3.

   * The *note XMLParser: 9f7. constructor no longer accepts the 'html'
     argument.  It never had an effect and was deprecated in Python 3.4.
     All other parameters are now *note keyword-only: 285.  (Contributed
     by Serhiy Storchaka in bpo-29209(6).)

   * Removed the ‘doctype()’ method of *note XMLParser: 9f7.
     (Contributed by Serhiy Storchaka in bpo-29209(7).)

   * "unicode_internal" codec is removed.  (Contributed by Inada Naoki
     in bpo-36297(8).)

   * The ‘Cache’ and ‘Statement’ objects of the *note sqlite3: ba.
     module are not exposed to the user.  (Contributed by Aviv Palivoda
     in bpo-30262(9).)

   * The ‘bufsize’ keyword argument of *note fileinput.input(): 7a3. and
     *note fileinput.FileInput(): 6db. which was ignored and deprecated
     since Python 3.6 has been removed.  bpo-36952(10) (Contributed by
     Matthias Bussonnier.)

   * The functions ‘sys.set_coroutine_wrapper()’ and
     ‘sys.get_coroutine_wrapper()’ deprecated in Python 3.7 have been
     removed; bpo-36933(11) (Contributed by Matthias Bussonnier.)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36952

   (2) https://bugs.python.org/issue?@action=redirect&bpo=35471

   (3) https://bugs.python.org/issue?@action=redirect&bpo=35345

   (4) https://bugs.python.org/issue?@action=redirect&bpo=36895

   (5) https://bugs.python.org/issue?@action=redirect&bpo=25427

   (6) https://bugs.python.org/issue?@action=redirect&bpo=29209

   (7) https://bugs.python.org/issue?@action=redirect&bpo=29209

   (8) https://bugs.python.org/issue?@action=redirect&bpo=36297

   (9) https://bugs.python.org/issue?@action=redirect&bpo=30262

   (10) https://bugs.python.org/issue?@action=redirect&bpo=36952

   (11) https://bugs.python.org/issue?@action=redirect&bpo=36933


File: python.info,  Node: Porting to Python 3 8,  Next: Python 3 8 1 中顯著的變更,  Prev: API and Feature Removals,  Up: Python 3 8 有什麼新功能

1.6.10 Porting to Python 3.8
----------------------------

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

* Menu:

* Changes in Python behavior::
* Changes in the Python API: Changes in the Python API<3>.
* C API 中的改動: C API 中的改動<3>.
* CPython 位元組碼變更: CPython 位元組碼變更<5>.
* Demos and Tools: Demos and Tools<2>.


File: python.info,  Node: Changes in Python behavior,  Next: Changes in the Python API<3>,  Up: Porting to Python 3 8

1.6.10.1 Changes in Python behavior
...................................

   * Yield expressions (both ‘yield’ and ‘yield from’ clauses) are now
     disallowed in comprehensions and generator expressions (aside from
     the iterable expression in the leftmost ‘for’ clause).
     (Contributed by Serhiy Storchaka in bpo-10544(1).)

   * The compiler now produces a *note SyntaxWarning: 40c. when identity
     checks (‘is’ and ‘is not’) are used with certain types of literals
     (e.g.  strings, numbers).  These can often work by accident in
     CPython, but are not guaranteed by the language spec.  The warning
     advises users to use equality tests (‘==’ and ‘!=’) instead.
     (Contributed by Serhiy Storchaka in bpo-34850(2).)

   * The CPython interpreter can swallow exceptions in some
     circumstances.  In Python 3.8 this happens in fewer cases.  In
     particular, exceptions raised when getting the attribute from the
     type dictionary are no longer ignored.  (Contributed by Serhiy
     Storchaka in bpo-35459(3).)

   * Removed ‘__str__’ implementations from builtin types *note bool:
     40e, *note int: 23c, *note float: 2c8, *note complex: 2c9. and few
     classes from the standard library.  They now inherit ‘__str__()’
     from *note object: a2f.  As result, defining the ‘__repr__()’
     method in the subclass of these classes will affect their string
     representation.  (Contributed by Serhiy Storchaka in bpo-36793(4).)

   * On AIX, *note sys.platform: a30. doesn't contain the major version
     anymore.  It is always ‘'aix'’, instead of ‘'aix3'’ ..  ‘'aix7'’.
     Since older Python versions include the version number, so it is
     recommended to always use ‘sys.platform.startswith('aix')’.
     (Contributed by M. Felt in bpo-36588(5).)

   * ‘PyEval_AcquireLock()’ and ‘PyEval_AcquireThread()’ now terminate
     the current thread if called while the interpreter is finalizing,
     making them consistent with *note PyEval_RestoreThread(): 374,
     *note Py_END_ALLOW_THREADS(): a31, and *note PyGILState_Ensure():
     376.  If this behavior is not desired, guard the call by checking
     ‘_Py_IsFinalizing()’ or *note sys.is_finalizing(): a32.
     (Contributed by Joannah Nanjekye in bpo-36475(6).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=10544

   (2) https://bugs.python.org/issue?@action=redirect&bpo=34850

   (3) https://bugs.python.org/issue?@action=redirect&bpo=35459

   (4) https://bugs.python.org/issue?@action=redirect&bpo=36793

   (5) https://bugs.python.org/issue?@action=redirect&bpo=36588

   (6) https://bugs.python.org/issue?@action=redirect&bpo=36475


File: python.info,  Node: Changes in the Python API<3>,  Next: C API 中的改動<3>,  Prev: Changes in Python behavior,  Up: Porting to Python 3 8

1.6.10.2 Changes in the Python API
..................................

   * The *note os.getcwdb(): a34. function now uses the UTF-8 encoding
     on Windows, rather than the ANSI code page: see PEP 529(1) for the
     rationale.  The function is no longer deprecated on Windows.
     (Contributed by Victor Stinner in bpo-37412(2).)

   * *note subprocess.Popen: 17d. can now use *note os.posix_spawn():
     205. in some cases for better performance.  On Windows Subsystem
     for Linux and QEMU User Emulation, the ‘Popen’ constructor using
     *note os.posix_spawn(): 205. no longer raises an exception on
     errors like "missing program".  Instead the child process fails
     with a non-zero ‘returncode’.  (Contributed by Joannah Nanjekye and
     Victor Stinner in bpo-35537(3).)

   * The 'preexec_fn' argument of * *note subprocess.Popen: 17d. is no
     longer compatible with subinterpreters.  The use of the parameter
     in a subinterpreter now raises *note RuntimeError: 179.
     (Contributed by Eric Snow in bpo-34651(4), modified by Christian
     Heimes in bpo-37951(5).)

   * The ‘imap.IMAP4.logout()’ method no longer silently ignores
     arbitrary exceptions.  (Contributed by Victor Stinner in
     bpo-36348(6).)

   * The function ‘platform.popen()’ has been removed, after having been
     deprecated since Python 3.3: use *note os.popen(): a2a. instead.
     (Contributed by Victor Stinner in bpo-35345(7).)

   * The *note statistics.mode(): a35. function no longer raises an
     exception when given multimodal data.  Instead, it returns the
     first mode encountered in the input data.  (Contributed by Raymond
     Hettinger in bpo-35892(8).)

   * The *note selection(): a36. method of the *note
     tkinter.ttk.Treeview: a37. class no longer takes arguments.  Using
     it with arguments for changing the selection was deprecated in
     Python 3.6.  Use specialized methods like *note selection_set():
     a38. for changing the selection.  (Contributed by Serhiy Storchaka
     in bpo-31508(9).)

   * The ‘writexml()’, ‘toxml()’ and ‘toprettyxml()’ methods of *note
     xml.dom.minidom: 109, and the ‘write()’ method of ‘xml.etree’, now
     preserve the attribute order specified by the user.  (Contributed
     by Diego Rojas and Raymond Hettinger in bpo-34160(10).)

   * A *note dbm.dumb: 2a. database opened with flags ‘'r'’ is now
     read-only.  *note dbm.dumb.open(): a39. with flags ‘'r'’ and ‘'w'’
     no longer creates a database if it does not exist.  (Contributed by
     Serhiy Storchaka in bpo-32749(11).)

   * The ‘doctype()’ method defined in a subclass of *note XMLParser:
     9f7. will no longer be called and will emit a *note RuntimeWarning:
     1a3. instead of a *note DeprecationWarning: 18b.  Define the *note
     doctype(): a3a. method on a target for handling an XML doctype
     declaration.  (Contributed by Serhiy Storchaka in bpo-29209(12).)

   * A *note RuntimeError: 179. is now raised when the custom metaclass
     doesn't provide the ‘__classcell__’ entry in the namespace passed
     to ‘type.__new__’.  A *note DeprecationWarning: 18b. was emitted in
     Python 3.6-3.7.  (Contributed by Serhiy Storchaka in
     bpo-23722(13).)

   * The ‘cProfile.Profile’ class can now be used as a context manager.
     (Contributed by Scott Sanderson in bpo-29235(14).)

   * *note shutil.copyfile(): 9fc, *note shutil.copy(): 9fd, *note
     shutil.copy2(): 9fe, *note shutil.copytree(): 9cd. and *note
     shutil.move(): 9ff. use platform-specific "fast-copy" syscalls (see
     *note Platform-dependent efficient copy operations: a01. section).

   * *note shutil.copyfile(): 9fc. default buffer size on Windows was
     changed from 16 KiB to 1 MiB.

   * The ‘PyGC_Head’ struct has changed completely.  All code that
     touched the struct member should be rewritten.  (See
     bpo-33597(15).)

   * The *note PyInterpreterState: 862. struct has been moved into the
     "internal" header files (specifically
     Include/internal/pycore_pystate.h).  An opaque ‘PyInterpreterState’
     is still available as part of the public API (and stable ABI). The
     docs indicate that none of the struct's fields are public, so we
     hope no one has been using them.  However, if you do rely on one or
     more of those private fields and have no alternative then please
     open a BPO issue.  We'll work on helping you adjust (possibly
     including adding accessor functions to the public API). (See
     bpo-35886(16).)

   * The *note mmap.flush(): a3b. method now returns ‘None’ on success
     and raises an exception on error under all platforms.  Previously,
     its behavior was platform-dependent: a nonzero value was returned
     on success; zero was returned on error under Windows.  A zero value
     was returned on success; an exception was raised on error under
     Unix.  (Contributed by Berker Peksag in bpo-2122(17).)

   * *note xml.dom.minidom: 109. and *note xml.sax: 110. modules no
     longer process external entities by default.  (Contributed by
     Christian Heimes in bpo-17239(18).)

   * Deleting a key from a read-only *note dbm: 29. database (*note
     dbm.dumb: 2a, *note dbm.gnu: 2b. or *note dbm.ndbm: 2c.) raises
     ‘error’ (*note dbm.dumb.error: a3c, *note dbm.gnu.error: a3d. or
     *note dbm.ndbm.error: a3e.) instead of *note KeyError: 2fb.
     (Contributed by Xiang Zhang in bpo-33106(19).)

   * Simplified AST for literals.  All constants will be represented as
     *note ast.Constant: 29a. instances.  Instantiating old classes
     ‘Num’, ‘Str’, ‘Bytes’, ‘NameConstant’ and ‘Ellipsis’ will return an
     instance of ‘Constant’.  (Contributed by Serhiy Storchaka in
     bpo-32892(20).)

   * *note expanduser(): 9b8. on Windows now prefers the ‘USERPROFILE’
     environment variable and does not use ‘HOME’, which is not normally
     set for regular user accounts.  (Contributed by Anthony Sottile in
     bpo-36264(21).)

   * The exception *note asyncio.CancelledError: 19e. now inherits from
     *note BaseException: 55f. rather than *note Exception: 97d. and no
     longer inherits from *note concurrent.futures.CancelledError: 97e.
     (Contributed by Yury Selivanov in bpo-32528(22).)

   * The function *note asyncio.wait_for(): 5a4. now correctly waits for
     cancellation when using an instance of *note asyncio.Task: 480.
     Previously, upon reaching 'timeout', it was cancelled and
     immediately returned.  (Contributed by Elvis Pranskevichus in
     bpo-32751(23).)

   * The function *note asyncio.BaseTransport.get_extra_info(): a3f. now
     returns a safe to use socket object when 'socket' is passed to the
     'name' parameter.  (Contributed by Yury Selivanov in
     bpo-37027(24).)

   * *note asyncio.BufferedProtocol: a40. has graduated to the stable
     API.

   * DLL dependencies for extension modules and DLLs loaded with *note
     ctypes: 22. on Windows are now resolved more securely.  Only the
     system paths, the directory containing the DLL or PYD file, and
     directories added with *note add_dll_directory(): 98e. are searched
     for load-time dependencies.  Specifically, ‘PATH’ and the current
     working directory are no longer used, and modifications to these
     will no longer have any effect on normal DLL resolution.  If your
     application relies on these mechanisms, you should check for *note
     add_dll_directory(): 98e. and if it exists, use it to add your DLLs
     directory while loading your library.  Note that Windows 7 users
     will need to ensure that Windows Update KB2533623 has been
     installed (this is also verified by the installer).  (Contributed
     by Steve Dower in bpo-36085(25).)

   * The header files and functions related to pgen have been removed
     after its replacement by a pure Python implementation.
     (Contributed by Pablo Galindo in bpo-36623(26).)

   * *note types.CodeType: 2b6. has a new parameter in the second
     position of the constructor ('posonlyargcount') to support
     positional-only arguments defined in PEP 570(27).  The first
     argument ('argcount') now represents the total number of positional
     arguments (including positional-only arguments).  The new
     ‘replace()’ method of *note types.CodeType: 2b6. can be used to
     make the code future-proof.

   * The parameter ‘digestmod’ for *note hmac.new(): a42. no longer uses
     the MD5 digest by default.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0529/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=37412

   (3) https://bugs.python.org/issue?@action=redirect&bpo=35537

   (4) https://bugs.python.org/issue?@action=redirect&bpo=34651

   (5) https://bugs.python.org/issue?@action=redirect&bpo=37951

   (6) https://bugs.python.org/issue?@action=redirect&bpo=36348

   (7) https://bugs.python.org/issue?@action=redirect&bpo=35345

   (8) https://bugs.python.org/issue?@action=redirect&bpo=35892

   (9) https://bugs.python.org/issue?@action=redirect&bpo=31508

   (10) https://bugs.python.org/issue?@action=redirect&bpo=34160

   (11) https://bugs.python.org/issue?@action=redirect&bpo=32749

   (12) https://bugs.python.org/issue?@action=redirect&bpo=29209

   (13) https://bugs.python.org/issue?@action=redirect&bpo=23722

   (14) https://bugs.python.org/issue?@action=redirect&bpo=29235

   (15) https://bugs.python.org/issue?@action=redirect&bpo=33597

   (16) https://bugs.python.org/issue?@action=redirect&bpo=35886

   (17) https://bugs.python.org/issue?@action=redirect&bpo=2122

   (18) https://bugs.python.org/issue?@action=redirect&bpo=17239

   (19) https://bugs.python.org/issue?@action=redirect&bpo=33106

   (20) https://bugs.python.org/issue?@action=redirect&bpo=32892

   (21) https://bugs.python.org/issue?@action=redirect&bpo=36264

   (22) https://bugs.python.org/issue?@action=redirect&bpo=32528

   (23) https://bugs.python.org/issue?@action=redirect&bpo=32751

   (24) https://bugs.python.org/issue?@action=redirect&bpo=37027

   (25) https://bugs.python.org/issue?@action=redirect&bpo=36085

   (26) https://bugs.python.org/issue?@action=redirect&bpo=36623

   (27) https://peps.python.org/pep-0570/


File: python.info,  Node: C API 中的改動<3>,  Next: CPython 位元組碼變更<5>,  Prev: Changes in the Python API<3>,  Up: Porting to Python 3 8

1.6.10.3 C API 中的改動
.......................

   * The *note PyCompilerFlags: a44. structure got a new
     'cf_feature_version' field.  It should be initialized to
     ‘PY_MINOR_VERSION’.  The field is ignored by default, and is used
     if and only if ‘PyCF_ONLY_AST’ flag is set in 'cf_flags'.
     (Contributed by Guido van Rossum in bpo-35766(1).)

   * The ‘PyEval_ReInitThreads()’ function has been removed from the C
     API. It should not be called explicitly: use *note
     PyOS_AfterFork_Child(): 3c3. instead.  (Contributed by Victor
     Stinner in bpo-36728(2).)

   * On Unix, C extensions are no longer linked to libpython except on
     Android and Cygwin.  When Python is embedded, ‘libpython’ must not
     be loaded with ‘RTLD_LOCAL’, but ‘RTLD_GLOBAL’ instead.
     Previously, using ‘RTLD_LOCAL’, it was already not possible to load
     C extensions which were not linked to ‘libpython’, like C
     extensions of the standard library built by the ‘*shared*’ section
     of ‘Modules/Setup’.  (Contributed by Victor Stinner in
     bpo-21536(3).)

   * Use of ‘#’ variants of formats in parsing or building value (e.g.
     *note PyArg_ParseTuple(): 517, *note Py_BuildValue(): 84c, *note
     PyObject_CallFunction(): 365, etc.)  without ‘PY_SSIZE_T_CLEAN’
     defined raises ‘DeprecationWarning’ now.  It will be removed in
     3.10 or 4.0.  Read *note 剖析引數與建置數值: 84d. for detail.
     (Contributed by Inada Naoki in bpo-36381(4).)

   * Instances of heap-allocated types (such as those created with *note
     PyType_FromSpec(): 523.) hold a reference to their type object.
     Increasing the reference count of these type objects has been moved
     from *note PyType_GenericAlloc(): a0e. to the more low-level
     functions, *note PyObject_Init(): a0d. and ‘PyObject_INIT()’.  This
     makes types created through *note PyType_FromSpec(): 523. behave
     like other classes in managed code.

     *note Statically allocated types: 723. are not affected.

     For the vast majority of cases, there should be no side effect.
     However, types that manually increase the reference count after
     allocating an instance (perhaps to work around the bug) may now
     become immortal.  To avoid this, these classes need to call
     Py_DECREF on the type object during instance deallocation.

     To correctly port these types into 3.8, please apply the following
     changes:

        * Remove *note Py_INCREF: 514. on the type object after
          allocating an instance - if any.  This may happen after
          calling *note PyObject_New: 929, *note PyObject_NewVar: 92a,
          *note PyObject_GC_New(): a45, *note PyObject_GC_NewVar(): a46,
          or any other custom allocator that uses *note PyObject_Init():
          a0d. or ‘PyObject_INIT()’.

          範例：

               static foo_struct *
               foo_new(PyObject *type) {
                   foo_struct *foo = PyObject_GC_New(foo_struct, (PyTypeObject *) type);
                   if (foo == NULL)
                       return NULL;
               #if PY_VERSION_HEX < 0x03080000
                   // Workaround for Python issue 35810; no longer necessary in Python 3.8
                   PY_INCREF(type)
               #endif
                   return foo;
               }

        * Ensure that all custom ‘tp_dealloc’ functions of
          heap-allocated types decrease the type's reference count.

          範例：

               static void
               foo_dealloc(foo_struct *instance) {
                   PyObject *type = Py_TYPE(instance);
                   PyObject_GC_Del(instance);
               #if PY_VERSION_HEX >= 0x03080000
                   // This was not needed before Python 3.8 (Python issue 35810)
                   Py_DECREF(type);
               #endif
               }

     （由 Eddie Elizondo 在 bpo-35810(5) 中貢獻。）

   * The *note Py_DEPRECATED(): a47. macro has been implemented for
     MSVC.  The macro now must be placed before the symbol name.

     範例：

          Py_DEPRECATED(3.8) PyAPI_FUNC(int) Py_OldFunction(void);

     （由 Zackery Spytz 在 bpo-33407(6) 中貢獻。）

   * The interpreter does not pretend to support binary compatibility of
     extension types across feature releases, anymore.  A *note
     PyTypeObject: a48. exported by a third-party extension module is
     supposed to have all the slots expected in the current Python
     version, including *note tp_finalize: a49. (*note
     Py_TPFLAGS_HAVE_FINALIZE: 3ba. is not checked anymore before
     reading *note tp_finalize: a49.).

     （由 Antoine Pitrou 在 bpo-32388(7) 中貢獻。）

   * The functions ‘PyNode_AddChild()’ and ‘PyParser_AddToken()’ now
     accept two additional ‘int’ arguments 'end_lineno' and
     'end_col_offset'.

   * The ‘libpython38.a’ file to allow MinGW tools to link directly
     against ‘python38.dll’ is no longer included in the regular Windows
     distribution.  If you require this file, it may be generated with
     the ‘gendef’ and ‘dlltool’ tools, which are part of the MinGW
     binutils package:

          gendef - python38.dll > tmp.def
          dlltool --dllname python38.dll --def tmp.def --output-lib libpython38.a

     The location of an installed ‘pythonXY.dll’ will depend on the
     installation options and the version and language of Windows.  See
     *note 在 Windows 上使用 Python: a4a. for more information.  The
     resulting library should be placed in the same directory as
     ‘pythonXY.lib’, which is generally the ‘libs’ directory under your
     Python installation.

     （由 Steve Dower 在 bpo-37351(8) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35766

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36728

   (3) https://bugs.python.org/issue?@action=redirect&bpo=21536

   (4) https://bugs.python.org/issue?@action=redirect&bpo=36381

   (5) https://bugs.python.org/issue?@action=redirect&bpo=35810

   (6) https://bugs.python.org/issue?@action=redirect&bpo=33407

   (7) https://bugs.python.org/issue?@action=redirect&bpo=32388

   (8) https://bugs.python.org/issue?@action=redirect&bpo=37351


File: python.info,  Node: CPython 位元組碼變更<5>,  Next: Demos and Tools<2>,  Prev: C API 中的改動<3>,  Up: Porting to Python 3 8

1.6.10.4 CPython 位元組碼變更
.............................

   * The interpreter loop has been simplified by moving the logic of
     unrolling the stack of blocks into the compiler.  The compiler
     emits now explicit instructions for adjusting the stack of values
     and calling the cleaning-up code for *note break: a4c, *note
     continue: 96d. and *note return: 972.

     Removed opcodes ‘BREAK_LOOP’, ‘CONTINUE_LOOP’, ‘SETUP_LOOP’ and
     ‘SETUP_EXCEPT’.  Added new opcodes ‘ROT_FOUR’, ‘BEGIN_FINALLY’,
     ‘CALL_FINALLY’ and ‘POP_FINALLY’.  Changed the behavior of
     ‘END_FINALLY’ and ‘WITH_CLEANUP_START’.

     （由 Mark Shannon、Antoine Pitrou 和 Serhiy Storchaka 在
     bpo-17611(1) 中貢獻。）

   * Added new opcode *note END_ASYNC_FOR: a4d. for handling exceptions
     raised when awaiting a next item in an *note async for: a4e. loop.
     (Contributed by Serhiy Storchaka in bpo-33041(2).)

   * The *note MAP_ADD: a4f. now expects the value as the first element
     in the stack and the key as the second element.  This change was
     made so the key is always evaluated before the value in dictionary
     comprehensions, as proposed by PEP 572(3).  (Contributed by Jörn
     Heissler in bpo-35224(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=17611

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33041

   (3) https://peps.python.org/pep-0572/

   (4) https://bugs.python.org/issue?@action=redirect&bpo=35224


File: python.info,  Node: Demos and Tools<2>,  Prev: CPython 位元組碼變更<5>,  Up: Porting to Python 3 8

1.6.10.5 Demos and Tools
........................

Added a benchmark script for timing various ways to access variables:
‘Tools/scripts/var_access_benchmark.py’.  (Contributed by Raymond
Hettinger in bpo-35884(1).)

Here's a summary of performance improvements since Python 3.3:

     Python version                       3.3     3.4     3.5     3.6     3.7     3.8
     --------------                       ---     ---     ---     ---     ---     ---

     Variable and attribute read access:
         read_local                       4.0     7.1     7.1     5.4     5.1     3.9
         read_nonlocal                    5.3     7.1     8.1     5.8     5.4     4.4
         read_global                     13.3    15.5    19.0    14.3    13.6     7.6
         read_builtin                    20.0    21.1    21.6    18.5    19.0     7.5
         read_classvar_from_class        20.5    25.6    26.5    20.7    19.5    18.4
         read_classvar_from_instance     18.5    22.8    23.5    18.8    17.1    16.4
         read_instancevar                26.8    32.4    33.1    28.0    26.3    25.4
         read_instancevar_slots          23.7    27.8    31.3    20.8    20.8    20.2
         read_namedtuple                 68.5    73.8    57.5    45.0    46.8    18.4
         read_boundmethod                29.8    37.6    37.9    29.6    26.9    27.7

     Variable and attribute write access:
         write_local                      4.6     8.7     9.3     5.5     5.3     4.3
         write_nonlocal                   7.3    10.5    11.1     5.6     5.5     4.7
         write_global                    15.9    19.7    21.2    18.0    18.0    15.8
         write_classvar                  81.9    92.9    96.0   104.6   102.1    39.2
         write_instancevar               36.4    44.6    45.8    40.0    38.9    35.5
         write_instancevar_slots         28.7    35.6    36.1    27.3    26.6    25.7

     Data structure read access:
         read_list                       19.2    24.2    24.5    20.8    20.8    19.0
         read_deque                      19.9    24.7    25.5    20.2    20.6    19.8
         read_dict                       19.7    24.3    25.7    22.3    23.0    21.0
         read_strdict                    17.9    22.6    24.3    19.5    21.2    18.9

     Data structure write access:
         write_list                      21.2    27.1    28.5    22.5    21.6    20.0
         write_deque                     23.8    28.7    30.1    22.7    21.8    23.5
         write_dict                      25.9    31.4    33.3    29.3    29.2    24.7
         write_strdict                   22.9    28.4    29.9    27.5    25.2    23.1

     Stack (or queue) operations:
         list_append_pop                144.2    93.4   112.7    75.4    74.2    50.8
         deque_append_pop                30.4    43.5    57.0    49.4    49.2    42.5
         deque_append_popleft            30.8    43.7    57.3    49.7    49.7    42.8

     Timing loop:
         loop_overhead                    0.3     0.5     0.6     0.4     0.3     0.3

The benchmarks were measured on an Intel® Core™ i7-4960HQ processor(2)
running the macOS 64-bit builds found at python.org(3).  The benchmark
script displays timings in nanoseconds.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35884

   (2) 
https://ark.intel.com/content/www/us/en/ark/products/76088/intel-core-i7-4960hq-processor-6m-cache-up-to-3-80-ghz.html

   (3) https://www.python.org/downloads/macos/


File: python.info,  Node: Python 3 8 1 中顯著的變更,  Next: Python 3 8 2 中顯著的變更,  Prev: Porting to Python 3 8,  Up: Python 3 8 有什麼新功能

1.6.11 Python 3.8.1 中顯著的變更
--------------------------------

Due to significant security concerns, the 'reuse_address' parameter of
*note asyncio.loop.create_datagram_endpoint(): 6d7. is no longer
supported.  This is because of the behavior of the socket option
‘SO_REUSEADDR’ in UDP. For more details, see the documentation for
‘loop.create_datagram_endpoint()’.  (Contributed by Kyle Stanley,
Antoine Pitrou, and Yury Selivanov in bpo-37228(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=37228


File: python.info,  Node: Python 3 8 2 中顯著的變更,  Next: Python 3 8 3 中顯著的變更,  Prev: Python 3 8 1 中顯著的變更,  Up: Python 3 8 有什麼新功能

1.6.12 Python 3.8.2 中顯著的變更
--------------------------------

Fixed a regression with the ‘ignore’ callback of *note
shutil.copytree(): 9cd.  The argument types are now str and List[str]
again.  (Contributed by Manuel Barkhau and Giampaolo Rodola in
gh-83571(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/83571


File: python.info,  Node: Python 3 8 3 中顯著的變更,  Next: Python 3 8 8 中顯著的變更,  Prev: Python 3 8 2 中顯著的變更,  Up: Python 3 8 有什麼新功能

1.6.13 Python 3.8.3 中顯著的變更
--------------------------------

The constant values of future flags in the *note __future__: 0. module
are updated in order to prevent collision with compiler flags.
Previously ‘PyCF_ALLOW_TOP_LEVEL_AWAIT’ was clashing with
‘CO_FUTURE_DIVISION’.  (Contributed by Batuhan Taskaya in gh-83743(1))

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/83743


File: python.info,  Node: Python 3 8 8 中顯著的變更,  Next: Python 3 8 9 中顯著的變更,  Prev: Python 3 8 3 中顯著的變更,  Up: Python 3 8 有什麼新功能

1.6.14 Python 3.8.8 中顯著的變更
--------------------------------

Earlier Python versions allowed using both ‘;’ and ‘&’ as query
parameter separators in *note urllib.parse.parse_qs(): 25f. and *note
urllib.parse.parse_qsl(): 25e.  Due to security concerns, and to conform
with newer W3C recommendations, this has been changed to allow only a
single separator key, with ‘&’ as the default.  This change also affects
‘cgi.parse()’ and ‘cgi.parse_multipart()’ as they use the affected
functions internally.  For more details, please see their respective
documentation.  (Contributed by Adam Goldschmidt, Senthil Kumaran and
Ken Jin in bpo-42967(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42967


File: python.info,  Node: Python 3 8 9 中顯著的變更,  Next: Python 3 8 10 中顯著的變更,  Prev: Python 3 8 8 中顯著的變更,  Up: Python 3 8 有什麼新功能

1.6.15 Python 3.8.9 中顯著的變更
--------------------------------

A security fix alters the *note ftplib.FTP: 89f. behavior to not trust
the IPv4 address sent from the remote server when setting up a passive
data channel.  We reuse the ftp server IP address instead.  For unusual
code requiring the old behavior, set a ‘trust_server_pasv_ipv4_address’
attribute on your FTP instance to ‘True’.  (See gh-87451(1))

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/87451


File: python.info,  Node: Python 3 8 10 中顯著的變更,  Next: Python 3 8 10 中顯著的變更<2>,  Prev: Python 3 8 9 中顯著的變更,  Up: Python 3 8 有什麼新功能

1.6.16 Python 3.8.10 中顯著的變更
---------------------------------

* Menu:

* macOS 11.0 (Big Sur) and Apple Silicon Mac support: macOS 11 0 Big Sur and Apple Silicon Mac support<2>.


File: python.info,  Node: macOS 11 0 Big Sur and Apple Silicon Mac support<2>,  Up: Python 3 8 10 中顯著的變更

1.6.16.1 macOS 11.0 (Big Sur) and Apple Silicon Mac support
...........................................................

As of 3.8.10, Python now supports building and running on macOS 11 (Big
Sur) and on Apple Silicon Macs (based on the ‘ARM64’ architecture).  A
new universal build variant, ‘universal2’, is now available to natively
support both ‘ARM64’ and ‘Intel 64’ in one set of executables.  Note
that support for "weaklinking", building binaries targeted for newer
versions of macOS that will also run correctly on older versions by
testing at runtime for missing features, is not included in this
backport from Python 3.9; to support a range of macOS versions, continue
to target for and build on the oldest version in the range.

(Originally contributed by Ronald Oussoren and Lawrence D'Anna in
gh-85272(1), with fixes by FX Coudert and Eli Rykoff, and backported to
3.8 by Maxime Bélanger and Ned Deily)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/85272


File: python.info,  Node: Python 3 8 10 中顯著的變更<2>,  Next: Python 3 8 12 中顯著的變更,  Prev: Python 3 8 10 中顯著的變更,  Up: Python 3 8 有什麼新功能

1.6.17 Python 3.8.10 中顯著的變更
---------------------------------

* Menu:

* urllib.parse: urllib parse<4>.


File: python.info,  Node: urllib parse<4>,  Up: Python 3 8 10 中顯著的變更<2>

1.6.17.1 urllib.parse
.....................

The presence of newline or tab characters in parts of a URL allows for
some forms of attacks.  Following the WHATWG specification that updates
RFC 3986(1), ASCII newline ‘\n’, ‘\r’ and tab ‘\t’ characters are
stripped from the URL by the parser in *note urllib.parse: f3.
preventing such attacks.  The removal characters are controlled by a new
module level variable ‘urllib.parse._UNSAFE_URL_BYTES_TO_REMOVE’.  (See
bpo-43882(2))

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc3986.html

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43882


File: python.info,  Node: Python 3 8 12 中顯著的變更,  Next: Notable security feature in 3 8 14,  Prev: Python 3 8 10 中顯著的變更<2>,  Up: Python 3 8 有什麼新功能

1.6.18 Python 3.8.12 中顯著的變更
---------------------------------

* Menu:

* Changes in the Python API: Changes in the Python API<4>.


File: python.info,  Node: Changes in the Python API<4>,  Up: Python 3 8 12 中顯著的變更

1.6.18.1 Changes in the Python API
..................................

Starting with Python 3.8.12 the *note ipaddress: 74. module no longer
accepts any leading zeros in IPv4 address strings.  Leading zeros are
ambiguous and interpreted as octal notation by some libraries.  For
example the legacy function *note socket.inet_aton(): 905. treats
leading zeros as octal notation.  glibc implementation of modern *note
inet_pton(): 906. does not accept any leading zeros.

(Originally contributed by Christian Heimes in bpo-36384(1), and
backported to 3.8 by Achraf Merzouki.)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36384


File: python.info,  Node: Notable security feature in 3 8 14,  Next: Notable changes in 3 8 17,  Prev: Python 3 8 12 中顯著的變更,  Up: Python 3 8 有什麼新功能

1.6.19 Notable security feature in 3.8.14
-----------------------------------------

Converting between *note int: 23c. and *note str: 3f2. in bases other
than 2 (binary), 4, 8 (octal), 16 (hexadecimal), or 32 such as base 10
(decimal) now raises a *note ValueError: 1e7. if the number of digits in
string form is above a limit to avoid potential denial of service
attacks due to the algorithmic complexity.  This is a mitigation for
CVE-2020-10735(1).  This limit can be configured or disabled by
environment variable, command line flag, or *note sys: c3. APIs.  See
the *note integer string conversion length limitation: 599.
documentation.  The default limit is 4300 digits in string form.

   ---------- Footnotes ----------

   (1) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10735


File: python.info,  Node: Notable changes in 3 8 17,  Prev: Notable security feature in 3 8 14,  Up: Python 3 8 有什麼新功能

1.6.20 Notable changes in 3.8.17
--------------------------------

* Menu:

* tarfile: tarfile<5>.


File: python.info,  Node: tarfile<5>,  Up: Notable changes in 3 8 17

1.6.20.1 tarfile
................

   * The extraction methods in *note tarfile: c8, and *note
     shutil.unpack_archive(): 412, 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
     *note Extraction filters: 413. for details.  In Python 3.12, use
     without the 'filter' argument will show a *note DeprecationWarning:
     18b.  In Python 3.14, the default will switch to ‘'data'’.
     (Contributed by Petr Viktorin in PEP 706(1).)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0706/


File: python.info,  Node: Python 3 7 有什麼新功能,  Next: Python 3 6 有什麼新功能,  Prev: Python 3 8 有什麼新功能,  Up: Python 有什麼新功能？

1.7 Python 3.7 有什麼新功能
===========================


編輯者: Elvis Pranskevichus <<elvis@magic.io>>

This article explains the new features in Python 3.7, compared to 3.6.
Python 3.7 was released on June 27, 2018.  For full details, see the
*note changelog: 122.

* Menu:

* Summary: Summary -- Release Highlights<2>. Release Highlights
* New Features: New Features<6>.
* 其他語言更動: 其他語言更動<6>.
* 新模組: 新模組<3>.
* 改進的模組: 改進的模組<6>.
* C API 變更: C API 變更<5>.
* 建置變更: 建置變更<5>.
* 最佳化: 最佳化<6>.
* Other CPython Implementation Changes::
* Deprecated Python Behavior::
* Deprecated Python modules, functions and methods: Deprecated Python modules functions and methods.
* Deprecated functions and types of the C API::
* Platform Support Removals::
* API and Feature Removals: API and Feature Removals<2>.
* Module Removals::
* Windows-only Changes::
* Porting to Python 3.7: Porting to Python 3 7.
* Python 3.7.1 中顯著的變更: Python 3 7 1 中顯著的變更.
* Python 3.7.2 中顯著的變更: Python 3 7 2 中顯著的變更.
* Python 3.7.6 中顯著的變更: Python 3 7 6 中顯著的變更.
* Python 3.7.10 中顯著的變更: Python 3 7 10 中顯著的變更.
* Python 3.7.11 中顯著的變更: Python 3 7 11 中顯著的變更.
* Notable security feature in 3.7.14: Notable security feature in 3 7 14.


File: python.info,  Node: Summary -- Release Highlights<2>,  Next: New Features<6>,  Up: Python 3 7 有什麼新功能

1.7.1 Summary - Release Highlights
----------------------------------

新增語法特性：

   * *note PEP 563: a62, postponed evaluation of type annotations.

Backwards incompatible syntax changes:

   * *note async: 6d6. 和 *note await: 19f. 現為保留關鍵字。

New library modules:

   * *note contextvars: 1d.: *note PEP 567 - Context Variables: a63.

   * *note dataclasses: 27.: *note PEP 557 - Data Classes: a64.

   * *note importlib.resources: a65.

New built-in features:

   * *note PEP 553: a66, the new *note breakpoint(): 219. function.

Python data model improvements:

   * *note PEP 562: a67, customization of access to module attributes.

   * *note PEP 560: a68, core support for typing module and generic
     types.

   * the insertion-order preservation nature of *note dict: a69. objects
     has been declared(1) to be an official part of the Python language
     spec.

Significant improvements in the standard library:

   * The *note asyncio: 8. module has received new features, significant
     *note usability and performance improvements: a6a.

   * The *note time: d7. module gained support for *note functions with
     nanosecond resolution: a6b.

CPython implementation improvements:

   * Avoiding the use of ASCII as a default text encoding:

        * *note PEP 538: a6c, legacy C locale coercion

        * *note PEP 540: a6d, forced UTF-8 runtime mode

   * *note PEP 552: a6e, deterministic .pycs

   * *note 新版 Python 開發模式: a6f.

   * *note PEP 565: a70, improved *note DeprecationWarning: 18b.
     handling

C API 改進：

   * *note PEP 539: a71, new C API for thread-local storage

Documentation improvements:

   * *note PEP 545: a72, Python documentation translations

   * New documentation translations: Japanese(2), French(3), and
     Korean(4).

This release features notable performance improvements in many areas.
The *note 最佳化: a73. section lists them in detail.

For a list of changes that may affect compatibility with previous Python
releases please refer to the *note Porting to Python 3.7: a74. section.

   ---------- Footnotes ----------

   (1) 
https://mail.python.org/pipermail/python-dev/2017-December/151283.html

   (2) https://docs.python.org/ja/

   (3) https://docs.python.org/fr/

   (4) https://docs.python.org/ko/


File: python.info,  Node: New Features<6>,  Next: 其他語言更動<6>,  Prev: Summary -- Release Highlights<2>,  Up: Python 3 7 有什麼新功能

1.7.2 New Features
------------------

* Menu:

* PEP 563; Postponed Evaluation of Annotations: PEP 563 Postponed Evaluation of Annotations.
* PEP 538; Legacy C Locale Coercion: PEP 538 Legacy C Locale Coercion.
* PEP 540; Forced UTF-8 Runtime Mode: PEP 540 Forced UTF-8 Runtime Mode.
* PEP 553; Built-in breakpoint(): PEP 553 Built-in breakpoint.
* PEP 539; New C API for Thread-Local Storage: PEP 539 New C API for Thread-Local Storage.
* PEP 562; Customization of Access to Module Attributes: PEP 562 Customization of Access to Module Attributes.
* PEP 564; New Time Functions With Nanosecond Resolution: PEP 564 New Time Functions With Nanosecond Resolution.
* PEP 565; Show DeprecationWarning in __main__: PEP 565 Show DeprecationWarning in __main__.
* PEP 560; Core Support for typing module and Generic Types: PEP 560 Core Support for typing module and Generic Types.
* PEP 552; Hash-based .pyc Files: PEP 552 Hash-based pyc Files.
* PEP 545：Python 文件翻譯::
* Python Development Mode (-X dev): Python Development Mode -X dev.


File: python.info,  Node: PEP 563 Postponed Evaluation of Annotations,  Next: PEP 538 Legacy C Locale Coercion,  Up: New Features<6>

1.7.2.1 PEP 563: Postponed Evaluation of Annotations
....................................................

The advent of type hints in Python uncovered two glaring usability
issues with the functionality of annotations added in PEP 3107(1) and
refined further in PEP 526(2):

   * annotations could only use names which were already available in
     the current scope, in other words they didn't support forward
     references of any kind; and

   * annotating source code had adverse effects on startup time of
     Python programs.

Both of these issues are fixed by postponing the evaluation of
annotations.  Instead of compiling code which executes expressions in
annotations at their definition time, the compiler stores the annotation
in a string form equivalent to the AST of the expression in question.
If needed, annotations can be resolved at runtime using *note
typing.get_type_hints(): 657.  In the common case where this is not
required, the annotations are cheaper to store (since short strings are
interned by the interpreter) and make startup time faster.

Usability-wise, annotations now support forward references, making the
following syntax valid:

     class C:
         @classmethod
         def from_string(cls, source: str) -> C:
             ...

         def validate_b(self, obj: B) -> bool:
             ...

     class B:
         ...

Since this change breaks compatibility, the new behavior needs to be
enabled on a per-module basis in Python 3.7 using a *note __future__: 0.
import:

     from __future__ import annotations

It will become the default in Python 3.10.

也參考
......

PEP 563(3) - Postponed evaluation of annotations

     PEP written and implemented by Łukasz Langa.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3107/

   (2) https://peps.python.org/pep-0526/

   (3) https://peps.python.org/pep-0563/


File: python.info,  Node: PEP 538 Legacy C Locale Coercion,  Next: PEP 540 Forced UTF-8 Runtime Mode,  Prev: PEP 563 Postponed Evaluation of Annotations,  Up: New Features<6>

1.7.2.2 PEP 538: Legacy C Locale Coercion
.........................................

An ongoing challenge within the Python 3 series has been determining a
sensible default strategy for handling the "7-bit ASCII" text encoding
assumption currently implied by the use of the default C or POSIX locale
on non-Windows platforms.

PEP 538(1) updates the default interpreter command line interface to
automatically coerce that locale to an available UTF-8 based locale as
described in the documentation of the new *note PYTHONCOERCECLOCALE:
a78. environment variable.  Automatically setting ‘LC_CTYPE’ this way
means that both the core interpreter and locale-aware C extensions (such
as *note readline: a8.) will assume the use of UTF-8 as the default text
encoding, rather than ASCII.

The platform support definition in PEP 11(2) has also been updated to
limit full text handling support to suitably configured non-ASCII based
locales.

As part of this change, the default error handler for *note stdin: 4e2.
and *note stdout: a79. is now ‘surrogateescape’ (rather than ‘strict’)
when using any of the defined coercion target locales (currently
‘C.UTF-8’, ‘C.utf8’, and ‘UTF-8’).  The default error handler for *note
stderr: 8dd. continues to be ‘backslashreplace’, regardless of locale.

Locale coercion is silent by default, but to assist in debugging
potentially locale related integration problems, explicit warnings
(emitted directly on *note stderr: 8dd.) can be requested by setting
‘PYTHONCOERCECLOCALE=warn’.  This setting will also cause the Python
runtime to emit a warning if the legacy C locale remains active when the
core interpreter is initialized.

While PEP 538(3)'s locale coercion has the benefit of also affecting
extension modules (such as GNU ‘readline’), as well as child processes
(including those running non-Python applications and older versions of
Python), it has the downside of requiring that a suitable target locale
be present on the running system.  To better handle the case where no
suitable target locale is available (as occurs on RHEL/CentOS 7, for
example), Python 3.7 also implements *note PEP 540; Forced UTF-8 Runtime
Mode: a6d.

也參考
......

PEP 538(4) - Coercing the legacy C locale to a UTF-8 based locale

     由 Nick Coghlan 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0538/

   (2) https://peps.python.org/pep-0011/

   (3) https://peps.python.org/pep-0538/

   (4) https://peps.python.org/pep-0538/


File: python.info,  Node: PEP 540 Forced UTF-8 Runtime Mode,  Next: PEP 553 Built-in breakpoint,  Prev: PEP 538 Legacy C Locale Coercion,  Up: New Features<6>

1.7.2.3 PEP 540: Forced UTF-8 Runtime Mode
..........................................

The new *note -X: 15a. ‘utf8’ command line option and *note PYTHONUTF8:
a7b. environment variable can be used to enable the *note Python UTF-8
Mode: 5fc.

When in UTF-8 mode, CPython ignores the locale settings, and uses the
UTF-8 encoding by default.  The error handlers for *note sys.stdin: 4e2.
and *note sys.stdout: a79. streams are set to ‘surrogateescape’.

The forced UTF-8 mode can be used to change the text handling behavior
in an embedded Python interpreter without changing the locale settings
of an embedding application.

While PEP 540(1)'s UTF-8 mode has the benefit of working regardless of
which locales are available on the running system, it has the downside
of having no effect on extension modules (such as GNU ‘readline’), child
processes running non-Python applications, and child processes running
older versions of Python.  To reduce the risk of corrupting text data
when communicating with such components, Python 3.7 also implements
*note PEP 540; Forced UTF-8 Runtime Mode: a6d.).

The UTF-8 mode is enabled by default when the locale is ‘C’ or ‘POSIX’,
and the PEP 538(2) locale coercion feature fails to change it to a UTF-8
based alternative (whether that failure is due to
‘PYTHONCOERCECLOCALE=0’ being set, ‘LC_ALL’ being set, or the lack of a
suitable target locale).

也參考
......

PEP 540(3) - Add a new UTF-8 mode

     由 Victor Stinner 撰寫 PEP 與實作

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0540/

   (2) https://peps.python.org/pep-0538/

   (3) https://peps.python.org/pep-0540/


File: python.info,  Node: PEP 553 Built-in breakpoint,  Next: PEP 539 New C API for Thread-Local Storage,  Prev: PEP 540 Forced UTF-8 Runtime Mode,  Up: New Features<6>

1.7.2.4 PEP 553: Built-in ‘breakpoint()’
........................................

Python 3.7 includes the new built-in *note breakpoint(): 219. function
as an easy and consistent way to enter the Python debugger.

Built-in ‘breakpoint()’ calls *note sys.breakpointhook(): a7d.  By
default, the latter imports *note pdb: 94. and then calls
‘pdb.set_trace()’, but by binding ‘sys.breakpointhook()’ to the function
of your choosing, ‘breakpoint()’ can enter any debugger.  Additionally,
the environment variable *note PYTHONBREAKPOINT: a7e. can be set to the
callable of your debugger of choice.  Set ‘PYTHONBREAKPOINT=0’ to
completely disable built-in ‘breakpoint()’.

也參考
......

PEP 553(1) - Built-in breakpoint()

     由 Barry Warsaw 撰寫 PEP 與實作

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0553/


File: python.info,  Node: PEP 539 New C API for Thread-Local Storage,  Next: PEP 562 Customization of Access to Module Attributes,  Prev: PEP 553 Built-in breakpoint,  Up: New Features<6>

1.7.2.5 PEP 539: New C API for Thread-Local Storage
...................................................

While Python provides a C API for thread-local storage support; the
existing *note Thread Local Storage (TLS) API: a80. has used int to
represent TLS keys across all platforms.  This has not generally been a
problem for officially support platforms, but that is neither
POSIX-compliant, nor portable in any practical sense.

PEP 539(1) changes this by providing a new *note Thread Specific Storage
(TSS) API: a81. to CPython which supersedes use of the existing TLS API
within the CPython interpreter, while deprecating the existing API. The
TSS API uses a new type *note Py_tss_t: a82. instead of int to represent
TSS keys-an opaque type the definition of which may depend on the
underlying TLS implementation.  Therefore, this will allow to build
CPython on platforms where the native TLS key is defined in a way that
cannot be safely cast to int.

Note that on platforms where the native TLS key is defined in a way that
cannot be safely cast to int, all functions of the existing TLS API will
be no-op and immediately return failure.  This indicates clearly that
the old API is not supported on platforms where it cannot be used
reliably, and that no effort will be made to add such support.

也參考
......

PEP 539(2) - A New C-API for Thread-Local Storage in CPython

     PEP 由 Erik M. Bray 撰寫；由 Masayuki Yamamoto 實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0539/

   (2) https://peps.python.org/pep-0539/


File: python.info,  Node: PEP 562 Customization of Access to Module Attributes,  Next: PEP 564 New Time Functions With Nanosecond Resolution,  Prev: PEP 539 New C API for Thread-Local Storage,  Up: New Features<6>

1.7.2.6 PEP 562: Customization of Access to Module Attributes
.............................................................

Python 3.7 allows defining ‘__getattr__()’ on modules and will call it
whenever a module attribute is otherwise not found.  Defining
‘__dir__()’ on modules is now also allowed.

A typical example of where this may be useful is module attribute
deprecation and lazy loading.

也參考
......

PEP 562(1) - ‘__getattr__’ 與 ‘__dir__’ 模組

     由 Ivan Levkivskyi 撰寫 PEP 與實作

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0562/


File: python.info,  Node: PEP 564 New Time Functions With Nanosecond Resolution,  Next: PEP 565 Show DeprecationWarning in __main__,  Prev: PEP 562 Customization of Access to Module Attributes,  Up: New Features<6>

1.7.2.7 PEP 564: New Time Functions With Nanosecond Resolution
..............................................................

The resolution of clocks in modern systems can exceed the limited
precision of a floating-point number returned by the *note time.time():
239. function and its variants.  To avoid loss of precision, PEP 564(1)
adds six new "nanosecond" variants of the existing timer functions to
the *note time: d7. module:

   * *note time.clock_gettime_ns(): a85.

   * *note time.clock_settime_ns(): a86.

   * *note time.monotonic_ns(): a87.

   * *note time.perf_counter_ns(): a88.

   * *note time.process_time_ns(): a89.

   * *note time.time_ns(): a8a.

The new functions return the number of nanoseconds as an integer value.

Measurements(2) show that on Linux and Windows the resolution of *note
time.time_ns(): a8a. is approximately 3 times better than that of *note
time.time(): 239.

也參考
......

PEP 564(3) - Add new time functions with nanosecond resolution

     由 Victor Stinner 撰寫 PEP 與實作

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0564/

   (2) 
https://peps.python.org/pep-0564/#annex-clocks-resolution-in-python

   (3) https://peps.python.org/pep-0564/


File: python.info,  Node: PEP 565 Show DeprecationWarning in __main__,  Next: PEP 560 Core Support for typing module and Generic Types,  Prev: PEP 564 New Time Functions With Nanosecond Resolution,  Up: New Features<6>

1.7.2.8 PEP 565: Show DeprecationWarning in ‘__main__’
......................................................

The default handling of *note DeprecationWarning: 18b. has been changed
such that these warnings are once more shown by default, but only when
the code triggering them is running directly in the *note __main__: 1.
module.  As a result, developers of single file scripts and those using
Python interactively should once again start seeing deprecation warnings
for the APIs they use, but deprecation warnings triggered by imported
application, library and framework modules will continue to be hidden by
default.

As a result of this change, the standard library now allows developers
to choose between three different deprecation warning behaviours:

   * *note FutureWarning: 357.: always displayed by default, recommended
     for warnings intended to be seen by application end users (e.g.
     for deprecated application configuration settings).

   * *note DeprecationWarning: 18b.: displayed by default only in *note
     __main__: 1. and when running tests, recommended for warnings
     intended to be seen by other Python developers where a version
     upgrade may result in changed behaviour or an error.

   * *note PendingDeprecationWarning: 86d.: displayed by default only
     when running tests, intended for cases where a future version
     upgrade will change the warning category to *note
     DeprecationWarning: 18b. or *note FutureWarning: 357.

Previously both *note DeprecationWarning: 18b. and *note
PendingDeprecationWarning: 86d. were only visible when running tests,
which meant that developers primarily writing single file scripts or
using Python interactively could be surprised by breaking changes in the
APIs they used.

也參考
......

PEP 565(1) - Show DeprecationWarning in ‘__main__’

     由 Nick Coghlan 撰寫 PEP 與實作

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0565/


File: python.info,  Node: PEP 560 Core Support for typing module and Generic Types,  Next: PEP 552 Hash-based pyc Files,  Prev: PEP 565 Show DeprecationWarning in __main__,  Up: New Features<6>

1.7.2.9 PEP 560: Core Support for ‘typing’ module and Generic Types
...................................................................

Initially PEP 484(1) was designed in such way that it would not
introduce 'any' changes to the core CPython interpreter.  Now type hints
and the *note typing: ed. module are extensively used by the community,
so this restriction is removed.  The PEP introduces two special methods
‘__class_getitem__()’ and ‘__mro_entries__’, these methods are now used
by most classes and special constructs in *note typing: ed.  As a
result, the speed of various operations with types increased up to 7
times, the generic types can be used without metaclass conflicts, and
several long standing bugs in *note typing: ed. module are fixed.

也參考
......

PEP 560(2) - Core support for typing module and generic types

     由 Ivan Levkivskyi 撰寫 PEP 與實作

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0484/

   (2) https://peps.python.org/pep-0560/


File: python.info,  Node: PEP 552 Hash-based pyc Files,  Next: PEP 545：Python 文件翻譯,  Prev: PEP 560 Core Support for typing module and Generic Types,  Up: New Features<6>

1.7.2.10 PEP 552: Hash-based .pyc Files
.......................................

Python has traditionally checked the up-to-dateness of bytecode cache
files (i.e., ‘.pyc’ files) by comparing the source metadata
(last-modified timestamp and size) with source metadata saved in the
cache file header when it was generated.  While effective, this
invalidation method has its drawbacks.  When filesystem timestamps are
too coarse, Python can miss source updates, leading to user confusion.
Additionally, having a timestamp in the cache file is problematic for
build reproducibility(1) and content-based build systems.

PEP 552(2) extends the pyc format to allow the hash of the source file
to be used for invalidation instead of the source timestamp.  Such
‘.pyc’ files are called "hash-based".  By default, Python still uses
timestamp-based invalidation and does not generate hash-based ‘.pyc’
files at runtime.  Hash-based ‘.pyc’ files may be generated with *note
py_compile: a1. or *note compileall: 19.

Hash-based ‘.pyc’ files come in two variants: checked and unchecked.
Python validates checked hash-based ‘.pyc’ files against the
corresponding source files at runtime but doesn't do so for unchecked
hash-based pycs.  Unchecked hash-based ‘.pyc’ files are a useful
performance optimization for environments where a system external to
Python (e.g., the build system) is responsible for keeping ‘.pyc’ files
up-to-date.

更多資訊請見 *note Cached bytecode invalidation: 590.。

也參考
......

PEP 552(3) - Deterministic pycs

     由 Benjamin Peterson 撰寫 PEP 與實作

   ---------- Footnotes ----------

   (1) https://reproducible-builds.org/

   (2) https://peps.python.org/pep-0552/

   (3) https://peps.python.org/pep-0552/


File: python.info,  Node: PEP 545：Python 文件翻譯,  Next: Python Development Mode -X dev,  Prev: PEP 552 Hash-based pyc Files,  Up: New Features<6>

1.7.2.11 PEP 545：Python 文件翻譯
.................................

PEP 545(1) describes the process of creating and maintaining Python
documentation translations.

Three new translations have been added:

   - 日文：‘https://docs.python.org/ja/’

   - 法文：‘https://docs.python.org/fr/’

   - 韓文：‘https://docs.python.org/ko/’

也參考
......

PEP 545(2) - Python 文件翻譯

     PEP 由 Julien Palard、Inada Naoki 與 Victor Stinner 撰寫。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0545/

   (2) https://peps.python.org/pep-0545/


File: python.info,  Node: Python Development Mode -X dev,  Prev: PEP 545：Python 文件翻譯,  Up: New Features<6>

1.7.2.12 Python Development Mode (-X dev)
.........................................

The new *note -X: 15a. ‘dev’ command line option or the new *note
PYTHONDEVMODE: a90. environment variable can be used to enable *note
Python Development Mode: 1dd.  When in development mode, Python performs
additional runtime checks that are too expensive to be enabled by
default.  See *note Python Development Mode: 1dd. documentation for the
full description.


File: python.info,  Node: 其他語言更動<6>,  Next: 新模組<3>,  Prev: New Features<6>,  Up: Python 3 7 有什麼新功能

1.7.3 其他語言更動
------------------

   * An *note await: 19f. expression and comprehensions containing an
     *note async for: a4e. clause were illegal in the expressions in
     *note formatted string literals: 94d. due to a problem with the
     implementation.  In Python 3.7 this restriction was lifted.

   * More than 255 arguments can now be passed to a function, and a
     function can now have more than 255 parameters.  (Contributed by
     Serhiy Storchaka in bpo-12844(1) and bpo-18896(2).)

   * *note bytes.fromhex(): a92. and *note bytearray.fromhex(): a93. now
     ignore all ASCII whitespace, not only spaces.  (Contributed by
     Robert Xiao in bpo-28927(3).)

   * *note str: 3f2, *note bytes: 1a5, and *note bytearray: 4e3. gained
     support for the new *note isascii(): a94. method, which can be used
     to test if a string or bytes contain only the ASCII characters.
     (Contributed by INADA Naoki in bpo-32677(4).)

   * *note ImportError: 352. now displays module name and module
     ‘__file__’ path when ‘from ... import ...’ fails.  (Contributed by
     Matthias Bussonnier in bpo-29546(5).)

   * Circular imports involving absolute imports with binding a
     submodule to a name are now supported.  (Contributed by Serhiy
     Storchaka in bpo-30024(6).)

   * ‘object.__format__(x, '')’ is now equivalent to ‘str(x)’ rather
     than ‘format(str(self), '')’.  (Contributed by Serhiy Storchaka in
     bpo-28974(7).)

   * In order to better support dynamic creation of stack traces, *note
     types.TracebackType: a95. can now be instantiated from Python code,
     and the *note tb_next: a96. attribute on *note tracebacks: a97. is
     now writable.  (Contributed by Nathaniel J. Smith in bpo-30579(8).)

   * When using the *note -m: 585. switch, ‘sys.path[0]’ is now eagerly
     expanded to the full starting directory path, rather than being
     left as the empty directory (which allows imports from the
     'current' working directory at the time when an import occurs)
     (Contributed by Nick Coghlan in bpo-33053(9).)

   * The new *note -X: 15a. ‘importtime’ option or the *note
     PYTHONPROFILEIMPORTTIME: a98. environment variable can be used to
     show the timing of each module import.  (Contributed by Inada Naoki
     in bpo-31415(10).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=12844

   (2) https://bugs.python.org/issue?@action=redirect&bpo=18896

   (3) https://bugs.python.org/issue?@action=redirect&bpo=28927

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32677

   (5) https://bugs.python.org/issue?@action=redirect&bpo=29546

   (6) https://bugs.python.org/issue?@action=redirect&bpo=30024

   (7) https://bugs.python.org/issue?@action=redirect&bpo=28974

   (8) https://bugs.python.org/issue?@action=redirect&bpo=30579

   (9) https://bugs.python.org/issue?@action=redirect&bpo=33053

   (10) https://bugs.python.org/issue?@action=redirect&bpo=31415


File: python.info,  Node: 新模組<3>,  Next: 改進的模組<6>,  Prev: 其他語言更動<6>,  Up: Python 3 7 有什麼新功能

1.7.4 新模組
------------

* Menu:

* contextvars::
* dataclasses: dataclasses<3>.
* importlib.resources: importlib resources<2>.


File: python.info,  Node: contextvars,  Next: dataclasses<3>,  Up: 新模組<3>

1.7.4.1 contextvars
...................

The new *note contextvars: 1d. module and a set of *note new C APIs:
a9b. introduce support for 'context variables'.  Context variables are
conceptually similar to thread-local variables.  Unlike TLS, context
variables support asynchronous code correctly.

The *note asyncio: 8. and *note decimal: 2e. modules have been updated
to use and support context variables out of the box.  Particularly the
active decimal context is now stored in a context variable, which allows
decimal operations to work with the correct context in asynchronous
code.

也參考
......

PEP 567(1) - Context Variables

     由 Yury Selivanov 撰寫 PEP 與實作

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0567/


File: python.info,  Node: dataclasses<3>,  Next: importlib resources<2>,  Prev: contextvars,  Up: 新模組<3>

1.7.4.2 dataclasses
...................

The new *note dataclass(): 1af. decorator provides a way to declare
'data classes'.  A data class describes its attributes using class
variable annotations.  Its constructor and other magic methods, such as
*note __repr__(): 5c2, *note __eq__(): a9d, and *note __hash__(): a9e.
are generated automatically.

範例：

     @dataclass
     class Point:
         x: float
         y: float
         z: float = 0.0

     p = Point(1.5, 2.5)
     print(p)   # produces "Point(x=1.5, y=2.5, z=0.0)"

也參考
......

PEP 557(1) - Data Classes

     由 Eric V. Smith 撰寫 PEP 與實作

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0557/


File: python.info,  Node: importlib resources<2>,  Prev: dataclasses<3>,  Up: 新模組<3>

1.7.4.3 importlib.resources
...........................

The new *note importlib.resources: 6f. module provides several new APIs
and one new ABC for access to, opening, and reading 'resources' inside
packages.  Resources are roughly similar to files inside packages, but
they needn't be actual files on the physical file system.  Module
loaders can provide a ‘get_resource_reader()’ function which returns a
*note importlib.abc.ResourceReader: aa0. instance to support this new
API. Built-in file path loaders and zip file loaders both support this.

Contributed by Barry Warsaw and Brett Cannon in bpo-32248(1).

也參考
......

importlib_resources(2) - a PyPI backport for earlier Python versions.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32248

   (2) https://importlib-resources.readthedocs.io/en/latest/


File: python.info,  Node: 改進的模組<6>,  Next: C API 變更<5>,  Prev: 新模組<3>,  Up: Python 3 7 有什麼新功能

1.7.5 改進的模組
----------------

* Menu:

* argparse: argparse<3>.
* asyncio: asyncio<7>.
* binascii::
* calendar: calendar<2>.
* collections: collections<2>.
* compileall: compileall<3>.
* concurrent.futures: concurrent futures<3>.
* contextlib: contextlib<3>.
* cProfile: cProfile<2>.
* crypt::
* datetime: datetime<4>.
* dbm: dbm<2>.
* decimal::
* dis: dis<3>.
* distutils: distutils<4>.
* enum: enum<4>.
* functools: functools<3>.
* gc: gc<5>.
* hmac: hmac<2>.
* http.client: http client.
* http.server: http server.
* idlelib and IDLE::
* importlib: importlib<4>.
* io: io<4>.
* ipaddress: ipaddress<3>.
* itertools: itertools<5>.
* locale: locale<4>.
* logging: logging<3>.
* math: math<6>.
* mimetypes: mimetypes<2>.
* msilib::
* multiprocessing: multiprocessing<4>.
* os: os<7>.
* pathlib: pathlib<8>.
* pdb: pdb<4>.
* py_compile: py_compile<3>.
* pydoc: pydoc<2>.
* queue: queue<2>.
* re: re<4>.
* signal: signal<2>.
* socket: socket<5>.
* socketserver::
* sqlite3: sqlite3<6>.
* ssl: ssl<5>.
* string: string<2>.
* subprocess: subprocess<2>.
* sys: sys<7>.
* time: time<5>.
* tkinter: tkinter<5>.
* tracemalloc: tracemalloc<2>.
* types: types<4>.
* unicodedata: unicodedata<6>.
* unittest: unittest<7>.
* unittest.mock: unittest mock.
* urllib.parse: urllib parse<5>.
* uu::
* uuid: uuid<2>.
* warnings: warnings<3>.
* xml: xml<5>.
* xml.etree: xml etree.
* xmlrpc.server: xmlrpc server.
* zipapp::
* zipfile: zipfile<2>.


File: python.info,  Node: argparse<3>,  Next: asyncio<7>,  Up: 改進的模組<6>

1.7.5.1 argparse
................

The new *note ArgumentParser.parse_intermixed_args(): aa3. method allows
intermixing options and positional arguments.  (Contributed by paul.j3
in bpo-14191(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=14191


File: python.info,  Node: asyncio<7>,  Next: binascii,  Prev: argparse<3>,  Up: 改進的模組<6>

1.7.5.2 asyncio
...............

The *note asyncio: 8. module has received many new features, usability
and *note performance improvements: aa5.  Notable changes include:

   * The new *note provisional: aa6. *note asyncio.run(): 423. function
     can be used to run a coroutine from synchronous code by
     automatically creating and destroying the event loop.  (Contributed
     by Yury Selivanov in bpo-32314(1).)

   * asyncio gained support for *note contextvars: 1d.  *note
     loop.call_soon(): aa7, *note loop.call_soon_threadsafe(): aa8,
     *note loop.call_later(): aa9, *note loop.call_at(): aaa, and *note
     Future.add_done_callback(): aab. have a new optional keyword-only
     'context' parameter.  *note Tasks: 480. now track their context
     automatically.  See PEP 567(2) for more details.  (Contributed by
     Yury Selivanov in bpo-32436(3).)

   * The new *note asyncio.create_task(): 5a1. function has been added
     as a shortcut to ‘asyncio.get_event_loop().create_task()’.
     (Contributed by Andrew Svetlov in bpo-32311(4).)

   * The new *note loop.start_tls(): aac. method can be used to upgrade
     an existing connection to TLS. (Contributed by Yury Selivanov in
     bpo-23749(5).)

   * The new *note loop.sock_recv_into(): aad. method allows reading
     data from a socket directly into a provided buffer making it
     possible to reduce data copies.  (Contributed by Antoine Pitrou in
     bpo-31819(6).)

   * The new *note asyncio.current_task(): 424. function returns the
     currently running *note Task: 480. instance, and the new *note
     asyncio.all_tasks(): 8fa. function returns a set of all existing
     ‘Task’ instances in a given loop.  The ‘Task.current_task()’ and
     ‘Task.all_tasks()’ methods have been deprecated.  (Contributed by
     Andrew Svetlov in bpo-32250(7).)

   * The new 'provisional' *note BufferedProtocol: a40. class allows
     implementing streaming protocols with manual control over the
     receive buffer.  (Contributed by Yury Selivanov in bpo-32251(8).)

   * The new *note asyncio.get_running_loop(): aae. function returns the
     currently running loop, and raises a *note RuntimeError: 179. if no
     loop is running.  This is in contrast with *note
     asyncio.get_event_loop(): 2a3, which will 'create' a new event loop
     if none is running.  (Contributed by Yury Selivanov in
     bpo-32269(9).)

   * The new *note StreamWriter.wait_closed(): aaf. coroutine method
     allows waiting until the stream writer is closed.  The new *note
     StreamWriter.is_closing(): ab0. method can be used to determine if
     the writer is closing.  (Contributed by Andrew Svetlov in
     bpo-32391(10).)

   * The new *note loop.sock_sendfile(): ab1. coroutine method allows
     sending files using *note os.sendfile: ab2. when possible.
     (Contributed by Andrew Svetlov in bpo-32410(11).)

   * The new *note Future.get_loop(): ab3. and ‘Task.get_loop()’ methods
     return the instance of the loop on which a task or a future were
     created.  *note Server.get_loop(): ab4. allows doing the same for
     *note asyncio.Server: ab5. objects.  (Contributed by Yury Selivanov
     in bpo-32415(12) and Srinivas Reddy Thatiparthy in bpo-32418(13).)

   * It is now possible to control how instances of *note
     asyncio.Server: ab5. begin serving.  Previously, the server would
     start serving immediately when created.  The new 'start_serving'
     keyword argument to *note loop.create_server(): ab6. and *note
     loop.create_unix_server(): 194, as well as *note
     Server.start_serving(): ab7, and *note Server.serve_forever(): ab8.
     can be used to decouple server instantiation and serving.  The new
     *note Server.is_serving(): ab9. method returns ‘True’ if the server
     is serving.  *note Server: ab5. objects are now asynchronous
     context managers:

          srv = await loop.create_server(...)

          async with srv:
              # some code

          # At this point, srv is closed and no longer accepts new connections.

     （由 Yury Selivanov 在 bpo-32662(14) 中貢獻。）

   * Callback objects returned by *note loop.call_later(): aa9. gained
     the new *note when(): aba. method which returns an absolute
     scheduled callback timestamp.  (Contributed by Andrew Svetlov in
     bpo-32741(15).)

   * The *note loop.create_datagram_endpoint(): 6d7. method gained
     support for Unix sockets.  (Contributed by Quentin Dawans in
     bpo-31245(16).)

   * The *note asyncio.open_connection(): abb, *note
     asyncio.start_server(): abc. functions, *note
     loop.create_connection(): 5a8, *note loop.create_server(): ab6,
     *note loop.create_accepted_socket(): abd. methods and their
     corresponding UNIX socket variants now accept the
     'ssl_handshake_timeout' keyword argument.  (Contributed by Neil
     Aspinall in bpo-29970(17).)

   * The new *note Handle.cancelled(): abe. method returns ‘True’ if the
     callback was cancelled.  (Contributed by Marat Sharafutdinov in
     bpo-31943(18).)

   * The asyncio source has been converted to use the *note async:
     6d6./*note await: 19f. syntax.  (Contributed by Andrew Svetlov in
     bpo-32193(19).)

   * The new *note ReadTransport.is_reading(): abf. method can be used
     to determine the reading state of the transport.  Additionally,
     calls to *note ReadTransport.resume_reading(): ac0. and *note
     ReadTransport.pause_reading(): ac1. are now idempotent.
     (Contributed by Yury Selivanov in bpo-32356(20).)

   * Loop methods which accept socket paths now support passing *note
     path-like objects: ac2.  (Contributed by Yury Selivanov in
     bpo-32066(21).)

   * In *note asyncio: 8. TCP sockets on Linux are now created with
     ‘TCP_NODELAY’ flag set by default.  (Contributed by Yury Selivanov
     and Victor Stinner in bpo-27456(22).)

   * Exceptions occurring in cancelled tasks are no longer logged.
     (Contributed by Yury Selivanov in bpo-30508(23).)

   * New ‘WindowsSelectorEventLoopPolicy’ and
     ‘WindowsProactorEventLoopPolicy’ classes.  (Contributed by Yury
     Selivanov in bpo-33792(24).)

Several ‘asyncio’ APIs have been *note deprecated: ac3.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32314

   (2) https://peps.python.org/pep-0567/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32436

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32311

   (5) https://bugs.python.org/issue?@action=redirect&bpo=23749

   (6) https://bugs.python.org/issue?@action=redirect&bpo=31819

   (7) https://bugs.python.org/issue?@action=redirect&bpo=32250

   (8) https://bugs.python.org/issue?@action=redirect&bpo=32251

   (9) https://bugs.python.org/issue?@action=redirect&bpo=32269

   (10) https://bugs.python.org/issue?@action=redirect&bpo=32391

   (11) https://bugs.python.org/issue?@action=redirect&bpo=32410

   (12) https://bugs.python.org/issue?@action=redirect&bpo=32415

   (13) https://bugs.python.org/issue?@action=redirect&bpo=32418

   (14) https://bugs.python.org/issue?@action=redirect&bpo=32662

   (15) https://bugs.python.org/issue?@action=redirect&bpo=32741

   (16) https://bugs.python.org/issue?@action=redirect&bpo=31245

   (17) https://bugs.python.org/issue?@action=redirect&bpo=29970

   (18) https://bugs.python.org/issue?@action=redirect&bpo=31943

   (19) https://bugs.python.org/issue?@action=redirect&bpo=32193

   (20) https://bugs.python.org/issue?@action=redirect&bpo=32356

   (21) https://bugs.python.org/issue?@action=redirect&bpo=32066

   (22) https://bugs.python.org/issue?@action=redirect&bpo=27456

   (23) https://bugs.python.org/issue?@action=redirect&bpo=30508

   (24) https://bugs.python.org/issue?@action=redirect&bpo=33792


File: python.info,  Node: binascii,  Next: calendar<2>,  Prev: asyncio<7>,  Up: 改進的模組<6>

1.7.5.3 binascii
................

The *note b2a_uu(): ac5. function now accepts an optional 'backtick'
keyword argument.  When it's true, zeros are represented by ‘'`'’
instead of spaces.  (Contributed by Xiang Zhang in bpo-30103(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30103


File: python.info,  Node: calendar<2>,  Next: collections<2>,  Prev: binascii,  Up: 改進的模組<6>

1.7.5.4 calendar
................

The *note HTMLCalendar: ac7. class has new class attributes which ease
the customization of CSS classes in the produced HTML calendar.
(Contributed by Oz Tiram in bpo-30095(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30095


File: python.info,  Node: collections<2>,  Next: compileall<3>,  Prev: calendar<2>,  Up: 改進的模組<6>

1.7.5.5 collections
...................

‘collections.namedtuple()’ now supports default values.  (Contributed by
Raymond Hettinger in bpo-32320(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32320


File: python.info,  Node: compileall<3>,  Next: concurrent futures<3>,  Prev: collections<2>,  Up: 改進的模組<6>

1.7.5.6 compileall
..................

*note compileall.compile_dir(): aca. learned the new 'invalidation_mode'
parameter, which can be used to enable *note hash-based .pyc
invalidation: a6e.  The invalidation mode can also be specified on the
command line using the new ‘--invalidation-mode’ argument.  (Contributed
by Benjamin Peterson in bpo-31650(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31650


File: python.info,  Node: concurrent futures<3>,  Next: contextlib<3>,  Prev: compileall<3>,  Up: 改進的模組<6>

1.7.5.7 concurrent.futures
..........................

*note ProcessPoolExecutor: 893. and *note ThreadPoolExecutor: 6e6. now
support the new 'initializer' and 'initargs' constructor arguments.
(Contributed by Antoine Pitrou in bpo-21423(1).)

The *note ProcessPoolExecutor: 893. can now take the multiprocessing
context via the new 'mp_context' argument.  (Contributed by Thomas
Moreau in bpo-31540(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21423

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31540


File: python.info,  Node: contextlib<3>,  Next: cProfile<2>,  Prev: concurrent futures<3>,  Up: 改進的模組<6>

1.7.5.8 contextlib
..................

The new *note nullcontext(): 792. is a simpler and faster no-op context
manager than *note ExitStack: acd.  (Contributed by Jesse-Bakker in
bpo-10049(1).)

The new *note asynccontextmanager(): ace, *note
AbstractAsyncContextManager: acf, and *note AsyncExitStack: ad0. have
been added to complement their synchronous counterparts.  (Contributed
by Jelle Zijlstra in bpo-29679(2) and bpo-30241(3), and by Alexander
Mohr and Ilya Kulakov in bpo-29302(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=10049

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29679

   (3) https://bugs.python.org/issue?@action=redirect&bpo=30241

   (4) https://bugs.python.org/issue?@action=redirect&bpo=29302


File: python.info,  Node: cProfile<2>,  Next: crypt,  Prev: contextlib<3>,  Up: 改進的模組<6>

1.7.5.9 cProfile
................

The *note cProfile: 20. command line now accepts ‘-m module_name’ as an
alternative to script path.  (Contributed by Sanyam Khurana in
bpo-21862(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21862


File: python.info,  Node: crypt,  Next: datetime<4>,  Prev: cProfile<2>,  Up: 改進的模組<6>

1.7.5.10 crypt
..............

The ‘crypt’ module now supports the Blowfish hashing method.
(Contributed by Serhiy Storchaka in bpo-31664(1).)

The ‘mksalt()’ function now allows specifying the number of rounds for
hashing.  (Contributed by Serhiy Storchaka in bpo-31702(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31664

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31702


File: python.info,  Node: datetime<4>,  Next: dbm<2>,  Prev: crypt,  Up: 改進的模組<6>

1.7.5.11 datetime
.................

The new *note datetime.fromisoformat(): 5bc. method constructs a *note
datetime: 1b0. object from a string in one of the formats output by
*note datetime.isoformat(): ad4.  (Contributed by Paul Ganssle in
bpo-15873(1).)

The *note tzinfo: 582. class now supports sub-minute offsets.
(Contributed by Alexander Belopolsky in bpo-5288(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=15873

   (2) https://bugs.python.org/issue?@action=redirect&bpo=5288


File: python.info,  Node: dbm<2>,  Next: decimal,  Prev: datetime<4>,  Up: 改進的模組<6>

1.7.5.12 dbm
............

*note dbm.dumb: 2a. now supports reading read-only files and no longer
writes the index file when it is not changed.


File: python.info,  Node: decimal,  Next: dis<3>,  Prev: dbm<2>,  Up: 改進的模組<6>

1.7.5.13 decimal
................

The *note decimal: 2e. module now uses *note context variables: a63. to
store the decimal context.  (Contributed by Yury Selivanov in
bpo-32630(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32630


File: python.info,  Node: dis<3>,  Next: distutils<4>,  Prev: decimal,  Up: 改進的模組<6>

1.7.5.14 dis
............

The *note dis(): ad8. function is now able to disassemble nested code
objects (the code of comprehensions, generator expressions and nested
functions, and the code used for building nested classes).  The maximum
depth of disassembly recursion is controlled by the new 'depth'
parameter.  (Contributed by Serhiy Storchaka in bpo-11822(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=11822


File: python.info,  Node: distutils<4>,  Next: enum<4>,  Prev: dis<3>,  Up: 改進的模組<6>

1.7.5.15 distutils
..................

‘README.rst’ is now included in the list of distutils standard READMEs
and therefore included in source distributions.  (Contributed by Ryan
Gonzalez in bpo-11913(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=11913


File: python.info,  Node: enum<4>,  Next: functools<3>,  Prev: distutils<4>,  Up: 改進的模組<6>

1.7.5.16 enum
.............

The *note Enum: 5d6. learned the new ‘_ignore_’ class property, which
allows listing the names of properties which should not become enum
members.  (Contributed by Ethan Furman in bpo-31801(1).)

In Python 3.8, attempting to check for non-Enum objects in ‘Enum’
classes will raise a *note TypeError: 4dd. (e.g.  ‘1 in Color’);
similarly, attempting to check for non-Flag objects in a ‘Flag’ member
will raise *note TypeError: 4dd. (e.g.  ‘1 in Perm.RW’); currently, both
operations return *note False: adb. instead and are deprecated.
(Contributed by Ethan Furman in bpo-33217(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31801

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33217


File: python.info,  Node: functools<3>,  Next: gc<5>,  Prev: enum<4>,  Up: 改進的模組<6>

1.7.5.17 functools
..................

*note functools.singledispatch(): 5df. now supports registering
implementations using type annotations.  (Contributed by Łukasz Langa in
bpo-32227(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32227


File: python.info,  Node: gc<5>,  Next: hmac<2>,  Prev: functools<3>,  Up: 改進的模組<6>

1.7.5.18 gc
...........

The new *note gc.freeze(): ade. function allows freezing all objects
tracked by the garbage collector and excluding them from future
collections.  This can be used before a POSIX ‘fork()’ call to make the
GC copy-on-write friendly or to speed up collection.  The new *note
gc.unfreeze(): adf. functions reverses this operation.  Additionally,
*note gc.get_freeze_count(): ae0. can be used to obtain the number of
frozen objects.  (Contributed by Li Zekun in bpo-31558(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31558


File: python.info,  Node: hmac<2>,  Next: http client,  Prev: gc<5>,  Up: 改進的模組<6>

1.7.5.19 hmac
.............

The *note hmac: 60. module now has an optimized one-shot *note digest():
ae2. function, which is up to three times faster than ‘HMAC()’.
(Contributed by Christian Heimes in bpo-32433(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32433


File: python.info,  Node: http client,  Next: http server,  Prev: hmac<2>,  Up: 改進的模組<6>

1.7.5.20 http.client
....................

*note HTTPConnection: ae4. and *note HTTPSConnection: ae5. now support
the new 'blocksize' argument for improved upload throughput.
(Contributed by Nir Soffer in bpo-31945(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31945


File: python.info,  Node: http server,  Next: idlelib and IDLE,  Prev: http client,  Up: 改進的模組<6>

1.7.5.21 http.server
....................

*note SimpleHTTPRequestHandler: ae7. now supports the HTTP
‘If-Modified-Since’ header.  The server returns the 304 response status
if the target file was not modified after the time specified in the
header.  (Contributed by Pierre Quentel in bpo-29654(1).)

*note SimpleHTTPRequestHandler: ae7. accepts the new 'directory'
argument, in addition to the new ‘--directory’ command line argument.
With this parameter, the server serves the specified directory, by
default it uses the current working directory.  (Contributed by Stéphane
Wirtel and Julien Palard in bpo-28707(2).)

The new *note ThreadingHTTPServer: ae8. class uses threads to handle
requests using ‘ThreadingMixin’.  It is used when ‘http.server’ is run
with ‘-m’.  (Contributed by Julien Palard in bpo-31639(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29654

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28707

   (3) https://bugs.python.org/issue?@action=redirect&bpo=31639


File: python.info,  Node: idlelib and IDLE,  Next: importlib<4>,  Prev: http server,  Up: 改進的模組<6>

1.7.5.22 idlelib and IDLE
.........................

Multiple fixes for autocompletion.  (Contributed by Louie Lu in
bpo-15786(1).)

Module Browser (on the File menu, formerly called Class Browser), now
displays nested functions and classes in addition to top-level functions
and classes.  (Contributed by Guilherme Polo, Cheryl Sabella, and Terry
Jan Reedy in bpo-1612262(2).)

The Settings dialog (Options, Configure IDLE) has been partly rewritten
to improve both appearance and function.  (Contributed by Cheryl Sabella
and Terry Jan Reedy in multiple issues.)

The font sample now includes a selection of non-Latin characters so that
users can better see the effect of selecting a particular font.
(Contributed by Terry Jan Reedy in bpo-13802(3).)  The sample can be
edited to include other characters.  (Contributed by Serhiy Storchaka in
bpo-31860(4).)

The IDLE features formerly implemented as extensions have been
reimplemented as normal features.  Their settings have been moved from
the Extensions tab to other dialog tabs.  (Contributed by Charles
Wohlganger and Terry Jan Reedy in bpo-27099(5).)

Editor code context option revised.  Box displays all context lines up
to maxlines.  Clicking on a context line jumps the editor to that line.
Context colors for custom themes is added to Highlights tab of Settings
dialog.  (Contributed by Cheryl Sabella and Terry Jan Reedy in
bpo-33642(6), bpo-33768(7), and bpo-33679(8).)

On Windows, a new API call tells Windows that tk scales for DPI. On
Windows 8.1+ or 10, with DPI compatibility properties of the Python
binary unchanged, and a monitor resolution greater than 96 DPI, this
should make text and lines sharper.  It should otherwise have no effect.
(Contributed by Terry Jan Reedy in bpo-33656(9).)

New in 3.7.1:

Output over N lines (50 by default) is squeezed down to a button.  N can
be changed in the PyShell section of the General page of the Settings
dialog.  Fewer, but possibly extra long, lines can be squeezed by right
clicking on the output.  Squeezed output can be expanded in place by
double-clicking the button or into the clipboard or a separate window by
right-clicking the button.  (Contributed by Tal Einat in
bpo-1529353(10).)

The changes above have been backported to 3.6 maintenance releases.

NEW in 3.7.4:

Add "Run Customized" to the Run menu to run a module with customized
settings.  Any command line arguments entered are added to sys.argv.
They re-appear in the box for the next customized run.  One can also
suppress the normal Shell main module restart.  (Contributed by Cheryl
Sabella, Terry Jan Reedy, and others in bpo-5680(11) and bpo-37627(12).)

New in 3.7.5:

Add optional line numbers for IDLE editor windows.  Windows open without
line numbers unless set otherwise in the General tab of the
configuration dialog.  Line numbers for an existing window are shown and
hidden in the Options menu.  (Contributed by Tal Einat and Saimadhav
Heblikar in bpo-17535(13).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=15786

   (2) https://bugs.python.org/issue?@action=redirect&bpo=1612262

   (3) https://bugs.python.org/issue?@action=redirect&bpo=13802

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31860

   (5) https://bugs.python.org/issue?@action=redirect&bpo=27099

   (6) https://bugs.python.org/issue?@action=redirect&bpo=33642

   (7) https://bugs.python.org/issue?@action=redirect&bpo=33768

   (8) https://bugs.python.org/issue?@action=redirect&bpo=33679

   (9) https://bugs.python.org/issue?@action=redirect&bpo=33656

   (10) https://bugs.python.org/issue?@action=redirect&bpo=1529353

   (11) https://bugs.python.org/issue?@action=redirect&bpo=5680

   (12) https://bugs.python.org/issue?@action=redirect&bpo=37627

   (13) https://bugs.python.org/issue?@action=redirect&bpo=17535


File: python.info,  Node: importlib<4>,  Next: io<4>,  Prev: idlelib and IDLE,  Up: 改進的模組<6>

1.7.5.23 importlib
..................

The *note importlib.abc.ResourceReader: aa0. ABC was introduced to
support the loading of resources from packages.  See also *note
importlib.resources: a65.  (Contributed by Barry Warsaw, Brett Cannon in
bpo-32248(1).)

*note importlib.reload(): 4bd. now raises *note ModuleNotFoundError:
aeb. if the module lacks a spec.  (Contributed by Garvit Khatri in
bpo-29851(2).)

‘importlib.find_spec()’ now raises *note ModuleNotFoundError: aeb.
instead of *note AttributeError: 2f6. if the specified parent module is
not a package (i.e.  lacks a ‘__path__’ attribute).  (Contributed by
Milan Oberkirch in bpo-30436(3).)

The new ‘importlib.source_hash()’ can be used to compute the hash of the
passed source.  A *note hash-based .pyc file: a6e. embeds the value
returned by this function.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32248

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29851

   (3) https://bugs.python.org/issue?@action=redirect&bpo=30436


File: python.info,  Node: io<4>,  Next: ipaddress<3>,  Prev: importlib<4>,  Up: 改進的模組<6>

1.7.5.24 io
...........

The new *note TextIOWrapper.reconfigure(): aed. method can be used to
reconfigure the text stream with the new settings.  (Contributed by
Antoine Pitrou in bpo-30526(1) and INADA Naoki in bpo-15216(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30526

   (2) https://bugs.python.org/issue?@action=redirect&bpo=15216


File: python.info,  Node: ipaddress<3>,  Next: itertools<5>,  Prev: io<4>,  Up: 改進的模組<6>

1.7.5.25 ipaddress
..................

The new ‘subnet_of()’ and ‘supernet_of()’ methods of *note
ipaddress.IPv6Network: 1e4. and *note ipaddress.IPv4Network: 1e3. can be
used for network containment tests.  (Contributed by Michel Albert and
Cheryl Sabella in bpo-20825(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=20825


File: python.info,  Node: itertools<5>,  Next: locale<4>,  Prev: ipaddress<3>,  Up: 改進的模組<6>

1.7.5.26 itertools
..................

*note itertools.islice(): af0. now accepts *note integer-like objects:
6c1. as start, stop, and slice arguments.  (Contributed by Will Roberts
in bpo-30537(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30537


File: python.info,  Node: locale<4>,  Next: logging<3>,  Prev: itertools<5>,  Up: 改進的模組<6>

1.7.5.27 locale
...............

The new 'monetary' argument to *note locale.format_string(): 4c3. can be
used to make the conversion use monetary thousands separators and
grouping strings.  (Contributed by Garvit in bpo-10379(1).)

The *note locale.getpreferredencoding(): 4df. function now always
returns ‘'UTF-8'’ on Android or when in the *note forced UTF-8 mode:
a6d.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=10379


File: python.info,  Node: logging<3>,  Next: math<6>,  Prev: locale<4>,  Up: 改進的模組<6>

1.7.5.28 logging
................

*note Logger: af3. instances can now be pickled.  (Contributed by Vinay
Sajip in bpo-30520(1).)

The new *note StreamHandler.setStream(): af4. method can be used to
replace the logger stream after handler creation.  (Contributed by Vinay
Sajip in bpo-30522(2).)

It is now possible to specify keyword arguments to handler constructors
in configuration passed to *note logging.config.fileConfig(): af5.
(Contributed by Preston Landers in bpo-31080(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30520

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30522

   (3) https://bugs.python.org/issue?@action=redirect&bpo=31080


File: python.info,  Node: math<6>,  Next: mimetypes<2>,  Prev: logging<3>,  Up: 改進的模組<6>

1.7.5.29 math
.............

The new *note math.remainder(): af7. function implements the IEEE
754-style remainder operation.  (Contributed by Mark Dickinson in
bpo-29962(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29962


File: python.info,  Node: mimetypes<2>,  Next: msilib,  Prev: math<6>,  Up: 改進的模組<6>

1.7.5.30 mimetypes
..................

The MIME type of .bmp has been changed from ‘'image/x-ms-bmp'’ to
‘'image/bmp'’.  (Contributed by Nitish Chandra in bpo-22589(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22589


File: python.info,  Node: msilib,  Next: multiprocessing<4>,  Prev: mimetypes<2>,  Up: 改進的模組<6>

1.7.5.31 msilib
...............

The new ‘Database.Close()’ method can be used to close the MSI database.
(Contributed by Berker Peksag in bpo-20486(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=20486


File: python.info,  Node: multiprocessing<4>,  Next: os<7>,  Prev: msilib,  Up: 改進的模組<6>

1.7.5.32 multiprocessing
........................

The new *note Process.close(): afb. method explicitly closes the process
object and releases all resources associated with it.  *note ValueError:
1e7. is raised if the underlying process is still running.  (Contributed
by Antoine Pitrou in bpo-30596(1).)

The new *note Process.kill(): afc. method can be used to terminate the
process using the ‘SIGKILL’ signal on Unix.  (Contributed by Vitor
Pereira in bpo-30794(2).)

Non-daemonic threads created by *note Process: afd. are now joined on
process exit.  (Contributed by Antoine Pitrou in bpo-18966(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30596

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30794

   (3) https://bugs.python.org/issue?@action=redirect&bpo=18966


File: python.info,  Node: os<7>,  Next: pathlib<8>,  Prev: multiprocessing<4>,  Up: 改進的模組<6>

1.7.5.33 os
...........

*note os.fwalk(): aff. now accepts the 'path' argument as *note bytes:
1a5.  (Contributed by Serhiy Storchaka in bpo-28682(1).)

*note os.scandir(): a02. gained support for *note file descriptors: b00.
(Contributed by Serhiy Storchaka in bpo-25996(2).)

The new *note register_at_fork(): 2d1. function allows registering
Python callbacks to be executed at process fork.  (Contributed by
Antoine Pitrou in bpo-16500(3).)

Added *note os.preadv(): b01. (combine the functionality of *note
os.readv(): b02. and *note os.pread(): b03.) and *note os.pwritev():
b04. functions (combine the functionality of *note os.writev(): b05. and
*note os.pwrite(): b06.).  (Contributed by Pablo Galindo in
bpo-31368(4).)

The mode argument of *note os.makedirs(): 203. no longer affects the
file permission bits of newly created intermediate-level directories.
(Contributed by Serhiy Storchaka in bpo-19930(5).)

*note os.dup2(): b07. now returns the new file descriptor.  Previously,
‘None’ was always returned.  (Contributed by Benjamin Peterson in
bpo-32441(6).)

The structure returned by *note os.stat(): 448. now contains the *note
st_fstype: b08. attribute on Solaris and its derivatives.  (Contributed
by Jesús Cea Avión in bpo-32659(7).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28682

   (2) https://bugs.python.org/issue?@action=redirect&bpo=25996

   (3) https://bugs.python.org/issue?@action=redirect&bpo=16500

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31368

   (5) https://bugs.python.org/issue?@action=redirect&bpo=19930

   (6) https://bugs.python.org/issue?@action=redirect&bpo=32441

   (7) https://bugs.python.org/issue?@action=redirect&bpo=32659


File: python.info,  Node: pathlib<8>,  Next: pdb<4>,  Prev: os<7>,  Up: 改進的模組<6>

1.7.5.34 pathlib
................

The new *note Path.is_mount(): 9bb. method is now available on POSIX
systems and can be used to determine whether a path is a mount point.
(Contributed by Cooper Ry Lees in bpo-30897(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30897


File: python.info,  Node: pdb<4>,  Next: py_compile<3>,  Prev: pathlib<8>,  Up: 改進的模組<6>

1.7.5.35 pdb
............

*note pdb.set_trace(): 21a. now takes an optional 'header' keyword-only
argument.  If given, it is printed to the console just before debugging
begins.  (Contributed by Barry Warsaw in bpo-31389(1).)

*note pdb: 94. command line now accepts ‘-m module_name’ as an
alternative to script file.  (Contributed by Mario Corchero in
bpo-32206(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31389

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32206


File: python.info,  Node: py_compile<3>,  Next: pydoc<2>,  Prev: pdb<4>,  Up: 改進的模組<6>

1.7.5.36 py_compile
...................

*note py_compile.compile(): 9c9. - and by extension, *note compileall:
19. - now respects the ‘SOURCE_DATE_EPOCH’ environment variable by
unconditionally creating ‘.pyc’ files for hash-based validation.  This
allows for guaranteeing reproducible builds(1) of ‘.pyc’ files when they
are created eagerly.  (Contributed by Bernhard M. Wiedemann in
bpo-29708(2).)

   ---------- Footnotes ----------

   (1) https://reproducible-builds.org/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29708


File: python.info,  Node: pydoc<2>,  Next: queue<2>,  Prev: py_compile<3>,  Up: 改進的模組<6>

1.7.5.37 pydoc
..............

The pydoc server can now bind to an arbitrary hostname specified by the
new ‘-n’ command-line argument.  (Contributed by Feanil Patel in
bpo-31128(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31128


File: python.info,  Node: queue<2>,  Next: re<4>,  Prev: pydoc<2>,  Up: 改進的模組<6>

1.7.5.38 queue
..............

The new *note SimpleQueue: b0e. class is an unbounded FIFO queue.
(Contributed by Antoine Pitrou in bpo-14976(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=14976


File: python.info,  Node: re<4>,  Next: signal<2>,  Prev: queue<2>,  Up: 改進的模組<6>

1.7.5.39 re
...........

The flags *note re.ASCII: 5d3, *note re.LOCALE: b10. and *note
re.UNICODE: b11. can be set within the scope of a group.  (Contributed
by Serhiy Storchaka in bpo-31690(1).)

*note re.split(): 282. now supports splitting on a pattern like ‘r'\b'’,
‘'^$'’ or ‘(?=-)’ that matches an empty string.  (Contributed by Serhiy
Storchaka in bpo-25054(2).)

Regular expressions compiled with the *note re.LOCALE: b10. flag no
longer depend on the locale at compile time.  Locale settings are
applied only when the compiled regular expression is used.  (Contributed
by Serhiy Storchaka in bpo-30215(3).)

*note FutureWarning: 357. is now emitted if a regular expression
contains character set constructs that will change semantically in the
future, such as nested sets and set operations.  (Contributed by Serhiy
Storchaka in bpo-30349(4).)

Compiled regular expression and match objects can now be copied using
*note copy.copy(): 4d8. and *note copy.deepcopy(): b12.  (Contributed by
Serhiy Storchaka in bpo-10076(5).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31690

   (2) https://bugs.python.org/issue?@action=redirect&bpo=25054

   (3) https://bugs.python.org/issue?@action=redirect&bpo=30215

   (4) https://bugs.python.org/issue?@action=redirect&bpo=30349

   (5) https://bugs.python.org/issue?@action=redirect&bpo=10076


File: python.info,  Node: signal<2>,  Next: socket<5>,  Prev: re<4>,  Up: 改進的模組<6>

1.7.5.40 signal
...............

The new 'warn_on_full_buffer' argument to the *note
signal.set_wakeup_fd(): b14. function makes it possible to specify
whether Python prints a warning on stderr when the wakeup buffer
overflows.  (Contributed by Nathaniel J. Smith in bpo-30050(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30050


File: python.info,  Node: socket<5>,  Next: socketserver,  Prev: signal<2>,  Up: 改進的模組<6>

1.7.5.41 socket
...............

The new *note socket.getblocking(): b16. method returns ‘True’ if the
socket is in blocking mode and ‘False’ otherwise.  (Contributed by Yury
Selivanov in bpo-32373(1).)

The new *note socket.close(): b17. function closes the passed socket
file descriptor.  This function should be used instead of *note
os.close(): b18. for better compatibility across platforms.
(Contributed by Christian Heimes in bpo-32454(2).)

The *note socket: b8. module now exposes the ‘socket.TCP_CONGESTION’
(Linux 2.6.13), ‘socket.TCP_USER_TIMEOUT’ (Linux 2.6.37), and
‘socket.TCP_NOTSENT_LOWAT’ (Linux 3.12) constants.  (Contributed by Omar
Sandoval in bpo-26273(3) and Nathaniel J. Smith in bpo-29728(4).)

Support for *note socket.AF_VSOCK: b19. sockets has been added to allow
communication between virtual machines and their hosts.  (Contributed by
Cathy Avery in bpo-27584(5).)

Sockets now auto-detect family, type and protocol from file descriptor
by default.  (Contributed by Christian Heimes in bpo-28134(6).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32373

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32454

   (3) https://bugs.python.org/issue?@action=redirect&bpo=26273

   (4) https://bugs.python.org/issue?@action=redirect&bpo=29728

   (5) https://bugs.python.org/issue?@action=redirect&bpo=27584

   (6) https://bugs.python.org/issue?@action=redirect&bpo=28134


File: python.info,  Node: socketserver,  Next: sqlite3<6>,  Prev: socket<5>,  Up: 改進的模組<6>

1.7.5.42 socketserver
.....................

‘socketserver.ThreadingMixIn.server_close()’ now waits until all
non-daemon threads complete.  ‘socketserver.ForkingMixIn.server_close()’
now waits until all child processes complete.

Add a new ‘socketserver.ForkingMixIn.block_on_close’ class attribute to
*note socketserver.ForkingMixIn: b1b. and *note
socketserver.ThreadingMixIn: b1c. classes.  Set the class attribute to
‘False’ to get the pre-3.7 behaviour.


File: python.info,  Node: sqlite3<6>,  Next: ssl<5>,  Prev: socketserver,  Up: 改進的模組<6>

1.7.5.43 sqlite3
................

*note sqlite3.Connection: 22a. now exposes the *note backup(): b1e.
method when the underlying SQLite library is at version 3.6.11 or
higher.  (Contributed by Lele Gaifax in bpo-27645(1).)

The 'database' argument of *note sqlite3.connect(): 288. now accepts any
*note path-like object: ac2, instead of just a string.  (Contributed by
Anders Lorentsen in bpo-31843(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27645

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31843


File: python.info,  Node: ssl<5>,  Next: string<2>,  Prev: sqlite3<6>,  Up: 改進的模組<6>

1.7.5.44 ssl
............

The *note ssl: bb. module now uses OpenSSL's builtin API instead of
‘match_hostname()’ to check a host name or an IP address.  Values are
validated during TLS handshake.  Any certificate validation error
including failing the host name check now raises *note
SSLCertVerificationError: b20. and aborts the handshake with a proper
TLS Alert message.  The new exception contains additional information.
Host name validation can be customized with *note
SSLContext.hostname_checks_common_name: b21.  (Contributed by Christian
Heimes in bpo-31399(1).)

     備註: The improved host name check requires a 'libssl'
     implementation compatible with OpenSSL 1.0.2 or 1.1.  Consequently,
     OpenSSL 0.9.8 and 1.0.1 are no longer supported (see *note Platform
     Support Removals: b22. for more details).  The ssl module is mostly
     compatible with LibreSSL 2.7.2 and newer.

The ‘ssl’ module no longer sends IP addresses in SNI TLS extension.
(Contributed by Christian Heimes in bpo-32185(2).)

‘match_hostname()’ no longer supports partial wildcards like
‘www*.example.org’.  (Contributed by Mandeep Singh in bpo-23033(3) and
Christian Heimes in bpo-31399(4).)

The default cipher suite selection of the ‘ssl’ module now uses a
blacklist approach rather than a hard-coded whitelist.  Python no longer
re-enables ciphers that have been blocked by OpenSSL security updates.
Default cipher suite selection can be configured at compile time.
(Contributed by Christian Heimes in bpo-31429(5).)

Validation of server certificates containing internationalized domain
names (IDNs) is now supported.  As part of this change, the *note
SSLSocket.server_hostname: b23. attribute now stores the expected
hostname in A-label form (‘"xn--pythn-mua.org"’), rather than the
U-label form (‘"pythön.org"’).  (Contributed by Nathaniel J. Smith and
Christian Heimes in bpo-28414(6).)

The ‘ssl’ module has preliminary and experimental support for TLS 1.3
and OpenSSL 1.1.1.  At the time of Python 3.7.0 release, OpenSSL 1.1.1
is still under development and TLS 1.3 hasn't been finalized yet.  The
TLS 1.3 handshake and protocol behaves slightly differently than TLS 1.2
and earlier, see *note TLS 1.3: b24.  (Contributed by Christian Heimes
in bpo-32947(7), bpo-20995(8), bpo-29136(9), bpo-30622(10) and
bpo-33618(11))

*note SSLSocket: 88f. and *note SSLObject: b25. no longer have a public
constructor.  Direct instantiation was never a documented and supported
feature.  Instances must be created with *note SSLContext: 276. methods
*note wrap_socket(): 4c9. and *note wrap_bio(): b26.  (Contributed by
Christian Heimes in bpo-32951(12))

OpenSSL 1.1 APIs for setting the minimum and maximum TLS protocol
version are available as *note SSLContext.minimum_version: b27. and
*note SSLContext.maximum_version: b28.  Supported protocols are
indicated by several new flags, such as *note HAS_TLSv1_1: b29.
(Contributed by Christian Heimes in bpo-32609(13).)

Added *note ssl.SSLContext.post_handshake_auth: 9d5. to enable and *note
ssl.SSLSocket.verify_client_post_handshake(): 9d6. to initiate TLS 1.3
post-handshake authentication.  (Contributed by Christian Heimes in
gh-78851(14).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31399

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32185

   (3) https://bugs.python.org/issue?@action=redirect&bpo=23033

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31399

   (5) https://bugs.python.org/issue?@action=redirect&bpo=31429

   (6) https://bugs.python.org/issue?@action=redirect&bpo=28414

   (7) https://bugs.python.org/issue?@action=redirect&bpo=32947

   (8) https://bugs.python.org/issue?@action=redirect&bpo=20995

   (9) https://bugs.python.org/issue?@action=redirect&bpo=29136

   (10) https://bugs.python.org/issue?@action=redirect&bpo=30622

   (11) https://bugs.python.org/issue?@action=redirect&bpo=33618

   (12) https://bugs.python.org/issue?@action=redirect&bpo=32951

   (13) https://bugs.python.org/issue?@action=redirect&bpo=32609

   (14) https://github.com/python/cpython/issues/78851


File: python.info,  Node: string<2>,  Next: subprocess<2>,  Prev: ssl<5>,  Up: 改進的模組<6>

1.7.5.45 string
...............

*note string.Template: 62d. now lets you to optionally modify the
regular expression pattern for braced placeholders and non-braced
placeholders separately.  (Contributed by Barry Warsaw in
bpo-1198569(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1198569


File: python.info,  Node: subprocess<2>,  Next: sys<7>,  Prev: string<2>,  Up: 改進的模組<6>

1.7.5.46 subprocess
...................

The *note subprocess.run(): b2c. function accepts the new
'capture_output' keyword argument.  When true, stdout and stderr will be
captured.  This is equivalent to passing *note subprocess.PIPE: b2d. as
'stdout' and 'stderr' arguments.  (Contributed by Bo Bayles in
bpo-32102(1).)

The ‘subprocess.run’ function and the *note subprocess.Popen: 17d.
constructor now accept the 'text' keyword argument as an alias to
'universal_newlines'.  (Contributed by Andrew Clegg in bpo-31756(2).)

On Windows the default for 'close_fds' was changed from ‘False’ to
‘True’ when redirecting the standard handles.  It's now possible to set
'close_fds' to true when redirecting the standard handles.  See *note
subprocess.Popen: 17d.  This means that 'close_fds' now defaults to
‘True’ on all supported platforms.  (Contributed by Segev Finer in
bpo-19764(3).)

The subprocess module is now more graceful when handling *note
KeyboardInterrupt: 975. during *note subprocess.call(): b2e, *note
subprocess.run(): b2c, or in a *note Popen: 17d. context manager.  It
now waits a short amount of time for the child to exit, before
continuing the handling of the ‘KeyboardInterrupt’ exception.
(Contributed by Gregory P. Smith in bpo-25942(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32102

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31756

   (3) https://bugs.python.org/issue?@action=redirect&bpo=19764

   (4) https://bugs.python.org/issue?@action=redirect&bpo=25942


File: python.info,  Node: sys<7>,  Next: time<5>,  Prev: subprocess<2>,  Up: 改進的模組<6>

1.7.5.47 sys
............

The new *note sys.breakpointhook(): a7d. hook function is called by the
built-in *note breakpoint(): 219.  (Contributed by Barry Warsaw in
bpo-31353(1).)

On Android, the new *note sys.getandroidapilevel(): b30. returns the
build-time Android API version.  (Contributed by Victor Stinner in
bpo-28740(2).)

The new *note sys.get_coroutine_origin_tracking_depth(): b31. function
returns the current coroutine origin tracking depth, as set by the new
*note sys.set_coroutine_origin_tracking_depth(): b32.  *note asyncio: 8.
has been converted to use this new API instead of the deprecated
‘sys.set_coroutine_wrapper()’.  (Contributed by Nathaniel J. Smith in
bpo-32591(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31353

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28740

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32591


File: python.info,  Node: time<5>,  Next: tkinter<5>,  Prev: sys<7>,  Up: 改進的模組<6>

1.7.5.48 time
.............

PEP 564(1) adds six new functions with nanosecond resolution to the
*note time: d7. module:

   * *note time.clock_gettime_ns(): a85.

   * *note time.clock_settime_ns(): a86.

   * *note time.monotonic_ns(): a87.

   * *note time.perf_counter_ns(): a88.

   * *note time.process_time_ns(): a89.

   * *note time.time_ns(): a8a.

New clock identifiers have been added:

   * *note time.CLOCK_BOOTTIME: b34. (Linux): Identical to *note
     time.CLOCK_MONOTONIC: b35, except it also includes any time that
     the system is suspended.

   * *note time.CLOCK_PROF: b36. (FreeBSD, NetBSD and OpenBSD):
     High-resolution per-process CPU timer.

   * *note time.CLOCK_UPTIME: b37. (FreeBSD, OpenBSD): Time whose
     absolute value is the time the system has been running and not
     suspended, providing accurate uptime measurement.

The new *note time.thread_time(): 8da. and *note time.thread_time_ns():
b38. functions can be used to get per-thread CPU time measurements.
(Contributed by Antoine Pitrou in bpo-32025(2).)

The new *note time.pthread_getcpuclockid(): b39. function returns the
clock ID of the thread-specific CPU-time clock.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0564/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32025


File: python.info,  Node: tkinter<5>,  Next: tracemalloc<2>,  Prev: time<5>,  Up: 改進的模組<6>

1.7.5.49 tkinter
................

The new *note tkinter.ttk.Spinbox: b3b. class is now available.
(Contributed by Alan Moore in bpo-32585(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32585


File: python.info,  Node: tracemalloc<2>,  Next: types<4>,  Prev: tkinter<5>,  Up: 改進的模組<6>

1.7.5.50 tracemalloc
....................

*note tracemalloc.Traceback: b3d. behaves more like regular tracebacks,
sorting the frames from oldest to most recent.  *note
Traceback.format(): b3e. now accepts negative 'limit', truncating the
result to the ‘abs(limit)’ oldest frames.  To get the old behaviour, use
the new 'most_recent_first' argument to ‘Traceback.format()’.
(Contributed by Jesse Bakker in bpo-32121(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32121


File: python.info,  Node: types<4>,  Next: unicodedata<6>,  Prev: tracemalloc<2>,  Up: 改進的模組<6>

1.7.5.51 types
..............

The new *note WrapperDescriptorType: b40, *note MethodWrapperType: 5f1,
*note MethodDescriptorType: b41, and *note ClassMethodDescriptorType:
b42. classes are now available.  (Contributed by Manuel Krebber and
Guido van Rossum in bpo-29377(1), and Serhiy Storchaka in bpo-32265(2).)

The new *note types.resolve_bases(): b43. function resolves MRO entries
dynamically as specified by PEP 560(3).  (Contributed by Ivan Levkivskyi
in bpo-32717(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29377

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32265

   (3) https://peps.python.org/pep-0560/

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32717


File: python.info,  Node: unicodedata<6>,  Next: unittest<7>,  Prev: types<4>,  Up: 改進的模組<6>

1.7.5.52 unicodedata
....................

The internal *note unicodedata: ee. database has been upgraded to use
Unicode 11(1).  (Contributed by Benjamin Peterson.)

   ---------- Footnotes ----------

   (1) https://www.unicode.org/versions/Unicode11.0.0/


File: python.info,  Node: unittest<7>,  Next: unittest mock,  Prev: unicodedata<6>,  Up: 改進的模組<6>

1.7.5.53 unittest
.................

The new ‘-k’ command-line option allows filtering tests by a name
substring or a Unix shell-like pattern.  For example, ‘python -m
unittest -k foo’ runs ‘foo_tests.SomeTest.test_something’,
‘bar_tests.SomeTest.test_foo’, but not
‘bar_tests.FooTest.test_something’.  (Contributed by Jonas Haag in
bpo-32071(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32071


File: python.info,  Node: unittest mock,  Next: urllib parse<5>,  Prev: unittest<7>,  Up: 改進的模組<6>

1.7.5.54 unittest.mock
......................

The *note sentinel: b47. attributes now preserve their identity when
they are *note copied: 1e. or *note pickled: 95.  (Contributed by Serhiy
Storchaka in bpo-20804(1).)

The new *note seal(): b48. function allows sealing *note Mock: 9ef.
instances, which will disallow further creation of attribute mocks.  The
seal is applied recursively to all attributes that are themselves mocks.
(Contributed by Mario Corchero in bpo-30541(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=20804

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30541


File: python.info,  Node: urllib parse<5>,  Next: uu,  Prev: unittest mock,  Up: 改進的模組<6>

1.7.5.55 urllib.parse
.....................

*note urllib.parse.quote(): b4a. has been updated from RFC 2396(1) to
RFC 3986(2), adding ‘~’ to the set of characters that are never quoted
by default.  (Contributed by Christian Theune and Ratnadeep Debnath in
bpo-16285(3).)

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2396.html

   (2) https://datatracker.ietf.org/doc/html/rfc3986.html

   (3) https://bugs.python.org/issue?@action=redirect&bpo=16285


File: python.info,  Node: uu,  Next: uuid<2>,  Prev: urllib parse<5>,  Up: 改進的模組<6>

1.7.5.56 uu
...........

The ‘uu.encode()’ function now accepts an optional 'backtick' keyword
argument.  When it's true, zeros are represented by ‘'`'’ instead of
spaces.  (Contributed by Xiang Zhang in bpo-30103(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30103


File: python.info,  Node: uuid<2>,  Next: warnings<3>,  Prev: uu,  Up: 改進的模組<6>

1.7.5.57 uuid
.............

The new *note UUID.is_safe: b4d. attribute relays information from the
platform about whether generated UUIDs are generated with a
multiprocessing-safe method.  (Contributed by Barry Warsaw in
bpo-22807(1).)

*note uuid.getnode(): b4e. now prefers universally administered MAC
addresses over locally administered MAC addresses.  This makes a better
guarantee for global uniqueness of UUIDs returned from *note
uuid.uuid1(): b4f.  If only locally administered MAC addresses are
available, the first such one found is returned.  (Contributed by Barry
Warsaw in bpo-32107(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22807

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32107


File: python.info,  Node: warnings<3>,  Next: xml<5>,  Prev: uuid<2>,  Up: 改進的模組<6>

1.7.5.58 warnings
.................

The initialization of the default warnings filters has changed as
follows:

   * warnings enabled via command line options (including those for
     *note -b: 587. and the new CPython-specific *note -X: 15a. ‘dev’
     option) are always passed to the warnings machinery via the *note
     sys.warnoptions: 37b. attribute.

   * warnings filters enabled via the command line or the environment
     now have the following order of precedence:

        * the ‘BytesWarning’ filter for *note -b: 587. (or ‘-bb’)

        * any filters specified with the *note -W: 86c. option

        * any filters specified with the *note PYTHONWARNINGS: b51.
          environment variable

        * any other CPython specific filters (e.g.  the ‘default’ filter
          added for the new ‘-X dev’ mode)

        * any implicit filters defined directly by the warnings
          machinery

   * in *note CPython debug builds: 1de, all warnings are now displayed
     by default (the implicit filter list is empty)

（由 Nick Coghlan 和 Victor Stinner 在 bpo-20361(1)、bpo-32043(2) 和
bpo-32230(3) 中貢獻。）

Deprecation warnings are once again shown by default in single-file
scripts and at the interactive prompt.  See *note PEP 565; Show
DeprecationWarning in __main__: a70. for details.  (Contributed by Nick
Coghlan in bpo-31975(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=20361

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32043

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32230

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31975


File: python.info,  Node: xml<5>,  Next: xml etree,  Prev: warnings<3>,  Up: 改進的模組<6>

1.7.5.59 xml
............

As mitigation against DTD and external entity retrieval, the *note
xml.dom.minidom: 109. and *note xml.sax: 110. modules no longer process
external entities by default.  (Contributed by Christian Heimes in
gh-61441(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/61441


File: python.info,  Node: xml etree,  Next: xmlrpc server,  Prev: xml<5>,  Up: 改進的模組<6>

1.7.5.60 xml.etree
..................

*note ElementPath: b54. predicates in the ‘find()’ methods can now
compare text of the current node with ‘[. = "text"]’, not only text in
children.  Predicates also allow adding spaces for better readability.
(Contributed by Stefan Behnel in bpo-31648(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31648


File: python.info,  Node: xmlrpc server,  Next: zipapp,  Prev: xml etree,  Up: 改進的模組<6>

1.7.5.61 xmlrpc.server
......................

‘SimpleXMLRPCDispatcher.register_function’ can now be used as a
decorator.  (Contributed by Xiang Zhang in bpo-7769(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=7769


File: python.info,  Node: zipapp,  Next: zipfile<2>,  Prev: xmlrpc server,  Up: 改進的模組<6>

1.7.5.62 zipapp
...............

Function *note create_archive(): b57. now accepts an optional 'filter'
argument to allow the user to select which files should be included in
the archive.  (Contributed by Irmen de Jong in bpo-31072(1).)

Function *note create_archive(): b57. now accepts an optional
'compressed' argument to generate a compressed archive.  A command line
option ‘--compress’ has also been added to support compression.
(Contributed by Zhiming Wang in bpo-31638(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31072

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31638


File: python.info,  Node: zipfile<2>,  Prev: zipapp,  Up: 改進的模組<6>

1.7.5.63 zipfile
................

*note ZipFile: 669. now accepts the new 'compresslevel' parameter to
control the compression level.  (Contributed by Bo Bayles in
bpo-21417(1).)

Subdirectories in archives created by ‘ZipFile’ are now stored in
alphabetical order.  (Contributed by Bernhard M. Wiedemann in
bpo-30693(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21417

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30693


File: python.info,  Node: C API 變更<5>,  Next: 建置變更<5>,  Prev: 改進的模組<6>,  Up: Python 3 7 有什麼新功能

1.7.6 C API 變更
----------------

A new API for thread-local storage has been implemented.  See *note PEP
539; New C API for Thread-Local Storage: a71. for an overview and *note
Thread Specific Storage (TSS) API: a81. for a complete reference.
(Contributed by Masayuki Yamamoto in bpo-25658(1).)

The new *note context variables: a63. functionality exposes a number of
*note new C APIs: a9b.

The new *note PyImport_GetModule(): b5a. function returns the previously
imported module with the given name.  (Contributed by Eric Snow in
bpo-28411(2).)

The new *note Py_RETURN_RICHCOMPARE: b5b. macro eases writing rich
comparison functions.  (Contributed by Petr Victorin in bpo-23699(3).)

The new *note Py_UNREACHABLE: b5c. macro can be used to mark unreachable
code paths.  (Contributed by Barry Warsaw in bpo-31338(4).)

The *note tracemalloc: e8. now exposes a C API through the new *note
PyTraceMalloc_Track(): b5d. and *note PyTraceMalloc_Untrack(): b5e.
functions.  (Contributed by Victor Stinner in bpo-30054(5).)

The new ‘import__find__load__start()’ and ‘import__find__load__done()’
static markers can be used to trace module imports.  (Contributed by
Christian Heimes in bpo-31574(6).)

The fields ‘name’ and ‘doc’ of structures *note PyMemberDef: 4f5, *note
PyGetSetDef: b5f, *note PyStructSequence_Field: b60, *note
PyStructSequence_Desc: b61, and ‘wrapperbase’ are now of type ‘const
char *’ rather of ‘char *’.  (Contributed by Serhiy Storchaka in
bpo-28761(7).)

The result of *note PyUnicode_AsUTF8AndSize(): 83d. and *note
PyUnicode_AsUTF8(): b62. is now of type ‘const char *’ rather of ‘char
*’.  (Contributed by Serhiy Storchaka in bpo-28769(8).)

The result of *note PyMapping_Keys(): b63, *note PyMapping_Values():
b64. and *note PyMapping_Items(): b65. is now always a list, rather than
a list or a tuple.  (Contributed by Oren Milman in bpo-28280(9).)

Added functions *note PySlice_Unpack(): 3c5. and *note
PySlice_AdjustIndices(): 3c6.  (Contributed by Serhiy Storchaka in
bpo-27867(10).)

*note PyOS_AfterFork(): 3c2. is deprecated in favour of the new
functions *note PyOS_BeforeFork(): b66, *note PyOS_AfterFork_Parent():
b67. and *note PyOS_AfterFork_Child(): 3c3.  (Contributed by Antoine
Pitrou in bpo-16500(11).)

The ‘PyExc_RecursionErrorInst’ singleton that was part of the public API
has been removed as its members being never cleared may cause a segfault
during finalization of the interpreter.  Contributed by Xavier de Gaye
in bpo-22898(12) and bpo-30697(13).

Added C API support for timezones with timezone constructors *note
PyTimeZone_FromOffset(): b68. and *note PyTimeZone_FromOffsetAndName():
b69, and access to the UTC singleton with *note PyDateTime_TimeZone_UTC:
b6a.  Contributed by Paul Ganssle in bpo-10381(14).

The type of results of ‘PyThread_start_new_thread()’ and
‘PyThread_get_thread_ident()’, and the 'id' parameter of *note
PyThreadState_SetAsyncExc(): b6b. changed from long to unsigned long.
(Contributed by Serhiy Storchaka in bpo-6532(15).)

*note PyUnicode_AsWideCharString(): 861. now raises a *note ValueError:
1e7. if the second argument is ‘NULL’ and the wchar_t* string contains
null characters.  (Contributed by Serhiy Storchaka in bpo-30708(16).)

Changes to the startup sequence and the management of dynamic memory
allocators mean that the long documented requirement to call *note
Py_Initialize(): 851. before calling most C API functions is now relied
on more heavily, and failing to abide by it may lead to segfaults in
embedding applications.  See the *note Porting to Python 3.7: a74.
section in this document and the *note Python 初始化之前: b6c. section
in the C API documentation for more details.

The new *note PyInterpreterState_GetID(): b6d. returns the unique ID for
a given interpreter.  (Contributed by Eric Snow in bpo-29102(17).)

*note Py_DecodeLocale(): b6e, *note Py_EncodeLocale(): b6f. now use the
UTF-8 encoding when the *note UTF-8 mode: a6d. is enabled.  (Contributed
by Victor Stinner in bpo-29240(18).)

*note PyUnicode_DecodeLocaleAndSize(): b70. and *note
PyUnicode_EncodeLocale(): b71. now use the current locale encoding for
‘surrogateescape’ error handler.  (Contributed by Victor Stinner in
bpo-29240(19).)

The 'start' and 'end' parameters of *note PyUnicode_FindChar(): 85e. are
now adjusted to behave like string slices.  (Contributed by Xiang Zhang
in bpo-28822(20).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25658

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28411

   (3) https://bugs.python.org/issue?@action=redirect&bpo=23699

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31338

   (5) https://bugs.python.org/issue?@action=redirect&bpo=30054

   (6) https://bugs.python.org/issue?@action=redirect&bpo=31574

   (7) https://bugs.python.org/issue?@action=redirect&bpo=28761

   (8) https://bugs.python.org/issue?@action=redirect&bpo=28769

   (9) https://bugs.python.org/issue?@action=redirect&bpo=28280

   (10) https://bugs.python.org/issue?@action=redirect&bpo=27867

   (11) https://bugs.python.org/issue?@action=redirect&bpo=16500

   (12) https://bugs.python.org/issue?@action=redirect&bpo=22898

   (13) https://bugs.python.org/issue?@action=redirect&bpo=30697

   (14) https://bugs.python.org/issue?@action=redirect&bpo=10381

   (15) https://bugs.python.org/issue?@action=redirect&bpo=6532

   (16) https://bugs.python.org/issue?@action=redirect&bpo=30708

   (17) https://bugs.python.org/issue?@action=redirect&bpo=29102

   (18) https://bugs.python.org/issue?@action=redirect&bpo=29240

   (19) https://bugs.python.org/issue?@action=redirect&bpo=29240

   (20) https://bugs.python.org/issue?@action=redirect&bpo=28822


File: python.info,  Node: 建置變更<5>,  Next: 最佳化<6>,  Prev: C API 變更<5>,  Up: Python 3 7 有什麼新功能

1.7.7 建置變更
--------------

Support for building ‘--without-threads’ has been removed.  The *note
threading: d6. module is now always available.  (Contributed by Antoine
Pitrou in bpo-31370(1).).

A full copy of libffi is no longer bundled for use when building the
*note _ctypes: 22. module on non-OSX UNIX platforms.  An installed copy
of libffi is now required when building ‘_ctypes’ on such platforms.
(Contributed by Zachary Ware in bpo-27979(2).)

The Windows build process no longer depends on Subversion to pull in
external sources, a Python script is used to download zipfiles from
GitHub instead.  If Python 3.6 is not found on the system (via ‘py
-3.6’), NuGet is used to download a copy of 32-bit Python for this
purpose.  (Contributed by Zachary Ware in bpo-30450(3).)

The *note ssl: bb. module requires OpenSSL 1.0.2 or 1.1 compatible
libssl.  OpenSSL 1.0.1 has reached end of lifetime on 2016-12-31 and is
no longer supported.  LibreSSL is temporarily not supported as well.
LibreSSL releases up to version 2.6.4 are missing required OpenSSL 1.0.2
APIs.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31370

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27979

   (3) https://bugs.python.org/issue?@action=redirect&bpo=30450


File: python.info,  Node: 最佳化<6>,  Next: Other CPython Implementation Changes,  Prev: 建置變更<5>,  Up: Python 3 7 有什麼新功能

1.7.8 最佳化
------------

The overhead of calling many methods of various standard library classes
implemented in C has been significantly reduced by porting more code to
use the ‘METH_FASTCALL’ convention.  (Contributed by Victor Stinner in
bpo-29300(1), bpo-29507(2), bpo-29452(3), and bpo-29286(4).)

Various optimizations have reduced Python startup time by 10% on Linux
and up to 30% on macOS. (Contributed by Victor Stinner, INADA Naoki in
bpo-29585(5), and Ivan Levkivskyi in bpo-31333(6).)

Method calls are now up to 20% faster due to the bytecode changes which
avoid creating bound method instances.  (Contributed by Yury Selivanov
and INADA Naoki in bpo-26110(7).)  The *note asyncio: 8. module received
a number of notable optimizations for commonly used functions:

   * The *note asyncio.get_event_loop(): 2a3. function has been
     reimplemented in C to make it up to 15 times faster.  (Contributed
     by Yury Selivanov in bpo-32296(8).)

   * *note asyncio.Future: b74. callback management has been optimized.
     (Contributed by Yury Selivanov in bpo-32348(9).)

   * *note asyncio.gather(): 5a2. is now up to 15% faster.  (Contributed
     by Yury Selivanov in bpo-32355(10).)

   * *note asyncio.sleep(): a12. is now up to 2 times faster when the
     'delay' argument is zero or negative.  (Contributed by Andrew
     Svetlov in bpo-32351(11).)

   * The performance overhead of asyncio debug mode has been reduced.
     (Contributed by Antoine Pitrou in bpo-31970(12).)

As a result of *note PEP 560 work: a68, the import time of *note typing:
ed. has been reduced by a factor of 7, and many typing operations are
now faster.  (Contributed by Ivan Levkivskyi in bpo-32226(13).)

*note sorted(): b75. and *note list.sort(): b76. have been optimized for
common cases to be up to 40-75% faster.  (Contributed by Elliot
Gorokhovsky in bpo-28685(14).)

*note dict.copy(): b77. is now up to 5.5 times faster.  (Contributed by
Yury Selivanov in bpo-31179(15).)

*note hasattr(): 479. and *note getattr(): b78. are now about 4 times
faster when 'name' is not found and 'obj' does not override *note
object.__getattr__(): 47a. or *note object.__getattribute__(): b79.
(Contributed by INADA Naoki in bpo-32544(16).)

Searching for certain Unicode characters (like Ukrainian capital "Є") in
a string was up to 25 times slower than searching for other characters.
It is now only 3 times slower in the worst case.  (Contributed by Serhiy
Storchaka in bpo-24821(17).)

The *note collections.namedtuple(): 1ae. factory has been reimplemented
to make the creation of named tuples 4 to 6 times faster.  (Contributed
by Jelle Zijlstra with further improvements by INADA Naoki, Serhiy
Storchaka, and Raymond Hettinger in bpo-28638(18).)

‘date.fromordinal()’ and ‘date.fromtimestamp()’ are now up to 30% faster
in the common case.  (Contributed by Paul Ganssle in bpo-32403(19).)

The *note os.fwalk(): aff. function is now up to 2 times faster thanks
to the use of *note os.scandir(): a02.  (Contributed by Serhiy Storchaka
in bpo-25996(20).)

The speed of the *note shutil.rmtree(): 2d2. function has been improved
by 20-40% thanks to the use of the *note os.scandir(): a02. function.
(Contributed by Serhiy Storchaka in bpo-28564(21).)

Optimized case-insensitive matching and searching of *note regular
expressions: a7.  Searching some patterns can now be up to 20 times
faster.  (Contributed by Serhiy Storchaka in bpo-30285(22).)

*note re.compile(): b7a. now converts ‘flags’ parameter to int object if
it is ‘RegexFlag’.  It is now as fast as Python 3.5, and faster than
Python 3.6 by about 10% depending on the pattern.  (Contributed by INADA
Naoki in bpo-31671(23).)

The *note modify(): b7b. methods of classes *note
selectors.EpollSelector: b7c, *note selectors.PollSelector: b7d. and
*note selectors.DevpollSelector: b7e. may be around 10% faster under
heavy loads.  (Contributed by Giampaolo Rodola' in bpo-30014(24))

Constant folding has been moved from the peephole optimizer to the new
AST optimizer, which is able perform optimizations more consistently.
(Contributed by Eugene Toder and INADA Naoki in bpo-29469(25) and
bpo-11549(26).)

Most functions and methods in *note abc: 4. have been rewritten in C.
This makes creation of abstract base classes, and calling *note
isinstance(): 3e8. and *note issubclass(): 765. on them 1.5x faster.
This also reduces Python start-up time by up to 10%.  (Contributed by
Ivan Levkivskyi and INADA Naoki in bpo-31333(27))

Significant speed improvements to alternate constructors for *note
datetime.date: 1b1. and *note datetime.datetime: 1b0. by using fast-path
constructors when not constructing subclasses.  (Contributed by Paul
Ganssle in bpo-32403(28))

The speed of comparison of *note array.array: 186. instances has been
improved considerably in certain cases.  It is now from 10x to 70x
faster when comparing arrays holding values of the same integer type.
(Contributed by Adrian Wielgosik in bpo-24700(29).)

The *note math.erf(): b7f. and *note math.erfc(): b80. functions now use
the (faster) C library implementation on most platforms.  (Contributed
by Serhiy Storchaka in bpo-26121(30).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29300

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29507

   (3) https://bugs.python.org/issue?@action=redirect&bpo=29452

   (4) https://bugs.python.org/issue?@action=redirect&bpo=29286

   (5) https://bugs.python.org/issue?@action=redirect&bpo=29585

   (6) https://bugs.python.org/issue?@action=redirect&bpo=31333

   (7) https://bugs.python.org/issue?@action=redirect&bpo=26110

   (8) https://bugs.python.org/issue?@action=redirect&bpo=32296

   (9) https://bugs.python.org/issue?@action=redirect&bpo=32348

   (10) https://bugs.python.org/issue?@action=redirect&bpo=32355

   (11) https://bugs.python.org/issue?@action=redirect&bpo=32351

   (12) https://bugs.python.org/issue?@action=redirect&bpo=31970

   (13) https://bugs.python.org/issue?@action=redirect&bpo=32226

   (14) https://bugs.python.org/issue?@action=redirect&bpo=28685

   (15) https://bugs.python.org/issue?@action=redirect&bpo=31179

   (16) https://bugs.python.org/issue?@action=redirect&bpo=32544

   (17) https://bugs.python.org/issue?@action=redirect&bpo=24821

   (18) https://bugs.python.org/issue?@action=redirect&bpo=28638

   (19) https://bugs.python.org/issue?@action=redirect&bpo=32403

   (20) https://bugs.python.org/issue?@action=redirect&bpo=25996

   (21) https://bugs.python.org/issue?@action=redirect&bpo=28564

   (22) https://bugs.python.org/issue?@action=redirect&bpo=30285

   (23) https://bugs.python.org/issue?@action=redirect&bpo=31671

   (24) https://bugs.python.org/issue?@action=redirect&bpo=30014

   (25) https://bugs.python.org/issue?@action=redirect&bpo=29469

   (26) https://bugs.python.org/issue?@action=redirect&bpo=11549

   (27) https://bugs.python.org/issue?@action=redirect&bpo=31333

   (28) https://bugs.python.org/issue?@action=redirect&bpo=32403

   (29) https://bugs.python.org/issue?@action=redirect&bpo=24700

   (30) https://bugs.python.org/issue?@action=redirect&bpo=26121


File: python.info,  Node: Other CPython Implementation Changes,  Next: Deprecated Python Behavior,  Prev: 最佳化<6>,  Up: Python 3 7 有什麼新功能

1.7.9 Other CPython Implementation Changes
------------------------------------------

   * Trace hooks may now opt out of receiving the ‘line’ and opt into
     receiving the ‘opcode’ events from the interpreter by setting the
     corresponding new *note f_trace_lines: b82. and *note
     f_trace_opcodes: b83. attributes on the frame being traced.
     (Contributed by Nick Coghlan in bpo-31344(1).)

   * Fixed some consistency problems with namespace package module
     attributes.  Namespace module objects now have an ‘__file__’ that
     is set to ‘None’ (previously unset), and their ‘__spec__.origin’ is
     also set to ‘None’ (previously the string ‘"namespace"’).  See
     bpo-32305(2).  Also, the namespace module object's
     ‘__spec__.loader’ is set to the same value as ‘__loader__’
     (previously, the former was set to ‘None’).  See bpo-32303(3).

   * The *note locals(): 127. dictionary now displays in the lexical
     order that variables were defined.  Previously, the order was
     undefined.  (Contributed by Raymond Hettinger in bpo-32690(4).)

   * The ‘distutils’ ‘upload’ command no longer tries to change CR
     end-of-line characters to CRLF. This fixes a corruption issue with
     sdists that ended with a byte equivalent to CR. (Contributed by Bo
     Bayles in bpo-32304(5).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31344

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32305

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32303

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32690

   (5) https://bugs.python.org/issue?@action=redirect&bpo=32304


File: python.info,  Node: Deprecated Python Behavior,  Next: Deprecated Python modules functions and methods,  Prev: Other CPython Implementation Changes,  Up: Python 3 7 有什麼新功能

1.7.10 Deprecated Python Behavior
---------------------------------

Yield expressions (both ‘yield’ and ‘yield from’ clauses) are now
deprecated in comprehensions and generator expressions (aside from the
iterable expression in the leftmost ‘for’ clause).  This ensures that
comprehensions always immediately return a container of the appropriate
type (rather than potentially returning a *note generator iterator: b85.
object), while generator expressions won't attempt to interleave their
implicit output with the output from any explicit yield expressions.  In
Python 3.7, such expressions emit *note DeprecationWarning: 18b. when
compiled, in Python 3.8 this will be a *note SyntaxError: 173.
(Contributed by Serhiy Storchaka in bpo-10544(1).)

Returning a subclass of *note complex: 2c9. from *note
object.__complex__(): 58d. is deprecated and will be an error in future
Python versions.  This makes ‘__complex__()’ consistent with *note
object.__int__(): 6c0. and *note object.__float__(): 970.  (Contributed
by Serhiy Storchaka in bpo-28894(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=10544

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28894


File: python.info,  Node: Deprecated Python modules functions and methods,  Next: Deprecated functions and types of the C API,  Prev: Deprecated Python Behavior,  Up: Python 3 7 有什麼新功能

1.7.11 Deprecated Python modules, functions and methods
-------------------------------------------------------

* Menu:

* aifc::
* asyncio: asyncio<8>.
* collections: collections<3>.
* dbm: dbm<3>.
* enum: enum<5>.
* gettext: gettext<2>.
* importlib: importlib<5>.
* locale: locale<5>.
* macpath::
* threading: threading<5>.
* socket: socket<6>.
* ssl: ssl<6>.
* sunau::
* sys: sys<8>.
* wave::


File: python.info,  Node: aifc,  Next: asyncio<8>,  Up: Deprecated Python modules functions and methods

1.7.11.1 aifc
.............

‘aifc.openfp()’ has been deprecated and will be removed in Python 3.9.
Use ‘aifc.open()’ instead.  (Contributed by Brian Curtin in
bpo-31985(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31985


File: python.info,  Node: asyncio<8>,  Next: collections<3>,  Prev: aifc,  Up: Deprecated Python modules functions and methods

1.7.11.2 asyncio
................

Support for directly ‘await’-ing instances of *note asyncio.Lock: a14.
and other asyncio synchronization primitives has been deprecated.  An
asynchronous context manager must be used in order to acquire and
release the synchronization resource.  (Contributed by Andrew Svetlov in
bpo-32253(1).)

The ‘asyncio.Task.current_task()’ and ‘asyncio.Task.all_tasks()’ methods
have been deprecated.  (Contributed by Andrew Svetlov in bpo-32250(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32253

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32250


File: python.info,  Node: collections<3>,  Next: dbm<3>,  Prev: asyncio<8>,  Up: Deprecated Python modules functions and methods

1.7.11.3 collections
....................

In Python 3.8, the abstract base classes in *note collections.abc: 17.
will no longer be exposed in the regular *note collections: 16. module.
This will help create a clearer distinction between the concrete classes
and the abstract base classes.  (Contributed by Serhiy Storchaka in
bpo-25988(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25988


File: python.info,  Node: dbm<3>,  Next: enum<5>,  Prev: collections<3>,  Up: Deprecated Python modules functions and methods

1.7.11.4 dbm
............

*note dbm.dumb: 2a. now supports reading read-only files and no longer
writes the index file when it is not changed.  A deprecation warning is
now emitted if the index file is missing and recreated in the ‘'r'’ and
‘'w'’ modes (this will be an error in future Python releases).
(Contributed by Serhiy Storchaka in bpo-28847(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28847


File: python.info,  Node: enum<5>,  Next: gettext<2>,  Prev: dbm<3>,  Up: Deprecated Python modules functions and methods

1.7.11.5 enum
.............

In Python 3.8, attempting to check for non-Enum objects in ‘Enum’
classes will raise a *note TypeError: 4dd. (e.g.  ‘1 in Color’);
similarly, attempting to check for non-Flag objects in a ‘Flag’ member
will raise *note TypeError: 4dd. (e.g.  ‘1 in Perm.RW’); currently, both
operations return *note False: adb. instead.  (Contributed by Ethan
Furman in bpo-33217(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33217


File: python.info,  Node: gettext<2>,  Next: importlib<5>,  Prev: enum<5>,  Up: Deprecated Python modules functions and methods

1.7.11.6 gettext
................

Using non-integer value for selecting a plural form in *note gettext:
59. is now deprecated.  It never correctly worked.  (Contributed by
Serhiy Storchaka in bpo-28692(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28692


File: python.info,  Node: importlib<5>,  Next: locale<5>,  Prev: gettext<2>,  Up: Deprecated Python modules functions and methods

1.7.11.7 importlib
..................

Methods ‘MetaPathFinder.find_module()’ (replaced by *note
MetaPathFinder.find_spec(): 80d.) and ‘PathEntryFinder.find_loader()’
(replaced by *note PathEntryFinder.find_spec(): 811.) both deprecated in
Python 3.4 now emit *note DeprecationWarning: 18b.  (Contributed by
Matthias Bussonnier in bpo-29576(1).)

The *note importlib.abc.ResourceLoader: b8e. ABC has been deprecated in
favour of *note importlib.abc.ResourceReader: aa0.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29576


File: python.info,  Node: locale<5>,  Next: macpath,  Prev: importlib<5>,  Up: Deprecated Python modules functions and methods

1.7.11.8 locale
...............

‘locale.format()’ has been deprecated, use *note locale.format_string():
4c3. instead.  (Contributed by Garvit in bpo-10379(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=10379


File: python.info,  Node: macpath,  Next: threading<5>,  Prev: locale<5>,  Up: Deprecated Python modules functions and methods

1.7.11.9 macpath
................

The ‘macpath’ is now deprecated and will be removed in Python 3.8.
(Contributed by Chi Hsuan Yen in bpo-9850(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=9850


File: python.info,  Node: threading<5>,  Next: socket<6>,  Prev: macpath,  Up: Deprecated Python modules functions and methods

1.7.11.10 threading
...................

‘dummy_threading’ and ‘_dummy_thread’ have been deprecated.  It is no
longer possible to build Python with threading disabled.  Use *note
threading: d6. instead.  (Contributed by Antoine Pitrou in
bpo-31370(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31370


File: python.info,  Node: socket<6>,  Next: ssl<6>,  Prev: threading<5>,  Up: Deprecated Python modules functions and methods

1.7.11.11 socket
................

The silent argument value truncation in *note socket.htons(): 823. and
*note socket.ntohs(): 824. has been deprecated.  In future versions of
Python, if the passed argument is larger than 16 bits, an exception will
be raised.  (Contributed by Oren Milman in bpo-28332(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28332


File: python.info,  Node: ssl<6>,  Next: sunau,  Prev: socket<6>,  Up: Deprecated Python modules functions and methods

1.7.11.12 ssl
.............

‘ssl.wrap_socket()’ is deprecated.  Use *note
ssl.SSLContext.wrap_socket(): 4c9. instead.  (Contributed by Christian
Heimes in bpo-28124(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28124


File: python.info,  Node: sunau,  Next: sys<8>,  Prev: ssl<6>,  Up: Deprecated Python modules functions and methods

1.7.11.13 sunau
...............

‘sunau.openfp()’ has been deprecated and will be removed in Python 3.9.
Use ‘sunau.open()’ instead.  (Contributed by Brian Curtin in
bpo-31985(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31985


File: python.info,  Node: sys<8>,  Next: wave,  Prev: sunau,  Up: Deprecated Python modules functions and methods

1.7.11.14 sys
.............

Deprecated ‘sys.set_coroutine_wrapper()’ and
‘sys.get_coroutine_wrapper()’.

The undocumented ‘sys.callstats()’ function has been deprecated and will
be removed in a future Python version.  (Contributed by Victor Stinner
in bpo-28799(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28799


File: python.info,  Node: wave,  Prev: sys<8>,  Up: Deprecated Python modules functions and methods

1.7.11.15 wave
..............

‘wave.openfp()’ has been deprecated and will be removed in Python 3.9.
Use *note wave.open(): 8ef. instead.  (Contributed by Brian Curtin in
bpo-31985(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31985


File: python.info,  Node: Deprecated functions and types of the C API,  Next: Platform Support Removals,  Prev: Deprecated Python modules functions and methods,  Up: Python 3 7 有什麼新功能

1.7.12 Deprecated functions and types of the C API
--------------------------------------------------

Function *note PySlice_GetIndicesEx(): 3c4. is deprecated and replaced
with a macro if ‘Py_LIMITED_API’ is not set or set to a value in the
range between ‘0x03050400’ and ‘0x03060000’ (not inclusive), or is
‘0x03060100’ or higher.  (Contributed by Serhiy Storchaka in
bpo-27867(1).)

*note PyOS_AfterFork(): 3c2. has been deprecated.  Use *note
PyOS_BeforeFork(): b66, *note PyOS_AfterFork_Parent(): b67. or *note
PyOS_AfterFork_Child(): 3c3. instead.  (Contributed by Antoine Pitrou in
bpo-16500(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27867

   (2) https://bugs.python.org/issue?@action=redirect&bpo=16500


File: python.info,  Node: Platform Support Removals,  Next: API and Feature Removals<2>,  Prev: Deprecated functions and types of the C API,  Up: Python 3 7 有什麼新功能

1.7.13 Platform Support Removals
--------------------------------

   * FreeBSD 9 and older are no longer officially supported.

   * For full Unicode support, including within extension modules, *nix
     platforms are now expected to provide at least one of ‘C.UTF-8’
     (full locale), ‘C.utf8’ (full locale) or ‘UTF-8’ (‘LC_CTYPE’-only
     locale) as an alternative to the legacy ‘ASCII’-based ‘C’ locale.

   * OpenSSL 0.9.8 and 1.0.1 are no longer supported, which means
     building CPython 3.7 with SSL/TLS support on older platforms still
     using these versions requires custom build options that link to a
     more recent version of OpenSSL.

     Notably, this issue affects the Debian 8 (aka "jessie") and Ubuntu
     14.04 (aka "Trusty") LTS Linux distributions, as they still use
     OpenSSL 1.0.1 by default.

     Debian 9 ("stretch") and Ubuntu 16.04 ("xenial"), as well as recent
     releases of other LTS Linux releases (e.g.  RHEL/CentOS 7.5, SLES
     12-SP3), use OpenSSL 1.0.2 or later, and remain supported in the
     default build configuration.

     CPython's own CI configuration file(1) provides an example of using
     the SSL compatibility testing infrastructure(2) in CPython's test
     suite to build and link against OpenSSL 1.1.0 rather than an
     outdated system provided OpenSSL.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/blob/v3.7.13/.travis.yml

   (2) 
https://github.com/python/cpython/tree/3.13/Tools/ssl/multissltests.py


File: python.info,  Node: API and Feature Removals<2>,  Next: Module Removals,  Prev: Platform Support Removals,  Up: Python 3 7 有什麼新功能

1.7.14 API and Feature Removals
-------------------------------

The following features and APIs have been removed from Python 3.7:

   * The ‘os.stat_float_times()’ function has been removed.  It was
     introduced in Python 2.3 for backward compatibility with Python
     2.2, and was deprecated since Python 3.1.

   * Unknown escapes consisting of ‘'\'’ and an ASCII letter in
     replacement templates for *note re.sub(): 283. were deprecated in
     Python 3.5, and will now cause an error.

   * Removed support of the 'exclude' argument in *note
     tarfile.TarFile.add(): b9a.  It was deprecated in Python 2.7 and
     3.2.  Use the 'filter' argument instead.

   * The ‘ntpath.splitunc()’ function was deprecated in Python 3.1, and
     has now been removed.  Use *note splitdrive(): b9b. instead.

   * *note collections.namedtuple(): 1ae. no longer supports the
     'verbose' parameter or ‘_source’ attribute which showed the
     generated source code for the named tuple class.  This was part of
     an optimization designed to speed-up class creation.  (Contributed
     by Jelle Zijlstra with further improvements by INADA Naoki, Serhiy
     Storchaka, and Raymond Hettinger in bpo-28638(1).)

   * Functions *note bool(): 40e, *note float(): 2c8, *note list(): 5b6.
     and *note tuple(): 322. no longer take keyword arguments.  The
     first argument of *note int(): 23c. can now be passed only as
     positional argument.

   * Removed previously deprecated in Python 2.4 classes ‘Plist’, ‘Dict’
     and ‘_InternalDict’ in the *note plistlib: 99. module.  Dict values
     in the result of functions ‘readPlist()’ and ‘readPlistFromBytes()’
     are now normal dicts.  You no longer can use attribute access to
     access items of these dictionaries.

   * The ‘asyncio.windows_utils.socketpair()’ function has been removed.
     Use the *note socket.socketpair(): b9c. function instead, it is
     available on all platforms since Python 3.5.
     ‘asyncio.windows_utils.socketpair’ was just an alias to
     ‘socket.socketpair’ on Python 3.5 and newer.

   * *note asyncio: 8. no longer exports the *note selectors: b0. and
     ‘_overlapped’ modules as ‘asyncio.selectors’ and
     ‘asyncio._overlapped’.  Replace ‘from asyncio import selectors’
     with ‘import selectors’.

   * Direct instantiation of *note ssl.SSLSocket: 88f. and *note
     ssl.SSLObject: b25. objects is now prohibited.  The constructors
     were never documented, tested, or designed as public constructors.
     Users were supposed to use ‘ssl.wrap_socket()’ or *note
     ssl.SSLContext: 276.  (Contributed by Christian Heimes in
     bpo-32951(2).)

   * The unused ‘distutils’ ‘install_misc’ command has been removed.
     (Contributed by Eric N. Vander Weele in bpo-29218(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28638

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32951

   (3) https://bugs.python.org/issue?@action=redirect&bpo=29218


File: python.info,  Node: Module Removals,  Next: Windows-only Changes,  Prev: API and Feature Removals<2>,  Up: Python 3 7 有什麼新功能

1.7.15 Module Removals
----------------------

The ‘fpectl’ module has been removed.  It was never enabled by default,
never worked correctly on x86-64, and it changed the Python ABI in ways
that caused unexpected breakage of C extensions.  (Contributed by
Nathaniel J. Smith in bpo-29137(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29137


File: python.info,  Node: Windows-only Changes,  Next: Porting to Python 3 7,  Prev: Module Removals,  Up: Python 3 7 有什麼新功能

1.7.16 Windows-only Changes
---------------------------

The python launcher, (py.exe), can accept 32 & 64 bit specifiers
'without' having to specify a minor version as well.  So ‘py -3-32’ and
‘py -3-64’ become valid as well as ‘py -3.7-32’, also the -'m'-64 and
-'m.n'-64 forms are now accepted to force 64 bit python even if 32 bit
would have otherwise been used.  If the specified version is not
available py.exe will error exit.  (Contributed by Steve Barnes in
bpo-30291(1).)

The launcher can be run as ‘py -0’ to produce a list of the installed
pythons, 'with default marked with an asterisk'.  Running ‘py -0p’ will
include the paths.  If py is run with a version specifier that cannot be
matched it will also print the 'short form' list of available
specifiers.  (Contributed by Steve Barnes in bpo-30362(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30291

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30362


File: python.info,  Node: Porting to Python 3 7,  Next: Python 3 7 1 中顯著的變更,  Prev: Windows-only Changes,  Up: Python 3 7 有什麼新功能

1.7.17 Porting to Python 3.7
----------------------------

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

* Menu:

* Changes in Python Behavior::
* Changes in the Python API: Changes in the Python API<5>.
* C API 中的改動: C API 中的改動<4>.
* CPython 位元組碼變更: CPython 位元組碼變更<6>.
* Windows-only Changes: Windows-only Changes<2>.
* Other CPython implementation changes::


File: python.info,  Node: Changes in Python Behavior,  Next: Changes in the Python API<5>,  Up: Porting to Python 3 7

1.7.17.1 Changes in Python Behavior
...................................

   * *note async: 6d6. and *note await: 19f. names are now reserved
     keywords.  Code using these names as identifiers will now raise a
     *note SyntaxError: 173.  (Contributed by Jelle Zijlstra in
     bpo-30406(1).)

   * PEP 479(2) is enabled for all code in Python 3.7, meaning that
     *note StopIteration: ba1. exceptions raised directly or indirectly
     in coroutines and generators are transformed into *note
     RuntimeError: 179. exceptions.  (Contributed by Yury Selivanov in
     bpo-32670(3).)

   * *note object.__aiter__(): ba2. methods can no longer be declared as
     asynchronous.  (Contributed by Yury Selivanov in bpo-31709(4).)

   * Due to an oversight, earlier Python versions erroneously accepted
     the following syntax:

          f(1 for x in [1],)

          class C(1 for x in [1]):
              pass

     Python 3.7 now correctly raises a *note SyntaxError: 173, as a
     generator expression always needs to be directly inside a set of
     parentheses and cannot have a comma on either side, and the
     duplication of the parentheses can be omitted only on calls.
     (Contributed by Serhiy Storchaka in bpo-32012(5) and bpo-32023(6).)

   * When using the *note -m: 585. switch, the initial working directory
     is now added to *note sys.path: 37f, rather than an empty string
     (which dynamically denoted the current working directory at the
     time of each import).  Any programs that are checking for the empty
     string, or otherwise relying on the previous behaviour, will need
     to be updated accordingly (e.g.  by also checking for ‘os.getcwd()’
     or ‘os.path.dirname(__main__.__file__)’, depending on why the code
     was checking for the empty string in the first place).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30406

   (2) https://peps.python.org/pep-0479/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32670

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31709

   (5) https://bugs.python.org/issue?@action=redirect&bpo=32012

   (6) https://bugs.python.org/issue?@action=redirect&bpo=32023


File: python.info,  Node: Changes in the Python API<5>,  Next: C API 中的改動<4>,  Prev: Changes in Python Behavior,  Up: Porting to Python 3 7

1.7.17.2 Changes in the Python API
..................................

   * ‘socketserver.ThreadingMixIn.server_close()’ now waits until all
     non-daemon threads complete.  Set the new *note
     socketserver.ThreadingMixIn.block_on_close: ba4. class attribute to
     ‘False’ to get the pre-3.7 behaviour.  (Contributed by Victor
     Stinner in bpo-31233(1) and bpo-33540(2).)

   * ‘socketserver.ForkingMixIn.server_close()’ now waits until all
     child processes complete.  Set the new
     ‘socketserver.ForkingMixIn.block_on_close’ class attribute to
     ‘False’ to get the pre-3.7 behaviour.  (Contributed by Victor
     Stinner in bpo-31151(3) and bpo-33540(4).)

   * The *note locale.localeconv(): ba5. function now temporarily sets
     the ‘LC_CTYPE’ locale to the value of ‘LC_NUMERIC’ in some cases.
     (Contributed by Victor Stinner in bpo-31900(5).)

   * *note pkgutil.walk_packages(): ba6. now raises a *note ValueError:
     1e7. if 'path' is a string.  Previously an empty list was returned.
     (Contributed by Sanyam Khurana in bpo-24744(6).)

   * A format string argument for *note string.Formatter.format(): ba7.
     is now *note positional-only: a28.  Passing it as a keyword
     argument was deprecated in Python 3.5.  (Contributed by Serhiy
     Storchaka in bpo-29193(7).)

   * Attributes *note key: ba8, *note value: ba9. and *note coded_value:
     baa. of class *note http.cookies.Morsel: bab. are now read-only.
     Assigning to them was deprecated in Python 3.5.  Use the *note
     set(): bac. method for setting them.  (Contributed by Serhiy
     Storchaka in bpo-29192(8).)

   * The 'mode' argument of *note os.makedirs(): 203. no longer affects
     the file permission bits of newly created intermediate-level
     directories.  To set their file permission bits you can set the
     umask before invoking ‘makedirs()’.  (Contributed by Serhiy
     Storchaka in bpo-19930(9).)

   * The *note struct.Struct.format: bad. type is now *note str: 3f2.
     instead of *note bytes: 1a5.  (Contributed by Victor Stinner in
     bpo-21071(10).)

   * ‘cgi.parse_multipart()’ now accepts the 'encoding' and 'errors'
     arguments and returns the same results as ‘FieldStorage’: for
     non-file fields, the value associated to a key is a list of
     strings, not bytes.  (Contributed by Pierre Quentel in
     bpo-29979(11).)

   * Due to internal changes in *note socket: b8, calling *note
     socket.fromshare(): bae. on a socket created by *note socket.share:
     baf. in older Python versions is not supported.

   * ‘repr’ for *note BaseException: 55f. has changed to not include the
     trailing comma.  Most exceptions are affected by this change.
     (Contributed by Serhiy Storchaka in bpo-30399(12).)

   * ‘repr’ for *note datetime.timedelta: 973. has changed to include
     the keyword arguments in the output.  (Contributed by Utkarsh
     Upadhyay in bpo-30302(13).)

   * Because *note shutil.rmtree(): 2d2. is now implemented using the
     *note os.scandir(): a02. function, the user specified handler
     'onerror' is now called with the first argument ‘os.scandir’
     instead of ‘os.listdir’ when listing the directory is failed.

   * Support for nested sets and set operations in regular expressions
     as in Unicode Technical Standard #18(14) might be added in the
     future.  This would change the syntax.  To facilitate this future
     change a *note FutureWarning: 357. will be raised in ambiguous
     cases for the time being.  That include sets starting with a
     literal ‘'['’ or containing literal character sequences ‘'--'’,
     ‘'&&'’, ‘'~~'’, and ‘'||'’.  To avoid a warning, escape them with a
     backslash.  (Contributed by Serhiy Storchaka in bpo-30349(15).)

   * The result of splitting a string on a *note regular expression: a7.
     that could match an empty string has been changed.  For example
     splitting on ‘r'\s*'’ will now split not only on whitespaces as it
     did previously, but also on empty strings before all non-whitespace
     characters and just before the end of the string.  The previous
     behavior can be restored by changing the pattern to ‘r'\s+'’.  A
     *note FutureWarning: 357. was emitted for such patterns since
     Python 3.5.

     For patterns that match both empty and non-empty strings, the
     result of searching for all matches may also be changed in other
     cases.  For example in the string ‘'a\n\n'’, the pattern
     ‘r'(?m)^\s*?$'’ will not only match empty strings at positions 2
     and 3, but also the string ‘'\n'’ at positions 2-3.  To match only
     blank lines, the pattern should be rewritten as
     ‘r'(?m)^[^\S\n]*$'’.

     *note re.sub(): 283. now replaces empty matches adjacent to a
     previous non-empty match.  For example ‘re.sub('x*', '-', 'abxd')’
     returns now ‘'-a-b--d-'’ instead of ‘'-a-b-d-'’ (the first minus
     between 'b' and 'd' replaces 'x', and the second minus replaces an
     empty string between 'x' and 'd').

     （由 Serhiy Storchaka 在 bpo-25054(16) 和 bpo-32308(17) 中貢獻。）

   * Change *note re.escape(): bb0. to only escape regex special
     characters instead of escaping all characters other than ASCII
     letters, numbers, and ‘'_'’.  (Contributed by Serhiy Storchaka in
     bpo-29995(18).)

   * *note tracemalloc.Traceback: b3d. frames are now sorted from oldest
     to most recent to be more consistent with *note traceback: e7.
     (Contributed by Jesse Bakker in bpo-32121(19).)

   * On OSes that support *note socket.SOCK_NONBLOCK: bb1. or *note
     socket.SOCK_CLOEXEC: bb2. bit flags, the *note socket.type: bb3. no
     longer has them applied.  Therefore, checks like ‘if sock.type ==
     socket.SOCK_STREAM’ work as expected on all platforms.
     (Contributed by Yury Selivanov in bpo-32331(20).)

   * On Windows the default for the 'close_fds' argument of *note
     subprocess.Popen: 17d. was changed from *note False: adb. to *note
     True: bb4. when redirecting the standard handles.  If you
     previously depended on handles being inherited when using *note
     subprocess.Popen: 17d. with standard io redirection, you will have
     to pass ‘close_fds=False’ to preserve the previous behaviour, or
     use *note STARTUPINFO.lpAttributeList: bb5.

   * *note importlib.machinery.PathFinder.invalidate_caches(): bb6. -
     which implicitly affects *note importlib.invalidate_caches(): bb7.
     - now deletes entries in *note sys.path_importer_cache: 588. which
     are set to ‘None’.  (Contributed by Brett Cannon in bpo-33169(21).)

   * In *note asyncio: 8, *note loop.sock_recv(): bb8, *note
     loop.sock_sendall(): bb9, *note loop.sock_accept(): bba, *note
     loop.getaddrinfo(): bbb, *note loop.getnameinfo(): bbc. have been
     changed to be proper coroutine methods to match their
     documentation.  Previously, these methods returned *note
     asyncio.Future: b74. instances.  (Contributed by Yury Selivanov in
     bpo-32327(22).)

   * *note asyncio.Server.sockets: bbd. now returns a copy of the
     internal list of server sockets, instead of returning it directly.
     (Contributed by Yury Selivanov in bpo-32662(23).)

   * *note Struct.format: bad. is now a *note str: 3f2. instance instead
     of a *note bytes: 1a5. instance.  (Contributed by Victor Stinner in
     bpo-21071(24).)

   * *note argparse: 5. subparsers can now be made mandatory by passing
     ‘required=True’ to *note ArgumentParser.add_subparsers(): bbe.
     (Contributed by Anthony Sottile in bpo-26510(25).)

   * *note ast.literal_eval(): bbf. is now stricter.  Addition and
     subtraction of arbitrary numbers are no longer allowed.
     (Contributed by Serhiy Storchaka in bpo-31778(26).)

   * *note Calendar.itermonthdates: bc0. will now consistently raise an
     exception when a date falls outside of the ‘0001-01-01’ through
     ‘9999-12-31’ range.  To support applications that cannot tolerate
     such exceptions, the new *note Calendar.itermonthdays3: bc1. and
     *note Calendar.itermonthdays4: bc2. can be used.  The new methods
     return tuples and are not restricted by the range supported by
     *note datetime.date: 1b1.  (Contributed by Alexander Belopolsky in
     bpo-28292(27).)

   * *note collections.ChainMap: bc3. now preserves the order of the
     underlying mappings.  (Contributed by Raymond Hettinger in
     bpo-32792(28).)

   * The ‘submit()’ method of *note
     concurrent.futures.ThreadPoolExecutor: 6e6. and *note
     concurrent.futures.ProcessPoolExecutor: 893. now raises a *note
     RuntimeError: 179. if called during interpreter shutdown.
     (Contributed by Mark Nemec in bpo-33097(29).)

   * The *note configparser.ConfigParser: 1aa. constructor now uses
     ‘read_dict()’ to process the default values, making its behavior
     consistent with the rest of the parser.  Non-string keys and values
     in the defaults dictionary are now being implicitly converted to
     strings.  (Contributed by James Tocknell in bpo-23835(30).)

   * Several undocumented internal imports were removed.  One example is
     that ‘os.errno’ is no longer available; use ‘import errno’ directly
     instead.  Note that such undocumented internal imports may be
     removed any time without notice, even in micro version releases.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31233

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33540

   (3) https://bugs.python.org/issue?@action=redirect&bpo=31151

   (4) https://bugs.python.org/issue?@action=redirect&bpo=33540

   (5) https://bugs.python.org/issue?@action=redirect&bpo=31900

   (6) https://bugs.python.org/issue?@action=redirect&bpo=24744

   (7) https://bugs.python.org/issue?@action=redirect&bpo=29193

   (8) https://bugs.python.org/issue?@action=redirect&bpo=29192

   (9) https://bugs.python.org/issue?@action=redirect&bpo=19930

   (10) https://bugs.python.org/issue?@action=redirect&bpo=21071

   (11) https://bugs.python.org/issue?@action=redirect&bpo=29979

   (12) https://bugs.python.org/issue?@action=redirect&bpo=30399

   (13) https://bugs.python.org/issue?@action=redirect&bpo=30302

   (14) https://unicode.org/reports/tr18/

   (15) https://bugs.python.org/issue?@action=redirect&bpo=30349

   (16) https://bugs.python.org/issue?@action=redirect&bpo=25054

   (17) https://bugs.python.org/issue?@action=redirect&bpo=32308

   (18) https://bugs.python.org/issue?@action=redirect&bpo=29995

   (19) https://bugs.python.org/issue?@action=redirect&bpo=32121

   (20) https://bugs.python.org/issue?@action=redirect&bpo=32331

   (21) https://bugs.python.org/issue?@action=redirect&bpo=33169

   (22) https://bugs.python.org/issue?@action=redirect&bpo=32327

   (23) https://bugs.python.org/issue?@action=redirect&bpo=32662

   (24) https://bugs.python.org/issue?@action=redirect&bpo=21071

   (25) https://bugs.python.org/issue?@action=redirect&bpo=26510

   (26) https://bugs.python.org/issue?@action=redirect&bpo=31778

   (27) https://bugs.python.org/issue?@action=redirect&bpo=28292

   (28) https://bugs.python.org/issue?@action=redirect&bpo=32792

   (29) https://bugs.python.org/issue?@action=redirect&bpo=33097

   (30) https://bugs.python.org/issue?@action=redirect&bpo=23835


File: python.info,  Node: C API 中的改動<4>,  Next: CPython 位元組碼變更<6>,  Prev: Changes in the Python API<5>,  Up: Porting to Python 3 7

1.7.17.3 C API 中的改動
.......................

The function *note PySlice_GetIndicesEx(): 3c4. is considered unsafe for
resizable sequences.  If the slice indices are not instances of *note
int: 23c, but objects that implement the ‘__index__()’ method, the
sequence can be resized after passing its length to
‘PySlice_GetIndicesEx()’.  This can lead to returning indices out of the
length of the sequence.  For avoiding possible problems use new
functions *note PySlice_Unpack(): 3c5. and *note
PySlice_AdjustIndices(): 3c6.  (Contributed by Serhiy Storchaka in
bpo-27867(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27867


File: python.info,  Node: CPython 位元組碼變更<6>,  Next: Windows-only Changes<2>,  Prev: C API 中的改動<4>,  Up: Porting to Python 3 7

1.7.17.4 CPython 位元組碼變更
.............................

There are two new opcodes: *note LOAD_METHOD: bc6. and ‘CALL_METHOD’.
(Contributed by Yury Selivanov and INADA Naoki in bpo-26110(1).)

The ‘STORE_ANNOTATION’ opcode has been removed.  (Contributed by Mark
Shannon in bpo-32550(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26110

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32550


File: python.info,  Node: Windows-only Changes<2>,  Next: Other CPython implementation changes,  Prev: CPython 位元組碼變更<6>,  Up: Porting to Python 3 7

1.7.17.5 Windows-only Changes
.............................

The file used to override *note sys.path: 37f. is now called
‘<python-executable>._pth’ instead of ‘'sys.path'’.  See *note 找尋模組:
bc8. for more information.  (Contributed by Steve Dower in
bpo-28137(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28137


File: python.info,  Node: Other CPython implementation changes,  Prev: Windows-only Changes<2>,  Up: Porting to Python 3 7

1.7.17.6 Other CPython implementation changes
.............................................

In preparation for potential future changes to the public CPython
runtime initialization API (see PEP 432(1) for an initial, but somewhat
outdated, draft), CPython's internal startup and configuration
management logic has been significantly refactored.  While these updates
are intended to be entirely transparent to both embedding applications
and users of the regular CPython CLI, they're being mentioned here as
the refactoring changes the internal order of various operations during
interpreter startup, and hence may uncover previously latent defects,
either in embedding applications, or in CPython itself.  (Initially
contributed by Nick Coghlan and Eric Snow as part of bpo-22257(2), and
further updated by Nick, Eric, and Victor Stinner in a number of other
issues).  Some known details affected:

   * ‘PySys_AddWarnOptionUnicode()’ is not currently usable by embedding
     applications due to the requirement to create a Unicode object
     prior to calling ‘Py_Initialize’.  Use ‘PySys_AddWarnOption()’
     instead.

   * warnings filters added by an embedding application with
     ‘PySys_AddWarnOption()’ should now more consistently take
     precedence over the default filters set by the interpreter

Due to changes in the way the default warnings filters are configured,
setting *note Py_BytesWarningFlag: 39f. to a value greater than one is
no longer sufficient to both emit *note BytesWarning: bca. messages and
have them converted to exceptions.  Instead, the flag must be set (to
cause the warnings to be emitted in the first place), and an explicit
‘error::BytesWarning’ warnings filter added to convert them to
exceptions.

Due to a change in the way docstrings are handled by the compiler, the
implicit ‘return None’ in a function body consisting solely of a
docstring is now marked as occurring on the same line as the docstring,
not on the function's header line.

The current exception state has been moved from the frame object to the
co-routine.  This simplified the interpreter and fixed a couple of
obscure bugs caused by having swap exception state when entering or
exiting a generator.  (Contributed by Mark Shannon in bpo-25612(3).)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0432/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=22257

   (3) https://bugs.python.org/issue?@action=redirect&bpo=25612


File: python.info,  Node: Python 3 7 1 中顯著的變更,  Next: Python 3 7 2 中顯著的變更,  Prev: Porting to Python 3 7,  Up: Python 3 7 有什麼新功能

1.7.18 Python 3.7.1 中顯著的變更
--------------------------------

Starting in 3.7.1, *note Py_Initialize(): 851. now consistently reads
and respects all of the same environment settings as *note Py_Main():
bcc. (in earlier Python versions, it respected an ill-defined subset of
those environment variables, while in Python 3.7.0 it didn't read any of
them due to bpo-34247(1)).  If this behavior is unwanted, set *note
Py_IgnoreEnvironmentFlag: 3a3. to 1 before calling *note
Py_Initialize(): 851.

In 3.7.1 the C API for Context Variables *note was updated: bcd. to use
*note PyObject: 311. pointers.  See also bpo-34762(2).

In 3.7.1 the *note tokenize: e4. module now implicitly emits a ‘NEWLINE’
token when provided with input that does not have a trailing new line.
This behavior now matches what the C tokenizer does internally.
(Contributed by Ammar Askar in bpo-33899(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=34247

   (2) https://bugs.python.org/issue?@action=redirect&bpo=34762

   (3) https://bugs.python.org/issue?@action=redirect&bpo=33899


File: python.info,  Node: Python 3 7 2 中顯著的變更,  Next: Python 3 7 6 中顯著的變更,  Prev: Python 3 7 1 中顯著的變更,  Up: Python 3 7 有什麼新功能

1.7.19 Python 3.7.2 中顯著的變更
--------------------------------

In 3.7.2, *note venv: f9. on Windows no longer copies the original
binaries, but creates redirector scripts named ‘python.exe’ and
‘pythonw.exe’ instead.  This resolves a long standing issue where all
virtual environments would have to be upgraded or recreated with each
Python update.  However, note that this release will still require
recreation of virtual environments in order to get the new scripts.


File: python.info,  Node: Python 3 7 6 中顯著的變更,  Next: Python 3 7 10 中顯著的變更,  Prev: Python 3 7 2 中顯著的變更,  Up: Python 3 7 有什麼新功能

1.7.20 Python 3.7.6 中顯著的變更
--------------------------------

Due to significant security concerns, the 'reuse_address' parameter of
*note asyncio.loop.create_datagram_endpoint(): 6d7. is no longer
supported.  This is because of the behavior of the socket option
‘SO_REUSEADDR’ in UDP. For more details, see the documentation for
‘loop.create_datagram_endpoint()’.  (Contributed by Kyle Stanley,
Antoine Pitrou, and Yury Selivanov in bpo-37228(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=37228


File: python.info,  Node: Python 3 7 10 中顯著的變更,  Next: Python 3 7 11 中顯著的變更,  Prev: Python 3 7 6 中顯著的變更,  Up: Python 3 7 有什麼新功能

1.7.21 Python 3.7.10 中顯著的變更
---------------------------------

Earlier Python versions allowed using both ‘;’ and ‘&’ as query
parameter separators in *note urllib.parse.parse_qs(): 25f. and *note
urllib.parse.parse_qsl(): 25e.  Due to security concerns, and to conform
with newer W3C recommendations, this has been changed to allow only a
single separator key, with ‘&’ as the default.  This change also affects
‘cgi.parse()’ and ‘cgi.parse_multipart()’ as they use the affected
functions internally.  For more details, please see their respective
documentation.  (Contributed by Adam Goldschmidt, Senthil Kumaran and
Ken Jin in bpo-42967(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42967


File: python.info,  Node: Python 3 7 11 中顯著的變更,  Next: Notable security feature in 3 7 14,  Prev: Python 3 7 10 中顯著的變更,  Up: Python 3 7 有什麼新功能

1.7.22 Python 3.7.11 中顯著的變更
---------------------------------

A security fix alters the *note ftplib.FTP: 89f. behavior to not trust
the IPv4 address sent from the remote server when setting up a passive
data channel.  We reuse the ftp server IP address instead.  For unusual
code requiring the old behavior, set a ‘trust_server_pasv_ipv4_address’
attribute on your FTP instance to ‘True’.  (See gh-87451(1))

The presence of newline or tab characters in parts of a URL allows for
some forms of attacks.  Following the WHATWG specification that updates
RFC 3986, ASCII newline ‘\n’, ‘\r’ and tab ‘\t’ characters are stripped
from the URL by the parser *note urllib.parse(): f3. preventing such
attacks.  The removal characters are controlled by a new module level
variable ‘urllib.parse._UNSAFE_URL_BYTES_TO_REMOVE’.  (See gh-88048(2))

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/87451

   (2) https://github.com/python/cpython/issues/88048


File: python.info,  Node: Notable security feature in 3 7 14,  Prev: Python 3 7 11 中顯著的變更,  Up: Python 3 7 有什麼新功能

1.7.23 Notable security feature in 3.7.14
-----------------------------------------

Converting between *note int: 23c. and *note str: 3f2. in bases other
than 2 (binary), 4, 8 (octal), 16 (hexadecimal), or 32 such as base 10
(decimal) now raises a *note ValueError: 1e7. if the number of digits in
string form is above a limit to avoid potential denial of service
attacks due to the algorithmic complexity.  This is a mitigation for
CVE-2020-10735(1).  This limit can be configured or disabled by
environment variable, command line flag, or *note sys: c3. APIs.  See
the *note integer string conversion length limitation: 599.
documentation.  The default limit is 4300 digits in string form.

   ---------- Footnotes ----------

   (1) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10735


File: python.info,  Node: Python 3 6 有什麼新功能,  Next: Python 3 4 有什麼新功能,  Prev: Python 3 7 有什麼新功能,  Up: Python 有什麼新功能？

1.8 Python 3.6 有什麼新功能
===========================


編輯者: Elvis Pranskevichus <<elvis@magic.io>>, Yury Selivanov
<<yury@magic.io>>

This article explains the new features in Python 3.6, compared to 3.5.
Python 3.6 was released on December 23, 2016.   See the changelog(1) for
a full list of changes.

也參考
......

PEP 494(2) - Python 3.6 Release Schedule

* Menu:

* Summary: Summary -- Release highlights<3>. Release highlights
* New Features: New Features<7>.
* 其他語言更動: 其他語言更動<7>.
* 新模組: 新模組<4>.
* 改進的模組: 改進的模組<7>.
* 最佳化: 最佳化<7>.
* Build and C API Changes: Build and C API Changes<2>.
* Other Improvements::
* 已棄用: 已棄用<9>.
* 已移除: 已移除<7>.
* Porting to Python 3.6: Porting to Python 3 6.
* Python 3.6.2 中顯著的變更: Python 3 6 2 中顯著的變更.
* Python 3.6.4 中顯著的變更: Python 3 6 4 中顯著的變更.
* Python 3.6.5 中顯著的變更: Python 3 6 5 中顯著的變更.
* Python 3.6.7 中顯著的變更: Python 3 6 7 中顯著的變更.
* Python 3.6.10 中顯著的變更: Python 3 6 10 中顯著的變更.
* Python 3.6.13 中顯著的變更: Python 3 6 13 中顯著的變更.
* Python 3.6.14 中顯著的變更: Python 3 6 14 中顯著的變更.

   ---------- Footnotes ----------

   (1) https://docs.python.org/3.6/whatsnew/changelog.html

   (2) https://peps.python.org/pep-0494/


File: python.info,  Node: Summary -- Release highlights<3>,  Next: New Features<7>,  Up: Python 3 6 有什麼新功能

1.8.1 Summary - Release highlights
----------------------------------

新增語法特性：

   * *note PEP 498: bd6, formatted string literals.

   * *note PEP 515: bd7, underscores in numeric literals.

   * *note PEP 526: bd8, syntax for variable annotations.

   * *note PEP 525: bd9, asynchronous generators.

   * *note PEP 530: bda.: asynchronous comprehensions.

New library modules:

   * *note secrets: ae.: *note PEP 506 - Adding A Secrets Module To The
     Standard Library: bdb.

CPython implementation improvements:

   * The *note dict: a69. type has been reimplemented to use a *note
     more compact representation: bdc. based on a proposal by Raymond
     Hettinger(1) and similar to the PyPy dict implementation(2).  This
     resulted in dictionaries using 20% to 25% less memory when compared
     to Python 3.5.

   * Customization of class creation has been simplified with the *note
     new protocol: bdd.

   * The class attribute definition order is *note now preserved: bde.

   * The order of elements in ‘**kwargs’ now *note corresponds to the
     order: bdf. in which keyword arguments were passed to the function.

   * DTrace and SystemTap *note probing support: be0. has been added.

   * The new *note PYTHONMALLOC: be1. environment variable can now be
     used to debug the interpreter memory allocation and access errors.

Significant improvements in the standard library:

   * The *note asyncio: 8. module has received new features, significant
     usability and performance improvements, and a fair amount of bug
     fixes.  Starting with Python 3.6 the ‘asyncio’ module is no longer
     provisional and its API is considered stable.

   * A new *note file system path protocol: be2. has been implemented to
     support *note path-like objects: ac2.  All standard library
     functions operating on paths have been updated to work with the new
     protocol.

   * The *note datetime: 28. module has gained support for *note Local
     Time Disambiguation: be3.

   * The *note typing: ed. module received a number of *note
     improvements: be4.

   * The *note tracemalloc: e8. module has been significantly reworked
     and is now used to provide better output for *note ResourceWarning:
     229. as well as provide better diagnostics for memory allocation
     errors.  See the *note PYTHONMALLOC section: be1. for more
     information.

安全性改進：

   * The new *note secrets: ae. module has been added to simplify the
     generation of cryptographically strong pseudo-random numbers
     suitable for managing secrets such as account authentication,
     tokens, and similar.

   * On Linux, *note os.urandom(): 4c7. now blocks until the system
     urandom entropy pool is initialized to increase the security.  See
     the PEP 524(3) for the rationale.

   * The *note hashlib: 5e. and *note ssl: bb. modules now support
     OpenSSL 1.1.0.

   * The default settings and feature set of the *note ssl: bb. module
     have been improved.

   * The *note hashlib: 5e. module received support for the BLAKE2,
     SHA-3 and SHAKE hash algorithms and the *note scrypt(): be5. key
     derivation function.

Windows improvements:

   * *note PEP 528: be6. and *note PEP 529: be7, Windows filesystem and
     console encoding changed to UTF-8.

   * The ‘py.exe’ launcher, when used interactively, no longer prefers
     Python 2 over Python 3 when the user doesn't specify a version (via
     command line arguments or a config file).  Handling of shebang
     lines remains unchanged - "python" refers to Python 2 in that case.

   * ‘python.exe’ and ‘pythonw.exe’ have been marked as long-path aware,
     which means that the 260 character path limit may no longer apply.
     See *note removing the MAX_PATH limitation: be8. for details.

   * A ‘._pth’ file can be added to force isolated mode and fully
     specify all search paths to avoid registry and environment lookup.
     See *note the documentation: bc8. for more information.

   * A ‘python36.zip’ file now works as a landmark to infer *note
     PYTHONHOME: 387.  See *note the documentation: bc8. for more
     information.

   ---------- Footnotes ----------

   (1) 
https://mail.python.org/pipermail/python-dev/2012-December/123028.html

   (2) 
https://morepypy.blogspot.com/2015/01/faster-more-memory-efficient-and-more.html

   (3) https://peps.python.org/pep-0524/


File: python.info,  Node: New Features<7>,  Next: 其他語言更動<7>,  Prev: Summary -- Release highlights<3>,  Up: Python 3 6 有什麼新功能

1.8.2 New Features
------------------

* Menu:

* PEP 498; Formatted string literals: PEP 498 Formatted string literals.
* PEP 526; Syntax for variable annotations: PEP 526 Syntax for variable annotations.
* PEP 515; Underscores in Numeric Literals: PEP 515 Underscores in Numeric Literals.
* PEP 525; Asynchronous Generators: PEP 525 Asynchronous Generators.
* PEP 530; Asynchronous Comprehensions: PEP 530 Asynchronous Comprehensions.
* PEP 487; Simpler customization of class creation: PEP 487 Simpler customization of class creation.
* PEP 487; Descriptor Protocol Enhancements: PEP 487 Descriptor Protocol Enhancements.
* PEP 519; Adding a file system path protocol: PEP 519 Adding a file system path protocol.
* PEP 495; Local Time Disambiguation: PEP 495 Local Time Disambiguation.
* PEP 529; Change Windows filesystem encoding to UTF-8: PEP 529 Change Windows filesystem encoding to UTF-8.
* PEP 528; Change Windows console encoding to UTF-8: PEP 528 Change Windows console encoding to UTF-8.
* PEP 520; Preserving Class Attribute Definition Order: PEP 520 Preserving Class Attribute Definition Order.
* PEP 468; Preserving Keyword Argument Order: PEP 468 Preserving Keyword Argument Order.
* New dict implementation::
* PEP 523; Adding a frame evaluation API to CPython: PEP 523 Adding a frame evaluation API to CPython.
* PYTHONMALLOC environment variable::
* DTrace and SystemTap probing support::


File: python.info,  Node: PEP 498 Formatted string literals,  Next: PEP 526 Syntax for variable annotations,  Up: New Features<7>

1.8.2.1 PEP 498: Formatted string literals
..........................................

PEP 498(1) introduces a new kind of string literals: 'f-strings', or
*note formatted string literals: 94d.

Formatted string literals are prefixed with ‘'f'’ and are similar to the
format strings accepted by *note str.format(): 5c7.  They contain
replacement fields surrounded by curly braces.  The replacement fields
are expressions, which are evaluated at run time, and then formatted
using the *note format(): 5c3. protocol:

     >>> name = "Fred"
     >>> f"He said his name is {name}."
     'He said his name is Fred.'
     >>> width = 10
     >>> precision = 4
     >>> value = decimal.Decimal("12.34567")
     >>> f"result: {value:{width}.{precision}}"  # nested fields
     'result:      12.35'

也參考
......

PEP 498(2) - Literal String Interpolation.

     由 Eric V. Smith 撰寫 PEP 與實作。

*note Feature documentation: 94d.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0498/

   (2) https://peps.python.org/pep-0498/


File: python.info,  Node: PEP 526 Syntax for variable annotations,  Next: PEP 515 Underscores in Numeric Literals,  Prev: PEP 498 Formatted string literals,  Up: New Features<7>

1.8.2.2 PEP 526: Syntax for variable annotations
................................................

PEP 484(1) introduced the standard for type annotations of function
parameters, a.k.a.  type hints.  This PEP adds syntax to Python for
annotating the types of variables including class variables and instance
variables:

     primes: List[int] = []

     captain: str  # Note: no initial value!

     class Starship:
         stats: Dict[str, int] = {}

Just as for function annotations, the Python interpreter does not attach
any particular meaning to variable annotations and only stores them in
the ‘__annotations__’ attribute of a class or module.

In contrast to variable declarations in statically typed languages, the
goal of annotation syntax is to provide an easy way to specify
structured type metadata for third party tools and libraries via the
abstract syntax tree and the ‘__annotations__’ attribute.

也參考
......

PEP 526(2) - Syntax for variable annotations.

     PEP written by Ryan Gonzalez, Philip House, Ivan Levkivskyi, Lisa
     Roach, and Guido van Rossum.  Implemented by Ivan Levkivskyi.

Tools that use or will use the new syntax: mypy(3), pytype(4), PyCharm,
etc.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0484/

   (2) https://peps.python.org/pep-0526/

   (3) https://www.mypy-lang.org/

   (4) https://github.com/google/pytype


File: python.info,  Node: PEP 515 Underscores in Numeric Literals,  Next: PEP 525 Asynchronous Generators,  Prev: PEP 526 Syntax for variable annotations,  Up: New Features<7>

1.8.2.3 PEP 515: Underscores in Numeric Literals
................................................

PEP 515(1) adds the ability to use underscores in numeric literals for
improved readability.  For example:

     >>> 1_000_000_000_000_000
     1000000000000000
     >>> 0x_FF_FF_FF_FF
     4294967295

Single underscores are allowed between digits and after any base
specifier.  Leading, trailing, or multiple underscores in a row are not
allowed.

The *note string formatting: 1c8. language also now has support for the
‘'_'’ option to signal the use of an underscore for a thousands
separator for floating-point presentation types and for integer
presentation type ‘'d'’.  For integer presentation types ‘'b'’, ‘'o'’,
‘'x'’, and ‘'X'’, underscores will be inserted every 4 digits:

     >>> '{:_}'.format(1000000)
     '1_000_000'
     >>> '{:_x}'.format(0xFFFFFFFF)
     'ffff_ffff'

也參考
......

PEP 515(2) - Underscores in Numeric Literals

     由 Georg Brandl 與 Serhiy Storchaka 撰寫 PEP。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0515/

   (2) https://peps.python.org/pep-0515/


File: python.info,  Node: PEP 525 Asynchronous Generators,  Next: PEP 530 Asynchronous Comprehensions,  Prev: PEP 515 Underscores in Numeric Literals,  Up: New Features<7>

1.8.2.4 PEP 525: Asynchronous Generators
........................................

PEP 492(1) introduced support for native coroutines and ‘async’ /
‘await’ syntax to Python 3.5.  A notable limitation of the Python 3.5
implementation is that it was not possible to use ‘await’ and ‘yield’ in
the same function body.  In Python 3.6 this restriction has been lifted,
making it possible to define 'asynchronous generators':

     async def ticker(delay, to):
         """Yield numbers from 0 to *to* every *delay* seconds."""
         for i in range(to):
             yield i
             await asyncio.sleep(delay)

The new syntax allows for faster and more concise code.

也參考
......

PEP 525(2) - Asynchronous Generators

     由 Yury Selivanov 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0492/

   (2) https://peps.python.org/pep-0525/


File: python.info,  Node: PEP 530 Asynchronous Comprehensions,  Next: PEP 487 Simpler customization of class creation,  Prev: PEP 525 Asynchronous Generators,  Up: New Features<7>

1.8.2.5 PEP 530: Asynchronous Comprehensions
............................................

PEP 530(1) adds support for using ‘async for’ in list, set, dict
comprehensions and generator expressions:

     result = [i async for i in aiter() if i % 2]

Additionally, ‘await’ expressions are supported in all kinds of
comprehensions:

     result = [await fun() for fun in funcs if await condition()]

也參考
......

PEP 530(2) - Asynchronous Comprehensions

     由 Yury Selivanov 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0530/

   (2) https://peps.python.org/pep-0530/


File: python.info,  Node: PEP 487 Simpler customization of class creation,  Next: PEP 487 Descriptor Protocol Enhancements,  Prev: PEP 530 Asynchronous Comprehensions,  Up: New Features<7>

1.8.2.6 PEP 487: Simpler customization of class creation
........................................................

It is now possible to customize subclass creation without using a
metaclass.  The new ‘__init_subclass__’ classmethod will be called on
the base class whenever a new subclass is created:

     class PluginBase:
         subclasses = []

         def __init_subclass__(cls, **kwargs):
             super().__init_subclass__(**kwargs)
             cls.subclasses.append(cls)

     class Plugin1(PluginBase):
         pass

     class Plugin2(PluginBase):
         pass

In order to allow zero-argument *note super(): 483. calls to work
correctly from *note __init_subclass__(): 5d7. implementations, custom
metaclasses must ensure that the new ‘__classcell__’ namespace entry is
propagated to ‘type.__new__’ (as described in *note Creating the class
object: bf1.).

也參考
......

PEP 487(1) - Simpler customization of class creation

     由 Martin Teichmann 撰寫 PEP 與實作。

*note Feature documentation: bf2.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0487/


File: python.info,  Node: PEP 487 Descriptor Protocol Enhancements,  Next: PEP 519 Adding a file system path protocol,  Prev: PEP 487 Simpler customization of class creation,  Up: New Features<7>

1.8.2.7 PEP 487: Descriptor Protocol Enhancements
.................................................

PEP 487(1) extends the descriptor protocol to include the new optional
*note __set_name__(): bf5. method.  Whenever a new class is defined, the
new method will be called on all descriptors included in the definition,
providing them with a reference to the class being defined and the name
given to the descriptor within the class namespace.  In other words,
instances of descriptors can now know the attribute name of the
descriptor in the owner class:

     class IntField:
         def __get__(self, instance, owner):
             return instance.__dict__[self.name]

         def __set__(self, instance, value):
             if not isinstance(value, int):
                 raise ValueError(f'expecting integer in {self.name}')
             instance.__dict__[self.name] = value

         # this is the new initializer:
         def __set_name__(self, owner, name):
             self.name = name

     class Model:
         int_field = IntField()

也參考
......

PEP 487(2) - Simpler customization of class creation

     由 Martin Teichmann 撰寫 PEP 與實作。

*note Feature documentation: bf6.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0487/

   (2) https://peps.python.org/pep-0487/


File: python.info,  Node: PEP 519 Adding a file system path protocol,  Next: PEP 495 Local Time Disambiguation,  Prev: PEP 487 Descriptor Protocol Enhancements,  Up: New Features<7>

1.8.2.8 PEP 519: Adding a file system path protocol
...................................................

File system paths have historically been represented as *note str: 3f2.
or *note bytes: 1a5. objects.  This has led to people who write code
which operate on file system paths to assume that such objects are only
one of those two types (an *note int: 23c. representing a file
descriptor does not count as that is not a file path).  Unfortunately
that assumption prevents alternative object representations of file
system paths like *note pathlib: 93. from working with pre-existing
code, including Python's standard library.

To fix this situation, a new interface represented by *note os.PathLike:
bf8. has been defined.  By implementing the *note __fspath__(): bf9.
method, an object signals that it represents a path.  An object can then
provide a low-level representation of a file system path as a *note str:
3f2. or *note bytes: 1a5. object.  This means an object is considered
*note path-like: ac2. if it implements *note os.PathLike: bf8. or is a
*note str: 3f2. or *note bytes: 1a5. object which represents a file
system path.  Code can use *note os.fspath(): bfa, *note os.fsdecode():
bfb, or *note os.fsencode(): bfc. to explicitly get a *note str: 3f2.
and/or *note bytes: 1a5. representation of a path-like object.

The built-in *note open(): 4c0. function has been updated to accept
*note os.PathLike: bf8. objects, as have all relevant functions in the
*note os: 91. and *note os.path: 92. modules, and most other functions
and classes in the standard library.  The *note os.DirEntry: 443. class
and relevant classes in *note pathlib: 93. have also been updated to
implement *note os.PathLike: bf8.

The hope is that updating the fundamental functions for operating on
file system paths will lead to third-party code to implicitly support
all *note path-like objects: ac2. without any code changes, or at least
very minimal ones (e.g.  calling *note os.fspath(): bfa. at the
beginning of code before operating on a path-like object).

Here are some examples of how the new interface allows for *note
pathlib.Path: 20e. to be used more easily and transparently with
pre-existing code:

     >>> import pathlib
     >>> with open(pathlib.Path("README")) as f:
     ...     contents = f.read()
     ...
     >>> import os.path
     >>> os.path.splitext(pathlib.Path("some_file.txt"))
     ('some_file', '.txt')
     >>> os.path.join("/a/b", pathlib.Path("c"))
     '/a/b/c'
     >>> import os
     >>> os.fspath(pathlib.Path("some_file.txt"))
     'some_file.txt'

(Implemented by Brett Cannon, Ethan Furman, Dusty Phillips, and Jelle
Zijlstra.)

也參考
......

PEP 519(1) - Adding a file system path protocol

     由 Brett Cannon 與 Koos Zevenhoven 撰寫 PEP。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0519/


File: python.info,  Node: PEP 495 Local Time Disambiguation,  Next: PEP 529 Change Windows filesystem encoding to UTF-8,  Prev: PEP 519 Adding a file system path protocol,  Up: New Features<7>

1.8.2.9 PEP 495: Local Time Disambiguation
..........................................

In most world locations, there have been and will be times when local
clocks are moved back.  In those times, intervals are introduced in
which local clocks show the same time twice in the same day.  In these
situations, the information displayed on a local clock (or stored in a
Python datetime instance) is insufficient to identify a particular
moment in time.

PEP 495(1) adds the new 'fold' attribute to instances of *note
datetime.datetime: 1b0. and *note datetime.time: 1b2. classes to
differentiate between two moments in time for which local times are the
same:

     >>> u0 = datetime(2016, 11, 6, 4, tzinfo=timezone.utc)
     >>> for i in range(4):
     ...     u = u0 + i*HOUR
     ...     t = u.astimezone(Eastern)
     ...     print(u.time(), 'UTC =', t.time(), t.tzname(), t.fold)
     ...
     04:00:00 UTC = 00:00:00 EDT 0
     05:00:00 UTC = 01:00:00 EDT 0
     06:00:00 UTC = 01:00:00 EST 1
     07:00:00 UTC = 02:00:00 EST 0

The values of the *note fold: bfe. attribute have the value ‘0’ for all
instances except those that represent the second (chronologically)
moment in time in an ambiguous case.

也參考
......

PEP 495(2) - Local Time Disambiguation

     PEP written by Alexander Belopolsky and Tim Peters, implementation
     by Alexander Belopolsky.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0495/

   (2) https://peps.python.org/pep-0495/


File: python.info,  Node: PEP 529 Change Windows filesystem encoding to UTF-8,  Next: PEP 528 Change Windows console encoding to UTF-8,  Prev: PEP 495 Local Time Disambiguation,  Up: New Features<7>

1.8.2.10 PEP 529: Change Windows filesystem encoding to UTF-8
.............................................................

Representing filesystem paths is best performed with str (Unicode)
rather than bytes.  However, there are some situations where using bytes
is sufficient and correct.

Prior to Python 3.6, data loss could result when using bytes paths on
Windows.  With this change, using bytes to represent paths is now
supported on Windows, provided those bytes are encoded with the encoding
returned by *note sys.getfilesystemencoding(): c00, which now defaults
to ‘'utf-8'’.

Applications that do not use str to represent paths should use *note
os.fsencode(): bfc. and *note os.fsdecode(): bfb. to ensure their bytes
are correctly encoded.  To revert to the previous behaviour, set *note
PYTHONLEGACYWINDOWSFSENCODING: 28f. or call *note
sys._enablelegacywindowsfsencoding(): 28e.

See PEP 529(1) for more information and discussion of code modifications
that may be required.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0529/


File: python.info,  Node: PEP 528 Change Windows console encoding to UTF-8,  Next: PEP 520 Preserving Class Attribute Definition Order,  Prev: PEP 529 Change Windows filesystem encoding to UTF-8,  Up: New Features<7>

1.8.2.11 PEP 528: Change Windows console encoding to UTF-8
..........................................................

The default console on Windows will now accept all Unicode characters
and provide correctly read str objects to Python code.  ‘sys.stdin’,
‘sys.stdout’ and ‘sys.stderr’ now default to utf-8 encoding.

This change only applies when using an interactive console, and not when
redirecting files or pipes.  To revert to the previous behaviour for
interactive console use, set *note PYTHONLEGACYWINDOWSSTDIO: c02.

也參考
......

PEP 528(1) - Change Windows console encoding to UTF-8

     由 Steve Dower 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0528/


File: python.info,  Node: PEP 520 Preserving Class Attribute Definition Order,  Next: PEP 468 Preserving Keyword Argument Order,  Prev: PEP 528 Change Windows console encoding to UTF-8,  Up: New Features<7>

1.8.2.12 PEP 520: Preserving Class Attribute Definition Order
.............................................................

Attributes in a class definition body have a natural ordering: the same
order in which the names appear in the source.  This order is now
preserved in the new class's *note __dict__: c04. attribute.

Also, the effective default class 'execution' namespace (returned from
*note type.__prepare__(): c05.) is now an insertion-order-preserving
mapping.

也參考
......

PEP 520(1) - Preserving Class Attribute Definition Order

     由 Eric Snow 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0520/


File: python.info,  Node: PEP 468 Preserving Keyword Argument Order,  Next: New dict implementation,  Prev: PEP 520 Preserving Class Attribute Definition Order,  Up: New Features<7>

1.8.2.13 PEP 468: Preserving Keyword Argument Order
...................................................

‘**kwargs’ in a function signature is now guaranteed to be an
insertion-order-preserving mapping.

也參考
......

PEP 468(1) - Preserving Keyword Argument Order

     由 Eric Snow 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0468/


File: python.info,  Node: New dict implementation,  Next: PEP 523 Adding a frame evaluation API to CPython,  Prev: PEP 468 Preserving Keyword Argument Order,  Up: New Features<7>

1.8.2.14 New dict implementation
................................

The *note dict: a69. type now uses a "compact" representation based on a
proposal by Raymond Hettinger(1) which was first implemented by PyPy(2).
The memory usage of the new *note dict(): 23b. is between 20% and 25%
smaller compared to Python 3.5.

The order-preserving aspect of this new implementation is considered an
implementation detail and should not be relied upon (this may change in
the future, but it is desired to have this new dict implementation in
the language for a few releases before changing the language spec to
mandate order-preserving semantics for all current and future Python
implementations; this also helps preserve backwards-compatibility with
older versions of the language where random iteration order is still in
effect, e.g.  Python 3.5).

(Contributed by INADA Naoki in bpo-27350(3).  Idea originally suggested
by Raymond Hettinger(4).)

   ---------- Footnotes ----------

   (1) 
https://mail.python.org/pipermail/python-dev/2012-December/123028.html

   (2) 
https://morepypy.blogspot.com/2015/01/faster-more-memory-efficient-and-more.html

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27350

   (4) 
https://mail.python.org/pipermail/python-dev/2012-December/123028.html


File: python.info,  Node: PEP 523 Adding a frame evaluation API to CPython,  Next: PYTHONMALLOC environment variable,  Prev: New dict implementation,  Up: New Features<7>

1.8.2.15 PEP 523: Adding a frame evaluation API to CPython
..........................................................

While Python provides extensive support to customize how code executes,
one place it has not done so is in the evaluation of frame objects.  If
you wanted some way to intercept frame evaluation in Python there really
wasn't any way without directly manipulating function pointers for
defined functions.

PEP 523(1) changes this by providing an API to make frame evaluation
pluggable at the C level.  This will allow for tools such as debuggers
and JITs to intercept frame evaluation before the execution of Python
code begins.  This enables the use of alternative evaluation
implementations for Python code, tracking frame evaluation, etc.

This API is not part of the limited C API and is marked as private to
signal that usage of this API is expected to be limited and only
applicable to very select, low-level use-cases.  Semantics of the API
will change with Python as necessary.

也參考
......

PEP 523(2) - Adding a frame evaluation API to CPython

     由 Brett Cannon 與 Dino Viehland 撰寫 PEP。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0523/

   (2) https://peps.python.org/pep-0523/


File: python.info,  Node: PYTHONMALLOC environment variable,  Next: DTrace and SystemTap probing support,  Prev: PEP 523 Adding a frame evaluation API to CPython,  Up: New Features<7>

1.8.2.16 PYTHONMALLOC environment variable
..........................................

The new *note PYTHONMALLOC: c0b. environment variable allows setting the
Python memory allocators and installing debug hooks.

It is now possible to install debug hooks on Python memory allocators on
Python compiled in release mode using ‘PYTHONMALLOC=debug’.  Effects of
debug hooks:

   * Newly allocated memory is filled with the byte ‘0xCB’

   * Freed memory is filled with the byte ‘0xDB’

   * Detect violations of the Python memory allocator API. For example,
     *note PyObject_Free(): c0c. called on a memory block allocated by
     *note PyMem_Malloc(): c0d.

   * Detect writes before the start of a buffer (buffer underflows)

   * Detect writes after the end of a buffer (buffer overflows)

   * Check that the *note GIL: 12e. is held when allocator functions of
     *note PYMEM_DOMAIN_OBJ: c0e. (ex: *note PyObject_Malloc(): c0f.)
     and *note PYMEM_DOMAIN_MEM: c10. (ex: *note PyMem_Malloc(): c0d.)
     domains are called.

Checking if the GIL is held is also a new feature of Python 3.6.

See the *note PyMem_SetupDebugHooks(): c11. function for debug hooks on
Python memory allocators.

It is now also possible to force the usage of the ‘malloc()’ allocator
of the C library for all Python memory allocations using
‘PYTHONMALLOC=malloc’.  This is helpful when using external memory
debuggers like Valgrind on a Python compiled in release mode.

On error, the debug hooks on Python memory allocators now use the *note
tracemalloc: e8. module to get the traceback where a memory block was
allocated.

Example of fatal error on buffer overflow using ‘python3.6 -X
tracemalloc=5’ (store 5 frames in traces):

     Debug memory block at address p=0x7fbcd41666f8: API 'o'
         4 bytes originally requested
         The 7 pad bytes at p-7 are FORBIDDENBYTE, as expected.
         The 8 pad bytes at tail=0x7fbcd41666fc are not all FORBIDDENBYTE (0xfb):
             at tail+0: 0x02 *** OUCH
             at tail+1: 0xfb
             at tail+2: 0xfb
             at tail+3: 0xfb
             at tail+4: 0xfb
             at tail+5: 0xfb
             at tail+6: 0xfb
             at tail+7: 0xfb
         The block was made by call #1233329 to debug malloc/realloc.
         Data at p: 1a 2b 30 00

     Memory block allocated at (most recent call first):
       File "test/test_bytes.py", line 323
       File "unittest/case.py", line 600
       File "unittest/case.py", line 648
       File "unittest/suite.py", line 122
       File "unittest/suite.py", line 84

     Fatal Python error: bad trailing pad byte

     Current thread 0x00007fbcdbd32700 (most recent call first):
       File "test/test_bytes.py", line 323 in test_hex
       File "unittest/case.py", line 600 in run
       File "unittest/case.py", line 648 in __call__
       File "unittest/suite.py", line 122 in run
       File "unittest/suite.py", line 84 in __call__
       File "unittest/suite.py", line 122 in run
       File "unittest/suite.py", line 84 in __call__
       ...

（由 Victor Stinner 於 bpo-26516(1) 和 bpo-26564(2) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26516

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26564


File: python.info,  Node: DTrace and SystemTap probing support,  Prev: PYTHONMALLOC environment variable,  Up: New Features<7>

1.8.2.17 DTrace and SystemTap probing support
.............................................

Python can now be built ‘--with-dtrace’ which enables static markers for
the following events in the interpreter:

   * function call/return

   * garbage collection started/finished

   * line of code executed.

This can be used to instrument running interpreters in production,
without the need to recompile specific *note debug builds: 1de. or
providing application-specific profiling/debugging code.

More details in *note 使用 DTrace 和 SystemTap 檢測 CPython: c13.

The current implementation is tested on Linux and macOS. Additional
markers may be added in the future.

(Contributed by Łukasz Langa in bpo-21590(1), based on patches by Jesús
Cea Avión, David Malcolm, and Nikhil Benesch.)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21590


File: python.info,  Node: 其他語言更動<7>,  Next: 新模組<4>,  Prev: New Features<7>,  Up: Python 3 6 有什麼新功能

1.8.3 其他語言更動
------------------

Some smaller changes made to the core Python language are:

   * A ‘global’ or ‘nonlocal’ statement must now textually appear before
     the first use of the affected name in the same scope.  Previously
     this was a *note SyntaxWarning: 40c.

   * It is now possible to set a *note special method: c15. to ‘None’ to
     indicate that the corresponding operation is not available.  For
     example, if a class sets ‘__iter__()’ to ‘None’, the class is not
     iterable.  (Contributed by Andrew Barnert and Ivan Levkivskyi in
     bpo-25958(1).)

   * Long sequences of repeated traceback lines are now abbreviated as
     ‘"[Previous line repeated {count} more times]"’ (see *note
     traceback: c16. for an example).  (Contributed by Emanuel Barry in
     bpo-26823(2).)

   * Import now raises the new exception *note ModuleNotFoundError: aeb.
     (subclass of *note ImportError: 352.) when it cannot find a module.
     Code that currently checks for ImportError (in try-except) will
     still work.  (Contributed by Eric Snow in bpo-15767(3).)

   * Class methods relying on zero-argument ‘super()’ will now work
     correctly when called from metaclass methods during class creation.
     (Contributed by Martin Teichmann in bpo-23722(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25958

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26823

   (3) https://bugs.python.org/issue?@action=redirect&bpo=15767

   (4) https://bugs.python.org/issue?@action=redirect&bpo=23722


File: python.info,  Node: 新模組<4>,  Next: 改進的模組<7>,  Prev: 其他語言更動<7>,  Up: Python 3 6 有什麼新功能

1.8.4 新模組
------------

* Menu:

* secrets::


File: python.info,  Node: secrets,  Up: 新模組<4>

1.8.4.1 secrets
...............

The main purpose of the new *note secrets: ae. module is to provide an
obvious way to reliably generate cryptographically strong pseudo-random
values suitable for managing secrets, such as account authentication,
tokens, and similar.

     警告: Note that the pseudo-random generators in the *note random:
     a6. module should 'NOT' be used for security purposes.  Use *note
     secrets: ae. on Python 3.6+ and *note os.urandom(): 4c7. on Python
     3.5 and earlier.

也參考
......

PEP 506(1) - Adding A Secrets Module To The Standard Library

     由 Steven D'Aprano 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0506/


File: python.info,  Node: 改進的模組<7>,  Next: 最佳化<7>,  Prev: 新模組<4>,  Up: Python 3 6 有什麼新功能

1.8.5 改進的模組
----------------

* Menu:

* array: array<4>.
* ast: ast<4>.
* asyncio: asyncio<9>.
* binascii: binascii<2>.
* cmath::
* collections: collections<4>.
* concurrent.futures: concurrent futures<4>.
* contextlib: contextlib<4>.
* datetime: datetime<5>.
* decimal: decimal<2>.
* distutils: distutils<5>.
* email: email<2>.
* encodings: encodings<2>.
* enum: enum<6>.
* faulthandler: faulthandler<2>.
* fileinput: fileinput<2>.
* hashlib: hashlib<5>.
* http.client: http client<2>.
* idlelib and IDLE: idlelib and IDLE<2>.
* importlib: importlib<6>.
* inspect: inspect<6>.
* json::
* logging: logging<4>.
* math: math<7>.
* multiprocessing: multiprocessing<5>.
* os: os<8>.
* pathlib: pathlib<9>.
* pdb: pdb<5>.
* pickle: pickle<2>.
* pickletools::
* pydoc: pydoc<3>.
* random: random<4>.
* re: re<5>.
* readline::
* rlcompleter::
* shlex: shlex<2>.
* site: site<3>.
* sqlite3: sqlite3<7>.
* socket: socket<7>.
* socketserver: socketserver<2>.
* ssl: ssl<7>.
* statistics: statistics<5>.
* struct::
* subprocess: subprocess<3>.
* sys: sys<9>.
* telnetlib::
* time: time<6>.
* timeit::
* tkinter: tkinter<6>.
* traceback: traceback<4>.
* tracemalloc: tracemalloc<3>.
* typing: typing<9>.
* unicodedata: unicodedata<7>.
* unittest.mock: unittest mock<2>.
* urllib.request: urllib request.
* urllib.robotparser: urllib robotparser.
* venv: venv<5>.
* warnings: warnings<4>.
* winreg::
* winsound::
* xmlrpc.client: xmlrpc client.
* zipfile: zipfile<3>.
* zlib::


File: python.info,  Node: array<4>,  Next: ast<4>,  Up: 改進的模組<7>

1.8.5.1 array
.............

Exhausted iterators of *note array.array: 186. will now stay exhausted
even if the iterated array is extended.  This is consistent with the
behavior of other mutable sequences.

Contributed by Serhiy Storchaka in bpo-26492(1).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26492


File: python.info,  Node: ast<4>,  Next: asyncio<9>,  Prev: array<4>,  Up: 改進的模組<7>

1.8.5.2 ast
...........

The new *note ast.Constant: 29a. AST node has been added.  It can be
used by external AST optimizers for the purposes of constant folding.

Contributed by Victor Stinner in bpo-26146(1).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26146


File: python.info,  Node: asyncio<9>,  Next: binascii<2>,  Prev: ast<4>,  Up: 改進的模組<7>

1.8.5.3 asyncio
...............

Starting with Python 3.6 the ‘asyncio’ module is no longer provisional
and its API is considered stable.

Notable changes in the *note asyncio: 8. module since Python 3.5.0 (all
backported to 3.5.x due to the provisional status):

   * The *note get_event_loop(): 2a3. function has been changed to
     always return the currently running loop when called from
     coroutines and callbacks.  (Contributed by Yury Selivanov in
     bpo-28613(1).)

   * The *note ensure_future(): c1d. function and all functions that use
     it, such as *note loop.run_until_complete(): c1e, now accept all
     kinds of *note awaitable objects: 193.  (Contributed by Yury
     Selivanov.)

   * New *note run_coroutine_threadsafe(): 826. function to submit
     coroutines to event loops from other threads.  (Contributed by
     Vincent Michel.)

   * New *note Transport.is_closing(): c1f. method to check if the
     transport is closing or closed.  (Contributed by Yury Selivanov.)

   * The *note loop.create_server(): ab6. method can now accept a list
     of hosts.  (Contributed by Yann Sionneau.)

   * New *note loop.create_future(): c20. method to create Future
     objects.  This allows alternative event loop implementations, such
     as uvloop(2), to provide a faster *note asyncio.Future: b74.
     implementation.  (Contributed by Yury Selivanov in bpo-27041(3).)

   * New *note loop.get_exception_handler(): c21. method to get the
     current exception handler.  (Contributed by Yury Selivanov in
     bpo-27040(4).)

   * New *note StreamReader.readuntil(): 19a. method to read data from
     the stream until a separator bytes sequence appears.  (Contributed
     by Mark Korenberg.)

   * The performance of *note StreamReader.readexactly(): c22. has been
     improved.  (Contributed by Mark Korenberg in bpo-28370(5).)

   * The *note loop.getaddrinfo(): bbb. method is optimized to avoid
     calling the system ‘getaddrinfo’ function if the address is already
     resolved.  (Contributed by A. Jesse Jiryu Davis.)

   * The *note loop.stop(): c23. method has been changed to stop the
     loop immediately after the current iteration.  Any new callbacks
     scheduled as a result of the last iteration will be discarded.
     (Contributed by Guido van Rossum in bpo-25593(6).)

   * ‘Future.set_exception’ will now raise *note TypeError: 4dd. when
     passed an instance of the *note StopIteration: ba1. exception.
     (Contributed by Chris Angelico in bpo-26221(7).)

   * New *note loop.connect_accepted_socket(): abd. method to be used by
     servers that accept connections outside of asyncio, but that use
     asyncio to handle them.  (Contributed by Jim Fulton in
     bpo-27392(8).)

   * ‘TCP_NODELAY’ flag is now set for all TCP transports by default.
     (Contributed by Yury Selivanov in bpo-27456(9).)

   * New *note loop.shutdown_asyncgens(): c24. to properly close pending
     asynchronous generators before closing the loop.  (Contributed by
     Yury Selivanov in bpo-28003(10).)

   * *note Future: b74. and *note Task: 480. classes now have an
     optimized C implementation which makes asyncio code up to 30%
     faster.  (Contributed by Yury Selivanov and INADA Naoki in
     bpo-26081(11) and bpo-28544(12).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28613

   (2) https://github.com/MagicStack/uvloop

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27041

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27040

   (5) https://bugs.python.org/issue?@action=redirect&bpo=28370

   (6) https://bugs.python.org/issue?@action=redirect&bpo=25593

   (7) https://bugs.python.org/issue?@action=redirect&bpo=26221

   (8) https://bugs.python.org/issue?@action=redirect&bpo=27392

   (9) https://bugs.python.org/issue?@action=redirect&bpo=27456

   (10) https://bugs.python.org/issue?@action=redirect&bpo=28003

   (11) https://bugs.python.org/issue?@action=redirect&bpo=26081

   (12) https://bugs.python.org/issue?@action=redirect&bpo=28544


File: python.info,  Node: binascii<2>,  Next: cmath,  Prev: asyncio<9>,  Up: 改進的模組<7>

1.8.5.4 binascii
................

The *note b2a_base64(): c26. function now accepts an optional 'newline'
keyword argument to control whether the newline character is appended to
the return value.  (Contributed by Victor Stinner in bpo-25357(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25357


File: python.info,  Node: cmath,  Next: collections<4>,  Prev: binascii<2>,  Up: 改進的模組<7>

1.8.5.5 cmath
.............

The new *note cmath.tau: c28. ('τ') constant has been added.
(Contributed by Lisa Roach in bpo-12345(1), see PEP 628(2) for details.)

New constants: *note cmath.inf: c29. and *note cmath.nan: c2a. to match
*note math.inf: c2b. and *note math.nan: 609, and also *note cmath.infj:
c2c. and *note cmath.nanj: c2d. to match the format used by complex
repr.  (Contributed by Mark Dickinson in bpo-23229(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=12345

   (2) https://peps.python.org/pep-0628/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=23229


File: python.info,  Node: collections<4>,  Next: concurrent futures<4>,  Prev: cmath,  Up: 改進的模組<7>

1.8.5.6 collections
...................

The new *note Collection: c2f. abstract base class has been added to
represent sized iterable container classes.  (Contributed by Ivan
Levkivskyi, docs by Neil Girdhar in bpo-27598(1).)

The new *note Reversible: c30. abstract base class represents iterable
classes that also provide the ‘__reversed__()’ method.  (Contributed by
Ivan Levkivskyi in bpo-25987(2).)

The new *note AsyncGenerator: c31. abstract base class represents
asynchronous generators.  (Contributed by Yury Selivanov in
bpo-28720(3).)

The *note namedtuple(): 1ae. function now accepts an optional keyword
argument 'module', which, when specified, is used for the ‘__module__’
attribute of the returned named tuple class.  (Contributed by Raymond
Hettinger in bpo-17941(4).)

The 'verbose' and 'rename' arguments for *note namedtuple(): 1ae. are
now keyword-only.  (Contributed by Raymond Hettinger in bpo-25628(5).)

Recursive *note collections.deque: 580. instances can now be pickled.
(Contributed by Serhiy Storchaka in bpo-26482(6).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27598

   (2) https://bugs.python.org/issue?@action=redirect&bpo=25987

   (3) https://bugs.python.org/issue?@action=redirect&bpo=28720

   (4) https://bugs.python.org/issue?@action=redirect&bpo=17941

   (5) https://bugs.python.org/issue?@action=redirect&bpo=25628

   (6) https://bugs.python.org/issue?@action=redirect&bpo=26482


File: python.info,  Node: concurrent futures<4>,  Next: contextlib<4>,  Prev: collections<4>,  Up: 改進的模組<7>

1.8.5.7 concurrent.futures
..........................

The *note ThreadPoolExecutor: 6e6. class constructor now accepts an
optional 'thread_name_prefix' argument to make it possible to customize
the names of the threads created by the pool.  (Contributed by Gregory
P.  Smith in bpo-27664(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27664


File: python.info,  Node: contextlib<4>,  Next: datetime<5>,  Prev: concurrent futures<4>,  Up: 改進的模組<7>

1.8.5.8 contextlib
..................

The *note contextlib.AbstractContextManager: c34. class has been added
to provide an abstract base class for context managers.  It provides a
sensible default implementation for ‘__enter__()’ which returns ‘self’
and leaves ‘__exit__()’ an abstract method.  A matching class has been
added to the *note typing: ed. module as *note typing.ContextManager:
c35.  (Contributed by Brett Cannon in bpo-25609(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25609


File: python.info,  Node: datetime<5>,  Next: decimal<2>,  Prev: contextlib<4>,  Up: 改進的模組<7>

1.8.5.9 datetime
................

The *note datetime: 1b0. and *note time: 1b2. classes have the new
‘fold’ attribute used to disambiguate local time when necessary.  Many
functions in the *note datetime: 28. have been updated to support local
time disambiguation.  See *note Local Time Disambiguation: be3. section
for more information.  (Contributed by Alexander Belopolsky in
bpo-24773(1).)

The *note datetime.strftime(): c37. and *note date.strftime(): c38.
methods now support ISO 8601 date directives ‘%G’, ‘%u’ and ‘%V’.
(Contributed by Ashley Anderson in bpo-12006(2).)

The *note datetime.isoformat(): ad4. function now accepts an optional
'timespec' argument that specifies the number of additional components
of the time value to include.  (Contributed by Alessandro Cucci and
Alexander Belopolsky in bpo-19475(3).)

The *note datetime.combine(): c39. now accepts an optional 'tzinfo'
argument.  (Contributed by Alexander Belopolsky in bpo-27661(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24773

   (2) https://bugs.python.org/issue?@action=redirect&bpo=12006

   (3) https://bugs.python.org/issue?@action=redirect&bpo=19475

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27661


File: python.info,  Node: decimal<2>,  Next: distutils<5>,  Prev: datetime<5>,  Up: 改進的模組<7>

1.8.5.10 decimal
................

New *note Decimal.as_integer_ratio(): c3b. method that returns a pair
‘(n, d)’ of integers that represent the given *note Decimal: 27c.
instance as a fraction, in lowest terms and with a positive denominator:

     >>> Decimal('-3.14').as_integer_ratio()
     (-157, 50)

（由 Stefan Krah 和 Mark Dickinson 於 bpo-25928(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25928


File: python.info,  Node: distutils<5>,  Next: email<2>,  Prev: decimal<2>,  Up: 改進的模組<7>

1.8.5.11 distutils
..................

The ‘default_format’ attribute has been removed from
‘distutils.command.sdist.sdist’ and the ‘formats’ attribute defaults to
‘['gztar']’.  Although not anticipated, any code relying on the presence
of ‘default_format’ may need to be adapted.  See bpo-27819(1) for more
details.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27819


File: python.info,  Node: email<2>,  Next: encodings<2>,  Prev: distutils<5>,  Up: 改進的模組<7>

1.8.5.12 email
..............

The new email API, enabled via the 'policy' keyword to various
constructors, is no longer provisional.  The *note email: 32.
documentation has been reorganized and rewritten to focus on the new
API, while retaining the old documentation for the legacy API.
(Contributed by R. David Murray in bpo-24277(1).)

The *note email.mime: 3c. classes now all accept an optional 'policy'
keyword.  (Contributed by Berker Peksag in bpo-27331(2).)

The *note DecodedGenerator: c3e. now supports the 'policy' keyword.

There is a new *note policy: 46. attribute, *note message_factory: c3f,
that controls what class is used by default when the parser creates new
message objects.  For the *note email.policy.compat32: c40. policy this
is *note Message: 261, for the new policies it is *note EmailMessage:
260.  (Contributed by R. David Murray in bpo-20476(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24277

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27331

   (3) https://bugs.python.org/issue?@action=redirect&bpo=20476


File: python.info,  Node: encodings<2>,  Next: enum<6>,  Prev: email<2>,  Up: 改進的模組<7>

1.8.5.13 encodings
..................

On Windows, added the ‘'oem'’ encoding to use ‘CP_OEMCP’, and the
‘'ansi'’ alias for the existing ‘'mbcs'’ encoding, which uses the
‘CP_ACP’ code page.  (Contributed by Steve Dower in bpo-27959(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27959


File: python.info,  Node: enum<6>,  Next: faulthandler<2>,  Prev: encodings<2>,  Up: 改進的模組<7>

1.8.5.14 enum
.............

Two new enumeration base classes have been added to the *note enum: 4c.
module: *note Flag: 5c9. and ‘IntFlags’.  Both are used to define
constants that can be combined using the bitwise operators.
(Contributed by Ethan Furman in bpo-23591(1).)

Many standard library modules have been updated to use the ‘IntFlags’
class for their constants.

The new *note enum.auto: c43. value can be used to assign values to enum
members automatically:

     >>> from enum import Enum, auto
     >>> class Color(Enum):
     ...     red = auto()
     ...     blue = auto()
     ...     green = auto()
     ...
     >>> list(Color)
     [<Color.red: 1>, <Color.blue: 2>, <Color.green: 3>]

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23591


File: python.info,  Node: faulthandler<2>,  Next: fileinput<2>,  Prev: enum<6>,  Up: 改進的模組<7>

1.8.5.15 faulthandler
.....................

On Windows, the *note faulthandler: 4e. module now installs a handler
for Windows exceptions: see *note faulthandler.enable(): c45.
(Contributed by Victor Stinner in bpo-23848(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23848


File: python.info,  Node: fileinput<2>,  Next: hashlib<5>,  Prev: faulthandler<2>,  Up: 改進的模組<7>

1.8.5.16 fileinput
..................

*note hook_encoded(): c47. now supports the 'errors' argument.
(Contributed by Joseph Hackman in bpo-25788(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25788


File: python.info,  Node: hashlib<5>,  Next: http client<2>,  Prev: fileinput<2>,  Up: 改進的模組<7>

1.8.5.17 hashlib
................

*note hashlib: 5e. supports OpenSSL 1.1.0.  The minimum recommend
version is 1.0.2.  (Contributed by Christian Heimes in bpo-26470(1).)

BLAKE2 hash functions were added to the module.  *note blake2b(): 5e8.
and *note blake2s(): 5e9. are always available and support the full
feature set of BLAKE2.  (Contributed by Christian Heimes in bpo-26798(2)
based on code by Dmitry Chestnykh and Samuel Neves.  Documentation
written by Dmitry Chestnykh.)

The SHA-3 hash functions *note sha3_224(): c49, *note sha3_256(): c4a,
*note sha3_384(): c4b, *note sha3_512(): c4c, and SHAKE hash functions
*note shake_128(): c4d. and *note shake_256(): c4e. were added.
(Contributed by Christian Heimes in bpo-16113(3).  Keccak Code Package
by Guido Bertoni, Joan Daemen, Michaël Peeters, Gilles Van Assche, and
Ronny Van Keer.)

The password-based key derivation function *note scrypt(): be5. is now
available with OpenSSL 1.1.0 and newer.  (Contributed by Christian
Heimes in bpo-27928(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26470

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26798

   (3) https://bugs.python.org/issue?@action=redirect&bpo=16113

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27928


File: python.info,  Node: http client<2>,  Next: idlelib and IDLE<2>,  Prev: hashlib<5>,  Up: 改進的模組<7>

1.8.5.18 http.client
....................

*note HTTPConnection.request(): c50. and *note endheaders(): c51. both
now support chunked encoding request bodies.  (Contributed by Demian
Brecht and Rolf Krahl in bpo-12319(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=12319


File: python.info,  Node: idlelib and IDLE<2>,  Next: importlib<6>,  Prev: http client<2>,  Up: 改進的模組<7>

1.8.5.19 idlelib and IDLE
.........................

The idlelib package is being modernized and refactored to make IDLE look
and work better and to make the code easier to understand, test, and
improve.  Part of making IDLE look better, especially on Linux and Mac,
is using ttk widgets, mostly in the dialogs.  As a result, IDLE no
longer runs with tcl/tk 8.4.  It now requires tcl/tk 8.5 or 8.6.  We
recommend running the latest release of either.

'Modernizing' includes renaming and consolidation of idlelib modules.
The renaming of files with partial uppercase names is similar to the
renaming of, for instance, Tkinter and TkFont to tkinter and
tkinter.font in 3.0.  As a result, imports of idlelib files that worked
in 3.5 will usually not work in 3.6.  At least a module name change will
be needed (see idlelib/README.txt), sometimes more.  (Name changes
contributed by Al Swiegart and Terry Reedy in bpo-24225(1).  Most
idlelib patches since have been and will be part of the process.)

In compensation, the eventual result with be that some idlelib classes
will be easier to use, with better APIs and docstrings explaining them.
Additional useful information will be added to idlelib when available.

New in 3.6.2:

Multiple fixes for autocompletion.  (Contributed by Louie Lu in
bpo-15786(2).)

New in 3.6.3:

Module Browser (on the File menu, formerly called Class Browser), now
displays nested functions and classes in addition to top-level functions
and classes.  (Contributed by Guilherme Polo, Cheryl Sabella, and Terry
Jan Reedy in bpo-1612262(3).)

The IDLE features formerly implemented as extensions have been
reimplemented as normal features.  Their settings have been moved from
the Extensions tab to other dialog tabs.  (Contributed by Charles
Wohlganger and Terry Jan Reedy in bpo-27099(4).)

The Settings dialog (Options, Configure IDLE) has been partly rewritten
to improve both appearance and function.  (Contributed by Cheryl Sabella
and Terry Jan Reedy in multiple issues.)

New in 3.6.4:

The font sample now includes a selection of non-Latin characters so that
users can better see the effect of selecting a particular font.
(Contributed by Terry Jan Reedy in bpo-13802(5).)  The sample can be
edited to include other characters.  (Contributed by Serhiy Storchaka in
bpo-31860(6).)

New in 3.6.6:

Editor code context option revised.  Box displays all context lines up
to maxlines.  Clicking on a context line jumps the editor to that line.
Context colors for custom themes is added to Highlights tab of Settings
dialog.  (Contributed by Cheryl Sabella and Terry Jan Reedy in
bpo-33642(7), bpo-33768(8), and bpo-33679(9).)

On Windows, a new API call tells Windows that tk scales for DPI. On
Windows 8.1+ or 10, with DPI compatibility properties of the Python
binary unchanged, and a monitor resolution greater than 96 DPI, this
should make text and lines sharper.  It should otherwise have no effect.
(Contributed by Terry Jan Reedy in bpo-33656(10).)

New in 3.6.7:

Output over N lines (50 by default) is squeezed down to a button.  N can
be changed in the PyShell section of the General page of the Settings
dialog.  Fewer, but possibly extra long, lines can be squeezed by right
clicking on the output.  Squeezed output can be expanded in place by
double-clicking the button or into the clipboard or a separate window by
right-clicking the button.  (Contributed by Tal Einat in
bpo-1529353(11).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24225

   (2) https://bugs.python.org/issue?@action=redirect&bpo=15786

   (3) https://bugs.python.org/issue?@action=redirect&bpo=1612262

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27099

   (5) https://bugs.python.org/issue?@action=redirect&bpo=13802

   (6) https://bugs.python.org/issue?@action=redirect&bpo=31860

   (7) https://bugs.python.org/issue?@action=redirect&bpo=33642

   (8) https://bugs.python.org/issue?@action=redirect&bpo=33768

   (9) https://bugs.python.org/issue?@action=redirect&bpo=33679

   (10) https://bugs.python.org/issue?@action=redirect&bpo=33656

   (11) https://bugs.python.org/issue?@action=redirect&bpo=1529353


File: python.info,  Node: importlib<6>,  Next: inspect<6>,  Prev: idlelib and IDLE<2>,  Up: 改進的模組<7>

1.8.5.20 importlib
..................

Import now raises the new exception *note ModuleNotFoundError: aeb.
(subclass of *note ImportError: 352.) when it cannot find a module.
Code that current checks for ‘ImportError’ (in try-except) will still
work.  (Contributed by Eric Snow in bpo-15767(1).)

*note importlib.util.LazyLoader: c54. now calls *note create_module():
c55. on the wrapped loader, removing the restriction that *note
importlib.machinery.BuiltinImporter: c56. and *note
importlib.machinery.ExtensionFileLoader: c57. couldn't be used with
*note importlib.util.LazyLoader: c54.

*note importlib.util.cache_from_source(): 2cf, *note
importlib.util.source_from_cache(): 4be, and *note
importlib.util.spec_from_file_location(): c58. now accept a *note
path-like object: ac2.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=15767


File: python.info,  Node: inspect<6>,  Next: json,  Prev: importlib<6>,  Up: 改進的模組<7>

1.8.5.21 inspect
................

The *note inspect.signature(): 6dc. function now reports the implicit
‘.0’ parameters generated by the compiler for comprehension and
generator expression scopes as if they were positional-only parameters
called ‘implicit0’.  (Contributed by Jelle Zijlstra in bpo-19611(1).)

To reduce code churn when upgrading from Python 2.7 and the legacy
‘inspect.getargspec()’ API, the previously documented deprecation of
*note inspect.getfullargspec(): 6dd. has been reversed.  While this
function is convenient for single/source Python 2/3 code bases, the
richer *note inspect.signature(): 6dc. interface remains the recommended
approach for new code.  (Contributed by Nick Coghlan in bpo-27172(2))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=19611

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27172


File: python.info,  Node: json,  Next: logging<4>,  Prev: inspect<6>,  Up: 改進的模組<7>

1.8.5.22 json
.............

*note json.load(): c5b. and *note json.loads(): 8f9. now support binary
input.  Encoded JSON should be represented using either UTF-8, UTF-16,
or UTF-32.  (Contributed by Serhiy Storchaka in bpo-17909(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=17909


File: python.info,  Node: logging<4>,  Next: math<7>,  Prev: json,  Up: 改進的模組<7>

1.8.5.23 logging
................

The new *note WatchedFileHandler.reopenIfNeeded(): c5d. method has been
added to add the ability to check if the log file needs to be reopened.
(Contributed by Marian Horban in bpo-24884(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24884


File: python.info,  Node: math<7>,  Next: multiprocessing<5>,  Prev: logging<4>,  Up: 改進的模組<7>

1.8.5.24 math
.............

The tau ('τ') constant has been added to the *note math: 81. and *note
cmath: 11. modules.  (Contributed by Lisa Roach in bpo-12345(1), see PEP
628(2) for details.)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=12345

   (2) https://peps.python.org/pep-0628/


File: python.info,  Node: multiprocessing<5>,  Next: os<8>,  Prev: math<7>,  Up: 改進的模組<7>

1.8.5.25 multiprocessing
........................

*note Proxy Objects: c60. returned by *note multiprocessing.Manager():
c61. can now be nested.  (Contributed by Davin Potts in bpo-6766(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=6766


File: python.info,  Node: os<8>,  Next: pathlib<9>,  Prev: multiprocessing<5>,  Up: 改進的模組<7>

1.8.5.26 os
...........

See the summary of *note PEP 519: be2. for details on how the *note os:
91. and *note os.path: 92. modules now support *note path-like objects:
ac2.

*note scandir(): a02. now supports *note bytes: 1a5. paths on Windows.

A new *note close(): c63. method allows explicitly closing a *note
scandir(): a02. iterator.  The *note scandir(): a02. iterator now
supports the *note context manager: 576. protocol.  If a ‘scandir()’
iterator is neither exhausted nor explicitly closed a *note
ResourceWarning: 229. will be emitted in its destructor.  (Contributed
by Serhiy Storchaka in bpo-25994(1).)

On Linux, *note os.urandom(): 4c7. now blocks until the system urandom
entropy pool is initialized to increase the security.  See the PEP
524(2) for the rationale.

The Linux ‘getrandom()’ syscall (get random bytes) is now exposed as the
new *note os.getrandom(): c64. function.  (Contributed by Victor
Stinner, part of the PEP 524(3))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25994

   (2) https://peps.python.org/pep-0524/

   (3) https://peps.python.org/pep-0524/


File: python.info,  Node: pathlib<9>,  Next: pdb<5>,  Prev: os<8>,  Up: 改進的模組<7>

1.8.5.27 pathlib
................

*note pathlib: 93. now supports *note path-like objects: ac2.
(Contributed by Brett Cannon in bpo-27186(1).)

細節請見 *note PEP 519: be2. 中的摘要。

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27186


File: python.info,  Node: pdb<5>,  Next: pickle<2>,  Prev: pathlib<9>,  Up: 改進的模組<7>

1.8.5.28 pdb
............

The *note Pdb: 8c7. class constructor has a new optional 'readrc'
argument to control whether ‘.pdbrc’ files should be read.


File: python.info,  Node: pickle<2>,  Next: pickletools,  Prev: pdb<5>,  Up: 改進的模組<7>

1.8.5.29 pickle
...............

Objects that need ‘__new__’ called with keyword arguments can now be
pickled using *note pickle protocols: c68. older than protocol version
4.  Protocol version 4 already supports this case.  (Contributed by
Serhiy Storchaka in bpo-24164(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24164


File: python.info,  Node: pickletools,  Next: pydoc<3>,  Prev: pickle<2>,  Up: 改進的模組<7>

1.8.5.30 pickletools
....................

*note pickletools.dis(): c6a. now outputs the implicit memo index for
the ‘MEMOIZE’ opcode.  (Contributed by Serhiy Storchaka in
bpo-25382(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25382


File: python.info,  Node: pydoc<3>,  Next: random<4>,  Prev: pickletools,  Up: 改進的模組<7>

1.8.5.31 pydoc
..............

The *note pydoc: a3. module has learned to respect the ‘MANPAGER’
environment variable.  (Contributed by Matthias Klose in bpo-8637(1).)

*note help(): 87c. and *note pydoc: a3. can now list named tuple fields
in the order they were defined rather than alphabetically.  (Contributed
by Raymond Hettinger in bpo-24879(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=8637

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24879


File: python.info,  Node: random<4>,  Next: re<5>,  Prev: pydoc<3>,  Up: 改進的模組<7>

1.8.5.32 random
...............

The new *note choices(): c6d. function returns a list of elements of
specified size from the given population with optional weights.
(Contributed by Raymond Hettinger in bpo-18844(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=18844


File: python.info,  Node: re<5>,  Next: readline,  Prev: random<4>,  Up: 改進的模組<7>

1.8.5.33 re
...........

Added support of modifier spans in regular expressions.  Examples:
‘'(?i:p)ython'’ matches ‘'python'’ and ‘'Python'’, but not ‘'PYTHON'’;
‘'(?i)g(?-i:v)r'’ matches ‘'GvR'’ and ‘'gvr'’, but not ‘'GVR'’.
(Contributed by Serhiy Storchaka in bpo-433028(1).)

Match object groups can be accessed by ‘__getitem__’, which is
equivalent to ‘group()’.  So ‘mo['name']’ is now equivalent to
‘mo.group('name')’.  (Contributed by Eric Smith in bpo-24454(2).)

*note Match: c6f. objects now support *note index-like objects: 6c1. as
group indices.  (Contributed by Jeroen Demeyer and Xiang Zhang in
bpo-27177(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=433028

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24454

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27177


File: python.info,  Node: readline,  Next: rlcompleter,  Prev: re<5>,  Up: 改進的模組<7>

1.8.5.34 readline
.................

Added *note set_auto_history(): c71. to enable or disable automatic
addition of input to the history list.  (Contributed by Tyler Crompton
in bpo-26870(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26870


File: python.info,  Node: rlcompleter,  Next: shlex<2>,  Prev: readline,  Up: 改進的模組<7>

1.8.5.35 rlcompleter
....................

Private and special attribute names now are omitted unless the prefix
starts with underscores.  A space or a colon is added after some
completed keywords.  (Contributed by Serhiy Storchaka in bpo-25011(1)
and bpo-25209(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25011

   (2) https://bugs.python.org/issue?@action=redirect&bpo=25209


File: python.info,  Node: shlex<2>,  Next: site<3>,  Prev: rlcompleter,  Up: 改進的模組<7>

1.8.5.36 shlex
..............

The *note shlex: c74. has much *note improved shell compatibility: c75.
through the new 'punctuation_chars' argument to control which characters
are treated as punctuation.  (Contributed by Vinay Sajip in
bpo-1521950(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1521950


File: python.info,  Node: site<3>,  Next: sqlite3<7>,  Prev: shlex<2>,  Up: 改進的模組<7>

1.8.5.37 site
.............

When specifying paths to add to *note sys.path: 37f. in a ‘.pth’ file,
you may now specify file paths on top of directories (e.g.  zip files).
(Contributed by Wolfgang Langner in bpo-26587(1)).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26587


File: python.info,  Node: sqlite3<7>,  Next: socket<7>,  Prev: site<3>,  Up: 改進的模組<7>

1.8.5.38 sqlite3
................

*note sqlite3.Cursor.lastrowid: c78. now supports the ‘REPLACE’
statement.  (Contributed by Alex LordThorsen in bpo-16864(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16864


File: python.info,  Node: socket<7>,  Next: socketserver<2>,  Prev: sqlite3<7>,  Up: 改進的模組<7>

1.8.5.39 socket
...............

The *note ioctl(): c7a. function now supports the *note
SIO_LOOPBACK_FAST_PATH: c7b. control code.  (Contributed by Daniel
Stokes in bpo-26536(1).)

The *note getsockopt(): c7c. constants ‘SO_DOMAIN’, ‘SO_PROTOCOL’,
‘SO_PEERSEC’, and ‘SO_PASSSEC’ are now supported.  (Contributed by
Christian Heimes in bpo-26907(2).)

The *note setsockopt(): c7d. now supports the ‘setsockopt(level,
optname, None, optlen: int)’ form.  (Contributed by Christian Heimes in
bpo-27744(3).)

The socket module now supports the address family *note AF_ALG: c7e. to
interface with Linux Kernel crypto API. ‘ALG_*’, ‘SOL_ALG’ and *note
sendmsg_afalg(): c7f. were added.  (Contributed by Christian Heimes in
bpo-27744(4) with support from Victor Stinner.)

New Linux constants ‘TCP_USER_TIMEOUT’ and ‘TCP_CONGESTION’ were added.
(Contributed by Omar Sandoval, bpo-26273(5)).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26536

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26907

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27744

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27744

   (5) https://bugs.python.org/issue?@action=redirect&bpo=26273


File: python.info,  Node: socketserver<2>,  Next: ssl<7>,  Prev: socket<7>,  Up: 改進的模組<7>

1.8.5.40 socketserver
.....................

Servers based on the *note socketserver: b9. module, including those
defined in *note http.server: 68, *note xmlrpc.server: 115. and *note
wsgiref.simple_server: 103, now support the *note context manager: 576.
protocol.  (Contributed by Aviv Palivoda in bpo-26404(1).)

The ‘wfile’ attribute of *note StreamRequestHandler: c81. classes now
implements the *note io.BufferedIOBase: 63a. writable interface.  In
particular, calling *note write(): c82. is now guaranteed to send the
data in full.  (Contributed by Martin Panter in bpo-26721(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26404

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26721


File: python.info,  Node: ssl<7>,  Next: statistics<5>,  Prev: socketserver<2>,  Up: 改進的模組<7>

1.8.5.41 ssl
............

*note ssl: bb. supports OpenSSL 1.1.0.  The minimum recommend version is
1.0.2.  (Contributed by Christian Heimes in bpo-26470(1).)

3DES has been removed from the default cipher suites and ChaCha20
Poly1305 cipher suites have been added.  (Contributed by Christian
Heimes in bpo-27850(2) and bpo-27766(3).)

*note SSLContext: 276. has better default configuration for options and
ciphers.  (Contributed by Christian Heimes in bpo-28043(4).)

SSL session can be copied from one client-side connection to another
with the new *note SSLSession: c84. class.  TLS session resumption can
speed up the initial handshake, reduce latency and improve performance
(Contributed by Christian Heimes in bpo-19500(5) based on a draft by
Alex Warhawk.)

The new *note get_ciphers(): c85. method can be used to get a list of
enabled ciphers in order of cipher priority.

All constants and flags have been converted to *note IntEnum: c86. and
‘IntFlags’.  (Contributed by Christian Heimes in bpo-28025(6).)

Server and client-side specific TLS protocols for *note SSLContext: 276.
were added.  (Contributed by Christian Heimes in bpo-28085(7).)

Added *note ssl.SSLContext.post_handshake_auth: 9d5. to enable and *note
ssl.SSLSocket.verify_client_post_handshake(): 9d6. to initiate TLS 1.3
post-handshake authentication.  (Contributed by Christian Heimes in
gh-78851(8).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26470

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27850

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27766

   (4) https://bugs.python.org/issue?@action=redirect&bpo=28043

   (5) https://bugs.python.org/issue?@action=redirect&bpo=19500

   (6) https://bugs.python.org/issue?@action=redirect&bpo=28025

   (7) https://bugs.python.org/issue?@action=redirect&bpo=28085

   (8) https://github.com/python/cpython/issues/78851


File: python.info,  Node: statistics<5>,  Next: struct,  Prev: ssl<7>,  Up: 改進的模組<7>

1.8.5.42 statistics
...................

A new *note harmonic_mean(): c88. function has been added.  (Contributed
by Steven D'Aprano in bpo-27181(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27181


File: python.info,  Node: struct,  Next: subprocess<3>,  Prev: statistics<5>,  Up: 改進的模組<7>

1.8.5.43 struct
...............

*note struct: c0. now supports IEEE 754 half-precision floats via the
‘'e'’ format specifier.  (Contributed by Eli Stevens, Mark Dickinson in
bpo-11734(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=11734


File: python.info,  Node: subprocess<3>,  Next: sys<9>,  Prev: struct,  Up: 改進的模組<7>

1.8.5.44 subprocess
...................

*note subprocess.Popen: 17d. destructor now emits a *note
ResourceWarning: 229. warning if the child process is still running.
Use the context manager protocol (‘with proc: ...’) or explicitly call
the *note wait(): c8b. method to read the exit status of the child
process.  (Contributed by Victor Stinner in bpo-26741(1).)

The *note subprocess.Popen: 17d. constructor and all functions that pass
arguments through to it now accept 'encoding' and 'errors' arguments.
Specifying either of these will enable text mode for the 'stdin',
'stdout' and 'stderr' streams.  (Contributed by Steve Dower in
bpo-6135(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26741

   (2) https://bugs.python.org/issue?@action=redirect&bpo=6135


File: python.info,  Node: sys<9>,  Next: telnetlib,  Prev: subprocess<3>,  Up: 改進的模組<7>

1.8.5.45 sys
............

The new *note getfilesystemencodeerrors(): c8d. function returns the
name of the error mode used to convert between Unicode filenames and
bytes filenames.  (Contributed by Steve Dower in bpo-27781(1).)

On Windows the return value of the *note getwindowsversion(): c8e.
function now includes the 'platform_version' field which contains the
accurate major version, minor version and build number of the current
operating system, rather than the version that is being emulated for the
process (Contributed by Steve Dower in bpo-27932(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27781

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27932


File: python.info,  Node: telnetlib,  Next: time<6>,  Prev: sys<9>,  Up: 改進的模組<7>

1.8.5.46 telnetlib
..................

‘telnetlib.Telnet’ is now a context manager (contributed by Stéphane
Wirtel in bpo-25485(1)).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25485


File: python.info,  Node: time<6>,  Next: timeit,  Prev: telnetlib,  Up: 改進的模組<7>

1.8.5.47 time
.............

The *note struct_time: c91. attributes ‘tm_gmtoff’ and ‘tm_zone’ are now
available on all platforms.


File: python.info,  Node: timeit,  Next: tkinter<6>,  Prev: time<6>,  Up: 改進的模組<7>

1.8.5.48 timeit
...............

The new *note Timer.autorange(): c93. convenience method has been added
to call *note Timer.timeit(): c94. repeatedly so that the total run time
is greater or equal to 200 milliseconds.  (Contributed by Steven
D'Aprano in bpo-6422(1).)

*note timeit: d8. now warns when there is substantial (4x) variance
between best and worst times.  (Contributed by Serhiy Storchaka in
bpo-23552(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=6422

   (2) https://bugs.python.org/issue?@action=redirect&bpo=23552


File: python.info,  Node: tkinter<6>,  Next: traceback<4>,  Prev: timeit,  Up: 改進的模組<7>

1.8.5.49 tkinter
................

Added methods ‘trace_add()’, ‘trace_remove()’ and ‘trace_info()’ in the
‘tkinter.Variable’ class.  They replace old methods ‘trace_variable()’,
‘trace()’, ‘trace_vdelete()’ and ‘trace_vinfo()’ that use obsolete Tcl
commands and might not work in future versions of Tcl.  (Contributed by
Serhiy Storchaka in bpo-22115(1)).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22115


File: python.info,  Node: traceback<4>,  Next: tracemalloc<3>,  Prev: tkinter<6>,  Up: 改進的模組<7>

1.8.5.50 traceback
..................

Both the traceback module and the interpreter's builtin exception
display now abbreviate long sequences of repeated lines in tracebacks as
shown in the following example:

     >>> def f(): f()
     ...
     >>> f()
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
       File "<stdin>", line 1, in f
       File "<stdin>", line 1, in f
       File "<stdin>", line 1, in f
       [Previous line repeated 995 more times]
     RecursionError: maximum recursion depth exceeded

（由 Emanuel Barry 於 bpo-26823(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26823


File: python.info,  Node: tracemalloc<3>,  Next: typing<9>,  Prev: traceback<4>,  Up: 改進的模組<7>

1.8.5.51 tracemalloc
....................

The *note tracemalloc: e8. module now supports tracing memory
allocations in multiple different address spaces.

The new *note DomainFilter: c98. filter class has been added to filter
block traces by their address space (domain).

（由 Victor Stinner 於 bpo-26588(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26588


File: python.info,  Node: typing<9>,  Next: unicodedata<7>,  Prev: tracemalloc<3>,  Up: 改進的模組<7>

1.8.5.52 typing
...............

Since the *note typing: ed. module is *note provisional: aa6, all
changes introduced in Python 3.6 have also been backported to Python
3.5.x.

The *note typing: ed. module has a much improved support for generic
type aliases.  For example ‘Dict[str, Tuple[S, T]]’ is now a valid type
annotation.  (Contributed by Guido van Rossum in Github #195(1).)

The *note typing.ContextManager: c35. class has been added for
representing *note contextlib.AbstractContextManager: c34.  (Contributed
by Brett Cannon in bpo-25609(2).)

The *note typing.Collection: c9a. class has been added for representing
*note collections.abc.Collection: c2f.  (Contributed by Ivan Levkivskyi
in bpo-27598(3).)

The *note typing.ClassVar: 24b. type construct has been added to mark
class variables.  As introduced in PEP 526(4), a variable annotation
wrapped in ClassVar indicates that a given attribute is intended to be
used as a class variable and should not be set on instances of that
class.  (Contributed by Ivan Levkivskyi in Github #280(5).)

A new *note TYPE_CHECKING: c9b. constant that is assumed to be ‘True’ by
the static type checkers, but is ‘False’ at runtime.  (Contributed by
Guido van Rossum in Github #230(6).)

A new *note NewType(): c9c. helper function has been added to create
lightweight distinct types for annotations:

     from typing import NewType

     UserId = NewType('UserId', int)
     some_id = UserId(524313)

The static type checker will treat the new type as if it were a subclass
of the original type.  (Contributed by Ivan Levkivskyi in Github
#189(7).)

   ---------- Footnotes ----------

   (1) https://github.com/python/typing/pull/195

   (2) https://bugs.python.org/issue?@action=redirect&bpo=25609

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27598

   (4) https://peps.python.org/pep-0526/

   (5) https://github.com/python/typing/pull/280

   (6) https://github.com/python/typing/issues/230

   (7) https://github.com/python/typing/issues/189


File: python.info,  Node: unicodedata<7>,  Next: unittest mock<2>,  Prev: typing<9>,  Up: 改進的模組<7>

1.8.5.53 unicodedata
....................

The *note unicodedata: ee. module now uses data from Unicode 9.0.0(1).
(Contributed by Benjamin Peterson.)

   ---------- Footnotes ----------

   (1) https://unicode.org/versions/Unicode9.0.0/


File: python.info,  Node: unittest mock<2>,  Next: urllib request,  Prev: unicodedata<7>,  Up: 改進的模組<7>

1.8.5.54 unittest.mock
......................

The *note Mock: 9ef. class has the following improvements:

   * Two new methods, *note Mock.assert_called(): c9f. and *note
     Mock.assert_called_once(): ca0. to check if the mock object was
     called.  (Contributed by Amit Saha in bpo-26323(1).)

   * The *note Mock.reset_mock(): ca1. method now has two optional
     keyword only arguments: 'return_value' and 'side_effect'.
     (Contributed by Kushal Das in bpo-21271(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26323

   (2) https://bugs.python.org/issue?@action=redirect&bpo=21271


File: python.info,  Node: urllib request,  Next: urllib robotparser,  Prev: unittest mock<2>,  Up: 改進的模組<7>

1.8.5.55 urllib.request
.......................

If a HTTP request has a file or iterable body (other than a bytes
object) but no ‘Content-Length’ header, rather than throwing an error,
‘AbstractHTTPHandler’ now falls back to use chunked transfer encoding.
(Contributed by Demian Brecht and Rolf Krahl in bpo-12319(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=12319


File: python.info,  Node: urllib robotparser,  Next: venv<5>,  Prev: urllib request,  Up: 改進的模組<7>

1.8.5.56 urllib.robotparser
...........................

*note RobotFileParser: ca4. now supports the ‘Crawl-delay’ and
‘Request-rate’ extensions.  (Contributed by Nikolay Bogoychev in
bpo-16099(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16099


File: python.info,  Node: venv<5>,  Next: warnings<4>,  Prev: urllib robotparser,  Up: 改進的模組<7>

1.8.5.57 venv
.............

*note venv: f9. accepts a new parameter ‘--prompt’.  This parameter
provides an alternative prefix for the virtual environment.  (Proposed
by Łukasz Balcerzak and ported to 3.6 by Stéphane Wirtel in
bpo-22829(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22829


File: python.info,  Node: warnings<4>,  Next: winreg,  Prev: venv<5>,  Up: 改進的模組<7>

1.8.5.58 warnings
.................

A new optional 'source' parameter has been added to the *note
warnings.warn_explicit(): ca7. function: the destroyed object which
emitted a *note ResourceWarning: 229.  A 'source' attribute has also
been added to ‘warnings.WarningMessage’ (contributed by Victor Stinner
in bpo-26568(1) and bpo-26567(2)).

When a *note ResourceWarning: 229. warning is logged, the *note
tracemalloc: e8. module is now used to try to retrieve the traceback
where the destroyed object was allocated.

Example with the script ‘example.py’:

     import warnings

     def func():
         return open(__file__)

     f = func()
     f = None

Output of the command ‘python3.6 -Wd -X tracemalloc=5 example.py’:

     example.py:7: ResourceWarning: unclosed file <_io.TextIOWrapper name='example.py' mode='r' encoding='UTF-8'>
       f = None
     Object allocated at (most recent call first):
       File "example.py", lineno 4
         return open(__file__)
       File "example.py", lineno 6
         f = func()

The "Object allocated at" traceback is new and is only displayed if
*note tracemalloc: e8. is tracing Python memory allocations and if the
*note warnings: fa. module was already imported.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26568

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26567


File: python.info,  Node: winreg,  Next: winsound,  Prev: warnings<4>,  Up: 改進的模組<7>

1.8.5.59 winreg
...............

Added the 64-bit integer type *note REG_QWORD: ca9.  (Contributed by
Clement Rouault in bpo-23026(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23026


File: python.info,  Node: winsound,  Next: xmlrpc client,  Prev: winreg,  Up: 改進的模組<7>

1.8.5.60 winsound
.................

Allowed keyword arguments to be passed to *note Beep: cab, *note
MessageBeep: cac, and *note PlaySound: cad. (bpo-27982(1)).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27982


File: python.info,  Node: xmlrpc client,  Next: zipfile<3>,  Prev: winsound,  Up: 改進的模組<7>

1.8.5.61 xmlrpc.client
......................

The *note xmlrpc.client: 114. module now supports unmarshalling
additional data types used by the Apache XML-RPC implementation for
numerics and ‘None’.  (Contributed by Serhiy Storchaka in bpo-26885(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26885


File: python.info,  Node: zipfile<3>,  Next: zlib,  Prev: xmlrpc client,  Up: 改進的模組<7>

1.8.5.62 zipfile
................

A new *note ZipInfo.from_file(): cb0. class method allows making a *note
ZipInfo: cb1. instance from a filesystem file.  A new *note
ZipInfo.is_dir(): cb2. method can be used to check if the *note ZipInfo:
cb1. instance represents a directory.  (Contributed by Thomas Kluyver in
bpo-26039(1).)

The *note ZipFile.open(): 355. method can now be used to write data into
a ZIP file, as well as for extracting data.  (Contributed by Thomas
Kluyver in bpo-26039(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26039

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26039


File: python.info,  Node: zlib,  Prev: zipfile<3>,  Up: 改進的模組<7>

1.8.5.63 zlib
.............

The *note compress(): 5e5. and *note decompress(): cb4. functions now
accept keyword arguments.  (Contributed by Aviv Palivoda in bpo-26243(1)
and Xiang Zhang in bpo-16764(2) respectively.)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26243

   (2) https://bugs.python.org/issue?@action=redirect&bpo=16764


File: python.info,  Node: 最佳化<7>,  Next: Build and C API Changes<2>,  Prev: 改進的模組<7>,  Up: Python 3 6 有什麼新功能

1.8.6 最佳化
------------

   * The Python interpreter now uses a 16-bit wordcode instead of
     bytecode which made a number of opcode optimizations possible.
     (Contributed by Demur Rumed with input and reviews from Serhiy
     Storchaka and Victor Stinner in bpo-26647(1) and bpo-28050(2).)

   * The *note asyncio.Future: b74. class now has an optimized C
     implementation.  (Contributed by Yury Selivanov and INADA Naoki in
     bpo-26081(3).)

   * The *note asyncio.Task: 480. class now has an optimized C
     implementation.  (Contributed by Yury Selivanov in bpo-28544(4).)

   * Various implementation improvements in the *note typing: ed. module
     (such as caching of generic types) allow up to 30 times performance
     improvements and reduced memory footprint.

   * The ASCII decoder is now up to 60 times as fast for error handlers
     ‘surrogateescape’, ‘ignore’ and ‘replace’ (Contributed by Victor
     Stinner in bpo-24870(5)).

   * The ASCII and the Latin1 encoders are now up to 3 times as fast for
     the error handler ‘surrogateescape’ (Contributed by Victor Stinner
     in bpo-25227(6)).

   * The UTF-8 encoder is now up to 75 times as fast for error handlers
     ‘ignore’, ‘replace’, ‘surrogateescape’, ‘surrogatepass’
     (Contributed by Victor Stinner in bpo-25267(7)).

   * The UTF-8 decoder is now up to 15 times as fast for error handlers
     ‘ignore’, ‘replace’ and ‘surrogateescape’ (Contributed by Victor
     Stinner in bpo-25301(8)).

   * ‘bytes % args’ is now up to 2 times faster.  (Contributed by Victor
     Stinner in bpo-25349(9)).

   * ‘bytearray % args’ is now between 2.5 and 5 times faster.
     (Contributed by Victor Stinner in bpo-25399(10)).

   * Optimize *note bytes.fromhex(): a92. and *note bytearray.fromhex():
     a93.: they are now between 2x and 3.5x faster.  (Contributed by
     Victor Stinner in bpo-25401(11)).

   * Optimize ‘bytes.replace(b'', b'.')’ and ‘bytearray.replace(b'',
     b'.')’: up to 80% faster.  (Contributed by Josh Snider in
     bpo-26574(12)).

   * Allocator functions of the *note PyMem_Malloc(): c0d. domain (*note
     PYMEM_DOMAIN_MEM: c10.) now use the *note pymalloc memory
     allocator: cb6. instead of ‘malloc()’ function of the C library.
     The pymalloc allocator is optimized for objects smaller or equal to
     512 bytes with a short lifetime, and use ‘malloc()’ for larger
     memory blocks.  (Contributed by Victor Stinner in bpo-26249(13)).

   * *note pickle.load(): cb7. and *note pickle.loads(): cb8. are now up
     to 10% faster when deserializing many small objects (Contributed by
     Victor Stinner in bpo-27056(14)).

   * Passing *note keyword arguments: cb9. to a function has an overhead
     in comparison with passing *note positional arguments: cba.  Now in
     extension functions implemented with using Argument Clinic this
     overhead is significantly decreased.  (Contributed by Serhiy
     Storchaka in bpo-27574(15)).

   * Optimized *note glob(): 280. and *note iglob(): 7ab. functions in
     the *note glob: 5a. module; they are now about 3-6 times faster.
     (Contributed by Serhiy Storchaka in bpo-25596(16)).

   * Optimized globbing in *note pathlib: 93. by using *note
     os.scandir(): a02.; it is now about 1.5-4 times faster.
     (Contributed by Serhiy Storchaka in bpo-26032(17)).

   * *note xml.etree.ElementTree: 10c. parsing, iteration and deepcopy
     performance has been significantly improved.  (Contributed by
     Serhiy Storchaka in bpo-25638(18), bpo-25873(19), and
     bpo-25869(20).)

   * Creation of *note fractions.Fraction: 1c7. instances from floats
     and decimals is now 2 to 3 times faster.  (Contributed by Serhiy
     Storchaka in bpo-25971(21).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26647

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28050

   (3) https://bugs.python.org/issue?@action=redirect&bpo=26081

   (4) https://bugs.python.org/issue?@action=redirect&bpo=28544

   (5) https://bugs.python.org/issue?@action=redirect&bpo=24870

   (6) https://bugs.python.org/issue?@action=redirect&bpo=25227

   (7) https://bugs.python.org/issue?@action=redirect&bpo=25267

   (8) https://bugs.python.org/issue?@action=redirect&bpo=25301

   (9) https://bugs.python.org/issue?@action=redirect&bpo=25349

   (10) https://bugs.python.org/issue?@action=redirect&bpo=25399

   (11) https://bugs.python.org/issue?@action=redirect&bpo=25401

   (12) https://bugs.python.org/issue?@action=redirect&bpo=26574

   (13) https://bugs.python.org/issue?@action=redirect&bpo=26249

   (14) https://bugs.python.org/issue?@action=redirect&bpo=27056

   (15) https://bugs.python.org/issue?@action=redirect&bpo=27574

   (16) https://bugs.python.org/issue?@action=redirect&bpo=25596

   (17) https://bugs.python.org/issue?@action=redirect&bpo=26032

   (18) https://bugs.python.org/issue?@action=redirect&bpo=25638

   (19) https://bugs.python.org/issue?@action=redirect&bpo=25873

   (20) https://bugs.python.org/issue?@action=redirect&bpo=25869

   (21) https://bugs.python.org/issue?@action=redirect&bpo=25971


File: python.info,  Node: Build and C API Changes<2>,  Next: Other Improvements,  Prev: 最佳化<7>,  Up: Python 3 6 有什麼新功能

1.8.7 Build and C API Changes
-----------------------------

   * Python now requires some C99 support in the toolchain to build.
     Most notably, Python now uses standard integer types and macros in
     place of custom macros like ‘PY_LONG_LONG’.  For more information,
     see PEP 7(1) and bpo-17884(2).

   * Cross-compiling CPython with the Android NDK and the Android API
     level set to 21 (Android 5.0 Lollipop) or greater runs
     successfully.  While Android is not yet a supported platform, the
     Python test suite runs on the Android emulator with only about 16
     tests failures.  See the Android meta-issue bpo-26865(3).

   * The ‘--enable-optimizations’ configure flag has been added.
     Turning it on will activate expensive optimizations like PGO.
     (Original patch by Alecsandru Patrascu of Intel in bpo-26359(4).)

   * The *note GIL: 12e. must now be held when allocator functions of
     *note PYMEM_DOMAIN_OBJ: c0e. (ex: *note PyObject_Malloc(): c0f.)
     and *note PYMEM_DOMAIN_MEM: c10. (ex: *note PyMem_Malloc(): c0d.)
     domains are called.

   * New *note Py_FinalizeEx(): cbc. API which indicates if flushing
     buffered data failed.  (Contributed by Martin Panter in
     bpo-5319(5).)

   * *note PyArg_ParseTupleAndKeywords(): 2e9. now supports *note
     positional-only parameters: a28.  Positional-only parameters are
     defined by empty names.  (Contributed by Serhiy Storchaka in
     bpo-26282(6)).

   * ‘PyTraceback_Print’ method now abbreviates long sequences of
     repeated lines as ‘"[Previous line repeated {count} more times]"’.
     (Contributed by Emanuel Barry in bpo-26823(7).)

   * The new *note PyErr_SetImportErrorSubclass(): cbd. function allows
     for specifying a subclass of *note ImportError: 352. to raise.
     (Contributed by Eric Snow in bpo-15767(8).)

   * The new *note PyErr_ResourceWarning(): cbe. function can be used to
     generate a *note ResourceWarning: 229. providing the source of the
     resource allocation.  (Contributed by Victor Stinner in
     bpo-26567(9).)

   * The new *note PyOS_FSPath(): cbf. function returns the file system
     representation of a *note path-like object: ac2.  (Contributed by
     Brett Cannon in bpo-27186(10).)

   * The *note PyUnicode_FSConverter(): cc0. and *note
     PyUnicode_FSDecoder(): 51d. functions will now accept *note
     path-like objects: ac2.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0007/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=17884

   (3) https://bugs.python.org/issue?@action=redirect&bpo=26865

   (4) https://bugs.python.org/issue?@action=redirect&bpo=26359

   (5) https://bugs.python.org/issue?@action=redirect&bpo=5319

   (6) https://bugs.python.org/issue?@action=redirect&bpo=26282

   (7) https://bugs.python.org/issue?@action=redirect&bpo=26823

   (8) https://bugs.python.org/issue?@action=redirect&bpo=15767

   (9) https://bugs.python.org/issue?@action=redirect&bpo=26567

   (10) https://bugs.python.org/issue?@action=redirect&bpo=27186


File: python.info,  Node: Other Improvements,  Next: 已棄用<9>,  Prev: Build and C API Changes<2>,  Up: Python 3 6 有什麼新功能

1.8.8 Other Improvements
------------------------

   * When *note -version: cc2. (short form: *note -V: 15b.) is supplied
     twice, Python prints *note sys.version: 15c. for detailed
     information.

          $ ./python -VV
          Python 3.6.0b4+ (3.6:223967b49e49+, Nov 21 2016, 20:55:04)
          [GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.42.1)]


File: python.info,  Node: 已棄用<9>,  Next: 已移除<7>,  Prev: Other Improvements,  Up: Python 3 6 有什麼新功能

1.8.9 已棄用
------------

* Menu:

* 新關鍵字::
* Deprecated Python behavior::
* Deprecated Python modules, functions and methods: Deprecated Python modules functions and methods<2>.
* xml: xml<6>.
* Deprecated functions and types of the C API: Deprecated functions and types of the C API<2>.
* Deprecated Build Options::


File: python.info,  Node: 新關鍵字,  Next: Deprecated Python behavior,  Up: 已棄用<9>

1.8.9.1 新關鍵字
................

‘async’ and ‘await’ are not recommended to be used as variable, class,
function or module names.  Introduced by PEP 492(1) in Python 3.5, they
will become proper keywords in Python 3.7.  Starting in Python 3.6, the
use of ‘async’ or ‘await’ as names will generate a *note
DeprecationWarning: 18b.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0492/


File: python.info,  Node: Deprecated Python behavior,  Next: Deprecated Python modules functions and methods<2>,  Prev: 新關鍵字,  Up: 已棄用<9>

1.8.9.2 Deprecated Python behavior
..................................

Raising the *note StopIteration: ba1. exception inside a generator will
now generate a *note DeprecationWarning: 18b, and will trigger a *note
RuntimeError: 179. in Python 3.7.  See *note PEP 479; Change
StopIteration handling inside generators: cc6. for details.

The ‘__aiter__()’ method is now expected to return an asynchronous
iterator directly instead of returning an awaitable as previously.
Doing the former will trigger a *note DeprecationWarning: 18b.  Backward
compatibility will be removed in Python 3.7.  (Contributed by Yury
Selivanov in bpo-27243(1).)

A backslash-character pair that is not a valid escape sequence now
generates a *note DeprecationWarning: 18b.  Although this will
eventually become a *note SyntaxError: 173, that will not be for several
Python releases.  (Contributed by Emanuel Barry in bpo-27364(2).)

When performing a relative import, falling back on ‘__name__’ and
‘__path__’ from the calling module when ‘__spec__’ or ‘__package__’ are
not defined now raises an *note ImportWarning: 4a2.  (Contributed by
Rose Ames in bpo-25791(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27243

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27364

   (3) https://bugs.python.org/issue?@action=redirect&bpo=25791


File: python.info,  Node: Deprecated Python modules functions and methods<2>,  Next: xml<6>,  Prev: Deprecated Python behavior,  Up: 已棄用<9>

1.8.9.3 Deprecated Python modules, functions and methods
........................................................

* Menu:

* asynchat::
* asyncore::
* dbm: dbm<4>.
* distutils: distutils<6>.
* grp::
* importlib: importlib<7>.
* os: os<9>.
* re: re<6>.
* ssl: ssl<8>.
* tkinter: tkinter<7>.
* venv: venv<6>.


File: python.info,  Node: asynchat,  Next: asyncore,  Up: Deprecated Python modules functions and methods<2>

1.8.9.4 asynchat
................

The ‘asynchat’ has been deprecated in favor of *note asyncio: 8.
(Contributed by Mariatta in bpo-25002(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25002


File: python.info,  Node: asyncore,  Next: dbm<4>,  Prev: asynchat,  Up: Deprecated Python modules functions and methods<2>

1.8.9.5 asyncore
................

The ‘asyncore’ has been deprecated in favor of *note asyncio: 8.
(Contributed by Mariatta in bpo-25002(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25002


File: python.info,  Node: dbm<4>,  Next: distutils<6>,  Prev: asyncore,  Up: Deprecated Python modules functions and methods<2>

1.8.9.6 dbm
...........

Unlike other *note dbm: 29. implementations, the *note dbm.dumb: 2a.
module creates databases with the ‘'rw'’ mode and allows modifying the
database opened with the ‘'r'’ mode.  This behavior is now deprecated
and will be removed in 3.8.  (Contributed by Serhiy Storchaka in
bpo-21708(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21708


File: python.info,  Node: distutils<6>,  Next: grp,  Prev: dbm<4>,  Up: Deprecated Python modules functions and methods<2>

1.8.9.7 distutils
.................

The undocumented ‘extra_path’ argument to the ‘distutils.Distribution’
constructor is now considered deprecated and will raise a warning if
set.  Support for this parameter will be removed in a future Python
release.  See bpo-27919(1) for details.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27919


File: python.info,  Node: grp,  Next: importlib<7>,  Prev: distutils<6>,  Up: Deprecated Python modules functions and methods<2>

1.8.9.8 grp
...........

The support of non-integer arguments in *note getgrgid(): ccd. has been
deprecated.  (Contributed by Serhiy Storchaka in bpo-26129(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26129


File: python.info,  Node: importlib<7>,  Next: os<9>,  Prev: grp,  Up: Deprecated Python modules functions and methods<2>

1.8.9.9 importlib
.................

The *note importlib.machinery.SourceFileLoader.load_module(): ccf. and
*note importlib.machinery.SourcelessFileLoader.load_module(): cd0.
methods are now deprecated.  They were the only remaining
implementations of *note importlib.abc.Loader.load_module(): 80e. in
*note importlib: 6b. that had not been deprecated in previous versions
of Python in favour of *note importlib.abc.Loader.exec_module(): 80f.

The *note importlib.machinery.WindowsRegistryFinder: cd1. class is now
deprecated.  As of 3.6.0, it is still added to *note sys.meta_path: cd2.
by default (on Windows), but this may change in future releases.


File: python.info,  Node: os<9>,  Next: re<6>,  Prev: importlib<7>,  Up: Deprecated Python modules functions and methods<2>

1.8.9.10 os
...........

Undocumented support of general *note bytes-like objects: cd4. as paths
in *note os: 91. functions, *note compile(): 178. and similar functions
is now deprecated.  (Contributed by Serhiy Storchaka in bpo-25791(1) and
bpo-26754(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25791

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26754


File: python.info,  Node: re<6>,  Next: ssl<8>,  Prev: os<9>,  Up: Deprecated Python modules functions and methods<2>

1.8.9.11 re
...........

Support for inline flags ‘(?letters)’ in the middle of the regular
expression has been deprecated and will be removed in a future Python
version.  Flags at the start of a regular expression are still allowed.
(Contributed by Serhiy Storchaka in bpo-22493(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22493


File: python.info,  Node: ssl<8>,  Next: tkinter<7>,  Prev: re<6>,  Up: Deprecated Python modules functions and methods<2>

1.8.9.12 ssl
............

OpenSSL 0.9.8, 1.0.0 and 1.0.1 are deprecated and no longer supported.
In the future the *note ssl: bb. module will require at least OpenSSL
1.0.2 or 1.1.0.

SSL-related arguments like ‘certfile’, ‘keyfile’ and ‘check_hostname’ in
*note ftplib: 54, *note http.client: 65, *note imaplib: 6a, *note
poplib: 9a, and *note smtplib: b7. have been deprecated in favor of
‘context’.  (Contributed by Christian Heimes in bpo-28022(1).)

A couple of protocols and functions of the *note ssl: bb. module are now
deprecated.  Some features will no longer be available in future
versions of OpenSSL. Other features are deprecated in favor of a
different API. (Contributed by Christian Heimes in bpo-28022(2) and
bpo-26470(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28022

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28022

   (3) https://bugs.python.org/issue?@action=redirect&bpo=26470


File: python.info,  Node: tkinter<7>,  Next: venv<6>,  Prev: ssl<8>,  Up: Deprecated Python modules functions and methods<2>

1.8.9.13 tkinter
................

The ‘tkinter.tix’ module is now deprecated.  *note tkinter: d9. users
should use *note tkinter.ttk: e2. instead.


File: python.info,  Node: venv<6>,  Prev: tkinter<7>,  Up: Deprecated Python modules functions and methods<2>

1.8.9.14 venv
.............

The ‘pyvenv’ script has been deprecated in favour of ‘python3 -m venv’.
This prevents confusion as to what Python interpreter ‘pyvenv’ is
connected to and thus what Python interpreter will be used by the
virtual environment.  (Contributed by Brett Cannon in bpo-25154(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25154


File: python.info,  Node: xml<6>,  Next: Deprecated functions and types of the C API<2>,  Prev: Deprecated Python modules functions and methods<2>,  Up: 已棄用<9>

1.8.9.15 xml
............

   * As mitigation against DTD and external entity retrieval, the *note
     xml.dom.minidom: 109. and *note xml.sax: 110. modules no longer
     process external entities by default.  (Contributed by Christian
     Heimes in gh-61441(1).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/61441


File: python.info,  Node: Deprecated functions and types of the C API<2>,  Next: Deprecated Build Options,  Prev: xml<6>,  Up: 已棄用<9>

1.8.9.16 Deprecated functions and types of the C API
....................................................

Undocumented functions ‘PyUnicode_AsEncodedObject()’,
‘PyUnicode_AsDecodedObject()’, ‘PyUnicode_AsEncodedUnicode()’ and
‘PyUnicode_AsDecodedUnicode()’ are deprecated now.  Use the *note
generic codec based API: cdc. instead.


File: python.info,  Node: Deprecated Build Options,  Prev: Deprecated functions and types of the C API<2>,  Up: 已棄用<9>

1.8.9.17 Deprecated Build Options
.................................

The ‘--with-system-ffi’ configure flag is now on by default on non-macOS
UNIX platforms.  It may be disabled by using ‘--without-system-ffi’, but
using the flag is deprecated and will not be accepted in Python 3.7.
macOS is unaffected by this change.  Note that many OS distributors
already use the ‘--with-system-ffi’ flag when building their system
Python.


File: python.info,  Node: 已移除<7>,  Next: Porting to Python 3 6,  Prev: 已棄用<9>,  Up: Python 3 6 有什麼新功能

1.8.10 已移除
-------------

* Menu:

* API and Feature Removals: API and Feature Removals<3>.


File: python.info,  Node: API and Feature Removals<3>,  Up: 已移除<7>

1.8.10.1 API and Feature Removals
.................................

   * Unknown escapes consisting of ‘'\'’ and an ASCII letter in regular
     expressions will now cause an error.  In replacement templates for
     *note re.sub(): 283. they are still allowed, but deprecated.  The
     *note re.LOCALE: b10. flag can now only be used with binary
     patterns.

   * ‘inspect.getmoduleinfo()’ was removed (was deprecated since CPython
     3.3).  *note inspect.getmodulename(): ce0. should be used for
     obtaining the module name for a given path.  (Contributed by Yury
     Selivanov in bpo-13248(1).)

   * ‘traceback.Ignore’ class and ‘traceback.usage’,
     ‘traceback.modname’, ‘traceback.fullmodname’,
     ‘traceback.find_lines_from_code’, ‘traceback.find_lines’,
     ‘traceback.find_strings’, ‘traceback.find_executable_lines’ methods
     were removed from the *note traceback: e7. module.  They were
     undocumented methods deprecated since Python 3.2 and equivalent
     functionality is available from private methods.

   * The ‘tk_menuBar()’ and ‘tk_bindForTraversal()’ dummy methods in
     *note tkinter: d9. widget classes were removed (corresponding Tk
     commands were obsolete since Tk 4.0).

   * The *note open(): 355. method of the *note zipfile.ZipFile: 669.
     class no longer supports the ‘'U'’ mode (was deprecated since
     Python 3.4).  Use *note io.TextIOWrapper: 75f. for reading
     compressed text files in *note universal newlines: ce1. mode.

   * The undocumented ‘IN’, ‘CDROM’, ‘DLFCN’, ‘TYPES’, ‘CDIO’, and
     ‘STROPTS’ modules have been removed.  They had been available in
     the platform specific ‘Lib/plat-*/’ directories, but were
     chronically out of date, inconsistently available across platforms,
     and unmaintained.  The script that created these modules is still
     available in the source distribution at Tools/scripts/h2py.py(2).

   * The deprecated ‘asynchat.fifo’ class has been removed.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=13248

   (2) 
https://github.com/python/cpython/blob/v3.6.15/Tools/scripts/h2py.py


File: python.info,  Node: Porting to Python 3 6,  Next: Python 3 6 2 中顯著的變更,  Prev: 已移除<7>,  Up: Python 3 6 有什麼新功能

1.8.11 Porting to Python 3.6
----------------------------

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

* Menu:

* Changes in 'python' Command Behavior::
* Changes in the Python API: Changes in the Python API<6>.
* C API 中的改動: C API 中的改動<5>.
* CPython 位元組碼變更: CPython 位元組碼變更<7>.


File: python.info,  Node: Changes in 'python' Command Behavior,  Next: Changes in the Python API<6>,  Up: Porting to Python 3 6

1.8.11.1 Changes in 'python' Command Behavior
.............................................

   * The output of a special Python build with defined ‘COUNT_ALLOCS’,
     ‘SHOW_ALLOC_COUNT’ or ‘SHOW_TRACK_COUNT’ macros is now off by
     default.  It can be re-enabled using the ‘-X showalloccount’
     option.  It now outputs to ‘stderr’ instead of ‘stdout’.
     (Contributed by Serhiy Storchaka in bpo-23034(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23034


File: python.info,  Node: Changes in the Python API<6>,  Next: C API 中的改動<5>,  Prev: Changes in 'python' Command Behavior,  Up: Porting to Python 3 6

1.8.11.2 Changes in the Python API
..................................

   * *note open(): 4c0. will no longer allow combining the ‘'U'’ mode
     flag with ‘'+'’.  (Contributed by Jeff Balogh and John O'Connor in
     bpo-2091(1).)

   * *note sqlite3: ba. no longer implicitly commits an open transaction
     before DDL statements.

   * On Linux, *note os.urandom(): 4c7. now blocks until the system
     urandom entropy pool is initialized to increase the security.

   * When *note importlib.abc.Loader.exec_module(): 80f. is defined,
     *note importlib.abc.Loader.create_module(): c55. must also be
     defined.

   * *note PyErr_SetImportError(): ce5. now sets *note TypeError: 4dd.
     when its 'msg' argument is not set.  Previously only ‘NULL’ was
     returned.

   * The format of the *note co_lnotab: 2b7. attribute of code objects
     changed to support a negative line number delta.  By default,
     Python does not emit bytecode with a negative line number delta.
     Functions using *note frame.f_lineno: 750,
     ‘PyFrame_GetLineNumber()’ or ‘PyCode_Addr2Line()’ are not affected.
     Functions directly decoding ‘co_lnotab’ should be updated to use a
     signed 8-bit integer type for the line number delta, but this is
     only required to support applications using a negative line number
     delta.  See ‘Objects/lnotab_notes.txt’ for the ‘co_lnotab’ format
     and how to decode it, and see the PEP 511(2) for the rationale.

   * The functions in the *note compileall: 19. module now return
     booleans instead of ‘1’ or ‘0’ to represent success or failure,
     respectively.  Thanks to booleans being a subclass of integers,
     this should only be an issue if you were doing identity checks for
     ‘1’ or ‘0’.  See bpo-25768(3).

   * Reading the ‘port’ attribute of *note urllib.parse.urlsplit(): ce6.
     and *note urlparse(): 2df. results now raises *note ValueError:
     1e7. for out-of-range values, rather than returning *note None:
     61b.  See bpo-20059(4).

   * The ‘imp’ module now raises a *note DeprecationWarning: 18b.
     instead of *note PendingDeprecationWarning: 86d.

   * The following modules have had missing APIs added to their
     ‘__all__’ attributes to match the documented APIs: *note calendar:
     10, ‘cgi’, *note csv: 21, *note ElementTree: 10c, *note enum: 4c,
     *note fileinput: 51, *note ftplib: 54, *note logging: 7b, *note
     mailbox: 7f, *note mimetypes: 82, *note optparse: 90, *note
     plistlib: 99, ‘smtpd’, *note subprocess: c1, *note tarfile: c8,
     *note threading: d6. and *note wave: fb.  This means they will
     export new symbols when ‘import *’ is used.  (Contributed by Joel
     Taddei and Jacek Kołodziej in bpo-23883(5).)

   * When performing a relative import, if ‘__package__’ does not
     compare equal to ‘__spec__.parent’ then *note ImportWarning: 4a2.
     is raised.  (Contributed by Brett Cannon in bpo-25791(6).)

   * When a relative import is performed and no parent package is known,
     then *note ImportError: 352. will be raised.  Previously, *note
     SystemError: 51b. could be raised.  (Contributed by Brett Cannon in
     bpo-18018(7).)

   * Servers based on the *note socketserver: b9. module, including
     those defined in *note http.server: 68, *note xmlrpc.server: 115.
     and *note wsgiref.simple_server: 103, now only catch exceptions
     derived from *note Exception: 97d.  Therefore if a request handler
     raises an exception like *note SystemExit: ce7. or *note
     KeyboardInterrupt: 975, *note handle_error(): ce8. is no longer
     called, and the exception will stop a single-threaded server.
     (Contributed by Martin Panter in bpo-23430(8).)

   * ‘spwd.getspnam()’ now raises a *note PermissionError: ce9. instead
     of *note KeyError: 2fb. if the user doesn't have privileges.

   * The *note socket.socket.close(): cea. method now raises an
     exception if an error (e.g.  ‘EBADF’) was reported by the
     underlying system call.  (Contributed by Martin Panter in
     bpo-26685(9).)

   * The 'decode_data' argument for the ‘smtpd.SMTPChannel’ and
     ‘smtpd.SMTPServer’ constructors is now ‘False’ by default.  This
     means that the argument passed to ‘process_message()’ is now a
     bytes object by default, and ‘process_message()’ will be passed
     keyword arguments.  Code that has already been updated in
     accordance with the deprecation warning generated by 3.5 will not
     be affected.

   * All optional arguments of the *note dump(): ceb, *note dumps():
     cec, *note load(): c5b. and *note loads(): 8f9. functions and *note
     JSONEncoder: ced. and *note JSONDecoder: cee. class constructors in
     the *note json: 76. module are now *note keyword-only: 285.
     (Contributed by Serhiy Storchaka in bpo-18726(10).)

   * Subclasses of *note type: cef. which don't override ‘type.__new__’
     may no longer use the one-argument form to get the type of an
     object.

   * As part of PEP 487(11), the handling of keyword arguments passed to
     *note type: cef. (other than the metaclass hint, ‘metaclass’) is
     now consistently delegated to *note object.__init_subclass__():
     5d7.  This means that ‘type.__new__()’ and ‘type.__init__()’ both
     now accept arbitrary keyword arguments, but *note
     object.__init_subclass__(): 5d7. (which is called from
     ‘type.__new__()’) will reject them by default.  Custom metaclasses
     accepting additional keyword arguments will need to adjust their
     calls to ‘type.__new__()’ (whether direct or via *note super: 483.)
     accordingly.

   * In ‘distutils.command.sdist.sdist’, the ‘default_format’ attribute
     has been removed and is no longer honored.  Instead, the gzipped
     tarfile format is the default on all platforms and no
     platform-specific selection is made.  In environments where
     distributions are built on Windows and zip distributions are
     required, configure the project with a ‘setup.cfg’ file containing
     the following:

          [sdist]
          formats=zip

     This behavior has also been backported to earlier Python versions
     by Setuptools 26.0.0.

   * In the *note urllib.request: f4. module and the *note
     http.client.HTTPConnection.request(): c50. method, if no
     Content-Length header field has been specified and the request body
     is a file object, it is now sent with HTTP 1.1 chunked encoding.
     If a file object has to be sent to a HTTP 1.0 server, the
     Content-Length value now has to be specified by the caller.
     (Contributed by Demian Brecht and Rolf Krahl with tweaks from
     Martin Panter in bpo-12319(12).)

   * The *note DictReader: 989. now returns rows of type *note
     OrderedDict: 57f.  (Contributed by Steve Holden in bpo-27842(13).)

   * The ‘crypt.METHOD_CRYPT’ will no longer be added to ‘crypt.methods’
     if unsupported by the platform.  (Contributed by Victor Stinner in
     bpo-25287(14).)

   * The 'verbose' and 'rename' arguments for *note namedtuple(): 1ae.
     are now keyword-only.  (Contributed by Raymond Hettinger in
     bpo-25628(15).)

   * On Linux, *note ctypes.util.find_library(): cf0. now looks in
     ‘LD_LIBRARY_PATH’ for shared libraries.  (Contributed by Vinay
     Sajip in bpo-9998(16).)

   * The *note imaplib.IMAP4: 8a8. class now handles flags containing
     the ‘']'’ character in messages sent from the server to improve
     real-world compatibility.  (Contributed by Lita Cho in
     bpo-21815(17).)

   * The ‘mmap.write()’ function now returns the number of bytes written
     like other write methods.  (Contributed by Jakub Stasiak in
     bpo-26335(18).)

   * The *note pkgutil.iter_modules(): cf1. and *note
     pkgutil.walk_packages(): ba6. functions now return *note
     ModuleInfo: cf2. named tuples.  (Contributed by Ramchandra Apte in
     bpo-17211(19).)

   * *note re.sub(): 283. now raises an error for invalid numerical
     group references in replacement templates even if the pattern is
     not found in the string.  The error message for invalid group
     references now includes the group index and the position of the
     reference.  (Contributed by SilentGhost, Serhiy Storchaka in
     bpo-25953(20).)

   * *note zipfile.ZipFile: 669. will now raise *note
     NotImplementedError: 20d. for unrecognized compression values.
     Previously a plain *note RuntimeError: 179. was raised.
     Additionally, calling *note ZipFile: 669. methods on a closed
     ZipFile or calling the *note write(): cf3. method on a ZipFile
     created with mode ‘'r'’ will raise a *note ValueError: 1e7.
     Previously, a *note RuntimeError: 179. was raised in those
     scenarios.

   * when custom metaclasses are combined with zero-argument *note
     super(): 483. or direct references from methods to the implicit
     ‘__class__’ closure variable, the implicit ‘__classcell__’
     namespace entry must now be passed up to ‘type.__new__’ for
     initialisation.  Failing to do so will result in a *note
     DeprecationWarning: 18b. in Python 3.6 and a *note RuntimeError:
     179. in Python 3.8.

   * With the introduction of *note ModuleNotFoundError: aeb, import
     system consumers may start expecting import system replacements to
     raise that more specific exception when appropriate, rather than
     the less-specific *note ImportError: 352.  To provide future
     compatibility with such consumers, implementers of alternative
     import systems that completely replace *note __import__(): 879.
     will need to update their implementations to raise the new subclass
     when a module can't be found at all.  Implementers of compliant
     plugins to the default import system shouldn't need to make any
     changes, as the default import system will raise the new subclass
     when appropriate.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=2091

   (2) https://peps.python.org/pep-0511/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=25768

   (4) https://bugs.python.org/issue?@action=redirect&bpo=20059

   (5) https://bugs.python.org/issue?@action=redirect&bpo=23883

   (6) https://bugs.python.org/issue?@action=redirect&bpo=25791

   (7) https://bugs.python.org/issue?@action=redirect&bpo=18018

   (8) https://bugs.python.org/issue?@action=redirect&bpo=23430

   (9) https://bugs.python.org/issue?@action=redirect&bpo=26685

   (10) https://bugs.python.org/issue?@action=redirect&bpo=18726

   (11) https://peps.python.org/pep-0487/

   (12) https://bugs.python.org/issue?@action=redirect&bpo=12319

   (13) https://bugs.python.org/issue?@action=redirect&bpo=27842

   (14) https://bugs.python.org/issue?@action=redirect&bpo=25287

   (15) https://bugs.python.org/issue?@action=redirect&bpo=25628

   (16) https://bugs.python.org/issue?@action=redirect&bpo=9998

   (17) https://bugs.python.org/issue?@action=redirect&bpo=21815

   (18) https://bugs.python.org/issue?@action=redirect&bpo=26335

   (19) https://bugs.python.org/issue?@action=redirect&bpo=17211

   (20) https://bugs.python.org/issue?@action=redirect&bpo=25953


File: python.info,  Node: C API 中的改動<5>,  Next: CPython 位元組碼變更<7>,  Prev: Changes in the Python API<6>,  Up: Porting to Python 3 6

1.8.11.3 C API 中的改動
.......................

   * The *note PyMem_Malloc(): c0d. allocator family now uses the *note
     pymalloc allocator: cb6. rather than the system ‘malloc()’.
     Applications calling *note PyMem_Malloc(): c0d. without holding the
     GIL can now crash.  Set the *note PYTHONMALLOC: c0b. environment
     variable to ‘debug’ to validate the usage of memory allocators in
     your application.  See bpo-26249(1).

   * *note Py_Exit(): cf5. (and the main interpreter) now override the
     exit status with 120 if flushing buffered data failed.  See
     bpo-5319(2).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26249

   (2) https://bugs.python.org/issue?@action=redirect&bpo=5319


File: python.info,  Node: CPython 位元組碼變更<7>,  Prev: C API 中的改動<5>,  Up: Porting to Python 3 6

1.8.11.4 CPython 位元組碼變更
.............................

There have been several major changes to the *note bytecode: 16d. in
Python 3.6.

   * The Python interpreter now uses a 16-bit wordcode instead of
     bytecode.  (Contributed by Demur Rumed with input and reviews from
     Serhiy Storchaka and Victor Stinner in bpo-26647(1) and
     bpo-28050(2).)

   * The new ‘FORMAT_VALUE’ and *note BUILD_STRING: cf7. opcodes as part
     of the *note formatted string literal: bd6. implementation.
     (Contributed by Eric Smith in bpo-25483(3) and Serhiy Storchaka in
     bpo-27078(4).)

   * The new *note BUILD_CONST_KEY_MAP: cf8. opcode to optimize the
     creation of dictionaries with constant keys.  (Contributed by
     Serhiy Storchaka in bpo-27140(5).)

   * The function call opcodes have been heavily reworked for better
     performance and simpler implementation.  The *note MAKE_FUNCTION:
     cf9, ‘CALL_FUNCTION’, ‘CALL_FUNCTION_KW’ and
     ‘BUILD_MAP_UNPACK_WITH_CALL’ opcodes have been modified, the new
     *note CALL_FUNCTION_EX: cfa. and ‘BUILD_TUPLE_UNPACK_WITH_CALL’
     have been added, and ‘CALL_FUNCTION_VAR’, ‘CALL_FUNCTION_VAR_KW’
     and ‘MAKE_CLOSURE’ opcodes have been removed.  (Contributed by
     Demur Rumed in bpo-27095(6), and Serhiy Storchaka in bpo-27213(7),
     bpo-28257(8).)

   * The new *note SETUP_ANNOTATIONS: cfb. and ‘STORE_ANNOTATION’
     opcodes have been added to support the new *note variable
     annotation: cfc. syntax.  (Contributed by Ivan Levkivskyi in
     bpo-27985(9).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26647

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28050

   (3) https://bugs.python.org/issue?@action=redirect&bpo=25483

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27078

   (5) https://bugs.python.org/issue?@action=redirect&bpo=27140

   (6) https://bugs.python.org/issue?@action=redirect&bpo=27095

   (7) https://bugs.python.org/issue?@action=redirect&bpo=27213

   (8) https://bugs.python.org/issue?@action=redirect&bpo=28257

   (9) https://bugs.python.org/issue?@action=redirect&bpo=27985


File: python.info,  Node: Python 3 6 2 中顯著的變更,  Next: Python 3 6 4 中顯著的變更,  Prev: Porting to Python 3 6,  Up: Python 3 6 有什麼新功能

1.8.12 Python 3.6.2 中顯著的變更
--------------------------------

* Menu:

* New make regen-all build target::
* Removal of make touch build target::


File: python.info,  Node: New make regen-all build target,  Next: Removal of make touch build target,  Up: Python 3 6 2 中顯著的變更

1.8.12.1 New ‘make regen-all’ build target
..........................................

To simplify cross-compilation, and to ensure that CPython can reliably
be compiled without requiring an existing version of Python to already
be available, the autotools-based build system no longer attempts to
implicitly recompile generated files based on file modification times.

Instead, a new ‘make regen-all’ command has been added to force
regeneration of these files when desired (e.g.  after an initial version
of Python has already been built based on the pregenerated versions).

More selective regeneration targets are also defined - see
Makefile.pre.in(1) for details.

（由 Victor Stinner 於 bpo-23404(2) 中貢獻。）

在 3.6.2 版被加入.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Makefile.pre.in

   (2) https://bugs.python.org/issue?@action=redirect&bpo=23404


File: python.info,  Node: Removal of make touch build target,  Prev: New make regen-all build target,  Up: Python 3 6 2 中顯著的變更

1.8.12.2 Removal of ‘make touch’ build target
.............................................

The ‘make touch’ build target previously used to request implicit
regeneration of generated files by updating their modification times has
been removed.

It has been replaced by the new ‘make regen-all’ target.

（由 Victor Stinner 於 bpo-23404(1) 中貢獻。）

在 3.6.2 版的變更.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23404


File: python.info,  Node: Python 3 6 4 中顯著的變更,  Next: Python 3 6 5 中顯著的變更,  Prev: Python 3 6 2 中顯著的變更,  Up: Python 3 6 有什麼新功能

1.8.13 Python 3.6.4 中顯著的變更
--------------------------------

The ‘PyExc_RecursionErrorInst’ singleton that was part of the public API
has been removed as its members being never cleared may cause a segfault
during finalization of the interpreter.  (Contributed by Xavier de Gaye
in bpo-22898(1) and bpo-30697(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22898

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30697


File: python.info,  Node: Python 3 6 5 中顯著的變更,  Next: Python 3 6 7 中顯著的變更,  Prev: Python 3 6 4 中顯著的變更,  Up: Python 3 6 有什麼新功能

1.8.14 Python 3.6.5 中顯著的變更
--------------------------------

The *note locale.localeconv(): ba5. function now sets temporarily the
‘LC_CTYPE’ locale to the ‘LC_NUMERIC’ locale in some cases.
(Contributed by Victor Stinner in bpo-31900(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31900


File: python.info,  Node: Python 3 6 7 中顯著的變更,  Next: Python 3 6 10 中顯著的變更,  Prev: Python 3 6 5 中顯著的變更,  Up: Python 3 6 有什麼新功能

1.8.15 Python 3.6.7 中顯著的變更
--------------------------------

*note xml.dom.minidom: 109. and *note xml.sax: 110. modules no longer
process external entities by default.  See also gh-61441(1).

In 3.6.7 the *note tokenize: e4. module now implicitly emits a ‘NEWLINE’
token when provided with input that does not have a trailing new line.
This behavior now matches what the C tokenizer does internally.
(Contributed by Ammar Askar in bpo-33899(2).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/61441

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33899


File: python.info,  Node: Python 3 6 10 中顯著的變更,  Next: Python 3 6 13 中顯著的變更,  Prev: Python 3 6 7 中顯著的變更,  Up: Python 3 6 有什麼新功能

1.8.16 Python 3.6.10 中顯著的變更
---------------------------------

Due to significant security concerns, the 'reuse_address' parameter of
*note asyncio.loop.create_datagram_endpoint(): 6d7. is no longer
supported.  This is because of the behavior of the socket option
‘SO_REUSEADDR’ in UDP. For more details, see the documentation for
‘loop.create_datagram_endpoint()’.  (Contributed by Kyle Stanley,
Antoine Pitrou, and Yury Selivanov in bpo-37228(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=37228


File: python.info,  Node: Python 3 6 13 中顯著的變更,  Next: Python 3 6 14 中顯著的變更,  Prev: Python 3 6 10 中顯著的變更,  Up: Python 3 6 有什麼新功能

1.8.17 Python 3.6.13 中顯著的變更
---------------------------------

Earlier Python versions allowed using both ‘;’ and ‘&’ as query
parameter separators in *note urllib.parse.parse_qs(): 25f. and *note
urllib.parse.parse_qsl(): 25e.  Due to security concerns, and to conform
with newer W3C recommendations, this has been changed to allow only a
single separator key, with ‘&’ as the default.  This change also affects
‘cgi.parse()’ and ‘cgi.parse_multipart()’ as they use the affected
functions internally.  For more details, please see their respective
documentation.  (Contributed by Adam Goldschmidt, Senthil Kumaran and
Ken Jin in bpo-42967(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42967


File: python.info,  Node: Python 3 6 14 中顯著的變更,  Prev: Python 3 6 13 中顯著的變更,  Up: Python 3 6 有什麼新功能

1.8.18 Python 3.6.14 中顯著的變更
---------------------------------

A security fix alters the *note ftplib.FTP: 89f. behavior to not trust
the IPv4 address sent from the remote server when setting up a passive
data channel.  We reuse the ftp server IP address instead.  For unusual
code requiring the old behavior, set a ‘trust_server_pasv_ipv4_address’
attribute on your FTP instance to ‘True’.  (See gh-87451(1))

The presence of newline or tab characters in parts of a URL allows for
some forms of attacks.  Following the WHATWG specification that updates
RFC 3986, ASCII newline ‘\n’, ‘\r’ and tab ‘\t’ characters are stripped
from the URL by the parser *note urllib.parse(): f3. preventing such
attacks.  The removal characters are controlled by a new module level
variable ‘urllib.parse._UNSAFE_URL_BYTES_TO_REMOVE’.  (See gh-88048(2))

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/87451

   (2) https://github.com/python/cpython/issues/88048


File: python.info,  Node: Python 3 4 有什麼新功能,  Next: Python 3 4 有什麼新功能<2>,  Prev: Python 3 6 有什麼新功能,  Up: Python 有什麼新功能？

1.9 Python 3.4 有什麼新功能
===========================


編輯者: Elvis Pranskevichus <<elvis@magic.io>>, Yury Selivanov
<<yury@magic.io>>

This article explains the new features in Python 3.5, compared to 3.4.
Python 3.5 was released on September 13, 2015.   See the changelog(1)
for a full list of changes.

也參考
......

PEP 478(2) - Python 3.5 Release Schedule

* Menu:

* Summary: Summary -- Release highlights<4>. Release highlights
* New Features: New Features<8>.
* 其他語言更動: 其他語言更動<8>.
* 新增模組: 新增模組<4>.
* 改進的模組: 改進的模組<8>.
* Other module-level changes::
* 最佳化: 最佳化<8>.
* Build and C API Changes: Build and C API Changes<3>.
* 已棄用: 已棄用<10>.
* 已移除: 已移除<8>.
* Porting to Python 3.5: Porting to Python 3 5.
* Python 3.5.4 中顯著的變更: Python 3 5 4 中顯著的變更.

   ---------- Footnotes ----------

   (1) https://docs.python.org/3.5/whatsnew/changelog.html

   (2) https://peps.python.org/pep-0478/


File: python.info,  Node: Summary -- Release highlights<4>,  Next: New Features<8>,  Up: Python 3 4 有什麼新功能

1.9.1 Summary - Release highlights
----------------------------------

新增語法特性：

   * *note PEP 492: d09, coroutines with async and await syntax.

   * *note PEP 465: d0a, a new matrix multiplication operator: ‘a @ b’.

   * *note PEP 448: d0b, additional unpacking generalizations.

New library modules:

   * *note typing: ed.: *note PEP 484 - Type Hints: d0c.

   * *note zipapp: 116.: *note PEP 441 Improving Python ZIP Application
     Support: d0d.

新的內建功能

   * ‘bytes % args’, ‘bytearray % args’: *note PEP 461: d0e. - Adding
     ‘%’ formatting to bytes and bytearray.

   * New *note bytes.hex(): d0f, *note bytearray.hex(): d10. and *note
     memoryview.hex(): d11. methods.  (Contributed by Arnon Yaari in
     bpo-9951(1).)

   * *note memoryview: 40f. now supports tuple indexing (including
     multi-dimensional).  (Contributed by Antoine Pitrou in
     bpo-23632(2).)

   * Generators have a new ‘gi_yieldfrom’ attribute, which returns the
     object being iterated by ‘yield from’ expressions.  (Contributed by
     Benno Leslie and Yury Selivanov in bpo-24450(3).)

   * A new *note RecursionError: d12. exception is now raised when
     maximum recursion depth is reached.  (Contributed by Georg Brandl
     in bpo-19235(4).)

CPython 實作改進：

   * When the ‘LC_TYPE’ locale is the POSIX locale (‘C’ locale), *note
     sys.stdin: 4e2. and *note sys.stdout: a79. now use the
     ‘surrogateescape’ error handler, instead of the ‘strict’ error
     handler.  (Contributed by Victor Stinner in bpo-19977(5).)

   * ‘.pyo’ files are no longer used and have been replaced by a more
     flexible scheme that includes the optimization level explicitly in
     ‘.pyc’ name.  (See *note PEP 488 overview: d13.)

   * Builtin and extension modules are now initialized in a multi-phase
     process, which is similar to how Python modules are loaded.  (See
     *note PEP 489 overview: d14.)

Significant improvements in the standard library:

   * *note collections.OrderedDict: 57f. is now *note implemented in C:
     d15, which makes it 4 to 100 times faster.

   * The *note ssl: bb. module gained *note support for Memory BIO: d16,
     which decouples SSL protocol handling from network IO.

   * The new *note os.scandir(): a02. function provides a *note better
     and significantly faster way: d17. of directory traversal.

   * *note functools.lru_cache(): 993. has been mostly *note
     reimplemented in C: d18, yielding much better performance.

   * The new *note subprocess.run(): b2c. function provides a *note
     streamlined way to run subprocesses: d19.

   * The *note traceback: e7. module has been significantly *note
     enhanced: d1a. for improved performance and developer convenience.

安全性改進：

   * SSLv3 is now disabled throughout the standard library.  It can
     still be enabled by instantiating a *note ssl.SSLContext: 276.
     manually.  (See bpo-22638(6) for more details; this change was
     backported to CPython 3.4 and 2.7.)

   * HTTP cookie parsing is now stricter, in order to protect against
     potential injection attacks.  (Contributed by Antoine Pitrou in
     bpo-22796(7).)

Windows improvements:

   * A new installer for Windows has replaced the old MSI. See *note 在
     Windows 上使用 Python: a4a. for more information.

   * Windows builds now use Microsoft Visual C++ 14.0, and extension
     modules should use the same.

Please read on for a comprehensive list of user-facing changes,
including many other smaller improvements, CPython optimizations,
deprecations, and potential porting issues.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=9951

   (2) https://bugs.python.org/issue?@action=redirect&bpo=23632

   (3) https://bugs.python.org/issue?@action=redirect&bpo=24450

   (4) https://bugs.python.org/issue?@action=redirect&bpo=19235

   (5) https://bugs.python.org/issue?@action=redirect&bpo=19977

   (6) https://bugs.python.org/issue?@action=redirect&bpo=22638

   (7) https://bugs.python.org/issue?@action=redirect&bpo=22796


File: python.info,  Node: New Features<8>,  Next: 其他語言更動<8>,  Prev: Summary -- Release highlights<4>,  Up: Python 3 4 有什麼新功能

1.9.2 New Features
------------------

* Menu:

* PEP 492 - Coroutines with async and await syntax::
* PEP 465 - A dedicated infix operator for matrix multiplication::
* PEP 448 - Additional Unpacking Generalizations::
* PEP 461 - percent formatting support for bytes and bytearray::
* PEP 484 - Type Hints::
* PEP 471 - os.scandir() function: PEP 471 - os scandir function -- a better and faster directory iterator. a better and faster directory iterator
* PEP 475; Retry system calls failing with EINTR: PEP 475 Retry system calls failing with EINTR.
* PEP 479; Change StopIteration handling inside generators: PEP 479 Change StopIteration handling inside generators.
* PEP 485; A function for testing approximate equality: PEP 485 A function for testing approximate equality.
* PEP 486; Make the Python Launcher aware of virtual environments: PEP 486 Make the Python Launcher aware of virtual environments.
* PEP 488; Elimination of PYO files: PEP 488 Elimination of PYO files.
* PEP 489; Multi-phase extension module initialization: PEP 489 Multi-phase extension module initialization.


File: python.info,  Node: PEP 492 - Coroutines with async and await syntax,  Next: PEP 465 - A dedicated infix operator for matrix multiplication,  Up: New Features<8>

1.9.2.1 PEP 492 - Coroutines with async and await syntax
........................................................

PEP 492(1) greatly improves support for asynchronous programming in
Python by adding *note awaitable objects: 193, *note coroutine
functions: d1d, *note asynchronous iteration: d1e, and *note
asynchronous context managers: 579.

Coroutine functions are declared using the new *note async def: 575.
syntax:

     >>> async def coro():
     ...     return 'spam'

Inside a coroutine function, the new *note await: 19f. expression can be
used to suspend coroutine execution until the result is available.  Any
object can be 'awaited', as long as it implements the *note awaitable:
193. protocol by defining the ‘__await__()’ method.

PEP 492 also adds *note async for: a4e. statement for convenient
iteration over asynchronous iterables.

An example of a rudimentary HTTP client written using the new syntax:

     import asyncio

     async def http_get(domain):
         reader, writer = await asyncio.open_connection(domain, 80)

         writer.write(b'\r\n'.join([
             b'GET / HTTP/1.1',
             b'Host: %b' % domain.encode('latin-1'),
             b'Connection: close',
             b'', b''
         ]))

         async for line in reader:
             print('>>>', line)

         writer.close()

     loop = asyncio.get_event_loop()
     try:
         loop.run_until_complete(http_get('example.com'))
     finally:
         loop.close()

Similarly to asynchronous iteration, there is a new syntax for
asynchronous context managers.  The following script:

     import asyncio

     async def coro(name, lock):
         print('coro {}: waiting for lock'.format(name))
         async with lock:
             print('coro {}: holding the lock'.format(name))
             await asyncio.sleep(1)
             print('coro {}: releasing the lock'.format(name))

     loop = asyncio.get_event_loop()
     lock = asyncio.Lock()
     coros = asyncio.gather(coro(1, lock), coro(2, lock))
     try:
         loop.run_until_complete(coros)
     finally:
         loop.close()

will output:

     coro 2: waiting for lock
     coro 2: holding the lock
     coro 1: waiting for lock
     coro 2: releasing the lock
     coro 1: holding the lock
     coro 1: releasing the lock

Note that both *note async for: a4e. and *note async with: 57a. can only
be used inside a coroutine function declared with *note async def: 575.

Coroutine functions are intended to be run inside a compatible event
loop, such as the *note asyncio loop: d1f.

     備註: 
     在 3.5.2 版的變更: Starting with CPython 3.5.2, ‘__aiter__’ can
     directly return *note asynchronous iterators: 191.  Returning an
     *note awaitable: 193. object will result in a *note
     PendingDeprecationWarning: 86d.

     See more details in the *note Asynchronous Iterators: d20.
     documentation section.

也參考
......

PEP 492(2) - Coroutines with async and await syntax

     由 Yury Selivanov 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0492/

   (2) https://peps.python.org/pep-0492/


File: python.info,  Node: PEP 465 - A dedicated infix operator for matrix multiplication,  Next: PEP 448 - Additional Unpacking Generalizations,  Prev: PEP 492 - Coroutines with async and await syntax,  Up: New Features<8>

1.9.2.2 PEP 465 - A dedicated infix operator for matrix multiplication
......................................................................

PEP 465(1) adds the ‘@’ infix operator for matrix multiplication.
Currently, no builtin Python types implement the new operator, however,
it can be implemented by defining ‘__matmul__()’, ‘__rmatmul__()’, and
‘__imatmul__()’ for regular, reflected, and in-place matrix
multiplication.  The semantics of these methods is similar to that of
methods defining other infix arithmetic operators.

Matrix multiplication is a notably common operation in many fields of
mathematics, science, engineering, and the addition of ‘@’ allows
writing cleaner code:

     S = (H @ beta - r).T @ inv(H @ V @ H.T) @ (H @ beta - r)

instead of:

     S = dot((dot(H, beta) - r).T,
             dot(inv(dot(dot(H, V), H.T)), dot(H, beta) - r))

NumPy 1.10 has support for the new operator:

     >>> import numpy

     >>> x = numpy.ones(3)
     >>> x
     array([ 1., 1., 1.])

     >>> m = numpy.eye(3)
     >>> m
     array([[ 1., 0., 0.],
            [ 0., 1., 0.],
            [ 0., 0., 1.]])

     >>> x @ m
     array([ 1., 1., 1.])

也參考
......

PEP 465(2) - A dedicated infix operator for matrix multiplication

     由 Nathaniel J. Smith 撰寫 PEP；由 Benjamin Peterson 實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0465/

   (2) https://peps.python.org/pep-0465/


File: python.info,  Node: PEP 448 - Additional Unpacking Generalizations,  Next: PEP 461 - percent formatting support for bytes and bytearray,  Prev: PEP 465 - A dedicated infix operator for matrix multiplication,  Up: New Features<8>

1.9.2.3 PEP 448 - Additional Unpacking Generalizations
......................................................

PEP 448(1) extends the allowed uses of the ‘*’ iterable unpacking
operator and ‘**’ dictionary unpacking operator.  It is now possible to
use an arbitrary number of unpackings in *note function calls: d23.:

     >>> print(*[1], *[2], 3, *[4, 5])
     1 2 3 4 5

     >>> def fn(a, b, c, d):
     ...     print(a, b, c, d)
     ...

     >>> fn(**{'a': 1, 'c': 3}, **{'b': 2, 'd': 4})
     1 2 3 4

Similarly, tuple, list, set, and dictionary displays allow multiple
unpackings (see *note Expression lists: d24. and *note Dictionary
displays: d25.):

     >>> *range(4), 4
     (0, 1, 2, 3, 4)

     >>> [*range(4), 4]
     [0, 1, 2, 3, 4]

     >>> {*range(4), 4, *(5, 6, 7)}
     {0, 1, 2, 3, 4, 5, 6, 7}

     >>> {'x': 1, **{'y': 2}}
     {'x': 1, 'y': 2}

也參考
......

PEP 448(2) - Additional Unpacking Generalizations

     PEP written by Joshua Landau; implemented by Neil Girdhar, Thomas
     Wouters, and Joshua Landau.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0448/

   (2) https://peps.python.org/pep-0448/


File: python.info,  Node: PEP 461 - percent formatting support for bytes and bytearray,  Next: PEP 484 - Type Hints,  Prev: PEP 448 - Additional Unpacking Generalizations,  Up: New Features<8>

1.9.2.4 PEP 461 - percent formatting support for bytes and bytearray
....................................................................

PEP 461(1) adds support for the ‘%’ *note interpolation operator: d27.
to *note bytes: 1a5. and *note bytearray: 4e3.

While interpolation is usually thought of as a string operation, there
are cases where interpolation on ‘bytes’ or ‘bytearrays’ makes sense,
and the work needed to make up for this missing functionality detracts
from the overall readability of the code.  This issue is particularly
important when dealing with wire format protocols, which are often a
mixture of binary and ASCII compatible text.

範例：

     >>> b'Hello %b!' % b'World'
     b'Hello World!'

     >>> b'x=%i y=%f' % (1, 2.5)
     b'x=1 y=2.500000'

Unicode is not allowed for ‘%b’, but it is accepted by ‘%a’ (equivalent
of ‘repr(obj).encode('ascii', 'backslashreplace')’):

     >>> b'Hello %b!' % 'World'
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: %b requires bytes, or an object that implements __bytes__, not 'str'

     >>> b'price: %a' % '10€'
     b"price: '10\\u20ac'"

Note that ‘%s’ and ‘%r’ conversion types, although supported, should
only be used in codebases that need compatibility with Python 2.

也參考
......

PEP 461(2) - Adding % formatting to bytes and bytearray

     PEP written by Ethan Furman; implemented by Neil Schemenauer and
     Ethan Furman.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0461/

   (2) https://peps.python.org/pep-0461/


File: python.info,  Node: PEP 484 - Type Hints,  Next: PEP 471 - os scandir function -- a better and faster directory iterator,  Prev: PEP 461 - percent formatting support for bytes and bytearray,  Up: New Features<8>

1.9.2.5 PEP 484 - Type Hints
............................

Function annotation syntax has been a Python feature since version 3.0 (
PEP 3107(1)), however the semantics of annotations has been left
undefined.

Experience has shown that the majority of function annotation uses were
to provide type hints to function parameters and return values.  It
became evident that it would be beneficial for Python users, if the
standard library included the base definitions and tools for type
annotations.

PEP 484(2) introduces a *note provisional module: aa6. to provide these
standard definitions and tools, along with some conventions for
situations where annotations are not available.

For example, here is a simple function whose argument and return type
are declared in the annotations:

     def greeting(name: str) -> str:
         return 'Hello ' + name

While these annotations are available at runtime through the usual
‘__annotations__’ attribute, 'no automatic type checking happens at
runtime'.  Instead, it is assumed that a separate off-line type checker
(e.g.  mypy(3)) will be used for on-demand source code analysis.

The type system supports unions, generic types, and a special type named
*note Any: 651. which is consistent with (i.e.  assignable to and from)
all types.

也參考
......

   * *note typing: ed. 模組文件

   * 
     PEP 484(4) - Type Hints

          PEP written by Guido van Rossum, Jukka Lehtosalo, and Łukasz
          Langa; implemented by Guido van Rossum.

   * 
     PEP 483(5) - The Theory of Type Hints

          由 Guido van Rossum 撰寫 PEP

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3107/

   (2) https://peps.python.org/pep-0484/

   (3) https://mypy-lang.org

   (4) https://peps.python.org/pep-0484/

   (5) https://peps.python.org/pep-0483/


File: python.info,  Node: PEP 471 - os scandir function -- a better and faster directory iterator,  Next: PEP 475 Retry system calls failing with EINTR,  Prev: PEP 484 - Type Hints,  Up: New Features<8>

1.9.2.6 PEP 471 - os.scandir() function - a better and faster directory iterator
................................................................................

PEP 471(1) adds a new directory iteration function, *note os.scandir():
a02, to the standard library.  Additionally, *note os.walk(): 451. is
now implemented using ‘scandir’, which makes it 3 to 5 times faster on
POSIX systems and 7 to 20 times faster on Windows systems.  This is
largely achieved by greatly reducing the number of calls to *note
os.stat(): 448. required to walk a directory tree.

Additionally, ‘scandir’ returns an iterator, as opposed to returning a
list of file names, which improves memory efficiency when iterating over
very large directories.

The following example shows a simple use of *note os.scandir(): a02. to
display all the files (excluding directories) in the given 'path' that
don't start with ‘'.'’.  The *note entry.is_file(): d2a. call will
generally not make an additional system call:

     for entry in os.scandir(path):
         if not entry.name.startswith('.') and entry.is_file():
             print(entry.name)

也參考
......

PEP 471(2) - os.scandir() function - a better and faster directory iterator

     在 Victor Stinner 協助下由 Ben Hoyt 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0471/

   (2) https://peps.python.org/pep-0471/


File: python.info,  Node: PEP 475 Retry system calls failing with EINTR,  Next: PEP 479 Change StopIteration handling inside generators,  Prev: PEP 471 - os scandir function -- a better and faster directory iterator,  Up: New Features<8>

1.9.2.7 PEP 475: Retry system calls failing with EINTR
......................................................

An *note errno.EINTR: d2d. error code is returned whenever a system
call, that is waiting for I/O, is interrupted by a signal.  Previously,
Python would raise *note InterruptedError: d2e. in such cases.  This
meant that, when writing a Python application, the developer had two
choices:

  1. Ignore the ‘InterruptedError’.

  2. Handle the ‘InterruptedError’ and attempt to restart the
     interrupted system call at every call site.

The first option makes an application fail intermittently.  The second
option adds a large amount of boilerplate that makes the code nearly
unreadable.  Compare:

     print("Hello World")

和：

     while True:
         try:
             print("Hello World")
             break
         except InterruptedError:
             continue

PEP 475(1) implements automatic retry of system calls on ‘EINTR’.  This
removes the burden of dealing with ‘EINTR’ or *note InterruptedError:
d2e. in user code in most situations and makes Python programs,
including the standard library, more robust.  Note that the system call
is only retried if the signal handler does not raise an exception.

Below is a list of functions which are now retried when interrupted by a
signal:

   * *note open(): 4c0. 和 *note io.open(): 4c1.；

   * *note faulthandler: 4e. 模組的函式；

   * *note os: 91. functions: *note fchdir(): d2f, *note fchmod(): 201,
     *note fchown(): d30, *note fdatasync(): d31, *note fstat(): d32,
     *note fstatvfs(): d33, *note fsync(): d34, *note ftruncate(): d35,
     *note mkfifo(): d36, *note mknod(): d37, *note open(): d38, *note
     posix_fadvise(): d39, *note posix_fallocate(): d3a, *note pread():
     b03, *note pwrite(): b06, *note read(): d3b, *note readv(): b02,
     *note sendfile(): ab2, *note wait3(): d3c, *note wait4(): d3d,
     *note wait(): d3e, *note waitid(): d3f, *note waitpid(): d40, *note
     write(): d41, *note writev(): b05.;

   * special cases: *note os.close(): b18. and *note os.dup2(): b07. now
     ignore *note EINTR: d2d. errors; the syscall is not retried (see
     the PEP for the rationale);

   * *note select: af. functions: *note devpoll.poll(): d42, *note
     epoll.poll(): d43, *note kqueue.control(): d44, *note poll.poll():
     d45, *note select(): d46.;

   * methods of the *note socket: d47. class: *note accept(): d48, *note
     connect(): d49. (except for non-blocking sockets), *note recv():
     d4a, *note recvfrom(): d4b, *note recvmsg(): d4c, *note send():
     d4d, *note sendall(): d4e, *note sendmsg(): 41d, *note sendto():
     d4f.;

   * *note signal.sigtimedwait(): d50. 和 *note signal.sigwaitinfo():
     d51.；

   * *note time.sleep(): 642.。

也參考
......

PEP 475(2) - Retry system calls failing with EINTR

     PEP and implementation written by Charles-François Natali and
     Victor Stinner, with the help of Antoine Pitrou (the French
     connection).

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0475/

   (2) https://peps.python.org/pep-0475/


File: python.info,  Node: PEP 479 Change StopIteration handling inside generators,  Next: PEP 485 A function for testing approximate equality,  Prev: PEP 475 Retry system calls failing with EINTR,  Up: New Features<8>

1.9.2.8 PEP 479: Change StopIteration handling inside generators
................................................................

The interaction of generators and *note StopIteration: ba1. in Python
3.4 and earlier was sometimes surprising, and could conceal obscure
bugs.  Previously, ‘StopIteration’ raised accidentally inside a
generator function was interpreted as the end of the iteration by the
loop construct driving the generator.

PEP 479(1) changes the behavior of generators: when a ‘StopIteration’
exception is raised inside a generator, it is replaced with a *note
RuntimeError: 179. before it exits the generator frame.  The main goal
of this change is to ease debugging in the situation where an unguarded
*note next(): 77c. call raises ‘StopIteration’ and causes the iteration
controlled by the generator to terminate silently.  This is particularly
pernicious in combination with the ‘yield from’ construct.

This is a backwards incompatible change, so to enable the new behavior,
a *note __future__: d53. import is necessary:

     >>> from __future__ import generator_stop

     >>> def gen():
     ...     next(iter([]))
     ...     yield
     ...
     >>> next(gen())
     Traceback (most recent call last):
       File "<stdin>", line 2, in gen
     StopIteration

     The above exception was the direct cause of the following exception:

     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     RuntimeError: generator raised StopIteration

Without a ‘__future__’ import, a *note PendingDeprecationWarning: 86d.
will be raised whenever a *note StopIteration: ba1. exception is raised
inside a generator.

也參考
......

PEP 479(2) - Change StopIteration handling inside generators

     PEP written by Chris Angelico and Guido van Rossum.  Implemented by
     Chris Angelico, Yury Selivanov and Nick Coghlan.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0479/

   (2) https://peps.python.org/pep-0479/


File: python.info,  Node: PEP 485 A function for testing approximate equality,  Next: PEP 486 Make the Python Launcher aware of virtual environments,  Prev: PEP 479 Change StopIteration handling inside generators,  Up: New Features<8>

1.9.2.9 PEP 485: A function for testing approximate equality
............................................................

PEP 485(1) adds the *note math.isclose(): d56. and *note
cmath.isclose(): d57. functions which tell whether two values are
approximately equal or "close" to each other.  Whether or not two values
are considered close is determined according to given absolute and
relative tolerances.  Relative tolerance is the maximum allowed
difference between ‘isclose’ arguments, relative to the larger absolute
value:

     >>> import math
     >>> a = 5.0
     >>> b = 4.99998
     >>> math.isclose(a, b, rel_tol=1e-5)
     True
     >>> math.isclose(a, b, rel_tol=1e-6)
     False

It is also possible to compare two values using absolute tolerance,
which must be a non-negative value:

     >>> import math
     >>> a = 5.0
     >>> b = 4.99998
     >>> math.isclose(a, b, abs_tol=0.00003)
     True
     >>> math.isclose(a, b, abs_tol=0.00001)
     False

也參考
......

PEP 485(2) - A function for testing approximate equality

     PEP written by Christopher Barker; implemented by Chris Barker and
     Tal Einat.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0485/

   (2) https://peps.python.org/pep-0485/


File: python.info,  Node: PEP 486 Make the Python Launcher aware of virtual environments,  Next: PEP 488 Elimination of PYO files,  Prev: PEP 485 A function for testing approximate equality,  Up: New Features<8>

1.9.2.10 PEP 486: Make the Python Launcher aware of virtual environments
........................................................................

PEP 486(1) makes the Windows launcher (see PEP 397(2)) aware of an
active virtual environment.  When the default interpreter would be used
and the ‘VIRTUAL_ENV’ environment variable is set, the interpreter in
the virtual environment will be used.

也參考
......

PEP 486(3) - Make the Python Launcher aware of virtual environments

     由 Paul Moore 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0486/

   (2) https://peps.python.org/pep-0397/

   (3) https://peps.python.org/pep-0486/


File: python.info,  Node: PEP 488 Elimination of PYO files,  Next: PEP 489 Multi-phase extension module initialization,  Prev: PEP 486 Make the Python Launcher aware of virtual environments,  Up: New Features<8>

1.9.2.11 PEP 488: Elimination of PYO files
..........................................

PEP 488(1) does away with the concept of ‘.pyo’ files.  This means that
‘.pyc’ files represent both unoptimized and optimized bytecode.  To
prevent the need to constantly regenerate bytecode files, ‘.pyc’ files
now have an optional ‘opt-’ tag in their name when the bytecode is
optimized.  This has the side-effect of no more bytecode file name
clashes when running under either *note -O: d5b. or *note -OO: d5c.
Consequently, bytecode files generated from *note -O: d5b, and *note
-OO: d5c. may now exist simultaneously.  *note
importlib.util.cache_from_source(): 2cf. has an updated API to help with
this change.

也參考
......

PEP 488(2) - Elimination of PYO files

     由 Brett Cannon 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0488/

   (2) https://peps.python.org/pep-0488/


File: python.info,  Node: PEP 489 Multi-phase extension module initialization,  Prev: PEP 488 Elimination of PYO files,  Up: New Features<8>

1.9.2.12 PEP 489: Multi-phase extension module initialization
.............................................................

PEP 489(1) updates extension module initialization to take advantage of
the two step module loading mechanism introduced by PEP 451(2) in Python
3.4.

This change brings the import semantics of extension modules that opt-in
to using the new mechanism much closer to those of Python source and
bytecode modules, including the ability to use any valid identifier as a
module name, rather than being restricted to ASCII.

也參考
......

PEP 489(3) - Multi-phase extension module initialization

     PEP written by Petr Viktorin, Stefan Behnel, and Nick Coghlan;
     implemented by Petr Viktorin.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0489/

   (2) https://peps.python.org/pep-0451/

   (3) https://peps.python.org/pep-0489/


File: python.info,  Node: 其他語言更動<8>,  Next: 新增模組<4>,  Prev: New Features<8>,  Up: Python 3 4 有什麼新功能

1.9.3 其他語言更動
------------------

Some smaller changes made to the core Python language are:

   * Added the ‘"namereplace"’ error handlers.  The ‘"backslashreplace"’
     error handlers now work with decoding and translating.
     (Contributed by Serhiy Storchaka in bpo-19676(1) and bpo-22286(2).)

   * The *note -b: 587. option now affects comparisons of *note bytes:
     1a5. with *note int: 23c.  (Contributed by Serhiy Storchaka in
     bpo-23681(3).)

   * New Kazakh ‘kz1048’ and Tajik ‘koi8_t’ *note codecs: d5f.
     (Contributed by Serhiy Storchaka in bpo-22682(4) and bpo-22681(5).)

   * Property docstrings are now writable.  This is especially useful
     for *note collections.namedtuple(): 1ae. docstrings.  (Contributed
     by Berker Peksag in bpo-24064(6).)

   * Circular imports involving relative imports are now supported.
     (Contributed by Brett Cannon and Antoine Pitrou in bpo-17636(7).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=19676

   (2) https://bugs.python.org/issue?@action=redirect&bpo=22286

   (3) https://bugs.python.org/issue?@action=redirect&bpo=23681

   (4) https://bugs.python.org/issue?@action=redirect&bpo=22682

   (5) https://bugs.python.org/issue?@action=redirect&bpo=22681

   (6) https://bugs.python.org/issue?@action=redirect&bpo=24064

   (7) https://bugs.python.org/issue?@action=redirect&bpo=17636


File: python.info,  Node: 新增模組<4>,  Next: 改進的模組<8>,  Prev: 其他語言更動<8>,  Up: Python 3 4 有什麼新功能

1.9.4 新增模組
--------------

* Menu:

* typing: typing<10>.
* zipapp: zipapp<2>.


File: python.info,  Node: typing<10>,  Next: zipapp<2>,  Up: 新增模組<4>

1.9.4.1 typing
..............

The new *note typing: ed. *note provisional: aa6. module provides
standard definitions and tools for function type annotations.  See *note
Type Hints: d0c. for more information.


File: python.info,  Node: zipapp<2>,  Prev: typing<10>,  Up: 新增模組<4>

1.9.4.2 zipapp
..............

The new *note zipapp: 116. module (specified in PEP 441(1)) provides an
API and command line tool for creating executable Python Zip
Applications, which were introduced in Python 2.6 in bpo-1739468(2), but
which were not well publicized, either at the time or since.

With the new module, bundling your application is as simple as putting
all the files, including a ‘__main__.py’ file, into a directory ‘myapp’
and running:

     $ python -m zipapp myapp
     $ python myapp.pyz

The module implementation has been contributed by Paul Moore in
bpo-23491(3).

也參考
......

PEP 441(4) - Improving Python ZIP Application Support

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0441/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=1739468

   (3) https://bugs.python.org/issue?@action=redirect&bpo=23491

   (4) https://peps.python.org/pep-0441/


File: python.info,  Node: 改進的模組<8>,  Next: Other module-level changes,  Prev: 新增模組<4>,  Up: Python 3 4 有什麼新功能

1.9.5 改進的模組
----------------

* Menu:

* argparse: argparse<4>.
* asyncio: asyncio<10>.
* bz2::
* cgi::
* cmath: cmath<2>.
* code::
* collections: collections<5>.
* collections.abc: collections abc<3>.
* compileall: compileall<4>.
* concurrent.futures: concurrent futures<5>.
* configparser: configparser<5>.
* contextlib: contextlib<5>.
* csv: csv<3>.
* curses: curses<4>.
* dbm: dbm<5>.
* difflib::
* distutils: distutils<7>.
* doctest: doctest<3>.
* email: email<3>.
* enum: enum<7>.
* faulthandler: faulthandler<3>.
* functools: functools<4>.
* glob: glob<3>.
* gzip: gzip<4>.
* heapq::
* http: http<2>.
* http.client: http client<3>.
* idlelib and IDLE: idlelib and IDLE<3>.
* imaplib: imaplib<2>.
* imghdr::
* importlib: importlib<8>.
* inspect: inspect<7>.
* io: io<5>.
* ipaddress: ipaddress<4>.
* json: json<2>.
* linecache: linecache<2>.
* locale: locale<6>.
* logging: logging<5>.
* lzma::
* math: math<8>.
* multiprocessing: multiprocessing<6>.
* operator: operator<2>.
* os: os<10>.
* pathlib: pathlib<10>.
* pickle: pickle<3>.
* poplib: poplib<2>.
* re: re<7>.
* readline: readline<2>.
* selectors::
* shutil: shutil<5>.
* signal: signal<3>.
* smtpd: smtpd<2>.
* smtplib: smtplib<2>.
* sndhdr::
* socket: socket<8>.
* ssl: ssl<9>.
* sqlite3: sqlite3<8>.
* subprocess: subprocess<4>.
* sys: sys<10>.
* sysconfig: sysconfig<2>.
* tarfile: tarfile<6>.
* threading: threading<6>.
* time: time<7>.
* timeit: timeit<2>.
* tkinter: tkinter<8>.
* traceback: traceback<5>.
* types: types<5>.
* unicodedata: unicodedata<8>.
* unittest: unittest<8>.
* unittest.mock: unittest mock<3>.
* urllib: urllib<2>.
* wsgiref::
* xmlrpc: xmlrpc<2>.
* xml.sax: xml sax.
* zipfile: zipfile<4>.


File: python.info,  Node: argparse<4>,  Next: asyncio<10>,  Up: 改進的模組<8>

1.9.5.1 argparse
................

The *note ArgumentParser: 4de. class now allows disabling *note
abbreviated usage: d65. of long options by setting *note allow_abbrev:
d66. to ‘False’.  (Contributed by Jonathan Paugh, Steven Bethard, paul
j3 and Daniel Eriksson in bpo-14910(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=14910


File: python.info,  Node: asyncio<10>,  Next: bz2,  Prev: argparse<4>,  Up: 改進的模組<8>

1.9.5.2 asyncio
...............

Since the *note asyncio: 8. module is *note provisional: aa6, all
changes introduced in Python 3.5 have also been backported to Python
3.4.x.

Notable changes in the *note asyncio: 8. module since Python 3.4.0:

   * New debugging APIs: *note loop.set_debug(): d68. and *note
     loop.get_debug(): d69. methods.  (Contributed by Victor Stinner.)

   * The proactor event loop now supports SSL. (Contributed by Antoine
     Pitrou and Victor Stinner in bpo-22560(1).)

   * A new *note loop.is_closed(): d6a. method to check if the event
     loop is closed.  (Contributed by Victor Stinner in bpo-21326(2).)

   * A new *note loop.create_task(): 980. to conveniently create and
     schedule a new *note Task: 480. for a coroutine.  The ‘create_task’
     method is also used by all asyncio functions that wrap coroutines
     into tasks, such as *note asyncio.wait(): 426, *note
     asyncio.gather(): 5a2, etc.  (Contributed by Victor Stinner.)

   * A new *note transport.get_write_buffer_limits(): d6b. method to
     inquire for 'high-' and 'low-' water limits of the flow control.
     (Contributed by Victor Stinner.)

   * The ‘async()’ function is deprecated in favor of *note
     ensure_future(): c1d.  (Contributed by Yury Selivanov.)

   * New *note loop.set_task_factory(): d6c. and *note
     loop.get_task_factory(): d6d. methods to customize the task factory
     that *note loop.create_task(): 980. method uses.  (Contributed by
     Yury Selivanov.)

   * New *note Queue.join(): d6e. and *note Queue.task_done(): d6f.
     queue methods.  (Contributed by Victor Stinner.)

   * The ‘JoinableQueue’ class was removed, in favor of the *note
     asyncio.Queue: a19. class.  (Contributed by Victor Stinner.)

Updates in 3.5.1:

   * The *note ensure_future(): c1d. function and all functions that use
     it, such as *note loop.run_until_complete(): c1e, now accept all
     kinds of *note awaitable objects: 193.  (Contributed by Yury
     Selivanov.)

   * New *note run_coroutine_threadsafe(): 826. function to submit
     coroutines to event loops from other threads.  (Contributed by
     Vincent Michel.)

   * New *note Transport.is_closing(): c1f. method to check if the
     transport is closing or closed.  (Contributed by Yury Selivanov.)

   * The *note loop.create_server(): ab6. method can now accept a list
     of hosts.  (Contributed by Yann Sionneau.)

Updates in 3.5.2:

   * New *note loop.create_future(): c20. method to create Future
     objects.  This allows alternative event loop implementations, such
     as uvloop(3), to provide a faster *note asyncio.Future: b74.
     implementation.  (Contributed by Yury Selivanov.)

   * New *note loop.get_exception_handler(): c21. method to get the
     current exception handler.  (Contributed by Yury Selivanov.)

   * New *note StreamReader.readuntil(): 19a. method to read data from
     the stream until a separator bytes sequence appears.  (Contributed
     by Mark Korenberg.)

   * The *note loop.create_connection(): 5a8. and *note
     loop.create_server(): ab6. methods are optimized to avoid calling
     the system ‘getaddrinfo’ function if the address is already
     resolved.  (Contributed by A. Jesse Jiryu Davis.)

   * The *note loop.sock_connect(sock, address): d70. no longer requires
     the 'address' to be resolved prior to the call.  (Contributed by A.
     Jesse Jiryu Davis.)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22560

   (2) https://bugs.python.org/issue?@action=redirect&bpo=21326

   (3) https://github.com/MagicStack/uvloop


File: python.info,  Node: bz2,  Next: cgi,  Prev: asyncio<10>,  Up: 改進的模組<8>

1.9.5.3 bz2
...........

The *note BZ2Decompressor.decompress: d72. method now accepts an
optional 'max_length' argument to limit the maximum size of decompressed
data.  (Contributed by Nikolaus Rath in bpo-15955(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=15955


File: python.info,  Node: cgi,  Next: cmath<2>,  Prev: bz2,  Up: 改進的模組<8>

1.9.5.4 cgi
...........

The ‘FieldStorage’ class now supports the *note context manager: 576.
protocol.  (Contributed by Berker Peksag in bpo-20289(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=20289


File: python.info,  Node: cmath<2>,  Next: code,  Prev: cgi,  Up: 改進的模組<8>

1.9.5.5 cmath
.............

A new function *note isclose(): d57. provides a way to test for
approximate equality.  (Contributed by Chris Barker and Tal Einat in
bpo-24270(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24270


File: python.info,  Node: code,  Next: collections<5>,  Prev: cmath<2>,  Up: 改進的模組<8>

1.9.5.6 code
............

The *note InteractiveInterpreter.showtraceback(): d76. method now prints
the full chained traceback, just like the interactive interpreter.
(Contributed by Claudiu Popa in bpo-17442(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=17442


File: python.info,  Node: collections<5>,  Next: collections abc<3>,  Prev: code,  Up: 改進的模組<8>

1.9.5.7 collections
...................

The *note OrderedDict: 57f. class is now implemented in C, which makes
it 4 to 100 times faster.  (Contributed by Eric Snow in bpo-16991(1).)

‘OrderedDict.items()’, ‘OrderedDict.keys()’, ‘OrderedDict.values()’
views now support *note reversed(): 80a. iteration.  (Contributed by
Serhiy Storchaka in bpo-19505(2).)

The *note deque: 580. class now defines *note index(): d78, *note
insert(): d79, and *note copy(): d7a, and supports the ‘+’ and ‘*’
operators.  This allows deques to be recognized as a *note
MutableSequence: 187. and improves their substitutability for lists.
(Contributed by Raymond Hettinger in bpo-23704(3).)

Docstrings produced by *note namedtuple(): 1ae. can now be updated:

     Point = namedtuple('Point', ['x', 'y'])
     Point.__doc__ += ': Cartesian coordinate'
     Point.x.__doc__ = 'abscissa'
     Point.y.__doc__ = 'ordinate'

（由 Berker Peksag 在 bpo-24064(4) 中貢獻。）

The *note UserString: d7b. class now implements the ‘__getnewargs__()’,
‘__rmod__()’, *note casefold(): d7c, *note format_map(): d7d, *note
isprintable(): d7e, and *note maketrans(): d7f. methods to match the
corresponding methods of *note str: 3f2.  (Contributed by Joe Jevnik in
bpo-22189(5).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16991

   (2) https://bugs.python.org/issue?@action=redirect&bpo=19505

   (3) https://bugs.python.org/issue?@action=redirect&bpo=23704

   (4) https://bugs.python.org/issue?@action=redirect&bpo=24064

   (5) https://bugs.python.org/issue?@action=redirect&bpo=22189


File: python.info,  Node: collections abc<3>,  Next: compileall<4>,  Prev: collections<5>,  Up: 改進的模組<8>

1.9.5.8 collections.abc
.......................

The ‘Sequence.index()’ method now accepts 'start' and 'stop' arguments
to match the corresponding methods of *note tuple: 322, *note list: 5b6,
etc.  (Contributed by Devin Jeanpierre in bpo-23086(1).)

A new *note Generator: d81. abstract base class.  (Contributed by Stefan
Behnel in bpo-24018(2).)

New *note Awaitable: d82, *note Coroutine: d83, *note AsyncIterator:
d84, and *note AsyncIterable: d85. abstract base classes.  (Contributed
by Yury Selivanov in bpo-24184(3).)

For earlier Python versions, a backport of the new ABCs is available in
an external PyPI package(4).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23086

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24018

   (3) https://bugs.python.org/issue?@action=redirect&bpo=24184

   (4) https://pypi.org/project/backports_abc/


File: python.info,  Node: compileall<4>,  Next: concurrent futures<5>,  Prev: collections abc<3>,  Up: 改進的模組<8>

1.9.5.9 compileall
..................

A new *note compileall: 19. option, ‘-j N’, allows running 'N' workers
simultaneously to perform parallel bytecode compilation.  The *note
compile_dir(): aca. function has a corresponding ‘workers’ parameter.
(Contributed by Claudiu Popa in bpo-16104(1).)

Another new option, ‘-r’, allows controlling the maximum recursion level
for subdirectories.  (Contributed by Claudiu Popa in bpo-19628(2).)

The ‘-q’ command line option can now be specified more than once, in
which case all output, including errors, will be suppressed.  The
corresponding ‘quiet’ parameter in *note compile_dir(): aca, *note
compile_file(): d87, and *note compile_path(): d88. can now accept an
integer value indicating the level of output suppression.  (Contributed
by Thomas Kluyver in bpo-21338(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16104

   (2) https://bugs.python.org/issue?@action=redirect&bpo=19628

   (3) https://bugs.python.org/issue?@action=redirect&bpo=21338


File: python.info,  Node: concurrent futures<5>,  Next: configparser<5>,  Prev: compileall<4>,  Up: 改進的模組<8>

1.9.5.10 concurrent.futures
...........................

The *note Executor.map(): d8a. method now accepts a 'chunksize' argument
to allow batching of tasks to improve performance when *note
ProcessPoolExecutor(): 893. is used.  (Contributed by Dan O'Reilly in
bpo-11271(1).)

The number of workers in the *note ThreadPoolExecutor: 6e6. constructor
is optional now.  The default value is 5 times the number of CPUs.
(Contributed by Claudiu Popa in bpo-21527(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=11271

   (2) https://bugs.python.org/issue?@action=redirect&bpo=21527


File: python.info,  Node: configparser<5>,  Next: contextlib<5>,  Prev: concurrent futures<5>,  Up: 改進的模組<8>

1.9.5.11 configparser
.....................

*note configparser: 1b. now provides a way to customize the conversion
of values by specifying a dictionary of converters in the *note
ConfigParser: 1aa. constructor, or by defining them as methods in
‘ConfigParser’ subclasses.  Converters defined in a parser instance are
inherited by its section proxies.

範例：

     >>> import configparser
     >>> conv = {}
     >>> conv['list'] = lambda v: [e.strip() for e in v.split() if e.strip()]
     >>> cfg = configparser.ConfigParser(converters=conv)
     >>> cfg.read_string("""
     ... [s]
     ... list = a b c d e f g
     ... """)
     >>> cfg.get('s', 'list')
     'a b c d e f g'
     >>> cfg.getlist('s', 'list')
     ['a', 'b', 'c', 'd', 'e', 'f', 'g']
     >>> section = cfg['s']
     >>> section.getlist('list')
     ['a', 'b', 'c', 'd', 'e', 'f', 'g']

（由 Łukasz Langa 在 bpo-18159(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=18159


File: python.info,  Node: contextlib<5>,  Next: csv<3>,  Prev: configparser<5>,  Up: 改進的模組<8>

1.9.5.12 contextlib
...................

The new *note redirect_stderr(): d8d. *note context manager: 576.
(similar to *note redirect_stdout(): d8e.) makes it easier for utility
scripts to handle inflexible APIs that write their output to *note
sys.stderr: 8dd. and don't provide any options to redirect it:

     >>> import contextlib, io, logging
     >>> f = io.StringIO()
     >>> with contextlib.redirect_stderr(f):
     ...     logging.warning('warning')
     ...
     >>> f.getvalue()
     'WARNING:root:warning\n'

（由 Berker Peksag 在 bpo-22389(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22389


File: python.info,  Node: csv<3>,  Next: curses<4>,  Prev: contextlib<5>,  Up: 改進的模組<8>

1.9.5.13 csv
............

The *note writerow(): d90. method now supports arbitrary iterables, not
just sequences.  (Contributed by Serhiy Storchaka in bpo-23171(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23171


File: python.info,  Node: curses<4>,  Next: dbm<5>,  Prev: csv<3>,  Up: 改進的模組<8>

1.9.5.14 curses
...............

The new *note update_lines_cols(): d92. function updates the ‘LINES’ and
‘COLS’ module variables.  This is useful for detecting manual screen
resizing.  (Contributed by Arnon Yaari in bpo-4254(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=4254


File: python.info,  Node: dbm<5>,  Next: difflib,  Prev: curses<4>,  Up: 改進的模組<8>

1.9.5.15 dbm
............

*note dumb.open: a39. always creates a new database when the flag has
the value ‘"n"’.  (Contributed by Claudiu Popa in bpo-18039(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=18039


File: python.info,  Node: difflib,  Next: distutils<7>,  Prev: dbm<5>,  Up: 改進的模組<8>

1.9.5.16 difflib
................

The charset of HTML documents generated by *note HtmlDiff.make_file():
d95. can now be customized by using a new 'charset' keyword-only
argument.  The default charset of HTML document changed from
‘"ISO-8859-1"’ to ‘"utf-8"’.  (Contributed by Berker Peksag in
bpo-2052(1).)

The *note diff_bytes(): d96. function can now compare lists of byte
strings.  This fixes a regression from Python 2.  (Contributed by Terry
J. Reedy and Greg Ward in bpo-17445(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=2052

   (2) https://bugs.python.org/issue?@action=redirect&bpo=17445


File: python.info,  Node: distutils<7>,  Next: doctest<3>,  Prev: difflib,  Up: 改進的模組<8>

1.9.5.17 distutils
..................

Both the ‘build’ and ‘build_ext’ commands now accept a ‘-j’ option to
enable parallel building of extension modules.  (Contributed by Antoine
Pitrou in bpo-5309(1).)

The ‘distutils’ module now supports ‘xz’ compression, and can be enabled
by passing ‘xztar’ as an argument to ‘bdist --format’.  (Contributed by
Serhiy Storchaka in bpo-16314(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=5309

   (2) https://bugs.python.org/issue?@action=redirect&bpo=16314


File: python.info,  Node: doctest<3>,  Next: email<3>,  Prev: distutils<7>,  Up: 改進的模組<8>

1.9.5.18 doctest
................

The *note DocTestSuite(): d99. function returns an empty *note
unittest.TestSuite: d9a. if 'module' contains no docstrings, instead of
raising *note ValueError: 1e7.  (Contributed by Glenn Jones in
bpo-15916(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=15916


File: python.info,  Node: email<3>,  Next: enum<7>,  Prev: doctest<3>,  Up: 改進的模組<8>

1.9.5.19 email
..............

A new policy option *note Policy.mangle_from_: d9c. controls whether or
not lines that start with ‘"From "’ in email bodies are prefixed with a
‘">"’ character by generators.  The default is ‘True’ for *note
compat32: c40. and ‘False’ for all other policies.  (Contributed by
Milan Oberkirch in bpo-20098(1).)

A new *note Message.get_content_disposition(): d9d. method provides easy
access to a canonical value for the ‘Content-Disposition’ header.
(Contributed by Abhilash Raj in bpo-21083(2).)

A new policy option *note EmailPolicy.utf8: d9e. can be set to ‘True’ to
encode email headers using the UTF-8 charset instead of using encoded
words.  This allows ‘Messages’ to be formatted according to RFC 6532(3)
and used with an SMTP server that supports the RFC 6531(4) ‘SMTPUTF8’
extension.  (Contributed by R. David Murray in bpo-24211(5).)

The *note mime.text.MIMEText: d9f. constructor now accepts a *note
charset.Charset: da0. instance.  (Contributed by Claude Paroz and Berker
Peksag in bpo-16324(6).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=20098

   (2) https://bugs.python.org/issue?@action=redirect&bpo=21083

   (3) https://datatracker.ietf.org/doc/html/rfc6532.html

   (4) https://datatracker.ietf.org/doc/html/rfc6531.html

   (5) https://bugs.python.org/issue?@action=redirect&bpo=24211

   (6) https://bugs.python.org/issue?@action=redirect&bpo=16324


File: python.info,  Node: enum<7>,  Next: faulthandler<3>,  Prev: email<3>,  Up: 改進的模組<8>

1.9.5.20 enum
.............

The *note Enum: 5d6. callable has a new parameter 'start' to specify the
initial number of enum values if only 'names' are provided:

     >>> Animal = enum.Enum('Animal', 'cat dog', start=10)
     >>> Animal.cat
     <Animal.cat: 10>
     >>> Animal.dog
     <Animal.dog: 11>

（由 Ethan Furman 在 bpo-21706(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21706


File: python.info,  Node: faulthandler<3>,  Next: functools<4>,  Prev: enum<7>,  Up: 改進的模組<8>

1.9.5.21 faulthandler
.....................

The *note enable(): c45, *note register(): da3, *note dump_traceback():
da4. and *note dump_traceback_later(): da5. functions now accept file
descriptors in addition to file-like objects.  (Contributed by Wei Wu in
bpo-23566(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23566


File: python.info,  Node: functools<4>,  Next: glob<3>,  Prev: faulthandler<3>,  Up: 改進的模組<8>

1.9.5.22 functools
..................

Most of the *note lru_cache(): 993. machinery is now implemented in C,
making it significantly faster.  (Contributed by Matt Joiner, Alexey
Kachayev, and Serhiy Storchaka in bpo-14373(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=14373


File: python.info,  Node: glob<3>,  Next: gzip<4>,  Prev: functools<4>,  Up: 改進的模組<8>

1.9.5.23 glob
.............

The *note iglob(): 7ab. and *note glob(): 280. functions now support
recursive search in subdirectories, using the ‘"**"’ pattern.
(Contributed by Serhiy Storchaka in bpo-13968(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=13968


File: python.info,  Node: gzip<4>,  Next: heapq,  Prev: glob<3>,  Up: 改進的模組<8>

1.9.5.24 gzip
.............

The 'mode' argument of the *note GzipFile: 354. constructor now accepts
‘"x"’ to request exclusive creation.  (Contributed by Tim Heaney in
bpo-19222(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=19222


File: python.info,  Node: heapq,  Next: http<2>,  Prev: gzip<4>,  Up: 改進的模組<8>

1.9.5.25 heapq
..............

Element comparison in *note merge(): daa. can now be customized by
passing a *note key function: dab. in a new optional 'key' keyword
argument, and a new optional 'reverse' keyword argument can be used to
reverse element comparison:

     >>> import heapq
     >>> a = ['9', '777', '55555']
     >>> b = ['88', '6666']
     >>> list(heapq.merge(a, b, key=len))
     ['9', '88', '777', '6666', '55555']
     >>> list(heapq.merge(reversed(a), reversed(b), key=len, reverse=True))
     ['55555', '6666', '777', '88', '9']

（由 Raymond Hettinger 在 bpo-13742(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=13742


File: python.info,  Node: http<2>,  Next: http client<3>,  Prev: heapq,  Up: 改進的模組<8>

1.9.5.26 http
.............

A new *note HTTPStatus: 8a5. enum that defines a set of HTTP status
codes, reason phrases and long descriptions written in English.
(Contributed by Demian Brecht in bpo-21793(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21793


File: python.info,  Node: http client<3>,  Next: idlelib and IDLE<3>,  Prev: http<2>,  Up: 改進的模組<8>

1.9.5.27 http.client
....................

*note HTTPConnection.getresponse(): dae. now raises a *note
RemoteDisconnected: daf. exception when a remote server connection is
closed unexpectedly.  Additionally, if a *note ConnectionError: db0. (of
which ‘RemoteDisconnected’ is a subclass) is raised, the client socket
is now closed automatically, and will reconnect on the next request:

     import http.client
     conn = http.client.HTTPConnection('www.python.org')
     for retries in range(3):
         try:
             conn.request('GET', '/')
             resp = conn.getresponse()
         except http.client.RemoteDisconnected:
             pass

（由 Martin Panter 在 bpo-3566(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=3566


File: python.info,  Node: idlelib and IDLE<3>,  Next: imaplib<2>,  Prev: http client<3>,  Up: 改進的模組<8>

1.9.5.28 idlelib and IDLE
.........................

Since idlelib implements the IDLE shell and editor and is not intended
for import by other programs, it gets improvements with every release.
See ‘Lib/idlelib/NEWS.txt’ for a cumulative list of changes since 3.4.0,
as well as changes made in future 3.5.x releases.  This file is also
available from the IDLE Help ‣ About IDLE dialog.


File: python.info,  Node: imaplib<2>,  Next: imghdr,  Prev: idlelib and IDLE<3>,  Up: 改進的模組<8>

1.9.5.29 imaplib
................

The *note IMAP4: 8a8. class now supports the *note context manager: 576.
protocol.  When used in a *note with: 577. statement, the IMAP4 ‘LOGOUT’
command will be called automatically at the end of the block.
(Contributed by Tarek Ziadé and Serhiy Storchaka in bpo-4972(1).)

The *note imaplib: 6a. module now supports RFC 5161(2) (ENABLE
Extension) and RFC 6855(3) (UTF-8 Support) via the *note IMAP4.enable():
db3. method.  A new *note IMAP4.utf8_enabled: db4. attribute tracks
whether or not RFC 6855(4) support is enabled.  (Contributed by Milan
Oberkirch, R. David Murray, and Maciej Szulik in bpo-21800(5).)

The *note imaplib: 6a. module now automatically encodes non-ASCII string
usernames and passwords using UTF-8, as recommended by the RFCs.
(Contributed by Milan Oberkirch in bpo-21800(6).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=4972

   (2) https://datatracker.ietf.org/doc/html/rfc5161.html

   (3) https://datatracker.ietf.org/doc/html/rfc6855.html

   (4) https://datatracker.ietf.org/doc/html/rfc6855.html

   (5) https://bugs.python.org/issue?@action=redirect&bpo=21800

   (6) https://bugs.python.org/issue?@action=redirect&bpo=21800


File: python.info,  Node: imghdr,  Next: importlib<8>,  Prev: imaplib<2>,  Up: 改進的模組<8>

1.9.5.30 imghdr
...............

The ‘what()’ function now recognizes the OpenEXR(1) format (contributed
by Martin Vignali and Claudiu Popa in bpo-20295(2)), and the WebP(3)
format (contributed by Fabrice Aneche and Claudiu Popa in bpo-20197(4).)

   ---------- Footnotes ----------

   (1) https://www.openexr.com

   (2) https://bugs.python.org/issue?@action=redirect&bpo=20295

   (3) https://en.wikipedia.org/wiki/WebP

   (4) https://bugs.python.org/issue?@action=redirect&bpo=20197


File: python.info,  Node: importlib<8>,  Next: inspect<7>,  Prev: imghdr,  Up: 改進的模組<8>

1.9.5.31 importlib
..................

The *note util.LazyLoader: c54. class allows for lazy loading of modules
in applications where startup time is important.  (Contributed by Brett
Cannon in bpo-17621(1).)

The *note abc.InspectLoader.source_to_code(): db7. method is now a
static method.  This makes it easier to initialize a module object with
code compiled from a string by running ‘exec(code, module.__dict__)’.
(Contributed by Brett Cannon in bpo-21156(2).)

The new *note util.module_from_spec(): db8. function is now the
preferred way to create a new module.  As opposed to creating a *note
types.ModuleType: db9. instance directly, this new function will set the
various import-controlled attributes based on the passed-in spec object.
(Contributed by Brett Cannon in bpo-20383(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=17621

   (2) https://bugs.python.org/issue?@action=redirect&bpo=21156

   (3) https://bugs.python.org/issue?@action=redirect&bpo=20383


File: python.info,  Node: inspect<7>,  Next: io<5>,  Prev: importlib<8>,  Up: 改進的模組<8>

1.9.5.32 inspect
................

Both the *note Signature: 1b3. and *note Parameter: 1b4. classes are now
picklable and hashable.  (Contributed by Yury Selivanov in bpo-20726(1)
and bpo-20334(2).)

A new *note BoundArguments.apply_defaults(): dbb. method provides a way
to set default values for missing arguments:

     >>> def foo(a, b='ham', *args): pass
     >>> ba = inspect.signature(foo).bind('spam')
     >>> ba.apply_defaults()
     >>> ba.arguments
     OrderedDict([('a', 'spam'), ('b', 'ham'), ('args', ())])

（由 Yury Selivanov 在 bpo-24190(3) 中貢獻。）

A new class method *note Signature.from_callable(): 6de. makes
subclassing of *note Signature: 1b3. easier.  (Contributed by Yury
Selivanov and Eric Snow in bpo-17373(4).)

The *note signature(): 6dc. function now accepts a 'follow_wrapped'
optional keyword argument, which, when set to ‘False’, disables
automatic following of ‘__wrapped__’ links.  (Contributed by Yury
Selivanov in bpo-20691(5).)

A set of new functions to inspect *note coroutine functions: d1d. and
*note coroutine objects: 438. has been added: *note iscoroutine(): dbc,
*note iscoroutinefunction(): 439, *note isawaitable(): dbd, *note
getcoroutinelocals(): dbe, and *note getcoroutinestate(): dbf.
(Contributed by Yury Selivanov in bpo-24017(6) and bpo-24400(7).)

The *note stack(): 5f8, *note trace(): 5f9, *note getouterframes(): 5f6,
and *note getinnerframes(): 5f7. functions now return a list of named
tuples.  (Contributed by Daniel Shahaf in bpo-16808(8).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=20726

   (2) https://bugs.python.org/issue?@action=redirect&bpo=20334

   (3) https://bugs.python.org/issue?@action=redirect&bpo=24190

   (4) https://bugs.python.org/issue?@action=redirect&bpo=17373

   (5) https://bugs.python.org/issue?@action=redirect&bpo=20691

   (6) https://bugs.python.org/issue?@action=redirect&bpo=24017

   (7) https://bugs.python.org/issue?@action=redirect&bpo=24400

   (8) https://bugs.python.org/issue?@action=redirect&bpo=16808


File: python.info,  Node: io<5>,  Next: ipaddress<4>,  Prev: inspect<7>,  Up: 改進的模組<8>

1.9.5.33 io
...........

A new *note BufferedIOBase.readinto1(): dc1. method, that uses at most
one call to the underlying raw stream's *note RawIOBase.read(): dc2. or
*note RawIOBase.readinto(): dc3. methods.  (Contributed by Nikolaus Rath
in bpo-20578(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=20578


File: python.info,  Node: ipaddress<4>,  Next: json<2>,  Prev: io<5>,  Up: 改進的模組<8>

1.9.5.34 ipaddress
..................

Both the *note IPv4Network: 1e3. and *note IPv6Network: 1e4. classes now
accept an ‘(address, netmask)’ tuple argument, so as to easily construct
network objects from existing addresses:

     >>> import ipaddress
     >>> ipaddress.IPv4Network(('127.0.0.0', 8))
     IPv4Network('127.0.0.0/8')
     >>> ipaddress.IPv4Network(('127.0.0.0', '255.0.0.0'))
     IPv4Network('127.0.0.0/8')

（由 Peter Moody 和 Antoine Pitrou 在 bpo-16531(1) 中貢獻。）

A new ‘reverse_pointer’ attribute for the *note IPv4Network: 1e3. and
*note IPv6Network: 1e4. classes returns the name of the reverse DNS PTR
record:

     >>> import ipaddress
     >>> addr = ipaddress.IPv4Address('127.0.0.1')
     >>> addr.reverse_pointer
     '1.0.0.127.in-addr.arpa'
     >>> addr6 = ipaddress.IPv6Address('::1')
     >>> addr6.reverse_pointer
     '1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa'

（由 Leon Weber 在 bpo-20480(2) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16531

   (2) https://bugs.python.org/issue?@action=redirect&bpo=20480


File: python.info,  Node: json<2>,  Next: linecache<2>,  Prev: ipaddress<4>,  Up: 改進的模組<8>

1.9.5.35 json
.............

The *note json.tool: 77. command line interface now preserves the order
of keys in JSON objects passed in input.  The new ‘--sort-keys’ option
can be used to sort the keys alphabetically.  (Contributed by Berker
Peksag in bpo-21650(1).)

JSON decoder now raises *note JSONDecodeError: dc6. instead of *note
ValueError: 1e7. to provide better context information about the error.
(Contributed by Serhiy Storchaka in bpo-19361(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21650

   (2) https://bugs.python.org/issue?@action=redirect&bpo=19361


File: python.info,  Node: linecache<2>,  Next: locale<6>,  Prev: json<2>,  Up: 改進的模組<8>

1.9.5.36 linecache
..................

A new *note lazycache(): dc8. function can be used to capture
information about a non-file-based module to permit getting its lines
later via *note getline(): dc9.  This avoids doing I/O until a line is
actually needed, without having to carry the module globals around
indefinitely.  (Contributed by Robert Collins in bpo-17911(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=17911


File: python.info,  Node: locale<6>,  Next: logging<5>,  Prev: linecache<2>,  Up: 改進的模組<8>

1.9.5.37 locale
...............

A new *note delocalize(): dcb. function can be used to convert a string
into a normalized number string, taking the ‘LC_NUMERIC’ settings into
account:

     >>> import locale
     >>> locale.setlocale(locale.LC_NUMERIC, 'de_DE.UTF-8')
     'de_DE.UTF-8'
     >>> locale.delocalize('1.234,56')
     '1234.56'
     >>> locale.setlocale(locale.LC_NUMERIC, 'en_US.UTF-8')
     'en_US.UTF-8'
     >>> locale.delocalize('1,234.56')
     '1234.56'

（由 Cédric Krier 在 bpo-13918(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=13918


File: python.info,  Node: logging<5>,  Next: lzma,  Prev: locale<6>,  Up: 改進的模組<8>

1.9.5.38 logging
................

All logging methods (*note Logger: af3. *note log(): dcd, *note
exception(): dce, *note critical(): dcf, *note debug(): dd0, etc.), now
accept exception instances as an 'exc_info' argument, in addition to
boolean values and exception tuples:

     >>> import logging
     >>> try:
     ...     1/0
     ... except ZeroDivisionError as ex:
     ...     logging.error('exception', exc_info=ex)
     ERROR:root:exception

（由 Yury Selivanov 在 bpo-20537(1) 中貢獻。）

The *note handlers.HTTPHandler: dd1. class now accepts an optional *note
ssl.SSLContext: 276. instance to configure SSL settings used in an HTTP
connection.  (Contributed by Alex Gaynor in bpo-22788(2).)

The *note handlers.QueueListener: dd2. class now takes a
'respect_handler_level' keyword argument which, if set to ‘True’, will
pass messages to handlers taking handler levels into account.
(Contributed by Vinay Sajip.)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=20537

   (2) https://bugs.python.org/issue?@action=redirect&bpo=22788


File: python.info,  Node: lzma,  Next: math<8>,  Prev: logging<5>,  Up: 改進的模組<8>

1.9.5.39 lzma
.............

The *note LZMADecompressor.decompress(): dd4. method now accepts an
optional 'max_length' argument to limit the maximum size of decompressed
data.  (Contributed by Martin Panter in bpo-15955(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=15955


File: python.info,  Node: math<8>,  Next: multiprocessing<6>,  Prev: lzma,  Up: 改進的模組<8>

1.9.5.40 math
.............

Two new constants have been added to the *note math: 81. module: *note
inf: c2b. and *note nan: 609.  (Contributed by Mark Dickinson in
bpo-23185(1).)

A new function *note isclose(): d56. provides a way to test for
approximate equality.  (Contributed by Chris Barker and Tal Einat in
bpo-24270(2).)

A new *note gcd(): 8b5. function has been added.  The ‘fractions.gcd()’
function is now deprecated.  (Contributed by Mark Dickinson and Serhiy
Storchaka in bpo-22486(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23185

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24270

   (3) https://bugs.python.org/issue?@action=redirect&bpo=22486


File: python.info,  Node: multiprocessing<6>,  Next: operator<2>,  Prev: math<8>,  Up: 改進的模組<8>

1.9.5.41 multiprocessing
........................

*note sharedctypes.synchronized(): dd7. objects now support the *note
context manager: 576. protocol.  (Contributed by Charles-François Natali
in bpo-21565(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21565


File: python.info,  Node: operator<2>,  Next: os<10>,  Prev: multiprocessing<6>,  Up: 改進的模組<8>

1.9.5.42 operator
.................

*note attrgetter(): dd9, *note itemgetter(): a05, and *note
methodcaller(): dda. objects now support pickling.  (Contributed by Josh
Rosenberg and Serhiy Storchaka in bpo-22955(1).)

New *note matmul(): ddb. and *note imatmul(): ddc. functions to perform
matrix multiplication.  (Contributed by Benjamin Peterson in
bpo-21176(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22955

   (2) https://bugs.python.org/issue?@action=redirect&bpo=21176


File: python.info,  Node: os<10>,  Next: pathlib<10>,  Prev: operator<2>,  Up: 改進的模組<8>

1.9.5.43 os
...........

The new *note scandir(): a02. function returning an iterator of *note
DirEntry: 443. objects has been added.  If possible, *note scandir():
a02. extracts file attributes while scanning a directory, removing the
need to perform subsequent system calls to determine file type or
attributes, which may significantly improve performance.  (Contributed
by Ben Hoyt with the help of Victor Stinner in bpo-22524(1).)

On Windows, a new *note stat_result.st_file_attributes: dde. attribute
is now available.  It corresponds to the ‘dwFileAttributes’ member of
the ‘BY_HANDLE_FILE_INFORMATION’ structure returned by
‘GetFileInformationByHandle()’.  (Contributed by Ben Hoyt in
bpo-21719(2).)

The *note urandom(): 4c7. function now uses the ‘getrandom()’ syscall on
Linux 3.17 or newer, and ‘getentropy()’ on OpenBSD 5.6 and newer,
removing the need to use ‘/dev/urandom’ and avoiding failures due to
potential file descriptor exhaustion.  (Contributed by Victor Stinner in
bpo-22181(3).)

New *note get_blocking(): ddf. and *note set_blocking(): de0. functions
allow getting and setting a file descriptor's blocking mode (*note
O_NONBLOCK: de1.)  (Contributed by Victor Stinner in bpo-22054(4).)

The *note truncate(): de2. and *note ftruncate(): d35. functions are now
supported on Windows.  (Contributed by Steve Dower in bpo-23668(5).)

There is a new *note os.path.commonpath(): de3. function returning the
longest common sub-path of each passed pathname.  Unlike the *note
os.path.commonprefix(): de4. function, it always returns a valid path:

     >>> os.path.commonprefix(['/usr/lib', '/usr/local/lib'])
     '/usr/l'

     >>> os.path.commonpath(['/usr/lib', '/usr/local/lib'])
     '/usr'

（由 Rafik Draoui 和 Serhiy Storchaka 在 bpo-10395(6) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22524

   (2) https://bugs.python.org/issue?@action=redirect&bpo=21719

   (3) https://bugs.python.org/issue?@action=redirect&bpo=22181

   (4) https://bugs.python.org/issue?@action=redirect&bpo=22054

   (5) https://bugs.python.org/issue?@action=redirect&bpo=23668

   (6) https://bugs.python.org/issue?@action=redirect&bpo=10395


File: python.info,  Node: pathlib<10>,  Next: pickle<3>,  Prev: os<10>,  Up: 改進的模組<8>

1.9.5.44 pathlib
................

The new *note Path.samefile(): de6. method can be used to check whether
the path points to the same file as another path, which can be either
another *note Path: 20e. object, or a string:

     >>> import pathlib
     >>> p1 = pathlib.Path('/etc/hosts')
     >>> p2 = pathlib.Path('/etc/../etc/hosts')
     >>> p1.samefile(p2)
     True

（由 Vajrasky Kok 和 Antoine Pitrou 在 bpo-19775(1) 中貢獻。）

The *note Path.mkdir(): de7. method now accepts a new optional
'exist_ok' argument to match ‘mkdir -p’ and *note os.makedirs(): 203.
functionality.  (Contributed by Berker Peksag in bpo-21539(2).)

There is a new *note Path.expanduser(): de8. method to expand ‘~’ and
‘~user’ prefixes.  (Contributed by Serhiy Storchaka and Claudiu Popa in
bpo-19776(3).)

A new *note Path.home(): de9. class method can be used to get a *note
Path: 20e. instance representing the user’s home directory.
(Contributed by Victor Salgado and Mayank Tripathi in bpo-19777(4).)

New *note Path.write_text(): dea, *note Path.read_text(): deb, *note
Path.write_bytes(): dec, *note Path.read_bytes(): ded. methods to
simplify read/write operations on files.

The following code snippet will create or rewrite existing file
‘~/spam42’:

     >>> import pathlib
     >>> p = pathlib.Path('~/spam42')
     >>> p.expanduser().write_text('ham')
     3

（由 Christopher Welborn 在 bpo-20218(5) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=19775

   (2) https://bugs.python.org/issue?@action=redirect&bpo=21539

   (3) https://bugs.python.org/issue?@action=redirect&bpo=19776

   (4) https://bugs.python.org/issue?@action=redirect&bpo=19777

   (5) https://bugs.python.org/issue?@action=redirect&bpo=20218


File: python.info,  Node: pickle<3>,  Next: poplib<2>,  Prev: pathlib<10>,  Up: 改進的模組<8>

1.9.5.45 pickle
...............

Nested objects, such as unbound methods or nested classes, can now be
pickled using *note pickle protocols: c68. older than protocol version
4.  Protocol version 4 already supports these cases.  (Contributed by
Serhiy Storchaka in bpo-23611(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23611


File: python.info,  Node: poplib<2>,  Next: re<7>,  Prev: pickle<3>,  Up: 改進的模組<8>

1.9.5.46 poplib
...............

A new *note POP3.utf8(): df0. command enables RFC 6856(1)
(Internationalized Email) support, if a POP server supports it.
(Contributed by Milan OberKirch in bpo-21804(2).)

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc6856.html

   (2) https://bugs.python.org/issue?@action=redirect&bpo=21804


File: python.info,  Node: re<7>,  Next: readline<2>,  Prev: poplib<2>,  Up: 改進的模組<8>

1.9.5.47 re
...........

References and conditional references to groups with fixed length are
now allowed in lookbehind assertions:

     >>> import re
     >>> pat = re.compile(r'(a|b).(?<=\1)c')
     >>> pat.match('aac')
     <_sre.SRE_Match object; span=(0, 3), match='aac'>
     >>> pat.match('bbc')
     <_sre.SRE_Match object; span=(0, 3), match='bbc'>

（由 Serhiy Storchaka 在 bpo-9179(1) 中貢獻。）

The number of capturing groups in regular expressions is no longer
limited to 100.  (Contributed by Serhiy Storchaka in bpo-22437(2).)

The *note sub(): 283. and *note subn(): 284. functions now replace
unmatched groups with empty strings instead of raising an exception.
(Contributed by Serhiy Storchaka in bpo-1519638(3).)

The ‘re.error’ exceptions have new attributes, ‘msg’, ‘pattern’, ‘pos’,
‘lineno’, and ‘colno’, that provide better context information about the
error:

     >>> re.compile("""
     ...     (?x)
     ...     .++
     ... """)
     Traceback (most recent call last):
        ...
     sre_constants.error: multiple repeat at position 16 (line 3, column 7)

（由 Serhiy Storchaka 在 bpo-22578(4) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=9179

   (2) https://bugs.python.org/issue?@action=redirect&bpo=22437

   (3) https://bugs.python.org/issue?@action=redirect&bpo=1519638

   (4) https://bugs.python.org/issue?@action=redirect&bpo=22578


File: python.info,  Node: readline<2>,  Next: selectors,  Prev: re<7>,  Up: 改進的模組<8>

1.9.5.48 readline
.................

A new *note append_history_file(): df3. function can be used to append
the specified number of trailing elements in history to the given file.
(Contributed by Bruno Cauet in bpo-22940(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22940


File: python.info,  Node: selectors,  Next: shutil<5>,  Prev: readline<2>,  Up: 改進的模組<8>

1.9.5.49 selectors
..................

The new *note DevpollSelector: b7e. supports efficient ‘/dev/poll’
polling on Solaris.  (Contributed by Giampaolo Rodola' in bpo-18931(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=18931


File: python.info,  Node: shutil<5>,  Next: signal<3>,  Prev: selectors,  Up: 改進的模組<8>

1.9.5.50 shutil
...............

The *note move(): 9ff. function now accepts a 'copy_function' argument,
allowing, for example, the *note copy(): 9fd. function to be used
instead of the default *note copy2(): 9fe. if there is a need to ignore
file metadata when moving.  (Contributed by Claudiu Popa in
bpo-19840(1).)

The *note make_archive(): 45a. function now supports the 'xztar' format.
(Contributed by Serhiy Storchaka in bpo-5411(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=19840

   (2) https://bugs.python.org/issue?@action=redirect&bpo=5411


File: python.info,  Node: signal<3>,  Next: smtpd<2>,  Prev: shutil<5>,  Up: 改進的模組<8>

1.9.5.51 signal
...............

On Windows, the *note set_wakeup_fd(): b14. function now also supports
socket handles.  (Contributed by Victor Stinner in bpo-22018(1).)

Various ‘SIG*’ constants in the *note signal: b4. module have been
converted into *note Enums: 4c.  This allows meaningful names to be
printed during debugging, instead of integer "magic numbers".
(Contributed by Giampaolo Rodola' in bpo-21076(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22018

   (2) https://bugs.python.org/issue?@action=redirect&bpo=21076


File: python.info,  Node: smtpd<2>,  Next: smtplib<2>,  Prev: signal<3>,  Up: 改進的模組<8>

1.9.5.52 smtpd
..............

Both the ‘SMTPServer’ and ‘SMTPChannel’ classes now accept a
'decode_data' keyword argument to determine if the ‘DATA’ portion of the
SMTP transaction is decoded using the ‘"utf-8"’ codec or is instead
provided to the ‘SMTPServer.process_message()’ method as a byte string.
The default is ‘True’ for backward compatibility reasons, but will
change to ‘False’ in Python 3.6.  If 'decode_data' is set to ‘False’,
the ‘process_message’ method must be prepared to accept keyword
arguments.  (Contributed by Maciej Szulik in bpo-19662(1).)

The ‘SMTPServer’ class now advertises the ‘8BITMIME’ extension ( RFC
6152(2)) if 'decode_data' has been set ‘True’.  If the client specifies
‘BODY=8BITMIME’ on the ‘MAIL’ command, it is passed to
‘SMTPServer.process_message()’ via the 'mail_options' keyword.
(Contributed by Milan Oberkirch and R. David Murray in bpo-21795(3).)

The ‘SMTPServer’ class now also supports the ‘SMTPUTF8’ extension ( RFC
6531(4): Internationalized Email).  If the client specified ‘SMTPUTF8
BODY=8BITMIME’ on the ‘MAIL’ command, they are passed to
‘SMTPServer.process_message()’ via the 'mail_options' keyword.  It is
the responsibility of the ‘process_message’ method to correctly handle
the ‘SMTPUTF8’ data.  (Contributed by Milan Oberkirch in bpo-21725(5).)

It is now possible to provide, directly or via name resolution, IPv6
addresses in the ‘SMTPServer’ constructor, and have it successfully
connect.  (Contributed by Milan Oberkirch in bpo-14758(6).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=19662

   (2) https://datatracker.ietf.org/doc/html/rfc6152.html

   (3) https://bugs.python.org/issue?@action=redirect&bpo=21795

   (4) https://datatracker.ietf.org/doc/html/rfc6531.html

   (5) https://bugs.python.org/issue?@action=redirect&bpo=21725

   (6) https://bugs.python.org/issue?@action=redirect&bpo=14758


File: python.info,  Node: smtplib<2>,  Next: sndhdr,  Prev: smtpd<2>,  Up: 改進的模組<8>

1.9.5.53 smtplib
................

A new *note SMTP.auth(): df9. method provides a convenient way to
implement custom authentication mechanisms.  (Contributed by Milan
Oberkirch in bpo-15014(1).)

The *note SMTP.set_debuglevel(): dfa. method now accepts an additional
debuglevel (2), which enables timestamps in debug messages.
(Contributed by Gavin Chappell and Maciej Szulik in bpo-16914(2).)

Both the *note SMTP.sendmail(): dfb. and *note SMTP.send_message(): dfc.
methods now support RFC 6531(3) (SMTPUTF8).  (Contributed by Milan
Oberkirch and R. David Murray in bpo-22027(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=15014

   (2) https://bugs.python.org/issue?@action=redirect&bpo=16914

   (3) https://datatracker.ietf.org/doc/html/rfc6531.html

   (4) https://bugs.python.org/issue?@action=redirect&bpo=22027


File: python.info,  Node: sndhdr,  Next: socket<8>,  Prev: smtplib<2>,  Up: 改進的模組<8>

1.9.5.54 sndhdr
...............

The ‘what()’ and ‘whathdr()’ functions now return a *note namedtuple():
1ae.  (Contributed by Claudiu Popa in bpo-18615(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=18615


File: python.info,  Node: socket<8>,  Next: ssl<9>,  Prev: sndhdr,  Up: 改進的模組<8>

1.9.5.55 socket
...............

Functions with timeouts now use a monotonic clock, instead of a system
clock.  (Contributed by Victor Stinner in bpo-22043(1).)

A new *note socket.sendfile(): dff. method allows sending a file over a
socket by using the high-performance *note os.sendfile(): ab2. function
on UNIX, resulting in uploads being from 2 to 3 times faster than when
using plain *note socket.send(): d4d.  (Contributed by Giampaolo Rodola'
in bpo-17552(2).)

The *note socket.sendall(): d4e. method no longer resets the socket
timeout every time bytes are received or sent.  The socket timeout is
now the maximum total duration to send all data.  (Contributed by Victor
Stinner in bpo-23853(3).)

The 'backlog' argument of the *note socket.listen(): e00. method is now
optional.  By default it is set to *note SOMAXCONN: e01. or to ‘128’,
whichever is less.  (Contributed by Charles-François Natali in
bpo-21455(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22043

   (2) https://bugs.python.org/issue?@action=redirect&bpo=17552

   (3) https://bugs.python.org/issue?@action=redirect&bpo=23853

   (4) https://bugs.python.org/issue?@action=redirect&bpo=21455


File: python.info,  Node: ssl<9>,  Next: sqlite3<8>,  Prev: socket<8>,  Up: 改進的模組<8>

1.9.5.56 ssl
............

* Menu:

* Memory BIO Support::
* Application-Layer Protocol Negotiation Support::
* Other Changes::


File: python.info,  Node: Memory BIO Support,  Next: Application-Layer Protocol Negotiation Support,  Up: ssl<9>

1.9.5.57 Memory BIO Support
...........................

（由 Geert Jansen 在 bpo-21965(1) 中貢獻。）

The new *note SSLObject: b25. class has been added to provide SSL
protocol support for cases when the network I/O capabilities of *note
SSLSocket: 88f. are not necessary or are suboptimal.  ‘SSLObject’
represents an SSL protocol instance, but does not implement any network
I/O methods, and instead provides a memory buffer interface.  The new
*note MemoryBIO: e04. class can be used to pass data between Python and
an SSL protocol instance.

The memory BIO SSL support is primarily intended to be used in
frameworks implementing asynchronous I/O for which *note SSLSocket:
88f.'s readiness model ("select/poll") is inefficient.

A new *note SSLContext.wrap_bio(): b26. method can be used to create a
new ‘SSLObject’ instance.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21965


File: python.info,  Node: Application-Layer Protocol Negotiation Support,  Next: Other Changes,  Prev: Memory BIO Support,  Up: ssl<9>

1.9.5.58 Application-Layer Protocol Negotiation Support
.......................................................

（由 Benjamin Peterson 在 bpo-20188(1) 中貢獻。）

Where OpenSSL support is present, the *note ssl: bb. module now
implements the 'Application-Layer Protocol Negotiation' TLS extension as
described in RFC 7301(2).

The new *note SSLContext.set_alpn_protocols(): e06. can be used to
specify which protocols a socket should advertise during the TLS
handshake.

The new *note SSLSocket.selected_alpn_protocol(): e07. returns the
protocol that was selected during the TLS handshake.  The *note
HAS_ALPN: e08. flag indicates whether ALPN support is present.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=20188

   (2) https://datatracker.ietf.org/doc/html/rfc7301.html


File: python.info,  Node: Other Changes,  Prev: Application-Layer Protocol Negotiation Support,  Up: ssl<9>

1.9.5.59 Other Changes
......................

There is a new *note SSLSocket.version(): e0a. method to query the
actual protocol version in use.  (Contributed by Antoine Pitrou in
bpo-20421(1).)

The *note SSLSocket: 88f. class now implements a ‘SSLSocket.sendfile()’
method.  (Contributed by Giampaolo Rodola' in bpo-17552(2).)

The ‘SSLSocket.send()’ method now raises either the *note
ssl.SSLWantReadError: e0b. or *note ssl.SSLWantWriteError: e0c.
exception on a non-blocking socket if the operation would block.
Previously, it would return ‘0’.  (Contributed by Nikolaus Rath in
bpo-20951(3).)

The *note cert_time_to_seconds(): e0d. function now interprets the input
time as UTC and not as local time, per RFC 5280(4).  Additionally, the
return value is always an *note int: 23c.  (Contributed by Akira Li in
bpo-19940(5).)

New ‘SSLObject.shared_ciphers()’ and *note SSLSocket.shared_ciphers():
e0e. methods return the list of ciphers sent by the client during the
handshake.  (Contributed by Benjamin Peterson in bpo-23186(6).)

The *note SSLSocket.do_handshake(): e0f, *note SSLSocket.read(): e10,
‘SSLSocket.shutdown()’, and *note SSLSocket.write(): e11. methods of the
*note SSLSocket: 88f. class no longer reset the socket timeout every
time bytes are received or sent.  The socket timeout is now the maximum
total duration of the method.  (Contributed by Victor Stinner in
bpo-23853(7).)

The ‘match_hostname()’ function now supports matching of IP addresses.
(Contributed by Antoine Pitrou in bpo-23239(8).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=20421

   (2) https://bugs.python.org/issue?@action=redirect&bpo=17552

   (3) https://bugs.python.org/issue?@action=redirect&bpo=20951

   (4) https://datatracker.ietf.org/doc/html/rfc5280.html

   (5) https://bugs.python.org/issue?@action=redirect&bpo=19940

   (6) https://bugs.python.org/issue?@action=redirect&bpo=23186

   (7) https://bugs.python.org/issue?@action=redirect&bpo=23853

   (8) https://bugs.python.org/issue?@action=redirect&bpo=23239


File: python.info,  Node: sqlite3<8>,  Next: subprocess<4>,  Prev: ssl<9>,  Up: 改進的模組<8>

1.9.5.60 sqlite3
................

The *note Row: e13. class now fully supports the sequence protocol, in
particular *note reversed(): 80a. iteration and slice indexing.
(Contributed by Claudiu Popa in bpo-10203(1); by Lucas Sinclair, Jessica
McKellar, and Serhiy Storchaka in bpo-13583(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=10203

   (2) https://bugs.python.org/issue?@action=redirect&bpo=13583


File: python.info,  Node: subprocess<4>,  Next: sys<10>,  Prev: sqlite3<8>,  Up: 改進的模組<8>

1.9.5.61 subprocess
...................

The new *note run(): b2c. function has been added.  It runs the
specified command and returns a *note CompletedProcess: e15. object,
which describes a finished process.  The new API is more consistent and
is the recommended approach to invoking subprocesses in Python code that
does not need to maintain compatibility with earlier Python versions.
(Contributed by Thomas Kluyver in bpo-23342(1).)

範例：

     >>> subprocess.run(["ls", "-l"])  # 沒有捕捉到輸出
     CompletedProcess(args=['ls', '-l'], returncode=0)

     >>> subprocess.run("exit 1", shell=True, check=True)
     Traceback (most recent call last):
       ...
     subprocess.CalledProcessError: Command 'exit 1' returned non-zero exit status 1

     >>> subprocess.run(["ls", "-l", "/dev/null"], stdout=subprocess.PIPE)
     CompletedProcess(args=['ls', '-l', '/dev/null'], returncode=0,
     stdout=b'crw-rw-rw- 1 root root 1, 3 Jan 23 16:23 /dev/null\n')

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23342


File: python.info,  Node: sys<10>,  Next: sysconfig<2>,  Prev: subprocess<4>,  Up: 改進的模組<8>

1.9.5.62 sys
............

A new ‘set_coroutine_wrapper()’ function allows setting a global hook
that will be called whenever a *note coroutine object: 438. is created
by an *note async def: 575. function.  A corresponding
‘get_coroutine_wrapper()’ can be used to obtain a currently set wrapper.
Both functions are *note provisional: aa6, and are intended for
debugging purposes only.  (Contributed by Yury Selivanov in
bpo-24017(1).)

A new *note is_finalizing(): a32. function can be used to check if the
Python interpreter is *note shutting down: 133.  (Contributed by Antoine
Pitrou in bpo-22696(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24017

   (2) https://bugs.python.org/issue?@action=redirect&bpo=22696


File: python.info,  Node: sysconfig<2>,  Next: tarfile<6>,  Prev: sys<10>,  Up: 改進的模組<8>

1.9.5.63 sysconfig
..................

The name of the user scripts directory on Windows now includes the first
two components of the Python version.  (Contributed by Paul Moore in
bpo-23437(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23437


File: python.info,  Node: tarfile<6>,  Next: threading<6>,  Prev: sysconfig<2>,  Up: 改進的模組<8>

1.9.5.64 tarfile
................

The 'mode' argument of the *note open(): e19. function now accepts ‘"x"’
to request exclusive creation.  (Contributed by Berker Peksag in
bpo-21717(1).)

The *note TarFile.extractall(): e1a. and *note TarFile.extract(): e1b.
methods now take a keyword argument 'numeric_owner'.  If set to ‘True’,
the extracted files and directories will be owned by the numeric ‘uid’
and ‘gid’ from the tarfile.  If set to ‘False’ (the default, and the
behavior in versions prior to 3.5), they will be owned by the named user
and group in the tarfile.  (Contributed by Michael Vogt and Eric Smith
in bpo-23193(2).)

The *note TarFile.list(): e1c. now accepts an optional 'members' keyword
argument that can be set to a subset of the list returned by *note
TarFile.getmembers(): e1d.  (Contributed by Serhiy Storchaka in
bpo-21549(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21717

   (2) https://bugs.python.org/issue?@action=redirect&bpo=23193

   (3) https://bugs.python.org/issue?@action=redirect&bpo=21549


File: python.info,  Node: threading<6>,  Next: time<7>,  Prev: tarfile<6>,  Up: 改進的模組<8>

1.9.5.65 threading
..................

Both the *note Lock.acquire(): 63e. and *note RLock.acquire(): e1f.
methods now use a monotonic clock for timeout management.  (Contributed
by Victor Stinner in bpo-22043(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22043


File: python.info,  Node: time<7>,  Next: timeit<2>,  Prev: threading<6>,  Up: 改進的模組<8>

1.9.5.66 time
.............

The *note monotonic(): 238. function is now always available.
(Contributed by Victor Stinner in bpo-22043(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22043


File: python.info,  Node: timeit<2>,  Next: tkinter<8>,  Prev: time<7>,  Up: 改進的模組<8>

1.9.5.67 timeit
...............

A new command line option ‘-u’ or ‘--unit=U’ can be used to specify the
time unit for the timer output.  Supported options are ‘usec’, ‘msec’,
or ‘sec’.  (Contributed by Julian Gindi in bpo-18983(1).)

The *note timeit(): e22. function has a new 'globals' parameter for
specifying the namespace in which the code will be running.
(Contributed by Ben Roberts in bpo-2527(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=18983

   (2) https://bugs.python.org/issue?@action=redirect&bpo=2527


File: python.info,  Node: tkinter<8>,  Next: traceback<5>,  Prev: timeit<2>,  Up: 改進的模組<8>

1.9.5.68 tkinter
................

The ‘tkinter._fix’ module used for setting up the Tcl/Tk environment on
Windows has been replaced by a private function in the ‘_tkinter’ module
which makes no permanent changes to environment variables.  (Contributed
by Zachary Ware in bpo-20035(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=20035


File: python.info,  Node: traceback<5>,  Next: types<5>,  Prev: tkinter<8>,  Up: 改進的模組<8>

1.9.5.69 traceback
..................

New *note walk_stack(): e25. and *note walk_tb(): e26. functions to
conveniently traverse frame and *note traceback objects: a97.
(Contributed by Robert Collins in bpo-17911(1).)

New lightweight classes: *note TracebackException: 241, *note
StackSummary: e27, and *note FrameSummary: e28.  (Contributed by Robert
Collins in bpo-17911(2).)

Both the *note print_tb(): e29. and *note print_stack(): e2a. functions
now support negative values for the 'limit' argument.  (Contributed by
Dmitry Kazakov in bpo-22619(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=17911

   (2) https://bugs.python.org/issue?@action=redirect&bpo=17911

   (3) https://bugs.python.org/issue?@action=redirect&bpo=22619


File: python.info,  Node: types<5>,  Next: unicodedata<8>,  Prev: traceback<5>,  Up: 改進的模組<8>

1.9.5.70 types
..............

A new *note coroutine(): e2c. function to transform *note generator:
b85. and *note generator-like: d81. objects into *note awaitables: 193.
(Contributed by Yury Selivanov in bpo-24017(1).)

A new type called *note CoroutineType: e2d, which is used for *note
coroutine: 438. objects created by *note async def: 575. functions.
(Contributed by Yury Selivanov in bpo-24400(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24017

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24400


File: python.info,  Node: unicodedata<8>,  Next: unittest<8>,  Prev: types<5>,  Up: 改進的模組<8>

1.9.5.71 unicodedata
....................

The *note unicodedata: ee. module now uses data from Unicode 8.0.0(1).

   ---------- Footnotes ----------

   (1) https://unicode.org/versions/Unicode8.0.0/


File: python.info,  Node: unittest<8>,  Next: unittest mock<3>,  Prev: unicodedata<8>,  Up: 改進的模組<8>

1.9.5.72 unittest
.................

The *note TestLoader.loadTestsFromModule(): 271. method now accepts a
keyword-only argument 'pattern' which is passed to ‘load_tests’ as the
third argument.  Found packages are now checked for ‘load_tests’
regardless of whether their path matches 'pattern', because it is
impossible for a package name to match the default pattern.
(Contributed by Robert Collins and Barry A. Warsaw in bpo-16662(1).)

Unittest discovery errors now are exposed in the *note
TestLoader.errors: e30. attribute of the *note TestLoader: 270.
instance.  (Contributed by Robert Collins in bpo-19746(2).)

A new command line option ‘--locals’ to show local variables in
tracebacks.  (Contributed by Robert Collins in bpo-22936(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16662

   (2) https://bugs.python.org/issue?@action=redirect&bpo=19746

   (3) https://bugs.python.org/issue?@action=redirect&bpo=22936


File: python.info,  Node: unittest mock<3>,  Next: urllib<2>,  Prev: unittest<8>,  Up: 改進的模組<8>

1.9.5.73 unittest.mock
......................

The *note Mock: 9ef. class has the following improvements:

   * The class constructor has a new 'unsafe' parameter, which causes
     mock objects to raise *note AttributeError: 2f6. on attribute names
     starting with ‘"assert"’.  (Contributed by Kushal Das in
     bpo-21238(1).)

   * A new *note Mock.assert_not_called(): e32. method to check if the
     mock object was called.  (Contributed by Kushal Das in
     bpo-21262(2).)

The *note MagicMock: e33. class now supports ‘__truediv__()’,
‘__divmod__()’ and ‘__matmul__()’ operators.  (Contributed by Johannes
Baiter in bpo-20968(3), and Håkan Lövdahl in bpo-23581(4) and
bpo-23568(5).)

It is no longer necessary to explicitly pass ‘create=True’ to the *note
patch(): e34. function when patching builtin names.  (Contributed by
Kushal Das in bpo-17660(6).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21238

   (2) https://bugs.python.org/issue?@action=redirect&bpo=21262

   (3) https://bugs.python.org/issue?@action=redirect&bpo=20968

   (4) https://bugs.python.org/issue?@action=redirect&bpo=23581

   (5) https://bugs.python.org/issue?@action=redirect&bpo=23568

   (6) https://bugs.python.org/issue?@action=redirect&bpo=17660


File: python.info,  Node: urllib<2>,  Next: wsgiref,  Prev: unittest mock<3>,  Up: 改進的模組<8>

1.9.5.74 urllib
...............

A new *note request.HTTPPasswordMgrWithPriorAuth: e36. class allows HTTP
Basic Authentication credentials to be managed so as to eliminate
unnecessary ‘401’ response handling, or to unconditionally send
credentials on the first request in order to communicate with servers
that return a ‘404’ response instead of a ‘401’ if the ‘Authorization’
header is not sent.  (Contributed by Matej Cepl in bpo-19494(1) and
Akshit Khurana in bpo-7159(2).)

A new 'quote_via' argument for the *note parse.urlencode(): e37.
function provides a way to control the encoding of query parts if
needed.  (Contributed by Samwyse and Arnon Yaari in bpo-13866(3).)

The *note request.urlopen(): 275. function accepts an *note
ssl.SSLContext: 276. object as a 'context' argument, which will be used
for the HTTPS connection.  (Contributed by Alex Gaynor in bpo-22366(4).)

The *note parse.urljoin(): e38. was updated to use the RFC 3986(5)
semantics for the resolution of relative URLs, rather than RFC 1808(6)
and RFC 2396(7).  (Contributed by Demian Brecht and Senthil Kumaran in
bpo-22118(8).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=19494

   (2) https://bugs.python.org/issue?@action=redirect&bpo=7159

   (3) https://bugs.python.org/issue?@action=redirect&bpo=13866

   (4) https://bugs.python.org/issue?@action=redirect&bpo=22366

   (5) https://datatracker.ietf.org/doc/html/rfc3986.html

   (6) https://datatracker.ietf.org/doc/html/rfc1808.html

   (7) https://datatracker.ietf.org/doc/html/rfc2396.html

   (8) https://bugs.python.org/issue?@action=redirect&bpo=22118


File: python.info,  Node: wsgiref,  Next: xmlrpc<2>,  Prev: urllib<2>,  Up: 改進的模組<8>

1.9.5.75 wsgiref
................

The 'headers' argument of the *note headers.Headers: e3a. class
constructor is now optional.  (Contributed by Pablo Torres Navarrete and
SilentGhost in bpo-5800(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=5800


File: python.info,  Node: xmlrpc<2>,  Next: xml sax,  Prev: wsgiref,  Up: 改進的模組<8>

1.9.5.76 xmlrpc
...............

The *note client.ServerProxy: 9fa. class now supports the *note context
manager: 576. protocol.  (Contributed by Claudiu Popa in bpo-20627(1).)

The *note client.ServerProxy: 9fa. constructor now accepts an optional
*note ssl.SSLContext: 276. instance.  (Contributed by Alex Gaynor in
bpo-22960(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=20627

   (2) https://bugs.python.org/issue?@action=redirect&bpo=22960


File: python.info,  Node: xml sax,  Next: zipfile<4>,  Prev: xmlrpc<2>,  Up: 改進的模組<8>

1.9.5.77 xml.sax
................

SAX parsers now support a character stream of the *note
xmlreader.InputSource: e3d. object.  (Contributed by Serhiy Storchaka in
bpo-2175(1).)

*note parseString(): e3e. now accepts a *note str: 3f2. instance.
(Contributed by Serhiy Storchaka in bpo-10590(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=2175

   (2) https://bugs.python.org/issue?@action=redirect&bpo=10590


File: python.info,  Node: zipfile<4>,  Prev: xml sax,  Up: 改進的模組<8>

1.9.5.78 zipfile
................

ZIP output can now be written to unseekable streams.  (Contributed by
Serhiy Storchaka in bpo-23252(1).)

The 'mode' argument of *note ZipFile.open(): 355. method now accepts
‘"x"’ to request exclusive creation.  (Contributed by Serhiy Storchaka
in bpo-21717(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23252

   (2) https://bugs.python.org/issue?@action=redirect&bpo=21717


File: python.info,  Node: Other module-level changes,  Next: 最佳化<8>,  Prev: 改進的模組<8>,  Up: Python 3 4 有什麼新功能

1.9.6 Other module-level changes
--------------------------------

Many functions in the *note mmap: 83, ‘ossaudiodev’, *note socket: b8,
*note ssl: bb, and *note codecs: 14. modules now accept writable *note
bytes-like objects: cd4.  (Contributed by Serhiy Storchaka in
bpo-23001(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23001


File: python.info,  Node: 最佳化<8>,  Next: Build and C API Changes<3>,  Prev: Other module-level changes,  Up: Python 3 4 有什麼新功能

1.9.7 最佳化
------------

The *note os.walk(): 451. function has been sped up by 3 to 5 times on
POSIX systems, and by 7 to 20 times on Windows.  This was done using the
new *note os.scandir(): a02. function, which exposes file information
from the underlying ‘readdir’ or ‘FindFirstFile’/‘FindNextFile’ system
calls.  (Contributed by Ben Hoyt with help from Victor Stinner in
bpo-23605(1).)

Construction of ‘bytes(int)’ (filled by zero bytes) is faster and uses
less memory for large objects.  ‘calloc()’ is used instead of ‘malloc()’
to allocate memory for these objects.  (Contributed by Victor Stinner in
bpo-21233(2).)

Some operations on *note ipaddress: 74. *note IPv4Network: 1e3. and
*note IPv6Network: 1e4. have been massively sped up, such as *note
subnets(): e42, *note supernet(): e43, *note summarize_address_range():
e44, *note collapse_addresses(): e45.  The speed up can range from 3 to
15 times.  (Contributed by Antoine Pitrou, Michel Albert, and Markus in
bpo-21486(3), bpo-21487(4), bpo-20826(5), bpo-23266(6).)

Pickling of *note ipaddress: 74. objects was optimized to produce
significantly smaller output.  (Contributed by Serhiy Storchaka in
bpo-23133(7).)

Many operations on *note io.BytesIO: e46. are now 50% to 100% faster.
(Contributed by Serhiy Storchaka in bpo-15381(8) and David Wilson in
bpo-22003(9).)

The *note marshal.dumps(): e47. function is now faster: 65-85% with
versions 3 and 4, 20-25% with versions 0 to 2 on typical data, and up to
5 times in best cases.  (Contributed by Serhiy Storchaka in
bpo-20416(10) and bpo-23344(11).)

The UTF-32 encoder is now 3 to 7 times faster.  (Contributed by Serhiy
Storchaka in bpo-15027(12).)

Regular expressions are now parsed up to 10% faster.  (Contributed by
Serhiy Storchaka in bpo-19380(13).)

The *note json.dumps(): cec. function was optimized to run with
‘ensure_ascii=False’ as fast as with ‘ensure_ascii=True’.  (Contributed
by Naoki Inada in bpo-23206(14).)

The *note PyObject_IsInstance(): e48. and *note PyObject_IsSubclass():
e49. functions have been sped up in the common case that the second
argument has *note type: cef. as its metaclass.  (Contributed Georg
Brandl by in bpo-22540(15).)

Method caching was slightly improved, yielding up to 5% performance
improvement in some benchmarks.  (Contributed by Antoine Pitrou in
bpo-22847(16).)

Objects from the *note random: a6. module now use 50% less memory on
64-bit builds.  (Contributed by Serhiy Storchaka in bpo-23488(17).)

The *note property(): 180. getter calls are up to 25% faster.
(Contributed by Joe Jevnik in bpo-23910(18).)

Instantiation of *note fractions.Fraction: 1c7. is now up to 30% faster.
(Contributed by Stefan Behnel in bpo-22464(19).)

String methods *note find(): e4a, *note rfind(): e4b, *note split():
e4c, *note partition(): e4d. and the *note in: 2c5. string operator are
now significantly faster for searching 1-character substrings.
(Contributed by Serhiy Storchaka in bpo-23573(20).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23605

   (2) https://bugs.python.org/issue?@action=redirect&bpo=21233

   (3) https://bugs.python.org/issue?@action=redirect&bpo=21486

   (4) https://bugs.python.org/issue?@action=redirect&bpo=21487

   (5) https://bugs.python.org/issue?@action=redirect&bpo=20826

   (6) https://bugs.python.org/issue?@action=redirect&bpo=23266

   (7) https://bugs.python.org/issue?@action=redirect&bpo=23133

   (8) https://bugs.python.org/issue?@action=redirect&bpo=15381

   (9) https://bugs.python.org/issue?@action=redirect&bpo=22003

   (10) https://bugs.python.org/issue?@action=redirect&bpo=20416

   (11) https://bugs.python.org/issue?@action=redirect&bpo=23344

   (12) https://bugs.python.org/issue?@action=redirect&bpo=15027

   (13) https://bugs.python.org/issue?@action=redirect&bpo=19380

   (14) https://bugs.python.org/issue?@action=redirect&bpo=23206

   (15) https://bugs.python.org/issue?@action=redirect&bpo=22540

   (16) https://bugs.python.org/issue?@action=redirect&bpo=22847

   (17) https://bugs.python.org/issue?@action=redirect&bpo=23488

   (18) https://bugs.python.org/issue?@action=redirect&bpo=23910

   (19) https://bugs.python.org/issue?@action=redirect&bpo=22464

   (20) https://bugs.python.org/issue?@action=redirect&bpo=23573


File: python.info,  Node: Build and C API Changes<3>,  Next: 已棄用<10>,  Prev: 最佳化<8>,  Up: Python 3 4 有什麼新功能

1.9.8 Build and C API Changes
-----------------------------

New ‘calloc’ functions were added:

   * *note PyMem_RawCalloc(): 324,

   * *note PyMem_Calloc(): e4f,

   * *note PyObject_Calloc(): e50.

（由 Victor Stinner 在 bpo-21233(1) 中貢獻。）

New encoding/decoding helper functions:

   * *note Py_DecodeLocale(): b6e. (replaced ‘_Py_char2wchar()’),

   * *note Py_EncodeLocale(): b6f. (replaced ‘_Py_wchar2char()’).

（由 Victor Stinner 在 bpo-18395(2) 中貢獻。）

A new *note PyCodec_NameReplaceErrors(): e51. function to replace the
unicode encode error with ‘\N{...}’ escapes.  (Contributed by Serhiy
Storchaka in bpo-19676(3).)

A new *note PyErr_FormatV(): e52. function similar to *note
PyErr_Format(): e53, but accepts a ‘va_list’ argument.  (Contributed by
Antoine Pitrou in bpo-18711(4).)

A new ‘PyExc_RecursionError’ exception.  (Contributed by Georg Brandl in
bpo-19235(5).)

New *note PyModule_FromDefAndSpec(): e54, *note
PyModule_FromDefAndSpec2(): e55, and *note PyModule_ExecDef(): e56.
functions introduced by PEP 489(6) - multi-phase extension module
initialization.  (Contributed by Petr Viktorin in bpo-24268(7).)

New *note PyNumber_MatrixMultiply(): e57. and *note
PyNumber_InPlaceMatrixMultiply(): e58. functions to perform matrix
multiplication.  (Contributed by Benjamin Peterson in bpo-21176(8).  See
also PEP 465(9) for details.)

The *note PyTypeObject.tp_finalize: a49. slot is now part of the stable
ABI.

Windows builds now require Microsoft Visual C++ 14.0, which is available
as part of Visual Studio 2015(10).

Extension modules now include a platform information tag in their
filename on some platforms (the tag is optional, and CPython will import
extensions without it, although if the tag is present and mismatched,
the extension won't be loaded):

   * On Linux, extension module filenames end with
     ‘.cpython-<major><minor>m-<architecture>-<os>.pyd’:

        * ‘<major>’ is the major number of the Python version; for
          Python 3.5 this is ‘3’.

        * ‘<minor>’ is the minor number of the Python version; for
          Python 3.5 this is ‘5’.

        * ‘<architecture>’ is the hardware architecture the extension
          module was built to run on.  It's most commonly either ‘i386’
          for 32-bit Intel platforms or ‘x86_64’ for 64-bit Intel (and
          AMD) platforms.

        * ‘<os>’ is always ‘linux-gnu’, except for extensions built to
          talk to the 32-bit ABI on 64-bit platforms, in which case it
          is ‘linux-gnu32’ (and ‘<architecture>’ will be ‘x86_64’).

   * On Windows, extension module filenames end with
     ‘<debug>.cp<major><minor>-<platform>.pyd’:

        * ‘<major>’ is the major number of the Python version; for
          Python 3.5 this is ‘3’.

        * ‘<minor>’ is the minor number of the Python version; for
          Python 3.5 this is ‘5’.

        * ‘<platform>’ is the platform the extension module was built
          for, either ‘win32’ for Win32, ‘win_amd64’ for Win64,
          ‘win_ia64’ for Windows Itanium 64, and ‘win_arm’ for Windows
          on ARM.

        * If built in debug mode, ‘<debug>’ will be ‘_d’, otherwise it
          will be blank.

   * On OS X platforms, extension module filenames now end with
     ‘-darwin.so’.

   * On all other platforms, extension module filenames are the same as
     they were with Python 3.4.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21233

   (2) https://bugs.python.org/issue?@action=redirect&bpo=18395

   (3) https://bugs.python.org/issue?@action=redirect&bpo=19676

   (4) https://bugs.python.org/issue?@action=redirect&bpo=18711

   (5) https://bugs.python.org/issue?@action=redirect&bpo=19235

   (6) https://peps.python.org/pep-0489/

   (7) https://bugs.python.org/issue?@action=redirect&bpo=24268

   (8) https://bugs.python.org/issue?@action=redirect&bpo=21176

   (9) https://peps.python.org/pep-0465/

   (10) 
https://visualstudio.microsoft.com/en/vs/older-downloads/#visual-studio-2015-and-other-products


File: python.info,  Node: 已棄用<10>,  Next: 已移除<8>,  Prev: Build and C API Changes<3>,  Up: Python 3 4 有什麼新功能

1.9.9 已棄用
------------

* Menu:

* New Keywords::
* Deprecated Python Behavior: Deprecated Python Behavior<2>.
* Unsupported Operating Systems::
* Deprecated Python modules, functions and methods: Deprecated Python modules functions and methods<3>.


File: python.info,  Node: New Keywords,  Next: Deprecated Python Behavior<2>,  Up: 已棄用<10>

1.9.9.1 New Keywords
....................

‘async’ and ‘await’ are not recommended to be used as variable, class,
function or module names.  Introduced by PEP 492(1) in Python 3.5, they
will become proper keywords in Python 3.7.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0492/


File: python.info,  Node: Deprecated Python Behavior<2>,  Next: Unsupported Operating Systems,  Prev: New Keywords,  Up: 已棄用<10>

1.9.9.2 Deprecated Python Behavior
..................................

Raising the *note StopIteration: ba1. exception inside a generator will
now generate a silent *note PendingDeprecationWarning: 86d, which will
become a non-silent deprecation warning in Python 3.6 and will trigger a
*note RuntimeError: 179. in Python 3.7.  See *note PEP 479; Change
StopIteration handling inside generators: cc6. for details.


File: python.info,  Node: Unsupported Operating Systems,  Next: Deprecated Python modules functions and methods<3>,  Prev: Deprecated Python Behavior<2>,  Up: 已棄用<10>

1.9.9.3 Unsupported Operating Systems
.....................................

Windows XP is no longer supported by Microsoft, thus, per PEP 11(1),
CPython 3.5 is no longer officially supported on this OS.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0011/


File: python.info,  Node: Deprecated Python modules functions and methods<3>,  Prev: Unsupported Operating Systems,  Up: 已棄用<10>

1.9.9.4 Deprecated Python modules, functions and methods
........................................................

The ‘formatter’ module has now graduated to full deprecation and is
still slated for removal in Python 3.6.

The ‘asyncio.async()’ function is deprecated in favor of *note
ensure_future(): c1d.

The ‘smtpd’ module has in the past always decoded the DATA portion of
email messages using the ‘utf-8’ codec.  This can now be controlled by
the new 'decode_data' keyword to ‘SMTPServer’.  The default value is
‘True’, but this default is deprecated.  Specify the 'decode_data'
keyword with an appropriate value to avoid the deprecation warning.

Directly assigning values to the *note key: ba8, *note value: ba9. and
*note coded_value: baa. of *note http.cookies.Morsel: bab. objects is
deprecated.  Use the *note set(): bac. method instead.  In addition, the
undocumented 'LegalChars' parameter of *note set(): bac. is deprecated,
and is now ignored.

Passing a format string as keyword argument 'format_string' to the *note
format(): ba7. method of the *note string.Formatter: e5e. class has been
deprecated.  (Contributed by Serhiy Storchaka in bpo-23671(1).)

The ‘platform.dist()’ and ‘platform.linux_distribution()’ functions are
now deprecated.  Linux distributions use too many different ways of
describing themselves, so the functionality is left to a package.
(Contributed by Vajrasky Kok and Berker Peksag in bpo-1322(2).)

The previously undocumented ‘from_function’ and ‘from_builtin’ methods
of *note inspect.Signature: 1b3. are deprecated.  Use the new *note
Signature.from_callable(): 6de. method instead.  (Contributed by Yury
Selivanov in bpo-24248(3).)

The ‘inspect.getargspec()’ function is deprecated and scheduled to be
removed in Python 3.6.  (See bpo-20438(4) for details.)

The *note inspect: 72. *note getfullargspec(): 6dd, *note getcallargs():
e5f, and ‘formatargspec()’ functions are deprecated in favor of the
*note inspect.signature(): 6dc. API. (Contributed by Yury Selivanov in
bpo-20438(5).)

*note getargvalues(): e60. and *note formatargvalues(): e61. functions
were inadvertently marked as deprecated with the release of Python
3.5.0.

Use of *note re.LOCALE: b10. flag with str patterns or *note re.ASCII:
5d3. is now deprecated.  (Contributed by Serhiy Storchaka in
bpo-22407(6).)

Use of unrecognized special sequences consisting of ‘'\'’ and an ASCII
letter in regular expression patterns and replacement patterns now
raises a deprecation warning and will be forbidden in Python 3.6.
(Contributed by Serhiy Storchaka in bpo-23622(7).)

The undocumented and unofficial 'use_load_tests' default argument of the
*note unittest.TestLoader.loadTestsFromModule(): 271. method now is
deprecated and ignored.  (Contributed by Robert Collins and Barry A.
Warsaw in bpo-16662(8).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23671

   (2) https://bugs.python.org/issue?@action=redirect&bpo=1322

   (3) https://bugs.python.org/issue?@action=redirect&bpo=24248

   (4) https://bugs.python.org/issue?@action=redirect&bpo=20438

   (5) https://bugs.python.org/issue?@action=redirect&bpo=20438

   (6) https://bugs.python.org/issue?@action=redirect&bpo=22407

   (7) https://bugs.python.org/issue?@action=redirect&bpo=23622

   (8) https://bugs.python.org/issue?@action=redirect&bpo=16662


File: python.info,  Node: 已移除<8>,  Next: Porting to Python 3 5,  Prev: 已棄用<10>,  Up: Python 3 4 有什麼新功能

1.9.10 已移除
-------------

* Menu:

* API and Feature Removals: API and Feature Removals<4>.


File: python.info,  Node: API and Feature Removals<4>,  Up: 已移除<8>

1.9.10.1 API and Feature Removals
.................................

The following obsolete and previously deprecated APIs and features have
been removed:

   * The ‘__version__’ attribute has been dropped from the email
     package.  The email code hasn't been shipped separately from the
     stdlib for a long time, and the ‘__version__’ string was not
     updated in the last few releases.

   * The internal ‘Netrc’ class in the *note ftplib: 54. module was
     deprecated in 3.4, and has now been removed.  (Contributed by Matt
     Chaput in bpo-6623(1).)

   * The concept of ‘.pyo’ files has been removed.

   * The JoinableQueue class in the provisional *note asyncio: 8. module
     was deprecated in 3.4.4 and is now removed.  (Contributed by A.
     Jesse Jiryu Davis in bpo-23464(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=6623

   (2) https://bugs.python.org/issue?@action=redirect&bpo=23464


File: python.info,  Node: Porting to Python 3 5,  Next: Python 3 5 4 中顯著的變更,  Prev: 已移除<8>,  Up: Python 3 4 有什麼新功能

1.9.11 Porting to Python 3.5
----------------------------

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

* Menu:

* Changes in Python behavior: Changes in Python behavior<2>.
* Changes in the Python API: Changes in the Python API<7>.
* C API 中的改動: C API 中的改動<6>.


File: python.info,  Node: Changes in Python behavior<2>,  Next: Changes in the Python API<7>,  Up: Porting to Python 3 5

1.9.11.1 Changes in Python behavior
...................................

   * Due to an oversight, earlier Python versions erroneously accepted
     the following syntax:

          f(1 for x in [1], *args)
          f(1 for x in [1], **kwargs)

     Python 3.5 now correctly raises a *note SyntaxError: 173, as
     generator expressions must be put in parentheses if not a sole
     argument to a function.


File: python.info,  Node: Changes in the Python API<7>,  Next: C API 中的改動<6>,  Prev: Changes in Python behavior<2>,  Up: Porting to Python 3 5

1.9.11.2 Changes in the Python API
..................................

   * PEP 475(1): System calls are now retried when interrupted by a
     signal instead of raising *note InterruptedError: d2e. if the
     Python signal handler does not raise an exception.

   * Before Python 3.5, a *note datetime.time: 1b2. object was
     considered to be false if it represented midnight in UTC. This
     behavior was considered obscure and error-prone and has been
     removed in Python 3.5.  See bpo-13936(2) for full details.

   * The ‘ssl.SSLSocket.send()’ method now raises either *note
     ssl.SSLWantReadError: e0b. or *note ssl.SSLWantWriteError: e0c. on
     a non-blocking socket if the operation would block.  Previously, it
     would return ‘0’.  (Contributed by Nikolaus Rath in bpo-20951(3).)

   * The ‘__name__’ attribute of generators is now set from the function
     name, instead of being set from the code name.  Use
     ‘gen.gi_code.co_name’ to retrieve the code name.  Generators also
     have a new ‘__qualname__’ attribute, the qualified name, which is
     now used for the representation of a generator (‘repr(gen)’).
     (Contributed by Victor Stinner in bpo-21205(4).)

   * The deprecated "strict" mode and argument of *note HTMLParser: 81a,
     ‘HTMLParser.error()’, and the ‘HTMLParserError’ exception have been
     removed.  (Contributed by Ezio Melotti in bpo-15114(5).)  The
     'convert_charrefs' argument of *note HTMLParser: 81a. is now ‘True’
     by default.  (Contributed by Berker Peksag in bpo-21047(6).)

   * Although it is not formally part of the API, it is worth noting for
     porting purposes (ie: fixing tests) that error messages that were
     previously of the form "'sometype' does not support the buffer
     protocol" are now of the form "a *note bytes-like object: cd4. is
     required, not 'sometype'".  (Contributed by Ezio Melotti in
     bpo-16518(7).)

   * If the current directory is set to a directory that no longer
     exists then *note FileNotFoundError: e67. will no longer be raised
     and instead *note find_spec(): e68. will return ‘None’ 'without'
     caching ‘None’ in *note sys.path_importer_cache: 588, which is
     different than the typical case (bpo-22834(8)).

   * HTTP status code and messages from *note http.client: 65. and *note
     http.server: 68. were refactored into a common *note HTTPStatus:
     8a5. enum.  The values in *note http.client: 65. and *note
     http.server: 68. remain available for backwards compatibility.
     (Contributed by Demian Brecht in bpo-21793(9).)

   * When an import loader defines
     ‘importlib.machinery.Loader.exec_module()’ it is now expected to
     also define ‘create_module()’ (raises a *note DeprecationWarning:
     18b. now, will be an error in Python 3.6).  If the loader inherits
     from *note importlib.abc.Loader: e69. then there is nothing to do,
     else simply define ‘create_module()’ to return ‘None’.
     (Contributed by Brett Cannon in bpo-23014(10).)

   * The *note re.split(): 282. function always ignored empty pattern
     matches, so the ‘"x*"’ pattern worked the same as ‘"x+"’, and the
     ‘"\b"’ pattern never worked.  Now *note re.split(): 282. raises a
     warning if the pattern could match an empty string.  For
     compatibility, use patterns that never match an empty string (e.g.
     ‘"x+"’ instead of ‘"x*"’).  Patterns that could only match an empty
     string (such as ‘"\b"’) now raise an error.  (Contributed by Serhiy
     Storchaka in bpo-22818(11).)

   * The *note http.cookies.Morsel: bab. dict-like interface has been
     made self consistent: morsel comparison now takes the *note key:
     ba8. and *note value: ba9. into account, *note copy(): e6a. now
     results in a *note Morsel: bab. instance rather than a *note dict:
     23b, and *note update(): e6b. will now raise an exception if any of
     the keys in the update dictionary are invalid.  In addition, the
     undocumented 'LegalChars' parameter of *note set(): bac. is
     deprecated and is now ignored.  (Contributed by Demian Brecht in
     bpo-2211(12).)

   * PEP 488(13) has removed ‘.pyo’ files from Python and introduced the
     optional ‘opt-’ tag in ‘.pyc’ file names.  The *note
     importlib.util.cache_from_source(): 2cf. has gained an
     'optimization' parameter to help control the ‘opt-’ tag.  Because
     of this, the 'debug_override' parameter of the function is now
     deprecated.  ‘.pyo’ files are also no longer supported as a file
     argument to the Python interpreter and thus serve no purpose when
     distributed on their own (i.e.  sourceless code distribution).  Due
     to the fact that the magic number for bytecode has changed in
     Python 3.5, all old ‘.pyo’ files from previous versions of Python
     are invalid regardless of this PEP.

   * The *note socket: b8. module now exports the *note
     CAN_RAW_FD_FRAMES: e6c. constant on linux 3.6 and greater.

   * The *note ssl.cert_time_to_seconds(): e0d. function now interprets
     the input time as UTC and not as local time, per RFC 5280(14).
     Additionally, the return value is always an *note int: 23c.
     (Contributed by Akira Li in bpo-19940(15).)

   * The ‘pygettext.py’ Tool now uses the standard +NNNN format for
     timezones in the POT-Creation-Date header.

   * The *note smtplib: b7. module now uses *note sys.stderr: 8dd.
     instead of the previous module-level ‘stderr’ variable for debug
     output.  If your (test) program depends on patching the
     module-level variable to capture the debug output, you will need to
     update it to capture sys.stderr instead.

   * The *note str.startswith(): e6d. and *note str.endswith(): e6e.
     methods no longer return ‘True’ when finding the empty string and
     the indexes are completely out of range.  (Contributed by Serhiy
     Storchaka in bpo-24284(16).)

   * The *note inspect.getdoc(): 99e. function now returns documentation
     strings inherited from base classes.  Documentation strings no
     longer need to be duplicated if the inherited documentation is
     appropriate.  To suppress an inherited string, an empty string must
     be specified (or the documentation may be filled in).  This change
     affects the output of the *note pydoc: a3. module and the *note
     help(): 87c. function.  (Contributed by Serhiy Storchaka in
     bpo-15582(17).)

   * Nested *note functools.partial(): 356. calls are now flattened.  If
     you were relying on the previous behavior, you can now either add
     an attribute to a *note functools.partial(): 356. object or you can
     create a subclass of *note functools.partial(): 356.  (Contributed
     by Alexander Belopolsky in bpo-7830(18).)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0475/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=13936

   (3) https://bugs.python.org/issue?@action=redirect&bpo=20951

   (4) https://bugs.python.org/issue?@action=redirect&bpo=21205

   (5) https://bugs.python.org/issue?@action=redirect&bpo=15114

   (6) https://bugs.python.org/issue?@action=redirect&bpo=21047

   (7) https://bugs.python.org/issue?@action=redirect&bpo=16518

   (8) https://bugs.python.org/issue?@action=redirect&bpo=22834

   (9) https://bugs.python.org/issue?@action=redirect&bpo=21793

   (10) https://bugs.python.org/issue?@action=redirect&bpo=23014

   (11) https://bugs.python.org/issue?@action=redirect&bpo=22818

   (12) https://bugs.python.org/issue?@action=redirect&bpo=2211

   (13) https://peps.python.org/pep-0488/

   (14) https://datatracker.ietf.org/doc/html/rfc5280.html

   (15) https://bugs.python.org/issue?@action=redirect&bpo=19940

   (16) https://bugs.python.org/issue?@action=redirect&bpo=24284

   (17) https://bugs.python.org/issue?@action=redirect&bpo=15582

   (18) https://bugs.python.org/issue?@action=redirect&bpo=7830


File: python.info,  Node: C API 中的改動<6>,  Prev: Changes in the Python API<7>,  Up: Porting to Python 3 5

1.9.11.3 C API 中的改動
.......................

   * The undocumented ‘format’ member of the (non-public)
     ‘PyMemoryViewObject’ structure has been removed.  All extensions
     relying on the relevant parts in ‘memoryobject.h’ must be rebuilt.

   * The ‘PyMemAllocator’ structure was renamed to *note
     PyMemAllocatorEx: e70. and a new ‘calloc’ field was added.

   * Removed non-documented macro ‘PyObject_REPR()’ which leaked
     references.  Use format character ‘%R’ in *note
     PyUnicode_FromFormat(): 33f.-like functions to format the *note
     repr(): 7a1. of the object.  (Contributed by Serhiy Storchaka in
     bpo-22453(1).)

   * Because the lack of the ‘__module__’ attribute breaks pickling and
     introspection, a deprecation warning is now raised for builtin
     types without the ‘__module__’ attribute.  This would be an
     AttributeError in the future.  (Contributed by Serhiy Storchaka in
     bpo-20204(2).)

   * As part of the PEP 492(3) implementation, the ‘tp_reserved’ slot of
     *note PyTypeObject: a48. was replaced with a *note tp_as_async:
     e71. slot.  Refer to *note Coroutine（協程）物件: e72. for new
     types, structures and functions.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22453

   (2) https://bugs.python.org/issue?@action=redirect&bpo=20204

   (3) https://peps.python.org/pep-0492/


File: python.info,  Node: Python 3 5 4 中顯著的變更,  Prev: Porting to Python 3 5,  Up: Python 3 4 有什麼新功能

1.9.12 Python 3.5.4 中顯著的變更
--------------------------------

* Menu:

* New make regen-all build target: New make regen-all build target<2>.
* Removal of make touch build target: Removal of make touch build target<2>.


File: python.info,  Node: New make regen-all build target<2>,  Next: Removal of make touch build target<2>,  Up: Python 3 5 4 中顯著的變更

1.9.12.1 New ‘make regen-all’ build target
..........................................

To simplify cross-compilation, and to ensure that CPython can reliably
be compiled without requiring an existing version of Python to already
be available, the autotools-based build system no longer attempts to
implicitly recompile generated files based on file modification times.

Instead, a new ‘make regen-all’ command has been added to force
regeneration of these files when desired (e.g.  after an initial version
of Python has already been built based on the pregenerated versions).

More selective regeneration targets are also defined - see
Makefile.pre.in(1) for details.

（由 Victor Stinner 在 bpo-23404(2) 中貢獻。）

在 3.5.4 版被加入.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Makefile.pre.in

   (2) https://bugs.python.org/issue?@action=redirect&bpo=23404


File: python.info,  Node: Removal of make touch build target<2>,  Prev: New make regen-all build target<2>,  Up: Python 3 5 4 中顯著的變更

1.9.12.2 Removal of ‘make touch’ build target
.............................................

The ‘make touch’ build target previously used to request implicit
regeneration of generated files by updating their modification times has
been removed.

It has been replaced by the new ‘make regen-all’ target.

（由 Victor Stinner 在 bpo-23404(1) 中貢獻。）

在 3.5.4 版的變更.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23404


File: python.info,  Node: Python 3 4 有什麼新功能<2>,  Next: Python 3 3 有什麼新功能,  Prev: Python 3 4 有什麼新功能,  Up: Python 有什麼新功能？

1.10 Python 3.4 有什麼新功能
============================


作者: R. David Murray <<rdmurray@bitdance.com>> （編輯者）

This article explains the new features in Python 3.4, compared to 3.3.
Python 3.4 was released on March 16, 2014.  For full details, see the
changelog(1).

也參考
......

PEP 429(2) - Python 3.4 Release Schedule

* Menu:

* Summary: Summary -- Release Highlights<3>. Release Highlights
* New Features: New Features<9>.
* 新模組: 新模組<5>.
* 改進的模組: 改進的模組<9>.
* CPython 實作變更::
* 已棄用: 已棄用<11>.
* 已移除: 已移除<9>.
* Porting to Python 3.4: Porting to Python 3 4.
* 3.4.3 中的變更: 3 4 3 中的變更.

   ---------- Footnotes ----------

   (1) https://docs.python.org/3.4/whatsnew/changelog.html

   (2) https://peps.python.org/pep-0429/


File: python.info,  Node: Summary -- Release Highlights<3>,  Next: New Features<9>,  Up: Python 3 4 有什麼新功能<2>

1.10.1 Summary - Release Highlights
-----------------------------------

新增語法特性：

   * No new syntax features were added in Python 3.4.

Other new features:

   * *note pip should always be available: e79. ( PEP 453(1)).

   * *note Newly created file descriptors are non-inheritable: e7a. (
     PEP 446(2)).

   * command line option for *note isolated mode: e7b. (bpo-16499(3)).

   * *note improvements in the handling of codecs: e7c. that are not
     text encodings (multiple issues).

   * *note A ModuleSpec Type: e7d. for the Import System ( PEP 451(4)).
     (Affects importer authors.)

   * The *note marshal: 80. format has been made *note more compact and
     efficient: e7e. (bpo-16475(5)).

New library modules:

   * *note asyncio: 8.: *note New provisional API for asynchronous IO:
     e7f. ( PEP 3156(6)).

   * *note ensurepip: 4b.: *note Bootstrapping the pip installer: e80. (
     PEP 453(7)).

   * *note enum: 4c.: *note Support for enumeration types: e81. ( PEP
     435(8)).

   * *note pathlib: 93.: *note Object-oriented filesystem paths: e82. (
     PEP 428(9)).

   * *note selectors: b0.: *note High-level and efficient I/O
     multiplexing: e83, built upon the *note select: af. module
     primitives (part of PEP 3156(10)).

   * *note statistics: bd.: A basic *note numerically stable statistics
     library: e84. ( PEP 450(11)).

   * *note tracemalloc: e8.: *note Trace Python memory allocations: e85.
     ( PEP 454(12)).

Significantly improved library modules:

   * *note Single-dispatch generic functions: e86. in *note functools:
     55. ( PEP 443(13)).

   * New *note pickle: 95. *note protocol 4: e87. ( PEP 3154(14)).

   * *note multiprocessing: 86. now has *note an option to avoid using
     os.fork on Unix: e88. (bpo-8713(15)).

   * *note email: 32. has a new submodule, *note contentmanager: 34, and
     a new *note Message: 261. subclass (‘EmailMessage’) that *note
     simplify MIME handling: e89. (bpo-18891(16)).

   * The *note inspect: 72. and *note pydoc: a3. modules are now capable
     of correct introspection of a much wider variety of callable
     objects, which improves the output of the Python *note help(): 87c.
     system.

   * The *note ipaddress: 74. module API has been declared stable

安全性改進：

   * *note Secure and interchangeable hash algorithm: e8a. ( PEP
     456(17)).

   * *note Make newly created file descriptors non-inheritable: e7a. (
     PEP 446(18)) to avoid leaking file descriptors to child processes.

   * New command line option for *note isolated mode: e7b,
     (bpo-16499(19)).

   * *note multiprocessing: 86. now has *note an option to avoid using
     os.fork on Unix: e88.  'spawn' and 'forkserver' are more secure
     because they avoid sharing data with child processes.

   * *note multiprocessing: 86. child processes on Windows no longer
     inherit all of the parent's inheritable handles, only the necessary
     ones.

   * A new *note hashlib.pbkdf2_hmac(): 4b4. function provides the
     PKCS#5 password-based key derivation function 2(20).

   * *note TLSv1.1 and TLSv1.2 support: e8b. for *note ssl: bb.

   * *note Retrieving certificates from the Windows system cert store
     support: e8c. for *note ssl: bb.

   * *note Server-side SNI (Server Name Indication) support: e8d. for
     *note ssl: bb.

   * The *note ssl.SSLContext: 276. class has a *note lot of
     improvements: e8e.

   * All modules in the standard library that support SSL now support
     server certificate verification, including hostname matching
     (‘ssl.match_hostname()’) and CRLs (Certificate Revocation lists,
     see *note ssl.SSLContext.load_verify_locations(): e8f.).

CPython implementation improvements:

   * *note Safe object finalization: e90. ( PEP 442(21)).

   * Leveraging PEP 442(22), in most cases *note module globals are no
     longer set to None during finalization: e90. (bpo-18214(23)).

   * *note Configurable memory allocators: e91. ( PEP 445(24)).

   * *note Argument Clinic: e92. ( PEP 436(25)).

Please read on for a comprehensive list of user-facing changes,
including many other smaller improvements, CPython optimizations,
deprecations, and potential porting issues.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0453/

   (2) https://peps.python.org/pep-0446/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=16499

   (4) https://peps.python.org/pep-0451/

   (5) https://bugs.python.org/issue?@action=redirect&bpo=16475

   (6) https://peps.python.org/pep-3156/

   (7) https://peps.python.org/pep-0453/

   (8) https://peps.python.org/pep-0435/

   (9) https://peps.python.org/pep-0428/

   (10) https://peps.python.org/pep-3156/

   (11) https://peps.python.org/pep-0450/

   (12) https://peps.python.org/pep-0454/

   (13) https://peps.python.org/pep-0443/

   (14) https://peps.python.org/pep-3154/

   (15) https://bugs.python.org/issue?@action=redirect&bpo=8713

   (16) https://bugs.python.org/issue?@action=redirect&bpo=18891

   (17) https://peps.python.org/pep-0456/

   (18) https://peps.python.org/pep-0446/

   (19) https://bugs.python.org/issue?@action=redirect&bpo=16499

   (20) https://en.wikipedia.org/wiki/PBKDF2

   (21) https://peps.python.org/pep-0442/

   (22) https://peps.python.org/pep-0442/

   (23) https://bugs.python.org/issue?@action=redirect&bpo=18214

   (24) https://peps.python.org/pep-0445/

   (25) https://peps.python.org/pep-0436/


File: python.info,  Node: New Features<9>,  Next: 新模組<5>,  Prev: Summary -- Release Highlights<3>,  Up: Python 3 4 有什麼新功能<2>

1.10.2 New Features
-------------------

* Menu:

* PEP 453; Explicit Bootstrapping of PIP in Python Installations: PEP 453 Explicit Bootstrapping of PIP in Python Installations.
* PEP 446; Newly Created File Descriptors Are Non-Inheritable: PEP 446 Newly Created File Descriptors Are Non-Inheritable.
* Improvements to Codec Handling::
* PEP 451; A ModuleSpec Type for the Import System: PEP 451 A ModuleSpec Type for the Import System.
* 其他語言更動: 其他語言更動<9>.


File: python.info,  Node: PEP 453 Explicit Bootstrapping of PIP in Python Installations,  Next: PEP 446 Newly Created File Descriptors Are Non-Inheritable,  Up: New Features<9>

1.10.2.1 PEP 453: Explicit Bootstrapping of PIP in Python Installations
.......................................................................

* Menu:

* Bootstrapping pip By Default::
* Documentation Changes::


File: python.info,  Node: Bootstrapping pip By Default,  Next: Documentation Changes,  Up: PEP 453 Explicit Bootstrapping of PIP in Python Installations

1.10.2.2 Bootstrapping pip By Default
.....................................

The new *note ensurepip: 4b. module (defined in PEP 453(1)) provides a
standard cross-platform mechanism to bootstrap the pip installer into
Python installations and virtual environments.  The version of ‘pip’
included with Python 3.4.0 is ‘pip’ 1.5.4, and future 3.4.x maintenance
releases will update the bundled version to the latest version of ‘pip’
that is available at the time of creating the release candidate.

By default, the commands ‘pipX’ and ‘pipX.Y’ will be installed on all
platforms (where X.Y stands for the version of the Python installation),
along with the ‘pip’ Python package and its dependencies.  On Windows
and in virtual environments on all platforms, the unversioned ‘pip’
command will also be installed.  On other platforms, the system wide
unversioned ‘pip’ command typically refers to the separately installed
Python 2 version.

The ‘pyvenv’ command line utility and the *note venv: f9. module make
use of the *note ensurepip: 4b. module to make ‘pip’ readily available
in virtual environments.  When using the command line utility, ‘pip’ is
installed by default, while when using the *note venv: f9. module *note
API: e96. installation of ‘pip’ must be requested explicitly.

For CPython *note source builds on POSIX systems: e97, the ‘make
install’ and ‘make altinstall’ commands bootstrap ‘pip’ by default.
This behaviour can be controlled through configure options, and
overridden through Makefile options.

On Windows and Mac OS X, the CPython installers now default to
installing ‘pip’ along with CPython itself (users may opt out of
installing it during the installation process).  Window users will need
to opt in to the automatic ‘PATH’ modifications to have ‘pip’ available
from the command line by default, otherwise it can still be accessed
through the Python launcher for Windows as ‘py -m pip’.

As discussed in the PEP(2), platform packagers may choose not to install
these commands by default, as long as, when invoked, they provide clear
and simple directions on how to install them on that platform (usually
using the system package manager).

     備註: To avoid conflicts between parallel Python 2 and Python 3
     installations, only the versioned ‘pip3’ and ‘pip3.4’ commands are
     bootstrapped by default when ‘ensurepip’ is invoked directly - the
     ‘--default-pip’ option is needed to also request the unversioned
     ‘pip’ command.  ‘pyvenv’ and the Windows installer ensure that the
     unqualified ‘pip’ command is made available in those environments,
     and ‘pip’ can always be invoked via the ‘-m’ switch rather than
     directly to avoid ambiguity on systems with multiple Python
     installations.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0453/

   (2) 
https://peps.python.org/pep-0453/#recommendations-for-downstream-distributors


File: python.info,  Node: Documentation Changes,  Prev: Bootstrapping pip By Default,  Up: PEP 453 Explicit Bootstrapping of PIP in Python Installations

1.10.2.3 Documentation Changes
..............................

As part of this change, the *note 安裝 Python 模組: e99. and
distributing-index sections of the documentation have been completely
redesigned as short getting started and FAQ documents.  Most packaging
documentation has now been moved out to the Python Packaging Authority
maintained Python Packaging User Guide(1) and the documentation of the
individual projects.

However, as this migration is currently still incomplete, the legacy
versions of those guides remaining available as *note Building C and C++
Extensions with setuptools: e9a. and *note Building C and C++ Extensions
with setuptools: e9b.

也參考
......

PEP 453(2) - Explicit bootstrapping of pip in Python installations

     PEP written by Donald Stufft and Nick Coghlan, implemented by
     Donald Stufft, Nick Coghlan, Martin von Löwis and Ned Deily.

   ---------- Footnotes ----------

   (1) https://packaging.python.org

   (2) https://peps.python.org/pep-0453/


File: python.info,  Node: PEP 446 Newly Created File Descriptors Are Non-Inheritable,  Next: Improvements to Codec Handling,  Prev: PEP 453 Explicit Bootstrapping of PIP in Python Installations,  Up: New Features<9>

1.10.2.4 PEP 446: Newly Created File Descriptors Are Non-Inheritable
....................................................................

PEP 446(1) makes newly created file descriptors *note non-inheritable:
e9d.  In general, this is the behavior an application will want: when
launching a new process, having currently open files also open in the
new process can lead to all sorts of hard to find bugs, and potentially
to security issues.

However, there are occasions when inheritance is desired.  To support
these cases, the following new functions and methods are available:

   * *note os.get_inheritable(): e9e, *note os.set_inheritable(): e9f.

   * *note os.get_handle_inheritable(): ea0, *note
     os.set_handle_inheritable(): ea1.

   * *note socket.socket.get_inheritable(): ea2, *note
     socket.socket.set_inheritable(): ea3.

也參考
......

PEP 446(2) - Make newly created file descriptors non-inheritable

     由 Victor Stinner 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0446/

   (2) https://peps.python.org/pep-0446/


File: python.info,  Node: Improvements to Codec Handling,  Next: PEP 451 A ModuleSpec Type for the Import System,  Prev: PEP 446 Newly Created File Descriptors Are Non-Inheritable,  Up: New Features<9>

1.10.2.5 Improvements to Codec Handling
.......................................

Since it was first introduced, the *note codecs: 14. module has always
been intended to operate as a type-neutral dynamic encoding and decoding
system.  However, its close coupling with the Python text model,
especially the type restricted convenience methods on the builtin *note
str: 3f2, *note bytes: 1a5. and *note bytearray: 4e3. types, has
historically obscured that fact.

As a key step in clarifying the situation, the *note codecs.encode():
ea5. and *note codecs.decode(): ea6. convenience functions are now
properly documented in Python 2.7, 3.3 and 3.4.  These functions have
existed in the *note codecs: 14. module (and have been covered by the
regression test suite) since Python 2.4, but were previously only
discoverable through runtime introspection.

Unlike the convenience methods on *note str: 3f2, *note bytes: 1a5. and
*note bytearray: 4e3, the *note codecs: 14. convenience functions
support arbitrary codecs in both Python 2 and Python 3, rather than
being limited to Unicode text encodings (in Python 3) or ‘basestring’
<-> ‘basestring’ conversions (in Python 2).

In Python 3.4, the interpreter is able to identify the known non-text
encodings provided in the standard library and direct users towards
these general purpose convenience functions when appropriate:

     >>> b"abcdef".decode("hex")
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     LookupError: 'hex' is not a text encoding; use codecs.decode() to handle arbitrary codecs

     >>> "hello".encode("rot13")
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     LookupError: 'rot13' is not a text encoding; use codecs.encode() to handle arbitrary codecs

     >>> open("foo.txt", encoding="hex")
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     LookupError: 'hex' is not a text encoding; use codecs.open() to handle arbitrary codecs

In a related change, whenever it is feasible without breaking backwards
compatibility, exceptions raised during encoding and decoding operations
are wrapped in a chained exception of the same type that mentions the
name of the codec responsible for producing the error:

     >>> import codecs

     >>> codecs.decode(b"abcdefgh", "hex")
     Traceback (most recent call last):
       File "/usr/lib/python3.4/encodings/hex_codec.py", line 20, in hex_decode
         return (binascii.a2b_hex(input), len(input))
     binascii.Error: Non-hexadecimal digit found

     The above exception was the direct cause of the following exception:

     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     binascii.Error: decoding with 'hex' codec failed (Error: Non-hexadecimal digit found)

     >>> codecs.encode("hello", "bz2")
     Traceback (most recent call last):
       File "/usr/lib/python3.4/encodings/bz2_codec.py", line 17, in bz2_encode
         return (bz2.compress(input), len(input))
       File "/usr/lib/python3.4/bz2.py", line 498, in compress
         return comp.compress(data) + comp.flush()
     TypeError: 'str' does not support the buffer interface

     The above exception was the direct cause of the following exception:

     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: encoding with 'bz2' codec failed (TypeError: 'str' does not support the buffer interface)

Finally, as the examples above show, these improvements have permitted
the restoration of the convenience aliases for the non-Unicode codecs
that were themselves restored in Python 3.2.  This means that encoding
binary data to and from its hexadecimal representation (for example) can
now be written as:

     >>> from codecs import encode, decode
     >>> encode(b"hello", "hex")
     b'68656c6c6f'
     >>> decode(b"68656c6c6f", "hex")
     b'hello'

The binary and text transforms provided in the standard library are
detailed in *note Binary Transforms: ea7. and *note Text Transforms:
ea8.

（由 Nick Coghlan 在 bpo-7475(1)、bpo-17827(2)、bpo-17828(3) 和
bpo-19619(4) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=7475

   (2) https://bugs.python.org/issue?@action=redirect&bpo=17827

   (3) https://bugs.python.org/issue?@action=redirect&bpo=17828

   (4) https://bugs.python.org/issue?@action=redirect&bpo=19619


File: python.info,  Node: PEP 451 A ModuleSpec Type for the Import System,  Next: 其他語言更動<9>,  Prev: Improvements to Codec Handling,  Up: New Features<9>

1.10.2.6 PEP 451: A ModuleSpec Type for the Import System
.........................................................

PEP 451(1) provides an encapsulation of the information about a module
that the import machinery will use to load it (that is, a module
specification).  This helps simplify both the import implementation and
several import-related APIs.  The change is also a stepping stone for
several future import-related improvements(2).

The public-facing changes from the PEP are entirely backward-compatible.
Furthermore, they should be transparent to everyone but importer
authors.  Key finder and loader methods have been deprecated, but they
will continue working.  New importers should use the new methods
described in the PEP. Existing importers should be updated to implement
the new methods.  See the *note 已棄用: eaa. section for a list of
methods that should be replaced and their replacements.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0451/

   (2) 
https://mail.python.org/pipermail/python-dev/2013-November/130111.html


File: python.info,  Node: 其他語言更動<9>,  Prev: PEP 451 A ModuleSpec Type for the Import System,  Up: New Features<9>

1.10.2.7 其他語言更動
.....................

Some smaller changes made to the core Python language are:

   * Unicode database updated to UCD version 6.3.

   * *note min(): eac. and *note max(): ead. now accept a 'default'
     keyword-only argument that can be used to specify the value they
     return if the iterable they are evaluating has no elements.
     (Contributed by Julian Berman in bpo-18111(1).)

   * Module objects are now *note weakly referenceable: eae.

   * Module ‘__file__’ attributes (and related values) should now always
     contain absolute paths by default, with the sole exception of
     ‘__main__.__file__’ when a script has been executed directly using
     a relative path.  (Contributed by Brett Cannon in bpo-18416(2).)

   * All the UTF-* codecs (except UTF-7) now reject surrogates during
     both encoding and decoding unless the ‘surrogatepass’ error handler
     is used, with the exception of the UTF-16 decoder (which accepts
     valid surrogate pairs) and the UTF-16 encoder (which produces them
     while encoding non-BMP characters).  (Contributed by Victor
     Stinner, Kang-Hao (Kenny) Lu and Serhiy Storchaka in bpo-12892(3).)

   * New German EBCDIC *note codec: d5f. ‘cp273’.  (Contributed by
     Michael Bierenfeld and Andrew Kuchling in bpo-1097797(4).)

   * New Ukrainian *note codec: d5f. ‘cp1125’.  (Contributed by Serhiy
     Storchaka in bpo-19668(5).)

   * *note bytes: 1a5.join() and *note bytearray: 4e3.join() now accept
     arbitrary buffer objects as arguments.  (Contributed by Antoine
     Pitrou in bpo-15958(6).)

   * The *note int: 23c. constructor now accepts any object that has an
     ‘__index__’ method for its 'base' argument.  (Contributed by Mark
     Dickinson in bpo-16772(7).)

   * Frame objects now have a *note clear(): 27f. method that clears all
     references to local variables from the frame.  (Contributed by
     Antoine Pitrou in bpo-17934(8).)

   * *note memoryview: 40f. is now registered as a *note Sequence: 17,
     and supports the *note reversed(): 80a. builtin.  (Contributed by
     Nick Coghlan and Claudiu Popa in bpo-18690(9) and bpo-19078(10).)

   * Signatures reported by *note help(): 87c. have been modified and
     improved in several cases as a result of the introduction of
     Argument Clinic and other changes to the *note inspect: 72. and
     *note pydoc: a3. modules.

   * *note __length_hint__(): eaf. is now part of the formal language
     specification (see PEP 424(11)).  (Contributed by Armin Ronacher in
     bpo-16148(12).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=18111

   (2) https://bugs.python.org/issue?@action=redirect&bpo=18416

   (3) https://bugs.python.org/issue?@action=redirect&bpo=12892

   (4) https://bugs.python.org/issue?@action=redirect&bpo=1097797

   (5) https://bugs.python.org/issue?@action=redirect&bpo=19668

   (6) https://bugs.python.org/issue?@action=redirect&bpo=15958

   (7) https://bugs.python.org/issue?@action=redirect&bpo=16772

   (8) https://bugs.python.org/issue?@action=redirect&bpo=17934

   (9) https://bugs.python.org/issue?@action=redirect&bpo=18690

   (10) https://bugs.python.org/issue?@action=redirect&bpo=19078

   (11) https://peps.python.org/pep-0424/

   (12) https://bugs.python.org/issue?@action=redirect&bpo=16148


File: python.info,  Node: 新模組<5>,  Next: 改進的模組<9>,  Prev: New Features<9>,  Up: Python 3 4 有什麼新功能<2>

1.10.3 新模組
-------------

* Menu:

* asyncio: asyncio<11>.
* ensurepip: ensurepip<2>.
* enum: enum<8>.
* pathlib: pathlib<11>.
* selectors: selectors<2>.
* statistics: statistics<6>.
* tracemalloc: tracemalloc<4>.


File: python.info,  Node: asyncio<11>,  Next: ensurepip<2>,  Up: 新模組<5>

1.10.3.1 asyncio
................

The new *note asyncio: 8. module (defined in PEP 3156(1)) provides a
standard pluggable event loop model for Python, providing solid
asynchronous IO support in the standard library, and making it easier
for other event loop implementations to interoperate with the standard
library and each other.

For Python 3.4, this module is considered a *note provisional API: aa6.

也參考
......

PEP 3156(2) - Asynchronous IO Support Rebooted: the "asyncio" Module

     由 Guido van Rossum 撰寫 PEP 與帶領實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3156/

   (2) https://peps.python.org/pep-3156/


File: python.info,  Node: ensurepip<2>,  Next: enum<8>,  Prev: asyncio<11>,  Up: 新模組<5>

1.10.3.2 ensurepip
..................

The new *note ensurepip: 4b. module is the primary infrastructure for
the PEP 453(1) implementation.  In the normal course of events end users
will not need to interact with this module, but it can be used to
manually bootstrap ‘pip’ if the automated bootstrapping into an
installation or virtual environment was declined.

*note ensurepip: 4b. includes a bundled copy of ‘pip’, up-to-date as of
the first release candidate of the release of CPython with which it
ships (this applies to both maintenance releases and feature releases).
‘ensurepip’ does not access the internet.  If the installation has
internet access, after ‘ensurepip’ is run the bundled ‘pip’ can be used
to upgrade ‘pip’ to a more recent release than the bundled one.  (Note
that such an upgraded version of ‘pip’ is considered to be a separately
installed package and will not be removed if Python is uninstalled.)

The module is named 'ensure'pip because if called when ‘pip’ is already
installed, it does nothing.  It also has an ‘--upgrade’ option that will
cause it to install the bundled copy of ‘pip’ if the existing installed
version of ‘pip’ is older than the bundled copy.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0453/


File: python.info,  Node: enum<8>,  Next: pathlib<11>,  Prev: ensurepip<2>,  Up: 新模組<5>

1.10.3.3 enum
.............

The new *note enum: 4c. module (defined in PEP 435(1)) provides a
standard implementation of enumeration types, allowing other modules
(such as *note socket: b8.) to provide more informative error messages
and better debugging support by replacing opaque integer constants with
backwards compatible enumeration values.

也參考
......

PEP 435(2) - Adding an Enum type to the Python standard library

     PEP written by Barry Warsaw, Eli Bendersky and Ethan Furman,
     implemented by Ethan Furman.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0435/

   (2) https://peps.python.org/pep-0435/


File: python.info,  Node: pathlib<11>,  Next: selectors<2>,  Prev: enum<8>,  Up: 新模組<5>

1.10.3.4 pathlib
................

The new *note pathlib: 93. module offers classes representing filesystem
paths with semantics appropriate for different operating systems.  Path
classes are divided between 'pure paths', which provide purely
computational operations without I/O, and 'concrete paths', which
inherit from pure paths but also provide I/O operations.

For Python 3.4, this module is considered a *note provisional API: aa6.

也參考
......

PEP 428(1) - The pathlib module - object-oriented filesystem paths

     由 Antoine Pitrou 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0428/


File: python.info,  Node: selectors<2>,  Next: statistics<6>,  Prev: pathlib<11>,  Up: 新模組<5>

1.10.3.5 selectors
..................

The new *note selectors: b0. module (created as part of implementing PEP
3156(1)) allows high-level and efficient I/O multiplexing, built upon
the *note select: af. module primitives.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3156/


File: python.info,  Node: statistics<6>,  Next: tracemalloc<4>,  Prev: selectors<2>,  Up: 新模組<5>

1.10.3.6 statistics
...................

The new *note statistics: bd. module (defined in PEP 450(1)) offers some
core statistics functionality directly in the standard library.  This
module supports calculation of the mean, median, mode, variance and
standard deviation of a data series.

也參考
......

PEP 450(2) - Adding A Statistics Module To The Standard Library

     由 Steven D'Aprano 撰寫 PEP 與實作

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0450/

   (2) https://peps.python.org/pep-0450/


File: python.info,  Node: tracemalloc<4>,  Prev: statistics<6>,  Up: 新模組<5>

1.10.3.7 tracemalloc
....................

The new *note tracemalloc: e8. module (defined in PEP 454(1)) is a debug
tool to trace memory blocks allocated by Python.  It provides the
following information:

   * Trace where an object was allocated

   * Statistics on allocated memory blocks per filename and per line
     number: total size, number and average size of allocated memory
     blocks

   * Compute the differences between two snapshots to detect memory
     leaks

也參考
......

PEP 454(2) - Add a new tracemalloc module to trace Python memory allocations

     由 Victor Stinner 撰寫 PEP 與實作

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0454/

   (2) https://peps.python.org/pep-0454/


File: python.info,  Node: 改進的模組<9>,  Next: CPython 實作變更,  Prev: 新模組<5>,  Up: Python 3 4 有什麼新功能<2>

1.10.4 改進的模組
-----------------

* Menu:

* abc::
* aifc: aifc<2>.
* argparse: argparse<5>.
* audioop::
* base64: base64<3>.
* collections: collections<6>.
* colorsys::
* contextlib: contextlib<6>.
* dbm: dbm<6>.
* dis: dis<4>.
* doctest: doctest<4>.
* email: email<4>.
* filecmp::
* functools: functools<5>.
* gc: gc<6>.
* glob: glob<4>.
* hashlib: hashlib<6>.
* hmac: hmac<3>.
* html::
* http: http<3>.
* idlelib 與 IDLE::
* importlib: importlib<9>.
* inspect: inspect<8>.
* ipaddress: ipaddress<5>.
* logging: logging<6>.
* marshal: marshal<2>.
* mmap: mmap<3>.
* multiprocessing: multiprocessing<7>.
* operator: operator<3>.
* os: os<11>.
* pdb: pdb<6>.
* pickle: pickle<4>.
* plistlib: plistlib<2>.
* poplib: poplib<3>.
* pprint: pprint<4>.
* pty::
* pydoc: pydoc<4>.
* re: re<8>.
* resource::
* select::
* shelve: shelve<2>.
* shutil: shutil<6>.
* smtpd: smtpd<3>.
* smtplib: smtplib<3>.
* socket: socket<9>.
* sqlite3: sqlite3<9>.
* ssl: ssl<10>.
* stat::
* struct: struct<2>.
* subprocess: subprocess<5>.
* sunau: sunau<2>.
* sys: sys<11>.
* tarfile: tarfile<7>.
* textwrap::
* threading: threading<7>.
* traceback: traceback<6>.
* types: types<6>.
* urllib: urllib<3>.
* unittest: unittest<9>.
* venv: venv<7>.
* wave: wave<2>.
* weakref: weakref<2>.
* xml.etree: xml etree<2>.
* zipfile: zipfile<5>.


File: python.info,  Node: abc,  Next: aifc<2>,  Up: 改進的模組<9>

1.10.4.1 abc
............

New function *note abc.get_cache_token(): eba. can be used to know when
to invalidate caches that are affected by changes in the object graph.
(Contributed by Łukasz Langa in bpo-16832(1).)

New class *note ABC: ebb. has *note ABCMeta: ebc. as its meta class.
Using ‘ABC’ as a base class has essentially the same effect as
specifying ‘metaclass=abc.ABCMeta’, but is simpler to type and easier to
read.  (Contributed by Bruno Dupuis in bpo-16049(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16832

   (2) https://bugs.python.org/issue?@action=redirect&bpo=16049


File: python.info,  Node: aifc<2>,  Next: argparse<5>,  Prev: abc,  Up: 改進的模組<9>

1.10.4.2 aifc
.............

The ‘getparams()’ method now returns a namedtuple rather than a plain
tuple.  (Contributed by Claudiu Popa in bpo-17818(1).)

‘aifc.open()’ now supports the context management protocol: when used in
a *note with: 577. block, the ‘close()’ method of the returned object
will be called automatically at the end of the block.  (Contributed by
Serhiy Storchacha in bpo-16486(2).)

The ‘writeframesraw()’ and ‘writeframes()’ methods now accept any *note
bytes-like object: cd4.  (Contributed by Serhiy Storchaka in
bpo-8311(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=17818

   (2) https://bugs.python.org/issue?@action=redirect&bpo=16486

   (3) https://bugs.python.org/issue?@action=redirect&bpo=8311


File: python.info,  Node: argparse<5>,  Next: audioop,  Prev: aifc<2>,  Up: 改進的模組<9>

1.10.4.3 argparse
.................

The *note FileType: ebf. class now accepts 'encoding' and 'errors'
arguments, which are passed through to *note open(): 4c0.  (Contributed
by Lucas Maystre in bpo-11175(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=11175


File: python.info,  Node: audioop,  Next: base64<3>,  Prev: argparse<5>,  Up: 改進的模組<9>

1.10.4.4 audioop
................

‘audioop’ now supports 24-bit samples.  (Contributed by Serhiy Storchaka
in bpo-12866(1).)

New ‘byteswap()’ function converts big-endian samples to little-endian
and vice versa.  (Contributed by Serhiy Storchaka in bpo-19641(2).)

All ‘audioop’ functions now accept any *note bytes-like object: cd4.
Strings are not accepted: they didn't work before, now they raise an
error right away.  (Contributed by Serhiy Storchaka in bpo-16685(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=12866

   (2) https://bugs.python.org/issue?@action=redirect&bpo=19641

   (3) https://bugs.python.org/issue?@action=redirect&bpo=16685


File: python.info,  Node: base64<3>,  Next: collections<6>,  Prev: audioop,  Up: 改進的模組<9>

1.10.4.5 base64
...............

The encoding and decoding functions in *note base64: a. now accept any
*note bytes-like object: cd4. in cases where it previously required a
*note bytes: 1a5. or *note bytearray: 4e3. instance.  (Contributed by
Nick Coghlan in bpo-17839(1).)

New functions *note a85encode(): ec2, *note a85decode(): ec3, *note
b85encode(): ec4, and *note b85decode(): ec5. provide the ability to
encode and decode binary data from and to ‘Ascii85’ and the
git/mercurial ‘Base85’ formats, respectively.  The ‘a85’ functions have
options that can be used to make them compatible with the variants of
the ‘Ascii85’ encoding, including the Adobe variant.  (Contributed by
Martin Morrison, the Mercurial project, Serhiy Storchaka, and Antoine
Pitrou in bpo-17618(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=17839

   (2) https://bugs.python.org/issue?@action=redirect&bpo=17618


File: python.info,  Node: collections<6>,  Next: colorsys,  Prev: base64<3>,  Up: 改進的模組<9>

1.10.4.6 collections
....................

The *note ChainMap.new_child(): ec7. method now accepts an 'm' argument
specifying the child map to add to the chain.  This allows an existing
mapping and/or a custom mapping type to be used for the child.
(Contributed by Vinay Sajip in bpo-16613(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16613


File: python.info,  Node: colorsys,  Next: contextlib<6>,  Prev: collections<6>,  Up: 改進的模組<9>

1.10.4.7 colorsys
.................

The number of digits in the coefficients for the RGB -- YIQ conversions
have been expanded so that they match the FCC NTSC versions.  The change
in results should be less than 1% and may better match results found
elsewhere.  (Contributed by Brian Landers and Serhiy Storchaka in
bpo-14323(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=14323


File: python.info,  Node: contextlib<6>,  Next: dbm<6>,  Prev: colorsys,  Up: 改進的模組<9>

1.10.4.8 contextlib
...................

The new *note contextlib.suppress: eca. context manager helps to clarify
the intent of code that deliberately suppresses exceptions from a single
statement.  (Contributed by Raymond Hettinger in bpo-15806(1) and Zero
Piraeus in bpo-19266(2).)

The new *note contextlib.redirect_stdout(): d8e. context manager makes
it easier for utility scripts to handle inflexible APIs that write their
output to *note sys.stdout: a79. and don't provide any options to
redirect it.  Using the context manager, the *note sys.stdout: a79.
output can be redirected to any other stream or, in conjunction with
*note io.StringIO: ecb, to a string.  The latter can be especially
useful, for example, to capture output from a function that was written
to implement a command line interface.  It is recommended only for
utility scripts because it affects the global state of *note sys.stdout:
a79.  (Contributed by Raymond Hettinger in bpo-15805(3).)

The *note contextlib: 1c. documentation has also been updated to include
a *note discussion: ecc. of the differences between single use, reusable
and reentrant context managers.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=15806

   (2) https://bugs.python.org/issue?@action=redirect&bpo=19266

   (3) https://bugs.python.org/issue?@action=redirect&bpo=15805


File: python.info,  Node: dbm<6>,  Next: dis<4>,  Prev: contextlib<6>,  Up: 改進的模組<9>

1.10.4.9 dbm
............

*note dbm.open(): ece. objects now support the context management
protocol.  When used in a *note with: 577. statement, the ‘close’ method
of the database object will be called automatically at the end of the
block.  (Contributed by Claudiu Popa and Nick Coghlan in bpo-19282(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=19282


File: python.info,  Node: dis<4>,  Next: doctest<4>,  Prev: dbm<6>,  Up: 改進的模組<9>

1.10.4.10 dis
.............

Functions *note show_code(): ed0, *note dis(): ad8, ‘distb()’, and *note
disassemble(): ed1. now accept a keyword-only 'file' argument that
controls where they write their output.

The *note dis: 30. module is now built around an *note Instruction: 1bd.
class that provides object oriented access to the details of each
individual bytecode operation.

A new method, *note get_instructions(): 1bc, provides an iterator that
emits the Instruction stream for a given piece of Python code.  Thus it
is now possible to write a program that inspects and manipulates a
bytecode object in ways different from those provided by the *note dis:
30. module itself.  For example:

     >>> import dis
     >>> for instr in dis.get_instructions(lambda x: x + 1):
     ...     print(instr.opname)
     LOAD_FAST
     LOAD_CONST
     BINARY_ADD
     RETURN_VALUE

The various display tools in the *note dis: 30. module have been
rewritten to use these new components.

In addition, a new application-friendly class *note Bytecode: ed2.
provides an object-oriented API for inspecting bytecode in both in
human-readable form and for iterating over instructions.  The *note
Bytecode: ed2. constructor takes the same arguments that
‘get_instruction()’ does (plus an optional 'current_offset'), and the
resulting object can be iterated to produce *note Instruction: 1bd.
objects.  But it also has a *note dis: ed3. method, equivalent to
calling *note dis: ad8. on the constructor argument, but returned as a
multi-line string:

     >>> bytecode = dis.Bytecode(lambda x: x + 1, current_offset=3)
     >>> for instr in bytecode:
     ...     print('{} ({})'.format(instr.opname, instr.opcode))
     LOAD_FAST (124)
     LOAD_CONST (100)
     BINARY_ADD (23)
     RETURN_VALUE (83)
     >>> bytecode.dis().splitlines()
     ['  1           0 LOAD_FAST                0 (x)',
      '      -->     3 LOAD_CONST               1 (1)',
      '              6 BINARY_ADD',
      '              7 RETURN_VALUE']

*note Bytecode: ed2. also has a class method, *note from_traceback():
ed4, that provides the ability to manipulate a traceback (that is,
‘print(Bytecode.from_traceback(tb).dis())’ is equivalent to
‘distb(tb)’).

（由 Nick Coghlan、Ryan Kelly 和 Thomas Kluyver 在 bpo-11816(1) 中以及
Claudiu Popa 在 bpo-17916(2) 中貢獻。）

New function *note stack_effect(): ed5. computes the effect on the
Python stack of a given opcode and argument, information that is not
otherwise available.  (Contributed by Larry Hastings in bpo-19722(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=11816

   (2) https://bugs.python.org/issue?@action=redirect&bpo=17916

   (3) https://bugs.python.org/issue?@action=redirect&bpo=19722


File: python.info,  Node: doctest<4>,  Next: email<4>,  Prev: dis<4>,  Up: 改進的模組<9>

1.10.4.11 doctest
.................

A new *note option flag: ed7, *note FAIL_FAST: ed8, halts test running
as soon as the first failure is detected.  (Contributed by R. David
Murray and Daniel Urban in bpo-16522(1).)

The *note doctest: 31. command line interface now uses *note argparse:
5, and has two new options, ‘-o’ and ‘-f’.  ‘-o’ allows *note doctest
options: ed7. to be specified on the command line, and ‘-f’ is a
shorthand for ‘-o FAIL_FAST’ (to parallel the similar option supported
by the *note unittest: ef. CLI). (Contributed by R. David Murray in
bpo-11390(2).)

*note doctest: 31. will now find doctests in extension module ‘__doc__’
strings.  (Contributed by Zachary Ware in bpo-3158(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16522

   (2) https://bugs.python.org/issue?@action=redirect&bpo=11390

   (3) https://bugs.python.org/issue?@action=redirect&bpo=3158


File: python.info,  Node: email<4>,  Next: filecmp,  Prev: doctest<4>,  Up: 改進的模組<9>

1.10.4.12 email
...............

*note as_string(): eda. now accepts a 'policy' argument to override the
default policy of the message when generating a string representation of
it.  This means that ‘as_string’ can now be used in more circumstances,
instead of having to create and use a *note generator: 37. in order to
pass formatting parameters to its ‘flatten’ method.  (Contributed by R.
David Murray in bpo-18600(1).)

New method *note as_bytes(): edb. added to produce a bytes
representation of the message in a fashion similar to how ‘as_string’
produces a string representation.  It does not accept the 'maxheaderlen'
argument, but does accept the 'unixfrom' and 'policy' arguments.  The
*note Message: 261. *note __bytes__(): edc. method calls it, meaning
that ‘bytes(mymsg)’ will now produce the intuitive result: a bytes
object containing the fully formatted message.  (Contributed by R. David
Murray in bpo-18600(2).)

The *note Message.set_param(): edd. message now accepts a 'replace'
keyword argument.  When specified, the associated header will be updated
without changing its location in the list of headers.  For backward
compatibility, the default is ‘False’.  (Contributed by R. David Murray
in bpo-18891(3).)  A pair of new subclasses of *note Message: 261. have
been added (*note EmailMessage: 260. and *note MIMEPart: ede.), along
with a new sub-module, *note contentmanager: 34. and a new *note policy:
46. attribute *note content_manager: edf.  All documentation is
currently in the new module, which is being added as part of email's new
*note provisional API: aa6.  These classes provide a number of new
methods that make extracting content from and inserting content into
email messages much easier.  For details, see the *note contentmanager:
34. documentation and the *note email：範例: ee0.  These API additions
complete the bulk of the work that was planned as part of the email6
project.  The currently provisional API is scheduled to become final in
Python 3.5 (possibly with a few minor additions in the area of error
handling).  (Contributed by R. David Murray in bpo-18891(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=18600

   (2) https://bugs.python.org/issue?@action=redirect&bpo=18600

   (3) https://bugs.python.org/issue?@action=redirect&bpo=18891

   (4) https://bugs.python.org/issue?@action=redirect&bpo=18891


File: python.info,  Node: filecmp,  Next: functools<5>,  Prev: email<4>,  Up: 改進的模組<9>

1.10.4.13 filecmp
.................

A new *note clear_cache(): ee2. function provides the ability to clear
the *note filecmp: 50. comparison cache, which uses *note os.stat():
448. information to determine if the file has changed since the last
compare.  This can be used, for example, if the file might have been
changed and re-checked in less time than the resolution of a particular
filesystem's file modification time field.  (Contributed by Mark Levitt
in bpo-18149(1).)

New module attribute *note DEFAULT_IGNORES: ee3. provides the list of
directories that are used as the default value for the 'ignore'
parameter of the *note dircmp(): ee4. function.  (Contributed by Eli
Bendersky in bpo-15442(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=18149

   (2) https://bugs.python.org/issue?@action=redirect&bpo=15442


File: python.info,  Node: functools<5>,  Next: gc<6>,  Prev: filecmp,  Up: 改進的模組<9>

1.10.4.14 functools
...................

The new *note partialmethod(): a1e. descriptor brings partial argument
application to descriptors, just as *note partial(): 356. provides for
normal callables.  The new descriptor also makes it easier to get
arbitrary callables (including *note partial(): 356. instances) to
behave like normal instance methods when included in a class definition.
(Contributed by Alon Horev and Nick Coghlan in bpo-4331(1).)  The new
*note singledispatch(): 5df. decorator brings support for
single-dispatch generic functions to the Python standard library.  Where
object oriented programming focuses on grouping multiple operations on a
common set of data into a class, a generic function focuses on grouping
multiple implementations of an operation that allows it to work with
'different' kinds of data.

也參考
......

PEP 443(2) - Single-dispatch generic functions

     由 Łukasz Langa 撰寫 PEP 與實作。

*note total_ordering(): ee6. now supports a return value of *note
NotImplemented: 776. from the underlying comparison function.
(Contributed by Katie Miller in bpo-10042(3).)

A pure-python version of the *note partial(): 356. function is now in
the stdlib; in CPython it is overridden by the C accelerated version,
but it is available for other implementations to use.  (Contributed by
Brian Thorne in bpo-12428(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=4331

   (2) https://peps.python.org/pep-0443/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=10042

   (4) https://bugs.python.org/issue?@action=redirect&bpo=12428


File: python.info,  Node: gc<6>,  Next: glob<4>,  Prev: functools<5>,  Up: 改進的模組<9>

1.10.4.15 gc
............

New function *note get_stats(): 1cd. returns a list of three
per-generation dictionaries containing the collections statistics since
interpreter startup.  (Contributed by Antoine Pitrou in bpo-16351(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16351


File: python.info,  Node: glob<4>,  Next: hashlib<6>,  Prev: gc<6>,  Up: 改進的模組<9>

1.10.4.16 glob
..............

A new function *note escape(): ee9. provides a way to escape special
characters in a filename so that they do not become part of the globbing
expansion but are instead matched literally.  (Contributed by Serhiy
Storchaka in bpo-8402(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=8402


File: python.info,  Node: hashlib<6>,  Next: hmac<3>,  Prev: glob<4>,  Up: 改進的模組<9>

1.10.4.17 hashlib
.................

A new *note hashlib.pbkdf2_hmac(): 4b4. function provides the PKCS#5
password-based key derivation function 2(1).  (Contributed by Christian
Heimes in bpo-18582(2).)

The *note name: eeb. attribute of *note hashlib: 5e. hash objects is now
a formally supported interface.  It has always existed in CPython's
*note hashlib: 5e. (although it did not return lower case names for all
supported hashes), but it was not a public interface and so some other
Python implementations have not previously supported it.  (Contributed
by Jason R. Coombs in bpo-18532(3).)

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/PBKDF2

   (2) https://bugs.python.org/issue?@action=redirect&bpo=18582

   (3) https://bugs.python.org/issue?@action=redirect&bpo=18532


File: python.info,  Node: hmac<3>,  Next: html,  Prev: hashlib<6>,  Up: 改進的模組<9>

1.10.4.18 hmac
..............

*note hmac: 60. now accepts ‘bytearray’ as well as ‘bytes’ for the 'key'
argument to the *note new(): a42. function, and the 'msg' parameter to
both the *note new(): a42. function and the *note update(): eed. method
now accepts any type supported by the *note hashlib: 5e. module.
(Contributed by Jonas Borgström in bpo-18240(1).)

The 'digestmod' argument to the *note hmac.new(): a42. function may now
be any hash digest name recognized by *note hashlib: 5e.  In addition,
the current behavior in which the value of 'digestmod' defaults to ‘MD5’
is deprecated: in a future version of Python there will be no default
value.  (Contributed by Christian Heimes in bpo-17276(2).)

With the addition of *note block_size: eee. and *note name: eef.
attributes (and the formal documentation of the *note digest_size: ef0.
attribute), the *note hmac: 60. module now conforms fully to the PEP
247(3) API. (Contributed by Christian Heimes in bpo-18775(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=18240

   (2) https://bugs.python.org/issue?@action=redirect&bpo=17276

   (3) https://peps.python.org/pep-0247/

   (4) https://bugs.python.org/issue?@action=redirect&bpo=18775


File: python.info,  Node: html,  Next: http<3>,  Prev: hmac<3>,  Up: 改進的模組<9>

1.10.4.19 html
..............

New function *note unescape(): 8fb. function converts HTML5 character
references to the corresponding Unicode characters.  (Contributed by
Ezio Melotti in bpo-2927(1).)

*note HTMLParser: 81a. accepts a new keyword argument 'convert_charrefs'
that, when ‘True’, automatically converts all character references.  For
backward-compatibility, its value defaults to ‘False’, but it will
change to ‘True’ in a future version of Python, so you are invited to
set it explicitly and update your code to use this new feature.
(Contributed by Ezio Melotti in bpo-13633(2).)

The 'strict' argument of *note HTMLParser: 81a. is now deprecated.
(Contributed by Ezio Melotti in bpo-15114(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=2927

   (2) https://bugs.python.org/issue?@action=redirect&bpo=13633

   (3) https://bugs.python.org/issue?@action=redirect&bpo=15114


File: python.info,  Node: http<3>,  Next: idlelib 與 IDLE,  Prev: html,  Up: 改進的模組<9>

1.10.4.20 http
..............

*note send_error(): ef3. now accepts an optional additional 'explain'
parameter which can be used to provide an extended error description,
overriding the hardcoded default if there is one.  This extended error
description will be formatted using the ‘error_message_format’ attribute
and sent as the body of the error response.  (Contributed by Karl Cow in
bpo-12921(1).)

The *note http.server: 68. *note command line interface: ef4. now has a
‘-b/--bind’ option that causes the server to listen on a specific
address.  (Contributed by Malte Swart in bpo-17764(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=12921

   (2) https://bugs.python.org/issue?@action=redirect&bpo=17764


File: python.info,  Node: idlelib 與 IDLE,  Next: importlib<9>,  Prev: http<3>,  Up: 改進的模組<9>

1.10.4.21 idlelib 與 IDLE
.........................

Since idlelib implements the IDLE shell and editor and is not intended
for import by other programs, it gets improvements with every release.
See ‘Lib/idlelib/NEWS.txt’ for a cumulative list of changes since 3.3.0,
as well as changes made in future 3.4.x releases.  This file is also
available from the IDLE Help ‣ About IDLE dialog.


File: python.info,  Node: importlib<9>,  Next: inspect<8>,  Prev: idlelib 與 IDLE,  Up: 改進的模組<9>

1.10.4.22 importlib
...................

The *note InspectLoader: ef7. ABC defines a new method, *note
source_to_code(): db7. that accepts source data and a path and returns a
code object.  The default implementation is equivalent to ‘compile(data,
path, 'exec', dont_inherit=True)’.  (Contributed by Eric Snow and Brett
Cannon in bpo-15627(1).)

*note InspectLoader: ef7. also now has a default implementation for the
*note get_code(): ef8. method.  However, it will normally be desirable
to override the default implementation for performance reasons.
(Contributed by Brett Cannon in bpo-18072(2).)

The *note reload(): 4bd. function has been moved from ‘imp’ to *note
importlib: 6b. as part of the ‘imp’ module deprecation.  (Contributed by
Berker Peksag in bpo-18193(3).)

*note importlib.util: 71. now has a *note MAGIC_NUMBER: 4b7. attribute
providing access to the bytecode version number.  This replaces the
‘get_magic()’ function in the deprecated ‘imp’ module.  (Contributed by
Brett Cannon in bpo-18192(4).)

New *note importlib.util: 71. functions *note cache_from_source(): 2cf.
and *note source_from_cache(): 4be. replace the same-named functions in
the deprecated ‘imp’ module.  (Contributed by Brett Cannon in
bpo-18194(5).)

The *note importlib: 6b. bootstrap *note NamespaceLoader: ef9. now
conforms to the *note InspectLoader: ef7. ABC, which means that ‘runpy’
and ‘python -m’ can now be used with namespace packages.  (Contributed
by Brett Cannon in bpo-18058(6).)

*note importlib.util: 71. has a new function *note decode_source(): efa.
that decodes source from bytes using universal newline processing.  This
is useful for implementing *note InspectLoader.get_source(): efb.
methods.

*note importlib.machinery.ExtensionFileLoader: c57. now has a *note
get_filename(): efc. method.  This was inadvertently omitted in the
original implementation.  (Contributed by Eric Snow in bpo-19152(7).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=15627

   (2) https://bugs.python.org/issue?@action=redirect&bpo=18072

   (3) https://bugs.python.org/issue?@action=redirect&bpo=18193

   (4) https://bugs.python.org/issue?@action=redirect&bpo=18192

   (5) https://bugs.python.org/issue?@action=redirect&bpo=18194

   (6) https://bugs.python.org/issue?@action=redirect&bpo=18058

   (7) https://bugs.python.org/issue?@action=redirect&bpo=19152


File: python.info,  Node: inspect<8>,  Next: ipaddress<5>,  Prev: importlib<9>,  Up: 改進的模組<9>

1.10.4.23 inspect
.................

The *note inspect: 72. module now offers a basic *note command line
interface: efe. to quickly display source code and other information for
modules, classes and functions.  (Contributed by Claudiu Popa and Nick
Coghlan in bpo-18626(1).)

*note unwrap(): eff. makes it easy to unravel wrapper function chains
created by *note functools.wraps(): f00. (and any other API that sets
the ‘__wrapped__’ attribute on a wrapper function).  (Contributed by
Daniel Urban, Aaron Iles and Nick Coghlan in bpo-13266(2).)

As part of the implementation of the new *note enum: 4c. module, the
*note inspect: 72. module now has substantially better support for
custom ‘__dir__’ methods and dynamic class attributes provided through
metaclasses.  (Contributed by Ethan Furman in bpo-18929(3) and
bpo-19030(4).)

*note getfullargspec(): 6dd. and ‘getargspec()’ now use the *note
signature(): 6dc. API. This allows them to support a much broader range
of callables, including those with ‘__signature__’ attributes, those
with metadata provided by argument clinic, *note functools.partial():
356. objects and more.  Note that, unlike *note signature(): 6dc, these
functions still ignore ‘__wrapped__’ attributes, and report the already
bound first argument for bound methods, so it is still necessary to
update your code to use *note signature(): 6dc. directly if those
features are desired.  (Contributed by Yury Selivanov in bpo-17481(5).)

*note signature(): 6dc. now supports duck types of CPython functions,
which adds support for functions compiled with Cython.  (Contributed by
Stefan Behnel and Yury Selivanov in bpo-17159(6).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=18626

   (2) https://bugs.python.org/issue?@action=redirect&bpo=13266

   (3) https://bugs.python.org/issue?@action=redirect&bpo=18929

   (4) https://bugs.python.org/issue?@action=redirect&bpo=19030

   (5) https://bugs.python.org/issue?@action=redirect&bpo=17481

   (6) https://bugs.python.org/issue?@action=redirect&bpo=17159


File: python.info,  Node: ipaddress<5>,  Next: logging<6>,  Prev: inspect<8>,  Up: 改進的模組<9>

1.10.4.24 ipaddress
...................

*note ipaddress: 74. was added to the standard library in Python 3.3 as
a *note provisional API: aa6.  With the release of Python 3.4, this
qualification has been removed: *note ipaddress: 74. is now considered a
stable API, covered by the normal standard library requirements to
maintain backwards compatibility.

A new *note is_global: f02. property is ‘True’ if an address is globally
routeable.  (Contributed by Peter Moody in bpo-17400(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=17400


File: python.info,  Node: logging<6>,  Next: marshal<2>,  Prev: ipaddress<5>,  Up: 改進的模組<9>

1.10.4.25 logging
.................

The *note TimedRotatingFileHandler: f04. has a new 'atTime' parameter
that can be used to specify the time of day when rollover should happen.
(Contributed by Ronald Oussoren in bpo-9556(1).)

*note SocketHandler: f05. and *note DatagramHandler: f06. now support
Unix domain sockets (by setting 'port' to ‘None’).  (Contributed by
Vinay Sajip in commit ce46195b56a9.)

*note fileConfig(): af5. now accepts a *note
configparser.RawConfigParser: f07. subclass instance for the 'fname'
parameter.  This facilitates using a configuration file when logging
configuration is just a part of the overall application configuration,
or where the application modifies the configuration before passing it to
*note fileConfig(): af5.  (Contributed by Vinay Sajip in bpo-16110(2).)

Logging configuration data received from a socket via the *note
logging.config.listen(): f08. function can now be validated before being
processed by supplying a verification function as the argument to the
new 'verify' keyword argument.  (Contributed by Vinay Sajip in
bpo-15452(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=9556

   (2) https://bugs.python.org/issue?@action=redirect&bpo=16110

   (3) https://bugs.python.org/issue?@action=redirect&bpo=15452


File: python.info,  Node: marshal<2>,  Next: mmap<3>,  Prev: logging<6>,  Up: 改進的模組<9>

1.10.4.26 marshal
.................

The default *note marshal: 80. version has been bumped to 3.  The code
implementing the new version restores the Python2 behavior of recording
only one copy of interned strings and preserving the interning on
deserialization, and extends this "one copy" ability to any object type
(including handling recursive references).  This reduces both the size
of ‘.pyc’ files and the amount of memory a module occupies in memory
when it is loaded from a ‘.pyc’ (or ‘.pyo’) file.  (Contributed by
Kristján Valur Jónsson in bpo-16475(1), with additional speedups by
Antoine Pitrou in bpo-19219(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16475

   (2) https://bugs.python.org/issue?@action=redirect&bpo=19219


File: python.info,  Node: mmap<3>,  Next: multiprocessing<7>,  Prev: marshal<2>,  Up: 改進的模組<9>

1.10.4.27 mmap
..............

mmap objects are now *note weakly referenceable: eae.  (Contributed by
Valerie Lambert in bpo-4885(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=4885


File: python.info,  Node: multiprocessing<7>,  Next: operator<3>,  Prev: mmap<3>,  Up: 改進的模組<9>

1.10.4.28 multiprocessing
.........................

On Unix two new *note start methods: 2aa, ‘spawn’ and ‘forkserver’, have
been added for starting processes using *note multiprocessing: 86.
These make the mixing of processes with threads more robust, and the
‘spawn’ method matches the semantics that multiprocessing has always
used on Windows.  New function *note get_all_start_methods(): f0c.
reports all start methods available on the platform, *note
get_start_method(): f0d. reports the current start method, and *note
set_start_method(): 2a9. sets the start method.  (Contributed by Richard
Oudkerk in bpo-8713(1).)

*note multiprocessing: 86. also now has the concept of a ‘context’,
which determines how child processes are created.  New function *note
get_context(): 2a8. returns a context that uses a specified start
method.  It has the same API as the *note multiprocessing: 86. module
itself, so you can use it to create *note Pool: f0e.s and other objects
that will operate within that context.  This allows a framework and an
application or different parts of the same application to use
multiprocessing without interfering with each other.  (Contributed by
Richard Oudkerk in bpo-18999(2).)

Except when using the old 'fork' start method, child processes no longer
inherit unneeded handles/file descriptors from their parents (part of
bpo-8713(3)).

*note multiprocessing: 86. now relies on *note runpy: ac. (which
implements the ‘-m’ switch) to initialise ‘__main__’ appropriately in
child processes when using the ‘spawn’ or ‘forkserver’ start methods.
This resolves some edge cases where combining multiprocessing, the ‘-m’
command line switch, and explicit relative imports could cause obscure
failures in child processes.  (Contributed by Nick Coghlan in
bpo-19946(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=8713

   (2) https://bugs.python.org/issue?@action=redirect&bpo=18999

   (3) https://bugs.python.org/issue?@action=redirect&bpo=8713

   (4) https://bugs.python.org/issue?@action=redirect&bpo=19946


File: python.info,  Node: operator<3>,  Next: os<11>,  Prev: multiprocessing<7>,  Up: 改進的模組<9>

1.10.4.29 operator
..................

New function *note length_hint(): f10. provides an implementation of the
specification for how the *note __length_hint__(): eaf. special method
should be used, as part of the PEP 424(1) formal specification of this
language feature.  (Contributed by Armin Ronacher in bpo-16148(2).)

There is now a pure-python version of the *note operator: 8f. module
available for reference and for use by alternate implementations of
Python.  (Contributed by Zachary Ware in bpo-16694(3).)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0424/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=16148

   (3) https://bugs.python.org/issue?@action=redirect&bpo=16694


File: python.info,  Node: os<11>,  Next: pdb<6>,  Prev: operator<3>,  Up: 改進的模組<9>

1.10.4.30 os
............

There are new functions to get and set the *note inheritable flag: e9d.
of a file descriptor (*note os.get_inheritable(): e9e, *note
os.set_inheritable(): e9f.) or a Windows handle (*note
os.get_handle_inheritable(): ea0, *note os.set_handle_inheritable():
ea1.).

New function *note cpu_count(): 1a8. reports the number of CPUs
available on the platform on which Python is running (or ‘None’ if the
count can't be determined).  The *note multiprocessing.cpu_count(): f12.
function is now implemented in terms of this function).  (Contributed by
Trent Nelson, Yogesh Chaudhari, Victor Stinner, and Charles-François
Natali in bpo-17914(1).)

*note os.path.samestat(): f13. is now available on the Windows platform
(and the *note os.path.samefile(): f14. implementation is now shared
between Unix and Windows).  (Contributed by Brian Curtin in
bpo-11939(2).)

*note os.path.ismount(): 9b6. now recognizes volumes mounted below a
drive root on Windows.  (Contributed by Tim Golden in bpo-9035(3).)

*note os.open(): d38. supports two new flags on platforms that provide
them, *note O_PATH: f15. (un-opened file descriptor), and *note
O_TMPFILE: f16. (unnamed temporary file; as of 3.4.0 release available
only on Linux systems with a kernel version of 3.11 or newer that have
uapi headers).  (Contributed by Christian Heimes in bpo-18673(4) and
Benjamin Peterson, respectively.)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=17914

   (2) https://bugs.python.org/issue?@action=redirect&bpo=11939

   (3) https://bugs.python.org/issue?@action=redirect&bpo=9035

   (4) https://bugs.python.org/issue?@action=redirect&bpo=18673


File: python.info,  Node: pdb<6>,  Next: pickle<4>,  Prev: os<11>,  Up: 改進的模組<9>

1.10.4.31 pdb
.............

*note pdb: 94. has been enhanced to handle generators, *note yield: 971,
and ‘yield from’ in a more useful fashion.  This is especially helpful
when debugging *note asyncio: 8. based programs.  (Contributed by Andrew
Svetlov and Xavier de Gaye in bpo-16596(1).)

The ‘print’ command has been removed from *note pdb: 94, restoring
access to the Python *note print(): f18. function from the pdb command
line.  Python2's ‘pdb’ did not have a ‘print’ command; instead, entering
‘print’ executed the ‘print’ statement.  In Python3 ‘print’ was
mistakenly made an alias for the pdb *note p: f19. command.  ‘p’,
however, prints the ‘repr’ of its argument, not the ‘str’ like the
Python2 ‘print’ command did.  Worse, the Python3 ‘pdb print’ command
shadowed the Python3 ‘print’ function, making it inaccessible at the
‘pdb’ prompt.  (Contributed by Connor Osborn in bpo-18764(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16596

   (2) https://bugs.python.org/issue?@action=redirect&bpo=18764


File: python.info,  Node: pickle<4>,  Next: plistlib<2>,  Prev: pdb<6>,  Up: 改進的模組<9>

1.10.4.32 pickle
................

*note pickle: 95. now supports (but does not use by default) a new
pickle protocol, protocol 4.  This new protocol addresses a number of
issues that were present in previous protocols, such as the
serialization of nested classes, very large strings and containers, and
classes whose ‘__new__()’ method takes keyword-only arguments.  It also
provides some efficiency improvements.

也參考
......

PEP 3154(1) - Pickle protocol 4

     由 Antoine Pitrou 撰寫 PEP、Alexandre Vassalotti 實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3154/


File: python.info,  Node: plistlib<2>,  Next: poplib<3>,  Prev: pickle<4>,  Up: 改進的模組<9>

1.10.4.33 plistlib
..................

*note plistlib: 99. now has an API that is similar to the standard
pattern for stdlib serialization protocols, with new *note load(): 8f3,
*note dump(): 8f5, *note loads(): 8f4, and *note dumps(): 8f6.
functions.  (The older API is now deprecated.)  In addition to the
already supported XML plist format (*note FMT_XML: f1c.), it also now
supports the binary plist format (*note FMT_BINARY: f1d.).  (Contributed
by Ronald Oussoren and others in bpo-14455(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=14455


File: python.info,  Node: poplib<3>,  Next: pprint<4>,  Prev: plistlib<2>,  Up: 改進的模組<9>

1.10.4.34 poplib
................

Two new methods have been added to *note poplib: 9a.: *note capa(): f1f,
which returns the list of capabilities advertised by the POP server, and
*note stls(): f20, which switches a clear-text POP3 session into an
encrypted POP3 session if the POP server supports it.  (Contributed by
Lorenzo Catucci in bpo-4473(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=4473


File: python.info,  Node: pprint<4>,  Next: pty,  Prev: poplib<3>,  Up: 改進的模組<9>

1.10.4.35 pprint
................

The *note pprint: 9c. module's *note PrettyPrinter: f22. class and its
*note pformat(): f23, and *note pprint(): 7cc. functions have a new
option, 'compact', that controls how the output is formatted.  Currently
setting 'compact' to ‘True’ means that sequences will be printed with as
many sequence elements as will fit within 'width' on each (indented)
line.  (Contributed by Serhiy Storchaka in bpo-19132(1).)

Long strings are now wrapped using Python's normal line continuation
syntax.  (Contributed by Antoine Pitrou in bpo-17150(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=19132

   (2) https://bugs.python.org/issue?@action=redirect&bpo=17150


File: python.info,  Node: pty,  Next: pydoc<4>,  Prev: pprint<4>,  Up: 改進的模組<9>

1.10.4.36 pty
.............

*note pty.spawn(): f25. now returns the status value from *note
os.waitpid(): d40. on the child process, instead of ‘None’.
(Contributed by Gregory P. Smith.)


File: python.info,  Node: pydoc<4>,  Next: re<8>,  Prev: pty,  Up: 改進的模組<9>

1.10.4.37 pydoc
...............

The *note pydoc: a3. module is now based directly on the *note
inspect.signature(): 6dc. introspection API, allowing it to provide
signature information for a wider variety of callable objects.  This
change also means that ‘__wrapped__’ attributes are now taken into
account when displaying help information.  (Contributed by Larry
Hastings in bpo-19674(1).)

The *note pydoc: a3. module no longer displays the ‘self’ parameter for
already bound methods.  Instead, it aims to always display the exact
current signature of the supplied callable.  (Contributed by Larry
Hastings in bpo-20710(2).)

In addition to the changes that have been made to *note pydoc: a3.
directly, its handling of custom ‘__dir__’ methods and various
descriptor behaviours has also been improved substantially by the
underlying changes in the *note inspect: 72. module.

As the *note help(): 87c. builtin is based on *note pydoc: a3, the above
changes also affect the behaviour of *note help(): 87c.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=19674

   (2) https://bugs.python.org/issue?@action=redirect&bpo=20710


File: python.info,  Node: re<8>,  Next: resource,  Prev: pydoc<4>,  Up: 改進的模組<9>

1.10.4.38 re
............

New *note fullmatch(): f28. function and ‘regex.fullmatch()’ method
anchor the pattern at both ends of the string to match.  This provides a
way to be explicit about the goal of the match, which avoids a class of
subtle bugs where ‘$’ characters get lost during code changes or the
addition of alternatives to an existing regular expression.
(Contributed by Matthew Barnett in bpo-16203(1).)

The repr of *note regex objects: f29. now includes the pattern and the
flags; the repr of *note match objects: f2a. now includes the start,
end, and the part of the string that matched.  (Contributed by Hugo
Lopes Tavares and Serhiy Storchaka in bpo-13592(2) and bpo-17087(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16203

   (2) https://bugs.python.org/issue?@action=redirect&bpo=13592

   (3) https://bugs.python.org/issue?@action=redirect&bpo=17087


File: python.info,  Node: resource,  Next: select,  Prev: re<8>,  Up: 改進的模組<9>

1.10.4.39 resource
..................

New *note prlimit(): f2c. function, available on Linux platforms with a
kernel version of 2.6.36 or later and glibc of 2.13 or later, provides
the ability to query or set the resource limits for processes other than
the one making the call.  (Contributed by Christian Heimes in
bpo-16595(1).)

On Linux kernel version 2.6.36 or later, there are also some new Linux
specific constants: *note RLIMIT_MSGQUEUE: f2d, *note RLIMIT_NICE: f2e,
*note RLIMIT_RTPRIO: f2f, *note RLIMIT_RTTIME: f30, and *note
RLIMIT_SIGPENDING: f31.  (Contributed by Christian Heimes in
bpo-19324(2).)

On FreeBSD version 9 and later, there some new FreeBSD specific
constants: *note RLIMIT_SBSIZE: f32, *note RLIMIT_SWAP: f33, and *note
RLIMIT_NPTS: f34.  (Contributed by Claudiu Popa in bpo-19343(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16595

   (2) https://bugs.python.org/issue?@action=redirect&bpo=19324

   (3) https://bugs.python.org/issue?@action=redirect&bpo=19343


File: python.info,  Node: select,  Next: shelve<2>,  Prev: resource,  Up: 改進的模組<9>

1.10.4.40 select
................

*note epoll: f36. objects now support the context management protocol.
When used in a *note with: 577. statement, the *note close(): f37.
method will be called automatically at the end of the block.
(Contributed by Serhiy Storchaka in bpo-16488(1).)

*note devpoll: f38. objects now have *note fileno(): f39. and *note
close(): f3a. methods, as well as a new attribute *note closed: f3b.
(Contributed by Victor Stinner in bpo-18794(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16488

   (2) https://bugs.python.org/issue?@action=redirect&bpo=18794


File: python.info,  Node: shelve<2>,  Next: shutil<6>,  Prev: select,  Up: 改進的模組<9>

1.10.4.41 shelve
................

*note Shelf: f3d. instances may now be used in *note with: 577.
statements, and will be automatically closed at the end of the ‘with’
block.  (Contributed by Filip Gruszczyński in bpo-13896(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=13896


File: python.info,  Node: shutil<6>,  Next: smtpd<3>,  Prev: shelve<2>,  Up: 改進的模組<9>

1.10.4.42 shutil
................

*note copyfile(): 9fc. now raises a specific *note Error: f3f. subclass,
*note SameFileError: f40, when the source and destination are the same
file, which allows an application to take appropriate action on this
specific error.  (Contributed by Atsuo Ishimoto and Hynek Schlawack in
bpo-1492704(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1492704


File: python.info,  Node: smtpd<3>,  Next: smtplib<3>,  Prev: shutil<6>,  Up: 改進的模組<9>

1.10.4.43 smtpd
...............

The ‘SMTPServer’ and ‘SMTPChannel’ classes now accept a 'map' keyword
argument which, if specified, is passed in to ‘asynchat.async_chat’ as
its 'map' argument.  This allows an application to avoid affecting the
global socket map.  (Contributed by Vinay Sajip in bpo-11959(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=11959


File: python.info,  Node: smtplib<3>,  Next: socket<9>,  Prev: smtpd<3>,  Up: 改進的模組<9>

1.10.4.44 smtplib
.................

*note SMTPException: f43. is now a subclass of *note OSError: 350, which
allows both socket level errors and SMTP protocol level errors to be
caught in one try/except statement by code that only cares whether or
not an error occurred.  (Contributed by Ned Jackson Lovely in
bpo-2118(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=2118


File: python.info,  Node: socket<9>,  Next: sqlite3<9>,  Prev: smtplib<3>,  Up: 改進的模組<9>

1.10.4.45 socket
................

The socket module now supports the *note CAN_BCM: f45. protocol on
platforms that support it.  (Contributed by Brian Thorne in
bpo-15359(1).)

Socket objects have new methods to get or set their *note inheritable
flag: e9d, *note get_inheritable(): ea2. and *note set_inheritable():
ea3.

The ‘socket.AF_*’ and ‘socket.SOCK_*’ constants are now enumeration
values using the new *note enum: 4c. module.  This allows meaningful
names to be printed during debugging, instead of integer "magic
numbers".

The *note AF_LINK: f46. constant is now available on BSD and OSX.

*note inet_pton(): 906. and *note inet_ntop(): f47. are now supported on
Windows.  (Contributed by Atsuo Ishimoto in bpo-7171(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=15359

   (2) https://bugs.python.org/issue?@action=redirect&bpo=7171


File: python.info,  Node: sqlite3<9>,  Next: ssl<10>,  Prev: socket<9>,  Up: 改進的模組<9>

1.10.4.46 sqlite3
.................

A new boolean parameter to the *note connect(): 288. function, 'uri',
can be used to indicate that the 'database' parameter is a ‘uri’ (see
the SQLite URI documentation(1)).  (Contributed by poq in bpo-13773(2).)

   ---------- Footnotes ----------

   (1) https://www.sqlite.org/uri.html

   (2) https://bugs.python.org/issue?@action=redirect&bpo=13773


File: python.info,  Node: ssl<10>,  Next: stat,  Prev: sqlite3<9>,  Up: 改進的模組<9>

1.10.4.47 ssl
.............

*note PROTOCOL_TLSv1_1: f4a. and *note PROTOCOL_TLSv1_2: f4b. (TLSv1.1
and TLSv1.2 support) have been added; support for these protocols is
only available if Python is linked with OpenSSL 1.0.1 or later.
(Contributed by Michele Orrù and Antoine Pitrou in bpo-16692(1).)  New
function *note create_default_context(): 13a. provides a standard way to
obtain an *note SSLContext: 276. whose settings are intended to be a
reasonable balance between compatibility and security.  These settings
are more stringent than the defaults provided by the *note SSLContext:
276. constructor, and may be adjusted in the future, without prior
deprecation, if best-practice security requirements change.  The new
recommended best practice for using stdlib libraries that support SSL is
to use *note create_default_context(): 13a. to obtain an *note
SSLContext: 276. object, modify it if needed, and then pass it as the
'context' argument of the appropriate stdlib API. (Contributed by
Christian Heimes in bpo-19689(2).)

*note SSLContext: 276. method *note load_verify_locations(): e8f.
accepts a new optional argument 'cadata', which can be used to provide
PEM or DER encoded certificates directly via strings or bytes,
respectively.  (Contributed by Christian Heimes in bpo-18138(3).)

New function *note get_default_verify_paths(): f4c. returns a named
tuple of the paths and environment variables that the *note
set_default_verify_paths(): f4d. method uses to set OpenSSL's default
‘cafile’ and ‘capath’.  This can be an aid in debugging default
verification issues.  (Contributed by Christian Heimes in bpo-18143(4).)

*note SSLContext: 276. has a new method, *note cert_store_stats(): f4e,
that reports the number of loaded ‘X.509’ certs, ‘X.509 CA’ certs, and
certificate revocation lists (‘crl’s), as well as a *note
get_ca_certs(): f4f. method that returns a list of the loaded ‘CA’
certificates.  (Contributed by Christian Heimes in bpo-18147(5).)

If OpenSSL 0.9.8 or later is available, *note SSLContext: 276. has a new
attribute *note verify_flags: f50. that can be used to control the
certificate verification process by setting it to some combination of
the new constants *note VERIFY_DEFAULT: f51, *note
VERIFY_CRL_CHECK_LEAF: f52, *note VERIFY_CRL_CHECK_CHAIN: f53, or *note
VERIFY_X509_STRICT: 13c.  OpenSSL does not do any CRL verification by
default.  (Contributed by Christien Heimes in bpo-8813(6).)

New *note SSLContext: 276. method *note load_default_certs(): f54. loads
a set of default "certificate authority" (CA) certificates from default
locations, which vary according to the platform.  It can be used to load
both TLS web server authentication certificates (‘purpose=’*note
SERVER_AUTH: f55.) for a client to use to verify a server, and
certificates for a server to use in verifying client certificates
(‘purpose=’*note CLIENT_AUTH: f56.).  (Contributed by Christian Heimes
in bpo-19292(7).)  Two new windows-only functions, *note
enum_certificates(): f57. and *note enum_crls(): f58. provide the
ability to retrieve certificates, certificate information, and CRLs from
the Windows cert store.  (Contributed by Christian Heimes in
bpo-17134(8).)  Support for server-side SNI (Server Name Indication)
using the new *note ssl.SSLContext.set_servername_callback(): f59.
method.  (Contributed by Daniel Black in bpo-8109(9).)

The dictionary returned by *note SSLSocket.getpeercert(): f5a. contains
additional ‘X509v3’ extension items: ‘crlDistributionPoints’,
‘calIssuers’, and ‘OCSP’ URIs.  (Contributed by Christian Heimes in
bpo-18379(10).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16692

   (2) https://bugs.python.org/issue?@action=redirect&bpo=19689

   (3) https://bugs.python.org/issue?@action=redirect&bpo=18138

   (4) https://bugs.python.org/issue?@action=redirect&bpo=18143

   (5) https://bugs.python.org/issue?@action=redirect&bpo=18147

   (6) https://bugs.python.org/issue?@action=redirect&bpo=8813

   (7) https://bugs.python.org/issue?@action=redirect&bpo=19292

   (8) https://bugs.python.org/issue?@action=redirect&bpo=17134

   (9) https://bugs.python.org/issue?@action=redirect&bpo=8109

   (10) https://bugs.python.org/issue?@action=redirect&bpo=18379


File: python.info,  Node: stat,  Next: struct<2>,  Prev: ssl<10>,  Up: 改進的模組<9>

1.10.4.48 stat
..............

The *note stat: bc. module is now backed by a C implementation in
‘_stat’.  A C implementation is required as most of the values aren't
standardized and are platform-dependent.  (Contributed by Christian
Heimes in bpo-11016(1).)

The module supports new *note ST_MODE: f5c. flags, *note S_IFDOOR: f5d,
*note S_IFPORT: f5e, and *note S_IFWHT: f5f.  (Contributed by Christian
Hiemes in bpo-11016(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=11016

   (2) https://bugs.python.org/issue?@action=redirect&bpo=11016


File: python.info,  Node: struct<2>,  Next: subprocess<5>,  Prev: stat,  Up: 改進的模組<9>

1.10.4.49 struct
................

New function *note iter_unpack: f61. and a new *note
struct.Struct.iter_unpack(): f62. method on compiled formats provide
streamed unpacking of a buffer containing repeated instances of a given
format of data.  (Contributed by Antoine Pitrou in bpo-17804(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=17804


File: python.info,  Node: subprocess<5>,  Next: sunau<2>,  Prev: struct<2>,  Up: 改進的模組<9>

1.10.4.50 subprocess
....................

*note check_output(): f64. now accepts an 'input' argument that can be
used to provide the contents of ‘stdin’ for the command that is run.
(Contributed by Zack Weinberg in bpo-16624(1).)

‘getstatus()’ and *note getstatusoutput(): f65. now work on Windows.
This change was actually inadvertently made in 3.3.4.  (Contributed by
Tim Golden in bpo-10197(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16624

   (2) https://bugs.python.org/issue?@action=redirect&bpo=10197


File: python.info,  Node: sunau<2>,  Next: sys<11>,  Prev: subprocess<5>,  Up: 改進的模組<9>

1.10.4.51 sunau
...............

The ‘getparams()’ method now returns a namedtuple rather than a plain
tuple.  (Contributed by Claudiu Popa in bpo-18901(1).)

‘sunau.open()’ now supports the context management protocol: when used
in a *note with: 577. block, the ‘close’ method of the returned object
will be called automatically at the end of the block.  (Contributed by
Serhiy Storchaka in bpo-18878(2).)

‘AU_write.setsampwidth()’ now supports 24 bit samples, thus adding
support for writing 24 sample using the module.  (Contributed by Serhiy
Storchaka in bpo-19261(3).)

The ‘writeframesraw()’ and ‘writeframes()’ methods now accept any *note
bytes-like object: cd4.  (Contributed by Serhiy Storchaka in
bpo-8311(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=18901

   (2) https://bugs.python.org/issue?@action=redirect&bpo=18878

   (3) https://bugs.python.org/issue?@action=redirect&bpo=19261

   (4) https://bugs.python.org/issue?@action=redirect&bpo=8311


File: python.info,  Node: sys<11>,  Next: tarfile<7>,  Prev: sunau<2>,  Up: 改進的模組<9>

1.10.4.52 sys
.............

New function *note sys.getallocatedblocks(): f68. returns the current
number of blocks allocated by the interpreter.  (In CPython with the
default ‘--with-pymalloc’ setting, this is allocations made through the
*note PyObject_Malloc(): c0f. API.) This can be useful for tracking
memory leaks, especially if automated via a test suite.  (Contributed by
Antoine Pitrou in bpo-13390(1).)

When the Python interpreter starts in *note interactive mode: f69, it
checks for an *note __interactivehook__: f6a. attribute on the *note
sys: c3. module.  If the attribute exists, its value is called with no
arguments just before interactive mode is started.  The check is made
after the *note PYTHONSTARTUP: f6b. file is read, so it can be set
there.  The *note site: b5. module *note sets it: f6c. to a function
that enables tab completion and history saving (in ‘~/.python-history’)
if the platform supports *note readline: a8.  If you do not want this
(new) behavior, you can override it in *note PYTHONSTARTUP: f6b, *note
sitecustomize: b6, or *note usercustomize: f7. by deleting this
attribute from *note sys: c3. (or setting it to some other callable).
(Contributed by Éric Araujo and Antoine Pitrou in bpo-5845(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=13390

   (2) https://bugs.python.org/issue?@action=redirect&bpo=5845


File: python.info,  Node: tarfile<7>,  Next: textwrap,  Prev: sys<11>,  Up: 改進的模組<9>

1.10.4.53 tarfile
.................

The *note tarfile: c8. module now supports a simple *note Command-Line
Interface: f6e. when called as a script directly or via ‘-m’.  This can
be used to create and extract tarfile archives.  (Contributed by Berker
Peksag in bpo-13477(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=13477


File: python.info,  Node: textwrap,  Next: threading<7>,  Prev: tarfile<7>,  Up: 改進的模組<9>

1.10.4.54 textwrap
..................

The *note TextWrapper: f70. class has two new attributes/constructor
arguments: *note max_lines: f71, which limits the number of lines in the
output, and *note placeholder: f72, which is a string that will appear
at the end of the output if it has been truncated because of
'max_lines'.  Building on these capabilities, a new convenience function
*note shorten(): f73. collapses all of the whitespace in the input to
single spaces and produces a single line of a given 'width' that ends
with the 'placeholder' (by default, ‘[...]’).  (Contributed by Antoine
Pitrou and Serhiy Storchaka in bpo-18585(1) and bpo-18725(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=18585

   (2) https://bugs.python.org/issue?@action=redirect&bpo=18725


File: python.info,  Node: threading<7>,  Next: traceback<6>,  Prev: textwrap,  Up: 改進的模組<9>

1.10.4.55 threading
...................

The *note Thread: 8f0. object representing the main thread can be
obtained from the new *note main_thread(): f75. function.  In normal
conditions this will be the thread from which the Python interpreter was
started.  (Contributed by Andrew Svetlov in bpo-18882(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=18882


File: python.info,  Node: traceback<6>,  Next: types<6>,  Prev: threading<7>,  Up: 改進的模組<9>

1.10.4.56 traceback
...................

A new *note traceback.clear_frames(): f77. function takes a traceback
object and clears the local variables in all of the frames it
references, reducing the amount of memory consumed.  (Contributed by
Andrew Kuchling in bpo-1565525(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1565525


File: python.info,  Node: types<6>,  Next: urllib<3>,  Prev: traceback<6>,  Up: 改進的模組<9>

1.10.4.57 types
...............

A new *note DynamicClassAttribute(): 5d0. descriptor provides a way to
define an attribute that acts normally when looked up through an
instance object, but which is routed to the 'class' ‘__getattr__’ when
looked up through the class.  This allows one to have properties active
on a class, and have virtual attributes on the class with the same name
(see ‘Enum’ for an example).  (Contributed by Ethan Furman in
bpo-19030(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=19030


File: python.info,  Node: urllib<3>,  Next: unittest<9>,  Prev: types<6>,  Up: 改進的模組<9>

1.10.4.58 urllib
................

*note urllib.request: f4. now supports ‘data:’ URLs via the *note
DataHandler: f7a. class.  (Contributed by Mathias Panzenböck in
bpo-16423(1).)

The http method that will be used by a *note Request: f7b. class can now
be specified by setting a *note method: f7c. class attribute on the
subclass.  (Contributed by Jason R Coombs in bpo-18978(2).)

*note Request: f7b. objects are now reusable: if the *note full_url:
f7d. or *note data: f7e. attributes are modified, all relevant internal
properties are updated.  This means, for example, that it is now
possible to use the same *note Request: f7b. object in more than one
*note OpenerDirector.open(): f7f. call with different 'data' arguments,
or to modify a *note Request: f7b.'s ‘url’ rather than recomputing it
from scratch.  There is also a new *note remove_header(): f80. method
that can be used to remove headers from a *note Request: f7b.
(Contributed by Alexey Kachayev in bpo-16464(3), Daniel Wozniak in
bpo-17485(4), and Damien Brecht and Senthil Kumaran in bpo-17272(5).)

*note HTTPError: f81. objects now have a *note headers: f82. attribute
that provides access to the HTTP response headers associated with the
error.  (Contributed by Berker Peksag in bpo-15701(6).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16423

   (2) https://bugs.python.org/issue?@action=redirect&bpo=18978

   (3) https://bugs.python.org/issue?@action=redirect&bpo=16464

   (4) https://bugs.python.org/issue?@action=redirect&bpo=17485

   (5) https://bugs.python.org/issue?@action=redirect&bpo=17272

   (6) https://bugs.python.org/issue?@action=redirect&bpo=15701


File: python.info,  Node: unittest<9>,  Next: venv<7>,  Prev: urllib<3>,  Up: 改進的模組<9>

1.10.4.59 unittest
..................

The *note TestCase: 3f4. class has a new method, *note subTest(): f84,
that produces a context manager whose *note with: 577. block becomes a
"sub-test".  This context manager allows a test method to dynamically
generate subtests by, say, calling the ‘subTest’ context manager inside
a loop.  A single test method can thereby produce an indefinite number
of separately identified and separately counted tests, all of which will
run even if one or more of them fail.  For example:

     class NumbersTest(unittest.TestCase):
         def test_even(self):
             for i in range(6):
                 with self.subTest(i=i):
                     self.assertEqual(i % 2, 0)

will result in six subtests, each identified in the unittest verbose
output with a label consisting of the variable name ‘i’ and a particular
value for that variable (‘i=0’, ‘i=1’, etc).  See *note Distinguishing
test iterations using subtests: f85. for the full version of this
example.  (Contributed by Antoine Pitrou in bpo-16997(1).)

*note unittest.main(): f86. now accepts an iterable of test names for
'defaultTest', where previously it only accepted a single test name as a
string.  (Contributed by Jyrki Pulliainen in bpo-15132(2).)

If *note SkipTest: f87. is raised during test discovery (that is, at the
module level in the test file), it is now reported as a skip instead of
an error.  (Contributed by Zach Ware in bpo-16935(3).)

*note discover(): f88. now sorts the discovered files to provide
consistent test ordering.  (Contributed by Martin Melin and Jeff Ramnani
in bpo-16709(4).)

*note TestSuite: d9a. now drops references to tests as soon as the test
has been run, if the test is successful.  On Python interpreters that do
garbage collection, this allows the tests to be garbage collected if
nothing else is holding a reference to the test.  It is possible to
override this behavior by creating a *note TestSuite: d9a. subclass that
defines a custom ‘_removeTestAtIndex’ method.  (Contributed by Tom
Wardill, Matt McClure, and Andrew Svetlov in bpo-11798(5).)

A new test assertion context-manager, *note assertLogs(): 7fd, will
ensure that a given block of code emits a log message using the *note
logging: 7b. module.  By default the message can come from any logger
and have a priority of ‘INFO’ or higher, but both the logger name and an
alternative minimum logging level may be specified.  The object returned
by the context manager can be queried for the *note LogRecord: f89.s
and/or formatted messages that were logged.  (Contributed by Antoine
Pitrou in bpo-18937(6).)

Test discovery now works with namespace packages (Contributed by Claudiu
Popa in bpo-17457(7).)

*note unittest.mock: f0. objects now inspect their specification
signatures when matching calls, which means an argument can now be
matched by either position or name, instead of only by position.
(Contributed by Antoine Pitrou in bpo-17015(8).)

‘mock_open()’ objects now have ‘readline’ and ‘readlines’ methods.
(Contributed by Toshio Kuratomi in bpo-17467(9).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16997

   (2) https://bugs.python.org/issue?@action=redirect&bpo=15132

   (3) https://bugs.python.org/issue?@action=redirect&bpo=16935

   (4) https://bugs.python.org/issue?@action=redirect&bpo=16709

   (5) https://bugs.python.org/issue?@action=redirect&bpo=11798

   (6) https://bugs.python.org/issue?@action=redirect&bpo=18937

   (7) https://bugs.python.org/issue?@action=redirect&bpo=17457

   (8) https://bugs.python.org/issue?@action=redirect&bpo=17015

   (9) https://bugs.python.org/issue?@action=redirect&bpo=17467


File: python.info,  Node: venv<7>,  Next: wave<2>,  Prev: unittest<9>,  Up: 改進的模組<9>

1.10.4.60 venv
..............

*note venv: f9. now includes activation scripts for the ‘csh’ and ‘fish’
shells.  (Contributed by Andrew Svetlov in bpo-15417(1).)

*note EnvBuilder: 24f. and the *note create(): 250. convenience function
take a new keyword argument 'with_pip', which defaults to ‘False’, that
controls whether or not *note EnvBuilder: 24f. ensures that ‘pip’ is
installed in the virtual environment.  (Contributed by Nick Coghlan in
bpo-19552(2) as part of the PEP 453(3) implementation.)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=15417

   (2) https://bugs.python.org/issue?@action=redirect&bpo=19552

   (3) https://peps.python.org/pep-0453/


File: python.info,  Node: wave<2>,  Next: weakref<2>,  Prev: venv<7>,  Up: 改進的模組<9>

1.10.4.61 wave
..............

The ‘getparams()’ method now returns a namedtuple rather than a plain
tuple.  (Contributed by Claudiu Popa in bpo-17487(1).)

*note wave.open(): 8ef. now supports the context management protocol.
(Contributed by Claudiu Popa in bpo-17616(2).)

*note wave: fb. can now *note write output to unseekable files: f8c.
(Contributed by David Jones, Guilherme Polo, and Serhiy Storchaka in
bpo-5202(3).)

The *note writeframesraw(): f8d. and *note writeframes(): f8e. methods
now accept any *note bytes-like object: cd4.  (Contributed by Serhiy
Storchaka in bpo-8311(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=17487

   (2) https://bugs.python.org/issue?@action=redirect&bpo=17616

   (3) https://bugs.python.org/issue?@action=redirect&bpo=5202

   (4) https://bugs.python.org/issue?@action=redirect&bpo=8311


File: python.info,  Node: weakref<2>,  Next: xml etree<2>,  Prev: wave<2>,  Up: 改進的模組<9>

1.10.4.62 weakref
.................

New *note WeakMethod: f90. class simulates weak references to bound
methods.  (Contributed by Antoine Pitrou in bpo-14631(1).)

New *note finalize: a1f. class makes it possible to register a callback
to be invoked when an object is garbage collected, without needing to
carefully manage the lifecycle of the weak reference itself.
(Contributed by Richard Oudkerk in bpo-15528(2).)

The callback, if any, associated with a *note ref: f91. is now exposed
via the *note __callback__: f92. attribute.  (Contributed by Mark
Dickinson in bpo-17643(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=14631

   (2) https://bugs.python.org/issue?@action=redirect&bpo=15528

   (3) https://bugs.python.org/issue?@action=redirect&bpo=17643


File: python.info,  Node: xml etree<2>,  Next: zipfile<5>,  Prev: weakref<2>,  Up: 改進的模組<9>

1.10.4.63 xml.etree
...................

A new parser, *note XMLPullParser: f94, allows a non-blocking
applications to parse XML documents.  An example can be seen at *note
Pull API for non-blocking parsing: f95.  (Contributed by Antoine Pitrou
in bpo-17741(1).)

The *note xml.etree.ElementTree: 10c. *note tostring(): f96. and *note
tostringlist(): f97. functions, and the *note ElementTree: 8f2. *note
write(): f98. method, now have a 'short_empty_elements' *note
keyword-only parameter: 285. providing control over whether elements
with no content are written in abbreviated (‘<tag />’) or expanded
(‘<tag></tag>’) form.  (Contributed by Ariel Poliak and Serhiy Storchaka
in bpo-14377(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=17741

   (2) https://bugs.python.org/issue?@action=redirect&bpo=14377


File: python.info,  Node: zipfile<5>,  Prev: xml etree<2>,  Up: 改進的模組<9>

1.10.4.64 zipfile
.................

The *note writepy(): f9a. method of the *note PyZipFile: f9b. class has
a new 'filterfunc' option that can be used to control which directories
and files are added to the archive.  For example, this could be used to
exclude test files from the archive.  (Contributed by Christian Tismer
in bpo-19274(1).)

The 'allowZip64' parameter to *note ZipFile: 669. and ‘PyZipfile’ is now
‘True’ by default.  (Contributed by William Mallard in bpo-17201(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=19274

   (2) https://bugs.python.org/issue?@action=redirect&bpo=17201


File: python.info,  Node: CPython 實作變更,  Next: 已棄用<11>,  Prev: 改進的模組<9>,  Up: Python 3 4 有什麼新功能<2>

1.10.5 CPython 實作變更
-----------------------

* Menu:

* PEP 445; Customization of CPython Memory Allocators: PEP 445 Customization of CPython Memory Allocators.
* PEP 442; Safe Object Finalization: PEP 442 Safe Object Finalization.
* PEP 456; Secure and Interchangeable Hash Algorithm: PEP 456 Secure and Interchangeable Hash Algorithm.
* PEP 436; Argument Clinic: PEP 436 Argument Clinic.
* Other Build and C API Changes::
* Other Improvements: Other Improvements<2>.
* 顯著最佳化::


File: python.info,  Node: PEP 445 Customization of CPython Memory Allocators,  Next: PEP 442 Safe Object Finalization,  Up: CPython 實作變更

1.10.5.1 PEP 445: Customization of CPython Memory Allocators
............................................................

PEP 445(1) adds new C level interfaces to customize memory allocation in
the CPython interpreter.

也參考
......

PEP 445(2) - Add new APIs to customize Python memory allocators

     由 Victor Stinner 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0445/

   (2) https://peps.python.org/pep-0445/


File: python.info,  Node: PEP 442 Safe Object Finalization,  Next: PEP 456 Secure and Interchangeable Hash Algorithm,  Prev: PEP 445 Customization of CPython Memory Allocators,  Up: CPython 實作變更

1.10.5.2 PEP 442: Safe Object Finalization
..........................................

PEP 442(1) removes the current limitations and quirks of object
finalization in CPython.  With it, objects with ‘__del__()’ methods, as
well as generators with *note finally: 96e. clauses, can be finalized
when they are part of a reference cycle.

As part of this change, module globals are no longer forcibly set to
*note None: 61b. during interpreter shutdown in most cases, instead
relying on the normal operation of the cyclic garbage collector.  This
avoids a whole class of interpreter-shutdown-time errors, usually
involving ‘__del__’ methods, that have plagued Python since the cyclic
GC was first introduced.

也參考
......

PEP 442(2) - Safe object finalization

     由 Antoine Pitrou 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0442/

   (2) https://peps.python.org/pep-0442/


File: python.info,  Node: PEP 456 Secure and Interchangeable Hash Algorithm,  Next: PEP 436 Argument Clinic,  Prev: PEP 442 Safe Object Finalization,  Up: CPython 實作變更

1.10.5.3 PEP 456: Secure and Interchangeable Hash Algorithm
...........................................................

PEP 456(1) follows up on earlier security fix work done on Python's hash
algorithm to address certain DOS attacks to which public facing APIs
backed by dictionary lookups may be subject.  (See bpo-14621(2) for the
start of the current round of improvements.)  The PEP unifies CPython's
hash code to make it easier for a packager to substitute a different
hash algorithm, and switches Python's default implementation to a
SipHash implementation on platforms that have a 64 bit data type.  Any
performance differences in comparison with the older FNV algorithm are
trivial.

The PEP adds additional fields to the *note sys.hash_info: fa0. named
tuple to describe the hash algorithm in use by the currently executing
binary.  Otherwise, the PEP does not alter any existing CPython APIs.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0456/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=14621


File: python.info,  Node: PEP 436 Argument Clinic,  Next: Other Build and C API Changes,  Prev: PEP 456 Secure and Interchangeable Hash Algorithm,  Up: CPython 實作變更

1.10.5.4 PEP 436: Argument Clinic
.................................

"Argument Clinic" ( PEP 436(1)) is now part of the CPython build process
and can be used to simplify the process of defining and maintaining
accurate signatures for builtins and standard library extension modules
implemented in C.

Some standard library extension modules have been converted to use
Argument Clinic in Python 3.4, and *note pydoc: a3. and *note inspect:
72. have been updated accordingly.

It is expected that signature metadata for programmatic introspection
will be added to additional callables implemented in C as part of Python
3.4 maintenance releases.

     備註: The Argument Clinic PEP is not fully up to date with the
     state of the implementation.  This has been deemed acceptable by
     the release manager and core development team in this case, as
     Argument Clinic will not be made available as a public API for
     third party use in Python 3.4.

也參考
......

PEP 436(2) - The Argument Clinic DSL

     由 Larry Hastings 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0436/

   (2) https://peps.python.org/pep-0436/


File: python.info,  Node: Other Build and C API Changes,  Next: Other Improvements<2>,  Prev: PEP 436 Argument Clinic,  Up: CPython 實作變更

1.10.5.5 Other Build and C API Changes
......................................

   * The new *note PyType_GetSlot(): 840. function has been added to the
     stable ABI, allowing retrieval of function pointers from named type
     slots when using the limited API. (Contributed by Martin von Löwis
     in bpo-17162(1).)

   * The new ‘Py_SetStandardStreamEncoding()’ pre-initialization API
     allows applications embedding the CPython interpreter to reliably
     force a particular encoding and error handler for the standard
     streams.  (Contributed by Bastien Montagne and Nick Coghlan in
     bpo-16129(2).)

   * Most Python C APIs that don't mutate string arguments are now
     correctly marked as accepting ‘const char *’ rather than ‘char *’.
     (Contributed by Serhiy Storchaka in bpo-1772673(3).)

   * A new shell version of ‘python-config’ can be used even when a
     python interpreter is not available (for example, in cross
     compilation scenarios).

   * *note PyUnicode_FromFormat(): 33f. now supports width and precision
     specifications for ‘%s’, ‘%A’, ‘%U’, ‘%V’, ‘%S’, and ‘%R’.
     (Contributed by Ysj Ray and Victor Stinner in bpo-7330(4).)

   * New function *note PyStructSequence_InitType2(): fa3. supplements
     the existing *note PyStructSequence_InitType(): fa4. function.  The
     difference is that it returns ‘0’ on success and ‘-1’ on failure.

   * The CPython source can now be compiled using the address sanity
     checking features of recent versions of GCC and clang: the false
     alarms in the small object allocator have been silenced.
     (Contributed by Dhiru Kholia in bpo-18596(5).)

   * The Windows build now uses Address Space Layout Randomization(6)
     and Data Execution Prevention(7).  (Contributed by Christian Heimes
     in bpo-16632(8).)

   * New function *note PyObject_LengthHint(): fa5. is the C API
     equivalent of *note operator.length_hint(): f10.  (Contributed by
     Armin Ronacher in bpo-16148(9).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=17162

   (2) https://bugs.python.org/issue?@action=redirect&bpo=16129

   (3) https://bugs.python.org/issue?@action=redirect&bpo=1772673

   (4) https://bugs.python.org/issue?@action=redirect&bpo=7330

   (5) https://bugs.python.org/issue?@action=redirect&bpo=18596

   (6) https://en.wikipedia.org/wiki/Address_space_layout_randomization

   (7) https://en.wikipedia.org/wiki/Data_Execution_Prevention

   (8) https://bugs.python.org/issue?@action=redirect&bpo=16632

   (9) https://bugs.python.org/issue?@action=redirect&bpo=16148


File: python.info,  Node: Other Improvements<2>,  Next: 顯著最佳化,  Prev: Other Build and C API Changes,  Up: CPython 實作變更

1.10.5.6 Other Improvements
...........................

   * The *note python: fa8. command has a new *note option: fa9, ‘-I’,
     which causes it to run in "isolated mode", which means that *note
     sys.path: 37f. contains neither the script's directory nor the
     user's ‘site-packages’ directory, and all ‘PYTHON*’ environment
     variables are ignored (it implies both ‘-s’ and ‘-E’).  Other
     restrictions may also be applied in the future, with the goal being
     to isolate the execution of a script from the user's environment.
     This is appropriate, for example, when Python is used to run a
     system script.  On most POSIX systems it can and should be used in
     the ‘#!’ line of system scripts.  (Contributed by Christian Heimes
     in bpo-16499(1).)

   * Tab-completion is now enabled by default in the interactive
     interpreter on systems that support *note readline: a8.  History is
     also enabled by default, and is written to (and read from) the file
     ‘~/.python-history’.  (Contributed by Antoine Pitrou and Éric
     Araujo in bpo-5845(2).)

   * Invoking the Python interpreter with ‘--version’ now outputs the
     version to standard output instead of standard error
     (bpo-18338(3)).  Similar changes were made to *note argparse: 5.
     (bpo-18920(4)) and other modules that have script-like invocation
     capabilities (bpo-18922(5)).

   * The CPython Windows installer now adds ‘.py’ to the ‘PATHEXT’
     variable when extensions are registered, allowing users to run a
     python script at the windows command prompt by just typing its name
     without the ‘.py’ extension.  (Contributed by Paul Moore in
     bpo-18569(6).)

   * A new ‘make’ target coverage-report(7) will build python, run the
     test suite, and generate an HTML coverage report for the C codebase
     using ‘gcov’ and lcov(8).

   * The ‘-R’ option to the *note python regression test suite: faa. now
     also checks for memory allocation leaks, using *note
     sys.getallocatedblocks(): f68.  (Contributed by Antoine Pitrou in
     bpo-13390(9).)

   * ‘python -m’ now works with namespace packages.

   * The *note stat: bc. module is now implemented in C, which means it
     gets the values for its constants from the C header files, instead
     of having the values hard-coded in the python module as was
     previously the case.

   * Loading multiple python modules from a single OS module (‘.so’,
     ‘.dll’) now works correctly (previously it silently returned the
     first python module in the file).  (Contributed by Václav Šmilauer
     in bpo-16421(10).)

   * A new opcode, ‘LOAD_CLASSDEREF’, has been added to fix a bug in the
     loading of free variables in class bodies that could be triggered
     by certain uses of *note __prepare__: c05.  (Contributed by
     Benjamin Peterson in bpo-17853(11).)

   * A number of MemoryError-related crashes were identified and fixed
     by Victor Stinner using his PEP 445(12)-based ‘pyfailmalloc’ tool
     (bpo-18408(13), bpo-18520(14)).

   * The ‘pyvenv’ command now accepts a ‘--copies’ option to use copies
     rather than symlinks even on systems where symlinks are the
     default.  (Contributed by Vinay Sajip in bpo-18807(15).)

   * The ‘pyvenv’ command also accepts a ‘--without-pip’ option to
     suppress the otherwise-automatic bootstrapping of pip into the
     virtual environment.  (Contributed by Nick Coghlan in bpo-19552(16)
     as part of the PEP 453(17) implementation.)

   * The encoding name is now optional in the value set for the *note
     PYTHONIOENCODING: fab. environment variable.  This makes it
     possible to set just the error handler, without changing the
     default encoding.  (Contributed by Serhiy Storchaka in
     bpo-18818(18).)

   * The *note bz2: f, *note lzma: 7e, and *note gzip: 5d. module ‘open’
     functions now support ‘x’ (exclusive creation) mode.  (Contributed
     by Tim Heaney and Vajrasky Kok in bpo-19201(19), bpo-19222(20), and
     bpo-19223(21).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16499

   (2) https://bugs.python.org/issue?@action=redirect&bpo=5845

   (3) https://bugs.python.org/issue?@action=redirect&bpo=18338

   (4) https://bugs.python.org/issue?@action=redirect&bpo=18920

   (5) https://bugs.python.org/issue?@action=redirect&bpo=18922

   (6) https://bugs.python.org/issue?@action=redirect&bpo=18569

   (7) 
https://devguide.python.org/coverage/#measuring-coverage-of-c-code-with-gcov-and-lcov

   (8) https://ltp.sourceforge.net/coverage/lcov.php

   (9) https://bugs.python.org/issue?@action=redirect&bpo=13390

   (10) https://bugs.python.org/issue?@action=redirect&bpo=16421

   (11) https://bugs.python.org/issue?@action=redirect&bpo=17853

   (12) https://peps.python.org/pep-0445/

   (13) https://bugs.python.org/issue?@action=redirect&bpo=18408

   (14) https://bugs.python.org/issue?@action=redirect&bpo=18520

   (15) https://bugs.python.org/issue?@action=redirect&bpo=18807

   (16) https://bugs.python.org/issue?@action=redirect&bpo=19552

   (17) https://peps.python.org/pep-0453/

   (18) https://bugs.python.org/issue?@action=redirect&bpo=18818

   (19) https://bugs.python.org/issue?@action=redirect&bpo=19201

   (20) https://bugs.python.org/issue?@action=redirect&bpo=19222

   (21) https://bugs.python.org/issue?@action=redirect&bpo=19223


File: python.info,  Node: 顯著最佳化,  Prev: Other Improvements<2>,  Up: CPython 實作變更

1.10.5.7 顯著最佳化
...................

   * The UTF-32 decoder is now 3x to 4x faster.  (Contributed by Serhiy
     Storchaka in bpo-14625(1).)

   * The cost of hash collisions for sets is now reduced.  Each hash
     table probe now checks a series of consecutive, adjacent key/hash
     pairs before continuing to make random probes through the hash
     table.  This exploits cache locality to make collision resolution
     less expensive.  The collision resolution scheme can be described
     as a hybrid of linear probing and open addressing.  The number of
     additional linear probes defaults to nine.  This can be changed at
     compile-time by defining LINEAR_PROBES to be any value.  Set
     LINEAR_PROBES=0 to turn-off linear probing entirely.  (Contributed
     by Raymond Hettinger in bpo-18771(2).)

   * The interpreter starts about 30% faster.  A couple of measures lead
     to the speedup.  The interpreter loads fewer modules on startup,
     e.g.  the *note re: a7, *note collections: 16. and *note locale:
     7a. modules and their dependencies are no longer imported by
     default.  The marshal module has been improved to load compiled
     Python code faster.  (Contributed by Antoine Pitrou, Christian
     Heimes and Victor Stinner in bpo-19219(3), bpo-19218(4),
     bpo-19209(5), bpo-19205(6) and bpo-9548(7).)

   * *note bz2.BZ2File: 80b. is now as fast or faster than the Python2
     version for most cases.  *note lzma.LZMAFile: fad. has also been
     optimized.  (Contributed by Serhiy Storchaka and Nadeem Vawda in
     bpo-16034(8).)

   * *note random.getrandbits(): fae. is 20%-40% faster for small
     integers (the most common use case).  (Contributed by Serhiy
     Storchaka in bpo-16674(9).)

   * By taking advantage of the new storage format for strings, pickling
     of strings is now significantly faster.  (Contributed by Victor
     Stinner and Antoine Pitrou in bpo-15596(10).)

   * A performance issue in ‘io.FileIO.readall()’ has been solved.  This
     particularly affects Windows, and significantly speeds up the case
     of piping significant amounts of data through *note subprocess: c1.
     (Contributed by Richard Oudkerk in bpo-15758(11).)

   * *note html.escape(): faf. is now 10x faster.  (Contributed by Matt
     Bryant in bpo-18020(12).)

   * On Windows, the native ‘VirtualAlloc’ is now used instead of the
     CRT ‘malloc’ in ‘obmalloc’.  Artificial benchmarks show about a 3%
     memory savings.

   * *note os.urandom(): 4c7. now uses a lazily opened persistent file
     descriptor so as to avoid using many file descriptors when run in
     parallel from multiple threads.  (Contributed by Antoine Pitrou in
     bpo-18756(13).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=14625

   (2) https://bugs.python.org/issue?@action=redirect&bpo=18771

   (3) https://bugs.python.org/issue?@action=redirect&bpo=19219

   (4) https://bugs.python.org/issue?@action=redirect&bpo=19218

   (5) https://bugs.python.org/issue?@action=redirect&bpo=19209

   (6) https://bugs.python.org/issue?@action=redirect&bpo=19205

   (7) https://bugs.python.org/issue?@action=redirect&bpo=9548

   (8) https://bugs.python.org/issue?@action=redirect&bpo=16034

   (9) https://bugs.python.org/issue?@action=redirect&bpo=16674

   (10) https://bugs.python.org/issue?@action=redirect&bpo=15596

   (11) https://bugs.python.org/issue?@action=redirect&bpo=15758

   (12) https://bugs.python.org/issue?@action=redirect&bpo=18020

   (13) https://bugs.python.org/issue?@action=redirect&bpo=18756


File: python.info,  Node: 已棄用<11>,  Next: 已移除<9>,  Prev: CPython 實作變更,  Up: Python 3 4 有什麼新功能<2>

1.10.6 已棄用
-------------

This section covers various APIs and other features that have been
deprecated in Python 3.4, and will be removed in Python 3.5 or later.
In most (but not all) cases, using the deprecated APIs will produce a
*note DeprecationWarning: 18b. when the interpreter is run with
deprecation warnings enabled (for example, by using ‘-Wd’).

* Menu:

* Deprecations in the Python API::
* 已棄用功能::


File: python.info,  Node: Deprecations in the Python API,  Next: 已棄用功能,  Up: 已棄用<11>

1.10.6.1 Deprecations in the Python API
.......................................

   * As mentioned in *note PEP 451; A ModuleSpec Type for the Import
     System: e7d, a number of *note importlib: 6b. methods and functions
     are deprecated: ‘importlib.find_loader()’ is replaced by *note
     importlib.util.find_spec(): 2af.;
     ‘importlib.machinery.PathFinder.find_module()’ is replaced by *note
     importlib.machinery.PathFinder.find_spec(): fb2.;
     ‘importlib.abc.MetaPathFinder.find_module()’ is replaced by *note
     importlib.abc.MetaPathFinder.find_spec(): 80d.;
     ‘importlib.abc.PathEntryFinder.find_loader()’ and ‘find_module()’
     are replaced by *note importlib.abc.PathEntryFinder.find_spec():
     811.; all of the ‘XXXLoader’ ABC ‘load_module’ methods
     (‘importlib.abc.Loader.load_module()’,
     ‘importlib.abc.InspectLoader.load_module()’,
     ‘importlib.abc.FileLoader.load_module()’,
     ‘importlib.abc.SourceLoader.load_module()’) should no longer be
     implemented, instead loaders should implement an ‘exec_module’
     method (*note importlib.abc.Loader.exec_module(): 80f, *note
     importlib.abc.InspectLoader.exec_module(): fb3. *note
     importlib.abc.SourceLoader.exec_module(): fb4.) and let the import
     system take care of the rest; and
     ‘importlib.abc.Loader.module_repr()’,
     ‘importlib.util.module_for_loader()’,
     ‘importlib.util.set_loader()’, and ‘importlib.util.set_package()’
     are no longer needed because their functions are now handled
     automatically by the import system.

   * The ‘imp’ module is pending deprecation.  To keep compatibility
     with Python 2/3 code bases, the module's removal is currently not
     scheduled.

   * The ‘formatter’ module is pending deprecation and is slated for
     removal in Python 3.6.

   * ‘MD5’ as the default 'digestmod' for the *note hmac.new(): a42.
     function is deprecated.  Python 3.6 will require an explicit digest
     name or constructor as 'digestmod' argument.

   * The internal ‘Netrc’ class in the *note ftplib: 54. module has been
     documented as deprecated in its docstring for quite some time.  It
     now emits a *note DeprecationWarning: 18b. and will be removed
     completely in Python 3.5.

   * The undocumented 'endtime' argument to *note
     subprocess.Popen.wait(): c8b. should not have been exposed and is
     hopefully not in use; it is deprecated and will mostly likely be
     removed in Python 3.5.

   * The 'strict' argument of *note HTMLParser: 81a. is deprecated.

   * The *note plistlib: 99. ‘readPlist()’, ‘writePlist()’,
     ‘readPlistFromBytes()’, and ‘writePlistToBytes()’ functions are
     deprecated in favor of the corresponding new functions *note
     load(): 8f3, *note dump(): 8f5, *note loads(): 8f4, and *note
     dumps(): 8f6.  ‘Data()’ is deprecated in favor of just using the
     *note bytes: 1a5. constructor.

   * The *note sysconfig: c5. key ‘SO’ is deprecated, it has been
     replaced by ‘EXT_SUFFIX’.

   * The ‘U’ mode accepted by various ‘open’ functions is deprecated.
     In Python3 it does not do anything useful, and should be replaced
     by appropriate uses of *note io.TextIOWrapper: 75f. (if needed) and
     its 'newline' argument.

   * The 'parser' argument of *note xml.etree.ElementTree.iterparse():
     258. has been deprecated, as has the 'html' argument of *note
     XMLParser(): 9f7.  To prepare for the removal of the latter, all
     arguments to ‘XMLParser’ should be passed by keyword.


File: python.info,  Node: 已棄用功能,  Prev: Deprecations in the Python API,  Up: 已棄用<11>

1.10.6.2 已棄用功能
...................

   * Running *note IDLE: fb6. with the ‘-n’ flag (no subprocess) is
     deprecated.  However, the feature will not be removed until
     bpo-18823(1) is resolved.

   * The site module adding a "site-python" directory to sys.path, if it
     exists, is deprecated (bpo-19375(2)).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=18823

   (2) https://bugs.python.org/issue?@action=redirect&bpo=19375


File: python.info,  Node: 已移除<9>,  Next: Porting to Python 3 4,  Prev: 已棄用<11>,  Up: Python 3 4 有什麼新功能<2>

1.10.7 已移除
-------------

* Menu:

* Operating Systems No Longer Supported::
* API 與功能的移除::
* 程式碼的清除::


File: python.info,  Node: Operating Systems No Longer Supported,  Next: API 與功能的移除,  Up: 已移除<9>

1.10.7.1 Operating Systems No Longer Supported
..............................................

Support for the following operating systems has been removed from the
source and build tools:

   * OS/2 (bpo-16135(1))。

   * Windows 2000 (changeset e52df05b496a).

   * Windows systems where ‘COMSPEC’ points to ‘command.com’
     (bpo-14470(2)).

   * VMS (bpo-16136(3))。

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16135

   (2) https://bugs.python.org/issue?@action=redirect&bpo=14470

   (3) https://bugs.python.org/issue?@action=redirect&bpo=16136


File: python.info,  Node: API 與功能的移除,  Next: 程式碼的清除,  Prev: Operating Systems No Longer Supported,  Up: 已移除<9>

1.10.7.2 API 與功能的移除
.........................

The following obsolete and previously deprecated APIs and features have
been removed:

   * The unmaintained ‘Misc/TextMate’ and ‘Misc/vim’ directories have
     been removed (see the devguide(1) for suggestions on what to use
     instead).

   * The ‘SO’ makefile macro is removed (it was replaced by the
     ‘SHLIB_SUFFIX’ and ‘EXT_SUFFIX’ macros) (bpo-16754(2)).

   * The ‘PyThreadState.tick_counter’ field has been removed; its value
     has been meaningless since Python 3.2, when the "new GIL" was
     introduced (bpo-19199(3)).

   * ‘PyLoader’ and ‘PyPycLoader’ have been removed from *note
     importlib: 6b.  (Contributed by Taras Lyapun in bpo-15641(4).)

   * The 'strict' argument to *note HTTPConnection: ae4. and *note
     HTTPSConnection: ae5. has been removed.  HTTP 0.9-style "Simple
     Responses" are no longer supported.

   * The deprecated *note urllib.request.Request: f7b. getter and setter
     methods ‘add_data’, ‘has_data’, ‘get_data’, ‘get_type’, ‘get_host’,
     ‘get_selector’, ‘set_proxy’, ‘get_origin_req_host’, and
     ‘is_unverifiable’ have been removed (use direct attribute access
     instead).

   * Support for loading the deprecated ‘TYPE_INT64’ has been removed
     from *note marshal: 80.  (Contributed by Dan Riti in bpo-15480(5).)

   * *note inspect.Signature: 1b3.: positional-only parameters are now
     required to have a valid name.

   * *note object.__format__(): 5c5. no longer accepts non-empty format
     strings, it now raises a *note TypeError: 4dd. instead.  Using a
     non-empty string has been deprecated since Python 3.2.  This change
     has been made to prevent a situation where previously working (but
     incorrect) code would start failing if an object gained a
     __format__ method, which means that your code may now raise a *note
     TypeError: 4dd. if you are using an ‘'s'’ format code with objects
     that do not have a __format__ method that handles it.  See
     bpo-7994(6) for background.

   * ‘difflib.SequenceMatcher.isbjunk()’ and
     ‘difflib.SequenceMatcher.isbpopular()’ were deprecated in 3.2, and
     have now been removed: use ‘x in sm.bjunk’ and ‘x in sm.bpopular’,
     where 'sm' is a *note SequenceMatcher: fba. object (bpo-13248(7)).

   ---------- Footnotes ----------

   (1) https://devguide.python.org

   (2) https://bugs.python.org/issue?@action=redirect&bpo=16754

   (3) https://bugs.python.org/issue?@action=redirect&bpo=19199

   (4) https://bugs.python.org/issue?@action=redirect&bpo=15641

   (5) https://bugs.python.org/issue?@action=redirect&bpo=15480

   (6) https://bugs.python.org/issue?@action=redirect&bpo=7994

   (7) https://bugs.python.org/issue?@action=redirect&bpo=13248


File: python.info,  Node: 程式碼的清除,  Prev: API 與功能的移除,  Up: 已移除<9>

1.10.7.3 程式碼的清除
.....................

   * The unused and undocumented internal ‘Scanner’ class has been
     removed from the *note pydoc: a3. module.

   * The private and effectively unused ‘_gestalt’ module has been
     removed, along with the private *note platform: 98. functions
     ‘_mac_ver_lookup’, ‘_mac_ver_gstalt’, and ‘_bcd2str’, which would
     only have ever been called on badly broken OSX systems (see
     bpo-18393(1)).

   * The hardcoded copies of certain *note stat: bc. constants that were
     included in the *note tarfile: c8. module namespace have been
     removed.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=18393


File: python.info,  Node: Porting to Python 3 4,  Next: 3 4 3 中的變更,  Prev: 已移除<9>,  Up: Python 3 4 有什麼新功能<2>

1.10.8 Porting to Python 3.4
----------------------------

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

* Menu:

* Changes in 'python' Command Behavior: Changes in 'python' Command Behavior<2>.
* Python API 的變更: Python API 的變更<2>.
* C API 中的改動: C API 中的改動<7>.


File: python.info,  Node: Changes in 'python' Command Behavior<2>,  Next: Python API 的變更<2>,  Up: Porting to Python 3 4

1.10.8.1 Changes in 'python' Command Behavior
.............................................

   * In a posix shell, setting the ‘PATH’ environment variable to an
     empty value is equivalent to not setting it at all.  However,
     setting *note PYTHONPATH: fbe. to an empty value was 'not'
     equivalent to not setting it at all: setting *note PYTHONPATH: fbe.
     to an empty value was equivalent to setting it to ‘.’, which leads
     to confusion when reasoning by analogy to how ‘PATH’ works.  The
     behavior now conforms to the posix convention for ‘PATH’.

   * The [X refs, Y blocks] output of a debug (‘--with-pydebug’) build
     of the CPython interpreter is now off by default.  It can be
     re-enabled using the ‘-X showrefcount’ option.  (Contributed by
     Ezio Melotti in bpo-17323(1).)

   * The python command and most stdlib scripts (as well as *note
     argparse: 5.) now output ‘--version’ information to ‘stdout’
     instead of ‘stderr’ (for issue list see *note Other Improvements:
     fa7. above).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=17323


File: python.info,  Node: Python API 的變更<2>,  Next: C API 中的改動<7>,  Prev: Changes in 'python' Command Behavior<2>,  Up: Porting to Python 3 4

1.10.8.2 Python API 的變更
..........................

   * The ABCs defined in *note importlib.abc: 6c. now either raise the
     appropriate exception or return a default value instead of raising
     *note NotImplementedError: 20d. blindly.  This will only affect
     code calling *note super(): 483. and falling through all the way to
     the ABCs.  For compatibility, catch both *note NotImplementedError:
     20d. or the appropriate exception as needed.

   * The module type now initializes the *note __package__: fc0. and
     *note __loader__: fc1. attributes to ‘None’ by default.  To
     determine if these attributes were set in a backwards-compatible
     fashion, use e.g.  ‘getattr(module, '__loader__', None) is not
     None’.  (bpo-17115(1).)

   * ‘importlib.util.module_for_loader()’ now sets ‘__loader__’ and
     ‘__package__’ unconditionally to properly support reloading.  If
     this is not desired then you will need to set these attributes
     manually.  You can use ‘importlib.util.module_to_load()’ for module
     management.

   * Import now resets relevant attributes (e.g.  ‘__name__’,
     ‘__loader__’, ‘__package__’, ‘__file__’, ‘__cached__’)
     unconditionally when reloading.  Note that this restores a pre-3.3
     behavior in that it means a module is re-found when re-loaded
     (bpo-19413(2)).

   * Frozen packages no longer set ‘__path__’ to a list containing the
     package name, they now set it to an empty list.  The previous
     behavior could cause the import system to do the wrong thing on
     submodule imports if there was also a directory with the same name
     as the frozen package.  The correct way to determine if a module is
     a package or not is to use ‘hasattr(module, '__path__')’
     (bpo-18065(3)).

   * Frozen modules no longer define a ‘__file__’ attribute.  It's
     semantically incorrect for frozen modules to set the attribute as
     they are not loaded from any explicit location.  If you must know
     that a module comes from frozen code then you can see if the
     module's ‘__spec__.location’ is set to ‘'frozen'’, check if the
     loader is a subclass of *note importlib.machinery.FrozenImporter:
     fc2, or if Python 2 compatibility is necessary you can use
     ‘imp.is_frozen()’.

   * *note py_compile.compile(): 9c9. now raises *note FileExistsError:
     fc3. if the file path it would write to is a symlink or a
     non-regular file.  This is to act as a warning that import will
     overwrite those files with a regular file regardless of what type
     of file path they were originally.

   * *note importlib.abc.SourceLoader.get_source(): fc4. no longer
     raises *note ImportError: 352. when the source code being loaded
     triggers a *note SyntaxError: 173. or *note UnicodeDecodeError:
     9b7.  As *note ImportError: 352. is meant to be raised only when
     source code cannot be found but it should, it was felt to be
     over-reaching/overloading of that meaning when the source code is
     found but improperly structured.  If you were catching ImportError
     before and wish to continue to ignore syntax or decoding issues,
     catch all three exceptions now.

   * *note functools.update_wrapper(): fc5. and *note functools.wraps():
     f00. now correctly set the ‘__wrapped__’ attribute to the function
     being wrapped, even if that function also had its ‘__wrapped__’
     attribute set.  This means ‘__wrapped__’ attributes now correctly
     link a stack of decorated functions rather than every ‘__wrapped__’
     attribute in the chain referring to the innermost function.
     Introspection libraries that assumed the previous behaviour was
     intentional can use *note inspect.unwrap(): eff. to access the
     first function in the chain that has no ‘__wrapped__’ attribute.

   * *note inspect.getfullargspec(): 6dd. has been reimplemented on top
     of *note inspect.signature(): 6dc. and hence handles a much wider
     variety of callable objects than it did in the past.  It is
     expected that additional builtin and extension module callables
     will gain signature metadata over the course of the Python 3.4
     series.  Code that assumes that *note inspect.getfullargspec():
     6dd. will fail on non-Python callables may need to be adjusted
     accordingly.

   * *note importlib.machinery.PathFinder: fc6. now passes on the
     current working directory to objects in *note sys.path_hooks: fc7.
     for the empty string.  This results in *note
     sys.path_importer_cache: 588. never containing ‘''’, thus iterating
     through *note sys.path_importer_cache: 588. based on *note
     sys.path: 37f. will not find all keys.  A module's ‘__file__’ when
     imported in the current working directory will also now have an
     absolute path, including when using ‘-m’ with the interpreter
     (except for ‘__main__.__file__’ when a script has been executed
     directly using a relative path) (Contributed by Brett Cannon in
     bpo-18416(4)).  is specified on the command-line) (bpo-18416(5)).

   * The removal of the 'strict' argument to *note HTTPConnection: ae4.
     and *note HTTPSConnection: ae5. changes the meaning of the
     remaining arguments if you are specifying them positionally rather
     than by keyword.  If you've been paying attention to deprecation
     warnings your code should already be specifying any additional
     arguments via keywords.

   * Strings between ‘from __future__ import ...’ statements now
     'always' raise a *note SyntaxError: 173.  Previously if there was
     no leading docstring, an interstitial string would sometimes be
     ignored.  This brings CPython into compliance with the language
     spec; Jython and PyPy already were.  (bpo-17434(6)).

   * *note ssl.SSLSocket.getpeercert(): f5a. and *note
     ssl.SSLSocket.do_handshake(): e0f. now raise an *note OSError: 350.
     with ‘ENOTCONN’ when the ‘SSLSocket’ is not connected, instead of
     the previous behavior of raising an *note AttributeError: 2f6.  In
     addition, *note getpeercert(): f5a. will raise a *note ValueError:
     1e7. if the handshake has not yet been done.

   * *note base64.b32decode(): fc8. now raises a *note binascii.Error:
     fc9. when the input string contains non-b32-alphabet characters,
     instead of a *note TypeError: 4dd.  This particular *note
     TypeError: 4dd. was missed when the other *note TypeError: 4dd.s
     were converted.  (Contributed by Serhiy Storchaka in bpo-18011(7).)
     Note: this change was also inadvertently applied in Python 3.3.3.

   * The ‘file’ attribute is now automatically closed when the creating
     ‘cgi.FieldStorage’ instance is garbage collected.  If you were
     pulling the file object out separately from the ‘cgi.FieldStorage’
     instance and not keeping the instance alive, then you should either
     store the entire ‘cgi.FieldStorage’ instance or read the contents
     of the file before the ‘cgi.FieldStorage’ instance is garbage
     collected.

   * Calling ‘read’ or ‘write’ on a closed SSL socket now raises an
     informative *note ValueError: 1e7. rather than the previous more
     mysterious *note AttributeError: 2f6. (bpo-9177(8)).

   * *note slice.indices(): fca. no longer produces an *note
     OverflowError: 825. for huge values.  As a consequence of this fix,
     *note slice.indices(): fca. now raises a *note ValueError: 1e7. if
     given a negative length; previously it returned nonsense values
     (bpo-14794(9)).

   * The *note complex: 2c9. constructor, unlike the *note cmath: 11.
     functions, was incorrectly accepting *note float: 2c8. values if an
     object's ‘__complex__’ special method returned one.  This now
     raises a *note TypeError: 4dd.  (bpo-16290(10).)

   * The *note int: 23c. constructor in 3.2 and 3.3 erroneously accepts
     *note float: 2c8. values for the 'base' parameter.  It is unlikely
     anyone was doing this, but if so, it will now raise a *note
     TypeError: 4dd. (bpo-16772(11)).

   * Defaults for keyword-only arguments are now evaluated 'after'
     defaults for regular keyword arguments, instead of before.
     Hopefully no one wrote any code that depends on the previous buggy
     behavior (bpo-16967(12)).

   * Stale thread states are now cleared after *note fork(): 17b.  This
     may cause some system resources to be released that previously were
     incorrectly kept perpetually alive (for example, database
     connections kept in thread-local storage).  (bpo-17094(13).)

   * Parameter names in ‘__annotations__’ dicts are now mangled
     properly, similarly to *note __kwdefaults__: fcb.  (Contributed by
     Yury Selivanov in bpo-20625(14).)

   * *note hashlib.hash.name: eeb. now always returns the identifier in
     lower case.  Previously some builtin hashes had uppercase names,
     but now that it is a formal public interface the naming has been
     made consistent (bpo-18532(15)).

   * Because *note unittest.TestSuite: d9a. now drops references to
     tests after they are run, test harnesses that reuse a *note
     TestSuite: d9a. to re-run a set of tests may fail.  Test suites
     should not be re-used in this fashion since it means state is
     retained between test runs, breaking the test isolation that *note
     unittest: ef. is designed to provide.  However, if the lack of
     isolation is considered acceptable, the old behavior can be
     restored by creating a *note TestSuite: d9a. subclass that defines
     a ‘_removeTestAtIndex’ method that does nothing (see *note
     TestSuite.__iter__(): fcc.) (bpo-11798(16)).

   * *note unittest: ef. now uses *note argparse: 5. for command line
     parsing.  There are certain invalid command forms that used to work
     that are no longer allowed; in theory this should not cause
     backward compatibility issues since the disallowed command forms
     didn't make any sense and are unlikely to be in use.

   * The *note re.split(): 282, *note re.findall(): fcd, and *note
     re.sub(): 283. functions, and the ‘group()’ and ‘groups()’ methods
     of ‘match’ objects now always return a 'bytes' object when the
     string to be matched is a *note bytes-like object: cd4.  Previously
     the return type matched the input type, so if your code was
     depending on the return value being, say, a ‘bytearray’, you will
     need to change your code.

   * ‘audioop’ functions now raise an error immediately if passed string
     input, instead of failing randomly later on (bpo-16685(17)).

   * The new 'convert_charrefs' argument to *note HTMLParser: 81a.
     currently defaults to ‘False’ for backward compatibility, but will
     eventually be changed to default to ‘True’.  It is recommended that
     you add this keyword, with the appropriate value, to any *note
     HTMLParser: 81a. calls in your code (bpo-13633(18)).

   * Since the 'digestmod' argument to the *note hmac.new(): a42.
     function will in the future have no default, all calls to *note
     hmac.new(): a42. should be changed to explicitly specify a
     'digestmod' (bpo-17276(19)).

   * Calling *note sysconfig.get_config_var(): fce. with the ‘SO’ key,
     or looking ‘SO’ up in the results of a call to *note
     sysconfig.get_config_vars(): fcf. is deprecated.  This key should
     be replaced by ‘EXT_SUFFIX’ or ‘SHLIB_SUFFIX’, depending on the
     context (bpo-19555(20)).

   * Any calls to ‘open’ functions that specify ‘U’ should be modified.
     ‘U’ is ineffective in Python3 and will eventually raise an error if
     used.  Depending on the function, the equivalent of its old Python2
     behavior can be achieved using either a 'newline' argument, or if
     necessary by wrapping the stream in *note TextIOWrapper: 75f. to
     use its 'newline' argument (bpo-15204(21)).

   * If you use ‘pyvenv’ in a script and desire that pip 'not' be
     installed, you must add ‘--without-pip’ to your command invocation.

   * The default behavior of *note json.dump(): ceb. and *note
     json.dumps(): cec. when an indent is specified has changed: it no
     longer produces trailing spaces after the item separating commas at
     the ends of lines.  This will matter only if you have tests that
     are doing white-space-sensitive comparisons of such output
     (bpo-16333(22)).

   * *note doctest: 31. now looks for doctests in extension module
     ‘__doc__’ strings, so if your doctest test discovery includes
     extension modules that have things that look like doctests in them
     you may see test failures you've never seen before when running
     your tests (bpo-3158(23)).

   * The *note collections.abc: 17. module has been slightly refactored
     as part of the Python startup improvements.  As a consequence of
     this, it is no longer the case that importing *note collections:
     16. automatically imports *note collections.abc: 17.  If your
     program depended on the (undocumented) implicit import, you will
     need to add an explicit ‘import collections.abc’ (bpo-20784(24)).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=17115

   (2) https://bugs.python.org/issue?@action=redirect&bpo=19413

   (3) https://bugs.python.org/issue?@action=redirect&bpo=18065

   (4) https://bugs.python.org/issue?@action=redirect&bpo=18416

   (5) https://bugs.python.org/issue?@action=redirect&bpo=18416

   (6) https://bugs.python.org/issue?@action=redirect&bpo=17434

   (7) https://bugs.python.org/issue?@action=redirect&bpo=18011

   (8) https://bugs.python.org/issue?@action=redirect&bpo=9177

   (9) https://bugs.python.org/issue?@action=redirect&bpo=14794

   (10) https://bugs.python.org/issue?@action=redirect&bpo=16290

   (11) https://bugs.python.org/issue?@action=redirect&bpo=16772

   (12) https://bugs.python.org/issue?@action=redirect&bpo=16967

   (13) https://bugs.python.org/issue?@action=redirect&bpo=17094

   (14) https://bugs.python.org/issue?@action=redirect&bpo=20625

   (15) https://bugs.python.org/issue?@action=redirect&bpo=18532

   (16) https://bugs.python.org/issue?@action=redirect&bpo=11798

   (17) https://bugs.python.org/issue?@action=redirect&bpo=16685

   (18) https://bugs.python.org/issue?@action=redirect&bpo=13633

   (19) https://bugs.python.org/issue?@action=redirect&bpo=17276

   (20) https://bugs.python.org/issue?@action=redirect&bpo=19555

   (21) https://bugs.python.org/issue?@action=redirect&bpo=15204

   (22) https://bugs.python.org/issue?@action=redirect&bpo=16333

   (23) https://bugs.python.org/issue?@action=redirect&bpo=3158

   (24) https://bugs.python.org/issue?@action=redirect&bpo=20784


File: python.info,  Node: C API 中的改動<7>,  Prev: Python API 的變更<2>,  Up: Porting to Python 3 4

1.10.8.3 C API 中的改動
.......................

   * *note PyEval_EvalFrameEx(): fd1, *note PyObject_Repr(): fd2, and
     *note PyObject_Str(): fd3, along with some other internal C APIs,
     now include a debugging assertion that ensures they are not used in
     situations where they may silently discard a currently active
     exception.  In cases where discarding the active exception is
     expected and desired (for example, because it has already been
     saved locally with *note PyErr_Fetch(): 3bb. or is being
     deliberately replaced with a different exception), an explicit
     *note PyErr_Clear(): fd4. call will be needed to avoid triggering
     the assertion when invoking these operations (directly or
     indirectly) and running against a version of Python that is
     compiled with assertions enabled.

   * *note PyErr_SetImportError(): ce5. now sets *note TypeError: 4dd.
     when its 'msg' argument is not set.  Previously only ‘NULL’ was
     returned with no exception set.

   * The result of the *note PyOS_ReadlineFunctionPointer: 52c. callback
     must now be a string allocated by *note PyMem_RawMalloc(): 323. or
     *note PyMem_RawRealloc(): 325, or ‘NULL’ if an error occurred,
     instead of a string allocated by *note PyMem_Malloc(): c0d. or
     *note PyMem_Realloc(): fd5. (bpo-16742(1))

   * *note PyThread_set_key_value(): 3d0. now always set the value.  In
     Python 3.3, the function did nothing if the key already exists (if
     the current value is a non-‘NULL’ pointer).

   * The ‘f_tstate’ (thread state) field of the *note PyFrameObject:
     72d. structure has been removed to fix a bug: see bpo-14432(2) for
     the rationale.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16742

   (2) https://bugs.python.org/issue?@action=redirect&bpo=14432


File: python.info,  Node: 3 4 3 中的變更,  Prev: Porting to Python 3 4,  Up: Python 3 4 有什麼新功能<2>

1.10.9 3.4.3 中的變更
---------------------

* Menu:

* PEP 476; Enabling certificate verification by default for stdlib http clients: PEP 476 Enabling certificate verification by default for stdlib http clients.


File: python.info,  Node: PEP 476 Enabling certificate verification by default for stdlib http clients,  Up: 3 4 3 中的變更

1.10.9.1 PEP 476: Enabling certificate verification by default for stdlib http clients
......................................................................................

*note http.client: 65. and modules which use it, such as *note
urllib.request: f4. and *note xmlrpc.client: 114, will now verify that
the server presents a certificate which is signed by a CA in the
platform trust store and whose hostname matches the hostname being
requested by default, significantly improving security for many
applications.

For applications which require the old previous behavior, they can pass
an alternate context:

     import urllib.request
     import ssl

     # This disables all verification
     context = ssl._create_unverified_context()

     # This allows using a specific certificate for the host, which doesn't need
     # to be in the trust store
     context = ssl.create_default_context(cafile="/path/to/file.crt")

     urllib.request.urlopen("https://invalid-cert", context=context)


File: python.info,  Node: Python 3 3 有什麼新功能,  Next: Python 3 2 有什麼新功能,  Prev: Python 3 4 有什麼新功能<2>,  Up: Python 有什麼新功能？

1.11 Python 3.3 有什麼新功能
============================

This article explains the new features in Python 3.3, compared to 3.2.
Python 3.3 was released on September 29, 2012.  For full details, see
the changelog(1).

也參考
......

PEP 398(2) - Python 3.3 發佈時間表

* Menu:

* Summary: Summary -- Release highlights<5>. Release highlights
* PEP 405：虛擬環境::
* PEP 420; Implicit Namespace Packages: PEP 420 Implicit Namespace Packages.
* PEP 3118; New memoryview implementation and buffer protocol documentation: PEP 3118 New memoryview implementation and buffer protocol documentation.
* PEP 393; Flexible String Representation: PEP 393 Flexible String Representation.
* PEP 397：適用於 Windows 的 Python 啟動器::
* PEP 3151; Reworking the OS and IO exception hierarchy: PEP 3151 Reworking the OS and IO exception hierarchy.
* PEP 380; Syntax for Delegating to a Subgenerator: PEP 380 Syntax for Delegating to a Subgenerator.
* PEP 409; Suppressing exception context: PEP 409 Suppressing exception context.
* PEP 414; Explicit Unicode literals: PEP 414 Explicit Unicode literals.
* PEP 3155; Qualified name for classes and functions: PEP 3155 Qualified name for classes and functions.
* PEP 412; Key-Sharing Dictionary: PEP 412 Key-Sharing Dictionary.
* PEP 362：函式簽名物件::
* PEP 421：新增 sys.implementation: PEP 421：新增 sys implementation.
* 使用 importlib 作為 import 的實作::
* 其他語言更動: 其他語言更動<10>.
* A Finer-Grained Import Lock::
* 內建函式和型別::
* 新模組: 新模組<6>.
* 改進的模組: 改進的模組<10>.
* 最佳化: 最佳化<9>.
* 建置和 C API 更改::
* 已棄用: 已棄用<12>.
* 移植到 Python 3.3: 移植到 Python 3 3.

   ---------- Footnotes ----------

   (1) https://docs.python.org/3.3/whatsnew/changelog.html

   (2) https://peps.python.org/pep-0398/


File: python.info,  Node: Summary -- Release highlights<5>,  Next: PEP 405：虛擬環境,  Up: Python 3 3 有什麼新功能

1.11.1 Summary - Release highlights
-----------------------------------

新增語法特性：

   * New ‘yield from’ expression for *note generator delegation: fdc.

   * *note str: 3f2. 物件再次接受 ‘u'unicode'’ 語法。

新的函式庫模組：

   * *note faulthandler: 4e. (helps debugging low-level crashes)

   * *note ipaddress: 74. (high-level objects representing IP addresses
     and masks)

   * *note lzma: 7e. (compress data using the XZ / LZMA algorithm)

   * *note unittest.mock: f0. (replace parts of your system under test
     with mock objects)

   * *note venv: f9. (Python *note virtual environments: fdd, as in the
     popular ‘virtualenv’ package)

新的內建功能：

   * 重新設計 *note I/O 例外層次結構: fde.。

實作改進：

   * Rewritten *note import machinery: fdf. based on *note importlib:
     6b.

   * More compact *note unicode strings: fe0.

   * More compact *note attribute dictionaries: fe1.

Significantly Improved Library Modules:

   * C Accelerator for the *note decimal: fe2. module.

   * Better unicode handling in the *note email: fe3. module (*note
     provisional: fe4.).

安全性改進：

   * 預設情況下，雜湊隨機化處於打開狀態。

Please read on for a comprehensive list of user-facing changes.


File: python.info,  Node: PEP 405：虛擬環境,  Next: PEP 420 Implicit Namespace Packages,  Prev: Summary -- Release highlights<5>,  Up: Python 3 3 有什麼新功能

1.11.2 PEP 405：虛擬環境
------------------------

Virtual environments help create separate Python setups while sharing a
system-wide base install, for ease of maintenance.  Virtual environments
have their own set of private site packages (i.e.  locally installed
libraries), and are optionally segregated from the system-wide site
packages.  Their concept and implementation are inspired by the popular
‘virtualenv’ third-party package, but benefit from tighter integration
with the interpreter core.

This PEP adds the *note venv: f9. module for programmatic access, and
the ‘pyvenv’ script for command-line access and administration.  The
Python interpreter checks for a ‘pyvenv.cfg’, file whose existence
signals the base of a virtual environment's directory tree.

也參考
......

PEP 405(1) - Python 虛擬環境

     由 Carl Meyer 撰寫 PEP；由 Carl Meyer 與 Vinay Sajip 實作

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0405/


File: python.info,  Node: PEP 420 Implicit Namespace Packages,  Next: PEP 3118 New memoryview implementation and buffer protocol documentation,  Prev: PEP 405：虛擬環境,  Up: Python 3 3 有什麼新功能

1.11.3 PEP 420: Implicit Namespace Packages
-------------------------------------------

Native support for package directories that don't require ‘__init__.py’
marker files and can automatically span multiple path segments (inspired
by various third party approaches to namespace packages, as described in
PEP 420(1))

也參考
......

PEP 420(2) - Implicit Namespace Packages

     由 Eric V. Smith 撰寫 PEP；由 Eric V. Smith 和 Barry Warsaw 實施

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0420/

   (2) https://peps.python.org/pep-0420/


File: python.info,  Node: PEP 3118 New memoryview implementation and buffer protocol documentation,  Next: PEP 393 Flexible String Representation,  Prev: PEP 420 Implicit Namespace Packages,  Up: Python 3 3 有什麼新功能

1.11.4 PEP 3118: New memoryview implementation and buffer protocol documentation
--------------------------------------------------------------------------------

The implementation of PEP 3118(1) has been significantly improved.

The new memoryview implementation comprehensively fixes all ownership
and lifetime issues of dynamically allocated fields in the Py_buffer
struct that led to multiple crash reports.  Additionally, several
functions that crashed or returned incorrect results for non-contiguous
or multi-dimensional input have been fixed.

The memoryview object now has a PEP-3118 compliant getbufferproc() that
checks the consumer's request type.  Many new features have been added,
most of them work in full generality for non-contiguous arrays and
arrays with suboffsets.

The documentation has been updated, clearly spelling out
responsibilities for both exporters and consumers.  Buffer request flags
are grouped into basic and compound flags.  The memory layout of
non-contiguous and multi-dimensional NumPy-style arrays is explained.

* Menu:

* 功能::
* API 變更::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3118/


File: python.info,  Node: 功能,  Next: API 變更,  Up: PEP 3118 New memoryview implementation and buffer protocol documentation

1.11.4.1 功能
.............

   * All native single character format specifiers in struct module
     syntax (optionally prefixed with '@') are now supported.

   * With some restrictions, the cast() method allows changing of format
     and shape of C-contiguous arrays.

   * Multi-dimensional list representations are supported for any array
     type.

   * Multi-dimensional comparisons are supported for any array type.

   * One-dimensional memoryviews of hashable (read-only) types with
     formats B, b or c are now hashable.  (Contributed by Antoine Pitrou
     in bpo-13411(1).)

   * Arbitrary slicing of any 1-D arrays type is supported.  For
     example, it is now possible to reverse a memoryview in 'O'(1) by
     using a negative step.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=13411


File: python.info,  Node: API 變更,  Prev: 功能,  Up: PEP 3118 New memoryview implementation and buffer protocol documentation

1.11.4.2 API 變更
.................

   * The maximum number of dimensions is officially limited to 64.

   * The representation of empty shape, strides and suboffsets is now an
     empty tuple instead of ‘None’.

   * Accessing a memoryview element with format 'B' (unsigned bytes) now
     returns an integer (in accordance with the struct module syntax).
     For returning a bytes object the view must be cast to 'c' first.

   * memoryview comparisons now use the logical structure of the
     operands and compare all array elements by value.  All format
     strings in struct module syntax are supported.  Views with
     unrecognised format strings are still permitted, but will always
     compare as unequal, regardless of view contents.

   * For further changes see *note Build and C API Changes: feb. and
     *note Porting C code: fec.

（由 Stefan Krah 在 bpo-10181(1) 中貢獻。）

也參考
......

PEP 3118(2) - 修訂緩衝協定

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=10181

   (2) https://peps.python.org/pep-3118/


File: python.info,  Node: PEP 393 Flexible String Representation,  Next: PEP 397：適用於 Windows 的 Python 啟動器,  Prev: PEP 3118 New memoryview implementation and buffer protocol documentation,  Up: Python 3 3 有什麼新功能

1.11.5 PEP 393: Flexible String Representation
----------------------------------------------

The Unicode string type is changed to support multiple internal
representations, depending on the character with the largest Unicode
ordinal (1, 2, or 4 bytes) in the represented string.  This allows a
space-efficient representation in common cases, but gives access to full
UCS-4 on all systems.  For compatibility with existing APIs, several
representations may exist in parallel; over time, this compatibility
should be phased out.

On the Python side, there should be no downside to this change.

On the C API side, PEP 393(1) is fully backward compatible.  The legacy
API should remain available at least five years.  Applications using the
legacy API will not fully benefit of the memory reduction, or - worse -
may use a bit more memory, because Python may have to maintain two
versions of each string (in the legacy format and in the new efficient
storage).

* Menu:

* 功能性::
* 性能和資源使用情況::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0393/


File: python.info,  Node: 功能性,  Next: 性能和資源使用情況,  Up: PEP 393 Flexible String Representation

1.11.5.1 功能性
...............

PEP 393(1) 引入的更改如下：

   * Python now always supports the full range of Unicode code points,
     including non-BMP ones (i.e.  from ‘U+0000’ to ‘U+10FFFF’).  The
     distinction between narrow and wide builds no longer exists and
     Python now behaves like a wide build, even under Windows.

   * With the death of narrow builds, the problems specific to narrow
     builds have also been fixed, for example:

        * *note len(): 5d4. now always returns 1 for non-BMP characters,
          so ‘len('\U0010FFFF') == 1’;

        * surrogate pairs are not recombined in string literals, so
          ‘'\uDBFF\uDFFF' != '\U0010FFFF'’;

        * indexing or slicing non-BMP characters returns the expected
          value, so ‘'\U0010FFFF'[0]’ now returns ‘'\U0010FFFF'’ and not
          ‘'\uDBFF'’;

        * all other functions in the standard library now correctly
          handle non-BMP code points.

   * The value of *note sys.maxunicode: fef. is now always ‘1114111’
     (‘0x10FFFF’ in hexadecimal).  The ‘PyUnicode_GetMax()’ function
     still returns either ‘0xFFFF’ or ‘0x10FFFF’ for backward
     compatibility, and it should not be used with the new Unicode API
     (see bpo-13054(2)).

   * ‘./configure’ 旗標 ‘--with-wide-unicode’ 已被刪除。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0393/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=13054


File: python.info,  Node: 性能和資源使用情況,  Prev: 功能性,  Up: PEP 393 Flexible String Representation

1.11.5.2 性能和資源使用情況
...........................

The storage of Unicode strings now depends on the highest code point in
the string:

   * pure ASCII and Latin1 strings (‘U+0000-U+00FF’) use 1 byte per code
     point;

   * BMP strings (‘U+0000-U+FFFF’) use 2 bytes per code point;

   * non-BMP strings (‘U+10000-U+10FFFF’) use 4 bytes per code point.

The net effect is that for most applications, memory usage of string
storage should decrease significantly - especially compared to former
wide unicode builds - as, in many cases, strings will be pure ASCII even
in international contexts (because many strings store non-human language
data, such as XML fragments, HTTP headers, JSON-encoded data, etc.).  We
also hope that it will, for the same reasons, increase CPU cache
efficiency on non-trivial applications.  The memory usage of Python 3.3
is two to three times smaller than Python 3.2, and a little bit better
than Python 2.7, on a Django benchmark (see the PEP for details).

也參考
......

PEP 393(1) - Flexible String Representation

     PEP 由 Martin von Löwis 撰寫；由 Torsten Becker 和 Martin von Löwis
     實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0393/


File: python.info,  Node: PEP 397：適用於 Windows 的 Python 啟動器,  Next: PEP 3151 Reworking the OS and IO exception hierarchy,  Prev: PEP 393 Flexible String Representation,  Up: Python 3 3 有什麼新功能

1.11.6 PEP 397：適用於 Windows 的 Python 啟動器
-----------------------------------------------

The Python 3.3 Windows installer now includes a ‘py’ launcher
application that can be used to launch Python applications in a version
independent fashion.

This launcher is invoked implicitly when double-clicking ‘*.py’ files.
If only a single Python version is installed on the system, that version
will be used to run the file.  If multiple versions are installed, the
most recent version is used by default, but this can be overridden by
including a Unix-style "shebang line" in the Python script.

The launcher can also be used explicitly from the command line as the
‘py’ application.  Running ‘py’ follows the same version selection rules
as implicitly launching scripts, but a more specific version can be
selected by passing appropriate arguments (such as ‘-3’ to request
Python 3 when Python 2 is also installed, or ‘-2.6’ to specifically
request an earlier Python version when a more recent version is
installed).

In addition to the launcher, the Windows installer now includes an
option to add the newly installed Python to the system PATH.
(Contributed by Brian Curtin in bpo-3561(1).)

也參考
......

PEP 397(2) - 適用於 Windows 的 Python 啟動器

     由 Mark Hammond 和 Martin v.  Löwis 撰寫 PEP；由 Vinay Sajip 實作。

啟動器文件：*note Python Launcher for Windows: 562.

Installer PATH modification: *note Finding the Python executable: ff3.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=3561

   (2) https://peps.python.org/pep-0397/


File: python.info,  Node: PEP 3151 Reworking the OS and IO exception hierarchy,  Next: PEP 380 Syntax for Delegating to a Subgenerator,  Prev: PEP 397：適用於 Windows 的 Python 啟動器,  Up: Python 3 3 有什麼新功能

1.11.7 PEP 3151: Reworking the OS and IO exception hierarchy
------------------------------------------------------------

The hierarchy of exceptions raised by operating system errors is now
both simplified and finer-grained.

You don't have to worry anymore about choosing the appropriate exception
type between *note OSError: 350, *note IOError: ff5, *note
EnvironmentError: ff6, *note WindowsError: ff7, ‘mmap.error’, *note
socket.error: ff8. or *note select.error: ff9.  All these exception
types are now only one: *note OSError: 350.  The other names are kept as
aliases for compatibility reasons.

Also, it is now easier to catch a specific error condition.  Instead of
inspecting the ‘errno’ attribute (or ‘args[0]’) for a particular
constant from the *note errno: 4d. module, you can catch the adequate
*note OSError: 350. subclass.  The available subclasses are the
following:

   * *note BlockingIOError: ffa.

   * *note ChildProcessError: ffb.

   * *note ConnectionError: db0.

   * *note FileExistsError: fc3.

   * *note FileNotFoundError: e67.

   * *note InterruptedError: d2e.

   * *note IsADirectoryError: ffc.

   * *note NotADirectoryError: ffd.

   * *note PermissionError: ce9.

   * *note ProcessLookupError: ffe.

   * *note TimeoutError: 7d9.

And the *note ConnectionError: db0. itself has finer-grained subclasses:

   * *note BrokenPipeError: fff.

   * *note ConnectionAbortedError: 1000.

   * *note ConnectionRefusedError: 1001.

   * *note ConnectionResetError: 1002.

Thanks to the new exceptions, common usages of the *note errno: 4d. can
now be avoided.  For example, the following code written for Python 3.2:

     from errno import ENOENT, EACCES, EPERM

     try:
         with open("document.txt") as f:
             content = f.read()
     except IOError as err:
         if err.errno == ENOENT:
             print("document.txt file is missing")
         elif err.errno in (EACCES, EPERM):
             print("You are not allowed to read document.txt")
         else:
             raise

can now be written without the *note errno: 4d. import and without
manual inspection of exception attributes:

     try:
         with open("document.txt") as f:
             content = f.read()
     except FileNotFoundError:
         print("document.txt file is missing")
     except PermissionError:
         print("You are not allowed to read document.txt")

也參考
......

PEP 3151(1) - Reworking the OS and IO Exception Hierarchy

     由 Antoine Pitrou 撰寫 PEP 與實作

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3151/


File: python.info,  Node: PEP 380 Syntax for Delegating to a Subgenerator,  Next: PEP 409 Suppressing exception context,  Prev: PEP 3151 Reworking the OS and IO exception hierarchy,  Up: Python 3 3 有什麼新功能

1.11.8 PEP 380: Syntax for Delegating to a Subgenerator
-------------------------------------------------------

PEP 380 adds the ‘yield from’ expression, allowing a *note generator:
1004. to delegate part of its operations to another generator.  This
allows a section of code containing *note yield: 971. to be factored out
and placed in another generator.  Additionally, the subgenerator is
allowed to return with a value, and the value is made available to the
delegating generator.

While designed primarily for use in delegating to a subgenerator, the
‘yield from’ expression actually allows delegation to arbitrary
subiterators.

For simple iterators, ‘yield from iterable’ is essentially just a
shortened form of ‘for item in iterable: yield item’:

     >>> def g(x):
     ...     yield from range(x, 0, -1)
     ...     yield from range(x)
     ...
     >>> list(g(5))
     [5, 4, 3, 2, 1, 0, 1, 2, 3, 4]

However, unlike an ordinary loop, ‘yield from’ allows subgenerators to
receive sent and thrown values directly from the calling scope, and
return a final value to the outer generator:

     >>> def accumulate():
     ...     tally = 0
     ...     while 1:
     ...         next = yield
     ...         if next is None:
     ...             return tally
     ...         tally += next
     ...
     >>> def gather_tallies(tallies):
     ...     while 1:
     ...         tally = yield from accumulate()
     ...         tallies.append(tally)
     ...
     >>> tallies = []
     >>> acc = gather_tallies(tallies)
     >>> next(acc)  # Ensure the accumulator is ready to accept values
     >>> for i in range(4):
     ...     acc.send(i)
     ...
     >>> acc.send(None)  # Finish the first tally
     >>> for i in range(5):
     ...     acc.send(i)
     ...
     >>> acc.send(None)  # Finish the second tally
     >>> tallies
     [6, 10]

The main principle driving this change is to allow even generators that
are designed to be used with the ‘send’ and ‘throw’ methods to be split
into multiple subgenerators as easily as a single large function can be
split into multiple subfunctions.

也參考
......

PEP 380(1) - Syntax for Delegating to a Subgenerator

     PEP written by Greg Ewing; implementation by Greg Ewing, integrated
     into 3.3 by Renaud Blanch, Ryan Kelly and Nick Coghlan;
     documentation by Zbigniew Jędrzejewski-Szmek and Nick Coghlan

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0380/


File: python.info,  Node: PEP 409 Suppressing exception context,  Next: PEP 414 Explicit Unicode literals,  Prev: PEP 380 Syntax for Delegating to a Subgenerator,  Up: Python 3 3 有什麼新功能

1.11.9 PEP 409: Suppressing exception context
---------------------------------------------

PEP 409 introduces new syntax that allows the display of the chained
exception context to be disabled.  This allows cleaner error messages in
applications that convert between exception types:

     >>> class D:
     ...     def __init__(self, extra):
     ...         self._extra_attributes = extra
     ...     def __getattr__(self, attr):
     ...         try:
     ...             return self._extra_attributes[attr]
     ...         except KeyError:
     ...             raise AttributeError(attr) from None
     ...
     >>> D({}).x
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
       File "<stdin>", line 8, in __getattr__
     AttributeError: x

Without the ‘from None’ suffix to suppress the cause, the original
exception would be displayed by default:

     >>> class C:
     ...     def __init__(self, extra):
     ...         self._extra_attributes = extra
     ...     def __getattr__(self, attr):
     ...         try:
     ...             return self._extra_attributes[attr]
     ...         except KeyError:
     ...             raise AttributeError(attr)
     ...
     >>> C({}).x
     Traceback (most recent call last):
       File "<stdin>", line 6, in __getattr__
     KeyError: 'x'

     During handling of the above exception, another exception occurred:

     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
       File "<stdin>", line 8, in __getattr__
     AttributeError: x

No debugging capability is lost, as the original exception context
remains available if needed (for example, if an intervening library has
incorrectly suppressed valuable underlying details):

     >>> try:
     ...     D({}).x
     ... except AttributeError as exc:
     ...     print(repr(exc.__context__))
     ...
     KeyError('x',)

也參考
......

PEP 409(1) - Suppressing exception context

     PEP written by Ethan Furman; implemented by Ethan Furman and Nick
     Coghlan.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0409/


File: python.info,  Node: PEP 414 Explicit Unicode literals,  Next: PEP 3155 Qualified name for classes and functions,  Prev: PEP 409 Suppressing exception context,  Up: Python 3 3 有什麼新功能

1.11.10 PEP 414: Explicit Unicode literals
------------------------------------------

To ease the transition from Python 2 for Unicode aware Python
applications that make heavy use of Unicode literals, Python 3.3 once
again supports the "‘u’" prefix for string literals.  This prefix has no
semantic significance in Python 3, it is provided solely to reduce the
number of purely mechanical changes in migrating to Python 3, making it
easier for developers to focus on the more significant semantic changes
(such as the stricter default separation of binary and text data).

也參考
......

PEP 414(1) - Explicit Unicode literals

     由 Armin Ronacher 撰寫 PEP。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0414/


File: python.info,  Node: PEP 3155 Qualified name for classes and functions,  Next: PEP 412 Key-Sharing Dictionary,  Prev: PEP 414 Explicit Unicode literals,  Up: Python 3 3 有什麼新功能

1.11.11 PEP 3155: Qualified name for classes and functions
----------------------------------------------------------

Functions and class objects have a new ‘__qualname__’ attribute
representing the "path" from the module top-level to their definition.
For global functions and classes, this is the same as ‘__name__’.  For
other functions and classes, it provides better information about where
they were actually defined, and how they might be accessible from the
global scope.

Example with (non-bound) methods:

     >>> class C:
     ...     def meth(self):
     ...         pass
     ...
     >>> C.meth.__name__
     'meth'
     >>> C.meth.__qualname__
     'C.meth'

巢狀類別範例：

     >>> class C:
     ...     class D:
     ...         def meth(self):
     ...             pass
     ...
     >>> C.D.__name__
     'D'
     >>> C.D.__qualname__
     'C.D'
     >>> C.D.meth.__name__
     'meth'
     >>> C.D.meth.__qualname__
     'C.D.meth'

巢狀函式範例：

     >>> def outer():
     ...     def inner():
     ...         pass
     ...     return inner
     ...
     >>> outer().__name__
     'inner'
     >>> outer().__qualname__
     'outer.<locals>.inner'

The string representation of those objects is also changed to include
the new, more precise information:

     >>> str(C.D)
     "<class '__main__.C.D'>"
     >>> str(C.D.meth)
     '<function C.D.meth at 0x7f46b9fe31e0>'

也參考
......

PEP 3155(1) - Qualified name for classes and functions

     由 Antoine Pitrou 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3155/


File: python.info,  Node: PEP 412 Key-Sharing Dictionary,  Next: PEP 362：函式簽名物件,  Prev: PEP 3155 Qualified name for classes and functions,  Up: Python 3 3 有什麼新功能

1.11.12 PEP 412: Key-Sharing Dictionary
---------------------------------------

Dictionaries used for the storage of objects' attributes are now able to
share part of their internal storage between each other (namely, the
part which stores the keys and their respective hashes).  This reduces
the memory consumption of programs creating many instances of
non-builtin types.

也參考
......

PEP 412(1) - 密鑰共享字典

     由 Mark Shannon 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0412/


File: python.info,  Node: PEP 362：函式簽名物件,  Next: PEP 421：新增 sys implementation,  Prev: PEP 412 Key-Sharing Dictionary,  Up: Python 3 3 有什麼新功能

1.11.13 PEP 362：函式簽名物件
-----------------------------

A new function *note inspect.signature(): 6dc. makes introspection of
python callables easy and straightforward.  A broad range of callables
is supported: python functions, decorated or not, classes, and *note
functools.partial(): 356. objects.  New classes *note inspect.Signature:
1b3, *note inspect.Parameter: 1b4. and *note inspect.BoundArguments:
100a. hold information about the call signatures, such as, annotations,
default values, parameters kinds, and bound arguments, which
considerably simplifies writing decorators and any code that validates
or amends calling signatures or arguments.

也參考
......

PEP 362(1): - 函式簽名物件

     PEP 由 Brett Cannon、Yury Selivanov、Larry Hastings、Jiwon Seo 撰寫
     ；由 Yury Selivanov 實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0362/


File: python.info,  Node: PEP 421：新增 sys implementation,  Next: 使用 importlib 作為 import 的實作,  Prev: PEP 362：函式簽名物件,  Up: Python 3 3 有什麼新功能

1.11.14 PEP 421：新增 sys.implementation
----------------------------------------

A new attribute on the *note sys: c3. module exposes details specific to
the implementation of the currently running interpreter.  The initial
set of attributes on *note sys.implementation: 4bb. are ‘name’,
‘version’, ‘hexversion’, and ‘cache_tag’.

The intention of ‘sys.implementation’ is to consolidate into one
namespace the implementation-specific data used by the standard library.
This allows different Python implementations to share a single standard
library code base much more easily.  In its initial state,
‘sys.implementation’ holds only a small portion of the
implementation-specific data.  Over time that ratio will shift in order
to make the standard library more portable.

One example of improved standard library portability is ‘cache_tag’.  As
of Python 3.3, ‘sys.implementation.cache_tag’ is used by *note
importlib: 6b. to support PEP 3147(1) compliance.  Any Python
implementation that uses ‘importlib’ for its built-in import system may
use ‘cache_tag’ to control the caching behavior for modules.

* Menu:

* SimpleNamespace::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3147/


File: python.info,  Node: SimpleNamespace,  Up: PEP 421：新增 sys implementation

1.11.14.1 SimpleNamespace
.........................

The implementation of ‘sys.implementation’ also introduces a new type to
Python: *note types.SimpleNamespace: 1b5.  In contrast to a
mapping-based namespace, like *note dict: 23b, ‘SimpleNamespace’ is
attribute-based, like *note object: a2f.  However, unlike ‘object’,
‘SimpleNamespace’ instances are writable.  This means that you can add,
remove, and modify the namespace through normal attribute access.

也參考
......

PEP 421(1) - 新增 sys.implementation

     由 Eric Snow 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0421/


File: python.info,  Node: 使用 importlib 作為 import 的實作,  Next: 其他語言更動<10>,  Prev: PEP 421：新增 sys implementation,  Up: Python 3 3 有什麼新功能

1.11.15 使用 importlib 作為 import 的實作
-----------------------------------------

bpo-2377(1) - Replace __import__ w/ importlib.__import__ bpo-13959(2) -
Re-implement parts of ‘imp’ in pure Python bpo-14605(3) - Make import
machinery explicit bpo-14646(4) - Require loaders set __loader__ and
__package__

The *note __import__(): 879. function is now powered by *note
importlib.__import__(): 100e.  This work leads to the completion of
"phase 2" of PEP 302(5).  There are multiple benefits to this change.
First, it has allowed for more of the machinery powering import to be
exposed instead of being implicit and hidden within the C code.  It also
provides a single implementation for all Python VMs supporting Python
3.3 to use, helping to end any VM-specific deviations in import
semantics.  And finally it eases the maintenance of import, allowing for
future growth to occur.

For the common user, there should be no visible change in semantics.
For those whose code currently manipulates import or calls import
programmatically, the code changes that might possibly be required are
covered in the *note Porting Python code: 100f. section of this
document.

* Menu:

* 新 API::
* 明顯的變更::

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=2377

   (2) https://bugs.python.org/issue?@action=redirect&bpo=13959

   (3) https://bugs.python.org/issue?@action=redirect&bpo=14605

   (4) https://bugs.python.org/issue?@action=redirect&bpo=14646

   (5) https://peps.python.org/pep-0302/


File: python.info,  Node: 新 API,  Next: 明顯的變更,  Up: 使用 importlib 作為 import 的實作

1.11.15.1 新 API
................

One of the large benefits of this work is the exposure of what goes into
making the import statement work.  That means the various importers that
were once implicit are now fully exposed as part of the *note importlib:
6b. package.

The abstract base classes defined in *note importlib.abc: 6c. have been
expanded to properly delineate between *note meta path finders: 1011.
and *note path entry finders: 1012. by introducing *note
importlib.abc.MetaPathFinder: 813. and *note
importlib.abc.PathEntryFinder: 814, respectively.  The old ABC of
‘importlib.abc.Finder’ is now only provided for backwards-compatibility
and does not enforce any method requirements.

In terms of finders, *note importlib.machinery.FileFinder: 1013. exposes
the mechanism used to search for source and bytecode files of a module.
Previously this class was an implicit member of *note sys.path_hooks:
fc7.

For loaders, the new abstract base class *note importlib.abc.FileLoader:
1014. helps write a loader that uses the file system as the storage
mechanism for a module's code.  The loader for source files (*note
importlib.machinery.SourceFileLoader: 1015.), sourceless bytecode files
(*note importlib.machinery.SourcelessFileLoader: 1016.), and extension
modules (*note importlib.machinery.ExtensionFileLoader: c57.) are now
available for direct use.

*note ImportError: 352. now has ‘name’ and ‘path’ attributes which are
set when there is relevant data to provide.  The message for failed
imports will also provide the full name of the module now instead of
just the tail end of the module's name.

The *note importlib.invalidate_caches(): bb7. function will now call the
method with the same name on all finders cached in *note
sys.path_importer_cache: 588. to help clean up any stored state as
necessary.


File: python.info,  Node: 明顯的變更,  Prev: 新 API,  Up: 使用 importlib 作為 import 的實作

1.11.15.2 明顯的變更
....................

For potential required changes to code, see the *note Porting Python
code: 100f. section.

Beyond the expanse of what *note importlib: 6b. now exposes, there are
other visible changes to import.  The biggest is that *note
sys.meta_path: cd2. and *note sys.path_hooks: fc7. now store all of the
meta path finders and path entry hooks used by import.  Previously the
finders were implicit and hidden within the C code of import instead of
being directly exposed.  This means that one can now easily remove or
change the order of the various finders to fit one's needs.

Another change is that all modules have a ‘__loader__’ attribute,
storing the loader used to create the module.  PEP 302(1) has been
updated to make this attribute mandatory for loaders to implement, so in
the future once 3rd-party loaders have been updated people will be able
to rely on the existence of the attribute.  Until such time, though,
import is setting the module post-load.

Loaders are also now expected to set the ‘__package__’ attribute from
PEP 366(2).  Once again, import itself is already setting this on all
loaders from *note importlib: 6b. and import itself is setting the
attribute post-load.

‘None’ is now inserted into *note sys.path_importer_cache: 588. when no
finder can be found on *note sys.path_hooks: fc7.  Since
‘imp.NullImporter’ is not directly exposed on *note sys.path_hooks: fc7.
it could no longer be relied upon to always be available to use as a
value representing no finder found.

All other changes relate to semantic changes which should be taken into
consideration when updating code for Python 3.3, and thus should be read
about in the *note Porting Python code: 100f. section of this document.

（由 Brett Cannon 實作）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0302/

   (2) https://peps.python.org/pep-0366/


File: python.info,  Node: 其他語言更動<10>,  Next: A Finer-Grained Import Lock,  Prev: 使用 importlib 作為 import 的實作,  Up: Python 3 3 有什麼新功能

1.11.16 其他語言更動
--------------------

對核心 Python 語言所做的一些較小的更改包括：

   * Added support for Unicode name aliases and named sequences.  Both
     *note unicodedata.lookup(): 1019. and ‘'\N{...}'’ now resolve name
     aliases, and *note unicodedata.lookup(): 1019. resolves named
     sequences too.

     （由 Ezio Melotti 在 bpo-12753(1) 中貢獻。）

   * Unicode 資料庫更新至 UCD 版本 6.1.0

   * Equality comparisons on *note range(): 8e7. objects now return a
     result reflecting the equality of the underlying sequences
     generated by those range objects.  (bpo-13201(2))

   * The ‘count()’, ‘find()’, ‘rfind()’, ‘index()’ and ‘rindex()’
     methods of *note bytes: 1a5. and *note bytearray: 4e3. objects now
     accept an integer between 0 and 255 as their first argument.

     （由 Petri Lehtinen 在 bpo-12170(3) 中貢獻。）

   * The ‘rjust()’, ‘ljust()’, and ‘center()’ methods of *note bytes:
     1a5. and *note bytearray: 4e3. now accept a *note bytearray: 4e3.
     for the ‘fill’ argument.  (Contributed by Petri Lehtinen in
     bpo-12380(4).)

   * New methods have been added to *note list: 5b6. and *note
     bytearray: 4e3.: ‘copy()’ and ‘clear()’ (bpo-10516(5)).
     Consequently, *note MutableSequence: 187. now also defines a
     ‘clear()’ method (bpo-11388(6)).

   * Raw bytes literals can now be written ‘rb"..."’ as well as
     ‘br"..."’.

     （由 Antoine Pitrou 在 bpo-13748(7) 中貢獻。）

   * *note dict.setdefault(): 101a. now does only one lookup for the
     given key, making it atomic when used with built-in types.

     （由 Filip Gruszczyński 在 bpo-13521(8) 中貢獻。）

   * The error messages produced when a function call does not match the
     function signature have been significantly improved.

     （由 Benjamin Peterson 貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=12753

   (2) https://bugs.python.org/issue?@action=redirect&bpo=13201

   (3) https://bugs.python.org/issue?@action=redirect&bpo=12170

   (4) https://bugs.python.org/issue?@action=redirect&bpo=12380

   (5) https://bugs.python.org/issue?@action=redirect&bpo=10516

   (6) https://bugs.python.org/issue?@action=redirect&bpo=11388

   (7) https://bugs.python.org/issue?@action=redirect&bpo=13748

   (8) https://bugs.python.org/issue?@action=redirect&bpo=13521


File: python.info,  Node: A Finer-Grained Import Lock,  Next: 內建函式和型別,  Prev: 其他語言更動<10>,  Up: Python 3 3 有什麼新功能

1.11.17 A Finer-Grained Import Lock
-----------------------------------

Previous versions of CPython have always relied on a global import lock.
This led to unexpected annoyances, such as deadlocks when importing a
module would trigger code execution in a different thread as a
side-effect.  Clumsy workarounds were sometimes employed, such as the
*note PyImport_ImportModuleNoBlock(): 388. C API function.

In Python 3.3, importing a module takes a per-module lock.  This
correctly serializes importation of a given module from multiple threads
(preventing the exposure of incompletely initialized modules), while
eliminating the aforementioned annoyances.

（由 Antoine Pitrou 在 bpo-9260(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=9260


File: python.info,  Node: 內建函式和型別,  Next: 新模組<6>,  Prev: A Finer-Grained Import Lock,  Up: Python 3 3 有什麼新功能

1.11.18 內建函式和型別
----------------------

   * *note open(): 4c0. gets a new 'opener' parameter: the underlying
     file descriptor for the file object is then obtained by calling
     'opener' with ('file', 'flags').  It can be used to use custom
     flags like *note os.O_CLOEXEC: 101d. for example.  The ‘'x'’ mode
     was added: open for exclusive creation, failing if the file already
     exists.

   * *note print(): f18.: added the 'flush' keyword argument.  If the
     'flush' keyword argument is true, the stream is forcibly flushed.

   * *note hash(): 58f.: hash randomization is enabled by default, see
     *note object.__hash__(): a9e. and *note PYTHONHASHSEED: 101e.

   * The *note str: 3f2. type gets a new *note casefold(): d7c. method:
     return a casefolded copy of the string, casefolded strings may be
     used for caseless matching.  For example, ‘'ß'.casefold()’ returns
     ‘'ss'’.

   * The sequence documentation has been substantially rewritten to
     better explain the binary/text sequence distinction and to provide
     specific documentation sections for the individual builtin sequence
     types (bpo-4966(1)).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=4966


File: python.info,  Node: 新模組<6>,  Next: 改進的模組<10>,  Prev: 內建函式和型別,  Up: Python 3 3 有什麼新功能

1.11.19 新模組
--------------

* Menu:

* faulthandler: faulthandler<4>.
* ipaddress: ipaddress<6>.
* lzma: lzma<2>.


File: python.info,  Node: faulthandler<4>,  Next: ipaddress<6>,  Up: 新模組<6>

1.11.19.1 faulthandler
......................

This new debug module *note faulthandler: 4e. contains functions to dump
Python tracebacks explicitly, on a fault (a crash like a segmentation
fault), after a timeout, or on a user signal.  Call *note
faulthandler.enable(): c45. to install fault handlers for the ‘SIGSEGV’,
‘SIGFPE’, ‘SIGABRT’, ‘SIGBUS’, and ‘SIGILL’ signals.  You can also
enable them at startup by setting the *note PYTHONFAULTHANDLER: 1021.
environment variable or by using *note -X: 15a. ‘faulthandler’ command
line option.

Example of a segmentation fault on Linux:

     $ python -q -X faulthandler
     >>> import ctypes
     >>> ctypes.string_at(0)
     Fatal Python error: Segmentation fault

     Current thread 0x00007fb899f39700:
       File "/home/python/cpython/Lib/ctypes/__init__.py", line 486 in string_at
       File "<stdin>", line 1 in <module>
     Segmentation fault


File: python.info,  Node: ipaddress<6>,  Next: lzma<2>,  Prev: faulthandler<4>,  Up: 新模組<6>

1.11.19.2 ipaddress
...................

The new *note ipaddress: 74. module provides tools for creating and
manipulating objects representing IPv4 and IPv6 addresses, networks and
interfaces (i.e.  an IP address associated with a specific IP subnet).

（由 Google 和 Peter Moody 在 PEP 3144(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3144/


File: python.info,  Node: lzma<2>,  Prev: ipaddress<6>,  Up: 新模組<6>

1.11.19.3 lzma
..............

The newly added *note lzma: 7e. module provides data compression and
decompression using the LZMA algorithm, including support for the ‘.xz’
and ‘.lzma’ file formats.

（由 Nadeem Vawda 和 Per Øyvind Karlsen 在 bpo-6715(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=6715


File: python.info,  Node: 改進的模組<10>,  Next: 最佳化<9>,  Prev: 新模組<6>,  Up: Python 3 3 有什麼新功能

1.11.20 改進的模組
------------------

* Menu:

* abc: abc<2>.
* array: array<5>.
* base64: base64<4>.
* binascii: binascii<3>.
* bz2: bz2<2>.
* codecs: codecs<2>.
* collections: collections<7>.
* contextlib: contextlib<7>.
* crypt: crypt<2>.
* curses: curses<5>.
* datetime: datetime<6>.
* decimal: decimal<3>.
* email: email<5>.
* ftplib: ftplib<3>.
* functools: functools<6>.
* gc: gc<7>.
* hmac: hmac<4>.
* http: http<4>.
* html: html<2>.
* imaplib: imaplib<3>.
* inspect: inspect<9>.
* io: io<6>.
* itertools: itertools<6>.
* logging: logging<7>.
* math: math<9>.
* mmap: mmap<4>.
* multiprocessing: multiprocessing<8>.
* nntplib: nntplib<2>.
* os: os<12>.
* pdb: pdb<7>.
* pickle: pickle<5>.
* pydoc: pydoc<5>.
* re: re<9>.
* sched::
* select: select<2>.
* shlex: shlex<3>.
* shutil: shutil<7>.
* signal: signal<4>.
* smtpd: smtpd<4>.
* smtplib: smtplib<4>.
* socket: socket<10>.
* socketserver: socketserver<3>.
* sqlite3: sqlite3<10>.
* ssl: ssl<11>.
* stat: stat<2>.
* struct: struct<3>.
* subprocess: subprocess<6>.
* sys: sys<12>.
* tarfile: tarfile<8>.
* tempfile: tempfile<4>.
* textwrap: textwrap<2>.
* threading: threading<8>.
* time: time<8>.
* types: types<7>.
* unittest: unittest<10>.
* urllib: urllib<4>.
* webbrowser: webbrowser<3>.
* xml.etree.ElementTree: xml etree ElementTree<2>.
* zlib: zlib<2>.


File: python.info,  Node: abc<2>,  Next: array<5>,  Up: 改進的模組<10>

1.11.20.1 abc
.............

Improved support for abstract base classes containing descriptors
composed with abstract methods.  The recommended approach to declaring
abstract descriptors is now to provide ‘__isabstractmethod__’ as a
dynamically updated property.  The built-in descriptors have been
updated accordingly.

   * *note abc.abstractproperty: 1026. 已被棄用，請改 *note property:
     180. 和 *note abc.abstractmethod(): 1027.。

   * *note abc.abstractclassmethod: 1028. 已被棄用，請改用 *note
     classmethod: 14a. 和 *note abc.abstractmethod(): 1027.。

   * *note abc.abstractstaticmethod: 1029. 已被棄用，請改用 *note
     staticmethod: 358. 和 *note abc.abstractmethod(): 1027.。

（由 Darren Dale 在 bpo-11610(1) 中貢獻。）

*note abc.ABCMeta.register(): 102a. now returns the registered subclass,
which means it can now be used as a class decorator (bpo-10868(2)).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=11610

   (2) https://bugs.python.org/issue?@action=redirect&bpo=10868


File: python.info,  Node: array<5>,  Next: base64<4>,  Prev: abc<2>,  Up: 改進的模組<10>

1.11.20.2 array
...............

The *note array: 6. module supports the long long type using ‘q’ and ‘Q’
type codes.

（由 Oren Tirosh 和 Hirokazu Yamamoto 在 bpo-1172711(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1172711


File: python.info,  Node: base64<4>,  Next: binascii<3>,  Prev: array<5>,  Up: 改進的模組<10>

1.11.20.3 base64
................

ASCII-only Unicode strings are now accepted by the decoding functions of
the *note base64: a. modern interface.  For example,
‘base64.b64decode('YWJj')’ returns ‘b'abc'’.  (Contributed by Catalin
Iacob in bpo-13641(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=13641


File: python.info,  Node: binascii<3>,  Next: bz2<2>,  Prev: base64<4>,  Up: 改進的模組<10>

1.11.20.4 binascii
..................

In addition to the binary objects they normally accept, the ‘a2b_’
functions now all also accept ASCII-only strings as input.  (Contributed
by Antoine Pitrou in bpo-13637(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=13637


File: python.info,  Node: bz2<2>,  Next: codecs<2>,  Prev: binascii<3>,  Up: 改進的模組<10>

1.11.20.5 bz2
.............

The *note bz2: f. module has been rewritten from scratch.  In the
process, several new features have been added:

   * New *note bz2.open(): 102f. function: open a bzip2-compressed file
     in binary or text mode.

   * *note bz2.BZ2File: 80b. can now read from and write to arbitrary
     file-like objects, by means of its constructor's 'fileobj'
     argument.

     （由 Nadeem Vawda 在 bpo-5863(1) 中貢獻。）

   * *note bz2.BZ2File: 80b. and *note bz2.decompress(): 1030. can now
     decompress multi-stream inputs (such as those produced by the
     ‘pbzip2’ tool).  *note bz2.BZ2File: 80b. can now also be used to
     create this type of file, using the ‘'a'’ (append) mode.

     （由 Nir Aides 在 bpo-1625(2) 中貢獻。）

   * *note bz2.BZ2File: 80b. now implements all of the *note
     io.BufferedIOBase: 63a. API, except for the ‘detach()’ and
     ‘truncate()’ methods.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=5863

   (2) https://bugs.python.org/issue?@action=redirect&bpo=1625


File: python.info,  Node: codecs<2>,  Next: collections<7>,  Prev: bz2<2>,  Up: 改進的模組<10>

1.11.20.6 codecs
................

The *note mbcs: 49. codec has been rewritten to handle correctly
‘replace’ and ‘ignore’ error handlers on all Windows versions.  The
*note mbcs: 49. codec now supports all error handlers, instead of only
‘replace’ to encode and ‘ignore’ to decode.

A new Windows-only codec has been added: ‘cp65001’ (bpo-13216(1)).  It
is the Windows code page 65001 (Windows UTF-8, ‘CP_UTF8’).  For example,
it is used by ‘sys.stdout’ if the console output code page is set to
cp65001 (e.g., using ‘chcp 65001’ command).

Multibyte CJK decoders now resynchronize faster.  They only ignore the
first byte of an invalid byte sequence.  For example,
‘b'\xff\n'.decode('gb2312', 'replace')’ now returns a ‘\n’ after the
replacement character.

(bpo-12016(2))

Incremental CJK codec encoders are no longer reset at each call to their
encode() methods.  For example:

     >>> import codecs
     >>> encoder = codecs.getincrementalencoder('hz')('strict')
     >>> b''.join(encoder.encode(x) for x in '\u52ff\u65bd\u65bc\u4eba\u3002 Bye.')
     b'~{NpJ)l6HK!#~} Bye.'

This example gives ‘b'~{Np~}~{J)~}~{l6~}~{HK~}~{!#~} Bye.'’ with older
Python versions.

(bpo-12100(3))

‘unicode_internal’ 編解碼器已被棄用。

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=13216

   (2) https://bugs.python.org/issue?@action=redirect&bpo=12016

   (3) https://bugs.python.org/issue?@action=redirect&bpo=12100


File: python.info,  Node: collections<7>,  Next: contextlib<7>,  Prev: codecs<2>,  Up: 改進的模組<10>

1.11.20.7 collections
.....................

Addition of a new *note ChainMap: bc3. class to allow treating a number
of mappings as a single unit.  (Written by Raymond Hettinger for
bpo-11089(1), made public in bpo-11297(2).)

The abstract base classes have been moved in a new *note
collections.abc: 17. module, to better differentiate between the
abstract and the concrete collections classes.  Aliases for ABCs are
still present in the *note collections: 16. module to preserve existing
imports.  (bpo-11085(3))

The *note Counter: 1033. class now supports the unary ‘+’ and ‘-’
operators, as well as the in-place operators ‘+=’, ‘-=’, ‘|=’, and ‘&=’.
(Contributed by Raymond Hettinger in bpo-13121(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=11089

   (2) https://bugs.python.org/issue?@action=redirect&bpo=11297

   (3) https://bugs.python.org/issue?@action=redirect&bpo=11085

   (4) https://bugs.python.org/issue?@action=redirect&bpo=13121


File: python.info,  Node: contextlib<7>,  Next: crypt<2>,  Prev: collections<7>,  Up: 改進的模組<10>

1.11.20.8 contextlib
....................

*note ExitStack: acd. now provides a solid foundation for programmatic
manipulation of context managers and similar cleanup functionality.
Unlike the previous ‘contextlib.nested’ API (which was deprecated and
removed), the new API is designed to work correctly regardless of
whether context managers acquire their resources in their ‘__init__’
method (for example, file objects) or in their ‘__enter__’ method (for
example, synchronisation objects from the *note threading: d6. module).

(bpo-13585(1))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=13585


File: python.info,  Node: crypt<2>,  Next: curses<5>,  Prev: contextlib<7>,  Up: 改進的模組<10>

1.11.20.9 crypt
...............

Addition of salt and modular crypt format (hashing method) and the
‘mksalt()’ function to the ‘crypt’ module.

(bpo-10924(1))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=10924


File: python.info,  Node: curses<5>,  Next: datetime<6>,  Prev: crypt<2>,  Up: 改進的模組<10>

1.11.20.10 curses
.................

   * If the *note curses: 23. module is linked to the ncursesw library,
     use Unicode functions when Unicode strings or characters are passed
     (e.g.  ‘waddwstr()’), and bytes functions otherwise (e.g.
     ‘waddstr()’).

   * Use the locale encoding instead of ‘utf-8’ to encode Unicode
     strings.

   * ‘curses.window’ 有一個新的 *note curses.window.encoding: 1037. 屬性
     。

   * ‘curses.window’ 類別有一個新的 *note get_wch(): 1038. 方法來獲取寬
     字元

   * The *note curses: 23. module has a new *note unget_wch(): 1039.
     function to push a wide character so the next *note get_wch():
     1038. will return it

（由 Iñigo Serna 在 bpo-6755(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=6755


File: python.info,  Node: datetime<6>,  Next: decimal<3>,  Prev: curses<5>,  Up: 改進的模組<10>

1.11.20.11 datetime
...................

   * Equality comparisons between naive and aware *note datetime: 1b0.
     instances now return *note False: adb. instead of raising *note
     TypeError: 4dd. (bpo-15006(1)).

   * New *note datetime.datetime.timestamp(): 103b. method: Return POSIX
     timestamp corresponding to the *note datetime: 1b0. instance.

   * The *note datetime.datetime.strftime(): c37. method supports
     formatting years older than 1000.

   * The *note datetime.datetime.astimezone(): 974. method can now be
     called without arguments to convert datetime instance to the system
     timezone.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=15006


File: python.info,  Node: decimal<3>,  Next: email<5>,  Prev: datetime<6>,  Up: 改進的模組<10>

1.11.20.12 decimal
..................

bpo-7652(1) - integrate fast native decimal arithmetic.

     由 Stefan Krah 編寫的 C 模組和 libmpdec。

The new C version of the decimal module integrates the high speed
libmpdec library for arbitrary precision correctly rounded decimal
floating-point arithmetic.  libmpdec conforms to IBM's General Decimal
Arithmetic Specification.

Performance gains range from 10x for database applications to 100x for
numerically intensive applications.  These numbers are expected gains
for standard precisions used in decimal floating-point arithmetic.
Since the precision is user configurable, the exact figures may vary.
For example, in integer bignum arithmetic the differences can be
significantly higher.

The following table is meant as an illustration.  Benchmarks are
available at ‘https://www.bytereef.org/mpdecimal/quickstart.html’.

                   decimal.py        _decimal           speedup
                                                        
     ---------------------------------------------------------------------
                                                        
     pi            42.02s            0.345s             120x
                                                        
                                                        
     telco         172.19s           5.68s              30x
                                                        
                                                        
     psycopg       3.57s             0.29s              12x
                                                        

* Menu:

* 功能: 功能<2>.
* API 變更: API 變更<2>.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=7652


File: python.info,  Node: 功能<2>,  Next: API 變更<2>,  Up: decimal<3>

1.11.20.13 功能
...............

   * The *note FloatOperation: 103e. signal optionally enables stricter
     semantics for mixing floats and Decimals.

   * If Python is compiled without threads, the C version automatically
     disables the expensive thread local context machinery.  In this
     case, the variable *note HAVE_THREADS: 103f. is set to ‘False’.


File: python.info,  Node: API 變更<2>,  Prev: 功能<2>,  Up: decimal<3>

1.11.20.14 API 變更
...................

   * The C module has the following context limits, depending on the
     machine architecture:

                                  32 位元              64 位元
                                                       
          ---------------------------------------------------------------------------
                                                       
          ‘MAX_PREC’              ‘425000000’          ‘999999999999999999’
                                                       
                                                       
          ‘MAX_EMAX’              ‘425000000’          ‘999999999999999999’
                                                       
                                                       
          ‘MIN_EMIN’              ‘-425000000’         ‘-999999999999999999’
                                                       

   * In the context templates (*note DefaultContext: 1041, *note
     BasicContext: 1042. and *note ExtendedContext: 1043.) the magnitude
     of ‘Emax’ and ‘Emin’ has changed to ‘999999’.

   * The *note Decimal: 27c. constructor in decimal.py does not observe
     the context limits and converts values with arbitrary exponents or
     precision exactly.  Since the C version has internal limits, the
     following scheme is used: If possible, values are converted
     exactly, otherwise *note InvalidOperation: 1044. is raised and the
     result is NaN. In the latter case it is always possible to use
     *note create_decimal(): 1045. in order to obtain a rounded or
     inexact value.

   * The power function in decimal.py is always correctly rounded.  In
     the C version, it is defined in terms of the correctly rounded
     *note exp(): 1046. and *note ln(): 1047. functions, but the final
     result is only "almost always correctly rounded".

   * In the C version, the context dictionary containing the signals is
     a *note MutableMapping: 1048.  For speed reasons, ‘flags’ and
     ‘traps’ always refer to the same *note MutableMapping: 1048. that
     the context was initialized with.  If a new signal dictionary is
     assigned, ‘flags’ and ‘traps’ are updated with the new values, but
     they do not reference the RHS dictionary.

   * Pickling a *note Context: 1049. produces a different output in
     order to have a common interchange format for the Python and C
     versions.

   * The order of arguments in the *note Context: 1049. constructor has
     been changed to match the order displayed by *note repr(): 7a1.

   * *note quantize(): 104a. 方法中的 ‘watchexp’ 參數已棄用。


File: python.info,  Node: email<5>,  Next: ftplib<3>,  Prev: decimal<3>,  Up: 改進的模組<10>

1.11.20.15 email
................

* Menu:

* Policy Framework::
* Provisional Policy with New Header API::
* 其他 API 變更::


File: python.info,  Node: Policy Framework,  Next: Provisional Policy with New Header API,  Up: email<5>

1.11.20.16 Policy Framework
...........................

The email package now has a *note policy: 46. framework.  A *note
Policy: 104d. is an object with several methods and properties that
control how the email package behaves.  The primary policy for Python
3.3 is the *note Compat32: 104e. policy, which provides backward
compatibility with the email package in Python 3.2.  A ‘policy’ can be
specified when an email message is parsed by a *note parser: 45, or when
a *note Message: 261. object is created, or when an email is serialized
using a *note generator: 37.  Unless overridden, a policy passed to a
‘parser’ is inherited by all the ‘Message’ object and sub-objects
created by the ‘parser’.  By default a ‘generator’ will use the policy
of the ‘Message’ object it is serializing.  The default policy is *note
compat32: c40.

The minimum set of controls implemented by all ‘policy’ objects are:

max_line_length     The maximum length, excluding the linesep character(s),
                    individual lines may have when a ‘Message’ is serialized.
                    Defaults to 78.
                    
                    
linesep             The character used to separate individual lines when a
                    ‘Message’ is serialized.  Defaults to ‘\n’.
                    
                    
cte_type            ‘7bit’ or ‘8bit’.  ‘8bit’ applies only to a ‘Bytes’
                    ‘generator’, and means that non-ASCII may be used where
                    allowed by the protocol (or where it exists in the
                    original input).
                    
                    
raise_on_defect     Causes a ‘parser’ to raise error when defects are
                    encountered instead of adding them to the ‘Message’
                    object's ‘defects’ list.
                    

A new policy instance, with new settings, is created using the *note
clone(): 104f. method of policy objects.  ‘clone’ takes any of the above
controls as keyword arguments.  Any control not specified in the call
retains its default value.  Thus you can create a policy that uses
‘\r\n’ linesep characters like this:

     mypolicy = compat32.clone(linesep='\r\n')

Policies can be used to make the generation of messages in the format
needed by your application simpler.  Instead of having to remember to
specify ‘linesep='\r\n'’ in all the places you call a ‘generator’, you
can specify it once, when you set the policy used by the ‘parser’ or the
‘Message’, whichever your program uses to create ‘Message’ objects.  On
the other hand, if you need to generate messages in multiple forms, you
can still specify the parameters in the appropriate ‘generator’ call.
Or you can have custom policy instances for your different cases, and
pass those in when you create the ‘generator’.


File: python.info,  Node: Provisional Policy with New Header API,  Next: 其他 API 變更,  Prev: Policy Framework,  Up: email<5>

1.11.20.17 Provisional Policy with New Header API
.................................................

While the policy framework is worthwhile all by itself, the main
motivation for introducing it is to allow the creation of new policies
that implement new features for the email package in a way that
maintains backward compatibility for those who do not use the new
policies.  Because the new policies introduce a new API, we are
releasing them in Python 3.3 as a *note provisional policy: fe4.
Backwards incompatible changes (up to and including removal of the code)
may occur if deemed necessary by the core developers.

The new policies are instances of *note EmailPolicy: 1051, and add the
following additional controls:

refold_source       Controls whether or not headers parsed by a
                    *note parser: 45. are refolded by the
                    *note generator: 37.  It can be ‘none’, ‘long’, or ‘all’.
                    The default is ‘long’, which means that source headers
                    with a line longer than ‘max_line_length’ get refolded.
                    ‘none’ means no line get refolded, and ‘all’ means that
                    all lines get refolded.
                    
                    
header_factory      A callable that take a ‘name’ and ‘value’ and produces a
                    custom header object.
                    

The ‘header_factory’ is the key to the new features provided by the new
policies.  When one of the new policies is used, any header retrieved
from a ‘Message’ object is an object produced by the ‘header_factory’,
and any time you set a header on a ‘Message’ it becomes an object
produced by ‘header_factory’.  All such header objects have a ‘name’
attribute equal to the header name.  Address and Date headers have
additional attributes that give you access to the parsed data of the
header.  This means you can now do things like this:

     >>> m = Message(policy=SMTP)
     >>> m['To'] = 'Éric <foo@example.com>'
     >>> m['to']
     'Éric <foo@example.com>'
     >>> m['to'].addresses
     (Address(display_name='Éric', username='foo', domain='example.com'),)
     >>> m['to'].addresses[0].username
     'foo'
     >>> m['to'].addresses[0].display_name
     'Éric'
     >>> m['Date'] = email.utils.localtime()
     >>> m['Date'].datetime
     datetime.datetime(2012, 5, 25, 21, 39, 24, 465484, tzinfo=datetime.timezone(datetime.timedelta(-1, 72000), 'EDT'))
     >>> m['Date']
     'Fri, 25 May 2012 21:44:27 -0400'
     >>> print(m)
     To: =?utf-8?q?=C3=89ric?= <foo@example.com>
     Date: Fri, 25 May 2012 21:44:27 -0400

You will note that the unicode display name is automatically encoded as
‘utf-8’ when the message is serialized, but that when the header is
accessed directly, you get the unicode version.  This eliminates any
need to deal with the *note email.header: 38. *note decode_header():
1052. or *note make_header(): 1053. functions.

You can also create addresses from parts:

     >>> m['cc'] = [Group('pals', [Address('Bob', 'bob', 'example.com'),
     ...                           Address('Sally', 'sally', 'example.com')]),
     ...            Address('Bonzo', addr_spec='bonz@laugh.com')]
     >>> print(m)
     To: =?utf-8?q?=C3=89ric?= <foo@example.com>
     Date: Fri, 25 May 2012 21:44:27 -0400
     cc: pals: Bob <bob@example.com>, Sally <sally@example.com>;, Bonzo <bonz@laugh.com>

解碼為 unicode 是自動完成的：

     >>> m2 = message_from_string(str(m))
     >>> m2['to']
     'Éric <foo@example.com>'

When you parse a message, you can use the ‘addresses’ and ‘groups’
attributes of the header objects to access the groups and individual
addresses:

     >>> m2['cc'].addresses
     (Address(display_name='Bob', username='bob', domain='example.com'), Address(display_name='Sally', username='sally', domain='example.com'), Address(display_name='Bonzo', username='bonz', domain='laugh.com'))
     >>> m2['cc'].groups
     (Group(display_name='pals', addresses=(Address(display_name='Bob', username='bob', domain='example.com'), Address(display_name='Sally', username='sally', domain='example.com')), Group(display_name=None, addresses=(Address(display_name='Bonzo', username='bonz', domain='laugh.com'),))

In summary, if you use one of the new policies, header manipulation
works the way it ought to: your application works with unicode strings,
and the email package transparently encodes and decodes the unicode to
and from the RFC standard Content Transfer Encodings.


File: python.info,  Node: 其他 API 變更,  Prev: Provisional Policy with New Header API,  Up: email<5>

1.11.20.18 其他 API 變更
........................

New *note BytesHeaderParser: 1055, added to the *note parser: 45. module
to complement *note HeaderParser: 1056. and complete the Bytes API.

新工具函式：

   * *note format_datetime(): 1057.: given a *note datetime: 1b0,
     produce a string formatted for use in an email header.

   * *note parsedate_to_datetime(): 1058.: given a date string from an
     email header, convert it into an aware *note datetime: 1b0, or a
     naive *note datetime: 1b0. if the offset is ‘-0000’.

   * *note localtime(): 2a6.: With no argument, returns the current
     local time as an aware *note datetime: 1b0. using the local *note
     timezone: 1059.  Given an aware *note datetime: 1b0, converts it
     into an aware *note datetime: 1b0. using the local *note timezone:
     1059.


File: python.info,  Node: ftplib<3>,  Next: functools<6>,  Prev: email<5>,  Up: 改進的模組<10>

1.11.20.19 ftplib
.................

   * *note ftplib.FTP: 89f. now accepts a ‘source_address’ keyword
     argument to specify the ‘(host, port)’ to use as the source address
     in the bind call when creating the outgoing socket.  (Contributed
     by Giampaolo Rodolà in bpo-8594(1).)

   * The *note FTP_TLS: 8a0. class now provides a new *note ccc(): 105b.
     function to revert control channel back to plaintext.  This can be
     useful to take advantage of firewalls that know how to handle NAT
     with non-secure FTP without opening fixed ports.  (Contributed by
     Giampaolo Rodolà in bpo-12139(2).)

   * Added *note ftplib.FTP.mlsd(): 105c. method which provides a
     parsable directory listing format and deprecates *note
     ftplib.FTP.nlst(): 105d. and *note ftplib.FTP.dir(): 105e.
     (Contributed by Giampaolo Rodolà in bpo-11072(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=8594

   (2) https://bugs.python.org/issue?@action=redirect&bpo=12139

   (3) https://bugs.python.org/issue?@action=redirect&bpo=11072


File: python.info,  Node: functools<6>,  Next: gc<7>,  Prev: ftplib<3>,  Up: 改進的模組<10>

1.11.20.20 functools
....................

The *note functools.lru_cache(): 993. decorator now accepts a ‘typed’
keyword argument (that defaults to ‘False’ to ensure that it caches
values of different types that compare equal in separate cache slots.
(Contributed by Raymond Hettinger in bpo-13227(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=13227


File: python.info,  Node: gc<7>,  Next: hmac<4>,  Prev: functools<6>,  Up: 改進的模組<10>

1.11.20.21 gc
.............

It is now possible to register callbacks invoked by the garbage
collector before and after collection using the new *note callbacks:
1061. list.


File: python.info,  Node: hmac<4>,  Next: http<4>,  Prev: gc<7>,  Up: 改進的模組<10>

1.11.20.22 hmac
...............

A new *note compare_digest(): 1063. function has been added to prevent
side channel attacks on digests through timing analysis.  (Contributed
by Nick Coghlan and Christian Heimes in bpo-15061(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=15061


File: python.info,  Node: http<4>,  Next: html<2>,  Prev: hmac<4>,  Up: 改進的模組<10>

1.11.20.23 http
...............

*note http.server.BaseHTTPRequestHandler: 1065. now buffers the headers
and writes them all at once when *note end_headers(): 1066. is called.
A new method *note flush_headers(): 1067. can be used to directly manage
when the accumulated headers are sent.  (Contributed by Andrew Schaaf in
bpo-3709(1).)

*note http.server: 68. now produces valid ‘HTML 4.01 strict’ output.
(Contributed by Ezio Melotti in bpo-13295(2).)

*note http.client.HTTPResponse: 1068. now has a *note readinto(): 1069.
method, which means it can be used as an *note io.RawIOBase: 106a.
class.  (Contributed by John Kuhn in bpo-13464(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=3709

   (2) https://bugs.python.org/issue?@action=redirect&bpo=13295

   (3) https://bugs.python.org/issue?@action=redirect&bpo=13464


File: python.info,  Node: html<2>,  Next: imaplib<3>,  Prev: http<4>,  Up: 改進的模組<10>

1.11.20.24 html
...............

*note html.parser.HTMLParser: 81a. is now able to parse broken markup
without raising errors, therefore the 'strict' argument of the
constructor and the ‘HTMLParseError’ exception are now deprecated.  The
ability to parse broken markup is the result of a number of bug fixes
that are also available on the latest bug fix releases of Python
2.7/3.2.  (Contributed by Ezio Melotti in bpo-15114(1), and
bpo-14538(2), bpo-13993(3), bpo-13960(4), bpo-13358(5), bpo-1745761(6),
bpo-755670(7), bpo-13357(8), bpo-12629(9), bpo-1200313(10),
bpo-670664(11), bpo-13273(12), bpo-12888(13), bpo-7311(14).)

A new *note html5: 106c. dictionary that maps HTML5 named character
references to the equivalent Unicode character(s) (e.g.  ‘html5['gt;']
== '>'’) has been added to the *note html.entities: 62. module.  The
dictionary is now also used by *note HTMLParser: 81a.  (Contributed by
Ezio Melotti in bpo-11113(15) and bpo-15156(16).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=15114

   (2) https://bugs.python.org/issue?@action=redirect&bpo=14538

   (3) https://bugs.python.org/issue?@action=redirect&bpo=13993

   (4) https://bugs.python.org/issue?@action=redirect&bpo=13960

   (5) https://bugs.python.org/issue?@action=redirect&bpo=13358

   (6) https://bugs.python.org/issue?@action=redirect&bpo=1745761

   (7) https://bugs.python.org/issue?@action=redirect&bpo=755670

   (8) https://bugs.python.org/issue?@action=redirect&bpo=13357

   (9) https://bugs.python.org/issue?@action=redirect&bpo=12629

   (10) https://bugs.python.org/issue?@action=redirect&bpo=1200313

   (11) https://bugs.python.org/issue?@action=redirect&bpo=670664

   (12) https://bugs.python.org/issue?@action=redirect&bpo=13273

   (13) https://bugs.python.org/issue?@action=redirect&bpo=12888

   (14) https://bugs.python.org/issue?@action=redirect&bpo=7311

   (15) https://bugs.python.org/issue?@action=redirect&bpo=11113

   (16) https://bugs.python.org/issue?@action=redirect&bpo=15156


File: python.info,  Node: imaplib<3>,  Next: inspect<9>,  Prev: html<2>,  Up: 改進的模組<10>

1.11.20.25 imaplib
..................

The *note IMAP4_SSL: 8a9. constructor now accepts an SSLContext
parameter to control parameters of the secure channel.

（由 Sijin Joseph 在 bpo-8808(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=8808


File: python.info,  Node: inspect<9>,  Next: io<6>,  Prev: imaplib<3>,  Up: 改進的模組<10>

1.11.20.26 inspect
..................

A new *note getclosurevars(): 106f. function has been added.  This
function reports the current binding of all names referenced from the
function body and where those names were resolved, making it easier to
verify correct internal state when testing code that relies on stateful
closures.

（由 Meador Inge 與 Nick Coghlan 在 bpo-13062(1) 中貢獻。）

A new *note getgeneratorlocals(): 1070. function has been added.  This
function reports the current binding of local variables in the
generator's stack frame, making it easier to verify correct internal
state when testing generators.

（由 Meador Inge 於 bpo-15153(2) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=13062

   (2) https://bugs.python.org/issue?@action=redirect&bpo=15153


File: python.info,  Node: io<6>,  Next: itertools<6>,  Prev: inspect<9>,  Up: 改進的模組<10>

1.11.20.27 io
.............

The *note open(): 4c1. function has a new ‘'x'’ mode that can be used to
exclusively create a new file, and raise a *note FileExistsError: fc3.
if the file already exists.  It is based on the C11 'x' mode to fopen().

（由 David Townshend 於 bpo-12760(1) 中貢獻。）

The constructor of the *note TextIOWrapper: 75f. class has a new
'write_through' optional argument.  If 'write_through' is ‘True’, calls
to ‘write()’ are guaranteed not to be buffered: any data written on the
*note TextIOWrapper: 75f. object is immediately handled to its
underlying binary buffer.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=12760


File: python.info,  Node: itertools<6>,  Next: logging<7>,  Prev: io<6>,  Up: 改進的模組<10>

1.11.20.28 itertools
....................

*note accumulate(): 9a1. now takes an optional ‘func’ argument for
providing a user-supplied binary function.


File: python.info,  Node: logging<7>,  Next: math<9>,  Prev: itertools<6>,  Up: 改進的模組<10>

1.11.20.29 logging
..................

The *note basicConfig(): 9a4. function now supports an optional
‘handlers’ argument taking an iterable of handlers to be added to the
root logger.

A class level attribute ‘append_nul’ has been added to *note
SysLogHandler: 602. to allow control of the appending of the ‘NUL’
(‘\000’) byte to syslog records, since for some daemons it is required
while for others it is passed through to the log.


File: python.info,  Node: math<9>,  Next: mmap<4>,  Prev: logging<7>,  Up: 改進的模組<10>

1.11.20.30 math
...............

The *note math: 81. module has a new function, *note log2(): 1075, which
returns the base-2 logarithm of 'x'.

（由 Mark Dickinson 於 bpo-11888(1) 中撰寫）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=11888


File: python.info,  Node: mmap<4>,  Next: multiprocessing<8>,  Prev: math<9>,  Up: 改進的模組<10>

1.11.20.31 mmap
...............

The *note read(): 1077. method is now more compatible with other
file-like objects: if the argument is omitted or specified as ‘None’, it
returns the bytes from the current file position to the end of the
mapping.  (Contributed by Petri Lehtinen in bpo-12021(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=12021


File: python.info,  Node: multiprocessing<8>,  Next: nntplib<2>,  Prev: mmap<4>,  Up: 改進的模組<10>

1.11.20.32 multiprocessing
..........................

The new *note multiprocessing.connection.wait(): 1079. function allows
polling multiple objects (such as connections, sockets and pipes) with a
timeout.  (Contributed by Richard Oudkerk in bpo-12328(1).)

‘multiprocessing.Connection’ objects can now be transferred over
multiprocessing connections.  (Contributed by Richard Oudkerk in
bpo-4892(2).)

*note multiprocessing.Process: afd. now accepts a ‘daemon’ keyword
argument to override the default behavior of inheriting the ‘daemon’
flag from the parent process (bpo-6064(3)).

New attribute *note multiprocessing.Process.sentinel: 107a. allows a
program to wait on multiple *note Process: afd. objects at one time
using the appropriate OS primitives (for example, *note select: af. on
posix systems).

New methods *note multiprocessing.pool.Pool.starmap(): 107b. and *note
starmap_async(): 107c. provide *note itertools.starmap(): 107d.
equivalents to the existing *note multiprocessing.pool.Pool.map(): 107e.
and *note map_async(): 107f. functions.  (Contributed by Hynek Schlawack
in bpo-12708(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=12328

   (2) https://bugs.python.org/issue?@action=redirect&bpo=4892

   (3) https://bugs.python.org/issue?@action=redirect&bpo=6064

   (4) https://bugs.python.org/issue?@action=redirect&bpo=12708


File: python.info,  Node: nntplib<2>,  Next: os<12>,  Prev: multiprocessing<8>,  Up: 改進的模組<10>

1.11.20.33 nntplib
..................

The ‘nntplib.NNTP’ class now supports the context management protocol to
unconditionally consume *note socket.error: ff8. exceptions and to close
the NNTP connection when done:

     >>> from nntplib import NNTP
     >>> with NNTP('news.gmane.org') as n:
     ...     n.group('gmane.comp.python.committers')
     ...
     ('211 1755 1 1755 gmane.comp.python.committers', 1755, 1, 1755, 'gmane.comp.python.committers')
     >>>

（由 Giampaolo Rodolà 於 bpo-9795(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=9795


File: python.info,  Node: os<12>,  Next: pdb<7>,  Prev: nntplib<2>,  Up: 改進的模組<10>

1.11.20.34 os
.............

   * The *note os: 91. module has a new *note pipe2(): 1082. function
     that makes it possible to create a pipe with *note O_CLOEXEC: 101d.
     or *note O_NONBLOCK: de1. flags set atomically.  This is especially
     useful to avoid race conditions in multi-threaded programs.

   * The *note os: 91. module has a new *note sendfile(): ab2. function
     which provides an efficient "zero-copy" way for copying data from
     one file (or socket) descriptor to another.  The phrase "zero-copy"
     refers to the fact that all of the copying of data between the two
     descriptors is done entirely by the kernel, with no copying of data
     into userspace buffers.  *note sendfile(): ab2. can be used to
     efficiently copy data from a file on disk to a network socket, e.g.
     for downloading a file.

     （由 Ross Lagerwall 和 Giampaolo Rodolà 於 bpo-10882(1) 提交補丁。
     ）

   * To avoid race conditions like symlink attacks and issues with
     temporary files and directories, it is more reliable (and also
     faster) to manipulate file descriptors instead of file names.
     Python 3.3 enhances existing functions and introduces new functions
     to work on file descriptors (bpo-4761(2), bpo-10755(3) and
     bpo-14626(4)).

        - The *note os: 91. module has a new *note fwalk(): aff.
          function similar to *note walk(): 451. except that it also
          yields file descriptors referring to the directories visited.
          This is especially useful to avoid symlink races.

        - The following functions get new optional 'dir_fd' (*note paths
          relative to directory descriptors: 1083.) and/or
          'follow_symlinks' (*note not following symlinks: 1084.): *note
          access(): 1085, *note chflags(): 1086, *note chmod(): 200,
          *note chown(): 1087, *note link(): 1088, *note lstat(): 449,
          *note mkdir(): 202, *note mkfifo(): d36, *note mknod(): d37,
          *note open(): d38, *note readlink(): 8c5, *note remove():
          1089, *note rename(): 108a, *note replace(): 108b, *note
          rmdir(): 108c, *note stat(): 448, *note symlink(): 108d, *note
          unlink(): 108e, *note utime(): 108f.  Platform support for
          using these parameters can be checked via the sets *note
          os.supports_dir_fd: 1090. and ‘os.supports_follows_symlinks’.

        - The following functions now support a file descriptor for
          their path argument: *note chdir(): 5b2, *note chmod(): 200,
          *note chown(): 1087, *note execve(): 1091, *note listdir():
          1092, *note pathconf(): 1093, *note exists(): 9b2, *note
          stat(): 448, *note statvfs(): 1094, *note utime(): 108f.
          Platform support for this can be checked via the *note
          os.supports_fd: 1095. set.

   * *note access(): 1085. accepts an ‘effective_ids’ keyword argument
     to turn on using the effective uid/gid rather than the real uid/gid
     in the access check.  Platform support for this can be checked via
     the *note supports_effective_ids: 1096. set.

   * The *note os: 91. module has two new functions: *note
     getpriority(): 1097. and *note setpriority(): 1098.  They can be
     used to get or set process niceness/priority in a fashion similar
     to *note os.nice(): 1099. but extended to all processes instead of
     just the current one.

     （由 Giampaolo Rodolà 於 bpo-10784(5) 提交補丁。）

   * The new *note os.replace(): 108b. function allows cross-platform
     renaming of a file with overwriting the destination.  With *note
     os.rename(): 108a, an existing destination file is overwritten
     under POSIX, but raises an error under Windows.  (Contributed by
     Antoine Pitrou in bpo-8828(6).)

   * The stat family of functions (*note stat(): 448, *note fstat():
     d32, and *note lstat(): 449.) now support reading a file's
     timestamps with nanosecond precision.  Symmetrically, *note
     utime(): 108f. can now write file timestamps with nanosecond
     precision.  (Contributed by Larry Hastings in bpo-14127(7).)

   * The new *note os.get_terminal_size(): 109a. function queries the
     size of the terminal attached to a file descriptor.  See also *note
     shutil.get_terminal_size(): 109b.  (Contributed by Zbigniew
     Jędrzejewski-Szmek in bpo-13609(8).)

   * New functions to support Linux extended attributes (bpo-12720(9)):
     *note getxattr(): 109c, *note listxattr(): 109d, *note
     removexattr(): 109e, *note setxattr(): 109f.

   * New interface to the scheduler.  These functions control how a
     process is allocated CPU time by the operating system.  New
     functions: *note sched_get_priority_max(): 10a0, *note
     sched_get_priority_min(): 10a1, *note sched_getaffinity(): 10a2,
     *note sched_getparam(): 10a3, *note sched_getscheduler(): 10a4,
     *note sched_rr_get_interval(): 10a5, *note sched_setaffinity():
     10a6, *note sched_setparam(): 10a7, *note sched_setscheduler():
     10a8, *note sched_yield(): 10a9,

   * New functions to control the file system:

        * *note posix_fadvise(): d39.: Announces an intention to access
          data in a specific pattern thus allowing the kernel to make
          optimizations.

        * *note posix_fallocate(): d3a.: Ensures that enough disk space
          is allocated for a file.

        * *note sync(): 10aa.: Force write of everything to disk.

   * 其他新的 posix 函式：

        * *note lockf(): 10ab.: Apply, test or remove a POSIX lock on an
          open file descriptor.

        * *note pread(): b03.: Read from a file descriptor at an offset,
          the file offset remains unchanged.

        * *note pwrite(): b06.: Write to a file descriptor from an
          offset, leaving the file offset unchanged.

        * *note readv(): b02.: Read from a file descriptor into a number
          of writable buffers.

        * *note truncate(): de2.: Truncate the file corresponding to
          'path', so that it is at most 'length' bytes in size.

        * *note waitid(): d3f.: Wait for the completion of one or more
          child processes.

        * *note writev(): b05.: Write the contents of 'buffers' to a
          file descriptor, where 'buffers' is an arbitrary sequence of
          buffers.

        * *note getgrouplist(): 10ac. (bpo-9344(10)): Return list of
          group ids that specified user belongs to.

   * *note times(): 10ad. and *note uname(): 10ae.: Return type changed
     from a tuple to a tuple-like object with named attributes.

   * Some platforms now support additional constants for the *note
     lseek(): 10af. function, such as ‘os.SEEK_HOLE’ and ‘os.SEEK_DATA’.

   * New constants *note RTLD_LAZY: 10b0, *note RTLD_NOW: 10b1, *note
     RTLD_GLOBAL: 10b2, *note RTLD_LOCAL: 10b3, *note RTLD_NODELETE:
     10b4, *note RTLD_NOLOAD: 10b5, and *note RTLD_DEEPBIND: 10b6. are
     available on platforms that support them.  These are for use with
     the *note sys.setdlopenflags(): 10b7. function, and supersede the
     similar constants defined in *note ctypes: 22. and ‘DLFCN’.
     (Contributed by Victor Stinner in bpo-13226(11).)

   * *note os.symlink(): 108d. now accepts (and ignores) the
     ‘target_is_directory’ keyword argument on non-Windows platforms, to
     ease cross-platform support.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=10882

   (2) https://bugs.python.org/issue?@action=redirect&bpo=4761

   (3) https://bugs.python.org/issue?@action=redirect&bpo=10755

   (4) https://bugs.python.org/issue?@action=redirect&bpo=14626

   (5) https://bugs.python.org/issue?@action=redirect&bpo=10784

   (6) https://bugs.python.org/issue?@action=redirect&bpo=8828

   (7) https://bugs.python.org/issue?@action=redirect&bpo=14127

   (8) https://bugs.python.org/issue?@action=redirect&bpo=13609

   (9) https://bugs.python.org/issue?@action=redirect&bpo=12720

   (10) https://bugs.python.org/issue?@action=redirect&bpo=9344

   (11) https://bugs.python.org/issue?@action=redirect&bpo=13226


File: python.info,  Node: pdb<7>,  Next: pickle<5>,  Prev: os<12>,  Up: 改進的模組<10>

1.11.20.35 pdb
..............

Tab-completion is now available not only for command names, but also
their arguments.  For example, for the ‘break’ command, function and
file names are completed.

（由 Georg Brandl 在 bpo-14210(1) 中貢獻）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=14210


File: python.info,  Node: pickle<5>,  Next: pydoc<5>,  Prev: pdb<7>,  Up: 改進的模組<10>

1.11.20.36 pickle
.................

*note pickle.Pickler: 9c2. objects now have an optional *note
dispatch_table: 10ba. attribute allowing per-pickler reduction functions
to be set.

（由 Richard Oudkerk 在 bpo-14166(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=14166


File: python.info,  Node: pydoc<5>,  Next: re<9>,  Prev: pickle<5>,  Up: 改進的模組<10>

1.11.20.37 pydoc
................

The Tk GUI and the ‘serve()’ function have been removed from the *note
pydoc: a3. module: ‘pydoc -g’ and ‘serve()’ have been deprecated in
Python 3.2.


File: python.info,  Node: re<9>,  Next: sched,  Prev: pydoc<5>,  Up: 改進的模組<10>

1.11.20.38 re
.............

*note str: 3f2. regular expressions now support ‘\u’ and ‘\U’ escapes.

（由 Serhiy Storchaka 在 bpo-3665(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=3665


File: python.info,  Node: sched,  Next: select<2>,  Prev: re<9>,  Up: 改進的模組<10>

1.11.20.39 sched
................

   * *note run(): 10be. now accepts a 'blocking' parameter which when
     set to false makes the method execute the scheduled events due to
     expire soonest (if any) and then return immediately.  This is
     useful in case you want to use the *note scheduler: 10bf. in
     non-blocking applications.  (Contributed by Giampaolo Rodolà in
     bpo-13449(1).)

   * *note scheduler: 10bf. class can now be safely used in
     multi-threaded environments.  (Contributed by Josiah Carlson and
     Giampaolo Rodolà in bpo-8684(2).)

   * 'timefunc' and 'delayfunct' parameters of *note scheduler: 10bf.
     class constructor are now optional and defaults to *note
     time.time(): 239. and *note time.sleep(): 642. respectively.
     (Contributed by Chris Clark in bpo-13245(3).)

   * *note enter(): 10c0. 和 *note enterabs(): 10c1. 'argument' 參數現在
     是可選的。（由 Chris Clark 在 bpo-13245(4) 中貢獻。）

   * *note enter(): 10c0. 和 *note enterabs(): 10c1. 現在接受 'kwargs' 參
     數。（由 Chris Clark 在 bpo-13245(5) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=13449

   (2) https://bugs.python.org/issue?@action=redirect&bpo=8684

   (3) https://bugs.python.org/issue?@action=redirect&bpo=13245

   (4) https://bugs.python.org/issue?@action=redirect&bpo=13245

   (5) https://bugs.python.org/issue?@action=redirect&bpo=13245


File: python.info,  Node: select<2>,  Next: shlex<3>,  Prev: sched,  Up: 改進的模組<10>

1.11.20.40 select
.................

Solaris and derivative platforms have a new class *note select.devpoll:
f38. for high performance asynchronous sockets via ‘/dev/poll’.
(Contributed by Jesús Cea Avión in bpo-6397(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=6397


File: python.info,  Node: shlex<3>,  Next: shutil<7>,  Prev: select<2>,  Up: 改進的模組<10>

1.11.20.41 shlex
................

The previously undocumented helper function ‘quote’ from the ‘pipes’
modules has been moved to the *note shlex: b2. module and documented.
*note quote(): 10c4. properly escapes all characters in a string that
might be otherwise given special meaning by the shell.


File: python.info,  Node: shutil<7>,  Next: signal<4>,  Prev: shlex<3>,  Up: 改進的模組<10>

1.11.20.42 shutil
.................

   * 新功能：

        * *note disk_usage(): 10c6.: provides total, used and free disk
          space statistics.  (Contributed by Giampaolo Rodolà in
          bpo-12442(1).)

        * *note chown(): 225.: allows one to change user and/or group of
          the given path also specifying the user/group names and not
          only their numeric ids.  (Contributed by Sandro Tosi in
          bpo-12191(2).)

        * *note shutil.get_terminal_size(): 109b.: returns the size of
          the terminal window to which the interpreter is attached.
          (Contributed by Zbigniew Jędrzejewski-Szmek in bpo-13609(3).)

   * *note copy2(): 9fe. and *note copystat(): 10c7. now preserve file
     timestamps with nanosecond precision on platforms that support it.
     They also preserve file "extended attributes" on Linux.
     (Contributed by Larry Hastings in bpo-14127(4) and bpo-15238(5).)

   * Several functions now take an optional ‘symlinks’ argument: when
     that parameter is true, symlinks aren't dereferenced and the
     operation instead acts on the symlink itself (or creates one, if
     relevant).  (Contributed by Hynek Schlawack in bpo-12715(6).)

   * When copying files to a different file system, *note move(): 9ff.
     now handles symlinks the way the posix ‘mv’ command does,
     recreating the symlink rather than copying the target file
     contents.  (Contributed by Jonathan Niehof in bpo-9993(7).)  *note
     move(): 9ff. now also returns the ‘dst’ argument as its result.

   * *note rmtree(): 2d2. is now resistant to symlink attacks on
     platforms which support the new ‘dir_fd’ parameter in *note
     os.open(): d38. and *note os.unlink(): 108e.  (Contributed by
     Martin von Löwis and Hynek Schlawack in bpo-4489(8).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=12442

   (2) https://bugs.python.org/issue?@action=redirect&bpo=12191

   (3) https://bugs.python.org/issue?@action=redirect&bpo=13609

   (4) https://bugs.python.org/issue?@action=redirect&bpo=14127

   (5) https://bugs.python.org/issue?@action=redirect&bpo=15238

   (6) https://bugs.python.org/issue?@action=redirect&bpo=12715

   (7) https://bugs.python.org/issue?@action=redirect&bpo=9993

   (8) https://bugs.python.org/issue?@action=redirect&bpo=4489


File: python.info,  Node: signal<4>,  Next: smtpd<4>,  Prev: shutil<7>,  Up: 改進的模組<10>

1.11.20.43 signal
.................

   * *note signal: b4. 模組有了新的函式：

        * *note pthread_sigmask(): 10c9.: fetch and/or change the signal
          mask of the calling thread (Contributed by Jean-Paul Calderone
          in bpo-8407(1));

        * *note pthread_kill(): 10ca.：向執行緒發送訊號；

        * *note sigpending(): 10cb.：檢查未定的函式；

        * *note sigwait(): 10cc.：等待訊號；

        * *note sigwaitinfo(): d51.：等待訊號，回傳有關該訊號的詳細資訊
          ；

        * *note sigtimedwait(): d50.：類似於 *note sigwaitinfo(): d51. 但
          有超時。

   * The signal handler writes the signal number as a single byte
     instead of a nul byte into the wakeup file descriptor.  So it is
     possible to wait more than one signal and know which signals were
     raised.

   * *note signal.signal(): 10cd. 和 *note signal.siginterrupt(): 10ce.
     會引發 OSError，而不是 RuntimeError：OSError 有一個 errno 屬性。

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=8407


File: python.info,  Node: smtpd<4>,  Next: smtplib<4>,  Prev: signal<4>,  Up: 改進的模組<10>

1.11.20.44 smtpd
................

The ‘smtpd’ module now supports RFC 5321(1) (extended SMTP) and RFC
1870(2) (size extension).  Per the standard, these extensions are
enabled if and only if the client initiates the session with an ‘EHLO’
command.

(Initial ‘ELHO’ support by Alberto Trevino.  Size extension by Juhana
Jauhiainen.  Substantial additional work on the patch contributed by
Michele Orrù and Dan Boswell.  bpo-8739(3))

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc5321.html

   (2) https://datatracker.ietf.org/doc/html/rfc1870.html

   (3) https://bugs.python.org/issue?@action=redirect&bpo=8739


File: python.info,  Node: smtplib<4>,  Next: socket<10>,  Prev: smtpd<4>,  Up: 改進的模組<10>

1.11.20.45 smtplib
..................

The *note SMTP: 8d1, *note SMTP_SSL: 8d2, and *note LMTP: 8d3. classes
now accept a ‘source_address’ keyword argument to specify the ‘(host,
port)’ to use as the source address in the bind call when creating the
outgoing socket.  (Contributed by Paulo Scardine in bpo-11281(1).)

*note SMTP: 8d1. 現在支援情境管理協議，允許在 ‘with’ 陳述式中使用 ‘SMTP’
實例。（由 Giampaolo Rodolà 在 bpo-11289(2) 中貢獻。）

*note SMTP_SSL: 8d2. 構造函式和 *note starttls(): 10d1. 方法現在接受
SSLContext 參數來控制安全通道的參數。（由 Kasun Herath 在 bpo-8809(3) 中
貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=11281

   (2) https://bugs.python.org/issue?@action=redirect&bpo=11289

   (3) https://bugs.python.org/issue?@action=redirect&bpo=8809


File: python.info,  Node: socket<10>,  Next: socketserver<3>,  Prev: smtplib<4>,  Up: 改進的模組<10>

1.11.20.46 socket
.................

   * 當底層平台支援時，*note socket: d47. 類現在公開了額外的方法來處理輔
     助資料：

        * *note sendmsg(): 41d.

        * *note recvmsg(): d4c.

        * *note recvmsg_into(): 10d3.

     （由 David Watson 在 bpo-6560(1) 中貢獻，其基於 Heiko Wundram 的早
     期補丁）

   * *note socket: d47. 類別現在支援 Linux
     (‘https://lwn.net/Articles/253425’) 上的 PF_CAN 協議系列
     (‘https://en.wikipedia.org/wiki/Socketcan’)。

     （在 bpo-10141(2) 中由 Matthias Fuchs 貢獻、並由 Tiago Gonçalves 更
     新。）

   * *note socket: d47. 類別現在支援 PF_RDS 協議系列（
     ‘https://en.wikipedia.org/wiki/Reliable_Datagram_Sockets’ 和
     https://oss.oracle.com/projects/rds(3)）。

   * *note socket: d47. 類別現在支援 OS X 上的 ‘PF_SYSTEM’ 協議系列。（
     由 Michael Goderbauer 在 bpo-13777(4) 中貢獻。）

   * New function *note sethostname(): 10d4. allows the hostname to be
     set on Unix systems if the calling process has sufficient
     privileges.  (Contributed by Ross Lagerwall in bpo-10866(5).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=6560

   (2) https://bugs.python.org/issue?@action=redirect&bpo=10141

   (3) 
https://web.archive.org/web/20130115155505/https://oss.oracle.com/projects/rds/

   (4) https://bugs.python.org/issue?@action=redirect&bpo=13777

   (5) https://bugs.python.org/issue?@action=redirect&bpo=10866


File: python.info,  Node: socketserver<3>,  Next: sqlite3<10>,  Prev: socket<10>,  Up: 改進的模組<10>

1.11.20.47 socketserver
.......................

*note BaseServer: 10d6. now has an overridable method *note
service_actions(): 10d7. that is called by the *note serve_forever():
10d8. method in the service loop.  *note ForkingMixIn: b1b. now uses
this to clean up zombie child processes.  (Contributed by Justin
Warkentin in bpo-11109(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=11109


File: python.info,  Node: sqlite3<10>,  Next: ssl<11>,  Prev: socketserver<3>,  Up: 改進的模組<10>

1.11.20.48 sqlite3
..................

New *note sqlite3.Connection: 22a. method *note set_trace_callback():
28d. can be used to capture a trace of all sql commands processed by
sqlite.  (Contributed by Torsten Landschoff in bpo-11688(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=11688


File: python.info,  Node: ssl<11>,  Next: stat<2>,  Prev: sqlite3<10>,  Up: 改進的模組<10>

1.11.20.49 ssl
..............

   * *note ssl: bb. 模組有兩個新的隨機生成函式：

        * *note RAND_bytes(): 4c8.：生成加密的強偽隨機位元組。

        * ‘RAND_pseudo_bytes()’：生成偽隨機位元組。

     （由 Victor Stinner 在 bpo-12049(1) 中貢獻。）

   * The *note ssl: bb. module now exposes a finer-grained exception
     hierarchy in order to make it easier to inspect the various kinds
     of errors.  (Contributed by Antoine Pitrou in bpo-11183(2).)

   * *note load_cert_chain(): 277. now accepts a 'password' argument to
     be used if the private key is encrypted.  (Contributed by Adam
     Simpkins in bpo-12803(3).)

   * Diffie-Hellman key exchange, both regular and Elliptic Curve-based,
     is now supported through the *note load_dh_params(): 10db. and
     *note set_ecdh_curve(): 10dc. methods.  (Contributed by Antoine
     Pitrou in bpo-13626(4) and bpo-13627(5).)

   * SSL sockets have a new *note get_channel_binding(): 10dd. method
     allowing the implementation of certain authentication mechanisms
     such as SCRAM-SHA-1-PLUS. (Contributed by Jacek Konieczny in
     bpo-12551(6).)

   * You can query the SSL compression algorithm used by an SSL socket,
     thanks to its new *note compression(): 10de. method.  The new
     attribute *note OP_NO_COMPRESSION: 10df. can be used to disable
     compression.  (Contributed by Antoine Pitrou in bpo-13634(7).)

   * Support has been added for the Next Protocol Negotiation extension
     using the *note ssl.SSLContext.set_npn_protocols(): 2d3. method.
     (Contributed by Colin Marc in bpo-14204(8).)

   * SSL errors can now be introspected more easily thanks to *note
     library: 10e0. and *note reason: 10e1. attributes.  (Contributed by
     Antoine Pitrou in bpo-14837(9).)

   * The *note get_server_certificate(): 7e0. function now supports
     IPv6.  (Contributed by Charles-François Natali in bpo-11811(10).)

   * New attribute *note OP_CIPHER_SERVER_PREFERENCE: 10e2. allows
     setting SSLv3 server sockets to use the server's cipher ordering
     preference rather than the client's (bpo-13635(11)).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=12049

   (2) https://bugs.python.org/issue?@action=redirect&bpo=11183

   (3) https://bugs.python.org/issue?@action=redirect&bpo=12803

   (4) https://bugs.python.org/issue?@action=redirect&bpo=13626

   (5) https://bugs.python.org/issue?@action=redirect&bpo=13627

   (6) https://bugs.python.org/issue?@action=redirect&bpo=12551

   (7) https://bugs.python.org/issue?@action=redirect&bpo=13634

   (8) https://bugs.python.org/issue?@action=redirect&bpo=14204

   (9) https://bugs.python.org/issue?@action=redirect&bpo=14837

   (10) https://bugs.python.org/issue?@action=redirect&bpo=11811

   (11) https://bugs.python.org/issue?@action=redirect&bpo=13635


File: python.info,  Node: stat<2>,  Next: struct<3>,  Prev: ssl<11>,  Up: 改進的模組<10>

1.11.20.50 stat
...............

The undocumented tarfile.filemode function has been moved to *note
stat.filemode(): 10e4.  It can be used to convert a file's mode to a
string of the form '-rwxrwxrwx'.

（由 Giampaolo Rodolà 在 bpo-14807(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=14807


File: python.info,  Node: struct<3>,  Next: subprocess<6>,  Prev: stat<2>,  Up: 改進的模組<10>

1.11.20.51 struct
.................

The *note struct: c0. module now supports ‘ssize_t’ and ‘size_t’ via the
new codes ‘n’ and ‘N’, respectively.  (Contributed by Antoine Pitrou in
bpo-3163(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=3163


File: python.info,  Node: subprocess<6>,  Next: sys<12>,  Prev: struct<3>,  Up: 改進的模組<10>

1.11.20.52 subprocess
.....................

Command strings can now be bytes objects on posix platforms.
(Contributed by Victor Stinner in bpo-8513(1).)

A new constant *note DEVNULL: 10e7. allows suppressing output in a
platform-independent fashion.  (Contributed by Ross Lagerwall in
bpo-5870(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=8513

   (2) https://bugs.python.org/issue?@action=redirect&bpo=5870


File: python.info,  Node: sys<12>,  Next: tarfile<8>,  Prev: subprocess<6>,  Up: 改進的模組<10>

1.11.20.53 sys
..............

The *note sys: c3. module has a new *note thread_info: 10e9. *note named
tuple: 5f4. holding information about the thread implementation
(bpo-11223(1)).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=11223


File: python.info,  Node: tarfile<8>,  Next: tempfile<4>,  Prev: sys<12>,  Up: 改進的模組<10>

1.11.20.54 tarfile
..................

*note tarfile: c8. 現在透過 *note lzma: 7e. 模組支援 ‘lzma’ 編碼。（由
Lars Gustäbel 在 bpo-5689(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=5689


File: python.info,  Node: tempfile<4>,  Next: textwrap<2>,  Prev: tarfile<8>,  Up: 改進的模組<10>

1.11.20.55 tempfile
...................

*note tempfile.SpooledTemporaryFile: 639.'s ‘truncate()’ method now
accepts a ‘size’ parameter.  (Contributed by Ryan Kelly in bpo-9957(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=9957


File: python.info,  Node: textwrap<2>,  Next: threading<8>,  Prev: tempfile<4>,  Up: 改進的模組<10>

1.11.20.56 textwrap
...................

The *note textwrap: d5. module has a new *note indent(): 25b. that makes
it straightforward to add a common prefix to selected lines in a block
of text (bpo-13857(1)).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=13857


File: python.info,  Node: threading<8>,  Next: time<8>,  Prev: textwrap<2>,  Up: 改進的模組<10>

1.11.20.57 threading
....................

*note threading.Condition: 10ee, *note threading.Semaphore: 10ef, *note
threading.BoundedSemaphore: 10f0, *note threading.Event: 10f1, and *note
threading.Timer: 10f2, all of which used to be factory functions
returning a class instance, are now classes and may be subclassed.
(Contributed by Éric Araujo in bpo-10968(1).)

The *note threading.Thread: 8f0. constructor now accepts a ‘daemon’
keyword argument to override the default behavior of inheriting the
‘daemon’ flag value from the parent thread (bpo-6064(2)).

The formerly private function ‘_thread.get_ident’ is now available as
the public function *note threading.get_ident(): 10f3.  This eliminates
several cases of direct access to the ‘_thread’ module in the stdlib.
Third party code that used ‘_thread.get_ident’ should likewise be
changed to use the new public interface.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=10968

   (2) https://bugs.python.org/issue?@action=redirect&bpo=6064


File: python.info,  Node: time<8>,  Next: types<7>,  Prev: threading<8>,  Up: 改進的模組<10>

1.11.20.58 time
...............

PEP 418(1) 向 *note time: d7. 模組新增了新功能：

   * *note get_clock_info(): 10f5.：獲取時鐘資訊。

   * *note monotonic(): 238.：單調時鐘（不能倒退），不受系統時鐘更新的影
     響。

   * *note perf_counter(): a2b.: Performance counter with the highest
     available resolution to measure a short duration.

   * *note process_time(): a2c.：當前行程的系統和使用者 CPU 時間總和。

其他新功能：

   * *note clock_getres(): 10f6.、*note clock_gettime(): 10f7. 和 *note
     clock_settime(): 10f8. 函式帶有 ‘CLOCK_XXX’ 常數。（由 Victor
     Stinner 在 bpo-10278(2) 中貢獻。）

To improve cross platform consistency, *note sleep(): 642. now raises a
*note ValueError: 1e7. when passed a negative sleep value.  Previously
this was an error on posix, but produced an infinite sleep on Windows.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0418/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=10278


File: python.info,  Node: types<7>,  Next: unittest<10>,  Prev: time<8>,  Up: 改進的模組<10>

1.11.20.59 types
................

Add a new *note types.MappingProxyType: 414. class: Read-only proxy of a
mapping.  (bpo-14386(1))

The new functions *note types.new_class(): 10fa. and *note
types.prepare_class(): 10fb. provide support for PEP 3115(2) compliant
dynamic type creation.  (bpo-14588(3))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=14386

   (2) https://peps.python.org/pep-3115/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=14588


File: python.info,  Node: unittest<10>,  Next: urllib<4>,  Prev: types<7>,  Up: 改進的模組<10>

1.11.20.60 unittest
...................

*note assertRaises(): 4d1, *note assertRaisesRegex(): 4d3, *note
assertWarns(): 10fd, and *note assertWarnsRegex(): 10fe. now accept a
keyword argument 'msg' when used as context managers.  (Contributed by
Ezio Melotti and Winston Ewert in bpo-10775(1).)

*note unittest.TestCase.run(): 10ff. 現在回傳 *note TestResult: 1100. 物
件。

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=10775


File: python.info,  Node: urllib<4>,  Next: webbrowser<3>,  Prev: unittest<10>,  Up: 改進的模組<10>

1.11.20.61 urllib
.................

The *note Request: f7b. class, now accepts a 'method' argument used by
*note get_method(): 1102. to determine what HTTP method should be used.
For example, this will send a ‘'HEAD'’ request:

     >>> urlopen(Request('https://www.python.org', method='HEAD'))

(bpo-1673007(1))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1673007


File: python.info,  Node: webbrowser<3>,  Next: xml etree ElementTree<2>,  Prev: urllib<4>,  Up: 改進的模組<10>

1.11.20.62 webbrowser
.....................

The *note webbrowser: fd. module supports more "browsers": Google Chrome
(named ‘chrome’, ‘chromium’, ‘chrome-browser’ or ‘chromium-browser’
depending on the version and operating system), and the generic
launchers ‘xdg-open’, from the FreeDesktop.org project, and ‘gvfs-open’,
which is the default URI handler for GNOME 3.  (The former contributed
by Arnaud Calmettes in bpo-13620(1), the latter by Matthias Klose in
bpo-14493(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=13620

   (2) https://bugs.python.org/issue?@action=redirect&bpo=14493


File: python.info,  Node: xml etree ElementTree<2>,  Next: zlib<2>,  Prev: webbrowser<3>,  Up: 改進的模組<10>

1.11.20.63 xml.etree.ElementTree
................................

The *note xml.etree.ElementTree: 10c. module now imports its C
accelerator by default; there is no longer a need to explicitly import
‘xml.etree.cElementTree’ (this module stays for backwards compatibility,
but is now deprecated).  In addition, the ‘iter’ family of methods of
*note Element: 2e2. has been optimized (rewritten in C). The module's
documentation has also been greatly improved with added examples and a
more detailed reference.


File: python.info,  Node: zlib<2>,  Prev: xml etree ElementTree<2>,  Up: 改進的模組<10>

1.11.20.64 zlib
...............

New attribute *note zlib.Decompress.eof: 1106. makes it possible to
distinguish between a properly formed compressed stream and an
incomplete or truncated one.  (Contributed by Nadeem Vawda in
bpo-12646(1).)

New attribute *note zlib.ZLIB_RUNTIME_VERSION: 1107. reports the version
string of the underlying ‘zlib’ library that is loaded at runtime.
(Contributed by Torsten Landschoff in bpo-12306(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=12646

   (2) https://bugs.python.org/issue?@action=redirect&bpo=12306


File: python.info,  Node: 最佳化<9>,  Next: 建置和 C API 更改,  Prev: 改進的模組<10>,  Up: Python 3 3 有什麼新功能

1.11.21 最佳化
--------------

Major performance enhancements have been added:

   * Thanks to PEP 393(1), some operations on Unicode strings have been
     optimized:

        * the memory footprint is divided by 2 to 4 depending on the
          text

        * encode an ASCII string to UTF-8 doesn't need to encode
          characters anymore, the UTF-8 representation is shared with
          the ASCII representation

        * the UTF-8 encoder has been optimized

        * repeating a single ASCII letter and getting a substring of an
          ASCII string is 4 times faster

   * UTF-8 is now 2x to 4x faster.  UTF-16 encoding is now up to 10x
     faster.

     （由 Serhiy Storchaka 於 bpo-14624(2)、bpo-14738(3) 和 bpo-15026(4)
     貢獻。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0393/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=14624

   (3) https://bugs.python.org/issue?@action=redirect&bpo=14738

   (4) https://bugs.python.org/issue?@action=redirect&bpo=15026


File: python.info,  Node: 建置和 C API 更改,  Next: 已棄用<12>,  Prev: 最佳化<9>,  Up: Python 3 3 有什麼新功能

1.11.22 建置和 C API 更改
-------------------------

Python 建置程序和 C API 的更改包括：

   * 新的 PEP 3118(1) 相關功能：

        * *note PyMemoryView_FromMemory(): 1109.

   * PEP 393(2) added new Unicode types, macros and functions:

        * 高階 API：

             * *note PyUnicode_CopyCharacters(): 85a.

             * *note PyUnicode_FindChar(): 85e.

             * *note PyUnicode_GetLength(): 858, *note
               PyUnicode_GET_LENGTH: 859.

             * *note PyUnicode_New(): 850.

             * *note PyUnicode_Substring(): 85b.

             * *note PyUnicode_ReadChar(): 110a, *note
               PyUnicode_WriteChar(): 110b.

        * 低階 API：

             * *note Py_UCS1: 110c.、*note Py_UCS2: 110d.、*note
               Py_UCS4: 110e. 型別

             * *note PyASCIIObject: 110f. 和 *note
               PyCompactUnicodeObject: 1110. 結構

             * *note PyUnicode_READY: 3c9.

             * *note PyUnicode_FromKindAndData(): 1111.

             * *note PyUnicode_AsUCS4(): 1112, *note
               PyUnicode_AsUCS4Copy(): 860.

             * *note PyUnicode_DATA: 1113, *note PyUnicode_1BYTE_DATA:
               1114, *note PyUnicode_2BYTE_DATA: 1115, *note
               PyUnicode_4BYTE_DATA: 1116.

             * *note PyUnicode_KIND: 1117. with ‘PyUnicode_Kind’ enum:
               ‘PyUnicode_WCHAR_KIND’, *note PyUnicode_1BYTE_KIND: 1118,
               *note PyUnicode_2BYTE_KIND: 1119, *note
               PyUnicode_4BYTE_KIND: 111a.

             * *note PyUnicode_READ: 111b, *note PyUnicode_READ_CHAR:
               111c, *note PyUnicode_WRITE: 111d.

             * *note PyUnicode_MAX_CHAR_VALUE: 111e.

   * *note PyArg_ParseTuple: 517. 現在接受 *note bytearray: 4e3. 為 ‘c’
     格式 (bpo-12380(3))。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3118/

   (2) https://peps.python.org/pep-0393/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=12380


File: python.info,  Node: 已棄用<12>,  Next: 移植到 Python 3 3,  Prev: 建置和 C API 更改,  Up: Python 3 3 有什麼新功能

1.11.23 已棄用
--------------

* Menu:

* 不支援的作業系統::
* 已棄用的 Python 模組、函式和方法::
* C API 中已棄用的函式和型別::
* 已棄用的功能::


File: python.info,  Node: 不支援的作業系統,  Next: 已棄用的 Python 模組、函式和方法,  Up: 已棄用<12>

1.11.23.1 不支援的作業系統
..........................

由於缺乏維護者，OS/2 和 VMS 不再受支援。

Windows 2000 and Windows platforms which set ‘COMSPEC’ to ‘command.com’
are no longer supported due to maintenance burden.

OSF 支援在 3.2 中已棄用，現已完全刪除。


File: python.info,  Node: 已棄用的 Python 模組、函式和方法,  Next: C API 中已棄用的函式和型別,  Prev: 不支援的作業系統,  Up: 已棄用<12>

1.11.23.2 已棄用的 Python 模組、函式和方法
..........................................

   * Passing a non-empty string to ‘object.__format__()’ is deprecated,
     and will produce a *note TypeError: 4dd. in Python 3.4
     (bpo-9856(1)).

   * The ‘unicode_internal’ codec has been deprecated because of the PEP
     393(2), use UTF-8, UTF-16 (‘utf-16-le’ or ‘utf-16-be’), or UTF-32
     (‘utf-32-le’ or ‘utf-32-be’)

   * *note ftplib.FTP.nlst(): 105d. 和 *note ftplib.FTP.dir(): 105e.：使
     用 *note ftplib.FTP.mlsd(): 105c.

   * ‘platform.popen()’：使用 *note subprocess: c1. 模組。請特別檢查
     *note Replacing Older Functions with the subprocess Module: 1122. 部
     分 (bpo-11377(3))。

   * bpo-13374(4): The Windows bytes API has been deprecated in the
     *note os: 91. module.  Use Unicode filenames, instead of bytes
     filenames, to not depend on the ANSI code page anymore and to
     support any filename.

   * bpo-13988(5): The ‘xml.etree.cElementTree’ module is deprecated.
     The accelerator is used automatically whenever available.

   * The behaviour of ‘time.clock()’ depends on the platform: use the
     new *note time.perf_counter(): a2b. or *note time.process_time():
     a2c. function instead, depending on your requirements, to have a
     well defined behaviour.

   * ‘os.stat_float_times()’ 函式已棄用。

   * *note abc: 4. 模組：

        * *note abc.abstractproperty: 1026. 已被棄用，請改 *note
          property: 180. 和 *note abc.abstractmethod(): 1027.。

        * *note abc.abstractclassmethod: 1028. 已被棄用，請改用 *note
          classmethod: 14a. 和 *note abc.abstractmethod(): 1027.。

        * *note abc.abstractstaticmethod: 1029. 已被棄用，請改用 *note
          staticmethod: 358. 和 *note abc.abstractmethod(): 1027.。

   * *note importlib: 6b. 套件：

        * *note importlib.abc.SourceLoader.path_mtime(): 1123. is now
          deprecated in favour of *note
          importlib.abc.SourceLoader.path_stats(): 1124. as bytecode
          files now store both the modification time and size of the
          source file the bytecode file was compiled from.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=9856

   (2) https://peps.python.org/pep-0393/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=11377

   (4) https://bugs.python.org/issue?@action=redirect&bpo=13374

   (5) https://bugs.python.org/issue?@action=redirect&bpo=13988


File: python.info,  Node: C API 中已棄用的函式和型別,  Next: 已棄用的功能,  Prev: 已棄用的 Python 模組、函式和方法,  Up: 已棄用<12>

1.11.23.3 C API 中已棄用的函式和型別
....................................

*note Py_UNICODE: 3b8. 已被 PEP 393(1) 棄用，並將在 Python 4 中刪除。所
有使用此型別的函式均已棄用：

Unicode functions and methods using *note Py_UNICODE: 3b8. and *note
Py_UNICODE: 3b8.* types:

   * ‘PyUnicode_FromUnicode’：使用 *note PyUnicode_FromWideChar(): 1126.
     或 *note PyUnicode_FromKindAndData(): 1111.

   * ‘PyUnicode_AS_UNICODE’、‘PyUnicode_AsUnicode()’、
     ‘PyUnicode_AsUnicodeAndSize()’：使用 *note
     PyUnicode_AsWideCharString(): 861.

   * ‘PyUnicode_AS_DATA’：將 *note PyUnicode_DATA: 1113. 與 *note
     PyUnicode_READ: 111b. 和 *note PyUnicode_WRITE: 111d. 一起使用

   * ‘PyUnicode_GET_SIZE’、‘PyUnicode_GetSize()’：使用 *note
     PyUnicode_GET_LENGTH: 859. 或 *note PyUnicode_GetLength(): 858.

   * ‘PyUnicode_GET_DATA_SIZE’：使用 ‘PyUnicode_GET_LENGTH(str) *
     PyUnicode_KIND(str)’（僅適用於準備好的字串）

   * ‘PyUnicode_AsUnicodeCopy()’：使用 *note PyUnicode_AsUCS4Copy():
     860. 或 *note PyUnicode_AsWideCharString(): 861.

   * ‘PyUnicode_GetMax()’

操作 Py_UNICODE* 字串的函式和巨集：

   * ‘Py_UNICODE_strlen()’：使用 *note PyUnicode_GetLength(): 858. 或
     *note PyUnicode_GET_LENGTH: 859.

   * ‘Py_UNICODE_strcat()’：使用 *note PyUnicode_CopyCharacters(): 85a.
     或 *note PyUnicode_FromFormat(): 33f.

   * ‘Py_UNICODE_strcpy()’、‘Py_UNICODE_strncpy()’、
     ‘Py_UNICODE_COPY()’：使用 *note PyUnicode_CopyCharacters(): 85a. 或
     *note PyUnicode_Substring(): 85b.

   * ‘Py_UNICODE_strcmp()’：使用 *note PyUnicode_Compare(): 85c.

   * ‘Py_UNICODE_strncmp()’: 使用 *note PyUnicode_Tailmatch(): 85d.

   * ‘Py_UNICODE_strchr()’, ‘Py_UNICODE_strrchr()’: 使用 *note
     PyUnicode_FindChar(): 85e.

   * ‘Py_UNICODE_FILL()’: 使用 *note PyUnicode_Fill(): 1127.

   * ‘Py_UNICODE_MATCH’

編碼器：

   * ‘PyUnicode_Encode()’：使用 ‘PyUnicode_AsEncodedObject()’

   * ‘PyUnicode_EncodeUTF7()’

   * ‘PyUnicode_EncodeUTF8()’：使用 *note PyUnicode_AsUTF8(): b62. 或
     *note PyUnicode_AsUTF8String(): 1128.

   * ‘PyUnicode_EncodeUTF32()’

   * ‘PyUnicode_EncodeUTF16()’

   * ‘PyUnicode_EncodeUnicodeEscape()’ 使用 *note
     PyUnicode_AsUnicodeEscapeString(): 1129.

   * ‘PyUnicode_EncodeRawUnicodeEscape()’ 使用 *note
     PyUnicode_AsRawUnicodeEscapeString(): 112a.

   * ‘PyUnicode_EncodeLatin1()’: 使用 *note PyUnicode_AsLatin1String():
     112b.

   * ‘PyUnicode_EncodeASCII()’：使用 *note PyUnicode_AsASCIIString():
     112c.

   * ‘PyUnicode_EncodeCharmap()’

   * ‘PyUnicode_TranslateCharmap()’

   * ‘PyUnicode_EncodeMBCS()’：使用 *note PyUnicode_AsMBCSString():
     112d. 或 *note PyUnicode_EncodeCodePage(): 112e. （帶有 ‘CP_ACP’
     code_page）

   * ‘PyUnicode_EncodeDecimal()’、‘PyUnicode_TransformDecimalToASCII()’

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0393/


File: python.info,  Node: 已棄用的功能,  Prev: C API 中已棄用的函式和型別,  Up: 已棄用<12>

1.11.23.4 已棄用的功能
......................

The *note array: 6. module's ‘'u'’ format code is now deprecated and
will be removed in Python 4 together with the rest of the (*note
Py_UNICODE: 3b8.) API.


File: python.info,  Node: 移植到 Python 3 3,  Prev: 已棄用<12>,  Up: Python 3 3 有什麼新功能

1.11.24 移植到 Python 3.3
-------------------------

本節列出了前面描述的更改以及可能需要你更改程式碼的其他錯誤修復。

* Menu:

* 移植 Python 程式碼::
* Porting C code::
* Building C extensions::
* 命令列開關更改::


File: python.info,  Node: 移植 Python 程式碼,  Next: Porting C code,  Up: 移植到 Python 3 3

1.11.24.1 移植 Python 程式碼
............................

   * Hash randomization is enabled by default.  Set the *note
     PYTHONHASHSEED: 101e. environment variable to ‘0’ to disable hash
     randomization.  See also the *note object.__hash__(): a9e. method.

   * bpo-12326(1): On Linux, sys.platform doesn't contain the major
     version anymore.  It is now always 'linux', instead of 'linux2' or
     'linux3' depending on the Linux version used to build Python.
     Replace sys.platform == 'linux2' with
     sys.platform.startswith('linux'), or directly sys.platform ==
     'linux' if you don't need to support older Python versions.

   * bpo-13847(2), bpo-14180(3): *note time: d7. and *note datetime:
     28.: *note OverflowError: 825. is now raised instead of *note
     ValueError: 1e7. if a timestamp is out of range.  *note OSError:
     350. is now raised if C functions ‘gmtime()’ or ‘localtime()’
     failed.

   * The default finders used by import now utilize a cache of what is
     contained within a specific directory.  If you create a Python
     source file or sourceless bytecode file, make sure to call *note
     importlib.invalidate_caches(): bb7. to clear out the cache for the
     finders to notice the new file.

   * *note ImportError: 352. now uses the full name of the module that
     was attempted to be imported.  Doctests that check ImportErrors'
     message will need to be updated to use the full name of the module
     instead of just the tail of the name.

   * The 'index' argument to *note __import__(): 879. now defaults to 0
     instead of -1 and no longer support negative values.  It was an
     oversight when PEP 328(4) was implemented that the default value
     remained -1.  If you need to continue to perform a relative import
     followed by an absolute import, then perform the relative import
     using an index of 1, followed by another import using an index of
     0.  It is preferred, though, that you use *note
     importlib.import_module(): 4bc. rather than call *note
     __import__(): 879. directly.

   * *note __import__(): 879. no longer allows one to use an index value
     other than 0 for top-level modules.  E.g.  ‘__import__('sys',
     level=1)’ is now an error.

   * Because *note sys.meta_path: cd2. and *note sys.path_hooks: fc7.
     now have finders on them by default, you will most likely want to
     use ‘list.insert()’ instead of ‘list.append()’ to add to those
     lists.

   * Because ‘None’ is now inserted into *note sys.path_importer_cache:
     588, if you are clearing out entries in the dictionary of paths
     that do not have a finder, you will need to remove keys paired with
     values of ‘None’ 'and' ‘imp.NullImporter’ to be
     backwards-compatible.  This will lead to extra overhead on older
     versions of Python that re-insert ‘None’ into *note
     sys.path_importer_cache: 588. where it represents the use of
     implicit finders, but semantically it should not change anything.

   * ‘importlib.abc.Finder’ no longer specifies a ‘find_module()’
     abstract method that must be implemented.  If you were relying on
     subclasses to implement that method, make sure to check for the
     method's existence first.  You will probably want to check for
     ‘find_loader()’ first, though, in the case of working with *note
     path entry finders: 1012.

   * *note pkgutil: 97. has been converted to use *note importlib: 6b.
     internally.  This eliminates many edge cases where the old
     behaviour of the PEP 302(5) import emulation failed to match the
     behaviour of the real import system.  The import emulation itself
     is still present, but is now deprecated.  The *note
     pkgutil.iter_importers(): 1132. and *note pkgutil.walk_packages():
     ba6. functions special case the standard import hooks so they are
     still supported even though they do not provide the non-standard
     ‘iter_modules()’ method.

   * A longstanding RFC-compliance bug (bpo-1079(6)) in the parsing done
     by *note email.header.decode_header(): 1052. has been fixed.  Code
     that uses the standard idiom to convert encoded headers into
     unicode (‘str(make_header(decode_header(h))’) will see no change,
     but code that looks at the individual tuples returned by
     decode_header will see that whitespace that precedes or follows
     ‘ASCII’ sections is now included in the ‘ASCII’ section.  Code that
     builds headers using ‘make_header’ should also continue to work
     without change, since ‘make_header’ continues to add whitespace
     between ‘ASCII’ and non-‘ASCII’ sections if it is not already
     present in the input strings.

   * *note email.utils.formataddr(): 1133. now does the correct content
     transfer encoding when passed non-‘ASCII’ display names.  Any code
     that depended on the previous buggy behavior that preserved the
     non-‘ASCII’ unicode in the formatted output string will need to be
     changed (bpo-1690608(7)).

   * *note poplib.POP3.quit(): 1134. may now raise protocol errors like
     all other ‘poplib’ methods.  Code that assumes ‘quit’ does not
     raise *note poplib.error_proto: 1135. errors may need to be changed
     if errors on ‘quit’ are encountered by a particular application
     (bpo-11291(8)).

   * 自 Python 2.4 以來已棄用的 *note email.parser.Parser: 1136. 的
     ‘strict’ 引數終於被刪除了。

   * 已棄用的方法 ‘unittest.TestCase.assertSameElements’ 已被刪除。

   * 已棄用的變數 ‘time.accept2dyear’ 已被刪除。

   * The deprecated ‘Context._clamp’ attribute has been removed from the
     *note decimal: 2e. module.  It was previously replaced by the
     public attribute ‘clamp’.  (See bpo-8540(9).)

   * The undocumented internal helper class ‘SSLFakeFile’ has been
     removed from *note smtplib: b7, since its functionality has long
     been provided directly by *note socket.socket.makefile(): 1137.

   * Passing a negative value to *note time.sleep(): 642. on Windows now
     raises an error instead of sleeping forever.  It has always raised
     an error on posix.

   * The ‘ast.__version__’ constant has been removed.  If you need to
     make decisions affected by the AST version, use *note
     sys.version_info: 645. to make the decision.

   * Code that used to work around the fact that the *note threading:
     d6. module used factory functions by subclassing the private
     classes will need to change to subclass the now-public classes.

   * The undocumented debugging machinery in the threading module has
     been removed, simplifying the code.  This should have no effect on
     production code, but is mentioned here in case any application
     debug frameworks were interacting with it (bpo-13550(10)).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=12326

   (2) https://bugs.python.org/issue?@action=redirect&bpo=13847

   (3) https://bugs.python.org/issue?@action=redirect&bpo=14180

   (4) https://peps.python.org/pep-0328/

   (5) https://peps.python.org/pep-0302/

   (6) https://bugs.python.org/issue?@action=redirect&bpo=1079

   (7) https://bugs.python.org/issue?@action=redirect&bpo=1690608

   (8) https://bugs.python.org/issue?@action=redirect&bpo=11291

   (9) https://bugs.python.org/issue?@action=redirect&bpo=8540

   (10) https://bugs.python.org/issue?@action=redirect&bpo=13550


File: python.info,  Node: Porting C code,  Next: Building C extensions,  Prev: 移植 Python 程式碼,  Up: 移植到 Python 3 3

1.11.24.2 Porting C code
........................

   * In the course of changes to the buffer API the undocumented
     ‘smalltable’ member of the *note Py_buffer: 6fc. structure has been
     removed and the layout of the ‘PyMemoryViewObject’ has changed.

     All extensions relying on the relevant parts in ‘memoryobject.h’ or
     ‘object.h’ must be rebuilt.

   * Due to *note PEP 393: fe0, the *note Py_UNICODE: 3b8. type and all
     functions using this type are deprecated (but will stay available
     for at least five years).  If you were using low-level Unicode APIs
     to construct and access unicode objects and you want to benefit of
     the memory footprint reduction provided by PEP 393(1), you have to
     convert your code to the new *note Unicode API: 1138.

     However, if you only have been using high-level functions such as
     *note PyUnicode_Concat(): 1139, *note PyUnicode_Join(): 113a. or
     *note PyUnicode_FromFormat(): 33f, your code will automatically
     take advantage of the new unicode representations.

   * *note PyImport_GetMagicNumber(): 113b. 現在在失敗時回傳 ‘-1’。

   * As a negative value for the 'level' argument to *note __import__():
     879. is no longer valid, the same now holds for *note
     PyImport_ImportModuleLevel(): 113c.  This also means that the value
     of 'level' used by *note PyImport_ImportModuleEx(): 113d. is now
     ‘0’ instead of ‘-1’.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0393/


File: python.info,  Node: Building C extensions,  Next: 命令列開關更改,  Prev: Porting C code,  Up: 移植到 Python 3 3

1.11.24.3 Building C extensions
...............................

   * The range of possible file names for C extensions has been
     narrowed.  Very rarely used spellings have been suppressed: under
     POSIX, files named ‘xxxmodule.so’, ‘xxxmodule.abi3.so’ and
     ‘xxxmodule.cpython-*.so’ are no longer recognized as implementing
     the ‘xxx’ module.  If you had been generating such files, you have
     to switch to the other spellings (i.e., remove the ‘module’ string
     from the file names).

     （於 bpo-14040(1) 中實作。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=14040


File: python.info,  Node: 命令列開關更改,  Prev: Building C extensions,  Up: 移植到 Python 3 3

1.11.24.4 命令列開關更改
........................

   * The -Q command-line flag and related artifacts have been removed.
     Code checking sys.flags.division_warning will need updating.

     （由 Éric Araujo 於 bpo-10998(1) 中實作。）

   * When ‘python’ is started with *note -S: 1140, ‘import site’ will no
     longer add site-specific paths to the module search paths.  In
     previous versions, it did.

     （bpo-11591(2)，由 Carl Meyer 貢獻並由 Éric Araujo 修訂。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=10998

   (2) https://bugs.python.org/issue?@action=redirect&bpo=11591


File: python.info,  Node: Python 3 2 有什麼新功能,  Next: Python 3 1 有什麼新功能,  Prev: Python 3 3 有什麼新功能,  Up: Python 有什麼新功能？

1.12 Python 3.2 有什麼新功能
============================


作者: Raymond Hettinger

This article explains the new features in Python 3.2 as compared to 3.1.
Python 3.2 was released on February 20, 2011.  It focuses on a few
highlights and gives a few examples.  For full details, see the
Misc/NEWS(1) file.

也參考
......

PEP 392(2) - Python 3.2 Release Schedule

* Menu:

* PEP 384; Defining a Stable ABI: PEP 384 Defining a Stable ABI.
* PEP 389; Argparse 命令列剖析模組: PEP 389 Argparse 命令列剖析模組.
* PEP 391; Dictionary Based Configuration for Logging: PEP 391 Dictionary Based Configuration for Logging.
* PEP 3148：concurrent.futures 模組: PEP 3148：concurrent futures 模組.
* PEP 3147; PYC Repository Directories: PEP 3147 PYC Repository Directories.
* PEP 3149; ABI Version Tagged .so Files: PEP 3149 ABI Version Tagged so Files.
* PEP 3333; Python Web Server Gateway Interface v1.0.1: PEP 3333 Python Web Server Gateway Interface v1 0 1.
* 其他語言更動: 其他語言更動<11>.
* New, Improved, and Deprecated Modules: New Improved and Deprecated Modules.
* Multi-threading::
* 最佳化: 最佳化<10>.
* Unicode::
* 編解碼器::
* 文件::
* IDLE::
* Code Repository::
* Build and C API Changes: Build and C API Changes<4>.
* Porting to Python 3.2: Porting to Python 3 2.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/blob/076ca6c3c8df3030307e548d9be792ce3c1c6eea/Misc/NEWS

   (2) https://peps.python.org/pep-0392/


File: python.info,  Node: PEP 384 Defining a Stable ABI,  Next: PEP 389 Argparse 命令列剖析模組,  Up: Python 3 2 有什麼新功能

1.12.1 PEP 384: Defining a Stable ABI
-------------------------------------

In the past, extension modules built for one Python version were often
not usable with other Python versions.  Particularly on Windows, every
feature release of Python required rebuilding all extension modules that
one wanted to use.  This requirement was the result of the free access
to Python interpreter internals that extension modules could use.

With Python 3.2, an alternative approach becomes available: extension
modules which restrict themselves to a limited API (by defining
Py_LIMITED_API) cannot use many of the internals, but are constrained to
a set of API functions that are promised to be stable for several
releases.  As a consequence, extension modules built for 3.2 in that
mode will also work with 3.3, 3.4, and so on.  Extension modules that
make use of details of memory structures can still be built, but will
need to be recompiled for every feature release.

也參考
......

PEP 384(1) - 定義一個穩定 ABI

     由 Martin von Löwis 撰寫 PEP。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0384/


File: python.info,  Node: PEP 389 Argparse 命令列剖析模組,  Next: PEP 391 Dictionary Based Configuration for Logging,  Prev: PEP 384 Defining a Stable ABI,  Up: Python 3 2 有什麼新功能

1.12.2 PEP 389: Argparse 命令列剖析模組
---------------------------------------

A new module for command line parsing, *note argparse: 5, was introduced
to overcome the limitations of *note optparse: 90. which did not provide
support for positional arguments (not just options), subcommands,
required options and other common patterns of specifying and validating
options.

This module has already had widespread success in the community as a
third-party module.  Being more fully featured than its predecessor, the
*note argparse: 5. module is now the preferred module for command-line
processing.  The older module is still being kept available because of
the substantial amount of legacy code that depends on it.

Here's an annotated example parser showing features like limiting
results to a set of choices, specifying a 'metavar' in the help screen,
validating that one or more positional arguments is present, and making
a required option:

     import argparse
     parser = argparse.ArgumentParser(
                 description = 'Manage servers',         # main description for help
                 epilog = 'Tested on Solaris and Linux') # displayed after help
     parser.add_argument('action',                       # argument name
                 choices = ['deploy', 'start', 'stop'],  # three allowed values
                 help = 'action on each target')         # help msg
     parser.add_argument('targets',
                 metavar = 'HOSTNAME',                   # var name used in help msg
                 nargs = '+',                            # require one or more targets
                 help = 'url for target machines')       # help msg explanation
     parser.add_argument('-u', '--user',                 # -u or --user option
                 required = True,                        # make it a required argument
                 help = 'login as user')

Example of calling the parser on a command string:

     >>> cmd = 'deploy sneezy.example.com sleepy.example.com -u skycaptain'
     >>> result = parser.parse_args(cmd.split())
     >>> result.action
     'deploy'
     >>> result.targets
     ['sneezy.example.com', 'sleepy.example.com']
     >>> result.user
     'skycaptain'

Example of the parser's automatically generated help:

     >>> parser.parse_args('-h'.split())

     usage: manage_cloud.py [-h] -u USER
                            {deploy,start,stop} HOSTNAME [HOSTNAME ...]

     Manage servers

     positional arguments:
       {deploy,start,stop}   action on each target
       HOSTNAME              url for target machines

     optional arguments:
       -h, --help            show this help message and exit
       -u USER, --user USER  login as user

     Tested on Solaris and Linux

An especially nice *note argparse: 5. feature is the ability to define
subparsers, each with their own argument patterns and help displays:

     import argparse
     parser = argparse.ArgumentParser(prog='HELM')
     subparsers = parser.add_subparsers()

     parser_l = subparsers.add_parser('launch', help='Launch Control')   # first subgroup
     parser_l.add_argument('-m', '--missiles', action='store_true')
     parser_l.add_argument('-t', '--torpedos', action='store_true')

     parser_m = subparsers.add_parser('move', help='Move Vessel',        # second subgroup
                                      aliases=('steer', 'turn'))         # equivalent names
     parser_m.add_argument('-c', '--course', type=int, required=True)
     parser_m.add_argument('-s', '--speed', type=int, default=0)

     $ ./helm.py --help                         # top level help (launch and move)
     $ ./helm.py launch --help                  # help for launch options
     $ ./helm.py launch --missiles              # set missiles=True and torpedos=False
     $ ./helm.py steer --course 180 --speed 5   # set movement parameters

也參考
......

PEP 389(1) - 新命令列剖析模組

     由 Steven Bethard 撰寫 PEP。

*note Upgrading optparse code: 1145. for details on the differences from
*note optparse: 90.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0389/


File: python.info,  Node: PEP 391 Dictionary Based Configuration for Logging,  Next: PEP 3148：concurrent futures 模組,  Prev: PEP 389 Argparse 命令列剖析模組,  Up: Python 3 2 有什麼新功能

1.12.3 PEP 391: Dictionary Based Configuration for Logging
----------------------------------------------------------

The *note logging: 7b. module provided two kinds of configuration, one
style with function calls for each option or another style driven by an
external file saved in a *note configparser: 1b. format.  Those options
did not provide the flexibility to create configurations from JSON or
YAML files, nor did they support incremental configuration, which is
needed for specifying logger options from a command line.

To support a more flexible style, the module now offers *note
logging.config.dictConfig(): 1147. for specifying logging configuration
with plain Python dictionaries.  The configuration options include
formatters, handlers, filters, and loggers.  Here's a working example of
a configuration dictionary:

     {"version": 1,
      "formatters": {"brief": {"format": "%(levelname)-8s: %(name)-15s: %(message)s"},
                     "full": {"format": "%(asctime)s %(name)-15s %(levelname)-8s %(message)s"}
                     },
      "handlers": {"console": {
                        "class": "logging.StreamHandler",
                        "formatter": "brief",
                        "level": "INFO",
                        "stream": "ext://sys.stdout"},
                   "console_priority": {
                        "class": "logging.StreamHandler",
                        "formatter": "full",
                        "level": "ERROR",
                        "stream": "ext://sys.stderr"}
                   },
      "root": {"level": "DEBUG", "handlers": ["console", "console_priority"]}}

If that dictionary is stored in a file called ‘conf.json’, it can be
loaded and called with code like this:

     >>> import json, logging.config
     >>> with open('conf.json') as f:
     ...     conf = json.load(f)
     ...
     >>> logging.config.dictConfig(conf)
     >>> logging.info("Transaction completed normally")
     INFO    : root           : Transaction completed normally
     >>> logging.critical("Abnormal termination")
     2011-02-17 11:14:36,694 root            CRITICAL Abnormal termination

也參考
......

PEP 391(1) - Dictionary Based Configuration for Logging

     由 Vinay Sajip 撰寫 PEP。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0391/


File: python.info,  Node: PEP 3148：concurrent futures 模組,  Next: PEP 3147 PYC Repository Directories,  Prev: PEP 391 Dictionary Based Configuration for Logging,  Up: Python 3 2 有什麼新功能

1.12.4 PEP 3148：‘concurrent.futures’ 模組
------------------------------------------

Code for creating and managing concurrency is being collected in a new
top-level namespace, 'concurrent'.  Its first member is a 'futures'
package which provides a uniform high-level interface for managing
threads and processes.

The design for *note concurrent.futures: 1a. was inspired by the
'java.util.concurrent' package.  In that model, a running call and its
result are represented by a *note Future: 1149. object that abstracts
features common to threads, processes, and remote procedure calls.  That
object supports status checks (running or done), timeouts,
cancellations, adding callbacks, and access to results or exceptions.

The primary offering of the new module is a pair of executor classes for
launching and managing calls.  The goal of the executors is to make it
easier to use existing tools for making parallel calls.  They save the
effort needed to setup a pool of resources, launch the calls, create a
results queue, add time-out handling, and limit the total number of
threads, processes, or remote procedure calls.

Ideally, each application should share a single executor across multiple
components so that process and thread limits can be centrally managed.
This solves the design challenge that arises when each component has its
own competing strategy for resource management.

Both classes share a common interface with three methods: *note
submit(): a25. for scheduling a callable and returning a *note Future:
1149. object; *note map(): d8a. for scheduling many asynchronous calls
at a time, and *note shutdown(): 892. for freeing resources.  The class
is a *note context manager: 576. and can be used in a *note with: 577.
statement to assure that resources are automatically released when
currently pending futures are done executing.

A simple of example of *note ThreadPoolExecutor: 6e6. is a launch of
four parallel threads for copying files:

     import concurrent.futures, shutil
     with concurrent.futures.ThreadPoolExecutor(max_workers=4) as e:
         e.submit(shutil.copy, 'src1.txt', 'dest1.txt')
         e.submit(shutil.copy, 'src2.txt', 'dest2.txt')
         e.submit(shutil.copy, 'src3.txt', 'dest3.txt')
         e.submit(shutil.copy, 'src3.txt', 'dest4.txt')

也參考
......

PEP 3148(1) - Futures - Execute Computations Asynchronously

     由 Brian Quinlan 撰寫 PEP。

*note Code for Threaded Parallel URL reads: 114a, an example using
threads to fetch multiple web pages in parallel.

*note Code for computing prime numbers in parallel: 114b, an example
demonstrating *note ProcessPoolExecutor: 893.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3148/


File: python.info,  Node: PEP 3147 PYC Repository Directories,  Next: PEP 3149 ABI Version Tagged so Files,  Prev: PEP 3148：concurrent futures 模組,  Up: Python 3 2 有什麼新功能

1.12.5 PEP 3147: PYC Repository Directories
-------------------------------------------

Python's scheme for caching bytecode in '.pyc' files did not work well
in environments with multiple Python interpreters.  If one interpreter
encountered a cached file created by another interpreter, it would
recompile the source and overwrite the cached file, thus losing the
benefits of caching.

The issue of "pyc fights" has become more pronounced as it has become
commonplace for Linux distributions to ship with multiple versions of
Python.  These conflicts also arise with CPython alternatives such as
Unladen Swallow.

To solve this problem, Python's import machinery has been extended to
use distinct filenames for each interpreter.  Instead of Python 3.2 and
Python 3.3 and Unladen Swallow each competing for a file called
"mymodule.pyc", they will now look for "mymodule.cpython-32.pyc",
"mymodule.cpython-33.pyc", and "mymodule.unladen10.pyc".  And to prevent
all of these new files from cluttering source directories, the 'pyc'
files are now collected in a "__pycache__" directory stored under the
package directory.

Aside from the filenames and target directories, the new scheme has a
few aspects that are visible to the programmer:

   * Imported modules now have a *note __cached__: 114d. attribute which
     stores the name of the actual file that was imported:

          >>> import collections
          >>> collections.__cached__
          'c:/py32/lib/__pycache__/collections.cpython-32.pyc'

   * The tag that is unique to each interpreter is accessible from the
     ‘imp’ module:

          >>> import imp
          >>> imp.get_tag()
          'cpython-32'

   * Scripts that try to deduce source filename from the imported file
     now need to be smarter.  It is no longer sufficient to simply strip
     the "c" from a ".pyc" filename.  Instead, use the new functions in
     the ‘imp’ module:

          >>> imp.source_from_cache('c:/py32/lib/__pycache__/collections.cpython-32.pyc')
          'c:/py32/lib/collections.py'
          >>> imp.cache_from_source('c:/py32/lib/collections.py')
          'c:/py32/lib/__pycache__/collections.cpython-32.pyc'

   * The *note py_compile: a1. and *note compileall: 19. modules have
     been updated to reflect the new naming convention and target
     directory.  The command-line invocation of 'compileall' has new
     options: ‘-i’ for specifying a list of files and directories to
     compile and ‘-b’ which causes bytecode files to be written to their
     legacy location rather than '__pycache__'.

   * The *note importlib.abc: 6c. module has been updated with new *note
     abstract base classes: 114e. for loading bytecode files.  The
     obsolete ABCs, ‘PyLoader’ and ‘PyPycLoader’, have been deprecated
     (instructions on how to stay Python 3.1 compatible are included
     with the documentation).

也參考
......

PEP 3147(1) - PYC Repository Directories

     由 Barry Warsaw 撰寫 PEP。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3147/


File: python.info,  Node: PEP 3149 ABI Version Tagged so Files,  Next: PEP 3333 Python Web Server Gateway Interface v1 0 1,  Prev: PEP 3147 PYC Repository Directories,  Up: Python 3 2 有什麼新功能

1.12.6 PEP 3149: ABI Version Tagged .so Files
---------------------------------------------

The PYC repository directory allows multiple bytecode cache files to be
co-located.  This PEP implements a similar mechanism for shared object
files by giving them a common directory and distinct names for each
version.

The common directory is "pyshared" and the file names are made distinct
by identifying the Python implementation (such as CPython, PyPy, Jython,
etc.), the major and minor version numbers, and optional build flags
(such as "d" for debug, "m" for pymalloc, "u" for wide-unicode).  For an
arbitrary package "foo", you may see these files when the distribution
package is installed:

     /usr/share/pyshared/foo.cpython-32m.so
     /usr/share/pyshared/foo.cpython-33md.so

In Python itself, the tags are accessible from functions in the *note
sysconfig: c5. module:

     >>> import sysconfig
     >>> sysconfig.get_config_var('SOABI')       # find the version tag
     'cpython-32mu'
     >>> sysconfig.get_config_var('EXT_SUFFIX')  # find the full filename extension
     '.cpython-32mu.so'

也參考
......

PEP 3149(1) - ABI Version Tagged .so Files

     由 Barry Warsaw 撰寫 PEP。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3149/


File: python.info,  Node: PEP 3333 Python Web Server Gateway Interface v1 0 1,  Next: 其他語言更動<11>,  Prev: PEP 3149 ABI Version Tagged so Files,  Up: Python 3 2 有什麼新功能

1.12.7 PEP 3333: Python Web Server Gateway Interface v1.0.1
-----------------------------------------------------------

This informational PEP clarifies how bytes/text issues are to be handled
by the WSGI protocol.  The challenge is that string handling in Python 3
is most conveniently handled with the *note str: 3f2. type even though
the HTTP protocol is itself bytes oriented.

The PEP differentiates so-called 'native strings' that are used for
request/response headers and metadata versus 'byte strings' which are
used for the bodies of requests and responses.

The 'native strings' are always of type *note str: 3f2. but are
restricted to code points between 'U+0000' through 'U+00FF' which are
translatable to bytes using 'Latin-1' encoding.  These strings are used
for the keys and values in the environment dictionary and for response
headers and statuses in the ‘start_response()’ function.  They must
follow RFC 2616(1) with respect to encoding.  That is, they must either
be 'ISO-8859-1' characters or use RFC 2047(2) MIME encoding.

For developers porting WSGI applications from Python 2, here are the
salient points:

   * If the app already used strings for headers in Python 2, no change
     is needed.

   * If instead, the app encoded output headers or decoded input
     headers, then the headers will need to be re-encoded to Latin-1.
     For example, an output header encoded in utf-8 was using
     ‘h.encode('utf-8')’ now needs to convert from bytes to native
     strings using ‘h.encode('utf-8').decode('latin-1')’.

   * Values yielded by an application or sent using the ‘write()’ method
     must be byte strings.  The ‘start_response()’ function and environ
     must use native strings.  The two cannot be mixed.

For server implementers writing CGI-to-WSGI pathways or other CGI-style
protocols, the users must to be able access the environment using native
strings even though the underlying platform may have a different
convention.  To bridge this gap, the *note wsgiref: 100. module has a
new function, *note wsgiref.handlers.read_environ(): 1151. for
transcoding CGI variables from *note os.environ: 1152. into native
strings and returning a new dictionary.

也參考
......

PEP 3333(3) - Python Web Server Gateway Interface v1.0.1

     由 Phillip Eby 撰寫 PEP。

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2616.html

   (2) https://datatracker.ietf.org/doc/html/rfc2047.html

   (3) https://peps.python.org/pep-3333/


File: python.info,  Node: 其他語言更動<11>,  Next: New Improved and Deprecated Modules,  Prev: PEP 3333 Python Web Server Gateway Interface v1 0 1,  Up: Python 3 2 有什麼新功能

1.12.8 其他語言更動
-------------------

Some smaller changes made to the core Python language are:

   * String formatting for *note format(): 5c3. and *note str.format():
     5c7. gained new capabilities for the format character '#'.
     Previously, for integers in binary, octal, or hexadecimal, it
     caused the output to be prefixed with '0b', '0o', or '0x'
     respectively.  Now it can also handle floats, complex, and Decimal,
     causing the output to always have a decimal point even when no
     digits follow it.

          >>> format(20, '#o')
          '0o24'
          >>> format(12.34, '#5.0f')
          '  12.'

     (Suggested by Mark Dickinson and implemented by Eric Smith in
     bpo-7094(1).)

   * There is also a new *note str.format_map(): d7d. method that
     extends the capabilities of the existing *note str.format(): 5c7.
     method by accepting arbitrary *note mapping: 1154. objects.  This
     new method makes it possible to use string formatting with any of
     Python's many dictionary-like objects such as *note defaultdict:
     1155, *note Shelf: f3d, *note ConfigParser: 1aa, or *note dbm: 29.
     It is also useful with custom *note dict: 23b. subclasses that
     normalize keys before look-up or that supply a ‘__missing__()’
     method for unknown keys:

          >>> import shelve
          >>> d = shelve.open('tmp.shl')
          >>> 'The {project_name} status is {status} as of {date}'.format_map(d)
          'The testing project status is green as of February 15, 2011'

          >>> class LowerCasedDict(dict):
          ...     def __getitem__(self, key):
          ...         return dict.__getitem__(self, key.lower())
          ...
          >>> lcd = LowerCasedDict(part='widgets', quantity=10)
          >>> 'There are {QUANTITY} {Part} in stock'.format_map(lcd)
          'There are 10 widgets in stock'

          >>> class PlaceholderDict(dict):
          ...     def __missing__(self, key):
          ...         return '<{}>'.format(key)
          ...
          >>> 'Hello {name}, welcome to {location}'.format_map(PlaceholderDict())
          'Hello <name>, welcome to <location>'

     (Suggested by Raymond Hettinger and implemented by Eric Smith in
     bpo-6081(2).)

   * The interpreter can now be started with a quiet option, ‘-q’, to
     prevent the copyright and version information from being displayed
     in the interactive mode.  The option can be introspected using the
     *note sys.flags: 632. attribute:

          $ python -q
          >>> sys.flags
          sys.flags(debug=0, division_warning=0, inspect=0, interactive=0,
          optimize=0, dont_write_bytecode=0, no_user_site=0, no_site=0,
          ignore_environment=0, verbose=0, bytes_warning=0, quiet=1)

     （由 Marcin Wojdyr 在 bpo-1772833(3) 中貢獻）。

   * The *note hasattr(): 479. function works by calling *note
     getattr(): b78. and detecting whether an exception is raised.  This
     technique allows it to detect methods created dynamically by *note
     __getattr__(): 47a. or *note __getattribute__(): b79. which would
     otherwise be absent from the class dictionary.  Formerly, 'hasattr'
     would catch any exception, possibly masking genuine errors.  Now,
     'hasattr' has been tightened to only catch *note AttributeError:
     2f6. and let other exceptions pass through:

          >>> class A:
          ...     @property
          ...     def f(self):
          ...         return 1 // 0
          ...
          >>> a = A()
          >>> hasattr(a, 'f')
          Traceback (most recent call last):
            ...
          ZeroDivisionError: integer division or modulo by zero

     (Discovered by Yury Selivanov and fixed by Benjamin Peterson;
     bpo-9666(4).)

   * The *note str(): 3f2. of a float or complex number is now the same
     as its *note repr(): 7a1.  Previously, the *note str(): 3f2. form
     was shorter but that just caused confusion and is no longer needed
     now that the shortest possible *note repr(): 7a1. is displayed by
     default:

          >>> import math
          >>> repr(math.pi)
          '3.141592653589793'
          >>> str(math.pi)
          '3.141592653589793'

     (Proposed and implemented by Mark Dickinson; bpo-9337(5).)

   * *note memoryview: 40f. objects now have a *note release(): 1156.
     method and they also now support the context management protocol.
     This allows timely release of any resources that were acquired when
     requesting a buffer from the original object.

          >>> with memoryview(b'abcdefgh') as v:
          ...     print(v.tolist())
          [97, 98, 99, 100, 101, 102, 103, 104]

     (Added by Antoine Pitrou; bpo-9757(6).)

   * Previously it was illegal to delete a name from the local namespace
     if it occurs as a free variable in a nested block:

          def outer(x):
              def inner():
                  return x
              inner()
              del x

     This is now allowed.  Remember that the target of an *note except:
     171. clause is cleared, so this code which used to work with Python
     2.6, raised a *note SyntaxError: 173. with Python 3.1 and now works
     again:

          def f():
              def print_error():
                  print(e)
              try:
                  something
              except Exception as e:
                  print_error()
                  # implicit "del e" here

     （請見 bpo-4617(7)。）

   * *note Struct sequence types: 1157. are now subclasses of tuple.
     This means that C structures like those returned by *note
     os.stat(): 448, *note time.gmtime(): 1158, and *note
     sys.version_info: 645. now work like a *note named tuple: 5f4. and
     now work with functions and methods that expect a tuple as an
     argument.  This is a big step forward in making the C structures as
     flexible as their pure Python counterparts:

          >>> import sys
          >>> isinstance(sys.version_info, tuple)
          True
          >>> 'Version %d.%d.%d %s(%d)' % sys.version_info
          'Version 3.2.0 final(0)'

     (Suggested by Arfrever Frehtes Taifersar Arahesis and implemented
     by Benjamin Peterson in bpo-8413(8).)

   * Warnings are now easier to control using the *note PYTHONWARNINGS:
     b51. environment variable as an alternative to using ‘-W’ at the
     command line:

          $ export PYTHONWARNINGS='ignore::RuntimeWarning::,once::UnicodeWarning::'

     (Suggested by Barry Warsaw and implemented by Philip Jenvey in
     bpo-7301(9).)

   * A new warning category, *note ResourceWarning: 229, has been added.
     It is emitted when potential issues with resource consumption or
     cleanup are detected.  It is silenced by default in normal release
     builds but can be enabled through the means provided by the *note
     warnings: fa. module, or on the command line.

     A *note ResourceWarning: 229. is issued at interpreter shutdown if
     the *note gc.garbage: 1159. list isn't empty, and if *note
     gc.DEBUG_UNCOLLECTABLE: 115a. is set, all uncollectable objects are
     printed.  This is meant to make the programmer aware that their
     code contains object finalization issues.

     A *note ResourceWarning: 229. is also issued when a *note file
     object: 115b. is destroyed without having been explicitly closed.
     While the deallocator for such object ensures it closes the
     underlying operating system resource (usually, a file descriptor),
     the delay in deallocating the object could produce various issues,
     especially under Windows.  Here is an example of enabling the
     warning from the command line:

          $ python -q -Wdefault
          >>> f = open("foo", "wb")
          >>> del f
          __main__:1: ResourceWarning: unclosed file <_io.BufferedWriter name='foo'>

     (Added by Antoine Pitrou and Georg Brandl in bpo-10093(10) and
     bpo-477863(11).)

   * *note range: 8e7. objects now support 'index' and 'count' methods.
     This is part of an effort to make more objects fully implement the
     *note collections.Sequence: 115c. *note abstract base class: 114e.
     As a result, the language will have a more uniform API. In
     addition, *note range: 8e7. objects now support slicing and
     negative indices, even with values larger than *note sys.maxsize:
     115d.  This makes 'range' more interoperable with lists:

          >>> range(0, 100, 2).count(10)
          1
          >>> range(0, 100, 2).index(10)
          5
          >>> range(0, 100, 2)[5]
          10
          >>> range(0, 100, 2)[0:5]
          range(0, 10, 2)

     （由 Daniel Stutzbach 在 bpo-9213(12)、Alexander Belopolsky 在
     bpo-2690(13)、Nick Coghlan 在 bpo-10889(14) 中貢獻。）

   * The *note callable(): 115e. builtin function from Py2.x was
     resurrected.  It provides a concise, readable alternative to using
     an *note abstract base class: 114e. in an expression like
     ‘isinstance(x, collections.Callable)’:

          >>> callable(max)
          True
          >>> callable(20)
          False

     （請見 bpo-10518(15)。）

   * Python's import mechanism can now load modules installed in
     directories with non-ASCII characters in the path name.  This
     solved an aggravating problem with home directories for users with
     non-ASCII characters in their usernames.

     (Required extensive work by Victor Stinner in bpo-9425(16).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=7094

   (2) https://bugs.python.org/issue?@action=redirect&bpo=6081

   (3) https://bugs.python.org/issue?@action=redirect&bpo=1772833

   (4) https://bugs.python.org/issue?@action=redirect&bpo=9666

   (5) https://bugs.python.org/issue?@action=redirect&bpo=9337

   (6) https://bugs.python.org/issue?@action=redirect&bpo=9757

   (7) https://bugs.python.org/issue?@action=redirect&bpo=4617

   (8) https://bugs.python.org/issue?@action=redirect&bpo=8413

   (9) https://bugs.python.org/issue?@action=redirect&bpo=7301

   (10) https://bugs.python.org/issue?@action=redirect&bpo=10093

   (11) https://bugs.python.org/issue?@action=redirect&bpo=477863

   (12) https://bugs.python.org/issue?@action=redirect&bpo=9213

   (13) https://bugs.python.org/issue?@action=redirect&bpo=2690

   (14) https://bugs.python.org/issue?@action=redirect&bpo=10889

   (15) https://bugs.python.org/issue?@action=redirect&bpo=10518

   (16) https://bugs.python.org/issue?@action=redirect&bpo=9425


File: python.info,  Node: New Improved and Deprecated Modules,  Next: Multi-threading,  Prev: 其他語言更動<11>,  Up: Python 3 2 有什麼新功能

1.12.9 New, Improved, and Deprecated Modules
--------------------------------------------

Python's standard library has undergone significant maintenance efforts
and quality improvements.

The biggest news for Python 3.2 is that the *note email: 32. package,
*note mailbox: 7f. module, and ‘nntplib’ modules now work correctly with
the bytes/text model in Python 3.  For the first time, there is correct
handling of messages with mixed encodings.

Throughout the standard library, there has been more careful attention
to encodings and text versus bytes issues.  In particular, interactions
with the operating system are now better able to exchange non-ASCII data
using the Windows MBCS encoding, locale-aware encodings, or UTF-8.

Another significant win is the addition of substantially better support
for 'SSL' connections and security certificates.

In addition, more classes now implement a *note context manager: 576. to
support convenient and reliable resource clean-up using a *note with:
577. statement.

* Menu:

* email: email<6>.
* elementtree::
* functools: functools<7>.
* itertools: itertools<7>.
* collections: collections<8>.
* threading: threading<9>.
* datetime 和 time::
* math: math<10>.
* abc: abc<3>.
* io: io<7>.
* reprlib::
* logging: logging<8>.
* csv: csv<4>.
* contextlib: contextlib<8>.
* decimal and fractions::
* ftp::
* popen::
* select: select<3>.
* gzip 和 zipfile::
* tarfile: tarfile<9>.
* hashlib: hashlib<7>.
* ast: ast<5>.
* os: os<13>.
* shutil: shutil<8>.
* sqlite3: sqlite3<11>.
* html: html<3>.
* socket: socket<11>.
* ssl: ssl<12>.
* nntp::
* certificates::
* imaplib: imaplib<4>.
* http.client: http client<4>.
* unittest: unittest<11>.
* random: random<5>.
* poplib: poplib<4>.
* asyncore: asyncore<2>.
* tempfile: tempfile<5>.
* inspect: inspect<10>.
* pydoc: pydoc<6>.
* dis: dis<5>.
* dbm: dbm<7>.
* ctypes: ctypes<2>.
* site: site<4>.
* sysconfig: sysconfig<3>.
* pdb: pdb<8>.
* configparser: configparser<6>.
* urllib.parse: urllib parse<6>.
* mailbox::
* turtledemo::


File: python.info,  Node: email<6>,  Next: elementtree,  Up: New Improved and Deprecated Modules

1.12.9.1 email
..............

The usability of the *note email: 32. package in Python 3 has been
mostly fixed by the extensive efforts of R. David Murray.  The problem
was that emails are typically read and stored in the form of *note
bytes: 1a5. rather than *note str: 3f2. text, and they may contain
multiple encodings within a single email.  So, the email package had to
be extended to parse and generate email messages in bytes format.

   * New functions *note message_from_bytes(): 1161. and *note
     message_from_binary_file(): 1162, and new classes *note
     BytesFeedParser: 1163. and *note BytesParser: 1164. allow binary
     message data to be parsed into model objects.

   * Given bytes input to the model, *note get_payload(): 1165. will by
     default decode a message body that has a
     ‘Content-Transfer-Encoding’ of '8bit' using the charset specified
     in the MIME headers and return the resulting string.

   * Given bytes input to the model, *note Generator: 1166. will convert
     message bodies that have a ‘Content-Transfer-Encoding’ of '8bit' to
     instead have a '7bit' ‘Content-Transfer-Encoding’.

     Headers with unencoded non-ASCII bytes are deemed to be RFC
     2047(1)-encoded using the 'unknown-8bit' character set.

   * A new class *note BytesGenerator: 1167. produces bytes as output,
     preserving any unchanged non-ASCII data that was present in the
     input used to build the model, including message bodies with a
     ‘Content-Transfer-Encoding’ of '8bit'.

   * The *note smtplib: b7. *note SMTP: 8d1. class now accepts a byte
     string for the 'msg' argument to the *note sendmail(): dfb. method,
     and a new method, *note send_message(): dfc. accepts a *note
     Message: 261. object and can optionally obtain the 'from_addr' and
     'to_addrs' addresses directly from the object.

(Proposed and implemented by R. David Murray, bpo-4661(2) and
bpo-10321(3).)

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2047.html

   (2) https://bugs.python.org/issue?@action=redirect&bpo=4661

   (3) https://bugs.python.org/issue?@action=redirect&bpo=10321


File: python.info,  Node: elementtree,  Next: functools<7>,  Prev: email<6>,  Up: New Improved and Deprecated Modules

1.12.9.2 elementtree
....................

The *note xml.etree.ElementTree: 10c. package and its
‘xml.etree.cElementTree’ counterpart have been updated to version 1.3.

Several new and useful functions and methods have been added:

   * *note xml.etree.ElementTree.fromstringlist(): 1169. which builds an
     XML document from a sequence of fragments

   * *note xml.etree.ElementTree.register_namespace(): 116a. for
     registering a global namespace prefix

   * *note xml.etree.ElementTree.tostringlist(): f97. for string
     representation including all sublists

   * *note xml.etree.ElementTree.Element.extend(): 116b. for appending a
     sequence of zero or more elements

   * *note xml.etree.ElementTree.Element.iterfind(): 116c. searches an
     element and subelements

   * *note xml.etree.ElementTree.Element.itertext(): 116d. creates a
     text iterator over an element and its subelements

   * *note xml.etree.ElementTree.TreeBuilder.end(): 116e. closes the
     current element

   * *note xml.etree.ElementTree.TreeBuilder.doctype(): a3a. handles a
     doctype declaration

有兩個方法已被棄用：

   * ‘xml.etree.ElementTree.getchildren()’ use ‘list(elem)’ instead.

   * ‘xml.etree.ElementTree.getiterator()’ use ‘Element.iter’ instead.

For details of the update, see Introducing ElementTree(1) on Fredrik
Lundh's website.

（由 Florent Xicluna 和 Fredrik Lundh 貢獻，bpo-6472(2)。）

   ---------- Footnotes ----------

   (1) 
https://web.archive.org/web/20200703234532/http://effbot.org/zone/elementtree-13-intro.htm

   (2) https://bugs.python.org/issue?@action=redirect&bpo=6472


File: python.info,  Node: functools<7>,  Next: itertools<7>,  Prev: elementtree,  Up: New Improved and Deprecated Modules

1.12.9.3 functools
..................

   * The *note functools: 55. module includes a new decorator for
     caching function calls.  *note functools.lru_cache(): 993. can save
     repeated queries to an external resource whenever the results are
     expected to be the same.

     For example, adding a caching decorator to a database query
     function can save database accesses for popular searches:

          >>> import functools
          >>> @functools.lru_cache(maxsize=300)
          ... def get_phone_number(name):
          ...     c = conn.cursor()
          ...     c.execute('SELECT phonenumber FROM phonelist WHERE name=?', (name,))
          ...     return c.fetchone()[0]

          >>> for name in user_requests:
          ...     get_phone_number(name)        # cached lookup

     To help with choosing an effective cache size, the wrapped function
     is instrumented for tracking cache statistics:

          >>> get_phone_number.cache_info()
          CacheInfo(hits=4805, misses=980, maxsize=300, currsize=300)

     If the phonelist table gets updated, the outdated contents of the
     cache can be cleared with:

          >>> get_phone_number.cache_clear()

     (Contributed by Raymond Hettinger and incorporating design ideas
     from Jim Baker, Miki Tebeka, and Nick Coghlan; see recipe
     498245(1), recipe 577479(2), bpo-10586(3), and bpo-10593(4).)

   * The *note functools.wraps(): f00. decorator now adds a
     ‘__wrapped__’ attribute pointing to the original callable function.
     This allows wrapped functions to be introspected.  It also copies
     *note __annotations__: 1170. if defined.  And now it also
     gracefully skips over missing attributes such as *note __doc__:
     1171. which might not be defined for the wrapped callable.

     In the above example, the cache can be removed by recovering the
     original function:

          >>> get_phone_number = get_phone_number.__wrapped__    # uncached function

     (By Nick Coghlan and Terrence Cole; bpo-9567(5), bpo-3445(6), and
     bpo-8814(7).)

   * To help write classes with rich comparison methods, a new decorator
     *note functools.total_ordering(): ee6. will use existing equality
     and inequality methods to fill in the remaining methods.

     For example, supplying '__eq__' and '__lt__' will enable *note
     total_ordering(): ee6. to fill-in '__le__', '__gt__' and '__ge__':

          @total_ordering
          class Student:
              def __eq__(self, other):
                  return ((self.lastname.lower(), self.firstname.lower()) ==
                          (other.lastname.lower(), other.firstname.lower()))

              def __lt__(self, other):
                  return ((self.lastname.lower(), self.firstname.lower()) <
                          (other.lastname.lower(), other.firstname.lower()))

     With the 'total_ordering' decorator, the remaining comparison
     methods are filled in automatically.

     （由 Raymond Hettinger 貢獻。）

   * To aid in porting programs from Python 2, the *note
     functools.cmp_to_key(): 1172. function converts an old-style
     comparison function to modern *note key function: dab.:

          >>> # locale-aware sort order
          >>> sorted(iterable, key=cmp_to_key(locale.strcoll))

     For sorting examples and a brief sorting tutorial, see the Sorting
     HowTo(8) tutorial.

     （由 Raymond Hettinger 貢獻。）

   ---------- Footnotes ----------

   (1) 
https://code.activestate.com/recipes/498245-lru-and-lfu-cache-decorators/

   (2) 
https://code.activestate.com/recipes/577479-simple-caching-decorator/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=10586

   (4) https://bugs.python.org/issue?@action=redirect&bpo=10593

   (5) https://bugs.python.org/issue?@action=redirect&bpo=9567

   (6) https://bugs.python.org/issue?@action=redirect&bpo=3445

   (7) https://bugs.python.org/issue?@action=redirect&bpo=8814

   (8) https://wiki.python.org/moin/HowTo/Sorting/


File: python.info,  Node: itertools<7>,  Next: collections<8>,  Prev: functools<7>,  Up: New Improved and Deprecated Modules

1.12.9.4 itertools
..................

   * The *note itertools: 75. module has a new *note accumulate(): 9a1.
     function modeled on APL's 'scan' operator and Numpy's 'accumulate'
     function:

          >>> from itertools import accumulate
          >>> list(accumulate([8, 2, 50]))
          [8, 10, 60]

          >>> prob_dist = [0.1, 0.4, 0.2, 0.3]
          >>> list(accumulate(prob_dist))      # cumulative probability distribution
          [0.1, 0.5, 0.7, 1.0]

     For an example using *note accumulate(): 9a1, see the *note
     examples for the random module: 1174.

     （由 Raymond Hettinger 貢獻，並結合了 Mark Dickinson 的設計建議。）


File: python.info,  Node: collections<8>,  Next: threading<9>,  Prev: itertools<7>,  Up: New Improved and Deprecated Modules

1.12.9.5 collections
....................

   * The *note collections.Counter: 1033. class now has two forms of
     in-place subtraction, the existing '-=' operator for saturating
     subtraction(1) and the new *note subtract(): 1176. method for
     regular subtraction.  The former is suitable for multisets(2) which
     only have positive counts, and the latter is more suitable for use
     cases that allow negative counts:

          >>> from collections import Counter
          >>> tally = Counter(dogs=5, cats=3)
          >>> tally -= Counter(dogs=2, cats=8)    # saturating subtraction
          >>> tally
          Counter({'dogs': 3})

          >>> tally = Counter(dogs=5, cats=3)
          >>> tally.subtract(dogs=2, cats=8)      # regular subtraction
          >>> tally
          Counter({'dogs': 3, 'cats': -5})

     （由 Raymond Hettinger 貢獻。）

   * The *note collections.OrderedDict: 57f. class has a new method
     *note move_to_end(): 1177. which takes an existing key and moves it
     to either the first or last position in the ordered sequence.

     The default is to move an item to the last position.  This is
     equivalent of renewing an entry with ‘od[k] = od.pop(k)’.

     A fast move-to-end operation is useful for resequencing entries.
     For example, an ordered dictionary can be used to track order of
     access by aging entries from the oldest to the most recently
     accessed.

          >>> from collections import OrderedDict
          >>> d = OrderedDict.fromkeys(['a', 'b', 'X', 'd', 'e'])
          >>> list(d)
          ['a', 'b', 'X', 'd', 'e']
          >>> d.move_to_end('X')
          >>> list(d)
          ['a', 'b', 'd', 'e', 'X']

     （由 Raymond Hettinger 貢獻。）

   * The *note collections.deque: 580. class grew two new methods *note
     count(): 1178. and *note reverse(): 1179. that make them more
     substitutable for *note list: 5b6. objects:

          >>> from collections import deque
          >>> d = deque('simsalabim')
          >>> d.count('s')
          2
          >>> d.reverse()
          >>> d
          deque(['m', 'i', 'b', 'a', 'l', 'a', 's', 'm', 'i', 's'])

     （由 Raymond Hettinger 貢獻。）

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Saturation_arithmetic

   (2) https://en.wikipedia.org/wiki/Multiset


File: python.info,  Node: threading<9>,  Next: datetime 和 time,  Prev: collections<8>,  Up: New Improved and Deprecated Modules

1.12.9.6 threading
..................

The *note threading: d6. module has a new *note Barrier: 117b.
synchronization class for making multiple threads wait until all of them
have reached a common barrier point.  Barriers are useful for making
sure that a task with multiple preconditions does not run until all of
the predecessor tasks are complete.

Barriers can work with an arbitrary number of threads.  This is a
generalization of a Rendezvous(1) which is defined for only two threads.

Implemented as a two-phase cyclic barrier, *note Barrier: 117b. objects
are suitable for use in loops.  The separate 'filling' and 'draining'
phases assure that all threads get released (drained) before any one of
them can loop back and re-enter the barrier.  The barrier fully resets
after each cycle.

Example of using barriers:

     from threading import Barrier, Thread

     def get_votes(site):
         ballots = conduct_election(site)
         all_polls_closed.wait()        # do not count until all polls are closed
         totals = summarize(ballots)
         publish(site, totals)

     all_polls_closed = Barrier(len(sites))
     for site in sites:
         Thread(target=get_votes, args=(site,)).start()

In this example, the barrier enforces a rule that votes cannot be
counted at any polling site until all polls are closed.  Notice how a
solution with a barrier is similar to one with *note
threading.Thread.join(): 117c, but the threads stay alive and continue
to do work (summarizing ballots) after the barrier point is crossed.

If any of the predecessor tasks can hang or be delayed, a barrier can be
created with an optional 'timeout' parameter.  Then if the timeout
period elapses before all the predecessor tasks reach the barrier point,
all waiting threads are released and a *note BrokenBarrierError: 117d.
exception is raised:

     def get_votes(site):
         ballots = conduct_election(site)
         try:
             all_polls_closed.wait(timeout=midnight - time.now())
         except BrokenBarrierError:
             lockbox = seal_ballots(ballots)
             queue.put(lockbox)
         else:
             totals = summarize(ballots)
             publish(site, totals)

In this example, the barrier enforces a more robust rule.  If some
election sites do not finish before midnight, the barrier times-out and
the ballots are sealed and deposited in a queue for later handling.

See Barrier Synchronization Patterns(2) for more examples of how
barriers can be used in parallel computing.  Also, there is a simple but
thorough explanation of barriers in The Little Book of Semaphores(3),
'section 3.6'.

（在 bpo-8777(4) 中由 Kristján Valur Jónsson 貢獻、Jeffrey Yasskin 進行
API 審查。）

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Synchronous_rendezvous

   (2) 
https://osl.cs.illinois.edu/media/papers/karmani-2009-barrier_synchronization_pattern.pdf

   (3) https://greenteapress.com/semaphores/LittleBookOfSemaphores.pdf

   (4) https://bugs.python.org/issue?@action=redirect&bpo=8777


File: python.info,  Node: datetime 和 time,  Next: math<10>,  Prev: threading<9>,  Up: New Improved and Deprecated Modules

1.12.9.7 datetime 和 time
.........................

   * The *note datetime: 28. module has a new type *note timezone: 1059.
     that implements the *note tzinfo: 582. interface by returning a
     fixed UTC offset and timezone name.  This makes it easier to create
     timezone-aware datetime objects:

          >>> from datetime import datetime, timezone

          >>> datetime.now(timezone.utc)
          datetime.datetime(2010, 12, 8, 21, 4, 2, 923754, tzinfo=datetime.timezone.utc)

          >>> datetime.strptime("01/01/2000 12:00 +0000", "%m/%d/%Y %H:%M %z")
          datetime.datetime(2000, 1, 1, 12, 0, tzinfo=datetime.timezone.utc)

   * Also, *note timedelta: 973. objects can now be multiplied by *note
     float: 2c8. and divided by *note float: 2c8. and *note int: 23c.
     objects.  And *note timedelta: 973. objects can now divide one
     another.

   * The *note datetime.date.strftime(): c38. method is no longer
     restricted to years after 1900.  The new supported year range is
     from 1000 to 9999 inclusive.

   * Whenever a two-digit year is used in a time tuple, the
     interpretation has been governed by ‘time.accept2dyear’.  The
     default is ‘True’ which means that for a two-digit year, the
     century is guessed according to the POSIX rules governing the ‘%y’
     strptime format.

     Starting with Py3.2, use of the century guessing heuristic will
     emit a *note DeprecationWarning: 18b.  Instead, it is recommended
     that ‘time.accept2dyear’ be set to ‘False’ so that large date
     ranges can be used without guesswork:

          >>> import time, warnings
          >>> warnings.resetwarnings()      # remove the default warning filters

          >>> time.accept2dyear = True      # guess whether 11 means 11 or 2011
          >>> time.asctime((11, 1, 1, 12, 34, 56, 4, 1, 0))
          Warning (from warnings module):
            ...
          DeprecationWarning: Century info guessed for a 2-digit year.
          'Fri Jan  1 12:34:56 2011'

          >>> time.accept2dyear = False     # use the full range of allowable dates
          >>> time.asctime((11, 1, 1, 12, 34, 56, 4, 1, 0))
          'Fri Jan  1 12:34:56 11'

     Several functions now have significantly expanded date ranges.
     When ‘time.accept2dyear’ is false, the *note time.asctime(): 117f.
     function will accept any year that fits in a C int, while the *note
     time.mktime(): 1180. and *note time.strftime(): 1181. functions
     will accept the full range supported by the corresponding operating
     system functions.

（由 Alexander Belopolsky 和 Victor Stinner 在 bpo-1289118(1)、
bpo-5094(2)、bpo-6641(3)、bpo-2706(4)、bpo-1777412(5)、bpo-8013(6) 和
bpo-10827(7) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1289118

   (2) https://bugs.python.org/issue?@action=redirect&bpo=5094

   (3) https://bugs.python.org/issue?@action=redirect&bpo=6641

   (4) https://bugs.python.org/issue?@action=redirect&bpo=2706

   (5) https://bugs.python.org/issue?@action=redirect&bpo=1777412

   (6) https://bugs.python.org/issue?@action=redirect&bpo=8013

   (7) https://bugs.python.org/issue?@action=redirect&bpo=10827


File: python.info,  Node: math<10>,  Next: abc<3>,  Prev: datetime 和 time,  Up: New Improved and Deprecated Modules

1.12.9.8 math
.............

The *note math: 81. module has been updated with six new functions
inspired by the C99 standard.

The *note isfinite(): 1183. function provides a reliable and fast way to
detect special values.  It returns ‘True’ for regular numbers and
‘False’ for 'Nan' or 'Infinity':

     >>> from math import isfinite
     >>> [isfinite(x) for x in (123, 4.56, float('Nan'), float('Inf'))]
     [True, True, False, False]

The *note expm1(): 1184. function computes ‘e**x-1’ for small values of
'x' without incurring the loss of precision that usually accompanies the
subtraction of nearly equal quantities:

     >>> from math import expm1
     >>> expm1(0.013671875)   # more accurate way to compute e**x-1 for a small x
     0.013765762467652909

The *note erf(): b7f. function computes a probability integral or
Gaussian error function(1).  The complementary error function, *note
erfc(): b80, is ‘1 - erf(x)’:

     >>> from math import erf, erfc, sqrt
     >>> erf(1.0/sqrt(2.0))   # portion of normal distribution within 1 standard deviation
     0.682689492137086
     >>> erfc(1.0/sqrt(2.0))  # portion of normal distribution outside 1 standard deviation
     0.31731050786291404
     >>> erf(1.0/sqrt(2.0)) + erfc(1.0/sqrt(2.0))
     1.0

The *note gamma(): 1185. function is a continuous extension of the
factorial function.  See ‘https://en.wikipedia.org/wiki/Gamma_function’
for details.  Because the function is related to factorials, it grows
large even for small values of 'x', so there is also a *note lgamma():
1186. function for computing the natural logarithm of the gamma
function:

     >>> from math import gamma, lgamma
     >>> gamma(7.0)           # six factorial
     720.0
     >>> lgamma(801.0)        # log(800 factorial)
     4551.950730698041

（由 Mark Dickinson 貢獻。）

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Error_function


File: python.info,  Node: abc<3>,  Next: io<7>,  Prev: math<10>,  Up: New Improved and Deprecated Modules

1.12.9.9 abc
............

The *note abc: 4. module now supports *note abstractclassmethod(): 1028.
and *note abstractstaticmethod(): 1029.

These tools make it possible to define an *note abstract base class:
114e. that requires a particular *note classmethod(): 14a. or *note
staticmethod(): 358. to be implemented:

     class Temperature(metaclass=abc.ABCMeta):
         @abc.abstractclassmethod
         def from_fahrenheit(cls, t):
             ...
         @abc.abstractclassmethod
         def from_celsius(cls, t):
             ...

(Patch submitted by Daniel Urban; bpo-5867(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=5867


File: python.info,  Node: io<7>,  Next: reprlib,  Prev: abc<3>,  Up: New Improved and Deprecated Modules

1.12.9.10 io
............

The *note io.BytesIO: e46. has a new method, *note getbuffer(): 1189,
which provides functionality similar to *note memoryview(): 40f.  It
creates an editable view of the data without making a copy.  The
buffer's random access and support for slice notation are well-suited to
in-place editing:

     >>> REC_LEN, LOC_START, LOC_LEN = 34, 7, 11

     >>> def change_location(buffer, record_number, location):
     ...     start = record_number * REC_LEN + LOC_START
     ...     buffer[start: start+LOC_LEN] = location

     >>> import io

     >>> byte_stream = io.BytesIO(
     ...     b'G3805  storeroom  Main chassis    '
     ...     b'X7899  shipping   Reserve cog     '
     ...     b'L6988  receiving  Primary sprocket'
     ... )
     >>> buffer = byte_stream.getbuffer()
     >>> change_location(buffer, 1, b'warehouse  ')
     >>> change_location(buffer, 0, b'showroom   ')
     >>> print(byte_stream.getvalue())
     b'G3805  showroom   Main chassis    '
     b'X7899  warehouse  Reserve cog     '
     b'L6988  receiving  Primary sprocket'

（由 Antoine Pitrou 在 bpo-5506(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=5506


File: python.info,  Node: reprlib,  Next: logging<8>,  Prev: io<7>,  Up: New Improved and Deprecated Modules

1.12.9.11 reprlib
.................

When writing a *note __repr__(): 5c2. method for a custom container, it
is easy to forget to handle the case where a member refers back to the
container itself.  Python's builtin objects such as *note list: 5b6. and
*note set: 57d. handle self-reference by displaying "..."  in the
recursive part of the representation string.

To help write such *note __repr__(): 5c2. methods, the *note reprlib:
a9. module has a new decorator, *note recursive_repr(): 118b, for
detecting recursive calls to ‘__repr__()’ and substituting a placeholder
string instead:

     >>> class MyList(list):
     ...     @recursive_repr()
     ...     def __repr__(self):
     ...         return '<' + '|'.join(map(repr, self)) + '>'
     ...
     >>> m = MyList('abc')
     >>> m.append(m)
     >>> m.append('x')
     >>> print(m)
     <'a'|'b'|'c'|...|'x'>

（由 Raymond Hettinger 在 bpo-9826(1) 和 bpo-9840(2) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=9826

   (2) https://bugs.python.org/issue?@action=redirect&bpo=9840


File: python.info,  Node: logging<8>,  Next: csv<4>,  Prev: reprlib,  Up: New Improved and Deprecated Modules

1.12.9.12 logging
.................

In addition to dictionary-based configuration described above, the *note
logging: 7b. package has many other improvements.

The logging documentation has been augmented by a *note basic tutorial:
118d, an *note advanced tutorial: 118e, and a *note cookbook: 118f. of
logging recipes.  These documents are the fastest way to learn about
logging.

The *note logging.basicConfig(): 9a4. set-up function gained a 'style'
argument to support three different types of string formatting.  It
defaults to "%" for traditional %-formatting, can be set to "{" for the
new *note str.format(): 5c7. style, or can be set to "$" for the
shell-style formatting provided by *note string.Template: 62d.  The
following three configurations are equivalent:

     >>> from logging import basicConfig
     >>> basicConfig(style='%', format="%(name)s -> %(levelname)s: %(message)s")
     >>> basicConfig(style='{', format="{name} -> {levelname} {message}")
     >>> basicConfig(style='$', format="$name -> $levelname: $message")

If no configuration is set-up before a logging event occurs, there is
now a default configuration using a *note StreamHandler: 1190. directed
to *note sys.stderr: 8dd. for events of ‘WARNING’ level or higher.
Formerly, an event occurring before a configuration was set-up would
either raise an exception or silently drop the event depending on the
value of *note logging.raiseExceptions: 1191.  The new default handler
is stored in *note logging.lastResort: 1192.

The use of filters has been simplified.  Instead of creating a *note
Filter: 1193. object, the predicate can be any Python callable that
returns ‘True’ or ‘False’.

There were a number of other improvements that add flexibility and
simplify configuration.  See the module documentation for a full listing
of changes in Python 3.2.


File: python.info,  Node: csv<4>,  Next: contextlib<8>,  Prev: logging<8>,  Up: New Improved and Deprecated Modules

1.12.9.13 csv
.............

The *note csv: 21. module now supports a new dialect, *note
unix_dialect: 1195, which applies quoting for all fields and a
traditional Unix style with ‘'\n'’ as the line terminator.  The
registered dialect name is ‘unix’.

The *note csv.DictWriter: 1196. has a new method, *note writeheader():
1197. for writing-out an initial row to document the field names:

     >>> import csv, sys
     >>> w = csv.DictWriter(sys.stdout, ['name', 'dept'], dialect='unix')
     >>> w.writeheader()
     "name","dept"
     >>> w.writerows([
     ...     {'name': 'tom', 'dept': 'accounting'},
     ...     {'name': 'susan', 'dept': 'Salesl'}])
     "tom","accounting"
     "susan","sales"

(New dialect suggested by Jay Talbot in bpo-5975(1), and the new method
suggested by Ed Abraham in bpo-1537721(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=5975

   (2) https://bugs.python.org/issue?@action=redirect&bpo=1537721


File: python.info,  Node: contextlib<8>,  Next: decimal and fractions,  Prev: csv<4>,  Up: New Improved and Deprecated Modules

1.12.9.14 contextlib
....................

There is a new and slightly mind-blowing tool *note ContextDecorator:
1199. that is helpful for creating a *note context manager: 576. that
does double duty as a function decorator.

As a convenience, this new functionality is used by *note
contextmanager(): 119a. so that no extra effort is needed to support
both roles.

The basic idea is that both context managers and function decorators can
be used for pre-action and post-action wrappers.  Context managers wrap
a group of statements using a *note with: 577. statement, and function
decorators wrap a group of statements enclosed in a function.  So,
occasionally there is a need to write a pre-action or post-action
wrapper that can be used in either role.

For example, it is sometimes useful to wrap functions or groups of
statements with a logger that can track the time of entry and time of
exit.  Rather than writing both a function decorator and a context
manager for the task, the *note contextmanager(): 119a. provides both
capabilities in a single definition:

     from contextlib import contextmanager
     import logging

     logging.basicConfig(level=logging.INFO)

     @contextmanager
     def track_entry_and_exit(name):
         logging.info('Entering: %s', name)
         yield
         logging.info('Exiting: %s', name)

Formerly, this would have only been usable as a context manager:

     with track_entry_and_exit('widget loader'):
         print('Some time consuming activity goes here')
         load_widget()

Now, it can be used as a decorator as well:

     @track_entry_and_exit('widget loader')
     def activity():
         print('Some time consuming activity goes here')
         load_widget()

Trying to fulfill two roles at once places some limitations on the
technique.  Context managers normally have the flexibility to return an
argument usable by a *note with: 577. statement, but there is no
parallel for function decorators.

In the above example, there is not a clean way for the
'track_entry_and_exit' context manager to return a logging instance for
use in the body of enclosed statements.

（由 Michael Foord 在 bpo-9110(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=9110


File: python.info,  Node: decimal and fractions,  Next: ftp,  Prev: contextlib<8>,  Up: New Improved and Deprecated Modules

1.12.9.15 decimal and fractions
...............................

Mark Dickinson crafted an elegant and efficient scheme for assuring that
different numeric datatypes will have the same hash value whenever their
actual values are equal (bpo-8188(1)):

     assert hash(Fraction(3, 2)) == hash(1.5) == \
            hash(Decimal("1.5")) == hash(complex(1.5, 0))

Some of the hashing details are exposed through a new attribute, *note
sys.hash_info: fa0, which describes the bit width of the hash value, the
prime modulus, the hash values for 'infinity' and 'nan', and the
multiplier used for the imaginary part of a number:

     >>> sys.hash_info
     sys.hash_info(width=64, modulus=2305843009213693951, inf=314159, nan=0, imag=1000003)

An early decision to limit the interoperability of various numeric types
has been relaxed.  It is still unsupported (and ill-advised) to have
implicit mixing in arithmetic expressions such as ‘Decimal('1.1') +
float('1.1')’ because the latter loses information in the process of
constructing the binary float.  However, since existing floating-point
value can be converted losslessly to either a decimal or rational
representation, it makes sense to add them to the constructor and to
support mixed-type comparisons.

   * The *note decimal.Decimal: 27c. constructor now accepts *note
     float: 2c8. objects directly so there in no longer a need to use
     the *note from_float(): 119c. method (bpo-8257(2)).

   * Mixed type comparisons are now fully supported so that *note
     Decimal: 27c. objects can be directly compared with *note float:
     2c8. and *note fractions.Fraction: 1c7. (bpo-2531(3) and
     bpo-8188(4)).

Similar changes were made to *note fractions.Fraction: 1c7. so that the
*note from_float(): 119d. and *note from_decimal(): 119e. methods are no
longer needed (bpo-8294(5)):

     >>> from decimal import Decimal
     >>> from fractions import Fraction
     >>> Decimal(1.1)
     Decimal('1.100000000000000088817841970012523233890533447265625')
     >>> Fraction(1.1)
     Fraction(2476979795053773, 2251799813685248)

Another useful change for the *note decimal: 2e. module is that the
‘Context.clamp’ attribute is now public.  This is useful in creating
contexts that correspond to the decimal interchange formats specified in
IEEE 754 (see bpo-8540(6)).

（由 Mark Dickinson 和 Raymond Hettinger 貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=8188

   (2) https://bugs.python.org/issue?@action=redirect&bpo=8257

   (3) https://bugs.python.org/issue?@action=redirect&bpo=2531

   (4) https://bugs.python.org/issue?@action=redirect&bpo=8188

   (5) https://bugs.python.org/issue?@action=redirect&bpo=8294

   (6) https://bugs.python.org/issue?@action=redirect&bpo=8540


File: python.info,  Node: ftp,  Next: popen,  Prev: decimal and fractions,  Up: New Improved and Deprecated Modules

1.12.9.16 ftp
.............

The *note ftplib.FTP: 89f. class now supports the context management
protocol to unconditionally consume *note socket.error: ff8. exceptions
and to close the FTP connection when done:

     >>> from ftplib import FTP
     >>> with FTP("ftp1.at.proftpd.org") as ftp:
             ftp.login()
             ftp.dir()

     '230 Anonymous login ok, restrictions apply.'
     dr-xr-xr-x   9 ftp      ftp           154 May  6 10:43 .
     dr-xr-xr-x   9 ftp      ftp           154 May  6 10:43 ..
     dr-xr-xr-x   5 ftp      ftp          4096 May  6 10:43 CentOS
     dr-xr-xr-x   3 ftp      ftp            18 Jul 10  2008 Fedora

Other file-like objects such as *note mmap.mmap: 1f0. and *note
fileinput.input(): 7a3. also grew auto-closing context managers:

     with fileinput.input(files=('log1.txt', 'log2.txt')) as f:
         for line in f:
             process(line)

（由 Tarek Ziadé 和 Giampaolo Rodolà 在 bpo-4972(1) 中貢獻，由 Georg
Brandl 在 bpo-8046(2) 和 bpo-1286(3) 中貢獻。）

The *note FTP_TLS: 8a0. class now accepts a 'context' parameter, which
is a *note ssl.SSLContext: 276. object allowing bundling SSL
configuration options, certificates and private keys into a single
(potentially long-lived) structure.

（由 Giampaolo Rodolà 貢獻；bpo-8806(4)。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=4972

   (2) https://bugs.python.org/issue?@action=redirect&bpo=8046

   (3) https://bugs.python.org/issue?@action=redirect&bpo=1286

   (4) https://bugs.python.org/issue?@action=redirect&bpo=8806


File: python.info,  Node: popen,  Next: select<3>,  Prev: ftp,  Up: New Improved and Deprecated Modules

1.12.9.17 popen
...............

The *note os.popen(): a2a. and *note subprocess.Popen(): 17d. functions
now support *note with: 577. statements for auto-closing of the file
descriptors.

（由 Antoine Pitrou 和 Brian Curtin 在 bpo-7461(1) 和 bpo-10554(2) 中貢
獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=7461

   (2) https://bugs.python.org/issue?@action=redirect&bpo=10554


File: python.info,  Node: select<3>,  Next: gzip 和 zipfile,  Prev: popen,  Up: New Improved and Deprecated Modules

1.12.9.18 select
................

The *note select: af. module now exposes a new, constant attribute,
*note PIPE_BUF: 11a2, which gives the minimum number of bytes which are
guaranteed not to block when *note select.select(): d46. says a pipe is
ready for writing.

     >>> import select
     >>> select.PIPE_BUF
     512

(Available on Unix systems.  Patch by Sébastien Sablé in bpo-9862(1))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=9862


File: python.info,  Node: gzip 和 zipfile,  Next: tarfile<9>,  Prev: select<3>,  Up: New Improved and Deprecated Modules

1.12.9.19 gzip 和 zipfile
.........................

*note gzip.GzipFile: 354. now implements the *note io.BufferedIOBase:
63a. *note abstract base class: 114e. (except for ‘truncate()’).  It
also has a *note peek(): 11a4. method and supports unseekable as well as
zero-padded file objects.

The *note gzip: 5d. module also gains the *note compress(): 5e4. and
*note decompress(): 11a5. functions for easier in-memory compression and
decompression.  Keep in mind that text needs to be encoded as *note
bytes: 1a5. before compressing and decompressing:

     >>> import gzip
     >>> s = 'Three shall be the number thou shalt count, '
     >>> s += 'and the number of the counting shall be three'
     >>> b = s.encode()                        # convert to utf-8
     >>> len(b)
     89
     >>> c = gzip.compress(b)
     >>> len(c)
     77
     >>> gzip.decompress(c).decode()[:42]      # decompress and convert to text
     'Three shall be the number thou shalt count'

（由 Anand B. Pillai 在 bpo-3488(1) 中貢獻；由 Antoine Pitrou、Nir Aides
和 Brian Curtin 在 bpo-9962(2)、bpo-1675951(3)、bpo-7471(4) 和
bpo-2846(5) 中貢獻。）

Also, the *note zipfile.ZipExtFile: 355. class was reworked internally
to represent files stored inside an archive.  The new implementation is
significantly faster and can be wrapped in an *note io.BufferedReader:
11a6. object for more speedups.  It also solves an issue where
interleaved calls to 'read' and 'readline' gave the wrong results.

(Patch submitted by Nir Aides in bpo-7610(6).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=3488

   (2) https://bugs.python.org/issue?@action=redirect&bpo=9962

   (3) https://bugs.python.org/issue?@action=redirect&bpo=1675951

   (4) https://bugs.python.org/issue?@action=redirect&bpo=7471

   (5) https://bugs.python.org/issue?@action=redirect&bpo=2846

   (6) https://bugs.python.org/issue?@action=redirect&bpo=7610


File: python.info,  Node: tarfile<9>,  Next: hashlib<7>,  Prev: gzip 和 zipfile,  Up: New Improved and Deprecated Modules

1.12.9.20 tarfile
.................

The *note TarFile: 290. class can now be used as a context manager.  In
addition, its *note add(): b9a. method has a new option, 'filter', that
controls which files are added to the archive and allows the file
metadata to be edited.

The new 'filter' option replaces the older, less flexible 'exclude'
parameter which is now deprecated.  If specified, the optional 'filter'
parameter needs to be a *note keyword argument: cb9.  The user-supplied
filter function accepts a *note TarInfo: 11a8. object and returns an
updated *note TarInfo: 11a8. object, or if it wants the file to be
excluded, the function can return ‘None’:

     >>> import tarfile, glob

     >>> def myfilter(tarinfo):
     ...     if tarinfo.isfile():             # only save real files
     ...         tarinfo.uname = 'monty'      # redact the user name
     ...         return tarinfo

     >>> with tarfile.open(name='myarchive.tar.gz', mode='w:gz') as tf:
     ...     for filename in glob.glob('*.txt'):
     ...         tf.add(filename, filter=myfilter)
     ...     tf.list()
     -rw-r--r-- monty/501        902 2011-01-26 17:59:11 annotations.txt
     -rw-r--r-- monty/501        123 2011-01-26 17:59:11 general_questions.txt
     -rw-r--r-- monty/501       3514 2011-01-26 17:59:11 prion.txt
     -rw-r--r-- monty/501        124 2011-01-26 17:59:11 py_todo.txt
     -rw-r--r-- monty/501       1399 2011-01-26 17:59:11 semaphore_notes.txt

（由 Tarek Ziadé 提議並由 Lars Gustäbel 實作於 bpo-6856(1)。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=6856


File: python.info,  Node: hashlib<7>,  Next: ast<5>,  Prev: tarfile<9>,  Up: New Improved and Deprecated Modules

1.12.9.21 hashlib
.................

The *note hashlib: 5e. module has two new constant attributes listing
the hashing algorithms guaranteed to be present in all implementations
and those available on the current implementation:

     >>> import hashlib

     >>> hashlib.algorithms_guaranteed
     {'sha1', 'sha224', 'sha384', 'sha256', 'sha512', 'md5'}

     >>> hashlib.algorithms_available
     {'md2', 'SHA256', 'SHA512', 'dsaWithSHA', 'mdc2', 'SHA224', 'MD4', 'sha256',
     'sha512', 'ripemd160', 'SHA1', 'MDC2', 'SHA', 'SHA384', 'MD2',
     'ecdsa-with-SHA1','md4', 'md5', 'sha1', 'DSA-SHA', 'sha224',
     'dsaEncryption', 'DSA', 'RIPEMD160', 'sha', 'MD5', 'sha384'}

（由 Carl Chenet 在 bpo-7418(1) 中提議。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=7418


File: python.info,  Node: ast<5>,  Next: os<13>,  Prev: hashlib<7>,  Up: New Improved and Deprecated Modules

1.12.9.22 ast
.............

The *note ast: 7. module has a wonderful a general-purpose tool for
safely evaluating expression strings using the Python literal syntax.
The *note ast.literal_eval(): bbf. function serves as a secure
alternative to the builtin *note eval(): 163. function which is easily
abused.  Python 3.2 adds *note bytes: 1a5. and *note set: 57d. literals
to the list of supported types: strings, bytes, numbers, tuples, lists,
dicts, sets, booleans, and ‘None’.

     >>> from ast import literal_eval

     >>> request = "{'req': 3, 'func': 'pow', 'args': (2, 0.5)}"
     >>> literal_eval(request)
     {'args': (2, 0.5), 'req': 3, 'func': 'pow'}

     >>> request = "os.system('do something harmful')"
     >>> literal_eval(request)
     Traceback (most recent call last):
       ...
     ValueError: malformed node or string: <_ast.Call object at 0x101739a10>

（由 Benjamin Peterson 和 Georg Brandl 實作。）


File: python.info,  Node: os<13>,  Next: shutil<8>,  Prev: ast<5>,  Up: New Improved and Deprecated Modules

1.12.9.23 os
............

Different operating systems use various encodings for filenames and
environment variables.  The *note os: 91. module provides two new
functions, *note fsencode(): bfc. and *note fsdecode(): bfb, for
encoding and decoding filenames:

     >>> import os
     >>> filename = 'Sehenswürdigkeiten'
     >>> os.fsencode(filename)
     b'Sehensw\xc3\xbcrdigkeiten'

Some operating systems allow direct access to encoded bytes in the
environment.  If so, the *note os.supports_bytes_environ: 11ac. constant
will be true.

For direct access to encoded environment variables (if available), use
the new *note os.getenvb(): 11ad. function or use *note os.environb:
11ae. which is a bytes version of *note os.environ: 1152.

（由 Victor Stinner 貢獻。）


File: python.info,  Node: shutil<8>,  Next: sqlite3<11>,  Prev: os<13>,  Up: New Improved and Deprecated Modules

1.12.9.24 shutil
................

The *note shutil.copytree(): 9cd. function has two new options:

   * 'ignore_dangling_symlinks': when ‘symlinks=False’ so that the
     function copies a file pointed to by a symlink, not the symlink
     itself.  This option will silence the error raised if the file
     doesn't exist.

   * 'copy_function': is a callable that will be used to copy files.
     *note shutil.copy2(): 9fe. is used by default.

（由 Tarek Ziadé 貢獻。）

In addition, the *note shutil: b3. module now supports *note archiving
operations: 11b0. for zipfiles, uncompressed tarfiles, gzipped tarfiles,
and bzipped tarfiles.  And there are functions for registering
additional archiving file formats (such as xz compressed tarfiles or
custom formats).

The principal functions are *note make_archive(): 45a. and *note
unpack_archive(): 412.  By default, both operate on the current
directory (which can be set by *note os.chdir(): 5b2.) and on any
sub-directories.  The archive filename needs to be specified with a full
pathname.  The archiving step is non-destructive (the original files are
left unchanged).

     >>> import shutil, pprint

     >>> os.chdir('mydata')  # change to the source directory
     >>> f = shutil.make_archive('/var/backup/mydata',
     ...                         'zip')      # archive the current directory
     >>> f                                   # show the name of archive
     '/var/backup/mydata.zip'
     >>> os.chdir('tmp')                     # change to an unpacking
     >>> shutil.unpack_archive('/var/backup/mydata.zip')  # recover the data

     >>> pprint.pprint(shutil.get_archive_formats())  # display known formats
     [('bztar', "bzip2'ed tar-file"),
      ('gztar', "gzip'ed tar-file"),
      ('tar', 'uncompressed tar file'),
      ('zip', 'ZIP file')]

     >>> shutil.register_archive_format(     # register a new archive format
     ...     name='xz',
     ...     function=xz.compress,           # callable archiving function
     ...     extra_args=[('level', 8)],      # arguments to the function
     ...     description='xz compression'
     ... )

（由 Tarek Ziadé 貢獻。）


File: python.info,  Node: sqlite3<11>,  Next: html<3>,  Prev: shutil<8>,  Up: New Improved and Deprecated Modules

1.12.9.25 sqlite3
.................

The *note sqlite3: ba. module was updated to pysqlite version 2.6.0.  It
has two new capabilities.

   * The ‘sqlite3.Connection.in_transit’ attribute is true if there is
     an active transaction for uncommitted changes.

   * The *note sqlite3.Connection.enable_load_extension(): 7e2. and
     *note sqlite3.Connection.load_extension(): 45f. methods allows you
     to load SQLite extensions from ".so" files.  One well-known
     extension is the fulltext-search extension distributed with SQLite.

（由 R. David Murray 和 Shashwat Anand 貢獻；bpo-8845(1)。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=8845


File: python.info,  Node: html<3>,  Next: socket<11>,  Prev: sqlite3<11>,  Up: New Improved and Deprecated Modules

1.12.9.26 html
..............

A new *note html: 61. module was introduced with only a single function,
*note escape(): faf, which is used for escaping reserved characters from
HTML markup:

     >>> import html
     >>> html.escape('x > 2 && x < 7')
     'x &gt; 2 &amp;&amp; x &lt; 7'


File: python.info,  Node: socket<11>,  Next: ssl<12>,  Prev: html<3>,  Up: New Improved and Deprecated Modules

1.12.9.27 socket
................

The *note socket: b8. module has two new improvements.

   * Socket objects now have a *note detach(): 11b4. method which puts
     the socket into closed state without actually closing the
     underlying file descriptor.  The latter can then be reused for
     other purposes.  (Added by Antoine Pitrou; bpo-8524(1).)

   * *note socket.create_connection(): 618. now supports the context
     management protocol to unconditionally consume *note socket.error:
     ff8. exceptions and to close the socket when done.  (Contributed by
     Giampaolo Rodolà; bpo-9794(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=8524

   (2) https://bugs.python.org/issue?@action=redirect&bpo=9794


File: python.info,  Node: ssl<12>,  Next: nntp,  Prev: socket<11>,  Up: New Improved and Deprecated Modules

1.12.9.28 ssl
.............

The *note ssl: bb. module added a number of features to satisfy common
requirements for secure (encrypted, authenticated) internet connections:

   * A new class, *note SSLContext: 276, serves as a container for
     persistent SSL data, such as protocol settings, certificates,
     private keys, and various other options.  It includes a *note
     wrap_socket(): 4c9. for creating an SSL socket from an SSL context.

   * A new function, ‘ssl.match_hostname()’, supports server identity
     verification for higher-level protocols by implementing the rules
     of HTTPS (from RFC 2818(1)) which are also suitable for other
     protocols.

   * The *note ssl.wrap_socket(): 4c9. constructor function now takes a
     'ciphers' argument.  The 'ciphers' string lists the allowed
     encryption algorithms using the format described in the OpenSSL
     documentation(2).

   * When linked against recent versions of OpenSSL, the *note ssl: bb.
     module now supports the Server Name Indication extension to the TLS
     protocol, allowing multiple "virtual hosts" using different
     certificates on a single IP port.  This extension is only supported
     in client mode, and is activated by passing the 'server_hostname'
     argument to *note ssl.SSLContext.wrap_socket(): 4c9.

   * Various options have been added to the *note ssl: bb. module, such
     as *note OP_NO_SSLv2: 7dd. which disables the insecure and obsolete
     SSLv2 protocol.

   * The extension now loads all the OpenSSL ciphers and digest
     algorithms.  If some SSL certificates cannot be verified, they are
     reported as an "unknown algorithm" error.

   * The version of OpenSSL being used is now accessible using the
     module attributes *note ssl.OPENSSL_VERSION: 11b6. (a string),
     *note ssl.OPENSSL_VERSION_INFO: 11b7. (a 5-tuple), and *note
     ssl.OPENSSL_VERSION_NUMBER: 11b8. (an integer).

（由 Antoine Pitrou 在 bpo-8850(3)、bpo-1589(4)、bpo-8322(5)、
bpo-5639(6)、bpo-4870(7)、bpo-8484(8) 和 bpo-8321(9) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2818.html

   (2) 
https://www.openssl.org/docs/man1.0.2/man1/ciphers.html#CIPHER-LIST-FORMAT

   (3) https://bugs.python.org/issue?@action=redirect&bpo=8850

   (4) https://bugs.python.org/issue?@action=redirect&bpo=1589

   (5) https://bugs.python.org/issue?@action=redirect&bpo=8322

   (6) https://bugs.python.org/issue?@action=redirect&bpo=5639

   (7) https://bugs.python.org/issue?@action=redirect&bpo=4870

   (8) https://bugs.python.org/issue?@action=redirect&bpo=8484

   (9) https://bugs.python.org/issue?@action=redirect&bpo=8321


File: python.info,  Node: nntp,  Next: certificates,  Prev: ssl<12>,  Up: New Improved and Deprecated Modules

1.12.9.29 nntp
..............

The ‘nntplib’ module has a revamped implementation with better bytes and
text semantics as well as more practical APIs.  These improvements break
compatibility with the nntplib version in Python 3.1, which was partly
dysfunctional in itself.

Support for secure connections through both implicit (using
‘nntplib.NNTP_SSL’) and explicit (using ‘nntplib.NNTP.starttls()’) TLS
has also been added.

（由 Antoine Pitrou 在 bpo-9360(1) 中和 Andrew Vant 在 bpo-1926(2) 中貢
獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=9360

   (2) https://bugs.python.org/issue?@action=redirect&bpo=1926


File: python.info,  Node: certificates,  Next: imaplib<4>,  Prev: nntp,  Up: New Improved and Deprecated Modules

1.12.9.30 certificates
......................

*note http.client.HTTPSConnection: ae5, *note
urllib.request.HTTPSHandler: 11bb. and *note urllib.request.urlopen():
275. now take optional arguments to allow for server certificate
checking against a set of Certificate Authorities, as recommended in
public uses of HTTPS.

(Added by Antoine Pitrou, bpo-9003(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=9003


File: python.info,  Node: imaplib<4>,  Next: http client<4>,  Prev: certificates,  Up: New Improved and Deprecated Modules

1.12.9.31 imaplib
.................

Support for explicit TLS on standard IMAP4 connections has been added
through the new *note imaplib.IMAP4.starttls: 11bd. method.

（由 Lorenzo M. Catucci 和 Antoine Pitrou 於 bpo-4471(1) 貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=4471


File: python.info,  Node: http client<4>,  Next: unittest<11>,  Prev: imaplib<4>,  Up: New Improved and Deprecated Modules

1.12.9.32 http.client
.....................

There were a number of small API improvements in the *note http.client:
65. module.  The old-style HTTP 0.9 simple responses are no longer
supported and the 'strict' parameter is deprecated in all classes.

The *note HTTPConnection: ae4. and *note HTTPSConnection: ae5. classes
now have a 'source_address' parameter for a (host, port) tuple
indicating where the HTTP connection is made from.

Support for certificate checking and HTTPS virtual hosts were added to
*note HTTPSConnection: ae5.

The *note request(): c50. method on connection objects allowed an
optional 'body' argument so that a *note file object: 115b. could be
used to supply the content of the request.  Conveniently, the 'body'
argument now also accepts an *note iterable: 11bf. object so long as it
includes an explicit ‘Content-Length’ header.  This extended interface
is much more flexible than before.

To establish an HTTPS connection through a proxy server, there is a new
*note set_tunnel(): 11c0. method that sets the host and port for HTTP
Connect tunneling.

To match the behavior of *note http.server: 68, the HTTP client library
now also encodes headers with ISO-8859-1 (Latin-1) encoding.  It was
already doing that for incoming headers, so now the behavior is
consistent for both incoming and outgoing traffic.  (See work by Armin
Ronacher in bpo-10980(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=10980


File: python.info,  Node: unittest<11>,  Next: random<5>,  Prev: http client<4>,  Up: New Improved and Deprecated Modules

1.12.9.33 unittest
..................

The unittest module has a number of improvements supporting test
discovery for packages, easier experimentation at the interactive
prompt, new testcase methods, improved diagnostic messages for test
failures, and better method names.

   * The command-line call ‘python -m unittest’ can now accept file
     paths instead of module names for running specific tests
     (bpo-10620(1)).  The new test discovery can find tests within
     packages, locating any test importable from the top-level
     directory.  The top-level directory can be specified with the ‘-t’
     option, a pattern for matching files with ‘-p’, and a directory to
     start discovery with ‘-s’:

          $ python -m unittest discover -s my_proj_dir -p _test.py

     （由 Michael Foord 貢獻。）

   * Experimentation at the interactive prompt is now easier because the
     *note unittest.TestCase: 3f4. class can now be instantiated without
     arguments:

          >>> from unittest import TestCase
          >>> TestCase().assertEqual(pow(2, 3), 8)

     （由 Michael Foord 貢獻。）

   * The *note unittest: ef. module has two new methods, *note
     assertWarns(): 10fd. and *note assertWarnsRegex(): 10fe. to verify
     that a given warning type is triggered by the code under test:

          with self.assertWarns(DeprecationWarning):
              legacy_function('XYZ')

     （由 Antoine Pitrou 於 bpo-9754(2) 貢獻。）

     Another new method, *note assertCountEqual(): 11c2. is used to
     compare two iterables to determine if their element counts are
     equal (whether the same elements are present with the same number
     of occurrences regardless of order):

          def test_anagram(self):
              self.assertCountEqual('algorithm', 'logarithm')

     （由 Raymond Hettinger 貢獻。）

   * A principal feature of the unittest module is an effort to produce
     meaningful diagnostics when a test fails.  When possible, the
     failure is recorded along with a diff of the output.  This is
     especially helpful for analyzing log files of failed test runs.
     However, since diffs can sometime be voluminous, there is a new
     *note maxDiff: 11c3. attribute that sets maximum length of diffs
     displayed.

   * In addition, the method names in the module have undergone a number
     of clean-ups.

     For example, *note assertRegex(): 4d2. is the new name for
     ‘assertRegexpMatches()’ which was misnamed because the test uses
     *note re.search(): 11c4, not *note re.match(): 11c5.  Other methods
     using regular expressions are now named using short form "Regex" in
     preference to "Regexp" - this matches the names used in other
     unittest implementations, matches Python's old name for the *note
     re: a7. module, and it has unambiguous camel-casing.

     （由 Raymond Hettinger 貢獻，由 Ezio Melotti 實作。）

   * To improve consistency, some long-standing method aliases are being
     deprecated in favor of the preferred names:

          舊名稱                              Preferred Name
                                              
          -----------------------------------------------------------------------
                                              
          ‘assert_()’                         *note assertTrue(): 4cb.
                                              
                                              
          ‘assertEquals()’                    *note assertEqual(): 4cd.
                                              
                                              
          ‘assertNotEquals()’                 *note assertNotEqual(): 4ce.
                                              
                                              
          ‘assertAlmostEquals()’              *note assertAlmostEqual(): 4cf.
                                              
                                              
          ‘assertNotAlmostEquals()’           *note assertNotAlmostEqual(): 4d0.
                                              

     Likewise, the ‘TestCase.fail*’ methods deprecated in Python 3.1 are
     expected to be removed in Python 3.3.

     （由 Ezio Melotti 貢獻；bpo-9424(3)。）

   * The ‘assertDictContainsSubset()’ method was deprecated because it
     was misimplemented with the arguments in the wrong order.  This
     created hard-to-debug optical illusions where tests like
     ‘TestCase().assertDictContainsSubset({'a':1, 'b':2}, {'a':1})’
     would fail.

     （由 Raymond Hettinger 貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=10620

   (2) https://bugs.python.org/issue?@action=redirect&bpo=9754

   (3) https://bugs.python.org/issue?@action=redirect&bpo=9424


File: python.info,  Node: random<5>,  Next: poplib<4>,  Prev: unittest<11>,  Up: New Improved and Deprecated Modules

1.12.9.34 random
................

The integer methods in the *note random: a6. module now do a better job
of producing uniform distributions.  Previously, they computed
selections with ‘int(n*random())’ which had a slight bias whenever 'n'
was not a power of two.  Now, multiple selections are made from a range
up to the next power of two and a selection is kept only when it falls
within the range ‘0 <= x < n’.  The functions and methods affected are
*note randrange(): 810, *note randint(): 11c7, *note choice(): 11c8,
*note shuffle(): 6eb. and *note sample(): 6ea.

（由 Raymond Hettinger 貢獻；bpo-9025(1)。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=9025


File: python.info,  Node: poplib<4>,  Next: asyncore<2>,  Prev: random<5>,  Up: New Improved and Deprecated Modules

1.12.9.35 poplib
................

*note POP3_SSL: 8ca. class now accepts a 'context' parameter, which is a
*note ssl.SSLContext: 276. object allowing bundling SSL configuration
options, certificates and private keys into a single (potentially
long-lived) structure.

（由 Giampaolo Rodolà 貢獻；bpo-8807(1)。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=8807


File: python.info,  Node: asyncore<2>,  Next: tempfile<5>,  Prev: poplib<4>,  Up: New Improved and Deprecated Modules

1.12.9.36 asyncore
..................

‘asyncore.dispatcher’ now provides a ‘handle_accepted()’ method
returning a ‘(sock, addr)’ pair which is called when a connection has
actually been established with a new remote endpoint.  This is supposed
to be used as a replacement for old ‘handle_accept()’ and avoids the
user to call ‘accept()’ directly.

（由 Giampaolo Rodolà 貢獻；bpo-6706(1)。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=6706


File: python.info,  Node: tempfile<5>,  Next: inspect<10>,  Prev: asyncore<2>,  Up: New Improved and Deprecated Modules

1.12.9.37 tempfile
..................

The *note tempfile: c9. module has a new context manager, *note
TemporaryDirectory: 11cc. which provides easy deterministic cleanup of
temporary directories:

     with tempfile.TemporaryDirectory() as tmpdirname:
         print('created temporary dir:', tmpdirname)

（由 Neil Schedulenauer 和 Nick Coghlan 貢獻；bpo-5178(1)。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=5178


File: python.info,  Node: inspect<10>,  Next: pydoc<6>,  Prev: tempfile<5>,  Up: New Improved and Deprecated Modules

1.12.9.38 inspect
.................

   * The *note inspect: 72. module has a new function *note
     getgeneratorstate(): 11ce. to easily identify the current state of
     a generator-iterator:

          >>> from inspect import getgeneratorstate
          >>> def gen():
          ...     yield 'demo'
          ...
          >>> g = gen()
          >>> getgeneratorstate(g)
          'GEN_CREATED'
          >>> next(g)
          'demo'
          >>> getgeneratorstate(g)
          'GEN_SUSPENDED'
          >>> next(g, None)
          >>> getgeneratorstate(g)
          'GEN_CLOSED'

     （由 Rodolfo Eckhardt 和 Nick Coghlan 於 bpo-10220(1) 貢獻。）

   * To support lookups without the possibility of activating a dynamic
     attribute, the *note inspect: 72. module has a new function, *note
     getattr_static(): 43c.  Unlike *note hasattr(): 479, this is a true
     read-only search, guaranteed not to change state while it is
     searching:

          >>> class A:
          ...     @property
          ...     def f(self):
          ...         print('Running')
          ...         return 10
          ...
          >>> a = A()
          >>> getattr(a, 'f')
          Running
          10
          >>> inspect.getattr_static(a, 'f')
          <property object at 0x1022bd788>

     （由 Michael Foord 貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=10220


File: python.info,  Node: pydoc<6>,  Next: dis<5>,  Prev: inspect<10>,  Up: New Improved and Deprecated Modules

1.12.9.39 pydoc
...............

The *note pydoc: a3. module now provides a much-improved web server
interface, as well as a new command-line option ‘-b’ to automatically
open a browser window to display that server:

     $ pydoc3.2 -b

（由 Ron Adam 貢獻；bpo-2001(1)。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=2001


File: python.info,  Node: dis<5>,  Next: dbm<7>,  Prev: pydoc<6>,  Up: New Improved and Deprecated Modules

1.12.9.40 dis
.............

The *note dis: 30. module gained two new functions for inspecting code,
*note code_info(): 11d1. and *note show_code(): ed0.  Both provide
detailed code object information for the supplied function, method,
source code string or code object.  The former returns a string and the
latter prints it:

     >>> import dis, random
     >>> dis.show_code(random.choice)
     Name:              choice
     Filename:          /Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/random.py
     Argument count:    2
     Kw-only arguments: 0
     Number of locals:  3
     Stack size:        11
     Flags:             OPTIMIZED, NEWLOCALS, NOFREE
     Constants:
        0: 'Choose a random element from a non-empty sequence.'
        1: 'Cannot choose from an empty sequence'
     Names:
        0: _randbelow
        1: len
        2: ValueError
        3: IndexError
     Variable names:
        0: self
        1: seq
        2: i

In addition, the *note dis(): ad8. function now accepts string arguments
so that the common idiom ‘dis(compile(s, '', 'eval'))’ can be shortened
to ‘dis(s)’:

     >>> dis('3*x+1 if x%2==1 else x//2')
       1           0 LOAD_NAME                0 (x)
                   3 LOAD_CONST               0 (2)
                   6 BINARY_MODULO
                   7 LOAD_CONST               1 (1)
                  10 COMPARE_OP               2 (==)
                  13 POP_JUMP_IF_FALSE       28
                  16 LOAD_CONST               2 (3)
                  19 LOAD_NAME                0 (x)
                  22 BINARY_MULTIPLY
                  23 LOAD_CONST               1 (1)
                  26 BINARY_ADD
                  27 RETURN_VALUE
             >>   28 LOAD_NAME                0 (x)
                  31 LOAD_CONST               0 (2)
                  34 BINARY_FLOOR_DIVIDE
                  35 RETURN_VALUE

Taken together, these improvements make it easier to explore how CPython
is implemented and to see for yourself what the language syntax does
under-the-hood.

（由 Nick Coghlan 在 bpo-9147(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=9147


File: python.info,  Node: dbm<7>,  Next: ctypes<2>,  Prev: dis<5>,  Up: New Improved and Deprecated Modules

1.12.9.41 dbm
.............

All database modules now support the ‘get()’ and ‘setdefault()’ methods.

（由 Ray Allen 在 bpo-9523(1) 中建議。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=9523


File: python.info,  Node: ctypes<2>,  Next: site<4>,  Prev: dbm<7>,  Up: New Improved and Deprecated Modules

1.12.9.42 ctypes
................

A new type, *note ctypes.c_ssize_t: 11d4. represents the C ‘ssize_t’
datatype.


File: python.info,  Node: site<4>,  Next: sysconfig<3>,  Prev: ctypes<2>,  Up: New Improved and Deprecated Modules

1.12.9.43 site
..............

The *note site: b5. module has three new functions useful for reporting
on the details of a given Python installation.

   * *note getsitepackages(): 11d6. lists all global site-packages
     directories.

   * *note getuserbase(): 11d7. reports on the user's base directory
     where data can be stored.

   * *note getusersitepackages(): 11d8. reveals the user-specific
     site-packages directory path.

     >>> import site
     >>> site.getsitepackages()
     ['/Library/Frameworks/Python.framework/Versions/3.2/lib/python3.2/site-packages',
      '/Library/Frameworks/Python.framework/Versions/3.2/lib/site-python',
      '/Library/Python/3.2/site-packages']
     >>> site.getuserbase()
     '/Users/raymondhettinger/Library/Python/3.2'
     >>> site.getusersitepackages()
     '/Users/raymondhettinger/Library/Python/3.2/lib/python/site-packages'

Conveniently, some of site's functionality is accessible directly from
the command-line:

     $ python -m site --user-base
     /Users/raymondhettinger/.local
     $ python -m site --user-site
     /Users/raymondhettinger/.local/lib/python3.2/site-packages

（由 Tarek Ziadé 在 bpo-6693(1) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=6693


File: python.info,  Node: sysconfig<3>,  Next: pdb<8>,  Prev: site<4>,  Up: New Improved and Deprecated Modules

1.12.9.44 sysconfig
...................

The new *note sysconfig: c5. module makes it straightforward to discover
installation paths and configuration variables that vary across
platforms and installations.

The module offers access simple access functions for platform and
version information:

   * *note get_platform(): 11da. returning values like 'linux-i586' or
     'macosx-10.6-ppc'.

   * *note get_python_version(): 11db. returns a Python version string
     such as "3.2".

It also provides access to the paths and variables corresponding to one
of seven named schemes used by ‘distutils’.  Those include
'posix_prefix', 'posix_home', 'posix_user', 'nt', 'nt_user', 'os2',
'os2_home':

   * *note get_paths(): 11dc. makes a dictionary containing installation
     paths for the current installation scheme.

   * *note get_config_vars(): fcf. returns a dictionary of platform
     specific variables.

There is also a convenient command-line interface:

     C:\Python32>python -m sysconfig
     Platform: "win32"
     Python version: "3.2"
     Current installation scheme: "nt"

     Paths:
             data = "C:\Python32"
             include = "C:\Python32\Include"
             platinclude = "C:\Python32\Include"
             platlib = "C:\Python32\Lib\site-packages"
             platstdlib = "C:\Python32\Lib"
             purelib = "C:\Python32\Lib\site-packages"
             scripts = "C:\Python32\Scripts"
             stdlib = "C:\Python32\Lib"

     Variables:
             BINDIR = "C:\Python32"
             BINLIBDEST = "C:\Python32\Lib"
             EXE = ".exe"
             INCLUDEPY = "C:\Python32\Include"
             LIBDEST = "C:\Python32\Lib"
             SO = ".pyd"
             VERSION = "32"
             abiflags = ""
             base = "C:\Python32"
             exec_prefix = "C:\Python32"
             platbase = "C:\Python32"
             prefix = "C:\Python32"
             projectbase = "C:\Python32"
             py_version = "3.2"
             py_version_nodot = "32"
             py_version_short = "3.2"
             srcdir = "C:\Python32"
             userbase = "C:\Documents and Settings\Raymond\Application Data\Python"

(Moved out of Distutils by Tarek Ziadé.)


File: python.info,  Node: pdb<8>,  Next: configparser<6>,  Prev: sysconfig<3>,  Up: New Improved and Deprecated Modules

1.12.9.45 pdb
.............

The *note pdb: 94. debugger module gained a number of usability
improvements:

   * ‘pdb.py’ now has a ‘-c’ option that executes commands as given in a
     ‘.pdbrc’ script file.

   * A ‘.pdbrc’ script file can contain ‘continue’ and ‘next’ commands
     that continue debugging.

   * 現在 *note Pdb: 8c7. 類別建構函式接受 'nosigint' 引數。

   * New commands: ‘l(list)’, ‘ll(long list)’ and ‘source’ for listing
     source code.

   * New commands: ‘display’ and ‘undisplay’ for showing or hiding the
     value of an expression if it has changed.

   * New command: ‘interact’ for starting an interactive interpreter
     containing the global and local names found in the current scope.

   * Breakpoints can be cleared by breakpoint number.

（由 Georg Brandl、Antonio Cuni 和 Ilya Sandler 貢獻。）


File: python.info,  Node: configparser<6>,  Next: urllib parse<6>,  Prev: pdb<8>,  Up: New Improved and Deprecated Modules

1.12.9.46 configparser
......................

The *note configparser: 1b. module was modified to improve usability and
predictability of the default parser and its supported INI syntax.  The
old ‘ConfigParser’ class was removed in favor of ‘SafeConfigParser’
which has in turn been renamed to *note ConfigParser: 1aa.  Support for
inline comments is now turned off by default and section or option
duplicates are not allowed in a single configuration source.

Config parsers gained a new API based on the mapping protocol:

     >>> parser = ConfigParser()
     >>> parser.read_string("""
     ... [DEFAULT]
     ... location = upper left
     ... visible = yes
     ... editable = no
     ... color = blue
     ...
     ... [main]
     ... title = Main Menu
     ... color = green
     ...
     ... [options]
     ... title = Options
     ... """)
     >>> parser['main']['color']
     'green'
     >>> parser['main']['editable']
     'no'
     >>> section = parser['options']
     >>> section['title']
     'Options'
     >>> section['title'] = 'Options (editable: %(editable)s)'
     >>> section['title']
     'Options (editable: no)'

The new API is implemented on top of the classical API, so custom parser
subclasses should be able to use it without modifications.

The INI file structure accepted by config parsers can now be customized.
Users can specify alternative option/value delimiters and comment
prefixes, change the name of the 'DEFAULT' section or switch the
interpolation syntax.

There is support for pluggable interpolation including an additional
interpolation handler *note ExtendedInterpolation: 6c7.:

     >>> parser = ConfigParser(interpolation=ExtendedInterpolation())
     >>> parser.read_dict({'buildout': {'directory': '/home/ambv/zope9'},
     ...                   'custom': {'prefix': '/usr/local'}})
     >>> parser.read_string("""
     ... [buildout]
     ... parts =
     ...   zope9
     ...   instance
     ... find-links =
     ...   ${buildout:directory}/downloads/dist
     ...
     ... [zope9]
     ... recipe = plone.recipe.zope9install
     ... location = /opt/zope
     ...
     ... [instance]
     ... recipe = plone.recipe.zope9instance
     ... zope9-location = ${zope9:location}
     ... zope-conf = ${custom:prefix}/etc/zope.conf
     ... """)
     >>> parser['buildout']['find-links']
     '\n/home/ambv/zope9/downloads/dist'
     >>> parser['instance']['zope-conf']
     '/usr/local/etc/zope.conf'
     >>> instance = parser['instance']
     >>> instance['zope-conf']
     '/usr/local/etc/zope.conf'
     >>> instance['zope9-location']
     '/opt/zope'

A number of smaller features were also introduced, like support for
specifying encoding in read operations, specifying fallback values for
get-functions, or reading directly from dictionaries and strings.

(All changes contributed by Łukasz Langa.)


File: python.info,  Node: urllib parse<6>,  Next: mailbox,  Prev: configparser<6>,  Up: New Improved and Deprecated Modules

1.12.9.47 urllib.parse
......................

A number of usability improvements were made for the *note urllib.parse:
f3. module.

The *note urlparse(): 2df. function now supports IPv6(1) addresses as
described in RFC 2732(2):

     >>> import urllib.parse
     >>> urllib.parse.urlparse('http://[dead:beef:cafe:5417:affe:8FA3:deaf:feed]/foo/')
     ParseResult(scheme='http',
                 netloc='[dead:beef:cafe:5417:affe:8FA3:deaf:feed]',
                 path='/foo/',
                 params='',
                 query='',
                 fragment='')

The *note urldefrag(): 11e0. function now returns a *note named tuple:
5f4.:

     >>> r = urllib.parse.urldefrag('http://python.org/about/#target')
     >>> r
     DefragResult(url='http://python.org/about/', fragment='target')
     >>> r[0]
     'http://python.org/about/'
     >>> r.fragment
     'target'

And, the *note urlencode(): e37. function is now much more flexible,
accepting either a string or bytes type for the 'query' argument.  If it
is a string, then the 'safe', 'encoding', and 'error' parameters are
sent to *note quote_plus(): 11e1. for encoding:

     >>> urllib.parse.urlencode([
     ...      ('type', 'telenovela'),
     ...      ('name', '¿Dónde Está Elisa?')],
     ...      encoding='latin-1')
     'type=telenovela&name=%BFD%F3nde+Est%E1+Elisa%3F'

As detailed in *note Parsing ASCII Encoded Bytes: 11e2, all the *note
urllib.parse: f3. functions now accept ASCII-encoded byte strings as
input, so long as they are not mixed with regular strings.  If
ASCII-encoded byte strings are given as parameters, the return types
will also be an ASCII-encoded byte strings:

     >>> urllib.parse.urlparse(b'http://www.python.org:80/about/')
     ParseResultBytes(scheme=b'http', netloc=b'www.python.org:80',
                      path=b'/about/', params=b'', query=b'', fragment=b'')

(Work by Nick Coghlan, Dan Mahn, and Senthil Kumaran in bpo-2987(3),
bpo-5468(4), and bpo-9873(5).)

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/IPv6

   (2) https://datatracker.ietf.org/doc/html/rfc2732.html

   (3) https://bugs.python.org/issue?@action=redirect&bpo=2987

   (4) https://bugs.python.org/issue?@action=redirect&bpo=5468

   (5) https://bugs.python.org/issue?@action=redirect&bpo=9873


File: python.info,  Node: mailbox,  Next: turtledemo,  Prev: urllib parse<6>,  Up: New Improved and Deprecated Modules

1.12.9.48 mailbox
.................

Thanks to a concerted effort by R. David Murray, the *note mailbox: 7f.
module has been fixed for Python 3.2.  The challenge was that mailbox
had been originally designed with a text interface, but email messages
are best represented with *note bytes: 1a5. because various parts of a
message may have different encodings.

The solution harnessed the *note email: 32. package's binary support for
parsing arbitrary email messages.  In addition, the solution required a
number of API changes.

As expected, the *note add(): 11e4. method for *note mailbox.Mailbox:
11e5. objects now accepts binary input.

*note StringIO: ecb. and text file input are deprecated.  Also, string
input will fail early if non-ASCII characters are used.  Previously it
would fail when the email was processed in a later step.

There is also support for binary output.  The *note get_file(): 11e6.
method now returns a file in the binary mode (where it used to
incorrectly set the file to text-mode).  There is also a new *note
get_bytes(): 11e7. method that returns a *note bytes: 1a5.
representation of a message corresponding to a given 'key'.

It is still possible to get non-binary output using the old API's *note
get_string(): 11e8. method, but that approach is not very useful.
Instead, it is best to extract messages from a *note Message: 11e9.
object or to load them from binary input.

(Contributed by R. David Murray, with efforts from Steffen Daode
Nurpmeso and an initial patch by Victor Stinner in bpo-9124(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=9124


File: python.info,  Node: turtledemo,  Prev: mailbox,  Up: New Improved and Deprecated Modules

1.12.9.49 turtledemo
....................

The demonstration code for the *note turtle: ea. module was moved from
the 'Demo' directory to main library.  It includes over a dozen sample
scripts with lively displays.  Being on *note sys.path: 37f, it can now
be run directly from the command-line:

     $ python -m turtledemo

(Moved from the Demo directory by Alexander Belopolsky in bpo-10199(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=10199


File: python.info,  Node: Multi-threading,  Next: 最佳化<10>,  Prev: New Improved and Deprecated Modules,  Up: Python 3 2 有什麼新功能

1.12.10 Multi-threading
-----------------------

   * The mechanism for serializing execution of concurrently running
     Python threads (generally known as the *note GIL: 13e. or Global
     Interpreter Lock) has been rewritten.  Among the objectives were
     more predictable switching intervals and reduced overhead due to
     lock contention and the number of ensuing system calls.  The notion
     of a "check interval" to allow thread switches has been abandoned
     and replaced by an absolute duration expressed in seconds.  This
     parameter is tunable through *note sys.setswitchinterval(): 8ee.
     It currently defaults to 5 milliseconds.

     Additional details about the implementation can be read from a
     python-dev mailing-list message(1) (however, "priority requests" as
     exposed in this message have not been kept for inclusion).

     （由 Antoine Pitrou 貢獻。）

   * Regular and recursive locks now accept an optional 'timeout'
     argument to their *note acquire(): 63e. method.  (Contributed by
     Antoine Pitrou; bpo-7316(2).)

   * Similarly, *note threading.Semaphore.acquire(): 11ec. also gained a
     'timeout' argument.  (Contributed by Torsten Landschoff;
     bpo-850728(3).)

   * Regular and recursive lock acquisitions can now be interrupted by
     signals on platforms using Pthreads.  This means that Python
     programs that deadlock while acquiring locks can be successfully
     killed by repeatedly sending SIGINT to the process (by pressing
     ‘Ctrl+C’ in most shells).  (Contributed by Reid Kleckner;
     bpo-8844(4).)

   ---------- Footnotes ----------

   (1) 
https://mail.python.org/pipermail/python-dev/2009-October/093321.html

   (2) https://bugs.python.org/issue?@action=redirect&bpo=7316

   (3) https://bugs.python.org/issue?@action=redirect&bpo=850728

   (4) https://bugs.python.org/issue?@action=redirect&bpo=8844


File: python.info,  Node: 最佳化<10>,  Next: Unicode,  Prev: Multi-threading,  Up: Python 3 2 有什麼新功能

1.12.11 最佳化
--------------

A number of small performance enhancements have been added:

   * Python's peephole optimizer now recognizes patterns such ‘x in {1,
     2, 3}’ as being a test for membership in a set of constants.  The
     optimizer recasts the *note set: 57d. as a *note frozenset: 57e.
     and stores the pre-built constant.

     Now that the speed penalty is gone, it is practical to start
     writing membership tests using set-notation.  This style is both
     semantically clear and operationally fast:

          extension = name.rpartition('.')[2]
          if extension in {'xml', 'html', 'xhtml', 'css'}:
              handle(name)

     (Patch and additional tests contributed by Dave Malcolm;
     bpo-6690(1)).

   * Serializing and unserializing data using the *note pickle: 95.
     module is now several times faster.

     （由 Alexandre Vassalotti、Antoine Pitrou 和 Unladen Swallow 團隊在
     bpo-9410(2) 和 bpo-3873(3) 中貢獻。）

   * The Timsort algorithm(4) used in *note list.sort(): b76. and *note
     sorted(): b75. now runs faster and uses less memory when called
     with a *note key function: dab.  Previously, every element of a
     list was wrapped with a temporary object that remembered the key
     value associated with each element.  Now, two arrays of keys and
     values are sorted in parallel.  This saves the memory consumed by
     the sort wrappers, and it saves time lost to delegating
     comparisons.

     (Patch by Daniel Stutzbach in bpo-9915(5).)

   * JSON decoding performance is improved and memory consumption is
     reduced whenever the same string is repeated for multiple keys.
     Also, JSON encoding now uses the C speedups when the ‘sort_keys’
     argument is true.

     （由 Antoine Pitrou 在 bpo-7451(6) 中貢獻、由 Raymond Hettinger 和
     Antoine Pitrou 在 bpo-10314(7) 中貢獻。）

   * Recursive locks (created with the *note threading.RLock(): 2be.
     API) now benefit from a C implementation which makes them as fast
     as regular locks, and between 10x and 15x faster than their
     previous pure Python implementation.

     （由 Antoine Pitrou 貢獻；bpo-3001(8)。）

   * The fast-search algorithm in stringlib is now used by the *note
     split(): e4c, *note rsplit(): 11ee, *note splitlines(): 11ef. and
     *note replace(): 17e. methods on *note bytes: 1a5, *note bytearray:
     4e3. and *note str: 3f2. objects.  Likewise, the algorithm is also
     used by *note rfind(): e4b, *note rindex(): 11f0, *note rsplit():
     11ee. and *note rpartition(): 11f1.

     (Patch by Florent Xicluna in bpo-7622(9) and bpo-7462(10).)

   * Integer to string conversions now work two "digits" at a time,
     reducing the number of division and modulo operations.

     (bpo-6713(11) by Gawain Bolton, Mark Dickinson, and Victor
     Stinner.)

There were several other minor optimizations.  Set differencing now runs
faster when one operand is much larger than the other (patch by Andress
Bennetts in bpo-8685(12)).  The ‘array.repeat()’ method has a faster
implementation (bpo-1569291(13) by Alexander Belopolsky).  The *note
BaseHTTPRequestHandler: 1065. has more efficient buffering (bpo-3709(14)
by Andrew Schaaf).  The *note operator.attrgetter(): dd9. function has
been sped-up (bpo-10160(15) by Christos Georgiou).  And *note
ConfigParser: 1aa. loads multi-line arguments a bit faster (bpo-7113(16)
by Łukasz Langa).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=6690

   (2) https://bugs.python.org/issue?@action=redirect&bpo=9410

   (3) https://bugs.python.org/issue?@action=redirect&bpo=3873

   (4) https://en.wikipedia.org/wiki/Timsort

   (5) https://bugs.python.org/issue?@action=redirect&bpo=9915

   (6) https://bugs.python.org/issue?@action=redirect&bpo=7451

   (7) https://bugs.python.org/issue?@action=redirect&bpo=10314

   (8) https://bugs.python.org/issue?@action=redirect&bpo=3001

   (9) https://bugs.python.org/issue?@action=redirect&bpo=7622

   (10) https://bugs.python.org/issue?@action=redirect&bpo=7462

   (11) https://bugs.python.org/issue?@action=redirect&bpo=6713

   (12) https://bugs.python.org/issue?@action=redirect&bpo=8685

   (13) https://bugs.python.org/issue?@action=redirect&bpo=1569291

   (14) https://bugs.python.org/issue?@action=redirect&bpo=3709

   (15) https://bugs.python.org/issue?@action=redirect&bpo=10160

   (16) https://bugs.python.org/issue?@action=redirect&bpo=7113


File: python.info,  Node: Unicode,  Next: 編解碼器,  Prev: 最佳化<10>,  Up: Python 3 2 有什麼新功能

1.12.12 Unicode
---------------

Python has been updated to Unicode 6.0.0(1).  The update to the standard
adds over 2,000 new characters including emoji(2) symbols which are
important for mobile phones.

In addition, the updated standard has altered the character properties
for two Kannada characters (U+0CF1, U+0CF2) and one New Tai Lue numeric
character (U+19DA), making the former eligible for use in identifiers
while disqualifying the latter.  For more information, see Unicode
Character Database Changes(3).

   ---------- Footnotes ----------

   (1) https://unicode.org/versions/Unicode6.0.0/

   (2) https://en.wikipedia.org/wiki/Emoji

   (3) https://www.unicode.org/versions/Unicode6.0.0/#Database_Changes


File: python.info,  Node: 編解碼器,  Next: 文件,  Prev: Unicode,  Up: Python 3 2 有什麼新功能

1.12.13 編解碼器
----------------

Support was added for 'cp720' Arabic DOS encoding (bpo-1616979(1)).

MBCS encoding no longer ignores the error handler argument.  In the
default strict mode, it raises an *note UnicodeDecodeError: 9b7. when it
encounters an undecodable byte sequence and an *note UnicodeEncodeError:
61d. for an unencodable character.

The MBCS codec supports ‘'strict'’ and ‘'ignore'’ error handlers for
decoding, and ‘'strict'’ and ‘'replace'’ for encoding.

To emulate Python3.1 MBCS encoding, select the ‘'ignore'’ handler for
decoding and the ‘'replace'’ handler for encoding.

On Mac OS X, Python decodes command line arguments with ‘'utf-8'’ rather
than the locale encoding.

By default, *note tarfile: c8. uses ‘'utf-8'’ encoding on Windows
(instead of ‘'mbcs'’) and the ‘'surrogateescape'’ error handler on all
operating systems.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1616979


File: python.info,  Node: 文件,  Next: IDLE,  Prev: 編解碼器,  Up: Python 3 2 有什麼新功能

1.12.14 文件
------------

The documentation continues to be improved.

   * A table of quick links has been added to the top of lengthy
     sections such as *note 內建函式: 11f5.  In the case of *note
     itertools: 75, the links are accompanied by tables of
     cheatsheet-style summaries to provide an overview and memory jog
     without having to read all of the docs.

   * In some cases, the pure Python source code can be a helpful adjunct
     to the documentation, so now many modules now feature quick links
     to the latest version of the source code.  For example, the *note
     functools: 55. module documentation has a quick link at the top
     labeled:

          'Source code' Lib/functools.py(1).

     (Contributed by Raymond Hettinger; see rationale(2).)

   * The docs now contain more examples and recipes.  In particular,
     *note re: a7. module has an extensive section, *note Regular
     Expression Examples: 11f6.  Likewise, the *note itertools: 75.
     module continues to be updated with new *note Itertools 應用技巧:
     11f7.

   * The *note datetime: 28. module now has an auxiliary implementation
     in pure Python.  No functionality was changed.  This just provides
     an easier-to-read alternate implementation.

     （由 Alexander Belopolsky 在 bpo-9528(3) 中貢獻。）

   * The unmaintained ‘Demo’ directory has been removed.  Some demos
     were integrated into the documentation, some were moved to the
     ‘Tools/demo’ directory, and others were removed altogether.

     （由 Georg Brandl 在 bpo-7962(4) 中貢獻。）

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/functools.py

   (2) 
https://rhettinger.wordpress.com/2011/01/28/open-your-source-more/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=9528

   (4) https://bugs.python.org/issue?@action=redirect&bpo=7962


File: python.info,  Node: IDLE,  Next: Code Repository,  Prev: 文件,  Up: Python 3 2 有什麼新功能

1.12.15 IDLE
------------

   * The format menu now has an option to clean source files by
     stripping trailing whitespace.

     （由 Raymond Hettinger 貢獻；bpo-5150(1)。）

   * IDLE on Mac OS X now works with both Carbon AquaTk and Cocoa
     AquaTk.

     （由 Kevin Walzer、Ned Deily 和 Ronald Oussoren 貢獻；bpo-6075(2)。
     ）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=5150

   (2) https://bugs.python.org/issue?@action=redirect&bpo=6075


File: python.info,  Node: Code Repository,  Next: Build and C API Changes<4>,  Prev: IDLE,  Up: Python 3 2 有什麼新功能

1.12.16 Code Repository
-----------------------

In addition to the existing Subversion code repository at
‘https://svn.python.org’ there is now a Mercurial(1) repository at
‘https://hg.python.org/’.

After the 3.2 release, there are plans to switch to Mercurial as the
primary repository.  This distributed version control system should make
it easier for members of the community to create and share external
changesets.  See PEP 385(2) for details.

To learn to use the new version control system, see the Quick Start(3)
or the Guide to Mercurial Workflows(4).

   ---------- Footnotes ----------

   (1) https://www.mercurial-scm.org/

   (2) https://peps.python.org/pep-0385/

   (3) https://www.mercurial-scm.org/wiki/QuickStart

   (4) https://www.mercurial-scm.org/guide


File: python.info,  Node: Build and C API Changes<4>,  Next: Porting to Python 3 2,  Prev: Code Repository,  Up: Python 3 2 有什麼新功能

1.12.17 Build and C API Changes
-------------------------------

Changes to Python's build process and to the C API include:

   * The 'idle', 'pydoc' and '2to3' scripts are now installed with a
     version-specific suffix on ‘make altinstall’ (bpo-10679(1)).

   * The C functions that access the Unicode Database now accept and
     return characters from the full Unicode range, even on narrow
     unicode builds (Py_UNICODE_TOLOWER, Py_UNICODE_ISDECIMAL, and
     others).  A visible difference in Python is that *note
     unicodedata.numeric(): 11fb. now returns the correct value for
     large code points, and *note repr(): 7a1. may consider more
     characters as printable.

     (Reported by Bupjoe Lee and fixed by Amaury Forgeot D'Arc;
     bpo-5127(2).)

   * Computed gotos are now enabled by default on supported compilers
     (which are detected by the configure script).  They can still be
     disabled selectively by specifying ‘--without-computed-gotos’.

     （由 Antoine Pitrou 貢獻；bpo-9203(3)。）

   * The option ‘--with-wctype-functions’ was removed.  The built-in
     unicode database is now used for all functions.

     （由 Amaury Forgeot D'Arc 貢獻；bpo-9210(4)。）

   * Hash values are now values of a new type, *note Py_hash_t: 11fc,
     which is defined to be the same size as a pointer.  Previously they
     were of type long, which on some 64-bit operating systems is still
     only 32 bits long.  As a result of this fix, *note set: 57d. and
     *note dict: 23b. can now hold more than ‘2**32’ entries on builds
     with 64-bit pointers (previously, they could grow to that size but
     their performance degraded catastrophically).

     （由 Raymond Hettinger 建議並由 Benjamin Peterson 實作；
     bpo-9778(5)。）

   * A new macro ‘Py_VA_COPY’ copies the state of the variable argument
     list.  It is equivalent to C99 'va_copy' but available on all
     Python platforms (bpo-2443(6)).

   * A new C API function ‘PySys_SetArgvEx()’ allows an embedded
     interpreter to set *note sys.argv: 11fd. without also modifying
     *note sys.path: 37f. (bpo-5753(7)).

   * ‘PyEval_CallObject()’ is now only available in macro form.  The
     function declaration, which was kept for backwards compatibility
     reasons, is now removed - the macro was introduced in 1997
     (bpo-8276(8)).

   * There is a new function *note PyLong_AsLongLongAndOverflow(): 11fe.
     which is analogous to *note PyLong_AsLongAndOverflow(): 11ff.  They
     both serve to convert Python *note int: 23c. into a native
     fixed-width type while providing detection of cases where the
     conversion won't fit (bpo-7767(9)).

   * The *note PyUnicode_CompareWithASCIIString(): 1200. function now
     returns 'not equal' if the Python string is 'NUL' terminated.

   * There is a new function *note PyErr_NewExceptionWithDoc(): 1201.
     that is like *note PyErr_NewException(): 1202. but allows a
     docstring to be specified.  This lets C exceptions have the same
     self-documenting capabilities as their pure Python counterparts
     (bpo-7033(10)).

   * When compiled with the ‘--with-valgrind’ option, the pymalloc
     allocator will be automatically disabled when running under
     Valgrind.  This gives improved memory leak detection when running
     under Valgrind, while taking advantage of pymalloc at other times
     (bpo-2422(11)).

   * Removed the ‘O?’ format from the 'PyArg_Parse' functions.  The
     format is no longer used and it had never been documented
     (bpo-8837(12)).

There were a number of other small changes to the C-API. See the
Misc/NEWS(13) file for a complete list.

Also, there were a number of updates to the Mac OS X build, see
Mac/BuildScript/README.txt(14) for details.  For users running a
32/64-bit build, there is a known problem with the default Tcl/Tk on Mac
OS X 10.6.  Accordingly, we recommend installing an updated alternative
such as ActiveState Tcl/Tk 8.5.9(15).  See
‘https://www.python.org/download/mac/tcltk/’ for additional details.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=10679

   (2) https://bugs.python.org/issue?@action=redirect&bpo=5127

   (3) https://bugs.python.org/issue?@action=redirect&bpo=9203

   (4) https://bugs.python.org/issue?@action=redirect&bpo=9210

   (5) https://bugs.python.org/issue?@action=redirect&bpo=9778

   (6) https://bugs.python.org/issue?@action=redirect&bpo=2443

   (7) https://bugs.python.org/issue?@action=redirect&bpo=5753

   (8) https://bugs.python.org/issue?@action=redirect&bpo=8276

   (9) https://bugs.python.org/issue?@action=redirect&bpo=7767

   (10) https://bugs.python.org/issue?@action=redirect&bpo=7033

   (11) https://bugs.python.org/issue?@action=redirect&bpo=2422

   (12) https://bugs.python.org/issue?@action=redirect&bpo=8837

   (13) https://github.com/python/cpython/blob/v3.2.6/Misc/NEWS

   (14) 
https://github.com/python/cpython/blob/v3.2.6/Mac/BuildScript/README.txt

   (15) 
https://web.archive.org/web/20101208191259/https://www.activestate.com/activetcl/downloads


File: python.info,  Node: Porting to Python 3 2,  Prev: Build and C API Changes<4>,  Up: Python 3 2 有什麼新功能

1.12.18 Porting to Python 3.2
-----------------------------

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

   * The *note configparser: 1b. module has a number of clean-ups.  The
     major change is to replace the old ‘ConfigParser’ class with
     long-standing preferred alternative ‘SafeConfigParser’.  In
     addition there are a number of smaller incompatibilities:

        * The interpolation syntax is now validated on *note get():
          1204. and *note set(): 1205. operations.  In the default
          interpolation scheme, only two tokens with percent signs are
          valid: ‘%(name)s’ and ‘%%’, the latter being an escaped
          percent sign.

        * The *note set(): 1205. and *note add_section(): 1206. methods
          now verify that values are actual strings.  Formerly,
          unsupported types could be introduced unintentionally.

        * Duplicate sections or options from a single source now raise
          either *note DuplicateSectionError: 1207. or *note
          DuplicateOptionError: 1208.  Formerly, duplicates would
          silently overwrite a previous entry.

        * Inline comments are now disabled by default so now the ';'
          character can be safely used in values.

        * Comments now can be indented.  Consequently, for ';' or '#' to
          appear at the start of a line in multiline values, it has to
          be interpolated.  This keeps comment prefix characters in
          values from being mistaken as comments.

        * ‘""’ is now a valid value and is no longer automatically
          converted to an empty string.  For empty strings, use ‘"option
          ="’ in a line.

   * The ‘nntplib’ module was reworked extensively, meaning that its
     APIs are often incompatible with the 3.1 APIs.

   * *note bytearray: 4e3. objects can no longer be used as filenames;
     instead, they should be converted to *note bytes: 1a5.

   * The ‘array.tostring()’ and ‘array.fromstring()’ have been renamed
     to *note array.tobytes(): 1209. and *note array.frombytes(): 120a.
     for clarity.  The old names have been deprecated.  (See
     bpo-8990(1).)

   * ‘PyArg_Parse*()’ functions:

        * "t#" format has been removed: use "s#" or "s*" instead

        * "w" and "w#" formats has been removed: use "w*" instead

   * The ‘PyCObject’ type, deprecated in 3.1, has been removed.  To wrap
     opaque C pointers in Python objects, the *note PyCapsule: 120b. API
     should be used instead; the new type has a well-defined interface
     for passing typing safety information and a less complicated
     signature for calling a destructor.

   * The ‘sys.setfilesystemencoding()’ function was removed because it
     had a flawed design.

   * The *note random.seed(): 120c. function and method now salt string
     seeds with an sha512 hash function.  To access the previous version
     of 'seed' in order to reproduce Python 3.1 sequences, set the
     'version' argument to '1', ‘random.seed(s, version=1)’.

   * The previously deprecated ‘string.maketrans()’ function has been
     removed in favor of the static methods *note bytes.maketrans():
     120d. and *note bytearray.maketrans(): 120e.  This change solves
     the confusion around which types were supported by the *note
     string: be. module.  Now, *note str: 3f2, *note bytes: 1a5, and
     *note bytearray: 4e3. each have their own 'maketrans' and
     'translate' methods with intermediate translation tables of the
     appropriate type.

     （由 Georg Brandl 貢獻；bpo-5675(2)。）

   * The previously deprecated ‘contextlib.nested()’ function has been
     removed in favor of a plain *note with: 577. statement which can
     accept multiple context managers.  The latter technique is faster
     (because it is built-in), and it does a better job finalizing
     multiple context managers when one of them raises an exception:

          with open('mylog.txt') as infile, open('a.out', 'w') as outfile:
              for line in infile:
                  if '<critical>' in line:
                      outfile.write(line)

     （由 Georg Brandl 和 Mattias Brändström 貢獻；appspot 問題
     53094(3)。）

   * *note struct.pack(): 120f. now only allows bytes for the ‘s’ string
     pack code.  Formerly, it would accept text arguments and implicitly
     encode them to bytes using UTF-8.  This was problematic because it
     made assumptions about the correct encoding and because a
     variable-length encoding can fail when writing to fixed length
     segment of a structure.

     Code such as ‘struct.pack('<6sHHBBB', 'GIF87a', x, y)’ should be
     rewritten with to use bytes instead of text,
     ‘struct.pack('<6sHHBBB', b'GIF87a', x, y)’.

     (Discovered by David Beazley and fixed by Victor Stinner;
     bpo-10783(4).)

   * The *note xml.etree.ElementTree: 10c. class now raises an *note
     xml.etree.ElementTree.ParseError: 1210. when a parse fails.
     Previously it raised an *note xml.parsers.expat.ExpatError: 1211.

   * The new, longer *note str(): 3f2. value on floats may break
     doctests which rely on the old output format.

   * In *note subprocess.Popen: 17d, the default value for 'close_fds'
     is now ‘True’ under Unix; under Windows, it is ‘True’ if the three
     standard streams are set to ‘None’, ‘False’ otherwise.  Previously,
     'close_fds' was always ‘False’ by default, which produced difficult
     to solve bugs or race conditions when open file descriptors would
     leak into the child process.

   * Support for legacy HTTP 0.9 has been removed from *note
     urllib.request: f4. and *note http.client: 65.  Such support is
     still present on the server side (in *note http.server: 68.).

     （由 Antoine Pitrou 於 bpo-10711(5) 貢獻。）

   * SSL sockets in timeout mode now raise *note socket.timeout: 7d8.
     when a timeout occurs, rather than a generic *note SSLError: 1212.

     （由 Antoine Pitrou 於 bpo-10272(6) 貢獻。）

   * The misleading functions ‘PyEval_AcquireLock()’ and
     ‘PyEval_ReleaseLock()’ have been officially deprecated.  The
     thread-state aware APIs (such as *note PyEval_SaveThread(): 373.
     and *note PyEval_RestoreThread(): 374.) should be used instead.

   * Due to security risks, ‘asyncore.handle_accept()’ has been
     deprecated, and a new function, ‘asyncore.handle_accepted()’, was
     added to replace it.

     （由 Giampaolo Rodola 在 bpo-6706(7) 中貢獻。）

   * Due to the new *note GIL: 13e. implementation,
     ‘PyEval_InitThreads()’ cannot be called before *note
     Py_Initialize(): 851. anymore.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=8990

   (2) https://bugs.python.org/issue?@action=redirect&bpo=5675

   (3) https://codereview.appspot.com/53094

   (4) https://bugs.python.org/issue?@action=redirect&bpo=10783

   (5) https://bugs.python.org/issue?@action=redirect&bpo=10711

   (6) https://bugs.python.org/issue?@action=redirect&bpo=10272

   (7) https://bugs.python.org/issue?@action=redirect&bpo=6706


File: python.info,  Node: Python 3 1 有什麼新功能,  Next: Python 3 0 有什麼新功能,  Prev: Python 3 2 有什麼新功能,  Up: Python 有什麼新功能？

1.13 Python 3.1 有什麼新功能
============================


作者: Raymond Hettinger

This article explains the new features in Python 3.1, compared to 3.0.
Python 3.1 was released on June 27, 2009.

* Menu:

* PEP 372：有序字典::
* PEP 378; Format Specifier for Thousands Separator: PEP 378 Format Specifier for Thousands Separator.
* 其他語言更動: 其他語言更動<12>.
* New, Improved, and Deprecated Modules: New Improved and Deprecated Modules<2>.
* 最佳化: 最佳化<11>.
* IDLE: IDLE<2>.
* Build and C API Changes: Build and C API Changes<5>.
* Porting to Python 3.1: Porting to Python 3 1.


File: python.info,  Node: PEP 372：有序字典,  Next: PEP 378 Format Specifier for Thousands Separator,  Up: Python 3 1 有什麼新功能

'PEP 372'：有序字典

Regular Python dictionaries iterate over key/value pairs in arbitrary
order.  Over the years, a number of authors have written alternative
implementations that remember the order that the keys were originally
inserted.  Based on the experiences from those implementations, a new
*note collections.OrderedDict: 57f. class has been introduced.

The OrderedDict API is substantially the same as regular dictionaries
but will iterate over keys and values in a guaranteed order depending on
when a key was first inserted.  If a new entry overwrites an existing
entry, the original insertion position is left unchanged.  Deleting an
entry and reinserting it will move it to the end.

The standard library now supports use of ordered dictionaries in several
modules.  The *note configparser: 1b. module uses them by default.  This
lets configuration files be read, modified, and then written back in
their original order.  The '_asdict()' method for *note
collections.namedtuple(): 1ae. now returns an ordered dictionary with
the values appearing in the same order as the underlying tuple indices.
The *note json: 76. module is being built-out with an
'object_pairs_hook' to allow OrderedDicts to be built by the decoder.
Support was also added for third-party tools like PyYAML(1).

也參考
......

PEP 372(2) - 有序字典

     PEP written by Armin Ronacher and Raymond Hettinger.
     Implementation written by Raymond Hettinger.

Since an ordered dictionary remembers its insertion order, it can be
used in conjunction with sorting to make a sorted dictionary:

     >>> # regular unsorted dictionary
     >>> d = {'banana': 3, 'apple':4, 'pear': 1, 'orange': 2}

     >>> # dictionary sorted by key
     >>> OrderedDict(sorted(d.items(), key=lambda t: t[0]))
     OrderedDict([('apple', 4), ('banana', 3), ('orange', 2), ('pear', 1)])

     >>> # dictionary sorted by value
     >>> OrderedDict(sorted(d.items(), key=lambda t: t[1]))
     OrderedDict([('pear', 1), ('orange', 2), ('banana', 3), ('apple', 4)])

     >>> # dictionary sorted by length of the key string
     >>> OrderedDict(sorted(d.items(), key=lambda t: len(t[0])))
     OrderedDict([('pear', 1), ('apple', 4), ('orange', 2), ('banana', 3)])

The new sorted dictionaries maintain their sort order when entries are
deleted.  But when new keys are added, the keys are appended to the end
and the sort is not maintained.

   ---------- Footnotes ----------

   (1) https://pyyaml.org/

   (2) https://peps.python.org/pep-0372/


File: python.info,  Node: PEP 378 Format Specifier for Thousands Separator,  Next: 其他語言更動<12>,  Prev: PEP 372：有序字典,  Up: Python 3 1 有什麼新功能

1.13.2 PEP 378: Format Specifier for Thousands Separator
--------------------------------------------------------

The built-in *note format(): 5c3. function and the *note str.format():
5c7. method use a mini-language that now includes a simple, non-locale
aware way to format a number with a thousands separator.  That provides
a way to humanize a program's output, improving its professional
appearance and readability:

     >>> format(1234567, ',d')
     '1,234,567'
     >>> format(1234567.89, ',.2f')
     '1,234,567.89'
     >>> format(12345.6 + 8901234.12j, ',f')
     '12,345.600000+8,901,234.120000j'
     >>> format(Decimal('1234567.89'), ',f')
     '1,234,567.89'

The supported types are *note int: 23c, *note float: 2c8, *note complex:
2c9. and *note decimal.Decimal: 27c.

Discussions are underway about how to specify alternative separators
like dots, spaces, apostrophes, or underscores.  Locale-aware
applications should use the existing 'n' format specifier which already
has some support for thousands separators.

也參考
......

PEP 378(1) - Format Specifier for Thousands Separator

     PEP written by Raymond Hettinger and implemented by Eric Smith and
     Mark Dickinson.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0378/


File: python.info,  Node: 其他語言更動<12>,  Next: New Improved and Deprecated Modules<2>,  Prev: PEP 378 Format Specifier for Thousands Separator,  Up: Python 3 1 有什麼新功能

1.13.3 其他語言更動
-------------------

Some smaller changes made to the core Python language are:

   * Directories and zip archives containing a ‘__main__.py’ file can
     now be executed directly by passing their name to the interpreter.
     The directory/zipfile is automatically inserted as the first entry
     in sys.path.  (Suggestion and initial patch by Andy Chu; revised
     patch by Phillip J. Eby and Nick Coghlan; bpo-1739468(1).)

   * The *note int(): 23c. type gained a ‘bit_length’ method that
     returns the number of bits necessary to represent its argument in
     binary:

          >>> n = 37
          >>> bin(37)
          '0b100101'
          >>> n.bit_length()
          6
          >>> n = 2**123-1
          >>> n.bit_length()
          123
          >>> (n+1).bit_length()
          124

     （由 Fredrik Johansson、Victor Stinner、Raymond Hettinger 和 Mark
     Dickinson 貢獻；bpo-3439(2)。）

   * The fields in *note format(): 5c3. strings can now be automatically
     numbered:

          >>> 'Sir {} of {}'.format('Gallahad', 'Camelot')
          'Sir Gallahad of Camelot'

     Formerly, the string would have required numbered fields such as:
     ‘'Sir {0} of {1}'’.

     （由 Eric Smith 貢獻；bpo-5237(3)。）

   * The ‘string.maketrans()’ function is deprecated and is replaced by
     new static methods, *note bytes.maketrans(): 120d. and *note
     bytearray.maketrans(): 120e.  This change solves the confusion
     around which types were supported by the *note string: be. module.
     Now, *note str: 3f2, *note bytes: 1a5, and *note bytearray: 4e3.
     each have their own 'maketrans' and 'translate' methods with
     intermediate translation tables of the appropriate type.

     （由 Georg Brandl 貢獻；bpo-5675(4)。）

   * The syntax of the *note with: 577. statement now allows multiple
     context managers in a single statement:

          >>> with open('mylog.txt') as infile, open('a.out', 'w') as outfile:
          ...     for line in infile:
          ...         if '<critical>' in line:
          ...             outfile.write(line)

     With the new syntax, the ‘contextlib.nested()’ function is no
     longer needed and is now deprecated.

     （由 Georg Brandl 和 Mattias Brändström 貢獻；appspot 問題
     53094(5)。）

   * ‘round(x, n)’ now returns an integer if 'x' is an integer.
     Previously it returned a float:

          >>> round(1123, -2)
          1100

     （由 Mark Dickinson 貢獻；bpo-4707(6)。）

   * Python now uses David Gay's algorithm for finding the shortest
     floating-point representation that doesn't change its value.  This
     should help mitigate some of the confusion surrounding binary
     floating-point numbers.

     The significance is easily seen with a number like ‘1.1’ which does
     not have an exact equivalent in binary floating point.  Since there
     is no exact equivalent, an expression like ‘float('1.1')’ evaluates
     to the nearest representable value which is ‘0x1.199999999999ap+0’
     in hex or ‘1.100000000000000088817841970012523233890533447265625’
     in decimal.  That nearest value was and still is used in subsequent
     floating-point calculations.

     What is new is how the number gets displayed.  Formerly, Python
     used a simple approach.  The value of ‘repr(1.1)’ was computed as
     ‘format(1.1, '.17g')’ which evaluated to ‘'1.1000000000000001'’.
     The advantage of using 17 digits was that it relied on IEEE-754
     guarantees to assure that ‘eval(repr(1.1))’ would round-trip
     exactly to its original value.  The disadvantage is that many
     people found the output to be confusing (mistaking intrinsic
     limitations of binary floating-point representation as being a
     problem with Python itself).

     The new algorithm for ‘repr(1.1)’ is smarter and returns ‘'1.1'’.
     Effectively, it searches all equivalent string representations
     (ones that get stored with the same underlying float value) and
     returns the shortest representation.

     The new algorithm tends to emit cleaner representations when
     possible, but it does not change the underlying values.  So, it is
     still the case that ‘1.1 + 2.2 != 3.3’ even though the
     representations may suggest otherwise.

     The new algorithm depends on certain features in the underlying
     floating-point implementation.  If the required features are not
     found, the old algorithm will continue to be used.  Also, the text
     pickle protocols assure cross-platform portability by using the old
     algorithm.

     （由 Eric Smith 和 Mark Dickinson 貢獻；bpo-1580(7)）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1739468

   (2) https://bugs.python.org/issue?@action=redirect&bpo=3439

   (3) https://bugs.python.org/issue?@action=redirect&bpo=5237

   (4) https://bugs.python.org/issue?@action=redirect&bpo=5675

   (5) https://codereview.appspot.com/53094

   (6) https://bugs.python.org/issue?@action=redirect&bpo=4707

   (7) https://bugs.python.org/issue?@action=redirect&bpo=1580


File: python.info,  Node: New Improved and Deprecated Modules<2>,  Next: 最佳化<11>,  Prev: 其他語言更動<12>,  Up: Python 3 1 有什麼新功能

1.13.4 New, Improved, and Deprecated Modules
--------------------------------------------

   * Added a *note collections.Counter: 1033. class to support
     convenient counting of unique items in a sequence or iterable:

          >>> Counter(['red', 'blue', 'red', 'green', 'blue', 'blue'])
          Counter({'blue': 3, 'red': 2, 'green': 1})

     （由 Raymond Hettinger 貢獻；bpo-1696199(1)。）

   * Added a new module, *note tkinter.ttk: e2. for access to the Tk
     themed widget set.  The basic idea of ttk is to separate, to the
     extent possible, the code implementing a widget's behavior from the
     code implementing its appearance.

     （由 Guilherme Polo 貢獻；bpo-2983(2)。）

   * The *note gzip.GzipFile: 354. and *note bz2.BZ2File: 80b. classes
     now support the context management protocol:

          >>> # Automatically close file after writing
          >>> with gzip.GzipFile(filename, "wb") as f:
          ...     f.write(b"xxx")

     （由 Antoine Pitrou 貢獻。）

   * The *note decimal: 2e. module now supports methods for creating a
     decimal object from a binary *note float: 2c8.  The conversion is
     exact but can sometimes be surprising:

          >>> Decimal.from_float(1.1)
          Decimal('1.100000000000000088817841970012523233890533447265625')

     The long decimal result shows the actual binary fraction being
     stored for '1.1'.  The fraction has many digits because '1.1'
     cannot be exactly represented in binary.

     （由 Raymond Hettinger 和 Mark Dickinso 貢獻。）

   * The *note itertools: 75. module grew two new functions.  The *note
     itertools.combinations_with_replacement(): 1219. function is one of
     four for generating combinatorics including permutations and
     Cartesian products.  The *note itertools.compress(): 121a. function
     mimics its namesake from APL. Also, the existing *note
     itertools.count(): 121b. function now has an optional 'step'
     argument and can accept any type of counting sequence including
     *note fractions.Fraction: 1c7. and *note decimal.Decimal: 27c.:

          >>> [p+q for p,q in combinations_with_replacement('LOVE', 2)]
          ['LL', 'LO', 'LV', 'LE', 'OO', 'OV', 'OE', 'VV', 'VE', 'EE']

          >>> list(compress(data=range(10), selectors=[0,0,1,1,0,1,0,1,0,0]))
          [2, 3, 5, 7]

          >>> c = count(start=Fraction(1,2), step=Fraction(1,6))
          >>> [next(c), next(c), next(c), next(c)]
          [Fraction(1, 2), Fraction(2, 3), Fraction(5, 6), Fraction(1, 1)]

     （由 Raymond Hettinger 貢獻。）

   * *note collections.namedtuple(): 1ae. now supports a keyword
     argument 'rename' which lets invalid fieldnames be automatically
     converted to positional names in the form _0, _1, etc.  This is
     useful when the field names are being created by an external source
     such as a CSV header, SQL field list, or user input:

          >>> query = input()
          SELECT region, dept, count(*) FROM main GROUPBY region, dept

          >>> cursor.execute(query)
          >>> query_fields = [desc[0] for desc in cursor.description]
          >>> UserQuery = namedtuple('UserQuery', query_fields, rename=True)
          >>> pprint.pprint([UserQuery(*row) for row in cursor])
          [UserQuery(region='South', dept='Shipping', _2=185),
           UserQuery(region='North', dept='Accounting', _2=37),
           UserQuery(region='West', dept='Sales', _2=419)]

     （由 Raymond Hettinger 貢獻；bpo-1818(3)。）

   * The *note re.sub(): 283, *note re.subn(): 284. and *note
     re.split(): 282. functions now accept a flags parameter.

     （由 Gregory Smith 貢獻。）

   * The *note logging: 7b. module now implements a simple *note
     logging.NullHandler: 121c. class for applications that are not
     using logging but are calling library code that does.  Setting-up a
     null handler will suppress spurious warnings such as "No handlers
     could be found for logger foo":

          >>> h = logging.NullHandler()
          >>> logging.getLogger("foo").addHandler(h)

     （由 Vinay Sajip 貢獻；bpo-4384(4)）。

   * The *note runpy: ac. module which supports the ‘-m’ command line
     switch now supports the execution of packages by looking for and
     executing a ‘__main__’ submodule when a package name is supplied.

     （由 Andi Vajda 貢獻；bpo-4195(5)。）

   * The *note pdb: 94. module can now access and display source code
     loaded via *note zipimport: 118. (or any other conformant PEP
     302(6) loader).

     （由 Alexander Belopolsky 貢獻；bpo-4201(7)。）

   * *note functools.partial: 356. objects can now be pickled.

     (Suggested by Antoine Pitrou and Jesse Noller.  Implemented by Jack
     Diederich; bpo-5228(8).)

   * Add *note pydoc: a3. help topics for symbols so that ‘help('@')’
     works as expected in the interactive environment.

     （由 David Laban 貢獻；bpo-4739(9)。）

   * The *note unittest: ef. module now supports skipping individual
     tests or classes of tests.  And it supports marking a test as an
     expected failure, a test that is known to be broken, but shouldn't
     be counted as a failure on a TestResult:

          class TestGizmo(unittest.TestCase):

              @unittest.skipUnless(sys.platform.startswith("win"), "requires Windows")
              def test_gizmo_on_windows(self):
                  ...

              @unittest.expectedFailure
              def test_gimzo_without_required_library(self):
                  ...

     Also, tests for exceptions have been builtout to work with context
     managers using the *note with: 577. statement:

          def test_division_by_zero(self):
              with self.assertRaises(ZeroDivisionError):
                  x / 0

     In addition, several new assertion methods were added including
     *note assertSetEqual(): 121d, *note assertDictEqual(): 121e,
     ‘assertDictContainsSubset()’, *note assertListEqual(): 121f, *note
     assertTupleEqual(): 1220, *note assertSequenceEqual(): 1221, *note
     assertRaisesRegexp(): 4d3, *note assertIsNone(): 1222, and *note
     assertIsNotNone(): 1223.

     （由 Benjamin Peterson 和 Antoine Pitrou 貢獻。）

   * The *note io: 73. module has three new constants for the *note
     seek(): 1224. method: *note SEEK_SET: 1225, *note SEEK_CUR: 1226,
     and *note SEEK_END: 1227.

   * The *note sys.version_info: 645. tuple is now a named tuple:

          >>> sys.version_info
          sys.version_info(major=3, minor=1, micro=0, releaselevel='alpha', serial=2)

     （由 Ross Light 貢獻；bpo-4285(10)。）

   * The ‘nntplib’ and *note imaplib: 6a. modules now support IPv6.

     （由 Derek Morr 貢獻；bpo-1655(11) 和 bpo-1664(12)。）

   * The *note pickle: 95. module has been adapted for better
     interoperability with Python 2.x when used with protocol 2 or
     lower.  The reorganization of the standard library changed the
     formal reference for many objects.  For example, ‘__builtin__.set’
     in Python 2 is called ‘builtins.set’ in Python 3.  This change
     confounded efforts to share data between different versions of
     Python.  But now when protocol 2 or lower is selected, the pickler
     will automatically use the old Python 2 names for both loading and
     dumping.  This remapping is turned-on by default but can be
     disabled with the 'fix_imports' option:

          >>> s = {1, 2, 3}
          >>> pickle.dumps(s, protocol=0)
          b'c__builtin__\nset\np0\n((lp1\nL1L\naL2L\naL3L\natp2\nRp3\n.'
          >>> pickle.dumps(s, protocol=0, fix_imports=False)
          b'cbuiltins\nset\np0\n((lp1\nL1L\naL2L\naL3L\natp2\nRp3\n.'

     An unfortunate but unavoidable side-effect of this change is that
     protocol 2 pickles produced by Python 3.1 won't be readable with
     Python 3.0.  The latest pickle protocol, protocol 3, should be used
     when migrating data between Python 3.x implementations, as it
     doesn't attempt to remain compatible with Python 2.x.

     （由 Alexandre Vassalotti 和 Antoine Pitrou 貢獻，bpo-6137(13)。）

   * A new module, *note importlib: 6b. was added.  It provides a
     complete, portable, pure Python reference implementation of the
     *note import: 586. statement and its counterpart, the *note
     __import__(): 879. function.  It represents a substantial step
     forward in documenting and defining the actions that take place
     during imports.

     （由 Brett Cannon 貢獻。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1696199

   (2) https://bugs.python.org/issue?@action=redirect&bpo=2983

   (3) https://bugs.python.org/issue?@action=redirect&bpo=1818

   (4) https://bugs.python.org/issue?@action=redirect&bpo=4384

   (5) https://bugs.python.org/issue?@action=redirect&bpo=4195

   (6) https://peps.python.org/pep-0302/

   (7) https://bugs.python.org/issue?@action=redirect&bpo=4201

   (8) https://bugs.python.org/issue?@action=redirect&bpo=5228

   (9) https://bugs.python.org/issue?@action=redirect&bpo=4739

   (10) https://bugs.python.org/issue?@action=redirect&bpo=4285

   (11) https://bugs.python.org/issue?@action=redirect&bpo=1655

   (12) https://bugs.python.org/issue?@action=redirect&bpo=1664

   (13) https://bugs.python.org/issue?@action=redirect&bpo=6137


File: python.info,  Node: 最佳化<11>,  Next: IDLE<2>,  Prev: New Improved and Deprecated Modules<2>,  Up: Python 3 1 有什麼新功能

1.13.5 最佳化
-------------

Major performance enhancements have been added:

   * The new I/O library (as defined in PEP 3116(1)) was mostly written
     in Python and quickly proved to be a problematic bottleneck in
     Python 3.0.  In Python 3.1, the I/O library has been entirely
     rewritten in C and is 2 to 20 times faster depending on the task at
     hand.  The pure Python version is still available for
     experimentation purposes through the ‘_pyio’ module.

     （由 Amaury Forgeot d'Arc 和 Antoine Pitrou 貢獻。）

   * Added a heuristic so that tuples and dicts containing only
     untrackable objects are not tracked by the garbage collector.  This
     can reduce the size of collections and therefore the garbage
     collection overhead on long-running programs, depending on their
     particular use of datatypes.

     （由 Antoine Pitrou 貢獻，bpo-4688(2)。）

   * Enabling a configure option named ‘--with-computed-gotos’ on
     compilers that support it (notably: gcc, SunPro, icc), the bytecode
     evaluation loop is compiled with a new dispatch mechanism which
     gives speedups of up to 20%, depending on the system, the compiler,
     and the benchmark.

     （由 Antoine Pitrou 和其他一些參與者共同貢獻，bpo-4753(3)）。

   * The decoding of UTF-8, UTF-16 and LATIN-1 is now two to four times
     faster.

     （由 Antoine Pitrou 和 Amaury Forgeot d'Arc 貢獻，bpo-4868(4)。）

   * The *note json: 76. module now has a C extension to substantially
     improve its performance.  In addition, the API was modified so that
     json works only with *note str: 3f2, not with *note bytes: 1a5.
     That change makes the module closely match the JSON
     specification(5) which is defined in terms of Unicode.

     （由 Bob Ippolito 貢獻，由 Antoine Pitrou 和 Benjamin Peterson 轉換
     為 Py3.1；bpo-4136(6)。）

   * Unpickling now interns the attribute names of pickled objects.
     This saves memory and allows pickles to be smaller.

     （由 Jake McGuire 和 Antoine Pitrou 貢獻；bpo-5084(7)。）

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3116/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=4688

   (3) https://bugs.python.org/issue?@action=redirect&bpo=4753

   (4) https://bugs.python.org/issue?@action=redirect&bpo=4868

   (5) https://json.org/

   (6) https://bugs.python.org/issue?@action=redirect&bpo=4136

   (7) https://bugs.python.org/issue?@action=redirect&bpo=5084


File: python.info,  Node: IDLE<2>,  Next: Build and C API Changes<5>,  Prev: 最佳化<11>,  Up: Python 3 1 有什麼新功能

1.13.6 IDLE
-----------

   * IDLE's format menu now provides an option to strip trailing
     whitespace from a source file.

     （由 Roger D. Serwy 貢獻；bpo-5150(1)。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=5150


File: python.info,  Node: Build and C API Changes<5>,  Next: Porting to Python 3 1,  Prev: IDLE<2>,  Up: Python 3 1 有什麼新功能

1.13.7 Build and C API Changes
------------------------------

Changes to Python's build process and to the C API include:

   * Integers are now stored internally either in base ‘2**15’ or in
     base ‘2**30’, the base being determined at build time.  Previously,
     they were always stored in base ‘2**15’.  Using base ‘2**30’ gives
     significant performance improvements on 64-bit machines, but
     benchmark results on 32-bit machines have been mixed.  Therefore,
     the default is to use base ‘2**30’ on 64-bit machines and base
     ‘2**15’ on 32-bit machines; on Unix, there's a new configure option
     ‘--enable-big-digits’ that can be used to override this default.

     Apart from the performance improvements this change should be
     invisible to end users, with one exception: for testing and
     debugging purposes there's a new *note sys.int_info: 122b. that
     provides information about the internal format, giving the number
     of bits per digit and the size in bytes of the C type used to store
     each digit:

          >>> import sys
          >>> sys.int_info
          sys.int_info(bits_per_digit=30, sizeof_digit=4)

     （由 Mark Dickinson 貢獻；bpo-4258(1)。）

   * The *note PyLong_AsUnsignedLongLong(): 122c. function now handles a
     negative 'pylong' by raising *note OverflowError: 825. instead of
     *note TypeError: 4dd.

     （由 Mark Dickinson 和 Lisandro Dalcrin 貢獻；bpo-5175(2)。）

   * Deprecated ‘PyNumber_Int()’.  Use *note PyNumber_Long(): a0a.
     instead.

     （由 Mark Dickinson 貢獻；bpo-4910(3)。）

   * Added a new *note PyOS_string_to_double(): 122d. function to
     replace the deprecated functions ‘PyOS_ascii_strtod()’ and
     ‘PyOS_ascii_atof()’.

     （由 Mark Dickinson 貢獻；bpo-5914(4)。）

   * Added *note PyCapsule: 120b. as a replacement for the ‘PyCObject’
     API. The principal difference is that the new type has a well
     defined interface for passing typing safety information and a less
     complicated signature for calling a destructor.  The old type had a
     problematic API and is now deprecated.

     （由 Larry Hastings 貢獻；bpo-5630(5)。）

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=4258

   (2) https://bugs.python.org/issue?@action=redirect&bpo=5175

   (3) https://bugs.python.org/issue?@action=redirect&bpo=4910

   (4) https://bugs.python.org/issue?@action=redirect&bpo=5914

   (5) https://bugs.python.org/issue?@action=redirect&bpo=5630


File: python.info,  Node: Porting to Python 3 1,  Prev: Build and C API Changes<5>,  Up: Python 3 1 有什麼新功能

1.13.8 Porting to Python 3.1
----------------------------

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

   * The new floating-point string representations can break existing
     doctests.  For example:

          def e():
              '''Compute the base of natural logarithms.

              >>> e()
              2.7182818284590451

              '''
              return sum(1/math.factorial(x) for x in reversed(range(30)))

          doctest.testmod()

          **********************************************************************
          Failed example:
              e()
          Expected:
              2.7182818284590451
          Got:
              2.718281828459045
          **********************************************************************

   * The automatic name remapping in the pickle module for protocol 2 or
     lower can make Python 3.1 pickles unreadable in Python 3.0.  One
     solution is to use protocol 3.  Another solution is to set the
     'fix_imports' option to ‘False’.  See the discussion above for more
     details.


File: python.info,  Node: Python 3 0 有什麼新功能,  Next: Python 2 7 有什麼新功能,  Prev: Python 3 1 有什麼新功能,  Up: Python 有什麼新功能？

1.14 Python 3.0 有什麼新功能
============================


作者: Guido van Rossum

This article explains the new features in Python 3.0, compared to 2.6.
Python 3.0, also known as "Python 3000" or "Py3K", is the first ever
'intentionally backwards incompatible' Python release.  Python 3.0 was
released on December 3, 2008.  There are more changes than in a typical
release, and more that are important for all Python users.
Nevertheless, after digesting the changes, you'll find that Python
really hasn't changed all that much - by and large, we're mostly fixing
well-known annoyances and warts, and removing a lot of old cruft.

This article doesn't attempt to provide a complete specification of all
new features, but instead tries to give a convenient overview.  For full
details, you should refer to the documentation for Python 3.0, and/or
the many PEPs referenced in the text.  If you want to understand the
complete implementation and design rationale for a particular feature,
PEPs usually have more details than the regular documentation; but note
that PEPs usually are not kept up-to-date once a feature has been fully
implemented.

Due to time constraints this document is not as complete as it should
have been.  As always for a new release, the ‘Misc/NEWS’ file in the
source distribution contains a wealth of detailed information about
every small thing that was changed.

* Menu:

* Common Stumbling Blocks::
* 語法變更概要::
* Changes Already Present In Python 2.6: Changes Already Present In Python 2 6.
* 函式庫變更::
* PEP 3101; A New Approach To String Formatting: PEP 3101 A New Approach To String Formatting.
* Changes To Exceptions::
* Miscellaneous Other Changes::
* Build and C API Changes: Build and C API Changes<6>.
* Performance::
* Porting To Python 3.0: Porting To Python 3 0.


File: python.info,  Node: Common Stumbling Blocks,  Next: 語法變更概要,  Up: Python 3 0 有什麼新功能

1.14.1 Common Stumbling Blocks
------------------------------

This section lists those few changes that are most likely to trip you up
if you're used to Python 2.5.

* Menu:

* Print Is A Function::
* Views And Iterators Instead Of Lists::
* Ordering Comparisons::
* 整數::
* Text Vs. Data Instead Of Unicode Vs. 8-bit: Text Vs Data Instead Of Unicode Vs 8-bit.


File: python.info,  Node: Print Is A Function,  Next: Views And Iterators Instead Of Lists,  Up: Common Stumbling Blocks

1.14.1.1 Print Is A Function
............................

The ‘print’ statement has been replaced with a *note print(): f18.
function, with keyword arguments to replace most of the special syntax
of the old ‘print’ statement ( PEP 3105(1)).  Examples:

     Old: print "The answer is", 2*2
     New: print("The answer is", 2*2)

     Old: print x,           # Trailing comma suppresses newline
     New: print(x, end=" ")  # Appends a space instead of a newline

     Old: print              # Prints a newline
     New: print()            # You must call the function!

     Old: print >>sys.stderr, "fatal error"
     New: print("fatal error", file=sys.stderr)

     Old: print (x, y)       # prints repr((x, y))
     New: print((x, y))      # Not the same as print(x, y)!

You can also customize the separator between items, e.g.:

     print("There are <", 2**32, "> possibilities!", sep="")

which produces:

     There are <4294967296> possibilities!

Note:

   * The *note print(): f18. function doesn't support the "softspace"
     feature of the old ‘print’ statement.  For example, in Python 2.x,
     ‘print "A\n", "B"’ would write ‘"A\nB\n"’; but in Python 3.0,
     ‘print("A\n", "B")’ writes ‘"A\n B\n"’.

   * Initially, you'll be finding yourself typing the old ‘print x’ a
     lot in interactive mode.  Time to retrain your fingers to type
     ‘print(x)’ instead!

   * When using the ‘2to3’ source-to-source conversion tool, all ‘print’
     statements are automatically converted to *note print(): f18.
     function calls, so this is mostly a non-issue for larger projects.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3105/


File: python.info,  Node: Views And Iterators Instead Of Lists,  Next: Ordering Comparisons,  Prev: Print Is A Function,  Up: Common Stumbling Blocks

1.14.1.2 Views And Iterators Instead Of Lists
.............................................

Some well-known APIs no longer return lists:

   * *note dict: 23b. methods *note dict.keys(): 771, *note
     dict.items(): 773. and *note dict.values(): 772. return "views"
     instead of lists.  For example, this no longer works: ‘k =
     d.keys(); k.sort()’.  Use ‘k = sorted(d)’ instead (this works in
     Python 2.5 too and is just as efficient).

   * Also, the ‘dict.iterkeys()’, ‘dict.iteritems()’ and
     ‘dict.itervalues()’ methods are no longer supported.

   * *note map(): 808. and *note filter(): 809. return iterators.  If
     you really need a list and the input sequences are all of equal
     length, a quick fix is to wrap *note map(): 808. in *note list():
     5b6, e.g.  ‘list(map(...))’, but a better fix is often to use a
     list comprehension (especially when the original code uses *note
     lambda: 1234.), or rewriting the code so it doesn't need a list at
     all.  Particularly tricky is *note map(): 808. invoked for the side
     effects of the function; the correct transformation is to use a
     regular *note for: 2c3. loop (since creating a list would just be
     wasteful).

     If the input sequences are not of equal length, *note map(): 808.
     will stop at the termination of the shortest of the sequences.  For
     full compatibility with *note map(): 808. from Python 2.x, also
     wrap the sequences in *note itertools.zip_longest(): 1235, e.g.
     ‘map(func, *sequences)’ becomes ‘list(map(func,
     itertools.zip_longest(*sequences)))’.

   * *note range(): 8e7. now behaves like ‘xrange()’ used to behave,
     except it works with values of arbitrary size.  The latter no
     longer exists.

   * *note zip(): 774. now returns an iterator.


File: python.info,  Node: Ordering Comparisons,  Next: 整數,  Prev: Views And Iterators Instead Of Lists,  Up: Common Stumbling Blocks

1.14.1.3 Ordering Comparisons
.............................

Python 3.0 has simplified the rules for ordering comparisons:

   * The ordering comparison operators (‘<’, ‘<=’, ‘>=’, ‘>’) raise a
     TypeError exception when the operands don't have a meaningful
     natural ordering.  Thus, expressions like ‘1 < ''’, ‘0 > None’ or
     ‘len <= len’ are no longer valid, and e.g.  ‘None < None’ raises
     *note TypeError: 4dd. instead of returning ‘False’.  A corollary is
     that sorting a heterogeneous list no longer makes sense - all the
     elements must be comparable to each other.  Note that this does not
     apply to the ‘==’ and ‘!=’ operators: objects of different
     incomparable types always compare unequal to each other.

   * ‘builtin.sorted()’ and *note list.sort(): b76. no longer accept the
     'cmp' argument providing a comparison function.  Use the 'key'
     argument instead.  N.B. the 'key' and 'reverse' arguments are now
     "keyword-only".

   * The ‘cmp()’ function should be treated as gone, and the ‘__cmp__()’
     special method is no longer supported.  Use ‘__lt__()’ for sorting,
     ‘__eq__()’ with ‘__hash__()’, and other rich comparisons as needed.
     (If you really need the ‘cmp()’ functionality, you could use the
     expression ‘(a > b) - (a < b)’ as the equivalent for ‘cmp(a, b)’.)


File: python.info,  Node: 整數,  Next: Text Vs Data Instead Of Unicode Vs 8-bit,  Prev: Ordering Comparisons,  Up: Common Stumbling Blocks

1.14.1.4 整數
.............

   * PEP 237(1): Essentially, ‘long’ renamed to *note int: 23c.  That
     is, there is only one built-in integral type, named *note int:
     23c.; but it behaves mostly like the old ‘long’ type.

   * PEP 238(2): An expression like ‘1/2’ returns a float.  Use ‘1//2’
     to get the truncating behavior.  (The latter syntax has existed for
     years, at least since Python 2.2.)

   * The ‘sys.maxint’ constant was removed, since there is no longer a
     limit to the value of integers.  However, *note sys.maxsize: 115d.
     can be used as an integer larger than any practical list or string
     index.  It conforms to the implementation's "natural" integer size
     and is typically the same as ‘sys.maxint’ in previous releases on
     the same platform (assuming the same build options).

   * The *note repr(): 7a1. of a long integer doesn't include the
     trailing ‘L’ anymore, so code that unconditionally strips that
     character will chop off the last digit instead.  (Use *note str():
     3f2. instead.)

   * Octal literals are no longer of the form ‘0720’; use ‘0o720’
     instead.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0237/

   (2) https://peps.python.org/pep-0238/


File: python.info,  Node: Text Vs Data Instead Of Unicode Vs 8-bit,  Prev: 整數,  Up: Common Stumbling Blocks

1.14.1.5 Text Vs. Data Instead Of Unicode Vs. 8-bit
...................................................

Everything you thought you knew about binary data and Unicode has
changed.

   * Python 3.0 uses the concepts of 'text' and (binary) 'data' instead
     of Unicode strings and 8-bit strings.  All text is Unicode; however
     'encoded' Unicode is represented as binary data.  The type used to
     hold text is *note str: 3f2, the type used to hold data is *note
     bytes: 1a5.  The biggest difference with the 2.x situation is that
     any attempt to mix text and data in Python 3.0 raises *note
     TypeError: 4dd, whereas if you were to mix Unicode and 8-bit
     strings in Python 2.x, it would work if the 8-bit string happened
     to contain only 7-bit (ASCII) bytes, but you would get *note
     UnicodeDecodeError: 9b7. if it contained non-ASCII values.  This
     value-specific behavior has caused numerous sad faces over the
     years.

   * As a consequence of this change in philosophy, pretty much all code
     that uses Unicode, encodings or binary data most likely has to
     change.  The change is for the better, as in the 2.x world there
     were numerous bugs having to do with mixing encoded and unencoded
     text.  To be prepared in Python 2.x, start using ‘unicode’ for all
     unencoded text, and *note str: 3f2. for binary or encoded data
     only.  Then the ‘2to3’ tool will do most of the work for you.

   * You can no longer use ‘u"..."’ literals for Unicode text.  However,
     you must use ‘b"..."’ literals for binary data.

   * As the *note str: 3f2. and *note bytes: 1a5. types cannot be mixed,
     you must always explicitly convert between them.  Use *note
     str.encode(): 87a. to go from *note str: 3f2. to *note bytes: 1a5,
     and *note bytes.decode(): 87b. to go from *note bytes: 1a5. to
     *note str: 3f2.  You can also use ‘bytes(s, encoding=...)’ and
     ‘str(b, encoding=...)’, respectively.

   * Like *note str: 3f2, the *note bytes: 1a5. type is immutable.
     There is a separate 'mutable' type to hold buffered binary data,
     *note bytearray: 4e3.  Nearly all APIs that accept *note bytes:
     1a5. also accept *note bytearray: 4e3.  The mutable API is based on
     ‘collections.MutableSequence’.

   * All backslashes in raw string literals are interpreted literally.
     This means that ‘'\U'’ and ‘'\u'’ escapes in raw strings are not
     treated specially.  For example, ‘r'\u20ac'’ is a string of 6
     characters in Python 3.0, whereas in 2.6, ‘ur'\u20ac'’ was the
     single "euro" character.  (Of course, this change only affects raw
     string literals; the euro character is ‘'\u20ac'’ in Python 3.0.)

   * The built-in ‘basestring’ abstract type was removed.  Use *note
     str: 3f2. instead.  The *note str: 3f2. and *note bytes: 1a5. types
     don't have functionality enough in common to warrant a shared base
     class.  The ‘2to3’ tool (see below) replaces every occurrence of
     ‘basestring’ with *note str: 3f2.

   * Files opened as text files (still the default mode for *note
     open(): 4c0.) always use an encoding to map between strings (in
     memory) and bytes (on disk).  Binary files (opened with a ‘b’ in
     the mode argument) always use bytes in memory.  This means that if
     a file is opened using an incorrect mode or encoding, I/O will
     likely fail loudly, instead of silently producing incorrect data.
     It also means that even Unix users will have to specify the correct
     mode (text or binary) when opening a file.  There is a
     platform-dependent default encoding, which on Unixy platforms can
     be set with the ‘LANG’ environment variable (and sometimes also
     with some other platform-specific locale-related environment
     variables).  In many cases, but not all, the system default is
     UTF-8; you should never count on this default.  Any application
     reading or writing more than pure ASCII text should probably have a
     way to override the encoding.  There is no longer any need for
     using the encoding-aware streams in the *note codecs: 14. module.

   * The initial values of *note sys.stdin: 4e2, *note sys.stdout: a79.
     and *note sys.stderr: 8dd. are now unicode-only text files (i.e.,
     they are instances of *note io.TextIOBase: 63b.).  To read and
     write bytes data with these streams, you need to use their *note
     io.TextIOBase.buffer: 1239. attribute.

   * Filenames are passed to and returned from APIs as (Unicode)
     strings.  This can present platform-specific problems because on
     some platforms filenames are arbitrary byte strings.  (On the other
     hand, on Windows filenames are natively stored as Unicode.)  As a
     work-around, most APIs (e.g.  *note open(): 4c0. and many functions
     in the *note os: 91. module) that take filenames accept *note
     bytes: 1a5. objects as well as strings, and a few APIs have a way
     to ask for a *note bytes: 1a5. return value.  Thus, *note
     os.listdir(): 1092. returns a list of *note bytes: 1a5. instances
     if the argument is a *note bytes: 1a5. instance, and *note
     os.getcwdb(): a34. returns the current working directory as a *note
     bytes: 1a5. instance.  Note that when *note os.listdir(): 1092.
     returns a list of strings, filenames that cannot be decoded
     properly are omitted rather than raising *note UnicodeError: 123a.

   * Some system APIs like *note os.environ: 1152. and *note sys.argv:
     11fd. can also present problems when the bytes made available by
     the system is not interpretable using the default encoding.
     Setting the ‘LANG’ variable and rerunning the program is probably
     the best approach.

   * PEP 3138(1): The *note repr(): 7a1. of a string no longer escapes
     non-ASCII characters.  It still escapes control characters and code
     points with non-printable status in the Unicode standard, however.

   * PEP 3120(2): The default source encoding is now UTF-8.

   * PEP 3131(3): Non-ASCII letters are now allowed in identifiers.
     (However, the standard library remains ASCII-only with the
     exception of contributor names in comments.)

   * The ‘StringIO’ and ‘cStringIO’ modules are gone.  Instead, import
     the *note io: 73. module and use *note io.StringIO: ecb. or *note
     io.BytesIO: e46. for text and data respectively.

   * 也請見為了 Python 3.0 所更新的 *note Unicode HOWTO: 123b.。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3138/

   (2) https://peps.python.org/pep-3120/

   (3) https://peps.python.org/pep-3131/


File: python.info,  Node: 語法變更概要,  Next: Changes Already Present In Python 2 6,  Prev: Common Stumbling Blocks,  Up: Python 3 0 有什麼新功能

1.14.2 語法變更概要
-------------------

This section gives a brief overview of every 'syntactic' change in
Python 3.0.

* Menu:

* New Syntax::
* 語法變更::
* 已被移除的語法::


File: python.info,  Node: New Syntax,  Next: 語法變更,  Up: 語法變更概要

1.14.2.1 New Syntax
...................

   * PEP 3107(1): Function argument and return value annotations.  This
     provides a standardized way of annotating a function's parameters
     and return value.  There are no semantics attached to such
     annotations except that they can be introspected at runtime using
     the ‘__annotations__’ attribute.  The intent is to encourage
     experimentation through metaclasses, decorators or frameworks.

   * PEP 3102(2): Keyword-only arguments.  Named parameters occurring
     after ‘*args’ in the parameter list 'must' be specified using
     keyword syntax in the call.  You can also use a bare ‘*’ in the
     parameter list to indicate that you don't accept a variable-length
     argument list, but you do have keyword-only arguments.

   * Keyword arguments are allowed after the list of base classes in a
     class definition.  This is used by the new convention for
     specifying a metaclass (see next section), but can be used for
     other purposes as well, as long as the metaclass supports it.

   * PEP 3104(3): *note nonlocal: 123e. statement.  Using ‘nonlocal x’
     you can now assign directly to a variable in an outer (but
     non-global) scope.  ‘nonlocal’ is a new reserved word.

   * PEP 3132(4): Extended Iterable Unpacking.  You can now write things
     like ‘a, b, *rest = some_sequence’.  And even ‘*rest, a = stuff’.
     The ‘rest’ object is always a (possibly empty) list; the right-hand
     side may be any iterable.  Example:

          (a, *rest, b) = range(5)

     This sets 'a' to ‘0’, 'b' to ‘4’, and 'rest' to ‘[1, 2, 3]’.

   * Dictionary comprehensions: ‘{k: v for k, v in stuff}’ means the
     same thing as ‘dict(stuff)’ but is more flexible.  (This is PEP
     274(5) vindicated.  :-)

   * Set literals, e.g.  ‘{1, 2}’.  Note that ‘{}’ is an empty
     dictionary; use ‘set()’ for an empty set.  Set comprehensions are
     also supported; e.g., ‘{x for x in stuff}’ means the same thing as
     ‘set(stuff)’ but is more flexible.

   * New octal literals, e.g.  ‘0o720’ (already in 2.6).  The old octal
     literals (‘0720’) are gone.

   * New binary literals, e.g.  ‘0b1010’ (already in 2.6), and there is
     a new corresponding built-in function, *note bin(): 123f.

   * Bytes literals are introduced with a leading ‘b’ or ‘B’, and there
     is a new corresponding built-in function, *note bytes(): 1a5.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3107/

   (2) https://peps.python.org/pep-3102/

   (3) https://peps.python.org/pep-3104/

   (4) https://peps.python.org/pep-3132/

   (5) https://peps.python.org/pep-0274/


File: python.info,  Node: 語法變更,  Next: 已被移除的語法,  Prev: New Syntax,  Up: 語法變更概要

1.14.2.2 語法變更
.................

   * PEP 3109(1) and PEP 3134(2): new *note raise: 591. statement
     syntax: ‘raise [EXPR [from EXPR]]’.  See below.

   * ‘as’ and *note with: 577. are now reserved words.  (Since 2.6,
     actually.)

   * ‘True’, ‘False’, and ‘None’ are reserved words.  (2.6 partially
     enforced the restrictions on ‘None’ already.)

   * Change from *note except: 171. 'exc', 'var' to ‘except’ 'exc' ‘as’
     'var'.  See PEP 3110(3).

   * PEP 3115(4): New Metaclass Syntax.  Instead of:

          class C:
              __metaclass__ = M
              ...

     you must now use:

          class C(metaclass=M):
              ...

     The module-global ‘__metaclass__’ variable is no longer supported.
     (It was a crutch to make it easier to default to new-style classes
     without deriving every class from *note object: a2f.)

   * List comprehensions no longer support the syntactic form ‘[... for
     VAR in ITEM1, ITEM2, ...]’.  Use ‘[... for VAR in (ITEM1, ITEM2,
     ...)]’ instead.  Also note that list comprehensions have different
     semantics: they are closer to syntactic sugar for a generator
     expression inside a *note list(): 5b6. constructor, and in
     particular the loop control variables are no longer leaked into the
     surrounding scope.

   * The 'ellipsis' (‘...’) can be used as an atomic expression
     anywhere.  (Previously it was only allowed in slices.)  Also, it
     'must' now be spelled as ‘...’.  (Previously it could also be
     spelled as ‘. . .’, by a mere accident of the grammar.)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3109/

   (2) https://peps.python.org/pep-3134/

   (3) https://peps.python.org/pep-3110/

   (4) https://peps.python.org/pep-3115/


File: python.info,  Node: 已被移除的語法,  Prev: 語法變更,  Up: 語法變更概要

1.14.2.3 已被移除的語法
.......................

   * PEP 3113(1): Tuple parameter unpacking removed.  You can no longer
     write ‘def foo(a, (b, c)): ...’.  Use ‘def foo(a, b_c): b, c = b_c’
     instead.

   * Removed backticks (use *note repr(): 7a1. instead).

   * 移除 ‘<>’(請改用 ‘!=’)。

   * Removed keyword: *note exec(): 162. is no longer a keyword; it
     remains as a function.  (Fortunately the function syntax was also
     accepted in 2.x.)  Also note that *note exec(): 162. no longer
     takes a stream argument; instead of ‘exec(f)’ you can use
     ‘exec(f.read())’.

   * Integer literals no longer support a trailing ‘l’ or ‘L’.

   * String literals no longer support a leading ‘u’ or ‘U’.

   * The *note from: 1242. 'module' *note import: 586. ‘*’ syntax is
     only allowed at the module level, no longer inside functions.

   * The only acceptable syntax for relative imports is ‘from .[MODULE]
     import NAME’.  All *note import: 586. forms not starting with ‘.’
     are interpreted as absolute imports.  ( PEP 328(2))

   * Classic classes are gone.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3113/

   (2) https://peps.python.org/pep-0328/


File: python.info,  Node: Changes Already Present In Python 2 6,  Next: 函式庫變更,  Prev: 語法變更概要,  Up: Python 3 0 有什麼新功能

1.14.3 Changes Already Present In Python 2.6
--------------------------------------------

Since many users presumably make the jump straight from Python 2.5 to
Python 3.0, this section reminds the reader of new features that were
originally designed for Python 3.0 but that were back-ported to Python
2.6.  The corresponding sections in *note Python 2.6 有什麼新功能: 1244.
should be consulted for longer descriptions.

   * *note PEP 343; The 'with' statement: 1245.  The *note with: 577.
     statement is now a standard feature and no longer needs to be
     imported from the *note __future__: 0.  Also check out *note
     Writing Context Managers: 1246. and *note contextlib 模組: 1247.

   * *note PEP 366; Explicit Relative Imports From a Main Module: 1248.
     This enhances the usefulness of the *note -m: 585. option when the
     referenced module lives in a package.

   * *note PEP 370; Per-user site-packages Directory: 1249.。

   * *note PEP 371; The multiprocessing Package: 124a.。

   * *note PEP 3101; Advanced String Formatting: 124b.  Note: the 2.6
     description mentions the *note format(): 5c3. method for both 8-bit
     and Unicode strings.  In 3.0, only the *note str: 3f2. type (text
     strings with Unicode support) supports this method; the *note
     bytes: 1a5. type does not.  The plan is to eventually make this the
     only API for string formatting, and to start deprecating the ‘%’
     operator in Python 3.1.

   * *note PEP 3105; print As a Function: 124c.  This is now a standard
     feature and no longer needs to be imported from *note __future__:
     0.  More details were given above.

   * *note PEP 3110; Exception-Handling Changes: 124d.  The *note
     except: 171. 'exc' ‘as’ 'var' syntax is now standard and ‘except’
     'exc', 'var' is no longer supported.  (Of course, the ‘as’ 'var'
     part is still optional.)

   * *note PEP 3112; Byte Literals: 124e.  The ‘b"..."’ string literal
     notation (and its variants like ‘b'...'’, ‘b"""..."""’, and
     ‘br"..."’) now produces a literal of type *note bytes: 1a5.

   * *note PEP 3116; New I/O Library: 124f.  The *note io: 73. module is
     now the standard way of doing file I/O. The built-in *note open():
     4c0. function is now an alias for *note io.open(): 4c1. and has
     additional keyword arguments 'encoding', 'errors', 'newline' and
     'closefd'.  Also note that an invalid 'mode' argument now raises
     *note ValueError: 1e7, not *note IOError: ff5.  The binary file
     object underlying a text file object can be accessed as ‘f.buffer’
     (but beware that the text object maintains a buffer of itself in
     order to speed up the encoding and decoding operations).

   * *note PEP 3118：修訂緩衝協定: 1250.  The old builtin ‘buffer()’ is
     now really gone; the new builtin *note memoryview(): 40f. provides
     (mostly) similar functionality.

   * *note PEP 3119; Abstract Base Classes: 1251.  The *note abc: 4.
     module and the ABCs defined in the *note collections: 16. module
     plays a somewhat more prominent role in the language now, and
     built-in collection types like *note dict: 23b. and *note list:
     5b6. conform to the ‘collections.MutableMapping’ and
     ‘collections.MutableSequence’ ABCs, respectively.

   * *note PEP 3127; Integer Literal Support and Syntax: 1252.  As
     mentioned above, the new octal literal notation is the only one
     supported, and binary literals have been added.

   * *note PEP 3129; Class Decorators: 1253.。

   * *note PEP 3141; A Type Hierarchy for Numbers: 1254.  The *note
     numbers: 8e. module is another new use of ABCs, defining Python's
     "numeric tower".  Also note the new *note fractions: 53. module
     which implements *note numbers.Rational: 1255.


File: python.info,  Node: 函式庫變更,  Next: PEP 3101 A New Approach To String Formatting,  Prev: Changes Already Present In Python 2 6,  Up: Python 3 0 有什麼新功能

1.14.4 函式庫變更
-----------------

Due to time constraints, this document does not exhaustively cover the
very extensive changes to the standard library.  PEP 3108(1) is the
reference for the major changes to the library.  Here's a capsule
review:

   * Many old modules were removed.  Some, like ‘gopherlib’ (no longer
     used) and ‘md5’ (replaced by *note hashlib: 5e.), were already
     deprecated by PEP 4(2).  Others were removed as a result of the
     removal of support for various platforms such as Irix, BeOS and Mac
     OS 9 (see PEP 11(3)).  Some modules were also selected for removal
     in Python 3.0 due to lack of use or because a better replacement
     exists.  See PEP 3108(4) for an exhaustive list.

   * The ‘bsddb3’ package was removed because its presence in the core
     standard library has proved over time to be a particular burden for
     the core developers due to testing instability and Berkeley DB's
     release schedule.  However, the package is alive and well,
     externally maintained at
     ‘https://www.jcea.es/programacion/pybsddb.htm’.

   * 一些模組因為舊名稱違反了 PEP 8(5) 或其他原因而被重新命名。以下為變
     更清單：

     舊名                        新名
                                 
     --------------------------------------------------------
                                 
     _winreg                     winreg
                                 
                                 
     ConfigParser                configparser
                                 
                                 
     copy_reg                    copyreg
                                 
                                 
     Queue                       queue
                                 
                                 
     SocketServer                socketserver
                                 
                                 
     markupbase                  _markupbase
                                 
                                 
     repr                        reprlib
                                 
                                 
     test.test_support           test.support
                                 

   * A common pattern in Python 2.x is to have one version of a module
     implemented in pure Python, with an optional accelerated version
     implemented as a C extension; for example, *note pickle: 95. and
     ‘cPickle’.  This places the burden of importing the accelerated
     version and falling back on the pure Python version on each user of
     these modules.  In Python 3.0, the accelerated versions are
     considered implementation details of the pure Python versions.
     Users should always import the standard version, which attempts to
     import the accelerated version and falls back to the pure Python
     version.  The *note pickle: 95. / ‘cPickle’ pair received this
     treatment.  The *note profile: 9d. module is on the list for 3.1.
     The ‘StringIO’ module has been turned into a class in the *note io:
     73. module.

   * Some related modules have been grouped into packages, and usually
     the submodule names have been simplified.  The resulting new
     packages are:

        * *note dbm: 29.（‘anydbm’、‘dbhash’、‘dbm’、‘dumbdbm’、‘gdbm’、
          ‘whichdb’）。

        * *note html: 61.（‘HTMLParser’、‘htmlentitydefs’）。

        * *note http: 64.（‘httplib’、‘BaseHTTPServer’、
          ‘CGIHTTPServer’、‘SimpleHTTPServer’、‘Cookie’、‘cookielib’）。

        * *note tkinter: d9. (all ‘Tkinter’-related modules except *note
          turtle: ea.).  The target audience of *note turtle: ea.
          doesn't really care about *note tkinter: d9.  Also note that
          as of Python 2.6, the functionality of *note turtle: ea. has
          been greatly enhanced.

        * *note urllib: f1.（‘urllib’、‘urllib2’、‘urlparse’、
          ‘robotparse’）。

        * ‘xmlrpc’（‘xmlrpclib’、‘DocXMLRPCServer’、
          ‘SimpleXMLRPCServer’）。

Some other changes to standard library modules, not covered by PEP
3108(6):

   * 移除 ‘sets’。請使用內建的 *note set(): 57d. 類別。

   * Cleanup of the *note sys: c3. module: removed ‘sys.exitfunc()’,
     ‘sys.exc_clear()’, ‘sys.exc_type’, ‘sys.exc_value’,
     ‘sys.exc_traceback’.  (Note that *note sys.last_type: 466. etc.
     remain.)

   * Cleanup of the *note array.array: 186. type: the ‘read()’ and
     ‘write()’ methods are gone; use ‘fromfile()’ and ‘tofile()’
     instead.  Also, the ‘'c'’ typecode for array is gone - use either
     ‘'b'’ for bytes or ‘'u'’ for Unicode characters.

   * Cleanup of the *note operator: 8f. module: removed
     ‘sequenceIncludes()’ and ‘isCallable()’.

   * Cleanup of the ‘thread’ module: ‘acquire_lock()’ and
     ‘release_lock()’ are gone; use *note acquire(): 63e. and *note
     release(): 1257. instead.

   * 清理 *note random: a6. 模組：移除 ‘jumpahead()’ API。

   * 移除 ‘new’ 模組。

   * The functions ‘os.tmpnam()’, ‘os.tempnam()’ and ‘os.tmpfile()’ have
     been removed in favor of the *note tempfile: c9. module.

   * The *note tokenize: e4. module has been changed to work with bytes.
     The main entry point is now *note tokenize.tokenize(): 481, instead
     of generate_tokens.

   * ‘string.letters’ and its friends (‘string.lowercase’ and
     ‘string.uppercase’) are gone.  Use *note string.ascii_letters:
     1258. etc.  instead.  (The reason for the removal is that
     ‘string.letters’ and friends had locale-specific behavior, which is
     a bad idea for such attractively named global "constants".)

   * Renamed module ‘__builtin__’ to *note builtins: e. (removing the
     underscores, adding an 's').  The ‘__builtins__’ variable found in
     most global namespaces is unchanged.  To modify a builtin, you
     should use *note builtins: e, not ‘__builtins__’!

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3108/

   (2) https://peps.python.org/pep-0004/

   (3) https://peps.python.org/pep-0011/

   (4) https://peps.python.org/pep-3108/

   (5) https://peps.python.org/pep-0008/

   (6) https://peps.python.org/pep-3108/


File: python.info,  Node: PEP 3101 A New Approach To String Formatting,  Next: Changes To Exceptions,  Prev: 函式庫變更,  Up: Python 3 0 有什麼新功能

'PEP 3101': A New Approach To String Formatting

   * A new system for built-in string formatting operations replaces the
     ‘%’ string formatting operator.  (However, the ‘%’ operator is
     still supported; it will be deprecated in Python 3.1 and removed
     from the language at some later time.)  Read PEP 3101(1) for the
     full scoop.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3101/


File: python.info,  Node: Changes To Exceptions,  Next: Miscellaneous Other Changes,  Prev: PEP 3101 A New Approach To String Formatting,  Up: Python 3 0 有什麼新功能

1.14.6 Changes To Exceptions
----------------------------

The APIs for raising and catching exception have been cleaned up and new
powerful features added:

   * PEP 352(1): All exceptions must be derived (directly or indirectly)
     from *note BaseException: 55f.  This is the root of the exception
     hierarchy.  This is not new as a recommendation, but the
     'requirement' to inherit from *note BaseException: 55f. is new.
     (Python 2.6 still allowed classic classes to be raised, and placed
     no restriction on what you can catch.)  As a consequence, string
     exceptions are finally truly and utterly dead.

   * Almost all exceptions should actually derive from *note Exception:
     97d.; *note BaseException: 55f. should only be used as a base class
     for exceptions that should only be handled at the top level, such
     as *note SystemExit: ce7. or *note KeyboardInterrupt: 975.  The
     recommended idiom for handling all exceptions except for this
     latter category is to use *note except: 171. *note Exception: 97d.

   * ‘StandardError’ 被移除。

   * Exceptions no longer behave as sequences.  Use the ‘args’ attribute
     instead.

   * PEP 3109(2): Raising exceptions.  You must now use ‘raise
     EXCEPTION(ARGS)’ instead of ‘raise EXCEPTION, ARGS’.  Additionally,
     you can no longer explicitly specify a traceback; instead, if you
     'have' to do this, you can assign directly to the *note
     __traceback__: 125b. attribute (see below).

   * PEP 3110(3): Catching exceptions.  You must now use ‘except
     SOMEEXCEPTION as VARIABLE’ instead of ‘except SOMEEXCEPTION,
     VARIABLE’.  Moreover, the 'variable' is explicitly deleted when the
     *note except: 171. block is left.

   * PEP 3134(4): Exception chaining.  There are two cases: implicit
     chaining and explicit chaining.  Implicit chaining happens when an
     exception is raised in an *note except: 171. or *note finally: 96e.
     handler block.  This usually happens due to a bug in the handler
     block; we call this a 'secondary' exception.  In this case, the
     original exception (that was being handled) is saved as the *note
     __context__: 125c. attribute of the secondary exception.  Explicit
     chaining is invoked with this syntax:

          raise SecondaryException() from primary_exception

     (where 'primary_exception' is any expression that produces an
     exception object, probably an exception that was previously
     caught).  In this case, the primary exception is stored on the
     *note __cause__: 125d. attribute of the secondary exception.  The
     traceback printed when an unhandled exception occurs walks the
     chain of ‘__cause__’ and *note __context__: 125c. attributes and
     prints a separate traceback for each component of the chain, with
     the primary exception at the top.  (Java users may recognize this
     behavior.)

   * PEP 3134(5): Exception objects now store their traceback as the
     *note __traceback__: 125b. attribute.  This means that an exception
     object now contains all the information pertaining to an exception,
     and there are fewer reasons to use *note sys.exc_info(): 630.
     (though the latter is not removed).

   * A few exception messages are improved when Windows fails to load an
     extension module.  For example, ‘error code 193’ is now ‘%1 is not
     a valid Win32 application’.  Strings now deal with non-English
     locales.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0352/

   (2) https://peps.python.org/pep-3109/

   (3) https://peps.python.org/pep-3110/

   (4) https://peps.python.org/pep-3134/

   (5) https://peps.python.org/pep-3134/


File: python.info,  Node: Miscellaneous Other Changes,  Next: Build and C API Changes<6>,  Prev: Changes To Exceptions,  Up: Python 3 0 有什麼新功能

1.14.7 Miscellaneous Other Changes
----------------------------------

* Menu:

* Operators And Special Methods::
* Builtins::


File: python.info,  Node: Operators And Special Methods,  Next: Builtins,  Up: Miscellaneous Other Changes

1.14.7.1 Operators And Special Methods
......................................

   * ‘!=’ now returns the opposite of ‘==’, unless ‘==’ returns *note
     NotImplemented: 776.

   * The concept of "unbound methods" has been removed from the
     language.  When referencing a method as a class attribute, you now
     get a plain function object.

   * ‘__getslice__()’, ‘__setslice__()’ and ‘__delslice__()’ were
     killed.  The syntax ‘a[i:j]’ now translates to
     ‘a.__getitem__(slice(i, j))’ (or ‘__setitem__()’ or
     ‘__delitem__()’, when used as an assignment or deletion target,
     respectively).

   * PEP 3114(1): the standard *note next(): 77c. method has been
     renamed to *note __next__(): 1260.

   * The ‘__oct__()’ and ‘__hex__()’ special methods are removed - *note
     oct(): 1261. and *note hex(): 1262. use ‘__index__()’ now to
     convert the argument to an integer.

   * 移除對 ‘__members__’ 和 ‘__methods__’ 的支援。

   * The function attributes named ‘func_X’ have been renamed to use the
     ‘__X__’ form, freeing up these names in the function attribute
     namespace for user-defined attributes.  To wit, ‘func_closure’,
     ‘func_code’, ‘func_defaults’, ‘func_dict’, ‘func_doc’,
     ‘func_globals’, ‘func_name’ were renamed to *note __closure__:
     1263, *note __code__: 296, *note __defaults__: 1264, *note
     __dict__: 1265, *note __doc__: 1171, *note __globals__: 1266, *note
     __name__: 1267, respectively.

   * ‘__nonzero__()’ 現在為 *note __bool__(): 1268.。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3114/


File: python.info,  Node: Builtins,  Prev: Operators And Special Methods,  Up: Miscellaneous Other Changes

1.14.7.2 Builtins
.................

   * PEP 3135(1): New *note super(): 483.  You can now invoke *note
     super(): 483. without arguments and (assuming this is in a regular
     instance method defined inside a *note class: 126a. statement) the
     right class and instance will automatically be chosen.  With
     arguments, the behavior of *note super(): 483. is unchanged.

   * PEP 3111(2): ‘raw_input()’ was renamed to *note input(): 126b.
     That is, the new *note input(): 126b. function reads a line from
     *note sys.stdin: 4e2. and returns it with the trailing newline
     stripped.  It raises *note EOFError: 126c. if the input is
     terminated prematurely.  To get the old behavior of *note input():
     126b, use ‘eval(input())’.

   * A new built-in function *note next(): 77c. was added to call the
     *note __next__(): 1260. method on an object.

   * The *note round(): 126d. function rounding strategy and return type
     have changed.  Exact halfway cases are now rounded to the nearest
     even result instead of away from zero.  (For example, ‘round(2.5)’
     now returns ‘2’ rather than ‘3’.)  ‘round(x[, n])’ now delegates to
     ‘x.__round__([n])’ instead of always returning a float.  It
     generally returns an integer when called with a single argument and
     a value of the same type as ‘x’ when called with two arguments.

   * Moved ‘intern()’ to *note sys.intern(): 126e.

   * Removed: ‘apply()’.  Instead of ‘apply(f, args)’ use ‘f(*args)’.

   * Removed *note callable(): 115e.  Instead of ‘callable(f)’ you can
     use ‘isinstance(f, collections.Callable)’.  The
     ‘operator.isCallable()’ function is also gone.

   * Removed ‘coerce()’.  This function no longer serves a purpose now
     that classic classes are gone.

   * 移除 ‘execfile()’。請使用 ‘exec(open(fn).read())’ 來替換
     ‘execfile(fn)’。

   * Removed the ‘file’ type.  Use *note open(): 4c0.  There are now
     several different kinds of streams that open can return in the
     *note io: 73. module.

   * Removed ‘reduce()’.  Use *note functools.reduce(): 126f. if you
     really need it; however, 99 percent of the time an explicit *note
     for: 2c3. loop is more readable.

   * Removed ‘reload()’.  Use ‘imp.reload()’.

   * Removed.  ‘dict.has_key()’ - use the *note in: 2c5. operator
     instead.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3135/

   (2) https://peps.python.org/pep-3111/


File: python.info,  Node: Build and C API Changes<6>,  Next: Performance,  Prev: Miscellaneous Other Changes,  Up: Python 3 0 有什麼新功能

1.14.8 Build and C API Changes
------------------------------

Due to time constraints, here is a 'very' incomplete list of changes to
the C API.

   * Support for several platforms was dropped, including but not
     limited to Mac OS 9, BeOS, RISCOS, Irix, and Tru64.

   * PEP 3118(1)：新的緩衝 API。

   * PEP 3121(2): Extension Module Initialization & Finalization.

   * PEP 3123(3): Making *note PyObject_HEAD: 1271. conform to standard
     C.

   * No more C API support for restricted execution.

   * ‘PyNumber_Coerce()’, ‘PyNumber_CoerceEx()’, ‘PyMember_Get()’, and
     ‘PyMember_Set()’ C APIs are removed.

   * New C API *note PyImport_ImportModuleNoBlock(): 388, works like
     *note PyImport_ImportModule(): 389. but won't block on the import
     lock (returning an error instead).

   * Renamed the boolean conversion C-level slot and method:
     ‘nb_nonzero’ is now ‘nb_bool’.

   * 移除 C API 中的 ‘METH_OLDARGS’ 和 ‘WITH_CYCLE_GC’。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3118/

   (2) https://peps.python.org/pep-3121/

   (3) https://peps.python.org/pep-3123/


File: python.info,  Node: Performance,  Next: Porting To Python 3 0,  Prev: Build and C API Changes<6>,  Up: Python 3 0 有什麼新功能

1.14.9 Performance
------------------

The net result of the 3.0 generalizations is that Python 3.0 runs the
pystone benchmark around 10% slower than Python 2.5.  Most likely the
biggest cause is the removal of special-casing for small integers.
There's room for improvement, but it will happen after 3.0 is released!


File: python.info,  Node: Porting To Python 3 0,  Prev: Performance,  Up: Python 3 0 有什麼新功能

1.14.10 Porting To Python 3.0
-----------------------------

For porting existing Python 2.5 or 2.6 source code to Python 3.0, the
best strategy is the following:

  0. (Prerequisite:) Start with excellent test coverage.

  1. Port to Python 2.6.  This should be no more work than the average
     port from Python 2.x to Python 2.(x+1).  Make sure all your tests
     pass.

  2. (Still using 2.6:) Turn on the ‘-3’ command line switch.  This
     enables warnings about features that will be removed (or change) in
     3.0.  Run your test suite again, and fix code that you get warnings
     about until there are no warnings left, and all your tests still
     pass.

  3. Run the ‘2to3’ source-to-source translator over your source code
     tree.  Run the result of the translation under Python 3.0.
     Manually fix up any remaining issues, fixing problems until all
     tests pass again.

It is not recommended to try to write source code that runs unchanged
under both Python 2.6 and 3.0; you'd have to use a very contorted coding
style, e.g.  avoiding ‘print’ statements, metaclasses, and much more.
If you are maintaining a library that needs to support both Python 2.6
and Python 3.0, the best approach is to modify step 3 above by editing
the 2.6 version of the source code and running the ‘2to3’ translator
again, rather than editing the 3.0 version of the source code.

For porting C extensions to Python 3.0, please see *note 遷移延伸模組到
Python 3: 1274.


File: python.info,  Node: Python 2 7 有什麼新功能,  Next: Python 2 6 有什麼新功能,  Prev: Python 3 0 有什麼新功能,  Up: Python 有什麼新功能？

1.15 Python 2.7 有什麼新功能
============================


作者: A.M. Kuchling (amk at amk.ca)

This article explains the new features in Python 2.7.  Python 2.7 was
released on July 3, 2010.

Numeric handling has been improved in many ways, for both floating-point
numbers and for the *note Decimal: 27c. class.  There are some useful
additions to the standard library, such as a greatly enhanced *note
unittest: ef. module, the *note argparse: 5. module for parsing
command-line options, convenient *note OrderedDict: 57f. and *note
Counter: 1033. classes in the *note collections: 16. module, and many
other improvements.

Python 2.7 is planned to be the last of the 2.x releases, so we worked
on making it a good release for the long term.  To help with porting to
Python 3, several new features from the Python 3.x series have been
included in 2.7.

This article doesn't attempt to provide a complete specification of the
new features, but instead provides a convenient overview.  For full
details, you should refer to the documentation for Python 2.7 at
‘https://docs.python.org’.  If you want to understand the rationale for
the design and implementation, refer to the PEP for a particular new
feature or the issue on ‘https://bugs.python.org’ in which a change was
discussed.  Whenever possible, "What's New in Python" links to the
bug/patch item for each change.

* Menu:

* Python 2.x 的未來: Python 2 x 的未來.
* Changes to the Handling of Deprecation Warnings::
* Python 3.1 Features: Python 3 1 Features.
* PEP 372; Adding an Ordered Dictionary to collections: PEP 372 Adding an Ordered Dictionary to collections.
* PEP 378; Format Specifier for Thousands Separator: PEP 378 Format Specifier for Thousands Separator<2>.
* PEP 389; The argparse Module for Parsing Command Lines: PEP 389 The argparse Module for Parsing Command Lines.
* PEP 391; Dictionary-Based Configuration For Logging: PEP 391 Dictionary-Based Configuration For Logging.
* PEP 3106; Dictionary Views: PEP 3106 Dictionary Views.
* PEP 3137; The memoryview Object: PEP 3137 The memoryview Object.
* 其他語言更動: 其他語言更動<13>.
* New and Improved Modules::
* Build and C API Changes: Build and C API Changes<7>.
* Other Changes and Fixes::
* Porting to Python 2.7: Porting to Python 2 7.
* New Features Added to Python 2.7 Maintenance Releases: New Features Added to Python 2 7 Maintenance Releases.
* 致謝::


File: python.info,  Node: Python 2 x 的未來,  Next: Changes to the Handling of Deprecation Warnings,  Up: Python 2 7 有什麼新功能

1.15.1 Python 2.x 的未來
------------------------

Python 2.7 is the last major release in the 2.x series, as the Python
maintainers have shifted the focus of their new feature development
efforts to the Python 3.x series.  This means that while Python 2
continues to receive bug fixes, and to be updated to build correctly on
new hardware and versions of supported operated systems, there will be
no new full feature releases for the language or standard library.

However, while there is a large common subset between Python 2.7 and
Python 3, and many of the changes involved in migrating to that common
subset, or directly to Python 3, can be safely automated, some other
changes (notably those associated with Unicode handling) may require
careful consideration, and preferably robust automated regression test
suites, to migrate effectively.

This means that Python 2.7 will remain in place for a long time,
providing a stable and supported base platform for production systems
that have not yet been ported to Python 3.  The full expected lifecycle
of the Python 2.7 series is detailed in PEP 373(1).

Some key consequences of the long-term significance of 2.7 are:

   * As noted above, the 2.7 release has a much longer period of
     maintenance when compared to earlier 2.x versions.  Python 2.7 is
     currently expected to remain supported by the core development team
     (receiving security updates and other bug fixes) until at least
     2020 (10 years after its initial release, compared to the more
     typical support period of 18-24 months).

   * As the Python 2.7 standard library ages, making effective use of
     the Python Package Index (either directly or via a redistributor)
     becomes more important for Python 2 users.  In addition to a wide
     variety of third party packages for various tasks, the available
     packages include backports of new modules and features from the
     Python 3 standard library that are compatible with Python 2, as
     well as various tools and libraries that can make it easier to
     migrate to Python 3.  The Python Packaging User Guide(2) provides
     guidance on downloading and installing software from the Python
     Package Index.

   * While the preferred approach to enhancing Python 2 is now the
     publication of new packages on the Python Package Index, this
     approach doesn't necessarily work in all cases, especially those
     related to network security.  In exceptional cases that cannot be
     handled adequately by publishing new or updated packages on PyPI,
     the Python Enhancement Proposal process may be used to make the
     case for adding new features directly to the Python 2 standard
     library.  Any such additions, and the maintenance releases where
     they were added, will be noted in the *note New Features Added to
     Python 2.7 Maintenance Releases: 1279. section below.

For projects wishing to migrate from Python 2 to Python 3, or for
library and framework developers wishing to support users on both Python
2 and Python 3, there are a variety of tools and guides available to
help decide on a suitable approach and manage some of the technical
details involved.  The recommended starting point is the pyporting-howto
HOWTO guide.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0373/

   (2) https://packaging.python.org


File: python.info,  Node: Changes to the Handling of Deprecation Warnings,  Next: Python 3 1 Features,  Prev: Python 2 x 的未來,  Up: Python 2 7 有什麼新功能

1.15.2 Changes to the Handling of Deprecation Warnings
------------------------------------------------------

For Python 2.7, a policy decision was made to silence warnings only of
interest to developers by default.  *note DeprecationWarning: 18b. and
its descendants are now ignored unless otherwise requested, preventing
users from seeing warnings triggered by an application.  This change was
also made in the branch that became Python 3.2.  (Discussed on
stdlib-sig and carried out in bpo-7319(1).)

In previous releases, *note DeprecationWarning: 18b. messages were
enabled by default, providing Python developers with a clear indication
of where their code may break in a future major version of Python.

However, there are increasingly many users of Python-based applications
who are not directly involved in the development of those applications.
*note DeprecationWarning: 18b. messages are irrelevant to such users,
making them worry about an application that's actually working correctly
and burdening application developers with responding to these concerns.

You can re-enable display of *note DeprecationWarning: 18b. messages by
running Python with the *note -Wdefault: 86c. (short form: *note -Wd:
86c.) switch, or by setting the *note PYTHONWARNINGS: b51. environment
variable to ‘"default"’ (or ‘"d"’) before running Python.  Python code
can also re-enable them by calling ‘warnings.simplefilter('default')’.

The ‘unittest’ module also automatically reenables deprecation warnings
when running tests.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=7319


File: python.info,  Node: Python 3 1 Features,  Next: PEP 372 Adding an Ordered Dictionary to collections,  Prev: Changes to the Handling of Deprecation Warnings,  Up: Python 2 7 有什麼新功能

1.15.3 Python 3.1 Features
--------------------------

Much as Python 2.6 incorporated features from Python 3.0, version 2.7
incorporates some of the new features in Python 3.1.  The 2.x series
continues to provide tools for migrating to the 3.x series.

A partial list of 3.1 features that were backported to 2.7:

   * The syntax for set literals (‘{1,2,3}’ is a mutable set).

   * Dictionary and set comprehensions (‘{i: i*2 for i in range(3)}’).

   * Multiple context managers in a single *note with: 577. statement.

   * A new version of the *note io: 73. library, rewritten in C for
     performance.

   * The ordered-dictionary type described in *note PEP 372; Adding an
     Ordered Dictionary to collections: 127c.

   * The new ‘","’ format specifier described in *note PEP 378; Format
     Specifier for Thousands Separator: 127d.

   * *note memoryview: 40f. 物件。

   * A small subset of the *note importlib: 6b. module, *note described
     below: 127e.

   * The *note repr(): 7a1. of a float ‘x’ is shorter in many cases:
     it's now based on the shortest decimal string that's guaranteed to
     round back to ‘x’.  As in previous versions of Python, it's
     guaranteed that ‘float(repr(x))’ recovers ‘x’.

   * Float-to-string and string-to-float conversions are correctly
     rounded.  The *note round(): 126d. function is also now correctly
     rounded.

   * The *note PyCapsule: 120b. type, used to provide a C API for
     extension modules.

   * *note PyLong_AsLongAndOverflow(): 11ff. C API 函式。

Other new Python3-mode warnings include:

   * ‘operator.isCallable()’ and ‘operator.sequenceIncludes()’, which
     are not supported in 3.x, now trigger warnings.

   * The ‘-3’ switch now automatically enables the ‘-Qwarn’ switch that
     causes warnings about using classic division with integers and long
     integers.


File: python.info,  Node: PEP 372 Adding an Ordered Dictionary to collections,  Next: PEP 378 Format Specifier for Thousands Separator<2>,  Prev: Python 3 1 Features,  Up: Python 2 7 有什麼新功能

1.15.4 PEP 372: Adding an Ordered Dictionary to collections
-----------------------------------------------------------

Regular Python dictionaries iterate over key/value pairs in arbitrary
order.  Over the years, a number of authors have written alternative
implementations that remember the order that the keys were originally
inserted.  Based on the experiences from those implementations, 2.7
introduces a new *note OrderedDict: 57f. class in the *note collections:
16. module.

The *note OrderedDict: 57f. API provides the same interface as regular
dictionaries but iterates over keys and values in a guaranteed order
depending on when a key was first inserted:

     >>> from collections import OrderedDict
     >>> d = OrderedDict([('first', 1),
     ...                  ('second', 2),
     ...                  ('third', 3)])
     >>> d.items()
     [('first', 1), ('second', 2), ('third', 3)]

If a new entry overwrites an existing entry, the original insertion
position is left unchanged:

     >>> d['second'] = 4
     >>> d.items()
     [('first', 1), ('second', 4), ('third', 3)]

Deleting an entry and reinserting it will move it to the end:

     >>> del d['second']
     >>> d['second'] = 5
     >>> d.items()
     [('first', 1), ('third', 3), ('second', 5)]

The *note popitem(): 1280. method has an optional 'last' argument that
defaults to ‘True’.  If 'last' is true, the most recently added key is
returned and removed; if it's false, the oldest key is selected:

     >>> od = OrderedDict([(x,0) for x in range(20)])
     >>> od.popitem()
     (19, 0)
     >>> od.popitem()
     (18, 0)
     >>> od.popitem(last=False)
     (0, 0)
     >>> od.popitem(last=False)
     (1, 0)

Comparing two ordered dictionaries checks both the keys and values, and
requires that the insertion order was the same:

     >>> od1 = OrderedDict([('first', 1),
     ...                    ('second', 2),
     ...                    ('third', 3)])
     >>> od2 = OrderedDict([('third', 3),
     ...                    ('first', 1),
     ...                    ('second', 2)])
     >>> od1 == od2
     False
     >>> # Move 'third' key to the end
     >>> del od2['third']; od2['third'] = 3
     >>> od1 == od2
     True

Comparing an *note OrderedDict: 57f. with a regular dictionary ignores
the insertion order and just compares the keys and values.

How does the *note OrderedDict: 57f. work?  It maintains a doubly linked
list of keys, appending new keys to the list as they're inserted.  A
secondary dictionary maps keys to their corresponding list node, so
deletion doesn't have to traverse the entire linked list and therefore
remains 'O'(1).

The standard library now supports use of ordered dictionaries in several
modules.

   * The *note ConfigParser: 1b. module uses them by default, meaning
     that configuration files can now be read, modified, and then
     written back in their original order.

   * The *note _asdict(): 985. method for *note
     collections.namedtuple(): 1ae. now returns an ordered dictionary
     with the values appearing in the same order as the underlying tuple
     indices.

   * The *note json: 76. module's *note JSONDecoder: cee. class
     constructor was extended with an 'object_pairs_hook' parameter to
     allow ‘OrderedDict’ instances to be built by the decoder.  Support
     was also added for third-party tools like PyYAML(1).

也參考
......

PEP 372(2) - Adding an ordered dictionary to collections

     PEP written by Armin Ronacher and Raymond Hettinger; implemented by
     Raymond Hettinger.

   ---------- Footnotes ----------

   (1) https://pyyaml.org/

   (2) https://peps.python.org/pep-0372/


File: python.info,  Node: PEP 378 Format Specifier for Thousands Separator<2>,  Next: PEP 389 The argparse Module for Parsing Command Lines,  Prev: PEP 372 Adding an Ordered Dictionary to collections,  Up: Python 2 7 有什麼新功能

1.15.5 PEP 378: Format Specifier for Thousands Separator
--------------------------------------------------------

To make program output more readable, it can be useful to add separators
to large numbers, rendering them as 18,446,744,073,709,551,616 instead
of 18446744073709551616.

The fully general solution for doing this is the *note locale: 7a.
module, which can use different separators ("," in North America, "."
in Europe) and different grouping sizes, but *note locale: 7a. is
complicated to use and unsuitable for multi-threaded applications where
different threads are producing output for different locales.

Therefore, a simple comma-grouping mechanism has been added to the
mini-language used by the *note str.format(): 5c7. method.  When
formatting a floating-point number, simply include a comma between the
width and the precision:

     >>> '{:20,.2f}'.format(18446744073709551616.0)
     '18,446,744,073,709,551,616.00'

When formatting an integer, include the comma after the width:

     >>> '{:20,d}'.format(18446744073709551616)
     '18,446,744,073,709,551,616'

This mechanism is not adaptable at all; commas are always used as the
separator and the grouping is always into three-digit groups.  The
comma-formatting mechanism isn't as general as the *note locale: 7a.
module, but it's easier to use.

也參考
......

PEP 378(1) - Format Specifier for Thousands Separator

     由 Raymond Hettinger 撰寫 PEP；由 Eric Smith 實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0378/


File: python.info,  Node: PEP 389 The argparse Module for Parsing Command Lines,  Next: PEP 391 Dictionary-Based Configuration For Logging,  Prev: PEP 378 Format Specifier for Thousands Separator<2>,  Up: Python 2 7 有什麼新功能

1.15.6 PEP 389: The argparse Module for Parsing Command Lines
-------------------------------------------------------------

The *note argparse: 5. module for parsing command-line arguments was
added as a more powerful replacement for the *note optparse: 90. module.

This means Python now supports three different modules for parsing
command-line arguments: *note getopt: 57, *note optparse: 90, and *note
argparse: 5.  The *note getopt: 57. module closely resembles the C
library's ‘getopt()’ function, so it remains useful if you're writing a
Python prototype that will eventually be rewritten in C. *note optparse:
90. becomes redundant, but there are no plans to remove it because there
are many scripts still using it, and there's no automated way to update
these scripts.  (Making the *note argparse: 5. API consistent with *note
optparse: 90.'s interface was discussed but rejected as too messy and
difficult.)

In short, if you're writing a new script and don't need to worry about
compatibility with earlier versions of Python, use *note argparse: 5.
instead of *note optparse: 90.

以下是個範例：

     import argparse

     parser = argparse.ArgumentParser(description='Command-line example.')

     # Add optional switches
     parser.add_argument('-v', action='store_true', dest='is_verbose',
                         help='produce verbose output')
     parser.add_argument('-o', action='store', dest='output',
                         metavar='FILE',
                         help='direct output to FILE instead of stdout')
     parser.add_argument('-C', action='store', type=int, dest='context',
                         metavar='NUM', default=0,
                         help='display NUM lines of added context')

     # Allow any number of additional arguments.
     parser.add_argument(nargs='*', action='store', dest='inputs',
                         help='input filenames (default is stdin)')

     args = parser.parse_args()
     print args.__dict__

Unless you override it, ‘-h’ and ‘--help’ switches are automatically
added, and produce neatly formatted output:

     -> ./python.exe argparse-example.py --help
     usage: argparse-example.py [-h] [-v] [-o FILE] [-C NUM] [inputs [inputs ...]]

     Command-line example.

     positional arguments:
       inputs      input filenames (default is stdin)

     optional arguments:
       -h, --help  show this help message and exit
       -v          produce verbose output
       -o FILE     direct output to FILE instead of stdout
       -C NUM      display NUM lines of added context

As with *note optparse: 90, the command-line switches and arguments are
returned as an object with attributes named by the 'dest' parameters:

     -> ./python.exe argparse-example.py -v
     {'output': None,
      'is_verbose': True,
      'context': 0,
      'inputs': []}

     -> ./python.exe argparse-example.py -v -o /tmp/output -C 4 file1 file2
     {'output': '/tmp/output',
      'is_verbose': True,
      'context': 4,
      'inputs': ['file1', 'file2']}

*note argparse: 5. has much fancier validation than *note optparse: 90.;
you can specify an exact number of arguments as an integer, 0 or more
arguments by passing ‘'*'’, 1 or more by passing ‘'+'’, or an optional
argument with ‘'?'’.  A top-level parser can contain sub-parsers to
define subcommands that have different sets of switches, as in ‘svn
commit’, ‘svn checkout’, etc.  You can specify an argument's type as
*note FileType: ebf, which will automatically open files for you and
understands that ‘'-'’ means standard input or output.

也參考
......

*note argparse: 5. 文件

     argparse 模組的文件頁面。

*note Upgrading optparse code: 1145.

     Part of the Python documentation, describing how to convert code
     that uses *note optparse: 90.

PEP 389(1) - argparse - New Command Line Parsing Module

     由 Steven Bethard 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0389/


File: python.info,  Node: PEP 391 Dictionary-Based Configuration For Logging,  Next: PEP 3106 Dictionary Views,  Prev: PEP 389 The argparse Module for Parsing Command Lines,  Up: Python 2 7 有什麼新功能

1.15.7 PEP 391: Dictionary-Based Configuration For Logging
----------------------------------------------------------

The *note logging: 7b. module is very flexible; applications can define
a tree of logging subsystems, and each logger in this tree can filter
out certain messages, format them differently, and direct messages to a
varying number of handlers.

All this flexibility can require a lot of configuration.  You can write
Python statements to create objects and set their properties, but a
complex set-up requires verbose but boring code.  *note logging: 7b.
also supports a *note fileConfig(): af5. function that parses a file,
but the file format doesn't support configuring filters, and it's
messier to generate programmatically.

Python 2.7 adds a *note dictConfig(): 1147. function that uses a
dictionary to configure logging.  There are many ways to produce a
dictionary from different sources: construct one with code; parse a file
containing JSON; or use a YAML parsing library if one is installed.  For
more information see *note Configuration functions: 1284.

The following example configures two loggers, the root logger and a
logger named "network".  Messages sent to the root logger will be sent
to the system log using the syslog protocol, and messages to the
"network" logger will be written to a ‘network.log’ file that will be
rotated once the log reaches 1MB.

     import logging
     import logging.config

     configdict = {
      'version': 1,    # Configuration schema in use; must be 1 for now
      'formatters': {
          'standard': {
              'format': ('%(asctime)s %(name)-15s '
                         '%(levelname)-8s %(message)s')}},

      'handlers': {'netlog': {'backupCount': 10,
                          'class': 'logging.handlers.RotatingFileHandler',
                          'filename': '/logs/network.log',
                          'formatter': 'standard',
                          'level': 'INFO',
                          'maxBytes': 1000000},
                   'syslog': {'class': 'logging.handlers.SysLogHandler',
                              'formatter': 'standard',
                              'level': 'ERROR'}},

      # Specify all the subordinate loggers
      'loggers': {
                  'network': {
                              'handlers': ['netlog']
                  }
      },
      # Specify properties of the root logger
      'root': {
               'handlers': ['syslog']
      },
     }

     # Set up configuration
     logging.config.dictConfig(configdict)

     # As an example, log two error messages
     logger = logging.getLogger('/')
     logger.error('Database not found')

     netlogger = logging.getLogger('network')
     netlogger.error('Connection failed')

Three smaller enhancements to the *note logging: 7b. module, all
implemented by Vinay Sajip, are:

   * The *note SysLogHandler: 602. class now supports syslogging over
     TCP. The constructor has a 'socktype' parameter giving the type of
     socket to use, either *note socket.SOCK_DGRAM: 1285. for UDP or
     *note socket.SOCK_STREAM: 1286. for TCP. The default protocol
     remains UDP.

   * *note Logger: af3. instances gained a *note getChild(): 1287.
     method that retrieves a descendant logger using a relative path.
     For example, once you retrieve a logger by doing ‘log =
     getLogger('app')’, calling ‘log.getChild('network.listen')’ is
     equivalent to ‘getLogger('app.network.listen')’.

   * The *note LoggerAdapter: 1288. class gained an *note
     isEnabledFor(): 1289. method that takes a 'level' and returns
     whether the underlying logger would process a message of that level
     of importance.

也參考
......

PEP 391(1) - Dictionary-Based Configuration For Logging

     由 Vinay Sajip 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0391/


File: python.info,  Node: PEP 3106 Dictionary Views,  Next: PEP 3137 The memoryview Object,  Prev: PEP 391 Dictionary-Based Configuration For Logging,  Up: Python 2 7 有什麼新功能

1.15.8 PEP 3106: Dictionary Views
---------------------------------

The dictionary methods *note keys(): 771, *note values(): 772, and *note
items(): 773. are different in Python 3.x.  They return an object called
a 'view' instead of a fully materialized list.

It's not possible to change the return values of *note keys(): 771,
*note values(): 772, and *note items(): 773. in Python 2.7 because too
much code would break.  Instead the 3.x versions were added under the
new names ‘viewkeys()’, ‘viewvalues()’, and ‘viewitems()’.

     >>> d = dict((i*10, chr(65+i)) for i in range(26))
     >>> d
     {0: 'A', 130: 'N', 10: 'B', 140: 'O', 20: ..., 250: 'Z'}
     >>> d.viewkeys()
     dict_keys([0, 130, 10, 140, 20, 150, 30, ..., 250])

Views can be iterated over, but the key and item views also behave like
sets.  The ‘&’ operator performs intersection, and ‘|’ performs a union:

     >>> d1 = dict((i*10, chr(65+i)) for i in range(26))
     >>> d2 = dict((i**.5, i) for i in range(1000))
     >>> d1.viewkeys() & d2.viewkeys()
     set([0.0, 10.0, 20.0, 30.0])
     >>> d1.viewkeys() | range(0, 30)
     set([0, 1, 130, 3, 4, 5, 6, ..., 120, 250])

The view keeps track of the dictionary and its contents change as the
dictionary is modified:

     >>> vk = d.viewkeys()
     >>> vk
     dict_keys([0, 130, 10, ..., 250])
     >>> d[260] = '&'
     >>> vk
     dict_keys([0, 130, 260, 10, ..., 250])

However, note that you can't add or remove keys while you're iterating
over the view:

     >>> for k in vk:
     ...     d[k*2] = k
     ...
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     RuntimeError: dictionary changed size during iteration

You can use the view methods in Python 2.x code, and the 2to3 converter
will change them to the standard *note keys(): 771, *note values(): 772,
and *note items(): 773. methods.

也參考
......

PEP 3106(1) - Revamping dict.keys(), .values() and .items()

     PEP written by Guido van Rossum.  Backported to 2.7 by Alexandre
     Vassalotti; bpo-1967(2).

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3106/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=1967


File: python.info,  Node: PEP 3137 The memoryview Object,  Next: 其他語言更動<13>,  Prev: PEP 3106 Dictionary Views,  Up: Python 2 7 有什麼新功能

1.15.9 PEP 3137: The memoryview Object
--------------------------------------

The *note memoryview: 40f. object provides a view of another object's
memory content that matches the *note bytes: 1a5. type's interface.

     >>> import string
     >>> m = memoryview(string.letters)
     >>> m
     <memory at 0x37f850>
     >>> len(m)           # Returns length of underlying object
     52
     >>> m[0], m[25], m[26]   # Indexing returns one byte
     ('a', 'z', 'A')
     >>> m2 = m[0:26]         # Slicing returns another memoryview
     >>> m2
     <memory at 0x37f080>

The content of the view can be converted to a string of bytes or a list
of integers:

     >>> m2.tobytes()
     'abcdefghijklmnopqrstuvwxyz'
     >>> m2.tolist()
     [97, 98, 99, 100, 101, 102, 103, ... 121, 122]
     >>>

*note memoryview: 40f. objects allow modifying the underlying object if
it's a mutable object.

     >>> m2[0] = 75
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: cannot modify read-only memory
     >>> b = bytearray(string.letters)  # Creating a mutable object
     >>> b
     bytearray(b'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ')
     >>> mb = memoryview(b)
     >>> mb[0] = '*'         # Assign to view, changing the bytearray.
     >>> b[0:5]              # The bytearray has been changed.
     bytearray(b'*bcde')
     >>>

也參考
......

PEP 3137(1) - Immutable Bytes and Mutable Buffer

     PEP written by Guido van Rossum.  Implemented by Travis Oliphant,
     Antoine Pitrou and others.  Backported to 2.7 by Antoine Pitrou;
     bpo-2396(2).

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3137/

   (2) https://bugs.python.org/issue?@action=redirect&bpo=2396


File: python.info,  Node: 其他語言更動<13>,  Next: New and Improved Modules,  Prev: PEP 3137 The memoryview Object,  Up: Python 2 7 有什麼新功能

1.15.10 其他語言更動
--------------------

Some smaller changes made to the core Python language are:

   * The syntax for set literals has been backported from Python 3.x.
     Curly brackets are used to surround the contents of the resulting
     mutable set; set literals are distinguished from dictionaries by
     not containing colons and values.  ‘{}’ continues to represent an
     empty dictionary; use ‘set()’ for an empty set.

          >>> {1, 2, 3, 4, 5}
          set([1, 2, 3, 4, 5])
          >>> set() # empty set
          set([])
          >>> {}    # empty dict
          {}

     Backported by Alexandre Vassalotti; bpo-2335(1).

   * Dictionary and set comprehensions are another feature backported
     from 3.x, generalizing list/generator comprehensions to use the
     literal syntax for sets and dictionaries.

          >>> {x: x*x for x in range(6)}
          {0: 0, 1: 1, 2: 4, 3: 9, 4: 16, 5: 25}
          >>> {('a'*x) for x in range(6)}
          set(['', 'a', 'aa', 'aaa', 'aaaa', 'aaaaa'])

     Backported by Alexandre Vassalotti; bpo-2333(2).

   * The *note with: 577. statement can now use multiple context
     managers in one statement.  Context managers are processed from
     left to right and each one is treated as beginning a new ‘with’
     statement.  This means that:

          with A() as a, B() as b:
              ... suite of statements ...

     is equivalent to:

          with A() as a:
              with B() as b:
                  ... suite of statements ...

     The ‘contextlib.nested()’ function provides a very similar
     function, so it's no longer necessary and has been deprecated.

     (Proposed in ‘https://codereview.appspot.com/53094’; implemented by
     Georg Brandl.)

   * Conversions between floating-point numbers and strings are now
     correctly rounded on most platforms.  These conversions occur in
     many different places: *note str(): 3f2. on floats and complex
     numbers; the *note float: 2c8. and *note complex: 2c9.
     constructors; numeric formatting; serializing and deserializing
     floats and complex numbers using the *note marshal: 80, *note
     pickle: 95. and *note json: 76. modules; parsing of float and
     imaginary literals in Python code; and *note Decimal: 27c.-to-float
     conversion.

     Related to this, the *note repr(): 7a1. of a floating-point number
     'x' now returns a result based on the shortest decimal string
     that's guaranteed to round back to 'x' under correct rounding (with
     round-half-to-even rounding mode).  Previously it gave a string
     based on rounding x to 17 decimal digits.

     The rounding library responsible for this improvement works on
     Windows and on Unix platforms using the gcc, icc, or suncc
     compilers.  There may be a small number of platforms where correct
     operation of this code cannot be guaranteed, so the code is not
     used on such systems.  You can find out which code is being used by
     checking *note sys.float_repr_style: 128d, which will be ‘short’ if
     the new code is in use and ‘legacy’ if it isn't.

     Implemented by Eric Smith and Mark Dickinson, using David Gay's
     ‘dtoa.c’ library; bpo-7117(3).

   * Conversions from long integers and regular integers to floating
     point now round differently, returning the floating-point number
     closest to the number.  This doesn't matter for small integers that
     can be converted exactly, but for large numbers that will
     unavoidably lose precision, Python 2.7 now approximates more
     closely.  For example, Python 2.6 computed the following:

          >>> n = 295147905179352891391
          >>> float(n)
          2.9514790517935283e+20
          >>> n - long(float(n))
          65535L

     Python 2.7's floating-point result is larger, but much closer to
     the true value:

          >>> n = 295147905179352891391
          >>> float(n)
          2.9514790517935289e+20
          >>> n - long(float(n))
          -1L

     （由 Mark Dickinson 實作；bpo-3166(4)。）

     Integer division is also more accurate in its rounding behaviours.
     (Also implemented by Mark Dickinson; bpo-1811(5).)

   * Implicit coercion for complex numbers has been removed; the
     interpreter will no longer ever attempt to call a ‘__coerce__()’
     method on complex objects.  (Removed by Meador Inge and Mark
     Dickinson; bpo-5211(6).)

   * The *note str.format(): 5c7. method now supports automatic
     numbering of the replacement fields.  This makes using *note
     str.format(): 5c7. more closely resemble using ‘%s’ formatting:

          >>> '{}:{}:{}'.format(2009, 04, 'Sunday')
          '2009:4:Sunday'
          >>> '{}:{}:{day}'.format(2009, 4, day='Sunday')
          '2009:4:Sunday'

     The auto-numbering takes the fields from left to right, so the
     first ‘{...}’ specifier will use the first argument to *note
     str.format(): 5c7, the next specifier will use the next argument,
     and so on.  You can't mix auto-numbering and explicit numbering -
     either number all of your specifier fields or none of them - but
     you can mix auto-numbering and named fields, as in the second
     example above.  (Contributed by Eric Smith; bpo-5237(7).)

     Complex numbers now correctly support usage with *note format():
     5c3, and default to being right-aligned.  Specifying a precision or
     comma-separation applies to both the real and imaginary parts of
     the number, but a specified field width and alignment is applied to
     the whole of the resulting ‘1.5+3j’ output.  (Contributed by Eric
     Smith; bpo-1588(8) and bpo-7988(9).)

     The 'F' format code now always formats its output using uppercase
     characters, so it will now produce 'INF' and 'NAN'. (Contributed by
     Eric Smith; bpo-3382(10).)

     A low-level change: the *note object.__format__(): 5c5. method now
     triggers a *note PendingDeprecationWarning: 86d. if it's passed a
     format string, because the ‘__format__()’ method for *note object:
     a2f. converts the object to a string representation and formats
     that.  Previously the method silently applied the format string to
     the string representation, but that could hide mistakes in Python
     code.  If you're supplying formatting information such as an
     alignment or precision, presumably you're expecting the formatting
     to be applied in some object-specific way.  (Fixed by Eric Smith;
     bpo-7994(11).)

   * The *note int(): 23c. and ‘long()’ types gained a ‘bit_length’
     method that returns the number of bits necessary to represent its
     argument in binary:

          >>> n = 37
          >>> bin(n)
          '0b100101'
          >>> n.bit_length()
          6
          >>> n = 2**123-1
          >>> n.bit_length()
          123
          >>> (n+1).bit_length()
          124

     （由 Fredrik Johansson 和 Victor Stinner 貢獻；bpo-3439(12)。）

   * The *note import: 586. statement will no longer try an absolute
     import if a relative import (e.g.  ‘from .os import sep’) fails.
     This fixes a bug, but could possibly break certain ‘import’
     statements that were only working by accident.  (Fixed by Meador
     Inge; bpo-7902(13).)

   * It's now possible for a subclass of the built-in ‘unicode’ type to
     override the ‘__unicode__()’ method.  (Implemented by Victor
     Stinner; bpo-1583863(14).)

   * The *note bytearray: 4e3. type's *note translate(): 128e. method
     now accepts ‘None’ as its first argument.  (Fixed by Georg Brandl;
     bpo-4759(15).)

   * When using *note @classmethod: 14a. and *note @staticmethod: 358.
     to wrap methods as class or static methods, the wrapper object now
     exposes the wrapped function as their *note __func__: 128f.
     attribute.  (Contributed by Amaury Forgeot d'Arc, after a
     suggestion by George Sakkis; bpo-5982(16).)

   * When a restricted set of attributes were set using ‘__slots__’,
     deleting an unset attribute would not raise *note AttributeError:
     2f6. as you would expect.  Fixed by Benjamin Peterson;
     bpo-7604(17).)

   * Two new encodings are now supported: "cp720", used primarily for
     Arabic text; and "cp858", a variant of CP 850 that adds the euro
     symbol.  (CP720 contributed by Alexander Belchenko and Amaury
     Forgeot d'Arc in bpo-1616979(18); CP858 contributed by Tim Hatch in
     bpo-8016(19).)

   * The ‘file’ object will now set the ‘filename’ attribute on the
     *note IOError: ff5. exception when trying to open a directory on
     POSIX platforms (noted by Jan Kaliszewski; bpo-4764(20)), and now
     explicitly checks for and forbids writing to read-only file objects
     instead of trusting the C library to catch and report the error
     (fixed by Stefan Krah; bpo-5677(21)).

   * The Python tokenizer now translates line endings itself, so the
     *note compile(): 178. built-in function now accepts code using any
     line-ending convention.  Additionally, it no longer requires that
     the code end in a newline.

   * Extra parentheses in function definitions are illegal in Python
     3.x, meaning that you get a syntax error from ‘def f((x)): pass’.
     In Python3-warning mode, Python 2.7 will now warn about this odd
     usage.  (Noted by James Lingard; bpo-7362(22).)

   * It's now possible to create weak references to old-style class
     objects.  New-style classes were always weak-referenceable.  (Fixed
     by Antoine Pitrou; bpo-8268(23).)

   * When a module object is garbage-collected, the module's dictionary
     is now only cleared if no one else is holding a reference to the
     dictionary (bpo-7140(24)).

* Menu:

* Interpreter Changes::
* 最佳化: 最佳化<12>.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=2335

   (2) https://bugs.python.org/issue?@action=redirect&bpo=2333

   (3) https://bugs.python.org/issue?@action=redirect&bpo=7117

   (4) https://bugs.python.org/issue?@action=redirect&bpo=3166

   (5) https://bugs.python.org/issue?@action=redirect&bpo=1811

   (6) https://bugs.python.org/issue?@action=redirect&bpo=5211

   (7) https://bugs.python.org/issue?@action=redirect&bpo=5237

   (8) https://bugs.python.org/issue?@action=redirect&bpo=1588

   (9) https://bugs.python.org/issue?@action=redirect&bpo=7988

   (10) https://bugs.python.org/issue?@action=redirect&bpo=3382

   (11) https://bugs.python.org/issue?@action=redirect&bpo=7994

   (12) https://bugs.python.org/issue?@action=redirect&bpo=3439

   (13) https://bugs.python.org/issue?@action=redirect&bpo=7902

   (14) https://bugs.python.org/issue?@action=redirect&bpo=1583863

   (15) https://bugs.python.org/issue?@action=redirect&bpo=4759

   (16) https://bugs.python.org/issue?@action=redirect&bpo=5982

   (17) https://bugs.python.org/issue?@action=redirect&bpo=7604

   (18) https://bugs.python.org/issue?@action=redirect&bpo=1616979

   (19) https://bugs.python.org/issue?@action=redirect&bpo=8016

   (20) https://bugs.python.org/issue?@action=redirect&bpo=4764

   (21) https://bugs.python.org/issue?@action=redirect&bpo=5677

   (22) https://bugs.python.org/issue?@action=redirect&bpo=7362

   (23) https://bugs.python.org/issue?@action=redirect&bpo=8268

   (24) https://bugs.python.org/issue?@action=redirect&bpo=7140


File: python.info,  Node: Interpreter Changes,  Next: 最佳化<12>,  Up: 其他語言更動<13>

1.15.10.1 Interpreter Changes
.............................

A new environment variable, *note PYTHONWARNINGS: b51, allows
controlling warnings.  It should be set to a string containing warning
settings, equivalent to those used with the *note -W: 86c. switch,
separated by commas.  (Contributed by Brian Curtin; bpo-7301(1).)

For example, the following setting will print warnings every time they
occur, but turn warnings from the *note Cookie: 67. module into an
error.  (The exact syntax for setting an environment variable varies
across operating systems and shells.)

     export PYTHONWARNINGS=all,error:::Cookie:0

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=7301


File: python.info,  Node: 最佳化<12>,  Prev: Interpreter Changes,  Up: 其他語言更動<13>

1.15.10.2 最佳化
................

Several performance enhancements have been added:

   * A new opcode was added to perform the initial setup for *note with:
     577. statements, looking up the *note __enter__(): 56c. and *note
     __exit__(): 1293. methods.  (Contributed by Benjamin Peterson.)

   * The garbage collector now performs better for one common usage
     pattern: when many objects are being allocated without deallocating
     any of them.  This would previously take quadratic time for garbage
     collection, but now the number of full garbage collections is
     reduced as the number of objects on the heap grows.  The new logic
     only performs a full garbage collection pass when the middle
     generation has been collected 10 times and when the number of
     survivor objects from the middle generation exceeds 10% of the
     number of objects in the oldest generation.  (Suggested by Martin
     von Löwis and implemented by Antoine Pitrou; bpo-4074(1).)

   * The garbage collector tries to avoid tracking simple containers
     which can't be part of a cycle.  In Python 2.7, this is now true
     for tuples and dicts containing atomic types (such as ints,
     strings, etc.).  Transitively, a dict containing tuples of atomic
     types won't be tracked either.  This helps reduce the cost of each
     garbage collection by decreasing the number of objects to be
     considered and traversed by the collector.  (Contributed by Antoine
     Pitrou; bpo-4688(2).)

   * Long integers are now stored internally either in base ‘2**15’ or
     in base ‘2**30’, the base being determined at build time.
     Previously, they were always stored in base ‘2**15’.  Using base
     ‘2**30’ gives significant performance improvements on 64-bit
     machines, but benchmark results on 32-bit machines have been mixed.
     Therefore, the default is to use base ‘2**30’ on 64-bit machines
     and base ‘2**15’ on 32-bit machines; on Unix, there's a new
     configure option ‘--enable-big-digits’ that can be used to override
     this default.

     Apart from the performance improvements this change should be
     invisible to end users, with one exception: for testing and
     debugging purposes there's a new structseq ‘sys.long_info’ that
     provides information about the internal format, giving the number
     of bits per digit and the size in bytes of the C type used to store
     each digit:

          >>> import sys
          >>> sys.long_info
          sys.long_info(bits_per_digit=30, sizeof_digit=4)

     （由 Mark Dickinson 貢獻；bpo-4258(3)。）

     Another set of changes made long objects a few bytes smaller: 2
     bytes smaller on 32-bit systems and 6 bytes on 64-bit.
     (Contributed by Mark Dickinson; bpo-5260(4).)

   * The division algorithm for long integers has been made faster by
     tightening the inner loop, doing shifts instead of multiplications,
     and fixing an unnecessary extra iteration.  Various benchmarks show
     speedups of between 50% and 150% for long integer divisions and
     modulo operations.  (Contributed by Mark Dickinson; bpo-5512(5).)
     Bitwise operations are also significantly faster (initial patch by
     Gregory Smith; bpo-1087418(6)).

   * The implementation of ‘%’ checks for the left-side operand being a
     Python string and special-cases it; this results in a 1-3%
     performance increase for applications that frequently use ‘%’ with
     strings, such as templating libraries.  (Implemented by Collin
     Winter; bpo-5176(7).)

   * List comprehensions with an ‘if’ condition are compiled into faster
     bytecode.  (Patch by Antoine Pitrou, back-ported to 2.7 by Jeffrey
     Yasskin; bpo-4715(8).)

   * Converting an integer or long integer to a decimal string was made
     faster by special-casing base 10 instead of using a generalized
     conversion function that supports arbitrary bases.  (Patch by
     Gawain Bolton; bpo-6713(9).)

   * The ‘split()’, ‘replace()’, ‘rindex()’, ‘rpartition()’, and
     ‘rsplit()’ methods of string-like types (strings, Unicode strings,
     and *note bytearray: 4e3. objects) now use a fast reverse-search
     algorithm instead of a character-by-character scan.  This is
     sometimes faster by a factor of 10.  (Added by Florent Xicluna;
     bpo-7462(10) and bpo-7622(11).)

   * The *note pickle: 95. and ‘cPickle’ modules now automatically
     intern the strings used for attribute names, reducing memory usage
     of the objects resulting from unpickling.  (Contributed by Jake
     McGuire; bpo-5084(12).)

   * The ‘cPickle’ module now special-cases dictionaries, nearly halving
     the time required to pickle them.  (Contributed by Collin Winter;
     bpo-5670(13).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=4074

   (2) https://bugs.python.org/issue?@action=redirect&bpo=4688

   (3) https://bugs.python.org/issue?@action=redirect&bpo=4258

   (4) https://bugs.python.org/issue?@action=redirect&bpo=5260

   (5) https://bugs.python.org/issue?@action=redirect&bpo=5512

   (6) https://bugs.python.org/issue?@action=redirect&bpo=1087418

   (7) https://bugs.python.org/issue?@action=redirect&bpo=5176

   (8) https://bugs.python.org/issue?@action=redirect&bpo=4715

   (9) https://bugs.python.org/issue?@action=redirect&bpo=6713

   (10) https://bugs.python.org/issue?@action=redirect&bpo=7462

   (11) https://bugs.python.org/issue?@action=redirect&bpo=7622

   (12) https://bugs.python.org/issue?@action=redirect&bpo=5084

   (13) https://bugs.python.org/issue?@action=redirect&bpo=5670


File: python.info,  Node: New and Improved Modules,  Next: Build and C API Changes<7>,  Prev: 其他語言更動<13>,  Up: Python 2 7 有什麼新功能

1.15.11 New and Improved Modules
--------------------------------

As in every release, Python's standard library received a number of
enhancements and bug fixes.  Here's a partial list of the most notable
changes, sorted alphabetically by module name.  Consult the ‘Misc/NEWS’
file in the source tree for a more complete list of changes, or look
through the Subversion logs for all the details.

   * The *note bdb: b. module's base debugging class *note Bdb: 1295.
     gained a feature for skipping modules.  The constructor now takes
     an iterable containing glob-style patterns such as ‘django.*’; the
     debugger will not step into stack frames from a module that matches
     one of these patterns.  (Contributed by Maru Newby after a
     suggestion by Senthil Kumaran; bpo-5142(1).)

   * The *note binascii: c. module now supports the buffer API, so it
     can be used with *note memoryview: 40f. instances and other similar
     buffer objects.  (Backported from 3.x by Florent Xicluna;
     bpo-7703(2).)

   * Updated module: the ‘bsddb’ module has been updated from
     4.7.2devel9 to version 4.8.4 of the pybsddb package(3).  The new
     version features better Python 3.x compatibility, various bug
     fixes, and adds several new BerkeleyDB flags and methods.  (Updated
     by Jesús Cea Avión; bpo-8156(4).  The pybsddb changelog can be read
     at ‘https://hg.jcea.es/pybsddb/file/tip/ChangeLog’.)

   * The *note bz2: f. module's *note BZ2File: 80b. now supports the
     context management protocol, so you can write ‘with
     bz2.BZ2File(...) as f:’.  (Contributed by Hagen Fürstenau;
     bpo-3860(5).)

   * New class: the *note Counter: 1033. class in the *note collections:
     16. module is useful for tallying data.  *note Counter: 1033.
     instances behave mostly like dictionaries but return zero for
     missing keys instead of raising a *note KeyError: 2fb.:

          >>> from collections import Counter
          >>> c = Counter()
          >>> for letter in 'here is a sample of english text':
          ...   c[letter] += 1
          ...
          >>> c
          Counter({' ': 6, 'e': 5, 's': 3, 'a': 2, 'i': 2, 'h': 2,
          'l': 2, 't': 2, 'g': 1, 'f': 1, 'm': 1, 'o': 1, 'n': 1,
          'p': 1, 'r': 1, 'x': 1})
          >>> c['e']
          5
          >>> c['z']
          0

     There are three additional *note Counter: 1033. methods.  *note
     most_common(): 1296. returns the N most common elements and their
     counts.  *note elements(): 1297. returns an iterator over the
     contained elements, repeating each element as many times as its
     count.  *note subtract(): 1176. takes an iterable and subtracts one
     for each element instead of adding; if the argument is a dictionary
     or another ‘Counter’, the counts are subtracted.

          >>> c.most_common(5)
          [(' ', 6), ('e', 5), ('s', 3), ('a', 2), ('i', 2)]
          >>> c.elements() ->
             'a', 'a', ' ', ' ', ' ', ' ', ' ', ' ',
             'e', 'e', 'e', 'e', 'e', 'g', 'f', 'i', 'i',
             'h', 'h', 'm', 'l', 'l', 'o', 'n', 'p', 's',
             's', 's', 'r', 't', 't', 'x'
          >>> c['e']
          5
          >>> c.subtract('very heavy on the letter e')
          >>> c['e']    # Count is now lower
          -1

     Contributed by Raymond Hettinger; bpo-1696199(6).

     New class: *note OrderedDict: 57f. is described in the earlier
     section *note PEP 372; Adding an Ordered Dictionary to collections:
     127c.

     New method: The *note deque: 580. data type now has a *note
     count(): 1178. method that returns the number of contained elements
     equal to the supplied argument 'x', and a *note reverse(): 1179.
     method that reverses the elements of the deque in-place.  *note
     deque: 580. also exposes its maximum length as the read-only *note
     maxlen: 1298. attribute.  (Both features added by Raymond
     Hettinger.)

     The *note namedtuple: 1ae. class now has an optional 'rename'
     parameter.  If 'rename' is true, field names that are invalid
     because they've been repeated or aren't legal Python identifiers
     will be renamed to legal names that are derived from the field's
     position within the list of fields:

          >>> from collections import namedtuple
          >>> T = namedtuple('T', ['field1', '$illegal', 'for', 'field2'], rename=True)
          >>> T._fields
          ('field1', '_1', '_2', 'field2')

     (Added by Raymond Hettinger; bpo-1818(7).)

     Finally, the *note Mapping: 86f. abstract base class now returns
     *note NotImplemented: 776. if a mapping is compared to another type
     that isn't a ‘Mapping’.  (Fixed by Daniel Stutzbach; bpo-8729(8).)

   * Constructors for the parsing classes in the *note ConfigParser: 1b.
     module now take an 'allow_no_value' parameter, defaulting to false;
     if true, options without values will be allowed.  For example:

          >>> import ConfigParser, StringIO
          >>> sample_config = """
          ... [mysqld]
          ... user = mysql
          ... pid-file = /var/run/mysqld/mysqld.pid
          ... skip-bdb
          ... """
          >>> config = ConfigParser.RawConfigParser(allow_no_value=True)
          >>> config.readfp(StringIO.StringIO(sample_config))
          >>> config.get('mysqld', 'user')
          'mysql'
          >>> print config.get('mysqld', 'skip-bdb')
          None
          >>> print config.get('mysqld', 'unknown')
          Traceback (most recent call last):
            ...
          NoOptionError: No option 'unknown' in section: 'mysqld'

     （由 Mats Kindahl 貢獻；bpo-7005(9)。）

   * Deprecated function: ‘contextlib.nested()’, which allows handling
     more than one context manager with a single *note with: 577.
     statement, has been deprecated, because the ‘with’ statement now
     supports multiple context managers.

   * The *note cookielib: 66. module now ignores cookies that have an
     invalid version field, one that doesn't contain an integer value.
     (Fixed by John J. Lee; bpo-3924(10).)

   * The *note copy: 1e. module's *note deepcopy(): b12. function will
     now correctly copy bound instance methods.  (Implemented by Robert
     Collins; bpo-1515(11).)

   * The *note ctypes: 22. module now always converts ‘None’ to a C
     ‘NULL’ pointer for arguments declared as pointers.  (Changed by
     Thomas Heller; bpo-4606(12).)  The underlying libffi library(13)
     has been updated to version 3.0.9, containing various fixes for
     different platforms.  (Updated by Matthias Klose; bpo-8142(14).)

   * New method: the *note datetime: 28. module's *note timedelta: 973.
     class gained a *note total_seconds(): 1299. method that returns the
     number of seconds in the duration.  (Contributed by Brian Quinlan;
     bpo-5788(15).)

   * New method: the *note Decimal: 27c. class gained a *note
     from_float(): 119c. class method that performs an exact conversion
     of a floating-point number to a ‘Decimal’.  This exact conversion
     strives for the closest decimal approximation to the floating-point
     representation's value; the resulting decimal value will therefore
     still include the inaccuracy, if any.  For example,
     ‘Decimal.from_float(0.1)’ returns
     ‘Decimal('0.1000000000000000055511151231257827021181583404541015625')’.
     (Implemented by Raymond Hettinger; bpo-4796(16).)

     Comparing instances of *note Decimal: 27c. with floating-point
     numbers now produces sensible results based on the numeric values
     of the operands.  Previously such comparisons would fall back to
     Python's default rules for comparing objects, which produced
     arbitrary results based on their type.  Note that you still cannot
     combine ‘Decimal’ and floating point in other operations such as
     addition, since you should be explicitly choosing how to convert
     between float and ‘Decimal’.  (Fixed by Mark Dickinson;
     bpo-2531(17).)

     The constructor for *note Decimal: 27c. now accepts floating-point
     numbers (added by Raymond Hettinger; bpo-8257(18)) and non-European
     Unicode characters such as Arabic-Indic digits (contributed by Mark
     Dickinson; bpo-6595(19)).

     Most of the methods of the *note Context: 1049. class now accept
     integers as well as *note Decimal: 27c. instances; the only
     exceptions are the *note canonical(): 129a. and *note
     is_canonical(): 129b. methods.  (Patch by Juan José Conti;
     bpo-7633(20).)

     When using *note Decimal: 27c. instances with a string's *note
     format(): 5c7. method, the default alignment was previously
     left-alignment.  This has been changed to right-alignment, which is
     more sensible for numeric types.  (Changed by Mark Dickinson;
     bpo-6857(21).)

     Comparisons involving a signaling NaN value (or ‘sNAN’) now signal
     *note InvalidOperation: 1044. instead of silently returning a true
     or false value depending on the comparison operator.  Quiet NaN
     values (or ‘NaN’) are now hashable.  (Fixed by Mark Dickinson;
     bpo-7279(22).)

   * The *note difflib: 2f. module now produces output that is more
     compatible with modern ‘diff’/‘patch’ tools through one small
     change, using a tab character instead of spaces as a separator in
     the header giving the filename.  (Fixed by Anatoly Techtonik;
     bpo-7585(23).)

   * The Distutils ‘sdist’ command now always regenerates the ‘MANIFEST’
     file, since even if the ‘MANIFEST.in’ or ‘setup.py’ files haven't
     been modified, the user might have created some new files that
     should be included.  (Fixed by Tarek Ziadé; bpo-8688(24).)

   * The *note doctest: 31. module's *note IGNORE_EXCEPTION_DETAIL:
     129c. flag will now ignore the name of the module containing the
     exception being tested.  (Patch by Lennart Regebro; bpo-7490(25).)

   * The *note email: 32. module's *note Message: 261. class will now
     accept a Unicode-valued payload, automatically converting the
     payload to the encoding specified by ‘output_charset’.  (Added by
     R.  David Murray; bpo-1368247(26).)

   * The *note Fraction: 1c7. class now accepts a single float or *note
     Decimal: 27c. instance, or two rational numbers, as arguments to
     its constructor.  (Implemented by Mark Dickinson; rationals added
     in bpo-5812(27), and float/decimal in bpo-8294(28).)

     Ordering comparisons (‘<’, ‘<=’, ‘>’, ‘>=’) between fractions and
     complex numbers now raise a *note TypeError: 4dd.  This fixes an
     oversight, making the *note Fraction: 1c7. match the other numeric
     types.

   * New class: *note FTP_TLS: 8a0. in the *note ftplib: 54. module
     provides secure FTP connections using TLS encapsulation of
     authentication as well as subsequent control and data transfers.
     (Contributed by Giampaolo Rodola; bpo-2054(29).)

     The *note storbinary(): 129d. method for binary uploads can now
     restart uploads thanks to an added 'rest' parameter (patch by Pablo
     Mouzo; bpo-6845(30).)

   * New class decorator: *note total_ordering(): ee6. in the *note
     functools: 55. module takes a class that defines an *note __eq__():
     a9d. method and one of *note __lt__(): 129e, *note __le__(): 129f,
     *note __gt__(): 12a0, or *note __ge__(): 12a1, and generates the
     missing comparison methods.  Since the ‘__cmp__()’ method is being
     deprecated in Python 3.x, this decorator makes it easier to define
     ordered classes.  (Added by Raymond Hettinger; bpo-5479(31).)

     New function: *note cmp_to_key(): 1172. will take an old-style
     comparison function that expects two arguments and return a new
     callable that can be used as the 'key' parameter to functions such
     as *note sorted(): b75, *note min(): eac. and *note max(): ead,
     etc.  The primary intended use is to help with making code
     compatible with Python 3.x.  (Added by Raymond Hettinger.)

   * New function: the *note gc: 56. module's *note is_tracked(): 12a2.
     returns true if a given instance is tracked by the garbage
     collector, false otherwise.  (Contributed by Antoine Pitrou;
     bpo-4688(32).)

   * The *note gzip: 5d. module's *note GzipFile: 354. now supports the
     context management protocol, so you can write ‘with
     gzip.GzipFile(...) as f:’ (contributed by Hagen Fürstenau;
     bpo-3860(33)), and it now implements the *note io.BufferedIOBase:
     63a. ABC, so you can wrap it with *note io.BufferedReader: 11a6.
     for faster processing (contributed by Nir Aides; bpo-7471(34)).
     It's also now possible to override the modification time recorded
     in a gzipped file by providing an optional timestamp to the
     constructor.  (Contributed by Jacques Frechet; bpo-4272(35).)

     Files in gzip format can be padded with trailing zero bytes; the
     *note gzip: 5d. module will now consume these trailing bytes.
     (Fixed by Tadek Pietraszek and Brian Curtin; bpo-2846(36).)

   * New attribute: the *note hashlib: 5e. module now has an
     ‘algorithms’ attribute containing a tuple naming the supported
     algorithms.  In Python 2.7, ‘hashlib.algorithms’ contains ‘('md5',
     'sha1', 'sha224', 'sha256', 'sha384', 'sha512')’.  (Contributed by
     Carl Chenet; bpo-7418(37).)

   * The default *note HTTPResponse: 1068. class used by the *note
     httplib: 64. module now supports buffering, resulting in much
     faster reading of HTTP responses.  (Contributed by Kristján Valur
     Jónsson; bpo-4879(38).)

     The *note HTTPConnection: ae4. and *note HTTPSConnection: ae5.
     classes now support a 'source_address' parameter, a ‘(host, port)’
     2-tuple giving the source address that will be used for the
     connection.  (Contributed by Eldon Ziegler; bpo-3972(39).)

   * The ‘ihooks’ module now supports relative imports.  Note that
     ‘ihooks’ is an older module for customizing imports, superseded by
     the ‘imputil’ module added in Python 2.0.  (Relative import support
     added by Neil Schemenauer.)

   * The *note imaplib: 6a. module now supports IPv6 addresses.
     (Contributed by Derek Morr; bpo-1655(40).)

   * New function: the *note inspect: 72. module's *note getcallargs():
     e5f. takes a callable and its positional and keyword arguments, and
     figures out which of the callable's parameters will receive each
     argument, returning a dictionary mapping argument names to their
     values.  For example:

          >>> from inspect import getcallargs
          >>> def f(a, b=1, *pos, **named):
          ...     pass
          ...
          >>> getcallargs(f, 1, 2, 3)
          {'a': 1, 'b': 2, 'pos': (3,), 'named': {}}
          >>> getcallargs(f, a=2, x=4)
          {'a': 2, 'b': 1, 'pos': (), 'named': {'x': 4}}
          >>> getcallargs(f)
          Traceback (most recent call last):
          ...
          TypeError: f() takes at least 1 argument (0 given)

     Contributed by George Sakkis; bpo-3135(41).

   * Updated module: The *note io: 73. library has been upgraded to the
     version shipped with Python 3.1.  For 3.1, the I/O library was
     entirely rewritten in C and is 2 to 20 times faster depending on
     the task being performed.  The original Python version was renamed
     to the ‘_pyio’ module.

     One minor resulting change: the *note io.TextIOBase: 63b. class now
     has an *note errors: 12a3. attribute giving the error setting used
     for encoding and decoding errors (one of ‘'strict'’, ‘'replace'’,
     ‘'ignore'’).

     The *note io.FileIO: 12a4. class now raises an *note OSError: 350.
     when passed an invalid file descriptor.  (Implemented by Benjamin
     Peterson; bpo-4991(42).)  The *note truncate(): 12a5. method now
     preserves the file position; previously it would change the file
     position to the end of the new file.  (Fixed by Pascal Chambon;
     bpo-6939(43).)

   * New function: ‘itertools.compress(data, selectors)’ takes two
     iterators.  Elements of 'data' are returned if the corresponding
     value in 'selectors' is true:

          itertools.compress('ABCDEF', [1,0,1,0,1,1]) =>
            A, C, E, F

     New function: ‘itertools.combinations_with_replacement(iter, r)’
     returns all the possible 'r'-length combinations of elements from
     the iterable 'iter'.  Unlike *note combinations(): 12a6, individual
     elements can be repeated in the generated combinations:

          itertools.combinations_with_replacement('abc', 2) =>
            ('a', 'a'), ('a', 'b'), ('a', 'c'),
            ('b', 'b'), ('b', 'c'), ('c', 'c')

     Note that elements are treated as unique depending on their
     position in the input, not their actual values.

     The *note itertools.count(): 121b. function now has a 'step'
     argument that allows incrementing by values other than 1.  *note
     count(): 121b. also now allows keyword arguments, and using
     non-integer values such as floats or *note Decimal: 27c. instances.
     (Implemented by Raymond Hettinger; bpo-5032(44).)

     *note itertools.combinations(): 12a6. and *note
     itertools.product(): 12a7. previously raised *note ValueError: 1e7.
     for values of 'r' larger than the input iterable.  This was deemed
     a specification error, so they now return an empty iterator.
     (Fixed by Raymond Hettinger; bpo-4816(45).)

   * Updated module: The *note json: 76. module was upgraded to version
     2.0.9 of the simplejson package, which includes a C extension that
     makes encoding and decoding faster.  (Contributed by Bob Ippolito;
     bpo-4136(46).)

     To support the new *note collections.OrderedDict: 57f. type, *note
     json.load(): c5b. now has an optional 'object_pairs_hook' parameter
     that will be called with any object literal that decodes to a list
     of pairs.  (Contributed by Raymond Hettinger; bpo-5381(47).)

   * The *note mailbox: 7f. module's *note Maildir: 353. class now
     records the timestamp on the directories it reads, and only
     re-reads them if the modification time has subsequently changed.
     This improves performance by avoiding unneeded directory scans.
     (Fixed by A.M. Kuchling and Antoine Pitrou; bpo-1607951(48),
     bpo-6896(49).)

   * New functions: the *note math: 81. module gained *note erf(): b7f.
     and *note erfc(): b80. for the error function and the complementary
     error function, *note expm1(): 1184. which computes ‘e**x - 1’ with
     more precision than using *note exp(): 12a8. and subtracting 1,
     *note gamma(): 1185. for the Gamma function, and *note lgamma():
     1186. for the natural log of the Gamma function.  (Contributed by
     Mark Dickinson and nirinA raseliarison; bpo-3366(50).)

   * The *note multiprocessing: 86. module's ‘Manager*’ classes can now
     be passed a callable that will be called whenever a subprocess is
     started, along with a set of arguments that will be passed to the
     callable.  (Contributed by lekma; bpo-5585(51).)

     The *note Pool: f0e. class, which controls a pool of worker
     processes, now has an optional 'maxtasksperchild' parameter.
     Worker processes will perform the specified number of tasks and
     then exit, causing the ‘Pool’ to start a new worker.  This is
     useful if tasks may leak memory or other resources, or if some
     tasks will cause the worker to become very large.  (Contributed by
     Charles Cazabon; bpo-6963(52).)

   * The ‘nntplib’ module now supports IPv6 addresses.  (Contributed by
     Derek Morr; bpo-1664(53).)

   * New functions: the *note os: 91. module wraps the following POSIX
     system calls: *note getresgid(): 12a9. and *note getresuid(): 12aa,
     which return the real, effective, and saved GIDs and UIDs; *note
     setresgid(): 12ab. and *note setresuid(): 12ac, which set real,
     effective, and saved GIDs and UIDs to new values; *note
     initgroups(): 12ad, which initialize the group access list for the
     current process.  (GID/UID functions contributed by Travis H.;
     bpo-6508(54).  Support for initgroups added by Jean-Paul Calderone;
     bpo-7333(55).)

     The *note os.fork(): 17b. function now re-initializes the import
     lock in the child process; this fixes problems on Solaris when
     *note fork(): 17b. is called from a thread.  (Fixed by Zsolt
     Cserna; bpo-7242(56).)

   * In the *note os.path: 92. module, the *note normpath(): 12ae. and
     *note abspath(): 12af. functions now preserve Unicode; if their
     input path is a Unicode string, the return value is also a Unicode
     string.  (*note normpath(): 12ae. fixed by Matt Giuca in
     bpo-5827(57); *note abspath(): 12af. fixed by Ezio Melotti in
     bpo-3426(58).)

   * The *note pydoc: a3. module now has help for the various symbols
     that Python uses.  You can now do ‘help('<<')’ or ‘help('@')’, for
     example.  (Contributed by David Laban; bpo-4739(59).)

   * The *note re: a7. module's *note split(): 282, *note sub(): 283,
     and *note subn(): 284. now accept an optional 'flags' argument, for
     consistency with the other functions in the module.  (Added by
     Gregory P. Smith.)

   * New function: *note run_path(): 164. in the *note runpy: ac. module
     will execute the code at a provided 'path' argument.  'path' can be
     the path of a Python source file (‘example.py’), a compiled
     bytecode file (‘example.pyc’), a directory (‘./package/’), or a zip
     archive (‘example.zip’).  If a directory or zip path is provided,
     it will be added to the front of ‘sys.path’ and the module *note
     __main__: 1. will be imported.  It's expected that the directory or
     zip contains a ‘__main__.py’; if it doesn't, some other
     ‘__main__.py’ might be imported from a location later in
     ‘sys.path’.  This makes more of the machinery of *note runpy: ac.
     available to scripts that want to mimic the way Python's command
     line processes an explicit path name.  (Added by Nick Coghlan;
     bpo-6816(60).)

   * New function: in the *note shutil: b3. module, *note
     make_archive(): 45a. takes a filename, archive type (zip or
     tar-format), and a directory path, and creates an archive
     containing the directory's contents.  (Added by Tarek Ziadé.)

     *note shutil: b3.'s *note copyfile(): 9fc. and *note copytree():
     9cd. functions now raise a ‘SpecialFileError’ exception when asked
     to copy a named pipe.  Previously the code would treat named pipes
     like a regular file by opening them for reading, and this would
     block indefinitely.  (Fixed by Antoine Pitrou; bpo-3002(61).)

   * The *note signal: b4. module no longer re-installs the signal
     handler unless this is truly necessary, which fixes a bug that
     could make it impossible to catch the EINTR signal robustly.
     (Fixed by Charles-Francois Natali; bpo-8354(62).)

   * New functions: in the *note site: b5. module, three new functions
     return various site- and user-specific paths.  *note
     getsitepackages(): 11d6. returns a list containing all global
     site-packages directories, *note getusersitepackages(): 11d8.
     returns the path of the user's site-packages directory, and *note
     getuserbase(): 11d7. returns the value of the *note USER_BASE:
     12b0. environment variable, giving the path to a directory that can
     be used to store data.  (Contributed by Tarek Ziadé; bpo-6693(63).)

     The *note site: b5. module now reports exceptions occurring when
     the *note sitecustomize: b6. module is imported, and will no longer
     catch and swallow the *note KeyboardInterrupt: 975. exception.
     (Fixed by Victor Stinner; bpo-3137(64).)

   * The *note create_connection(): 618. function gained a
     'source_address' parameter, a ‘(host, port)’ 2-tuple giving the
     source address that will be used for the connection.  (Contributed
     by Eldon Ziegler; bpo-3972(65).)

     The *note recv_into(): 12b1. and *note recvfrom_into(): 12b2.
     methods will now write into objects that support the buffer API,
     most usefully the *note bytearray: 4e3. and *note memoryview: 40f.
     objects.  (Implemented by Antoine Pitrou; bpo-8104(66).)

   * The *note SocketServer: b9. module's *note TCPServer: 12b3. class
     now supports socket timeouts and disabling the Nagle algorithm.
     The ‘disable_nagle_algorithm’ class attribute defaults to ‘False’;
     if overridden to be true, new request connections will have the
     TCP_NODELAY option set to prevent buffering many small sends into a
     single TCP packet.  The *note timeout: 12b4. class attribute can
     hold a timeout in seconds that will be applied to the request
     socket; if no request is received within that time, *note
     handle_timeout(): 12b5. will be called and *note handle_request():
     12b6. will return.  (Contributed by Kristján Valur Jónsson;
     bpo-6192(67) and bpo-6267(68).)

   * Updated module: the *note sqlite3: ba. module has been updated to
     version 2.6.0 of the pysqlite package(69).  Version 2.6.0 includes
     a number of bugfixes, and adds the ability to load SQLite
     extensions from shared libraries.  Call the
     ‘enable_load_extension(True)’ method to enable extensions, and then
     call *note load_extension(): 45f. to load a particular shared
     library.  (Updated by Gerhard Häring.)

   * The *note ssl: bb. module's *note SSLSocket: 88f. objects now
     support the buffer API, which fixed a test suite failure (fix by
     Antoine Pitrou; bpo-7133(70)) and automatically set OpenSSL's
     ‘SSL_MODE_AUTO_RETRY’, which will prevent an error code being
     returned from ‘recv()’ operations that trigger an SSL renegotiation
     (fix by Antoine Pitrou; bpo-8222(71)).

     The *note wrap_socket(): 4c9. constructor function now takes a
     'ciphers' argument that's a string listing the encryption
     algorithms to be allowed; the format of the string is described in
     the OpenSSL documentation(72).  (Added by Antoine Pitrou;
     bpo-8322(73).)

     Another change makes the extension load all of OpenSSL's ciphers
     and digest algorithms so that they're all available.  Some SSL
     certificates couldn't be verified, reporting an "unknown algorithm"
     error.  (Reported by Beda Kosata, and fixed by Antoine Pitrou;
     bpo-8484(74).)

     The version of OpenSSL being used is now available as the module
     attributes *note ssl.OPENSSL_VERSION: 11b6. (a string), *note
     ssl.OPENSSL_VERSION_INFO: 11b7. (a 5-tuple), and *note
     ssl.OPENSSL_VERSION_NUMBER: 11b8. (an integer).  (Added by Antoine
     Pitrou; bpo-8321(75).)

   * The *note struct: c0. module will no longer silently ignore
     overflow errors when a value is too large for a particular integer
     format code (one of ‘bBhHiIlLqQ’); it now always raises a *note
     struct.error: 12b7. exception.  (Changed by Mark Dickinson;
     bpo-1523(76).)  The *note pack(): 120f. function will also attempt
     to use *note __index__(): 6c1. to convert and pack non-integers
     before trying the *note __int__(): 6c0. method or reporting an
     error.  (Changed by Mark Dickinson; bpo-8300(77).)

   * New function: the *note subprocess: c1. module's *note
     check_output(): f64. runs a command with a specified set of
     arguments and returns the command's output as a string when the
     command runs without error, or raises a *note CalledProcessError:
     12b8. exception otherwise.

          >>> subprocess.check_output(['df', '-h', '.'])
          'Filesystem     Size   Used  Avail Capacity  Mounted on\n
          /dev/disk0s2    52G    49G   3.0G    94%    /\n'

          >>> subprocess.check_output(['df', '-h', '/bogus'])
            ...
          subprocess.CalledProcessError: Command '['df', '-h', '/bogus']' returned non-zero exit status 1

     （由 Gregory P. Smith 所貢獻。）

     The *note subprocess: c1. module will now retry its internal system
     calls on receiving an *note EINTR: d2d. signal.  (Reported by
     several people; final patch by Gregory P. Smith in
     bpo-1068268(78).)

   * New function: *note is_declared_global(): 12b9. in the *note
     symtable: c2. module returns true for variables that are explicitly
     declared to be global, false for ones that are implicitly global.
     (Contributed by Jeremy Hylton.)

   * The *note syslog: c6. module will now use the value of
     ‘sys.argv[0]’ as the identifier instead of the previous default
     value of ‘'python'’.  (Changed by Sean Reifschneider;
     bpo-8451(79).)

   * The *note sys.version_info: 645. value is now a named tuple, with
     attributes named ‘major’, ‘minor’, ‘micro’, ‘releaselevel’, and
     ‘serial’.  (Contributed by Ross Light; bpo-4285(80).)

     *note sys.getwindowsversion(): c8e. also returns a named tuple,
     with attributes named ‘major’, ‘minor’, ‘build’, ‘platform’,
     ‘service_pack’, ‘service_pack_major’, ‘service_pack_minor’,
     ‘suite_mask’, and ‘product_type’.  (Contributed by Brian Curtin;
     bpo-7766(81).)

   * The *note tarfile: c8. module's default error handling has changed,
     to no longer suppress fatal errors.  The default error level was
     previously 0, which meant that errors would only result in a
     message being written to the debug log, but because the debug log
     is not activated by default, these errors go unnoticed.  The
     default error level is now 1, which raises an exception if there's
     an error.  (Changed by Lars Gustäbel; bpo-7357(82).)

     *note tarfile: c8. now supports filtering the *note TarInfo: 11a8.
     objects being added to a tar file.  When you call *note add(): b9a,
     you may supply an optional 'filter' argument that's a callable.
     The 'filter' callable will be passed the *note TarInfo: 11a8. for
     every file being added, and can modify and return it.  If the
     callable returns ‘None’, the file will be excluded from the
     resulting archive.  This is more powerful than the existing
     'exclude' argument, which has therefore been deprecated.  (Added by
     Lars Gustäbel; bpo-6856(83).)  The *note TarFile: 290. class also
     now supports the context management protocol.  (Added by Lars
     Gustäbel; bpo-7232(84).)

   * The *note wait(): 12ba. method of the *note threading.Event: 10f1.
     class now returns the internal flag on exit.  This means the method
     will usually return true because *note wait(): 12ba. is supposed to
     block until the internal flag becomes true.  The return value will
     only be false if a timeout was provided and the operation timed
     out.  (Contributed by Tim Lesher; bpo-1674032(85).)

   * The Unicode database provided by the *note unicodedata: ee. module
     is now used internally to determine which characters are numeric,
     whitespace, or represent line breaks.  The database also includes
     information from the ‘Unihan.txt’ data file (patch by Anders
     Chrigström and Amaury Forgeot d'Arc; bpo-1571184(86)) and has been
     updated to version 5.2.0 (updated by Florent Xicluna;
     bpo-8024(87)).

   * The *note urlparse: f3. module's *note urlsplit(): ce6. now handles
     unknown URL schemes in a fashion compliant with RFC 3986(88): if
     the URL is of the form ‘"<something>://..."’, the text before the
     ‘://’ is treated as the scheme, even if it's a made-up scheme that
     the module doesn't know about.  This change may break code that
     worked around the old behaviour.  For example, Python 2.6.4 or 2.5
     will return the following:

          >>> import urlparse
          >>> urlparse.urlsplit('invented://host/filename?query')
          ('invented', '', '//host/filename?query', '', '')

     Python 2.7 (and Python 2.6.5) will return:

          >>> import urlparse
          >>> urlparse.urlsplit('invented://host/filename?query')
          ('invented', 'host', '/filename?query', '', '')

     (Python 2.7 actually produces slightly different output, since it
     returns a named tuple instead of a standard tuple.)

     The *note urlparse: f3. module also supports IPv6 literal addresses
     as defined by RFC 2732(89) (contributed by Senthil Kumaran;
     bpo-2987(90)).

          >>> urlparse.urlparse('http://[1080::8:800:200C:417A]/foo')
          ParseResult(scheme='http', netloc='[1080::8:800:200C:417A]',
                      path='/foo', params='', query='', fragment='')

   * New class: the *note WeakSet: 581. class in the *note weakref: fc.
     module is a set that only holds weak references to its elements;
     elements will be removed once there are no references pointing to
     them.  (Originally implemented in Python 3.x by Raymond Hettinger,
     and backported to 2.7 by Michael Foord.)

   * The *note xml.etree.ElementTree: 10c. library, no longer escapes
     ampersands and angle brackets when outputting an XML processing
     instruction (which looks like ‘<?xml-stylesheet href="#style1"?>’)
     or comment (which looks like ‘<!-- comment -->’).  (Patch by Neil
     Muller; bpo-2746(91).)

   * The XML-RPC client and server, provided by the *note xmlrpclib:
     114. and *note SimpleXMLRPCServer: 115. modules, have improved
     performance by supporting HTTP/1.1 keep-alive and by optionally
     using gzip encoding to compress the XML being exchanged.  The gzip
     compression is controlled by the ‘encode_threshold’ attribute of
     *note SimpleXMLRPCRequestHandler: 12bb, which contains a size in
     bytes; responses larger than this will be compressed.  (Contributed
     by Kristján Valur Jónsson; bpo-6267(92).)

   * The *note zipfile: 117. module's *note ZipFile: 669. now supports
     the context management protocol, so you can write ‘with
     zipfile.ZipFile(...) as f:’.  (Contributed by Brian Curtin;
     bpo-5511(93).)

     *note zipfile: 117. now also supports archiving empty directories
     and extracts them correctly.  (Fixed by Kuba Wieczorek;
     bpo-4710(94).)  Reading files out of an archive is faster, and
     interleaving *note read(): 12bc. and *note readline(): 12bd. now
     works correctly.  (Contributed by Nir Aides; bpo-7610(95).)

     The *note is_zipfile(): 12be. function now accepts a file object,
     in addition to the path names accepted in earlier versions.
     (Contributed by Gabriel Genellina; bpo-4756(96).)

     The *note writestr(): 12bf. method now has an optional
     'compress_type' parameter that lets you override the default
     compression method specified in the *note ZipFile: 669.
     constructor.  (Contributed by Ronald Oussoren; bpo-6003(97).)

* Menu:

* New module; importlib: New module importlib.
* New module; sysconfig: New module sysconfig.
* ttk; Themed Widgets for Tk: ttk Themed Widgets for Tk.
* Updated module; unittest: Updated module unittest.
* Updated module; ElementTree 1.3: Updated module ElementTree 1 3.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=5142

   (2) https://bugs.python.org/issue?@action=redirect&bpo=7703

   (3) https://www.jcea.es/programacion/pybsddb.htm

   (4) https://bugs.python.org/issue?@action=redirect&bpo=8156

   (5) https://bugs.python.org/issue?@action=redirect&bpo=3860

   (6) https://bugs.python.org/issue?@action=redirect&bpo=1696199

   (7) https://bugs.python.org/issue?@action=redirect&bpo=1818

   (8) https://bugs.python.org/issue?@action=redirect&bpo=8729

   (9) https://bugs.python.org/issue?@action=redirect&bpo=7005

   (10) https://bugs.python.org/issue?@action=redirect&bpo=3924

   (11) https://bugs.python.org/issue?@action=redirect&bpo=1515

   (12) https://bugs.python.org/issue?@action=redirect&bpo=4606

   (13) https://sourceware.org/libffi/

   (14) https://bugs.python.org/issue?@action=redirect&bpo=8142

   (15) https://bugs.python.org/issue?@action=redirect&bpo=5788

   (16) https://bugs.python.org/issue?@action=redirect&bpo=4796

   (17) https://bugs.python.org/issue?@action=redirect&bpo=2531

   (18) https://bugs.python.org/issue?@action=redirect&bpo=8257

   (19) https://bugs.python.org/issue?@action=redirect&bpo=6595

   (20) https://bugs.python.org/issue?@action=redirect&bpo=7633

   (21) https://bugs.python.org/issue?@action=redirect&bpo=6857

   (22) https://bugs.python.org/issue?@action=redirect&bpo=7279

   (23) https://bugs.python.org/issue?@action=redirect&bpo=7585

   (24) https://bugs.python.org/issue?@action=redirect&bpo=8688

   (25) https://bugs.python.org/issue?@action=redirect&bpo=7490

   (26) https://bugs.python.org/issue?@action=redirect&bpo=1368247

   (27) https://bugs.python.org/issue?@action=redirect&bpo=5812

   (28) https://bugs.python.org/issue?@action=redirect&bpo=8294

   (29) https://bugs.python.org/issue?@action=redirect&bpo=2054

   (30) https://bugs.python.org/issue?@action=redirect&bpo=6845

   (31) https://bugs.python.org/issue?@action=redirect&bpo=5479

   (32) https://bugs.python.org/issue?@action=redirect&bpo=4688

   (33) https://bugs.python.org/issue?@action=redirect&bpo=3860

   (34) https://bugs.python.org/issue?@action=redirect&bpo=7471

   (35) https://bugs.python.org/issue?@action=redirect&bpo=4272

   (36) https://bugs.python.org/issue?@action=redirect&bpo=2846

   (37) https://bugs.python.org/issue?@action=redirect&bpo=7418

   (38) https://bugs.python.org/issue?@action=redirect&bpo=4879

   (39) https://bugs.python.org/issue?@action=redirect&bpo=3972

   (40) https://bugs.python.org/issue?@action=redirect&bpo=1655

   (41) https://bugs.python.org/issue?@action=redirect&bpo=3135

   (42) https://bugs.python.org/issue?@action=redirect&bpo=4991

   (43) https://bugs.python.org/issue?@action=redirect&bpo=6939

   (44) https://bugs.python.org/issue?@action=redirect&bpo=5032

   (45) https://bugs.python.org/issue?@action=redirect&bpo=4816

   (46) https://bugs.python.org/issue?@action=redirect&bpo=4136

   (47) https://bugs.python.org/issue?@action=redirect&bpo=5381

   (48) https://bugs.python.org/issue?@action=redirect&bpo=1607951

   (49) https://bugs.python.org/issue?@action=redirect&bpo=6896

   (50) https://bugs.python.org/issue?@action=redirect&bpo=3366

   (51) https://bugs.python.org/issue?@action=redirect&bpo=5585

   (52) https://bugs.python.org/issue?@action=redirect&bpo=6963

   (53) https://bugs.python.org/issue?@action=redirect&bpo=1664

   (54) https://bugs.python.org/issue?@action=redirect&bpo=6508

   (55) https://bugs.python.org/issue?@action=redirect&bpo=7333

   (56) https://bugs.python.org/issue?@action=redirect&bpo=7242

   (57) https://bugs.python.org/issue?@action=redirect&bpo=5827

   (58) https://bugs.python.org/issue?@action=redirect&bpo=3426

   (59) https://bugs.python.org/issue?@action=redirect&bpo=4739

   (60) https://bugs.python.org/issue?@action=redirect&bpo=6816

   (61) https://bugs.python.org/issue?@action=redirect&bpo=3002

   (62) https://bugs.python.org/issue?@action=redirect&bpo=8354

   (63) https://bugs.python.org/issue?@action=redirect&bpo=6693

   (64) https://bugs.python.org/issue?@action=redirect&bpo=3137

   (65) https://bugs.python.org/issue?@action=redirect&bpo=3972

   (66) https://bugs.python.org/issue?@action=redirect&bpo=8104

   (67) https://bugs.python.org/issue?@action=redirect&bpo=6192

   (68) https://bugs.python.org/issue?@action=redirect&bpo=6267

   (69) https://github.com/ghaering/pysqlite

   (70) https://bugs.python.org/issue?@action=redirect&bpo=7133

   (71) https://bugs.python.org/issue?@action=redirect&bpo=8222

   (72) https://www.openssl.org/docs/man1.0.2/man1/ciphers.html

   (73) https://bugs.python.org/issue?@action=redirect&bpo=8322

   (74) https://bugs.python.org/issue?@action=redirect&bpo=8484

   (75) https://bugs.python.org/issue?@action=redirect&bpo=8321

   (76) https://bugs.python.org/issue?@action=redirect&bpo=1523

   (77) https://bugs.python.org/issue?@action=redirect&bpo=8300

   (78) https://bugs.python.org/issue?@action=redirect&bpo=1068268

   (79) https://bugs.python.org/issue?@action=redirect&bpo=8451

   (80) https://bugs.python.org/issue?@action=redirect&bpo=4285

   (81) https://bugs.python.org/issue?@action=redirect&bpo=7766

   (82) https://bugs.python.org/issue?@action=redirect&bpo=7357

   (83) https://bugs.python.org/issue?@action=redirect&bpo=6856

   (84) https://bugs.python.org/issue?@action=redirect&bpo=7232

   (85) https://bugs.python.org/issue?@action=redirect&bpo=1674032

   (86) https://bugs.python.org/issue?@action=redirect&bpo=1571184

   (87) https://bugs.python.org/issue?@action=redirect&bpo=8024

   (88) https://datatracker.ietf.org/doc/html/rfc3986.html

   (89) https://datatracker.ietf.org/doc/html/rfc2732.html

   (90) https://bugs.python.org/issue?@action=redirect&bpo=2987

   (91) https://bugs.python.org/issue?@action=redirect&bpo=2746

   (92) https://bugs.python.org/issue?@action=redirect&bpo=6267

   (93) https://bugs.python.org/issue?@action=redirect&bpo=5511

   (94) https://bugs.python.org/issue?@action=redirect&bpo=4710

   (95) https://bugs.python.org/issue?@action=redirect&bpo=7610

   (96) https://bugs.python.org/issue?@action=redirect&bpo=4756

   (97) https://bugs.python.org/issue?@action=redirect&bpo=6003


File: python.info,  Node: New module importlib,  Next: New module sysconfig,  Up: New and Improved Modules

1.15.11.1 New module: importlib
...............................

Python 3.1 includes the *note importlib: 6b. package, a
re-implementation of the logic underlying Python's *note import: 586.
statement.  *note importlib: 6b. is useful for implementers of Python
interpreters and to users who wish to write new importers that can
participate in the import process.  Python 2.7 doesn't contain the
complete *note importlib: 6b. package, but instead has a tiny subset
that contains a single function, *note import_module(): 4bc.

‘import_module(name, package=None)’ imports a module.  'name' is a
string containing the module or package's name.  It's possible to do
relative imports by providing a string that begins with a ‘.’ character,
such as ‘..utils.errors’.  For relative imports, the 'package' argument
must be provided and is the name of the package that will be used as the
anchor for the relative import.  *note import_module(): 4bc. both
inserts the imported module into ‘sys.modules’ and returns the module
object.

以下是一些範例：

     >>> from importlib import import_module
     >>> anydbm = import_module('anydbm')  # Standard absolute import
     >>> anydbm
     <module 'anydbm' from '/p/python/Lib/anydbm.py'>
     >>> # Relative import
     >>> file_util = import_module('..file_util', 'distutils.command')
     >>> file_util
     <module 'distutils.file_util' from '/python/Lib/distutils/file_util.pyc'>

*note importlib: 6b. was implemented by Brett Cannon and introduced in
Python 3.1.


File: python.info,  Node: New module sysconfig,  Next: ttk Themed Widgets for Tk,  Prev: New module importlib,  Up: New and Improved Modules

1.15.11.2 New module: sysconfig
...............................

The *note sysconfig: c5. module has been pulled out of the Distutils
package, becoming a new top-level module in its own right.  *note
sysconfig: c5. provides functions for getting information about Python's
build process: compiler switches, installation paths, the platform name,
and whether Python is running from its source directory.

Some of the functions in the module are:

   * *note get_config_var(): fce. returns variables from Python's
     Makefile and the ‘pyconfig.h’ file.

   * *note get_config_vars(): fcf. returns a dictionary containing all
     of the configuration variables.

   * *note get_path(): 12c2. returns the configured path for a
     particular type of module: the standard library, site-specific
     modules, platform-specific modules, etc.

   * *note is_python_build(): 2d4. returns true if you're running a
     binary from a Python source tree, and false otherwise.

Consult the *note sysconfig: c5. documentation for more details and for
a complete list of functions.

The Distutils package and *note sysconfig: c5. are now maintained by
Tarek Ziadé, who has also started a Distutils2 package (source
repository at ‘https://hg.python.org/distutils2/’) for developing a
next-generation version of Distutils.


File: python.info,  Node: ttk Themed Widgets for Tk,  Next: Updated module unittest,  Prev: New module sysconfig,  Up: New and Improved Modules

1.15.11.3 ttk: Themed Widgets for Tk
....................................

Tcl/Tk 8.5 includes a set of themed widgets that re-implement basic Tk
widgets but have a more customizable appearance and can therefore more
closely resemble the native platform's widgets.  This widget set was
originally called Tile, but was renamed to Ttk (for "themed Tk") on
being added to Tcl/Tck release 8.5.

To learn more, read the *note ttk: e2. module documentation.  You may
also wish to read the Tcl/Tk manual page describing the Ttk theme
engine, available at
‘https://www.tcl.tk/man/tcl8.5/TkCmd/ttk_intro.html’.  Some screenshots
of the Python/Ttk code in use are at
‘https://code.google.com/archive/p/python-ttk/wikis/Screenshots.wiki’.

The *note tkinter.ttk: e2. module was written by Guilherme Polo and
added in bpo-2983(1).  An alternate version called ‘Tile.py’, written by
Martin Franklin and maintained by Kevin Walzer, was proposed for
inclusion in bpo-2618(2), but the authors argued that Guilherme Polo's
work was more comprehensive.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=2983

   (2) https://bugs.python.org/issue?@action=redirect&bpo=2618


File: python.info,  Node: Updated module unittest,  Next: Updated module ElementTree 1 3,  Prev: ttk Themed Widgets for Tk,  Up: New and Improved Modules

1.15.11.4 Updated module: unittest
..................................

The *note unittest: ef. module was greatly enhanced; many new features
were added.  Most of these features were implemented by Michael Foord,
unless otherwise noted.  The enhanced version of the module is
downloadable separately for use with Python versions 2.4 to 2.6,
packaged as the ‘unittest2’ package, from unittest2(1).

When used from the command line, the module can automatically discover
tests.  It's not as fancy as py.test(2) or nose(3), but provides a
simple way to run tests kept within a set of package directories.  For
example, the following command will search the ‘test/’ subdirectory for
any importable test files named ‘test*.py’:

     python -m unittest discover -s test

Consult the *note unittest: ef. module documentation for more details.
(Developed in bpo-6001(4).)

The *note main(): f86. function supports some other new options:

   * *note -b: 12c6. or ‘--buffer’ will buffer the standard output and
     standard error streams during each test.  If the test passes, any
     resulting output will be discarded; on failure, the buffered output
     will be displayed.

   * *note -c: 12c7. or ‘--catch’ will cause the control-C interrupt to
     be handled more gracefully.  Instead of interrupting the test
     process immediately, the currently running test will be completed
     and then the partial results up to the interruption will be
     reported.  If you're impatient, a second press of control-C will
     cause an immediate interruption.

     This control-C handler tries to avoid causing problems when the
     code being tested or the tests being run have defined a signal
     handler of their own, by noticing that a signal handler was already
     set and calling it.  If this doesn't work for you, there's a *note
     removeHandler(): 12c8. decorator that can be used to mark tests
     that should have the control-C handling disabled.

   * *note -f: 12c9. or ‘--failfast’ makes test execution stop
     immediately when a test fails instead of continuing to execute
     further tests.  (Suggested by Cliff Dyer and implemented by Michael
     Foord; bpo-8074(5).)

The progress messages now show 'x' for expected failures and 'u' for
unexpected successes when run in verbose mode.  (Contributed by Benjamin
Peterson.)

Test cases can raise the *note SkipTest: f87. exception to skip a test
(bpo-1034053(6)).

The error messages for *note assertEqual(): 4cd, *note assertTrue():
4cb, and *note assertFalse(): 4cc. failures now provide more
information.  If you set the *note longMessage: 12ca. attribute of your
*note TestCase: 3f4. classes to true, both the standard error message
and any additional message you provide will be printed for failures.
(Added by Michael Foord; bpo-5663(7).)

The *note assertRaises(): 4d1. method now returns a context handler when
called without providing a callable object to run.  For example, you can
write this:

     with self.assertRaises(KeyError):
         {}['foo']

（由 Antoine Pitrou 實作；bpo-4444(8)。）

Module- and class-level setup and teardown fixtures are now supported.
Modules can contain ‘setUpModule()’ and ‘tearDownModule()’ functions.
Classes can have *note setUpClass(): 9f2. and *note tearDownClass():
12cb. methods that must be defined as class methods (using
‘@classmethod’ or equivalent).  These functions and methods are invoked
when the test runner switches to a test case in a different module or
class.

The methods *note addCleanup(): a24. and *note doCleanups(): 12cc. were
added.  *note addCleanup(): a24. lets you add cleanup functions that
will be called unconditionally (after *note setUp(): 12cd. if *note
setUp(): 12cd. fails, otherwise after *note tearDown(): 12ce.).  This
allows for much simpler resource allocation and deallocation during
tests (bpo-5679(9)).

A number of new methods were added that provide more specialized tests.
Many of these methods were written by Google engineers for use in their
test suites; Gregory P. Smith, Michael Foord, and GvR worked on merging
them into Python's version of *note unittest: ef.

   * *note assertIsNone(): 1222. and *note assertIsNotNone(): 1223. take
     one expression and verify that the result is or is not ‘None’.

   * *note assertIs(): 12cf. and *note assertIsNot(): 12d0. take two
     values and check whether the two values evaluate to the same object
     or not.  (Added by Michael Foord; bpo-2578(10).)

   * *note assertIsInstance(): 12d1. and *note assertNotIsInstance():
     12d2. check whether the resulting object is an instance of a
     particular class, or of one of a tuple of classes.  (Added by Georg
     Brandl; bpo-7031(11).)

   * *note assertGreater(): 12d3, *note assertGreaterEqual(): 12d4,
     *note assertLess(): 12d5, and *note assertLessEqual(): 12d6.
     compare two quantities.

   * *note assertMultiLineEqual(): 12d7. compares two strings, and if
     they're not equal, displays a helpful comparison that highlights
     the differences in the two strings.  This comparison is now used by
     default when Unicode strings are compared with *note assertEqual():
     4cd.

   * *note assertRegexpMatches(): 4d2. and *note
     assertNotRegexpMatches(): 4d4. checks whether the first argument is
     a string matching or not matching the regular expression provided
     as the second argument (bpo-8038(12)).

   * *note assertRaisesRegexp(): 4d3. checks whether a particular
     exception is raised, and then also checks that the string
     representation of the exception matches the provided regular
     expression.

   * *note assertIn(): 12d8. and *note assertNotIn(): 12d9. tests
     whether 'first' is or is not in 'second'.

   * *note assertItemsEqual(): 11c2. tests whether two provided
     sequences contain the same elements.

   * *note assertSetEqual(): 121d. compares whether two sets are equal,
     and only reports the differences between the sets in case of error.

   * Similarly, *note assertListEqual(): 121f. and *note
     assertTupleEqual(): 1220. compare the specified types and explain
     any differences without necessarily printing their full values;
     these methods are now used by default when comparing lists and
     tuples using *note assertEqual(): 4cd.  More generally, *note
     assertSequenceEqual(): 1221. compares two sequences and can
     optionally check whether both sequences are of a particular type.

   * *note assertDictEqual(): 121e. compares two dictionaries and
     reports the differences; it's now used by default when you compare
     two dictionaries using *note assertEqual(): 4cd.
     ‘assertDictContainsSubset()’ checks whether all of the key/value
     pairs in 'first' are found in 'second'.

   * *note assertAlmostEqual(): 4cf. and *note assertNotAlmostEqual():
     4d0. test whether 'first' and 'second' are approximately equal.
     This method can either round their difference to an optionally
     specified number of 'places' (the default is 7) and compare it to
     zero, or require the difference to be smaller than a supplied
     'delta' value.

   * *note loadTestsFromName(): 12da. properly honors the *note
     suiteClass: 12db. attribute of the *note TestLoader: 270.  (Fixed
     by Mark Roddy; bpo-6866(13).)

   * A new hook lets you extend the *note assertEqual(): 4cd. method to
     handle new data types.  The *note addTypeEqualityFunc(): 12dc.
     method takes a type object and a function.  The function will be
     used when both of the objects being compared are of the specified
     type.  This function should compare the two objects and raise an
     exception if they don't match; it's a good idea for the function to
     provide additional information about why the two objects aren't
     matching, much as the new sequence comparison methods do.

*note unittest.main(): f86. now takes an optional ‘exit’ argument.  If
false, *note main(): f86. doesn't call *note sys.exit(): 12dd, allowing
*note main(): f86. to be used from the interactive interpreter.
(Contributed by J. Pablo Fernández; bpo-3379(14).)

*note TestResult: 1100. has new *note startTestRun(): 12de. and *note
stopTestRun(): 12df. methods that are called immediately before and
after a test run.  (Contributed by Robert Collins; bpo-5728(15).)

With all these changes, the ‘unittest.py’ was becoming awkwardly large,
so the module was turned into a package and the code split into several
files (by Benjamin Peterson).  This doesn't affect how the module is
imported or used.

也參考
......

‘https://web.archive.org/web/20210619163128/http://www.voidspace.org.uk/python/articles/unittest2.shtml’

     Describes the new features, how to use them, and the rationale for
     various design decisions.  (By Michael Foord.)

   ---------- Footnotes ----------

   (1) https://pypi.org/project/unittest2/

   (2) https://pytest.org

   (3) https://nose.readthedocs.io/

   (4) https://bugs.python.org/issue?@action=redirect&bpo=6001

   (5) https://bugs.python.org/issue?@action=redirect&bpo=8074

   (6) https://bugs.python.org/issue?@action=redirect&bpo=1034053

   (7) https://bugs.python.org/issue?@action=redirect&bpo=5663

   (8) https://bugs.python.org/issue?@action=redirect&bpo=4444

   (9) https://bugs.python.org/issue?@action=redirect&bpo=5679

   (10) https://bugs.python.org/issue?@action=redirect&bpo=2578

   (11) https://bugs.python.org/issue?@action=redirect&bpo=7031

   (12) https://bugs.python.org/issue?@action=redirect&bpo=8038

   (13) https://bugs.python.org/issue?@action=redirect&bpo=6866

   (14) https://bugs.python.org/issue?@action=redirect&bpo=3379

   (15) https://bugs.python.org/issue?@action=redirect&bpo=5728


File: python.info,  Node: Updated module ElementTree 1 3,  Prev: Updated module unittest,  Up: New and Improved Modules

1.15.11.5 Updated module: ElementTree 1.3
.........................................

The version of the ElementTree library included with Python was updated
to version 1.3.  Some of the new features are:

   * The various parsing functions now take a 'parser' keyword argument
     giving an *note XMLParser: 9f7. instance that will be used.  This
     makes it possible to override the file's internal encoding:

          p = ET.XMLParser(encoding='utf-8')
          t = ET.XML("""<root/>""", parser=p)

     Errors in parsing XML now raise a *note ParseError: 1210.
     exception, whose instances have a ‘position’ attribute containing a
     ('line', 'column') tuple giving the location of the problem.

   * ElementTree's code for converting trees to a string has been
     significantly reworked, making it roughly twice as fast in many
     cases.  The *note ElementTree.write(): f98. and ‘Element.write()’
     methods now have a 'method' parameter that can be "xml" (the
     default), "html", or "text".  HTML mode will output empty elements
     as ‘<empty></empty>’ instead of ‘<empty/>’, and text mode will skip
     over elements and only output the text chunks.  If you set the
     *note tag: 12e2. attribute of an element to ‘None’ but leave its
     children in place, the element will be omitted when the tree is
     written out, so you don't need to do more extensive rearrangement
     to remove a single element.

     Namespace handling has also been improved.  All ‘xmlns:<whatever>’
     declarations are now output on the root element, not scattered
     throughout the resulting XML. You can set the default namespace for
     a tree by setting the ‘default_namespace’ attribute and can
     register new prefixes with *note register_namespace(): 116a.  In
     XML mode, you can use the true/false 'xml_declaration' parameter to
     suppress the XML declaration.

   * New *note Element: 2e2. method: *note extend(): 116b. appends the
     items from a sequence to the element's children.  Elements
     themselves behave like sequences, so it's easy to move children
     from one element to another:

          from xml.etree import ElementTree as ET

          t = ET.XML("""<list>
            <item>1</item> <item>2</item>  <item>3</item>
          </list>""")
          new = ET.XML('<root/>')
          new.extend(t)

          # Outputs <root><item>1</item>...</root>
          print ET.tostring(new)

   * New *note Element: 2e2. method: *note iter(): 12e3. yields the
     children of the element as a generator.  It's also possible to
     write ‘for child in elem:’ to loop over an element's children.  The
     existing method ‘getiterator()’ is now deprecated, as is
     ‘getchildren()’ which constructs and returns a list of children.

   * New *note Element: 2e2. method: *note itertext(): 116d. yields all
     chunks of text that are descendants of the element.  For example:

          t = ET.XML("""<list>
            <item>1</item> <item>2</item>  <item>3</item>
          </list>""")

          # Outputs ['\n  ', '1', ' ', '2', '  ', '3', '\n']
          print list(t.itertext())

   * Deprecated: using an element as a Boolean (i.e., ‘if elem:’) would
     return true if the element had any children, or false if there were
     no children.  This behaviour is confusing - ‘None’ is false, but so
     is a childless element?  - so it will now trigger a *note
     FutureWarning: 357.  In your code, you should be explicit: write
     ‘len(elem) != 0’ if you're interested in the number of children, or
     ‘elem is not None’.

Fredrik Lundh develops ElementTree and produced the 1.3 version; you can
read his article describing 1.3 at
‘https://web.archive.org/web/20200703234532/http://effbot.org/zone/elementtree-13-intro.htm’.
Florent Xicluna updated the version included with Python, after
discussions on python-dev and in bpo-6472(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=6472


File: python.info,  Node: Build and C API Changes<7>,  Next: Other Changes and Fixes,  Prev: New and Improved Modules,  Up: Python 2 7 有什麼新功能

1.15.12 Build and C API Changes
-------------------------------

Changes to Python's build process and to the C API include:

   * The latest release of the GNU Debugger, GDB 7, can be scripted
     using Python(1).  When you begin debugging an executable program P,
     GDB will look for a file named ‘P-gdb.py’ and automatically read
     it.  Dave Malcolm contributed a ‘python-gdb.py’ that adds a number
     of commands useful when debugging Python itself.  For example,
     ‘py-up’ and ‘py-down’ go up or down one Python stack frame, which
     usually corresponds to several C stack frames.  ‘py-print’ prints
     the value of a Python variable, and ‘py-bt’ prints the Python stack
     trace.  (Added as a result of bpo-8032(2).)

   * If you use the ‘.gdbinit’ file provided with Python, the "pyo"
     macro in the 2.7 version now works correctly when the thread being
     debugged doesn't hold the GIL; the macro now acquires it before
     printing.  (Contributed by Victor Stinner; bpo-3632(3).)

   * *note Py_AddPendingCall(): 925. is now thread-safe, letting any
     worker thread submit notifications to the main Python thread.  This
     is particularly useful for asynchronous IO operations.
     (Contributed by Kristján Valur Jónsson; bpo-4293(4).)

   * New function: *note PyCode_NewEmpty(): 12e5. creates an empty code
     object; only the filename, function name, and first line number are
     required.  This is useful for extension modules that are attempting
     to construct a more useful traceback stack.  Previously such
     extensions needed to call ‘PyCode_New()’, which had many more
     arguments.  (Added by Jeffrey Yasskin.)

   * New function: *note PyErr_NewExceptionWithDoc(): 1201. creates a
     new exception class, just as the existing *note
     PyErr_NewException(): 1202. does, but takes an extra ‘char *’
     argument containing the docstring for the new exception class.
     (Added by 'lekma' on the Python bug tracker; bpo-7033(5).)

   * New function: *note PyFrame_GetLineNumber(): 72f. takes a frame
     object and returns the line number that the frame is currently
     executing.  Previously code would need to get the index of the
     bytecode instruction currently executing, and then look up the line
     number corresponding to that address.  (Added by Jeffrey Yasskin.)

   * New functions: *note PyLong_AsLongAndOverflow(): 11ff. and *note
     PyLong_AsLongLongAndOverflow(): 11fe. approximates a Python long
     integer as a C long or long long.  If the number is too large to
     fit into the output type, an 'overflow' flag is set and returned to
     the caller.  (Contributed by Case Van Horsen; bpo-7528(6) and
     bpo-7767(7).)

   * New function: stemming from the rewrite of string-to-float
     conversion, a new *note PyOS_string_to_double(): 122d. function was
     added.  The old ‘PyOS_ascii_strtod()’ and ‘PyOS_ascii_atof()’
     functions are now deprecated.

   * New function: ‘PySys_SetArgvEx()’ sets the value of ‘sys.argv’ and
     can optionally update ‘sys.path’ to include the directory
     containing the script named by ‘sys.argv[0]’ depending on the value
     of an 'updatepath' parameter.

     This function was added to close a security hole for applications
     that embed Python.  The old function, ‘PySys_SetArgv()’, would
     always update ‘sys.path’, and sometimes it would add the current
     directory.  This meant that, if you ran an application embedding
     Python in a directory controlled by someone else, attackers could
     put a Trojan-horse module in the directory (say, a file named
     ‘os.py’) that your application would then import and run.

     If you maintain a C/C++ application that embeds Python, check
     whether you're calling ‘PySys_SetArgv()’ and carefully consider
     whether the application should be using ‘PySys_SetArgvEx()’ with
     'updatepath' set to false.

     Security issue reported as CVE-2008-5983(8); discussed in
     bpo-5753(9), and fixed by Antoine Pitrou.

   * New macros: the Python header files now define the following
     macros: ‘Py_ISALNUM’, ‘Py_ISALPHA’, ‘Py_ISDIGIT’, ‘Py_ISLOWER’,
     ‘Py_ISSPACE’, ‘Py_ISUPPER’, ‘Py_ISXDIGIT’, ‘Py_TOLOWER’, and
     ‘Py_TOUPPER’.  All of these functions are analogous to the C
     standard macros for classifying characters, but ignore the current
     locale setting, because in several places Python needs to analyze
     characters in a locale-independent way.  (Added by Eric Smith;
     bpo-5793(10).)

   * Removed function: ‘PyEval_CallObject()’ is now only available as a
     macro.  A function version was being kept around to preserve ABI
     linking compatibility, but that was in 1997; it can certainly be
     deleted by now.  (Removed by Antoine Pitrou; bpo-8276(11).)

   * New format codes: the ‘PyString_FromFormat()’,
     ‘PyString_FromFormatV()’, and *note PyErr_Format(): e53. functions
     now accept ‘%lld’ and ‘%llu’ format codes for displaying C's long
     long types.  (Contributed by Mark Dickinson; bpo-7228(12).)

   * The complicated interaction between threads and process forking has
     been changed.  Previously, the child process created by *note
     os.fork(): 17b. might fail because the child is created with only a
     single thread running, the thread performing the *note os.fork():
     17b.  If other threads were holding a lock, such as Python's import
     lock, when the fork was performed, the lock would still be marked
     as "held" in the new process.  But in the child process nothing
     would ever release the lock, since the other threads weren't
     replicated, and the child process would no longer be able to
     perform imports.

     Python 2.7 acquires the import lock before performing an *note
     os.fork(): 17b, and will also clean up any locks created using the
     *note threading: d6. module.  C extension modules that have
     internal locks, or that call ‘fork()’ themselves, will not benefit
     from this clean-up.

     (Fixed by Thomas Wouters; bpo-1590864(13).)

   * The *note Py_Finalize(): 12e6. function now calls the internal
     ‘threading._shutdown()’ function; this prevents some exceptions
     from being raised when an interpreter shuts down.  (Patch by Adam
     Olsen; bpo-1722344(14).)

   * When using the *note PyMemberDef: 4f5. structure to define
     attributes of a type, Python will no longer let you try to delete
     or set a ‘T_STRING_INPLACE’ attribute.

   * Global symbols defined by the *note ctypes: 22. module are now
     prefixed with ‘Py’, or with ‘_ctypes’.  (Implemented by Thomas
     Heller; bpo-3102(15).)

   * New configure option: the ‘--with-system-expat’ switch allows
     building the *note pyexpat: 10d. module to use the system Expat
     library.  (Contributed by Arfrever Frehtes Taifersar Arahesis;
     bpo-7609(16).)

   * New configure option: the ‘--with-valgrind’ option will now disable
     the pymalloc allocator, which is difficult for the Valgrind
     memory-error detector to analyze correctly.  Valgrind will
     therefore be better at detecting memory leaks and overruns.
     (Contributed by James Henstridge; bpo-2422(17).)

   * New configure option: you can now supply an empty string to
     ‘--with-dbmliborder=’ in order to disable all of the various DBM
     modules.  (Added by Arfrever Frehtes Taifersar Arahesis;
     bpo-6491(18).)

   * The ‘configure’ script now checks for floating-point rounding bugs
     on certain 32-bit Intel chips and defines a ‘X87_DOUBLE_ROUNDING’
     preprocessor definition.  No code currently uses this definition,
     but it's available if anyone wishes to use it.  (Added by Mark
     Dickinson; bpo-2937(19).)

     ‘configure’ also now sets a ‘LDCXXSHARED’ Makefile variable for
     supporting C++ linking.  (Contributed by Arfrever Frehtes Taifersar
     Arahesis; bpo-1222585(20).)

   * The build process now creates the necessary files for pkg-config
     support.  (Contributed by Clinton Roy; bpo-3585(21).)

   * The build process now supports Subversion 1.7.  (Contributed by
     Arfrever Frehtes Taifersar Arahesis; bpo-6094(22).)

* Menu:

* Capsules::
* Port-Specific Changes; Windows: Port-Specific Changes Windows.
* Port-Specific Changes; Mac OS X: Port-Specific Changes Mac OS X.
* Port-Specific Changes; FreeBSD: Port-Specific Changes FreeBSD.

   ---------- Footnotes ----------

   (1) 
https://web.archive.org/web/20110715084810/http://sourceware.org/gdb/current/onlinedocs/gdb/Python.html

   (2) https://bugs.python.org/issue?@action=redirect&bpo=8032

   (3) https://bugs.python.org/issue?@action=redirect&bpo=3632

   (4) https://bugs.python.org/issue?@action=redirect&bpo=4293

   (5) https://bugs.python.org/issue?@action=redirect&bpo=7033

   (6) https://bugs.python.org/issue?@action=redirect&bpo=7528

   (7) https://bugs.python.org/issue?@action=redirect&bpo=7767

   (8) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5983

   (9) https://bugs.python.org/issue?@action=redirect&bpo=5753

   (10) https://bugs.python.org/issue?@action=redirect&bpo=5793

   (11) https://bugs.python.org/issue?@action=redirect&bpo=8276

   (12) https://bugs.python.org/issue?@action=redirect&bpo=7228

   (13) https://bugs.python.org/issue?@action=redirect&bpo=1590864

   (14) https://bugs.python.org/issue?@action=redirect&bpo=1722344

   (15) https://bugs.python.org/issue?@action=redirect&bpo=3102

   (16) https://bugs.python.org/issue?@action=redirect&bpo=7609

   (17) https://bugs.python.org/issue?@action=redirect&bpo=2422

   (18) https://bugs.python.org/issue?@action=redirect&bpo=6491

   (19) https://bugs.python.org/issue?@action=redirect&bpo=2937

   (20) https://bugs.python.org/issue?@action=redirect&bpo=1222585

   (21) https://bugs.python.org/issue?@action=redirect&bpo=3585

   (22) https://bugs.python.org/issue?@action=redirect&bpo=6094


File: python.info,  Node: Capsules,  Next: Port-Specific Changes Windows,  Up: Build and C API Changes<7>

1.15.12.1 Capsules
..................

Python 3.1 adds a new C datatype, *note PyCapsule: 120b, for providing a
C API to an extension module.  A capsule is essentially the holder of a
C ‘void *’ pointer, and is made available as a module attribute; for
example, the *note socket: b8. module's API is exposed as ‘socket.CAPI’,
and *note unicodedata: ee. exposes ‘ucnhash_CAPI’.  Other extensions can
import the module, access its dictionary to get the capsule object, and
then get the ‘void *’ pointer, which will usually point to an array of
pointers to the module's various API functions.

There is an existing data type already used for this, ‘PyCObject’, but
it doesn't provide type safety.  Evil code written in pure Python could
cause a segmentation fault by taking a ‘PyCObject’ from module A and
somehow substituting it for the ‘PyCObject’ in module B. Capsules know
their own name, and getting the pointer requires providing the name:

     void *vtable;

     if (!PyCapsule_IsValid(capsule, "mymodule.CAPI") {
             PyErr_SetString(PyExc_ValueError, "argument type invalid");
             return NULL;
     }

     vtable = PyCapsule_GetPointer(capsule, "mymodule.CAPI");

You are assured that ‘vtable’ points to whatever you're expecting.  If a
different capsule was passed in, *note PyCapsule_IsValid(): 12e9. would
detect the mismatched name and return false.  Refer to *note Providing a
C API for an Extension Module: 12ea. for more information on using these
objects.

Python 2.7 now uses capsules internally to provide various
extension-module APIs, but the ‘PyCObject_AsVoidPtr()’ was modified to
handle capsules, preserving compile-time compatibility with the
‘PyCObject’ interface.  Use of ‘PyCObject_AsVoidPtr()’ will signal a
*note PendingDeprecationWarning: 86d, which is silent by default.

Implemented in Python 3.1 and backported to 2.7 by Larry Hastings;
discussed in bpo-5630(1).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=5630


File: python.info,  Node: Port-Specific Changes Windows,  Next: Port-Specific Changes Mac OS X,  Prev: Capsules,  Up: Build and C API Changes<7>

1.15.12.2 Port-Specific Changes: Windows
........................................

   * The *note msvcrt: 85. module now contains some constants from the
     ‘crtassem.h’ header file: *note CRT_ASSEMBLY_VERSION: 12ec, *note
     VC_ASSEMBLY_PUBLICKEYTOKEN: 12ed, and *note
     LIBRARIES_ASSEMBLY_NAME_PREFIX: 12ee.  (Contributed by David
     Cournapeau; bpo-4365(1).)

   * The *note _winreg: fe. module for accessing the registry now
     implements the *note CreateKeyEx(): 12ef. and *note DeleteKeyEx():
     12f0. functions, extended versions of previously supported
     functions that take several extra arguments.  The *note
     DisableReflectionKey(): 12f1, *note EnableReflectionKey(): 12f2,
     and *note QueryReflectionKey(): 12f3. were also tested and
     documented.  (Implemented by Brian Curtin: bpo-7347(2).)

   * The new ‘_beginthreadex()’ API is used to start threads, and the
     native thread-local storage functions are now used.  (Contributed
     by Kristján Valur Jónsson; bpo-3582(3).)

   * The *note os.kill(): 12f4. function now works on Windows.  The
     signal value can be the constants *note CTRL_C_EVENT: 12f5, *note
     CTRL_BREAK_EVENT: 12f6, or any integer.  The first two constants
     will send ‘Control-C’ and ‘Control-Break’ keystroke events to
     subprocesses; any other value will use the ‘TerminateProcess()’
     API.  (Contributed by Miki Tebeka; bpo-1220212(4).)

   * The *note os.listdir(): 1092. function now correctly fails for an
     empty path.  (Fixed by Hirokazu Yamamoto; bpo-5913(5).)

   * The *note mimetypes: 82. module will now read the MIME database
     from the Windows registry when initializing.  (Patch by Gabriel
     Genellina; bpo-4969(6).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=4365

   (2) https://bugs.python.org/issue?@action=redirect&bpo=7347

   (3) https://bugs.python.org/issue?@action=redirect&bpo=3582

   (4) https://bugs.python.org/issue?@action=redirect&bpo=1220212

   (5) https://bugs.python.org/issue?@action=redirect&bpo=5913

   (6) https://bugs.python.org/issue?@action=redirect&bpo=4969


File: python.info,  Node: Port-Specific Changes Mac OS X,  Next: Port-Specific Changes FreeBSD,  Prev: Port-Specific Changes Windows,  Up: Build and C API Changes<7>

1.15.12.3 Port-Specific Changes: Mac OS X
.........................................

   * The path ‘/Library/Python/2.7/site-packages’ is now appended to
     ‘sys.path’, in order to share added packages between the system
     installation and a user-installed copy of the same version.
     (Changed by Ronald Oussoren; bpo-4865(1).)

     在 2.7.13 版的變更: As of 2.7.13, this change was removed.
     ‘/Library/Python/2.7/site-packages’, the site-packages directory
     used by the Apple-supplied system Python 2.7 is no longer appended
     to ‘sys.path’ for user-installed Pythons such as from the
     python.org installers.  As of macOS 10.12, Apple changed how the
     system site-packages directory is configured, which could cause
     installation of pip components, like setuptools, to fail.  Packages
     installed for the system Python will no longer be shared with
     user-installed Pythons.  (bpo-28440(2))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=4865

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28440


File: python.info,  Node: Port-Specific Changes FreeBSD,  Prev: Port-Specific Changes Mac OS X,  Up: Build and C API Changes<7>

1.15.12.4 Port-Specific Changes: FreeBSD
........................................

   * FreeBSD 7.1's ‘SO_SETFIB’ constant, used with the *note socket():
     d47. methods *note getsockopt(): c7c./*note setsockopt(): c7d. to
     select an alternate routing table, is now available in the *note
     socket: b8. module.  (Added by Kyle VanderBeek; bpo-8235(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=8235


File: python.info,  Node: Other Changes and Fixes,  Next: Porting to Python 2 7,  Prev: Build and C API Changes<7>,  Up: Python 2 7 有什麼新功能

1.15.13 Other Changes and Fixes
-------------------------------

   * Two benchmark scripts, ‘iobench’ and ‘ccbench’, were added to the
     ‘Tools’ directory.  ‘iobench’ measures the speed of the built-in
     file I/O objects returned by *note open(): 4c0. while performing
     various operations, and ‘ccbench’ is a concurrency benchmark that
     tries to measure computing throughput, thread switching latency,
     and IO processing bandwidth when performing several tasks using a
     varying number of threads.

   * The ‘Tools/i18n/msgfmt.py’ script now understands plural forms in
     ‘.po’ files.  (Fixed by Martin von Löwis; bpo-5464(1).)

   * When importing a module from a ‘.pyc’ or ‘.pyo’ file with an
     existing ‘.py’ counterpart, the *note co_filename: 12fa. attributes
     of the resulting code objects are overwritten when the original
     filename is obsolete.  This can happen if the file has been
     renamed, moved, or is accessed through different paths.  (Patch by
     Ziga Seilnacht and Jean-Paul Calderone; bpo-1180193(2).)

   * The ‘regrtest.py’ script now takes a ‘--randseed=’ switch that
     takes an integer that will be used as the random seed for the ‘-r’
     option that executes tests in random order.  The ‘-r’ option also
     reports the seed that was used (Added by Collin Winter.)

   * Another ‘regrtest.py’ switch is ‘-j’, which takes an integer
     specifying how many tests run in parallel.  This allows reducing
     the total runtime on multi-core machines.  This option is
     compatible with several other options, including the ‘-R’ switch
     which is known to produce long runtimes.  (Added by Antoine Pitrou,
     bpo-6152(3).)  This can also be used with a new ‘-F’ switch that
     runs selected tests in a loop until they fail.  (Added by Antoine
     Pitrou; bpo-7312(4).)

   * When executed as a script, the ‘py_compile.py’ module now accepts
     ‘'-'’ as an argument, which will read standard input for the list
     of filenames to be compiled.  (Contributed by Piotr Ożarowski;
     bpo-8233(5).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=5464

   (2) https://bugs.python.org/issue?@action=redirect&bpo=1180193

   (3) https://bugs.python.org/issue?@action=redirect&bpo=6152

   (4) https://bugs.python.org/issue?@action=redirect&bpo=7312

   (5) https://bugs.python.org/issue?@action=redirect&bpo=8233


File: python.info,  Node: Porting to Python 2 7,  Next: New Features Added to Python 2 7 Maintenance Releases,  Prev: Other Changes and Fixes,  Up: Python 2 7 有什麼新功能

1.15.14 Porting to Python 2.7
-----------------------------

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

   * The *note range(): 8e7. function processes its arguments more
     consistently; it will now call *note __int__(): 6c0. on non-float,
     non-integer arguments that are supplied to it.  (Fixed by Alexander
     Belopolsky; bpo-1533(1).)

   * The string *note format(): 5c3. method changed the default
     precision used for floating-point and complex numbers from 6
     decimal places to 12, which matches the precision used by *note
     str(): 3f2.  (Changed by Eric Smith; bpo-5920(2).)

   * Because of an optimization for the *note with: 577. statement, the
     special methods *note __enter__(): 56c. and *note __exit__(): 1293.
     must belong to the object's type, and cannot be directly attached
     to the object's instance.  This affects new-style classes (derived
     from *note object: a2f.) and C extension types.  (bpo-6101(3).)

   * Due to a bug in Python 2.6, the 'exc_value' parameter to *note
     __exit__(): 1293. methods was often the string representation of
     the exception, not an instance.  This was fixed in 2.7, so
     'exc_value' will be an instance as expected.  (Fixed by Florent
     Xicluna; bpo-7853(4).)

   * When a restricted set of attributes were set using ‘__slots__’,
     deleting an unset attribute would not raise *note AttributeError:
     2f6. as you would expect.  Fixed by Benjamin Peterson;
     bpo-7604(5).)

In the standard library:

   * Operations with *note datetime: 1b0. instances that resulted in a
     year falling outside the supported range didn't always raise *note
     OverflowError: 825.  Such errors are now checked more carefully and
     will now raise the exception.  (Reported by Mark Leander, patch by
     Anand B. Pillai and Alexander Belopolsky; bpo-7150(6).)

   * When using *note Decimal: 27c. instances with a string's *note
     format(): 5c3. method, the default alignment was previously
     left-alignment.  This has been changed to right-alignment, which
     might change the output of your programs.  (Changed by Mark
     Dickinson; bpo-6857(7).)

     Comparisons involving a signaling NaN value (or ‘sNAN’) now signal
     *note InvalidOperation: 1044. instead of silently returning a true
     or false value depending on the comparison operator.  Quiet NaN
     values (or ‘NaN’) are now hashable.  (Fixed by Mark Dickinson;
     bpo-7279(8).)

   * The *note xml.etree.ElementTree: 10c. library no longer escapes
     ampersands and angle brackets when outputting an XML processing
     instruction (which looks like ‘<?xml-stylesheet href="#style1"?>’)
     or comment (which looks like ‘<!-- comment -->’).  (Patch by Neil
     Muller; bpo-2746(9).)

   * The ‘readline()’ method of *note StringIO: ecb. objects now does
     nothing when a negative length is requested, as other file-like
     objects do.  (bpo-7348(10)).

   * The *note syslog: c6. module will now use the value of
     ‘sys.argv[0]’ as the identifier instead of the previous default
     value of ‘'python'’.  (Changed by Sean Reifschneider;
     bpo-8451(11).)

   * The *note tarfile: c8. module's default error handling has changed,
     to no longer suppress fatal errors.  The default error level was
     previously 0, which meant that errors would only result in a
     message being written to the debug log, but because the debug log
     is not activated by default, these errors go unnoticed.  The
     default error level is now 1, which raises an exception if there's
     an error.  (Changed by Lars Gustäbel; bpo-7357(12).)

   * The *note urlparse: f3. module's *note urlsplit(): ce6. now handles
     unknown URL schemes in a fashion compliant with RFC 3986(13): if
     the URL is of the form ‘"<something>://..."’, the text before the
     ‘://’ is treated as the scheme, even if it's a made-up scheme that
     the module doesn't know about.  This change may break code that
     worked around the old behaviour.  For example, Python 2.6.4 or 2.5
     will return the following:

          >>> import urlparse
          >>> urlparse.urlsplit('invented://host/filename?query')
          ('invented', '', '//host/filename?query', '', '')

     Python 2.7 (and Python 2.6.5) will return:

          >>> import urlparse
          >>> urlparse.urlsplit('invented://host/filename?query')
          ('invented', 'host', '/filename?query', '', '')

     (Python 2.7 actually produces slightly different output, since it
     returns a named tuple instead of a standard tuple.)

For C extensions:

   * C extensions that use integer format codes with the ‘PyArg_Parse*’
     family of functions will now raise a *note TypeError: 4dd.
     exception instead of triggering a *note DeprecationWarning: 18b.
     (bpo-5080(14)).

   * Use the new *note PyOS_string_to_double(): 122d. function instead
     of the old ‘PyOS_ascii_strtod()’ and ‘PyOS_ascii_atof()’ functions,
     which are now deprecated.

For applications that embed Python:

   * The ‘PySys_SetArgvEx()’ function was added, letting applications
     close a security hole when the existing ‘PySys_SetArgv()’ function
     was used.  Check whether you're calling ‘PySys_SetArgv()’ and
     carefully consider whether the application should be using
     ‘PySys_SetArgvEx()’ with 'updatepath' set to false.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1533

   (2) https://bugs.python.org/issue?@action=redirect&bpo=5920

   (3) https://bugs.python.org/issue?@action=redirect&bpo=6101

   (4) https://bugs.python.org/issue?@action=redirect&bpo=7853

   (5) https://bugs.python.org/issue?@action=redirect&bpo=7604

   (6) https://bugs.python.org/issue?@action=redirect&bpo=7150

   (7) https://bugs.python.org/issue?@action=redirect&bpo=6857

   (8) https://bugs.python.org/issue?@action=redirect&bpo=7279

   (9) https://bugs.python.org/issue?@action=redirect&bpo=2746

   (10) https://bugs.python.org/issue?@action=redirect&bpo=7348

   (11) https://bugs.python.org/issue?@action=redirect&bpo=8451

   (12) https://bugs.python.org/issue?@action=redirect&bpo=7357

   (13) https://datatracker.ietf.org/doc/html/rfc3986.html

   (14) https://bugs.python.org/issue?@action=redirect&bpo=5080


File: python.info,  Node: New Features Added to Python 2 7 Maintenance Releases,  Next: 致謝,  Prev: Porting to Python 2 7,  Up: Python 2 7 有什麼新功能

1.15.15 New Features Added to Python 2.7 Maintenance Releases
-------------------------------------------------------------

New features may be added to Python 2.7 maintenance releases when the
situation genuinely calls for it.  Any such additions must go through
the Python Enhancement Proposal process, and make a compelling case for
why they can't be adequately addressed by either adding the new feature
solely to Python 3, or else by publishing it on the Python Package
Index.

In addition to the specific proposals listed below, there is a general
exemption allowing new ‘-3’ warnings to be added in any Python 2.7
maintenance release.

* Menu:

* Two new environment variables for debug mode::
* PEP 434; IDLE Enhancement Exception for All Branches: PEP 434 IDLE Enhancement Exception for All Branches.
* PEP 466; Network Security Enhancements for Python 2.7: PEP 466 Network Security Enhancements for Python 2 7.
* PEP 477; Backport ensurepip (PEP 453) to Python 2.7: PEP 477 Backport ensurepip PEP 453 to Python 2 7.
* PEP 476; Enabling certificate verification by default for stdlib http clients: PEP 476 Enabling certificate verification by default for stdlib http clients<2>.
* PEP 493; HTTPS verification migration tools for Python 2.7: PEP 493 HTTPS verification migration tools for Python 2 7.
* New make regen-all build target: New make regen-all build target<3>.
* Removal of make touch build target: Removal of make touch build target<3>.


File: python.info,  Node: Two new environment variables for debug mode,  Next: PEP 434 IDLE Enhancement Exception for All Branches,  Up: New Features Added to Python 2 7 Maintenance Releases

1.15.15.1 Two new environment variables for debug mode
......................................................

In debug mode, the ‘[xxx refs]’ statistic is not written by default, the
‘PYTHONSHOWREFCOUNT’ environment variable now must also be set.
(Contributed by Victor Stinner; bpo-31733(1).)

When Python is compiled with ‘COUNT_ALLOC’ defined, allocation counts
are no longer dumped by default anymore: the ‘PYTHONSHOWALLOCCOUNT’
environment variable must now also be set.  Moreover, allocation counts
are now dumped into stderr, rather than stdout.  (Contributed by Victor
Stinner; bpo-31692(2).)

在 2.7.15 版被加入.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31733

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31692


File: python.info,  Node: PEP 434 IDLE Enhancement Exception for All Branches,  Next: PEP 466 Network Security Enhancements for Python 2 7,  Prev: Two new environment variables for debug mode,  Up: New Features Added to Python 2 7 Maintenance Releases

1.15.15.2 PEP 434: IDLE Enhancement Exception for All Branches
..............................................................

PEP 434(1) describes a general exemption for changes made to the IDLE
development environment shipped along with Python.  This exemption makes
it possible for the IDLE developers to provide a more consistent user
experience across all supported versions of Python 2 and 3.

For details of any IDLE changes, refer to the NEWS file for the specific
release.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0434/


File: python.info,  Node: PEP 466 Network Security Enhancements for Python 2 7,  Next: PEP 477 Backport ensurepip PEP 453 to Python 2 7,  Prev: PEP 434 IDLE Enhancement Exception for All Branches,  Up: New Features Added to Python 2 7 Maintenance Releases

1.15.15.3 PEP 466: Network Security Enhancements for Python 2.7
...............................................................

PEP 466(1) describes a number of network security enhancement proposals
that have been approved for inclusion in Python 2.7 maintenance
releases, with the first of those changes appearing in the Python 2.7.7
release.

PEP 466(2) related features added in Python 2.7.7:

   * *note hmac.compare_digest(): 1063. was backported from Python 3 to
     make a timing attack resistant comparison operation available to
     Python 2 applications.  (Contributed by Alex Gaynor; bpo-21306(3).)

   * OpenSSL 1.0.1g was upgraded in the official Windows installers
     published on python.org.  (Contributed by Zachary Ware;
     bpo-21462(4).)

PEP 466(5) related features added in Python 2.7.8:

   * *note hashlib.pbkdf2_hmac(): 4b4. was backported from Python 3 to
     make a hashing algorithm suitable for secure password storage
     broadly available to Python 2 applications.  (Contributed by Alex
     Gaynor; bpo-21304(6).)

   * OpenSSL 1.0.1h was upgraded for the official Windows installers
     published on python.org.  (Contributed by Zachary Ware in
     bpo-21671(7) for CVE-2014-0224(8).)

PEP 466(9) related features added in Python 2.7.9:

   * Most of Python 3.4's *note ssl: bb. module was backported.  This
     means *note ssl: bb. now supports Server Name Indication, TLS1.x
     settings, access to the platform certificate store, the *note
     SSLContext: 276. class, and other features.  (Contributed by Alex
     Gaynor and David Reid; bpo-21308(10).)

     Refer to the "Version added: 2.7.9" notes in the module
     documentation for specific details.

   * *note os.urandom(): 4c7. was changed to cache a file descriptor to
     ‘/dev/urandom’ instead of reopening ‘/dev/urandom’ on every call.
     (Contributed by Alex Gaynor; bpo-21305(11).)

   * *note hashlib.algorithms_guaranteed: 1300. and *note
     hashlib.algorithms_available: 1301. were backported from Python 3
     to make it easier for Python 2 applications to select the strongest
     available hash algorithm.  (Contributed by Alex Gaynor in
     bpo-21307(12))

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0466/

   (2) https://peps.python.org/pep-0466/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=21306

   (4) https://bugs.python.org/issue?@action=redirect&bpo=21462

   (5) https://peps.python.org/pep-0466/

   (6) https://bugs.python.org/issue?@action=redirect&bpo=21304

   (7) https://bugs.python.org/issue?@action=redirect&bpo=21671

   (8) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0224

   (9) https://peps.python.org/pep-0466/

   (10) https://bugs.python.org/issue?@action=redirect&bpo=21308

   (11) https://bugs.python.org/issue?@action=redirect&bpo=21305

   (12) https://bugs.python.org/issue?@action=redirect&bpo=21307


File: python.info,  Node: PEP 477 Backport ensurepip PEP 453 to Python 2 7,  Next: PEP 476 Enabling certificate verification by default for stdlib http clients<2>,  Prev: PEP 466 Network Security Enhancements for Python 2 7,  Up: New Features Added to Python 2 7 Maintenance Releases

1.15.15.4 PEP 477: Backport ensurepip (PEP 453) to Python 2.7
.............................................................

PEP 477(1) approves the inclusion of the PEP 453(2) ensurepip module and
the improved documentation that was enabled by it in the Python 2.7
maintenance releases, appearing first in the Python 2.7.9 release.

* Menu:

* Bootstrapping pip By Default: Bootstrapping pip By Default<2>.
* Documentation Changes: Documentation Changes<2>.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0477/

   (2) https://peps.python.org/pep-0453/


File: python.info,  Node: Bootstrapping pip By Default<2>,  Next: Documentation Changes<2>,  Up: PEP 477 Backport ensurepip PEP 453 to Python 2 7

1.15.15.5 Bootstrapping pip By Default
......................................

The new *note ensurepip: 4b. module (defined in PEP 453(1)) provides a
standard cross-platform mechanism to bootstrap the pip installer into
Python installations.  The version of ‘pip’ included with Python 2.7.9
is ‘pip’ 1.5.6, and future 2.7.x maintenance releases will update the
bundled version to the latest version of ‘pip’ that is available at the
time of creating the release candidate.

By default, the commands ‘pip’, ‘pipX’ and ‘pipX.Y’ will be installed on
all platforms (where X.Y stands for the version of the Python
installation), along with the ‘pip’ Python package and its dependencies.

For CPython *note source builds on POSIX systems: e97, the ‘make
install’ and ‘make altinstall’ commands do not bootstrap ‘pip’ by
default.  This behaviour can be controlled through configure options,
and overridden through Makefile options.

On Windows and Mac OS X, the CPython installers now default to
installing ‘pip’ along with CPython itself (users may opt out of
installing it during the installation process).  Window users will need
to opt in to the automatic ‘PATH’ modifications to have ‘pip’ available
from the command line by default, otherwise it can still be accessed
through the Python launcher for Windows as ‘py -m pip’.

As discussed in the PEP(2), platform packagers may choose not to install
these commands by default, as long as, when invoked, they provide clear
and simple directions on how to install them on that platform (usually
using the system package manager).

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0453/

   (2) 
https://peps.python.org/pep-0477/#disabling-ensurepip-by-downstream-distributors


File: python.info,  Node: Documentation Changes<2>,  Prev: Bootstrapping pip By Default<2>,  Up: PEP 477 Backport ensurepip PEP 453 to Python 2 7

1.15.15.6 Documentation Changes
...............................

As part of this change, the *note 安裝 Python 模組: e99. and
distributing-index sections of the documentation have been completely
redesigned as short getting started and FAQ documents.  Most packaging
documentation has now been moved out to the Python Packaging Authority
maintained Python Packaging User Guide(1) and the documentation of the
individual projects.

However, as this migration is currently still incomplete, the legacy
versions of those guides remaining available as *note Building C and C++
Extensions with setuptools: e9a. and *note Building C and C++ Extensions
with setuptools: e9b.

也參考
......

PEP 453(2) - Explicit bootstrapping of pip in Python installations

     PEP written by Donald Stufft and Nick Coghlan, implemented by
     Donald Stufft, Nick Coghlan, Martin von Löwis and Ned Deily.

   ---------- Footnotes ----------

   (1) https://packaging.python.org

   (2) https://peps.python.org/pep-0453/


File: python.info,  Node: PEP 476 Enabling certificate verification by default for stdlib http clients<2>,  Next: PEP 493 HTTPS verification migration tools for Python 2 7,  Prev: PEP 477 Backport ensurepip PEP 453 to Python 2 7,  Up: New Features Added to Python 2 7 Maintenance Releases

1.15.15.7 PEP 476: Enabling certificate verification by default for stdlib http clients
.......................................................................................

PEP 476(1) updated *note httplib: 64. and modules which use it, such as
*note urllib2: f4. and *note xmlrpclib: 114, to now verify that the
server presents a certificate which is signed by a Certificate Authority
in the platform trust store and whose hostname matches the hostname
being requested by default, significantly improving security for many
applications.  This change was made in the Python 2.7.9 release.

For applications which require the old previous behavior, they can pass
an alternate context:

     import urllib2
     import ssl

     # This disables all verification
     context = ssl._create_unverified_context()

     # This allows using a specific certificate for the host, which doesn't need
     # to be in the trust store
     context = ssl.create_default_context(cafile="/path/to/file.crt")

     urllib2.urlopen("https://invalid-cert", context=context)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0476/


File: python.info,  Node: PEP 493 HTTPS verification migration tools for Python 2 7,  Next: New make regen-all build target<3>,  Prev: PEP 476 Enabling certificate verification by default for stdlib http clients<2>,  Up: New Features Added to Python 2 7 Maintenance Releases

1.15.15.8 PEP 493: HTTPS verification migration tools for Python 2.7
....................................................................

PEP 493(1) provides additional migration tools to support a more
incremental infrastructure upgrade process for environments containing
applications and services relying on the historically permissive
processing of server certificates when establishing client HTTPS
connections.  These additions were made in the Python 2.7.12 release.

These tools are intended for use in cases where affected applications
and services can't be modified to explicitly pass a more permissive SSL
context when establishing the connection.

For applications and services which can't be modified at all, the new
‘PYTHONHTTPSVERIFY’ environment variable may be set to ‘0’ to revert an
entire Python process back to the default permissive behaviour of Python
2.7.8 and earlier.

For cases where the connection establishment code can't be modified, but
the overall application can be, the new
‘ssl._https_verify_certificates()’ function can be used to adjust the
default behaviour at runtime.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0493/


File: python.info,  Node: New make regen-all build target<3>,  Next: Removal of make touch build target<3>,  Prev: PEP 493 HTTPS verification migration tools for Python 2 7,  Up: New Features Added to Python 2 7 Maintenance Releases

1.15.15.9 New ‘make regen-all’ build target
...........................................

To simplify cross-compilation, and to ensure that CPython can reliably
be compiled without requiring an existing version of Python to already
be available, the autotools-based build system no longer attempts to
implicitly recompile generated files based on file modification times.

Instead, a new ‘make regen-all’ command has been added to force
regeneration of these files when desired (e.g.  after an initial version
of Python has already been built based on the pregenerated versions).

More selective regeneration targets are also defined - see
Makefile.pre.in(1) for details.

（由 Victor Stinner 於 bpo-23404(2) 中貢獻。）

在 2.7.14 版被加入.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Makefile.pre.in

   (2) https://bugs.python.org/issue?@action=redirect&bpo=23404


File: python.info,  Node: Removal of make touch build target<3>,  Prev: New make regen-all build target<3>,  Up: New Features Added to Python 2 7 Maintenance Releases

1.15.15.10 Removal of ‘make touch’ build target
...............................................

The ‘make touch’ build target previously used to request implicit
regeneration of generated files by updating their modification times has
been removed.

It has been replaced by the new ‘make regen-all’ target.

（由 Victor Stinner 於 bpo-23404(1) 中貢獻。）

在 2.7.14 版的變更.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23404


File: python.info,  Node: 致謝,  Prev: New Features Added to Python 2 7 Maintenance Releases,  Up: Python 2 7 有什麼新功能

1.15.16 致謝
------------

The author would like to thank the following people for offering
suggestions, corrections and assistance with various drafts of this
article: Nick Coghlan, Philip Jenvey, Ryan Lovett, R. David Murray, Hugh
Secker-Walker.


File: python.info,  Node: Python 2 6 有什麼新功能,  Next: Python 2 5 有什麼新功能,  Prev: Python 2 7 有什麼新功能,  Up: Python 有什麼新功能？

1.16 Python 2.6 有什麼新功能
============================


作者: A.M. Kuchling (amk at amk.ca)

This article explains the new features in Python 2.6, released on
October 1, 2008.  The release schedule is described in PEP 361(1).

The major theme of Python 2.6 is preparing the migration path to Python
3.0, a major redesign of the language.  Whenever possible, Python 2.6
incorporates new features and syntax from 3.0 while remaining compatible
with existing code by not removing older features or syntax.  When it's
not possible to do that, Python 2.6 tries to do what it can, adding
compatibility functions in a ‘future_builtins’ module and a ‘-3’ switch
to warn about usages that will become unsupported in 3.0.

Some significant new packages have been added to the standard library,
such as the *note multiprocessing: 86. and *note json: 76. modules, but
there aren't many new features that aren't related to Python 3.0 in some
way.

Python 2.6 also sees a number of improvements and bugfixes throughout
the source.  A search through the change logs finds there were 259
patches applied and 612 bugs fixed between Python 2.5 and 2.6.  Both
figures are likely to be underestimates.

This article doesn't attempt to provide a complete specification of the
new features, but instead provides a convenient overview.  For full
details, you should refer to the documentation for Python 2.6.  If you
want to understand the rationale for the design and implementation,
refer to the PEP for a particular new feature.  Whenever possible,
"What's New in Python" links to the bug/patch item for each change.

* Menu:

* Python 3.0: Python 3 0.
* Changes to the Development Process::
* PEP 343; The 'with' statement: PEP 343 The 'with' statement.
* PEP 366; Explicit Relative Imports From a Main Module: PEP 366 Explicit Relative Imports From a Main Module.
* PEP 370; Per-user site-packages Directory: PEP 370 Per-user site-packages Directory.
* PEP 371; The multiprocessing Package: PEP 371 The multiprocessing Package.
* PEP 3101; Advanced String Formatting: PEP 3101 Advanced String Formatting.
* PEP 3105; print As a Function: PEP 3105 print As a Function.
* PEP 3110; Exception-Handling Changes: PEP 3110 Exception-Handling Changes.
* PEP 3112; Byte Literals: PEP 3112 Byte Literals.
* PEP 3116; New I/O Library: PEP 3116 New I/O Library.
* PEP 3118：修訂緩衝協定::
* PEP 3119; Abstract Base Classes: PEP 3119 Abstract Base Classes.
* PEP 3127; Integer Literal Support and Syntax: PEP 3127 Integer Literal Support and Syntax.
* PEP 3129; Class Decorators: PEP 3129 Class Decorators.
* PEP 3141; A Type Hierarchy for Numbers: PEP 3141 A Type Hierarchy for Numbers.
* 其他語言更動: 其他語言更動<14>.
* New and Improved Modules: New and Improved Modules<2>.
* Deprecations and Removals::
* Build and C API Changes: Build and C API Changes<8>.
* Porting to Python 2.6: Porting to Python 2 6.
* 致謝: 致謝<2>.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0361/


File: python.info,  Node: Python 3 0,  Next: Changes to the Development Process,  Up: Python 2 6 有什麼新功能

1.16.1 Python 3.0
-----------------

The development cycle for Python versions 2.6 and 3.0 was synchronized,
with the alpha and beta releases for both versions being made on the
same days.  The development of 3.0 has influenced many features in 2.6.

Python 3.0 is a far-ranging redesign of Python that breaks compatibility
with the 2.x series.  This means that existing Python code will need
some conversion in order to run on Python 3.0.  However, not all the
changes in 3.0 necessarily break compatibility.  In cases where new
features won't cause existing code to break, they've been backported to
2.6 and are described in this document in the appropriate place.  Some
of the 3.0-derived features are:

   * A ‘__complex__()’ method for converting objects to a complex
     number.

   * Alternate syntax for catching exceptions: ‘except TypeError as
     exc’.

   * The addition of *note functools.reduce(): 126f. as a synonym for
     the built-in ‘reduce()’ function.

Python 3.0 adds several new built-in functions and changes the semantics
of some existing builtins.  Functions that are new in 3.0 such as *note
bin(): 123f. have simply been added to Python 2.6, but existing builtins
haven't been changed; instead, the ‘future_builtins’ module has versions
with the new 3.0 semantics.  Code written to be compatible with 3.0 can
do ‘from future_builtins import hex, map’ as necessary.

A new command-line switch, ‘-3’, enables warnings about features that
will be removed in Python 3.0.  You can run code with this switch to see
how much work will be necessary to port code to 3.0.  The value of this
switch is available to Python code as the boolean variable
‘sys.py3kwarning’, and to C extension code as ‘Py_Py3kWarningFlag’.

也參考
......

The 3'xxx' series of PEPs, which contains proposals for Python 3.0.  PEP
3000(1) describes the development process for Python 3.0.  Start with
PEP 3100(2) that describes the general goals for Python 3.0, and then
explore the higher-numbered PEPs that propose specific features.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3000/

   (2) https://peps.python.org/pep-3100/


File: python.info,  Node: Changes to the Development Process,  Next: PEP 343 The 'with' statement,  Prev: Python 3 0,  Up: Python 2 6 有什麼新功能

1.16.2 Changes to the Development Process
-----------------------------------------

While 2.6 was being developed, the Python development process underwent
two significant changes: we switched from SourceForge's issue tracker to
a customized Roundup installation, and the documentation was converted
from LaTeX to reStructuredText.

* Menu:

* New Issue Tracker; Roundup: New Issue Tracker Roundup.
* New Documentation Format; reStructuredText Using Sphinx: New Documentation Format reStructuredText Using Sphinx.


File: python.info,  Node: New Issue Tracker Roundup,  Next: New Documentation Format reStructuredText Using Sphinx,  Up: Changes to the Development Process

1.16.2.1 New Issue Tracker: Roundup
...................................

For a long time, the Python developers had been growing increasingly
annoyed by SourceForge's bug tracker.  SourceForge's hosted solution
doesn't permit much customization; for example, it wasn't possible to
customize the life cycle of issues.

The infrastructure committee of the Python Software Foundation therefore
posted a call for issue trackers, asking volunteers to set up different
products and import some of the bugs and patches from SourceForge.  Four
different trackers were examined: Jira(1), Launchpad(2), Roundup(3), and
Trac(4).  The committee eventually settled on Jira and Roundup as the
two candidates.  Jira is a commercial product that offers no-cost hosted
instances to free-software projects; Roundup is an open-source project
that requires volunteers to administer it and a server to host it.

After posting a call for volunteers, a new Roundup installation was set
up at ‘https://bugs.python.org’.  One installation of Roundup can host
multiple trackers, and this server now also hosts issue trackers for
Jython and for the Python web site.  It will surely find other uses in
the future.  Where possible, this edition of "What's New in Python"
links to the bug/patch item for each change.

Hosting of the Python bug tracker is kindly provided by Upfront
Systems(5) of Stellenbosch, South Africa.  Martin von Löwis put a lot of
effort into importing existing bugs and patches from SourceForge; his
scripts for this import operation are at
‘https://svn.python.org/view/tracker/importer/’ and may be useful to
other projects wishing to move from SourceForge to Roundup.

也參考
......

‘https://bugs.python.org’

     The Python bug tracker.

‘https://bugs.jython.org’:

     The Jython bug tracker.

‘https://roundup.sourceforge.io/’

     Roundup downloads and documentation.

‘https://svn.python.org/view/tracker/importer/’

     Martin von Löwis's conversion scripts.

   ---------- Footnotes ----------

   (1) https://www.atlassian.com/software/jira/

   (2) https://launchpad.net/

   (3) https://roundup.sourceforge.io/

   (4) https://trac.edgewall.org/

   (5) https://upfrontsoftware.co.za


File: python.info,  Node: New Documentation Format reStructuredText Using Sphinx,  Prev: New Issue Tracker Roundup,  Up: Changes to the Development Process

1.16.2.2 New Documentation Format: reStructuredText Using Sphinx
................................................................

The Python documentation was written using LaTeX since the project
started around 1989.  In the 1980s and early 1990s, most documentation
was printed out for later study, not viewed online.  LaTeX was widely
used because it provided attractive printed output while remaining
straightforward to write once the basic rules of the markup were
learned.

Today LaTeX is still used for writing publications destined for
printing, but the landscape for programming tools has shifted.  We no
longer print out reams of documentation; instead, we browse through it
online and HTML has become the most important format to support.
Unfortunately, converting LaTeX to HTML is fairly complicated and Fred
L.  Drake Jr., the long-time Python documentation editor, spent a lot of
time maintaining the conversion process.  Occasionally people would
suggest converting the documentation into SGML and later XML, but
performing a good conversion is a major task and no one ever committed
the time required to finish the job.

During the 2.6 development cycle, Georg Brandl put a lot of effort into
building a new toolchain for processing the documentation.  The
resulting package is called Sphinx, and is available from
‘https://www.sphinx-doc.org/’.

Sphinx concentrates on HTML output, producing attractively styled and
modern HTML; printed output is still supported through conversion to
LaTeX. The input format is reStructuredText, a markup syntax supporting
custom extensions and directives that is commonly used in the Python
community.

Sphinx is a standalone package that can be used for writing, and almost
two dozen other projects (listed on the Sphinx web site(1)) have adopted
Sphinx as their documentation tool.

也參考
......

Documenting Python(2)

     Describes how to write for Python's documentation.

Sphinx(3)

     Documentation and code for the Sphinx toolchain.

Docutils(4)

     The underlying reStructuredText parser and toolset.

   ---------- Footnotes ----------

   (1) https://www.sphinx-doc.org/en/master/examples.html

   (2) https://devguide.python.org/documenting/

   (3) https://www.sphinx-doc.org/

   (4) https://docutils.sourceforge.io


File: python.info,  Node: PEP 343 The 'with' statement,  Next: PEP 366 Explicit Relative Imports From a Main Module,  Prev: Changes to the Development Process,  Up: Python 2 6 有什麼新功能

1.16.3 PEP 343: The 'with' statement
------------------------------------

The previous version, Python 2.5, added the '*note with: 577.' statement
as an optional feature, to be enabled by a ‘from __future__ import
with_statement’ directive.  In 2.6 the statement no longer needs to be
specially enabled; this means that ‘with’ is now always a keyword.  The
rest of this section is a copy of the corresponding section from the
"What's New in Python 2.5" document; if you're familiar with the
'‘with’' statement from Python 2.5, you can skip this section.

The '*note with: 577.' statement clarifies code that previously would
use ‘try...finally’ blocks to ensure that clean-up code is executed.  In
this section, I'll discuss the statement as it will commonly be used.
In the next section, I'll examine the implementation details and show
how to write objects for use with this statement.

The '*note with: 577.' statement is a control-flow structure whose basic
structure is:

     with expression [as variable]:
         with-block

The expression is evaluated, and it should result in an object that
supports the context management protocol (that is, has *note
__enter__(): 56c. and *note __exit__(): 1293. methods).

The object's *note __enter__(): 56c. is called before 'with-block' is
executed and therefore can run set-up code.  It also may return a value
that is bound to the name 'variable', if given.  (Note carefully that
'variable' is 'not' assigned the result of 'expression'.)

After execution of the 'with-block' is finished, the object's *note
__exit__(): 1293. method is called, even if the block raised an
exception, and can therefore run clean-up code.

Some standard Python objects now support the context management protocol
and can be used with the '*note with: 577.' statement.  File objects are
one example:

     with open('/etc/passwd', 'r') as f:
         for line in f:
             print line
             ... more processing code ...

After this statement has executed, the file object in 'f' will have been
automatically closed, even if the *note for: 2c3. loop raised an
exception part-way through the block.

     備註: In this case, 'f' is the same object created by *note open():
     4c0, because *note __enter__(): 56c. returns 'self'.

The *note threading: d6. module's locks and condition variables also
support the '*note with: 577.' statement:

     lock = threading.Lock()
     with lock:
         # Critical section of code
         ...

The lock is acquired before the block is executed and always released
once the block is complete.

The ‘localcontext()’ function in the *note decimal: 2e. module makes it
easy to save and restore the current decimal context, which encapsulates
the desired precision and rounding characteristics for computations:

     from decimal import Decimal, Context, localcontext

     # Displays with default precision of 28 digits
     v = Decimal('578')
     print v.sqrt()

     with localcontext(Context(prec=16)):
         # All code in this block uses a precision of 16 digits.
         # The original context is restored on exiting the block.
         print v.sqrt()

* Menu:

* Writing Context Managers::
* contextlib 模組::


File: python.info,  Node: Writing Context Managers,  Next: contextlib 模組,  Up: PEP 343 The 'with' statement

1.16.3.1 Writing Context Managers
.................................

Under the hood, the '*note with: 577.' statement is fairly complicated.
Most people will only use '‘with’' in company with existing objects and
don't need to know these details, so you can skip the rest of this
section if you like.  Authors of new objects will need to understand the
details of the underlying implementation and should keep reading.

A high-level explanation of the context management protocol is:

   * The expression is evaluated and should result in an object called a
     "context manager".  The context manager must have *note
     __enter__(): 56c. and *note __exit__(): 1293. methods.

   * The context manager's *note __enter__(): 56c. method is called.
     The value returned is assigned to 'VAR'. If no ‘as VAR’ clause is
     present, the value is simply discarded.

   * The code in 'BLOCK' is executed.

   * If 'BLOCK' raises an exception, the context manager's *note
     __exit__(): 1293. method is called with three arguments, the
     exception details (‘type, value, traceback’, the same values
     returned by *note sys.exc_info(): 630, which can also be ‘None’ if
     no exception occurred).  The method's return value controls whether
     an exception is re-raised: any false value re-raises the exception,
     and ‘True’ will result in suppressing it.  You'll only rarely want
     to suppress the exception, because if you do the author of the code
     containing the '*note with: 577.' statement will never realize
     anything went wrong.

   * If 'BLOCK' didn't raise an exception, the *note __exit__(): 1293.
     method is still called, but 'type', 'value', and 'traceback' are
     all ‘None’.

Let's think through an example.  I won't present detailed code but will
only sketch the methods necessary for a database that supports
transactions.

(For people unfamiliar with database terminology: a set of changes to
the database are grouped into a transaction.  Transactions can be either
committed, meaning that all the changes are written into the database,
or rolled back, meaning that the changes are all discarded and the
database is unchanged.  See any database textbook for more information.)

Let's assume there's an object representing a database connection.  Our
goal will be to let the user write code like this:

     db_connection = DatabaseConnection()
     with db_connection as cursor:
         cursor.execute('insert into ...')
         cursor.execute('delete from ...')
         # ... more operations ...

The transaction should be committed if the code in the block runs
flawlessly or rolled back if there's an exception.  Here's the basic
interface for ‘DatabaseConnection’ that I'll assume:

     class DatabaseConnection:
         # Database interface
         def cursor(self):
             "Returns a cursor object and starts a new transaction"
         def commit(self):
             "Commits current transaction"
         def rollback(self):
             "Rolls back current transaction"

The *note __enter__(): 56c. method is pretty easy, having only to start
a new transaction.  For this application the resulting cursor object
would be a useful result, so the method will return it.  The user can
then add ‘as cursor’ to their '*note with: 577.' statement to bind the
cursor to a variable name.

     class DatabaseConnection:
         ...
         def __enter__(self):
             # Code to start a new transaction
             cursor = self.cursor()
             return cursor

The *note __exit__(): 1293. method is the most complicated because it's
where most of the work has to be done.  The method has to check if an
exception occurred.  If there was no exception, the transaction is
committed.  The transaction is rolled back if there was an exception.

In the code below, execution will just fall off the end of the function,
returning the default value of ‘None’.  ‘None’ is false, so the
exception will be re-raised automatically.  If you wished, you could be
more explicit and add a *note return: 972. statement at the marked
location.

     class DatabaseConnection:
         ...
         def __exit__(self, type, value, tb):
             if tb is None:
                 # No exception, so commit
                 self.commit()
             else:
                 # Exception occurred, so rollback.
                 self.rollback()
                 # return False


File: python.info,  Node: contextlib 模組,  Prev: Writing Context Managers,  Up: PEP 343 The 'with' statement

1.16.3.2 contextlib 模組
........................

The *note contextlib: 1c. module provides some functions and a decorator
that are useful when writing objects for use with the '*note with: 577.'
statement.

The decorator is called ‘contextmanager()’, and lets you write a single
generator function instead of defining a new class.  The generator
should yield exactly one value.  The code up to the *note yield: 971.
will be executed as the *note __enter__(): 56c. method, and the value
yielded will be the method's return value that will get bound to the
variable in the '*note with: 577.' statement's ‘as’ clause, if any.  The
code after the ‘yield’ will be executed in the *note __exit__(): 1293.
method.  Any exception raised in the block will be raised by the ‘yield’
statement.

Using this decorator, our database example from the previous section
could be written as:

     from contextlib import contextmanager

     @contextmanager
     def db_transaction(connection):
         cursor = connection.cursor()
         try:
             yield cursor
         except:
             connection.rollback()
             raise
         else:
             connection.commit()

     db = DatabaseConnection()
     with db_transaction(db) as cursor:
         ...

The *note contextlib: 1c. module also has a ‘nested(mgr1, mgr2, ...)’
function that combines a number of context managers so you don't need to
write nested '*note with: 577.' statements.  In this example, the single
'‘with’' statement both starts a database transaction and acquires a
thread lock:

     lock = threading.Lock()
     with nested (db_transaction(db), lock) as (cursor, locked):
         ...

Finally, the ‘closing()’ function returns its argument so that it can be
bound to a variable, and calls the argument's ‘.close()’ method at the
end of the block.

     import urllib, sys
     from contextlib import closing

     with closing(urllib.urlopen('http://www.yahoo.com')) as f:
         for line in f:
             sys.stdout.write(line)

也參考
......

PEP 343(1) - The "with" statement

     PEP written by Guido van Rossum and Nick Coghlan; implemented by
     Mike Bland, Guido van Rossum, and Neal Norwitz.  The PEP shows the
     code generated for a '*note with: 577.' statement, which can be
     helpful in learning how the statement works.

*note contextlib: 1c. 模組的文件。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0343/


File: python.info,  Node: PEP 366 Explicit Relative Imports From a Main Module,  Next: PEP 370 Per-user site-packages Directory,  Prev: PEP 343 The 'with' statement,  Up: Python 2 6 有什麼新功能

1.16.4 PEP 366: Explicit Relative Imports From a Main Module
------------------------------------------------------------

Python's *note -m: 585. switch allows running a module as a script.
When you ran a module that was located inside a package, relative
imports didn't work correctly.

The fix for Python 2.6 adds a *note __package__: fc0. attribute to
modules.  When this attribute is present, relative imports will be
relative to the value of this attribute instead of the *note __name__:
1316. attribute.

PEP 302-style importers can then set *note __package__: fc0. as
necessary.  The *note runpy: ac. module that implements the *note -m:
585. switch now does this, so relative imports will now work correctly
in scripts running from inside a package.


File: python.info,  Node: PEP 370 Per-user site-packages Directory,  Next: PEP 371 The multiprocessing Package,  Prev: PEP 366 Explicit Relative Imports From a Main Module,  Up: Python 2 6 有什麼新功能

1.16.5 PEP 370: Per-user ‘site-packages’ Directory
--------------------------------------------------

When you run Python, the module search path ‘sys.path’ usually includes
a directory whose path ends in ‘"site-packages"’.  This directory is
intended to hold locally installed packages available to all users using
a machine or a particular site installation.

Python 2.6 introduces a convention for user-specific site directories.
The directory varies depending on the platform:

   * Unix and Mac OS X: ‘~/.local/’

   * Windows: ‘%APPDATA%/Python’

Within this directory, there will be version-specific subdirectories,
such as ‘lib/python2.6/site-packages’ on Unix/Mac OS and
‘Python26/site-packages’ on Windows.

If you don't like the default directory, it can be overridden by an
environment variable.  *note PYTHONUSERBASE: 1318. sets the root
directory used for all Python versions supporting this feature.  On
Windows, the directory for application-specific data can be changed by
setting the ‘APPDATA’ environment variable.  You can also modify the
‘site.py’ file for your Python installation.

The feature can be disabled entirely by running Python with the *note
-s: 1319. option or setting the *note PYTHONNOUSERSITE: 131a.
environment variable.

也參考
......

PEP 370(1) - Per-user ‘site-packages’ Directory

     由 Christian Heimes 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0370/


File: python.info,  Node: PEP 371 The multiprocessing Package,  Next: PEP 3101 Advanced String Formatting,  Prev: PEP 370 Per-user site-packages Directory,  Up: Python 2 6 有什麼新功能

1.16.6 PEP 371: The ‘multiprocessing’ Package
---------------------------------------------

The new *note multiprocessing: 86. package lets Python programs create
new processes that will perform a computation and return a result to the
parent.  The parent and child processes can communicate using queues and
pipes, synchronize their operations using locks and semaphores, and can
share simple arrays of data.

The *note multiprocessing: 86. module started out as an exact emulation
of the *note threading: d6. module using processes instead of threads.
That goal was discarded along the path to Python 2.6, but the general
approach of the module is still similar.  The fundamental class is the
‘Process’, which is passed a callable object and a collection of
arguments.  The ‘start()’ method sets the callable running in a
subprocess, after which you can call the ‘is_alive()’ method to check
whether the subprocess is still running and the ‘join()’ method to wait
for the process to exit.

Here's a simple example where the subprocess will calculate a factorial.
The function doing the calculation is written strangely so that it takes
significantly longer when the input argument is a multiple of 4.

     import time
     from multiprocessing import Process, Queue


     def factorial(queue, N):
         "Compute a factorial."
         # If N is a multiple of 4, this function will take much longer.
         if (N % 4) == 0:
             time.sleep(.05 * N/4)

         # Calculate the result
         fact = 1L
         for i in range(1, N+1):
             fact = fact * i

         # Put the result on the queue
         queue.put(fact)

     if __name__ == '__main__':
         queue = Queue()

         N = 5

         p = Process(target=factorial, args=(queue, N))
         p.start()
         p.join()

         result = queue.get()
         print 'Factorial', N, '=', result

A *note Queue: 131c. is used to communicate the result of the factorial.
The *note Queue: 131c. object is stored in a global variable.  The child
process will use the value of the variable when the child was created;
because it's a *note Queue: 131c, parent and child can use the object to
communicate.  (If the parent were to change the value of the global
variable, the child's value would be unaffected, and vice versa.)

Two other classes, ‘Pool’ and ‘Manager’, provide higher-level
interfaces.  ‘Pool’ will create a fixed number of worker processes, and
requests can then be distributed to the workers by calling ‘apply()’ or
‘apply_async()’ to add a single request, and *note map(): 808. or
‘map_async()’ to add a number of requests.  The following code uses a
‘Pool’ to spread requests across 5 worker processes and retrieve a list
of results:

     from multiprocessing import Pool

     def factorial(N, dictionary):
         "Compute a factorial."
         ...
     p = Pool(5)
     result = p.map(factorial, range(1, 1000, 10))
     for v in result:
         print v

This produces the following output:

     1
     39916800
     51090942171709440000
     8222838654177922817725562880000000
     33452526613163807108170062053440751665152000000000
     ...

The other high-level interface, the ‘Manager’ class, creates a separate
server process that can hold master copies of Python data structures.
Other processes can then access and modify these data structures using
proxy objects.  The following example creates a shared dictionary by
calling the *note dict(): 23b. method; the worker processes then insert
values into the dictionary.  (Locking is not done for you automatically,
which doesn't matter in this example.  ‘Manager’'s methods also include
‘Lock()’, ‘RLock()’, and ‘Semaphore()’ to create shared locks.)

     import time
     from multiprocessing import Pool, Manager

     def factorial(N, dictionary):
         "Compute a factorial."
         # Calculate the result
         fact = 1L
         for i in range(1, N+1):
             fact = fact * i

         # Store result in dictionary
         dictionary[N] = fact

     if __name__ == '__main__':
         p = Pool(5)
         mgr = Manager()
         d = mgr.dict()         # Create shared dictionary

         # Run tasks using the pool
         for N in range(1, 1000, 10):
             p.apply_async(factorial, (N, d))

         # Mark pool as closed -- no more tasks can be added.
         p.close()

         # Wait for tasks to exit
         p.join()

         # Output results
         for k, v in sorted(d.items()):
             print k, v

This will produce the output:

     1 1
     11 39916800
     21 51090942171709440000
     31 8222838654177922817725562880000000
     41 33452526613163807108170062053440751665152000000000
     51 15511187532873822802242430164693032110632597200169861120000...

也參考
......

*note multiprocessing: 86. 模組的文件。

PEP 371(1) - Addition of the multiprocessing package

     PEP written by Jesse Noller and Richard Oudkerk; implemented by
     Richard Oudkerk and Jesse Noller.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0371/


File: python.info,  Node: PEP 3101 Advanced String Formatting,  Next: PEP 3105 print As a Function,  Prev: PEP 371 The multiprocessing Package,  Up: Python 2 6 有什麼新功能

1.16.7 PEP 3101: Advanced String Formatting
-------------------------------------------

In Python 3.0, the ‘%’ operator is supplemented by a more powerful
string formatting method, *note format(): 5c3.  Support for the *note
str.format(): 5c7. method has been backported to Python 2.6.

In 2.6, both 8-bit and Unicode strings have a ‘.format()’ method that
treats the string as a template and takes the arguments to be formatted.
The formatting template uses curly brackets (‘{’, ‘}’) as special
characters:

     >>> # Substitute positional argument 0 into the string.
     >>> "User ID: {0}".format("root")
     'User ID: root'
     >>> # Use the named keyword arguments
     >>> "User ID: {uid}   Last seen: {last_login}".format(
     ...    uid="root",
     ...    last_login = "5 Mar 2008 07:20")
     'User ID: root   Last seen: 5 Mar 2008 07:20'

Curly brackets can be escaped by doubling them:

     >>> "Empty dict: {{}}".format()
     "Empty dict: {}"

Field names can be integers indicating positional arguments, such as
‘{0}’, ‘{1}’, etc.  or names of keyword arguments.  You can also supply
compound field names that read attributes or access dictionary keys:

     >>> import sys
     >>> print 'Platform: {0.platform}\nPython version: {0.version}'.format(sys)
     Platform: darwin
     Python version: 2.6a1+ (trunk:61261M, Mar  5 2008, 20:29:41)
     [GCC 4.0.1 (Apple Computer, Inc. build 5367)]'

     >>> import mimetypes
     >>> 'Content-type: {0[.mp4]}'.format(mimetypes.types_map)
     'Content-type: video/mp4'

Note that when using dictionary-style notation such as ‘[.mp4]’, you
don't need to put any quotation marks around the string; it will look up
the value using ‘.mp4’ as the key.  Strings beginning with a number will
be converted to an integer.  You can't write more complicated
expressions inside a format string.

So far we've shown how to specify which field to substitute into the
resulting string.  The precise formatting used is also controllable by
adding a colon followed by a format specifier.  For example:

     >>> # Field 0: left justify, pad to 15 characters
     >>> # Field 1: right justify, pad to 6 characters
     >>> fmt = '{0:15} ${1:>6}'
     >>> fmt.format('Registration', 35)
     'Registration    $    35'
     >>> fmt.format('Tutorial', 50)
     'Tutorial        $    50'
     >>> fmt.format('Banquet', 125)
     'Banquet         $   125'

Format specifiers can reference other fields through nesting:

     >>> fmt = '{0:{1}}'
     >>> width = 15
     >>> fmt.format('Invoice #1234', width)
     'Invoice #1234  '
     >>> width = 35
     >>> fmt.format('Invoice #1234', width)
     'Invoice #1234                      '

The alignment of a field within the desired width can be specified:

Character            Effect
                     
----------------------------------------------------------------------
                     
< (default)          Left-align
                     
                     
>                    Right-align
                     
                     
^                    Center
                     
                     
=                    (For numeric types only) Pad after the sign.
                     

Format specifiers can also include a presentation type, which controls
how the value is formatted.  For example, floating-point numbers can be
formatted as a general number or in exponential notation:

     >>> '{0:g}'.format(3.75)
     '3.75'
     >>> '{0:e}'.format(3.75)
     '3.750000e+00'

A variety of presentation types are available.  Consult the 2.6
documentation for a *note complete list: 131e.; here's a sample:

‘b’       Binary.  Outputs the number in base 2.
          
          
‘c’       Character.  Converts the integer to the corresponding Unicode character
          before printing.
          
          
‘d’       Decimal Integer.  Outputs the number in base 10.
          
          
‘o’       Octal format.  Outputs the number in base 8.
          
          
‘x’       Hex format.  Outputs the number in base 16, using lower-case letters for
          the digits above 9.
          
          
‘e’       Exponent notation.  Prints the number in scientific notation using the
          letter 'e' to indicate the exponent.
          
          
‘g’       General format.  This prints the number as a fixed-point number, unless
          the number is too large, in which case it switches to 'e' exponent
          notation.
          
          
‘n’       Number.  This is the same as 'g' (for floats) or 'd' (for integers),
          except that it uses the current locale setting to insert the appropriate
          number separator characters.
          
          
‘%’       Percentage.  Multiplies the number by 100 and displays in fixed ('f')
          format, followed by a percent sign.
          

Classes and types can define a ‘__format__()’ method to control how
they're formatted.  It receives a single argument, the format specifier:

     def __format__(self, format_spec):
         if isinstance(format_spec, unicode):
             return unicode(str(self))
         else:
             return str(self)

There's also a *note format(): 5c3. builtin that will format a single
value.  It calls the type's ‘__format__()’ method with the provided
specifier:

     >>> format(75.6564, '.2f')
     '75.66'

也參考
......

*note 格式化文字語法: 131e.

     The reference documentation for format fields.

PEP 3101(1) - Advanced String Formatting

     由 Talin 撰寫 PEP、由 Eric Smith 實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3101/


File: python.info,  Node: PEP 3105 print As a Function,  Next: PEP 3110 Exception-Handling Changes,  Prev: PEP 3101 Advanced String Formatting,  Up: Python 2 6 有什麼新功能

1.16.8 PEP 3105: ‘print’ As a Function
--------------------------------------

The ‘print’ statement becomes the *note print(): f18. function in Python
3.0.  Making *note print(): f18. a function makes it possible to replace
the function by doing ‘def print(...)’ or importing a new function from
somewhere else.

Python 2.6 has a ‘__future__’ import that removes ‘print’ as language
syntax, letting you use the functional form instead.  For example:

     >>> from __future__ import print_function
     >>> print('# of entries', len(dictionary), file=sys.stderr)

The signature of the new function is:

     def print(*args, sep=' ', end='\n', file=None)

The parameters are:

   * 'args': positional arguments whose values will be printed out.

   * 'sep': the separator, which will be printed between arguments.

   * 'end': the ending text, which will be printed after all of the
     arguments have been output.

   * 'file': the file object to which the output will be sent.

也參考
......

PEP 3105(1) - Make print a function

     由 Georg Brandl 撰寫 PEP。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3105/


File: python.info,  Node: PEP 3110 Exception-Handling Changes,  Next: PEP 3112 Byte Literals,  Prev: PEP 3105 print As a Function,  Up: Python 2 6 有什麼新功能

1.16.9 PEP 3110: Exception-Handling Changes
-------------------------------------------

One error that Python programmers occasionally make is writing the
following code:

     try:
         ...
     except TypeError, ValueError:  # Wrong!
         ...

The author is probably trying to catch both *note TypeError: 4dd. and
*note ValueError: 1e7. exceptions, but this code actually does something
different: it will catch *note TypeError: 4dd. and bind the resulting
exception object to the local name ‘"ValueError"’.  The *note
ValueError: 1e7. exception will not be caught at all.  The correct code
specifies a tuple of exceptions:

     try:
         ...
     except (TypeError, ValueError):
         ...

This error happens because the use of the comma here is ambiguous: does
it indicate two different nodes in the parse tree, or a single node
that's a tuple?

Python 3.0 makes this unambiguous by replacing the comma with the word
"as".  To catch an exception and store the exception object in the
variable ‘exc’, you must write:

     try:
         ...
     except TypeError as exc:
         ...

Python 3.0 will only support the use of "as", and therefore interprets
the first example as catching two different exceptions.  Python 2.6
supports both the comma and "as", so existing code will continue to
work.  We therefore suggest using "as" when writing new Python code that
will only be executed with 2.6.

也參考
......

PEP 3110(1) - Catching Exceptions in Python 3000

     由 Collin Winter 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3110/


File: python.info,  Node: PEP 3112 Byte Literals,  Next: PEP 3116 New I/O Library,  Prev: PEP 3110 Exception-Handling Changes,  Up: Python 2 6 有什麼新功能

1.16.10 PEP 3112: Byte Literals
-------------------------------

Python 3.0 adopts Unicode as the language's fundamental string type and
denotes 8-bit literals differently, either as ‘b'string'’ or using a
*note bytes: 1a5. constructor.  For future compatibility, Python 2.6
adds *note bytes: 1a5. as a synonym for the *note str: 3f2. type, and it
also supports the ‘b''’ notation.

The 2.6 *note str: 3f2. differs from 3.0's *note bytes: 1a5. type in
various ways; most notably, the constructor is completely different.  In
3.0, ‘bytes([65, 66, 67])’ is 3 elements long, containing the bytes
representing ‘ABC’; in 2.6, ‘bytes([65, 66, 67])’ returns the 12-byte
string representing the *note str(): 3f2. of the list.

The primary use of *note bytes: 1a5. in 2.6 will be to write tests of
object type such as ‘isinstance(x, bytes)’.  This will help the 2to3
converter, which can't tell whether 2.x code intends strings to contain
either characters or 8-bit bytes; you can now use either *note bytes:
1a5. or *note str: 3f2. to represent your intention exactly, and the
resulting code will also be correct in Python 3.0.

There's also a ‘__future__’ import that causes all string literals to
become Unicode strings.  This means that ‘\u’ escape sequences can be
used to include Unicode characters:

     from __future__ import unicode_literals

     s = ('\u751f\u3080\u304e\u3000\u751f\u3054'
          '\u3081\u3000\u751f\u305f\u307e\u3054')

     print len(s)               # 12 Unicode characters

At the C level, Python 3.0 will rename the existing 8-bit string type,
called ‘PyStringObject’ in Python 2.x, to *note PyBytesObject: 736.
Python 2.6 uses ‘#define’ to support using the names *note
PyBytesObject(): 736, *note PyBytes_Check(): 1322, *note
PyBytes_FromStringAndSize(): 1323, and all the other functions and
macros used with strings.

Instances of the *note bytes: 1a5. type are immutable just as strings
are.  A new *note bytearray: 4e3. type stores a mutable sequence of
bytes:

     >>> bytearray([65, 66, 67])
     bytearray(b'ABC')
     >>> b = bytearray(u'\u21ef\u3244', 'utf-8')
     >>> b
     bytearray(b'\xe2\x87\xaf\xe3\x89\x84')
     >>> b[0] = '\xe3'
     >>> b
     bytearray(b'\xe3\x87\xaf\xe3\x89\x84')
     >>> unicode(str(b), 'utf-8')
     u'\u31ef \u3244'

Byte arrays support most of the methods of string types, such as
‘startswith()’/‘endswith()’, ‘find()’/‘rfind()’, and some of the methods
of lists, such as ‘append()’, ‘pop()’, and ‘reverse()’.

     >>> b = bytearray('ABC')
     >>> b.append('d')
     >>> b.append(ord('e'))
     >>> b
     bytearray(b'ABCde')

There's also a corresponding C API, with *note PyByteArray_FromObject():
1324, *note PyByteArray_FromStringAndSize(): 1325, and various other
functions.

也參考
......

PEP 3112(1) - Bytes literals in Python 3000

     PEP written by Jason Orendorff; backported to 2.6 by Christian
     Heimes.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3112/


File: python.info,  Node: PEP 3116 New I/O Library,  Next: PEP 3118：修訂緩衝協定,  Prev: PEP 3112 Byte Literals,  Up: Python 2 6 有什麼新功能

1.16.11 PEP 3116: New I/O Library
---------------------------------

Python's built-in file objects support a number of methods, but
file-like objects don't necessarily support all of them.  Objects that
imitate files usually support ‘read()’ and ‘write()’, but they may not
support *note readline(): a8, for example.  Python 3.0 introduces a
layered I/O library in the *note io: 73. module that separates buffering
and text-handling features from the fundamental read and write
operations.

There are three levels of abstract base classes provided by the *note
io: 73. module:

   * ‘RawIOBase’ defines raw I/O operations: ‘read()’, ‘readinto()’,
     ‘write()’, ‘seek()’, ‘tell()’, ‘truncate()’, and ‘close()’.  Most
     of the methods of this class will often map to a single system
     call.  There are also ‘readable()’, ‘writable()’, and ‘seekable()’
     methods for determining what operations a given object will allow.

     Python 3.0 has concrete implementations of this class for files and
     sockets, but Python 2.6 hasn't restructured its file and socket
     objects in this way.

   * ‘BufferedIOBase’ is an abstract base class that buffers data in
     memory to reduce the number of system calls used, making I/O
     processing more efficient.  It supports all of the methods of
     ‘RawIOBase’, and adds a ‘raw’ attribute holding the underlying raw
     object.

     There are five concrete classes implementing this ABC.
     ‘BufferedWriter’ and ‘BufferedReader’ are for objects that support
     write-only or read-only usage that have a ‘seek()’ method for
     random access.  ‘BufferedRandom’ objects support read and write
     access upon the same underlying stream, and ‘BufferedRWPair’ is for
     objects such as TTYs that have both read and write operations
     acting upon unconnected streams of data.  The ‘BytesIO’ class
     supports reading, writing, and seeking over an in-memory buffer.

   * ‘TextIOBase’: Provides functions for reading and writing strings
     (remember, strings will be Unicode in Python 3.0), and supporting
     *note universal newlines: ce1.  ‘TextIOBase’ defines the *note
     readline(): a8. method and supports iteration upon objects.

     There are two concrete implementations.  ‘TextIOWrapper’ wraps a
     buffered I/O object, supporting all of the methods for text I/O and
     adding a ‘buffer’ attribute for access to the underlying object.
     ‘StringIO’ simply buffers everything in memory without ever writing
     anything to disk.

     (In Python 2.6, *note io.StringIO: ecb. is implemented in pure
     Python, so it's pretty slow.  You should therefore stick with the
     existing ‘StringIO’ module or ‘cStringIO’ for now.  At some point
     Python 3.0's *note io: 73. module will be rewritten into C for
     speed, and perhaps the C implementation will be backported to the
     2.x releases.)

In Python 2.6, the underlying implementations haven't been restructured
to build on top of the *note io: 73. module's classes.  The module is
being provided to make it easier to write code that's forward-compatible
with 3.0, and to save developers the effort of writing their own
implementations of buffering and text I/O.

也參考
......

PEP 3116(1) - New I/O

     PEP written by Daniel Stutzbach, Mike Verdone, and Guido van
     Rossum.  Code by Guido van Rossum, Georg Brandl, Walter Doerwald,
     Jeremy Hylton, Martin von Löwis, Tony Lownds, and others.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3116/


File: python.info,  Node: PEP 3118：修訂緩衝協定,  Next: PEP 3119 Abstract Base Classes,  Prev: PEP 3116 New I/O Library,  Up: Python 2 6 有什麼新功能

1.16.12 PEP 3118：修訂緩衝協定
------------------------------

The buffer protocol is a C-level API that lets Python types exchange
pointers into their internal representations.  A memory-mapped file can
be viewed as a buffer of characters, for example, and this lets another
module such as *note re: a7. treat memory-mapped files as a string of
characters to be searched.

The primary users of the buffer protocol are numeric-processing packages
such as NumPy, which expose the internal representation of arrays so
that callers can write data directly into an array instead of going
through a slower API. This PEP updates the buffer protocol in light of
experience from NumPy development, adding a number of new features such
as indicating the shape of an array or locking a memory region.

The most important new C API function is ‘PyObject_GetBuffer(PyObject
*obj, Py_buffer *view, int flags)’, which takes an object and a set of
flags, and fills in the ‘Py_buffer’ structure with information about the
object's memory representation.  Objects can use this operation to lock
memory in place while an external caller could be modifying the
contents, so there's a corresponding ‘PyBuffer_Release(Py_buffer *view)’
to indicate that the external caller is done.

The 'flags' argument to *note PyObject_GetBuffer(): 369. specifies
constraints upon the memory returned.  Some examples are:

   * *note PyBUF_WRITABLE: 1328. indicates that the memory must be
     writable.

   * ‘PyBUF_LOCK’ requests a read-only or exclusive lock on the memory.

   * *note PyBUF_C_CONTIGUOUS: 1329. and *note PyBUF_F_CONTIGUOUS: 132a.
     requests a C-contiguous (last dimension varies the fastest) or
     Fortran-contiguous (first dimension varies the fastest) array
     layout.

Two new argument codes for *note PyArg_ParseTuple(): 517, ‘s*’ and ‘z*’,
return locked buffer objects for a parameter.

也參考
......

PEP 3118(1) - Revising the buffer protocol

     PEP written by Travis Oliphant and Carl Banks; implemented by
     Travis Oliphant.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3118/


File: python.info,  Node: PEP 3119 Abstract Base Classes,  Next: PEP 3127 Integer Literal Support and Syntax,  Prev: PEP 3118：修訂緩衝協定,  Up: Python 2 6 有什麼新功能

1.16.13 PEP 3119: Abstract Base Classes
---------------------------------------

Some object-oriented languages such as Java support interfaces,
declaring that a class has a given set of methods or supports a given
access protocol.  Abstract Base Classes (or ABCs) are an equivalent
feature for Python.  The ABC support consists of an *note abc: 4. module
containing a metaclass called ‘ABCMeta’, special handling of this
metaclass by the *note isinstance(): 3e8. and *note issubclass(): 765.
builtins, and a collection of basic ABCs that the Python developers
think will be widely useful.  Future versions of Python will probably
add more ABCs.

Let's say you have a particular class and wish to know whether it
supports dictionary-style access.  The phrase "dictionary-style" is
vague, however.  It probably means that accessing items with ‘obj[1]’
works.  Does it imply that setting items with ‘obj[2] = value’ works?
Or that the object will have ‘keys()’, ‘values()’, and ‘items()’
methods?  What about the iterative variants such as ‘iterkeys()’?  *note
copy(): 1e. and ‘update()’?  Iterating over the object with *note
iter(): 77b.?

The Python 2.6 *note collections: 16. module includes a number of
different ABCs that represent these distinctions.  ‘Iterable’ indicates
that a class defines ‘__iter__()’, and ‘Container’ means the class
defines a ‘__contains__()’ method and therefore supports ‘x in y’
expressions.  The basic dictionary interface of getting items, setting
items, and ‘keys()’, ‘values()’, and ‘items()’, is defined by the
‘MutableMapping’ ABC.

You can derive your own classes from a particular ABC to indicate they
support that ABC's interface:

     import collections

     class Storage(collections.MutableMapping):
         ...

Alternatively, you could write the class without deriving from the
desired ABC and instead register the class by calling the ABC's
‘register()’ method:

     import collections

     class Storage:
         ...

     collections.MutableMapping.register(Storage)

For classes that you write, deriving from the ABC is probably clearer.
The ‘register()’ method is useful when you've written a new ABC that can
describe an existing type or class, or if you want to declare that some
third-party class implements an ABC. For example, if you defined a
‘PrintableType’ ABC, it's legal to do:

     # Register Python's types
     PrintableType.register(int)
     PrintableType.register(float)
     PrintableType.register(str)

Classes should obey the semantics specified by an ABC, but Python can't
check this; it's up to the class author to understand the ABC's
requirements and to implement the code accordingly.

To check whether an object supports a particular interface, you can now
write:

     def func(d):
         if not isinstance(d, collections.MutableMapping):
             raise ValueError("Mapping object expected, not %r" % d)

Don't feel that you must now begin writing lots of checks as in the
above example.  Python has a strong tradition of duck-typing, where
explicit type-checking is never done and code simply calls methods on an
object, trusting that those methods will be there and raising an
exception if they aren't.  Be judicious in checking for ABCs and only do
it where it's absolutely necessary.

You can write your own ABCs by using ‘abc.ABCMeta’ as the metaclass in a
class definition:

     from abc import ABCMeta, abstractmethod

     class Drawable():
         __metaclass__ = ABCMeta

         @abstractmethod
         def draw(self, x, y, scale=1.0):
             pass

         def draw_doubled(self, x, y):
             self.draw(x, y, scale=2.0)


     class Square(Drawable):
         def draw(self, x, y, scale):
             ...

In the ‘Drawable’ ABC above, the ‘draw_doubled()’ method renders the
object at twice its size and can be implemented in terms of other
methods described in ‘Drawable’.  Classes implementing this ABC
therefore don't need to provide their own implementation of
‘draw_doubled()’, though they can do so.  An implementation of ‘draw()’
is necessary, though; the ABC can't provide a useful generic
implementation.

You can apply the ‘@abstractmethod’ decorator to methods such as
‘draw()’ that must be implemented; Python will then raise an exception
for classes that don't define the method.  Note that the exception is
only raised when you actually try to create an instance of a subclass
lacking the method:

     >>> class Circle(Drawable):
     ...     pass
     ...
     >>> c = Circle()
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: Can't instantiate abstract class Circle with abstract methods draw
     >>>

Abstract data attributes can be declared using the ‘@abstractproperty’
decorator:

     from abc import abstractproperty
     ...

     @abstractproperty
     def readonly(self):
        return self._x

Subclasses must then define a ‘readonly()’ property.

也參考
......

PEP 3119(1) - Introducing Abstract Base Classes

     PEP written by Guido van Rossum and Talin.  Implemented by Guido
     van Rossum.  Backported to 2.6 by Benjamin Aranguren, with Alex
     Martelli.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3119/


File: python.info,  Node: PEP 3127 Integer Literal Support and Syntax,  Next: PEP 3129 Class Decorators,  Prev: PEP 3119 Abstract Base Classes,  Up: Python 2 6 有什麼新功能

1.16.14 PEP 3127: Integer Literal Support and Syntax
----------------------------------------------------

Python 3.0 changes the syntax for octal (base-8) integer literals,
prefixing them with "0o" or "0O" instead of a leading zero, and adds
support for binary (base-2) integer literals, signalled by a "0b" or
"0B" prefix.

Python 2.6 doesn't drop support for a leading 0 signalling an octal
number, but it does add support for "0o" and "0b":

     >>> 0o21, 2*8 + 1
     (17, 17)
     >>> 0b101111
     47

The *note oct(): 1261. builtin still returns numbers prefixed with a
leading zero, and a new *note bin(): 123f. builtin returns the binary
representation for a number:

     >>> oct(42)
     '052'
     >>> future_builtins.oct(42)
     '0o52'
     >>> bin(173)
     '0b10101101'

The *note int(): 23c. and ‘long()’ builtins will now accept the "0o" and
"0b" prefixes when base-8 or base-2 are requested, or when the 'base'
argument is zero (signalling that the base used should be determined
from the string):

     >>> int ('0o52', 0)
     42
     >>> int('1101', 2)
     13
     >>> int('0b1101', 2)
     13
     >>> int('0b1101', 0)
     13

也參考
......

PEP 3127(1) - Integer Literal Support and Syntax

     PEP written by Patrick Maupin; backported to 2.6 by Eric Smith.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3127/


File: python.info,  Node: PEP 3129 Class Decorators,  Next: PEP 3141 A Type Hierarchy for Numbers,  Prev: PEP 3127 Integer Literal Support and Syntax,  Up: Python 2 6 有什麼新功能

1.16.15 PEP 3129: Class Decorators
----------------------------------

Decorators have been extended from functions to classes.  It's now legal
to write:

     @foo
     @bar
     class A:
       pass

This is equivalent to:

     class A:
       pass

     A = foo(bar(A))

也參考
......

PEP 3129(1) - Class Decorators

     由 Collin Winter 撰寫 PEP。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3129/


File: python.info,  Node: PEP 3141 A Type Hierarchy for Numbers,  Next: 其他語言更動<14>,  Prev: PEP 3129 Class Decorators,  Up: Python 2 6 有什麼新功能

1.16.16 PEP 3141: A Type Hierarchy for Numbers
----------------------------------------------

Python 3.0 adds several abstract base classes for numeric types inspired
by Scheme's numeric tower.  These classes were backported to 2.6 as the
*note numbers: 8e. module.

The most general ABC is ‘Number’.  It defines no operations at all, and
only exists to allow checking if an object is a number by doing
‘isinstance(obj, Number)’.

‘Complex’ is a subclass of ‘Number’.  Complex numbers can undergo the
basic operations of addition, subtraction, multiplication, division, and
exponentiation, and you can retrieve the real and imaginary parts and
obtain a number's conjugate.  Python's built-in complex type is an
implementation of ‘Complex’.

‘Real’ further derives from ‘Complex’, and adds operations that only
work on real numbers: ‘floor()’, ‘trunc()’, rounding, taking the
remainder mod N, floor division, and comparisons.

‘Rational’ numbers derive from ‘Real’, have ‘numerator’ and
‘denominator’ properties, and can be converted to floats.  Python 2.6
adds a simple rational-number class, ‘Fraction’, in the *note fractions:
53. module.  (It's called ‘Fraction’ instead of ‘Rational’ to avoid a
name clash with *note numbers.Rational: 1255.)

‘Integral’ numbers derive from ‘Rational’, and can be shifted left and
right with ‘<<’ and ‘>>’, combined using bitwise operations such as ‘&’
and ‘|’, and can be used as array indexes and slice boundaries.

In Python 3.0, the PEP slightly redefines the existing builtins *note
round(): 126d, *note math.floor(): 132f, *note math.ceil(): 1330, and
adds a new one, *note math.trunc(): 1331, that's been backported to
Python 2.6.  *note math.trunc(): 1331. rounds toward zero, returning the
closest ‘Integral’ that's between the function's argument and zero.

也參考
......

PEP 3141(1) - A Type Hierarchy for Numbers

     由 Jeffrey Yasskin 撰寫 PEP。

Scheme's numerical tower(2), from the Guile manual.

Scheme's number datatypes(3) from the R5RS Scheme specification.

* Menu:

* The fractions Module::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3141/

   (2) 
https://www.gnu.org/software/guile/manual/html_node/Numerical-Tower.html#Numerical-Tower

   (3) 
https://conservatory.scheme.org/schemers/Documents/Standards/R5RS/HTML/r5rs-Z-H-9.html#%_sec_6.2


File: python.info,  Node: The fractions Module,  Up: PEP 3141 A Type Hierarchy for Numbers

1.16.16.1 The ‘fractions’ Module
................................

To fill out the hierarchy of numeric types, the *note fractions: 53.
module provides a rational-number class.  Rational numbers store their
values as a numerator and denominator forming a fraction, and can
exactly represent numbers such as ‘2/3’ that floating-point numbers can
only approximate.

The ‘Fraction’ constructor takes two ‘Integral’ values that will be the
numerator and denominator of the resulting fraction.

     >>> from fractions import Fraction
     >>> a = Fraction(2, 3)
     >>> b = Fraction(2, 5)
     >>> float(a), float(b)
     (0.66666666666666663, 0.40000000000000002)
     >>> a+b
     Fraction(16, 15)
     >>> a/b
     Fraction(5, 3)

For converting floating-point numbers to rationals, the float type now
has an ‘as_integer_ratio()’ method that returns the numerator and
denominator for a fraction that evaluates to the same floating-point
value:

     >>> (2.5) .as_integer_ratio()
     (5, 2)
     >>> (3.1415) .as_integer_ratio()
     (7074029114692207L, 2251799813685248L)
     >>> (1./3) .as_integer_ratio()
     (6004799503160661L, 18014398509481984L)

Note that values that can only be approximated by floating-point
numbers, such as 1./3, are not simplified to the number being
approximated; the fraction attempts to match the floating-point value
'exactly'.

The *note fractions: 53. module is based upon an implementation by
Sjoerd Mullender that was in Python's ‘Demo/classes/’ directory for a
long time.  This implementation was significantly updated by Jeffrey
Yasskin.


File: python.info,  Node: 其他語言更動<14>,  Next: New and Improved Modules<2>,  Prev: PEP 3141 A Type Hierarchy for Numbers,  Up: Python 2 6 有什麼新功能

1.16.17 其他語言更動
--------------------

Some smaller changes made to the core Python language are:

   * Directories and zip archives containing a ‘__main__.py’ file can
     now be executed directly by passing their name to the interpreter.
     The directory or zip archive is automatically inserted as the first
     entry in sys.path.  (Suggestion and initial patch by Andy Chu,
     subsequently revised by Phillip J. Eby and Nick Coghlan;
     bpo-1739468(1).)

   * The *note hasattr(): 479. function was catching and ignoring all
     errors, under the assumption that they meant a ‘__getattr__()’
     method was failing somehow and the return value of *note hasattr():
     479. would therefore be ‘False’.  This logic shouldn't be applied
     to *note KeyboardInterrupt: 975. and *note SystemExit: ce7,
     however; Python 2.6 will no longer discard such exceptions when
     *note hasattr(): 479. encounters them.  (Fixed by Benjamin
     Peterson; bpo-2196(2).)

   * When calling a function using the ‘**’ syntax to provide keyword
     arguments, you are no longer required to use a Python dictionary;
     any mapping will now work:

          >>> def f(**kw):
          ...    print sorted(kw)
          ...
          >>> ud=UserDict.UserDict()
          >>> ud['a'] = 1
          >>> ud['b'] = 'string'
          >>> f(**ud)
          ['a', 'b']

     （由 Alexander Belopolsky 所貢獻；bpo-1686487(3)。）

     It's also become legal to provide keyword arguments after a ‘*args’
     argument to a function call.

          >>> def f(*args, **kw):
          ...     print args, kw
          ...
          >>> f(1,2,3, *(4,5,6), keyword=13)
          (1, 2, 3, 4, 5, 6) {'keyword': 13}

     Previously this would have been a syntax error.  (Contributed by
     Amaury Forgeot d'Arc; bpo-3473(4).)

   * A new builtin, ‘next(iterator, [default])’ returns the next item
     from the specified iterator.  If the 'default' argument is
     supplied, it will be returned if 'iterator' has been exhausted;
     otherwise, the *note StopIteration: ba1. exception will be raised.
     (Backported in bpo-2719(5).)

   * Tuples now have ‘index()’ and ‘count()’ methods matching the list
     type's ‘index()’ and ‘count()’ methods:

          >>> t = (0,1,2,3,4,0,1,2)
          >>> t.index(3)
          3
          >>> t.count(0)
          2

     （由 Raymond Hettinger 所貢獻。）

   * The built-in types now have improved support for extended slicing
     syntax, accepting various combinations of ‘(start, stop, step)’.
     Previously, the support was partial and certain corner cases
     wouldn't work.  (Implemented by Thomas Wouters.)

   * Properties now have three attributes, ‘getter’, ‘setter’ and
     ‘deleter’, that are decorators providing useful shortcuts for
     adding a getter, setter or deleter function to an existing
     property.  You would use them like this:

          class C(object):
              @property
              def x(self):
                  return self._x

              @x.setter
              def x(self, value):
                  self._x = value

              @x.deleter
              def x(self):
                  del self._x

          class D(C):
              @C.x.getter
              def x(self):
                  return self._x * 2

              @x.setter
              def x(self, value):
                  self._x = value / 2

   * Several methods of the built-in set types now accept multiple
     iterables: ‘intersection()’, ‘intersection_update()’, ‘union()’,
     ‘update()’, ‘difference()’ and ‘difference_update()’.

          >>> s=set('1234567890')
          >>> s.intersection('abc123', 'cdf246')  # Intersection between all inputs
          set(['2'])
          >>> s.difference('246', '789')
          set(['1', '0', '3', '5'])

     （由 Raymond Hettinger 所貢獻。）

   * Many floating-point features were added.  The *note float(): 2c8.
     function will now turn the string ‘nan’ into an IEEE 754 Not A
     Number value, and ‘+inf’ and ‘-inf’ into positive or negative
     infinity.  This works on any platform with IEEE 754 semantics.
     (Contributed by Christian Heimes; bpo-1635(6).)

     Other functions in the *note math: 81. module, ‘isinf()’ and
     ‘isnan()’, return true if their floating-point argument is infinite
     or Not A Number.  (bpo-1640(7))

     Conversion functions were added to convert floating-point numbers
     into hexadecimal strings (bpo-3008(8)).  These functions convert
     floats to and from a string representation without introducing
     rounding errors from the conversion between decimal and binary.
     Floats have a *note hex(): 1262. method that returns a string
     representation, and the ‘float.fromhex()’ method converts a string
     back into a number:

          >>> a = 3.75
          >>> a.hex()
          '0x1.e000000000000p+1'
          >>> float.fromhex('0x1.e000000000000p+1')
          3.75
          >>> b=1./3
          >>> b.hex()
          '0x1.5555555555555p-2'

   * A numerical nicety: when creating a complex number from two floats
     on systems that support signed zeros (-0 and +0), the *note
     complex(): 2c9. constructor will now preserve the sign of the zero.
     (Fixed by Mark T. Dickinson; bpo-1507(9).)

   * Classes that inherit a ‘__hash__()’ method from a parent class can
     set ‘__hash__ = None’ to indicate that the class isn't hashable.
     This will make ‘hash(obj)’ raise a *note TypeError: 4dd. and the
     class will not be indicated as implementing the ‘Hashable’ ABC.

     You should do this when you've defined a ‘__cmp__()’ or ‘__eq__()’
     method that compares objects by their value rather than by
     identity.  All objects have a default hash method that uses
     ‘id(obj)’ as the hash value.  There's no tidy way to remove the
     ‘__hash__()’ method inherited from a parent class, so assigning
     ‘None’ was implemented as an override.  At the C level, extensions
     can set ‘tp_hash’ to *note PyObject_HashNotImplemented(): 1334.
     (Fixed by Nick Coghlan and Amaury Forgeot d'Arc; bpo-2235(10).)

   * The *note GeneratorExit: 1335. exception now subclasses *note
     BaseException: 55f. instead of *note Exception: 97d.  This means
     that an exception handler that does ‘except Exception:’ will not
     inadvertently catch *note GeneratorExit: 1335.  (Contributed by
     Chad Austin; bpo-1537(11).)

   * Generator objects now have a ‘gi_code’ attribute that refers to the
     original code object backing the generator.  (Contributed by Collin
     Winter; bpo-1473257(12).)

   * The *note compile(): 178. built-in function now accepts keyword
     arguments as well as positional parameters.  (Contributed by Thomas
     Wouters; bpo-1444529(13).)

   * The *note complex(): 2c9. constructor now accepts strings
     containing parenthesized complex numbers, meaning that
     ‘complex(repr(cplx))’ will now round-trip values.  For example,
     ‘complex('(3+4j)')’ now returns the value (3+4j).
     (bpo-1491866(14))

   * The string ‘translate()’ method now accepts ‘None’ as the
     translation table parameter, which is treated as the identity
     transformation.  This makes it easier to carry out operations that
     only delete characters.  (Contributed by Bengt Richter and
     implemented by Raymond Hettinger; bpo-1193128(15).)

   * The built-in *note dir(): 5d8. function now checks for a
     ‘__dir__()’ method on the objects it receives.  This method must
     return a list of strings containing the names of valid attributes
     for the object, and lets the object control the value that *note
     dir(): 5d8. produces.  Objects that have ‘__getattr__()’ or
     ‘__getattribute__()’ methods can use this to advertise
     pseudo-attributes they will honor.  (bpo-1591665(16))

   * Instance method objects have new attributes for the object and
     function comprising the method; the new synonym for ‘im_self’ is
     *note __self__: 1336, and ‘im_func’ is also available as *note
     __func__: 128f.  The old names are still supported in Python 2.6,
     but are gone in 3.0.

   * An obscure change: when you use the *note locals(): 127. function
     inside a *note class: 126a. statement, the resulting dictionary no
     longer returns free variables.  (Free variables, in this case, are
     variables referenced in the ‘class’ statement that aren't
     attributes of the class.)

* Menu:

* 最佳化: 最佳化<13>.
* Interpreter Changes: Interpreter Changes<2>.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1739468

   (2) https://bugs.python.org/issue?@action=redirect&bpo=2196

   (3) https://bugs.python.org/issue?@action=redirect&bpo=1686487

   (4) https://bugs.python.org/issue?@action=redirect&bpo=3473

   (5) https://bugs.python.org/issue?@action=redirect&bpo=2719

   (6) https://bugs.python.org/issue?@action=redirect&bpo=1635

   (7) https://bugs.python.org/issue?@action=redirect&bpo=1640

   (8) https://bugs.python.org/issue?@action=redirect&bpo=3008

   (9) https://bugs.python.org/issue?@action=redirect&bpo=1507

   (10) https://bugs.python.org/issue?@action=redirect&bpo=2235

   (11) https://bugs.python.org/issue?@action=redirect&bpo=1537

   (12) https://bugs.python.org/issue?@action=redirect&bpo=1473257

   (13) https://bugs.python.org/issue?@action=redirect&bpo=1444529

   (14) https://bugs.python.org/issue?@action=redirect&bpo=1491866

   (15) https://bugs.python.org/issue?@action=redirect&bpo=1193128

   (16) https://bugs.python.org/issue?@action=redirect&bpo=1591665


File: python.info,  Node: 最佳化<13>,  Next: Interpreter Changes<2>,  Up: 其他語言更動<14>

1.16.17.1 最佳化
................

   * The *note warnings: fa. module has been rewritten in C. This makes
     it possible to invoke warnings from the parser, and may also make
     the interpreter's startup faster.  (Contributed by Neal Norwitz and
     Brett Cannon; bpo-1631171(1).)

   * Type objects now have a cache of methods that can reduce the work
     required to find the correct method implementation for a particular
     class; once cached, the interpreter doesn't need to traverse base
     classes to figure out the right method to call.  The cache is
     cleared if a base class or the class itself is modified, so the
     cache should remain correct even in the face of Python's dynamic
     nature.  (Original optimization implemented by Armin Rigo, updated
     for Python 2.6 by Kevin Jacobs; bpo-1700288(2).)

     By default, this change is only applied to types that are included
     with the Python core.  Extension modules may not necessarily be
     compatible with this cache, so they must explicitly add
     ‘Py_TPFLAGS_HAVE_VERSION_TAG’ to the module's ‘tp_flags’ field to
     enable the method cache.  (To be compatible with the method cache,
     the extension module's code must not directly access and modify the
     ‘tp_dict’ member of any of the types it implements.  Most modules
     don't do this, but it's impossible for the Python interpreter to
     determine that.  See bpo-1878(3) for some discussion.)

   * Function calls that use keyword arguments are significantly faster
     by doing a quick pointer comparison, usually saving the time of a
     full string comparison.  (Contributed by Raymond Hettinger, after
     an initial implementation by Antoine Pitrou; bpo-1819(4).)

   * All of the functions in the *note struct: c0. module have been
     rewritten in C, thanks to work at the Need For Speed sprint.
     (Contributed by Raymond Hettinger.)

   * Some of the standard built-in types now set a bit in their type
     objects.  This speeds up checking whether an object is a subclass
     of one of these types.  (Contributed by Neal Norwitz.)

   * Unicode strings now use faster code for detecting whitespace and
     line breaks; this speeds up the ‘split()’ method by about 25% and
     ‘splitlines()’ by 35%.  (Contributed by Antoine Pitrou.)  Memory
     usage is reduced by using pymalloc for the Unicode string's data.

   * The ‘with’ statement now stores the *note __exit__(): 1293. method
     on the stack, producing a small speedup.  (Implemented by Jeffrey
     Yasskin.)

   * To reduce memory usage, the garbage collector will now clear
     internal free lists when garbage-collecting the highest generation
     of objects.  This may return memory to the operating system sooner.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1631171

   (2) https://bugs.python.org/issue?@action=redirect&bpo=1700288

   (3) https://bugs.python.org/issue?@action=redirect&bpo=1878

   (4) https://bugs.python.org/issue?@action=redirect&bpo=1819


File: python.info,  Node: Interpreter Changes<2>,  Prev: 最佳化<13>,  Up: 其他語言更動<14>

1.16.17.2 Interpreter Changes
.............................

Two command-line options have been reserved for use by other Python
implementations.  The *note -J: 133a. switch has been reserved for use
by Jython for Jython-specific options, such as switches that are passed
to the underlying JVM. *note -X: 15a. has been reserved for options
specific to a particular implementation of Python such as CPython,
Jython, or IronPython.  If either option is used with Python 2.6, the
interpreter will report that the option isn't currently used.

Python can now be prevented from writing ‘.pyc’ or ‘.pyo’ files by
supplying the *note -B: 133b. switch to the Python interpreter, or by
setting the *note PYTHONDONTWRITEBYTECODE: 133c. environment variable
before running the interpreter.  This setting is available to Python
programs as the ‘sys.dont_write_bytecode’ variable, and Python code can
change the value to modify the interpreter's behaviour.  (Contributed by
Neal Norwitz and Georg Brandl.)

The encoding used for standard input, output, and standard error can be
specified by setting the *note PYTHONIOENCODING: fab. environment
variable before running the interpreter.  The value should be a string
in the form ‘<encoding>’ or ‘<encoding>:<errorhandler>’.  The 'encoding'
part specifies the encoding's name, e.g.  ‘utf-8’ or ‘latin-1’; the
optional 'errorhandler' part specifies what to do with characters that
can't be handled by the encoding, and should be one of "error",
"ignore", or "replace".  (Contributed by Martin von Löwis.)


File: python.info,  Node: New and Improved Modules<2>,  Next: Deprecations and Removals,  Prev: 其他語言更動<14>,  Up: Python 2 6 有什麼新功能

1.16.18 New and Improved Modules
--------------------------------

As in every release, Python's standard library received a number of
enhancements and bug fixes.  Here's a partial list of the most notable
changes, sorted alphabetically by module name.  Consult the ‘Misc/NEWS’
file in the source tree for a more complete list of changes, or look
through the Subversion logs for all the details.

   * The ‘asyncore’ and ‘asynchat’ modules are being actively maintained
     again, and a number of patches and bugfixes were applied.
     (Maintained by Josiah Carlson; see bpo-1736190(1) for one patch.)

   * The ‘bsddb’ module also has a new maintainer, Jesús Cea Avión, and
     the package is now available as a standalone package.  The web page
     for the package is www.jcea.es/programacion/pybsddb.htm(2).  The
     plan is to remove the package from the standard library in Python
     3.0, because its pace of releases is much more frequent than
     Python's.

     The ‘bsddb.dbshelve’ module now uses the highest pickling protocol
     available, instead of restricting itself to protocol 1.
     (Contributed by W. Barnes.)

   * The ‘cgi’ module will now read variables from the query string of
     an HTTP POST request.  This makes it possible to use form actions
     with URLs that include query strings such as
     "/cgi-bin/add.py?category=1".  (Contributed by Alexandre Fiori and
     Nubis; bpo-1817(3).)

     The ‘parse_qs()’ and ‘parse_qsl()’ functions have been relocated
     from the ‘cgi’ module to the *note urlparse: f3. module.  The
     versions still available in the ‘cgi’ module will trigger *note
     PendingDeprecationWarning: 86d. messages in 2.6 (bpo-600362(4)).

   * The *note cmath: 11. module underwent extensive revision,
     contributed by Mark Dickinson and Christian Heimes.  Five new
     functions were added:

        * ‘polar()’ converts a complex number to polar form, returning
          the modulus and argument of the complex number.

        * ‘rect()’ does the opposite, turning a modulus, argument pair
          back into the corresponding complex number.

        * ‘phase()’ returns the argument (also called the angle) of a
          complex number.

        * ‘isnan()’ returns True if either the real or imaginary part of
          its argument is a NaN.

        * ‘isinf()’ returns True if either the real or imaginary part of
          its argument is infinite.

     The revisions also improved the numerical soundness of the *note
     cmath: 11. module.  For all functions, the real and imaginary parts
     of the results are accurate to within a few units of least
     precision (ulps) whenever possible.  See bpo-1381(5) for the
     details.  The branch cuts for ‘asinh()’, ‘atanh()’: and ‘atan()’
     have also been corrected.

     The tests for the module have been greatly expanded; nearly 2000
     new test cases exercise the algebraic functions.

     On IEEE 754 platforms, the *note cmath: 11. module now handles IEEE
     754 special values and floating-point exceptions in a manner
     consistent with Annex 'G' of the C99 standard.

   * A new data type in the *note collections: 16. module:
     ‘namedtuple(typename, fieldnames)’ is a factory function that
     creates subclasses of the standard tuple whose fields are
     accessible by name as well as index.  For example:

          >>> var_type = collections.namedtuple('variable',
          ...             'id name type size')
          >>> # Names are separated by spaces or commas.
          >>> # 'id, name, type, size' would also work.
          >>> var_type._fields
          ('id', 'name', 'type', 'size')

          >>> var = var_type(1, 'frequency', 'int', 4)
          >>> print var[0], var.id    # Equivalent
          1 1
          >>> print var[2], var.type  # Equivalent
          int int
          >>> var._asdict()
          {'size': 4, 'type': 'int', 'id': 1, 'name': 'frequency'}
          >>> v2 = var._replace(name='amplitude')
          >>> v2
          variable(id=1, name='amplitude', type='int', size=4)

     Several places in the standard library that returned tuples have
     been modified to return ‘namedtuple()’ instances.  For example, the
     ‘Decimal.as_tuple()’ method now returns a named tuple with ‘sign’,
     ‘digits’, and ‘exponent’ fields.

     （由 Raymond Hettinger 所貢獻。）

   * Another change to the *note collections: 16. module is that the
     ‘deque’ type now supports an optional 'maxlen' parameter; if
     supplied, the deque's size will be restricted to no more than
     'maxlen' items.  Adding more items to a full deque causes old items
     to be discarded.

          >>> from collections import deque
          >>> dq=deque(maxlen=3)
          >>> dq
          deque([], maxlen=3)
          >>> dq.append(1); dq.append(2); dq.append(3)
          >>> dq
          deque([1, 2, 3], maxlen=3)
          >>> dq.append(4)
          >>> dq
          deque([2, 3, 4], maxlen=3)

     （由 Raymond Hettinger 所貢獻。）

   * The *note Cookie: 67. module's *note Morsel: bab. objects now
     support an *note httponly: 133e. attribute.  In some browsers.
     cookies with this attribute set cannot be accessed or manipulated
     by JavaScript code.  (Contributed by Arvin Schnell;
     bpo-1638033(6).)

   * A new window method in the *note curses: 23. module, ‘chgat()’,
     changes the display attributes for a certain number of characters
     on a single line.  (Contributed by Fabian Kreutz.)

          # Boldface text starting at y=0,x=21
          # and affecting the rest of the line.
          stdscr.chgat(0, 21, curses.A_BOLD)

     The ‘Textbox’ class in the *note curses.textpad: 26. module now
     supports editing in insert mode as well as overwrite mode.  Insert
     mode is enabled by supplying a true value for the 'insert_mode'
     parameter when creating the ‘Textbox’ instance.

   * The *note datetime: 28. module's ‘strftime()’ methods now support a
     ‘%f’ format code that expands to the number of microseconds in the
     object, zero-padded on the left to six places.  (Contributed by
     Skip Montanaro; bpo-1158(7).)

   * The *note decimal: 2e. module was updated to version 1.66 of the
     General Decimal Specification(8).  New features include some
     methods for some basic mathematical functions such as ‘exp()’ and
     ‘log10()’:

          >>> Decimal(1).exp()
          Decimal("2.718281828459045235360287471")
          >>> Decimal("2.7182818").ln()
          Decimal("0.9999999895305022877376682436")
          >>> Decimal(1000).log10()
          Decimal("3")

     The ‘as_tuple()’ method of ‘Decimal’ objects now returns a named
     tuple with ‘sign’, ‘digits’, and ‘exponent’ fields.

     (Implemented by Facundo Batista and Mark Dickinson.  Named tuple
     support added by Raymond Hettinger.)

   * The *note difflib: 2f. module's ‘SequenceMatcher’ class now returns
     named tuples representing matches, with ‘a’, ‘b’, and ‘size’
     attributes.  (Contributed by Raymond Hettinger.)

   * An optional ‘timeout’ parameter, specifying a timeout measured in
     seconds, was added to the *note ftplib.FTP: 89f. class constructor
     as well as the ‘connect()’ method.  (Added by Facundo Batista.)
     Also, the ‘FTP’ class's ‘storbinary()’ and ‘storlines()’ now take
     an optional 'callback' parameter that will be called with each
     block of data after the data has been sent.  (Contributed by Phil
     Schwartz; bpo-1221598(9).)

   * The ‘reduce()’ built-in function is also available in the *note
     functools: 55. module.  In Python 3.0, the builtin has been dropped
     and ‘reduce()’ is only available from *note functools: 55.;
     currently there are no plans to drop the builtin in the 2.x series.
     (Patched by Christian Heimes; bpo-1739906(10).)

   * When possible, the *note getpass: 58. module will now use
     ‘/dev/tty’ to print a prompt message and read the password, falling
     back to standard error and standard input.  If the password may be
     echoed to the terminal, a warning is printed before the prompt is
     displayed.  (Contributed by Gregory P. Smith.)

   * The *note glob.glob(): 280. function can now return Unicode
     filenames if a Unicode path was used and Unicode filenames are
     matched within the directory.  (bpo-1001604(11))

   * A new function in the *note heapq: 5f. module, ‘merge(iter1, iter2,
     ...)’, takes any number of iterables returning data in sorted
     order, and returns a new generator that returns the contents of all
     the iterators, also in sorted order.  For example:

          >>> list(heapq.merge([1, 3, 5, 9], [2, 8, 16]))
          [1, 2, 3, 5, 8, 9, 16]

     Another new function, ‘heappushpop(heap, item)’, pushes 'item' onto
     'heap', then pops off and returns the smallest item.  This is more
     efficient than making a call to ‘heappush()’ and then ‘heappop()’.

     *note heapq: 5f. is now implemented to only use less-than
     comparison, instead of the less-than-or-equal comparison it
     previously used.  This makes *note heapq: 5f.'s usage of a type
     match the *note list.sort(): b76. method.  (Contributed by Raymond
     Hettinger.)

   * An optional ‘timeout’ parameter, specifying a timeout measured in
     seconds, was added to the *note httplib.HTTPConnection: ae4. and
     *note HTTPSConnection: ae5. class constructors.  (Added by Facundo
     Batista.)

   * Most of the *note inspect: 72. module's functions, such as
     ‘getmoduleinfo()’ and ‘getargs()’, now return named tuples.  In
     addition to behaving like tuples, the elements of the return value
     can also be accessed as attributes.  (Contributed by Raymond
     Hettinger.)

     Some new functions in the module include ‘isgenerator()’,
     ‘isgeneratorfunction()’, and ‘isabstract()’.

   * The *note itertools: 75. module gained several new functions.

     ‘izip_longest(iter1, iter2, ...[, fillvalue])’ makes tuples from
     each of the elements; if some of the iterables are shorter than
     others, the missing values are set to 'fillvalue'.  For example:

          >>> tuple(itertools.izip_longest([1,2,3], [1,2,3,4,5]))
          ((1, 1), (2, 2), (3, 3), (None, 4), (None, 5))

     ‘product(iter1, iter2, ..., [repeat=N])’ returns the Cartesian
     product of the supplied iterables, a set of tuples containing every
     possible combination of the elements returned from each iterable.

          >>> list(itertools.product([1,2,3], [4,5,6]))
          [(1, 4), (1, 5), (1, 6),
           (2, 4), (2, 5), (2, 6),
           (3, 4), (3, 5), (3, 6)]

     The optional 'repeat' keyword argument is used for taking the
     product of an iterable or a set of iterables with themselves,
     repeated 'N' times.  With a single iterable argument, 'N'-tuples
     are returned:

          >>> list(itertools.product([1,2], repeat=3))
          [(1, 1, 1), (1, 1, 2), (1, 2, 1), (1, 2, 2),
           (2, 1, 1), (2, 1, 2), (2, 2, 1), (2, 2, 2)]

     With two iterables, '2N'-tuples are returned.

          >>> list(itertools.product([1,2], [3,4], repeat=2))
          [(1, 3, 1, 3), (1, 3, 1, 4), (1, 3, 2, 3), (1, 3, 2, 4),
           (1, 4, 1, 3), (1, 4, 1, 4), (1, 4, 2, 3), (1, 4, 2, 4),
           (2, 3, 1, 3), (2, 3, 1, 4), (2, 3, 2, 3), (2, 3, 2, 4),
           (2, 4, 1, 3), (2, 4, 1, 4), (2, 4, 2, 3), (2, 4, 2, 4)]

     ‘combinations(iterable, r)’ returns sub-sequences of length 'r'
     from the elements of 'iterable'.

          >>> list(itertools.combinations('123', 2))
          [('1', '2'), ('1', '3'), ('2', '3')]
          >>> list(itertools.combinations('123', 3))
          [('1', '2', '3')]
          >>> list(itertools.combinations('1234', 3))
          [('1', '2', '3'), ('1', '2', '4'),
           ('1', '3', '4'), ('2', '3', '4')]

     ‘permutations(iter[, r])’ returns all the permutations of length
     'r' of the iterable's elements.  If 'r' is not specified, it will
     default to the number of elements produced by the iterable.

          >>> list(itertools.permutations([1,2,3,4], 2))
          [(1, 2), (1, 3), (1, 4),
           (2, 1), (2, 3), (2, 4),
           (3, 1), (3, 2), (3, 4),
           (4, 1), (4, 2), (4, 3)]

     ‘itertools.chain(*iterables)’ is an existing function in *note
     itertools: 75. that gained a new constructor in Python 2.6.
     ‘itertools.chain.from_iterable(iterable)’ takes a single iterable
     that should return other iterables.  ‘chain()’ will then return all
     the elements of the first iterable, then all the elements of the
     second, and so on.

          >>> list(itertools.chain.from_iterable([[1,2,3], [4,5,6]]))
          [1, 2, 3, 4, 5, 6]

     (All contributed by Raymond Hettinger.)

   * The *note logging: 7b. module's ‘FileHandler’ class and its
     subclasses ‘WatchedFileHandler’, ‘RotatingFileHandler’, and
     ‘TimedRotatingFileHandler’ now have an optional 'delay' parameter
     to their constructors.  If 'delay' is true, opening of the log file
     is deferred until the first ‘emit()’ call is made.  (Contributed by
     Vinay Sajip.)

     ‘TimedRotatingFileHandler’ also has a 'utc' constructor parameter.
     If the argument is true, UTC time will be used in determining when
     midnight occurs and in generating filenames; otherwise local time
     will be used.

   * Several new functions were added to the *note math: 81. module:

        * *note isinf(): 133f. and *note isnan(): 1340. determine
          whether a given float is a (positive or negative) infinity or
          a NaN (Not a Number), respectively.

        * *note copysign(): 1341. copies the sign bit of an IEEE 754
          number, returning the absolute value of 'x' combined with the
          sign bit of 'y'.  For example, ‘math.copysign(1, -0.0)’
          returns -1.0.  (Contributed by Christian Heimes.)

        * *note factorial(): 8eb. computes the factorial of a number.
          (Contributed by Raymond Hettinger; bpo-2138(12).)

        * *note fsum(): 1342. adds up the stream of numbers from an
          iterable, and is careful to avoid loss of precision through
          using partial sums.  (Contributed by Jean Brouwers, Raymond
          Hettinger, and Mark Dickinson; bpo-2819(13).)

        * *note acosh(): 1343, *note asinh(): 1344. and *note atanh():
          1345. compute the inverse hyperbolic functions.

        * *note log1p(): 1346. returns the natural logarithm of '1+x'
          (base 'e').

        * ‘trunc()’ rounds a number toward zero, returning the closest
          ‘Integral’ that's between the function's argument and zero.
          Added as part of the backport of *note PEP 3141's type
          hierarchy for numbers: 1254.

   * The *note math: 81. module has been improved to give more
     consistent behaviour across platforms, especially with respect to
     handling of floating-point exceptions and IEEE 754 special values.

     Whenever possible, the module follows the recommendations of the
     C99 standard about 754's special values.  For example, ‘sqrt(-1.)’
     should now give a *note ValueError: 1e7. across almost all
     platforms, while ‘sqrt(float('NaN'))’ should return a NaN on all
     IEEE 754 platforms.  Where Annex 'F' of the C99 standard recommends
     signaling 'divide-by-zero' or 'invalid', Python will raise *note
     ValueError: 1e7.  Where Annex 'F' of the C99 standard recommends
     signaling 'overflow', Python will raise *note OverflowError: 825.
     (See bpo-711019(14) and bpo-1640(15).)

     （由 Christian Heimes 和 Mark Dickinson 所貢獻。）

   * *note mmap: 1f0. objects now have a ‘rfind()’ method that searches
     for a substring beginning at the end of the string and searching
     backwards.  The ‘find()’ method also gained an 'end' parameter
     giving an index at which to stop searching.  (Contributed by John
     Lenton.)

   * The *note operator: 8f. module gained a ‘methodcaller()’ function
     that takes a name and an optional set of arguments, returning a
     callable that will call the named function on any arguments passed
     to it.  For example:

          >>> # Equivalent to lambda s: s.replace('old', 'new')
          >>> replacer = operator.methodcaller('replace', 'old', 'new')
          >>> replacer('old wine in old bottles')
          'new wine in new bottles'

     （經 Gregory Petrosyan 建議後由 Georg Brandl 所貢獻。）

     The ‘attrgetter()’ function now accepts dotted names and performs
     the corresponding attribute lookups:

          >>> inst_name = operator.attrgetter(
          ...        '__class__.__name__')
          >>> inst_name('')
          'str'
          >>> inst_name(help)
          '_Helper'

     （經 Barry Warsaw 建議後由 Georg Brandl 所貢獻。）

   * The *note os: 91. module now wraps several new system calls.
     ‘fchmod(fd, mode)’ and ‘fchown(fd, uid, gid)’ change the mode and
     ownership of an opened file, and ‘lchmod(path, mode)’ changes the
     mode of a symlink.  (Contributed by Georg Brandl and Christian
     Heimes.)

     ‘chflags()’ and ‘lchflags()’ are wrappers for the corresponding
     system calls (where they're available), changing the flags set on a
     file.  Constants for the flag values are defined in the *note stat:
     bc. module; some possible values include ‘UF_IMMUTABLE’ to signal
     the file may not be changed and ‘UF_APPEND’ to indicate that data
     can only be appended to the file.  (Contributed by M. Levinson.)

     ‘os.closerange(low, high)’ efficiently closes all file descriptors
     from 'low' to 'high', ignoring any errors and not including 'high'
     itself.  This function is now used by the *note subprocess: c1.
     module to make starting processes faster.  (Contributed by Georg
     Brandl; bpo-1663329(16).)

   * The ‘os.environ’ object's ‘clear()’ method will now unset the
     environment variables using *note os.unsetenv(): 8c0. in addition
     to clearing the object's keys.  (Contributed by Martin Horcicka;
     bpo-1181(17).)

   * The *note os.walk(): 451. function now has a ‘followlinks’
     parameter.  If set to True, it will follow symlinks pointing to
     directories and visit the directory's contents.  For backward
     compatibility, the parameter's default value is false.  Note that
     the function can fall into an infinite recursion if there's a
     symlink that points to a parent directory.  (bpo-1273829(18))

   * In the *note os.path: 92. module, the ‘splitext()’ function has
     been changed to not split on leading period characters.  This
     produces better results when operating on Unix's dot-files.  For
     example, ‘os.path.splitext('.ipython')’ now returns ‘('.ipython',
     '')’ instead of ‘('', '.ipython')’.  (bpo-1115886(19))

     A new function, ‘os.path.relpath(path, start='.')’, returns a
     relative path from the ‘start’ path, if it's supplied, or from the
     current working directory to the destination ‘path’.  (Contributed
     by Richard Barran; bpo-1339796(20).)

     On Windows, *note os.path.expandvars(): 1347. will now expand
     environment variables given in the form "%var%", and "~user" will
     be expanded into the user's home directory path.  (Contributed by
     Josiah Carlson; bpo-957650(21).)

   * The Python debugger provided by the *note pdb: 94. module gained a
     new command: "run" restarts the Python program being debugged and
     can optionally take new command-line arguments for the program.
     (Contributed by Rocky Bernstein; bpo-1393667(22).)

   * The *note pdb.post_mortem(): 1348. function, used to begin
     debugging a traceback, will now use the traceback returned by *note
     sys.exc_info(): 630. if no traceback is supplied.  (Contributed by
     Facundo Batista; bpo-1106316(23).)

   * The *note pickletools: 96. module now has an ‘optimize()’ function
     that takes a string containing a pickle and removes some unused
     opcodes, returning a shorter pickle that contains the same data
     structure.  (Contributed by Raymond Hettinger.)

   * A ‘get_data()’ function was added to the *note pkgutil: 97. module
     that returns the contents of resource files included with an
     installed Python package.  For example:

          >>> import pkgutil
          >>> print pkgutil.get_data('test', 'exception_hierarchy.txt')
          BaseException
           +-- SystemExit
           +-- KeyboardInterrupt
           +-- GeneratorExit
           +-- Exception
                +-- StopIteration
                +-- StandardError
           ...

     （由 Paul Moore 貢獻；bpo-2439(24)。）

   * The ‘pyexpat’ module's ‘Parser’ objects now allow setting their
     ‘buffer_size’ attribute to change the size of the buffer used to
     hold character data.  (Contributed by Achim Gaedke; bpo-1137(25).)

   * The ‘Queue’ module now provides queue variants that retrieve
     entries in different orders.  The ‘PriorityQueue’ class stores
     queued items in a heap and retrieves them in priority order, and
     ‘LifoQueue’ retrieves the most recently added entries first,
     meaning that it behaves like a stack.  (Contributed by Raymond
     Hettinger.)

   * The *note random: a6. module's ‘Random’ objects can now be pickled
     on a 32-bit system and unpickled on a 64-bit system, and vice
     versa.  Unfortunately, this change also means that Python 2.6's
     ‘Random’ objects can't be unpickled correctly on earlier versions
     of Python.  (Contributed by Shawn Ligocki; bpo-1727780(26).)

     The new ‘triangular(low, high, mode)’ function returns random
     numbers following a triangular distribution.  The returned values
     are between 'low' and 'high', not including 'high' itself, and with
     'mode' as the most frequently occurring value in the distribution.
     (Contributed by Wladmir van der Laan and Raymond Hettinger;
     bpo-1681432(27).)

   * Long regular expression searches carried out by the *note re: a7.
     module will check for signals being delivered, so time-consuming
     searches can now be interrupted.  (Contributed by Josh Hoyt and
     Ralf Schmitt; bpo-846388(28).)

     The regular expression module is implemented by compiling bytecodes
     for a tiny regex-specific virtual machine.  Untrusted code could
     create malicious strings of bytecode directly and cause crashes, so
     Python 2.6 includes a verifier for the regex bytecode.
     (Contributed by Guido van Rossum from work for Google App Engine;
     bpo-3487(29).)

   * The *note rlcompleter: ab. module's ‘Completer.complete()’ method
     will now ignore exceptions triggered while evaluating a name.
     (Fixed by Lorenz Quack; bpo-2250(30).)

   * The *note sched: ad. module's ‘scheduler’ instances now have a
     read-only *note queue: a4. attribute that returns the contents of
     the scheduler's queue, represented as a list of named tuples with
     the fields ‘(time, priority, action, argument)’.  (Contributed by
     Raymond Hettinger; bpo-1861(31).)

   * The *note select: af. module now has wrapper functions for the
     Linux ‘epoll()’ and BSD ‘kqueue()’ system calls.  ‘modify()’ method
     was added to the existing ‘poll’ objects; ‘pollobj.modify(fd,
     eventmask)’ takes a file descriptor or file object and an event
     mask, modifying the recorded event mask for that file.
     (Contributed by Christian Heimes; bpo-1657(32).)

   * The *note shutil.copytree(): 9cd. function now has an optional
     'ignore' argument that takes a callable object.  This callable will
     receive each directory path and a list of the directory's contents,
     and returns a list of names that will be ignored, not copied.

     The *note shutil: b3. module also provides an ‘ignore_patterns()’
     function for use with this new parameter.  ‘ignore_patterns()’
     takes an arbitrary number of glob-style patterns and returns a
     callable that will ignore any files and directories that match any
     of these patterns.  The following example copies a directory tree,
     but skips both ‘.svn’ directories and Emacs backup files, which
     have names ending with '~':

          shutil.copytree('Doc/library', '/tmp/library',
                          ignore=shutil.ignore_patterns('*~', '.svn'))

     （由 Tarek Ziadé 貢獻；bpo-2663(33)。）

   * Integrating signal handling with GUI handling event loops like
     those used by Tkinter or GTk+ has long been a problem; most
     software ends up polling, waking up every fraction of a second to
     check if any GUI events have occurred.  The *note signal: b4.
     module can now make this more efficient.  Calling
     ‘signal.set_wakeup_fd(fd)’ sets a file descriptor to be used; when
     a signal is received, a byte is written to that file descriptor.
     There's also a C-level function, *note PySignal_SetWakeupFd():
     1349, for setting the descriptor.

     Event loops will use this by opening a pipe to create two
     descriptors, one for reading and one for writing.  The writable
     descriptor will be passed to ‘set_wakeup_fd()’, and the readable
     descriptor will be added to the list of descriptors monitored by
     the event loop via ‘select()’ or ‘poll()’.  On receiving a signal,
     a byte will be written and the main event loop will be woken up,
     avoiding the need to poll.

     （由 Adam Olsen 貢獻；bpo-1583(34)。）

     The ‘siginterrupt()’ function is now available from Python code,
     and allows changing whether signals can interrupt system calls or
     not.  (Contributed by Ralf Schmitt.)

     The ‘setitimer()’ and ‘getitimer()’ functions have also been added
     (where they're available).  ‘setitimer()’ allows setting interval
     timers that will cause a signal to be delivered to the process
     after a specified time, measured in wall-clock time, consumed
     process time, or combined process+system time.  (Contributed by
     Guilherme Polo; bpo-2240(35).)

   * The *note smtplib: b7. module now supports SMTP over SSL thanks to
     the addition of the ‘SMTP_SSL’ class.  This class supports an
     interface identical to the existing ‘SMTP’ class.  (Contributed by
     Monty Taylor.)  Both class constructors also have an optional
     ‘timeout’ parameter that specifies a timeout for the initial
     connection attempt, measured in seconds.  (Contributed by Facundo
     Batista.)

     An implementation of the LMTP protocol ( RFC 2033(36)) was also
     added to the module.  LMTP is used in place of SMTP when
     transferring e-mail between agents that don't manage a mail queue.
     (LMTP implemented by Leif Hedstrom; bpo-957003(37).)

     ‘SMTP.starttls()’ now complies with RFC 3207(38) and forgets any
     knowledge obtained from the server not obtained from the TLS
     negotiation itself.  (Patch contributed by Bill Fenner;
     bpo-829951(39).)

   * The *note socket: b8. module now supports TIPC
     (‘https://tipc.sourceforge.net/’), a high-performance non-IP-based
     protocol designed for use in clustered environments.  TIPC
     addresses are 4- or 5-tuples.  (Contributed by Alberto Bertogli;
     bpo-1646(40).)

     A new function, ‘create_connection()’, takes an address and
     connects to it using an optional timeout value, returning the
     connected socket object.  This function also looks up the address's
     type and connects to it using IPv4 or IPv6 as appropriate.
     Changing your code to use ‘create_connection()’ instead of
     ‘socket(socket.AF_INET, ...)’ may be all that's required to make
     your code work with IPv6.

   * The base classes in the *note SocketServer: b9. module now support
     calling a *note handle_timeout(): 12b5. method after a span of
     inactivity specified by the server's *note timeout: 12b4.
     attribute.  (Contributed by Michael Pomraning.)  The *note
     serve_forever(): 10d8. method now takes an optional poll interval
     measured in seconds, controlling how often the server will check
     for a shutdown request.  (Contributed by Pedro Werneck and Jeffrey
     Yasskin; bpo-742598(41), bpo-1193577(42).)

   * The *note sqlite3: ba. module, maintained by Gerhard Häring, has
     been updated from version 2.3.2 in Python 2.5 to version 2.4.1.

   * The *note struct: c0. module now supports the C99 _Bool type, using
     the format character ‘'?'’.  (Contributed by David Remahl.)

   * The *note Popen: 17d. objects provided by the *note subprocess: c1.
     module now have *note terminate(): 134a, *note kill(): 134b, and
     *note send_signal(): 134c. methods.  On Windows, ‘send_signal()’
     only supports the *note SIGTERM: 134d. signal, and all these
     methods are aliases for the Win32 API function
     ‘TerminateProcess()’.  (Contributed by Christian Heimes.)

   * A new variable in the *note sys: c3. module, ‘float_info’, is an
     object containing information derived from the ‘float.h’ file about
     the platform's floating-point support.  Attributes of this object
     include ‘mant_dig’ (number of digits in the mantissa), ‘epsilon’
     (smallest difference between 1.0 and the next largest value
     representable), and several others.  (Contributed by Christian
     Heimes; bpo-1534(43).)

     Another new variable, ‘dont_write_bytecode’, controls whether
     Python writes any ‘.pyc’ or ‘.pyo’ files on importing a module.  If
     this variable is true, the compiled files are not written.  The
     variable is initially set on start-up by supplying the *note -B:
     133b. switch to the Python interpreter, or by setting the *note
     PYTHONDONTWRITEBYTECODE: 133c. environment variable before running
     the interpreter.  Python code can subsequently change the value of
     this variable to control whether bytecode files are written or not.
     (Contributed by Neal Norwitz and Georg Brandl.)

     Information about the command-line arguments supplied to the Python
     interpreter is available by reading attributes of a named tuple
     available as ‘sys.flags’.  For example, the ‘verbose’ attribute is
     true if Python was executed in verbose mode, ‘debug’ is true in
     debugging mode, etc.  These attributes are all read-only.
     (Contributed by Christian Heimes.)

     A new function, ‘getsizeof()’, takes a Python object and returns
     the amount of memory used by the object, measured in bytes.
     Built-in objects return correct results; third-party extensions may
     not, but can define a ‘__sizeof__()’ method to return the object's
     size.  (Contributed by Robert Schuppenies; bpo-2898(44).)

     It's now possible to determine the current profiler and tracer
     functions by calling *note sys.getprofile(): 134e. and *note
     sys.gettrace(): 134f.  (Contributed by Georg Brandl; bpo-1648(45).)

   * The *note tarfile: c8. module now supports POSIX.1-2001 (pax)
     tarfiles in addition to the POSIX.1-1988 (ustar) and GNU tar
     formats that were already supported.  The default format is GNU
     tar; specify the ‘format’ parameter to open a file using a
     different format:

          tar = tarfile.open("output.tar", "w",
                             format=tarfile.PAX_FORMAT)

     The new ‘encoding’ and ‘errors’ parameters specify an encoding and
     an error handling scheme for character conversions.  ‘'strict'’,
     ‘'ignore'’, and ‘'replace'’ are the three standard ways Python can
     handle errors,; ‘'utf-8'’ is a special value that replaces bad
     characters with their UTF-8 representation.  (Character conversions
     occur because the PAX format supports Unicode filenames, defaulting
     to UTF-8 encoding.)

     The ‘TarFile.add()’ method now accepts an ‘exclude’ argument that's
     a function that can be used to exclude certain filenames from an
     archive.  The function must take a filename and return true if the
     file should be excluded or false if it should be archived.  The
     function is applied to both the name initially passed to ‘add()’
     and to the names of files in recursively added directories.

     (All changes contributed by Lars Gustäbel).

   * An optional ‘timeout’ parameter was added to the ‘telnetlib.Telnet’
     class constructor, specifying a timeout measured in seconds.
     (Added by Facundo Batista.)

   * The *note tempfile.NamedTemporaryFile: 46d. class usually deletes
     the temporary file it created when the file is closed.  This
     behaviour can now be changed by passing ‘delete=False’ to the
     constructor.  (Contributed by Damien Miller; bpo-1537850(46).)

     A new class, ‘SpooledTemporaryFile’, behaves like a temporary file
     but stores its data in memory until a maximum size is exceeded.  On
     reaching that limit, the contents will be written to an on-disk
     temporary file.  (Contributed by Dustin J. Mitchell.)

     The ‘NamedTemporaryFile’ and ‘SpooledTemporaryFile’ classes both
     work as context managers, so you can write ‘with
     tempfile.NamedTemporaryFile() as tmp: ...’.  (Contributed by
     Alexander Belopolsky; bpo-2021(47).)

   * The *note test.test_support: cd. module gained a number of context
     managers useful for writing tests.  *note EnvironmentVarGuard():
     1350. is a context manager that temporarily changes environment
     variables and automatically restores them to their old values.

     Another context manager, ‘TransientResource’, can surround calls to
     resources that may or may not be available; it will catch and
     ignore a specified list of exceptions.  For example, a network test
     may ignore certain failures when connecting to an external web
     site:

          with test_support.TransientResource(IOError,
                                          errno=errno.ETIMEDOUT):
              f = urllib.urlopen('https://sf.net')
              ...

     Finally, ‘check_warnings()’ resets the ‘warning’ module's warning
     filters and returns an object that will record all warning messages
     triggered (bpo-3781(48)):

          with test_support.check_warnings() as wrec:
              warnings.simplefilter("always")
              # ... code that triggers a warning ...
              assert str(wrec.message) == "function is outdated"
              assert len(wrec.warnings) == 1, "Multiple warnings raised"

     （由 Brett Cannon 貢獻。）

   * The *note textwrap: d5. module can now preserve existing whitespace
     at the beginnings and ends of the newly created lines by specifying
     ‘drop_whitespace=False’ as an argument:

          >>> S = """This  sentence  has a bunch   of
          ...   extra   whitespace."""
          >>> print textwrap.fill(S, width=15)
          This  sentence
          has a bunch
          of    extra
          whitespace.
          >>> print textwrap.fill(S, drop_whitespace=False, width=15)
          This  sentence
            has a bunch
             of    extra
             whitespace.
          >>>

     （由 Dwayne Bailey 貢獻；bpo-1581073(49)。）

   * The *note threading: d6. module API is being changed to use
     properties such as ‘daemon’ instead of ‘setDaemon()’ and
     ‘isDaemon()’ methods, and some methods have been renamed to use
     underscores instead of camel-case; for example, the ‘activeCount()’
     method is renamed to ‘active_count()’.  Both the 2.6 and 3.0
     versions of the module support the same properties and renamed
     methods, but don't remove the old methods.  No date has been set
     for the deprecation of the old APIs in Python 3.x; the old APIs
     won't be removed in any 2.x version.  (Carried out by several
     people, most notably Benjamin Peterson.)

     The *note threading: d6. module's ‘Thread’ objects gained an
     ‘ident’ property that returns the thread's identifier, a nonzero
     integer.  (Contributed by Gregory P. Smith; bpo-2871(50).)

   * The *note timeit: d8. module now accepts callables as well as
     strings for the statement being timed and for the setup code.  Two
     convenience functions were added for creating ‘Timer’ instances:
     ‘repeat(stmt, setup, time, repeat, number)’ and ‘timeit(stmt,
     setup, time, number)’ create an instance and call the corresponding
     method.  (Contributed by Erik Demaine; bpo-1533909(51).)

   * The ‘Tkinter’ module now accepts lists and tuples for options,
     separating the elements by spaces before passing the resulting
     value to Tcl/Tk.  (Contributed by Guilherme Polo; bpo-2906(52).)

   * The *note turtle: ea. module for turtle graphics was greatly
     enhanced by Gregor Lingl.  New features in the module include:

        * Better animation of turtle movement and rotation.

        * Control over turtle movement using the new ‘delay()’,
          ‘tracer()’, and ‘speed()’ methods.

        * The ability to set new shapes for the turtle, and to define a
          new coordinate system.

        * Turtles now have an ‘undo()’ method that can roll back
          actions.

        * Simple support for reacting to input events such as mouse and
          keyboard activity, making it possible to write simple games.

        * A ‘turtle.cfg’ file can be used to customize the starting
          appearance of the turtle's screen.

        * The module's docstrings can be replaced by new docstrings that
          have been translated into another language.

     (bpo-1513695(53))

   * An optional ‘timeout’ parameter was added to the *note
     urllib.urlopen: 275. function and the ‘urllib.ftpwrapper’ class
     constructor, as well as the *note urllib2.urlopen: 275. function.
     The parameter specifies a timeout measured in seconds.  For
     example:

          >>> u = urllib2.urlopen("http://slow.example.com",
                                  timeout=3)
          Traceback (most recent call last):
            ...
          urllib2.URLError: <urlopen error timed out>
          >>>

     (Added by Facundo Batista.)

   * The Unicode database provided by the *note unicodedata: ee. module
     has been updated to version 5.1.0.  (Updated by Martin von Löwis;
     bpo-3811(54).)

   * The *note warnings: fa. module's ‘formatwarning()’ and
     ‘showwarning()’ gained an optional 'line' argument that can be used
     to supply the line of source code.  (Added as part of
     bpo-1631171(55), which re-implemented part of the *note warnings:
     fa. module in C code.)

     A new function, ‘catch_warnings()’, is a context manager intended
     for testing purposes that lets you temporarily modify the warning
     filters and then restore their original values (bpo-3781(56)).

   * The XML-RPC *note SimpleXMLRPCServer: 115. and *note
     DocXMLRPCServer: 115. classes can now be prevented from immediately
     opening and binding to their socket by passing ‘False’ as the
     'bind_and_activate' constructor parameter.  This can be used to
     modify the instance's ‘allow_reuse_address’ attribute before
     calling the ‘server_bind()’ and ‘server_activate()’ methods to open
     the socket and begin listening for connections.  (Contributed by
     Peter Parente; bpo-1599845(57).)

     ‘SimpleXMLRPCServer’ also has a ‘_send_traceback_header’ attribute;
     if true, the exception and formatted traceback are returned as HTTP
     headers "X-Exception" and "X-Traceback".  This feature is for
     debugging purposes only and should not be used on production
     servers because the tracebacks might reveal passwords or other
     sensitive information.  (Contributed by Alan McIntyre as part of
     his project for Google's Summer of Code 2007.)

   * The *note xmlrpclib: 114. module no longer automatically converts
     *note datetime.date: 1b1. and *note datetime.time: 1b2. to the
     *note xmlrpclib.DateTime: 1351. type; the conversion semantics were
     not necessarily correct for all applications.  Code using
     ‘xmlrpclib’ should convert ‘date’ and *note time: 1b2. instances.
     (bpo-1330538(58)) The code can also handle dates before 1900
     (contributed by Ralf Schmitt; bpo-2014(59)) and 64-bit integers
     represented by using ‘<i8>’ in XML-RPC responses (contributed by
     Riku Lindblad; bpo-2985(60)).

   * The *note zipfile: 117. module's ‘ZipFile’ class now has
     ‘extract()’ and ‘extractall()’ methods that will unpack a single
     file or all the files in the archive to the current directory, or
     to a specified directory:

          z = zipfile.ZipFile('python-251.zip')

          # Unpack a single file, writing it relative
          # to the /tmp directory.
          z.extract('Python/sysmodule.c', '/tmp')

          # Unpack all the files in the archive.
          z.extractall()

     （由 Alan McIntyre 貢獻；bpo-467924(61)。）

     The *note open(): 4c0, ‘read()’ and ‘extract()’ methods can now
     take either a filename or a ‘ZipInfo’ object.  This is useful when
     an archive accidentally contains a duplicated filename.
     (Contributed by Graham Horler; bpo-1775025(62).)

     Finally, *note zipfile: 117. now supports using Unicode filenames
     for archived files.  (Contributed by Alexey Borzenkov;
     bpo-1734346(63).)

* Menu:

* ast 模組::
* future_builtins 模組::
* The json module; JavaScript Object Notation: The json module JavaScript Object Notation.
* The plistlib module; A Property-List Parser: The plistlib module A Property-List Parser.
* ctypes Enhancements::
* Improved SSL Support::

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1736190

   (2) https://www.jcea.es/programacion/pybsddb.htm

   (3) https://bugs.python.org/issue?@action=redirect&bpo=1817

   (4) https://bugs.python.org/issue?@action=redirect&bpo=600362

   (5) https://bugs.python.org/issue?@action=redirect&bpo=1381

   (6) https://bugs.python.org/issue?@action=redirect&bpo=1638033

   (7) https://bugs.python.org/issue?@action=redirect&bpo=1158

   (8) https://speleotrove.com/decimal/decarith.html

   (9) https://bugs.python.org/issue?@action=redirect&bpo=1221598

   (10) https://bugs.python.org/issue?@action=redirect&bpo=1739906

   (11) https://bugs.python.org/issue?@action=redirect&bpo=1001604

   (12) https://bugs.python.org/issue?@action=redirect&bpo=2138

   (13) https://bugs.python.org/issue?@action=redirect&bpo=2819

   (14) https://bugs.python.org/issue?@action=redirect&bpo=711019

   (15) https://bugs.python.org/issue?@action=redirect&bpo=1640

   (16) https://bugs.python.org/issue?@action=redirect&bpo=1663329

   (17) https://bugs.python.org/issue?@action=redirect&bpo=1181

   (18) https://bugs.python.org/issue?@action=redirect&bpo=1273829

   (19) https://bugs.python.org/issue?@action=redirect&bpo=1115886

   (20) https://bugs.python.org/issue?@action=redirect&bpo=1339796

   (21) https://bugs.python.org/issue?@action=redirect&bpo=957650

   (22) https://bugs.python.org/issue?@action=redirect&bpo=1393667

   (23) https://bugs.python.org/issue?@action=redirect&bpo=1106316

   (24) https://bugs.python.org/issue?@action=redirect&bpo=2439

   (25) https://bugs.python.org/issue?@action=redirect&bpo=1137

   (26) https://bugs.python.org/issue?@action=redirect&bpo=1727780

   (27) https://bugs.python.org/issue?@action=redirect&bpo=1681432

   (28) https://bugs.python.org/issue?@action=redirect&bpo=846388

   (29) https://bugs.python.org/issue?@action=redirect&bpo=3487

   (30) https://bugs.python.org/issue?@action=redirect&bpo=2250

   (31) https://bugs.python.org/issue?@action=redirect&bpo=1861

   (32) https://bugs.python.org/issue?@action=redirect&bpo=1657

   (33) https://bugs.python.org/issue?@action=redirect&bpo=2663

   (34) https://bugs.python.org/issue?@action=redirect&bpo=1583

   (35) https://bugs.python.org/issue?@action=redirect&bpo=2240

   (36) https://datatracker.ietf.org/doc/html/rfc2033.html

   (37) https://bugs.python.org/issue?@action=redirect&bpo=957003

   (38) https://datatracker.ietf.org/doc/html/rfc3207.html

   (39) https://bugs.python.org/issue?@action=redirect&bpo=829951

   (40) https://bugs.python.org/issue?@action=redirect&bpo=1646

   (41) https://bugs.python.org/issue?@action=redirect&bpo=742598

   (42) https://bugs.python.org/issue?@action=redirect&bpo=1193577

   (43) https://bugs.python.org/issue?@action=redirect&bpo=1534

   (44) https://bugs.python.org/issue?@action=redirect&bpo=2898

   (45) https://bugs.python.org/issue?@action=redirect&bpo=1648

   (46) https://bugs.python.org/issue?@action=redirect&bpo=1537850

   (47) https://bugs.python.org/issue?@action=redirect&bpo=2021

   (48) https://bugs.python.org/issue?@action=redirect&bpo=3781

   (49) https://bugs.python.org/issue?@action=redirect&bpo=1581073

   (50) https://bugs.python.org/issue?@action=redirect&bpo=2871

   (51) https://bugs.python.org/issue?@action=redirect&bpo=1533909

   (52) https://bugs.python.org/issue?@action=redirect&bpo=2906

   (53) https://bugs.python.org/issue?@action=redirect&bpo=1513695

   (54) https://bugs.python.org/issue?@action=redirect&bpo=3811

   (55) https://bugs.python.org/issue?@action=redirect&bpo=1631171

   (56) https://bugs.python.org/issue?@action=redirect&bpo=3781

   (57) https://bugs.python.org/issue?@action=redirect&bpo=1599845

   (58) https://bugs.python.org/issue?@action=redirect&bpo=1330538

   (59) https://bugs.python.org/issue?@action=redirect&bpo=2014

   (60) https://bugs.python.org/issue?@action=redirect&bpo=2985

   (61) https://bugs.python.org/issue?@action=redirect&bpo=467924

   (62) https://bugs.python.org/issue?@action=redirect&bpo=1775025

   (63) https://bugs.python.org/issue?@action=redirect&bpo=1734346


File: python.info,  Node: ast 模組,  Next: future_builtins 模組,  Up: New and Improved Modules<2>

1.16.18.1 ‘ast’ 模組
....................

The *note ast: 7. module provides an Abstract Syntax Tree representation
of Python code, and Armin Ronacher contributed a set of helper functions
that perform a variety of common tasks.  These will be useful for HTML
templating packages, code analyzers, and similar tools that process
Python code.

The ‘parse()’ function takes an expression and returns an AST. The
‘dump()’ function outputs a representation of a tree, suitable for
debugging:

     import ast

     t = ast.parse("""
     d = {}
     for i in 'abcdefghijklm':
         d[i + i] = ord(i) - ord('a') + 1
     print d
     """)
     print ast.dump(t)

This outputs a deeply nested tree:

     Module(body=[
       Assign(targets=[
         Name(id='d', ctx=Store())
        ], value=Dict(keys=[], values=[]))
       For(target=Name(id='i', ctx=Store()),
           iter=Str(s='abcdefghijklm'), body=[
         Assign(targets=[
           Subscript(value=
             Name(id='d', ctx=Load()),
               slice=
               Index(value=
                 BinOp(left=Name(id='i', ctx=Load()), op=Add(),
                  right=Name(id='i', ctx=Load()))), ctx=Store())
          ], value=
          BinOp(left=
           BinOp(left=
            Call(func=
             Name(id='ord', ctx=Load()), args=[
               Name(id='i', ctx=Load())
              ], keywords=[], starargs=None, kwargs=None),
            op=Sub(), right=Call(func=
             Name(id='ord', ctx=Load()), args=[
               Str(s='a')
              ], keywords=[], starargs=None, kwargs=None)),
            op=Add(), right=Num(n=1)))
         ], orelse=[])
        Print(dest=None, values=[
          Name(id='d', ctx=Load())
        ], nl=True)
      ])

The ‘literal_eval()’ method takes a string or an AST representing a
literal expression, parses and evaluates it, and returns the resulting
value.  A literal expression is a Python expression containing only
strings, numbers, dictionaries, etc.  but no statements or function
calls.  If you need to evaluate an expression but cannot accept the
security risk of using an *note eval(): 163. call, ‘literal_eval()’ will
handle it safely:

     >>> literal = '("a", "b", {2:4, 3:8, 1:2})'
     >>> print ast.literal_eval(literal)
     ('a', 'b', {1: 2, 2: 4, 3: 8})
     >>> print ast.literal_eval('"a" + "b"')
     Traceback (most recent call last):
       ...
     ValueError: malformed string

The module also includes ‘NodeVisitor’ and ‘NodeTransformer’ classes for
traversing and modifying an AST, and functions for common
transformations such as changing line numbers.


File: python.info,  Node: future_builtins 模組,  Next: The json module JavaScript Object Notation,  Prev: ast 模組,  Up: New and Improved Modules<2>

1.16.18.2 ‘future_builtins’ 模組
................................

Python 3.0 makes many changes to the repertoire of built-in functions,
and most of the changes can't be introduced in the Python 2.x series
because they would break compatibility.  The ‘future_builtins’ module
provides versions of these built-in functions that can be imported when
writing 3.0-compatible code.

The functions in this module currently include:

   * ‘ascii(obj)’: equivalent to *note repr(): 7a1.  In Python 3.0,
     *note repr(): 7a1. will return a Unicode string, while *note
     ascii(): 1354. will return a pure ASCII bytestring.

   * ‘filter(predicate, iterable)’, ‘map(func, iterable1, ...)’: the 3.0
     versions return iterators, unlike the 2.x builtins which return
     lists.

   * ‘hex(value)’, ‘oct(value)’: instead of calling the ‘__hex__()’ or
     ‘__oct__()’ methods, these versions will call the ‘__index__()’
     method and convert the result to hexadecimal or octal.  *note
     oct(): 1261. will use the new ‘0o’ notation for its result.


File: python.info,  Node: The json module JavaScript Object Notation,  Next: The plistlib module A Property-List Parser,  Prev: future_builtins 模組,  Up: New and Improved Modules<2>

1.16.18.3 The ‘json’ module: JavaScript Object Notation
.......................................................

The new *note json: 76. module supports the encoding and decoding of
Python types in JSON (Javascript Object Notation).  JSON is a
lightweight interchange format often used in web applications.  For more
information about JSON, see ‘http://www.json.org’.

*note json: 76. comes with support for decoding and encoding most
built-in Python types.  The following example encodes and decodes a
dictionary:

     >>> import json
     >>> data = {"spam": "foo", "parrot": 42}
     >>> in_json = json.dumps(data) # Encode the data
     >>> in_json
     '{"parrot": 42, "spam": "foo"}'
     >>> json.loads(in_json) # Decode into a Python object
     {"spam": "foo", "parrot": 42}

It's also possible to write your own decoders and encoders to support
more types.  Pretty-printing of the JSON strings is also supported.

*note json: 76. (originally called simplejson) was written by Bob
Ippolito.


File: python.info,  Node: The plistlib module A Property-List Parser,  Next: ctypes Enhancements,  Prev: The json module JavaScript Object Notation,  Up: New and Improved Modules<2>

1.16.18.4 The ‘plistlib’ module: A Property-List Parser
.......................................................

The ‘.plist’ format is commonly used on Mac OS X to store basic data
types (numbers, strings, lists, and dictionaries) by serializing them
into an XML-based format.  It resembles the XML-RPC serialization of
data types.

Despite being primarily used on Mac OS X, the format has nothing
Mac-specific about it and the Python implementation works on any
platform that Python supports, so the *note plistlib: 99. module has
been promoted to the standard library.

Using the module is simple:

     import sys
     import plistlib
     import datetime

     # Create data structure
     data_struct = dict(lastAccessed=datetime.datetime.now(),
                        version=1,
                        categories=('Personal','Shared','Private'))

     # Create string containing XML.
     plist_str = plistlib.writePlistToString(data_struct)
     new_struct = plistlib.readPlistFromString(plist_str)
     print data_struct
     print new_struct

     # Write data structure to a file and read it back.
     plistlib.writePlist(data_struct, '/tmp/customizations.plist')
     new_struct = plistlib.readPlist('/tmp/customizations.plist')

     # read/writePlist accepts file-like objects as well as paths.
     plistlib.writePlist(data_struct, sys.stdout)


File: python.info,  Node: ctypes Enhancements,  Next: Improved SSL Support,  Prev: The plistlib module A Property-List Parser,  Up: New and Improved Modules<2>

1.16.18.5 ctypes Enhancements
.............................

Thomas Heller continued to maintain and enhance the *note ctypes: 22.
module.

*note ctypes: 22. now supports a ‘c_bool’ datatype that represents the
C99 ‘bool’ type.  (Contributed by David Remahl; bpo-1649190(1).)

The *note ctypes: 22. string, buffer and array types have improved
support for extended slicing syntax, where various combinations of
‘(start, stop, step)’ are supplied.  (Implemented by Thomas Wouters.)

All *note ctypes: 22. data types now support ‘from_buffer()’ and
‘from_buffer_copy()’ methods that create a ctypes instance based on a
provided buffer object.  ‘from_buffer_copy()’ copies the contents of the
object, while ‘from_buffer()’ will share the same memory area.

A new calling convention tells *note ctypes: 22. to clear the ‘errno’ or
Win32 LastError variables at the outset of each wrapped call.
(Implemented by Thomas Heller; bpo-1798(2).)

You can now retrieve the Unix ‘errno’ variable after a function call.
When creating a wrapped function, you can supply ‘use_errno=True’ as a
keyword parameter to the ‘DLL()’ function and then call the module-level
methods ‘set_errno()’ and ‘get_errno()’ to set and retrieve the error
value.

The Win32 LastError variable is similarly supported by the ‘DLL()’,
‘OleDLL()’, and ‘WinDLL()’ functions.  You supply ‘use_last_error=True’
as a keyword parameter and then call the module-level methods
‘set_last_error()’ and ‘get_last_error()’.

The ‘byref()’ function, used to retrieve a pointer to a ctypes instance,
now has an optional 'offset' parameter that is a byte count that will be
added to the returned pointer.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1649190

   (2) https://bugs.python.org/issue?@action=redirect&bpo=1798


File: python.info,  Node: Improved SSL Support,  Prev: ctypes Enhancements,  Up: New and Improved Modules<2>

1.16.18.6 Improved SSL Support
..............................

Bill Janssen made extensive improvements to Python 2.6's support for the
Secure Sockets Layer by adding a new module, *note ssl: bb, that's built
atop the OpenSSL(1) library.  This new module provides more control over
the protocol negotiated, the X.509 certificates used, and has better
support for writing SSL servers (as opposed to clients) in Python.  The
existing SSL support in the *note socket: b8. module hasn't been removed
and continues to work, though it will be removed in Python 3.0.

To use the new module, you must first create a TCP connection in the
usual way and then pass it to the ‘ssl.wrap_socket()’ function.  It's
possible to specify whether a certificate is required, and to obtain
certificate info by calling the ‘getpeercert()’ method.

也參考
......

The documentation for the *note ssl: bb. module.

   ---------- Footnotes ----------

   (1) https://www.openssl.org/


File: python.info,  Node: Deprecations and Removals,  Next: Build and C API Changes<8>,  Prev: New and Improved Modules<2>,  Up: Python 2 6 有什麼新功能

1.16.19 Deprecations and Removals
---------------------------------

   * String exceptions have been removed.  Attempting to use them raises
     a *note TypeError: 4dd.

   * Changes to the *note Exception: 97d. interface as dictated by PEP
     352(1) continue to be made.  For 2.6, the ‘message’ attribute is
     being deprecated in favor of the *note args: 512. attribute.

   * (3.0-warning mode) Python 3.0 will feature a reorganized standard
     library that will drop many outdated modules and rename others.
     Python 2.6 running in 3.0-warning mode will warn about these
     modules when they are imported.

     The list of deprecated modules is: ‘audiodev’, ‘bgenlocations’,
     ‘buildtools’, ‘bundlebuilder’, ‘Canvas’, ‘compiler’, ‘dircache’,
     ‘dl’, ‘fpformat’, ‘gensuitemodule’, ‘ihooks’, ‘imageop’, ‘imgfile’,
     ‘linuxaudiodev’, ‘mhlib’, ‘mimetools’, ‘multifile’, ‘new’, ‘pure’,
     ‘statvfs’, ‘sunaudiodev’, ‘test.testall’, and ‘toaiff’.

   * The ‘gopherlib’ module has been removed.

   * The ‘MimeWriter’ module and ‘mimify’ module have been deprecated;
     use the *note email: 32. package instead.

   * The ‘md5’ module has been deprecated; use the *note hashlib: 5e.
     module instead.

   * The ‘posixfile’ module has been deprecated; *note fcntl.lockf():
     135a. provides better locking.

   * The ‘popen2’ module has been deprecated; use the *note subprocess:
     c1. module.

   * The ‘rgbimg’ module has been removed.

   * The ‘sets’ module has been deprecated; it's better to use the
     built-in *note set: 57d. and *note frozenset: 57e. types.

   * The ‘sha’ module has been deprecated; use the *note hashlib: 5e.
     module instead.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0352/


File: python.info,  Node: Build and C API Changes<8>,  Next: Porting to Python 2 6,  Prev: Deprecations and Removals,  Up: Python 2 6 有什麼新功能

1.16.20 Build and C API Changes
-------------------------------

Changes to Python's build process and to the C API include:

   * Python now must be compiled with C89 compilers (after 19 years!).
     This means that the Python source tree has dropped its own
     implementations of ‘memmove()’ and ‘strerror()’, which are in the
     C89 standard library.

   * Python 2.6 can be built with Microsoft Visual Studio 2008 (version
     9.0), and this is the new default compiler.  See the ‘PCbuild’
     directory for the build files.  (Implemented by Christian Heimes.)

   * On Mac OS X, Python 2.6 can be compiled as a 4-way universal build.
     The ‘configure’ script can take a
     ‘--with-universal-archs=[32-bit|64-bit|all]’ switch, controlling
     whether the binaries are built for 32-bit architectures (x86,
     PowerPC), 64-bit (x86-64 and PPC-64), or both.  (Contributed by
     Ronald Oussoren.)

   * A new function added in Python 2.6.6, ‘PySys_SetArgvEx()’, sets the
     value of ‘sys.argv’ and can optionally update ‘sys.path’ to include
     the directory containing the script named by ‘sys.argv[0]’
     depending on the value of an 'updatepath' parameter.

     This function was added to close a security hole for applications
     that embed Python.  The old function, ‘PySys_SetArgv()’, would
     always update ‘sys.path’, and sometimes it would add the current
     directory.  This meant that, if you ran an application embedding
     Python in a directory controlled by someone else, attackers could
     put a Trojan-horse module in the directory (say, a file named
     ‘os.py’) that your application would then import and run.

     If you maintain a C/C++ application that embeds Python, check
     whether you're calling ‘PySys_SetArgv()’ and carefully consider
     whether the application should be using ‘PySys_SetArgvEx()’ with
     'updatepath' set to false.  Note that using this function will
     break compatibility with Python versions 2.6.5 and earlier; if you
     have to continue working with earlier versions, you can leave the
     call to ‘PySys_SetArgv()’ alone and call
     ‘PyRun_SimpleString("sys.path.pop(0)\n")’ afterwards to discard the
     first ‘sys.path’ component.

     Security issue reported as CVE-2008-5983(1); discussed in
     gh-50003(2), and fixed by Antoine Pitrou.

   * The BerkeleyDB module now has a C API object, available as
     ‘bsddb.db.api’.  This object can be used by other C extensions that
     wish to use the ‘bsddb’ module for their own purposes.
     (Contributed by Duncan Grisby.)

   * The new buffer interface, previously described in *note the PEP
     3118 section: 1327, adds *note PyObject_GetBuffer(): 369. and *note
     PyBuffer_Release(): 36a, as well as a few other functions.

   * Python's use of the C stdio library is now thread-safe, or at least
     as thread-safe as the underlying library is.  A long-standing
     potential bug occurred if one thread closed a file object while
     another thread was reading from or writing to the object.  In 2.6
     file objects have a reference count, manipulated by the
     ‘PyFile_IncUseCount()’ and ‘PyFile_DecUseCount()’ functions.  File
     objects can't be closed unless the reference count is zero.
     ‘PyFile_IncUseCount()’ should be called while the GIL is still
     held, before carrying out an I/O operation using the ‘FILE *’
     pointer, and ‘PyFile_DecUseCount()’ should be called immediately
     after the GIL is re-acquired.  (Contributed by Antoine Pitrou and
     Gregory P. Smith.)

   * Importing modules simultaneously in two different threads no longer
     deadlocks; it will now raise an *note ImportError: 352.  A new API
     function, *note PyImport_ImportModuleNoBlock(): 388, will look for
     a module in ‘sys.modules’ first, then try to import it after
     acquiring an import lock.  If the import lock is held by another
     thread, an *note ImportError: 352. is raised.  (Contributed by
     Christian Heimes.)

   * Several functions return information about the platform's
     floating-point support.  *note PyFloat_GetMax(): 135c. returns the
     maximum representable floating-point value, and *note
     PyFloat_GetMin(): 135d. returns the minimum positive value.  *note
     PyFloat_GetInfo(): 135e. returns an object containing more
     information from the ‘float.h’ file, such as ‘"mant_dig"’ (number
     of digits in the mantissa), ‘"epsilon"’ (smallest difference
     between 1.0 and the next largest value representable), and several
     others.  (Contributed by Christian Heimes; bpo-1534(3).)

   * C functions and methods that use *note PyComplex_AsCComplex():
     135f. will now accept arguments that have a ‘__complex__()’ method.
     In particular, the functions in the *note cmath: 11. module will
     now accept objects with this method.  This is a backport of a
     Python 3.0 change.  (Contributed by Mark Dickinson;
     bpo-1675423(4).)

   * Python's C API now includes two functions for case-insensitive
     string comparisons, ‘PyOS_stricmp(char*, char*)’ and
     ‘PyOS_strnicmp(char*, char*, Py_ssize_t)’.  (Contributed by
     Christian Heimes; bpo-1635(5).)

   * Many C extensions define their own little macro for adding integers
     and strings to the module's dictionary in the ‘init*’ function.
     Python 2.6 finally defines standard macros for adding values to a
     module, *note PyModule_AddStringMacro: 1360. and *note
     PyModule_AddIntMacro(): 1361.  (Contributed by Christian Heimes.)

   * Some macros were renamed in both 3.0 and 2.6 to make it clearer
     that they are macros, not functions.  ‘Py_Size()’ became *note
     Py_SIZE(): 726, ‘Py_Type()’ became *note Py_TYPE(): 724, and
     ‘Py_Refcnt()’ became *note Py_REFCNT(): 84e.  The mixed-case macros
     are still available in Python 2.6 for backward compatibility.
     (bpo-1629(6))

   * Distutils now places C extensions it builds in a different
     directory when running on a debug version of Python.  (Contributed
     by Collin Winter; bpo-1530959(7).)

   * Several basic data types, such as integers and strings, maintain
     internal free lists of objects that can be re-used.  The data
     structures for these free lists now follow a naming convention: the
     variable is always named ‘free_list’, the counter is always named
     ‘numfree’, and a macro ‘Py<typename>_MAXFREELIST’ is always
     defined.

   * A new Makefile target, "make patchcheck", prepares the Python
     source tree for making a patch: it fixes trailing whitespace in all
     modified ‘.py’ files, checks whether the documentation has been
     changed, and reports whether the ‘Misc/ACKS’ and ‘Misc/NEWS’ files
     have been updated.  (Contributed by Brett Cannon.)

     Another new target, "make profile-opt", compiles a Python binary
     using GCC's profile-guided optimization.  It compiles Python with
     profiling enabled, runs the test suite to obtain a set of profiling
     results, and then compiles using these results for optimization.
     (Contributed by Gregory P. Smith.)

* Menu:

* Port-Specific Changes; Windows: Port-Specific Changes Windows<2>.
* Port-Specific Changes; Mac OS X: Port-Specific Changes Mac OS X<2>.
* Port-Specific Changes; IRIX: Port-Specific Changes IRIX.

   ---------- Footnotes ----------

   (1) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5983

   (2) https://github.com/python/cpython/issues/50003

   (3) https://bugs.python.org/issue?@action=redirect&bpo=1534

   (4) https://bugs.python.org/issue?@action=redirect&bpo=1675423

   (5) https://bugs.python.org/issue?@action=redirect&bpo=1635

   (6) https://bugs.python.org/issue?@action=redirect&bpo=1629

   (7) https://bugs.python.org/issue?@action=redirect&bpo=1530959


File: python.info,  Node: Port-Specific Changes Windows<2>,  Next: Port-Specific Changes Mac OS X<2>,  Up: Build and C API Changes<8>

1.16.20.1 Port-Specific Changes: Windows
........................................

   * The support for Windows 95, 98, ME and NT4 has been dropped.
     Python 2.6 requires at least Windows 2000 SP4.

   * The new default compiler on Windows is Visual Studio 2008 (version
     9.0).  The build directories for Visual Studio 2003 (version 7.1)
     and 2005 (version 8.0) were moved into the PC/ directory.  The new
     ‘PCbuild’ directory supports cross compilation for X64, debug
     builds and Profile Guided Optimization (PGO). PGO builds are
     roughly 10% faster than normal builds.  (Contributed by Christian
     Heimes with help from Amaury Forgeot d'Arc and Martin von Löwis.)

   * The *note msvcrt: 85. module now supports both the normal and wide
     char variants of the console I/O API. The *note getwch(): 1363.
     function reads a keypress and returns a Unicode value, as does the
     *note getwche(): 1364. function.  The *note putwch(): 1365.
     function takes a Unicode character and writes it to the console.
     (Contributed by Christian Heimes.)

   * *note os.path.expandvars(): 1347. will now expand environment
     variables in the form "%var%", and "~user" will be expanded into
     the user's home directory path.  (Contributed by Josiah Carlson;
     bpo-957650(1).)

   * The *note socket: b8. module's socket objects now have an *note
     ioctl(): c7a. method that provides a limited interface to the
     ‘WSAIoctl()’ system interface.

   * The *note _winreg: fe. module now has a function, *note
     ExpandEnvironmentStrings(): 1366, that expands environment variable
     references such as ‘%NAME%’ in an input string.  The handle objects
     provided by this module now support the context protocol, so they
     can be used in *note with: 577. statements.  (Contributed by
     Christian Heimes.)

     *note _winreg: fe. also has better support for x64 systems,
     exposing the *note DisableReflectionKey(): 12f1, *note
     EnableReflectionKey(): 12f2, and *note QueryReflectionKey(): 12f3.
     functions, which enable and disable registry reflection for 32-bit
     processes running on 64-bit systems.  (bpo-1753245(2))

   * The ‘msilib’ module's ‘Record’ object gained ‘GetInteger()’ and
     ‘GetString()’ methods that return field values as an integer or a
     string.  (Contributed by Floris Bruynooghe; bpo-2125(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=957650

   (2) https://bugs.python.org/issue?@action=redirect&bpo=1753245

   (3) https://bugs.python.org/issue?@action=redirect&bpo=2125


File: python.info,  Node: Port-Specific Changes Mac OS X<2>,  Next: Port-Specific Changes IRIX,  Prev: Port-Specific Changes Windows<2>,  Up: Build and C API Changes<8>

1.16.20.2 Port-Specific Changes: Mac OS X
.........................................

   * When compiling a framework build of Python, you can now specify the
     framework name to be used by providing the ‘--with-framework-name=’
     option to the ‘configure’ script.

   * The ‘macfs’ module has been removed.  This in turn required the
     ‘macostools.touched()’ function to be removed because it depended
     on the ‘macfs’ module.  (bpo-1490190(1))

   * Many other Mac OS modules have been deprecated and will be removed
     in Python 3.0: ‘_builtinSuites’, ‘aepack’, ‘aetools’, ‘aetypes’,
     ‘applesingle’, ‘appletrawmain’, ‘appletrunner’, ‘argvemulator’,
     ‘Audio_mac’, ‘autoGIL’, ‘Carbon’, ‘cfmfile’, ‘CodeWarrior’,
     ‘ColorPicker’, ‘EasyDialogs’, ‘Explorer’, ‘Finder’, ‘FrameWork’,
     ‘findertools’, ‘ic’, ‘icglue’, ‘icopen’, ‘macerrors’, ‘MacOS’,
     ‘macfs’, ‘macostools’, ‘macresource’, ‘MiniAEFrame’, ‘Nav’,
     ‘Netscape’, ‘OSATerminology’, ‘pimp’, ‘PixMapWrapper’, ‘StdSuites’,
     ‘SystemEvents’, ‘Terminal’, and ‘terminalcommand’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1490190


File: python.info,  Node: Port-Specific Changes IRIX,  Prev: Port-Specific Changes Mac OS X<2>,  Up: Build and C API Changes<8>

1.16.20.3 Port-Specific Changes: IRIX
.....................................

A number of old IRIX-specific modules were deprecated and will be
removed in Python 3.0: ‘al’ and ‘AL’, ‘cd’, ‘cddb’, ‘cdplayer’, ‘CL’ and
‘cl’, ‘DEVICE’, ‘ERRNO’, ‘FILE’, ‘FL’ and ‘fl’, ‘flp’, ‘fm’, ‘GET’,
‘GLWS’, ‘GL’ and ‘gl’, ‘IN’, ‘IOCTL’, ‘jpeg’, ‘panelparser’, ‘readcd’,
‘SV’ and ‘sv’, ‘torgb’, ‘videoreader’, and ‘WAIT’.


File: python.info,  Node: Porting to Python 2 6,  Next: 致謝<2>,  Prev: Build and C API Changes<8>,  Up: Python 2 6 有什麼新功能

1.16.21 Porting to Python 2.6
-----------------------------

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

   * Classes that aren't supposed to be hashable should set ‘__hash__ =
     None’ in their definitions to indicate the fact.

   * String exceptions have been removed.  Attempting to use them raises
     a *note TypeError: 4dd.

   * The ‘__init__()’ method of *note collections.deque: 580. now clears
     any existing contents of the deque before adding elements from the
     iterable.  This change makes the behavior match ‘list.__init__()’.

   * *note object.__init__(): 655. previously accepted arbitrary
     arguments and keyword arguments, ignoring them.  In Python 2.6,
     this is no longer allowed and will result in a *note TypeError:
     4dd.  This will affect ‘__init__()’ methods that end up calling the
     corresponding method on *note object: a2f. (perhaps through using
     *note super(): 483.).  See bpo-1683368(1) for discussion.

   * The ‘Decimal’ constructor now accepts leading and trailing
     whitespace when passed a string.  Previously it would raise an
     ‘InvalidOperation’ exception.  On the other hand, the
     ‘create_decimal()’ method of ‘Context’ objects now explicitly
     disallows extra whitespace, raising a ‘ConversionSyntax’ exception.

   * Due to an implementation accident, if you passed a file path to the
     built-in *note __import__(): 879. function, it would actually
     import the specified file.  This was never intended to work,
     however, and the implementation now explicitly checks for this case
     and raises an *note ImportError: 352.

   * C API: the *note PyImport_Import(): 136a. and *note
     PyImport_ImportModule(): 389. functions now default to absolute
     imports, not relative imports.  This will affect C extensions that
     import other modules.

   * C API: extension data types that shouldn't be hashable should
     define their ‘tp_hash’ slot to *note PyObject_HashNotImplemented():
     1334.

   * The *note socket: b8. module exception *note socket.error: ff8. now
     inherits from *note IOError: ff5.  Previously it wasn't a subclass
     of ‘StandardError’ but now it is, through *note IOError: ff5.
     (Implemented by Gregory P. Smith; bpo-1706815(2).)

   * The *note xmlrpclib: 114. module no longer automatically converts
     *note datetime.date: 1b1. and *note datetime.time: 1b2. to the
     *note xmlrpclib.DateTime: 1351. type; the conversion semantics were
     not necessarily correct for all applications.  Code using
     ‘xmlrpclib’ should convert ‘date’ and *note time: 1b2. instances.
     (bpo-1330538(3))

   * (3.0-warning mode) The *note Exception: 97d. class now warns when
     accessed using slicing or index access; having *note Exception:
     97d. behave like a tuple is being phased out.

   * (3.0-warning mode) inequality comparisons between two dictionaries
     or two objects that don't implement comparison methods are reported
     as warnings.  ‘dict1 == dict2’ still works, but ‘dict1 < dict2’ is
     being phased out.

     Comparisons between cells, which are an implementation detail of
     Python's scoping rules, also cause warnings because such
     comparisons are forbidden entirely in 3.0.

For applications that embed Python:

   * The ‘PySys_SetArgvEx()’ function was added in Python 2.6.6, letting
     applications close a security hole when the existing
     ‘PySys_SetArgv()’ function was used.  Check whether you're calling
     ‘PySys_SetArgv()’ and carefully consider whether the application
     should be using ‘PySys_SetArgvEx()’ with 'updatepath' set to false.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1683368

   (2) https://bugs.python.org/issue?@action=redirect&bpo=1706815

   (3) https://bugs.python.org/issue?@action=redirect&bpo=1330538


File: python.info,  Node: 致謝<2>,  Prev: Porting to Python 2 6,  Up: Python 2 6 有什麼新功能

1.16.22 致謝
------------

The author would like to thank the following people for offering
suggestions, corrections and assistance with various drafts of this
article: Georg Brandl, Steve Brown, Nick Coghlan, Ralph Corderoy, Jim
Jewett, Kent Johnson, Chris Lambacher, Martin Michlmayr, Antoine Pitrou,
Brian Warner.


File: python.info,  Node: Python 2 5 有什麼新功能,  Next: Python 2 4 有什麼新功能,  Prev: Python 2 6 有什麼新功能,  Up: Python 有什麼新功能？

1.17 Python 2.5 有什麼新功能
============================


作者: A.M. Kuchling

This article explains the new features in Python 2.5.  The final release
of Python 2.5 is scheduled for August 2006; PEP 356(1) describes the
planned release schedule.  Python 2.5 was released on September 19,
2006.

The changes in Python 2.5 are an interesting mix of language and library
improvements.  The library enhancements will be more important to
Python's user community, I think, because several widely useful packages
were added.  New modules include ElementTree for XML processing
(‘xml.etree’), the SQLite database module (‘sqlite’), and the *note
ctypes: 22. module for calling C functions.

The language changes are of middling significance.  Some pleasant new
features were added, but most of them aren't features that you'll use
every day.  Conditional expressions were finally added to the language
using a novel syntax; see section *note PEP 308; Conditional
Expressions: 136f.  The new '*note with: 577.' statement will make
writing cleanup code easier (section *note PEP 343：'with' 陳述式:
1370.).  Values can now be passed into generators (section *note PEP
342; New Generator Features: 1371.).  Imports are now visible as either
absolute or relative (section *note PEP 328; Absolute and Relative
Imports: 1372.).  Some corner cases of exception handling are handled
better (section *note PEP 341; Unified try/except/finally: 1373.).  All
these improvements are worthwhile, but they're improvements to one
specific language feature or another; none of them are broad
modifications to Python's semantics.

As well as the language and library additions, other improvements and
bugfixes were made throughout the source tree.  A search through the SVN
change logs finds there were 353 patches applied and 458 bugs fixed
between Python 2.4 and 2.5.  (Both figures are likely to be
underestimates.)

This article doesn't try to be a complete specification of the new
features; instead changes are briefly introduced using helpful examples.
For full details, you should always refer to the documentation for
Python 2.5 at ‘https://docs.python.org’.  If you want to understand the
complete implementation and design rationale, refer to the PEP for a
particular new feature.

Comments, suggestions, and error reports for this document are welcome;
please e-mail them to the author or open a bug in the Python bug
tracker.

* Menu:

* PEP 308; Conditional Expressions: PEP 308 Conditional Expressions.
* PEP 309; Partial Function Application: PEP 309 Partial Function Application.
* PEP 314; Metadata for Python Software Packages v1.1: PEP 314 Metadata for Python Software Packages v1 1.
* PEP 328; Absolute and Relative Imports: PEP 328 Absolute and Relative Imports.
* PEP 338; Executing Modules as Scripts: PEP 338 Executing Modules as Scripts.
* PEP 341; Unified try/except/finally: PEP 341 Unified try/except/finally.
* PEP 342; New Generator Features: PEP 342 New Generator Features.
* PEP 343：'with' 陳述式::
* PEP 352; Exceptions as New-Style Classes: PEP 352 Exceptions as New-Style Classes.
* PEP 353; Using ssize_t as the index type: PEP 353 Using ssize_t as the index type.
* PEP 357; The '__index__' method: PEP 357 The '__index__' method.
* 其他語言更動: 其他語言更動<15>.
* New, Improved, and Removed Modules: New Improved and Removed Modules.
* Build and C API Changes: Build and C API Changes<9>.
* Porting to Python 2.5: Porting to Python 2 5.
* 致謝: 致謝<3>.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0356/


File: python.info,  Node: PEP 308 Conditional Expressions,  Next: PEP 309 Partial Function Application,  Up: Python 2 5 有什麼新功能

1.17.1 PEP 308: Conditional Expressions
---------------------------------------

For a long time, people have been requesting a way to write conditional
expressions, which are expressions that return value A or value B
depending on whether a Boolean value is true or false.  A conditional
expression lets you write a single assignment statement that has the
same effect as the following:

     if condition:
         x = true_value
     else:
         x = false_value

There have been endless tedious discussions of syntax on both python-dev
and comp.lang.python.  A vote was even held that found the majority of
voters wanted conditional expressions in some form, but there was no
syntax that was preferred by a clear majority.  Candidates included C's
‘cond ? true_v : false_v’, ‘if cond then true_v else false_v’, and 16
other variations.

Guido van Rossum eventually chose a surprising syntax:

     x = true_value if condition else false_value

Evaluation is still lazy as in existing Boolean expressions, so the
order of evaluation jumps around a bit.  The 'condition' expression in
the middle is evaluated first, and the 'true_value' expression is
evaluated only if the condition was true.  Similarly, the 'false_value'
expression is only evaluated when the condition is false.

This syntax may seem strange and backwards; why does the condition go in
the 'middle' of the expression, and not in the front as in C's ‘c ? x :
y’?  The decision was checked by applying the new syntax to the modules
in the standard library and seeing how the resulting code read.  In many
cases where a conditional expression is used, one value seems to be the
'common case' and one value is an 'exceptional case', used only on rarer
occasions when the condition isn't met.  The conditional syntax makes
this pattern a bit more obvious:

     contents = ((doc + '\n') if doc else '')

I read the above statement as meaning "here 'contents' is usually
assigned a value of ‘doc+'\n'’; sometimes 'doc' is empty, in which
special case an empty string is returned."  I doubt I will use
conditional expressions very often where there isn't a clear common and
uncommon case.

There was some discussion of whether the language should require
surrounding conditional expressions with parentheses.  The decision was
made to 'not' require parentheses in the Python language's grammar, but
as a matter of style I think you should always use them.  Consider these
two statements:

     # First version -- no parens
     level = 1 if logging else 0

     # Second version -- with parens
     level = (1 if logging else 0)

In the first version, I think a reader's eye might group the statement
into 'level = 1', 'if logging', 'else 0', and think that the condition
decides whether the assignment to 'level' is performed.  The second
version reads better, in my opinion, because it makes it clear that the
assignment is always performed and the choice is being made between two
values.

Another reason for including the brackets: a few odd combinations of
list comprehensions and lambdas could look like incorrect conditional
expressions.  See PEP 308(1) for some examples.  If you put parentheses
around your conditional expressions, you won't run into this case.

也參考
......

PEP 308(2) - Conditional Expressions

     PEP written by Guido van Rossum and Raymond D. Hettinger;
     implemented by Thomas Wouters.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0308/

   (2) https://peps.python.org/pep-0308/


File: python.info,  Node: PEP 309 Partial Function Application,  Next: PEP 314 Metadata for Python Software Packages v1 1,  Prev: PEP 308 Conditional Expressions,  Up: Python 2 5 有什麼新功能

1.17.2 PEP 309: Partial Function Application
--------------------------------------------

The *note functools: 55. module is intended to contain tools for
functional-style programming.

One useful tool in this module is the ‘partial()’ function.  For
programs written in a functional style, you'll sometimes want to
construct variants of existing functions that have some of the
parameters filled in.  Consider a Python function ‘f(a, b, c)’; you
could create a new function ‘g(b, c)’ that was equivalent to ‘f(1, b,
c)’.  This is called "partial function application".

‘partial()’ takes the arguments ‘(function, arg1, arg2, ...
kwarg1=value1, kwarg2=value2)’.  The resulting object is callable, so
you can just call it to invoke 'function' with the filled-in arguments.

Here's a small but realistic example:

     import functools

     def log (message, subsystem):
         "Write the contents of 'message' to the specified subsystem."
         print '%s: %s' % (subsystem, message)
         ...

     server_log = functools.partial(log, subsystem='server')
     server_log('Unable to open socket')

Here's another example, from a program that uses PyGTK. Here a
context-sensitive pop-up menu is being constructed dynamically.  The
callback provided for the menu option is a partially applied version of
the ‘open_item()’ method, where the first argument has been provided.

     ...
     class Application:
         def open_item(self, path):
            ...
         def init (self):
             open_func = functools.partial(self.open_item, item_path)
             popup_menu.append( ("Open", open_func, 1) )

Another function in the *note functools: 55. module is the
‘update_wrapper(wrapper, wrapped)’ function that helps you write
well-behaved decorators.  ‘update_wrapper()’ copies the name, module,
and docstring attribute to a wrapper function so that tracebacks inside
the wrapped function are easier to understand.  For example, you might
write:

     def my_decorator(f):
         def wrapper(*args, **kwds):
             print 'Calling decorated function'
             return f(*args, **kwds)
         functools.update_wrapper(wrapper, f)
         return wrapper

‘wraps()’ is a decorator that can be used inside your own decorators to
copy the wrapped function's information.  An alternate version of the
previous example would be:

     def my_decorator(f):
         @functools.wraps(f)
         def wrapper(*args, **kwds):
             print 'Calling decorated function'
             return f(*args, **kwds)
         return wrapper

也參考
......

PEP 309(1) - Partial Function Application

     PEP proposed and written by Peter Harris; implemented by Hye-Shik
     Chang and Nick Coghlan, with adaptations by Raymond Hettinger.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0309/


File: python.info,  Node: PEP 314 Metadata for Python Software Packages v1 1,  Next: PEP 328 Absolute and Relative Imports,  Prev: PEP 309 Partial Function Application,  Up: Python 2 5 有什麼新功能

1.17.3 PEP 314: Metadata for Python Software Packages v1.1
----------------------------------------------------------

Some simple dependency support was added to Distutils.  The ‘setup()’
function now has ‘requires’, ‘provides’, and ‘obsoletes’ keyword
parameters.  When you build a source distribution using the ‘sdist’
command, the dependency information will be recorded in the ‘PKG-INFO’
file.

Another new keyword parameter is ‘download_url’, which should be set to
a URL for the package's source code.  This means it's now possible to
look up an entry in the package index, determine the dependencies for a
package, and download the required packages.

     VERSION = '1.0'
     setup(name='PyPackage',
           version=VERSION,
           requires=['numarray', 'zlib (>=1.1.4)'],
           obsoletes=['OldPackage']
           download_url=('http://www.example.com/pypackage/dist/pkg-%s.tar.gz'
                         % VERSION),
          )

Another new enhancement to the Python package index at
‘https://pypi.org’ is storing source and binary archives for a package.
The new ‘upload’ Distutils command will upload a package to the
repository.

Before a package can be uploaded, you must be able to build a
distribution using the ‘sdist’ Distutils command.  Once that works, you
can run ‘python setup.py upload’ to add your package to the PyPI
archive.  Optionally you can GPG-sign the package by supplying the
‘--sign’ and ‘--identity’ options.

Package uploading was implemented by Martin von Löwis and Richard Jones.

也參考
......

PEP 314(1) - Metadata for Python Software Packages v1.1

     PEP proposed and written by A.M. Kuchling, Richard Jones, and Fred
     Drake; implemented by Richard Jones and Fred Drake.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0314/


File: python.info,  Node: PEP 328 Absolute and Relative Imports,  Next: PEP 338 Executing Modules as Scripts,  Prev: PEP 314 Metadata for Python Software Packages v1 1,  Up: Python 2 5 有什麼新功能

1.17.4 PEP 328: Absolute and Relative Imports
---------------------------------------------

The simpler part of PEP 328(1) was implemented in Python 2.4:
parentheses could now be used to enclose the names imported from a
module using the ‘from ... import ...’ statement, making it easier to
import many different names.

The more complicated part has been implemented in Python 2.5: importing
a module can be specified to use absolute or package-relative imports.
The plan is to move toward making absolute imports the default in future
versions of Python.

Let's say you have a package directory like this:

     pkg/
     pkg/__init__.py
     pkg/main.py
     pkg/string.py

This defines a package named ‘pkg’ containing the ‘pkg.main’ and
‘pkg.string’ submodules.

Consider the code in the ‘main.py’ module.  What happens if it executes
the statement ‘import string’?  In Python 2.4 and earlier, it will first
look in the package's directory to perform a relative import, finds
‘pkg/string.py’, imports the contents of that file as the ‘pkg.string’
module, and that module is bound to the name ‘string’ in the ‘pkg.main’
module's namespace.

That's fine if ‘pkg.string’ was what you wanted.  But what if you wanted
Python's standard *note string: be. module?  There's no clean way to
ignore ‘pkg.string’ and look for the standard module; generally you had
to look at the contents of ‘sys.modules’, which is slightly unclean.
Holger Krekel's ‘py.std’ package provides a tidier way to perform
imports from the standard library, ‘import py; py.std.string.join()’,
but that package isn't available on all Python installations.

Reading code which relies on relative imports is also less clear,
because a reader may be confused about which module, *note string: be.
or ‘pkg.string’, is intended to be used.  Python users soon learned not
to duplicate the names of standard library modules in the names of their
packages' submodules, but you can't protect against having your
submodule's name being used for a new module added in a future version
of Python.

In Python 2.5, you can switch *note import: 586.'s behaviour to absolute
imports using a ‘from __future__ import absolute_import’ directive.
This absolute-import behaviour will become the default in a future
version (probably Python 2.7).  Once absolute imports are the default,
‘import string’ will always find the standard library's version.  It's
suggested that users should begin using absolute imports as much as
possible, so it's preferable to begin writing ‘from pkg import string’
in your code.

Relative imports are still possible by adding a leading period to the
module name when using the ‘from ... import’ form:

     # Import names from pkg.string
     from .string import name1, name2
     # Import pkg.string
     from . import string

This imports the *note string: be. module relative to the current
package, so in ‘pkg.main’ this will import 'name1' and 'name2' from
‘pkg.string’.  Additional leading periods perform the relative import
starting from the parent of the current package.  For example, code in
the ‘A.B.C’ module can do:

     from . import D                 # 引入 A.B.D
     from .. import E                # 引入 A.E
     from ..F import G               # 引入 A.F.G

Leading periods cannot be used with the ‘import modname’ form of the
import statement, only the ‘from ... import’ form.

也參考
......

PEP 328(2) - Imports: Multi-Line and Absolute/Relative

     由 Aahz 撰寫 PEP；由 Thomas Wouters 實作。

‘https://pylib.readthedocs.io/’

     The py library by Holger Krekel, which contains the ‘py.std’
     package.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0328/

   (2) https://peps.python.org/pep-0328/


File: python.info,  Node: PEP 338 Executing Modules as Scripts,  Next: PEP 341 Unified try/except/finally,  Prev: PEP 328 Absolute and Relative Imports,  Up: Python 2 5 有什麼新功能

1.17.5 PEP 338: Executing Modules as Scripts
--------------------------------------------

The *note -m: 585. switch added in Python 2.4 to execute a module as a
script gained a few more abilities.  Instead of being implemented in C
code inside the Python interpreter, the switch now uses an
implementation in a new module, *note runpy: ac.

The *note runpy: ac. module implements a more sophisticated import
mechanism so that it's now possible to run modules in a package such as
‘pychecker.checker’.  The module also supports alternative import
mechanisms such as the *note zipimport: 118. module.  This means you can
add a .zip archive's path to ‘sys.path’ and then use the *note -m: 585.
switch to execute code from the archive.

也參考
......

PEP 338(1) - Executing modules as scripts

     由 Nick Coghlan 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0338/


File: python.info,  Node: PEP 341 Unified try/except/finally,  Next: PEP 342 New Generator Features,  Prev: PEP 338 Executing Modules as Scripts,  Up: Python 2 5 有什麼新功能

1.17.6 PEP 341: Unified try/except/finally
------------------------------------------

Until Python 2.5, the *note try: 68c. statement came in two flavours.
You could use a *note finally: 96e. block to ensure that code is always
executed, or one or more *note except: 171. blocks to catch specific
exceptions.  You couldn't combine both ‘except’ blocks and a ‘finally’
block, because generating the right bytecode for the combined version
was complicated and it wasn't clear what the semantics of the combined
statement should be.

Guido van Rossum spent some time working with Java, which does support
the equivalent of combining *note except: 171. blocks and a *note
finally: 96e. block, and this clarified what the statement should mean.
In Python 2.5, you can now write:

     try:
         block-1 ...
     except Exception1:
         handler-1 ...
     except Exception2:
         handler-2 ...
     else:
         else-block
     finally:
         final-block

The code in 'block-1' is executed.  If the code raises an exception, the
various *note except: 171. blocks are tested: if the exception is of
class ‘Exception1’, 'handler-1' is executed; otherwise if it's of class
‘Exception2’, 'handler-2' is executed, and so forth.  If no exception is
raised, the 'else-block' is executed.

No matter what happened previously, the 'final-block' is executed once
the code block is complete and any raised exceptions handled.  Even if
there's an error in an exception handler or the 'else-block' and a new
exception is raised, the code in the 'final-block' is still run.

也參考
......

PEP 341(1) - Unifying try-except and try-finally

     由 Georg Brandl 撰寫 PEP；由 Thomas Lee 實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0341/


File: python.info,  Node: PEP 342 New Generator Features,  Next: PEP 343：'with' 陳述式,  Prev: PEP 341 Unified try/except/finally,  Up: Python 2 5 有什麼新功能

1.17.7 PEP 342: New Generator Features
--------------------------------------

Python 2.5 adds a simple way to pass values 'into' a generator.  As
introduced in Python 2.3, generators only produce output; once a
generator's code was invoked to create an iterator, there was no way to
pass any new information into the function when its execution is
resumed.  Sometimes the ability to pass in some information would be
useful.  Hackish solutions to this include making the generator's code
look at a global variable and then changing the global variable's value,
or passing in some mutable object that callers then modify.

To refresh your memory of basic generators, here's a simple example:

     def counter (maximum):
         i = 0
         while i < maximum:
             yield i
             i += 1

When you call ‘counter(10)’, the result is an iterator that returns the
values from 0 up to 9.  On encountering the *note yield: 971. statement,
the iterator returns the provided value and suspends the function's
execution, preserving the local variables.  Execution resumes on the
following call to the iterator's *note next(): 77c. method, picking up
after the ‘yield’ statement.

In Python 2.3, *note yield: 971. was a statement; it didn't return any
value.  In 2.5, ‘yield’ is now an expression, returning a value that can
be assigned to a variable or otherwise operated on:

     val = (yield i)

I recommend that you always put parentheses around a *note yield: 971.
expression when you're doing something with the returned value, as in
the above example.  The parentheses aren't always necessary, but it's
easier to always add them instead of having to remember when they're
needed.

( PEP 342(1) explains the exact rules, which are that a *note yield:
971.-expression must always be parenthesized except when it occurs at
the top-level expression on the right-hand side of an assignment.  This
means you can write ‘val = yield i’ but have to use parentheses when
there's an operation, as in ‘val = (yield i) + 12’.)

Values are sent into a generator by calling its ‘send(value)’ method.
The generator's code is then resumed and the *note yield: 971.
expression returns the specified 'value'.  If the regular *note next():
77c. method is called, the ‘yield’ returns *note None: 61b.

Here's the previous example, modified to allow changing the value of the
internal counter.

     def counter (maximum):
         i = 0
         while i < maximum:
             val = (yield i)
             # If value provided, change counter
             if val is not None:
                 i = val
             else:
                 i += 1

And here's an example of changing the counter:

     >>> it = counter(10)
     >>> print it.next()
     0
     >>> print it.next()
     1
     >>> print it.send(8)
     8
     >>> print it.next()
     9
     >>> print it.next()
     Traceback (most recent call last):
       File "t.py", line 15, in ?
         print it.next()
     StopIteration

*note yield: 971. will usually return *note None: 61b, so you should
always check for this case.  Don't just use its value in expressions
unless you're sure that the ‘send()’ method will be the only method used
to resume your generator function.

In addition to ‘send()’, there are two other new methods on generators:

   * ‘throw(type, value=None, traceback=None)’ is used to raise an
     exception inside the generator; the exception is raised by the
     *note yield: 971. expression where the generator's execution is
     paused.

   * ‘close()’ raises a new *note GeneratorExit: 1335. exception inside
     the generator to terminate the iteration.  On receiving this
     exception, the generator's code must either raise *note
     GeneratorExit: 1335. or *note StopIteration: ba1.  Catching the
     *note GeneratorExit: 1335. exception and returning a value is
     illegal and will trigger a *note RuntimeError: 179.; if the
     function raises some other exception, that exception is propagated
     to the caller.  ‘close()’ will also be called by Python's garbage
     collector when the generator is garbage-collected.

     If you need to run cleanup code when a *note GeneratorExit: 1335.
     occurs, I suggest using a ‘try: ... finally:’ suite instead of
     catching *note GeneratorExit: 1335.

The cumulative effect of these changes is to turn generators from
one-way producers of information into both producers and consumers.

Generators also become 'coroutines', a more generalized form of
subroutines.  Subroutines are entered at one point and exited at another
point (the top of the function, and a *note return: 972. statement), but
coroutines can be entered, exited, and resumed at many different points
(the *note yield: 971. statements).  We'll have to figure out patterns
for using coroutines effectively in Python.

The addition of the ‘close()’ method has one side effect that isn't
obvious.  ‘close()’ is called when a generator is garbage-collected, so
this means the generator's code gets one last chance to run before the
generator is destroyed.  This last chance means that ‘try...finally’
statements in generators can now be guaranteed to work; the *note
finally: 96e. clause will now always get a chance to run.  The syntactic
restriction that you couldn't mix *note yield: 971. statements with a
‘try...finally’ suite has therefore been removed.  This seems like a
minor bit of language trivia, but using generators and ‘try...finally’
is actually necessary in order to implement the *note with: 577.
statement described by PEP 343(2).  I'll look at this new statement in
the following section.

Another even more esoteric effect of this change: previously, the
‘gi_frame’ attribute of a generator was always a frame object.  It's now
possible for ‘gi_frame’ to be ‘None’ once the generator has been
exhausted.

也參考
......

PEP 342(3) - Coroutines via Enhanced Generators

     PEP written by Guido van Rossum and Phillip J. Eby; implemented by
     Phillip J. Eby.  Includes examples of some fancier uses of
     generators as coroutines.

     Earlier versions of these features were proposed in PEP 288(4) by
     Raymond Hettinger and PEP 325(5) by Samuele Pedroni.

‘https://en.wikipedia.org/wiki/Coroutine’

     The Wikipedia entry for coroutines.

‘https://web.archive.org/web/20160321211320/http://www.sidhe.org/~dan/blog/archives/000178.html’

     An explanation of coroutines from a Perl point of view, written by
     Dan Sugalski.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0342/

   (2) https://peps.python.org/pep-0343/

   (3) https://peps.python.org/pep-0342/

   (4) https://peps.python.org/pep-0288/

   (5) https://peps.python.org/pep-0325/


File: python.info,  Node: PEP 343：'with' 陳述式,  Next: PEP 352 Exceptions as New-Style Classes,  Prev: PEP 342 New Generator Features,  Up: Python 2 5 有什麼新功能

1.17.8 PEP 343：'with' 陳述式
-----------------------------

The '*note with: 577.' statement clarifies code that previously would
use ‘try...finally’ blocks to ensure that clean-up code is executed.  In
this section, I'll discuss the statement as it will commonly be used.
In the next section, I'll examine the implementation details and show
how to write objects for use with this statement.

The '*note with: 577.' statement is a new control-flow structure whose
basic structure is:

     with expression [as variable]:
         with-block

The expression is evaluated, and it should result in an object that
supports the context management protocol (that is, has *note
__enter__(): 56c. and *note __exit__(): 1293. methods.

The object's *note __enter__(): 56c. is called before 'with-block' is
executed and therefore can run set-up code.  It also may return a value
that is bound to the name 'variable', if given.  (Note carefully that
'variable' is 'not' assigned the result of 'expression'.)

After execution of the 'with-block' is finished, the object's *note
__exit__(): 1293. method is called, even if the block raised an
exception, and can therefore run clean-up code.

To enable the statement in Python 2.5, you need to add the following
directive to your module:

     from __future__ import with_statement

The statement will always be enabled in Python 2.6.

Some standard Python objects now support the context management protocol
and can be used with the '*note with: 577.' statement.  File objects are
one example:

     with open('/etc/passwd', 'r') as f:
         for line in f:
             print line
             ... more processing code ...

After this statement has executed, the file object in 'f' will have been
automatically closed, even if the *note for: 2c3. loop raised an
exception part-way through the block.

     備註: In this case, 'f' is the same object created by *note open():
     4c0, because *note __enter__(): 56c. returns 'self'.

The *note threading: d6. module's locks and condition variables also
support the '*note with: 577.' statement:

     lock = threading.Lock()
     with lock:
         # Critical section of code
         ...

The lock is acquired before the block is executed and always released
once the block is complete.

The new ‘localcontext()’ function in the *note decimal: 2e. module makes
it easy to save and restore the current decimal context, which
encapsulates the desired precision and rounding characteristics for
computations:

     from decimal import Decimal, Context, localcontext

     # Displays with default precision of 28 digits
     v = Decimal('578')
     print v.sqrt()

     with localcontext(Context(prec=16)):
         # All code in this block uses a precision of 16 digits.
         # The original context is restored on exiting the block.
         print v.sqrt()

* Menu:

* Writing Context Managers: Writing Context Managers<2>.
* contextlib 模組: contextlib 模組<2>.


File: python.info,  Node: Writing Context Managers<2>,  Next: contextlib 模組<2>,  Up: PEP 343：'with' 陳述式

1.17.8.1 Writing Context Managers
.................................

Under the hood, the '*note with: 577.' statement is fairly complicated.
Most people will only use '‘with’' in company with existing objects and
don't need to know these details, so you can skip the rest of this
section if you like.  Authors of new objects will need to understand the
details of the underlying implementation and should keep reading.

A high-level explanation of the context management protocol is:

   * The expression is evaluated and should result in an object called a
     "context manager".  The context manager must have *note
     __enter__(): 56c. and *note __exit__(): 1293. methods.

   * The context manager's *note __enter__(): 56c. method is called.
     The value returned is assigned to 'VAR'. If no ‘'as VAR'’ clause is
     present, the value is simply discarded.

   * The code in 'BLOCK' is executed.

   * If 'BLOCK' raises an exception, the ‘__exit__(type, value,
     traceback)’ is called with the exception details, the same values
     returned by *note sys.exc_info(): 630.  The method's return value
     controls whether the exception is re-raised: any false value
     re-raises the exception, and ‘True’ will result in suppressing it.
     You'll only rarely want to suppress the exception, because if you
     do the author of the code containing the '*note with: 577.'
     statement will never realize anything went wrong.

   * If 'BLOCK' didn't raise an exception, the *note __exit__(): 1293.
     method is still called, but 'type', 'value', and 'traceback' are
     all ‘None’.

Let's think through an example.  I won't present detailed code but will
only sketch the methods necessary for a database that supports
transactions.

(For people unfamiliar with database terminology: a set of changes to
the database are grouped into a transaction.  Transactions can be either
committed, meaning that all the changes are written into the database,
or rolled back, meaning that the changes are all discarded and the
database is unchanged.  See any database textbook for more information.)

Let's assume there's an object representing a database connection.  Our
goal will be to let the user write code like this:

     db_connection = DatabaseConnection()
     with db_connection as cursor:
         cursor.execute('insert into ...')
         cursor.execute('delete from ...')
         # ... more operations ...

The transaction should be committed if the code in the block runs
flawlessly or rolled back if there's an exception.  Here's the basic
interface for ‘DatabaseConnection’ that I'll assume:

     class DatabaseConnection:
         # Database interface
         def cursor (self):
             "Returns a cursor object and starts a new transaction"
         def commit (self):
             "Commits current transaction"
         def rollback (self):
             "Rolls back current transaction"

The *note __enter__(): 56c. method is pretty easy, having only to start
a new transaction.  For this application the resulting cursor object
would be a useful result, so the method will return it.  The user can
then add ‘as cursor’ to their '*note with: 577.' statement to bind the
cursor to a variable name.

     class DatabaseConnection:
         ...
         def __enter__ (self):
             # Code to start a new transaction
             cursor = self.cursor()
             return cursor

The *note __exit__(): 1293. method is the most complicated because it's
where most of the work has to be done.  The method has to check if an
exception occurred.  If there was no exception, the transaction is
committed.  The transaction is rolled back if there was an exception.

In the code below, execution will just fall off the end of the function,
returning the default value of ‘None’.  ‘None’ is false, so the
exception will be re-raised automatically.  If you wished, you could be
more explicit and add a *note return: 972. statement at the marked
location.

     class DatabaseConnection:
         ...
         def __exit__ (self, type, value, tb):
             if tb is None:
                 # No exception, so commit
                 self.commit()
             else:
                 # Exception occurred, so rollback.
                 self.rollback()
                 # return False


File: python.info,  Node: contextlib 模組<2>,  Prev: Writing Context Managers<2>,  Up: PEP 343：'with' 陳述式

1.17.8.2 contextlib 模組
........................

The new *note contextlib: 1c. module provides some functions and a
decorator that are useful for writing objects for use with the '*note
with: 577.' statement.

The decorator is called ‘contextmanager()’, and lets you write a single
generator function instead of defining a new class.  The generator
should yield exactly one value.  The code up to the *note yield: 971.
will be executed as the *note __enter__(): 56c. method, and the value
yielded will be the method's return value that will get bound to the
variable in the '*note with: 577.' statement's ‘as’ clause, if any.  The
code after the *note yield: 971. will be executed in the *note
__exit__(): 1293. method.  Any exception raised in the block will be
raised by the ‘yield’ statement.

Our database example from the previous section could be written using
this decorator as:

     from contextlib import contextmanager

     @contextmanager
     def db_transaction (connection):
         cursor = connection.cursor()
         try:
             yield cursor
         except:
             connection.rollback()
             raise
         else:
             connection.commit()

     db = DatabaseConnection()
     with db_transaction(db) as cursor:
         ...

The *note contextlib: 1c. module also has a ‘nested(mgr1, mgr2, ...)’
function that combines a number of context managers so you don't need to
write nested '*note with: 577.' statements.  In this example, the single
'‘with’' statement both starts a database transaction and acquires a
thread lock:

     lock = threading.Lock()
     with nested (db_transaction(db), lock) as (cursor, locked):
         ...

Finally, the ‘closing(object)’ function returns 'object' so that it can
be bound to a variable, and calls ‘object.close’ at the end of the
block.

     import urllib, sys
     from contextlib import closing

     with closing(urllib.urlopen('http://www.yahoo.com')) as f:
         for line in f:
             sys.stdout.write(line)

也參考
......

PEP 343(1) - The "with" statement

     PEP written by Guido van Rossum and Nick Coghlan; implemented by
     Mike Bland, Guido van Rossum, and Neal Norwitz.  The PEP shows the
     code generated for a '*note with: 577.' statement, which can be
     helpful in learning how the statement works.

*note contextlib: 1c. 模組的文件。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0343/


File: python.info,  Node: PEP 352 Exceptions as New-Style Classes,  Next: PEP 353 Using ssize_t as the index type,  Prev: PEP 343：'with' 陳述式,  Up: Python 2 5 有什麼新功能

1.17.9 PEP 352: Exceptions as New-Style Classes
-----------------------------------------------

Exception classes can now be new-style classes, not just classic
classes, and the built-in *note Exception: 97d. class and all the
standard built-in exceptions (*note NameError: 3e5, *note ValueError:
1e7, etc.)  are now new-style classes.

The inheritance hierarchy for exceptions has been rearranged a bit.  In
2.5, the inheritance relationships are:

     BaseException       # New in Python 2.5
     |- KeyboardInterrupt
     |- SystemExit
     |- Exception
        |- (all other current built-in exceptions)

This rearrangement was done because people often want to catch all
exceptions that indicate program errors.  *note KeyboardInterrupt: 975.
and *note SystemExit: ce7. aren't errors, though, and usually represent
an explicit action such as the user hitting ‘Control-C’ or code calling
*note sys.exit(): 12dd.  A bare ‘except:’ will catch all exceptions, so
you commonly need to list *note KeyboardInterrupt: 975. and *note
SystemExit: ce7. in order to re-raise them.  The usual pattern is:

     try:
         ...
     except (KeyboardInterrupt, SystemExit):
         raise
     except:
         # Log error...
         # Continue running program...

In Python 2.5, you can now write ‘except Exception’ to achieve the same
result, catching all the exceptions that usually indicate errors but
leaving *note KeyboardInterrupt: 975. and *note SystemExit: ce7. alone.
As in previous versions, a bare ‘except:’ still catches all exceptions.

The goal for Python 3.0 is to require any class raised as an exception
to derive from *note BaseException: 55f. or some descendant of *note
BaseException: 55f, and future releases in the Python 2.x series may
begin to enforce this constraint.  Therefore, I suggest you begin making
all your exception classes derive from *note Exception: 97d. now.  It's
been suggested that the bare ‘except:’ form should be removed in Python
3.0, but Guido van Rossum hasn't decided whether to do this or not.

Raising of strings as exceptions, as in the statement ‘raise "Error
occurred"’, is deprecated in Python 2.5 and will trigger a warning.  The
aim is to be able to remove the string-exception feature in a few
releases.

也參考
......

PEP 352(1) - Required Superclass for Exceptions

     PEP written by Brett Cannon and Guido van Rossum; implemented by
     Brett Cannon.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0352/


File: python.info,  Node: PEP 353 Using ssize_t as the index type,  Next: PEP 357 The '__index__' method,  Prev: PEP 352 Exceptions as New-Style Classes,  Up: Python 2 5 有什麼新功能

1.17.10 PEP 353: Using ssize_t as the index type
------------------------------------------------

A wide-ranging change to Python's C API, using a new *note Py_ssize_t:
a03. type definition instead of int, will permit the interpreter to
handle more data on 64-bit platforms.  This change doesn't affect
Python's capacity on 32-bit platforms.

Various pieces of the Python interpreter used C's int type to store
sizes or counts; for example, the number of items in a list or tuple
were stored in an int.  The C compilers for most 64-bit platforms still
define int as a 32-bit type, so that meant that lists could only hold up
to ‘2**31 - 1’ = 2147483647 items.  (There are actually a few different
programming models that 64-bit C compilers can use - see
‘https://unix.org/version2/whatsnew/lp64_wp.html’ for a discussion - but
the most commonly available model leaves int as 32 bits.)

A limit of 2147483647 items doesn't really matter on a 32-bit platform
because you'll run out of memory before hitting the length limit.  Each
list item requires space for a pointer, which is 4 bytes, plus space for
a *note PyObject: 311. representing the item.  2147483647*4 is already
more bytes than a 32-bit address space can contain.

It's possible to address that much memory on a 64-bit platform, however.
The pointers for a list that size would only require 16 GiB of space, so
it's not unreasonable that Python programmers might construct lists that
large.  Therefore, the Python interpreter had to be changed to use some
type other than int, and this will be a 64-bit type on 64-bit platforms.
The change will cause incompatibilities on 64-bit machines, so it was
deemed worth making the transition now, while the number of 64-bit users
is still relatively small.  (In 5 or 10 years, we may 'all' be on 64-bit
machines, and the transition would be more painful then.)

This change most strongly affects authors of C extension modules.
Python strings and container types such as lists and tuples now use
*note Py_ssize_t: a03. to store their size.  Functions such as *note
PyList_Size(): 1387. now return *note Py_ssize_t: a03.  Code in
extension modules may therefore need to have some variables changed to
*note Py_ssize_t: a03.

The *note PyArg_ParseTuple(): 517. and *note Py_BuildValue(): 84c.
functions have a new conversion code, ‘n’, for *note Py_ssize_t: a03.
*note PyArg_ParseTuple(): 517.'s ‘s#’ and ‘t#’ still output int by
default, but you can define the macro ‘PY_SSIZE_T_CLEAN’ before
including ‘Python.h’ to make them return *note Py_ssize_t: a03.

PEP 353(1) has a section on conversion guidelines that extension authors
should read to learn about supporting 64-bit platforms.

也參考
......

PEP 353(2) - Using ssize_t as the index type

     由 Martin von Löwis 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0353/

   (2) https://peps.python.org/pep-0353/


File: python.info,  Node: PEP 357 The '__index__' method,  Next: 其他語言更動<15>,  Prev: PEP 353 Using ssize_t as the index type,  Up: Python 2 5 有什麼新功能

1.17.11 PEP 357: The '__index__' method
---------------------------------------

The NumPy developers had a problem that could only be solved by adding a
new special method, ‘__index__()’.  When using slice notation, as in
‘[start:stop:step]’, the values of the 'start', 'stop', and 'step'
indexes must all be either integers or long integers.  NumPy defines a
variety of specialized integer types corresponding to unsigned and
signed integers of 8, 16, 32, and 64 bits, but there was no way to
signal that these types could be used as slice indexes.

Slicing can't just use the existing ‘__int__()’ method because that
method is also used to implement coercion to integers.  If slicing used
‘__int__()’, floating-point numbers would also become legal slice
indexes and that's clearly an undesirable behaviour.

Instead, a new special method called ‘__index__()’ was added.  It takes
no arguments and returns an integer giving the slice index to use.  For
example:

     class C:
         def __index__ (self):
             return self.value

The return value must be either a Python integer or long integer.  The
interpreter will check that the type returned is correct, and raises a
*note TypeError: 4dd. if this requirement isn't met.

A corresponding *note nb_index: 138a. slot was added to the C-level
*note PyNumberMethods: 138b. structure to let C extensions implement
this protocol.  ‘PyNumber_Index(obj)’ can be used in extension code to
call the ‘__index__()’ function and retrieve its result.

也參考
......

PEP 357(1) - Allowing Any Object to be Used for Slicing

     由 Travis Oliphant 撰寫 PEP 與實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0357/


File: python.info,  Node: 其他語言更動<15>,  Next: New Improved and Removed Modules,  Prev: PEP 357 The '__index__' method,  Up: Python 2 5 有什麼新功能

1.17.12 其他語言更動
--------------------

Here are all of the changes that Python 2.5 makes to the core Python
language.

   * The *note dict: 23b. type has a new hook for letting subclasses
     provide a default value when a key isn't contained in the
     dictionary.  When a key isn't found, the dictionary's
     ‘__missing__(key)’ method will be called.  This hook is used to
     implement the new ‘defaultdict’ class in the *note collections: 16.
     module.  The following example defines a dictionary that returns
     zero for any missing key:

          class zerodict (dict):
              def __missing__ (self, key):
                  return 0

          d = zerodict({1:1, 2:2})
          print d[1], d[2]   # 印出 1, 2
          print d[3], d[4]   # 印出 0, 0

   * Both 8-bit and Unicode strings have new ‘partition(sep)’ and
     ‘rpartition(sep)’ methods that simplify a common use case.

     The ‘find(S)’ method is often used to get an index which is then
     used to slice the string and obtain the pieces that are before and
     after the separator.  ‘partition(sep)’ condenses this pattern into
     a single method call that returns a 3-tuple containing the
     substring before the separator, the separator itself, and the
     substring after the separator.  If the separator isn't found, the
     first element of the tuple is the entire string and the other two
     elements are empty.  ‘rpartition(sep)’ also returns a 3-tuple but
     starts searching from the end of the string; the ‘r’ stands for
     'reverse'.

     一些範例：

          >>> ('http://www.python.org').partition('://')
          ('http', '://', 'www.python.org')
          >>> ('file:/usr/share/doc/index.html').partition('://')
          ('file:/usr/share/doc/index.html', '', '')
          >>> (u'Subject: a quick question').partition(':')
          (u'Subject', u':', u' a quick question')
          >>> 'www.python.org'.rpartition('.')
          ('www.python', '.', 'org')
          >>> 'www.python.org'.rpartition(':')
          ('', '', 'www.python.org')

     (Implemented by Fredrik Lundh following a suggestion by Raymond
     Hettinger.)

   * The ‘startswith()’ and ‘endswith()’ methods of string types now
     accept tuples of strings to check for.

          def is_image_file (filename):
              return filename.endswith(('.gif', '.jpg', '.tiff'))

     （由 Georg Brandl 實作、後有 Tom Lynn 提出建議。）

   * The *note min(): eac. and *note max(): ead. built-in functions
     gained a ‘key’ keyword parameter analogous to the ‘key’ argument
     for ‘sort()’.  This parameter supplies a function that takes a
     single argument and is called for every value in the list; *note
     min(): eac./*note max(): ead. will return the element with the
     smallest/largest return value from this function.  For example, to
     find the longest string in a list, you can do:

          L = ['medium', 'longest', 'short']
          # Prints 'longest'
          print max(L, key=len)
          # Prints 'short', because lexicographically 'short' has the largest value
          print max(L)

     （由 Steven Bethard 和 Raymond Hettinger 所貢獻。）

   * Two new built-in functions, *note any(): 138e. and *note all():
     138f, evaluate whether an iterator contains any true or false
     values.  *note any(): 138e. returns *note True: bb4. if any value
     returned by the iterator is true; otherwise it will return *note
     False: adb.  *note all(): 138f. returns *note True: bb4. only if
     all of the values returned by the iterator evaluate as true.
     (Suggested by Guido van Rossum, and implemented by Raymond
     Hettinger.)

   * The result of a class's ‘__hash__()’ method can now be either a
     long integer or a regular integer.  If a long integer is returned,
     the hash of that value is taken.  In earlier versions the hash
     value was required to be a regular integer, but in 2.5 the *note
     id(): 1390. built-in was changed to always return non-negative
     numbers, and users often seem to use ‘id(self)’ in ‘__hash__()’
     methods (though this is discouraged).

   * ASCII is now the default encoding for modules.  It's now a syntax
     error if a module contains string literals with 8-bit characters
     but doesn't have an encoding declaration.  In Python 2.4 this
     triggered a warning, not a syntax error.  See PEP 263(1) for how to
     declare a module's encoding; for example, you might add a line like
     this near the top of the source file:

          # -*- coding: latin1 -*-

   * A new warning, *note UnicodeWarning: 1391, is triggered when you
     attempt to compare a Unicode string and an 8-bit string that can't
     be converted to Unicode using the default ASCII encoding.  The
     result of the comparison is false:

          >>> chr(128) == unichr(128)   # Can't convert chr(128) to Unicode
          __main__:1: UnicodeWarning: Unicode equal comparison failed
            to convert both arguments to Unicode - interpreting them
            as being unequal
          False
          >>> chr(127) == unichr(127)   # chr(127) can be converted
          True

     Previously this would raise a *note UnicodeDecodeError: 9b7.
     exception, but in 2.5 this could result in puzzling problems when
     accessing a dictionary.  If you looked up ‘unichr(128)’ and
     ‘chr(128)’ was being used as a key, you'd get a *note
     UnicodeDecodeError: 9b7. exception.  Other changes in 2.5 resulted
     in this exception being raised instead of suppressed by the code in
     ‘dictobject.c’ that implements dictionaries.

     Raising an exception for such a comparison is strictly correct, but
     the change might have broken code, so instead *note UnicodeWarning:
     1391. was introduced.

     （由 Marc-André Lemburg 實作。）

   * One error that Python programmers sometimes make is forgetting to
     include an ‘__init__.py’ module in a package directory.  Debugging
     this mistake can be confusing, and usually requires running Python
     with the *note -v: 1392. switch to log all the paths searched.  In
     Python 2.5, a new *note ImportWarning: 4a2. warning is triggered
     when an import would have picked up a directory as a package but no
     ‘__init__.py’ was found.  This warning is silently ignored by
     default; provide the *note -Wd: 86c. option when running the Python
     executable to display the warning message.  (Implemented by Thomas
     Wouters.)

   * The list of base classes in a class definition can now be empty.
     As an example, this is now legal:

          class C():
              pass

     （由 Brett Cannon 實作。）

* Menu:

* Interactive Interpreter Changes::
* 最佳化: 最佳化<14>.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0263/


File: python.info,  Node: Interactive Interpreter Changes,  Next: 最佳化<14>,  Up: 其他語言更動<15>

1.17.12.1 Interactive Interpreter Changes
.........................................

In the interactive interpreter, ‘quit’ and ‘exit’ have long been strings
so that new users get a somewhat helpful message when they try to quit:

     >>> quit
     'Use Ctrl-D (i.e. EOF) to exit.'

In Python 2.5, ‘quit’ and ‘exit’ are now objects that still produce
string representations of themselves, but are also callable.  Newbies
who try ‘quit()’ or ‘exit()’ will now exit the interpreter as they
expect.  (Implemented by Georg Brandl.)

The Python executable now accepts the standard long options *note -help:
594. and *note -version: cc2.; on Windows, it also accepts the *note /?:
1395. option for displaying a help message.  (Implemented by Georg
Brandl.)


File: python.info,  Node: 最佳化<14>,  Prev: Interactive Interpreter Changes,  Up: 其他語言更動<15>

1.17.12.2 最佳化
................

Several of the optimizations were developed at the NeedForSpeed sprint,
an event held in Reykjavik, Iceland, from May 21-28 2006.  The sprint
focused on speed enhancements to the CPython implementation and was
funded by EWT LLC with local support from CCP Games.  Those
optimizations added at this sprint are specially marked in the following
list.

   * When they were introduced in Python 2.4, the built-in *note set:
     57d. and *note frozenset: 57e. types were built on top of Python's
     dictionary type.  In 2.5 the internal data structure has been
     customized for implementing sets, and as a result sets will use a
     third less memory and are somewhat faster.  (Implemented by Raymond
     Hettinger.)

   * The speed of some Unicode operations, such as finding substrings,
     string splitting, and character map encoding and decoding, has been
     improved.  (Substring search and splitting improvements were added
     by Fredrik Lundh and Andrew Dalke at the NeedForSpeed sprint.
     Character maps were improved by Walter Dörwald and Martin von
     Löwis.)

   * The ‘long(str, base)’ function is now faster on long digit strings
     because fewer intermediate results are calculated.  The peak is for
     strings of around 800-1000 digits where the function is 6 times
     faster.  (Contributed by Alan McIntyre and committed at the
     NeedForSpeed sprint.)

   * It's now illegal to mix iterating over a file with ‘for line in
     file’ and calling the file object's ‘read()’/*note readline():
     a8./‘readlines()’ methods.  Iteration uses an internal buffer and
     the ‘read*()’ methods don't use that buffer.  Instead they would
     return the data following the buffer, causing the data to appear
     out of order.  Mixing iteration and these methods will now trigger
     a *note ValueError: 1e7. from the ‘read*()’ method.  (Implemented
     by Thomas Wouters.)

   * The *note struct: c0. module now compiles structure format strings
     into an internal representation and caches this representation,
     yielding a 20% speedup.  (Contributed by Bob Ippolito at the
     NeedForSpeed sprint.)

   * The *note re: a7. module got a 1 or 2% speedup by switching to
     Python's allocator functions instead of the system's ‘malloc()’ and
     ‘free()’.  (Contributed by Jack Diederich at the NeedForSpeed
     sprint.)

   * The code generator's peephole optimizer now performs simple
     constant folding in expressions.  If you write something like ‘a =
     2+3’, the code generator will do the arithmetic and produce code
     corresponding to ‘a = 5’.  (Proposed and implemented by Raymond
     Hettinger.)

   * Function calls are now faster because code objects now keep the
     most recently finished frame (a "zombie frame") in an internal
     field of the code object, reusing it the next time the code object
     is invoked.  (Original patch by Michael Hudson, modified by Armin
     Rigo and Richard Jones; committed at the NeedForSpeed sprint.)
     Frame objects are also slightly smaller, which may improve cache
     locality and reduce memory usage a bit.  (Contributed by Neal
     Norwitz.)

   * Python's built-in exceptions are now new-style classes, a change
     that speeds up instantiation considerably.  Exception handling in
     Python 2.5 is therefore about 30% faster than in 2.4.  (Contributed
     by Richard Jones, Georg Brandl and Sean Reifschneider at the
     NeedForSpeed sprint.)

   * Importing now caches the paths tried, recording whether they exist
     or not so that the interpreter makes fewer ‘open()’ and ‘stat()’
     calls on startup.  (Contributed by Martin von Löwis and Georg
     Brandl.)


File: python.info,  Node: New Improved and Removed Modules,  Next: Build and C API Changes<9>,  Prev: 其他語言更動<15>,  Up: Python 2 5 有什麼新功能

1.17.13 New, Improved, and Removed Modules
------------------------------------------

The standard library received many enhancements and bug fixes in Python
2.5.  Here's a partial list of the most notable changes, sorted
alphabetically by module name.  Consult the ‘Misc/NEWS’ file in the
source tree for a more complete list of changes, or look through the SVN
logs for all the details.

   * The ‘audioop’ module now supports the a-LAW encoding, and the code
     for u-LAW encoding has been improved.  (Contributed by Lars
     Immisch.)

   * The *note codecs: 14. module gained support for incremental codecs.
     The ‘codec.lookup()’ function now returns a ‘CodecInfo’ instance
     instead of a tuple.  ‘CodecInfo’ instances behave like a 4-tuple to
     preserve backward compatibility but also have the attributes
     ‘encode’, ‘decode’, ‘incrementalencoder’, ‘incrementaldecoder’,
     ‘streamwriter’, and ‘streamreader’.  Incremental codecs can receive
     input and produce output in multiple chunks; the output is the same
     as if the entire input was fed to the non-incremental codec.  See
     the *note codecs: 14. module documentation for details.  (Designed
     and implemented by Walter Dörwald.)

   * The *note collections: 16. module gained a new type, ‘defaultdict’,
     that subclasses the standard *note dict: 23b. type.  The new type
     mostly behaves like a dictionary but constructs a default value
     when a key isn't present, automatically adding it to the dictionary
     for the requested key value.

     The first argument to ‘defaultdict’'s constructor is a factory
     function that gets called whenever a key is requested but not
     found.  This factory function receives no arguments, so you can use
     built-in type constructors such as *note list(): 5b6. or *note
     int(): 23c.  For example, you can make an index of words based on
     their initial letter like this:

          words = """Nel mezzo del cammin di nostra vita
          mi ritrovai per una selva oscura
          che la diritta via era smarrita""".lower().split()

          index = defaultdict(list)

          for w in words:
              init_letter = w[0]
              index[init_letter].append(w)

     Printing ‘index’ results in the following output:

          defaultdict(<type 'list'>, {'c': ['cammin', 'che'], 'e': ['era'],
                  'd': ['del', 'di', 'diritta'], 'm': ['mezzo', 'mi'],
                  'l': ['la'], 'o': ['oscura'], 'n': ['nel', 'nostra'],
                  'p': ['per'], 's': ['selva', 'smarrita'],
                  'r': ['ritrovai'], 'u': ['una'], 'v': ['vita', 'via']}

     （由 Guido van Rossum 所貢獻。）

   * The ‘deque’ double-ended queue type supplied by the *note
     collections: 16. module now has a ‘remove(value)’ method that
     removes the first occurrence of 'value' in the queue, raising *note
     ValueError: 1e7. if the value isn't found.  (Contributed by Raymond
     Hettinger.)

   * New module: The *note contextlib: 1c. module contains helper
     functions for use with the new '*note with: 577.' statement.  See
     section *note contextlib 模組: 1381. for more about this module.

   * New module: The *note cProfile: 20. module is a C implementation of
     the existing *note profile: 9d. module that has much lower
     overhead.  The module's interface is the same as *note profile:
     9d.: you run ‘cProfile.run('main()')’ to profile a function, can
     save profile data to a file, etc.  It's not yet known if the
     Hotshot profiler, which is also written in C but doesn't match the
     *note profile: 9d. module's interface, will continue to be
     maintained in future versions of Python.  (Contributed by Armin
     Rigo.)

     Also, the *note pstats: 9e. module for analyzing the data measured
     by the profiler now supports directing the output to any file
     object by supplying a 'stream' argument to the ‘Stats’ constructor.
     (Contributed by Skip Montanaro.)

   * The *note csv: 21. module, which parses files in comma-separated
     value format, received several enhancements and a number of
     bugfixes.  You can now set the maximum size in bytes of a field by
     calling the ‘csv.field_size_limit(new_limit)’ function; omitting
     the 'new_limit' argument will return the currently set limit.  The
     ‘reader’ class now has a ‘line_num’ attribute that counts the
     number of physical lines read from the source; records can span
     multiple physical lines, so ‘line_num’ is not the same as the
     number of records read.

     The CSV parser is now stricter about multi-line quoted fields.
     Previously, if a line ended within a quoted field without a
     terminating newline character, a newline would be inserted into the
     returned field.  This behavior caused problems when reading files
     that contained carriage return characters within fields, so the
     code was changed to return the field without inserting newlines.
     As a consequence, if newlines embedded within fields are important,
     the input should be split into lines in a manner that preserves the
     newline characters.

     （由 Skip Montanaro 和 Andrew McNamara 所貢獻。）

   * The *note datetime: 1b0. class in the *note datetime: 28. module
     now has a ‘strptime(string, format)’ method for parsing date
     strings, contributed by Josh Spoerri.  It uses the same format
     characters as *note time.strptime(): 139a. and *note
     time.strftime(): 1181.:

          from datetime import datetime

          ts = datetime.strptime('10:13:15 2006-03-07',
                                 '%H:%M:%S %Y-%m-%d')

   * The ‘SequenceMatcher.get_matching_blocks()’ method in the *note
     difflib: 2f. module now guarantees to return a minimal list of
     blocks describing matching subsequences.  Previously, the algorithm
     would occasionally break a block of matching elements into two list
     entries.  (Enhancement by Tim Peters.)

   * The *note doctest: 31. module gained a ‘SKIP’ option that keeps an
     example from being executed at all.  This is intended for code
     snippets that are usage examples intended for the reader and aren't
     actually test cases.

     An 'encoding' parameter was added to the ‘testfile()’ function and
     the ‘DocFileSuite’ class to specify the file's encoding.  This
     makes it easier to use non-ASCII characters in tests contained
     within a docstring.  (Contributed by Bjorn Tillenius.)

   * The *note email: 32. package has been updated to version 4.0.
     (Contributed by Barry Warsaw.)

   * The *note fileinput: 51. module was made more flexible.  Unicode
     filenames are now supported, and a 'mode' parameter that defaults
     to ‘"r"’ was added to the *note input(): 126b. function to allow
     opening files in binary or *note universal newlines: ce1. mode.
     Another new parameter, 'openhook', lets you use a function other
     than *note open(): 4c0. to open the input files.  Once you're
     iterating over the set of files, the ‘FileInput’ object's new *note
     fileno(): 139b. returns the file descriptor for the currently
     opened file.  (Contributed by Georg Brandl.)

   * In the *note gc: 56. module, the new ‘get_count()’ function returns
     a 3-tuple containing the current collection counts for the three GC
     generations.  This is accounting information for the garbage
     collector; when these counts reach a specified threshold, a garbage
     collection sweep will be made.  The existing *note gc.collect():
     16b. function now takes an optional 'generation' argument of 0, 1,
     or 2 to specify which generation to collect.  (Contributed by Barry
     Warsaw.)

   * The ‘nsmallest()’ and ‘nlargest()’ functions in the *note heapq:
     5f. module now support a ‘key’ keyword parameter similar to the one
     provided by the *note min(): eac./*note max(): ead. functions and
     the ‘sort()’ methods.  For example:

          >>> import heapq
          >>> L = ["short", 'medium', 'longest', 'longer still']
          >>> heapq.nsmallest(2, L)  # Return two lowest elements, lexicographically
          ['longer still', 'longest']
          >>> heapq.nsmallest(2, L, key=len)   # Return two shortest elements
          ['short', 'medium']

     （由 Raymond Hettinger 所貢獻。）

   * The *note itertools.islice(): af0. function now accepts ‘None’ for
     the start and step arguments.  This makes it more compatible with
     the attributes of slice objects, so that you can now write the
     following:

          s = slice(5)     # Create slice object
          itertools.islice(iterable, s.start, s.stop, s.step)

     （由 Raymond Hettinger 所貢獻。）

   * The *note format(): 5c3. function in the *note locale: 7a. module
     has been modified and two new functions were added,
     ‘format_string()’ and ‘currency()’.

     The *note format(): 5c3. function's 'val' parameter could
     previously be a string as long as no more than one %char specifier
     appeared; now the parameter must be exactly one %char specifier
     with no surrounding text.  An optional 'monetary' parameter was
     also added which, if ‘True’, will use the locale's rules for
     formatting currency in placing a separator between groups of three
     digits.

     To format strings with multiple %char specifiers, use the new
     ‘format_string()’ function that works like *note format(): 5c3. but
     also supports mixing %char specifiers with arbitrary text.

     A new ‘currency()’ function was also added that formats a number
     according to the current locale's settings.

     （由 Georg Brandl 所貢獻。）

   * The *note mailbox: 7f. module underwent a massive rewrite to add
     the capability to modify mailboxes in addition to reading them.  A
     new set of classes that include ‘mbox’, ‘MH’, and ‘Maildir’ are
     used to read mailboxes, and have an ‘add(message)’ method to add
     messages, ‘remove(key)’ to remove messages, and ‘lock()’/‘unlock()’
     to lock/unlock the mailbox.  The following example converts a
     maildir-format mailbox into an mbox-format one:

          import mailbox

          # 'factory=None' uses email.Message.Message as the class representing
          # individual messages.
          src = mailbox.Maildir('maildir', factory=None)
          dest = mailbox.mbox('/tmp/mbox')

          for msg in src:
              dest.add(msg)

     (Contributed by Gregory K. Johnson.  Funding was provided by
     Google's 2005 Summer of Code.)

   * New module: the ‘msilib’ module allows creating Microsoft Installer
     ‘.msi’ files and CAB files.  Some support for reading the ‘.msi’
     database is also included.  (Contributed by Martin von Löwis.)

   * The ‘nis’ module now supports accessing domains other than the
     system default domain by supplying a 'domain' argument to the
     ‘nis.match()’ and ‘nis.maps()’ functions.  (Contributed by Ben
     Bell.)

   * The *note operator: 8f. module's ‘itemgetter()’ and ‘attrgetter()’
     functions now support multiple fields.  A call such as
     ‘operator.attrgetter('a', 'b')’ will return a function that
     retrieves the ‘a’ and ‘b’ attributes.  Combining this new feature
     with the ‘sort()’ method's ‘key’ parameter lets you easily sort
     lists using multiple fields.  (Contributed by Raymond Hettinger.)

   * The *note optparse: 90. module was updated to version 1.5.1 of the
     Optik library.  The ‘OptionParser’ class gained an ‘epilog’
     attribute, a string that will be printed after the help message,
     and a ‘destroy()’ method to break reference cycles created by the
     object.  (Contributed by Greg Ward.)

   * The *note os: 91. module underwent several changes.  The
     ‘stat_float_times’ variable now defaults to true, meaning that
     *note os.stat(): 448. will now return time values as floats.  (This
     doesn't necessarily mean that *note os.stat(): 448. will return
     times that are precise to fractions of a second; not all systems
     support such precision.)

     Constants named *note os.SEEK_SET: 1225, *note os.SEEK_CUR: 1226,
     and *note os.SEEK_END: 1227. have been added; these are the
     parameters to the *note os.lseek(): 10af. function.  Two new
     constants for locking are *note os.O_SHLOCK: 139c. and *note
     os.O_EXLOCK: 139d.

     Two new functions, ‘wait3()’ and ‘wait4()’, were added.  They're
     similar the ‘waitpid()’ function which waits for a child process to
     exit and returns a tuple of the process ID and its exit status, but
     ‘wait3()’ and ‘wait4()’ return additional information.  ‘wait3()’
     doesn't take a process ID as input, so it waits for any child
     process to exit and returns a 3-tuple of 'process-id',
     'exit-status', 'resource-usage' as returned from the *note
     resource.getrusage(): 139e. function.  ‘wait4(pid)’ does take a
     process ID. (Contributed by Chad J. Schroeder.)

     On FreeBSD, the *note os.stat(): 448. function now returns times
     with nanosecond resolution, and the returned object now has
     ‘st_gen’ and ‘st_birthtime’.  The ‘st_flags’ attribute is also
     available, if the platform supports it.  (Contributed by Antti
     Louko and Diego Pettenò.)

   * The Python debugger provided by the *note pdb: 94. module can now
     store lists of commands to execute when a breakpoint is reached and
     execution stops.  Once breakpoint #1 has been created, enter
     ‘commands 1’ and enter a series of commands to be executed,
     finishing the list with ‘end’.  The command list can include
     commands that resume execution, such as ‘continue’ or ‘next’.
     (Contributed by Grégoire Dooms.)

   * The *note pickle: 95. and ‘cPickle’ modules no longer accept a
     return value of ‘None’ from the *note __reduce__(): 977. method;
     the method must return a tuple of arguments instead.  The ability
     to return ‘None’ was deprecated in Python 2.4, so this completes
     the removal of the feature.

   * The *note pkgutil: 97. module, containing various utility functions
     for finding packages, was enhanced to support PEP 302(1)'s import
     hooks and now also works for packages stored in ZIP-format
     archives.  (Contributed by Phillip J. Eby.)

   * The pybench benchmark suite by Marc-André Lemburg is now included
     in the ‘Tools/pybench’ directory.  The pybench suite is an
     improvement on the commonly used ‘pystone.py’ program because
     pybench provides a more detailed measurement of the interpreter's
     speed.  It times particular operations such as function calls,
     tuple slicing, method lookups, and numeric operations, instead of
     performing many different operations and reducing the result to a
     single number as ‘pystone.py’ does.

   * The ‘pyexpat’ module now uses version 2.0 of the Expat parser.
     (Contributed by Trent Mick.)

   * The *note Queue: 131c. class provided by the ‘Queue’ module gained
     two new methods.  ‘join()’ blocks until all items in the queue have
     been retrieved and all processing work on the items have been
     completed.  Worker threads call the other new method,
     ‘task_done()’, to signal that processing for an item has been
     completed.  (Contributed by Raymond Hettinger.)

   * The old ‘regex’ and ‘regsub’ modules, which have been deprecated
     ever since Python 2.0, have finally been deleted.  Other deleted
     modules: ‘statcache’, ‘tzparse’, ‘whrandom’.

   * Also deleted: the ‘lib-old’ directory, which includes ancient
     modules such as ‘dircmp’ and ‘ni’, was removed.  ‘lib-old’ wasn't
     on the default ‘sys.path’, so unless your programs explicitly added
     the directory to ‘sys.path’, this removal shouldn't affect your
     code.

   * The *note rlcompleter: ab. module is no longer dependent on
     importing the *note readline: a8. module and therefore now works on
     non-Unix platforms.  (Patch from Robert Kiendl.)

   * The *note SimpleXMLRPCServer: 115. and *note DocXMLRPCServer: 115.
     classes now have a ‘rpc_paths’ attribute that constrains XML-RPC
     operations to a limited set of URL paths; the default is to allow
     only ‘'/'’ and ‘'/RPC2'’.  Setting ‘rpc_paths’ to ‘None’ or an
     empty tuple disables this path checking.

   * The *note socket: b8. module now supports ‘AF_NETLINK’ sockets on
     Linux, thanks to a patch from Philippe Biondi.  Netlink sockets are
     a Linux-specific mechanism for communications between a user-space
     process and kernel code; an introductory article about them is at
     ‘https://www.linuxjournal.com/article/7356’.  In Python code,
     netlink addresses are represented as a tuple of 2 integers, ‘(pid,
     group_mask)’.

     Two new methods on socket objects, ‘recv_into(buffer)’ and
     ‘recvfrom_into(buffer)’, store the received data in an object that
     supports the buffer protocol instead of returning the data as a
     string.  This means you can put the data directly into an array or
     a memory-mapped file.

     Socket objects also gained ‘getfamily()’, ‘gettype()’, and
     ‘getproto()’ accessor methods to retrieve the family, type, and
     protocol values for the socket.

   * New module: the ‘spwd’ module provides functions for accessing the
     shadow password database on systems that support shadow passwords.

   * The *note struct: c0. is now faster because it compiles format
     strings into ‘Struct’ objects with ‘pack()’ and ‘unpack()’ methods.
     This is similar to how the *note re: a7. module lets you create
     compiled regular expression objects.  You can still use the
     module-level ‘pack()’ and ‘unpack()’ functions; they'll create
     ‘Struct’ objects and cache them.  Or you can use ‘Struct’ instances
     directly:

          s = struct.Struct('ih3s')

          data = s.pack(1972, 187, 'abc')
          year, number, name = s.unpack(data)

     You can also pack and unpack data to and from buffer objects
     directly using the ‘pack_into(buffer, offset, v1, v2, ...)’ and
     ‘unpack_from(buffer, offset)’ methods.  This lets you store data
     directly into an array or a memory-mapped file.

     (‘Struct’ objects were implemented by Bob Ippolito at the
     NeedForSpeed sprint.  Support for buffer objects was added by
     Martin Blais, also at the NeedForSpeed sprint.)

   * The Python developers switched from CVS to Subversion during the
     2.5 development process.  Information about the exact build version
     is available as the ‘sys.subversion’ variable, a 3-tuple of
     ‘(interpreter-name, branch-name, revision-range)’.  For example, at
     the time of writing my copy of 2.5 was reporting ‘('CPython',
     'trunk', '45313:45315')’.

     This information is also available to C extensions via the *note
     Py_GetBuildInfo(): 139f. function that returns a string of build
     information like this: ‘"trunk:45355:45356M, Apr 13 2006,
     07:42:19"’.  (Contributed by Barry Warsaw.)

   * Another new function, *note sys._current_frames(): 13a0, returns
     the current stack frames for all running threads as a dictionary
     mapping thread identifiers to the topmost stack frame currently
     active in that thread at the time the function is called.
     (Contributed by Tim Peters.)

   * The ‘TarFile’ class in the *note tarfile: c8. module now has an
     ‘extractall()’ method that extracts all members from the archive
     into the current working directory.  It's also possible to set a
     different directory as the extraction target, and to unpack only a
     subset of the archive's members.

     The compression used for a tarfile opened in stream mode can now be
     autodetected using the mode ‘'r|*'’.  (Contributed by Lars
     Gustäbel.)

   * The *note threading: d6. module now lets you set the stack size
     used when new threads are created.  The ‘stack_size([*size*])’
     function returns the currently configured stack size, and supplying
     the optional 'size' parameter sets a new value.  Not all platforms
     support changing the stack size, but Windows, POSIX threading, and
     OS/2 all do.  (Contributed by Andrew MacIntyre.)

   * The *note unicodedata: ee. module has been updated to use version
     4.1.0 of the Unicode character database.  Version 3.2.0 is required
     by some specifications, so it's still available as *note
     unicodedata.ucd_3_2_0: 13a1.

   * New module: the *note uuid: f8. module generates universally unique
     identifiers (UUIDs) according to RFC 4122(2).  The RFC defines
     several different UUID versions that are generated from a starting
     string, from system properties, or purely randomly.  This module
     contains a ‘UUID’ class and functions named ‘uuid1()’, ‘uuid3()’,
     ‘uuid4()’, and ‘uuid5()’ to generate different versions of UUID.
     (Version 2 UUIDs are not specified in RFC 4122(3) and are not
     supported by this module.)

          >>> import uuid
          >>> # make a UUID based on the host ID and current time
          >>> uuid.uuid1()
          UUID('a8098c1a-f86e-11da-bd1a-00112444be1e')

          >>> # make a UUID using an MD5 hash of a namespace UUID and a name
          >>> uuid.uuid3(uuid.NAMESPACE_DNS, 'python.org')
          UUID('6fa459ea-ee8a-3ca4-894e-db77e160355e')

          >>> # make a random UUID
          >>> uuid.uuid4()
          UUID('16fd2706-8baf-433b-82eb-8c7fada847da')

          >>> # make a UUID using a SHA-1 hash of a namespace UUID and a name
          >>> uuid.uuid5(uuid.NAMESPACE_DNS, 'python.org')
          UUID('886313e1-3b8a-5372-9b90-0c9aee199e5d')

     （由 Ka-Ping Yee 所貢獻。）

   * The *note weakref: fc. module's ‘WeakKeyDictionary’ and
     ‘WeakValueDictionary’ types gained new methods for iterating over
     the weak references contained in the dictionary.  ‘iterkeyrefs()’
     and ‘keyrefs()’ methods were added to ‘WeakKeyDictionary’, and
     ‘itervaluerefs()’ and ‘valuerefs()’ were added to
     ‘WeakValueDictionary’.  (Contributed by Fred L. Drake, Jr.)

   * The *note webbrowser: fd. module received a number of enhancements.
     It's now usable as a script with ‘python -m webbrowser’, taking a
     URL as the argument; there are a number of switches to control the
     behaviour (‘-n’ for a new browser window, ‘-t’ for a new tab).  New
     module-level functions, ‘open_new()’ and ‘open_new_tab()’, were
     added to support this.  The module's *note open(): 4c0. function
     supports an additional feature, an 'autoraise' parameter that
     signals whether to raise the open window when possible.  A number
     of additional browsers were added to the supported list such as
     Firefox, Opera, Konqueror, and elinks.  (Contributed by Oleg
     Broytmann and Georg Brandl.)

   * The *note xmlrpclib: 114. module now supports returning *note
     datetime: 1b0. objects for the XML-RPC date type.  Supply
     ‘use_datetime=True’ to the *note loads(): 13a2. function or the
     ‘Unmarshaller’ class to enable this feature.  (Contributed by Skip
     Montanaro.)

   * The *note zipfile: 117. module now supports the ZIP64 version of
     the format, meaning that a .zip archive can now be larger than 4
     GiB and can contain individual files larger than 4 GiB.
     (Contributed by Ronald Oussoren.)

   * The *note zlib: 119. module's ‘Compress’ and ‘Decompress’ objects
     now support a *note copy(): 1e. method that makes a copy of the
     object's internal state and returns a new ‘Compress’ or
     ‘Decompress’ object.  (Contributed by Chris AtLee.)

* Menu:

* ctypes 套件::
* ElementTree 套件::
* hashlib 套件::
* sqlite3 套件::
* wsgiref 套件::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0302/

   (2) https://datatracker.ietf.org/doc/html/rfc4122.html

   (3) https://datatracker.ietf.org/doc/html/rfc4122.html


File: python.info,  Node: ctypes 套件,  Next: ElementTree 套件,  Up: New Improved and Removed Modules

1.17.13.1 ctypes 套件
.....................

The *note ctypes: 22. package, written by Thomas Heller, has been added
to the standard library.  *note ctypes: 22. lets you call arbitrary
functions in shared libraries or DLLs.  Long-time users may remember the
‘dl’ module, which provides functions for loading shared libraries and
calling functions in them.  The *note ctypes: 22. package is much
fancier.

To load a shared library or DLL, you must create an instance of the
‘CDLL’ class and provide the name or path of the shared library or DLL.
Once that's done, you can call arbitrary functions by accessing them as
attributes of the ‘CDLL’ object.

     import ctypes

     libc = ctypes.CDLL('libc.so.6')
     result = libc.printf("Line of output\n")

Type constructors for the various C types are provided: ‘c_int()’,
‘c_float()’, ‘c_double()’, ‘c_char_p()’ (equivalent to char*), and so
forth.  Unlike Python's types, the C versions are all mutable; you can
assign to their ‘value’ attribute to change the wrapped value.  Python
integers and strings will be automatically converted to the
corresponding C types, but for other types you must call the correct
type constructor.  (And I mean 'must'; getting it wrong will often
result in the interpreter crashing with a segmentation fault.)

You shouldn't use ‘c_char_p()’ with a Python string when the C function
will be modifying the memory area, because Python strings are supposed
to be immutable; breaking this rule will cause puzzling bugs.  When you
need a modifiable memory area, use ‘create_string_buffer()’:

     s = "this is a string"
     buf = ctypes.create_string_buffer(s)
     libc.strfry(buf)

C functions are assumed to return integers, but you can set the
‘restype’ attribute of the function object to change this:

     >>> libc.atof('2.71828')
     -1783957616
     >>> libc.atof.restype = ctypes.c_double
     >>> libc.atof('2.71828')
     2.71828

*note ctypes: 22. also provides a wrapper for Python's C API as the
‘ctypes.pythonapi’ object.  This object does 'not' release the global
interpreter lock before calling a function, because the lock must be
held when calling into the interpreter's code.  There's a *note
py_object: 13a5. type constructor that will create a *note PyObject:
311.* pointer.  A simple usage:

     import ctypes

     d = {}
     ctypes.pythonapi.PyObject_SetItem(ctypes.py_object(d),
               ctypes.py_object("abc"),  ctypes.py_object(1))
     # d 現在為 {'abc', 1}.

Don't forget to use *note py_object(): 13a5.; if it's omitted you end up
with a segmentation fault.

*note ctypes: 22. has been around for a while, but people still write
and distribution hand-coded extension modules because you can't rely on
*note ctypes: 22. being present.  Perhaps developers will begin to write
Python wrappers atop a library accessed through *note ctypes: 22.
instead of extension modules, now that *note ctypes: 22. is included
with core Python.

也參考
......

‘https://web.archive.org/web/20180410025338/http://starship.python.net/crew/theller/ctypes/’

     The pre-stdlib ctypes web page, with a tutorial, reference, and
     FAQ.

*note ctypes: 22. 模組的文件。


File: python.info,  Node: ElementTree 套件,  Next: hashlib 套件,  Prev: ctypes 套件,  Up: New Improved and Removed Modules

1.17.13.2 ElementTree 套件
..........................

A subset of Fredrik Lundh's ElementTree library for processing XML has
been added to the standard library as ‘xml.etree’.  The available
modules are ‘ElementTree’, ‘ElementPath’, and ‘ElementInclude’ from
ElementTree 1.2.6.  The ‘cElementTree’ accelerator module is also
included.

The rest of this section will provide a brief overview of using
ElementTree.  Full documentation for ElementTree is available at
‘https://web.archive.org/web/20201124024954/http://effbot.org/zone/element-index.htm’.

ElementTree represents an XML document as a tree of element nodes.  The
text content of the document is stored as the ‘text’ and ‘tail’
attributes of (This is one of the major differences between ElementTree
and the Document Object Model; in the DOM there are many different types
of node, including ‘TextNode’.)

The most commonly used parsing function is ‘parse()’, that takes either
a string (assumed to contain a filename) or a file-like object and
returns an ‘ElementTree’ instance:

     from xml.etree import ElementTree as ET

     tree = ET.parse('ex-1.xml')

     feed = urllib.urlopen(
               'http://planet.python.org/rss10.xml')
     tree = ET.parse(feed)

Once you have an ‘ElementTree’ instance, you can call its ‘getroot()’
method to get the root ‘Element’ node.

There's also an ‘XML()’ function that takes a string literal and returns
an ‘Element’ node (not an ‘ElementTree’).  This function provides a tidy
way to incorporate XML fragments, approaching the convenience of an XML
literal:

     svg = ET.XML("""<svg width="10px" version="1.0">
                  </svg>""")
     svg.set('height', '320px')
     svg.append(elem1)

Each XML element supports some dictionary-like and some list-like access
methods.  Dictionary-like operations are used to access attribute
values, and list-like operations are used to access child nodes.

操作                                結果
                                    
-------------------------------------------------------------------------------------
                                    
‘elem[n]’                           Returns n'th child element.
                                    
                                    
‘elem[m:n]’                         Returns list of m'th through n'th child
                                    elements.
                                    
                                    
‘len(elem)’                         Returns number of child elements.
                                    
                                    
‘list(elem)’                        Returns list of child elements.
                                    
                                    
‘elem.append(elem2)’                Adds 'elem2' as a child.
                                    
                                    
‘elem.insert(index, elem2)’         Inserts 'elem2' at the specified location.
                                    
                                    
‘del elem[n]’                       Deletes n'th child element.
                                    
                                    
‘elem.keys()’                       Returns list of attribute names.
                                    
                                    
‘elem.get(name)’                    Returns value of attribute 'name'.
                                    
                                    
‘elem.set(name, value)’             Sets new value for attribute 'name'.
                                    
                                    
‘elem.attrib’                       Retrieves the dictionary containing
                                    attributes.
                                    
                                    
‘del elem.attrib[name]’             Deletes attribute 'name'.
                                    

Comments and processing instructions are also represented as ‘Element’
nodes.  To check if a node is a comment or processing instructions:

     if elem.tag is ET.Comment:
         ...
     elif elem.tag is ET.ProcessingInstruction:
         ...

To generate XML output, you should call the ‘ElementTree.write()’
method.  Like ‘parse()’, it can take either a string or a file-like
object:

     # Encoding is US-ASCII
     tree.write('output.xml')

     # Encoding is UTF-8
     f = open('output.xml', 'w')
     tree.write(f, encoding='utf-8')

(Caution: the default encoding used for output is ASCII. For general XML
work, where an element's name may contain arbitrary Unicode characters,
ASCII isn't a very useful encoding because it will raise an exception if
an element's name contains any characters with values greater than 127.
Therefore, it's best to specify a different encoding such as UTF-8 that
can handle any Unicode character.)

This section is only a partial description of the ElementTree
interfaces.  Please read the package's official documentation for more
details.

也參考
......

‘https://web.archive.org/web/20201124024954/http://effbot.org/zone/element-index.htm’

     Official documentation for ElementTree.


File: python.info,  Node: hashlib 套件,  Next: sqlite3 套件,  Prev: ElementTree 套件,  Up: New Improved and Removed Modules

1.17.13.3 hashlib 套件
......................

A new *note hashlib: 5e. module, written by Gregory P. Smith, has been
added to replace the ‘md5’ and ‘sha’ modules.  *note hashlib: 5e. adds
support for additional secure hashes (SHA-224, SHA-256, SHA-384, and
SHA-512).  When available, the module uses OpenSSL for fast platform
optimized implementations of algorithms.

The old ‘md5’ and ‘sha’ modules still exist as wrappers around hashlib
to preserve backwards compatibility.  The new module's interface is very
close to that of the old modules, but not identical.  The most
significant difference is that the constructor functions for creating
new hashing objects are named differently.

     # Old versions
     h = md5.md5()
     h = md5.new()

     # New version
     h = hashlib.md5()

     # Old versions
     h = sha.sha()
     h = sha.new()

     # New version
     h = hashlib.sha1()

     # Hash that weren't previously available
     h = hashlib.sha224()
     h = hashlib.sha256()
     h = hashlib.sha384()
     h = hashlib.sha512()

     # Alternative form
     h = hashlib.new('md5')          # Provide algorithm as a string

Once a hash object has been created, its methods are the same as before:
‘update(string)’ hashes the specified string into the current digest
state, ‘digest()’ and ‘hexdigest()’ return the digest value as a binary
string or a string of hex digits, and *note copy(): 1e. returns a new
hashing object with the same digest state.

也參考
......

*note hashlib: 5e. 模組的文件。


File: python.info,  Node: sqlite3 套件,  Next: wsgiref 套件,  Prev: hashlib 套件,  Up: New Improved and Removed Modules

1.17.13.4 sqlite3 套件
......................

The pysqlite module (‘https://www.pysqlite.org’), a wrapper for the
SQLite embedded database, has been added to the standard library under
the package name *note sqlite3: ba.

SQLite is a C library that provides a lightweight disk-based database
that doesn't require a separate server process and allows accessing the
database using a nonstandard variant of the SQL query language.  Some
applications can use SQLite for internal data storage.  It's also
possible to prototype an application using SQLite and then port the code
to a larger database such as PostgreSQL or Oracle.

pysqlite was written by Gerhard Häring and provides a SQL interface
compliant with the DB-API 2.0 specification described by PEP 249(1).

If you're compiling the Python source yourself, note that the source
tree doesn't include the SQLite code, only the wrapper module.  You'll
need to have the SQLite libraries and headers installed before compiling
Python, and the build process will compile the module when the necessary
headers are available.

To use the module, you must first create a ‘Connection’ object that
represents the database.  Here the data will be stored in the
‘/tmp/example’ file:

     conn = sqlite3.connect('/tmp/example')

You can also supply the special name ‘:memory:’ to create a database in
RAM.

Once you have a ‘Connection’, you can create a ‘Cursor’ object and call
its ‘execute()’ method to perform SQL commands:

     c = conn.cursor()

     # Create table
     c.execute('''create table stocks
     (date text, trans text, symbol text,
      qty real, price real)''')

     # Insert a row of data
     c.execute("""insert into stocks
               values ('2006-01-05','BUY','RHAT',100,35.14)""")

Usually your SQL operations will need to use values from Python
variables.  You shouldn't assemble your query using Python's string
operations because doing so is insecure; it makes your program
vulnerable to an SQL injection attack.

Instead, use the DB-API's parameter substitution.  Put ‘?’ as a
placeholder wherever you want to use a value, and then provide a tuple
of values as the second argument to the cursor's ‘execute()’ method.
(Other database modules may use a different placeholder, such as ‘%s’ or
‘:1’.)  For example:

     # Never do this -- insecure!
     symbol = 'IBM'
     c.execute("... where symbol = '%s'" % symbol)

     # Do this instead
     t = (symbol,)
     c.execute('select * from stocks where symbol=?', t)

     # Larger example
     for t in (('2006-03-28', 'BUY', 'IBM', 1000, 45.00),
               ('2006-04-05', 'BUY', 'MSOFT', 1000, 72.00),
               ('2006-04-06', 'SELL', 'IBM', 500, 53.00),
              ):
         c.execute('insert into stocks values (?,?,?,?,?)', t)

To retrieve data after executing a SELECT statement, you can either
treat the cursor as an iterator, call the cursor's ‘fetchone()’ method
to retrieve a single matching row, or call ‘fetchall()’ to get a list of
the matching rows.

This example uses the iterator form:

     >>> c = conn.cursor()
     >>> c.execute('select * from stocks order by price')
     >>> for row in c:
     ...    print row
     ...
     (u'2006-01-05', u'BUY', u'RHAT', 100, 35.140000000000001)
     (u'2006-03-28', u'BUY', u'IBM', 1000, 45.0)
     (u'2006-04-06', u'SELL', u'IBM', 500, 53.0)
     (u'2006-04-05', u'BUY', u'MSOFT', 1000, 72.0)
     >>>

For more information about the SQL dialect supported by SQLite, see
‘https://www.sqlite.org’.

也參考
......

‘https://www.pysqlite.org’

     The pysqlite web page.

‘https://www.sqlite.org’

     The SQLite web page; the documentation describes the syntax and the
     available data types for the supported SQL dialect.

*note sqlite3: ba. 模組的文件。

PEP 249(2) - Database API Specification 2.0

     由 Marc-André Lemburg 撰寫 PEP。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0249/

   (2) https://peps.python.org/pep-0249/


File: python.info,  Node: wsgiref 套件,  Prev: sqlite3 套件,  Up: New Improved and Removed Modules

1.17.13.5 wsgiref 套件
......................

The Web Server Gateway Interface (WSGI) v1.0 defines a standard
interface between web servers and Python web applications and is
described in PEP 333(1).  The *note wsgiref: 100. package is a reference
implementation of the WSGI specification.

The package includes a basic HTTP server that will run a WSGI
application; this server is useful for debugging but isn't intended for
production use.  Setting up a server takes only a few lines of code:

     from wsgiref import simple_server

     wsgi_app = ...

     host = ''
     port = 8000
     httpd = simple_server.make_server(host, port, wsgi_app)
     httpd.serve_forever()

也參考
......

‘https://web.archive.org/web/20160331090247/http://wsgi.readthedocs.org/en/latest/’

     A central web site for WSGI-related resources.

PEP 333(2) - Python Web Server Gateway Interface v1.0

     由 Phillip J. Eby 撰寫 PEP。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0333/

   (2) https://peps.python.org/pep-0333/


File: python.info,  Node: Build and C API Changes<9>,  Next: Porting to Python 2 5,  Prev: New Improved and Removed Modules,  Up: Python 2 5 有什麼新功能

1.17.14 Build and C API Changes
-------------------------------

Changes to Python's build process and to the C API include:

   * The Python source tree was converted from CVS to Subversion, in a
     complex migration procedure that was supervised and flawlessly
     carried out by Martin von Löwis.  The procedure was developed as
     PEP 347(1).

   * Coverity, a company that markets a source code analysis tool called
     Prevent, provided the results of their examination of the Python
     source code.  The analysis found about 60 bugs that were quickly
     fixed.  Many of the bugs were refcounting problems, often occurring
     in error-handling code.  See ‘https://scan.coverity.com’ for the
     statistics.

   * The largest change to the C API came from PEP 353(2), which
     modifies the interpreter to use a *note Py_ssize_t: a03. type
     definition instead of int.  See the earlier section *note PEP 353;
     Using ssize_t as the index type: 1385. for a discussion of this
     change.

   * The design of the bytecode compiler has changed a great deal, no
     longer generating bytecode by traversing the parse tree.  Instead
     the parse tree is converted to an abstract syntax tree (or AST),
     and it is the abstract syntax tree that's traversed to produce the
     bytecode.

     It's possible for Python code to obtain AST objects by using the
     *note compile(): 178. built-in and specifying ‘_ast.PyCF_ONLY_AST’
     as the value of the 'flags' parameter:

          from _ast import PyCF_ONLY_AST
          ast = compile("""a=0
          for i in range(10):
              a += i
          """, "<string>", 'exec', PyCF_ONLY_AST)

          assignment = ast.body[0]
          for_loop = ast.body[1]

     No official documentation has been written for the AST code yet,
     but PEP 339(3) discusses the design.  To start learning about the
     code, read the definition of the various AST nodes in
     ‘Parser/Python.asdl’.  A Python script reads this file and
     generates a set of C structure definitions in
     ‘Include/Python-ast.h’.  The ‘PyParser_ASTFromString()’ and
     ‘PyParser_ASTFromFile()’, defined in ‘Include/pythonrun.h’, take
     Python source as input and return the root of an AST representing
     the contents.  This AST can then be turned into a code object by
     ‘PyAST_Compile()’.  For more information, read the source code, and
     then ask questions on python-dev.

     The AST code was developed under Jeremy Hylton's management, and
     implemented by (in alphabetical order) Brett Cannon, Nick Coghlan,
     Grant Edwards, John Ehresman, Kurt Kaiser, Neal Norwitz, Tim
     Peters, Armin Rigo, and Neil Schemenauer, plus the participants in
     a number of AST sprints at conferences such as PyCon.

   * Evan Jones's patch to obmalloc, first described in a talk at PyCon
     DC 2005, was applied.  Python 2.4 allocated small objects in
     256K-sized arenas, but never freed arenas.  With this patch, Python
     will free arenas when they're empty.  The net effect is that on
     some platforms, when you allocate many objects, Python's memory
     usage may actually drop when you delete them and the memory may be
     returned to the operating system.  (Implemented by Evan Jones, and
     reworked by Tim Peters.)

     Note that this change means extension modules must be more careful
     when allocating memory.  Python's API has many different functions
     for allocating memory that are grouped into families.  For example,
     *note PyMem_Malloc(): c0d, *note PyMem_Realloc(): fd5, and *note
     PyMem_Free(): 13b0. are one family that allocates raw memory, while
     *note PyObject_Malloc(): c0f, *note PyObject_Realloc(): 13b1, and
     *note PyObject_Free(): c0c. are another family that's supposed to
     be used for creating Python objects.

     Previously these different families all reduced to the platform's
     ‘malloc()’ and ‘free()’ functions.  This meant it didn't matter if
     you got things wrong and allocated memory with the ‘PyMem’ function
     but freed it with the ‘PyObject’ function.  With 2.5's changes to
     obmalloc, these families now do different things and mismatches
     will probably result in a segfault.  You should carefully test your
     C extension modules with Python 2.5.

   * The built-in set types now have an official C API. Call *note
     PySet_New(): 13b2. and *note PyFrozenSet_New(): 13b3. to create a
     new set, *note PySet_Add(): 13b4. and *note PySet_Discard(): 13b5.
     to add and remove elements, and *note PySet_Contains(): 13b6. and
     *note PySet_Size(): 13b7. to examine the set's state.  (Contributed
     by Raymond Hettinger.)

   * C code can now obtain information about the exact revision of the
     Python interpreter by calling the *note Py_GetBuildInfo(): 139f.
     function that returns a string of build information like this:
     ‘"trunk:45355:45356M, Apr 13 2006, 07:42:19"’.  (Contributed by
     Barry Warsaw.)

   * Two new macros can be used to indicate C functions that are local
     to the current file so that a faster calling convention can be
     used.  ‘Py_LOCAL(type)’ declares the function as returning a value
     of the specified 'type' and uses a fast-calling qualifier.
     ‘Py_LOCAL_INLINE(type)’ does the same thing and also requests the
     function be inlined.  If macro ‘PY_LOCAL_AGGRESSIVE’ is defined
     before ‘python.h’ is included, a set of more aggressive
     optimizations are enabled for the module; you should benchmark the
     results to find out if these optimizations actually make the code
     faster.  (Contributed by Fredrik Lundh at the NeedForSpeed sprint.)

   * ‘PyErr_NewException(name, base, dict)’ can now accept a tuple of
     base classes as its 'base' argument.  (Contributed by Georg
     Brandl.)

   * The ‘PyErr_Warn()’ function for issuing warnings is now deprecated
     in favour of ‘PyErr_WarnEx(category, message, stacklevel)’ which
     lets you specify the number of stack frames separating this
     function and the caller.  A 'stacklevel' of 1 is the function
     calling *note PyErr_WarnEx(): 13b8, 2 is the function above that,
     and so forth.  (Added by Neal Norwitz.)

   * The CPython interpreter is still written in C, but the code can now
     be compiled with a C++ compiler without errors.  (Implemented by
     Anthony Baxter, Martin von Löwis, Skip Montanaro.)

   * The ‘PyRange_New()’ function was removed.  It was never documented,
     never used in the core code, and had dangerously lax error
     checking.  In the unlikely case that your extensions were using it,
     you can replace it by something like the following:

          range = PyObject_CallFunction((PyObject*) &PyRange_Type, "lll",
                                        start, stop, step);

* Menu:

* Port-Specific Changes::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0347/

   (2) https://peps.python.org/pep-0353/

   (3) https://peps.python.org/pep-0339/


File: python.info,  Node: Port-Specific Changes,  Up: Build and C API Changes<9>

1.17.14.1 Port-Specific Changes
...............................

   * MacOS X (10.3 and higher): dynamic loading of modules now uses the
     ‘dlopen()’ function instead of MacOS-specific functions.

   * MacOS X: an ‘--enable-universalsdk’ switch was added to the
     ‘configure’ script that compiles the interpreter as a universal
     binary able to run on both PowerPC and Intel processors.
     (Contributed by Ronald Oussoren; bpo-2573(1).)

   * Windows: ‘.dll’ is no longer supported as a filename extension for
     extension modules.  ‘.pyd’ is now the only filename extension that
     will be searched for.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=2573


File: python.info,  Node: Porting to Python 2 5,  Next: 致謝<3>,  Prev: Build and C API Changes<9>,  Up: Python 2 5 有什麼新功能

1.17.15 Porting to Python 2.5
-----------------------------

This section lists previously described changes that may require changes
to your code:

   * ASCII is now the default encoding for modules.  It's now a syntax
     error if a module contains string literals with 8-bit characters
     but doesn't have an encoding declaration.  In Python 2.4 this
     triggered a warning, not a syntax error.

   * Previously, the ‘gi_frame’ attribute of a generator was always a
     frame object.  Because of the PEP 342(1) changes described in
     section *note PEP 342; New Generator Features: 1371, it's now
     possible for ‘gi_frame’ to be ‘None’.

   * A new warning, *note UnicodeWarning: 1391, is triggered when you
     attempt to compare a Unicode string and an 8-bit string that can't
     be converted to Unicode using the default ASCII encoding.
     Previously such comparisons would raise a *note UnicodeDecodeError:
     9b7. exception.

   * Library: the *note csv: 21. module is now stricter about multi-line
     quoted fields.  If your files contain newlines embedded within
     fields, the input should be split into lines in a manner which
     preserves the newline characters.

   * Library: the *note locale: 7a. module's *note format(): 5c3.
     function's would previously accept any string as long as no more
     than one %char specifier appeared.  In Python 2.5, the argument
     must be exactly one %char specifier with no surrounding text.

   * Library: The *note pickle: 95. and ‘cPickle’ modules no longer
     accept a return value of ‘None’ from the *note __reduce__(): 977.
     method; the method must return a tuple of arguments instead.  The
     modules also no longer accept the deprecated 'bin' keyword
     parameter.

   * Library: The *note SimpleXMLRPCServer: 115. and *note
     DocXMLRPCServer: 115. classes now have a ‘rpc_paths’ attribute that
     constrains XML-RPC operations to a limited set of URL paths; the
     default is to allow only ‘'/'’ and ‘'/RPC2'’.  Setting ‘rpc_paths’
     to ‘None’ or an empty tuple disables this path checking.

   * C API: Many functions now use *note Py_ssize_t: a03. instead of int
     to allow processing more data on 64-bit machines.  Extension code
     may need to make the same change to avoid warnings and to support
     64-bit machines.  See the earlier section *note PEP 353; Using
     ssize_t as the index type: 1385. for a discussion of this change.

   * C API: The obmalloc changes mean that you must be careful to not
     mix usage of the ‘PyMem_*’ and ‘PyObject_*’ families of functions.
     Memory allocated with one family's ‘*_Malloc’ must be freed with
     the corresponding family's ‘*_Free’ function.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0342/


File: python.info,  Node: 致謝<3>,  Prev: Porting to Python 2 5,  Up: Python 2 5 有什麼新功能

1.17.16 致謝
------------

The author would like to thank the following people for offering
suggestions, corrections and assistance with various drafts of this
article: Georg Brandl, Nick Coghlan, Phillip J. Eby, Lars Gustäbel,
Raymond Hettinger, Ralf W. Grosse-Kunstleve, Kent Johnson, Iain Lowe,
Martin von Löwis, Fredrik Lundh, Andrew McNamara, Skip Montanaro,
Gustavo Niemeyer, Paul Prescod, James Pryor, Mike Rovner, Scott Weikart,
Barry Warsaw, Thomas Wouters.


File: python.info,  Node: Python 2 4 有什麼新功能,  Next: Python 2 3 有什麼新功能,  Prev: Python 2 5 有什麼新功能,  Up: Python 有什麼新功能？

1.18 Python 2.4 有什麼新功能
============================


作者: A.M. Kuchling

This article explains the new features in Python 2.4.1, released on
March 30, 2005.

Python 2.4 is a medium-sized release.  It doesn't introduce as many
changes as the radical Python 2.2, but introduces more features than the
conservative 2.3 release.  The most significant new language features
are function decorators and generator expressions; most other changes
are to the standard library.

According to the CVS change logs, there were 481 patches applied and 502
bugs fixed between Python 2.3 and 2.4.  Both figures are likely to be
underestimates.

This article doesn't attempt to provide a complete specification of
every single new feature, but instead provides a brief introduction to
each feature.  For full details, you should refer to the documentation
for Python 2.4, such as the Python Library Reference and the Python
Reference Manual.  Often you will be referred to the PEP for a
particular new feature for explanations of the implementation and design
rationale.

* Menu:

* PEP 218; Built-In Set Objects: PEP 218 Built-In Set Objects.
* PEP 237; Unifying Long Integers and Integers: PEP 237 Unifying Long Integers and Integers.
* PEP 289; Generator Expressions: PEP 289 Generator Expressions.
* PEP 292; Simpler String Substitutions: PEP 292 Simpler String Substitutions.
* PEP 318; Decorators for Functions and Methods: PEP 318 Decorators for Functions and Methods.
* PEP 322; Reverse Iteration: PEP 322 Reverse Iteration.
* PEP 324; New subprocess Module: PEP 324 New subprocess Module.
* PEP 327; Decimal Data Type: PEP 327 Decimal Data Type.
* PEP 328; Multi-line Imports: PEP 328 Multi-line Imports.
* PEP 331; Locale-Independent Float/String Conversions: PEP 331 Locale-Independent Float/String Conversions.
* 其他語言更動: 其他語言更動<16>.
* New, Improved, and Deprecated Modules: New Improved and Deprecated Modules<3>.
* Build and C API Changes: Build and C API Changes<10>.
* Porting to Python 2.4: Porting to Python 2 4.
* 致謝: 致謝<4>.


File: python.info,  Node: PEP 218 Built-In Set Objects,  Next: PEP 237 Unifying Long Integers and Integers,  Up: Python 2 4 有什麼新功能

1.18.1 PEP 218: Built-In Set Objects
------------------------------------

Python 2.3 introduced the ‘sets’ module.  C implementations of set data
types have now been added to the Python core as two new built-in types,
‘set(iterable)’ and ‘frozenset(iterable)’.  They provide high speed
operations for membership testing, for eliminating duplicates from
sequences, and for mathematical operations like unions, intersections,
differences, and symmetric differences.

     >>> a = set('abracadabra')              # form a set from a string
     >>> 'z' in a                            # fast membership testing
     False
     >>> a                                   # unique letters in a
     set(['a', 'r', 'b', 'c', 'd'])
     >>> ''.join(a)                          # convert back into a string
     'arbcd'

     >>> b = set('alacazam')                 # form a second set
     >>> a - b                               # letters in a but not in b
     set(['r', 'd', 'b'])
     >>> a | b                               # letters in either a or b
     set(['a', 'c', 'r', 'd', 'b', 'm', 'z', 'l'])
     >>> a & b                               # letters in both a and b
     set(['a', 'c'])
     >>> a ^ b                               # letters in a or b but not both
     set(['r', 'd', 'b', 'm', 'z', 'l'])

     >>> a.add('z')                          # add a new element
     >>> a.update('wxy')                     # add multiple new elements
     >>> a
     set(['a', 'c', 'b', 'd', 'r', 'w', 'y', 'x', 'z'])
     >>> a.remove('x')                       # take one element out
     >>> a
     set(['a', 'c', 'b', 'd', 'r', 'w', 'y', 'z'])

The *note frozenset(): 57e. type is an immutable version of *note set():
57d.  Since it is immutable and hashable, it may be used as a dictionary
key or as a member of another set.

The ‘sets’ module remains in the standard library, and may be useful if
you wish to subclass the ‘Set’ or ‘ImmutableSet’ classes.  There are
currently no plans to deprecate the module.

也參考
......

PEP 218(1) - Adding a Built-In Set Object Type

     Originally proposed by Greg Wilson and ultimately implemented by
     Raymond Hettinger.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0218/


File: python.info,  Node: PEP 237 Unifying Long Integers and Integers,  Next: PEP 289 Generator Expressions,  Prev: PEP 218 Built-In Set Objects,  Up: Python 2 4 有什麼新功能

1.18.2 PEP 237: Unifying Long Integers and Integers
---------------------------------------------------

The lengthy transition process for this PEP, begun in Python 2.2, takes
another step forward in Python 2.4.  In 2.3, certain integer operations
that would behave differently after int/long unification triggered *note
FutureWarning: 357. warnings and returned values limited to 32 or 64
bits (depending on your platform).  In 2.4, these expressions no longer
produce a warning and instead produce a different result that's usually
a long integer.

The problematic expressions are primarily left shifts and lengthy
hexadecimal and octal constants.  For example, ‘2 << 32’ results in a
warning in 2.3, evaluating to 0 on 32-bit platforms.  In Python 2.4,
this expression now returns the correct answer, 8589934592.

也參考
......

PEP 237(1) - Unifying Long Integers and Integers

     Original PEP written by Moshe Zadka and GvR. The changes for 2.4
     were implemented by Kalle Svensson.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0237/


File: python.info,  Node: PEP 289 Generator Expressions,  Next: PEP 292 Simpler String Substitutions,  Prev: PEP 237 Unifying Long Integers and Integers,  Up: Python 2 4 有什麼新功能

1.18.3 PEP 289: Generator Expressions
-------------------------------------

The iterator feature introduced in Python 2.2 and the *note itertools:
75. module make it easier to write programs that loop through large data
sets without having the entire data set in memory at one time.  List
comprehensions don't fit into this picture very well because they
produce a Python list object containing all of the items.  This
unavoidably pulls all of the objects into memory, which can be a problem
if your data set is very large.  When trying to write a functionally
styled program, it would be natural to write something like:

     links = [link for link in get_all_links() if not link.followed]
     for link in links:
         ...

instead of

     for link in get_all_links():
         if link.followed:
             continue
         ...

The first form is more concise and perhaps more readable, but if you're
dealing with a large number of link objects you'd have to write the
second form to avoid having all link objects in memory at the same time.

Generator expressions work similarly to list comprehensions but don't
materialize the entire list; instead they create a generator that will
return elements one by one.  The above example could be written as:

     links = (link for link in get_all_links() if not link.followed)
     for link in links:
         ...

Generator expressions always have to be written inside parentheses, as
in the above example.  The parentheses signalling a function call also
count, so if you want to create an iterator that will be immediately
passed to a function you could write:

     print sum(obj.count for obj in list_all_objects())

Generator expressions differ from list comprehensions in various small
ways.  Most notably, the loop variable ('obj' in the above example) is
not accessible outside of the generator expression.  List comprehensions
leave the variable assigned to its last value; future versions of Python
will change this, making list comprehensions match generator expressions
in this respect.

也參考
......

PEP 289(1) - Generator Expressions

     Proposed by Raymond Hettinger and implemented by Jiwon Seo with
     early efforts steered by Hye-Shik Chang.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0289/


File: python.info,  Node: PEP 292 Simpler String Substitutions,  Next: PEP 318 Decorators for Functions and Methods,  Prev: PEP 289 Generator Expressions,  Up: Python 2 4 有什麼新功能

1.18.4 PEP 292: Simpler String Substitutions
--------------------------------------------

Some new classes in the standard library provide an alternative
mechanism for substituting variables into strings; this style of
substitution may be better for applications where untrained users need
to edit templates.

The usual way of substituting variables by name is the ‘%’ operator:

     >>> '%(page)i: %(title)s' % {'page':2, 'title': 'The Best of Times'}
     '2: The Best of Times'

When writing the template string, it can be easy to forget the ‘i’ or
‘s’ after the closing parenthesis.  This isn't a big problem if the
template is in a Python module, because you run the code, get an
"Unsupported format character" *note ValueError: 1e7, and fix the
problem.  However, consider an application such as Mailman where
template strings or translations are being edited by users who aren't
aware of the Python language.  The format string's syntax is complicated
to explain to such users, and if they make a mistake, it's difficult to
provide helpful feedback to them.

PEP 292 adds a ‘Template’ class to the *note string: be. module that
uses ‘$’ to indicate a substitution:

     >>> import string
     >>> t = string.Template('$page: $title')
     >>> t.substitute({'page':2, 'title': 'The Best of Times'})
     '2: The Best of Times'

If a key is missing from the dictionary, the ‘substitute()’ method will
raise a *note KeyError: 2fb.  There's also a ‘safe_substitute()’ method
that ignores missing keys:

     >>> t = string.Template('$page: $title')
     >>> t.safe_substitute({'page':3})
     '3: $title'

也參考
......

PEP 292(1) - Simpler String Substitutions

     Written and implemented by Barry Warsaw.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0292/


File: python.info,  Node: PEP 318 Decorators for Functions and Methods,  Next: PEP 322 Reverse Iteration,  Prev: PEP 292 Simpler String Substitutions,  Up: Python 2 4 有什麼新功能

1.18.5 PEP 318: Decorators for Functions and Methods
----------------------------------------------------

Python 2.2 extended Python's object model by adding static methods and
class methods, but it didn't extend Python's syntax to provide any new
way of defining static or class methods.  Instead, you had to write a
*note def: 13c5. statement in the usual way, and pass the resulting
method to a *note staticmethod(): 358. or *note classmethod(): 14a.
function that would wrap up the function as a method of the new type.
Your code would look like this:

     class C:
        def meth (cls):
            ...

        meth = classmethod(meth)   # Rebind name to wrapped-up class method

If the method was very long, it would be easy to miss or forget the
*note classmethod(): 14a. invocation after the function body.

The intention was always to add some syntax to make such definitions
more readable, but at the time of 2.2's release a good syntax was not
obvious.  Today a good syntax 'still' isn't obvious but users are asking
for easier access to the feature; a new syntactic feature has been added
to meet this need.

The new feature is called "function decorators".  The name comes from
the idea that *note classmethod(): 14a, *note staticmethod(): 358, and
friends are storing additional information on a function object; they're
'decorating' functions with more details.

The notation borrows from Java and uses the ‘'@'’ character as an
indicator.  Using the new syntax, the example above would be written:

     class C:

        @classmethod
        def meth (cls):
            ...

The ‘@classmethod’ is shorthand for the ‘meth=classmethod(meth)’
assignment.  More generally, if you have the following:

     @A
     @B
     @C
     def f ():
         ...

It's equivalent to the following pre-decorator code:

     def f(): ...
     f = A(B(C(f)))

Decorators must come on the line before a function definition, one
decorator per line, and can't be on the same line as the def statement,
meaning that ‘@A def f(): ...’ is illegal.  You can only decorate
function definitions, either at the module level or inside a class; you
can't decorate class definitions.

A decorator is just a function that takes the function to be decorated
as an argument and returns either the same function or some new object.
The return value of the decorator need not be callable (though it
typically is), unless further decorators will be applied to the result.
It's easy to write your own decorators.  The following simple example
just sets an attribute on the function object:

     >>> def deco(func):
     ...    func.attr = 'decorated'
     ...    return func
     ...
     >>> @deco
     ... def f(): pass
     ...
     >>> f
     <function f at 0x402ef0d4>
     >>> f.attr
     'decorated'
     >>>

As a slightly more realistic example, the following decorator checks
that the supplied argument is an integer:

     def require_int (func):
         def wrapper (arg):
             assert isinstance(arg, int)
             return func(arg)

         return wrapper

     @require_int
     def p1 (arg):
         print arg

     @require_int
     def p2(arg):
         print arg*2

An example in PEP 318(1) contains a fancier version of this idea that
lets you both specify the required type and check the returned type.

Decorator functions can take arguments.  If arguments are supplied, your
decorator function is called with only those arguments and must return a
new decorator function; this function must take a single function and
return a function, as previously described.  In other words, ‘@A @B
@C(args)’ becomes:

     def f(): ...
     _deco = C(args)
     f = A(B(_deco(f)))

Getting this right can be slightly brain-bending, but it's not too
difficult.

A small related change makes the *note func_name: 1267. attribute of
functions writable.  This attribute is used to display function names in
tracebacks, so decorators should change the name of any new function
that's constructed and returned.

也參考
......

PEP 318(2) - Decorators for Functions, Methods and Classes

     Written by Kevin D. Smith, Jim Jewett, and Skip Montanaro.  Several
     people wrote patches implementing function decorators, but the one
     that was actually checked in was patch #979728, written by Mark
     Russell.

‘https://wiki.python.org/moin/PythonDecoratorLibrary’

     This Wiki page contains several examples of decorators.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0318/

   (2) https://peps.python.org/pep-0318/


File: python.info,  Node: PEP 322 Reverse Iteration,  Next: PEP 324 New subprocess Module,  Prev: PEP 318 Decorators for Functions and Methods,  Up: Python 2 4 有什麼新功能

1.18.6 PEP 322: Reverse Iteration
---------------------------------

A new built-in function, ‘reversed(seq)’, takes a sequence and returns
an iterator that loops over the elements of the sequence in reverse
order.

     >>> for i in reversed(xrange(1,4)):
     ...    print i
     ...
     3
     2
     1

Compared to extended slicing, such as ‘range(1,4)[::-1]’, *note
reversed(): 80a. is easier to read, runs faster, and uses substantially
less memory.

Note that *note reversed(): 80a. only accepts sequences, not arbitrary
iterators.  If you want to reverse an iterator, first convert it to a
list with *note list(): 5b6.

     >>> input = open('/etc/passwd', 'r')
     >>> for line in reversed(list(input)):
     ...   print line
     ...
     root:*:0:0:System Administrator:/var/root:/bin/tcsh
       ...

也參考
......

PEP 322(1) - Reverse Iteration

     Written and implemented by Raymond Hettinger.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0322/


File: python.info,  Node: PEP 324 New subprocess Module,  Next: PEP 327 Decimal Data Type,  Prev: PEP 322 Reverse Iteration,  Up: Python 2 4 有什麼新功能

1.18.7 PEP 324: New subprocess Module
-------------------------------------

The standard library provides a number of ways to execute a subprocess,
offering different features and different levels of complexity.
‘os.system(command)’ is easy to use, but slow (it runs a shell process
which executes the command) and dangerous (you have to be careful about
escaping the shell's metacharacters).  The ‘popen2’ module offers
classes that can capture standard output and standard error from the
subprocess, but the naming is confusing.  The *note subprocess: c1.
module cleans this up, providing a unified interface that offers all the
features you might need.

Instead of ‘popen2’'s collection of classes, *note subprocess: c1.
contains a single class called *note subprocess.Popen: 17d. whose
constructor supports a number of different keyword arguments.

     class Popen(args, bufsize=0, executable=None,
                 stdin=None, stdout=None, stderr=None,
                 preexec_fn=None, close_fds=False, shell=False,
                 cwd=None, env=None, universal_newlines=False,
                 startupinfo=None, creationflags=0):

'args' is commonly a sequence of strings that will be the arguments to
the program executed as the subprocess.  (If the 'shell' argument is
true, 'args' can be a string which will then be passed on to the shell
for interpretation, just as *note os.system(): 13c8. does.)

'stdin', 'stdout', and 'stderr' specify what the subprocess's input,
output, and error streams will be.  You can provide a file object or a
file descriptor, or you can use the constant ‘subprocess.PIPE’ to create
a pipe between the subprocess and the parent.

The constructor has a number of handy options:

   * 'close_fds' requests that all file descriptors be closed before
     running the subprocess.

   * 'cwd' specifies the working directory in which the subprocess will
     be executed (defaulting to whatever the parent's working directory
     is).

   * 'env' is a dictionary specifying environment variables.

   * 'preexec_fn' is a function that gets called before the child is
     started.

   * 'universal_newlines' opens the child's input and output using
     Python's *note universal newlines: ce1. feature.

Once you've created the ‘Popen’ instance, you can call its ‘wait()’
method to pause until the subprocess has exited, ‘poll()’ to check if
it's exited without pausing, or ‘communicate(data)’ to send the string
'data' to the subprocess's standard input.  ‘communicate(data)’ then
reads any data that the subprocess has sent to its standard output or
standard error, returning a tuple ‘(stdout_data, stderr_data)’.

‘call()’ is a shortcut that passes its arguments along to the ‘Popen’
constructor, waits for the command to complete, and returns the status
code of the subprocess.  It can serve as a safer analog to *note
os.system(): 13c8.:

     sts = subprocess.call(['dpkg', '-i', '/tmp/new-package.deb'])
     if sts == 0:
         # Success
         ...
     else:
         # dpkg returned an error
         ...

The command is invoked without use of the shell.  If you really do want
to use the shell, you can add ‘shell=True’ as a keyword argument and
provide a string instead of a sequence:

     sts = subprocess.call('dpkg -i /tmp/new-package.deb', shell=True)

The PEP takes various examples of shell and Python code and shows how
they'd be translated into Python code that uses *note subprocess: c1.
Reading this section of the PEP is highly recommended.

也參考
......

PEP 324(1) - subprocess - 新的行程模組

     Written and implemented by Peter Åstrand, with assistance from
     Fredrik Lundh and others.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0324/


File: python.info,  Node: PEP 327 Decimal Data Type,  Next: PEP 328 Multi-line Imports,  Prev: PEP 324 New subprocess Module,  Up: Python 2 4 有什麼新功能

1.18.8 PEP 327: Decimal Data Type
---------------------------------

Python has always supported floating-point (FP) numbers, based on the
underlying C double type, as a data type.  However, while most
programming languages provide a floating-point type, many people (even
programmers) are unaware that floating-point numbers don't represent
certain decimal fractions accurately.  The new ‘Decimal’ type can
represent these fractions accurately, up to a user-specified precision
limit.

* Menu:

* Why is Decimal needed?::
* Decimal 型別::
* Context 型別::


File: python.info,  Node: Why is Decimal needed?,  Next: Decimal 型別,  Up: PEP 327 Decimal Data Type

1.18.8.1 Why is Decimal needed?
...............................

The limitations arise from the representation used for floating-point
numbers.  FP numbers are made up of three components:

   * The sign, which is positive or negative.

   * The mantissa, which is a single-digit binary number followed by a
     fractional part.  For example, ‘1.01’ in base-2 notation is ‘1 +
     0/2 + 1/4’, or 1.25 in decimal notation.

   * The exponent, which tells where the decimal point is located in the
     number represented.

For example, the number 1.25 has positive sign, a mantissa value of 1.01
(in binary), and an exponent of 0 (the decimal point doesn't need to be
shifted).  The number 5 has the same sign and mantissa, but the exponent
is 2 because the mantissa is multiplied by 4 (2 to the power of the
exponent 2); 1.25 * 4 equals 5.

Modern systems usually provide floating-point support that conforms to a
standard called IEEE 754.  C's double type is usually implemented as a
64-bit IEEE 754 number, which uses 52 bits of space for the mantissa.
This means that numbers can only be specified to 52 bits of precision.
If you're trying to represent numbers whose expansion repeats endlessly,
the expansion is cut off after 52 bits.  Unfortunately, most software
needs to produce output in base 10, and common fractions in base 10 are
often repeating decimals in binary.  For example, 1.1 decimal is binary
‘1.0001100110011 ...’; .1 = 1/16 + 1/32 + 1/256 plus an infinite number
of additional terms.  IEEE 754 has to chop off that infinitely repeated
decimal after 52 digits, so the representation is slightly inaccurate.

Sometimes you can see this inaccuracy when the number is printed:

     >>> 1.1
     1.1000000000000001

The inaccuracy isn't always visible when you print the number because
the FP-to-decimal-string conversion is provided by the C library, and
most C libraries try to produce sensible output.  Even if it's not
displayed, however, the inaccuracy is still there and subsequent
operations can magnify the error.

For many applications this doesn't matter.  If I'm plotting points and
displaying them on my monitor, the difference between 1.1 and
1.1000000000000001 is too small to be visible.  Reports often limit
output to a certain number of decimal places, and if you round the
number to two or three or even eight decimal places, the error is never
apparent.  However, for applications where it does matter, it's a lot of
work to implement your own custom arithmetic routines.

Hence, the ‘Decimal’ type was created.


File: python.info,  Node: Decimal 型別,  Next: Context 型別,  Prev: Why is Decimal needed?,  Up: PEP 327 Decimal Data Type

1.18.8.2 ‘Decimal’ 型別
.......................

A new module, *note decimal: 2e, was added to Python's standard library.
It contains two classes, ‘Decimal’ and ‘Context’.  ‘Decimal’ instances
represent numbers, and ‘Context’ instances are used to wrap up various
settings such as the precision and default rounding mode.

‘Decimal’ instances are immutable, like regular Python integers and FP
numbers; once it's been created, you can't change the value an instance
represents.  ‘Decimal’ instances can be created from integers or
strings:

     >>> import decimal
     >>> decimal.Decimal(1972)
     Decimal("1972")
     >>> decimal.Decimal("1.1")
     Decimal("1.1")

You can also provide tuples containing the sign, the mantissa
represented as a tuple of decimal digits, and the exponent:

     >>> decimal.Decimal((1, (1, 4, 7, 5), -2))
     Decimal("-14.75")

Cautionary note: the sign bit is a Boolean value, so 0 is positive and 1
is negative.

Converting from floating-point numbers poses a bit of a problem: should
the FP number representing 1.1 turn into the decimal number for exactly
1.1, or for 1.1 plus whatever inaccuracies are introduced?  The decision
was to dodge the issue and leave such a conversion out of the API.
Instead, you should convert the floating-point number into a string
using the desired precision and pass the string to the ‘Decimal’
constructor:

     >>> f = 1.1
     >>> decimal.Decimal(str(f))
     Decimal("1.1")
     >>> decimal.Decimal('%.12f' % f)
     Decimal("1.100000000000")

Once you have ‘Decimal’ instances, you can perform the usual
mathematical operations on them.  One limitation: exponentiation
requires an integer exponent:

     >>> a = decimal.Decimal('35.72')
     >>> b = decimal.Decimal('1.73')
     >>> a+b
     Decimal("37.45")
     >>> a-b
     Decimal("33.99")
     >>> a*b
     Decimal("61.7956")
     >>> a/b
     Decimal("20.64739884393063583815028902")
     >>> a ** 2
     Decimal("1275.9184")
     >>> a**b
     Traceback (most recent call last):
       ...
     decimal.InvalidOperation: x ** (non-integer)

You can combine ‘Decimal’ instances with integers, but not with
floating-point numbers:

     >>> a + 4
     Decimal("39.72")
     >>> a + 4.5
     Traceback (most recent call last):
       ...
     TypeError: You can interact Decimal only with int, long or Decimal data types.
     >>>

‘Decimal’ numbers can be used with the *note math: 81. and *note cmath:
11. modules, but note that they'll be immediately converted to
floating-point numbers before the operation is performed, resulting in a
possible loss of precision and accuracy.  You'll also get back a regular
floating-point number and not a ‘Decimal’.

     >>> import math, cmath
     >>> d = decimal.Decimal('123456789012.345')
     >>> math.sqrt(d)
     351364.18288201344
     >>> cmath.sqrt(-d)
     351364.18288201344j

‘Decimal’ instances have a ‘sqrt()’ method that returns a ‘Decimal’, but
if you need other things such as trigonometric functions you'll have to
implement them.

     >>> d.sqrt()
     Decimal("351364.1828820134592177245001")


File: python.info,  Node: Context 型別,  Prev: Decimal 型別,  Up: PEP 327 Decimal Data Type

1.18.8.3 ‘Context’ 型別
.......................

Instances of the ‘Context’ class encapsulate several settings for
decimal operations:

   * ‘prec’ is the precision, the number of decimal places.

   * ‘rounding’ specifies the rounding mode.  The *note decimal: 2e.
     module has constants for the various possibilities: ‘ROUND_DOWN’,
     ‘ROUND_CEILING’, ‘ROUND_HALF_EVEN’, and various others.

   * ‘traps’ is a dictionary specifying what happens on encountering
     certain error conditions: either an exception is raised or a value
     is returned.  Some examples of error conditions are division by
     zero, loss of precision, and overflow.

There's a thread-local default context available by calling
‘getcontext()’; you can change the properties of this context to alter
the default precision, rounding, or trap handling.  The following
example shows the effect of changing the precision of the default
context:

     >>> decimal.getcontext().prec
     28
     >>> decimal.Decimal(1) / decimal.Decimal(7)
     Decimal("0.1428571428571428571428571429")
     >>> decimal.getcontext().prec = 9
     >>> decimal.Decimal(1) / decimal.Decimal(7)
     Decimal("0.142857143")

The default action for error conditions is selectable; the module can
either return a special value such as infinity or not-a-number, or
exceptions can be raised:

     >>> decimal.Decimal(1) / decimal.Decimal(0)
     Traceback (most recent call last):
       ...
     decimal.DivisionByZero: x / 0
     >>> decimal.getcontext().traps[decimal.DivisionByZero] = False
     >>> decimal.Decimal(1) / decimal.Decimal(0)
     Decimal("Infinity")
     >>>

The ‘Context’ instance also has various methods for formatting numbers
such as ‘to_eng_string()’ and ‘to_sci_string()’.

For more information, see the documentation for the *note decimal: 2e.
module, which includes a quick-start tutorial and a reference.

也參考
......

PEP 327(1) - Decimal Data Type

     Written by Facundo Batista and implemented by Facundo Batista, Eric
     Price, Raymond Hettinger, Aahz, and Tim Peters.

‘http://www.lahey.com/float.htm’

     The article uses Fortran code to illustrate many of the problems
     that floating-point inaccuracy can cause.

‘http://speleotrove.com/decimal/’

     A description of a decimal-based representation.  This
     representation is being proposed as a standard, and underlies the
     new Python decimal type.  Much of this material was written by Mike
     Cowlishaw, designer of the Rexx language.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0327/


File: python.info,  Node: PEP 328 Multi-line Imports,  Next: PEP 331 Locale-Independent Float/String Conversions,  Prev: PEP 327 Decimal Data Type,  Up: Python 2 4 有什麼新功能

1.18.9 PEP 328: Multi-line Imports
----------------------------------

One language change is a small syntactic tweak aimed at making it easier
to import many names from a module.  In a ‘from module import names’
statement, 'names' is a sequence of names separated by commas.  If the
sequence is very long, you can either write multiple imports from the
same module, or you can use backslashes to escape the line endings like
this:

     from SimpleXMLRPCServer import SimpleXMLRPCServer,\
                 SimpleXMLRPCRequestHandler,\
                 CGIXMLRPCRequestHandler,\
                 resolve_dotted_attribute

The syntactic change in Python 2.4 simply allows putting the names
within parentheses.  Python ignores newlines within a parenthesized
expression, so the backslashes are no longer needed:

     from SimpleXMLRPCServer import (SimpleXMLRPCServer,
                                     SimpleXMLRPCRequestHandler,
                                     CGIXMLRPCRequestHandler,
                                     resolve_dotted_attribute)

The PEP also proposes that all *note import: 586. statements be absolute
imports, with a leading ‘.’ character to indicate a relative import.
This part of the PEP was not implemented for Python 2.4, but was
completed for Python 2.5.

也參考
......

PEP 328(1) - Imports: Multi-Line and Absolute/Relative

     Written by Aahz.  Multi-line imports were implemented by Dima
     Dorfman.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0328/


File: python.info,  Node: PEP 331 Locale-Independent Float/String Conversions,  Next: 其他語言更動<16>,  Prev: PEP 328 Multi-line Imports,  Up: Python 2 4 有什麼新功能

1.18.10 PEP 331: Locale-Independent Float/String Conversions
------------------------------------------------------------

The *note locale: 7a. modules lets Python software select various
conversions and display conventions that are localized to a particular
country or language.  However, the module was careful to not change the
numeric locale because various functions in Python's implementation
required that the numeric locale remain set to the ‘'C'’ locale.  Often
this was because the code was using the C library's ‘atof()’ function.

Not setting the numeric locale caused trouble for extensions that used
third-party C libraries, however, because they wouldn't have the correct
locale set.  The motivating example was GTK+, whose user interface
widgets weren't displaying numbers in the current locale.

The solution described in the PEP is to add three new functions to the
Python API that perform ASCII-only conversions, ignoring the locale
setting:

   * ‘PyOS_ascii_strtod(str, ptr)’ and ‘PyOS_ascii_atof(str, ptr)’ both
     convert a string to a C double.

   * ‘PyOS_ascii_formatd(buffer, buf_len, format, d)’ converts a double
     to an ASCII string.

The code for these functions came from the GLib library
(‘https://developer-old.gnome.org/glib/2.26/’), whose developers kindly
relicensed the relevant functions and donated them to the Python
Software Foundation.  The *note locale: 7a. module can now change the
numeric locale, letting extensions such as GTK+ produce the correct
results.

也參考
......

PEP 331(1) - Locale-Independent Float/String Conversions

     Written by Christian R. Reis, and implemented by Gustavo Carneiro.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0331/


File: python.info,  Node: 其他語言更動<16>,  Next: New Improved and Deprecated Modules<3>,  Prev: PEP 331 Locale-Independent Float/String Conversions,  Up: Python 2 4 有什麼新功能

1.18.11 其他語言更動
--------------------

Here are all of the changes that Python 2.4 makes to the core Python
language.

   * Decorators for functions and methods were added ( PEP 318(1)).

   * Built-in *note set(): 57d. and *note frozenset(): 57e. types were
     added ( PEP 218(2)).  Other new built-ins include the
     ‘reversed(seq)’ function ( PEP 322(3)).

   * Generator expressions were added ( PEP 289(4)).

   * Certain numeric expressions no longer return values restricted to
     32 or 64 bits ( PEP 237(5)).

   * You can now put parentheses around the list of names in a ‘from
     module import names’ statement ( PEP 328(6)).

   * The *note dict.update(): 13d0. method now accepts the same argument
     forms as the *note dict: 23b. constructor.  This includes any
     mapping, any iterable of key/value pairs, and keyword arguments.
     (Contributed by Raymond Hettinger.)

   * The string methods ‘ljust()’, ‘rjust()’, and ‘center()’ now take an
     optional argument for specifying a fill character other than a
     space.  (Contributed by Raymond Hettinger.)

   * Strings also gained an ‘rsplit()’ method that works like the
     ‘split()’ method but splits from the end of the string.
     (Contributed by Sean Reifschneider.)

          >>> 'www.python.org'.split('.', 1)
          ['www', 'python.org']
          'www.python.org'.rsplit('.', 1)
          ['www.python', 'org']

   * Three keyword parameters, 'cmp', 'key', and 'reverse', were added
     to the ‘sort()’ method of lists.  These parameters make some common
     usages of ‘sort()’ simpler.  All of these parameters are optional.

     For the 'cmp' parameter, the value should be a comparison function
     that takes two parameters and returns -1, 0, or +1 depending on how
     the parameters compare.  This function will then be used to sort
     the list.  Previously this was the only parameter that could be
     provided to ‘sort()’.

     'key' should be a single-parameter function that takes a list
     element and returns a comparison key for the element.  The list is
     then sorted using the comparison keys.  The following example sorts
     a list case-insensitively:

          >>> L = ['A', 'b', 'c', 'D']
          >>> L.sort()                 # Case-sensitive sort
          >>> L
          ['A', 'D', 'b', 'c']
          >>> # Using 'key' parameter to sort list
          >>> L.sort(key=lambda x: x.lower())
          >>> L
          ['A', 'b', 'c', 'D']
          >>> # Old-fashioned way
          >>> L.sort(cmp=lambda x,y: cmp(x.lower(), y.lower()))
          >>> L
          ['A', 'b', 'c', 'D']

     The last example, which uses the 'cmp' parameter, is the old way to
     perform a case-insensitive sort.  It works but is slower than using
     a 'key' parameter.  Using 'key' calls ‘lower()’ method once for
     each element in the list while using 'cmp' will call it twice for
     each comparison, so using 'key' saves on invocations of the
     ‘lower()’ method.

     For simple key functions and comparison functions, it is often
     possible to avoid a *note lambda: 1234. expression by using an
     unbound method instead.  For example, the above case-insensitive
     sort is best written as:

          >>> L.sort(key=str.lower)
          >>> L
          ['A', 'b', 'c', 'D']

     Finally, the 'reverse' parameter takes a Boolean value.  If the
     value is true, the list will be sorted into reverse order.  Instead
     of ‘L.sort(); L.reverse()’, you can now write
     ‘L.sort(reverse=True)’.

     The results of sorting are now guaranteed to be stable.  This means
     that two entries with equal keys will be returned in the same order
     as they were input.  For example, you can sort a list of people by
     name, and then sort the list by age, resulting in a list sorted by
     age where people with the same age are in name-sorted order.

     (All changes to ‘sort()’ contributed by Raymond Hettinger.)

   * There is a new built-in function ‘sorted(iterable)’ that works like
     the in-place *note list.sort(): b76. method but can be used in
     expressions.  The differences are:

   * the input may be any iterable;

   * a newly formed copy is sorted, leaving the original intact; and

   * the expression returns the new sorted copy

          >>> L = [9,7,8,3,2,4,1,6,5]
          >>> [10+i for i in sorted(L)]       # usable in a list comprehension
          [11, 12, 13, 14, 15, 16, 17, 18, 19]
          >>> L                               # original is left unchanged
          [9,7,8,3,2,4,1,6,5]
          >>> sorted('Monty Python')          # any iterable may be an input
          [' ', 'M', 'P', 'h', 'n', 'n', 'o', 'o', 't', 't', 'y', 'y']

          >>> # List the contents of a dict sorted by key values
          >>> colormap = dict(red=1, blue=2, green=3, black=4, yellow=5)
          >>> for k, v in sorted(colormap.iteritems()):
          ...     print k, v
          ...
          black 4
          blue 2
          green 3
          red 1
          yellow 5

     （由 Raymond Hettinger 所貢獻。）

   * Integer operations will no longer trigger an ‘OverflowWarning’.
     The ‘OverflowWarning’ warning will disappear in Python 2.5.

   * The interpreter gained a new switch, *note -m: 585, that takes a
     name, searches for the corresponding module on ‘sys.path’, and runs
     the module as a script.  For example, you can now run the Python
     profiler with ‘python -m profile’.  (Contributed by Nick Coghlan.)

   * The ‘eval(expr, globals, locals)’ and ‘execfile(filename, globals,
     locals)’ functions and the ‘exec’ statement now accept any mapping
     type for the 'locals' parameter.  Previously this had to be a
     regular Python dictionary.  (Contributed by Raymond Hettinger.)

   * The *note zip(): 774. built-in function and ‘itertools.izip()’ now
     return an empty list if called with no arguments.  Previously they
     raised a *note TypeError: 4dd. exception.  This makes them more
     suitable for use with variable length argument lists:

          >>> def transpose(array):
          ...    return zip(*array)
          ...
          >>> transpose([(1,2,3), (4,5,6)])
          [(1, 4), (2, 5), (3, 6)]
          >>> transpose([])
          []

     （由 Raymond Hettinger 所貢獻。）

   * Encountering a failure while importing a module no longer leaves a
     partially initialized module object in ‘sys.modules’.  The
     incomplete module object left behind would fool further imports of
     the same module into succeeding, leading to confusing errors.
     (Fixed by Tim Peters.)

   * *note None: 61b. is now a constant; code that binds a new value to
     the name ‘None’ is now a syntax error.  (Contributed by Raymond
     Hettinger.)

* Menu:

* 最佳化: 最佳化<15>.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0318/

   (2) https://peps.python.org/pep-0218/

   (3) https://peps.python.org/pep-0322/

   (4) https://peps.python.org/pep-0289/

   (5) https://peps.python.org/pep-0237/

   (6) https://peps.python.org/pep-0328/


File: python.info,  Node: 最佳化<15>,  Up: 其他語言更動<16>

1.18.11.1 最佳化
................

   * The inner loops for list and tuple slicing were optimized and now
     run about one-third faster.  The inner loops for dictionaries were
     also optimized, resulting in performance boosts for ‘keys()’,
     ‘values()’, ‘items()’, ‘iterkeys()’, ‘itervalues()’, and
     ‘iteritems()’.  (Contributed by Raymond Hettinger.)

   * The machinery for growing and shrinking lists was optimized for
     speed and for space efficiency.  Appending and popping from lists
     now runs faster due to more efficient code paths and less frequent
     use of the underlying system ‘realloc()’.  List comprehensions also
     benefit.  ‘list.extend()’ was also optimized and no longer converts
     its argument into a temporary list before extending the base list.
     (Contributed by Raymond Hettinger.)

   * *note list(): 5b6, *note tuple(): 322, *note map(): 808, *note
     filter(): 809, and *note zip(): 774. now run several times faster
     with non-sequence arguments that supply a ‘__len__()’ method.
     (Contributed by Raymond Hettinger.)

   * The methods ‘list.__getitem__()’, ‘dict.__getitem__()’, and
     ‘dict.__contains__()’ are now implemented as ‘method_descriptor’
     objects rather than ‘wrapper_descriptor’ objects.  This form of
     access doubles their performance and makes them more suitable for
     use as arguments to functionals: ‘map(mydict.__getitem__,
     keylist)’.  (Contributed by Raymond Hettinger.)

   * Added a new opcode, ‘LIST_APPEND’, that simplifies the generated
     bytecode for list comprehensions and speeds them up by about a
     third.  (Contributed by Raymond Hettinger.)

   * The peephole bytecode optimizer has been improved to produce
     shorter, faster bytecode; remarkably, the resulting bytecode is
     more readable.  (Enhanced by Raymond Hettinger.)

   * String concatenations in statements of the form ‘s = s + "abc"’ and
     ‘s += "abc"’ are now performed more efficiently in certain
     circumstances.  This optimization won't be present in other Python
     implementations such as Jython, so you shouldn't rely on it; using
     the ‘join()’ method of strings is still recommended when you want
     to efficiently glue a large number of strings together.
     (Contributed by Armin Rigo.)

The net result of the 2.4 optimizations is that Python 2.4 runs the
pystone benchmark around 5% faster than Python 2.3 and 35% faster than
Python 2.2.  (pystone is not a particularly good benchmark, but it's the
most commonly used measurement of Python's performance.  Your own
applications may show greater or smaller benefits from Python 2.4.)


File: python.info,  Node: New Improved and Deprecated Modules<3>,  Next: Build and C API Changes<10>,  Prev: 其他語言更動<16>,  Up: Python 2 4 有什麼新功能

1.18.12 New, Improved, and Deprecated Modules
---------------------------------------------

As usual, Python's standard library received a number of enhancements
and bug fixes.  Here's a partial list of the most notable changes,
sorted alphabetically by module name.  Consult the ‘Misc/NEWS’ file in
the source tree for a more complete list of changes, or look through the
CVS logs for all the details.

   * The ‘asyncore’ module's ‘loop()’ function now has a 'count'
     parameter that lets you perform a limited number of passes through
     the polling loop.  The default is still to loop forever.

   * The *note base64: a. module now has more complete RFC 3548(1)
     support for Base64, Base32, and Base16 encoding and decoding,
     including optional case folding and optional alternative alphabets.
     (Contributed by Barry Warsaw.)

   * The *note bisect: d. module now has an underlying C implementation
     for improved performance.  (Contributed by Dmitry Vasiliev.)

   * The CJKCodecs collections of East Asian codecs, maintained by
     Hye-Shik Chang, was integrated into 2.4.  The new encodings are:

   * Chinese (PRC): gb2312, gbk, gb18030, big5hkscs, hz

   * Chinese (ROC): big5, cp950

   * 
     Japanese: cp932, euc-jis-2004, euc-jp, euc-jisx0213, iso-2022-jp,

          iso-2022-jp-1, iso-2022-jp-2, iso-2022-jp-3, iso-2022-jp-ext,
          iso-2022-jp-2004, shift-jis, shift-jisx0213, shift-jis-2004

   * Korean: cp949, euc-kr, johab, iso-2022-kr

   * Some other new encodings were added: HP Roman8, ISO_8859-11,
     ISO_8859-16, PCTP-154, and TIS-620.

   * The UTF-8 and UTF-16 codecs now cope better with receiving partial
     input.  Previously the ‘StreamReader’ class would try to read more
     data, making it impossible to resume decoding from the stream.  The
     ‘read()’ method will now return as much data as it can and future
     calls will resume decoding where previous ones left off.
     (Implemented by Walter Dörwald.)

   * There is a new *note collections: 16. module for various
     specialized collection datatypes.  Currently it contains just one
     type, ‘deque’, a double-ended queue that supports efficiently
     adding and removing elements from either end:

          >>> from collections import deque
          >>> d = deque('ghi')        # make a new deque with three items
          >>> d.append('j')           # add a new entry to the right side
          >>> d.appendleft('f')       # add a new entry to the left side
          >>> d                       # show the representation of the deque
          deque(['f', 'g', 'h', 'i', 'j'])
          >>> d.pop()                 # return and remove the rightmost item
          'j'
          >>> d.popleft()             # return and remove the leftmost item
          'f'
          >>> list(d)                 # list the contents of the deque
          ['g', 'h', 'i']
          >>> 'h' in d                # search the deque
          True

     Several modules, such as the ‘Queue’ and *note threading: d6.
     modules, now take advantage of *note collections.deque: 580. for
     improved performance.  (Contributed by Raymond Hettinger.)

   * The *note ConfigParser: 1b. classes have been enhanced slightly.
     The *note read(): 13d3. method now returns a list of the files that
     were successfully parsed, and the *note set(): 1205. method raises
     *note TypeError: 4dd. if passed a 'value' argument that isn't a
     string.  (Contributed by John Belmonte and David Goodger.)

   * The *note curses: 23. module now supports the ncurses extension
     ‘use_default_colors()’.  On platforms where the terminal supports
     transparency, this makes it possible to use a transparent
     background.  (Contributed by Jörg Lehmann.)

   * The *note difflib: 2f. module now includes an ‘HtmlDiff’ class that
     creates an HTML table showing a side by side comparison of two
     versions of a text.  (Contributed by Dan Gass.)

   * The *note email: 32. package was updated to version 3.0, which
     dropped various deprecated APIs and removes support for Python
     versions earlier than 2.3.  The 3.0 version of the package uses a
     new incremental parser for MIME messages, available in the
     ‘email.FeedParser’ module.  The new parser doesn't require reading
     the entire message into memory, and doesn't raise exceptions if a
     message is malformed; instead it records any problems in the
     ‘defect’ attribute of the message.  (Developed by Anthony Baxter,
     Barry Warsaw, Thomas Wouters, and others.)

   * The *note heapq: 5f. module has been converted to C. The resulting
     tenfold improvement in speed makes the module suitable for handling
     high volumes of data.  In addition, the module has two new
     functions ‘nlargest()’ and ‘nsmallest()’ that use heaps to find the
     N largest or smallest values in a dataset without the expense of a
     full sort.  (Contributed by Raymond Hettinger.)

   * The *note httplib: 64. module now contains constants for HTTP
     status codes defined in various HTTP-related RFC documents.
     Constants have names such as ‘OK’, ‘CREATED’, ‘CONTINUE’, and
     ‘MOVED_PERMANENTLY’; use pydoc to get a full list.  (Contributed by
     Andrew Eland.)

   * The *note imaplib: 6a. module now supports IMAP's THREAD command
     (contributed by Yves Dionne) and new ‘deleteacl()’ and ‘myrights()’
     methods (contributed by Arnaud Mazin).

   * The *note itertools: 75. module gained a ‘groupby(iterable[,
     *func*])’ function.  'iterable' is something that can be iterated
     over to return a stream of elements, and the optional 'func'
     parameter is a function that takes an element and returns a key
     value; if omitted, the key is simply the element itself.
     ‘groupby()’ then groups the elements into subsequences which have
     matching values of the key, and returns a series of 2-tuples
     containing the key value and an iterator over the subsequence.

     Here's an example to make this clearer.  The 'key' function simply
     returns whether a number is even or odd, so the result of
     ‘groupby()’ is to return consecutive runs of odd or even numbers.

          >>> import itertools
          >>> L = [2, 4, 6, 7, 8, 9, 11, 12, 14]
          >>> for key_val, it in itertools.groupby(L, lambda x: x % 2):
          ...    print key_val, list(it)
          ...
          0 [2, 4, 6]
          1 [7]
          0 [8]
          1 [9, 11]
          0 [12, 14]
          >>>

     ‘groupby()’ is typically used with sorted input.  The logic for
     ‘groupby()’ is similar to the Unix ‘uniq’ filter which makes it
     handy for eliminating, counting, or identifying duplicate elements:

          >>> word = 'abracadabra'
          >>> letters = sorted(word)   # Turn string into a sorted list of letters
          >>> letters
          ['a', 'a', 'a', 'a', 'a', 'b', 'b', 'c', 'd', 'r', 'r']
          >>> for k, g in itertools.groupby(letters):
          ...    print k, list(g)
          ...
          a ['a', 'a', 'a', 'a', 'a']
          b ['b', 'b']
          c ['c']
          d ['d']
          r ['r', 'r']
          >>> # List unique letters
          >>> [k for k, g in groupby(letters)]
          ['a', 'b', 'c', 'd', 'r']
          >>> # Count letter occurrences
          >>> [(k, len(list(g))) for k, g in groupby(letters)]
          [('a', 5), ('b', 2), ('c', 1), ('d', 1), ('r', 2)]

     （由 Hye-Shik Chang 所貢獻。）

   * *note itertools: 75. also gained a function named ‘tee(iterator,
     N)’ that returns 'N' independent iterators that replicate
     'iterator'.  If 'N' is omitted, the default is 2.

          >>> L = [1,2,3]
          >>> i1, i2 = itertools.tee(L)
          >>> i1,i2
          (<itertools.tee object at 0x402c2080>, <itertools.tee object at 0x402c2090>)
          >>> list(i1)               # Run the first iterator to exhaustion
          [1, 2, 3]
          >>> list(i2)               # Run the second iterator to exhaustion
          [1, 2, 3]

     Note that ‘tee()’ has to keep copies of the values returned by the
     iterator; in the worst case, it may need to keep all of them.  This
     should therefore be used carefully if the leading iterator can run
     far ahead of the trailing iterator in a long stream of inputs.  If
     the separation is large, then you might as well use *note list():
     5b6. instead.  When the iterators track closely with one another,
     ‘tee()’ is ideal.  Possible applications include bookmarking,
     windowing, or lookahead iterators.  (Contributed by Raymond
     Hettinger.)

   * A number of functions were added to the *note locale: 7a. module,
     such as ‘bind_textdomain_codeset()’ to specify a particular
     encoding and a family of ‘l*gettext()’ functions that return
     messages in the chosen encoding.  (Contributed by Gustavo
     Niemeyer.)

   * Some keyword arguments were added to the *note logging: 7b.
     package's ‘basicConfig()’ function to simplify log configuration.
     The default behavior is to log messages to standard error, but
     various keyword arguments can be specified to log to a particular
     file, change the logging format, or set the logging level.  For
     example:

          import logging
          logging.basicConfig(filename='/var/log/application.log',
              level=0,  # Log all messages
              format='%(levelname):%(process):%(thread):%(message)')

     Other additions to the *note logging: 7b. package include a
     ‘log(level, msg)’ convenience method, as well as a
     ‘TimedRotatingFileHandler’ class that rotates its log files at a
     timed interval.  The module already had ‘RotatingFileHandler’,
     which rotated logs once the file exceeded a certain size.  Both
     classes derive from a new ‘BaseRotatingHandler’ class that can be
     used to implement other rotating handlers.

     (Changes implemented by Vinay Sajip.)

   * The *note marshal: 80. module now shares interned strings on
     unpacking a data structure.  This may shrink the size of certain
     pickle strings, but the primary effect is to make ‘.pyc’ files
     significantly smaller.  (Contributed by Martin von Löwis.)

   * The ‘nntplib’ module's ‘NNTP’ class gained ‘description()’ and
     ‘descriptions()’ methods to retrieve newsgroup descriptions for a
     single group or for a range of groups.  (Contributed by Jürgen A.
     Erhard.)

   * Two new functions were added to the *note operator: 8f. module,
     ‘attrgetter(attr)’ and ‘itemgetter(index)’.  Both functions return
     callables that take a single argument and return the corresponding
     attribute or item; these callables make excellent data extractors
     when used with *note map(): 808. or *note sorted(): b75.  For
     example:

          >>> L = [('c', 2), ('d', 1), ('a', 4), ('b', 3)]
          >>> map(operator.itemgetter(0), L)
          ['c', 'd', 'a', 'b']
          >>> map(operator.itemgetter(1), L)
          [2, 1, 4, 3]
          >>> sorted(L, key=operator.itemgetter(1)) # Sort list by second tuple item
          [('d', 1), ('c', 2), ('b', 3), ('a', 4)]

     （由 Raymond Hettinger 所貢獻。）

   * The *note optparse: 90. module was updated in various ways.  The
     module now passes its messages through *note gettext.gettext():
     13d4, making it possible to internationalize Optik's help and error
     messages.  Help messages for options can now include the string
     ‘'%default'’, which will be replaced by the option's default value.
     (Contributed by Greg Ward.)

   * The long-term plan is to deprecate the ‘rfc822’ module in some
     future Python release in favor of the *note email: 32. package.  To
     this end, the *note email.Utils.formatdate: 13d5. function has been
     changed to make it usable as a replacement for
     ‘rfc822.formatdate()’.  You may want to write new e-mail processing
     code with this in mind.  (Change implemented by Anthony Baxter.)

   * A new ‘urandom(n)’ function was added to the *note os: 91. module,
     returning a string containing 'n' bytes of random data.  This
     function provides access to platform-specific sources of randomness
     such as ‘/dev/urandom’ on Linux or the Windows CryptoAPI.
     (Contributed by Trevor Perrin.)

   * Another new function: ‘os.path.lexists(path)’ returns true if the
     file specified by 'path' exists, whether or not it's a symbolic
     link.  This differs from the existing ‘os.path.exists(path)’
     function, which returns false if 'path' is a symlink that points to
     a destination that doesn't exist.  (Contributed by Beni
     Cherniavsky.)

   * A new ‘getsid()’ function was added to the *note posix: 9b. module
     that underlies the *note os: 91. module.  (Contributed by J.
     Raynor.)

   * The *note poplib: 9a. module now supports POP over SSL.
     (Contributed by Hector Urtubia.)

   * The *note profile: 9d. module can now profile C extension
     functions.  (Contributed by Nick Bastin.)

   * The *note random: a6. module has a new method called
     ‘getrandbits(N)’ that returns a long integer 'N' bits in length.
     The existing ‘randrange()’ method now uses ‘getrandbits()’ where
     appropriate, making generation of arbitrarily large random numbers
     more efficient.  (Contributed by Raymond Hettinger.)

   * The regular expression language accepted by the *note re: a7.
     module was extended with simple conditional expressions, written as
     ‘(?(group)A|B)’.  'group' is either a numeric group ID or a group
     name defined with ‘(?P<group>...)’ earlier in the expression.  If
     the specified group matched, the regular expression pattern 'A'
     will be tested against the string; if the group didn't match, the
     pattern 'B' will be used instead.  (Contributed by Gustavo
     Niemeyer.)

   * The *note re: a7. module is also no longer recursive, thanks to a
     massive amount of work by Gustavo Niemeyer.  In a recursive regular
     expression engine, certain patterns result in a large amount of C
     stack space being consumed, and it was possible to overflow the
     stack.  For example, if you matched a 30000-byte string of ‘a’
     characters against the expression ‘(a|b)+’, one stack frame was
     consumed per character.  Python 2.3 tried to check for stack
     overflow and raise a *note RuntimeError: 179. exception, but
     certain patterns could sidestep the checking and if you were
     unlucky Python could segfault.  Python 2.4's regular expression
     engine can match this pattern without problems.

   * The *note signal: b4. module now performs tighter error-checking on
     the parameters to the *note signal.signal(): 10cd. function.  For
     example, you can't set a handler on the ‘SIGKILL’ signal; previous
     versions of Python would quietly accept this, but 2.4 will raise a
     *note RuntimeError: 179. exception.

   * Two new functions were added to the *note socket: b8. module.
     ‘socketpair()’ returns a pair of connected sockets and
     ‘getservbyport(port)’ looks up the service name for a given port
     number.  (Contributed by Dave Cole and Barry Warsaw.)

   * The ‘sys.exitfunc()’ function has been deprecated.  Code should be
     using the existing *note atexit: 9. module, which correctly handles
     calling multiple exit functions.  Eventually ‘sys.exitfunc()’ will
     become a purely internal interface, accessed only by *note atexit:
     9.

   * The *note tarfile: c8. module now generates GNU-format tar files by
     default.  (Contributed by Lars Gustäbel.)

   * The *note threading: d6. module now has an elegantly simple way to
     support thread-local data.  The module contains a ‘local’ class
     whose attribute values are local to different threads.

          import threading

          data = threading.local()
          data.number = 42
          data.url = ('www.python.org', 80)

     Other threads can assign and retrieve their own values for the
     ‘number’ and ‘url’ attributes.  You can subclass ‘local’ to
     initialize attributes or to add methods.  (Contributed by Jim
     Fulton.)

   * The *note timeit: d8. module now automatically disables periodic
     garbage collection during the timing loop.  This change makes
     consecutive timings more comparable.  (Contributed by Raymond
     Hettinger.)

   * The *note weakref: fc. module now supports a wider variety of
     objects including Python functions, class instances, sets,
     frozensets, deques, arrays, files, sockets, and regular expression
     pattern objects.  (Contributed by Raymond Hettinger.)

   * The *note xmlrpclib: 114. module now supports a multi-call
     extension for transmitting multiple XML-RPC calls in a single HTTP
     operation.  (Contributed by Brian Quinlan.)

   * The ‘mpz’, ‘rotor’, and ‘xreadlines’ modules have been removed.

* Menu:

* cookielib::
* doctest: doctest<5>.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc3548.html


File: python.info,  Node: cookielib,  Next: doctest<5>,  Up: New Improved and Deprecated Modules<3>

1.18.12.1 cookielib
...................

The *note cookielib: 66. library supports client-side handling for HTTP
cookies, mirroring the *note Cookie: 67. module's server-side cookie
support.  Cookies are stored in cookie jars; the library transparently
stores cookies offered by the web server in the cookie jar, and fetches
the cookie from the jar when connecting to the server.  As in web
browsers, policy objects control whether cookies are accepted or not.

In order to store cookies across sessions, two implementations of cookie
jars are provided: one that stores cookies in the Netscape format so
applications can use the Mozilla or Lynx cookie files, and one that
stores cookies in the same format as the Perl libwww library.

*note urllib2: f4. has been changed to interact with *note cookielib:
66.: ‘HTTPCookieProcessor’ manages a cookie jar that is used when
accessing URLs.

This module was contributed by John J. Lee.


File: python.info,  Node: doctest<5>,  Prev: cookielib,  Up: New Improved and Deprecated Modules<3>

1.18.12.2 doctest
.................

The *note doctest: 31. module underwent considerable refactoring thanks
to Edward Loper and Tim Peters.  Testing can still be as simple as
running *note doctest.testmod(): 13d8, but the refactorings allow
customizing the module's operation in various ways

The new ‘DocTestFinder’ class extracts the tests from a given object's
docstrings:

     def f (x, y):
         """>>> f(2,2)
     4
     >>> f(3,2)
     6
         """
         return x*y

     finder = doctest.DocTestFinder()

     # Get list of DocTest instances
     tests = finder.find(f)

The new ‘DocTestRunner’ class then runs individual tests and can produce
a summary of the results:

     runner = doctest.DocTestRunner()
     for t in tests:
         tried, failed = runner.run(t)

     runner.summarize(verbose=1)

The above example produces the following output:

     1 items passed all tests:
        2 tests in f
     2 tests in 1 items.
     2 passed and 0 failed.
     Test passed.

‘DocTestRunner’ uses an instance of the ‘OutputChecker’ class to compare
the expected output with the actual output.  This class takes a number
of different flags that customize its behaviour; ambitious users can
also write a completely new subclass of ‘OutputChecker’.

The default output checker provides a number of handy features.  For
example, with the *note doctest.ELLIPSIS: 13d9. option flag, an ellipsis
(‘...’) in the expected output matches any substring, making it easier
to accommodate outputs that vary in minor ways:

     def o (n):
         """>>> o(1)
     <__main__.C instance at 0x...>
     >>>
     """

Another special string, ‘<BLANKLINE>’, matches a blank line:

     def p (n):
         """>>> p(1)
     <BLANKLINE>
     >>>
     """

Another new capability is producing a diff-style display of the output
by specifying the *note doctest.REPORT_UDIFF: 13da. (unified diffs),
*note doctest.REPORT_CDIFF: 13db. (context diffs), or *note
doctest.REPORT_NDIFF: 13dc. (delta-style) option flags.  For example:

     def g (n):
         """>>> g(4)
     here
     is
     a
     lengthy
     >>>"""
         L = 'here is a rather lengthy list of words'.split()
         for word in L[:n]:
             print word

Running the above function's tests with *note doctest.REPORT_UDIFF:
13da. specified, you get the following output:

     **********************************************************************
     File "t.py", line 15, in g
     Failed example:
         g(4)
     Differences (unified diff with -expected +actual):
         @@ -2,3 +2,3 @@
          is
          a
         -lengthy
         +rather
     **********************************************************************


File: python.info,  Node: Build and C API Changes<10>,  Next: Porting to Python 2 4,  Prev: New Improved and Deprecated Modules<3>,  Up: Python 2 4 有什麼新功能

1.18.13 Build and C API Changes
-------------------------------

Some of the changes to Python's build process and to the C API are:

   * Three new convenience macros were added for common return values
     from extension functions: *note Py_RETURN_NONE: 13de, *note
     Py_RETURN_TRUE: 13df, and *note Py_RETURN_FALSE: 13e0.
     (Contributed by Brett Cannon.)

   * Another new macro, *note Py_CLEAR: 51e, decreases the reference
     count of 'obj' and sets 'obj' to the null pointer.  (Contributed by
     Jim Fulton.)

   * A new function, ‘PyTuple_Pack(N, obj1, obj2, ..., objN)’,
     constructs tuples from a variable length argument list of Python
     objects.  (Contributed by Raymond Hettinger.)

   * A new function, ‘PyDict_Contains(d, k)’, implements fast dictionary
     lookups without masking exceptions raised during the look-up
     process.  (Contributed by Raymond Hettinger.)

   * The Py_IS_NAN(X) macro returns 1 if its float or double argument
     'X' is a NaN. (Contributed by Tim Peters.)

   * C code can avoid unnecessary locking by using the new
     ‘PyEval_ThreadsInitialized()’ function to tell if any thread
     operations have been performed.  If this function returns false, no
     lock operations are needed.  (Contributed by Nick Coghlan.)

   * A new function, *note PyArg_VaParseTupleAndKeywords(): 2ea, is the
     same as *note PyArg_ParseTupleAndKeywords(): 2e9. but takes a
     ‘va_list’ instead of a number of arguments.  (Contributed by Greg
     Chapman.)

   * A new method flag, *note METH_COEXIST: 13e1, allows a function
     defined in slots to co-exist with a *note PyCFunction: 13e2. having
     the same name.  This can halve the access time for a method such as
     ‘set.__contains__()’.  (Contributed by Raymond Hettinger.)

   * Python can now be built with additional profiling for the
     interpreter itself, intended as an aid to people developing the
     Python core.  Providing ‘--enable-profiling’ to the ‘configure’
     script will let you profile the interpreter with ‘gprof’, and
     providing the ‘--with-tsc’ switch enables profiling using the
     Pentium's Time-Stamp-Counter register.  Note that the ‘--with-tsc’
     switch is slightly misnamed, because the profiling feature also
     works on the PowerPC platform, though that processor architecture
     doesn't call that register "the TSC register".  (Contributed by
     Jeremy Hylton.)

   * The ‘tracebackobject’ type has been renamed to ‘PyTracebackObject’.

* Menu:

* Port-Specific Changes: Port-Specific Changes<2>.


File: python.info,  Node: Port-Specific Changes<2>,  Up: Build and C API Changes<10>

1.18.13.1 Port-Specific Changes
...............................

   * The Windows port now builds under MSVC++ 7.1 as well as version 6.
     (Contributed by Martin von Löwis.)


File: python.info,  Node: Porting to Python 2 4,  Next: 致謝<4>,  Prev: Build and C API Changes<10>,  Up: Python 2 4 有什麼新功能

1.18.14 Porting to Python 2.4
-----------------------------

This section lists previously described changes that may require changes
to your code:

   * Left shifts and hexadecimal/octal constants that are too large no
     longer trigger a *note FutureWarning: 357. and return a value
     limited to 32 or 64 bits; instead they return a long integer.

   * Integer operations will no longer trigger an ‘OverflowWarning’.
     The ‘OverflowWarning’ warning will disappear in Python 2.5.

   * The *note zip(): 774. built-in function and ‘itertools.izip()’ now
     return an empty list instead of raising a *note TypeError: 4dd.
     exception if called with no arguments.

   * You can no longer compare the ‘date’ and *note datetime: 1b0.
     instances provided by the *note datetime: 28. module.  Two
     instances of different classes will now always be unequal, and
     relative comparisons (‘<’, ‘>’) will raise a *note TypeError: 4dd.

   * ‘dircache.listdir()’ now passes exceptions to the caller instead of
     returning empty lists.

   * ‘LexicalHandler.startDTD()’ used to receive the public and system
     IDs in the wrong order.  This has been corrected; applications
     relying on the wrong order need to be fixed.

   * *note fcntl.ioctl(): 13e5. now warns if the 'mutate' argument is
     omitted and relevant.

   * The *note tarfile: c8. module now generates GNU-format tar files by
     default.

   * Encountering a failure while importing a module no longer leaves a
     partially initialized module object in ‘sys.modules’.

   * *note None: 61b. is now a constant; code that binds a new value to
     the name ‘None’ is now a syntax error.

   * The ‘signals.signal()’ function now raises a *note RuntimeError:
     179. exception for certain illegal values; previously these errors
     would pass silently.  For example, you can no longer set a handler
     on the ‘SIGKILL’ signal.


File: python.info,  Node: 致謝<4>,  Prev: Porting to Python 2 4,  Up: Python 2 4 有什麼新功能

1.18.15 致謝
------------

The author would like to thank the following people for offering
suggestions, corrections and assistance with various drafts of this
article: Koray Can, Hye-Shik Chang, Michael Dyck, Raymond Hettinger,
Brian Hurt, Hamish Lawson, Fredrik Lundh, Sean Reifschneider, Sadruddin
Rejeb.


File: python.info,  Node: Python 2 3 有什麼新功能,  Next: Python 2 2 有什麼新功能,  Prev: Python 2 4 有什麼新功能,  Up: Python 有什麼新功能？

1.19 Python 2.3 有什麼新功能
============================


作者: A.M. Kuchling

This article explains the new features in Python 2.3.  Python 2.3 was
released on July 29, 2003.

The main themes for Python 2.3 are polishing some of the features added
in 2.2, adding various small but useful enhancements to the core
language, and expanding the standard library.  The new object model
introduced in the previous version has benefited from 18 months of
bugfixes and from optimization efforts that have improved the
performance of new-style classes.  A few new built-in functions have
been added such as *note sum(): 411. and *note enumerate(): 13ea.  The
*note in: 2c5. operator can now be used for substring searches (e.g.
‘"ab" in "abc"’ returns *note True: bb4.).

Some of the many new library features include Boolean, set, heap, and
date/time data types, the ability to import modules from ZIP-format
archives, metadata support for the long-awaited Python catalog, an
updated version of IDLE, and modules for logging messages, wrapping
text, parsing CSV files, processing command-line options, using
BerkeleyDB databases...  the list of new and enhanced modules is
lengthy.

This article doesn't attempt to provide a complete specification of the
new features, but instead provides a convenient overview.  For full
details, you should refer to the documentation for Python 2.3, such as
the Python Library Reference and the Python Reference Manual.  If you
want to understand the complete implementation and design rationale,
refer to the PEP for a particular new feature.

* Menu:

* PEP 218; A Standard Set Datatype: PEP 218 A Standard Set Datatype.
* PEP 255; Simple Generators: PEP 255 Simple Generators.
* PEP 263; Source Code Encodings: PEP 263 Source Code Encodings.
* PEP 273; Importing Modules from ZIP Archives: PEP 273 Importing Modules from ZIP Archives.
* PEP 277; Unicode file name support for Windows NT: PEP 277 Unicode file name support for Windows NT.
* PEP 278; Universal Newline Support: PEP 278 Universal Newline Support.
* PEP 279：enumerate(): PEP 279：enumerate.
* PEP 282; The logging Package: PEP 282 The logging Package.
* PEP 285; A Boolean Type: PEP 285 A Boolean Type.
* PEP 293; Codec Error Handling Callbacks: PEP 293 Codec Error Handling Callbacks.
* PEP 301; Package Index and Metadata for Distutils: PEP 301 Package Index and Metadata for Distutils.
* PEP 302; New Import Hooks: PEP 302 New Import Hooks.
* PEP 305; Comma-separated Files: PEP 305 Comma-separated Files.
* PEP 307; Pickle Enhancements: PEP 307 Pickle Enhancements.
* Extended Slices::
* 其他語言更動: 其他語言更動<17>.
* New, Improved, and Deprecated Modules: New Improved and Deprecated Modules<4>.
* Pymalloc; A Specialized Object Allocator: Pymalloc A Specialized Object Allocator.
* Build and C API Changes: Build and C API Changes<11>.
* Other Changes and Fixes: Other Changes and Fixes<2>.
* Porting to Python 2.3: Porting to Python 2 3.
* 致謝: 致謝<5>.


File: python.info,  Node: PEP 218 A Standard Set Datatype,  Next: PEP 255 Simple Generators,  Up: Python 2 3 有什麼新功能

1.19.1 PEP 218: A Standard Set Datatype
---------------------------------------

The new ‘sets’ module contains an implementation of a set datatype.  The
‘Set’ class is for mutable sets, sets that can have members added and
removed.  The ‘ImmutableSet’ class is for sets that can't be modified,
and instances of ‘ImmutableSet’ can therefore be used as dictionary
keys.  Sets are built on top of dictionaries, so the elements within a
set must be hashable.

以下是個簡單範例：

     >>> import sets
     >>> S = sets.Set([1,2,3])
     >>> S
     Set([1, 2, 3])
     >>> 1 in S
     True
     >>> 0 in S
     False
     >>> S.add(5)
     >>> S.remove(3)
     >>> S
     Set([1, 2, 5])
     >>>

The union and intersection of sets can be computed with the *note
union(): 13ec. and *note intersection(): 13ed. methods; an alternative
notation uses the bitwise operators ‘&’ and ‘|’.  Mutable sets also have
in-place versions of these methods, ‘union_update()’ and *note
intersection_update(): 13ee.

     >>> S1 = sets.Set([1,2,3])
     >>> S2 = sets.Set([4,5,6])
     >>> S1.union(S2)
     Set([1, 2, 3, 4, 5, 6])
     >>> S1 | S2                  # Alternative notation
     Set([1, 2, 3, 4, 5, 6])
     >>> S1.intersection(S2)
     Set([])
     >>> S1 & S2                  # Alternative notation
     Set([])
     >>> S1.union_update(S2)
     >>> S1
     Set([1, 2, 3, 4, 5, 6])
     >>>

It's also possible to take the symmetric difference of two sets.  This
is the set of all elements in the union that aren't in the intersection.
Another way of putting it is that the symmetric difference contains all
elements that are in exactly one set.  Again, there's an alternative
notation (‘^’), and an in-place version with the ungainly name *note
symmetric_difference_update(): 13ef.

     >>> S1 = sets.Set([1,2,3,4])
     >>> S2 = sets.Set([3,4,5,6])
     >>> S1.symmetric_difference(S2)
     Set([1, 2, 5, 6])
     >>> S1 ^ S2
     Set([1, 2, 5, 6])
     >>>

There are also ‘issubset()’ and ‘issuperset()’ methods for checking
whether one set is a subset or superset of another:

     >>> S1 = sets.Set([1,2,3])
     >>> S2 = sets.Set([2,3])
     >>> S2.issubset(S1)
     True
     >>> S1.issubset(S2)
     False
     >>> S1.issuperset(S2)
     True
     >>>

也參考
......

PEP 218(1) - Adding a Built-In Set Object Type

     PEP written by Greg V. Wilson.  Implemented by Greg V. Wilson, Alex
     Martelli, and GvR.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0218/


File: python.info,  Node: PEP 255 Simple Generators,  Next: PEP 263 Source Code Encodings,  Prev: PEP 218 A Standard Set Datatype,  Up: Python 2 3 有什麼新功能

1.19.2 PEP 255: Simple Generators
---------------------------------

In Python 2.2, generators were added as an optional feature, to be
enabled by a ‘from __future__ import generators’ directive.  In 2.3
generators no longer need to be specially enabled, and are now always
present; this means that *note yield: 971. is now always a keyword.  The
rest of this section is a copy of the description of generators from the
"What's New in Python 2.2" document; if you read it back when Python 2.2
came out, you can skip the rest of this section.

You're doubtless familiar with how function calls work in Python or C.
When you call a function, it gets a private namespace where its local
variables are created.  When the function reaches a *note return: 972.
statement, the local variables are destroyed and the resulting value is
returned to the caller.  A later call to the same function will get a
fresh new set of local variables.  But, what if the local variables
weren't thrown away on exiting a function?  What if you could later
resume the function where it left off?  This is what generators provide;
they can be thought of as resumable functions.

Here's the simplest example of a generator function:

     def generate_ints(N):
         for i in range(N):
             yield i

A new keyword, *note yield: 971, was introduced for generators.  Any
function containing a ‘yield’ statement is a generator function; this is
detected by Python's bytecode compiler which compiles the function
specially as a result.

When you call a generator function, it doesn't return a single value;
instead it returns a generator object that supports the iterator
protocol.  On executing the *note yield: 971. statement, the generator
outputs the value of ‘i’, similar to a *note return: 972. statement.
The big difference between ‘yield’ and a ‘return’ statement is that on
reaching a ‘yield’ the generator's state of execution is suspended and
local variables are preserved.  On the next call to the generator's
‘.next()’ method, the function will resume executing immediately after
the ‘yield’ statement.  (For complicated reasons, the ‘yield’ statement
isn't allowed inside the *note try: 68c. block of a ‘try’...‘finally’
statement; read PEP 255(1) for a full explanation of the interaction
between ‘yield’ and exceptions.)

Here's a sample usage of the ‘generate_ints()’ generator:

     >>> gen = generate_ints(3)
     >>> gen
     <generator object at 0x8117f90>
     >>> gen.next()
     0
     >>> gen.next()
     1
     >>> gen.next()
     2
     >>> gen.next()
     Traceback (most recent call last):
       File "stdin", line 1, in ?
       File "stdin", line 2, in generate_ints
     StopIteration

You could equally write ‘for i in generate_ints(5)’, or ‘a,b,c =
generate_ints(3)’.

Inside a generator function, the *note return: 972. statement can only
be used without a value, and signals the end of the procession of
values; afterwards the generator cannot return any further values.
‘return’ with a value, such as ‘return 5’, is a syntax error inside a
generator function.  The end of the generator's results can also be
indicated by raising *note StopIteration: ba1. manually, or by just
letting the flow of execution fall off the bottom of the function.

You could achieve the effect of generators manually by writing your own
class and storing all the local variables of the generator as instance
variables.  For example, returning a list of integers could be done by
setting ‘self.count’ to 0, and having the *note next(): 77c. method
increment ‘self.count’ and return it.  However, for a moderately
complicated generator, writing a corresponding class would be much
messier.  ‘Lib/test/test_generators.py’ contains a number of more
interesting examples.  The simplest one implements an in-order traversal
of a tree using generators recursively.

     # A recursive generator that generates Tree leaves in in-order.
     def inorder(t):
         if t:
             for x in inorder(t.left):
                 yield x
             yield t.label
             for x in inorder(t.right):
                 yield x

Two other examples in ‘Lib/test/test_generators.py’ produce solutions
for the N-Queens problem (placing $N$ queens on an $NxN$ chess board so
that no queen threatens another) and the Knight's Tour (a route that
takes a knight to every square of an $NxN$ chessboard without visiting
any square twice).

The idea of generators comes from other programming languages,
especially Icon (‘https://www2.cs.arizona.edu/icon/’), where the idea of
generators is central.  In Icon, every expression and function call
behaves like a generator.  One example from "An Overview of the Icon
Programming Language" at
‘https://www2.cs.arizona.edu/icon/docs/ipd266.htm’ gives an idea of what
this looks like:

     sentence := "Store it in the neighboring harbor"
     if (i := find("or", sentence)) > 5 then write(i)

In Icon the ‘find()’ function returns the indexes at which the substring
"or" is found: 3, 23, 33.  In the *note if: 2c4. statement, ‘i’ is first
assigned a value of 3, but 3 is less than 5, so the comparison fails,
and Icon retries it with the second value of 23.  23 is greater than 5,
so the comparison now succeeds, and the code prints the value 23 to the
screen.

Python doesn't go nearly as far as Icon in adopting generators as a
central concept.  Generators are considered part of the core Python
language, but learning or using them isn't compulsory; if they don't
solve any problems that you have, feel free to ignore them.  One novel
feature of Python's interface as compared to Icon's is that a
generator's state is represented as a concrete object (the iterator)
that can be passed around to other functions or stored in a data
structure.

也參考
......

PEP 255(2) - Simple Generators

     Written by Neil Schemenauer, Tim Peters, Magnus Lie Hetland.
     Implemented mostly by Neil Schemenauer and Tim Peters, with other
     fixes from the Python Labs crew.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0255/

   (2) https://peps.python.org/pep-0255/


File: python.info,  Node: PEP 263 Source Code Encodings,  Next: PEP 273 Importing Modules from ZIP Archives,  Prev: PEP 255 Simple Generators,  Up: Python 2 3 有什麼新功能

1.19.3 PEP 263: Source Code Encodings
-------------------------------------

Python source files can now be declared as being in different character
set encodings.  Encodings are declared by including a specially
formatted comment in the first or second line of the source file.  For
example, a UTF-8 file can be declared with:

     #!/usr/bin/env python
     # -*- coding: UTF-8 -*-

Without such an encoding declaration, the default encoding used is 7-bit
ASCII. Executing or importing modules that contain string literals with
8-bit characters and have no encoding declaration will result in a *note
DeprecationWarning: 18b. being signalled by Python 2.3; in 2.4 this will
be a syntax error.

The encoding declaration only affects Unicode string literals, which
will be converted to Unicode using the specified encoding.  Note that
Python identifiers are still restricted to ASCII characters, so you
can't have variable names that use characters outside of the usual
alphanumerics.

也參考
......

PEP 263(1) - Defining Python Source Code Encodings

     Written by Marc-André Lemburg and Martin von Löwis; implemented by
     Suzuki Hisao and Martin von Löwis.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0263/


File: python.info,  Node: PEP 273 Importing Modules from ZIP Archives,  Next: PEP 277 Unicode file name support for Windows NT,  Prev: PEP 263 Source Code Encodings,  Up: Python 2 3 有什麼新功能

1.19.4 PEP 273: Importing Modules from ZIP Archives
---------------------------------------------------

The new *note zipimport: 118. module adds support for importing modules
from a ZIP-format archive.  You don't need to import the module
explicitly; it will be automatically imported if a ZIP archive's
filename is added to ‘sys.path’.  For example:

     amk@nyman:~/src/python$ unzip -l /tmp/example.zip
     Archive:  /tmp/example.zip
       Length     Date   Time    Name
      --------    ----   ----    ----
          8467  11-26-02 22:30   jwzthreading.py
      --------                   -------
          8467                   1 file
     amk@nyman:~/src/python$ ./python
     Python 2.3 (#1, Aug 1 2003, 19:54:32)
     >>> import sys
     >>> sys.path.insert(0, '/tmp/example.zip')  # Add .zip file to front of path
     >>> import jwzthreading
     >>> jwzthreading.__file__
     '/tmp/example.zip/jwzthreading.py'
     >>>

An entry in ‘sys.path’ can now be the filename of a ZIP archive.  The
ZIP archive can contain any kind of files, but only files named ‘*.py’,
‘*.pyc’, or ‘*.pyo’ can be imported.  If an archive only contains ‘*.py’
files, Python will not attempt to modify the archive by adding the
corresponding ‘*.pyc’ file, meaning that if a ZIP archive doesn't
contain ‘*.pyc’ files, importing may be rather slow.

A path within the archive can also be specified to only import from a
subdirectory; for example, the path ‘/tmp/example.zip/lib/’ would only
import from the ‘lib/’ subdirectory within the archive.

也參考
......

PEP 273(1) - Import Modules from Zip Archives

     Written by James C. Ahlstrom, who also provided an implementation.
     Python 2.3 follows the specification in PEP 273(2), but uses an
     implementation written by Just van Rossum that uses the import
     hooks described in PEP 302(3).  See section *note PEP 302; New
     Import Hooks: 13f5. for a description of the new import hooks.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0273/

   (2) https://peps.python.org/pep-0273/

   (3) https://peps.python.org/pep-0302/


File: python.info,  Node: PEP 277 Unicode file name support for Windows NT,  Next: PEP 278 Universal Newline Support,  Prev: PEP 273 Importing Modules from ZIP Archives,  Up: Python 2 3 有什麼新功能

1.19.5 PEP 277: Unicode file name support for Windows NT
--------------------------------------------------------

On Windows NT, 2000, and XP, the system stores file names as Unicode
strings.  Traditionally, Python has represented file names as byte
strings, which is inadequate because it renders some file names
inaccessible.

Python now allows using arbitrary Unicode strings (within the
limitations of the file system) for all functions that expect file
names, most notably the *note open(): 4c0. built-in function.  If a
Unicode string is passed to *note os.listdir(): 1092, Python now returns
a list of Unicode strings.  A new function, ‘os.getcwdu()’, returns the
current directory as a Unicode string.

Byte strings still work as file names, and on Windows Python will
transparently convert them to Unicode using the ‘mbcs’ encoding.

Other systems also allow Unicode strings as file names but convert them
to byte strings before passing them to the system, which can cause a
*note UnicodeError: 123a. to be raised.  Applications can test whether
arbitrary Unicode strings are supported as file names by checking *note
os.path.supports_unicode_filenames: 13f7, a Boolean value.

Under MacOS, *note os.listdir(): 1092. may now return Unicode filenames.

也參考
......

PEP 277(1) - Unicode file name support for Windows NT

     Written by Neil Hodgson; implemented by Neil Hodgson, Martin von
     Löwis, and Mark Hammond.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0277/


File: python.info,  Node: PEP 278 Universal Newline Support,  Next: PEP 279：enumerate,  Prev: PEP 277 Unicode file name support for Windows NT,  Up: Python 2 3 有什麼新功能

1.19.6 PEP 278: Universal Newline Support
-----------------------------------------

The three major operating systems used today are Microsoft Windows,
Apple's Macintosh OS, and the various Unix derivatives.  A minor
irritation of cross-platform work is that these three platforms all use
different characters to mark the ends of lines in text files.  Unix uses
the linefeed (ASCII character 10), MacOS uses the carriage return (ASCII
character 13), and Windows uses a two-character sequence of a carriage
return plus a newline.

Python's file objects can now support end of line conventions other than
the one followed by the platform on which Python is running.  Opening a
file with the mode ‘'U'’ or ‘'rU'’ will open a file for reading in *note
universal newlines: ce1. mode.  All three line ending conventions will
be translated to a ‘'\n'’ in the strings returned by the various file
methods such as ‘read()’ and ‘readline()’.

Universal newline support is also used when importing modules and when
executing a file with the ‘execfile()’ function.  This means that Python
modules can be shared between all three operating systems without
needing to convert the line-endings.

This feature can be disabled when compiling Python by specifying the
‘--without-universal-newlines’ switch when running Python's ‘configure’
script.

也參考
......

PEP 278(1) - Universal Newline Support

     Written and implemented by Jack Jansen.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0278/


File: python.info,  Node: PEP 279：enumerate,  Next: PEP 282 The logging Package,  Prev: PEP 278 Universal Newline Support,  Up: Python 2 3 有什麼新功能

1.19.7 PEP 279：enumerate()
---------------------------

A new built-in function, *note enumerate(): 13ea, will make certain
loops a bit clearer.  ‘enumerate(thing)’, where 'thing' is either an
iterator or a sequence, returns an iterator that will return ‘(0,
thing[0])’, ‘(1, thing[1])’, ‘(2, thing[2])’, and so forth.

A common idiom to change every element of a list looks like this:

     for i in range(len(L)):
         item = L[i]
         # ... compute some result based on item ...
         L[i] = result

This can be rewritten using *note enumerate(): 13ea. as:

     for i, item in enumerate(L):
         # ... compute some result based on item ...
         L[i] = result

也參考
......

PEP 279(1) - The enumerate() built-in function

     Written and implemented by Raymond D. Hettinger.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0279/


File: python.info,  Node: PEP 282 The logging Package,  Next: PEP 285 A Boolean Type,  Prev: PEP 279：enumerate,  Up: Python 2 3 有什麼新功能

1.19.8 PEP 282: The logging Package
-----------------------------------

A standard package for writing logs, *note logging: 7b, has been added
to Python 2.3.  It provides a powerful and flexible mechanism for
generating logging output which can then be filtered and processed in
various ways.  A configuration file written in a standard format can be
used to control the logging behavior of a program.  Python includes
handlers that will write log records to standard error or to a file or
socket, send them to the system log, or even e-mail them to a particular
address; of course, it's also possible to write your own handler
classes.

The *note Logger: af3. class is the primary class.  Most application
code will deal with one or more *note Logger: af3. objects, each one
used by a particular subsystem of the application.  Each *note Logger:
af3. is identified by a name, and names are organized into a hierarchy
using ‘.’ as the component separator.  For example, you might have *note
Logger: af3. instances named ‘server’, ‘server.auth’ and
‘server.network’.  The latter two instances are below ‘server’ in the
hierarchy.  This means that if you turn up the verbosity for ‘server’ or
direct ‘server’ messages to a different handler, the changes will also
apply to records logged to ‘server.auth’ and ‘server.network’.  There's
also a root *note Logger: af3. that's the parent of all other loggers.

For simple uses, the *note logging: 7b. package contains some
convenience functions that always use the root log:

     import logging

     logging.debug('Debugging information')
     logging.info('Informational message')
     logging.warning('Warning:config file %s not found', 'server.conf')
     logging.error('Error occurred')
     logging.critical('Critical error -- shutting down')

This produces the following output:

     WARNING:root:Warning:config file server.conf not found
     ERROR:root:Error occurred
     CRITICAL:root:Critical error -- shutting down

In the default configuration, informational and debugging messages are
suppressed and the output is sent to standard error.  You can enable the
display of informational and debugging messages by calling the *note
setLevel(): 13fc. method on the root logger.

Notice the *note warning(): 2d0. call's use of string formatting
operators; all of the functions for logging messages take the arguments
‘(msg, arg1, arg2, ...)’ and log the string resulting from ‘msg % (arg1,
arg2, ...)’.

There's also an *note exception(): 13fd. function that records the most
recent traceback.  Any of the other functions will also record the
traceback if you specify a true value for the keyword argument
'exc_info'.

     def f():
         try:    1/0
         except: logging.exception('Problem recorded')

     f()

This produces the following output:

     ERROR:root:Problem recorded
     Traceback (most recent call last):
       File "t.py", line 6, in f
         1/0
     ZeroDivisionError: integer division or modulo by zero

Slightly more advanced programs will use a logger other than the root
logger.  The ‘getLogger(name)’ function is used to get a particular log,
creating it if it doesn't exist yet.  ‘getLogger(None)’ returns the root
logger.

     log = logging.getLogger('server')
      ...
     log.info('Listening on port %i', port)
      ...
     log.critical('Disk full')
      ...

Log records are usually propagated up the hierarchy, so a message logged
to ‘server.auth’ is also seen by ‘server’ and ‘root’, but a *note
Logger: af3. can prevent this by setting its *note propagate: 13fe.
attribute to *note False: adb.

There are more classes provided by the *note logging: 7b. package that
can be customized.  When a *note Logger: af3. instance is told to log a
message, it creates a *note LogRecord: f89. instance that is sent to any
number of different *note Handler: 13ff. instances.  Loggers and
handlers can also have an attached list of filters, and each filter can
cause the *note LogRecord: f89. to be ignored or can modify the record
before passing it along.  When they're finally output, *note LogRecord:
f89. instances are converted to text by a *note Formatter: 1400. class.
All of these classes can be replaced by your own specially written
classes.

With all of these features the *note logging: 7b. package should provide
enough flexibility for even the most complicated applications.  This is
only an incomplete overview of its features, so please see the package's
reference documentation for all of the details.  Reading PEP 282(1) will
also be helpful.

也參考
......

PEP 282(2) - A Logging System

     Written by Vinay Sajip and Trent Mick; implemented by Vinay Sajip.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0282/

   (2) https://peps.python.org/pep-0282/


File: python.info,  Node: PEP 285 A Boolean Type,  Next: PEP 293 Codec Error Handling Callbacks,  Prev: PEP 282 The logging Package,  Up: Python 2 3 有什麼新功能

1.19.9 PEP 285: A Boolean Type
------------------------------

A Boolean type was added to Python 2.3.  Two new constants were added to
the ‘__builtin__’ module, *note True: bb4. and *note False: adb.  (*note
True: bb4. and *note False: adb. constants were added to the built-ins
in Python 2.2.1, but the 2.2.1 versions are simply set to integer values
of 1 and 0 and aren't a different type.)

The type object for this new type is named *note bool: 40e.; the
constructor for it takes any Python value and converts it to *note True:
bb4. or *note False: adb.

     >>> bool(1)
     True
     >>> bool(0)
     False
     >>> bool([])
     False
     >>> bool( (1,) )
     True

Most of the standard library modules and built-in functions have been
changed to return Booleans.

     >>> obj = []
     >>> hasattr(obj, 'append')
     True
     >>> isinstance(obj, list)
     True
     >>> isinstance(obj, tuple)
     False

Python's Booleans were added with the primary goal of making code
clearer.  For example, if you're reading a function and encounter the
statement ‘return 1’, you might wonder whether the ‘1’ represents a
Boolean truth value, an index, or a coefficient that multiplies some
other quantity.  If the statement is ‘return True’, however, the meaning
of the return value is quite clear.

Python's Booleans were 'not' added for the sake of strict type-checking.
A very strict language such as Pascal would also prevent you performing
arithmetic with Booleans, and would require that the expression in an
*note if: 2c4. statement always evaluate to a Boolean result.  Python is
not this strict and never will be, as PEP 285(1) explicitly says.  This
means you can still use any expression in an ‘if’ statement, even ones
that evaluate to a list or tuple or some random object.  The Boolean
type is a subclass of the *note int: 23c. class so that arithmetic using
a Boolean still works.

     >>> True + 1
     2
     >>> False + 1
     1
     >>> False * 75
     0
     >>> True * 75
     75

To sum up *note True: bb4. and *note False: adb. in a sentence: they're
alternative ways to spell the integer values 1 and 0, with the single
difference that *note str(): 3f2. and *note repr(): 7a1. return the
strings ‘'True'’ and ‘'False'’ instead of ‘'1'’ and ‘'0'’.

也參考
......

PEP 285(2) - Adding a bool type

     Written and implemented by GvR.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0285/

   (2) https://peps.python.org/pep-0285/


File: python.info,  Node: PEP 293 Codec Error Handling Callbacks,  Next: PEP 301 Package Index and Metadata for Distutils,  Prev: PEP 285 A Boolean Type,  Up: Python 2 3 有什麼新功能

1.19.10 PEP 293: Codec Error Handling Callbacks
-----------------------------------------------

When encoding a Unicode string into a byte string, unencodable
characters may be encountered.  So far, Python has allowed specifying
the error processing as either "strict" (raising *note UnicodeError:
123a.), "ignore" (skipping the character), or "replace" (using a
question mark in the output string), with "strict" being the default
behavior.  It may be desirable to specify alternative processing of such
errors, such as inserting an XML character reference or HTML entity
reference into the converted string.

Python now has a flexible framework to add different processing
strategies.  New error handlers can be added with *note
codecs.register_error(): 1404, and codecs then can access the error
handler with *note codecs.lookup_error(): 1405.  An equivalent C API has
been added for codecs written in C. The error handler gets the necessary
state information such as the string being converted, the position in
the string where the error was detected, and the target encoding.  The
handler can then either raise an exception or return a replacement
string.

Two additional error handlers have been implemented using this
framework: "backslashreplace" uses Python backslash quoting to represent
unencodable characters and "xmlcharrefreplace" emits XML character
references.

也參考
......

PEP 293(1) - Codec Error Handling Callbacks

     Written and implemented by Walter Dörwald.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0293/


File: python.info,  Node: PEP 301 Package Index and Metadata for Distutils,  Next: PEP 302 New Import Hooks,  Prev: PEP 293 Codec Error Handling Callbacks,  Up: Python 2 3 有什麼新功能

1.19.11 PEP 301: Package Index and Metadata for Distutils
---------------------------------------------------------

Support for the long-requested Python catalog makes its first appearance
in 2.3.

The heart of the catalog is the new Distutils ‘register’ command.
Running ‘python setup.py register’ will collect the metadata describing
a package, such as its name, version, maintainer, description, &c., and
send it to a central catalog server.  The resulting catalog is available
from ‘https://pypi.org’.

To make the catalog a bit more useful, a new optional 'classifiers'
keyword argument has been added to the Distutils ‘setup()’ function.  A
list of Trove(1)-style strings can be supplied to help classify the
software.

Here's an example ‘setup.py’ with classifiers, written to be compatible
with older versions of the Distutils:

     from distutils import core
     kw = {'name': "Quixote",
           'version': "0.5.1",
           'description': "A highly Pythonic Web application framework",
           # ...
           }

     if (hasattr(core, 'setup_keywords') and
         'classifiers' in core.setup_keywords):
         kw['classifiers'] = \
             ['Topic :: Internet :: WWW/HTTP :: Dynamic Content',
              'Environment :: No Input/Output (Daemon)',
              'Intended Audience :: Developers'],

     core.setup(**kw)

The full list of classifiers can be obtained by running ‘python setup.py
register --list-classifiers’.

也參考
......

PEP 301(2) - Package Index and Metadata for Distutils

     Written and implemented by Richard Jones.

   ---------- Footnotes ----------

   (1) http://catb.org/~esr/trove/

   (2) https://peps.python.org/pep-0301/


File: python.info,  Node: PEP 302 New Import Hooks,  Next: PEP 305 Comma-separated Files,  Prev: PEP 301 Package Index and Metadata for Distutils,  Up: Python 2 3 有什麼新功能

1.19.12 PEP 302: New Import Hooks
---------------------------------

While it's been possible to write custom import hooks ever since the
‘ihooks’ module was introduced in Python 1.3, no one has ever been
really happy with it because writing new import hooks is difficult and
messy.  There have been various proposed alternatives such as the
‘imputil’ and ‘iu’ modules, but none of them has ever gained much
acceptance, and none of them were easily usable from C code.

PEP 302(1) borrows ideas from its predecessors, especially from Gordon
McMillan's ‘iu’ module.  Three new items are added to the *note sys: c3.
module:

   * ‘sys.path_hooks’ is a list of callable objects; most often they'll
     be classes.  Each callable takes a string containing a path and
     either returns an importer object that will handle imports from
     this path or raises an *note ImportError: 352. exception if it
     can't handle this path.

   * ‘sys.path_importer_cache’ caches importer objects for each path, so
     ‘sys.path_hooks’ will only need to be traversed once for each path.

   * ‘sys.meta_path’ is a list of importer objects that will be
     traversed before ‘sys.path’ is checked.  This list is initially
     empty, but user code can add objects to it.  Additional built-in
     and frozen modules can be imported by an object added to this list.

Importer objects must have a single method, ‘find_module(fullname,
path=None)’.  'fullname' will be a module or package name, e.g.
‘string’ or ‘distutils.core’.  ‘find_module()’ must return a loader
object that has a single method, ‘load_module(fullname)’, that creates
and returns the corresponding module object.

Pseudo-code for Python's new import logic, therefore, looks something
like this (simplified a bit; see PEP 302(2) for the full details):

     for mp in sys.meta_path:
         loader = mp(fullname)
         if loader is not None:
             <module> = loader.load_module(fullname)

     for path in sys.path:
         for hook in sys.path_hooks:
             try:
                 importer = hook(path)
             except ImportError:
                 # ImportError, so try the other path hooks
                 pass
             else:
                 loader = importer.find_module(fullname)
                 <module> = loader.load_module(fullname)

     # Not found!
     raise ImportError

也參考
......

PEP 302(3) - New Import Hooks

     Written by Just van Rossum and Paul Moore.  Implemented by Just van
     Rossum.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0302/

   (2) https://peps.python.org/pep-0302/

   (3) https://peps.python.org/pep-0302/


File: python.info,  Node: PEP 305 Comma-separated Files,  Next: PEP 307 Pickle Enhancements,  Prev: PEP 302 New Import Hooks,  Up: Python 2 3 有什麼新功能

1.19.13 PEP 305: Comma-separated Files
--------------------------------------

Comma-separated files are a format frequently used for exporting data
from databases and spreadsheets.  Python 2.3 adds a parser for
comma-separated files.

Comma-separated format is deceptively simple at first glance:

     Costs,150,200,3.95

Read a line and call ‘line.split(',')’: what could be simpler?  But toss
in string data that can contain commas, and things get more complicated:

     "Costs",150,200,3.95,"Includes taxes, shipping, and sundry items"

A big ugly regular expression can parse this, but using the new *note
csv: 21. package is much simpler:

     import csv

     input = open('datafile', 'rb')
     reader = csv.reader(input)
     for line in reader:
         print line

The *note reader(): 42d. function takes a number of different options.
The field separator isn't limited to the comma and can be changed to any
character, and so can the quoting and line-ending characters.

Different dialects of comma-separated files can be defined and
registered; currently there are two dialects, both used by Microsoft
Excel.  A separate *note csv.writer: 42e. class will generate
comma-separated files from a succession of tuples or lists, quoting
strings that contain the delimiter.

也參考
......

PEP 305(1) - CSV 檔案 API

     Written and implemented by Kevin Altis, Dave Cole, Andrew McNamara,
     Skip Montanaro, Cliff Wells.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0305/


File: python.info,  Node: PEP 307 Pickle Enhancements,  Next: Extended Slices,  Prev: PEP 305 Comma-separated Files,  Up: Python 2 3 有什麼新功能

1.19.14 PEP 307: Pickle Enhancements
------------------------------------

The *note pickle: 95. and ‘cPickle’ modules received some attention
during the 2.3 development cycle.  In 2.2, new-style classes could be
pickled without difficulty, but they weren't pickled very compactly; PEP
307(1) quotes a trivial example where a new-style class results in a
pickled string three times longer than that for a classic class.

The solution was to invent a new pickle protocol.  The *note
pickle.dumps(): 140d. function has supported a text-or-binary flag for a
long time.  In 2.3, this flag is redefined from a Boolean to an integer:
0 is the old text-mode pickle format, 1 is the old binary format, and
now 2 is a new 2.3-specific format.  A new constant, *note
pickle.HIGHEST_PROTOCOL: 140e, can be used to select the fanciest
protocol available.

Unpickling is no longer considered a safe operation.  2.2's *note
pickle: 95. provided hooks for trying to prevent unsafe classes from
being unpickled (specifically, a ‘__safe_for_unpickling__’ attribute),
but none of this code was ever audited and therefore it's all been
ripped out in 2.3.  You should not unpickle untrusted data in any
version of Python.

To reduce the pickling overhead for new-style classes, a new interface
for customizing pickling was added using three special methods: *note
__getstate__(): 57c, *note __setstate__(): 140f, and *note
__getnewargs__(): 1410.  Consult PEP 307(2) for the full semantics of
these methods.

As a way to compress pickles yet further, it's now possible to use
integer codes instead of long strings to identify pickled classes.  The
Python Software Foundation will maintain a list of standardized codes;
there's also a range of codes for private use.  Currently no codes have
been specified.

也參考
......

PEP 307(3) - Extensions to the pickle protocol

     Written and implemented by Guido van Rossum and Tim Peters.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0307/

   (2) https://peps.python.org/pep-0307/

   (3) https://peps.python.org/pep-0307/


File: python.info,  Node: Extended Slices,  Next: 其他語言更動<17>,  Prev: PEP 307 Pickle Enhancements,  Up: Python 2 3 有什麼新功能

1.19.15 Extended Slices
-----------------------

Ever since Python 1.4, the slicing syntax has supported an optional
third "step" or "stride" argument.  For example, these are all legal
Python syntax: ‘L[1:10:2]’, ‘L[:-1:1]’, ‘L[::-1]’.  This was added to
Python at the request of the developers of Numerical Python, which uses
the third argument extensively.  However, Python's built-in list, tuple,
and string sequence types have never supported this feature, raising a
*note TypeError: 4dd. if you tried it.  Michael Hudson contributed a
patch to fix this shortcoming.

For example, you can now easily extract the elements of a list that have
even indexes:

     >>> L = range(10)
     >>> L[::2]
     [0, 2, 4, 6, 8]

Negative values also work to make a copy of the same list in reverse
order:

     >>> L[::-1]
     [9, 8, 7, 6, 5, 4, 3, 2, 1, 0]

This also works for tuples, arrays, and strings:

     >>> s='abcd'
     >>> s[::2]
     'ac'
     >>> s[::-1]
     'dcba'

If you have a mutable sequence such as a list or an array you can assign
to or delete an extended slice, but there are some differences between
assignment to extended and regular slices.  Assignment to a regular
slice can be used to change the length of the sequence:

     >>> a = range(3)
     >>> a
     [0, 1, 2]
     >>> a[1:3] = [4, 5, 6]
     >>> a
     [0, 4, 5, 6]

Extended slices aren't this flexible.  When assigning to an extended
slice, the list on the right hand side of the statement must contain the
same number of items as the slice it is replacing:

     >>> a = range(4)
     >>> a
     [0, 1, 2, 3]
     >>> a[::2]
     [0, 2]
     >>> a[::2] = [0, -1]
     >>> a
     [0, 1, -1, 3]
     >>> a[::2] = [0,1,2]
     Traceback (most recent call last):
       File "<stdin>", line 1, in ?
     ValueError: attempt to assign sequence of size 3 to extended slice of size 2

Deletion is more straightforward:

     >>> a = range(4)
     >>> a
     [0, 1, 2, 3]
     >>> a[::2]
     [0, 2]
     >>> del a[::2]
     >>> a
     [1, 3]

One can also now pass slice objects to the *note __getitem__(): 266.
methods of the built-in sequences:

     >>> range(10).__getitem__(slice(0, 5, 2))
     [0, 2, 4]

Or use slice objects directly in subscripts:

     >>> range(10)[slice(0, 5, 2)]
     [0, 2, 4]

To simplify implementing sequences that support extended slicing, slice
objects now have a method ‘indices(length)’ which, given the length of a
sequence, returns a ‘(start, stop, step)’ tuple that can be passed
directly to *note range(): 8e7.  ‘indices()’ handles omitted and
out-of-bounds indices in a manner consistent with regular slices (and
this innocuous phrase hides a welter of confusing details!).  The method
is intended to be used like this:

     class FakeSeq:
         ...
         def calc_item(self, i):
             ...
         def __getitem__(self, item):
             if isinstance(item, slice):
                 indices = item.indices(len(self))
                 return FakeSeq([self.calc_item(i) for i in range(*indices)])
             else:
                 return self.calc_item(i)

From this example you can also see that the built-in *note slice: 410.
object is now the type object for the slice type, and is no longer a
function.  This is consistent with Python 2.2, where *note int: 23c,
*note str: 3f2, etc., underwent the same change.


File: python.info,  Node: 其他語言更動<17>,  Next: New Improved and Deprecated Modules<4>,  Prev: Extended Slices,  Up: Python 2 3 有什麼新功能

1.19.16 其他語言更動
--------------------

Here are all of the changes that Python 2.3 makes to the core Python
language.

   * The *note yield: 971. statement is now always a keyword, as
     described in section *note PEP 255; Simple Generators: 13f1. of
     this document.

   * A new built-in function *note enumerate(): 13ea. was added, as
     described in section *note PEP 279：enumerate(): 13fa. of this
     document.

   * Two new constants, *note True: bb4. and *note False: adb. were
     added along with the built-in *note bool: 40e. type, as described
     in section *note PEP 285; A Boolean Type: 1402. of this document.

   * The *note int(): 23c. type constructor will now return a long
     integer instead of raising an *note OverflowError: 825. when a
     string or floating-point number is too large to fit into an
     integer.  This can lead to the paradoxical result that
     ‘isinstance(int(expression), int)’ is false, but that seems
     unlikely to cause problems in practice.

   * Built-in types now support the extended slicing syntax, as
     described in section *note Extended Slices: 1412. of this document.

   * A new built-in function, ‘sum(iterable, start=0)’, adds up the
     numeric items in the iterable object and returns their sum.  *note
     sum(): 411. only accepts numbers, meaning that you can't use it to
     concatenate a bunch of strings.  (Contributed by Alex Martelli.)

   * ‘list.insert(pos, value)’ used to insert 'value' at the front of
     the list when 'pos' was negative.  The behaviour has now been
     changed to be consistent with slice indexing, so when 'pos' is -1
     the value will be inserted before the last element, and so forth.

   * ‘list.index(value)’, which searches for 'value' within the list and
     returns its index, now takes optional 'start' and 'stop' arguments
     to limit the search to only part of the list.

   * Dictionaries have a new method, ‘pop(key[, *default*])’, that
     returns the value corresponding to 'key' and removes that key/value
     pair from the dictionary.  If the requested key isn't present in
     the dictionary, 'default' is returned if it's specified and *note
     KeyError: 2fb. raised if it isn't.

          >>> d = {1:2}
          >>> d
          {1: 2}
          >>> d.pop(4)
          Traceback (most recent call last):
            File "stdin", line 1, in ?
          KeyError: 4
          >>> d.pop(1)
          2
          >>> d.pop(1)
          Traceback (most recent call last):
            File "stdin", line 1, in ?
          KeyError: 'pop(): dictionary is empty'
          >>> d
          {}
          >>>

     There's also a new class method, ‘dict.fromkeys(iterable, value)’,
     that creates a dictionary with keys taken from the supplied
     iterator 'iterable' and all values set to 'value', defaulting to
     ‘None’.

     (Patches contributed by Raymond Hettinger.)

     Also, the *note dict(): 23b. constructor now accepts keyword
     arguments to simplify creating small dictionaries:

          >>> dict(red=1, blue=2, green=3, black=4)
          {'blue': 2, 'black': 4, 'green': 3, 'red': 1}

     （由 Just van Rossum 所貢獻。）

   * The *note assert: 90c. statement no longer checks the ‘__debug__’
     flag, so you can no longer disable assertions by assigning to
     ‘__debug__’.  Running Python with the *note -O: d5b. switch will
     still generate code that doesn't execute any assertions.

   * Most type objects are now callable, so you can use them to create
     new objects such as functions, classes, and modules.  (This means
     that the ‘new’ module can be deprecated in a future Python version,
     because you can now use the type objects available in the *note
     types: ec. module.)  For example, you can create a new module
     object with the following code:

          >>> import types
          >>> m = types.ModuleType('abc','docstring')
          >>> m
          <module 'abc' (built-in)>
          >>> m.__doc__
          'docstring'

   * A new warning, *note PendingDeprecationWarning: 86d. was added to
     indicate features which are in the process of being deprecated.
     The warning will 'not' be printed by default.  To check for use of
     features that will be deprecated in the future, supply *note
     -Walways;;PendingDeprecationWarning;;: 86c. on the command line or
     use *note warnings.filterwarnings(): 1414.

   * The process of deprecating string-based exceptions, as in ‘raise
     "Error occurred"’, has begun.  Raising a string will now trigger
     *note PendingDeprecationWarning: 86d.

   * Using ‘None’ as a variable name will now result in a *note
     SyntaxWarning: 40c. warning.  In a future version of Python, ‘None’
     may finally become a keyword.

   * The ‘xreadlines()’ method of file objects, introduced in Python
     2.1, is no longer necessary because files now behave as their own
     iterator.  ‘xreadlines()’ was originally introduced as a faster way
     to loop over all the lines in a file, but now you can simply write
     ‘for line in file_obj’.  File objects also have a new read-only
     ‘encoding’ attribute that gives the encoding used by the file;
     Unicode strings written to the file will be automatically converted
     to bytes using the given encoding.

   * The method resolution order used by new-style classes has changed,
     though you'll only notice the difference if you have a really
     complicated inheritance hierarchy.  Classic classes are unaffected
     by this change.  Python 2.2 originally used a topological sort of a
     class's ancestors, but 2.3 now uses the C3 algorithm as described
     in the paper "A Monotonic Superclass Linearization for Dylan"(1).
     To understand the motivation for this change, read Michele
     Simionato's article *note The Python 2.3 Method Resolution Order:
     1415, or read the thread on python-dev starting with the message at
     ‘https://mail.python.org/pipermail/python-dev/2002-October/029035.html’.
     Samuele Pedroni first pointed out the problem and also implemented
     the fix by coding the C3 algorithm.

   * Python runs multithreaded programs by switching between threads
     after executing N bytecodes.  The default value for N has been
     increased from 10 to 100 bytecodes, speeding up single-threaded
     applications by reducing the switching overhead.  Some
     multithreaded applications may suffer slower response time, but
     that's easily fixed by setting the limit back to a lower number
     using ‘sys.setcheckinterval(N)’.  The limit can be retrieved with
     the new ‘sys.getcheckinterval()’ function.

   * One minor but far-reaching change is that the names of extension
     types defined by the modules included with Python now contain the
     module and a ‘'.'’ in front of the type name.  For example, in
     Python 2.2, if you created a socket and printed its ‘__class__’,
     you'd get this output:

          >>> s = socket.socket()
          >>> s.__class__
          <type 'socket'>

     In 2.3, you get this:

          >>> s.__class__
          <type '_socket.socket'>

   * One of the noted incompatibilities between old- and new-style
     classes has been removed: you can now assign to the *note __name__:
     1416. and *note __bases__: 1417. attributes of new-style classes.
     There are some restrictions on what can be assigned to *note
     __bases__: 1417. along the lines of those relating to assigning to
     an instance's *note __class__: 1418. attribute.

* Menu:

* String Changes::
* 最佳化: 最佳化<16>.

   ---------- Footnotes ----------

   (1) https://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.19.3910


File: python.info,  Node: String Changes,  Next: 最佳化<16>,  Up: 其他語言更動<17>

1.19.16.1 String Changes
........................

   * The *note in: 2c5. operator now works differently for strings.
     Previously, when evaluating ‘X in Y’ where 'X' and 'Y' are strings,
     'X' could only be a single character.  That's now changed; 'X' can
     be a string of any length, and ‘X in Y’ will return *note True:
     bb4. if 'X' is a substring of 'Y'. If 'X' is the empty string, the
     result is always *note True: bb4.

          >>> 'ab' in 'abcd'
          True
          >>> 'ad' in 'abcd'
          False
          >>> '' in 'abcd'
          True

     Note that this doesn't tell you where the substring starts; if you
     need that information, use the *note find(): e4a. string method.

   * The *note strip(): 141a, *note lstrip(): 141b, and *note rstrip():
     141c. string methods now have an optional argument for specifying
     the characters to strip.  The default is still to remove all
     whitespace characters:

          >>> '   abc '.strip()
          'abc'
          >>> '><><abc<><><>'.strip('<>')
          'abc'
          >>> '><><abc<><><>\n'.strip('<>')
          'abc<><><>\n'
          >>> u'\u4000\u4001abc\u4000'.strip(u'\u4000')
          u'\u4001abc'
          >>>

     (Suggested by Simon Brunning and implemented by Walter Dörwald.)

   * The *note startswith(): e6d. and *note endswith(): e6e. string
     methods now accept negative numbers for the 'start' and 'end'
     parameters.

   * Another new string method is *note zfill(): 141d, originally a
     function in the *note string: be. module.  *note zfill(): 141d.
     pads a numeric string with zeros on the left until it's the
     specified width.  Note that the ‘%’ operator is still more flexible
     and powerful than *note zfill(): 141d.

          >>> '45'.zfill(4)
          '0045'
          >>> '12345'.zfill(4)
          '12345'
          >>> 'goofy'.zfill(6)
          '0goofy'

     （由 Walter Dörwald 所貢獻。）

   * A new type object, ‘basestring’, has been added.  Both 8-bit
     strings and Unicode strings inherit from this type, so
     ‘isinstance(obj, basestring)’ will return *note True: bb4. for
     either kind of string.  It's a completely abstract type, so you
     can't create ‘basestring’ instances.

   * Interned strings are no longer immortal and will now be
     garbage-collected in the usual way when the only reference to them
     is from the internal dictionary of interned strings.  (Implemented
     by Oren Tirosh.)


File: python.info,  Node: 最佳化<16>,  Prev: String Changes,  Up: 其他語言更動<17>

1.19.16.2 最佳化
................

   * The creation of new-style class instances has been made much
     faster; they're now faster than classic classes!

   * The *note sort(): b76. method of list objects has been extensively
     rewritten by Tim Peters, and the implementation is significantly
     faster.

   * Multiplication of large long integers is now much faster thanks to
     an implementation of Karatsuba multiplication, an algorithm that
     scales better than the 'O'('n'^2) required for the grade-school
     multiplication algorithm.  (Original patch by Christopher A. Craig,
     and significantly reworked by Tim Peters.)

   * The ‘SET_LINENO’ opcode is now gone.  This may provide a small
     speed increase, depending on your compiler's idiosyncrasies.  See
     section *note Other Changes and Fixes: 141f. for a longer
     explanation.  (Removed by Michael Hudson.)

   * ‘xrange()’ objects now have their own iterator, making ‘for i in
     xrange(n)’ slightly faster than ‘for i in range(n)’.  (Patch by
     Raymond Hettinger.)

   * A number of small rearrangements have been made in various hotspots
     to improve performance, such as inlining a function or removing
     some code.  (Implemented mostly by GvR, but lots of people have
     contributed single changes.)

The net result of the 2.3 optimizations is that Python 2.3 runs the
pystone benchmark around 25% faster than Python 2.2.


File: python.info,  Node: New Improved and Deprecated Modules<4>,  Next: Pymalloc A Specialized Object Allocator,  Prev: 其他語言更動<17>,  Up: Python 2 3 有什麼新功能

1.19.17 New, Improved, and Deprecated Modules
---------------------------------------------

As usual, Python's standard library received a number of enhancements
and bug fixes.  Here's a partial list of the most notable changes,
sorted alphabetically by module name.  Consult the ‘Misc/NEWS’ file in
the source tree for a more complete list of changes, or look through the
CVS logs for all the details.

   * The *note array: 6. module now supports arrays of Unicode
     characters using the ‘'u'’ format character.  Arrays also now
     support using the ‘+=’ assignment operator to add another array's
     contents, and the ‘*=’ assignment operator to repeat an array.
     (Contributed by Jason Orendorff.)

   * The ‘bsddb’ module has been replaced by version 4.1.6 of the
     PyBSDDB(1) package, providing a more complete interface to the
     transactional features of the BerkeleyDB library.

     The old version of the module has been renamed to ‘bsddb185’ and is
     no longer built automatically; you'll have to edit ‘Modules/Setup’
     to enable it.  Note that the new ‘bsddb’ package is intended to be
     compatible with the old module, so be sure to file bugs if you
     discover any incompatibilities.  When upgrading to Python 2.3, if
     the new interpreter is compiled with a new version of the
     underlying BerkeleyDB library, you will almost certainly have to
     convert your database files to the new version.  You can do this
     fairly easily with the new scripts ‘db2pickle.py’ and
     ‘pickle2db.py’ which you will find in the distribution's
     ‘Tools/scripts’ directory.  If you've already been using the
     PyBSDDB package and importing it as ‘bsddb3’, you will have to
     change your ‘import’ statements to import it as ‘bsddb’.

   * The new *note bz2: f. module is an interface to the bz2 data
     compression library.  bz2-compressed data is usually smaller than
     corresponding *note zlib: 119.-compressed data.  (Contributed by
     Gustavo Niemeyer.)

   * A set of standard date/time types has been added in the new *note
     datetime: 28. module.  See the following section for more details.

   * The Distutils ‘Extension’ class now supports an extra constructor
     argument named 'depends' for listing additional source files that
     an extension depends on.  This lets Distutils recompile the module
     if any of the dependency files are modified.  For example, if
     ‘sampmodule.c’ includes the header file ‘sample.h’, you would
     create the ‘Extension’ object like this:

          ext = Extension("samp",
                          sources=["sampmodule.c"],
                          depends=["sample.h"])

     Modifying ‘sample.h’ would then cause the module to be recompiled.
     (Contributed by Jeremy Hylton.)

   * Other minor changes to Distutils: it now checks for the *note CC:
     1421, *note CFLAGS: 1422, ‘CPP’, *note LDFLAGS: 1423, and *note
     CPPFLAGS: 1424. environment variables, using them to override the
     settings in Python's configuration (contributed by Robert Weber).

   * Previously the *note doctest: 31. module would only search the
     docstrings of public methods and functions for test cases, but it
     now also examines private ones as well.  The *note DocTestSuite():
     d99. function creates a *note unittest.TestSuite: d9a. object from
     a set of *note doctest: 31. tests.

   * The new ‘gc.get_referents(object)’ function returns a list of all
     the objects referenced by 'object'.

   * The *note getopt: 57. module gained a new function, *note
     gnu_getopt(): 1425, that supports the same arguments as the
     existing *note getopt(): 1426. function but uses GNU-style scanning
     mode.  The existing *note getopt(): 1426. stops processing options
     as soon as a non-option argument is encountered, but in GNU-style
     mode processing continues, meaning that options and arguments can
     be mixed.  For example:

          >>> getopt.getopt(['-f', 'filename', 'output', '-v'], 'f:v')
          ([('-f', 'filename')], ['output', '-v'])
          >>> getopt.gnu_getopt(['-f', 'filename', 'output', '-v'], 'f:v')
          ([('-f', 'filename'), ('-v', '')], ['output'])

     （由 Peter Åstrand 所貢獻。）

   * The *note grp: 5c, *note pwd: a0, and *note resource: aa. modules
     now return enhanced tuples:

          >>> import grp
          >>> g = grp.getgrnam('amk')
          >>> g.gr_name, g.gr_gid
          ('amk', 500)

   * The *note gzip: 5d. module can now handle files exceeding 2 GiB.

   * The new *note heapq: 5f. module contains an implementation of a
     heap queue algorithm.  A heap is an array-like data structure that
     keeps items in a partially sorted order such that, for every index
     'k', ‘heap[k] <= heap[2*k+1]’ and ‘heap[k] <= heap[2*k+2]’.  This
     makes it quick to remove the smallest item, and inserting a new
     item while maintaining the heap property is 'O'(log 'n').  (See
     ‘https://xlinux.nist.gov/dads//HTML/priorityque.html’ for more
     information about the priority queue data structure.)

     The *note heapq: 5f. module provides *note heappush(): 1427. and
     *note heappop(): 1428. functions for adding and removing items
     while maintaining the heap property on top of some other mutable
     Python sequence type.  Here's an example that uses a Python list:

          >>> import heapq
          >>> heap = []
          >>> for item in [3, 7, 5, 11, 1]:
          ...    heapq.heappush(heap, item)
          ...
          >>> heap
          [1, 3, 5, 11, 7]
          >>> heapq.heappop(heap)
          1
          >>> heapq.heappop(heap)
          3
          >>> heap
          [5, 7, 11]

     （由 Kevin O'Connor 所貢獻。）

   * The IDLE integrated development environment has been updated using
     the code from the IDLEfork project
     (‘https://idlefork.sourceforge.net’).  The most notable feature is
     that the code being developed is now executed in a subprocess,
     meaning that there's no longer any need for manual ‘reload()’
     operations.  IDLE's core code has been incorporated into the
     standard library as the *note idlelib: 69. package.

   * The *note imaplib: 6a. module now supports IMAP over SSL.
     (Contributed by Piers Lauder and Tino Lange.)

   * The *note itertools: 75. contains a number of useful functions for
     use with iterators, inspired by various functions provided by the
     ML and Haskell languages.  For example,
     ‘itertools.ifilter(predicate, iterator)’ returns all elements in
     the iterator for which the function ‘predicate()’ returns *note
     True: bb4, and ‘itertools.repeat(obj, N)’ returns ‘obj’ 'N' times.
     There are a number of other functions in the module; see the
     package's reference documentation for details.  (Contributed by
     Raymond Hettinger.)

   * Two new functions in the *note math: 81. module, ‘degrees(rads)’
     and ‘radians(degs)’, convert between radians and degrees.  Other
     functions in the *note math: 81. module such as *note math.sin():
     1429. and *note math.cos(): 142a. have always required input values
     measured in radians.  Also, an optional 'base' argument was added
     to *note math.log(): 142b. to make it easier to compute logarithms
     for bases other than ‘e’ and ‘10’.  (Contributed by Raymond
     Hettinger.)

   * Several new POSIX functions (‘getpgid()’, ‘killpg()’, ‘lchown()’,
     ‘loadavg()’, ‘major()’, ‘makedev()’, ‘minor()’, and ‘mknod()’) were
     added to the *note posix: 9b. module that underlies the *note os:
     91. module.  (Contributed by Gustavo Niemeyer, Geert Jansen, and
     Denis S. Otkidach.)

   * In the *note os: 91. module, the ‘*stat()’ family of functions can
     now report fractions of a second in a timestamp.  Such time stamps
     are represented as floats, similar to the value returned by *note
     time.time(): 239.

     During testing, it was found that some applications will break if
     time stamps are floats.  For compatibility, when using the tuple
     interface of the *note stat_result: 142c. time stamps will be
     represented as integers.  When using named fields (a feature first
     introduced in Python 2.2), time stamps are still represented as
     integers, unless ‘os.stat_float_times()’ is invoked to enable float
     return values:

          >>> os.stat("/tmp").st_mtime
          1034791200
          >>> os.stat_float_times(True)
          >>> os.stat("/tmp").st_mtime
          1034791200.6335014

     In Python 2.4, the default will change to always returning floats.

     Application developers should enable this feature only if all their
     libraries work properly when confronted with floating-point time
     stamps, or if they use the tuple API. If used, the feature should
     be activated on an application level instead of trying to enable it
     on a per-use basis.

   * The *note optparse: 90. module contains a new parser for
     command-line arguments that can convert option values to a
     particular Python type and will automatically generate a usage
     message.  See the following section for more details.

   * The old and never-documented ‘linuxaudiodev’ module has been
     deprecated, and a new version named ‘ossaudiodev’ has been added.
     The module was renamed because the OSS sound drivers can be used on
     platforms other than Linux, and the interface has also been tidied
     and brought up to date in various ways.  (Contributed by Greg Ward
     and Nicholas FitzRoy-Dale.)

   * The new *note platform: 98. module contains a number of functions
     that try to determine various properties of the platform you're
     running on.  There are functions for getting the architecture, CPU
     type, the Windows OS version, and even the Linux distribution
     version.  (Contributed by Marc-André Lemburg.)

   * The parser objects provided by the *note pyexpat: 10d. module can
     now optionally buffer character data, resulting in fewer calls to
     your character data handler and therefore faster performance.
     Setting the parser object's *note buffer_text: 142d. attribute to
     *note True: bb4. will enable buffering.

   * The ‘sample(population, k)’ function was added to the *note random:
     a6. module.  'population' is a sequence or ‘xrange’ object
     containing the elements of a population, and *note sample(): 6ea.
     chooses 'k' elements from the population without replacing chosen
     elements.  'k' can be any value up to ‘len(population)’.  For
     example:

          >>> days = ['Mo', 'Tu', 'We', 'Th', 'Fr', 'St', 'Sn']
          >>> random.sample(days, 3)      # Choose 3 elements
          ['St', 'Sn', 'Th']
          >>> random.sample(days, 7)      # Choose 7 elements
          ['Tu', 'Th', 'Mo', 'We', 'St', 'Fr', 'Sn']
          >>> random.sample(days, 7)      # Choose 7 again
          ['We', 'Mo', 'Sn', 'Fr', 'Tu', 'St', 'Th']
          >>> random.sample(days, 8)      # Can't choose eight
          Traceback (most recent call last):
            File "<stdin>", line 1, in ?
            File "random.py", line 414, in sample
                raise ValueError, "sample larger than population"
          ValueError: sample larger than population
          >>> random.sample(xrange(1,10000,2), 10)   # Choose ten odd nos. under 10000
          [3407, 3805, 1505, 7023, 2401, 2267, 9733, 3151, 8083, 9195]

     The *note random: a6. module now uses a new algorithm, the Mersenne
     Twister, implemented in C. It's faster and more extensively studied
     than the previous algorithm.

     (All changes contributed by Raymond Hettinger.)

   * The *note readline: a8. module also gained a number of new
     functions: *note get_history_item(): 142e, *note
     get_current_history_length(): 142f, and *note redisplay(): 1430.

   * The ‘rexec’ and ‘Bastion’ modules have been declared dead, and
     attempts to import them will fail with a *note RuntimeError: 179.
     New-style classes provide new ways to break out of the restricted
     execution environment provided by ‘rexec’, and no one has interest
     in fixing them or time to do so.  If you have applications using
     ‘rexec’, rewrite them to use something else.

     (Sticking with Python 2.2 or 2.1 will not make your applications
     any safer because there are known bugs in the ‘rexec’ module in
     those versions.  To repeat: if you're using ‘rexec’, stop using it
     immediately.)

   * The ‘rotor’ module has been deprecated because the algorithm it
     uses for encryption is not believed to be secure.  If you need
     encryption, use one of the several AES Python modules that are
     available separately.

   * The *note shutil: b3. module gained a ‘move(src, dest)’ function
     that recursively moves a file or directory to a new location.

   * Support for more advanced POSIX signal handling was added to the
     *note signal: b4. but then removed again as it proved impossible to
     make it work reliably across platforms.

   * The *note socket: b8. module now supports timeouts.  You can call
     the ‘settimeout(t)’ method on a socket object to set a timeout of
     't' seconds.  Subsequent socket operations that take longer than
     't' seconds to complete will abort and raise a *note
     socket.timeout: 7d8. exception.

     The original timeout implementation was by Tim O'Malley.  Michael
     Gilfix integrated it into the Python *note socket: b8. module and
     shepherded it through a lengthy review.  After the code was checked
     in, Guido van Rossum rewrote parts of it.  (This is a good example
     of a collaborative development process in action.)

   * On Windows, the *note socket: b8. module now ships with Secure
     Sockets Layer (SSL) support.

   * The value of the C ‘PYTHON_API_VERSION’ macro is now exposed at the
     Python level as ‘sys.api_version’.  The current exception can be
     cleared by calling the new ‘sys.exc_clear()’ function.

   * The new *note tarfile: c8. module allows reading from and writing
     to ‘tar’-format archive files.  (Contributed by Lars Gustäbel.)

   * The new *note textwrap: d5. module contains functions for wrapping
     strings containing paragraphs of text.  The ‘wrap(text, width)’
     function takes a string and returns a list containing the text
     split into lines of no more than the chosen width.  The ‘fill(text,
     width)’ function returns a single string, reformatted to fit into
     lines no longer than the chosen width.  (As you can guess, *note
     fill(): 1431. is built on top of *note wrap(): 1432.  For example:

          >>> import textwrap
          >>> paragraph = "Not a whit, we defy augury: ... more text ..."
          >>> textwrap.wrap(paragraph, 60)
          ["Not a whit, we defy augury: there's a special providence in",
           "the fall of a sparrow. If it be now, 'tis not to come; if it",
           ...]
          >>> print textwrap.fill(paragraph, 35)
          Not a whit, we defy augury: there's
          a special providence in the fall of
          a sparrow. If it be now, 'tis not
          to come; if it be not to come, it
          will be now; if it be not now, yet
          it will come: the readiness is all.
          >>>

     The module also contains a *note TextWrapper: f70. class that
     actually implements the text wrapping strategy.  Both the *note
     TextWrapper: f70. class and the *note wrap(): 1432. and *note
     fill(): 1431. functions support a number of additional keyword
     arguments for fine-tuning the formatting; consult the module's
     documentation for details.  (Contributed by Greg Ward.)

   * The ‘thread’ and *note threading: d6. modules now have companion
     modules, ‘dummy_thread’ and ‘dummy_threading’, that provide a
     do-nothing implementation of the ‘thread’ module's interface for
     platforms where threads are not supported.  The intention is to
     simplify thread-aware modules (ones that 'don't' rely on threads to
     run) by putting the following code at the top:

          try:
              import threading as _threading
          except ImportError:
              import dummy_threading as _threading

     In this example, ‘_threading’ is used as the module name to make it
     clear that the module being used is not necessarily the actual
     *note threading: d6. module.  Code can call functions and use
     classes in ‘_threading’ whether or not threads are supported,
     avoiding an *note if: 2c4. statement and making the code slightly
     clearer.  This module will not magically make multithreaded code
     run without threads; code that waits for another thread to return
     or to do something will simply hang forever.

   * The *note time: d7. module's *note strptime(): 139a. function has
     long been an annoyance because it uses the platform C library's
     *note strptime(): 139a. implementation, and different platforms
     sometimes have odd bugs.  Brett Cannon contributed a portable
     implementation that's written in pure Python and should behave
     identically on all platforms.

   * The new *note timeit: d8. module helps measure how long snippets of
     Python code take to execute.  The ‘timeit.py’ file can be run
     directly from the command line, or the module's *note Timer: 1433.
     class can be imported and used directly.  Here's a short example
     that figures out whether it's faster to convert an 8-bit string to
     Unicode by appending an empty Unicode string to it or by using the
     ‘unicode()’ function:

          import timeit

          timer1 = timeit.Timer('unicode("abc")')
          timer2 = timeit.Timer('"abc" + u""')

          # Run three trials
          print timer1.repeat(repeat=3, number=100000)
          print timer2.repeat(repeat=3, number=100000)

          # On my laptop this outputs:
          # [0.36831796169281006, 0.37441694736480713, 0.35304892063140869]
          # [0.17574405670166016, 0.18193507194519043, 0.17565798759460449]

   * The ‘Tix’ module has received various bug fixes and updates for the
     current version of the Tix package.

   * The ‘Tkinter’ module now works with a thread-enabled version of
     Tcl.  Tcl's threading model requires that widgets only be accessed
     from the thread in which they're created; accesses from another
     thread can cause Tcl to panic.  For certain Tcl interfaces,
     ‘Tkinter’ will now automatically avoid this when a widget is
     accessed from a different thread by marshalling a command, passing
     it to the correct thread, and waiting for the results.  Other
     interfaces can't be handled automatically but ‘Tkinter’ will now
     raise an exception on such an access so that you can at least find
     out about the problem.  See
     ‘https://mail.python.org/pipermail/python-dev/2002-December/031107.html’
     for a more detailed explanation of this change.  (Implemented by
     Martin von Löwis.)

   * Calling Tcl methods through ‘_tkinter’ no longer returns only
     strings.  Instead, if Tcl returns other objects those objects are
     converted to their Python equivalent, if one exists, or wrapped
     with a ‘_tkinter.Tcl_Obj’ object if no Python equivalent exists.
     This behavior can be controlled through the ‘wantobjects()’ method
     of ‘tkapp’ objects.

     When using ‘_tkinter’ through the ‘Tkinter’ module (as most Tkinter
     applications will), this feature is always activated.  It should
     not cause compatibility problems, since Tkinter would always
     convert string results to Python types where possible.

     If any incompatibilities are found, the old behavior can be
     restored by setting the ‘wantobjects’ variable in the ‘Tkinter’
     module to false before creating the first ‘tkapp’ object.

          import Tkinter
          Tkinter.wantobjects = 0

     Any breakage caused by this change should be reported as a bug.

   * The ‘UserDict’ module has a new ‘DictMixin’ class which defines all
     dictionary methods for classes that already have a minimum mapping
     interface.  This greatly simplifies writing classes that need to be
     substitutable for dictionaries, such as the classes in the *note
     shelve: b1. module.

     Adding the mix-in as a superclass provides the full dictionary
     interface whenever the class defines *note __getitem__(): 266,
     *note __setitem__(): 1434, *note __delitem__(): 1435, and ‘keys()’.
     For example:

          >>> import UserDict
          >>> class SeqDict(UserDict.DictMixin):
          ...     """Dictionary lookalike implemented with lists."""
          ...     def __init__(self):
          ...         self.keylist = []
          ...         self.valuelist = []
          ...     def __getitem__(self, key):
          ...         try:
          ...             i = self.keylist.index(key)
          ...         except ValueError:
          ...             raise KeyError
          ...         return self.valuelist[i]
          ...     def __setitem__(self, key, value):
          ...         try:
          ...             i = self.keylist.index(key)
          ...             self.valuelist[i] = value
          ...         except ValueError:
          ...             self.keylist.append(key)
          ...             self.valuelist.append(value)
          ...     def __delitem__(self, key):
          ...         try:
          ...             i = self.keylist.index(key)
          ...         except ValueError:
          ...             raise KeyError
          ...         self.keylist.pop(i)
          ...         self.valuelist.pop(i)
          ...     def keys(self):
          ...         return list(self.keylist)
          ...
          >>> s = SeqDict()
          >>> dir(s)      # See that other dictionary methods are implemented
          ['__cmp__', '__contains__', '__delitem__', '__doc__', '__getitem__',
           '__init__', '__iter__', '__len__', '__module__', '__repr__',
           '__setitem__', 'clear', 'get', 'has_key', 'items', 'iteritems',
           'iterkeys', 'itervalues', 'keylist', 'keys', 'pop', 'popitem',
           'setdefault', 'update', 'valuelist', 'values']

     （由 Raymond Hettinger 所貢獻。）

   * The DOM implementation in *note xml.dom.minidom: 109. can now
     generate XML output in a particular encoding by providing an
     optional encoding argument to the *note toxml(): 1436. and *note
     toprettyxml(): 1437. methods of DOM nodes.

   * The ‘xmlrpclib’ module now supports an XML-RPC extension for
     handling nil data values such as Python's ‘None’.  Nil values are
     always supported on unmarshalling an XML-RPC response.  To generate
     requests containing ‘None’, you must supply a true value for the
     'allow_none' parameter when creating a ‘Marshaller’ instance.

   * The new ‘DocXMLRPCServer’ module allows writing self-documenting
     XML-RPC servers.  Run it in demo mode (as a program) to see it in
     action.  Pointing the web browser to the RPC server produces
     pydoc-style documentation; pointing xmlrpclib to the server allows
     invoking the actual methods.  (Contributed by Brian Quinlan.)

   * Support for internationalized domain names (RFCs 3454, 3490, 3491,
     and 3492) has been added.  The "idna" encoding can be used to
     convert between a Unicode domain name and the ASCII-compatible
     encoding (ACE) of that name.

          >{}>{}> u"www.Alliancefrançaise.nu".encode("idna")
          'www.xn--alliancefranaise-npb.nu'

     The *note socket: b8. module has also been extended to
     transparently convert Unicode hostnames to the ACE version before
     passing them to the C library.  Modules that deal with hostnames
     such as ‘httplib’ and *note ftplib: 54.) also support Unicode host
     names; ‘httplib’ also sends HTTP ‘Host’ headers using the ACE
     version of the domain name.  *note urllib: f1. supports Unicode
     URLs with non-ASCII host names as long as the ‘path’ part of the
     URL is ASCII only.

     To implement this change, the *note stringprep: bf. module, the
     ‘mkstringprep’ tool and the ‘punycode’ encoding have been added.

* Menu:

* Date/Time Type::
* The optparse Module::

   ---------- Footnotes ----------

   (1) https://pybsddb.sourceforge.net


File: python.info,  Node: Date/Time Type,  Next: The optparse Module,  Up: New Improved and Deprecated Modules<4>

1.19.17.1 Date/Time Type
........................

Date and time types suitable for expressing timestamps were added as the
*note datetime: 28. module.  The types don't support different calendars
or many fancy features, and just stick to the basics of representing
time.

The three primary types are: *note date: 1b1, representing a day, month,
and year; *note time: 1b2, consisting of hour, minute, and second; and
*note datetime: 1b0, which contains all the attributes of both *note
date: 1b1. and *note time: 1b2.  There's also a *note timedelta: 973.
class representing differences between two points in time, and time zone
logic is implemented by classes inheriting from the abstract *note
tzinfo: 582. class.

You can create instances of *note date: 1b1. and *note time: 1b2. by
either supplying keyword arguments to the appropriate constructor, e.g.
‘datetime.date(year=1972, month=10, day=15)’, or by using one of a
number of class methods.  For example, the *note today(): 1439. class
method returns the current local date.

Once created, instances of the date/time classes are all immutable.
There are a number of methods for producing formatted strings from
objects:

     >>> import datetime
     >>> now = datetime.datetime.now()
     >>> now.isoformat()
     '2002-12-30T21:27:03.994956'
     >>> now.ctime()  # Only available on date, datetime
     'Mon Dec 30 21:27:03 2002'
     >>> now.strftime('%Y %d %b')
     '2002 30 Dec'

The *note replace(): 143a. method allows modifying one or more fields of
a *note date: 1b1. or *note datetime: 1b0. instance, returning a new
instance:

     >>> d = datetime.datetime.now()
     >>> d
     datetime.datetime(2002, 12, 30, 22, 15, 38, 827738)
     >>> d.replace(year=2001, hour = 12)
     datetime.datetime(2001, 12, 30, 12, 15, 38, 827738)
     >>>

Instances can be compared, hashed, and converted to strings (the result
is the same as that of *note isoformat(): ad4.).  *note date: 1b1. and
*note datetime: 1b0. instances can be subtracted from each other, and
added to *note timedelta: 973. instances.  The largest missing feature
is that there's no standard library support for parsing strings and
getting back a *note date: 1b1. or *note datetime: 1b0.

For more information, refer to the module's reference documentation.
(Contributed by Tim Peters.)


File: python.info,  Node: The optparse Module,  Prev: Date/Time Type,  Up: New Improved and Deprecated Modules<4>

1.19.17.2 The optparse Module
.............................

The *note getopt: 57. module provides simple parsing of command-line
arguments.  The new *note optparse: 90. module (originally named Optik)
provides more elaborate command-line parsing that follows the Unix
conventions, automatically creates the output for ‘--help’, and can
perform different actions for different options.

You start by creating an instance of *note OptionParser: 143c. and
telling it what your program's options are.

     import sys
     from optparse import OptionParser

     op = OptionParser()
     op.add_option('-i', '--input',
                   action='store', type='string', dest='input',
                   help='set input filename')
     op.add_option('-l', '--length',
                   action='store', type='int', dest='length',
                   help='set maximum length of output')

Parsing a command line is then done by calling the *note parse_args():
143d. method.

     options, args = op.parse_args(sys.argv[1:])
     print options
     print args

This returns an object containing all of the option values, and a list
of strings containing the remaining arguments.

Invoking the script with the various arguments now works as you'd expect
it to.  Note that the length argument is automatically converted to an
integer.

     $ ./python opt.py -i data arg1
     <Values at 0x400cad4c: {'input': 'data', 'length': None}>
     ['arg1']
     $ ./python opt.py --input=data --length=4
     <Values at 0x400cad2c: {'input': 'data', 'length': 4}>
     []
     $

The help message is automatically generated for you:

     $ ./python opt.py --help
     usage: opt.py [options]

     options:
       -h, --help            show this help message and exit
       -iINPUT, --input=INPUT
                             set input filename
       -lLENGTH, --length=LENGTH
                             set maximum length of output
     $

更多細節請見 module 文件。

Optik was written by Greg Ward, with suggestions from the readers of the
Getopt SIG.


File: python.info,  Node: Pymalloc A Specialized Object Allocator,  Next: Build and C API Changes<11>,  Prev: New Improved and Deprecated Modules<4>,  Up: Python 2 3 有什麼新功能

1.19.18 Pymalloc: A Specialized Object Allocator
------------------------------------------------

Pymalloc, a specialized object allocator written by Vladimir Marangozov,
was a feature added to Python 2.1.  Pymalloc is intended to be faster
than the system ‘malloc()’ and to have less memory overhead for
allocation patterns typical of Python programs.  The allocator uses C's
‘malloc()’ function to get large pools of memory and then fulfills
smaller memory requests from these pools.

In 2.1 and 2.2, pymalloc was an experimental feature and wasn't enabled
by default; you had to explicitly enable it when compiling Python by
providing the ‘--with-pymalloc’ option to the ‘configure’ script.  In
2.3, pymalloc has had further enhancements and is now enabled by
default; you'll have to supply ‘--without-pymalloc’ to disable it.

This change is transparent to code written in Python; however, pymalloc
may expose bugs in C extensions.  Authors of C extension modules should
test their code with pymalloc enabled, because some incorrect code may
cause core dumps at runtime.

There's one particularly common error that causes problems.  There are a
number of memory allocation functions in Python's C API that have
previously just been aliases for the C library's ‘malloc()’ and
‘free()’, meaning that if you accidentally called mismatched functions
the error wouldn't be noticeable.  When the object allocator is enabled,
these functions aren't aliases of ‘malloc()’ and ‘free()’ any more, and
calling the wrong function to free memory may get you a core dump.  For
example, if memory was allocated using *note PyObject_Malloc(): c0f, it
has to be freed using *note PyObject_Free(): c0c, not ‘free()’.  A few
modules included with Python fell afoul of this and had to be fixed;
doubtless there are more third-party modules that will have the same
problem.

As part of this change, the confusing multiple interfaces for allocating
memory have been consolidated down into two API families.  Memory
allocated with one family must not be manipulated with functions from
the other family.  There is one family for allocating chunks of memory
and another family of functions specifically for allocating Python
objects.

   * To allocate and free an undistinguished chunk of memory use the
     "raw memory" family: *note PyMem_Malloc(): c0d, *note
     PyMem_Realloc(): fd5, and *note PyMem_Free(): 13b0.

   * The "object memory" family is the interface to the pymalloc
     facility described above and is biased towards a large number of
     "small" allocations: *note PyObject_Malloc(): c0f, *note
     PyObject_Realloc(): 13b1, and *note PyObject_Free(): c0c.

   * To allocate and free Python objects, use the "object" family *note
     PyObject_New: 929, *note PyObject_NewVar: 92a, and *note
     PyObject_Del(): 1440.

Thanks to lots of work by Tim Peters, pymalloc in 2.3 also provides
debugging features to catch memory overwrites and doubled frees in both
extension modules and in the interpreter itself.  To enable this
support, compile a debugging version of the Python interpreter by
running ‘configure’ with ‘--with-pydebug’.

To aid extension writers, a header file ‘Misc/pymemcompat.h’ is
distributed with the source to Python 2.3 that allows Python extensions
to use the 2.3 interfaces to memory allocation while compiling against
any version of Python since 1.5.2.  You would copy the file from
Python's source distribution and bundle it with the source of your
extension.

也參考
......

‘https://hg.python.org/cpython/file/default/Objects/obmalloc.c’

     For the full details of the pymalloc implementation, see the
     comments at the top of the file ‘Objects/obmalloc.c’ in the Python
     source code.  The above link points to the file within the
     python.org SVN browser.


File: python.info,  Node: Build and C API Changes<11>,  Next: Other Changes and Fixes<2>,  Prev: Pymalloc A Specialized Object Allocator,  Up: Python 2 3 有什麼新功能

1.19.19 Build and C API Changes
-------------------------------

Changes to Python's build process and to the C API include:

   * The cycle detection implementation used by the garbage collection
     has proven to be stable, so it's now been made mandatory.  You can
     no longer compile Python without it, and the ‘--with-cycle-gc’
     switch to ‘configure’ has been removed.

   * Python can now optionally be built as a shared library
     (‘libpython2.3.so’) by supplying ‘--enable-shared’ when running
     Python's ‘configure’ script.  (Contributed by Ondrej Palkovsky.)

   * The ‘DL_EXPORT’ and ‘DL_IMPORT’ macros are now deprecated.
     Initialization functions for Python extension modules should now be
     declared using the new macro *note PyMODINIT_FUNC: 1442, while the
     Python core will generally use the ‘PyAPI_FUNC’ and ‘PyAPI_DATA’
     macros.

   * The interpreter can be compiled without any docstrings for the
     built-in functions and modules by supplying ‘--without-doc-strings’
     to the ‘configure’ script.  This makes the Python executable about
     10% smaller, but will also mean that you can't get help for
     Python's built-ins.  (Contributed by Gustavo Niemeyer.)

   * The ‘PyArg_NoArgs()’ macro is now deprecated, and code that uses it
     should be changed.  For Python 2.2 and later, the method definition
     table can specify the *note METH_NOARGS: 1443. flag, signalling
     that there are no arguments, and the argument checking can then be
     removed.  If compatibility with pre-2.2 versions of Python is
     important, the code could use ‘PyArg_ParseTuple(args, "")’ instead,
     but this will be slower than using *note METH_NOARGS: 1443.

   * *note PyArg_ParseTuple(): 517. accepts new format characters for
     various sizes of unsigned integers: ‘B’ for unsigned char, ‘H’ for
     unsigned short int, ‘I’ for unsigned int, and ‘K’ for unsigned long
     long.

   * A new function, ‘PyObject_DelItemString(mapping, char *key)’ was
     added as shorthand for ‘PyObject_DelItem(mapping,
     PyString_New(key))’.

   * File objects now manage their internal string buffer differently,
     increasing it exponentially when needed.  This results in the
     benchmark tests in ‘Lib/test/test_bufio.py’ speeding up
     considerably (from 57 seconds to 1.7 seconds, according to one
     measurement).

   * It's now possible to define class and static methods for a C
     extension type by setting either the *note METH_CLASS: 1444. or
     *note METH_STATIC: 1445. flags in a method's *note PyMethodDef:
     1446. structure.

   * Python now includes a copy of the Expat XML parser's source code,
     removing any dependence on a system version or local installation
     of Expat.

   * If you dynamically allocate type objects in your extension, you
     should be aware of a change in the rules relating to the
     ‘__module__’ and *note __name__: 1416. attributes.  In summary, you
     will want to ensure the type's dictionary contains a ‘'__module__'’
     key; making the module name the part of the type name leading up to
     the final period will no longer have the desired effect.  For more
     detail, read the API reference documentation or the source.

* Menu:

* Port-Specific Changes: Port-Specific Changes<3>.


File: python.info,  Node: Port-Specific Changes<3>,  Up: Build and C API Changes<11>

1.19.19.1 Port-Specific Changes
...............................

Support for a port to IBM's OS/2 using the EMX runtime environment was
merged into the main Python source tree.  EMX is a POSIX emulation layer
over the OS/2 system APIs.  The Python port for EMX tries to support all
the POSIX-like capability exposed by the EMX runtime, and mostly
succeeds; ‘fork()’ and *note fcntl(): 4f. are restricted by the
limitations of the underlying emulation layer.  The standard OS/2 port,
which uses IBM's Visual Age compiler, also gained support for
case-sensitive import semantics as part of the integration of the EMX
port into CVS. (Contributed by Andrew MacIntyre.)

On MacOS, most toolbox modules have been weaklinked to improve backward
compatibility.  This means that modules will no longer fail to load if a
single routine is missing on the current OS version.  Instead calling
the missing routine will raise an exception.  (Contributed by Jack
Jansen.)

The RPM spec files, found in the ‘Misc/RPM/’ directory in the Python
source distribution, were updated for 2.3.  (Contributed by Sean
Reifschneider.)

Other new platforms now supported by Python include AtheOS
(‘http://www.atheos.cx/’), GNU/Hurd, and OpenVMS.


File: python.info,  Node: Other Changes and Fixes<2>,  Next: Porting to Python 2 3,  Prev: Build and C API Changes<11>,  Up: Python 2 3 有什麼新功能

1.19.20 Other Changes and Fixes
-------------------------------

As usual, there were a bunch of other improvements and bugfixes
scattered throughout the source tree.  A search through the CVS change
logs finds there were 523 patches applied and 514 bugs fixed between
Python 2.2 and 2.3.  Both figures are likely to be underestimates.

Some of the more notable changes are:

   * If the *note PYTHONINSPECT: 1449. environment variable is set, the
     Python interpreter will enter the interactive prompt after running
     a Python program, as if Python had been invoked with the *note -i:
     144a. option.  The environment variable can be set before running
     the Python interpreter, or it can be set by the Python program as
     part of its execution.

   * The ‘regrtest.py’ script now provides a way to allow "all resources
     except 'foo'."  A resource name passed to the ‘-u’ option can now
     be prefixed with a hyphen (‘'-'’) to mean "remove this resource."
     For example, the option '‘-uall,-bsddb’' could be used to enable
     the use of all resources except ‘bsddb’.

   * The tools used to build the documentation now work under Cygwin as
     well as Unix.

   * The ‘SET_LINENO’ opcode has been removed.  Back in the mists of
     time, this opcode was needed to produce line numbers in tracebacks
     and support trace functions (for, e.g., *note pdb: 94.).  Since
     Python 1.5, the line numbers in tracebacks have been computed using
     a different mechanism that works with "python -O". For Python 2.3
     Michael Hudson implemented a similar scheme to determine when to
     call the trace function, removing the need for ‘SET_LINENO’
     entirely.

     It would be difficult to detect any resulting difference from
     Python code, apart from a slight speed up when Python is run
     without *note -O: d5b.

     C extensions that access the *note f_lineno: 750. field of frame
     objects should instead call ‘PyCode_Addr2Line(f->f_code,
     f->f_lasti)’.  This will have the added effect of making the code
     work as desired under "python -O" in earlier versions of Python.

     A nifty new feature is that trace functions can now assign to the
     *note f_lineno: 750. attribute of frame objects, changing the line
     that will be executed next.  A ‘jump’ command has been added to the
     *note pdb: 94. debugger taking advantage of this new feature.
     (Implemented by Richie Hindle.)


File: python.info,  Node: Porting to Python 2 3,  Next: 致謝<5>,  Prev: Other Changes and Fixes<2>,  Up: Python 2 3 有什麼新功能

1.19.21 Porting to Python 2.3
-----------------------------

This section lists previously described changes that may require changes
to your code:

   * *note yield: 971. is now always a keyword; if it's used as a
     variable name in your code, a different name must be chosen.

   * For strings 'X' and 'Y', ‘X in Y’ now works if 'X' is more than one
     character long.

   * The *note int(): 23c. type constructor will now return a long
     integer instead of raising an *note OverflowError: 825. when a
     string or floating-point number is too large to fit into an
     integer.

   * If you have Unicode strings that contain 8-bit characters, you must
     declare the file's encoding (UTF-8, Latin-1, or whatever) by adding
     a comment to the top of the file.  See section *note PEP 263;
     Source Code Encodings: 13f3. for more information.

   * Calling Tcl methods through ‘_tkinter’ no longer returns only
     strings.  Instead, if Tcl returns other objects those objects are
     converted to their Python equivalent, if one exists, or wrapped
     with a ‘_tkinter.Tcl_Obj’ object if no Python equivalent exists.

   * Large octal and hex literals such as ‘0xffffffff’ now trigger a
     *note FutureWarning: 357.  Currently they're stored as 32-bit
     numbers and result in a negative value, but in Python 2.4 they'll
     become positive long integers.

     There are a few ways to fix this warning.  If you really need a
     positive number, just add an ‘L’ to the end of the literal.  If
     you're trying to get a 32-bit integer with low bits set and have
     previously used an expression such as ‘~(1 << 31)’, it's probably
     clearest to start with all bits set and clear the desired upper
     bits.  For example, to clear just the top bit (bit 31), you could
     write ‘0xffffffffL &~(1L<<31)’.

   * You can no longer disable assertions by assigning to ‘__debug__’.

   * The Distutils ‘setup()’ function has gained various new keyword
     arguments such as 'depends'.  Old versions of the Distutils will
     abort if passed unknown keywords.  A solution is to check for the
     presence of the new ‘get_distutil_options()’ function in your
     ‘setup.py’ and only uses the new keywords with a version of the
     Distutils that supports them:

          from distutils import core

          kw = {'sources': 'foo.c', ...}
          if hasattr(core, 'get_distutil_options'):
              kw['depends'] = ['foo.h']
          ext = Extension(**kw)

   * Using ‘None’ as a variable name will now result in a *note
     SyntaxWarning: 40c. warning.

   * Names of extension types defined by the modules included with
     Python now contain the module and a ‘'.'’ in front of the type
     name.


File: python.info,  Node: 致謝<5>,  Prev: Porting to Python 2 3,  Up: Python 2 3 有什麼新功能

1.19.22 致謝
------------

The author would like to thank the following people for offering
suggestions, corrections and assistance with various drafts of this
article: Jeff Bauer, Simon Brunning, Brett Cannon, Michael Chermside,
Andrew Dalke, Scott David Daniels, Fred L. Drake, Jr., David Fraser,
Kelly Gerber, Raymond Hettinger, Michael Hudson, Chris Lambert, Detlef
Lannert, Martin von Löwis, Andrew MacIntyre, Lalo Martins, Chad Netzer,
Gustavo Niemeyer, Neal Norwitz, Hans Nowak, Chris Reedy, Francesco
Ricciardi, Vinay Sajip, Neil Schemenauer, Roman Suzi, Jason Tishler,
Just van Rossum.


File: python.info,  Node: Python 2 2 有什麼新功能,  Next: Python 2 1 有什麼新功能,  Prev: Python 2 3 有什麼新功能,  Up: Python 有什麼新功能？

1.20 Python 2.2 有什麼新功能
============================


作者: A.M. Kuchling

* Menu:

* 簡介::
* PEPs 252 and 253; Type and Class Changes: PEPs 252 and 253 Type and Class Changes.
* PEP 234：疊代器::
* PEP 255; Simple Generators: PEP 255 Simple Generators<2>.
* PEP 237; Unifying Long Integers and Integers: PEP 237 Unifying Long Integers and Integers<2>.
* PEP 238; Changing the Division Operator: PEP 238 Changing the Division Operator.
* Unicode 變更::
* PEP 227; Nested Scopes: PEP 227 Nested Scopes.
* New and Improved Modules: New and Improved Modules<3>.
* 直譯器的變更與修正::
* 其他改動與修正::
* 致謝: 致謝<6>.


File: python.info,  Node: 簡介,  Next: PEPs 252 and 253 Type and Class Changes,  Up: Python 2 2 有什麼新功能

1.20.1 簡介
-----------

This article explains the new features in Python 2.2.2, released on
October 14, 2002.  Python 2.2.2 is a bugfix release of Python 2.2,
originally released on December 21, 2001.

Python 2.2 can be thought of as the "cleanup release".  There are some
features such as generators and iterators that are completely new, but
most of the changes, significant and far-reaching though they may be,
are aimed at cleaning up irregularities and dark corners of the language
design.

This article doesn't attempt to provide a complete specification of the
new features, but instead provides a convenient overview.  For full
details, you should refer to the documentation for Python 2.2, such as
the Python Library Reference(1) and the Python Reference Manual(2).  If
you want to understand the complete implementation and design rationale
for a change, refer to the PEP for a particular new feature.

   ---------- Footnotes ----------

   (1) https://docs.python.org/2.2/lib/lib.html

   (2) https://docs.python.org/2.2/ref/ref.html


File: python.info,  Node: PEPs 252 and 253 Type and Class Changes,  Next: PEP 234：疊代器,  Prev: 簡介,  Up: Python 2 2 有什麼新功能

1.20.2 PEPs 252 and 253: Type and Class Changes
-----------------------------------------------

The largest and most far-reaching changes in Python 2.2 are to Python's
model of objects and classes.  The changes should be backward
compatible, so it's likely that your code will continue to run
unchanged, but the changes provide some amazing new capabilities.
Before beginning this, the longest and most complicated section of this
article, I'll provide an overview of the changes and offer some
comments.

A long time ago I wrote a web page listing flaws in Python's design.
One of the most significant flaws was that it's impossible to subclass
Python types implemented in C. In particular, it's not possible to
subclass built-in types, so you can't just subclass, say, lists in order
to add a single useful method to them.  The ‘UserList’ module provides a
class that supports all of the methods of lists and that can be
subclassed further, but there's lots of C code that expects a regular
Python list and won't accept a *note UserList: 1452. instance.

Python 2.2 fixes this, and in the process adds some exciting new
capabilities.  A brief summary:

   * You can subclass built-in types such as lists and even integers,
     and your subclasses should work in every place that requires the
     original type.

   * It's now possible to define static and class methods, in addition
     to the instance methods available in previous versions of Python.

   * It's also possible to automatically call methods on accessing or
     setting an instance attribute by using a new mechanism called
     'properties'.  Many uses of *note __getattr__(): 47a. can be
     rewritten to use properties instead, making the resulting code
     simpler and faster.  As a small side benefit, attributes can now
     have docstrings, too.

   * The list of legal attributes for an instance can be limited to a
     particular set using 'slots', making it possible to safeguard
     against typos and perhaps make more optimizations possible in
     future versions of Python.

Some users have voiced concern about all these changes.  Sure, they say,
the new features are neat and lend themselves to all sorts of tricks
that weren't possible in previous versions of Python, but they also make
the language more complicated.  Some people have said that they've
always recommended Python for its simplicity, and feel that its
simplicity is being lost.

Personally, I think there's no need to worry.  Many of the new features
are quite esoteric, and you can write a lot of Python code without ever
needed to be aware of them.  Writing a simple class is no more difficult
than it ever was, so you don't need to bother learning or teaching them
unless they're actually needed.  Some very complicated tasks that were
previously only possible from C will now be possible in pure Python, and
to my mind that's all for the better.

I'm not going to attempt to cover every single corner case and small
change that were required to make the new features work.  Instead this
section will paint only the broad strokes.  See section *note 相關連結:
1453, "Related Links", for further sources of information about Python
2.2's new object model.

* Menu:

* Old and New Classes::
* Descriptors::
* Multiple Inheritance; The Diamond Rule: Multiple Inheritance The Diamond Rule.
* Attribute Access::
* 相關連結::


File: python.info,  Node: Old and New Classes,  Next: Descriptors,  Up: PEPs 252 and 253 Type and Class Changes

1.20.2.1 Old and New Classes
............................

First, you should know that Python 2.2 really has two kinds of classes:
classic or old-style classes, and new-style classes.  The old-style
class model is exactly the same as the class model in earlier versions
of Python.  All the new features described in this section apply only to
new-style classes.  This divergence isn't intended to last forever;
eventually old-style classes will be dropped, possibly in Python 3.0.

So how do you define a new-style class?  You do it by subclassing an
existing new-style class.  Most of Python's built-in types, such as
integers, lists, dictionaries, and even files, are new-style classes
now.  A new-style class named *note object: a2f, the base class for all
built-in types, has also been added so if no built-in type is suitable,
you can just subclass *note object: a2f.:

     class C(object):
         def __init__ (self):
             ...
         ...

This means that *note class: 126a. statements that don't have any base
classes are always classic classes in Python 2.2.  (Actually you can
also change this by setting a module-level variable named
‘__metaclass__’ -- see PEP 253(1) for the details -- but it's easier to
just subclass *note object: a2f.)

The type objects for the built-in types are available as built-ins,
named using a clever trick.  Python has always had built-in functions
named *note int(): 23c, *note float(): 2c8, and *note str(): 3f2.  In
2.2, they aren't functions any more, but type objects that behave as
factories when called.

     >>> int
     <type 'int'>
     >>> int('123')
     123

To make the set of types complete, new type objects such as *note
dict(): 23b. and ‘file()’ have been added.  Here's a more interesting
example, adding a ‘lock()’ method to file objects:

     class LockableFile(file):
         def lock (self, operation, length=0, start=0, whence=0):
             import fcntl
             return fcntl.lockf(self.fileno(), operation,
                                length, start, whence)

The now-obsolete ‘posixfile’ module contained a class that emulated all
of a file object's methods and also added a ‘lock()’ method, but this
class couldn't be passed to internal functions that expected a built-in
file, something which is possible with our new ‘LockableFile’.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0253/


File: python.info,  Node: Descriptors,  Next: Multiple Inheritance The Diamond Rule,  Prev: Old and New Classes,  Up: PEPs 252 and 253 Type and Class Changes

1.20.2.2 Descriptors
....................

In previous versions of Python, there was no consistent way to discover
what attributes and methods were supported by an object.  There were
some informal conventions, such as defining ‘__members__’ and
‘__methods__’ attributes that were lists of names, but often the author
of an extension type or a class wouldn't bother to define them.  You
could fall back on inspecting the *note __dict__: c04. of an object, but
when class inheritance or an arbitrary ‘__getattr__()’ hook were in use
this could still be inaccurate.

The one big idea underlying the new class model is that an API for
describing the attributes of an object using 'descriptors' has been
formalized.  Descriptors specify the value of an attribute, stating
whether it's a method or a field.  With the descriptor API, static
methods and class methods become possible, as well as more exotic
constructs.

Attribute descriptors are objects that live inside class objects, and
have a few attributes of their own:

   * *note __name__: 1416. 是屬性的名稱。

   * ‘__doc__’ 是屬性的文件字串 (docstring)。

   * ‘__get__(object)’ is a method that retrieves the attribute value
     from 'object'.

   * ‘__set__(object, value)’ sets the attribute on 'object' to 'value'.

   * ‘__delete__(object, value)’ deletes the 'value' attribute of
     'object'.

For example, when you write ‘obj.x’, the steps that Python actually
performs are:

     descriptor = obj.__class__.x
     descriptor.__get__(obj)

For methods, ‘descriptor.__get__()’ returns a temporary object that's
callable, and wraps up the instance and the method to be called on it.
This is also why static methods and class methods are now possible; they
have descriptors that wrap up just the method, or the method and the
class.  As a brief explanation of these new kinds of methods, static
methods aren't passed the instance, and therefore resemble regular
functions.  Class methods are passed the class of the object, but not
the object itself.  Static and class methods are defined like this:

     class C(object):
         def f(arg1, arg2):
             ...
         f = staticmethod(f)

         def g(cls, arg1, arg2):
             ...
         g = classmethod(g)

The *note staticmethod(): 358. function takes the function ‘f()’, and
returns it wrapped up in a descriptor so it can be stored in the class
object.  You might expect there to be special syntax for creating such
methods (‘def static f’, ‘defstatic f()’, or something like that) but no
such syntax has been defined yet; that's been left for future versions
of Python.

More new features, such as slots and properties, are also implemented as
new kinds of descriptors, and it's not difficult to write a descriptor
class that does something novel.  For example, it would be possible to
write a descriptor class that made it possible to write Eiffel-style
preconditions and postconditions for a method.  A class that used this
feature might be defined like this:

     from eiffel import eiffelmethod

     class C(object):
         def f(self, arg1, arg2):
             # The actual function
             ...
         def pre_f(self):
             # Check preconditions
             ...
         def post_f(self):
             # Check postconditions
             ...

         f = eiffelmethod(f, pre_f, post_f)

Note that a person using the new ‘eiffelmethod()’ doesn't have to
understand anything about descriptors.  This is why I think the new
features don't increase the basic complexity of the language.  There
will be a few wizards who need to know about it in order to write
‘eiffelmethod()’ or the ZODB or whatever, but most users will just write
code on top of the resulting libraries and ignore the implementation
details.


File: python.info,  Node: Multiple Inheritance The Diamond Rule,  Next: Attribute Access,  Prev: Descriptors,  Up: PEPs 252 and 253 Type and Class Changes

1.20.2.3 Multiple Inheritance: The Diamond Rule
...............................................

Multiple inheritance has also been made more useful through changing the
rules under which names are resolved.  Consider this set of classes
(diagram taken from PEP 253(1) by Guido van Rossum):

           class A:
             ^ ^  def save(self): ...
            /   \
           /     \
          /       \
         /         \
     class B     class C:
         ^         ^  def save(self): ...
          \       /
           \     /
            \   /
             \ /
           class D

The lookup rule for classic classes is simple but not very smart; the
base classes are searched depth-first, going from left to right.  A
reference to ‘D.save()’ will search the classes ‘D’, ‘B’, and then ‘A’,
where ‘save()’ would be found and returned.  ‘C.save()’ would never be
found at all.  This is bad, because if ‘C’'s ‘save()’ method is saving
some internal state specific to ‘C’, not calling it will result in that
state never getting saved.

New-style classes follow a different algorithm that's a bit more
complicated to explain, but does the right thing in this situation.
(Note that Python 2.3 changes this algorithm to one that produces the
same results in most cases, but produces more useful results for really
complicated inheritance graphs.)

  1. List all the base classes, following the classic lookup rule and
     include a class multiple times if it's visited repeatedly.  In the
     above example, the list of visited classes is [‘D’, ‘B’, ‘A’, ‘C’,
     ‘A’].

  2. Scan the list for duplicated classes.  If any are found, remove all
     but one occurrence, leaving the 'last' one in the list.  In the
     above example, the list becomes [‘D’, ‘B’, ‘C’, ‘A’] after dropping
     duplicates.

Following this rule, referring to ‘D.save()’ will return ‘C.save()’,
which is the behaviour we're after.  This lookup rule is the same as the
one followed by Common Lisp.  A new built-in function, *note super():
483, provides a way to get at a class's superclasses without having to
reimplement Python's algorithm.  The most commonly used form will be
‘super(class, obj)’, which returns a bound superclass object (not the
actual class object).  This form will be used in methods to call a
method in the superclass; for example, ‘D’'s ‘save()’ method would look
like this:

     class D (B,C):
         def save (self):
             # Call superclass .save()
             super(D, self).save()
             # Save D's private information here
             ...

*note super(): 483. can also return unbound superclass objects when
called as ‘super(class)’ or ‘super(class1, class2)’, but this probably
won't often be useful.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0253/


File: python.info,  Node: Attribute Access,  Next: 相關連結,  Prev: Multiple Inheritance The Diamond Rule,  Up: PEPs 252 and 253 Type and Class Changes

1.20.2.4 Attribute Access
.........................

A fair number of sophisticated Python classes define hooks for attribute
access using *note __getattr__(): 47a.; most commonly this is done for
convenience, to make code more readable by automatically mapping an
attribute access such as ‘obj.parent’ into a method call such as
‘obj.get_parent’.  Python 2.2 adds some new ways of controlling
attribute access.

First, ‘__getattr__(attr_name)’ is still supported by new-style classes,
and nothing about it has changed.  As before, it will be called when an
attempt is made to access ‘obj.foo’ and no attribute named ‘foo’ is
found in the instance's dictionary.

New-style classes also support a new method,
‘__getattribute__(attr_name)’.  The difference between the two methods
is that *note __getattribute__(): b79. is 'always' called whenever any
attribute is accessed, while the old *note __getattr__(): 47a. is only
called if ‘foo’ isn't found in the instance's dictionary.

However, Python 2.2's support for 'properties' will often be a simpler
way to trap attribute references.  Writing a ‘__getattr__()’ method is
complicated because to avoid recursion you can't use regular attribute
accesses inside them, and instead have to mess around with the contents
of *note __dict__: c04.  *note __getattr__(): 47a. methods also end up
being called by Python when it checks for other methods such as *note
__repr__(): 5c2. or ‘__coerce__()’, and so have to be written with this
in mind.  Finally, calling a function on every attribute access results
in a sizable performance loss.

*note property: 180. is a new built-in type that packages up three
functions that get, set, or delete an attribute, and a docstring.  For
example, if you want to define a ‘size’ attribute that's computed, but
also settable, you could write:

     class C(object):
         def get_size (self):
             result = ... computation ...
             return result
         def set_size (self, size):
             ... compute something based on the size
             and set internal state appropriately ...

         # Define a property.  The 'delete this attribute'
         # method is defined as None, so the attribute
         # can't be deleted.
         size = property(get_size, set_size,
                         None,
                         "Storage size of this instance")

That is certainly clearer and easier to write than a pair of
‘__getattr__()’/‘__setattr__()’ methods that check for the ‘size’
attribute and handle it specially while retrieving all other attributes
from the instance's *note __dict__: c04.  Accesses to ‘size’ are also
the only ones which have to perform the work of calling a function, so
references to other attributes run at their usual speed.

Finally, it's possible to constrain the list of attributes that can be
referenced on an object using the new *note __slots__: 1458. class
attribute.  Python objects are usually very dynamic; at any time it's
possible to define a new attribute on an instance by just doing
‘obj.new_attr=1’.  A new-style class can define a class attribute named
*note __slots__: 1458. to limit the legal attributes to a particular set
of names.  An example will make this clear:

     >>> class C(object):
     ...     __slots__ = ('template', 'name')
     ...
     >>> obj = C()
     >>> print obj.template
     None
     >>> obj.template = 'Test'
     >>> print obj.template
     Test
     >>> obj.newattr = None
     Traceback (most recent call last):
       File "<stdin>", line 1, in ?
     AttributeError: 'C' object has no attribute 'newattr'

Note how you get an *note AttributeError: 2f6. on the attempt to assign
to an attribute not listed in *note __slots__: 1458.


File: python.info,  Node: 相關連結,  Prev: Attribute Access,  Up: PEPs 252 and 253 Type and Class Changes

1.20.2.5 相關連結
.................

This section has just been a quick overview of the new features, giving
enough of an explanation to start you programming, but many details have
been simplified or ignored.  Where should you go to get a more complete
picture?

The *note 描述器 (Descriptor) 指南: 145a. is a lengthy tutorial
introduction to the descriptor features, written by Guido van Rossum.
If my description has whetted your appetite, go read this tutorial next,
because it goes into much more detail about the new features while still
remaining quite easy to read.

Next, there are two relevant PEPs, PEP 252(1) and PEP 253(2).  PEP
252(3) is titled "Making Types Look More Like Classes", and covers the
descriptor API. PEP 253(4) is titled "Subtyping Built-in Types", and
describes the changes to type objects that make it possible to subtype
built-in objects.  PEP 253(5) is the more complicated PEP of the two,
and at a few points the necessary explanations of types and meta-types
may cause your head to explode.  Both PEPs were written and implemented
by Guido van Rossum, with substantial assistance from the rest of the
Zope Corp.  team.

Finally, there's the ultimate authority: the source code.  Most of the
machinery for the type handling is in ‘Objects/typeobject.c’, but you
should only resort to it after all other avenues have been exhausted,
including posting a question to python-list or python-dev.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0252/

   (2) https://peps.python.org/pep-0253/

   (3) https://peps.python.org/pep-0252/

   (4) https://peps.python.org/pep-0253/

   (5) https://peps.python.org/pep-0253/


File: python.info,  Node: PEP 234：疊代器,  Next: PEP 255 Simple Generators<2>,  Prev: PEPs 252 and 253 Type and Class Changes,  Up: Python 2 2 有什麼新功能

1.20.3 PEP 234：疊代器
----------------------

Another significant addition to 2.2 is an iteration interface at both
the C and Python levels.  Objects can define how they can be looped over
by callers.

In Python versions up to 2.1, the usual way to make ‘for item in obj’
work is to define a *note __getitem__(): 266. method that looks
something like this:

     def __getitem__(self, index):
         return <next item>

*note __getitem__(): 266. is more properly used to define an indexing
operation on an object so that you can write ‘obj[5]’ to retrieve the
sixth element.  It's a bit misleading when you're using this only to
support *note for: 2c3. loops.  Consider some file-like object that
wants to be looped over; the 'index' parameter is essentially
meaningless, as the class probably assumes that a series of *note
__getitem__(): 266. calls will be made with 'index' incrementing by one
each time.  In other words, the presence of the *note __getitem__():
266. method doesn't mean that using ‘file[5]’ to randomly access the
sixth element will work, though it really should.

In Python 2.2, iteration can be implemented separately, and *note
__getitem__(): 266. methods can be limited to classes that really do
support random access.  The basic idea of iterators is simple.  A new
built-in function, ‘iter(obj)’ or ‘iter(C, sentinel)’, is used to get an
iterator.  ‘iter(obj)’ returns an iterator for the object 'obj', while
‘iter(C, sentinel)’ returns an iterator that will invoke the callable
object 'C' until it returns 'sentinel' to signal that the iterator is
done.

Python classes can define an ‘__iter__()’ method, which should create
and return a new iterator for the object; if the object is its own
iterator, this method can just return ‘self’.  In particular, iterators
will usually be their own iterators.  Extension types implemented in C
can implement a *note tp_iter: 145c. function in order to return an
iterator, and extension types that want to behave as iterators can
define a *note tp_iternext: 145d. function.

So, after all this, what do iterators actually do?  They have one
required method, *note next(): 77c, which takes no arguments and returns
the next value.  When there are no more values to be returned, calling
*note next(): 77c. should raise the *note StopIteration: ba1. exception.

     >>> L = [1,2,3]
     >>> i = iter(L)
     >>> print i
     <iterator object at 0x8116870>
     >>> i.next()
     1
     >>> i.next()
     2
     >>> i.next()
     3
     >>> i.next()
     Traceback (most recent call last):
       File "<stdin>", line 1, in ?
     StopIteration
     >>>

In 2.2, Python's *note for: 2c3. statement no longer expects a sequence;
it expects something for which *note iter(): 77b. will return an
iterator.  For backward compatibility and convenience, an iterator is
automatically constructed for sequences that don't implement
‘__iter__()’ or a *note tp_iter: 145c. slot, so ‘for i in [1,2,3]’ will
still work.  Wherever the Python interpreter loops over a sequence, it's
been changed to use the iterator protocol.  This means you can do things
like this:

     >>> L = [1,2,3]
     >>> i = iter(L)
     >>> a,b,c = i
     >>> a,b,c
     (1, 2, 3)

Iterator support has been added to some of Python's basic types.
Calling *note iter(): 77b. on a dictionary will return an iterator which
loops over its keys:

     >>> m = {'Jan': 1, 'Feb': 2, 'Mar': 3, 'Apr': 4, 'May': 5, 'Jun': 6,
     ...      'Jul': 7, 'Aug': 8, 'Sep': 9, 'Oct': 10, 'Nov': 11, 'Dec': 12}
     >>> for key in m: print key, m[key]
     ...
     Mar 3
     Feb 2
     Aug 8
     Sep 9
     May 5
     Jun 6
     Jul 7
     Jan 1
     Apr 4
     Nov 11
     Dec 12
     Oct 10

That's just the default behaviour.  If you want to iterate over keys,
values, or key/value pairs, you can explicitly call the ‘iterkeys()’,
‘itervalues()’, or ‘iteritems()’ methods to get an appropriate iterator.
In a minor related change, the *note in: 2c5. operator now works on
dictionaries, so ‘key in dict’ is now equivalent to ‘dict.has_key(key)’.

Files also provide an iterator, which calls the *note readline(): a8.
method until there are no more lines in the file.  This means you can
now read each line of a file using code like this:

     for line in file:
         # do something for each line
         ...

Note that you can only go forward in an iterator; there's no way to get
the previous element, reset the iterator, or make a copy of it.  An
iterator object could provide such additional capabilities, but the
iterator protocol only requires a *note next(): 77c. method.

也參考
......

PEP 234(1) - 疊代器

     由 Ka-Ping Yee 和 GvR 撰寫；由 Python Labs 團隊實作，主要為 GvR 和
     Tim Peters 所貢獻。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0234/


File: python.info,  Node: PEP 255 Simple Generators<2>,  Next: PEP 237 Unifying Long Integers and Integers<2>,  Prev: PEP 234：疊代器,  Up: Python 2 2 有什麼新功能

1.20.4 PEP 255: Simple Generators
---------------------------------

Generators are another new feature, one that interacts with the
introduction of iterators.

You're doubtless familiar with how function calls work in Python or C.
When you call a function, it gets a private namespace where its local
variables are created.  When the function reaches a *note return: 972.
statement, the local variables are destroyed and the resulting value is
returned to the caller.  A later call to the same function will get a
fresh new set of local variables.  But, what if the local variables
weren't thrown away on exiting a function?  What if you could later
resume the function where it left off?  This is what generators provide;
they can be thought of as resumable functions.

Here's the simplest example of a generator function:

     def generate_ints(N):
         for i in range(N):
             yield i

A new keyword, *note yield: 971, was introduced for generators.  Any
function containing a ‘yield’ statement is a generator function; this is
detected by Python's bytecode compiler which compiles the function
specially as a result.  Because a new keyword was introduced, generators
must be explicitly enabled in a module by including a ‘from __future__
import generators’ statement near the top of the module's source code.
In Python 2.3 this statement will become unnecessary.

When you call a generator function, it doesn't return a single value;
instead it returns a generator object that supports the iterator
protocol.  On executing the *note yield: 971. statement, the generator
outputs the value of ‘i’, similar to a *note return: 972. statement.
The big difference between ‘yield’ and a ‘return’ statement is that on
reaching a ‘yield’ the generator's state of execution is suspended and
local variables are preserved.  On the next call to the generator's
‘next()’ method, the function will resume executing immediately after
the ‘yield’ statement.  (For complicated reasons, the ‘yield’ statement
isn't allowed inside the ‘try’ block of a *note try: 68c...*note
finally: 96e. statement; read PEP 255(1) for a full explanation of the
interaction between ‘yield’ and exceptions.)

Here's a sample usage of the ‘generate_ints()’ generator:

     >>> gen = generate_ints(3)
     >>> gen
     <generator object at 0x8117f90>
     >>> gen.next()
     0
     >>> gen.next()
     1
     >>> gen.next()
     2
     >>> gen.next()
     Traceback (most recent call last):
       File "<stdin>", line 1, in ?
       File "<stdin>", line 2, in generate_ints
     StopIteration

You could equally write ‘for i in generate_ints(5)’, or ‘a,b,c =
generate_ints(3)’.

Inside a generator function, the *note return: 972. statement can only
be used without a value, and signals the end of the procession of
values; afterwards the generator cannot return any further values.
‘return’ with a value, such as ‘return 5’, is a syntax error inside a
generator function.  The end of the generator's results can also be
indicated by raising *note StopIteration: ba1. manually, or by just
letting the flow of execution fall off the bottom of the function.

You could achieve the effect of generators manually by writing your own
class and storing all the local variables of the generator as instance
variables.  For example, returning a list of integers could be done by
setting ‘self.count’ to 0, and having the *note next(): 77c. method
increment ‘self.count’ and return it.  However, for a moderately
complicated generator, writing a corresponding class would be much
messier.  ‘Lib/test/test_generators.py’ contains a number of more
interesting examples.  The simplest one implements an in-order traversal
of a tree using generators recursively.

     # A recursive generator that generates Tree leaves in in-order.
     def inorder(t):
         if t:
             for x in inorder(t.left):
                 yield x
             yield t.label
             for x in inorder(t.right):
                 yield x

Two other examples in ‘Lib/test/test_generators.py’ produce solutions
for the N-Queens problem (placing $N$ queens on an $NxN$ chess board so
that no queen threatens another) and the Knight's Tour (a route that
takes a knight to every square of an $NxN$ chessboard without visiting
any square twice).

The idea of generators comes from other programming languages,
especially Icon (‘https://www2.cs.arizona.edu/icon/’), where the idea of
generators is central.  In Icon, every expression and function call
behaves like a generator.  One example from "An Overview of the Icon
Programming Language" at
‘https://www2.cs.arizona.edu/icon/docs/ipd266.htm’ gives an idea of what
this looks like:

     sentence := "Store it in the neighboring harbor"
     if (i := find("or", sentence)) > 5 then write(i)

In Icon the ‘find()’ function returns the indexes at which the substring
"or" is found: 3, 23, 33.  In the *note if: 2c4. statement, ‘i’ is first
assigned a value of 3, but 3 is less than 5, so the comparison fails,
and Icon retries it with the second value of 23.  23 is greater than 5,
so the comparison now succeeds, and the code prints the value 23 to the
screen.

Python doesn't go nearly as far as Icon in adopting generators as a
central concept.  Generators are considered a new part of the core
Python language, but learning or using them isn't compulsory; if they
don't solve any problems that you have, feel free to ignore them.  One
novel feature of Python's interface as compared to Icon's is that a
generator's state is represented as a concrete object (the iterator)
that can be passed around to other functions or stored in a data
structure.

也參考
......

PEP 255(2) - Simple Generators

     Written by Neil Schemenauer, Tim Peters, Magnus Lie Hetland.
     Implemented mostly by Neil Schemenauer and Tim Peters, with other
     fixes from the Python Labs crew.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0255/

   (2) https://peps.python.org/pep-0255/


File: python.info,  Node: PEP 237 Unifying Long Integers and Integers<2>,  Next: PEP 238 Changing the Division Operator,  Prev: PEP 255 Simple Generators<2>,  Up: Python 2 2 有什麼新功能

1.20.5 PEP 237: Unifying Long Integers and Integers
---------------------------------------------------

In recent versions, the distinction between regular integers, which are
32-bit values on most machines, and long integers, which can be of
arbitrary size, was becoming an annoyance.  For example, on platforms
that support files larger than ‘2**32’ bytes, the ‘tell()’ method of
file objects has to return a long integer.  However, there were various
bits of Python that expected plain integers and would raise an error if
a long integer was provided instead.  For example, in Python 1.5, only
regular integers could be used as a slice index, and ‘'abc'[1L:]’ would
raise a *note TypeError: 4dd. exception with the message 'slice index
must be int'.

Python 2.2 will shift values from short to long integers as required.
The 'L' suffix is no longer needed to indicate a long integer literal,
as now the compiler will choose the appropriate type.  (Using the 'L'
suffix will be discouraged in future 2.x versions of Python, triggering
a warning in Python 2.4, and probably dropped in Python 3.0.)  Many
operations that used to raise an *note OverflowError: 825. will now
return a long integer as their result.  For example:

     >>> 1234567890123
     1234567890123L
     >>> 2 ** 64
     18446744073709551616L

In most cases, integers and long integers will now be treated
identically.  You can still distinguish them with the *note type(): cef.
built-in function, but that's rarely needed.

也參考
......

PEP 237(1) - Unifying Long Integers and Integers

     Written by Moshe Zadka and Guido van Rossum.  Implemented mostly by
     Guido van Rossum.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0237/


File: python.info,  Node: PEP 238 Changing the Division Operator,  Next: Unicode 變更,  Prev: PEP 237 Unifying Long Integers and Integers<2>,  Up: Python 2 2 有什麼新功能

1.20.6 PEP 238: Changing the Division Operator
----------------------------------------------

The most controversial change in Python 2.2 heralds the start of an
effort to fix an old design flaw that's been in Python from the
beginning.  Currently Python's division operator, ‘/’, behaves like C's
division operator when presented with two integer arguments: it returns
an integer result that's truncated down when there would be a fractional
part.  For example, ‘3/2’ is 1, not 1.5, and ‘(-1)/2’ is -1, not -0.5.
This means that the results of division can vary unexpectedly depending
on the type of the two operands and because Python is dynamically typed,
it can be difficult to determine the possible types of the operands.

(The controversy is over whether this is 'really' a design flaw, and
whether it's worth breaking existing code to fix this.  It's caused
endless discussions on python-dev, and in July 2001 erupted into a storm
of acidly sarcastic postings on ‘comp.lang.python’.  I won't argue for
either side here and will stick to describing what's implemented in 2.2.
Read PEP 238(1) for a summary of arguments and counter-arguments.)

Because this change might break code, it's being introduced very
gradually.  Python 2.2 begins the transition, but the switch won't be
complete until Python 3.0.

First, I'll borrow some terminology from PEP 238(2).  "True division" is
the division that most non-programmers are familiar with: 3/2 is 1.5,
1/4 is 0.25, and so forth.  "Floor division" is what Python's ‘/’
operator currently does when given integer operands; the result is the
floor of the value returned by true division.  "Classic division" is the
current mixed behaviour of ‘/’; it returns the result of floor division
when the operands are integers, and returns the result of true division
when one of the operands is a floating-point number.

Here are the changes 2.2 introduces:

   * A new operator, ‘//’, is the floor division operator.  (Yes, we
     know it looks like C++'s comment symbol.)  ‘//’ 'always' performs
     floor division no matter what the types of its operands are, so ‘1
     // 2’ is 0 and ‘1.0 // 2.0’ is also 0.0.

     ‘//’ is always available in Python 2.2; you don't need to enable it
     using a ‘__future__’ statement.

   * By including a ‘from __future__ import division’ in a module, the
     ‘/’ operator will be changed to return the result of true division,
     so ‘1/2’ is 0.5.  Without the ‘__future__’ statement, ‘/’ still
     means classic division.  The default meaning of ‘/’ will not change
     until Python 3.0.

   * Classes can define methods called *note __truediv__(): 1461. and
     *note __floordiv__(): 1462. to overload the two division operators.
     At the C level, there are also slots in the *note PyNumberMethods:
     138b. structure so extension types can define the two operators.

   * Python 2.2 supports some command-line arguments for testing whether
     code will work with the changed division semantics.  Running python
     with ‘-Q warn’ will cause a warning to be issued whenever division
     is applied to two integers.  You can use this to find code that's
     affected by the change and fix it.  By default, Python 2.2 will
     simply perform classic division without a warning; the warning will
     be turned on by default in Python 2.3.

也參考
......

PEP 238(3) - Changing the Division Operator

     Written by Moshe Zadka and Guido van Rossum.  Implemented by Guido
     van Rossum..

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0238/

   (2) https://peps.python.org/pep-0238/

   (3) https://peps.python.org/pep-0238/


File: python.info,  Node: Unicode 變更,  Next: PEP 227 Nested Scopes,  Prev: PEP 238 Changing the Division Operator,  Up: Python 2 2 有什麼新功能

1.20.7 Unicode 變更
-------------------

Python's Unicode support has been enhanced a bit in 2.2.  Unicode
strings are usually stored as UCS-2, as 16-bit unsigned integers.
Python 2.2 can also be compiled to use UCS-4, 32-bit unsigned integers,
as its internal encoding by supplying ‘--enable-unicode=ucs4’ to the
configure script.  (It's also possible to specify ‘--disable-unicode’ to
completely disable Unicode support.)

When built to use UCS-4 (a "wide Python"), the interpreter can natively
handle Unicode characters from U+000000 to U+110000, so the range of
legal values for the ‘unichr()’ function is expanded accordingly.  Using
an interpreter compiled to use UCS-2 (a "narrow Python"), values greater
than 65535 will still cause ‘unichr()’ to raise a *note ValueError: 1e7.
exception.  This is all described in PEP 261(1), "Support for 'wide'
Unicode characters"; consult it for further details.

Another change is simpler to explain.  Since their introduction, Unicode
strings have supported an ‘encode()’ method to convert the string to a
selected encoding such as UTF-8 or Latin-1.  A symmetric
‘decode([*encoding*])’ method has been added to 8-bit strings (though
not to Unicode strings) in 2.2.  ‘decode()’ assumes that the string is
in the specified encoding and decodes it, returning whatever is returned
by the codec.

Using this new feature, codecs have been added for tasks not directly
related to Unicode.  For example, codecs have been added for
uu-encoding, MIME's base64 encoding, and compression with the *note
zlib: 119. module:

     >>> s = """Here is a lengthy piece of redundant, overly verbose,
     ... and repetitive text.
     ... """
     >>> data = s.encode('zlib')
     >>> data
     'x\x9c\r\xc9\xc1\r\x80 \x10\x04\xc0?Ul...'
     >>> data.decode('zlib')
     'Here is a lengthy piece of redundant, overly verbose,\nand repetitive text.\n'
     >>> print s.encode('uu')
     begin 666 <data>
     M2&5R92!I<R!A(&QE;F=T:'D@<&EE8V4@;V8@<F5D=6YD86YT+"!O=F5R;'D@
     >=F5R8F]S92P*86YD(')E<&5T:71I=F4@=&5X="X*

     end
     >>> "sheesh".encode('rot-13')
     'furrfu'

To convert a class instance to Unicode, a ‘__unicode__()’ method can be
defined by a class, analogous to ‘__str__()’.

‘encode()’, ‘decode()’, and ‘__unicode__()’ were implemented by
Marc-André Lemburg.  The changes to support using UCS-4 internally were
implemented by Fredrik Lundh and Martin von Löwis.

也參考
......

PEP 261(2) - 支援 'wide' Unicode 字元

     由 Paul Prescod 撰寫。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0261/

   (2) https://peps.python.org/pep-0261/


File: python.info,  Node: PEP 227 Nested Scopes,  Next: New and Improved Modules<3>,  Prev: Unicode 變更,  Up: Python 2 2 有什麼新功能

1.20.8 PEP 227: Nested Scopes
-----------------------------

In Python 2.1, statically nested scopes were added as an optional
feature, to be enabled by a ‘from __future__ import nested_scopes’
directive.  In 2.2 nested scopes no longer need to be specially enabled,
and are now always present.  The rest of this section is a copy of the
description of nested scopes from my "What's New in Python 2.1"
document; if you read it when 2.1 came out, you can skip the rest of
this section.

The largest change introduced in Python 2.1, and made complete in 2.2,
is to Python's scoping rules.  In Python 2.0, at any given time there
are at most three namespaces used to look up variable names: local,
module-level, and the built-in namespace.  This often surprised people
because it didn't match their intuitive expectations.  For example, a
nested recursive function definition doesn't work:

     def f():
         ...
         def g(value):
             ...
             return g(value-1) + 1
         ...

The function ‘g()’ will always raise a *note NameError: 3e5. exception,
because the binding of the name ‘g’ isn't in either its local namespace
or in the module-level namespace.  This isn't much of a problem in
practice (how often do you recursively define interior functions like
this?), but this also made using the *note lambda: 1234. expression
clumsier, and this was a problem in practice.  In code which uses
‘lambda’ you can often find local variables being copied by passing them
as the default values of arguments.

     def find(self, name):
         "Return list of any entries equal to 'name'"
         L = filter(lambda x, name=name: x == name,
                    self.list_attribute)
         return L

The readability of Python code written in a strongly functional style
suffers greatly as a result.

The most significant change to Python 2.2 is that static scoping has
been added to the language to fix this problem.  As a first effect, the
‘name=name’ default argument is now unnecessary in the above example.
Put simply, when a given variable name is not assigned a value within a
function (by an assignment, or the *note def: 13c5, *note class: 126a,
or *note import: 586. statements), references to the variable will be
looked up in the local namespace of the enclosing scope.  A more
detailed explanation of the rules, and a dissection of the
implementation, can be found in the PEP.

This change may cause some compatibility problems for code where the
same variable name is used both at the module level and as a local
variable within a function that contains further function definitions.
This seems rather unlikely though, since such code would have been
pretty confusing to read in the first place.

One side effect of the change is that the ‘from module import *’ and
‘exec’ statements have been made illegal inside a function scope under
certain conditions.  The Python reference manual has said all along that
‘from module import *’ is only legal at the top level of a module, but
the CPython interpreter has never enforced this before.  As part of the
implementation of nested scopes, the compiler which turns Python source
into bytecodes has to generate different code to access variables in a
containing scope.  ‘from module import *’ and ‘exec’ make it impossible
for the compiler to figure this out, because they add names to the local
namespace that are unknowable at compile time.  Therefore, if a function
contains function definitions or *note lambda: 1234. expressions with
free variables, the compiler will flag this by raising a *note
SyntaxError: 173. exception.

To make the preceding explanation a bit clearer, here's an example:

     x = 1
     def f():
         # The next line is a syntax error
         exec 'x=2'
         def g():
             return x

Line 4 containing the ‘exec’ statement is a syntax error, since ‘exec’
would define a new local variable named ‘x’ whose value should be
accessed by ‘g()’.

This shouldn't be much of a limitation, since ‘exec’ is rarely used in
most Python code (and when it is used, it's often a sign of a poor
design anyway).

也參考
......

PEP 227(1) - Statically Nested Scopes

     Written and implemented by Jeremy Hylton.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0227/


File: python.info,  Node: New and Improved Modules<3>,  Next: 直譯器的變更與修正,  Prev: PEP 227 Nested Scopes,  Up: Python 2 2 有什麼新功能

1.20.9 New and Improved Modules
-------------------------------

   * The *note xmlrpclib: 114. module was contributed to the standard
     library by Fredrik Lundh, providing support for writing XML-RPC
     clients.  XML-RPC is a simple remote procedure call protocol built
     on top of HTTP and XML. For example, the following snippet
     retrieves a list of RSS channels from the O'Reilly Network, and
     then lists the recent headlines for one channel:

          import xmlrpclib
          s = xmlrpclib.Server(
                'http://www.oreillynet.com/meerkat/xml-rpc/server.php')
          channels = s.meerkat.getChannels()
          # channels is a list of dictionaries, like this:
          # [{'id': 4, 'title': 'Freshmeat Daily News'}
          #  {'id': 190, 'title': '32Bits Online'},
          #  {'id': 4549, 'title': '3DGamers'}, ... ]

          # Get the items for one channel
          items = s.meerkat.getItems( {'channel': 4} )

          # 'items' is another list of dictionaries, like this:
          # [{'link': 'http://freshmeat.net/releases/52719/',
          #   'description': 'A utility which converts HTML to XSL FO.',
          #   'title': 'html2fo 0.3 (Default)'}, ... ]

     The *note SimpleXMLRPCServer: 115. module makes it easy to create
     straightforward XML-RPC servers.  See
     ‘http://xmlrpc.scripting.com/’ for more information about XML-RPC.

   * The new *note hmac: 60. module implements the HMAC algorithm
     described by RFC 2104(1).  (Contributed by Gerhard Häring.)

   * Several functions that originally returned lengthy tuples now
     return pseudo-sequences that still behave like tuples but also have
     mnemonic attributes such as ‘memberst_mtime’ or *note tm_year:
     1466.  The enhanced functions include *note stat(): 448, *note
     fstat(): d32, *note statvfs(): 1094, and *note fstatvfs(): d33. in
     the *note os: 91. module, and *note localtime(): 1467, *note
     gmtime(): 1158, and *note strptime(): 139a. in the *note time: d7.
     module.

     For example, to obtain a file's size using the old tuples, you'd
     end up writing something like ‘file_size =
     os.stat(filename)[stat.ST_SIZE]’, but now this can be written more
     clearly as ‘file_size = os.stat(filename).st_size’.

     The original patch for this feature was contributed by Nick
     Mathewson.

   * The Python profiler has been extensively reworked and various
     errors in its output have been corrected.  (Contributed by Fred L.
     Drake, Jr.  and Tim Peters.)

   * The *note socket: b8. module can be compiled to support IPv6;
     specify the ‘--enable-ipv6’ option to Python's configure script.
     (Contributed by Jun-ichiro "itojun" Hagino.)

   * Two new format characters were added to the *note struct: c0.
     module for 64-bit integers on platforms that support the C long
     long type.  ‘q’ is for a signed 64-bit integer, and ‘Q’ is for an
     unsigned one.  The value is returned in Python's long integer type.
     (Contributed by Tim Peters.)

   * In the interpreter's interactive mode, there's a new built-in
     function *note help(): 87c. that uses the *note pydoc: a3. module
     introduced in Python 2.1 to provide interactive help.
     ‘help(object)’ displays any available help text about 'object'.
     *note help(): 87c. with no argument puts you in an online help
     utility, where you can enter the names of functions, classes, or
     modules to read their help text.  (Contributed by Guido van Rossum,
     using Ka-Ping Yee's *note pydoc: a3. module.)

   * Various bugfixes and performance improvements have been made to the
     SRE engine underlying the *note re: a7. module.  For example, the
     *note re.sub(): 283. and *note re.split(): 282. functions have been
     rewritten in C. Another contributed patch speeds up certain Unicode
     character ranges by a factor of two, and a new *note finditer():
     1468. method that returns an iterator over all the non-overlapping
     matches in a given string.  (SRE is maintained by Fredrik Lundh.
     The BIGCHARSET patch was contributed by Martin von Löwis.)

   * The *note smtplib: b7. module now supports RFC 2487(2), "Secure
     SMTP over TLS", so it's now possible to encrypt the SMTP traffic
     between a Python program and the mail transport agent being handed
     a message.  *note smtplib: b7. also supports SMTP authentication.
     (Contributed by Gerhard Häring.)

   * The *note imaplib: 6a. module, maintained by Piers Lauder, has
     support for several new extensions: the NAMESPACE extension defined
     in RFC 2342(3), SORT, GETACL and SETACL. (Contributed by Anthony
     Baxter and Michel Pelletier.)

   * The ‘rfc822’ module's parsing of email addresses is now compliant
     with RFC 2822(4), an update to RFC 822(5).  (The module's name is
     'not' going to be changed to ‘rfc2822’.)  A new package, *note
     email: 32, has also been added for parsing and generating e-mail
     messages.  (Contributed by Barry Warsaw, and arising out of his
     work on Mailman.)

   * The *note difflib: 2f. module now contains a new ‘Differ’ class for
     producing human-readable lists of changes (a "delta") between two
     sequences of lines of text.  There are also two generator
     functions, ‘ndiff()’ and ‘restore()’, which respectively return a
     delta from two sequences, or one of the original sequences from a
     delta.  (Grunt work contributed by David Goodger, from ndiff.py
     code by Tim Peters who then did the generatorization.)

   * New constants ‘ascii_letters’, ‘ascii_lowercase’, and
     ‘ascii_uppercase’ were added to the *note string: be. module.
     There were several modules in the standard library that used
     ‘string.letters’ to mean the ranges A-Za-z, but that assumption is
     incorrect when locales are in use, because ‘string.letters’ varies
     depending on the set of legal characters defined by the current
     locale.  The buggy modules have all been fixed to use
     ‘ascii_letters’ instead.  (Reported by an unknown person; fixed by
     Fred L. Drake, Jr.)

   * The *note mimetypes: 82. module now makes it easier to use
     alternative MIME-type databases by the addition of a *note
     MimeTypes: 1469. class, which takes a list of filenames to be
     parsed.  (Contributed by Fred L. Drake, Jr.)

   * A *note Timer: 10f2. class was added to the *note threading: d6.
     module that allows scheduling an activity to happen at some future
     time.  (Contributed by Itamar Shtull-Trauring.)

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2104.html

   (2) https://datatracker.ietf.org/doc/html/rfc2487.html

   (3) https://datatracker.ietf.org/doc/html/rfc2342.html

   (4) https://datatracker.ietf.org/doc/html/rfc2822.html

   (5) https://datatracker.ietf.org/doc/html/rfc822.html


File: python.info,  Node: 直譯器的變更與修正,  Next: 其他改動與修正,  Prev: New and Improved Modules<3>,  Up: Python 2 2 有什麼新功能

1.20.10 直譯器的變更與修正
--------------------------

Some of the changes only affect people who deal with the Python
interpreter at the C level because they're writing Python extension
modules, embedding the interpreter, or just hacking on the interpreter
itself.  If you only write Python code, none of the changes described
here will affect you very much.

   * Profiling and tracing functions can now be implemented in C, which
     can operate at much higher speeds than Python-based functions and
     should reduce the overhead of profiling and tracing.  This will be
     of interest to authors of development environments for Python.  Two
     new C functions were added to Python's API, *note
     PyEval_SetProfile(): 146b. and *note PyEval_SetTrace(): 146c.  The
     existing *note sys.setprofile(): 146d. and *note sys.settrace():
     146e. functions still exist, and have simply been changed to use
     the new C-level interface.  (Contributed by Fred L. Drake, Jr.)

   * Another low-level API, primarily of interest to implementers of
     Python debuggers and development tools, was added.  *note
     PyInterpreterState_Head(): 146f. and *note
     PyInterpreterState_Next(): 1470. let a caller walk through all the
     existing interpreter objects; *note
     PyInterpreterState_ThreadHead(): 1471. and *note
     PyThreadState_Next(): 1472. allow looping over all the thread
     states for a given interpreter.  (Contributed by David Beazley.)

   * The C-level interface to the garbage collector has been changed to
     make it easier to write extension types that support garbage
     collection and to debug misuses of the functions.  Various
     functions have slightly different semantics, so a bunch of
     functions had to be renamed.  Extensions that use the old API will
     still compile but will 'not' participate in garbage collection, so
     updating them for 2.2 should be considered fairly high priority.

     To upgrade an extension module to the new API, perform the
     following steps:

   * 將 ‘Py_TPFLAGS_GC’ 重新命名為 *note Py_TPFLAGS_HAVE_GC: 720.。

   * 
     Use *note PyObject_GC_New(): a45. or *note PyObject_GC_NewVar(): a46. to allocate

          objects, and *note PyObject_GC_Del(): 1473. to deallocate
          them.

   * Rename ‘PyObject_GC_Init()’ to *note PyObject_GC_Track(): 1474. and
     ‘PyObject_GC_Fini()’ to *note PyObject_GC_UnTrack(): 1475.

   * Remove ‘PyGC_HEAD_SIZE’ from object size calculations.

   * Remove calls to ‘PyObject_AS_GC()’ and ‘PyObject_FROM_GC()’.

   * A new ‘et’ format sequence was added to *note PyArg_ParseTuple():
     517.; ‘et’ takes both a parameter and an encoding name, and
     converts the parameter to the given encoding if the parameter turns
     out to be a Unicode string, or leaves it alone if it's an 8-bit
     string, assuming it to already be in the desired encoding.  This
     differs from the ‘es’ format character, which assumes that 8-bit
     strings are in Python's default ASCII encoding and converts them to
     the specified new encoding.  (Contributed by M.-A. Lemburg, and
     used for the MBCS support on Windows described in the following
     section.)

   * A different argument parsing function, *note PyArg_UnpackTuple():
     1476, has been added that's simpler and presumably faster.  Instead
     of specifying a format string, the caller simply gives the minimum
     and maximum number of arguments expected, and a set of pointers to
     *note PyObject: 311.* variables that will be filled in with
     argument values.

   * Two new flags *note METH_NOARGS: 1443. and *note METH_O: 1477. are
     available in method definition tables to simplify implementation of
     methods with no arguments or a single untyped argument.  Calling
     such methods is more efficient than calling a corresponding method
     that uses *note METH_VARARGS: 1478.  Also, the old ‘METH_OLDARGS’
     style of writing C methods is now officially deprecated.

   * Two new wrapper functions, *note PyOS_snprintf(): 1479. and *note
     PyOS_vsnprintf(): 147a. were added to provide cross-platform
     implementations for the relatively new ‘snprintf()’ and
     ‘vsnprintf()’ C lib APIs.  In contrast to the standard ‘sprintf()’
     and ‘vsprintf()’ functions, the Python versions check the bounds of
     the buffer used to protect against buffer overruns.  (Contributed
     by M.-A. Lemburg.)

   * The *note _PyTuple_Resize(): 147b. function has lost an unused
     parameter, so now it takes 2 parameters instead of 3.  The third
     argument was never used, and can simply be discarded when porting
     code from earlier versions to Python 2.2.


File: python.info,  Node: 其他改動與修正,  Next: 致謝<6>,  Prev: 直譯器的變更與修正,  Up: Python 2 2 有什麼新功能

1.20.11 其他改動與修正
----------------------

As usual there were a bunch of other improvements and bugfixes scattered
throughout the source tree.  A search through the CVS change logs finds
there were 527 patches applied and 683 bugs fixed between Python 2.1 and
2.2; 2.2.1 applied 139 patches and fixed 143 bugs; 2.2.2 applied 106
patches and fixed 82 bugs.  These figures are likely to be
underestimates.

一些較顯著的變更為：

   * The code for the MacOS port for Python, maintained by Jack Jansen,
     is now kept in the main Python CVS tree, and many changes have been
     made to support MacOS X.

     The most significant change is the ability to build Python as a
     framework, enabled by supplying the ‘--enable-framework’ option to
     the configure script when compiling Python.  According to Jack
     Jansen, "This installs a self-contained Python installation plus
     the OS X framework "glue" into
     ‘/Library/Frameworks/Python.framework’ (or another location of
     choice).  For now there is little immediate added benefit to this
     (actually, there is the disadvantage that you have to change your
     PATH to be able to find Python), but it is the basis for creating a
     full-blown Python application, porting the MacPython IDE, possibly
     using Python as a standard OSA scripting language and much more."

     Most of the MacPython toolbox modules, which interface to MacOS
     APIs such as windowing, QuickTime, scripting, etc.  have been
     ported to OS X, but they've been left commented out in ‘setup.py’.
     People who want to experiment with these modules can uncomment them
     manually.

   * Keyword arguments passed to built-in functions that don't take them
     now cause a *note TypeError: 4dd. exception to be raised, with the
     message "'function' takes no keyword arguments".

   * Weak references, added in Python 2.1 as an extension module, are
     now part of the core because they're used in the implementation of
     new-style classes.  The *note ReferenceError: 147d. exception has
     therefore moved from the *note weakref: fc. module to become a
     built-in exception.

   * A new script, ‘Tools/scripts/cleanfuture.py’ by Tim Peters,
     automatically removes obsolete ‘__future__’ statements from Python
     source code.

   * An additional 'flags' argument has been added to the built-in
     function *note compile(): 178, so the behaviour of ‘__future__’
     statements can now be correctly observed in simulated shells, such
     as those presented by IDLE and other development environments.
     This is described in PEP 264(1).  (Contributed by Michael Hudson.)

   * The new license introduced with Python 1.6 wasn't GPL-compatible.
     This is fixed by some minor textual changes to the 2.2 license, so
     it's now legal to embed Python inside a GPLed program again.  Note
     that Python itself is not GPLed, but instead is under a license
     that's essentially equivalent to the BSD license, same as it always
     was.  The license changes were also applied to the Python 2.0.1 and
     2.1.1 releases.

   * When presented with a Unicode filename on Windows, Python will now
     convert it to an MBCS encoded string, as used by the Microsoft file
     APIs.  As MBCS is explicitly used by the file APIs, Python's choice
     of ASCII as the default encoding turns out to be an annoyance.  On
     Unix, the locale's character set is used if
     ‘locale.nl_langinfo(CODESET)’ is available.  (Windows support was
     contributed by Mark Hammond with assistance from Marc-André
     Lemburg.  Unix support was added by Martin von Löwis.)

   * Large file support is now enabled on Windows.  (Contributed by Tim
     Peters.)

   * The ‘Tools/scripts/ftpmirror.py’ script now parses a ‘.netrc’ file,
     if you have one.  (Contributed by Mike Romberg.)

   * Some features of the object returned by the ‘xrange()’ function are
     now deprecated, and trigger warnings when they're accessed; they'll
     disappear in Python 2.3.  ‘xrange’ objects tried to pretend they
     were full sequence types by supporting slicing, sequence
     multiplication, and the *note in: 2c5. operator, but these features
     were rarely used and therefore buggy.  The ‘tolist()’ method and
     the ‘start’, ‘stop’, and ‘step’ attributes are also being
     deprecated.  At the C level, the fourth argument to the
     ‘PyRange_New()’ function, ‘repeat’, has also been deprecated.

   * There were a bunch of patches to the dictionary implementation,
     mostly to fix potential core dumps if a dictionary contains objects
     that sneakily changed their hash value, or mutated the dictionary
     they were contained in.  For a while python-dev fell into a gentle
     rhythm of Michael Hudson finding a case that dumped core, Tim
     Peters fixing the bug, Michael finding another case, and round and
     round it went.

   * On Windows, Python can now be compiled with Borland C thanks to a
     number of patches contributed by Stephen Hansen, though the result
     isn't fully functional yet.  (But this 'is' progress...)

   * Another Windows enhancement: Wise Solutions generously offered
     PythonLabs use of their InstallerMaster 8.1 system.  Earlier
     PythonLabs Windows installers used Wise 5.0a, which was beginning
     to show its age.  (Packaged up by Tim Peters.)

   * Files ending in ‘.pyw’ can now be imported on Windows.  ‘.pyw’ is a
     Windows-only thing, used to indicate that a script needs to be run
     using PYTHONW.EXE instead of PYTHON.EXE in order to prevent a DOS
     console from popping up to display the output.  This patch makes it
     possible to import such scripts, in case they're also usable as
     modules.  (Implemented by David Bolen.)

   * On platforms where Python uses the C ‘dlopen()’ function to load
     extension modules, it's now possible to set the flags used by
     ‘dlopen()’ using the *note sys.getdlopenflags(): 147e. and *note
     sys.setdlopenflags(): 10b7. functions.  (Contributed by Bram
     Stolk.)

   * The *note pow(): 976. built-in function no longer supports 3
     arguments when floating-point numbers are supplied.  ‘pow(x, y, z)’
     returns ‘(x**y) % z’, but this is never useful for floating-point
     numbers, and the final result varies unpredictably depending on the
     platform.  A call such as ‘pow(2.0, 8.0, 7.0)’ will now raise a
     *note TypeError: 4dd. exception.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0264/


File: python.info,  Node: 致謝<6>,  Prev: 其他改動與修正,  Up: Python 2 2 有什麼新功能

1.20.12 致謝
------------

The author would like to thank the following people for offering
suggestions, corrections and assistance with various drafts of this
article: Fred Bremmer, Keith Briggs, Andrew Dalke, Fred L. Drake, Jr.,
Carel Fellinger, David Goodger, Mark Hammond, Stephen Hansen, Michael
Hudson, Jack Jansen, Marc-André Lemburg, Martin von Löwis, Fredrik
Lundh, Michael McLay, Nick Mathewson, Paul Moore, Gustavo Niemeyer, Don
O'Donnell, Joonas Paalasma, Tim Peters, Jens Quade, Tom Reinhardt, Neil
Schemenauer, Guido van Rossum, Greg Ward, Edward Welbourne.


File: python.info,  Node: Python 2 1 有什麼新功能,  Next: Python 2 0 有什麼新功能,  Prev: Python 2 2 有什麼新功能,  Up: Python 有什麼新功能？

1.21 Python 2.1 有什麼新功能
============================


作者: A.M. Kuchling

* Menu:

* 簡介: 簡介<2>.
* PEP 227; Nested Scopes: PEP 227 Nested Scopes<2>.
* PEP 236; __future__ Directives: PEP 236 __future__ Directives.
* PEP 207; Rich Comparisons: PEP 207 Rich Comparisons.
* PEP 230; Warning Framework: PEP 230 Warning Framework.
* PEP 229; New Build System: PEP 229 New Build System.
* PEP 205; Weak References: PEP 205 Weak References.
* PEP 232; Function Attributes: PEP 232 Function Attributes.
* PEP 235; Importing Modules on Case-Insensitive Platforms: PEP 235 Importing Modules on Case-Insensitive Platforms.
* PEP 217; Interactive Display Hook: PEP 217 Interactive Display Hook.
* PEP 208; New Coercion Model: PEP 208 New Coercion Model.
* PEP 241; Metadata in Python Packages: PEP 241 Metadata in Python Packages.
* New and Improved Modules: New and Improved Modules<4>.
* Other Changes and Fixes: Other Changes and Fixes<3>.
* 致謝: 致謝<7>.


File: python.info,  Node: 簡介<2>,  Next: PEP 227 Nested Scopes<2>,  Up: Python 2 1 有什麼新功能

1.21.1 簡介
-----------

This article explains the new features in Python 2.1.  While there
aren't as many changes in 2.1 as there were in Python 2.0, there are
still some pleasant surprises in store.  2.1 is the first release to be
steered through the use of Python Enhancement Proposals, or PEPs, so
most of the sizable changes have accompanying PEPs that provide more
complete documentation and a design rationale for the change.  This
article doesn't attempt to document the new features completely, but
simply provides an overview of the new features for Python programmers.
Refer to the Python 2.1 documentation, or to the specific PEP, for more
details about any new feature that particularly interests you.

One recent goal of the Python development team has been to accelerate
the pace of new releases, with a new release coming every 6 to 9 months.
2.1 is the first release to come out at this faster pace, with the first
alpha appearing in January, 3 months after the final version of 2.0 was
released.

The final release of Python 2.1 was made on April 17, 2001.


File: python.info,  Node: PEP 227 Nested Scopes<2>,  Next: PEP 236 __future__ Directives,  Prev: 簡介<2>,  Up: Python 2 1 有什麼新功能

1.21.2 PEP 227: Nested Scopes
-----------------------------

The largest change in Python 2.1 is to Python's scoping rules.  In
Python 2.0, at any given time there are at most three namespaces used to
look up variable names: local, module-level, and the built-in namespace.
This often surprised people because it didn't match their intuitive
expectations.  For example, a nested recursive function definition
doesn't work:

     def f():
         ...
         def g(value):
             ...
             return g(value-1) + 1
         ...

The function ‘g()’ will always raise a *note NameError: 3e5. exception,
because the binding of the name ‘g’ isn't in either its local namespace
or in the module-level namespace.  This isn't much of a problem in
practice (how often do you recursively define interior functions like
this?), but this also made using the *note lambda: 1234. expression
clumsier, and this was a problem in practice.  In code which uses *note
lambda: 1234. you can often find local variables being copied by passing
them as the default values of arguments.

     def find(self, name):
         "Return list of any entries equal to 'name'"
         L = filter(lambda x, name=name: x == name,
                    self.list_attribute)
         return L

The readability of Python code written in a strongly functional style
suffers greatly as a result.

The most significant change to Python 2.1 is that static scoping has
been added to the language to fix this problem.  As a first effect, the
‘name=name’ default argument is now unnecessary in the above example.
Put simply, when a given variable name is not assigned a value within a
function (by an assignment, or the *note def: 13c5, *note class: 126a,
or *note import: 586. statements), references to the variable will be
looked up in the local namespace of the enclosing scope.  A more
detailed explanation of the rules, and a dissection of the
implementation, can be found in the PEP.

This change may cause some compatibility problems for code where the
same variable name is used both at the module level and as a local
variable within a function that contains further function definitions.
This seems rather unlikely though, since such code would have been
pretty confusing to read in the first place.

One side effect of the change is that the ‘from module import *’ and
‘exec’ statements have been made illegal inside a function scope under
certain conditions.  The Python reference manual has said all along that
‘from module import *’ is only legal at the top level of a module, but
the CPython interpreter has never enforced this before.  As part of the
implementation of nested scopes, the compiler which turns Python source
into bytecodes has to generate different code to access variables in a
containing scope.  ‘from module import *’ and ‘exec’ make it impossible
for the compiler to figure this out, because they add names to the local
namespace that are unknowable at compile time.  Therefore, if a function
contains function definitions or *note lambda: 1234. expressions with
free variables, the compiler will flag this by raising a *note
SyntaxError: 173. exception.

To make the preceding explanation a bit clearer, here's an example:

     x = 1
     def f():
         # The next line is a syntax error
         exec 'x=2'
         def g():
             return x

Line 4 containing the ‘exec’ statement is a syntax error, since ‘exec’
would define a new local variable named ‘x’ whose value should be
accessed by ‘g()’.

This shouldn't be much of a limitation, since ‘exec’ is rarely used in
most Python code (and when it is used, it's often a sign of a poor
design anyway).

Compatibility concerns have led to nested scopes being introduced
gradually; in Python 2.1, they aren't enabled by default, but can be
turned on within a module by using a future statement as described in
PEP 236(1).  (See the following section for further discussion of PEP
236(2).)  In Python 2.2, nested scopes will become the default and there
will be no way to turn them off, but users will have had all of 2.1's
lifetime to fix any breakage resulting from their introduction.

也參考
......

PEP 227(3) - Statically Nested Scopes

     Written and implemented by Jeremy Hylton.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0236/

   (2) https://peps.python.org/pep-0236/

   (3) https://peps.python.org/pep-0227/


File: python.info,  Node: PEP 236 __future__ Directives,  Next: PEP 207 Rich Comparisons,  Prev: PEP 227 Nested Scopes<2>,  Up: Python 2 1 有什麼新功能

1.21.3 PEP 236: __future__ Directives
-------------------------------------

The reaction to nested scopes was widespread concern about the dangers
of breaking code with the 2.1 release, and it was strong enough to make
the Pythoneers take a more conservative approach.  This approach
consists of introducing a convention for enabling optional functionality
in release N that will become compulsory in release N+1.

The syntax uses a ‘from...import’ statement using the reserved module
name *note __future__: 0.  Nested scopes can be enabled by the following
statement:

     from __future__ import nested_scopes

While it looks like a normal *note import: 586. statement, it's not;
there are strict rules on where such a future statement can be put.
They can only be at the top of a module, and must precede any Python
code or regular ‘import’ statements.  This is because such statements
can affect how the Python bytecode compiler parses code and generates
bytecode, so they must precede any statement that will result in
bytecodes being produced.

也參考
......

PEP 236(1) - Back to the *note __future__: 0.

     Written by Tim Peters, and primarily implemented by Jeremy Hylton.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0236/


File: python.info,  Node: PEP 207 Rich Comparisons,  Next: PEP 230 Warning Framework,  Prev: PEP 236 __future__ Directives,  Up: Python 2 1 有什麼新功能

1.21.4 PEP 207: Rich Comparisons
--------------------------------

In earlier versions, Python's support for implementing comparisons on
user-defined classes and extension types was quite simple.  Classes
could implement a ‘__cmp__()’ method that was given two instances of a
class, and could only return 0 if they were equal or +1 or -1 if they
weren't; the method couldn't raise an exception or return anything other
than a Boolean value.  Users of Numeric Python often found this model
too weak and restrictive, because in the number-crunching programs that
numeric Python is used for, it would be more useful to be able to
perform elementwise comparisons of two matrices, returning a matrix
containing the results of a given comparison for each element.  If the
two matrices are of different sizes, then the compare has to be able to
raise an exception to signal the error.

In Python 2.1, rich comparisons were added in order to support this
need.  Python classes can now individually overload each of the ‘<’,
‘<=’, ‘>’, ‘>=’, ‘==’, and ‘!=’ operations.  The new magic method names
are:

操作            方法名稱
                
---------------------------------------------
                
‘<’             *note __lt__(): 129e.
                
                
‘<=’            *note __le__(): 129f.
                
                
‘>’             *note __gt__(): 12a0.
                
                
‘>=’            *note __ge__(): 12a1.
                
                
‘==’            *note __eq__(): a9d.
                
                
‘!=’            *note __ne__(): 1486.
                

(The magic methods are named after the corresponding Fortran operators
‘.LT.’.  ‘.LE.’, &c.  Numeric programmers are almost certainly quite
familiar with these names and will find them easy to remember.)

Each of these magic methods is of the form ‘method(self, other)’, where
‘self’ will be the object on the left-hand side of the operator, while
‘other’ will be the object on the right-hand side.  For example, the
expression ‘A < B’ will cause ‘A.__lt__(B)’ to be called.

Each of these magic methods can return anything at all: a Boolean, a
matrix, a list, or any other Python object.  Alternatively they can
raise an exception if the comparison is impossible, inconsistent, or
otherwise meaningless.

The built-in ‘cmp(A,B)’ function can use the rich comparison machinery,
and now accepts an optional argument specifying which comparison
operation to use; this is given as one of the strings ‘"<"’, ‘"<="’,
‘">"’, ‘">="’, ‘"=="’, or ‘"!="’.  If called without the optional third
argument, ‘cmp()’ will only return -1, 0, or +1 as in previous versions
of Python; otherwise it will call the appropriate method and can return
any Python object.

There are also corresponding changes of interest to C programmers;
there's a new slot ‘tp_richcmp’ in type objects and an API for
performing a given rich comparison.  I won't cover the C API here, but
will refer you to PEP 207(1), or to 2.1's C API documentation, for the
full list of related functions.

也參考
......

PEP 207(2) - Rich Comparisons

     Written by Guido van Rossum, heavily based on earlier work by David
     Ascher, and implemented by Guido van Rossum.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0207/

   (2) https://peps.python.org/pep-0207/


File: python.info,  Node: PEP 230 Warning Framework,  Next: PEP 229 New Build System,  Prev: PEP 207 Rich Comparisons,  Up: Python 2 1 有什麼新功能

1.21.5 PEP 230: Warning Framework
---------------------------------

Over its 10 years of existence, Python has accumulated a certain number
of obsolete modules and features along the way.  It's difficult to know
when a feature is safe to remove, since there's no way of knowing how
much code uses it -- perhaps no programs depend on the feature, or
perhaps many do.  To enable removing old features in a more structured
way, a warning framework was added.  When the Python developers want to
get rid of a feature, it will first trigger a warning in the next
version of Python.  The following Python version can then drop the
feature, and users will have had a full release cycle to remove uses of
the old feature.

Python 2.1 adds the warning framework to be used in this scheme.  It
adds a *note warnings: fa. module that provide functions to issue
warnings, and to filter out warnings that you don't want to be
displayed.  Third-party modules can also use this framework to deprecate
old features that they no longer wish to support.

For example, in Python 2.1 the ‘regex’ module is deprecated, so
importing it causes a warning to be printed:

     >>> import regex
     __main__:1: DeprecationWarning: the regex module
              is deprecated; please use the re module
     >>>

Warnings can be issued by calling the *note warnings.warn(): 1488.
function:

     warnings.warn("feature X no longer supported")

The first parameter is the warning message; an additional optional
parameters can be used to specify a particular warning category.

Filters can be added to disable certain warnings; a regular expression
pattern can be applied to the message or to the module name in order to
suppress a warning.  For example, you may have a program that uses the
‘regex’ module and not want to spare the time to convert it to use the
*note re: a7. module right now.  The warning can be suppressed by
calling

     import warnings
     warnings.filterwarnings(action = 'ignore',
                             message='.*regex module is deprecated',
                             category=DeprecationWarning,
                             module = '__main__')

This adds a filter that will apply only to warnings of the class *note
DeprecationWarning: 18b. triggered in the *note __main__: 1. module, and
applies a regular expression to only match the message about the ‘regex’
module being deprecated, and will cause such warnings to be ignored.
Warnings can also be printed only once, printed every time the offending
code is executed, or turned into exceptions that will cause the program
to stop (unless the exceptions are caught in the usual way, of course).

Functions were also added to Python's C API for issuing warnings; refer
to PEP 230 or to Python's API documentation for the details.

也參考
......

PEP 5(1) - Guidelines for Language Evolution

     Written by Paul Prescod, to specify procedures to be followed when
     removing old features from Python.  The policy described in this
     PEP hasn't been officially adopted, but the eventual policy
     probably won't be too different from Prescod's proposal.

PEP 230(2) - Warning Framework

     Written and implemented by Guido van Rossum.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0005/

   (2) https://peps.python.org/pep-0230/


File: python.info,  Node: PEP 229 New Build System,  Next: PEP 205 Weak References,  Prev: PEP 230 Warning Framework,  Up: Python 2 1 有什麼新功能

1.21.6 PEP 229: New Build System
--------------------------------

When compiling Python, the user had to go in and edit the
‘Modules/Setup’ file in order to enable various additional modules; the
default set is relatively small and limited to modules that compile on
most Unix platforms.  This means that on Unix platforms with many more
features, most notably Linux, Python installations often don't contain
all useful modules they could.

Python 2.0 added the Distutils, a set of modules for distributing and
installing extensions.  In Python 2.1, the Distutils are used to compile
much of the standard library of extension modules, autodetecting which
ones are supported on the current machine.  It's hoped that this will
make Python installations easier and more featureful.

Instead of having to edit the ‘Modules/Setup’ file in order to enable
modules, a ‘setup.py’ script in the top directory of the Python source
distribution is run at build time, and attempts to discover which
modules can be enabled by examining the modules and header files on the
system.  If a module is configured in ‘Modules/Setup’, the ‘setup.py’
script won't attempt to compile that module and will defer to the
‘Modules/Setup’ file's contents.  This provides a way to specific any
strange command-line flags or libraries that are required for a specific
platform.

In another far-reaching change to the build mechanism, Neil Schemenauer
restructured things so Python now uses a single makefile that isn't
recursive, instead of makefiles in the top directory and in each of the
‘Python/’, ‘Parser/’, ‘Objects/’, and ‘Modules/’ subdirectories.  This
makes building Python faster and also makes hacking the Makefiles
clearer and simpler.

也參考
......

PEP 229(1) - Using Distutils to Build Python

     Written and implemented by A.M. Kuchling.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0229/


File: python.info,  Node: PEP 205 Weak References,  Next: PEP 232 Function Attributes,  Prev: PEP 229 New Build System,  Up: Python 2 1 有什麼新功能

1.21.7 PEP 205: Weak References
-------------------------------

Weak references, available through the *note weakref: fc. module, are a
minor but useful new data type in the Python programmer's toolbox.

Storing a reference to an object (say, in a dictionary or a list) has
the side effect of keeping that object alive forever.  There are a few
specific cases where this behaviour is undesirable, object caches being
the most common one, and another being circular references in data
structures such as trees.

For example, consider a memoizing function that caches the results of
another function ‘f(x)’ by storing the function's argument and its
result in a dictionary:

     _cache = {}
     def memoize(x):
         if _cache.has_key(x):
             return _cache[x]

         retval = f(x)

         # Cache the returned object
         _cache[x] = retval

         return retval

This version works for simple things such as integers, but it has a side
effect; the ‘_cache’ dictionary holds a reference to the return values,
so they'll never be deallocated until the Python process exits and
cleans up.  This isn't very noticeable for integers, but if ‘f()’
returns an object, or a data structure that takes up a lot of memory,
this can be a problem.

Weak references provide a way to implement a cache that won't keep
objects alive beyond their time.  If an object is only accessible
through weak references, the object will be deallocated and the weak
references will now indicate that the object it referred to no longer
exists.  A weak reference to an object 'obj' is created by calling ‘wr =
weakref.ref(obj)’.  The object being referred to is returned by calling
the weak reference as if it were a function: ‘wr()’.  It will return the
referenced object, or ‘None’ if the object no longer exists.

This makes it possible to write a ‘memoize()’ function whose cache
doesn't keep objects alive, by storing weak references in the cache.

     _cache = {}
     def memoize(x):
         if _cache.has_key(x):
             obj = _cache[x]()
             # If weak reference object still exists,
             # return it
             if obj is not None: return obj

         retval = f(x)

         # Cache a weak reference
         _cache[x] = weakref.ref(retval)

         return retval

The *note weakref: fc. module also allows creating proxy objects which
behave like weak references -- an object referenced only by proxy
objects is deallocated - but instead of requiring an explicit call to
retrieve the object, the proxy transparently forwards all operations to
the object as long as the object still exists.  If the object is
deallocated, attempting to use a proxy will cause a
‘weakref.ReferenceError’ exception to be raised.

     proxy = weakref.proxy(obj)
     proxy.attr   # Equivalent to obj.attr
     proxy.meth() # Equivalent to obj.meth()
     del obj
     proxy.attr   # raises weakref.ReferenceError

也參考
......

PEP 205(1) - Weak References

     Written and implemented by Fred L. Drake, Jr.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0205/


File: python.info,  Node: PEP 232 Function Attributes,  Next: PEP 235 Importing Modules on Case-Insensitive Platforms,  Prev: PEP 205 Weak References,  Up: Python 2 1 有什麼新功能

1.21.8 PEP 232: Function Attributes
-----------------------------------

In Python 2.1, functions can now have arbitrary information attached to
them.  People were often using docstrings to hold information about
functions and methods, because the *note __doc__: 1171. attribute was
the only way of attaching any information to a function.  For example,
in the Zope web application server, functions are marked as safe for
public access by having a docstring, and in John Aycock's SPARK parsing
framework, docstrings hold parts of the BNF grammar to be parsed.  This
overloading is unfortunate, since docstrings are really intended to hold
a function's documentation; for example, it means you can't properly
document functions intended for private use in Zope.

Arbitrary attributes can now be set and retrieved on functions using the
regular Python syntax:

     def f(): pass

     f.publish = 1
     f.secure = 1
     f.grammar = "A ::= B (C D)*"

The dictionary containing attributes can be accessed as the function's
*note __dict__: c04.  Unlike the *note __dict__: c04. attribute of class
instances, in functions you can actually assign a new dictionary to
*note __dict__: c04, though the new value is restricted to a regular
Python dictionary; you 'can't' be tricky and set it to a ‘UserDict’
instance, or any other random object that behaves like a mapping.

也參考
......

PEP 232(1) - Function Attributes

     Written and implemented by Barry Warsaw.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0232/


File: python.info,  Node: PEP 235 Importing Modules on Case-Insensitive Platforms,  Next: PEP 217 Interactive Display Hook,  Prev: PEP 232 Function Attributes,  Up: Python 2 1 有什麼新功能

1.21.9 PEP 235: Importing Modules on Case-Insensitive Platforms
---------------------------------------------------------------

Some operating systems have filesystems that are case-insensitive, MacOS
and Windows being the primary examples; on these systems, it's
impossible to distinguish the filenames ‘FILE.PY’ and ‘file.py’, even
though they do store the file's name in its original case (they're
case-preserving, too).

In Python 2.1, the *note import: 586. statement will work to simulate
case-sensitivity on case-insensitive platforms.  Python will now search
for the first case-sensitive match by default, raising an *note
ImportError: 352. if no such file is found, so ‘import file’ will not
import a module named ‘FILE.PY’.  Case-insensitive matching can be
requested by setting the *note PYTHONCASEOK: 900. environment variable
before starting the Python interpreter.


File: python.info,  Node: PEP 217 Interactive Display Hook,  Next: PEP 208 New Coercion Model,  Prev: PEP 235 Importing Modules on Case-Insensitive Platforms,  Up: Python 2 1 有什麼新功能

1.21.10 PEP 217: Interactive Display Hook
-----------------------------------------

When using the Python interpreter interactively, the output of commands
is displayed using the built-in *note repr(): 7a1. function.  In Python
2.1, the variable *note sys.displayhook(): 148e. can be set to a
callable object which will be called instead of *note repr(): 7a1.  For
example, you can set it to a special pretty-printing function:

     >>> # Create a recursive data structure
     ... L = [1,2,3]
     >>> L.append(L)
     >>> L # Show Python's default output
     [1, 2, 3, [...]]
     >>> # Use pprint.pprint() as the display function
     ... import sys, pprint
     >>> sys.displayhook = pprint.pprint
     >>> L
     [1, 2, 3,  <Recursion on list with id=135143996>]
     >>>

也參考
......

PEP 217(1) - Display Hook for Interactive Use

     Written and implemented by Moshe Zadka.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0217/


File: python.info,  Node: PEP 208 New Coercion Model,  Next: PEP 241 Metadata in Python Packages,  Prev: PEP 217 Interactive Display Hook,  Up: Python 2 1 有什麼新功能

1.21.11 PEP 208: New Coercion Model
-----------------------------------

How numeric coercion is done at the C level was significantly modified.
This will only affect the authors of C extensions to Python, allowing
them more flexibility in writing extension types that support numeric
operations.

Extension types can now set the type flag ‘Py_TPFLAGS_CHECKTYPES’ in
their ‘PyTypeObject’ structure to indicate that they support the new
coercion model.  In such extension types, the numeric slot functions can
no longer assume that they'll be passed two arguments of the same type;
instead they may be passed two arguments of differing types, and can
then perform their own internal coercion.  If the slot function is
passed a type it can't handle, it can indicate the failure by returning
a reference to the ‘Py_NotImplemented’ singleton value.  The numeric
functions of the other type will then be tried, and perhaps they can
handle the operation; if the other type also returns
‘Py_NotImplemented’, then a *note TypeError: 4dd. will be raised.
Numeric methods written in Python can also return ‘Py_NotImplemented’,
causing the interpreter to act as if the method did not exist (perhaps
raising a *note TypeError: 4dd, perhaps trying another object's numeric
methods).

也參考
......

PEP 208(1) - Reworking the Coercion Model

     Written and implemented by Neil Schemenauer, heavily based upon
     earlier work by Marc-André Lemburg.  Read this to understand the
     fine points of how numeric operations will now be processed at the
     C level.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0208/


File: python.info,  Node: PEP 241 Metadata in Python Packages,  Next: New and Improved Modules<4>,  Prev: PEP 208 New Coercion Model,  Up: Python 2 1 有什麼新功能

1.21.12 PEP 241: Metadata in Python Packages
--------------------------------------------

A common complaint from Python users is that there's no single catalog
of all the Python modules in existence.  T. Middleton's Vaults of
Parnassus at ‘www.vex.net/parnassus/’ (retired in February 2009,
available in the Internet Archive Wayback Machine(1)) was the largest
catalog of Python modules, but registering software at the Vaults is
optional, and many people did not bother.

As a first small step toward fixing the problem, Python software
packaged using the Distutils ‘sdist’ command will include a file named
‘PKG-INFO’ containing information about the package such as its name,
version, and author (metadata, in cataloguing terminology).  PEP 241(2)
contains the full list of fields that can be present in the ‘PKG-INFO’
file.  As people began to package their software using Python 2.1, more
and more packages will include metadata, making it possible to build
automated cataloguing systems and experiment with them.  With the result
experience, perhaps it'll be possible to design a really good catalog
and then build support for it into Python 2.2.  For example, the
Distutils ‘sdist’ and ‘bdist_*’ commands could support an ‘upload’
option that would automatically upload your package to a catalog server.

You can start creating packages containing ‘PKG-INFO’ even if you're not
using Python 2.1, since a new release of the Distutils will be made for
users of earlier Python versions.  Version 1.0.2 of the Distutils
includes the changes described in PEP 241(3), as well as various
bugfixes and enhancements.  It will be available from the Distutils SIG
at ‘https://www.python.org/community/sigs/current/distutils-sig/’.

也參考
......

PEP 241(4) - Metadata for Python Software Packages

     Written and implemented by A.M. Kuchling.

PEP 243(5) - Module Repository Upload Mechanism

     Written by Sean Reifschneider, this draft PEP describes a proposed
     mechanism for uploading Python packages to a central server.

   ---------- Footnotes ----------

   (1) 
https://web.archive.org/web/20090130140102/http://www.vex.net/parnassus/

   (2) https://peps.python.org/pep-0241/

   (3) https://peps.python.org/pep-0241/

   (4) https://peps.python.org/pep-0241/

   (5) https://peps.python.org/pep-0243/


File: python.info,  Node: New and Improved Modules<4>,  Next: Other Changes and Fixes<3>,  Prev: PEP 241 Metadata in Python Packages,  Up: Python 2 1 有什麼新功能

1.21.13 New and Improved Modules
--------------------------------

   * Ka-Ping Yee contributed two new modules: ‘inspect.py’, a module for
     getting information about live Python code, and ‘pydoc.py’, a
     module for interactively converting docstrings to HTML or text.  As
     a bonus, ‘Tools/scripts/pydoc’, which is now automatically
     installed, uses ‘pydoc.py’ to display documentation given a Python
     module, package, or class name.  For example, ‘pydoc xml.dom’
     displays the following:

          Python Library Documentation: package xml.dom in xml

          NAME
              xml.dom - W3C Document Object Model implementation for Python.

          FILE
              /usr/local/lib/python2.1/xml/dom/__init__.pyc

          DESCRIPTION
              The Python mapping of the Document Object Model is documented in the
              Python Library Reference in the section on the xml.dom package.

              This package contains the following modules:
                ...

     ‘pydoc’ also includes a Tk-based interactive help browser.  ‘pydoc’
     quickly becomes addictive; try it out!

   * Two different modules for unit testing were added to the standard
     library.  The *note doctest: 31. module, contributed by Tim Peters,
     provides a testing framework based on running embedded examples in
     docstrings and comparing the results against the expected output.
     PyUnit, contributed by Steve Purcell, is a unit testing framework
     inspired by JUnit, which was in turn an adaptation of Kent Beck's
     Smalltalk testing framework.  See ‘https://pyunit.sourceforge.net/’
     for more information about PyUnit.

   * The *note difflib: 2f. module contains a class, *note
     SequenceMatcher: fba, which compares two sequences and computes the
     changes required to transform one sequence into the other.  For
     example, this module can be used to write a tool similar to the
     Unix ‘diff’ program, and in fact the sample program
     ‘Tools/scripts/ndiff.py’ demonstrates how to write such a script.

   * *note curses.panel: 25, a wrapper for the panel library, part of
     ncurses and of SYSV curses, was contributed by Thomas Gellekum.
     The panel library provides windows with the additional feature of
     depth.  Windows can be moved higher or lower in the depth ordering,
     and the panel library figures out where panels overlap and which
     sections are visible.

   * The PyXML package has gone through a few releases since Python 2.0,
     and Python 2.1 includes an updated version of the *note xml: 107.
     package.  Some of the noteworthy changes include support for Expat
     1.2 and later versions, the ability for Expat parsers to handle
     files in any encoding supported by Python, and various bugfixes for
     SAX, DOM, and the ‘minidom’ module.

   * Ping also contributed another hook for handling uncaught
     exceptions.  *note sys.excepthook(): 7af. can be set to a callable
     object.  When an exception isn't caught by any *note try:
     68c...*note except: 171. blocks, the exception will be passed to
     *note sys.excepthook(): 7af, which can then do whatever it likes.
     At the Ninth Python Conference, Ping demonstrated an application
     for this hook: printing an extended traceback that not only lists
     the stack frames, but also lists the function arguments and the
     local variables for each frame.

   * Various functions in the *note time: d7. module, such as *note
     asctime(): 117f. and *note localtime(): 1467, require a
     floating-point argument containing the time in seconds since the
     epoch.  The most common use of these functions is to work with the
     current time, so the floating-point argument has been made
     optional; when a value isn't provided, the current time will be
     used.  For example, log file entries usually need a string
     containing the current time; in Python 2.1, ‘time.asctime()’ can be
     used, instead of the lengthier
     ‘time.asctime(time.localtime(time.time()))’ that was previously
     required.

     This change was proposed and implemented by Thomas Wouters.

   * The *note ftplib: 54. module now defaults to retrieving files in
     passive mode, because passive mode is more likely to work from
     behind a firewall.  This request came from the Debian bug tracking
     system, since other Debian packages use *note ftplib: 54. to
     retrieve files and then don't work from behind a firewall.  It's
     deemed unlikely that this will cause problems for anyone, because
     Netscape defaults to passive mode and few people complain, but if
     passive mode is unsuitable for your application or network setup,
     call ‘set_pasv(0)’ on FTP objects to disable passive mode.

   * Support for raw socket access has been added to the *note socket:
     b8. module, contributed by Grant Edwards.

   * The *note pstats: 9e. module now contains a simple interactive
     statistics browser for displaying timing profiles for Python
     programs, invoked when the module is run as a script.  Contributed
     by Eric S. Raymond.

   * A new implementation-dependent function, ‘sys._getframe([depth])’,
     has been added to return a given frame object from the current call
     stack.  *note sys._getframe(): 684. returns the frame at the top of
     the call stack; if the optional integer argument 'depth' is
     supplied, the function returns the frame that is 'depth' calls
     below the top of the stack.  For example, ‘sys._getframe(1)’
     returns the caller's frame object.

     This function is only present in CPython, not in Jython or the .NET
     implementation.  Use it for debugging, and resist the temptation to
     put it into production code.


File: python.info,  Node: Other Changes and Fixes<3>,  Next: 致謝<7>,  Prev: New and Improved Modules<4>,  Up: Python 2 1 有什麼新功能

1.21.14 Other Changes and Fixes
-------------------------------

There were relatively few smaller changes made in Python 2.1 due to the
shorter release cycle.  A search through the CVS change logs turns up
117 patches applied, and 136 bugs fixed; both figures are likely to be
underestimates.  Some of the more notable changes are:

   * A specialized object allocator is now optionally available, that
     should be faster than the system ‘malloc()’ and have less memory
     overhead.  The allocator uses C's ‘malloc()’ function to get large
     pools of memory, and then fulfills smaller memory requests from
     these pools.  It can be enabled by providing the ‘--with-pymalloc’
     option to the ‘configure’ script; see ‘Objects/obmalloc.c’ for the
     implementation details.

     Authors of C extension modules should test their code with the
     object allocator enabled, because some incorrect code may break,
     causing core dumps at runtime.  There are a bunch of memory
     allocation functions in Python's C API that have previously been
     just aliases for the C library's ‘malloc()’ and ‘free()’, meaning
     that if you accidentally called mismatched functions, the error
     wouldn't be noticeable.  When the object allocator is enabled,
     these functions aren't aliases of ‘malloc()’ and ‘free()’ any more,
     and calling the wrong function to free memory will get you a core
     dump.  For example, if memory was allocated using *note PyMem_New:
     1493, it has to be freed using *note PyMem_Del(): 1494, not
     ‘free()’.  A few modules included with Python fell afoul of this
     and had to be fixed; doubtless there are more third-party modules
     that will have the same problem.

     The object allocator was contributed by Vladimir Marangozov.

   * The speed of line-oriented file I/O has been improved because
     people often complain about its lack of speed, and because it's
     often been used as a naïve benchmark.  The *note readline(): a8.
     method of file objects has therefore been rewritten to be much
     faster.  The exact amount of the speedup will vary from platform to
     platform depending on how slow the C library's ‘getc()’ was, but is
     around 66%, and potentially much faster on some particular
     operating systems.  Tim Peters did much of the benchmarking and
     coding for this change, motivated by a discussion in
     comp.lang.python.

     A new module and method for file objects was also added,
     contributed by Jeff Epler.  The new method, ‘xreadlines()’, is
     similar to the existing ‘xrange()’ built-in.  ‘xreadlines()’
     returns an opaque sequence object that only supports being iterated
     over, reading a line on every iteration but not reading the entire
     file into memory as the existing ‘readlines()’ method does.  You'd
     use it like this:

          for line in sys.stdin.xreadlines():
              # ... do something for each line ...
              ...

     For a fuller discussion of the line I/O changes, see the python-dev
     summary for January 1-15, 2001 at
     ‘https://mail.python.org/pipermail/python-dev/2001-January/’.

   * A new method, *note popitem(): 1495, was added to dictionaries to
     enable destructively iterating through the contents of a
     dictionary; this can be faster for large dictionaries because
     there's no need to construct a list containing all the keys or
     values.  ‘D.popitem()’ removes a random ‘(key, value)’ pair from
     the dictionary ‘D’ and returns it as a 2-tuple.  This was
     implemented mostly by Tim Peters and Guido van Rossum, after a
     suggestion and preliminary patch by Moshe Zadka.

   * Modules can now control which names are imported when ‘from module
     import *’ is used, by defining an ‘__all__’ attribute containing a
     list of names that will be imported.  One common complaint is that
     if the module imports other modules such as *note sys: c3. or *note
     string: be, ‘from module import *’ will add them to the importing
     module's namespace.  To fix this, simply list the public names in
     ‘__all__’:

          # List public names
          __all__ = ['Database', 'open']

     A stricter version of this patch was first suggested and
     implemented by Ben Wolfson, but after some python-dev discussion, a
     weaker final version was checked in.

   * Applying *note repr(): 7a1. to strings previously used octal
     escapes for non-printable characters; for example, a newline was
     ‘'\012'’.  This was a vestigial trace of Python's C ancestry, but
     today octal is of very little practical use.  Ka-Ping Yee suggested
     using hex escapes instead of octal ones, and using the ‘\n’, ‘\t’,
     ‘\r’ escapes for the appropriate characters, and implemented this
     new formatting.

   * Syntax errors detected at compile-time can now raise exceptions
     containing the filename and line number of the error, a pleasant
     side effect of the compiler reorganization done by Jeremy Hylton.

   * C extensions which import other modules have been changed to use
     *note PyImport_ImportModule(): 389, which means that they will use
     any import hooks that have been installed.  This is also encouraged
     for third-party extensions that need to import some other module
     from C code.

   * The size of the Unicode character database was shrunk by another
     340K thanks to Fredrik Lundh.

   * Some new ports were contributed: MacOS X (by Steven Majewski),
     Cygwin (by Jason Tishler); RISCOS (by Dietmar Schwertberger);
     Unixware 7 (by Billy G. Allie).

And there's the usual list of minor bugfixes, minor memory leaks,
docstring edits, and other tweaks, too lengthy to be worth itemizing;
see the CVS logs for the full details if you want them.


File: python.info,  Node: 致謝<7>,  Prev: Other Changes and Fixes<3>,  Up: Python 2 1 有什麼新功能

1.21.15 致謝
------------

The author would like to thank the following people for offering
suggestions on various drafts of this article: Graeme Cross, David
Goodger, Jay Graves, Michael Hudson, Marc-André Lemburg, Fredrik Lundh,
Neil Schemenauer, Thomas Wouters.


File: python.info,  Node: Python 2 0 有什麼新功能,  Next: Changelog（更動日誌）,  Prev: Python 2 1 有什麼新功能,  Up: Python 有什麼新功能？

1.22 Python 2.0 有什麼新功能
============================


作者: A.M. Kuchling 和 Moshe Zadka

* Menu:

* 簡介: 簡介<3>.
* What About Python 1.6?: What About Python 1 6?.
* New Development Process::
* Unicode: Unicode<2>.
* 串列綜合運算（List Comprehension）::
* Augmented Assignment::
* String Methods::
* Garbage Collection of Cycles::
* Other Core Changes::
* Porting to 2.0: Porting to 2 0.
* Extending/Embedding Changes::
* Distutils; Making Modules Easy to Install: Distutils Making Modules Easy to Install.
* XML 模組::
* 模組變更::
* 新增模組: 新增模組<5>.
* IDLE Improvements::
* Deleted and Deprecated Modules::
* 致謝: 致謝<8>.


File: python.info,  Node: 簡介<3>,  Next: What About Python 1 6?,  Up: Python 2 0 有什麼新功能

1.22.1 簡介
-----------

A new release of Python, version 2.0, was released on October 16, 2000.
This article covers the exciting new features in 2.0, highlights some
other useful changes, and points out a few incompatible changes that may
require rewriting code.

Python's development never completely stops between releases, and a
steady flow of bug fixes and improvements are always being submitted.  A
host of minor fixes, a few optimizations, additional docstrings, and
better error messages went into 2.0; to list them all would be
impossible, but they're certainly significant.  Consult the publicly
available CVS logs if you want to see the full list.  This progress is
due to the five developers working for PythonLabs are now getting paid
to spend their days fixing bugs, and also due to the improved
communication resulting from moving to SourceForge.


File: python.info,  Node: What About Python 1 6?,  Next: New Development Process,  Prev: 簡介<3>,  Up: Python 2 0 有什麼新功能

1.22.2 What About Python 1.6?
-----------------------------

Python 1.6 can be thought of as the Contractual Obligations Python
release.  After the core development team left CNRI in May 2000, CNRI
requested that a 1.6 release be created, containing all the work on
Python that had been performed at CNRI. Python 1.6 therefore represents
the state of the CVS tree as of May 2000, with the most significant new
feature being Unicode support.  Development continued after May, of
course, so the 1.6 tree received a few fixes to ensure that it's
forward-compatible with Python 2.0.  1.6 is therefore part of Python's
evolution, and not a side branch.

So, should you take much interest in Python 1.6?  Probably not.  The
1.6final and 2.0beta1 releases were made on the same day (September 5,
2000), the plan being to finalize Python 2.0 within a month or so.  If
you have applications to maintain, there seems little point in breaking
things by moving to 1.6, fixing them, and then having another round of
breakage within a month by moving to 2.0; you're better off just going
straight to 2.0.  Most of the really interesting features described in
this document are only in 2.0, because a lot of work was done between
May and September.


File: python.info,  Node: New Development Process,  Next: Unicode<2>,  Prev: What About Python 1 6?,  Up: Python 2 0 有什麼新功能

1.22.3 New Development Process
------------------------------

The most important change in Python 2.0 may not be to the code at all,
but to how Python is developed: in May 2000 the Python developers began
using the tools made available by SourceForge for storing source code,
tracking bug reports, and managing the queue of patch submissions.  To
report bugs or submit patches for Python 2.0, use the bug tracking and
patch manager tools available from Python's project page, located at
‘https://sourceforge.net/projects/python/’.

The most important of the services now hosted at SourceForge is the
Python CVS tree, the version-controlled repository containing the source
code for Python.  Previously, there were roughly 7 or so people who had
write access to the CVS tree, and all patches had to be inspected and
checked in by one of the people on this short list.  Obviously, this
wasn't very scalable.  By moving the CVS tree to SourceForge, it became
possible to grant write access to more people; as of September 2000
there were 27 people able to check in changes, a fourfold increase.
This makes possible large-scale changes that wouldn't be attempted if
they'd have to be filtered through the small group of core developers.
For example, one day Peter Schneider-Kamp took it into his head to drop
K&R C compatibility and convert the C source for Python to ANSI C. After
getting approval on the python-dev mailing list, he launched into a
flurry of checkins that lasted about a week, other developers joined in
to help, and the job was done.  If there were only 5 people with write
access, probably that task would have been viewed as "nice, but not
worth the time and effort needed" and it would never have gotten done.

The shift to using SourceForge's services has resulted in a remarkable
increase in the speed of development.  Patches now get submitted,
commented on, revised by people other than the original submitter, and
bounced back and forth between people until the patch is deemed worth
checking in.  Bugs are tracked in one central location and can be
assigned to a specific person for fixing, and we can count the number of
open bugs to measure progress.  This didn't come without a cost:
developers now have more e-mail to deal with, more mailing lists to
follow, and special tools had to be written for the new environment.
For example, SourceForge sends default patch and bug notification e-mail
messages that are completely unhelpful, so Ka-Ping Yee wrote an HTML
screen-scraper that sends more useful messages.

The ease of adding code caused a few initial growing pains, such as code
was checked in before it was ready or without getting clear agreement
from the developer group.  The approval process that has emerged is
somewhat similar to that used by the Apache group.  Developers can vote
+1, +0, -0, or -1 on a patch; +1 and -1 denote acceptance or rejection,
while +0 and -0 mean the developer is mostly indifferent to the change,
though with a slight positive or negative slant.  The most significant
change from the Apache model is that the voting is essentially advisory,
letting Guido van Rossum, who has Benevolent Dictator For Life status,
know what the general opinion is.  He can still ignore the result of a
vote, and approve or reject a change even if the community disagrees
with him.

Producing an actual patch is the last step in adding a new feature, and
is usually easy compared to the earlier task of coming up with a good
design.  Discussions of new features can often explode into lengthy
mailing list threads, making the discussion hard to follow, and no one
can read every posting to python-dev.  Therefore, a relatively formal
process has been set up to write Python Enhancement Proposals (PEPs),
modelled on the internet RFC process.  PEPs are draft documents that
describe a proposed new feature, and are continually revised until the
community reaches a consensus, either accepting or rejecting the
proposal.  Quoting from the introduction to PEP 1(1), "PEP Purpose and
Guidelines":

     PEP stands for Python Enhancement Proposal.  A PEP is a design
     document providing information to the Python community, or
     describing a new feature for Python.  The PEP should provide a
     concise technical specification of the feature and a rationale for
     the feature.

     We intend PEPs to be the primary mechanisms for proposing new
     features, for collecting community input on an issue, and for
     documenting the design decisions that have gone into Python.  The
     PEP author is responsible for building consensus within the
     community and documenting dissenting opinions.

Read the rest of PEP 1(2) for the details of the PEP editorial process,
style, and format.  PEPs are kept in the Python CVS tree on SourceForge,
though they're not part of the Python 2.0 distribution, and are also
available in HTML form from ‘https://peps.python.org/’.  As of September
2000, there are 25 PEPs, ranging from PEP 201(3), "Lockstep Iteration",
to PEP 225, "Elementwise/Objectwise Operators".

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0001/

   (2) https://peps.python.org/pep-0001/

   (3) https://peps.python.org/pep-0201/


File: python.info,  Node: Unicode<2>,  Next: 串列綜合運算（List Comprehension）,  Prev: New Development Process,  Up: Python 2 0 有什麼新功能

1.22.4 Unicode
--------------

The largest new feature in Python 2.0 is a new fundamental data type:
Unicode strings.  Unicode uses 16-bit numbers to represent characters
instead of the 8-bit number used by ASCII, meaning that 65,536 distinct
characters can be supported.

The final interface for Unicode support was arrived at through countless
often-stormy discussions on the python-dev mailing list, and mostly
implemented by Marc-André Lemburg, based on a Unicode string type
implementation by Fredrik Lundh.  A detailed explanation of the
interface was written up as PEP 100(1), "Python Unicode Integration".
This article will simply cover the most significant points about the
Unicode interfaces.

In Python source code, Unicode strings are written as ‘u"string"’.
Arbitrary Unicode characters can be written using a new escape sequence,
‘\uHHHH’, where 'HHHH' is a 4-digit hexadecimal number from 0000 to
FFFF.  The existing ‘\xHH’ escape sequence can also be used, and octal
escapes can be used for characters up to U+01FF, which is represented by
‘\777’.

Unicode strings, just like regular strings, are an immutable sequence
type.  They can be indexed and sliced, but not modified in place.
Unicode strings have an ‘encode( [encoding] )’ method that returns an
8-bit string in the desired encoding.  Encodings are named by strings,
such as ‘'ascii'’, ‘'utf-8'’, ‘'iso-8859-1'’, or whatever.  A codec API
is defined for implementing and registering new encodings that are then
available throughout a Python program.  If an encoding isn't specified,
the default encoding is usually 7-bit ASCII, though it can be changed
for your Python installation by calling the
‘sys.setdefaultencoding(encoding)’ function in a customized version of
‘site.py’.

Combining 8-bit and Unicode strings always coerces to Unicode, using the
default ASCII encoding; the result of ‘'a' + u'bc'’ is ‘u'abc'’.

New built-in functions have been added, and existing built-ins modified
to support Unicode:

   * ‘unichr(ch)’ returns a Unicode string 1 character long, containing
     the character 'ch'.

   * ‘ord(u)’, where 'u' is a 1-character regular or Unicode string,
     returns the number of the character as an integer.

   * ‘unicode(string [, encoding] [, errors] )’ creates a Unicode string
     from an 8-bit string.  ‘encoding’ is a string naming the encoding
     to use.  The ‘errors’ parameter specifies the treatment of
     characters that are invalid for the current encoding; passing
     ‘'strict'’ as the value causes an exception to be raised on any
     encoding error, while ‘'ignore'’ causes errors to be silently
     ignored and ‘'replace'’ uses U+FFFD, the official replacement
     character, in case of any problems.

   * The ‘exec’ statement, and various built-ins such as ‘eval()’,
     ‘getattr()’, and ‘setattr()’ will also accept Unicode strings as
     well as regular strings.  (It's possible that the process of fixing
     this missed some built-ins; if you find a built-in function that
     accepts strings but doesn't accept Unicode strings at all, please
     report it as a bug.)

A new module, *note unicodedata: ee, provides an interface to Unicode
character properties.  For example, ‘unicodedata.category(u'A')’ returns
the 2-character string 'Lu', the 'L' denoting it's a letter, and 'u'
meaning that it's uppercase.  ‘unicodedata.bidirectional(u'\u0660')’
returns 'AN', meaning that U+0660 is an Arabic number.

The *note codecs: 14. module contains functions to look up existing
encodings and register new ones.  Unless you want to implement a new
encoding, you'll most often use the ‘codecs.lookup(encoding)’ function,
which returns a 4-element tuple: ‘(encode_func, decode_func,
stream_reader, stream_writer)’.

   * 'encode_func' is a function that takes a Unicode string, and
     returns a 2-tuple ‘(string, length)’.  'string' is an 8-bit string
     containing a portion (perhaps all) of the Unicode string converted
     into the given encoding, and 'length' tells you how much of the
     Unicode string was converted.

   * 'decode_func' is the opposite of 'encode_func', taking an 8-bit
     string and returning a 2-tuple ‘(ustring, length)’, consisting of
     the resulting Unicode string 'ustring' and the integer 'length'
     telling how much of the 8-bit string was consumed.

   * 'stream_reader' is a class that supports decoding input from a
     stream.  'stream_reader(file_obj)' returns an object that supports
     the ‘read()’, ‘readline()’, and ‘readlines()’ methods.  These
     methods will all translate from the given encoding and return
     Unicode strings.

   * 'stream_writer', similarly, is a class that supports encoding
     output to a stream.  'stream_writer(file_obj)' returns an object
     that supports the ‘write()’ and ‘writelines()’ methods.  These
     methods expect Unicode strings, translating them to the given
     encoding on output.

For example, the following code writes a Unicode string into a file,
encoding it as UTF-8:

     import codecs

     unistr = u'\u0660\u2000ab ...'

     (UTF8_encode, UTF8_decode,
      UTF8_streamreader, UTF8_streamwriter) = codecs.lookup('UTF-8')

     output = UTF8_streamwriter( open( '/tmp/output', 'wb') )
     output.write( unistr )
     output.close()

The following code would then read UTF-8 input from the file:

     input = UTF8_streamreader( open( '/tmp/output', 'rb') )
     print repr(input.read())
     input.close()

Unicode-aware regular expressions are available through the *note re:
a7. module, which has a new underlying implementation called SRE written
by Fredrik Lundh of Secret Labs AB.

A ‘-U’ command line option was added which causes the Python compiler to
interpret all string literals as Unicode string literals.  This is
intended to be used in testing and future-proofing your Python code,
since some future version of Python may drop support for 8-bit strings
and provide only Unicode strings.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0100/


File: python.info,  Node: 串列綜合運算（List Comprehension）,  Next: Augmented Assignment,  Prev: Unicode<2>,  Up: Python 2 0 有什麼新功能

1.22.5 串列綜合運算（List Comprehension）
-----------------------------------------

Lists are a workhorse data type in Python, and many programs manipulate
a list at some point.  Two common operations on lists are to loop over
them, and either pick out the elements that meet a certain criterion, or
apply some function to each element.  For example, given a list of
strings, you might want to pull out all the strings containing a given
substring, or strip off trailing whitespace from each line.

The existing *note map(): 808. and *note filter(): 809. functions can be
used for this purpose, but they require a function as one of their
arguments.  This is fine if there's an existing built-in function that
can be passed directly, but if there isn't, you have to create a little
function to do the required work, and Python's scoping rules make the
result ugly if the little function needs additional information.  Take
the first example in the previous paragraph, finding all the strings in
the list containing a given substring.  You could write the following to
do it:

     # Given the list L, make a list of all strings
     # containing the substring S.
     sublist = filter( lambda s, substring=S:
                          string.find(s, substring) != -1,
                       L)

Because of Python's scoping rules, a default argument is used so that
the anonymous function created by the *note lambda: 1234. expression
knows what substring is being searched for.  List comprehensions make
this cleaner:

     sublist = [ s for s in L if string.find(s, S) != -1 ]

List comprehensions have the form:

     [ expression for expr in sequence1
                  for expr2 in sequence2 ...
                  for exprN in sequenceN
                  if condition ]

The ‘for’...‘in’ clauses contain the sequences to be iterated over.  The
sequences do not have to be the same length, because they are 'not'
iterated over in parallel, but from left to right; this is explained
more clearly in the following paragraphs.  The elements of the generated
list will be the successive values of 'expression'.  The final ‘if’
clause is optional; if present, 'expression' is only evaluated and added
to the result if 'condition' is true.

To make the semantics very clear, a list comprehension is equivalent to
the following Python code:

     for expr1 in sequence1:
         for expr2 in sequence2:
         ...
             for exprN in sequenceN:
                  if (condition):
                       # Append the value of
                       # the expression to the
                       # resulting list.

This means that when there are multiple ‘for’...‘in’ clauses, the
resulting list will be equal to the product of the lengths of all the
sequences.  If you have two lists of length 3, the output list is 9
elements long:

     seq1 = 'abc'
     seq2 = (1,2,3)
     >>> [ (x,y) for x in seq1 for y in seq2]
     [('a', 1), ('a', 2), ('a', 3), ('b', 1), ('b', 2), ('b', 3), ('c', 1),
     ('c', 2), ('c', 3)]

To avoid introducing an ambiguity into Python's grammar, if 'expression'
is creating a tuple, it must be surrounded with parentheses.  The first
list comprehension below is a syntax error, while the second one is
correct:

     # 語法錯誤
     [ x,y for x in seq1 for y in seq2]
     # 正確
     [ (x,y) for x in seq1 for y in seq2]

The idea of list comprehensions originally comes from the functional
programming language Haskell (‘https://www.haskell.org’).  Greg Ewing
argued most effectively for adding them to Python and wrote the initial
list comprehension patch, which was then discussed for a seemingly
endless time on the python-dev mailing list and kept up-to-date by Skip
Montanaro.


File: python.info,  Node: Augmented Assignment,  Next: String Methods,  Prev: 串列綜合運算（List Comprehension）,  Up: Python 2 0 有什麼新功能

1.22.6 Augmented Assignment
---------------------------

Augmented assignment operators, another long-requested feature, have
been added to Python 2.0.  Augmented assignment operators include ‘+=’,
‘-=’, ‘*=’, and so forth.  For example, the statement ‘a += 2’
increments the value of the variable ‘a’ by 2, equivalent to the
slightly lengthier ‘a = a + 2’.

The full list of supported assignment operators is ‘+=’, ‘-=’, ‘*=’,
‘/=’, ‘%=’, ‘**=’, ‘&=’, ‘|=’, ‘^=’, ‘>>=’, and ‘<<=’.  Python classes
can override the augmented assignment operators by defining methods
named ‘__iadd__()’, ‘__isub__()’, etc.  For example, the following
‘Number’ class stores a number and supports using += to create a new
instance with an incremented value.

     class Number:
         def __init__(self, value):
             self.value = value
         def __iadd__(self, increment):
             return Number( self.value + increment)

     n = Number(5)
     n += 3
     print n.value

The ‘__iadd__()’ special method is called with the value of the
increment, and should return a new instance with an appropriately
modified value; this return value is bound as the new value of the
variable on the left-hand side.

Augmented assignment operators were first introduced in the C
programming language, and most C-derived languages, such as ‘awk’, C++,
Java, Perl, and PHP also support them.  The augmented assignment patch
was implemented by Thomas Wouters.


File: python.info,  Node: String Methods,  Next: Garbage Collection of Cycles,  Prev: Augmented Assignment,  Up: Python 2 0 有什麼新功能

1.22.7 String Methods
---------------------

Until now string-manipulation functionality was in the *note string: be.
module, which was usually a front-end for the ‘strop’ module written in
C. The addition of Unicode posed a difficulty for the ‘strop’ module,
because the functions would all need to be rewritten in order to accept
either 8-bit or Unicode strings.  For functions such as
‘string.replace()’, which takes 3 string arguments, that means eight
possible permutations, and correspondingly complicated code.

Instead, Python 2.0 pushes the problem onto the string type, making
string manipulation functionality available through methods on both
8-bit strings and Unicode strings.

     >>> 'andrew'.capitalize()
     'Andrew'
     >>> 'hostname'.replace('os', 'linux')
     'hlinuxtname'
     >>> 'moshe'.find('sh')
     2

One thing that hasn't changed, a noteworthy April Fools' joke
notwithstanding, is that Python strings are immutable.  Thus, the string
methods return new strings, and do not modify the string on which they
operate.

The old *note string: be. module is still around for backwards
compatibility, but it mostly acts as a front-end to the new string
methods.

Two methods which have no parallel in pre-2.0 versions, although they
did exist in JPython for quite some time, are ‘startswith()’ and
‘endswith()’.  ‘s.startswith(t)’ is equivalent to ‘s[:len(t)] == t’,
while ‘s.endswith(t)’ is equivalent to ‘s[-len(t):] == t’.

One other method which deserves special mention is ‘join()’.  The
‘join()’ method of a string receives one parameter, a sequence of
strings, and is equivalent to the ‘string.join()’ function from the old
*note string: be. module, with the arguments reversed.  In other words,
‘s.join(seq)’ is equivalent to the old ‘string.join(seq, s)’.


File: python.info,  Node: Garbage Collection of Cycles,  Next: Other Core Changes,  Prev: String Methods,  Up: Python 2 0 有什麼新功能

1.22.8 Garbage Collection of Cycles
-----------------------------------

The C implementation of Python uses reference counting to implement
garbage collection.  Every Python object maintains a count of the number
of references pointing to itself, and adjusts the count as references
are created or destroyed.  Once the reference count reaches zero, the
object is no longer accessible, since you need to have a reference to an
object to access it, and if the count is zero, no references exist any
longer.

Reference counting has some pleasant properties: it's easy to understand
and implement, and the resulting implementation is portable, fairly
fast, and reacts well with other libraries that implement their own
memory handling schemes.  The major problem with reference counting is
that it sometimes doesn't realise that objects are no longer accessible,
resulting in a memory leak.  This happens when there are cycles of
references.

Consider the simplest possible cycle, a class instance which has a
reference to itself:

     instance = SomeClass()
     instance.myself = instance

After the above two lines of code have been executed, the reference
count of ‘instance’ is 2; one reference is from the variable named
‘'instance'’, and the other is from the ‘myself’ attribute of the
instance.

If the next line of code is ‘del instance’, what happens?  The reference
count of ‘instance’ is decreased by 1, so it has a reference count of 1;
the reference in the ‘myself’ attribute still exists.  Yet the instance
is no longer accessible through Python code, and it could be deleted.
Several objects can participate in a cycle if they have references to
each other, causing all of the objects to be leaked.

Python 2.0 fixes this problem by periodically executing a cycle
detection algorithm which looks for inaccessible cycles and deletes the
objects involved.  A new *note gc: 56. module provides functions to
perform a garbage collection, obtain debugging statistics, and tuning
the collector's parameters.

Running the cycle detection algorithm takes some time, and therefore
will result in some additional overhead.  It is hoped that after we've
gotten experience with the cycle collection from using 2.0, Python 2.1
will be able to minimize the overhead with careful tuning.  It's not yet
obvious how much performance is lost, because benchmarking this is
tricky and depends crucially on how often the program creates and
destroys objects.  The detection of cycles can be disabled when Python
is compiled, if you can't afford even a tiny speed penalty or suspect
that the cycle collection is buggy, by specifying the
‘--without-cycle-gc’ switch when running the ‘configure’ script.

Several people tackled this problem and contributed to a solution.  An
early implementation of the cycle detection approach was written by Toby
Kelsey.  The current algorithm was suggested by Eric Tiedemann during a
visit to CNRI, and Guido van Rossum and Neil Schemenauer wrote two
different implementations, which were later integrated by Neil.  Lots of
other people offered suggestions along the way; the March 2000 archives
of the python-dev mailing list contain most of the relevant discussion,
especially in the threads titled "Reference cycle collection for Python"
and "Finalization again".


File: python.info,  Node: Other Core Changes,  Next: Porting to 2 0,  Prev: Garbage Collection of Cycles,  Up: Python 2 0 有什麼新功能

1.22.9 Other Core Changes
-------------------------

Various minor changes have been made to Python's syntax and built-in
functions.  None of the changes are very far-reaching, but they're handy
conveniences.

* Menu:

* Minor Language Changes::
* Changes to Built-in Functions::


File: python.info,  Node: Minor Language Changes,  Next: Changes to Built-in Functions,  Up: Other Core Changes

1.22.9.1 Minor Language Changes
...............................

A new syntax makes it more convenient to call a given function with a
tuple of arguments and/or a dictionary of keyword arguments.  In Python
1.5 and earlier, you'd use the ‘apply()’ built-in function: ‘apply(f,
args, kw)’ calls the function ‘f()’ with the argument tuple 'args' and
the keyword arguments in the dictionary 'kw'.  ‘apply()’ is the same in
2.0, but thanks to a patch from Greg Ewing, ‘f(*args, **kw)’ is a
shorter and clearer way to achieve the same effect.  This syntax is
symmetrical with the syntax for defining functions:

     def f(*args, **kw):
         # args is a tuple of positional args,
         # kw is a dictionary of keyword args
         ...

The ‘print’ statement can now have its output directed to a file-like
object by following the ‘print’ with ‘>> file’, similar to the
redirection operator in Unix shells.  Previously you'd either have to
use the ‘write()’ method of the file-like object, which lacks the
convenience and simplicity of ‘print’, or you could assign a new value
to ‘sys.stdout’ and then restore the old value.  For sending output to
standard error, it's much easier to write this:

     print >> sys.stderr, "Warning: action field not supplied"

Modules can now be renamed on importing them, using the syntax ‘import
module as name’ or ‘from module import name as othername’.  The patch
was submitted by Thomas Wouters.

A new format style is available when using the ‘%’ operator; '%r' will
insert the *note repr(): 7a1. of its argument.  This was also added from
symmetry considerations, this time for symmetry with the existing '%s'
format style, which inserts the *note str(): 3f2. of its argument.  For
example, ‘'%r %s' % ('abc', 'abc')’ returns a string containing ‘'abc'
abc’.

Previously there was no way to implement a class that overrode Python's
built-in *note in: 2c5. operator and implemented a custom version.  ‘obj
in seq’ returns true if 'obj' is present in the sequence 'seq'; Python
computes this by simply trying every index of the sequence until either
'obj' is found or an *note IndexError: 14a3. is encountered.  Moshe
Zadka contributed a patch which adds a ‘__contains__()’ magic method for
providing a custom implementation for ‘in’.  Additionally, new built-in
objects written in C can define what ‘in’ means for them via a new slot
in the sequence protocol.

Earlier versions of Python used a recursive algorithm for deleting
objects.  Deeply nested data structures could cause the interpreter to
fill up the C stack and crash; Christian Tismer rewrote the deletion
logic to fix this problem.  On a related note, comparing recursive
objects recursed infinitely and crashed; Jeremy Hylton rewrote the code
to no longer crash, producing a useful result instead.  For example,
after this code:

     a = []
     b = []
     a.append(a)
     b.append(b)

The comparison ‘a==b’ returns true, because the two recursive data
structures are isomorphic.  See the thread "trashcan and PR#7" in the
April 2000 archives of the python-dev mailing list for the discussion
leading up to this implementation, and some useful relevant links.  Note
that comparisons can now also raise exceptions.  In earlier versions of
Python, a comparison operation such as ‘cmp(a,b)’ would always produce
an answer, even if a user-defined ‘__cmp__()’ method encountered an
error, since the resulting exception would simply be silently swallowed.

Work has been done on porting Python to 64-bit Windows on the Itanium
processor, mostly by Trent Mick of ActiveState.  (Confusingly,
‘sys.platform’ is still ‘'win32'’ on Win64 because it seems that for
ease of porting, MS Visual C++ treats code as 32 bit on Itanium.)
PythonWin also supports Windows CE; see the Python CE page at
‘https://pythonce.sourceforge.net/’ for more information.

Another new platform is Darwin/MacOS X; initial support for it is in
Python 2.0.  Dynamic loading works, if you specify "configure -with-dyld
-with-suffix=.x".  Consult the README in the Python source distribution
for more instructions.

An attempt has been made to alleviate one of Python's warts, the
often-confusing *note NameError: 3e5. exception when code refers to a
local variable before the variable has been assigned a value.  For
example, the following code raises an exception on the ‘print’ statement
in both 1.5.2 and 2.0; in 1.5.2 a *note NameError: 3e5. exception is
raised, while 2.0 raises a new *note UnboundLocalError: 14a4. exception.
*note UnboundLocalError: 14a4. is a subclass of *note NameError: 3e5, so
any existing code that expects *note NameError: 3e5. to be raised should
still work.

     def f():
         print "i=",i
         i = i + 1
     f()

Two new exceptions, *note TabError: 4e9. and *note IndentationError:
74c, have been introduced.  They're both subclasses of *note
SyntaxError: 173, and are raised when Python code is found to be
improperly indented.


File: python.info,  Node: Changes to Built-in Functions,  Prev: Minor Language Changes,  Up: Other Core Changes

1.22.9.2 Changes to Built-in Functions
......................................

A new built-in, ‘zip(seq1, seq2, ...)’, has been added.  *note zip():
774. returns a list of tuples where each tuple contains the i-th element
from each of the argument sequences.  The difference between *note
zip(): 774. and ‘map(None, seq1, seq2)’ is that *note map(): 808. pads
the sequences with ‘None’ if the sequences aren't all of the same
length, while *note zip(): 774. truncates the returned list to the
length of the shortest argument sequence.

The *note int(): 23c. and ‘long()’ functions now accept an optional
"base" parameter when the first argument is a string.  ‘int('123', 10)’
returns 123, while ‘int('123', 16)’ returns 291.  ‘int(123, 16)’ raises
a *note TypeError: 4dd. exception with the message "can't convert
non-string with explicit base".

A new variable holding more detailed version information has been added
to the *note sys: c3. module.  ‘sys.version_info’ is a tuple ‘(major,
minor, micro, level, serial)’ For example, in a hypothetical 2.0.1beta1,
‘sys.version_info’ would be ‘(2, 0, 1, 'beta', 1)’.  'level' is a string
such as ‘"alpha"’, ‘"beta"’, or ‘"final"’ for a final release.

Dictionaries have an odd new method, ‘setdefault(key, default)’, which
behaves similarly to the existing ‘get()’ method.  However, if the key
is missing, ‘setdefault()’ both returns the value of 'default' as
‘get()’ would do, and also inserts it into the dictionary as the value
for 'key'.  Thus, the following lines of code:

     if dict.has_key( key ): return dict[key]
     else:
         dict[key] = []
         return dict[key]

can be reduced to a single ‘return dict.setdefault(key, [])’ statement.

The interpreter sets a maximum recursion depth in order to catch runaway
recursion before filling the C stack and causing a core dump or GPF..
Previously this limit was fixed when you compiled Python, but in 2.0 the
maximum recursion depth can be read and modified using *note
sys.getrecursionlimit(): 46b. and *note sys.setrecursionlimit(): 46a.
The default value is 1000, and a rough maximum value for a given
platform can be found by running a new script,
‘Misc/find_recursionlimit.py’.


File: python.info,  Node: Porting to 2 0,  Next: Extending/Embedding Changes,  Prev: Other Core Changes,  Up: Python 2 0 有什麼新功能

1.22.10 Porting to 2.0
----------------------

New Python releases try hard to be compatible with previous releases,
and the record has been pretty good.  However, some changes are
considered useful enough, usually because they fix initial design
decisions that turned out to be actively mistaken, that breaking
backward compatibility can't always be avoided.  This section lists the
changes in Python 2.0 that may cause old Python code to break.

The change which will probably break the most code is tightening up the
arguments accepted by some methods.  Some methods would take multiple
arguments and treat them as a tuple, particularly various list methods
such as ‘append()’ and ‘insert()’.  In earlier versions of Python, if
‘L’ is a list, ‘L.append( 1,2 )’ appends the tuple ‘(1,2)’ to the list.
In Python 2.0 this causes a *note TypeError: 4dd. exception to be
raised, with the message: 'append requires exactly 1 argument; 2 given'.
The fix is to simply add an extra set of parentheses to pass both values
as a tuple: ‘L.append( (1,2) )’.

The earlier versions of these methods were more forgiving because they
used an old function in Python's C interface to parse their arguments;
2.0 modernizes them to use *note PyArg_ParseTuple(): 517, the current
argument parsing function, which provides more helpful error messages
and treats multi-argument calls as errors.  If you absolutely must use
2.0 but can't fix your code, you can edit ‘Objects/listobject.c’ and
define the preprocessor symbol ‘NO_STRICT_LIST_APPEND’ to preserve the
old behaviour; this isn't recommended.

Some of the functions in the *note socket: b8. module are still
forgiving in this way.  For example, ‘socket.connect( ('hostname', 25)
)’ is the correct form, passing a tuple representing an IP address, but
‘socket.connect('hostname', 25)’ also works.  *note socket.connect_ex:
14a7. and *note socket.bind: 14a8. are similarly easy-going.  2.0alpha1
tightened these functions up, but because the documentation actually
used the erroneous multiple argument form, many people wrote code which
would break with the stricter checking.  GvR backed out the changes in
the face of public reaction, so for the *note socket: b8. module, the
documentation was fixed and the multiple argument form is simply marked
as deprecated; it 'will' be tightened up again in a future Python
version.

The ‘\x’ escape in string literals now takes exactly 2 hex digits.
Previously it would consume all the hex digits following the 'x' and
take the lowest 8 bits of the result, so ‘\x123456’ was equivalent to
‘\x56’.

The *note AttributeError: 2f6. and *note NameError: 3e5. exceptions have
a more friendly error message, whose text will be something like ‘'Spam'
instance has no attribute 'eggs'’ or ‘name 'eggs' is not defined’.
Previously the error message was just the missing attribute name ‘eggs’,
and code written to take advantage of this fact will break in 2.0.

Some work has been done to make integers and long integers a bit more
interchangeable.  In 1.5.2, large-file support was added for Solaris, to
allow reading files larger than 2 GiB; this made the ‘tell()’ method of
file objects return a long integer instead of a regular integer.  Some
code would subtract two file offsets and attempt to use the result to
multiply a sequence or slice a string, but this raised a *note
TypeError: 4dd.  In 2.0, long integers can be used to multiply or slice
a sequence, and it'll behave as you'd intuitively expect it to; ‘3L *
'abc'’ produces 'abcabcabc', and ‘(0,1,2,3)[2L:4L]’ produces (2,3).
Long integers can also be used in various contexts where previously only
integers were accepted, such as in the ‘seek()’ method of file objects,
and in the formats supported by the ‘%’ operator (‘%d’, ‘%i’, ‘%x’,
etc.).  For example, ‘"%d" % 2L**64’ will produce the string
‘18446744073709551616’.

The subtlest long integer change of all is that the *note str(): 3f2. of
a long integer no longer has a trailing 'L' character, though *note
repr(): 7a1. still includes it.  The 'L' annoyed many people who wanted
to print long integers that looked just like regular integers, since
they had to go out of their way to chop off the character.  This is no
longer a problem in 2.0, but code which does ‘str(longval)[:-1]’ and
assumes the 'L' is there, will now lose the final digit.

Taking the *note repr(): 7a1. of a float now uses a different formatting
precision than *note str(): 3f2.  *note repr(): 7a1. uses ‘%.17g’ format
string for C's ‘sprintf()’, while *note str(): 3f2. uses ‘%.12g’ as
before.  The effect is that *note repr(): 7a1. may occasionally show
more decimal places than *note str(): 3f2, for certain numbers.  For
example, the number 8.1 can't be represented exactly in binary, so
‘repr(8.1)’ is ‘'8.0999999999999996'’, while str(8.1) is ‘'8.1'’.

The ‘-X’ command-line option, which turned all standard exceptions into
strings instead of classes, has been removed; the standard exceptions
will now always be classes.  The ‘exceptions’ module containing the
standard exceptions was translated from Python to a built-in C module,
written by Barry Warsaw and Fredrik Lundh.


File: python.info,  Node: Extending/Embedding Changes,  Next: Distutils Making Modules Easy to Install,  Prev: Porting to 2 0,  Up: Python 2 0 有什麼新功能

1.22.11 Extending/Embedding Changes
-----------------------------------

Some of the changes are under the covers, and will only be apparent to
people writing C extension modules or embedding a Python interpreter in
a larger application.  If you aren't dealing with Python's C API, you
can safely skip this section.

The version number of the Python C API was incremented, so C extensions
compiled for 1.5.2 must be recompiled in order to work with 2.0.  On
Windows, it's not possible for Python 2.0 to import a third party
extension built for Python 1.5.x due to how Windows DLLs work, so Python
will raise an exception and the import will fail.

Users of Jim Fulton's ExtensionClass module will be pleased to find out
that hooks have been added so that ExtensionClasses are now supported by
*note isinstance(): 3e8. and *note issubclass(): 765.  This means you no
longer have to remember to write code such as ‘if type(obj) ==
myExtensionClass’, but can use the more natural ‘if isinstance(obj,
myExtensionClass)’.

The ‘Python/importdl.c’ file, which was a mass of #ifdefs to support
dynamic loading on many different platforms, was cleaned up and
reorganised by Greg Stein.  ‘importdl.c’ is now quite small, and
platform-specific code has been moved into a bunch of
‘Python/dynload_*.c’ files.  Another cleanup: there were also a number
of ‘my*.h’ files in the Include/ directory that held various portability
hacks; they've been merged into a single file, ‘Include/pyport.h’.

Vladimir Marangozov's long-awaited malloc restructuring was completed,
to make it easy to have the Python interpreter use a custom allocator
instead of C's standard ‘malloc()’.  For documentation, read the
comments in ‘Include/pymem.h’ and ‘Include/objimpl.h’.  For the lengthy
discussions during which the interface was hammered out, see the web
archives of the 'patches' and 'python-dev' lists at python.org.

Recent versions of the GUSI development environment for MacOS support
POSIX threads.  Therefore, Python's POSIX threading support now works on
the Macintosh.  Threading support using the user-space GNU ‘pth’ library
was also contributed.

Threading support on Windows was enhanced, too.  Windows supports thread
locks that use kernel objects only in case of contention; in the common
case when there's no contention, they use simpler functions which are an
order of magnitude faster.  A threaded version of Python 1.5.2 on NT is
twice as slow as an unthreaded version; with the 2.0 changes, the
difference is only 10%.  These improvements were contributed by Yakov
Markovitch.

Python 2.0's source now uses only ANSI C prototypes, so compiling Python
now requires an ANSI C compiler, and can no longer be done using a
compiler that only supports K&R C.

Previously the Python virtual machine used 16-bit numbers in its
bytecode, limiting the size of source files.  In particular, this
affected the maximum size of literal lists and dictionaries in Python
source; occasionally people who are generating Python code would run
into this limit.  A patch by Charles G. Waldman raises the limit from
‘2**16’ to ‘2**32’.

Three new convenience functions intended for adding constants to a
module's dictionary at module initialization time were added: *note
PyModule_AddObject(): 309, *note PyModule_AddIntConstant(): 14aa, and
*note PyModule_AddStringConstant(): 14ab.  Each of these functions takes
a module object, a null-terminated C string containing the name to be
added, and a third argument for the value to be assigned to the name.
This third argument is, respectively, a Python object, a C long, or a C
string.

A wrapper API was added for Unix-style signal handlers.  *note
PyOS_getsig(): 14ac. gets a signal handler and *note PyOS_setsig():
14ad. will set a new handler.


File: python.info,  Node: Distutils Making Modules Easy to Install,  Next: XML 模組,  Prev: Extending/Embedding Changes,  Up: Python 2 0 有什麼新功能

1.22.12 Distutils: Making Modules Easy to Install
-------------------------------------------------

Before Python 2.0, installing modules was a tedious affair - there was
no way to figure out automatically where Python is installed, or what
compiler options to use for extension modules.  Software authors had to
go through an arduous ritual of editing Makefiles and configuration
files, which only really work on Unix and leave Windows and MacOS
unsupported.  Python users faced wildly differing installation
instructions which varied between different extension packages, which
made administering a Python installation something of a chore.

The SIG for distribution utilities, shepherded by Greg Ward, has created
the Distutils, a system to make package installation much easier.  They
form the ‘distutils’ package, a new part of Python's standard library.
In the best case, installing a Python module from source will require
the same steps: first you simply mean unpack the tarball or zip archive,
and the run "‘python setup.py install’".  The platform will be
automatically detected, the compiler will be recognized, C extension
modules will be compiled, and the distribution installed into the proper
directory.  Optional command-line arguments provide more control over
the installation process, the distutils package offers many places to
override defaults - separating the build from the install, building or
installing in non-default directories, and more.

In order to use the Distutils, you need to write a ‘setup.py’ script.
For the simple case, when the software contains only .py files, a
minimal ‘setup.py’ can be just a few lines long:

     from distutils.core import setup
     setup (name = "foo", version = "1.0",
            py_modules = ["module1", "module2"])

The ‘setup.py’ file isn't much more complicated if the software consists
of a few packages:

     from distutils.core import setup
     setup (name = "foo", version = "1.0",
            packages = ["package", "package.subpackage"])

A C extension can be the most complicated case; here's an example taken
from the PyXML package:

     from distutils.core import setup, Extension

     expat_extension = Extension('xml.parsers.pyexpat',
          define_macros = [('XML_NS', None)],
          include_dirs = [ 'extensions/expat/xmltok',
                           'extensions/expat/xmlparse' ],
          sources = [ 'extensions/pyexpat.c',
                      'extensions/expat/xmltok/xmltok.c',
                      'extensions/expat/xmltok/xmlrole.c', ]
            )
     setup (name = "PyXML", version = "0.5.4",
            ext_modules =[ expat_extension ] )

The Distutils can also take care of creating source and binary
distributions.  The "sdist" command, run by "‘python setup.py sdist’',
builds a source distribution such as ‘foo-1.0.tar.gz’.  Adding new
commands isn't difficult, "bdist_rpm" and "bdist_wininst" commands have
already been contributed to create an RPM distribution and a Windows
installer for the software, respectively.  Commands to create other
distribution formats such as Debian packages and Solaris ‘.pkg’ files
are in various stages of development.

All this is documented in a new manual, 'Distributing Python Modules',
that joins the basic set of Python documentation.


File: python.info,  Node: XML 模組,  Next: 模組變更,  Prev: Distutils Making Modules Easy to Install,  Up: Python 2 0 有什麼新功能

1.22.13 XML 模組
----------------

Python 1.5.2 included a simple XML parser in the form of the ‘xmllib’
module, contributed by Sjoerd Mullender.  Since 1.5.2's release, two
different interfaces for processing XML have become common: SAX2
(version 2 of the Simple API for XML) provides an event-driven interface
with some similarities to ‘xmllib’, and the DOM (Document Object Model)
provides a tree-based interface, transforming an XML document into a
tree of nodes that can be traversed and modified.  Python 2.0 includes a
SAX2 interface and a stripped-down DOM interface as part of the *note
xml: 107. package.  Here we will give a brief overview of these new
interfaces; consult the Python documentation or the source code for
complete details.  The Python XML SIG is also working on improved
documentation.

* Menu:

* SAX2 支援::
* DOM 支援::
* Relationship to PyXML::


File: python.info,  Node: SAX2 支援,  Next: DOM 支援,  Up: XML 模組

1.22.13.1 SAX2 支援
...................

SAX defines an event-driven interface for parsing XML. To use SAX, you
must write a SAX handler class.  Handler classes inherit from various
classes provided by SAX, and override various methods that will then be
called by the XML parser.  For example, the *note startElement(): 14b1.
and *note endElement(): 14b2. methods are called for every starting and
end tag encountered by the parser, the *note characters(): 14b3. method
is called for every chunk of character data, and so forth.

The advantage of the event-driven approach is that the whole document
doesn't have to be resident in memory at any one time, which matters if
you are processing really huge documents.  However, writing the SAX
handler class can get very complicated if you're trying to modify the
document structure in some elaborate way.

For example, this little example program defines a handler that prints a
message for every starting and ending tag, and then parses the file
‘hamlet.xml’ using it:

     from xml import sax

     class SimpleHandler(sax.ContentHandler):
         def startElement(self, name, attrs):
             print 'Start of element:', name, attrs.keys()

         def endElement(self, name):
             print 'End of element:', name

     # Create a parser object
     parser = sax.make_parser()

     # Tell it what handler to use
     handler = SimpleHandler()
     parser.setContentHandler( handler )

     # Parse a file!
     parser.parse( 'hamlet.xml' )

For more information, consult the Python documentation, or the XML HOWTO
at ‘https://pyxml.sourceforge.net/topics/howto/xml-howto.html’.


File: python.info,  Node: DOM 支援,  Next: Relationship to PyXML,  Prev: SAX2 支援,  Up: XML 模組

1.22.13.2 DOM 支援
..................

The Document Object Model is a tree-based representation for an XML
document.  A top-level ‘Document’ instance is the root of the tree, and
has a single child which is the top-level ‘Element’ instance.  This
‘Element’ has children nodes representing character data and any
sub-elements, which may have further children of their own, and so
forth.  Using the DOM you can traverse the resulting tree any way you
like, access element and attribute values, insert and delete nodes, and
convert the tree back into XML.

The DOM is useful for modifying XML documents, because you can create a
DOM tree, modify it by adding new nodes or rearranging subtrees, and
then produce a new XML document as output.  You can also construct a DOM
tree manually and convert it to XML, which can be a more flexible way of
producing XML output than simply writing ‘<tag1>’...‘</tag1>’ to a file.

The DOM implementation included with Python lives in the *note
xml.dom.minidom: 109. module.  It's a lightweight implementation of the
Level 1 DOM with support for XML namespaces.  The ‘parse()’ and
‘parseString()’ convenience functions are provided for generating a DOM
tree:

     from xml.dom import minidom
     doc = minidom.parse('hamlet.xml')

‘doc’ is a ‘Document’ instance.  ‘Document’, like all the other DOM
classes such as ‘Element’ and ‘Text’, is a subclass of the ‘Node’ base
class.  All the nodes in a DOM tree therefore support certain common
methods, such as ‘toxml()’ which returns a string containing the XML
representation of the node and its children.  Each class also has
special methods of its own; for example, ‘Element’ and ‘Document’
instances have a method to find all child elements with a given tag
name.  Continuing from the previous 2-line example:

     perslist = doc.getElementsByTagName( 'PERSONA' )
     print perslist[0].toxml()
     print perslist[1].toxml()

For the 'Hamlet' XML file, the above few lines output:

     <PERSONA>CLAUDIUS, king of Denmark. </PERSONA>
     <PERSONA>HAMLET, son to the late, and nephew to the present king.</PERSONA>

The root element of the document is available as ‘doc.documentElement’,
and its children can be easily modified by deleting, adding, or removing
nodes:

     root = doc.documentElement

     # Remove the first child
     root.removeChild( root.childNodes[0] )

     # Move the new first child to the end
     root.appendChild( root.childNodes[0] )

     # Insert the new first child (originally,
     # the third child) before the 20th child.
     root.insertBefore( root.childNodes[0], root.childNodes[20] )

Again, I will refer you to the Python documentation for a complete
listing of the different ‘Node’ classes and their various methods.


File: python.info,  Node: Relationship to PyXML,  Prev: DOM 支援,  Up: XML 模組

1.22.13.3 Relationship to PyXML
...............................

The XML Special Interest Group has been working on XML-related Python
code for a while.  Its code distribution, called PyXML, is available
from the SIG's web pages at
‘https://www.python.org/community/sigs/current/xml-sig’.  The PyXML
distribution also used the package name ‘xml’.  If you've written
programs that used PyXML, you're probably wondering about its
compatibility with the 2.0 *note xml: 107. package.

The answer is that Python 2.0's *note xml: 107. package isn't compatible
with PyXML, but can be made compatible by installing a recent version
PyXML. Many applications can get by with the XML support that is
included with Python 2.0, but more complicated applications will require
that the full PyXML package will be installed.  When installed, PyXML
versions 0.6.0 or greater will replace the *note xml: 107. package
shipped with Python, and will be a strict superset of the standard
package, adding a bunch of additional features.  Some of the additional
features in PyXML include:

   * 4DOM, a full DOM implementation from FourThought, Inc.

   * The xmlproc validating parser, written by Lars Marius Garshol.

   * The ‘sgmlop’ parser accelerator module, written by Fredrik Lundh.


File: python.info,  Node: 模組變更,  Next: 新增模組<5>,  Prev: XML 模組,  Up: Python 2 0 有什麼新功能

1.22.14 模組變更
----------------

Lots of improvements and bugfixes were made to Python's extensive
standard library; some of the affected modules include *note readline:
a8, *note ConfigParser: 1b, ‘cgi’, *note calendar: 10, *note posix: 9b,
*note readline: a8, ‘xmllib’, ‘aifc’, ‘chunk’, *note wave: fb, *note
random: a6, *note shelve: b1, and ‘nntplib’.  Consult the CVS logs for
the exact patch-by-patch details.

Brian Gallew contributed OpenSSL support for the *note socket: b8.
module.  OpenSSL is an implementation of the Secure Socket Layer, which
encrypts the data being sent over a socket.  When compiling Python, you
can edit ‘Modules/Setup’ to include SSL support, which adds an
additional function to the *note socket: b8. module: ‘socket.ssl(socket,
keyfile, certfile)’, which takes a socket object and returns an SSL
socket.  The *note httplib: 64. and *note urllib: f1. modules were also
changed to support ‘https://’ URLs, though no one has implemented FTP or
SMTP over SSL.

The *note httplib: 64. module has been rewritten by Greg Stein to
support HTTP/1.1.

Backward compatibility with the 1.5 version of ‘httplib’ is provided,
though using HTTP/1.1 features such as pipelining will require rewriting
code to use a different set of interfaces.

The ‘Tkinter’ module now supports Tcl/Tk version 8.1, 8.2, or 8.3, and
support for the older 7.x versions has been dropped.  The Tkinter module
now supports displaying Unicode strings in Tk widgets.  Also, Fredrik
Lundh contributed an optimization which makes operations like
‘create_line’ and ‘create_polygon’ much faster, especially when using
lots of coordinates.

The *note curses: 23. module has been greatly extended, starting from
Oliver Andrich's enhanced version, to provide many additional functions
from ncurses and SYSV curses, such as colour, alternative character set
support, pads, and mouse support.  This means the module is no longer
compatible with operating systems that only have BSD curses, but there
don't seem to be any currently maintained OSes that fall into this
category.

As mentioned in the earlier discussion of 2.0's Unicode support, the
underlying implementation of the regular expressions provided by the
*note re: a7. module has been changed.  SRE, a new regular expression
engine written by Fredrik Lundh and partially funded by Hewlett Packard,
supports matching against both 8-bit strings and Unicode strings.


File: python.info,  Node: 新增模組<5>,  Next: IDLE Improvements,  Prev: 模組變更,  Up: Python 2 0 有什麼新功能

1.22.15 新增模組
----------------

A number of new modules were added.  We'll simply list them with brief
descriptions; consult the 2.0 documentation for the details of a
particular module.

   * *note atexit: 9.: For registering functions to be called before the
     Python interpreter exits.  Code that currently sets ‘sys.exitfunc’
     directly should be changed to use the *note atexit: 9. module
     instead, importing *note atexit: 9. and calling *note
     atexit.register(): 821. with the function to be called on exit.
     (Contributed by Skip Montanaro.)

   * *note codecs: 14, ‘encodings’, *note unicodedata: ee.: Added as
     part of the new Unicode support.

   * *note filecmp: 50.: Supersedes the old ‘cmp’, ‘cmpcache’ and
     ‘dircmp’ modules, which have now become deprecated.  (Contributed
     by Gordon MacMillan and Moshe Zadka.)

   * *note gettext: 59.: This module provides internationalization
     (I18N) and localization (L10N) support for Python programs by
     providing an interface to the GNU gettext message catalog library.
     (Integrated by Barry Warsaw, from separate contributions by Martin
     von Löwis, Peter Funk, and James Henstridge.)

   * ‘linuxaudiodev’: Support for the ‘/dev/audio’ device on Linux, a
     twin to the existing ‘sunaudiodev’ module.  (Contributed by Peter
     Bosch, with fixes by Jeremy Hylton.)

   * *note mmap: 83.: An interface to memory-mapped files on both
     Windows and Unix.  A file's contents can be mapped directly into
     memory, at which point it behaves like a mutable string, so its
     contents can be read and modified.  They can even be passed to
     functions that expect ordinary strings, such as the *note re: a7.
     module.  (Contributed by Sam Rushing, with some extensions by A.M.
     Kuchling.)

   * ‘pyexpat’: An interface to the Expat XML parser.  (Contributed by
     Paul Prescod.)

   * *note robotparser: f6.: Parse a ‘robots.txt’ file, which is used
     for writing web spiders that politely avoid certain areas of a web
     site.  The parser accepts the contents of a ‘robots.txt’ file,
     builds a set of rules from it, and can then answer questions about
     the fetchability of a given URL. (Contributed by Skip Montanaro.)

   * *note tabnanny: c7.: A module/script to check Python source code
     for ambiguous indentation.  (Contributed by Tim Peters.)

   * ‘UserString’: A base class useful for deriving objects that behave
     like strings.

   * *note webbrowser: fd.: A module that provides a platform
     independent way to launch a web browser on a specific URL. For each
     platform, various browsers are tried in a specific order.  The user
     can alter which browser is launched by setting the 'BROWSER'
     environment variable.  (Originally inspired by Eric S. Raymond's
     patch to *note urllib: f1. which added similar functionality, but
     the final module comes from code originally implemented by Fred
     Drake as ‘Tools/idle/BrowserControl.py’, and adapted for the
     standard library by Fred.)

   * *note _winreg: fe.: An interface to the Windows registry.
     ‘_winreg’ is an adaptation of functions that have been part of
     PythonWin since 1995, but has now been added to the core
     distribution, and enhanced to support Unicode.  ‘_winreg’ was
     written by Bill Tutt and Mark Hammond.

   * *note zipfile: 117.: A module for reading and writing ZIP-format
     archives.  These are archives produced by ‘PKZIP’ on DOS/Windows or
     ‘zip’ on Unix, not to be confused with ‘gzip’-format files (which
     are supported by the *note gzip: 5d. module) (Contributed by James
     C. Ahlstrom.)

   * ‘imputil’: A module that provides a simpler way for writing
     customized import hooks, in comparison to the existing ‘ihooks’
     module.  (Implemented by Greg Stein, with much discussion on
     python-dev along the way.)


File: python.info,  Node: IDLE Improvements,  Next: Deleted and Deprecated Modules,  Prev: 新增模組<5>,  Up: Python 2 0 有什麼新功能

1.22.16 IDLE Improvements
-------------------------

IDLE is the official Python cross-platform IDE, written using Tkinter.
Python 2.0 includes IDLE 0.6, which adds a number of new features and
improvements.  A partial list:

   * UI improvements and optimizations, especially in the area of syntax
     highlighting and auto-indentation.

   * The class browser now shows more information, such as the top level
     functions in a module.

   * Tab width is now a user settable option.  When opening an existing
     Python file, IDLE automatically detects the indentation
     conventions, and adapts.

   * There is now support for calling browsers on various platforms,
     used to open the Python documentation in a browser.

   * IDLE now has a command line, which is largely similar to the
     vanilla Python interpreter.

   * Call tips were added in many places.

   * IDLE can now be installed as a package.

   * In the editor window, there is now a line/column bar at the bottom.

   * Three new keystroke commands: Check module (‘Alt-F5’), Import
     module (‘F5’) and Run script (‘Ctrl-F5’).


File: python.info,  Node: Deleted and Deprecated Modules,  Next: 致謝<8>,  Prev: IDLE Improvements,  Up: Python 2 0 有什麼新功能

1.22.17 Deleted and Deprecated Modules
--------------------------------------

A few modules have been dropped because they're obsolete, or because
there are now better ways to do the same thing.  The ‘stdwin’ module is
gone; it was for a platform-independent windowing toolkit that's no
longer developed.

A number of modules have been moved to the ‘lib-old’ subdirectory:
‘cmp’, ‘cmpcache’, ‘dircmp’, ‘dump’, ‘find’, ‘grep’, ‘packmail’, ‘poly’,
‘util’, ‘whatsound’, ‘zmod’.  If you have code which relies on a module
that's been moved to ‘lib-old’, you can simply add that directory to
‘sys.path’ to get them back, but you're encouraged to update any code
that uses these modules.


File: python.info,  Node: 致謝<8>,  Prev: Deleted and Deprecated Modules,  Up: Python 2 0 有什麼新功能

1.22.18 致謝
------------

The authors would like to thank the following people for offering
suggestions on various drafts of this article: David Bolen, Mark
Hammond, Gregg Hauser, Jeremy Hylton, Fredrik Lundh, Detlef Lannert,
Aahz Maruch, Skip Montanaro, Vladimir Marangozov, Tobias Polzin, Guido
van Rossum, Neil Schemenauer, and Russ Schmidt.

「Changelog（更動日誌）」是從 Misc/NEWS.d(1) 目錄樹內容檔案建置(2)的一個
HTML 版本，其中包含了 Python 目前版本中的'所有'重要變更。

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Misc/NEWS.d

   (2) https://pypi.org/project/blurb/


File: python.info,  Node: Changelog（更動日誌）,  Prev: Python 2 0 有什麼新功能,  Up: Python 有什麼新功能？

1.23 Changelog（更動日誌）
==========================

* Menu:

* Python next::
* Python 3.13.0 release candidate 2: Python 3 13 0 release candidate 2.
* Python 3.13.0 release candidate 1: Python 3 13 0 release candidate 1.
* Python 3.13.0 beta 4: Python 3 13 0 beta 4.
* Python 3.13.0 beta 3: Python 3 13 0 beta 3.
* Python 3.13.0 beta 2: Python 3 13 0 beta 2.
* Python 3.13.0 beta 1: Python 3 13 0 beta 1.
* Python 3.13.0 alpha 6: Python 3 13 0 alpha 6.
* Python 3.13.0 alpha 5: Python 3 13 0 alpha 5.
* Python 3.13.0 alpha 4: Python 3 13 0 alpha 4.
* Python 3.13.0 alpha 3: Python 3 13 0 alpha 3.
* Python 3.13.0 alpha 2: Python 3 13 0 alpha 2.
* Python 3.13.0 alpha 1: Python 3 13 0 alpha 1.
* Python 3.12.0 beta 1: Python 3 12 0 beta 1.
* Python 3.12.0 alpha 7: Python 3 12 0 alpha 7.
* Python 3.12.0 alpha 6: Python 3 12 0 alpha 6.
* Python 3.12.0 alpha 5: Python 3 12 0 alpha 5.
* Python 3.12.0 alpha 4: Python 3 12 0 alpha 4.
* Python 3.12.0 alpha 3: Python 3 12 0 alpha 3.
* Python 3.12.0 alpha 2: Python 3 12 0 alpha 2.
* Python 3.12.0 alpha 1: Python 3 12 0 alpha 1.
* Python 3.11.0 beta 1: Python 3 11 0 beta 1.
* Python 3.11.0 alpha 7: Python 3 11 0 alpha 7.
* Python 3.11.0 alpha 6: Python 3 11 0 alpha 6.
* Python 3.11.0 alpha 5: Python 3 11 0 alpha 5.
* Python 3.11.0 alpha 4: Python 3 11 0 alpha 4.
* Python 3.11.0 alpha 3: Python 3 11 0 alpha 3.
* Python 3.11.0 alpha 2: Python 3 11 0 alpha 2.
* Python 3.11.0 alpha 1: Python 3 11 0 alpha 1.
* Python 3.10.0 beta 1: Python 3 10 0 beta 1.
* Python 3.10.0 alpha 7: Python 3 10 0 alpha 7.
* Python 3.10.0 alpha 6: Python 3 10 0 alpha 6.
* Python 3.10.0 alpha 5: Python 3 10 0 alpha 5.
* Python 3.10.0 alpha 4: Python 3 10 0 alpha 4.
* Python 3.10.0 alpha 3: Python 3 10 0 alpha 3.
* Python 3.10.0 alpha 2: Python 3 10 0 alpha 2.
* Python 3.10.0 alpha 1: Python 3 10 0 alpha 1.
* Python 3.9.0 beta 1: Python 3 9 0 beta 1.
* Python 3.9.0 alpha 6: Python 3 9 0 alpha 6.
* Python 3.9.0 alpha 5: Python 3 9 0 alpha 5.
* Python 3.9.0 alpha 4: Python 3 9 0 alpha 4.
* Python 3.9.0 alpha 3: Python 3 9 0 alpha 3.
* Python 3.9.0 alpha 2: Python 3 9 0 alpha 2.
* Python 3.9.0 alpha 1: Python 3 9 0 alpha 1.
* Python 3.8.0 beta 1: Python 3 8 0 beta 1.
* Python 3.8.0 alpha 4: Python 3 8 0 alpha 4.
* Python 3.8.0 alpha 3: Python 3 8 0 alpha 3.
* Python 3.8.0 alpha 2: Python 3 8 0 alpha 2.
* Python 3.8.0 alpha 1: Python 3 8 0 alpha 1.
* Python 3.7.0 final: Python 3 7 0 final.
* Python 3.7.0 release candidate 1: Python 3 7 0 release candidate 1.
* Python 3.7.0 beta 5: Python 3 7 0 beta 5.
* Python 3.7.0 beta 4: Python 3 7 0 beta 4.
* Python 3.7.0 beta 3: Python 3 7 0 beta 3.
* Python 3.7.0 beta 2: Python 3 7 0 beta 2.
* Python 3.7.0 beta 1: Python 3 7 0 beta 1.
* Python 3.7.0 alpha 4: Python 3 7 0 alpha 4.
* Python 3.7.0 alpha 3: Python 3 7 0 alpha 3.
* Python 3.7.0 alpha 2: Python 3 7 0 alpha 2.
* Python 3.7.0 alpha 1: Python 3 7 0 alpha 1.
* Python 3.6.6 final: Python 3 6 6 final.
* Python 3.6.6 release candidate 1: Python 3 6 6 release candidate 1.
* Python 3.6.5 final: Python 3 6 5 final.
* Python 3.6.5 release candidate 1: Python 3 6 5 release candidate 1.
* Python 3.6.4 final: Python 3 6 4 final.
* Python 3.6.4 release candidate 1: Python 3 6 4 release candidate 1.
* Python 3.6.3 final: Python 3 6 3 final.
* Python 3.6.3 release candidate 1: Python 3 6 3 release candidate 1.
* Python 3.6.2 final: Python 3 6 2 final.
* Python 3.6.2 release candidate 2: Python 3 6 2 release candidate 2.
* Python 3.6.2 release candidate 1: Python 3 6 2 release candidate 1.
* Python 3.6.1 final: Python 3 6 1 final.
* Python 3.6.1 release candidate 1: Python 3 6 1 release candidate 1.
* Python 3.6.0 final: Python 3 6 0 final.
* Python 3.6.0 release candidate 2: Python 3 6 0 release candidate 2.
* Python 3.6.0 release candidate 1: Python 3 6 0 release candidate 1.
* Python 3.6.0 beta 4: Python 3 6 0 beta 4.
* Python 3.6.0 beta 3: Python 3 6 0 beta 3.
* Python 3.6.0 beta 2: Python 3 6 0 beta 2.
* Python 3.6.0 beta 1: Python 3 6 0 beta 1.
* Python 3.6.0 alpha 4: Python 3 6 0 alpha 4.
* Python 3.6.0 alpha 3: Python 3 6 0 alpha 3.
* Python 3.6.0 alpha 2: Python 3 6 0 alpha 2.
* Python 3.6.0 alpha 1: Python 3 6 0 alpha 1.
* Python 3.5.5 final: Python 3 5 5 final.
* Python 3.5.5 release candidate 1: Python 3 5 5 release candidate 1.
* Python 3.5.4 final: Python 3 5 4 final.
* Python 3.5.4 release candidate 1: Python 3 5 4 release candidate 1.
* Python 3.5.3 final: Python 3 5 3 final.
* Python 3.5.3 release candidate 1: Python 3 5 3 release candidate 1.
* Python 3.5.2 final: Python 3 5 2 final.
* Python 3.5.2 release candidate 1: Python 3 5 2 release candidate 1.
* Python 3.5.1 final: Python 3 5 1 final.
* Python 3.5.1 release candidate 1: Python 3 5 1 release candidate 1.
* Python 3.5.0 final: Python 3 5 0 final.
* Python 3.5.0 release candidate 4: Python 3 5 0 release candidate 4.
* Python 3.5.0 release candidate 3: Python 3 5 0 release candidate 3.
* Python 3.5.0 release candidate 2: Python 3 5 0 release candidate 2.
* Python 3.5.0 release candidate 1: Python 3 5 0 release candidate 1.
* Python 3.5.0 beta 4: Python 3 5 0 beta 4.
* Python 3.5.0 beta 3: Python 3 5 0 beta 3.
* Python 3.5.0 beta 2: Python 3 5 0 beta 2.
* Python 3.5.0 beta 1: Python 3 5 0 beta 1.
* Python 3.5.0 alpha 4: Python 3 5 0 alpha 4.
* Python 3.5.0 alpha 3: Python 3 5 0 alpha 3.
* Python 3.5.0 alpha 2: Python 3 5 0 alpha 2.
* Python 3.5.0 alpha 1: Python 3 5 0 alpha 1.


File: python.info,  Node: Python next,  Next: Python 3 13 0 release candidate 2,  Up: Changelog（更動日誌）

1.23.1 Python next
------------------

'Release date: XXXX-XX-XX'

* Menu:

* Core and Builtins::


File: python.info,  Node: Core and Builtins,  Up: Python next

1.23.1.1 Core and Builtins
..........................

   - gh-124027(1): Support ‘<page up>’, ‘<page down>’, and ‘<delete>’
     keys in the Python REPL when ‘$TERM’ is set to ‘vt100’.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/124027


File: python.info,  Node: Python 3 13 0 release candidate 2,  Next: Python 3 13 0 release candidate 1,  Prev: Python next,  Up: Changelog（更動日誌）

1.23.2 Python 3.13.0 release candidate 2
----------------------------------------

'Release date: 2024-09-06'

* Menu:

* macOS::
* Windows::
* Tools/Demos::
* Tests::
* Security::
* Library::
* IDLE: IDLE<3>.
* Core and Builtins: Core and Builtins<2>.
* C API::
* Build::


File: python.info,  Node: macOS,  Next: Windows,  Up: Python 3 13 0 release candidate 2

1.23.2.1 macOS
..............

   - gh-123418(1): Updated macOS installer build to use OpenSSL 3.0.15.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/123418


File: python.info,  Node: Windows,  Next: Tools/Demos,  Prev: macOS,  Up: Python 3 13 0 release candidate 2

1.23.2.2 Windows
................

   - gh-123418(1): Updated Windows build to use OpenSSL 3.0.15.

   - gh-122573(2): The Windows build of CPython now requires 3.10 or
     newer.

   - gh-100256(3): *note mimetypes: 82. no longer fails when it
     encounters an inaccessible registry key.

   - gh-79846(4): Makes ‘ssl.create_default_context()’ ignore invalid
     certificates in the Windows certificate store

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/123418

   (2) https://github.com/python/cpython/issues/122573

   (3) https://github.com/python/cpython/issues/100256

   (4) https://github.com/python/cpython/issues/79846


File: python.info,  Node: Tools/Demos,  Next: Tests,  Prev: Windows,  Up: Python 3 13 0 release candidate 2

1.23.2.3 Tools/Demos
....................

   - gh-123418(1): Update GitHub CI workflows to use OpenSSL 3.0.15 and
     multissltests to use 3.0.15, 3.1.7, and 3.2.3.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/123418


File: python.info,  Node: Tests,  Next: Security,  Prev: Tools/Demos,  Up: Python 3 13 0 release candidate 2

1.23.2.4 Tests
..............

   - gh-119727(1): Add ‘--single-process’ command line option to Python
     test runner (regrtest).  Patch by Victor Stinner.

   - gh-101525(2): Skip ‘test_gdb’ if the binary is relocated by BOLT.
     Patch by Donghee Na.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/119727

   (2) https://github.com/python/cpython/issues/101525


File: python.info,  Node: Security,  Next: Library,  Prev: Tests,  Up: Python 3 13 0 release candidate 2

1.23.2.5 Security
.................

   - gh-123678(1): Upgrade libexpat to 2.6.3

   - gh-121285(2): Remove backtracking from tarfile header parsing for
     ‘hdrcharset’, PAX, and GNU sparse headers.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/123678

   (2) https://github.com/python/cpython/issues/121285


File: python.info,  Node: Library,  Next: IDLE<3>,  Prev: Security,  Up: Python 3 13 0 release candidate 2

1.23.2.6 Library
................

   - gh-123657(1): Fix crash and memory leak in *note
     decimal.getcontext(): 14c6.  It crashed when using a thread-local
     context by ‘--with-decimal-contextvar=no’.

   - gh-123448(2): Fixed memory leak of *note typing.NoDefault: 247. by
     moving it to the static types array.

   - gh-123409(3): Fix *note ipaddress.IPv6Address.reverse_pointer:
     14c7. output according to RFC 3596, §2.5(4).  Patch by Bénédikt
     Tran.

   - gh-123270(5): Applied a more surgical fix for malformed payloads in
     *note zipfile.Path: 66b. causing infinite loops (gh-122905(6))
     without breaking contents using legitimate characters.

   - gh-123228(7): Fix return type for
     ‘_pyrepl.readline._ReadlineWrapper.get_line_buffer()’ to be *note
     str(): 3f2.  Patch by Sergey B Kirpichev.

   - gh-123240(8): Raise audit events for the *note input(): 126b. in
     the new REPL.

   - gh-123243(9): Fix memory leak in ‘_decimal’.

   - gh-122546(10): Consistently use same file name for different
     exceptions in the new repl.  Patch by Sergey B Kirpichev.

   - gh-123213(11): *note xml.etree.ElementTree.Element.extend(): 116b.
     and *note Element: 2e2. assignment no longer hide the internal
     exception if an erronous generator is passed.  Patch by Bar Harel.

   - gh-85110(12): Preserve relative path in URL without netloc in *note
     urllib.parse.urlunsplit(): 14c8. and *note
     urllib.parse.urlunparse(): 14c9.

   - gh-123067(13): Fix quadratic complexity in parsing ‘"’-quoted
     cookie values with backslashes by *note http.cookies: 67.

   - gh-122981(14): Fix *note inspect.getsource(): 14ca. for generated
     classes with Python base classes (e.g.  enums).

   - gh-122903(15): ‘zipfile.Path.glob’ now correctly matches
     directories instead of silently omitting them.

   - gh-122905(16): *note zipfile.Path: 66b. objects now sanitize names
     from the zipfile.

   - gh-122695(17): Fixed double-free when using *note
     gc.get_referents(): 7a9. with a freed *note asyncio.Future: b74.
     iterator.

   - gh-116263(18): *note logging.handlers.RotatingFileHandler: 14cb. no
     longer rolls over empty log files.

   - gh-105376(19): Restore the deprecated *note logging: 7b. ‘warn()’
     method.  It was removed in Python 3.13 alpha 1.  Keep the
     deprecated ‘warn()’ method in Python 3.13.  Patch by Victor
     Stinner.

   - gh-122744(20): Bump the version of pip bundled in ensurepip to
     version 24.2.

   - gh-118814(21): Fix the *note typing.TypeVar: 141. constructor when
     name is passed by keyword.

   - gh-122478(22): Remove internal frames from tracebacks shown in
     *note code.InteractiveInterpreter: 14cc. with non-default *note
     sys.excepthook(): 7af.  Save correct tracebacks in *note
     sys.last_traceback: 468. and update ‘__traceback__’ attribute of
     *note sys.last_value: 467. and *note sys.last_exc: 465.

   - gh-116622(23): On Android, the ‘FICLONE’ and ‘FICLONERANGE’
     constants are no longer exposed by *note fcntl: 4f, as these ioctls
     are blocked by SELinux.

   - gh-82378(24): Make sure that the new *note REPL: 14e. interprets
     *note sys.tracebacklimit: 14cd. in the same way that the classic
     REPL did.

   - gh-122334(25): Fix crash when importing *note ssl: bb. after the
     main interpreter restarts.

   - gh-87320(26): In *note code.InteractiveInterpreter: 14cc, handle
     exceptions caused by calling a non-default *note sys.excepthook():
     7af.  Before, the exception bubbled up to the caller, ending the
     *note REPL: 14e.

   - gh-121650(27): *note email: 32. headers with embedded newlines are
     now quoted on output.  The *note generator: 37. will now refuse to
     serialize (write) headers that are unsafely folded or delimited;
     see *note verify_generated_headers: 1c3.  (Contributed by Bas
     Bloemsaat and Petr Viktorin in gh-121650(28).)

   - gh-121723(29): Make *note logging.config.dictConfig(): 1147. accept
     any object implementing the Queue public API. See the *note queue
     configuration: 14ce. section for details.  Patch by Bénédikt Tran.

   - gh-122081(30): Fix a crash in the ‘decimal.IEEEContext()’ optional
     function available via the ‘EXTRA_FUNCTIONALITY’ configuration
     flag.

   - gh-121804(31): Correctly show error locations, when *note
     SyntaxError: 173. raised in new repl.  Patch by Sergey B Kirpichev.

   - gh-121151(32): Fix wrapping of long usage text of arguments inside
     a mutually exclusive group in *note argparse: 5.

   - gh-108172(33): ‘webbrowser’ honors OS preferred browser on Linux
     when its desktop entry name contains the text of a known browser
     name.

   - gh-109109(34): You can now get the raw TLS certificate chains from
     TLS connections via *note ssl.SSLSocket.get_verified_chain(): 14cf.
     and *note ssl.SSLSocket.get_unverified_chain(): 14d0. methods.

     Contributed by Mateusz Nowak.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/123657

   (2) https://github.com/python/cpython/issues/123448

   (3) https://github.com/python/cpython/issues/123409

   (4) https://datatracker.ietf.org/doc/html/rfc3596.html#section-2.5

   (5) https://github.com/python/cpython/issues/123270

   (6) https://github.com/python/cpython/issues/122905

   (7) https://github.com/python/cpython/issues/123228

   (8) https://github.com/python/cpython/issues/123240

   (9) https://github.com/python/cpython/issues/123243

   (10) https://github.com/python/cpython/issues/122546

   (11) https://github.com/python/cpython/issues/123213

   (12) https://github.com/python/cpython/issues/85110

   (13) https://github.com/python/cpython/issues/123067

   (14) https://github.com/python/cpython/issues/122981

   (15) https://github.com/python/cpython/issues/122903

   (16) https://github.com/python/cpython/issues/122905

   (17) https://github.com/python/cpython/issues/122695

   (18) https://github.com/python/cpython/issues/116263

   (19) https://github.com/python/cpython/issues/105376

   (20) https://github.com/python/cpython/issues/122744

   (21) https://github.com/python/cpython/issues/118814

   (22) https://github.com/python/cpython/issues/122478

   (23) https://github.com/python/cpython/issues/116622

   (24) https://github.com/python/cpython/issues/82378

   (25) https://github.com/python/cpython/issues/122334

   (26) https://github.com/python/cpython/issues/87320

   (27) https://github.com/python/cpython/issues/121650

   (28) https://github.com/python/cpython/issues/121650

   (29) https://github.com/python/cpython/issues/121723

   (30) https://github.com/python/cpython/issues/122081

   (31) https://github.com/python/cpython/issues/121804

   (32) https://github.com/python/cpython/issues/121151

   (33) https://github.com/python/cpython/issues/108172

   (34) https://github.com/python/cpython/issues/109109


File: python.info,  Node: IDLE<3>,  Next: Core and Builtins<2>,  Prev: Library,  Up: Python 3 13 0 release candidate 2

1.23.2.7 IDLE
.............

   - gh-120083(1): Add explicit black IDLE Hovertip foreground color
     needed for recent macOS. Fixes Sonoma showing unreadable white on
     pale yellow.  Patch by John Riggles.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/120083


File: python.info,  Node: Core and Builtins<2>,  Next: C API,  Prev: IDLE<3>,  Up: Python 3 13 0 release candidate 2

1.23.2.8 Core and Builtins
..........................

   - gh-120221(1): asyncio REPL is now again properly recognizing
     KeyboardInterrupts.  Display of exceptions raised in secondary
     threads is fixed.

   - gh-119310(2): Allow the new interactive shell to read history files
     written with the editline library that use unicode-escaped entries.
     Patch by aorcajo and Łukasz Langa.

   - gh-123572(3): Fix key mappings for various F-keys in Windows for
     the new REPL. Patch by devdanzin

   - gh-119034(4): Change ‘<page up>’ and ‘<page down>’ keys of the
     Python REPL to history search forward/backward.  Patch by Victor
     Stinner.

   - gh-123545(5): Fix a double decref in rare cases on experimental JIT
     builds.

   - gh-123484(6): Fix ‘_Py_DebugOffsets’ for long objects to be
     relative to the start of the object rather than the start of a
     subobject.

   - gh-123344(7): Add AST optimizations for type parameter defaults.

   - gh-123321(8): Prevent Parser/myreadline race condition from
     segfaulting on multi-threaded use.  Patch by Bar Harel and Amit
     Wienner.

   - gh-123177(9): Fix a bug causing stray prompts to appear in the
     middle of wrapped lines in the new REPL.

   - gh-122982(10): Extend the deprecation period for bool inversion
     (‘~’) by two years.

   - gh-123275(11): Support *note -X gil=1: 15a. and *note PYTHON_GIL=1:
     159. on non-free-threaded builds.

   - gh-123177(12): Deactivate line wrap in the Apple Terminal via a
     ANSI escape code.  Patch by Pablo Galindo

   - gh-123229(13): Fix valgrind warning by initializing the f-string
     buffers to 0 in the tokenizer.  Patch by Pablo Galindo

   - gh-122298(14): Restore printout of GC stats when
     ‘gc.set_debug(gc.DEBUG_STATS)’ is called.  This featue was
     accidentally removed when implementing incremental GC.

   - gh-121804(15): Correctly show error locations when a *note
     SyntaxError: 173. is raised in the basic REPL. Patch by Sergey B
     Kirpichev.

   - gh-123142(16): Fix too-wide source location in exception tracebacks
     coming from broken iterables in comprehensions.

   - gh-123048(17): Fix a bug where pattern matching code could emit a
     *note JUMP_FORWARD: 14d3. with no source location.

   - gh-123123(18): Fix displaying *note SyntaxError: 173. exceptions
     covering multiple lines.  Patch by Pablo Galindo

   - gh-123083(19): Fix a potential use-after-free in
     ‘STORE_ATTR_WITH_HINT’.

   - gh-123022(20): Fix crash in free-threaded build when calling *note
     Py_Initialize(): 851. from a non-main thread.

   - gh-122888(21): Fix crash on certain calls to ‘str()’ with
     positional arguments of the wrong type.  Patch by Jelle Zijlstra.

   - gh-116622(22): Fix Android stdout and stderr messages being
     truncated or lost.

   - gh-122527(23): Fix a crash that occurred when a ‘PyStructSequence’
     was deallocated after its type's dictionary was cleared by the GC.
     The type's *note tp_basicsize: 92b. now accounts for non-sequence
     fields that aren't included in the *note Py_SIZE: 726. of the
     sequence.

   - gh-122445(24): Add only fields which are modified via self.* to
     *note __static_attributes__: 131.

   - gh-98442(25): Fix too wide source locations of the cleanup
     instructions of a with statement.

   - gh-93691(26): Fix source locations of instructions generated for
     with statements.

   - gh-120097(27): ‘FrameLocalsProxy’ now subclasses
     ‘collections.abc.Mapping’ and can be matched as a mapping in
     ‘match’ statements

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/120221

   (2) https://github.com/python/cpython/issues/119310

   (3) https://github.com/python/cpython/issues/123572

   (4) https://github.com/python/cpython/issues/119034

   (5) https://github.com/python/cpython/issues/123545

   (6) https://github.com/python/cpython/issues/123484

   (7) https://github.com/python/cpython/issues/123344

   (8) https://github.com/python/cpython/issues/123321

   (9) https://github.com/python/cpython/issues/123177

   (10) https://github.com/python/cpython/issues/122982

   (11) https://github.com/python/cpython/issues/123275

   (12) https://github.com/python/cpython/issues/123177

   (13) https://github.com/python/cpython/issues/123229

   (14) https://github.com/python/cpython/issues/122298

   (15) https://github.com/python/cpython/issues/121804

   (16) https://github.com/python/cpython/issues/123142

   (17) https://github.com/python/cpython/issues/123048

   (18) https://github.com/python/cpython/issues/123123

   (19) https://github.com/python/cpython/issues/123083

   (20) https://github.com/python/cpython/issues/123022

   (21) https://github.com/python/cpython/issues/122888

   (22) https://github.com/python/cpython/issues/116622

   (23) https://github.com/python/cpython/issues/122527

   (24) https://github.com/python/cpython/issues/122445

   (25) https://github.com/python/cpython/issues/98442

   (26) https://github.com/python/cpython/issues/93691

   (27) https://github.com/python/cpython/issues/120097


File: python.info,  Node: C API,  Next: Build,  Prev: Core and Builtins<2>,  Up: Python 3 13 0 release candidate 2

1.23.2.9 C API
..............

   - gh-122728(1): Fix *note PyEval_GetLocals(): 34a. to avoid *note
     SystemError: 51b. ("bad argument to internal function").  Patch by
     Victor Stinner.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/122728


File: python.info,  Node: Build,  Prev: C API,  Up: Python 3 13 0 release candidate 2

1.23.2.10 Build
...............

   - gh-123418(1): Updated Android build to use OpenSSL 3.0.15.

   - gh-123297(2): Propagate the value of ‘LDFLAGS’ to ‘LDCXXSHARED’ in
     *note sysconfig: c5.  Patch by Pablo Galindo

   - gh-116622(3): Rename build variable ‘MODULE_LDFLAGS’ back to
     ‘LIBPYTHON’, as it's used by package build systems (e.g.  Meson).

   - gh-118943(4): Fix an issue where the experimental JIT could be
     built several times by the ‘make regen-all’ target, leading to
     possible race conditions on heavily parallelized builds.

   - gh-118943(5): Fix a possible race condition affecting parallel
     builds configured with ‘--enable-experimental-jit’, in which *note
     FileNotFoundError: e67. could be caused by another process already
     moving ‘jit_stencils.h.new’ to ‘jit_stencils.h’.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/123418

   (2) https://github.com/python/cpython/issues/123297

   (3) https://github.com/python/cpython/issues/116622

   (4) https://github.com/python/cpython/issues/118943

   (5) https://github.com/python/cpython/issues/118943


File: python.info,  Node: Python 3 13 0 release candidate 1,  Next: Python 3 13 0 beta 4,  Prev: Python 3 13 0 release candidate 2,  Up: Changelog（更動日誌）

1.23.3 Python 3.13.0 release candidate 1
----------------------------------------

'Release date: 2024-07-31'

* Menu:

* Tests: Tests<2>.
* Security: Security<2>.
* Library: Library<2>.
* IDLE: IDLE<4>.
* Core and Builtins: Core and Builtins<3>.
* C API: C API<2>.
* Build: Build<2>.


File: python.info,  Node: Tests<2>,  Next: Security<2>,  Up: Python 3 13 0 release candidate 1

1.23.3.1 Tests
..............

   - gh-59022(1): Add tests for *note pkgutil.extend_path(): 14d8.
     Patch by Andreas Stocker.

   - gh-99242(2): *note os.getloadavg(): 14d9. may throw *note OSError:
     350. when running regression tests under certain conditions (e.g.
     chroot).  This error is now caught and ignored, since reporting
     load average is optional.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/59022

   (2) https://github.com/python/cpython/issues/99242


File: python.info,  Node: Security<2>,  Next: Library<2>,  Prev: Tests<2>,  Up: Python 3 13 0 release candidate 1

1.23.3.2 Security
.................

   - gh-122133(1): Authenticate the socket connection for the
     ‘socket.socketpair()’ fallback on platforms where ‘AF_UNIX’ is not
     available like Windows.

     Patch by Gregory P. Smith <<greg@krypto.org>> and Seth Larson
     <<seth@python.org>>.  Reported by Ellie <<el@horse64.org>>

   - gh-121957(2): Fixed missing audit events around interactive use of
     Python, now also properly firing for ‘python -i’, as well as for
     ‘python -m asyncio’.  The events in question are
     ‘cpython.run_stdin’ and ‘cpython.run_startup’.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/122133

   (2) https://github.com/python/cpython/issues/121957


File: python.info,  Node: Library<2>,  Next: IDLE<4>,  Prev: Security<2>,  Up: Python 3 13 0 release candidate 1

1.23.3.3 Library
................

   - gh-122400(1): Handle *note ValueError: 1e7.s raised by *note
     os.stat(): 448. in *note filecmp.dircmp: ee4. and *note
     filecmp.cmpfiles(): 14dc.  Patch by Bénédikt Tran.

   - gh-122311(2): Fix some error messages in *note pickle: 95.

   - gh-122332(3): Fixed segfault with *note asyncio.Task.get_coro():
     97f. when using an eager task factory.

   - gh-105733(4): *note ctypes.ARRAY(): 27b. is now *note soft
     deprecated: 1ee.: it no longer emits deprecation warnings and is
     not scheduled for removal.

   - gh-122087(5): Restore *note inspect.ismethoddescriptor(): 14dd. and
     *note inspect.isroutine(): 14de. returning ‘False’ for *note
     functools.partial: 356. objects.

   - gh-122170(6): Handle *note ValueError: 1e7.s raised by *note
     os.stat(): 448. in *note linecache: 79.  Patch by Bénédikt Tran.

   - gh-82951(7): Serializing objects with complex ‘__qualname__’ (such
     as unbound methods and nested classes) by name no longer involves
     serializing parent objects by value in pickle protocols < 4.

   - gh-113785(8): *note csv: 21. now correctly parses numeric fields
     (when used with *note csv.QUOTE_NONNUMERIC: 14df. or *note
     csv.QUOTE_STRINGS: 42c.) which start with an escape character.

   - gh-122088(9): *note @warnings.deprecated: 144. now copies the
     coroutine status of functions and methods so that *note
     inspect.iscoroutinefunction(): 439. returns the correct result.

   - gh-120930(10): Fixed a bug introduced by gh-92081(11) that added an
     incorrect extra blank to encoded words occurring in wrapped
     headers.

   - gh-121474(12): Fix missing sanity check for ‘parties’ arg in *note
     threading.Barrier: 117b. constructor.  Patch by Clinton Christian
     (pygeek).

   - gh-120289(13): Fixed the use-after-free issue in *note cProfile:
     20. by disallowing ‘disable()’ and ‘clear()’ in external timers.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/122400

   (2) https://github.com/python/cpython/issues/122311

   (3) https://github.com/python/cpython/issues/122332

   (4) https://github.com/python/cpython/issues/105733

   (5) https://github.com/python/cpython/issues/122087

   (6) https://github.com/python/cpython/issues/122170

   (7) https://github.com/python/cpython/issues/82951

   (8) https://github.com/python/cpython/issues/113785

   (9) https://github.com/python/cpython/issues/122088

   (10) https://github.com/python/cpython/issues/120930

   (11) https://github.com/python/cpython/issues/92081

   (12) https://github.com/python/cpython/issues/121474

   (13) https://github.com/python/cpython/issues/120289


File: python.info,  Node: IDLE<4>,  Next: Core and Builtins<3>,  Prev: Library<2>,  Up: Python 3 13 0 release candidate 1

1.23.3.4 IDLE
.............

   - gh-122482(1): Change About IDLE to direct users to
     discuss.python.org instead of the now unused idle-dev email and
     mailing list.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/122482


File: python.info,  Node: Core and Builtins<3>,  Next: C API<2>,  Prev: IDLE<4>,  Up: Python 3 13 0 release candidate 1

1.23.3.5 Core and Builtins
..........................

   - gh-116090(1): Fix an issue in JIT builds that prevented some *note
     for: 2c3. loops from correctly firing *note RAISE: 14e2. monitoring
     events.

   - gh-122208(2): Dictionary watchers now only deliver the
     PyDict_EVENT_ADDED event when the insertion is in a known good
     state to succeed.

   - gh-122300(3): Preserve AST nodes for f-string with single-element
     format specifiers.  Patch by Pablo Galindo

   - gh-120906(4): *note frame.f_locals: 165. now supports arbitrary
     hashable objects as keys.

   - gh-122029(5): Emit ‘c_call’ events in *note sys.setprofile(): 146d.
     when a ‘PyMethodObject’ pointing to a ‘PyCFunction’ is called.

   - gh-122026(6): Fix a bug that caused the tokenizer to not correctly
     identify mismatched parentheses inside f-strings in some
     situations.  Patch by Pablo Galindo

   - gh-118934(7): Make ‘PyEval_GetLocals’ return borrowed reference

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/116090

   (2) https://github.com/python/cpython/issues/122208

   (3) https://github.com/python/cpython/issues/122300

   (4) https://github.com/python/cpython/issues/120906

   (5) https://github.com/python/cpython/issues/122029

   (6) https://github.com/python/cpython/issues/122026

   (7) https://github.com/python/cpython/issues/118934


File: python.info,  Node: C API<2>,  Next: Build<2>,  Prev: Core and Builtins<3>,  Up: Python 3 13 0 release candidate 1

1.23.3.6 C API
..............

   - gh-116622(1): Make *note PyObject_Print: 14e4. work around a bug in
     Android and OpenBSD which prevented it from throwing an exception
     when trying to write to a read-only stream.

   - gh-121489(2): Export private ‘_PyBytes_Join()’ again.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/116622

   (2) https://github.com/python/cpython/issues/121489


File: python.info,  Node: Build<2>,  Prev: C API<2>,  Up: Python 3 13 0 release candidate 1

1.23.3.7 Build
..............

   - gh-120522(1): Added a *note -with-app-store-compliance: 14e6.
     option to patch out known issues with macOS/iOS App Store review
     processes.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/120522


File: python.info,  Node: Python 3 13 0 beta 4,  Next: Python 3 13 0 beta 3,  Prev: Python 3 13 0 release candidate 1,  Up: Changelog（更動日誌）

1.23.4 Python 3.13.0 beta 4
---------------------------

'Release date: 2024-07-18'

* Menu:

* Tests: Tests<3>.
* Library: Library<3>.
* IDLE: IDLE<5>.
* Documentation::
* Core and Builtins: Core and Builtins<4>.
* C API: C API<3>.
* Build: Build<3>.


File: python.info,  Node: Tests<3>,  Next: Library<3>,  Up: Python 3 13 0 beta 4

1.23.4.1 Tests
..............

   - gh-121084(1): Fix test_typing random leaks.  Clear typing ABC
     caches when running tests for refleaks (‘-R’ option): call
     ‘_abc_caches_clear()’ on typing abstract classes and their
     subclasses.  Patch by Victor Stinner.

   - gh-121160(2): Add a test for *note readline.set_history_length():
     14e9.  Note that this test may fail on readline libraries.

   - gh-121200(3): Fix ‘test_expanduser_pwd2()’ of ‘test_posixpath’.
     Call ‘getpwnam()’ to get ‘pw_dir’, since it can be different than
     ‘getpwall()’ ‘pw_dir’.  Patch by Victor Stinner.

   - gh-121188(4): When creating the JUnit XML file, regrtest now
     escapes characters which are invalid in XML, such as the chr(27)
     control character used in ANSI escape sequences.  Patch by Victor
     Stinner.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/121084

   (2) https://github.com/python/cpython/issues/121160

   (3) https://github.com/python/cpython/issues/121200

   (4) https://github.com/python/cpython/issues/121188


File: python.info,  Node: Library<3>,  Next: IDLE<5>,  Prev: Tests<3>,  Up: Python 3 13 0 beta 4

1.23.4.2 Library
................

   - gh-57141(1): The 'shallow' argument to *note filecmp.dircmp: ee4.
     (new in Python 3.13) is now keyword-only.

   - gh-121245(2): Simplify handling of the history file in
     ‘site.register_readline()’ helper.  The ‘CAN_USE_PYREPL’ variable
     now will be initialized, when imported.  Patch by Sergey B
     Kirpichev.

   - gh-121332(3): Fix constructor of *note ast: 7. nodes with custom
     ‘_attributes’.  Previously, passing custom attributes would raise a
     *note DeprecationWarning: 18b.  Passing arguments to the
     constructor that are not in ‘_fields’ or ‘_attributes’ remains
     deprecated.  Patch by Jelle Zijlstra.

   - gh-121279(4): Avoid *note NameError: 3e5. for the *note warnings:
     fa. module when accessing the depracated atributes of the *note
     importlib.abc: 6c. module.

   - gh-121245(5): Fix a bug in the handling of the command history of
     the new *note REPL: 14e. that caused the history file to be wiped
     at REPL exit.

   - gh-87744(6): Fix waitpid race while calling *note send_signal():
     14eb. in asyncio.  Patch by Kumar Aditya.

   - gh-121018(7): Fixed other issues where *note
     argparse.ArgumentParser: 4de. did not honor ‘exit_on_error=False’.

   - gh-120678(8): Fix regression in the new REPL that meant that
     globals from files passed using the ‘-i’ argument would not be
     included in the REPL's global namespace.  Patch by Alex Waygood.

   - gh-120782(9): Fix wrong references of the *note datetime: 28. types
     after reloading the module.

   - gh-120713(10): *note datetime.datetime.strftime(): c37. now 0-pads
     years with less than four digits for the format specifiers ‘%Y’ and
     ‘%G’ on Linux.  Patch by Ben Hsing

   - gh-117983(11): Defer the ‘threading’ import in ‘importlib.util’
     until lazy loading is used.

   - gh-119189(12): When using the ‘**’ operator or *note pow(): 976.
     with *note Fraction: 1c7. as the base and an exponent that is not
     rational, a float, or a complex, the fraction is no longer
     converted to a float.

   - gh-118714(13): Allow ‘restart’ in post-mortem debugging of *note
     pdb: 94.  Removed restart message when the user quits pdb from
     post-mortem mode.

   - gh-105623(14): Fix performance degradation in *note
     logging.handlers.RotatingFileHandler: 14cb.  Patch by Craig Robson.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/57141

   (2) https://github.com/python/cpython/issues/121245

   (3) https://github.com/python/cpython/issues/121332

   (4) https://github.com/python/cpython/issues/121279

   (5) https://github.com/python/cpython/issues/121245

   (6) https://github.com/python/cpython/issues/87744

   (7) https://github.com/python/cpython/issues/121018

   (8) https://github.com/python/cpython/issues/120678

   (9) https://github.com/python/cpython/issues/120782

   (10) https://github.com/python/cpython/issues/120713

   (11) https://github.com/python/cpython/issues/117983

   (12) https://github.com/python/cpython/issues/119189

   (13) https://github.com/python/cpython/issues/118714

   (14) https://github.com/python/cpython/issues/105623


File: python.info,  Node: IDLE<5>,  Next: Documentation,  Prev: Library<3>,  Up: Python 3 13 0 beta 4

1.23.4.3 IDLE
.............

   - gh-78889(1): Stop Shell freezes by blocking user access to
     non-method sys.stdout.shell attributes, which are all private.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/78889


File: python.info,  Node: Documentation,  Next: Core and Builtins<4>,  Prev: IDLE<5>,  Up: Python 3 13 0 beta 4

1.23.4.4 Documentation
......................

   - gh-121749(1): Fix documentation for *note PyModule_AddObjectRef():
     308.

   - gh-120012(2): Clarify the behaviours of *note
     multiprocessing.Queue.empty(): 14ee. and *note
     multiprocessing.SimpleQueue.empty(): 14ef. on closed queues.  Patch
     by Bénédikt Tran.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/121749

   (2) https://github.com/python/cpython/issues/120012


File: python.info,  Node: Core and Builtins<4>,  Next: C API<3>,  Prev: Documentation,  Up: Python 3 13 0 beta 4

1.23.4.5 Core and Builtins
..........................

   - gh-121860(1): Fix crash when rematerializing a managed dictionary
     after it was deleted.

   - gh-121814(2): Fixed the SegFault when *note PyEval_SetTrace():
     146c. is used with no Python frame on stack.

   - gh-121295(3): Fix PyREPL console getting into a blocked state after
     interrupting a long paste

   - gh-121794(4): Fix bug in free-threaded Python where a resurrected
     object could lead to a negative ref count assertion failure.

   - gh-121657(5): Improve the *note SyntaxError: 173. message if the
     user tries to use *note yield from: 971. outside a function.

   - gh-121609(6): Fix pasting of characters containing unicode
     character joiners in the new REPL. Patch by Marta Gomez Macias

   - gh-117482(7): Unexpected slot wrappers are no longer created for
     builtin static types in subinterpreters.

   - gh-121499(8): Fix a bug affecting how multi-line history was being
     rendered in the new REPL after interacting with the new screen
     cache.  Patch by Pablo Galindo

   - gh-121497(9): Fix a bug that was preventing the REPL to correctly
     respect the history when an input hook was set.  Patch by Pablo
     Galindo

   - gh-121012(10): Tier 2 execution now ensures that list iterators
     remain exhausted, once they become exhausted.

   - gh-121439(11): Allow tuples of length 20 in the freelist to be
     reused.

   - gh-121368(12): Fix race condition in ‘_PyType_Lookup’ in the
     free-threaded build due to a missing memory fence.  This could lead
     to ‘_PyType_Lookup’ returning incorrect results on arm64.

   - gh-121130(13): Fix f-strings with debug expressions in format
     specifiers.  Patch by Pablo Galindo

   - gh-121115(14): *note PyLong_AsNativeBytes(): 33a. no longer uses
     *note __index__(): 6c1. methods by default.  The
     ‘Py_ASNATIVEBYTES_ALLOW_INDEX’ flag has been added to allow it.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/121860

   (2) https://github.com/python/cpython/issues/121814

   (3) https://github.com/python/cpython/issues/121295

   (4) https://github.com/python/cpython/issues/121794

   (5) https://github.com/python/cpython/issues/121657

   (6) https://github.com/python/cpython/issues/121609

   (7) https://github.com/python/cpython/issues/117482

   (8) https://github.com/python/cpython/issues/121499

   (9) https://github.com/python/cpython/issues/121497

   (10) https://github.com/python/cpython/issues/121012

   (11) https://github.com/python/cpython/issues/121439

   (12) https://github.com/python/cpython/issues/121368

   (13) https://github.com/python/cpython/issues/121130

   (14) https://github.com/python/cpython/issues/121115


File: python.info,  Node: C API<3>,  Next: Build<3>,  Prev: Core and Builtins<4>,  Up: Python 3 13 0 beta 4

1.23.4.6 C API
..............

   - gh-89364(1): Export the *note PySignal_SetWakeupFd(): 1349.
     function.  Previously, the function was documented but it couldn't
     be used in 3rd party code.  Patch by Victor Stinner.

   - gh-113993(2): *note PyUnicode_InternInPlace(): 856. no longer
     prevents its argument from being garbage collected.

     Several functions that take ‘char *’ are now documented as possibly
     preventing string objects from being garbage collected; refer to
     their documentation for details: *note
     PyUnicode_InternFromString(): 14f2, *note PyDict_SetItemString():
     14f3, *note PyObject_SetAttrString(): 14f4, *note
     PyObject_DelAttrString(): 14f5, *note PyUnicode_InternFromString():
     14f2, and ‘PyModule_Add*’ convenience functions.

   - gh-113601(3): Removed debug build assertions related to interning
     strings, which were falsely triggered by stable ABI extensions.

   - gh-112136(4): Restore the private ‘_PyArg_Parser’ structure and the
     private ‘_PyArg_ParseTupleAndKeywordsFast()’ function, previously
     removed in Python 3.13 alpha 1.  Patch by Victor Stinner.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/89364

   (2) https://github.com/python/cpython/issues/113993

   (3) https://github.com/python/cpython/issues/113601

   (4) https://github.com/python/cpython/issues/112136


File: python.info,  Node: Build<3>,  Prev: C API<3>,  Up: Python 3 13 0 beta 4

1.23.4.7 Build
..............

   - gh-120371(1): Support WASI SDK 22 by explicitly skipping functions
     that are just stubs in wasi-libc.

   - gh-121731(2): Fix mimalloc compile error on GNU/Hurd

   - gh-121487(3): Fix deprecation warning for ATOMIC_VAR_INIT in
     mimalloc.

   - gh-121467(4): Fix a Makefile bug that prevented mimalloc header
     files from being installed.

   - gh-121103(5): On POSIX systems, excluding macOS framework installs,
     the lib directory for the free-threaded build now includes a "t"
     suffix to avoid conflicts with a co-located default build
     installation.

   - gh-120831(6): The default minimum iOS version was increased to
     13.0.

   - gh-113565(7): Improve *note curses: 23. and *note curses.panel: 25.
     dependency checks in ‘configure’.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/120371

   (2) https://github.com/python/cpython/issues/121731

   (3) https://github.com/python/cpython/issues/121487

   (4) https://github.com/python/cpython/issues/121467

   (5) https://github.com/python/cpython/issues/121103

   (6) https://github.com/python/cpython/issues/120831

   (7) https://github.com/python/cpython/issues/113565


File: python.info,  Node: Python 3 13 0 beta 3,  Next: Python 3 13 0 beta 2,  Prev: Python 3 13 0 beta 4,  Up: Changelog（更動日誌）

1.23.5 Python 3.13.0 beta 3
---------------------------

'Release date: 2024-06-27'

* Menu:

* Core and Builtins: Core and Builtins<5>.
* Library: Library<4>.
* Build: Build<4>.
* C API: C API<4>.


File: python.info,  Node: Core and Builtins<5>,  Next: Library<4>,  Up: Python 3 13 0 beta 3

1.23.5.1 Core and Builtins
..........................

   - gh-120838(1): *note Py_Finalize(): 12e6. and *note Py_FinalizeEx():
     cbc. now always run with the main interpreter active.

   - gh-113433(2): Subinterpreters now get cleaned up automatically
     during runtime finalization.

   - gh-119462(3): Make sure that invariants of type versioning are
     maintained: * Superclasses always have their version number
     assigned before subclasses * The version tag is always zero if the
     tag is not valid.  * The version tag is always non-zero if the tag
     is valid.

   - gh-120437(4): Fix ‘_CHECK_STACK_SPACE’ optimization problems
     introduced in gh-118322(5).

   - gh-120722(6): Correctly set the bytecode position on return
     instructions within lambdas.  Patch by Jelle Zijlstra.

   - gh-120367(7): Fix bug where compiler creates a redundant jump
     during pseudo-op replacement.  Can only happen with a synthetic AST
     that has a try on the same line as the instruction following the
     exception handler.

   - gh-113993(8): Strings interned with *note sys.intern(): 126e. are
     again garbage-collected when no longer used, as per the
     documentation.  Strings interned with the C function *note
     PyUnicode_InternInPlace(): 856. are still immortal.  Internals of
     the string interning mechanism have been changed.  This may affect
     performance and identities of *note str: 3f2. objects.

   - gh-120384(9): Fix an array out of bounds crash in
     ‘list_ass_subscript’, which could be invoked via some specificly
     tailored input: including concurrent modification of a list object,
     where one thread assigns a slice and another clears it.

   - gh-120367(10): Fix crash in compiler on code with redundant NOPs
     and JUMPs which show up after exception handlers are moved to the
     end of the code.

   - gh-120380(11): Fix Python implementation of *note pickle.Pickler:
     9c2. for *note bytes: 1a5. and *note bytearray: 4e3. objects when
     using protocol version 5.  Patch by Bénédikt Tran.

   - gh-120400(12): Support Linux perf profiler to see Python calls on
     RISC-V architecture.

   - gh-120221(13): Deliver real signals on Ctrl-C and Ctrl-Z in the new
     REPL. Patch by Pablo Galindo

   - gh-120346(14): Respect *note PYTHON_BASIC_REPL: 152. when running
     in interative inspect mode (‘python -i’).  Patch by Pablo Galindo

   - gh-93691(15): Fix source locations of instructions generated for
     the iterator of a for statement.

   - gh-120198(16): Fix a crash when multiple threads read and write to
     the same ‘__class__’ of an object concurrently.

   - gh-120298(17): Fix use-after free in ‘list_richcompare_impl’ which
     can be invoked via some specificly tailored evil input.

   - gh-119666(18): Fix a compiler crash in the case where two
     comprehensions in class scope both reference ‘__class__’.

   - gh-120225(19): Fix crash in compiler on empty block at end of
     exception handler.

   - gh-119933(20): Improve *note SyntaxError: 173. messages for invalid
     expressions in a type parameters bound, a type parameter constraint
     tuple or a default type parameter.  Patch by Bénédikt Tran.

   - bpo-24766(21): Fix handling of ‘doc’ argument to subclasses of
     ‘property’.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/120838

   (2) https://github.com/python/cpython/issues/113433

   (3) https://github.com/python/cpython/issues/119462

   (4) https://github.com/python/cpython/issues/120437

   (5) https://github.com/python/cpython/issues/118322

   (6) https://github.com/python/cpython/issues/120722

   (7) https://github.com/python/cpython/issues/120367

   (8) https://github.com/python/cpython/issues/113993

   (9) https://github.com/python/cpython/issues/120384

   (10) https://github.com/python/cpython/issues/120367

   (11) https://github.com/python/cpython/issues/120380

   (12) https://github.com/python/cpython/issues/120400

   (13) https://github.com/python/cpython/issues/120221

   (14) https://github.com/python/cpython/issues/120346

   (15) https://github.com/python/cpython/issues/93691

   (16) https://github.com/python/cpython/issues/120198

   (17) https://github.com/python/cpython/issues/120298

   (18) https://github.com/python/cpython/issues/119666

   (19) https://github.com/python/cpython/issues/120225

   (20) https://github.com/python/cpython/issues/119933

   (21) https://bugs.python.org/issue?@action=redirect&bpo=24766


File: python.info,  Node: Library<4>,  Next: Build<4>,  Prev: Core and Builtins<5>,  Up: Python 3 13 0 beta 3

1.23.5.2 Library
................

   - gh-121027(1): Add a future warning in
     ‘functools.partial.__get__()’.  In future Python versions *note
     functools.partial: 356. will be a method descriptor.

   - gh-121025(2): Improve the *note __repr__(): 5c2. of *note
     functools.partialmethod: a1e.  Patch by Bénédikt Tran.

   - gh-121018(3): Fixed an issue where
     ‘argparse.ArgumentParser.parses_args()’ did not honor
     ‘exit_on_error=False’ when given unrecognized arguments.  Patch by
     Ben Hsing.

   - gh-119614(4): Fix truncation of strings with embedded null
     characters in some internal operations in *note tkinter: d9.

   - gh-120910(5): When reading installed files from an egg, use
     ‘relative_to(walk_up=True)’ to honor files installed outside of the
     installation root.

   - gh-120888(6): Upgrade pip wheel bundled with ensurepip (pip 24.1.1)

   - gh-101830(7): Accessing the *note tkinter: d9. object's string
     representation no longer converts the underlying Tcl object to a
     string on Windows.

   - gh-120811(8): Fix possible memory leak in *note
     contextvars.Context.run(): 14fa.

   - gh-120769(9): Make empty line in *note pdb: 94. repeats the last
     command even when the command is from ‘cmdqueue’.

   - gh-120732(10): Fix ‘name’ passing to *note unittest.mock.Mock: 9ef.
     object when using *note unittest.mock.create_autospec(): 14fb.

   - gh-120683(11): Fix an error in *note logging.LogRecord: f89, when
     the integer part of the timestamp is rounded up, while the
     millisecond calculation truncates, causing the log timestamp to be
     wrong by up to 999 ms (affected roughly 1 in 8 million timestamps).

   - gh-120633(12): Move scrollbar and remove tear-off menus in
     turtledemo.

   - gh-120541(13): Improve the prompt in the "less" pager when *note
     help(): 87c. is called with non-string argument.

   - gh-120495(14): Fix incorrect exception handling in Tab Nanny.
     Patch by Wulian233.

   - gh-120381(15): Correct *note inspect.ismethoddescriptor(): 14dd. to
     check also for the lack of *note __delete__(): 14fc.  Patch by Jan
     Kaliszewski.

   - gh-90425(16): The OS byte in gzip headers is now always set to 255
     when using *note gzip.compress(): 5e4.

   - gh-120343(17): Fix column offset reporting for tokens that come
     after multiline f-strings in the *note tokenize: e4. module.

   - gh-119600(18): Fix *note unittest.mock.patch(): e34. to not read
     attributes of the target when ‘new_callable’ is set.  Patch by
     Robert Collins.

   - gh-114053(19): Fix edge-case bug where *note
     typing.get_type_hints(): 657. would produce incorrect results if
     type parameters in a class scope were overridden by assignments in
     a class scope and ‘from __future__ import annotations’ semantics
     were enabled.  Patch by Alex Waygood.

   - gh-114053(20): Fix erroneous *note NameError: 3e5. when calling
     *note inspect.get_annotations(): 7b7. with ‘eval_str=True`’ on a
     class that made use of PEP 695(21) type parameters in a module that
     had ‘from __future__ import annotations’ at the top of the file.
     Patch by Alex Waygood.

   - gh-120268(22): Prohibit passing ‘None’ to pure-Python *note
     datetime.date.fromtimestamp(): 14fd. to achieve consistency with
     C-extension implementation.

   - gh-120244(23): Fix memory leak in *note re.sub(): 283. when the
     replacement string contains backreferences.

   - gh-120211(24): Fix *note tkinter.ttk: e2. with Tcl/Tk 9.0.

   - gh-71587(25): Fix crash in C version of *note
     datetime.datetime.strptime(): 14fe. when called again on the
     restarted interpreter.

   - gh-120161(26): *note datetime: 28. no longer crashes in certain
     complex reference cycle situations.

   - gh-119698(27): Fix *note symtable.Class.get_methods(): 2c0. and
     document its behaviour.  Patch by Bénédikt Tran.

   - gh-120121(28): Add *note concurrent.futures.InvalidStateError:
     14ff. to module's ‘__all__’.

   - gh-119933(29): Add the *note symtable.SymbolTableType: 1500.
     enumeration to represent the possible outputs of the *note
     symtable.SymbolTable.get_type: 1501. method.  Patch by Bénédikt
     Tran.

   - gh-120108(30): Fix calling *note copy.deepcopy(): b12. on *note
     ast: 7. trees that have been modified to have references to parent
     nodes.  Patch by Jelle Zijlstra.

   - gh-112672(31): Support building *note tkinter: d9. with Tcl 9.0.

   - gh-65454(32): *note unittest.mock.Mock.attach_mock(): 1502. no
     longer triggers a call to a ‘PropertyMock’ being attached.

   - gh-81936(33): ‘help()’ and ‘showtopic()’ methods now respect a
     configured 'output' argument to ‘pydoc.Helper’ and not use the
     pager in such cases.  Patch by Enrico Tröger.

   - gh-119577(34): The *note DeprecationWarning: 18b. emitted when
     testing the truth value of an *note xml.etree.ElementTree.Element:
     2e2. now describes unconditionally returning ‘True’ in a future
     version rather than raising an exception in Python 3.14.

   - gh-118908(35): Limit exposed globals from internal imports and
     definitions on new REPL startup.  Patch by Eugene Triguba and Pablo
     Galindo.

   - gh-119506(36): Fix ‘io.TextIOWrapper.write()’ method breaks
     internal buffer when the method is called again during flushing
     internal buffer.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/121027

   (2) https://github.com/python/cpython/issues/121025

   (3) https://github.com/python/cpython/issues/121018

   (4) https://github.com/python/cpython/issues/119614

   (5) https://github.com/python/cpython/issues/120910

   (6) https://github.com/python/cpython/issues/120888

   (7) https://github.com/python/cpython/issues/101830

   (8) https://github.com/python/cpython/issues/120811

   (9) https://github.com/python/cpython/issues/120769

   (10) https://github.com/python/cpython/issues/120732

   (11) https://github.com/python/cpython/issues/120683

   (12) https://github.com/python/cpython/issues/120633

   (13) https://github.com/python/cpython/issues/120541

   (14) https://github.com/python/cpython/issues/120495

   (15) https://github.com/python/cpython/issues/120381

   (16) https://github.com/python/cpython/issues/90425

   (17) https://github.com/python/cpython/issues/120343

   (18) https://github.com/python/cpython/issues/119600

   (19) https://github.com/python/cpython/issues/114053

   (20) https://github.com/python/cpython/issues/114053

   (21) https://peps.python.org/pep-0695/

   (22) https://github.com/python/cpython/issues/120268

   (23) https://github.com/python/cpython/issues/120244

   (24) https://github.com/python/cpython/issues/120211

   (25) https://github.com/python/cpython/issues/71587

   (26) https://github.com/python/cpython/issues/120161

   (27) https://github.com/python/cpython/issues/119698

   (28) https://github.com/python/cpython/issues/120121

   (29) https://github.com/python/cpython/issues/119933

   (30) https://github.com/python/cpython/issues/120108

   (31) https://github.com/python/cpython/issues/112672

   (32) https://github.com/python/cpython/issues/65454

   (33) https://github.com/python/cpython/issues/81936

   (34) https://github.com/python/cpython/issues/119577

   (35) https://github.com/python/cpython/issues/118908

   (36) https://github.com/python/cpython/issues/119506


File: python.info,  Node: Build<4>,  Next: C API<4>,  Prev: Library<4>,  Up: Python 3 13 0 beta 3

1.23.5.3 Build
..............

   - gh-120671(1): Fix failing configure tests due to a missing space
     when appending to CFLAGS.

   - gh-120602(2): Correctly handle LLVM installs with
     ‘LLVM_VERSION_SUFFIX’ when building with
     ‘--enable-experimental-jit’.

   - gh-120326(3): On Windows, fix build error when ‘--disable-gil’ and
     ‘--experimental-jit’ options are combined.

   - gh-120291(4): Make the ‘python-config’ shell script compatible with
     non-bash shells.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/120671

   (2) https://github.com/python/cpython/issues/120602

   (3) https://github.com/python/cpython/issues/120326

   (4) https://github.com/python/cpython/issues/120291


File: python.info,  Node: C API<4>,  Prev: Build<4>,  Up: Python 3 13 0 beta 3

1.23.5.4 C API
..............

   - gh-120642(1): Remove the private ‘_Py_CODEUNIT’ type from the
     public C API. The internal ‘pycore_code.h’ header should now be
     used to get this internal type.  Patch by Victor Stinner.

   - gh-120858(2): *note PyDict_Next(): 1505. no longer locks the
     dictionary in the free-threaded build.  The locking needs to be
     done by the caller around the entire iteration loop.

   - gh-120642(3): Remove the following unstable functions:

        * ‘PyUnstable_Replace_Executor()’

        * ‘PyUnstable_SetOptimizer()’

        * ‘PyUnstable_GetOptimizer()’

        * ‘PyUnstable_GetExecutor()’

        * ‘PyUnstable_Optimizer_NewCounter()’

        * ‘PyUnstable_Optimizer_NewUOpOptimizer()’

     Patch by Victor Stinner.

   - gh-119344(4): The critical section API is now public as part of the
     non-limited C API.

   - gh-118789(5): Add *note
     PyUnstable_Object_ClearWeakRefsNoCallbacks(): 1506, which clears
     weakrefs without calling their callbacks.

   - gh-117511(6): Make the *note PyMutex: 140. public in the
     non-limited C API.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/120642

   (2) https://github.com/python/cpython/issues/120858

   (3) https://github.com/python/cpython/issues/120642

   (4) https://github.com/python/cpython/issues/119344

   (5) https://github.com/python/cpython/issues/118789

   (6) https://github.com/python/cpython/issues/117511


File: python.info,  Node: Python 3 13 0 beta 2,  Next: Python 3 13 0 beta 1,  Prev: Python 3 13 0 beta 3,  Up: Changelog（更動日誌）

1.23.6 Python 3.13.0 beta 2
---------------------------

'Release date: 2024-06-05'

* Menu:

* Security: Security<3>.
* Core and Builtins: Core and Builtins<6>.
* Library: Library<5>.
* Tests: Tests<4>.
* Build: Build<5>.
* Windows: Windows<2>.
* C API: C API<5>.


File: python.info,  Node: Security<3>,  Next: Core and Builtins<6>,  Up: Python 3 13 0 beta 2

1.23.6.1 Security
.................

   - gh-118773(1): Fixes creation of ACLs in *note os.mkdir(): 202. on
     Windows to work correctly on non-English machines.

   - gh-118486(2): *note os.mkdir(): 202. on Windows now accepts 'mode'
     of ‘0o700’ to restrict the new directory to the current user.  This
     fixes CVE-2024-4030(3) affecting *note tempfile.mkdtemp(): 204. in
     scenarios where the base temporary directory is more permissive
     than the default.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/118773

   (2) https://github.com/python/cpython/issues/118486

   (3) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-4030


File: python.info,  Node: Core and Builtins<6>,  Next: Library<5>,  Prev: Security<3>,  Up: Python 3 13 0 beta 2

1.23.6.2 Core and Builtins
..........................

   - gh-119724(1): Reverted improvements to error messages for
     ‘elif’/‘else’ statements not matching any valid statements, which
     made in hard to locate the syntax errors inside those ‘elif’/‘else’
     blocks.

   - gh-119842(2): Honor *note PyOS_InputHook(): 52b. in the new REPL.
     Patch by Pablo Galindo

   - gh-119821(3): Fix execution of *note annotation scopes: 16e. within
     classes when ‘globals’ is set to a non-dict.  Patch by Jelle
     Zijlstra.

   - gh-119548(4): Add a ‘clear’ command to the REPL. Patch by Pablo
     Galindo

   - gh-111999(5): Fix the signature of *note str.format_map(): d7d.

   - gh-119560(6): An invalid assert in beta 1 has been removed.  The
     assert would fail if ‘PyState_FindModule()’ was used in an
     extension module's init function before the module def had been
     initialized.

   - gh-119369(7): Fix deadlock during thread deletion in free-threaded
     build, which could occur when the GIL was enabled at runtime.

   - gh-119525(8): Fix deadlock involving ‘_PyType_Lookup()’ cache in
     the free-threaded build when the GIL is dynamically enabled at
     runtime.

   - gh-119311(9): Fix bug where names are unexpectedly mangled in the
     bases of generic classes.

   - gh-119395(10): Fix bug where names appearing after a generic class
     are mangled as if they are in the generic class.

   - gh-119213(11): Non-builtin modules built with argument clinic were
     crashing if used in a subinterpreter before the main interpreter.
     The objects that were causing the problem by leaking between
     interpreters carelessly have been fixed.

   - gh-119011(12): Fixes ‘type.__type_params__’ to return an empty
     tuple instead of a descriptor.

   - gh-118692(13): Avoid creating unnecessary *note StopIteration: ba1.
     instances for monitoring.

   - gh-119049(14): Fix displaying the source line for warnings created
     by the C API if the *note warnings: fa. module had not yet been
     imported.

   - gh-118844(15): Fix build failures when configuring with both
     ‘--disable-gil’ and ‘--enable-experimental-jit’.

   - gh-118921(16): Add ‘copy()’ method for ‘FrameLocalsProxy’ which
     returns a snapshot ‘dict’ for local variables.

   - gh-117657(17): Fix data races on the field that stores a pointer to
     the interpreter's main thread that occur in free-threaded builds.

   - gh-118561(18): Fix race condition in free-threaded build where
     ‘list.extend()’ could expose uninitialised memory to concurrent
     readers.

   - gh-117195(19): Avoid assertion failure for debug builds when
     calling ‘object.__sizeof__(1)’

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/119724

   (2) https://github.com/python/cpython/issues/119842

   (3) https://github.com/python/cpython/issues/119821

   (4) https://github.com/python/cpython/issues/119548

   (5) https://github.com/python/cpython/issues/111999

   (6) https://github.com/python/cpython/issues/119560

   (7) https://github.com/python/cpython/issues/119369

   (8) https://github.com/python/cpython/issues/119525

   (9) https://github.com/python/cpython/issues/119311

   (10) https://github.com/python/cpython/issues/119395

   (11) https://github.com/python/cpython/issues/119213

   (12) https://github.com/python/cpython/issues/119011

   (13) https://github.com/python/cpython/issues/118692

   (14) https://github.com/python/cpython/issues/119049

   (15) https://github.com/python/cpython/issues/118844

   (16) https://github.com/python/cpython/issues/118921

   (17) https://github.com/python/cpython/issues/117657

   (18) https://github.com/python/cpython/issues/118561

   (19) https://github.com/python/cpython/issues/117195


File: python.info,  Node: Library<5>,  Next: Tests<4>,  Prev: Core and Builtins<6>,  Up: Python 3 13 0 beta 2

1.23.6.3 Library
................

   - gh-119819(1): Fix regression to allow logging configuration with
     multiprocessing queue types.

   - gh-117142(2): The *note ctypes: 22. module may now be imported in
     all subinterpreters, including those that have their own GIL.

   - gh-118835(3): Fix _pyrepl crash when using custom prompt with ANSI
     escape codes.

   - gh-117398(4): The ‘_datetime’ module (C implementation for *note
     datetime: 28.) now supports being imported in multiple
     interpreters.

   - gh-89727(5): Fix issue with *note shutil.rmtree(): 2d2. where a
     *note RecursionError: d12. is raised on deep directory trees.

   - gh-89727(6): Partially fix issue with *note shutil.rmtree(): 2d2.
     where a *note RecursionError: d12. is raised on deep directory
     trees.  A recursion error is no longer raised when
     ‘rmtree.avoids_symlink_attacks’ is false.

   - gh-119118(7): Fix performance regression in the *note tokenize: e4.
     module by caching the ‘line’ token attribute and calculating the
     column offset more efficiently.

   - gh-89727(8): Fix issue with *note os.fwalk(): aff. where a *note
     RecursionError: d12. was raised on deep directory trees by
     adjusting the implementation to be iterative instead of recursive.

   - gh-119588(9): ‘zipfile.Path.is_symlink’ now assesses if the given
     path is a symlink.

   - gh-119555(10): Catch *note SyntaxError: 173. from *note compile():
     178. in the runsource() method of the InteractiveColoredConsole.
     Patch by Sergey B Kirpichev.

   - gh-113892(11): Now, the method ‘sock_connect’ of *note
     asyncio.ProactorEventLoop: 5ae. raises a *note ValueError: 1e7. if
     given socket is not in non-blocking mode, as well as in other loop
     implementations.

   - gh-119443(12): The interactive REPL no longer runs with ‘from
     __future__ import annotations’ enabled.  Patch by Jelle Zijlstra.

   - gh-117398(13): Objects in the datetime C-API are now all statically
     allocated, which means better memory safety, especially when the
     module is reloaded.  This should be transparent to users.

   - gh-118894(14): *note asyncio: 8. REPL now has the same capabilities
     as PyREPL.

   - gh-118911(15): In PyREPL, updated ‘maybe-accept’'s logic so that if
     the user hits ‘Enter’ twice, they are able to terminate the block
     even if there's trailing whitespace.  Also, now when the user hits
     arrow up, the cursor is on the last functional line.  This matches
     IPython's behavior.  Patch by Aya Elsayed.

   - gh-111201(16): Remove dependency to *note readline: a8. from the
     new Python REPL.

   - gh-119174(17): Fix high DPI causes turtledemo(turtle-graphics
     examples) windows blurry Patch by Wulian233 and Terry Jan Reedy

   - gh-119121(18): Fix a NameError happening in
     ‘asyncio.staggered.staggered_race’.  This function is now tested.

   - gh-119113(19): Fix issue where *note
     pathlib.PurePath.with_suffix(): 150b. didn't raise *note TypeError:
     4dd. when given ‘None’ as a suffix.

   - gh-118643(20): Fix an AttributeError in the *note email: 32. module
     when re-fold a long address list.  Also fix more cases of incorrect
     encoding of the address separator in the address list.

   - gh-58933(21): Make *note pdb: 94. return to caller frame correctly
     when ‘f_trace’ of the caller frame is not set

   - gh-118895(22): Setting attributes on *note typing.NoDefault: 247.
     now raises *note AttributeError: 2f6. instead of *note TypeError:
     4dd.

   - gh-118868(23): Fixed issue where kwargs were no longer passed to
     the logging handler QueueHandler

   - gh-118851(24): ‘ctx’ arguments to the constructors of *note ast: 7.
     node classes now default to *note ast.Load(): 18a.  Patch by Jelle
     Zijlstra.

   - gh-118760(25): Restore the default value of ‘tkiter.wantobjects’ to
     ‘1’.

   - gh-118760(26): Fix errors in calling Tkinter bindings on Windows.

   - gh-118507(27): Fix *note os.path.isfile(): 9b5. on Windows for
     pipes.  Speedup *note os.path.isjunction(): 44b. and *note
     os.path.lexists(): 9b3. on Windows with a native implementation.

   - gh-118772(28): Allow *note typing.TypeVar: 141. instances without a
     default to follow instances without a default in some cases.  Patch
     by Jelle Zijlstra.

   - gh-110863(29): *note os.path.realpath(): 20a. now suppresses any
     *note OSError: 350. from *note os.readlink(): 8c5. when 'strict'
     mode is disabled (the default).

   - gh-118263(30): Speed up *note os.path.splitroot(): 44c. & *note
     os.path.normpath(): 12ae. with a direct C call.

   - gh-118033(31): Fix *note dataclasses.dataclass(): 1af. not creating
     a ‘__weakref__’ slot when subclassing *note typing.Generic: 150c.

   - gh-106531(32): In *note importlib.resources: 6f, sync with
     importlib_resources 6.3.2(33), including: ‘MultiplexedPath’ now
     expects ‘Traversable’ paths, deprecating string arguments to
     ‘MultiplexedPath’; Enabled support for resources in namespace
     packages in zip files; Fixed ‘NotADirectoryError’ when calling
     files on a subdirectory of a namespace package.

   - gh-113978(34): Ignore warnings on text completion inside REPL.

   - gh-103956(35): Fix lack of newline characters in *note trace: e6.
     module output when line tracing is enabled but source code line for
     current frame is not available.

   - gh-92081(36): Fix missing spaces in email headers when the spaces
     are mixed with encoded 8-bit characters.

   - gh-103194(37): Prepare Tkinter for C API changes in Tcl 8.7/9.0 to
     avoid ‘_tkinter.Tcl_Obj’ being unexpectedly returned instead of
     *note bool: 40e, *note str: 3f2, *note bytearray: 4e3, or *note
     int: 23c.

   - gh-87106(38): Fixed handling in *note inspect.Signature.bind():
     150d. of keyword arguments having the same name as positional-only
     arguments when a variadic keyword argument (e.g.  ‘**kwargs’) is
     present.

   - bpo-45767(39): Fix integer conversion in *note os.major(): 150e,
     *note os.minor(): 150f, and *note os.makedev(): 1510.  Support
     device numbers larger than ‘2**63-1’.  Support non-existent device
     number (‘NODEV’).

   - gh-67693(40): Fix *note urllib.parse.urlunparse(): 14c9. and *note
     urllib.parse.urlunsplit(): 14c8. for URIs with path starting with
     multiple slashes and no authority.  Based on patch by Ashwin
     Ramaswami.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/119819

   (2) https://github.com/python/cpython/issues/117142

   (3) https://github.com/python/cpython/issues/118835

   (4) https://github.com/python/cpython/issues/117398

   (5) https://github.com/python/cpython/issues/89727

   (6) https://github.com/python/cpython/issues/89727

   (7) https://github.com/python/cpython/issues/119118

   (8) https://github.com/python/cpython/issues/89727

   (9) https://github.com/python/cpython/issues/119588

   (10) https://github.com/python/cpython/issues/119555

   (11) https://github.com/python/cpython/issues/113892

   (12) https://github.com/python/cpython/issues/119443

   (13) https://github.com/python/cpython/issues/117398

   (14) https://github.com/python/cpython/issues/118894

   (15) https://github.com/python/cpython/issues/118911

   (16) https://github.com/python/cpython/issues/111201

   (17) https://github.com/python/cpython/issues/119174

   (18) https://github.com/python/cpython/issues/119121

   (19) https://github.com/python/cpython/issues/119113

   (20) https://github.com/python/cpython/issues/118643

   (21) https://github.com/python/cpython/issues/58933

   (22) https://github.com/python/cpython/issues/118895

   (23) https://github.com/python/cpython/issues/118868

   (24) https://github.com/python/cpython/issues/118851

   (25) https://github.com/python/cpython/issues/118760

   (26) https://github.com/python/cpython/issues/118760

   (27) https://github.com/python/cpython/issues/118507

   (28) https://github.com/python/cpython/issues/118772

   (29) https://github.com/python/cpython/issues/110863

   (30) https://github.com/python/cpython/issues/118263

   (31) https://github.com/python/cpython/issues/118033

   (32) https://github.com/python/cpython/issues/106531

   (33) 
https://importlib-resources.readthedocs.io/en/latest/history.html#v6-3-2

   (34) https://github.com/python/cpython/issues/113978

   (35) https://github.com/python/cpython/issues/103956

   (36) https://github.com/python/cpython/issues/92081

   (37) https://github.com/python/cpython/issues/103194

   (38) https://github.com/python/cpython/issues/87106

   (39) https://bugs.python.org/issue?@action=redirect&bpo=45767

   (40) https://github.com/python/cpython/issues/67693


File: python.info,  Node: Tests<4>,  Next: Build<5>,  Prev: Library<5>,  Up: Python 3 13 0 beta 2

1.23.6.4 Tests
..............

   - gh-119050(1): regrtest test runner: Add XML support to the refleak
     checker (-R option).  Patch by Victor Stinner.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/119050


File: python.info,  Node: Build<5>,  Next: Windows<2>,  Prev: Tests<4>,  Up: Python 3 13 0 beta 2

1.23.6.5 Build
..............

   - gh-119729(1): On POSIX systems, the pkg-config (‘.pc’) filenames
     now include the ABI flags, which may include debug ("d") and
     free-threaded ("t").  For example: * ‘python-3.14.pc’ (default,
     non-debug build) * ‘python-3.14d.pc’ (default, debug build) *
     ‘python-3.14t.pc’ (free-threaded build)

   - gh-115119(2): Fall back to the bundled libmpdec if a system version
     cannot be found.

   - gh-119132(3): Update *note sys.version: 15c. to identify whether
     the build is default build or free-threading build.  Patch By
     Donghee Na.

   - gh-118836(4): Fix an ‘AssertionError’ when building with
     ‘--enable-experimental-jit’ and the compiler emits a ‘SHT_NOTE’
     section.

   - gh-118943(5): Fix a possible race condition affecting parallel
     builds configured with ‘--enable-experimental-jit’, in which
     compilation errors could be caused by an incompletely-generated
     header file.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/119729

   (2) https://github.com/python/cpython/issues/115119

   (3) https://github.com/python/cpython/issues/119132

   (4) https://github.com/python/cpython/issues/118836

   (5) https://github.com/python/cpython/issues/118943


File: python.info,  Node: Windows<2>,  Next: C API<5>,  Prev: Build<5>,  Up: Python 3 13 0 beta 2

1.23.6.6 Windows
................

   - gh-119679(1): Ensures correct import libraries are included in
     Windows installs.

   - gh-119690(2): Adds Unicode support and fixes audit events for
     ‘_winapi.CreateNamedPipe’.

   - gh-111201(3): Add support for new pyrepl on Windows

   - gh-119070(4): Fixes ‘py.exe’ handling of shebangs like
     ‘/usr/bin/env python3.12’, which were previously interpreted as
     ‘python3.exe’ instead of ‘python3.12.exe’.

   - gh-117505(5): Fixes an issue with the Windows installer not running
     ensurepip in a fully isolated environment.  This could cause
     unexpected interactions with the user site-packages.

   - gh-118209(6): Avoid crashing in *note mmap: 83. on Windows when the
     mapped memory is inaccessible due to file system errors or access
     violations.

   - gh-116145(7): Updated bundled Tcl/Tk to 8.6.14.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/119679

   (2) https://github.com/python/cpython/issues/119690

   (3) https://github.com/python/cpython/issues/111201

   (4) https://github.com/python/cpython/issues/119070

   (5) https://github.com/python/cpython/issues/117505

   (6) https://github.com/python/cpython/issues/118209

   (7) https://github.com/python/cpython/issues/116145


File: python.info,  Node: C API<5>,  Prev: Windows<2>,  Up: Python 3 13 0 beta 2

1.23.6.7 C API
..............

   - gh-119585(1): Fix crash when a thread state that was created by
     *note PyGILState_Ensure(): 376. calls a destructor that during
     *note PyThreadState_Clear(): 1515. that calls back into *note
     PyGILState_Ensure(): 376. and *note PyGILState_Release(): 377.
     This might occur when in the free-threaded build or when using
     thread-local variables whose destructors call *note
     PyGILState_Ensure(): 376.

   - gh-119336(2): Restore the removed ‘_PyLong_NumBits()’ function.  It
     is used by the pywin32 project.  Patch by Ethan Smith

   - gh-119247(3): Added ‘Py_BEGIN_CRITICAL_SECTION_SEQUENCE_FAST’ and
     ‘Py_END_CRITICAL_SECTION_SEQUENCE_FAST’ macros to make it possible
     to use PySequence_Fast APIs safely when free-threaded, and update
     str.join to work without the GIL using them.

   - gh-111389(4): Add *note PyHASH_MULTIPLIER: 1516. constant: prime
     multiplier used in string and various other hashes.  Patch by
     Victor Stinner.

   - gh-116984(5): Make mimalloc includes relative to the current file
     to avoid embedders or extensions needing to include
     ‘Internal/mimalloc’ if they are already including internal CPython
     headers.

   - gh-118789(6): Restore ‘_PyWeakref_ClearRef’ that was previously
     removed in Python 3.13 alpha 1.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/119585

   (2) https://github.com/python/cpython/issues/119336

   (3) https://github.com/python/cpython/issues/119247

   (4) https://github.com/python/cpython/issues/111389

   (5) https://github.com/python/cpython/issues/116984

   (6) https://github.com/python/cpython/issues/118789


File: python.info,  Node: Python 3 13 0 beta 1,  Next: Python 3 13 0 alpha 6,  Prev: Python 3 13 0 beta 2,  Up: Changelog（更動日誌）

1.23.7 Python 3.13.0 beta 1
---------------------------

'Release date: 2024-05-08'

* Menu:

* Security: Security<4>.
* Core and Builtins: Core and Builtins<7>.
* Library: Library<6>.
* Documentation: Documentation<2>.
* Build: Build<6>.
* Windows: Windows<3>.
* macOS: macOS<2>.
* IDLE: IDLE<6>.
* C API: C API<6>.


File: python.info,  Node: Security<4>,  Next: Core and Builtins<7>,  Up: Python 3 13 0 beta 1

1.23.7.1 Security
.................

   - gh-116741(1): Update bundled libexpat to 2.6.2

   - gh-117233(2): Detect BLAKE2, SHA3, Shake, & truncated SHA512
     support in the OpenSSL-ish libcrypto library at build time.  This
     allows *note hashlib: 5e. to be used with libraries that do not to
     support every algorithm that upstream OpenSSL does.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/116741

   (2) https://github.com/python/cpython/issues/117233


File: python.info,  Node: Core and Builtins<7>,  Next: Library<6>,  Prev: Security<4>,  Up: Python 3 13 0 beta 1

1.23.7.2 Core and Builtins
..........................

   - gh-118414(1): Add instrumented opcodes to YIELD_VALUE assertion for
     tracing cases.

   - gh-117953(2): When a builtin or extension module is imported for
     the first time, while a subinterpreter is active, the module's init
     function is now run by the main interpreter first before import
     continues in the subinterpreter.  Consequently, single-phase init
     modules now fail in an isolated subinterpreter without the init
     function running under that interpreter, whereas before it would
     run under the subinterpreter 'before' failing, potentially leaving
     behind global state and callbacks and otherwise leaving the module
     in an inconsistent state.

   - gh-117549(3): Don't use designated initializer syntax in inline
     functions in internal headers.  They cause problems for C++ or MSVC
     users who aren't yet using the latest C++ standard (C++20).  While
     internal, pycore_backoff.h, is included (indirectly, via
     pycore_code.h) by some key 3rd party software that does so for
     speed.

   - gh-95382(4): Improve performance of *note json.dumps(): cec. and
     *note json.dump(): ceb. when using the argument 'indent'.
     Depending on the data the encoding using *note json.dumps(): cec.
     with 'indent' can be up to 2 to 3 times faster.

   - gh-116322(5): In ‘--disable-gil’ builds, the GIL will be enabled
     while loading C extension modules.  If the module indicates that it
     supports running without the GIL, the GIL will be disabled once
     loading is complete.  Otherwise, the GIL will remain enabled for
     the remainder of the interpreter's lifetime.  This behavior does
     not apply if the GIL has been explicitly enabled or disabled with
     ‘PYTHON_GIL’ or ‘-Xgil’.

   - gh-118513(6): Fix incorrect *note UnboundLocalError: 14a4. when two
     comprehensions in the same function both reference the same name,
     and in one comprehension the name is bound while in the other it's
     an implicit global.

   - gh-118518(7): Allow the Linux perf support to work without frame
     pointers using perf's advanced JIT support.  The feature is
     activated when using the ‘PYTHON_PERF_JIT_SUPPORT’ environment
     variable or when running Python with ‘-Xperf_jit’.  Patch by Pablo
     Galindo.

   - gh-117514(8): Add ‘sys._is_gil_enabled()’ function that returns
     whether the GIL is currently enabled.  In the default build it
     always returns ‘True’ because the GIL is always enabled.  In the
     free-threaded build, it may return ‘True’ or ‘False’.

   - gh-118164(9): Break a loop between the Python implementation of the
     *note decimal: 2e. module and the Python code for integer to string
     conversion.  Also optimize integer to string conversion for values
     in the range from 9_000 to 135_000 decimal digits.

   - gh-118473(10): Fix *note sys.set_asyncgen_hooks(): 151a. not to be
     partially set when raising *note TypeError: 4dd.

   - gh-118465(11): Compiler populates the new ‘__firstlineno__’ field
     on a class with the line number of the first line of the class
     definition.

   - gh-118492(12): Fix an issue where the type cache can expose a
     previously accessed attribute when a finalizer is run.

   - gh-117714(13): update ‘async_generator.athrow().close()’ and
     ‘async_generator.asend().close()’ to close their section of the
     underlying async generator

   - gh-111201(14): The *note interactive: 14d. interpreter is now
     implemented in Python, which allows for a number of new features
     like colors, multiline input, history viewing, and paste mode.
     Contributed by Pablo Galindo, Łukasz Langa and Lysandros Nikolaou
     based on code from the PyPy project.

   - gh-74929(15): Implement PEP 667: converted *note
     FrameType.f_locals: 165. and *note PyFrame_GetLocals(): 35f. to
     return a write-through proxy object when the frame refers to a
     function or comprehension.

   - gh-116767(16): Fix crash in compiler on 'async with' that has many
     context managers.

   - gh-118335(17): Change how to use the tier 2 interpreter.  Instead
     of running Python with ‘-X uops’ or setting the environment
     variable ‘PYTHON_UOPS=1’, this choice is now made at build time by
     configuring with ‘--enable-experimental-jit=interpreter’.

     'Beware!'  This changes the environment variable to enable or
     disable micro-ops to ‘PYTHON_JIT’.  The old ‘PYTHON_UOPS’ is no
     longer used.

   - gh-118306(18): Update JIT compilation to use LLVM 18

   - gh-118160(19): *note Annotation scopes: 16e. within classes can now
     contain comprehensions.  However, such comprehensions are not
     inlined into their parent scope at runtime.  Patch by Jelle
     Zijlstra.

   - gh-118272(20): Fix bug where ‘generator.close’ does not free the
     generator frame's locals.

   - gh-118216(21): Don't consider *note __future__: 0. imports with
     dots before the module name.

   - gh-118074(22): Make sure that the Executor objects in the
     COLD_EXITS array aren't assumed to be GC-able (which would access
     bytes outside the object).

   - gh-107674(23): Lazy load frame line number to improve performance
     of tracing

   - gh-118082(24): Improve *note SyntaxError: 173. message for imports
     without names, like in ‘from x import’ and ‘import’ cases.  It now
     points out to users that *note import: 586. expects at least one
     name after it.

   - gh-118090(25): Improve *note SyntaxError: 173. message for empty
     type param brackets.

   - gh-117958(26): Added a ‘get_jit_code()’ method to access JIT
     compiled machine code from the UOp Executor when the experimental
     JIT is enabled.  Patch by Anthony Shaw.

   - gh-117901(27): Add option for compiler's codegen to save nested
     instruction sequences for introspection.

   - gh-116622(28): Redirect stdout and stderr to system log when
     embedded in an Android app.

   - gh-109118(29): *note annotation scope: 16e. within class scopes can
     now contain lambdas.

   - gh-117894(30): Prevent ‘agen.aclose()’ objects being re-used after
     ‘.throw()’.

   - gh-117881(31): prevent concurrent access to an async generator via
     athrow().throw() or asend().throw()

   - gh-117536(32): Fix a *note RuntimeWarning: 1a3. when calling
     ‘agen.aclose().throw(Exception)’.

   - gh-117755(33): Fix mimalloc allocator for huge memory allocation
     (around 8,589,934,592 GiB) on s390x.  Patch by Victor Stinner.

   - gh-117750(34): Fix issue where an object's dict would get out of
     sync with the object's internal values when being cleared.
     ‘obj.__dict__.clear()’ now clears the internal values, but leaves
     the dict attached to the object.

   - gh-117431(35): Improve the performance of the following *note
     bytes: 1a5. and *note bytearray: 4e3. methods by adapting them to
     the *note METH_FASTCALL: 151b. calling convention:

        * ‘count()’

        * ‘find()’

        * ‘index()’

        * ‘rfind()’

        * ‘rindex()’

   - gh-117709(36): Speed up calls to *note str(): 3f2. with
     positional-only argument, by using the PEP 590(37) ‘vectorcall’
     calling convention.  Patch by Erlend Aasland.

   - gh-117680(38): Give ‘_PyInstructionSequence’ a Python interface and
     use it in tests.

   - gh-115776(39): Statically allocated objects are, by definition,
     immortal so must be marked as such regardless of whether they are
     in extension modules or not.

   - gh-117385(40): Remove unhandled ‘PY_MONITORING_EVENT_BRANCH’ and
     ‘PY_MONITORING_EVENT_EXCEPTION_HANDLED’ events from *note
     sys.settrace(): 146e.

   - gh-116322(41): Extension modules may indicate to the runtime that
     they can run without the GIL. Multi-phase init modules do so by
     calling providing ‘Py_MOD_GIL_NOT_USED’ for the ‘Py_mod_gil’ slot,
     while single-phase init modules call ‘PyUnstable_Module_SetGIL(mod,
     Py_MOD_GIL_NOT_USED)’ from their init function.

   - gh-116129(42): Implement PEP 696(43), adding support for defaults
     on type parameters.  Patch by Jelle Zijlstra.

   - gh-93502(44): Add two new functions to the C-API, *note
     PyRefTracer_SetTracer(): 343. and *note PyRefTracer_GetTracer():
     344, that allows to track object creation and destruction the same
     way the *note tracemalloc: e8. module does.  Patch by Pablo Galindo

   - gh-107674(45): Improved the performance of *note sys.settrace():
     146e. significantly

   - gh-95754(46): Improve the error message when a script shadowing a
     module from the standard library causes *note AttributeError: 2f6.
     to be raised.  Similarly, improve the error message when a script
     shadowing a third party module attempts to access an attribute from
     that third party module while still initialising.

   - gh-99180(47): Elide uninformative traceback indicators in ‘return’
     and simple ‘assignment’ statements.  Patch by Pablo Galindo.

   - gh-105879(48): Allow the 'globals' and 'locals' arguments to *note
     exec(): 162. and *note eval(): 163. to be passed as keywords.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/118414

   (2) https://github.com/python/cpython/issues/117953

   (3) https://github.com/python/cpython/issues/117549

   (4) https://github.com/python/cpython/issues/95382

   (5) https://github.com/python/cpython/issues/116322

   (6) https://github.com/python/cpython/issues/118513

   (7) https://github.com/python/cpython/issues/118518

   (8) https://github.com/python/cpython/issues/117514

   (9) https://github.com/python/cpython/issues/118164

   (10) https://github.com/python/cpython/issues/118473

   (11) https://github.com/python/cpython/issues/118465

   (12) https://github.com/python/cpython/issues/118492

   (13) https://github.com/python/cpython/issues/117714

   (14) https://github.com/python/cpython/issues/111201

   (15) https://github.com/python/cpython/issues/74929

   (16) https://github.com/python/cpython/issues/116767

   (17) https://github.com/python/cpython/issues/118335

   (18) https://github.com/python/cpython/issues/118306

   (19) https://github.com/python/cpython/issues/118160

   (20) https://github.com/python/cpython/issues/118272

   (21) https://github.com/python/cpython/issues/118216

   (22) https://github.com/python/cpython/issues/118074

   (23) https://github.com/python/cpython/issues/107674

   (24) https://github.com/python/cpython/issues/118082

   (25) https://github.com/python/cpython/issues/118090

   (26) https://github.com/python/cpython/issues/117958

   (27) https://github.com/python/cpython/issues/117901

   (28) https://github.com/python/cpython/issues/116622

   (29) https://github.com/python/cpython/issues/109118

   (30) https://github.com/python/cpython/issues/117894

   (31) https://github.com/python/cpython/issues/117881

   (32) https://github.com/python/cpython/issues/117536

   (33) https://github.com/python/cpython/issues/117755

   (34) https://github.com/python/cpython/issues/117750

   (35) https://github.com/python/cpython/issues/117431

   (36) https://github.com/python/cpython/issues/117709

   (37) https://peps.python.org/pep-0590/

   (38) https://github.com/python/cpython/issues/117680

   (39) https://github.com/python/cpython/issues/115776

   (40) https://github.com/python/cpython/issues/117385

   (41) https://github.com/python/cpython/issues/116322

   (42) https://github.com/python/cpython/issues/116129

   (43) https://peps.python.org/pep-0696/

   (44) https://github.com/python/cpython/issues/93502

   (45) https://github.com/python/cpython/issues/107674

   (46) https://github.com/python/cpython/issues/95754

   (47) https://github.com/python/cpython/issues/99180

   (48) https://github.com/python/cpython/issues/105879


File: python.info,  Node: Library<6>,  Next: Documentation<2>,  Prev: Core and Builtins<7>,  Up: Python 3 13 0 beta 1

1.23.7.3 Library
................

   - gh-118418(1): A *note DeprecationWarning: 18b. is now emitted if
     you fail to pass a value to the new 'type_params' parameter of
     ‘typing._eval_type()’ or ‘typing.ForwardRef._evaluate()’.  (Using
     either of these private and undocumented functions is discouraged
     to begin with, but failing to pass a value to the ‘type_params’
     parameter may lead to incorrect behaviour on Python 3.12 or newer.)

   - gh-118660(2): Add an optional second type parameter to *note
     typing.ContextManager: c35. and *note typing.AsyncContextManager:
     151d, representing the return types of *note __exit__(): 1293. and
     *note __aexit__(): 151e. respectively.  This parameter defaults to
     ‘bool | None’.

   - gh-118650(3): The ‘enum’ module allows method named ‘_repr_*’ to be
     defined on ‘Enum’ types.

   - gh-118648(4): Add type parameter defaults to *note
     typing.Generator: 151f. and *note typing.AsyncGenerator: 1520.

   - gh-101137(5): Mime type ‘text/x-rst’ is now supported by *note
     mimetypes: 82.

   - gh-118164(6): The Python implementation of the ‘decimal’ module
     could appear to hang in relatively small power cases (like
     ‘2**117’) if context precision was set to a very high value.  A
     different method to check for exactly representable results is used
     now that doesn't rely on computing ‘10**precision’ (which could be
     effectively too large to compute).

   - gh-111744(7): ‘breakpoint()’ and ‘pdb.set_trace()’ now enter the
     debugger immediately after the call rather than before the next
     line is executed.

   - gh-118500(8): Add *note pdb: 94. support for zipapps

   - gh-118406(9): Add signature for *note sqlite3.Connection: 22a.
     objects.

   - gh-101732(10): Use a Y2038 compatible openssl time function when
     available.

   - gh-118404(11): Fix *note inspect.signature(): 6dc. for
     non-comparable callables.

   - gh-118402(12): Fix *note inspect.signature(): 6dc. for the result
     of the *note functools.cmp_to_key(): 1172. call.

   - gh-116622(13): On Android, *note sysconfig.get_platform: 11da. now
     returns the format specified by PEP 738(14).

   - gh-118285(15): Allow to specify the signature of custom callable
     instances of extension type by the ‘__text_signature__’ attribute.
     Specify signatures of *note operator.attrgetter: dd9, *note
     operator.itemgetter: a05, and *note operator.methodcaller: dda.
     instances.

   - gh-118314(16): Fix an edge case in *note binascii.a2b_base64():
     1521. strict mode, where excessive padding is not detected when no
     padding is necessary.

   - gh-118271(17): Add the ‘PhotoImage’ methods ‘read()’ to read an
     image from a file and ‘data()’ to get the image data.  Add
     'background' and 'grayscale' parameters to ‘PhotoImage’ method
     ‘write()’.

   - gh-118225(18): Add the ‘PhotoImage’ method ‘copy_replace()’ to copy
     a region from one image to other image, possibly with pixel zooming
     and/or subsampling.  Add 'from_coords' parameter to ‘PhotoImage’
     methods ‘copy()’, ‘zoom()’ and ‘subsample()’.  Add 'zoom' and
     'subsample' parameters to ‘PhotoImage’ method ‘copy()’.

   - gh-118221(19): Fix a bug where *note sqlite3.Connection.iterdump():
     22c. could fail if a custom *note row factory: 1522. was used.
     Patch by Erlend Aasland.

   - gh-118013(20): Fix regression introduced in gh-103193(21) that
     meant that calling *note inspect.getattr_static(): 43c. on an
     instance would cause a strong reference to that instance's class to
     persist in an internal cache in the *note inspect: 72. module.
     This caused unexpected memory consumption if the class was
     dynamically created, the class held strong references to other
     objects which took up a significant amount of memory, and the cache
     contained the sole strong reference to the class.  The fix for the
     regression leads to a slowdown in ‘getattr_static()’, but the
     function should still be significantly faster than it was in Python
     3.11.  Patch by Alex Waygood.

   - gh-118218(22): Speed up *note itertools.pairwise(): 7b9. in the
     common case by up to 1.8x.

   - gh-117486(23): Improve the behavior of user-defined subclasses of
     *note ast.AST: 18c.  Such classes will now require no changes in
     the usual case to conform with the behavior changes of the *note
     ast: 7. module in Python 3.13.  Patch by Jelle Zijlstra.

   - gh-90848(24): Fixed *note unittest.mock.create_autospec(): 14fb. to
     configure parent mock with keyword arguments.

   - gh-118168(25): Fix incorrect argument substitution when *note
     typing.Unpack: 1523. is used with the builtin *note tuple: 322.
     ‘typing.Unpack’ now raises *note TypeError: 4dd. when used with
     certain invalid types.  Patch by Jelle Zijlstra.

   - gh-118131(26): Add command-line interface for the *note random: a6.
     module.  Patch by Hugo van Kemenade.

   - gh-118107(27): Fix *note zipimport: 118. reading of ZIP64 files
     with file entries that are too big or offset too far.

   - gh-102511(28): Fix *note os.path.normpath(): 12ae. for UNC paths on
     Windows.  Speed up *note os.path.splitroot(): 44c. with a native
     implementation.

   - gh-117535(29): Change the unknown filename of *note warnings: fa.
     from ‘sys’ to ‘<sys>’ to clarify that it's not a real filename.

   - gh-114053(30): Fix erroneous *note NameError: 3e5. when calling
     *note typing.get_type_hints(): 657. on a class that made use of PEP
     695(31) type parameters in a module that had ‘from __future__
     import annotations’ at the top of the file.  Patch by Alex Waygood.

   - gh-116931(32): Add parameter 'fileobj' check for *note
     tarfile.TarFile.addfile(): 1524.

   - gh-117995(33): Don't raise *note DeprecationWarning: 18b. when a
     *note sequence: 499. of parameters is used to bind indexed,
     nameless placeholders.  See also gh-100668(34).

   - gh-80361(35): Fix TypeError in *note
     email.message.Message.get_payload(): 1165. when the charset is RFC
     2231(36) encoded.

   - gh-86650(37): Fix IndexError when parse some emails with invalid
     Message-ID (including one-off addresses generated by Microsoft
     Outlook).

   - gh-117691(38): Improve the error messages emitted by *note tarfile:
     c8. deprecation warnings relating to PEP 706.  If a ‘filter’
     argument is not provided to ‘extract()’ or ‘extractall’, the
     deprecation warning now points to the line in the user's code where
     the relevant function was called.  Patch by Alex Waygood.

   - gh-115874(39): Fixed a possible segfault during garbage collection
     of ‘_asyncio.FutureIter’ objects.  Patch by Savannah Ostrowski.

   - gh-115060(40): Speed up *note pathlib.Path.glob(): 212. by omitting
     an initial *note is_dir(): 215. call.  As a result of this change,
     *note glob(): 212. can no longer raise *note OSError: 350.

   - gh-77102(41): *note site: b5. module now parses ‘.pth’ file with
     UTF-8 first, and *note locale encoding: 227. if
     ‘UnicodeDecodeError’ happened.  It supported only locale encoding
     before.

   - gh-76785(42): We've exposed the low-level ‘_interpreters’ module
     for the sake of the PyPI implementation of PEP 734(43).  It was
     sometimes available as the ‘_xxsubinterpreters’ module and was
     formerly used only for testing.  For the most part, it should be
     considered an internal module, like ‘_thread’ and ‘_imp’.  See
     ‘https://discuss.python.org/t/pep-734-multiple-interpreters-in-the-stdlib/41147/26’.

   - gh-115060(44): Speed up *note pathlib.Path.glob(): 212. by not
     scanning directories for non-wildcard pattern segments.

   - gh-117727(45): Speed up *note pathlib.Path.iterdir(): 1525. by
     using *note os.scandir(): a02. internally.

   - gh-117586(46): Speed up *note pathlib.Path.walk(): 450. by working
     with strings internally.

   - gh-117722(47): Change the new multi-separator support in *note
     asyncio.StreamReader.readuntil(): 19a. to only accept tuples of
     separators rather than arbitrary iterables.

   - gh-117692(48): Fixes a bug when *note doctest.DocTestFinder: 1526.
     was failing on wrapped ‘builtin_function_or_method’.

   - gh-117348(49): Largely restored import time performance of
     configparser by avoiding dataclasses.

   - gh-117641(50): Speedup *note os.path.commonpath(): de3. on Unix.

   - gh-117663(51): Fix ‘_simple_enum’ to detect aliases when multiple
     arguments are present but only one is the member value.

   - gh-117636(52): Speedup *note os.path.join(): 1527.

   - gh-117618(53): Support ‘package.module’ as ‘filename’ for ‘break’
     command of *note pdb: 94.

   - gh-102247(54): the status codes enum with constants in
     http.HTTPStatus are updated to include the names from RFC9110.
     This RFC includes some HTTP statuses previously only used for
     WEBDAV and assigns more generic names to them.

     The old constants are preserved for backwards compatibility.

   - gh-117607(55): Speedup *note os.path.relpath(): 452.

   - gh-117586(56): Speed up *note pathlib.Path.glob(): 212. by working
     with strings internally.

   - gh-117225(57): Add colour to doctest output.  Patch by Hugo van
     Kemenade.

   - gh-117566(58): *note ipaddress.IPv6Address.is_loopback(): 1528.
     will now return ‘True’ for IPv4-mapped loopback addresses, i.e.
     addresses in the ‘::ffff:127.0.0.0/104’ address space.

   - gh-117546(59): Fix issue where *note os.path.realpath(): 20a.
     stopped resolving symlinks after encountering a symlink loop on
     POSIX.

   - gh-116720(60): Improved behavior of *note asyncio.TaskGroup: 19b.
     when an external cancellation collides with an internal
     cancellation.  For example, when two task groups are nested and
     both experience an exception in a child task simultaneously, it was
     possible that the outer task group would misbehave, because its
     internal cancellation was swallowed by the inner task group.

     In the case where a task group is cancelled externally and also
     must raise an *note ExceptionGroup: 19c, it will now call the
     parent task's *note cancel(): 19d. method.  This ensures that a
     *note asyncio.CancelledError: 19e. will be raised at the next *note
     await: 19f, so the cancellation is not lost.

     An added benefit of these changes is that task groups now preserve
     the cancellation count (*note asyncio.Task.cancelling(): 1a0.).

     In order to handle some corner cases, *note
     asyncio.Task.uncancel(): 1a1. may now reset the undocumented
     ‘_must_cancel’ flag when the cancellation count reaches zero.

   - gh-117516(61): Add *note typing.TypeIs: 147, implementing PEP
     742(62).  Patch by Jelle Zijlstra.

   - gh-117503(63): Fix support of non-ASCII user names in bytes paths
     in *note os.path.expanduser(): 9b8. on Posix.

   - gh-117394(64): *note os.path.ismount(): 9b6. is now 2-3 times
     faster if the user has permissions.

   - gh-117313(65): Only treat ‘'\n'’, ‘'\r'’ and ‘'\r\n'’ as line
     separators in re-folding the *note email: 32. messages.  Preserve
     control characters ‘'\v'’, ‘'\f'’, ‘'\x1c'’, ‘'\x1d'’ and ‘'\x1e'’
     and Unicode line separators ‘'\x85'’, ‘'\u2028'’ and ‘'\u2029'’ as
     is.

   - gh-117142(66): Convert ‘_ctypes’ to multi-phase initialisation (
     PEP 489(67)).

   - gh-66543(68): Add the *note mimetypes.guess_file_type(): 1ec.
     function which works with file path.  Passing file path instead of
     URL in *note guess_type(): 1ed. is *note soft deprecated: 1ee.

   - gh-68583(69): webbrowser CLI: replace getopt with argparse, add
     long options.  Patch by Hugo van Kemenade.

   - gh-116871(70): Name suggestions for *note AttributeError: 2f6. and
     *note ImportError: 352. now only include underscored names if the
     original name was underscored.

   - gh-116023(71): Don't show empty fields (value ‘None’ or ‘[]’) in
     *note ast.dump(): 889. by default.  Add ‘show_empty=False’
     parameter to optionally show them.

   - gh-115961(72): Added ‘name’ and ‘mode’ attributes for compressed
     and archived file-like objects in modules *note bz2: f, *note lzma:
     7e, *note tarfile: c8. and *note zipfile: 117.  The value of the
     ‘mode’ attribute of *note gzip.GzipFile: 354. was changed from
     integer (‘1’ or ‘2’) to string (‘'rb'’ or ‘'wb'’).  The value of
     the ‘mode’ attribute of the readable file-like object returned by
     *note zipfile.ZipFile.open(): 355. was changed from ‘'r'’ to
     ‘'rb'’.

   - gh-82062(73): Fix *note inspect.signature(): 6dc. to correctly
     handle parameter defaults on methods in extension modules that use
     names defined in the module namespace.

   - gh-83856(74): Honor *note atexit: 9. for all *note multiprocessing:
     86. start methods

   - gh-113081(75): Print colorized exception just like built-in
     traceback in *note pdb: 94.

   - gh-112855(76): Speed up pickling of *note pathlib.PurePath: 44e.
     objects.  Patch by Barney Gale.

   - gh-111744(77): Support opcode events in *note bdb: b.

   - gh-109617(78): ‘ncurses’: fixed a crash that could occur on macOS
     13 or earlier when Python was built with Apple Xcode 15's SDK.

   - gh-83151(79): Enabled arbitrary statements and evaluations in *note
     pdb: 94. shell to access the local variables of the current frame,
     which made it possible for multi-scope code like generators or
     nested function to work.

   - gh-110209(80): Add *note __class_getitem__(): 6df. to *note
     types.GeneratorType: 1529. and *note types.CoroutineType: e2d. for
     type hinting purposes.  Patch by James Hilton-Balfe.

   - gh-108191(81): The *note types.SimpleNamespace: 1b5. now accepts an
     optional positional argument which specifies initial values of
     attributes as a dict or an iterable of key-value pairs.

   - gh-62090(82): Fix assertion errors caused by whitespace in metavars
     or ‘SUPPRESS’-ed groups in *note argparse: 5. by simplifying usage
     formatting.  Patch by Ali Hamdan.

   - gh-102402(83): Adjust ‘logging.LogRecord’ to use ‘time.time_ns()’
     and fix minor bug related to floating-point math.

   - gh-100242(84): Bring pure Python implementation
     ‘functools.partial.__new__’ more in line with the C-implementation
     by not just always checking for the presence of the attribute
     ‘'func'’ on the first argument of ‘partial’.  Instead, both the
     Python version and the C version perform an ‘isinstance(func,
     partial)’ check on the first argument of ‘partial’.

   - gh-99730(85): HEAD requests are no longer upgraded to GET request
     during redirects in urllib.

   - gh-66410(86): Setting the ‘tkinter’ module global ‘wantobjects’ to
     ‘2’ before creating the *note Tk: 152a. object or call the
     ‘wantobjects()’ method of the ‘Tk’ object with argument ‘2’ makes
     now arguments to callbacks registered in the *note tkinter: d9.
     module to be passed as various Python objects (‘int’, ‘float’,
     ‘bytes’, ‘tuple’), depending on their internal representation in
     Tcl, instead of always ‘str’.  ‘tkinter.wantobjects’ is now set to
     ‘2’ by default.

   - bpo-40943(87): Fix several IndexError when parse emails with
     truncated Message-ID, address, routes, etc, e.g.  ‘example@’.

   - bpo-39324(88): Add mime type mapping for .md <-> text/markdown

   - bpo-18108(89): *note shutil.chown(): 225. now supports 'dir_fd' and
     'follow_symlinks' keyword arguments.

   - bpo-30988(90): Fix parsing of emails with invalid address headers
     having a leading or trailing dot.  Patch by tsufeki.

   - bpo-32839(91): Add the ‘after_info()’ method for Tkinter widgets.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/118418

   (2) https://github.com/python/cpython/issues/118660

   (3) https://github.com/python/cpython/issues/118650

   (4) https://github.com/python/cpython/issues/118648

   (5) https://github.com/python/cpython/issues/101137

   (6) https://github.com/python/cpython/issues/118164

   (7) https://github.com/python/cpython/issues/111744

   (8) https://github.com/python/cpython/issues/118500

   (9) https://github.com/python/cpython/issues/118406

   (10) https://github.com/python/cpython/issues/101732

   (11) https://github.com/python/cpython/issues/118404

   (12) https://github.com/python/cpython/issues/118402

   (13) https://github.com/python/cpython/issues/116622

   (14) https://peps.python.org/pep-0738/

   (15) https://github.com/python/cpython/issues/118285

   (16) https://github.com/python/cpython/issues/118314

   (17) https://github.com/python/cpython/issues/118271

   (18) https://github.com/python/cpython/issues/118225

   (19) https://github.com/python/cpython/issues/118221

   (20) https://github.com/python/cpython/issues/118013

   (21) https://github.com/python/cpython/issues/103193

   (22) https://github.com/python/cpython/issues/118218

   (23) https://github.com/python/cpython/issues/117486

   (24) https://github.com/python/cpython/issues/90848

   (25) https://github.com/python/cpython/issues/118168

   (26) https://github.com/python/cpython/issues/118131

   (27) https://github.com/python/cpython/issues/118107

   (28) https://github.com/python/cpython/issues/102511

   (29) https://github.com/python/cpython/issues/117535

   (30) https://github.com/python/cpython/issues/114053

   (31) https://peps.python.org/pep-0695/

   (32) https://github.com/python/cpython/issues/116931

   (33) https://github.com/python/cpython/issues/117995

   (34) https://github.com/python/cpython/issues/100668

   (35) https://github.com/python/cpython/issues/80361

   (36) https://datatracker.ietf.org/doc/html/rfc2231.html

   (37) https://github.com/python/cpython/issues/86650

   (38) https://github.com/python/cpython/issues/117691

   (39) https://github.com/python/cpython/issues/115874

   (40) https://github.com/python/cpython/issues/115060

   (41) https://github.com/python/cpython/issues/77102

   (42) https://github.com/python/cpython/issues/76785

   (43) https://peps.python.org/pep-0734/

   (44) https://github.com/python/cpython/issues/115060

   (45) https://github.com/python/cpython/issues/117727

   (46) https://github.com/python/cpython/issues/117586

   (47) https://github.com/python/cpython/issues/117722

   (48) https://github.com/python/cpython/issues/117692

   (49) https://github.com/python/cpython/issues/117348

   (50) https://github.com/python/cpython/issues/117641

   (51) https://github.com/python/cpython/issues/117663

   (52) https://github.com/python/cpython/issues/117636

   (53) https://github.com/python/cpython/issues/117618

   (54) https://github.com/python/cpython/issues/102247

   (55) https://github.com/python/cpython/issues/117607

   (56) https://github.com/python/cpython/issues/117586

   (57) https://github.com/python/cpython/issues/117225

   (58) https://github.com/python/cpython/issues/117566

   (59) https://github.com/python/cpython/issues/117546

   (60) https://github.com/python/cpython/issues/116720

   (61) https://github.com/python/cpython/issues/117516

   (62) https://peps.python.org/pep-0742/

   (63) https://github.com/python/cpython/issues/117503

   (64) https://github.com/python/cpython/issues/117394

   (65) https://github.com/python/cpython/issues/117313

   (66) https://github.com/python/cpython/issues/117142

   (67) https://peps.python.org/pep-0489/

   (68) https://github.com/python/cpython/issues/66543

   (69) https://github.com/python/cpython/issues/68583

   (70) https://github.com/python/cpython/issues/116871

   (71) https://github.com/python/cpython/issues/116023

   (72) https://github.com/python/cpython/issues/115961

   (73) https://github.com/python/cpython/issues/82062

   (74) https://github.com/python/cpython/issues/83856

   (75) https://github.com/python/cpython/issues/113081

   (76) https://github.com/python/cpython/issues/112855

   (77) https://github.com/python/cpython/issues/111744

   (78) https://github.com/python/cpython/issues/109617

   (79) https://github.com/python/cpython/issues/83151

   (80) https://github.com/python/cpython/issues/110209

   (81) https://github.com/python/cpython/issues/108191

   (82) https://github.com/python/cpython/issues/62090

   (83) https://github.com/python/cpython/issues/102402

   (84) https://github.com/python/cpython/issues/100242

   (85) https://github.com/python/cpython/issues/99730

   (86) https://github.com/python/cpython/issues/66410

   (87) https://bugs.python.org/issue?@action=redirect&bpo=40943

   (88) https://bugs.python.org/issue?@action=redirect&bpo=39324

   (89) https://bugs.python.org/issue?@action=redirect&bpo=18108

   (90) https://bugs.python.org/issue?@action=redirect&bpo=30988

   (91) https://bugs.python.org/issue?@action=redirect&bpo=32839


File: python.info,  Node: Documentation<2>,  Next: Build<6>,  Prev: Library<6>,  Up: Python 3 13 0 beta 1

1.23.7.4 Documentation
......................

   - gh-117928(1): The minimum Sphinx version required for the
     documentation is now 6.2.1.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/117928


File: python.info,  Node: Build<6>,  Next: Windows<3>,  Prev: Documentation<2>,  Up: Python 3 13 0 beta 1

1.23.7.5 Build
..............

   - gh-118734(1): Fixes Windows build when invoked directly (not
     through the ‘build.bat’ script) without specifying a value for
     ‘UseTIER2’.

   - gh-115119(2): The ‘configure’ option *note -with-system-libmpdec:
     34d. now defaults to ‘yes’.  The bundled copy of ‘libmpdecimal’
     will be removed in Python 3.15.

   - gh-117845(3): Fix building against recent libedit versions by
     detecting readline hook signatures in ‘configure’.

   - gh-116622(4): A testbed project was added to run the test suite on
     Android.

   - gh-117645(5): Increase WASI stack size from 512 KiB to 8 MiB and
     the initial memory from 10 MiB to 20 MiB. Patch by Victor Stinner.

   - gh-115119(6): ‘configure’ now uses ‘pkg-config’ to detect *note
     decimal: 2e. dependencies if the *note -with-system-libmpdec: 34d.
     option is given.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/118734

   (2) https://github.com/python/cpython/issues/115119

   (3) https://github.com/python/cpython/issues/117845

   (4) https://github.com/python/cpython/issues/116622

   (5) https://github.com/python/cpython/issues/117645

   (6) https://github.com/python/cpython/issues/115119


File: python.info,  Node: Windows<3>,  Next: macOS<2>,  Prev: Build<6>,  Up: Python 3 13 0 beta 1

1.23.7.6 Windows
................

   - gh-115119(1): Update Windows installer to use libmpdecimal 4.0.0.

   - gh-118486(2): *note os.mkdir(): 202. now accepts 'mode' of ‘0o700’
     to restrict the new directory to the current user.

   - gh-118347(3): Fixes launcher updates not being installed.

   - gh-118293(4): The ‘multiprocessing’ module now passes the
     ‘STARTF_FORCEOFFFEEDBACK’ flag when spawning processes to tell
     Windows not to change the mouse cursor.

   - gh-115009(5): Update Windows installer to use SQLite 3.45.3.

   - gh-90329(6): Suppress the warning displayed on virtual environment
     creation when the requested and created paths differ only by a
     short (8.3 style) name.  Warnings will continue to be shown if a
     junction or symlink in the path caused the venv to be created in a
     different location than originally requested.

   - gh-117786(7): Fixes virtual environments not correctly launching
     when created from a Store install.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/115119

   (2) https://github.com/python/cpython/issues/118486

   (3) https://github.com/python/cpython/issues/118347

   (4) https://github.com/python/cpython/issues/118293

   (5) https://github.com/python/cpython/issues/115009

   (6) https://github.com/python/cpython/issues/90329

   (7) https://github.com/python/cpython/issues/117786


File: python.info,  Node: macOS<2>,  Next: IDLE<6>,  Prev: Windows<3>,  Up: Python 3 13 0 beta 1

1.23.7.7 macOS
..............

   - gh-115119(1): Update macOS installer to use libmpdecimal 4.0.0.

   - gh-114099(2): iOS preprocessor symbol usage was made compatible
     with older macOS SDKs.

   - gh-115009(3): Update macOS installer to use SQLite 3.45.3.

   - gh-91629(4): Use ‘~/.config/fish/conf.d’ configs and
     ‘fish_add_path’ to set ‘PATH’ when installing for the Fish shell.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/115119

   (2) https://github.com/python/cpython/issues/114099

   (3) https://github.com/python/cpython/issues/115009

   (4) https://github.com/python/cpython/issues/91629


File: python.info,  Node: IDLE<6>,  Next: C API<6>,  Prev: macOS<2>,  Up: Python 3 13 0 beta 1

1.23.7.8 IDLE
.............

   - bpo-34774(1): Use user-selected color theme for Help => IDLE Doc.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=34774


File: python.info,  Node: C API<6>,  Prev: IDLE<6>,  Up: Python 3 13 0 beta 1

1.23.7.9 C API
..............

   - gh-118124(1): Fix ‘Py_BUILD_ASSERT’ and ‘Py_BUILD_ASSERT_EXPR’ for
     non-constant expressions: use ‘static_assert()’ on C11 and newer.
     Patch by Victor Stinner.

   - gh-110850(2): Add "Raw" variant of PyTime functions

        * *note PyTime_MonotonicRaw(): 335.

        * *note PyTime_PerfCounterRaw(): 337.

        * *note PyTime_TimeRaw(): 339.

     Patch by Victor Stinner.

   - gh-117987(3): Restore functions removed in Python 3.13 alpha 1:

        * *note Py_SetPythonHome(): 1531.

        * *note Py_SetProgramName(): 1532.

        * *note PySys_SetArgvEx(): 1533.

        * *note PySys_SetArgv(): 1534.

     Patch by Victor Stinner.

   - gh-117929(4): Restore removed *note PyEval_InitThreads(): 1535.
     function.  Patch by Victor Stinner.

   - gh-117534(5): Improve validation logic in the C implementation of
     *note datetime.datetime.fromisoformat(): 5bc. to better handle
     invalid years.  Patch by Vlad Efanov.

   - gh-68114(6): Fixed skipitem()'s handling of the old 'w' and 'w#'
     formatters.  These are no longer supported and now raise an
     exception if used.

   - gh-111997(7): Add a C-API for firing monitoring events.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/118124

   (2) https://github.com/python/cpython/issues/110850

   (3) https://github.com/python/cpython/issues/117987

   (4) https://github.com/python/cpython/issues/117929

   (5) https://github.com/python/cpython/issues/117534

   (6) https://github.com/python/cpython/issues/68114

   (7) https://github.com/python/cpython/issues/111997


File: python.info,  Node: Python 3 13 0 alpha 6,  Next: Python 3 13 0 alpha 5,  Prev: Python 3 13 0 beta 1,  Up: Changelog（更動日誌）

1.23.8 Python 3.13.0 alpha 6
----------------------------

'Release date: 2024-04-09'

* Menu:

* Core and Builtins: Core and Builtins<8>.
* Library: Library<7>.
* Documentation: Documentation<3>.
* Tests: Tests<5>.
* Build: Build<7>.
* Windows: Windows<4>.
* C API: C API<7>.


File: python.info,  Node: Core and Builtins<8>,  Next: Library<7>,  Up: Python 3 13 0 alpha 6

1.23.8.1 Core and Builtins
..........................

   - gh-117494(1): Refactored the instruction sequence data structure
     out of compile.c into instruction_sequence.c.

   - gh-116968(2): Introduce a unified 16-bit backoff counter type
     (‘_Py_BackoffCounter’), shared between the Tier 1 adaptive
     specializer and the Tier 2 optimizer.  The API used for adaptive
     specialization counters is changed but the behavior is (supposed to
     be) identical.

     The behavior of the Tier 2 counters is changed:

        * There are no longer dynamic thresholds (we never varied
          these).

        * All counters now use the same exponential backoff.

        * The counter for ‘JUMP_BACKWARD’ starts counting down from 16.

        * The ‘temperature’ in side exits starts counting down from 64.

   - gh-117431(3): Improve the performance of the following *note bytes:
     1a5. and *note bytearray: 4e3. methods by adapting them to the
     *note METH_FASTCALL: 151b. calling convention:

        * ‘endswith()’

        * ‘startswith()’

   - gh-117431(4): Improve the performance of the following *note str:
     3f2. methods by adapting them to the *note METH_FASTCALL: 151b.
     calling convention:

        * *note count(): 1538.

        * *note endswith(): e6e.

        * *note find(): e4a.

        * *note index(): 1539.

        * *note rfind(): e4b.

        * *note rindex(): 11f0.

        * *note startswith(): e6d.

   - gh-117411(5): Move ‘PyFutureFeatures’ to an internal header and
     make it private.

   - gh-109120(6): Added handle of incorrect star expressions, e.g ‘f(3,
     *)’.  Patch by Grigoryev Semyon

   - gh-117266(7): Fix crashes for certain user-created subclasses of
     *note ast.AST: 18c.  Such classes are now expected to set the
     ‘_field_types’ attribute.

   - gh-99108(8): Updated the *note hashlib: 5e. built-in HACL*
     project(9) C code from upstream that we use for many
     implementations when they are not present via OpenSSL in a given
     build.  This also avoids the rare potential for a C symbol name one
     definition rule linking issue.

   - gh-117108(10): Change the old space bit of objects in the young
     generation from 0 to gcstate->visited, so that any objects created
     during GC will have the old bit set correctly if they get moved
     into the old generation.

   - gh-117108(11): The cycle GC now chooses the size of increments
     based on the total heap size, instead of the rate of object
     creation.  This ensures that it can keep up with growing heaps.

   - gh-116735(12): For ‘INSTRUMENTED_CALL_FUNCTION_EX’, set ‘arg0’ to
     ‘sys.monitoring.MISSING’ instead of ‘None’ for *note CALL: 153a.
     event.

   - gh-113964(13): Starting new threads and process creation through
     *note os.fork(): 17b. are now only prevented once all non-daemon
     threads exit.

   - gh-116626(14): Ensure ‘INSTRUMENTED_CALL_FUNCTION_EX’ always emits
     *note CALL: 153a.

   - gh-116554(15): ‘list.sort()’ now exploits more cases of partial
     ordering, particularly those with long descending runs with
     sub-runs of equal values.  Those are recognized as single runs now
     (previously, each block of repeated values caused a new run to be
     created).

   - gh-114099(16): Added a Loader that can discover extension modules
     in an iOS-style Frameworks folder.

   - gh-115775(17): Compiler populates the new ‘__static_attributes__’
     field on a class with the names of attributes of this class which
     are accessed through self.X from any function in its body.

   - gh-115776(18): The array of values, the ‘PyDictValues’ struct is
     now embedded in the object during allocation.  This provides better
     performance in the common case, and does not degrade as much when
     the object's ‘__dict__’ is materialized.

   - gh-108362(19): Implement an incremental cyclic garbage collector.
     By collecting the old generation in increments, there is no need
     for a full heap scan.  This can hugely reduce maximum pause time
     for programs with large heaps.

     Reduce the number of generations from three to two.  The old
     generation is split into two spaces, "visited" and "pending".

     Collection happens in two steps:: * An increment is formed from the
     young generation and a small part of the pending space.  * This
     increment is scanned and the survivors moved to the end of the
     visited space.

     When the collecting space becomes empty, the two spaces are
     swapped.

   - gh-109870(20): Dataclasses now calls *note exec(): 162. once per
     dataclass, instead of once per method being added.  This can speed
     up dataclass creation by up to 20%.

   - gh-97901(21): Mime type ‘text/rtf’ is now supported by *note
     mimetypes: 82.

   - bpo-24612(22): Improve the *note SyntaxError: 173. that happens
     when 'not' appears after an operator.  Patch by Pablo Galindo

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/117494

   (2) https://github.com/python/cpython/issues/116968

   (3) https://github.com/python/cpython/issues/117431

   (4) https://github.com/python/cpython/issues/117431

   (5) https://github.com/python/cpython/issues/117411

   (6) https://github.com/python/cpython/issues/109120

   (7) https://github.com/python/cpython/issues/117266

   (8) https://github.com/python/cpython/issues/99108

   (9) https://github.com/hacl-star/hacl-star

   (10) https://github.com/python/cpython/issues/117108

   (11) https://github.com/python/cpython/issues/117108

   (12) https://github.com/python/cpython/issues/116735

   (13) https://github.com/python/cpython/issues/113964

   (14) https://github.com/python/cpython/issues/116626

   (15) https://github.com/python/cpython/issues/116554

   (16) https://github.com/python/cpython/issues/114099

   (17) https://github.com/python/cpython/issues/115775

   (18) https://github.com/python/cpython/issues/115776

   (19) https://github.com/python/cpython/issues/108362

   (20) https://github.com/python/cpython/issues/109870

   (21) https://github.com/python/cpython/issues/97901

   (22) https://bugs.python.org/issue?@action=redirect&bpo=24612


File: python.info,  Node: Library<7>,  Next: Documentation<3>,  Prev: Core and Builtins<8>,  Up: Python 3 13 0 alpha 6

1.23.8.2 Library
................

   - gh-117648(1): Improve performance of *note os.path.join(): 1527.
     and *note os.path.expanduser(): 9b8.

   - gh-117584(2): Raise *note TypeError: 4dd. for non-paths in
     ‘posixpath.relpath()’.

   - gh-117467(3): Preserve mailbox ownership when rewriting in
     ‘mailbox.mbox.flush()’.  Patch by Tony Mountifield.

   - gh-114848(4): Raise *note FileNotFoundError: e67. when ‘getcwd()’
     returns '(unreachable)', which can happen on Linux >= 2.6.36 with
     glibc < 2.27.

   - gh-117459(5): ‘asyncio.asyncio.run_coroutine_threadsafe()’ now
     keeps the traceback of ‘CancelledError’, *note TimeoutError: 7d9.
     and ‘InvalidStateError’ which are raised in the coroutine.

   - gh-117381(6): Fix error message for ‘ntpath.commonpath()’.

   - gh-117337(7): Deprecate undocumented ‘glob.glob0()’ and
     ‘glob.glob1()’ functions.  Use *note glob.glob(): 280. and pass a
     directory to its 'root_dir' argument instead.

   - gh-117349(8): Optimise several functions in *note os.path: 92.

   - gh-117348(9): Refactored ‘configparser.RawConfigParser._read()’ to
     reduce cyclometric complexity and improve comprehensibility.

   - gh-117335(10): Raise TypeError for non-sequences for
     ‘ntpath.commonpath()’.

   - gh-66449(11): *note configparser.ConfigParser: 1aa. now accepts
     unnamed sections before named ones, if configured to do so.

   - gh-88014(12): In documentation of *note gzip.GzipFile: 354. in
     module gzip, explain data type of optional constructor argument
     'mtime', and recommend ‘mtime = 0’ for generating deterministic
     streams.

   - gh-117310(13): Fixed an unlikely early & extra ‘Py_DECREF’
     triggered crash in *note ssl: bb. when creating a new
     ‘_ssl._SSLContext’ if CPython was built implausibly such that the
     default cipher list is empty 'or' the SSL library it was linked
     against reports a failure from its C ‘SSL_CTX_set_cipher_list()’
     API.

   - gh-117294(14): A ‘DocTestCase’ now reports as skipped if all
     examples in the doctest are skipped.

   - gh-98966(15): In *note subprocess: c1, raise a more informative
     message when ‘stdout=STDOUT’.

   - gh-117225(16): doctest: only print "and X failed" when non-zero,
     don't pluralise "1 items".  Patch by Hugo van Kemenade.

   - gh-117205(17): Speed up *note compileall.compile_dir(): aca. by 20%
     when using multiprocessing by increasing ‘chunksize’.

   - gh-117178(18): Fix regression in lazy loading of self-referential
     modules, introduced in gh-114781(19).

   - gh-112383(20): Fix *note dis: 30. module's handling of
     ‘ENTER_EXECUTOR’ instructions.

   - gh-117182(21): Lazy-loading of modules that modify their own
     ‘__class__’ no longer reverts the ‘__class__’ to *note
     types.ModuleType: db9.

   - gh-117084(22): Fix *note zipfile: 117. extraction for directory
     entries with the name containing backslashes on Windows.

   - gh-117114(23): Make *note os.path.isdevdrive(): 153c. available on
     all platforms.  For those that do not offer Dev Drives, it will
     always return ‘False’.

   - gh-117110(24): Fix a bug that prevents subclasses of *note
     typing.Any: 651. to be instantiated with arguments.  Patch by Chris
     Fu.

   - gh-109653(25): Deferred select imports in importlib.metadata and
     importlib.resources for a 14% speedup.

   - gh-70647(26): Start the deprecation period for the current behavior
     of *note datetime.datetime.strptime(): 14fe. and *note
     time.strptime(): 139a. which always fails to parse a date string
     with a *note ValueError: 1e7. involving a day of month such as
     ‘strptime("02-29", "%m-%d")’ when a year is 'not' specified and the
     date happen to be February 29th.  This should help avoid users
     finding new bugs every four years due to a natural mistaken
     assumption about the API when parsing partial date values.

   - gh-116987(27): Fixed ‘inspect.findsource()’ for class code objects.

   - gh-114099(28): Modify standard library to allow for iOS platform
     differences.

   - gh-90872(29): On Windows, *note subprocess.Popen.wait(): c8b. no
     longer calls ‘WaitForSingleObject()’ with a negative timeout: pass
     ‘0’ ms if the timeout is negative.  Patch by Victor Stinner.

   - gh-116957(30): configparser: Don't leave ConfigParser values in an
     invalid state (stored as a list instead of a str) after an earlier
     read raised DuplicateSectionError or DuplicateOptionError.

   - gh-115538(31): ‘_io.WindowsConsoleIO’ now emit a warning if a
     boolean value is passed as a filedescriptor argument.

   - gh-90095(32): Ignore empty lines and comments in ‘.pdbrc’

   - gh-106531(33): Refreshed zipfile._path from zipp 3.18(34),
     providing better compatibility for PyPy, better glob performance
     for deeply nested zipfiles, and providing internal access to
     ‘CompleteDirs.inject’ for use in other tests (like
     importlib.resources).

   - gh-63207(35): On Windows, *note time.time(): 239. now uses the
     ‘GetSystemTimePreciseAsFileTime()’ clock to have a resolution
     better than 1 us, instead of the ‘GetSystemTimeAsFileTime()’ clock
     which has a resolution of 15.6 ms.  Patch by Victor Stinner.

   - gh-116764(36): Restore support of ‘None’ and other false values in
     *note urllib.parse: f3. functions *note parse_qs(): 25f. and *note
     parse_qsl(): 25e.  Also, they now raise a TypeError for non-zero
     integers and non-empty sequences.

   - gh-116811(37): In ‘PathFinder.invalidate_caches’, delegate to
     ‘MetadataPathFinder.invalidate_caches’.

   - gh-116647(38): Fix recursive child in dataclasses

   - gh-113171(39): Fixed various false positives and false negatives in

        * *note ipaddress.IPv4Address.is_private: 153d. (see these docs
          for details)

        * *note ipaddress.IPv4Address.is_global: f02.

        * *note ipaddress.IPv6Address.is_private: 153e.

        * *note ipaddress.IPv6Address.is_global: 153f.

     Also in the corresponding *note ipaddress.IPv4Network: 1e3. and
     *note ipaddress.IPv6Network: 1e4. attributes.

   - gh-63283(40): In *note encodings.idna: 48, any capitalization of
     the the ACE prefix (‘xn--’) is now acceptable.  Patch by Pepijn de
     Vos and Zackery Spytz.

   - gh-71042(41): Add *note platform.android_ver(): 1540, which
     provides device and OS information on Android.

   - gh-73468(42): Added new *note math.fma(): 1ea. function, wrapping
     C99's ‘fma()’ operation: fused multiply-add function.  Patch by
     Mark Dickinson and Victor Stinner.

   - gh-116608(43): The *note importlib.resources: 6f. functions *note
     is_resource(): 1d1, *note open_binary(): 1d2, *note open_text():
     1d3, *note path(): 1d4, *note read_binary(): 1d5, and *note
     read_text(): 1d6. are un-deprecated, and support subdirectories via
     multiple positional arguments.  The *note contents(): 1d7. function
     also allows subdirectories, but remains deprecated.

   - gh-116484(44): Change automatically generated ‘tkinter.Checkbutton’
     widget names to avoid collisions with automatically generated
     ‘tkinter.ttk.Checkbutton’ widget names within the same parent
     widget.

   - gh-114314(45): In *note ctypes: 22, ctype data is now stored in
     type objects directly rather than in a dict subclass.  This is an
     internal change that should not affect usage.

   - gh-116401(46): Fix blocking *note os.fwalk(): aff. and *note
     shutil.rmtree(): 2d2. on opening named pipe.

   - gh-71052(47): Implement *note ctypes.util.find_library(): cf0. on
     Android.

   - gh-90535(48): Fix support of 'interval' values > 1 in
     ‘logging.TimedRotatingFileHandler’ for ‘when='MIDNIGHT'’ and
     ‘when='Wx'’.

   - gh-113308(49): Remove some internal protected parts from *note
     uuid: f8.: ‘_has_uuid_generate_time_safe’, ‘_netbios_getnode’,
     ‘_ipconfig_getnode’, and ‘_load_system_functions’.  They were
     unused.

   - gh-115627(50): Fix the *note ssl: bb. module error handling of
     connection terminate by peer.  It now throws an OSError with the
     appropriate error code instead of an EOFError.

   - gh-114847(51): Speed up *note os.path.realpath(): 20a. on
     non-Windows platforms.

   - gh-114271(52): Fix a race in ‘threading.Thread.join()’.

     ‘threading._MainThread’ now always represents the main thread of
     the main interpreter.

     ‘PyThreadState.on_delete’ and ‘PyThreadState.on_delete_data’ have
     been removed.

   - gh-113538(53): Add *note asyncio.Server.close_clients(): 198. and
     *note asyncio.Server.abort_clients(): 199. methods which allow to
     more forcefully close an asyncio server.

   - gh-85287(54): Changes Unicode codecs to return UnicodeEncodeError
     or UnicodeDecodeError, rather than just UnicodeError.

   - gh-113548(55): *note pdb: 94. now allows CLI arguments to ‘pdb -m’.

   - gh-112948(56): Make completion of *note pdb: 94. similar to Python
     REPL

   - gh-105866(57): Fixed ‘_get_slots’ bug which caused error when
     defining dataclasses with slots and a weakref_slot.

   - gh-96471(58): Add *note asyncio.Queue: a19. termination with *note
     shutdown(): 196. method.

   - gh-89739(59): The *note zipimport: 118. module can now read ZIP64
     files.

   - bpo-33533(60): *note asyncio.as_completed(): 190. now returns an
     object that is both an asynchronous iterator and plain iterator.
     The new asynchronous iteration pattern allows for easier
     correlation between prior tasks and their completed results.  This
     is a closer match to *note concurrent.futures.as_completed():
     1541.'s iteration pattern.  Patch by Justin Arthur.

   - bpo-27578(61): *note inspect.getsource(): 14ca. (and related
     functions) work with empty module files, returning ‘'\n'’ (or
     reasonable equivalent) instead of raising ‘OSError’.  Patch by
     Kernc.

   - bpo-37141(62): Accept an iterable of separators in *note
     asyncio.StreamReader.readuntil(): 19a, stopping when one of them is
     encountered.

   - gh-66543(63): Make *note mimetypes.guess_type(): 1ed. properly
     parsing of URLs with only a host name, URLs containing fragment or
     query, and filenames with only a UNC sharepoint on Windows.  Based
     on patch by Dong-hee Na.

   - bpo-15010(64): *note unittest.TestLoader.discover(): f88. now saves
     the original value of ‘unittest.TestLoader._top_level_dir’ and
     restores it at the end of the call.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/117648

   (2) https://github.com/python/cpython/issues/117584

   (3) https://github.com/python/cpython/issues/117467

   (4) https://github.com/python/cpython/issues/114848

   (5) https://github.com/python/cpython/issues/117459

   (6) https://github.com/python/cpython/issues/117381

   (7) https://github.com/python/cpython/issues/117337

   (8) https://github.com/python/cpython/issues/117349

   (9) https://github.com/python/cpython/issues/117348

   (10) https://github.com/python/cpython/issues/117335

   (11) https://github.com/python/cpython/issues/66449

   (12) https://github.com/python/cpython/issues/88014

   (13) https://github.com/python/cpython/issues/117310

   (14) https://github.com/python/cpython/issues/117294

   (15) https://github.com/python/cpython/issues/98966

   (16) https://github.com/python/cpython/issues/117225

   (17) https://github.com/python/cpython/issues/117205

   (18) https://github.com/python/cpython/issues/117178

   (19) https://github.com/python/cpython/issues/114781

   (20) https://github.com/python/cpython/issues/112383

   (21) https://github.com/python/cpython/issues/117182

   (22) https://github.com/python/cpython/issues/117084

   (23) https://github.com/python/cpython/issues/117114

   (24) https://github.com/python/cpython/issues/117110

   (25) https://github.com/python/cpython/issues/109653

   (26) https://github.com/python/cpython/issues/70647

   (27) https://github.com/python/cpython/issues/116987

   (28) https://github.com/python/cpython/issues/114099

   (29) https://github.com/python/cpython/issues/90872

   (30) https://github.com/python/cpython/issues/116957

   (31) https://github.com/python/cpython/issues/115538

   (32) https://github.com/python/cpython/issues/90095

   (33) https://github.com/python/cpython/issues/106531

   (34) https://zipp.readthedocs.io/en/latest/history.html#v3-18-0

   (35) https://github.com/python/cpython/issues/63207

   (36) https://github.com/python/cpython/issues/116764

   (37) https://github.com/python/cpython/issues/116811

   (38) https://github.com/python/cpython/issues/116647

   (39) https://github.com/python/cpython/issues/113171

   (40) https://github.com/python/cpython/issues/63283

   (41) https://github.com/python/cpython/issues/71042

   (42) https://github.com/python/cpython/issues/73468

   (43) https://github.com/python/cpython/issues/116608

   (44) https://github.com/python/cpython/issues/116484

   (45) https://github.com/python/cpython/issues/114314

   (46) https://github.com/python/cpython/issues/116401

   (47) https://github.com/python/cpython/issues/71052

   (48) https://github.com/python/cpython/issues/90535

   (49) https://github.com/python/cpython/issues/113308

   (50) https://github.com/python/cpython/issues/115627

   (51) https://github.com/python/cpython/issues/114847

   (52) https://github.com/python/cpython/issues/114271

   (53) https://github.com/python/cpython/issues/113538

   (54) https://github.com/python/cpython/issues/85287

   (55) https://github.com/python/cpython/issues/113548

   (56) https://github.com/python/cpython/issues/112948

   (57) https://github.com/python/cpython/issues/105866

   (58) https://github.com/python/cpython/issues/96471

   (59) https://github.com/python/cpython/issues/89739

   (60) https://bugs.python.org/issue?@action=redirect&bpo=33533

   (61) https://bugs.python.org/issue?@action=redirect&bpo=27578

   (62) https://bugs.python.org/issue?@action=redirect&bpo=37141

   (63) https://github.com/python/cpython/issues/66543

   (64) https://bugs.python.org/issue?@action=redirect&bpo=15010


File: python.info,  Node: Documentation<3>,  Next: Tests<5>,  Prev: Library<7>,  Up: Python 3 13 0 alpha 6

1.23.8.3 Documentation
......................

   - gh-115977(1): Remove compatibility references to Emscripten.

   - gh-114099(2): Add an iOS platform guide, and flag modules not
     available on iOS.

   - gh-91565(3): Changes to documentation files and config outputs to
     reflect the new location for reporting bugs - i.e.  GitHub rather
     than bugs.python.org.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/115977

   (2) https://github.com/python/cpython/issues/114099

   (3) https://github.com/python/cpython/issues/91565


File: python.info,  Node: Tests<5>,  Next: Build<7>,  Prev: Documentation<3>,  Up: Python 3 13 0 alpha 6

1.23.8.4 Tests
..............

   - gh-83434(1): Disable JUnit XML output (‘--junit-xml=FILE’ command
     line option) in regrtest when hunting for reference leaks (‘-R’
     option).  Patch by Victor Stinner.

   - gh-117187(2): Fix XML tests for vanilla Expat <2.6.0.

   - gh-116333(3): Tests of TLS related things (error codes, etc) were
     updated to be more lenient about specific error message strings and
     behaviors as seen in the BoringSSL and AWS-LC forks of OpenSSL.

   - gh-117089(4): Consolidated tests for importlib.metadata in their
     own ‘metadata’ package.

   - gh-115979(5): Update test_importlib so that it passes under WASI
     SDK 21.

   - gh-112536(6): Add -tsan to test.regrtest for running TSAN tests in
     reasonable execution times.  Patch by Donghee Na.

   - gh-116307(7): Added import helper ‘isolated_modules’ as
     ‘CleanImport’ does not remove modules imported during the context.
     Use it in importlib.resources tests to avoid leaving ‘mod’ around
     to impede importlib.metadata tests.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/83434

   (2) https://github.com/python/cpython/issues/117187

   (3) https://github.com/python/cpython/issues/116333

   (4) https://github.com/python/cpython/issues/117089

   (5) https://github.com/python/cpython/issues/115979

   (6) https://github.com/python/cpython/issues/112536

   (7) https://github.com/python/cpython/issues/116307


File: python.info,  Node: Build<7>,  Next: Windows<4>,  Prev: Tests<5>,  Up: Python 3 13 0 alpha 6

1.23.8.5 Build
..............

   - gh-114736(1): Have WASI builds use WASI SDK 21.

   - gh-115983(2): Skip building test modules that must be built as
     shared under WASI.

   - gh-71052(3): Add Android build script and instructions.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/114736

   (2) https://github.com/python/cpython/issues/115983

   (3) https://github.com/python/cpython/issues/71052


File: python.info,  Node: Windows<4>,  Next: C API<7>,  Prev: Build<7>,  Up: Python 3 13 0 alpha 6

1.23.8.6 Windows
................

   - gh-117267(1): Ensure ‘DirEntry.stat().st_ctime’ behaves
     consistently with *note os.stat(): 448. during the deprecation
     period of ‘st_ctime’ by containing the same value as
     ‘st_birthtime’.  After the deprecation period, ‘st_ctime’ will be
     the metadata change time (or unavailable through ‘DirEntry’), and
     only ‘st_birthtime’ will contain the creation time.

   - gh-116195(2): Improves performance of *note os.getppid(): 1546. by
     using an alternate system API when available.  Contributed by
     vxiiduu.

   - gh-88494(3): On Windows, *note time.monotonic(): 238. now uses the
     ‘QueryPerformanceCounter()’ clock to have a resolution better than
     1 us, instead of the ‘GetTickCount64()’ clock which has a
     resolution of 15.6 ms.  Patch by Victor Stinner.

   - gh-116773(4): Fix instances of ‘<_overlapped.Overlapped object at
     0xXXX> still has pending operation at deallocation, the process may
     crash’.

   - gh-91227(5): Fix the asyncio ProactorEventLoop implementation so
     that sending a datagram to an address that is not listening does
     not prevent receiving any more datagrams.

   - gh-115119(6): Switched from vendored ‘libmpdecimal’ code to a
     separately-hosted external package in the ‘cpython-source-deps’
     repository when building the ‘_decimal’ module.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/117267

   (2) https://github.com/python/cpython/issues/116195

   (3) https://github.com/python/cpython/issues/88494

   (4) https://github.com/python/cpython/issues/116773

   (5) https://github.com/python/cpython/issues/91227

   (6) https://github.com/python/cpython/issues/115119


File: python.info,  Node: C API<7>,  Prev: Windows<4>,  Up: Python 3 13 0 alpha 6

1.23.8.7 C API
..............

   - gh-117642(1): Fix PEP 737(2) implementation for ‘%#T’ and ‘%#N’.

   - gh-87193(3): *note _PyBytes_Resize(): 1548. can now be called for
     bytes objects with reference count > 1, including 1-byte bytes
     objects.  It creates a new bytes object and destroys the old one if
     it has reference count > 1.

   - gh-117021(4): Fix integer overflow in ‘PyLong_AsPid()’ on
     non-Windows 64-bit platforms.

   - gh-115756(5): ‘PyCode_GetFirstFree()’ is an ustable API now and has
     been renamed to *note PyUnstable_Code_GetFirstFree(): 35e.
     (Contributed by Bogdan Romanyuk in gh-115781(6))

   - gh-116869(7): Add ‘test_cext’ test: build a C extension to check if
     the Python C API emits C compiler warnings.  Patch by Victor
     Stinner.

   - gh-116869(8): Make the C API compatible with
     ‘-Werror=declaration-after-statement’ compiler flag again.  Patch
     by Victor Stinner.

   - gh-116936(9): Add *note PyType_GetModuleByDef(): 342. to the
     limited C API. Patch by Victor Stinner.

   - gh-116809(10): Restore removed private ‘_PyErr_ChainExceptions1()’
     function.  Patch by Victor Stinner.

   - gh-115754(11): In the limited C API version 3.13, getting
     ‘Py_None’, ‘Py_False’, ‘Py_True’, ‘Py_Ellipsis’ and
     ‘Py_NotImplemented’ singletons is now implemented as function calls
     at the stable ABI level to hide implementation details.  Getting
     these constants still return borrowed references.  Patch by Victor
     Stinner.

   - gh-115754(12): Add *note Py_GetConstant(): 340. and *note
     Py_GetConstantBorrowed(): 341. functions to get constants.  For
     example, ‘Py_GetConstant(Py_CONSTANT_ZERO)’ returns a *note strong
     reference: 2ee. to the constant zero.  Patch by Victor Stinner.

   - gh-111696(13): Add support for ‘%T’, ‘%T#’, ‘%N’ and ‘%N#’ formats
     to *note PyUnicode_FromFormat(): 33f.: format the fully qualified
     name of an object type and of a type: call *note
     PyType_GetModuleName(): 33e.  See PEP 737(14) for more information.
     Patch by Victor Stinner.

   - gh-111696(15): Add *note PyType_GetModuleName(): 33e. function to
     get the type's module name.  Equivalent to getting the
     ‘type.__module__’ attribute.  Patch by Eric Snow and Victor
     Stinner.

   - gh-111696(16): Add *note PyType_GetFullyQualifiedName(): 33d.
     function to get the type's fully qualified name.  Equivalent to
     ‘f"{type.__module__}.{type.__qualname__}"’, or ‘type.__qualname__’
     if ‘type.__module__’ is not a string or is equal to ‘"builtins"’.
     Patch by Victor Stinner.

   - gh-85283(17): The ‘fcntl’, ‘grp’, ‘pwd’, ‘termios’, ‘_statistics’
     and ‘_testconsole’ C extensions are now built with the *note
     limited C API: 318.  Patch by Victor Stinner.

   - gh-111140(18): Add additional flags to *note
     PyLong_AsNativeBytes(): 33a. and *note PyLong_FromNativeBytes():
     33b. to allow the caller to determine how to handle edge cases
     around values that fill the entire buffer.

   - gh-113024(19): Add *note PyObject_GenericHash(): 32f. function.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/117642

   (2) https://peps.python.org/pep-0737/

   (3) https://github.com/python/cpython/issues/87193

   (4) https://github.com/python/cpython/issues/117021

   (5) https://github.com/python/cpython/issues/115756

   (6) https://github.com/python/cpython/issues/115781

   (7) https://github.com/python/cpython/issues/116869

   (8) https://github.com/python/cpython/issues/116869

   (9) https://github.com/python/cpython/issues/116936

   (10) https://github.com/python/cpython/issues/116809

   (11) https://github.com/python/cpython/issues/115754

   (12) https://github.com/python/cpython/issues/115754

   (13) https://github.com/python/cpython/issues/111696

   (14) https://peps.python.org/pep-0737/

   (15) https://github.com/python/cpython/issues/111696

   (16) https://github.com/python/cpython/issues/111696

   (17) https://github.com/python/cpython/issues/85283

   (18) https://github.com/python/cpython/issues/111140

   (19) https://github.com/python/cpython/issues/113024


File: python.info,  Node: Python 3 13 0 alpha 5,  Next: Python 3 13 0 alpha 4,  Prev: Python 3 13 0 alpha 6,  Up: Changelog（更動日誌）

1.23.9 Python 3.13.0 alpha 5
----------------------------

'Release date: 2024-03-12'

* Menu:

* Security: Security<5>.
* Core and Builtins: Core and Builtins<9>.
* Library: Library<8>.
* Documentation: Documentation<4>.
* Tests: Tests<6>.
* Build: Build<8>.
* Windows: Windows<5>.
* macOS: macOS<3>.
* IDLE: IDLE<7>.
* Tools/Demos: Tools/Demos<2>.
* C API: C API<8>.


File: python.info,  Node: Security<5>,  Next: Core and Builtins<9>,  Up: Python 3 13 0 alpha 5

1.23.9.1 Security
.................

   - gh-115398(1): Allow controlling Expat >=2.6.0 reparse deferral
     (CVE-2023-52425(2)) by adding five new methods:

        * *note xml.etree.ElementTree.XMLParser.flush(): 254.

        * *note xml.etree.ElementTree.XMLPullParser.flush(): 255.

        * *note xml.parsers.expat.xmlparser.GetReparseDeferralEnabled():
          256.

        * *note xml.parsers.expat.xmlparser.SetReparseDeferralEnabled():
          257.

        * ‘xml.sax.expatreader.ExpatParser.flush()’

   - gh-114572(3): *note ssl.SSLContext.cert_store_stats(): f4e. and
     *note ssl.SSLContext.get_ca_certs(): f4f. now correctly lock access
     to the certificate store, when the *note ssl.SSLContext: 276. is
     shared across multiple threads.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/115398

   (2) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-52425

   (3) https://github.com/python/cpython/issues/114572


File: python.info,  Node: Core and Builtins<9>,  Next: Library<8>,  Prev: Security<5>,  Up: Python 3 13 0 alpha 5

1.23.9.2 Core and Builtins
..........................

   - gh-116604(1): Respect the status of the garbage collector when
     indirect calls are made via *note PyErr_CheckSignals(): 40d. and
     the evaluation breaker.  Patch by Pablo Galindo

   - gh-112087(2): *note list: 5b6. is now compatible with the
     implementation of PEP 703(3).

   - gh-116381(4): Add specialization for ‘CONTAINS_OP’.

   - gh-116296(5): Fix possible refleak in ‘object.__reduce__()’
     internal error handling.

   - gh-115823(6): Properly calculate error ranges in the parser when
     raising *note SyntaxError: 173. exceptions caused by invalid byte
     sequences.  Patch by Pablo Galindo

   - gh-115778(7): Add ‘tierN’ annotation for instruction definition in
     interpreter DSL.

   - gh-115733(8): Fix crash when calling ‘next()’ on exhausted list
     iterators.

   - gh-115700(9): The regen-cases build stage now works on Windows.

   - gh-115347(10): Fix bug where docstring was replaced by a redundant
     NOP when Python is run with ‘-OO’.

   - gh-115323(11): Make error message more meaningful for when
     ‘bytearray.extend()’ is called with a *note str: 3f2. object.

   - gh-112175(12): Every ‘PyThreadState’ now has its own
     ‘eval_breaker’, allowing specific threads to be interrupted.

   - gh-115154(13): Fix a bug that was causing the *note
     tokenize.untokenize(): 154c. function to handle unicode named
     literals incorrectly.  Patch by Pablo Galindo

   - gh-112433(14): Add ability to force alignment of *note
     ctypes.Structure: 154d. by way of the new ‘_align_’ attribute on
     the class.

   - gh-104090(15): The multiprocessing resource tracker now exits with
     non-zero status code if a resource leak was detected.  It still
     exits with status code 0 otherwise.

   - gh-105858(16): Improve the constructors for *note ast: 7. nodes.
     Arguments of list types now default to an empty list if omitted,
     and optional fields default to ‘None’.  AST nodes now have an
     ‘__annotations__’ attribute with the expected types of their
     attributes.  Passing unrecognized extra arguments to AST nodes is
     deprecated and will become an error in Python 3.15.  Omitting a
     required argument to an AST node is deprecated and will become an
     error in Python 3.15.  Patch by Jelle Zijlstra.

   - gh-101860(17): Expose ‘__name__’ attribute on property.

   - gh-96497(18): Fix incorrect resolution of mangled class variables
     used in assignment expressions in comprehensions.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/116604

   (2) https://github.com/python/cpython/issues/112087

   (3) https://peps.python.org/pep-0703/

   (4) https://github.com/python/cpython/issues/116381

   (5) https://github.com/python/cpython/issues/116296

   (6) https://github.com/python/cpython/issues/115823

   (7) https://github.com/python/cpython/issues/115778

   (8) https://github.com/python/cpython/issues/115733

   (9) https://github.com/python/cpython/issues/115700

   (10) https://github.com/python/cpython/issues/115347

   (11) https://github.com/python/cpython/issues/115323

   (12) https://github.com/python/cpython/issues/112175

   (13) https://github.com/python/cpython/issues/115154

   (14) https://github.com/python/cpython/issues/112433

   (15) https://github.com/python/cpython/issues/104090

   (16) https://github.com/python/cpython/issues/105858

   (17) https://github.com/python/cpython/issues/101860

   (18) https://github.com/python/cpython/issues/96497


File: python.info,  Node: Library<8>,  Next: Documentation<4>,  Prev: Core and Builtins<9>,  Up: Python 3 13 0 alpha 5

1.23.9.3 Library
................

   - gh-116600(1): Fix *note repr(): 7a1. for global *note Flag: 5c9.
     members.

   - gh-116349(2): *note platform.java_ver(): 287. is deprecated and
     will be removed in 3.15.  It was largely untested, had a confusing
     API, and was only useful for Jython support.

   - gh-116143(3): Fix a race in pydoc ‘_start_server’, eliminating a
     window in which ‘_start_server’ can return a thread that is
     "serving" but without a ‘docserver’ set.

   - gh-116127(4): *note typing: ed.: implement PEP 705(5) which adds
     *note typing.ReadOnly: 145. support to *note typing.TypedDict: 146.

   - gh-116325(6): *note typing: ed.: raise *note SyntaxError: 173.
     instead of *note AttributeError: 2f6. on forward references as
     empty strings.

   - gh-115957(7): When ‘asyncio.TaskGroup.create_task’ is called on an
     inactive ‘asyncio.TaskGroup’, the given coroutine will be closed
     (which prevents a ‘RuntimeWarning’).

   - gh-115978(8): Disable preadv(), readv(), pwritev(), and writev() on
     WASI.

     Under wasmtime for WASI 0.2, these functions don't pass test_posix
     (‘https://github.com/bytecodealliance/wasmtime/issues/7830’).

   - gh-88352(9): Fix the computation of the next rollover time in the
     ‘logging.TimedRotatingFileHandler’ handler.  ‘computeRollover()’
     now always returns a timestamp larger than the specified time and
     works correctly during the DST change.  ‘doRollover()’ no longer
     overwrite the already rolled over file, saving from data loss when
     run at midnight or during repeated time at the DST change.

   - gh-87115(10): Set ‘__main__.__spec__’ to ‘None’ when running a
     script with *note pdb: 94.

   - gh-76511(11): Fix UnicodeEncodeError in ‘email.Message.as_string()’
     that results when a message that claims to be in the ascii
     character set actually has non-ascii characters.  Non-ascii
     characters are now replaced with the U+FFFD replacement character,
     like in the ‘replace’ error handler.

   - gh-89547(12): Add support for nested typing special forms like
     Final[ClassVar[int]].

   - gh-65824(13): Improve the ‘less’ prompt in *note pydoc: a3.

   - gh-116040(14): [Enum] fix by-value calls when second value is
     falsey; e.g.  Cardinal(1, 0)

   - gh-115821(15): [Enum] Improve error message when calling
     super().__new__() in custom __new__.

   - gh-85644(16): Use the ‘XDG_CURRENT_DESKTOP’ environment variable in
     *note webbrowser: fd. to check desktop.  Prefer it to the
     deprecated ‘GNOME_DESKTOP_SESSION_ID’ for GNOME detection.

   - gh-75988(17): Fixed *note unittest.mock.create_autospec(): 14fb. to
     pass the call through to the wrapped object to return the real
     result.

   - gh-115881(18): Fix issue where *note ast.parse(): 18e. would
     incorrectly flag conditional context managers (such as ‘with (x()
     if y else z()): ...’) as invalid syntax if ‘feature_version=(3, 8)’
     was passed.  This reverts changes to the grammar made as part of
     gh-94949(19).

   - gh-115886(20): Fix silent truncation of the name with an embedded
     null character in *note multiprocessing.shared_memory.SharedMemory:
     154f.

   - gh-115532(21): Add kernel density estimation to the statistics
     module.

   - gh-115714(22): On WASI, the *note time: d7. module no longer get
     process time using ‘times()’ or ‘CLOCK_PROCESS_CPUTIME_ID’, system
     API is that is unreliable and is likely to be removed from WASI.
     The affected clock functions fall back to calling ‘clock()’.

   - gh-115809(23): Improve algorithm for computing which rolled-over
     log files to delete in ‘logging.TimedRotatingFileHandler’.  It is
     now reliable for handlers without ‘namer’ and with arbitrary
     deterministic ‘namer’ that leaves the datetime part in the file
     name unmodified.

   - gh-74668(24): *note urllib.parse: f3. functions *note parse_qs():
     25f. and *note parse_qsl(): 25e. now support bytes arguments
     containing raw and percent-encoded non-ASCII data.

   - gh-67044(25): *note csv.writer(): 42e. now always quotes or escapes
     ‘'\r'’ and ‘'\n'’, regardless of 'lineterminator' value.

   - gh-115712(26): Restore support of space delimiter with
     ‘skipinitialspace=True’ in *note csv: 21.  *note csv.writer(): 42e.
     now quotes empty fields if delimiter is a space and
     skipinitialspace is true and raises exception if quoting is not
     possible.

   - gh-112364(27): Fixed *note ast.unparse(): 88a. to handle
     format_spec with ‘"’, ‘'’ or ‘\\’.  Patched by Frank Hoffmann.

   - gh-112997(28): Stop logging potentially sensitive callback
     arguments in *note asyncio: 8. unless debug mode is active.

   - gh-114914(29): Fix an issue where an abandoned ‘StreamWriter’ would
     not be garbage collected.

   - gh-111358(30): Fix a bug in
     ‘asyncio.BaseEventLoop.shutdown_default_executor()’ to ensure the
     timeout passed to the coroutine behaves as expected.

   - gh-115618(31): Fix improper decreasing the reference count for
     ‘None’ argument in *note property: 180. methods *note getter():
     1550, *note setter(): 1551. and *note deleter(): 1552.

   - gh-112720(32): Refactor ‘dis.ArgResolver’ to make it possible to
     subclass and change the way jump args are interpreted.

   - gh-112006(33): Fix *note inspect.unwrap(): eff. for types with the
     ‘__wrapper__’ data descriptor.  Fix *note
     inspect.Signature.from_callable(): 6de. for builtins *note
     classmethod(): 14a. and *note staticmethod(): 358.

   - gh-101293(34): Support callables with the ‘__call__()’ method and
     types with ‘__new__()’ and ‘__init__()’ methods set to class
     methods, static methods, bound methods, partial functions, and
     other types of methods and descriptors in *note
     inspect.Signature.from_callable(): 6de.

   - gh-103092(35): Isolate ‘_lsprof’ (apply PEP 687(36)).

   - gh-113942(37): *note pydoc: a3. no longer skips global functions
     implemented as builtin methods, such as ‘MethodDescriptorType’ and
     ‘WrapperDescriptorType’.

   - gh-115256(38): Added DeprecationWarning when accessing the tarfile
     attribute of TarInfo objects.  The attribute is never used
     internally and is only attached to TarInfos when the tarfile is
     opened in write-mode, not read-mode.  The attribute creates an
     unnecessary reference cycle which may cause corruption when not
     closing the handle after writing a tarfile.

   - gh-115197(39): ‘urllib.request’ no longer resolves the hostname
     before checking it against the system's proxy bypass list on macOS
     and Windows.

   - gh-113812(40): ‘DatagramTransport.sendto()’ will now send
     zero-length datagrams if called with an empty bytes object.  The
     transport flow control also now accounts for the datagram header
     when calculating the buffer size.

   - gh-114763(41): Protect modules loaded with *note
     importlib.util.LazyLoader: c54. from race conditions when multiple
     threads try to access attributes before the loading is complete.

   - gh-114709(42): ‘posixpath.commonpath()’ now raises a *note
     ValueError: 1e7. exception when passed an empty iterable.
     Previously, *note IndexError: 14a3. was raised.

     ‘posixpath.commonpath()’ now raises a *note TypeError: 4dd.
     exception when passed ‘None’.  Previously, *note ValueError: 1e7.
     was raised.

   - gh-114610(43): Fix bug where *note pathlib.PurePath.with_stem():
     1553. converted a non-empty path suffix to a stem when given an
     empty 'stem' argument.  It now raises *note ValueError: 1e7, just
     like *note pathlib.PurePath.with_suffix(): 150b. does when called
     on a path with an empty stem, given a non-empty 'suffix' argument.

   - gh-107361(44): Add *note ssl.VERIFY_X509_PARTIAL_CHAIN: 13b. and
     ‘VERIFY_X509_STRICT’ to the default SSL context created with *note
     ssl.create_default_context(): 13a.

   - gh-112281(45): Allow creating *note union of types: 766. for *note
     typing.Annotated: 8e1. with unhashable metadata.

   - gh-111775(46): Fix
     ‘importlib.resources.simple.ResourceHandle.open()’ for text mode,
     added missed ‘stream’ argument.

   - gh-90095(47): Make .pdbrc and -c work with any valid pdb commands.

   - gh-107625(48): Raise *note configparser.ParsingError: 4ab. from
     *note read(): 13d3. and *note read_file(): 4ac. methods of *note
     configparser.ConfigParser: 1aa. if a key without a corresponding
     value is continued (that is, followed by an indented line).

   - gh-107155(49): Fix incorrect output of ‘help(x)’ where ‘x’ is a
     *note lambda: 1234. function, which has an ‘__annotations__’
     dictionary attribute with a ‘"return"’ key.

   - gh-57141(50): Add option for 'non-shallow' comparisons to *note
     filecmp.dircmp: ee4. like *note filecmp.cmp(): 1554.  Original
     patch by Steven Ward.  Enhanced by Tobias Rautenkranz

   - gh-69990(51): ‘Profile.print_stats()’ has been improved to accept
     multiple sort arguments.  Patched by Chiu-Hsiang Hsu and Furkan
     Onder.

   - gh-104061(52): Add ‘socket.SO_BINDTOIFINDEX’ constant.

   - gh-60346(53): Fix ArgumentParser inconsistent with
     parse_known_args.

   - gh-102389(54): Add ‘windows_31j’ to aliases for ‘cp932’ codec

   - gh-72249(55): ‘functools.partial`s of :func:`repr()’ has been
     improved to include the *note module: 1555. name.  Patched by
     Furkan Onder and Anilyka Barry.

   - gh-100985(56): Update HTTPSConnection to consistently wrap IPv6
     Addresses when using a proxy.

   - gh-100884(57): email: fix misfolding of comma in address-lists over
     multiple lines in combination with unicode encoding.

   - gh-95782(58): Fix ‘io.BufferedReader.tell()’,
     ‘io.BufferedReader.seek()’, ‘_pyio.BufferedReader.tell()’,
     ‘io.BufferedRandom.tell()’, ‘io.BufferedRandom.seek()’ and
     ‘_pyio.BufferedRandom.tell()’ being able to return negative
     offsets.

   - gh-96310(59): Fix a traceback in *note argparse: 5. when all
     options in a mutually exclusive group are suppressed.

   - gh-93205(60): Fixed a bug in *note
     logging.handlers.TimedRotatingFileHandler: f04. where multiple
     rotating handler instances pointing to files with the same name but
     different extensions would conflict and not delete the correct
     files.

   - bpo-31116(61): Add Z85 encoding to ‘base64’.

   - bpo-44865(62): Add missing call to localization function in *note
     argparse: 5.

   - bpo-43952(63): Fix *note
     multiprocessing.connection.Listener.accept(): 1556. to accept empty
     bytes as authkey.  Not accepting empty bytes as key causes it to
     hang indefinitely.

   - bpo-42125(64): linecache: get module name from ‘__spec__’ if
     available.  This allows getting source code for the ‘__main__’
     module when a custom loader is used.

   - bpo-41122(65): Failing to pass arguments properly to *note
     functools.singledispatchmethod(): 994. now throws a TypeError
     instead of hitting an index out of bounds internally.

   - bpo-40818(66): The asyncio REPL now runs *note
     sys.__interactivehook__: f6a. on startup.  The default
     implementation of *note sys.__interactivehook__: f6a. provides
     auto-completion to the asyncio REPL. Patch contributed by Rémi
     Lapeyre.

   - bpo-33775(67): Add 'default' and 'version' help text for
     localization in argparse.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/116600

   (2) https://github.com/python/cpython/issues/116349

   (3) https://github.com/python/cpython/issues/116143

   (4) https://github.com/python/cpython/issues/116127

   (5) https://peps.python.org/pep-0705/

   (6) https://github.com/python/cpython/issues/116325

   (7) https://github.com/python/cpython/issues/115957

   (8) https://github.com/python/cpython/issues/115978

   (9) https://github.com/python/cpython/issues/88352

   (10) https://github.com/python/cpython/issues/87115

   (11) https://github.com/python/cpython/issues/76511

   (12) https://github.com/python/cpython/issues/89547

   (13) https://github.com/python/cpython/issues/65824

   (14) https://github.com/python/cpython/issues/116040

   (15) https://github.com/python/cpython/issues/115821

   (16) https://github.com/python/cpython/issues/85644

   (17) https://github.com/python/cpython/issues/75988

   (18) https://github.com/python/cpython/issues/115881

   (19) https://github.com/python/cpython/issues/94949

   (20) https://github.com/python/cpython/issues/115886

   (21) https://github.com/python/cpython/issues/115532

   (22) https://github.com/python/cpython/issues/115714

   (23) https://github.com/python/cpython/issues/115809

   (24) https://github.com/python/cpython/issues/74668

   (25) https://github.com/python/cpython/issues/67044

   (26) https://github.com/python/cpython/issues/115712

   (27) https://github.com/python/cpython/issues/112364

   (28) https://github.com/python/cpython/issues/112997

   (29) https://github.com/python/cpython/issues/114914

   (30) https://github.com/python/cpython/issues/111358

   (31) https://github.com/python/cpython/issues/115618

   (32) https://github.com/python/cpython/issues/112720

   (33) https://github.com/python/cpython/issues/112006

   (34) https://github.com/python/cpython/issues/101293

   (35) https://github.com/python/cpython/issues/103092

   (36) https://peps.python.org/pep-0687/

   (37) https://github.com/python/cpython/issues/113942

   (38) https://github.com/python/cpython/issues/115256

   (39) https://github.com/python/cpython/issues/115197

   (40) https://github.com/python/cpython/issues/113812

   (41) https://github.com/python/cpython/issues/114763

   (42) https://github.com/python/cpython/issues/114709

   (43) https://github.com/python/cpython/issues/114610

   (44) https://github.com/python/cpython/issues/107361

   (45) https://github.com/python/cpython/issues/112281

   (46) https://github.com/python/cpython/issues/111775

   (47) https://github.com/python/cpython/issues/90095

   (48) https://github.com/python/cpython/issues/107625

   (49) https://github.com/python/cpython/issues/107155

   (50) https://github.com/python/cpython/issues/57141

   (51) https://github.com/python/cpython/issues/69990

   (52) https://github.com/python/cpython/issues/104061

   (53) https://github.com/python/cpython/issues/60346

   (54) https://github.com/python/cpython/issues/102389

   (55) https://github.com/python/cpython/issues/72249

   (56) https://github.com/python/cpython/issues/100985

   (57) https://github.com/python/cpython/issues/100884

   (58) https://github.com/python/cpython/issues/95782

   (59) https://github.com/python/cpython/issues/96310

   (60) https://github.com/python/cpython/issues/93205

   (61) https://bugs.python.org/issue?@action=redirect&bpo=31116

   (62) https://bugs.python.org/issue?@action=redirect&bpo=44865

   (63) https://bugs.python.org/issue?@action=redirect&bpo=43952

   (64) https://bugs.python.org/issue?@action=redirect&bpo=42125

   (65) https://bugs.python.org/issue?@action=redirect&bpo=41122

   (66) https://bugs.python.org/issue?@action=redirect&bpo=40818

   (67) https://bugs.python.org/issue?@action=redirect&bpo=33775


File: python.info,  Node: Documentation<4>,  Next: Tests<6>,  Prev: Library<8>,  Up: Python 3 13 0 alpha 5

1.23.9.4 Documentation
......................

   - gh-115399(1): Document CVE-2023-52425(2) of Expat <2.6.0 under "XML
     vulnerabilities".

   - gh-109653(3): Improve import time of *note uuid: f8. on Linux.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/115399

   (2) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-52425

   (3) https://github.com/python/cpython/issues/109653


File: python.info,  Node: Tests<6>,  Next: Build<8>,  Prev: Documentation<4>,  Up: Python 3 13 0 alpha 5

1.23.9.5 Tests
..............

   - gh-71052(1): Add test exclusions to support running the test suite
     on Android.

   - gh-71052(2): Enable ‘test_concurrent_futures’ on platforms that
     support threading but not multiprocessing.

   - gh-115796(3): Make '_testinternalcapi.assemble_code_object'
     construct the exception table for the code object.

   - gh-115720(4): Leak tests (‘-R’, ‘--huntrleaks’) now show a summary
     of the number of leaks found in each iteration.

   - gh-115122(5): Add ‘--bisect’ option to regrtest test runner: run
     failed tests with ‘test.bisect_cmd’ to identify failing tests.
     Patch by Victor Stinner.

   - gh-115596(6): Fix ‘ProgramPriorityTests’ in ‘test_os’ permanently
     changing the process priority.

   - gh-115556(7): On Windows, commas passed in arguments to
     ‘Tools\buildbot\test.bat’ and ‘PCbuild\\rt.bat’ are now properly
     handled.

   - gh-115420(8): Fix translation of exception handler targets by
     ‘_testinternalcapi.optimize_cfg’.

   - gh-115376(9): Fix segfault in ‘_testinternalcapi.compiler_codegen’
     on bad input.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/71052

   (2) https://github.com/python/cpython/issues/71052

   (3) https://github.com/python/cpython/issues/115796

   (4) https://github.com/python/cpython/issues/115720

   (5) https://github.com/python/cpython/issues/115122

   (6) https://github.com/python/cpython/issues/115596

   (7) https://github.com/python/cpython/issues/115556

   (8) https://github.com/python/cpython/issues/115420

   (9) https://github.com/python/cpython/issues/115376


File: python.info,  Node: Build<8>,  Next: Windows<5>,  Prev: Tests<6>,  Up: Python 3 13 0 alpha 5

1.23.9.6 Build
..............

   - gh-116313(1): Get WASI builds to work under wasmtime 18 w/ WASI
     0.2/preview2 primitives.

   - gh-71052(2): Change Android's *note sys.platform: a30. from
     ‘"linux"’ to ‘"android"’.

   - gh-116117(3): Backport ‘libb2’'s PR #42 to fix compiling CPython on
     32-bit Windows with ‘clang-cl’.

   - gh-71052(4): Fix several Android build issues

   - gh-114099(5): A testbed project was added to run the test suite on
     iOS.

   - gh-115350(6): Fix building ctypes module with -DWIN32_LEAN_AND_MEAN
     defined

   - gh-111225(7): Link extension modules against libpython on Android.

   - gh-115737(8): The install name for libPython is now correctly set
     for non-framework macOS builds.

   - gh-114099(9): Makefile targets were added to support compiling an
     iOS-compatible framework build.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/116313

   (2) https://github.com/python/cpython/issues/71052

   (3) https://github.com/python/cpython/issues/116117

   (4) https://github.com/python/cpython/issues/71052

   (5) https://github.com/python/cpython/issues/114099

   (6) https://github.com/python/cpython/issues/115350

   (7) https://github.com/python/cpython/issues/111225

   (8) https://github.com/python/cpython/issues/115737

   (9) https://github.com/python/cpython/issues/114099


File: python.info,  Node: Windows<5>,  Next: macOS<3>,  Prev: Build<8>,  Up: Python 3 13 0 alpha 5

1.23.9.7 Windows
................

   - gh-116012(1): Ensure the value of ‘GetLastError()’ is preserved
     across GIL operations.

   - gh-115582(2): Building extensions intended for free-threaded builds
     of CPython now require compiling with ‘/DPy_GIL_DISABLED’ manually
     when using a regular install.  This is expected to change in future
     releases.

   - gh-115554(3): The installer now has more strict rules about
     updating the *note Python Launcher for Windows: 562.  In general,
     most users only have a single launcher installed and will see no
     difference.  When multiple launchers have been installed, the
     option to install the launcher is disabled until all but one have
     been removed.  Downgrading the launcher (which was never allowed)
     is now more obviously blocked.

   - gh-115543(4): *note Python Launcher for Windows: 562. can now
     detect Python 3.13 when installed from the Microsoft Store, and
     will install Python 3.12 by default when ‘PYLAUNCHER_ALLOW_INSTALL’
     is set.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/116012

   (2) https://github.com/python/cpython/issues/115582

   (3) https://github.com/python/cpython/issues/115554

   (4) https://github.com/python/cpython/issues/115543


File: python.info,  Node: macOS<3>,  Next: IDLE<7>,  Prev: Windows<5>,  Up: Python 3 13 0 alpha 5

1.23.9.8 macOS
..............

   - gh-116145(1): Update macOS installer to Tcl/Tk 8.6.14.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/116145


File: python.info,  Node: IDLE<7>,  Next: Tools/Demos<2>,  Prev: macOS<3>,  Up: Python 3 13 0 alpha 5

1.23.9.9 IDLE
.............

   - gh-88516(1): On macOS show a proxy icon in the title bar of editor
     windows to match platform behaviour.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/88516


File: python.info,  Node: Tools/Demos<2>,  Next: C API<8>,  Prev: IDLE<7>,  Up: Python 3 13 0 alpha 5

1.23.9.10 Tools/Demos
.....................

   - gh-100176(1): Remove outdated Tools/{io,cc,string}bench

   - bpo-45101(2): Add consistency in usage message IO between 2
     versions of python-config.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/100176

   (2) https://bugs.python.org/issue?@action=redirect&bpo=45101


File: python.info,  Node: C API<8>,  Prev: Tools/Demos<2>,  Up: Python 3 13 0 alpha 5

1.23.9.11 C API
...............

   - gh-114626(1): Add again ‘_PyCFunctionFastWithKeywords’ name,
     removed in Python 3.13 alpha 4 by mistake.  Keep the old private
     ‘_PyCFunctionFastWithKeywords’ name (Python 3.7) as an alias to the
     new public name ‘PyCFunctionFastWithKeywords’ (Python 3.13a4).
     Patch by Victor Stinner.

   - gh-111418(2): Add *note PyHASH_MODULUS: 155f, *note PyHASH_BITS:
     1560, *note PyHASH_INF: 1561. and *note PyHASH_IMAG: 1562. C
     macros.  Patch by Sergey B Kirpichev.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/114626

   (2) https://github.com/python/cpython/issues/111418


File: python.info,  Node: Python 3 13 0 alpha 4,  Next: Python 3 13 0 alpha 3,  Prev: Python 3 13 0 alpha 5,  Up: Changelog（更動日誌）

1.23.10 Python 3.13.0 alpha 4
-----------------------------

'Release date: 2024-02-15'

* Menu:

* Security: Security<6>.
* Core and Builtins: Core and Builtins<10>.
* Library: Library<9>.
* Documentation: Documentation<5>.
* Tests: Tests<7>.
* Build: Build<9>.
* Windows: Windows<6>.
* macOS: macOS<4>.
* IDLE: IDLE<8>.
* Tools/Demos: Tools/Demos<3>.
* C API: C API<9>.


File: python.info,  Node: Security<6>,  Next: Core and Builtins<10>,  Up: Python 3 13 0 alpha 4

1.23.10.1 Security
..................

   - gh-115399(1): Update bundled libexpat to 2.6.0

   - gh-115243(2): Fix possible crashes in *note
     collections.deque.index(): d78. when the deque is concurrently
     modified.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/115399

   (2) https://github.com/python/cpython/issues/115243


File: python.info,  Node: Core and Builtins<10>,  Next: Library<9>,  Prev: Security<6>,  Up: Python 3 13 0 alpha 4

1.23.10.2 Core and Builtins
...........................

   - gh-112087(1): For an empty reverse iterator for list will be
     reduced to *note reversed(): 80a.  Patch by Donghee Na

   - gh-114570(2): Add *note PythonFinalizationError: 132. exception.
     This exception derived from *note RuntimeError: 179. is raised when
     an operation is blocked during the *note Python finalization: 133.
     Patch by Victor Stinner.

   - gh-114695(3): Add *note sys._clear_internal_caches(): 1566, which
     clears all internal performance-related caches (and deprecate the
     less-general *note sys._clear_type_cache(): 1567. function).

   - gh-114828(4): Fix compilation crashes in uncommon code examples
     using *note super(): 483. inside a comprehension in a class body.

   - gh-112069(5): Adapt *note set: 57d. and *note frozenset: 57e.
     methods to Argument Clinic.

   - gh-115011(6): Setters for members with an unsigned integer type now
     support the same range of valid values for objects that has a *note
     __index__(): 6c1. method as for *note int: 23c.

   - gh-114887(7): Changed socket type validation in *note
     create_datagram_endpoint(): 6d7. to accept all non-stream sockets.
     This fixes a regression in compatibility with raw sockets.

   - gh-114944(8): Fixes a race between ‘PyParkingLot_Park’ and
     ‘_PyParkingLot_UnparkAll’.

   - gh-113462(9): Limit the number of versions that a single class can
     use.  Prevents a few wayward classes using up all the version
     numbers.

   - gh-76763(10): The *note chr(): 1568. builtin function now always
     raises *note ValueError: 1e7. for values outside the valid range.
     Previously it raised *note OverflowError: 825. for very large or
     small values.

   - gh-114806(11): No longer specialize calls to classes, if those
     classes have metaclasses.  Fixes bug where the ‘__call__’ method of
     the metaclass was not being called.

   - gh-107944(12): Improve error message for function calls with bad
     keyword arguments via getargs

   - gh-112529(13): The free-threaded build no longer allocates space
     for the ‘PyGC_Head’ structure in objects that support cyclic
     garbage collection.  A number of other fields and data structures
     are used as replacements, including ‘ob_gc_bits’, ‘ob_tid’, and
     mimalloc internal data structures.

   - gh-114456(14): Lower the recursion limit under a debug build of
     WASI.

   - gh-114083(15): Compiler applies folding of LOAD_CONST with
     following instruction in a separate pass before other
     optimisations.  This enables jump threading in certain
     circumstances.

   - gh-114388(16): Fix a *note RuntimeWarning: 1a3. emitted when assign
     an integer-like value that is not an instance of *note int: 23c. to
     an attribute that corresponds to a C struct member of *note type:
     1569. T_UINT and T_ULONG. Fix a double *note RuntimeWarning: 1a3.
     emitted when assign a negative integer value to an attribute that
     corresponds to a C struct member of type T_UINT.

   - gh-114265(17): Compiler propagates line numbers before
     optimization, leading to more optimization opportunities and
     removing the need for the ‘guarantee_lineno_for_exits’ hack.

   - gh-112529(18): The free-threaded build now has its own thread-safe
     GC implementation that uses mimalloc to find GC tracked objects.
     It is non-generational, unlike the existing GC implementation.

   - gh-114050(19): Fix segmentation fault caused by an incorrect format
     string in ‘TypeError’ exception when more than two arguments are
     passed to ‘int’.

   - gh-112354(20): The ‘END_FOR’ instruction now pops only one value.
     This is to better support side exits in loops.

   - gh-113884(21): Make *note queue.SimpleQueue: b0e. thread safe when
     the GIL is disabled.

   - gh-114058(22): Implement the foundations of the Tier 2 redundancy
     eliminator.

   - gh-113939(23): frame.clear(): Clear frame.f_locals as well, and not
     only the fast locals.  This is relevant once frame.f_locals was
     accessed, which would contain also references to all the locals.

   - gh-112050(24): Convert *note collections.deque: 580. to use
     Argument Clinic.

   - gh-112050(25): Make methods on *note collections.deque: 580.
     thread-safe when the GIL is disabled.

   - gh-113464(26): Add an option (‘--enable-experimental-jit’ for
     ‘configure’-based builds or ‘--experimental-jit’ for
     ‘PCbuild’-based ones) to build an 'experimental' just-in-time
     compiler, based on copy-and-patch(27)

   - gh-113055(28): Make interp->obmalloc a pointer.  For interpreters
     that share state with the main interpreter, this points to the same
     static memory structure.  For interpreters with their own obmalloc
     state, it is heap allocated.  Add free_obmalloc_arenas() which will
     free the obmalloc arenas and radix tree structures for interpreters
     with their own obmalloc state.

   - gh-55664(29): Add warning when creating *note type: cef. using a
     namespace dictionary with non-string keys.  Patched by Daniel Urban
     and Furkan Onder.

   - gh-104530(30): Use native Win32 condition variables.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/112087

   (2) https://github.com/python/cpython/issues/114570

   (3) https://github.com/python/cpython/issues/114695

   (4) https://github.com/python/cpython/issues/114828

   (5) https://github.com/python/cpython/issues/112069

   (6) https://github.com/python/cpython/issues/115011

   (7) https://github.com/python/cpython/issues/114887

   (8) https://github.com/python/cpython/issues/114944

   (9) https://github.com/python/cpython/issues/113462

   (10) https://github.com/python/cpython/issues/76763

   (11) https://github.com/python/cpython/issues/114806

   (12) https://github.com/python/cpython/issues/107944

   (13) https://github.com/python/cpython/issues/112529

   (14) https://github.com/python/cpython/issues/114456

   (15) https://github.com/python/cpython/issues/114083

   (16) https://github.com/python/cpython/issues/114388

   (17) https://github.com/python/cpython/issues/114265

   (18) https://github.com/python/cpython/issues/112529

   (19) https://github.com/python/cpython/issues/114050

   (20) https://github.com/python/cpython/issues/112354

   (21) https://github.com/python/cpython/issues/113884

   (22) https://github.com/python/cpython/issues/114058

   (23) https://github.com/python/cpython/issues/113939

   (24) https://github.com/python/cpython/issues/112050

   (25) https://github.com/python/cpython/issues/112050

   (26) https://github.com/python/cpython/issues/113464

   (27) https://fredrikbk.com/publications/copy-and-patch.pdf

   (28) https://github.com/python/cpython/issues/113055

   (29) https://github.com/python/cpython/issues/55664

   (30) https://github.com/python/cpython/issues/104530


File: python.info,  Node: Library<9>,  Next: Documentation<5>,  Prev: Core and Builtins<10>,  Up: Python 3 13 0 alpha 4

1.23.10.3 Library
.................

   - gh-115392(1): Fix a bug in *note doctest: 31. where incorrect line
     numbers would be reported for decorated functions.

   - gh-114563(2): Fix several *note format(): 5c3. bugs when using the
     C implementation of *note Decimal: 27c.: * memory leak in some rare
     cases when using the ‘z’ format option (coerce negative 0) *
     incorrect output when applying the ‘z’ format option to type ‘F’
     (fixed-point with capital ‘NAN’ / ‘INF’) * incorrect output when
     applying the ‘#’ format option (alternate form)

   - gh-102840(3): Fix confused traceback when floordiv, mod, or divmod
     operations happens between instances of *note fractions.Fraction:
     1c7. and *note complex: 2c9.

   - gh-115165(4): Most exceptions are now ignored when attempting to
     set the ‘__orig_class__’ attribute on objects returned when calling
     *note typing: ed. generic aliases (including generic aliases
     created using *note typing.Annotated: 8e1.).  Previously only *note
     AttributeError: 2f6. was ignored.  Patch by Dave Shawley.

   - gh-112903(5): Fix "issubclass() arg 1 must be a class" errors in
     certain cases of multiple inheritance with generic aliases
     (regression in early 3.13 alpha releases).

   - gh-115133(6): Fix tests for *note XMLPullParser: f94. with Expat
     2.6.0.

   - gh-115059(7): ‘io.BufferedRandom.read1()’ now flushes the
     underlying write buffer.

   - gh-79382(8): Trailing ‘**’ no longer allows to match files and
     non-existing paths in recursive *note glob(): 280.

   - gh-67837(9): Avoid race conditions in the creation of directories
     during concurrent extraction in *note tarfile: c8. and *note
     zipfile: 117.

   - gh-115060(10): Speed up *note pathlib.Path.glob(): 212. by removing
     redundant regex matching.

   - gh-97928(11): Partially revert the behavior of
     ‘tkinter.Text.count()’.  By default it preserves the behavior of
     older Python versions, except that setting ‘wantobjects’ to 0 no
     longer has effect.  Add a new parameter 'return_ints': specifying
     ‘return_ints=True’ makes ‘Text.count()’ always returning the single
     count as an integer instead of a 1-tuple or ‘None’.

   - gh-114628(12): When csv.Error is raised when handling TypeError, do
     not print the TypeError traceback.

   - gh-85984(13): Added ‘_POSIX_VDISABLE’ from C's ‘<unistd.h>’ to
     *note termios: ca.

   - gh-114965(14): Update bundled pip to 24.0

   - gh-114959(15): *note tarfile: c8. no longer ignores errors when
     trying to extract a directory on top of a file.

   - gh-114894(16): Add *note array.array.clear(): 188.

   - gh-114071(17): Support tuple subclasses using auto() for enum
     member value.

   - gh-109475(18): Fix support of explicit option value "-" in *note
     argparse: 5. (e.g.  ‘--option=--’).

   - gh-49766(19): Fix *note date: 1b1.-*note datetime: 1b0. comparison.
     Now the special comparison methods like ‘__eq__’ and ‘__lt__’
     return *note NotImplemented: 776. if one of comparands is ‘date’
     and other is ‘datetime’ instead of ignoring the time part and the
     time zone or forcefully return "not equal" or raise *note
     TypeError: 4dd.  It makes comparison of ‘date’ and ‘datetime’
     subclasses more symmetric and allows to change the default behavior
     by overriding the special comparison methods in subclasses.

   - gh-110190(20): Fix ctypes structs with array on Windows ARM64
     platform by setting ‘MAX_STRUCT_SIZE’ to 32 in stgdict.  Patch by
     Diego Russo

   - gh-114678(21): Ensure that deprecation warning for 'N' specifier in
     *note Decimal: 27c. format is not raised for cases where 'N'
     appears in other places in the format specifier.  Based on patch by
     Stefan Krah.

   - gh-70303(22): Return both files and directories from *note
     pathlib.Path.glob(): 212. if a pattern ends with "‘**’".
     Previously only directories were returned.

   - gh-109653(23): Improve import time of *note importlib.metadata: 6e.
     and *note email.utils: 47.

   - gh-113280(24): Fix a leak of open socket in rare cases when error
     occurred in *note ssl.SSLSocket: 88f. creation.

   - gh-77749(25): *note email.policy.EmailPolicy.fold(): 156b. now
     always encodes non-ASCII characters in headers if *note utf8: d9e.
     is false.

   - gh-83383(26): Synchronization of the *note dbm.dumb: 2a. database
     is now no-op if there was no modification since opening or last
     synchronization.  The directory file for a newly created empty
     *note dbm.dumb: 2a. database is now created immediately after
     opening instead of deferring this until synchronizing or closing.

   - gh-91602(27): Add 'filter' keyword-only parameter to *note
     sqlite3.Connection.iterdump(): 22c. for filtering database objects
     to dump.  Patch by Mariusz Felisiak.

   - gh-112451(28): Prohibit subclassing pure-Python *note
     datetime.timezone: 1059.  This is consistent with C-extension
     implementation.  Patch by Mariusz Felisiak.

   - gh-69893(29): Add the ‘close()’ method for the iterator returned by
     *note xml.etree.ElementTree.iterparse(): 258.

   - gh-109653(30): Reduce the import time of *note threading: d6.
     module by ~50%.  Patch by Daniel Hollas.

   - gh-114492(31): Make the result of *note termios.tcgetattr(): 156c.
     reproducible on Alpine Linux.  Previously it could leave a random
     garbage in some fields.

   - gh-114315(32): Make *note threading.Lock: 156d. a real class, not a
     factory function.  Add ‘__new__’ to ‘_thread.lock’ type.

   - gh-100414(33): Add *note dbm.sqlite3: 2d. as a backend to *note
     dbm: 29, and make it the new default ‘dbm’ backend.  Patch by
     Raymond Hettinger and Erlend E. Aasland.

   - gh-113267(34): Revert changes in gh-106584(35) which made calls of
     ‘TestResult’ methods ‘startTest()’ and ‘stopTest()’ unbalanced.

   - gh-75128(36): Ignore an *note OSError: 350. in
     ‘asyncio.BaseEventLoop.create_server()’ when IPv6 is available but
     the interface cannot actually support it.

   - gh-114423(37): ‘_DummyThread’ entries in ‘threading._active’ are
     now automatically removed when the related thread dies.

   - gh-114257(38): Dismiss the ‘FileNotFound’ error in *note
     ctypes.util.find_library(): cf0. and just return ‘None’ on Linux.

   - gh-114321(39): Expose more platform specific constants in the *note
     fcntl: 4f. module on Linux, macOS, FreeBSD and NetBSD.

   - gh-114328(40): The *note tty.setcbreak(): 156e. and new *note
     tty.cfmakecbreak(): 156f. no longer clears the terminal input ICRLF
     flag.  This fixes a regression introduced in 3.12 that no longer
     matched how OSes define cbreak mode in their ‘stty(1)’ manual
     pages.

   - gh-114281(41): Remove type hints from ‘Lib/asyncio/staggered.py’.
     The annotations in the typeshed(42) project should be used instead.

   - gh-101438(43): Avoid reference cycle in ElementTree.iterparse.  The
     iterator returned by ‘ElementTree.iterparse’ may hold on to a file
     descriptor.  The reference cycle prevented prompt clean-up of the
     file descriptor if the returned iterator was not exhausted.

   - gh-114198(44): The signature for the ‘__replace__’ method on *note
     dataclasses: 27. now has the first argument named ‘self’, rather
     than ‘obj’.

   - gh-104522(45): *note OSError: 350. raised when run a subprocess now
     only has 'filename' attribute set to 'cwd' if the error was caused
     by a failed attempt to change the current directory.

   - gh-114149(46): Enum: correctly handle tuple subclasses in custom
     ‘__new__’.

   - gh-83648(47): Support deprecation of options, positional arguments
     and subcommands in *note argparse: 5.

   - gh-114087(48): Speed up ‘dataclasses.asdict’ up to 1.35x.

   - gh-109534(49): Fix a reference leak in
     ‘asyncio.selector_events.BaseSelectorEventLoop’ when SSL handshakes
     fail.  Patch contributed by Jamie Phan.

   - gh-79634(50): Accept *note path-like objects: ac2. as patterns in
     *note pathlib.Path.glob(): 212. and *note rglob(): 213.

   - gh-112202(51): Ensure that a *note asyncio.Condition.notify():
     1570. call does not get lost if the awakened ‘Task’ is
     simultaneously cancelled or encounters any other error.

   - gh-113951(52): Fix the behavior of ‘tag_unbind()’ methods of
     ‘tkinter.Text’ and ‘tkinter.Canvas’ classes with three arguments.
     Previously, ‘widget.tag_unbind(tag, sequence, funcid)’ destroyed
     the current binding for 'sequence', leaving 'sequence' unbound, and
     deleted the 'funcid' command.  Now it removes only 'funcid' from
     the binding for 'sequence', keeping other commands, and deletes the
     'funcid' command.  It leaves 'sequence' unbound only if 'funcid'
     was the last bound command.

   - gh-97959(53): Fix rendering class methods, bound methods, method
     and function aliases in *note pydoc: a3.  Class methods no longer
     have "method of builtins.type instance" note.  Corresponding notes
     are now added for class and unbound methods.  Method and function
     aliases now have references to the module or the class where the
     origin was defined if it differs from the current.  Bound methods
     are now listed in the static methods section.  Methods of builtin
     classes are now supported as well as methods of Python classes.

   - gh-113796(54): Add more validation checks in the *note csv.Dialect:
     1571. constructor.  *note ValueError: 1e7. is now raised if the
     same character is used in different roles.

   - gh-113732(55): Fix support of *note QUOTE_NOTNULL: 42b. and *note
     QUOTE_STRINGS: 42c. in *note csv.reader(): 42d.

   - gh-113225(56): Speed up *note pathlib.Path.walk(): 450. by using
     *note os.DirEntry.path: 1572. where possible.

   - gh-89039(57): When replace() method is called on a subclass of
     datetime, date or time, properly call derived constructor.
     Previously, only the base class's constructor was called.

     Also, make sure to pass non-zero fold values when creating
     subclasses in various methods.  Previously, fold was silently
     ignored.

   - gh-112919(58): Speed-up *note datetime.datetime.replace(): 143a,
     *note datetime.date.replace(): 1573. and *note
     datetime.time.replace(): 1574.

   - gh-59013(59): Set breakpoint on the first executable line of the
     function, instead of the line of function definition when the user
     do ‘break func’ using *note pdb: 94.

   - gh-112343(60): Improve handling of pdb convenience variables to
     avoid replacing string contents.

   - gh-112240(61): Add option to calendar module CLI to specify the
     weekday to start each week.  Patch by Steven Ward.

   - gh-111741(62): Recognise ‘image/webp’ as a standard format in the
     *note mimetypes: 82. module.

   - gh-43457(63): Fix the *note tkinter: d9. widget method
     ‘wm_attributes()’.  It now accepts the attribute name without the
     minus prefix to get window attributes and allows to specify
     attributes and values to set as keyword arguments.  Add new
     optional keyword argument 'return_python_dict': calling
     ‘w.wm_attributes(return_python_dict=True)’ returns the attributes
     as a dict instead of a tuple.  Calling ‘w.wm_attributes()’ now
     returns a tuple instead of string if 'wantobjects' was set to 0.

   - gh-82626(64): Many functions now emit a warning if a boolean value
     is passed as a file descriptor argument.

   - gh-111051(65): Added check for file modification during debugging
     with *note pdb: 94.

   - gh-110345(66): Show the Tcl/Tk patchlevel (rather than version) in
     ‘tkinter._test()’.

   - gh-38807(67): Fix race condition in *note trace: e6.  Instead of
     checking if a directory exists and creating it, directly call *note
     os.makedirs(): 203. with the kwarg ‘exist_ok=True’.

   - gh-75705(68): Set unixfrom envelope in *note mailbox.mbox: 1575.
     and *note mailbox.MMDF: 1576.

   - gh-106233(69): Fix stacklevel in ‘InvalidTZPathWarning’ during
     *note zoneinfo: 11a. module import.

   - gh-105102(70): Allow *note ctypes.Union: 1577. to be nested in
     *note ctypes.Structure: 154d. when the system endianness is the
     opposite of the classes.

   - gh-104282(71): Fix null pointer dereference in
     ‘lzma._decode_filter_properties()’ due to improper handling of BCJ
     filters with properties of zero length.  Patch by Radislav
     Chugunov.

   - gh-96471(72): Add *note queue.Queue: 131c. termination with *note
     shutdown(): 21f.

   - gh-101599(73): Changed argparse flag options formatting to remove
     redundancy.

   - gh-85984(74): Add POSIX pseudo-terminal functions *note
     os.posix_openpt(): 1578, *note os.grantpt(): 1579, *note
     os.unlockpt(): 157a, and *note os.ptsname(): 157b.

   - gh-102512(75): When *note os.fork(): 17b. is called from a foreign
     thread (aka ‘_DummyThread’), the type of the thread in a child
     process is changed to ‘_MainThread’.  Also changed its name and
     daemonic status, it can be now joined.

   - gh-88569(76): Add *note os.path.isreserved(): 208, which identifies
     reserved pathnames such as "NUL", "AUX" and "CON". This function is
     only available on Windows.

     Deprecate *note pathlib.PurePath.is_reserved(): 286.

   - bpo-38364(77): The ‘inspect’ functions ‘isgeneratorfunction’,
     ‘iscoroutinefunction’, ‘isasyncgenfunction’ now support
     ‘functools.partialmethod’ wrapped functions the same way they
     support ‘functools.partial’.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/115392

   (2) https://github.com/python/cpython/issues/114563

   (3) https://github.com/python/cpython/issues/102840

   (4) https://github.com/python/cpython/issues/115165

   (5) https://github.com/python/cpython/issues/112903

   (6) https://github.com/python/cpython/issues/115133

   (7) https://github.com/python/cpython/issues/115059

   (8) https://github.com/python/cpython/issues/79382

   (9) https://github.com/python/cpython/issues/67837

   (10) https://github.com/python/cpython/issues/115060

   (11) https://github.com/python/cpython/issues/97928

   (12) https://github.com/python/cpython/issues/114628

   (13) https://github.com/python/cpython/issues/85984

   (14) https://github.com/python/cpython/issues/114965

   (15) https://github.com/python/cpython/issues/114959

   (16) https://github.com/python/cpython/issues/114894

   (17) https://github.com/python/cpython/issues/114071

   (18) https://github.com/python/cpython/issues/109475

   (19) https://github.com/python/cpython/issues/49766

   (20) https://github.com/python/cpython/issues/110190

   (21) https://github.com/python/cpython/issues/114678

   (22) https://github.com/python/cpython/issues/70303

   (23) https://github.com/python/cpython/issues/109653

   (24) https://github.com/python/cpython/issues/113280

   (25) https://github.com/python/cpython/issues/77749

   (26) https://github.com/python/cpython/issues/83383

   (27) https://github.com/python/cpython/issues/91602

   (28) https://github.com/python/cpython/issues/112451

   (29) https://github.com/python/cpython/issues/69893

   (30) https://github.com/python/cpython/issues/109653

   (31) https://github.com/python/cpython/issues/114492

   (32) https://github.com/python/cpython/issues/114315

   (33) https://github.com/python/cpython/issues/100414

   (34) https://github.com/python/cpython/issues/113267

   (35) https://github.com/python/cpython/issues/106584

   (36) https://github.com/python/cpython/issues/75128

   (37) https://github.com/python/cpython/issues/114423

   (38) https://github.com/python/cpython/issues/114257

   (39) https://github.com/python/cpython/issues/114321

   (40) https://github.com/python/cpython/issues/114328

   (41) https://github.com/python/cpython/issues/114281

   (42) https://github.com/python/typeshed

   (43) https://github.com/python/cpython/issues/101438

   (44) https://github.com/python/cpython/issues/114198

   (45) https://github.com/python/cpython/issues/104522

   (46) https://github.com/python/cpython/issues/114149

   (47) https://github.com/python/cpython/issues/83648

   (48) https://github.com/python/cpython/issues/114087

   (49) https://github.com/python/cpython/issues/109534

   (50) https://github.com/python/cpython/issues/79634

   (51) https://github.com/python/cpython/issues/112202

   (52) https://github.com/python/cpython/issues/113951

   (53) https://github.com/python/cpython/issues/97959

   (54) https://github.com/python/cpython/issues/113796

   (55) https://github.com/python/cpython/issues/113732

   (56) https://github.com/python/cpython/issues/113225

   (57) https://github.com/python/cpython/issues/89039

   (58) https://github.com/python/cpython/issues/112919

   (59) https://github.com/python/cpython/issues/59013

   (60) https://github.com/python/cpython/issues/112343

   (61) https://github.com/python/cpython/issues/112240

   (62) https://github.com/python/cpython/issues/111741

   (63) https://github.com/python/cpython/issues/43457

   (64) https://github.com/python/cpython/issues/82626

   (65) https://github.com/python/cpython/issues/111051

   (66) https://github.com/python/cpython/issues/110345

   (67) https://github.com/python/cpython/issues/38807

   (68) https://github.com/python/cpython/issues/75705

   (69) https://github.com/python/cpython/issues/106233

   (70) https://github.com/python/cpython/issues/105102

   (71) https://github.com/python/cpython/issues/104282

   (72) https://github.com/python/cpython/issues/96471

   (73) https://github.com/python/cpython/issues/101599

   (74) https://github.com/python/cpython/issues/85984

   (75) https://github.com/python/cpython/issues/102512

   (76) https://github.com/python/cpython/issues/88569

   (77) https://bugs.python.org/issue?@action=redirect&bpo=38364


File: python.info,  Node: Documentation<5>,  Next: Tests<7>,  Prev: Library<9>,  Up: Python 3 13 0 alpha 4

1.23.10.4 Documentation
.......................

   - gh-115233(1): Fix an example for *note LoggerAdapter: 1288. in the
     Logging Cookbook.

   - gh-114123(2): Move the *note csv: 21. module docstring to the ‘csv’
     module instead of reexporting it from the internal ‘_csv’ module,
     and remove ‘__doc__’ from ‘csv.__all__’.

     Move ‘csv.__version__’ to the ‘csv’ module instead of reexporting
     it from the internal ‘_csv’ module, and remove ‘__version__’ from
     ‘csv.__all__’.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/115233

   (2) https://github.com/python/cpython/issues/114123


File: python.info,  Node: Tests<7>,  Next: Build<9>,  Prev: Documentation<5>,  Up: Python 3 13 0 alpha 4

1.23.10.5 Tests
...............

   - gh-114099(1): Added test exclusions required to run the test suite
     on iOS.

   - gh-105089(2): Fix
     ‘test.test_zipfile.test_core.TestWithDirectory.test_create_directory_with_write’
     test in AIX by doing a bitwise AND of 0xFFFF on mode , so that it
     will be in sync with ‘zinfo.external_attr’

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/114099

   (2) https://github.com/python/cpython/issues/105089


File: python.info,  Node: Build<9>,  Next: Windows<6>,  Prev: Tests<7>,  Up: Python 3 13 0 alpha 4

1.23.10.6 Build
...............

   - gh-115167(1): Avoid vendoring ‘vcruntime140_threads.dll’ when
     building with Visual Studio 2022 version 17.8.

   - gh-113632(2): Promote WASI to a tier 2 platform and drop Emscripten
     from tier 3 in configure.ac.

   - gh-114099(3): configure and Makefile were refactored to accommodate
     framework builds on Apple platforms other than macOS.

   - gh-114875(4): Add ‘getgrent()’ as a prerequisite for building the
     *note grp: 5c. module.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/115167

   (2) https://github.com/python/cpython/issues/113632

   (3) https://github.com/python/cpython/issues/114099

   (4) https://github.com/python/cpython/issues/114875


File: python.info,  Node: Windows<6>,  Next: macOS<4>,  Prev: Build<9>,  Up: Python 3 13 0 alpha 4

1.23.10.7 Windows
.................

   - gh-115049(1): Fixes ‘py.exe’ launcher failing when run as users
     without user profiles.

   - gh-115009(2): Update Windows installer to use SQLite 3.45.1.

   - gh-109991(3): Update Windows build to use OpenSSL 3.0.13.

   - gh-111239(4): Update Windows builds to use zlib v1.3.1.

   - gh-100107(5): The ‘py.exe’ launcher will no longer attempt to run
     the Microsoft Store redirector when launching a script containing a
     ‘/usr/bin/env’ shebang

   - gh-112984(6): Adds free-threaded binaries to Windows installer as
     an optional component.

   - gh-89240(7): Allows *note multiprocessing: 86. to create pools of
     greater than 62 processes.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/115049

   (2) https://github.com/python/cpython/issues/115009

   (3) https://github.com/python/cpython/issues/109991

   (4) https://github.com/python/cpython/issues/111239

   (5) https://github.com/python/cpython/issues/100107

   (6) https://github.com/python/cpython/issues/112984

   (7) https://github.com/python/cpython/issues/89240


File: python.info,  Node: macOS<4>,  Next: IDLE<8>,  Prev: Windows<6>,  Up: Python 3 13 0 alpha 4

1.23.10.8 macOS
...............

   - gh-115009(1): Update macOS installer to use SQLite 3.45.1.

   - gh-109991(2): Update macOS installer to use OpenSSL 3.0.13.

   - gh-114490(3): Add Mach-O linkage support for *note
     platform.architecture(): 1581.

   - gh-87804(4): On macOS the result of ‘os.statvfs’ and ‘os.fstatvfs’
     now correctly report the size of very large disks, in previous
     versions the reported number of blocks was wrong for disks with at
     least 2**32 blocks.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/115009

   (2) https://github.com/python/cpython/issues/109991

   (3) https://github.com/python/cpython/issues/114490

   (4) https://github.com/python/cpython/issues/87804


File: python.info,  Node: IDLE<8>,  Next: Tools/Demos<3>,  Prev: macOS<4>,  Up: Python 3 13 0 alpha 4

1.23.10.9 IDLE
..............

   - gh-96905(1): In idlelib code, stop redefining built-ins 'dict' and
     'object'.

   - gh-103820(2): Revise IDLE bindings so that events from mouse button
     4/5 on non-X11 windowing systems (i.e.  Win32 and Aqua) are not
     mistaken for scrolling.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/96905

   (2) https://github.com/python/cpython/issues/103820


File: python.info,  Node: Tools/Demos<3>,  Next: C API<9>,  Prev: IDLE<8>,  Up: Python 3 13 0 alpha 4

1.23.10.10 Tools/Demos
......................

   - gh-113516(1): Don't set ‘LDSHARED’ when building for WASI.

   - gh-109991(2): Update GitHub CI workflows to use OpenSSL 3.0.13 and
     multissltests to use 1.1.1w, 3.0.13, 3.1.5, and 3.2.1.

   - gh-115015(3): Fix a bug in Argument Clinic that generated incorrect
     code for methods with no parameters that use the *note METH_METHOD
     | METH_FASTCALL | METH_KEYWORDS: 1584. calling convention.  Only
     the positional parameter count was checked; any keyword argument
     passed would be silently accepted.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/113516

   (2) https://github.com/python/cpython/issues/109991

   (3) https://github.com/python/cpython/issues/115015


File: python.info,  Node: C API<9>,  Prev: Tools/Demos<3>,  Up: Python 3 13 0 alpha 4

1.23.10.11 C API
................

   - gh-111140(1): Adds *note PyLong_AsNativeBytes(): 33a, *note
     PyLong_FromNativeBytes(): 33b. and *note
     PyLong_FromUnsignedNativeBytes(): 33c. functions.

   - gh-114685(2): *note PyBuffer_FillInfo(): 704. now raises a *note
     SystemError: 51b. if called with *note PyBUF_READ: 1586. or *note
     PyBUF_WRITE: 1587. as flags.  These flags should only be used with
     the ‘PyMemoryView_*’ C API.

   - gh-114685(3): *note PyObject_GetBuffer(): 369. now raises a *note
     SystemError: 51b. if called with *note PyBUF_READ: 1586. or *note
     PyBUF_WRITE: 1587. as flags.  These flags should only be used with
     the ‘PyMemoryView_*’ C API.

   - gh-114626(4): Add ‘PyCFunctionFast’ and
     ‘PyCFunctionFastWithKeywords’ typedefs (identical to the existing
     ‘_PyCFunctionFast’ and ‘_PyCFunctionFastWithKeywords’ typedefs,
     just without a leading ‘_’ prefix).

   - gh-114329(5): Add *note PyList_GetItemRef(): 312, which is similar
     to *note PyList_GetItem(): 313. but returns a *note strong
     reference: 2ee. instead of a *note borrowed reference: 2ef.

   - gh-110850(6): Add PyTime C API:

        * *note PyTime_t: 330. type.

        * *note PyTime_MIN: 331. and *note PyTime_MAX: 332. constants.

        * *note PyTime_AsSecondsDouble(): 333, *note PyTime_Monotonic():
          334, *note PyTime_PerfCounter(): 336, and *note PyTime_Time():
          338. functions.

     Patch by Victor Stinner.

   - gh-112066(7): Add *note PyDict_SetDefaultRef(): 30d.: insert a key
     and value into a dictionary if the key is not already present.
     This is similar to *note dict.setdefault(): 101a, but returns an
     integer value indicating if the key was already present.  It is
     also similar to *note PyDict_SetDefault(): 30e, but returns a
     strong reference instead of a borrowed reference.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/111140

   (2) https://github.com/python/cpython/issues/114685

   (3) https://github.com/python/cpython/issues/114685

   (4) https://github.com/python/cpython/issues/114626

   (5) https://github.com/python/cpython/issues/114329

   (6) https://github.com/python/cpython/issues/110850

   (7) https://github.com/python/cpython/issues/112066


File: python.info,  Node: Python 3 13 0 alpha 3,  Next: Python 3 13 0 alpha 2,  Prev: Python 3 13 0 alpha 4,  Up: Changelog（更動日誌）

1.23.11 Python 3.13.0 alpha 3
-----------------------------

'Release date: 2024-01-17'

* Menu:

* Security: Security<7>.
* Core and Builtins: Core and Builtins<11>.
* Library: Library<10>.
* Documentation: Documentation<6>.
* Tests: Tests<8>.
* Build: Build<10>.
* Windows: Windows<7>.
* macOS: macOS<5>.
* IDLE: IDLE<9>.
* C API: C API<10>.


File: python.info,  Node: Security<7>,  Next: Core and Builtins<11>,  Up: Python 3 13 0 alpha 3

1.23.11.1 Security
..................

   - gh-113659(1): Skip ‘.pth’ files with names starting with a dot or
     hidden file attribute.

   - gh-112302(2): Created a Software Bill-of-Materials document and
     tooling for tracking dependencies.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/113659

   (2) https://github.com/python/cpython/issues/112302


File: python.info,  Node: Core and Builtins<11>,  Next: Library<10>,  Prev: Security<7>,  Up: Python 3 13 0 alpha 3

1.23.11.2 Core and Builtins
...........................

   - gh-107901(1): Compiler duplicates basic blocks that have an eval
     breaker check, no line number, and multiple predecessors.

   - gh-107901(2): A jump leaving an exception handler back to normal
     code no longer checks the eval breaker.

   - gh-113655(3): Set the C recursion limit to 4000 on Windows, and
     10000 on Linux/OSX. This seems to be near the sweet spot to
     maintain safety, but not compromise backwards compatibility.

   - gh-113710(4): Add typed stack effects to the interpreter DSL, along
     with various instruction annotations.

   - gh-77046(5): On Windows, file descriptors wrapping Windows handles
     are now created non inheritable by default ( PEP 446(6)).  Patch by
     Zackery Spytz and Victor Stinner.

   - gh-113853(7): Guarantee that all executors make progress.  This
     then guarantees that tier 2 execution always makes progress.

   - gh-113753(8): Fix an issue where the finalizer of ‘PyAsyncGenASend’
     objects might not be called if they were allocated from a free
     list.

   - gh-107901(9): Compiler changed so that synthetic jumps which are
     not at loop end no longer check the eval breaker.

   - gh-113703(10): Fix a regression in the *note codeop: 15. module
     that was causing it to incorrectly identify incomplete f-strings.
     Patch by Pablo Galindo

   - gh-89811(11): Check for a valid ‘tp_version_tag’ before performing
     bytecode specializations that rely on this value being usable.

   - gh-111488(12): Changed error message in case of no 'in' keyword
     after 'for' in list comprehensions

   - gh-113657(13): Fix an issue that caused important instruction
     pointer updates to be optimized out of tier two traces.

   - gh-113603(14): Fixed bug where a redundant NOP is not removed,
     causing an assertion to fail in the compiler in debug mode.

   - gh-113602(15): Fix an error that was causing the parser to try to
     overwrite existing errors and crashing in the process.  Patch by
     Pablo Galindo

   - gh-113486(16): No longer issue spurious ‘PY_UNWIND’ events for
     optimized calls to classes.

   - gh-113297(17): Fix segfault in the compiler on with statement with
     19 context managers.

   - gh-113212(18): Improve *note super: 483. error messages.

   - gh-111375(19): Only use ‘NULL’ in the exception stack to indicate
     an exception was handled.  Patch by Carey Metcalfe.

   - gh-112215(20): Increase the C recursion limit by a factor of 3 for
     non-debug builds, except for webassembly and s390 platforms which
     are unchanged.  This mitigates some regressions in 3.12 with deep
     recursion mixing builtin (C) and Python code.

   - gh-113054(21): Fixed bug where a redundant NOP is not removed,
     causing an assertion to fail in the compiler in debug mode.

   - gh-106905(22): Use per AST-parser state rather than global state to
     track recursion depth within the AST parser to prevent potential
     race condition due to simultaneous parsing.

     The issue primarily showed up in 3.11 by multithreaded users of
     *note ast.parse(): 18e.  In 3.12 a change to when garbage
     collection can be triggered prevented the race condition from
     occurring.

   - gh-108866(23): Change the API and contract of ‘_PyExecutorObject’
     to return the next_instr pointer, instead of the frame, and to
     always execute at least one instruction.

   - gh-90350(24): Optimize builtin functions *note min(): eac. and
     *note max(): ead.

   - gh-112943(25): Correctly compute end column offsets for multiline
     tokens in the *note tokenize: e4. module.  Patch by Pablo Galindo

   - gh-112125(26): Fix ‘None.__ne__(None)’ returning ‘NotImplemented’
     instead of ‘False’.

   - gh-74616(27): *note input(): 126b. now raises a ValueError when
     output on the terminal if the prompt contains embedded null
     characters instead of silently truncating it.

   - gh-112716(28): Fix SystemError in the ‘import’ statement and in
     ‘__reduce__()’ methods of builtin types when ‘__builtins__’ is not
     a dict.

   - gh-112730(29): Use color to highlight error locations in
     tracebacks.  Patch by Pablo Galindo

   - gh-112625(30): Fixes a bug where a bytearray object could be
     cleared while iterating over an argument in the ‘bytearray.join()’
     method that could result in reading memory after it was freed.

   - gh-112660(31): Do not clear unexpected errors during formatting
     error messages for ImportError and AttributeError for modules.

   - gh-105967(32): Workaround a bug in Apple's macOS platform zlib
     library where *note zlib.crc32(): 158b. and *note binascii.crc32():
     158c. could produce incorrect results on multi-gigabyte inputs.
     Including when using *note zipfile: 117. on zips containing large
     data.

   - gh-95754(33): Provide a better error message when accessing invalid
     attributes on partially initialized modules.  The origin of the
     module being accessed is now included in the message to help with
     the common issue of shadowing other modules.

   - gh-112217(34): Add check for the type of ‘__cause__’ returned from
     calling the type ‘T’ in ‘raise from T’.

   - gh-111058(35): Change coro.cr_frame/gen.gi_frame to return ‘None’
     after the coroutine/generator has been closed.  This fixes a bug
     where *note getcoroutinestate(): dbf. and *note
     getgeneratorstate(): 11ce. return the wrong state for a closed
     coroutine/generator.

   - gh-112388(36): Fix an error that was causing the parser to try to
     overwrite tokenizer errors.  Patch by pablo Galindo

   - gh-112387(37): Fix error positions for decoded strings with
     backwards tokenize errors.  Patch by Pablo Galindo

   - gh-99606(38): Make code generated for an empty f-string identical
     to the code of an empty normal string.

   - gh-112367(39): Avoid undefined behaviour when using the perf
     trampolines by not freeing the code arenas until shutdown.  Patch
     by Pablo Galindo

   - gh-112320(40): The Tier 2 translator now tracks the confidence
     level for staying "on trace" (i.e.  not exiting back to the Tier 1
     interpreter) for branch instructions based on the number of bits
     set in the branch "counter".  Trace translation ends when the
     confidence drops below 1/3rd.

   - gh-109598(41): *note PyComplex_RealAsDouble(): 158d./*note
     PyComplex_ImagAsDouble(): 158e. now tries to convert an object to a
     *note complex: 2c9. instance using its ‘__complex__()’ method
     before falling back to the ‘__float__()’ method.  Patch by Sergey B
     Kirpichev.

   - gh-94606(42): Fix UnicodeEncodeError when
     ‘email.message.get_payload()’ reads a message with a Unicode
     surrogate character and the message content is not well-formed for
     surrogateescape encoding.  Patch by Sidney Markowitz.

   - bpo-21861(43): Use the object's actual class name in
     ‘_io.FileIO.__repr__()’, ‘_io._WindowsConsoleIO()’ and
     ‘_io.TextIOWrapper.__repr__()’, to make these methods subclass
     friendly.

   - bpo-45369(44): Remove LibreSSL workarounds as per PEP 644(45).

   - bpo-34392(46): Added *note sys._is_interned(): 235.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/107901

   (2) https://github.com/python/cpython/issues/107901

   (3) https://github.com/python/cpython/issues/113655

   (4) https://github.com/python/cpython/issues/113710

   (5) https://github.com/python/cpython/issues/77046

   (6) https://peps.python.org/pep-0446/

   (7) https://github.com/python/cpython/issues/113853

   (8) https://github.com/python/cpython/issues/113753

   (9) https://github.com/python/cpython/issues/107901

   (10) https://github.com/python/cpython/issues/113703

   (11) https://github.com/python/cpython/issues/89811

   (12) https://github.com/python/cpython/issues/111488

   (13) https://github.com/python/cpython/issues/113657

   (14) https://github.com/python/cpython/issues/113603

   (15) https://github.com/python/cpython/issues/113602

   (16) https://github.com/python/cpython/issues/113486

   (17) https://github.com/python/cpython/issues/113297

   (18) https://github.com/python/cpython/issues/113212

   (19) https://github.com/python/cpython/issues/111375

   (20) https://github.com/python/cpython/issues/112215

   (21) https://github.com/python/cpython/issues/113054

   (22) https://github.com/python/cpython/issues/106905

   (23) https://github.com/python/cpython/issues/108866

   (24) https://github.com/python/cpython/issues/90350

   (25) https://github.com/python/cpython/issues/112943

   (26) https://github.com/python/cpython/issues/112125

   (27) https://github.com/python/cpython/issues/74616

   (28) https://github.com/python/cpython/issues/112716

   (29) https://github.com/python/cpython/issues/112730

   (30) https://github.com/python/cpython/issues/112625

   (31) https://github.com/python/cpython/issues/112660

   (32) https://github.com/python/cpython/issues/105967

   (33) https://github.com/python/cpython/issues/95754

   (34) https://github.com/python/cpython/issues/112217

   (35) https://github.com/python/cpython/issues/111058

   (36) https://github.com/python/cpython/issues/112388

   (37) https://github.com/python/cpython/issues/112387

   (38) https://github.com/python/cpython/issues/99606

   (39) https://github.com/python/cpython/issues/112367

   (40) https://github.com/python/cpython/issues/112320

   (41) https://github.com/python/cpython/issues/109598

   (42) https://github.com/python/cpython/issues/94606

   (43) https://bugs.python.org/issue?@action=redirect&bpo=21861

   (44) https://bugs.python.org/issue?@action=redirect&bpo=45369

   (45) https://peps.python.org/pep-0644/

   (46) https://bugs.python.org/issue?@action=redirect&bpo=34392


File: python.info,  Node: Library<10>,  Next: Documentation<6>,  Prev: Core and Builtins<11>,  Up: Python 3 13 0 alpha 3

1.23.11.3 Library
.................

   - gh-114077(1): Fix possible *note OverflowError: 825. in *note
     socket.socket.sendfile(): dff. when pass 'count' larger than 2 GiB
     on 32-bit platform.

   - gh-111803(2): *note plistlib: 99. now supports loading more deeply
     nested lists in binary format.

   - gh-114014(3): Fixed a bug in *note fractions.Fraction: 1c7. where
     an invalid string using ‘d’ in the decimals part creates a
     different error compared to other invalid letters/characters.
     Patch by Jeremiah Gabriel Pascual.

   - gh-108364(4): *note sqlite3.Connection.iterdump(): 22c. now ensures
     that foreign key support is disabled before dumping the database
     schema, if there is any foreign key violation.  Patch by Erlend E.
     Aasland and Mariusz Felisiak.

   - gh-113971(5): The *note zipfile.ZipInfo: cb1. previously protected
     ‘._compresslevel’ attribute has been made public as
     ‘.compress_level’ with the old ‘_compresslevel’ name remaining
     available as a property to retain compatibility.

   - gh-113877(6): Fix *note tkinter: d9. method ‘winfo_pathname()’ on
     64-bit Windows.

   - gh-113868(7): Added *note mmap.MAP_NORESERVE: 1590, *note
     mmap.MAP_NOEXTEND: 1591, *note mmap.MAP_HASSEMAPHORE: 1592, *note
     mmap.MAP_NOCACHE: 1593, *note mmap.MAP_JIT: 1594, *note
     mmap.MAP_RESILIENT_CODESIGN: 1595, *note mmap.MAP_RESILIENT_MEDIA:
     1596, *note mmap.MAP_32BIT: 1597, *note
     mmap.MAP_TRANSLATED_ALLOW_EXECUTE: 1598, *note mmap.MAP_UNIX03:
     1599. and *note mmap.MAP_TPRO: 159a.  All of them are ‘mmap(2)’
     flags on macOS.

   - gh-113848(8): *note asyncio.TaskGroup(): 19b. and *note
     asyncio.timeout(): 5a3. context managers now handle *note
     CancelledError: 19e. subclasses as well as exact ‘CancelledError’.

   - gh-113661(9): unittest runner: Don't exit 5 if tests were skipped.
     The intention of exiting 5 was to detect issues where the test
     suite wasn't discovered at all.  If we skipped tests, it was
     correctly discovered.

   - gh-96037(10): Insert *note TimeoutError: 7d9. in the context of the
     exception that was raised during exiting an expired *note
     asyncio.timeout(): 5a3. block.

   - gh-113781(11): Silence unraisable AttributeError when warnings are
     emitted during Python finalization.

   - gh-113238(12): Add ‘Anchor’ to ‘importlib.resources’ (in order for
     the code to comply with the documentation)

   - gh-111693(13): *note asyncio.Condition.wait(): 159b. now re-raises
     the same ‘CancelledError’ instance that may have caused it to be
     interrupted.  Fixed race condition in *note
     asyncio.Semaphore.acquire(): 159c. when interrupted with a
     ‘CancelledError’.

   - gh-113791(14): Add ‘CLOCK_MONOTONIC_RAW_APPROX’ and
     ‘CLOCK_UPTIME_RAW_APPROX’ to *note time: d7. on macOS. These are
     clocks available on macOS 10.12 or later.

   - gh-112932(15): Restore the ability for *note zipfile: 117. to
     ‘extractall’ from zip files with a "/" directory entry in them as
     is commonly added to zips by some wiki or bug tracker data
     exporters.

   - gh-113568(16): Raise deprecation warnings from *note
     pathlib.PurePath: 44e. and not its private base class
     ‘PurePathBase’.

   - gh-113594(17): Fix *note UnicodeEncodeError: 61d. in *note email:
     32. when re-fold lines that contain unknown-8bit encoded part
     followed by non-unknown-8bit encoded part.

   - gh-113538(18): In ‘asyncio.StreamReaderProtocol.connection_made()’,
     there is callback that logs an error if the task wrapping the
     "connected callback" fails.  This callback would itself fail if the
     task was cancelled.  Prevent this by checking whether the task was
     cancelled first.  If so, close the transport but don't log an
     error.

   - gh-113626(19): Add support for the 'allow_code' argument in the
     *note marshal: 80. module.  Passing ‘allow_code=False’ prevents
     serialization and de-serialization of code objects which is
     incompatible between Python versions.

   - gh-85567(20): Fix resource warnings for unclosed files in *note
     pickle: 95. and *note pickletools: 96. command line interfaces.

   - gh-113537(21): Support loads ‘str’ in *note plistlib.loads(): 8f4.

   - gh-89850(22): Add default implementations of *note
     pickle.Pickler.persistent_id(): 159d. and *note
     pickle.Unpickler.persistent_load(): 159e. methods in the C
     implementation.  Calling ‘super().persistent_id()’ and
     ‘super().persistent_load()’ in subclasses of the C implementation
     of *note pickle.Pickler: 9c2. and *note pickle.Unpickler: 159f.
     classes no longer causes infinite recursion.

   - gh-113569(23): Indicate if there were no actual calls in unittest
     *note assert_has_calls(): 15a0. failure.

   - gh-101225(24): Increase the backlog for *note
     multiprocessing.connection.Listener: 15a1. objects created by
     ‘multiprocessing.manager’ and ‘multiprocessing.resource_sharer’ to
     significantly reduce the risk of getting a connection refused error
     when creating a *note multiprocessing.connection.Connection: 15a2.
     to them.

   - gh-113568(25): Raise audit events from *note pathlib.Path: 20e. and
     not its private base class ‘PathBase’.

   - gh-113543(26): Make sure that ‘webbrowser.MacOSXOSAScript’ sends
     ‘webbrowser.open’ audit event.

   - gh-113028(27): When a second reference to a string appears in the
     input to *note pickle: 95, and the Python implementation is in use,
     we are guaranteed that a single copy gets pickled and a single
     object is shared when reloaded.  Previously, in protocol 0, when a
     string contained certain characters (e.g.  newline) it resulted in
     duplicate objects.

   - gh-113421(28): Fix multiprocessing logger for ‘%(filename)s’.

   - gh-111784(29): Fix segfaults in the ‘_elementtree’ module.  Fix
     first segfault during deallocation of ‘_elementtree.XMLParser’
     instances by keeping strong reference to ‘pyexpat’ module in module
     state for capsule lifetime.  Fix second segfault which happens in
     the same deallocation process by keeping strong reference to
     ‘_elementtree’ module in ‘XMLParser’ structure for ‘_elementtree’
     module lifetime.

   - gh-113407(30): Fix import of *note unittest.mock: f0. when CPython
     is built without docstrings.

   - gh-113320(31): Fix regression in Python 3.12 where *note Protocol:
     249. classes that were not marked as *note runtime-checkable: 3e9.
     would be unnecessarily introspected, potentially causing exceptions
     to be raised if the protocol had problematic members.  Patch by
     Alex Waygood.

   - gh-53502(32): Add a new option ‘aware_datetime’ in *note plistlib:
     99. to loads or dumps aware datetime.

   - gh-113358(33): Fix rendering tracebacks with exceptions with a
     broken __getattr__

   - gh-113214(34): Fix an ‘AttributeError’ during asyncio SSL protocol
     aborts in SSL-over-SSL scenarios.

   - gh-113246(35): Update bundled pip to 23.3.2.

   - gh-87264(36): Fixed tarfile list() method to show file type.

   - gh-112182(37): ‘asyncio.futures.Future.set_exception()’ now
     transforms *note StopIteration: ba1. into *note RuntimeError: 179.
     instead of hanging or other misbehavior.  Patch contributed by
     Jamie Phan.

   - gh-113225(38): Speed up *note pathlib.Path.glob(): 212. by using
     *note os.DirEntry.path: 1572. where possible.

   - gh-113149(39): Improve error message when a JSON array or object
     contains a trailing comma.  Patch by Carson Radtke.

   - gh-113117(40): The *note subprocess: c1. module can now use the
     *note os.posix_spawn(): 205. function with ‘close_fds=True’ on
     platforms where ‘posix_spawn_file_actions_addclosefrom_np’ is
     available.  Patch by Jakub Kulik.

   - gh-113199(41): Make ‘http.client.HTTPResponse.read1’ and
     ‘http.client.HTTPResponse.readline’ close IO after reading all data
     when content length is known.  Patch by Illia Volochii.

   - gh-113191(42): Add support of *note os.fchmod(): 201. and a file
     descriptor in *note os.chmod(): 200. on Windows.

   - gh-113188(43): Fix *note shutil.copymode(): 15a3. and *note
     shutil.copystat(): 10c7. on Windows.  Previously they worked
     differently if 'dst' is a symbolic link: they modified the
     permission bits of 'dst' itself rather than the file it points to
     if 'follow_symlinks' is true or 'src' is not a symbolic link, and
     did not modify the permission bits if 'follow_symlinks' is false
     and 'src' is a symbolic link.

   - gh-113119(44): *note os.posix_spawn(): 205. now accepts ‘env=None’,
     which makes the newly spawned process use the current process
     environment.  Patch by Jakub Kulik.

   - gh-113202(45): Add a ‘strict’ option to ‘batched()’ in the
     ‘itertools’ module.

   - gh-61648(46): Detect line numbers of properties in doctests.

   - gh-113175(47): Sync with importlib_metadata 7.0, including improved
     type annotations, fixed issue with symlinked packages in
     ‘package_distributions’, added ‘EntryPoints.__repr__’, introduced
     the ‘diagnose’ script, added ‘Distribution.origin’ property, and
     removed deprecated ‘EntryPoint’ access by numeric index (tuple
     behavior).

   - gh-59616(48): Add support of *note os.lchmod(): 1ff. and the
     'follow_symlinks' argument in *note os.chmod(): 200. on Windows.
     Note that the default value of 'follow_symlinks' in ‘os.lchmod()’
     is ‘False’ on Windows.

   - gh-112559(49): *note signal.signal(): 10cd. and *note
     signal.getsignal(): 15a4. no longer call ‘repr’ on callable
     handlers.  *note asyncio.run(): 423. and *note
     asyncio.Runner.run(): 15a5. no longer call ‘repr’ on the task
     results.  Patch by Yilei Yang.

   - gh-112962(50): *note dis: 30. module functions add cache
     information to the *note Instruction: 1bd. instance rather than
     creating fake *note Instruction: 1bd. instances to represent the
     cache entries.

   - gh-112989(51): Reduce overhead to connect sockets with *note
     asyncio: 8. SelectorEventLoop.

   - gh-112970(52): Use ‘closefrom()’ on Linux where available (e.g.
     glibc-2.34), rather than only FreeBSD.

   - gh-110190(53): Fix ctypes structs with array on PPC64LE platform by
     setting ‘MAX_STRUCT_SIZE’ to 64 in stgdict.  Patch by Diego Russo.

   - gh-112540(54): The statistics.geometric_mean() function now returns
     zero for datasets containing a zero.  Formerly, it would raise an
     exception.

   - gh-87286(55): Added ‘LOG_FTP’, ‘LOG_NETINFO’, ‘LOG_REMOTEAUTH’,
     ‘LOG_INSTALL’, ‘LOG_RAS’, and ‘LOG_LAUNCHD’ tot the *note syslog:
     c6. module, all of them constants on used on macOS.

   - gh-112800(56): Fix *note asyncio: 8. ‘SubprocessTransport.close()’
     not to throw ‘PermissionError’ when used with setuid executables.

   - gh-51944(57): Add the following constants to the *note termios: ca.
     module.  These values are present in macOS system headers:
     ‘ALTWERASE’, ‘B14400’, ‘B28800’, ‘B7200’, ‘B76800’, ‘CCAR_OFLOW’,
     ‘CCTS_OFLOW’, ‘CDSR_OFLOW’, ‘CDTR_IFLOW’, ‘CIGNORE’, ‘CRTS_IFLOW’,
     ‘EXTPROC’, ‘IUTF8’, ‘MDMBUF’, ‘NL2’, ‘NL3’, ‘NOKERNINFO’, ‘ONOEOT’,
     ‘OXTABS’, ‘VDSUSP’, ‘VSTATUS’.

   - gh-79325(58): Fix an infinite recursion error in *note
     tempfile.TemporaryDirectory(): 11cc. cleanup on Windows.

   - gh-94692(59): *note shutil.rmtree(): 2d2. now only catches OSError
     exceptions.  Previously a symlink attack resistant version of
     ‘shutil.rmtree()’ could ignore or pass to the error handler
     arbitrary exception when invalid arguments were provided.

   - gh-112736(60): The use of del-safe symbols in ‘subprocess’ was
     refactored to allow for use in cross-platform build environments.

   - gh-112727(61): Speed up *note pathlib.Path.absolute(): 15a6.  Patch
     by Barney Gale.

   - gh-74690(62): Speedup *note issubclass(): 765. checks against
     simple *note runtime-checkable protocols: 3e9. by around 6%.  Patch
     by Alex Waygood.

   - gh-74690(63): Speedup *note isinstance(): 3e8. checks by roughly
     20% for *note runtime-checkable protocols: 3e9. that only have one
     callable member.  Speedup *note issubclass(): 765. checks for these
     protocols by roughly 10%.  Patch by Alex Waygood.

   - gh-112645(64): Remove deprecation error on passing ‘onerror’ to
     *note shutil.rmtree(): 2d2.

   - gh-112640(65): Add ‘kwdefaults’ parameter to *note
     types.FunctionType: 827. to set default keyword argument values.

   - gh-112622(66): Ensure ‘name’ parameter is passed to event loop in
     *note asyncio.create_task(): 5a1.

   - gh-112618(67): Fix a caching bug relating to *note
     typing.Annotated: 8e1.  ‘Annotated[str, True]’ is no longer
     identical to ‘Annotated[str, 1]’.

   - gh-112334(68): Fixed a performance regression in 3.12's *note
     subprocess: c1. on Linux where it would no longer use the fast-path
     ‘vfork()’ system call when it could have due to a logic bug,
     instead falling back to the safe but slower ‘fork()’.

     Also fixed a second 3.12.0 potential security bug.  If a value of
     ‘extra_groups=[]’ was passed to *note subprocess.Popen: 17d. or
     related APIs, the underlying ‘setgroups(0, NULL)’ system call to
     clear the groups list would not be made in the child process prior
     to ‘exec()’.

     This was identified via code inspection in the process of fixing
     the first bug.

   - gh-110190(69): Fix ctypes structs with array on Arm platform by
     setting ‘MAX_STRUCT_SIZE’ to 32 in stgdict.  Patch by Diego Russo.

   - gh-81194(70): Fix a crash in *note socket.if_indextoname(): 9d3.
     with specific value (UINT_MAX). Fix an integer overflow in *note
     socket.if_indextoname(): 9d3. on 64-bit non-Windows platforms.

   - gh-112578(71): Fix a spurious *note RuntimeWarning: 1a3. when
     executing the *note zipfile: 117. module.

   - gh-112516(72): Update the bundled copy of pip to version 23.3.1.

   - gh-112510(73): Add *note readline.backend: 15a7. for the backend
     readline uses (‘editline’ or ‘readline’)

   - gh-112328(74): [Enum] Make ‘EnumDict’, ‘EnumDict.member_names’,
     ‘EnumType._add_alias_’ and ‘EnumType._add_value_alias_’ public.

   - gh-112509(75): Fix edge cases that could cause a key to be present
     in both the ‘__required_keys__’ and ‘__optional_keys__’ attributes
     of a *note typing.TypedDict: 146.  Patch by Jelle Zijlstra.

   - gh-101336(76): Add ‘keep_alive’ keyword parameter for
     ‘AbstractEventLoop.create_server()’ and
     ‘BaseEventLoop.create_server()’.

   - gh-63284(77): Added support for TLS-PSK (pre-shared key) mode to
     the *note ssl: bb. module.

   - gh-112414(78): Fix regression in Python 3.12 where calling *note
     repr(): 7a1. on a module that had been imported using a custom
     *note loader: 15a8. could fail with *note AttributeError: 2f6.
     Patch by Alex Waygood.

   - gh-112358(79): Revert change to *note struct.Struct: 15a9.
     initialization that broke some cases of subclassing.

   - gh-112405(80): Optimize *note pathlib.PurePath.relative_to(): 2ac.
     Patch by Alex Waygood.

   - gh-94722(81): Fix bug where comparison between instances of *note
     DocTest: 15aa. fails if one of them has ‘None’ as its lineno.

   - gh-112361(82): Speed up a small handful of *note pathlib: 93.
     methods by removing some temporary objects.

   - gh-112345(83): Improve error message when trying to call *note
     issubclass(): 765. against a *note typing.Protocol: 249. that has
     non-method members.  Patch by Randolf Scholz.

   - gh-112137(84): Change *note dis: 30. output to display no-lineno as
     "-" instead of "None".

   - gh-112332(85): Deprecate the ‘exc_type’ field of *note
     traceback.TracebackException: 241.  Add ‘exc_type_str’ to replace
     it.

   - gh-81620(86): Add extra tests for *note random.binomialvariate():
     457.

   - gh-112292(87): Fix a crash in *note readline: a8. when imported
     from a sub interpreter.  Patch by Anthony Shaw

   - gh-77621(88): Slightly improve the import time of the *note
     pathlib: 93. module by deferring some imports.  Patch by Barney
     Gale.

   - gh-112137(89): Change *note dis: 30. output to display logical
     labels for jump targets instead of offsets.

   - gh-112139(90): Add ‘Signature.format()’ to format signatures to
     string with extra options.  And use it in *note pydoc: a3. to
     render more readable signatures that have new lines between
     parameters.

   - gh-112105(91): Make *note readline.set_completer_delims(): 15ab.
     work with libedit

   - gh-106922(92): Display multiple lines with ‘traceback’ when errors
     span multiple lines.

   - gh-111874(93): When creating a *note typing.NamedTuple: 291. class,
     ensure *note __set_name__(): bf5. is called on all objects that
     define ‘__set_name__’ and exist in the values of the ‘NamedTuple’
     class's class dictionary.  Patch by Alex Waygood.

   - gh-68166(94): Add support of the "vsapi" element type in *note
     tkinter.ttk.Style.element_create(): 23d.

   - gh-110275(95): Named tuple's methods ‘_replace()’ and
     ‘__replace__()’ now raise TypeError instead of ValueError for
     invalid keyword arguments.

   - gh-99367(96): Do not mangle ‘sys.path[0]’ in *note pdb: 94. if
     safe_path is set

   - gh-111615(97): Fix a regression caused by a fix to gh-93162(98)
     whereby you couldn't configure a ‘QueueHandler’ without specifying
     handlers.

   - gh-75666(99): Fix the behavior of *note tkinter: d9. widget's
     ‘unbind()’ method with two arguments.  Previously,
     ‘widget.unbind(sequence, funcid)’ destroyed the current binding for
     'sequence', leaving 'sequence' unbound, and deleted the 'funcid'
     command.  Now it removes only 'funcid' from the binding for
     'sequence', keeping other commands, and deletes the 'funcid'
     command.  It leaves 'sequence' unbound only if 'funcid' was the
     last bound command.

   - gh-67790(100): Implement basic formatting support (minimum width,
     alignment, fill) for *note fractions.Fraction: 1c7.

   - gh-111049(101): Fix crash during garbage collection of the *note
     io.BytesIO: e46. buffer object.

   - gh-102980(102): Redirect the output of ‘interact’ command of *note
     pdb: 94. to the same channel as the debugger.  Add tests and
     improve docs.

   - gh-102988(103): *note email.utils.getaddresses(): 1c4. and *note
     email.utils.parseaddr(): 1c5. now return ‘('', '')’ 2-tuples in
     more situations where invalid email addresses are encountered
     instead of potentially inaccurate values.  Add optional 'strict'
     parameter to these two functions: use ‘strict=False’ to get the old
     behavior, accept malformed inputs.  ‘getattr(email.utils,
     'supports_strict_parsing', False)’ can be use to check if the
     'strict' parameter is available.  Patch by Thomas Dwyer and Victor
     Stinner to improve the CVE-2023-27043(104) fix.

   - gh-52161(105): *note cmd.Cmd.do_help(): 15ac. now cleans docstrings
     with *note inspect.cleandoc(): 15ad. before writing them.  Patch by
     Filip Łapkiewicz.

   - gh-82300(106): Add ‘track’ parameter to *note
     multiprocessing.shared_memory.SharedMemory: 154f. that allows using
     shared memory blocks without having to register with the POSIX
     resource tracker that automatically releases them upon process
     exit.

   - gh-110109(107): Add private ‘pathlib._PurePathBase’ class: a base
     class for *note pathlib.PurePath: 44e. that omits certain magic
     methods.  It may be made public (along with ‘_PathBase’) in future.

   - gh-109858(108): Protect *note zipfile: 117. from "quoted-overlap"
     zipbomb.  It now raises BadZipFile when try to read an entry that
     overlaps with other entry or central directory.

   - gh-109786(109): Fix possible reference leaks and crash when
     re-enter the ‘__next__()’ method of *note itertools.pairwise: 7b9.

   - gh-91539(110): Small (10 - 20%) and trivial performance improvement
     of ‘urllib.request.getproxies_environment()’, typically useful when
     there are many environment variables to go over.

   - gh-103363(111): Add 'follow_symlinks' keyword-only argument to
     *note pathlib.Path.owner(): 216. and *note group(): 217, defaulting
     to ‘True’.

   - gh-102130(112): Support tab completion in *note cmd: 12. for
     ‘editline’.

   - gh-99437(113): *note runpy.run_path(): 164. now decodes path-like
     objects, making sure __file__ and sys.argv[0] of the module being
     run are always strings.

   - gh-104003(114): Add *note warnings.deprecated(): 144, a decorator
     to mark deprecated functions to static type checkers and to warn on
     usage of deprecated classes and functions.  See PEP 702(115).
     Patch by Jelle Zijlstra.

   - gh-103708(116): Make hardcoded python name, a configurable
     parameter so that different implementations of python can override
     it instead of making huge diffs in sysconfig.py

   - gh-66515(117): *note mailbox.MH: 15ae. now supports folders that do
     not contain a ‘.mh_sequences’ file (e.g.  Claws Mail IMAP-cache
     folders).  Patch by Serhiy Storchaka.

   - gh-83162(118): Renamed ‘re.error’ to ‘PatternError’ for clarity,
     and kept ‘re.error’ for backward compatibility.  Patch by Matthias
     Bussonnier and Adam Chhina.

   - gh-91133(119): Fix a bug in *note tempfile.TemporaryDirectory:
     11cc. cleanup, which now no longer dereferences symlinks when
     working around file system permission errors.

   - bpo-43153(120): On Windows, ‘tempfile.TemporaryDirectory’
     previously masked a ‘PermissionError’ with ‘NotADirectoryError’
     during directory cleanup.  It now correctly raises
     ‘PermissionError’ if errors are not ignored.  Patch by Andrei
     Kulakov and Ken Jin.

   - bpo-32731(121): *note getpass.getuser(): 351. now raises *note
     OSError: 350. for all failures rather than *note ImportError: 352.
     on systems lacking the *note pwd: a0. module or *note KeyError:
     2fb. if the password database is empty.

   - bpo-34321(122): *note mmap.mmap: 1f0. now has a 'trackfd' parameter
     on Unix; if it is ‘False’, the file descriptor specified by
     'fileno' will not be duplicated.

   - bpo-35332(123): The *note shutil.rmtree(): 2d2. function now
     ignores errors when calling *note os.close(): b18. when
     'ignore_errors' is ‘True’, and *note os.close(): b18. no longer
     retried after error.

   - bpo-35928(124): *note io.TextIOWrapper: 75f. now correctly handles
     the decoding buffer after ‘read()’ and ‘write()’.

   - bpo-26791(125): *note shutil.move(): 9ff. now moves a symlink into
     a directory when that directory is the target of the symlink.  This
     provides the same behavior as the mv shell command.  The previous
     behavior raised an exception.  Patch by Jeffrey Kintscher.

   - bpo-41422(126): Fixed memory leaks of *note pickle.Pickler: 9c2.
     and *note pickle.Unpickler: 159f. involving cyclic references via
     the internal memo mapping.

   - bpo-19821(127): The ‘pydoc.ispackage()’ function has been
     deprecated.

   - bpo-40262(128): The ‘ssl.SSLSocket.recv_into()’ method no longer
     requires the 'buffer' argument to implement ‘__len__’ and supports
     buffers with arbitrary item size.

   - bpo-39912(129): *note warnings.filterwarnings(): 1414. and *note
     warnings.simplefilter(): 666. now raise appropriate exceptions
     instead of ‘AssertionError’.  Patch contributed by Rémi Lapeyre.

   - bpo-37260(130): Fixed a race condition in *note shutil.rmtree():
     2d2. in which directory entries removed by another process or
     thread while ‘shutil.rmtree()’ is running can cause it to raise
     FileNotFoundError.  Patch by Jeffrey Kintscher.

   - bpo-36959(131): Fix some error messages for invalid ISO format
     string combinations in ‘strptime()’ that referred to directives not
     contained in the format string.  Patch by Gordon P. Hemsley.

   - bpo-18060(132): Fixed a class inheritance issue that can cause
     segfaults when deriving two or more levels of subclasses from a
     base class of Structure or Union.

   - bpo-29779(133): Add a new *note PYTHON_HISTORY: 177. environment
     variable to set the location of a ‘.python_history’ file.

   - bpo-21360(134): *note mailbox.Maildir: 353. now ignores files with
     a leading dot.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/114077

   (2) https://github.com/python/cpython/issues/111803

   (3) https://github.com/python/cpython/issues/114014

   (4) https://github.com/python/cpython/issues/108364

   (5) https://github.com/python/cpython/issues/113971

   (6) https://github.com/python/cpython/issues/113877

   (7) https://github.com/python/cpython/issues/113868

   (8) https://github.com/python/cpython/issues/113848

   (9) https://github.com/python/cpython/issues/113661

   (10) https://github.com/python/cpython/issues/96037

   (11) https://github.com/python/cpython/issues/113781

   (12) https://github.com/python/cpython/issues/113238

   (13) https://github.com/python/cpython/issues/111693

   (14) https://github.com/python/cpython/issues/113791

   (15) https://github.com/python/cpython/issues/112932

   (16) https://github.com/python/cpython/issues/113568

   (17) https://github.com/python/cpython/issues/113594

   (18) https://github.com/python/cpython/issues/113538

   (19) https://github.com/python/cpython/issues/113626

   (20) https://github.com/python/cpython/issues/85567

   (21) https://github.com/python/cpython/issues/113537

   (22) https://github.com/python/cpython/issues/89850

   (23) https://github.com/python/cpython/issues/113569

   (24) https://github.com/python/cpython/issues/101225

   (25) https://github.com/python/cpython/issues/113568

   (26) https://github.com/python/cpython/issues/113543

   (27) https://github.com/python/cpython/issues/113028

   (28) https://github.com/python/cpython/issues/113421

   (29) https://github.com/python/cpython/issues/111784

   (30) https://github.com/python/cpython/issues/113407

   (31) https://github.com/python/cpython/issues/113320

   (32) https://github.com/python/cpython/issues/53502

   (33) https://github.com/python/cpython/issues/113358

   (34) https://github.com/python/cpython/issues/113214

   (35) https://github.com/python/cpython/issues/113246

   (36) https://github.com/python/cpython/issues/87264

   (37) https://github.com/python/cpython/issues/112182

   (38) https://github.com/python/cpython/issues/113225

   (39) https://github.com/python/cpython/issues/113149

   (40) https://github.com/python/cpython/issues/113117

   (41) https://github.com/python/cpython/issues/113199

   (42) https://github.com/python/cpython/issues/113191

   (43) https://github.com/python/cpython/issues/113188

   (44) https://github.com/python/cpython/issues/113119

   (45) https://github.com/python/cpython/issues/113202

   (46) https://github.com/python/cpython/issues/61648

   (47) https://github.com/python/cpython/issues/113175

   (48) https://github.com/python/cpython/issues/59616

   (49) https://github.com/python/cpython/issues/112559

   (50) https://github.com/python/cpython/issues/112962

   (51) https://github.com/python/cpython/issues/112989

   (52) https://github.com/python/cpython/issues/112970

   (53) https://github.com/python/cpython/issues/110190

   (54) https://github.com/python/cpython/issues/112540

   (55) https://github.com/python/cpython/issues/87286

   (56) https://github.com/python/cpython/issues/112800

   (57) https://github.com/python/cpython/issues/51944

   (58) https://github.com/python/cpython/issues/79325

   (59) https://github.com/python/cpython/issues/94692

   (60) https://github.com/python/cpython/issues/112736

   (61) https://github.com/python/cpython/issues/112727

   (62) https://github.com/python/cpython/issues/74690

   (63) https://github.com/python/cpython/issues/74690

   (64) https://github.com/python/cpython/issues/112645

   (65) https://github.com/python/cpython/issues/112640

   (66) https://github.com/python/cpython/issues/112622

   (67) https://github.com/python/cpython/issues/112618

   (68) https://github.com/python/cpython/issues/112334

   (69) https://github.com/python/cpython/issues/110190

   (70) https://github.com/python/cpython/issues/81194

   (71) https://github.com/python/cpython/issues/112578

   (72) https://github.com/python/cpython/issues/112516

   (73) https://github.com/python/cpython/issues/112510

   (74) https://github.com/python/cpython/issues/112328

   (75) https://github.com/python/cpython/issues/112509

   (76) https://github.com/python/cpython/issues/101336

   (77) https://github.com/python/cpython/issues/63284

   (78) https://github.com/python/cpython/issues/112414

   (79) https://github.com/python/cpython/issues/112358

   (80) https://github.com/python/cpython/issues/112405

   (81) https://github.com/python/cpython/issues/94722

   (82) https://github.com/python/cpython/issues/112361

   (83) https://github.com/python/cpython/issues/112345

   (84) https://github.com/python/cpython/issues/112137

   (85) https://github.com/python/cpython/issues/112332

   (86) https://github.com/python/cpython/issues/81620

   (87) https://github.com/python/cpython/issues/112292

   (88) https://github.com/python/cpython/issues/77621

   (89) https://github.com/python/cpython/issues/112137

   (90) https://github.com/python/cpython/issues/112139

   (91) https://github.com/python/cpython/issues/112105

   (92) https://github.com/python/cpython/issues/106922

   (93) https://github.com/python/cpython/issues/111874

   (94) https://github.com/python/cpython/issues/68166

   (95) https://github.com/python/cpython/issues/110275

   (96) https://github.com/python/cpython/issues/99367

   (97) https://github.com/python/cpython/issues/111615

   (98) https://github.com/python/cpython/issues/93162

   (99) https://github.com/python/cpython/issues/75666

   (100) https://github.com/python/cpython/issues/67790

   (101) https://github.com/python/cpython/issues/111049

   (102) https://github.com/python/cpython/issues/102980

   (103) https://github.com/python/cpython/issues/102988

   (104) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-27043

   (105) https://github.com/python/cpython/issues/52161

   (106) https://github.com/python/cpython/issues/82300

   (107) https://github.com/python/cpython/issues/110109

   (108) https://github.com/python/cpython/issues/109858

   (109) https://github.com/python/cpython/issues/109786

   (110) https://github.com/python/cpython/issues/91539

   (111) https://github.com/python/cpython/issues/103363

   (112) https://github.com/python/cpython/issues/102130

   (113) https://github.com/python/cpython/issues/99437

   (114) https://github.com/python/cpython/issues/104003

   (115) https://peps.python.org/pep-0702/

   (116) https://github.com/python/cpython/issues/103708

   (117) https://github.com/python/cpython/issues/66515

   (118) https://github.com/python/cpython/issues/83162

   (119) https://github.com/python/cpython/issues/91133

   (120) https://bugs.python.org/issue?@action=redirect&bpo=43153

   (121) https://bugs.python.org/issue?@action=redirect&bpo=32731

   (122) https://bugs.python.org/issue?@action=redirect&bpo=34321

   (123) https://bugs.python.org/issue?@action=redirect&bpo=35332

   (124) https://bugs.python.org/issue?@action=redirect&bpo=35928

   (125) https://bugs.python.org/issue?@action=redirect&bpo=26791

   (126) https://bugs.python.org/issue?@action=redirect&bpo=41422

   (127) https://bugs.python.org/issue?@action=redirect&bpo=19821

   (128) https://bugs.python.org/issue?@action=redirect&bpo=40262

   (129) https://bugs.python.org/issue?@action=redirect&bpo=39912

   (130) https://bugs.python.org/issue?@action=redirect&bpo=37260

   (131) https://bugs.python.org/issue?@action=redirect&bpo=36959

   (132) https://bugs.python.org/issue?@action=redirect&bpo=18060

   (133) https://bugs.python.org/issue?@action=redirect&bpo=29779

   (134) https://bugs.python.org/issue?@action=redirect&bpo=21360


File: python.info,  Node: Documentation<6>,  Next: Tests<8>,  Prev: Library<10>,  Up: Python 3 13 0 alpha 3

1.23.11.4 Documentation
.......................

   - gh-111699(1): Relocate ‘smtpd’ deprecation notice to its own
     section rather than under ‘locale’ in What's New in Python 3.12
     document

   - gh-110746(2): Improved markup for valid options/values for methods
     ttk.treeview.column and ttk.treeview.heading, and for Layouts.

   - gh-95649(3): Document that the *note asyncio: 8. module contains
     code taken from v0.16.0 of the uvloop project(4), as well as the
     required MIT licensing information.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/111699

   (2) https://github.com/python/cpython/issues/110746

   (3) https://github.com/python/cpython/issues/95649

   (4) https://github.com/MagicStack/uvloop/tree/v0.16.0


File: python.info,  Node: Tests<8>,  Next: Build<10>,  Prev: Documentation<6>,  Up: Python 3 13 0 alpha 3

1.23.11.5 Tests
...............

   - gh-111798(1): Disable ‘test_super_deep()’ from ‘test_call’ under
     pydebug builds on WASI; the stack depth is too small to make the
     test useful.

   - gh-111801(2): Lower the recursion limit in ‘test_isinstance’ for
     ‘test_infinitely_many_bases()’.  This prevents a stack overflow on
     a pydebug build of WASI.

   - gh-111802(3): Specify a low recursion depth for
     ‘test_bad_getattr()’ in ‘test.pickletester’ to avoid exhausting the
     stack under a pydebug build for WASI.

   - gh-44626(4): Fix *note os.path.isabs(): 209. incorrectly returning
     ‘True’ when given a path that starts with exactly one (back)slash
     on Windows.

     Fix ‘pathlib.PureWindowsPath.is_absolute()’ incorrectly returning
     ‘False’ for some paths beginning with two (back)slashes.

   - gh-113633(5): Use module state for the _testcapi extension module.

   - gh-109980(6): Fix ‘test_tarfile_vs_tar’ in ‘test_shutil’ for macOS,
     where system tar can include more information in the archive than
     *note shutil.make_archive: 45a.

   - gh-112769(7): The tests now correctly compare zlib version when
     *note zlib.ZLIB_RUNTIME_VERSION: 1107. contains non-integer
     suffixes.  For example zlib-ng defines the version as
     ‘1.3.0.zlib-ng’.

   - gh-112334(8): Adds a regression test to verify that ‘vfork()’ is
     used when expected by *note subprocess: c1. on vfork enabled POSIX
     systems (Linux).

   - gh-108927(9): Fixed order dependence in running tests in the same
     process when a test that has submodules (e.g.  test_importlib)
     follows a test that imports its submodule (e.g.
     test_importlib.util) and precedes a test (e.g.  test_unittest or
     test_compileall) that uses that submodule.

   - bpo-40648(10): Test modes that file can get with chmod() on
     Windows.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/111798

   (2) https://github.com/python/cpython/issues/111801

   (3) https://github.com/python/cpython/issues/111802

   (4) https://github.com/python/cpython/issues/44626

   (5) https://github.com/python/cpython/issues/113633

   (6) https://github.com/python/cpython/issues/109980

   (7) https://github.com/python/cpython/issues/112769

   (8) https://github.com/python/cpython/issues/112334

   (9) https://github.com/python/cpython/issues/108927

   (10) https://bugs.python.org/issue?@action=redirect&bpo=40648


File: python.info,  Node: Build<10>,  Next: Windows<7>,  Prev: Tests<8>,  Up: Python 3 13 0 alpha 3

1.23.11.6 Build
...............

   - gh-114013(1): Fix ‘Tools/wasm/wasi.py’ to not include the path to
     ‘python.wasm’ as part of ‘HOSTRUNNER’.  The environment variable is
     meant to specify how to run the WASI host only, having
     ‘python.wasm’ and relevant flags appended to the ‘HOSTRUNNER’.
     This fixes ‘make test’ work.

   - gh-113258(2): Changed the Windows build to write out generated
     frozen modules into the build tree instead of the source tree.

   - gh-112305(3): Fixed the ‘check-clean-src’ step performed on out of
     tree builds to detect errant ‘$(srcdir)/Python/frozen_modules/*.h’
     files and recommend appropriate source tree cleanup steps to get a
     working build again.

   - gh-112536(4): Add support for thread sanitizer (TSAN)

   - gh-112867(5): Fix the build for the case that
     WITH_PYMALLOC_RADIX_TREE=0 set.

   - gh-103065(6): Introduce ‘Tools/wasm/wasi.py’ to simplify doing a
     WASI build.

   - bpo-11102(7): The *note os.major(): 150e, *note os.makedev(): 1510,
     and *note os.minor(): 150f. functions are now available on HP-UX
     v3.

   - bpo-36351(8): Do not set ipv6type when cross-compiling.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/114013

   (2) https://github.com/python/cpython/issues/113258

   (3) https://github.com/python/cpython/issues/112305

   (4) https://github.com/python/cpython/issues/112536

   (5) https://github.com/python/cpython/issues/112867

   (6) https://github.com/python/cpython/issues/103065

   (7) https://bugs.python.org/issue?@action=redirect&bpo=11102

   (8) https://bugs.python.org/issue?@action=redirect&bpo=36351


File: python.info,  Node: Windows<7>,  Next: macOS<5>,  Prev: Build<10>,  Up: Python 3 13 0 alpha 3

1.23.11.7 Windows
.................

   - gh-114096(1): Process privileges that are activated for creating
     directory junctions are now restored afterwards, avoiding behaviour
     changes in other parts of the program.

   - gh-111877(2): *note os.stat(): 448. calls were returning incorrect
     time values for files that could not be accessed directly.

   - gh-111973(3): Update Windows installer to use SQLite 3.44.2.

   - gh-113009(4): *note multiprocessing: 86.: On Windows, fix a race
     condition in ‘Process.terminate()’: no longer set the ‘returncode’
     attribute to always call ‘WaitForSingleObject()’ in
     ‘Process.wait()’.  Previously, sometimes the process was still
     running after ‘TerminateProcess()’ even if ‘GetExitCodeProcess()’
     is not ‘STILL_ACTIVE’.  Patch by Victor Stinner.

   - gh-86179(5): Fixes path calculations when launching Python on
     Windows through a symlink.

   - gh-71383(6): Update Tcl/Tk in Windows installer to 8.6.13 with a
     patch to suppress incorrect ThemeChanged warnings.

   - gh-111650(7): Ensures the ‘Py_GIL_DISABLED’ preprocessor variable
     is defined in ‘pyconfig.h’ so that extension modules written in C
     are able to use it.

   - gh-112278(8): Reduce the time cost for some functions in *note
     platform: 98. on Windows if current user has no permission to the
     WMI.

   - gh-73427(9): Deprecate *note sys._enablelegacywindowsfsencoding():
     28e.  Use *note PYTHONLEGACYWINDOWSFSENCODING: 28f. instead.  Patch
     by Inada Naoki.

   - gh-87868(10): Correctly sort and remove duplicate environment
     variables in ‘_winapi.CreateProcess()’.

   - bpo-37308(11): Fix mojibake in *note mmap.mmap: 1f0. when using a
     non-ASCII 'tagname' argument on Windows.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/114096

   (2) https://github.com/python/cpython/issues/111877

   (3) https://github.com/python/cpython/issues/111973

   (4) https://github.com/python/cpython/issues/113009

   (5) https://github.com/python/cpython/issues/86179

   (6) https://github.com/python/cpython/issues/71383

   (7) https://github.com/python/cpython/issues/111650

   (8) https://github.com/python/cpython/issues/112278

   (9) https://github.com/python/cpython/issues/73427

   (10) https://github.com/python/cpython/issues/87868

   (11) https://bugs.python.org/issue?@action=redirect&bpo=37308


File: python.info,  Node: macOS<5>,  Next: IDLE<9>,  Prev: Windows<7>,  Up: Python 3 13 0 alpha 3

1.23.11.8 macOS
...............

   - gh-113666(1): Add the following constants to module *note stat:
     bc.: ‘UF_SETTABLE’, ‘UF_TRACKED’, ‘UF_DATAVAULT’, ‘SF_SUPPORTED’,
     ‘SF_SETTABLE’, ‘SF_SYNTHETIC’, ‘SF_RESTRICTED’, ‘SF_FIRMLINK’ and
     ‘SF_DATALESS’.  The values ‘UF_SETTABLE’, ‘SF_SUPPORTED’,
     ‘SF_SETTABLE’ and ‘SF_SYNTHETIC’ are only available on macOS.

   - gh-113536(2): *note os.waitid(): d3f. is now available on macOS

   - gh-110459(3): Running ‘configure ... --with-openssl-rpath=X/Y/Z’ no
     longer fails to detect OpenSSL on macOS.

   - gh-74573(4): Document that *note dbm.ndbm: 2c. can silently corrupt
     DBM files on updates when exceeding undocumented platform limits,
     and can crash (segmentation fault) when reading such a corrupted
     file.  (FB8919203)

   - gh-65701(5): The ‘freeze’ tool doesn't work with framework builds
     of Python.  Document this and bail out early when running the tool
     with such a build.

   - gh-87277(6): webbrowser: Don't look for X11 browsers on macOS.
     Those are generally not used and probing for them can result in
     starting XQuartz even if it isn't used otherwise.

   - gh-111973(7): Update macOS installer to use SQLite 3.44.2.

   - gh-108269(8): Set ‘CFBundleAllowMixedLocalizations’ to true in the
     Info.plist for the framework, embedded Python.app and IDLE.app with
     framework installs on macOS. This allows applications to pick up
     the user's preferred locale when that's different from english.

   - gh-102362(9): Make sure the result of ‘sysconfig.get_plaform()’
     includes at least a major and minor versions, even if
     ‘MACOSX_DEPLOYMENT_TARGET’ is set to only a major version during
     build to match the format expected by pip.

   - gh-110017(10): Disable a signal handling stress test on macOS due
     to a bug in macOS (FB13453490).

   - gh-110820(11): Make sure the preprocessor definitions for
     ‘ALIGNOF_MAX_ALIGN_T’, ‘SIZEOF_LONG_DOUBLE’ and
     ‘HAVE_GCC_ASM_FOR_X64’ are correct for Universal 2 builds on macOS.

   - gh-109981(12): Use ‘/dev/fd’ on macOS to determine the number of
     open files in ‘test.support.os_helper.fd_count’ to avoid a crash
     with "guarded" file descriptors when probing for open files.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/113666

   (2) https://github.com/python/cpython/issues/113536

   (3) https://github.com/python/cpython/issues/110459

   (4) https://github.com/python/cpython/issues/74573

   (5) https://github.com/python/cpython/issues/65701

   (6) https://github.com/python/cpython/issues/87277

   (7) https://github.com/python/cpython/issues/111973

   (8) https://github.com/python/cpython/issues/108269

   (9) https://github.com/python/cpython/issues/102362

   (10) https://github.com/python/cpython/issues/110017

   (11) https://github.com/python/cpython/issues/110820

   (12) https://github.com/python/cpython/issues/109981


File: python.info,  Node: IDLE<9>,  Next: C API<10>,  Prev: macOS<5>,  Up: Python 3 13 0 alpha 3

1.23.11.9 IDLE
..............

   - gh-72284(1): Improve the lists of features, editor key bindings,
     and shell key bingings in the IDLE doc.

   - gh-113903(2): Fix rare failure of test.test_idle, in
     test_configdialog.

   - gh-113729(3): Fix the "Help -> IDLE Doc" menu bug in 3.11.7 and
     3.12.1.

   - gh-113269(4): Fix test_editor hang on macOS Catalina.

   - gh-112898(5): Fix processing unsaved files when quitting IDLE on
     macOS.

   - bpo-13586(6): Enter the selected text when opening the "Replace"
     dialog.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/72284

   (2) https://github.com/python/cpython/issues/113903

   (3) https://github.com/python/cpython/issues/113729

   (4) https://github.com/python/cpython/issues/113269

   (5) https://github.com/python/cpython/issues/112898

   (6) https://bugs.python.org/issue?@action=redirect&bpo=13586


File: python.info,  Node: C API<10>,  Prev: IDLE<9>,  Up: Python 3 13 0 alpha 3

1.23.11.10 C API
................

   - gh-106560(1): Fix redundant declarations in the public C API.
     Declare PyBool_Type, PyLong_Type and PySys_Audit() only once.
     Patch by Victor Stinner.

   - gh-112438(2): Fix support of format units "es", "et", "es#", and
     "et#" in nested tuples in *note PyArg_ParseTuple(): 517.-like
     functions.

   - gh-111545(3): Add *note Py_HashPointer(): 32e. function to hash a
     pointer.  Patch by Victor Stinner.

   - gh-65210(4): Change the declaration of the 'keywords' parameter of
     *note PyArg_ParseTupleAndKeywords(): 2e9. and *note
     PyArg_VaParseTupleAndKeywords(): 2ea. for better compatibility with
     C++.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/106560

   (2) https://github.com/python/cpython/issues/112438

   (3) https://github.com/python/cpython/issues/111545

   (4) https://github.com/python/cpython/issues/65210


File: python.info,  Node: Python 3 13 0 alpha 2,  Next: Python 3 13 0 alpha 1,  Prev: Python 3 13 0 alpha 3,  Up: Changelog（更動日誌）

1.23.12 Python 3.13.0 alpha 2
-----------------------------

'Release date: 2023-11-22'

* Menu:

* Core and Builtins: Core and Builtins<12>.
* Library: Library<11>.
* Tests: Tests<9>.
* Build: Build<11>.
* Windows: Windows<8>.
* macOS: macOS<6>.
* IDLE: IDLE<10>.
* Tools/Demos: Tools/Demos<4>.
* C API: C API<11>.


File: python.info,  Node: Core and Builtins<12>,  Next: Library<11>,  Up: Python 3 13 0 alpha 2

1.23.12.1 Core and Builtins
...........................

   - gh-112243(1): Don't include comments in f-string debug expressions.
     Patch by Pablo Galindo

   - gh-112287(2): Slightly optimize the Tier 2 (uop) interpreter by
     only loading ‘oparg’ and ‘operand’ when needed.  Also double the
     trace size limit again, to 512 this time.

   - gh-112266(3): Change docstrings of *note __dict__: c04. and
     ‘__weakref__’.

   - gh-111807(4): Lower the max parser stack depth to 1000 under WASI
     debug builds.

   - gh-111798(5): When Python is built in debug mode, set the C
     recursion limit to 500 instead of 1500.  A debug build is likely
     built with low optimization level which implies higher stack memory
     usage than a release build.  Patch by Victor Stinner.

   - gh-106529(6): Enable translating unspecialized ‘FOR_ITER’ to Tier
     2.

   - gh-111916(7): Make hashlib related modules thread-safe without the
     GIL

   - gh-81137(8): Deprecate assignment to a function's ‘__code__’ field
     when the new code object is of a mismatched type (e.g., from a
     generator to a plain function).

   - gh-79932(9): Raise exception if *note frame.clear(): 27f. is called
     on a suspended frame.

   - gh-81925(10): Implement native thread ids for GNU KFreeBSD.

   - gh-111843(11): Use exponential backoff to reduce the number of
     failed tier 2 optimization attempts by over 99%.

   - gh-110829(12): Joining a thread now ensures the underlying OS
     thread has exited.  This is required for safer fork() in
     multi-threaded processes.

   - gh-109369(13): Make sure that tier 2 traces are de-optimized if the
     code is instrumented

   - gh-111772(14): Specialize slot loads and stores for _Py_T_OBJECT as
     well as Py_T_OBJECT_EX

   - gh-111666(15): Speed up *note BaseExceptionGroup.derive(): 15b8,
     *note BaseExceptionGroup.subgroup(): 15b9, and *note
     BaseExceptionGroup.split(): 15ba. by changing how they parse passed
     arguments.

   - gh-111654(16): Fix runtime crash when some error happens in opcode
     ‘LOAD_FROM_DICT_OR_DEREF’.

   - gh-111623(17): Add support for sharing tuples between interpreters
     using the cross-interpreter API. Patch by Anthony Shaw.

   - gh-111354(18): The oparg of *note YIELD_VALUE: 15bb. is now ‘1’ if
     the instruction is part of a yield-from or await, and ‘0’
     otherwise.

     The SUSPENDED frame state is now split into ‘SUSPENDED’ and
     ‘SUSPENDED_YIELD_FROM’.  This simplifies the code in ‘_PyGen_yf’.

   - gh-111520(19): Merge the Tier 1 (bytecode) and Tier 2 (micro-ops)
     interpreters together, moving the Tier 2 interpreter loop and
     switch into ‘_PyEval_EvalFrameDefault()’ in ‘Python/ceval.c’.  The
     ‘Python/executor.c’ file is gone.  Also the ‘TIER_ONE’ and
     ‘TIER_TWO’ macros are now handled by the code generator.

     'Beware!'  This changes the environment variables to enable
     micro-ops and their debugging to ‘PYTHON_UOPS’ and
     ‘PYTHON_LLTRACE’.

   - gh-109181(20): Speed up ‘Traceback’ object creation by lazily
     compute the line number.  Patch by Pablo Galindo

   - gh-111420(21): Allow type comments in parenthesized ‘with’
     statements

   - gh-111438(22): Add support for sharing floats between interpreters
     using the cross-interpreter API. Patch by Anthony Shaw.

   - gh-111435(23): Add support for sharing of ‘True’ and ‘False’
     between interpreters using the cross-interpreter API. Patch by
     Anthony Shaw.

   - gh-102388(24): Fix a bug where ‘iso2022_jp_3’ and ‘iso2022_jp_2004’
     codecs read out of bounds

   - gh-111366(25): Fix an issue in the *note codeop: 15. that was
     causing *note SyntaxError: 173. exceptions raised in the presence
     of invalid syntax to not contain precise error messages.  Patch by
     Pablo Galindo

   - gh-111380(26): Fix a bug that was causing *note SyntaxWarning: 40c.
     to appear twice when parsing if invalid syntax is encountered
     later.  Patch by Pablo galindo

   - gh-111374(27): Added a new environment variable *note
     PYTHON_FROZEN_MODULES: 174.  It determines whether or not frozen
     modules are ignored by the import machinery, equivalent of the
     *note -X frozen_modules: 15a. command-line option.

   - gh-111354(28): Remove ‘oparg’ from *note YIELD_VALUE: 15bb.  Change
     ‘oparg’ of *note RESUME: 6a7. to include information about the
     except-depth.  These changes make it possible to simplify the code
     in generator close.

   - gh-94438(29): Fix a regression that prevented jumping across ‘is
     None’ and ‘is not None’ when debugging.  Patch by Savannah
     Ostrowski.

   - gh-67224(30): Show source lines in tracebacks when using the ‘-c’
     option when running Python.  Patch by Pablo Galindo

   - gh-111123(31): Fix a bug where a *note global: 170. declaration in
     an *note except: 171. block is rejected when the global is used in
     the *note else: 172. block.

   - gh-110938(32): Fix error messages for indented blocks with
     functions and classes with generic type parameters.  Patch by Pablo
     Galindo

   - gh-109214(33): Remove unnecessary instruction pointer updates
     before returning from frames.

   - gh-110912(34): Correctly display the traceback for *note
     MemoryError: 15bc. exceptions using the *note traceback: e7.
     module.  Patch by Pablo Galindo

   - gh-109894(35): Fixed crash due to improperly initialized static
     *note MemoryError: 15bc. in subinterpreter.

   - gh-110892(36): Return ‘NULL’ for ‘PyTrace_RETURN’ events caused by
     an exception

   - gh-110864(37): Fix argument parsing by
     ‘_PyArg_UnpackKeywordsWithVararg’ for functions defining
     pos-or-keyword, vararg, and kw-only parameters.

   - gh-109094(38): Replace ‘prev_instr’ on the interpreter frame by
     ‘instr_ptr’ which points to the beginning of the instruction that
     is currently executing (or will execute once the frame resumes).

   - gh-110805(39): Allow the repl to show source code and complete
     tracebacks.  Patch by Pablo Galindo

   - gh-110722(40): Add ‘PYTHON_PRESITE=package.module’ to import a
     module early in the interpreter lifecycle before ‘site.py’ is
     executed.  Python needs to be *note built in debug mode: 1de. for
     this option to exist.

   - gh-110481(41): Implement biased reference counting in
     ‘--disable-gil’ builds.

   - gh-110543(42): Fix regression in Python 3.12 where
     ‘types.CodeType.replace()’ would produce a broken code object if
     called on a module or class code object that contains a
     comprehension.  Patch by Jelle Zijlstra.

   - gh-89519(43): Removed chained *note classmethod: 14a. descriptors
     (introduced in bpo-19072(44)).  This can no longer be used to wrap
     other descriptors such as *note property: 180.  The core design of
     this feature was flawed and caused a number of downstream problems.
     To "pass-through" a *note classmethod: 14a, consider using the
     ‘__wrapped__’ attribute that was added in Python 3.10.

   - gh-103615(45): Use local events for opcode tracing

   - bpo-46657(46): Add mimalloc memory allocator support.

   - gh-106718(47): When PyConfig.stdlib_dir is explicitly set, it's now
     respected and won't be overridden by PyConfig.home.

   - gh-106905(48): Fix incorrect SystemError about AST constructor
     recursion depth mismatch.

   - gh-100445(49): Improve error message for unterminated strings with
     escapes.

   - bpo-45759(50): Improved error messages for ‘elif’/‘else’ statements
     not matching any valid statements.  Patch by Jeremiah Vivian.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/112243

   (2) https://github.com/python/cpython/issues/112287

   (3) https://github.com/python/cpython/issues/112266

   (4) https://github.com/python/cpython/issues/111807

   (5) https://github.com/python/cpython/issues/111798

   (6) https://github.com/python/cpython/issues/106529

   (7) https://github.com/python/cpython/issues/111916

   (8) https://github.com/python/cpython/issues/81137

   (9) https://github.com/python/cpython/issues/79932

   (10) https://github.com/python/cpython/issues/81925

   (11) https://github.com/python/cpython/issues/111843

   (12) https://github.com/python/cpython/issues/110829

   (13) https://github.com/python/cpython/issues/109369

   (14) https://github.com/python/cpython/issues/111772

   (15) https://github.com/python/cpython/issues/111666

   (16) https://github.com/python/cpython/issues/111654

   (17) https://github.com/python/cpython/issues/111623

   (18) https://github.com/python/cpython/issues/111354

   (19) https://github.com/python/cpython/issues/111520

   (20) https://github.com/python/cpython/issues/109181

   (21) https://github.com/python/cpython/issues/111420

   (22) https://github.com/python/cpython/issues/111438

   (23) https://github.com/python/cpython/issues/111435

   (24) https://github.com/python/cpython/issues/102388

   (25) https://github.com/python/cpython/issues/111366

   (26) https://github.com/python/cpython/issues/111380

   (27) https://github.com/python/cpython/issues/111374

   (28) https://github.com/python/cpython/issues/111354

   (29) https://github.com/python/cpython/issues/94438

   (30) https://github.com/python/cpython/issues/67224

   (31) https://github.com/python/cpython/issues/111123

   (32) https://github.com/python/cpython/issues/110938

   (33) https://github.com/python/cpython/issues/109214

   (34) https://github.com/python/cpython/issues/110912

   (35) https://github.com/python/cpython/issues/109894

   (36) https://github.com/python/cpython/issues/110892

   (37) https://github.com/python/cpython/issues/110864

   (38) https://github.com/python/cpython/issues/109094

   (39) https://github.com/python/cpython/issues/110805

   (40) https://github.com/python/cpython/issues/110722

   (41) https://github.com/python/cpython/issues/110481

   (42) https://github.com/python/cpython/issues/110543

   (43) https://github.com/python/cpython/issues/89519

   (44) https://bugs.python.org/issue?@action=redirect&bpo=19072

   (45) https://github.com/python/cpython/issues/103615

   (46) https://bugs.python.org/issue?@action=redirect&bpo=46657

   (47) https://github.com/python/cpython/issues/106718

   (48) https://github.com/python/cpython/issues/106905

   (49) https://github.com/python/cpython/issues/100445

   (50) https://bugs.python.org/issue?@action=redirect&bpo=45759


File: python.info,  Node: Library<11>,  Next: Tests<9>,  Prev: Core and Builtins<12>,  Up: Python 3 13 0 alpha 2

1.23.12.2 Library
.................

   - gh-111942(1): Fix SystemError in the TextIOWrapper constructor with
     non-encodable "errors" argument in non-debug mode.

   - gh-111995(2): Added the ‘NI_IDN’ constant to the *note socket: b8.
     module when present in C at build time for use with *note
     socket.getnameinfo(): 15be.

   - gh-109538(3): Issue warning message instead of having *note
     RuntimeError: 179. be displayed when event loop has already been
     closed at ‘StreamWriter.__del__()’.

   - gh-111942(4): Fix crashes in *note io.TextIOWrapper.reconfigure():
     aed. when pass invalid arguments, e.g.  non-string encoding.

   - gh-111460(5): *note curses: 23.: restore wide character support
     (including *note curses.unget_wch(): 1039. and *note get_wch():
     1038.) on macOS, which was unavailable due to a regression in
     Python 3.12.

   - gh-103791(6): *note contextlib.suppress: eca. now supports
     suppressing exceptions raised as part of a *note
     BaseExceptionGroup: 244, in addition to the recent support for
     *note ExceptionGroup: 19c.

   - gh-111835(7): The *note mmap.mmap: 1f0. class now has an *note
     seekable(): 1f1. method that can be used when a seekable file-like
     object is required.  The *note seek(): 1f2. method now returns the
     new absolute position.  Patch by Donghee Na.

   - gh-111804(8): Remove posix.fallocate() under WASI as the underlying
     posix_fallocate() is not available in WASI preview2.

   - gh-111841(9): Fix truncating arguments on an embedded null
     character in *note os.putenv(): 8c1. and *note os.unsetenv(): 8c0.
     on Windows.

   - gh-111768(10): *note wsgiref.util.is_hop_by_hop(): 15bf. is now
     exposed correctly in ‘__all__’.

   - gh-80731(11): Avoid executing the default function in *note
     cmd.Cmd: 15c0. in an except block

   - gh-111541(12): Fix *note doctest: 31. for *note SyntaxError: 173.
     not-builtin subclasses.

   - gh-111719(13): Add extra argument validation for ‘alias’ command in
     *note pdb: 94.

   - gh-111482(14): *note time: d7.: Make *note time.clock_gettime():
     10f7. and *note time.clock_gettime_ns(): a85. functions up to 2x
     faster by faster calling convention.  Patch by Victor Stinner.

   - gh-110894(15): Call loop exception handler for exceptions in
     ‘client_connected_cb’ of *note asyncio.start_server(): abc. so that
     applications can handle it.  Patch by Kumar Aditya.

   - gh-111531(16): Fix reference leaks in ‘bind_class()’ and
     ‘bind_all()’ methods of *note tkinter: d9. widgets.

   - gh-111246(17): *note asyncio.loop.create_unix_server(): 194. will
     now automatically remove the Unix socket when the server is closed.

   - gh-111356(18): Added *note io.text_encoding(): 15c1, *note
     io.DEFAULT_BUFFER_SIZE: 15c2, and *note
     io.IncrementalNewlineDecoder: 15c3. to ‘io.__all__’.

   - gh-66425(19): Remove the code to set the REMOTE_HOST header from
     wsgiref module, as it is unreachable.  This header is used for
     performance reasons, which is not necessary in the wsgiref module.

   - gh-111429(20): Speed up *note pathlib.PurePath.relative_to(): 2ac.
     and *note is_relative_to(): 2ab.

   - gh-111342(21): Fixed typo in *note math.sumprod(): 43f.

   - gh-68166(22): Remove mention of not supported "vsapi" element type
     in *note tkinter.ttk.Style.element_create(): 23d.  Add tests for
     ‘element_create()’ and other ‘ttk.Style’ methods.  Add examples for
     ‘element_create()’ in the documentation.

   - gh-111388(23): Add ‘show_group’ parameter to *note
     traceback.format_exception_only(): 7f2, which allows to format
     *note ExceptionGroup: 19c. instances.

   - gh-79033(24): Another attempt at fixing *note
     asyncio.Server.wait_closed(): 15c4.  It now blocks until both
     conditions are true: the server is closed, 'and' there are no more
     active connections.  (This means that in some cases where in 3.12.0
     this function would 'incorrectly' have returned immediately, it
     will now block; in particular, when there are no active connections
     but the server hasn't been closed yet.)

   - gh-111259(25): Optimize recursive wildcards in *note pathlib: 93.

   - gh-111295(26): Fix *note time: d7. not checking for errors when
     initializing.

   - gh-111253(27): Add error checking during ‘_socket’ module init.

   - gh-111251(28): Fix ‘_blake2’ not checking for errors when
     initializing.

   - gh-111233(29): Fix *note select: af. not checking for errors when
     initializing.

   - gh-111230(30): Fix *note ssl: bb. not checking for errors when
     initializing.

   - gh-111174(31): Fix crash in *note io.BytesIO.getbuffer(): 1189.
     called repeatedly for empty BytesIO.

   - gh-111187(32): Postpone removal version for
     locale.getdefaultlocale() to Python 3.15.

   - gh-111159(33): Fix *note doctest: 31. output comparison for
     exceptions with notes.

   - gh-110910(34): Fix invalid state handling in *note
     asyncio.TaskGroup: 19b. and *note asyncio.Timeout: 15c5.  They now
     raise proper RuntimeError if they are improperly used and are left
     in consistent state after this.

   - gh-111092(35): Make turtledemo run without default root enabled.

   - gh-110944(36): Support alias and convenience vars for *note pdb:
     94. completion

   - gh-110745(37): Added 'newline' parameter to *note
     pathlib.Path.read_text(): deb.  Patch by Junya Okabe.

   - gh-84583(38): Make *note pdb: 94. enter post-mortem mode even for
     *note SyntaxError: 173.

   - gh-80675(39): Set ‘f_trace_lines = True’ on all frames upon *note
     pdb.set_trace(): 21a.

   - gh-110771(40): Expose the setup and cleanup portions of
     ‘asyncio.run_forever()’ as the standalone methods
     ‘asyncio.run_forever_setup()’ and ‘asyncio.run_forever_cleanup()’.
     This allows for tighter integration with GUI event loops.

   - gh-110774(41): Support setting the *note asyncio.Runner: 5a5.
     loop_factory kwarg in *note unittest.IsolatedAsyncioTestCase: 2de.

   - gh-110392(42): Fix *note tty.setraw(): 15c6. and *note
     tty.setcbreak(): 156e.: previously they returned partially modified
     list of the original tty attributes.  *note tty.cfmakeraw(): 15c7.
     and *note tty.cfmakecbreak(): 156f. now make a copy of the list of
     special characters before modifying it.

   - gh-59013(43): Make line number of function breakpoint more precise
     in *note pdb: 94.

   - gh-88434(44): Emit deprecation warning for non-integer numbers in
     *note gettext: 59. functions and methods that consider plural forms
     even if the translation was not found.

   - gh-110395(45): Ensure that *note select.kqueue(): 15c8. objects
     correctly appear as closed in forked children, to prevent
     operations on an invalid file descriptor.

   - gh-110196(46): Add ‘__reduce__’ method to ‘IPv6Address’ in order to
     keep ‘scope_id’

   - gh-109747(47): Improve errors for unsupported look-behind patterns.
     Now re.error is raised instead of OverflowError or RuntimeError for
     too large width of look-behind pattern.

   - gh-109466(48): Add the *note ipaddress.IPv4Address.ipv6_mapped:
     1e0. property, which returns the IPv4-mapped IPv6 address.

   - gh-85098(49): Implement the CLI of the *note symtable: c2. module
     and improve the repr of *note Symbol: 15c9.

   - gh-108791(50): Improved error handling in *note pdb: 94. command
     line interface, making it produce more concise error messages.

   - gh-105931(51): Change *note compileall: 19. to only strip the
     stripdir prefix from the full path recorded in the compiled ‘.pyc’
     file, when the prefix matches the start of the full path in its
     entirety.  When the prefix does not match, no stripping is
     performed and a warning to this effect is displayed.

     Previously all path components of the stripdir prefix that matched
     the full path were removed, while those that did not match were
     left alone (including ones interspersed between matching
     components).

   - gh-107431(52): Make the ‘DictProxy’ and ‘ListProxy’ types in *note
     multiprocessing.managers: 89. *note Generic Alias Types: 656. for
     ‘[]’ use in typing contexts.

   - gh-72904(53): Add *note glob.translate(): 1cf.  This function
     converts a pathname with shell-style wildcards to a regular
     expression.

   - gh-90026(54): Define ‘USE_XATTRS’ on Cygwin so that XATTR-related
     functions in the *note os: 91. module become available.

   - gh-90890(55): New methods *note mailbox.Maildir.get_info(): 15ca,
     *note mailbox.Maildir.set_info(): 15cb, *note
     mailbox.Maildir.get_flags(): 15cc, *note
     mailbox.Maildir.set_flags(): 15cd, *note
     mailbox.Maildir.add_flag(): 15ce, *note
     mailbox.Maildir.remove_flag(): 15cf.  These methods speed up
     accessing a message's info and/or flags and are useful when it is
     not necessary to access the message's contents, as when iterating
     over a Maildir to find messages with specific flags.

   - gh-102956(56): Fix returning of empty byte strings after seek in
     zipfile module

   - gh-102895(57): Added a parameter ‘local_exit’ for *note
     code.interact(): 15d0. to prevent ‘exit()’ and ‘quit’ from closing
     ‘sys.stdin’ and raise ‘SystemExit’.

   - gh-97928(58): Change the behavior of ‘tkinter.Text.count()’.  It
     now always returns an integer if one or less counting options are
     specified.  Previously it could return a single count as a 1-tuple,
     an integer (only if option ‘"update"’ was specified) or ‘None’ if
     no items found.  The result is now the same if ‘wantobjects’ is set
     to ‘0’.

   - gh-96954(59): Switch the storage of the unicode codepoint names to
     use a different data-structure, a directed acyclic word graph(60).
     This makes the unicodedata shared library about 440 KiB smaller.
     Contributed by Carl Friedrich Bolz-Tereick using code from the PyPy
     project.

   - gh-73561(61): Omit the interface scope from an IPv6 address when
     used as Host header by *note http.client: 65.

   - gh-86826(62): ‘zipinfo’ now supports the full range of values in
     the TZ string determined by RFC 8536 and detects all invalid
     formats.  Both Python and C implementations now raise exceptions of
     the same type on invalid data.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/111942

   (2) https://github.com/python/cpython/issues/111995

   (3) https://github.com/python/cpython/issues/109538

   (4) https://github.com/python/cpython/issues/111942

   (5) https://github.com/python/cpython/issues/111460

   (6) https://github.com/python/cpython/issues/103791

   (7) https://github.com/python/cpython/issues/111835

   (8) https://github.com/python/cpython/issues/111804

   (9) https://github.com/python/cpython/issues/111841

   (10) https://github.com/python/cpython/issues/111768

   (11) https://github.com/python/cpython/issues/80731

   (12) https://github.com/python/cpython/issues/111541

   (13) https://github.com/python/cpython/issues/111719

   (14) https://github.com/python/cpython/issues/111482

   (15) https://github.com/python/cpython/issues/110894

   (16) https://github.com/python/cpython/issues/111531

   (17) https://github.com/python/cpython/issues/111246

   (18) https://github.com/python/cpython/issues/111356

   (19) https://github.com/python/cpython/issues/66425

   (20) https://github.com/python/cpython/issues/111429

   (21) https://github.com/python/cpython/issues/111342

   (22) https://github.com/python/cpython/issues/68166

   (23) https://github.com/python/cpython/issues/111388

   (24) https://github.com/python/cpython/issues/79033

   (25) https://github.com/python/cpython/issues/111259

   (26) https://github.com/python/cpython/issues/111295

   (27) https://github.com/python/cpython/issues/111253

   (28) https://github.com/python/cpython/issues/111251

   (29) https://github.com/python/cpython/issues/111233

   (30) https://github.com/python/cpython/issues/111230

   (31) https://github.com/python/cpython/issues/111174

   (32) https://github.com/python/cpython/issues/111187

   (33) https://github.com/python/cpython/issues/111159

   (34) https://github.com/python/cpython/issues/110910

   (35) https://github.com/python/cpython/issues/111092

   (36) https://github.com/python/cpython/issues/110944

   (37) https://github.com/python/cpython/issues/110745

   (38) https://github.com/python/cpython/issues/84583

   (39) https://github.com/python/cpython/issues/80675

   (40) https://github.com/python/cpython/issues/110771

   (41) https://github.com/python/cpython/issues/110774

   (42) https://github.com/python/cpython/issues/110392

   (43) https://github.com/python/cpython/issues/59013

   (44) https://github.com/python/cpython/issues/88434

   (45) https://github.com/python/cpython/issues/110395

   (46) https://github.com/python/cpython/issues/110196

   (47) https://github.com/python/cpython/issues/109747

   (48) https://github.com/python/cpython/issues/109466

   (49) https://github.com/python/cpython/issues/85098

   (50) https://github.com/python/cpython/issues/108791

   (51) https://github.com/python/cpython/issues/105931

   (52) https://github.com/python/cpython/issues/107431

   (53) https://github.com/python/cpython/issues/72904

   (54) https://github.com/python/cpython/issues/90026

   (55) https://github.com/python/cpython/issues/90890

   (56) https://github.com/python/cpython/issues/102956

   (57) https://github.com/python/cpython/issues/102895

   (58) https://github.com/python/cpython/issues/97928

   (59) https://github.com/python/cpython/issues/96954

   (60) 
https://en.wikipedia.org/wiki/Deterministic_acyclic_finite_state_automaton

   (61) https://github.com/python/cpython/issues/73561

   (62) https://github.com/python/cpython/issues/86826


File: python.info,  Node: Tests<9>,  Next: Build<11>,  Prev: Library<11>,  Up: Python 3 13 0 alpha 2

1.23.12.3 Tests
...............

   - gh-111808(1): Make the default value of
     ‘test.support.infinite_recursion()’ to be conditional based on
     whether optimizations were used when compiling the interpreter.
     This helps with platforms like WASI whose stack size is greatly
     restricted in debug builds.

   - gh-110722(2): Gathering line coverage of standard libraries within
     the regression test suite is now precise, as well as much faster.
     Patch by Łukasz Langa.

   - gh-110367(3): Make regrtest ‘--verbose3’ option compatible with
     ‘--huntrleaks -jN’ options.  The ‘./python -m test -j1 -R 3:3
     --verbose3’ command now works as expected.  Patch by Victor
     Stinner.

   - gh-111165(4): Remove no longer used functions ‘run_unittest()’ and
     ‘run_doctest()’ from the *note test.support: cd. module.

   - gh-110932(5): Fix regrtest if the ‘SOURCE_DATE_EPOCH’ environment
     variable is defined: use the variable value as the random seed.
     Patch by Victor Stinner.

   - gh-110995(6): test_gdb: Fix detection of gdb built without Python
     scripting support.  Patch by Victor Stinner.

   - gh-110918(7): Test case matching patterns specified by options
     ‘--match’, ‘--ignore’, ‘--matchfile’ and ‘--ignorefile’ are now
     tested in the order of specification, and the last match determines
     whether the test case be run or ignored.

   - gh-108747(8): Add unit test for ‘usercustomize’ and ‘sitecustomize’
     hooks from *note site: b5.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/111808

   (2) https://github.com/python/cpython/issues/110722

   (3) https://github.com/python/cpython/issues/110367

   (4) https://github.com/python/cpython/issues/111165

   (5) https://github.com/python/cpython/issues/110932

   (6) https://github.com/python/cpython/issues/110995

   (7) https://github.com/python/cpython/issues/110918

   (8) https://github.com/python/cpython/issues/108747


File: python.info,  Node: Build<11>,  Next: Windows<8>,  Prev: Tests<9>,  Up: Python 3 13 0 alpha 2

1.23.12.4 Build
...............

   - gh-96954(1): Make ‘make regen-unicodedata’ work for out-of-tree
     builds of CPython.

   - gh-112088(2): Add ‘Tools/build/regen-configure.sh’ script to
     regenerate the ‘configure’ with an Ubuntu container image.  The
     ‘quay.io/tiran/cpython_autoconf:271’ container image
     (tiran/cpython_autoconf(3)) is no longer used.  Patch by Victor
     Stinner.

   - gh-111046(4): For wasi-threads, memory is now exported to fix
     compatibility issues with some wasm runtimes.

   - gh-110828(5): AIX 32bit needs ‘-latomic’ to build the ‘_testcapi’
     extension module.

   - gh-85283(6): The ‘errno’, ‘md5’, ‘resource’, ‘winsound’,
     ‘_ctypes_test’, ‘_multiprocessing.posixshmem’, ‘_scproxy’, ‘_stat’,
     ‘_testimportmultiple’ and ‘_uuid’ C extensions are now built with
     the *note limited C API: 318.  Patch by Victor Stinner.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/96954

   (2) https://github.com/python/cpython/issues/112088

   (3) https://github.com/tiran/cpython_autoconf

   (4) https://github.com/python/cpython/issues/111046

   (5) https://github.com/python/cpython/issues/110828

   (6) https://github.com/python/cpython/issues/85283


File: python.info,  Node: Windows<8>,  Next: macOS<6>,  Prev: Build<11>,  Up: Python 3 13 0 alpha 2

1.23.12.5 Windows
.................

   - gh-111856(1): Fixes *note fstat(): d32. on file systems that do not
     support file ID requests.  This includes FAT32 and exFAT.

   - gh-111293(2): Fix *note os.DirEntry.inode: 15d4. dropping higher 64
     bits of a file id on some filesystems on Windows.

   - gh-110913(3): WindowsConsoleIO now correctly chunks large buffers
     without splitting up UTF-8 sequences.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/111856

   (2) https://github.com/python/cpython/issues/111293

   (3) https://github.com/python/cpython/issues/110913


File: python.info,  Node: macOS<6>,  Next: IDLE<10>,  Prev: Windows<8>,  Up: Python 3 13 0 alpha 2

1.23.12.6 macOS
...............

   - gh-59703(1): For macOS framework builds, in ‘getpath.c’ use the
     system ‘dladdr’ function to find the path to the shared library
     rather than depending on deprecated macOS APIs.

   - gh-110950(2): Update macOS installer to include an upstream Tcl/Tk
     fix for the ‘Secure coding is not enabled for restorable state!’
     warning encountered in Tkinter on macOS 14 Sonoma.

   - gh-111015(3): Ensure that IDLE.app and Python Launcher.app are
     installed with appropriate permissions on macOS builds.

   - gh-71383(4): Update macOS installer to include an upstream Tcl/Tk
     fix for the ‘ttk::ThemeChanged’ error encountered in Tkinter.

   - gh-92603(5): Update macOS installer to include a fix accepted by
     upstream Tcl/Tk for a crash encountered after the first *note
     tkinter.Tk(): 152a. instance is destroyed.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/59703

   (2) https://github.com/python/cpython/issues/110950

   (3) https://github.com/python/cpython/issues/111015

   (4) https://github.com/python/cpython/issues/71383

   (5) https://github.com/python/cpython/issues/92603


File: python.info,  Node: IDLE<10>,  Next: Tools/Demos<4>,  Prev: macOS<6>,  Up: Python 3 13 0 alpha 2

1.23.12.7 IDLE
..............

   - bpo-35668(1): Add docstrings to the IDLE debugger module.  Fix two
     bugs: initialize ‘Idb.botframe’ (should be in Bdb); in
     ‘Idb.in_rpc_code’, check whether ‘prev_frame’ is ‘None’ before
     trying to use it.  Greatly expand test_debugger.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35668


File: python.info,  Node: Tools/Demos<4>,  Next: C API<11>,  Prev: IDLE<10>,  Up: Python 3 13 0 alpha 2

1.23.12.8 Tools/Demos
.....................

   - gh-111903(1): Argument Clinic now supports the ‘@critical_section’
     directive that instructs Argument Clinic to generate a critical
     section around the function call, which locks the ‘self’ object in
     ‘--disable-gil’ builds.  Patch by Sam Gross.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/111903


File: python.info,  Node: C API<11>,  Prev: Tools/Demos<4>,  Up: Python 3 13 0 alpha 2

1.23.12.9 C API
...............

   - gh-112026(1): Add again the private ‘_PyThreadState_UncheckedGet()’
     function as an alias to the new public *note
     PyThreadState_GetUnchecked(): 31e. function.  Patch by Victor
     Stinner.

   - gh-112026(2): Restore the removed
     ‘_PyDict_GetItemStringWithError()’ function.  It is used by numpy.
     Patch by Victor Stinner.

   - gh-112026(3): Restore removed private C API functions, macros and
     structures which have no simple replacement for now:

        * _PyDict_GetItem_KnownHash()

        * _PyDict_NewPresized()

        * _PyHASH_BITS

        * _PyHASH_IMAG

        * _PyHASH_INF

        * _PyHASH_MODULUS

        * _PyHASH_MULTIPLIER

        * _PyLong_Copy()

        * _PyLong_FromDigits()

        * _PyLong_New()

        * _PyLong_Sign()

        * _PyObject_CallMethodId()

        * _PyObject_CallMethodNoArgs()

        * _PyObject_CallMethodOneArg()

        * _PyObject_CallOneArg()

        * _PyObject_EXTRA_INIT

        * _PyObject_FastCallDict()

        * _PyObject_GetAttrId()

        * _PyObject_Vectorcall()

        * _PyObject_VectorcallMethod()

        * _PyStack_AsDict()

        * _PyThread_CurrentFrames()

        * _PyUnicodeWriter structure

        * _PyUnicodeWriter_Dealloc()

        * _PyUnicodeWriter_Finish()

        * _PyUnicodeWriter_Init()

        * _PyUnicodeWriter_Prepare()

        * _PyUnicodeWriter_PrepareKind()

        * _PyUnicodeWriter_WriteASCIIString()

        * _PyUnicodeWriter_WriteChar()

        * _PyUnicodeWriter_WriteLatin1String()

        * _PyUnicodeWriter_WriteStr()

        * _PyUnicodeWriter_WriteSubstring()

        * _PyUnicode_AsString()

        * _PyUnicode_FromId()

        * _PyVectorcall_Function()

        * _Py_IDENTIFIER()

        * _Py_c_abs()

        * _Py_c_diff()

        * _Py_c_neg()

        * _Py_c_pow()

        * _Py_c_prod()

        * _Py_c_quot()

        * _Py_c_sum()

        * _Py_static_string()

        * _Py_static_string_init()

     Patch by Victor Stinner.

   - gh-112026(4): Add again ‘<ctype.h>’ and ‘<unistd.h>’ includes in
     ‘Python.h’, but don't include them in the limited C API version
     3.13 and newer.  Patch by Victor Stinner.

   - gh-111956(5): Add internal-only one-time initialization API:
     ‘_PyOnceFlag’ and ‘_PyOnceFlag_CallOnce’.

   - gh-111262(6): Add *note PyDict_Pop(): 32b. and *note
     PyDict_PopString(): 32c. functions: remove a key from a dictionary
     and optionally return the removed value.  This is similar to *note
     dict.pop(): 32d, but without the default value and not raising
     *note KeyError: 2fb. if the key missing.  Patch by Stefan Behnel
     and Victor Stinner.

   - gh-111863(7): Rename ‘Py_NOGIL’ to ‘Py_GIL_DISABLED’.  Patch by
     Hugo van Kemenade.

   - gh-111138(8): Add *note PyList_Extend(): 329. and *note
     PyList_Clear(): 32a. functions: similar to Python ‘list.extend()’
     and ‘list.clear()’ methods.  Patch by Victor Stinner.

   - gh-108765(9): On Windows, ‘Python.h’ no longer includes the
     ‘<stddef.h>’ standard header file.  If needed, it should now be
     included explicitly.  Patch by Victor Stinner.

   - gh-111569(10): Implement "Python Critical Sections" from PEP
     703(11).  These are macros to help replace the GIL with per-object
     locks in the ‘--disable-gil’ build of CPython.  The macros are
     no-ops in the default build.

   - gh-111506(12): In the limited C API version 3.13, *note
     Py_SET_REFCNT(): 84f. function is now implemented as an opaque
     function call.  Patch by Victor Stinner.

   - gh-108082(13): Add *note PyErr_FormatUnraisable(): 327. function.

   - gh-110964(14): Move the undocumented private _PyArg functions and
     _PyArg_Parser structure to internal C API (‘pycore_modsupport.h’).
     Patch by Victor Stinner.

   - gh-110815(15): Support non-ASCII keyword names in *note
     PyArg_ParseTupleAndKeywords(): 2e9.

   - gh-109587(16): Introduced
     ‘PyUnstable_PerfTrampoline_CompileCode()’,
     ‘PyUnstable_PerfTrampoline_SetPersistAfterFork()’ and
     ‘PyUnstable_CopyPerfMapFile()’.  These functions allow extension
     modules to initialize trampolines eagerly, after the application is
     "warmed up".  This makes it possible to have perf-trampolines
     running in an always-enabled fashion.

   - gh-85283(17): Add the *note PySys_Audit(): 321. function to the
     limited C API. Patch by Victor Stinner.

   - gh-85283(18): Add *note PyMem_RawMalloc(): 323, *note
     PyMem_RawCalloc(): 324, *note PyMem_RawRealloc(): 325. and *note
     PyMem_RawFree(): 326. to the limited C API. Patch by Victor
     Stinner.

   - gh-106672(19): Functions *note PyDict_GetItem(): 35b, *note
     PyDict_GetItemString(): 35c, *note PyMapping_HasKey(): 301, *note
     PyMapping_HasKeyString(): 303, *note PyObject_HasAttr(): 2fd, *note
     PyObject_HasAttrString(): 2ff, and *note PySys_GetObject(): 35d,
     which clear all errors occurred during calling the function, report
     now them using *note sys.unraisablehook(): 1dc.

   - gh-67565(20): Remove redundant C-contiguity check in ‘getargs.c’,
     *note binascii: c, *note ssl: bb. and Argument Clinic.  Patched by
     Stefan Krah and Furkan Onder

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/112026

   (2) https://github.com/python/cpython/issues/112026

   (3) https://github.com/python/cpython/issues/112026

   (4) https://github.com/python/cpython/issues/112026

   (5) https://github.com/python/cpython/issues/111956

   (6) https://github.com/python/cpython/issues/111262

   (7) https://github.com/python/cpython/issues/111863

   (8) https://github.com/python/cpython/issues/111138

   (9) https://github.com/python/cpython/issues/108765

   (10) https://github.com/python/cpython/issues/111569

   (11) https://peps.python.org/pep-0703/

   (12) https://github.com/python/cpython/issues/111506

   (13) https://github.com/python/cpython/issues/108082

   (14) https://github.com/python/cpython/issues/110964

   (15) https://github.com/python/cpython/issues/110815

   (16) https://github.com/python/cpython/issues/109587

   (17) https://github.com/python/cpython/issues/85283

   (18) https://github.com/python/cpython/issues/85283

   (19) https://github.com/python/cpython/issues/106672

   (20) https://github.com/python/cpython/issues/67565


File: python.info,  Node: Python 3 13 0 alpha 1,  Next: Python 3 12 0 beta 1,  Prev: Python 3 13 0 alpha 2,  Up: Changelog（更動日誌）

1.23.13 Python 3.13.0 alpha 1
-----------------------------

'Release date: 2023-10-13'

* Menu:

* Security: Security<8>.
* Core and Builtins: Core and Builtins<13>.
* Library: Library<12>.
* Documentation: Documentation<7>.
* Tests: Tests<10>.
* Build: Build<12>.
* Windows: Windows<9>.
* macOS: macOS<7>.
* IDLE: IDLE<11>.
* Tools/Demos: Tools/Demos<5>.
* C API: C API<12>.


File: python.info,  Node: Security<8>,  Next: Core and Builtins<13>,  Up: Python 3 13 0 alpha 1

1.23.13.1 Security
..................

   - gh-108310(1): Fixed an issue where instances of *note
     ssl.SSLSocket: 88f. were vulnerable to a bypass of the TLS
     handshake and included protections (like certificate verification)
     and treating sent unencrypted data as if it were post-handshake TLS
     encrypted data.  Security issue reported as CVE-2023-40217(2) by
     Aapo Oksman.  Patch by Gregory P. Smith.

   - gh-107774(3): PEP 669 specifies that
     ‘sys.monitoring.register_callback’ will generate an audit event.
     Pre-releases of Python 3.12 did not generate the audit event.  This
     is now fixed.

   - gh-102988(4): Reverted the *note email.utils: 47. security
     improvement change released in 3.12beta4 that unintentionally
     caused *note email.utils.getaddresses: 1c4. to fail to parse email
     addresses with a comma in the quoted name field.  See gh-106669(5).

   - gh-99108(6): Refresh our new HACL* built-in *note hashlib: 5e. code
     from upstream.  Built-in SHA2 should be faster and an issue with
     SHA3 on 32-bit platforms is fixed.

   - gh-102509(7): Start initializing ‘ob_digit’ during creation of
     *note PyLongObject: 52e. objects.  Patch by Illia Volochii.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/108310

   (2) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40217

   (3) https://github.com/python/cpython/issues/107774

   (4) https://github.com/python/cpython/issues/102988

   (5) https://github.com/python/cpython/issues/106669

   (6) https://github.com/python/cpython/issues/99108

   (7) https://github.com/python/cpython/issues/102509


File: python.info,  Node: Core and Builtins<13>,  Next: Library<12>,  Prev: Security<8>,  Up: Python 3 13 0 alpha 1

1.23.13.2 Core and Builtins
...........................

   - gh-110782(1): Fix crash when *note typing.TypeVar: 141. is
     constructed with a keyword argument.  Patch by Jelle Zijlstra.

   - gh-110752(2): Reset ‘ceval.eval_breaker’ in ‘interpreter_clear()’

   - gh-110721(3): Use the *note traceback: e7. implementation for the
     default ‘PyErr_Display()’ functionality.  Patch by Pablo Galindo

   - gh-110696(4): Fix incorrect error message for invalid argument
     unpacking.  Patch by Pablo Galindo

   - gh-104169(5): Split the tokenizer into two separate directories: -
     One part includes the actual lexeme producing logic and lives in
     ‘Parser/lexer’.  - The second part wraps the lexer according to the
     different tokenization modes we have (string, utf-8, file,
     interactive, readline) and lives in ‘Parser/tokenizer’.

   - gh-110688(6): Remove undocumented ‘test_c_api’ method from *note
     set: 57d, which was only defined for testing purposes under
     ‘Py_DEBUG’.  Now we have proper CAPI tests.

   - gh-104584(7): Fix a reference leak when running with ‘PYTHONUOPS’
     or *note -X uops: 15a. enabled.

   - gh-110514(8): Add ‘PY_THROW’ to *note sys.setprofile(): 146d.
     events

   - gh-110489(9): Optimise *note math.ceil(): 1330. when the input is
     exactly a float, resulting in about a 10% improvement.

   - gh-110455(10): Guard ‘assert(tstate->thread_id > 0)’ with ‘#ifndef
     HAVE_PTHREAD_STUBS’.  This allows for for pydebug builds to work
     under WASI which (currently) lacks thread support.

   - gh-110309(11): Remove unnecessary empty constant nodes in the ast
     of f-string specs.

   - gh-110259(12): Correctly identify the format spec in f-strings
     (with single or triple quotes) that have multiple lines in the
     expression part and include a formatting spec.  Patch by Pablo
     Galindo

   - gh-110237(13): Fix missing error checks for calls to
     ‘PyList_Append’ in ‘_PyEval_MatchClass’.

   - gh-110164(14): regrtest: If the ‘SOURCE_DATE_EPOCH’ environment
     variable is defined, regrtest now disables tests randomization.
     Patch by Victor Stinner.

   - gh-109889(15): Fix the compiler's redundant NOP detection algorithm
     to skip over NOPs with no line number when looking for the next
     instruction's lineno.

   - gh-109853(16): ‘sys.path[0]’ is now set correctly for
     subinterpreters.

   - gh-109923(17): Set line number on the ‘POP_TOP’ that follows a
     ‘RETURN_GENERATOR’.

   - gh-105716(18): Subinterpreters now correctly handle the case where
     they have threads running in the background.  Before, such threads
     would interfere with cleaning up and destroying them, as well as
     prevent running another script.

   - gh-109369(19): The internal eval_breaker and supporting flags, plus
     the monitoring version have been merged into a single atomic
     integer to speed up checks.

   - gh-109823(20): Fix bug where compiler does not adjust labels when
     removing an empty basic block which is a jump target.

   - gh-109793(21): The main thread no longer exits prematurely when a
     subinterpreter is cleaned up during runtime finalization.  The bug
     was a problem particularly because, when triggered, the Python
     process would always return with a 0 exitcode, even if it failed.

   - gh-109719(22): Fix missing jump target labels when compiler
     reorders cold/warm blocks.

   - gh-109595(23): Add *note -X cpu_count: 15a. command line option to
     override return results of *note os.cpu_count(): 1a8. and *note
     os.process_cpu_count(): 1a7.  This option is useful for users who
     need to limit CPU resources of a container system without having to
     modify the container (application code).  Patch by Donghee Na.

   - gh-109627(24): Fix bug where the compiler does not assign a new
     jump target label to a duplicated small exit block.

   - gh-109596(25): Fix some tokens in the grammar that were incorrectly
     marked as soft keywords.  Also fix some repeated rule names and
     ensure that repeated rules are not allowed.  Patch by Pablo Galindo

   - gh-109496(26): On a Python built in debug mode, *note Py_DECREF():
     515. now calls ‘_Py_NegativeRefcount()’ if the object is a dangling
     pointer to deallocated memory: memory filled with ‘0xDD’ "dead
     byte" by the debug hook on memory allocators.  The fix is to check
     the reference count 'before' checking for ‘_Py_IsImmortal()’.
     Patch by Victor Stinner.

   - gh-107265(27): Deopt opcodes hidden by the executor when base
     opcode is needed

   - gh-109371(28): Deopted instructions correctly for tool
     initialization and modified the incorrect assertion in
     instrumentation, when a previous tool already sets INSTRUCTION
     events

   - gh-105658(29): Fix bug where the line trace of an except block
     ending with a conditional includes an excess event with the line of
     the conditional expression.

   - gh-109219(30): Fix compiling type param scopes that use a name
     which is also free in an inner scope.

   - gh-109351(31): Fix crash when compiling an invalid AST involving a
     named (walrus) expression.

   - gh-109341(32): Fix crash when compiling an invalid AST involving a
     *note ast.TypeAlias: 15dc.

   - gh-109195(33): Fix source location for the ‘LOAD_*’ instruction
     preceding a ‘LOAD_SUPER_ATTR’ to load the ‘super’ global (or
     shadowing variable) so that it encompasses only the name ‘super’
     and not the following parentheses.

   - gh-109256(34): Opcode IDs for specialized opcodes are allocated in
     their own range to improve stability of the IDs for the 'real'
     opcodes.

   - gh-109216(35): Fix possible memory leak in *note BUILD_MAP: 15dd.

   - gh-109207(36): Fix a SystemError in ‘__repr__’ of symtable entry
     object.

   - gh-109179(37): Fix bug where the C traceback display drops notes
     from *note SyntaxError: 173.

   - gh-109118(38): Disallow nested scopes (lambdas, generator
     expressions, and comprehensions) within PEP 695 annotation scopes
     that are nested within classes.

   - gh-109156(39): Add tests for de-instrumenting instructions while
     keeping the instrumentation for lines

   - gh-109114(40): Relax the detection of the error message for invalid
     lambdas inside f-strings to not search for arbitrary replacement
     fields to avoid false positives.  Patch by Pablo Galindo

   - gh-105848(41): Add a new *note CALL_KW: 15de. opcode, used for
     calls containing keyword arguments.  Also, fix a possible crash
     when jumping over method calls in a debugger.

   - gh-109052(42): Use the base opcode when comparing code objects to
     avoid interference from instrumentation

   - gh-109118(43): Fix interpreter crash when a NameError is raised
     inside the type parameters of a generic class.

   - gh-88943(44): Improve syntax error for non-ASCII character that
     follows a numerical literal.  It now points on the invalid
     non-ASCII character, not on the valid numerical literal.

   - gh-108976(45): Fix crash that occurs after de-instrumenting a code
     object in a monitoring callback.

   - gh-108732(46): Make iteration variables of module- and class-scoped
     comprehensions visible to pdb and other tools that use
     ‘frame.f_locals’ again.

   - gh-108959(47): Fix caret placement for error locations for
     subscript and binary operations that involve non-semantic
     parentheses and spaces.  Patch by Pablo Galindo

   - gh-104584(48): Fix a crash when running with ‘PYTHONUOPS’ or *note
     -X uops: 15a. enabled and an error occurs during optimization.

   - gh-108727(49): Define ‘tp_dealloc’ for ‘CounterOptimizer_Type’.
     This fixes a segfault on deallocation.

   - gh-108520(50): Fix
     ‘multiprocessing.synchronize.SemLock.__setstate__()’ to properly
     initialize ‘multiprocessing.synchronize.SemLock._is_fork_ctx’.
     This fixes a regression when passing a SemLock across nested
     processes.

     Rename ‘multiprocessing.synchronize.SemLock.is_fork_ctx’ to
     ‘multiprocessing.synchronize.SemLock._is_fork_ctx’ to avoid
     exposing it as public API.

   - gh-108654(51): Restore locals shadowed by an inlined comprehension
     if the comprehension raises an exception.

   - gh-108488(52): Change the initialization of inline cache entries so
     that the cache entry for ‘JUMP_BACKWARD’ is initialized to zero,
     instead of the ‘adaptive_counter_warmup()’ value used for all other
     instructions.  This counter, unique among instructions, counts up
     from zero.

   - gh-108716(53): Turn off deep-freezing of code objects.  Modules are
     still frozen, so that a file system search is not needed for common
     modules.

   - gh-108614(54): Add RESUME_CHECK instruction, to avoid having to
     handle instrumentation, signals, and contexts switches in the tier
     2 execution engine.

   - gh-108487(55): Move an assert that would cause a spurious crash in
     a devious case that should only trigger deoptimization.

   - gh-106176(56): Use a ‘WeakValueDictionary’ to track the lists
     containing the modules each thread is currently importing.  This
     helps avoid a reference leak from keeping the list around longer
     than necessary.  Weakrefs are used as GC can't interrupt the
     cleanup.

   - gh-105481(57): The regen-opcode build stage was removed and its
     work is now done in regen-cases.

   - gh-107901(58): Fix missing line number on *note JUMP_BACKWARD: 6b0.
     at the end of a for loop.

   - gh-108113(59): The *note compile(): 178. built-in can now accept a
     new flag, ‘ast.PyCF_OPTIMIZED_AST’, which is similar to
     ‘ast.PyCF_ONLY_AST’ except that the returned ‘AST’ is optimized
     according to the value of the ‘optimize’ argument.

     *note ast.parse(): 18e. now accepts an optional argument ‘optimize’
     which is passed on to the *note compile(): 178. built-in.  This
     makes it possible to obtain an optimized ‘AST’.

   - gh-107971(60): Opcode IDs are generated from bytecodes.c instead of
     being hard coded in opcode.py.

   - gh-107944(61): Improve error message for function calls with bad
     keyword arguments.  Patch by Pablo Galindo

   - gh-108390(62): Raise an exception when setting a non-local event
     (‘RAISE’, ‘EXCEPTION_HANDLED’, etc.)  in
     ‘sys.monitoring.set_local_events’.

     Fixes crash when tracing in recursive calls to Python classes.

   - gh-108035(63): Remove the ‘_PyCFrame’ struct, moving the pointer to
     the current interpreter frame back to the threadstate, as it was
     for 3.10 and earlier.  The ‘_PyCFrame’ existed as a performance
     optimization for tracing.  Since PEP 669 has been implemented, this
     optimization no longer applies.

   - gh-91051(64): Fix abort / segfault when using all eight type
     watcher slots, on platforms where ‘char’ is signed by default.

   - gh-106581(65): Fix possible assertion failures and missing
     instrumentation events when ‘PYTHONUOPS’ or *note -X uops: 15a. is
     enabled.

   - gh-107526(66): Revert converting ‘vars’, ‘dir’, ‘next’, ‘getattr’,
     and ‘iter’ to argument clinic.

   - gh-84805(67): Autogenerate signature for *note METH_NOARGS: 1443.
     and *note METH_O: 1477. extension functions.

   - gh-107758(68): Make the ‘dump_stack()’ routine used by the
     ‘lltrace’ feature (low-level interpreter debugging) robust against
     recursion by ensuring that it never calls a ‘__repr__’ method
     implemented in Python.  Also make the similar output for Tier-2
     uops appear on ‘stdout’ (instead of ‘stderr’), to match the
     ‘lltrace’ code in ceval.c.

   - gh-107659(69): Add docstrings for *note ctypes.pointer(): 15df. and
     *note ctypes.POINTER(): 15e0.

   - gh-105848(70): Modify the bytecode so that the actual callable for
     a *note CALL: 6ab. is at a consistent position on the stack
     (regardless of whether or not bound-method-calling optimizations
     are active).

   - gh-107674(71): Fixed performance regression in ‘sys.settrace’.

   - gh-107724(72): In pre-release versions of 3.12, up to rc1, the
     sys.monitoring callback function for the ‘PY_THROW’ event was
     missing the third, exception argument.  That is now fixed.

   - gh-84436(73): Skip reference count modifications for many known
     immortal objects.

   - gh-107596(74): Specialize subscripting *note str: 3f2. objects by
     *note int: 23c. indexes.

   - gh-107080(75): Trace refs builds (‘--with-trace-refs’) were
     crashing when used with isolated subinterpreters.  The problematic
     global state has been isolated to each interpreter.  Other fixing
     the crashes, this change does not affect users.

   - gh-107557(76): Generate the cases needed for the barebones tier 2
     abstract interpreter for optimization passes in CPython.

   - gh-106608(77): Make ‘_PyUOpExecutorObject’ variable length.

   - gh-100964(78): Clear generators' exception state after ‘return’ to
     break reference cycles.

   - gh-107455(79): Improve error messages when converting an
     incompatible type to *note ctypes.c_char_p: 15e1, *note
     ctypes.c_wchar_p: 15e2. and *note ctypes.c_void_p: 15e3.

   - gh-107263(80): Increase C recursion limit for functions other than
     the main interpreter from 800 to 1500.  This should allow functions
     like ‘list.__repr__’ and ‘json.dumps’ to handle all the inputs that
     they could prior to 3.12

   - gh-104584(81): Fix an issue which caused incorrect inline caches to
     be read when running with ‘PYTHONUOPS’ or *note -X uops: 15a.
     enabled.

   - gh-104432(82): Fix potential unaligned memory access on C APIs
     involving returned sequences of ‘char *’ pointers within the *note
     grp: 5c. and *note socket: b8. modules.  These were revealed using
     a ‘-fsaniziter=alignment’ build on ARM macOS. Patch by Christopher
     Chavez.

   - gh-106078(83): Isolate ‘_decimal’ (apply PEP 687(84)).  Patch by
     Charlie Zhao.

   - gh-106898(85): Add the exception as the third argument to
     ‘PY_UNIND’ callbacks in ‘sys.monitoring’.  This makes the
     ‘PY_UNWIND’ callback consistent with the other exception handling
     callbacks.

   - gh-106895(86): Raise a ‘ValueError’ when a monitoring callback
     function returns ‘DISABLE’ for events that cannot be disabled
     locally.

   - gh-106897(87): Add a ‘RERAISE’ event to ‘sys.monitoring’, which
     occurs when an exception is reraise, either explicitly by a plain
     ‘raise’ statement, or implicitly in an ‘except’ or ‘finally’ block.

   - gh-77377(88): Ensure that multiprocessing synchronization objects
     created in a fork context are not sent to a different process
     created in a spawn context.  This changes a segfault into an
     actionable RuntimeError in the parent process.

   - gh-106931(89): Statically allocated string objects are now interned
     globally instead of per-interpreter.  This fixes a situation where
     such a string would only be interned in a single interpreter.
     Normal string objects are unaffected.

   - gh-104621(90): Unsupported modules now always fail to be imported.

   - gh-107122(91): Add *note dbm.ndbm.ndbm.clear(): 1b9. to *note
     dbm.ndbm: 2c.  Patch By Donghee Na.

   - gh-107122(92): Add *note dbm.gnu.gdbm.clear(): 1b8. to *note
     dbm.gnu: 2b.  Patch By Donghee Na.

   - gh-107015(93): The ASYNC and AWAIT tokens are removed from the
     Grammar, which removes the possibility of making ‘async’ and
     ‘await’ soft keywords when using ‘feature_version<7’ in *note
     ast.parse(): 18e.

   - gh-106917(94): Fix classmethod-style *note super(): 483. method
     calls (i.e., where the second argument to *note super(): 483, or
     the implied second argument drawn from ‘self/cls’ in the case of
     zero-arg super, is a type) when the target of the call is not a
     classmethod.

   - gh-105699(95): Python no longer crashes due an infrequent race when
     initializing per-interpreter interned strings.  The crash would
     manifest when the interpreter was finalized.

   - gh-105699(96): Python no longer crashes due to an infrequent race
     in setting ‘Py_FileSystemDefaultEncoding’ and
     ‘Py_FileSystemDefaultEncodeErrors’ (both deprecated), when
     simultaneously initializing two isolated subinterpreters.  Now they
     are only set during runtime initialization.

   - gh-106908(97): Fix various hangs, reference leaks, test failures,
     and tracing/introspection bugs when running with ‘PYTHONUOPS’ or
     *note -X uops: 15a. enabled.

   - gh-106092(98): Fix a segmentation fault caused by a use-after-free
     bug in ‘frame_dealloc’ when the trashcan delays the deallocation of
     a ‘PyFrameObject’.

   - gh-106485(99): Reduce the number of materialized instances
     dictionaries by dematerializing them when possible.

   - gh-106719(100): No longer suppress arbitrary errors in the
     ‘__annotations__’ getter and setter in the type and module types.

   - gh-106723(101): Propagate ‘frozen_modules’ to multiprocessing
     spawned process interpreters.

   - gh-104909(102): Split ‘LOAD_ATTR_INSTANCE_VALUE’ into micro-ops.

   - gh-104909(103): Split *note LOAD_GLOBAL: 15e4. specializations into
     micro-ops.

   - gh-106597(104): A new debug structure of offsets has been added to
     the ‘_PyRuntimeState’ that will help out-of-process debuggers and
     profilers to obtain the offsets to relevant interpreter structures
     in a way that is agnostic of how Python was compiled and that
     doesn't require copying the headers.  Patch by Pablo Galindo

   - gh-106487(105): Allow the 'count' argument of *note str.replace():
     17e. to be a keyword.  Patch by Hugo van Kemenade.

   - gh-96844(106): Improve error message of ‘list.remove()’.  Patch by
     Donghee Na.

   - gh-81283(107): Compiler now strips indents from docstrings.  It
     reduces ‘pyc’ file size 5% when the module is heavily documented.
     This change affects to ‘__doc__’ so tools like doctest will be
     affected.

   - gh-106396(108): When the format specification of an f-string
     expression is empty, the parser now generates an empty *note
     ast.JoinedStr: 15e5. node for it instead of an one-element *note
     ast.JoinedStr: 15e5. with an empty string *note ast.Constant: 29a.

   - gh-100288(109): Specialize *note LOAD_ATTR: 486. for
     non-descriptors on the class.  Adds
     ‘LOAD_ATTR_NONDESCRIPTOR_WITH_VALUES’ and
     ‘LOAD_ATTR_NONDESCRIPTOR_NO_DICT’.

   - gh-106008(110): Fix possible reference leaks when failing to
     optimize comparisons with *note None: 61b. in the bytecode
     compiler.

   - gh-106145(111): Make ‘end_lineno’ and ‘end_col_offset’ required on
     ‘type_param’ ast nodes.

   - gh-106213(112): Changed the way that Emscripten call trampolines
     work for compatibility with Wasm/JS Promise integration.

   - gh-106182(113): *note sys.getfilesystemencoding(): c00. and *note
     sys.getfilesystemencodeerrors: c8d. now return interned Unicode
     object.

   - gh-106210(114): Removed Emscripten import trampoline as it was no
     longer necessary for Pyodide.

   - gh-104584(115): Added a new, experimental, tracing optimizer and
     interpreter (a.k.a.  "tier 2").  This currently pessimizes, so
     don't use yet - this is infrastructure so we can experiment with
     optimizing passes.  To enable it, pass ‘-Xuops’ or set
     ‘PYTHONUOPS=1’.  To get debug output, set ‘PYTHONUOPSDEBUG=N’ where
     ‘N’ is a debug level (0-4, where 0 is no debug output and 4 is
     excessively verbose).

   - gh-105775(116): *note LOAD_CLOSURE: 15e6. is now a pseudo-op.

   - gh-105730(117): Allow any callable other than type objects as the
     condition predicate in *note BaseExceptionGroup.split(): 15ba. and
     *note BaseExceptionGroup.subgroup(): 15b9.

   - gh-105979(118): Fix crash in ‘_imp.get_frozen_object()’ due to
     improper exception handling.

   - gh-106003(119): Add a new *note TO_BOOL: 15e7. instruction, which
     performs boolean conversions for *note POP_JUMP_IF_TRUE: 15e8,
     *note POP_JUMP_IF_FALSE: 15e9, and *note UNARY_NOT: 15ea. (which
     all expect exact *note bool: 40e. values now).  Also, modify the
     oparg of *note COMPARE_OP: 90d. to include an optional "boolean
     conversion" flag.

   - gh-98931(120): Ensure custom *note SyntaxError: 173. error messages
     are raised for invalid imports with multiple targets.  Patch by
     Pablo Galindo

   - gh-105724(121): Improve ‘assert’ error messages by providing exact
     error range.

   - gh-105908(122): Fixed bug where gh-99111(123) breaks future import
     ‘barry_as_FLUFL’ in the Python REPL.

   - gh-105840(124): Fix possible crashes when specializing function
     calls with too many ‘__defaults__’.

   - gh-105831(125): Fix an f-string bug, where using a debug expression
     (the ‘=’ sign) that appears in the last line of a file results to
     the debug buffer that holds the expression text being one character
     too small.

   - gh-105800(126): Correctly issue *note SyntaxWarning: 40c. in
     f-strings if invalid sequences are used.  Patch by Pablo Galindo

   - gh-105340(127): Include the comprehension iteration variable in
     ‘locals()’ inside a module- or class-scope comprehension.

   - gh-105331(128): Raise *note ValueError: 1e7. if the ‘delay’
     argument to *note asyncio.sleep(): a12. is a NaN (matching *note
     time.sleep(): 642.).

   - gh-105587(129): The runtime can't guarantee that immortal objects
     will not be mutated by Extensions.  Thus, this modifies
     _PyStaticObject_CheckRefcnt to warn instead of asserting.

   - gh-105564(130): Don't include artificil newlines in the ‘line’
     attribute of tokens in the APIs of the *note tokenize: e4. module.
     Patch by Pablo Galindo

   - gh-105549(131): Tokenize separately ‘NUMBER’ and ‘NAME’ tokens that
     are not ambiguous.  Patch by Pablo Galindo.

   - gh-105588(132): Fix an issue that could result in crashes when
     compiling malformed *note ast: 7. nodes.

   - gh-100987(133): Allow objects other than code objects as the
     "executable" in internal frames.  In the long term, this can help
     tools like Cython and PySpy interact more efficiently.  In the
     shorter term, it allows us to perform some optimizations more
     simply.

   - gh-105375(134): Fix bugs in the *note builtins: e. module where
     exceptions could end up being overwritten.

   - gh-105375(135): Fix bug in the compiler where an exception could
     end up being overwritten.

   - gh-105375(136): Improve error handling in
     ‘PyUnicode_BuildEncodingMap()’ where an exception could end up
     being overwritten.

   - gh-105486(137): Change the repr of ‘ParamSpec’ list of args in
     ‘types.GenericAlias’.

   - gh-105678(138): Break the ‘MAKE_FUNCTION’ instruction into two
     parts, ‘MAKE_FUNCTION’ which makes the function and
     ‘SET_FUNCTION_ATTRIBUTE’ which sets the attributes on the function.
     This makes the stack effect of ‘MAKE_FUNCTION’ regular to ease
     optimization and code generation.

   - gh-105435(139): Fix spurious newline character if file ends on a
     comment without a newline.  Patch by Pablo Galindo

   - gh-105390(140): Correctly raise *note tokenize.TokenError: 4e8.
     exceptions instead of *note SyntaxError: 173. for tokenize errors
     such as incomplete input.  Patch by Pablo Galindo

   - gh-105259(141): Don't include newline character for trailing
     ‘NEWLINE’ tokens emitted in the *note tokenize: e4. module.  Patch
     by Pablo Galindo

   - gh-104635(142): Eliminate redundant *note STORE_FAST: 15eb.
     instructions in the compiler.  Patch by Donghee Na and Carl Meyer.

   - gh-105324(143): Fix the main function of the *note tokenize: e4.
     module when reading from ‘sys.stdin’.  Patch by Pablo Galindo

   - gh-33092(144): Simplify and speed up interpreter for f-strings.
     Removes ‘FORMAT_VALUE’ opcode.  Add ‘CONVERT_VALUE’,
     ‘FORMAT_SIMPLE’ and ‘FORMAT_WITH_SPEC’ opcode.  Compiler emits more
     efficient sequence for each format expression.

   - gh-105229(145): Remove remaining two-codeunit superinstructions.
     All remaining superinstructions only take a single codeunit,
     simplifying instrumentation and quickening.

   - gh-105235(146): Prevent out-of-bounds memory access during
     ‘mmap.find()’ calls.

   - gh-98963(147): Restore the ability for a subclass of *note
     property: 180. to define ‘__slots__’ or otherwise be dict-less by
     ignoring failures to set a docstring on such a class.  This
     behavior had regressed in 3.12beta1.  An *note AttributeError: 2f6.
     where there had not previously been one was disruptive to existing
     code.

   - gh-104812(148): The "pending call" machinery now works for all
     interpreters, not just the main interpreter, and runs in all
     threads, not just the main thread.  Some calls are still only done
     in the main thread, ergo in the main interpreter.  This change does
     not affect signal handling nor the existing public C-API
     (‘Py_AddPendingCall()’), which both still only target the main
     thread.  The new functionality is meant strictly for internal use
     for now, since consequences of its use are not well understood yet
     outside some very restricted cases.  This change brings the
     capability in line with the intention when the state was made
     per-interpreter several years ago.

   - gh-105194(149): Do not escape with backslashes f-string format
     specifiers.  Patch by Pablo Galindo

   - gh-105229(150): Replace some dynamic superinstructions with single
     instruction equivalents.

   - gh-105162(151): Fixed bug in generator.close()/throw() where an
     inner iterator would be ignored when the outer iterator was
     instrumented.

   - gh-105164(152): Ensure annotations are set up correctly if the only
     annotation in a block is within a *note match: 7b1. block.  Patch
     by Jelle Zijlstra.

   - gh-105148(153): Make ‘_PyASTOptimizeState’ internal to ast_opt.c.
     Make ‘_PyAST_Optimize’ take two integers instead of a pointer to
     this struct.  This avoids the need to include pycore_compile.h in
     ast_opt.c.

   - gh-104799(154): Attributes of *note ast: 7. nodes that are lists
     now default to the empty list if omitted.  This means that some
     code that previously raised *note TypeError: 4dd. when the AST node
     was used will now proceed with the empty list instead.  Patch by
     Jelle Zijlstra.

   - gh-105111(155): Remove the old trashcan macros
     ‘Py_TRASHCAN_SAFE_BEGIN’ and ‘Py_TRASHCAN_SAFE_END’.  They should
     be replaced by the new macros ‘Py_TRASHCAN_BEGIN’ and
     ‘Py_TRASHCAN_END’.

   - gh-105035(156): Fix *note super(): 483. calls on types with custom
     *note tp_getattro: 15ec. implementation (e.g.  meta-types.)

   - gh-105017(157): Show CRLF lines in the tokenize string attribute in
     both NL and NEWLINE tokens.  Patch by Marta Gómez.

   - gh-105013(158): Fix handling of multiline parenthesized lambdas in
     *note inspect.getsource(): 14ca.  Patch by Pablo Galindo

   - gh-105017(159): Do not include an additional final ‘NL’ token when
     parsing files having CRLF lines.  Patch by Marta Gómez.

   - gh-104976(160): Ensure that trailing ‘DEDENT’ ‘tokenize.TokenInfo’
     objects emitted by the *note tokenize: e4. module are reported as
     in Python 3.11.  Patch by Pablo Galindo

   - gh-104972(161): Ensure that the ‘line’ attribute in
     ‘tokenize.TokenInfo’ objects in the *note tokenize: e4. module are
     always correct.  Patch by Pablo Galindo

   - gh-104955(162): Fix signature for the new *note
     __release_buffer__(): 15ed. slot.  Patch by Jelle Zijlstra.

   - gh-104690(163): Starting new threads and process creation through
     *note os.fork(): 17b. during interpreter shutdown (such as from
     *note atexit: 9. handlers) is no longer supported.  It can lead to
     race condition between the main Python runtime thread freeing
     thread states while internal *note threading: d6. routines are
     trying to allocate and use the state of just created threads.  Or
     forked children trying to use the mid-shutdown runtime and thread
     state in the child process.

   - gh-104879(164): Fix crash when accessing the ‘__module__’ attribute
     of type aliases defined outside a module.  Patch by Jelle Zijlstra.

   - gh-104825(165): Tokens emitted by the *note tokenize: e4. module do
     not include an implicit ‘\n’ character in the ‘line’ attribute
     anymore.  Patch by Pablo Galindo

   - gh-104770(166): If a generator returns a value upon being closed,
     the value is now returned by *note generator.close(): 15ee.

   - gh-89091(167): Raise *note RuntimeWarning: 1a3. for unawaited async
     generator methods like *note asend(): 87e, *note athrow(): 4a1. and
     *note aclose(): 87d.  Patch by Kumar Aditya.

   - gh-96663(168): Add a better, more introspect-able error message
     when setting attributes on classes without a ‘__dict__’ and no slot
     member for the attribute.

   - gh-93627(169): Update the Python pickle module implementation to
     match the C implementation of the pickle module.  For objects
     setting reduction methods like *note __reduce_ex__(): 15ef. or
     *note __reduce__(): 977. to ‘None’, pickling will result in a *note
     TypeError: 4dd.

   - gh-101006(170): Improve error handling when read *note marshal: 80.
     data.

   - gh-91095(171): Specializes calls to most Python classes.
     Specifically, any class that inherits from ‘object’, or another
     Python class, and does not override ‘__new__’.

     The specialized instruction does the following:

       1. Creates the object (by calling ‘object.__new__’)

       2. Pushes a shim frame to the frame stack (to cleanup after
          ‘__init__’)

       3. Pushes the frame for ‘__init__’ to the frame stack

     Speeds up the instantiation of most Python classes.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/110782

   (2) https://github.com/python/cpython/issues/110752

   (3) https://github.com/python/cpython/issues/110721

   (4) https://github.com/python/cpython/issues/110696

   (5) https://github.com/python/cpython/issues/104169

   (6) https://github.com/python/cpython/issues/110688

   (7) https://github.com/python/cpython/issues/104584

   (8) https://github.com/python/cpython/issues/110514

   (9) https://github.com/python/cpython/issues/110489

   (10) https://github.com/python/cpython/issues/110455

   (11) https://github.com/python/cpython/issues/110309

   (12) https://github.com/python/cpython/issues/110259

   (13) https://github.com/python/cpython/issues/110237

   (14) https://github.com/python/cpython/issues/110164

   (15) https://github.com/python/cpython/issues/109889

   (16) https://github.com/python/cpython/issues/109853

   (17) https://github.com/python/cpython/issues/109923

   (18) https://github.com/python/cpython/issues/105716

   (19) https://github.com/python/cpython/issues/109369

   (20) https://github.com/python/cpython/issues/109823

   (21) https://github.com/python/cpython/issues/109793

   (22) https://github.com/python/cpython/issues/109719

   (23) https://github.com/python/cpython/issues/109595

   (24) https://github.com/python/cpython/issues/109627

   (25) https://github.com/python/cpython/issues/109596

   (26) https://github.com/python/cpython/issues/109496

   (27) https://github.com/python/cpython/issues/107265

   (28) https://github.com/python/cpython/issues/109371

   (29) https://github.com/python/cpython/issues/105658

   (30) https://github.com/python/cpython/issues/109219

   (31) https://github.com/python/cpython/issues/109351

   (32) https://github.com/python/cpython/issues/109341

   (33) https://github.com/python/cpython/issues/109195

   (34) https://github.com/python/cpython/issues/109256

   (35) https://github.com/python/cpython/issues/109216

   (36) https://github.com/python/cpython/issues/109207

   (37) https://github.com/python/cpython/issues/109179

   (38) https://github.com/python/cpython/issues/109118

   (39) https://github.com/python/cpython/issues/109156

   (40) https://github.com/python/cpython/issues/109114

   (41) https://github.com/python/cpython/issues/105848

   (42) https://github.com/python/cpython/issues/109052

   (43) https://github.com/python/cpython/issues/109118

   (44) https://github.com/python/cpython/issues/88943

   (45) https://github.com/python/cpython/issues/108976

   (46) https://github.com/python/cpython/issues/108732

   (47) https://github.com/python/cpython/issues/108959

   (48) https://github.com/python/cpython/issues/104584

   (49) https://github.com/python/cpython/issues/108727

   (50) https://github.com/python/cpython/issues/108520

   (51) https://github.com/python/cpython/issues/108654

   (52) https://github.com/python/cpython/issues/108488

   (53) https://github.com/python/cpython/issues/108716

   (54) https://github.com/python/cpython/issues/108614

   (55) https://github.com/python/cpython/issues/108487

   (56) https://github.com/python/cpython/issues/106176

   (57) https://github.com/python/cpython/issues/105481

   (58) https://github.com/python/cpython/issues/107901

   (59) https://github.com/python/cpython/issues/108113

   (60) https://github.com/python/cpython/issues/107971

   (61) https://github.com/python/cpython/issues/107944

   (62) https://github.com/python/cpython/issues/108390

   (63) https://github.com/python/cpython/issues/108035

   (64) https://github.com/python/cpython/issues/91051

   (65) https://github.com/python/cpython/issues/106581

   (66) https://github.com/python/cpython/issues/107526

   (67) https://github.com/python/cpython/issues/84805

   (68) https://github.com/python/cpython/issues/107758

   (69) https://github.com/python/cpython/issues/107659

   (70) https://github.com/python/cpython/issues/105848

   (71) https://github.com/python/cpython/issues/107674

   (72) https://github.com/python/cpython/issues/107724

   (73) https://github.com/python/cpython/issues/84436

   (74) https://github.com/python/cpython/issues/107596

   (75) https://github.com/python/cpython/issues/107080

   (76) https://github.com/python/cpython/issues/107557

   (77) https://github.com/python/cpython/issues/106608

   (78) https://github.com/python/cpython/issues/100964

   (79) https://github.com/python/cpython/issues/107455

   (80) https://github.com/python/cpython/issues/107263

   (81) https://github.com/python/cpython/issues/104584

   (82) https://github.com/python/cpython/issues/104432

   (83) https://github.com/python/cpython/issues/106078

   (84) https://peps.python.org/pep-0687/

   (85) https://github.com/python/cpython/issues/106898

   (86) https://github.com/python/cpython/issues/106895

   (87) https://github.com/python/cpython/issues/106897

   (88) https://github.com/python/cpython/issues/77377

   (89) https://github.com/python/cpython/issues/106931

   (90) https://github.com/python/cpython/issues/104621

   (91) https://github.com/python/cpython/issues/107122

   (92) https://github.com/python/cpython/issues/107122

   (93) https://github.com/python/cpython/issues/107015

   (94) https://github.com/python/cpython/issues/106917

   (95) https://github.com/python/cpython/issues/105699

   (96) https://github.com/python/cpython/issues/105699

   (97) https://github.com/python/cpython/issues/106908

   (98) https://github.com/python/cpython/issues/106092

   (99) https://github.com/python/cpython/issues/106485

   (100) https://github.com/python/cpython/issues/106719

   (101) https://github.com/python/cpython/issues/106723

   (102) https://github.com/python/cpython/issues/104909

   (103) https://github.com/python/cpython/issues/104909

   (104) https://github.com/python/cpython/issues/106597

   (105) https://github.com/python/cpython/issues/106487

   (106) https://github.com/python/cpython/issues/96844

   (107) https://github.com/python/cpython/issues/81283

   (108) https://github.com/python/cpython/issues/106396

   (109) https://github.com/python/cpython/issues/100288

   (110) https://github.com/python/cpython/issues/106008

   (111) https://github.com/python/cpython/issues/106145

   (112) https://github.com/python/cpython/issues/106213

   (113) https://github.com/python/cpython/issues/106182

   (114) https://github.com/python/cpython/issues/106210

   (115) https://github.com/python/cpython/issues/104584

   (116) https://github.com/python/cpython/issues/105775

   (117) https://github.com/python/cpython/issues/105730

   (118) https://github.com/python/cpython/issues/105979

   (119) https://github.com/python/cpython/issues/106003

   (120) https://github.com/python/cpython/issues/98931

   (121) https://github.com/python/cpython/issues/105724

   (122) https://github.com/python/cpython/issues/105908

   (123) https://github.com/python/cpython/issues/99111

   (124) https://github.com/python/cpython/issues/105840

   (125) https://github.com/python/cpython/issues/105831

   (126) https://github.com/python/cpython/issues/105800

   (127) https://github.com/python/cpython/issues/105340

   (128) https://github.com/python/cpython/issues/105331

   (129) https://github.com/python/cpython/issues/105587

   (130) https://github.com/python/cpython/issues/105564

   (131) https://github.com/python/cpython/issues/105549

   (132) https://github.com/python/cpython/issues/105588

   (133) https://github.com/python/cpython/issues/100987

   (134) https://github.com/python/cpython/issues/105375

   (135) https://github.com/python/cpython/issues/105375

   (136) https://github.com/python/cpython/issues/105375

   (137) https://github.com/python/cpython/issues/105486

   (138) https://github.com/python/cpython/issues/105678

   (139) https://github.com/python/cpython/issues/105435

   (140) https://github.com/python/cpython/issues/105390

   (141) https://github.com/python/cpython/issues/105259

   (142) https://github.com/python/cpython/issues/104635

   (143) https://github.com/python/cpython/issues/105324

   (144) https://github.com/python/cpython/issues/33092

   (145) https://github.com/python/cpython/issues/105229

   (146) https://github.com/python/cpython/issues/105235

   (147) https://github.com/python/cpython/issues/98963

   (148) https://github.com/python/cpython/issues/104812

   (149) https://github.com/python/cpython/issues/105194

   (150) https://github.com/python/cpython/issues/105229

   (151) https://github.com/python/cpython/issues/105162

   (152) https://github.com/python/cpython/issues/105164

   (153) https://github.com/python/cpython/issues/105148

   (154) https://github.com/python/cpython/issues/104799

   (155) https://github.com/python/cpython/issues/105111

   (156) https://github.com/python/cpython/issues/105035

   (157) https://github.com/python/cpython/issues/105017

   (158) https://github.com/python/cpython/issues/105013

   (159) https://github.com/python/cpython/issues/105017

   (160) https://github.com/python/cpython/issues/104976

   (161) https://github.com/python/cpython/issues/104972

   (162) https://github.com/python/cpython/issues/104955

   (163) https://github.com/python/cpython/issues/104690

   (164) https://github.com/python/cpython/issues/104879

   (165) https://github.com/python/cpython/issues/104825

   (166) https://github.com/python/cpython/issues/104770

   (167) https://github.com/python/cpython/issues/89091

   (168) https://github.com/python/cpython/issues/96663

   (169) https://github.com/python/cpython/issues/93627

   (170) https://github.com/python/cpython/issues/101006

   (171) https://github.com/python/cpython/issues/91095


File: python.info,  Node: Library<12>,  Next: Documentation<7>,  Prev: Core and Builtins<13>,  Up: Python 3 13 0 alpha 1

1.23.13.3 Library
.................

   - gh-110786(1): *note sysconfig: c5.'s CLI now ignores *note
     BrokenPipeError: fff, making it exit normally if its output is
     being piped and the pipe closes.

   - gh-103480(2): The *note sysconfig: c5. module is now a package,
     instead of a single-file module.

   - gh-110733(3): Micro-optimization: Avoid calling ‘min()’, ‘max()’ in
     ‘BaseEventLoop._run_once()’.

   - gh-94597(4): Added *note asyncio.EventLoop: 15f1. for use with the
     *note asyncio.run(): 423. 'loop_factory' kwarg to avoid calling the
     asyncio policy system.

   - gh-110682(5): *note runtime-checkable protocols: 3e9. used to
     consider ‘__match_args__’ a protocol member in ‘__instancecheck__’
     if it was present on the protocol.  Now, this attribute is ignored
     if it is present.

   - gh-110488(6): Fix a couple of issues in *note
     pathlib.PurePath.with_name(): 15f2.: a single dot was incorrectly
     considered a valid name, and in ‘PureWindowsPath’, a name with an
     NTFS alternate data stream, like ‘a:b’, was incorrectly considered
     invalid.

   - gh-110590(7): Fix a bug in ‘_sre.compile()’ where *note TypeError:
     4dd. would be overwritten by *note OverflowError: 825. when the
     'code' argument was a list of non-ints.

   - gh-65052(8): Prevent *note pdb: 94. from crashing when trying to
     display undisplayable objects

   - gh-110519(9): Deprecation warning about non-integer number in *note
     gettext: 59. now always refers to the line in the user code where
     gettext function or method is used.  Previously it could refer to a
     line in ‘gettext’ code.

   - gh-89902(10): Deprecate non-standard format specifier "N" for *note
     decimal.Decimal: 27c.  It was not documented and only supported in
     the C implementation.

   - gh-110378(11): *note contextmanager(): 119a. and *note
     asynccontextmanager(): ace. context managers now close an invalid
     underlying generator object that yields more then one value.

   - gh-106670(12): In *note pdb: 94, set convenience variable
     ‘$_exception’ for post mortem debugging.

   - gh-110365(13): Fix *note termios.tcsetattr(): 15f3. bug that was
     overwriting existing errors during parsing integers from ‘term’
     list.

   - gh-109653(14): Slightly improve the import time of several
     standard-library modules by deferring imports of *note warnings:
     fa. within those modules.  Patch by Alex Waygood.

   - gh-110273(15): *note dataclasses.replace(): 15f4. now raises
     TypeError instead of ValueError if specify keyword argument for a
     field declared with init=False or miss keyword argument for
     required InitVar field.

   - gh-110249(16): Add ‘--inline-caches’ flag to ‘dis’ command line.

   - gh-109653(17): Fix a Python 3.12 regression in the import time of
     *note random: a6.  Patch by Alex Waygood.

   - gh-110222(18): Add support of struct sequence objects in *note
     copy.replace(): 136.  Patched by Xuehai Pan.

   - gh-109649(19): *note multiprocessing: 86, *note concurrent.futures:
     1a, *note compileall: 19.: Replace *note os.cpu_count(): 1a8. with
     *note os.process_cpu_count(): 1a7. to select the default number of
     worker threads and processes.  Get the CPU affinity if supported.
     Patch by Victor Stinner.

   - gh-110150(20): Fix base case handling in statistics.quantiles.  Now
     allows a single data point.

   - gh-110036(21): On Windows, multiprocessing ‘Popen.terminate()’ now
     catches *note PermissionError: ce9. and get the process exit code.
     If the process is still running, raise again the *note
     PermissionError: ce9.  Otherwise, the process terminated as
     expected: store its exit code.  Patch by Victor Stinner.

   - gh-110038(22): Fixed an issue that caused ‘KqueueSelector.select()’
     to not return all the ready events in some cases when a file
     descriptor is registered for both read and write.

   - gh-110045(23): Update the *note symtable: c2. module to support the
     new scopes introduced by PEP 695(24).

   - gh-88402(25): Add new variables to *note
     sysconfig.get_config_vars(): fcf. on Windows: ‘LIBRARY’,
     ‘LDLIBRARY’, ‘LIBDIR’, ‘SOABI’, and ‘Py_NOGIL’.

   - gh-109631(26): *note re: a7. functions such as *note re.findall():
     fcd, *note re.split(): 282, *note re.search(): 11c4. and *note
     re.sub(): 283. which perform short repeated matches can now be
     interrupted by user.

   - gh-109653(27): Reduce the import time of *note email.utils: 47. by
     around 43%.  This results in the import time of *note
     email.message: 3b. falling by around 18%, which in turn reduces the
     import time of *note importlib.metadata: 6e. by around 6%.  Patch
     by Alex Waygood.

   - gh-109818(28): Fix *note reprlib.recursive_repr(): 118b. not
     copying ‘__type_params__’ from decorated function.

   - gh-109047(29): *note concurrent.futures: 1a.: The 'executor manager
     thread' now catches exceptions when adding an item to the 'call
     queue'.  During Python finalization, creating a new thread can now
     raise *note RuntimeError: 179.  Catch the exception and call
     ‘terminate_broken()’ in this case.  Patch by Victor Stinner.

   - gh-109782(30): Ensure the signature of *note os.path.isdir(): 9b4.
     is identical on all platforms.  Patch by Amin Alaee.

   - gh-109653(31): Improve import time of *note functools: 55. by
     around 13%.  Patch by Alex Waygood.

   - gh-109590(32): *note shutil.which(): 45b. will prefer files with an
     extension in ‘PATHEXT’ if the given mode includes ‘os.X_OK’ on
     win32.  If no ‘PATHEXT’ match is found, a file without an extension
     in ‘PATHEXT’ can be returned.  This change will have *note
     shutil.which(): 45b. act more similarly to previous behavior in
     Python 3.11.

   - gh-109653(33): Reduce the import time of *note enum: 4c. by over
     50%.  Patch by Alex Waygood.

   - gh-109593(34): Avoid deadlocking on a reentrant call to the
     multiprocessing resource tracker.  Such a reentrant call, though
     unlikely, can happen if a GC pass invokes the finalizer for a
     multiprocessing object such as SemLock.

   - gh-109653(35): Reduce the import time of *note typing: ed. by
     around a third.  Patch by Alex Waygood.

   - gh-109649(36): Add *note os.process_cpu_count(): 1a7. function to
     get the number of logical CPUs usable by the calling thread of the
     current process.  Patch by Victor Stinner.

   - gh-74481(37): Add ‘set_error_mode’ related constants in ‘msvcrt’
     module in Python debug build.

   - gh-109613(38): Fix *note os.stat(): 448. and *note
     os.DirEntry.stat(): 15f5.: check for exceptions.  Previously, on
     Python built in debug mode, these functions could trigger a fatal
     Python error (and abort the process) when a function succeeded with
     an exception set.  Patch by Victor Stinner.

   - gh-109599(39): Expose the type of PyCapsule objects as
     ‘types.CapsuleType’.

   - gh-109109(40): You can now get the raw TLS certificate chains from
     TLS connections via *note ssl.SSLSocket.get_verified_chain(): 14cf.
     and *note ssl.SSLSocket.get_unverified_chain(): 14d0. methods.

     Contributed by Mateusz Nowak.

   - gh-109559(41): Update *note unicodedata: ee. database to Unicode
     15.1.0.

   - gh-109543(42): Remove unnecessary *note hasattr(): 479. check
     during *note typing.TypedDict: 146. creation.

   - gh-109495(43): Remove unnecessary extra ‘__slots__’ in *note
     datetime: 1b0.'s pure python implementation to reduce memory size,
     as they are defined in the superclass.  Patch by James Hilton-Balfe

   - gh-109461(44): *note logging: 7b.: Use a context manager for lock
     acquisition.

   - gh-109096(45): *note http.server.CGIHTTPRequestHandler: 281. has
     been deprecated for removal in 3.15.  Its design is old and the web
     world has long since moved beyond CGI.

   - gh-109409(46): Fix error when it was possible to inherit a frozen
     dataclass from multiple parents some of which were possibly not
     frozen.

   - gh-109375(47): The *note pdb: 94. ‘alias’ command now prevents
     registering aliases without arguments.

   - gh-109319(48): Deprecate the ‘dis.HAVE_ARGUMENT’ field in favour of
     ‘dis.hasarg’.

   - gh-107219(49): Fix a race condition in ‘concurrent.futures’.  When
     a process in the process pool was terminated abruptly (while the
     future was running or pending), close the connection write end.  If
     the call queue is blocked on sending bytes to a worker process,
     closing the connection write end interrupts the send, so the queue
     can be closed.  Patch by Victor Stinner.

   - gh-66143(50): The *note codecs.CodecInfo: 15f6. object has been
     made copyable and pickleable.  Patched by Robert Lehmann and Furkan
     Onder.

   - gh-109187(51): *note pathlib.Path.resolve(): 15f7. now treats
     symlink loops like other errors: in strict mode, *note OSError:
     350. is raised, and in non-strict mode, no exception is raised.

   - gh-50644(52): Attempts to pickle or create a shallow or deep copy
     of *note codecs: 14. streams now raise a TypeError.  Previously,
     copying failed with a RecursionError, while pickling produced wrong
     results that eventually caused unpickling to fail with a
     RecursionError.

   - gh-109174(53): Add support of *note types.SimpleNamespace: 1b5. in
     *note copy.replace(): 136.

   - gh-109164(54): *note pdb: 94.: Replace *note getopt: 57. with *note
     argparse: 5. for parsing command line arguments.

   - gh-109151(55): Enable ‘readline’ editing features in the *note
     sqlite3 command-line interface: 3e7. (‘python -m sqlite3’).

   - gh-108987(56): Fix *note _thread.start_new_thread(): 17a. race
     condition.  If a thread is created during Python finalization, the
     newly spawned thread now exits immediately instead of trying to
     access freed memory and lead to a crash.  Patch by Victor Stinner.

   - gh-108682(57): Enum: require ‘names=()’ or ‘type=...’ to create an
     empty enum using the functional syntax.

   - gh-109033(58): Exceptions raised by os.utime builtin function now
     include the related filename

   - gh-108843(59): Fix an issue in *note ast.unparse(): 88a. when
     unparsing f-strings containing many quote types.

   - gh-108469(60): *note ast.unparse(): 88a. now supports new *note
     f-string: 3dc. syntax introduced in Python 3.12.  Note that the
     *note f-string: 3dc. quotes are reselected for simplicity under the
     new syntax.  (Patch by Steven Sun)

   - gh-108751(61): Add *note copy.replace(): 136. function which allows
     to create a modified copy of an object.  It supports named tuples,
     dataclasses, and many other objects.

   - gh-108682(62): Enum: raise *note TypeError: 4dd. if
     ‘super().__new__()’ is called from a custom ‘__new__’.

   - gh-108278(63): Deprecate passing the callback callable by keyword
     for the following *note sqlite3.Connection: 22a. APIs:

        * *note set_authorizer(): 28b.

        * *note set_progress_handler(): 28c.

        * *note set_trace_callback(): 28d.

     The affected parameters will become positional-only in Python 3.15.

     Patch by Erlend E. Aasland.

   - gh-105829(64): Fix concurrent.futures.ProcessPoolExecutor deadlock

   - gh-108295(65): Fix crashes related to use of weakrefs on *note
     typing.TypeVar: 141.

   - gh-108463(66): Make expressions/statements work as expected in pdb

   - gh-108277(67): Add *note os.timerfd_create(): 1f6, *note
     os.timerfd_settime(): 1f7, *note os.timerfd_gettime(): 1f9, *note
     os.timerfd_settime_ns(): 1f8, and *note os.timerfd_gettime_ns():
     1fa. to provide a low level interface for Linux's timer
     notification file descriptor.

   - gh-107811(68): *note tarfile: c8.: extraction of members with
     overly large UID or GID (e.g.  on an OS with 32-bit ‘id_t’) now
     fails in the same way as failing to set the ID.

   - gh-64662(69): Fix support for virtual tables in *note
     sqlite3.Connection.iterdump(): 22c.  Patch by Aviv Palivoda.

   - gh-108111(70): Fix a regression introduced in gh-101251(71) for
     3.12, resulting in an incorrect offset calculation in
     ‘gzip.GzipFile.seek()’.

   - gh-108294(72): *note time.sleep(): 642. now raises an auditing
     event.

   - gh-108278(73): Deprecate passing name, number of arguments, and the
     callable as keyword arguments, for the following *note
     sqlite3.Connection: 22a. APIs:

        * *note create_function(): 289.

        * *note create_aggregate(): 28a.

     The affected parameters will become positional-only in Python 3.15.

     Patch by Erlend E. Aasland.

   - gh-108322(74): Speed-up NormalDist.samples() by using the inverse
     CDF method instead of calling random.gauss().

   - gh-83417(75): Add the ability for venv to create a ‘.gitignore’
     file which causes the created environment to be ignored by Git.  It
     is on by default when venv is called via its CLI.

   - gh-105736(76): Harmonized the pure Python version of *note
     OrderedDict: 57f. with the C version.  Now, both versions set up
     their internal state in ‘__new__’.  Formerly, the pure Python
     version did the set up in ‘__init__’.

   - gh-108083(77): Fix bugs in the constructor of *note
     sqlite3.Connection: 22a. and *note sqlite3.Connection.close(): 22b.
     where exceptions could be leaked.  Patch by Erlend E. Aasland.

   - gh-107932(78): Fix ‘dis’ module to properly report and display
     bytecode that do not have source lines.

   - gh-105539(79): *note sqlite3: ba. now emits an *note
     ResourceWarning: 229. if a *note sqlite3.Connection: 22a. object is
     not ‘closed’ explicitly.  Patch by Erlend E. Aasland.

   - gh-107995(80): The ‘__module__’ attribute on instances of *note
     functools.cached_property: 4e7. is now set to the name of the
     module in which the cached_property is defined, rather than
     "functools".  This means that doctests in ‘cached_property’
     docstrings are now properly collected by the *note doctest: 31.
     module.  Patch by Tyler Smart.

   - gh-107963(81): Fix *note multiprocessing.set_forkserver_preload():
     15f8. to check the given list of modules names.  Patch by Donghee
     Na.

   - gh-106242(82): Fixes *note os.path.normpath(): 12ae. to handle
     embedded null characters without truncating the path.

   - gh-81555(83): *note xml.dom.minidom: 109. now only quotes ‘"’ in
     attributes.

   - gh-50002(84): *note xml.dom.minidom: 109. now preserves whitespaces
     in attributes.

   - gh-93057(85): Passing more than one positional argument to *note
     sqlite3.connect(): 288. and the *note sqlite3.Connection: 22a.
     constructor is deprecated.  The remaining parameters will become
     keyword-only in Python 3.15.  Patch by Erlend E. Aasland.

   - gh-76913(86): Add 'merge_extra' parameter/feature to *note
     logging.LoggerAdapter: 1288.

   - gh-107913(87): Fix possible losses of ‘errno’ and ‘winerror’ values
     in *note OSError: 350. exceptions if they were cleared or modified
     by the cleanup code before creating the exception object.

   - gh-107845(88): *note tarfile.data_filter(): 15f9. now takes the
     location of symlinks into account when determining their target, so
     it will no longer reject some valid tarballs with
     ‘LinkOutsideDestinationError’.

   - gh-107812(89): Extend socket's netlink support to the FreeBSD
     platform.

   - gh-107805(90): Fix signatures of module-level generated functions
     in *note turtle: ea.

   - gh-107782(91): *note pydoc: a3. is now able to show signatures
     which are not representable in Python, e.g.  for ‘getattr’ and
     ‘dict.pop’.

   - gh-56166(92): Deprecate passing optional arguments 'maxsplit',
     'count' and 'flags' in module-level functions *note re.split():
     282, *note re.sub(): 283. and *note re.subn(): 284. as positional.
     They should only be passed by keyword.

   - gh-107710(93): Speed up *note logging.getHandlerNames(): 15fa.

   - gh-107715(94): Fix *note doctest.DocTestFinder.find(): 15fb. in
     presence of class names with special characters.  Patch by Gertjan
     van Zwieten.

   - gh-100814(95): Passing a callable object as an option value to a
     Tkinter image now raises the expected TclError instead of an
     AttributeError.

   - gh-72684(96): Add *note tkinter: d9. widget methods:
     ‘tk_busy_hold()’, ‘tk_busy_configure()’, ‘tk_busy_cget()’,
     ‘tk_busy_forget()’, ‘tk_busy_current()’, and ‘tk_busy_status()’.

   - gh-106684(97): Raise *note ResourceWarning: 229. when *note
     asyncio.StreamWriter: 15fc. is not closed leading to memory leaks.
     Patch by Kumar Aditya.

   - gh-107465(98): Add *note pathlib.Path.from_uri(): 20f. classmethod.

   - gh-107077(99): Seems that in some conditions, OpenSSL will return
     ‘SSL_ERROR_SYSCALL’ instead of ‘SSL_ERROR_SSL’ when a certification
     verification has failed, but the error parameters will still
     contain ‘ERR_LIB_SSL’ and ‘SSL_R_CERTIFICATE_VERIFY_FAILED’.  We
     are now detecting this situation and raising the appropriate
     ‘ssl.SSLCertVerificationError’.  Patch by Pablo Galindo

   - gh-107576(100): Fix *note types.get_original_bases(): 475. to only
     return ‘__orig_bases__’ if it is present on ‘cls’ directly.  Patch
     by James Hilton-Balfe.

   - gh-105481(101): Remove ‘opcode.is_pseudo’,
     ‘opcode.MIN_PSEUDO_OPCODE’ and ‘opcode.MAX_PSEUDO_OPCODE’, which
     were added in 3.12, were never documented and were not intended to
     be used externally.

   - gh-105481(102): ‘opcode.ENABLE_SPECIALIZATION’ (which was added in
     3.12 but never documented or intended for external usage) is moved
     to ‘_opcode.ENABLE_SPECIALIZATION’ where tests can access it.

   - gh-107396(103): tarfiles; Fixed use before assignment of
     self.exception for gzip decompression

   - gh-107409(104): Set ‘__wrapped__’ attribute in *note
     reprlib.recursive_repr(): 118b.

   - gh-107406(105): Implement new ‘__repr__()’ method for *note
     struct.Struct: 15a9.  Now it returns ‘Struct(<format repr>)’.

   - gh-107369(106): Optimize *note textwrap.indent(): 25b.  It is ~30%
     faster for large input.  Patch by Inada Naoki.

   - gh-78722(107): Fix issue where *note pathlib.Path.iterdir(): 1525.
     did not raise *note OSError: 350. until iterated.

   - gh-105578(108): Deprecate *note typing.AnyStr: 293. in favor of the
     new Type Parameter syntax.  See PEP 695.

   - gh-62519(109): Make *note gettext.pgettext(): 999. search plural
     definitions when translation is not found.

   - gh-107089(110): Shelves opened with *note shelve.open(): 15fd. have
     a much faster ‘clear()’ method.  Patch by James Cave.

   - gh-82500(111): Fix overflow on 32-bit systems with *note asyncio:
     8. *note os.sendfile(): ab2. implementation.

   - gh-83006(112): Document behavior of *note shutil.disk_usage():
     10c6. for non-mounted filesystems on Unix.

   - gh-65495(113): Use lowercase ‘mail from’ and ‘rcpt to’ in
     ‘smptlib.SMTP’.

   - gh-106186(114): Do not report ‘MultipartInvariantViolationDefect’
     defect when the *note email.parser.Parser: 1136. class is used to
     parse emails with ‘headersonly=True’.

   - gh-105002(115): Fix invalid result from ‘PurePath.relative_to()’
     method when attempting to walk a "‘..’" segment in 'other' with
     'walk_up' enabled.  A *note ValueError: 1e7. exception is now
     raised in this case.

   - gh-106739(116): Add the ‘rtype_cache’ to the warning message (as an
     addition to the type of leaked objects and the number of leaked
     objects already included in the message) to make debugging leaked
     objects easier when the multiprocessing resource tracker process
     finds leaked objects at shutdown.  This helps more quickly identify
     what was leaked and/or why the leaked object was not properly
     cleaned up.

   - gh-106751(117): Optimize ‘SelectSelector.select()’ for many
     iteration case.  Patch By Donghee Na.

   - gh-106751(118): Optimize ‘_PollLikeSelector.select()’ for many
     iteration case.

   - gh-106751(119): Optimize ‘KqueueSelector.select()’ for many
     iteration case.  Patch By Donghee Na.

   - gh-106831(120): Fix potential missing ‘NULL’ check of
     ‘d2i_SSL_SESSION’ result in ‘_ssl.c’.

   - gh-105481(121): The various opcode lists in the *note dis: 30.
     module are now generated from bytecodes.c instead of explicitly
     constructed in opcode.py.

   - gh-106727(122): Make *note inspect.getsource(): 14ca. smarter for
     class for same name definitions

   - gh-106789(123): Remove import of *note pprint: 9c. from *note
     sysconfig: c5.

   - gh-105726(124): Added ‘__slots__’ to *note
     contextlib.AbstractContextManager: c34. and *note
     contextlib.AbstractAsyncContextManager: acf. so that child classes
     can use ‘__slots__’.

   - gh-106774(125): Update the bundled copy of pip to version 23.2.1.

   - gh-106751(126): *note selectors: b0.: Optimize
     ‘EpollSelector.select()’ code by moving some code outside of the
     loop.

   - gh-106752(127): Fixed several bugs in zipfile.Path, including: in
     ‘zipfile.Path.match()’, Windows separators are no longer honored
     (and never were meant to be); Fixed
     ‘name’/‘suffix’/‘suffixes’/‘stem’ operations when no filename is
     present and the Path is not at the root of the zipfile; Reworked
     glob for performance and more correct matching behavior.

   - gh-105293(128): Remove call to ‘SSL_CTX_set_session_id_context’
     during client side context creation in the *note ssl: bb. module.

   - gh-106734(129): Disable tab completion in multiline mode of *note
     pdb: 94.

   - gh-105481(130): Expose opcode metadata through ‘_opcode’.

   - gh-106670(131): Add the new ‘exceptions’ command to the Pdb
     debugger.  It makes it possible to move between chained exceptions
     when using post mortem debugging.

   - gh-106602(132): Add __copy__ and __deepcopy__ in *note enum: 4c.

   - gh-106664(133): *note selectors: b0.: Add ‘_SelectorMapping.get()’
     method and optimize ‘_SelectorMapping.__getitem__()’.

   - gh-106628(134): Speed up parsing of emails by about 20% by not
     compiling a new regular expression for every single email.

   - gh-89427(135): Set the environment variable ‘VIRTUAL_ENV_PROMPT’ at
     *note venv: f9. activation, even when ‘VIRTUAL_ENV_DISABLE_PROMPT’
     is set.

   - gh-106530(136): Revert a change to *note colorsys.rgb_to_hls():
     15fe. that caused division by zero for certain almost-white inputs.
     Patch by Terry Jan Reedy.

   - gh-106584(137): Fix exit code for ‘unittest’ if all tests are
     skipped.  Patch by Egor Eliseev.

   - gh-106566(138): Optimize ‘(?!)’ (pattern which always fails) in
     regular expressions.

   - gh-106554(139): *note selectors: b0.: Reduce Selector overhead by
     using a ‘dict.get()’ to lookup file descriptors.

   - gh-106558(140): Remove ref cycle in callers of ‘convert_to_error()’
     by deleting ‘result’ from scope in a ‘finally’ block.

   - gh-100502(141): Add ‘pathlib.PurePath.pathmod’ class attribute that
     stores the implementation of *note os.path: 92. used for low-level
     path operations: either ‘posixpath’ or ‘ntpath’.

   - gh-106527(142): Reduce overhead to add and remove *note asyncio: 8.
     readers and writers.

   - gh-106524(143): Fix crash in ‘_sre.template()’ with templates
     containing invalid group indices.

   - gh-106531(144): Removed ‘_legacy’ and the names it provided from
     ‘importlib.resources’: ‘Resource’, ‘contents’, ‘is_resource’,
     ‘open_binary’, ‘open_text’, ‘path’, ‘read_binary’, and ‘read_text’.

   - gh-106052(145): *note re: a7. module: fix the matching of
     possessive quantifiers in the case of a subpattern containing
     backtracking.

   - gh-106510(146): Improve debug output for atomic groups in regular
     expressions.

   - gh-106503(147): Fix ref cycle in ‘asyncio._SelectorSocketTransport’
     by removing ‘_write_ready’ in ‘close’.

   - gh-105497(148): Fix flag mask inversion when unnamed flags exist.

   - gh-90876(149): Prevent ‘multiprocessing.spawn’ from failing to
     'import' in environments where ‘sys.executable’ is ‘None’.  This
     regressed in 3.11 with the addition of support for path-like
     objects in multiprocessing.

   - gh-106403(150): Instances of *note typing.TypeVar: 141, *note
     typing.ParamSpec: 142, *note typing.ParamSpecArgs: 76a, *note
     typing.ParamSpecKwargs: 76b, and *note typing.TypeVarTuple: 143.
     once again support weak references, fixing a regression introduced
     in Python 3.12.0 beta 1.  Patch by Jelle Zijlstra.

   - gh-89812(151): Add private ‘pathlib._PathBase’ class, which
     provides experimental support for virtual filesystems, and may be
     made public in a future version of Python.

   - gh-106292(152): Check for an instance-dict cached value in the
     ‘__get__()’ method of *note functools.cached_property(): 4e7.  This
     better matches the pre-3.12 behavior and improves compatibility for
     users subclassing *note functools.cached_property(): 4e7. and
     adding a ‘__set__()’ method.

   - gh-106350(153): Detect possible memory allocation failure in the
     libtommath function ‘mp_init()’ used by the ‘_tkinter’ module.

   - gh-106330(154): Fix incorrect matching of empty paths in *note
     pathlib.PurePath.match(): 454.  This bug was introduced in Python
     3.12.0 beta 1.

   - gh-106309(155): Deprecate *note typing.no_type_check_decorator():
     292.  No major type checker ever added support for this decorator.
     Patch by Alex Waygood.

   - gh-102541(156): Make ‘pydoc.doc()’ catch bad module *note
     ImportError: 352. when output stream is not ‘None’.

   - gh-106263(157): Fix crash when calling ‘repr’ with a manually
     constructed SignalDict object.  Patch by Charlie Zhao.

   - gh-106236(158): Replace ‘assert’ statements with ‘raise
     RuntimeError’ in *note threading: d6, so that ‘_DummyThread’ cannot
     be joined even with ‘-OO’.

   - gh-106238(159): Fix rare concurrency bug in lock acquisition by the
     logging package.

   - gh-106152(160): Added PY_THROW event hook for *note cProfile: 20.
     for generators

   - gh-106075(161): Added ‘asyncio.taskgroups.__all__’ to
     ‘asyncio.__all__’ for export in star imports.

   - gh-104527(162): Zipapp will now skip over appending an archive to
     itself.

   - gh-106046(163): Improve the error message from *note os.fspath():
     bfa. if called on an object where ‘__fspath__’ is set to ‘None’.
     Patch by Alex Waygood.

   - gh-105987(164): Fix crash due to improper reference counting in
     *note asyncio: 8. eager task factory internal routines.

   - gh-105974(165): Fix bug where a *note typing.Protocol: 249. class
     that had one or more non-callable members would raise *note
     TypeError: 4dd. when *note issubclass(): 765. was called against
     it, even if it defined a custom ‘__subclasshook__’ method.  The
     behaviour in Python 3.11 and lower - which has now been restored -
     was not to raise *note TypeError: 4dd. in these situations if a
     custom ‘__subclasshook__’ method was defined.  Patch by Alex
     Waygood.

   - gh-96145(166): Reverted addition of ‘json.AttrDict’.

   - gh-89812(167): Add *note pathlib.UnsupportedOperation: 20c, which
     is raised instead of *note NotImplementedError: 20d. when a path
     operation isn't supported.

   - gh-105808(168): Fix a regression introduced in gh-101251(169) for
     3.12, causing ‘gzip.GzipFile.flush()’ to not flush the compressor
     (nor pass along the ‘zip_mode’ argument).

   - gh-105481(170): *note stack_effect(): ed5. no longer raises an
     exception if an ‘oparg’ is provided for an ‘opcode’ that doesn't
     use its arg, or when it is not provided for an ‘opcode’ that does
     use it.  In the latter case, the stack effect is returned for
     ‘oparg=0’.

   - gh-104799(171): Enable *note ast.unparse(): 88a. to unparse
     function and class definitions created without the new
     ‘type_params’ field from PEP 695(172).  Patch by Jelle Zijlstra.

   - gh-105793(173): Add 'follow_symlinks' keyword-only argument to
     *note pathlib.Path.is_dir(): 215. and *note is_file(): 214,
     defaulting to ‘True’.

   - gh-105570(174): Deprecate two methods of creating *note
     typing.TypedDict: 146. classes with 0 fields using the functional
     syntax: ‘TD = TypedDict("TD")’ and ‘TD = TypedDict("TD", None)’.
     Both will be disallowed in Python 3.15.  To create a ‘TypedDict’
     class with 0 fields, either use ‘class TD(TypedDict): pass’ or ‘TD
     = TypedDict("TD", {})’.

   - gh-105745(175): Fix ‘webbrowser.Konqueror.open’ method.

   - gh-105733(176): *note ctypes: 22.: Deprecate undocumented
     ‘ctypes.SetPointerType()’ and ‘ctypes.ARRAY()’ functions.  Patch by
     Victor Stinner.

   - gh-105687(177): Remove deprecated ‘re.template’, ‘re.T’,
     ‘re.TEMPLATE’, ‘sre_constans.SRE_FLAG_TEMPLATE’.

   - gh-105684(178): Supporting *note asyncio.Task.set_name(): 981. is
     now mandatory for third party task implementations.  The
     undocumented ‘_set_task_name()’ function (deprecated since 3.8) has
     been removed.  Patch by Kumar Aditya.

   - gh-105375(179): Fix a bug in ‘_Unpickler_SetInputStream()’ where an
     exception could end up being overwritten in case of failure.

   - gh-105626(180): Change the default return value of *note
     http.client.HTTPConnection.get_proxy_response_headers(): 15ff. to
     be ‘None’ and not ‘{}’.

   - gh-105375(181): Fix bugs in *note sys: c3. where exceptions could
     end up being overwritten because of deferred error handling.

   - gh-105605(182): Harden ‘pyexpat’ error handling during module
     initialisation to prevent exceptions from possibly being
     overwritten, and objects from being dereferenced twice.

   - gh-105375(183): Fix bug in *note decimal: 2e. where an exception
     could end up being overwritten.

   - gh-105375(184): Fix bugs in ‘_datetime’ where exceptions could be
     overwritten in case of module initialisation failure.

   - gh-105375(185): Fix bugs in ‘_ssl’ initialisation which could lead
     to leaked references and overwritten exceptions.

   - gh-105375(186): Fix a bug in *note array.array: 186. where an
     exception could end up being overwritten.

   - gh-105375(187): Fix bugs in ‘_ctypes’ where exceptions could end up
     being overwritten.

   - gh-105375(188): Fix a bug in the *note posix: 9b. module where an
     exception could be overwritten.

   - gh-105375(189): Fix bugs in ‘_elementtree’ where exceptions could
     be overwritten.

   - gh-105375(190): Fix bugs in *note zoneinfo: 11a. where exceptions
     could be overwritten.

   - gh-105375(191): Fix bugs in *note errno: 4d. where exceptions could
     be overwritten.

   - gh-105566(192): Deprecate creating a *note typing.NamedTuple: 291.
     class using keyword arguments to denote the fields (‘NT =
     NamedTuple("NT", x=int, y=str)’).  This will be disallowed in
     Python 3.15.  Use the class-based syntax or the functional syntax
     instead.

     Two methods of creating ‘NamedTuple’ classes with 0 fields using
     the functional syntax are also deprecated, and will be disallowed
     in Python 3.15: ‘NT = NamedTuple("NT")’ and ‘NT = NamedTuple("NT",
     None)’.  To create a ‘NamedTuple’ class with 0 fields, either use
     ‘class NT(NamedTuple): pass’ or ‘NT = NamedTuple("NT", [])’.

   - gh-105545(193): Remove deprecated in 3.11
     ‘webbrowser.MacOSXOSAScript._name’ attribute.

   - gh-105497(194): Fix flag inversion when alias/mask members exist.

   - gh-105509(195): *note typing.Annotated: 8e1. is now implemented as
     an instance of ‘typing._SpecialForm’ rather than a class.  This
     should have no user-facing impact for users of the *note typing:
     ed. module public API.

   - gh-105375(196): Fix bugs in *note pickle: 95. where exceptions
     could be overwritten.

   - gh-70303(197): Emit *note FutureWarning: 357. from *note
     pathlib.Path.glob(): 212. and *note rglob(): 213. if the given
     pattern ends with "‘**’".  In a future Python release, patterns
     with this ending will match both files and directories.  Add a
     trailing slash to only match directories.

   - gh-105375(198): Fix a bug in *note sqlite3: ba. where an exception
     could be overwritten in the *note collation: 61c. callback.

   - gh-105382(199): Remove 'cafile', 'capath' and 'cadefault'
     parameters of the *note urllib.request.urlopen(): 275. function,
     deprecated in Python 3.6.  Patch by Victor Stinner.

   - gh-105376(200): *note logging: 7b.: Remove undocumented and
     untested ‘Logger.warn()’ and ‘LoggerAdapter.warn()’ methods and
     ‘logging.warn()’ function.  Deprecated since Python 3.3, they were
     aliases to the *note logging.Logger.warning(): 1600. method,
     ‘logging.LoggerAdapter.warning()’ method and *note
     logging.warning(): 2d0. function.  Patch by Victor Stinner.

   - gh-105332(201): Revert pickling method from by-name back to
     by-value.

   - gh-104554(202): Add RTSPS scheme support in urllib.parse

   - gh-105292(203): Add option to *note
     traceback.format_exception_only(): 7f2. to recurse into the nested
     exception of a *note BaseExceptionGroup: 244.

   - gh-105280(204): Fix bug where ‘isinstance([],
     collections.abc.Mapping)’ could evaluate to ‘True’ if garbage
     collection happened at the wrong time.  The bug was caused by
     changes to the implementation of *note typing.Protocol: 249. in
     Python 3.12.

   - gh-80480(205): *note array: 6.: Add ‘'w'’ typecode that represents
     ‘Py_UCS4’.

   - gh-105239(206): Fix longstanding bug where ‘issubclass(object,
     typing.Protocol)’ would evaluate to ‘True’ in some edge cases.
     Patch by Alex Waygood.

   - gh-104310(207): In the beta 1 release we added a utility function
     for extension module authors, to use when testing their module for
     support in multiple interpreters or under a per-interpreter GIL.
     The name of that function has changed from
     ‘allowing_all_extensions’ to
     ‘_incompatible_extension_module_restrictions’.  The default for the
     "disable_check" argument has change from ‘True’ to ‘False’, to
     better match the new function name.

   - gh-105080(208): Fixed inconsistent signature on derived classes for
     *note inspect.signature(): 6dc.

   - gh-105144(209): Fix a recent regression in the *note typing: ed.
     module.  The regression meant that doing ‘class Foo(X,
     typing.Protocol)’, where ‘X’ was a class that had *note
     abc.ABCMeta: ebc. as its metaclass, would then cause subsequent
     ‘isinstance(1, X)’ calls to erroneously raise *note TypeError: 4dd.
     Patch by Alex Waygood.

   - gh-62948(210): The *note io.IOBase: 1da. finalizer now logs the
     ‘close()’ method errors with *note sys.unraisablehook: 1dc.
     Previously, errors were ignored silently by default, and only
     logged in *note Python Development Mode: 1dd. or on *note Python
     built on debug mode: 1de.  Patch by Victor Stinner.

   - gh-105096(211): *note wave: fb.: Deprecate the ‘getmark()’,
     ‘setmark()’ and ‘getmarkers()’ methods of the *note wave.Wave_read:
     297. and *note wave.Wave_write: 298. classes.  They will be removed
     in Python 3.15.  Patch by Victor Stinner.

   - gh-104992(212): Remove the untested and undocumented
     ‘unittest.TestProgram.usageExit()’ method, deprecated in Python
     3.11.  Patch by Hugo van Kemenade.

   - gh-104996(213): Improve performance of *note pathlib.PurePath: 44e.
     initialisation by deferring joining of paths when multiple
     arguments are given.

   - gh-101588(214): Deprecate undocumented copy/deepcopy/pickle support
     for itertools.

   - gh-103631(215): Fix
     ‘pathlib.PurePosixPath(pathlib.PureWindowsPath(...))’ not
     converting path separators to restore 3.11 compatible behavior.

   - gh-104947(216): Make comparisons between *note
     pathlib.PureWindowsPath: 1601. objects consistent across Windows
     and Posix to match 3.11 behavior.

   - gh-104773(217): PEP 594(218): Remove the ‘audioop’ module,
     deprecated in Python 3.11.  Patch by Victor Stinner.

   - gh-104773(219): PEP 594(220): Remove the ‘aifc’ module, deprecated
     in Python 3.11.  Patch by Victor Stinner.

   - gh-104773(221): PEP 594(222): Remove the ‘uu’ module, deprecated in
     Python 3.11.  Patch by Victor Stinner.

   - gh-104935(223): Fix bugs with the interaction between *note
     typing.runtime_checkable(): 3e9. and *note typing.Generic: 150c.
     that were introduced by the PEP 695(224) implementation.  Patch by
     Jelle Zijlstra.

   - gh-104773(225): PEP 594(226): Remove the ‘crypt’ module and its
     private ‘_crypt’ extension, deprecated in Python 3.11.  Patch by
     Victor Stinner.

   - gh-104773(227): PEP 594(228): Remove the ‘nis’ module, deprecated
     in Python 3.11.  Patch by Victor Stinner.

   - gh-104898(229): Add missing *note __slots__: 1458. to *note
     os.PathLike: bf8.

   - gh-104773(230): PEP 594(231): Remove the ‘xdrlib’ module,
     deprecated in Python 3.11.  Patch by Victor Stinner.

   - gh-104773(232): PEP 594(233): Remove the ‘nntplib’ module,
     deprecated in Python 3.11.  Patch by Victor Stinner.

   - gh-104886(234): Remove the undocumented
     ‘configparser.LegacyInterpolation’ class, deprecated in the
     docstring since Python 3.2, and with a deprecation warning since
     Python 3.11.  Patch by Hugo van Kemenade.

   - gh-104786(235): Remove kwargs-based *note typing.TypedDict: 146.
     creation

   - gh-104876(236): Remove the ‘turtle.RawTurtle.settiltangle()’
     method, deprecated in docs since Python 3.1 and with a deprecation
     warning since Python 3.11.  Patch by Hugo van Kemenade.

   - gh-104773(237): PEP 594(238): Removed the ‘msilib’ package,
     deprecated in Python 3.11.

   - gh-104773(239): PEP 594(240): Remove the ‘spwd’ module, deprecated
     in Python 3.11: the python-pam(241) project can be used instead.
     Patch by Victor Stinner.

   - gh-75552(242): Removed the ‘tkinter.tix’ module, deprecated since
     Python 3.6.

   - gh-104773(243): PEP 594(244): Remove the ‘chunk’ module, deprecated
     in Python 3.11.  Patch by Victor Stinner.

   - gh-104773(245): PEP 594(246): Remove the ‘mailcap’ module,
     deprecated in Python 3.11.  Patch by Victor Stinner.

   - gh-104773(247): PEP 594(248): Remove the ‘sunau’ module, deprecated
     in Python 3.11.  Patch by Victor Stinner.

   - gh-104780(249): PEP 594(250): Remove the ‘ossaudiodev’ module,
     deprecated in Python 3.11.  Patch Victor Stinner.

   - gh-104773(251): PEP 594(252): Remove the ‘pipes’ module, deprecated
     in Python 3.11.  Patch by Victor Stinner.

   - gh-104873(253): Add *note typing.get_protocol_members(): 248. to
     return the set of members defining a *note typing.Protocol: 249.
     Add *note typing.is_protocol(): 24a. to check whether a class is a
     *note typing.Protocol: 249.  Patch by Jelle Zijlstra.

   - gh-104874(254): Document the ‘__name__’ and ‘__supertype__’
     attributes of *note typing.NewType: c9c.  Patch by Jelle Zijlstra.

   - gh-104835(255): Removed the following *note unittest: ef.
     functions, deprecated in Python 3.11:

        * ‘unittest.findTestCases()’

        * ‘unittest.makeSuite()’

        * ‘unittest.getTestCaseNames()’

     Use *note TestLoader: 270. methods instead:

        * *note unittest.TestLoader.loadTestsFromModule(): 271.

        * *note unittest.TestLoader.loadTestsFromTestCase(): 272.

        * *note unittest.TestLoader.getTestCaseNames(): 273.

     Patch by Hugo van Kemenade.

   - gh-104804(256): Remove the untested and undocumented *note
     webbrowser: fd. ‘MacOSX’ class, deprecated in Python 3.11.  Patch
     by Hugo van Kemenade.

   - gh-83863(257): Support for using *note pathlib.Path: 20e. objects
     as context managers has been removed.  Before Python 3.9, exiting
     the context manager marked a path as "closed", which caused some
     (but not all!)  methods to raise when called.  Since Python 3.9,
     using a path as a context manager does nothing.

   - gh-104799(258): Adjust the location of the (see PEP 695(259))
     ‘type_params’ field on *note ast.ClassDef: 1602, *note
     ast.AsyncFunctionDef: 1603, and *note ast.FunctionDef: 1604. to
     better preserve backward compatibility.  Patch by Jelle Zijlstra

   - gh-104797(260): Allow *note typing.Protocol: 249. classes to
     inherit from *note collections.abc.Buffer: 2a5.  Patch by Jelle
     Zijlstra.

   - gh-104783(261): Remove ‘locale.resetlocale()’ function deprecated
     in Python 3.11.  Patch by Victor Stinner.

   - gh-104780(262): Remove the ‘2to3’ program and the ‘lib2to3’ module,
     deprecated in Python 3.11.  Patch by Victor Stinner.

   - gh-104773(263): PEP 594(264): Remove the ‘telnetlib’ module,
     deprecated in Python 3.11.  Patch by Victor Stinner.

   - gh-104773(265): PEP 594(266): Remove the ‘imghdr’ module,
     deprecated in Python 3.11.  Patch by Victor Stinner.

   - gh-104773(267): PEP 594(268): Remove the ‘cgi’ and ‘cgitb’ modules,
     deprecated in Python 3.11.  Patch by Victor Stinner.

   - gh-104773(269): PEP 594(270): Remove the ‘sndhdr’ module,
     deprecated in Python 3.11.  Patch by Victor Stinner.

   - gh-104372(271): On Linux where *note subprocess: c1. can use the
     ‘vfork()’ syscall for faster spawning, prevent the parent process
     from blocking other threads by dropping the GIL while it waits for
     the vfork'ed child process ‘exec()’ outcome.  This prevents
     spawning a binary from a slow filesystem from blocking the rest of
     the application.

   - gh-99108(272): We now release the GIL around built-in *note
     hashlib: 5e. computations of reasonable size for the SHA families
     and MD5 hash functions, matching what our OpenSSL backed hash
     computations already does.

   - gh-102613(273): Improve performance of *note pathlib.Path.glob():
     212. when expanding a pattern with a non-terminal "‘**’" component
     by filtering walked paths through a regular expression, rather than
     calling *note os.scandir(): a02. more than once on each directory.

   - gh-104399(274): Prepare the ‘_tkinter’ module for building with Tcl
     9.0 and future libtommath by replacing usage of deprecated
     functions ‘mp_to_unsigned_bin_n()’ and ‘mp_unsigned_bin_size()’
     when necessary.

   - gh-102676(275): Add fields ‘start_offset’, ‘cache_offset’,
     ‘end_offset’, ‘baseopname’, ‘baseopcode’, ‘jump_target’ and ‘oparg’
     to *note dis.Instruction: 1bd.

   - gh-103558(276): Fixed ‘parent’ argument validation mechanism of
     *note argparse: 5.  Improved test coverage.

   - gh-103464(277): Provide helpful usage messages when parsing
     incorrect *note pdb: 94. commands.

   - gh-103384(278): Generalize the regex pattern
     ‘BaseConfigurator.INDEX_PATTERN’ to allow spaces and
     non-alphanumeric characters in keys.

   - gh-103124(279): Added multiline statement support for *note pdb:
     94.

   - gh-101162(280): Forbid using ‘builtins.issubclass()’ with *note
     types.GenericAlias: 78f. as the first argument.

   - gh-103200(281): Fix cache repopulation semantics of
     zipimport.invalidate_caches().  The cache is now repopulated upon
     retrieving files with an invalid cache, not when the cache is
     invalidated.

   - gh-100061(282): Fix a bug that causes wrong matches for regular
     expressions with possessive qualifier.

   - gh-77609(283): Add 'follow_symlinks' argument to *note
     pathlib.Path.glob(): 212. and *note rglob(): 213, defaulting to
     false.

   - gh-102541(284): Hide traceback in *note help(): 87c. prompt, when
     import failed.

   - gh-102120(285): Added a stream mode to ‘tarfile’ that allows for
     reading archives without caching info about the inner files.

   - gh-102029(286): Deprecate passing any arguments to *note
     threading.RLock(): 2be.

   - gh-88233(287): Refactored ‘zipfile._strip_extra’ to use higher
     level abstractions for extras instead of a heavy-state loop.

   - gh-102024(288): Reduce calls of ‘_idle_semaphore.release()’ in
     ‘concurrent.futures.thread._worker()’.

   - gh-73435(289): Add support for recursive wildcards in *note
     pathlib.PurePath.match(): 454.

   - gh-84867(290): *note unittest.TestLoader: 270. no longer loads test
     cases from exact *note unittest.TestCase: 3f4. and *note
     unittest.FunctionTestCase: 1605. classes.

   - gh-99203(291): Restore following CPython <= 3.10.5 behavior of
     *note shutil.make_archive(): 45a.: do not create an empty archive
     if ‘root_dir’ is not a directory, and, in that case, raise *note
     FileNotFoundError: e67. or *note NotADirectoryError: ffd.
     regardless of ‘format’ choice.  Beyond the brought-back behavior,
     the function may now also raise these exceptions in ‘dry_run’ mode.

   - gh-80480(292): Emit *note DeprecationWarning: 18b. for *note array:
     6.'s ‘'u'’ type code, deprecated in docs since Python 3.3.

   - gh-94924(293): *note unittest.mock.create_autospec(): 14fb. now
     properly returns coroutine functions compatible with *note
     inspect.iscoroutinefunction(): 439.

   - gh-94777(294): Fix hanging *note multiprocessing: 86.
     ‘ProcessPoolExecutor’ when a child process crashes while data is
     being written in the call queue.

   - gh-92871(295): Remove the ‘typing.io’ and ‘typing.re’ namespaces,
     deprecated since Python 3.8.  All items are still available from
     the main *note typing: ed. module.

   - bpo-43633(296): Improve the textual representation of IPv4-mapped
     IPv6 addresses ( RFC 4291(297) Sections 2.2, 2.5.5.2) in *note
     ipaddress: 74.  Patch by Oleksandr Pavliuk.

   - bpo-44850(298): Improve performance of *note
     operator.methodcaller(): dda. using the PEP 590(299) ‘vectorcall’
     convention.  Patch by Anthony Lee and Pieter Eendebak.

   - bpo-44185(300): *note unittest.mock.mock_open(): 1606. will call
     the ‘close()’ method of the file handle mock when it is exiting
     from the context manager.  Patch by Samet Yaslan.

   - bpo-40988(301): Improve performance of *note
     functools.singledispatchmethod: 994. by caching the generated
     dispatch wrapper.  Optimization suggested by frederico.  Patch by
     @mental32, Alex Waygood and Pieter Eendebak.

   - bpo-41768(302): *note unittest.mock: f0. speccing no longer calls
     class properties.  Patch by Melanie Witt.

   - bpo-18319(303): Ensure ‘gettext(msg)’ retrieve translations even if
     a plural form exists.  In other words: ‘gettext(msg) ==
     ngettext(msg, '', 1)’.

   - bpo-17013(304): Add ‘ThreadingMock’ to *note unittest.mock: f0.
     that can be used to create Mock objects that can wait until they
     are called.  Patch by Karthikeyan Singaravelan and Mario Corchero.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/110786

   (2) https://github.com/python/cpython/issues/103480

   (3) https://github.com/python/cpython/issues/110733

   (4) https://github.com/python/cpython/issues/94597

   (5) https://github.com/python/cpython/issues/110682

   (6) https://github.com/python/cpython/issues/110488

   (7) https://github.com/python/cpython/issues/110590

   (8) https://github.com/python/cpython/issues/65052

   (9) https://github.com/python/cpython/issues/110519

   (10) https://github.com/python/cpython/issues/89902

   (11) https://github.com/python/cpython/issues/110378

   (12) https://github.com/python/cpython/issues/106670

   (13) https://github.com/python/cpython/issues/110365

   (14) https://github.com/python/cpython/issues/109653

   (15) https://github.com/python/cpython/issues/110273

   (16) https://github.com/python/cpython/issues/110249

   (17) https://github.com/python/cpython/issues/109653

   (18) https://github.com/python/cpython/issues/110222

   (19) https://github.com/python/cpython/issues/109649

   (20) https://github.com/python/cpython/issues/110150

   (21) https://github.com/python/cpython/issues/110036

   (22) https://github.com/python/cpython/issues/110038

   (23) https://github.com/python/cpython/issues/110045

   (24) https://peps.python.org/pep-0695/

   (25) https://github.com/python/cpython/issues/88402

   (26) https://github.com/python/cpython/issues/109631

   (27) https://github.com/python/cpython/issues/109653

   (28) https://github.com/python/cpython/issues/109818

   (29) https://github.com/python/cpython/issues/109047

   (30) https://github.com/python/cpython/issues/109782

   (31) https://github.com/python/cpython/issues/109653

   (32) https://github.com/python/cpython/issues/109590

   (33) https://github.com/python/cpython/issues/109653

   (34) https://github.com/python/cpython/issues/109593

   (35) https://github.com/python/cpython/issues/109653

   (36) https://github.com/python/cpython/issues/109649

   (37) https://github.com/python/cpython/issues/74481

   (38) https://github.com/python/cpython/issues/109613

   (39) https://github.com/python/cpython/issues/109599

   (40) https://github.com/python/cpython/issues/109109

   (41) https://github.com/python/cpython/issues/109559

   (42) https://github.com/python/cpython/issues/109543

   (43) https://github.com/python/cpython/issues/109495

   (44) https://github.com/python/cpython/issues/109461

   (45) https://github.com/python/cpython/issues/109096

   (46) https://github.com/python/cpython/issues/109409

   (47) https://github.com/python/cpython/issues/109375

   (48) https://github.com/python/cpython/issues/109319

   (49) https://github.com/python/cpython/issues/107219

   (50) https://github.com/python/cpython/issues/66143

   (51) https://github.com/python/cpython/issues/109187

   (52) https://github.com/python/cpython/issues/50644

   (53) https://github.com/python/cpython/issues/109174

   (54) https://github.com/python/cpython/issues/109164

   (55) https://github.com/python/cpython/issues/109151

   (56) https://github.com/python/cpython/issues/108987

   (57) https://github.com/python/cpython/issues/108682

   (58) https://github.com/python/cpython/issues/109033

   (59) https://github.com/python/cpython/issues/108843

   (60) https://github.com/python/cpython/issues/108469

   (61) https://github.com/python/cpython/issues/108751

   (62) https://github.com/python/cpython/issues/108682

   (63) https://github.com/python/cpython/issues/108278

   (64) https://github.com/python/cpython/issues/105829

   (65) https://github.com/python/cpython/issues/108295

   (66) https://github.com/python/cpython/issues/108463

   (67) https://github.com/python/cpython/issues/108277

   (68) https://github.com/python/cpython/issues/107811

   (69) https://github.com/python/cpython/issues/64662

   (70) https://github.com/python/cpython/issues/108111

   (71) https://github.com/python/cpython/issues/101251

   (72) https://github.com/python/cpython/issues/108294

   (73) https://github.com/python/cpython/issues/108278

   (74) https://github.com/python/cpython/issues/108322

   (75) https://github.com/python/cpython/issues/83417

   (76) https://github.com/python/cpython/issues/105736

   (77) https://github.com/python/cpython/issues/108083

   (78) https://github.com/python/cpython/issues/107932

   (79) https://github.com/python/cpython/issues/105539

   (80) https://github.com/python/cpython/issues/107995

   (81) https://github.com/python/cpython/issues/107963

   (82) https://github.com/python/cpython/issues/106242

   (83) https://github.com/python/cpython/issues/81555

   (84) https://github.com/python/cpython/issues/50002

   (85) https://github.com/python/cpython/issues/93057

   (86) https://github.com/python/cpython/issues/76913

   (87) https://github.com/python/cpython/issues/107913

   (88) https://github.com/python/cpython/issues/107845

   (89) https://github.com/python/cpython/issues/107812

   (90) https://github.com/python/cpython/issues/107805

   (91) https://github.com/python/cpython/issues/107782

   (92) https://github.com/python/cpython/issues/56166

   (93) https://github.com/python/cpython/issues/107710

   (94) https://github.com/python/cpython/issues/107715

   (95) https://github.com/python/cpython/issues/100814

   (96) https://github.com/python/cpython/issues/72684

   (97) https://github.com/python/cpython/issues/106684

   (98) https://github.com/python/cpython/issues/107465

   (99) https://github.com/python/cpython/issues/107077

   (100) https://github.com/python/cpython/issues/107576

   (101) https://github.com/python/cpython/issues/105481

   (102) https://github.com/python/cpython/issues/105481

   (103) https://github.com/python/cpython/issues/107396

   (104) https://github.com/python/cpython/issues/107409

   (105) https://github.com/python/cpython/issues/107406

   (106) https://github.com/python/cpython/issues/107369

   (107) https://github.com/python/cpython/issues/78722

   (108) https://github.com/python/cpython/issues/105578

   (109) https://github.com/python/cpython/issues/62519

   (110) https://github.com/python/cpython/issues/107089

   (111) https://github.com/python/cpython/issues/82500

   (112) https://github.com/python/cpython/issues/83006

   (113) https://github.com/python/cpython/issues/65495

   (114) https://github.com/python/cpython/issues/106186

   (115) https://github.com/python/cpython/issues/105002

   (116) https://github.com/python/cpython/issues/106739

   (117) https://github.com/python/cpython/issues/106751

   (118) https://github.com/python/cpython/issues/106751

   (119) https://github.com/python/cpython/issues/106751

   (120) https://github.com/python/cpython/issues/106831

   (121) https://github.com/python/cpython/issues/105481

   (122) https://github.com/python/cpython/issues/106727

   (123) https://github.com/python/cpython/issues/106789

   (124) https://github.com/python/cpython/issues/105726

   (125) https://github.com/python/cpython/issues/106774

   (126) https://github.com/python/cpython/issues/106751

   (127) https://github.com/python/cpython/issues/106752

   (128) https://github.com/python/cpython/issues/105293

   (129) https://github.com/python/cpython/issues/106734

   (130) https://github.com/python/cpython/issues/105481

   (131) https://github.com/python/cpython/issues/106670

   (132) https://github.com/python/cpython/issues/106602

   (133) https://github.com/python/cpython/issues/106664

   (134) https://github.com/python/cpython/issues/106628

   (135) https://github.com/python/cpython/issues/89427

   (136) https://github.com/python/cpython/issues/106530

   (137) https://github.com/python/cpython/issues/106584

   (138) https://github.com/python/cpython/issues/106566

   (139) https://github.com/python/cpython/issues/106554

   (140) https://github.com/python/cpython/issues/106558

   (141) https://github.com/python/cpython/issues/100502

   (142) https://github.com/python/cpython/issues/106527

   (143) https://github.com/python/cpython/issues/106524

   (144) https://github.com/python/cpython/issues/106531

   (145) https://github.com/python/cpython/issues/106052

   (146) https://github.com/python/cpython/issues/106510

   (147) https://github.com/python/cpython/issues/106503

   (148) https://github.com/python/cpython/issues/105497

   (149) https://github.com/python/cpython/issues/90876

   (150) https://github.com/python/cpython/issues/106403

   (151) https://github.com/python/cpython/issues/89812

   (152) https://github.com/python/cpython/issues/106292

   (153) https://github.com/python/cpython/issues/106350

   (154) https://github.com/python/cpython/issues/106330

   (155) https://github.com/python/cpython/issues/106309

   (156) https://github.com/python/cpython/issues/102541

   (157) https://github.com/python/cpython/issues/106263

   (158) https://github.com/python/cpython/issues/106236

   (159) https://github.com/python/cpython/issues/106238

   (160) https://github.com/python/cpython/issues/106152

   (161) https://github.com/python/cpython/issues/106075

   (162) https://github.com/python/cpython/issues/104527

   (163) https://github.com/python/cpython/issues/106046

   (164) https://github.com/python/cpython/issues/105987

   (165) https://github.com/python/cpython/issues/105974

   (166) https://github.com/python/cpython/issues/96145

   (167) https://github.com/python/cpython/issues/89812

   (168) https://github.com/python/cpython/issues/105808

   (169) https://github.com/python/cpython/issues/101251

   (170) https://github.com/python/cpython/issues/105481

   (171) https://github.com/python/cpython/issues/104799

   (172) https://peps.python.org/pep-0695/

   (173) https://github.com/python/cpython/issues/105793

   (174) https://github.com/python/cpython/issues/105570

   (175) https://github.com/python/cpython/issues/105745

   (176) https://github.com/python/cpython/issues/105733

   (177) https://github.com/python/cpython/issues/105687

   (178) https://github.com/python/cpython/issues/105684

   (179) https://github.com/python/cpython/issues/105375

   (180) https://github.com/python/cpython/issues/105626

   (181) https://github.com/python/cpython/issues/105375

   (182) https://github.com/python/cpython/issues/105605

   (183) https://github.com/python/cpython/issues/105375

   (184) https://github.com/python/cpython/issues/105375

   (185) https://github.com/python/cpython/issues/105375

   (186) https://github.com/python/cpython/issues/105375

   (187) https://github.com/python/cpython/issues/105375

   (188) https://github.com/python/cpython/issues/105375

   (189) https://github.com/python/cpython/issues/105375

   (190) https://github.com/python/cpython/issues/105375

   (191) https://github.com/python/cpython/issues/105375

   (192) https://github.com/python/cpython/issues/105566

   (193) https://github.com/python/cpython/issues/105545

   (194) https://github.com/python/cpython/issues/105497

   (195) https://github.com/python/cpython/issues/105509

   (196) https://github.com/python/cpython/issues/105375

   (197) https://github.com/python/cpython/issues/70303

   (198) https://github.com/python/cpython/issues/105375

   (199) https://github.com/python/cpython/issues/105382

   (200) https://github.com/python/cpython/issues/105376

   (201) https://github.com/python/cpython/issues/105332

   (202) https://github.com/python/cpython/issues/104554

   (203) https://github.com/python/cpython/issues/105292

   (204) https://github.com/python/cpython/issues/105280

   (205) https://github.com/python/cpython/issues/80480

   (206) https://github.com/python/cpython/issues/105239

   (207) https://github.com/python/cpython/issues/104310

   (208) https://github.com/python/cpython/issues/105080

   (209) https://github.com/python/cpython/issues/105144

   (210) https://github.com/python/cpython/issues/62948

   (211) https://github.com/python/cpython/issues/105096

   (212) https://github.com/python/cpython/issues/104992

   (213) https://github.com/python/cpython/issues/104996

   (214) https://github.com/python/cpython/issues/101588

   (215) https://github.com/python/cpython/issues/103631

   (216) https://github.com/python/cpython/issues/104947

   (217) https://github.com/python/cpython/issues/104773

   (218) https://peps.python.org/pep-0594/

   (219) https://github.com/python/cpython/issues/104773

   (220) https://peps.python.org/pep-0594/

   (221) https://github.com/python/cpython/issues/104773

   (222) https://peps.python.org/pep-0594/

   (223) https://github.com/python/cpython/issues/104935

   (224) https://peps.python.org/pep-0695/

   (225) https://github.com/python/cpython/issues/104773

   (226) https://peps.python.org/pep-0594/

   (227) https://github.com/python/cpython/issues/104773

   (228) https://peps.python.org/pep-0594/

   (229) https://github.com/python/cpython/issues/104898

   (230) https://github.com/python/cpython/issues/104773

   (231) https://peps.python.org/pep-0594/

   (232) https://github.com/python/cpython/issues/104773

   (233) https://peps.python.org/pep-0594/

   (234) https://github.com/python/cpython/issues/104886

   (235) https://github.com/python/cpython/issues/104786

   (236) https://github.com/python/cpython/issues/104876

   (237) https://github.com/python/cpython/issues/104773

   (238) https://peps.python.org/pep-0594/

   (239) https://github.com/python/cpython/issues/104773

   (240) https://peps.python.org/pep-0594/

   (241) https://pypi.org/project/python-pam/

   (242) https://github.com/python/cpython/issues/75552

   (243) https://github.com/python/cpython/issues/104773

   (244) https://peps.python.org/pep-0594/

   (245) https://github.com/python/cpython/issues/104773

   (246) https://peps.python.org/pep-0594/

   (247) https://github.com/python/cpython/issues/104773

   (248) https://peps.python.org/pep-0594/

   (249) https://github.com/python/cpython/issues/104780

   (250) https://peps.python.org/pep-0594/

   (251) https://github.com/python/cpython/issues/104773

   (252) https://peps.python.org/pep-0594/

   (253) https://github.com/python/cpython/issues/104873

   (254) https://github.com/python/cpython/issues/104874

   (255) https://github.com/python/cpython/issues/104835

   (256) https://github.com/python/cpython/issues/104804

   (257) https://github.com/python/cpython/issues/83863

   (258) https://github.com/python/cpython/issues/104799

   (259) https://peps.python.org/pep-0695/

   (260) https://github.com/python/cpython/issues/104797

   (261) https://github.com/python/cpython/issues/104783

   (262) https://github.com/python/cpython/issues/104780

   (263) https://github.com/python/cpython/issues/104773

   (264) https://peps.python.org/pep-0594/

   (265) https://github.com/python/cpython/issues/104773

   (266) https://peps.python.org/pep-0594/

   (267) https://github.com/python/cpython/issues/104773

   (268) https://peps.python.org/pep-0594/

   (269) https://github.com/python/cpython/issues/104773

   (270) https://peps.python.org/pep-0594/

   (271) https://github.com/python/cpython/issues/104372

   (272) https://github.com/python/cpython/issues/99108

   (273) https://github.com/python/cpython/issues/102613

   (274) https://github.com/python/cpython/issues/104399

   (275) https://github.com/python/cpython/issues/102676

   (276) https://github.com/python/cpython/issues/103558

   (277) https://github.com/python/cpython/issues/103464

   (278) https://github.com/python/cpython/issues/103384

   (279) https://github.com/python/cpython/issues/103124

   (280) https://github.com/python/cpython/issues/101162

   (281) https://github.com/python/cpython/issues/103200

   (282) https://github.com/python/cpython/issues/100061

   (283) https://github.com/python/cpython/issues/77609

   (284) https://github.com/python/cpython/issues/102541

   (285) https://github.com/python/cpython/issues/102120

   (286) https://github.com/python/cpython/issues/102029

   (287) https://github.com/python/cpython/issues/88233

   (288) https://github.com/python/cpython/issues/102024

   (289) https://github.com/python/cpython/issues/73435

   (290) https://github.com/python/cpython/issues/84867

   (291) https://github.com/python/cpython/issues/99203

   (292) https://github.com/python/cpython/issues/80480

   (293) https://github.com/python/cpython/issues/94924

   (294) https://github.com/python/cpython/issues/94777

   (295) https://github.com/python/cpython/issues/92871

   (296) https://bugs.python.org/issue?@action=redirect&bpo=43633

   (297) https://datatracker.ietf.org/doc/html/rfc4291.html

   (298) https://bugs.python.org/issue?@action=redirect&bpo=44850

   (299) https://peps.python.org/pep-0590/

   (300) https://bugs.python.org/issue?@action=redirect&bpo=44185

   (301) https://bugs.python.org/issue?@action=redirect&bpo=40988

   (302) https://bugs.python.org/issue?@action=redirect&bpo=41768

   (303) https://bugs.python.org/issue?@action=redirect&bpo=18319

   (304) https://bugs.python.org/issue?@action=redirect&bpo=17013


File: python.info,  Node: Documentation<7>,  Next: Tests<10>,  Prev: Library<12>,  Up: Python 3 13 0 alpha 1

1.23.13.4 Documentation
.......................

   - gh-109209(1): The minimum Sphinx version required for the
     documentation is now 4.2.

   - gh-108826(2): *note dis: 30. module command-line interface is now
     mentioned in documentation.

   - gh-107305(3): Add documentation for *note PyInterpreterConfig: 513.
     and *note Py_NewInterpreterFromConfig(): 402.  Also clarify some of
     the nearby docs relative to per-interpreter GIL.

   - gh-107008(4): Document the *note curses: 23. module variables *note
     LINES: 1608. and *note COLS: 1609.

   - gh-106948(5): Add a number of standard external names to
     ‘nitpick_ignore’.

   - gh-106232(6): Make timeit doc command lines compatible with Windows
     by using double quotes for arguments.  This works on linux and
     macOS also.

   - gh-105172(7): Fixed *note functools.lru_cache(): 993. docstring
     accounting for ‘typed’ argument's different handling of str and
     int.  Patch by Bar Harel.

   - gh-105052(8): Update ‘timeit’ doc to specify that time in seconds
     is just the default.

   - gh-89455(9): Add missing documentation for the ‘max_group_depth’
     and ‘max_group_width’ parameters and the ‘exceptions’ attribute of
     the *note traceback.TracebackException: 241. class.

   - gh-89412(10): Add missing documentation for the ‘end_lineno’ and
     ‘end_offset’ attributes of the *note traceback.TracebackException:
     241. class.

   - gh-104943(11): Remove mentions of old Python versions in *note
     typing.NamedTuple: 291.

   - gh-54738(12): Add documentation on how to localize the *note
     argparse: 5. module.

   - gh-102823(13): Document the return type of ‘x // y’ when ‘x’ and
     ‘y’ have type *note float: 2c8.

   - gh-102759(14): Align function signature for ‘functools.reduce’ in
     documentation and docstring with the C implementation.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/109209

   (2) https://github.com/python/cpython/issues/108826

   (3) https://github.com/python/cpython/issues/107305

   (4) https://github.com/python/cpython/issues/107008

   (5) https://github.com/python/cpython/issues/106948

   (6) https://github.com/python/cpython/issues/106232

   (7) https://github.com/python/cpython/issues/105172

   (8) https://github.com/python/cpython/issues/105052

   (9) https://github.com/python/cpython/issues/89455

   (10) https://github.com/python/cpython/issues/89412

   (11) https://github.com/python/cpython/issues/104943

   (12) https://github.com/python/cpython/issues/54738

   (13) https://github.com/python/cpython/issues/102823

   (14) https://github.com/python/cpython/issues/102759


File: python.info,  Node: Tests<10>,  Next: Build<12>,  Prev: Documentation<7>,  Up: Python 3 13 0 alpha 1

1.23.13.5 Tests
...............

   - gh-110647(1): Fix test_stress_modifying_handlers() of test_signal.
     Patch by Victor Stinner.

   - gh-103053(2): Fix test_tools.test_freeze on FreeBSD: run "make
     distclean" instead of "make clean" in the copied source directory
     to remove also the "python" program.  Patch by Victor Stinner.

   - gh-110167(3): Fix a deadlock in test_socket when server fails with
     a timeout but the client is still running in its thread.  Don't
     hold a lock to call cleanup functions in doCleanups().  One of the
     cleanup function waits until the client completes, whereas the
     client could deadlock if it called addCleanup() in such situation.
     Patch by Victor Stinner.

   - gh-110388(4): Add tests for *note tty: e9.

   - gh-81002(5): Add tests for *note termios: ca.

   - gh-110367(6): regrtest: When using worker processes (-jN) with
     -verbose3 option, regrtest can now display the worker output even
     if a worker process does crash.  Previously, sys.stdout and
     sys.stderr were replaced and so the worker output was lost on a
     crash.  Patch by Victor Stinner.

   - gh-110267(7): Add tests for pickling and copying PyStructSequence
     objects.  Patched by Xuehai Pan.

   - gh-110171(8): ‘libregrtest’ now always sets and shows
     ‘random.seed’, so tests are more reproducible.  Use ‘--randseed’
     flag to pass the explicit random seed for tests.

   - gh-110152(9): Remove ‘Tools/scripts/run_tests.py’ and ‘make
     hostrunnertest’.  Just run ‘./python -m test --slow-ci’, ‘make
     buildbottest’ or ‘make test’ instead.  Python test runner
     (regrtest) now handles cross-compilation and HOSTRUNNER. It also
     adds options to Python such fast ‘-u -E -W default -bb’ when
     ‘--fast-ci’ or ‘--slow-ci’ option is used.  Patch by Victor
     Stinner.

   - gh-110031(10): Skip test_threading tests using thread+fork if
     Python is built with Address Sanitizer (ASAN). Patch by Victor
     Stinner.

   - gh-110088(11): Fix test_asyncio timeouts: don't measure the maximum
     duration, a test should not measure a CI performance.  Only measure
     the minimum duration when a task has a timeout or delay.  Add
     ‘CLOCK_RES’ to ‘test_asyncio.utils’.  Patch by Victor Stinner.

   - gh-109974(12): Fix race conditions in test_threading lock tests.
     Wait until a condition is met rather than using *note time.sleep():
     642. with a hardcoded number of seconds.  Patch by Victor Stinner.

   - gh-110033(13): Fix ‘test_interprocess_signal()’ of ‘test_signal’.
     Make sure that the ‘subprocess.Popen’ object is deleted before the
     test raising an exception in a signal handler.  Otherwise,
     ‘Popen.__del__()’ can get the exception which is logged as
     ‘Exception ignored in: ...’ and the test fails.  Patch by Victor
     Stinner.

   - gh-109594(14): Fix test_timeout() of
     test_concurrent_futures.test_wait.  Remove the future which may or
     may not complete depending if it takes longer than the timeout or
     not.  Keep the second future which does not complete before wait()
     timeout.  Patch by Victor Stinner.

   - gh-109972(15): Split test_gdb.py file into a test_gdb package made
     of multiple tests, so tests can now be run in parallel.  Patch by
     Victor Stinner.

   - gh-109566(16): regrtest: When ‘--fast-ci’ or ‘--slow-ci’ option is
     used, regrtest now replaces the current process with a new process
     to add ‘-u -W default -bb -E’ options to Python.  Patch by Victor
     Stinner.

   - gh-109748(17): Fix ‘test_zippath_from_non_installed_posix()’ of
     test_venv: don't copy ‘__pycache__/’ sub-directories, because they
     can be modified by other Python tests running in parallel.  Patch
     by Victor Stinner.

   - gh-109739(18): regrtest: Fix reference leak check on Windows.
     Disable the load tracker on Windows in the reference leak check
     mode (-R option).  Patch by Victor Stinner.

   - gh-109276(19): regrtest: When a test fails with "env changed" and
     the -rerun option is used, the test is now re-run in verbose mode
     in a fresh process.  Patch by Victor Stinner.

   - gh-103053(20): Skip test_freeze_simple_script() of
     test_tools.test_freeze if Python is built with ‘./configure
     --enable-optimizations’, which means with Profile Guided
     Optimization (PGO): it just makes the test too slow.  The freeze
     tool is tested by many other CIs with other (faster) compiler
     flags.  Patch by Victor Stinner.

   - gh-109580(21): Skip ‘test_perf_profiler’ if Python is built with
     ASAN, MSAN or UBSAN sanitizer.  Python does crash randomly in this
     test on such build.  Patch by Victor Stinner.

   - gh-109566(22): regrtest: Add ‘--fast-ci’ and ‘--slow-ci’ options.
     ‘--fast-ci’ uses a default timeout of 10 minutes and ‘-u all,-cpu’
     (skip slowest tests).  ‘--slow-ci’ uses a default timeout of 20
     minutes and ‘-u all’ (run all tests).  Patch by Victor Stinner.

   - gh-109425(23): libregrtest now decodes stdout of test worker
     processes with the "backslashreplace" error handler to log
     corrupted stdout, instead of failing with an error and not logging
     the stdout.  Patch by Victor Stinner.

   - gh-109396(24): Fix ‘test_socket.test_hmac_sha1()’ in FIPS mode.
     Use a longer key: FIPS mode requires at least of at least 112 bits.
     The previous key was only 32 bits.  Patch by Victor Stinner.

   - gh-104736(25): Fix test_gdb on Python built with LLVM clang 16 on
     Linux ppc64le (ex: Fedora 38).  Search patterns in gdb "bt" command
     output to detect when gdb fails to retrieve the traceback.  For
     example, skip a test if ‘Backtrace stopped: frame did not save the
     PC’ is found.  Patch by Victor Stinner.

   - gh-109276(26): libregrtest now calls *note random.seed(): 120c.
     before running each test file when ‘-r/--randomize’ command line
     option is used.  Moreover, it's also called in worker processes.
     It should help to make tests more deterministic.  Previously, it
     was only called once in the main process before running all test
     files and it was not called in worker processes.  Patch by Victor
     Stinner.

   - gh-109276(27): libregrtest now uses a separated file descriptor to
     write test result as JSON. Previously, if a test wrote debug
     messages late around the JSON, the main test process failed to
     parse JSON. Patch by Victor Stinner.

   - gh-108996(28): Fix and enable ‘test_msvcrt’.

   - gh-109237(29): Fix ‘test_site.test_underpth_basic()’ when the
     working directory contains at least one non-ASCII character: encode
     the ‘._pth’ file to UTF-8 and enable the UTF-8 Mode to use UTF-8
     for the child process stdout.  Patch by Victor Stinner.

   - gh-109230(30): Fix ‘test_pyexpat.test_exception()’: it can now be
     run from a directory different than Python source code directory.
     Before, the test failed in this case.  Skip the test if
     Modules/pyexpat.c source is not available.  Skip also the test on
     Python implementations other than CPython.  Patch by Victor
     Stinner.

   - gh-108996(31): Add tests for ‘msvcrt’.

   - gh-109015(32): Fix test_asyncio, test_imaplib and test_socket tests
     on FreeBSD if the TCP blackhole is enabled (‘sysctl
     net.inet.tcp.blackhole’).  Skip the few tests which failed with
     ‘ETIMEDOUT’ which such non standard configuration.  Currently, the
     FreeBSD GCP image enables TCP and UDP blackhole(33) (‘sysctl
     net.inet.tcp.blackhole=2’ and ‘sysctl net.inet.udp.blackhole=1’).
     Patch by Victor Stinner.

   - gh-91960(34): Skip ‘test_gdb’ if gdb is unable to retrieve Python
     frame objects: if a frame is ‘<optimized out>’.  When Python is
     built with "clang -Og", gdb can fail to retrieve the 'frame'
     parameter of ‘_PyEval_EvalFrameDefault()’.  In this case, tests
     like ‘py_bt()’ are likely to fail.  Without getting access to
     Python frames, ‘python-gdb.py’ is mostly clueless on retrieving the
     Python traceback.  Moreover, ‘test_gdb’ is no longer skipped on
     macOS if Python is built with Clang.  Patch by Victor Stinner.

   - gh-108962(35): Skip ‘test_tempfile.test_flags()’ if ‘chflags()’
     fails with "OSError: [Errno 45] Operation not supported" (ex: on
     FreeBSD 13).  Patch by Victor Stinner.

   - gh-91960(36): FreeBSD 13.2 CI coverage for pull requests is now
     provided by Cirrus-CI (a hosted CI service that supports Linux,
     macOS, Windows, and FreeBSD).

   - gh-89392(37): Removed support of ‘test_main()’ function in tests.
     They now always use normal unittest test runner.

   - gh-108851(38): Fix ‘test_tomllib’ recursion tests for WASI
     buildbots: reduce the recursion limit and compute the maximum
     nested array/dict depending on the current available recursion
     limit.  Patch by Victor Stinner.

   - gh-108851(39): Add ‘get_recursion_available()’ and
     ‘get_recursion_depth()’ functions to the *note test.support: cd.
     module.  Patch by Victor Stinner.

   - gh-108834(40): Add ‘--fail-rerun option’ option to regrtest: if a
     test failed when then passed when rerun in verbose mode, exit the
     process with exit code 2 (error), instead of exit code 0 (success).
     Patch by Victor Stinner.

   - gh-108834(41): Rename regrtest ‘--verbose2’ option (‘-w’) to
     ‘--rerun’.  Keep ‘--verbose2’ as a deprecated alias.  Patch by
     Victor Stinner.

   - gh-108834(42): When regrtest reruns failed tests in verbose mode
     (‘./python -m test --rerun’), tests are now rerun in fresh worker
     processes rather than being executed in the main process.  If a
     test does crash or is killed by a timeout, the main process can
     detect and handle the killed worker process.  Tests are rerun in
     parallel if the ‘-jN’ option is used to run tests in parallel.
     Patch by Victor Stinner.

   - gh-108822(43): ‘regrtest’ now computes statistics on all tests:
     successes, failures and skipped.  ‘test_netrc’,
     ‘test_pep646_syntax’ and ‘test_xml_etree’ now return results in
     their ‘test_main()’ function.  Patch by Victor Stinner and Alex
     Waygood.

   - gh-108794(44): The *note doctest.DocTestRunner.run(): 1bf. method
     now counts the number of skipped tests.  Add *note
     doctest.DocTestRunner.skips: 1c0. and *note
     doctest.TestResults.skipped: 1c1. attributes.  Patch by Victor
     Stinner.

   - gh-108388(45): Convert test_concurrent_futures to a package of 7
     sub-tests.  Patch by Victor Stinner.

   - gh-108388(46): Split test_multiprocessing_fork,
     test_multiprocessing_forkserver and test_multiprocessing_spawn into
     test packages.  Each package is made of 4 sub-tests: processes,
     threads, manager and misc.  It allows running more tests in
     parallel and so reduce the total test duration.  Patch by Victor
     Stinner.

   - gh-105776(47): Fix test_cppext when the C compiler command
     ‘-std=c11’ option: remove ‘-std=’ options from the compiler
     command.  Patch by Victor Stinner.

   - gh-107652(48): Set up CIFuzz to run fuzz targets in GitHub Actions.
     Patch by Illia Volochii.

   - gh-107237(49): ‘test_logging’: Fix ‘test_udp_reconnection()’ by
     increasing the timeout from 100 ms to 5 minutes (LONG_TIMEOUT).
     Patch by Victor Stinner.

   - gh-107178(50): Add the C API test for functions in the Mapping
     Protocol, the Sequence Protocol and some functions in the Object
     Protocol.

   - gh-106714(51): test_capi: Fix test_no_FatalError_infinite_loop() to
     no longer write a coredump, by using
     test.support.SuppressCrashReport.  Patch by Victor Stinner.

   - gh-104090(52): Avoid creating a reference to the test object in
     *note collectedDurations(): 160b.

   - gh-106752(53): Moved tests for ‘zipfile.Path’ into
     ‘Lib/test/test_zipfile/_path’.  Made ‘zipfile._path’ a package.

   - gh-106690(54): Add .coveragerc to cpython repository for use with
     coverage package.

   - gh-101634(55): When running the Python test suite with ‘-jN’
     option, if a worker stdout cannot be decoded from the locale
     encoding report a failed testn so the exitcode is non-zero.  Patch
     by Victor Stinner.

   - gh-105084(56): When the Python build is configured
     ‘--with-wheel-pkg-dir’, tests requiring the ‘setuptools’ and
     ‘wheel’ wheels will search for the wheels in ‘WHEEL_PKG_DIR’.

   - gh-81005(57): String tests are modified to reflect that ‘str’ and
     ‘unicode’ are merged in Python 3.  Patch by Daniel Fortunov.

   - gh-103186(58): Suppress and assert expected RuntimeWarnings in
     test_sys_settrace.py

   - gh-69714(59): Add additional tests to *note calendar: 10. to
     achieve full test coverage.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/110647

   (2) https://github.com/python/cpython/issues/103053

   (3) https://github.com/python/cpython/issues/110167

   (4) https://github.com/python/cpython/issues/110388

   (5) https://github.com/python/cpython/issues/81002

   (6) https://github.com/python/cpython/issues/110367

   (7) https://github.com/python/cpython/issues/110267

   (8) https://github.com/python/cpython/issues/110171

   (9) https://github.com/python/cpython/issues/110152

   (10) https://github.com/python/cpython/issues/110031

   (11) https://github.com/python/cpython/issues/110088

   (12) https://github.com/python/cpython/issues/109974

   (13) https://github.com/python/cpython/issues/110033

   (14) https://github.com/python/cpython/issues/109594

   (15) https://github.com/python/cpython/issues/109972

   (16) https://github.com/python/cpython/issues/109566

   (17) https://github.com/python/cpython/issues/109748

   (18) https://github.com/python/cpython/issues/109739

   (19) https://github.com/python/cpython/issues/109276

   (20) https://github.com/python/cpython/issues/103053

   (21) https://github.com/python/cpython/issues/109580

   (22) https://github.com/python/cpython/issues/109566

   (23) https://github.com/python/cpython/issues/109425

   (24) https://github.com/python/cpython/issues/109396

   (25) https://github.com/python/cpython/issues/104736

   (26) https://github.com/python/cpython/issues/109276

   (27) https://github.com/python/cpython/issues/109276

   (28) https://github.com/python/cpython/issues/108996

   (29) https://github.com/python/cpython/issues/109237

   (30) https://github.com/python/cpython/issues/109230

   (31) https://github.com/python/cpython/issues/108996

   (32) https://github.com/python/cpython/issues/109015

   (33) https://reviews.freebsd.org/D41751

   (34) https://github.com/python/cpython/issues/91960

   (35) https://github.com/python/cpython/issues/108962

   (36) https://github.com/python/cpython/issues/91960

   (37) https://github.com/python/cpython/issues/89392

   (38) https://github.com/python/cpython/issues/108851

   (39) https://github.com/python/cpython/issues/108851

   (40) https://github.com/python/cpython/issues/108834

   (41) https://github.com/python/cpython/issues/108834

   (42) https://github.com/python/cpython/issues/108834

   (43) https://github.com/python/cpython/issues/108822

   (44) https://github.com/python/cpython/issues/108794

   (45) https://github.com/python/cpython/issues/108388

   (46) https://github.com/python/cpython/issues/108388

   (47) https://github.com/python/cpython/issues/105776

   (48) https://github.com/python/cpython/issues/107652

   (49) https://github.com/python/cpython/issues/107237

   (50) https://github.com/python/cpython/issues/107178

   (51) https://github.com/python/cpython/issues/106714

   (52) https://github.com/python/cpython/issues/104090

   (53) https://github.com/python/cpython/issues/106752

   (54) https://github.com/python/cpython/issues/106690

   (55) https://github.com/python/cpython/issues/101634

   (56) https://github.com/python/cpython/issues/105084

   (57) https://github.com/python/cpython/issues/81005

   (58) https://github.com/python/cpython/issues/103186

   (59) https://github.com/python/cpython/issues/69714


File: python.info,  Node: Build<12>,  Next: Windows<9>,  Prev: Tests<10>,  Up: Python 3 13 0 alpha 1

1.23.13.6 Build
...............

   - gh-103053(1): "make check-clean-src" now also checks if the
     "python" program is found in the source directory: fail with an
     error if it does exist.  Patch by Victor Stinner.

   - gh-109191(2): Fix compile error when building with recent versions
     of libedit.

   - gh-110276(3): No longer ignore *note PROFILE_TASK: 160d. failure
     silently: command used by Profile Guided Optimization (PGO). Patch
     by Victor Stinner.

   - gh-109566(4): Remove ‘make testall’ target: use ‘make buildbottest’
     instead.  Patch by Victor Stinner.

   - gh-109740(5): The experimental ‘--disable-gil’ configure flag now
     includes "t" (for "threaded") in extension ABI tags.

   - gh-109054(6): Fix building the ‘_testcapi’ extension on Linux
     AArch64 which requires linking to libatomic when
     ‘<cpython/pyatomic.h>’ is used: the ‘_Py_atomic_or_uint64()’
     function requires libatomic ‘__atomic_fetch_or_8()’ on this
     platform.  The configure script now checks if linking to libatomic
     is needed and generates a new LIBATOMIC variable used to build the
     _testcapi extension.  Patch by Victor Stinner.

   - gh-63760(7): Fix Solaris build: no longer redefine the
     ‘gethostname()’ function.  Solaris defines the function since 2005.
     Patch by Victor Stinner, original patch by Jakub Kulík.

   - gh-108740(8): Fix a race condition in ‘make regen-all’.  The
     ‘deepfreeze.c’ source and files generated by Argument Clinic are
     now generated or updated before generating "global objects".
     Previously, some identifiers may miss depending on the order in
     which these files were generated.  Patch by Victor Stinner.

   - gh-108634(9): Python built with ‘configure’ *note -with-trace-refs:
     317. (tracing references) is now ABI compatible with Python release
     build and *note debug build: 1de.  Patch by Victor Stinner.

   - gh-85283(10): The ‘_stat’ C extension is now built with the *note
     limited C API: 318.  Patch by Victor Stinner.

   - gh-108447(11): Fix x86_64 GNU/Hurd build

   - gh-107814(12): When calling ‘find_python.bat’ with ‘-q’ it did not
     properly silence the output of nuget.  That is now fixed.

   - gh-105481(13): Remove the make target ‘regen-opcode-targets’, merge
     its work into ‘regen-opcode’ which repeats most of the calculation.
     This simplifies the code for the build and reduces code
     duplication.

   - gh-106881(14): Check for ‘linux/limits.h’ before including it in
     ‘Modules/posixmodule.c’.

   - gh-95855(15): Refactor platform triplet detection code and add
     detection for MIPS soft float and musl libc.

   - gh-106962(16): Detect MPI compilers in ‘configure’.

   - gh-106118(17): Fix compilation for platforms without ‘O_CLOEXEC’.
     The issue was introduced with Python 3.12b1 in gh-103295(18).
     Patch by Erlend Aasland.

   - gh-105875(19): SQLite 3.15.2 or newer is required to build the
     *note sqlite3: ba. extension module.  Patch by Erlend Aasland.

   - gh-90005(20): Fix a regression in ‘configure’ where we could end up
     unintentionally linking with ‘libbsd’.

   - gh-102404(21): Document how to perform a WASI build on Linux.  Also
     add Tools/wasm/build_wasi.sh as a reference implementation of the
     docs.

   - gh-89886(22): Autoconf 2.71 and aclocal 1.16.4 is now required to
     regenerate ‘!configure’.

   - gh-104692(23): Include ‘commoninstall’ as a prerequisite for
     ‘bininstall’

     This ensures that ‘commoninstall’ is completed before ‘bininstall’
     is started when parallel builds are used (‘make -j install’), and
     so the ‘python3’ symlink is only installed after all standard
     library modules are installed.

   - gh-101538(24): Add experimental wasi-threads support.  Patch by
     Takashi Yamamoto.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/103053

   (2) https://github.com/python/cpython/issues/109191

   (3) https://github.com/python/cpython/issues/110276

   (4) https://github.com/python/cpython/issues/109566

   (5) https://github.com/python/cpython/issues/109740

   (6) https://github.com/python/cpython/issues/109054

   (7) https://github.com/python/cpython/issues/63760

   (8) https://github.com/python/cpython/issues/108740

   (9) https://github.com/python/cpython/issues/108634

   (10) https://github.com/python/cpython/issues/85283

   (11) https://github.com/python/cpython/issues/108447

   (12) https://github.com/python/cpython/issues/107814

   (13) https://github.com/python/cpython/issues/105481

   (14) https://github.com/python/cpython/issues/106881

   (15) https://github.com/python/cpython/issues/95855

   (16) https://github.com/python/cpython/issues/106962

   (17) https://github.com/python/cpython/issues/106118

   (18) https://github.com/python/cpython/issues/103295

   (19) https://github.com/python/cpython/issues/105875

   (20) https://github.com/python/cpython/issues/90005

   (21) https://github.com/python/cpython/issues/102404

   (22) https://github.com/python/cpython/issues/89886

   (23) https://github.com/python/cpython/issues/104692

   (24) https://github.com/python/cpython/issues/101538


File: python.info,  Node: Windows<9>,  Next: macOS<7>,  Prev: Build<12>,  Up: Python 3 13 0 alpha 1

1.23.13.7 Windows
.................

   - gh-110437(1): Allows overriding the source of VC redistributables
     so that releases can be guaranteed to never downgrade between
     updates.

   - gh-109286(2): Update Windows installer to use SQLite 3.43.1.

   - gh-82367(3): *note os.path.realpath(): 20a. now resolves MS-DOS
     style file names even if the file is not accessible.  Patch by
     Moonsik Park.

   - gh-109991(4): Update Windows build to use OpenSSL 3.0.11.

   - gh-106242(5): Fixes *note realpath(): 20a. to behave consistently
     when passed a path containing an embedded null character on
     Windows.  In strict mode, it now raises *note OSError: 350. instead
     of the unexpected *note ValueError: 1e7, and in non-strict mode
     will make the path absolute.

   - gh-83180(6): Changes the *note Python Launcher for Windows: 562. to
     prefer an active virtual environment when the launched script has a
     shebang line using a Unix-like virtual command, even if the command
     requests a specific version of Python.

   - gh-106844(7): Fix integer overflow and truncating by the null
     character in ‘_winapi.LCMapStringEx()’ which affects
     ‘ntpath.normcase()’.

   - gh-105436(8): Ensure that an empty environment block is terminated
     by two null characters, as is required by Windows.

   - gh-105146(9): Updated the links at the end of the installer to
     point to Discourse rather than the mailing lists.

   - gh-103646(10): When installed from the Microsoft Store, ‘pip’ no
     longer defaults to per-user installs.  However, as the install
     directory is unwritable, it should automatically decide to do a
     per-user install anyway.  This should resolve issues when ‘pip’ is
     passed an option that conflicts with ‘--user’.

   - gh-88745(11): Improve performance of *note shutil.copy2(): 9fe. by
     using the operating system's ‘CopyFile2’ function.  This may result
     in subtle changes to metadata copied along with some files,
     bringing them in line with normal OS behavior.

   - gh-104820(12): Fixes *note stat(): 448. and related functions on
     file systems that do not support file ID requests.  This includes
     FAT32 and exFAT.

   - gh-104803(13): Add *note os.path.isdevdrive(): 153c. to detect
     whether a path is on a Windows Dev Drive.  Returns ‘False’ on
     platforms that do not support Dev Drive, and is absent on
     non-Windows platforms.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/110437

   (2) https://github.com/python/cpython/issues/109286

   (3) https://github.com/python/cpython/issues/82367

   (4) https://github.com/python/cpython/issues/109991

   (5) https://github.com/python/cpython/issues/106242

   (6) https://github.com/python/cpython/issues/83180

   (7) https://github.com/python/cpython/issues/106844

   (8) https://github.com/python/cpython/issues/105436

   (9) https://github.com/python/cpython/issues/105146

   (10) https://github.com/python/cpython/issues/103646

   (11) https://github.com/python/cpython/issues/88745

   (12) https://github.com/python/cpython/issues/104820

   (13) https://github.com/python/cpython/issues/104803


File: python.info,  Node: macOS<7>,  Next: IDLE<11>,  Prev: Windows<9>,  Up: Python 3 13 0 alpha 1

1.23.13.8 macOS
...............

   - gh-109286(1): Update macOS installer to use SQLite 3.43.1.

   - gh-109991(2): Update macOS installer to use OpenSSL 3.0.11.

   - gh-99079(3): Update macOS installer to use OpenSSL 3.0.9.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/109286

   (2) https://github.com/python/cpython/issues/109991

   (3) https://github.com/python/cpython/issues/99079


File: python.info,  Node: IDLE<11>,  Next: Tools/Demos<5>,  Prev: macOS<7>,  Up: Python 3 13 0 alpha 1

1.23.13.9 IDLE
..............

   - gh-104719(1): Remove IDLE's modification of tokenize.tabsize and
     test other uses of tokenize data and methods.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/104719


File: python.info,  Node: Tools/Demos<5>,  Next: C API<12>,  Prev: IDLE<11>,  Up: Python 3 13 0 alpha 1

1.23.13.10 Tools/Demos
......................

   - gh-109991(1): Update GitHub CI workflows to use OpenSSL 3.0.11 and
     multissltests to use 1.1.1w, 3.0.11, and 3.1.3.

   - gh-108494(2): Argument Clinic(3) now has a partial support of the
     *note Limited API: 318.: see documentation in the Python
     Developer's Guide(4) Patch by Victor Stinner.

   - gh-107704(5): It is now possible to deprecate passing keyword
     arguments for keyword-or-positional parameters with Argument
     Clinic, using the new ‘/ [from X.Y]’ syntax.  (To be read as
     '"positional-only from Python version X.Y"'.) See documentation in
     the Python Developer's Guide(6) for more information.

   - gh-107880(7): Argument Clinic can now clone ‘__init__()’ and
     ‘__new__()’ methods.

   - gh-104683(8): Add ‘--exclude’ option to Argument Clinic CLI.

   - gh-95065(9): Argument Clinic now supports overriding automatically
     generated signature by using directive ‘@text_signature’.  See
     documentation in the Python Developer's Guide(10)

   - gh-107609(11): Fix duplicate module check in Argument Clinic.
     Previously, a duplicate definition would incorrectly be silently
     accepted.  Patch by Erlend E. Aasland.

   - gh-107467(12): The Argument Clinic command-line tool now prints to
     stderr instead of stdout on failure.

   - gh-106970(13): Fix bugs in the Argument Clinic ‘destination <name>
     clear’ command; the destination buffers would never be cleared, and
     the ‘destination’ directive parser would simply continue to the
     fault handler after processing the command.  Patch by Erlend E.
     Aasland.

   - gh-106706(14): Change bytecode syntax for families to remove
     redundant name matching pseudo syntax.

   - gh-106359(15): Argument Clinic now explicitly forbids "kwarg
     splats" in function calls used as annotations.

   - gh-103186(16): ‘freeze’ now fetches ‘CONFIG_ARGS’ from the original
     CPython instance the Makefile uses to call utility scripts.  Patch
     by Ijtaba Hussain.

   - gh-95065(17): It is now possible to deprecate passing parameters
     positionally with Argument Clinic, using the new ‘* [from X.Y]’
     syntax.  (To be read as '"keyword-only from Python version X.Y"'.)
     See documentation in the Python Developer's Guide(18) for more
     information.  Patch by Erlend E. Aasland with help from Alex
     Waygood, Nikita Sobolev, and Serhiy Storchaka.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/109991

   (2) https://github.com/python/cpython/issues/108494

   (3) https://devguide.python.org/development-tools/clinic/

   (4) 
https://devguide.python.org/development-tools/clinic/#clinic-howto-limited-capi

   (5) https://github.com/python/cpython/issues/107704

   (6) 
https://devguide.python.org/development-tools/clinic/#clinic-howto-deprecate-keyword

   (7) https://github.com/python/cpython/issues/107880

   (8) https://github.com/python/cpython/issues/104683

   (9) https://github.com/python/cpython/issues/95065

   (10) 
https://devguide.python.org/development-tools/clinic/#clinic-howto-override-signature

   (11) https://github.com/python/cpython/issues/107609

   (12) https://github.com/python/cpython/issues/107467

   (13) https://github.com/python/cpython/issues/106970

   (14) https://github.com/python/cpython/issues/106706

   (15) https://github.com/python/cpython/issues/106359

   (16) https://github.com/python/cpython/issues/103186

   (17) https://github.com/python/cpython/issues/95065

   (18) 
https://devguide.python.org/development-tools/clinic/#clinic-howto-deprecate-positional


File: python.info,  Node: C API<12>,  Prev: Tools/Demos<5>,  Up: Python 3 13 0 alpha 1

1.23.13.11 C API
................

   - gh-85283(1): If the *note Py_LIMITED_API: 35a. macro is defined,
     ‘Py_BUILD_CORE’, ‘Py_BUILD_CORE_BUILTIN’ and ‘Py_BUILD_CORE_MODULE’
     macros are now undefined by ‘<Python.h>’.  Patch by Victor Stinner.

   - gh-110289(2): Add *note PyUnicode_EqualToUTF8AndSize(): 31c. and
     *note PyUnicode_EqualToUTF8(): 31d. functions.

   - gh-110235(3): Raise *note TypeError: 4dd. for duplicate/unknown
     fields in ‘PyStructSequence’ constructor.  Patched by Xuehai Pan.

   - gh-110014(4): Remove undocumented ‘PY_TIMEOUT_MAX’ constant from
     the limited C API. Patch by Victor Stinner.

   - gh-109521(5): *note PyImport_GetImporter(): 1613. now sets
     RuntimeError if it fails to get *note sys.path_hooks: fc7. or *note
     sys.path_importer_cache: 588. or they are not list and dict
     correspondingly.  Previously it could return NULL without setting
     error in obscure cases, crash or raise SystemError if these
     attributes have wrong type.

   - gh-108724(6): Add *note PyMutex: 140. internal-only lightweight
     locking API.

   - gh-85283(7): Add *note PySys_AuditTuple(): 320. function: similar
     to *note PySys_Audit(): 321, but pass event arguments as a Python
     *note tuple: 322. object.  Patch by Victor Stinner.

   - gh-108867(8): Add *note PyThreadState_GetUnchecked(): 31e.
     function: similar to *note PyThreadState_Get(): 31f, but don't kill
     the process with a fatal error if it is NULL. The caller is
     responsible to check if the result is NULL. Previously, the
     function was private and known as ‘_PyThreadState_UncheckedGet()’.
     Patch by Victor Stinner.

   - gh-108765(9): ‘Python.h’ no longer includes the ‘<ctype.h>’
     standard header file.  If needed, it should now be included
     explicitly.  For example, it provides ‘isalpha()’ and ‘tolower()’
     functions which are locale dependent.  Python provides locale
     independent functions, like ‘Py_ISALPHA()’ and ‘Py_TOLOWER()’.
     Patch by Victor Stinner.

   - gh-108765(10): ‘Python.h’ no longer includes the ‘<unistd.h>’
     standard header file.  If needed, it should now be included
     explicitly.  For example, it provides the functions: ‘close()’,
     ‘getpagesize()’, ‘getpid()’ and ‘sysconf()’.  Patch by Victor
     Stinner.

   - gh-108765(11): ‘Python.h’ no longer includes the ‘<ieeefp.h>’
     standard header.  It was included for the ‘finite()’ function which
     is now provided by the ‘<math.h>’ header.  It should now be
     included explicitly if needed.  Remove also the ‘HAVE_IEEEFP_H’
     macro.  Patch by Victor Stinner.

   - gh-108765(12): ‘Python.h’ no longer includes these standard header
     files: ‘<time.h>’, ‘<sys/select.h>’ and ‘<sys/time.h>’.  If needed,
     they should now be included explicitly.  For example, ‘<time.h>’
     provides the ‘clock()’ and ‘gmtime()’ functions, ‘<sys/select.h>’
     provides the ‘select()’ function, and ‘<sys/time.h>’ provides the
     ‘futimes()’, ‘gettimeofday()’ and ‘setitimer()’ functions.  Patch
     by Victor Stinner.

   - gh-108511(13): Add functions *note PyObject_HasAttrWithError():
     2fc, *note PyObject_HasAttrStringWithError(): 2fe, *note
     PyMapping_HasKeyWithError(): 300. and *note
     PyMapping_HasKeyStringWithError(): 302.

   - gh-107073(14): Add *note PyObject_VisitManagedDict(): 319. and
     *note PyObject_ClearManagedDict(): 31a. functions which must be
     called by the traverse and clear functions of a type using *note
     Py_TPFLAGS_MANAGED_DICT: 31b. flag.  Patch by Victor Stinner.

   - gh-108634(15): Python built with ‘configure’ *note
     -with-trace-refs: 317. (tracing references) now supports the *note
     Limited API: 318.  Patch by Victor Stinner.

   - gh-108014(16): Add *note PyLong_AsInt(): 315. function: similar to
     *note PyLong_AsLong(): 316, but store the result in a C int instead
     of a C long.  Previously, it was known as the private function
     ‘_PyLong_AsInt()’ (with an underscore prefix).  Patch by Victor
     Stinner.

   - gh-108314(17): Add *note PyDict_ContainsString(): 30f. function:
     same as *note PyDict_Contains(): 310, but 'key' is specified as a
     const char* UTF-8 encoded bytes string, rather than a *note
     PyObject: 311.*.  Patch by Victor Stinner.

   - gh-108337(18): Add atomic operations on additional data types in
     pyatomic.h.

   - gh-108014(19): Add *note Py_IsFinalizing(): 314. function: check if
     the main Python interpreter is *note shutting down: 133.  Patch by
     Victor Stinner.

   - gh-107916(20): C API functions *note
     PyErr_SetFromErrnoWithFilename(): 1614, *note
     PyErr_SetExcFromWindowsErrWithFilename(): 1615. and *note
     PyErr_SetFromWindowsErrWithFilename(): 1616. save now the error
     code before calling *note PyUnicode_DecodeFSDefault(): 1617.

   - gh-107915(21): Such C API functions as ‘PyErr_SetString()’,
     ‘PyErr_Format()’, ‘PyErr_SetFromErrnoWithFilename()’ and many
     others no longer crash or ignore errors if it failed to format the
     error message or decode the filename.  Instead, they keep a
     corresponding error.

   - gh-107810(22): Improve *note DeprecationWarning: 18b. for uses of
     *note PyType_Spec: 1618. with metaclasses that have custom
     ‘tp_new’.

   - gh-107249(23): Implement the *note Py_UNUSED: 1619. macro for
     Windows MSVC compiler.  Patch by Victor Stinner.

   - gh-107226(24): *note PyModule_AddObjectRef(): 308. is now only
     available in the limited API version 3.10 or later.

   - gh-106320(25): Remove private ‘_PyUnicode_AsString()’ alias to
     *note PyUnicode_AsUTF8(): b62.  It was kept for backward
     compatibility with Python 3.0 - 3.2.  The *note PyUnicode_AsUTF8():
     b62. is available since Python 3.3.  The *note
     PyUnicode_AsUTF8String(): 1128. function can be used to keep
     compatibility with Python 3.2 and older.  Patch by Victor Stinner.

   - gh-106572(26): Convert *note PyObject_DelAttr(): 161a. and *note
     PyObject_DelAttrString(): 14f5. macros to functions.  Patch by
     Victor Stinner.

   - gh-106307(27): Add *note PyMapping_GetOptionalItem(): 2f7.
     function.

   - gh-106521(28): Add *note PyObject_GetOptionalAttr(): 2f2. and *note
     PyObject_GetOptionalAttrString(): 2f3. functions.

   - gh-106320(29): Remove ‘_PyInterpreterState_Get()’ alias to *note
     PyInterpreterState_Get(): 378. which was kept for backward
     compatibility with Python 3.8.  Patch by Victor Stinner.

   - gh-106316(30): Remove ‘cpython/pytime.h’ header file: it only
     contained private functions.  Patch by Victor Stinner.

   - gh-106023(31): Remove private ‘_PyObject_FastCall()’ function: use
     ‘PyObject_Vectorcall()’ which is available since Python 3.8 ( PEP
     590(32)).  Patch by Victor Stinner.

   - gh-106168(33): If Python is built in *note debug mode: 1de. or
     *note with assertions: 304, *note PyTuple_SET_ITEM(): 305. and
     *note PyList_SET_ITEM(): 306. now check the index argument with an
     assertion.  If the assertion fails, make sure that the size is set
     before.  Patch by Victor Stinner.

   - gh-106084(34): Remove the old aliases to functions calling
     functions which were kept for backward compatibility with Python
     3.8 provisional API:

        * ‘_PyObject_CallMethodNoArgs()’: use
          ‘PyObject_CallMethodNoArgs()’

        * ‘_PyObject_CallMethodOneArg()’: use
          ‘PyObject_CallMethodOneArg()’

        * ‘_PyObject_CallOneArg()’: use ‘PyObject_CallOneArg()’

        * ‘_PyObject_FastCallDict()’: use ‘PyObject_VectorcallDict()’

        * ‘_PyObject_Vectorcall()’: use ‘PyObject_Vectorcall()’

        * ‘_PyObject_VectorcallMethod()’: use
          ‘PyObject_VectorcallMethod()’

        * ‘_PyVectorcall_Function()’: use ‘PyVectorcall_Function()’

     Just remove the underscore prefix to update your code.  Patch by
     Victor Stinner.

   - gh-106004(35): Adds *note PyDict_GetItemRef(): 30a. and *note
     PyDict_GetItemStringRef(): 30b. functions: similar to *note
     PyDict_GetItemWithError(): 30c. but returning a *note strong
     reference: 2ee. instead of a *note borrowed reference: 2ef.  Patch
     by Victor Stinner.

   - gh-105927(36): Deprecate the *note PyWeakref_GetObject(): 2f1. and
     *note PyWeakref_GET_OBJECT(): 38a. functions: use the new *note
     PyWeakref_GetRef(): 2f0. function instead.  Patch by Victor
     Stinner.

   - gh-105927(37): Add *note PyWeakref_GetRef(): 2f0. function: similar
     to *note PyWeakref_GetObject(): 2f1. but returns a *note strong
     reference: 2ee, or ‘NULL’ if the referent is no longer live.  Patch
     by Victor Stinner.

   - gh-105922(38): Add *note PyImport_AddModuleRef(): 2ec.: similar to
     *note PyImport_AddModule(): 2ed, but return a *note strong
     reference: 2ee. instead of a *note borrowed reference: 2ef.  Patch
     by Victor Stinner.

   - gh-105227(39): The new *note PyType_GetDict(): 161b. provides the
     dictionary for the given type object that is normally exposed by
     ‘cls.__dict__’.  Normally it's sufficient to use *note tp_dict:
     161c, but for the static builtin types ‘tp_dict’ is now always
     ‘NULL’.  ‘PyType_GetDict()’ provides the correct dict object
     instead.

   - gh-105375(40): Fix a bug in *note PyErr_WarnExplicit(): 161d. where
     an exception could end up being overwritten if the API failed
     internally.

   - gh-105603(41): We've renamed the new (in 3.12)
     ‘PyInterpreterConfig.own_gil’ to ‘PyInterpreterConfig.gil’ and
     changed the meaning of the value from "bool" to an integer with
     supported values of ‘PyInterpreterConfig_DEFAULT_GIL’,
     ‘PyInterpreterConfig_SHARED_GIL’, and
     ‘PyInterpreterConfig_OWN_GIL’.  The default is "shared".

   - gh-105387(42): In the limited C API version 3.12, *note
     Py_INCREF(): 514. and *note Py_DECREF(): 515. functions are now
     implemented as opaque function calls to hide implementation
     details.  Patch by Victor Stinner.

   - gh-105396(43): Deprecate the *note PyImport_ImportModuleNoBlock():
     388. function which is just an alias to *note
     PyImport_ImportModule(): 389. since Python 3.3.  Patch by Victor
     Stinner.

   - gh-103968(44): *note PyType_FromMetaclass(): 4f6. now allows
     metaclasses with ‘tp_new’ set to ‘NULL’.

   - gh-105268(45): Remove the old private, undocumented and untested
     ‘_PyGC_FINALIZED()’ macro which was kept for backward compatibility
     with Python 3.8 and older.  Patch by Victor Stinner.

   - gh-105182(46): Remove ‘PyEval_AcquireLock()’ and
     ‘PyEval_ReleaseLock()’ functions, deprecated in Python 3.2.  Patch
     by Victor Stinner.

   - gh-105182(47): Remove ‘PyEval_InitThreads()’ and
     ‘PyEval_ThreadsInitialized()’ functions, deprecated in Python 3.9.
     Patch by Victor Stinner.

   - gh-105145(48): Deprecate old Python initialization functions:

        * *note PySys_ResetWarnOptions(): 37a.

        * *note Py_GetExecPrefix(): 37c.

        * *note Py_GetPath(): 37e.

        * *note Py_GetPrefix(): 380.

        * *note Py_GetProgramFullPath(): 382.

        * *note Py_GetProgramName(): 384.

        * *note Py_GetPythonHome(): 385.

     Patch by Victor Stinner.

   - gh-85275(49): ‘PyObject_AsCharBuffer()’, ‘PyObject_AsReadBuffer()’,
     ‘PyObject_CheckReadBuffer()’, and ‘PyObject_AsWriteBuffer()’ are
     removed.  Please migrate to new buffer protocol; *note
     PyObject_GetBuffer(): 369. and *note PyBuffer_Release(): 36a.

   - gh-105156(50): Deprecate the old ‘Py_UNICODE’ and ‘PY_UNICODE_TYPE’
     types: use directly the ‘wchar_t’ type instead.  Since Python 3.3,
     ‘Py_UNICODE’ and ‘PY_UNICODE_TYPE’ are just aliases to ‘wchar_t’.
     Patch by Victor Stinner.

   - gh-105145(51): Remove the following old functions to configure the
     Python initialization, deprecated in Python 3.11:

        * ‘PySys_AddWarnOptionUnicode()’

        * ‘PySys_AddWarnOption()’

        * ‘PySys_AddXOption()’

        * ‘PySys_HasWarnOptions()’

        * ‘PySys_SetArgvEx()’

        * ‘PySys_SetArgv()’

        * ‘PySys_SetPath()’

        * ‘Py_SetPath()’

        * ‘Py_SetProgramName()’

        * ‘Py_SetPythonHome()’

        * ‘Py_SetStandardStreamEncoding()’

        * ‘_Py_SetProgramFullPath()’

     Patch by Victor Stinner.

   - gh-105107(52): Remove functions deprecated in Python 3.9.

        * ‘PyEval_CallObject()’, ‘PyEval_CallObjectWithKeywords()’: use
          *note PyObject_CallNoArgs(): 362. and *note PyObject_Call():
          363. (positional arguments must not be 'NULL') instead.

        * ‘PyEval_CallFunction()’: use *note PyObject_CallFunction():
          365. instead.

        * ‘PyEval_CallMethod()’: use *note PyObject_CallMethod(): 366.
          instead.

        * ‘PyCFunction_Call()’: use *note PyObject_Call(): 363. instead.

     Patch by Victor Stinner.

   - gh-105115(53): ‘PyTypeObject.tp_bases’ (and ‘tp_mro’) for builtin
     static types are now shared by all interpreters, whereas in
     3.12-beta1 they were stored on ‘PyInterpreterState’.  Also note
     that now the tuples are immortal objects.

   - gh-105071(54): Add ‘PyUnstable_Exc_PrepReraiseStar’ to the unstable
     C api to expose the implementation of *note except*: 55c.

   - gh-104922(55): ‘PY_SSIZE_T_CLEAN’ is no longer required to use
     ‘'#'’ formats in APIs like *note PyArg_ParseTuple(): 517. and *note
     Py_BuildValue(): 84c.  They uses ‘Py_ssize_t’ for ‘'#'’ regardless
     ‘PY_SSIZE_T_CLEAN’.

   - gh-104584(56): Add an unstable C API for hooking in an optimizer.
     This is mainly internal, but marked "unstable" to allow third-party
     experimentation.

   - gh-104668(57): Don't call *note PyOS_InputHook: 52b. or *note
     PyOS_ReadlineFunctionPointer: 52c. in subinterpreters, since it's
     generally difficult to avoid using global state in their registered
     callbacks.  This also avoids situations where extensions may find
     themselves running in a subinterpreter they don't support (or
     haven't yet been loaded in).

   - bpo-42327(58): Add *note PyModule_Add(): 307. function: similar to
     *note PyModule_AddObjectRef(): 308. and *note PyModule_AddObject():
     309, but always steals a reference to the value.

   - bpo-40309(59): Properly handle trailing spaces before closing
     parenthesis in *note Py_BuildValue(): 84c. format strings.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/85283

   (2) https://github.com/python/cpython/issues/110289

   (3) https://github.com/python/cpython/issues/110235

   (4) https://github.com/python/cpython/issues/110014

   (5) https://github.com/python/cpython/issues/109521

   (6) https://github.com/python/cpython/issues/108724

   (7) https://github.com/python/cpython/issues/85283

   (8) https://github.com/python/cpython/issues/108867

   (9) https://github.com/python/cpython/issues/108765

   (10) https://github.com/python/cpython/issues/108765

   (11) https://github.com/python/cpython/issues/108765

   (12) https://github.com/python/cpython/issues/108765

   (13) https://github.com/python/cpython/issues/108511

   (14) https://github.com/python/cpython/issues/107073

   (15) https://github.com/python/cpython/issues/108634

   (16) https://github.com/python/cpython/issues/108014

   (17) https://github.com/python/cpython/issues/108314

   (18) https://github.com/python/cpython/issues/108337

   (19) https://github.com/python/cpython/issues/108014

   (20) https://github.com/python/cpython/issues/107916

   (21) https://github.com/python/cpython/issues/107915

   (22) https://github.com/python/cpython/issues/107810

   (23) https://github.com/python/cpython/issues/107249

   (24) https://github.com/python/cpython/issues/107226

   (25) https://github.com/python/cpython/issues/106320

   (26) https://github.com/python/cpython/issues/106572

   (27) https://github.com/python/cpython/issues/106307

   (28) https://github.com/python/cpython/issues/106521

   (29) https://github.com/python/cpython/issues/106320

   (30) https://github.com/python/cpython/issues/106316

   (31) https://github.com/python/cpython/issues/106023

   (32) https://peps.python.org/pep-0590/

   (33) https://github.com/python/cpython/issues/106168

   (34) https://github.com/python/cpython/issues/106084

   (35) https://github.com/python/cpython/issues/106004

   (36) https://github.com/python/cpython/issues/105927

   (37) https://github.com/python/cpython/issues/105927

   (38) https://github.com/python/cpython/issues/105922

   (39) https://github.com/python/cpython/issues/105227

   (40) https://github.com/python/cpython/issues/105375

   (41) https://github.com/python/cpython/issues/105603

   (42) https://github.com/python/cpython/issues/105387

   (43) https://github.com/python/cpython/issues/105396

   (44) https://github.com/python/cpython/issues/103968

   (45) https://github.com/python/cpython/issues/105268

   (46) https://github.com/python/cpython/issues/105182

   (47) https://github.com/python/cpython/issues/105182

   (48) https://github.com/python/cpython/issues/105145

   (49) https://github.com/python/cpython/issues/85275

   (50) https://github.com/python/cpython/issues/105156

   (51) https://github.com/python/cpython/issues/105145

   (52) https://github.com/python/cpython/issues/105107

   (53) https://github.com/python/cpython/issues/105115

   (54) https://github.com/python/cpython/issues/105071

   (55) https://github.com/python/cpython/issues/104922

   (56) https://github.com/python/cpython/issues/104584

   (57) https://github.com/python/cpython/issues/104668

   (58) https://bugs.python.org/issue?@action=redirect&bpo=42327

   (59) https://bugs.python.org/issue?@action=redirect&bpo=40309


File: python.info,  Node: Python 3 12 0 beta 1,  Next: Python 3 12 0 alpha 7,  Prev: Python 3 13 0 alpha 1,  Up: Changelog（更動日誌）

1.23.14 Python 3.12.0 beta 1
----------------------------

'Release date: 2023-05-22'

* Menu:

* Security: Security<9>.
* Core and Builtins: Core and Builtins<14>.
* Library: Library<13>.
* Documentation: Documentation<8>.
* Tests: Tests<11>.
* Build: Build<13>.
* Windows: Windows<10>.
* macOS: macOS<8>.
* IDLE: IDLE<12>.
* Tools/Demos: Tools/Demos<6>.
* C API: C API<13>.


File: python.info,  Node: Security<9>,  Next: Core and Builtins<14>,  Up: Python 3 12 0 beta 1

1.23.14.1 Security
..................

   - gh-99889(1): Fixed a security in flaw in ‘uu.decode()’ that could
     allow for directory traversal based on the input if no ‘out_file’
     was specified.

   - gh-104049(2): Do not expose the local on-disk location in directory
     indexes produced by ‘http.client.SimpleHTTPRequestHandler’.

   - gh-99108(3): Upgrade built-in *note hashlib: 5e. SHA3
     implementation to a verified implementation from the ‘HACL*’
     project.  Used when OpenSSL is not present or lacks SHA3.

   - gh-102153(4): *note urllib.parse.urlsplit(): ce6. now strips
     leading C0 control and space characters following the specification
     for URLs defined by WHATWG in response to CVE-2023-24329(5).  Patch
     by Illia Volochii.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/99889

   (2) https://github.com/python/cpython/issues/104049

   (3) https://github.com/python/cpython/issues/99108

   (4) https://github.com/python/cpython/issues/102153

   (5) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-24329


File: python.info,  Node: Core and Builtins<14>,  Next: Library<13>,  Prev: Security<9>,  Up: Python 3 12 0 beta 1

1.23.14.2 Core and Builtins
...........................

   - gh-102856(1): Implement PEP 701 changes in the *note tokenize: e4.
     module.  Patch by Marta Gómez Macías and Pablo Galindo Salgado

   - gh-104615(2): Fix wrong ordering of assignments in code like ‘a, a
     = x, y’.  Contributed by Carl Meyer.

   - gh-104572(3): Improve syntax error message for invalid constructs
     in PEP 695(4) contexts and in annotations when ‘from __future__
     import annotations’ is active.

   - gh-104482(5): Fix three error handling bugs in ast.c's validation
     of pattern matching statements.

   - gh-102818(6): Do not add a frame to the traceback in the
     ‘sys.setprofile’ and ‘sys.settrace’ trampoline functions.  This
     ensures that frames are not duplicated if an exception is raised in
     the callback function, and ensures that frames are not omitted if a
     C callback is used and that does not add the frame.

   - gh-104405(7): Fix an issue where some *note bytecode: 16d.
     instructions could ignore PEP 523(8) when "inlining" calls.

   - gh-103082(9): Change behavior of ‘sys.monitoring.events.LINE’
     events in ‘sys.monitoring’: Line events now occur when a new line
     is reached dynamically, instead of using a static approximation, as
     before.  This makes the behavior very similar to that of "line"
     events in ‘sys.settrace’.  This should ease porting of tools from
     3.11 to 3.12.

   - gh-104263(10): Fix ‘float("nan")’ to produce a quiet NaN on
     platforms (like MIPS) where the meaning of the signalling / quiet
     bit is inverted from its usual meaning.  Also introduce a new macro
     ‘Py_INFINITY’ matching C99's ‘INFINITY’, and refactor internals to
     rely on C99's ‘NAN’ and ‘INFINITY’ macros instead of hard-coding
     bit patterns for infinities and NaNs.  Thanks Sebastian Berg.

   - gh-99113(11): Multi-phase init extension modules may now indicate
     that they support running in subinterpreters that have their own
     GIL. This is done by using ‘Py_MOD_PER_INTERPRETER_GIL_SUPPORTED’
     as the value for the ‘Py_mod_multiple_interpreters’ module def
     slot.  Otherwise the module, by default, cannot be imported in such
     subinterpreters.  (This does not affect the main interpreter or
     subinterpreters that do not have their own GIL.) In addition to the
     isolation that multi-phase init already normally requires, support
     for per-interpreter GIL involves one additional constraint:
     thread-safety.  If the module has external (linked) dependencies
     and those libraries have any state that isn't thread-safe then the
     module must do the additional work to add thread-safety.  This
     should be an uncommon case.

   - gh-99113(12): The GIL is now (optionally) per-interpreter.  This is
     the fundamental change for PEP 684.  This is all made possible by
     virtue of the isolated state of each interpreter in the process.
     The behavior of the main interpreter remains unchanged.  Likewise,
     interpreters created using ‘Py_NewInterpreter()’ are not affected.
     To get an interpreter with its own GIL, call
     ‘Py_NewInterpreterFromConfig()’.

   - gh-104108(13): Multi-phase init extension modules may now indicate
     whether or not they actually support multiple interpreters.  By
     default such modules are expected to support use in multiple
     interpreters.  In the uncommon case that one does not, it may use
     the new ‘Py_mod_multiple_interpreters’ module def slot.  A value of
     ‘0’ means the module does not support them.  ‘1’ means it does.
     The default is ‘1’.

   - gh-104142(14): Fix an issue where *note list: 5b6. or *note tuple:
     322. repetition could fail to respect PEP 683(15).

   - gh-104078(16): Improve the performance of *note
     PyObject_HasAttrString(): 2ff.

   - gh-104066(17): Improve the performance of *note hasattr(): 479. for
     module objects with a missing attribute.

   - gh-104028(18): Reduce object creation while calling callback
     function from gc.  Patch by Donghee Na.

   - gh-104018(19): Disallow the "z" format specifier in %-format of
     bytes objects.

   - gh-102213(20): Fix performance loss when accessing an object's
     attributes with ‘__getattr__’ defined.

   - gh-103895(21): Improve handling of edge cases in showing
     ‘Exception.__notes__’.  Ensures that the messages always end with a
     newline and that string/bytes are not exploded over multiple lines.
     Patch by Carey Metcalfe.

   - gh-103907(22): Don't modify the refcounts of known immortal objects
     (*note True: bb4, *note False: adb, and *note None: 61b.) in the
     main interpreter loop.

   - gh-103899(23): Provide a helpful hint in the *note TypeError: 4dd.
     message when accidentally calling a *note module: 1555. object that
     has a callable attribute of the same name (such as *note dis.dis():
     ad8. or *note datetime.datetime: 1b0.).

   - gh-103845(24): Remove both line and instruction instrumentation
     before adding new ones for monitoring, to avoid newly added
     instrumentation being removed immediately.

   - gh-103763(25): Implement PEP 695(26), adding syntactic support for
     generic classes, generic functions, and type aliases.

     A new ‘type X = ...’ syntax is added for type aliases, which
     resolves at runtime to an instance of the new class
     ‘typing.TypeAliasType’.  The value is lazily evaluated and is
     accessible through the ‘.__value__’ attribute.  This is implemented
     as a new AST node ‘ast.TypeAlias’.

     New syntax (‘class X[T]: ...’, ‘def func[T](): ...’) is added for
     defining generic functions and classes.  This is implemented as a
     new ‘type_params’ attribute on the AST nodes for classes and
     functions.  This node holds instances of the new AST classes
     ‘ast.TypeVar’, ‘ast.ParamSpec’, and ‘ast.TypeVarTuple’.

     ‘typing.TypeVar’, ‘typing.ParamSpec’, ‘typing.ParamSpecArgs’,
     ‘typing.ParamSpecKwargs’, ‘typing.TypeVarTuple’, and
     ‘typing.Generic’ are now implemented in C rather than Python.

     There are new bytecode instructions ‘LOAD_LOCALS’,
     ‘LOAD_CLASSDICT_OR_GLOBAL’, and ‘LOAD_CLASSDICT_OR_DEREF’ to
     support correct resolution of names in class namespaces.

     Patch by Eric Traut, Larry Hastings, and Jelle Zijlstra.

   - gh-103801(27): Adds three minor linting fixes to the wasm module
     caught that were caught by ruff.

   - gh-103793(28): Optimized asyncio Task creation by deferring
     expensive string formatting (task name generation) from Task
     creation to the first time ‘get_name’ is called.  This makes
     asyncio benchmarks up to 5% faster.

   - gh-102310(29): Change the error range for invalid bytes literals.

   - gh-103590(30): Do not wrap a single exception raised from a
     ‘try-except*’ construct in an *note ExceptionGroup: 19c.

   - gh-103650(31): Change the perf map format to remove the '0x' prefix
     from the addresses

   - gh-102856(32): Implement the required C tokenizer changes for PEP
     701.  Patch by Pablo Galindo Salgado, Lysandros Nikolaou, Batuhan
     Taskaya, Marta Gómez Macías and sunmy2019.

   - gh-100530(33): Clarify the error message raised when the called
     part of a class pattern isn't actually a class.

   - gh-101517(34): Fix bug in line numbers of instructions emitted for
     *note except*: 55c.

   - gh-103492(35): Clarify *note SyntaxWarning: 40c. with literal ‘is’
     comparison by specifying which literal is problematic, since
     comparisons using ‘is’ with e.g.  ‘None’ and bool literals are
     idiomatic.

   - gh-87729(36): Add *note LOAD_SUPER_ATTR: 484. (and a specialization
     for ‘super().method()’) to speed up ‘super().method()’ and
     ‘super().attr’.  This makes ‘super().method()’ roughly 2.3x faster
     and brings it within 20% of the performance of a simple method
     call.  Patch by Vladimir Matveev and Carl Meyer.

   - gh-103488(37): Change the internal offset distinguishing yield and
     return target addresses, so that the instruction pointer is correct
     for exception handling and other stack unwinding.

   - gh-82012(38): The bitwise inversion operator (‘~’) on bool is
     deprecated.  It returns the bitwise inversion of the underlying
     ‘int’ representation such that ‘bool(~True) == True’, which can be
     confusing.  Use ‘not’ for logical negation of bools.  In the rare
     case that you really need the bitwise inversion of the underlying
     ‘int’, convert to int explicitly ‘~int(x)’.

   - gh-77757(39): Exceptions raised in a typeobject's ‘__set_name__’
     method are no longer wrapped by a *note RuntimeError: 179.  Context
     information is added to the exception as a PEP 678(40) note.

   - gh-103333(41): *note AttributeError: 2f6. now retains the ‘name’
     attribute when pickled and unpickled.

   - gh-103242(42): Migrate *note set_ecdh_curve(): 10dc. method not to
     use deprecated OpenSSL APIs.  Patch by Donghee Na.

   - gh-103323(43): We've replaced our use of
     ‘_PyRuntime.tstate_current’ with a thread-local variable.  This is
     a fairly low-level implementation detail, and there should be no
     change in behavior.

   - gh-84436(44): The implementation of PEP-683 which adds Immortal
     Objects by using a fixed reference count that skips reference
     counting to make objects truly immutable.

   - gh-102700(45): Allow built-in modules to be submodules.  This
     allows submodules to be statically linked into a CPython binary.

   - gh-103082(46): Implement PEP 669(47) Low Impact Monitoring for
     CPython.

   - gh-88691(48): Reduce the number of inline *note CACHE: 69c. entries
     for *note CALL: 6ab.

   - gh-102500(49): Make the buffer protocol accessible in Python code
     using the new ‘__buffer__’ and ‘__release_buffer__’ magic methods.
     See PEP 688(50) for details.  Patch by Jelle Zijlstra.

   - gh-97933(51): PEP 709(52): inline list, dict and set comprehensions
     to improve performance and reduce bytecode size.

   - gh-99184(53): Bypass instance attribute access of ‘__name__’ in
     ‘repr’ of *note weakref.ref: f91.

   - gh-98003(54): Complex function calls are now faster and consume no
     C stack space.

   - bpo-39610(55): ‘len()’ for 0-dimensional *note memoryview: 40f.
     objects (such as ‘memoryview(ctypes.c_uint8(42))’) now raises a
     *note TypeError: 4dd.  Previously this returned ‘1’, which was not
     consistent with ‘mem_0d[0]’ raising an *note IndexError: 14a3.

   - bpo-31821(56): Fix ‘pause_reading()’ to work when called from
     ‘connection_made()’ in *note asyncio: 8.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/102856

   (2) https://github.com/python/cpython/issues/104615

   (3) https://github.com/python/cpython/issues/104572

   (4) https://peps.python.org/pep-0695/

   (5) https://github.com/python/cpython/issues/104482

   (6) https://github.com/python/cpython/issues/102818

   (7) https://github.com/python/cpython/issues/104405

   (8) https://peps.python.org/pep-0523/

   (9) https://github.com/python/cpython/issues/103082

   (10) https://github.com/python/cpython/issues/104263

   (11) https://github.com/python/cpython/issues/99113

   (12) https://github.com/python/cpython/issues/99113

   (13) https://github.com/python/cpython/issues/104108

   (14) https://github.com/python/cpython/issues/104142

   (15) https://peps.python.org/pep-0683/

   (16) https://github.com/python/cpython/issues/104078

   (17) https://github.com/python/cpython/issues/104066

   (18) https://github.com/python/cpython/issues/104028

   (19) https://github.com/python/cpython/issues/104018

   (20) https://github.com/python/cpython/issues/102213

   (21) https://github.com/python/cpython/issues/103895

   (22) https://github.com/python/cpython/issues/103907

   (23) https://github.com/python/cpython/issues/103899

   (24) https://github.com/python/cpython/issues/103845

   (25) https://github.com/python/cpython/issues/103763

   (26) https://peps.python.org/pep-0695/

   (27) https://github.com/python/cpython/issues/103801

   (28) https://github.com/python/cpython/issues/103793

   (29) https://github.com/python/cpython/issues/102310

   (30) https://github.com/python/cpython/issues/103590

   (31) https://github.com/python/cpython/issues/103650

   (32) https://github.com/python/cpython/issues/102856

   (33) https://github.com/python/cpython/issues/100530

   (34) https://github.com/python/cpython/issues/101517

   (35) https://github.com/python/cpython/issues/103492

   (36) https://github.com/python/cpython/issues/87729

   (37) https://github.com/python/cpython/issues/103488

   (38) https://github.com/python/cpython/issues/82012

   (39) https://github.com/python/cpython/issues/77757

   (40) https://peps.python.org/pep-0678/

   (41) https://github.com/python/cpython/issues/103333

   (42) https://github.com/python/cpython/issues/103242

   (43) https://github.com/python/cpython/issues/103323

   (44) https://github.com/python/cpython/issues/84436

   (45) https://github.com/python/cpython/issues/102700

   (46) https://github.com/python/cpython/issues/103082

   (47) https://peps.python.org/pep-0669/

   (48) https://github.com/python/cpython/issues/88691

   (49) https://github.com/python/cpython/issues/102500

   (50) https://peps.python.org/pep-0688/

   (51) https://github.com/python/cpython/issues/97933

   (52) https://peps.python.org/pep-0709/

   (53) https://github.com/python/cpython/issues/99184

   (54) https://github.com/python/cpython/issues/98003

   (55) https://bugs.python.org/issue?@action=redirect&bpo=39610

   (56) https://bugs.python.org/issue?@action=redirect&bpo=31821


File: python.info,  Node: Library<13>,  Next: Documentation<8>,  Prev: Core and Builtins<14>,  Up: Python 3 12 0 beta 1

1.23.14.3 Library
.................

   - gh-104600(1): *note functools.update_wrapper(): fc5. now sets the
     ‘__type_params__’ attribute (added by PEP 695(2)).

   - gh-104340(3): When an ‘asyncio’ pipe protocol loses its connection
     due to an error, and the caller doesn't await ‘wait_closed()’ on
     the corresponding ‘StreamWriter’, don't log a warning about an
     exception that was never retrieved.  After all, according to the
     ‘StreamWriter.close()’ docs, the ‘wait_closed()’ call is optional
     ("not mandatory").

   - gh-104555(4): Fix issue where an *note issubclass(): 765. check
     comparing a class ‘X’ against a *note runtime-checkable protocol:
     3e9. ‘Y’ with non-callable members would not cause *note TypeError:
     4dd. to be raised if an *note isinstance(): 3e8. call had
     previously been made comparing an instance of ‘X’ to ‘Y’.  This
     issue was present in edge cases on Python 3.11, but became more
     prominent in 3.12 due to some unrelated changes that were made to
     runtime-checkable protocols.  Patch by Alex Waygood.

   - gh-104372(5): Refactored the ‘_posixsubprocess’ internals to avoid
     Python C API usage between fork and exec when marking ‘pass_fds=’
     file descriptors inheritable.

   - gh-104484(6): Added 'case_sensitive' argument to *note
     pathlib.PurePath.match(): 454.

   - gh-75367(7): Fix data descriptor detection in *note
     inspect.getattr_static(): 43c.

   - gh-104536(8): Fix a race condition in the internal
     ‘multiprocessing.process’ cleanup logic that could manifest as an
     unintended ‘AttributeError’ when calling ‘process.close()’.

   - gh-103857(9): Update datetime deprecations' stracktrace to point to
     the calling line

   - gh-101520(10): Move the core functionality of the ‘tracemalloc’
     module in the ‘Python/’ folder, leaving just the module wrapper in
     ‘Modules/’.

   - gh-104392(11): Remove undocumented and unused ‘_paramspec_tvars’
     attribute from some classes in *note typing: ed.

   - gh-102613(12): Fix issue where *note pathlib.Path.glob(): 212.
     raised *note RecursionError: d12. when walking deep directory
     trees.

   - gh-103000(13): Improve performance of *note dataclasses.asdict():
     1622. for the common case where 'dict_factory' is ‘dict’.  Patch by
     David C Ellis.

   - gh-104301(14): Allow leading whitespace in disambiguated statements
     in *note pdb: 94.

   - gh-104139(15): Teach ‘urllib.parse.unsplit()’ to retain the ‘"//"’
     when assembling ‘itms-services://?action=generate-bugs’ style Apple
     Platform Deployment(16) URLs.

   - gh-104307(17): *note socket.getnameinfo(): 15be. now releases the
     GIL while contacting the DNS server

   - gh-104310(18): Users may now use
     ‘importlib.util.allowing_all_extensions()’ (a context manager) to
     temporarily disable the strict compatibility checks for importing
     extension modules in subinterpreters.

   - gh-87695(19): Fix issue where *note pathlib.Path.glob(): 212.
     raised *note OSError: 350. when it encountered a symlink to an
     overly long path.

   - gh-104265(20): Prevent possible crash by disallowing instantiation
     of the ‘_csv.Reader’ and ‘_csv.Writer’ types.  The regression was
     introduced in 3.10.0a4 with PR 23224 (bpo-14935(21)).  Patch by
     Radislav Chugunov.

   - gh-102613(22): Improve performance of *note pathlib.Path.glob():
     212. when expanding recursive wildcards ("‘**’") by merging
     adjacent wildcards and de-duplicating results only when necessary.

   - gh-65772(23): Remove unneeded comments and code in turtle.py.

   - gh-90208(24): Fixed issue where *note pathlib.Path.glob(): 212.
     returned incomplete results when it encountered a *note
     PermissionError: ce9.  This method now suppresses all *note
     OSError: 350. exceptions, except those raised from calling *note
     is_dir(): 215. on the top-level path.

   - gh-104144(25): Optimize *note asyncio.TaskGroup: 19b. when using
     *note asyncio.eager_task_factory(): 41e.  Skip scheduling a done
     callback if a TaskGroup task completes eagerly.

   - gh-104144(26): Optimize *note asyncio.gather(): 5a2. when using
     *note asyncio.eager_task_factory(): 41e. to complete eagerly if all
     fututres completed eagerly.  Avoid scheduling done callbacks for
     futures that complete eagerly.

   - gh-104114(27): Fix issue where *note pathlib.Path.glob(): 212.
     returns paths using the case of non-wildcard segments for
     corresponding path segments, rather than the real filesystem case.

   - gh-104104(28): Improve performance of *note pathlib.Path.glob():
     212. by using *note re.IGNORECASE: 1623. to implement
     case-insensitive matching.

   - gh-104102(29): Improve performance of *note pathlib.Path.glob():
     212. when evaluating patterns that contain ‘'../'’ segments.

   - gh-103822(30): Update the return type of ‘weekday’ to the newly
     added Day attribute

   - gh-103629(31): Update the ‘repr’ of *note typing.Unpack: 1523.
     according to PEP 692(32).

   - gh-103963(33): Make *note dis: 30. display the names of the args
     for ‘CALL_INTRINSIC_*’.

   - gh-104035(34): Do not ignore user-defined ‘__getstate__’ and
     ‘__setstate__’ methods for slotted frozen dataclasses.

   - gh-103987(35): In *note mmap: 83, fix several bugs that could lead
     to access to memory-mapped files after they have been invalidated.

   - gh-103977(36): Improve import time of *note platform: 98. module.

   - gh-88773(37): Added *note turtle.teleport(): 1624. to the *note
     turtle: ea. module to move a turtle to a new point without tracing
     a line, visible or invisible.  Patch by Liam Gersten.

   - gh-103935(38): Use *note io.open_code(): 1625. for files to be
     executed instead of raw *note open(): 4c0.

   - gh-68968(39): Fixed garbled output of *note assertEqual(): 4cd.
     when an input lacks final newline.

   - gh-100370(40): Fix potential *note OverflowError: 825. in *note
     sqlite3.Connection.blobopen(): 627. for 32-bit builds.  Patch by
     Erlend E. Aasland.

   - gh-102628(41): Substitute CTRL-D with CTRL-Z in *note sqlite3: ba.
     CLI banner when running on Windows.

   - gh-103636(42): Module-level attributes ‘January’ and ‘February’ are
     deprecated from *note calendar: 10.

   - gh-103583(43): Isolate ‘_multibytecodec’ and codecs extension
     modules.  Patches by Erlend E. Aasland.

   - gh-103848(44): Add checks to ensure that ‘[’ bracketed ‘]’ hosts
     found by *note urllib.parse.urlsplit(): ce6. are of IPv6 or
     IPvFuture format.

   - gh-103872(45): Update the bundled copy of pip to version 23.1.2.

   - gh-99944(46): Make *note dis: 30. display the value of oparg of
     ‘KW_NAMES’.

   - gh-74940(47): The C.UTF-8 locale is no longer converted to
     en_US.UTF-8, enabling the use of UTF-8 encoding on systems which
     have no locales installed.

   - gh-103861(48): Fix ‘zipfile.Zipfile’ creating invalid zip files
     when ‘force_zip64’ was used to add files to them.  Patch by Carey
     Metcalfe.

   - gh-103857(49): Deprecated *note datetime.datetime.utcnow(): 2cd.
     and *note datetime.datetime.utcfromtimestamp(): 2ce.  (Patch by
     Paul Ganssle)

   - gh-103839(50): Avoid compilation error due to tommath.h not being
     found when building Tkinter against Tcl 8.7 built with bundled
     libtommath.

   - gh-103791(51): *note contextlib.suppress: eca. now supports
     suppressing exceptions raised as part of an *note ExceptionGroup:
     19c.  If other exceptions exist on the group, they are re-raised in
     a group that does not contain the suppressed exceptions.

   - gh-90750(52): Use *note datetime.datetime.fromisocalendar(): 991.
     in the implementation of *note datetime.datetime.strptime(): 14fe,
     which should now accept only valid ISO dates.  (Patch by Paul
     Ganssle)

   - gh-103685(53): Prepare ‘tkinter.Menu.index()’ for Tk 8.7 so that it
     does not raise ‘TclError: expected integer but got ""’ when it
     should return ‘None’.

   - gh-81403(54): *note urllib.request.CacheFTPHandler: 1626. no longer
     raises ‘URLError’ if a cached FTP instance is reused.  ftplib's
     endtransfer method calls voidresp to drain the connection to handle
     FTP instance reuse properly.

   - gh-103699(55): Add ‘__orig_bases__’ to non-generic TypedDicts,
     call-based TypedDicts, and call-based NamedTuples.  Other
     TypedDicts and NamedTuples already had the attribute.

   - gh-103693(56): Add convenience variable feature to *note pdb: 94.

   - gh-92248(57): Deprecate ‘type’, ‘choices’, and ‘metavar’ parameters
     of ‘argparse.BooleanOptionalAction’.

   - gh-89415(58): Add *note socket: b8. constants for source-specific
     multicast.  Patch by Reese Hyde.

   - gh-103673(59): *note socketserver: b9. gains
     ‘ForkingUnixStreamServer’ and ‘ForkingUnixDatagramServer’ classes.
     Patch by Jay Berry.

   - gh-103636(60): Added Enum for months and days in the calendar
     module.

   - gh-84976(61): Create a new ‘Lib/_pydatetime.py’ file that defines
     the Python version of the ‘datetime’ module, and make ‘datetime’
     import the contents of the new library only if the C implementation
     is missing.  Currently, the full Python implementation is defined
     and then deleted if the C implementation is not available, slowing
     down ‘import datetime’ unnecessarily.

   - gh-103596(62): Attributes/methods are no longer shadowed by
     same-named enum members, although they may be shadowed by
     enum.property's.

   - gh-103584(63): Updated ‘importlib.metadata’ with changes from
     ‘importlib_metadata’ 5.2 through 6.5.0, including: Support
     ‘installed-files.txt’ for ‘Distribution.files’ when present.
     ‘PackageMetadata’ now stipulates an additional ‘get’ method
     allowing for easy querying of metadata keys that may not be
     present.  ‘packages_distributions’ now honors packages and modules
     with Python modules that not ‘.py’ sources (e.g.  ‘.pyc’, ‘.so’).
     Expand protocol for ‘PackageMetadata.get_all’ to match the upstream
     implementation of ‘email.message.Message.get_all’ in
     python/typeshed#9620.  Deprecated use of ‘Distribution’ without
     defining abstract methods.  Deprecated expectation that
     ‘PackageMetadata.__getitem__’ will return ‘None’ for missing keys.
     In the future, it will raise a ‘KeyError’.

   - gh-103578(64): Fixed a bug where *note pdb: 94. crashes when
     reading source file with different encoding by replacing *note
     io.open(): 4c1. with *note io.open_code(): 1625.  The new method
     would also call into the hook set by *note
     PyFile_SetOpenCodeHook(): 1627.

   - gh-103556(65): Now creating *note inspect.Signature: 1b3. objects
     with positional-only parameter with a default followed by a
     positional-or-keyword parameter without one is impossible.

   - gh-103559(66): Update the bundled copy of pip to version 23.1.1.

   - gh-103548(67): Improve performance of *note
     pathlib.Path.absolute(): 15a6. and *note cwd(): 1628. by joining
     paths only when necessary.  Also improve performance of *note
     pathlib.PurePath.is_absolute(): 1629. on Posix by skipping path
     parsing and normalization.

   - gh-103538(68): Remove ‘_tkinter’ module code guarded by definition
     of the ‘TK_AQUA’ macro which was only needed for Tk 8.4.7 or
     earlier and was never actually defined by any build system or
     documented for manual use.

   - gh-103533(69): Update *note cProfile: 20. to use PEP 669 API

   - gh-103525(70): Fix misleading exception message when mixed ‘str’
     and ‘bytes’ arguments are supplied to *note pathlib.PurePath: 44e.
     and *note Path: 20e.

   - gh-103489(71): Add *note getconfig(): 460. and *note setconfig():
     461. to *note Connection: 22a. to make configuration changes to a
     database connection.  Patch by Erlend E. Aasland.

   - gh-103365(72): Set default Flag boundary to ‘STRICT’ and fix
     bitwise operations.

   - gh-103472(73): Avoid a potential *note ResourceWarning: 229. in
     *note http.client.HTTPConnection: ae4. by closing the proxy /
     tunnel's CONNECT response explicitly.

   - gh-103462(74): Fixed an issue with using *note writelines(): 162a.
     in *note asyncio: 8. to send very large payloads that exceed the
     amount of data that can be written in one call to *note
     socket.socket.send(): d4d. or *note socket.socket.sendmsg(): 41d,
     resulting in the remaining buffer being left unwritten.

   - gh-103449(75): Fix a bug in doc string generation in *note
     dataclasses.dataclass(): 1af.

   - gh-103092(76): Isolate ‘_collections’ (apply PEP 687(77)).  Patch
     by Erlend E. Aasland.

   - gh-103357(78): Added support for *note logging.Formatter: 1400.
     ‘defaults’ parameter to *note logging.config.dictConfig(): 1147.
     and *note logging.config.fileConfig(): af5.  Patch by Bar Harel.

   - gh-103092(79): Adapt the *note winreg: fe. extension module to PEP
     687(80).

   - gh-74690(81): The performance of *note isinstance(): 3e8. checks
     against *note runtime-checkable protocols: 3e9. has been
     considerably improved for protocols that only have a few members.
     To achieve this improvement, several internal implementation
     details of the *note typing: ed. module have been refactored,
     including ‘typing._ProtocolMeta.__instancecheck__’,
     ‘typing._is_callable_members_only’, and
     ‘typing._get_protocol_attrs’.  Patches by Alex Waygood.

   - gh-74690(82): The members of a runtime-checkable protocol are now
     considered "frozen" at runtime as soon as the class has been
     created.  See *note "What's new in Python 3.12": 478. for more
     details.

   - gh-103256(83): Fixed a bug that caused *note hmac: 60. to raise an
     exception when the requested hash algorithm was not available in
     OpenSSL despite being available separately as part of ‘hashlib’
     itself.  It now falls back properly to the built-in.  This could
     happen when, for example, your OpenSSL does not include SHA3
     support and you want to compute ‘hmac.digest(b'K', b'M',
     'sha3_256')’.

   - gh-102778(84): Support ‘sys.last_exc’ in *note idlelib: 69.

   - gh-103285(85): Improve performance of *note
     ast.get_source_segment(): 97b.

   - gh-103225(86): Fix a bug in *note pdb: 94. when displaying line
     numbers of module-level source code.

   - gh-103092(87): Adapt the *note msvcrt: 85. extension module to PEP
     687(88).

   - gh-103092(89): Adapt the *note winsound: ff. extension module to
     PEP 687(90).

   - gh-93910(91): Remove deprecation of enum ‘member.member’ access.

   - gh-102978(92): Fixes *note unittest.mock.patch(): e34. not
     enforcing function signatures for methods decorated with
     ‘@classmethod’ or ‘@staticmethod’ when patch is called with
     ‘autospec=True’.

   - gh-103092(93): Isolate ‘_socket’ (apply PEP 687(94)).  Patch by
     Erlend E. Aasland.

   - gh-100479(95): Add *note pathlib.PurePath.with_segments(): 44f,
     which creates a path object from arguments.  This method is called
     whenever a derivative path is created, such as from *note
     pathlib.PurePath.parent: 162b.  Subclasses may override this method
     to share information between path objects.

   - gh-103220(96): Fix issue where *note os.path.join(): 1527. added a
     slash when joining onto an incomplete UNC drive with a trailing
     slash on Windows.

   - gh-103204(97): Fixes *note http.server: 68. accepting HTTP requests
     with HTTP version numbers preceded by '+', or '-', or with
     digit-separating '_' characters.  The length of the version numbers
     is also constrained.

   - gh-75586(98): Fix various Windows-specific issues with
     ‘shutil.which’.

   - gh-103193(99): Improve performance of *note
     inspect.getattr_static(): 43c.  Patch by Alex Waygood.

   - gh-103176(100): *note sys._current_exceptions(): 469. now returns a
     mapping from thread-id to an exception instance, rather than to a
     ‘(typ, exc, tb)’ tuple.

   - gh-103143(101): Polish the help messages and docstrings of *note
     pdb: 94.

   - gh-103015(102): Add 'entrypoint' keyword-only parameter to *note
     sqlite3.Connection.load_extension(): 45f, for overriding the SQLite
     extension entry point.  Patch by Erlend E. Aasland.

   - gh-103000(103): Improve performance of *note dataclasses.astuple():
     162c. and *note dataclasses.asdict(): 1622. in cases where the
     contents are common Python types.

   - gh-102953(104): The extraction methods in *note tarfile: c8, and
     *note shutil.unpack_archive(): 412, 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 *note Extraction filters: 413. for details.

   - gh-97696(105): Implemented an eager task factory in asyncio.  When
     used as a task factory on an event loop, it performs eager
     execution of coroutines.  Coroutines that are able to complete
     synchronously (e.g.  return or raise without blocking) are returned
     immediately as a finished task, and the task is never scheduled to
     the event loop.  If the coroutine blocks, the (pending) task is
     scheduled and returned.

   - gh-81079(106): Add 'case_sensitive' keyword-only argument to *note
     pathlib.Path.glob(): 212. and *note rglob(): 213.

   - gh-101819(107): Isolate the *note io: 73. extension module by
     applying PEP 687(108).  Patch by Kumar Aditya, Victor Stinner, and
     Erlend E. Aasland.

   - gh-91896(109): Deprecate *note collections.abc.ByteString: 2a4.

   - gh-101362(110): Speed up *note pathlib.Path: 20e. construction by
     omitting the path anchor from the internal list of path parts.

   - gh-102114(111): Functions in the *note dis: 30. module that accept
     a source code string as argument now print a more concise traceback
     when the string contains a syntax or indentation error.

   - gh-62432(112): The *note unittest: ef. runner will now exit with
     status code 5 if no tests were run.  It is common for test runner
     misconfiguration to fail to find any tests, this should be an
     error.

   - gh-78079(113): Fix incorrect normalization of UNC device path
     roots, and partial UNC share path roots, in *note pathlib.PurePath:
     44e.  Pathlib no longer appends a trailing slash to such paths.

   - gh-85984(114): Add *note tty.cfmakeraw(): 15c7. and *note
     tty.cfmakecbreak(): 156f. to *note tty: e9. and modernize, the
     behavior of *note tty.setraw(): 15c6. and *note tty.setcbreak():
     156e. to use POSIX.1-2017 Chapter 11 "General Terminal Interface"
     flag masks by default.

   - gh-101688(115): Implement *note types.get_original_bases(): 475. to
     provide further introspection for types.

   - gh-101640(116): *note argparse.ArgumentParser: 4de. now catches
     errors when writing messages, such as when *note sys.stderr: 8dd.
     is ‘None’.  Patch by Oleg Iarygin.

   - gh-83861(117): Fix datetime.astimezone method return value when
     invoked on a naive datetime instance that represents local time
     falling in a timezone transition gap.  PEP 495 requires that
     instances with fold=1 produce earlier times than those with fold=0
     in this case.

   - gh-89550(118): Decrease execution time of some *note gzip: 5d. file
     writes by 15% by adding more appropriate buffering.

   - gh-95299(119): Remove the bundled setuptools wheel from
     ‘ensurepip’, and stop installing setuptools in environments created
     by ‘venv’.

   - gh-99353(120): Respect the *note http.client.HTTPConnection: ae4.
     ‘.debuglevel’ flag in ‘urllib.request.AbstractHTTPHandler’ when its
     constructor parameter ‘debuglevel’ is not set.  And do the same for
     ‘*HTTPS*’.

   - gh-98040(121): Remove the long-deprecated ‘imp’ module.

   - gh-97850(122): Deprecate *note pkgutil.find_loader(): 2ad. and
     *note pkgutil.get_loader(): 2ae. in favor of *note
     importlib.util.find_spec(): 2af.

   - gh-94473(123): Flatten arguments in ‘tkinter.Canvas.coords()’.  It
     now accepts not only ‘x1, y1, x2, y2, ...’ and ‘[x1, y1, x2, y2,
     ...]’, but also ‘(x1, y1), (x2, y2), ...’ and ‘[(x1, y1), (x2, y2),
     ...]’.

   - gh-98040(124): Remove more deprecated importlib APIs:
     ‘find_loader()’, ‘find_module()’, ‘importlib.abc.Finder’,
     ‘pkgutil.ImpImporter’, ‘pkgutil.ImpLoader’.

   - gh-96522(125): Fix potential deadlock in pty.spawn()

   - gh-96534(126): Support divert(4) added in FreeBSD 14.

   - gh-87474(127): Fix potential file descriptor leaks in *note
     subprocess.Popen: 17d.

   - gh-94906(128): Support multiple steps in *note math.nextafter():
     440.  Patch by Shantanu Jain and Matthias Gorgens.

   - gh-51574(129): Make *note tempfile.mkdtemp(): 204. return absolute
     paths when its 'dir' parameter is relative.

   - gh-94518(130): Convert private ‘_posixsubprocess.fork_exec()’ to
     use Argument Clinic.

   - gh-92184(131): When creating zip files using *note zipfile: 117,
     ‘os.altsep’, if not ‘None’, will always be treated as a path
     separator even when it is not ‘/’.  Patch by Carey Metcalfe.

   - bpo-46797(132): Deprecation warnings are now emitted for ‘ast.Num’,
     ‘ast.Bytes’, ‘ast.Str’, ‘ast.NameConstant’ and ‘ast.Ellipsis’.
     These have been documented as deprecated since Python 3.8, and will
     be removed in Python 3.14.

   - bpo-44844(133): Enables *note webbrowser: fd. to detect and launch
     Microsoft Edge browser.

   - bpo-45606(134): Fixed the bug in *note pathlib.Path.glob(): 212. -
     previously a dangling symlink would not be found by this method
     when the pattern is an exact match, but would be found when the
     pattern contains a wildcard or the recursive wildcard (‘**’).  With
     this change, a dangling symlink will be found in both cases.

   - bpo-23041(135): Add *note QUOTE_STRINGS: 42c. and *note
     QUOTE_NOTNULL: 42b. to the suite of *note csv: 21. module quoting
     styles.

   - bpo-24964(136): Added *note
     http.client.HTTPConnection.get_proxy_response_headers(): 15ff. that
     provides access to the HTTP headers on a proxy server response to
     the ‘CONNECT’ request.

   - bpo-17258(137): *note multiprocessing: 86. now supports stronger
     HMAC algorithms for inter-process connection authentication rather
     than only HMAC-MD5.

   - bpo-39744(138): Make *note
     asyncio.subprocess.Process.communicate(): 162d. close the
     subprocess's stdin even when called with ‘input=None’.

   - bpo-22708(139): http.client CONNECT method tunnel improvements: Use
     HTTP 1.1 protocol; send a matching Host: header with CONNECT, if
     one is not provided; convert IDN domain names to Punycode.  Patch
     by Michael Handler.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/104600

   (2) https://peps.python.org/pep-0695/

   (3) https://github.com/python/cpython/issues/104340

   (4) https://github.com/python/cpython/issues/104555

   (5) https://github.com/python/cpython/issues/104372

   (6) https://github.com/python/cpython/issues/104484

   (7) https://github.com/python/cpython/issues/75367

   (8) https://github.com/python/cpython/issues/104536

   (9) https://github.com/python/cpython/issues/103857

   (10) https://github.com/python/cpython/issues/101520

   (11) https://github.com/python/cpython/issues/104392

   (12) https://github.com/python/cpython/issues/102613

   (13) https://github.com/python/cpython/issues/103000

   (14) https://github.com/python/cpython/issues/104301

   (15) https://github.com/python/cpython/issues/104139

   (16) 
https://support.apple.com/en-gb/guide/deployment/depce7cefc4d/web

   (17) https://github.com/python/cpython/issues/104307

   (18) https://github.com/python/cpython/issues/104310

   (19) https://github.com/python/cpython/issues/87695

   (20) https://github.com/python/cpython/issues/104265

   (21) https://bugs.python.org/issue?@action=redirect&bpo=14935

   (22) https://github.com/python/cpython/issues/102613

   (23) https://github.com/python/cpython/issues/65772

   (24) https://github.com/python/cpython/issues/90208

   (25) https://github.com/python/cpython/issues/104144

   (26) https://github.com/python/cpython/issues/104144

   (27) https://github.com/python/cpython/issues/104114

   (28) https://github.com/python/cpython/issues/104104

   (29) https://github.com/python/cpython/issues/104102

   (30) https://github.com/python/cpython/issues/103822

   (31) https://github.com/python/cpython/issues/103629

   (32) https://peps.python.org/pep-0692/

   (33) https://github.com/python/cpython/issues/103963

   (34) https://github.com/python/cpython/issues/104035

   (35) https://github.com/python/cpython/issues/103987

   (36) https://github.com/python/cpython/issues/103977

   (37) https://github.com/python/cpython/issues/88773

   (38) https://github.com/python/cpython/issues/103935

   (39) https://github.com/python/cpython/issues/68968

   (40) https://github.com/python/cpython/issues/100370

   (41) https://github.com/python/cpython/issues/102628

   (42) https://github.com/python/cpython/issues/103636

   (43) https://github.com/python/cpython/issues/103583

   (44) https://github.com/python/cpython/issues/103848

   (45) https://github.com/python/cpython/issues/103872

   (46) https://github.com/python/cpython/issues/99944

   (47) https://github.com/python/cpython/issues/74940

   (48) https://github.com/python/cpython/issues/103861

   (49) https://github.com/python/cpython/issues/103857

   (50) https://github.com/python/cpython/issues/103839

   (51) https://github.com/python/cpython/issues/103791

   (52) https://github.com/python/cpython/issues/90750

   (53) https://github.com/python/cpython/issues/103685

   (54) https://github.com/python/cpython/issues/81403

   (55) https://github.com/python/cpython/issues/103699

   (56) https://github.com/python/cpython/issues/103693

   (57) https://github.com/python/cpython/issues/92248

   (58) https://github.com/python/cpython/issues/89415

   (59) https://github.com/python/cpython/issues/103673

   (60) https://github.com/python/cpython/issues/103636

   (61) https://github.com/python/cpython/issues/84976

   (62) https://github.com/python/cpython/issues/103596

   (63) https://github.com/python/cpython/issues/103584

   (64) https://github.com/python/cpython/issues/103578

   (65) https://github.com/python/cpython/issues/103556

   (66) https://github.com/python/cpython/issues/103559

   (67) https://github.com/python/cpython/issues/103548

   (68) https://github.com/python/cpython/issues/103538

   (69) https://github.com/python/cpython/issues/103533

   (70) https://github.com/python/cpython/issues/103525

   (71) https://github.com/python/cpython/issues/103489

   (72) https://github.com/python/cpython/issues/103365

   (73) https://github.com/python/cpython/issues/103472

   (74) https://github.com/python/cpython/issues/103462

   (75) https://github.com/python/cpython/issues/103449

   (76) https://github.com/python/cpython/issues/103092

   (77) https://peps.python.org/pep-0687/

   (78) https://github.com/python/cpython/issues/103357

   (79) https://github.com/python/cpython/issues/103092

   (80) https://peps.python.org/pep-0687/

   (81) https://github.com/python/cpython/issues/74690

   (82) https://github.com/python/cpython/issues/74690

   (83) https://github.com/python/cpython/issues/103256

   (84) https://github.com/python/cpython/issues/102778

   (85) https://github.com/python/cpython/issues/103285

   (86) https://github.com/python/cpython/issues/103225

   (87) https://github.com/python/cpython/issues/103092

   (88) https://peps.python.org/pep-0687/

   (89) https://github.com/python/cpython/issues/103092

   (90) https://peps.python.org/pep-0687/

   (91) https://github.com/python/cpython/issues/93910

   (92) https://github.com/python/cpython/issues/102978

   (93) https://github.com/python/cpython/issues/103092

   (94) https://peps.python.org/pep-0687/

   (95) https://github.com/python/cpython/issues/100479

   (96) https://github.com/python/cpython/issues/103220

   (97) https://github.com/python/cpython/issues/103204

   (98) https://github.com/python/cpython/issues/75586

   (99) https://github.com/python/cpython/issues/103193

   (100) https://github.com/python/cpython/issues/103176

   (101) https://github.com/python/cpython/issues/103143

   (102) https://github.com/python/cpython/issues/103015

   (103) https://github.com/python/cpython/issues/103000

   (104) https://github.com/python/cpython/issues/102953

   (105) https://github.com/python/cpython/issues/97696

   (106) https://github.com/python/cpython/issues/81079

   (107) https://github.com/python/cpython/issues/101819

   (108) https://peps.python.org/pep-0687/

   (109) https://github.com/python/cpython/issues/91896

   (110) https://github.com/python/cpython/issues/101362

   (111) https://github.com/python/cpython/issues/102114

   (112) https://github.com/python/cpython/issues/62432

   (113) https://github.com/python/cpython/issues/78079

   (114) https://github.com/python/cpython/issues/85984

   (115) https://github.com/python/cpython/issues/101688

   (116) https://github.com/python/cpython/issues/101640

   (117) https://github.com/python/cpython/issues/83861

   (118) https://github.com/python/cpython/issues/89550

   (119) https://github.com/python/cpython/issues/95299

   (120) https://github.com/python/cpython/issues/99353

   (121) https://github.com/python/cpython/issues/98040

   (122) https://github.com/python/cpython/issues/97850

   (123) https://github.com/python/cpython/issues/94473

   (124) https://github.com/python/cpython/issues/98040

   (125) https://github.com/python/cpython/issues/96522

   (126) https://github.com/python/cpython/issues/96534

   (127) https://github.com/python/cpython/issues/87474

   (128) https://github.com/python/cpython/issues/94906

   (129) https://github.com/python/cpython/issues/51574

   (130) https://github.com/python/cpython/issues/94518

   (131) https://github.com/python/cpython/issues/92184

   (132) https://bugs.python.org/issue?@action=redirect&bpo=46797

   (133) https://bugs.python.org/issue?@action=redirect&bpo=44844

   (134) https://bugs.python.org/issue?@action=redirect&bpo=45606

   (135) https://bugs.python.org/issue?@action=redirect&bpo=23041

   (136) https://bugs.python.org/issue?@action=redirect&bpo=24964

   (137) https://bugs.python.org/issue?@action=redirect&bpo=17258

   (138) https://bugs.python.org/issue?@action=redirect&bpo=39744

   (139) https://bugs.python.org/issue?@action=redirect&bpo=22708


File: python.info,  Node: Documentation<8>,  Next: Tests<11>,  Prev: Library<13>,  Up: Python 3 12 0 beta 1

1.23.14.4 Documentation
.......................

   - gh-67056(1): Document that the effect of registering or
     unregistering an *note atexit: 9. cleanup function from within a
     registered cleanup function is undefined.

   - gh-103629(2): Mention the new way of typing ‘**kwargs’ with
     ‘Unpack’ and ‘TypedDict’ introduced in PEP 692(3).

   - gh-48241(4): Clarifying documentation about the url parameter to
     urllib.request.urlopen and urllib.request.Request needing to be
     encoded properly.

   - gh-86094(5): Add support for Unicode Path Extra Field in ZipFile.
     Patch by Yeojin Kim and Andrea Giudiceandrea

   - gh-99202(6): Fix extension type from documentation for compiling in
     C++20 mode

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/67056

   (2) https://github.com/python/cpython/issues/103629

   (3) https://peps.python.org/pep-0692/

   (4) https://github.com/python/cpython/issues/48241

   (5) https://github.com/python/cpython/issues/86094

   (6) https://github.com/python/cpython/issues/99202


File: python.info,  Node: Tests<11>,  Next: Build<13>,  Prev: Documentation<8>,  Up: Python 3 12 0 beta 1

1.23.14.5 Tests
...............

   - gh-104494(1): Update ‘test_pack_configure_in’ and
     ‘test_place_configure_in’ for changes to error message formatting
     in Tk 8.7.

   - gh-104461(2): Run test_configure_screen on X11 only, since the
     ‘DISPLAY’ environment variable and ‘-screen’ option for toplevels
     are not useful on Tk for Win32 or Aqua.

   - gh-86275(3): Added property-based tests to the *note zoneinfo: 11a.
     tests, along with stubs for the ‘hypothesis’ interface.  (Patch by
     Paul Ganssle)

   - gh-103329(4): Regression tests for the behaviour of
     ‘unittest.mock.PropertyMock’ were added.

   - gh-102795(5): fix use of poll in test_epoll's test_control_and_wait

   - gh-75729(6): Fix the *note os.spawn*: 1630. tests failing on
     Windows when the working directory or interpreter path contains
     spaces.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/104494

   (2) https://github.com/python/cpython/issues/104461

   (3) https://github.com/python/cpython/issues/86275

   (4) https://github.com/python/cpython/issues/103329

   (5) https://github.com/python/cpython/issues/102795

   (6) https://github.com/python/cpython/issues/75729


File: python.info,  Node: Build<13>,  Next: Windows<10>,  Prev: Tests<11>,  Up: Python 3 12 0 beta 1

1.23.14.6 Build
...............

   - gh-101282(1): BOLT optimization is now applied to the libpython
     shared library if building a shared library.  BOLT instrumentation
     and application settings can now be influenced via the
     ‘BOLT_INSTRUMENT_FLAGS’ and ‘BOLT_APPLY_FLAGS’ configure variables.

   - gh-99017(2): ‘PYTHON_FOR_REGEN’ now require Python 3.10 or newer.

   - gh-104490(3): Define ‘.PHONY’ / virtual make targets consistently
     and properly.

   - gh-104106(4): Add gcc fallback of mkfifoat/mknodat for macOS. Patch
     by Donghee Na.

   - gh-103532(5): The ‘TKINTER_PROTECT_LOADTK’ macro is no longer
     defined or used in the ‘_tkinter’ module.  It was previously only
     defined when building against Tk 8.4.13 and older, but Tk older
     than 8.5.12 has been unsupported since gh-91152(6).

   - gh-99069(7): Extended workaround defining ‘static_assert’ when
     missing from the libc headers to all clang and gcc builds.  In
     particular, this fixes building on macOS <= 10.10.

   - gh-100220(8): Changed the default value of the ‘SHELL’ Makefile
     variable from ‘/bin/sh’ to ‘/bin/sh -e’ to ensure that complex
     recipes correctly fail after an error.  Previously, ‘make install’
     could fail to install some files and yet return a successful
     result.

   - gh-90656(9): Add platform triplets for 64-bit LoongArch:

        * loongarch64-linux-gnusf

        * loongarch64-linux-gnuf32

        * loongarch64-linux-gnu

     Patch by Zhang Na.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/101282

   (2) https://github.com/python/cpython/issues/99017

   (3) https://github.com/python/cpython/issues/104490

   (4) https://github.com/python/cpython/issues/104106

   (5) https://github.com/python/cpython/issues/103532

   (6) https://github.com/python/cpython/issues/91152

   (7) https://github.com/python/cpython/issues/99069

   (8) https://github.com/python/cpython/issues/100220

   (9) https://github.com/python/cpython/issues/90656


File: python.info,  Node: Windows<10>,  Next: macOS<8>,  Prev: Build<13>,  Up: Python 3 12 0 beta 1

1.23.14.7 Windows
.................

   - gh-104623(1): Update Windows installer to use SQLite 3.42.0.

   - gh-82814(2): Fix a potential ‘[Errno 13] Permission denied’ when
     using *note shutil.copystat(): 10c7. within Windows Subsystem for
     Linux (WSL) on a mounted filesystem by adding ‘errno.EACCES’ to the
     list of ignored errors within the internal implementation.

   - gh-103088(3): Fix virtual environment ‘activate’ script having
     incorrect line endings for Cygwin.

   - gh-103088(4): Fixes venvs not working in bash on Windows across
     different disks

   - gh-102997(5): Update Windows installer to use SQLite 3.41.2.

   - gh-88013(6): Fixed a bug where *note TypeError: 4dd. was raised
     when calling ‘ntpath.realpath()’ with a bytes parameter in some
     cases.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/104623

   (2) https://github.com/python/cpython/issues/82814

   (3) https://github.com/python/cpython/issues/103088

   (4) https://github.com/python/cpython/issues/103088

   (5) https://github.com/python/cpython/issues/102997

   (6) https://github.com/python/cpython/issues/88013


File: python.info,  Node: macOS<8>,  Next: IDLE<12>,  Prev: Windows<10>,  Up: Python 3 12 0 beta 1

1.23.14.8 macOS
...............

   - gh-99834(1): Update macOS installer to Tcl/Tk 8.6.13.

   - gh-104623(2): Update macOS installer to SQLite 3.42.0.

   - gh-103545(3): Add ‘os.PRIO_DARWIN_THREAD’,
     ‘os.PRIO_DARWIN_PROCESS’, ‘os.PRIO_DARWIN_BG’ and
     ‘os.PRIO_DARWIN_NONUI’.  These can be used with ‘os.setpriority’ to
     run the process at a lower priority and make use of the efficiency
     cores on Apple Silicon systems.

   - gh-104180(4): Support reading SOCKS proxy configuration from macOS
     System Configuration.  Patch by Sam Schott.

   - gh-60436(5): update curses textbox to additionally handle backspace
     using the ‘curses.ascii.DEL’ key press.

   - gh-102997(6): Update macOS installer to SQLite 3.41.2.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/99834

   (2) https://github.com/python/cpython/issues/104623

   (3) https://github.com/python/cpython/issues/103545

   (4) https://github.com/python/cpython/issues/104180

   (5) https://github.com/python/cpython/issues/60436

   (6) https://github.com/python/cpython/issues/102997


File: python.info,  Node: IDLE<12>,  Next: Tools/Demos<6>,  Prev: macOS<8>,  Up: Python 3 12 0 beta 1

1.23.14.9 IDLE
..............

   - gh-104499(1): Fix completions for Tk Aqua 8.7 (currently blank).

   - gh-104496(2): About prints both tcl and tk versions if different
     (expected someday).

   - gh-88496(3): Fix IDLE test hang on macOS.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/104499

   (2) https://github.com/python/cpython/issues/104496

   (3) https://github.com/python/cpython/issues/88496


File: python.info,  Node: Tools/Demos<6>,  Next: C API<13>,  Prev: IDLE<12>,  Up: Python 3 12 0 beta 1

1.23.14.10 Tools/Demos
......................

   - gh-104389(1): Argument Clinic C converters now accept the ‘unused’
     keyword, for wrapping a parameter with *note Py_UNUSED: 1619.
     Patch by Erlend E. Aasland.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/104389


File: python.info,  Node: C API<13>,  Prev: Tools/Demos<6>,  Up: Python 3 12 0 beta 1

1.23.14.11 C API
................

   - gh-101291(1): Added unstable C API for extracting the value of
     "compact" integers: *note PyUnstable_Long_IsCompact(): 52f. and
     *note PyUnstable_Long_CompactValue(): 530.

   - gh-104109(2): We've added ‘Py_NewInterpreterFromConfig()’ and
     ‘PyInterpreterConfig’ to the public C-API (but not the stable ABI;
     not yet at least).  The new function may be used to create a new
     interpreter with various features configured.  The function was
     added to support PEP 684 (per-interpreter GIL).

   - gh-103968(3): *note PyType_FromSpec(): 523. and its variants now
     allow creating classes whose metaclass overrides *note tp_new: 525.
     The ‘tp_new’ is ignored.  This behavior is deprecated and will be
     disallowed in 3.14+.  The new *note PyType_FromMetaclass(): 4f6.
     already disallows it.

   - gh-103743(4): Add *note PyUnstable_Object_GC_NewWithExtraData():
     1637. function that can be used to allocate additional memory after
     an object for data not managed by Python.

   - gh-103295(5): Introduced *note PyUnstable_WritePerfMapEntry():
     1638, *note PyUnstable_PerfMapState_Init(): 1639. and *note
     PyUnstable_PerfMapState_Fini(): 163a.  These allow extension
     modules (JIT compilers in particular) to write to perf-map files in
     a thread safe manner.  The *note Python 對 Linux perf 分析器的支援:
     163b. also uses these APIs to write entries in the perf-map file.

   - gh-103509(6): Added C API for extending types whose instance memory
     layout is opaque: *note PyType_Spec.basicsize: 4ee. can now be zero
     or negative, *note PyObject_GetTypeData(): 4ef. can be used to get
     subclass-specific data, and *note Py_TPFLAGS_ITEMS_AT_END: 4f1. can
     be used to safely extend variable-size objects.  See PEP 697(7) for
     details.

   - gh-103091(8): Add a new C-API function to eagerly assign a version
     tag to a PyTypeObject: ‘PyUnstable_Type_AssignVersionTag()’.

   - gh-101408(9): *note PyObject_GC_Resize: 163c. should calculate
     preheader size if needed.  Patch by Donghee Na.

   - gh-98836(10): Add support of more formatting options (left
     aligning, octals, uppercase hexadecimals, ‘intmax_t’, ‘ptrdiff_t’,
     ‘wchar_t’ C strings, variable width and precision) in *note
     PyUnicode_FromFormat(): 33f. and *note PyUnicode_FromFormatV():
     51a.

   - gh-96803(11): Add unstable C-API functions to get the code object,
     lasti and line number from the internal ‘_PyInterpreterFrame’ in
     the limited API. The functions are:

        * ‘PyCodeObject * PyUnstable_InterpreterFrame_GetCode(struct
          _PyInterpreterFrame *frame)’

        * ‘int PyUnstable_InterpreterFrame_GetLasti(struct
          _PyInterpreterFrame *frame)’

        * ‘int PyUnstable_InterpreterFrame_GetLine(struct
          _PyInterpreterFrame *frame)’

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/101291

   (2) https://github.com/python/cpython/issues/104109

   (3) https://github.com/python/cpython/issues/103968

   (4) https://github.com/python/cpython/issues/103743

   (5) https://github.com/python/cpython/issues/103295

   (6) https://github.com/python/cpython/issues/103509

   (7) https://peps.python.org/pep-0697/

   (8) https://github.com/python/cpython/issues/103091

   (9) https://github.com/python/cpython/issues/101408

   (10) https://github.com/python/cpython/issues/98836

   (11) https://github.com/python/cpython/issues/96803


File: python.info,  Node: Python 3 12 0 alpha 7,  Next: Python 3 12 0 alpha 6,  Prev: Python 3 12 0 beta 1,  Up: Changelog（更動日誌）

1.23.15 Python 3.12.0 alpha 7
-----------------------------

'Release date: 2023-04-04'

* Menu:

* Core and Builtins: Core and Builtins<15>.
* Library: Library<14>.
* Documentation: Documentation<9>.
* Tests: Tests<12>.
* Build: Build<14>.
* Windows: Windows<11>.
* Tools/Demos: Tools/Demos<7>.
* C API: C API<14>.


File: python.info,  Node: Core and Builtins<15>,  Next: Library<14>,  Up: Python 3 12 0 alpha 7

1.23.15.1 Core and Builtins
...........................

   - gh-102192(1): Deprecated ‘_PyErr_ChainExceptions’ in favour of
     ‘_PyErr_ChainExceptions1’.

   - gh-89987(2): Reduce the number of inline *note CACHE: 69c. entries
     for *note BINARY_SUBSCR: 163f.

   - gh-102859(3): Removed ‘JUMP_IF_FALSE_OR_POP’ and
     ‘JUMP_IF_TRUE_OR_POP’ instructions.

   - gh-101975(4): Fixed ‘stacktop’ value on tracing entries to avoid
     corruption on garbage collection.

   - gh-102778(5): Add *note sys.last_exc: 465. and deprecate *note
     sys.last_type: 466, *note sys.last_value: 467. and *note
     sys.last_traceback: 468, which hold the same information in its
     legacy form.

   - gh-100982(6): Replace all occurrences of ‘COMPARE_AND_BRANCH’ with
     *note COMPARE_OP: 90d.

   - gh-102701(7): Fix overflow when creating very large dict.

   - gh-102755(8): Add *note PyErr_DisplayException(): 3ca. which takes
     just an exception instance, to replace the legacy ‘PyErr_Display()’
     which takes the ‘(typ, exc, tb)’ triplet.

   - gh-102594(9): Add note to exception raised in ‘PyErr_SetObject’
     when normalization fails.

   - gh-90997(10): Shrink the number of inline *note CACHE: 69c. entries
     used by *note LOAD_GLOBAL: 15e4.

   - gh-102491(11): Improve import time of ‘platform’ by removing
     IronPython version parsing.  The IronPython version parsing was not
     functional (see
     ‘https://github.com/IronLanguages/ironpython3/issues/1667’).

   - gh-101291(12): Rearrage bits in first field (after header) of
     PyLongObject.  * Bits 0 and 1: 1 - sign.  I.e.  0 for positive
     numbers, 1 for zero and 2 for negative numbers.  * Bit 2 reserved
     (probably for the immortal bit) * Bits 3+ the unsigned size.

     This makes a few operations slightly more efficient, and will
     enable a more compact and faster 2s-complement representation of
     most ints in future.

   - gh-102397(13): Fix segfault from race condition in signal handling
     during garbage collection.  Patch by Kumar Aditya.

   - gh-102406(14): *note codecs: 14. encoding/decoding errors now get
     the context information (which operation and which codecs) attached
     as PEP 678(15) notes instead of through chaining a new instance of
     the exception.

   - gh-102281(16): Fix potential nullptr dereference and use of
     uninitialized memory in fileutils.  Patch by Max Bachmann.

   - gh-102300(17): Reuse operands with refcount of 1 in float
     specializations of BINARY_OP.

   - gh-102213(18): Fix performance loss when accessing an object's
     attributes with ‘__getattr__’ defined.

   - gh-102255(19): Improve build support for the Xbox.  Patch by Max
     Bachmann.

   - gh-102027(20): Fix SSE2 and SSE3 detection in ‘_blake2’ internal
     module.  Patch by Max Bachmann.

   - gh-101865(21): Deprecate ‘co_lnotab’ in code objects, schedule it
     for removal in Python 3.14

   - bpo-1635741(22): Adapt ‘_pickle’ to PEP 687(23).  Patch by Mohamed
     Koubaa and Erlend Aasland.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/102192

   (2) https://github.com/python/cpython/issues/89987

   (3) https://github.com/python/cpython/issues/102859

   (4) https://github.com/python/cpython/issues/101975

   (5) https://github.com/python/cpython/issues/102778

   (6) https://github.com/python/cpython/issues/100982

   (7) https://github.com/python/cpython/issues/102701

   (8) https://github.com/python/cpython/issues/102755

   (9) https://github.com/python/cpython/issues/102594

   (10) https://github.com/python/cpython/issues/90997

   (11) https://github.com/python/cpython/issues/102491

   (12) https://github.com/python/cpython/issues/101291

   (13) https://github.com/python/cpython/issues/102397

   (14) https://github.com/python/cpython/issues/102406

   (15) https://peps.python.org/pep-0678/

   (16) https://github.com/python/cpython/issues/102281

   (17) https://github.com/python/cpython/issues/102300

   (18) https://github.com/python/cpython/issues/102213

   (19) https://github.com/python/cpython/issues/102255

   (20) https://github.com/python/cpython/issues/102027

   (21) https://github.com/python/cpython/issues/101865

   (22) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (23) https://peps.python.org/pep-0687/


File: python.info,  Node: Library<14>,  Next: Documentation<9>,  Prev: Core and Builtins<15>,  Up: Python 3 12 0 alpha 7

1.23.15.2 Library
.................

   - gh-103085(1): Pure python *note locale.getencoding(): 2bc. will not
     warn deprecation.

   - gh-103068(2): It's no longer possible to register conditional
     breakpoints in *note Pdb: 8c7. that raise *note SyntaxError: 173.
     Patch by Tian Gao.

   - gh-102549(3): Don't ignore exceptions in member type creation.

   - gh-103056(4): Ensure final ‘_generate_next_value_’ is a
     ‘staticmethod’.

   - gh-103046(5): Display current line label correctly in *note dis:
     30. when ‘show_caches’ is False and ‘lasti’ points to a CACHE
     entry.

   - gh-102433(6): *note isinstance(): 3e8. checks against *note
     runtime-checkable protocols: 3e9. now use *note
     inspect.getattr_static(): 43c. rather than *note hasattr(): 479. to
     lookup whether attributes exist.  This means that descriptors and
     *note __getattr__(): 47a. 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.  Patch by Alex Waygood.

   - gh-103023(7): It's no longer possible to register expressions to
     display in *note Pdb: 8c7. that raise *note SyntaxError: 173.
     Patch by Tian Gao.

   - gh-102947(8): Improve traceback when *note dataclasses.fields():
     1641. is called on a non-dataclass.  Patch by Alex Waygood

   - gh-102780(9): The *note asyncio.Timeout: 15c5. context manager now
     works reliably even when performing cleanup due to task
     cancellation.  Previously it could raise a *note CancelledError:
     19e. instead of an *note TimeoutError: 1642. in such cases.

   - gh-102871(10): Remove support for obsolete browsers from *note
     webbrowser: fd.  Removed browsers include Grail, Mosaic, Netscape,
     Galeon, Skipstone, Iceape, Firebird, and Firefox versions 35 and
     below.

   - gh-102839(11): Improve performance of *note math.log(): 142b.
     arguments handling by removing the argument clinic.

   - gh-102828(12): Add the ‘onexc’ arg to *note shutil.rmtree(): 2d2,
     which is like ‘onerror’ but expects an exception instance rather
     than an exc_info tuple.  Deprecate ‘onerror’.

   - gh-88965(13): typing: Fix a bug relating to substitution in custom
     classes generic over a *note ParamSpec: 142.  Previously, if the
     ‘ParamSpec’ was substituted with a parameters list that itself
     contained a *note TypeVar: 141, the ‘TypeVar’ in the parameters
     list could not be subsequently substituted.  This is now fixed.

     Patch by Nikita Sobolev.

   - gh-76846(14): Fix issue where ‘__new__()’ and ‘__init__()’ methods
     of *note pathlib.PurePath: 44e. and *note Path: 20e. subclasses
     were not called in some circumstances.

   - gh-78530(15): *note asyncio.wait(): 426. now accepts generators
     yielding tasks.  Patch by Kumar Aditya.

   - gh-102748(16): *note asyncio.iscoroutine(): 425. now returns
     ‘False’ for generators as *note asyncio: 8. does not support legacy
     generator-based coroutines.  Patch by Kumar Aditya.

   - gh-102670(17): Optimized fmean(), correlation(), covariance(), and
     linear_regression() using the new math.sumprod() function.

   - gh-102615(18): Typing: Improve the ‘repr’ of generic aliases for
     classes generic over a *note ParamSpec: 142.  (Use square brackets
     to represent a parameter list.)

   - gh-100112(19): *note asyncio.Task.get_coro(): 97f. now always
     returns a coroutine when wrapping an awaitable object.  Patch by
     Kumar Aditya.

   - gh-102578(20): Speed up setting or deleting mutable attributes on
     non-dataclass subclasses of frozen dataclasses.  Due to the
     implementation of ‘__setattr__’ and ‘__delattr__’ for frozen
     dataclasses, this previously had a time complexity of 'O'('n').  It
     now has a time complexity of 'O'(1).

   - gh-102519(21): Add *note os.listdrives(): 445, *note
     os.listvolumes(): 446. and *note os.listmounts(): 447. functions on
     Windows for enumerating drives, volumes and mount points

   - gh-74468(22): Attribute name of the extracted *note tarfile: c8.
     file object now holds filename of itself rather than of the archive
     it is contained in.  Patch by Oleg Iarygin.

   - gh-102378(23): Private helper method
     ‘inspect._signature_strip_non_python_syntax’ will no longer strip
     ‘/’ from the input string.

   - gh-79940(24): Add *note inspect.getasyncgenstate(): 43a. and *note
     inspect.getasyncgenlocals(): 43b.  Patch by Thomas Krennwallner.

   - gh-102103(25): Add ‘module’ argument to *note
     dataclasses.make_dataclass(): 1643. and make classes produced by it
     pickleable.

   - gh-102069(26): Fix ‘__weakref__’ descriptor generation for custom
     dataclasses.

   - gh-102038(27): Skip a ‘stat’ in *note site: b5. if we have already
     found a ‘pyvenv.cfg’

   - gh-98886(28): Fix issues when defining dataclasses that have fields
     with specific underscore names that aren't clearly reserved by
     *note dataclasses: 27.

   - gh-101673(29): Fix a *note pdb: 94. bug where ‘ll’ clears the
     changes to local variables.

   - gh-101313(30): Added -h and -help arguments to the webbrowser CLI

   - gh-100372(31): *note ssl.SSLContext.load_verify_locations(): e8f.
     no longer incorrectly accepts some cases of trailing data when
     parsing DER.

   - gh-89727(32): Fix pathlib.Path.walk RecursionError on deep
     directory trees by rewriting it using iteration instead of
     recursion.

   - gh-100131(33): Added an optional ‘delete’ keyword argument to *note
     tempfile.TemporaryDirectory: 11cc.

   - gh-48330(34): Added ‘--durations’ command line option, showing the
     N slowest test cases.  *note unittest.TextTestRunner: 1644. and
     *note unittest.TextTestResult: 4d5. constructors accept a new
     'durations' keyword argument.  Subclasses should take this into
     account or accept ‘**kwargs’.  Added *note
     unittest.TestResult.addDuration(): 1645. method and *note
     unittest.TestResult.collectedDurations: 160b. attribute.

     (Contributed by Giampaolo Rodola)

   - gh-98169(35): Fix *note dataclasses.astuple(): 162c. crash when
     *note collections.defaultdict: 1155. is present in the attributes.

   - gh-96931(36): Fix incorrect results from *note
     ssl.SSLSocket.shared_ciphers(): e0e.

   - gh-95495(37): When built against OpenSSL 3.0, the *note ssl: bb.
     module had a bug where it reported unauthenticated EOFs (i.e.
     without close_notify) as a clean TLS-level EOF. It now raises *note
     SSLEOFError: 1646, matching the behavior in previous versions of
     OpenSSL. The *note options: 7dc. attribute on *note SSLContext:
     276. also no longer includes *note OP_IGNORE_UNEXPECTED_EOF: 7db.
     by default.  This option may be set to specify the previous OpenSSL
     3.0 behavior.

   - gh-94684(38): Now *note uuid.uuid3(): 1647. and *note uuid.uuid5():
     1648. functions support *note bytes: 1a5. objects as their 'name'
     argument.

   - gh-94440(39): Fix a ‘concurrent.futures.process’ bug where
     ‘ProcessPoolExecutor’ shutdown could hang after a future has been
     quickly submitted and canceled.

   - gh-72346(40): Added deprecation warning to 'isdst' parameter of
     *note email.utils.localtime(): 2a6.

   - bpo-36305(41): Fix handling of Windows filenames that resemble
     drives, such as ‘./a:b’, in *note pathlib: 93.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/103085

   (2) https://github.com/python/cpython/issues/103068

   (3) https://github.com/python/cpython/issues/102549

   (4) https://github.com/python/cpython/issues/103056

   (5) https://github.com/python/cpython/issues/103046

   (6) https://github.com/python/cpython/issues/102433

   (7) https://github.com/python/cpython/issues/103023

   (8) https://github.com/python/cpython/issues/102947

   (9) https://github.com/python/cpython/issues/102780

   (10) https://github.com/python/cpython/issues/102871

   (11) https://github.com/python/cpython/issues/102839

   (12) https://github.com/python/cpython/issues/102828

   (13) https://github.com/python/cpython/issues/88965

   (14) https://github.com/python/cpython/issues/76846

   (15) https://github.com/python/cpython/issues/78530

   (16) https://github.com/python/cpython/issues/102748

   (17) https://github.com/python/cpython/issues/102670

   (18) https://github.com/python/cpython/issues/102615

   (19) https://github.com/python/cpython/issues/100112

   (20) https://github.com/python/cpython/issues/102578

   (21) https://github.com/python/cpython/issues/102519

   (22) https://github.com/python/cpython/issues/74468

   (23) https://github.com/python/cpython/issues/102378

   (24) https://github.com/python/cpython/issues/79940

   (25) https://github.com/python/cpython/issues/102103

   (26) https://github.com/python/cpython/issues/102069

   (27) https://github.com/python/cpython/issues/102038

   (28) https://github.com/python/cpython/issues/98886

   (29) https://github.com/python/cpython/issues/101673

   (30) https://github.com/python/cpython/issues/101313

   (31) https://github.com/python/cpython/issues/100372

   (32) https://github.com/python/cpython/issues/89727

   (33) https://github.com/python/cpython/issues/100131

   (34) https://github.com/python/cpython/issues/48330

   (35) https://github.com/python/cpython/issues/98169

   (36) https://github.com/python/cpython/issues/96931

   (37) https://github.com/python/cpython/issues/95495

   (38) https://github.com/python/cpython/issues/94684

   (39) https://github.com/python/cpython/issues/94440

   (40) https://github.com/python/cpython/issues/72346

   (41) https://bugs.python.org/issue?@action=redirect&bpo=36305


File: python.info,  Node: Documentation<9>,  Next: Tests<12>,  Prev: Library<14>,  Up: Python 3 12 0 alpha 7

1.23.15.3 Documentation
.......................

   - gh-103112(1): Add docstring to *note
     http.client.HTTPResponse.read(): 164a. to fix ‘pydoc’ output.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/103112


File: python.info,  Node: Tests<12>,  Next: Build<14>,  Prev: Documentation<9>,  Up: Python 3 12 0 alpha 7

1.23.15.4 Tests
...............

   - gh-102980(1): Improve test coverage on *note pdb: 94.

   - gh-102537(2): Adjust the error handling strategy in
     ‘test_zoneinfo.TzPathTest.python_tzpath_context’.  Patch by Paul
     Ganssle.

   - gh-101377(3): Improved test_locale_calendar_formatweekday of
     calendar.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/102980

   (2) https://github.com/python/cpython/issues/102537

   (3) https://github.com/python/cpython/issues/101377


File: python.info,  Node: Build<14>,  Next: Windows<11>,  Prev: Tests<12>,  Up: Python 3 12 0 alpha 7

1.23.15.5 Build
...............

   - gh-102973(1): Add a dev container (along with accompanying
     Dockerfile) for development purposes.

   - gh-102711(2): Fix ‘-Wstrict-prototypes’ compiler warnings.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/102973

   (2) https://github.com/python/cpython/issues/102711


File: python.info,  Node: Windows<11>,  Next: Tools/Demos<7>,  Prev: Build<14>,  Up: Python 3 12 0 alpha 7

1.23.15.6 Windows
.................

   - gh-102690(1): Update *note webbrowser: fd. to fall back to
     Microsoft Edge instead of Internet Explorer.

   - gh-99726(2): Improves correctness of stat results for Windows, and
     uses faster API when available

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/102690

   (2) https://github.com/python/cpython/issues/99726


File: python.info,  Node: Tools/Demos<7>,  Next: C API<14>,  Prev: Windows<11>,  Up: Python 3 12 0 alpha 7

1.23.15.7 Tools/Demos
.....................

   - gh-102809(1): ‘Misc/gdbinit’ was removed.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/102809


File: python.info,  Node: C API<14>,  Prev: Tools/Demos<7>,  Up: Python 3 12 0 alpha 7

1.23.15.8 C API
...............

   - gh-102013(1): Add a new (unstable) C-API function for iterating
     over GC'able objects using a callback: ‘PyUnstable_VisitObjects’.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/102013


File: python.info,  Node: Python 3 12 0 alpha 6,  Next: Python 3 12 0 alpha 5,  Prev: Python 3 12 0 alpha 7,  Up: Changelog（更動日誌）

1.23.16 Python 3.12.0 alpha 6
-----------------------------

'Release date: 2023-03-07'

* Menu:

* Security: Security<10>.
* Core and Builtins: Core and Builtins<16>.
* Library: Library<15>.
* Documentation: Documentation<10>.
* Tests: Tests<13>.
* Build: Build<15>.
* Windows: Windows<12>.
* macOS: macOS<9>.
* C API: C API<15>.


File: python.info,  Node: Security<10>,  Next: Core and Builtins<16>,  Up: Python 3 12 0 alpha 6

1.23.16.1 Security
..................

   - gh-99108(1): Replace builtin hashlib implementations of MD5 and
     SHA1 with verified ones from the HACL* project.

   - gh-101727(2): Updated the OpenSSL version used in Windows and macOS
     binary release builds to 1.1.1t to address CVE-2023-0286(3),
     CVE-2022-4303(4), and CVE-2022-4303(5) per the OpenSSL 2023-02-07
     security advisory(6).

   - gh-99108(7): Replace the builtin *note hashlib: 5e. implementations
     of SHA2-384 and SHA2-512 originally from LibTomCrypt with formally
     verified, side-channel resistant code from the HACL*(8) project.
     The builtins remain a fallback only used when OpenSSL does not
     provide them.

   - gh-101283(9): *note subprocess.Popen: 17d. now uses a safer
     approach to find ‘cmd.exe’ when launching with ‘shell=True’.  Patch
     by Eryk Sun, based on a patch by Oleg Iarygin.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/99108

   (2) https://github.com/python/cpython/issues/101727

   (3) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0286

   (4) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-4303

   (5) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-4303

   (6) https://www.openssl.org/news/secadv/20230207.txt

   (7) https://github.com/python/cpython/issues/99108

   (8) https://github.com/hacl-star/hacl-star/

   (9) https://github.com/python/cpython/issues/101283


File: python.info,  Node: Core and Builtins<16>,  Next: Library<15>,  Prev: Security<10>,  Up: Python 3 12 0 alpha 6

1.23.16.2 Core and Builtins
...........................

   - gh-102493(1): Fix regression in semantics of normalisation in
     ‘PyErr_SetObject’.

   - gh-102416(2): Do not memoize incorrectly automatically generated
     loop rules in the parser.  Patch by Pablo Galindo.

   - gh-102356(3): Fix a bug that caused a crash when deallocating
     deeply nested filter objects.  Patch by Marta Gómez Macías.

   - gh-102336(4): Cleanup Windows 7 specific special handling.  Patch
     by Max Bachmann.

   - gh-102250(5): Fixed a segfault occurring when the interpreter calls
     a ‘__bool__’ method that raises.

   - gh-102126(6): Fix deadlock at shutdown when clearing thread states
     if any finalizer tries to acquire the runtime head lock.  Patch by
     Kumar Aditya.

   - gh-102027(7): Use ‘GetCurrentProcessId’ on Windows when ‘getpid’ is
     unavailable.  Patch by Max Bachmann.

   - gh-102056(8): Fix error handling bugs in interpreter's exception
     printing code, which could cause a crash on infinite recursion.

   - gh-100982(9): Restrict the scope of the ‘FOR_ITER_RANGE’
     instruction to the scope of the original *note FOR_ITER: 1653.
     instruction, to allow instrumentation.

   - gh-101967(10): Fix possible segfault in
     ‘positional_only_passed_as_keyword’ function, when new list
     created.

   - gh-101952(11): Fix possible segfault in ‘BUILD_SET’ opcode, when
     new set created.

   - gh-74895(12): *note socket.getaddrinfo: 1654. no longer raises
     *note OverflowError: 825. for *note int: 23c. 'port' values outside
     of the C long range.  Out of range values are left up to the
     underlying string based C library API to report.  A *note
     socket.gaierror: 1655. ‘SAI_SERVICE’ may occur instead, or no error
     at all as not all platform C libraries generate an error.

   - gh-101799(13): Add *note CALL_INTRINSIC_2: 48a. and use it instead
     of ‘PREP_RERAISE_STAR’.

   - gh-101857(14): Fix xattr support detection on Linux systems by
     widening the check to linux, not just glibc.  This fixes support
     for musl.

   - gh-84783(15): Make the slice object hashable.  Patch by Will
     Bradshaw and Furkan Onder.

   - gh-87849(16): Change the ‘SEND’ instruction to leave the receiver
     on the stack.  This allows the specialized form of ‘SEND’ to skip
     the chain of C calls and jump directly to the ‘RESUME’ in the
     generator or coroutine.

   - gh-101765(17): Fix SystemError / segmentation fault in iter
     ‘__reduce__’ when internal access of ‘builtins.__dict__’ keys
     mutates the iter object.

   - gh-101430(18): Update *note tracemalloc: e8. to handle presize of
     object properly.  Patch by Donghee Na.

   - gh-101696(19): Invalidate type version tag in
     ‘_PyStaticType_Dealloc’ for static types, avoiding bug where a
     false cache hit could crash the interpreter.  Patch by Kumar
     Aditya.

   - gh-101632(20): Adds a new *note RETURN_CONST: 491. instruction.

   - gh-100719(21): Remove gi_code field from generator (and coroutine
     and async generator) objects as it is redundant.  The frame already
     includes a reference to the code object.

   - gh-98627(22): When an interpreter is configured to check (and only
     then), importing an extension module will now fail when the
     extension does not support multiple interpreters (i.e.  doesn't
     implement PEP 489 multi-phase init).  This does not apply to the
     main interpreter, nor to subinterpreters created with
     ‘Py_NewInterpreter()’.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/102493

   (2) https://github.com/python/cpython/issues/102416

   (3) https://github.com/python/cpython/issues/102356

   (4) https://github.com/python/cpython/issues/102336

   (5) https://github.com/python/cpython/issues/102250

   (6) https://github.com/python/cpython/issues/102126

   (7) https://github.com/python/cpython/issues/102027

   (8) https://github.com/python/cpython/issues/102056

   (9) https://github.com/python/cpython/issues/100982

   (10) https://github.com/python/cpython/issues/101967

   (11) https://github.com/python/cpython/issues/101952

   (12) https://github.com/python/cpython/issues/74895

   (13) https://github.com/python/cpython/issues/101799

   (14) https://github.com/python/cpython/issues/101857

   (15) https://github.com/python/cpython/issues/84783

   (16) https://github.com/python/cpython/issues/87849

   (17) https://github.com/python/cpython/issues/101765

   (18) https://github.com/python/cpython/issues/101430

   (19) https://github.com/python/cpython/issues/101696

   (20) https://github.com/python/cpython/issues/101632

   (21) https://github.com/python/cpython/issues/100719

   (22) https://github.com/python/cpython/issues/98627


File: python.info,  Node: Library<15>,  Next: Documentation<10>,  Prev: Core and Builtins<16>,  Up: Python 3 12 0 alpha 6

1.23.16.3 Library
.................

   - gh-102302(1): Micro-optimise hashing of *note inspect.Parameter:
     1b4, reducing the time it takes to hash an instance by around 40%.

   - gh-101979(2): Fix a bug where parentheses in the ‘metavar’ argument
     to *note argparse.ArgumentParser.add_argument(): 184. were dropped.
     Patch by Yeojin Kim.

   - gh-91038(3): *note platform.platform(): 1657. now has boolean
     default arguments.

   - gh-81652(4): Add *note mmap.MAP_ALIGNED_SUPER: 1658. FreeBSD and
     *note mmap.MAP_CONCEAL: 1659. OpenBSD constants to *note mmap: 83.
     Patch by Yeojin Kim.

   - gh-102179(5): Fix *note os.dup2(): b07. error message for negative
     fds.

   - gh-101961(6): For the binary mode, ‘fileinput.hookcompressed()’
     doesn't set the ‘encoding’ value even if the value is ‘None’.
     Patch by Gihwan Kim.

   - gh-101936(7): The default value of ‘fp’ becomes *note io.BytesIO:
     e46. if *note HTTPError: f81. is initialized without a designated
     ‘fp’ parameter.  Patch by Long Vo.

   - gh-101566(8): In zipfile, sync Path with zipp 3.14(9), including
     fix for extractall on the underlying zipfile after being wrapped in
     ‘Path’.

   - gh-97930(10): Apply changes from importlib_resources 5.12(11),
     including fix for ‘MultiplexedPath’ to support directories in
     multiple namespaces (python/importlib_resources#265).

   - gh-101997(12): Upgrade pip wheel bundled with ensurepip (pip
     23.0.1)

   - gh-99108(13): The built-in extension modules for *note hashlib: 5e.
     SHA2 algorithms, used when OpenSSL does not provide them, now live
     in a single internal ‘_sha2’ module instead of separate ‘_sha256’
     and ‘_sha512’ modules.

   - gh-101892(14): Callable iterators no longer raise *note
     SystemError: 51b. when the callable object exhausts the iterator
     but forgets to either return a sentinel value or raise *note
     StopIteration: ba1.

   - gh-87634(15): Remove locking behavior from *note
     functools.cached_property(): 4e7.

   - gh-97786(16): Fix potential undefined behaviour in corner cases of
     floating-point-to-time conversions.

   - gh-101517(17): Fixed bug where *note bdb: b. looks up the source
     line with *note linecache: 79. with a ‘lineno=None’, which causes
     it to fail with an unhandled exception.

   - gh-101773(18): Optimize *note fractions.Fraction: 1c7. for small
     components.  The private argument ‘_normalize’ of the *note
     fractions.Fraction: 1c7. constructor has been removed.

   - gh-101693(19): In *note sqlite3.Cursor.execute(): 2b3, *note
     DeprecationWarning: 18b. is now emitted when *note named
     placeholders: 2b5. are used together with parameters supplied as a
     *note sequence: 499. instead of as a *note dict: 23b.  Starting
     from Python 3.14, using named placeholders with parameters supplied
     as a sequence will raise a *note ProgrammingError: 49a.  Patch by
     Erlend E. Aasland.

   - gh-101446(20): Change repr of *note collections.OrderedDict: 57f.
     to use regular dictionary formatting instead of pairs of keys and
     values.

   - gh-101362(21): Speed up *note pathlib.PurePath: 44e. construction
     by handling arguments more uniformly.  When a *note pathlib.Path:
     20e. argument is supplied, we use its string representation rather
     than joining its parts with *note os.path.join(): 1527.

   - gh-101362(22): Speed up *note pathlib.PurePath: 44e. construction
     by calling *note os.path.join(): 1527. only when two or more
     arguments are given.

   - gh-101362(23): Speed up *note pathlib.Path: 20e. construction by
     running the path flavour compatibility check only when pathlib is
     imported.

   - gh-85984(24): Refactored the implementation of *note pty.fork():
     165a. to use *note os.login_tty(): 165b.

     A *note DeprecationWarning: 18b. is now raised by
     ‘pty.master_open()’ and ‘pty.slave_open()’.  They were undocumented
     and deprecated long long ago in the docstring in favor of *note
     pty.openpty(): 2b0.

   - gh-101561(25): Add a new decorator *note typing.override(): 3f1.
     See PEP 698(26) for details.  Patch by Steven Troxler.

   - gh-63301(27): Set exit code when *note tabnanny: c7. CLI exits on
     error.

   - gh-101360(28): Fix anchor matching in
     ‘pathlib.PureWindowsPath.match()’.  Path and pattern anchors are
     now matched with *note fnmatch: 52, just like other path parts.
     This allows patterns such as ‘"*:/Users/*"’ to be matched.

   - gh-101277(29): Remove global state from *note itertools: 75. module
     ( PEP 687(30)).  Patches by Erlend E. Aasland.

   - gh-100809(31): Fix handling of drive-relative paths (like 'C:' and
     'C:foo') in *note pathlib.Path.absolute(): 15a6.  This method now
     uses the OS API to retrieve the correct current working directory
     for the drive.

   - gh-99138(32): Apply PEP 687(33) to *note zoneinfo: 11a.  Patch by
     Erlend E. Aasland.

   - gh-96764(34): *note asyncio.wait_for(): 5a4. now uses *note
     asyncio.timeout(): 5a3. as its underlying implementation.  Patch by
     Kumar Aditya.

   - gh-88233(35): Correctly preserve "extra" fields in ‘zipfile’
     regardless of their ordering relative to a zip64 "extra."

   - bpo-23224(36): Fix segfaults when creating *note
     lzma.LZMADecompressor: 165c. and *note bz2.BZ2Decompressor: 165d.
     objects without calling ‘__init__()’, and fix leakage of locks and
     internal buffers when calling the ‘__init__()’ methods of *note
     lzma.LZMADecompressor: 165c, *note lzma.LZMACompressor: 165e, *note
     bz2.BZ2Compressor: 165f, and *note bz2.BZ2Decompressor: 165d.
     objects multiple times.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/102302

   (2) https://github.com/python/cpython/issues/101979

   (3) https://github.com/python/cpython/issues/91038

   (4) https://github.com/python/cpython/issues/81652

   (5) https://github.com/python/cpython/issues/102179

   (6) https://github.com/python/cpython/issues/101961

   (7) https://github.com/python/cpython/issues/101936

   (8) https://github.com/python/cpython/issues/101566

   (9) https://zipp.readthedocs.io/en/latest/history.html#v3-14-0

   (10) https://github.com/python/cpython/issues/97930

   (11) 
https://importlib-resources.readthedocs.io/en/latest/history.html#v5-12-0

   (12) https://github.com/python/cpython/issues/101997

   (13) https://github.com/python/cpython/issues/99108

   (14) https://github.com/python/cpython/issues/101892

   (15) https://github.com/python/cpython/issues/87634

   (16) https://github.com/python/cpython/issues/97786

   (17) https://github.com/python/cpython/issues/101517

   (18) https://github.com/python/cpython/issues/101773

   (19) https://github.com/python/cpython/issues/101693

   (20) https://github.com/python/cpython/issues/101446

   (21) https://github.com/python/cpython/issues/101362

   (22) https://github.com/python/cpython/issues/101362

   (23) https://github.com/python/cpython/issues/101362

   (24) https://github.com/python/cpython/issues/85984

   (25) https://github.com/python/cpython/issues/101561

   (26) https://peps.python.org/pep-0698/

   (27) https://github.com/python/cpython/issues/63301

   (28) https://github.com/python/cpython/issues/101360

   (29) https://github.com/python/cpython/issues/101277

   (30) https://peps.python.org/pep-0687/

   (31) https://github.com/python/cpython/issues/100809

   (32) https://github.com/python/cpython/issues/99138

   (33) https://peps.python.org/pep-0687/

   (34) https://github.com/python/cpython/issues/96764

   (35) https://github.com/python/cpython/issues/88233

   (36) https://bugs.python.org/issue?@action=redirect&bpo=23224


File: python.info,  Node: Documentation<10>,  Next: Tests<13>,  Prev: Library<15>,  Up: Python 3 12 0 alpha 6

1.23.16.4 Documentation
.......................

   - gh-85417(1): Update *note cmath: 11. documentation to clarify
     behaviour on branch cuts.

   - gh-97725(2): Fix *note asyncio.Task.print_stack(): 1661.
     description for ‘file=None’.  Patch by Oleg Iarygin.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/85417

   (2) https://github.com/python/cpython/issues/97725


File: python.info,  Node: Tests<13>,  Next: Build<15>,  Prev: Documentation<10>,  Up: Python 3 12 0 alpha 6

1.23.16.5 Tests
...............

   - gh-102019(1): Fix deadlock on shutdown if
     ‘test_current_{exception,frames}’ fails.  Patch by Jacob Bower.

   - gh-85984(2): Utilize new "winsize" functions from termios in pty
     tests.

   - gh-89792(3): ‘test_tools’ now copies up to 10x less source data to
     a temporary directory during the ‘freeze’ test by ignoring git
     metadata and other artifacts.  It also limits its python build
     parallelism based on os.cpu_count instead of hard coding it as 8
     cores.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/102019

   (2) https://github.com/python/cpython/issues/85984

   (3) https://github.com/python/cpython/issues/89792


File: python.info,  Node: Build<15>,  Next: Windows<12>,  Prev: Tests<13>,  Up: Python 3 12 0 alpha 6

1.23.16.6 Build
...............

   - gh-99942(1): On Android, in a static build, python-config in embed
     mode no longer incorrectly reports a library to link to.

   - gh-99942(2): On Android, python.pc now correctly reports the
     library to link to, the same as python-config.sh.

   - gh-100221(3): Fix creating install directories in ‘make
     sharedinstall’ if they exist outside ‘DESTDIR’ already.

   - gh-96821(4): Explicitly mark C extension modules that need defined
     signed integer overflow, and add a configure option *note
     -with-strict-overflow: 1664.  Patch by Matthias Görgens and
     Shantanu Jain.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/99942

   (2) https://github.com/python/cpython/issues/99942

   (3) https://github.com/python/cpython/issues/100221

   (4) https://github.com/python/cpython/issues/96821


File: python.info,  Node: Windows<12>,  Next: macOS<9>,  Prev: Build<15>,  Up: Python 3 12 0 alpha 6

1.23.16.7 Windows
.................

   - gh-102344(1): Implement ‘winreg.QueryValue’ using ‘QueryValueEx’
     and ‘winreg.SetValue’ using ‘SetValueEx’.  Patch by Max Bachmann.

   - gh-101881(2): Handle read and write operations on non-blocking
     pipes properly on Windows.

   - gh-101881(3): Add support for the os.get_blocking() and
     os.set_blocking() functions on Windows.

   - gh-101849(4): Ensures installer will correctly upgrade existing
     ‘py.exe’ launcher installs.

   - gh-101763(5): Updates copy of libffi bundled with Windows installs
     to 3.4.4.

   - gh-101759(6): Update Windows installer to SQLite 3.40.1.

   - gh-101614(7): Correctly handle extensions built against debug
     binaries that reference ‘python3_d.dll’.

   - gh-101196(8): The functions ‘os.path.isdir’, ‘os.path.isfile’,
     ‘os.path.islink’ and ‘os.path.exists’ are now 13% to 28% faster on
     Windows, by making fewer Win32 API calls.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/102344

   (2) https://github.com/python/cpython/issues/101881

   (3) https://github.com/python/cpython/issues/101881

   (4) https://github.com/python/cpython/issues/101849

   (5) https://github.com/python/cpython/issues/101763

   (6) https://github.com/python/cpython/issues/101759

   (7) https://github.com/python/cpython/issues/101614

   (8) https://github.com/python/cpython/issues/101196


File: python.info,  Node: macOS<9>,  Next: C API<15>,  Prev: Windows<12>,  Up: Python 3 12 0 alpha 6

1.23.16.8 macOS
...............

   - gh-101759(1): Update macOS installer to SQLite 3.40.1.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/101759


File: python.info,  Node: C API<15>,  Prev: macOS<9>,  Up: Python 3 12 0 alpha 6

1.23.16.9 C API
...............

   - gh-101907(1): Removes use of non-standard C++ extension in public
     header files.

   - gh-99293(2): Document that the Py_TPFLAGS_VALID_VERSION_TAG is an
     internal feature, should not be used, and will be removed.

   - gh-101578(3): Add *note PyErr_GetRaisedException(): 3bc. and *note
     PyErr_SetRaisedException(): 3bf. 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 *note PyErr_Fetch(): 3bb. and *note PyErr_Restore():
     3be.  This is less error prone and a bit more efficient.

     Add *note PyException_GetArgs(): 510. and *note
     PyException_SetArgs(): 511. as convenience functions for retrieving
     and modifying the *note args: 512. passed to the exception's
     constructor.

   - gh-91744(4): Introduced the 'Unstable C API tier', marking APi that
     is allowed to change in minor releases without a deprecation
     period.  See PEP 689(5) for details.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/101907

   (2) https://github.com/python/cpython/issues/99293

   (3) https://github.com/python/cpython/issues/101578

   (4) https://github.com/python/cpython/issues/91744

   (5) https://peps.python.org/pep-0689/


File: python.info,  Node: Python 3 12 0 alpha 5,  Next: Python 3 12 0 alpha 4,  Prev: Python 3 12 0 alpha 6,  Up: Changelog（更動日誌）

1.23.17 Python 3.12.0 alpha 5
-----------------------------

'Release date: 2023-02-07'

* Menu:

* Security: Security<11>.
* Core and Builtins: Core and Builtins<17>.
* Library: Library<16>.
* Documentation: Documentation<11>.
* Tests: Tests<14>.
* Build: Build<16>.
* Windows: Windows<13>.


File: python.info,  Node: Security<11>,  Next: Core and Builtins<17>,  Up: Python 3 12 0 alpha 5

1.23.17.1 Security
..................

   - gh-99108(1): Replace the builtin *note hashlib: 5e. implementations
     of SHA2-224 and SHA2-256 originally from LibTomCrypt with formally
     verified, side-channel resistant code from the HACL*(2) project.
     The builtins remain a fallback only used when OpenSSL does not
     provide them.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/99108

   (2) https://github.com/hacl-star/hacl-star/


File: python.info,  Node: Core and Builtins<17>,  Next: Library<16>,  Prev: Security<11>,  Up: Python 3 12 0 alpha 5

1.23.17.2 Core and Builtins
...........................

   - gh-92173(1): Fix the ‘defs’ and ‘kwdefs’ arguments to *note
     PyEval_EvalCodeEx(): 166b. and a reference leak in that function.

   - gh-59956(2): The GILState API is now partially compatible with
     subinterpreters.  Previously, ‘PyThreadState_GET()’ and
     ‘PyGILState_GetThisThreadState()’ would get out of sync, causing
     inconsistent behavior and crashes.

   - gh-101400(3): Fix wrong lineno in exception message on *note
     continue: 96d. or *note break: a4c. which are not in a loop.  Patch
     by Donghee Na.

   - gh-101372(4): Fix *note is_normalized(): 9ec. to properly handle
     the UCD 3.2.0 cases.  Patch by Donghee Na.

   - gh-101266(5): Fix *note sys.getsizeof(): 166c. reporting for *note
     int: 23c. subclasses.

   - gh-101291(6): Refactor the ‘PyLongObject’ struct into a normal
     Python object header and a ‘PyLongValue’ struct.

   - gh-101046(7): Fix a possible memory leak in the parser when raising
     *note MemoryError: 15bc.  Patch by Pablo Galindo

   - gh-101037(8): Fix potential memory underallocation issue for
     instances of *note int: 23c. subclasses with value zero.

   - gh-100762(9): Record the (virtual) exception block depth in the
     oparg of *note YIELD_VALUE: 15bb.  Use this to avoid the expensive
     ‘throw()’ when closing generators (and coroutines) that can be
     closed trivially.

   - gh-100982(10): Adds a new ‘COMPARE_AND_BRANCH’ instruction.  This
     is a bit more efficient when performing a comparison immediately
     followed by a branch, and restores the design intent of PEP 659
     that specializations are local to a single instruction.

   - gh-100942(11): Fixed segfault in property.getter/setter/deleter
     that occurred when a property subclass overrode the ‘__new__’
     method to return a non-property instance.

   - gh-100923(12): Remove the ‘mask’ cache entry for the *note
     COMPARE_OP: 90d. instruction and embed the mask into the oparg.

   - gh-100892(13): Fix race while iterating over thread states in
     clearing *note threading.local: 166d.  Patch by Kumar Aditya.

   - gh-91351(14): Fix a case where re-entrant imports could corrupt the
     import deadlock detection code and cause a *note KeyError: 2fb. to
     be raised out of ‘importlib/_bootstrap’.  In addition to the
     straightforward cases, this could also happen when garbage
     collection leads to a warning being emitted - as happens when it
     collects an open socket or file)

   - gh-100726(15): Optimize construction of ‘range’ object for medium
     size integers.

   - gh-100712(16): Added option to build cpython with specialization
     disabled, by setting ‘ENABLE_SPECIALIZATION=False’ in ‘opcode’,
     followed by ‘make regen-all’.

   - bpo-32780(17): Inter-field padding is now inserted into the PEP3118
     format strings obtained from *note ctypes.Structure: 154d. objects,
     reflecting their true representation in memory.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/92173

   (2) https://github.com/python/cpython/issues/59956

   (3) https://github.com/python/cpython/issues/101400

   (4) https://github.com/python/cpython/issues/101372

   (5) https://github.com/python/cpython/issues/101266

   (6) https://github.com/python/cpython/issues/101291

   (7) https://github.com/python/cpython/issues/101046

   (8) https://github.com/python/cpython/issues/101037

   (9) https://github.com/python/cpython/issues/100762

   (10) https://github.com/python/cpython/issues/100982

   (11) https://github.com/python/cpython/issues/100942

   (12) https://github.com/python/cpython/issues/100923

   (13) https://github.com/python/cpython/issues/100892

   (14) https://github.com/python/cpython/issues/91351

   (15) https://github.com/python/cpython/issues/100726

   (16) https://github.com/python/cpython/issues/100712

   (17) https://bugs.python.org/issue?@action=redirect&bpo=32780


File: python.info,  Node: Library<16>,  Next: Documentation<11>,  Prev: Core and Builtins<17>,  Up: Python 3 12 0 alpha 5

1.23.17.3 Library
.................

   - gh-101541(1): [Enum] - fix psuedo-flag creation

   - gh-101570(2): Upgrade pip wheel bundled with ensurepip (pip 23.0)

   - gh-101323(3): Fix a bug where errors where not thrown by
     zlib._ZlibDecompressor if encountered during decompressing.

   - gh-101317(4): Add 'ssl_shutdown_timeout' parameter for *note
     asyncio.StreamWriter.start_tls(): 5a9.

   - gh-101326(5): Fix regression when passing ‘None’ as second or third
     argument to ‘FutureIter.throw’.

   - gh-92123(6): Adapt the ‘_elementtree’ extension module to
     multi-phase init ( PEP 489(7)).  Patches by Erlend E. Aasland.

   - gh-100795(8): Avoid potential unexpected ‘freeaddrinfo’ call
     (double free) in *note socket: b8. when when a libc ‘getaddrinfo()’
     implementation leaves garbage in an output pointer when returning
     an error.  Original patch by Sergey G. Brester.

   - gh-101143(9): Remove unused references to *note TimerHandle: 166f.
     in ‘asyncio.base_events.BaseEventLoop._add_callback’.

   - gh-101144(10): Make *note zipfile.Path.open(): 1670. and *note
     zipfile.Path.read_text(): 1671. also accept ‘encoding’ as a
     positional argument.  This was the behavior in Python 3.9 and
     earlier.  3.10 introduced a regression where supplying it as a
     positional argument would lead to a *note TypeError: 4dd.

   - gh-94518(11): Group-related variables of ‘_posixsubprocess’ module
     are renamed to stress that supplementary group affinity is added to
     a fork, not replace the inherited ones.  Patch by Oleg Iarygin.

   - gh-101015(12): Fix *note typing.get_type_hints(): 657. on
     ‘'*tuple[...]'’ and ‘*tuple[...]’.  It must not drop the ‘Unpack’
     part.

   - gh-101000(13): Add *note os.path.splitroot(): 44c, which splits a
     path into a 3-item tuple ‘(drive, root, tail)’.  This new function
     is used by *note pathlib: 93. to improve the performance of path
     construction by up to a third.

   - gh-100573(14): Fix a Windows *note asyncio: 8. bug with named pipes
     where a client doing ‘os.stat()’ on the pipe would cause an error
     in the server that disabled serving future requests.

   - gh-39615(15): *note warnings.warn(): 1488. now has the ability to
     skip stack frames based on code filename prefix rather than only a
     numeric ‘stacklevel’ via the new ‘skip_file_prefixes’ keyword
     argument.

   - gh-100750(16): pass encoding kwarg to subprocess in platform

   - gh-100160(17): Emit a deprecation warning in
     ‘asyncio.DefaultEventLoopPolicy.get_event_loop()’ if there is no
     current event loop set and it decides to create one.

   - gh-96290(18): Fix handling of partial and invalid UNC drives in
     ‘ntpath.splitdrive()’, and in ‘ntpath.normpath()’ on non-Windows
     systems.  Paths such as '\server' and '\' are now considered by
     ‘splitdrive()’ to contain only a drive, and consequently are not
     modified by ‘normpath()’ on non-Windows systems.  The behaviour of
     ‘normpath()’ on Windows systems is unaffected, as native OS APIs
     are used.  Patch by Eryk Sun, with contributions by Barney Gale.

   - gh-99952(19): Fix a reference undercounting issue in *note
     ctypes.Structure: 154d. with ‘from_param()’ results larger than a C
     pointer.

   - gh-67790(20): Add float-style formatting support for *note
     fractions.Fraction: 1c7. instances.

   - gh-99266(21): Preserve more detailed error messages in *note
     ctypes: 22.

   - gh-86682(22): Ensure runtime-created collections have the correct
     module name using the newly added (internal) *note
     sys._getframemodulename(): 1672.

   - gh-88597(23): *note uuid: f8. now has a command line interface.
     Try ‘python -m uuid -h’.

   - gh-60580(24): ‘ctypes.wintypes.BYTE’ definition changed from *note
     c_byte: 1673. to *note c_ubyte: 1674. to match Windows SDK. Patch
     by Anatoly Techtonik and Oleg Iarygin.

   - gh-94518(25): ‘_posixsubprocess’ now initializes all UID and GID
     variables using a reserved ‘-1’ value instead of a separate flag.
     Patch by Oleg Iarygin.

   - bpo-38941(26): The *note xml.etree.ElementTree: 10c. module now
     emits *note DeprecationWarning: 18b. when testing the truth value
     of an *note xml.etree.ElementTree.Element: 2e2.  Before, the Python
     implementation emitted *note FutureWarning: 357, and the C
     implementation emitted nothing.

   - bpo-40077(27): Convert ‘elementtree’ types to heap types.  Patch by
     Erlend E. Aasland.

   - bpo-29847(28): Fix a bug where *note pathlib.Path: 20e. accepted
     and ignored keyword arguments.  Patch provided by Yurii Karabas.

   - gh-77772(29): *note ctypes.CDLL: 98d, *note ctypes.OleDLL: 1675,
     *note ctypes.WinDLL: 1676, and *note ctypes.PyDLL: 1677. now accept
     *note path-like objects: ac2. as their ‘name’ argument.  Patch by
     Robert Hoelzl.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/101541

   (2) https://github.com/python/cpython/issues/101570

   (3) https://github.com/python/cpython/issues/101323

   (4) https://github.com/python/cpython/issues/101317

   (5) https://github.com/python/cpython/issues/101326

   (6) https://github.com/python/cpython/issues/92123

   (7) https://peps.python.org/pep-0489/

   (8) https://github.com/python/cpython/issues/100795

   (9) https://github.com/python/cpython/issues/101143

   (10) https://github.com/python/cpython/issues/101144

   (11) https://github.com/python/cpython/issues/94518

   (12) https://github.com/python/cpython/issues/101015

   (13) https://github.com/python/cpython/issues/101000

   (14) https://github.com/python/cpython/issues/100573

   (15) https://github.com/python/cpython/issues/39615

   (16) https://github.com/python/cpython/issues/100750

   (17) https://github.com/python/cpython/issues/100160

   (18) https://github.com/python/cpython/issues/96290

   (19) https://github.com/python/cpython/issues/99952

   (20) https://github.com/python/cpython/issues/67790

   (21) https://github.com/python/cpython/issues/99266

   (22) https://github.com/python/cpython/issues/86682

   (23) https://github.com/python/cpython/issues/88597

   (24) https://github.com/python/cpython/issues/60580

   (25) https://github.com/python/cpython/issues/94518

   (26) https://bugs.python.org/issue?@action=redirect&bpo=38941

   (27) https://bugs.python.org/issue?@action=redirect&bpo=40077

   (28) https://bugs.python.org/issue?@action=redirect&bpo=29847

   (29) https://github.com/python/cpython/issues/77772


File: python.info,  Node: Documentation<11>,  Next: Tests<14>,  Prev: Library<16>,  Up: Python 3 12 0 alpha 5

1.23.17.4 Documentation
.......................

   - gh-88324(1): Reword *note subprocess: c1. to emphasize default
     behavior of 'stdin', 'stdout', and 'stderr' arguments.  Remove
     inaccurate statement about child file handle inheritance.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/88324


File: python.info,  Node: Tests<14>,  Next: Build<16>,  Prev: Documentation<11>,  Up: Python 3 12 0 alpha 5

1.23.17.5 Tests
...............

   - gh-101334(1): ‘test_tarfile’ has been updated to pass when run as a
     high UID.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/101334


File: python.info,  Node: Build<16>,  Next: Windows<13>,  Prev: Tests<14>,  Up: Python 3 12 0 alpha 5

1.23.17.6 Build
...............

   - gh-101282(1): Update BOLT configuration not to use deprecated usage
     of ‘--split functions’.  Patch by Donghee Na.

   - gh-101522(2): Allow overriding Windows dependencies versions and
     paths using MSBuild properties.

   - gh-77532(3): Minor fixes to allow building with
     ‘PlatformToolset=ClangCL’ on Windows.

   - gh-101152(4): In accordance with PEP 699(5), the ‘ma_version_tag’
     field in *note PyDictObject: 38c. 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.

   - gh-100340(6): Allows -Wno-int-conversion for wasm-sdk 17 and
     onwards, thus enables building WASI builds once against the latest
     sdk.

   - gh-101060(7): Conditionally add ‘-fno-reorder-blocks-and-partition’
     in configure.  Effectively fixes ‘--enable-bolt’ when using Clang,
     as this appears to be a GCC-only flag.

   - gh-98705(8): ‘__bool__’ is defined in AIX system header files which
     breaks the build in AIX, so undefine it.

   - gh-98636(9): Fix a regression in detecting ‘gdbm_compat’ library
     for the ‘_gdbm’ module build.

   - gh-96305(10): ‘_aix_support’ now uses a simple code to get platform
     details rather than the now non-existent ‘_bootsubprocess’ during
     bootstrap.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/101282

   (2) https://github.com/python/cpython/issues/101522

   (3) https://github.com/python/cpython/issues/77532

   (4) https://github.com/python/cpython/issues/101152

   (5) https://peps.python.org/pep-0699/

   (6) https://github.com/python/cpython/issues/100340

   (7) https://github.com/python/cpython/issues/101060

   (8) https://github.com/python/cpython/issues/98705

   (9) https://github.com/python/cpython/issues/98636

   (10) https://github.com/python/cpython/issues/96305


File: python.info,  Node: Windows<13>,  Prev: Build<16>,  Up: Python 3 12 0 alpha 5

1.23.17.7 Windows
.................

   - gh-101543(1): Ensure the install path in the registry is only used
     when the standard library hasn't been located in any other way.

   - gh-101467(2): The ‘py.exe’ launcher now correctly filters when only
     a single runtime is installed.  It also correctly handles prefix
     matches on tags so that ‘-3.1’ does not match ‘3.11’, but would
     still match ‘3.1-32’.

   - gh-99834(3): Updates bundled copy of Tcl/Tk to 8.6.13.0

   - gh-101135(4): Restore ability to launch older 32-bit versions from
     the ‘py.exe’ launcher when both 32-bit and 64-bit installs of the
     same version are available.

   - gh-82052(5): Fixed an issue where writing more than 32K of Unicode
     output to the console screen in one go can result in mojibake.

   - gh-100320(6): Ensures the ‘PythonPath’ registry key from an install
     is used when launching from a different copy of Python that relies
     on an existing install to provide a copy of its modules and
     standard library.

   - gh-100247(7): Restores support for the ‘py.exe’ launcher finding
     shebang commands in its configuration file using the full command
     name.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/101543

   (2) https://github.com/python/cpython/issues/101467

   (3) https://github.com/python/cpython/issues/99834

   (4) https://github.com/python/cpython/issues/101135

   (5) https://github.com/python/cpython/issues/82052

   (6) https://github.com/python/cpython/issues/100320

   (7) https://github.com/python/cpython/issues/100247


File: python.info,  Node: Python 3 12 0 alpha 4,  Next: Python 3 12 0 alpha 3,  Prev: Python 3 12 0 alpha 5,  Up: Changelog（更動日誌）

1.23.18 Python 3.12.0 alpha 4
-----------------------------

'Release date: 2023-01-10'

* Menu:

* Core and Builtins: Core and Builtins<18>.
* Library: Library<17>.
* Documentation: Documentation<12>.
* Tests: Tests<15>.
* Build: Build<17>.
* Windows: Windows<14>.
* macOS: macOS<10>.
* Tools/Demos: Tools/Demos<8>.
* C API: C API<16>.


File: python.info,  Node: Core and Builtins<18>,  Next: Library<17>,  Up: Python 3 12 0 alpha 4

1.23.18.1 Core and Builtins
...........................

   - gh-100776(1): Fix misleading default value in *note input():
     126b.'s ‘__text_signature__’.

   - gh-99005(2): Remove ‘UNARY_POSITIVE’, ‘ASYNC_GEN_WRAP’ and
     ‘LIST_TO_TUPLE’, replacing them with intrinsics.

   - gh-99005(3): Add new *note CALL_INTRINSIC_1: 489. instruction.
     Remove ‘IMPORT_STAR’, ‘PRINT_EXPR’ and ‘STOPITERATION_ERROR’,
     replacing them with the *note CALL_INTRINSIC_1: 489. instruction.

   - gh-100288(4): Remove the LOAD_ATTR_METHOD_WITH_DICT specialized
     instruction.  Stats show it is not useful.

   - gh-100720(5): Added ‘_PyFrame_NumSlotsForCodeObject’, which returns
     the number of slots needed in a frame for a given code object.

   - gh-100719(6): Removed the co_nplaincellvars field from the code
     object, as it is redundant.

   - gh-100637(7): Fix ‘int.__sizeof__()’ calculation to include the
     1-element ‘ob_digit’ array for ‘0’ and ‘False’.

   - gh-100649(8): Update the native_thread_id field of PyThreadState
     after fork.

   - gh-100126(9): Fix an issue where "incomplete" frames could be
     briefly visible to C code while other frames are being torn down,
     possibly resulting in corruption or hard crashes of the interpreter
     while running finalizers.

   - gh-87447(10): Fix *note SyntaxError: 173. on comprehension rebind
     checking with names that are not actually redefined.

     Now reassigning ‘b’ in ‘[(b := 1) for a, b.prop in some_iter]’ is
     allowed.  Reassigning ‘a’ is still disallowed as per PEP 572(11).

   - gh-100268(12): Add *note int.is_integer(): 167e. to improve duck
     type compatibility between *note int: 23c. and *note float: 2c8.

   - gh-100425(13): Improve the accuracy of ‘sum()’ with compensated
     summation.

   - gh-100374(14): Fix incorrect result and delay in *note
     socket.getfqdn(): 167f.  Patch by Dominic Socular.

   - gh-100357(15): Convert ‘vars’, ‘dir’, ‘next’, ‘getattr’, and ‘iter’
     to argument clinic.

   - gh-100117(16): Improve the output of *note codeobject.co_lines():
     2cc. by emitting only one entry for each line range.

   - gh-90043(17): Handle NaNs when specializing *note COMPARE_OP: 90d.
     for *note float: 2c8. values.

   - gh-100222(18): Redefine the ‘_Py_CODEUNIT’ typedef as a union to
     describe its layout to the C compiler, avoiding type punning and
     improving clarity.

   - gh-99955(19): Internal compiler functions (in compile.c) now
     consistently return -1 on error and 0 on success.

   - gh-100188(20): The ‘BINARY_SUBSCR_LIST_INT’ and
     ‘BINARY_SUBSCR_TUPLE_INT’ instructions are no longer used for
     negative integers because those instructions always miss when
     encountering negative integers.

   - gh-99110(21): Initialize frame->previous in frameobject.c to fix a
     segmentation fault when accessing frames created by
     ‘PyFrame_New()’.

   - gh-94155(22): Improved the hashing algorithm for code objects,
     mitigating some hash collisions.

   - gh-99540(23): ‘None’ now hashes to a constant value.  This is not a
     requirements change.

   - gh-100143(24): When built with ‘--enable-pystats’, stats collection
     is now off by default.  To enable it early at startup, pass the
     ‘-Xpystats’ flag.  Stats are now always dumped, even if switched
     off.

   - gh-100146(25): Improve ‘BUILD_LIST’ opcode so that it works
     similarly to the ‘BUILD_TUPLE’ opcode, by stealing references from
     the stack rather than repeatedly using stack operations to set list
     elements.  Implementation details are in a new private API
     ‘_PyList_FromArraySteal()’.

   - gh-100110(26): Specialize ‘FOR_ITER’ for tuples.

   - gh-100050(27): Honor existing errors obtained when searching for
     mismatching parentheses in the tokenizer.  Patch by Pablo Galindo

   - gh-92216(28): Improve the performance of *note hasattr(): 479. for
     type objects with a missing attribute.

   - gh-99582(29): Freeze *note zipimport: 118. module into
     ‘_bootstrap_python’.

   - gh-99554(30): Pack debugging location tables more efficiently
     during bytecode compilation.

   - gh-98522(31): Add an internal version number to code objects, to
     give better versioning of inner functions and comprehensions, and
     thus better specialization of those functions.  This change is
     invisible to both Python and C extensions.

   - gh-94603(32): Improve performance of ‘list.pop’ for small lists.

   - gh-89051(33): Add *note ssl.OP_LEGACY_SERVER_CONNECT: 1680.

   - bpo-32782(34): ‘ctypes’ arrays of length 0 now report a correct
     itemsize when a ‘memoryview’ is constructed from them, rather than
     always giving a value of 0.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/100776

   (2) https://github.com/python/cpython/issues/99005

   (3) https://github.com/python/cpython/issues/99005

   (4) https://github.com/python/cpython/issues/100288

   (5) https://github.com/python/cpython/issues/100720

   (6) https://github.com/python/cpython/issues/100719

   (7) https://github.com/python/cpython/issues/100637

   (8) https://github.com/python/cpython/issues/100649

   (9) https://github.com/python/cpython/issues/100126

   (10) https://github.com/python/cpython/issues/87447

   (11) https://peps.python.org/pep-0572/

   (12) https://github.com/python/cpython/issues/100268

   (13) https://github.com/python/cpython/issues/100425

   (14) https://github.com/python/cpython/issues/100374

   (15) https://github.com/python/cpython/issues/100357

   (16) https://github.com/python/cpython/issues/100117

   (17) https://github.com/python/cpython/issues/90043

   (18) https://github.com/python/cpython/issues/100222

   (19) https://github.com/python/cpython/issues/99955

   (20) https://github.com/python/cpython/issues/100188

   (21) https://github.com/python/cpython/issues/99110

   (22) https://github.com/python/cpython/issues/94155

   (23) https://github.com/python/cpython/issues/99540

   (24) https://github.com/python/cpython/issues/100143

   (25) https://github.com/python/cpython/issues/100146

   (26) https://github.com/python/cpython/issues/100110

   (27) https://github.com/python/cpython/issues/100050

   (28) https://github.com/python/cpython/issues/92216

   (29) https://github.com/python/cpython/issues/99582

   (30) https://github.com/python/cpython/issues/99554

   (31) https://github.com/python/cpython/issues/98522

   (32) https://github.com/python/cpython/issues/94603

   (33) https://github.com/python/cpython/issues/89051

   (34) https://bugs.python.org/issue?@action=redirect&bpo=32782


File: python.info,  Node: Library<17>,  Next: Documentation<12>,  Prev: Core and Builtins<18>,  Up: Python 3 12 0 alpha 4

1.23.18.2 Library
.................

   - gh-100833(1): Speed up *note math.fsum(): 1342. by removing
     defensive ‘volatile’ qualifiers.

   - gh-100805(2): Modify *note random.choice(): 11c8. implementation to
     once again work with NumPy arrays.

   - gh-100813(3): Add ‘socket.IP_PKTINFO’ constant.

   - gh-100792(4): Make *note email.message.Message.__contains__():
     1682. twice as fast.

   - gh-91851(5): Microoptimizations for *note
     fractions.Fraction.__round__(): 1683, *note
     fractions.Fraction.__ceil__(): 1684. and *note
     fractions.Fraction.__floor__(): 1685.

   - gh-90104(6): Avoid RecursionError on ‘repr’ if a dataclass field
     definition has a cyclic reference.

   - gh-100689(7): Fix crash in ‘pyexpat’ by statically allocating
     ‘PyExpat_CAPI’ capsule.

   - gh-100740(8): Fix ‘unittest.mock.Mock’ not respecting the spec for
     attribute names prefixed with ‘assert’.

   - gh-91219(9): Change ‘SimpleHTTPRequestHandler’ to support
     subclassing to provide a different set of index file names instead
     of using ‘__init__’ parameters.

   - gh-100690(10): ‘Mock’ objects which are not unsafe will now raise
     an ‘AttributeError’ when accessing an attribute that matches the
     name of an assertion but without the prefix ‘assert_’, e.g.
     accessing ‘called_once’ instead of ‘assert_called_once’.  This is
     in addition to this already happening for accessing attributes with
     prefixes ‘assert’, ‘assret’, ‘asert’, ‘aseert’, and ‘assrt’.

   - gh-89727(11): Simplify and optimize *note os.walk(): 451. by using
     *note isinstance(): 3e8. checks to check the top of the stack.

   - gh-100485(12): Add math.sumprod() to compute the sum of products.

   - gh-86508(13): Fix *note asyncio.open_connection(): abb. to skip
     binding to local addresses of different family.  Patch by Kumar
     Aditya.

   - gh-97930(14): ‘importlib.resources.files’ now accepts a module as
     an anchor instead of only accepting packages.  If a module is
     passed, resources are resolved adjacent to that module (in the same
     package or at the package root).  The parameter was renamed from
     ‘package’ to ‘anchor’ with a compatibility shim for those passing
     by keyword.  Additionally, the new ‘anchor’ parameter is now
     optional and will default to the caller's module.

   - gh-100585(15): Fixed a bug where importlib.resources.as_file was
     leaving file pointers open

   - gh-100562(16): Improve performance of *note
     pathlib.Path.absolute(): 15a6. by nearly 2x.  This comes at the
     cost of a performance regression in *note pathlib.Path.cwd(): 1628,
     which is generally used less frequently in user code.

   - gh-100519(17): Small simplification of
     ‘http.cookiejar.eff_request_host()’ that improves readability and
     better matches the RFC wording.

   - gh-100287(18): Fix the interaction of *note unittest.mock.seal():
     b48. with *note unittest.mock.AsyncMock: 9ee.

   - gh-100488(19): Add ‘Fraction.is_integer()’ to check whether a *note
     fractions.Fraction: 1c7. is an integer.  This improves duck type
     compatibility with *note float: 2c8. and *note int: 23c.

   - gh-100474(20): *note http.server: 68. now checks that an index page
     is actually a regular file before trying to serve it.  This avoids
     issues with directories named ‘index.html’.

   - gh-100363(21): Speed up *note asyncio.get_running_loop(): aae. by
     removing redundant ‘getpid’ checks.  Patch by Kumar Aditya.

   - gh-78878(22): Fix crash when creating an instance of
     ‘_ctypes.CField’.

   - gh-100348(23): Fix ref cycle in ‘asyncio._SelectorSocketTransport’
     by removing ‘_read_ready_cb’ in ‘close’.

   - gh-100344(24): Provide C implementation for *note
     asyncio.current_task(): 424. for a 4x-6x speedup.

   - gh-100272(25): Fix JSON serialization of OrderedDict.  It now
     preserves the order of keys.

   - gh-83076(26): Instantiation of ‘Mock()’ and ‘AsyncMock()’ is now
     3.8x faster.

   - gh-100234(27): Set a default value of 1.0 for the ‘lambd’ parameter
     in random.expovariate().

   - gh-100228(28): A *note DeprecationWarning: 18b. may be raised when
     *note os.fork(): 17b. or *note os.forkpty(): 17c. is called from
     multi-threaded processes.  Forking with threads is unsafe and can
     cause deadlocks, crashes and subtle problems.  Lack of a warning
     does not indicate that the fork call was actually safe, as Python
     may not be aware of all threads.

   - gh-100039(29): Improve signatures for enums and flags.

   - gh-100133(30): Fix regression in *note asyncio: 8. where a
     subprocess would sometimes lose data received from pipe.

   - bpo-44592(31): Fixes inconsistent handling of case sensitivity of
     'extrasaction' arg in *note csv.DictWriter: 1196.

   - gh-100098(32): Fix ‘tuple’ subclasses being cast to ‘tuple’ when
     used as enum values.

   - gh-85432(33): Rename the 'fmt' parameter of the pure-Python
     implementation of *note datetime.time.strftime(): 1686. to
     'format'.  Rename the 't' parameter of *note
     datetime.datetime.fromtimestamp(): 495. to 'timestamp'.  These
     changes mean the parameter names in the pure-Python implementation
     now match the parameter names in the C implementation.  Patch by
     Alex Waygood.

   - gh-98778(34): Update *note HTTPError: f81. to be initialized
     properly, even if the ‘fp’ is ‘None’.  Patch by Donghee Na.

   - gh-99925(35): Unify error messages in JSON serialization between
     ‘json.dumps(float('nan'), allow_nan=False)’ and
     ‘json.dumps(float('nan'), allow_nan=False, indent=<SOMETHING>)’.
     Now both include the representation of the value that could not be
     serialized.

   - gh-89727(36): Fix issue with *note os.walk(): 451. where a *note
     RecursionError: d12. would occur on deep directory structures by
     adjusting the implementation of *note os.walk(): 451. to be
     iterative instead of recursive.

   - gh-94943(37): Add *note Dataclass support: 1687. to the *note Enum:
     5d6. *note __repr__(): 1688.  When inheriting from a *note
     dataclass: 1af, only show the field names in the value section of
     the member *note repr(): 7a1, and not the dataclass' class name.

   - gh-83035(38): Fix *note inspect.getsource(): 14ca. handling of
     decorator calls with nested parentheses.

   - gh-99576(39): Fix ‘.save()’ method for ‘LWPCookieJar’ and
     ‘MozillaCookieJar’: saved file was not truncated on repeated save.

   - gh-94912(40): Add *note inspect.markcoroutinefunction(): 437.
     decorator which manually marks a function as a coroutine for the
     benefit of ‘iscoroutinefunction()’.

   - gh-99509(41): Add PEP 585(42) support for
     ‘multiprocessing.queues.Queue’.

   - gh-99482(43): Remove ‘Jython’ partial compatibility code from
     several stdlib modules.

   - gh-99433(44): Fix *note doctest: 31. failure on *note
     types.MethodWrapperType: 5f1. in modules.

   - gh-85267(45): Several improvements to *note inspect.signature():
     6dc.'s handling of ‘__text_signature’.  - Fixes a case where *note
     inspect.signature(): 6dc. dropped parameters - Fixes a case where
     *note inspect.signature(): 6dc. raised *note tokenize.TokenError:
     4e8. - Allows *note inspect.signature(): 6dc. to understand
     defaults involving binary operations of constants - *note
     inspect.signature(): 6dc. is documented as only raising *note
     TypeError: 4dd. or *note ValueError: 1e7, but sometimes raised
     *note RuntimeError: 179.  These cases now raise *note ValueError:
     1e7. - Removed a dead code path

   - gh-91166(46): *note asyncio: 8. is optimized to avoid excessive
     copying when writing to socket and use *note sendmsg(): 41d. if the
     platform supports it.  Patch by Kumar Aditya.

   - gh-98030(47): Add missing TCP socket options from Linux:
     ‘TCP_MD5SIG’, ‘TCP_THIN_LINEAR_TIMEOUTS’, ‘TCP_THIN_DUPACK’,
     ‘TCP_REPAIR’, ‘TCP_REPAIR_QUEUE’, ‘TCP_QUEUE_SEQ’,
     ‘TCP_REPAIR_OPTIONS’, ‘TCP_TIMESTAMP’, ‘TCP_CC_INFO’,
     ‘TCP_SAVE_SYN’, ‘TCP_SAVED_SYN’, ‘TCP_REPAIR_WINDOW’,
     ‘TCP_FASTOPEN_CONNECT’, ‘TCP_ULP’, ‘TCP_MD5SIG_EXT’,
     ‘TCP_FASTOPEN_KEY’, ‘TCP_FASTOPEN_NO_COOKIE’,
     ‘TCP_ZEROCOPY_RECEIVE’, ‘TCP_INQ’, ‘TCP_TX_DELAY’.

   - gh-88500(48): Reduced the memory usage of *note
     urllib.parse.unquote(): 1689. and *note
     urllib.parse.unquote_to_bytes(): 168a. on large values.

   - gh-96127(49): ‘inspect.signature’ was raising ‘TypeError’ on call
     with mock objects.  Now it correctly returns ‘(*args, **kwargs)’ as
     inferred signature.

   - gh-95882(50): Fix a 3.11 regression in *note asynccontextmanager():
     ace, which caused it to propagate exceptions with incorrect
     tracebacks and fix a 3.11 regression in *note contextmanager():
     119a, which caused it to propagate exceptions with incorrect
     tracebacks for *note StopIteration: ba1.

   - gh-78707(51): Deprecate passing more than one positional argument
     to *note pathlib.PurePath.relative_to(): 2ac. and *note
     is_relative_to(): 2ab.

   - gh-92122(52): Fix reStructuredText syntax errors in docstrings in
     the *note enum: 4c. module.

   - gh-91851(53): Optimize the *note Fraction: 1c7. arithmetics for
     small components.

   - bpo-24132(54): Make *note pathlib.PurePath: 44e. and *note Path:
     20e. subclassable (private to start).  Previously, attempting to
     instantiate a subclass resulted in an *note AttributeError: 2f6.
     being raised.  Patch by Barney Gale.

   - bpo-40447(55): Accept *note os.PathLike: bf8. (such as *note
     pathlib.Path: 20e.) in the ‘stripdir’ arguments of *note
     compileall.compile_file(): d87. and *note compileall.compile_dir():
     aca.

   - bpo-36880(56): Fix a reference counting issue when a *note ctypes:
     22. callback with return type *note py_object: 13a5. returns
     ‘None’, which could cause crashes.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/100833

   (2) https://github.com/python/cpython/issues/100805

   (3) https://github.com/python/cpython/issues/100813

   (4) https://github.com/python/cpython/issues/100792

   (5) https://github.com/python/cpython/issues/91851

   (6) https://github.com/python/cpython/issues/90104

   (7) https://github.com/python/cpython/issues/100689

   (8) https://github.com/python/cpython/issues/100740

   (9) https://github.com/python/cpython/issues/91219

   (10) https://github.com/python/cpython/issues/100690

   (11) https://github.com/python/cpython/issues/89727

   (12) https://github.com/python/cpython/issues/100485

   (13) https://github.com/python/cpython/issues/86508

   (14) https://github.com/python/cpython/issues/97930

   (15) https://github.com/python/cpython/issues/100585

   (16) https://github.com/python/cpython/issues/100562

   (17) https://github.com/python/cpython/issues/100519

   (18) https://github.com/python/cpython/issues/100287

   (19) https://github.com/python/cpython/issues/100488

   (20) https://github.com/python/cpython/issues/100474

   (21) https://github.com/python/cpython/issues/100363

   (22) https://github.com/python/cpython/issues/78878

   (23) https://github.com/python/cpython/issues/100348

   (24) https://github.com/python/cpython/issues/100344

   (25) https://github.com/python/cpython/issues/100272

   (26) https://github.com/python/cpython/issues/83076

   (27) https://github.com/python/cpython/issues/100234

   (28) https://github.com/python/cpython/issues/100228

   (29) https://github.com/python/cpython/issues/100039

   (30) https://github.com/python/cpython/issues/100133

   (31) https://bugs.python.org/issue?@action=redirect&bpo=44592

   (32) https://github.com/python/cpython/issues/100098

   (33) https://github.com/python/cpython/issues/85432

   (34) https://github.com/python/cpython/issues/98778

   (35) https://github.com/python/cpython/issues/99925

   (36) https://github.com/python/cpython/issues/89727

   (37) https://github.com/python/cpython/issues/94943

   (38) https://github.com/python/cpython/issues/83035

   (39) https://github.com/python/cpython/issues/99576

   (40) https://github.com/python/cpython/issues/94912

   (41) https://github.com/python/cpython/issues/99509

   (42) https://peps.python.org/pep-0585/

   (43) https://github.com/python/cpython/issues/99482

   (44) https://github.com/python/cpython/issues/99433

   (45) https://github.com/python/cpython/issues/85267

   (46) https://github.com/python/cpython/issues/91166

   (47) https://github.com/python/cpython/issues/98030

   (48) https://github.com/python/cpython/issues/88500

   (49) https://github.com/python/cpython/issues/96127

   (50) https://github.com/python/cpython/issues/95882

   (51) https://github.com/python/cpython/issues/78707

   (52) https://github.com/python/cpython/issues/92122

   (53) https://github.com/python/cpython/issues/91851

   (54) https://bugs.python.org/issue?@action=redirect&bpo=24132

   (55) https://bugs.python.org/issue?@action=redirect&bpo=40447

   (56) https://bugs.python.org/issue?@action=redirect&bpo=36880


File: python.info,  Node: Documentation<12>,  Next: Tests<15>,  Prev: Library<17>,  Up: Python 3 12 0 alpha 4

1.23.18.3 Documentation
.......................

   - gh-100616(1): Document existing ‘attr’ parameter to *note
     curses.window.vline(): 168c. function in *note curses: 23.

   - gh-100472(2): Remove claim in documentation that the ‘stripdir’,
     ‘prependdir’ and ‘limit_sl_dest’ parameters of *note
     compileall.compile_dir(): aca. and *note compileall.compile_file():
     d87. could be *note bytes: 1a5.

   - bpo-25377(3): Clarify use of octal format of mode argument in
     help(os.chmod) as well as help(os.fchmod)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/100616

   (2) https://github.com/python/cpython/issues/100472

   (3) https://bugs.python.org/issue?@action=redirect&bpo=25377


File: python.info,  Node: Tests<15>,  Next: Build<17>,  Prev: Documentation<12>,  Up: Python 3 12 0 alpha 4

1.23.18.4 Tests
...............

   - gh-100454(1): Start running SSL tests with OpenSSL 3.1.0-beta1.

   - gh-100086(2): The Python test runner (libregrtest) now logs Python
     build information like "debug" vs "release" build, or LTO and PGO
     optimizations.  Patch by Victor Stinner.

   - gh-93018(3): Make two tests forgiving towards host system libexpat
     with backported security fixes applied.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/100454

   (2) https://github.com/python/cpython/issues/100086

   (3) https://github.com/python/cpython/issues/93018


File: python.info,  Node: Build<17>,  Next: Windows<14>,  Prev: Tests<15>,  Up: Python 3 12 0 alpha 4

1.23.18.5 Build
...............

   - gh-100540(1): Removed the ‘--with-system-ffi’ ‘configure’ option;
     ‘libffi’ must now always be supplied by the system on all
     non-Windows platforms.  The option has had no effect on non-Darwin
     platforms for several releases, and in 3.11 only had the
     non-obvious effect of invoking ‘pkg-config’ to find ‘libffi’ and
     never setting ‘-DUSING_APPLE_OS_LIBFFI’.  Now on Darwin platforms
     ‘configure’ will first check for the OS ‘libffi’ and then fall back
     to the same processing as other platforms if it is not found.

   - gh-88267(2): Avoid exporting Python symbols in linked Windows
     applications when the core is built as static.

   - bpo-41916(3): Allow override of ac_cv_cxx_thread so that cross
     compiled python can set -pthread for CXX.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/100540

   (2) https://github.com/python/cpython/issues/88267

   (3) https://bugs.python.org/issue?@action=redirect&bpo=41916


File: python.info,  Node: Windows<14>,  Next: macOS<10>,  Prev: Build<17>,  Up: Python 3 12 0 alpha 4

1.23.18.6 Windows
.................

   - gh-100180(1): Update Windows installer to OpenSSL 1.1.1s

   - gh-99191(2): Use ‘_MSVC_LANG >= 202002L’ instead of less-precise
     ‘_MSC_VER >=1929’ to more accurately test for C++20 support in
     ‘PC/_wmimodule.cpp’.

   - gh-79218(3): Define ‘MS_WIN64’ for Mingw-w64 64bit, fix cython
     compilation failure.

   - gh-99941(4): Ensure that *note asyncio.Protocol.data_received():
     1690. receives an immutable *note bytes: 1a5. object (as
     documented), instead of *note bytearray: 4e3.

   - bpo-43984(5): *note winreg.SetValueEx(): 1691. now leaves the
     target value untouched in the case of conversion errors.
     Previously, ‘-1’ would be written in case of such errors.

   - bpo-34816(6): ‘hasattr(ctypes.windll, 'nonexistant')’ now returns
     ‘False’ instead of raising *note OSError: 350.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/100180

   (2) https://github.com/python/cpython/issues/99191

   (3) https://github.com/python/cpython/issues/79218

   (4) https://github.com/python/cpython/issues/99941

   (5) https://bugs.python.org/issue?@action=redirect&bpo=43984

   (6) https://bugs.python.org/issue?@action=redirect&bpo=34816


File: python.info,  Node: macOS<10>,  Next: Tools/Demos<8>,  Prev: Windows<14>,  Up: Python 3 12 0 alpha 4

1.23.18.7 macOS
...............

   - gh-100180(1): Update macOS installer to OpenSSL 1.1.1s

   - gh-100540(2): Removed obsolete ‘dlfcn.h’ shim from the ‘_ctypes’
     extension module, which has not been necessary since Mac OS X 10.2.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/100180

   (2) https://github.com/python/cpython/issues/100540


File: python.info,  Node: Tools/Demos<8>,  Next: C API<16>,  Prev: macOS<10>,  Up: Python 3 12 0 alpha 4

1.23.18.8 Tools/Demos
.....................

   - bpo-45256(1): Fix a bug that caused an *note AttributeError: 2f6.
     to be raised in ‘python-gdb.py’ when ‘py-locals’ is used without a
     frame.

   - gh-100342(2): Add missing ‘NULL’ check for possible allocation
     failure in ‘*args’ parsing in Argument Clinic.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45256

   (2) https://github.com/python/cpython/issues/100342


File: python.info,  Node: C API<16>,  Prev: Tools/Demos<8>,  Up: Python 3 12 0 alpha 4

1.23.18.9 C API
...............

   - gh-99947(1): Raising SystemError on import will now have its cause
     be set to the original unexpected exception.

   - gh-99240(2): In argument parsing, after deallocating newly
     allocated memory, reset its pointer to NULL.

   - gh-98724(3): The *note Py_CLEAR: 51e, *note Py_SETREF: 51f. and
     *note Py_XSETREF: 520. macros now only evaluate their arguments
     once.  If an argument has side effects, these side effects are no
     longer duplicated.  Patch by Victor Stinner.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/99947

   (2) https://github.com/python/cpython/issues/99240

   (3) https://github.com/python/cpython/issues/98724


File: python.info,  Node: Python 3 12 0 alpha 3,  Next: Python 3 12 0 alpha 2,  Prev: Python 3 12 0 alpha 4,  Up: Changelog（更動日誌）

1.23.19 Python 3.12.0 alpha 3
-----------------------------

'Release date: 2022-12-06'

* Menu:

* Security: Security<12>.
* Core and Builtins: Core and Builtins<19>.
* Library: Library<18>.
* Documentation: Documentation<13>.
* Tests: Tests<16>.
* Build: Build<18>.
* Windows: Windows<15>.
* macOS: macOS<11>.
* Tools/Demos: Tools/Demos<9>.
* C API: C API<17>.


File: python.info,  Node: Security<12>,  Next: Core and Builtins<19>,  Up: Python 3 12 0 alpha 3

1.23.19.1 Security
..................

   - gh-100001(1): ‘python -m http.server’ no longer allows terminal
     control characters sent within a garbage request to be printed to
     the stderr server log.

     This is done by changing the *note http.server: 68.
     ‘BaseHTTPRequestHandler’ ‘.log_message’ method to replace control
     characters with a ‘\xHH’ hex escape before printing.

   - gh-87604(2): Avoid publishing list of active per-interpreter audit
     hooks via the *note gc: 56. module

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/100001

   (2) https://github.com/python/cpython/issues/87604


File: python.info,  Node: Core and Builtins<19>,  Next: Library<18>,  Prev: Security<12>,  Up: Python 3 12 0 alpha 3

1.23.19.2 Core and Builtins
...........................

   - gh-99891(1): Fix a bug in the tokenizer that could cause infinite
     recursion when showing syntax warnings that happen in the first
     line of the source.  Patch by Pablo Galindo

   - gh-91054(2): Add *note PyCode_AddWatcher(): 50c. and *note
     PyCode_ClearWatcher(): 50d. APIs to register callbacks to receive
     notification on creation and destruction of code objects.

   - gh-99729(3): Fix an issue that could cause frames to be visible to
     Python code as they are being torn down, possibly leading to memory
     corruption or hard crashes of the interpreter.

   - gh-99708(4): Fix bug where compiler crashes on an if expression
     with an empty body block.

   - gh-99578(5): Fix a reference bug in ‘_imp.create_builtin()’ after
     the creation of the first sub-interpreter for modules ‘builtins’
     and ‘sys’.  Patch by Victor Stinner.

   - gh-99581(6): Fixed a bug that was causing a buffer overflow if the
     tokenizer copies a line missing the newline character from a file
     that is as long as the available tokenizer buffer.  Patch by Pablo
     galindo

   - gh-99553(7): Fix bug where an *note ExceptionGroup: 19c. subclass
     can wrap a *note BaseException: 55f.

   - gh-99547(8): Add a function to os.path to check if a path is a
     junction: isjunction.  Add similar functionality to pathlib.Path as
     is_junction.

   - gh-99370(9): Fix zip path for venv created from a non-installed
     python on POSIX platforms.

   - gh-99377(10): Add audit events for thread creation and clear
     operations.

   - gh-98686(11): Remove the ‘BINARY_OP_GENERIC’ and
     ‘COMPARE_OP_GENERIC’ "specializations".

   - gh-99298(12): Remove the remaining error paths for attribute
     specializations, and refuse to specialize attribute accesses on
     types that haven't had *note PyType_Ready(): 722. called on them
     yet.

   - gh-99127(13): Allow some features of *note syslog: c6. to the main
     interpreter only.  Patch by Donghee Na.

   - gh-91053(14): Optimizing interpreters and JIT compilers may need to
     invalidate internal metadata when functions are modified.  This
     change adds the ability to provide a callback that will be invoked
     each time a function is created, modified, or destroyed.

   - gh-90994(15): Improve error messages when there's a syntax error
     with call arguments.  The following three cases are covered: - No
     value is assigned to a named argument, eg ‘foo(a=)’.  - A value is
     assigned to a star argument, eg ‘foo(*args=[0])’.  - A value is
     assigned to a double-star keyword argument, eg ‘foo(**kwarg={'a':
     0})’.

   - bpo-45026(16): Optimize the *note range: 8e7. object iterator.  It
     is now smaller, faster iteration of ranges containing large
     numbers.  Smaller pickles, faster unpickling.

   - bpo-31718(17): Raise *note ValueError: 1e7. instead of *note
     SystemError: 51b. when methods of uninitialized *note
     io.IncrementalNewlineDecoder: 15c3. objects are called.  Patch by
     Oren Milman.

   - bpo-38031(18): Fix a possible assertion failure in *note io.FileIO:
     12a4. when the opener returns an invalid file descriptor.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/99891

   (2) https://github.com/python/cpython/issues/91054

   (3) https://github.com/python/cpython/issues/99729

   (4) https://github.com/python/cpython/issues/99708

   (5) https://github.com/python/cpython/issues/99578

   (6) https://github.com/python/cpython/issues/99581

   (7) https://github.com/python/cpython/issues/99553

   (8) https://github.com/python/cpython/issues/99547

   (9) https://github.com/python/cpython/issues/99370

   (10) https://github.com/python/cpython/issues/99377

   (11) https://github.com/python/cpython/issues/98686

   (12) https://github.com/python/cpython/issues/99298

   (13) https://github.com/python/cpython/issues/99127

   (14) https://github.com/python/cpython/issues/91053

   (15) https://github.com/python/cpython/issues/90994

   (16) https://bugs.python.org/issue?@action=redirect&bpo=45026

   (17) https://bugs.python.org/issue?@action=redirect&bpo=31718

   (18) https://bugs.python.org/issue?@action=redirect&bpo=38031


File: python.info,  Node: Library<18>,  Next: Documentation<13>,  Prev: Core and Builtins<19>,  Up: Python 3 12 0 alpha 3

1.23.19.3 Library
.................

   - gh-100001(1): Also escape s in the http.server
     BaseHTTPRequestHandler.log_message so that it is technically
     possible to parse the line and reconstruct what the original data
     was.  Without this a xHH is ambiguous as to if it is a hex
     replacement we put in or the characters r"x" came through in the
     original request line.

   - gh-99957(2): Add ‘frozen_default’ parameter to *note
     typing.dataclass_transform(): 47b.

   - gh-79033(3): Fix *note asyncio.Server.wait_closed(): 15c4. to
     actually do what the docs promise - wait for all existing
     connections to complete, after closing the server.

   - gh-51524(4): Fix bug when calling trace.CoverageResults with valid
     infile.

   - gh-99645(5): Fix a bug in handling class cleanups in *note
     unittest.TestCase: 3f4.  Now ‘addClassCleanup()’ uses separate
     lists for different ‘TestCase’ subclasses, and ‘doClassCleanups()’
     only cleans up the particular class.

   - gh-99508(6): Fix ‘TypeError’ in
     ‘Lib/importlib/_bootstrap_external.py’ while calling
     ‘_imp.source_hash()’.

   - gh-66285(7): Fix *note asyncio: 8. to not share event loop and
     signal wakeupfd in forked processes.  Patch by Kumar Aditya.

   - gh-97001(8): Release the GIL when calling termios APIs to avoid
     blocking threads.

   - gh-92647(9): Use final status of an enum to determine lookup or
     creation branch of functional API.

   - gh-99388(10): Add 'loop_factory' parameter to *note asyncio.run():
     423. to allow specifying a custom event loop factory.  Patch by
     Kumar Aditya.

   - gh-99341(11): Fix *note ast.increment_lineno(): 1699. to also cover
     ‘ast.TypeIgnore’ when changing line numbers.

   - gh-99382(12): Check the number of arguments in substitution in user
     generics containing a *note TypeVarTuple: 143. and one or more
     *note TypeVar: 141.

   - gh-99379(13): Fix substitution of *note ParamSpec: 142. followed by
     *note TypeVarTuple: 143. in generic aliases.

   - gh-99344(14): Fix substitution of *note TypeVarTuple: 143. and
     *note ParamSpec: 142. together in user generics.

   - gh-99284(15): Remove ‘_use_broken_old_ctypes_structure_semantics_’
     old untested and undocumented hack from *note ctypes: 22.

   - gh-99201(16): Fix *note IndexError: 14a3. when initializing the
     config variables on Windows if ‘HAVE_DYNAMIC_LOADING’ is not set.

   - gh-99240(17): Fix double-free bug in Argument Clinic
     ‘str_converter’ by extracting memory clean up to a new
     ‘post_parsing’ section.

   - gh-64490(18): Fix refcount error when arguments are packed to tuple
     in Argument Clinic.

   - gh-99029(19): *note pathlib.PurePath.relative_to(): 2ac. now treats
     naked Windows drive paths as relative.  This brings its behaviour
     in line with other parts of pathlib.

   - gh-98253(20): The implementation of the typing module is now more
     resilient to reference leaks in binary extension modules.

     Previously, a reference leak in a typed C API-based extension
     module could leak internals of the typing module, which could in
     turn introduce leaks in essentially any other package with typed
     function signatures.  Although the typing package is not the
     original source of the problem, such non-local dependences
     exacerbate debugging of large-scale projects, and the
     implementation was therefore changed to reduce harm by providing
     better isolation.

   - gh-98458(21): Fix infinite loop in unittest when a self-referencing
     chained exception is raised

   - gh-93453(22): *note asyncio.get_event_loop(): 2a3. and many other
     *note asyncio: 8. functions like *note asyncio.ensure_future():
     c1d, *note asyncio.shield(): a13. or *note asyncio.gather(): 5a2,
     and also the ‘get_event_loop()’ method of
     ‘asyncio.BaseDefaultEventLoopPolicy’ now raise a *note
     RuntimeError: 179. if called when there is no running event loop
     and the current event loop was not set.  Previously they implicitly
     created and set a new current event loop.  *note
     DeprecationWarning: 18b. is no longer emitted if there is no
     running event loop but the current event loop was set.

   - gh-97966(23): On ‘uname_result’, restored expectation that
     ‘_fields’ and ‘_asdict’ would include all six properties including
     ‘processor’.

   - gh-98248(24): Provide informative error messages in *note
     struct.pack(): 120f. when its integral arguments are not in range.

   - gh-98108(25): ‘zipfile.Path’ is now pickleable if its
     initialization parameters were pickleable (e.g.  for file system
     paths).

   - gh-98098(26): Created packages from zipfile and test_zipfile
     modules, separating ‘zipfile.Path’ functionality.

   - gh-82836(27): Fix *note is_private: 153d. properties in the *note
     ipaddress: 74. module.  Previously non-private networks (0.0.0.0/0)
     would return ‘True’ from this method; now they correctly return
     ‘False’.

   - gh-96828(28): Add an *note OP_ENABLE_KTLS: 169a. option for
     enabling the use of the kernel TLS (kTLS). Patch by Illia Volochii.

   - gh-88863(29): To avoid apparent memory leaks when *note
     asyncio.open_connection(): abb. raises, break reference cycles
     generated by local exception and future instances (which has
     exception instance as its member var).  Patch by Dong Uk, Kang.

   - gh-91078(30): ‘TarFile.next()’ now returns ‘None’ when called on an
     empty tarfile.

   - bpo-47220(31): Document the optional 'callback' parameter of
     ‘WeakMethod’.  Patch by Géry Ogam.

   - bpo-44817(32): Ignore WinError 53 (ERROR_BAD_NETPATH), 65
     (ERROR_NETWORK_ACCESS_DENIED) and 161 (ERROR_BAD_PATHNAME) when
     using ntpath.realpath().

   - bpo-41260(33): Rename the 'fmt' parameter of the pure Python
     implementation of *note datetime.date.strftime(): c38. to 'format'.

   - bpo-15999(34): All built-in functions now accept arguments of any
     type instead of just ‘bool’ and ‘int’ for boolean parameters.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/100001

   (2) https://github.com/python/cpython/issues/99957

   (3) https://github.com/python/cpython/issues/79033

   (4) https://github.com/python/cpython/issues/51524

   (5) https://github.com/python/cpython/issues/99645

   (6) https://github.com/python/cpython/issues/99508

   (7) https://github.com/python/cpython/issues/66285

   (8) https://github.com/python/cpython/issues/97001

   (9) https://github.com/python/cpython/issues/92647

   (10) https://github.com/python/cpython/issues/99388

   (11) https://github.com/python/cpython/issues/99341

   (12) https://github.com/python/cpython/issues/99382

   (13) https://github.com/python/cpython/issues/99379

   (14) https://github.com/python/cpython/issues/99344

   (15) https://github.com/python/cpython/issues/99284

   (16) https://github.com/python/cpython/issues/99201

   (17) https://github.com/python/cpython/issues/99240

   (18) https://github.com/python/cpython/issues/64490

   (19) https://github.com/python/cpython/issues/99029

   (20) https://github.com/python/cpython/issues/98253

   (21) https://github.com/python/cpython/issues/98458

   (22) https://github.com/python/cpython/issues/93453

   (23) https://github.com/python/cpython/issues/97966

   (24) https://github.com/python/cpython/issues/98248

   (25) https://github.com/python/cpython/issues/98108

   (26) https://github.com/python/cpython/issues/98098

   (27) https://github.com/python/cpython/issues/82836

   (28) https://github.com/python/cpython/issues/96828

   (29) https://github.com/python/cpython/issues/88863

   (30) https://github.com/python/cpython/issues/91078

   (31) https://bugs.python.org/issue?@action=redirect&bpo=47220

   (32) https://bugs.python.org/issue?@action=redirect&bpo=44817

   (33) https://bugs.python.org/issue?@action=redirect&bpo=41260

   (34) https://bugs.python.org/issue?@action=redirect&bpo=15999


File: python.info,  Node: Documentation<13>,  Next: Tests<16>,  Prev: Library<18>,  Up: Python 3 12 0 alpha 3

1.23.19.4 Documentation
.......................

   - gh-99931(1): Use sphinxext-opengraph(2) to generate OpenGraph
     metadata(3).

   - gh-89682(4): Reworded docstring of the default ‘__contains__’ to
     clarify that it returns a *note bool: 40e.

   - gh-88330(5): Improved the description of what a resource is in
     importlib.resources docs.

   - gh-92892(6): Document that calling variadic functions with ctypes
     requires special care on macOS/arm64 (and possibly other
     platforms).

   - bpo-41825(7): Restructured the documentation for the *note
     os.wait*: d3e. family of functions, and improved the docs for *note
     os.waitid(): d3f. with more explanation of the possible argument
     constants.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/99931

   (2) https://sphinxext-opengraph.readthedocs.io/

   (3) https://ogp.me/

   (4) https://github.com/python/cpython/issues/89682

   (5) https://github.com/python/cpython/issues/88330

   (6) https://github.com/python/cpython/issues/92892

   (7) https://bugs.python.org/issue?@action=redirect&bpo=41825


File: python.info,  Node: Tests<16>,  Next: Build<18>,  Prev: Documentation<13>,  Up: Python 3 12 0 alpha 3

1.23.19.5 Tests
...............

   - gh-99892(1): Skip test_normalization() of test_unicodedata if it
     fails to download NormalizationTest.txt file from pythontest.net.
     Patch by Victor Stinner.

   - gh-99934(2): Correct test_marsh on (32 bit) x86: test_deterministic
     sets was failing.

   - gh-99741(3): We've implemented multi-phase init (PEP 489/630/687)
     for the internal (for testing) _xxsubinterpreters module.

   - gh-99659(4): Optional big memory tests in ‘test_sqlite3’ now catch
     the correct ‘sqlite.DataError’ exception type in case of too large
     strings and/or blobs passed.

   - gh-99593(5): Cover the Unicode C API with tests.

   - gh-96002(6): Add functional test for Argument Clinic.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/99892

   (2) https://github.com/python/cpython/issues/99934

   (3) https://github.com/python/cpython/issues/99741

   (4) https://github.com/python/cpython/issues/99659

   (5) https://github.com/python/cpython/issues/99593

   (6) https://github.com/python/cpython/issues/96002


File: python.info,  Node: Build<18>,  Next: Windows<15>,  Prev: Tests<16>,  Up: Python 3 12 0 alpha 3

1.23.19.6 Build
...............

   - gh-99086(1): Fix ‘-Wimplicit-int’, ‘-Wstrict-prototypes’, and
     ‘-Wimplicit-function-declaration’ compiler warnings in ‘configure’
     checks.

   - gh-99337(2): Fix a compilation issue with GCC 12 on macOS.

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

   - gh-98872(4): Fix a possible fd leak in ‘Programs/_freeze_module.c’
     introduced in Python 3.11.

   - gh-88226(5): Always define ‘TARGET_*’ labels in ‘Python/ceval.c’,
     even if ‘USE_COMPUTED_GOTOS’ is disabled.  This allows breakpoints
     to be set at those labels in (for instance) ‘gdb’.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/99086

   (2) https://github.com/python/cpython/issues/99337

   (3) https://github.com/python/cpython/issues/99289

   (4) https://github.com/python/cpython/issues/98872

   (5) https://github.com/python/cpython/issues/88226


File: python.info,  Node: Windows<15>,  Next: macOS<11>,  Prev: Build<18>,  Up: Python 3 12 0 alpha 3

1.23.19.7 Windows
.................

   - gh-99345(1): Use faster initialization functions to detect install
     location for Windows Store package

   - gh-98629(2): Fix initialization of *note sys.version: 15c. and
     ‘sys._git’ on Windows

   - gh-99442(3): Fix handling in *note Python Launcher for Windows:
     562. when ‘argv[0]’ does not include a file extension.

   - bpo-40882(4): Fix a memory leak in *note
     multiprocessing.shared_memory.SharedMemory: 154f. on Windows.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/99345

   (2) https://github.com/python/cpython/issues/98629

   (3) https://github.com/python/cpython/issues/99442

   (4) https://bugs.python.org/issue?@action=redirect&bpo=40882


File: python.info,  Node: macOS<11>,  Next: Tools/Demos<9>,  Prev: Windows<15>,  Up: Python 3 12 0 alpha 3

1.23.19.8 macOS
...............

   - gh-87235(1): On macOS ‘python3 /dev/fd/9 9</path/to/script.py’
     failed for any script longer than a couple of bytes.

   - gh-98940(2): Fix ‘Mac/Extras.install.py’ file filter bug.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/87235

   (2) https://github.com/python/cpython/issues/98940


File: python.info,  Node: Tools/Demos<9>,  Next: C API<17>,  Prev: macOS<11>,  Up: Python 3 12 0 alpha 3

1.23.19.9 Tools/Demos
.....................

   - gh-64490(1): Argument Clinic varargs bugfixes

        * Fix out-of-bounds error in
          ‘_PyArg_UnpackKeywordsWithVararg()’.

        * Fix incorrect check which allowed more than one varargs in
          clinic.py.

        * Fix miscalculation of ‘noptargs’ in generated code.

        * Do not generate ‘noptargs’ when there is a vararg argument and
          no optional argument.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/64490


File: python.info,  Node: C API<17>,  Prev: Tools/Demos<9>,  Up: Python 3 12 0 alpha 3

1.23.19.10 C API
................

   - gh-98680(1): ‘PyBUF_*’ constants were marked as part of Limited API
     of Python 3.11+.  These were available in 3.11.0 with *note
     Py_LIMITED_API: 35a. defined for 3.11, and are necessary to use the
     buffer API.

   - gh-99612(2): Fix *note PyUnicode_DecodeUTF8Stateful(): 16a2. for
     ASCII-only data: ‘*consumed’ was not set.

   - gh-47146(3): The ‘structmember.h’ header is deprecated.  Its
     non-deprecated contents are now available just by including
     ‘Python.h’, with a ‘Py_’ prefix added if it was missing.
     (Deprecated contents are *note T_OBJECT: 539, *note T_NONE: 53b,
     and no-op flags.)  Patch by Petr Viktorin, based on earlier work by
     Alexander Belopolsky and Matthias Braun.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/98680

   (2) https://github.com/python/cpython/issues/99612

   (3) https://github.com/python/cpython/issues/47146


File: python.info,  Node: Python 3 12 0 alpha 2,  Next: Python 3 12 0 alpha 1,  Prev: Python 3 12 0 alpha 3,  Up: Changelog（更動日誌）

1.23.20 Python 3.12.0 alpha 2
-----------------------------

'Release date: 2022-11-14'

* Menu:

* Security: Security<13>.
* Core and Builtins: Core and Builtins<20>.
* Library: Library<19>.
* Documentation: Documentation<14>.
* Tests: Tests<17>.
* Build: Build<19>.
* Windows: Windows<16>.
* macOS: macOS<12>.
* C API: C API<18>.


File: python.info,  Node: Security<13>,  Next: Core and Builtins<20>,  Up: Python 3 12 0 alpha 2

1.23.20.1 Security
..................

   - gh-98433(1): The IDNA codec decoder used on DNS hostnames by *note
     socket: b8. or *note asyncio: 8. related name resolution functions
     no longer involves a quadratic algorithm.  This prevents a
     potential CPU denial of service if an out-of-spec excessive length
     hostname involving bidirectional characters were decoded.  Some
     protocols such as *note urllib: f1. http ‘3XX’ redirects
     potentially allow for an attacker to supply such a name.

     Individual labels within an IDNA encoded DNS name will now raise an
     error early during IDNA decoding if they are longer than 1024
     unicode characters given that each decoded DNS label must be 63 or
     fewer characters and the entire decoded DNS name is limited to 255.
     Only an application presenting a hostname or label consisting
     primarily of RFC 3454(2) section 3.1 "Nothing" characters to be
     removed would run into of this new limit.  See also RFC 5894(3)
     section 6 and RFC 3491(4).

   - gh-98739(5): Update bundled libexpat to 2.5.0

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/98433

   (2) https://datatracker.ietf.org/doc/html/rfc3454.html

   (3) https://datatracker.ietf.org/doc/html/rfc5894.html

   (4) https://datatracker.ietf.org/doc/html/rfc3491.html

   (5) https://github.com/python/cpython/issues/98739


File: python.info,  Node: Core and Builtins<20>,  Next: Library<19>,  Prev: Security<13>,  Up: Python 3 12 0 alpha 2

1.23.20.2 Core and Builtins
...........................

   - gh-81057(1): The docs clearly say that ‘PyImport_Inittab’, *note
     PyImport_AppendInittab(): 16a6, and *note PyImport_ExtendInittab():
     16a7. should not be used after *note Py_Initialize(): 851. has been
     called.  We now enforce this for the two functions.  Additionally,
     the runtime now uses an internal copy of ‘PyImport_Inittab’, to
     guard against modification.

   - gh-99298(2): Fix an issue that could potentially cause incorrect
     error handling for some bytecode instructions.

   - gh-99254(3): The compiler now removes all unused constants from
     code objects (except the first one, which may be a docstring).

   - gh-99205(4): Fix an issue that prevented *note PyThreadState: 731.
     and *note PyInterpreterState: 862. memory from being freed
     properly.

   - gh-81057(5): The 18 global C variables holding the state of the
     allocators have been moved to ‘_PyRuntimeState’.  This is a
     strictly internal change with no change in behavior.

   - gh-99181(6): Fix failure in *note except*: 55c. with unhashable
     exceptions.

   - gh-99204(7): Fix calculation of ‘sys._base_executable’ when inside
     a POSIX virtual environment using copies of the python binary when
     the base installation does not provide the executable name used by
     the venv.  Calculation will fall back to alternative names
     ("python<MAJOR>", "python<MAJOR>.<MINOR>").

   - gh-96055(8): Update *note faulthandler: 4e. to emit an error
     message with the proper unexpected signal number.  Patch by Donghee
     Na.

   - gh-99153(9): Fix location of *note SyntaxError: 173. for a *note
     try: 68c. block with both *note except: 171. and *note except*:
     55c.

   - gh-98686(10): Merge the adaptive opcode logic into each
     instruction's unquickened variant, and merge the logic in
     ‘EXTENDED_ARG_QUICK’ into *note EXTENDED_ARG: 16a8.  With these
     changes, the quickening that happens at code object creation is now
     only responsible for initializing warmup counters and inserting
     superinstructions.

   - gh-99103(11): Fix the error reporting positions of specialized
     traceback anchors when the source line contains Unicode characters.

   - gh-99139(12): Improve the error suggestion for *note NameError:
     3e5. exceptions for instances.  Now if a *note NameError: 3e5. 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.
     Patch by Pablo Galindo

   - gh-98401(13): Octal escapes with value larger than ‘0o377’ (ex:
     ‘"\477"’), deprecated in Python 3.11, now produce a *note
     SyntaxWarning: 40c, instead of *note DeprecationWarning: 18b.  In a
     future Python version they will be eventually a *note SyntaxError:
     173.  Patch by Victor Stinner.

   - gh-98401(14): A backslash-character pair that is not a valid escape
     sequence now generates a *note SyntaxWarning: 40c, instead of *note
     DeprecationWarning: 18b.  For example, ‘re.compile("\d+\.\d+")’ now
     emits a *note SyntaxWarning: 40c. (‘"\d"’ is an invalid escape
     sequence), use raw strings for regular expression:
     ‘re.compile(r"\d+\.\d+")’.  In a future Python version, *note
     SyntaxError: 173. will eventually be raised, instead of *note
     SyntaxWarning: 40c.  Patch by Victor Stinner.

   - gh-96793(15): Handle StopIteration and StopAsyncIteration raised in
     generator or coroutines in the bytecode, rather than in wrapping C
     code.

   - gh-98931(16): Improve the *note SyntaxError: 173. error message
     when the user types ‘import x from y’ instead of ‘from y import x’.
     Patch by Pablo Galindo

   - gh-98852(17): Fix subscription of type aliases containing bare
     generic types or types like *note TypeVar: 141.: for example
     ‘tuple[A, T][int]’ and ‘tuple[TypeVar, T][int]’, where ‘A’ is a
     generic type, and ‘T’ is a type variable.

   - gh-98925(18): Lower the recursion depth for marshal on WASI to
     support (in-development) wasmtime 2.0.

   - gh-98783(19): Fix multiple crashes in debug mode when ‘str’
     subclasses are used instead of ‘str’ itself.

   - gh-98811(20): Use complete source locations to simplify detection
     of ‘__future__’ imports which are not at the beginning of the file.
     Also corrects the offset in the exception raised in one case, which
     was off by one and impeded highlighting.

   - gh-96793(21): Add specialization of *note FOR_ITER: 1653. for
     generators.  Saves multiple layers of dispatch and checking to get
     from the *note FOR_ITER: 1653. instruction in the caller to the
     *note RESUME: 6a7. in the generator.

   - gh-98762(22): Fix source locations of *note match: 7b1.
     sub-patterns.

   - gh-98586(23): Added the methods *note PyObject_Vectorcall(): 501.
     and *note PyObject_VectorcallMethod(): 502. to the *note Limited
     API: 4f9. along with the auxiliary macro constant *note
     PY_VECTORCALL_ARGUMENTS_OFFSET: 503.

     The availability of these functions enables more efficient PEP
     590(24) vector calls from binary extension modules that avoid
     argument boxing/unboxing overheads.

   - gh-99257(25): Fix an issue where member descriptors (such as those
     for *note __slots__: 1458.) could behave incorrectly or crash
     instead of raising a *note TypeError: 4dd. when accessed via an
     instance of an invalid type.

   - gh-93143(26): Rather than changing ‘co_code’, the interpreter will
     now display a *note RuntimeWarning: 1a3. and assign *note None:
     61b. to any fast locals that are left unbound after jumps or *note
     del: 16a9. statements executed while tracing.

   - gh-96421(27): When calling into Python code from C code, through
     *note PyEval_EvalFrameEx(): fd1. or a related C-API function, a
     shim frame in inserted into the call stack.  This occurs in the
     ‘_PyEval_EvalFrameDefault()’ function.  The extra frame should be
     invisible to all Python and most C extensions, but out-of-process
     profilers and debuggers need to be aware of it.  These shim frames
     can be detected by checking ‘frame->owner ==
     FRAME_OWNED_BY_CSTACK’.

     Extensions implementing their own interpreters using PEP 523 need
     to be aware of this shim frame and the changes to the semantics of
     *note RETURN_VALUE: 16aa, *note YIELD_VALUE: 15bb, and *note
     RETURN_GENERATOR: 69f, which now clear the frame.

   - gh-98415(28): Fix detection of MAC addresses for *note uuid: f8. on
     certain OSs.  Patch by Chaim Sanders

   - gh-98686(29): Quicken all code objects, and specialize adaptive
     bytecode instructions more aggressively.

   - gh-92119(30): Print exception class name instead of its string
     representation when raising errors from *note ctypes: 22. calls.

   - gh-91058(31): *note ImportError: 352. raised from failed ‘from
     <module> import <name>’ now include suggestions for the value of
     ‘<name>’ based on the available names in ‘<module>’.  Patch by
     Pablo Galindo

   - gh-96793(32): The *note FOR_ITER: 1653. now leaves the iterator on
     the stack on termination of the loop.  This is to assist
     specialization of loops for generators.

   - gh-90716(33): Add _pylong.py module.  It includes asymptotically
     faster algorithms that can be used for operations on integers with
     many digits.  It is used by longobject.c to speed up some
     operations.

   - gh-95389(34): Expose *note ETH_P_ALL: 16ab. and some of the *note
     ETHERTYPE_* constants: 16ac. in *note socket: b8.  Patch by Noam
     Cohen.

   - gh-93696(35): Allow *note pdb: 94. to locate source for frozen
     modules in the standard library.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/81057

   (2) https://github.com/python/cpython/issues/99298

   (3) https://github.com/python/cpython/issues/99254

   (4) https://github.com/python/cpython/issues/99205

   (5) https://github.com/python/cpython/issues/81057

   (6) https://github.com/python/cpython/issues/99181

   (7) https://github.com/python/cpython/issues/99204

   (8) https://github.com/python/cpython/issues/96055

   (9) https://github.com/python/cpython/issues/99153

   (10) https://github.com/python/cpython/issues/98686

   (11) https://github.com/python/cpython/issues/99103

   (12) https://github.com/python/cpython/issues/99139

   (13) https://github.com/python/cpython/issues/98401

   (14) https://github.com/python/cpython/issues/98401

   (15) https://github.com/python/cpython/issues/96793

   (16) https://github.com/python/cpython/issues/98931

   (17) https://github.com/python/cpython/issues/98852

   (18) https://github.com/python/cpython/issues/98925

   (19) https://github.com/python/cpython/issues/98783

   (20) https://github.com/python/cpython/issues/98811

   (21) https://github.com/python/cpython/issues/96793

   (22) https://github.com/python/cpython/issues/98762

   (23) https://github.com/python/cpython/issues/98586

   (24) https://peps.python.org/pep-0590/

   (25) https://github.com/python/cpython/issues/99257

   (26) https://github.com/python/cpython/issues/93143

   (27) https://github.com/python/cpython/issues/96421

   (28) https://github.com/python/cpython/issues/98415

   (29) https://github.com/python/cpython/issues/98686

   (30) https://github.com/python/cpython/issues/92119

   (31) https://github.com/python/cpython/issues/91058

   (32) https://github.com/python/cpython/issues/96793

   (33) https://github.com/python/cpython/issues/90716

   (34) https://github.com/python/cpython/issues/95389

   (35) https://github.com/python/cpython/issues/93696


File: python.info,  Node: Library<19>,  Next: Documentation<14>,  Prev: Core and Builtins<20>,  Up: Python 3 12 0 alpha 2

1.23.20.3 Library
.................

   - gh-99418(1): Fix bug in *note urllib.parse.urlparse(): 2df. that
     causes URL schemes that begin with a digit, a plus sign, or a minus
     sign to be parsed incorrectly.

   - gh-94597(2): Deprecate *note asyncio.AbstractChildWatcher: 29d. to
     be removed in Python 3.14.  Patch by Kumar Aditya.

   - gh-99305(3): Improve performance of *note secrets.token_hex():
     16ae.

   - gh-74044(4): Fixed bug where *note inspect.signature(): 6dc.
     reported incorrect arguments for decorated methods.

   - gh-99275(5): Fix ‘SystemError’ in *note ctypes: 22. when exception
     was not set during ‘__initsubclass__’.

   - gh-99277(6): Remove older version of
     ‘_SSLProtocolTransport.get_write_buffer_limits’ in
     ‘asyncio.sslproto’

   - gh-99248(7): fix negative numbers failing in verify()

   - gh-99155(8): Fix *note statistics.NormalDist: 9dc. pickle with ‘0’
     and ‘1’ protocols.

   - gh-93464(9): ‘enum.auto()’ is now correctly activated when combined
     with other assignment values.  E.g.  ‘ONE = auto(), 'some text'’
     will now evaluate as ‘(1, 'some text')’.

   - gh-99134(10): Update the bundled copy of pip to version 22.3.1.

   - gh-92584(11): Remove the ‘distutils’ package.  It was deprecated in
     Python 3.10 by PEP 632(12) "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’.  Patch by Victor Stinner.

   - gh-98999(13): Now ‘_pyio’ is consistent with ‘_io’ in raising
     ‘ValueError’ when executing methods over closed buffers.

   - gh-83004(14): Clean up refleak on failed module initialisation in
     ‘_zoneinfo’

   - gh-83004(15): Clean up refleaks on failed module initialisation in
     ‘_pickle’

   - gh-83004(16): Clean up refleak on failed module initialisation in
     ‘_io’.

   - gh-98897(17): Fix memory leak in *note math.dist(): 9a6. when both
     points don't have the same dimension.  Patch by Kumar Aditya.

   - gh-98878(18): Use the frame bound builtins when offering a name
     suggestion in *note traceback: e7. to prevent crashing when
     ‘__builtins__’ is not a dict.

   - gh-98139(19): In ‘importlib._bootstrap’, enhance namespace package
     repr to ‘<module 'x' (namespace) from ['path']>’.

   - gh-90352(20): Fix ‘_SelectorDatagramTransport’ to inherit from
     *note DatagramTransport: 16af. in *note asyncio: 8.  Patch by Kumar
     Aditya.

   - gh-98793(21): Fix argument typechecks in ‘_overlapped.WSAConnect()’
     and ‘_overlapped.Overlapped.WSASendTo()’ functions.

   - gh-98744(22): Prevent crashing in *note traceback: e7. when
     retrieving the byte-offset for some source files that contain
     certain unicode characters.

   - gh-98740(23): Fix internal error in the *note re: a7. module which
     in very rare circumstances prevented compilation of a regular
     expression containing a *note conditional expression: 16b0. without
     the "else" branch.

   - gh-98703(24): Fix *note asyncio.StreamWriter.drain(): 16b1. to call
     ‘protocol.connection_lost’ callback only once on Windows.

   - gh-98624(25): Add a mutex to unittest.mock.NonCallableMock to
     protect concurrent access to mock attributes.

   - gh-98658(26): The *note array.array: 186. class now supports
     subscripting, making it a *note generic type: 3df.

   - gh-98284(27): Improved *note TypeError: 4dd. message for undefined
     abstract methods of a *note abc.ABC: ebb. instance.  The names of
     the missing methods are surrounded by single-quotes to highlight
     them.

   - gh-96151(28): Allow ‘BUILTINS’ to be a valid field name for frozen
     dataclasses.

   - gh-98086(29): Make sure ‘patch.dict()’ can be applied on async
     functions.

   - gh-72719(30): Remove modules ‘asyncore’ and ‘asynchat’, which were
     deprecated by PEP 594(31).

   - gh-96192(32): Fix handling of ‘bytes’ *note path-like objects: ac2.
     in ‘os.ismount()’.

   - gh-94172(33): *note ftplib: 54.: Remove the ‘FTP_TLS.ssl_version’
     class attribute: use the 'context' parameter instead.  Patch by
     Victor Stinner

   - gh-94172(34): Remove the 'keyfile' and 'certfile' parameters from
     the *note ftplib: 54, *note imaplib: 6a, *note poplib: 9a. and
     *note smtplib: b7. modules, and the 'key_file', 'cert_file' and
     'check_hostname' parameters from the *note http.client: 65. module,
     all deprecated since Python 3.6.  Use the 'context' parameter
     ('ssl_context' in *note imaplib: 6a.) instead.  Patch by Victor
     Stinner.

   - gh-83638(35): Add the *note autocommit: 45d. attribute to *note
     sqlite3.Connection: 22a. and the 'autocommit' parameter to *note
     sqlite3.connect(): 288. to control PEP 249(36)-compliant *note
     transaction handling: 45e.  Patch by Erlend E. Aasland.

   - gh-92452(37): Fixed a race condition that could cause *note
     sysconfig.get_config_var(): fce. to incorrectly return *note None:
     61b. in multi-threaded programs.

   - gh-91803(38): Fix an error when using a method of objects mocked
     with *note unittest.mock.create_autospec(): 14fb. after it was
     sealed with *note unittest.mock.seal(): b48. function.

   - bpo-38523(39): *note shutil.copytree(): 9cd. now applies the
     'ignore_dangling_symlinks' argument recursively.

   - bpo-40358(40): Add walk_up argument in *note
     pathlib.PurePath.relative_to(): 2ac.

   - bpo-36267(41): Fix IndexError in *note argparse.ArgumentParser:
     4de. when a ‘store_true’ action is given an explicit argument.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/99418

   (2) https://github.com/python/cpython/issues/94597

   (3) https://github.com/python/cpython/issues/99305

   (4) https://github.com/python/cpython/issues/74044

   (5) https://github.com/python/cpython/issues/99275

   (6) https://github.com/python/cpython/issues/99277

   (7) https://github.com/python/cpython/issues/99248

   (8) https://github.com/python/cpython/issues/99155

   (9) https://github.com/python/cpython/issues/93464

   (10) https://github.com/python/cpython/issues/99134

   (11) https://github.com/python/cpython/issues/92584

   (12) https://peps.python.org/pep-0632/

   (13) https://github.com/python/cpython/issues/98999

   (14) https://github.com/python/cpython/issues/83004

   (15) https://github.com/python/cpython/issues/83004

   (16) https://github.com/python/cpython/issues/83004

   (17) https://github.com/python/cpython/issues/98897

   (18) https://github.com/python/cpython/issues/98878

   (19) https://github.com/python/cpython/issues/98139

   (20) https://github.com/python/cpython/issues/90352

   (21) https://github.com/python/cpython/issues/98793

   (22) https://github.com/python/cpython/issues/98744

   (23) https://github.com/python/cpython/issues/98740

   (24) https://github.com/python/cpython/issues/98703

   (25) https://github.com/python/cpython/issues/98624

   (26) https://github.com/python/cpython/issues/98658

   (27) https://github.com/python/cpython/issues/98284

   (28) https://github.com/python/cpython/issues/96151

   (29) https://github.com/python/cpython/issues/98086

   (30) https://github.com/python/cpython/issues/72719

   (31) https://peps.python.org/pep-0594/

   (32) https://github.com/python/cpython/issues/96192

   (33) https://github.com/python/cpython/issues/94172

   (34) https://github.com/python/cpython/issues/94172

   (35) https://github.com/python/cpython/issues/83638

   (36) https://peps.python.org/pep-0249/

   (37) https://github.com/python/cpython/issues/92452

   (38) https://github.com/python/cpython/issues/91803

   (39) https://bugs.python.org/issue?@action=redirect&bpo=38523

   (40) https://bugs.python.org/issue?@action=redirect&bpo=40358

   (41) https://bugs.python.org/issue?@action=redirect&bpo=36267


File: python.info,  Node: Documentation<14>,  Next: Tests<17>,  Prev: Library<19>,  Up: Python 3 12 0 alpha 2

1.23.20.4 Documentation
.......................

   - gh-98832(1): Changes wording of docstring for *note
     pathlib.Path.iterdir(): 1525.

   - gh-97966(2): Update uname docs to clarify the special nature of the
     platform attribute and to indicate when it became late-bound.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/98832

   (2) https://github.com/python/cpython/issues/97966


File: python.info,  Node: Tests<17>,  Next: Build<19>,  Prev: Documentation<14>,  Up: Python 3 12 0 alpha 2

1.23.20.5 Tests
...............

   - gh-98903(1): The Python test suite now fails with exit code 4 if no
     tests ran.  It should help detecting typos in test names and test
     methods.

   - gh-98713(2): Fix a bug in the *note typing: ed. tests where a test
     relying on CPython-specific implementation details was not
     decorated with ‘@cpython_only’ and was not skipped on other
     implementations.

   - gh-87390(3): Add tests for star-unpacking with PEP 646, and some
     other miscellaneous PEP 646 tests.

   - gh-96853(4): Added explicit coverage of ‘Py_Initialize’ (and hence
     ‘Py_InitializeEx’) back to the embedding tests (all other embedding
     tests migrated to ‘Py_InitializeFromConfig’ in Python 3.11)

   - bpo-34272(5): Some C API tests were moved into the new
     Lib/test/test_capi/ directory.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/98903

   (2) https://github.com/python/cpython/issues/98713

   (3) https://github.com/python/cpython/issues/87390

   (4) https://github.com/python/cpython/issues/96853

   (5) https://bugs.python.org/issue?@action=redirect&bpo=34272


File: python.info,  Node: Build<19>,  Next: Windows<16>,  Prev: Tests<17>,  Up: Python 3 12 0 alpha 2

1.23.20.6 Build
...............

   - gh-99086(1): Fix ‘-Wimplicit-int’ compiler warning in ‘configure’
     check for ‘PTHREAD_SCOPE_SYSTEM’.

   - gh-99016(2): Fix build with ‘PYTHON_FOR_REGEN=python3.8’.

   - gh-97731(3): Specify the full path to the source location for ‘make
     docclean’ (needed for cross-builds).

   - gh-98949(4): Drop unused build dependency on ‘readelf’.

   - gh-98989(5): Use ‘python3.11’, if available, for regeneration and
     freezing.

   - gh-98831(6): Add new tooling, in ‘Tools/cases_generator’, to
     generate the interpreter switch statement from a list of opcode
     definitions.  This only affects adding, modifying or removing
     instruction definitions.  The instruction definitions now live in
     ‘Python/bytecodes.c’, in the form of a custom DSL (under
     development)(7).  The tooling reads this file and writes
     ‘Python/generated_cases.c.h’, which is then included by
     ‘Python/ceval.c’ to provide most of the cases of the main
     interpreter switch.

   - gh-98817(8): Remove PCbuild/lib.pyproj: it's not used for anything,
     is only a minor convenience for Visual Studio users (who probably
     mostly don't even know about it), and it takes a lot of maintenance
     effort to keep updated.

   - gh-98776(9): Fix ‘make regen-test-levenshtein’ for out-of-tree
     builds.

   - gh-98707(10): Don't use vendored ‘libmpdec’ headers if *note
     -with-system-libmpdec: 34d. is passed to ‘configure’.  Don't use
     vendored ‘libexpat’ headers if *note -with-system-expat: 16b5. is
     passed to ‘configure’.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/99086

   (2) https://github.com/python/cpython/issues/99016

   (3) https://github.com/python/cpython/issues/97731

   (4) https://github.com/python/cpython/issues/98949

   (5) https://github.com/python/cpython/issues/98989

   (6) https://github.com/python/cpython/issues/98831

   (7) 
https://github.com/faster-cpython/ideas/blob/main/3.12/interpreter_definition.md

   (8) https://github.com/python/cpython/issues/98817

   (9) https://github.com/python/cpython/issues/98776

   (10) https://github.com/python/cpython/issues/98707


File: python.info,  Node: Windows<16>,  Next: macOS<12>,  Prev: Build<19>,  Up: Python 3 12 0 alpha 2

1.23.20.7 Windows
.................

   - gh-98689(1): Update Windows builds to zlib v1.2.13.  v1.2.12 has
     CVE-2022-37434(2), but the vulnerable ‘inflateGetHeader’ API is not
     used by Python.

   - gh-98790(3): Assumes that a missing ‘DLLs’ directory means that
     standard extension modules are in the executable's directory.

   - gh-98745(4): Update ‘py.exe’ launcher to install 3.11 by default
     and 3.12 on request.

   - gh-98692(5): Fix the *note Python Launcher for Windows: 562.
     ignoring unrecognized shebang lines instead of treating them as
     local paths

   - gh-94328(6): Update Windows installer to use SQLite 3.39.4.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/98689

   (2) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-37434

   (3) https://github.com/python/cpython/issues/98790

   (4) https://github.com/python/cpython/issues/98745

   (5) https://github.com/python/cpython/issues/98692

   (6) https://github.com/python/cpython/issues/94328


File: python.info,  Node: macOS<12>,  Next: C API<18>,  Prev: Windows<16>,  Up: Python 3 12 0 alpha 2

1.23.20.8 macOS
...............

   - gh-94328(1): Update macOS installer to SQLite 3.39.4.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/94328


File: python.info,  Node: C API<18>,  Prev: macOS<12>,  Up: Python 3 12 0 alpha 2

1.23.20.9 C API
...............

   - gh-98724(1): The *note Py_CLEAR: 51e, *note Py_SETREF: 51f. and
     *note Py_XSETREF: 520. macros now only evaluate their argument
     once.  If the argument has side effects, these side effects are no
     longer duplicated.  Patch by Victor Stinner.

   - gh-98978(2): Fix use-after-free in ‘Py_SetPythonHome(NULL)’,
     ‘Py_SetProgramName(NULL)’ and ‘_Py_SetProgramFullPath(NULL)’
     function calls.  Issue reported by Benedikt Reinartz.  Patch by
     Victor Stinner.

   - gh-98410(3): Add ‘getbufferproc’ and ‘releasebufferproc’ to the
     stable API.

   - gh-98610(4): Some configurable capabilities of sub-interpreters
     have changed.  They always allow subprocesses (*note subprocess:
     c1.) now, whereas before subprocesses could be optionally
     disallowed for a sub-interpreter.  Instead ‘os.exec()’ can now be
     disallowed.  Disallowing daemon threads is now supported.
     Disallowing all threads is still allowed, but is never done by
     default.  Note that the optional restrictions are only available
     through ‘_Py_NewInterpreterFromConfig()’, which isn't a public API.
     They do not affect the main interpreter, nor *note
     Py_NewInterpreter(): 16b9.

   - gh-98608(5): A ‘_PyInterpreterConfig’ has been added and
     ‘_Py_NewInterpreter()’ has been renamed to
     ‘_Py_NewInterpreterFromConfig()’.  The "isolated_subinterpreters"
     argument is now a granular config that captures the previous
     behavior.  Note that this is all "private" API.

   - gh-96853(6): ‘Py_InitializeEx’ now correctly calls ‘PyConfig_Clear’
     after initializing the interpreter (the omission didn't cause a
     memory leak only because none of the dynamically allocated config
     fields are populated by the wrapper function)

   - gh-91248(7): Add *note PyFrame_GetVar(): 50e. and *note
     PyFrame_GetVarString(): 50f. functions to get a frame variable by
     its name.  Patch by Victor Stinner.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/98724

   (2) https://github.com/python/cpython/issues/98978

   (3) https://github.com/python/cpython/issues/98410

   (4) https://github.com/python/cpython/issues/98610

   (5) https://github.com/python/cpython/issues/98608

   (6) https://github.com/python/cpython/issues/96853

   (7) https://github.com/python/cpython/issues/91248


File: python.info,  Node: Python 3 12 0 alpha 1,  Next: Python 3 11 0 beta 1,  Prev: Python 3 12 0 alpha 2,  Up: Changelog（更動日誌）

1.23.21 Python 3.12.0 alpha 1
-----------------------------

'Release date: 2022-10-25'

* Menu:

* Security: Security<14>.
* Core and Builtins: Core and Builtins<21>.
* Library: Library<20>.
* Documentation: Documentation<15>.
* Tests: Tests<18>.
* Build: Build<20>.
* Windows: Windows<17>.
* macOS: macOS<13>.
* IDLE: IDLE<13>.
* Tools/Demos: Tools/Demos<10>.
* C API: C API<19>.


File: python.info,  Node: Security<14>,  Next: Core and Builtins<21>,  Up: Python 3 12 0 alpha 1

1.23.21.1 Security
..................

   - gh-97616(1): Fix multiplying a list by an integer (‘list *= int’):
     detect the integer overflow when the new allocated length is close
     to the maximum size.  Issue reported by Jordan Limor.  Patch by
     Victor Stinner.

   - gh-97514(2): On Linux the *note multiprocessing: 86. module returns
     to using filesystem backed unix domain sockets for communication
     with the 'forkserver' process instead of the Linux abstract socket
     namespace.  Only code that chooses to use the *note "forkserver"
     start method: 2aa. is affected.

     Abstract sockets have no permissions and could allow any user on
     the system in the same network namespace(3) (often the whole
     system) to inject code into the multiprocessing 'forkserver'
     process.  This was a potential privilege escalation.  Filesystem
     based socket permissions restrict this to the 'forkserver' process
     user as was the default in Python 3.8 and earlier.

     This prevents Linux CVE-2022-42919(4).

   - gh-87389(5): *note http.server: 68.: Fix an open redirection
     vulnerability in the HTTP server when an URI path starts with ‘//’.
     Vulnerability discovered, and initial fix proposed, by Hamza Avvan.

   - gh-79096(6): LWPCookieJar and MozillaCookieJar create files with
     file mode 600 instead of 644 (Microsoft Windows is not affected)

   - gh-92888(7): Fix ‘memoryview’ use after free when accessing the
     backing buffer in certain cases.

   - gh-68966(8): The deprecated mailcap module now refuses to inject
     unsafe text (filenames, MIME types, parameters) into shell
     commands.  Instead of using such text, it will warn and act as if a
     match was not found (or for test commands, as if the test failed).

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/97616

   (2) https://github.com/python/cpython/issues/97514

   (3) https://man7.org/linux/man-pages/man7/network_namespaces.7.html

   (4) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-42919

   (5) https://github.com/python/cpython/issues/87389

   (6) https://github.com/python/cpython/issues/79096

   (7) https://github.com/python/cpython/issues/92888

   (8) https://github.com/python/cpython/issues/68966


File: python.info,  Node: Core and Builtins<21>,  Next: Library<20>,  Prev: Security<14>,  Up: Python 3 12 0 alpha 1

1.23.21.2 Core and Builtins
...........................

   - gh-98374(1): Suppress ImportError for invalid query for help()
     command.  Patch by Donghee Na.

   - gh-98461(2): Fix source location in bytecode for list, set and dict
     comprehensions as well as generator expressions.

   - gh-98354(3): Added unicode check for ‘name’ attribute of ‘spec’
     argument passed in ‘_imp.create_builtin()’ function.

   - gh-98398(4): Fix source location of 'assert' bytecodes.

   - gh-98390(5): Fix location of sub-expressions of boolean
     expressions, by reducing their scope to that of the sub-expression.

   - gh-98254(6): Modules from the standard library are now potentially
     suggested as part of the error messages displayed by the
     interpreter when an *note NameError: 3e5. is raised to the top
     level.  Patch by Pablo Galindo

   - gh-97997(7): Add running column offset to the tokenizer state to
     avoid calculating AST column information with pointer arithmetic.

   - gh-97973(8): Modify the tokenizer to return all necessary
     information the parser needs to set location information in the AST
     nodes, so that the parser does not have to calculate those doing
     pointer arithmetic.

   - gh-96078(9): *note os.sched_yield(): 10a9. now release the GIL
     while calling sched_yield(2).  Patch by Donghee Na.

   - gh-97955(10): Migrate *note zoneinfo: 11a. to Argument Clinic.

   - gh-97912(11): The compiler now avoids quadratic behavior when
     finding which instructions should use the *note LOAD_FAST_CHECK:
     48d. opcode.

   - gh-97002(12): Fix an issue where several frame objects could be
     backed by the same interpreter frame, possibly leading to corrupted
     memory and hard crashes of the interpreter.

   - gh-97943(13): Bugfix: *note PyFunction_GetAnnotations(): 16bd.
     should return a borrowed reference.  It was returning a new
     reference.

   - gh-97922(14): The Garbage Collector now runs only on the eval
     breaker mechanism of the Python bytecode evaluation loop instead on
     object allocations.  The GC can also run when *note
     PyErr_CheckSignals(): 40d. 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.

   - gh-65961(15): When ‘__package__’ is different than
     ‘__spec__.parent’, raise a ‘DeprecationWarning’ instead of
     ‘ImportWarning’.

     Also remove ‘importlib.util.set_package()’ which was scheduled for
     removal.

   - gh-97850(16): Long deprecated, ‘module_repr()’ should now be
     completely eradicated.

   - gh-86298(17): In cases where ‘warnings.warn_explicit()’ consults
     the module's loader, an ‘DeprecationWarning’ is issued when
     ‘m.__loader__’ differs from ‘m.__spec__.loader’.

   - gh-97779(18): Ensure that all Python frame objects are backed by
     "complete" frames.

   - gh-91052(19): Add API for subscribing to modification events on
     selected dictionaries.

   - gh-97752(20): Fix possible data corruption or crashes when
     accessing the ‘f_back’ member of newly-created generator or
     coroutine frames.

   - gh-97591(21): Fixed a missing incref/decref pair in
     ‘Exception.__setstate__()’.  Patch by Ofey Chan.

   - gh-97670(22): Remove the ‘sys.getdxp()’ function and the
     ‘Tools/scripts/analyze_dxp.py’ script.  DXP stands for "dynamic
     execution pairs".  They were related to ‘DYNAMIC_EXECUTION_PROFILE’
     and ‘DXPAIRS’ macros which have been removed in Python 3.11.
     Python can now be built with *note ./configure -enable-pystats:
     16be. to gather statistics on Python opcodes.  Patch by Victor
     Stinner.

   - gh-94526(23): Fix the Python path configuration used to initialized
     *note sys.path: 37f. at Python startup.  Paths are no longer
     encoded to UTF-8/strict to avoid encoding errors if it contains
     surrogate characters (bytes paths are decoded with the
     surrogateescape error handler).  Patch by Victor Stinner.

   - gh-96670(24): The parser now raises *note SyntaxError: 173. when
     parsing source code containing null bytes.  Patch by Pablo Galindo

   - gh-96975(25): Fix a crash occurring when *note PyEval_GetFrame():
     16bf. is called while the topmost Python frame is in a
     partially-initialized state.

   - gh-96848(26): Fix command line parsing: reject *note -X
     int_max_str_digits: 15a. option with no value (invalid) when the
     *note PYTHONINTMAXSTRDIGITS: 16c0. environment variable is set to a
     valid limit.  Patch by Victor Stinner.

   - gh-95921(27): Fix overly-broad source position information for
     chained comparisons used as branching conditions.

   - gh-96821(28): Fix undefined behaviour in ‘audioop.c’.

   - gh-96821(29): Fix undefined behaviour in ‘_testcapimodule.c’.

   - gh-95778(30): When *note ValueError: 1e7. is raised if an integer
     is larger than the limit, mention the *note
     sys.set_int_max_str_digits(): 16c1. function in the error message.
     Patch by Victor Stinner.

   - gh-96387(31): At Python exit, sometimes a thread holding the GIL
     can wait forever for a thread (usually a daemon thread) which
     requested to drop the GIL, whereas the thread already exited.  To
     fix the race condition, the thread which requested the GIL drop now
     resets its request before exiting.  Issue discovered and analyzed
     by Mingliang ZHAO. Patch by Victor Stinner.

   - gh-96864(32): Fix a possible assertion failure, fatal error, or
     *note SystemError: 51b. if a line tracing event raises an exception
     while opcode tracing is enabled.

   - gh-95778(33): The ‘PyLong_FromString’ function was refactored to
     make it more maintainable and extensible.

   - gh-96678(34): Fix undefined behaviour in C code of null pointer
     arithmetic.

   - gh-96754(35): Make sure that all frame objects created are created
     from valid interpreter frames.  Prevents the possibility of invalid
     frames in backtraces and signal handlers.

   - gh-90997(36): Improve the performance of reading and writing inline
     bytecode caches on some platforms.

   - gh-96751(37): Remove dead code from ‘CALL_FUNCTION_EX’ opcode.

   - gh-90751(38): *note memoryview: 40f. now supports half-floats.
     Patch by Donghee Na and Antoine Pitrou.

   - gh-96678(39): Fix case of undefined behavior in ceval.c

   - gh-64373(40): Convert ‘_functools’ to argument clinic.

   - gh-96641(41): Do not expose ‘KeyWrapper’ in ‘_functools’.

   - gh-96636(42): Ensure that tracing, ‘sys.setrace()’, is turned on
     immediately.  In pre-release versions of 3.11, some tracing events
     might have been lost when turning on tracing in a ‘__del__’ method
     or interrupt.

   - gh-96572(43): Fix use after free in trace refs build mode.  Patch
     by Kumar Aditya.

   - gh-96611(44): When loading a file with invalid UTF-8 inside a
     multi-line string, a correct SyntaxError is emitted.

   - gh-96612(45): Make sure that incomplete frames do not show up in
     tracemalloc traces.

   - gh-90230(46): Fix compiler warnings and test failures when building
     with ‘--enable-pystats’.

   - gh-96587(47): Correctly raise ‘SyntaxError’ on exception groups (
     PEP 654(48)) on python versions prior to 3.11

   - gh-96569(49): Remove two cases of undefined behavior, by adding
     NULL checks.

   - gh-96582(50): Fix possible ‘NULL’ pointer dereference in
     ‘_PyThread_CurrentFrames’.  Patch by Kumar Aditya.

   - gh-91079(51): Separate Python recursion checking from C recursion
     checking which reduces the chance of C stack overflow and allows
     the recursion limit to be increased safely.

   - gh-93911(52): Fix an issue that could prevent *note LOAD_ATTR: 486.
     from specializing properly when accessing properties.

   - gh-96348(53): Emit a DeprecationWarning when *note throw(): 4a0,
     *note throw(): 49f. or *note athrow(): 4a1. are called with more
     than one argument.

   - gh-95196(54): Disable incorrect pickling of the C implemented
     classmethod descriptors.

   - gh-96364(55): Fix text signatures of ‘list.__getitem__’ and
     ‘dict.__getitem__’.

   - gh-96352(56): Fix *note AttributeError: 2f6. missing ‘name’ and
     ‘obj’ attributes in *note object.__getattribute__(): b79.  Patch by
     Philip Georgi.

   - gh-93554(57): Change the jump opcodes so that all conditional jumps
     are forward jumps.  Backward jumps are converted by the assembler
     into a conditional forward jump whose target is the fallthrough
     block (and with a reversed condition), followed by an unconditional
     backward jump.  For example:

     ‘POP_JUMP_IF_TRUE BACKWARD_TARGET’ becomes ‘POP_JUMP_IF_FALSE
     NEXT_BLOCK; JUMP BACKWARD_TARGET’.

     All the directed conditional jump opcodes were removed:
     ‘POP_JUMP_FORWARD_IF_TRUE’, ‘POP_JUMP_BACKWARD_IF_TRUE’,
     ‘POP_JUMP_FORWARD_IF_FALSE’, ‘POP_JUMP_BACKWARD_IF_FALSE’,
     ‘POP_JUMP_FORWARD_IF_NONE’, ‘POP_JUMP_BACKWARD_IF_NONE’,
     ‘POP_JUMP_FORWARD_IF_NOT_NONE’, ‘POP_JUMP_BACKWARD_IF_NOT_NONE’.

     The corresponding opcodes without direction are no longer
     pseudo-instructions, and they implement the forward conditional
     jumps.

   - gh-96268(58): Loading a file with invalid UTF-8 will now report the
     broken character at the correct location.

   - gh-96237(59): The internal field ‘_PyInterpreterFrame.f_func’ is
     renamed to ‘_PyInterpreterFrame.f_funcobj’ and may be any object.
     The ‘f_globals’ and ‘f_builtin’ fields may hold junk values.

     It is safest to treat the ‘_PyInterpreterFrame’ struct as opaque.

   - gh-96187(60): Fixed a bug that caused ‘_PyCode_GetExtra’ to return
     garbage for negative indexes.  Patch by Pablo Galindo

   - gh-96143(61): Add a new ‘-X perf’ Python command line option as
     well as *note sys.activate_stack_trampoline(): 416. and *note
     sys.deactivate_stack_trampoline(): 417. function in the *note sys:
     c3. module that allows to set/unset the interpreter in a way that
     the Linux ‘perf’ profiler can detect Python calls.  The new *note
     sys.is_stack_trampoline_active(): 418. function allows to query the
     state of the perf trampoline.  Design by Pablo Galindo.  Patch by
     Pablo Galindo and Christian Heimes with contributions from Gregory
     P. Smith [Google] and Mark Shannon.

   - gh-96071(62): Fix a deadlock in *note PyGILState_Ensure(): 376.
     when allocating new thread state.  Patch by Kumar Aditya.

   - gh-96046(63): *note PyType_Ready(): 722. now initializes
     ‘ht_cached_keys’ and performs additional checks to ensure that type
     objects are properly configured.  This avoids crashes in 3rd party
     packages that don't use regular API to create new types.

   - gh-96005(64): On WASI *note ENOTCAPABLE: 16c2. is now mapped to
     *note PermissionError: ce9.  The *note errno: 4d. modules exposes
     the new error number.  ‘getpath.py’ now ignores *note
     PermissionError: ce9. when it cannot open landmark files
     ‘pybuilddir.txt’ and ‘pyenv.cfg’.

   - gh-93678(65): Added test a harness for direct unit tests of the
     compiler's optimization stage.  The
     ‘_testinternalcapi.optimize_cfg()’ function runs the optimiser on a
     sequence of instructions.  The ‘CfgOptimizationTestCase’ class in
     ‘test.support’ has utilities for invoking the optimizer and
     checking the output.

   - gh-95245(66): Reduces the size of a "simple" Python object from 8
     to 6 words by moving the weakreflist pointer into the pre-header
     directly before the object's dict/values pointer.

   - gh-90997(67): Compile virtual *note try: 68c./*note except: 171.
     blocks to handle exceptions raised during *note close(): 15ee. or
     *note throw(): 4a0. calls through a suspended frame.

   - gh-95977(68): Optimized calling *note __get__(): 16c3. with
     vectorcall.  Patch by Kumar Aditya.

   - gh-91210(69): Improve error message when a parameter without a
     default value follows one with a default value, and show the same
     message, even when the non-default/default sequence is preceded by
     positional-only parameters.

   - gh-95922(70): Fixed bug where the compiler's
     ‘eliminate_empty_basic_blocks’ function ignores the last block of
     the code unit.

   - gh-95818(71): Skip over incomplete frames in *note
     PyThreadState_GetFrame(): 732.

   - gh-95876(72): Fix format string in
     ‘_PyPegen_raise_error_known_location’ that can lead to memory
     corruption on some 64bit systems.  The function was building a
     tuple with ‘i’ (int) instead of ‘n’ (Py_ssize_t) for Py_ssize_t
     arguments.

   - gh-95605(73): Fix misleading contents of error message when
     converting an all-whitespace string to *note float: 2c8.

   - gh-95150(74): Update code object hashing and equality to consider
     all debugging and exception handling tables.  This fixes an issue
     where certain non-identical code objects could be "deduplicated"
     during compilation.

   - gh-91146(75): Reduce allocation size of *note list: 5b6. from *note
     str.split(): e4c. and *note str.rsplit(): 11ee.  Patch by Donghee
     Na and Inada Naoki.

   - gh-87092(76): Create a 'jump target label' abstraction in the
     compiler so that the compiler's codegen stage does not work
     directly with basic blocks.  This prepares the code for changes to
     the underlying CFG generation mechanism.

   - gh-95355(77): ‘_PyPegen_Parser_New’ now properly detects token
     memory allocation errors.  Patch by Honglin Zhu.

   - gh-90081(78): Run Python code in tracer/profiler function at full
     speed.  Fixes slowdown in earlier versions of 3.11.

   - gh-95324(79): Emit a warning in debug mode if an object does not
     call *note PyObject_GC_UnTrack(): 1475. before deallocation.  Patch
     by Pablo Galindo.

   - gh-95245(80): Merge managed dict and values pointer into a single
     tagged pointer to save one word in the pre-header.

   - gh-93678(81): Add cfg_builder struct and refactor the relevant code
     so that a cfg can be constructed without an instance of the
     compiler struct.

   - gh-95185(82): Prevented crashes in the AST constructor when
     compiling some absurdly long expressions like ‘"+0"*1000000’.
     *note RecursionError: d12. is now raised instead.  Patch by Pablo
     Galindo

   - gh-93351(83): *note ast.AST: 18c. node positions are now validated
     when provided to *note compile(): 178. and other related functions.
     If invalid positions are detected, a *note ValueError: 1e7. will be
     raised.

   - gh-94438(84): Fix an issue that caused extended opcode arguments
     and some conditional pops to be ignored when calculating valid jump
     targets for assignments to the ‘f_lineno’ attribute of frame
     objects.  In some cases, this could cause inconsistent internal
     state, resulting in a hard crash of the interpreter.

   - gh-95060(85): Undocumented ‘PyCode_Addr2Location’ function now
     properly returns when ‘addrq’ argument is less than zero.

   - gh-95113(86): Replace all ‘EXTENDED_ARG_QUICK’ instructions with
     basic *note EXTENDED_ARG: 16a8. instructions in unquickened code.
     Consumers of non-adaptive bytecode should be able to handle
     extended arguments the same way they were handled in CPython 3.10
     and older.

   - gh-91409(87): Fix incorrect source location info caused by certain
     optimizations in the bytecode compiler.

   - gh-95023(88): Implement *note os.setns(): 16c4. and *note
     os.unshare(): 16c5. for Linux.  Patch by Noam Cohen.

   - gh-94036(89): Fix incorrect source location info for some
     multi-line attribute accesses and method calls.

   - gh-94938(90): Fix error detection in some builtin functions when
     keyword argument name is an instance of a str subclass with
     overloaded ‘__eq__’ and ‘__hash__’.  Previously it could cause
     SystemError or other undesired behavior.

   - gh-94996(91): *note ast.parse(): 18e. will no longer parse function
     definitions with positional-only params when passed
     ‘feature_version’ less than ‘(3, 8)’.  Patch by Shantanu Jain.

   - gh-94739(92): Allow jumping within, out of, and across exception
     handlers in the debugger.

   - gh-94949(93): *note ast.parse(): 18e. will no longer parse
     parenthesized context managers when passed ‘feature_version’ less
     than ‘(3, 9)’.  Patch by Shantanu Jain.

   - gh-94947(94): *note ast.parse(): 18e. will no longer parse
     assignment expressions when passed ‘feature_version’ less than ‘(3,
     8)’.  Patch by Shantanu Jain.

   - gh-91256(95): Ensures the program name is known for help text
     during interpreter startup.

   - gh-94869(96): Fix the column offsets for some expressions in
     multi-line f-strings *note ast: 7. nodes.  Patch by Pablo Galindo.

   - gh-94893(97): Fix an issue where frame object manipulations could
     corrupt inline bytecode caches.

   - gh-94822(98): Fix an issue where lookups of metaclass descriptors
     may be ignored when an identically-named attribute also exists on
     the class itself.

   - gh-91153(99): Fix an issue where a *note bytearray: 4e3. item
     assignment could crash if it's resized by the new value's
     ‘__index__()’ method.

   - gh-90699(100): Fix reference counting bug in ‘bool.__repr__()’.
     Patch by Kumar Aditya.

   - gh-94694(101): Fix an issue that could cause code with multi-line
     method lookups to have misleading or incorrect column offset
     information.  In some cases (when compiling a hand-built AST) this
     could have resulted in a hard crash of the interpreter.

   - gh-93252(102): Fix an issue that caused internal frames to outlive
     failed Python function calls, possibly resulting in memory leaks or
     hard interpreter crashes.

   - gh-94215(103): Fix an issue where exceptions raised by line-tracing
     events would cause frames to be left in an invalid state, possibly
     resulting in a hard crash of the interpreter.

   - gh-92228(104): Disable the compiler's inline-small-exit-blocks
     optimization for exit blocks that are associated with source code
     lines.  This fixes a bug where the debugger cannot tell where an
     exception handler ends and the following code block begins.

   - gh-94485(105): Line number of a module's ‘RESUME’ instruction is
     set to 0 as specified in PEP 626(106).

   - gh-94438(107): Account for instructions that can push NULL to the
     stack when setting line number in a frame.  Prevents some
     (unlikely) crashes.

   - gh-91719(108): Reload ‘opcode’ when raising ‘unknown opcode error’
     in the interpreter main loop, for C compilers to generate
     dispatching code independently.

   - gh-94329(109): Compile and run code with unpacking of extremely
     large sequences (1000s of elements).  Such code failed to compile.
     It now compiles and runs correctly.

   - gh-94360(110): Fixed a tokenizer crash when reading encoded files
     with syntax errors from ‘stdin’ with non utf-8 encoded text.  Patch
     by Pablo Galindo

   - gh-88116(111): Fix an issue when reading line numbers from code
     objects if the encoded line numbers are close to ‘INT_MIN’.  Patch
     by Pablo Galindo

   - gh-94262(112): Don't create frame objects for incomplete frames.
     Prevents the creation of generators and closures from being
     observable to Python and C extensions, restoring the behavior of
     3.10 and earlier.

   - gh-94192(113): Fix error for dictionary literals with invalid
     expression as value.

   - gh-87995(114): *note types.MappingProxyType: 414. instances are now
     hashable if the underlying mapping is hashable.

   - gh-93883(115): Revise the display strategy of traceback enhanced
     error locations.  The indicators are only shown when the location
     doesn't span the whole line.

   - gh-94163(116): Add *note BINARY_SLICE: 487. and *note STORE_SLICE:
     488. instructions for more efficient handling and better
     specialization of slicing operations, where the slice is explicit
     in the source code.

   - gh-94021(117): Fix unreachable code warning in
     ‘Python/specialize.c’.

   - gh-93911(118): Specialize ‘LOAD_ATTR’ for objects with custom
     ‘__getattribute__’.

   - gh-93955(119): Improve performance of attribute lookups on objects
     with custom ‘__getattribute__’ and ‘__getattr__’.  Patch by Ken
     Jin.

   - gh-93911(120): Specialize ‘LOAD_ATTR’ for ‘property()’ attributes.

   - gh-93678(121): Refactor compiler optimisation code so that it no
     longer needs the ‘struct assembler’ and ‘struct compiler’ passed
     around.  Instead, each function takes the CFG and other data that
     it actually needs.  This will make it possible to test this code
     directly.

   - gh-93841(122): When built with ‘-enable-pystats’,
     ‘sys._stats_on()’, ‘sys._stats_off()’, ‘sys._stats_clear()’ and
     ‘sys._stats_dump()’ functions have been added to enable gathering
     stats for parts of programs.

   - gh-93516(123): Store offset of first traceable instruction in code
     object to avoid having to recompute it for each instruction when
     tracing.

   - gh-93516(124): Lazily create a table mapping bytecode offsets to
     line numbers to speed up calculation of line numbers when tracing.

   - gh-89828(125): *note types.GenericAlias: 78f. no longer relays the
     ‘__class__’ attribute.  For example, ‘isinstance(list[int], type)’
     no longer returns ‘True’.

   - gh-93678(126): Refactor the compiler to reduce boilerplate and
     repetition.

   - gh-93671(127): Fix some exponential backtrace case happening with
     deeply nested sequence patterns in match statements.  Patch by
     Pablo Galindo

   - gh-93662(128): Make sure that the end column offsets are correct in
     multi-line method calls.  Previously, the end column could precede
     the column offset.

   - gh-93461(129): *note importlib.invalidate_caches(): bb7. now drops
     entries from *note sys.path_importer_cache: 588. with a relative
     path as name.  This solves a caching issue when a process changes
     its current working directory.

     ‘FileFinder’ no longer inserts a dot in the path, e.g.
     ‘/egg/./spam’ is now ‘/egg/spam’.

   - gh-93621(130): Change order of bytecode instructions emitted for
     *note with: 577. and *note async with: 57a. to reduce the number of
     entries in the exception table.

   - gh-93533(131): Reduce the size of the inline cache for
     ‘LOAD_METHOD’ by 2 bytes.

   - gh-93444(132): Removed redundant fields from the compiler's
     basicblock struct: ‘b_nofallthrough’, ‘b_exit’, ‘b_return’.  They
     can be easily calculated from the opcode of the last instruction of
     the block.

   - gh-93429(133): ‘LOAD_METHOD’ instruction has been removed.  It was
     merged back into ‘LOAD_ATTR’.

   - gh-93418(134): Fixed an assert where an f-string has an equal sign
     '=' following an expression, but there's no trailing brace.  For
     example, f"{i=".

   - gh-93382(135): Cache the result of *note PyCode_GetCode(): 71c.
     function to restore the 'O'(1) lookup of the ‘co_code’ attribute.

   - gh-93359(136): Ensure that custom *note ast: 7. nodes without
     explicit end positions can be compiled.  Patch by Pablo Galindo.

   - gh-93356(137): Code for exception handlers is emitted at the end of
     the code unit's bytecode.  This avoids one jump when no exception
     is raised.

   - gh-93354(138): Use exponential backoff for specialization counters
     in the interpreter.  Can reduce the number of failed
     specializations significantly and avoid slowdown for those parts of
     a program that are not suitable for specialization.

   - gh-93283(139): Improve error message for invalid syntax of
     conversion character in f-string expressions.

   - gh-93345(140): Fix a crash in substitution of a ‘TypeVar’ in nested
     generic alias after ‘TypeVarTuple’.

   - gh-93223(141): When a bytecode instruction jumps to an
     unconditional jump instruction, the first instruction can often be
     optimized to target the unconditional jump's target directly.  For
     tracing reasons, this would previously only occur if both
     instructions have the same line number.  This also now occurs if
     the unconditional jump is artificial, i.e., if it has no associated
     line number.

   - gh-84694(142): The ‘--experimental-isolated-subinterpreters’
     configure option and ‘EXPERIMENTAL_ISOLATED_SUBINTERPRETERS’ macro
     have been removed.

   - gh-91924(143): Fix ‘__lltrace__’ debug feature if the stdout
     encoding is not UTF-8.  Patch by Victor Stinner.

   - gh-93040(144): Wraps unused parameters in ‘Objects/obmalloc.c’ with
     ‘Py_UNUSED’.

   - gh-93143(145): Avoid ‘NULL’ checks for uninitialized local
     variables by determining at compile time which variables must be
     initialized.

   - gh-93061(146): Backward jumps after ‘async for’ loops are no longer
     given dubious line numbers.

   - gh-93065(147): Fix contextvars HAMT implementation to handle
     iteration over deep trees.

     The bug was discovered and fixed by Eli Libman.  See
     MagicStack/immutables#84(148) for more details.

   - gh-93012(149): Added the new function *note PyType_FromMetaclass():
     4f6, which generalizes the existing *note
     PyType_FromModuleAndSpec(): 4f7. using an additional metaclass
     argument.  This is useful for language binding tools, where it can
     be used to intercept type-related operations like subclassing or
     static attribute access by specifying a metaclass with custom
     slots.

     Importantly, *note PyType_FromMetaclass(): 4f6. is available in the
     Limited API, which provides a path towards migrating more binding
     tools onto the Stable ABI.

   - gh-93021(150): Fix the ‘__text_signature__’ for ‘__get__()’ methods
     implemented in C. Patch by Jelle Zijlstra.

   - gh-89914(151): The operand of the ‘YIELD_VALUE’ instruction is set
     to the stack depth.  This is done to help frame handling on ‘yield’
     and may assist debuggers.

   - gh-92955(152): Fix memory leak in code object's lines and positions
     iterators as they were not finalized at exit.  Patch by Kumar
     Aditya.

   - gh-92930(153): Fixed a crash in ‘_pickle.c’ from mutating
     collections during ‘__reduce__’ or ‘persistent_id’.

   - gh-90690(154): The PRECALL instruction has been removed.  It
     offered only a small advantage for specialization and is not needed
     in the vast majority of cases.

   - gh-92914(155): Always round the allocated size for lists up to the
     nearest even number.

   - gh-92858(156): Improve error message for some suites with syntax
     error before ':'

   - gh-90473(157): Decrease default recursion limit on WASI to address
     limited call stack size.

   - gh-92804(158): Fix memory leak in ‘memoryview’ iterator as it was
     not finalized at exit.  Patch by Kumar Aditya.

   - gh-92777(159): Specialize ‘LOAD_METHOD’ for objects with lazy
     dictionaries.  Patch by Ken Jin.

   - gh-92658(160): Add support for connecting and binding to Hyper-V
     sockets on Windows Hyper-V hosts and guests.

   - gh-92236(161): Remove spurious "LINE" event when starting a
     generator or coroutine, visible tracing functions implemented in C.

   - gh-91102(162): ‘_warnings.warn_explicit()’ is ported to Argument
     Clinic.

   - gh-92619(163): Make the compiler duplicate an exit block only if
     none of its instructions have a lineno (previously only the first
     instruction in the block was checked, leading to unnecessarily
     duplicated blocks).

   - gh-88750(164): The deprecated debug build only ‘PYTHONTHREADDEBUG’
     environment variable no longer does anything.

   - gh-92261(165): Fix hang when trying to iterate over a
     ‘typing.Union’.

   - gh-91432(166): Specialized the *note FOR_ITER: 1653. opcode using
     the PEP 659 machinery

   - gh-91399(167): Removed duplicate '{0, 0, 0, 0, 0, 0}' entry in
     'Objects/unicodetype_db.h'.

   - gh-91578(168): Updates the error message for abstract class.

   - bpo-47091(169): Improve performance of repetition of *note list:
     5b6. and *note tuple: 322. by using ‘memcpy’ to copy data and
     performing the reference increments in one step.

   - bpo-46142(170): Make ‘--help’ output shorter by moving some info to
     the new ‘--help-env’ and ‘--help-xoptions’ command-line options.
     Also add ‘--help-all’ option to print complete usage.

   - bpo-42316(171): Document some places where an assignment expression
     needs parentheses.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/98374

   (2) https://github.com/python/cpython/issues/98461

   (3) https://github.com/python/cpython/issues/98354

   (4) https://github.com/python/cpython/issues/98398

   (5) https://github.com/python/cpython/issues/98390

   (6) https://github.com/python/cpython/issues/98254

   (7) https://github.com/python/cpython/issues/97997

   (8) https://github.com/python/cpython/issues/97973

   (9) https://github.com/python/cpython/issues/96078

   (10) https://github.com/python/cpython/issues/97955

   (11) https://github.com/python/cpython/issues/97912

   (12) https://github.com/python/cpython/issues/97002

   (13) https://github.com/python/cpython/issues/97943

   (14) https://github.com/python/cpython/issues/97922

   (15) https://github.com/python/cpython/issues/65961

   (16) https://github.com/python/cpython/issues/97850

   (17) https://github.com/python/cpython/issues/86298

   (18) https://github.com/python/cpython/issues/97779

   (19) https://github.com/python/cpython/issues/91052

   (20) https://github.com/python/cpython/issues/97752

   (21) https://github.com/python/cpython/issues/97591

   (22) https://github.com/python/cpython/issues/97670

   (23) https://github.com/python/cpython/issues/94526

   (24) https://github.com/python/cpython/issues/96670

   (25) https://github.com/python/cpython/issues/96975

   (26) https://github.com/python/cpython/issues/96848

   (27) https://github.com/python/cpython/issues/95921

   (28) https://github.com/python/cpython/issues/96821

   (29) https://github.com/python/cpython/issues/96821

   (30) https://github.com/python/cpython/issues/95778

   (31) https://github.com/python/cpython/issues/96387

   (32) https://github.com/python/cpython/issues/96864

   (33) https://github.com/python/cpython/issues/95778

   (34) https://github.com/python/cpython/issues/96678

   (35) https://github.com/python/cpython/issues/96754

   (36) https://github.com/python/cpython/issues/90997

   (37) https://github.com/python/cpython/issues/96751

   (38) https://github.com/python/cpython/issues/90751

   (39) https://github.com/python/cpython/issues/96678

   (40) https://github.com/python/cpython/issues/64373

   (41) https://github.com/python/cpython/issues/96641

   (42) https://github.com/python/cpython/issues/96636

   (43) https://github.com/python/cpython/issues/96572

   (44) https://github.com/python/cpython/issues/96611

   (45) https://github.com/python/cpython/issues/96612

   (46) https://github.com/python/cpython/issues/90230

   (47) https://github.com/python/cpython/issues/96587

   (48) https://peps.python.org/pep-0654/

   (49) https://github.com/python/cpython/issues/96569

   (50) https://github.com/python/cpython/issues/96582

   (51) https://github.com/python/cpython/issues/91079

   (52) https://github.com/python/cpython/issues/93911

   (53) https://github.com/python/cpython/issues/96348

   (54) https://github.com/python/cpython/issues/95196

   (55) https://github.com/python/cpython/issues/96364

   (56) https://github.com/python/cpython/issues/96352

   (57) https://github.com/python/cpython/issues/93554

   (58) https://github.com/python/cpython/issues/96268

   (59) https://github.com/python/cpython/issues/96237

   (60) https://github.com/python/cpython/issues/96187

   (61) https://github.com/python/cpython/issues/96143

   (62) https://github.com/python/cpython/issues/96071

   (63) https://github.com/python/cpython/issues/96046

   (64) https://github.com/python/cpython/issues/96005

   (65) https://github.com/python/cpython/issues/93678

   (66) https://github.com/python/cpython/issues/95245

   (67) https://github.com/python/cpython/issues/90997

   (68) https://github.com/python/cpython/issues/95977

   (69) https://github.com/python/cpython/issues/91210

   (70) https://github.com/python/cpython/issues/95922

   (71) https://github.com/python/cpython/issues/95818

   (72) https://github.com/python/cpython/issues/95876

   (73) https://github.com/python/cpython/issues/95605

   (74) https://github.com/python/cpython/issues/95150

   (75) https://github.com/python/cpython/issues/91146

   (76) https://github.com/python/cpython/issues/87092

   (77) https://github.com/python/cpython/issues/95355

   (78) https://github.com/python/cpython/issues/90081

   (79) https://github.com/python/cpython/issues/95324

   (80) https://github.com/python/cpython/issues/95245

   (81) https://github.com/python/cpython/issues/93678

   (82) https://github.com/python/cpython/issues/95185

   (83) https://github.com/python/cpython/issues/93351

   (84) https://github.com/python/cpython/issues/94438

   (85) https://github.com/python/cpython/issues/95060

   (86) https://github.com/python/cpython/issues/95113

   (87) https://github.com/python/cpython/issues/91409

   (88) https://github.com/python/cpython/issues/95023

   (89) https://github.com/python/cpython/issues/94036

   (90) https://github.com/python/cpython/issues/94938

   (91) https://github.com/python/cpython/issues/94996

   (92) https://github.com/python/cpython/issues/94739

   (93) https://github.com/python/cpython/issues/94949

   (94) https://github.com/python/cpython/issues/94947

   (95) https://github.com/python/cpython/issues/91256

   (96) https://github.com/python/cpython/issues/94869

   (97) https://github.com/python/cpython/issues/94893

   (98) https://github.com/python/cpython/issues/94822

   (99) https://github.com/python/cpython/issues/91153

   (100) https://github.com/python/cpython/issues/90699

   (101) https://github.com/python/cpython/issues/94694

   (102) https://github.com/python/cpython/issues/93252

   (103) https://github.com/python/cpython/issues/94215

   (104) https://github.com/python/cpython/issues/92228

   (105) https://github.com/python/cpython/issues/94485

   (106) https://peps.python.org/pep-0626/

   (107) https://github.com/python/cpython/issues/94438

   (108) https://github.com/python/cpython/issues/91719

   (109) https://github.com/python/cpython/issues/94329

   (110) https://github.com/python/cpython/issues/94360

   (111) https://github.com/python/cpython/issues/88116

   (112) https://github.com/python/cpython/issues/94262

   (113) https://github.com/python/cpython/issues/94192

   (114) https://github.com/python/cpython/issues/87995

   (115) https://github.com/python/cpython/issues/93883

   (116) https://github.com/python/cpython/issues/94163

   (117) https://github.com/python/cpython/issues/94021

   (118) https://github.com/python/cpython/issues/93911

   (119) https://github.com/python/cpython/issues/93955

   (120) https://github.com/python/cpython/issues/93911

   (121) https://github.com/python/cpython/issues/93678

   (122) https://github.com/python/cpython/issues/93841

   (123) https://github.com/python/cpython/issues/93516

   (124) https://github.com/python/cpython/issues/93516

   (125) https://github.com/python/cpython/issues/89828

   (126) https://github.com/python/cpython/issues/93678

   (127) https://github.com/python/cpython/issues/93671

   (128) https://github.com/python/cpython/issues/93662

   (129) https://github.com/python/cpython/issues/93461

   (130) https://github.com/python/cpython/issues/93621

   (131) https://github.com/python/cpython/issues/93533

   (132) https://github.com/python/cpython/issues/93444

   (133) https://github.com/python/cpython/issues/93429

   (134) https://github.com/python/cpython/issues/93418

   (135) https://github.com/python/cpython/issues/93382

   (136) https://github.com/python/cpython/issues/93359

   (137) https://github.com/python/cpython/issues/93356

   (138) https://github.com/python/cpython/issues/93354

   (139) https://github.com/python/cpython/issues/93283

   (140) https://github.com/python/cpython/issues/93345

   (141) https://github.com/python/cpython/issues/93223

   (142) https://github.com/python/cpython/issues/84694

   (143) https://github.com/python/cpython/issues/91924

   (144) https://github.com/python/cpython/issues/93040

   (145) https://github.com/python/cpython/issues/93143

   (146) https://github.com/python/cpython/issues/93061

   (147) https://github.com/python/cpython/issues/93065

   (148) https://github.com/MagicStack/immutables/issues/84

   (149) https://github.com/python/cpython/issues/93012

   (150) https://github.com/python/cpython/issues/93021

   (151) https://github.com/python/cpython/issues/89914

   (152) https://github.com/python/cpython/issues/92955

   (153) https://github.com/python/cpython/issues/92930

   (154) https://github.com/python/cpython/issues/90690

   (155) https://github.com/python/cpython/issues/92914

   (156) https://github.com/python/cpython/issues/92858

   (157) https://github.com/python/cpython/issues/90473

   (158) https://github.com/python/cpython/issues/92804

   (159) https://github.com/python/cpython/issues/92777

   (160) https://github.com/python/cpython/issues/92658

   (161) https://github.com/python/cpython/issues/92236

   (162) https://github.com/python/cpython/issues/91102

   (163) https://github.com/python/cpython/issues/92619

   (164) https://github.com/python/cpython/issues/88750

   (165) https://github.com/python/cpython/issues/92261

   (166) https://github.com/python/cpython/issues/91432

   (167) https://github.com/python/cpython/issues/91399

   (168) https://github.com/python/cpython/issues/91578

   (169) https://bugs.python.org/issue?@action=redirect&bpo=47091

   (170) https://bugs.python.org/issue?@action=redirect&bpo=46142

   (171) https://bugs.python.org/issue?@action=redirect&bpo=42316


File: python.info,  Node: Library<20>,  Next: Documentation<15>,  Prev: Core and Builtins<21>,  Up: Python 3 12 0 alpha 1

1.23.21.3 Library
.................

   - gh-89237(1): Fix hang on Windows in ‘subprocess.wait_closed()’ in
     *note asyncio: 8. with *note ProactorEventLoop: 5ae.  Patch by
     Kumar Aditya.

   - gh-97928(2): ‘tkinter.Text.count()’ raises now an exception for
     options starting with "-" instead of silently ignoring them.

   - gh-98393(3): The *note os: 91. module no longer accepts bytes-like
     paths, like *note bytearray: 4e3. and *note memoryview: 40f. types:
     only the exact *note bytes: 1a5. type is accepted for bytes
     strings.  Patch by Victor Stinner.

   - gh-98363(4): Added itertools.batched() to batch data into lists of
     a given length with the last list possibly being shorter than the
     others.

   - gh-98331(5): Update the bundled copies of pip and setuptools to
     versions 22.3 and 65.5.0 respectively.

   - gh-98307(6): A *note createSocket(): 601. method was added to *note
     SysLogHandler: 602.

   - gh-96035(7): Fix bug in *note urllib.parse.urlparse(): 2df. that
     causes certain port numbers containing whitespace, underscores,
     plus and minus signs, or non-ASCII digits to be incorrectly
     accepted.

   - gh-98257(8): Make *note sys.setprofile(): 146d. and *note
     sys.settrace(): 146e. functions reentrant.  They can no long fail
     with: ‘RuntimeError("Cannot install a trace function while another
     trace function is being installed")’.  Patch by Victor Stinner.

   - gh-98251(9): Allow *note venv: f9. to pass along ‘PYTHON*’
     variables to ‘ensurepip’ and ‘pip’ when they do not impact path
     resolution

   - gh-94597(10): Deprecated *note
     asyncio.AbstractEventLoopPolicy.get_child_watcher(): 2a2. and *note
     asyncio.AbstractEventLoopPolicy.set_child_watcher(): 2a1. methods
     to be removed in Python 3.14.  Patch by Kumar Aditya.

   - gh-98178(11): On macOS, fix a crash in *note syslog.syslog(): 4e6.
     in multi-threaded applications.  On macOS, the libc ‘syslog()’
     function is not thread-safe, so *note syslog.syslog(): 4e6. no
     longer releases the GIL to call it.  Patch by Victor Stinner.

   - gh-44098(12): Release the GIL when creating *note mmap.mmap: 1f0.
     objects on Unix.

   - gh-87730(13): Wrap network errors consistently in urllib FTP
     support, so the test suite doesn't fail when a network is available
     but the public internet is not reachable.

   - gh-94597(14): The child watcher classes *note
     MultiLoopChildWatcher: 29b, *note FastChildWatcher: 29c. and *note
     SafeChildWatcher: 29e. are deprecated and will be removed in Python
     3.14.  Patch by Kumar Aditya.

   - gh-98023(15): Change default child watcher to *note
     PidfdChildWatcher: 420. on Linux systems which supports it.  Patch
     by Kumar Aditya.

   - gh-90985(16): Earlier in 3.11 we deprecated
     ‘asyncio.Task.cancel("message")’.  We realized we were too harsh,
     and have undeprecated it.

   - gh-65961(17): Do not rely solely on ‘__cached__’ on modules; code
     will also support ‘__spec__.cached’.

   - gh-97646(18): Replace deprecated ‘application/javascript’ with
     ‘text/javascript’ in *note mimetypes: 82.  See RFC 9239(19).  Patch
     by Noam Cohen.

   - gh-97930(20): Apply changes from importlib_resources 5.8 and 5.9:
     ‘Traversable.joinpath’ provides a concrete implementation.
     ‘as_file’ now supports directories of resources.

   - gh-97850(21): Remove deprecated ‘importlib.util.set_loader()’ and
     ‘importlib.util.module_for_loader()’ from *note importlib.util: 71.

   - gh-97837(22): Change deprecate warning message in *note unittest:
     ef. from

     ‘It is deprecated to return a value!=None’

     to

     ‘It is deprecated to return a value that is not None from a test
     case’

   - gh-97825(23): Fixes *note AttributeError: 2f6. when *note
     subprocess.check_output(): f64. is used with argument ‘input=None’
     and either of the arguments 'encoding' or 'errors' are used.

   - gh-97008(24): *note NameError: 3e5. and *note AttributeError: 2f6.
     spelling suggestions provided since gh-82711(25) are now also
     emitted by the pure Python *note traceback: e7. module.  Tests for
     those suggestions now exercise both implementations to ensure they
     are equivalent.  Patch by Carl Friedrich Bolz-Tereick and Łukasz
     Langa.

   - gh-97799(26): ‘dataclass’ now uses *note inspect.get_annotations():
     7b7. to examine the annotations on class objects.

   - gh-97781(27): Removed deprecated interfaces in ‘importlib.metadata’
     (entry points accessed as dictionary, implicit dictionary
     construction of sequence of ‘EntryPoint’ objects, mutablility of
     ‘EntryPoints’ result, access of entry point by index).
     ‘entry_points’ now has a simpler, more straightforward API
     (returning ‘EntryPoints’).

   - gh-96827(28): Avoid spurious tracebacks from *note asyncio: 8. when
     default executor cleanup is delayed until after the event loop is
     closed (e.g.  as the result of a keyboard interrupt).

   - gh-95534(29): ‘gzip.GzipFile.read()’ reads 10% faster.

   - gh-97592(30): Avoid a crash in the C version of *note
     asyncio.Future.remove_done_callback(): 16c7. when an evil argument
     is passed.

   - gh-97639(31): Remove ‘tokenize.NL’ check from *note tabnanny: c7.

   - gh-97545(32): Make Semaphore run faster.

   - gh-73588(33): Fix generation of the default name of
     ‘tkinter.Checkbutton’.  Previously, checkbuttons in different
     parent widgets could have the same short name and share the same
     state if arguments "name" and "variable" are not specified.  Now
     they are globally unique.

   - gh-96865(34): fix Flag to use boundary CONFORM

     This restores previous Flag behavior of allowing flags with
     non-sequential values to be combined; e.g.

     class Skip(Flag): TWO = 2 EIGHT = 8

     Skip.TWO | Skip.EIGHT -> <Skip.TWO|EIGHT: 10>

   - gh-97005(35): Update bundled libexpat to 2.4.9

   - gh-85760(36): Fix race condition in *note asyncio: 8. where *note
     process_exited(): 16c8. called before the *note
     pipe_data_received(): 16c9. leading to inconsistent output.  Patch
     by Kumar Aditya.

   - gh-96704(37): Pass the correct ‘contextvars.Context’ when a
     ‘asyncio’ exception handler is called on behalf of a task or
     callback handle.  This adds a new ‘Task’ method, ‘get_context’, and
     also a new ‘Handle’ method with the same name.  If this method is
     not found on a task object (perhaps because it is a third-party
     library that does not yet provide this method), the context
     prevailing at the time the exception handler is called is used.

   - gh-96819(38): Fixed check in ‘multiprocessing.resource_tracker’
     that guarantees that the length of a write to a pipe is not greater
     than ‘PIPE_BUF’.

   - gh-95865(39): Reduce *note urllib.parse.quote_from_bytes(): 16ca.
     memory use on large values.

     Contributed by Dennis Sweeney.

   - gh-96741(40): Corrected type annotation for dataclass attribute
     ‘pstats.FunctionProfile.ncalls’ to be ‘str’.

   - gh-96734(41): Update *note unicodedata: ee. database to Unicode
     15.0.0.

   - gh-96735(42): Fix undefined behaviour in *note struct.unpack():
     16cb.

   - gh-46412(43): Improve performance of ‘bool(db)’ for large ndb/gdb
     databases.  Previously this would call ‘len(db)’ which would
     iterate over all keys - the answer (empty or not) is known after
     the first key.

   - gh-96652(44): Fix the faulthandler implementation of
     ‘faulthandler.register(signal, chain=True)’ if the ‘sigaction()’
     function is not available: don't call the previous signal handler
     if it's NULL. Patch by Victor Stinner.

   - gh-68163(45): Correct conversion of *note numbers.Rational: 1255.'s
     to *note float: 2c8.

   - gh-96538(46): Speed up ‘bisect.bisect()’ functions by taking
     advantage of type-stability.

   - gh-96465(47): Fraction hashes are now cached.

   - gh-96079(48): In *note typing: ed, fix missing field ‘name’ and
     incorrect ‘__module__’ in _AnnotatedAlias.

   - gh-96415(49): Remove ‘types._cell_factory’ from module namespace.

   - gh-95987(50): Fix ‘repr’ of ‘Any’ subclasses.

   - gh-96388(51): Work around missing socket functions in *note socket:
     d47.'s ‘__repr__’.

   - gh-96385(52): Fix ‘TypeVarTuple.__typing_prepare_subst__’.
     ‘TypeError’ was not raised when using more than one ‘TypeVarTuple’,
     like ‘[*T, *V]’ in type alias substitutions.

   - gh-96142(53): Add ‘match_args’, ‘kw_only’, ‘slots’, and
     ‘weakref_slot’ to ‘_DataclassParams’.

   - gh-96073(54): In *note inspect: 72, fix overeager replacement of
     "‘typing.’" in formatting annotations.

   - gh-89258(55): Added a *note getChildren(): 16cc. method to *note
     logging.Logger: af3, to get the immediate child loggers of a
     logger.

   - gh-96346(56): Use double caching for compiled RE patterns.

   - gh-96349(57): Fixed a minor performance regression in
     ‘threading.Event.__init__()’

   - gh-90467(58): Fix ‘asyncio.streams.StreamReaderProtocol’ to keep a
     strong reference to the created task, so that it's not garbage
     collected

   - gh-96172(59): Fix a bug in ‘unicodedata’: ‘east_asian_width’ used
     to return the wrong value for unassigned characters; and for yet
     unassigned, but reserved characters.

   - gh-96159(60): Fix a performance regression in logging
     TimedRotatingFileHandler.  Only check for special files when the
     rollover time has passed.

   - gh-96175(61): Fix unused ‘localName’ parameter in the ‘Attr’ class
     in *note xml.dom.minidom: 109.

   - gh-96145(62): Add AttrDict to JSON module for use with object_hook.

   - gh-96052(63): Fix handling compiler warnings (SyntaxWarning and
     DeprecationWarning) in *note codeop.compile_command(): 16cd. when
     checking for incomplete input.  Previously it emitted warnings and
     raised a SyntaxError.  Now it always returns ‘None’ for incomplete
     input without emitting any warnings.

   - gh-96125(64): Fix incorrect condition that causes
     ‘sys.thread_info.name’ to be wrong on pthread platforms.

   - gh-96019(65): Fix a bug in the ‘makeunicodedata.py’ script leading
     to about 13 KiB of space saving in the ‘unicodedata’ module,
     specifically the character decomposition data.

   - gh-95463(66): Remove an incompatible change from bpo-28080(67) that
     caused a regression that ignored the utf8 in ‘ZipInfo.flag_bits’.
     Patch by Pablo Galindo.

   - gh-69142(68): Add ‘%:z’ strftime format code (generates tzoffset
     with colons as separator), see *note strftime() 與 strptime()
     的行為: 16ce.

   - gh-95899(69): Fix *note asyncio.Runner: 5a5. to call *note
     asyncio.set_event_loop(): 16cf. only once to avoid calling *note
     attach_loop(): 16d0. multiple times on child watchers.  Patch by
     Kumar Aditya.

   - gh-95736(70): Fix *note unittest.IsolatedAsyncioTestCase: 2de. to
     set event loop before calling setup functions.  Patch by Kumar
     Aditya.

   - gh-95865(71): Speed up *note urllib.parse.quote_from_bytes(): 16ca.
     by replacing a list comprehension with ‘map()’.

   - gh-95861(72): Add support for computing Spearman's correlation
     coefficient to the existing statistics.correlation() function.

   - gh-95804(73): Fix ‘logging’ shutdown handler so it respects
     ‘MemoryHandler.flushOnClose’.

   - gh-95704(74): When a task catches *note asyncio.CancelledError:
     19e. and raises some other error, the other error should generally
     not silently be suppressed.

   - gh-95149(75): The *note HTTPStatus: 8a5. enum offers a couple of
     properties to indicate the HTTP status category e.g.
     ‘HTTPStatus.OK.is_success’.

   - gh-95609(76): Update bundled pip to 22.2.2.

   - gh-95289(77): Fix *note asyncio.TaskGroup: 19b. to propagate
     exception when *note asyncio.CancelledError: 19e. was replaced with
     another exception by a context manager.  Patch by Kumar Aditya and
     Guido van Rossum.

   - gh-94909(78): Fix incorrect joining of relative Windows paths with
     drives in *note pathlib.PurePath: 44e. initializer.

   - gh-95385(79): Faster ‘json.dumps()’ when sorting of keys is not
     requested (default).

   - gh-83901(80): Improve *note Signature.bind: 150d. error message for
     missing keyword-only arguments.

   - gh-95339(81): Update bundled pip to 22.2.1.

   - gh-95045(82): Fix GC crash when deallocating ‘_lsprof.Profiler’ by
     untracking it before calling any callbacks.  Patch by Kumar Aditya.

   - gh-95231(83): Fail gracefully if *note EPERM: 16d1. or *note
     ENOSYS: 16d2. is raised when loading ‘crypt’ methods.  This may
     happen when trying to load ‘MD5’ on a Linux kernel with FIPS
     (Federal Information Processing Standard) enabled.

   - gh-95097(84): Fix *note asyncio.run(): 423. for *note asyncio.Task:
     480. implementations without *note uncancel(): 1a1. method.  Patch
     by Kumar Aditya.

   - gh-95087(85): Fix IndexError in parsing invalid date in the *note
     email: 32. module.

   - gh-95199(86): Upgrade bundled setuptools to 63.2.0.

   - gh-95194(87): Upgrade bundled pip to 22.2.

   - gh-93899(88): Fix check for existence of *note os.EFD_CLOEXEC:
     16d3, *note os.EFD_NONBLOCK: 16d4. and *note os.EFD_SEMAPHORE:
     16d5. flags on older kernel versions where these flags are not
     present.  Patch by Kumar Aditya.

   - gh-95166(89): Fix *note concurrent.futures.Executor.map(): d8a. to
     cancel the currently waiting on future on an error - e.g.
     TimeoutError or KeyboardInterrupt.

   - gh-95132(90): Fix a *note sqlite3: ba. regression where ‘*args’ and
     ‘**kwds’ were incorrectly relayed from *note connect(): 288. to the
     *note Connection: 22a. factory.  The regression was introduced in
     3.11a1 with PR 24421 (gh-85128(91)).  Patch by Erlend E. Aasland.

   - gh-93157(92): Fix *note fileinput: 51. module didn't support
     ‘errors’ option when ‘inplace’ is true.

   - gh-91212(93): Fixed flickering of the turtle window when the tracer
     is turned off.  Patch by Shin-myoung-serp.

   - gh-95077(94): Add deprecation warning for enum ‘member.member’
     access (e.g.  ‘Color.RED.BLUE’).  Remove ‘EnumMeta.__getattr__’.

   - gh-95109(95): Ensure that timeouts scheduled with *note
     asyncio.Timeout: 15c5. that have already expired are delivered
     promptly.

   - gh-95105(96): ‘wsgiref.types.InputStream.__iter__()’ should return
     ‘Iterator[bytes]’, not ‘Iterable[bytes]’.  Patch by Shantanu Jain.

   - gh-95066(97): Replaced assert with exception in *note ast.parse():
     18e, when ‘feature_version’ has an invalid major version.  Patch by
     Shantanu Jain.

   - gh-77617(98): Add *note sqlite3: ba. *note command-line interface:
     3e7.  Patch by Erlend Aasland.

   - gh-95005(99): Replace _PyAccu with _PyUnicodeWriter in JSON encoder
     and StringIO and remove the _PyAccu implementation.

   - gh-90085(100): Remove ‘-c/--clock’ and ‘-t/--time’ CLI options of
     *note timeit: d8.  The options had been deprecated since Python 3.3
     and the functionality was removed in Python 3.7.  Patch by Shantanu
     Jain.

   - gh-94857(101): Fix refleak in ‘_io.TextIOWrapper.reconfigure’.
     Patch by Kumar Aditya.

   - gh-94821(102): Fix binding of unix socket to empty address on Linux
     to use an available address from the abstract namespace, instead of
     "0".

   - gh-94736(103): Fix crash when deallocating an instance of a
     subclass of ‘_multiprocessing.SemLock’.  Patch by Kumar Aditya.

   - gh-81620(104): Add random.binomialvariate().

   - gh-74116(105): Allow *note asyncio.StreamWriter.drain(): 16b1. to
     be awaited concurrently by multiple tasks.  Patch by Kumar Aditya.

   - gh-87822(106): When called with ‘capture_locals=True’, the *note
     traceback: e7. module functions swallow exceptions raised from
     calls to ‘repr()’ on local variables of frames.  This is in order
     to prioritize the original exception over rendering errors.  An
     indication of the failure is printed in place of the missing value.
     (Patch by Simon-Martin Schroeder).

   - gh-88050(107): Fix *note asyncio: 8. subprocess transport to kill
     process cleanly when process is blocked and avoid ‘RuntimeError’
     when loop is closed.  Patch by Kumar Aditya.

   - gh-94637(108): ‘SSLContext.set_default_verify_paths()’ now releases
     the GIL around ‘SSL_CTX_set_default_verify_paths’ call.  The
     function call performs I/O and CPU intensive work.

   - gh-94309(109): Deprecate aliases *note typing.Hashable: 49b. and
     *note typing.Sized: 49c.

   - gh-92546(110): An undocumented ‘python -m pprint’ benchmark is
     moved into ‘pprint’ suite of pyperformance.  Patch by Oleg Iarygin.

   - gh-94607(111): Fix subclassing complex generics with type variables
     in *note typing: ed.  Previously an error message saying ‘Some type
     variables ... are not listed in Generic[...]’ was shown.  *note
     typing: ed. no longer populates ‘__parameters__’ with the
     ‘__parameters__’ of a Python class.

   - gh-94619(112): Remove the long-deprecated ‘module_repr()’ from
     *note importlib: 6b.

   - gh-93910(113): The ability to access the other values of an enum on
     an enum (e.g.  ‘Color.RED.BLUE’) has been restored in order to fix
     a performance regression.

   - gh-93896(114): Fix *note asyncio.run(): 423. and *note
     unittest.IsolatedAsyncioTestCase: 2de. to always the set event loop
     as it was done in Python 3.10 and earlier.  Patch by Kumar Aditya.

   - gh-94343(115): Allow setting the attributes of ‘reprlib.Repr’
     during object initialization

   - gh-94382(116): Port static types of ‘_multiprocessing’ module to
     heap types.  Patch by Kumar Aditya.

   - gh-78724(117): Fix crash in *note struct.Struct: 15a9. when it was
     not completely initialized by initializing it in *note __new__():
     526.  Patch by Kumar Aditya.

   - gh-94510(118): Re-entrant calls to *note sys.setprofile(): 146d.
     and *note sys.settrace(): 146e. now raise *note RuntimeError: 179.
     Patch by Pablo Galindo.

   - gh-92336(119): Fix bug where *note linecache.getline(): dc9. fails
     on bad files with *note UnicodeDecodeError: 9b7. or *note
     SyntaxError: 173.  It now returns an empty string as per the
     documentation.

   - gh-94398(120): Once a *note asyncio.TaskGroup: 19b. has started
     shutting down (i.e., at least one task has failed and the task
     group has started cancelling the remaining tasks), it should not be
     possible to add new tasks to the task group.

   - gh-94383(121): ‘xml.etree’: Remove the ‘ElementTree.Element.copy()’
     method of the pure Python implementation, deprecated in Python
     3.10, use the *note copy.copy(): 4d8. function instead.  The C
     implementation of ‘xml.etree’ has no ‘copy()’ method, only a
     ‘__copy__()’ method.  Patch by Victor Stinner.

   - gh-94379(122): *note zipimport: 118.: Remove ‘find_loader()’ and
     ‘find_module()’ methods, deprecated in Python 3.10: use the
     ‘find_spec()’ method instead.  See PEP 451(123) for the rationale.
     Patch by Victor Stinner.

   - gh-94352(124): *note shlex.split(): 4e1.: Passing ‘None’ for 's'
     argument now raises an exception, rather than reading *note
     sys.stdin: 4e2.  The feature was deprecated in Python 3.9.  Patch
     by Victor Stinner.

   - gh-94318(125): Strip trailing spaces in *note pydoc: a3. text
     output.

   - gh-89988(126): Fix memory leak in *note pickle.Pickler: 9c2. when
     looking up ‘dispatch_table’.  Patch by Kumar Aditya.

   - gh-90016(127): Deprecate *note sqlite3: ba. *note default adapters
     and converters: 497.  Patch by Erlend E. Aasland.

   - gh-94254(128): Fixed types of *note struct: c0. module to be
     immutable.  Patch by Kumar Aditya.

   - gh-93259(129): Now raise ‘ValueError’ when ‘None’ or an empty
     string are passed to ‘Distribution.from_name’ (and other callers).

   - gh-74696(130): *note shutil.make_archive(): 45a. now passes the
     'root_dir' argument to custom archivers which support it.

   - gh-94216(131): The *note dis: 30. module now has the opcodes for
     pseudo instructions (those which are used by the compiler during
     code generation but then removed or replaced by real opcodes before
     the final bytecode is emitted).

   - gh-93096(132): Removed undocumented ‘python -m codecs’.  Use
     ‘python -m unittest test.test_codecs.EncodedFileTest’ instead.

   - gh-94207(133): Made ‘_struct.Struct’ GC-tracked in order to fix a
     reference leak in the ‘_struct’ module.

   - gh-93096(134): Removed undocumented ‘-t’ argument of ‘python -m
     base64’.  Use ‘python -m unittest
     test.test_base64.LegacyBase64TestCase.test_encodebytes’ instead.

   - gh-94226(135): Remove the ‘locale.format()’ function, deprecated in
     Python 3.7: use *note locale.format_string(): 4c3. instead.  Patch
     by Victor Stinner.

   - gh-94199(136): Remove the ‘ssl.match_hostname()’ function.  The
     ‘ssl.match_hostname()’ was deprecated in Python 3.7.  OpenSSL
     performs hostname matching since Python 3.7, Python no longer uses
     the ‘ssl.match_hostname()’ function.  Patch by Victor Stinner.

   - gh-94214(137): Document the ‘context’ object used in the
     ‘venv.EnvBuilder’ class, and add the new environment's library path
     to it.

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

   - gh-94199(140): Remove the ‘ssl.RAND_pseudo_bytes()’ function,
     deprecated in Python 3.6: use *note os.urandom(): 4c7. or *note
     ssl.RAND_bytes(): 4c8. instead.  Patch by Victor Stinner.

   - gh-94199(141): *note hashlib: 5e.: Remove the pure Python
     implementation of *note hashlib.pbkdf2_hmac(): 4b4, deprecated in
     Python 3.10.  Python 3.10 and newer requires OpenSSL 1.1.1 ( PEP
     644(142)): this OpenSSL version provides a C implementation of
     *note pbkdf2_hmac(): 4b4. which is faster.  Patch by Victor
     Stinner.

   - gh-94196(143): *note gzip: 5d.: Remove the ‘filename’ attribute of
     *note gzip.GzipFile: 354, deprecated since Python 2.6, use the
     *note name: 4b2. attribute instead.  In write mode, the ‘filename’
     attribute added ‘'.gz'’ file extension if it was not present.
     Patch by Victor Stinner.

   - gh-94182(144): run the *note asyncio.PidfdChildWatcher: 420. on the
     running loop, this allows event loops to run subprocesses when
     there is no default event loop running on the main thread

   - gh-94169(145): Remove ‘io.OpenWrapper’ and ‘_pyio.OpenWrapper’,
     deprecated in Python 3.10: just use *note open(): 4c0. instead.
     The *note open(): 4c0. (*note io.open(): 4c1.) function is a
     built-in function.  Since Python 3.10, ‘_pyio.open()’ is also a
     static method.  Patch by Victor Stinner.

   - gh-91742(146): Fix *note pdb: 94. crash after jump caused by a null
     pointer dereference.  Patch by Kumar Aditya.

   - gh-94101(147): Manual instantiation of *note ssl.SSLSession: c84.
     objects is no longer allowed as it lead to misconfigured instances
     that crashed the interpreter when attributes where accessed on
     them.

   - gh-84753(148): *note inspect.iscoroutinefunction(): 439, *note
     inspect.isgeneratorfunction(): 16d6, and *note
     inspect.isasyncgenfunction(): 16d7. now properly return ‘True’ for
     duck-typed function-like objects like instances of *note
     unittest.mock.AsyncMock: 9ee.

     This makes *note inspect.iscoroutinefunction(): 439. consistent
     with the behavior of ‘asyncio.iscoroutinefunction()’.  Patch by
     Mehdi ABAAKOUK.

   - gh-94028(149): Fix a regression in the *note sqlite3: ba. where
     statement objects were not properly cleared and reset after use in
     cursor iters.  The regression was introduced by PR 27884 in Python
     3.11a1.  Patch by Erlend E. Aasland.

   - gh-93973(150): Add keyword argument ‘all_errors’ to
     ‘asyncio.create_connection’ so that multiple connection errors can
     be raised as an ‘ExceptionGroup’.

   - gh-93963(151): Officially deprecate from ‘importlib.abc’ classes
     moved to ‘importlib.resources.abc’.

   - gh-93858(152): Prevent error when activating venv in nested fish
     instances.

   - gh-93820(153): Pickle *note enum.Flag: 5c9. by name.

   - gh-93847(154): Fix repr of enum of generic aliases.

   - gh-91404(155): Revert the *note re: a7. memory leak when a match is
     terminated by a signal or memory allocation failure as the
     implemented fix caused a major performance regression.

   - gh-83499(156): Fix double closing of file description in *note
     tempfile: c9.

   - gh-93820(157): Fixed a regression when *note copy.copy(): 4d8.-ing
     *note enum.Flag: 5c9. with multiple flag members.

   - gh-79512(158): Fixed names and ‘__module__’ value of *note weakref:
     fc. classes *note ReferenceType: 16d8, *note ProxyType: 16d9, *note
     CallableProxyType: 16da.  It makes them pickleable.

   - gh-91389(159): Fix an issue where *note dis: 30. utilities could
     report missing or incorrect position information in the presence of
     ‘CACHE’ entries.

   - gh-93626(160): Set ‘__future__.annotations’ to have a ‘None’
     mandatoryRelease to indicate that it is currently 'TBD'.

   - gh-90473(161): Emscripten and WASI have no home directory and
     cannot provide PEP 370(162) user site directory.

   - gh-90494(163): *note copy.copy(): 4d8. and *note copy.deepcopy():
     b12. now always raise a TypeError if ‘__reduce__()’ returns a tuple
     with length 6 instead of silently ignore the 6th item or produce
     incorrect result.

   - gh-90549(164): Fix a multiprocessing bug where a global named
     resource (such as a semaphore) could leak when a child process is
     spawned (as opposed to forked).

   - gh-93521(165): Fixed a case where dataclasses would try to add
     ‘__weakref__’ into the ‘__slots__’ for a dataclass that specified
     ‘weakref_slot=True’ when it was already defined in one of its
     bases.  This resulted in a ‘TypeError’ upon the new class being
     created.

   - gh-79579(166): *note sqlite3: ba. now correctly detects DML queries
     with leading comments.  Patch by Erlend E. Aasland.

   - gh-93421(167): Update *note sqlite3.Cursor.rowcount: 16db. when a
     DML statement has run to completion.  This fixes the row count for
     SQL queries like ‘UPDATE ... RETURNING’.  Patch by Erlend E.
     Aasland.

   - gh-93475(168): Expose ‘FICLONE’ and ‘FICLONERANGE’ constants in
     *note fcntl: 4f.  Patch by Illia Volochii.

   - gh-93370(169): Deprecate *note sqlite3.version: 2b1. and *note
     sqlite3.version_info: 2b2.

   - gh-91810(170): Suppress writing an XML declaration in open files in
     ‘ElementTree.write()’ with ‘encoding='unicode'’ and
     ‘xml_declaration=None’.

   - gh-91162(171): Support splitting of unpacked arbitrary-length tuple
     over ‘TypeVar’ and ‘TypeVarTuple’ parameters.  For example:

        * ‘A[T, *Ts][*tuple[int, ...]]’ -> ‘A[int, *tuple[int, ...]]’

        * ‘A[*Ts, T][*tuple[int, ...]]’ -> ‘A[*tuple[int, ...], int]’

   - gh-93353(172): Fix the *note importlib.resources.as_file(): 434.
     context manager to remove the temporary file if destroyed late
     during Python finalization: keep a local reference to the *note
     os.remove(): 1089. function.  Patch by Victor Stinner.

   - gh-83658(173): Make ‘multiprocessing.Pool’ raise an exception if
     ‘maxtasksperchild’ is not ‘None’ or a positive int.

   - gh-93312(174): Add *note os.PIDFD_NONBLOCK: 442. flag to open a
     file descriptor for a process with *note os.pidfd_open(): 421. in
     non-blocking mode.  Patch by Kumar Aditya.

   - gh-88123(175): Implement ‘Enum.__contains__’ that returns ‘True’ or
     ‘False’ to replace the deprecated behaviour that would sometimes
     raise a *note TypeError: 4dd.

   - gh-93297(176): Make asyncio task groups prevent child tasks from
     being GCed

   - gh-85308(177): Changed *note argparse.ArgumentParser: 4de. to use
     *note filesystem encoding and error handler: 4e0. instead of
     default text encoding to read arguments from file (e.g.
     ‘fromfile_prefix_chars’ option).  This change affects Windows;
     argument file should be encoded with UTF-8 instead of ANSI
     Codepage.

   - gh-93156(178): Accessing the *note pathlib.PurePath.parents: 7c4.
     sequence of an absolute path using negative index values produced
     incorrect results.

   - gh-93162(179): Add the ability for *note
     logging.config.dictConfig(): 1147. to usefully configure *note
     QueueHandler: 16dc. and *note QueueListener: dd2. as a pair, and
     add *note logging.getHandlerByName(): 16dd. and *note
     logging.getHandlerNames(): 15fa. APIs to allow access to handlers
     by name.

   - gh-93243(180): The ‘smtpd’ module was removed per the schedule in
     PEP 594(181).

   - gh-92886(182): Replace ‘assert’ statements with ‘raise
     AssertionError()’ in ‘BaseHandler’ so that the tested behaviour is
     maintained running with optimizations ‘(-O)’.

   - gh-90155(183): Fix broken *note asyncio.Semaphore: a17. when
     acquire is cancelled.

   - gh-90817(184): The ‘locale.resetlocale()’ function is deprecated
     and will be removed in Python 3.13.  Use
     ‘locale.setlocale(locale.LC_ALL, "")’ instead.  Patch by Victor
     Stinner.

   - gh-91513(185): Added ‘taskName’ attribute to *note logging: 7b.
     module for use with *note asyncio: 8. tasks.

   - gh-74696(186): *note shutil.make_archive(): 45a. no longer
     temporarily changes the current working directory during creation
     of standard ‘.zip’ or tar archives.

   - gh-92728(187): The ‘re.template()’ function and the corresponding
     ‘re.TEMPLATE’ and ‘re.T’ flags are restored after they were removed
     in 3.11.0b1, but they are now deprecated, so they might be removed
     from Python 3.13.

   - gh-93033(188): Search in some strings (platform dependent i.e
     [U+0xFFFF, U+0x0100] on Windows or [U+0xFFFFFFFF, U+0x00010000] on
     Linux 64-bit) are now up to 10 times faster.

   - gh-89973(189): Fix ‘re.error’ raised in *note fnmatch: 52. if the
     pattern contains a character range with upper bound lower than
     lower bound (e.g.  ‘[c-a]’).  Now such ranges are interpreted as
     empty ranges.

   - gh-93044(190): No longer convert the database argument of *note
     sqlite3.connect(): 288. to bytes before passing it to the factory.

   - gh-93010(191): In a very special case, the email package tried to
     append the nonexistent ‘InvalidHeaderError’ to the defect list.  It
     should have been ‘InvalidHeaderDefect’.

   - gh-92986(192): Fix *note ast.unparse(): 88a. when
     ‘ImportFrom.level’ is ‘None’

   - gh-92932(193): Now *note dis(): ad8. and *note get_instructions():
     1bc. handle operand values for instructions prefixed by
     ‘EXTENDED_ARG_QUICK’.  Patch by Sam Gross and Donghee Na.

   - gh-92675(194): Fix ‘venv.ensure_directories()’ to accept *note
     pathlib.Path: 20e. arguments in addition to *note str: 3f2. paths.
     Patch by David Foster.

   - gh-87901(195): Removed the ‘encoding’ argument from *note
     os.popen(): a2a. that was added in 3.11b1.

   - gh-91922(196): Fix function ‘sqlite.connect()’ and the
     ‘sqlite.Connection’ constructor on non-UTF-8 locales.  Also, they
     now support bytes paths non-decodable with the current FS encoding.

   - gh-92869(197): Added *note c_time_t: 16de. to *note ctypes: 22,
     which has the same size as the ‘time_t’ type in C.

   - gh-92839(198): Fixed crash resulting from calling bisect.insort()
     or bisect.insort_left() with the key argument not equal to ‘None’.

   - gh-90473(199): *note subprocess: c1. now fails early on Emscripten
     and WASI platforms to work around missing *note os.pipe(): 16df. on
     WASI.

   - gh-89325(200): Removed many old deprecated *note unittest: ef.
     features: *note TestCase: 3f4. method aliases, undocumented and
     broken *note TestCase: 3f4. method ‘assertDictContainsSubset’,
     undocumented *note TestLoader.loadTestsFromModule: 271. parameter
     'use_load_tests', and an underscored alias of the *note
     TextTestResult: 4d5. class.

   - gh-92734(201): Allow multi-element reprs emitted by *note reprlib:
     a9. to be pretty-printed using configurable indentation.

   - gh-92671(202): Fixed *note ast.unparse(): 88a. for empty tuples in
     the assignment target context.

   - gh-91581(203): *note utcfromtimestamp(): 2ce. no longer attempts to
     resolve ‘fold’ in the pure Python implementation, since the fold is
     never 1 in UTC. In addition to being slightly faster in the common
     case, this also prevents some errors when the timestamp is close to
     *note datetime.min: 16e0.  Patch by Paul Ganssle.

   - gh-86388(204): Removed 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-integral values such as randrange(10.5) or
     randrange('10') has been changed from ValueError to TypeError.

   - gh-90385(205): Add *note pathlib.Path.walk(): 450. as an
     alternative to *note os.walk(): 451.

   - gh-92550(206): Fix *note pathlib.Path.rglob(): 213. for empty
     pattern.

   - gh-92591(207): Allow *note logging: 7b. filters to return a *note
     logging.LogRecord: f89. instance so that filters attached to *note
     logging.Handler: 13ff.s can enrich records without side effects on
     other handlers.

   - gh-92445(208): Fix a bug in *note argparse: 5. where ‘nargs="*"’
     would raise an error instead of returning an empty list when 0
     arguments were supplied if choice was also defined in
     ‘parser.add_argument’.

   - gh-92547(209): Remove undocumented *note sqlite3: ba. features
     deprecated in Python 3.10:

        * ‘sqlite3.enable_shared_cache()’

        * ‘sqlite3.OptimizedUnicode’

     Patch by Erlend E. Aasland.

   - gh-92530(210): Fix an issue that occurred after interrupting *note
     threading.Condition.notify(): 16e1.

   - gh-92531(211): The statistics.median_grouped() function now always
     return a float.  Formerly, it did not convert the input type when
     for sequences of length one.

   - gh-84131(212): The *note pathlib.Path: 20e. deprecated method
     ‘link_to’ has been removed.  Use 3.10's *note hardlink_to(): 7c5.
     method instead as its semantics are consistent with that of *note
     symlink_to(): 7c6.

   - gh-89336(213): Removed *note configparser: 1b. module APIs: the
     ‘SafeConfigParser’ class alias, the ‘ParsingError.filename’
     property and parameter, and the ‘ConfigParser.readfp’ method, all
     of which were deprecated since Python 3.2.

   - gh-92391(214): Add *note __class_getitem__(): 6df. to *note
     csv.DictReader: 989. and *note csv.DictWriter: 1196, allowing them
     to be parameterized at runtime.  Patch by Marc Mueller.

   - gh-91968(215): Add ‘SO_RTABLE’ and ‘SO_USER_COOKIE’ constants to
     *note socket: b8.

   - gh-91810(216): *note ElementTree: 8f2. method *note write(): f98.
     and function *note tostring(): f96. now use the text file's
     encoding ("UTF-8" if not available) instead of locale encoding in
     XML declaration when ‘encoding="unicode"’ is specified.

   - gh-81790(217): *note os.path.splitdrive(): b9b. now understands DOS
     device paths with UNC links (beginning ‘\\?\UNC\’).  Contributed by
     Barney Gale.

   - gh-91760(218): Apply more strict rules 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.

   - gh-90622(219): Worker processes for *note
     concurrent.futures.ProcessPoolExecutor: 893. are no longer spawned
     on demand (a feature added in 3.9) when the multiprocessing context
     start method is ‘"fork"’ as that can lead to deadlocks in the child
     processes due to a fork happening while threads are running.

   - gh-91577(220): Move imports in ‘SharedMemory’ methods to module
     level so that they can be executed late in python finalization.

   - gh-91581(221): Remove an unhandled error case in the C
     implementation of calls to *note datetime.fromtimestamp: 495. with
     no time zone (i.e.  getting a local time from an epoch timestamp).
     This should have no user-facing effect other than giving a possibly
     more accurate error message when called with timestamps that fall
     on 10000-01-01 in the local time.  Patch by Paul Ganssle.

   - gh-91539(222): Improve performance of
     ‘urllib.request.getproxies_environment’ when there are many
     environment variables

   - gh-91524(223): Speed up the regular expression substitution
     (functions *note re.sub(): 283. and *note re.subn(): 284. and
     corresponding *note re.Pattern: 16e2. methods) for replacement
     strings containing group references by 2-3 times.

   - gh-91447(224): Fix findtext in the xml module to only give an empty
     string when the text attribute is set to ‘None’.

   - gh-91456(225): Deprecate current default auto() behavior: In 3.13
     the default will be for for auto() to always return the largest
     member value incremented by 1, and to raise if incompatible value
     types are used.

   - bpo-47231(226): Fixed an issue with inconsistent trailing slashes
     in tarfile longname directories.

   - bpo-39064(227): *note zipfile.ZipFile: 669. now raises *note
     zipfile.BadZipFile: 16e3. instead of ‘ValueError’ when reading a
     corrupt zip file in which the central directory offset is negative.

   - bpo-41287(228): Fix handling of the ‘doc’ argument in subclasses of
     *note property(): 180.

   - gh-90005(229): *note ctypes: 22. dependency ‘libffi’ is now
     detected with ‘pkg-config’.

   - bpo-32547(230): The constructors for *note DictWriter: 1196. and
     *note DictReader: 989. now coerce the ‘fieldnames’ argument to a
     *note list: 5b6. if it is an iterator.

   - bpo-35540(231): Fix *note dataclasses.asdict(): 1622. crash when
     *note collections.defaultdict: 1155. is present in the attributes.

   - bpo-47063(232): Add an index_pages parameter to support using
     non-default index page names.

   - bpo-47025(233): Drop support for *note bytes: 1a5. on *note
     sys.path: 37f.

   - bpo-46951(234): Order the contents of zipapp archives, to make
     builds more reproducible.

   - bpo-42777(235): Implement *note pathlib.Path.is_mount(): 9bb. for
     Windows paths.

   - bpo-46755(236): In ‘QueueHandler’, clear ‘stack_info’ from
     ‘LogRecord’ to prevent stack trace from being written twice.

   - bpo-45393(237): Fix the formatting for ‘await x’ and ‘not x’ in the
     operator precedence table when using the *note help(): 87c. system.

   - bpo-46642(238): Improve error message when trying to subclass an
     instance of *note typing.TypeVar: 141, *note typing.ParamSpec: 142,
     *note typing.TypeVarTuple: 143, etc.  Based on patch by Gregory
     Beauregard.

   - bpo-46364(239): Restrict use of sockets instead of pipes for stdin
     of subprocesses created by *note asyncio: 8. to AIX platform only.

   - bpo-28249(240): Set *note doctest.DocTest.lineno: 16e4. to ‘None’
     when object does not have ‘__doc__’.

   - bpo-46197(241): Fix *note ensurepip: 4b. environment isolation for
     subprocess running ‘pip’.

   - bpo-45924(242): Fix *note asyncio: 8. incorrect traceback when
     future's exception is raised multiple times.  Patch by Kumar
     Aditya.

   - bpo-45046(243): Add support of context managers in *note unittest:
     ef.: methods *note enterContext(): 65e. and *note
     enterClassContext(): 65f. of class *note TestCase: 3f4, method
     *note enterAsyncContext(): 660. of class *note
     IsolatedAsyncioTestCase: 2de. and function *note
     unittest.enterModuleContext(): 661.

   - bpo-44173(244): Enable fast seeking of uncompressed unencrypted
     ‘zipfile.ZipExtFile’

   - bpo-42627(245): Fix incorrect parsing of Windows registry proxy
     settings

   - bpo-42047(246): Add *note threading.get_native_id(): 9e1. support
     for DragonFly BSD. Patch by David Carlier.

   - bpo-14243(247): The *note tempfile.NamedTemporaryFile: 46d.
     function has a new optional parameter 'delete_on_close'

   - bpo-41246(248): Give the same callback function for when the
     overlapped operation is done to the functions ‘recv’, ‘recv_into’,
     ‘recvfrom’, ‘sendto’, ‘send’ and ‘sendfile’ inside ‘IocpProactor’.

   - bpo-39264(249): Fixed ‘collections.UserDict.get()’ to not call
     ‘__missing__()’ when a value is not found.  This matches the
     behavior of *note dict: 23b.  Patch by Bar Harel.

   - bpo-38693(250): *note importlib: 6b. now uses f-strings internally
     instead of ‘str.format’.

   - bpo-38267(251): Add 'timeout' parameter to *note
     asyncio.loop.shutdown_default_executor(): 88c.  The default value
     is ‘None’, which means the executor will be given an unlimited
     amount of time.  When called from *note asyncio.Runner: 5a5. or
     *note asyncio.run(): 423, the default timeout is 5 minutes.

   - bpo-34828(252): *note sqlite3.Connection.iterdump(): 22c. now
     handles databases that use ‘AUTOINCREMENT’ in one or more tables.

   - bpo-32990(253): Support reading wave files with the
     ‘WAVE_FORMAT_EXTENSIBLE’ format in the *note wave: fb. module.

   - bpo-26253(254): Allow adjustable compression level for tarfile
     streams in *note tarfile.open(): e19.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/89237

   (2) https://github.com/python/cpython/issues/97928

   (3) https://github.com/python/cpython/issues/98393

   (4) https://github.com/python/cpython/issues/98363

   (5) https://github.com/python/cpython/issues/98331

   (6) https://github.com/python/cpython/issues/98307

   (7) https://github.com/python/cpython/issues/96035

   (8) https://github.com/python/cpython/issues/98257

   (9) https://github.com/python/cpython/issues/98251

   (10) https://github.com/python/cpython/issues/94597

   (11) https://github.com/python/cpython/issues/98178

   (12) https://github.com/python/cpython/issues/44098

   (13) https://github.com/python/cpython/issues/87730

   (14) https://github.com/python/cpython/issues/94597

   (15) https://github.com/python/cpython/issues/98023

   (16) https://github.com/python/cpython/issues/90985

   (17) https://github.com/python/cpython/issues/65961

   (18) https://github.com/python/cpython/issues/97646

   (19) https://datatracker.ietf.org/doc/html/rfc9239.html

   (20) https://github.com/python/cpython/issues/97930

   (21) https://github.com/python/cpython/issues/97850

   (22) https://github.com/python/cpython/issues/97837

   (23) https://github.com/python/cpython/issues/97825

   (24) https://github.com/python/cpython/issues/97008

   (25) https://github.com/python/cpython/issues/82711

   (26) https://github.com/python/cpython/issues/97799

   (27) https://github.com/python/cpython/issues/97781

   (28) https://github.com/python/cpython/issues/96827

   (29) https://github.com/python/cpython/issues/95534

   (30) https://github.com/python/cpython/issues/97592

   (31) https://github.com/python/cpython/issues/97639

   (32) https://github.com/python/cpython/issues/97545

   (33) https://github.com/python/cpython/issues/73588

   (34) https://github.com/python/cpython/issues/96865

   (35) https://github.com/python/cpython/issues/97005

   (36) https://github.com/python/cpython/issues/85760

   (37) https://github.com/python/cpython/issues/96704

   (38) https://github.com/python/cpython/issues/96819

   (39) https://github.com/python/cpython/issues/95865

   (40) https://github.com/python/cpython/issues/96741

   (41) https://github.com/python/cpython/issues/96734

   (42) https://github.com/python/cpython/issues/96735

   (43) https://github.com/python/cpython/issues/46412

   (44) https://github.com/python/cpython/issues/96652

   (45) https://github.com/python/cpython/issues/68163

   (46) https://github.com/python/cpython/issues/96538

   (47) https://github.com/python/cpython/issues/96465

   (48) https://github.com/python/cpython/issues/96079

   (49) https://github.com/python/cpython/issues/96415

   (50) https://github.com/python/cpython/issues/95987

   (51) https://github.com/python/cpython/issues/96388

   (52) https://github.com/python/cpython/issues/96385

   (53) https://github.com/python/cpython/issues/96142

   (54) https://github.com/python/cpython/issues/96073

   (55) https://github.com/python/cpython/issues/89258

   (56) https://github.com/python/cpython/issues/96346

   (57) https://github.com/python/cpython/issues/96349

   (58) https://github.com/python/cpython/issues/90467

   (59) https://github.com/python/cpython/issues/96172

   (60) https://github.com/python/cpython/issues/96159

   (61) https://github.com/python/cpython/issues/96175

   (62) https://github.com/python/cpython/issues/96145

   (63) https://github.com/python/cpython/issues/96052

   (64) https://github.com/python/cpython/issues/96125

   (65) https://github.com/python/cpython/issues/96019

   (66) https://github.com/python/cpython/issues/95463

   (67) https://bugs.python.org/issue?@action=redirect&bpo=28080

   (68) https://github.com/python/cpython/issues/69142

   (69) https://github.com/python/cpython/issues/95899

   (70) https://github.com/python/cpython/issues/95736

   (71) https://github.com/python/cpython/issues/95865

   (72) https://github.com/python/cpython/issues/95861

   (73) https://github.com/python/cpython/issues/95804

   (74) https://github.com/python/cpython/issues/95704

   (75) https://github.com/python/cpython/issues/95149

   (76) https://github.com/python/cpython/issues/95609

   (77) https://github.com/python/cpython/issues/95289

   (78) https://github.com/python/cpython/issues/94909

   (79) https://github.com/python/cpython/issues/95385

   (80) https://github.com/python/cpython/issues/83901

   (81) https://github.com/python/cpython/issues/95339

   (82) https://github.com/python/cpython/issues/95045

   (83) https://github.com/python/cpython/issues/95231

   (84) https://github.com/python/cpython/issues/95097

   (85) https://github.com/python/cpython/issues/95087

   (86) https://github.com/python/cpython/issues/95199

   (87) https://github.com/python/cpython/issues/95194

   (88) https://github.com/python/cpython/issues/93899

   (89) https://github.com/python/cpython/issues/95166

   (90) https://github.com/python/cpython/issues/95132

   (91) https://github.com/python/cpython/issues/85128

   (92) https://github.com/python/cpython/issues/93157

   (93) https://github.com/python/cpython/issues/91212

   (94) https://github.com/python/cpython/issues/95077

   (95) https://github.com/python/cpython/issues/95109

   (96) https://github.com/python/cpython/issues/95105

   (97) https://github.com/python/cpython/issues/95066

   (98) https://github.com/python/cpython/issues/77617

   (99) https://github.com/python/cpython/issues/95005

   (100) https://github.com/python/cpython/issues/90085

   (101) https://github.com/python/cpython/issues/94857

   (102) https://github.com/python/cpython/issues/94821

   (103) https://github.com/python/cpython/issues/94736

   (104) https://github.com/python/cpython/issues/81620

   (105) https://github.com/python/cpython/issues/74116

   (106) https://github.com/python/cpython/issues/87822

   (107) https://github.com/python/cpython/issues/88050

   (108) https://github.com/python/cpython/issues/94637

   (109) https://github.com/python/cpython/issues/94309

   (110) https://github.com/python/cpython/issues/92546

   (111) https://github.com/python/cpython/issues/94607

   (112) https://github.com/python/cpython/issues/94619

   (113) https://github.com/python/cpython/issues/93910

   (114) https://github.com/python/cpython/issues/93896

   (115) https://github.com/python/cpython/issues/94343

   (116) https://github.com/python/cpython/issues/94382

   (117) https://github.com/python/cpython/issues/78724

   (118) https://github.com/python/cpython/issues/94510

   (119) https://github.com/python/cpython/issues/92336

   (120) https://github.com/python/cpython/issues/94398

   (121) https://github.com/python/cpython/issues/94383

   (122) https://github.com/python/cpython/issues/94379

   (123) https://peps.python.org/pep-0451/

   (124) https://github.com/python/cpython/issues/94352

   (125) https://github.com/python/cpython/issues/94318

   (126) https://github.com/python/cpython/issues/89988

   (127) https://github.com/python/cpython/issues/90016

   (128) https://github.com/python/cpython/issues/94254

   (129) https://github.com/python/cpython/issues/93259

   (130) https://github.com/python/cpython/issues/74696

   (131) https://github.com/python/cpython/issues/94216

   (132) https://github.com/python/cpython/issues/93096

   (133) https://github.com/python/cpython/issues/94207

   (134) https://github.com/python/cpython/issues/93096

   (135) https://github.com/python/cpython/issues/94226

   (136) https://github.com/python/cpython/issues/94199

   (137) https://github.com/python/cpython/issues/94214

   (138) https://github.com/python/cpython/issues/94199

   (139) https://cwe.mitre.org/data/definitions/295.html

   (140) https://github.com/python/cpython/issues/94199

   (141) https://github.com/python/cpython/issues/94199

   (142) https://peps.python.org/pep-0644/

   (143) https://github.com/python/cpython/issues/94196

   (144) https://github.com/python/cpython/issues/94182

   (145) https://github.com/python/cpython/issues/94169

   (146) https://github.com/python/cpython/issues/91742

   (147) https://github.com/python/cpython/issues/94101

   (148) https://github.com/python/cpython/issues/84753

   (149) https://github.com/python/cpython/issues/94028

   (150) https://github.com/python/cpython/issues/93973

   (151) https://github.com/python/cpython/issues/93963

   (152) https://github.com/python/cpython/issues/93858

   (153) https://github.com/python/cpython/issues/93820

   (154) https://github.com/python/cpython/issues/93847

   (155) https://github.com/python/cpython/issues/91404

   (156) https://github.com/python/cpython/issues/83499

   (157) https://github.com/python/cpython/issues/93820

   (158) https://github.com/python/cpython/issues/79512

   (159) https://github.com/python/cpython/issues/91389

   (160) https://github.com/python/cpython/issues/93626

   (161) https://github.com/python/cpython/issues/90473

   (162) https://peps.python.org/pep-0370/

   (163) https://github.com/python/cpython/issues/90494

   (164) https://github.com/python/cpython/issues/90549

   (165) https://github.com/python/cpython/issues/93521

   (166) https://github.com/python/cpython/issues/79579

   (167) https://github.com/python/cpython/issues/93421

   (168) https://github.com/python/cpython/issues/93475

   (169) https://github.com/python/cpython/issues/93370

   (170) https://github.com/python/cpython/issues/91810

   (171) https://github.com/python/cpython/issues/91162

   (172) https://github.com/python/cpython/issues/93353

   (173) https://github.com/python/cpython/issues/83658

   (174) https://github.com/python/cpython/issues/93312

   (175) https://github.com/python/cpython/issues/88123

   (176) https://github.com/python/cpython/issues/93297

   (177) https://github.com/python/cpython/issues/85308

   (178) https://github.com/python/cpython/issues/93156

   (179) https://github.com/python/cpython/issues/93162

   (180) https://github.com/python/cpython/issues/93243

   (181) https://peps.python.org/pep-0594/

   (182) https://github.com/python/cpython/issues/92886

   (183) https://github.com/python/cpython/issues/90155

   (184) https://github.com/python/cpython/issues/90817

   (185) https://github.com/python/cpython/issues/91513

   (186) https://github.com/python/cpython/issues/74696

   (187) https://github.com/python/cpython/issues/92728

   (188) https://github.com/python/cpython/issues/93033

   (189) https://github.com/python/cpython/issues/89973

   (190) https://github.com/python/cpython/issues/93044

   (191) https://github.com/python/cpython/issues/93010

   (192) https://github.com/python/cpython/issues/92986

   (193) https://github.com/python/cpython/issues/92932

   (194) https://github.com/python/cpython/issues/92675

   (195) https://github.com/python/cpython/issues/87901

   (196) https://github.com/python/cpython/issues/91922

   (197) https://github.com/python/cpython/issues/92869

   (198) https://github.com/python/cpython/issues/92839

   (199) https://github.com/python/cpython/issues/90473

   (200) https://github.com/python/cpython/issues/89325

   (201) https://github.com/python/cpython/issues/92734

   (202) https://github.com/python/cpython/issues/92671

   (203) https://github.com/python/cpython/issues/91581

   (204) https://github.com/python/cpython/issues/86388

   (205) https://github.com/python/cpython/issues/90385

   (206) https://github.com/python/cpython/issues/92550

   (207) https://github.com/python/cpython/issues/92591

   (208) https://github.com/python/cpython/issues/92445

   (209) https://github.com/python/cpython/issues/92547

   (210) https://github.com/python/cpython/issues/92530

   (211) https://github.com/python/cpython/issues/92531

   (212) https://github.com/python/cpython/issues/84131

   (213) https://github.com/python/cpython/issues/89336

   (214) https://github.com/python/cpython/issues/92391

   (215) https://github.com/python/cpython/issues/91968

   (216) https://github.com/python/cpython/issues/91810

   (217) https://github.com/python/cpython/issues/81790

   (218) https://github.com/python/cpython/issues/91760

   (219) https://github.com/python/cpython/issues/90622

   (220) https://github.com/python/cpython/issues/91577

   (221) https://github.com/python/cpython/issues/91581

   (222) https://github.com/python/cpython/issues/91539

   (223) https://github.com/python/cpython/issues/91524

   (224) https://github.com/python/cpython/issues/91447

   (225) https://github.com/python/cpython/issues/91456

   (226) https://bugs.python.org/issue?@action=redirect&bpo=47231

   (227) https://bugs.python.org/issue?@action=redirect&bpo=39064

   (228) https://bugs.python.org/issue?@action=redirect&bpo=41287

   (229) https://github.com/python/cpython/issues/90005

   (230) https://bugs.python.org/issue?@action=redirect&bpo=32547

   (231) https://bugs.python.org/issue?@action=redirect&bpo=35540

   (232) https://bugs.python.org/issue?@action=redirect&bpo=47063

   (233) https://bugs.python.org/issue?@action=redirect&bpo=47025

   (234) https://bugs.python.org/issue?@action=redirect&bpo=46951

   (235) https://bugs.python.org/issue?@action=redirect&bpo=42777

   (236) https://bugs.python.org/issue?@action=redirect&bpo=46755

   (237) https://bugs.python.org/issue?@action=redirect&bpo=45393

   (238) https://bugs.python.org/issue?@action=redirect&bpo=46642

   (239) https://bugs.python.org/issue?@action=redirect&bpo=46364

   (240) https://bugs.python.org/issue?@action=redirect&bpo=28249

   (241) https://bugs.python.org/issue?@action=redirect&bpo=46197

   (242) https://bugs.python.org/issue?@action=redirect&bpo=45924

   (243) https://bugs.python.org/issue?@action=redirect&bpo=45046

   (244) https://bugs.python.org/issue?@action=redirect&bpo=44173

   (245) https://bugs.python.org/issue?@action=redirect&bpo=42627

   (246) https://bugs.python.org/issue?@action=redirect&bpo=42047

   (247) https://bugs.python.org/issue?@action=redirect&bpo=14243

   (248) https://bugs.python.org/issue?@action=redirect&bpo=41246

   (249) https://bugs.python.org/issue?@action=redirect&bpo=39264

   (250) https://bugs.python.org/issue?@action=redirect&bpo=38693

   (251) https://bugs.python.org/issue?@action=redirect&bpo=38267

   (252) https://bugs.python.org/issue?@action=redirect&bpo=34828

   (253) https://bugs.python.org/issue?@action=redirect&bpo=32990

   (254) https://bugs.python.org/issue?@action=redirect&bpo=26253


File: python.info,  Node: Documentation<15>,  Next: Tests<18>,  Prev: Library<20>,  Up: Python 3 12 0 alpha 1

1.23.21.4 Documentation
.......................

   - gh-85525(1): Remove extra row

   - gh-86404(2): Deprecated tools ‘make suspicious’ and ‘rstlint.py’
     are now removed.  They have been replaced by sphinx-lint(3).

   - gh-97741(4): Fix ‘!’ in c domain ref target syntax via a ‘conf.py’
     patch, so it works as intended to disable ref target resolution.

   - gh-96432(5): Fraction literals now support whitespace around the
     forward slash, ‘Fraction('2 / 3')’.

   - gh-96098(6): Improve discoverability of the higher level
     concurrent.futures module by providing clearer links from the lower
     level threading and multiprocessing modules.

   - gh-95957(7): What's New 3.11 now has instructions for how to
     provide compiler and linker flags for Tcl/Tk and OpenSSL on RHEL 7
     and CentOS 7.

   - gh-95588(8): Clarified the conflicting advice given in the *note
     ast: 7. documentation about *note ast.literal_eval(): bbf. being
     "safe" for use on untrusted input while at the same time warning
     that it can crash the process.  The latter statement is true and is
     deemed unfixable without a large amount of work unsuitable for a
     bugfix.  So we keep the warning and no longer claim that
     ‘literal_eval’ is safe.

   - gh-91207(9): Fix stylesheet not working in Windows CHM htmlhelp
     docs and add warning that they are deprecated.  Contributed by
     C.A.M. Gerlach.

   - gh-95454(10): Replaced incorrectly written true/false values in
     documentation.  Patch by Robert O'Shea

   - gh-95451(11): Update library documentation with *note availability
     information: 16e6. on WebAssembly platforms ‘wasm32-emscripten’ and
     ‘wasm32-wasi’.

   - gh-95415(12): Use consistent syntax for platform availability.  The
     directive now supports a content body and emits a warning when it
     encounters an unknown platform.

   - gh-94321(13): Document the PEP 246(14) style protocol type *note
     sqlite3.PrepareProtocol: 16e7.

   - gh-86128(15): Document a limitation in ThreadPoolExecutor where its
     exit handler is executed before any handlers in atexit.

   - gh-61162(16): Clarify *note sqlite3: ba. behavior when *note How to
     use the connection context manager: 16e8.

   - gh-87260(17): Align *note sqlite3: ba. argument specs with the
     actual implementation.

   - gh-86986(18): The minimum Sphinx version required to build the
     documentation is now 3.2.

   - gh-88831(19): Augmented documentation of asyncio.create_task().
     Clarified the need to keep strong references to tasks and added a
     code snippet detailing how to do this.

   - gh-86438(20): Clarify that *note -W: 86c. and *note PYTHONWARNINGS:
     b51. are matched literally and case-insensitively, rather than as
     regular expressions, in *note warnings: fa.

   - gh-93031(21): Update tutorial introduction output to use 3.10+
     SyntaxError invalid range.

   - gh-92240(22): Added release dates for "What's New in Python 3.X"
     for 3.0, 3.1, 3.2, 3.8 and 3.10

   - bpo-47161(23): Document that *note pathlib.PurePath: 44e. does not
     collapse initial double slashes because they denote UNC paths.

   - bpo-40838(24): Document that *note inspect.getdoc(): 99e, *note
     inspect.getmodule(): 16e9, and *note inspect.getsourcefile(): 16ea.
     might return ‘None’.

   - bpo-43689(25): The ‘Differ’ documentation now also mentions other
     whitespace characters, which make it harder to understand the diff
     output.

   - bpo-38056(26): Overhaul the *note Error Handlers: 16eb.
     documentation in *note codecs: 14.

   - bpo-13553(27): Document tkinter.Tk args.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/85525

   (2) https://github.com/python/cpython/issues/86404

   (3) https://pypi.org/project/sphinx-lint/

   (4) https://github.com/python/cpython/issues/97741

   (5) https://github.com/python/cpython/issues/96432

   (6) https://github.com/python/cpython/issues/96098

   (7) https://github.com/python/cpython/issues/95957

   (8) https://github.com/python/cpython/issues/95588

   (9) https://github.com/python/cpython/issues/91207

   (10) https://github.com/python/cpython/issues/95454

   (11) https://github.com/python/cpython/issues/95451

   (12) https://github.com/python/cpython/issues/95415

   (13) https://github.com/python/cpython/issues/94321

   (14) https://peps.python.org/pep-0246/

   (15) https://github.com/python/cpython/issues/86128

   (16) https://github.com/python/cpython/issues/61162

   (17) https://github.com/python/cpython/issues/87260

   (18) https://github.com/python/cpython/issues/86986

   (19) https://github.com/python/cpython/issues/88831

   (20) https://github.com/python/cpython/issues/86438

   (21) https://github.com/python/cpython/issues/93031

   (22) https://github.com/python/cpython/issues/92240

   (23) https://bugs.python.org/issue?@action=redirect&bpo=47161

   (24) https://bugs.python.org/issue?@action=redirect&bpo=40838

   (25) https://bugs.python.org/issue?@action=redirect&bpo=43689

   (26) https://bugs.python.org/issue?@action=redirect&bpo=38056

   (27) https://bugs.python.org/issue?@action=redirect&bpo=13553


File: python.info,  Node: Tests<18>,  Next: Build<20>,  Prev: Documentation<15>,  Up: Python 3 12 0 alpha 1

1.23.21.5 Tests
...............

   - gh-95027(1): On Windows, when the Python test suite is run with the
     ‘-jN’ option, the ANSI code page is now used as the encoding for
     the stdout temporary file, rather than using UTF-8 which can lead
     to decoding errors.  Patch by Victor Stinner.

   - gh-96624(2): Fixed the failure of repeated runs of
     ‘test.test_unittest’ caused by side effects in
     ‘test_dotted_but_module_not_loaded’.

   - gh-95243(3): Mitigate the inherent race condition from using
     find_unused_port() in testSockName() by trying to find an unused
     port a few times before failing.  Patch by Ross Burton.

   - gh-95573(4): Lib/test/test_asyncio/test_ssl.py(5) exposed a bug in
     the macOS kernel where intense concurrent load on non-blocking
     sockets occasionally causes *note errno.ENOBUFS: 16ed. ("No buffer
     space available") to be emitted.  FB11063974 filed with Apple, in
     the mean time as a workaround buffer size used in tests on macOS is
     decreased to avoid intermittent failures.  Patch by Fantix King.

   - gh-95280(6): Fix problem with ‘test_ssl’ ‘test_get_ciphers’ on
     systems that require perfect forward secrecy (PFS) ciphers.

   - gh-95212(7): Make multiprocessing test case
     ‘test_shared_memory_recreate’ parallel-safe.

   - gh-95218(8): Move tests for importlib.resources into
     test_importlib.resources.

   - gh-93963(9): Updated tests to use preferred location for
     ‘importlib.resources’ ABCs.

   - gh-94675(10): Add a regression test for *note re: a7. exponentional
     slowdown when using rjsmin.

   - gh-91330(11): Added more tests for *note dataclasses: 27. to cover
     behavior with data descriptor-based fields.

   - gh-94208(12): ‘test_ssl’ is now checking for supported TLS version
     and protocols in more tests.

   - gh-94315(13): Tests now check for DAC override capability instead
     of relying on *note os.geteuid(): 16ee.

   - gh-54781(14): Rename test_tk to test_tkinter, and rename
     test_ttk_guionly to test_ttk.  Patch by Victor Stinner.

   - gh-93839(15): Move ‘Lib/ctypes/test/’ to ‘Lib/test/test_ctypes/’.
     Patch by Victor Stinner.

   - gh-93951(16): In test_bdb.StateTestCase.test_skip, avoid including
     auxiliary importers.

   - gh-93957(17): Provide nicer error reporting from subprocesses in
     test_venv.EnsurePipTest.test_with_pip.

   - gh-93884(18): Add test cases for *note PyNumber_ToBase(): 16ef.
     that take a large number or a non-int object as parameter.

   - gh-93852(19): test_asyncio, test_logging, test_socket and
     test_socketserver now create AF_UNIX domains in the current
     directory to no longer fail with ‘OSError("AF_UNIX path too long")’
     if the temporary directory (the ‘TMPDIR’ environment variable) is
     too long.  Patch by Victor Stinner.

   - gh-93353(20): regrtest now checks if a test leaks temporary files
     or directories if run with -jN option.  Patch by Victor Stinner.

   - gh-84461(21): ‘run_tests.py’ now handles cross compiling env vars
     correctly and pass ‘HOSTRUNNER’ to regression tests.

   - gh-93616(22): ‘test_modulefinder’ now creates a temporary directory
     in ‘ModuleFinderTest.setUp()’ instead of module scope.

   - gh-93575(23): Fix issue with test_unicode test_raiseMemError.  The
     test case now use ‘test.support.calcobjsize’ to calculate size of
     PyUnicode structs.  *note sys.getsizeof(): 166c. may return
     different size when string has UTF-8 memory.

   - gh-90473(24): WASI does not have a ‘chmod(2)’ syscall.  *note
     os.chmod(): 200. is now a dummy function on WASI. Skip all tests
     that depend on working *note os.chmod(): 200.

   - gh-90473(25): Skip tests on WASI that require symlinks with
     absolute paths.

   - gh-57539(26): Increase calendar test coverage for
     ‘calendar.LocaleTextCalendar.formatweekday()’.

   - gh-90473(27): Skip symlink tests on WASI. wasmtime uses
     ‘openat2(2)’ with ‘RESOLVE_BENEATH’ flag, which prevents symlinks
     with absolute paths.

   - gh-89858(28): Fix ‘test_embed’ for out-of-tree builds.  Patch by
     Kumar Aditya.

   - gh-92886(29): Fixing tests that fail when running with
     optimizations (‘-O’) in ‘test_imaplib.py’.

   - gh-92886(30): Fixing tests that fail when running with
     optimizations (‘-O’) in ‘test_zipimport.py’

   - gh-92886(31): Fixing tests that fail when running with
     optimizations (‘-O’) in ‘test_py_compile.py’

   - gh-92886(32): Fixing tests that fail when running with
     optimizations (‘-O’) in ‘test_sys_settrace.py’.

   - gh-92886(33): Fixing tests that fail when running with
     optimizations (‘-O’) in ‘_test_multiprocessing.py’

   - gh-92670(34): Skip
     ‘test_shutil.TestCopy.test_copyfile_nonexistent_dir’ test on AIX as
     the test uses a trailing slash to force the OS consider the path as
     a directory, but on AIX the trailing slash has no effect and is
     considered as a file.

   - gh-92514(35): Remove unused ‘test.support.BasicTestRunner’.  Patch
     by Jelle Zijlstra.

   - bpo-47016(36): Create a GitHub Actions workflow for verifying
     bundled pip and setuptools.  Patch by Illia Volochii and Adam
     Turner.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/95027

   (2) https://github.com/python/cpython/issues/96624

   (3) https://github.com/python/cpython/issues/95243

   (4) https://github.com/python/cpython/issues/95573

   (5) 
https://github.com/python/cpython/tree/3.13/Lib/test/test_asyncio/test_ssl.py

   (6) https://github.com/python/cpython/issues/95280

   (7) https://github.com/python/cpython/issues/95212

   (8) https://github.com/python/cpython/issues/95218

   (9) https://github.com/python/cpython/issues/93963

   (10) https://github.com/python/cpython/issues/94675

   (11) https://github.com/python/cpython/issues/91330

   (12) https://github.com/python/cpython/issues/94208

   (13) https://github.com/python/cpython/issues/94315

   (14) https://github.com/python/cpython/issues/54781

   (15) https://github.com/python/cpython/issues/93839

   (16) https://github.com/python/cpython/issues/93951

   (17) https://github.com/python/cpython/issues/93957

   (18) https://github.com/python/cpython/issues/93884

   (19) https://github.com/python/cpython/issues/93852

   (20) https://github.com/python/cpython/issues/93353

   (21) https://github.com/python/cpython/issues/84461

   (22) https://github.com/python/cpython/issues/93616

   (23) https://github.com/python/cpython/issues/93575

   (24) https://github.com/python/cpython/issues/90473

   (25) https://github.com/python/cpython/issues/90473

   (26) https://github.com/python/cpython/issues/57539

   (27) https://github.com/python/cpython/issues/90473

   (28) https://github.com/python/cpython/issues/89858

   (29) https://github.com/python/cpython/issues/92886

   (30) https://github.com/python/cpython/issues/92886

   (31) https://github.com/python/cpython/issues/92886

   (32) https://github.com/python/cpython/issues/92886

   (33) https://github.com/python/cpython/issues/92886

   (34) https://github.com/python/cpython/issues/92670

   (35) https://github.com/python/cpython/issues/92514

   (36) https://bugs.python.org/issue?@action=redirect&bpo=47016


File: python.info,  Node: Build<20>,  Next: Windows<17>,  Prev: Tests<18>,  Up: Python 3 12 0 alpha 1

1.23.21.6 Build
...............

   - gh-96761(1): Fix the build process of clang compiler for
     ‘_bootstrap_python’ if LTO optimization is applied.  Patch by
     Matthias Görgens and Donghee Na.

   - gh-96883(2): ‘wasm32-emscripten’ builds for browsers now include
     *note concurrent.futures: 1a. for *note asyncio: 8. and *note
     unittest.mock: f0.

   - gh-85936(3): CPython now uses the ThinLTO option as the default
     policy if the Clang compiler accepts the flag.  Patch by Donghee
     Na.

   - gh-96729(4): Ensure that Windows releases built with
     ‘Tools\msi\buildrelease.bat’ are upgradable to and from official
     Python releases.

   - gh-96269(5): Shared module targets now depend on new ‘MODULE_DEPS’
     variable, which includes ‘EXPORTSYMS’.  This fixes a build order
     issue on unsupported AIX platform.

   - gh-84461(6): ‘wasm32-emscripten’ platform no longer builds *note
     resource: aa. module, *note getresuid(): 12aa, *note getresgid():
     12a9, and their setters.  The APIs are stubs and not functional.

   - gh-95973(7): Add a new ‘--with-dsymutil’ configure option to link
     debug information in macOS. Patch by Pablo Galindo.

   - gh-90536(8): Use the BOLT post-link optimizer to improve
     performance, particularly on medium-to-large applications.

   - gh-93744(9): Remove the ‘configure --with-cxx-main’ build option:
     it didn't work for many years.  Remove the ‘MAINCC’ variable from
     ‘configure’ and ‘Makefile’.  Patch by Victor Stinner.

   - gh-94801(10): Fix a regression in ‘configure’ script that caused
     some header checks to ignore custom ‘CPPFLAGS’.  The regression was
     introduced in gh-94802(11).

   - gh-95145(12): wasm32-wasi builds no longer depend on WASIX's
     pthread stubs.  Python now has its own stubbed pthread API.

   - gh-95174(13): Python now detects missing ‘dup’ function in WASI and
     works around some missing *note errno: 4d, *note select: af, and
     *note socket: b8. constants.

   - gh-95174(14): Python now skips missing *note socket: b8. functions
     and methods on WASI. WASI can only create sockets from existing fd
     / accept and has no netdb.

   - gh-95085(15): Platforms ‘wasm32-unknown-emscripten’ and
     ‘wasm32-unknown-wasi’ have been promoted to PEP 11(16) tier 3
     platform support.

   - gh-94847(17): Fixed ‘_decimal’ module build issue on GCC when
     compiling with LTO and pydebug.  Debug builds no longer force
     inlining of functions.

   - gh-94841(18): Fix the possible performance regression of *note
     PyObject_Free(): c0c. compiled with MSVC version 1932.

   - gh-94801(19): ‘configure’ now uses custom flags like ‘ZLIB_CFLAGS’
     and ‘ZLIB_LIBS’ when searching for headers and libraries.

   - gh-94773(20): ‘deepfreeze.py’ now supports code object with
     frozensets that contain incompatible, unsortable types.

   - gh-94682(21): Build and test with OpenSSL 1.1.1q

   - gh-90005(22): Dependencies of *note readline: a8. and *note curses:
     23. module are now detected in ‘configure’ script with
     ‘pkg-config’.  Only ‘ncurses’ / ‘ncursesw’ are detected
     automatically.  The old ‘curses’ library is not configured
     automatically.  Workaround for missing ‘termcap’ or ‘tinfo’ library
     has been removed.

   - gh-90005(23): Fix building ‘_ctypes’ extension without
     ‘pkg-config’.

   - gh-90005(24): ‘_dbm’ module dependencies are now detected by
     configure.

   - gh-94404(25): ‘makesetup’ now works around an issue with sed on
     macOS and uses correct CFLAGS for object files that end up in a
     shared extension.  Module CFLAGS are used before
     PY_STDMODULE_CFLAGS to avoid clashes with system headers.

   - gh-93939(26): C extension modules are now built by ‘configure’ and
     ‘make’ instead of ‘distutils’ and ‘setup.py’.

   - gh-93939(27): The ‘2to3’, ‘idle’, and ‘pydoc’ scripts are now
     generated and installed by ‘Makefile’ instead of ‘setup.py’.

   - gh-94280(28): Updated pegen regeneration script on Windows to find
     and use Python 3.9 or higher.  Prior to this, pegen regeneration
     already required 3.9 or higher, but the script may have used lower
     versions of Python.

   - gh-93584(29): Address race condition in ‘Makefile’ when installing
     a PGO build.  All ‘test’ and ‘install’ targets now depend on ‘all’
     target.

   - gh-93491(30): ‘configure’ now detects and reports PEP 11(31)
     support tiers.

   - gh-69093(32): Fix ‘Modules/Setup.stdlib.in’ rule for ‘_sqlite3’
     extension.

   - gh-93207(33): ‘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.  Patch by
     Kumar Aditya.

   - gh-93202(34): Python now always use the ‘%zu’ and ‘%zd’ printf
     formats to format a ‘size_t’ or ‘Py_ssize_t’ number.  Building
     Python 3.12 requires a C11 compiler, so these printf formats are
     now always supported.  Patch by Victor Stinner.

   - gh-90473(35): Disable pymalloc and increase stack size on
     ‘wasm32-wasi’.

   - bpo-34449(36): Drop invalid compiler switch ‘-fPIC’ for HP aCC on
     HP-UX. Patch by Michael Osipov.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/96761

   (2) https://github.com/python/cpython/issues/96883

   (3) https://github.com/python/cpython/issues/85936

   (4) https://github.com/python/cpython/issues/96729

   (5) https://github.com/python/cpython/issues/96269

   (6) https://github.com/python/cpython/issues/84461

   (7) https://github.com/python/cpython/issues/95973

   (8) https://github.com/python/cpython/issues/90536

   (9) https://github.com/python/cpython/issues/93744

   (10) https://github.com/python/cpython/issues/94801

   (11) https://github.com/python/cpython/issues/94802

   (12) https://github.com/python/cpython/issues/95145

   (13) https://github.com/python/cpython/issues/95174

   (14) https://github.com/python/cpython/issues/95174

   (15) https://github.com/python/cpython/issues/95085

   (16) https://peps.python.org/pep-0011/

   (17) https://github.com/python/cpython/issues/94847

   (18) https://github.com/python/cpython/issues/94841

   (19) https://github.com/python/cpython/issues/94801

   (20) https://github.com/python/cpython/issues/94773

   (21) https://github.com/python/cpython/issues/94682

   (22) https://github.com/python/cpython/issues/90005

   (23) https://github.com/python/cpython/issues/90005

   (24) https://github.com/python/cpython/issues/90005

   (25) https://github.com/python/cpython/issues/94404

   (26) https://github.com/python/cpython/issues/93939

   (27) https://github.com/python/cpython/issues/93939

   (28) https://github.com/python/cpython/issues/94280

   (29) https://github.com/python/cpython/issues/93584

   (30) https://github.com/python/cpython/issues/93491

   (31) https://peps.python.org/pep-0011/

   (32) https://github.com/python/cpython/issues/69093

   (33) https://github.com/python/cpython/issues/93207

   (34) https://github.com/python/cpython/issues/93202

   (35) https://github.com/python/cpython/issues/90473

   (36) https://bugs.python.org/issue?@action=redirect&bpo=34449


File: python.info,  Node: Windows<17>,  Next: macOS<13>,  Prev: Build<20>,  Up: Python 3 12 0 alpha 1

1.23.21.7 Windows
.................

   - gh-98360(1): Fixes *note multiprocessing: 86. spawning child
     processes on Windows from a virtual environment to ensure that
     child processes that also use *note multiprocessing: 86. to spawn
     more children will recognize that they are in a virtual
     environment.

   - gh-98414(2): Fix ‘py.exe’ launcher handling of ‘-V:<COMPANY>/’
     option when default preferences have been set in environment
     variables or configuration files.

   - gh-97728(3): Fix possible crashes caused by the use of
     uninitialized variables when pass invalid arguments in *note
     os.system(): 13c8. on Windows and in Windows-specific modules (like
     ‘winreg’).

   - gh-90989(4): Made *note Python Launcher for Windows: 562. install
     per-user by default (unless an all users install already exists),
     and clarify some text in the installer.

   - gh-97649(5): The ‘Tools’ directory is no longer installed on
     Windows

   - gh-96965(6): Update libffi to 3.4.3

   - gh-96577(7): Fixes a potential buffer overrun in ‘msilib’.

   - gh-96559(8): Fixes the Windows launcher not using the compatible
     interpretation of default tags found in configuration files when no
     tag was passed to the command.

   - gh-94781(9): Fix ‘pcbuild.proj’ to clean previous instances of
     output files in ‘Python\deepfreeze’ and ‘Python\frozen_modules’
     directories on Windows.  Patch by Charlie Zhao.

   - gh-89545(10): Updates *note platform: 98. code getting the Windows
     version to use native Windows Management Instrumentation (WMI)
     queries to determine OS version, type, and architecture.

   - gh-95733(11): Make certain requirements of the Windows Store
     package optional to allow installing on earlier updates of Windows.

   - gh-95656(12): Enable the *note enable_load_extension(): 7e2. *note
     sqlite3: ba. API.

   - gh-95587(13): Fixes some issues where the Windows installer would
     incorrectly detect certain features of an existing install when
     upgrading.

   - gh-94399(14): Restores the behaviour of *note Python Launcher for
     Windows: 562. for ‘/usr/bin/env’ shebang lines, which will now
     search ‘PATH’ for an executable matching the given command.  If
     none is found, the usual search process is used.

   - gh-95445(15): Fixes the unsuccessful removal of the HTML document
     directory when uninstalling with Windows msi.

   - gh-95359(16): Fix *note Python Launcher for Windows: 562. handling
     of ‘py.ini’ commands (it was incorrectly expecting a ‘py_’ prefix
     on keys) and crashes when reading per-user configuration file.

   - gh-95285(17): Fix *note Python Launcher for Windows: 562. handling
     of command lines where it is only passed a short executable name.

   - gh-90844(18): Allow virtual environments to correctly launch when
     they have spaces in the path.

   - gh-94772(19): Fix incorrect handling of shebang lines in py.exe
     launcher

   - gh-94018(20): *note zipfile: 117. will now remove trailing spaces
     from path components when extracting files on Windows.

   - gh-93824(21): Drag and drop of files onto Python files in Windows
     Explorer has been enabled for Windows ARM64.

   - gh-43414(22): *note os.get_terminal_size(): 109a. now attempts to
     read the size from any provided handle, rather than only supporting
     file descriptors 0, 1 and 2.

   - gh-92817(23): Ensures that ‘py.exe’ will prefer an active virtual
     environment over default tags specified with environment variables
     or through a ‘py.ini’ file.

   - gh-92984(24): Explicitly disable incremental linking for non-Debug
     builds

   - gh-92841(25): *note asyncio: 8. no longer throws ‘RuntimeError:
     Event loop is closed’ on interpreter exit after asynchronous socket
     activity.  Patch by Oleg Iarygin.

   - bpo-46907(26): Update Windows installer to use SQLite 3.38.4.

   - gh-91061(27): Accept os.PathLike for the argument to
     winsound.PlaySound

   - bpo-42658(28): Support native Windows case-insensitive path
     comparisons by using ‘LCMapStringEx’ instead of *note str.lower():
     16f2. in ‘ntpath.normcase()’.  Add ‘LCMapStringEx’ to the ‘_winapi’
     module.

   - bpo-38704(29): Prevent installation on unsupported Windows
     versions.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/98360

   (2) https://github.com/python/cpython/issues/98414

   (3) https://github.com/python/cpython/issues/97728

   (4) https://github.com/python/cpython/issues/90989

   (5) https://github.com/python/cpython/issues/97649

   (6) https://github.com/python/cpython/issues/96965

   (7) https://github.com/python/cpython/issues/96577

   (8) https://github.com/python/cpython/issues/96559

   (9) https://github.com/python/cpython/issues/94781

   (10) https://github.com/python/cpython/issues/89545

   (11) https://github.com/python/cpython/issues/95733

   (12) https://github.com/python/cpython/issues/95656

   (13) https://github.com/python/cpython/issues/95587

   (14) https://github.com/python/cpython/issues/94399

   (15) https://github.com/python/cpython/issues/95445

   (16) https://github.com/python/cpython/issues/95359

   (17) https://github.com/python/cpython/issues/95285

   (18) https://github.com/python/cpython/issues/90844

   (19) https://github.com/python/cpython/issues/94772

   (20) https://github.com/python/cpython/issues/94018

   (21) https://github.com/python/cpython/issues/93824

   (22) https://github.com/python/cpython/issues/43414

   (23) https://github.com/python/cpython/issues/92817

   (24) https://github.com/python/cpython/issues/92984

   (25) https://github.com/python/cpython/issues/92841

   (26) https://bugs.python.org/issue?@action=redirect&bpo=46907

   (27) https://github.com/python/cpython/issues/91061

   (28) https://bugs.python.org/issue?@action=redirect&bpo=42658

   (29) https://bugs.python.org/issue?@action=redirect&bpo=38704


File: python.info,  Node: macOS<13>,  Next: IDLE<13>,  Prev: Windows<17>,  Up: Python 3 12 0 alpha 1

1.23.21.8 macOS
...............

   - gh-97897(1): The macOS 13 SDK includes support for the ‘mkfifoat’
     and ‘mknodat’ system calls.  Using the ‘dir_fd’ option with either
     *note os.mkfifo(): d36. or *note os.mknod(): d37. could result in a
     segfault if cpython is built with the macOS 13 SDK but run on an
     earlier version of macOS. Prevent this by adding runtime support
     for detection of these system calls ("weaklinking") as is done for
     other newer syscalls on macOS.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/97897


File: python.info,  Node: IDLE<13>,  Next: Tools/Demos<10>,  Prev: macOS<13>,  Up: Python 3 12 0 alpha 1

1.23.21.9 IDLE
..............

   - gh-97527(1): Fix a bug in the previous bugfix that caused IDLE to
     not start when run with 3.10.8, 3.12.0a1, and at least Microsoft
     Python 3.10.2288.0 installed without the Lib/test package.  3.11.0
     was never affected.

   - gh-65802(2): Document handling of extensions in Save As dialogs.

   - gh-95191(3): Include prompts when saving Shell (interactive input
     and output).

   - gh-95511(4): Fix the Shell context menu copy-with-prompts bug of
     copying an extra line when one selects whole lines.

   - gh-95471(5): In the Edit menu, move ‘Select All’ and add a new
     separator.

   - gh-95411(6): Enable using IDLE's module browser with .pyw files.

   - gh-89610(7): Add .pyi as a recognized extension for IDLE on macOS.
     This allows opening stub files by double clicking on them in the
     Finder.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/97527

   (2) https://github.com/python/cpython/issues/65802

   (3) https://github.com/python/cpython/issues/95191

   (4) https://github.com/python/cpython/issues/95511

   (5) https://github.com/python/cpython/issues/95471

   (6) https://github.com/python/cpython/issues/95411

   (7) https://github.com/python/cpython/issues/89610


File: python.info,  Node: Tools/Demos<10>,  Next: C API<19>,  Prev: IDLE<13>,  Up: Python 3 12 0 alpha 1

1.23.21.10 Tools/Demos
......................

   - gh-68686(1): Remove ptags and eptags scripts.

   - gh-97681(2): Remove the ‘Tools/demo/’ directory which contained old
     demo scripts.  A copy can be found in the old-demos project(3).
     Patch by Victor Stinner.

   - gh-97669(4): Remove outdated example scripts of the
     ‘Tools/scripts/’ directory.  A copy can be found in the old-demos
     project(5).  Patch by Victor Stinner.

   - gh-95853(6): The ‘wasm_build.py’ script now pre-builds Emscripten
     ports, checks for broken EMSDK versions, and warns about pkg-config
     env vars.

   - gh-95853(7): The new tool ‘Tools/wasm/wasm_builder.py’ automates
     configure, compile, and test steps for building CPython on
     WebAssembly platforms.

   - gh-95731(8): Fix handling of module docstrings in
     ‘Tools/i18n/pygettext.py’.

   - gh-93939(9): Add script ‘Tools/scripts/check_modules.py’ to check
     and validate builtin and shared extension modules.  The script also
     handles ‘Modules/Setup’ and will eventually replace ‘setup.py’.

   - gh-94538(10): Fix Argument Clinic output to custom file
     destinations.  Patch by Erlend E. Aasland.

   - gh-94430(11): Allow parameters named ‘module’ and ‘self’ with
     custom C names in Argument Clinic.  Patch by Erlend E. Aasland

   - gh-86087(12): The ‘Tools/scripts/parseentities.py’ script used to
     parse HTML4 entities has been removed.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/68686

   (2) https://github.com/python/cpython/issues/97681

   (3) https://github.com/gvanrossum/old-demos

   (4) https://github.com/python/cpython/issues/97669

   (5) https://github.com/gvanrossum/old-demos

   (6) https://github.com/python/cpython/issues/95853

   (7) https://github.com/python/cpython/issues/95853

   (8) https://github.com/python/cpython/issues/95731

   (9) https://github.com/python/cpython/issues/93939

   (10) https://github.com/python/cpython/issues/94538

   (11) https://github.com/python/cpython/issues/94430

   (12) https://github.com/python/cpython/issues/86087


File: python.info,  Node: C API<19>,  Prev: Tools/Demos<10>,  Up: Python 3 12 0 alpha 1

1.23.21.11 C API
................

   - gh-98393(1): The *note PyUnicode_FSDecoder(): 51d. function no
     longer accepts bytes-like paths, like *note bytearray: 4e3. and
     *note memoryview: 40f. types: only the exact *note bytes: 1a5. type
     is accepted for bytes strings.  Patch by Victor Stinner.

   - gh-91051(2): Add *note PyType_Watch(): 50b. and related APIs to
     allow callbacks on *note PyType_Modified(): 16f7.

   - gh-95756(3): Lazily create and cache ‘co_’ attributes for better
     performance for code getters.

   - gh-96512(4): Configuration for the *note integer string conversion
     length limitation: 599. now lives in the PyConfig C API struct.

   - gh-95589(5): Extensions classes that set ‘tp_dictoffset’ and
     ‘tp_weaklistoffset’ lose the support for multiple inheritance, but
     are now safe.  Extension classes should use *note
     Py_TPFLAGS_MANAGED_DICT: 31b. and *note Py_TPFLAGS_MANAGED_WEAKREF:
     500. instead.

   - gh-95781(6): An unrecognized format character in *note
     PyUnicode_FromFormat(): 33f. and *note PyUnicode_FromFormatV():
     51a. now sets a *note SystemError: 51b.  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.

   - gh-92678(7): Restore the 3.10 behavior for multiple inheritance of
     C extension classes that store their dictionary at the end of the
     struct.

   - gh-92678(8): Support C extensions using managed dictionaries by
     setting the ‘Py_TPFLAGS_MANAGED_DICT’ flag.

   - gh-93274(9): API for implementing vectorcall (*note
     Py_TPFLAGS_HAVE_VECTORCALL: 4fa, *note PyVectorcall_NARGS(): 4fb.
     and *note PyVectorcall_Call(): 4fc.) was added to the limited API
     and stable ABI.

   - gh-95504(10): Fix sign placement when specifying width or precision
     in *note PyUnicode_FromFormat(): 33f. and *note
     PyUnicode_FromFormatV(): 51a.  Patch by Philip Georgi.

   - gh-93012(11): The *note Py_TPFLAGS_HAVE_VECTORCALL: 4fa. flag is
     now removed from a class when the class's *note __call__(): 4fe.
     method is reassigned.  This makes vectorcall safe to use with
     mutable types (i.e.  heap types without the ‘immutable’ flag).
     Mutable types that do not override *note tp_call: 4ff. now inherit
     the *note Py_TPFLAGS_HAVE_VECTORCALL: 4fa. flag.

   - gh-95388(12): Creating *note immutable types: 38d. with mutable
     bases is deprecated and is planned to be disabled in Python 3.14.

   - gh-92678(13): Adds unstable C-API functions
     ‘_PyObject_VisitManagedDict’ and ‘_PyObject_ClearManagedDict’ to
     allow C extensions to allow the VM to manage their object's
     dictionaries.

   - gh-94936(14): Added *note PyCode_GetVarnames(): 71d, *note
     PyCode_GetCellvars(): 71e. and *note PyCode_GetFreevars(): 71f. for
     accessing ‘co_varnames’, ‘co_cellvars’ and ‘co_freevars’
     respectively via the C API.

   - gh-94930(15): Fix ‘SystemError’ raised when *note
     PyArg_ParseTupleAndKeywords(): 2e9. is used with ‘#’ in ‘(...)’ but
     without ‘PY_SSIZE_T_CLEAN’ defined.

   - gh-94731(16): Python again uses C-style casts for most casting
     operations when compiled with C++.  This may trigger compiler
     warnings, if they are enabled with e.g.  ‘-Wold-style-cast’ or
     ‘-Wzero-as-null-pointer-constant’ options for ‘g++’.

   - gh-93937(17): The following frame functions and type are now
     directly available with ‘#include <Python.h>’, it's no longer
     needed to add ‘#include <frameobject.h>’:

        * *note PyFrame_Check(): 729.

        * *note PyFrame_GetBack(): 72a.

        * *note PyFrame_GetBuiltins(): 70f.

        * *note PyFrame_GetGenerator(): 710.

        * *note PyFrame_GetGlobals(): 711.

        * *note PyFrame_GetLasti(): 712.

        * *note PyFrame_GetLocals(): 35f.

        * *note PyFrame_Type: 72b.

     Patch by Victor Stinner.

   - gh-91321(18): Fix the compatibility of the Python C API with C++
     older than C++11.  Patch by Victor Stinner.

   - gh-91731(19): Avoid defining the ‘static_assert’ when compiling
     with C++ 11, where this is a keyword and redefining it can lead to
     undefined behavior.  Patch by Pablo Galindo

   - gh-89546(20): *note PyType_FromMetaclass(): 4f6. (and other
     ‘PyType_From*’ functions) now check that offsets and the base
     class's *note tp_basicsize: 92b. fit in the new class's
     ‘tp_basicsize’.

   - gh-93503(21): Add two new public functions to the public C-API,
     *note PyEval_SetProfileAllThreads(): 504. and *note
     PyEval_SetTraceAllThreads(): 505, that allow to set tracing and
     profiling functions in all running threads in addition to the
     calling one.  Also, two analogous functions to the *note threading:
     d6. module (*note threading.setprofile_all_threads(): 470. and
     *note threading.settrace_all_threads(): 46f.) that allow to do the
     same from Python.  Patch by Pablo Galindo

   - gh-93442(22): Add C++ overloads for _Py_CAST_impl() to handle
     0/NULL. This will allow C++ extensions that pass 0 or NULL to
     macros using _Py_CAST() to continue to compile.

   - gh-93466(23): Slot IDs in PyType_Spec may not be repeated.  The
     documentation was updated to mention this.  For some cases of
     repeated slots, PyType_FromSpec and related functions will now
     raise an exception.

   - gh-92898(24): Fix C++ compiler warnings when casting function
     arguments to ‘PyObject*’.  Patch by Serge Guelton.

   - gh-93103(25): Deprecate global configuration variables, like *note
     Py_IgnoreEnvironmentFlag: 3a3, in the documentation: the *note
     Py_InitializeFromConfig(): 390. API should be instead.  Patch by
     Victor Stinner.

   - gh-77782(26): Deprecate global configuration variable like *note
     Py_IgnoreEnvironmentFlag: 3a3.: the *note
     Py_InitializeFromConfig(): 390. API should be instead.  Patch by
     Victor Stinner.

   - gh-92913(27): Ensures changes to *note
     PyConfig.module_search_paths: 36d. are ignored unless *note
     PyConfig.module_search_paths_set: 593. is set

   - gh-92781(28): Avoid mixing declarations and code in the C API to
     fix the compiler warning: "ISO C90 forbids mixed declarations and
     code" [-Werror=declaration-after-statement].  Patch by Victor
     Stinner.

   - gh-92651(29): Remove the ‘token.h’ header file.  There was never
     any public tokenizer C API. The ‘token.h’ header file was only
     designed to be used by Python internals.  Patch by Victor Stinner.

   - gh-92536(30): Remove legacy Unicode APIs based on ‘Py_UNICODE*’.

   - gh-85858(31): Remove the ‘PyUnicode_InternImmortal()’ function and
     the ‘SSTATE_INTERNED_IMMORTAL’ macro.  Patch by Victor Stinner.

   - gh-92193(32): Add new function *note PyFunction_SetVectorcall():
     506. to the C API which sets the vectorcall field of a given *note
     PyFunctionObject: 507.

     Warning: extensions using this API must preserve the behavior of
     the unaltered function!

   - gh-59121(33): Fixed an assert that prevented ‘PyRun_InteractiveOne’
     from providing tracebacks when parsing from the provided FD.

   - bpo-45383(34): The *note PyType_FromSpec(): 523. API will now find
     and use a metaclass based on the provided bases.  An error will be
     raised if there is a metaclass conflict.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/98393

   (2) https://github.com/python/cpython/issues/91051

   (3) https://github.com/python/cpython/issues/95756

   (4) https://github.com/python/cpython/issues/96512

   (5) https://github.com/python/cpython/issues/95589

   (6) https://github.com/python/cpython/issues/95781

   (7) https://github.com/python/cpython/issues/92678

   (8) https://github.com/python/cpython/issues/92678

   (9) https://github.com/python/cpython/issues/93274

   (10) https://github.com/python/cpython/issues/95504

   (11) https://github.com/python/cpython/issues/93012

   (12) https://github.com/python/cpython/issues/95388

   (13) https://github.com/python/cpython/issues/92678

   (14) https://github.com/python/cpython/issues/94936

   (15) https://github.com/python/cpython/issues/94930

   (16) https://github.com/python/cpython/issues/94731

   (17) https://github.com/python/cpython/issues/93937

   (18) https://github.com/python/cpython/issues/91321

   (19) https://github.com/python/cpython/issues/91731

   (20) https://github.com/python/cpython/issues/89546

   (21) https://github.com/python/cpython/issues/93503

   (22) https://github.com/python/cpython/issues/93442

   (23) https://github.com/python/cpython/issues/93466

   (24) https://github.com/python/cpython/issues/92898

   (25) https://github.com/python/cpython/issues/93103

   (26) https://github.com/python/cpython/issues/77782

   (27) https://github.com/python/cpython/issues/92913

   (28) https://github.com/python/cpython/issues/92781

   (29) https://github.com/python/cpython/issues/92651

   (30) https://github.com/python/cpython/issues/92536

   (31) https://github.com/python/cpython/issues/85858

   (32) https://github.com/python/cpython/issues/92193

   (33) https://github.com/python/cpython/issues/59121

   (34) https://bugs.python.org/issue?@action=redirect&bpo=45383


File: python.info,  Node: Python 3 11 0 beta 1,  Next: Python 3 11 0 alpha 7,  Prev: Python 3 12 0 alpha 1,  Up: Changelog（更動日誌）

1.23.22 Python 3.11.0 beta 1
----------------------------

'Release date: 2022-05-06'

* Menu:

* Security: Security<15>.
* Core and Builtins: Core and Builtins<22>.
* Library: Library<21>.
* Documentation: Documentation<16>.
* Tests: Tests<19>.
* Build: Build<21>.
* Windows: Windows<18>.
* macOS: macOS<14>.
* Tools/Demos: Tools/Demos<11>.
* C API: C API<20>.


File: python.info,  Node: Security<15>,  Next: Core and Builtins<22>,  Up: Python 3 11 0 beta 1

1.23.22.1 Security
..................

   - gh-57684(1): Add the *note -P: 548. command line option and the
     *note PYTHONSAFEPATH: 549. environment variable to not prepend a
     potentially unsafe path to *note sys.path: 37f.  Patch by Victor
     Stinner.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/57684


File: python.info,  Node: Core and Builtins<22>,  Next: Library<21>,  Prev: Security<15>,  Up: Python 3 11 0 beta 1

1.23.22.2 Core and Builtins
...........................

   - gh-89519(1): Chaining classmethod descriptors (introduced in
     bpo-19072(2)) is deprecated.  It can no longer be used to wrap
     other descriptors such as property().  The core design of this
     feature was flawed, and it caused a number of downstream problems.

   - gh-92345(3): ‘pymain_run_python()’ now imports ‘readline’ and
     ‘rlcompleter’ before sys.path is extended to include the current
     working directory of an interactive interpreter.  Non-interactive
     interpreters are not affected.

   - bpo-43857(4): Improve the *note AttributeError: 2f6. message when
     deleting a missing attribute.  Patch by Géry Ogam.

   - gh-92245(5): Make sure that PEP 523 is respected in all cases.  In
     3.11a7, specialization may have prevented Python-to-Python calls
     respecting PEP 523.

   - gh-92203(6): Add a closure keyword-only parameter to *note exec():
     162.  It can only be specified when exec-ing a code object that
     uses free variables.  When specified, it must be a tuple, with
     exactly the number of cell variables referenced by the code object.
     closure has a default value of ‘None’, and it must be ‘None’ if the
     code object doesn't refer to any free variables.

   - gh-91173(7): Disable frozen modules in debug builds.  Patch by
     Kumar Aditya.

   - gh-92114(8): Improve error message when subscript a type with
     ‘__class_getitem__’ set to ‘None’.

   - gh-92112(9): Fix crash triggered by an evil custom ‘mro()’ on a
     metaclass.

   - gh-92063(10): The ‘PRECALL_METHOD_DESCRIPTOR_FAST_WITH_KEYWORDS’
     instruction now ensures methods are called only on objects of the
     correct type.

   - gh-92031(11): Deoptimize statically allocated code objects during
     ‘Py_FINALIZE()’ so that future ‘_PyCode_Quicken’ calls always start
     with unquickened code.

   - gh-92036(12): Fix a crash in subinterpreters related to the garbage
     collector.  When a subinterpreter is deleted, untrack all objects
     tracked by its GC. To prevent a crash in deallocator functions
     expecting objects to be tracked by the GC, leak a strong reference
     to these objects on purpose, so they are never deleted and their
     deallocator functions are not called.  Patch by Victor Stinner.

   - gh-92032(13): The interpreter can now autocomplete soft keywords,
     as of now ‘match’, ‘case’, and ‘_’ (wildcard pattern) from PEP
     634(14).

   - gh-87999(15): The warning emitted by the Python parser for a
     numeric literal immediately followed by keyword has been changed
     from deprecation warning to syntax warning.

   - gh-91869(16): Fix an issue where specialized opcodes with extended
     arguments could produce incorrect tracing output or lead to
     assertion failures.

   - gh-91603(17): Speed up *note types.UnionType: 5e0. instantiation.
     Based on patch provided by Yurii Karabas.

   - gh-89373(18): If Python is built in debug mode, Python now ensures
     that deallocator functions leave the current exception unchanged.
     Patch by Victor Stinner.

   - gh-91632(19): Fix a minor memory leak at exit: release the memory
     of the ‘generic_alias_iterator’ type.  Patch by Donghee Na.

   - gh-81548(20): Octal escapes with value larger than ‘0o377’ now
     produce a *note DeprecationWarning: 18b.  In a future Python
     version they will be a *note SyntaxWarning: 40c. and eventually a
     *note SyntaxError: 173.

   - bpo-43950(21): Use a single compact table for line starts, ends and
     column offsets.  Reduces memory consumption for location info by
     half

   - gh-91102(22): Use Argument Clinic for ‘EncodingMap’.  Patch by Oleg
     Iarygin.

   - gh-91636(23): Fixed a crash in a garbage-collection edge-case, in
     which a ‘PyFunction_Type.tp_clear’ function could leave a python
     function object in an inconsistent state.

   - gh-91603(24): Speed up *note isinstance(): 3e8. and *note
     issubclass(): 765. checks for *note types.UnionType: 5e0.  Patch by
     Yurii Karabas.

   - gh-91625(25): Fixed a bug in which adaptive opcodes ignored any
     preceding ‘EXTENDED_ARG’s on specialization failure.

   - gh-78607(26): The LLTRACE special build now looks for the name
     ‘__lltrace__’ defined in module globals, rather than the name
     ‘__ltrace__’, which had been introduced as a typo.

   - gh-91576(27): Speed up iteration of ascii strings by 50%.  Patch by
     Kumar Aditya.

   - gh-89279(28): Improve interpreter performance on Windows by
     inlining a few specific macros.

   - gh-91502(29): Add a new ‘_PyFrame_IsEntryFrame()’ API function, to
     check if a *note PyFrameObject: 72d. is an entry frame.  Patch by
     Pablo Galindo.

   - gh-91266(30): Refactor the ‘bytearray’ strip methods ‘strip’,
     ‘lstrip’ and ‘rstrip’ to use a common implementation.

   - gh-91479(31): Replaced the ‘__note__’ field of *note BaseException:
     55f. (added in an earlier version of 3.11) with the final design of
     PEP 678(32).  Namely, *note BaseException: 55f. gets an
     ‘add_note()’ method, and its ‘__notes__’ field is created when
     necessary.

   - gh-46055(33): Speed up right shift of negative integers, by
     removing unnecessary creation of temporaries.  Original patch by
     Xinhang Xu, reworked by Mark Dickinson.

   - gh-91462(34): Make the interpreter's low-level tracing (lltrace)
     feature output more readable by displaying opcode names (rather
     than just numbers), and by displaying stack contents before each
     opcode.

   - gh-89455(35): Fixed an uninitialized bool value in the traceback
     printing code path that was introduced by the initial bpo-45292(36)
     exception groups work.

   - gh-91421(37): Fix a potential integer overflow in _Py_DecodeUTF8Ex.

   - gh-91428(38): Add ‘static const char *const _PyOpcode_OpName[256] =
     {...};’ to ‘opcode.h’ for debug builds to assist in debugging the
     Python interpreter.  It is now more convenient to make various
     forms of debugging output more human-readable by including opcode
     names rather than just the corresponding decimal digits.

   - bpo-47120(39): Make *note POP_JUMP_IF_TRUE: 15e8, *note
     POP_JUMP_IF_FALSE: 15e9, *note POP_JUMP_IF_NONE: 16fb. and *note
     POP_JUMP_IF_NOT_NONE: 16fc. virtual, mapping to new relative jump
     opcodes.

   - bpo-45317(40): Add internal documentation explaining design of new
     (for 3.11) frame stack.

   - bpo-47197(41): ctypes used to mishandle ‘void’ return types, so
     that for instance a function declared like ‘ctypes.CFUNCTYPE(None,
     ctypes.c_int)’ would be called with signature ‘int f(int)’ instead
     of ‘void f(int)’.  Wasm targets require function pointers to be
     called with the correct signatures so this led to crashes.  The
     problem is now fixed.

   - bpo-47120(42): Make opcodes ‘JUMP_IF_TRUE_OR_POP’ and
     ‘JUMP_IF_FALSE_OR_POP’ relative rather than absolute.

   - bpo-47177(43): Replace the ‘f_lasti’ member of the internal
     ‘_PyInterpreterFrame’ structure with a ‘prev_instr’ pointer, which
     reduces overhead in the main interpreter loop.  The ‘f_lasti’
     attribute of Python-layer frame objects is preserved for
     backward-compatibility.

   - bpo-46961(44): Integer mod/remainder operations, including the
     three-argument form of *note pow(): 976, now consistently return
     ints from the global small integer cache when applicable.

   - bpo-46962(45): Classes and functions that unconditionally declared
     their docstrings ignoring the ‘--without-doc-strings’ compilation
     flag no longer do so.

     The classes affected are ‘ctypes.UnionType’, *note
     pickle.PickleBuffer: 16fd, ‘testcapi.RecursingInfinitelyError’, and
     *note types.GenericAlias: 78f.

     The functions affected are 24 methods in *note ctypes: 22.

     Patch by Oleg Iarygin.

   - bpo-46942(46): Use Argument Clinic for the *note types.MethodType:
     16fe. constructor.  Patch by Oleg Iarygin.

   - bpo-46764(47): Fix wrapping bound methods with @classmethod

   - bpo-43464(48): Optimize ‘set.intersection()’ for non-set arguments.

   - bpo-46721(49): Optimize ‘set.issuperset()’ for non-set argument.

   - bpo-46509(50): Add type-specialized versions of the ‘Py_DECREF()’,
     and use them for ‘float’, ‘int’, ‘str’, ‘bool’, and ‘None’ to avoid
     pointer-chasing at runtime where types are known at C compile time.

   - bpo-46045(51): Do not use POSIX semaphores on NetBSD

   - bpo-36819(52): Fix crashes in built-in encoders with error handlers
     that return position less or equal than the starting position of
     non-encodable characters.

   - bpo-34093(53): ‘marshal.dumps()’ uses ‘FLAG_REF’ for all interned
     strings.  This makes output more deterministic and helps
     reproducible build.

   - bpo-26579(54): Added ‘object.__getstate__’ which provides the
     default implementation of the ‘__getstate__()’ method.

     Copying and pickling instances of subclasses of builtin types
     bytearray, set, frozenset, collections.OrderedDict,
     collections.deque, weakref.WeakSet, and datetime.tzinfo now copies
     and pickles instance attributes implemented as slots.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/89519

   (2) https://bugs.python.org/issue?@action=redirect&bpo=19072

   (3) https://github.com/python/cpython/issues/92345

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43857

   (5) https://github.com/python/cpython/issues/92245

   (6) https://github.com/python/cpython/issues/92203

   (7) https://github.com/python/cpython/issues/91173

   (8) https://github.com/python/cpython/issues/92114

   (9) https://github.com/python/cpython/issues/92112

   (10) https://github.com/python/cpython/issues/92063

   (11) https://github.com/python/cpython/issues/92031

   (12) https://github.com/python/cpython/issues/92036

   (13) https://github.com/python/cpython/issues/92032

   (14) https://peps.python.org/pep-0634/

   (15) https://github.com/python/cpython/issues/87999

   (16) https://github.com/python/cpython/issues/91869

   (17) https://github.com/python/cpython/issues/91603

   (18) https://github.com/python/cpython/issues/89373

   (19) https://github.com/python/cpython/issues/91632

   (20) https://github.com/python/cpython/issues/81548

   (21) https://bugs.python.org/issue?@action=redirect&bpo=43950

   (22) https://github.com/python/cpython/issues/91102

   (23) https://github.com/python/cpython/issues/91636

   (24) https://github.com/python/cpython/issues/91603

   (25) https://github.com/python/cpython/issues/91625

   (26) https://github.com/python/cpython/issues/78607

   (27) https://github.com/python/cpython/issues/91576

   (28) https://github.com/python/cpython/issues/89279

   (29) https://github.com/python/cpython/issues/91502

   (30) https://github.com/python/cpython/issues/91266

   (31) https://github.com/python/cpython/issues/91479

   (32) https://peps.python.org/pep-0678/

   (33) https://github.com/python/cpython/issues/46055

   (34) https://github.com/python/cpython/issues/91462

   (35) https://github.com/python/cpython/issues/89455

   (36) https://bugs.python.org/issue?@action=redirect&bpo=45292

   (37) https://github.com/python/cpython/issues/91421

   (38) https://github.com/python/cpython/issues/91428

   (39) https://bugs.python.org/issue?@action=redirect&bpo=47120

   (40) https://bugs.python.org/issue?@action=redirect&bpo=45317

   (41) https://bugs.python.org/issue?@action=redirect&bpo=47197

   (42) https://bugs.python.org/issue?@action=redirect&bpo=47120

   (43) https://bugs.python.org/issue?@action=redirect&bpo=47177

   (44) https://bugs.python.org/issue?@action=redirect&bpo=46961

   (45) https://bugs.python.org/issue?@action=redirect&bpo=46962

   (46) https://bugs.python.org/issue?@action=redirect&bpo=46942

   (47) https://bugs.python.org/issue?@action=redirect&bpo=46764

   (48) https://bugs.python.org/issue?@action=redirect&bpo=43464

   (49) https://bugs.python.org/issue?@action=redirect&bpo=46721

   (50) https://bugs.python.org/issue?@action=redirect&bpo=46509

   (51) https://bugs.python.org/issue?@action=redirect&bpo=46045

   (52) https://bugs.python.org/issue?@action=redirect&bpo=36819

   (53) https://bugs.python.org/issue?@action=redirect&bpo=34093

   (54) https://bugs.python.org/issue?@action=redirect&bpo=26579


File: python.info,  Node: Library<21>,  Next: Documentation<16>,  Prev: Core and Builtins<22>,  Up: Python 3 11 0 beta 1

1.23.22.3 Library
.................

   - gh-87901(1): Add the 'encoding' parameter to *note os.popen(): a2a.

   - gh-90997(2): Fix an issue where *note dis: 30. utilities may
     interpret populated inline cache entries as valid instructions.

   - gh-92332(3): Deprecate *note typing.Text: 2dd. (removal of the
     class is currently not planned).  Patch by Alex Waygood.

   - Deprecate nested classes in enum definitions becoming members - in
     3.13 they will be normal classes; add ‘member’ and ‘nonmember’
     functions to allow control over results now.

   - gh-92356(4): Fixed a performance regression in ctypes function
     calls.

   - gh-90997(5): Show the actual named values stored in inline caches
     when ‘show_caches=True’ is passed to *note dis: 30. utilities.

   - gh-92301(6): Prefer ‘close_range()’ to iterating over procfs for
     file descriptor closing in *note subprocess: c1. for better
     performance.

   - gh-67248(7): Sort the miscellaneous topics in Cmd.do_help()

   - gh-92210(8): Port ‘socket.__init__’ to Argument Clinic.  Patch by
     Cinder.

   - gh-80010(9): Add support for generalized ISO 8601 parsing to *note
     datetime.datetime.fromisoformat(): 5bc, *note
     datetime.date.fromisoformat(): 5ba. and *note
     datetime.time.fromisoformat(): 5bb.  Patch by Paul Ganssle.

   - gh-92118(10): Fix a 3.11 regression in *note contextmanager():
     119a, which caused it to propagate exceptions with incorrect
     tracebacks.

   - gh-90887(11): Adding ‘COPYFILE_STAT’, ‘COPYFILE_ACL’ and
     ‘COPYFILE_XATTR’ constants for ‘os.fcopyfile()’ available in macOs.

   - gh-91215(12): For *note @dataclass: 1af, add 'weakref_slot'.  The
     new parameter defaults to ‘False’.  If true, and if ‘slots=True’,
     add a slot named ‘"__weakref__"’, which will allow instances to be
     weakref'd.  Contributed by Eric V. Smith

   - gh-85984(13): New function os.login_tty() for Unix.

   - gh-92128(14): Add *note __class_getitem__(): 6df. to *note
     logging.LoggerAdapter: 1288. and *note logging.StreamHandler: 1190,
     allowing them to be parameterized at runtime.  Patch by Alex
     Waygood.

   - gh-92049(15): Forbid pickling constants ‘re._constants.SUCCESS’
     etc.  Previously, pickling did not fail, but the result could not
     be unpickled.

   - gh-92062(16): *note inspect.Parameter: 1b4. now raises *note
     ValueError: 1e7. if ‘name’ is a keyword, in addition to the
     existing check that it is an identifier.

   - gh-87390(17): Add an ‘__unpacked__’ attribute to *note
     types.GenericAlias: 78f.  Patch by Jelle Zijlstra.

   - gh-88089(18): Add support for generic *note typing.NamedTuple: 291.

   - gh-91996(19): New http.HTTPMethod enum to represent all the
     available HTTP request methods in a convenient way

   - gh-91984(20): Modified test strings in test_argparse.py to not
     contain trailing spaces before end of line.

   - gh-91952(21): Add ‘encoding="locale"’ support to
     ‘TextIOWrapper.reconfigure()’.

   - gh-91954(22): Add 'encoding' and 'errors' arguments to *note
     subprocess.getoutput(): 1700. and *note
     subprocess.getstatusoutput(): f65.

   - bpo-47029(23): Always close the read end of the pipe used by *note
     multiprocessing.Queue: 1701. 'after' the last write of buffered
     data to the write end of the pipe to avoid *note BrokenPipeError:
     fff. at garbage collection and at *note
     multiprocessing.Queue.close(): 1702. calls.  Patch by Géry Ogam.

   - gh-91928(24): Add ‘datetime.UTC’ alias for ‘datetime.timezone.utc’.

     Patch by Kabir Kwatra.

   - gh-68966(25): The ‘mailcap’ module is now deprecated and will be
     removed in Python 3.13.  See PEP 594(26) for the rationale and the
     *note mimetypes: 82. module for an alternative.  Patch by Victor
     Stinner.

   - gh-91401(27): Provide a way to disable *note subprocess: c1. use of
     ‘vfork()’ just in case it is ever needed and document the existing
     mechanism for ‘posix_spawn()’.

   - gh-64783(28): Fix *note signal.NSIG: 1703. value on FreeBSD to
     accept signal numbers greater than 32, like ‘signal.SIGRTMIN’ and
     ‘signal.SIGRTMAX’.  Patch by Victor Stinner.

   - gh-91910(29): Add missing f prefix to f-strings in error messages
     from the *note multiprocessing: 86. and *note asyncio: 8. modules.

   - gh-91860(30): Add *note typing.dataclass_transform(): 47b,
     implementing PEP 681(31).  Patch by Jelle Zijlstra.

   - gh-91832(32): Add ‘required’ attribute to *note argparse.Action:
     1704. repr output.

   - gh-91827(33): In the *note tkinter: d9. module add method
     ‘info_patchlevel()’ which returns the exact version of the Tcl
     library as a named tuple similar to *note sys.version_info: 645.

   - gh-84461(34): Add *note -enable-wasm-pthreads: 1705. to enable
     pthreads support for WASM builds.  ‘Emscripten/node’ no longer has
     threading enabled by default.  Include additional file systems.

   - gh-91821(35): Fix unstable ‘test_from_tuple’ test in
     ‘test_decimal.py’.

   - gh-91217(36): Deprecate the xdrlib module.

   - gh-91217(37): Deprecate the uu module.

   - gh-91760(38): More strict rules will be applied for numerical group
     references and group names in regular expressions.  For now, a
     deprecation warning is emitted for group references and group names
     which will be errors in future Python versions.

   - gh-84461(39): Add provisional *note sys._emscripten_info: 1706.
     named tuple with build-time and run-time information about
     Emscripten platform.

   - gh-90623(40): *note signal.raise_signal(): 1707. and *note
     os.kill(): 12f4. now check immediately for pending signals.  Patch
     by Victor Stinner.

   - gh-91734(41): Fix OSS audio support on Solaris.

   - gh-90633(42): Include the passed value in the exception thrown by
     *note typing.assert_never(): 64c.  Patch by Jelle Zijlstra.

   - gh-91700(43): Compilation of regular expression containing a
     conditional expression ‘(?(group)...)’ now raises an appropriate
     ‘re.error’ if the group number refers to not defined group.
     Previously an internal RuntimeError was raised.

   - gh-91231(44): Add an optional keyword 'shutdown_timeout' parameter
     to the ‘multiprocessing.BaseManager’ constructor.  Kill the process
     if terminate() takes longer than the timeout.  Patch by Victor
     Stinner.

   - gh-91621(45): Fix *note typing.get_type_hints(): 657. for *note
     collections.abc.Callable: 78e.  Patch by Shantanu Jain.

   - gh-90568(46): Parsing ‘\N’ escapes of Unicode Named Character
     Sequences in a *note regular expression: a7. raises now ‘re.error’
     instead of ‘TypeError’.

   - gh-91670(47): Remove deprecated ‘SO’ config variable in *note
     sysconfig: c5.

   - gh-91217(48): Deprecate the telnetlib module.

   - gh-91217(49): Deprecate the sunau module.

   - gh-91217(50): Deprecate the spwd module.

   - gh-91217(51): Deprecate the sndhdr module, as well as inline needed
     functionality for ‘email.mime.MIMEAudio’.

   - gh-91616(52): *note re: a7. module, fix *note fullmatch(): 1708.
     mismatch when using Atomic Grouping or Possessive Quantifiers.

   - gh-91217(53): Deprecate the 'pipes' module.

   - gh-91217(54): Deprecate the ossaudiodev module.

   - bpo-47256(55): *note re: a7. module, limit the maximum capturing
     group to 1,073,741,823 in 64-bit build, this increases the depth of
     backtracking.

   - gh-91217(56): Deprecate the nis module.

   - gh-91595(57): Fix the comparison of character and integer inside
     ‘Tools.gdb.libpython.write_repr()’.  Patch by Yu Liu.

   - gh-74166(58): Add option to raise all errors from *note
     create_connection(): 618. in an *note ExceptionGroup: 19c. when it
     fails to create a connection.  The default remains to raise only
     the last error that had occurred when multiple addresses were
     tried.

   - gh-91487(59): Optimize asyncio UDP speed, over 100 times faster
     when transferring a large file.

   - gh-91575(60): Update case-insensitive matching in the *note re: a7.
     module to the latest Unicode version.

   - gh-90622(61): In ‘concurrent.futures.process.ProcessPoolExecutor’
     disallow the "fork" multiprocessing start method when the new
     ‘max_tasks_per_child’ feature is used as the mix of threads+fork
     can hang the child processes.  Default to using the safe "spawn"
     start method in that circumstance if no ‘mp_context’ was supplied.

   - gh-89022(62): In *note sqlite3: ba, ‘SQLITE_MISUSE’ result codes
     are now mapped to *note InterfaceError: 623. instead of *note
     ProgrammingError: 49a.  Also, more accurate exceptions are raised
     when binding parameters fail.  Patch by Erlend E. Aasland.

   - gh-91526(63): Stop calling ‘os.device_encoding(file.fileno())’ in
     ‘TextIOWrapper’.  It was complex, never documented, and didn't work
     for most cases.  (Patch by Inada Naoki.)

   - gh-88116(64): Change the frame-related functions in the *note
     inspect: 72. module to return a regular object (that is backwards
     compatible with the old tuple-like interface) that include the
     extended PEP 657(65) position information (end line number, column
     and end column).  The affected functions are: *note
     inspect.getframeinfo(): 5f5, *note inspect.getouterframes(): 5f6,
     *note inspect.getinnerframes(): 5f7, *note inspect.stack(): 5f8.
     and *note inspect.trace(): 5f9.  Patch by Pablo Galindo.

   - gh-69093(66): Add indexing and slicing support to *note
     sqlite3.Blob: 628.  Patch by Aviv Palivoda and Erlend E. Aasland.

   - gh-69093(67): Add *note context manager: 576. support to *note
     sqlite3.Blob: 628.  Patch by Aviv Palivoda and Erlend E. Aasland.

   - gh-91217(68): Deprecate nntplib.

   - gh-91217(69): Deprecate msilib.

   - gh-91404(70): Improve the performance of *note re: a7. matching by
     using computed gotos (or "threaded code") on supported platforms
     and removing expensive pointer indirections.

   - gh-91217(71): Deprecate the imghdr module.

   - gh-91217(72): Deprecate the crypt module.

   - gh-91276(73): Make space for longer opcodes in *note dis: 30.
     output.

   - bpo-47000(74): Make ‘TextIOWrapper’ uses locale encoding when
     ‘encoding="locale"’ is specified even in UTF-8 mode.

   - gh-91230(75): *note warnings.catch_warnings(): 52a. now accepts
     arguments for *note warnings.simplefilter(): 666, providing a more
     concise way to locally ignore warnings or convert them to errors.

   - gh-91217(76): Deprecate the chunk module.

   - Add the ‘TCP_CONNECTION_INFO’ option (available on macOS) to *note
     socket: b8.

   - bpo-47260(77): Fix ‘os.closerange()’ potentially being a no-op in a
     Linux seccomp sandbox.

   - bpo-47087(78): Implement ‘typing.Required’ and ‘typing.NotRequired’
     ( PEP 655(79)).  Patch by David Foster and Jelle Zijlstra.

   - bpo-47061(80): Deprecate cgi and cgitb.

   - bpo-47061(81): Deprecate audioop.

   - bpo-47000(82): Add *note locale.getencoding(): 2bc. to get the
     current locale encoding.  It is similar to
     ‘locale.getpreferredencoding(False)’ but ignores the *note Python
     UTF-8 Mode: 5fc.

   - bpo-42012(83): Add *note wsgiref.types: 104, containing
     WSGI-specific types for static type checking.

   - bpo-47227(84): Suppress expression chaining for more *note re: a7.
     parsing errors.

   - bpo-47211(85): Remove undocumented and never working function
     ‘re.template()’ and flag ‘re.TEMPLATE’.  This was later reverted in
     3.11.0b2 and deprecated instead.

   - bpo-47135(86): *note decimal.localcontext(): 1709. now accepts
     context attributes via keyword arguments

   - bpo-43323(87): Fix errors in the *note email: 32. module if the
     charset itself contains undecodable/unencodable characters.

   - bpo-46841(88): Disassembly of quickened code.

   - bpo-46681(89): Forward gzip.compress() compresslevel to zlib.

   - bpo-45100(90): Add *note typing.get_overloads(): 653. and *note
     typing.clear_overloads(): 654.  Patch by Jelle Zijlstra.

   - bpo-44807(91): *note typing.Protocol: 249. no longer silently
     replaces ‘__init__()’ methods defined on subclasses.  Patch by
     Adrian Garcia Badaracco.

   - bpo-46787(92): Fix *note concurrent.futures.ProcessPoolExecutor:
     893. exception memory leak

   - bpo-46720(93): Add support for path-like objects to *note
     multiprocessing.set_executable(): 170a. for Windows to be on a par
     with Unix-like systems.  Patch by Géry Ogam.

   - bpo-46696(94): Add ‘SO_INCOMING_CPU’ constant to *note socket: b8.

   - bpo-46053(95): Fix OSS audio support on NetBSD.

   - bpo-45639(96): ‘image/avif’ and ‘image/webp’ were added to *note
     mimetypes: 82.

   - bpo-46285(97): Add command-line option ‘-p’/‘--protocol’ to module
     *note http.server: 68. which specifies the HTTP version to which
     the server is conformant (HTTP/1.1 conformant servers can now be
     run from the command-line interface of module *note http.server:
     68.).  Patch by Géry Ogam.

   - bpo-44791(98): Accept ellipsis as the last argument of *note
     typing.Concatenate: 768.

   - bpo-46547(99): Remove variables leaking into ‘pydoc.Helper’ class
     namespace.

   - bpo-46415(100): Fix ipaddress.ip_{address,interface,network}
     raising TypeError instead of ValueError if given invalid tuple as
     address parameter.

   - bpo-46075(101): ‘CookieJar’ with ‘DefaultCookiePolicy’ now can
     process cookies from localhost with domain=localhost explicitly
     specified in Set-Cookie header.

   - bpo-45995(102): Add a "z" option to the string formatting
     specification that coerces negative zero floating-point values to
     positive zero after rounding to the format precision.  Contributed
     by John Belmonte.

   - bpo-26175(103): Fully implement the *note io.BufferedIOBase: 63a.
     or *note io.TextIOBase: 63b. interface for *note
     tempfile.SpooledTemporaryFile: 639. objects.  This lets them work
     correctly with higher-level layers (like compression modules).
     Patch by Carey Metcalfe.

   - bpo-45138(104): Fix a regression in the *note sqlite3: ba. trace
     callback where bound parameters were not expanded in the passed
     statement string.  The regression was introduced in Python 3.10 by
     bpo-40318(105).  Patch by Erlend E. Aasland.

   - bpo-44863(106): Allow *note TypedDict: 146. subclasses to also
     include *note Generic: 150c. as a base class in class based syntax.
     Thereby allowing the user to define a generic ‘TypedDict’, just
     like a user-defined generic but with ‘TypedDict’ semantics.

   - bpo-44587(107): Fix BooleanOptionalAction to not automatically add
     a default string.  If a default string is desired, use a formatter
     to add it.

   - bpo-43827(108): All positional-or-keyword parameters to
     ‘ABCMeta.__new__’ are now positional-only to avoid conflicts with
     keyword arguments to be passed to ‘__init_subclass__()’.

   - bpo-43218(109): Prevent creation of a venv whose path contains the
     PATH separator.  This could affect the usage of the activate
     script.  Patch by Dustin Rodrigues.

   - bpo-38435(110): Add a ‘process_group’ parameter to *note
     subprocess.Popen: 17d. to help move more things off of the unsafe
     ‘preexec_fn’ parameter.

   - bpo-42066(111): Fix cookies getting sorted in
     ‘CookieJar.__iter__()’ which is an extra behavior and not mentioned
     in RFC 2965 or Netscape cookie protocol.  Now the cookies in
     ‘CookieJar’ follows the order of the ‘Set-Cookie’ header.  Patch by
     Iman Kermani.

   - bpo-40617(112): Add *note create_window_function(): 626. to *note
     sqlite3.Connection: 22a. for creating aggregate window functions.
     Patch by Erlend E. Aasland.

   - bpo-40676(113): Convert *note csv: 21. to use Argument Clinic for
     *note csv.field_size_limit(): 170b, *note csv.get_dialect(): 170c,
     *note csv.unregister_dialect(): 170d. and *note
     csv.list_dialects(): 170e.

   - bpo-39716(114): Raise an ‘ArgumentError’ when the same subparser
     name is added twice to an ‘argparse.ArgumentParser’.  This is
     consistent with the (default) behavior when the same option string
     is added twice to an ‘ArgumentParser’.

   - bpo-36073(115): Raise *note ProgrammingError: 49a. instead of
     segfaulting on recursive usage of cursors in *note sqlite3: ba.
     converters.  Patch by Sergey Fedoseev.

   - bpo-34975(116): Adds a ‘start_tls()’ method to ‘StreamWriter’,
     which upgrades the connection with TLS using the given *note
     SSLContext: 276.

   - bpo-22276(117): *note Path: 20e. methods *note glob(): 212. and
     *note rglob(): 213. return only directories if 'pattern' ends with
     a pathname components separator (‘/’ or *note sep: 610.).  Patch by
     Eisuke Kawashima.

   - bpo-24905(118): Add *note blobopen(): 627. to *note
     sqlite3.Connection: 22a.  *note sqlite3.Blob: 628. allows
     incremental I/O operations on blobs.  Patch by Aviv Palivoda and
     Erlend E. Aasland.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/87901

   (2) https://github.com/python/cpython/issues/90997

   (3) https://github.com/python/cpython/issues/92332

   (4) https://github.com/python/cpython/issues/92356

   (5) https://github.com/python/cpython/issues/90997

   (6) https://github.com/python/cpython/issues/92301

   (7) https://github.com/python/cpython/issues/67248

   (8) https://github.com/python/cpython/issues/92210

   (9) https://github.com/python/cpython/issues/80010

   (10) https://github.com/python/cpython/issues/92118

   (11) https://github.com/python/cpython/issues/90887

   (12) https://github.com/python/cpython/issues/91215

   (13) https://github.com/python/cpython/issues/85984

   (14) https://github.com/python/cpython/issues/92128

   (15) https://github.com/python/cpython/issues/92049

   (16) https://github.com/python/cpython/issues/92062

   (17) https://github.com/python/cpython/issues/87390

   (18) https://github.com/python/cpython/issues/88089

   (19) https://github.com/python/cpython/issues/91996

   (20) https://github.com/python/cpython/issues/91984

   (21) https://github.com/python/cpython/issues/91952

   (22) https://github.com/python/cpython/issues/91954

   (23) https://bugs.python.org/issue?@action=redirect&bpo=47029

   (24) https://github.com/python/cpython/issues/91928

   (25) https://github.com/python/cpython/issues/68966

   (26) https://peps.python.org/pep-0594/

   (27) https://github.com/python/cpython/issues/91401

   (28) https://github.com/python/cpython/issues/64783

   (29) https://github.com/python/cpython/issues/91910

   (30) https://github.com/python/cpython/issues/91860

   (31) https://peps.python.org/pep-0681/

   (32) https://github.com/python/cpython/issues/91832

   (33) https://github.com/python/cpython/issues/91827

   (34) https://github.com/python/cpython/issues/84461

   (35) https://github.com/python/cpython/issues/91821

   (36) https://github.com/python/cpython/issues/91217

   (37) https://github.com/python/cpython/issues/91217

   (38) https://github.com/python/cpython/issues/91760

   (39) https://github.com/python/cpython/issues/84461

   (40) https://github.com/python/cpython/issues/90623

   (41) https://github.com/python/cpython/issues/91734

   (42) https://github.com/python/cpython/issues/90633

   (43) https://github.com/python/cpython/issues/91700

   (44) https://github.com/python/cpython/issues/91231

   (45) https://github.com/python/cpython/issues/91621

   (46) https://github.com/python/cpython/issues/90568

   (47) https://github.com/python/cpython/issues/91670

   (48) https://github.com/python/cpython/issues/91217

   (49) https://github.com/python/cpython/issues/91217

   (50) https://github.com/python/cpython/issues/91217

   (51) https://github.com/python/cpython/issues/91217

   (52) https://github.com/python/cpython/issues/91616

   (53) https://github.com/python/cpython/issues/91217

   (54) https://github.com/python/cpython/issues/91217

   (55) https://bugs.python.org/issue?@action=redirect&bpo=47256

   (56) https://github.com/python/cpython/issues/91217

   (57) https://github.com/python/cpython/issues/91595

   (58) https://github.com/python/cpython/issues/74166

   (59) https://github.com/python/cpython/issues/91487

   (60) https://github.com/python/cpython/issues/91575

   (61) https://github.com/python/cpython/issues/90622

   (62) https://github.com/python/cpython/issues/89022

   (63) https://github.com/python/cpython/issues/91526

   (64) https://github.com/python/cpython/issues/88116

   (65) https://peps.python.org/pep-0657/

   (66) https://github.com/python/cpython/issues/69093

   (67) https://github.com/python/cpython/issues/69093

   (68) https://github.com/python/cpython/issues/91217

   (69) https://github.com/python/cpython/issues/91217

   (70) https://github.com/python/cpython/issues/91404

   (71) https://github.com/python/cpython/issues/91217

   (72) https://github.com/python/cpython/issues/91217

   (73) https://github.com/python/cpython/issues/91276

   (74) https://bugs.python.org/issue?@action=redirect&bpo=47000

   (75) https://github.com/python/cpython/issues/91230

   (76) https://github.com/python/cpython/issues/91217

   (77) https://bugs.python.org/issue?@action=redirect&bpo=47260

   (78) https://bugs.python.org/issue?@action=redirect&bpo=47087

   (79) https://peps.python.org/pep-0655/

   (80) https://bugs.python.org/issue?@action=redirect&bpo=47061

   (81) https://bugs.python.org/issue?@action=redirect&bpo=47061

   (82) https://bugs.python.org/issue?@action=redirect&bpo=47000

   (83) https://bugs.python.org/issue?@action=redirect&bpo=42012

   (84) https://bugs.python.org/issue?@action=redirect&bpo=47227

   (85) https://bugs.python.org/issue?@action=redirect&bpo=47211

   (86) https://bugs.python.org/issue?@action=redirect&bpo=47135

   (87) https://bugs.python.org/issue?@action=redirect&bpo=43323

   (88) https://bugs.python.org/issue?@action=redirect&bpo=46841

   (89) https://bugs.python.org/issue?@action=redirect&bpo=46681

   (90) https://bugs.python.org/issue?@action=redirect&bpo=45100

   (91) https://bugs.python.org/issue?@action=redirect&bpo=44807

   (92) https://bugs.python.org/issue?@action=redirect&bpo=46787

   (93) https://bugs.python.org/issue?@action=redirect&bpo=46720

   (94) https://bugs.python.org/issue?@action=redirect&bpo=46696

   (95) https://bugs.python.org/issue?@action=redirect&bpo=46053

   (96) https://bugs.python.org/issue?@action=redirect&bpo=45639

   (97) https://bugs.python.org/issue?@action=redirect&bpo=46285

   (98) https://bugs.python.org/issue?@action=redirect&bpo=44791

   (99) https://bugs.python.org/issue?@action=redirect&bpo=46547

   (100) https://bugs.python.org/issue?@action=redirect&bpo=46415

   (101) https://bugs.python.org/issue?@action=redirect&bpo=46075

   (102) https://bugs.python.org/issue?@action=redirect&bpo=45995

   (103) https://bugs.python.org/issue?@action=redirect&bpo=26175

   (104) https://bugs.python.org/issue?@action=redirect&bpo=45138

   (105) https://bugs.python.org/issue?@action=redirect&bpo=40318

   (106) https://bugs.python.org/issue?@action=redirect&bpo=44863

   (107) https://bugs.python.org/issue?@action=redirect&bpo=44587

   (108) https://bugs.python.org/issue?@action=redirect&bpo=43827

   (109) https://bugs.python.org/issue?@action=redirect&bpo=43218

   (110) https://bugs.python.org/issue?@action=redirect&bpo=38435

   (111) https://bugs.python.org/issue?@action=redirect&bpo=42066

   (112) https://bugs.python.org/issue?@action=redirect&bpo=40617

   (113) https://bugs.python.org/issue?@action=redirect&bpo=40676

   (114) https://bugs.python.org/issue?@action=redirect&bpo=39716

   (115) https://bugs.python.org/issue?@action=redirect&bpo=36073

   (116) https://bugs.python.org/issue?@action=redirect&bpo=34975

   (117) https://bugs.python.org/issue?@action=redirect&bpo=22276

   (118) https://bugs.python.org/issue?@action=redirect&bpo=24905


File: python.info,  Node: Documentation<16>,  Next: Tests<19>,  Prev: Library<21>,  Up: Python 3 11 0 beta 1

1.23.22.4 Documentation
.......................

   - gh-91888(1): Add a new ‘gh’ role to the documentation to link to
     GitHub issues.

   - gh-91783(2): Document security issues concerning the use of the
     function *note shutil.unpack_archive(): 412.

   - gh-91547(3): Remove "Undocumented modules" page.

   - gh-91298(4): In ‘importlib.resources.abc’, refined the
     documentation of the Traversable Protocol, applying changes from
     importlib_resources 5.7.1.

   - bpo-44347(5): Clarify the meaning of 'dirs_exist_ok', a kwarg of
     *note shutil.copytree(): 9cd.

   - bpo-36329(6): Remove 'make -C Doc serve' in favour of 'make -C Doc
     htmlview'

   - bpo-47189(7): Add a What's New in Python 3.11 entry for the Faster
     CPython project.  Documentation by Ken Jin and Kumar Aditya.

   - bpo-38668(8): Update the introduction to documentation for *note
     os.path: 92. to remove warnings that became irrelevant after the
     implementations of PEP 383(9) and PEP 529(10).

   - bpo-47115(11): The documentation now lists which members of C
     structs are part of the *note Limited API/Stable ABI: 4f9.

   - bpo-46962(12): All docstrings in code snippets are now wrapped into
     *note PyDoc_STR: 1710. to follow the guideline of PEP 7's
     Documentation Strings paragraph(13).  Patch by Oleg Iarygin.

   - bpo-26792(14): Improve the docstrings of *note runpy.run_module():
     1711. and *note runpy.run_path(): 164.  Original patch by Andrew
     Brezovsky.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/91888

   (2) https://github.com/python/cpython/issues/91783

   (3) https://github.com/python/cpython/issues/91547

   (4) https://github.com/python/cpython/issues/91298

   (5) https://bugs.python.org/issue?@action=redirect&bpo=44347

   (6) https://bugs.python.org/issue?@action=redirect&bpo=36329

   (7) https://bugs.python.org/issue?@action=redirect&bpo=47189

   (8) https://bugs.python.org/issue?@action=redirect&bpo=38668

   (9) https://peps.python.org/pep-0383/

   (10) https://peps.python.org/pep-0529/

   (11) https://bugs.python.org/issue?@action=redirect&bpo=47115

   (12) https://bugs.python.org/issue?@action=redirect&bpo=46962

   (13) https://www.python.org/dev/peps/pep-0007/#documentation-strings

   (14) https://bugs.python.org/issue?@action=redirect&bpo=26792


File: python.info,  Node: Tests<19>,  Next: Build<21>,  Prev: Documentation<16>,  Up: Python 3 11 0 beta 1

1.23.22.5 Tests
...............

   - gh-92169(1): Use ‘warnings_helper.import_deprecated()’ to import
     deprecated modules uniformly in tests.  Patch by Hugo van Kemenade.

   - gh-84461(2): When multiprocessing is enabled, libregrtest can now
     use a Python executable other than ‘sys.executable’ via the
     ‘--python’ flag.

   - gh-91904(3): Fix initialization of ‘PYTHONREGRTEST_UNICODE_GUARD’
     which prevented running regression tests on non-UTF-8 locale.

   - gh-91752(4): Added @requires_zlib to
     test.test_tools.test_freeze.TestFreeze.

   - gh-91607(5): Fix ‘test_concurrent_futures’ to test the correct
     multiprocessing start method context in several cases where the
     test logic mixed this up.

   - bpo-40280(6): Threading tests are now skipped on WASM targets
     without pthread support.

   - bpo-47109(7): Test for ‘ctypes.macholib.dyld’,
     ‘ctypes.macholib.dylib’, and ‘ctypes.macholib.framework’ are
     brought from manual pre-*note unittest: ef. times to ‘ctypes.test’
     location and structure.  Patch by Oleg Iarygin.

   - bpo-29890(8): Add tests for *note ipaddress.IPv4Interface: 1713.
     and *note ipaddress.IPv6Interface: 1714. construction with tuple
     arguments.  Original patch and tests by louisom.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/92169

   (2) https://github.com/python/cpython/issues/84461

   (3) https://github.com/python/cpython/issues/91904

   (4) https://github.com/python/cpython/issues/91752

   (5) https://github.com/python/cpython/issues/91607

   (6) https://bugs.python.org/issue?@action=redirect&bpo=40280

   (7) https://bugs.python.org/issue?@action=redirect&bpo=47109

   (8) https://bugs.python.org/issue?@action=redirect&bpo=29890


File: python.info,  Node: Build<21>,  Next: Windows<18>,  Prev: Tests<19>,  Up: Python 3 11 0 beta 1

1.23.22.6 Build
...............

   - gh-89452(1): gdbm-compat is now preferred over ndbm if both are
     available on the system.  This allows avoiding the problematic
     ndbm.h on macOS.

   - gh-91731(2): Python is now built with ‘-std=c11’ compiler option,
     rather than ‘-std=c99’.  Patch by Victor Stinner.

   - bpo-47152(3): Add script and make target for generating
     ‘sre_constants.h’.

   - bpo-47103(4): Windows ‘PGInstrument’ builds now copy a required DLL
     into the output directory, making it easier to run the profile
     stage of a PGO build.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/89452

   (2) https://github.com/python/cpython/issues/91731

   (3) https://bugs.python.org/issue?@action=redirect&bpo=47152

   (4) https://bugs.python.org/issue?@action=redirect&bpo=47103


File: python.info,  Node: Windows<18>,  Next: macOS<14>,  Prev: Build<21>,  Up: Python 3 11 0 beta 1

1.23.22.7 Windows
.................

   - bpo-46907(1): Update Windows installer to use SQLite 3.38.3.

   - bpo-47239(2): Fixed -list and -list-paths output for *note Python
     Launcher for Windows: 562. when used in an active virtual
     environment.

   - bpo-46907(3): Update Windows installer to use SQLite 3.38.2.

   - bpo-46785(4): Fix race condition between *note os.stat(): 448. and
     unlinking a file on Windows, by using errors codes returned by
     ‘FindFirstFileW()’ when appropriate in ‘win32_xstat_impl’.

   - bpo-40859(5): Update Windows build to use xz-5.2.5

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46907

   (2) https://bugs.python.org/issue?@action=redirect&bpo=47239

   (3) https://bugs.python.org/issue?@action=redirect&bpo=46907

   (4) https://bugs.python.org/issue?@action=redirect&bpo=46785

   (5) https://bugs.python.org/issue?@action=redirect&bpo=40859


File: python.info,  Node: macOS<14>,  Next: Tools/Demos<11>,  Prev: Windows<18>,  Up: Python 3 11 0 beta 1

1.23.22.8 macOS
...............

   - bpo-46907(1): Update macOS installer to SQLite 3.38.4.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46907


File: python.info,  Node: Tools/Demos<11>,  Next: C API<20>,  Prev: macOS<14>,  Up: Python 3 11 0 beta 1

1.23.22.9 Tools/Demos
.....................

   - gh-91583(1): Fix regression in the code generated by Argument
     Clinic for functions with the ‘defining_class’ parameter.

   - gh-91575(2): Add script ‘Tools/scripts/generate_re_casefix.py’ and
     the make target ‘regen-re’ for generating additional data for
     case-insensitive matching according to the current Unicode version.

   - gh-91551(3): Remove the ancient Pynche color editor.  It has moved
     to ‘https://gitlab.com/warsaw/pynche’

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/91583

   (2) https://github.com/python/cpython/issues/91575

   (3) https://github.com/python/cpython/issues/91551


File: python.info,  Node: C API<20>,  Prev: Tools/Demos<11>,  Up: Python 3 11 0 beta 1

1.23.22.10 C API
................

   - gh-88279(1): Deprecate the C functions: ‘PySys_SetArgv()’,
     ‘PySys_SetArgvEx()’, ‘PySys_SetPath()’.  Patch by Victor Stinner.

   - gh-92154(2): Added the *note PyCode_GetCode(): 71c. function.  This
     function does the equivalent of the Python code
     ‘getattr(code_object, 'co_code')’.

   - gh-92173(3): Fix the ‘closure’ argument to *note
     PyEval_EvalCodeEx(): 166b.

   - gh-91320(4): Fix C++ compiler warnings about "old-style cast" (‘g++
     -Wold-style-cast’) in the Python C API. Use C++
     ‘reinterpret_cast<>’ and ‘static_cast<>’ casts when the Python C
     API is used in C++.  Patch by Victor Stinner.

   - gh-80527(5): Mark functions as deprecated by PEP 623(6):
     ‘PyUnicode_AS_DATA()’, ‘PyUnicode_AS_UNICODE()’,
     ‘PyUnicode_GET_DATA_SIZE()’, ‘PyUnicode_GET_SIZE()’.  Patch by
     Victor Stinner.

   - gh-91768(7): *note Py_REFCNT(): 84e, *note Py_TYPE(): 724, *note
     Py_SIZE(): 726. and *note Py_IS_TYPE(): 171a. functions argument
     type is now ‘PyObject*’, rather than ‘const PyObject*’.  Patch by
     Victor Stinner.

   - gh-91020(8): Add ‘PyBytes_Type.tp_alloc’ to initialize
     ‘PyBytesObject.ob_shash’ for bytes subclasses.

   - bpo-40421(9): Add ‘PyFrame_GetLasti’ C-API function to access frame
     object's ‘f_lasti’ attribute safely from C code.

   - bpo-35134(10): Remove the ‘Include/code.h’ header file.  C
     extensions should only include the main ‘<Python.h>’ header file.
     Patch by Victor Stinner.

   - bpo-47169(11): *note PyOS_CheckStack(): 171b. is now exported in
     the Stable ABI on Windows.

   - bpo-47169(12): ‘PyThread_get_thread_native_id()’ is excluded from
     the stable ABI on platforms where it doesn't exist (like Solaris).

   - bpo-46343(13): Added *note PyErr_GetHandledException(): 713. and
     *note PyErr_SetHandledException(): 714. as simpler alternatives to
     *note PyErr_GetExcInfo(): 716. and *note PyErr_SetExcInfo(): 715.

     They are included in the stable ABI.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/88279

   (2) https://github.com/python/cpython/issues/92154

   (3) https://github.com/python/cpython/issues/92173

   (4) https://github.com/python/cpython/issues/91320

   (5) https://github.com/python/cpython/issues/80527

   (6) https://peps.python.org/pep-0623/

   (7) https://github.com/python/cpython/issues/91768

   (8) https://github.com/python/cpython/issues/91020

   (9) https://bugs.python.org/issue?@action=redirect&bpo=40421

   (10) https://bugs.python.org/issue?@action=redirect&bpo=35134

   (11) https://bugs.python.org/issue?@action=redirect&bpo=47169

   (12) https://bugs.python.org/issue?@action=redirect&bpo=47169

   (13) https://bugs.python.org/issue?@action=redirect&bpo=46343


File: python.info,  Node: Python 3 11 0 alpha 7,  Next: Python 3 11 0 alpha 6,  Prev: Python 3 11 0 beta 1,  Up: Changelog（更動日誌）

1.23.23 Python 3.11.0 alpha 7
-----------------------------

'Release date: 2022-04-05'

* Menu:

* Core and Builtins: Core and Builtins<23>.
* Library: Library<22>.
* Documentation: Documentation<17>.
* Tests: Tests<20>.
* Build: Build<22>.
* Windows: Windows<19>.
* macOS: macOS<15>.
* Tools/Demos: Tools/Demos<12>.
* C API: C API<21>.


File: python.info,  Node: Core and Builtins<23>,  Next: Library<22>,  Up: Python 3 11 0 alpha 7

1.23.23.1 Core and Builtins
...........................

   - bpo-47212(1): Raise *note IndentationError: 74c. instead of *note
     SyntaxError: 173. for a bare ‘except’ with no following indent.
     Improve *note SyntaxError: 173. locations for an un-parenthesized
     generator used as arguments.  Patch by Matthieu Dartiailh.

   - bpo-47186(2): Replace ‘JUMP_IF_NOT_EG_MATCH’ by *note
     CHECK_EG_MATCH: 6a5. + jump.

   - bpo-47176(3): Emscripten builds cannot handle signals in the usual
     way due to platform limitations.  Python can now handle signals.
     To use, set Module.Py_EmscriptenSignalBuffer to be a single byte
     SharedArrayBuffer and set Py_EMSCRIPTEN_SIGNAL_HANDLING to 1.
     Writing a number into the SharedArrayBuffer will cause the
     corresponding signal to be raised into the Python thread.

   - bpo-47186(4): Replace ‘JUMP_IF_NOT_EXC_MATCH’ by *note
     CHECK_EXC_MATCH: 6af. + jump.

   - bpo-47120(5): Replace the absolute jump opcode *note
     JUMP_NO_INTERRUPT: 171e. by the relative *note
     JUMP_BACKWARD_NO_INTERRUPT: 6a2.

   - bpo-46841(6): Avoid unnecessary allocations when comparing code
     objects.

   - bpo-47182(7): Fix a crash when using a named unicode character like
     ‘"\N{digit nine}"’ after the main interpreter has been initialized
     a second time.

   - bpo-47162(8): WebAssembly cannot deal with bad function pointer
     casts (different count or types of arguments).  Python can now use
     call trampolines to mitigate the problem.  Define
     ‘PY_CALL_TRAMPOLINE’ to enable call trampolines.

   - bpo-46775(9): Some Windows system error codes(>= 10000) are now
     mapped into the correct errno and may now raise a subclass of *note
     OSError: 350.  Patch by Donghee Na.

   - bpo-47129(10): Improve error messages in f-string syntax errors
     concerning empty expressions.

   - bpo-47117(11): Fix a crash if we fail to decode characters in
     interactive mode if the tokenizer buffers are uninitialized.  Patch
     by Pablo Galindo.

   - bpo-47127(12): Speed up calls to c functions with keyword arguments
     by 25% with specialization.  Patch by Kumar Aditya.

   - bpo-47120(13): Replaced ‘JUMP_ABSOLUTE’ by the relative jump *note
     JUMP_BACKWARD: 6b0.

   - bpo-42197(14): ‘PyFrame_FastToLocalsWithError()’ and
     ‘PyFrame_LocalsToFast()’ are no longer called during profiling nor
     tracing.  C code can access the ‘f_locals’ attribute of *note
     PyFrameObject: 72d. by calling *note PyFrame_GetLocals(): 35f.

   - bpo-47070(15): Improve performance of ‘array_inplace_repeat’ by
     reducing the number of invocations of ‘memcpy’.  Refactor the
     ‘repeat’ and inplace ‘repeat’ methods of ‘array’, ‘bytes’,
     ‘bytearray’ and ‘unicodeobject’ to use the common
     ‘_PyBytes_Repeat’.

   - bpo-47053(16): Reduce de-optimization in the specialized
     ‘BINARY_OP_INPLACE_ADD_UNICODE’ opcode.

   - bpo-47045(17): Remove the ‘f_state’ field from the
     _PyInterpreterFrame struct.  Add the ‘owner’ field to the
     _PyInterpreterFrame struct to make ownership explicit to simplify
     clearing and deallocing frames and generators.

   - bpo-46968(18): Check for the existence of the "sys/auxv.h" header
     in *note faulthandler: 4e. to avoid compilation problems in systems
     where this header doesn't exist.  Patch by Pablo Galindo

   - bpo-46329(19): Use low bit of ‘LOAD_GLOBAL’ to indicate whether to
     push a ‘NULL’ before the global.  Helps streamline the call
     sequence a bit.

   - bpo-46841(20): Quicken bytecode in-place by storing it as part of
     the corresponding ‘PyCodeObject’.

   - bpo-47012(21): Speed up iteration of *note bytes: 1a5. and *note
     bytearray: 4e3. by 30%.  Patch by Kumar Aditya.

   - bpo-47009(22): Improved the performance of ‘list.append()’ and list
     comprehensions by optimizing for the common case, where no resize
     is needed.  Patch by Dennis Sweeney.

   - bpo-47005(23): Improve performance of ‘bytearray_repeat’ and
     ‘bytearray_irepeat’ by reducing the number of invocations of
     ‘memcpy’.

   - bpo-46829(24): Deprecate passing a message into *note
     asyncio.Future.cancel(): 171f. and *note asyncio.Task.cancel():
     19d.

   - bpo-46993(25): Speed up *note bytearray: 4e3. creation from *note
     list: 5b6. and *note tuple: 322. by 40%.  Patch by Kumar Aditya.

   - bpo-39829(26): Removed the ‘__len__()’ call when initializing a
     list and moved initializing to ‘list_extend’.  Patch by Jeremiah
     Pascual.

   - bpo-46944(27): Speed up throwing exception in generator with *note
     METH_FASTCALL: 151b. calling convention.  Patch by Kumar Aditya.

   - bpo-46841(28): Modify *note STORE_SUBSCR: 1720. to use an inline
     cache entry (rather than its oparg) as an adaptive counter.

   - bpo-46841(29): Use inline caching for ‘PRECALL’ and *note CALL:
     6ab, and remove the internal machinery for managing the (now
     unused) non-inline caches.

   - bpo-46881(30): Statically allocate and initialize the latin1
     characters.

   - bpo-46838(31): Improve syntax errors for incorrect function
     definitions.  Patch by Pablo Galindo

   - bpo-43721(32): Fix docstrings of *note getter: 1550, *note setter:
     1551, and *note deleter: 1552. to clarify that they create a new
     copy of the property.

   - bpo-43224(33): Make grammar changes required for PEP 646.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=47212

   (2) https://bugs.python.org/issue?@action=redirect&bpo=47186

   (3) https://bugs.python.org/issue?@action=redirect&bpo=47176

   (4) https://bugs.python.org/issue?@action=redirect&bpo=47186

   (5) https://bugs.python.org/issue?@action=redirect&bpo=47120

   (6) https://bugs.python.org/issue?@action=redirect&bpo=46841

   (7) https://bugs.python.org/issue?@action=redirect&bpo=47182

   (8) https://bugs.python.org/issue?@action=redirect&bpo=47162

   (9) https://bugs.python.org/issue?@action=redirect&bpo=46775

   (10) https://bugs.python.org/issue?@action=redirect&bpo=47129

   (11) https://bugs.python.org/issue?@action=redirect&bpo=47117

   (12) https://bugs.python.org/issue?@action=redirect&bpo=47127

   (13) https://bugs.python.org/issue?@action=redirect&bpo=47120

   (14) https://bugs.python.org/issue?@action=redirect&bpo=42197

   (15) https://bugs.python.org/issue?@action=redirect&bpo=47070

   (16) https://bugs.python.org/issue?@action=redirect&bpo=47053

   (17) https://bugs.python.org/issue?@action=redirect&bpo=47045

   (18) https://bugs.python.org/issue?@action=redirect&bpo=46968

   (19) https://bugs.python.org/issue?@action=redirect&bpo=46329

   (20) https://bugs.python.org/issue?@action=redirect&bpo=46841

   (21) https://bugs.python.org/issue?@action=redirect&bpo=47012

   (22) https://bugs.python.org/issue?@action=redirect&bpo=47009

   (23) https://bugs.python.org/issue?@action=redirect&bpo=47005

   (24) https://bugs.python.org/issue?@action=redirect&bpo=46829

   (25) https://bugs.python.org/issue?@action=redirect&bpo=46993

   (26) https://bugs.python.org/issue?@action=redirect&bpo=39829

   (27) https://bugs.python.org/issue?@action=redirect&bpo=46944

   (28) https://bugs.python.org/issue?@action=redirect&bpo=46841

   (29) https://bugs.python.org/issue?@action=redirect&bpo=46841

   (30) https://bugs.python.org/issue?@action=redirect&bpo=46881

   (31) https://bugs.python.org/issue?@action=redirect&bpo=46838

   (32) https://bugs.python.org/issue?@action=redirect&bpo=43721

   (33) https://bugs.python.org/issue?@action=redirect&bpo=43224


File: python.info,  Node: Library<22>,  Next: Documentation<17>,  Prev: Core and Builtins<23>,  Up: Python 3 11 0 alpha 7

1.23.23.2 Library
.................

   - bpo-47208(1): Allow vendors to override ‘CTYPES_MAX_ARGCOUNT’.

   - bpo-23689(2): *note re: a7. module: fix memory leak when a match is
     terminated by a signal or memory allocation failure.  Patch by Ma
     Lin.

   - bpo-47167(3): Allow overriding a future compliance check in *note
     asyncio.Task: 480.

   - bpo-47151(4): When subprocess tries to use vfork, it now falls back
     to fork if vfork returns an error.  This allows use in situations
     where vfork isn't allowed by the OS kernel.

   - bpo-47152(5): Convert the *note re: a7. module into a package.
     Deprecate modules ‘sre_compile’, ‘sre_constants’ and ‘sre_parse’.

   - bpo-4833(6): Add ‘ZipFile.mkdir()’

   - bpo-27929(7): Fix *note asyncio.loop.sock_connect(): d70. to only
     resolve names for *note socket.AF_INET: 1722. or *note
     socket.AF_INET6: 1723. families.  Resolution may not make sense for
     other families, like ‘socket.AF_BLUETOOTH’ and *note
     socket.AF_UNIX: 1724.

   - bpo-14265(8): Adds the fully qualified test name to unittest output

   - bpo-47061(9): Deprecate the aifc module.

   - bpo-39622(10): Handle Ctrl+C in asyncio programs to interrupt the
     main task.

   - bpo-47101(11): *note hashlib.algorithms_available: 1301. now lists
     only algorithms that are provided by activated crypto providers on
     OpenSSL 3.0.  Legacy algorithms are not listed unless the legacy
     provider has been loaded into the default OSSL context.

   - bpo-47099(12): All ‘URLError’ exception messages raised in *note
     urllib.request.URLopener: 2e0. now contain a colon between ‘ftp
     error’ and the rest of the message.  Previously, ‘open_ftp()’
     missed the colon.  Patch by Oleg Iarygin.

   - bpo-47099(13): Exception chaining is changed from
     ‘Exception.with_traceback()’/*note sys.exc_info(): 630. to PEP
     3134(14).  Patch by Oleg Iarygin.

   - bpo-47095(15): *note hashlib: 5e.'s internal ‘_blake2’ module now
     prefers ‘libb2’ from ‘https://www.blake2.net/’ over Python's
     vendored copy of blake2.

   - bpo-47098(16): The Keccak Code Package for *note hashlib: 5e.'s
     internal ‘_sha3’ module has been replaced with tiny_sha3.  The
     module is used as fallback when Python is built without OpenSSL.

   - bpo-47088(17): Implement *note typing.LiteralString: 56e, part of
     PEP 675(18).  Patch by Jelle Zijlstra.

   - bpo-42885(19): Optimize *note re.search(): 11c4, *note re.split():
     282, *note re.findall(): fcd, *note re.finditer(): 1468. and *note
     re.sub(): 283. for regular expressions starting with ‘\A’ or ‘^’.

   - bpo-23691(20): Protect the *note re.finditer(): 1468. iterator from
     re-entering.

   - bpo-47067(21): Optimize calling ‘GenericAlias’ objects by using PEP
     590(22) ‘vectorcall’ and by replacing ‘PyObject_SetAttrString’ with
     ‘PyObject_SetAttr’.

   - bpo-28080(23): Add the 'metadata_encoding' parameter in the *note
     zipfile.ZipFile: 669. constructor and the ‘--metadata-encoding’
     option in the *note zipfile: 117. CLI to allow reading zipfiles
     using non-standard codecs to encode the filenames within the
     archive.

   - bpo-47000(24): Make *note io.text_encoding(): 15c1. returns "utf-8"
     when UTF-8 mode is enabled.

   - bpo-42369(25): Fix thread safety of ‘zipfile._SharedFile.tell()’ to
     avoid a "zipfile.BadZipFile: Bad CRC-32 for file" exception when
     reading a ‘ZipFile’ from multiple threads.

   - bpo-38256(26): Fix *note binascii.crc32(): 158c. when it is
     compiled to use zlib'c crc32 to work properly on inputs 4+GiB in
     length instead of returning the wrong result.  The workaround prior
     to this was to always feed the function data in increments smaller
     than 4GiB or to just call the zlib module function.

     We also have *note binascii.crc32(): 158c. release the GIL when
     computing on larger inputs as *note zlib.crc32(): 158b. and *note
     hashlib: 5e. do.

     This also boosts performance on Windows as it now uses the zlib
     crc32 implementation for *note binascii.crc32(): 158c. for a 2-3x
     speedup.

     That the stdlib has a crc32 API in two modules is a known
     historical oddity.  This moves us closer to a single implementation
     behind them.

   - bpo-47066(27): Global inline flags (e.g.  ‘(?i)’) can now only be
     used at the start of the regular expressions.  Using them not at
     the start of expression was deprecated since Python 3.6.

   - bpo-39394(28): A warning about inline flags not at the start of the
     regular expression now contains the position of the flag.

   - bpo-433030(29): Add support of atomic grouping (‘(?>...)’) and
     possessive quantifiers (‘*+’, ‘++’, ‘?+’, ‘{m,n}+’) in *note
     regular expressions: a7.

   - bpo-47062(30): Implement *note asyncio.Runner: 5a5. context
     manager.

   - bpo-46382(31): *note dataclass(): 1af. ‘slots=True’ now correctly
     omits slots already defined in base classes.  Patch by Arie
     Bovenberg.

   - bpo-47057(32): Use FASTCALL convention for ‘FutureIter.throw()’

   - bpo-47061(33): Deprecate the various modules listed by PEP 594(34):

     aifc, asynchat, asyncore, audioop, cgi, cgitb, chunk, crypt,
     imghdr, msilib, nntplib, nis, ossaudiodev, pipes, smtpd, sndhdr,
     spwd, sunau, telnetlib, uu, xdrlib

   - bpo-34790(35): Remove passing coroutine objects to *note
     asyncio.wait(): 426.

   - bpo-47039(36): Normalize ‘repr()’ of asyncio future and task
     objects.

   - bpo-2604(37): Fix bug where doctests using globals would fail when
     run multiple times.

   - bpo-45150(38): Add *note hashlib.file_digest(): 5ea. helper for
     efficient hashing of file object.

   - bpo-34861(39): Made cumtime the default sorting key for cProfile

   - bpo-45997(40): Fix *note asyncio.Semaphore: a17. re-aquiring FIFO
     order.

   - bpo-47022(41): The ‘asynchat’, ‘asyncore’ and ‘smtpd’ modules have
     been deprecated since at least Python 3.6.  Their documentation and
     deprecation warnings and have now been updated to note they will
     removed in Python 3.12 ( PEP 594(42)).

   - bpo-43253(43): Fix a crash when closing transports where the
     underlying socket handle is already invalid on the Proactor event
     loop.

   - bpo-40280(44): *note select.select(): d46. now passes ‘NULL’ to
     ‘select’ for each empty fdset.

   - bpo-47004(45): Apply bugfixes from importlib_metadata 4.11.3,
     including bugfix for EntryPoint.extras, which was returning match
     objects and not the extras strings.

   - bpo-46998(46): Allow subclassing of *note typing.Any: 651.  Patch
     by Shantanu Jain.

   - bpo-46995(47): Deprecate missing *note asyncio.Task.set_name():
     981. for third-party task implementations, schedule making it
     mandatory in Python 3.13.

   - bpo-46994(48): Accept explicit contextvars.Context in *note
     asyncio.create_task(): 5a1. and *note asyncio.loop.create_task():
     980.

   - bpo-46981(49): ‘typing.get_args(typing.Tuple[()])’ now returns ‘()’
     instead of ‘((),)’.

   - bpo-46968(50): Add ‘os.sysconf_names['SC_MINSIGSTKSZ']’.

   - bpo-46985(51): Upgrade pip wheel bundled with ensurepip (pip
     22.0.4)

   - bpo-46968(52): *note faulthandler: 4e.: On Linux 5.14 and newer,
     dynamically determine size of signal handler stack size CPython
     allocates using ‘getauxval(AT_MINSIGSTKSZ)’.  This changes allows
     for Python extension's request to Linux kernel to use AMX_TILE
     instruction set on Sapphire Rapids Xeon processor to succeed,
     unblocking use of the ISA in frameworks.

   - bpo-46917(53): The *note math.nan: 609. value is now always
     available.  Patch by Victor Stinner.

   - bpo-46955(54): Expose ‘asyncio.base_events.Server’ as *note
     asyncio.Server: ab5.  Patch by Stefan Zabka.

   - bpo-23325(55): The *note signal: b4. module no longer assumes that
     *note SIG_IGN: 1725. and *note SIG_DFL: 1726. are small int
     singletons.

   - bpo-46932(56): Update bundled libexpat to 2.4.7

   - bpo-46933(57): The *note pwd: a0. module is now optional.  *note
     os.path.expanduser(): 9b8. returns the path when the *note pwd: a0.
     module is not available.

   - bpo-40059(58): PEP 680(59), the *note tomllib: e5. module.  Adds
     support for parsing TOML.

   - bpo-464471(60): *note asyncio.timeout(): 5a3. and *note
     asyncio.timeout_at(): 1727. context managers added.  Patch by Tin
     Tvrtković and Andrew Svetlov.

   - bpo-46805(61): Added raw datagram socket functions for asyncio:
     ‘sock_sendto()’, ‘sock_recvfrom()’ and ‘sock_recvfrom_into()’.

   - bpo-46644(62): No longer require valid typeforms to be callable.
     This allows *note typing.Annotated: 8e1. to wrap *note
     typing.ParamSpecArgs: 76a. and ‘dataclasses.InitVar’.  Patch by
     Gregory Beauregard.

   - bpo-46581(63): Brings ‘ParamSpec’ propagation for ‘GenericAlias’ in
     line with ‘Concatenate’ (and others).

   - bpo-45413(64): Define 'posix_venv' and 'nt_venv' *note sysconfig
     installation schemes: 635. to be used for bootstrapping new virtual
     environments.  Add 'venv' sysconfig installation scheme to get the
     appropriate one of the above.  The schemes are identical to the
     pre-existing 'posix_prefix' and 'nt' install schemes.  The *note
     venv: f9. module now uses the 'venv' scheme to create new virtual
     environments instead of hardcoding the paths depending only on the
     platform.  Downstream Python distributors customizing the
     'posix_prefix' or 'nt' install scheme in a way that is not
     compatible with the install scheme used in virtual environments are
     encouraged not to customize the 'venv' schemes.  When Python itself
     runs in a virtual environment, *note
     sysconfig.get_default_scheme(): 1728. and *note
     sysconfig.get_preferred_scheme(): 636. with ‘key="prefix"’ returns
     'venv'.

   - bpo-43224(65): Implement support for PEP 646 in typing.py.

   - bpo-43224(66): Allow unpacking types.GenericAlias objects, e.g.
     ‘*tuple[int, str]’.

   - bpo-46557(67): Warnings captured by the logging module are now
     logged without a format string to prevent systems that group logs
     by the msg argument from grouping captured warnings together.

   - bpo-41370(68): *note typing.get_type_hints(): 657. now supports
     evaluating strings as forward references in *note PEP 585 generic
     aliases: 656.

   - bpo-46607(69): Add *note DeprecationWarning: 18b. to
     ‘LegacyInterpolation’, deprecated in the docstring since Python
     3.2.  Will be removed in Python 3.13.  Use ‘BasicInterpolation’ or
     ‘ExtendedInterpolation’ instead.

   - bpo-26120(70): *note pydoc: a3. now excludes __future__ imports
     from the module's data items.

   - bpo-46480(71): Add *note typing.assert_type(): 650.  Patch by Jelle
     Zijlstra.

   - bpo-46421(72): Fix a unittest issue where if the command was
     invoked as ‘python -m unittest’ and the filename(s) began with a
     dot (.), a ‘ValueError’ is returned.

   - bpo-46245(73): Add optional parameter 'dir_fd' in *note
     shutil.rmtree(): 2d2.

   - bpo-22859(74): ‘unittest.TestProgram.usageExit()’ is marked as
     deprecated, to be removed in Python 3.13.

   - bpo-46170(75): Improve the error message when you try to subclass
     an instance of *note typing.NewType: c9c.

   - bpo-40296(76): Fix supporting generic aliases in *note pydoc: a3.

   - bpo-20392(77): Fix inconsistency with uppercase file extensions in
     ‘MimeTypes.guess_type()’.  Patch by Kumar Aditya.

   - bpo-46030(78): Add ‘LOCAL_CREDS’, ‘LOCAL_CREDS_PERSISTENT’ and
     ‘SCM_CREDS2’ FreeBSD constants to the socket module.

   - bpo-44439(79): Fix ‘.write()’ method of a member file in ‘ZipFile’,
     when the input data is an object that supports the buffer protocol,
     the file length may be wrong.

   - bpo-45171(80): Fix handling of the ‘stacklevel’ argument to logging
     functions in the *note logging: 7b. module so that it is consistent
     across all logging functions and, as advertised, similar to the
     ‘stacklevel’ argument used in *note warn(): 1488.

   - bpo-24959(81): Fix bug where *note unittest: ef. sometimes drops
     frames from tracebacks of exceptions raised in tests.

   - bpo-44859(82): Raise more accurate and PEP 249(83) compatible
     exceptions in *note sqlite3: ba.

        * Raise *note InterfaceError: 623. instead of *note
          ProgrammingError: 49a. for ‘SQLITE_MISUSE’ errors.

        * Don't overwrite *note BufferError: 1729. with *note
          ValueError: 1e7. when conversion to BLOB fails.

        * Raise *note ProgrammingError: 49a. instead of *note Warning:
          172a. if user tries to *note execute(): 2b3. more than one SQL
          statement.

        * Raise *note ProgrammingError: 49a. instead of *note
          ValueError: 1e7. if an SQL query contains null characters.

   - bpo-44493(84): Add missing terminated NUL in sockaddr_un's length

     This was potentially observable when using non-abstract AF_UNIX
     datagram sockets to processes written in another programming
     language.

   - bpo-41930(85): Add *note serialize(): 624. and *note deserialize():
     625. support to *note sqlite3: ba.  Patch by Erlend E. Aasland.

   - bpo-33178(86): Added *note ctypes.BigEndianUnion: 172b. and *note
     ctypes.LittleEndianUnion: 172c. classes, as originally documented
     in the library docs but not yet implemented.

   - bpo-43352(87): Add an Barrier object in synchronization primitives
     of 'asyncio' Lib in order to be consistent with Barrier from
     'threading' and 'multiprocessing' libs*

   - bpo-35859(88): *note re: a7. module, fix a few bugs about capturing
     group.  In rare cases, capturing group gets an incorrect string.
     Patch by Ma Lin.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=47208

   (2) https://bugs.python.org/issue?@action=redirect&bpo=23689

   (3) https://bugs.python.org/issue?@action=redirect&bpo=47167

   (4) https://bugs.python.org/issue?@action=redirect&bpo=47151

   (5) https://bugs.python.org/issue?@action=redirect&bpo=47152

   (6) https://bugs.python.org/issue?@action=redirect&bpo=4833

   (7) https://bugs.python.org/issue?@action=redirect&bpo=27929

   (8) https://bugs.python.org/issue?@action=redirect&bpo=14265

   (9) https://bugs.python.org/issue?@action=redirect&bpo=47061

   (10) https://bugs.python.org/issue?@action=redirect&bpo=39622

   (11) https://bugs.python.org/issue?@action=redirect&bpo=47101

   (12) https://bugs.python.org/issue?@action=redirect&bpo=47099

   (13) https://bugs.python.org/issue?@action=redirect&bpo=47099

   (14) https://peps.python.org/pep-3134/

   (15) https://bugs.python.org/issue?@action=redirect&bpo=47095

   (16) https://bugs.python.org/issue?@action=redirect&bpo=47098

   (17) https://bugs.python.org/issue?@action=redirect&bpo=47088

   (18) https://peps.python.org/pep-0675/

   (19) https://bugs.python.org/issue?@action=redirect&bpo=42885

   (20) https://bugs.python.org/issue?@action=redirect&bpo=23691

   (21) https://bugs.python.org/issue?@action=redirect&bpo=47067

   (22) https://peps.python.org/pep-0590/

   (23) https://bugs.python.org/issue?@action=redirect&bpo=28080

   (24) https://bugs.python.org/issue?@action=redirect&bpo=47000

   (25) https://bugs.python.org/issue?@action=redirect&bpo=42369

   (26) https://bugs.python.org/issue?@action=redirect&bpo=38256

   (27) https://bugs.python.org/issue?@action=redirect&bpo=47066

   (28) https://bugs.python.org/issue?@action=redirect&bpo=39394

   (29) https://bugs.python.org/issue?@action=redirect&bpo=433030

   (30) https://bugs.python.org/issue?@action=redirect&bpo=47062

   (31) https://bugs.python.org/issue?@action=redirect&bpo=46382

   (32) https://bugs.python.org/issue?@action=redirect&bpo=47057

   (33) https://bugs.python.org/issue?@action=redirect&bpo=47061

   (34) https://peps.python.org/pep-0594/

   (35) https://bugs.python.org/issue?@action=redirect&bpo=34790

   (36) https://bugs.python.org/issue?@action=redirect&bpo=47039

   (37) https://bugs.python.org/issue?@action=redirect&bpo=2604

   (38) https://bugs.python.org/issue?@action=redirect&bpo=45150

   (39) https://bugs.python.org/issue?@action=redirect&bpo=34861

   (40) https://bugs.python.org/issue?@action=redirect&bpo=45997

   (41) https://bugs.python.org/issue?@action=redirect&bpo=47022

   (42) https://peps.python.org/pep-0594/

   (43) https://bugs.python.org/issue?@action=redirect&bpo=43253

   (44) https://bugs.python.org/issue?@action=redirect&bpo=40280

   (45) https://bugs.python.org/issue?@action=redirect&bpo=47004

   (46) https://bugs.python.org/issue?@action=redirect&bpo=46998

   (47) https://bugs.python.org/issue?@action=redirect&bpo=46995

   (48) https://bugs.python.org/issue?@action=redirect&bpo=46994

   (49) https://bugs.python.org/issue?@action=redirect&bpo=46981

   (50) https://bugs.python.org/issue?@action=redirect&bpo=46968

   (51) https://bugs.python.org/issue?@action=redirect&bpo=46985

   (52) https://bugs.python.org/issue?@action=redirect&bpo=46968

   (53) https://bugs.python.org/issue?@action=redirect&bpo=46917

   (54) https://bugs.python.org/issue?@action=redirect&bpo=46955

   (55) https://bugs.python.org/issue?@action=redirect&bpo=23325

   (56) https://bugs.python.org/issue?@action=redirect&bpo=46932

   (57) https://bugs.python.org/issue?@action=redirect&bpo=46933

   (58) https://bugs.python.org/issue?@action=redirect&bpo=40059

   (59) https://peps.python.org/pep-0680/

   (60) https://bugs.python.org/issue?@action=redirect&bpo=464471

   (61) https://bugs.python.org/issue?@action=redirect&bpo=46805

   (62) https://bugs.python.org/issue?@action=redirect&bpo=46644

   (63) https://bugs.python.org/issue?@action=redirect&bpo=46581

   (64) https://bugs.python.org/issue?@action=redirect&bpo=45413

   (65) https://bugs.python.org/issue?@action=redirect&bpo=43224

   (66) https://bugs.python.org/issue?@action=redirect&bpo=43224

   (67) https://bugs.python.org/issue?@action=redirect&bpo=46557

   (68) https://bugs.python.org/issue?@action=redirect&bpo=41370

   (69) https://bugs.python.org/issue?@action=redirect&bpo=46607

   (70) https://bugs.python.org/issue?@action=redirect&bpo=26120

   (71) https://bugs.python.org/issue?@action=redirect&bpo=46480

   (72) https://bugs.python.org/issue?@action=redirect&bpo=46421

   (73) https://bugs.python.org/issue?@action=redirect&bpo=46245

   (74) https://bugs.python.org/issue?@action=redirect&bpo=22859

   (75) https://bugs.python.org/issue?@action=redirect&bpo=46170

   (76) https://bugs.python.org/issue?@action=redirect&bpo=40296

   (77) https://bugs.python.org/issue?@action=redirect&bpo=20392

   (78) https://bugs.python.org/issue?@action=redirect&bpo=46030

   (79) https://bugs.python.org/issue?@action=redirect&bpo=44439

   (80) https://bugs.python.org/issue?@action=redirect&bpo=45171

   (81) https://bugs.python.org/issue?@action=redirect&bpo=24959

   (82) https://bugs.python.org/issue?@action=redirect&bpo=44859

   (83) https://peps.python.org/pep-0249/

   (84) https://bugs.python.org/issue?@action=redirect&bpo=44493

   (85) https://bugs.python.org/issue?@action=redirect&bpo=41930

   (86) https://bugs.python.org/issue?@action=redirect&bpo=33178

   (87) https://bugs.python.org/issue?@action=redirect&bpo=43352

   (88) https://bugs.python.org/issue?@action=redirect&bpo=35859


File: python.info,  Node: Documentation<17>,  Next: Tests<20>,  Prev: Library<22>,  Up: Python 3 11 0 alpha 7

1.23.23.3 Documentation
.......................

   - bpo-45099(1): Document internal *note asyncio: 8. API.

   - bpo-47126(2): Update PEP URLs to PEP 676(3)'s new canonical form.

   - bpo-47040(4): Clarified the old Python versions compatibility note
     of *note binascii.crc32(): 158c. / *note zlib.adler32(): 172e. /
     *note zlib.crc32(): 158b. functions.

   - bpo-46033(5): Clarify ‘for’ statement execution in its doc.

   - bpo-45790(6): Adjust inaccurate phrasing in *note Defining
     Extension Types; Tutorial: 172f. about the ‘ob_base’ field and the
     macros used to access its contents.

   - bpo-42340(7): Document that in some circumstances *note
     KeyboardInterrupt: 975. may cause the code to enter an inconsistent
     state.  Provided a sample workaround to avoid it if needed.

   - bpo-41233(8): Link the errnos referenced in
     ‘Doc/library/exceptions.rst’ to their respective section in
     ‘Doc/library/errno.rst’, and vice versa.  Previously this was only
     done for EINTR and InterruptedError.  Patch by Yan "yyyyyyyan"
     Orestes.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45099

   (2) https://bugs.python.org/issue?@action=redirect&bpo=47126

   (3) https://peps.python.org/pep-0676/

   (4) https://bugs.python.org/issue?@action=redirect&bpo=47040

   (5) https://bugs.python.org/issue?@action=redirect&bpo=46033

   (6) https://bugs.python.org/issue?@action=redirect&bpo=45790

   (7) https://bugs.python.org/issue?@action=redirect&bpo=42340

   (8) https://bugs.python.org/issue?@action=redirect&bpo=41233


File: python.info,  Node: Tests<20>,  Next: Build<22>,  Prev: Documentation<17>,  Up: Python 3 11 0 alpha 7

1.23.23.4 Tests
...............

   - bpo-47205(1): Skip test for *note sched_getaffinity(): 10a2. and
     *note sched_setaffinity(): 10a6. error case on FreeBSD.

   - bpo-46126(2): Restore 'descriptions' when running tests internally.

   - bpo-47104(3): Rewrite *note asyncio.to_thread(): 88d. tests to use
     *note unittest.IsolatedAsyncioTestCase: 2de.

   - bpo-40280(4): The test suite is now passing on the Emscripten
     platform.  All fork, socket, and subprocess-based tests are
     skipped.

   - bpo-47037(5): Skip ‘strftime("%4Y")’ feature test on Windows.  It
     can cause an assertion error in debug builds.

   - bpo-46587(6): Skip tests if platform's ‘strftime’ does not support
     non-portable glibc extensions.

   - bpo-47015(7): A test case for *note os.sendfile(): ab2. is
     converted from deprecated ‘asyncore’ (see PEP 594(8)) to *note
     asyncio: 8.  Patch by Oleg Iarygin.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=47205

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46126

   (3) https://bugs.python.org/issue?@action=redirect&bpo=47104

   (4) https://bugs.python.org/issue?@action=redirect&bpo=40280

   (5) https://bugs.python.org/issue?@action=redirect&bpo=47037

   (6) https://bugs.python.org/issue?@action=redirect&bpo=46587

   (7) https://bugs.python.org/issue?@action=redirect&bpo=47015

   (8) https://peps.python.org/pep-0594/


File: python.info,  Node: Build<22>,  Next: Windows<19>,  Prev: Tests<20>,  Up: Python 3 11 0 alpha 7

1.23.23.5 Build
...............

   - bpo-40280(1): Add configure option *note
     -enable-wasm-dynamic-linking: 1732. to enable ‘dlopen’ and
     MAIN_MODULE / SIDE_MODULE on ‘wasm32-emscripten’.

   - bpo-46023(2): ‘makesetup’ now detects and skips all duplicated
     module definitions.  The first entry wins.

   - bpo-40280(3): Add SOABI ‘wasm32-emscripten’ for Emscripten and
     ‘wasm32-wasi’ for WASI on 32bit WASM as well as ‘wasm64’ counter
     parts.

   - bpo-47032(4): Ensure Windows install builds fail correctly with a
     non-zero exit code when part of the build fails.

   - bpo-47024(5): Update OpenSSL to 1.1.1n for macOS installers and all
     Windows builds.

   - bpo-46996(6): The *note tkinter: d9. package now requires Tcl/Tk
     version 8.5.12 or newer.

   - bpo-46973(7): Add ‘regen-configure’ make target to regenerate
     configure script with Christian's container image
     ‘quay.io/tiran/cpython_autoconf:269’.

   - bpo-46917(8): Building Python now requires support of IEEE 754
     floating-point numbers.  Patch by Victor Stinner.

   - bpo-45774(9): ‘configure’ now verifies that all SQLite C APIs
     needed for the *note sqlite3: ba. extension module are found.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40280

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46023

   (3) https://bugs.python.org/issue?@action=redirect&bpo=40280

   (4) https://bugs.python.org/issue?@action=redirect&bpo=47032

   (5) https://bugs.python.org/issue?@action=redirect&bpo=47024

   (6) https://bugs.python.org/issue?@action=redirect&bpo=46996

   (7) https://bugs.python.org/issue?@action=redirect&bpo=46973

   (8) https://bugs.python.org/issue?@action=redirect&bpo=46917

   (9) https://bugs.python.org/issue?@action=redirect&bpo=45774


File: python.info,  Node: Windows<19>,  Next: macOS<15>,  Prev: Build<22>,  Up: Python 3 11 0 alpha 7

1.23.23.6 Windows
.................

   - bpo-47194(1): Update ‘zlib’ to v1.2.12 to resolve
     CVE-2018-25032(2).

   - bpo-47171(3): Enables installing the ‘py.exe’ launcher on Windows
     ARM64.

   - bpo-46566(4): Upgraded *note Python Launcher for Windows: 562. to
     support a new ‘-V:company/tag’ argument for full PEP 514(5) support
     and to detect ARM64 installs.  The ‘-64’ suffix on arguments is
     deprecated, but still selects any non-32-bit install.  Setting
     ‘PYLAUNCHER_ALLOW_INSTALL’ and specifying a version that is not
     installed will attempt to install the requested version from the
     Microsoft Store.

   - bpo-47086(6): The installer for Windows now includes documentation
     as loose HTML files rather than a single compiled ‘.chm’ file.

   - bpo-46907(7): Update Windows installer to use SQLite 3.38.1.

   - bpo-44549(8): Update bzip2 to 1.0.8 in Windows builds to mitigate
     CVE-2016-3189(9) and CVE-2019-12900(10).

   - bpo-46948(11): Prevent CVE-2022-26488(12) by ensuring the Add to
     PATH option in the Windows installer uses the correct path when
     being repaired.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=47194

   (2) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-25032

   (3) https://bugs.python.org/issue?@action=redirect&bpo=47171

   (4) https://bugs.python.org/issue?@action=redirect&bpo=46566

   (5) https://peps.python.org/pep-0514/

   (6) https://bugs.python.org/issue?@action=redirect&bpo=47086

   (7) https://bugs.python.org/issue?@action=redirect&bpo=46907

   (8) https://bugs.python.org/issue?@action=redirect&bpo=44549

   (9) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3189

   (10) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12900

   (11) https://bugs.python.org/issue?@action=redirect&bpo=46948

   (12) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-26488


File: python.info,  Node: macOS<15>,  Next: Tools/Demos<12>,  Prev: Windows<19>,  Up: Python 3 11 0 alpha 7

1.23.23.7 macOS
...............

   - bpo-46890(1): Fix a regression in the setting of
     ‘sys._base_executable’ in framework builds, and thereby fix a
     regression in *note venv: f9. virtual environments with such
     builds.

   - bpo-46907(2): Update macOS installer to SQLite 3.38.1.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46890

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46907


File: python.info,  Node: Tools/Demos<12>,  Next: C API<21>,  Prev: macOS<15>,  Up: Python 3 11 0 alpha 7

1.23.23.8 Tools/Demos
.....................

   - bpo-40280(1): Replace Emscripten's limited shell with Katie Bell's
     browser-ui REPL from python-wasm project.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40280


File: python.info,  Node: C API<21>,  Prev: Tools/Demos<12>,  Up: Python 3 11 0 alpha 7

1.23.23.9 C API
...............

   - bpo-40421(1): Add ‘PyFrame_GetBuiltins’, ‘PyFrame_GetGenerator’ and
     ‘PyFrame_GetGlobals’ C-API functions to access frame object
     attributes safely from C code.

   - bpo-46850(2): Move the private ‘_PyFrameEvalFunction’ type, and
     private ‘_PyInterpreterState_GetEvalFrameFunc()’ and
     ‘_PyInterpreterState_SetEvalFrameFunc()’ functions to the internal
     C API. The ‘_PyFrameEvalFunction’ callback function type now uses
     the ‘_PyInterpreterFrame’ type which is part of the internal C API.
     Patch by Victor Stinner.

   - bpo-46850(3): Move the private undocumented
     ‘_PyEval_EvalFrameDefault()’ function to the internal C API. The
     function now uses the ‘_PyInterpreterFrame’ type which is part of
     the internal C API. Patch by Victor Stinner.

   - bpo-46850(4): Remove the private undocumented function
     ‘_PyEval_CallTracing()’ from the C API. Call the public *note
     sys.call_tracing(): 1737. function instead.  Patch by Victor
     Stinner.

   - bpo-46850(5): Remove the private undocumented function
     ‘_PyEval_GetCoroutineOriginTrackingDepth()’ from the C API. Call
     the public *note sys.get_coroutine_origin_tracking_depth(): b31.
     function instead.  Patch by Victor Stinner.

   - bpo-46850(6): Remove the following private undocumented functions
     from the C API:

        * ‘_PyEval_GetAsyncGenFirstiter()’

        * ‘_PyEval_GetAsyncGenFinalizer()’

        * ‘_PyEval_SetAsyncGenFirstiter()’

        * ‘_PyEval_SetAsyncGenFinalizer()’

     Call the public *note sys.get_asyncgen_hooks(): 1738. and *note
     sys.set_asyncgen_hooks(): 151a. functions instead.  Patch by Victor
     Stinner.

   - bpo-46987(7): Remove private functions ‘_PySys_GetObjectId()’ and
     ‘_PySys_SetObjectId()’.  Patch by Donghee Na.

   - bpo-46906(8): Add new functions to pack and unpack C double
     (serialize and deserialize): *note PyFloat_Pack2(): 709, *note
     PyFloat_Pack4(): 70a, *note PyFloat_Pack8(): 70b, *note
     PyFloat_Unpack2(): 70c, *note PyFloat_Unpack4(): 70d. and *note
     PyFloat_Unpack8(): 70e.  Patch by Victor Stinner.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40421

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46850

   (3) https://bugs.python.org/issue?@action=redirect&bpo=46850

   (4) https://bugs.python.org/issue?@action=redirect&bpo=46850

   (5) https://bugs.python.org/issue?@action=redirect&bpo=46850

   (6) https://bugs.python.org/issue?@action=redirect&bpo=46850

   (7) https://bugs.python.org/issue?@action=redirect&bpo=46987

   (8) https://bugs.python.org/issue?@action=redirect&bpo=46906


File: python.info,  Node: Python 3 11 0 alpha 6,  Next: Python 3 11 0 alpha 5,  Prev: Python 3 11 0 alpha 7,  Up: Changelog（更動日誌）

1.23.24 Python 3.11.0 alpha 6
-----------------------------

'Release date: 2022-03-07'

* Menu:

* Core and Builtins: Core and Builtins<24>.
* Library: Library<23>.
* Documentation: Documentation<18>.
* Tests: Tests<21>.
* Build: Build<23>.
* Windows: Windows<20>.
* IDLE: IDLE<14>.
* C API: C API<22>.


File: python.info,  Node: Core and Builtins<24>,  Next: Library<23>,  Up: Python 3 11 0 alpha 6

1.23.24.1 Core and Builtins
...........................

   - bpo-46940(1): Avoid overriding *note AttributeError: 2f6. metadata
     information for nested attribute access calls.  Patch by Pablo
     Galindo.

   - bpo-46927(2): Include the type's name in the error message for
     subscripting non-generic types.

   - bpo-46921(3): Support vectorcall for ‘super()’.  Patch by Ken Jin.

   - bpo-46841(4): Fix incorrect handling of inline cache entries when
     specializing *note BINARY_OP: 6aa.

   - bpo-46841(5): Use an oparg to simplify the construction of helpful
     error messages in *note GET_AWAITABLE: 173b.

   - bpo-46903(6): Make sure that str subclasses can be used as
     attribute names for instances with virtual dictionaries.  Fixes
     regression in 3.11alpha

   - bpo-46841(7): Add more detailed specialization failure stats for
     *note COMPARE_OP: 90d. followed by *note EXTENDED_ARG: 16a8.

   - bpo-46891(8): Fix bug introduced during 3.11alpha where subclasses
     of ‘types.ModuleType’ with ‘__slots__’ were not initialized
     correctly, resulting in an interpreter crash.

   - bpo-46841(9): Use inline caching for *note LOAD_ATTR: 486, *note
     LOAD_METHOD: bc6, and *note STORE_ATTR: 173c.

   - bpo-46841(10): Use inline cache for *note BINARY_SUBSCR: 163f.

   - bpo-46841(11): Use inline caching for *note COMPARE_OP: 90d.

   - bpo-46864(12): Deprecate ‘PyBytesObject.ob_shash’.  It will be
     removed in Python 3.13.

   - bpo-46841(13): Use inline caching for *note UNPACK_SEQUENCE: 173d.

   - bpo-46845(14): Reduces dict size by removing hash value from hash
     table when all inserted keys are Unicode.  For example,
     ‘sys.getsizeof(dict.fromkeys("abcdefg"))’ becomes 272 bytes from
     352 bytes on 64bit platform.

   - bpo-46841(15): Use inline cache for *note LOAD_GLOBAL: 15e4.

   - bpo-46852(16): Rename the private undocumented
     ‘float.__set_format__()’ method to ‘float.__setformat__()’ to fix a
     typo introduced in Python 3.7.  The method is only used by
     test_float.  Patch by Victor Stinner.

   - bpo-46852(17): Remove the undocumented private
     ‘float.__set_format__()’ method, previously known as
     ‘float.__setformat__()’ in Python 3.7.  Its docstring said: "You
     probably don't want to use this function.  It exists mainly to be
     used in Python's test suite."  Patch by Victor Stinner.

   - bpo-40116(18): Fix regression that dict.update(other) may don't
     respect iterate order of other when other is key sharing dict.

   - bpo-46712(19): Share global string identifiers in deep-frozen
     modules.

   - bpo-46430(20): Fix memory leak in interned strings of deep-frozen
     modules.

   - bpo-46841(21): Store *note BINARY_OP: 6aa. caches inline using a
     new *note CACHE: 69c. instruction.

   - bpo-45107(22): Specialize ‘LOAD_METHOD’ for instances with a dict.

   - bpo-44337(23): Reduce the memory usage of specialized *note
     LOAD_ATTR: 486. and *note STORE_ATTR: 173c. instructions.

   - bpo-46729(24): Add number of sub-exceptions to
     ‘BaseException.__str__()’.

   - bpo-45885(25): Don't un-adapt *note COMPARE_OP: 90d. when
     collecting specialization stats.

   - bpo-46329(26): Fix specialization stats gathering for ‘PRECALL’
     instructions.

   - bpo-46794(27): Bump up the libexpat version into 2.4.6

   - bpo-46823(28): Implement a specialized combined opcode
     ‘LOAD_FAST__LOAD_ATTR_INSTANCE_VALUE’.  Patch by Dennis Sweeney.

   - bpo-46820(29): Fix parsing a numeric literal immediately (without
     spaces) followed by "not in" keywords, like in ‘1not in x’.  Now
     the parser only emits a warning, not a syntax error.

   - bpo-46329(30): Move ‘KW_NAMES’ before ‘PRECALL’ instruction in call
     sequence.  Change ‘operand’ of ‘CALL’ to match ‘PRECALL’ for easier
     specialization.

   - bpo-46808(31): Remove the ‘NEXT_BLOCK’ macro from compile.c, and
     make the compiler automatically generate implicit blocks when they
     are needed.

   - bpo-46329(32): Add ‘PUSH_NULL’ instruction.  This is used as a
     prefix when evaluating a callable, so that the stack has the same
     shape for methods and other calls.  ‘PRECALL_FUNCTION’ and
     ‘PRECALL_METHOD’ are merged into a single ‘PRECALL’ instruction.

     There is no change in semantics.

   - bpo-46762(33): Fix an assert failure in debug builds when a '<',
     '>', or '=' is the last character in an f-string that's missing a
     closing right brace.

   - bpo-46730(34): Message of AttributeError caused by getting, setting
     or deleting a property without the corresponding function now
     mentions that the attribute is in fact a property and also
     specifies type of the class that it belongs to.

   - bpo-46724(35): Make sure that all backwards jumps use the
     ‘JUMP_ABSOLUTE’ instruction, rather than ‘JUMP_FORWARD’ with an
     argument of ‘(2**32)+offset’.

   - bpo-46732(36): Correct the docstring for the *note __bool__():
     1268. method.  Patch by Jelle Zijlstra.

   - bpo-46072(37): Add more detailed specialization failure statistics
     for *note BINARY_OP: 6aa.

   - bpo-46707(38): Avoid potential exponential backtracking when
     producing some syntax errors involving lots of brackets.  Patch by
     Pablo Galindo.

   - bpo-46323(39): *note ctypes: 22. now allocates memory on the stack
     instead of on the heap to pass arguments while calling a Python
     callback function.  Patch by Donghee Na.

   - bpo-45923(40): Add a quickened form of *note RESUME: 6a7. that
     skips quickening checks.

   - bpo-46702(41): Specialize *note UNPACK_SEQUENCE: 173d. for *note
     tuple: 322. and *note list: 5b6. unpackings.

   - bpo-46072(42): Opcode pair stats are now gathered with
     ‘--enable-pystats’.  Defining ‘DYNAMIC_EXECUTION_PROFILE’ or
     ‘DXPAIRS’ no longer has any effect.

   - bpo-46675(43): Allow more than 16 items in a split dict before it
     is combined.  The limit is now 254.

   - bpo-40479(44): Add a missing call to ‘va_end()’ in
     ‘Modules/_hashopenssl.c’.

   - bpo-46323(45): Use *note PyObject_Vectorcall(): 501. while calling
     ctypes callback function.  Patch by Donghee Na.

   - bpo-46615(46): When iterating over sets internally in
     ‘setobject.c’, acquire strong references to the resulting items
     from the set.  This prevents crashes in corner-cases of various set
     operations where the set gets mutated.

   - bpo-45828(47): The bytecode compiler now attempts to apply runtime
     stack manipulations at compile-time (whenever it is feasible to do
     so).

   - bpo-30496(48): Fixed a minor portability issue in the
     implementation of *note PyLong_FromLong(): 173e, and added a fast
     path for single-digit integers to *note PyLong_FromLongLong():
     173f.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46940

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46927

   (3) https://bugs.python.org/issue?@action=redirect&bpo=46921

   (4) https://bugs.python.org/issue?@action=redirect&bpo=46841

   (5) https://bugs.python.org/issue?@action=redirect&bpo=46841

   (6) https://bugs.python.org/issue?@action=redirect&bpo=46903

   (7) https://bugs.python.org/issue?@action=redirect&bpo=46841

   (8) https://bugs.python.org/issue?@action=redirect&bpo=46891

   (9) https://bugs.python.org/issue?@action=redirect&bpo=46841

   (10) https://bugs.python.org/issue?@action=redirect&bpo=46841

   (11) https://bugs.python.org/issue?@action=redirect&bpo=46841

   (12) https://bugs.python.org/issue?@action=redirect&bpo=46864

   (13) https://bugs.python.org/issue?@action=redirect&bpo=46841

   (14) https://bugs.python.org/issue?@action=redirect&bpo=46845

   (15) https://bugs.python.org/issue?@action=redirect&bpo=46841

   (16) https://bugs.python.org/issue?@action=redirect&bpo=46852

   (17) https://bugs.python.org/issue?@action=redirect&bpo=46852

   (18) https://bugs.python.org/issue?@action=redirect&bpo=40116

   (19) https://bugs.python.org/issue?@action=redirect&bpo=46712

   (20) https://bugs.python.org/issue?@action=redirect&bpo=46430

   (21) https://bugs.python.org/issue?@action=redirect&bpo=46841

   (22) https://bugs.python.org/issue?@action=redirect&bpo=45107

   (23) https://bugs.python.org/issue?@action=redirect&bpo=44337

   (24) https://bugs.python.org/issue?@action=redirect&bpo=46729

   (25) https://bugs.python.org/issue?@action=redirect&bpo=45885

   (26) https://bugs.python.org/issue?@action=redirect&bpo=46329

   (27) https://bugs.python.org/issue?@action=redirect&bpo=46794

   (28) https://bugs.python.org/issue?@action=redirect&bpo=46823

   (29) https://bugs.python.org/issue?@action=redirect&bpo=46820

   (30) https://bugs.python.org/issue?@action=redirect&bpo=46329

   (31) https://bugs.python.org/issue?@action=redirect&bpo=46808

   (32) https://bugs.python.org/issue?@action=redirect&bpo=46329

   (33) https://bugs.python.org/issue?@action=redirect&bpo=46762

   (34) https://bugs.python.org/issue?@action=redirect&bpo=46730

   (35) https://bugs.python.org/issue?@action=redirect&bpo=46724

   (36) https://bugs.python.org/issue?@action=redirect&bpo=46732

   (37) https://bugs.python.org/issue?@action=redirect&bpo=46072

   (38) https://bugs.python.org/issue?@action=redirect&bpo=46707

   (39) https://bugs.python.org/issue?@action=redirect&bpo=46323

   (40) https://bugs.python.org/issue?@action=redirect&bpo=45923

   (41) https://bugs.python.org/issue?@action=redirect&bpo=46702

   (42) https://bugs.python.org/issue?@action=redirect&bpo=46072

   (43) https://bugs.python.org/issue?@action=redirect&bpo=46675

   (44) https://bugs.python.org/issue?@action=redirect&bpo=40479

   (45) https://bugs.python.org/issue?@action=redirect&bpo=46323

   (46) https://bugs.python.org/issue?@action=redirect&bpo=46615

   (47) https://bugs.python.org/issue?@action=redirect&bpo=45828

   (48) https://bugs.python.org/issue?@action=redirect&bpo=30496


File: python.info,  Node: Library<23>,  Next: Documentation<18>,  Prev: Core and Builtins<24>,  Up: Python 3 11 0 alpha 6

1.23.24.2 Library
.................

   - bpo-25707(1): Fixed a file leak in *note
     xml.etree.ElementTree.iterparse(): 258. when the iterator is not
     exhausted.  Patch by Jacob Walls.

   - bpo-46877(2): Export *note unittest.doModuleCleanups(): 1741. in
     *note unittest: ef.  Patch by Kumar Aditya.

   - bpo-46848(3): For performance, use the optimized string-searching
     implementations from *note find(): 1742. and *note rfind(): 1743.
     for ‘find()’ and ‘rfind()’.

   - bpo-46736(4): *note SimpleHTTPRequestHandler: ae7. now uses HTML5
     grammar.  Patch by Donghee Na.

   - bpo-44886(5): Inherit asyncio proactor datagram transport from
     *note asyncio.DatagramTransport: 16af.

   - bpo-46827(6): Support UDP sockets in *note
     asyncio.loop.sock_connect(): d70. for selector-based event loops.
     Patch by Thomas Grainger.

   - bpo-46811(7): Make test suite support Expat >=2.4.5

   - bpo-46252(8): Raise *note TypeError: 4dd. if *note ssl.SSLSocket:
     88f. is passed to transport-based APIs.

   - bpo-46784(9): Fix libexpat symbols collisions with user dynamically
     loaded or statically linked libexpat in embedded Python.

   - bpo-46786(10): The HTML serialisation in xml.etree.ElementTree now
     writes ‘embed’, ‘source’, ‘track’ and ‘wbr’ as empty tags, as
     defined in HTML 5.

   - bpo-39327(11): *note shutil.rmtree(): 2d2. can now work with
     VirtualBox shared folders when running from the guest
     operating-system.

   - bpo-45390(12): Propagate *note asyncio.CancelledError: 19e. message
     from inner task to outer awaiter.

   - bpo-46756(13): Fix a bug in *note
     urllib.request.HTTPPasswordMgr.find_user_password(): 1744. and
     *note
     urllib.request.HTTPPasswordMgrWithPriorAuth.is_authenticated():
     1745. which allowed to bypass authorization.  For example, access
     to URI ‘example.org/foobar’ was allowed if the user was authorized
     for URI ‘example.org/foo’.

   - bpo-46737(14): *note random.gauss(): 1746. and *note
     random.normalvariate(): 1747. now have default arguments.

   - bpo-46752(15): Add task groups to asyncio (structured concurrency,
     inspired by Trio's nurseries).  This also introduces a change to
     task cancellation, where a cancelled task can't be cancelled again
     until it calls .uncancel().

   - bpo-46724(16): Fix *note dis: 30. behavior on negative jump
     offsets.

   - bpo-46333(17): The ‘__repr__()’ method of *note typing.ForwardRef:
     1748. now includes the ‘module’ parameter of *note
     typing.ForwardRef: 1748. when it is set.

   - bpo-46643(18): In *note typing.get_type_hints(): 657, support
     evaluating stringified ‘ParamSpecArgs’ and ‘ParamSpecKwargs’
     annotations.  Patch by Gregory Beauregard.

   - bpo-45863(19): When the *note tarfile: c8. module creates a pax
     format archive, it will put an integer representation of timestamps
     in the ustar header (if possible) for the benefit of older
     unarchivers, in addition to the existing full-precision timestamps
     in the pax extended header.

   - bpo-46066(20): Deprecate kwargs-based syntax for *note
     typing.TypedDict: 146. definitions.  It had confusing semantics
     when specifying totality, and was largely unused.  Patch by
     Jingchen Ye.

   - bpo-46676(21): Make *note typing.ParamSpec: 142. args and kwargs
     equal to themselves.  Patch by Gregory Beauregard.

   - bpo-46323(22): ‘ctypes.CFUNCTYPE()’ and ‘ctypes.WINFUNCTYPE()’ now
     fail to create the type if its ‘_argtypes_’ member contains too
     many arguments.  Previously, the error was only raised when calling
     a function.  Patch by Victor Stinner.

   - bpo-46672(23): Fix ‘NameError’ in *note asyncio.gather(): 5a2. when
     initial type check fails.

   - bpo-46659(24): The *note calendar.LocaleTextCalendar: 6e8. and
     *note calendar.LocaleHTMLCalendar: 6e9. classes now use *note
     locale.getlocale(): 2bd, instead of using *note
     locale.getdefaultlocale(): 2ba, if no locale is specified.  Patch
     by Victor Stinner.

   - bpo-46659(25): The *note locale.getdefaultlocale(): 2ba. function
     is deprecated and will be removed in Python 3.13.  Use *note
     locale.setlocale(): 2bb, *note locale.getpreferredencoding(False):
     4df. and *note locale.getlocale(): 2bd. functions instead.  Patch
     by Victor Stinner.

   - bpo-46655(26): In *note typing.get_type_hints(): 657, support
     evaluating bare stringified ‘TypeAlias’ annotations.  Patch by
     Gregory Beauregard.

   - bpo-45948(27): Fixed a discrepancy in the C implementation of the
     *note xml.etree.ElementTree: 10c. module.  Now, instantiating an
     *note xml.etree.ElementTree.XMLParser: 9f7. with a ‘target=None’
     keyword provides a default *note xml.etree.ElementTree.TreeBuilder:
     9f8. target as the Python implementation does.

   - bpo-46626(28): Expose Linux's ‘IP_BIND_ADDRESS_NO_PORT’ option in
     *note socket: b8.

   - bpo-46521(29): Fix a bug in the *note codeop: 15. module that was
     incorrectly identifying invalid code involving string quotes as
     valid code.

   - bpo-46571(30): Improve *note typing.no_type_check(): 659.

     Now it does not modify external classes and functions.  We also now
     correctly mark classmethods as not to be type checked.

   - bpo-46400(31): expat: Update libexpat from 2.4.1 to 2.4.4

   - bpo-46556(32): Deprecate undocumented support for using a *note
     pathlib.Path: 20e. object as a context manager.

   - bpo-46534(33): Implement PEP 673(34) *note typing.Self: 56b.  Patch
     by James Hilton-Balfe.

   - bpo-46522(35): Make various module ‘__getattr__’ AttributeErrors
     more closely match a typical AttributeError

   - bpo-46475(36): Add *note typing.Never: 64d. and *note
     typing.assert_never(): 64c.  Patch by Jelle Zijlstra.

   - bpo-46333(37): The ‘__eq__()’ and ‘__hash__()’ methods of *note
     typing.ForwardRef: 1748. now honor the ‘module’ parameter of *note
     typing.ForwardRef: 1748.  Forward references from different modules
     are now differentiated.

   - bpo-46246(38): Add missing ‘__slots__’ to
     ‘importlib.metadata.DeprecatedList’.  Patch by Arie Bovenberg.

   - bpo-46232(39): The *note ssl: bb. module now handles certificates
     with bit strings in DN correctly.

   - bpo-46195(40): *note typing.get_type_hints(): 657. no longer adds
     ‘Optional’ to parameters with ‘None’ as a default.  This aligns to
     changes to PEP 484 in ‘https://github.com/python/peps/pull/689’

   - bpo-31369(41): Add *note RegexFlag: 5d2. to ‘re.__all__’ and
     documented it.  Add ‘NOFLAG’ to indicate no flags being set.

   - bpo-45898(42): *note ctypes: 22. no longer defines ‘ffi_type_*’
     symbols in ‘cfield.c’.  The symbols have been provided by libffi
     for over a decade.

   - bpo-44953(43): Calling ‘operator.itemgetter’ objects and
     ‘operator.attrgetter’ objects is now faster due to use of the
     vectorcall calling convention.

   - bpo-44289(44): Fix an issue with *note is_tarfile(): 1749. method
     when using 'fileobj' argument: position in the 'fileobj' was
     advanced forward which made it unreadable with *note
     tarfile.TarFile.open(): 174a.

   - bpo-44011(45): Reimplement SSL/TLS support in asyncio, borrow the
     implementation from uvloop library.

   - bpo-41086(46): Make the *note configparser.ConfigParser: 1aa.
     constructor raise *note TypeError: 4dd. if the ‘interpolation’
     parameter is not of type ‘configparser.Interpolation’

   - bpo-29418(47): Implement *note inspect.ismethodwrapper(): 5f0. and
     fix *note inspect.isroutine(): 14de. for cases where methodwrapper
     is given.  Patch by Hakan Çelik.

   - bpo-14156(48): argparse.FileType now supports an argument of '-' in
     binary mode, returning the .buffer attribute of
     sys.stdin/sys.stdout as appropriate.  Modes including 'x' and 'a'
     are treated equivalently to 'w' when argument is '-'.  Patch
     contributed by Josh Rosenberg

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25707

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46877

   (3) https://bugs.python.org/issue?@action=redirect&bpo=46848

   (4) https://bugs.python.org/issue?@action=redirect&bpo=46736

   (5) https://bugs.python.org/issue?@action=redirect&bpo=44886

   (6) https://bugs.python.org/issue?@action=redirect&bpo=46827

   (7) https://bugs.python.org/issue?@action=redirect&bpo=46811

   (8) https://bugs.python.org/issue?@action=redirect&bpo=46252

   (9) https://bugs.python.org/issue?@action=redirect&bpo=46784

   (10) https://bugs.python.org/issue?@action=redirect&bpo=46786

   (11) https://bugs.python.org/issue?@action=redirect&bpo=39327

   (12) https://bugs.python.org/issue?@action=redirect&bpo=45390

   (13) https://bugs.python.org/issue?@action=redirect&bpo=46756

   (14) https://bugs.python.org/issue?@action=redirect&bpo=46737

   (15) https://bugs.python.org/issue?@action=redirect&bpo=46752

   (16) https://bugs.python.org/issue?@action=redirect&bpo=46724

   (17) https://bugs.python.org/issue?@action=redirect&bpo=46333

   (18) https://bugs.python.org/issue?@action=redirect&bpo=46643

   (19) https://bugs.python.org/issue?@action=redirect&bpo=45863

   (20) https://bugs.python.org/issue?@action=redirect&bpo=46066

   (21) https://bugs.python.org/issue?@action=redirect&bpo=46676

   (22) https://bugs.python.org/issue?@action=redirect&bpo=46323

   (23) https://bugs.python.org/issue?@action=redirect&bpo=46672

   (24) https://bugs.python.org/issue?@action=redirect&bpo=46659

   (25) https://bugs.python.org/issue?@action=redirect&bpo=46659

   (26) https://bugs.python.org/issue?@action=redirect&bpo=46655

   (27) https://bugs.python.org/issue?@action=redirect&bpo=45948

   (28) https://bugs.python.org/issue?@action=redirect&bpo=46626

   (29) https://bugs.python.org/issue?@action=redirect&bpo=46521

   (30) https://bugs.python.org/issue?@action=redirect&bpo=46571

   (31) https://bugs.python.org/issue?@action=redirect&bpo=46400

   (32) https://bugs.python.org/issue?@action=redirect&bpo=46556

   (33) https://bugs.python.org/issue?@action=redirect&bpo=46534

   (34) https://peps.python.org/pep-0673/

   (35) https://bugs.python.org/issue?@action=redirect&bpo=46522

   (36) https://bugs.python.org/issue?@action=redirect&bpo=46475

   (37) https://bugs.python.org/issue?@action=redirect&bpo=46333

   (38) https://bugs.python.org/issue?@action=redirect&bpo=46246

   (39) https://bugs.python.org/issue?@action=redirect&bpo=46232

   (40) https://bugs.python.org/issue?@action=redirect&bpo=46195

   (41) https://bugs.python.org/issue?@action=redirect&bpo=31369

   (42) https://bugs.python.org/issue?@action=redirect&bpo=45898

   (43) https://bugs.python.org/issue?@action=redirect&bpo=44953

   (44) https://bugs.python.org/issue?@action=redirect&bpo=44289

   (45) https://bugs.python.org/issue?@action=redirect&bpo=44011

   (46) https://bugs.python.org/issue?@action=redirect&bpo=41086

   (47) https://bugs.python.org/issue?@action=redirect&bpo=29418

   (48) https://bugs.python.org/issue?@action=redirect&bpo=14156


File: python.info,  Node: Documentation<18>,  Next: Tests<21>,  Prev: Library<23>,  Up: Python 3 11 0 alpha 6

1.23.24.3 Documentation
.......................

   - bpo-42238(1): ‘Doc/tools/rstlint.py’ has moved to its own
     repository and is now packaged on PyPI as ‘sphinx-lint’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42238


File: python.info,  Node: Tests<21>,  Next: Build<23>,  Prev: Documentation<18>,  Up: Python 3 11 0 alpha 6

1.23.24.4 Tests
...............

   - bpo-46913(1): Fix test_faulthandler.test_sigfpe() if Python is
     built with undefined behavior sanitizer (UBSAN): disable UBSAN on
     the faulthandler_sigfpe() function.  Patch by Victor Stinner.

   - bpo-46760(2): Remove bytecode offsets from expected values in
     test.test_dis module.  Reduces the obstacles to modifying the VM or
     compiler.

   - bpo-46708(3): Prevent default asyncio event loop policy
     modification warning after ‘test_asyncio’ execution.

   - bpo-46678(4): The function ‘make_legacy_pyc’ in
     ‘Lib/test/support/import_helper.py’ no longer fails when
     ‘PYTHONPYCACHEPREFIX’ is set to a directory on a different device
     from where tempfiles are stored.

   - bpo-46623(5): Skip test_pair() and test_speech128() of test_zlib on
     s390x since they fail if zlib uses the s390x hardware accelerator.
     Patch by Victor Stinner.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46913

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46760

   (3) https://bugs.python.org/issue?@action=redirect&bpo=46708

   (4) https://bugs.python.org/issue?@action=redirect&bpo=46678

   (5) https://bugs.python.org/issue?@action=redirect&bpo=46623


File: python.info,  Node: Build<23>,  Next: Windows<20>,  Prev: Tests<21>,  Up: Python 3 11 0 alpha 6

1.23.24.5 Build
...............

   - bpo-46860(1): Respect ‘--with-suffix’ when building on
     case-insensitive file systems.

   - bpo-46656(2): Building Python now requires a C11 compiler.
     Optional C11 features are not required.  Patch by Victor Stinner.

   - bpo-46656(3): Building Python now requires support for
     floating-point Not-a-Number (NaN): remove the ‘Py_NO_NAN’ macro.
     Patch by Victor Stinner.

   - bpo-46640(4): Building Python now requires a C99 ‘<math.h>’ header
     file providing a ‘NAN’ constant, or the ‘__builtin_nan()’ built-in
     function.  Patch by Victor Stinner.

   - bpo-46608(5): Exclude marshalled-frozen data if deep-freezing to
     save 300 KB disk space.  This includes adding a new ‘is_package’
     field to *note _frozen: 719.  Patch by Kumar Aditya.

   - bpo-40280(6): Fix wasm32-emscripten test failures and platform
     issues.  - Disable syscalls that are not supported or don't work,
     e.g.  wait, getrusage, prlimit, mkfifo, mknod, setres[gu]id,
     setgroups.  - Use fd_count to count open fds.  - Add more checks
     for subprocess and fork.  - Add workarounds for missing
     _multiprocessing and failing socket.accept().  - Enable bzip2.  -
     Disable large file support.  - Disable signal.alarm.

   - bpo-46430(7): Intern strings in deep-frozen modules.  Patch by
     Kumar Aditya.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46860

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46656

   (3) https://bugs.python.org/issue?@action=redirect&bpo=46656

   (4) https://bugs.python.org/issue?@action=redirect&bpo=46640

   (5) https://bugs.python.org/issue?@action=redirect&bpo=46608

   (6) https://bugs.python.org/issue?@action=redirect&bpo=40280

   (7) https://bugs.python.org/issue?@action=redirect&bpo=46430


File: python.info,  Node: Windows<20>,  Next: IDLE<14>,  Prev: Build<23>,  Up: Python 3 11 0 alpha 6

1.23.24.6 Windows
.................

   - bpo-46744(1): The default all users install directory for ARM64 is
     now under the native ‘Program Files’ folder, rather than ‘Program
     Files (Arm)’ which is intended for ARM (32-bit) files.

   - bpo-46567(2): Adds Tcl and Tk support for Windows ARM64.  This also
     adds IDLE to the installation.

   - bpo-46638(3): Ensures registry virtualization is consistently
     disabled.  For 3.10 and earlier, it remains enabled (some registry
     writes are protected), while for 3.11 and later it is disabled
     (registry modifications affect all applications).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46744

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46567

   (3) https://bugs.python.org/issue?@action=redirect&bpo=46638


File: python.info,  Node: IDLE<14>,  Next: C API<22>,  Prev: Windows<20>,  Up: Python 3 11 0 alpha 6

1.23.24.7 IDLE
..............

   - bpo-46630(1): Make query dialogs on Windows start with a cursor in
     the entry box.

   - bpo-45447(2): Apply IDLE syntax highlighting to ‘.pyi’ files.
     Patch by Alex Waygood and Terry Jan Reedy.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46630

   (2) https://bugs.python.org/issue?@action=redirect&bpo=45447


File: python.info,  Node: C API<22>,  Prev: IDLE<14>,  Up: Python 3 11 0 alpha 6

1.23.24.8 C API
...............

   - bpo-46748(1): Python's public headers no longer import
     ‘<stdbool.h>’, leaving code that embeds/extends Python free to
     define ‘bool’, ‘true’ and ‘false’.

   - bpo-46836(2): Move the *note PyFrameObject: 72d. type definition
     (‘struct _frame’) to the internal C API ‘pycore_frame.h’ header
     file.  Patch by Victor Stinner.

   - bpo-45459(3): Rename ‘Include/buffer.h’ header file to
     ‘Include/pybuffer.h’ to avoid conflicts with projects having an
     existing ‘buffer.h’ header file.  Patch by Victor Stinner.

   - bpo-45412(4): Remove the ‘HAVE_PY_SET_53BIT_PRECISION’ macro (moved
     to the internal C API). Patch by Victor Stinner.

   - bpo-46613(5): Added function *note PyType_GetModuleByDef(): 342,
     which allows access to module state when a method's defining class
     is not available.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46748

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46836

   (3) https://bugs.python.org/issue?@action=redirect&bpo=45459

   (4) https://bugs.python.org/issue?@action=redirect&bpo=45412

   (5) https://bugs.python.org/issue?@action=redirect&bpo=46613


File: python.info,  Node: Python 3 11 0 alpha 5,  Next: Python 3 11 0 alpha 4,  Prev: Python 3 11 0 alpha 6,  Up: Changelog（更動日誌）

1.23.25 Python 3.11.0 alpha 5
-----------------------------

'Release date: 2022-02-03'

* Menu:

* Core and Builtins: Core and Builtins<25>.
* Library: Library<24>.
* Documentation: Documentation<19>.
* Tests: Tests<22>.
* Build: Build<24>.
* Windows: Windows<21>.
* macOS: macOS<16>.
* IDLE: IDLE<15>.
* C API: C API<23>.


File: python.info,  Node: Core and Builtins<25>,  Next: Library<24>,  Up: Python 3 11 0 alpha 5

1.23.25.1 Core and Builtins
...........................

   - bpo-45773(1): Remove two invalid "peephole" optimizations from the
     bytecode compiler.

   - bpo-46564(2): Do not create frame objects when creating *note
     super: 483. object.  Patch by Kumar Aditya.

   - bpo-45885(3): Added more fined-grained specialization failure stats
     regarding the ‘COMPARE_OP’ bytecode.

   - bpo-44977(4): The delegation of *note int(): 23c. to ‘__trunc__()’
     is now deprecated.  Calling ‘int(a)’ when ‘type(a)’ implements
     ‘__trunc__()’ but not ‘__int__()’ or ‘__index__()’ now raises a
     *note DeprecationWarning: 18b.

   - bpo-46458(5): Reorder code emitted by the compiler for a *note try:
     68c.-*note except: 171. block so that the *note else: 172. block's
     code immediately follows the *note try: 68c. body (without a jump).
     This is more optimal for the happy path.

   - bpo-46527(6): Allow passing ‘iterable’ as a keyword argument to
     *note enumerate(): 13ea. again.  Patch by Jelle Zijlstra.

   - bpo-46528(7): Replace several stack manipulation instructions
     (‘DUP_TOP’, ‘DUP_TOP_TWO’, ‘ROT_TWO’, ‘ROT_THREE’, ‘ROT_FOUR’, and
     ‘ROT_N’) with new *note COPY: 6ad. and *note SWAP: 6ae.
     instructions.

   - bpo-46329(8): Use two or three bytecodes to implement most calls.

     Calls without named arguments are implemented as a sequence of two
     instructions: ‘PRECALL; CALL’.  Calls with named arguments are
     implemented as a sequence of three instructions: ‘PRECALL;
     KW_NAMES; CALL’.  There are two different ‘PRECALL’ instructions:
     ‘PRECALL_FUNTION’ and ‘PRECALL_METHOD’.  The latter pairs with
     ‘LOAD_METHOD’.

     This partition into pre-call and call allows better specialization,
     and thus better performance ultimately.

     There is no change in semantics.

   - bpo-46503(9): Fix an assert when parsing some invalid N escape
     sequences in f-strings.

   - bpo-46431(10): Improve error message on invalid calls to
     ‘BaseExceptionGroup.__new__()’.

   - bpo-46476(11): Fix memory leak in code objects generated by
     deepfreeze.  Patch by Kumar Aditya.

   - bpo-46481(12): Speed up calls to ‘weakref.ref.__call__()’ by using
     the PEP 590(13) ‘vectorcall’ calling convention.  Patch by Donghee
     Na.

   - bpo-46417(14): Fix a race condition on setting a type ‘__bases__’
     attribute: the internal function ‘add_subclass()’ now gets the
     ‘PyTypeObject.tp_subclasses’ member after calling *note
     PyWeakref_NewRef(): 1753. which can trigger a garbage collection
     which can indirectly modify ‘PyTypeObject.tp_subclasses’.  Patch by
     Victor Stinner.

   - bpo-46417(15): ‘python -X showrefcount’ now shows the total
     reference count after clearing and destroyed the main Python
     interpreter.  Previously, it was shown before.  Patch by Victor
     Stinner.

   - bpo-43683(16): Add ASYNC_GEN_WRAP opcode to wrap the value to be
     yielded in async generators.  Removes the need to special case
     async generators in the ‘YIELD_VALUE’ instruction.

   - bpo-46407(17): Optimize some modulo operations in
     ‘Objects/longobject.c’.  Patch by Jeremiah Vivian.

   - bpo-46409(18): Add new ‘RETURN_GENERATOR’ bytecode to make
     generators.  Simplifies calling Python functions in the VM, as they
     no longer any need to special case generator functions.

     Also add ‘JUMP_NO_INTERRUPT’ bytecode that acts like
     ‘JUMP_ABSOLUTE’, but does not check for interrupts.

   - bpo-46406(19): The integer division ‘//’ implementation has been
     optimized to better let the compiler understand its constraints.
     It can be 20% faster on the amd64 platform when dividing an int by
     a value smaller than ‘2**30’.

   - bpo-46383(20): Fix invalid signature of ‘_zoneinfo’'s ‘module_free’
     function to resolve a crash on wasm32-emscripten platform.

   - bpo-46361(21): Ensure that "small" integers created by *note
     int.from_bytes(): 1754. and *note decimal.Decimal: 27c. are
     properly cached.

   - bpo-46161(22): Fix the class building error when the arguments are
     constants and CALL_FUNCTION_EX is used.

   - bpo-46028(23): Fixes calculation of ‘sys._base_executable’ when
     inside a virtual environment that uses symlinks with different
     binary names than the base environment provides.

   - bpo-46091(24): Correctly calculate indentation levels for lines
     with whitespace character that are ended by line continuation
     characters.  Patch by Pablo Galindo

   - bpo-30512(25): Add CAN Socket support for NetBSD.

   - bpo-46045(26): Do not use POSIX semaphores on NetBSD

   - bpo-44024(27): Improve the *note TypeError: 4dd. message for
     non-string second arguments passed to the built-in functions *note
     getattr(): b78. and *note hasattr(): 479.  Patch by Géry Ogam.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45773

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46564

   (3) https://bugs.python.org/issue?@action=redirect&bpo=45885

   (4) https://bugs.python.org/issue?@action=redirect&bpo=44977

   (5) https://bugs.python.org/issue?@action=redirect&bpo=46458

   (6) https://bugs.python.org/issue?@action=redirect&bpo=46527

   (7) https://bugs.python.org/issue?@action=redirect&bpo=46528

   (8) https://bugs.python.org/issue?@action=redirect&bpo=46329

   (9) https://bugs.python.org/issue?@action=redirect&bpo=46503

   (10) https://bugs.python.org/issue?@action=redirect&bpo=46431

   (11) https://bugs.python.org/issue?@action=redirect&bpo=46476

   (12) https://bugs.python.org/issue?@action=redirect&bpo=46481

   (13) https://peps.python.org/pep-0590/

   (14) https://bugs.python.org/issue?@action=redirect&bpo=46417

   (15) https://bugs.python.org/issue?@action=redirect&bpo=46417

   (16) https://bugs.python.org/issue?@action=redirect&bpo=43683

   (17) https://bugs.python.org/issue?@action=redirect&bpo=46407

   (18) https://bugs.python.org/issue?@action=redirect&bpo=46409

   (19) https://bugs.python.org/issue?@action=redirect&bpo=46406

   (20) https://bugs.python.org/issue?@action=redirect&bpo=46383

   (21) https://bugs.python.org/issue?@action=redirect&bpo=46361

   (22) https://bugs.python.org/issue?@action=redirect&bpo=46161

   (23) https://bugs.python.org/issue?@action=redirect&bpo=46028

   (24) https://bugs.python.org/issue?@action=redirect&bpo=46091

   (25) https://bugs.python.org/issue?@action=redirect&bpo=30512

   (26) https://bugs.python.org/issue?@action=redirect&bpo=46045

   (27) https://bugs.python.org/issue?@action=redirect&bpo=44024


File: python.info,  Node: Library<24>,  Next: Documentation<19>,  Prev: Core and Builtins<25>,  Up: Python 3 11 0 alpha 5

1.23.25.2 Library
.................

   - bpo-46624(1): Restore support for non-integer arguments of *note
     random.randrange(): 810. and *note random.randint(): 11c7.

   - bpo-46591(2): Make the IDLE doc URL on the About IDLE dialog
     clickable.

   - bpo-46565(3): Remove loop variables that are leaking into modules'
     namespaces.

   - bpo-46553(4): In *note typing.get_type_hints(): 657, support
     evaluating bare stringified ‘ClassVar’ annotations.  Patch by
     Gregory Beauregard.

   - bpo-46544(5): Don't leak ‘x’ & ‘uspace’ intermediate vars in *note
     textwrap.TextWrapper: f70.

   - bpo-46487(6): Add the ‘get_write_buffer_limits’ method to
     ‘asyncio.transports.WriteTransport’ and to the SSL transport.

   - bpo-45173(7): Note the configparser deprecations will be removed in
     Python 3.12.

   - bpo-45162(8): The deprecated *note unittest: ef. APIs removed in
     3.11a1 have been temporarily restored to be removed in 3.12 while
     cleanups in external projects go in.

   - bpo-46539(9): In *note typing.get_type_hints(): 657, support
     evaluating stringified ‘ClassVar’ and ‘Final’ annotations inside
     ‘Annotated’.  Patch by Gregory Beauregard.

   - bpo-46510(10): Add missing test for *note types.TracebackType: a95.
     and *note types.FrameType: 1756.  Calculate them directly from the
     caught exception without calling *note sys.exc_info(): 630.

   - bpo-46491(11): Allow *note typing.Annotated: 8e1. to wrap *note
     typing.Final: 24c. and *note typing.ClassVar: 24b.  Patch by
     Gregory Beauregard.

   - bpo-46483(12): Remove *note __class_getitem__(): 6df. from *note
     pathlib.PurePath: 44e. as this class was not supposed to be
     generic.

   - bpo-46436(13): Fix command-line option ‘-d’/‘--directory’ in module
     *note http.server: 68. which is ignored when combined with
     command-line option ‘--cgi’.  Patch by Géry Ogam.

   - bpo-41403(14): Make ‘mock.patch()’ raise a *note TypeError: 4dd.
     with a relevant error message on invalid arg.  Previously it
     allowed a cryptic *note AttributeError: 2f6. to escape.

   - bpo-46474(15): In ‘importlib.metadata.EntryPoint.pattern’, avoid
     potential REDoS by limiting ambiguity in consecutive whitespace.

   - bpo-46474(16): Removed private method from
     ‘importlib.metadata.Path’.  Sync with importlib_metadata 4.10.0.

   - bpo-46470(17): Remove unused branch from
     ‘typing._remove_dups_flatten’

   - bpo-46469(18): *note asyncio: 8. generic classes now return *note
     types.GenericAlias: 78f. in ‘__class_getitem__’ instead of the same
     class.

   - bpo-41906(19): Support passing filter instances in the ‘filters’
     values of ‘handlers’ and ‘loggers’ in the dictionary passed to
     *note logging.config.dictConfig(): 1147.

   - bpo-46422(20): Use ‘dis.Positions’ in ‘dis.Instruction’ instead of
     a regular ‘tuple’.

   - bpo-46434(21): *note pdb: 94. now gracefully handles ‘help’ when
     ‘__doc__’ is missing, for example when run with pregenerated
     optimized ‘.pyc’ files.

   - bpo-43869(22): Python uses the same time Epoch on all platforms.
     Add an explicit unit test to ensure that it's the case.  Patch by
     Victor Stinner.

   - bpo-46414(23): Add *note typing.reveal_type(): 64f.  Patch by Jelle
     Zijlstra.

   - bpo-40280(24): *note subprocess: c1. now imports Windows-specific
     imports when ‘msvcrt’ module is available, and POSIX-specific
     imports on all other platforms.  This gives a clean exception when
     ‘_posixsubprocess’ is not available (e.g.  Emscripten browser
     target).

   - bpo-40066(25): ‘IntEnum’, ‘IntFlag’, and ‘StrEnum’ use the mixed-in
     type for their ‘str()’ and ‘format()’ output.

   - bpo-46316(26): Optimize *note pathlib.Path.iterdir(): 1525. by
     removing an unnecessary check for special entries.

   - bpo-29688(27): Document *note pathlib.Path.absolute(): 15a6. (which
     has always existed).

   - bpo-43012(28): The pathlib module's obsolete and internal
     ‘_Accessor’ class has been removed to prepare the terrain for
     upcoming enhancements to the module.

   - bpo-46258(29): Speed up *note math.isqrt(): 9a9. for small positive
     integers by replacing two division steps with a lookup table.

   - bpo-46242(30): Improve error message when creating a new *note
     enum.Enum: 5d6. type subclassing an existing ‘Enum’ with
     ‘_member_names_’ using ‘enum.Enum.__call__()’.

   - bpo-43118(31): Fix a bug in *note inspect.signature(): 6dc. that
     was causing it to fail on some subclasses of classes with a
     ‘__text_signature__’ referencing module globals.  Patch by Weipeng
     Hong.

   - bpo-26552(32): Fixed case where failing *note
     asyncio.ensure_future(): c1d. did not close the coroutine.  Patch
     by Kumar Aditya.

   - bpo-21987(33): Fix an issue with *note tarfile.TarFile.getmember():
     1757. getting a directory name with a trailing slash.

   - bpo-46124(34): Update *note zoneinfo: 11a. to rely on
     importlib.resources traversable API.

   - bpo-46103(35): Now *note inspect.getmembers(): 1758. only gets
     ‘__bases__’ attribute from class type.  Patch by Weipeng Hong.

   - bpo-46080(36): Fix exception in argparse help text generation if a
     ‘argparse.BooleanOptionalAction’ argument's default is
     ‘argparse.SUPPRESS’ and it has ‘help’ specified.  Patch by Felix
     Fontein.

   - bpo-44791(37): Fix substitution of *note ParamSpec: 142. in *note
     Concatenate: 768. with different parameter expressions.
     Substitution with a list of types returns now a tuple of types.
     Substitution with ‘Concatenate’ returns now a ‘Concatenate’ with
     concatenated lists of arguments.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46624

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46591

   (3) https://bugs.python.org/issue?@action=redirect&bpo=46565

   (4) https://bugs.python.org/issue?@action=redirect&bpo=46553

   (5) https://bugs.python.org/issue?@action=redirect&bpo=46544

   (6) https://bugs.python.org/issue?@action=redirect&bpo=46487

   (7) https://bugs.python.org/issue?@action=redirect&bpo=45173

   (8) https://bugs.python.org/issue?@action=redirect&bpo=45162

   (9) https://bugs.python.org/issue?@action=redirect&bpo=46539

   (10) https://bugs.python.org/issue?@action=redirect&bpo=46510

   (11) https://bugs.python.org/issue?@action=redirect&bpo=46491

   (12) https://bugs.python.org/issue?@action=redirect&bpo=46483

   (13) https://bugs.python.org/issue?@action=redirect&bpo=46436

   (14) https://bugs.python.org/issue?@action=redirect&bpo=41403

   (15) https://bugs.python.org/issue?@action=redirect&bpo=46474

   (16) https://bugs.python.org/issue?@action=redirect&bpo=46474

   (17) https://bugs.python.org/issue?@action=redirect&bpo=46470

   (18) https://bugs.python.org/issue?@action=redirect&bpo=46469

   (19) https://bugs.python.org/issue?@action=redirect&bpo=41906

   (20) https://bugs.python.org/issue?@action=redirect&bpo=46422

   (21) https://bugs.python.org/issue?@action=redirect&bpo=46434

   (22) https://bugs.python.org/issue?@action=redirect&bpo=43869

   (23) https://bugs.python.org/issue?@action=redirect&bpo=46414

   (24) https://bugs.python.org/issue?@action=redirect&bpo=40280

   (25) https://bugs.python.org/issue?@action=redirect&bpo=40066

   (26) https://bugs.python.org/issue?@action=redirect&bpo=46316

   (27) https://bugs.python.org/issue?@action=redirect&bpo=29688

   (28) https://bugs.python.org/issue?@action=redirect&bpo=43012

   (29) https://bugs.python.org/issue?@action=redirect&bpo=46258

   (30) https://bugs.python.org/issue?@action=redirect&bpo=46242

   (31) https://bugs.python.org/issue?@action=redirect&bpo=43118

   (32) https://bugs.python.org/issue?@action=redirect&bpo=26552

   (33) https://bugs.python.org/issue?@action=redirect&bpo=21987

   (34) https://bugs.python.org/issue?@action=redirect&bpo=46124

   (35) https://bugs.python.org/issue?@action=redirect&bpo=46103

   (36) https://bugs.python.org/issue?@action=redirect&bpo=46080

   (37) https://bugs.python.org/issue?@action=redirect&bpo=44791


File: python.info,  Node: Documentation<19>,  Next: Tests<22>,  Prev: Library<24>,  Up: Python 3 11 0 alpha 5

1.23.25.3 Documentation
.......................

   - bpo-46463(1): Fixes ‘escape4chm.py’ script used when building the
     CHM documentation file

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46463


File: python.info,  Node: Tests<22>,  Next: Build<24>,  Prev: Documentation<19>,  Up: Python 3 11 0 alpha 5

1.23.25.4 Tests
...............

   - bpo-43478(1): Mocks can no longer be provided as the specs for
     other Mocks.  As a result, an already-mocked object cannot be
     passed to ‘mock.Mock()’.  This can uncover bugs in tests since
     these Mock-derived Mocks will always pass certain tests (e.g.
     isinstance) and builtin assert functions (e.g.
     assert_called_once_with) will unconditionally pass.

   - bpo-46616(2): Ensures ‘test_importlib.test_windows’ cleans up
     registry keys after completion.

   - bpo-44359(3): test_ftplib now silently ignores socket errors to
     prevent logging unhandled threading exceptions.  Patch by Victor
     Stinner.

   - bpo-46600(4): Fix test_gdb.test_pycfunction() for Python built with
     ‘clang -Og’.  Tolerate inlined functions in the gdb traceback.
     Patch by Victor Stinner.

   - bpo-46542(5): Fix a Python crash in test_lib2to3 when using Python
     built in debug mode: limit the recursion limit.  Patch by Victor
     Stinner.

   - bpo-46576(6): test_peg_generator now disables compiler optimization
     when testing compilation of its own C extensions to significantly
     speed up the testing on non-debug builds of CPython.

   - bpo-46542(7): Fix ‘test_json’ tests checking for *note
     RecursionError: d12.: modify these tests to use
     ‘support.infinite_recursion()’.  Patch by Victor Stinner.

   - bpo-13886(8): Skip test_builtin PTY tests on non-ASCII characters
     if the readline module is loaded.  The readline module changes
     input() behavior, but test_builtin is not intended to test the
     readline module.  Patch by Victor Stinner.

   - bpo-40280(9): Add ‘test.support.requires_fork()’ decorators to mark
     tests that require a working *note os.fork(): 17b.

   - bpo-40280(10): Add ‘test.support.requires_subprocess()’ decorator
     to mark tests which require working *note subprocess: c1. module or
     ‘os.spawn*’.  The wasm32-emscripten platform has no support for
     processes.

   - bpo-46126(11): Disable 'descriptions' when running tests
     internally.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43478

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46616

   (3) https://bugs.python.org/issue?@action=redirect&bpo=44359

   (4) https://bugs.python.org/issue?@action=redirect&bpo=46600

   (5) https://bugs.python.org/issue?@action=redirect&bpo=46542

   (6) https://bugs.python.org/issue?@action=redirect&bpo=46576

   (7) https://bugs.python.org/issue?@action=redirect&bpo=46542

   (8) https://bugs.python.org/issue?@action=redirect&bpo=13886

   (9) https://bugs.python.org/issue?@action=redirect&bpo=40280

   (10) https://bugs.python.org/issue?@action=redirect&bpo=40280

   (11) https://bugs.python.org/issue?@action=redirect&bpo=46126


File: python.info,  Node: Build<24>,  Next: Windows<21>,  Prev: Tests<22>,  Up: Python 3 11 0 alpha 5

1.23.25.5 Build
...............

   - bpo-46602(1): Tidied up configure.ac so that conftest.c is
     truncated rather than appended.  This assists in the case where the
     'rm' of conftest.c fails to happen between tests.  Downstream
     issues such as a clobbered SOABI can result.

   - bpo-46600(2): Fix the test checking if the C compiler supports
     ‘-Og’ option in the ‘./configure’ script to also use ‘-Og’ on clang
     which supports it.  Patch by Victor Stinner.

   - bpo-38472(3): Fix GCC detection in setup.py when cross-compiling.
     The C compiler is now run with LC_ALL=C. Previously, the detection
     failed with a German locale.

   - bpo-46513(4): ‘configure’ no longer uses ‘AC_C_CHAR_UNSIGNED’ macro
     and ‘pyconfig.h’ no longer defines reserved symbol
     ‘__CHAR_UNSIGNED__’.

   - bpo-46471(5): Use global singletons for single byte bytes objects
     in deepfreeze.

   - bpo-46443(6): Deepfreeze now uses cached small integers as it saves
     some space for common small integers.

   - bpo-46429(7): Merge all deep-frozen files into one for space
     savings.  Patch by Kumar Aditya.

   - bpo-45569(8): The build now defaults to using 30-bit digits for
     Python integers.  Previously either 15-bit or 30-bit digits would
     be selected, depending on the platform.  15-bit digits may still be
     selected using the ‘--enable-big-digits=15’ option to the
     ‘configure’ script, or by defining ‘PYLONG_BITS_IN_DIGIT’ in
     ‘pyconfig.h’.

   - bpo-45925(9): Update Windows installer to use SQLite 3.37.2.

   - bpo-43112(10): Detect musl libc as a separate SOABI (tagged as
     ‘linux-musl’).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46602

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46600

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38472

   (4) https://bugs.python.org/issue?@action=redirect&bpo=46513

   (5) https://bugs.python.org/issue?@action=redirect&bpo=46471

   (6) https://bugs.python.org/issue?@action=redirect&bpo=46443

   (7) https://bugs.python.org/issue?@action=redirect&bpo=46429

   (8) https://bugs.python.org/issue?@action=redirect&bpo=45569

   (9) https://bugs.python.org/issue?@action=redirect&bpo=45925

   (10) https://bugs.python.org/issue?@action=redirect&bpo=43112


File: python.info,  Node: Windows<21>,  Next: macOS<16>,  Prev: Build<24>,  Up: Python 3 11 0 alpha 5

1.23.25.6 Windows
.................

   - bpo-33125(1): The traditional EXE/MSI based installer for Windows
     is now available for ARM64

   - bpo-46362(2): os.path.abspath("C:CON") is now fixed to return
     "\.CON", not the same path.  The regression was true of all legacy
     DOS devices such as COM1, LPT1, or NUL.

   - bpo-44934(3): The installer now offers a command-line only option
     to add the installation directory to the end of ‘PATH’ instead of
     at the start.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33125

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46362

   (3) https://bugs.python.org/issue?@action=redirect&bpo=44934


File: python.info,  Node: macOS<16>,  Next: IDLE<15>,  Prev: Windows<21>,  Up: Python 3 11 0 alpha 5

1.23.25.7 macOS
...............

   - bpo-45925(1): Update macOS installer to SQLite 3.37.2.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45925


File: python.info,  Node: IDLE<15>,  Next: C API<23>,  Prev: macOS<16>,  Up: Python 3 11 0 alpha 5

1.23.25.8 IDLE
..............

   - bpo-45296(1): Clarify close, quit, and exit in IDLE. In the File
     menu, 'Close' and 'Exit' are now 'Close Window' (the current one)
     and 'Exit' is now 'Exit IDLE' (by closing all windows).  In Shell,
     'quit()' and 'exit()' mean 'close Shell'.  If there are no other
     windows, this also exits IDLE.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45296


File: python.info,  Node: C API<23>,  Prev: IDLE<15>,  Up: Python 3 11 0 alpha 5

1.23.25.9 C API
...............

   - bpo-40170(1): Remove the ‘PyHeapType_GET_MEMBERS()’ macro.  It was
     exposed in the public C API by mistake, it must only be used by
     Python internally.  Use the ‘PyTypeObject.tp_members’ member
     instead.  Patch by Victor Stinner.

   - bpo-40170(2): Move _Py_GetAllocatedBlocks() and
     _PyObject_DebugMallocStats() private functions to the internal C
     API. Patch by Victor Stinner.

   - bpo-46433(3): The internal function _PyType_GetModuleByDef now
     correctly handles inheritance patterns involving static types.

   - bpo-45459(4): *note Py_buffer: 6fc. and various ‘Py_buffer’ related
     functions are now part of the limited API and stable ABI.

   - bpo-14916(5): Fixed bug in the tokenizer that prevented
     ‘PyRun_InteractiveOne’ from parsing from the provided FD.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40170

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40170

   (3) https://bugs.python.org/issue?@action=redirect&bpo=46433

   (4) https://bugs.python.org/issue?@action=redirect&bpo=45459

   (5) https://bugs.python.org/issue?@action=redirect&bpo=14916


File: python.info,  Node: Python 3 11 0 alpha 4,  Next: Python 3 11 0 alpha 3,  Prev: Python 3 11 0 alpha 5,  Up: Changelog（更動日誌）

1.23.26 Python 3.11.0 alpha 4
-----------------------------

'Release date: 2022-01-13'

* Menu:

* Core and Builtins: Core and Builtins<26>.
* Library: Library<25>.
* Documentation: Documentation<20>.
* Tests: Tests<23>.
* Build: Build<25>.
* Windows: Windows<22>.
* macOS: macOS<17>.
* C API: C API<24>.


File: python.info,  Node: Core and Builtins<26>,  Next: Library<25>,  Up: Python 3 11 0 alpha 4

1.23.26.1 Core and Builtins
...........................

   - bpo-46070(1): *note Py_EndInterpreter(): 1762. now explicitly
     untracks all objects currently tracked by the GC. Previously, if an
     object was used later by another interpreter, calling *note
     PyObject_GC_UnTrack(): 1475. on the object crashed if the previous
     or the next object of the ‘PyGC_Head’ structure became a dangling
     pointer.  Patch by Victor Stinner.

   - bpo-46347(2): Fix memory leak in PyEval_EvalCodeEx.

   - bpo-46339(3): Fix a crash in the parser when retrieving the error
     text for multi-line f-strings expressions that do not start in the
     first line of the string.  Patch by Pablo Galindo

   - bpo-46331(4): Do not set line number of instruction storing
     doc-string.  Fixes regression introduced in 3.11 alpha.

   - bpo-46314(5): Remove spurious "call" event when creating a lambda
     function that was accidentally introduced in 3.11a4.

   - bpo-46289(6): ASDL declaration of ‘FormattedValue’ has changed to
     reflect ‘conversion’ field is not optional.

   - bpo-46297(7): Fixed an interpreter crash on bootup with multiple
     PythonPaths set in the Windows registry.  Patch by Derzsi Dániel.

   - bpo-46237(8): Fix the line number of tokenizer errors inside
     f-strings.  Patch by Pablo Galindo.

   - bpo-46263(9): We always expect the "use_frozen_modules" config to
     be set, now that getpath.c was rewritten in pure Python and the
     logic improved.

   - bpo-46006(10): Fix a regression when a type method like
     ‘__init__()’ is modified in a subinterpreter.  Fix a regression in
     ‘_PyUnicode_EqualToASCIIId()’ and type ‘update_slot()’.  Revert the
     change which made the Unicode dictionary of interned strings
     compatible with subinterpreters: the internal interned dictionary
     is shared again by all interpreters.  Patch by Victor Stinner.

   - bpo-45923(11): Add RESUME opcode.  This is a logical no-op.  It is
     emitted by the compiler anywhere a Python function can be entered.
     It is used by the interpreter to perform tracing and optimizer
     checks.

   - bpo-46208(12): Fix the regression of os.path.normpath("A/../../B")
     not returning expected "../B" but "B".

   - bpo-46240(13): Correct the error message for unclosed parentheses
     when the tokenizer doesn't reach the end of the source when the
     error is reported.  Patch by Pablo Galindo

   - bpo-46009(14): Remove the ‘GEN_START’ opcode.

   - bpo-46235(15): Certain sequence multiplication operations like ‘[0]
     * 1_000’ are now faster due to reference-counting optimizations.
     Patch by Dennis Sweeney.

   - bpo-46221(16): ‘PREP_RERAISE_STAR’ no longer pushes ‘lasti’ to the
     stack.

   - bpo-46202(17): Remove ‘POP_EXCEPT_AND_RERAISE’ and replace it by an
     equivalent sequence of other opcodes.

   - bpo-46085(18): Fix iterator cache mechanism of ‘OrderedDict’.

   - bpo-46055(19): Speed up shifting operation involving integers less
     than ‘PyLong_BASE’.  Patch by Xinhang Xu.

   - bpo-46110(20): Add a maximum recursion check to the PEG parser to
     avoid stack overflow.  Patch by Pablo Galindo

   - bpo-46107(21): Fix bug where ‘ExceptionGroup.split()’ and
     ‘ExceptionGroup.subgroup()’ did not copy the exception group's
     ‘__note__’ field to the parts.

   - bpo-45711(22): The interpreter state's representation of handled
     exceptions (a.k.a exc_info, or _PyErr_StackItem) now has only the
     ‘exc_value’ field, ‘exc_type’ and ‘exc_traceback’ have been removed
     as their values can be derived from ‘exc_value’.

   - bpo-44525(23): Replace the four call bytecode instructions which
     one pre-call instruction and two call instructions.

     Removes ‘CALL_FUNCTION’, ‘CALL_FUNCTION_KW’, ‘CALL_METHOD’ and
     ‘CALL_METHOD_KW’.

     Adds ‘CALL_NO_KW’ and ‘CALL_KW’ call instructions, and
     ‘PRECALL_METHOD’ prefix for pairing with ‘LOAD_METHOD’.

   - bpo-46039(24): Remove the ‘YIELD_FROM’ instruction and replace it
     with the ‘SEND’ instruction which performs the same operation, but
     without the loop.

   - bpo-45635(25): The code called from ‘_PyErr_Display()’ was
     refactored to improve error handling.  It now exits immediately
     upon an unrecoverable error.

   - bpo-46054(26): Fix parser error when parsing non-utf8 characters in
     source files.  Patch by Pablo Galindo.

   - bpo-46042(27): Improve the location of the caret in *note
     SyntaxError: 173. exceptions emitted by the symbol table.  Patch by
     Pablo Galindo.

   - bpo-46049(28): Ensure ‘._pth’ files work as intended on platforms
     other than Windows.

   - bpo-46048(29): Fixes parsing of ‘._pth’ files on startup so that
     single-character paths are correctly read.

   - bpo-37971(30): Fix a bug where the line numbers given in a
     traceback when a decorator application raised an exception were
     wrong.

   - bpo-46031(31): Add *note POP_JUMP_IF_NOT_NONE: 16fc. and *note
     POP_JUMP_IF_NONE: 16fb. opcodes to speed up conditional jumps.

   - bpo-45654(32): Deepfreeze *note runpy: ac, patch by Kumar Aditya.

   - bpo-46025(33): Fix a crash in the *note atexit: 9. module involving
     functions that unregister themselves before raising exceptions.
     Patch by Pablo Galindo.

   - bpo-46000(34): Improve compatibility of the *note curses: 23.
     module with NetBSD curses.

   - bpo-44525(35): Specialize the CALL_FUNCTION instruction for calls
     to builtin types with a single argument.  Speeds up ‘range(x)’,
     ‘list(x)’, and specifically ‘type(obj)’.

   - bpo-42918(36): Fix bug where the built-in *note compile(): 178.
     function did not always raise a *note SyntaxError: 173. when passed
     multiple statements in 'single' mode.  Patch by Weipeng Hong.

   - bpo-45953(37): The main interpreter in _PyRuntimeState.interpreters
     is now statically allocated (as part of _PyRuntime).  Likewise for
     the initial thread state of each interpreter.  This means less
     allocation during runtime init, as well as better memory locality
     for these key state objects.

   - bpo-45292(38): Complete the PEP 654(39) implementation: add
     ‘except*’.

   - bpo-43413(40): Revert changes in ‘set.__init__’.  Subclass of *note
     set: 57d. needs to define a ‘__init__()’ method if it defines a
     ‘__new__()’ method with additional keyword parameters.

   - bpo-43931(41): Added the *note Py_Version: 6fa. constant which
     bears the same value as *note PY_VERSION_HEX: 6fb.  Patch by
     Gabriele N. Tornetta.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46070

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46347

   (3) https://bugs.python.org/issue?@action=redirect&bpo=46339

   (4) https://bugs.python.org/issue?@action=redirect&bpo=46331

   (5) https://bugs.python.org/issue?@action=redirect&bpo=46314

   (6) https://bugs.python.org/issue?@action=redirect&bpo=46289

   (7) https://bugs.python.org/issue?@action=redirect&bpo=46297

   (8) https://bugs.python.org/issue?@action=redirect&bpo=46237

   (9) https://bugs.python.org/issue?@action=redirect&bpo=46263

   (10) https://bugs.python.org/issue?@action=redirect&bpo=46006

   (11) https://bugs.python.org/issue?@action=redirect&bpo=45923

   (12) https://bugs.python.org/issue?@action=redirect&bpo=46208

   (13) https://bugs.python.org/issue?@action=redirect&bpo=46240

   (14) https://bugs.python.org/issue?@action=redirect&bpo=46009

   (15) https://bugs.python.org/issue?@action=redirect&bpo=46235

   (16) https://bugs.python.org/issue?@action=redirect&bpo=46221

   (17) https://bugs.python.org/issue?@action=redirect&bpo=46202

   (18) https://bugs.python.org/issue?@action=redirect&bpo=46085

   (19) https://bugs.python.org/issue?@action=redirect&bpo=46055

   (20) https://bugs.python.org/issue?@action=redirect&bpo=46110

   (21) https://bugs.python.org/issue?@action=redirect&bpo=46107

   (22) https://bugs.python.org/issue?@action=redirect&bpo=45711

   (23) https://bugs.python.org/issue?@action=redirect&bpo=44525

   (24) https://bugs.python.org/issue?@action=redirect&bpo=46039

   (25) https://bugs.python.org/issue?@action=redirect&bpo=45635

   (26) https://bugs.python.org/issue?@action=redirect&bpo=46054

   (27) https://bugs.python.org/issue?@action=redirect&bpo=46042

   (28) https://bugs.python.org/issue?@action=redirect&bpo=46049

   (29) https://bugs.python.org/issue?@action=redirect&bpo=46048

   (30) https://bugs.python.org/issue?@action=redirect&bpo=37971

   (31) https://bugs.python.org/issue?@action=redirect&bpo=46031

   (32) https://bugs.python.org/issue?@action=redirect&bpo=45654

   (33) https://bugs.python.org/issue?@action=redirect&bpo=46025

   (34) https://bugs.python.org/issue?@action=redirect&bpo=46000

   (35) https://bugs.python.org/issue?@action=redirect&bpo=44525

   (36) https://bugs.python.org/issue?@action=redirect&bpo=42918

   (37) https://bugs.python.org/issue?@action=redirect&bpo=45953

   (38) https://bugs.python.org/issue?@action=redirect&bpo=45292

   (39) https://peps.python.org/pep-0654/

   (40) https://bugs.python.org/issue?@action=redirect&bpo=43413

   (41) https://bugs.python.org/issue?@action=redirect&bpo=43931


File: python.info,  Node: Library<25>,  Next: Documentation<20>,  Prev: Core and Builtins<26>,  Up: Python 3 11 0 alpha 4

1.23.26.2 Library
.................

   - bpo-46342(1): The ‘@typing.final’ decorator now sets the
     ‘__final__’ attribute on the decorated object to allow runtime
     introspection.  Patch by Jelle Zijlstra.

   - bpo-46328(2): Added the *note sys.exception(): 631. method which
     returns the active exception instance.

   - bpo-46307(3): Add *note string.Template.is_valid(): 62c. and *note
     string.Template.get_identifiers(): 62b. methods.

   - bpo-46306(4): Assume that *note types.CodeType: 2b6. always has
     ‘types.CodeType.co_firstlineno’ in *note doctest: 31.

   - bpo-40479(5): Fix *note hashlib: 5e. 'usedforsecurity' option to
     work correctly with OpenSSL 3.0.0 in FIPS mode.

   - bpo-46070(6): Fix possible segfault when importing the *note
     asyncio: 8. module from different sub-interpreters in parallel.
     Patch by Erlend E. Aasland.

   - bpo-46244(7): Removed ‘__slots__’ from *note typing.ParamSpec: 142.
     and *note typing.TypeVar: 141.  They served no purpose.  Patch by
     Arie Bovenberg.

   - bpo-46278(8): Reflect ‘context’ argument in
     ‘AbstractEventLoop.call_*()’ methods.  Loop implementations already
     support it.

   - bpo-46269(9): Remove special-casing of ‘__new__’ in *note
     enum.Enum.__dir__(): 1764.

   - bpo-46266(10): Improve day constants in *note calendar: 10.

     Now all constants (‘MONDAY’ ...  ‘SUNDAY’) are documented, tested,
     and added to ‘__all__’.

   - bpo-46257(11): Optimized the mean, variance, and stdev functions in
     the statistics module.  If the input is an iterator, it is consumed
     in a single pass rather than eating memory by conversion to a list.
     The single pass algorithm is about twice as fast as the previous
     two pass code.

   - bpo-41011(12): Added two new variables to 'pyvenv.cfg' which is
     generated by *note venv: f9. module: 'executable' for the
     executable and 'command' for the command line used to create the
     environment.

   - bpo-46239(13): Improve error message when importing
     ‘asyncio.windows_events’ on non-Windows.

   - bpo-46238(14): Reuse ‘_winapi’ constants in
     ‘asyncio.windows_events’.

   - bpo-46222(15): Adding ‘SF_NOCACHE’ sendfile constant for FreeBSD
     for the posixmodule.

   - bpo-37295(16): Add fast path for ‘0 <= k <= n <= 67’ for *note
     math.comb(): 674.

   - bpo-46176(17): Adding the ‘MAP_STACK’ constant for the mmap module.

   - bpo-43424(18): Deprecate ‘webbrowser.MacOSXOSAScript._name’ and use
     ‘name’ instead.

   - bpo-45321(19): Added missing error codes to module
     ‘xml.parsers.expat.errors’.

   - bpo-46125(20): Refactor tests to test traversable API directly.
     Includes changes from importlib 5.4.0.

   - bpo-46118(21): Moved importlib.resources and its related
     functionality to a package.

   - bpo-37578(22): Add 'include_hidden' parameter to *note glob(): 280.
     and *note iglob(): 7ab. to match hidden files and directories when
     using special characters like ‘*’, ‘**’, ‘?’ and ‘[]’.

   - bpo-20369(23): *note concurrent.futures.wait(): 1765. no longer
     blocks forever when given duplicate Futures.  Patch by Kumar
     Aditya.

   - bpo-46105(24): Honor spec when generating requirement specs with
     urls and extras (importlib_metadata 4.8.3).

   - bpo-44893(25): EntryPoint objects are no longer tuples.
     Recommended means to access is by attribute ('.name', '.group') or
     accessor ('.load()').  Access by index is deprecated and will raise
     deprecation warning.

   - bpo-22815(26): Print unexpected successes together with failures
     and errors in summary in *note unittest.TextTestResult: 4d5.

   - bpo-22047(27): Calling ‘add_argument_group()’ on an argument group
     is deprecated.  Calling ‘add_argument_group()’ or
     ‘add_mutually_exclusive_group()’ on a mutually exclusive group is
     deprecated.

     These features were never supported and do not always work
     correctly.  The functions exist on the API by accident through
     inheritance and will be removed in the future.

   - bpo-26952(28): *note argparse: 5. raises *note ValueError: 1e7.
     with clear message when trying to render usage for an empty
     mutually exclusive group.  Previously it raised a cryptic *note
     IndexError: 14a3.

   - bpo-45615(29): Functions in the *note traceback: e7. module raise
     *note TypeError: 4dd. rather than *note AttributeError: 2f6. when
     an exception argument is not of type *note BaseException: 55f.

   - bpo-16594(30): Add allow allow_reuse_port flag in socketserver.

   - bpo-27718(31): Fix help for the *note signal: b4. module.  Some
     functions (e.g.  ‘signal()’ and ‘getsignal()’) were omitted.

   - bpo-46032(32): The ‘registry()’ method of *note
     functools.singledispatch(): 5df. functions checks now the first
     argument or the first parameter annotation and raises a TypeError
     if it is not supported.  Previously unsupported "types" were
     ignored (e.g.  ‘typing.List[int]’) or caused an error at calling
     time (e.g.  ‘list[int]’).

   - bpo-46014(33): Add ability to use ‘typing.Union’ and
     ‘types.UnionType’ as dispatch argument to
     ‘functools.singledispatch’.  Patch provided by Yurii Karabas.

   - bpo-27062(34): Add ‘__all__’ to *note inspect: 72, patch by Kumar
     Aditya.

   - bpo-46018(35): Ensure that *note math.expm1(): 1184. does not raise
     on underflow.

   - bpo-46016(36): Adding ‘F_DUP2FD’ and ‘F_DUP2FD_CLOEXEC’ constants
     from FreeBSD into the fcntl module.

   - bpo-45755(37): *note typing: ed. generic aliases now reveal the
     class attributes of the original generic class when passed to
     ‘dir()’.  This was the behavior up to Python 3.6, but was changed
     in 3.7-3.9.

   - bpo-45874(38): The empty query string, consisting of no query
     arguments, is now handled correctly in ‘urllib.parse.parse_qsl’.
     This caused problems before when strict parsing was enabled.

   - bpo-44674(39): Change how dataclasses disallows mutable default
     values.  It used to use a list of known types (list, dict, set).
     Now it disallows unhashable objects to be defaults.  It's using
     unhashability as a proxy for mutability.  Patch by Eric V. Smith,
     idea by Raymond Hettinger.

   - bpo-23882(40): Remove namespace package (PEP 420) support from
     unittest discovery.  It was introduced in Python 3.4 but has been
     broken since Python 3.7.

   - bpo-25066(41): Added a ‘__repr__()’ method to *note
     multiprocessing.Event: 1766. objects, patch by Kumar Aditya.

   - bpo-45643(42): Added *note signal.SIGSTKFLT: 1767. on platforms
     where this signal is defined.

   - bpo-44092(43): Fetch across rollback no longer raises *note
     InterfaceError: 623.  Instead we leave it to the SQLite library to
     handle these cases.  Patch by Erlend E. Aasland.

   - bpo-42413(44): Replace ‘concurrent.futures.TimeoutError’ and
     ‘asyncio.TimeoutError’ with builtin *note TimeoutError: 7d9, keep
     these names as deprecated aliases.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46342

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46328

   (3) https://bugs.python.org/issue?@action=redirect&bpo=46307

   (4) https://bugs.python.org/issue?@action=redirect&bpo=46306

   (5) https://bugs.python.org/issue?@action=redirect&bpo=40479

   (6) https://bugs.python.org/issue?@action=redirect&bpo=46070

   (7) https://bugs.python.org/issue?@action=redirect&bpo=46244

   (8) https://bugs.python.org/issue?@action=redirect&bpo=46278

   (9) https://bugs.python.org/issue?@action=redirect&bpo=46269

   (10) https://bugs.python.org/issue?@action=redirect&bpo=46266

   (11) https://bugs.python.org/issue?@action=redirect&bpo=46257

   (12) https://bugs.python.org/issue?@action=redirect&bpo=41011

   (13) https://bugs.python.org/issue?@action=redirect&bpo=46239

   (14) https://bugs.python.org/issue?@action=redirect&bpo=46238

   (15) https://bugs.python.org/issue?@action=redirect&bpo=46222

   (16) https://bugs.python.org/issue?@action=redirect&bpo=37295

   (17) https://bugs.python.org/issue?@action=redirect&bpo=46176

   (18) https://bugs.python.org/issue?@action=redirect&bpo=43424

   (19) https://bugs.python.org/issue?@action=redirect&bpo=45321

   (20) https://bugs.python.org/issue?@action=redirect&bpo=46125

   (21) https://bugs.python.org/issue?@action=redirect&bpo=46118

   (22) https://bugs.python.org/issue?@action=redirect&bpo=37578

   (23) https://bugs.python.org/issue?@action=redirect&bpo=20369

   (24) https://bugs.python.org/issue?@action=redirect&bpo=46105

   (25) https://bugs.python.org/issue?@action=redirect&bpo=44893

   (26) https://bugs.python.org/issue?@action=redirect&bpo=22815

   (27) https://bugs.python.org/issue?@action=redirect&bpo=22047

   (28) https://bugs.python.org/issue?@action=redirect&bpo=26952

   (29) https://bugs.python.org/issue?@action=redirect&bpo=45615

   (30) https://bugs.python.org/issue?@action=redirect&bpo=16594

   (31) https://bugs.python.org/issue?@action=redirect&bpo=27718

   (32) https://bugs.python.org/issue?@action=redirect&bpo=46032

   (33) https://bugs.python.org/issue?@action=redirect&bpo=46014

   (34) https://bugs.python.org/issue?@action=redirect&bpo=27062

   (35) https://bugs.python.org/issue?@action=redirect&bpo=46018

   (36) https://bugs.python.org/issue?@action=redirect&bpo=46016

   (37) https://bugs.python.org/issue?@action=redirect&bpo=45755

   (38) https://bugs.python.org/issue?@action=redirect&bpo=45874

   (39) https://bugs.python.org/issue?@action=redirect&bpo=44674

   (40) https://bugs.python.org/issue?@action=redirect&bpo=23882

   (41) https://bugs.python.org/issue?@action=redirect&bpo=25066

   (42) https://bugs.python.org/issue?@action=redirect&bpo=45643

   (43) https://bugs.python.org/issue?@action=redirect&bpo=44092

   (44) https://bugs.python.org/issue?@action=redirect&bpo=42413


File: python.info,  Node: Documentation<20>,  Next: Tests<23>,  Prev: Library<25>,  Up: Python 3 11 0 alpha 4

1.23.26.3 Documentation
.......................

   - bpo-46196(1): Document method *note cmd.Cmd.columnize(): 1769.

   - bpo-46120(2): State that ‘|’ is preferred for readability over
     ‘Union’ in the *note typing: ed. docs.

   - bpo-46109(3): Extracted ‘importlib.resources’ and
     ‘importlib.resources.abc’ documentation into separate files.

   - bpo-19737(4): Update the documentation for the *note globals():
     176a. function.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46196

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46120

   (3) https://bugs.python.org/issue?@action=redirect&bpo=46109

   (4) https://bugs.python.org/issue?@action=redirect&bpo=19737


File: python.info,  Node: Tests<23>,  Next: Build<25>,  Prev: Documentation<20>,  Up: Python 3 11 0 alpha 4

1.23.26.4 Tests
...............

   - bpo-46296(1): Add a test case for *note enum: 4c. with ‘_use_args_
     == True’ and ‘_member_type_ == object’.

   - bpo-46205(2): Fix hang in runtest_mp due to race condition

   - bpo-46263(3): Fix test_capi on FreeBSD 14-dev: instruct jemalloc to
     not fill freed memory with junk byte.

   - bpo-46262(4): Cover ‘ValueError’ path in tests for
     ‘enum.Flag._missing_()’.

   - bpo-46150(5): Now ‘fakename’ in
     ‘test_pathlib.PosixPathTest.test_expanduser’ is checked to be
     non-existent.

   - bpo-46129(6): Rewrite ‘asyncio.locks’ tests with *note
     unittest.IsolatedAsyncioTestCase: 2de. usage.

   - bpo-23819(7): Fixed *note asyncio: 8. tests in python optimized
     mode.  Patch by Kumar Aditya.

   - bpo-46114(8): Fix test case for OpenSSL 3.0.1 version.  OpenSSL 3.0
     uses ‘0xMNN00PP0L’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46296

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46205

   (3) https://bugs.python.org/issue?@action=redirect&bpo=46263

   (4) https://bugs.python.org/issue?@action=redirect&bpo=46262

   (5) https://bugs.python.org/issue?@action=redirect&bpo=46150

   (6) https://bugs.python.org/issue?@action=redirect&bpo=46129

   (7) https://bugs.python.org/issue?@action=redirect&bpo=23819

   (8) https://bugs.python.org/issue?@action=redirect&bpo=46114


File: python.info,  Node: Build<25>,  Next: Windows<22>,  Prev: Tests<23>,  Up: Python 3 11 0 alpha 4

1.23.26.5 Build
...............

   - bpo-44133(1): When Python is configured with *note
     -without-static-libpython: 832, the Python static library
     (libpython.a) is no longer built.  Patch by Victor Stinner.

   - bpo-44133(2): When Python is built without *note -enable-shared:
     807, the ‘python’ program is now linked to object files, rather
     than being linked to the Python static library (libpython.a), to
     make sure that all symbols are exported.  Previously, the linker
     omitted some symbols like the ‘Py_FrozenMain()’ function.  Patch by
     Victor Stinner.

   - bpo-40280(3): The ‘configure’ script has a new option
     ‘--with-emscripten-target’ to select browser or node as Emscripten
     build target.

   - bpo-46315(4): Added and fixed ‘#ifdef HAVE_FEATURE’ checks for
     functionality that is not available on WASI platform.

   - bpo-45723(5): Fixed a regression in ‘configure’ check for *note
     select.epoll(): f36.

   - bpo-46263(6): ‘configure’ no longer sets ‘MULTIARCH’ on FreeBSD
     platforms.

   - bpo-46106(7): Updated OpenSSL to 1.1.1m in Windows builds, macOS
     installer builds, and CI. Patch by Kumar Aditya.

   - bpo-46088(8): Automatically detect or install bootstrap Python
     runtime when building from Visual Studio.

   - bpo-46072(9): Add a -with-pystats configure option to turn on
     internal statistics gathering.

   - bpo-40280(10): A new directory ‘Tools/wasm’ contains
     WebAssembly-related helpers like ‘config.site’ override for
     wasm32-emscripten, wasm assets generator to bundle the stdlib, and
     a README.

   - bpo-46023(11): ‘makesetup’ no longer builds extensions that have
     been marked as 'disabled'.  This allows users to disable modules in
     ‘Modules/Setup.local’.

   - bpo-45949(12): Use pure Python ‘freeze_module’ for all but
     importlib bootstrap files.  ‘--with-freeze-module’ ‘configure’
     option is no longer needed for cross builds.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=44133

   (2) https://bugs.python.org/issue?@action=redirect&bpo=44133

   (3) https://bugs.python.org/issue?@action=redirect&bpo=40280

   (4) https://bugs.python.org/issue?@action=redirect&bpo=46315

   (5) https://bugs.python.org/issue?@action=redirect&bpo=45723

   (6) https://bugs.python.org/issue?@action=redirect&bpo=46263

   (7) https://bugs.python.org/issue?@action=redirect&bpo=46106

   (8) https://bugs.python.org/issue?@action=redirect&bpo=46088

   (9) https://bugs.python.org/issue?@action=redirect&bpo=46072

   (10) https://bugs.python.org/issue?@action=redirect&bpo=40280

   (11) https://bugs.python.org/issue?@action=redirect&bpo=46023

   (12) https://bugs.python.org/issue?@action=redirect&bpo=45949


File: python.info,  Node: Windows<22>,  Next: macOS<17>,  Prev: Build<25>,  Up: Python 3 11 0 alpha 4

1.23.26.6 Windows
.................

   - bpo-46217(1): Removed parameter that is unsupported on Windows 8.1
     and early Windows 10 and may have caused build or runtime failures.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46217


File: python.info,  Node: macOS<17>,  Next: C API<24>,  Prev: Windows<22>,  Up: Python 3 11 0 alpha 4

1.23.26.7 macOS
...............

   - bpo-40477(1): The Python Launcher app for macOS now properly
     launches scripts and, if necessary, the Terminal app when running
     on recent macOS releases.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40477


File: python.info,  Node: C API<24>,  Prev: macOS<17>,  Up: Python 3 11 0 alpha 4

1.23.26.8 C API
...............

   - bpo-46236(1): Fix a bug in *note PyFunction_GetAnnotations(): 16bd.
     that caused it to return a ‘tuple’ instead of a ‘dict’.

   - bpo-46140(2): *note PyBuffer_GetPointer(): 6fd, *note
     PyBuffer_FromContiguous(): 700, *note PyBuffer_ToContiguous(): 6ff.
     and *note PyMemoryView_FromBuffer(): 705. now take buffer info by
     ‘const Py_buffer *’ instead of ‘Py_buffer *’, as they do not need
     mutability.  *note PyBuffer_FromContiguous(): 700. also now takes
     the source buffer as ‘const void *’, and similarly *note
     PyBuffer_GetPointer(): 6fd. takes the strides as ‘const Py_ssize_t
     *’.

   - bpo-45855(3): Document that the 'no_block' argument to *note
     PyCapsule_Import(): 1770. is a no-op now.

   - bpo-45855(4): Replaced deprecated usage of *note
     PyImport_ImportModuleNoBlock(): 388. with *note
     PyImport_ImportModule(): 389. in stdlib modules.  Patch by Kumar
     Aditya.

   - bpo-46007(5): The ‘PyUnicode_CHECK_INTERNED()’ macro has been
     excluded from the limited C API. It was never usable there, because
     it used internal structures which are not available in the limited
     C API. Patch by Victor Stinner.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46236

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46140

   (3) https://bugs.python.org/issue?@action=redirect&bpo=45855

   (4) https://bugs.python.org/issue?@action=redirect&bpo=45855

   (5) https://bugs.python.org/issue?@action=redirect&bpo=46007


File: python.info,  Node: Python 3 11 0 alpha 3,  Next: Python 3 11 0 alpha 2,  Prev: Python 3 11 0 alpha 4,  Up: Changelog（更動日誌）

1.23.27 Python 3.11.0 alpha 3
-----------------------------

'Release date: 2021-12-08'

* Menu:

* Core and Builtins: Core and Builtins<27>.
* Library: Library<26>.
* Documentation: Documentation<21>.
* Tests: Tests<24>.
* Build: Build<26>.
* Windows: Windows<23>.
* macOS: macOS<18>.
* C API: C API<25>.


File: python.info,  Node: Core and Builtins<27>,  Next: Library<26>,  Up: Python 3 11 0 alpha 3

1.23.27.1 Core and Builtins
...........................

   - bpo-46009(1): Restore behavior from 3.9 and earlier when sending
     non-None to newly started generator.  In 3.9 this did not affect
     the state of the generator.  In 3.10.0 and 3.10.1
     ‘gen_func().send(0)’ is equivalent to
     ‘gen_func().throw(TypeError(...)’ which exhausts the generator.  In
     3.10.2 onward, the behavior has been reverted to that of 3.9.

   - bpo-46004(2): Fix the *note SyntaxError: 173. location for errors
     involving for loops with invalid targets.  Patch by Pablo Galindo

   - bpo-45711(3): ‘_PyErr_ChainStackItem()’ no longer normalizes
     ‘exc_info’ (including setting the traceback on the exception
     instance) because ‘exc_info’ is always normalized.

   - bpo-45607(4): The ‘__note__’ field was added to *note
     BaseException: 55f.  It is ‘None’ by default but can be set to a
     string which is added to the exception's traceback.

   - bpo-45947(5): Place pointers to dict and values immediately before
     GC header.  This reduces number of dependent memory loads to access
     either dict or values from 3 to 1.

   - bpo-45915(6): ‘is_valid_fd’ now uses faster ‘fcntl(fd, F_GETFD)’ on
     Linux, macOS, and Windows.

   - bpo-44530(7): Reverts a change to the ‘code.__new__’ *note audit
     event: 1773. from an earlier prerelease.

   - bpo-42268(8): Fail the configure step if the selected compiler
     doesn't support memory sanitizer.  Patch by Pablo Galindo

   - bpo-45711(9): The three values of ‘exc_info’ are now always
     consistent with each other.  In particular, the ‘type’ and
     ‘traceback’ fields are now derived from the exception instance.
     This impacts the return values of *note sys.exc_info(): 630. and
     *note PyErr_GetExcInfo(): 716. if the exception instance is
     modified while the exception is handled, as well as *note
     PyErr_SetExcInfo(): 715, which now ignores the ‘type’ and
     ‘traceback’ arguments provided to it.

   - bpo-45727(10): Refine the custom syntax error that suggests that a
     comma may be missing to trigger only when the expressions are
     detected between parentheses or brackets.  Patch by Pablo Galindo

   - bpo-45885(11): Specialized the ‘COMPARE_OP’ opcode using the PEP
     659 machinery.

   - bpo-45786(12): Allocate space for the interpreter frame in the
     frame object, to avoid an additional allocation when the frame
     object outlives the frame activation.

   - bpo-45614(13): Fix *note traceback: e7. display for exceptions with
     invalid module name.

   - bpo-45813(14): Fix crash when calling coro.cr_frame.clear() after
     coroutine has been freed.

   - bpo-45811(15): Improve the tokenizer errors when encountering
     invisible control characters in the parser.  Patch by Pablo Galindo

   - bpo-45848(16): Allow the parser to obtain error lines directly from
     encoded files.  Patch by Pablo Galindo

   - bpo-45709(17): Restore behavior from 3.10 when tracing an exception
     raised within a with statement.

   - bpo-44525(18): Adds new *note COPY_FREE_VARS: 6a1. opcode, to make
     copying of free variables from function to frame explicit.  Helps
     optimization of calls to Python function.

   - bpo-45829(19): Specialize *note BINARY_SUBSCR: 163f. for classes
     with a ‘__getitem__’ method implemented in Python

   - bpo-45826(20): Fixed a crash when calling ‘.with_traceback(None)’
     on ‘NameError’.  This occurs internally in
     ‘unittest.TestCase.assertRaises()’.

   - bpo-45822(21): Fixed a bug in the parser that was causing it to not
     respect PEP 263(22) coding cookies when no flags are provided.
     Patch by Pablo Galindo

   - bpo-45820(23): Fix a segfault when the parser fails without reading
     any input.  Patch by Pablo Galindo

   - bpo-45636(24): Simplify the implementation of *note BINARY_OP: 6aa.
     by indexing into an array of function pointers (rather than
     switching on the oparg).

   - bpo-42540(25): Fix crash when *note os.fork(): 17b. is called with
     an active non-default memory allocator.

   - bpo-45738(26): Fix computation of error location for invalid
     continuation characters in the parser.  Patch by Pablo Galindo.

   - bpo-45636(27): Remove an existing "fast path" for old-style string
     formatting, since it no longer appears to have any measurable
     impact.

   - bpo-45753(28): Make recursion checks a bit more efficient by
     tracking amount of calls left before overflow.

   - bpo-45773(29): Fix a compiler hang when attempting to optimize
     certain jump patterns.

   - bpo-45764(30): The parser now gives a better error message when
     leaving out the opening parenthesis ‘(’ after a ‘def’-statement:

          >>> def f:
            File "<stdin>", line 1
              def f:
                   ^
          SyntaxError: expected '('

   - bpo-45609(31): Specialized the ‘STORE_SUBSCR’ opcode using the PEP
     659 machinery.

   - bpo-45636(32): Replace all numeric ‘BINARY_*’ and ‘INPLACE_*’
     instructions with a single *note BINARY_OP: 6aa. implementation.

   - bpo-45582(33): Path calculation (known as ‘getpath’) has been
     reimplemented as a frozen Python module.  This should have no
     visible impact, but may affect calculation of all paths referenced
     in *note sys: c3. and *note sysconfig: c5.

   - bpo-45450(34): Improve the syntax error message for parenthesized
     arguments.  Patch by Pablo Galindo.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46009

   (2) https://bugs.python.org/issue?@action=redirect&bpo=46004

   (3) https://bugs.python.org/issue?@action=redirect&bpo=45711

   (4) https://bugs.python.org/issue?@action=redirect&bpo=45607

   (5) https://bugs.python.org/issue?@action=redirect&bpo=45947

   (6) https://bugs.python.org/issue?@action=redirect&bpo=45915

   (7) https://bugs.python.org/issue?@action=redirect&bpo=44530

   (8) https://bugs.python.org/issue?@action=redirect&bpo=42268

   (9) https://bugs.python.org/issue?@action=redirect&bpo=45711

   (10) https://bugs.python.org/issue?@action=redirect&bpo=45727

   (11) https://bugs.python.org/issue?@action=redirect&bpo=45885

   (12) https://bugs.python.org/issue?@action=redirect&bpo=45786

   (13) https://bugs.python.org/issue?@action=redirect&bpo=45614

   (14) https://bugs.python.org/issue?@action=redirect&bpo=45813

   (15) https://bugs.python.org/issue?@action=redirect&bpo=45811

   (16) https://bugs.python.org/issue?@action=redirect&bpo=45848

   (17) https://bugs.python.org/issue?@action=redirect&bpo=45709

   (18) https://bugs.python.org/issue?@action=redirect&bpo=44525

   (19) https://bugs.python.org/issue?@action=redirect&bpo=45829

   (20) https://bugs.python.org/issue?@action=redirect&bpo=45826

   (21) https://bugs.python.org/issue?@action=redirect&bpo=45822

   (22) https://peps.python.org/pep-0263/

   (23) https://bugs.python.org/issue?@action=redirect&bpo=45820

   (24) https://bugs.python.org/issue?@action=redirect&bpo=45636

   (25) https://bugs.python.org/issue?@action=redirect&bpo=42540

   (26) https://bugs.python.org/issue?@action=redirect&bpo=45738

   (27) https://bugs.python.org/issue?@action=redirect&bpo=45636

   (28) https://bugs.python.org/issue?@action=redirect&bpo=45753

   (29) https://bugs.python.org/issue?@action=redirect&bpo=45773

   (30) https://bugs.python.org/issue?@action=redirect&bpo=45764

   (31) https://bugs.python.org/issue?@action=redirect&bpo=45609

   (32) https://bugs.python.org/issue?@action=redirect&bpo=45636

   (33) https://bugs.python.org/issue?@action=redirect&bpo=45582

   (34) https://bugs.python.org/issue?@action=redirect&bpo=45450


File: python.info,  Node: Library<26>,  Next: Documentation<21>,  Prev: Core and Builtins<27>,  Up: Python 3 11 0 alpha 3

1.23.27.2 Library
.................

   - bpo-27946(1): Fix possible crash when getting an attribute of *note
     xml.etree.ElementTree.Element: 2e2. simultaneously with replacing
     the ‘attrib’ dict.

   - bpo-45711(2): Make *note asyncio: 8. normalize exceptions as soon
     as they are captured with *note PyErr_Fetch(): 3bb, and before they
     are stored as an exc_info triplet.  This brings *note asyncio: 8.
     in line with the rest of the codebase, where an exc_info triplet is
     always normalized.

   - bpo-23819(3): Replaced asserts with exceptions in asyncio, patch by
     Kumar Aditya.

   - bpo-13236(4): *note unittest.TextTestResult: 4d5. and *note
     unittest.TextTestRunner: 1644. flush now the output stream more
     often.

   - bpo-45917(5): Added *note math.exp2(): 606.:, which returns 2
     raised to the power of x.

   - bpo-37658(6): Fix issue when on certain conditions
     ‘asyncio.wait_for()’ may allow a coroutine to complete
     successfully, but fail to return the result, potentially causing
     memory leaks or other issues.

   - bpo-45876(7): Improve the accuracy of stdev() and pstdev() in the
     statistics module.  When the inputs are floats or fractions, the
     output is a correctly rounded float

   - bpo-44649(8): Handle dataclass(slots=True) with a field that has
     default a default value, but for which init=False.

   - bpo-45803(9): Added missing kw_only parameter to
     dataclasses.make_dataclass().

   - bpo-45837(10): The ‘turtle.RawTurtle.settiltangle()’ is deprecated
     since Python 3.1, it now emits a deprecation warning and will be
     removed in Python 3.13.

     Use ‘turtle.RawTurtle.tiltangle()’ instead.

     ‘turtle.RawTurtle.tiltangle()’ was earlier incorrectly marked as
     deprecated, its docstring has been corrected.

     Patch by Hugo van Kemenade.

   - bpo-45831(11): *note faulthandler: 4e. can now write ASCII-only
     strings (like filenames and function names) with a single write()
     syscall when dumping a traceback.  It reduces the risk of getting
     an unreadable dump when two threads or two processes dump a
     traceback to the same file (like stderr) at the same time.  Patch
     by Victor Stinner.

   - bpo-45828(12): ‘sqlite’ C callbacks now use unraisable exceptions
     if callback tracebacks are enabled.  Patch by Erlend E. Aasland.

   - bpo-41735(13): Fix thread lock in ‘zlib.Decompress.flush()’ method
     before ‘PyObject_GetBuffer’.

   - bpo-45235(14): Reverted an argparse bugfix that caused regression
     in the handling of default arguments for subparsers.  This
     prevented leaf level arguments from taking precedence over root
     level arguments.

   - bpo-45754(15): Fix a regression in Python 3.11a1 and 3.11a2 where
     *note sqlite3: ba. incorrectly would use ‘SQLITE_LIMIT_LENGTH’ when
     checking SQL statement lengths.  Now, ‘SQLITE_LIMIT_SQL_LENGTH’ is
     used.  Patch by Erlend E. Aasland.

   - bpo-45766(16): Added 'proportional' option to *note
     statistics.linear_regression(): 7d5.

   - bpo-45765(17): In importlib.metadata, fix distribution discovery
     for an empty path.

   - bpo-45757(18): Fix bug where *note dis: 30. produced an incorrect
     oparg when *note EXTENDED_ARG: 16a8. is followed by an opcode that
     does not use its argument.

   - bpo-45644(19): In-place JSON file formatting using ‘python3 -m
     json.tool infile infile’ now works correctly, previously it left
     the file empty.  Patch by Chris Wesseling.

   - bpo-45703(20): When a namespace package is imported before another
     module from the same namespace is created/installed in a different
     *note sys.path: 37f. location while the program is running, calling
     the *note importlib.invalidate_caches(): bb7. function will now
     also guarantee the new module is noticed.

   - bpo-45535(21): Improve output of ‘dir()’ with Enums.

   - bpo-45664(22): Fix *note types.resolve_bases(): b43. and *note
     types.new_class(): 10fa. for *note types.GenericAlias: 78f.
     instance as a base.

   - bpo-45663(23): Fix *note dataclasses.is_dataclass(): 1775. for
     dataclasses which are subclasses of *note types.GenericAlias: 78f.

   - bpo-45662(24): Fix the repr of ‘dataclasses.InitVar’ with a type
     alias to the built-in class, e.g.  ‘InitVar[list[int]]’.

   - bpo-43137(25): Launch GNOME web browsers via gio tool instead of
     obsolete gvfs-open

   - bpo-45429(26): On Windows, *note time.sleep(): 642. now uses a
     waitable timer which supports high-resolution timers.  Patch by
     Donghee Na and Eryk Sun.

   - bpo-37295(27): Optimize *note math.comb(): 674. and *note
     math.perm(): 675.

   - bpo-45514(28): Deprecated legacy functions in *note
     importlib.resources: 6f.

   - bpo-45507(29): Add tests for truncated/missing trailers in
     gzip.decompress implementation.

   - bpo-45359(30): Implement PEP 585(31) for *note
     graphlib.TopologicalSorter: 886.

   - bpo-44733(32): Add ‘max_tasks_per_child’ to *note
     concurrent.futures.ProcessPoolExecutor: 893.  This allows users to
     specify the maximum number of tasks a single process should execute
     before the process needs to be restarted.

   - bpo-28806(33): Improve netrc library.  netrc file no longer needs
     to contain all tokens.  And if the login name is anonymous,
     security check is no longer need.

   - bpo-43498(34): Avoid a possible '"RuntimeError: dictionary changed
     size during iteration"' when adjusting the process count of
     ‘ProcessPoolExecutor’.

   - bpo-42158(35): Add MIME types for N-quads, N-triples, Notation3 and
     TriG to ‘mimetypes’.

   - bpo-30533(36): Add *note inspect.getmembers_static(): 5ef. , it
     return all members without triggering dynamic lookup via the
     descriptor protocol.  Patch by Weipeng Hong.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27946

   (2) https://bugs.python.org/issue?@action=redirect&bpo=45711

   (3) https://bugs.python.org/issue?@action=redirect&bpo=23819

   (4) https://bugs.python.org/issue?@action=redirect&bpo=13236

   (5) https://bugs.python.org/issue?@action=redirect&bpo=45917

   (6) https://bugs.python.org/issue?@action=redirect&bpo=37658

   (7) https://bugs.python.org/issue?@action=redirect&bpo=45876

   (8) https://bugs.python.org/issue?@action=redirect&bpo=44649

   (9) https://bugs.python.org/issue?@action=redirect&bpo=45803

   (10) https://bugs.python.org/issue?@action=redirect&bpo=45837

   (11) https://bugs.python.org/issue?@action=redirect&bpo=45831

   (12) https://bugs.python.org/issue?@action=redirect&bpo=45828

   (13) https://bugs.python.org/issue?@action=redirect&bpo=41735

   (14) https://bugs.python.org/issue?@action=redirect&bpo=45235

   (15) https://bugs.python.org/issue?@action=redirect&bpo=45754

   (16) https://bugs.python.org/issue?@action=redirect&bpo=45766

   (17) https://bugs.python.org/issue?@action=redirect&bpo=45765

   (18) https://bugs.python.org/issue?@action=redirect&bpo=45757

   (19) https://bugs.python.org/issue?@action=redirect&bpo=45644

   (20) https://bugs.python.org/issue?@action=redirect&bpo=45703

   (21) https://bugs.python.org/issue?@action=redirect&bpo=45535

   (22) https://bugs.python.org/issue?@action=redirect&bpo=45664

   (23) https://bugs.python.org/issue?@action=redirect&bpo=45663

   (24) https://bugs.python.org/issue?@action=redirect&bpo=45662

   (25) https://bugs.python.org/issue?@action=redirect&bpo=43137

   (26) https://bugs.python.org/issue?@action=redirect&bpo=45429

   (27) https://bugs.python.org/issue?@action=redirect&bpo=37295

   (28) https://bugs.python.org/issue?@action=redirect&bpo=45514

   (29) https://bugs.python.org/issue?@action=redirect&bpo=45507

   (30) https://bugs.python.org/issue?@action=redirect&bpo=45359

   (31) https://peps.python.org/pep-0585/

   (32) https://bugs.python.org/issue?@action=redirect&bpo=44733

   (33) https://bugs.python.org/issue?@action=redirect&bpo=28806

   (34) https://bugs.python.org/issue?@action=redirect&bpo=43498

   (35) https://bugs.python.org/issue?@action=redirect&bpo=42158

   (36) https://bugs.python.org/issue?@action=redirect&bpo=30533


File: python.info,  Node: Documentation<21>,  Next: Tests<24>,  Prev: Library<26>,  Up: Python 3 11 0 alpha 3

1.23.27.3 Documentation
.......................

   - bpo-42238(1): ‘make -C Doc suspicious’ will be removed soon in
     favor of ‘make -C Doc check’, mark it as deprecated.

   - bpo-45840(2): Improve cross-references in the documentation for the
     data model.

   - bpo-45640(3): Properly marked-up grammar tokens in the
     documentation are now clickable and take you to the definition of a
     given piece of grammar.  Patch by Arthur Milchior.

   - bpo-45788(4): Link doc for sys.prefix to sysconfig doc on
     installation paths.

   - bpo-45772(5): ‘socket.socket’ documentation is corrected to a class
     from a function.

   - bpo-45392(6): Update the docstring of the *note type: cef. built-in
     to remove a redundant line and to mention keyword arguments for the
     constructor.

   - bpo-45250(7): Update the documentation to note that CPython does
     not consistently require iterators to define ‘__iter__’.

   - bpo-25381(8): In the extending chapter of the extending doc, update
     a paragraph about the global variables containing exception
     information.

   - bpo-43905(9): Expanded *note astuple(): 162c. and *note asdict():
     1622. docs, warning about deepcopy being applied and providing a
     workaround.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42238

   (2) https://bugs.python.org/issue?@action=redirect&bpo=45840

   (3) https://bugs.python.org/issue?@action=redirect&bpo=45640

   (4) https://bugs.python.org/issue?@action=redirect&bpo=45788

   (5) https://bugs.python.org/issue?@action=redirect&bpo=45772

   (6) https://bugs.python.org/issue?@action=redirect&bpo=45392

   (7) https://bugs.python.org/issue?@action=redirect&bpo=45250

   (8) https://bugs.python.org/issue?@action=redirect&bpo=25381

   (9) https://bugs.python.org/issue?@action=redirect&bpo=43905


File: python.info,  Node: Tests<24>,  Next: Build<26>,  Prev: Documentation<21>,  Up: Python 3 11 0 alpha 3

1.23.27.4 Tests
...............

   - bpo-45695(1): Out-of-tree builds with a read-only source directory
     are now tested by CI.

   - bpo-19460(2): Add new Test for
     ‘Lib/email/mime/nonmultipart.py::MIMENonMultipart’.

   - bpo-45835(3): Fix race condition in test_queue tests with multiple
     "feeder" threads.

   - bpo-45783(4): The test for the freeze tool now handles file moves
     and deletions.

   - bpo-45745(5): Remove the ‘--findleaks’ command line option of
     regrtest: use the ‘--fail-env-changed’ option instead.  Since
     Python 3.7, it was a deprecated alias to the ‘--fail-env-changed’
     option.

   - bpo-45701(6): Add tests with ‘tuple’ type with *note
     functools.lru_cache(): 993. to ‘test_functools’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45695

   (2) https://bugs.python.org/issue?@action=redirect&bpo=19460

   (3) https://bugs.python.org/issue?@action=redirect&bpo=45835

   (4) https://bugs.python.org/issue?@action=redirect&bpo=45783

   (5) https://bugs.python.org/issue?@action=redirect&bpo=45745

   (6) https://bugs.python.org/issue?@action=redirect&bpo=45701


File: python.info,  Node: Build<26>,  Next: Windows<23>,  Prev: Tests<24>,  Up: Python 3 11 0 alpha 3

1.23.27.5 Build
...............

   - bpo-44035(1): CI now verifies that autoconf files have been
     regenerated with a current and unpatched autoconf package.

   - bpo-45950(2): The build system now uses a ‘_bootstrap_python’
     interpreter for freezing and deepfreezing again.  To speed up build
     process the build tools ‘_bootstrap_python’ and ‘_freeze_module’
     are no longer build with LTO.

   - bpo-45881(3): The ‘configure’ script now accepts
     ‘--with-build-python’ and ‘--with-freeze-module’ options to make
     cross compiling easier.

   - bpo-40280(4): Emscripten platform now uses ‘.wasm’ suffix by
     default.

   - bpo-40280(5): Disable unusable core extension modules on
     WASM/Emscripten targets.

   - bpo-40280(6): ‘configure’ now checks for socket ‘shutdown’
     function.  The check makes it possible to disable ‘SYS_shutdown’
     with ‘ac_cv_func_shutdown=no’ in CONFIG_SITE.

   - bpo-40280(7): ‘configure’ now checks for functions ‘fork1, getegid,
     geteuid, getgid, getppid, getuid, opendir, pipe, system, wait,
     ttyname’.

   - bpo-33393(8): Update ‘config.guess’ to 2021-06-03 and ‘config.sub’
     to 2021-08-14.  ‘Makefile’ now has an ‘update-config’ target to
     make updating more convenient.

   - bpo-45866(9): ‘make regen-all’ now produces the same output when
     run from a directory other than the source tree: when building
     Python out of the source tree.  pegen now strips directory of the
     "generated by pygen from <FILENAME>" header Patch by Victor
     Stinner.

   - bpo-40280(10): ‘configure’ now accepts machine ‘wasm32’ or ‘wasm64’
     and OS ‘wasi’ or ‘emscripten’ for cross building, e.g.
     ‘wasm32-unknown-emscripten’, ‘wasm32-wasi’, or
     ‘wasm32-unknown-wasi’.

   - bpo-41498(11): Python now compiles on platforms without ‘sigset_t’.
     Several functions in *note signal: b4. are not available when
     ‘sigset_t’ is missing.

     Based on patch by Roman Yurchak for pyodide.

   - bpo-45881(12): ‘setup.py’ now uses ‘CC’ from environment first to
     discover multiarch and cross compile paths.

   - bpo-45886(13): The ‘_freeze_module’ program path can now be
     overridden on the command line, e.g.  ‘make
     FREEZE_MODULE=../x86_64/Program/_freeze_module’.

   - bpo-45873(14): Get rid of the ‘_bootstrap_python’ build step.  The
     deepfreeze.py script is now run using ‘$(PYTHON_FOR_REGEN)’ which
     can be Python 3.7 or newer (on Windows, 3.8 or newer).

   - bpo-45847(15): Port builtin hashlib extensions to ‘PY_STDLIB_MOD’
     macro and ‘addext()’.

   - bpo-45723(16): Add ‘autoconf’ helpers for saving and restoring
     environment variables:

        * ‘SAVE_ENV’: Save ‘$CFLAGS’, ‘$LDFLAGS’, ‘$LIBS’, and
          ‘$CPPFLAGS’.

        * ‘RESTORE_ENV’: Restore ‘$CFLAGS’, ‘$LDFLAGS’, ‘$LIBS’, and
          ‘$CPPFLAGS’.

        * ‘WITH_SAVE_ENV([SCRIPT])’: Run ‘SCRIPT’ wrapped with
          ‘SAVE_ENV’ and ‘RESTORE_ENV’.

     Patch by Erlend E. Aasland.

   - bpo-45573(17): Mandatory core modules, that are required to
     bootstrap Python, are now in ‘Modules/Setup.bootstrap’.

   - bpo-45573(18): ‘configure’ now creates ‘Modules/Setup.stdlib’ with
     conditionally enabled/disabled extension module lines.  The file is
     not used, yet.

   - bpo-45573(19): ‘configure’ now uses a unified format to set state,
     compiler flags, and linker flags in Makefile.  The new macro
     ‘PY_STDLIB_MOD’ sets three variables that are consumed by
     ‘Modules/Setup’ and ‘setup.py’.

   - bpo-45816(20): Python now supports building with Visual Studio 2022
     (MSVC v143, VS Version 17.0).  Patch by Jeremiah Vivian.

   - bpo-45800(21): Settings for ‘pyexpat’ C extension are now detected
     by ‘configure’.  The bundled ‘expat’ library is built in
     ‘Makefile’.

   - bpo-45798(22): Settings for *note decimal: 2e. internal C extension
     are now detected by ‘configure’.  The bundled ‘libmpdec’ library is
     built in ‘Makefile’.

   - bpo-45723(23): ‘configure’ has a new option ‘--with-pkg-config’ to
     disable or require pkg-config.

   - bpo-45774(24): The build dependencies for *note sqlite3: ba. are
     now detected by ‘configure’ and ‘pkg-config’.  Patch by Erlend E.
     Aasland.

   - bpo-45763(25): The build dependencies for *note zlib: 119, *note
     bz2: f, and *note lzma: 7e. are now detected by ‘configure’.

   - bpo-45747(26): gdbm and dbm build dependencies are now detected by
     ‘configure’.

   - bpo-45743(27): On macOS, the build system no longer passes
     ‘search_paths_first’ to the linker.  The flag has been the default
     since Xcode 4 / macOS 10.6.

   - bpo-45723(28): ‘configure.ac’ is now compatible with autoconf 2.71.
     Deprecated checks ‘STDC_HEADERS’ and ‘AC_HEADER_TIME’ have been
     removed.

   - bpo-45723(29): ‘configure’ now prints a warning when pkg-config is
     missing.

   - bpo-45731(30): ‘configure --enable-loadable-sqlite-extensions’ is
     now handled by new ‘PY_SQLITE_ENABLE_LOAD_EXTENSION’ macro instead
     of logic in setup.py.

   - bpo-45723(31): configure.ac now uses custom helper macros and
     ‘AC_CACHE_CHECK’ to simplify and speed up configure runs.

   - bpo-45696(32): Skip the marshal step for frozen modules by
     generating C code that produces a set of ready-to-use code objects.
     This speeds up startup time by another 10% or more.

   - bpo-45561(33): Run smelly.py tool from $(srcdir).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=44035

   (2) https://bugs.python.org/issue?@action=redirect&bpo=45950

   (3) https://bugs.python.org/issue?@action=redirect&bpo=45881

   (4) https://bugs.python.org/issue?@action=redirect&bpo=40280

   (5) https://bugs.python.org/issue?@action=redirect&bpo=40280

   (6) https://bugs.python.org/issue?@action=redirect&bpo=40280

   (7) https://bugs.python.org/issue?@action=redirect&bpo=40280

   (8) https://bugs.python.org/issue?@action=redirect&bpo=33393

   (9) https://bugs.python.org/issue?@action=redirect&bpo=45866

   (10) https://bugs.python.org/issue?@action=redirect&bpo=40280

   (11) https://bugs.python.org/issue?@action=redirect&bpo=41498

   (12) https://bugs.python.org/issue?@action=redirect&bpo=45881

   (13) https://bugs.python.org/issue?@action=redirect&bpo=45886

   (14) https://bugs.python.org/issue?@action=redirect&bpo=45873

   (15) https://bugs.python.org/issue?@action=redirect&bpo=45847

   (16) https://bugs.python.org/issue?@action=redirect&bpo=45723

   (17) https://bugs.python.org/issue?@action=redirect&bpo=45573

   (18) https://bugs.python.org/issue?@action=redirect&bpo=45573

   (19) https://bugs.python.org/issue?@action=redirect&bpo=45573

   (20) https://bugs.python.org/issue?@action=redirect&bpo=45816

   (21) https://bugs.python.org/issue?@action=redirect&bpo=45800

   (22) https://bugs.python.org/issue?@action=redirect&bpo=45798

   (23) https://bugs.python.org/issue?@action=redirect&bpo=45723

   (24) https://bugs.python.org/issue?@action=redirect&bpo=45774

   (25) https://bugs.python.org/issue?@action=redirect&bpo=45763

   (26) https://bugs.python.org/issue?@action=redirect&bpo=45747

   (27) https://bugs.python.org/issue?@action=redirect&bpo=45743

   (28) https://bugs.python.org/issue?@action=redirect&bpo=45723

   (29) https://bugs.python.org/issue?@action=redirect&bpo=45723

   (30) https://bugs.python.org/issue?@action=redirect&bpo=45731

   (31) https://bugs.python.org/issue?@action=redirect&bpo=45723

   (32) https://bugs.python.org/issue?@action=redirect&bpo=45696

   (33) https://bugs.python.org/issue?@action=redirect&bpo=45561


File: python.info,  Node: Windows<23>,  Next: macOS<18>,  Prev: Build<26>,  Up: Python 3 11 0 alpha 3

1.23.27.6 Windows
.................

   - bpo-46105(1): Fixed calculation of *note sys.path: 37f. in a venv
     on Windows.

   - bpo-45901(2): When installed through the Microsoft Store and set as
     the default app for ‘*.py’ files, command line arguments will now
     be passed to Python when invoking a script without explicitly
     launching Python (that is, ‘script.py args’ rather than ‘python
     script.py args’).

   - bpo-45616(3): Fix Python Launcher's ability to distinguish between
     versions 3.1 and 3.10 when either one is explicitly requested.
     Previously, 3.1 would be used if 3.10 was requested but not
     installed, and 3.10 would be used if 3.1 was requested but 3.10 was
     installed.

   - bpo-45850(4): Implement changes to build with deep-frozen modules
     on Windows.  Note that we now require Python 3.10 as the
     "bootstrap" or "host" Python.

   - bpo-45732(5): Updates bundled Tcl/Tk to 8.6.12.

   - bpo-45720(6): Internal reference to ‘shlwapi.dll’ was dropped to
     help improve startup time.  This DLL will no longer be loaded at
     the start of every Python process.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=46105

   (2) https://bugs.python.org/issue?@action=redirect&bpo=45901

   (3) https://bugs.python.org/issue?@action=redirect&bpo=45616

   (4) https://bugs.python.org/issue?@action=redirect&bpo=45850

   (5) https://bugs.python.org/issue?@action=redirect&bpo=45732

   (6) https://bugs.python.org/issue?@action=redirect&bpo=45720


File: python.info,  Node: macOS<18>,  Next: C API<25>,  Prev: Windows<23>,  Up: Python 3 11 0 alpha 3

1.23.27.7 macOS
...............

   - bpo-45732(1): Update python.org macOS installer to use Tcl/Tk
     8.6.12.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45732


File: python.info,  Node: C API<25>,  Prev: macOS<18>,  Up: Python 3 11 0 alpha 3

1.23.27.8 C API
...............

   - bpo-39026(1): Fix Python.h to build C extensions with Xcode: remove
     a relative include from ‘Include/cpython/pystate.h’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39026


File: python.info,  Node: Python 3 11 0 alpha 2,  Next: Python 3 11 0 alpha 1,  Prev: Python 3 11 0 alpha 3,  Up: Changelog（更動日誌）

1.23.28 Python 3.11.0 alpha 2
-----------------------------

'Release date: 2021-11-05'

* Menu:

* Core and Builtins: Core and Builtins<28>.
* Library: Library<27>.
* Documentation: Documentation<22>.
* Tests: Tests<25>.
* Build: Build<27>.
* Windows: Windows<24>.
* macOS: macOS<19>.
* IDLE: IDLE<16>.
* C API: C API<26>.


File: python.info,  Node: Core and Builtins<28>,  Next: Library<27>,  Up: Python 3 11 0 alpha 2

1.23.28.1 Core and Builtins
...........................

   - bpo-45716(1): Improve the *note SyntaxError: 173. message when
     using ‘True’, ‘None’ or ‘False’ as keywords in a function call.
     Patch by Pablo Galindo.

   - bpo-45688(2): *note sys.stdlib_module_names: 7e5. now contains the
     macOS-specific module ‘_scproxy’.

   - bpo-45379(3): Clarify *note ImportError: 352. message when we try
     to explicitly import a frozen module but frozen modules are
     disabled.

   - bpo-44525(4): Specialize simple calls to Python functions (no
     starargs, keyword dict, or closure)

   - bpo-45530(5): Cases of sorting using tuples as keys may now be
     significantly faster in some cases.  Patch by Tim Peters.

     The order of the result may differ from earlier releases if the
     tuple elements don't define a total ordering (see *note Value
     comparisons: 177e. for information on total ordering).  It's
     generally true that the result of sorting simply isn't well-defined
     in the absence of a total ordering on list elements.

   - bpo-45526(6): In obmalloc, set ADDRESS_BITS to not ignore any bits
     (ignored 16 before).  That is safer in the case that the kernel
     gives user-space virtual addresses that span a range greater than
     48 bits.

   - bpo-30570(7): Fixed a crash in ‘issubclass()’ from infinite
     recursion when searching pathological ‘__bases__’ tuples.

   - bpo-45521(8): Fix a bug in the obmalloc radix tree code.  On 64-bit
     machines, the bug causes the tree to hold 46-bits of virtual
     addresses, rather than the intended 48-bits.

   - bpo-45494(9): Fix parser crash when reporting errors involving
     invalid continuation characters.  Patch by Pablo Galindo.

   - bpo-45445(10): Python now fails to initialize if it finds an
     invalid *note -X: 15a. option in the command line.  Patch by Pablo
     Galindo.

   - bpo-45340(11): Object attributes are held in an array instead of a
     dictionary.  An object's dictionary are created lazily, only when
     needed.  Reduces the memory consumption of a typical Python object
     by about 30%.  Patch by Mark Shannon.

   - bpo-45408(12): Fix a crash in the parser when reporting tokenizer
     errors that occur at the same time unclosed parentheses are
     detected.  Patch by Pablo Galindo.

   - bpo-29410(13): Add SipHash13 for string hash algorithm and use it
     by default.

   - bpo-45385(14): Fix reference leak from descr_check.  Patch by
     Donghee Na.

   - bpo-45367(15): Specialized the ‘BINARY_MULTIPLY’ opcode to
     ‘BINARY_MULTIPLY_INT’ and ‘BINARY_MULTIPLY_FLOAT’ using the PEP 659
     machinery.

   - bpo-21736(16): Frozen stdlib modules now have ‘__file__’ to the .py
     file they would otherwise be loaded from, if possible.  For
     packages, ‘__path__’ now has the correct entry instead of being an
     empty list, which allows unfrozen submodules to be imported.  These
     are set only if the stdlib directory is known when the runtime is
     initialized.  Note that the file at ‘__file__’ is not guaranteed to
     exist.  None of this affects non-stdlib frozen modules nor, for
     now, frozen modules imported using ‘PyImport_ImportFrozenModule()’.
     Also, at the moment ‘co_filename’ is not updated for the module.

   - bpo-45020(17): For frozen stdlib modules, record the original
     module name as ‘module.__spec__.loader_state.origname’.  If the
     value is different than ‘module.__spec__.name’ then the module was
     defined as an alias in Tools/scripts/freeze_modules.py.  If it is
     ‘None’ then the module comes from a source file outside the stdlib.

   - bpo-45324(18): In FrozenImporter.find_spec(), we now preserve the
     information needed in exec_module() to load the module.  This
     change mostly impacts internal details, rather than changing the
     importer's behavior.

   - bpo-45292(19): Implement PEP 654(20).  Add *note ExceptionGroup:
     19c. and *note BaseExceptionGroup: 244.  Update traceback display
     code.

   - bpo-40116(21): Change to the implementation of split dictionaries.
     Classes where the instances differ either in the exact set of
     attributes, or in the order in which those attributes are set, can
     still share keys.  This should have no observable effect on users
     of Python or the C-API. Patch by Mark Shannon.

   - bpo-44050(22): Extensions that indicate they use global state (by
     setting ‘m_size’ to -1) can again be used in multiple interpreters.
     This reverts to behavior of Python 3.8.

   - bpo-44525(23): Setup initial specialization infrastructure for the
     ‘CALL_FUNCTION’ opcode.  Implemented initial specializations for C
     function calls:

        * ‘CALL_FUNCTION_BUILTIN_O’ for ‘METH_O’ flag.

        * ‘CALL_FUNCTION_BUILTIN_FAST’ for ‘METH_FASTCALL’ flag without
          keywords.

        * ‘CALL_FUNCTION_LEN’ for ‘len(o)’.

        * ‘CALL_FUNCTION_ISINSTANCE’ for ‘isinstance(o, t)’.

   - bpo-44511(24): Improve the generated bytecode for class and mapping
     patterns.

   - bpo-43706(25): Speed up calls to ‘enumerate()’ by using the PEP
     590(26) ‘vectorcall’ calling convention.  Patch by Donghee Na.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45716

   (2) https://bugs.python.org/issue?@action=redirect&bpo=45688

   (3) https://bugs.python.org/issue?@action=redirect&bpo=45379

   (4) https://bugs.python.org/issue?@action=redirect&bpo=44525

   (5) https://bugs.python.org/issue?@action=redirect&bpo=45530

   (6) https://bugs.python.org/issue?@action=redirect&bpo=45526

   (7) https://bugs.python.org/issue?@action=redirect&bpo=30570

   (8) https://bugs.python.org/issue?@action=redirect&bpo=45521

   (9) https://bugs.python.org/issue?@action=redirect&bpo=45494

   (10) https://bugs.python.org/issue?@action=redirect&bpo=45445

   (11) https://bugs.python.org/issue?@action=redirect&bpo=45340

   (12) https://bugs.python.org/issue?@action=redirect&bpo=45408

   (13) https://bugs.python.org/issue?@action=redirect&bpo=29410

   (14) https://bugs.python.org/issue?@action=redirect&bpo=45385

   (15) https://bugs.python.org/issue?@action=redirect&bpo=45367

   (16) https://bugs.python.org/issue?@action=redirect&bpo=21736

   (17) https://bugs.python.org/issue?@action=redirect&bpo=45020

   (18) https://bugs.python.org/issue?@action=redirect&bpo=45324

   (19) https://bugs.python.org/issue?@action=redirect&bpo=45292

   (20) https://peps.python.org/pep-0654/

   (21) https://bugs.python.org/issue?@action=redirect&bpo=40116

   (22) https://bugs.python.org/issue?@action=redirect&bpo=44050

   (23) https://bugs.python.org/issue?@action=redirect&bpo=44525

   (24) https://bugs.python.org/issue?@action=redirect&bpo=44511

   (25) https://bugs.python.org/issue?@action=redirect&bpo=43706

   (26) https://peps.python.org/pep-0590/


File: python.info,  Node: Library<27>,  Next: Documentation<22>,  Prev: Core and Builtins<28>,  Up: Python 3 11 0 alpha 2

1.23.28.2 Library
.................

   - bpo-45679(1): Fix caching of multi-value *note typing.Literal: 7f9.
     ‘Literal[True, 2]’ is no longer equal to ‘Literal[1, 2]’.

   - bpo-42064(2): Convert *note sqlite3: ba. to multi-phase
     initialisation (PEP 489).  Patches by Erlend E. Aasland.

   - bpo-45438(3): Fix typing.Signature string representation for
     generic builtin types.

   - bpo-45613(4): *note sqlite3: ba. now sets *note
     sqlite3.threadsafety: 622. based on the default threading mode the
     underlying SQLite library has been compiled with.  Patch by Erlend
     E. Aasland.

   - bpo-45574(5): Fix warning about ‘print_escape’ being unused.

   - bpo-45581(6): *note sqlite3.connect(): 288. now correctly raises
     *note MemoryError: 15bc. if the underlying SQLite API signals
     memory error.  Patch by Erlend E. Aasland.

   - bpo-45557(7): *note pprint.pprint(): 7cc. now handles
     'underscore_numbers' correctly.  Previously it was always setting
     it to ‘False’.

   - bpo-44019(8): Add *note operator.call(): 1780. to
     ‘operator.__all__’.  Patch by Kreusada.

   - bpo-42174(9): *note shutil.get_terminal_size(): 109b. now falls
     back to sane values if the column or line count are 0.

   - bpo-35673(10): Improve the introspectability of the ‘__loader__’
     attribute for namespace packages.  *note
     importlib.machinery.NamespaceLoader: ef9. is now public, and
     implements the *note importlib.abc.InspectLoader: ef7. interface.
     ‘_NamespaceLoader’ is kept for backward compatibility.

   - bpo-45515(11): Add references to *note zoneinfo: 11a. in the *note
     datetime: 28. documentation, mostly replacing outdated references
     to ‘dateutil.tz’.  Change by Paul Ganssle.

   - bpo-45475(12): Reverted optimization of iterating *note
     gzip.GzipFile: 354, *note bz2.BZ2File: 80b, and *note
     lzma.LZMAFile: fad. (see bpo-43787(13)) because it caused
     regression when user iterate them without having reference of them.
     Patch by Inada Naoki.

   - bpo-45489(14): Update *note ForwardRef: 1748. to support ‘|’
     operator.  Patch by Donghee Na.

   - bpo-42222(15): Removed deprecated support for float arguments in
     'randrange()'.

   - bpo-45428(16): Fix a regression in py_compile when reading
     filenames from standard input.

   - bpo-45467(17): Fix incremental decoder and stream reader in the
     "raw-unicode-escape" codec.  Previously they failed if the escape
     sequence was split.

   - bpo-45461(18): Fix incremental decoder and stream reader in the
     "unicode-escape" codec.  Previously they failed if the escape
     sequence was split.

   - bpo-45239(19): Fixed *note email.utils.parsedate_tz(): 1781.
     crashing with *note UnboundLocalError: 14a4. on certain invalid
     input instead of returning ‘None’.  Patch by Ben Hoyt.

   - bpo-45417(20): Fix quadratic behaviour in the enum module: Creation
     of enum classes with a lot of entries was quadratic.

   - bpo-45249(21): Fix the behaviour of *note traceback.print_exc():
     1782. when displaying the caret when the ‘end_offset’ in the
     exception is set to 0.  Patch by Pablo Galindo

   - bpo-45416(22): Fix use of *note asyncio.Condition: a16. with
     explicit *note asyncio.Lock: a14. objects, which was a regression
     due to removal of explicit loop arguments.  Patch by Joongi Kim.

   - bpo-20028(23): Empty escapechar/quotechar is not allowed when
     initializing *note csv.Dialect: 1571.  Patch by Vajrasky Kok and
     Donghee Na.

   - bpo-44904(24): Fix bug in the *note doctest: 31. module that caused
     it to fail if a docstring included an example with a ‘classmethod’
     ‘property’.  Patch by Alex Waygood.

   - bpo-45406(25): Make *note inspect.getmodule(): 16e9. catch
     ‘FileNotFoundError’ raised by ‘inspect.getabsfile()’, and return
     ‘None’ to indicate that the module could not be determined.

   - bpo-45411(26): Add extensions for files containing subtitles - .srt
     & .vtt - to the mimetypes.py module.

   - bpo-10716(27): Migrated pydoc to HTML5 (without changing the look
     of it).  Side effect is to update xmlrpc's ‘ServerHTMLDoc’ which
     now uses the CSS too.  cgitb now relies less on pydoc (as it can't
     use the CSS file).

   - bpo-27580(28): Add support of null characters in *note csv: 21.

   - bpo-45262(29): Prevent use-after-free in asyncio.  Make sure the
     cached running loop holder gets cleared on dealloc to prevent
     use-after-free in get_running_loop

   - bpo-45386(30): Make *note xmlrpc.client: 114. more robust to C
     runtimes where the underlying C ‘strftime’ function results in a
     ‘ValueError’ when testing for year formatting options.

   - bpo-20028(31): Improve error message of *note csv.Dialect: 1571.
     when initializing.  Patch by Vajrasky Kok and Donghee Na.

   - bpo-45343(32): Update bundled pip to 21.2.4 and setuptools to
     58.1.0

   - bpo-45328(33): Fixed *note http.client.HTTPConnection: ae4. to work
     properly in OSs that don't support the ‘TCP_NODELAY’ socket option.

   - bpo-45243(34): Add *note setlimit(): 620. and *note getlimit():
     621. to *note sqlite3.Connection: 22a. for setting and getting
     SQLite limits by connection basis.  Patch by Erlend E. Aasland.

   - bpo-45320(35): Removed from the *note inspect: 72. module:

        * 
          the ‘getargspec’ function, deprecated since Python 3.0;

               use *note inspect.signature(): 6dc. or *note
               inspect.getfullargspec(): 6dd. instead.

        * the ‘formatargspec’ function, deprecated since Python 3.5; use
          the *note inspect.signature(): 6dc. function and ‘Signature’
          object directly.

        * the undocumented ‘Signature.from_builtin’ and
          ‘Signature.from_function’ functions, deprecated since Python
          3.5; use the *note Signature.from_callable(): 6de. method
          instead.

     Patch by Hugo van Kemenade.

   - bpo-45192(36): Fix the ‘tempfile._infer_return_type’ function so
     that the ‘dir’ argument of the *note tempfile: c9. functions
     accepts an object implementing the ‘os.PathLike’ protocol.

     Patch by Kyungmin Lee.

   - bpo-45160(37): When tracing a tkinter variable used by a ttk
     OptionMenu, callbacks are no longer made twice.

   - bpo-25625(38): Added non parallel-safe *note chdir(): 5b1. context
     manager to change the current working directory and then restore it
     on exit.  Simple wrapper around *note chdir(): 5b2.

   - bpo-24139(39): Add support for SQLite extended result codes in
     *note sqlite3.Error: 1783.  Patch by Erlend E. Aasland.

   - bpo-24444(40): Fixed an error raised in *note argparse: 5. help
     display when help for an option is set to 1+ blank spaces or when
     'choices' arg is an empty container.

   - bpo-44547(41): Implement ‘Fraction.__int__’, so that a *note
     fractions.Fraction: 1c7. instance ‘f’ passes an ‘isinstance(f,
     typing.SupportsInt)’ check.

   - bpo-40321(42): Adds support for HTTP 308 redirects to *note urllib:
     f1.  See RFC 7538(43) for details.  Patch by Jochem Schulenklopper.

   - bpo-41374(44): Ensure that ‘socket.TCP_*’ constants are exposed on
     Cygwin 3.1.6 and greater.

   - bpo-35970(45): Add help flag to the base64 module's command line
     interface.  Patch contributed by Robert Kuska.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45679

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42064

   (3) https://bugs.python.org/issue?@action=redirect&bpo=45438

   (4) https://bugs.python.org/issue?@action=redirect&bpo=45613

   (5) https://bugs.python.org/issue?@action=redirect&bpo=45574

   (6) https://bugs.python.org/issue?@action=redirect&bpo=45581

   (7) https://bugs.python.org/issue?@action=redirect&bpo=45557

   (8) https://bugs.python.org/issue?@action=redirect&bpo=44019

   (9) https://bugs.python.org/issue?@action=redirect&bpo=42174

   (10) https://bugs.python.org/issue?@action=redirect&bpo=35673

   (11) https://bugs.python.org/issue?@action=redirect&bpo=45515

   (12) https://bugs.python.org/issue?@action=redirect&bpo=45475

   (13) https://bugs.python.org/issue?@action=redirect&bpo=43787

   (14) https://bugs.python.org/issue?@action=redirect&bpo=45489

   (15) https://bugs.python.org/issue?@action=redirect&bpo=42222

   (16) https://bugs.python.org/issue?@action=redirect&bpo=45428

   (17) https://bugs.python.org/issue?@action=redirect&bpo=45467

   (18) https://bugs.python.org/issue?@action=redirect&bpo=45461

   (19) https://bugs.python.org/issue?@action=redirect&bpo=45239

   (20) https://bugs.python.org/issue?@action=redirect&bpo=45417

   (21) https://bugs.python.org/issue?@action=redirect&bpo=45249

   (22) https://bugs.python.org/issue?@action=redirect&bpo=45416

   (23) https://bugs.python.org/issue?@action=redirect&bpo=20028

   (24) https://bugs.python.org/issue?@action=redirect&bpo=44904

   (25) https://bugs.python.org/issue?@action=redirect&bpo=45406

   (26) https://bugs.python.org/issue?@action=redirect&bpo=45411

   (27) https://bugs.python.org/issue?@action=redirect&bpo=10716

   (28) https://bugs.python.org/issue?@action=redirect&bpo=27580

   (29) https://bugs.python.org/issue?@action=redirect&bpo=45262

   (30) https://bugs.python.org/issue?@action=redirect&bpo=45386

   (31) https://bugs.python.org/issue?@action=redirect&bpo=20028

   (32) https://bugs.python.org/issue?@action=redirect&bpo=45343

   (33) https://bugs.python.org/issue?@action=redirect&bpo=45328

   (34) https://bugs.python.org/issue?@action=redirect&bpo=45243

   (35) https://bugs.python.org/issue?@action=redirect&bpo=45320

   (36) https://bugs.python.org/issue?@action=redirect&bpo=45192

   (37) https://bugs.python.org/issue?@action=redirect&bpo=45160

   (38) https://bugs.python.org/issue?@action=redirect&bpo=25625

   (39) https://bugs.python.org/issue?@action=redirect&bpo=24139

   (40) https://bugs.python.org/issue?@action=redirect&bpo=24444

   (41) https://bugs.python.org/issue?@action=redirect&bpo=44547

   (42) https://bugs.python.org/issue?@action=redirect&bpo=40321

   (43) https://datatracker.ietf.org/doc/html/rfc7538.html

   (44) https://bugs.python.org/issue?@action=redirect&bpo=41374

   (45) https://bugs.python.org/issue?@action=redirect&bpo=35970


File: python.info,  Node: Documentation<22>,  Next: Tests<25>,  Prev: Library<27>,  Up: Python 3 11 0 alpha 2

1.23.28.3 Documentation
.......................

   - bpo-45726(1): Improve documentation for *note
     functools.singledispatch(): 5df. and *note
     functools.singledispatchmethod: 994.

   - bpo-45680(2): Amend the docs on ‘GenericAlias’ objects to clarify
     that non-container classes can also implement ‘__class_getitem__’.
     Patch contributed by Alex Waygood.

   - bpo-45618(3): Update Sphinx version used to build the documentation
     to 4.2.0.  Patch by Maciej Olko.

   - bpo-45655(4): Add a new "relevant PEPs" section to the top of the
     documentation for the ‘typing’ module.  Patch by Alex Waygood.

   - bpo-45604(5): Add ‘level’ argument to
     ‘multiprocessing.log_to_stderr’ function docs.

   - bpo-45516(6): Add protocol description to the *note
     importlib.abc.TraversableResources: 1785. documentation.

   - bpo-45464(7): Mention in the documentation of *note Built-in
     Exceptions: 1786. that inheriting from multiple exception types in
     a single subclass is not recommended due to possible memory layout
     incompatibility.

   - bpo-45449(8): Add note about PEP 585(9) in *note collections.abc:
     17.

   - bpo-45516(10): Add protocol description to the *note
     importlib.abc.Traversable: 1787. documentation.

   - bpo-20692(11): Add Programming FAQ entry explaining that int
     literal attribute access requires either a space after or
     parentheses around the literal.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45726

   (2) https://bugs.python.org/issue?@action=redirect&bpo=45680

   (3) https://bugs.python.org/issue?@action=redirect&bpo=45618

   (4) https://bugs.python.org/issue?@action=redirect&bpo=45655

   (5) https://bugs.python.org/issue?@action=redirect&bpo=45604

   (6) https://bugs.python.org/issue?@action=redirect&bpo=45516

   (7) https://bugs.python.org/issue?@action=redirect&bpo=45464

   (8) https://bugs.python.org/issue?@action=redirect&bpo=45449

   (9) https://peps.python.org/pep-0585/

   (10) https://bugs.python.org/issue?@action=redirect&bpo=45516

   (11) https://bugs.python.org/issue?@action=redirect&bpo=20692


File: python.info,  Node: Tests<25>,  Next: Build<27>,  Prev: Documentation<22>,  Up: Python 3 11 0 alpha 2

1.23.28.4 Tests
...............

   - bpo-45678(1): Add tests for scenarios in which *note
     functools.singledispatchmethod: 994. is stacked on top of a method
     that has already been wrapped by two other decorators.  Patch by
     Alex Waygood.

   - bpo-45578(2): Add tests for ‘dis.distb()’

   - bpo-45678(3): Add tests to ensure that
     ‘functools.singledispatchmethod’ correctly wraps the attributes of
     the target function.

   - bpo-45668(4): PGO tests now pass when Python is built without test
     extension modules.

   - bpo-45577(5): Add subtests for all ‘pickle’ protocols in
     ‘test_zoneinfo’.

   - bpo-45566(6): Fix ‘test_frozen_pickle’ in ‘test_dataclasses’ to
     check all ‘pickle’ versions.

   - bpo-43592(7): ‘test.libregrtest’ now raises the soft resource limit
     for the maximum number of file descriptors when the default is too
     low for our test suite as was often the case on macOS.

   - bpo-39679(8): Add more test cases for
     ‘@functools.singledispatchmethod’ when combined with ‘@classmethod’
     or ‘@staticmethod’.

   - bpo-45410(9): When libregrtest spawns a worker process, stderr is
     now written into stdout to keep messages order.  Use a single pipe
     for stdout and stderr, rather than two pipes.  Previously, messages
     were out of order which made analysis of buildbot logs harder Patch
     by Victor Stinner.

   - bpo-45402(10): Fix test_tools.test_sundry() when Python is built
     out of tree: fix how the freeze_modules.py tool locates the
     _freeze_module program.  Patch by Victor Stinner.

   - bpo-45403(11): Fix test_sys.test_stdlib_dir() when Python is built
     outside the source tree: compare normalized paths.  Patch by Victor
     Stinner.

   - bpo-45400(12): Fix
     test_name_error_suggestions_do_not_trigger_for_too_many_locals() of
     test_exceptions if a directory name contains "a1" (like
     "Python-3.11.0a1"): use a stricter regular expression.  Patch by
     Victor Stinner.

   - bpo-10572(13): Rename *note sqlite3: ba. tests from ‘test_sqlite’
     to ‘test_sqlite3’, and relocate them to ‘Lib/test/test_sqlite3’.
     Patch by Erlend E. Aasland.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45678

   (2) https://bugs.python.org/issue?@action=redirect&bpo=45578

   (3) https://bugs.python.org/issue?@action=redirect&bpo=45678

   (4) https://bugs.python.org/issue?@action=redirect&bpo=45668

   (5) https://bugs.python.org/issue?@action=redirect&bpo=45577

   (6) https://bugs.python.org/issue?@action=redirect&bpo=45566

   (7) https://bugs.python.org/issue?@action=redirect&bpo=43592

   (8) https://bugs.python.org/issue?@action=redirect&bpo=39679

   (9) https://bugs.python.org/issue?@action=redirect&bpo=45410

   (10) https://bugs.python.org/issue?@action=redirect&bpo=45402

   (11) https://bugs.python.org/issue?@action=redirect&bpo=45403

   (12) https://bugs.python.org/issue?@action=redirect&bpo=45400

   (13) https://bugs.python.org/issue?@action=redirect&bpo=10572


File: python.info,  Node: Build<27>,  Next: Windows<24>,  Prev: Tests<25>,  Up: Python 3 11 0 alpha 2

1.23.28.5 Build
...............

   - bpo-43158(1): ‘setup.py’ now uses values from configure script to
     build the ‘_uuid’ extension module.  Configure now detects
     util-linux's ‘libuuid’, too.

   - bpo-45666(2): Fix warning of ‘swprintf’ and ‘%s’ usage in
     ‘_testembed.c’

   - bpo-45548(3): ‘Modules/Setup’ and ‘Modules/makesetup’ have been
     improved.  The ‘Setup’ file now contains working rules for all
     extensions.  Outdated comments have been removed.  Rules defined by
     ‘makesetup’ track dependencies correctly.

   - bpo-45548(4): The *note math: 81. and *note cmath: 11.
     implementation now require a C99 compatible ‘libm’ and no longer
     ship with workarounds for missing acosh, asinh, atanh, expm1, and
     log1p functions.

   - bpo-45595(5): ‘setup.py’ and ‘makesetup’ now track build
     dependencies on all Python header files and module specific header
     files.

   - bpo-45571(6): ‘Modules/Setup’ now use ‘PY_CFLAGS_NODIST’ instead of
     ‘PY_CFLAGS’ to compile shared modules.

   - bpo-45570(7): ‘pyexpat’ and ‘_elementtree’ no longer define
     obsolete macros ‘HAVE_EXPAT_CONFIG_H’ and ‘USE_PYEXPAT_CAPI’.
     ‘XML_POOR_ENTROPY’ is now defined in ‘expat_config.h’.

   - bpo-43974(8): ‘setup.py’ no longer defines ‘Py_BUILD_CORE_MODULE’.
     Instead every module, that uses the internal API, defines the
     macro.

   - bpo-45548(9): Fill in missing entries in Modules/Setup.

   - bpo-45532(10): Update *note sys.version: 15c. to use ‘main’ as
     fallback information.  Patch by Jeong YunWon.

   - bpo-45536(11): The ‘configure’ script now checks whether OpenSSL
     headers and libraries provide required APIs.  Most common APIs are
     verified.  The check detects outdated or missing OpenSSL. Failures
     do not stop configure.

   - bpo-45221(12): Fixed regression in handling of ‘LDFLAGS’ and
     ‘CPPFLAGS’ options where ‘argparse.parse_known_args()’ could
     interpret an option as one of the built-in command line argument,
     for example ‘-h’ for help.

   - bpo-45440(13): Building Python now requires a C99 ‘<math.h>’ header
     file providing the following functions: ‘copysign()’, ‘hypot()’,
     ‘isfinite()’, ‘isinf()’, ‘isnan()’, ‘round()’.  Patch by Victor
     Stinner.

   - bpo-45405(14): Prevent ‘internal configure error’ when running
     ‘configure’ with recent versions of non-Apple clang.  Patch by
     David Bohman.

   - bpo-45433(15): Avoid linking libpython with libcrypt.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43158

   (2) https://bugs.python.org/issue?@action=redirect&bpo=45666

   (3) https://bugs.python.org/issue?@action=redirect&bpo=45548

   (4) https://bugs.python.org/issue?@action=redirect&bpo=45548

   (5) https://bugs.python.org/issue?@action=redirect&bpo=45595

   (6) https://bugs.python.org/issue?@action=redirect&bpo=45571

   (7) https://bugs.python.org/issue?@action=redirect&bpo=45570

   (8) https://bugs.python.org/issue?@action=redirect&bpo=43974

   (9) https://bugs.python.org/issue?@action=redirect&bpo=45548

   (10) https://bugs.python.org/issue?@action=redirect&bpo=45532

   (11) https://bugs.python.org/issue?@action=redirect&bpo=45536

   (12) https://bugs.python.org/issue?@action=redirect&bpo=45221

   (13) https://bugs.python.org/issue?@action=redirect&bpo=45440

   (14) https://bugs.python.org/issue?@action=redirect&bpo=45405

   (15) https://bugs.python.org/issue?@action=redirect&bpo=45433


File: python.info,  Node: Windows<24>,  Next: macOS<19>,  Prev: Build<27>,  Up: Python 3 11 0 alpha 2

1.23.28.6 Windows
.................

   - bpo-43652(1): Update Tcl/Tk to 8.6.11, actually this time.  The
     previous update incorrectly included 8.6.10.

   - bpo-45337(2): venv now warns when the created environment may need
     to be accessed at a different path, due to redirections, links or
     junctions.  It also now correctly installs or upgrades components
     when the alternate path is required.

   - bpo-43851(3): Build SQLite ‘SQLITE_OMIT_AUTOINIT’ on Windows.
     Patch by Erlend E. Aasland.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43652

   (2) https://bugs.python.org/issue?@action=redirect&bpo=45337

   (3) https://bugs.python.org/issue?@action=redirect&bpo=43851


File: python.info,  Node: macOS<19>,  Next: IDLE<16>,  Prev: Windows<24>,  Up: Python 3 11 0 alpha 2

1.23.28.7 macOS
...............

   - bpo-44828(1): Avoid tkinter file dialog failure on macOS 12
     Monterey when using the Tk 8.6.11 provided by python.org macOS
     installers.  Patch by Marc Culler of the Tk project.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=44828


File: python.info,  Node: IDLE<16>,  Next: C API<26>,  Prev: macOS<19>,  Up: Python 3 11 0 alpha 2

1.23.28.8 IDLE
..............

   - bpo-45495(1): Add context keywords 'case' and 'match' to
     completions list.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45495


File: python.info,  Node: C API<26>,  Prev: IDLE<16>,  Up: Python 3 11 0 alpha 2

1.23.28.9 C API
...............

   - bpo-29103(1): *note PyType_FromSpec*: 4f7. now copies the class
     name from the spec to a buffer owned by the class, so the original
     can be safely deallocated.  Patch by Petr Viktorin.

   - bpo-45522(2): The internal freelists for frame, float, list, dict,
     async generators, and context objects can now be disabled.

   - bpo-35134(3): Exclude *note PyWeakref_GET_OBJECT(): 38a. from the
     limited C API. It never worked since the ‘PyWeakReference’
     structure is opaque in the limited C API.

   - bpo-35081(4): Move the ‘interpreteridobject.h’ header file from
     ‘Include/’ to ‘Include/internal/’.  It only provides private
     functions.  Patch by Victor Stinner.

   - bpo-35134(5): The non-limited API files ‘cellobject.h’,
     ‘classobject.h’, ‘context.h’, ‘funcobject.h’, ‘genobject.h’ and
     ‘longintrepr.h’ have been moved to the ‘Include/cpython’ directory.
     Moreover, the ‘eval.h’ header file was removed.  These files must
     not be included directly, as they are already included in
     ‘Python.h’: *note Include Files: 728.  If they have been included
     directly, consider including ‘Python.h’ instead.  Patch by Victor
     Stinner.

   - bpo-45474(6): The following items are no longer available when
     ‘Py_LIMITED_API’ is defined:

        * *note PyMarshal_WriteLongToFile(): 73a.

        * *note PyMarshal_WriteObjectToFile(): 73b.

        * *note PyMarshal_ReadObjectFromString(): 73c.

        * *note PyMarshal_WriteObjectToString(): 73d.

        * the ‘Py_MARSHAL_VERSION’ macro

     These are not part of the *note limited API: 73e.

     Patch by Victor Stinner.

   - bpo-45434(7): Remove the ‘pystrhex.h’ header file.  It only
     contains private functions.  C extensions should only include the
     main ‘<Python.h>’ header file.  Patch by Victor Stinner.

   - bpo-45440(8): Remove the ‘Py_FORCE_DOUBLE()’ macro.  It was used by
     the ‘Py_IS_INFINITY()’ macro.  Patch by Victor Stinner.

   - bpo-45434(9): ‘<Python.h>’ no longer includes the header files
     ‘<stdlib.h>’, ‘<stdio.h>’, ‘<errno.h>’ and ‘<string.h>’ when the
     ‘Py_LIMITED_API’ macro is set to ‘0x030b0000’ (Python 3.11) or
     higher.  C extensions should explicitly include the header files
     after ‘#include <Python.h>’.  Patch by Victor Stinner.

   - bpo-41123(10): Remove ‘Py_UNICODE_COPY()’ and ‘Py_UNICODE_FILL()’
     macros, deprecated since Python 3.3.  Use
     ‘PyUnicode_CopyCharacters()’ or ‘memcpy()’ (‘wchar_t*’ string), and
     ‘PyUnicode_Fill()’ functions instead.  Patch by Victor Stinner.

   - bpo-45412(11): Remove the following math macros using the ‘errno’
     variable:

        * ‘Py_ADJUST_ERANGE1()’

        * ‘Py_ADJUST_ERANGE2()’

        * ‘Py_OVERFLOWED()’

        * ‘Py_SET_ERANGE_IF_OVERFLOW()’

        * ‘Py_SET_ERRNO_ON_MATH_ERROR()’

     Patch by Victor Stinner.

   - bpo-45395(12): Custom frozen modules (the array set to
     ‘PyImport_FrozenModules’) are now treated as additions, rather than
     replacing all the default frozen modules.  Frozen stdlib modules
     can still be disabled by setting the "code" field of the custom
     array entry to NULL.

   - bpo-43760(13): Add new *note PyThreadState_EnterTracing(): 6f8, and
     *note PyThreadState_LeaveTracing(): 6f9. functions to the limited C
     API to suspend and resume tracing and profiling.  Patch by Victor
     Stinner.

   - bpo-44220(14): *note PyStructSequence_UnnamedField: 926. is added
     to the Stable ABI.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29103

   (2) https://bugs.python.org/issue?@action=redirect&bpo=45522

   (3) https://bugs.python.org/issue?@action=redirect&bpo=35134

   (4) https://bugs.python.org/issue?@action=redirect&bpo=35081

   (5) https://bugs.python.org/issue?@action=redirect&bpo=35134

   (6) https://bugs.python.org/issue?@action=redirect&bpo=45474

   (7) https://bugs.python.org/issue?@action=redirect&bpo=45434

   (8) https://bugs.python.org/issue?@action=redirect&bpo=45440

   (9) https://bugs.python.org/issue?@action=redirect&bpo=45434

   (10) https://bugs.python.org/issue?@action=redirect&bpo=41123

   (11) https://bugs.python.org/issue?@action=redirect&bpo=45412

   (12) https://bugs.python.org/issue?@action=redirect&bpo=45395

   (13) https://bugs.python.org/issue?@action=redirect&bpo=43760

   (14) https://bugs.python.org/issue?@action=redirect&bpo=44220


File: python.info,  Node: Python 3 11 0 alpha 1,  Next: Python 3 10 0 beta 1,  Prev: Python 3 11 0 alpha 2,  Up: Changelog（更動日誌）

1.23.29 Python 3.11.0 alpha 1
-----------------------------

'Release date: 2021-10-05'

* Menu:

* Security: Security<16>.
* Core and Builtins: Core and Builtins<29>.
* Library: Library<28>.
* Documentation: Documentation<23>.
* Tests: Tests<26>.
* Build: Build<28>.
* Windows: Windows<25>.
* macOS: macOS<20>.
* IDLE: IDLE<17>.
* Tools/Demos: Tools/Demos<13>.
* C API: C API<27>.


File: python.info,  Node: Security<16>,  Next: Core and Builtins<29>,  Up: Python 3 11 0 alpha 1

1.23.29.1 Security
..................

   - bpo-42278(1): Replaced usage of *note tempfile.mktemp(): 1790. with
     *note TemporaryDirectory: 11cc. to avoid a potential race
     condition.

   - bpo-44600(2): Fix incorrect line numbers while tracing some failed
     patterns in *note match: 7b1. statements.  Patch by Charles
     Burkland.

   - bpo-41180(3): Add auditing events to the *note marshal: 80. module,
     and stop raising ‘code.__init__’ events for every unmarshalled code
     object.  Directly instantiated code objects will continue to raise
     an event, and audit event handlers should inspect or collect the
     raw marshal data.  This reduces a significant performance overhead
     when loading from ‘.pyc’ files.

   - bpo-44394(4): Update the vendored copy of libexpat to 2.4.1 (from
     2.2.8) to get the fix for the CVE-2013-0340(5) "Billion Laughs"
     vulnerability.  This copy is most used on Windows and macOS.

   - bpo-43124(6): Made the internal ‘putcmd’ function in *note smtplib:
     b7. sanitize input for presence of ‘\r’ and ‘\n’ characters to
     avoid (unlikely) command injection.

   - bpo-44022(7): *note http.client: 65. now avoids infinitely reading
     potential HTTP headers after a ‘100 Continue’ status response from
     the server.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42278

   (2) https://bugs.python.org/issue?@action=redirect&bpo=44600

   (3) https://bugs.python.org/issue?@action=redirect&bpo=41180

   (4) https://bugs.python.org/issue?@action=redirect&bpo=44394

   (5) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0340

   (6) https://bugs.python.org/issue?@action=redirect&bpo=43124

   (7) https://bugs.python.org/issue?@action=redirect&bpo=44022


File: python.info,  Node: Core and Builtins<29>,  Next: Library<28>,  Prev: Security<16>,  Up: Python 3 11 0 alpha 1

1.23.29.2 Core and Builtins
...........................

   - bpo-43760(1): The number of hardware branches per instruction
     dispatch is reduced from two to one by adding a special instruction
     for tracing.  Patch by Mark Shannon.

   - bpo-45061(2): Add a deallocator to the bool type to detect refcount
     bugs in C extensions which call Py_DECREF(Py_True) or
     Py_DECREF(Py_False) by mistake.  Detect also refcount bugs when the
     empty tuple singleton or the Unicode empty string singleton is
     destroyed by mistake.  Patch by Victor Stinner.

   - bpo-24076(3): sum() was further optimised for summing up single
     digit integers.

   - bpo-45190(4): Update Unicode databases to Unicode 14.0.0.

   - bpo-45167(5): Fix deepcopying of *note types.GenericAlias: 78f.
     objects.

   - bpo-45155(6): *note int.to_bytes(): 1792. and *note
     int.from_bytes(): 1754. now take a default value of ‘"big"’ for the
     ‘byteorder’ argument.  *note int.to_bytes(): 1792. also takes a
     default value of ‘1’ for the ‘length’ argument.

   - bpo-44219(7): Release the GIL while performing ‘isatty’ system
     calls on arbitrary file descriptors.  In particular, this affects
     *note os.isatty(): 1793, *note os.device_encoding(): 1794. and
     *note io.TextIOWrapper: 75f.  By extension, *note io.open(): 4c1.
     in text mode is also affected.  This change solves a deadlock in
     *note os.isatty(): 1793.  Patch by Vincent Michel in bpo-44219(8).

   - bpo-44959(9): Added fallback to extension modules with '.sl' suffix
     on HP-UX

   - bpo-45121(10): Fix issue where ‘Protocol.__init__’ raises
     ‘RecursionError’ when it's called directly or via ‘super()’.  Patch
     provided by Yurii Karabas.

   - bpo-44348(11): The deallocator function of the *note BaseException:
     55f. type now uses the trashcan mechanism to prevent stack
     overflow.  For example, when a *note RecursionError: d12. instance
     is raised, it can be linked to another RecursionError through the
     ‘__context__’ attribute or the ‘__traceback__’ attribute, and then
     a chain of exceptions is created.  When the chain is destroyed,
     nested deallocator function calls can crash with a stack overflow
     if the chain is too long compared to the available stack memory.
     Patch by Victor Stinner.

   - bpo-45123(12): Fix PyAiter_Check to only check for the __anext__
     presence (not for __aiter__).  Rename PyAiter_Check to
     PyAIter_Check, PyObject_GetAiter -> PyObject_GetAIter.

   - bpo-1514420(13): Interpreter no longer attempts to open files with
     names in angle brackets (like "<string>" or "<stdin>") when
     formatting an exception.

   - bpo-41031(14): Match C and Python code formatting of unprintable
     exceptions and exceptions in the *note __main__: 1. module.

   - bpo-37330(15): *note open(): 4c0, *note io.open(): 4c1, *note
     codecs.open(): 6e4. and *note fileinput.FileInput: 6db. no longer
     accept ‘'U'’ ("universal newline") in the file mode.  This flag was
     deprecated since Python 3.3.  Patch by Victor Stinner.

   - bpo-45083(16): When the interpreter renders an exception, its name
     now has a complete qualname.  Previously only the class name was
     concatenated to the module name, which sometimes resulted in an
     incorrect full name being displayed.

     (This issue impacted only the C code exception rendering, the *note
     traceback: e7. module was using qualname already).

   - bpo-34561(17): List sorting now uses the merge-ordering strategy
     from Munro and Wild's ‘powersort()’.  Unlike the former strategy,
     this is provably near-optimal in the entropy of the distribution of
     run lengths.  Most uses of ‘list.sort()’ probably won't see a
     significant time difference, but may see significant improvements
     in cases where the former strategy was exceptionally poor.
     However, as these are all fast linear-time approximations to a
     problem that's inherently at best quadratic-time to solve truly
     optimally, it's also possible to contrive cases where the former
     strategy did better.

   - bpo-45056(18): Compiler now removes trailing unused constants from
     co_consts.

   - bpo-45020(19): Add a new command line option, "-X
     frozen_modules=[on|off]" to opt out of (or into) using optional
     frozen modules.  This defaults to "on" (or "off" if it's running
     out of the source tree).

   - bpo-45012(20): In *note posix: 9b, release GIL during ‘stat()’,
     ‘lstat()’, and ‘fstatat()’ syscalls made by *note
     os.DirEntry.stat(): 15f5.  Patch by Stanisław Skonieczny.

   - bpo-45018(21): Fixed pickling of range iterators that iterated for
     over ‘2**32’ times.

   - bpo-45000(22): A *note SyntaxError: 173. is now raised when trying
     to delete *note __debug__: 77e.  Patch by Donghee Na.

   - bpo-44963(23): Implement ‘send()’ and ‘throw()’ methods for
     ‘anext_awaitable’ objects.  Patch by Pablo Galindo.

   - bpo-44962(24): Fix a race in WeakKeyDictionary, WeakValueDictionary
     and WeakSet when two threads attempt to commit the last pending
     removal.  This fixes asyncio.create_task and fixes a data loss in
     asyncio.run where shutdown_asyncgens is not run

   - bpo-24234(25): Implement the ‘__bytes__()’ special method on the
     *note bytes: 1a5. type, so a bytes object ‘b’ passes an
     ‘isinstance(b, typing.SupportsBytes)’ check.

   - bpo-24234(26): Implement the ‘__complex__()’ special method on the
     *note complex: 2c9. type, so a complex number ‘z’ passes an
     ‘isinstance(z, typing.SupportsComplex)’ check.

   - bpo-44954(27): Fixed a corner case bug where the result of
     ‘float.fromhex('0x.8p-1074')’ was rounded the wrong way.

   - bpo-44947(28): Refine the syntax error for trailing commas in
     import statements.  Patch by Pablo Galindo.

   - bpo-44945(29): Specialize the BINARY_ADD instruction using the PEP
     659 machinery.  Adds five new instructions:

        * BINARY_ADD_ADAPTIVE

        * BINARY_ADD_FLOAT

        * BINARY_ADD_INT

        * BINARY_ADD_UNICODE

        * BINARY_ADD_UNICODE_INPLACE_FAST

   - bpo-44929(30): Fix some edge cases of ‘enum.Flag’ string
     representation in the REPL. Patch by Pablo Galindo.

   - bpo-44914(31): Class version tags are no longer recycled.

     This means that a version tag serves as a unique identifier for the
     state of a class.  We rely on this for effective specialization of
     the LOAD_ATTR and other instructions.

   - bpo-44698(32): Restore behaviour of complex exponentiation with
     integer-valued exponent of type *note float: 2c8. or *note complex:
     2c9.

   - bpo-44895(33): A debug variable *note PYTHONDUMPREFSFILE: 1795. is
     added for creating a dump file which is generated by *note
     -with-trace-refs: 317.  Patch by Donghee Na.

   - bpo-44900(34): Add five superinstructions for PEP 659 quickening:

        * LOAD_FAST LOAD_FAST

        * STORE_FAST LOAD_FAST

        * LOAD_FAST LOAD_CONST

        * LOAD_CONST LOAD_FAST

        * STORE_FAST STORE_FAST

   - bpo-44889(35): Initial implementation of adaptive specialization of
     ‘LOAD_METHOD’.  The following specialized forms were added:

        * ‘LOAD_METHOD_CACHED’

        * ‘LOAD_METHOD_MODULE’

        * ‘LOAD_METHOD_CLASS’

   - bpo-44890(36): Specialization stats are always collected in debug
     builds.

   - bpo-44885(37): Correct the ast locations of f-strings with format
     specs and repeated expressions.  Patch by Pablo Galindo

   - bpo-44878(38): Remove the loop from the bytecode interpreter.  All
     instructions end with a DISPATCH macro, so the loop is now
     redundant.

   - bpo-44878(39): Remove switch statement for interpreter loop when
     using computed gotos.  This makes sure that we only have one
     dispatch table in the interpreter.

   - bpo-44874(40): Deprecate the old trashcan macros
     (‘Py_TRASHCAN_SAFE_BEGIN’/‘Py_TRASHCAN_SAFE_END’).  They should be
     replaced by the new macros ‘Py_TRASHCAN_BEGIN’ and
     ‘Py_TRASHCAN_END’.

   - bpo-44872(41): Use new trashcan macros (Py_TRASHCAN_BEGIN/END) in
     frameobject.c instead of the old ones (Py_TRASHCAN_SAFE_BEGIN/END).

   - bpo-33930(42): Fix segmentation fault with deep recursion when
     cleaning method objects.  Patch by Augusto Goulart and Pablo
     Galindo.

   - bpo-25782(43): Fix bug where ‘PyErr_SetObject’ hangs when the
     current exception has a cycle in its context chain.

   - bpo-44856(44): Fix reference leaks in the error paths of
     ‘update_bases()’ and ‘__build_class__’.  Patch by Pablo Galindo.

   - bpo-44826(45): Initial implementation of adaptive specialization of
     STORE_ATTR

     Three specialized forms of STORE_ATTR are added:

        * STORE_ATTR_SLOT

        * STORE_ATTR_SPLIT_KEYS

        * STORE_ATTR_WITH_HINT

   - bpo-44838(46): Fixed a bug that was causing the parser to raise an
     incorrect custom *note SyntaxError: 173. for invalid 'if'
     expressions.  Patch by Pablo Galindo.

   - bpo-44821(47): Create instance dictionaries (__dict__) eagerly, to
     improve regularity of object layout and assist specialization.

   - bpo-44792(48): Improve syntax errors for if expressions.  Patch by
     Miguel Brito

   - bpo-34013(49): Generalize the invalid legacy statement custom error
     message (like the one generated when "print" is called without
     parentheses) to include more generic expressions.  Patch by Pablo
     Galindo

   - bpo-44732(50): Rename ‘types.Union’ to ‘types.UnionType’.

   - bpo-44725(51): Expose specialization stats in python via
     ‘_opcode.get_specialization_stats()’.

   - bpo-44717(52): Improve AttributeError on circular imports of
     submodules.

   - bpo-44698(53): Fix undefined behaviour in complex object
     exponentiation.

   - bpo-44653(54): Support *note typing: ed. types in parameter
     substitution in the union type.

   - bpo-44676(55): Add ability to serialise ‘types.Union’ objects.
     Patch provided by Yurii Karabas.

   - bpo-44633(56): Parameter substitution of the union type with wrong
     types now raises ‘TypeError’ instead of returning *note
     NotImplemented: 776.

   - bpo-44661(57): Update ‘property_descr_set’ to use vectorcall if
     possible.  Patch by Donghee Na.

   - bpo-44662(58): Add ‘__module__’ to ‘types.Union’.  This also fixes
     ‘types.Union’ issues with ‘typing.Annotated’.  Patch provided by
     Yurii Karabas.

   - bpo-44655(59): Include the name of the type in unset __slots__
     attribute errors.  Patch by Pablo Galindo

   - bpo-44655(60): Don't include a missing attribute with the same name
     as the failing one when offering suggestions for missing
     attributes.  Patch by Pablo Galindo

   - bpo-44646(61): Fix the hash of the union type: it no longer depends
     on the order of arguments.

   - bpo-44636(62): Collapse union of equal types.  E.g.  the result of
     ‘int | int’ is now ‘int’.  Fix comparison of the union type with
     non-hashable objects.  E.g.  ‘int | str == {}’ no longer raises a
     TypeError.

   - bpo-44611(63): On Windows, *note os.urandom(): 4c7.: uses
     BCryptGenRandom API instead of CryptGenRandom API which is
     deprecated from Microsoft Windows API. Patch by Donghee Na.

   - bpo-44635(64): Convert ‘None’ to ‘type(None)’ in the union type
     constructor.

   - bpo-26280(65): Implement adaptive specialization for BINARY_SUBSCR

     Three specialized forms of BINARY_SUBSCR are added:

        * BINARY_SUBSCR_LIST_INT

        * BINARY_SUBSCR_TUPLE_INT

        * BINARY_SUBSCR_DICT

   - bpo-44589(66): Mapping patterns in ‘match’ statements with two or
     more equal literal keys will now raise a *note SyntaxError: 173. at
     compile-time.

   - bpo-44606(67): Fix ‘__instancecheck__’ and ‘__subclasscheck__’ for
     the union type.

   - bpo-42073(68): The ‘@classmethod’ decorator can now wrap other
     classmethod-like descriptors.

   - bpo-41972(69): Tuned the string-searching algorithm of fastsearch.h
     to have a shorter inner loop for most cases.

   - bpo-44590(70): All necessary data for executing a Python function
     (local variables, stack, etc) is now kept in a per-thread stack.
     Frame objects are lazily allocated on demand.  This increases
     performance by about 7% on the standard benchmark suite.
     Introspection and debugging are unaffected as frame objects are
     always available when needed.  Patch by Mark Shannon.

   - bpo-44584(71): The threading debug (‘PYTHONTHREADDEBUG’ environment
     variable) is deprecated in Python 3.10 and will be removed in
     Python 3.12.  This feature requires a debug build of Python.  Patch
     by Victor Stinner.

   - bpo-43895(72): An obsolete internal cache of shared object file
     handles added in 1995 that attempted, but did not guarantee, that a
     .so would not be dlopen'ed twice to work around flaws in mid-1990s
     posix-ish operating systems has been removed from dynload_shlib.c.

   - bpo-44490(73): *note typing: ed. now searches for type parameters
     in ‘types.Union’ objects.  ‘get_type_hints’ will also properly
     resolve annotations with nested ‘types.Union’ objects.  Patch
     provided by Yurii Karabas.

   - bpo-43950(74): Code objects can now provide the column information
     for instructions when available.  This is levaraged during
     traceback printing to show the expressions responsible for errors.

     Contributed by Pablo Galindo, Batuhan Taskaya and Ammar Askar as
     part of PEP 657(75).

   - bpo-44562(76): Remove uses of *note PyObject_GC_Del(): 1473. in
     error path when initializing *note types.GenericAlias: 78f.

   - bpo-41486(77): Fix a memory consumption and copying performance
     regression in earlier 3.10 beta releases if someone used an output
     buffer larger than 4GiB with zlib.decompress on input data that
     expands that large.

   - bpo-43908(78): Heap types with the *note Py_TPFLAGS_IMMUTABLETYPE:
     38d. flag can now inherit the PEP 590(79) vectorcall protocol.
     Previously, this was only possible for *note static types: 723.
     Patch by Erlend E. Aasland.

   - bpo-44553(80): Implement GC methods for ‘types.Union’ to break
     reference cycles and prevent memory leaks.

   - bpo-44490(81): Add ‘__parameters__’ attribute and ‘__getitem__’
     operator to ‘types.Union’.  Patch provided by Yurii Karabas.

   - bpo-44523(82): Remove the pass-through for *note hash(): 58f. of
     *note weakref.proxy: 9f5. objects to prevent unintended
     consequences when the original referred object dies while the proxy
     is part of a hashable object.  Patch by Pablo Galindo.

   - bpo-44483(83): Fix a crash in ‘types.Union’ objects when creating a
     union of an object with bad ‘__module__’ field.

   - bpo-44486(84): Modules will always have a dictionary, even when
     created by ‘types.ModuleType.__new__()’

   - bpo-44472(85): Fix ltrace functionality when exceptions are raised.
     Patch by Pablo Galindo

   - bpo-12022(86): A *note TypeError: 4dd. is now raised instead of an
     *note AttributeError: 2f6. in *note with: 577. and *note async
     with: 57a. statements for objects which do not support the *note
     context manager: 576. or *note asynchronous context manager: 579.
     protocols correspondingly.

   - bpo-44297(87): Make sure that the line number is set when entering
     a comprehension scope.  This ensures that backtraces including
     generator expressions show the correct line number.

   - bpo-44456(88): Improve the syntax error when mixing positional and
     keyword patterns.  Patch by Pablo Galindo.

   - bpo-44409(89): Fix error location information for tokenizer errors
     raised on initialization of the tokenizer.  Patch by Pablo Galindo.

   - bpo-44396(90): Fix a possible crash in the tokenizer when raising
     syntax errors for unclosed strings.  Patch by Pablo Galindo.

   - bpo-44376(91): Exact integer exponentiation (like ‘i**2’ or ‘pow(i,
     2)’) with a small exponent is much faster, due to reducing overhead
     in such cases.

   - bpo-44313(92): Directly imported objects and modules (through
     import and from import statements) don't generate
     ‘LOAD_METHOD’/‘CALL_METHOD’ for directly accessed objects on their
     namespace.  They now use the regular ‘LOAD_ATTR’/‘CALL_FUNCTION’.

   - bpo-44338(93): Implement adaptive specialization for LOAD_GLOBAL

     Two specialized forms of LOAD_GLOBAL are added:

        * LOAD_GLOBAL_MODULE

        * LOAD_GLOBAL_BUILTIN

   - bpo-44368(94): Improve syntax errors for invalid "as" targets.
     Patch by Pablo Galindo

   - bpo-44349(95): Fix an edge case when displaying text from files
     with encoding in syntax errors.  Patch by Pablo Galindo.

   - bpo-44337(96): Initial implementation of adaptive specialization of
     LOAD_ATTR

     Four specialized forms of LOAD_ATTR are added:

        * LOAD_ATTR_SLOT

        * LOAD_ATTR_SPLIT_KEYS

        * LOAD_ATTR_WITH_HINT

        * LOAD_ATTR_MODULE

   - bpo-44335(97): Fix a regression when identifying incorrect
     characters in syntax errors.  Patch by Pablo Galindo

   - bpo-43693(98): Computation of the offsets of cell variables is done
     in the compiler instead of at runtime.  This reduces the overhead
     of handling cell and free variables, especially in the case where a
     variable is both an argument and cell variable.

   - bpo-44317(99): Improve tokenizer error with improved locations.
     Patch by Pablo Galindo.

   - bpo-44304(100): Fix a crash in the *note sqlite3: ba. module that
     happened when the garbage collector clears ‘sqlite.Statement’
     objects.  Patch by Pablo Galindo

   - bpo-44305(101): Improve error message for ‘try’ blocks without
     ‘except’ or ‘finally’ blocks.  Patch by Pablo Galindo.

   - bpo-43413(102): Constructors of subclasses of some builtin classes
     (e.g.  *note tuple: 322, *note list: 5b6, *note frozenset: 57e.) no
     longer accept arbitrary keyword arguments.  [reverted in 3.11a4]
     Subclass of *note set: 57d. can now define a ‘__new__()’ method
     with additional keyword parameters without overriding also
     ‘__init__()’.

   - bpo-43667(103): Improve Unicode support in non-UTF locales on
     Oracle Solaris.  This issue does not affect other Solaris systems.

   - bpo-43693(104): A new opcode MAKE_CELL has been added that
     effectively moves some of the work done on function entry into the
     compiler and into the eval loop.  In addition to creating the
     required cell objects, the new opcode converts relevant arguments
     (and other locals) to cell variables on function entry.

   - bpo-44232(105): Fix a regression in *note type(): cef. when a
     metaclass raises an exception.  The C function ‘type_new()’ must
     properly report the exception when a metaclass constructor raises
     an exception and the winner class is not the metaclass.  Patch by
     Victor Stinner.

   - bpo-44201(106): Avoid side effects of checking for specialized
     syntax errors in the REPL that was causing it to ask for extra
     tokens after a syntax error had been detected.  Patch by Pablo
     Galindo

   - bpo-43693(107): ‘PyCodeObject’ gained ‘co_fastlocalnames’ and
     ‘co_fastlocalkinds’ as the authoritative source of fast locals
     info.  Marshaled code objects have changed accordingly.

   - bpo-44184(108): Fix a crash at Python exit when a deallocator
     function removes the last strong reference to a heap type.  Patch
     by Victor Stinner.

   - bpo-44187(109): Implement quickening in the interpreter.  This
     offers no advantages as yet, but is an enabler of future
     optimizations.  See PEP 659 for full explanation.

   - bpo-44180(110): The parser doesn't report generic syntax errors
     that happen in a position further away that the one it reached in
     the first pass.  Patch by Pablo Galindo

   - bpo-44168(111): Fix error message in the parser involving keyword
     arguments with invalid expressions.  Patch by Pablo Galindo

   - bpo-44156(112): String caches in ‘compile.c’ are now subinterpreter
     compatible.

   - bpo-44143(113): Fixed a crash in the parser that manifest when
     raising tokenizer errors when an existing exception was present.
     Patch by Pablo Galindo.

   - bpo-44032(114): Move 'fast' locals and other variables from the
     frame object to a per-thread datastack.

   - bpo-44114(115): Fix incorrect dictkeys_reversed and
     dictitems_reversed function signatures in C code, which broke
     webassembly builds.

   - bpo-44110(116): Improve ‘str.__getitem__()’ error message

   - bpo-26110(117): Add ‘CALL_METHOD_KW’ opcode to speed up method
     calls with keyword arguments.  Idea originated from PyPy.  A side
     effect is executing ‘CALL_METHOD’ is now branchless in the
     evaluation loop.

   - bpo-28307(118): Compiler now optimizes simple C-style formatting
     with literal format containing only format codes %s, %r and %a by
     converting them to f-string expressions.

   - bpo-43149(119): Correct the syntax error message regarding multiple
     exception types to not refer to "exception groups".  Patch by Pablo
     Galindo

   - bpo-43822(120): The parser will prioritize tokenizer errors over
     custom syntax errors when raising exceptions.  Patch by Pablo
     Galindo.

   - bpo-40222(121): "Zero cost" exception handling.

        * Uses a lookup table to determine how to handle exceptions.

        * Removes SETUP_FINALLY and POP_TOP block instructions,
          eliminating the runtime overhead of try statements.

        * Reduces the size of the frame object by about 60%.

     Patch by Mark Shannon

   - bpo-43918(122): Document the signature and ‘default’ argument in
     the docstring of the new ‘anext’ builtin.

   - bpo-43833(123): Emit a deprecation warning if the numeric literal
     is immediately followed by one of keywords: and, else, for, if, in,
     is, or.  Raise a syntax error with more informative message if it
     is immediately followed by other keyword or identifier.

   - bpo-43879(124): Add native_thread_id to PyThreadState.  Patch by
     Gabriele N. Tornetta.

   - bpo-43693(125): Compute cell offsets relative to locals in
     compiler.  Allows the interpreter to treats locals and cells a
     single array, which is slightly more efficient.  Also make the
     LOAD_CLOSURE opcode an alias for LOAD_FAST. Preserving LOAD_CLOSURE
     helps keep bytecode a bit more readable.

   - bpo-17792(126): More accurate error messages for access of unbound
     locals or free vars.

   - bpo-28146(127): Fix a confusing error message in *note
     str.format(): 5c7.

   - bpo-11105(128): When compiling *note ast.AST: 18c. objects with
     recursive references through *note compile(): 178, the interpreter
     doesn't crash anymore instead it raises a *note RecursionError:
     d12.

   - bpo-39091(129): Fix crash when using passing a non-exception to a
     generator's ‘throw()’ method.  Patch by Noah Oxer

   - bpo-33346(130): Asynchronous comprehensions are now allowed inside
     comprehensions in asynchronous functions.  Outer comprehensions
     implicitly become asynchronous.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43760

   (2) https://bugs.python.org/issue?@action=redirect&bpo=45061

   (3) https://bugs.python.org/issue?@action=redirect&bpo=24076

   (4) https://bugs.python.org/issue?@action=redirect&bpo=45190

   (5) https://bugs.python.org/issue?@action=redirect&bpo=45167

   (6) https://bugs.python.org/issue?@action=redirect&bpo=45155

   (7) https://bugs.python.org/issue?@action=redirect&bpo=44219

   (8) https://bugs.python.org/issue?@action=redirect&bpo=44219

   (9) https://bugs.python.org/issue?@action=redirect&bpo=44959

   (10) https://bugs.python.org/issue?@action=redirect&bpo=45121

   (11) https://bugs.python.org/issue?@action=redirect&bpo=44348

   (12) https://bugs.python.org/issue?@action=redirect&bpo=45123

   (13) https://bugs.python.org/issue?@action=redirect&bpo=1514420

   (14) https://bugs.python.org/issue?@action=redirect&bpo=41031

   (15) https://bugs.python.org/issue?@action=redirect&bpo=37330

   (16) https://bugs.python.org/issue?@action=redirect&bpo=45083

   (17) https://bugs.python.org/issue?@action=redirect&bpo=34561

   (18) https://bugs.python.org/issue?@action=redirect&bpo=45056

   (19) https://bugs.python.org/issue?@action=redirect&bpo=45020

   (20) https://bugs.python.org/issue?@action=redirect&bpo=45012

   (21) https://bugs.python.org/issue?@action=redirect&bpo=45018

   (22) https://bugs.python.org/issue?@action=redirect&bpo=45000

   (23) https://bugs.python.org/issue?@action=redirect&bpo=44963

   (24) https://bugs.python.org/issue?@action=redirect&bpo=44962

   (25) https://bugs.python.org/issue?@action=redirect&bpo=24234

   (26) https://bugs.python.org/issue?@action=redirect&bpo=24234

   (27) https://bugs.python.org/issue?@action=redirect&bpo=44954

   (28) https://bugs.python.org/issue?@action=redirect&bpo=44947

   (29) https://bugs.python.org/issue?@action=redirect&bpo=44945

   (30) https://bugs.python.org/issue?@action=redirect&bpo=44929

   (31) https://bugs.python.org/issue?@action=redirect&bpo=44914

   (32) https://bugs.python.org/issue?@action=redirect&bpo=44698

   (33) https://bugs.python.org/issue?@action=redirect&bpo=44895

   (34) https://bugs.python.org/issue?@action=redirect&bpo=44900

   (35) https://bugs.python.org/issue?@action=redirect&bpo=44889

   (36) https://bugs.python.org/issue?@action=redirect&bpo=44890

   (37) https://bugs.python.org/issue?@action=redirect&bpo=44885

   (38) https://bugs.python.org/issue?@action=redirect&bpo=44878

   (39) https://bugs.python.org/issue?@action=redirect&bpo=44878

   (40) https://bugs.python.org/issue?@action=redirect&bpo=44874

   (41) https://bugs.python.org/issue?@action=redirect&bpo=44872

   (42) https://bugs.python.org/issue?@action=redirect&bpo=33930

   (43) https://bugs.python.org/issue?@action=redirect&bpo=25782

   (44) https://bugs.python.org/issue?@action=redirect&bpo=44856

   (45) https://bugs.python.org/issue?@action=redirect&bpo=44826

   (46) https://bugs.python.org/issue?@action=redirect&bpo=44838

   (47) https://bugs.python.org/issue?@action=redirect&bpo=44821

   (48) https://bugs.python.org/issue?@action=redirect&bpo=44792

   (49) https://bugs.python.org/issue?@action=redirect&bpo=34013

   (50) https://bugs.python.org/issue?@action=redirect&bpo=44732

   (51) https://bugs.python.org/issue?@action=redirect&bpo=44725

   (52) https://bugs.python.org/issue?@action=redirect&bpo=44717

   (53) https://bugs.python.org/issue?@action=redirect&bpo=44698

   (54) https://bugs.python.org/issue?@action=redirect&bpo=44653

   (55) https://bugs.python.org/issue?@action=redirect&bpo=44676

   (56) https://bugs.python.org/issue?@action=redirect&bpo=44633

   (57) https://bugs.python.org/issue?@action=redirect&bpo=44661

   (58) https://bugs.python.org/issue?@action=redirect&bpo=44662

   (59) https://bugs.python.org/issue?@action=redirect&bpo=44655

   (60) https://bugs.python.org/issue?@action=redirect&bpo=44655

   (61) https://bugs.python.org/issue?@action=redirect&bpo=44646

   (62) https://bugs.python.org/issue?@action=redirect&bpo=44636

   (63) https://bugs.python.org/issue?@action=redirect&bpo=44611

   (64) https://bugs.python.org/issue?@action=redirect&bpo=44635

   (65) https://bugs.python.org/issue?@action=redirect&bpo=26280

   (66) https://bugs.python.org/issue?@action=redirect&bpo=44589

   (67) https://bugs.python.org/issue?@action=redirect&bpo=44606

   (68) https://bugs.python.org/issue?@action=redirect&bpo=42073

   (69) https://bugs.python.org/issue?@action=redirect&bpo=41972

   (70) https://bugs.python.org/issue?@action=redirect&bpo=44590

   (71) https://bugs.python.org/issue?@action=redirect&bpo=44584

   (72) https://bugs.python.org/issue?@action=redirect&bpo=43895

   (73) https://bugs.python.org/issue?@action=redirect&bpo=44490

   (74) https://bugs.python.org/issue?@action=redirect&bpo=43950

   (75) https://peps.python.org/pep-0657/

   (76) https://bugs.python.org/issue?@action=redirect&bpo=44562

   (77) https://bugs.python.org/issue?@action=redirect&bpo=41486

   (78) https://bugs.python.org/issue?@action=redirect&bpo=43908

   (79) https://peps.python.org/pep-0590/

   (80) https://bugs.python.org/issue?@action=redirect&bpo=44553

   (81) https://bugs.python.org/issue?@action=redirect&bpo=44490

   (82) https://bugs.python.org/issue?@action=redirect&bpo=44523

   (83) https://bugs.python.org/issue?@action=redirect&bpo=44483

   (84) https://bugs.python.org/issue?@action=redirect&bpo=44486

   (85) https://bugs.python.org/issue?@action=redirect&bpo=44472

   (86) https://bugs.python.org/issue?@action=redirect&bpo=12022

   (87) https://bugs.python.org/issue?@action=redirect&bpo=44297

   (88) https://bugs.python.org/issue?@action=redirect&bpo=44456

   (89) https://bugs.python.org/issue?@action=redirect&bpo=44409

   (90) https://bugs.python.org/issue?@action=redirect&bpo=44396

   (91) https://bugs.python.org/issue?@action=redirect&bpo=44376

   (92) https://bugs.python.org/issue?@action=redirect&bpo=44313

   (93) https://bugs.python.org/issue?@action=redirect&bpo=44338

   (94) https://bugs.python.org/issue?@action=redirect&bpo=44368

   (95) https://bugs.python.org/issue?@action=redirect&bpo=44349

   (96) https://bugs.python.org/issue?@action=redirect&bpo=44337

   (97) https://bugs.python.org/issue?@action=redirect&bpo=44335

   (98) https://bugs.python.org/issue?@action=redirect&bpo=43693

   (99) https://bugs.python.org/issue?@action=redirect&bpo=44317

   (100) https://bugs.python.org/issue?@action=redirect&bpo=44304

   (101) https://bugs.python.org/issue?@action=redirect&bpo=44305

   (102) https://bugs.python.org/issue?@action=redirect&bpo=43413

   (103) https://bugs.python.org/issue?@action=redirect&bpo=43667

   (104) https://bugs.python.org/issue?@action=redirect&bpo=43693

   (105) https://bugs.python.org/issue?@action=redirect&bpo=44232

   (106) https://bugs.python.org/issue?@action=redirect&bpo=44201

   (107) https://bugs.python.org/issue?@action=redirect&bpo=43693

   (108) https://bugs.python.org/issue?@action=redirect&bpo=44184

   (109) https://bugs.python.org/issue?@action=redirect&bpo=44187

   (110) https://bugs.python.org/issue?@action=redirect&bpo=44180

   (111) https://bugs.python.org/issue?@action=redirect&bpo=44168

   (112) https://bugs.python.org/issue?@action=redirect&bpo=44156

   (113) https://bugs.python.org/issue?@action=redirect&bpo=44143

   (114) https://bugs.python.org/issue?@action=redirect&bpo=44032

   (115) https://bugs.python.org/issue?@action=redirect&bpo=44114

   (116) https://bugs.python.org/issue?@action=redirect&bpo=44110

   (117) https://bugs.python.org/issue?@action=redirect&bpo=26110

   (118) https://bugs.python.org/issue?@action=redirect&bpo=28307

   (119) https://bugs.python.org/issue?@action=redirect&bpo=43149

   (120) https://bugs.python.org/issue?@action=redirect&bpo=43822

   (121) https://bugs.python.org/issue?@action=redirect&bpo=40222

   (122) https://bugs.python.org/issue?@action=redirect&bpo=43918

   (123) https://bugs.python.org/issue?@action=redirect&bpo=43833

   (124) https://bugs.python.org/issue?@action=redirect&bpo=43879

   (125) https://bugs.python.org/issue?@action=redirect&bpo=43693

   (126) https://bugs.python.org/issue?@action=redirect&bpo=17792

   (127) https://bugs.python.org/issue?@action=redirect&bpo=28146

   (128) https://bugs.python.org/issue?@action=redirect&bpo=11105

   (129) https://bugs.python.org/issue?@action=redirect&bpo=39091

   (130) https://bugs.python.org/issue?@action=redirect&bpo=33346


File: python.info,  Node: Library<28>,  Next: Documentation<23>,  Prev: Core and Builtins<29>,  Up: Python 3 11 0 alpha 1

1.23.29.3 Library
.................

   - bpo-45371(1): Fix clang rpath issue in ‘distutils’.  The
     UnixCCompiler now uses correct clang option to add a runtime
     library directory (rpath) to a shared library.

   - bpo-45329(2): Fix freed memory access in ‘pyexpat.xmlparser’ when
     building it with an installed expat library <= 2.2.0.

   - bpo-41710(3): On Unix, if the ‘sem_clockwait()’ function is
     available in the C library (glibc 2.30 and newer), the *note
     threading.Lock.acquire(): 63e. method now uses the monotonic clock
     (*note time.CLOCK_MONOTONIC: b35.) for the timeout, rather than
     using the system clock (*note time.CLOCK_REALTIME: 63f.), to not be
     affected by system clock changes.  Patch by Victor Stinner.

   - bpo-1596321(4): Fix the ‘threading._shutdown()’ function when the
     *note threading: d6. module was imported first from a thread
     different than the main thread: no longer log an error at Python
     exit.

   - bpo-45274(5): Fix a race condition in the *note Thread.join():
     117c. method of the *note threading: d6. module.  If the function
     is interrupted by a signal and the signal handler raises an
     exception, make sure that the thread remains in a consistent state
     to prevent a deadlock.  Patch by Victor Stinner.

   - bpo-21302(6): In Unix operating systems, *note time.sleep(): 642.
     now uses the ‘nanosleep()’ function, if ‘clock_nanosleep()’ is not
     available but ‘nanosleep()’ is available.  ‘nanosleep()’ allows to
     sleep with nanosecond precision.

   - bpo-21302(7): On Windows, *note time.sleep(): 642. now uses a
     waitable timer which has a resolution of 100 nanoseconds (10^-7
     seconds).  Previously, it had a resolution of 1 millisecond (10^-3
     seconds).  Patch by Benjamin Szőke and Victor Stinner.

   - bpo-45238(8): Fix ‘unittest.IsolatedAsyncioTestCase.debug()’: it
     runs now asynchronous methods and callbacks.

   - bpo-36674(9): *note unittest.TestCase.debug(): 1797. raises now a
     *note unittest.SkipTest: f87. if the class or the test method are
     decorated with the skipping decorator.

   - bpo-45235(10): Fix an issue where argparse would not preserve
     values in a provided namespace when using a subparser with
     defaults.

   - bpo-45183(11): Have zipimport.zipimporter.find_spec() not raise an
     exception when the underlying zip file has been deleted and the
     internal cache has been reset via invalidate_cache().

   - bpo-45234(12): Fixed a regression in *note copyfile(): 9fc, *note
     copy(): 9fd, *note copy2(): 9fe. raising *note FileNotFoundError:
     e67. when source is a directory, which should raise *note
     IsADirectoryError: ffc.

   - bpo-45228(13): Fix stack buffer overflow in parsing J1939 network
     address.

   - bpo-45225(14): use map function instead of genexpr in capwords.

   - bpo-42135(15): Fix typo: ‘importlib.find_loader’ is really slated
     for removal in Python 3.12 not 3.10, like the others in PR 25169.

     Patch by Hugo van Kemenade.

   - bpo-20524(16): Improves error messages on ‘.format()’ operation for
     ‘str’, ‘float’, ‘int’, and ‘complex’.  New format now shows the
     problematic pattern and the object type.

   - bpo-45168(17): Change *note dis.dis(): ad8. output to omit op arg
     values that cannot be resolved due to ‘co_consts’, ‘co_names’ etc
     not being provided.  Previously the oparg itself was repeated in
     the value field, which is not useful and can be confusing.

   - bpo-21302(18): In Unix operating systems, *note time.sleep(): 642.
     now uses the ‘clock_nanosleep()’ function, if available, which
     allows to sleep for an interval specified with nanosecond
     precision.

   - bpo-45173(19): Remove from the *note configparser: 1b. module: the
     ‘SafeConfigParser’ class, the ‘filename’ property of the *note
     ParsingError: 4ab. class, the ‘readfp()’ method of the *note
     ConfigParser: 1aa. class, deprecated since Python 3.2.

     Patch by Hugo van Kemenade.

   - bpo-44987(20): Pure ASCII strings are now normalized in constant
     time by *note unicodedata.normalize(): 679.  Patch by Donghee Na.

   - bpo-35474(21): Calling *note mimetypes.guess_all_extensions():
     1798. with ‘strict=False’ no longer affects the result of the
     following call with ‘strict=True’.  Also, mutating the returned
     list no longer affects the global state.

   - bpo-45166(22): *note typing.get_type_hints(): 657. now works with
     *note Final: 24c. wrapped in *note ForwardRef: 1748.

   - bpo-45162(23): Remove many old deprecated *note unittest: ef.
     features:

        * "‘fail*’" and "‘assert*’" aliases of *note TestCase: 3f4.
          methods.

        * Broken from start *note TestCase: 3f4. method
          ‘assertDictContainsSubset()’.

        * Ignored ‘<unittest.TestLoader.loadTestsFromModule>
          TestLoader.loadTestsFromModule()’ parameter 'use_load_tests'.

        * Old alias ‘_TextTestResult’ of *note TextTestResult: 4d5.

   - bpo-38371(24): Remove the deprecated ‘split()’ method of
     ‘_tkinter.TkappType’.  Patch by Erlend E. Aasland.

   - bpo-20499(25): Improve the speed and accuracy of
     statistics.pvariance().

   - bpo-45132(26): Remove *note __getitem__(): 266. methods of *note
     xml.dom.pulldom.DOMEventStream: 6d9, *note
     wsgiref.util.FileWrapper: 6da. and *note fileinput.FileInput: 6db,
     deprecated since Python 3.9.

     Patch by Hugo van Kemenade.

   - bpo-45129(27): Due to significant security concerns, the
     'reuse_address' parameter of *note
     asyncio.loop.create_datagram_endpoint(): 6d7, disabled in Python
     3.9, is now entirely removed.  This is because of the behavior of
     the socket option ‘SO_REUSEADDR’ in UDP.

     Patch by Hugo van Kemenade.

   - bpo-45124(28): The ‘bdist_msi’ command, deprecated in Python 3.9,
     is now removed.

     Use ‘bdist_wheel’ (wheel packages) instead.

     Patch by Hugo van Kemenade.

   - bpo-30856(29): *note unittest.TestResult: 1100. methods *note
     addFailure(): 1799, *note addError(): 179a, *note addSkip(): 179b.
     and *note addSubTest(): 179c. are now called immediately after
     raising an exception in test or finishing a subtest.  Previously
     they were called only after finishing the test clean up.

   - bpo-45034(30): Changes how error is formatted for ‘struct.pack’
     with ‘'H'’ and ‘'h'’ modes and too large / small numbers.  Now it
     shows the actual numeric limits, while previously it was showing
     arithmetic expressions.

   - bpo-25894(31): *note unittest: ef. now always reports skipped and
     failed subtests separately: separate characters in default mode and
     separate lines in verbose mode.  Also the test description is now
     output for errors in test method, class and module cleanups.

   - bpo-45081(32): Fix issue when dataclasses that inherit from
     ‘typing.Protocol’ subclasses have wrong ‘__init__’.  Patch provided
     by Yurii Karabas.

   - bpo-45085(33): The ‘binhex’ module, deprecated in Python 3.9, is
     now removed.  The following *note binascii: c. functions,
     deprecated in Python 3.9, are now also removed:

        * ‘a2b_hqx()’, ‘b2a_hqx()’;

        * ‘rlecode_hqx()’, ‘rledecode_hqx()’.

     The *note binascii.crc_hqx(): 6d8. function remains available.

     Patch by Victor Stinner.

   - bpo-40360(34): The ‘lib2to3’ package is now deprecated and may not
     be able to parse Python 3.10 or newer.  See the PEP 617(35) (New
     PEG parser for CPython).  Patch by Victor Stinner.

   - bpo-45075(36): Rename ‘traceback.StackSummary.format_frame()’ to
     *note traceback.StackSummary.format_frame_summary(): 648.  This
     method was added for 3.11 so it was not released yet.

     Updated code and docs to better distinguish frame and FrameSummary.

   - bpo-31299(37): Add option to completely drop frames from a
     traceback by returning ‘None’ from a ‘format_frame()’ override.

   - bpo-41620(38): *note run(): 10ff. now always return a *note
     TestResult: 1100. instance.  Previously it returned ‘None’ if the
     test class or method was decorated with a skipping decorator.

   - bpo-45021(39): Fix a potential deadlock at shutdown of forked
     children when using *note concurrent.futures: 1a. module

   - bpo-43913(40): Fix bugs in cleaning up classes and modules in *note
     unittest: ef.:

        * Functions registered with *note addModuleCleanup(): 9f0. were
          not called unless the user defines ‘tearDownModule()’ in their
          test module.

        * Functions registered with *note addClassCleanup(): 9f1. were
          not called if ‘tearDownClass’ is set to ‘None’.

        * Buffering in *note TestResult: 1100. did not work with
          functions registered with ‘addClassCleanup()’ and
          ‘addModuleCleanup()’.

        * Errors in functions registered with ‘addClassCleanup()’ and
          ‘addModuleCleanup()’ were not handled correctly in buffered
          and debug modes.

        * Errors in ‘setUpModule()’ and functions registered with
          ‘addModuleCleanup()’ were reported in wrong order.

        * And several lesser bugs.

   - bpo-45030(41): Fix integer overflow in pickling and copying the
     range iterator.

   - bpo-45001(42): Made email date parsing more robust against
     malformed input, namely a whitespace-only ‘Date:’ header.  Patch by
     Wouter Bolsterlee.

   - bpo-45010(43): Remove support of special method ‘__div__’ in *note
     unittest.mock: f0.  It is not used in Python 3.

   - bpo-39218(44): Improve accuracy of variance calculations by using
     ‘x*x’ instead of ‘x**2’.

   - bpo-43613(45): Improve the speed of *note gzip.compress(): 5e4. and
     *note gzip.decompress(): 11a5. by compressing and decompressing at
     once in memory instead of in a streamed fashion.

   - bpo-37596(46): Ensure that *note set: 57d. and *note frozenset:
     57e. objects are always *note marshalled: 80. reproducibly.

   - bpo-44019(47): A new function ‘operator.call’ has been added, such
     that ‘operator.call(obj, *args, **kwargs) == obj(*args, **kwargs)’.

   - bpo-42255(48): ‘webbrowser.MacOSX’ is deprecated and will be
     removed in Python 3.13.  It is untested and undocumented and also
     not used by *note webbrowser: fd. itself.  Patch by Donghee Na.

   - bpo-44955(49): Method *note stopTestRun(): 12df. is now always
     called in pair with method *note startTestRun(): 12de. for *note
     TestResult: 1100. objects implicitly created in *note run(): 10ff.
     Previously it was not called for test methods and classes decorated
     with a skipping decorator.

   - bpo-39039(50): tarfile.open raises *note ReadError: 179d. when a
     zlib error occurs during file extraction.

   - bpo-44935(51): *note subprocess: c1. on Solaris now also uses *note
     os.posix_spawn(): 205. for better performance.

   - bpo-44911(52): *note IsolatedAsyncioTestCase: 2de. will no longer
     throw an exception while cancelling leaked tasks.  Patch by Bar
     Harel.

   - bpo-41322(53): Added ‘DeprecationWarning’ for tests and async tests
     that return a value!=None (as this may indicate an improperly
     written test, for example a test written as a generator function).

   - bpo-44524(54): Make exception message more useful when subclass
     from typing special form alias.  Patch provided by Yurii Karabas.

   - bpo-38956(55): ‘argparse.BooleanOptionalAction’'s default value is
     no longer printed twice when used with *note
     argparse.ArgumentDefaultsHelpFormatter: 179e.

   - bpo-44860(56): Fix the ‘posix_user’ scheme in *note sysconfig: c5.
     to not depend on *note sys.platlibdir: 8dc.

   - bpo-44859(57): Improve error handling in *note sqlite3: ba. and
     raise more accurate exceptions.

        * *note MemoryError: 15bc. is now raised instead of *note
          sqlite3.Warning: 172a. when memory is not enough for encoding
          a statement to UTF-8 in ‘Connection.__call__()’ and
          ‘Cursor.execute()’.

        * ‘UnicodEncodeError’ is now raised instead of *note
          sqlite3.Warning: 172a. when the statement contains surrogate
          characters in ‘Connection.__call__()’ and ‘Cursor.execute()’.

        * *note TypeError: 4dd. is now raised instead of *note
          ValueError: 1e7. for non-string script argument in
          ‘Cursor.executescript()’.

        * *note ValueError: 1e7. is now raised for script containing the
          null character instead of truncating it in
          ‘Cursor.executescript()’.

        * Correctly handle exceptions raised when getting boolean value
          of the result of the progress handler.

        * Add many tests covering different corner cases.

   - bpo-44581(58): Upgrade bundled pip to 21.2.3 and setuptools to
     57.4.0

   - bpo-44849(59): Fix the *note os.set_inheritable(): e9f. function on
     FreeBSD 14 for file descriptor opened with the *note O_PATH: f15.
     flag: ignore the *note EBADF: 8ff. error on ‘ioctl()’, fallback on
     the ‘fcntl()’ implementation.  Patch by Victor Stinner.

   - bpo-44605(60): The @functools.total_ordering() decorator now works
     with metaclasses.

   - bpo-44524(61): Fixed an issue wherein the ‘__name__’ and
     ‘__qualname__’ attributes of subscribed specialforms could be
     ‘None’.

   - bpo-44839(62): *note MemoryError: 15bc. raised in user-defined
     functions will now produce a ‘MemoryError’ in *note sqlite3: ba.
     *note OverflowError: 825. will now be converted to *note DataError:
     179f.  Previously *note OperationalError: 17a0. was produced in
     these cases.

   - bpo-44822(63): *note sqlite3: ba. user-defined functions and
     aggregators returning *note strings: 3f2. with embedded NUL
     characters are no longer truncated.  Patch by Erlend E. Aasland.

   - bpo-44801(64): Ensure that the *note ParamSpec: 142. variable in
     Callable can only be substituted with a parameters expression (a
     list of types, an ellipsis, ParamSpec or Concatenate).

   - bpo-44806(65): Non-protocol subclasses of *note typing.Protocol:
     249. ignore now the ‘__init__’ method inherited from protocol base
     classes.

   - bpo-27275(66): *note collections.OrderedDict.popitem(): 1280. and
     ‘collections.OrderedDict.pop()’ no longer call ‘__getitem__’ and
     ‘__delitem__’ methods of the OrderedDict subclasses.

   - bpo-44793(67): Fix checking the number of arguments when subscribe
     a generic type with ‘ParamSpec’ parameter.

   - bpo-44784(68): In importlib.metadata tests, override warnings
     behavior under expected DeprecationWarnings (importlib_metadata
     4.6.3).

   - bpo-44667(69): The *note tokenize.tokenize(): 481. doesn't
     incorrectly generate a ‘NEWLINE’ token if the source doesn't end
     with a new line character but the last line is a comment, as the
     function is already generating a ‘NL’ token.  Patch by Pablo
     Galindo

   - bpo-44771(70): Added ‘importlib.simple’ module implementing
     adapters from a low-level resources reader interface to a
     ‘TraversableResources’ interface.  Legacy API (‘path’, ‘contents’,
     ...)  is now supported entirely by the ‘.files()’ API with a
     compatibility shim supplied for resource loaders without that
     functionality.  Feature parity with ‘importlib_resources’ 5.2.

   - bpo-44752(71): ‘rcompleter’ does not call *note getattr(): b78. on
     *note property: 180. objects to avoid the side-effect of evaluating
     the corresponding method.

   - bpo-44747(72): Refactor usage of ‘sys._getframe’ in ‘typing’
     module.  Patch provided by Yurii Karabas.

   - bpo-42378(73): Fixes the issue with log file being overwritten when
     *note logging.FileHandler: 17a1. is used in *note atexit: 9. with
     'filemode' set to ‘'w'’.  Note this will cause the message in
     'atexit' not being logged if the log stream is already closed due
     to shutdown of logging.

   - bpo-44720(74): ‘weakref.proxy’ objects referencing non-iterators
     now raise ‘TypeError’ rather than dereferencing the null
     ‘tp_iternext’ slot and crashing.

   - bpo-44704(75): The implementation of ‘collections.abc.Set._hash()’
     now matches that of ‘frozenset.__hash__()’.

   - bpo-44666(76): Fixed issue in *note compileall.compile_file(): d87.
     when ‘sys.stdout’ is redirected.  Patch by Stefan Hölzl.

   - bpo-44688(77): *note sqlite3.Connection.create_collation(): 61c.
     now accepts non-ASCII collation names.  Patch by Erlend E. Aasland.

   - bpo-44690(78): Adopt 'binacii.a2b_base64"s strict mode in
     'base64.b64decode'.

   - bpo-42854(79): Fixed a bug in the ‘_ssl’ module that was throwing
     *note OverflowError: 825. when using ‘_ssl._SSLSocket.write()’ and
     ‘_ssl._SSLSocket.read()’ for a big value of the ‘len’ parameter.
     Patch by Pablo Galindo.

   - bpo-44686(80): Replace ‘unittest.mock._importer’ with
     ‘pkgutil.resolve_name’.

   - bpo-44353(81): Make ‘NewType.__call__’ faster by implementing it in
     C. Patch provided by Yurii Karabas.

   - bpo-44682(82): Change the *note pdb: 94. 'commands' directive to
     disallow setting commands for an invalid breakpoint and to display
     an appropriate error.

   - bpo-44353(83): Refactor ‘typing.NewType’ from function into
     callable class.  Patch provided by Yurii Karabas.

   - bpo-44678(84): Added a separate error message for discontinuous
     padding in 'binascii.a2b_base64' strict mode.

   - bpo-44524(85): Add missing ‘__name__’ and ‘__qualname__’ attributes
     to ‘typing’ module classes.  Patch provided by Yurii Karabas.

   - bpo-40897(86): Give priority to using the current class constructor
     in *note inspect.signature(): 6dc.  Patch by Weipeng Hong.

   - bpo-44638(87): Add a reference to the zipp project and hint as to
     how to use it.

   - bpo-44648(88): Fixed wrong error being thrown by *note
     inspect.getsource(): 14ca. when examining a class in the
     interactive session.  Instead of *note TypeError: 4dd, it should be
     *note OSError: 350. with appropriate error message.

   - bpo-44608(89): Fix memory leak in ‘_tkinter._flatten()’ if it is
     called with a sequence or set, but not list or tuple.

   - bpo-44594(90): Fix an edge case of ‘ExitStack’ and ‘AsyncExitStack’
     exception chaining.  They will now match ‘with’ block behavior when
     ‘__context__’ is explicitly set to ‘None’ when the exception is in
     flight.

   - bpo-42799(91): In *note fnmatch: 52, the cache size for compiled
     regex patterns (*note functools.lru_cache(): 993.) was bumped up
     from 256 to 32768, affecting functions: *note fnmatch.fnmatch():
     17a2, *note fnmatch.fnmatchcase(): 17a3, *note fnmatch.filter():
     17a4.

   - bpo-41928(92): Update *note shutil.copyfile(): 9fc. to raise *note
     FileNotFoundError: e67. instead of confusing *note
     IsADirectoryError: ffc. when a path ending with a ‘os.path.sep’
     does not exist; *note shutil.copy(): 9fd. and *note shutil.copy2():
     9fe. are also affected.

   - bpo-44569(93): Added the ‘StackSummary.format_frame()’ function in
     *note traceback: e7.  This allows users to customize the way
     individual lines are formatted in tracebacks without
     re-implementing logic to handle recursive tracebacks.

   - bpo-44566(94): handle StopIteration subclass raised from
     @contextlib.contextmanager generator

   - bpo-44558(95): Make the implementation consistency of *note
     indexOf(): 880. between C and Python versions.  Patch by Donghee
     Na.

   - bpo-41249(96): Fixes ‘TypedDict’ to work with
     ‘typing.get_type_hints()’ and postponed evaluation of annotations
     across modules.

   - bpo-44554(97): Refactor argument processing in ‘pdb.main()’ to
     simplify detection of errors in input loading and clarify behavior
     around module or script invocation.

   - bpo-34798(98): Break up paragraph about *note pprint.PrettyPrinter:
     f22. construction parameters to make it easier to read.

   - bpo-44539(99): Added support for recognizing JPEG files without
     JFIF or Exif markers.

   - bpo-44461(100): Fix bug with *note pdb: 94.'s handling of import
     error due to a package which does not have a ‘__main__’ module

   - bpo-43625(101): Fix a bug in the detection of CSV file headers by
     *note csv.Sniffer.has_header(): 17a5. and improve documentation of
     same.

   - bpo-44516(102): Update vendored pip to 21.1.3

   - bpo-42892(103): Fixed an exception thrown while parsing a malformed
     multipart email by *note email.message.EmailMessage: 260.

   - bpo-44468(104): *note typing.get_type_hints(): 657. now finds
     annotations in classes and base classes with unexpected
     ‘__module__’.  Previously, it skipped those MRO elements.

   - bpo-44491(105): Allow clearing the *note sqlite3: ba. authorizer
     callback by passing *note None: 61b. to *note set_authorizer():
     28b.  Patch by Erlend E. Aasland.

   - bpo-43977(106): Set the proper *note Py_TPFLAGS_MAPPING: 17a6. and
     *note Py_TPFLAGS_SEQUENCE: 17a7. flags for subclasses created
     before a parent has been registered as a *note
     collections.abc.Mapping: 86f. or *note collections.abc.Sequence:
     115c.

   - bpo-44482(107): Fix very unlikely resource leak in *note glob: 5a.
     in alternate Python implementations.

   - bpo-44466(108): The *note faulthandler: 4e. module now detects if a
     fatal error occurs during a garbage collector collection.  Patch by
     Victor Stinner.

   - bpo-44471(109): A *note TypeError: 4dd. is now raised instead of an
     *note AttributeError: 2f6. in *note
     contextlib.ExitStack.enter_context(): 578. and *note
     contextlib.AsyncExitStack.enter_async_context(): 57b. for objects
     which do not support the *note context manager: 576. or *note
     asynchronous context manager: 579. protocols correspondingly.

   - bpo-44404(110): *note tkinter: d9.'s ‘after()’ method now supports
     callables without the ‘__name__’ attribute.

   - bpo-41546(111): Make *note pprint: 9c. (like the builtin ‘print’)
     not attempt to write to ‘stdout’ when it is ‘None’.

   - bpo-44458(112): ‘BUFFER_BLOCK_SIZE’ is now declared static, to
     avoid linking collisions when bz2, lmza or zlib are statically
     linked.

   - bpo-44464(113): Remove exception for flake8 in deprecated
     importlib.metadata interfaces.  Sync with importlib_metadata 4.6.

   - bpo-44446(114): Take into account that ‘lineno’ might be ‘None’ in
     *note traceback.FrameSummary: e28.

   - bpo-44439(115): Fix in ‘bz2.BZ2File.write()’ /
     ‘lzma.LZMAFile.write()’ methods, when the input data is an object
     that supports the buffer protocol, the file length may be wrong.

   - bpo-44434(116): _thread.start_new_thread() no longer calls
     PyThread_exit_thread() explicitly at the thread exit, the call was
     redundant.  On Linux with the glibc, pthread_exit() aborts the
     whole process if dlopen() fails to open libgcc_s.so file (ex:
     EMFILE error).  Patch by Victor Stinner.

   - bpo-42972(117): The _thread.RLock type now fully implement the GC
     protocol: add a traverse function and the *note Py_TPFLAGS_HAVE_GC:
     720. flag.  Patch by Victor Stinner.

   - bpo-44422(118): The *note threading.enumerate(): 17a8. function now
     uses a reentrant lock to prevent a hang on reentrant call.  Patch
     by Victor Stinner.

   - bpo-38291(119): Importing typing.io or typing.re now prints a
     ‘DeprecationWarning’.

   - bpo-37880(120): argparse actions store_const and append_const each
     receive a default value of ‘None’ when the ‘const’ kwarg is not
     provided.  Previously, this raised a *note TypeError: 4dd.

   - bpo-44389(121): Fix deprecation of *note ssl.OP_NO_TLSv1_3: 17a9.

   - bpo-27827(122): ‘pathlib.PureWindowsPath.is_reserved()’ now
     identifies a greater range of reserved filenames, including those
     with trailing spaces or colons.

   - bpo-44395(123): Fix ‘as_string()’ to pass unixfrom properly.  Patch
     by Donghee Na.

   - bpo-34266(124): Handle exceptions from parsing the arg of *note
     pdb: 94.'s run/restart command.

   - bpo-44362(125): Improve *note ssl: bb. module's deprecation
     messages, error reporting, and documentation for deprecations.

   - bpo-44342(126): [Enum] Change pickling from by-value to by-name.

   - bpo-44356(127): [Enum] Allow multiple data-type mixins if they are
     all the same.

   - bpo-44351(128): Restore back ‘parse_makefile()’ in
     ‘distutils.sysconfig’ because it behaves differently than the
     similar implementation in *note sysconfig: c5.

   - bpo-35800(129): ‘smtpd.MailmanProxy’ is now removed as it is
     unusable without an external module, ‘mailman’.  Patch by Donghee
     Na.

   - bpo-44357(130): Added a function that returns cube root of the
     given number *note math.cbrt(): 607.

   - bpo-44339(131): Change ‘math.pow(±0.0, -math.inf)’ to return ‘inf’
     instead of raising ‘ValueError’.  This brings the special-case
     handling of ‘math.pow’ into compliance with the IEEE 754 standard.

   - bpo-44242(132): Remove missing flag check from Enum creation and
     move into a ‘verify’ decorator.

   - bpo-44246(133): In ‘importlib.metadata’, restore compatibility in
     the result from ‘Distribution.entry_points’ (‘EntryPoints’) to
     honor expectations in older implementations and issuing deprecation
     warnings for these cases: A. ‘EntryPoints’ objects are once again
     mutable, allowing for ‘sort()’ and other list-based mutation
     operations.  Avoid deprecation warnings by casting to a mutable
     sequence (e.g.  ‘list(dist.entry_points).sort()’).  B.
     ‘EntryPoints’ results once again allow for access by index.  To
     avoid deprecation warnings, cast the result to a Sequence first
     (e.g.  ‘tuple(dist.entry_points)[0]’).

   - bpo-44246(134): In importlib.metadata.entry_points, de-duplication
     of distributions no longer requires loading the full metadata for
     PathDistribution objects, improving entry point loading performance
     by ~10x.

   - bpo-43858(135): Added a function that returns a copy of a dict of
     logging levels: *note logging.getLevelNamesMapping(): 5ff.

   - bpo-44260(136): The *note random.Random: 17aa. constructor no
     longer reads system entropy without need.

   - bpo-44254(137): On Mac, give turtledemo button text a color that
     works on both light or dark background.  Programmers cannot control
     the latter.

   - bpo-44258(138): Support PEP 515 for Fraction's initialization from
     string.

   - bpo-44235(139): Remove deprecated functions in the *note gettext:
     59.  Patch by Donghee Na.

   - bpo-38693(140): Prefer f-strings to ‘.format’ in
     importlib.resources.

   - bpo-33693(141): Importlib.metadata now prefers f-strings to
     .format.

   - bpo-44241(142): Incorporate minor tweaks from importlib_metadata
     4.1: SimplePath protocol, support for Metadata 2.2.

   - bpo-43216(143): Remove the ‘@asyncio.coroutine’ *note decorator:
     6d5. enabling legacy generator-based coroutines to be compatible
     with async/await code; remove ‘asyncio.coroutines.CoroWrapper’ used
     for wrapping legacy coroutine objects in the debug mode.  The
     decorator has been deprecated since Python 3.8 and the removal was
     initially scheduled for Python 3.10.  Patch by Illia Volochii.

   - bpo-44210(144): Make importlib.metadata._meta.PackageMetadata
     public.

   - bpo-43643(145): Declare readers.MultiplexedPath.name as a property
     per the spec.

   - bpo-27334(146): The *note sqlite3: ba. context manager now performs
     a rollback (thus releasing the database lock) if commit failed.
     Patch by Luca Citi and Erlend E. Aasland.

   - bpo-4928(147): Documented existing behavior on POSIX:
     NamedTemporaryFiles are not deleted when creating process is killed
     with SIGKILL

   - bpo-44154(148): Optimize *note fractions.Fraction: 1c7. pickling
     for large components.

   - bpo-33433(149): For IPv4 mapped IPv6 addresses ( RFC 4291(150)
     Section 2.5.5.2), the *note ipaddress.IPv6Address.is_private: 153e.
     check is deferred to the mapped IPv4 address.  This solves a bug
     where public mapped IPv4 addresses were considered private by the
     IPv6 check.

   - bpo-44150(151): Add optional 'weights' argument to
     statistics.fmean().

   - bpo-44142(152): *note ast.unparse(): 88a. will now drop the
     redundant parentheses when tuples used as assignment targets (e.g
     in for loops).

   - bpo-44145(153): *note hmac: 60. computations were not releasing the
     GIL while calling the OpenSSL ‘HMAC_Update’ C API (a new feature in
     3.9).  This unintentionally prevented parallel computation as other
     *note hashlib: 5e. algorithms support.

   - bpo-44095(154): *note zipfile.Path: 66b. now supports *note
     zipfile.Path.stem: 66c, *note zipfile.Path.suffixes: 66e, and *note
     zipfile.Path.suffix: 66d. attributes.

   - bpo-44077(155): It's now possible to receive the type of service
     (ToS), a.k.a.  differentiated services (DS), a.k.a.  differentiated
     services code point (DSCP) and explicit congestion notification
     (ECN) IP header fields with ‘socket.IP_RECVTOS’.

   - bpo-37788(156): Fix a reference leak when a Thread object is never
     joined.

   - bpo-38908(157): Subclasses of ‘typing.Protocol’ which only have
     data variables declared will now raise a ‘TypeError’ when checked
     with ‘isinstance’ unless they are decorated with
     ‘runtime_checkable()’.  Previously, these checks passed silently.
     Patch provided by Yurii Karabas.

   - bpo-44098(158): ‘typing.ParamSpec’ will no longer be found in the
     ‘__parameters__’ of most *note typing: ed. generics except in valid
     use locations specified by PEP 612(159).  This prevents incorrect
     usage like ‘typing.List[P][int]’.  This change means incorrect
     usage which may have passed silently in 3.10 beta 1 and earlier
     will now error.

   - bpo-44089(160): Allow subclassing ‘csv.Error’ in 3.10 (it was
     allowed in 3.9 and earlier but was disallowed in early versions of
     3.10).

   - bpo-44081(161): *note ast.unparse(): 88a. now doesn't use redundant
     spaces to separate ‘lambda’ and the ‘:’ if there are no parameters.

   - bpo-44061(162): Fix regression in previous release when calling
     *note pkgutil.iter_modules(): cf1. with a list of *note
     pathlib.Path: 20e. objects

   - bpo-44059(163): Register the SerenityOS Browser in the *note
     webbrowser: fd. module.

   - bpo-36515(164): The *note hashlib: 5e. module no longer does
     unaligned memory accesses when compiled for ARM platforms.

   - bpo-40465(165): Remove random module features deprecated in Python
     3.9.

   - bpo-44018(166): random.seed() no longer mutates bytearray inputs.

   - bpo-38352(167): Add ‘IO’, ‘BinaryIO’, ‘TextIO’, ‘Match’, and
     ‘Pattern’ to ‘typing.__all__’.  Patch by Jelle Zijlstra.

   - bpo-44002(168): *note urllib.parse: f3. now uses
     ‘functool.lru_cache()’ for its internal URL splitting and quoting
     caches instead of rolling its own like its the '90s.

     The undocumented internal *note urllib.parse: f3. ‘Quoted’ class
     API is now deprecated, for removal in 3.14.

   - bpo-43972(169): When *note http.server.SimpleHTTPRequestHandler:
     ae7. sends a ‘301 (Moved Permanently)’ for a directory path not
     ending with ‘/’, add a ‘Content-Length: 0’ header.  This improves
     the behavior for certain clients.

   - bpo-28528(170): Fix a bug in *note pdb: 94. where ‘checkline()’
     raises *note AttributeError: 2f6. if it is called after ‘reset()’.

   - bpo-43853(171): Improved string handling for *note sqlite3: ba.
     user-defined functions and aggregates:

        * It is now possible to pass strings with embedded null
          characters to UDFs

        * Conversion failures now correctly raise *note MemoryError:
          15bc.

     Patch by Erlend E. Aasland.

   - bpo-43666(172): AIX: ‘Lib/_aix_support.get_platform()’ may fail in
     an AIX WPAR. The fileset bos.rte appears to have a builddate in
     both LPAR and WPAR so this fileset is queried rather than bos.mp64.
     To prevent a similar situation (no builddate in ODM) a value (9988)
     sufficient for completing a build is provided.  Patch by M Felt.

   - bpo-43650(173): Fix *note MemoryError: 15bc. in *note
     shutil.unpack_archive(): 412. which fails inside
     ‘shutil._unpack_zipfile()’ on large files.  Patch by Igor
     Bolshakov.

   - bpo-43612(174): *note zlib.compress(): 5e5. now accepts a wbits
     parameter which allows users to compress data as a raw deflate
     block without zlib headers and trailers in one go.  Previously this
     required instantiating a ‘zlib.compressobj’.  It also provides a
     faster alternative to ‘gzip.compress’ when wbits=31 is used.

   - bpo-43392(175): ‘importlib._bootstrap._find_and_load()’ now
     implements a two-step check to avoid locking when modules have been
     already imported and are ready.  This improves performance of
     repeated calls to *note importlib.import_module(): 4bc. and *note
     importlib.__import__(): 100e.

   - bpo-43318(176): Fix a bug where *note pdb: 94. does not always echo
     cleared breakpoints.

   - bpo-43234(177): Prohibit passing non-*note
     concurrent.futures.ThreadPoolExecutor: 6e6. executors to
     ‘loop.set_default_executor()’ following a deprecation in Python
     3.8.  Patch by Illia Volochii.

   - bpo-43232(178): Prohibit previously deprecated potentially
     disruptive operations on ‘asyncio.trsock.TransportSocket’.  Patch
     by Illia Volochii.

   - bpo-30077(179): Added support for Apple's aifc/sowt
     pseudo-compression

   - bpo-42971(180): Add definition of ‘errno.EQFULL’ for platforms that
     define this constant (such as macOS).

   - bpo-43086(181): Added a new optional ‘strict_mode’ parameter to
     'binascii.a2b_base64'.  When ‘scrict_mode’ is set to ‘True’, the
     'a2b_base64' function will accept only valid base64 content.  More
     details about what "valid base64 content" is, can be found in the
     function's documentation.

   - bpo-43024(182): Improve the help signature of *note
     traceback.print_exception(): 7f3, *note
     traceback.format_exception(): 7f1. and *note
     traceback.format_exception_only(): 7f2.

   - bpo-33809(183): Add the *note traceback.TracebackException.print():
     649. method which prints the formatted exception information.

   - bpo-42862(184): *note sqlite3: ba. now utilizes *note
     functools.lru_cache(): 993. to implement the connection statement
     cache.  As a small optimisation, the default statement cache size
     has been increased from 100 to 128.  Patch by Erlend E. Aasland.

   - bpo-41818(185): Soumendra Ganguly: add termios.tcgetwinsize(),
     termios.tcsetwinsize().

   - bpo-40497(186): *note subprocess.check_output(): f64. now raises
     *note ValueError: 1e7. when the invalid keyword argument 'check' is
     passed by user code.  Previously such use would fail later with a
     *note TypeError: 4dd.  Patch by Rémi Lapeyre.

   - bpo-37449(187): ‘ensurepip’ now uses ‘importlib.resources.files()’
     traversable APIs

   - bpo-40956(188): Use Argument Clinic in *note sqlite3: ba.  Patches
     by Erlend E. Aasland.

   - bpo-41730(189): ‘DeprecationWarning’ is now raised when importing
     ‘tkinter.tix’, which has been deprecated in documentation since
     Python 3.6.

   - bpo-20684(190): Remove unused ‘_signature_get_bound_param’ function
     from *note inspect: 72. - by Anthony Sottile.

   - bpo-41402(191): Fix *note email.message.EmailMessage.set_content():
     17ab. when called with binary data and ‘7bit’ content transfer
     encoding.

   - bpo-32695(192): The 'compresslevel' and 'preset' keyword arguments
     of *note tarfile.open(): e19. are now both documented and tested.

   - bpo-41137(193): Use utf-8 encoding while reading .pdbrc files.
     Patch by Srinivas Reddy Thatiparthy

   - bpo-24391(194): Improved reprs of *note threading: d6.
     synchronization objects: *note Semaphore: 10ef, *note
     BoundedSemaphore: 10f0, *note Event: 10f1. and *note Barrier: 117b.

   - bpo-5846(195): Deprecated the following *note unittest: ef.
     functions, scheduled for removal in Python 3.13:

        * ‘findTestCases()’

        * ‘makeSuite()’

        * ‘getTestCaseNames()’

     Use *note TestLoader: 270. methods instead:

        * *note unittest.TestLoader.loadTestsFromModule(): 271.

        * *note unittest.TestLoader.loadTestsFromTestCase(): 272.

        * *note unittest.TestLoader.getTestCaseNames(): 273.

     Patch by Erlend E. Aasland.

   - bpo-40563(196): Support pathlike objects on dbm/shelve.  Patch by
     Hakan Çelik and Henry-Joseph Audéoud.

   - bpo-34990(197): Fixed a Y2k38 bug in the compileall module where it
     would fail to compile files with a modification time after the year
     2038.

   - bpo-39549(198): Whereas the code for reprlib.Repr had previously
     used a hardcoded string value of '...', this PR updates it to use
     of a “fillvalue” attribute, whose value defaults to '...'  and can
     be reset in either individual reprlib.Repr instances or in
     subclasses thereof.

   - bpo-37022(199): *note pdb: 94. now displays exceptions from
     ‘repr()’ with its ‘p’ and ‘pp’ commands.

   - bpo-38840(200): Fix ‘test___all__’ on platforms lacking a shared
     memory implementation.

   - bpo-39359(201): Add one missing check that the password is a bytes
     object for an encrypted zipfile.

   - bpo-38741(202): *note configparser: 1b.: using ']' inside a section
     header will no longer cut the section name short at the ']'

   - bpo-38415(203): Added missing behavior to *note
     contextlib.asynccontextmanager(): ace. to match *note
     contextlib.contextmanager(): 119a. so decorated functions can
     themselves be decorators.

   - bpo-30256(204): Pass multiprocessing BaseProxy argument
     ‘manager_owned’ through AutoProxy.

   - bpo-27513(205): *note email.utils.getaddresses(): 1c4. now accepts
     *note email.header.Header: 17ac. objects along with string values.
     Patch by Zackery Spytz.

   - bpo-16379(206): Add SQLite error code and name to *note sqlite3:
     ba. exceptions.  Patch by Aviv Palivoda, Daniel Shahaf, and Erlend
     E. Aasland.

   - bpo-26228(207): pty.spawn no longer hangs on FreeBSD, macOS, and
     Solaris.

   - bpo-33349(208): lib2to3 now recognizes async generators everywhere.

   - bpo-29298(209): Fix ‘TypeError’ when required subparsers without
     ‘dest’ do not receive arguments.  Patch by Anthony Sottile.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45371

   (2) https://bugs.python.org/issue?@action=redirect&bpo=45329

   (3) https://bugs.python.org/issue?@action=redirect&bpo=41710

   (4) https://bugs.python.org/issue?@action=redirect&bpo=1596321

   (5) https://bugs.python.org/issue?@action=redirect&bpo=45274

   (6) https://bugs.python.org/issue?@action=redirect&bpo=21302

   (7) https://bugs.python.org/issue?@action=redirect&bpo=21302

   (8) https://bugs.python.org/issue?@action=redirect&bpo=45238

   (9) https://bugs.python.org/issue?@action=redirect&bpo=36674

   (10) https://bugs.python.org/issue?@action=redirect&bpo=45235

   (11) https://bugs.python.org/issue?@action=redirect&bpo=45183

   (12) https://bugs.python.org/issue?@action=redirect&bpo=45234

   (13) https://bugs.python.org/issue?@action=redirect&bpo=45228

   (14) https://bugs.python.org/issue?@action=redirect&bpo=45225

   (15) https://bugs.python.org/issue?@action=redirect&bpo=42135

   (16) https://bugs.python.org/issue?@action=redirect&bpo=20524

   (17) https://bugs.python.org/issue?@action=redirect&bpo=45168

   (18) https://bugs.python.org/issue?@action=redirect&bpo=21302

   (19) https://bugs.python.org/issue?@action=redirect&bpo=45173

   (20) https://bugs.python.org/issue?@action=redirect&bpo=44987

   (21) https://bugs.python.org/issue?@action=redirect&bpo=35474

   (22) https://bugs.python.org/issue?@action=redirect&bpo=45166

   (23) https://bugs.python.org/issue?@action=redirect&bpo=45162

   (24) https://bugs.python.org/issue?@action=redirect&bpo=38371

   (25) https://bugs.python.org/issue?@action=redirect&bpo=20499

   (26) https://bugs.python.org/issue?@action=redirect&bpo=45132

   (27) https://bugs.python.org/issue?@action=redirect&bpo=45129

   (28) https://bugs.python.org/issue?@action=redirect&bpo=45124

   (29) https://bugs.python.org/issue?@action=redirect&bpo=30856

   (30) https://bugs.python.org/issue?@action=redirect&bpo=45034

   (31) https://bugs.python.org/issue?@action=redirect&bpo=25894

   (32) https://bugs.python.org/issue?@action=redirect&bpo=45081

   (33) https://bugs.python.org/issue?@action=redirect&bpo=45085

   (34) https://bugs.python.org/issue?@action=redirect&bpo=40360

   (35) https://peps.python.org/pep-0617/

   (36) https://bugs.python.org/issue?@action=redirect&bpo=45075

   (37) https://bugs.python.org/issue?@action=redirect&bpo=31299

   (38) https://bugs.python.org/issue?@action=redirect&bpo=41620

   (39) https://bugs.python.org/issue?@action=redirect&bpo=45021

   (40) https://bugs.python.org/issue?@action=redirect&bpo=43913

   (41) https://bugs.python.org/issue?@action=redirect&bpo=45030

   (42) https://bugs.python.org/issue?@action=redirect&bpo=45001

   (43) https://bugs.python.org/issue?@action=redirect&bpo=45010

   (44) https://bugs.python.org/issue?@action=redirect&bpo=39218

   (45) https://bugs.python.org/issue?@action=redirect&bpo=43613

   (46) https://bugs.python.org/issue?@action=redirect&bpo=37596

   (47) https://bugs.python.org/issue?@action=redirect&bpo=44019

   (48) https://bugs.python.org/issue?@action=redirect&bpo=42255

   (49) https://bugs.python.org/issue?@action=redirect&bpo=44955

   (50) https://bugs.python.org/issue?@action=redirect&bpo=39039

   (51) https://bugs.python.org/issue?@action=redirect&bpo=44935

   (52) https://bugs.python.org/issue?@action=redirect&bpo=44911

   (53) https://bugs.python.org/issue?@action=redirect&bpo=41322

   (54) https://bugs.python.org/issue?@action=redirect&bpo=44524

   (55) https://bugs.python.org/issue?@action=redirect&bpo=38956

   (56) https://bugs.python.org/issue?@action=redirect&bpo=44860

   (57) https://bugs.python.org/issue?@action=redirect&bpo=44859

   (58) https://bugs.python.org/issue?@action=redirect&bpo=44581

   (59) https://bugs.python.org/issue?@action=redirect&bpo=44849

   (60) https://bugs.python.org/issue?@action=redirect&bpo=44605

   (61) https://bugs.python.org/issue?@action=redirect&bpo=44524

   (62) https://bugs.python.org/issue?@action=redirect&bpo=44839

   (63) https://bugs.python.org/issue?@action=redirect&bpo=44822

   (64) https://bugs.python.org/issue?@action=redirect&bpo=44801

   (65) https://bugs.python.org/issue?@action=redirect&bpo=44806

   (66) https://bugs.python.org/issue?@action=redirect&bpo=27275

   (67) https://bugs.python.org/issue?@action=redirect&bpo=44793

   (68) https://bugs.python.org/issue?@action=redirect&bpo=44784

   (69) https://bugs.python.org/issue?@action=redirect&bpo=44667

   (70) https://bugs.python.org/issue?@action=redirect&bpo=44771

   (71) https://bugs.python.org/issue?@action=redirect&bpo=44752

   (72) https://bugs.python.org/issue?@action=redirect&bpo=44747

   (73) https://bugs.python.org/issue?@action=redirect&bpo=42378

   (74) https://bugs.python.org/issue?@action=redirect&bpo=44720

   (75) https://bugs.python.org/issue?@action=redirect&bpo=44704

   (76) https://bugs.python.org/issue?@action=redirect&bpo=44666

   (77) https://bugs.python.org/issue?@action=redirect&bpo=44688

   (78) https://bugs.python.org/issue?@action=redirect&bpo=44690

   (79) https://bugs.python.org/issue?@action=redirect&bpo=42854

   (80) https://bugs.python.org/issue?@action=redirect&bpo=44686

   (81) https://bugs.python.org/issue?@action=redirect&bpo=44353

   (82) https://bugs.python.org/issue?@action=redirect&bpo=44682

   (83) https://bugs.python.org/issue?@action=redirect&bpo=44353

   (84) https://bugs.python.org/issue?@action=redirect&bpo=44678

   (85) https://bugs.python.org/issue?@action=redirect&bpo=44524

   (86) https://bugs.python.org/issue?@action=redirect&bpo=40897

   (87) https://bugs.python.org/issue?@action=redirect&bpo=44638

   (88) https://bugs.python.org/issue?@action=redirect&bpo=44648

   (89) https://bugs.python.org/issue?@action=redirect&bpo=44608

   (90) https://bugs.python.org/issue?@action=redirect&bpo=44594

   (91) https://bugs.python.org/issue?@action=redirect&bpo=42799

   (92) https://bugs.python.org/issue?@action=redirect&bpo=41928

   (93) https://bugs.python.org/issue?@action=redirect&bpo=44569

   (94) https://bugs.python.org/issue?@action=redirect&bpo=44566

   (95) https://bugs.python.org/issue?@action=redirect&bpo=44558

   (96) https://bugs.python.org/issue?@action=redirect&bpo=41249

   (97) https://bugs.python.org/issue?@action=redirect&bpo=44554

   (98) https://bugs.python.org/issue?@action=redirect&bpo=34798

   (99) https://bugs.python.org/issue?@action=redirect&bpo=44539

   (100) https://bugs.python.org/issue?@action=redirect&bpo=44461

   (101) https://bugs.python.org/issue?@action=redirect&bpo=43625

   (102) https://bugs.python.org/issue?@action=redirect&bpo=44516

   (103) https://bugs.python.org/issue?@action=redirect&bpo=42892

   (104) https://bugs.python.org/issue?@action=redirect&bpo=44468

   (105) https://bugs.python.org/issue?@action=redirect&bpo=44491

   (106) https://bugs.python.org/issue?@action=redirect&bpo=43977

   (107) https://bugs.python.org/issue?@action=redirect&bpo=44482

   (108) https://bugs.python.org/issue?@action=redirect&bpo=44466

   (109) https://bugs.python.org/issue?@action=redirect&bpo=44471

   (110) https://bugs.python.org/issue?@action=redirect&bpo=44404

   (111) https://bugs.python.org/issue?@action=redirect&bpo=41546

   (112) https://bugs.python.org/issue?@action=redirect&bpo=44458

   (113) https://bugs.python.org/issue?@action=redirect&bpo=44464

   (114) https://bugs.python.org/issue?@action=redirect&bpo=44446

   (115) https://bugs.python.org/issue?@action=redirect&bpo=44439

   (116) https://bugs.python.org/issue?@action=redirect&bpo=44434

   (117) https://bugs.python.org/issue?@action=redirect&bpo=42972

   (118) https://bugs.python.org/issue?@action=redirect&bpo=44422

   (119) https://bugs.python.org/issue?@action=redirect&bpo=38291

   (120) https://bugs.python.org/issue?@action=redirect&bpo=37880

   (121) https://bugs.python.org/issue?@action=redirect&bpo=44389

   (122) https://bugs.python.org/issue?@action=redirect&bpo=27827

   (123) https://bugs.python.org/issue?@action=redirect&bpo=44395

   (124) https://bugs.python.org/issue?@action=redirect&bpo=34266

   (125) https://bugs.python.org/issue?@action=redirect&bpo=44362

   (126) https://bugs.python.org/issue?@action=redirect&bpo=44342

   (127) https://bugs.python.org/issue?@action=redirect&bpo=44356

   (128) https://bugs.python.org/issue?@action=redirect&bpo=44351

   (129) https://bugs.python.org/issue?@action=redirect&bpo=35800

   (130) https://bugs.python.org/issue?@action=redirect&bpo=44357

   (131) https://bugs.python.org/issue?@action=redirect&bpo=44339

   (132) https://bugs.python.org/issue?@action=redirect&bpo=44242

   (133) https://bugs.python.org/issue?@action=redirect&bpo=44246

   (134) https://bugs.python.org/issue?@action=redirect&bpo=44246

   (135) https://bugs.python.org/issue?@action=redirect&bpo=43858

   (136) https://bugs.python.org/issue?@action=redirect&bpo=44260

   (137) https://bugs.python.org/issue?@action=redirect&bpo=44254

   (138) https://bugs.python.org/issue?@action=redirect&bpo=44258

   (139) https://bugs.python.org/issue?@action=redirect&bpo=44235

   (140) https://bugs.python.org/issue?@action=redirect&bpo=38693

   (141) https://bugs.python.org/issue?@action=redirect&bpo=33693

   (142) https://bugs.python.org/issue?@action=redirect&bpo=44241

   (143) https://bugs.python.org/issue?@action=redirect&bpo=43216

   (144) https://bugs.python.org/issue?@action=redirect&bpo=44210

   (145) https://bugs.python.org/issue?@action=redirect&bpo=43643

   (146) https://bugs.python.org/issue?@action=redirect&bpo=27334

   (147) https://bugs.python.org/issue?@action=redirect&bpo=4928

   (148) https://bugs.python.org/issue?@action=redirect&bpo=44154

   (149) https://bugs.python.org/issue?@action=redirect&bpo=33433

   (150) https://datatracker.ietf.org/doc/html/rfc4291.html

   (151) https://bugs.python.org/issue?@action=redirect&bpo=44150

   (152) https://bugs.python.org/issue?@action=redirect&bpo=44142

   (153) https://bugs.python.org/issue?@action=redirect&bpo=44145

   (154) https://bugs.python.org/issue?@action=redirect&bpo=44095

   (155) https://bugs.python.org/issue?@action=redirect&bpo=44077

   (156) https://bugs.python.org/issue?@action=redirect&bpo=37788

   (157) https://bugs.python.org/issue?@action=redirect&bpo=38908

   (158) https://bugs.python.org/issue?@action=redirect&bpo=44098

   (159) https://peps.python.org/pep-0612/

   (160) https://bugs.python.org/issue?@action=redirect&bpo=44089

   (161) https://bugs.python.org/issue?@action=redirect&bpo=44081

   (162) https://bugs.python.org/issue?@action=redirect&bpo=44061

   (163) https://bugs.python.org/issue?@action=redirect&bpo=44059

   (164) https://bugs.python.org/issue?@action=redirect&bpo=36515

   (165) https://bugs.python.org/issue?@action=redirect&bpo=40465

   (166) https://bugs.python.org/issue?@action=redirect&bpo=44018

   (167) https://bugs.python.org/issue?@action=redirect&bpo=38352

   (168) https://bugs.python.org/issue?@action=redirect&bpo=44002

   (169) https://bugs.python.org/issue?@action=redirect&bpo=43972

   (170) https://bugs.python.org/issue?@action=redirect&bpo=28528

   (171) https://bugs.python.org/issue?@action=redirect&bpo=43853

   (172) https://bugs.python.org/issue?@action=redirect&bpo=43666

   (173) https://bugs.python.org/issue?@action=redirect&bpo=43650

   (174) https://bugs.python.org/issue?@action=redirect&bpo=43612

   (175) https://bugs.python.org/issue?@action=redirect&bpo=43392

   (176) https://bugs.python.org/issue?@action=redirect&bpo=43318

   (177) https://bugs.python.org/issue?@action=redirect&bpo=43234

   (178) https://bugs.python.org/issue?@action=redirect&bpo=43232

   (179) https://bugs.python.org/issue?@action=redirect&bpo=30077

   (180) https://bugs.python.org/issue?@action=redirect&bpo=42971

   (181) https://bugs.python.org/issue?@action=redirect&bpo=43086

   (182) https://bugs.python.org/issue?@action=redirect&bpo=43024

   (183) https://bugs.python.org/issue?@action=redirect&bpo=33809

   (184) https://bugs.python.org/issue?@action=redirect&bpo=42862

   (185) https://bugs.python.org/issue?@action=redirect&bpo=41818

   (186) https://bugs.python.org/issue?@action=redirect&bpo=40497

   (187) https://bugs.python.org/issue?@action=redirect&bpo=37449

   (188) https://bugs.python.org/issue?@action=redirect&bpo=40956

   (189) https://bugs.python.org/issue?@action=redirect&bpo=41730

   (190) https://bugs.python.org/issue?@action=redirect&bpo=20684

   (191) https://bugs.python.org/issue?@action=redirect&bpo=41402

   (192) https://bugs.python.org/issue?@action=redirect&bpo=32695

   (193) https://bugs.python.org/issue?@action=redirect&bpo=41137

   (194) https://bugs.python.org/issue?@action=redirect&bpo=24391

   (195) https://bugs.python.org/issue?@action=redirect&bpo=5846

   (196) https://bugs.python.org/issue?@action=redirect&bpo=40563

   (197) https://bugs.python.org/issue?@action=redirect&bpo=34990

   (198) https://bugs.python.org/issue?@action=redirect&bpo=39549

   (199) https://bugs.python.org/issue?@action=redirect&bpo=37022

   (200) https://bugs.python.org/issue?@action=redirect&bpo=38840

   (201) https://bugs.python.org/issue?@action=redirect&bpo=39359

   (202) https://bugs.python.org/issue?@action=redirect&bpo=38741

   (203) https://bugs.python.org/issue?@action=redirect&bpo=38415

   (204) https://bugs.python.org/issue?@action=redirect&bpo=30256

   (205) https://bugs.python.org/issue?@action=redirect&bpo=27513

   (206) https://bugs.python.org/issue?@action=redirect&bpo=16379

   (207) https://bugs.python.org/issue?@action=redirect&bpo=26228

   (208) https://bugs.python.org/issue?@action=redirect&bpo=33349

   (209) https://bugs.python.org/issue?@action=redirect&bpo=29298


File: python.info,  Node: Documentation<23>,  Next: Tests<26>,  Prev: Library<28>,  Up: Python 3 11 0 alpha 1

1.23.29.4 Documentation
.......................

   - bpo-45216(1): Remove extra documentation listing methods in
     ‘difflib’.  It was rendering twice in pydoc and was outdated in
     some places.

   - bpo-45024(2): *note collections.abc: 17. documentation has been
     expanded to explicitly cover how instance and subclass checks work,
     with additional doctest examples and an exhaustive list of ABCs
     which test membership purely by presence of the right *note special
     method: 17ae.s.  Patch by Raymond Hettinger.

   - bpo-44957(3): Promote PEP 604 union syntax by using it where
     possible.  Also, mention ‘X | Y’ more prominently in section about
     ‘Union’ and mention ‘X | None’ at all in section about ‘Optional’.

   - bpo-16580(4): Added code equivalents for the *note int.to_bytes():
     1792. and *note int.from_bytes(): 1754. methods, as well as tests
     ensuring that these code equivalents are valid.

   - bpo-44903(5): Removed the ‘othergui.rst’ file, any references to
     it, and the list of GUI frameworks in the FAQ. In their place I've
     added links to the Python Wiki page on GUI frameworks(6).

   - bpo-33479(7): Tkinter documentation has been greatly expanded with
     new "Architecture" and "Threading model" sections.

   - bpo-36700(8): *note base64: a. RFC references were updated to point
     to RFC 4648(9); a section was added to point users to the new
     "security considerations" section of the RFC.

   - bpo-44740(10): Replaced occurrences of uppercase "Web" and
     "Internet" with lowercase versions per the 2016 revised Associated
     Press Style Book.

   - bpo-44693(11): Update the definition of __future__ in the glossary
     by replacing the confusing word "pseudo-module" with a more
     accurate description.

   - bpo-35183(12): Add typical examples to os.path.splitext docs

   - bpo-30511(13): Clarify that *note shutil.make_archive(): 45a. is
     not thread-safe due to reliance on changing the current working
     directory.

   - bpo-44561(14): Update of three expired hyperlinks in
     Doc/distributing/index.rst: "Project structure", "Building and
     packaging the project", and "Uploading the project to the Python
     Packaging Index".

   - bpo-44651(15): Delete entry "coercion" in Doc/glossary.rst for its
     outdated definition.

   - bpo-42958(16): Updated the docstring and docs of *note
     filecmp.cmp(): 1554. to be more accurate and less confusing
     especially in respect to 'shallow' arg.

   - bpo-44631(17): Refactored the ‘repr()’ code of the ‘_Environ’ (os
     module).

   - bpo-44613(18): importlib.metadata is no longer provisional.

   - bpo-44558(19): Match the docstring and python implementation of
     *note countOf(): 881. to the behavior of its c implementation.

   - bpo-44544(20): List all kwargs for *note textwrap.wrap(): 1432,
     *note textwrap.fill(): 1431, and *note textwrap.shorten(): f73.
     Now, there are nav links to attributes of ‘TextWrap’, which makes
     navigation much easier while minimizing duplication in the
     documentation.

   - bpo-38062(21): Clarify that atexit uses equality comparisons
     internally.

   - bpo-40620(22): Convert examples in tutorial controlflow.rst section
     4.3 to be interpreter-demo style.

   - bpo-43066(23): Added a warning to *note zipfile: 117. docs:
     filename arg with a leading slash may cause archive to be
     un-openable on Windows systems.

   - bpo-39452(24): Rewrote ‘Doc/library/__main__.rst’.  Broadened scope
     of the document to explicitly discuss and differentiate between
     ‘__main__.py’ in packages versus the ‘__name__ == '__main__'’
     expression (and the idioms that surround it).

   - bpo-13814(25): In the Design FAQ, answer "Why don't generators
     support the with statement?"

   - bpo-27752(26): Documentation of csv.Dialect is more descriptive.

   - bpo-44453(27): Fix documentation for the return type of *note
     sysconfig.get_path(): 12c2.

   - bpo-44392(28): Added a new section in the C API documentation for
     types used in type hinting.  Documented ‘Py_GenericAlias’ and
     ‘Py_GenericAliasType’.

   - bpo-38291(29): Mark ‘typing.io’ and ‘typing.re’ as deprecated since
     Python 3.8 in the documentation.  They were never properly
     supported by type checkers.

   - bpo-44322(30): Document that SyntaxError args have a details tuple
     and that details are adjusted for errors in f-string field
     replacement expressions.

   - bpo-42392(31): Document the deprecation and removal of the ‘loop’
     parameter for many functions and classes in *note asyncio: 8.

   - bpo-44195(32): Corrected references to ‘TraversableResources’ in
     docs.  There is no ‘TraversableReader’.

   - bpo-41963(33): Document that ‘ConfigParser’ strips off comments
     when reading configuration files.

   - bpo-44072(34): Correct where in the numeric ABC hierarchy ‘**’
     support is added, i.e., in numbers.Complex, not numbers.Integral.

   - bpo-43558(35): Add the remark to *note dataclasses: 27.
     documentation that the ‘__init__()’ of any base class has to be
     called in ‘__post_init__()’, along with a code example.

   - bpo-44025(36): Clarify when '_' in match statements is a keyword,
     and when not.

   - bpo-41706(37): Fix docs about how methods like ‘__add__’ are
     invoked when evaluating operator expressions.

   - bpo-41621(38): Document that *note collections.defaultdict: 1155.
     parameter ‘default_factory’ defaults to ‘None’ and is
     positional-only.

   - bpo-41576(39): document BaseException in favor of bare except

   - bpo-21760(40): The description for __file__ fixed.  Patch by Furkan
     Onder

   - bpo-39498(41): Add a "Security Considerations" index which links to
     standard library modules that have explicitly documented security
     considerations.

   - bpo-33479(42): Remove the unqualified claim that tkinter is
     threadsafe.  It has not been true for several years and likely
     never was.  An explanation of what is true may be added later,
     after more discussion, and possibly after patching _tkinter.c,

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45216

   (2) https://bugs.python.org/issue?@action=redirect&bpo=45024

   (3) https://bugs.python.org/issue?@action=redirect&bpo=44957

   (4) https://bugs.python.org/issue?@action=redirect&bpo=16580

   (5) https://bugs.python.org/issue?@action=redirect&bpo=44903

   (6) https://wiki.python.org/moin/GuiProgramming

   (7) https://bugs.python.org/issue?@action=redirect&bpo=33479

   (8) https://bugs.python.org/issue?@action=redirect&bpo=36700

   (9) https://datatracker.ietf.org/doc/html/rfc4648.html

   (10) https://bugs.python.org/issue?@action=redirect&bpo=44740

   (11) https://bugs.python.org/issue?@action=redirect&bpo=44693

   (12) https://bugs.python.org/issue?@action=redirect&bpo=35183

   (13) https://bugs.python.org/issue?@action=redirect&bpo=30511

   (14) https://bugs.python.org/issue?@action=redirect&bpo=44561

   (15) https://bugs.python.org/issue?@action=redirect&bpo=44651

   (16) https://bugs.python.org/issue?@action=redirect&bpo=42958

   (17) https://bugs.python.org/issue?@action=redirect&bpo=44631

   (18) https://bugs.python.org/issue?@action=redirect&bpo=44613

   (19) https://bugs.python.org/issue?@action=redirect&bpo=44558

   (20) https://bugs.python.org/issue?@action=redirect&bpo=44544

   (21) https://bugs.python.org/issue?@action=redirect&bpo=38062

   (22) https://bugs.python.org/issue?@action=redirect&bpo=40620

   (23) https://bugs.python.org/issue?@action=redirect&bpo=43066

   (24) https://bugs.python.org/issue?@action=redirect&bpo=39452

   (25) https://bugs.python.org/issue?@action=redirect&bpo=13814

   (26) https://bugs.python.org/issue?@action=redirect&bpo=27752

   (27) https://bugs.python.org/issue?@action=redirect&bpo=44453

   (28) https://bugs.python.org/issue?@action=redirect&bpo=44392

   (29) https://bugs.python.org/issue?@action=redirect&bpo=38291

   (30) https://bugs.python.org/issue?@action=redirect&bpo=44322

   (31) https://bugs.python.org/issue?@action=redirect&bpo=42392

   (32) https://bugs.python.org/issue?@action=redirect&bpo=44195

   (33) https://bugs.python.org/issue?@action=redirect&bpo=41963

   (34) https://bugs.python.org/issue?@action=redirect&bpo=44072

   (35) https://bugs.python.org/issue?@action=redirect&bpo=43558

   (36) https://bugs.python.org/issue?@action=redirect&bpo=44025

   (37) https://bugs.python.org/issue?@action=redirect&bpo=41706

   (38) https://bugs.python.org/issue?@action=redirect&bpo=41621

   (39) https://bugs.python.org/issue?@action=redirect&bpo=41576

   (40) https://bugs.python.org/issue?@action=redirect&bpo=21760

   (41) https://bugs.python.org/issue?@action=redirect&bpo=39498

   (42) https://bugs.python.org/issue?@action=redirect&bpo=33479


File: python.info,  Node: Tests<26>,  Next: Build<28>,  Prev: Documentation<23>,  Up: Python 3 11 0 alpha 1

1.23.29.5 Tests
...............

   - bpo-40173(1): Fix *note
     test.support.import_helper.import_fresh_module(): 17b0.

   - bpo-45280(2): Add a test case for empty *note typing.NamedTuple:
     291.

   - bpo-45269(3): Cover case when invalid ‘markers’ type is supplied to
     ‘c_make_encoder’.

   - bpo-45128(4): Fix ‘test_multiprocessing_fork’ failure due to
     ‘test_logging’ and ‘sys.modules’ manipulation.

   - bpo-45209(5): Fix ‘UserWarning: resource_tracker’ warning in
     ‘_test_multiprocessing._TestSharedMemory.test_shared_memory_cleaned_after_process_termination’

   - bpo-45185(6): Enables ‘TestEnumerations’ test cases in ‘test_ssl’
     suite.

   - bpo-45195(7): Fix test_readline.test_nonascii(): sometimes, the
     newline character is not written at the end, so don't expect it in
     the output.  Patch by Victor Stinner.

   - bpo-45156(8): Fixes infinite loop on *note unittest.mock.seal():
     b48. of mocks created by ‘create_autospec()’.

   - bpo-45125(9): Improves pickling tests and docs of ‘SharedMemory’
     and ‘SharableList’ objects.

   - bpo-44860(10): Update ‘test_sysconfig.test_user_similar()’ for the
     posix_user scheme: ‘platlib’ doesn't use *note sys.platlibdir: 8dc.
     Patch by Victor Stinner.

   - bpo-45052(11):
     ‘WithProcessesTestSharedMemory.test_shared_memory_basics’ test was
     ignored, because ‘self.assertEqual(sms.size, sms2.size)’ line was
     failing.  It is now removed and test is unskipped.

     The main motivation for this line to be removed from the test is
     that the ‘size’ of ‘SharedMemory’ is not ever guaranteed to be the
     same.  It is decided by the platform.

   - bpo-44895(12): libregrtest now clears the type cache later to
     reduce the risk of false alarm when checking for reference leaks.
     Previously, the type cache was cleared too early and libregrtest
     raised a false alarm about reference leaks under very specific
     conditions.  Patch by Irit Katriel and Victor Stinner.

   - bpo-45042(13): Fixes that test classes decorated with
     ‘@hashlib_helper.requires_hashdigest’ were skipped all the time.

   - bpo-25130(14): Add calls of *note gc.collect(): 16b. in tests to
     support PyPy.

   - bpo-45011(15): Made tests relying on the ‘_asyncio’ C extension
     module optional to allow running on alternative Python
     implementations.  Patch by Serhiy Storchaka.

   - bpo-44949(16): Fix auto history tests of test_readline: sometimes,
     the newline character is not written at the end, so don't expect it
     in the output.

   - bpo-44891(17): Tests were added to clarify *note id(): 1390. is
     preserved when ‘obj * 1’ is used on *note str: 3f2. and *note
     bytes: 1a5. objects.  Patch by Nikita Sobolev.

   - bpo-44852(18): Add ability to wholesale silence DeprecationWarnings
     while running the regression test suite.

   - bpo-40928(19): Notify users running test_decimal regression tests
     on macOS of potential harmless "malloc can't allocate region"
     messages spewed by test_decimal.

   - bpo-44734(20): Fixed floating-point precision issue in turtle
     tests.

   - bpo-44708(21): Regression tests, when run with -w, are now
     re-running only the affected test methods instead of re-running the
     entire test file.

   - bpo-42095(22): Added interop tests for Apple plists: generate plist
     files with Python plistlib and parse with Apple plutil; and the
     other way round.

   - bpo-44647(23): Added a permanent Unicode-valued environment
     variable to regression tests to ensure they handle this use case in
     the future.  If your test environment breaks because of that,
     report a bug to us, and temporarily set
     PYTHONREGRTEST_UNICODE_GUARD=0 in your test environment.

   - bpo-44515(24): Adjust recently added contextlib tests to avoid
     assuming the use of a refcounted GC

   - bpo-44287(25): Fix asyncio test_popen() of test_windows_utils by
     using a longer timeout.  Use military grade battle-tested *note
     test.support.SHORT_TIMEOUT: 17b1. timeout rather than a hardcoded
     timeout of 10 seconds: it's 30 seconds by default, but it is made
     longer on slow buildbots.  Patch by Victor Stinner.

   - bpo-44451(26): Reset ‘DeprecationWarning’ filters in
     ‘test.test_importlib.test_metadata_api.APITests.test_entry_points_by_index’
     to avoid ‘StopIteration’ error if ‘DeprecationWarnings’ are
     ignored.

   - bpo-44363(27): Account for address sanitizer in test_capi.
     test_capi now passes when run GCC address sanitizer.

   - bpo-44364(28): Add non integral tests for *note math.sqrt(): 9aa.
     function.

   - bpo-43921(29): Fix test_ssl.test_wrong_cert_tls13(): use
     ‘suppress_ragged_eofs=False’, since ‘read()’ can raise *note
     ssl.SSLEOFError: 1646. on Windows.  Patch by Victor Stinner.

   - bpo-43921(30): Fix test_pha_required_nocert() of test_ssl: catch
     two more EOF cases (when the ‘recv()’ method returns an empty
     string).  Patch by Victor Stinner.

   - bpo-44131(31): Add test_frozenmain to test_embed to test the
     ‘Py_FrozenMain()’ C function.  Patch by Victor Stinner.

   - bpo-31904(32): Ignore error string case in test_file_not_exists().

   - bpo-42083(33): Add test to check that ‘PyStructSequence_NewType’
     accepts a ‘PyStructSequence_Desc’ with ‘doc’ field set to ‘NULL’.

   - bpo-35753(34): Fix crash in doctest when doctest parses modules
     that include unwrappable functions by skipping those functions.

   - bpo-30256(35): Add test for nested queues when using
     ‘multiprocessing’ shared objects ‘AutoProxy[Queue]’ inside
     ‘ListProxy’ and ‘DictProxy’

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40173

   (2) https://bugs.python.org/issue?@action=redirect&bpo=45280

   (3) https://bugs.python.org/issue?@action=redirect&bpo=45269

   (4) https://bugs.python.org/issue?@action=redirect&bpo=45128

   (5) https://bugs.python.org/issue?@action=redirect&bpo=45209

   (6) https://bugs.python.org/issue?@action=redirect&bpo=45185

   (7) https://bugs.python.org/issue?@action=redirect&bpo=45195

   (8) https://bugs.python.org/issue?@action=redirect&bpo=45156

   (9) https://bugs.python.org/issue?@action=redirect&bpo=45125

   (10) https://bugs.python.org/issue?@action=redirect&bpo=44860

   (11) https://bugs.python.org/issue?@action=redirect&bpo=45052

   (12) https://bugs.python.org/issue?@action=redirect&bpo=44895

   (13) https://bugs.python.org/issue?@action=redirect&bpo=45042

   (14) https://bugs.python.org/issue?@action=redirect&bpo=25130

   (15) https://bugs.python.org/issue?@action=redirect&bpo=45011

   (16) https://bugs.python.org/issue?@action=redirect&bpo=44949

   (17) https://bugs.python.org/issue?@action=redirect&bpo=44891

   (18) https://bugs.python.org/issue?@action=redirect&bpo=44852

   (19) https://bugs.python.org/issue?@action=redirect&bpo=40928

   (20) https://bugs.python.org/issue?@action=redirect&bpo=44734

   (21) https://bugs.python.org/issue?@action=redirect&bpo=44708

   (22) https://bugs.python.org/issue?@action=redirect&bpo=42095

   (23) https://bugs.python.org/issue?@action=redirect&bpo=44647

   (24) https://bugs.python.org/issue?@action=redirect&bpo=44515

   (25) https://bugs.python.org/issue?@action=redirect&bpo=44287

   (26) https://bugs.python.org/issue?@action=redirect&bpo=44451

   (27) https://bugs.python.org/issue?@action=redirect&bpo=44363

   (28) https://bugs.python.org/issue?@action=redirect&bpo=44364

   (29) https://bugs.python.org/issue?@action=redirect&bpo=43921

   (30) https://bugs.python.org/issue?@action=redirect&bpo=43921

   (31) https://bugs.python.org/issue?@action=redirect&bpo=44131

   (32) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (33) https://bugs.python.org/issue?@action=redirect&bpo=42083

   (34) https://bugs.python.org/issue?@action=redirect&bpo=35753

   (35) https://bugs.python.org/issue?@action=redirect&bpo=30256


File: python.info,  Node: Build<28>,  Next: Windows<25>,  Prev: Tests<26>,  Up: Python 3 11 0 alpha 1

1.23.29.6 Build
...............

   - bpo-45220(1): Avoid building with the Windows 11 SDK previews
     automatically.  This may be overridden by setting the
     ‘DefaultWindowsSDKVersion’ environment variable before building.

   - bpo-45020(2): Freeze stdlib modules that are imported during
     startup.  This provides significant performance improvements to
     startup.  If necessary, use the previously added "-X
     frozen_modules=off" commandline option to force importing the
     source modules.

   - bpo-45188(3): Windows builds now regenerate frozen modules as the
     first part of the build.  Previously the regeneration was later in
     the build, which would require it to be restarted if any modules
     had changed.

   - bpo-45163(4): Fixes Haiku platform build.

   - bpo-45067(5): The ncurses function extended_color_content was
     introduced in 2017

     (‘https://invisible-island.net/ncurses/NEWS.html#index-t20170401’).
     The

     ncurses-devel package in CentOS 7 had a older version ncurses
     resulted in compilation error.  For compiling ncurses with extended
     color support, we verify the version of the ncurses library >=
     20170401.

   - bpo-45019(6): Generate lines in relevant files for frozen modules.
     Up until now each of the files had to be edited manually.  This
     change makes it easier to add to and modify the frozen modules.

   - bpo-44340(7): Add support for building with clang thin lto via
     -with-lto=thin/full.  Patch by Donghee Na and Brett Holman.

   - bpo-44535(8): Enable building using a Visual Studio 2022 install on
     Windows.

   - bpo-43298(9): Improved error message when building without a
     Windows SDK installed.

   - bpo-44381(10): The Windows build now accepts
     ‘EnableControlFlowGuard’ set to ‘guard’ to enable CFG.

   - bpo-41282(11): Fix broken ‘make install’ that caused standard
     library extension modules to be unnecessarily and incorrectly
     rebuilt during the install phase of cpython.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45220

   (2) https://bugs.python.org/issue?@action=redirect&bpo=45020

   (3) https://bugs.python.org/issue?@action=redirect&bpo=45188

   (4) https://bugs.python.org/issue?@action=redirect&bpo=45163

   (5) https://bugs.python.org/issue?@action=redirect&bpo=45067

   (6) https://bugs.python.org/issue?@action=redirect&bpo=45019

   (7) https://bugs.python.org/issue?@action=redirect&bpo=44340

   (8) https://bugs.python.org/issue?@action=redirect&bpo=44535

   (9) https://bugs.python.org/issue?@action=redirect&bpo=43298

   (10) https://bugs.python.org/issue?@action=redirect&bpo=44381

   (11) https://bugs.python.org/issue?@action=redirect&bpo=41282


File: python.info,  Node: Windows<25>,  Next: macOS<20>,  Prev: Build<28>,  Up: Python 3 11 0 alpha 1

1.23.29.7 Windows
.................

   - bpo-45375(1): Fixes an assertion failure due to searching for the
     standard library in unnormalised paths.

   - bpo-45022(2): Update Windows release to include libffi 3.4.2

   - bpo-45007(3): Update to OpenSSL 1.1.1l in Windows build

   - bpo-44848(4): Upgrade Windows installer to use SQLite 3.36.0.

   - bpo-44572(5): Avoid consuming standard input in the *note platform:
     98. module

   - bpo-44582(6): Accelerate speed of *note mimetypes: 82.
     initialization using a native implementation of the registry scan.

   - bpo-41299(7): Fix 16 milliseconds jitter when using timeouts in
     *note threading: d6, such as with *note threading.Lock.acquire():
     63e. or *note threading.Condition.wait(): 17b4.

   - bpo-42686(8): Build *note sqlite3: ba. with math functions enabled.
     Patch by Erlend E. Aasland.

   - bpo-40263(9): This is a follow-on bug from
     ‘https://bugs.python.org/issue26903’.  Once that is applied we run
     into an off-by-one assertion problem.  The assert was not correct.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45375

   (2) https://bugs.python.org/issue?@action=redirect&bpo=45022

   (3) https://bugs.python.org/issue?@action=redirect&bpo=45007

   (4) https://bugs.python.org/issue?@action=redirect&bpo=44848

   (5) https://bugs.python.org/issue?@action=redirect&bpo=44572

   (6) https://bugs.python.org/issue?@action=redirect&bpo=44582

   (7) https://bugs.python.org/issue?@action=redirect&bpo=41299

   (8) https://bugs.python.org/issue?@action=redirect&bpo=42686

   (9) https://bugs.python.org/issue?@action=redirect&bpo=40263


File: python.info,  Node: macOS<20>,  Next: IDLE<17>,  Prev: Windows<25>,  Up: Python 3 11 0 alpha 1

1.23.29.8 macOS
...............

   - bpo-45007(1): Update macOS installer builds to use OpenSSL 1.1.1l.

   - bpo-34602(2): When building CPython on macOS with ‘./configure
     --with-undefined-behavior-sanitizer --with-pydebug’, the stack size
     is now quadrupled to allow for the entire test suite to pass.

   - bpo-44848(3): Update macOS installer to use SQLite 3.36.0.

   - bpo-44689(4): *note ctypes.util.find_library(): cf0. now works
     correctly on macOS 11 Big Sur even if Python is built on an older
     version of macOS. Previously, when built on older macOS systems,
     ‘find_library’ was not able to find macOS system libraries when
     running on Big Sur due to changes in how system libraries are
     stored.

   - bpo-41972(5): The framework build's user header path in sysconfig
     is changed to add a 'pythonX.Y' component to match distutils's
     behavior.

   - bpo-43109(6): Allow -with-lto configure option to work with
     Apple-supplied Xcode or Command Line Tools.

   - bpo-34932(7): Add socket.TCP_KEEPALIVE support for macOS. Patch by
     Shane Harvey.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45007

   (2) https://bugs.python.org/issue?@action=redirect&bpo=34602

   (3) https://bugs.python.org/issue?@action=redirect&bpo=44848

   (4) https://bugs.python.org/issue?@action=redirect&bpo=44689

   (5) https://bugs.python.org/issue?@action=redirect&bpo=41972

   (6) https://bugs.python.org/issue?@action=redirect&bpo=43109

   (7) https://bugs.python.org/issue?@action=redirect&bpo=34932


File: python.info,  Node: IDLE<17>,  Next: Tools/Demos<13>,  Prev: macOS<20>,  Up: Python 3 11 0 alpha 1

1.23.29.9 IDLE
..............

   - bpo-45296(1): On Windows, change exit/quit message to suggest
     Ctrl-D, which works, instead of <Ctrl-Z Return>, which does not
     work in IDLE.

   - bpo-45193(2): Make completion boxes appear on Ubuntu again.

   - bpo-40128(3): Mostly fix completions on macOS when not using tcl/tk
     8.6.11 (as with 3.9).  The added update_idletask call should be
     harmless and possibly helpful otherwise.

   - bpo-33962(4): Move the indent space setting from the Font tab to
     the new Windows tab.  Patch by Mark Roseman and Terry Jan Reedy.

   - bpo-40468(5): Split the settings dialog General tab into Windows
     and Shell/ED tabs.  Move help sources, which extend the Help menu,
     to the Extensions tab.  Make space for new options and shorten the
     dialog.  The latter makes the dialog better fit small screens.

   - bpo-41611(6): Avoid uncaught exceptions in
     ‘AutoCompleteWindow.winconfig_event()’.

   - bpo-41611(7): Fix IDLE sometimes freezing upon tab-completion on
     macOS.

   - bpo-44010(8): Highlight the new *note match: 7b1. statement's *note
     soft keywords: 7b0.: *note match: 7b1, *note case: 7b1, and *note
     _: 7b2.  However, this highlighting is not perfect and will be
     incorrect in some rare cases, including some ‘_’-s in ‘case’
     patterns.

   - bpo-44026(9): Include interpreter's typo fix suggestions in message
     line for NameErrors and AttributeErrors.  Patch by E. Paine.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=45296

   (2) https://bugs.python.org/issue?@action=redirect&bpo=45193

   (3) https://bugs.python.org/issue?@action=redirect&bpo=40128

   (4) https://bugs.python.org/issue?@action=redirect&bpo=33962

   (5) https://bugs.python.org/issue?@action=redirect&bpo=40468

   (6) https://bugs.python.org/issue?@action=redirect&bpo=41611

   (7) https://bugs.python.org/issue?@action=redirect&bpo=41611

   (8) https://bugs.python.org/issue?@action=redirect&bpo=44010

   (9) https://bugs.python.org/issue?@action=redirect&bpo=44026


File: python.info,  Node: Tools/Demos<13>,  Next: C API<27>,  Prev: IDLE<17>,  Up: Python 3 11 0 alpha 1

1.23.29.10 Tools/Demos
......................

   - bpo-44786(1): Fix a warning in regular expression in the c-analyzer
     script.

   - bpo-44967(2): pydoc now returns a non-zero status code when a
     module cannot be found.

   - bpo-44978(3): Allow the Argument Clinic tool to handle
     ‘__complex__’ special methods.

   - bpo-43425(4): Removed the 'test2to3' demo project that demonstrated
     using lib2to3 to support Python 2.x and Python 3.x from a single
     source in a distutils package.  Patch by Donghee Na

   - bpo-44074(5): Make patchcheck automatically detect the correct base
     branch name (previously it was hardcoded to 'master')

   - bpo-20291(6): Added support for variadic positional parameters in
     Argument Clinic.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=44786

   (2) https://bugs.python.org/issue?@action=redirect&bpo=44967

   (3) https://bugs.python.org/issue?@action=redirect&bpo=44978

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43425

   (5) https://bugs.python.org/issue?@action=redirect&bpo=44074

   (6) https://bugs.python.org/issue?@action=redirect&bpo=20291


File: python.info,  Node: C API<27>,  Prev: Tools/Demos<13>,  Up: Python 3 11 0 alpha 1

1.23.29.11 C API
................

   - bpo-41710(1): The PyThread_acquire_lock_timed() function now clamps
     the timeout if it is too large, rather than aborting the process.
     Patch by Victor Stinner.

   - bpo-44687(2): ‘BufferedReader.peek()’ no longer raises *note
     ValueError: 1e7. when the entire file has already been buffered.

   - bpo-45116(3): Add the *note Py_ALWAYS_INLINE: 17b9. macro to ask
     the compiler to always inline a static inline function.  The
     compiler can ignore it and decides to not inline the function.
     Patch by Victor Stinner.

   - bpo-45094(4): Add the *note Py_NO_INLINE: 17ba. macro to disable
     inlining on a function.  Patch by Victor Stinner.

   - bpo-45061(5): Add a deallocator to the *note bool: 40e. type to
     detect refcount bugs in C extensions which call
     ‘Py_DECREF(Py_True);’ or ‘Py_DECREF(Py_False);’ by mistake.  Patch
     by Victor Stinner.

   - bpo-42035(6): Add a new *note PyType_GetQualName(): 6f7. function
     to get type's qualified name.

   - bpo-41103(7): Reverts removal of the old buffer protocol because
     they are part of stable ABI.

   - bpo-44751(8): Remove ‘crypt.h’ include from the public ‘Python.h’
     header.

   - bpo-42747(9): The ‘Py_TPFLAGS_HAVE_VERSION_TAG’ type flag now does
     nothing.  The ‘Py_TPFLAGS_HAVE_AM_SEND’ flag (which was added in
     3.10) is removed.  Both were unnecessary because it is not possible
     to have type objects with the relevant fields missing.

   - bpo-44530(10): Added the ‘co_qualname’ to the ‘PyCodeObject’
     structure to propagate the qualified name from the compiler to code
     objects.

     Patch by Gabriele N. Tornetta

   - bpo-44441(11): *note Py_RunMain(): 969. now resets
     ‘PyImport_Inittab’ to its initial value at exit.  It must be
     possible to call *note PyImport_AppendInittab(): 16a6. or *note
     PyImport_ExtendInittab(): 16a7. at each Python initialization.
     Patch by Victor Stinner.

   - bpo-39947(12): Remove 4 private trashcan C API functions which were
     only kept for the backward compatibility of the stable ABI with
     Python 3.8 and older, since the trashcan API was not usable with
     the limited C API on Python 3.8 and older.  The trashcan API was
     excluded from the limited C API in Python 3.9.

     Removed functions:

        * _PyTrash_deposit_object()

        * _PyTrash_destroy_chain()

        * _PyTrash_thread_deposit_object()

        * _PyTrash_thread_destroy_chain()

     The trashcan C API was never usable with the limited C API, since
     old trashcan macros accessed directly *note PyThreadState: 731.
     members like ‘_tstate->trash_delete_nesting’, whereas the *note
     PyThreadState: 731. structure is opaque in the limited C API.

     Exclude also the ‘PyTrash_UNWIND_LEVEL’ constant from the C API.

     Patch by Victor Stinner.

   - bpo-40939(13): Removed documentation for the removed ‘PyParser_*’ C
     API.

   - bpo-43795(14): The list in *note 受限 API 的內容: 73e. now shows
     the public name *note PyFrameObject: 72d. rather than ‘_frame’.
     The non-existing entry ‘_node’ no longer appears in the list.

   - bpo-44378(15): *note Py_IS_TYPE(): 171a. no longer uses *note
     Py_TYPE(): 724. to avoid a compiler warning: no longer cast ‘const
     PyObject*’ to ‘PyObject*’.  Patch by Victor Stinner.

   - bpo-39573(16): Convert the *note Py_TYPE(): 724. and *note
     Py_SIZE(): 726. macros to static inline functions.  The *note
     Py_SET_TYPE(): 725. and *note Py_SET_SIZE(): 727. functions must
     now be used to set an object type and size.  Patch by Victor
     Stinner.

   - bpo-44263(17): The *note PyType_Ready(): 722. function now raises
     an error if a type is defined with the *note Py_TPFLAGS_HAVE_GC:
     720. flag set but has no traverse function (*note
     PyTypeObject.tp_traverse: 721.).  Patch by Victor Stinner.

   - bpo-43795(18): The undocumented function ‘Py_FrozenMain()’ is
     removed from the Limited API.

   - bpo-44113(19): Deprecate the following functions to configure the
     Python initialization:

        * ‘PySys_AddWarnOptionUnicode()’

        * ‘PySys_AddWarnOption()’

        * ‘PySys_AddXOption()’

        * ‘PySys_HasWarnOptions()’

        * ‘Py_SetPath()’

        * ‘Py_SetProgramName()’

        * ‘Py_SetPythonHome()’

        * ‘Py_SetStandardStreamEncoding()’

        * ‘_Py_SetProgramFullPath()’

     Use the new *note PyConfig: 371. API of the *note Python
     Initialization Configuration: 372. instead ( PEP 587(20)).

   - bpo-44094(21): Remove ‘PyErr_SetFromErrnoWithUnicodeFilename()’,
     ‘PyErr_SetFromWindowsErrWithUnicodeFilename()’, and
     ‘PyErr_SetExcFromWindowsErrWithUnicodeFilename()’.  They are not
     documented and have been deprecated since Python 3.3.

   - bpo-43795(22): *note PyCodec_Unregister(): 83b. is now properly
     exported as a function in the Windows Stable ABI DLL.

   - bpo-44029(23): Remove deprecated ‘Py_UNICODE’ APIs:
     ‘PyUnicode_Encode’, ‘PyUnicode_EncodeUTF7’, ‘PyUnicode_EncodeUTF8’,
     ‘PyUnicode_EncodeUTF16’, ‘PyUnicode_EncodeUTF32’,
     ‘PyUnicode_EncodeLatin1’, ‘PyUnicode_EncodeMBCS’,
     ‘PyUnicode_EncodeDecimal’, ‘PyUnicode_EncodeRawUnicodeEscape’,
     ‘PyUnicode_EncodeCharmap’, ‘PyUnicode_EncodeUnicodeEscape’,
     ‘PyUnicode_TransformDecimalToASCII’, ‘PyUnicode_TranslateCharmap’,
     ‘PyUnicodeEncodeError_Create’, ‘PyUnicodeTranslateError_Create’.
     See PEP 393(24) and PEP 624(25) for reference.

   - bpo-42035(26): Add a new *note PyType_GetName(): 6f6. function to
     get type's short name.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41710

   (2) https://bugs.python.org/issue?@action=redirect&bpo=44687

   (3) https://bugs.python.org/issue?@action=redirect&bpo=45116

   (4) https://bugs.python.org/issue?@action=redirect&bpo=45094

   (5) https://bugs.python.org/issue?@action=redirect&bpo=45061

   (6) https://bugs.python.org/issue?@action=redirect&bpo=42035

   (7) https://bugs.python.org/issue?@action=redirect&bpo=41103

   (8) https://bugs.python.org/issue?@action=redirect&bpo=44751

   (9) https://bugs.python.org/issue?@action=redirect&bpo=42747

   (10) https://bugs.python.org/issue?@action=redirect&bpo=44530

   (11) https://bugs.python.org/issue?@action=redirect&bpo=44441

   (12) https://bugs.python.org/issue?@action=redirect&bpo=39947

   (13) https://bugs.python.org/issue?@action=redirect&bpo=40939

   (14) https://bugs.python.org/issue?@action=redirect&bpo=43795

   (15) https://bugs.python.org/issue?@action=redirect&bpo=44378

   (16) https://bugs.python.org/issue?@action=redirect&bpo=39573

   (17) https://bugs.python.org/issue?@action=redirect&bpo=44263

   (18) https://bugs.python.org/issue?@action=redirect&bpo=43795

   (19) https://bugs.python.org/issue?@action=redirect&bpo=44113

   (20) https://peps.python.org/pep-0587/

   (21) https://bugs.python.org/issue?@action=redirect&bpo=44094

   (22) https://bugs.python.org/issue?@action=redirect&bpo=43795

   (23) https://bugs.python.org/issue?@action=redirect&bpo=44029

   (24) https://peps.python.org/pep-0393/

   (25) https://peps.python.org/pep-0624/

   (26) https://bugs.python.org/issue?@action=redirect&bpo=42035


File: python.info,  Node: Python 3 10 0 beta 1,  Next: Python 3 10 0 alpha 7,  Prev: Python 3 11 0 alpha 1,  Up: Changelog（更動日誌）

1.23.30 Python 3.10.0 beta 1
----------------------------

'Release date: 2021-05-03'

* Menu:

* Security: Security<17>.
* Core and Builtins: Core and Builtins<30>.
* Library: Library<29>.
* Documentation: Documentation<24>.
* Tests: Tests<27>.
* Build: Build<29>.
* Windows: Windows<26>.
* macOS: macOS<21>.
* IDLE: IDLE<18>.
* C API: C API<28>.


File: python.info,  Node: Security<17>,  Next: Core and Builtins<30>,  Up: Python 3 10 0 beta 1

1.23.30.1 Security
..................

   - bpo-43434(1): Creating *note sqlite3.Connection: 22a. objects now
     also produces ‘sqlite3.connect’ and ‘sqlite3.connect/handle’ *note
     auditing events: 17bd.  Previously these events were only produced
     by *note sqlite3.connect(): 288. calls.  Patch by Erlend E.
     Aasland.

   - bpo-43998(2): The *note ssl: bb. module sets more secure cipher
     suites defaults.  Ciphers without forward secrecy and with SHA-1
     MAC are disabled by default.  Security level 2 prohibits weak RSA,
     DH, and ECC keys with less than 112 bits of security.  *note
     SSLContext: 276. defaults to minimum protocol version TLS 1.2.
     Settings are based on Hynek Schlawack's research.

   - bpo-43882(3): The presence of newline or tab characters in parts of
     a URL could allow some forms of attacks.

     Following the controlling specification for URLs defined by WHATWG
     *note urllib.parse(): f3. now removes ASCII newlines and tabs from
     URLs, preventing such attacks.

   - bpo-43472(4): Ensures interpreter-level audit hooks receive the
     ‘cpython.PyInterpreterState_New’ event when called through the
     ‘_xxsubinterpreters’ module.

   - bpo-43362(5): Fix invalid free in _sha3 module.  The issue was
     introduced in 3.10.0a1.  Python 3.9 and earlier are not affected.

   - bpo-43762(6): Add audit events for ‘sqlite3.connect/handle()’,
     *note sqlite3.Connection.enable_load_extension(): 7e2, and *note
     sqlite3.Connection.load_extension(): 45f.  Patch by Erlend E.
     Aasland.

   - bpo-43756(7): Add new audit event ‘glob.glob/2’ to incorporate the
     new 'root_dir' and 'dir_fd' arguments added to *note glob.glob():
     280. and *note glob.iglob(): 7ab.

   - bpo-36384(8): *note ipaddress: 74. module no longer accepts any
     leading zeros in IPv4 address strings.  Leading zeros are ambiguous
     and interpreted as octal notation by some libraries.  For example
     the legacy function *note socket.inet_aton(): 905. treats leading
     zeros as octal notation.  glibc implementation of modern *note
     inet_pton(): 906. does not accept any leading zeros.  For a while
     the *note ipaddress: 74. module used to accept ambiguous leading
     zeros.

   - bpo-43075(9): Fix Regular Expression Denial of Service (ReDoS)
     vulnerability in *note urllib.request.AbstractBasicAuthHandler:
     17be.  The ReDoS-vulnerable regex has quadratic worst-case
     complexity and it allows cause a denial of service when identifying
     crafted invalid RFCs.  This ReDoS issue is on the client side and
     needs remote attackers to control the HTTP server.

   - bpo-42800(10): Audit hooks are now fired for frame.f_code,
     traceback.tb_frame, and generator code/frame attribute access.

   - bpo-37363(11): Add audit events to the *note http.client: 65.
     module.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43434

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43998

   (3) https://bugs.python.org/issue?@action=redirect&bpo=43882

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43472

   (5) https://bugs.python.org/issue?@action=redirect&bpo=43362

   (6) https://bugs.python.org/issue?@action=redirect&bpo=43762

   (7) https://bugs.python.org/issue?@action=redirect&bpo=43756

   (8) https://bugs.python.org/issue?@action=redirect&bpo=36384

   (9) https://bugs.python.org/issue?@action=redirect&bpo=43075

   (10) https://bugs.python.org/issue?@action=redirect&bpo=42800

   (11) https://bugs.python.org/issue?@action=redirect&bpo=37363


File: python.info,  Node: Core and Builtins<30>,  Next: Library<29>,  Prev: Security<17>,  Up: Python 3 10 0 beta 1

1.23.30.2 Core and Builtins
...........................

   - bpo-43977(1): Prevent classes being both a sequence and a mapping
     when pattern matching.

   - bpo-43977(2): Use *note tp_flags: 17c0. on the class object to
     determine if the subject is a sequence or mapping when pattern
     matching.  Avoids the need to import *note collections.abc: 17.
     when pattern matching.

   - bpo-43892(3): Restore proper validation of complex literal value
     patterns when parsing ‘match’ blocks.

   - bpo-43933(4): Set frame.f_lineno to the line number of the 'with'
     kweyword when executing the call to ‘__exit__’.

   - bpo-43933(5): If the current position in a frame has no line number
     then set the f_lineno attribute to None, instead of -1, to conform
     to PEP 626.  This should not normally be possible, but might occur
     in some unusual circumstances.

   - bpo-43963(6): Importing the ‘_signal’ module in a subinterpreter
     has no longer side effects.

   - bpo-42739(7): The internal representation of line number tables is
     changed to not use sentinels, and an explicit length parameter is
     added to the out of process API function
     ‘PyLineTable_InitAddressRange’.  This makes the handling of line
     number tables more robust in some circumstances.

   - bpo-43908(8): Make *note re: a7. types immutable.  Patch by Erlend
     E. Aasland.

   - bpo-43908(9): Make the *note array.array: 186. type immutable.
     Patch by Erlend E. Aasland.

   - bpo-43901(10): Change class and module objects to lazy-create empty
     annotations dicts on demand.  The annotations dicts are stored in
     the object's __dict__ for backwards compatibility.

   - bpo-43892(11): Match patterns now use new dedicated AST nodes
     (‘MatchValue’, ‘MatchSingleton’, ‘MatchSequence’, ‘MatchStar’,
     ‘MatchMapping’, ‘MatchClass’) rather than reusing expression AST
     nodes.  ‘MatchAs’ and ‘MatchOr’ are now defined as pattern nodes
     rather than as expression nodes.  Patch by Nick Coghlan.

   - bpo-42725(12): Usage of ‘await’/‘yield’/‘yield from’ and named
     expressions within an annotation is now forbidden when PEP 563 is
     activated.

   - bpo-43754(13): When performing structural pattern matching ( PEP
     634(14)), captured names are now left unbound until the 'entire'
     pattern has matched successfully.

   - bpo-42737(15): Annotations for complex targets (everything beside
     simple names) no longer cause any runtime effects with ‘from
     __future__ import annotations’.

   - bpo-43914(16): *note SyntaxError: 173. exceptions raised by the
     interpreter will highlight the full error range of the expression
     that constitutes the syntax error itself, instead of just where the
     problem is detected.  Patch by Pablo Galindo.

   - bpo-38605(17): Revert making ‘from __future__ import annotations’
     the default.  This follows the Steering Council decision to
     postpone PEP 563 changes to at least Python 3.11.  See the original
     email for more information regarding the decision:
     ‘https://mail.python.org/archives/list/python-dev@python.org/thread/CLVXXPQ2T2LQ5MP2Y53VVQFCXYWQJHKZ/’.
     Patch by Pablo Galindo.

   - bpo-43475(18): Hashes of NaN values now depend on object identity.
     Formerly, they always hashed to 0 even though NaN values are not
     equal to one another.  Having the same hash for unequal values
     caused pile-ups in hash tables.

   - bpo-43859(19): Improve the error message for *note
     IndentationError: 74c. exceptions.  Patch by Pablo Galindo

   - bpo-41323(20): Constant tuple folding in bytecode optimizer now
     reuses tuple in constant table.

   - bpo-43846(21): Data stack usage is much reduced for large literal
     and call expressions.

   - bpo-38530(22): When printing *note NameError: 3e5. raised by the
     interpreter, ‘PyErr_Display()’ will offer suggestions of similar
     variable names in the function that the exception was raised from.
     Patch by Pablo Galindo

   - bpo-43823(23): Improve syntax errors for invalid dictionary
     literals.  Patch by Pablo Galindo.

   - bpo-43822(24): Improve syntax errors in the parser for missing
     commas between expressions.  Patch by Pablo Galindo.

   - bpo-43798(25): *note ast.alias: 17c1. nodes now include source
     location metadata attributes e.g.  lineno, col_offset.

   - bpo-43797(26): Improve ‘SyntaxError’ error messages for invalid
     comparisons.  Patch by Pablo Galindo.

   - bpo-43760(27): Move the flag for checking whether tracing is
     enabled to the C stack, from the heap.  Should speed up dispatch in
     the interpreter.

   - bpo-43682(28): Static methods (*note @staticmethod: 358.) and class
     methods (*note @classmethod: 14a.) now inherit the method
     attributes (‘__module__’, ‘__name__’, ‘__qualname__’, ‘__doc__’,
     ‘__annotations__’) and have a new ‘__wrapped__’ attribute.  Patch
     by Victor Stinner.

   - bpo-43751(29): Fixed a bug where ‘anext(ait, default)’ would
     erroneously return None.

   - bpo-42128(30): *note __match_args__: 17c2. is no longer allowed to
     be a list.

   - bpo-43683(31): Add GEN_START opcode.  Marks start of generator,
     including async, or coroutine and handles sending values to a newly
     created generator or coroutine.

   - bpo-43105(32): Importlib now resolves relative paths when creating
     module spec objects from file locations.

   - bpo-43682(33): Static methods (*note @staticmethod: 358.) are now
     callable as regular functions.  Patch by Victor Stinner.

   - bpo-42609(34): Prevented crashes in the AST validator and optimizer
     when compiling some absurdly long expressions like ‘"+0"*1000000’.
     *note RecursionError: d12. is now raised instead.

   - bpo-38530(35): When printing *note AttributeError: 2f6,
     ‘PyErr_Display()’ will offer suggestions of similar attribute names
     in the object that the exception was raised from.  Patch by Pablo
     Galindo

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43977

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43977

   (3) https://bugs.python.org/issue?@action=redirect&bpo=43892

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43933

   (5) https://bugs.python.org/issue?@action=redirect&bpo=43933

   (6) https://bugs.python.org/issue?@action=redirect&bpo=43963

   (7) https://bugs.python.org/issue?@action=redirect&bpo=42739

   (8) https://bugs.python.org/issue?@action=redirect&bpo=43908

   (9) https://bugs.python.org/issue?@action=redirect&bpo=43908

   (10) https://bugs.python.org/issue?@action=redirect&bpo=43901

   (11) https://bugs.python.org/issue?@action=redirect&bpo=43892

   (12) https://bugs.python.org/issue?@action=redirect&bpo=42725

   (13) https://bugs.python.org/issue?@action=redirect&bpo=43754

   (14) https://peps.python.org/pep-0634/

   (15) https://bugs.python.org/issue?@action=redirect&bpo=42737

   (16) https://bugs.python.org/issue?@action=redirect&bpo=43914

   (17) https://bugs.python.org/issue?@action=redirect&bpo=38605

   (18) https://bugs.python.org/issue?@action=redirect&bpo=43475

   (19) https://bugs.python.org/issue?@action=redirect&bpo=43859

   (20) https://bugs.python.org/issue?@action=redirect&bpo=41323

   (21) https://bugs.python.org/issue?@action=redirect&bpo=43846

   (22) https://bugs.python.org/issue?@action=redirect&bpo=38530

   (23) https://bugs.python.org/issue?@action=redirect&bpo=43823

   (24) https://bugs.python.org/issue?@action=redirect&bpo=43822

   (25) https://bugs.python.org/issue?@action=redirect&bpo=43798

   (26) https://bugs.python.org/issue?@action=redirect&bpo=43797

   (27) https://bugs.python.org/issue?@action=redirect&bpo=43760

   (28) https://bugs.python.org/issue?@action=redirect&bpo=43682

   (29) https://bugs.python.org/issue?@action=redirect&bpo=43751

   (30) https://bugs.python.org/issue?@action=redirect&bpo=42128

   (31) https://bugs.python.org/issue?@action=redirect&bpo=43683

   (32) https://bugs.python.org/issue?@action=redirect&bpo=43105

   (33) https://bugs.python.org/issue?@action=redirect&bpo=43682

   (34) https://bugs.python.org/issue?@action=redirect&bpo=42609

   (35) https://bugs.python.org/issue?@action=redirect&bpo=38530


File: python.info,  Node: Library<29>,  Next: Documentation<24>,  Prev: Core and Builtins<30>,  Up: Python 3 10 0 beta 1

1.23.30.3 Library
.................

   - bpo-44015(1): In @dataclass(), raise a TypeError if KW_ONLY is
     specified more than once.

   - bpo-25478(2): Added a 'total()' method to collections.Counter() to
     compute the sum of the counts.

   - bpo-43733(3): Change *note netrc.netrc: 17c4. to use UTF-8 encoding
     before using locale encoding.

   - bpo-43979(4): Removed an unnecessary list comprehension before
     looping from *note urllib.parse.parse_qsl(): 25e.  Patch by
     Christoph Zwerschke and Donghee Na.

   - bpo-43993(5): Update bundled pip to 21.1.1.

   - bpo-43957(6): [Enum] Deprecate ‘TypeError’ when non-member is used
     in a containment check; In 3.12 ‘True’ or ‘False’ will be returned
     instead, and containment will return ‘True’ if the value is either
     a member of that enum or one of its members' value.

   - bpo-42904(7): For backwards compatibility with previous minor
     versions of Python, if *note typing.get_type_hints(): 657. receives
     no namespace dictionary arguments, *note typing.get_type_hints():
     657. will search through the global then local namespaces during
     evaluation of stringized type annotations (string forward
     references) inside a class.

   - bpo-43945(8): [Enum] Deprecate non-standard mixin format()
     behavior: in 3.12 the enum member, not the member's value, will be
     used for format() calls.

   - bpo-41139(9): Deprecate undocumented ‘cgi.log()’ API.

   - bpo-43937(10): Fixed the *note turtle: ea. module working with
     non-default root window.

   - bpo-43930(11): Update bundled pip to 21.1 and setuptools to 56.0.0

   - bpo-43907(12): Fix a bug in the pure-Python pickle implementation
     when using protocol 5, where bytearray instances that occur several
     time in the pickled object graph would incorrectly unpickle into
     repeated copies of the bytearray object.

   - bpo-43926(13): In ‘importlib.metadata’, provide a uniform interface
     to ‘Description’, allow for any field to be encoded with multiline
     values, remove continuation lines from multiline values, and add a
     ‘.json’ property for easy access to the PEP 566 JSON-compatible
     form.  Sync with ‘importlib_metadata 4.0’.

   - bpo-43920(14): OpenSSL 3.0.0: *note load_verify_locations(): e8f.
     now returns a consistent error message when cadata contains no
     valid certificate.

   - bpo-43607(15): *note urllib: f1. can now convert Windows paths with
     ‘\\?\’ prefixes into URL paths.

   - bpo-43817(16): Add *note inspect.get_annotations(): 7b7, which
     safely computes the annotations defined on an object.  It works
     around the quirks of accessing the annotations from various types
     of objects, and makes very few assumptions about the object passed
     in.  *note inspect.get_annotations(): 7b7. can also correctly
     un-stringize stringized annotations.

     *note inspect.signature(): 6dc, ‘inspect.from_callable()’, and
     ‘inspect.from_function()’ now call *note inspect.get_annotations():
     7b7. to retrieve annotations.  This means *note
     inspect.signature(): 6dc. and ‘inspect.from_callable()’ can now
     un-stringize stringized annotations, too.

   - bpo-43284(17): platform.win32_ver derives the windows version from
     sys.getwindowsversion().platform_version which in turn derives the
     version from kernel32.dll (which can be of a different version than
     Windows itself).  Therefore change the platform.win32_ver to
     determine the version using the platform module's _syscmd_ver
     private function to return an accurate version.

   - bpo-42854(18): The *note ssl: bb. module now uses ‘SSL_read_ex’ and
     ‘SSL_write_ex’ internally.  The functions support reading and
     writing of data larger than 2 GB. Writing zero-length data no
     longer fails with a protocol violation error.

   - bpo-42333(19): Port ‘_ssl’ extension module to multiphase
     initialization.

   - bpo-43880(20): *note ssl: bb. now raises DeprecationWarning for
     OP_NO_SSL/TLS* options, old TLS versions, old protocols, and other
     features that have been deprecated since Python 3.6, 3.7, or
     OpenSSL 1.1.0.

   - bpo-41559(21): PEP 612(22) is now implemented purely in Python;
     builtin ‘types.GenericAlias’ objects no longer include
     ‘typing.ParamSpec’ in ‘__parameters__’ (with the exception of
     ‘collections.abc.Callable’'s ‘GenericAlias’).  This means
     previously invalid uses of ‘ParamSpec’ (such as ‘list[P]’) which
     worked in earlier versions of Python 3.10 alpha, will now raise
     ‘TypeError’ during substitution.

   - bpo-43867(23): The *note multiprocessing: 86. ‘Server’ class now
     explicitly catches *note SystemExit: ce7. and closes the client
     connection in this case.  It happens when the
     ‘Server.serve_client()’ method reaches the end of file (EOF).

   - bpo-40443(24): Remove unused imports: pyclbr no longer uses copy,
     and typing no longer uses ast.  Patch by Victor Stinner.

   - bpo-43820(25): Remove an unneeded copy of the namespace passed to
     dataclasses.make_dataclass().

   - bpo-43787(26): Add ‘__iter__()’ method to *note bz2.BZ2File: 80b,
     *note gzip.GzipFile: 354, and *note lzma.LZMAFile: fad.  It makes
     iterating them about 2x faster.  Patch by Inada Naoki.

   - bpo-43680(27): Deprecate io.OpenWrapper and _pyio.OpenWrapper: use
     io.open and _pyio.open instead.  Until Python 3.9, _pyio.open was
     not a static method and builtins.open was set to OpenWrapper to not
     become a bound method when set to a class variable.  _io.open is a
     built-in function whereas _pyio.open is a Python function.  In
     Python 3.10, _pyio.open() is now a static method, and
     builtins.open() is now io.open().

   - bpo-43680(28): The Python ‘_pyio.open()’ function becomes a static
     method to behave as *note io.open(): 4c1. built-in function: don't
     become a bound method when stored as a class variable.  It becomes
     possible since static methods are now callable in Python 3.10.
     Moreover, ‘_pyio.OpenWrapper()’ becomes a simple alias to
     ‘_pyio.open()’.  Patch by Victor Stinner.

   - bpo-41515(29): Fix *note KeyError: 2fb. raised in *note
     typing.get_type_hints(): 657. due to synthetic modules that don't
     appear in ‘sys.modules’.

   - bpo-43776(30): When *note subprocess.Popen: 17d. args are provided
     as a string or as *note pathlib.Path: 20e, the Popen instance repr
     now shows the right thing.

   - bpo-42248(31): [Enum] ensure exceptions raised in ‘_missing__’ are
     released

   - bpo-43744(32): fix issue with enum member name matching the start
     of a private variable name

   - bpo-43772(33): Fixed the return value of ‘TypeVar.__ror__’.  Patch
     by Jelle Zijlstra.

   - bpo-43764(34): Add match_args parameter to @dataclass decorator to
     allow suppression of __match_args__ generation.

   - bpo-43799(35): OpenSSL 3.0.0: define ‘OPENSSL_API_COMPAT’ 1.1.1 to
     suppress deprecation warnings.  Python requires OpenSSL 1.1.1 APIs.

   - bpo-43478(36): Mocks can no longer be used as the specs for other
     Mocks.  As a result, an already-mocked object cannot have an
     attribute mocked using ‘autospec=True’ or be the subject of a
     ‘create_autospec(...)’ call.  This can uncover bugs in tests since
     these Mock-derived Mocks will always pass certain tests (e.g.
     *note isinstance(): 3e8.) and builtin assert functions (e.g.
     assert_called_once_with) will unconditionally pass.

   - bpo-43794(37): Add *note ssl.OP_IGNORE_UNEXPECTED_EOF: 7db.
     constants (OpenSSL 3.0.0)

   - bpo-43785(38): Improve ‘bz2.BZ2File’ performance by removing the
     RLock from BZ2File.  This makes BZ2File thread unsafe in the face
     of multiple simultaneous readers or writers, just like its
     equivalent classes in *note gzip: 5d. and *note lzma: 7e. have
     always been.  Patch by Inada Naoki.

   - bpo-43789(39): OpenSSL 3.0.0: Don't call the password callback
     function a second time when first call has signaled an error
     condition.

   - bpo-43788(40): The header files for *note ssl: bb. error codes are
     now OpenSSL version-specific.  Exceptions will now show correct
     reason and library codes.  The ‘make_ssl_data.py’ script has been
     rewritten to use OpenSSL's text file with error codes.

   - bpo-43766(41): Implement PEP 647(42) in the *note typing: ed.
     module by adding ‘TypeGuard’.

   - bpo-25264(43): *note os.path.realpath(): 20a. now accepts a
     'strict' keyword-only argument.  When set to ‘True’, *note OSError:
     350. is raised if a path doesn't exist or a symlink loop is
     encountered.

   - bpo-43780(44): In ‘importlib.metadata’, incorporate changes from
     importlib_metadata 3.10: Add mtime-based caching during
     distribution discovery.  Flagged use of dict result from
     ‘entry_points()’ as deprecated.

   - The ‘P.args’ and ‘P.kwargs’ attributes of *note typing.ParamSpec:
     142. are now instances of the new classes *note
     typing.ParamSpecArgs: 76a. and *note typing.ParamSpecKwargs: 76b,
     which enables a more useful ‘repr()’.  Patch by Jelle Zijlstra.

   - bpo-43731(45): Add an ‘encoding’ parameter ‘logging.fileConfig()’.

   - bpo-43712(46): Add ‘encoding’ and ‘errors’ parameters to *note
     fileinput.input(): 7a3. and *note fileinput.FileInput: 6db.

   - bpo-38659(47): A ‘simple_enum’ decorator is added to the ‘enum’
     module to convert a normal class into an Enum.  ‘test_simple_enum’
     added to test simple enums against a corresponding normal Enum.
     Standard library modules updated to use ‘simple_enum’.

   - bpo-43764(48): Fix an issue where *note __match_args__: 17c2.
     generation could fail for some *note dataclasses: 27.

   - bpo-43752(49): Fix *note sqlite3: ba. regression for zero-sized
     blobs with converters, where ‘b""’ was returned instead of ‘None’.
     The regression was introduced by PR 24723.  Patch by Erlend E.
     Aasland.

   - bpo-43655(50): *note tkinter: d9. dialog windows are now recognized
     as dialogs by window managers on macOS and X Window.

   - bpo-43723(51): The following ‘threading’ methods are now deprecated
     and should be replaced:

        - ‘currentThread’ => *note threading.current_thread(): 2db.

        - ‘activeCount’ => *note threading.active_count(): 2dc.

        - ‘Condition.notifyAll’ => *note
          threading.Condition.notify_all(): 2d5.

        - ‘Event.isSet’ => *note threading.Event.is_set(): 2d6.

        - ‘Thread.setName’ => *note threading.Thread.name: 2da.

        - ‘thread.getName’ => *note threading.Thread.name: 2da.

        - ‘Thread.isDaemon’ => *note threading.Thread.daemon: 2d8.

        - ‘Thread.setDaemon’ => *note threading.Thread.daemon: 2d8.

     Patch by Jelle Zijlstra.

   - bpo-2135(52): Deprecate find_module() and find_loader()
     implementations in importlib and zipimport.

   - bpo-43534(53): *note turtle.textinput(): 17c5. and *note
     turtle.numinput(): 17c6. create now a transient window working on
     behalf of the canvas window.

   - bpo-43532(54): Add the ability to specify keyword-only fields to
     dataclasses.  These fields will become keyword-only arguments to
     the generated __init__.

   - bpo-43522(55): Fix problem with *note hostname_checks_common_name:
     b21.  OpenSSL does not copy hostflags from 'struct SSL_CTX' to
     'struct SSL'.

   - bpo-8978(56): Improve error message for *note tarfile.open(): e19.
     when *note lzma: 7e. / *note bz2: f. are unavailable.  Patch by
     Anthony Sottile.

   - bpo-42967(57): Allow *note bytes: 1a5. ‘separator’ argument in
     ‘urllib.parse.parse_qs’ and ‘urllib.parse.parse_qsl’ when parsing
     *note str: 3f2. query strings.  Previously, this raised a
     ‘TypeError’.

   - bpo-43296(58): Improve *note sqlite3: ba. error handling:
     ‘sqlite3_value_blob()’ errors that set ‘SQLITE_NOMEM’ now raise
     *note MemoryError: 15bc.  Patch by Erlend E. Aasland.

   - bpo-43312(59): New functions *note
     sysconfig.get_preferred_scheme(): 636. and *note
     sysconfig.get_default_scheme(): 1728. are added to query a platform
     for its preferred "user", "home", and "prefix" (default) scheme
     names.

   - bpo-43265(60): Improve *note sqlite3.Connection.backup(): b1e.
     error handling.  The error message for non-existent target database
     names is now ‘unknown database <database name>’ instead of ‘SQL
     logic error’.  Patch by Erlend E. Aasland.

   - bpo-41282(61): Install schemes in ‘distutils.command.install’ are
     now loaded from *note sysconfig: c5.

   - bpo-41282(62): ‘distutils.sysconfig’ has been merged to *note
     sysconfig: c5.

   - bpo-43176(63): Fixed processing of a dataclass that inherits from a
     frozen dataclass with no fields.  It is now correctly detected as
     an error.

   - bpo-43080(64): *note pprint: 9c. now has support for *note
     dataclasses.dataclass: 1af.  Patch by Lewis Gaul.

   - bpo-39950(65): Add ‘pathlib.Path.hardlink_to()’ method that
     supersedes ‘link_to()’.  The new method has the same argument order
     as ‘symlink_to()’.

   - bpo-42904(66): *note typing.get_type_hints(): 657. now checks the
     local namespace of a class when evaluating PEP 563(67) annotations
     inside said class.

   - bpo-42269(68): Add ‘slots’ parameter to ‘dataclasses.dataclass’
     decorator to automatically generate ‘__slots__’ for class.  Patch
     provided by Yurii Karabas.

   - bpo-39529(69): Deprecated use of *note asyncio.get_event_loop():
     2a3. without running event loop.  Emit deprecation warning for
     *note asyncio: 8. functions which implicitly create a *note Future:
     b74. or *note Task: 480. objects if there is no running event loop
     and no explicit 'loop' argument is passed: *note ensure_future():
     c1d, *note wrap_future(): 17c7, *note gather(): 5a2, *note
     shield(): a13, *note as_completed(): 190. and constructors of *note
     Future: b74, *note Task: 480, *note StreamReader: 17c8,
     ‘StreamReaderProtocol’.

   - bpo-18369(70): Certificate and PrivateKey classes were added to the
     ssl module.  Certificates and keys can now be loaded from memory
     buffer, too.

   - bpo-41486(71): Use a new output buffer management code for *note
     bz2: f. / *note lzma: 7e. / *note zlib: 119. modules, and add
     ‘.readall()’ function to ‘_compression.DecompressReader’ class.
     These bring some performance improvements.  Patch by Ma Lin.

   - bpo-31870(72): The *note ssl.get_server_certificate(): 7e0.
     function now has a 'timeout' parameter.

   - bpo-41735(73): Fix thread locks in zlib module may go wrong in rare
     case.  Patch by Ma Lin.

   - bpo-36470(74): Fix dataclasses with ‘InitVar’s and *note replace():
     15f4.  Patch by Claudiu Popa.

   - bpo-40849(75): Expose X509_V_FLAG_PARTIAL_CHAIN ssl flag

   - bpo-35114(76): *note ssl.RAND_status(): 17c9. now returns a boolean
     value (as documented) instead of ‘1’ or ‘0’.

   - bpo-39906(77): *note pathlib.Path.stat(): 7c7. and *note chmod():
     7c8. now accept a 'follow_symlinks' keyword-only argument for
     consistency with corresponding functions in the *note os: 91.
     module.

   - bpo-39899(78): *note os.path.expanduser(): 9b8. now refuses to
     guess Windows home directories if the basename of current user's
     home directory does not match their username.

     *note pathlib.Path.expanduser(): de8. and *note home(): de9. now
     consistently raise *note RuntimeError: 179. exception when a home
     directory cannot be resolved.  Previously a *note KeyError: 2fb.
     exception could be raised on Windows when the ‘"USERNAME"’
     environment variable was unset.

   - bpo-36076(79): Added SNI support to *note
     ssl.get_server_certificate(): 7e0.

   - bpo-38490(80): Covariance, Pearson's correlation, and simple linear
     regression functionality was added to statistics module.  Patch by
     Tymoteusz Wołodźko.

   - bpo-33731(81): Provide a locale.localize() function, which converts
     a normalized number string into a locale format.

   - bpo-32745(82): Fix a regression in the handling of ctypes' *note
     ctypes.c_wchar_p: 15e2. type: embedded null characters would cause
     a *note ValueError: 1e7. to be raised.  Patch by Zackery Spytz.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=44015

   (2) https://bugs.python.org/issue?@action=redirect&bpo=25478

   (3) https://bugs.python.org/issue?@action=redirect&bpo=43733

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43979

   (5) https://bugs.python.org/issue?@action=redirect&bpo=43993

   (6) https://bugs.python.org/issue?@action=redirect&bpo=43957

   (7) https://bugs.python.org/issue?@action=redirect&bpo=42904

   (8) https://bugs.python.org/issue?@action=redirect&bpo=43945

   (9) https://bugs.python.org/issue?@action=redirect&bpo=41139

   (10) https://bugs.python.org/issue?@action=redirect&bpo=43937

   (11) https://bugs.python.org/issue?@action=redirect&bpo=43930

   (12) https://bugs.python.org/issue?@action=redirect&bpo=43907

   (13) https://bugs.python.org/issue?@action=redirect&bpo=43926

   (14) https://bugs.python.org/issue?@action=redirect&bpo=43920

   (15) https://bugs.python.org/issue?@action=redirect&bpo=43607

   (16) https://bugs.python.org/issue?@action=redirect&bpo=43817

   (17) https://bugs.python.org/issue?@action=redirect&bpo=43284

   (18) https://bugs.python.org/issue?@action=redirect&bpo=42854

   (19) https://bugs.python.org/issue?@action=redirect&bpo=42333

   (20) https://bugs.python.org/issue?@action=redirect&bpo=43880

   (21) https://bugs.python.org/issue?@action=redirect&bpo=41559

   (22) https://peps.python.org/pep-0612/

   (23) https://bugs.python.org/issue?@action=redirect&bpo=43867

   (24) https://bugs.python.org/issue?@action=redirect&bpo=40443

   (25) https://bugs.python.org/issue?@action=redirect&bpo=43820

   (26) https://bugs.python.org/issue?@action=redirect&bpo=43787

   (27) https://bugs.python.org/issue?@action=redirect&bpo=43680

   (28) https://bugs.python.org/issue?@action=redirect&bpo=43680

   (29) https://bugs.python.org/issue?@action=redirect&bpo=41515

   (30) https://bugs.python.org/issue?@action=redirect&bpo=43776

   (31) https://bugs.python.org/issue?@action=redirect&bpo=42248

   (32) https://bugs.python.org/issue?@action=redirect&bpo=43744

   (33) https://bugs.python.org/issue?@action=redirect&bpo=43772

   (34) https://bugs.python.org/issue?@action=redirect&bpo=43764

   (35) https://bugs.python.org/issue?@action=redirect&bpo=43799

   (36) https://bugs.python.org/issue?@action=redirect&bpo=43478

   (37) https://bugs.python.org/issue?@action=redirect&bpo=43794

   (38) https://bugs.python.org/issue?@action=redirect&bpo=43785

   (39) https://bugs.python.org/issue?@action=redirect&bpo=43789

   (40) https://bugs.python.org/issue?@action=redirect&bpo=43788

   (41) https://bugs.python.org/issue?@action=redirect&bpo=43766

   (42) https://peps.python.org/pep-0647/

   (43) https://bugs.python.org/issue?@action=redirect&bpo=25264

   (44) https://bugs.python.org/issue?@action=redirect&bpo=43780

   (45) https://bugs.python.org/issue?@action=redirect&bpo=43731

   (46) https://bugs.python.org/issue?@action=redirect&bpo=43712

   (47) https://bugs.python.org/issue?@action=redirect&bpo=38659

   (48) https://bugs.python.org/issue?@action=redirect&bpo=43764

   (49) https://bugs.python.org/issue?@action=redirect&bpo=43752

   (50) https://bugs.python.org/issue?@action=redirect&bpo=43655

   (51) https://bugs.python.org/issue?@action=redirect&bpo=43723

   (52) https://bugs.python.org/issue?@action=redirect&bpo=2135

   (53) https://bugs.python.org/issue?@action=redirect&bpo=43534

   (54) https://bugs.python.org/issue?@action=redirect&bpo=43532

   (55) https://bugs.python.org/issue?@action=redirect&bpo=43522

   (56) https://bugs.python.org/issue?@action=redirect&bpo=8978

   (57) https://bugs.python.org/issue?@action=redirect&bpo=42967

   (58) https://bugs.python.org/issue?@action=redirect&bpo=43296

   (59) https://bugs.python.org/issue?@action=redirect&bpo=43312

   (60) https://bugs.python.org/issue?@action=redirect&bpo=43265

   (61) https://bugs.python.org/issue?@action=redirect&bpo=41282

   (62) https://bugs.python.org/issue?@action=redirect&bpo=41282

   (63) https://bugs.python.org/issue?@action=redirect&bpo=43176

   (64) https://bugs.python.org/issue?@action=redirect&bpo=43080

   (65) https://bugs.python.org/issue?@action=redirect&bpo=39950

   (66) https://bugs.python.org/issue?@action=redirect&bpo=42904

   (67) https://peps.python.org/pep-0563/

   (68) https://bugs.python.org/issue?@action=redirect&bpo=42269

   (69) https://bugs.python.org/issue?@action=redirect&bpo=39529

   (70) https://bugs.python.org/issue?@action=redirect&bpo=18369

   (71) https://bugs.python.org/issue?@action=redirect&bpo=41486

   (72) https://bugs.python.org/issue?@action=redirect&bpo=31870

   (73) https://bugs.python.org/issue?@action=redirect&bpo=41735

   (74) https://bugs.python.org/issue?@action=redirect&bpo=36470

   (75) https://bugs.python.org/issue?@action=redirect&bpo=40849

   (76) https://bugs.python.org/issue?@action=redirect&bpo=35114

   (77) https://bugs.python.org/issue?@action=redirect&bpo=39906

   (78) https://bugs.python.org/issue?@action=redirect&bpo=39899

   (79) https://bugs.python.org/issue?@action=redirect&bpo=36076

   (80) https://bugs.python.org/issue?@action=redirect&bpo=38490

   (81) https://bugs.python.org/issue?@action=redirect&bpo=33731

   (82) https://bugs.python.org/issue?@action=redirect&bpo=32745


File: python.info,  Node: Documentation<24>,  Next: Tests<27>,  Prev: Library<29>,  Up: Python 3 10 0 beta 1

1.23.30.4 Documentation
.......................

   - bpo-43987(1): Add "Annotations Best Practices" document as a new
     HOWTO.

   - bpo-43977(2): Document the new *note Py_TPFLAGS_MAPPING: 17a6. and
     *note Py_TPFLAGS_SEQUENCE: 17a7. type flags.

   - bpo-43959(3): The documentation on the PyContextVar C-API was
     clarified.

   - bpo-43938(4): Update dataclasses documentation to express that
     FrozenInstanceError is derived from AttributeError.

   - bpo-43778(5): Fix the Sphinx glossary_search extension: create the
     _static/ sub-directory if it doesn't exist.

   - bpo-43755(6): Update documentation to reflect that unparenthesized
     lambda expressions can no longer be the expression part in an ‘if’
     clause in comprehensions and generator expressions since Python
     3.9.

   - bpo-43739(7): Fixing the example code in
     Doc/extending/extending.rst to declare and initialize the pmodule
     variable to be of the right type.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43987

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43977

   (3) https://bugs.python.org/issue?@action=redirect&bpo=43959

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43938

   (5) https://bugs.python.org/issue?@action=redirect&bpo=43778

   (6) https://bugs.python.org/issue?@action=redirect&bpo=43755

   (7) https://bugs.python.org/issue?@action=redirect&bpo=43739


File: python.info,  Node: Tests<27>,  Next: Build<29>,  Prev: Documentation<24>,  Up: Python 3 10 0 beta 1

1.23.30.5 Tests
...............

   - bpo-43961(1): Fix test_logging.test_namer_rotator_inheritance() on
     Windows: use *note os.replace(): 108b. rather than *note
     os.rename(): 108a.  Patch by Victor Stinner.

   - bpo-43842(2): Fix a race condition in the SMTP test of
     test_logging.  Don't close a file descriptor (socket) from a
     different thread while asyncore.loop() is polling the file
     descriptor.  Patch by Victor Stinner.

   - bpo-43843(3): ‘test.libregrtest’ now marks a test as ENV_CHANGED
     (altered the execution environment) if a thread raises an exception
     but does not catch it.  It sets a hook on *note
     threading.excepthook(): 7ef.  Use ‘--fail-env-changed’ option to
     mark the test as failed.  Patch by Victor Stinner.

   - bpo-43811(4): Tests multiple OpenSSL versions on GitHub Actions.
     Use ccache to speed up testing.

   - bpo-43791(5): OpenSSL 3.0.0: Disable testing of legacy protocols
     TLS 1.0 and 1.1.  Tests are failing with
     TLSV1_ALERT_INTERNAL_ERROR.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43961

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43842

   (3) https://bugs.python.org/issue?@action=redirect&bpo=43843

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43811

   (5) https://bugs.python.org/issue?@action=redirect&bpo=43791


File: python.info,  Node: Build<29>,  Next: Windows<26>,  Prev: Tests<27>,  Up: Python 3 10 0 beta 1

1.23.30.6 Build
...............

   - bpo-43567(1): Improved generated code refresh
     (AST/tokens/opcodes/keywords) on Windows.

   - bpo-43669(2): Implement PEP 644(3).  Python now requires OpenSSL
     1.1.1 or newer.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43567

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43669

   (3) https://peps.python.org/pep-0644/


File: python.info,  Node: Windows<26>,  Next: macOS<21>,  Prev: Build<29>,  Up: Python 3 10 0 beta 1

1.23.30.7 Windows
.................

   - bpo-35306(1): Adds additional arguments to *note os.startfile():
     17ce. function.

   - bpo-43538(2): Avoid raising errors from *note
     pathlib.Path.exists(): 9ba. when passed an invalid filename.

   - bpo-38822(3): Fixed *note os.stat(): 448. failing on inaccessible
     directories with a trailing slash, rather than falling back to the
     parent directory's metadata.  This implicitly affected *note
     os.path.exists(): 9b2. and *note os.path.isdir(): 9b4.

   - bpo-26227(4): Fixed decoding of host names in *note
     socket.gethostbyaddr(): 17cf. and *note socket.gethostbyname_ex():
     17d0.

   - bpo-40432(5): Updated pegen regeneration script on Windows to find
     and use Python 3.8 or higher.  Prior to this, pegen regeneration
     already required 3.8 or higher, but the script may have used lower
     versions of Python.

   - bpo-43745(6): Actually updates Windows release to OpenSSL 1.1.1k.
     Earlier releases were mislabelled and actually included 1.1.1i
     again.

   - bpo-43652(7): Update Tcl and Tk to 8.6.11 in Windows installer.

   - bpo-43492(8): Upgrade Windows installer to use SQLite 3.35.5.

   - bpo-30555(9): Fix ‘WindowsConsoleIO’ errors in the presence of fd
     redirection.  Patch by Segev Finer.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35306

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43538

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38822

   (4) https://bugs.python.org/issue?@action=redirect&bpo=26227

   (5) https://bugs.python.org/issue?@action=redirect&bpo=40432

   (6) https://bugs.python.org/issue?@action=redirect&bpo=43745

   (7) https://bugs.python.org/issue?@action=redirect&bpo=43652

   (8) https://bugs.python.org/issue?@action=redirect&bpo=43492

   (9) https://bugs.python.org/issue?@action=redirect&bpo=30555


File: python.info,  Node: macOS<21>,  Next: IDLE<18>,  Prev: Windows<26>,  Up: Python 3 10 0 beta 1

1.23.30.8 macOS
...............

   - bpo-42119(1): Fix check for macOS SDK paths when building Python.
     Narrow search to match contents of SDKs, namely only files in
     ‘/System/Library’, ‘/System/IOSSupport’, and ‘/usr’ other than
     ‘/usr/local’.  Previously, anything under ‘/System’ was assumed to
     be in an SDK which causes problems with the new file system layout
     in 10.15+ where user file systems may appear to be mounted under
     ‘/System’.  Paths in ‘/Library’ were also incorrectly treated as
     SDK locations.

   - bpo-43568(2): Drop support for MACOSX_DEPLOYMENT_TARGET < 10.3

   - bpo-44009(3): Provide "python3.x-intel64" executable to allow
     reliably forcing macOS universal2 framework builds to run under
     Rosetta 2 Intel-64 emulation on Apple Silicon Macs.  This can be
     useful for testing or when universal2 wheels are not yet available.

   - bpo-43851(4): Build SQLite with ‘SQLITE_OMIT_AUTOINIT’ on macOS.
     Patch by Erlend E. Aasland.

   - bpo-43492(5): Update macOS installer to use SQLite 3.35.4.

   - bpo-42235(6): ‘Mac/BuildScript/build-installer.py’ will now use
     "-enable-optimizations" and ‘--with-lto’ when building on macOS
     10.15 or later.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42119

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43568

   (3) https://bugs.python.org/issue?@action=redirect&bpo=44009

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43851

   (5) https://bugs.python.org/issue?@action=redirect&bpo=43492

   (6) https://bugs.python.org/issue?@action=redirect&bpo=42235


File: python.info,  Node: IDLE<18>,  Next: C API<28>,  Prev: macOS<21>,  Up: Python 3 10 0 beta 1

1.23.30.9 IDLE
..............

   - bpo-37903(1): Add mouse actions to the shell sidebar.  Left click
     and optional drag selects one or more lines, as with the editor
     line number sidebar.  Right click after selecting raises a context
     menu with 'copy with prompts'.  This zips together prompts from the
     sidebar with lines from the selected text.

   - bpo-43981(2): Fix reference leak in test_sidebar and test_squeezer.
     Patches by Terry Jan Reedy and Pablo Galindo

   - bpo-37892(3): Indent IDLE Shell input with spaces instead of tabs

   - bpo-43655(4): IDLE dialog windows are now recognized as dialogs by
     window managers on macOS and X Window.

   - bpo-37903(5): IDLE's shell now shows prompts in a separate
     side-bar.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=37903

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43981

   (3) https://bugs.python.org/issue?@action=redirect&bpo=37892

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43655

   (5) https://bugs.python.org/issue?@action=redirect&bpo=37903


File: python.info,  Node: C API<28>,  Prev: IDLE<18>,  Up: Python 3 10 0 beta 1

1.23.30.10 C API
................

   - bpo-43916(1): Add a new *note Py_TPFLAGS_DISALLOW_INSTANTIATION:
     528. type flag to disallow creating type instances.  Patch by
     Victor Stinner.

   - bpo-43774(2): Remove the now unused ‘PYMALLOC_DEBUG’ macro.  Debug
     hooks on memory allocators are now installed by default if Python
     is built in debug mode (if ‘Py_DEBUG’ macro is defined).  Moreover,
     they can now be used on Python build in release mode (ex: using
     ‘PYTHONMALLOC=debug’ environment variable).

   - bpo-43962(3): _PyInterpreterState_IDIncref() now calls
     _PyInterpreterState_IDInitref() and always increments id_refcount.
     Previously, calling _xxsubinterpreters.get_current() could create
     an id_refcount inconsistency when a
     _xxsubinterpreters.InterpreterID object was deallocated.  Patch by
     Victor Stinner.

   - bpo-28254(4): Add new C-API functions to control the state of the
     garbage collector: *note PyGC_Enable(): 848, *note PyGC_Disable():
     849, *note PyGC_IsEnabled(): 84a, corresponding to the functions in
     the *note gc: 56. module.

   - bpo-43908(5): Introduce *note Py_TPFLAGS_IMMUTABLETYPE: 38d. flag
     for immutable type objects, and modify *note PyType_Ready(): 722.
     to set it for static types.  Patch by Erlend E. Aasland.

   - bpo-43795(6): *note PyMem_Calloc(): e4f. is now available in the
     limited C API (‘Py_LIMITED_API’).

   - bpo-43868(7): *note PyOS_ReadlineFunctionPointer(): 52c. is no
     longer exported by limited C API headers and by ‘python3.dll’ on
     Windows.  Like any function that takes ‘FILE*’, it is not part of
     the stable ABI.

   - bpo-43795(8): Stable ABI and limited API definitions are generated
     from a central manifest ( PEP 652(9)).

   - bpo-43753(10): Add the *note Py_Is(x, y): 844. function to test if
     the 'x' object is the 'y' object, the same as ‘x is y’ in Python.
     Add also the *note Py_IsNone(): 845, *note Py_IsTrue(): 846, *note
     Py_IsFalse(): 847. functions to test if an object is, respectively,
     the ‘None’ singleton, the ‘True’ singleton or the ‘False’
     singleton.  Patch by Victor Stinner.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43916

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43774

   (3) https://bugs.python.org/issue?@action=redirect&bpo=43962

   (4) https://bugs.python.org/issue?@action=redirect&bpo=28254

   (5) https://bugs.python.org/issue?@action=redirect&bpo=43908

   (6) https://bugs.python.org/issue?@action=redirect&bpo=43795

   (7) https://bugs.python.org/issue?@action=redirect&bpo=43868

   (8) https://bugs.python.org/issue?@action=redirect&bpo=43795

   (9) https://peps.python.org/pep-0652/

   (10) https://bugs.python.org/issue?@action=redirect&bpo=43753


File: python.info,  Node: Python 3 10 0 alpha 7,  Next: Python 3 10 0 alpha 6,  Prev: Python 3 10 0 beta 1,  Up: Changelog（更動日誌）

1.23.31 Python 3.10.0 alpha 7
-----------------------------

'Release date: 2021-04-05'

* Menu:

* Security: Security<18>.
* Core and Builtins: Core and Builtins<31>.
* Library: Library<30>.
* Documentation: Documentation<25>.
* Tests: Tests<28>.
* Build: Build<30>.
* Windows: Windows<27>.
* IDLE: IDLE<19>.
* C API: C API<29>.


File: python.info,  Node: Security<18>,  Next: Core and Builtins<31>,  Up: Python 3 10 0 alpha 7

1.23.31.1 Security
..................

   - bpo-42988(1): CVE-2021-3426(2): Remove the ‘getfile’ feature of the
     *note pydoc: a3. module which could be abused to read arbitrary
     files on the disk (directory traversal vulnerability).  Moreover,
     even source code of Python modules can contain sensitive data like
     passwords.  Vulnerability reported by David Schwörer.

   - bpo-43285(3): *note ftplib: 54. no longer trusts the IP address
     value returned from the server in response to the PASV command by
     default.  This prevents a malicious FTP server from using the
     response to probe IPv4 address and port combinations on the client
     network.

     Code that requires the former vulnerable behavior may set a
     ‘trust_server_pasv_ipv4_address’ attribute on their *note
     ftplib.FTP: 89f. instances to ‘True’ to re-enable it.

   - bpo-43439(4): Add audit hooks for *note gc.get_objects(): 7a7,
     *note gc.get_referrers(): 7a8. and *note gc.get_referents(): 7a9.
     Patch by Pablo Galindo.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42988

   (2) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3426

   (3) https://bugs.python.org/issue?@action=redirect&bpo=43285

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43439


File: python.info,  Node: Core and Builtins<31>,  Next: Library<30>,  Prev: Security<18>,  Up: Python 3 10 0 alpha 7

1.23.31.2 Core and Builtins
...........................

   - bpo-27129(1): Update CPython bytecode magic number.

   - bpo-43672(2): Raise ImportWarning when calling find_loader().

   - bpo-43660(3): Fix crash that happens when replacing ‘sys.stderr’
     with a callable that can remove the object while an exception is
     being printed.  Patch by Pablo Galindo.

   - bpo-27129(4): The bytecode interpreter uses instruction, rather
     byte, offsets internally.  This reduces the number of EXTENDED_ARG
     instructions needed and streamlines instruction dispatch a bit.

   - bpo-40645(5): Fix reference leak in the ‘_hashopenssl’ extension.
     Patch by Pablo Galindo.

   - bpo-42134(6): Calls to find_module() by the import system now raise
     ImportWarning.

   - bpo-41064(7): Improve the syntax error for invalid usage of double
     starred elements ('**') in f-strings.  Patch by Pablo Galindo.

   - bpo-43575(8): Speed up calls to ‘map()’ by using the PEP 590(9)
     ‘vectorcall’ calling convention.  Patch by Donghee Na.

   - bpo-42137(10): The import system now prefers using ‘__spec__’ for
     ‘ModuleType.__repr__’ over ‘module_repr()’.

   - bpo-43452(11): Added micro-optimizations to ‘_PyType_Lookup()’ to
     improve cache lookup performance in the common case of cache hits.

   - bpo-43555(12): Report the column offset for *note SyntaxError: 173.
     for invalid line continuation characters.  Patch by Pablo Galindo.

   - bpo-43517(13): Fix misdetection of circular imports when using
     ‘from pkg.mod import attr’, which caused false positives in
     non-trivial multi-threaded code.

   - bpo-43497(14): Emit SyntaxWarnings for assertions with tuple
     constants, this is a regression introduced in python3.7

   - bpo-39316(15): Tracing now has correct line numbers for attribute
     accesses when the attribute is on a different line from the object.
     Improves debugging and profiling for multi-line method chains.

   - bpo-35883(16): Python no longer fails at startup with a fatal error
     if a command line argument contains an invalid Unicode character.
     The *note Py_DecodeLocale(): b6e. function now escapes byte
     sequences which would be decoded as Unicode characters outside the
     [U+0000; U+10ffff] range.

   - bpo-43410(17): Fix a bug that was causing the parser to crash when
     emitting syntax errors when reading input from stdin.  Patch by
     Pablo Galindo

   - bpo-43406(18): Fix a possible race condition where
     ‘PyErr_CheckSignals’ tries to execute a non-Python signal handler.

   - bpo-42128(19): Add ‘__match_args__’ to *note struct sequence
     objects: 1157.  Patch by Pablo Galindo.

   - bpo-43390(20): CPython now sets the ‘SA_ONSTACK’ flag in
     ‘PyOS_setsig’ for the VM's default signal handlers.  This is
     friendlier to other in-process code that an extension module or
     embedding use could pull in (such as Golang's cgo) where tiny
     thread stacks are the norm and ‘sigaltstack()’ has been used to
     provide for signal handlers.  This is a no-op change for the vast
     majority of processes that don't use sigaltstack.

   - bpo-43287(21): Speed up calls to ‘filter()’ by using the PEP
     590(22) ‘vectorcall’ calling convention.  Patch by Donghee Na.

   - bpo-37448(23): Add a radix tree based memory map to track in-use
     obmalloc arenas.  Use to replace the old implementation of
     address_in_range().  The radix tree approach makes it easy to
     increase pool sizes beyond the OS page size.  Boosting the pool and
     arena size allows obmalloc to handle a significantly higher
     percentage of requests from its ultra-fast paths.

     It also has the advantage of eliminating the memory unsanitary
     behavior of the previous address_in_range().  The old
     address_in_range() was marked with the annotations
     _Py_NO_SANITIZE_ADDRESS, _Py_NO_SANITIZE_THREAD, and
     _Py_NO_SANITIZE_MEMORY. Those annotations are no longer needed.

     To disable the radix tree map, set a preprocessor flag as follows:
     ‘-DWITH_PYMALLOC_RADIX_TREE=0’.

     Co-authored-by: Tim Peters <<tim.peters@gmail.com>>

   - bpo-29988(24): Only handle asynchronous exceptions and requests to
     drop the GIL when returning from a call or on the back edges of
     loops.  Makes sure that *note __exit__(): 1293. is always called in
     with statements, even for interrupts.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27129

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43672

   (3) https://bugs.python.org/issue?@action=redirect&bpo=43660

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27129

   (5) https://bugs.python.org/issue?@action=redirect&bpo=40645

   (6) https://bugs.python.org/issue?@action=redirect&bpo=42134

   (7) https://bugs.python.org/issue?@action=redirect&bpo=41064

   (8) https://bugs.python.org/issue?@action=redirect&bpo=43575

   (9) https://peps.python.org/pep-0590/

   (10) https://bugs.python.org/issue?@action=redirect&bpo=42137

   (11) https://bugs.python.org/issue?@action=redirect&bpo=43452

   (12) https://bugs.python.org/issue?@action=redirect&bpo=43555

   (13) https://bugs.python.org/issue?@action=redirect&bpo=43517

   (14) https://bugs.python.org/issue?@action=redirect&bpo=43497

   (15) https://bugs.python.org/issue?@action=redirect&bpo=39316

   (16) https://bugs.python.org/issue?@action=redirect&bpo=35883

   (17) https://bugs.python.org/issue?@action=redirect&bpo=43410

   (18) https://bugs.python.org/issue?@action=redirect&bpo=43406

   (19) https://bugs.python.org/issue?@action=redirect&bpo=42128

   (20) https://bugs.python.org/issue?@action=redirect&bpo=43390

   (21) https://bugs.python.org/issue?@action=redirect&bpo=43287

   (22) https://peps.python.org/pep-0590/

   (23) https://bugs.python.org/issue?@action=redirect&bpo=37448

   (24) https://bugs.python.org/issue?@action=redirect&bpo=29988


File: python.info,  Node: Library<30>,  Next: Documentation<25>,  Prev: Core and Builtins<31>,  Up: Python 3 10 0 alpha 7

1.23.31.3 Library
.................

   - bpo-43720(1): Document various stdlib deprecations in imp, pkgutil,
     and importlib.util for removal in Python 3.12.

   - bpo-43433(2): *note xmlrpc.client.ServerProxy: 9fa. no longer
     ignores query and fragment in the URL of the server.

   - bpo-31956(3): The *note index(): 784. method of *note array.array:
     186. now has optional 'start' and 'stop' parameters.

   - bpo-40066(4): Enum: adjust ‘repr()’ to show only enum and member
     name (not value, nor angle brackets) and ‘str()’ to show only
     member name.  Update and improve documentation to match.

   - bpo-42136(5): Deprecate all module_repr() methods found in
     importlib as their use is being phased out by Python 3.12.

   - bpo-35930(6): Raising an exception raised in a "future" instance
     will create reference cycles.

   - bpo-41369(7): Finish updating the vendored libmpdec to version
     2.5.1.  Patch by Stefan Krah.

   - bpo-43422(8): Revert the _decimal C API which was added in
     bpo-41324(9).

   - bpo-43577(10): Fix deadlock when using *note ssl.SSLContext: 276.
     debug callback with *note ssl.SSLContext.sni_callback(): 17d8.

   - bpo-43571(11): It's now possible to create MPTCP sockets with
     IPPROTO_MPTCP

   - bpo-43542(12): ‘image/heic’ and ‘image/heif’ were added to *note
     mimetypes: 82.

   - bpo-40645(13): The *note hmac: 60. module now uses OpenSSL's HMAC
     implementation when digestmod argument is a hash name or builtin
     hash function.

   - bpo-43510(14): Implement PEP 597(15): Add ‘EncodingWarning’
     warning, ‘-X warn_default_encoding’ option, *note
     PYTHONWARNDEFAULTENCODING: 760. environment variable and
     ‘encoding="locale"’ argument value.

   - bpo-43521(16): ‘ast.unparse’ can now render NaNs and empty sets.

   - bpo-42914(17): *note pprint.pprint(): 7cc. gains a new boolean
     ‘underscore_numbers’ optional argument to emit integers with
     thousands separated by an underscore character for improved
     readability (for example ‘1_000_000’ instead of ‘1000000’).

   - bpo-41361(18): *note rotate(): 17d9. calls are now slightly faster
     due to faster argument parsing.

   - bpo-43423(19): ‘subprocess.communicate()’ no longer raises an
     IndexError when there is an empty stdout or stderr IO buffer during
     a timeout on Windows.

   - bpo-27820(20): Fixed long-standing bug of smtplib.SMTP where doing
     AUTH LOGIN with initial_response_ok=False will fail.

     The cause is that SMTP.auth_login _always_ returns a password if
     provided with a challenge string, thus non-compliant with the
     standard for AUTH LOGIN.

     Also fixes bug with the test for smtpd.

   - bpo-43445(21): Add frozen modules to *note sys.stdlib_module_names:
     7e5.  For example, add ‘"_frozen_importlib"’ and
     ‘"_frozen_importlib_external"’ names.

   - bpo-43245(22): Add keyword arguments support to
     ‘ChainMap.new_child()’.

   - bpo-29982(23): Add optional parameter 'ignore_cleanup_errors' to
     *note tempfile.TemporaryDirectory(): 11cc. and allow multiple
     ‘cleanup()’ attempts.  Contributed by C.A.M. Gerlach.

   - bpo-43428(24): Include changes from importlib_metadata 3.7(25):

     Performance enhancements to distribution discovery.

     ‘entry_points’ only returns unique distributions.

     Introduces new ‘EntryPoints’ object for containing a set of entry
     points with convenience methods for selecting entry points by group
     or name.  ‘entry_points’ now returns this object if selection
     parameters are supplied but continues to return a dict object for
     compatibility.  Users are encouraged to rely on the selection
     interface.  The dict object result is likely to be deprecated in
     the future.

     Added packages_distributions function to return a mapping of
     packages to the distributions that provide them.

   - bpo-43332(26): Improves the networking efficiency of *note
     http.client: 65. when using a proxy via ‘set_tunnel()’.  Fewer
     small send calls are made during connection setup.

   - bpo-43420(27): Improve performance of *note fractions.Fraction:
     1c7. arithmetics for large components.  Contributed by Sergey B.
     Kirpichev.

   - bpo-43356(28): Allow passing a signal number to
     ‘_thread.interrupt_main()’.

   - bpo-43399(29): Fix ‘ElementTree.extend’ not working on iterators
     when using the Python implementation

   - bpo-43369(30): Improve *note sqlite3: ba. error handling: If
     ‘sqlite3_column_text()’ and ‘sqlite3_column_blob()’ set
     ‘SQLITE_NOMEM’, *note MemoryError: 15bc. is now raised.  Patch by
     Erlend E. Aasland.

   - bpo-43368(31): Fix a regression introduced in PR 24562, where an
     empty bytestring was fetched as ‘None’ instead of ‘b''’ in *note
     sqlite3: ba.  Patch by Mariusz Felisiak.

   - bpo-41282(32): Fixed stacklevel of ‘DeprecationWarning’ emitted
     from ‘import distutils’.

   - bpo-42129(33): ‘importlib.resources’ now honors namespace packages,
     merging resources from each location in the namespace as introduced
     in ‘importlib_resources’ 3.2 and including incidental changes
     through 5.0.3.

   - bpo-43295(34): *note datetime.datetime.strptime(): 14fe. now raises
     ‘ValueError’ instead of ‘IndexError’ when matching ‘'z'’ with the
     ‘%z’ format specifier.

   - bpo-43125(35): Return empty string if base64mime.body_encode
     receive empty bytes

   - bpo-43084(36): *note curses.window.enclose(): 17da. returns now
     ‘True’ or ‘False’ (as was documented) instead of ‘1’ or ‘0’.

   - bpo-42994(37): Add MIME types for opus, AAC, 3gpp and 3gpp2

   - bpo-14678(38): Add an invalidate_caches() method to the
     zipimport.zipimporter class to support
     importlib.invalidate_caches().  Patch by Desmond Cheong.

   - bpo-42782(39): Fail fast in *note shutil.move(): 9ff. to avoid
     creating destination directories on failure.

   - bpo-40066(40): Enum's ‘repr()’ and ‘str()’ have changed: ‘repr()’
     is now 'EnumClass.MemberName' and ‘str()’ is 'MemberName'.
     Additionally, stdlib Enum's whose contents are available as module
     attributes, such as ‘RegexFlag.IGNORECASE’, have their ‘repr()’ as
     'module.name', e.g.  ‘re.IGNORECASE’.

   - bpo-26053(41): Fixed bug where the *note pdb: 94. interactive run
     command echoed the args from the shell command line, even if those
     have been overridden at the pdb prompt.

   - bpo-24160(42): Fixed bug where breakpoints did not persist across
     multiple debugger sessions in *note pdb: 94.'s interactive mode.

   - bpo-40701(43): When the *note tempfile.tempdir: 17db. global
     variable is set to a value of type bytes, it is now handled
     consistently.  Previously exceptions could be raised from some
     tempfile APIs when the directory did not already exist in this
     situation.  Also ensures that the *note tempfile.gettempdir():
     17dc. and *note tempfile.gettempdirb(): 17dd. functions 'always'
     return ‘str’ and ‘bytes’ respectively.

   - bpo-39342(44): Expose ‘X509_V_FLAG_ALLOW_PROXY_CERTS’ as *note
     VERIFY_ALLOW_PROXY_CERTS: 17de. to allow proxy certificate
     validation as explained in
     ‘https://www.openssl.org/docs/man1.1.1/man7/proxy-certificates.html’.

   - bpo-31861(45): Add builtins.aiter and builtins.anext.  Patch by
     Joshua Bronson (@jab), Daniel Pope (@lordmauve), and Justin Wang
     (@justin39).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43720

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43433

   (3) https://bugs.python.org/issue?@action=redirect&bpo=31956

   (4) https://bugs.python.org/issue?@action=redirect&bpo=40066

   (5) https://bugs.python.org/issue?@action=redirect&bpo=42136

   (6) https://bugs.python.org/issue?@action=redirect&bpo=35930

   (7) https://bugs.python.org/issue?@action=redirect&bpo=41369

   (8) https://bugs.python.org/issue?@action=redirect&bpo=43422

   (9) https://bugs.python.org/issue?@action=redirect&bpo=41324

   (10) https://bugs.python.org/issue?@action=redirect&bpo=43577

   (11) https://bugs.python.org/issue?@action=redirect&bpo=43571

   (12) https://bugs.python.org/issue?@action=redirect&bpo=43542

   (13) https://bugs.python.org/issue?@action=redirect&bpo=40645

   (14) https://bugs.python.org/issue?@action=redirect&bpo=43510

   (15) https://peps.python.org/pep-0597/

   (16) https://bugs.python.org/issue?@action=redirect&bpo=43521

   (17) https://bugs.python.org/issue?@action=redirect&bpo=42914

   (18) https://bugs.python.org/issue?@action=redirect&bpo=41361

   (19) https://bugs.python.org/issue?@action=redirect&bpo=43423

   (20) https://bugs.python.org/issue?@action=redirect&bpo=27820

   (21) https://bugs.python.org/issue?@action=redirect&bpo=43445

   (22) https://bugs.python.org/issue?@action=redirect&bpo=43245

   (23) https://bugs.python.org/issue?@action=redirect&bpo=29982

   (24) https://bugs.python.org/issue?@action=redirect&bpo=43428

   (25) 
https://importlib-metadata.readthedocs.io/en/latest/history.html#v3-7-0

   (26) https://bugs.python.org/issue?@action=redirect&bpo=43332

   (27) https://bugs.python.org/issue?@action=redirect&bpo=43420

   (28) https://bugs.python.org/issue?@action=redirect&bpo=43356

   (29) https://bugs.python.org/issue?@action=redirect&bpo=43399

   (30) https://bugs.python.org/issue?@action=redirect&bpo=43369

   (31) https://bugs.python.org/issue?@action=redirect&bpo=43368

   (32) https://bugs.python.org/issue?@action=redirect&bpo=41282

   (33) https://bugs.python.org/issue?@action=redirect&bpo=42129

   (34) https://bugs.python.org/issue?@action=redirect&bpo=43295

   (35) https://bugs.python.org/issue?@action=redirect&bpo=43125

   (36) https://bugs.python.org/issue?@action=redirect&bpo=43084

   (37) https://bugs.python.org/issue?@action=redirect&bpo=42994

   (38) https://bugs.python.org/issue?@action=redirect&bpo=14678

   (39) https://bugs.python.org/issue?@action=redirect&bpo=42782

   (40) https://bugs.python.org/issue?@action=redirect&bpo=40066

   (41) https://bugs.python.org/issue?@action=redirect&bpo=26053

   (42) https://bugs.python.org/issue?@action=redirect&bpo=24160

   (43) https://bugs.python.org/issue?@action=redirect&bpo=40701

   (44) https://bugs.python.org/issue?@action=redirect&bpo=39342

   (45) https://bugs.python.org/issue?@action=redirect&bpo=31861


File: python.info,  Node: Documentation<25>,  Next: Tests<28>,  Prev: Library<30>,  Up: Python 3 10 0 alpha 7

1.23.31.4 Documentation
.......................

   - bpo-43199(1): Answer "Why is there no goto?"  in the Design and
     History FAQ.

   - bpo-43407(2): Clarified that a result from *note time.monotonic():
     238, *note time.perf_counter(): a2b, *note time.process_time():
     a2c, or *note time.thread_time(): 8da. can be compared with the
     result from any following call to the same function - not just the
     next immediate call.

   - bpo-43354(3): Fix type documentation for ‘Fault.faultCode’; the
     type has to be ‘int’ instead of ‘str’.

   - bpo-41933(4): Clarified wording of s * n in the Common Sequence
     Operations

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43199

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43407

   (3) https://bugs.python.org/issue?@action=redirect&bpo=43354

   (4) https://bugs.python.org/issue?@action=redirect&bpo=41933


File: python.info,  Node: Tests<28>,  Next: Build<30>,  Prev: Documentation<25>,  Up: Python 3 10 0 alpha 7

1.23.31.5 Tests
...............

   - bpo-37945(1): Fix test_getsetlocale_issue1813() of test_locale:
     skip the test if ‘setlocale()’ fails.  Patch by Victor Stinner.

   - bpo-41561(2): Add workaround for Ubuntu's custom OpenSSL security
     level policy.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=37945

   (2) https://bugs.python.org/issue?@action=redirect&bpo=41561


File: python.info,  Node: Build<30>,  Next: Windows<27>,  Prev: Tests<28>,  Up: Python 3 10 0 alpha 7

1.23.31.6 Build
...............

   - bpo-43179(1): Introduce and correctly use ALIGNOF_X in place of
     SIZEOF_X for alignment-related code in optimized string routines.
     Patch by Jessica Clarke.

   - bpo-43631(2): Update macOS, Windows, and CI to OpenSSL 1.1.1k.

   - bpo-43617(3): Improve configure.ac: Check for presence of
     autoconf-archive package and remove our copies of M4 macros.

   - bpo-43466(4): The ‘configure’ script now supports
     ‘--with-openssl-rpath’ option.

   - bpo-43372(5): Use ‘_freeze_importlib’ to generate code for the
     ‘__hello__’ module.  This approach ensures the code matches the
     interpreter version.  Previously, PYTHON_FOR_REGEN was used to
     generate the code, which might be wrong.  The marshal format for
     code objects has changed with bpo-42246(6), commit 877df851.
     Update the code and the expected code sizes in ctypes
     test_frozentable.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43179

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43631

   (3) https://bugs.python.org/issue?@action=redirect&bpo=43617

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43466

   (5) https://bugs.python.org/issue?@action=redirect&bpo=43372

   (6) https://bugs.python.org/issue?@action=redirect&bpo=42246


File: python.info,  Node: Windows<27>,  Next: IDLE<19>,  Prev: Build<30>,  Up: Python 3 10 0 alpha 7

1.23.31.7 Windows
.................

   - bpo-43440(1): Build *note sqlite3: ba. with the ‘R*Tree’ module
     enabled.  Patch by Erlend E. Aasland.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43440


File: python.info,  Node: IDLE<19>,  Next: C API<29>,  Prev: Windows<27>,  Up: Python 3 10 0 alpha 7

1.23.31.8 IDLE
..............

   - bpo-42225(1): Document that IDLE can fail on Unix either from
     misconfigured IP masquerade rules or failure displaying complex
     colored (non-ascii) characters.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42225


File: python.info,  Node: C API<29>,  Prev: IDLE<19>,  Up: Python 3 10 0 alpha 7

1.23.31.9 C API
...............

   - bpo-43688(1): The limited C API is now supported if Python is built
     in debug mode (if the ‘Py_DEBUG’ macro is defined).  In the limited
     C API, the *note Py_INCREF(): 514. and *note Py_DECREF(): 515.
     functions are now implemented as opaque function calls, rather than
     accessing directly the *note PyObject.ob_refcnt: 843. member, if
     Python is built in debug mode and the ‘Py_LIMITED_API’ macro
     targets Python 3.10 or newer.  It became possible to support the
     limited C API in debug mode because the *note PyObject: 311.
     structure is the same in release and debug mode since Python 3.8
     (see bpo-36465(2)).

     The limited C API is still not supported in the ‘--with-trace-refs’
     special build (‘Py_TRACE_REFS’ macro).

     Patch by Victor Stinner.

   - bpo-43244(3): Remove the ‘pyarena.h’ header file with functions:

        * ‘PyArena_New()’

        * ‘PyArena_Free()’

        * ‘PyArena_Malloc()’

        * ‘PyArena_AddPyObject()’

     These functions were undocumented, excluded from the limited C API,
     and were only used internally by the compiler.  Patch by Victor
     Stinner.

   - bpo-43244(4): Remove the compiler and parser functions using
     ‘struct _mod’ type, because the public AST C API was removed:

        * ‘PyAST_Compile()’

        * ‘PyAST_CompileEx()’

        * ‘PyAST_CompileObject()’

        * ‘PyFuture_FromAST()’

        * ‘PyFuture_FromASTObject()’

        * ‘PyParser_ASTFromFile()’

        * ‘PyParser_ASTFromFileObject()’

        * ‘PyParser_ASTFromFilename()’

        * ‘PyParser_ASTFromString()’

        * ‘PyParser_ASTFromStringObject()’

     These functions were undocumented and excluded from the limited C
     API. Patch by Victor Stinner.

   - bpo-43244(5): Remove ‘ast.h’, ‘asdl.h’, and ‘Python-ast.h’ header
     files.  These functions were undocumented and excluded from the
     limited C API. Most names defined by these header files were not
     prefixed by ‘Py’ and so could create names conflicts.  For example,
     ‘Python-ast.h’ defined a ‘Yield’ macro which was conflict with the
     ‘Yield’ name used by the Windows ‘<winbase.h>’ header.  Use the
     Python *note ast: 7. module instead.  Patch by Victor Stinner.

   - bpo-43541(6): Fix a ‘PyEval_EvalCodeEx()’ regression: fix reference
     counting on builtins.  Patch by Victor Stinner.

   - bpo-43244(7): Remove the ‘symtable.h’ header file and the
     undocumented functions:

        * ‘PyST_GetScope()’

        * ‘PySymtable_Build()’

        * ‘PySymtable_BuildObject()’

        * ‘PySymtable_Free()’

        * ‘Py_SymtableString()’

        * ‘Py_SymtableStringObject()’

     The ‘Py_SymtableString()’ function was part the stable ABI by
     mistake but it could not be used, because the ‘symtable.h’ header
     file was excluded from the limited C API.

     The Python *note symtable: c2. module remains available and is
     unchanged.

     Patch by Victor Stinner.

   - bpo-43244(8): Remove the ‘PyAST_Validate()’ function.  It is no
     longer possible to build a AST object (‘mod_ty’ type) with the
     public C API. The function was already excluded from the limited C
     API ( PEP 384(9)).  Patch by Victor Stinner.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43688

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36465

   (3) https://bugs.python.org/issue?@action=redirect&bpo=43244

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43244

   (5) https://bugs.python.org/issue?@action=redirect&bpo=43244

   (6) https://bugs.python.org/issue?@action=redirect&bpo=43541

   (7) https://bugs.python.org/issue?@action=redirect&bpo=43244

   (8) https://bugs.python.org/issue?@action=redirect&bpo=43244

   (9) https://peps.python.org/pep-0384/


File: python.info,  Node: Python 3 10 0 alpha 6,  Next: Python 3 10 0 alpha 5,  Prev: Python 3 10 0 alpha 7,  Up: Changelog（更動日誌）

1.23.32 Python 3.10.0 alpha 6
-----------------------------

'Release date: 2021-03-01'

* Menu:

* Security: Security<19>.
* Core and Builtins: Core and Builtins<32>.
* Library: Library<31>.
* Documentation: Documentation<26>.
* Tests: Tests<29>.
* Build: Build<31>.
* Windows: Windows<28>.
* macOS: macOS<22>.
* IDLE: IDLE<20>.
* C API: C API<30>.


File: python.info,  Node: Security<19>,  Next: Core and Builtins<32>,  Up: Python 3 10 0 alpha 6

1.23.32.1 Security
..................

   - bpo-42967(1): Fix web cache poisoning vulnerability by defaulting
     the query args separator to ‘&’, and allowing the user to choose a
     custom separator.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42967


File: python.info,  Node: Core and Builtins<32>,  Next: Library<31>,  Prev: Security<19>,  Up: Python 3 10 0 alpha 6

1.23.32.2 Core and Builtins
...........................

   - bpo-43321(1): Fix ‘SystemError’ raised when ‘PyArg_Parse*()’ is
     used with ‘#’ but without ‘PY_SSIZE_T_CLEAN’ defined.

   - bpo-36346(2): ‘PyArg_Parse*()’ functions now emits
     ‘DeprecationWarning’ when ‘u’ or ‘Z’ format is used.  See PEP
     623(3) for detail.

   - bpo-43277(4): Add a new *note PySet_CheckExact(): 841. function to
     the C-API to check if an object is an instance of *note set: 57d.
     but not an instance of a subtype.  Patch by Pablo Galindo.

   - bpo-42990(5): The *note types.FunctionType: 827. constructor now
     inherits the current builtins if the 'globals' dictionary has no
     ‘"__builtins__"’ key, rather than using ‘{"None": None}’ as
     builtins: same behavior as *note eval(): 163. and *note exec():
     162. functions.  Defining a function with ‘def function(...): ...’
     in Python is not affected, globals cannot be overridden with this
     syntax: it also inherits the current builtins.  Patch by Victor
     Stinner.

   - bpo-42990(6): Functions have a new ‘__builtins__’ attribute which
     is used to look for builtin symbols when a function is executed,
     instead of looking into ‘__globals__['__builtins__']’.  Patch by
     Mark Shannon and Victor Stinner.

   - bpo-43149(7): Improve the error message in the parser for exception
     groups without parentheses.  Patch by Pablo Galindo.

   - bpo-43121(8): Fixed an incorrect *note SyntaxError: 173. message
     for missing comma in literals.  Patch by Pablo Galindo.

   - bpo-42819(9): *note readline: a8.: Explicitly disable bracketed
     paste in the interactive interpreter, even if it's set in the
     inputrc, is enabled by default (eg GNU Readline 8.1), or a user
     calls ‘readline.read_init_file()’.  The Python REPL has not
     implemented bracketed paste support.  Also, bracketed mode writes
     the ‘"\x1b[?2004h"’ escape sequence into stdout which causes test
     failures in applications that don't support it.  It can still be
     explicitly enabled by calling ‘readline.parse_and_bind("set
     enable-bracketed-paste on")’.  Patch by Dustin Rodrigues.

   - bpo-42808(10): Simple calls to ‘type(object)’ are now faster due to
     the ‘vectorcall’ calling convention.  Patch by Dennis Sweeney.

   - bpo-42217(11): Make the compiler merges same co_code and
     co_linetable objects in a module like already did for co_consts.

   - bpo-41972(12): Substring search functions such as ‘str1 in str2’
     and ‘str2.find(str1)’ now sometimes use the "Two-Way" string
     comparison algorithm to avoid quadratic behavior on long strings.

   - bpo-42128(13): Implement PEP 634(14) (structural pattern matching).
     Patch by Brandt Bucher.

   - bpo-40692(15): In the *note concurrent.futures.ProcessPoolExecutor:
     893, validate that ‘multiprocess.synchronize()’ is available on a
     given platform and rely on that check in the *note
     concurrent.futures: 1a. test suite so we can run tests that are
     unrelated to ‘ProcessPoolExecutor’ on those platforms.

   - bpo-38302(16): If *note object.__ipow__(): 775. returns *note
     NotImplemented: 776, the operator will correctly fall back to *note
     object.__pow__(): 777. and *note object.__rpow__(): 778. as
     expected.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43321

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36346

   (3) https://peps.python.org/pep-0623/

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43277

   (5) https://bugs.python.org/issue?@action=redirect&bpo=42990

   (6) https://bugs.python.org/issue?@action=redirect&bpo=42990

   (7) https://bugs.python.org/issue?@action=redirect&bpo=43149

   (8) https://bugs.python.org/issue?@action=redirect&bpo=43121

   (9) https://bugs.python.org/issue?@action=redirect&bpo=42819

   (10) https://bugs.python.org/issue?@action=redirect&bpo=42808

   (11) https://bugs.python.org/issue?@action=redirect&bpo=42217

   (12) https://bugs.python.org/issue?@action=redirect&bpo=41972

   (13) https://bugs.python.org/issue?@action=redirect&bpo=42128

   (14) https://peps.python.org/pep-0634/

   (15) https://bugs.python.org/issue?@action=redirect&bpo=40692

   (16) https://bugs.python.org/issue?@action=redirect&bpo=38302


File: python.info,  Node: Library<31>,  Next: Documentation<26>,  Prev: Core and Builtins<32>,  Up: Python 3 10 0 alpha 6

1.23.32.3 Library
.................

   - bpo-43316(1): The ‘python -m gzip’ command line application now
     properly fails when detecting an unsupported extension.  It exits
     with a non-zero exit code and prints an error message to stderr.

   - bpo-43317(2): Set the chunk size for the ‘gzip’ module main
     function to io.DEFAULT_BUFFER_SIZE. This is slightly faster than
     the 1024 bytes constant that was used previously.

   - bpo-43146(3): Handle None in single-arg versions of *note
     print_exception(): 7f3. and *note format_exception(): 7f1.

   - bpo-43260(4): Fix TextIOWrapper can not flush internal buffer
     forever after very large text is written.

   - bpo-43258(5): Prevent needless allocation of *note sqlite3: ba.
     aggregate function context when no rows match an aggregate query.
     Patch by Erlend E. Aasland.

   - bpo-43251(6): Improve *note sqlite3: ba. error handling:
     ‘sqlite3_column_name()’ failures now result in *note MemoryError:
     15bc.  Patch by Erlend E. Aasland.

   - bpo-40956(7): Fix segfault in *note sqlite3.Connection.backup():
     b1e. if no argument was provided.  The regression was introduced by
     PR 23838.  Patch by Erlend E. Aasland.

   - bpo-43172(8): The readline module now passes its tests when built
     directly against libedit.  Existing irreconcilable API differences
     remain in *note readline.get_begidx(): 17e9. and *note
     readline.get_endidx(): 17ea. behavior based on libreadline vs
     libedit use.

   - bpo-43163(9): Fix a bug in *note codeop: 15. that was causing it to
     not ask for more input when multi-line snippets have unclosed
     parentheses.  Patch by Pablo Galindo

   - bpo-43162(10): deprecate unsupported ability to access enum members
     as attributes of other enum members

   - bpo-43146(11): Fix recent regression in None argument handling in
     *note traceback: e7. module functions.

   - bpo-43102(12): The namedtuple __new__ method had its __builtins__
     set to None instead of an actual dictionary.  This created problems
     for introspection tools.

   - bpo-43106(13): Added *note O_EVTONLY: 7be, *note O_FSYNC: 7bf,
     *note O_SYMLINK: 7c0. and *note O_NOFOLLOW_ANY: 7c1. for macOS.
     Patch by Donghee Na.

   - bpo-42960(14): Adds *note resource.RLIMIT_KQUEUES: 17eb. constant
     from FreeBSD to the *note resource: aa. module.

   - bpo-42151(15): Make the pure Python implementation of *note
     xml.etree.ElementTree: 10c. behave the same as the C implementation
     (‘_elementree’) regarding default attribute values (by not setting
     ‘specified_attributes=1’).

   - bpo-29753(16): In ctypes, now packed bitfields are calculated
     properly and the first item of packed bitfields is now shrank
     correctly.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43316

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43317

   (3) https://bugs.python.org/issue?@action=redirect&bpo=43146

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43260

   (5) https://bugs.python.org/issue?@action=redirect&bpo=43258

   (6) https://bugs.python.org/issue?@action=redirect&bpo=43251

   (7) https://bugs.python.org/issue?@action=redirect&bpo=40956

   (8) https://bugs.python.org/issue?@action=redirect&bpo=43172

   (9) https://bugs.python.org/issue?@action=redirect&bpo=43163

   (10) https://bugs.python.org/issue?@action=redirect&bpo=43162

   (11) https://bugs.python.org/issue?@action=redirect&bpo=43146

   (12) https://bugs.python.org/issue?@action=redirect&bpo=43102

   (13) https://bugs.python.org/issue?@action=redirect&bpo=43106

   (14) https://bugs.python.org/issue?@action=redirect&bpo=42960

   (15) https://bugs.python.org/issue?@action=redirect&bpo=42151

   (16) https://bugs.python.org/issue?@action=redirect&bpo=29753


File: python.info,  Node: Documentation<26>,  Next: Tests<29>,  Prev: Library<31>,  Up: Python 3 10 0 alpha 6

1.23.32.4 Documentation
.......................

   - bpo-27646(1): Clarify that 'yield from <expr>' works with any
     iterable, not just iterators.

   - bpo-36346(2): Update some deprecated unicode APIs which are
     documented as "will be removed in 4.0" to "3.12".  See PEP 623(3)
     for detail.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27646

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36346

   (3) https://peps.python.org/pep-0623/


File: python.info,  Node: Tests<29>,  Next: Build<31>,  Prev: Documentation<26>,  Up: Python 3 10 0 alpha 6

1.23.32.5 Tests
...............

   - bpo-43288(1): Fix test_importlib to correctly skip Unicode file
     tests if the filesystem does not support them.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43288


File: python.info,  Node: Build<31>,  Next: Windows<28>,  Prev: Tests<29>,  Up: Python 3 10 0 alpha 6

1.23.32.6 Build
...............

   - bpo-43174(1): Windows build now uses ‘/utf-8’ compiler option.

   - bpo-43103(2): Add a new configure ‘--without-static-libpython’
     option to not build the ‘libpythonMAJOR.MINOR.a’ static library and
     not install the ‘python.o’ object file.

   - bpo-13501(3): The configure script can now use 'libedit' instead of
     'readline' with the command line option ‘--with-readline=editline’.

   - bpo-42603(4): Make configure script use pkg-config to detect the
     location of Tcl/Tk headers and libraries, used to build tkinter.

     On macOS, a Tcl/Tk configuration provided by pkg-config will be
     preferred over Tcl/Tk frameworks installed in
     ‘/{System/,}Library/Frameworks’.  If both exist and the latter is
     preferred, the appropriate ‘--with-tcltk-*’ configuration options
     need to be explicitly set.

   - bpo-39448(5): Add the "regen-frozen" makefile target that
     regenerates the code for the frozen ‘__hello__’ module.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43174

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43103

   (3) https://bugs.python.org/issue?@action=redirect&bpo=13501

   (4) https://bugs.python.org/issue?@action=redirect&bpo=42603

   (5) https://bugs.python.org/issue?@action=redirect&bpo=39448


File: python.info,  Node: Windows<28>,  Next: macOS<22>,  Prev: Build<31>,  Up: Python 3 10 0 alpha 6

1.23.32.7 Windows
.................

   - bpo-43155(1): *note PyCMethod_New(): 17f0. is now present in
     ‘python3.lib’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43155


File: python.info,  Node: macOS<22>,  Next: IDLE<20>,  Prev: Windows<28>,  Up: Python 3 10 0 alpha 6

1.23.32.8 macOS
...............

   - bpo-41837(1): Update macOS installer build to use OpenSSL 1.1.1j.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41837


File: python.info,  Node: IDLE<20>,  Next: C API<30>,  Prev: macOS<22>,  Up: Python 3 10 0 alpha 6

1.23.32.9 IDLE
..............

   - bpo-43283(1): Document why printing to IDLE's Shell is often slower
     than printing to a system terminal and that it can be made faster
     by pre-formatting a single string before printing.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43283


File: python.info,  Node: C API<30>,  Prev: IDLE<20>,  Up: Python 3 10 0 alpha 6

1.23.32.10 C API
................

   - bpo-43278(1): Always put compiler and system information on the
     first line of the REPL welcome message.

   - bpo-43270(2): Remove the private ‘_PyErr_OCCURRED()’ macro: use the
     public *note PyErr_Occurred(): 17f4. function instead.

   - bpo-35134(3): Move odictobject.h, parser_interface.h,
     picklebufobject.h, pydebug.h, and pyfpe.h into the cpython/
     directory.  They must not be included directly, as they are already
     included by Python.h: *note Include Files: 728.

   - bpo-35134(4): Move pyarena.h, pyctype.h, and pytime.h into the
     cpython/ directory.  They must not be included directly, as they
     are already included by Python.h: *note Include Files: 728.

   - bpo-40170(5): ‘PyExceptionClass_Name()’ is now always declared as a
     function, in order to hide implementation details.  The macro
     accessed *note PyTypeObject.tp_name: 17f5. directly.  Patch by
     Erlend E. Aasland.

   - bpo-43239(6): The *note PyCFunction_New(): 17f6. function is now
     exported in the ABI when compiled with ‘-fvisibility=hidden’.

   - bpo-40170(7): *note PyIter_Check(): 17f7. is now always declared as
     a function, in order to hide implementation details.  The macro
     accessed *note PyTypeObject.tp_iternext: 145d. directly.  Patch by
     Erlend E. Aasland.

   - bpo-40170(8): Convert *note PyDescr_IsData(): 17f8. macro to a
     function to hide implementation details: The macro accessed *note
     PyTypeObject.tp_descr_set: 17f9. directly.  Patch by Erlend E.
     Aasland.

   - bpo-43181(9): Convert *note PyObject_TypeCheck(): 17fa. macro to a
     static inline function.  Patch by Erlend E. Aasland.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43278

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43270

   (3) https://bugs.python.org/issue?@action=redirect&bpo=35134

   (4) https://bugs.python.org/issue?@action=redirect&bpo=35134

   (5) https://bugs.python.org/issue?@action=redirect&bpo=40170

   (6) https://bugs.python.org/issue?@action=redirect&bpo=43239

   (7) https://bugs.python.org/issue?@action=redirect&bpo=40170

   (8) https://bugs.python.org/issue?@action=redirect&bpo=40170

   (9) https://bugs.python.org/issue?@action=redirect&bpo=43181


File: python.info,  Node: Python 3 10 0 alpha 5,  Next: Python 3 10 0 alpha 4,  Prev: Python 3 10 0 alpha 6,  Up: Changelog（更動日誌）

1.23.33 Python 3.10.0 alpha 5
-----------------------------

'Release date: 2021-02-02'

* Menu:

* Security: Security<20>.
* Core and Builtins: Core and Builtins<33>.
* Library: Library<32>.
* Documentation: Documentation<27>.
* Tests: Tests<30>.
* Build: Build<32>.
* Windows: Windows<29>.
* macOS: macOS<23>.
* IDLE: IDLE<21>.
* C API: C API<31>.


File: python.info,  Node: Security<20>,  Next: Core and Builtins<33>,  Up: Python 3 10 0 alpha 5

1.23.33.1 Security
..................

   - bpo-42938(1): Avoid static buffers when computing the repr of *note
     ctypes.c_double: 17fd. and *note ctypes.c_longdouble: 17fe. values.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42938


File: python.info,  Node: Core and Builtins<33>,  Next: Library<32>,  Prev: Security<20>,  Up: Python 3 10 0 alpha 5

1.23.33.2 Core and Builtins
...........................

   - bpo-42990(1): Refactor the ‘PyEval_’ family of functions.

        * An new function ‘_PyEval_Vector’ is added to simplify calls to
          Python from C.

        * ‘_PyEval_EvalCodeWithName’ is removed

        * ‘PyEval_EvalCodeEx’ is retained as part of the API, but is not
          used internally

   - bpo-38631(2): Replace *note Py_FatalError(): 927. calls in the
     compiler with regular *note SystemError: 51b. exceptions.  Patch by
     Victor Stinner.

   - bpo-42997(3): Improve error message for missing ":" before blocks.
     Patch by Pablo Galindo.

   - bpo-43017(4): Improve error message in the parser when using
     un-parenthesised tuples in comprehensions.  Patch by Pablo Galindo.

   - bpo-42986(5): Fix parser crash when reporting syntax errors in
     f-string with newlines.  Patch by Pablo Galindo.

   - bpo-40176(6): Syntax errors for unterminated string literals now
     point to the start of the string instead of reporting EOF/EOL.

   - bpo-42927(7): The inline cache for ‘LOAD_ATTR’ now also optimizes
     access to attributes defined by ‘__slots__’.  This makes reading
     such attribute up to 30% faster.

   - bpo-42864(8): Improve error messages in the parser when parentheses
     are not closed.  Patch by Pablo Galindo.

   - bpo-42924(9): Fix ‘bytearray’ repetition incorrectly copying data
     from the start of the buffer, even if the data is offset within the
     buffer (e.g.  after reassigning a slice at the start of the
     ‘bytearray’ to a shorter byte string).

   - bpo-42882(10): Fix the ‘_PyUnicode_FromId()’ function
     (_Py_IDENTIFIER(var) API) when *note Py_Initialize(): 851. / *note
     Py_Finalize(): 12e6. is called multiple times: preserve
     ‘_PyRuntime.unicode_ids.next_index’ value.

   - bpo-42827(11): Fix a crash when working out the error line of a
     *note SyntaxError: 173. in some multi-line expressions.

   - bpo-42823(12): frame.f_lineno is correct even if frame.f_trace is
     set to True

   - bpo-37324(13): Remove deprecated aliases to *note Collections
     Abstract Base Classes: 81b. from the *note collections: 16. module.

   - bpo-41994(14): Fixed possible leak in ‘import’ when ‘sys.modules’
     is not a ‘dict’.

   - bpo-27772(15): In string formatting, preceding the 'width' field by
     ‘'0'’ no longer affects the default alignment for strings.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42990

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38631

   (3) https://bugs.python.org/issue?@action=redirect&bpo=42997

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43017

   (5) https://bugs.python.org/issue?@action=redirect&bpo=42986

   (6) https://bugs.python.org/issue?@action=redirect&bpo=40176

   (7) https://bugs.python.org/issue?@action=redirect&bpo=42927

   (8) https://bugs.python.org/issue?@action=redirect&bpo=42864

   (9) https://bugs.python.org/issue?@action=redirect&bpo=42924

   (10) https://bugs.python.org/issue?@action=redirect&bpo=42882

   (11) https://bugs.python.org/issue?@action=redirect&bpo=42827

   (12) https://bugs.python.org/issue?@action=redirect&bpo=42823

   (13) https://bugs.python.org/issue?@action=redirect&bpo=37324

   (14) https://bugs.python.org/issue?@action=redirect&bpo=41994

   (15) https://bugs.python.org/issue?@action=redirect&bpo=27772


File: python.info,  Node: Library<32>,  Next: Documentation<27>,  Prev: Core and Builtins<33>,  Up: Python 3 10 0 alpha 5

1.23.33.3 Library
.................

   - bpo-43108(1): Fixed a reference leak in the *note curses: 23.
     module.  Patch by Pablo Galindo

   - bpo-43077(2): Update the bundled pip to 21.0.1 and setuptools to
     52.0.0.

   - bpo-41282(3): Deprecate ‘distutils’ in documentation and add
     warning on import.

   - bpo-43014(4): Improve performance of *note tokenize: e4. by 20-30%.
     Patch by Anthony Sottile.

   - bpo-42323(5): Fix *note math.nextafter(): 440. for NaN on AIX.

   - bpo-42955(6): Add *note sys.stdlib_module_names: 7e5, containing
     the list of the standard library module names.  Patch by Victor
     Stinner.

   - bpo-42944(7): Fix ‘random.Random.sample’ when ‘counts’ argument is
     not ‘None’.

   - bpo-42934(8): Use *note TracebackException: 241.'s new ‘compact’
     param in *note TestResult: 1100. to reduce time and memory consumed
     by traceback formatting.

   - bpo-42931(9): Add ‘randbytes()’ to ‘random.__all__’.

   - bpo-38250(10): [Enum] Flags consisting of a single bit are now
     considered canonical, and will be the only flags returned from
     listing and iterating over a Flag class or a Flag member.
     Multi-bit flags are considered aliases; they will be returned from
     lookups and operations that result in their value.  Iteration for
     both Flag and Flag members is in definition order.

   - bpo-42877(11): Added the ‘compact’ parameter to the constructor of
     *note traceback.TracebackException: 241. to reduce time and memory
     for use cases that only need to call ‘TracebackException.format()’
     and ‘TracebackException.format_exception_only()’.

   - bpo-42923(12): The *note Py_FatalError(): 927. function and the
     *note faulthandler: 4e. module now dump the list of extension
     modules on a fatal error.

   - bpo-42848(13): Removed recursion from *note TracebackException:
     241. to allow it to handle long exception chains.

   - bpo-42901(14): [Enum] move member creation from ‘EnumMeta.__new__’
     to ‘_proto_member.__set_name__’, allowing members to be created and
     visible in ‘__init_subclass__’.

   - bpo-42780(15): Fix os.set_inheritable() for O_PATH file descriptors
     on Linux.

   - bpo-42866(16): Fix a reference leak in the ‘getcodec()’ function of
     CJK codecs.  Patch by Victor Stinner.

   - bpo-42846(17): Convert the 6 CJK codec extension modules
     (_codecs_cn, _codecs_hk, _codecs_iso2022, _codecs_jp, _codecs_kr
     and _codecs_tw) to the multiphase initialization API ( PEP
     489(18)).  Patch by Victor Stinner.

   - bpo-42851(19): remove __init_subclass__ support for Enum members

   - bpo-42834(20): Make internal caches of the ‘_json’ module
     compatible with subinterpreters.

   - bpo-41748(21): Fix HTMLParser parsing rules for element attributes
     containing commas with spaces.  Patch by Karl Dubost.

   - bpo-40810(22): Require SQLite 3.7.15 or newer.  Patch by Erlend E.
     Aasland.

   - bpo-1635741(23): Convert the _multibytecodec extension module (CJK
     codecs) to multi-phase initialization ( PEP 489(24)).  Patch by
     Erlend E. Aasland.

   - bpo-42802(25): The distutils ‘bdist_wininst’ command deprecated in
     Python 3.8 has been removed.  The distutils ‘bdist_wheel’ command
     is now recommended to distribute binary packages on Windows.

   - bpo-24464(26): The undocumented built-in function
     ‘sqlite3.enable_shared_cache’ is now deprecated, scheduled for
     removal in Python 3.12.  Its use is strongly discouraged by the
     SQLite3 documentation.  Patch by Erlend E. Aasland.

   - bpo-42384(27): Make pdb populate sys.path[0] exactly the same as
     regular python execution.

   - bpo-42383(28): Fix pdb: previously pdb would fail to restart the
     debugging target if it was specified using a relative path and the
     current directory changed.

   - bpo-42005(29): Fix CLI of *note cProfile: 20. and *note profile:
     9d. to catch *note BrokenPipeError: fff.

   - bpo-41604(30): Don't decrement the reference count of the previous
     user_ptr when set_panel_userptr fails.

   - bpo-41149(31): Allow executing callables that have a boolean value
     of ‘False’ when passed to ‘Threading.thread’ as the target.  Patch
     contributed by Barney Stratford.

   - bpo-38307(32): Add an 'end_lineno' attribute to the Class and
     Function objects that appear in the tree returned by pyclbr
     functions.  This and the existing 'lineno' attribute define the
     extent of class and def statements.  Patch by Aviral Srivastava.

   - bpo-39273(33): The ‘BUTTON5_*’ constants are now exposed in the
     *note curses: 23. module if available.

   - bpo-33289(34): Correct call to *note tkinter.colorchooser: da. to
     return RGB triplet of ints instead of floats.  Patch by Cheryl
     Sabella.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43108

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43077

   (3) https://bugs.python.org/issue?@action=redirect&bpo=41282

   (4) https://bugs.python.org/issue?@action=redirect&bpo=43014

   (5) https://bugs.python.org/issue?@action=redirect&bpo=42323

   (6) https://bugs.python.org/issue?@action=redirect&bpo=42955

   (7) https://bugs.python.org/issue?@action=redirect&bpo=42944

   (8) https://bugs.python.org/issue?@action=redirect&bpo=42934

   (9) https://bugs.python.org/issue?@action=redirect&bpo=42931

   (10) https://bugs.python.org/issue?@action=redirect&bpo=38250

   (11) https://bugs.python.org/issue?@action=redirect&bpo=42877

   (12) https://bugs.python.org/issue?@action=redirect&bpo=42923

   (13) https://bugs.python.org/issue?@action=redirect&bpo=42848

   (14) https://bugs.python.org/issue?@action=redirect&bpo=42901

   (15) https://bugs.python.org/issue?@action=redirect&bpo=42780

   (16) https://bugs.python.org/issue?@action=redirect&bpo=42866

   (17) https://bugs.python.org/issue?@action=redirect&bpo=42846

   (18) https://peps.python.org/pep-0489/

   (19) https://bugs.python.org/issue?@action=redirect&bpo=42851

   (20) https://bugs.python.org/issue?@action=redirect&bpo=42834

   (21) https://bugs.python.org/issue?@action=redirect&bpo=41748

   (22) https://bugs.python.org/issue?@action=redirect&bpo=40810

   (23) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (24) https://peps.python.org/pep-0489/

   (25) https://bugs.python.org/issue?@action=redirect&bpo=42802

   (26) https://bugs.python.org/issue?@action=redirect&bpo=24464

   (27) https://bugs.python.org/issue?@action=redirect&bpo=42384

   (28) https://bugs.python.org/issue?@action=redirect&bpo=42383

   (29) https://bugs.python.org/issue?@action=redirect&bpo=42005

   (30) https://bugs.python.org/issue?@action=redirect&bpo=41604

   (31) https://bugs.python.org/issue?@action=redirect&bpo=41149

   (32) https://bugs.python.org/issue?@action=redirect&bpo=38307

   (33) https://bugs.python.org/issue?@action=redirect&bpo=39273

   (34) https://bugs.python.org/issue?@action=redirect&bpo=33289


File: python.info,  Node: Documentation<27>,  Next: Tests<30>,  Prev: Library<32>,  Up: Python 3 10 0 alpha 5

1.23.33.4 Documentation
.......................

   - bpo-40304(1): Fix doc for type(name, bases, dict).  Patch by Boris
     Verkhovskiy and Éric Araujo.

   - bpo-42811(2): Updated importlib.util.resolve_name() doc to use
     __spec__.parent instead of __package__.  (Thanks Yair Frid.)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40304

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42811


File: python.info,  Node: Tests<30>,  Next: Build<32>,  Prev: Documentation<27>,  Up: Python 3 10 0 alpha 5

1.23.33.5 Tests
...............

   - bpo-40823(1): Use ‘unittest.TestLoader().loadTestsFromTestCase()’
     instead of ‘unittest.makeSuite()’ in *note sqlite3: ba. tests.
     Patch by Erlend E. Aasland.

   - bpo-40810(2): In *note sqlite3: ba, fix ‘CheckTraceCallbackContent’
     for SQLite pre 3.7.15.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40823

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40810


File: python.info,  Node: Build<32>,  Next: Windows<29>,  Prev: Tests<30>,  Up: Python 3 10 0 alpha 5

1.23.33.6 Build
...............

   - bpo-43031(1): Pass ‘--timeout=$(TESTTIMEOUT)’ option to the default
     profile task ‘./python -m test --pgo’ command.

   - bpo-36143(2): ‘make regen-all’ now also runs ‘regen-keyword’.
     Patch by Victor Stinner.

   - bpo-42874(3): Removed the grep -q and -E flags in the tzpath
     validation section of the configure script to better accommodate
     users of some platforms (specifically Solaris 10).

   - bpo-31904(4): Add library search path by wr-cc in
     add_cross_compiling_paths() for VxWorks.

   - bpo-42856(5): Add ‘--with-wheel-pkg-dir=PATH’ option to the
     ‘./configure’ script.  If specified, the *note ensurepip: 4b.
     module looks for ‘setuptools’ and ‘pip’ wheel packages in this
     directory: if both are present, these wheel packages are used
     instead of ensurepip bundled wheel packages.

     Some Linux distribution packaging policies recommend against
     bundling dependencies.  For example, Fedora installs wheel packages
     in the ‘/usr/share/python-wheels/’ directory and don't install the
     ‘ensurepip._bundled’ package.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43031

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36143

   (3) https://bugs.python.org/issue?@action=redirect&bpo=42874

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (5) https://bugs.python.org/issue?@action=redirect&bpo=42856


File: python.info,  Node: Windows<29>,  Next: macOS<23>,  Prev: Build<32>,  Up: Python 3 10 0 alpha 5

1.23.33.7 Windows
.................

   - bpo-41837(1): Updated Windows installer to include OpenSSL 1.1.1i

   - bpo-42584(2): Upgrade Windows installer to use SQLite 3.34.0.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41837

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42584


File: python.info,  Node: macOS<23>,  Next: IDLE<21>,  Prev: Windows<29>,  Up: Python 3 10 0 alpha 5

1.23.33.8 macOS
...............

   - bpo-42504(1): Ensure that the value of
     sysconfig.get_config_var('MACOSX_DEPLOYMENT_TARGET') is always a
     string, even in when the value is parsable as an integer.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42504


File: python.info,  Node: IDLE<21>,  Next: C API<31>,  Prev: macOS<23>,  Up: Python 3 10 0 alpha 5

1.23.33.9 IDLE
..............

   - bpo-43008(1): Make IDLE invoke *note sys.excepthook(): 7af. in
     normal, 2-process mode.  Patch by Ken Hilton.

   - bpo-33065(2): Fix problem debugging user classes with __repr__
     method.

   - bpo-23544(3): Disable Debug=>Stack Viewer when user code is running
     or Debugger is active, to prevent hang or crash.  Patch by Zackery
     Spytz.

   - bpo-32631(4): Finish zzdummy example extension module: make menu
     entries work; add docstrings and tests with 100% coverage.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=43008

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33065

   (3) https://bugs.python.org/issue?@action=redirect&bpo=23544

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32631


File: python.info,  Node: C API<31>,  Prev: IDLE<21>,  Up: Python 3 10 0 alpha 5

1.23.33.10 C API
................

   - bpo-42979(1): When Python is built in debug mode (with C
     assertions), calling a type slot like ‘sq_length’ (‘__len__()’ in
     Python) now fails with a fatal error if the slot succeeded with an
     exception set, or failed with no exception set.  The error message
     contains the slot, the type name, and the current exception (if an
     exception is set).  Patch by Victor Stinner.

   - bpo-43030(2): Fixed a compiler warning in *note
     Py_UNICODE_ISSPACE(): 1808. on platforms with signed ‘wchar_t’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42979

   (2) https://bugs.python.org/issue?@action=redirect&bpo=43030


File: python.info,  Node: Python 3 10 0 alpha 4,  Next: Python 3 10 0 alpha 3,  Prev: Python 3 10 0 alpha 5,  Up: Changelog（更動日誌）

1.23.34 Python 3.10.0 alpha 4
-----------------------------

'Release date: 2021-01-04'

* Menu:

* Core and Builtins: Core and Builtins<34>.
* Library: Library<33>.
* Documentation: Documentation<28>.
* Tests: Tests<31>.
* Build: Build<33>.
* macOS: macOS<24>.
* Tools/Demos: Tools/Demos<14>.
* C API: C API<32>.


File: python.info,  Node: Core and Builtins<34>,  Next: Library<33>,  Up: Python 3 10 0 alpha 4

1.23.34.1 Core and Builtins
...........................

   - bpo-42814(1): Fix undefined behavior in
     ‘Objects/genericaliasobject.c’.

   - bpo-42806(2): Fix the column offsets for f-strings *note ast: 7.
     nodes surrounded by parentheses and for nodes that spawn multiple
     lines.  Patch by Pablo Galindo.

   - bpo-40631(3): Fix regression where a single parenthesized starred
     expression was a valid assignment target.

   - bpo-27794(4): Improve the error message for failed writes/deletes
     to property objects.  When possible, the attribute name is now
     shown.  Patch provided by Yurii Karabas.

   - bpo-42745(5): Make the type attribute lookup cache per-interpreter.
     Patch by Victor Stinner.

   - bpo-42246(6): Jumps to jumps are not eliminated when it would break
     PEP 626.

   - bpo-42246(7): Make sure that the ‘f_lasti’ and ‘f_lineno’
     attributes of a frame are set correctly when an exception is raised
     or re-raised.  Required for PEP 626.

   - bpo-32381(8): The coding cookie (ex: ‘# coding: latin1’) is now
     ignored in the command passed to the *note -c: 584. command line
     option.  Patch by Victor Stinner.

   - bpo-30858(9): Improve error location in expressions that contain
     assignments.  Patch by Pablo Galindo and Lysandros Nikolaou.

   - bpo-42615(10): Remove jump commands made redundant by the deletion
     of unreachable bytecode blocks

   - bpo-42639(11): Make the *note atexit: 9. module state
     per-interpreter.  It is now safe have more than one *note atexit:
     9. module instance.  Patch by Donghee Na and Victor Stinner.

   - bpo-32381(12): Fix encoding name when running a ‘.pyc’ file on
     Windows: *note PyRun_SimpleFileExFlags(): 180b. now uses the
     correct encoding to decode the filename.

   - bpo-42195(13): The ‘__args__’ of the parameterized generics for
     *note typing.Callable: 769. and *note collections.abc.Callable:
     78e. are now consistent.  The ‘__args__’ for *note
     collections.abc.Callable: 78e. are now flattened while *note
     typing.Callable: 769.'s have not changed.  To allow this change,
     *note types.GenericAlias: 78f. can now be subclassed and
     ‘collections.abc.Callable’'s ‘__class_getitem__’ will now return a
     subclass of ‘types.GenericAlias’.  Tests for typing were also
     updated to not subclass things like ‘Callable[..., T]’ as that is
     not a valid base class.  Finally, both ‘Callable’s no longer
     validate their ‘argtypes’, in ‘Callable[[argtypes], resulttype]’ to
     prepare for PEP 612(14).  Patch by Ken Jin.

   - bpo-40137(15): Convert functools module to use *note
     PyType_FromModuleAndSpec(): 4f7.

   - bpo-40077(16): Convert *note array: 6. to use heap types, and
     establish module state for these.

   - bpo-42008(17): Fix _random.Random() seeding.

   - bpo-1635741(18): Port the ‘pyexpat’ extension module to multi-phase
     initialization ( PEP 489(19)).

   - bpo-40521(20): Make the Unicode dictionary of interned strings
     compatible with subinterpreters.  Patch by Victor Stinner.

   - bpo-39465(21): Make ‘_PyUnicode_FromId()’ function compatible with
     subinterpreters.  Each interpreter now has an array of identifier
     objects (interned strings decoded from UTF-8).  Patch by Victor
     Stinner.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42814

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42806

   (3) https://bugs.python.org/issue?@action=redirect&bpo=40631

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27794

   (5) https://bugs.python.org/issue?@action=redirect&bpo=42745

   (6) https://bugs.python.org/issue?@action=redirect&bpo=42246

   (7) https://bugs.python.org/issue?@action=redirect&bpo=42246

   (8) https://bugs.python.org/issue?@action=redirect&bpo=32381

   (9) https://bugs.python.org/issue?@action=redirect&bpo=30858

   (10) https://bugs.python.org/issue?@action=redirect&bpo=42615

   (11) https://bugs.python.org/issue?@action=redirect&bpo=42639

   (12) https://bugs.python.org/issue?@action=redirect&bpo=32381

   (13) https://bugs.python.org/issue?@action=redirect&bpo=42195

   (14) https://peps.python.org/pep-0612/

   (15) https://bugs.python.org/issue?@action=redirect&bpo=40137

   (16) https://bugs.python.org/issue?@action=redirect&bpo=40077

   (17) https://bugs.python.org/issue?@action=redirect&bpo=42008

   (18) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (19) https://peps.python.org/pep-0489/

   (20) https://bugs.python.org/issue?@action=redirect&bpo=40521

   (21) https://bugs.python.org/issue?@action=redirect&bpo=39465


File: python.info,  Node: Library<33>,  Next: Documentation<28>,  Prev: Core and Builtins<34>,  Up: Python 3 10 0 alpha 4

1.23.34.2 Library
.................

   - bpo-42257(1): Handle empty string in variable executable in
     platform.libc_ver()

   - bpo-42772(2): randrange() now raises a TypeError when step is
     specified without a stop argument.  Formerly, it silently ignored
     the step argument.

   - bpo-42759(3): Fixed equality comparison of ‘tkinter.Variable’ and
     *note tkinter.font.Font: 180d.  Objects which belong to different
     Tcl interpreters are now always different, even if they have the
     same name.

   - bpo-42756(4): Configure LMTP Unix-domain socket to use socket
     global default timeout when a timeout is not explicitly provided.

   - bpo-23328(5): Allow / character in username, password fields on
     _PROXY envars.

   - bpo-42740(6): *note typing.get_args(): 822. and *note
     typing.get_origin(): 9ea. now support PEP 604(7) union types and
     PEP 612(8) additions to ‘Callable’.

   - bpo-42655(9): *note subprocess: c1. 'extra_groups' is now correctly
     passed into setgroups() system call.

   - bpo-42727(10): ‘EnumMeta.__prepare__’ now accepts ‘**kwds’ to
     properly support ‘__init_subclass__’

   - bpo-38308(11): Add optional 'weights' to
     'statistics.harmonic_mean()'.

   - bpo-42721(12): When simple query dialogs (*note
     tkinter.simpledialog: e1.), message boxes (*note
     tkinter.messagebox: df.) or color choose dialog (*note
     tkinter.colorchooser: da.) are created without arguments 'master'
     and 'parent', and the default root window is not yet created, and
     ‘NoDefaultRoot()’ was not called, a new temporal hidden root window
     will be created automatically.  It will not be set as the default
     root window and will be destroyed right after closing the dialog
     window.  It will help to use these simple dialog windows in
     programs which do not need other GUI.

   - bpo-25246(13): Optimized *note collections.deque.remove(): 180e.

   - bpo-35728(14): Added a root parameter to *note
     tkinter.font.nametofont(): 180f.

   - bpo-15303(15): *note tkinter: d9. supports now widgets with boolean
     value False.

   - bpo-42681(16): Fixed range checks for color and pair numbers in
     *note curses: 23.

   - bpo-42685(17): Improved placing of simple query windows in Tkinter
     (such as *note tkinter.simpledialog.askinteger(): 1810.).  They are
     now centered at the center of the parent window if it is specified
     and shown, otherwise at the center of the screen.

   - bpo-9694(18): Argparse help no longer uses the confusing phrase,
     "optional arguments".  It uses "options" instead.

   - bpo-1635741(19): Port the ‘_thread’ extension module to the
     multiphase initialization API ( PEP 489(20)) and convert its static
     types to heap types.

   - bpo-37961(21): Fix crash in ‘tracemalloc.Traceback.__repr__()’
     (regressed in Python 3.9).

   - bpo-42630(22): *note tkinter: d9. functions and constructors which
     need a default root window raise now *note RuntimeError: 179. with
     descriptive message instead of obscure *note AttributeError: 2f6.
     or *note NameError: 3e5. if it is not created yet or cannot be
     created automatically.

   - bpo-42639(23): ‘atexit._run_exitfuncs()’ now logs callback
     exceptions using *note sys.unraisablehook: 1dc, rather than logging
     them directly into *note sys.stderr: 8dd. and raise the last
     exception.

   - bpo-42644(24): ‘logging.disable’ will now validate the types and
     value of its parameter.  It also now accepts strings representing
     the levels (as does ‘logging.setLevel’) instead of only the
     numerical values.

   - bpo-42639(25): At Python exit, if a callback registered with *note
     atexit.register(): 821. fails, its exception is now logged.
     Previously, only some exceptions were logged, and the last
     exception was always silently ignored.

   - bpo-36541(26): Fixed lib2to3.pgen2 to be able to parse PEP-570
     positional only argument syntax.

   - bpo-42382(27): In ‘importlib.metadata’: - ‘EntryPoint’ objects now
     expose a ‘.dist’ object referencing the ‘Distribution’ when
     constructed from a ‘Distribution’.  - Add support for package
     discovery under package normalization rules.  - The object returned
     by ‘metadata()’ now has a formally defined protocol called
     ‘PackageMetadata’ with declared support for the ‘.get_all()’
     method.  - Synced with importlib_metadata 3.3.

   - bpo-41877(28): A check is added against misspellings of autospect,
     auto_spec and set_spec being passed as arguments to patch,
     patch.object and create_autospec.

   - bpo-39717(29): [tarfile] update nested exception raising to use
     ‘from None’ or ‘from e’

   - bpo-41877(30): AttributeError for suspected misspellings of
     assertions on mocks are now pointing out that the cause are
     misspelled assertions and also what to do if the misspelling is
     actually an intended attribute name.  The unittest.mock document is
     also updated to reflect the current set of recognised misspellings.

   - bpo-41559(31): Implemented PEP 612(32): added ‘ParamSpec’ and
     ‘Concatenate’ to *note typing: ed.  Patch by Ken Jin.

   - bpo-42385(33): StrEnum: fix _generate_next_value_ to return a str

   - bpo-31904(34): Define THREAD_STACK_SIZE for VxWorks.

   - bpo-34750(35): [Enum] ‘_EnumDict.update()’ is now supported.

   - bpo-42517(36): Enum: private names do not become members / do not
     generate errors - they remain normal attributes

   - bpo-42678(37): ‘Enum’: call ‘__init_subclass__’ after members have
     been added

   - bpo-28964(38): *note ast.literal_eval(): bbf. adds line number
     information (if available) in error message for malformed nodes.

   - bpo-42470(39): *note random.sample(): 6ea. no longer warns on a
     sequence which is also a set.

   - bpo-31904(40): ‘posixpath.expanduser()’ returns the input 'path'
     unchanged if user home directory is None on VxWorks.

   - bpo-42388(41): Fix subprocess.check_output(..., input=None)
     behavior when text=True to be consistent with that of the
     documentation and universal_newlines=True.

   - bpo-34463(42): Fixed discrepancy between *note traceback: e7. and
     the interpreter in formatting of SyntaxError with lineno not set
     (*note traceback: e7. was changed to match interpreter).

   - bpo-42393(43): Raise *note OverflowError: 825. instead of silent
     truncation in *note socket.ntohs(): 824. and *note socket.htons():
     823.  Silent truncation was deprecated in Python 3.7.  Patch by
     Erlend E. Aasland

   - bpo-42222(44): Harmonized *note random.randrange(): 810. argument
     handling to match *note range(): 8e7.

        * The integer test and conversion in ‘randrange()’ now uses
          *note operator.index(): 1811.

        * Non-integer arguments to ‘randrange()’ are deprecated.

        * The ‘ValueError’ is deprecated in favor of a ‘TypeError’.

        * It now runs a little faster than before.

     (Contributed by Raymond Hettinger and Serhiy Storchaka.)

   - bpo-42163(45): Restore compatibility for ‘uname_result’ around
     deepcopy and _replace.

   - bpo-42090(46): ‘zipfile.Path.joinpath’ now accepts arbitrary
     arguments, same as ‘pathlib.Path.joinpath’.

   - bpo-1635741(47): Port the _csv module to the multi-phase
     initialization API ( PEP 489(48)).

   - bpo-42059(49): *note typing.TypedDict: 146. types created using the
     alternative call-style syntax now correctly respect the ‘total’
     keyword argument when setting their ‘__required_keys__’ and
     ‘__optional_keys__’ class attributes.

   - bpo-41960(50): Add ‘globalns’ and ‘localns’ parameters to the *note
     inspect.signature(): 6dc. and *note
     inspect.Signature.from_callable(): 6de.

   - bpo-41907(51): fix ‘format()’ behavior for ‘IntFlag’

   - bpo-41891(52): Ensure asyncio.wait_for waits for task completion

   - bpo-24792(53): Fixed bug where ‘zipimporter’ sometimes reports an
     incorrect cause of import errors.

   - bpo-31904(54): Fix site and sysconfig modules for VxWorks RTOS
     which has no home directories.

   - bpo-41462(55): Add *note os.set_blocking(): de0. support for
     VxWorks RTOS.

   - bpo-40219(56): Lowered ‘tkinter.ttk.LabeledScale’ dummy widget to
     prevent hiding part of the content label.

   - bpo-37193(57): Fixed memory leak in ‘socketserver.ThreadingMixIn’
     introduced in Python 3.7.

   - bpo-39068(58): Fix initialization race condition in ‘a85encode()’
     and ‘b85encode()’ in *note base64: a.  Patch by Brandon Stansbury.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42257

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42772

   (3) https://bugs.python.org/issue?@action=redirect&bpo=42759

   (4) https://bugs.python.org/issue?@action=redirect&bpo=42756

   (5) https://bugs.python.org/issue?@action=redirect&bpo=23328

   (6) https://bugs.python.org/issue?@action=redirect&bpo=42740

   (7) https://peps.python.org/pep-0604/

   (8) https://peps.python.org/pep-0612/

   (9) https://bugs.python.org/issue?@action=redirect&bpo=42655

   (10) https://bugs.python.org/issue?@action=redirect&bpo=42727

   (11) https://bugs.python.org/issue?@action=redirect&bpo=38308

   (12) https://bugs.python.org/issue?@action=redirect&bpo=42721

   (13) https://bugs.python.org/issue?@action=redirect&bpo=25246

   (14) https://bugs.python.org/issue?@action=redirect&bpo=35728

   (15) https://bugs.python.org/issue?@action=redirect&bpo=15303

   (16) https://bugs.python.org/issue?@action=redirect&bpo=42681

   (17) https://bugs.python.org/issue?@action=redirect&bpo=42685

   (18) https://bugs.python.org/issue?@action=redirect&bpo=9694

   (19) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (20) https://peps.python.org/pep-0489/

   (21) https://bugs.python.org/issue?@action=redirect&bpo=37961

   (22) https://bugs.python.org/issue?@action=redirect&bpo=42630

   (23) https://bugs.python.org/issue?@action=redirect&bpo=42639

   (24) https://bugs.python.org/issue?@action=redirect&bpo=42644

   (25) https://bugs.python.org/issue?@action=redirect&bpo=42639

   (26) https://bugs.python.org/issue?@action=redirect&bpo=36541

   (27) https://bugs.python.org/issue?@action=redirect&bpo=42382

   (28) https://bugs.python.org/issue?@action=redirect&bpo=41877

   (29) https://bugs.python.org/issue?@action=redirect&bpo=39717

   (30) https://bugs.python.org/issue?@action=redirect&bpo=41877

   (31) https://bugs.python.org/issue?@action=redirect&bpo=41559

   (32) https://peps.python.org/pep-0612/

   (33) https://bugs.python.org/issue?@action=redirect&bpo=42385

   (34) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (35) https://bugs.python.org/issue?@action=redirect&bpo=34750

   (36) https://bugs.python.org/issue?@action=redirect&bpo=42517

   (37) https://bugs.python.org/issue?@action=redirect&bpo=42678

   (38) https://bugs.python.org/issue?@action=redirect&bpo=28964

   (39) https://bugs.python.org/issue?@action=redirect&bpo=42470

   (40) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (41) https://bugs.python.org/issue?@action=redirect&bpo=42388

   (42) https://bugs.python.org/issue?@action=redirect&bpo=34463

   (43) https://bugs.python.org/issue?@action=redirect&bpo=42393

   (44) https://bugs.python.org/issue?@action=redirect&bpo=42222

   (45) https://bugs.python.org/issue?@action=redirect&bpo=42163

   (46) https://bugs.python.org/issue?@action=redirect&bpo=42090

   (47) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (48) https://peps.python.org/pep-0489/

   (49) https://bugs.python.org/issue?@action=redirect&bpo=42059

   (50) https://bugs.python.org/issue?@action=redirect&bpo=41960

   (51) https://bugs.python.org/issue?@action=redirect&bpo=41907

   (52) https://bugs.python.org/issue?@action=redirect&bpo=41891

   (53) https://bugs.python.org/issue?@action=redirect&bpo=24792

   (54) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (55) https://bugs.python.org/issue?@action=redirect&bpo=41462

   (56) https://bugs.python.org/issue?@action=redirect&bpo=40219

   (57) https://bugs.python.org/issue?@action=redirect&bpo=37193

   (58) https://bugs.python.org/issue?@action=redirect&bpo=39068


File: python.info,  Node: Documentation<28>,  Next: Tests<31>,  Prev: Library<33>,  Up: Python 3 10 0 alpha 4

1.23.34.3 Documentation
.......................

   - bpo-17140(1): Add documentation for the *note
     multiprocessing.pool.ThreadPool: 1813. class.

   - bpo-34398(2): Prominently feature listings from the glossary in
     documentation search results.  Patch by Ammar Askar.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=17140

   (2) https://bugs.python.org/issue?@action=redirect&bpo=34398


File: python.info,  Node: Tests<31>,  Next: Build<33>,  Prev: Documentation<28>,  Up: Python 3 10 0 alpha 4

1.23.34.4 Tests
...............

   - bpo-42794(1): Update test_nntplib to use official group name of
     news.aioe.org for testing.  Patch by Donghee Na.

   - bpo-31904(2): Skip some asyncio tests on VxWorks.

   - bpo-42641(3): Enhance ‘test_select.test_select()’: it now takes 500
     milliseconds rather than 10 seconds.  Use Python rather than a
     shell to make the test more portable.

   - bpo-31904(4): Skip some tests in _test_all_chown_common() on
     VxWorks.

   - bpo-42199(5): Fix bytecode helper assertNotInBytecode.

   - bpo-41443(6): Add more attribute checking in test_posix.py

   - bpo-31904(7): Disable os.popen and impacted tests on VxWorks

   - bpo-41439(8): Port test_ssl and test_uuid to VxWorks RTOS.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42794

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (3) https://bugs.python.org/issue?@action=redirect&bpo=42641

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (5) https://bugs.python.org/issue?@action=redirect&bpo=42199

   (6) https://bugs.python.org/issue?@action=redirect&bpo=41443

   (7) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (8) https://bugs.python.org/issue?@action=redirect&bpo=41439


File: python.info,  Node: Build<33>,  Next: macOS<24>,  Prev: Tests<31>,  Up: Python 3 10 0 alpha 4

1.23.34.5 Build
...............

   - bpo-42692(1): Fix __builtin_available check on older compilers.
     Patch by Joshua Root.

   - bpo-27640(2): Added ‘--disable-test-modules’ option to the
     ‘configure’ script: don't build nor install test modules.  Patch by
     Xavier de Gaye, Thomas Petazzoni and Peixing Xin.

   - bpo-42604(3): Now all platforms use a value for the "EXT_SUFFIX"
     build variable derived from SOABI (for instance in freeBSD,
     "EXT_SUFFIX" is now ".cpython-310d.so" instead of ".so").
     Previously only Linux, Mac and VxWorks were using a value for
     "EXT_SUFFIX" that included "SOABI".

   - bpo-42598(4): Fix implicit function declarations in configure which
     could have resulted in incorrect configuration checks.  Patch
     contributed by Joshua Root.

   - bpo-31904(5): Enable libpython3.so for VxWorks.

   - bpo-29076(6): Add fish shell support to macOS installer.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42692

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27640

   (3) https://bugs.python.org/issue?@action=redirect&bpo=42604

   (4) https://bugs.python.org/issue?@action=redirect&bpo=42598

   (5) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (6) https://bugs.python.org/issue?@action=redirect&bpo=29076


File: python.info,  Node: macOS<24>,  Next: Tools/Demos<14>,  Prev: Build<33>,  Up: Python 3 10 0 alpha 4

1.23.34.6 macOS
...............

   - bpo-42361(1): Update macOS installer build to use Tcl/Tk 8.6.11
     (rc2, expected to be final release).

   - bpo-41837(2): Update macOS installer build to use OpenSSL 1.1.1i.

   - bpo-42584(3): Update macOS installer to use SQLite 3.34.0.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42361

   (2) https://bugs.python.org/issue?@action=redirect&bpo=41837

   (3) https://bugs.python.org/issue?@action=redirect&bpo=42584


File: python.info,  Node: Tools/Demos<14>,  Next: C API<32>,  Prev: macOS<24>,  Up: Python 3 10 0 alpha 4

1.23.34.7 Tools/Demos
.....................

   - bpo-42726(1): Fixed Python 3 compatibility issue with
     gdb/libpython.py handling of attribute dictionaries.

   - bpo-42613(2): Fix ‘freeze.py’ tool to use the prope config and
     library directories.  Patch by Victor Stinner.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42726

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42613


File: python.info,  Node: C API<32>,  Prev: Tools/Demos<14>,  Up: Python 3 10 0 alpha 4

1.23.34.8 C API
...............

   - bpo-42591(1): Export the ‘Py_FrozenMain()’ function: fix a Python
     3.9.0 regression.  Python 3.9 uses ‘-fvisibility=hidden’ and the
     function was not exported explicitly and so not exported.

   - bpo-32381(2): Remove the private ‘_Py_fopen()’ function which is no
     longer needed.  Use ‘_Py_wfopen()’ or ‘_Py_fopen_obj()’ instead.
     Patch by Victor Stinner.

   - bpo-1635741(3): Port *note resource: aa. extension module to module
     state

   - bpo-42111(4): Update the ‘xxlimited’ module to be a better example
     of how to use the limited C API.

   - bpo-40052(5): Fix an alignment build warning/error in function
     ‘PyVectorcall_Function()’.  Patch by Andreas Schneider, Antoine
     Pitrou and Petr Viktorin.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42591

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32381

   (3) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (4) https://bugs.python.org/issue?@action=redirect&bpo=42111

   (5) https://bugs.python.org/issue?@action=redirect&bpo=40052


File: python.info,  Node: Python 3 10 0 alpha 3,  Next: Python 3 10 0 alpha 2,  Prev: Python 3 10 0 alpha 4,  Up: Changelog（更動日誌）

1.23.35 Python 3.10.0 alpha 3
-----------------------------

'Release date: 2020-12-07'

* Menu:

* Security: Security<21>.
* Core and Builtins: Core and Builtins<35>.
* Library: Library<34>.
* Documentation: Documentation<29>.
* Tests: Tests<32>.
* Build: Build<34>.
* Windows: Windows<30>.
* macOS: macOS<25>.
* IDLE: IDLE<22>.
* Tools/Demos: Tools/Demos<15>.
* C API: C API<33>.


File: python.info,  Node: Security<21>,  Next: Core and Builtins<35>,  Up: Python 3 10 0 alpha 3

1.23.35.1 Security
..................

   - bpo-40791(1): Add ‘volatile’ to the accumulator variable in
     ‘hmac.compare_digest’, making constant-time-defeating optimizations
     less likely.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40791


File: python.info,  Node: Core and Builtins<35>,  Next: Library<34>,  Prev: Security<21>,  Up: Python 3 10 0 alpha 3

1.23.35.2 Core and Builtins
...........................

   - bpo-42576(1): ‘types.GenericAlias’ will now raise a ‘TypeError’
     when attempting to initialize with a keyword argument.  Previously,
     this would cause the interpreter to crash if the interpreter was
     compiled with debug symbols.  This does not affect interpreters
     compiled for release.  Patch by Ken Jin.

   - bpo-42536(2): Several built-in and standard library types now
     ensure that their internal result tuples are always tracked by the
     *note garbage collector: 181c.:

        - *note collections.OrderedDict.items(): 57f.

        - *note dict.items(): 773.

        - *note enumerate(): 13ea.

        - *note functools.reduce(): 126f.

        - *note itertools.combinations(): 12a6.

        - *note itertools.combinations_with_replacement(): 1219.

        - *note itertools.permutations(): 181d.

        - *note itertools.product(): 12a7.

        - *note itertools.zip_longest(): 1235.

        - *note zip(): 774.

     Previously, they could have become untracked by a prior garbage
     collection.  Patch by Brandt Bucher.

   - bpo-42500(3): Improve handling of exceptions near recursion limit.
     Converts a number of Fatal Errors in RecursionErrors.

   - bpo-42246(4): PEP 626: After a return, the f_lineno attribute of a
     frame is always the last line executed.

   - bpo-42435(5): Speed up comparison of bytes objects with non-bytes
     objects when option *note -b: 587. is specified.  Speed up
     comparison of bytarray objects with non-buffer object.

   - bpo-1635741(6): Port the ‘_warnings’ extension module to the
     multi-phase initialization API ( PEP 489(7)).  Patch by Victor
     Stinner.

   - bpo-41686(8): On Windows, the ‘SIGINT’ event,
     ‘_PyOS_SigintEvent()’, is now created even if Python is configured
     to not install signal handlers (if *note
     PyConfig.install_signal_handlers: 863. equals to 0, or
     ‘Py_InitializeEx(0)’).

   - bpo-42381(9): Allow assignment expressions in set literals and set
     comprehensions as per PEP 572.  Patch by Pablo Galindo.

   - bpo-42202(10): Change function parameters annotations internal
     representation to tuple of strings.  Patch provided by Yurii
     Karabas.

   - bpo-42374(11): Fix a regression introduced by the new parser, where
     an unparenthesized walrus operator was not allowed within generator
     expressions.

   - bpo-42316(12): Allow an unparenthesized walrus in subscript
     indexes.

   - bpo-42349(13): Make sure that the compiler front-end produces a
     well-formed control flow graph.  Be more aggressive in the compiler
     back-end, as it is now safe to do so.

   - bpo-42296(14): On Windows, fix a regression in signal handling
     which prevented to interrupt a program using CTRL+C. The signal
     handler can be run in a thread different than the Python thread, in
     which case the test deciding if the thread can handle signals is
     wrong.

   - bpo-42332(15): *note types.GenericAlias: 78f. objects can now be
     the targets of weakrefs.

   - bpo-42282(16): Optimise constant subexpressions that appear as part
     of named expressions (previously the AST optimiser did not descend
     into named expressions).  Patch by Nick Coghlan.

   - bpo-42266(17): Fixed a bug with the LOAD_ATTR opcode cache that was
     not respecting monkey-patching a class-level attribute to make it a
     descriptor.  Patch by Pablo Galindo.

   - bpo-40077(18): Convert *note queue: a4. to use heap types.

   - bpo-42246(19): Improved accuracy of line tracing events and
     f_lineno attribute of Frame objects.  See PEP 626 for details.

   - bpo-40077(20): Convert *note mmap: 83. to use heap types.

   - bpo-42233(21): Allow ‘GenericAlias’ objects to use *note union type
     expressions: 766.  This allows expressions like ‘list[int] |
     dict[float, str]’ where previously a ‘TypeError’ would have been
     thrown.  This also fixes union type expressions not de-duplicating
     ‘GenericAlias’ objects.  (Contributed by Ken Jin in bpo-42233(22).)

   - bpo-26131(23): The import system triggers a ‘ImportWarning’ when it
     falls back to using ‘load_module()’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42576

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42536

   (3) https://bugs.python.org/issue?@action=redirect&bpo=42500

   (4) https://bugs.python.org/issue?@action=redirect&bpo=42246

   (5) https://bugs.python.org/issue?@action=redirect&bpo=42435

   (6) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (7) https://peps.python.org/pep-0489/

   (8) https://bugs.python.org/issue?@action=redirect&bpo=41686

   (9) https://bugs.python.org/issue?@action=redirect&bpo=42381

   (10) https://bugs.python.org/issue?@action=redirect&bpo=42202

   (11) https://bugs.python.org/issue?@action=redirect&bpo=42374

   (12) https://bugs.python.org/issue?@action=redirect&bpo=42316

   (13) https://bugs.python.org/issue?@action=redirect&bpo=42349

   (14) https://bugs.python.org/issue?@action=redirect&bpo=42296

   (15) https://bugs.python.org/issue?@action=redirect&bpo=42332

   (16) https://bugs.python.org/issue?@action=redirect&bpo=42282

   (17) https://bugs.python.org/issue?@action=redirect&bpo=42266

   (18) https://bugs.python.org/issue?@action=redirect&bpo=40077

   (19) https://bugs.python.org/issue?@action=redirect&bpo=42246

   (20) https://bugs.python.org/issue?@action=redirect&bpo=40077

   (21) https://bugs.python.org/issue?@action=redirect&bpo=42233

   (22) https://bugs.python.org/issue?@action=redirect&bpo=42233

   (23) https://bugs.python.org/issue?@action=redirect&bpo=26131


File: python.info,  Node: Library<34>,  Next: Documentation<29>,  Prev: Core and Builtins<35>,  Up: Python 3 10 0 alpha 3

1.23.35.3 Library
.................

   - bpo-5054(1): CGIHTTPRequestHandler.run_cgi() HTTP_ACCEPT improperly
     parsed.  Replace the special purpose getallmatchingheaders with
     generic get_all method and add relevant tests.

     Original Patch by Martin Panter.  Modified by Senthil Kumaran.

   - bpo-42562(2): Fix issue when dis failed to parse function that has
     no line numbers.  Patch provided by Yurii Karabas.

   - bpo-17735(3): ‘inspect.findsource()’ now raises *note OSError: 350.
     instead of *note IndexError: 14a3. when ‘co_lineno’ of a code
     object is greater than the file length.  This can happen, for
     example, when a file is edited after it was imported.  PR by Irit
     Katriel.

   - bpo-42116(4): Fix handling of trailing comments by *note
     inspect.getsource(): 14ca.

   - bpo-42532(5): Remove unexpected call of ‘__bool__’ when passing a
     ‘spec_arg’ argument to a Mock.

   - bpo-38200(6): Added itertools.pairwise()

   - bpo-41818(7): Fix test_master_read() so that it succeeds on all
     platforms that either raise OSError or return b"" upon reading from
     master.

   - bpo-42487(8): ChainMap.__iter__ no longer calls __getitem__ on
     underlying maps

   - bpo-42482(9): *note TracebackException: 241. no longer holds a
     reference to the exception's traceback object.  Consequently,
     instances of TracebackException for equivalent but non-equal
     exceptions now compare as equal.

   - bpo-41818(10): Make test_openpty() avoid unexpected success due to
     number of rows and/or number of columns being == 0.

   - bpo-42392(11): Remove loop parameter from ‘asyncio.subprocess’ and
     ‘asyncio.tasks’ functions.  Patch provided by Yurii Karabas.

   - bpo-42392(12): Remove loop parameter from ‘asyncio.open_connection’
     and ‘asyncio.start_server’ functions.  Patch provided by Yurii
     Karabas.

   - bpo-28468(13): Add *note platform.freedesktop_os_release(): 7ca.
     function to parse freedesktop.org ‘os-release’ files.

   - bpo-42299(14): Removed the ‘formatter’ module, which was deprecated
     in Python 3.4.  It is somewhat obsolete, little used, and not
     tested.  It was originally scheduled to be removed in Python 3.6,
     but such removals were delayed until after Python 2.7 EOL. Existing
     users should copy whatever classes they use into their code.  Patch
     by Donghee Na and and Terry J. Reedy.

   - bpo-26131(15): Deprecate zipimport.zipimporter.load_module() in
     favour of exec_module().

   - bpo-41818(16): Updated tests for the pty library.  test_basic() has
     been changed to test_openpty(); this additionally checks if slave
     termios and slave winsize are being set properly by pty.openpty().
     In order to add support for FreeBSD, NetBSD, OpenBSD, and Darwin,
     this also adds test_master_read(), which demonstrates that
     pty.spawn() should not depend on an OSError to exit from its copy
     loop.

   - bpo-42392(17): Remove loop parameter from ‘__init__’ in all
     ‘asyncio.locks’ and ‘asyncio.Queue’ classes.  Patch provided by
     Yurii Karabas.

   - bpo-15450(18): Make *note filecmp.dircmp: ee4. respect subclassing.
     Now the *note filecmp.dircmp.subdirs: 181f. behaves as expected
     when subclassing dircmp.

   - bpo-42413(19): The exception *note socket.timeout: 7d8. is now an
     alias of *note TimeoutError: 7d9.

   - bpo-31904(20): Support signal module on VxWorks.

   - bpo-42406(21): We fixed an issue in ‘pickle.whichmodule’ in which
     importing ‘multiprocessing’ could change the how pickle identifies
     which module an object belongs to, potentially breaking the
     unpickling of those objects.

   - bpo-42403(22): Simplify the *note importlib: 6b. external bootstrap
     code: ‘importlib._bootstrap_external’ now uses regular imports to
     import builtin modules.  When it is imported, the builtin *note
     __import__(): 879. function is already fully working and so can be
     used to import builtin modules like *note sys: c3.  Patch by Victor
     Stinner.

   - bpo-1635741(23): Convert _sre module types to heap types (PEP 384).
     Patch by Erlend E. Aasland.

   - bpo-42375(24): subprocess module update for DragonFlyBSD support.

   - bpo-41713(25): Port the ‘_signal’ extension module to the
     multi-phase initialization API ( PEP 489(26)).  Patch by Victor
     Stinner and Mohamed Koubaa.

   - bpo-37205(27): *note time.time(): 239, *note time.perf_counter():
     a2b. and *note time.monotonic(): 238. functions can no longer fail
     with a Python fatal error, instead raise a regular Python exception
     on failure.

   - bpo-42328(28): Fixed *note tkinter.ttk.Style.map(): 1820.  The
     function accepts now the representation of the default state as
     empty sequence (as returned by ‘Style.map()’).  The structure of
     the result is now the same on all platform and does not depend on
     the value of ‘wantobjects’.

   - bpo-42345(29): Fix various issues with ‘typing.Literal’ parameter
     handling (flatten, deduplicate, use type to cache key).  Patch
     provided by Yurii Karabas.

   - bpo-37205(30): *note time.perf_counter(): a2b. on Windows and *note
     time.monotonic(): 238. on macOS are now system-wide.  Previously,
     they used an offset computed at startup to reduce the precision
     loss caused by the float type.  Use *note time.perf_counter_ns():
     a88. and *note time.monotonic_ns(): a87. added in Python 3.7 to
     avoid this precision loss.

   - bpo-42318(31): Fixed support of non-BMP characters in *note
     tkinter: d9. on macOS.

   - bpo-42350(32): Fix the *note threading.Thread: 8f0. class at fork:
     do nothing if the thread is already stopped (ex: fork called at
     Python exit).  Previously, an error was logged in the child
     process.

   - bpo-42333(33): Port _ssl extension module to heap types.

   - bpo-42014(34): The ‘onerror’ callback from ‘shutil.rmtree’ now
     receives correct function when ‘os.open’ fails.

   - bpo-42237(35): Fix ‘os.sendfile()’ on illumos.

   - bpo-42308(36): Add *note threading.__excepthook__: 7ee. to allow
     retrieving the original value of *note threading.excepthook(): 7ef.
     in case it is set to a broken or a different value.  Patch by Mario
     Corchero.

   - bpo-42131(37): Implement PEP 451/spec methods on
     zipimport.zipimporter: find_spec(), create_module(), and
     exec_module().

     This also allows for the documented deprecation of find_loader(),
     find_module(), and load_module().

   - bpo-41877(38): Mock objects which are not unsafe will now raise an
     AttributeError if an attribute with the prefix asert, aseert, or
     assrt is accessed, in addition to this already happening for the
     prefixes assert or assret.

   - bpo-42264(39): ‘sqlite3.OptimizedUnicode’ has been undocumented and
     obsolete since Python 3.3, when it was made an alias to *note str:
     3f2.  It is now deprecated, scheduled for removal in Python 3.12.

   - bpo-42251(40): Added *note threading.gettrace(): 7ea. and *note
     threading.getprofile(): 7eb. to retrieve the functions set by *note
     threading.settrace(): 7ec. and *note threading.setprofile(): 7ed.
     respectively.  Patch by Mario Corchero.

   - bpo-42249(41): Fixed writing binary Plist files larger than 4 GiB.

   - bpo-42236(42): On Unix, the *note os.device_encoding(): 1794.
     function now returns ‘'UTF-8'’ rather than the device encoding if
     the *note Python UTF-8 Mode: 5fc. is enabled.

   - bpo-41754(43): webbrowser: Ignore 'NotADirectoryError' when calling
     ‘xdg-settings’.

   - bpo-42183(44): Fix a stack overflow error for asyncio Task or
     Future repr().

     The overflow occurs under some circumstances when a Task or Future
     recursively returns itself.

   - bpo-42140(45): Improve asyncio.wait function to create the futures
     set just one time.

   - bpo-42133(46): Update various modules in the stdlib to fall back on
     ‘__spec__.loader’ when ‘__loader__’ isn't defined on a module.

   - bpo-26131(47): The ‘load_module()’ methods found in ‘importlib’ now
     trigger a ‘DeprecationWarning’.

   - bpo-39825(48): Windows: Change
     ‘sysconfig.get_config_var('EXT_SUFFIX')’ to the expected full
     ‘platform_tag.extension’ format.  Previously it was hard-coded to
     ‘.pyd’, now it is compatible with ‘distutils.sysconfig’ and will
     result in something like ‘.cp38-win_amd64.pyd’.  This brings
     windows into conformance with the other platforms.

   - bpo-26389(49): The *note traceback.format_exception(): 7f1, *note
     traceback.format_exception_only(): 7f2, and *note
     traceback.print_exception(): 7f3. functions can now take an
     exception object as a positional-only argument.

   - bpo-41889(50): Enum: fix regression involving inheriting a multiply
     inherited enum

   - bpo-41861(51): Convert *note sqlite3: ba. to use heap types (PEP
     384).  Patch by Erlend E. Aasland.

   - bpo-40624(52): Added support for the XPath ‘!=’ operator in
     xml.etree

   - bpo-28850(53): Fix *note pprint.PrettyPrinter.format(): 1821.
     overrides being ignored for contents of small containers.  The
     ‘pprint._safe_repr()’ function was removed.

   - bpo-41625(54): Expose the ‘splice()’ as *note os.splice(): 7bd. in
     the *note os: 91. module.  Patch by Pablo Galindo

   - bpo-34215(55): Clarify the error message for *note
     asyncio.IncompleteReadError: 1822. when ‘expected’ is ‘None’.

   - bpo-41543(56): Add async context manager support for
     contextlib.nullcontext.

   - bpo-21041(57): *note pathlib.PurePath.parents: 7c4. now supports
     negative indexing.  Patch contributed by Yaroslav Pankovych.

   - bpo-41332(58): Added missing connect_accepted_socket() method to
     ‘asyncio.AbstractEventLoop’.

   - bpo-12800(59): Extracting a symlink from a tarball should succeed
     and overwrite the symlink if it already exists.  The fix is to
     remove the existing file or symlink before extraction.  Based on
     patch by Chris AtLee, Jeffrey Kintscher, and Senthil Kumaran.

   - bpo-40968(60): *note urllib.request: f4. and *note http.client: 65.
     now send ‘http/1.1’ ALPN extension during TLS handshake when no
     custom context is supplied.

   - bpo-41001(61): Add *note os.eventfd(): 7bc. to provide a low level
     interface for Linux's event notification file descriptor.

   - bpo-40816(62): Add AsyncContextDecorator to contextlib to support
     async context manager as a decorator.

   - bpo-40550(63): Fix time-of-check/time-of-action issue in
     subprocess.Popen.send_signal.

   - bpo-39411(64): Add an ‘is_async’ identifier to *note pyclbr: a2.'s
     ‘Function’ objects.  Patch by Batuhan Taskaya

   - bpo-35498(65): Add slice support to *note pathlib.PurePath.parents:
     7c4.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=5054

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42562

   (3) https://bugs.python.org/issue?@action=redirect&bpo=17735

   (4) https://bugs.python.org/issue?@action=redirect&bpo=42116

   (5) https://bugs.python.org/issue?@action=redirect&bpo=42532

   (6) https://bugs.python.org/issue?@action=redirect&bpo=38200

   (7) https://bugs.python.org/issue?@action=redirect&bpo=41818

   (8) https://bugs.python.org/issue?@action=redirect&bpo=42487

   (9) https://bugs.python.org/issue?@action=redirect&bpo=42482

   (10) https://bugs.python.org/issue?@action=redirect&bpo=41818

   (11) https://bugs.python.org/issue?@action=redirect&bpo=42392

   (12) https://bugs.python.org/issue?@action=redirect&bpo=42392

   (13) https://bugs.python.org/issue?@action=redirect&bpo=28468

   (14) https://bugs.python.org/issue?@action=redirect&bpo=42299

   (15) https://bugs.python.org/issue?@action=redirect&bpo=26131

   (16) https://bugs.python.org/issue?@action=redirect&bpo=41818

   (17) https://bugs.python.org/issue?@action=redirect&bpo=42392

   (18) https://bugs.python.org/issue?@action=redirect&bpo=15450

   (19) https://bugs.python.org/issue?@action=redirect&bpo=42413

   (20) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (21) https://bugs.python.org/issue?@action=redirect&bpo=42406

   (22) https://bugs.python.org/issue?@action=redirect&bpo=42403

   (23) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (24) https://bugs.python.org/issue?@action=redirect&bpo=42375

   (25) https://bugs.python.org/issue?@action=redirect&bpo=41713

   (26) https://peps.python.org/pep-0489/

   (27) https://bugs.python.org/issue?@action=redirect&bpo=37205

   (28) https://bugs.python.org/issue?@action=redirect&bpo=42328

   (29) https://bugs.python.org/issue?@action=redirect&bpo=42345

   (30) https://bugs.python.org/issue?@action=redirect&bpo=37205

   (31) https://bugs.python.org/issue?@action=redirect&bpo=42318

   (32) https://bugs.python.org/issue?@action=redirect&bpo=42350

   (33) https://bugs.python.org/issue?@action=redirect&bpo=42333

   (34) https://bugs.python.org/issue?@action=redirect&bpo=42014

   (35) https://bugs.python.org/issue?@action=redirect&bpo=42237

   (36) https://bugs.python.org/issue?@action=redirect&bpo=42308

   (37) https://bugs.python.org/issue?@action=redirect&bpo=42131

   (38) https://bugs.python.org/issue?@action=redirect&bpo=41877

   (39) https://bugs.python.org/issue?@action=redirect&bpo=42264

   (40) https://bugs.python.org/issue?@action=redirect&bpo=42251

   (41) https://bugs.python.org/issue?@action=redirect&bpo=42249

   (42) https://bugs.python.org/issue?@action=redirect&bpo=42236

   (43) https://bugs.python.org/issue?@action=redirect&bpo=41754

   (44) https://bugs.python.org/issue?@action=redirect&bpo=42183

   (45) https://bugs.python.org/issue?@action=redirect&bpo=42140

   (46) https://bugs.python.org/issue?@action=redirect&bpo=42133

   (47) https://bugs.python.org/issue?@action=redirect&bpo=26131

   (48) https://bugs.python.org/issue?@action=redirect&bpo=39825

   (49) https://bugs.python.org/issue?@action=redirect&bpo=26389

   (50) https://bugs.python.org/issue?@action=redirect&bpo=41889

   (51) https://bugs.python.org/issue?@action=redirect&bpo=41861

   (52) https://bugs.python.org/issue?@action=redirect&bpo=40624

   (53) https://bugs.python.org/issue?@action=redirect&bpo=28850

   (54) https://bugs.python.org/issue?@action=redirect&bpo=41625

   (55) https://bugs.python.org/issue?@action=redirect&bpo=34215

   (56) https://bugs.python.org/issue?@action=redirect&bpo=41543

   (57) https://bugs.python.org/issue?@action=redirect&bpo=21041

   (58) https://bugs.python.org/issue?@action=redirect&bpo=41332

   (59) https://bugs.python.org/issue?@action=redirect&bpo=12800

   (60) https://bugs.python.org/issue?@action=redirect&bpo=40968

   (61) https://bugs.python.org/issue?@action=redirect&bpo=41001

   (62) https://bugs.python.org/issue?@action=redirect&bpo=40816

   (63) https://bugs.python.org/issue?@action=redirect&bpo=40550

   (64) https://bugs.python.org/issue?@action=redirect&bpo=39411

   (65) https://bugs.python.org/issue?@action=redirect&bpo=35498


File: python.info,  Node: Documentation<29>,  Next: Tests<32>,  Prev: Library<34>,  Up: Python 3 10 0 alpha 3

1.23.35.4 Documentation
.......................

   - bpo-42238(1): Tentative to deprecate ‘make suspicious’ by first
     removing it from the CI and documentation builds, but keeping it
     around for manual uses.

   - bpo-42153(2): Fix the URL for the IMAP protocol documents.

   - bpo-41028(3): Language and version switchers, previously maintained
     in every cpython branches, are now handled by docsbuild-script.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42238

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42153

   (3) https://bugs.python.org/issue?@action=redirect&bpo=41028


File: python.info,  Node: Tests<32>,  Next: Build<34>,  Prev: Documentation<29>,  Up: Python 3 10 0 alpha 3

1.23.35.5 Tests
...............

   - bpo-41473(1): Re-enable test_gdb on gdb 9.2 and newer:
     ‘https://bugzilla.redhat.com/show_bug.cgi?id=1866884’ bug is fixed
     in gdb 10.1.

   - bpo-42553(2): Fix ‘test_asyncio.test_call_later()’ race condition:
     don't measure asyncio performance in the ‘call_later()’ unit test.
     The test failed randomly on the CI.

   - bpo-31904(3): Fix test_netrc on VxWorks: create temporary
     directories using temp_cwd().

   - bpo-31904(4): skip test_getaddrinfo_ipv6_scopeid_symbolic and
     test_getnameinfo_ipv6_scopeid_symbolic on VxWorks

   - bpo-31904(5): skip test_test of test_mailcap on VxWorks

   - bpo-31904(6): add shell requirement for test_pipes

   - bpo-31904(7): skip some tests related to fifo on VxWorks

   - bpo-31904(8): Fix test_doctest.py failures for VxWorks.

   - bpo-40754(9): Include ‘_testinternalcapi’ module in Windows
     installer for test suite

   - bpo-41561(10): test_ssl: skip test_min_max_version_mismatch when
     TLS 1.0 is not available

   - bpo-31904(11): Fix os module failures for VxWorks RTOS.

   - bpo-31904(12): Fix fifo test cases for VxWorks RTOS.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41473

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42553

   (3) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (5) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (6) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (7) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (8) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (9) https://bugs.python.org/issue?@action=redirect&bpo=40754

   (10) https://bugs.python.org/issue?@action=redirect&bpo=41561

   (11) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (12) https://bugs.python.org/issue?@action=redirect&bpo=31904


File: python.info,  Node: Build<34>,  Next: Windows<30>,  Prev: Tests<32>,  Up: Python 3 10 0 alpha 3

1.23.35.6 Build
...............

   - bpo-31904(1): remove libnet dependency from detect_socket() for
     VxWorks

   - bpo-42398(2): Fix a race condition in "make regen-all" when make
     -jN option is used to run jobs in parallel.  The clinic.py script
     now only use atomic write to write files.  Moveover, generated
     files are now left unchanged if the content does not change, to not
     change the file modification time.

   - bpo-41617(3): Fix building ‘pycore_bitutils.h’ internal header on
     old clang version without ‘__builtin_bswap16()’ (ex: Xcode 4.6.3 on
     Mac OS X 10.7).  Patch by Joshua Root and Victor Stinner.

   - bpo-38823(4): It is no longer possible to build the ‘_ctypes’
     extension module without ‘wchar_t’ type: remove ‘CTYPES_UNICODE’
     macro.  Anyway, the ‘wchar_t’ type is required to build Python.
     Patch by Victor Stinner.

   - bpo-42087(5): Support was removed for AIX 5.3 and below.  See
     bpo-40680(6).

   - bpo-40998(7): Addressed three compiler warnings found by undefined
     behavior sanitizer (ubsan).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42398

   (3) https://bugs.python.org/issue?@action=redirect&bpo=41617

   (4) https://bugs.python.org/issue?@action=redirect&bpo=38823

   (5) https://bugs.python.org/issue?@action=redirect&bpo=42087

   (6) https://bugs.python.org/issue?@action=redirect&bpo=40680

   (7) https://bugs.python.org/issue?@action=redirect&bpo=40998


File: python.info,  Node: Windows<30>,  Next: macOS<25>,  Prev: Build<34>,  Up: Python 3 10 0 alpha 3

1.23.35.7 Windows
.................

   - bpo-42120(1): Remove macro definition of ‘copysign’ (to
     ‘_copysign’) in headers.

   - bpo-38506(2): The Windows launcher now properly handles Python 3.10
     when listing installed Python versions.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42120

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38506


File: python.info,  Node: macOS<25>,  Next: IDLE<22>,  Prev: Windows<30>,  Up: Python 3 10 0 alpha 3

1.23.35.8 macOS
...............

   - bpo-42504(1): Fix build on macOS Big Sur when
     MACOSX_DEPLOYMENT_TARGET=11

   - bpo-41116(2): Ensure distutils.unixxcompiler.find_library_file can
     find system provided libraries on macOS 11.

   - bpo-41100(3): Add support for macOS 11 and Apple Silicon systems.

     It is now possible to build "Universal 2" binaries using
     "-enable-universalsdk -with-universal-archs=universal2".

     Binaries build on later macOS versions can be deployed back to
     older versions (tested up to macOS 10.9), when using the correct
     deployment target.  This is tested using Xcode 11 and later.

   - bpo-42232(4): Added Darwin specific madvise options to mmap module.

   - bpo-38443(5): The ‘--enable-universalsdk’ and
     ‘--with-universal-archs’ options for the configure script now check
     that the specified architectures can be used.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42504

   (2) https://bugs.python.org/issue?@action=redirect&bpo=41116

   (3) https://bugs.python.org/issue?@action=redirect&bpo=41100

   (4) https://bugs.python.org/issue?@action=redirect&bpo=42232

   (5) https://bugs.python.org/issue?@action=redirect&bpo=38443


File: python.info,  Node: IDLE<22>,  Next: Tools/Demos<15>,  Prev: macOS<25>,  Up: Python 3 10 0 alpha 3

1.23.35.9 IDLE
..............

   - bpo-42508(1): Keep IDLE running on macOS. Remove obsolete
     workaround that prevented running files with shortcuts when using
     new universal2 installers built on macOS 11.

   - bpo-42426(2): Fix reporting offset of the RE error in searchengine.

   - bpo-42415(3): Get docstrings for IDLE calltips more often by using
     inspect.getdoc.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42508

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42426

   (3) https://bugs.python.org/issue?@action=redirect&bpo=42415


File: python.info,  Node: Tools/Demos<15>,  Next: C API<33>,  Prev: IDLE<22>,  Up: Python 3 10 0 alpha 3

1.23.35.10 Tools/Demos
......................

   - bpo-42212(1): The smelly.py script now also checks the Python
     dynamic library and extension modules, not only the Python static
     library.  Make also the script more verbose: explain what it does.

   - bpo-36310(2): Allow ‘Tools/i18n/pygettext.py’ to detect calls to
     ‘gettext’ in f-strings.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42212

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36310


File: python.info,  Node: C API<33>,  Prev: Tools/Demos<15>,  Up: Python 3 10 0 alpha 3

1.23.35.11 C API
................

   - bpo-42423(1): The *note PyType_FromSpecWithBases(): 524. and *note
     PyType_FromModuleAndSpec(): 4f7. functions now accept a single
     class as the 'bases' argument.

   - bpo-1635741(2): Port *note select: af. extension module to
     multiphase initialization ( PEP 489(3)).

   - bpo-1635741(4): Port _posixsubprocess extension module to
     multiphase initialization ( PEP 489(5)).

   - bpo-1635741(6): Port _posixshmem extension module to multiphase
     initialization ( PEP 489(7))

   - bpo-1635741(8): Port _struct extension module to multiphase
     initialization ( PEP 489(9))

   - bpo-1635741(10): Port ‘spwd’ extension module to multiphase
     initialization ( PEP 489(11))

   - bpo-1635741(12): Port *note gc: 56. extension module to multiphase
     initialization ( PEP 489(13))

   - bpo-1635741(14): Port _queue extension module to multiphase
     initialization ( PEP 489(15))

   - bpo-39573(16): Convert *note Py_TYPE(): 724. and *note Py_SIZE():
     726. back to macros to allow using them as an l-value.  Many third
     party C extension modules rely on the ability of using Py_TYPE()
     and Py_SIZE() to set an object type and size: ‘Py_TYPE(obj) =
     type;’ and ‘Py_SIZE(obj) = size;’.

   - bpo-1635741(17): Port *note symtable: c2. extension module to
     multiphase initialization ( PEP 489(18))

   - bpo-1635741(19): Port *note grp: 5c. and *note pwd: a0. extension
     modules to multiphase initialization ( PEP 489(20))

   - bpo-1635741(21): Port _random extension module to multiphase
     initialization ( PEP 489(22))

   - bpo-1635741(23): Port _hashlib extension module to multiphase
     initialization ( PEP 489(24))

   - bpo-41713(25): Removed the undocumented ‘PyOS_InitInterrupts()’
     function.  Initializing Python already implicitly installs signal
     handlers: see *note PyConfig.install_signal_handlers: 863.  Patch
     by Victor Stinner.

   - bpo-40170(26): The ‘Py_TRASHCAN_BEGIN’ macro no longer accesses
     PyTypeObject attributes, but now can get the condition by calling
     the new private ‘_PyTrash_cond()’ function which hides
     implementation details.

   - bpo-42260(27): *note Py_GetPath(): 37e, *note Py_GetPrefix(): 380,
     *note Py_GetExecPrefix(): 37c, *note Py_GetProgramFullPath(): 382,
     *note Py_GetPythonHome(): 385. and *note Py_GetProgramName(): 384.
     functions now return ‘NULL’ if called before *note Py_Initialize():
     851. (before Python is initialized).  Use the new *note Python
     Initialization Configuration API: 372. to get the *note Python Path
     Configuration.: 852.  Patch by Victor Stinner.

   - bpo-42260(28): The *note PyConfig_Read(): 734. function now only
     parses *note PyConfig.argv: 38e. arguments once: *note
     PyConfig.parse_argv: 182b. is set to ‘2’ after arguments are
     parsed.  Since Python arguments are strippped from *note
     PyConfig.argv: 38e, parsing arguments twice would parse the
     application options as Python options.

   - bpo-42262(29): Added *note Py_NewRef(): 83e. and *note
     Py_XNewRef(): 83f. functions to increment the reference count of an
     object and return the object.  Patch by Victor Stinner.

   - bpo-42260(30): When *note Py_Initialize(): 851. is called twice,
     the second call now updates more *note sys: c3. attributes for the
     configuration, rather than only *note sys.argv: 11fd.  Patch by
     Victor Stinner.

   - bpo-41832(31): The *note PyType_FromModuleAndSpec(): 4f7. function
     now accepts NULL ‘tp_doc’ slot.

   - bpo-1635741(32): Added *note PyModule_AddObjectRef(): 308.
     function: similar to *note PyModule_AddObject(): 309. but don't
     steal a reference to the value on success.  Patch by Victor
     Stinner.

   - bpo-42171(33): The *note METH_FASTCALL: 151b. calling convention is
     added to the limited API. The functions *note PyModule_AddType():
     919, *note PyType_FromModuleAndSpec(): 4f7, *note
     PyType_GetModule(): 912. and *note PyType_GetModuleState(): 913.
     are added to the limited API on Windows.

   - bpo-42085(34): Add dedicated entry to PyAsyncMethods for sending
     values

   - bpo-41073(35): *note PyType_GetSlot(): 840. can now accept static
     types.

   - bpo-30459(36): *note PyList_SET_ITEM(): 306, *note
     PyTuple_SET_ITEM(): 305. and *note PyCell_SET(): 853. macros can no
     longer be used as l-value or r-value.  For example, ‘x =
     PyList_SET_ITEM(a, b, c)’ and ‘PyList_SET_ITEM(a, b, c) = x’ now
     fail with a compiler error.  It prevents bugs like ‘if
     (PyList_SET_ITEM (a, b, c) < 0) ...’ test.  Patch by Zackery Spytz
     and Victor Stinner.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42423

   (2) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (3) https://peps.python.org/pep-0489/

   (4) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (5) https://peps.python.org/pep-0489/

   (6) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (7) https://peps.python.org/pep-0489/

   (8) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (9) https://peps.python.org/pep-0489/

   (10) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (11) https://peps.python.org/pep-0489/

   (12) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (13) https://peps.python.org/pep-0489/

   (14) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (15) https://peps.python.org/pep-0489/

   (16) https://bugs.python.org/issue?@action=redirect&bpo=39573

   (17) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (18) https://peps.python.org/pep-0489/

   (19) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (20) https://peps.python.org/pep-0489/

   (21) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (22) https://peps.python.org/pep-0489/

   (23) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (24) https://peps.python.org/pep-0489/

   (25) https://bugs.python.org/issue?@action=redirect&bpo=41713

   (26) https://bugs.python.org/issue?@action=redirect&bpo=40170

   (27) https://bugs.python.org/issue?@action=redirect&bpo=42260

   (28) https://bugs.python.org/issue?@action=redirect&bpo=42260

   (29) https://bugs.python.org/issue?@action=redirect&bpo=42262

   (30) https://bugs.python.org/issue?@action=redirect&bpo=42260

   (31) https://bugs.python.org/issue?@action=redirect&bpo=41832

   (32) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (33) https://bugs.python.org/issue?@action=redirect&bpo=42171

   (34) https://bugs.python.org/issue?@action=redirect&bpo=42085

   (35) https://bugs.python.org/issue?@action=redirect&bpo=41073

   (36) https://bugs.python.org/issue?@action=redirect&bpo=30459


File: python.info,  Node: Python 3 10 0 alpha 2,  Next: Python 3 10 0 alpha 1,  Prev: Python 3 10 0 alpha 3,  Up: Changelog（更動日誌）

1.23.36 Python 3.10.0 alpha 2
-----------------------------

'Release date: 2020-11-03'

* Menu:

* Security: Security<22>.
* Core and Builtins: Core and Builtins<36>.
* Library: Library<35>.
* Documentation: Documentation<30>.
* Tests: Tests<33>.
* Build: Build<35>.
* Windows: Windows<31>.
* macOS: macOS<26>.
* IDLE: IDLE<23>.
* C API: C API<34>.


File: python.info,  Node: Security<22>,  Next: Core and Builtins<36>,  Up: Python 3 10 0 alpha 2

1.23.36.1 Security
..................

   - bpo-42103(1): Prevented potential DoS attack via CPU and RAM
     exhaustion when processing malformed Apple Property List files in
     binary format.

   - bpo-42051(2): The *note plistlib: 99. module no longer accepts
     entity declarations in XML plist files to avoid XML
     vulnerabilities.  This should not affect users as entity
     declarations are not used in regular plist files.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42103

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42051


File: python.info,  Node: Core and Builtins<36>,  Next: Library<35>,  Prev: Security<22>,  Up: Python 3 10 0 alpha 2

1.23.36.2 Core and Builtins
...........................

   - bpo-42236(1): If the ‘nl_langinfo(CODESET)’ function returns an
     empty string, Python now uses UTF-8 as the filesystem encoding.
     Patch by Victor Stinner.

   - bpo-42218(2): Fixed a bug in the PEG parser that was causing
     crashes in debug mode.  Now errors are checked in left-recursive
     rules to avoid cases where such errors do not get handled in time
     and appear as long-distance crashes in other places.

   - bpo-42214(3): Fixed a possible crash in the PEG parser when
     checking for the '!=' token in the ‘barry_as_flufl’ rule.  Patch by
     Pablo Galindo.

   - bpo-42206(4): Propagate and raise the errors caused by
     ‘PyAST_Validate()’ in the parser.

   - bpo-41796(5): The *note ast: 7. module internal state is now per
     interpreter.  Patch by Victor Stinner.

   - bpo-42143(6): Fix handling of errors during creation of
     ‘PyFunctionObject’, which resulted in operations on uninitialized
     memory.  Patch by Yonatan Goldschmidt.

   - bpo-41659(7): Fix a bug in the parser, where a curly brace
     following a ‘primary’ didn't fail immediately.  This led to invalid
     expressions like ‘a {b}’ to throw a *note SyntaxError: 173. with a
     wrong offset, or invalid expressions ending with a curly brace like
     ‘a {’ to not fail immediately in the REPL.

   - bpo-42150(8): Fix possible buffer overflow in the new parser when
     checking for continuation lines.  Patch by Pablo Galindo.

   - bpo-42123(9): Run the parser two times.  On the first run, disable
     all the rules that only generate better error messages to gain
     performance.  If there's a parse failure, run the parser a second
     time with those enabled.

   - bpo-42093(10): The ‘LOAD_ATTR’ instruction now uses new "per opcode
     cache" mechanism and it is about 36% faster now.  Patch by Pablo
     Galindo and Yury Selivanov.

   - bpo-42030(11): Support for the legacy AIX-specific shared library
     loading support has been removed.  All versions of AIX since 4.3
     have supported and defaulted to using the common Unix mechanism
     instead.

   - bpo-41984(12): The garbage collector now tracks all user-defined
     classes.  Patch by Brandt Bucher.

   - bpo-41993(13): Fixed potential issues with removing not completely
     initialized module from ‘sys.modules’ when import fails.

   - bpo-41979(14): Star-unpacking is now allowed for with item's
     targets in the PEG parser.

   - bpo-41974(15): Removed special methods ‘__int__’, ‘__float__’,
     ‘__floordiv__’, ‘__mod__’, ‘__divmod__’, ‘__rfloordiv__’,
     ‘__rmod__’ and ‘__rdivmod__’ of the *note complex: 2c9. class.
     They always raised a *note TypeError: 4dd.

   - bpo-41902(16): Micro optimization when compute *note sq_item: 182f.
     and *note mp_subscript: 1830. of *note range: 8e7.  Patch by
     Donghee Na.

   - bpo-41894(17): When loading a native module and a load failure
     occurs, prevent a possible UnicodeDecodeError when not running in a
     UTF-8 locale by decoding the load error message using the current
     locale's encoding.

   - bpo-41902(18): Micro optimization for range.index if step is 1.
     Patch by Donghee Na.

   - bpo-41435(19): Add ‘sys._current_exceptions()’ function to retrieve
     a dictionary mapping each thread's identifier to the topmost
     exception currently active in that thread at the time the function
     is called.

   - bpo-38605(20): Enable ‘from __future__ import annotations’ ( PEP
     563(21)) by default.  The values found in ‘__annotations__’ dicts
     are now strings, e.g.  ‘{"x": "int"}’ instead of ‘{"x": int}’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42236

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42218

   (3) https://bugs.python.org/issue?@action=redirect&bpo=42214

   (4) https://bugs.python.org/issue?@action=redirect&bpo=42206

   (5) https://bugs.python.org/issue?@action=redirect&bpo=41796

   (6) https://bugs.python.org/issue?@action=redirect&bpo=42143

   (7) https://bugs.python.org/issue?@action=redirect&bpo=41659

   (8) https://bugs.python.org/issue?@action=redirect&bpo=42150

   (9) https://bugs.python.org/issue?@action=redirect&bpo=42123

   (10) https://bugs.python.org/issue?@action=redirect&bpo=42093

   (11) https://bugs.python.org/issue?@action=redirect&bpo=42030

   (12) https://bugs.python.org/issue?@action=redirect&bpo=41984

   (13) https://bugs.python.org/issue?@action=redirect&bpo=41993

   (14) https://bugs.python.org/issue?@action=redirect&bpo=41979

   (15) https://bugs.python.org/issue?@action=redirect&bpo=41974

   (16) https://bugs.python.org/issue?@action=redirect&bpo=41902

   (17) https://bugs.python.org/issue?@action=redirect&bpo=41894

   (18) https://bugs.python.org/issue?@action=redirect&bpo=41902

   (19) https://bugs.python.org/issue?@action=redirect&bpo=41435

   (20) https://bugs.python.org/issue?@action=redirect&bpo=38605

   (21) https://peps.python.org/pep-0563/


File: python.info,  Node: Library<35>,  Next: Documentation<30>,  Prev: Core and Builtins<36>,  Up: Python 3 10 0 alpha 2

1.23.36.3 Library
.................

   - bpo-35455(1): On Solaris, *note thread_time(): 8da. is now
     implemented with ‘gethrvtime()’ because
     ‘clock_gettime(CLOCK_THREAD_CPUTIME_ID)’ is not always available.
     Patch by Jakub Kulik.

   - bpo-42233(2): The *note repr(): 7a1. of *note typing: ed. types
     containing *note Generic Alias Types: 656. previously did not show
     the parameterized types in the ‘GenericAlias’.  They have now been
     changed to do so.

   - bpo-29566(3): ‘binhex.binhex()’ consistently writes macOS 9 line
     endings.

   - bpo-26789(4): The *note logging.FileHandler: 17a1. class now keeps
     a reference to the builtin *note open(): 4c0. function to be able
     to open or reopen the file during Python finalization.  Fix errors
     like: ‘NameError: name 'open' is not defined’.  Patch by Victor
     Stinner.

   - bpo-42157(5): Removed the ‘unicodedata.ucnhash_CAPI’ attribute
     which was an internal PyCapsule object.  The related private
     ‘_PyUnicode_Name_CAPI’ structure was moved to the internal C API.
     Patch by Victor Stinner.

   - bpo-42157(6): Convert the *note unicodedata: ee. extension module
     to the multiphase initialization API ( PEP 489(7)) and convert the
     ‘unicodedata.UCD’ static type to a heap type.  Patch by Mohamed
     Koubaa and Victor Stinner.

   - bpo-42146(8): Fix memory leak in *note subprocess.Popen(): 17d. in
     case an uid (gid) specified in ‘user’ (‘group’, ‘extra_groups’)
     overflows ‘uid_t’ (‘gid_t’).

   - bpo-42103(9): ‘InvalidFileException’ and *note RecursionError: d12.
     are now the only errors caused by loading malformed binary Plist
     file (previously ValueError and TypeError could be raised in some
     specific cases).

   - bpo-41490(10): In ‘importlib.resources’, ‘.path’ method is more
     aggressive about releasing handles to zipfile objects early,
     enabling use-cases like certifi to leave the context open but
     delete the underlying zip file.

   - bpo-41052(11): Pickling heap types implemented in C with protocols
     0 and 1 raises now an error instead of producing incorrect data.

   - bpo-42089(12): In ‘importlib.metadata.PackageNotFoundError’, make
     reference to the package metadata being missing to improve the user
     experience.

   - bpo-41491(13): plistlib: fix parsing XML plists with hexadecimal
     integer values

   - bpo-42065(14): Fix an incorrectly formatted error from
     ‘_codecs.charmap_decode()’ when called with a mapped value outside
     the range of valid Unicode code points.  PR by Max Bernstein.

   - bpo-41966(15): Fix pickling pure Python *note datetime.time: 1b2.
     subclasses.  Patch by Dean Inwood.

   - bpo-19270(16): *note sched.scheduler.cancel(): 1832. will now
     cancel the correct event, if two events with same priority are
     scheduled for the same time.  Patch by Bar Harel.

   - bpo-28660(17): *note textwrap.wrap(): 1432. now attempts to break
     long words after hyphens when ‘break_long_words=True’ and
     ‘break_on_hyphens=True’.

   - bpo-35823(18): Use ‘vfork()’ instead of ‘fork()’ for *note
     subprocess.Popen(): 17d. on Linux to improve performance in cases
     where it is deemed safe.

   - bpo-42043(19): Add support for ‘zipfile.Path’ inheritance.
     ‘zipfile.Path.is_file()’ now returns False for non-existent names.
     ‘zipfile.Path’ objects now expose a ‘.filename’ attribute and rely
     on that to resolve ‘.name’ and ‘.parent’ when the ‘Path’ object is
     at the root of the zipfile.

   - bpo-42021(20): Fix possible ref leaks in *note sqlite3: ba. module
     init.

   - bpo-39101(21): Fixed tests using IsolatedAsyncioTestCase from
     hanging on BaseExceptions.

   - bpo-41976(22): Fixed a bug that was causing *note
     ctypes.util.find_library(): cf0. to return ‘None’ when triying to
     locate a library in an environment when gcc>=9 is available and
     ‘ldconfig’ is not.  Patch by Pablo Galindo

   - bpo-41943(23): Fix bug where TestCase.assertLogs doesn't correctly
     filter messages by level.

   - bpo-41923(24): Implement PEP 613(25), introducing *note
     typing.TypeAlias: 76d. annotation.

   - bpo-41905(26): A new function in abc: 'update_abstractmethods' to
     re-calculate an abstract class's abstract status.  In addition,
     'dataclass' has been changed to call this function.

   - bpo-23706(27): Added 'newline' parameter to
     ‘pathlib.Path.write_text()’.

   - bpo-41876(28): Tkinter font class repr uses font name

   - bpo-41831(29): ‘str()’ for the ‘type’ attribute of the
     ‘tkinter.Event’ object always returns now the numeric code returned
     by Tk instead of the name of the event type.

   - bpo-39337(30): ‘encodings.normalize_encoding()’ now ignores
     non-ASCII characters.

   - bpo-41747(31): Ensure all methods that generated from *note
     dataclasses.dataclass(): 1af. objects now have the proper
     ‘__qualname__’ attribute referring to the class they belong to.
     Patch by Batuhan Taskaya.

   - bpo-30681(32): Handle exceptions caused by unparsable date headers
     when using email "default" policy.  Patch by Tim Bell, Georges Toth

   - bpo-41586(33): Add F_SETPIPE_SZ and F_GETPIPE_SZ to fcntl module.
     Allow setting pipesize on subprocess.Popen.

   - bpo-41229(34): Add ‘contextlib.aclosing’ for deterministic cleanup
     of async generators which is analogous to ‘contextlib.closing’ for
     non-async generators.  Patch by Joongi Kim and John Belmonte.

   - bpo-16396(35): Allow ‘ctypes.wintypes’ to be imported on
     non-Windows systems.

   - bpo-4356(36): Add a key function to the bisect module.

   - bpo-40592(37): *note shutil.which(): 45b. now ignores empty entries
     in ‘PATHEXT’ instead of treating them as a match.

   - bpo-40492(38): Fix ‘--outfile’ for *note cProfile: 20. / *note
     profile: 9d. not writing the output file in the original directory
     when the program being profiled changes the working directory.  PR
     by Anthony Sottile.

   - bpo-34204(39): The *note shelve: b1. module now uses *note
     pickle.DEFAULT_PROTOCOL: 7d2. by default instead of *note pickle:
     95. protocol ‘3’.

   - bpo-27321(40): Fixed KeyError exception when flattening an email to
     a string attempts to replace a non-existent
     Content-Transfer-Encoding header.

   - bpo-38976(41): The *note http.cookiejar: 66. module now supports
     the parsing of cookies in CURL-style cookiejar files through
     MozillaCookieJar on all platforms.  Previously, such cookie entries
     would be silently ignored when loading a cookiejar with such
     entries.

     Additionally, the HTTP Only attribute is persisted in the object,
     and will be correctly written to file if the MozillaCookieJar
     object is subsequently dumped.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35455

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42233

   (3) https://bugs.python.org/issue?@action=redirect&bpo=29566

   (4) https://bugs.python.org/issue?@action=redirect&bpo=26789

   (5) https://bugs.python.org/issue?@action=redirect&bpo=42157

   (6) https://bugs.python.org/issue?@action=redirect&bpo=42157

   (7) https://peps.python.org/pep-0489/

   (8) https://bugs.python.org/issue?@action=redirect&bpo=42146

   (9) https://bugs.python.org/issue?@action=redirect&bpo=42103

   (10) https://bugs.python.org/issue?@action=redirect&bpo=41490

   (11) https://bugs.python.org/issue?@action=redirect&bpo=41052

   (12) https://bugs.python.org/issue?@action=redirect&bpo=42089

   (13) https://bugs.python.org/issue?@action=redirect&bpo=41491

   (14) https://bugs.python.org/issue?@action=redirect&bpo=42065

   (15) https://bugs.python.org/issue?@action=redirect&bpo=41966

   (16) https://bugs.python.org/issue?@action=redirect&bpo=19270

   (17) https://bugs.python.org/issue?@action=redirect&bpo=28660

   (18) https://bugs.python.org/issue?@action=redirect&bpo=35823

   (19) https://bugs.python.org/issue?@action=redirect&bpo=42043

   (20) https://bugs.python.org/issue?@action=redirect&bpo=42021

   (21) https://bugs.python.org/issue?@action=redirect&bpo=39101

   (22) https://bugs.python.org/issue?@action=redirect&bpo=41976

   (23) https://bugs.python.org/issue?@action=redirect&bpo=41943

   (24) https://bugs.python.org/issue?@action=redirect&bpo=41923

   (25) https://peps.python.org/pep-0613/

   (26) https://bugs.python.org/issue?@action=redirect&bpo=41905

   (27) https://bugs.python.org/issue?@action=redirect&bpo=23706

   (28) https://bugs.python.org/issue?@action=redirect&bpo=41876

   (29) https://bugs.python.org/issue?@action=redirect&bpo=41831

   (30) https://bugs.python.org/issue?@action=redirect&bpo=39337

   (31) https://bugs.python.org/issue?@action=redirect&bpo=41747

   (32) https://bugs.python.org/issue?@action=redirect&bpo=30681

   (33) https://bugs.python.org/issue?@action=redirect&bpo=41586

   (34) https://bugs.python.org/issue?@action=redirect&bpo=41229

   (35) https://bugs.python.org/issue?@action=redirect&bpo=16396

   (36) https://bugs.python.org/issue?@action=redirect&bpo=4356

   (37) https://bugs.python.org/issue?@action=redirect&bpo=40592

   (38) https://bugs.python.org/issue?@action=redirect&bpo=40492

   (39) https://bugs.python.org/issue?@action=redirect&bpo=34204

   (40) https://bugs.python.org/issue?@action=redirect&bpo=27321

   (41) https://bugs.python.org/issue?@action=redirect&bpo=38976


File: python.info,  Node: Documentation<30>,  Next: Tests<33>,  Prev: Library<35>,  Up: Python 3 10 0 alpha 2

1.23.36.4 Documentation
.......................

   - bpo-42061(1): Document __format__ functionality for IP addresses.

   - bpo-41910(2): Document the default implementation of
     ‘object.__eq__’.

   - bpo-42010(3): Clarify that subscription expressions are also valid
     for certain *note classes: 1834. and *note types: 1835. in the
     standard library, and for user-defined classes and types if the
     classmethod ‘__class_getitem__()’ is provided.

   - bpo-41805(4): Documented *note generic alias type: 656. and *note
     types.GenericAlias: 78f.  Also added an entry in glossary for *note
     generic types: 3df.

   - bpo-39693(5): Fix tarfile's extractfile documentation

   - bpo-39416(6): Document some restrictions on the default string
     representations of numeric classes.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42061

   (2) https://bugs.python.org/issue?@action=redirect&bpo=41910

   (3) https://bugs.python.org/issue?@action=redirect&bpo=42010

   (4) https://bugs.python.org/issue?@action=redirect&bpo=41805

   (5) https://bugs.python.org/issue?@action=redirect&bpo=39693

   (6) https://bugs.python.org/issue?@action=redirect&bpo=39416


File: python.info,  Node: Tests<33>,  Next: Build<35>,  Prev: Documentation<30>,  Up: Python 3 10 0 alpha 2

1.23.36.5 Tests
...............

   - bpo-41739(1): Fix
     test_logging.test_race_between_set_target_and_flush(): the test now
     waits until all threads complete to avoid leaking running threads.

   - bpo-41970(2): Avoid a test failure in ‘test_lib2to3’ if the module
     has already imported at the time the test executes.  Patch by Pablo
     Galindo.

   - bpo-41944(3): Tests for CJK codecs no longer call ‘eval()’ on
     content received via HTTP.

   - bpo-41306(4): Fixed a failure in ‘test_tk.test_widgets.ScaleTest’
     happening when executing the test with Tk 8.6.10.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41739

   (2) https://bugs.python.org/issue?@action=redirect&bpo=41970

   (3) https://bugs.python.org/issue?@action=redirect&bpo=41944

   (4) https://bugs.python.org/issue?@action=redirect&bpo=41306


File: python.info,  Node: Build<35>,  Next: Windows<31>,  Prev: Tests<33>,  Up: Python 3 10 0 alpha 2

1.23.36.6 Build
...............

   - bpo-38980(1): Add ‘-fno-semantic-interposition’ to both the compile
     and link line when building with ‘--enable-optimizations’.  Patch
     by Victor Stinner and Pablo Galindo.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38980


File: python.info,  Node: Windows<31>,  Next: macOS<26>,  Prev: Build<35>,  Up: Python 3 10 0 alpha 2

1.23.36.7 Windows
.................

   - bpo-38439(1): Updates the icons for IDLE in the Windows Store
     package.

   - bpo-38252(2): Use 8-byte step to detect ASCII sequence in 64-bit
     Windows build.

   - bpo-39107(3): Update Tcl and Tk to 8.6.10 in Windows installer.

   - bpo-41557(4): Update Windows installer to use SQLite 3.33.0.

   - bpo-38324(5): Avoid Unicode errors when accessing certain locale
     data on Windows.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38439

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38252

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39107

   (4) https://bugs.python.org/issue?@action=redirect&bpo=41557

   (5) https://bugs.python.org/issue?@action=redirect&bpo=38324


File: python.info,  Node: macOS<26>,  Next: IDLE<23>,  Prev: Windows<31>,  Up: Python 3 10 0 alpha 2

1.23.36.8 macOS
...............

   - bpo-41471(1): Ignore invalid prefix lengths in system proxy
     excludes.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41471


File: python.info,  Node: IDLE<23>,  Next: C API<34>,  Prev: macOS<26>,  Up: Python 3 10 0 alpha 2

1.23.36.9 IDLE
..............

   - bpo-33987(1): Mostly finish using ttk widgets, mainly for editor,
     settings, and searches.  Some patches by Mark Roseman.

   - bpo-40511(2): Typing opening and closing parentheses inside the
     parentheses of a function call will no longer cause unnecessary
     "flashing" off and on of an existing open call-tip, e.g.  when
     typed in a string literal.

   - bpo-38439(3): Add a 256×256 pixel IDLE icon to the Windows .ico
     file.  Created by Andrew Clover.  Remove the low-color gif
     variations from the .ico file.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33987

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40511

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38439


File: python.info,  Node: C API<34>,  Prev: IDLE<23>,  Up: Python 3 10 0 alpha 2

1.23.36.10 C API
................

   - bpo-42157(1): The private ‘_PyUnicode_Name_CAPI’ structure of the
     PyCapsule API ‘unicodedata.ucnhash_CAPI’ has been moved to the
     internal C API. Patch by Victor Stinner.

   - bpo-42015(2): Fix potential crash in deallocating method objects
     when dynamically allocated *note PyMethodDef: 1446.'s lifetime is
     managed through the ‘self’ argument of a *note PyCFunction: 13e2.

   - bpo-40423(3): The *note subprocess: c1. module and ‘os.closerange’
     will now use the ‘close_range(low, high, flags)’ syscall when it is
     available for more efficient closing of ranges of descriptors.

   - bpo-41845(4): *note PyObject_GenericGetDict(): 183c. is available
     again in the limited API when targeting 3.10 or later.

   - bpo-40422(5): Add ‘_Py_closerange’ function to provide performant
     closing of a range of file descriptors.

   - bpo-41986(6): ‘Py_FileSystemDefaultEncodeErrors’ and ‘Py_UTF8Mode’
     are available again in limited API.

   - bpo-41756(7): Add ‘PyIter_Send’ function to allow sending value
     into generator/coroutine/iterator without raising StopIteration
     exception to signal return.

   - bpo-41784(8): Added ‘PyUnicode_AsUTF8AndSize’ to the limited C API.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42157

   (2) https://bugs.python.org/issue?@action=redirect&bpo=42015

   (3) https://bugs.python.org/issue?@action=redirect&bpo=40423

   (4) https://bugs.python.org/issue?@action=redirect&bpo=41845

   (5) https://bugs.python.org/issue?@action=redirect&bpo=40422

   (6) https://bugs.python.org/issue?@action=redirect&bpo=41986

   (7) https://bugs.python.org/issue?@action=redirect&bpo=41756

   (8) https://bugs.python.org/issue?@action=redirect&bpo=41784


File: python.info,  Node: Python 3 10 0 alpha 1,  Next: Python 3 9 0 beta 1,  Prev: Python 3 10 0 alpha 2,  Up: Changelog（更動日誌）

1.23.37 Python 3.10.0 alpha 1
-----------------------------

'Release date: 2020-10-05'

* Menu:

* Security: Security<23>.
* Core and Builtins: Core and Builtins<37>.
* Library: Library<36>.
* Documentation: Documentation<31>.
* Tests: Tests<34>.
* Build: Build<36>.
* Windows: Windows<32>.
* macOS: macOS<27>.
* IDLE: IDLE<24>.
* C API: C API<35>.


File: python.info,  Node: Security<23>,  Next: Core and Builtins<37>,  Up: Python 3 10 0 alpha 1

1.23.37.1 Security
..................

   - bpo-41304(1): Fixes ‘python3x._pth’ being ignored on Windows,
     caused by the fix for bpo-29778(2) (CVE-2020-15801(3)).

   - bpo-41162(4): Audit hooks are now cleared later during finalization
     to avoid missing events.

   - bpo-29778(5): Ensure ‘python3.dll’ is loaded from correct locations
     when Python is embedded (CVE-2020-15523(6)).

   - bpo-41004(7): The __hash__() methods of ipaddress.IPv4Interface and
     ipaddress.IPv6Interface incorrectly generated constant hash values
     of 32 and 128 respectively.  This resulted in always causing hash
     collisions.  The fix uses hash() to generate hash values for the
     tuple of (address, mask length, network address).

   - bpo-39603(8): Prevent http header injection by rejecting control
     characters in http.client.putrequest(...).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41304

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29778

   (3) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15801

   (4) https://bugs.python.org/issue?@action=redirect&bpo=41162

   (5) https://bugs.python.org/issue?@action=redirect&bpo=29778

   (6) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15523

   (7) https://bugs.python.org/issue?@action=redirect&bpo=41004

   (8) https://bugs.python.org/issue?@action=redirect&bpo=39603


File: python.info,  Node: Core and Builtins<37>,  Next: Library<36>,  Prev: Security<23>,  Up: Python 3 10 0 alpha 1

1.23.37.2 Core and Builtins
...........................

   - bpo-41909(1): Fixed stack overflow in *note issubclass(): 765. and
     *note isinstance(): 3e8. when getting the ‘__bases__’ attribute
     leads to infinite recursion.

   - bpo-41922(2): Speed up calls to ‘reversed()’ by using the PEP
     590(3) ‘vectorcall’ calling convention.  Patch by Donghee Na.

   - bpo-41873(4): Calls to ‘float()’ are now faster due to the
     ‘vectorcall’ calling convention.  Patch by Dennis Sweeney.

   - bpo-41870(5): Speed up calls to ‘bool()’ by using the PEP 590(6)
     ‘vectorcall’ calling convention.  Patch by Donghee Na.

   - bpo-1635741(7): Port the ‘_bisect’ module to the multi-phase
     initialization API ( PEP 489(8)).

   - bpo-39934(9): Correctly count control blocks in 'except' in
     compiler.  Ensures that a syntax error, rather a fatal error,
     occurs for deeply nested, named exception handlers.

   - bpo-41780(10): Fix ‘__dir__()’ of *note types.GenericAlias: 78f.
     Patch by Batuhan Taskaya.

   - bpo-1635741(11): Port the ‘_lsprof’ extension module to multi-phase
     initialization ( PEP 489(12)).

   - bpo-1635741(13): Port the *note cmath: 11. extension module to
     multi-phase initialization ( PEP 489(14)).

   - bpo-1635741(15): Port the ‘_scproxy’ extension module to
     multi-phase initialization ( PEP 489(16)).

   - bpo-1635741(17): Port the *note termios: ca. extension module to
     multi-phase initialization ( PEP 489(18)).

   - bpo-1635741(19): Convert the ‘_sha256’ extension module types to
     heap types.

   - bpo-41690(20): Fix a possible stack overflow in the parser when
     parsing functions and classes with a huge amount of arguments.
     Patch by Pablo Galindo.

   - bpo-1635741(21): Port the ‘_overlapped’ extension module to
     multi-phase initialization ( PEP 489(22)).

   - bpo-1635741(23): Port the ‘_curses_panel’ extension module to
     multi-phase initialization ( PEP 489(24)).

   - bpo-1635741(25): Port the ‘_opcode’ extension module to multi-phase
     initialization ( PEP 489(26)).

   - bpo-41681(27): Fixes the wrong error description in the error
     raised by using 2 ‘,’ in format string in f-string and *note
     str.format(): 5c7.

   - bpo-41675(28): The implementation of *note signal.siginterrupt():
     10ce. now uses ‘sigaction()’ (if it is available in the system)
     instead of the deprecated ‘siginterrupt()’.  Patch by Pablo
     Galindo.

   - bpo-41670(29): Prevent line trace being skipped on platforms not
     compiled with ‘USE_COMPUTED_GOTOS’.  Fixes issue where some lines
     nested within a try-except block were not being traced on Windows.

   - bpo-41654(30): Fix a crash that occurred when destroying subclasses
     of *note MemoryError: 15bc.  Patch by Pablo Galindo.

   - bpo-1635741(31): Port the *note zlib: 119. extension module to
     multi-phase initialization ( PEP 489(32)).

   - bpo-41631(33): The ‘_ast’ module uses again a global state.  Using
     a module state per module instance is causing subtle practical
     problems.  For example, the Mercurial project replaces the
     ‘__import__()’ function to implement lazy import, whereas Python
     expected that ‘import _ast’ always return a fully initialized
     ‘_ast’ module.

   - bpo-40077(34): Convert ‘_operator’ to use *note PyType_FromSpec():
     523.

   - bpo-1653741(35): Port ‘_sha3’ to multi-phase init.  Convert static
     types to heap types.

   - bpo-1635741(36): Port the ‘_blake2’ extension module to the
     multi-phase initialization API ( PEP 489(37)).

   - bpo-41533(38): Free the stack allocated in ‘va_build_stack’ if
     ‘do_mkstack’ fails and the stack is not a ‘small_stack’.

   - bpo-41531(39): Fix a bug that was dropping keys when compiling dict
     literals with more than 0xFFFF elements.  Patch by Pablo Galindo.

   - bpo-41525(40): The output of ‘python --help’ contains now only
     ASCII characters.

   - bpo-1635741(41): Port the ‘_sha1’, ‘_sha512’, and ‘_md5’ extension
     modules to multi-phase initialization API ( PEP 489(42)).

   - bpo-41431(43): Optimize ‘dict_merge()’ for copying dict (e.g.
     ‘dict(d)’ and ‘{}.update(d)’).

   - bpo-41428(44): Implement PEP 604.  This supports (int | str) etc.
     in place of Union[str, int].

   - bpo-41340(45): Removed fallback implementation for ‘strdup’.

   - bpo-38156(46): Handle interrupts that come after EOF correctly in
     ‘PyOS_StdioReadline’.

   - bpo-41342(47): *note round(): 126d. with integer argument is now
     faster (9-60%).

   - bpo-41334(48): Constructors *note str(): 3f2, *note bytes(): 1a5.
     and *note bytearray(): 4e3. are now faster (around 30-40% for small
     objects).

   - bpo-41295(49): Resolve a regression in CPython 3.8.4 where defining
     "__setattr__" in a multi-inheritance setup and calling up the
     hierarchy chain could fail if builtins/extension types were
     involved in the base types.

   - bpo-41323(50): Bytecode optimizations are performed directly on the
     control flow graph.  This will result in slightly more compact code
     objects in some circumstances.

   - bpo-41247(51): Always cache the running loop holder when running
     ‘asyncio.set_running_loop’.

   - bpo-41252(52): Fix incorrect refcounting in _ssl.c's
     ‘_servername_callback()’.

   - bpo-1635741(53): Port *note multiprocessing: 86. to multi-phase
     initialization

   - bpo-1635741(54): Port ‘winapi’ to multiphase initialization

   - bpo-41215(55): Use non-NULL default values in the PEG parser
     keyword list to overcome a bug that was preventing Python from
     being properly compiled when using the XLC compiler.  Patch by
     Pablo Galindo.

   - bpo-41218(56): Python 3.8.3 had a regression where compiling with
     ast.PyCF_ALLOW_TOP_LEVEL_AWAIT would aggressively mark list
     comprehension with CO_COROUTINE. Now only list comprehension making
     use of async/await will tagged as so.

   - bpo-1635741(57): Port *note faulthandler: 4e. to multiphase
     initialization.

   - bpo-1635741(58): Port ‘sha256’ to multiphase initialization

   - bpo-41175(59): Guard against a NULL pointer dereference within
     bytearrayobject triggered by the ‘bytearray() + bytearray()’
     operation.

   - bpo-41100(60): add arm64 to the allowable Mac OS arches in
     mpdecimal.h

   - bpo-41094(61): Fix decoding errors with audit when open files with
     non-ASCII names on non-UTF-8 locale.

   - bpo-39960(62): The "hackcheck" that prevents sneaking around a
     type's __setattr__() by calling the superclass method was rewritten
     to allow C implemented heap types.

   - bpo-41084(63): Prefix the error message with 'f-string: ', when
     parsing an f-string expression which throws a *note SyntaxError:
     173.

   - bpo-40521(64): Empty frozensets are no longer singletons.

   - bpo-41076(65): Pre-feed the parser with the location of the
     f-string expression, not the f-string itself, which allows us to
     skip the shifting of the AST node locations after the parsing is
     completed.

   - bpo-41056(66): Fixes a reference to deallocated stack space during
     startup when constructing sys.path involving a relative symlink
     when code was supplied via -c.  (discovered via Coverity)

   - bpo-41061(67): Fix incorrect expressions and asserts in hashtable
     code and tests.

   - bpo-41052(68): Opt out serialization/deserialization for
     _random.Random

   - bpo-40939(69): Rename ‘PyPegen*’ functions to ‘PyParser*’, so that
     we can remove the old set of ‘PyParser*’ functions that were using
     the old parser, but keep everything backwards-compatible.

   - bpo-35975(70): Stefan Behnel reported that cf_feature_version is
     used even when PyCF_ONLY_AST is not set.  This is against the
     intention and against the documented behavior, so it's been fixed.

   - bpo-40939(71): Remove the remaining files from the old parser and
     the ‘symbol’ module.

   - bpo-40077(72): Convert ‘_bz2’ to use *note PyType_FromSpec(): 523.

   - bpo-41006(73): The ‘encodings.latin_1’ module is no longer imported
     at startup.  Now it is only imported when it is the filesystem
     encoding or the stdio encoding.

   - bpo-40636(74): *note zip(): 774. now supports PEP 618(75)'s
     ‘strict’ parameter, which raises a *note ValueError: 1e7. if the
     arguments are exhausted at different lengths.  Patch by Brandt
     Bucher.

   - bpo-1635741(76): Port ‘_gdbm’ to multiphase initialization.

   - bpo-40985(77): Fix a bug that caused the *note SyntaxError: 173.
     text to be empty when a file ends with a line ending in a line
     continuation character (i.e.  backslash).  The error text should
     contain the text of the last line.

   - bpo-40958(78): Fix a possible buffer overflow in the PEG parser
     when gathering information for emitting syntax errors.  Patch by
     Pablo Galindo.

   - bpo-1635741(79): Port ‘_dbm’ to multiphase initialization.

   - bpo-40957(80): Fix refleak in _Py_fopen_obj() when PySys_Audit()
     fails

   - bpo-40950(81): Add a state to the ‘nis’ module ( PEP 3121(82)) and
     apply the multiphase initialization.  Patch by Donghee Na.

   - bpo-40947(83): The Python *note Path Configuration: 852. now takes
     *note PyConfig.platlibdir: 1840. in account.

   - bpo-40939(84): Remove the old parser, the ‘parser’ module and all
     associated support code, command-line options and environment
     variables.  Patch by Pablo Galindo.

   - bpo-40847(85): Fix a bug where a line with only a line continuation
     character is not considered a blank line at tokenizer level.  In
     such cases, more than a single ‘NEWLINE’ token was emitted.  The
     old parser was working around the issue, but the new parser threw a
     *note SyntaxError: 173. for valid input due to this.  For example,
     an empty line following a line continuation character was
     interpreted as a *note SyntaxError: 173.

   - bpo-40890(86): Each dictionary view now has a ‘mapping’ attribute
     that provides a *note types.MappingProxyType: 414. wrapping the
     original dictionary.  Patch contributed by Dennis Sweeney.

   - bpo-40889(87): Improved the performance of symmetric difference
     operations on dictionary item views.  Patch by Dennis Sweeney.

   - bpo-40904(88): Fix possible segfault in the new PEG parser when
     parsing f-string containing yield statements with no value
     (‘f"{yield}"’).  Patch by Pablo Galindo

   - bpo-40903(89): Fixed a possible segfault in the new PEG parser when
     producing error messages for invalid assignments of the form
     ‘p=p=’.  Patch by Pablo Galindo

   - bpo-40880(90): Fix invalid memory read in the new parser when
     checking newlines in string literals.  Patch by Pablo Galindo.

   - bpo-40883(91): Fix memory leak in when parsing f-strings in the new
     parser.  Patch by Pablo Galindo

   - bpo-40870(92): Raise *note ValueError: 1e7. when validating custom
     AST's where the constants ‘True’, ‘False’ and ‘None’ are used
     within a *note ast.Name: 1841. node.

   - bpo-40854(93): Allow overriding *note sys.platlibdir: 8dc. via a
     new *note PYTHONPLATLIBDIR: 1842. environment variable.

   - bpo-40826(94): Fix GIL usage in ‘PyOS_Readline()’: lock the GIL to
     set an exception and pass the Python thread state when checking if
     there is a pending signal.

   - bpo-1635741(95): Port *note fcntl: 4f. to multiphase
     initialization.

   - bpo-19468(96): Delete unnecessary instance check in
     importlib.reload().  Patch by Furkan Önder.

   - bpo-40824(97): Unexpected errors in calling the ‘__iter__’ method
     are no longer masked by ‘TypeError’ in the *note in: 2c5. operator
     and functions *note contains(): 87f, *note indexOf(): 880. and
     *note countOf(): 881. of the *note operator: 8f. module.

   - bpo-40792(98): Attributes ‘start’, ‘stop’ and ‘step’ of the *note
     range: 8e7. object now always has exact type *note int: 23c.
     Previously, they could have been an instance of a subclass of
     ‘int’.

   - bpo-40780(99): Fix a corner case where g-style string formatting of
     a float failed to remove trailing zeros.

   - bpo-38964(100): When there's a *note SyntaxError: 173. in the
     expression part of an fstring, the filename attribute of the *note
     SyntaxError: 173. gets correctly set to the name of the file the
     fstring resides in.

   - bpo-40750(101): Support the "-d" debug flag in the new PEG parser.
     Patch by Pablo Galindo

   - bpo-40217(102): Instances of types created with *note
     PyType_FromSpecWithBases(): 524. will no longer automatically visit
     their class object when traversing references in the garbage
     collector.  The user is expected to manually visit the object's
     class.  Patch by Pablo Galindo.

   - bpo-39573(103): *note Py_TYPE(): 724. is changed to the inline
     static function.  Patch by Donghee Na.

   - bpo-40696(104): Fix a hang that can arise after *note
     generator.throw(): 4a0. due to a cycle in the exception context
     chain.

   - bpo-40521(105): Each interpreter now its has own free lists,
     singletons and caches:

        * Free lists: float, tuple, list, dict, frame, context,
          asynchronous generator, MemoryError.

        * Singletons: empty tuple, empty bytes string, empty Unicode
          string, single byte character, single Unicode (latin1)
          character.

        * Slice cache.

     They are no longer shared by all interpreters.

   - bpo-40679(106): Certain *note TypeError: 4dd. messages about
     missing or extra arguments now include the function's *note
     qualified name: 1843.  Patch by Dennis Sweeney.

   - bpo-29590(107): Make the stack trace correct after calling *note
     generator.throw(): 4a0. on a generator that has yielded from a
     ‘yield from’.

   - bpo-4022(108): Improve performance of generators by not raising
     internal StopIteration.

   - bpo-1635741(109): Port *note mmap: 83. to multiphase
     initialization.

   - bpo-1635741(110): Port ‘_lzma’ to multiphase initialization.

   - bpo-37999(111): Builtin and extension functions that take integer
     arguments no longer accept *note Decimal: 27c.s, *note Fraction:
     1c7.s and other objects that can be converted to integers only with
     a loss (e.g.  that have the *note __int__(): 6c0. method but do not
     have the *note __index__(): 6c1. method).

   - bpo-29882(112): Add *note int.bit_count(): 770, counting the number
     of ones in the binary representation of an integer.  Patch by
     Niklas Fiekas.

   - bpo-36982(113): Use ncurses extended color functions when available
     to support terminals with 256 colors, and add the new function
     *note curses.has_extended_color_support(): 799. to indicate whether
     extended color support is provided by the underlying ncurses
     library.

   - bpo-19569(114): Add the private macros ‘_Py_COMP_DIAG_PUSH’,
     ‘_Py_COMP_DIAG_IGNORE_DEPR_DECLS’, and ‘_Py_COMP_DIAG_POP’.

   - bpo-26680(115): The int type now supports the x.is_integer() method
     for compatibility with float.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41909

   (2) https://bugs.python.org/issue?@action=redirect&bpo=41922

   (3) https://peps.python.org/pep-0590/

   (4) https://bugs.python.org/issue?@action=redirect&bpo=41873

   (5) https://bugs.python.org/issue?@action=redirect&bpo=41870

   (6) https://peps.python.org/pep-0590/

   (7) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (8) https://peps.python.org/pep-0489/

   (9) https://bugs.python.org/issue?@action=redirect&bpo=39934

   (10) https://bugs.python.org/issue?@action=redirect&bpo=41780

   (11) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (12) https://peps.python.org/pep-0489/

   (13) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (14) https://peps.python.org/pep-0489/

   (15) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (16) https://peps.python.org/pep-0489/

   (17) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (18) https://peps.python.org/pep-0489/

   (19) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (20) https://bugs.python.org/issue?@action=redirect&bpo=41690

   (21) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (22) https://peps.python.org/pep-0489/

   (23) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (24) https://peps.python.org/pep-0489/

   (25) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (26) https://peps.python.org/pep-0489/

   (27) https://bugs.python.org/issue?@action=redirect&bpo=41681

   (28) https://bugs.python.org/issue?@action=redirect&bpo=41675

   (29) https://bugs.python.org/issue?@action=redirect&bpo=41670

   (30) https://bugs.python.org/issue?@action=redirect&bpo=41654

   (31) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (32) https://peps.python.org/pep-0489/

   (33) https://bugs.python.org/issue?@action=redirect&bpo=41631

   (34) https://bugs.python.org/issue?@action=redirect&bpo=40077

   (35) https://bugs.python.org/issue?@action=redirect&bpo=1653741

   (36) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (37) https://peps.python.org/pep-0489/

   (38) https://bugs.python.org/issue?@action=redirect&bpo=41533

   (39) https://bugs.python.org/issue?@action=redirect&bpo=41531

   (40) https://bugs.python.org/issue?@action=redirect&bpo=41525

   (41) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (42) https://peps.python.org/pep-0489/

   (43) https://bugs.python.org/issue?@action=redirect&bpo=41431

   (44) https://bugs.python.org/issue?@action=redirect&bpo=41428

   (45) https://bugs.python.org/issue?@action=redirect&bpo=41340

   (46) https://bugs.python.org/issue?@action=redirect&bpo=38156

   (47) https://bugs.python.org/issue?@action=redirect&bpo=41342

   (48) https://bugs.python.org/issue?@action=redirect&bpo=41334

   (49) https://bugs.python.org/issue?@action=redirect&bpo=41295

   (50) https://bugs.python.org/issue?@action=redirect&bpo=41323

   (51) https://bugs.python.org/issue?@action=redirect&bpo=41247

   (52) https://bugs.python.org/issue?@action=redirect&bpo=41252

   (53) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (54) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (55) https://bugs.python.org/issue?@action=redirect&bpo=41215

   (56) https://bugs.python.org/issue?@action=redirect&bpo=41218

   (57) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (58) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (59) https://bugs.python.org/issue?@action=redirect&bpo=41175

   (60) https://bugs.python.org/issue?@action=redirect&bpo=41100

   (61) https://bugs.python.org/issue?@action=redirect&bpo=41094

   (62) https://bugs.python.org/issue?@action=redirect&bpo=39960

   (63) https://bugs.python.org/issue?@action=redirect&bpo=41084

   (64) https://bugs.python.org/issue?@action=redirect&bpo=40521

   (65) https://bugs.python.org/issue?@action=redirect&bpo=41076

   (66) https://bugs.python.org/issue?@action=redirect&bpo=41056

   (67) https://bugs.python.org/issue?@action=redirect&bpo=41061

   (68) https://bugs.python.org/issue?@action=redirect&bpo=41052

   (69) https://bugs.python.org/issue?@action=redirect&bpo=40939

   (70) https://bugs.python.org/issue?@action=redirect&bpo=35975

   (71) https://bugs.python.org/issue?@action=redirect&bpo=40939

   (72) https://bugs.python.org/issue?@action=redirect&bpo=40077

   (73) https://bugs.python.org/issue?@action=redirect&bpo=41006

   (74) https://bugs.python.org/issue?@action=redirect&bpo=40636

   (75) https://peps.python.org/pep-0618/

   (76) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (77) https://bugs.python.org/issue?@action=redirect&bpo=40985

   (78) https://bugs.python.org/issue?@action=redirect&bpo=40958

   (79) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (80) https://bugs.python.org/issue?@action=redirect&bpo=40957

   (81) https://bugs.python.org/issue?@action=redirect&bpo=40950

   (82) https://peps.python.org/pep-3121/

   (83) https://bugs.python.org/issue?@action=redirect&bpo=40947

   (84) https://bugs.python.org/issue?@action=redirect&bpo=40939

   (85) https://bugs.python.org/issue?@action=redirect&bpo=40847

   (86) https://bugs.python.org/issue?@action=redirect&bpo=40890

   (87) https://bugs.python.org/issue?@action=redirect&bpo=40889

   (88) https://bugs.python.org/issue?@action=redirect&bpo=40904

   (89) https://bugs.python.org/issue?@action=redirect&bpo=40903

   (90) https://bugs.python.org/issue?@action=redirect&bpo=40880

   (91) https://bugs.python.org/issue?@action=redirect&bpo=40883

   (92) https://bugs.python.org/issue?@action=redirect&bpo=40870

   (93) https://bugs.python.org/issue?@action=redirect&bpo=40854

   (94) https://bugs.python.org/issue?@action=redirect&bpo=40826

   (95) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (96) https://bugs.python.org/issue?@action=redirect&bpo=19468

   (97) https://bugs.python.org/issue?@action=redirect&bpo=40824

   (98) https://bugs.python.org/issue?@action=redirect&bpo=40792

   (99) https://bugs.python.org/issue?@action=redirect&bpo=40780

   (100) https://bugs.python.org/issue?@action=redirect&bpo=38964

   (101) https://bugs.python.org/issue?@action=redirect&bpo=40750

   (102) https://bugs.python.org/issue?@action=redirect&bpo=40217

   (103) https://bugs.python.org/issue?@action=redirect&bpo=39573

   (104) https://bugs.python.org/issue?@action=redirect&bpo=40696

   (105) https://bugs.python.org/issue?@action=redirect&bpo=40521

   (106) https://bugs.python.org/issue?@action=redirect&bpo=40679

   (107) https://bugs.python.org/issue?@action=redirect&bpo=29590

   (108) https://bugs.python.org/issue?@action=redirect&bpo=4022

   (109) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (110) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (111) https://bugs.python.org/issue?@action=redirect&bpo=37999

   (112) https://bugs.python.org/issue?@action=redirect&bpo=29882

   (113) https://bugs.python.org/issue?@action=redirect&bpo=36982

   (114) https://bugs.python.org/issue?@action=redirect&bpo=19569

   (115) https://bugs.python.org/issue?@action=redirect&bpo=26680


File: python.info,  Node: Library<36>,  Next: Documentation<31>,  Prev: Core and Builtins<37>,  Up: Python 3 10 0 alpha 1

1.23.37.3 Library
.................

   - bpo-41900(1): C14N 2.0 serialisation in xml.etree.ElementTree
     failed for unprefixed attributes when a default namespace was
     defined.

   - bpo-41887(2): Strip leading spaces and tabs on *note
     ast.literal_eval(): bbf.  Also document stripping of spaces and
     tabs for *note eval(): 163.

   - bpo-41773(3): Note in documentation that *note random.choices():
     c6d. doesn't support non-finite weights, raise *note ValueError:
     1e7. when given non-finite weights.

   - bpo-41840(4): Fix a bug in the *note symtable: c2. module that was
     causing module-scope global variables to not be reported as both
     local and global.  Patch by Pablo Galindo.

   - bpo-41842(5): Add *note codecs.unregister(): 78c. function to
     unregister a codec search function.

   - bpo-40564(6): In ‘zipfile.Path’, mutate the passed ZipFile object
     type instead of making a copy.  Prevents issues when both the local
     copy and the caller’s copy attempt to close the same file handle.

   - bpo-40670(7): More reliable validation of statements in *note
     timeit.Timer: 1433.  It now accepts "empty" statements (only
     whitespaces and comments) and rejects misindentent statements.

   - bpo-41833(8): The *note threading.Thread: 8f0. constructor now uses
     the target name if the 'target' argument is specified but the
     'name' argument is omitted.

   - bpo-41817(9): fix ‘tkinter.EventType’ Enum so all members are
     strings, and none are tuples

   - bpo-41810(10): *note types.EllipsisType: 7f5, *note
     types.NotImplementedType: 7f7. and *note types.NoneType: 7f6. have
     been reintroduced, providing a new set of types readily
     interpretable by static type checkers.

   - bpo-41815(11): Fix SQLite3 segfault when backing up closed
     database.  Patch contributed by Peter David McCormick.

   - bpo-41816(12): StrEnum added: it ensures that all members are
     already strings or string candidates

   - bpo-41517(13): fix bug allowing Enums to be extended via multiple
     inheritance

   - bpo-39587(14): use the correct mix-in data type when constructing
     Enums

   - bpo-41792(15): Add is_typeddict function to typing.py to check if a
     type is a TypedDict class

     Previously there was no way to check that without using private
     API.  See the relevant issue in python/typing(16).

   - bpo-41789(17): Honor ‘object’ overrides in ‘Enum’ class creation
     (specifically, ‘__str__’, ‘__repr__’, ‘__format__’, and
     ‘__reduce_ex__’).

   - bpo-32218(18): ‘enum.Flag’ and ‘enum.IntFlag’ members are now
     iterable.

   - bpo-39651(19): Fix a race condition in the ‘call_soon_threadsafe()’
     method of ‘asyncio.ProactorEventLoop’: do nothing if the self-pipe
     socket has been closed.

   - bpo-1635741(20): Port the ‘mashal’ extension module to the
     multi-phase initialization API ( PEP 489(21)).

   - bpo-1635741(22): Port the ‘_string’ extension module to the
     multi-phase initialization API ( PEP 489(23)).

   - bpo-41732(24): Added an *note iterator: 192. to *note memoryview:
     40f.

   - bpo-41720(25): Fixed ‘turtle.Vec2D.__rmul__()’ for arguments which
     are not int or float.

   - bpo-41696(26): Fix handling of debug mode in *note asyncio.run():
     423.  This allows setting ‘PYTHONASYNCIODEBUG’ or ‘-X dev’ to
     enable asyncio debug mode when using *note asyncio.run(): 423.

   - bpo-41687(27): Fix implementation of sendfile to be compatible with
     Solaris.

   - bpo-41662(28): No longer override exceptions raised in ‘__len__()’
     of a sequence of parameters in *note sqlite3: ba. with *note
     ProgrammingError: 49a.

   - bpo-39010(29): Restarting a ‘ProactorEventLoop’ on Windows no
     longer logs spurious ‘ConnectionResetErrors’.

   - bpo-41638(30): *note ProgrammingError: 49a. message for absent
     parameter in *note sqlite3: ba. contains now the name of the
     parameter instead of its index when parameters are supplied as a
     dict.

   - bpo-41662(31): Fixed crash when mutate list of parameters during
     iteration in *note sqlite3: ba.

   - bpo-41513(32): Improved the accuracy of math.hypot().  Internally,
     each step is computed with extra precision so that the result is
     now almost always correctly rounded.

   - bpo-41609(33): The pdb whatis command correctly reports instance
     methods as 'Method' rather than 'Function'.

   - bpo-39994(34): Fixed pprint's handling of dict subclasses that
     override __repr__.

   - bpo-32751(35): When cancelling the task due to a timeout, *note
     asyncio.wait_for(): 5a4. will now wait until the cancellation is
     complete also in the case when 'timeout' is <= 0, like it does with
     positive timeouts.

   - bpo-37658(36): *note asyncio.wait_for(): 5a4. now properly handles
     races between cancellation of itself and the completion of the
     wrapped awaitable.

   - bpo-40782(37): Change the method
     asyncio.AbstractEventLoop.run_in_executor to not be a coroutine.

   - bpo-41520(38): Fix *note codeop: 15. regression that prevented
     turning compile warnings into errors.

   - bpo-41528(39): turtle uses math module functions to convert degrees
     to radians and vice versa and to calculate vector norm

   - bpo-41513(40): Minor algorithmic improvement to math.hypot() and
     math.dist() giving small gains in speed and accuracy.

   - bpo-41503(41): Fixed a race between setTarget and flush in
     logging.handlers.MemoryHandler.

   - bpo-41497(42): Fix potential UnicodeDecodeError in dis module.

   - bpo-41467(43): On Windows, fix asyncio ‘recv_into()’ return value
     when the socket/pipe is closed (*note BrokenPipeError: fff.):
     return ‘0’ rather than an empty byte string (‘b''’).

   - bpo-41425(44): Make tkinter doc example runnable.

   - bpo-41421(45): Make an algebraic simplification to
     random.paretovariate().  It now is slightly less subject to
     round-off error and is slightly faster.  Inputs that used to cause
     ZeroDivisionError now cause an OverflowError instead.

   - bpo-41440(46): Add *note os.cpu_count(): 1a8. support for VxWorks
     RTOS.

   - bpo-41316(47): Fix the *note tarfile: c8. module to write only
     basename of TAR file to GZIP compression header.

   - bpo-41384(48): Raise TclError instead of TypeError when an unknown
     option is passed to tkinter.OptionMenu.

   - bpo-41317(49): Use add_done_callback() in
     asyncio.loop.sock_accept() to unsubscribe reader early on
     cancellation.

   - bpo-41364(50): Reduce import overhead of *note uuid: f8.

   - bpo-35328(51): Set the environment variable ‘VIRTUAL_ENV_PROMPT’ at
     *note venv: f9. activation.

   - bpo-41341(52): Recursive evaluation of ‘typing.ForwardRef’ in
     ‘get_type_hints’.

   - bpo-41344(53): Prevent creating ‘shared_memory.SharedMemory’
     objects with ‘size=0’.

   - bpo-41333(54): ‘collections.OrderedDict.pop()’ is now 2 times
     faster.

   - bpo-41288(55): Unpickling invalid NEWOBJ_EX opcode with the C
     implementation raises now UnpicklingError instead of crashing.

   - bpo-39017(56): Avoid infinite loop when reading specially crafted
     TAR files using the tarfile module (CVE-2019-20907(57)).

   - bpo-41273(58): Speed up any transport using
     ‘_ProactorReadPipeTransport’ by calling ‘recv_into’ instead of
     ‘recv’, thus not creating a new buffer for each ‘recv’ call in the
     transport's read loop.

   - bpo-41235(59): Fix the error handling in *note
     ssl.SSLContext.load_dh_params(): 10db.

   - bpo-41207(60): In distutils.spawn, restore expectation that
     DistutilsExecError is raised when the command is not found.

   - bpo-29727(61): Register *note array.array: 186. as a *note
     MutableSequence: 187.  Patch by Pablo Galindo.

   - bpo-39168(62): Remove the ‘__new__’ method of *note typing.Generic:
     150c.

   - bpo-41194(63): Fix a crash in the ‘_ast’ module: it can no longer
     be loaded more than once.  It now uses a global state rather than a
     module state.

   - bpo-41195(64): Add read-only ssl.SSLContext.security_level
     attribute to retrieve the context's security level.

   - bpo-41193(65): The ‘write_history()’ atexit function of the
     readline completer now ignores any *note OSError: 350. to ignore
     error if the filesystem is read-only, instead of only ignoring
     *note FileNotFoundError: e67. and *note PermissionError: ce9.

   - bpo-41182(66): selector: use DefaultSelector based upon
     implementation

   - bpo-41161(67): The decimal module now requires libmpdec-2.5.0.
     Users of -with-system-libmpdec should update their system library.

   - bpo-40874(68): The decimal module now requires libmpdec-2.5.0.

   - bpo-41138(69): Fixed the *note trace: e6. module CLI for Python
     source files with non-UTF-8 encoding.

   - bpo-31082(70): Use the term "iterable" in the docstring for *note
     functools.reduce(): 126f.

   - bpo-40521(71): Remove freelist from collections.deque().

   - bpo-31938(72): Fix default-value signatures of several functions in
     the *note select: af. module - by Anthony Sottile.

   - bpo-41068(73): Fixed reading files with non-ASCII names from ZIP
     archive directly after writing them.

   - bpo-41058(74): ‘pdb.find_function()’ now correctly determines the
     source file encoding.

   - bpo-41056(75): Invalid file descriptor values are now prevented
     from being passed to os.fpathconf.  (discovered by Coverity)

   - bpo-41056(76): Fix a NULL pointer dereference within the ssl module
     during a MemoryError in the keylog callback.  (discovered by
     Coverity)

   - bpo-41056(77): Fixed an instance where a MemoryError within the
     zoneinfo module might not be reported or not reported at its
     source.  (found by Coverity)

   - bpo-41048(78): *note mimetypes.read_mime_types(): 1845. function
     reads the rule file using UTF-8 encoding, not the locale encoding.
     Patch by Srinivas Reddy Thatiparthy.

   - bpo-41043(79): Fixed the use of *note glob(): 280. in the stdlib:
     literal part of the path is now always correctly escaped.

   - bpo-41025(80): Fixed an issue preventing the C implementation of
     *note zoneinfo.ZoneInfo: 884. from being subclassed.

   - bpo-35018(81): Add the *note xml.sax.handler.LexicalHandler: 800.
     class that is present in other SAX XML implementations.

   - bpo-41002(82): Improve performance of HTTPResponse.read with a
     given amount.  Patch by Bruce Merry.

   - bpo-40448(83): *note ensurepip: 4b. now disables the use of ‘pip’
     cache when installing the bundled versions of ‘pip’ and
     ‘setuptools’.  Patch by Krzysztof Konopko.

   - bpo-40967(84): Removed ‘asyncio.Task.current_task()’ and
     ‘asyncio.Task.all_tasks()’.  Patch contributed by Rémi Lapeyre.

   - bpo-40924(85): Ensure ‘importlib.resources.path’ returns an extant
     path for the SourceFileLoader's resource reader.  Avoids the
     regression identified in master while a long-term solution is
     devised.

   - bpo-40955(86): Fix a minor memory leak in *note subprocess: c1.
     module when extra_groups was specified.

   - bpo-40855(87): The standard deviation and variance functions in the
     statistics module were ignoring their mu and xbar arguments.

   - bpo-40939(88): Use the new PEG parser when generating the stdlib
     *note keyword: 78. module.

   - bpo-23427(89): Add *note sys.orig_argv: 7e4. attribute: the list of
     the original command line arguments passed to the Python
     executable.

   - bpo-33689(90): Ignore empty or whitespace-only lines in .pth files.
     This matches the documentated behavior.  Before, empty lines caused
     the site-packages dir to appear multiple times in sys.path.  By Ido
     Michael, contributors Malcolm Smith and Tal Einat.

   - bpo-40884(91): Added a ‘defaults’ parameter to *note
     logging.Formatter: 1400, to allow specifying default values for
     custom fields.  Patch by Asaf Alon and Bar Harel.

   - bpo-40876(92): Clarify error message in the *note csv: 21. module.

   - bpo-39791(93): Refresh importlib.metadata from importlib_metadata
     1.6.1.

   - bpo-40807(94): Stop codeop._maybe_compile, used by
     code.InteractiveInterpreter (and IDLE). from emitting each warning
     three times.

   - bpo-32604(95): Fix reference leak in the *note select: af. module
     when the module is imported in a subinterpreter.

   - bpo-39791(96): Built-in loaders (SourceFileLoader and ZipImporter)
     now supply ‘TraversableResources’ implementations for
     ‘ResourceReader’, and the fallback function has been removed.

   - bpo-39314(97): *note rlcompleter.Completer: 1846. and the standard
     Python shell now close the parenthesis for functions that take no
     arguments.  Patch contributed by Rémi Lapeyre.

   - bpo-17005(98): The topological sort functionality that was
     introduced initially in the *note functools: 55. module has been
     moved to a new *note graphlib: 5b. module to better accommodate the
     new tools and keep the original scope of the *note functools: 55.
     module.  Patch by Pablo Galindo

   - bpo-40834(99): Fix truncate when sending str object
     with_xxsubinterpreters.channel_send.

   - bpo-40755(100): Add rich comparisons to collections.Counter().

   - bpo-26407(101): Unexpected errors in calling the ‘__iter__’ method
     are no longer masked by ‘TypeError’ in *note csv.reader(): 42d,
     ‘csv.writer.writerow()’ and ‘csv.writer.writerows()’.

   - bpo-39384(102): Fixed email.contentmanager to allow set_content()
     to set a null string.

   - bpo-40744(103): The *note sqlite3: ba. module uses SQLite API
     functions that require SQLite v3.7.3 or higher.  This patch removes
     support for older SQLite versions, and explicitly requires SQLite
     3.7.3 both at build, compile and runtime.  Patch by Sergey Fedoseev
     and Erlend E. Aasland.

   - bpo-40777(104): Initialize PyDateTime_IsoCalendarDateType.tp_base
     at run-time to avoid errors on some compilers.

   - bpo-38488(105): Update ensurepip to install pip 20.1.1 and
     setuptools 47.1.0.

   - bpo-40792(106): The result of *note operator.index(): 1811. now
     always has exact type *note int: 23c.  Previously, the result could
     have been an instance of a subclass of ‘int’.

   - bpo-40767(107): *note webbrowser: fd. now properly finds the
     default browser in pure Wayland systems by checking the
     WAYLAND_DISPLAY environment variable.  Patch contributed by Jérémy
     Attali.

   - bpo-40791(108): ‘hashlib.compare_digest()’ uses OpenSSL's
     ‘CRYPTO_memcmp()’ function when OpenSSL is available.

   - bpo-40795(109): *note ctypes: 22. module: If ctypes fails to
     convert the result of a callback or if a ctypes callback function
     raises an exception, sys.unraisablehook is now called with an
     exception set.  Previously, the error was logged into stderr by
     *note PyErr_Print(): 1847.

   - bpo-16995(110): Add *note base64.b32hexencode(): 787. and *note
     base64.b32hexdecode(): 788. to support the Base32 Encoding with
     Extended Hex Alphabet.

   - bpo-30008(111): Fix *note ssl: bb. code to be compatible with
     OpenSSL 1.1.x builds that use ‘no-deprecated’ and ‘--api=1.1.0’.

   - bpo-30064(112): Fix asyncio ‘loop.sock_*’ race condition issue

   - bpo-40759(113): Deprecate the ‘symbol’ module.

   - bpo-40756(114): The second argument (extra) of
     ‘LoggerAdapter.__init__’ now defaults to None.

   - bpo-37129(115): Add a new *note os.RWF_APPEND: 1848. flag for *note
     os.pwritev(): b04.

   - bpo-40737(116): Fix possible reference leak for *note sqlite3: ba.
     initialization.

   - bpo-40726(117): Handle cases where the ‘end_lineno’ is ‘None’ on
     *note ast.increment_lineno(): 1699.

   - bpo-40698(118): ‘distutils’ upload creates SHA2-256 and Blake2b-256
     digests.  MD5 digests is skipped if platform blocks MD5.

   - bpo-40695(119): *note hashlib: 5e. no longer falls back to builtin
     hash implementations when OpenSSL provides a hash digest and the
     algorithm is blocked by security policy.

   - bpo-9216(120): *note hashlib.new(): 1849. passed ‘usedforsecurity’
     to OpenSSL EVP constructor ‘_hashlib.new()’.  test_hashlib and
     test_smtplib handle strict security policy better.

   - bpo-40614(121): *note ast.parse(): 18e. will not parse self
     documenting expressions in f-strings when passed ‘feature_version’
     is less than ‘(3, 8)’.

   - bpo-40626(122): Add h5 file extension as MIME Type
     application/x-hdf5, as per HDF Group recommendation for HDF5
     formatted data files.  Patch contributed by Mark Schwab.

   - bpo-25920(123): On macOS, when building Python for macOS 10.4 and
     older, which wasn't the case for python.org macOS installer, *note
     socket.getaddrinfo(): 1654. no longer uses an internal lock to
     prevent race conditions when calling ‘getaddrinfo()’ which is
     thread-safe since macOS 10.5.  Python 3.9 requires macOS 10.6 or
     newer.  The internal lock caused random hang on fork when another
     thread was calling *note socket.getaddrinfo(): 1654.  The lock was
     also used on FreeBSD older than 5.3, OpenBSD older than 201311 and
     NetBSD older than 4.

   - bpo-40671(124): Prepare ‘_hashlib’ for PEP 489(125) and use *note
     PyModule_AddType(): 919.

   - bpo-32309(126): Added a new *note coroutine: 438. *note
     asyncio.to_thread(): 88d.  It is mainly used for running IO-bound
     functions in a separate thread to avoid blocking the event loop,
     and essentially works as a high-level version of *note
     run_in_executor(): 88e. that can directly take keyword arguments.

   - bpo-36543(127): Restored the deprecated ‘xml.etree.cElementTree’
     module.

   - bpo-40611(128): *note MAP_POPULATE: 184a. constant has now been
     added to the list of exported *note mmap: 83. module flags.

   - bpo-39881(129): PEP 554 for use in the test suite.  (Patch By
     Joannah Nanjekye)

   - bpo-13097(130): ‘ctypes’ now raises an ‘ArgumentError’ when a
     callback is invoked with more than 1024 arguments.

   - bpo-39385(131): A new test assertion context-manager,
     ‘unittest.assertNoLogs()’ will ensure a given block of code emits
     no log messages using the logging module.  Contributed by Kit Yan
     Choi.

   - bpo-23082(132): Updated the error message and docs of
     PurePath.relative_to() to better reflect the function behaviour.

   - bpo-40318(133): Use SQLite3 trace v2 API, if it is available.

   - bpo-40105(134): ZipFile truncates files to avoid corruption when a
     shorter comment is provided in append ("a") mode.  Patch by Jan
     Mazur.

   - bpo-40084(135): Fix ‘Enum.__dir__’: dir(Enum.member) now includes
     attributes as well as methods.

   - bpo-31122(136): ssl.wrap_socket() now raises ssl.SSLEOFError rather
     than OSError when peer closes connection during TLS negotiation

   - bpo-39728(137): fix default ‘_missing_’ so a duplicate ‘ValueError’
     is not set as the ‘__context__’ of the original ‘ValueError’.

   - bpo-39244(138): Fixed
     ‘multiprocessing.context.get_all_start_methods’ to properly return
     the default method first on macOS.

   - bpo-39040(139): Fix parsing of invalid mime headers parameters by
     collapsing whitespace between encoded words in a bare-quote-string.

   - bpo-38731(140): Add ‘--quiet’ option to command-line interface of
     *note py_compile: a1.  Patch by Gregory Schevchenko.

   - bpo-35714(141): *note struct.error: 12b7. is now raised if there is
     a null character in a *note struct: c0. format string.

   - bpo-38144(142): Added the 'root_dir' and 'dir_fd' parameters in
     *note glob.glob(): 280.

   - bpo-26543(143): Fix ‘IMAP4.noop()’ when debug mode is enabled (ex:
     ‘imaplib.Debug = 3’).

   - bpo-12178(144): *note csv.writer(): 42e. now correctly escapes
     'escapechar' when input contains 'escapechar'.  Patch by Catalin
     Iacob, Berker Peksag, and Itay Elbirt.

   - bpo-36290(145): AST nodes are now raising *note TypeError: 4dd. on
     conflicting keyword arguments.  Patch contributed by Rémi Lapeyre.

   - bpo-33944(146): Added site.py site-packages tracing in verbose
     mode.

   - bpo-35078(147): Refactor formatweekday, formatmonthname methods in
     LocaleHTMLCalendar and LocaleTextCalendar classes in calendar
     module to call the base class methods.This enables customizable CSS
     classes for LocaleHTMLCalendar.  Patch by Srinivas Reddy
     Thatiparthy

   - bpo-29620(148): *note assertWarns(): 10fd. no longer raises a
     ‘RuntimeException’ when accessing a module's ‘__warningregistry__’
     causes importation of a new module, or when a new module is
     imported in another thread.  Patch by Kernc.

   - bpo-31844(149): Remove ‘ParserBase.error()’ method from the private
     and undocumented ‘_markupbase’ module.  *note
     html.parser.HTMLParser: 81a. is the only subclass of ‘ParserBase’
     and its ‘error()’ implementation was deprecated in Python 3.4 and
     removed in Python 3.5.

   - bpo-34226(150): Fix ‘cgi.parse_multipart’ without content_length.
     Patch by Roger Duran

   - bpo-33660(151): Fix pathlib.PosixPath to resolve a relative path
     located on the root directory properly.

   - bpo-28557(152): Improve the error message for a misbehaving
     ‘rawio.readinto’

   - bpo-26680(153): The d.is_integer() method is added to the Decimal
     type, for compatibility with other number types.

   - bpo-26680(154): The x.is_integer() method is incorporated into the
     abstract types of the numeric tower, Real, Rational and Integral,
     with appropriate default implementations.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41900

   (2) https://bugs.python.org/issue?@action=redirect&bpo=41887

   (3) https://bugs.python.org/issue?@action=redirect&bpo=41773

   (4) https://bugs.python.org/issue?@action=redirect&bpo=41840

   (5) https://bugs.python.org/issue?@action=redirect&bpo=41842

   (6) https://bugs.python.org/issue?@action=redirect&bpo=40564

   (7) https://bugs.python.org/issue?@action=redirect&bpo=40670

   (8) https://bugs.python.org/issue?@action=redirect&bpo=41833

   (9) https://bugs.python.org/issue?@action=redirect&bpo=41817

   (10) https://bugs.python.org/issue?@action=redirect&bpo=41810

   (11) https://bugs.python.org/issue?@action=redirect&bpo=41815

   (12) https://bugs.python.org/issue?@action=redirect&bpo=41816

   (13) https://bugs.python.org/issue?@action=redirect&bpo=41517

   (14) https://bugs.python.org/issue?@action=redirect&bpo=39587

   (15) https://bugs.python.org/issue?@action=redirect&bpo=41792

   (16) https://github.com/python/typing/issues/751

   (17) https://bugs.python.org/issue?@action=redirect&bpo=41789

   (18) https://bugs.python.org/issue?@action=redirect&bpo=32218

   (19) https://bugs.python.org/issue?@action=redirect&bpo=39651

   (20) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (21) https://peps.python.org/pep-0489/

   (22) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (23) https://peps.python.org/pep-0489/

   (24) https://bugs.python.org/issue?@action=redirect&bpo=41732

   (25) https://bugs.python.org/issue?@action=redirect&bpo=41720

   (26) https://bugs.python.org/issue?@action=redirect&bpo=41696

   (27) https://bugs.python.org/issue?@action=redirect&bpo=41687

   (28) https://bugs.python.org/issue?@action=redirect&bpo=41662

   (29) https://bugs.python.org/issue?@action=redirect&bpo=39010

   (30) https://bugs.python.org/issue?@action=redirect&bpo=41638

   (31) https://bugs.python.org/issue?@action=redirect&bpo=41662

   (32) https://bugs.python.org/issue?@action=redirect&bpo=41513

   (33) https://bugs.python.org/issue?@action=redirect&bpo=41609

   (34) https://bugs.python.org/issue?@action=redirect&bpo=39994

   (35) https://bugs.python.org/issue?@action=redirect&bpo=32751

   (36) https://bugs.python.org/issue?@action=redirect&bpo=37658

   (37) https://bugs.python.org/issue?@action=redirect&bpo=40782

   (38) https://bugs.python.org/issue?@action=redirect&bpo=41520

   (39) https://bugs.python.org/issue?@action=redirect&bpo=41528

   (40) https://bugs.python.org/issue?@action=redirect&bpo=41513

   (41) https://bugs.python.org/issue?@action=redirect&bpo=41503

   (42) https://bugs.python.org/issue?@action=redirect&bpo=41497

   (43) https://bugs.python.org/issue?@action=redirect&bpo=41467

   (44) https://bugs.python.org/issue?@action=redirect&bpo=41425

   (45) https://bugs.python.org/issue?@action=redirect&bpo=41421

   (46) https://bugs.python.org/issue?@action=redirect&bpo=41440

   (47) https://bugs.python.org/issue?@action=redirect&bpo=41316

   (48) https://bugs.python.org/issue?@action=redirect&bpo=41384

   (49) https://bugs.python.org/issue?@action=redirect&bpo=41317

   (50) https://bugs.python.org/issue?@action=redirect&bpo=41364

   (51) https://bugs.python.org/issue?@action=redirect&bpo=35328

   (52) https://bugs.python.org/issue?@action=redirect&bpo=41341

   (53) https://bugs.python.org/issue?@action=redirect&bpo=41344

   (54) https://bugs.python.org/issue?@action=redirect&bpo=41333

   (55) https://bugs.python.org/issue?@action=redirect&bpo=41288

   (56) https://bugs.python.org/issue?@action=redirect&bpo=39017

   (57) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20907

   (58) https://bugs.python.org/issue?@action=redirect&bpo=41273

   (59) https://bugs.python.org/issue?@action=redirect&bpo=41235

   (60) https://bugs.python.org/issue?@action=redirect&bpo=41207

   (61) https://bugs.python.org/issue?@action=redirect&bpo=29727

   (62) https://bugs.python.org/issue?@action=redirect&bpo=39168

   (63) https://bugs.python.org/issue?@action=redirect&bpo=41194

   (64) https://bugs.python.org/issue?@action=redirect&bpo=41195

   (65) https://bugs.python.org/issue?@action=redirect&bpo=41193

   (66) https://bugs.python.org/issue?@action=redirect&bpo=41182

   (67) https://bugs.python.org/issue?@action=redirect&bpo=41161

   (68) https://bugs.python.org/issue?@action=redirect&bpo=40874

   (69) https://bugs.python.org/issue?@action=redirect&bpo=41138

   (70) https://bugs.python.org/issue?@action=redirect&bpo=31082

   (71) https://bugs.python.org/issue?@action=redirect&bpo=40521

   (72) https://bugs.python.org/issue?@action=redirect&bpo=31938

   (73) https://bugs.python.org/issue?@action=redirect&bpo=41068

   (74) https://bugs.python.org/issue?@action=redirect&bpo=41058

   (75) https://bugs.python.org/issue?@action=redirect&bpo=41056

   (76) https://bugs.python.org/issue?@action=redirect&bpo=41056

   (77) https://bugs.python.org/issue?@action=redirect&bpo=41056

   (78) https://bugs.python.org/issue?@action=redirect&bpo=41048

   (79) https://bugs.python.org/issue?@action=redirect&bpo=41043

   (80) https://bugs.python.org/issue?@action=redirect&bpo=41025

   (81) https://bugs.python.org/issue?@action=redirect&bpo=35018

   (82) https://bugs.python.org/issue?@action=redirect&bpo=41002

   (83) https://bugs.python.org/issue?@action=redirect&bpo=40448

   (84) https://bugs.python.org/issue?@action=redirect&bpo=40967

   (85) https://bugs.python.org/issue?@action=redirect&bpo=40924

   (86) https://bugs.python.org/issue?@action=redirect&bpo=40955

   (87) https://bugs.python.org/issue?@action=redirect&bpo=40855

   (88) https://bugs.python.org/issue?@action=redirect&bpo=40939

   (89) https://bugs.python.org/issue?@action=redirect&bpo=23427

   (90) https://bugs.python.org/issue?@action=redirect&bpo=33689

   (91) https://bugs.python.org/issue?@action=redirect&bpo=40884

   (92) https://bugs.python.org/issue?@action=redirect&bpo=40876

   (93) https://bugs.python.org/issue?@action=redirect&bpo=39791

   (94) https://bugs.python.org/issue?@action=redirect&bpo=40807

   (95) https://bugs.python.org/issue?@action=redirect&bpo=32604

   (96) https://bugs.python.org/issue?@action=redirect&bpo=39791

   (97) https://bugs.python.org/issue?@action=redirect&bpo=39314

   (98) https://bugs.python.org/issue?@action=redirect&bpo=17005

   (99) https://bugs.python.org/issue?@action=redirect&bpo=40834

   (100) https://bugs.python.org/issue?@action=redirect&bpo=40755

   (101) https://bugs.python.org/issue?@action=redirect&bpo=26407

   (102) https://bugs.python.org/issue?@action=redirect&bpo=39384

   (103) https://bugs.python.org/issue?@action=redirect&bpo=40744

   (104) https://bugs.python.org/issue?@action=redirect&bpo=40777

   (105) https://bugs.python.org/issue?@action=redirect&bpo=38488

   (106) https://bugs.python.org/issue?@action=redirect&bpo=40792

   (107) https://bugs.python.org/issue?@action=redirect&bpo=40767

   (108) https://bugs.python.org/issue?@action=redirect&bpo=40791

   (109) https://bugs.python.org/issue?@action=redirect&bpo=40795

   (110) https://bugs.python.org/issue?@action=redirect&bpo=16995

   (111) https://bugs.python.org/issue?@action=redirect&bpo=30008

   (112) https://bugs.python.org/issue?@action=redirect&bpo=30064

   (113) https://bugs.python.org/issue?@action=redirect&bpo=40759

   (114) https://bugs.python.org/issue?@action=redirect&bpo=40756

   (115) https://bugs.python.org/issue?@action=redirect&bpo=37129

   (116) https://bugs.python.org/issue?@action=redirect&bpo=40737

   (117) https://bugs.python.org/issue?@action=redirect&bpo=40726

   (118) https://bugs.python.org/issue?@action=redirect&bpo=40698

   (119) https://bugs.python.org/issue?@action=redirect&bpo=40695

   (120) https://bugs.python.org/issue?@action=redirect&bpo=9216

   (121) https://bugs.python.org/issue?@action=redirect&bpo=40614

   (122) https://bugs.python.org/issue?@action=redirect&bpo=40626

   (123) https://bugs.python.org/issue?@action=redirect&bpo=25920

   (124) https://bugs.python.org/issue?@action=redirect&bpo=40671

   (125) https://peps.python.org/pep-0489/

   (126) https://bugs.python.org/issue?@action=redirect&bpo=32309

   (127) https://bugs.python.org/issue?@action=redirect&bpo=36543

   (128) https://bugs.python.org/issue?@action=redirect&bpo=40611

   (129) https://bugs.python.org/issue?@action=redirect&bpo=39881

   (130) https://bugs.python.org/issue?@action=redirect&bpo=13097

   (131) https://bugs.python.org/issue?@action=redirect&bpo=39385

   (132) https://bugs.python.org/issue?@action=redirect&bpo=23082

   (133) https://bugs.python.org/issue?@action=redirect&bpo=40318

   (134) https://bugs.python.org/issue?@action=redirect&bpo=40105

   (135) https://bugs.python.org/issue?@action=redirect&bpo=40084

   (136) https://bugs.python.org/issue?@action=redirect&bpo=31122

   (137) https://bugs.python.org/issue?@action=redirect&bpo=39728

   (138) https://bugs.python.org/issue?@action=redirect&bpo=39244

   (139) https://bugs.python.org/issue?@action=redirect&bpo=39040

   (140) https://bugs.python.org/issue?@action=redirect&bpo=38731

   (141) https://bugs.python.org/issue?@action=redirect&bpo=35714

   (142) https://bugs.python.org/issue?@action=redirect&bpo=38144

   (143) https://bugs.python.org/issue?@action=redirect&bpo=26543

   (144) https://bugs.python.org/issue?@action=redirect&bpo=12178

   (145) https://bugs.python.org/issue?@action=redirect&bpo=36290

   (146) https://bugs.python.org/issue?@action=redirect&bpo=33944

   (147) https://bugs.python.org/issue?@action=redirect&bpo=35078

   (148) https://bugs.python.org/issue?@action=redirect&bpo=29620

   (149) https://bugs.python.org/issue?@action=redirect&bpo=31844

   (150) https://bugs.python.org/issue?@action=redirect&bpo=34226

   (151) https://bugs.python.org/issue?@action=redirect&bpo=33660

   (152) https://bugs.python.org/issue?@action=redirect&bpo=28557

   (153) https://bugs.python.org/issue?@action=redirect&bpo=26680

   (154) https://bugs.python.org/issue?@action=redirect&bpo=26680


File: python.info,  Node: Documentation<31>,  Next: Tests<34>,  Prev: Library<36>,  Up: Python 3 10 0 alpha 1

1.23.37.4 Documentation
.......................

   - bpo-41428(1): Add documentation for PEP 604(2) (Allow writing union
     types as ‘X | Y’).

   - bpo-41774(3): In Programming FAQ "Sequences (Tuples/Lists)"
     section, add "How do you remove multiple items from a list".

   - bpo-35293(4): Fix RemovedInSphinx40Warning when building the
     documentation.  Patch by Donghee Na.

   - bpo-37149(5): Change Shipman tkinter doc link from archive.org to
     TkDocs.  (The doc has been removed from the NMT server.)  The new
     link responds much faster and includes a short explanatory note.

   - bpo-41726(6): Update the refcounts info of
     ‘PyType_FromModuleAndSpec’.

   - bpo-41624(7): Fix the signature of *note typing.Coroutine: 184c.

   - bpo-40204(8): Enable Sphinx 3.2 ‘c_allow_pre_v3’ option and disable
     ‘c_warn_on_allowed_pre_v3’ option to make the documentation
     compatible with Sphinx 2 and Sphinx 3.

   - bpo-41045(9): Add documentation for debug feature of f-strings.

   - bpo-41314(10): Changed the release when ‘from __future__ import
     annotations’ becomes the default from ‘4.0’ to ‘3.10’ (following a
     change in PEP 563).

   - bpo-40979(11): Refactored typing.rst, arranging more than 70
     classes, functions, and decorators into new sub-sections.

   - bpo-40552(12): Fix in tutorial section 4.2.  Code snippet is now
     correct.

   - bpo-39883(13): Make code, examples, and recipes in the Python
     documentation be licensed under the more permissive BSD0 license in
     addition to the existing Python 2.0 license.

   - bpo-37703(14): Updated Documentation to comprehensively elaborate
     on the behaviour of gather.cancel()

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41428

   (2) https://peps.python.org/pep-0604/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=41774

   (4) https://bugs.python.org/issue?@action=redirect&bpo=35293

   (5) https://bugs.python.org/issue?@action=redirect&bpo=37149

   (6) https://bugs.python.org/issue?@action=redirect&bpo=41726

   (7) https://bugs.python.org/issue?@action=redirect&bpo=41624

   (8) https://bugs.python.org/issue?@action=redirect&bpo=40204

   (9) https://bugs.python.org/issue?@action=redirect&bpo=41045

   (10) https://bugs.python.org/issue?@action=redirect&bpo=41314

   (11) https://bugs.python.org/issue?@action=redirect&bpo=40979

   (12) https://bugs.python.org/issue?@action=redirect&bpo=40552

   (13) https://bugs.python.org/issue?@action=redirect&bpo=39883

   (14) https://bugs.python.org/issue?@action=redirect&bpo=37703


File: python.info,  Node: Tests<34>,  Next: Build<36>,  Prev: Documentation<31>,  Up: Python 3 10 0 alpha 1

1.23.37.5 Tests
...............

   - bpo-41939(1): Fix test_site.test_license_exists_at_url(): call
     ‘urllib.request.urlcleanup()’ to reset the global
     ‘urllib.request._opener’.  Patch by Victor Stinner.

   - bpo-41731(2): Make test_cmd_line_script pass with option '-vv'.

   - bpo-41602(3): Add tests for SIGINT handling in the runpy module.

   - bpo-41521(4): *note test.support: cd.: Rename ‘blacklist’ parameter
     of *note check__all__(): 184e. to ‘not_exported’.

   - bpo-41477(5): Make ctypes optional in test_genericalias.

   - bpo-41085(6): Fix integer overflow in the *note
     array.array.index(): 784. method on 64-bit Windows for index larger
     than ‘2**31’.

   - bpo-41069(7): ‘test.support.TESTFN’ and the current directory for
     tests when run via ‘test.regrtest’ contain now non-ascii characters
     if possible.

   - bpo-38377(8): On Linux, skip tests using multiprocessing if the
     current user cannot create a file in ‘/dev/shm/’ directory.  Add
     the *note skip_if_broken_multiprocessing_synchronize(): 184f.
     function to the *note test.support: cd. module.

   - bpo-41009(9): Fix use of
     ‘support.require_{linux|mac|freebsd}_version()’ decorators as class
     decorator.

   - bpo-41003(10): Fix ‘test_copyreg’ when ‘numpy’ is installed:
     ‘test.pickletester’ now saves/restores warnings filters when
     importing ‘numpy’, to ignore filters installed by ‘numpy’.

   - bpo-40964(11): Disable remote *note imaplib: 6a. tests, host
     cyrus.andrew.cmu.edu is blocking incoming connections.

   - bpo-40927(12): Fix test_binhex when run twice: it now uses
     import_fresh_module() to ensure that it raises DeprecationWarning
     each time.

   - bpo-17258(13): Skip some *note multiprocessing: 86. tests when MD5
     hash digest is blocked.

   - bpo-31904(14): Increase LOOPBACK_TIMEOUT to 10 for VxWorks RTOS.

   - bpo-38169(15): Increase code coverage for SharedMemory and
     ShareableList

   - bpo-34401(16): Make test_gdb properly run on HP-UX. Patch by
     Michael Osipov.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41939

   (2) https://bugs.python.org/issue?@action=redirect&bpo=41731

   (3) https://bugs.python.org/issue?@action=redirect&bpo=41602

   (4) https://bugs.python.org/issue?@action=redirect&bpo=41521

   (5) https://bugs.python.org/issue?@action=redirect&bpo=41477

   (6) https://bugs.python.org/issue?@action=redirect&bpo=41085

   (7) https://bugs.python.org/issue?@action=redirect&bpo=41069

   (8) https://bugs.python.org/issue?@action=redirect&bpo=38377

   (9) https://bugs.python.org/issue?@action=redirect&bpo=41009

   (10) https://bugs.python.org/issue?@action=redirect&bpo=41003

   (11) https://bugs.python.org/issue?@action=redirect&bpo=40964

   (12) https://bugs.python.org/issue?@action=redirect&bpo=40927

   (13) https://bugs.python.org/issue?@action=redirect&bpo=17258

   (14) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (15) https://bugs.python.org/issue?@action=redirect&bpo=38169

   (16) https://bugs.python.org/issue?@action=redirect&bpo=34401


File: python.info,  Node: Build<36>,  Next: Windows<32>,  Prev: Tests<34>,  Up: Python 3 10 0 alpha 1

1.23.37.6 Build
...............

   - bpo-38249(1): Update *note Py_UNREACHABLE: b5c. to use
     __builtin_unreachable() if only the compiler is able to use it.
     Patch by Donghee Na.

   - bpo-41617(2): Fix ‘pycore_bitutils.h’ header file to support old
     clang versions: ‘__builtin_bswap16()’ is not available in LLVM
     clang 3.0.

   - bpo-40204(3): Pin Sphinx version to 2.3.1 in ‘Doc/Makefile’.

   - bpo-36020(4): The C99 functions ‘snprintf()’ and ‘vsnprintf()’ are
     now required to build Python.

   - bpo-40684(5): ‘make install’ now uses the ‘PLATLIBDIR’ variable for
     the destination ‘lib-dynload/’ directory when ‘./configure
     --with-platlibdir’ is used.

   - bpo-40683(6): Fixed an issue where the *note zoneinfo: 11a. module
     and its tests were not included when Python is installed with
     ‘make’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38249

   (2) https://bugs.python.org/issue?@action=redirect&bpo=41617

   (3) https://bugs.python.org/issue?@action=redirect&bpo=40204

   (4) https://bugs.python.org/issue?@action=redirect&bpo=36020

   (5) https://bugs.python.org/issue?@action=redirect&bpo=40684

   (6) https://bugs.python.org/issue?@action=redirect&bpo=40683


File: python.info,  Node: Windows<32>,  Next: macOS<27>,  Prev: Build<36>,  Up: Python 3 10 0 alpha 1

1.23.37.7 Windows
.................

   - bpo-41744(1): Fixes automatic import of props file when using the
     Nuget package.

   - bpo-41627(2): The user site directory for 32-bit now includes a
     ‘-32’ suffix to distinguish it from the 64-bit interpreter's
     directory.

   - bpo-41526(3): Fixed layout of final page of the installer by
     removing the special thanks to Mark Hammond (with his permission).

   - bpo-41492(4): Fixes the description that appears in UAC prompts.

   - bpo-40948(5): Improve post-install message to direct people to the
     "py" command.

   - bpo-41412(6): The installer will now fail to install on Windows 7
     and Windows 8.  Further, the UCRT dependency is now always
     downloaded on demand.

   - bpo-40741(7): Update Windows release to include SQLite 3.32.3.

   - bpo-41142(8): ‘msilib’ now supports creating CAB files with
     non-ASCII file path and adding files with non-ASCII file path to
     them.

   - bpo-41074(9): Fixed support of non-ASCII names in functions
     ‘msilib.OpenDatabase()’ and ‘msilib.init_database()’ and non-ASCII
     SQL in method ‘msilib.Database.OpenView()’.

   - bpo-41039(10): Stable ABI redirection DLL (python3.dll) now uses
     ‘#pragma comment(linker)’ for re-exporting.

   - bpo-40164(11): Updates Windows OpenSSL to 1.1.1g

   - bpo-39631(12): Changes the registered MIME type for ‘.py’ files on
     Windows to ‘text/x-python’ instead of ‘text/plain’.

   - bpo-40677(13): Manually define IO_REPARSE_TAG_APPEXECLINK in case
     some old Windows SDK doesn't have it.

   - bpo-37556(14): Extend py.exe help to mention overrides via venv,
     shebang, environmental variables & ini files.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41744

   (2) https://bugs.python.org/issue?@action=redirect&bpo=41627

   (3) https://bugs.python.org/issue?@action=redirect&bpo=41526

   (4) https://bugs.python.org/issue?@action=redirect&bpo=41492

   (5) https://bugs.python.org/issue?@action=redirect&bpo=40948

   (6) https://bugs.python.org/issue?@action=redirect&bpo=41412

   (7) https://bugs.python.org/issue?@action=redirect&bpo=40741

   (8) https://bugs.python.org/issue?@action=redirect&bpo=41142

   (9) https://bugs.python.org/issue?@action=redirect&bpo=41074

   (10) https://bugs.python.org/issue?@action=redirect&bpo=41039

   (11) https://bugs.python.org/issue?@action=redirect&bpo=40164

   (12) https://bugs.python.org/issue?@action=redirect&bpo=39631

   (13) https://bugs.python.org/issue?@action=redirect&bpo=40677

   (14) https://bugs.python.org/issue?@action=redirect&bpo=37556


File: python.info,  Node: macOS<27>,  Next: IDLE<24>,  Prev: Windows<32>,  Up: Python 3 10 0 alpha 1

1.23.37.8 macOS
...............

   - bpo-41557(1): Update macOS installer to use SQLite 3.33.0.

   - bpo-39580(2): Avoid opening Finder window if running installer from
     the command line.  Patch contributed by Rick Heil.

   - bpo-41100(3): Fix configure error when building on macOS 11.  Note
     that the current Python release was released shortly after the
     first developer preview of macOS 11 (Big Sur); there are other
     known issues with building and running on the developer preview.
     Big Sur is expected to be fully supported in a future bugfix
     release of Python 3.8.x and with 3.9.0.

   - bpo-40741(4): Update macOS installer to use SQLite 3.32.3.

   - bpo-41005(5): fixed an XDG settings issue not allowing macos to
     open browser in webbrowser.py

   - bpo-40741(6): Update macOS installer to use SQLite 3.32.2.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41557

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39580

   (3) https://bugs.python.org/issue?@action=redirect&bpo=41100

   (4) https://bugs.python.org/issue?@action=redirect&bpo=40741

   (5) https://bugs.python.org/issue?@action=redirect&bpo=41005

   (6) https://bugs.python.org/issue?@action=redirect&bpo=40741


File: python.info,  Node: IDLE<24>,  Next: C API<35>,  Prev: macOS<27>,  Up: Python 3 10 0 alpha 1

1.23.37.9 IDLE
..............

   - bpo-41775(1): Use 'IDLE Shell' as shell title

   - bpo-35764(2): Rewrite the Calltips doc section.

   - bpo-40181(3): In calltips, stop reminding that '/' marks the end of
     positional-only arguments.

   - bpo-41468(4): Improve IDLE run crash error message (which users
     should never see).

   - bpo-41373(5): Save files loaded with no line ending, as when blank,
     or different line endings, by setting its line ending to the system
     default.  Fix regression in 3.8.4 and 3.9.0b4.

   - bpo-41300(6): Save files with non-ascii chars.  Fix regression
     released in 3.9.0b4 and 3.8.4.

   - bpo-37765(7): Add keywords to module name completion list.  Rewrite
     Completions section of IDLE doc.

   - bpo-41152(8): The encoding of ‘stdin’, ‘stdout’ and ‘stderr’ in
     IDLE is now always UTF-8.

   - bpo-41144(9): Make Open Module open a special module such as
     os.path.

   - bpo-39885(10): Make context menu Cut and Copy work again when
     right-clicking within a selection.

   - bpo-40723(11): Make test_idle pass when run after import.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41775

   (2) https://bugs.python.org/issue?@action=redirect&bpo=35764

   (3) https://bugs.python.org/issue?@action=redirect&bpo=40181

   (4) https://bugs.python.org/issue?@action=redirect&bpo=41468

   (5) https://bugs.python.org/issue?@action=redirect&bpo=41373

   (6) https://bugs.python.org/issue?@action=redirect&bpo=41300

   (7) https://bugs.python.org/issue?@action=redirect&bpo=37765

   (8) https://bugs.python.org/issue?@action=redirect&bpo=41152

   (9) https://bugs.python.org/issue?@action=redirect&bpo=41144

   (10) https://bugs.python.org/issue?@action=redirect&bpo=39885

   (11) https://bugs.python.org/issue?@action=redirect&bpo=40723


File: python.info,  Node: C API<35>,  Prev: IDLE<24>,  Up: Python 3 10 0 alpha 1

1.23.37.10 C API
................

   - bpo-41936(1): Removed undocumented macros ‘Py_ALLOW_RECURSION’ and
     ‘Py_END_ALLOW_RECURSION’ and the ‘recursion_critical’ field of the
     *note PyInterpreterState: 862. structure.

   - bpo-41692(2): The ‘PyUnicode_InternImmortal()’ function is now
     deprecated and will be removed in Python 3.12: use *note
     PyUnicode_InternInPlace(): 856. instead.  Patch by Victor Stinner.

   - bpo-41842(3): Add *note PyCodec_Unregister(): 83b. function to
     unregister a codec search function.

   - bpo-41834(4): Remove the ‘_Py_CheckRecursionLimit’ variable: it has
     been replaced by ‘ceval.recursion_limit’ of the *note
     PyInterpreterState: 862. structure.  Patch by Victor Stinner.

   - bpo-41689(5): Types created with *note PyType_FromSpec(): 523. now
     make any signature in their ‘tp_doc’ slot accessible from
     ‘__text_signature__’.

   - bpo-41524(6): Fix bug in PyOS_mystrnicmp and PyOS_mystricmp that
     incremented pointers beyond the end of a string.

   - bpo-41324(7): Add a minimal decimal capsule API. The API supports
     fast conversions between Decimals up to 38 digits and their triple
     representation as a C struct.

   - bpo-30155(8): Add *note PyDateTime_DATE_GET_TZINFO(): 839. and
     *note PyDateTime_TIME_GET_TZINFO(): 83a. macros for accessing the
     ‘tzinfo’ attributes of *note datetime.datetime: 1b0. and *note
     datetime.time: 1b2. objects.

   - bpo-40170(9): Revert *note PyType_HasFeature(): 1855. change: it
     reads again directly the *note PyTypeObject.tp_flags: 17c0. member
     when the limited C API is not used, rather than always calling
     *note PyType_GetFlags(): 1856. which hides implementation details.

   - bpo-41123(10): Remove ‘PyUnicode_AsUnicodeCopy’.

   - bpo-41123(11): Removed ‘PyLong_FromUnicode()’.

   - bpo-41123(12): Removed ‘PyUnicode_GetMax()’.

   - bpo-41123(13): Removed ‘Py_UNICODE_str*’ functions manipulating
     ‘Py_UNICODE*’ strings.

   - bpo-41103(14): ‘PyObject_AsCharBuffer()’,
     ‘PyObject_AsReadBuffer()’, ‘PyObject_CheckReadBuffer()’, and
     ‘PyObject_AsWriteBuffer()’ are removed.  Please migrate to new
     buffer protocol; *note PyObject_GetBuffer(): 369. and *note
     PyBuffer_Release(): 36a.

   - bpo-36346(15): Raises DeprecationWarning for
     ‘PyUnicode_FromUnicode(NULL, size)’ and
     ‘PyUnicode_FromStringAndSize(NULL, size)’ with ‘size > 0’.

   - bpo-36346(16): Mark ‘Py_UNICODE_COPY’, ‘Py_UNICODE_FILL’,
     ‘PyUnicode_WSTR_LENGTH’, ‘PyUnicode_FromUnicode’,
     ‘PyUnicode_AsUnicode’, and ‘PyUnicode_AsUnicodeAndSize’ as
     deprecated in C. Remove ‘Py_UNICODE_MATCH’ which was deprecated and
     broken since Python 3.3.

   - bpo-40989(17): The ‘PyObject_INIT()’ and ‘PyObject_INIT_VAR()’
     macros become aliases to, respectively, *note PyObject_Init(): a0d.
     and *note PyObject_InitVar(): 1857. functions.

   - bpo-36020(18): On Windows, ‘#include "pyerrors.h"’ no longer
     defines ‘snprintf’ and ‘vsnprintf’ macros.

   - bpo-40943(19): The ‘PY_SSIZE_T_CLEAN’ macro must now be defined to
     use *note PyArg_ParseTuple(): 517. and *note Py_BuildValue(): 84c.
     formats which use ‘#’: ‘es#’, ‘et#’, ‘s#’, ‘u#’, ‘y#’, ‘z#’, ‘U#’
     and ‘Z#’.  See *note Parsing arguments and building values: 84d.
     and the PEP 353(20).

   - bpo-40910(21): Export explicitly the *note Py_GetArgcArgv(): 1858.
     function to the C API and document the function.  Previously, it
     was exported implicitly which no longer works since Python is built
     with ‘-fvisibility=hidden’.

   - bpo-40724(22): Allow defining buffer slots in type specs.

   - bpo-40679(23): Fix a ‘_PyEval_EvalCode()’ crash if 'qualname'
     argument is NULL.

   - bpo-40839(24): Calling *note PyDict_GetItem(): 35b. without *note
     GIL: 13e. held had been allowed for historical reason.  It is no
     longer allowed.

   - bpo-40826(25): ‘PyOS_InterruptOccurred()’ now fails with a fatal
     error if it is called with the GIL released.

   - bpo-40792(26): The result of *note PyNumber_Index(): 837. now
     always has exact type *note int: 23c.  Previously, the result could
     have been an instance of a subclass of ‘int’.

   - bpo-39573(27): Convert *note Py_REFCNT(): 84e. and *note Py_SIZE():
     726. macros to static inline functions.  They cannot be used as
     l-value anymore: use *note Py_SET_REFCNT(): 84f. and *note
     Py_SET_SIZE(): 727. to set an object reference count and size.
     This change is backward incompatible on purpose, to prepare the C
     API for an opaque *note PyObject: 311. structure.

   - bpo-40703(28): The PyType_FromSpec*() functions no longer overwrite
     the type's "__module__" attribute if it is set via "Py_tp_members"
     or "Py_tp_getset".

   - bpo-39583(29): Remove superfluous "extern C" declarations from
     ‘Include/cpython/*.h’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=41936

   (2) https://bugs.python.org/issue?@action=redirect&bpo=41692

   (3) https://bugs.python.org/issue?@action=redirect&bpo=41842

   (4) https://bugs.python.org/issue?@action=redirect&bpo=41834

   (5) https://bugs.python.org/issue?@action=redirect&bpo=41689

   (6) https://bugs.python.org/issue?@action=redirect&bpo=41524

   (7) https://bugs.python.org/issue?@action=redirect&bpo=41324

   (8) https://bugs.python.org/issue?@action=redirect&bpo=30155

   (9) https://bugs.python.org/issue?@action=redirect&bpo=40170

   (10) https://bugs.python.org/issue?@action=redirect&bpo=41123

   (11) https://bugs.python.org/issue?@action=redirect&bpo=41123

   (12) https://bugs.python.org/issue?@action=redirect&bpo=41123

   (13) https://bugs.python.org/issue?@action=redirect&bpo=41123

   (14) https://bugs.python.org/issue?@action=redirect&bpo=41103

   (15) https://bugs.python.org/issue?@action=redirect&bpo=36346

   (16) https://bugs.python.org/issue?@action=redirect&bpo=36346

   (17) https://bugs.python.org/issue?@action=redirect&bpo=40989

   (18) https://bugs.python.org/issue?@action=redirect&bpo=36020

   (19) https://bugs.python.org/issue?@action=redirect&bpo=40943

   (20) https://peps.python.org/pep-0353/

   (21) https://bugs.python.org/issue?@action=redirect&bpo=40910

   (22) https://bugs.python.org/issue?@action=redirect&bpo=40724

   (23) https://bugs.python.org/issue?@action=redirect&bpo=40679

   (24) https://bugs.python.org/issue?@action=redirect&bpo=40839

   (25) https://bugs.python.org/issue?@action=redirect&bpo=40826

   (26) https://bugs.python.org/issue?@action=redirect&bpo=40792

   (27) https://bugs.python.org/issue?@action=redirect&bpo=39573

   (28) https://bugs.python.org/issue?@action=redirect&bpo=40703

   (29) https://bugs.python.org/issue?@action=redirect&bpo=39583


File: python.info,  Node: Python 3 9 0 beta 1,  Next: Python 3 9 0 alpha 6,  Prev: Python 3 10 0 alpha 1,  Up: Changelog（更動日誌）

1.23.38 Python 3.9.0 beta 1
---------------------------

'Release date: 2020-05-19'

* Menu:

* Security: Security<24>.
* Core and Builtins: Core and Builtins<38>.
* Library: Library<37>.
* Documentation: Documentation<32>.
* Tests: Tests<35>.
* Build: Build<37>.
* Windows: Windows<33>.
* macOS: macOS<28>.
* Tools/Demos: Tools/Demos<16>.
* C API: C API<36>.


File: python.info,  Node: Security<24>,  Next: Core and Builtins<38>,  Up: Python 3 9 0 beta 1

1.23.38.1 Security
..................

   - bpo-40501(1): *note uuid: f8. no longer uses *note ctypes: 22. to
     load ‘libuuid’ or ‘rpcrt4.dll’ at runtime.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40501


File: python.info,  Node: Core and Builtins<38>,  Next: Library<37>,  Prev: Security<24>,  Up: Python 3 9 0 beta 1

1.23.38.2 Core and Builtins
...........................

   - bpo-40663(1): Correctly generate annotations where parentheses are
     omitted but required (e.g: ‘Type[(str, int, *other))]’.

   - bpo-40596(2): Fixed *note str.isidentifier(): 185c. for
     non-canonicalized strings containing non-BMP characters on Windows.

   - bpo-40593(3): Improved syntax errors for invalid characters in
     source code.

   - bpo-40585(4): Fixed a bug when using *note
     codeop.compile_command(): 16cd. that was causing exceptions to be
     swallowed with the new parser.  Patch by Pablo Galindo

   - bpo-40566(5): Apply PEP 573(6) to *note abc: 4.

   - bpo-40502(7): Initialize ‘n->n_col_offset’.  (Patch by Joannah
     Nanjekye)

   - bpo-40527(8): Fix command line argument parsing: no longer write
     errors multiple times into stderr.

   - bpo-1635741(9): Port *note errno: 4d. to multiphase initialization
     ( PEP 489(10)).

   - bpo-40523(11): Add pass-throughs for *note hash(): 58f. and *note
     reversed(): 80a. to *note weakref.proxy: 9f5. objects.  Patch by
     Pablo Galindo.

   - bpo-1635741(12): Port *note syslog: c6. to multiphase
     initialization ( PEP 489(13)).

   - bpo-40246(14): Reporting a specialised error message for invalid
     string prefixes, which was introduced in bpo-40246(15), is being
     reverted due to backwards compatibility concerns for strings that
     immediately follow a reserved keyword without whitespace between
     them.  Constructs like ‘bg="#d00" if clear else"#fca"’ were failing
     to parse, which is not an acceptable breakage on such short notice.

   - bpo-40417(16): Fix imp module deprecation warning when
     PyImport_ReloadModule is called.  Patch by Robert Rouhani.

   - bpo-40408(17): Fixed support of nested type variables in
     GenericAlias (e.g.  ‘list[list[T]]’).

   - bpo-1635741(18): Port _stat module to multiphase initialization (
     PEP 489(19)).

   - bpo-29587(20): Enable implicit exception chaining when calling
     *note generator.throw(): 4a0.

   - bpo-40328(21): Add tools for generating mappings headers for
     CJKCodecs.

   - bpo-40228(22): Setting frame.f_lineno is now robust w.r.t.  changes
     in the source-to-bytecode compiler

   - bpo-38880(23): Added the ability to list interpreters associated
     with channel ends in the internal subinterpreters module.

   - bpo-37986(24): Improve performance of *note PyLong_FromDouble():
     8e6. for values that fit into long.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40663

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40596

   (3) https://bugs.python.org/issue?@action=redirect&bpo=40593

   (4) https://bugs.python.org/issue?@action=redirect&bpo=40585

   (5) https://bugs.python.org/issue?@action=redirect&bpo=40566

   (6) https://peps.python.org/pep-0573/

   (7) https://bugs.python.org/issue?@action=redirect&bpo=40502

   (8) https://bugs.python.org/issue?@action=redirect&bpo=40527

   (9) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (10) https://peps.python.org/pep-0489/

   (11) https://bugs.python.org/issue?@action=redirect&bpo=40523

   (12) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (13) https://peps.python.org/pep-0489/

   (14) https://bugs.python.org/issue?@action=redirect&bpo=40246

   (15) https://bugs.python.org/issue?@action=redirect&bpo=40246

   (16) https://bugs.python.org/issue?@action=redirect&bpo=40417

   (17) https://bugs.python.org/issue?@action=redirect&bpo=40408

   (18) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (19) https://peps.python.org/pep-0489/

   (20) https://bugs.python.org/issue?@action=redirect&bpo=29587

   (21) https://bugs.python.org/issue?@action=redirect&bpo=40328

   (22) https://bugs.python.org/issue?@action=redirect&bpo=40228

   (23) https://bugs.python.org/issue?@action=redirect&bpo=38880

   (24) https://bugs.python.org/issue?@action=redirect&bpo=37986


File: python.info,  Node: Library<37>,  Next: Documentation<32>,  Prev: Core and Builtins<38>,  Up: Python 3 9 0 beta 1

1.23.38.3 Library
.................

   - bpo-40662(1): Fixed *note ast.get_source_segment(): 97b. for ast
     nodes that have incomplete location information.  Patch by Irit
     Katriel.

   - bpo-40665(2): Convert *note bisect: d. to use Argument Clinic.

   - bpo-40536(3): Added the *note available_timezones(): 185e. function
     to the *note zoneinfo: 11a. module.  Patch by Paul Ganssle.

   - bpo-40645(4): The ‘hmac.HMAC’ exposes internal implementation
     details.  The attributes ‘digest_cons’, ‘inner’, and ‘outer’ are
     deprecated and will be removed in the future.

   - bpo-40645(5): The internal module ‘_hashlib’ wraps and exposes
     OpenSSL's HMAC API. The new code will be used in Python 3.10 after
     the internal implementation details of the pure Python HMAC module
     are no longer part of the public API.

   - bpo-40637(6): Builtin hash modules can now be disabled or
     selectively enabled with ‘configure
     --with-builtin-hashlib-hashes=sha3,blake1’ or
     ‘--without-builtin-hashlib-hashes’.

   - bpo-37630(7): The *note hashlib: 5e. module can now use SHA3 hashes
     and SHAKE XOF from OpenSSL when available.

   - bpo-40479(8): The *note hashlib: 5e. now compiles with OpenSSL
     3.0.0-alpha2.

   - bpo-40257(9): Revert changes to *note inspect.getdoc(): 99e.

   - bpo-40607(10): When cancelling a task due to timeout, *note
     asyncio.wait_for(): 5a4. will now propagate the exception if an
     error happens during cancellation.  Patch by Roman Skurikhin.

   - bpo-40612(11): Fix edge cases in SyntaxError formatting.  If the
     offset is <= 0, no caret is printed.  If the offset is > line
     length, the caret is printed pointing just after the last
     character.

   - bpo-40597(12): If text content lines are longer than
     policy.max_line_length, always use a content-encoding to make sure
     they are wrapped.

   - bpo-40571(13): Added functools.cache() as a simpler, more
     discoverable way to access the unbounded cache variant of
     lru_cache(maxsize=None).

   - bpo-40503(14): PEP 615(15), the *note zoneinfo: 11a. module.  Adds
     support for the IANA time zone database.

   - bpo-40397(16): Removed attributes ‘__args__’ and ‘__parameters__’
     from special generic aliases like ‘typing.List’ (not subscripted).

   - bpo-40549(17): Convert posixmodule.c ("posix" or "nt" module) to
     the multiphase initialization (PEP 489).

   - bpo-31033(18): Add a ‘msg’ argument to ‘Future.cancel()’ and
     ‘Task.cancel()’.

   - bpo-40541(19): Added an optional 'counts' parameter to
     random.sample().

   - bpo-40515(20): The *note ssl: bb. and *note hashlib: 5e. modules
     now actively check that OpenSSL is build with thread support.
     Python 3.7.0 made thread support mandatory and no longer works
     safely with a no-thread builds.

   - bpo-31033(21): When a *note asyncio.Task: 480. is cancelled, the
     exception traceback now chains all the way back to where the task
     was first interrupted.

   - bpo-40504(22): *note functools.lru_cache(): 993. objects can now be
     the targets of weakrefs.

   - bpo-40559(23): Fix possible memory leak in the C implementation of
     *note asyncio.Task: 480.

   - bpo-40480(24): ‘fnmatch.fnmatch()’ could take exponential time in
     the presence of multiple ‘*’ pattern characters.  This was repaired
     by generating more elaborate regular expressions to avoid futile
     backtracking.

   - bpo-40495(25): *note compileall: 19. is now able to use hardlinks
     to prevent duplicates in a case when ‘.pyc’ files for different
     optimization levels have the same content.

   - bpo-40457(26): The ssl module now support OpenSSL builds without
     TLS 1.0 and 1.1 methods.

   - bpo-40355(27): Improve error reporting in *note ast.literal_eval():
     bbf. in the presence of malformed *note ast.Dict: 185f. nodes
     instead of silently ignoring any non-conforming elements.  Patch by
     Curtis Bucher.

   - bpo-40465(28): Deprecated the optional 'random' argument to
     'random.shuffle()'.

   - bpo-40459(29): *note platform.win32_ver(): 1860. now produces
     correct 'ptype' strings instead of empty strings.

   - bpo-39435(30): The first argument of *note pickle.loads(): cb8. is
     now positional-only.

   - bpo-39305(31): Update ‘nntplib’ to merge ‘nntplib.NNTP’ and
     ‘nntplib._NNTPBase’.  Patch by Donghee Na.

   - bpo-32494(32): Update *note dbm.gnu: 2b. to use gdbm_count if
     possible when calling *note len(): 5d4.  Patch by Donghee Na.

   - bpo-40453(33): Add ‘isolated=True’ keyword-only parameter to
     ‘_xxsubinterpreters.create()’.  An isolated subinterpreter cannot
     spawn threads, spawn a child process or call ‘os.fork()’.

   - bpo-40286(34): Remove ‘_random.Random.randbytes()’: the C
     implementation of ‘randbytes()’.  Implement the method in Python to
     ease subclassing: ‘randbytes()’ now directly reuses
     ‘getrandbits()’.

   - bpo-40394(35): Added default arguments to *note
     difflib.SequenceMatcher.find_longest_match(): 1861.

   - bpo-39995(36): Fix a race condition in
     concurrent.futures._ThreadWakeup: access to _ThreadWakeup is now
     protected with the shutdown lock.

   - bpo-30966(37): ‘Process.shutdown(wait=True)’ of *note
     concurrent.futures: 1a. now closes explicitly the result queue.

   - bpo-30966(38): Add a new *note close(): 8ba. method to the *note
     SimpleQueue: 8b9. class to explicitly close the queue.

   - bpo-39966(39): Revert bpo-25597(40).  *note
     unittest.mock.MagicMock: e33. with wraps' set uses default return
     values for magic methods.

   - bpo-39791(41): Added ‘files()’ function to importlib.resources with
     support for subdirectories in package data, matching backport in
     importlib_resources 1.5.

   - bpo-40375(42): *note imaplib.IMAP4.unselect(): 8ac. is added.
     Patch by Donghee Na.

   - bpo-40389(43): ‘repr()’ now returns ‘typing.Optional[T]’ when
     called for ‘typing.Union’ of two types, one of which is ‘NoneType’.

   - bpo-40291(44): Add support for CAN_J1939 sockets (available on
     Linux 5.4+)

   - bpo-40273(45): *note types.MappingProxyType: 414. is now
     reversible.

   - bpo-39075(46): The repr for *note types.SimpleNamespace: 1b5. is
     now insertion ordered rather than alphabetical.

   - bpo-40192(47): On AIX, *note thread_time(): 8da. is now implemented
     with ‘thread_cputime()’ which has nanosecond resolution, rather
     than ‘clock_gettime(CLOCK_THREAD_CPUTIME_ID)’ which has a
     resolution of 10 milliseconds.  Patch by Batuhan Taskaya.

   - bpo-40025(48): Raise TypeError when _generate_next_value_ is
     defined after members.  Patch by Ethan Onstott.

   - bpo-39058(49): In the argparse module, the repr for Namespace() and
     other argument holders now displayed in the order attributes were
     added.  Formerly, it displayed in alphabetical order even though
     argument order is preserved the user visible parts of the module.

   - bpo-24416(50): The ‘isocalendar()’ methods of *note datetime.date:
     1b1. and *note datetime.datetime: 1b0. now return a *note named
     tuple: 5f4. instead of a *note tuple: 322.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40662

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40665

   (3) https://bugs.python.org/issue?@action=redirect&bpo=40536

   (4) https://bugs.python.org/issue?@action=redirect&bpo=40645

   (5) https://bugs.python.org/issue?@action=redirect&bpo=40645

   (6) https://bugs.python.org/issue?@action=redirect&bpo=40637

   (7) https://bugs.python.org/issue?@action=redirect&bpo=37630

   (8) https://bugs.python.org/issue?@action=redirect&bpo=40479

   (9) https://bugs.python.org/issue?@action=redirect&bpo=40257

   (10) https://bugs.python.org/issue?@action=redirect&bpo=40607

   (11) https://bugs.python.org/issue?@action=redirect&bpo=40612

   (12) https://bugs.python.org/issue?@action=redirect&bpo=40597

   (13) https://bugs.python.org/issue?@action=redirect&bpo=40571

   (14) https://bugs.python.org/issue?@action=redirect&bpo=40503

   (15) https://peps.python.org/pep-0615/

   (16) https://bugs.python.org/issue?@action=redirect&bpo=40397

   (17) https://bugs.python.org/issue?@action=redirect&bpo=40549

   (18) https://bugs.python.org/issue?@action=redirect&bpo=31033

   (19) https://bugs.python.org/issue?@action=redirect&bpo=40541

   (20) https://bugs.python.org/issue?@action=redirect&bpo=40515

   (21) https://bugs.python.org/issue?@action=redirect&bpo=31033

   (22) https://bugs.python.org/issue?@action=redirect&bpo=40504

   (23) https://bugs.python.org/issue?@action=redirect&bpo=40559

   (24) https://bugs.python.org/issue?@action=redirect&bpo=40480

   (25) https://bugs.python.org/issue?@action=redirect&bpo=40495

   (26) https://bugs.python.org/issue?@action=redirect&bpo=40457

   (27) https://bugs.python.org/issue?@action=redirect&bpo=40355

   (28) https://bugs.python.org/issue?@action=redirect&bpo=40465

   (29) https://bugs.python.org/issue?@action=redirect&bpo=40459

   (30) https://bugs.python.org/issue?@action=redirect&bpo=39435

   (31) https://bugs.python.org/issue?@action=redirect&bpo=39305

   (32) https://bugs.python.org/issue?@action=redirect&bpo=32494

   (33) https://bugs.python.org/issue?@action=redirect&bpo=40453

   (34) https://bugs.python.org/issue?@action=redirect&bpo=40286

   (35) https://bugs.python.org/issue?@action=redirect&bpo=40394

   (36) https://bugs.python.org/issue?@action=redirect&bpo=39995

   (37) https://bugs.python.org/issue?@action=redirect&bpo=30966

   (38) https://bugs.python.org/issue?@action=redirect&bpo=30966

   (39) https://bugs.python.org/issue?@action=redirect&bpo=39966

   (40) https://bugs.python.org/issue?@action=redirect&bpo=25597

   (41) https://bugs.python.org/issue?@action=redirect&bpo=39791

   (42) https://bugs.python.org/issue?@action=redirect&bpo=40375

   (43) https://bugs.python.org/issue?@action=redirect&bpo=40389

   (44) https://bugs.python.org/issue?@action=redirect&bpo=40291

   (45) https://bugs.python.org/issue?@action=redirect&bpo=40273

   (46) https://bugs.python.org/issue?@action=redirect&bpo=39075

   (47) https://bugs.python.org/issue?@action=redirect&bpo=40192

   (48) https://bugs.python.org/issue?@action=redirect&bpo=40025

   (49) https://bugs.python.org/issue?@action=redirect&bpo=39058

   (50) https://bugs.python.org/issue?@action=redirect&bpo=24416


File: python.info,  Node: Documentation<32>,  Next: Tests<35>,  Prev: Library<37>,  Up: Python 3 9 0 beta 1

1.23.38.4 Documentation
.......................

   - bpo-34790(1): Add version of removal for explicit passing of coros
     to ‘asyncio.wait()’'s documentation

   - bpo-40561(2): Provide docstrings for webbrowser open functions.

   - bpo-40499(3): Mention that *note asyncio.wait(): 426. requires a
     non-empty set of awaitables.

   - bpo-39705(4): Tutorial example for sorted() in the Loop Techniques
     section is given a better explanation.  Also a new example is
     included to explain sorted()'s basic behavior.

   - bpo-39435(5): Fix an incorrect signature for *note pickle.loads():
     cb8. in the docs

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=34790

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40561

   (3) https://bugs.python.org/issue?@action=redirect&bpo=40499

   (4) https://bugs.python.org/issue?@action=redirect&bpo=39705

   (5) https://bugs.python.org/issue?@action=redirect&bpo=39435


File: python.info,  Node: Tests<35>,  Next: Build<37>,  Prev: Documentation<32>,  Up: Python 3 9 0 beta 1

1.23.38.5 Tests
...............

   - bpo-40055(1): distutils.tests now saves/restores warnings filters
     to leave them unchanged.  Importing tests imports docutils which
     imports pkg_resources which adds a warnings filter.

   - bpo-40436(2): test_gdb and test.pythoninfo now check gdb command
     exit code.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40055

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40436


File: python.info,  Node: Build<37>,  Next: Windows<33>,  Prev: Tests<35>,  Up: Python 3 9 0 beta 1

1.23.38.6 Build
...............

   - bpo-40653(1): Move _dirnameW out of HAVE_SYMLINK to fix a potential
     compiling issue.

   - bpo-40514(2): Add ‘--with-experimental-isolated-subinterpreters’
     build option to ‘configure’: better isolate subinterpreters,
     experimental build mode.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40653

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40514


File: python.info,  Node: Windows<33>,  Next: macOS<28>,  Prev: Build<37>,  Up: Python 3 9 0 beta 1

1.23.38.7 Windows
.................

   - bpo-40650(1): Include winsock2.h in pytime.c for timeval.

   - bpo-40458(2): Increase reserved stack space to prevent overflow
     crash on Windows.

   - bpo-39148(3): Add IPv6 support to *note asyncio: 8. datagram
     endpoints in ProactorEventLoop.  Change the raised exception for
     unknown address families to ValueError as it's not coming from
     Windows API.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40650

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40458

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39148


File: python.info,  Node: macOS<28>,  Next: Tools/Demos<16>,  Prev: Windows<33>,  Up: Python 3 9 0 beta 1

1.23.38.8 macOS
...............

   - bpo-34956(1): When building Python on macOS from source, ‘_tkinter’
     now links with non-system Tcl and Tk frameworks if they are
     installed in ‘/Library/Frameworks’, as had been the case on older
     releases of macOS. If a macOS SDK is explicitly configured, by
     using ‘--enable-universalsdk=’ or ‘-isysroot’, only the SDK itself
     is searched.  The default behavior can still be overridden with
     ‘--with-tcltk-includes’ and ‘--with-tcltk-libs’.

   - bpo-35569(2): Expose RFC 3542 IPv6 socket options.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=34956

   (2) https://bugs.python.org/issue?@action=redirect&bpo=35569


File: python.info,  Node: Tools/Demos<16>,  Next: C API<36>,  Prev: macOS<28>,  Up: Python 3 9 0 beta 1

1.23.38.9 Tools/Demos
.....................

   - bpo-40479(1): Update multissltest helper to test with latest
     OpenSSL 1.0.2, 1.1.0, 1.1.1, and 3.0.0-alpha.

   - bpo-40431(2): Fix a syntax typo in ‘turtledemo’ that now raises a
     ‘SyntaxError’.

   - bpo-40163(3): Fix multissltest tool.  OpenSSL has changed download
     URL for old releases.  The multissltest tool now tries to download
     from current and old download URLs.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40479

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40431

   (3) https://bugs.python.org/issue?@action=redirect&bpo=40163


File: python.info,  Node: C API<36>,  Prev: Tools/Demos<16>,  Up: Python 3 9 0 beta 1

1.23.38.10 C API
................

   - bpo-39465(1): Remove the ‘_PyUnicode_ClearStaticStrings()’ function
     from the C API.

   - bpo-38787(2): Add PyCFunction_CheckExact() macro for exact type
     checks now that we allow subtypes of PyCFunction, as well as
     PyCMethod_CheckExact() and PyCMethod_Check() for the new PyCMethod
     subtype.

   - bpo-40545(3): Declare ‘_PyErr_GetTopmostException()’ with
     ‘PyAPI_FUNC()’ to properly export the function in the C API. The
     function remains private (‘_Py’) prefix.

   - bpo-40412(4): Nullify inittab_copy during finalization, preventing
     future interpreter initializations in an embedded situation from
     crashing.  Patch by Gregory Szorc.

   - bpo-40429(5): The *note PyThreadState_GetFrame(): 732. function now
     returns a strong reference to the frame.

   - bpo-40428(6): Remove the following functions from the C API. Call
     *note PyGC_Collect(): 932. explicitly to free all free lists.

        * ‘PyAsyncGen_ClearFreeLists()’

        * ‘PyContext_ClearFreeList()’

        * ‘PyDict_ClearFreeList()’

        * ‘PyFloat_ClearFreeList()’

        * ‘PyFrame_ClearFreeList()’

        * ‘PyList_ClearFreeList()’

        * ‘PySet_ClearFreeList()’

        * ‘PyTuple_ClearFreeList()’

   - bpo-40421(7): New *note PyFrame_GetBack(): 72a. function: get the
     frame next outer frame.

   - bpo-40421(8): New *note PyFrame_GetCode(): 72e. function: return a
     borrowed reference to the frame code.

   - bpo-40217(9): Ensure that instances of types created with *note
     PyType_FromSpecWithBases(): 524. will visit its class object when
     traversing references in the garbage collector (implemented as an
     extension of the provided *note tp_traverse: 721.).  Patch by Pablo
     Galindo.

   - bpo-38787(10): Module C state is now accessible from C-defined heap
     type methods ( PEP 573(11)).  Patch by Marcel Plch and Petr
     Viktorin.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39465

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38787

   (3) https://bugs.python.org/issue?@action=redirect&bpo=40545

   (4) https://bugs.python.org/issue?@action=redirect&bpo=40412

   (5) https://bugs.python.org/issue?@action=redirect&bpo=40429

   (6) https://bugs.python.org/issue?@action=redirect&bpo=40428

   (7) https://bugs.python.org/issue?@action=redirect&bpo=40421

   (8) https://bugs.python.org/issue?@action=redirect&bpo=40421

   (9) https://bugs.python.org/issue?@action=redirect&bpo=40217

   (10) https://bugs.python.org/issue?@action=redirect&bpo=38787

   (11) https://peps.python.org/pep-0573/


File: python.info,  Node: Python 3 9 0 alpha 6,  Next: Python 3 9 0 alpha 5,  Prev: Python 3 9 0 beta 1,  Up: Changelog（更動日誌）

1.23.39 Python 3.9.0 alpha 6
----------------------------

'Release date: 2020-04-27'

* Menu:

* Security: Security<25>.
* Core and Builtins: Core and Builtins<39>.
* Library: Library<38>.
* Documentation: Documentation<33>.
* Tests: Tests<36>.
* Build: Build<38>.
* Windows: Windows<34>.
* macOS: macOS<29>.
* IDLE: IDLE<25>.
* Tools/Demos: Tools/Demos<17>.
* C API: C API<37>.


File: python.info,  Node: Security<25>,  Next: Core and Builtins<39>,  Up: Python 3 9 0 alpha 6

1.23.39.1 Security
..................

   - bpo-40121(1): Fixes audit events raised on creating a new socket.

   - bpo-39073(2): Disallow CR or LF in email.headerregistry.Address
     arguments to guard against header injection attacks.

   - bpo-39503(3): CVE-2020-8492(4): The *note AbstractBasicAuthHandler:
     17be. class of the *note urllib.request: f4. module uses an
     inefficient regular expression which can be exploited by an
     attacker to cause a denial of service.  Fix the regex to prevent
     the catastrophic backtracking.  Vulnerability reported by Ben
     Caller and Matt Schwager.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40121

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39073

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39503

   (4) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8492


File: python.info,  Node: Core and Builtins<39>,  Next: Library<38>,  Prev: Security<25>,  Up: Python 3 9 0 alpha 6

1.23.39.2 Core and Builtins
...........................

   - bpo-40313(1): Improve the performance of bytes.hex().

   - bpo-40334(2): Switch to a new parser, based on PEG. For more
     details see PEP 617.  To temporarily switch back to the old parser,
     use ‘-X oldparser’ or ‘PYTHONOLDPARSER=1’.  In Python 3.10 we will
     remove the old parser completely, including the ‘parser’ module
     (already deprecated) and anything that depends on it.

   - bpo-40267(3): Fix the tokenizer to display the correct error
     message, when there is a ‘SyntaxError’ on the last input character
     and no newline follows.  It used to be ‘unexpected EOF while
     parsing’, while it should be ‘invalid syntax’.

   - bpo-39522(4): Correctly unparse explicit ‘u’ prefix for strings
     when postponed evaluation for annotations activated.  Patch by
     Batuhan Taskaya.

   - bpo-40246(5): Report a specialized error message, ‘invalid string
     prefix’, when the tokenizer encounters a string with an invalid
     prefix.

   - bpo-40082(6): Fix the signal handler: it now always uses the main
     interpreter, rather than trying to get the current Python thread
     state.

   - bpo-37388(7): str.encode() and str.decode() no longer check the
     encoding and errors in development mode or in debug mode during
     Python finalization.  The codecs machinery can no longer work on
     very late calls to str.encode() and str.decode().

   - bpo-40077(8): Fix possible refleaks in ‘_json’, memo of
     PyScannerObject should be traversed.

   - bpo-37207(9): Speed up calls to ‘dict()’ by using the PEP 590(10)
     ‘vectorcall’ calling convention.

   - bpo-40141(11): Add column and line information to ‘ast.keyword’
     nodes.  Patch by Pablo Galindo.

   - bpo-1635741(12): Port *note resource: aa. to multiphase
     initialization ( PEP 489(13)).

   - bpo-1635741(14): Port *note math: 81. to multiphase initialization
     ( PEP 489(15)).

   - bpo-1635741(16): Port _uuid module to multiphase initialization (
     PEP 489(17)).

   - bpo-40077(18): Convert json module to use *note PyType_FromSpec():
     523.

   - bpo-40067(19): Improve the error message for multiple star
     expressions in an assignment.  Patch by Furkan Onder

   - bpo-1635741(20): Port _functools module to multiphase
     initialization (PEP 489).  Patch by Paulo Henrique Silva.

   - bpo-1635741(21): Port operator module to multiphase initialization
     (PEP 489).  Patch by Paulo Henrique Silva.

   - bpo-20526(22): Fix *note PyThreadState_Clear(): 1515.
     ‘PyThreadState.frame’ is a borrowed reference, not a strong
     reference: ‘PyThreadState_Clear()’ must not call
     ‘Py_CLEAR(tstate->frame)’.

   - bpo-1635741(23): Port time module to multiphase initialization (
     PEP 489(24)).  Patch by Paulo Henrique Silva.

   - bpo-1635741(25): Port _weakref extension module to multiphase
     initialization ( PEP 489(26)).

   - bpo-40020(27): Fix a leak and subsequent crash in parsetok.c caused
     by realloc misuse on a rare codepath.

   - bpo-39939(28): Added str.removeprefix and str.removesuffix methods
     and corresponding bytes, bytearray, and collections.UserString
     methods to remove affixes from a string if present.  See PEP
     616(29) for a full description.  Patch by Dennis Sweeney.

   - bpo-39481(30): Implement PEP 585.  This supports list[int],
     tuple[str, ...]  etc.

   - bpo-32894(31): Support unparsing of infinity numbers in postponed
     annotations.  Patch by Batuhan Taşkaya.

   - bpo-37207(32): Speed up calls to ‘list()’ by using the PEP 590(33)
     ‘vectorcall’ calling convention.  Patch by Mark Shannon.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40313

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40334

   (3) https://bugs.python.org/issue?@action=redirect&bpo=40267

   (4) https://bugs.python.org/issue?@action=redirect&bpo=39522

   (5) https://bugs.python.org/issue?@action=redirect&bpo=40246

   (6) https://bugs.python.org/issue?@action=redirect&bpo=40082

   (7) https://bugs.python.org/issue?@action=redirect&bpo=37388

   (8) https://bugs.python.org/issue?@action=redirect&bpo=40077

   (9) https://bugs.python.org/issue?@action=redirect&bpo=37207

   (10) https://peps.python.org/pep-0590/

   (11) https://bugs.python.org/issue?@action=redirect&bpo=40141

   (12) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (13) https://peps.python.org/pep-0489/

   (14) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (15) https://peps.python.org/pep-0489/

   (16) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (17) https://peps.python.org/pep-0489/

   (18) https://bugs.python.org/issue?@action=redirect&bpo=40077

   (19) https://bugs.python.org/issue?@action=redirect&bpo=40067

   (20) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (21) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (22) https://bugs.python.org/issue?@action=redirect&bpo=20526

   (23) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (24) https://peps.python.org/pep-0489/

   (25) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (26) https://peps.python.org/pep-0489/

   (27) https://bugs.python.org/issue?@action=redirect&bpo=40020

   (28) https://bugs.python.org/issue?@action=redirect&bpo=39939

   (29) https://peps.python.org/pep-0616/

   (30) https://bugs.python.org/issue?@action=redirect&bpo=39481

   (31) https://bugs.python.org/issue?@action=redirect&bpo=32894

   (32) https://bugs.python.org/issue?@action=redirect&bpo=37207

   (33) https://peps.python.org/pep-0590/


File: python.info,  Node: Library<38>,  Next: Documentation<33>,  Prev: Core and Builtins<39>,  Up: Python 3 9 0 alpha 6

1.23.39.3 Library
.................

   - bpo-40398(1): *note typing.get_args(): 822. now always returns an
     empty tuple for special generic aliases.

   - bpo-40396(2): Functions *note typing.get_origin(): 9ea, *note
     typing.get_args(): 822. and *note typing.get_type_hints(): 657.
     support now generic aliases like ‘list[int]’.

   - bpo-38061(3): Optimize the *note subprocess: c1. module on FreeBSD
     using ‘closefrom()’.  A single ‘close(fd)’ syscall is cheap, but
     when ‘sysconf(_SC_OPEN_MAX)’ is high, the loop calling ‘close(fd)’
     on each file descriptor can take several milliseconds.

     The workaround on FreeBSD to improve performance was to load and
     mount the fdescfs kernel module, but this is not enabled by
     default.

     Initial patch by Ed Maste (emaste), Conrad Meyer (cem), Kyle Evans
     (kevans) and Kubilay Kocak (koobs):
     ‘https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242274’

   - bpo-38061(4): On FreeBSD, ‘os.closerange(fd_low, fd_high)’ now
     calls ‘closefrom(fd_low)’ if 'fd_high' is greater than or equal to
     ‘sysconf(_SC_OPEN_MAX)’.

     Initial patch by Ed Maste (emaste), Conrad Meyer (cem), Kyle Evans
     (kevans) and Kubilay Kocak (koobs):
     ‘https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242274’

   - bpo-40360(5): The ‘lib2to3’ module is pending deprecation due to
     PEP 617(6).

   - bpo-40138(7): Fix the Windows implementation of *note os.waitpid():
     d40. for exit code larger than ‘INT_MAX >> 8’.  The exit status is
     now interpreted as an unsigned number.

   - bpo-39942(8): Set "__main__" as the default module name when
     "__name__" is missing in *note typing.TypeVar: 141.  Patch by
     Weipeng Hong.

   - bpo-40275(9): The *note logging: 7b. package is now imported lazily
     in *note unittest: ef. only when the *note assertLogs(): 7fd.
     assertion is used.

   - bpo-40275(10): The *note asyncio: 8. package is now imported lazily
     in *note unittest: ef. only when the *note IsolatedAsyncioTestCase:
     2de. class is used.

   - bpo-40330(11): In ‘ShareableList.__setitem__()’, check the size of
     a new string item after encoding it to utf-8, not before.

   - bpo-40148(12): Added ‘pathlib.Path.with_stem()’ to create a new
     Path with the stem replaced.

   - bpo-40325(13): Deprecated support for set objects in
     random.sample().

   - bpo-40257(14): Improved help for the *note typing: ed. module.
     Docstrings are now shown for all special forms and special generic
     aliases (like ‘Union’ and ‘List’).  Using ‘help()’ with generic
     alias like ‘List[int]’ will show the help for the correspondent
     concrete type (‘list’ in this case).

   - bpo-40257(15): *note inspect.getdoc(): 99e. no longer returns
     docstring inherited from the type of the object or from parent
     class if it is a class if it is not defined in the object itself.
     In *note pydoc: a3. the documentation string is now shown not only
     for class, function, method etc, but for any object that has its
     own ‘__doc__’ attribute.

   - bpo-40287(16): Fixed ‘SpooledTemporaryFile.seek()’ to return the
     position.

   - bpo-40290(17): Added zscore() to statistics.NormalDist().

   - bpo-40282(18): Allow ‘random.getrandbits(0)’ to succeed and to
     return 0.

   - bpo-40286(19): Add *note random.randbytes(): 186d. function and
     ‘random.Random.randbytes()’ method to generate random bytes.

   - bpo-40277(20): *note collections.namedtuple(): 1ae. now provides a
     human-readable repr for its field accessors.

   - bpo-40270(21): The included copy of sqlite3 on Windows is now
     compiled with the json extension.  This allows the use of functions
     such as ‘json_object’.

   - bpo-29255(22): Wait in ‘KqueueSelector.select’ when no fds are
     registered

   - bpo-40260(23): Ensure *note modulefinder: 84. uses *note
     io.open_code(): 1625. and respects coding comments.

   - bpo-40234(24): Allow again to spawn daemon threads in
     subinterpreters (revert change which denied them).

   - bpo-39207(25): Workers in *note ProcessPoolExecutor: 893. are now
     spawned on demand, only when there are no available idle workers to
     reuse.  This optimizes startup overhead and reduces the amount of
     lost CPU time to idle workers.  Patch by Kyle Stanley.

   - bpo-40091(26): Fix a hang at fork in the logging module: the new
     private _at_fork_reinit() method is now used to reinitialize locks
     at fork in the child process.

   - bpo-40149(27): Implement traverse and clear slots in _abc._abc_data
     type.

   - bpo-40208(28): Remove deprecated ‘symtable.SymbolTable.has_exec()’.

   - bpo-40196(29): Fix a bug in the *note symtable: c2. module that was
     causing incorrectly report global variables as local.  Patch by
     Pablo Galindo.

   - bpo-40190(30): Add support for ‘_SC_AIX_REALMEM’ to
     ‘posix.sysconf()’.

   - bpo-40182(31): Removed the ‘_field_types’ attribute of the *note
     typing.NamedTuple: 291. class.

   - bpo-36517(32): Multiple inheritance with *note typing.NamedTuple:
     291. now raises an error instead of silently ignoring other types.

   - bpo-40126(33): Fixed reverting multiple patches in unittest.mock.
     Patcher's ‘__exit__()’ is now never called if its ‘__enter__()’ is
     failed.  Returning true from ‘__exit__()’ silences now the
     exception.

   - bpo-40094(34): CGIHTTPRequestHandler of http.server now logs the
     CGI script exit code, rather than the CGI script exit status of
     os.waitpid().  For example, if the script is killed by signal 11,
     it now logs: "CGI script exit code -11."

   - bpo-40108(35): Improve the error message when triying to import a
     module using *note runpy: ac. and incorrectly using the ".py"
     extension at the end of the module name.  Patch by Pablo Galindo.

   - bpo-40094(36): Add *note os.waitstatus_to_exitcode(): 8c2.
     function: convert a wait status to an exit code.

   - bpo-40089(37): Fix threading._after_fork(): if fork was not called
     by a thread spawned by threading.Thread, threading._after_fork()
     now creates a _MainThread instance for _main_thread, instead of a
     _DummyThread instance.

   - bpo-40089(38): Add a private ‘_at_fork_reinit()’ method to
     ‘_thread.Lock’, ‘_thread.RLock’, *note threading.RLock: 2be. and
     *note threading.Condition: 10ee. classes: reinitialize the lock at
     fork in the child process, reset the lock to the unlocked state.
     Rename also the private ‘_reset_internal_locks()’ method of *note
     threading.Event: 10f1. to ‘_at_fork_reinit()’.

   - bpo-25780(39): Expose *note CAN_RAW_JOIN_FILTERS: 8d5. in the *note
     socket: b8. module.

   - bpo-39503(40): *note AbstractBasicAuthHandler: 17be. of *note
     urllib.request: f4. now parses all WWW-Authenticate HTTP headers
     and accepts multiple challenges per header: use the realm of the
     first Basic challenge.

   - bpo-39812(41): Removed daemon threads from *note
     concurrent.futures: 1a. by adding an internal
     ‘threading._register_atexit()’, which calls registered functions
     prior to joining all non-daemon threads.  This allows for
     compatibility with subinterpreters, which don't support daemon
     threads.

   - bpo-40050(42): Fix ‘importlib._bootstrap_external’: avoid creating
     a new ‘winreg’ builtin module if it's already available in *note
     sys.modules: 186e, and remove redundant imports.

   - bpo-40014(43): Fix ‘os.getgrouplist()’: if ‘getgrouplist()’
     function fails because the group list is too small, retry with a
     larger group list.  On failure, the glibc implementation of
     ‘getgrouplist()’ sets ‘ngroups’ to the total number of groups.  For
     other implementations, double the group list size.

   - bpo-40017(44): Add *note time.CLOCK_TAI: 186f. constant if the
     operating system support it.

   - bpo-40016(45): In re docstring, clarify the relationship between
     inline and argument compile flags.

   - bpo-39953(46): Update internal table of OpenSSL error codes in the
     ‘ssl’ module.

   - bpo-36144(47): Added PEP 584(48) operators to *note
     weakref.WeakValueDictionary: 1870.

   - bpo-36144(49): Added PEP 584(50) operators to *note
     weakref.WeakKeyDictionary: 1871.

   - bpo-38891(51): Fix linear runtime behaviour of the ‘__getitem__’
     and ‘__setitem__’ methods in *note
     multiprocessing.shared_memory.ShareableList: 1872.  This avoids
     quadratic performance when iterating a ‘ShareableList’.  Patch by
     Thomas Krennwallner.

   - bpo-39682(52): Remove undocumented support for 'closing' a
     ‘pathlib.Path’ object via its context manager.  The context manager
     magic methods remain, but they are now a no-op, making ‘Path’
     objects immutable.

   - bpo-36144(53): Added PEP 584(54) operators (‘|’ and ‘|=’) to *note
     collections.ChainMap: bc3.

   - bpo-39011(55): Normalization of line endings in ElementTree
     attributes was removed, as line endings which were replaced by
     entity numbers should be preserved in original form.

   - bpo-38410(56): Properly handle *note sys.audit(): 1873. failures in
     *note sys.set_asyncgen_hooks(): 151a.

   - bpo-36541(57): lib2to3 now recognizes named assignment expressions
     (the walrus operator, ‘:=’)

   - bpo-35967(58): In platform, delay the invocation of 'uname -p'
     until the processor attribute is requested.

   - bpo-35113(59): *note inspect.getsource(): 14ca. now returns correct
     source code for inner class with same name as module level class.
     Decorators are also returned as part of source of the class.  Patch
     by Karthikeyan Singaravelan.

   - bpo-33262(60): Deprecate passing None as an argument for *note
     shlex.split(): 4e1.'s ‘s’ parameter.  Patch by Zackery Spytz.

   - bpo-31758(61): Prevent crashes when using an uninitialized
     ‘_elementtree.XMLParser’ object.  Patch by Oren Milman.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40398

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40396

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38061

   (4) https://bugs.python.org/issue?@action=redirect&bpo=38061

   (5) https://bugs.python.org/issue?@action=redirect&bpo=40360

   (6) https://peps.python.org/pep-0617/

   (7) https://bugs.python.org/issue?@action=redirect&bpo=40138

   (8) https://bugs.python.org/issue?@action=redirect&bpo=39942

   (9) https://bugs.python.org/issue?@action=redirect&bpo=40275

   (10) https://bugs.python.org/issue?@action=redirect&bpo=40275

   (11) https://bugs.python.org/issue?@action=redirect&bpo=40330

   (12) https://bugs.python.org/issue?@action=redirect&bpo=40148

   (13) https://bugs.python.org/issue?@action=redirect&bpo=40325

   (14) https://bugs.python.org/issue?@action=redirect&bpo=40257

   (15) https://bugs.python.org/issue?@action=redirect&bpo=40257

   (16) https://bugs.python.org/issue?@action=redirect&bpo=40287

   (17) https://bugs.python.org/issue?@action=redirect&bpo=40290

   (18) https://bugs.python.org/issue?@action=redirect&bpo=40282

   (19) https://bugs.python.org/issue?@action=redirect&bpo=40286

   (20) https://bugs.python.org/issue?@action=redirect&bpo=40277

   (21) https://bugs.python.org/issue?@action=redirect&bpo=40270

   (22) https://bugs.python.org/issue?@action=redirect&bpo=29255

   (23) https://bugs.python.org/issue?@action=redirect&bpo=40260

   (24) https://bugs.python.org/issue?@action=redirect&bpo=40234

   (25) https://bugs.python.org/issue?@action=redirect&bpo=39207

   (26) https://bugs.python.org/issue?@action=redirect&bpo=40091

   (27) https://bugs.python.org/issue?@action=redirect&bpo=40149

   (28) https://bugs.python.org/issue?@action=redirect&bpo=40208

   (29) https://bugs.python.org/issue?@action=redirect&bpo=40196

   (30) https://bugs.python.org/issue?@action=redirect&bpo=40190

   (31) https://bugs.python.org/issue?@action=redirect&bpo=40182

   (32) https://bugs.python.org/issue?@action=redirect&bpo=36517

   (33) https://bugs.python.org/issue?@action=redirect&bpo=40126

   (34) https://bugs.python.org/issue?@action=redirect&bpo=40094

   (35) https://bugs.python.org/issue?@action=redirect&bpo=40108

   (36) https://bugs.python.org/issue?@action=redirect&bpo=40094

   (37) https://bugs.python.org/issue?@action=redirect&bpo=40089

   (38) https://bugs.python.org/issue?@action=redirect&bpo=40089

   (39) https://bugs.python.org/issue?@action=redirect&bpo=25780

   (40) https://bugs.python.org/issue?@action=redirect&bpo=39503

   (41) https://bugs.python.org/issue?@action=redirect&bpo=39812

   (42) https://bugs.python.org/issue?@action=redirect&bpo=40050

   (43) https://bugs.python.org/issue?@action=redirect&bpo=40014

   (44) https://bugs.python.org/issue?@action=redirect&bpo=40017

   (45) https://bugs.python.org/issue?@action=redirect&bpo=40016

   (46) https://bugs.python.org/issue?@action=redirect&bpo=39953

   (47) https://bugs.python.org/issue?@action=redirect&bpo=36144

   (48) https://peps.python.org/pep-0584/

   (49) https://bugs.python.org/issue?@action=redirect&bpo=36144

   (50) https://peps.python.org/pep-0584/

   (51) https://bugs.python.org/issue?@action=redirect&bpo=38891

   (52) https://bugs.python.org/issue?@action=redirect&bpo=39682

   (53) https://bugs.python.org/issue?@action=redirect&bpo=36144

   (54) https://peps.python.org/pep-0584/

   (55) https://bugs.python.org/issue?@action=redirect&bpo=39011

   (56) https://bugs.python.org/issue?@action=redirect&bpo=38410

   (57) https://bugs.python.org/issue?@action=redirect&bpo=36541

   (58) https://bugs.python.org/issue?@action=redirect&bpo=35967

   (59) https://bugs.python.org/issue?@action=redirect&bpo=35113

   (60) https://bugs.python.org/issue?@action=redirect&bpo=33262

   (61) https://bugs.python.org/issue?@action=redirect&bpo=31758


File: python.info,  Node: Documentation<33>,  Next: Tests<36>,  Prev: Library<38>,  Up: Python 3 9 0 alpha 6

1.23.39.4 Documentation
.......................

   - bpo-27635(1): The pickle documentation incorrectly claimed that
     ‘__new__’ isn't called by default when unpickling.

   - bpo-39879(2): Updated *note 資料模型: 1875. docs to include *note
     dict(): 23b. insertion order preservation.  Patch by Furkan Onder
     and Samy Lahfa.

   - bpo-38387(3): Document *note PyDoc_STRVAR: 1876. macro in the C-API
     reference.

   - bpo-13743(4): Some methods within xml.dom.minidom.Element class are
     now better documented.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27635

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39879

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38387

   (4) https://bugs.python.org/issue?@action=redirect&bpo=13743


File: python.info,  Node: Tests<36>,  Next: Build<38>,  Prev: Documentation<33>,  Up: Python 3 9 0 alpha 6

1.23.39.5 Tests
...............

   - bpo-31904(1): Set expected default encoding in
     test_c_locale_coercion.py for VxWorks RTOS.

   - bpo-40162(2): Update Travis CI configuration to OpenSSL 1.1.1f.

   - bpo-40146(3): Update OpenSSL to 1.1.1f in Azure Pipelines.

   - bpo-40094(4): Add *note test.support.wait_process(): 1878.
     function.

   - bpo-40003(5): ‘test.bisect_cmd’ now copies Python command line
     options like ‘-O’ or ‘-W’.  Moreover, emit a warning if
     ‘test.bisect_cmd’ is used with ‘-w’/‘--verbose2’ option.

   - bpo-39380(6): Add the encoding in *note ftplib.FTP: 89f. and *note
     ftplib.FTP_TLS: 8a0. to the constructor as keyword-only and change
     the default from ‘latin-1’ to ‘utf-8’ to follow RFC 2640(7).

   - bpo-39793(8): Use the same domain when testing ‘make_msgid’.  Patch
     by Batuhan Taskaya.

   - bpo-1812(9): Fix newline handling in doctest.testfile when loading
     from a package whose loader has a get_data method.  Patch by Peter
     Donis.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40162

   (3) https://bugs.python.org/issue?@action=redirect&bpo=40146

   (4) https://bugs.python.org/issue?@action=redirect&bpo=40094

   (5) https://bugs.python.org/issue?@action=redirect&bpo=40003

   (6) https://bugs.python.org/issue?@action=redirect&bpo=39380

   (7) https://datatracker.ietf.org/doc/html/rfc2640.html

   (8) https://bugs.python.org/issue?@action=redirect&bpo=39793

   (9) https://bugs.python.org/issue?@action=redirect&bpo=1812


File: python.info,  Node: Build<38>,  Next: Windows<34>,  Prev: Tests<36>,  Up: Python 3 9 0 alpha 6

1.23.39.6 Build
...............

   - bpo-38360(1): Support single-argument form of macOS -isysroot flag.

   - bpo-40158(2): Fix CPython MSBuild Properties in NuGet Package
     (build/native/python.props)

   - bpo-38527(3): Fix configure check on Solaris for "float word
     ordering": sometimes, the correct "grep" command was not being
     used.  Patch by Arnon Yaari.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38360

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40158

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38527


File: python.info,  Node: Windows<34>,  Next: macOS<29>,  Prev: Build<38>,  Up: Python 3 9 0 alpha 6

1.23.39.7 Windows
.................

   - bpo-40164(1): Updates Windows to OpenSSL 1.1.1f

   - bpo-8901(2): Ignore the Windows registry when the ‘-E’ option is
     used.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40164

   (2) https://bugs.python.org/issue?@action=redirect&bpo=8901


File: python.info,  Node: macOS<29>,  Next: IDLE<25>,  Prev: Windows<34>,  Up: Python 3 9 0 alpha 6

1.23.39.8 macOS
...............

   - bpo-38329(1): python.org macOS installers now update the Current
     version symlink of /Library/Frameworks/Python.framework/Versions
     for 3.9 installs.  Previously, Current was only updated for Python
     2.x installs.  This should make it easier to embed Python 3 into
     other macOS applications.

   - bpo-40164(2): Update macOS installer builds to use OpenSSL 1.1.1g.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38329

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40164


File: python.info,  Node: IDLE<25>,  Next: Tools/Demos<17>,  Prev: macOS<29>,  Up: Python 3 9 0 alpha 6

1.23.39.9 IDLE
..............

   - bpo-38439(1): Add a 256×256 pixel IDLE icon to support more modern
     environments.  Created by Andrew Clover.  Delete the unused macOS
     idle.icns icon file.

   - bpo-38689(2): IDLE will no longer freeze when inspect.signature
     fails when fetching a calltip.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38439

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38689


File: python.info,  Node: Tools/Demos<17>,  Next: C API<37>,  Prev: IDLE<25>,  Up: Python 3 9 0 alpha 6

1.23.39.10 Tools/Demos
......................

   - bpo-40385(1): Removed the checkpyc.py tool.  Please see compileall
     without force mode as a potential alternative.

   - bpo-40179(2): Fixed translation of ‘#elif’ in Argument Clinic.

   - bpo-40094(3): Fix ‘which.py’ script exit code: it now uses *note
     os.waitstatus_to_exitcode(): 8c2. to convert *note os.system():
     13c8. exit status into an exit code.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40385

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40179

   (3) https://bugs.python.org/issue?@action=redirect&bpo=40094


File: python.info,  Node: C API<37>,  Prev: Tools/Demos<17>,  Up: Python 3 9 0 alpha 6

1.23.39.11 C API
................

   - bpo-40241(1): Move the ‘PyGC_Head’ structure to the internal C API.

   - bpo-40170(2): Convert *note PyObject_IS_GC(): 928. macro to a
     function to hide implementation details.

   - bpo-40241(3): Add the functions *note PyObject_GC_IsTracked(): 91a.
     and *note PyObject_GC_IsFinalized(): 91b. to the public API to
     allow to query if Python objects are being currently tracked or
     have been already finalized by the garbage collector respectively.
     Patch by Pablo Galindo.

   - bpo-40170(4): The ‘PyObject_NEW()’ macro becomes an alias to the
     *note PyObject_New(): 929. macro, and the ‘PyObject_NEW_VAR()’
     macro becomes an alias to the *note PyObject_NewVar(): 92a. macro,
     to hide implementation details.  They no longer access directly the
     *note PyTypeObject.tp_basicsize: 92b. member.

   - bpo-40170(5): *note PyType_HasFeature(): 1855. now always calls
     *note PyType_GetFlags(): 1856. to hide implementation details.
     Previously, it accessed directly the *note PyTypeObject.tp_flags:
     17c0. member when the limited C API was not used.

   - bpo-40170(6): Convert the ‘PyObject_GET_WEAKREFS_LISTPTR()’ macro
     to a function to hide implementation details: the macro accessed
     directly to the *note PyTypeObject.tp_weaklistoffset: 92c. member.

   - bpo-40170(7): Convert *note PyObject_CheckBuffer(): 368. macro to a
     function to hide implementation details: the macro accessed
     directly the *note PyTypeObject.tp_as_buffer: 92d. member.

   - bpo-40170(8): Always declare *note PyIndex_Check(): 92e. as an
     opaque function to hide implementation details: remove
     ‘PyIndex_Check()’ macro.  The macro accessed directly the *note
     PyTypeObject.tp_as_number: 92f. member.

   - bpo-39947(9): Add *note PyThreadState_GetID(): 916. function: get
     the unique identifier of a Python thread state.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40241

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40170

   (3) https://bugs.python.org/issue?@action=redirect&bpo=40241

   (4) https://bugs.python.org/issue?@action=redirect&bpo=40170

   (5) https://bugs.python.org/issue?@action=redirect&bpo=40170

   (6) https://bugs.python.org/issue?@action=redirect&bpo=40170

   (7) https://bugs.python.org/issue?@action=redirect&bpo=40170

   (8) https://bugs.python.org/issue?@action=redirect&bpo=40170

   (9) https://bugs.python.org/issue?@action=redirect&bpo=39947


File: python.info,  Node: Python 3 9 0 alpha 5,  Next: Python 3 9 0 alpha 4,  Prev: Python 3 9 0 alpha 6,  Up: Changelog（更動日誌）

1.23.40 Python 3.9.0 alpha 5
----------------------------

'Release date: 2020-03-23'

* Menu:

* Security: Security<26>.
* Core and Builtins: Core and Builtins<40>.
* Library: Library<39>.
* Documentation: Documentation<34>.
* Tests: Tests<37>.
* Build: Build<39>.
* Windows: Windows<35>.
* macOS: macOS<30>.
* IDLE: IDLE<26>.
* Tools/Demos: Tools/Demos<18>.
* C API: C API<38>.


File: python.info,  Node: Security<26>,  Next: Core and Builtins<40>,  Up: Python 3 9 0 alpha 5

1.23.40.1 Security
..................

   - bpo-38576(1): Disallow control characters in hostnames in
     http.client, addressing CVE-2019-18348(2).  Such potentially
     malicious header injection URLs now cause a InvalidURL to be
     raised.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38576

   (2) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18348


File: python.info,  Node: Core and Builtins<40>,  Next: Library<39>,  Prev: Security<26>,  Up: Python 3 9 0 alpha 5

1.23.40.2 Core and Builtins
...........................

   - bpo-40010(1): Optimize pending calls in multithreaded applications.
     If a thread different than the main thread schedules a pending call
     (*note Py_AddPendingCall(): 925.), the bytecode evaluation loop is
     no longer interrupted at each bytecode instruction to check for
     pending calls which cannot be executed.  Only the main thread can
     execute pending calls.

     Previously, the bytecode evaluation loop was interrupted at each
     instruction until the main thread executes pending calls.

   - bpo-1635741(2): Port _weakref extension module to multiphase
     initialization ( PEP 489(3)).

   - bpo-1635741(4): Port _collections module to multiphase
     initialization ( PEP 489(5)).

   - bpo-40010(6): Optimize signal handling in multithreaded
     applications.  If a thread different than the main thread gets a
     signal, the bytecode evaluation loop is no longer interrupted at
     each bytecode instruction to check for pending signals which cannot
     be handled.  Only the main thread of the main interpreter can
     handle signals.

     Previously, the bytecode evaluation loop was interrupted at each
     instruction until the main thread handles signals.

   - bpo-39984(7): If *note Py_AddPendingCall(): 925. is called in a
     subinterpreter, the function is now scheduled to be called from the
     subinterpreter, rather than being called from the main interpreter.
     Each subinterpreter now has its own list of scheduled calls.

   - bpo-1635741(8): Port _heapq module to multiphase initialization.

   - bpo-1635741(9): Port itertools module to multiphase initialization
     ( PEP 489(10)).

   - bpo-37207(11): Speed up calls to ‘frozenset()’ by using the PEP
     590(12) ‘vectorcall’ calling convention.  Patch by Donghee Na.

   - bpo-39984(13): subinterpreters: Move
     ‘_PyRuntimeState.ceval.tracing_possible’ to
     ‘PyInterpreterState.ceval.tracing_possible’: each interpreter now
     has its own variable.

   - bpo-37207(14): Speed up calls to ‘set()’ by using the PEP 590(15)
     ‘vectorcall’ calling convention.  Patch by Donghee Na.

   - bpo-1635741(16): Port _statistics module to multiphase
     initialization ( PEP 489(17)).

   - bpo-39968(18): Use inline function to replace extension modules'
     get_module_state macros.

   - bpo-39965(19): Correctly raise ‘SyntaxError’ if 'await' is used
     inside non-async functions and ‘PyCF_ALLOW_TOP_LEVEL_AWAIT’ is set
     (like in the asyncio REPL). Patch by Pablo Galindo.

   - bpo-39562(20): Allow executing asynchronous comprehensions on the
     top level when the ‘PyCF_ALLOW_TOP_LEVEL_AWAIT’ flag is given.
     Patch by Batuhan Taskaya.

   - bpo-37207(21): Speed up calls to ‘tuple()’ by using the PEP 590(22)
     ‘vectorcall’ calling convention.  Patch by Donghee Na.

   - bpo-38373(23): Changed list overallocation strategy.  It no longer
     overallocates if the new size is closer to overallocated size than
     to the old size and adds padding.

   - bpo-39926(24): Update Unicode database to Unicode version 13.0.0.

   - bpo-19466(25): Clear the frames of daemon threads earlier during
     the Python shutdown to call objects destructors.  So "unclosed
     file" resource warnings are now emitted for daemon threads in a
     more reliable way.

   - bpo-38894(26): Fix a bug that was causing incomplete results when
     calling ‘pathlib.Path.glob’ in the presence of symlinks that point
     to files where the user does not have read access.  Patch by Pablo
     Galindo and Matt Wozniski.

   - bpo-39877(27): Fix *note PyEval_RestoreThread(): 374. random crash
     at exit with daemon threads.  It now accesses the ‘_PyRuntime’
     variable directly instead of using ‘tstate->interp->runtime’, since
     ‘tstate’ can be a dangling pointer after *note Py_Finalize(): 12e6.
     has been called.  Moreover, the daemon thread now exits before
     trying to take the GIL.

   - bpo-39871(28): Fix a possible *note SystemError: 51b. in
     ‘math.{atan2,copysign,remainder}()’ when the first argument cannot
     be converted to a *note float: 2c8.  Patch by Zackery Spytz.

   - bpo-39776(29): Fix race condition where threads created by
     PyGILState_Ensure() could get a duplicate id.

     This affects consumers of tstate->id like the contextvar caching
     machinery, which could return invalid cached objects under heavy
     thread load (observed in embedded scenarios).

   - bpo-39778(30): Fixed a crash due to incorrect handling of weak
     references in ‘collections.OrderedDict’ classes.  Patch by Pablo
     Galindo.

   - bpo-1635741(31): Port audioop extension module to multiphase
     initialization ( PEP 489(32)).

   - bpo-39702(33): Relax *note decorator: 6d5. grammar restrictions to
     allow any valid expression ( PEP 614(34)).

   - bpo-38091(35): Tweak import deadlock detection code to not deadlock
     itself.

   - bpo-1635741(36): Port _locale extension module to multiphase
     initialization ( PEP 489(37)).

   - bpo-39087(38): Optimize *note PyUnicode_AsUTF8(): b62. and *note
     PyUnicode_AsUTF8AndSize(): 83d. slightly when they need to create
     internal UTF-8 cache.

   - bpo-39520(39): Fix unparsing of ext slices with no items
     (‘foo[:,]’).  Patch by Batuhan Taskaya.

   - bpo-39220(40): Do not optimize annotations if 'from __future__
     import annotations' is used.  Patch by Pablo Galindo.

   - bpo-35712(41): Using *note NotImplemented: 776. in a boolean
     context has been deprecated.  Patch contributed by Josh Rosenberg.

   - bpo-22490(42): Don't leak environment variable
     ‘__PYVENV_LAUNCHER__’ into the interpreter session on macOS.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40010

   (2) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (3) https://peps.python.org/pep-0489/

   (4) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (5) https://peps.python.org/pep-0489/

   (6) https://bugs.python.org/issue?@action=redirect&bpo=40010

   (7) https://bugs.python.org/issue?@action=redirect&bpo=39984

   (8) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (9) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (10) https://peps.python.org/pep-0489/

   (11) https://bugs.python.org/issue?@action=redirect&bpo=37207

   (12) https://peps.python.org/pep-0590/

   (13) https://bugs.python.org/issue?@action=redirect&bpo=39984

   (14) https://bugs.python.org/issue?@action=redirect&bpo=37207

   (15) https://peps.python.org/pep-0590/

   (16) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (17) https://peps.python.org/pep-0489/

   (18) https://bugs.python.org/issue?@action=redirect&bpo=39968

   (19) https://bugs.python.org/issue?@action=redirect&bpo=39965

   (20) https://bugs.python.org/issue?@action=redirect&bpo=39562

   (21) https://bugs.python.org/issue?@action=redirect&bpo=37207

   (22) https://peps.python.org/pep-0590/

   (23) https://bugs.python.org/issue?@action=redirect&bpo=38373

   (24) https://bugs.python.org/issue?@action=redirect&bpo=39926

   (25) https://bugs.python.org/issue?@action=redirect&bpo=19466

   (26) https://bugs.python.org/issue?@action=redirect&bpo=38894

   (27) https://bugs.python.org/issue?@action=redirect&bpo=39877

   (28) https://bugs.python.org/issue?@action=redirect&bpo=39871

   (29) https://bugs.python.org/issue?@action=redirect&bpo=39776

   (30) https://bugs.python.org/issue?@action=redirect&bpo=39778

   (31) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (32) https://peps.python.org/pep-0489/

   (33) https://bugs.python.org/issue?@action=redirect&bpo=39702

   (34) https://peps.python.org/pep-0614/

   (35) https://bugs.python.org/issue?@action=redirect&bpo=38091

   (36) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (37) https://peps.python.org/pep-0489/

   (38) https://bugs.python.org/issue?@action=redirect&bpo=39087

   (39) https://bugs.python.org/issue?@action=redirect&bpo=39520

   (40) https://bugs.python.org/issue?@action=redirect&bpo=39220

   (41) https://bugs.python.org/issue?@action=redirect&bpo=35712

   (42) https://bugs.python.org/issue?@action=redirect&bpo=22490


File: python.info,  Node: Library<39>,  Next: Documentation<34>,  Prev: Core and Builtins<40>,  Up: Python 3 9 0 alpha 5

1.23.40.3 Library
.................

   - bpo-39830(1): Add *note zipfile.Path: 66b. to ‘__all__’ in the
     *note zipfile: 117. module.

   - bpo-40000(2): Improved error messages for validation of
     ‘ast.Constant’ nodes.  Patch by Batuhan Taskaya.

   - bpo-39999(3): ‘__module__’ of the AST node classes is now set to
     "ast" instead of "_ast".  Added docstrings for dummy AST node
     classes and deprecated attributes.

   - bpo-39991(4): *note uuid.getnode(): b4e. now skips IPv6 addresses
     with the same string length than a MAC address (17 characters):
     only use MAC addresses.

   - bpo-39988(5): Deprecated ‘ast.AugLoad’ and ‘ast.AugStore’ node
     classes because they are no longer used.

   - bpo-39656(6): Ensure ‘bin/python3.#’ is always present in virtual
     environments on POSIX platforms - by Anthony Sottile.

   - bpo-39969(7): Deprecated ‘ast.Param’ node class because it's no
     longer used.  Patch by Batuhan Taskaya.

   - bpo-39360(8): Ensure all workers exit when finalizing a
     ‘multiprocessing.Pool’ implicitly via the module finalization
     handlers of multiprocessing.  This fixes a deadlock situation that
     can be experienced when the Pool is not properly finalized via the
     context manager or a call to ‘multiprocessing.Pool.terminate’.
     Patch by Batuhan Taskaya and Pablo Galindo.

   - bpo-35370(9): sys.settrace(), sys.setprofile() and
     _lsprof.Profiler.enable() now properly report *note PySys_Audit():
     321. error if "sys.setprofile" or "sys.settrace" audit event is
     denied.

   - bpo-39936(10): AIX: Fix _aix_support module when the subprocess is
     not available, when building Python from scratch.  It now uses new
     private _bootsubprocess module, rather than having two
     implementations depending if subprocess is available or not.  So
     _aix_support.aix_platform() result is now the same if subprocess is
     available or not.

   - bpo-36144(11): *note collections.OrderedDict: 57f. now implements
     ‘|’ and ‘|=’ ( PEP 584(12)).

   - bpo-39652(13): The column name found in
     ‘sqlite3.Cursor.description’ is now truncated on the first '[' only
     if the PARSE_COLNAMES option is set.

   - bpo-39915(14): Ensure *note
     unittest.mock.AsyncMock.await_args_list: 1883. has call objects in
     the order of awaited arguments instead of using *note
     unittest.mock.Mock.call_args: 1884. which has the last value of the
     call.  Patch by Karthikeyan Singaravelan.

   - bpo-36144(15): Updated *note os.environ: 1152. and *note
     os.environb: 11ae. to support PEP 584(16)'s merge (‘|’) and update
     (‘|=’) operators.

   - bpo-38662(17): The ‘ensurepip’ module now invokes ‘pip’ via the
     ‘runpy’ module.  Hence it is no longer tightly coupled with the
     internal API of the bundled ‘pip’ version, allowing easier updates
     to a newer ‘pip’ version both internally and for distributors.

   - bpo-38075(18): Fix the *note random.Random.seed(): 1885. method
     when a *note bool: 40e. is passed as the seed.

   - bpo-39916(19): More reliable use of ‘os.scandir()’ in
     ‘Path.glob()’.  It no longer emits a ResourceWarning when
     interrupted.

   - bpo-39850(20): *note multiprocessing: 86. now supports abstract
     socket addresses (if abstract sockets are supported in the running
     platform).  When creating arbitrary addresses (like when
     default-constructing *note multiprocessing.connection.Listener:
     15a1. objects) abstract sockets are preferred to avoid the case
     when the temporary-file-generated address is too large for an
     AF_UNIX socket address.  Patch by Pablo Galindo.

   - bpo-36287(21): *note ast.dump(): 889. no longer outputs optional
     fields and attributes with default values.  The default values for
     optional fields and attributes of AST nodes are now set as class
     attributes (e.g.  ‘Constant.kind’ is set to ‘None’).

   - bpo-39889(22): Fixed *note ast.unparse(): 88a. for extended slices
     containing a single element (e.g.  ‘a[i:j,]’).  Remove redundant
     tuples when index with a tuple (e.g.  ‘a[i, j]’).

   - bpo-39828(23): Fix *note json.tool: 77. to catch *note
     BrokenPipeError: fff.  Patch by Donghee Na.

   - bpo-13487(24): Avoid a possible '"RuntimeError: dictionary changed
     size during iteration"' from *note inspect.getmodule(): 16e9. when
     it tried to loop through *note sys.modules: 186e.

   - bpo-39674(25): Revert "bpo-37330(26): open() no longer accept 'U'
     in file mode".  The "U" mode of open() is kept in Python 3.9 to
     ease transition from Python 2.7, but will be removed in Python
     3.10.

   - bpo-28577(27): The hosts method on 32-bit prefix length
     IPv4Networks and 128-bit prefix IPv6Networks now returns a list
     containing the single Address instead of an empty list.

   - bpo-39826(28): Add getConnection method to logging HTTPHandler to
     enable custom connections.

   - bpo-39763(29): Reimplement ‘distutils.spawn.spawn’ function with
     the *note subprocess: c1. module.

   - bpo-39794(30): Add -without-decimal-contextvar build option.  This
     enables a thread-local rather than a coroutine local context.

   - bpo-36144(31): *note collections.defaultdict: 1155. now implements
     ‘|’ ( PEP 584(32)).

   - bpo-39517(33): Fix runpy.run_path() when using pathlike objects

   - bpo-39775(34): Change ‘inspect.Signature.parameters’ back to
     ‘collections.OrderedDict’.  This was changed to ‘dict’ in Python
     3.9.0a4.

   - bpo-39678(35): Refactor queue_manager in *note
     concurrent.futures.ProcessPoolExecutor: 893. to make it easier to
     maintain.

   - bpo-39764(36): Fix AttributeError when calling get_stack on a
     PyAsyncGenObject Task

   - bpo-39769(37): The *note compileall.compile_dir(): aca. function's
     'ddir' parameter and the compileall command line flag ‘-d’ no
     longer write the wrong pathname to the generated pyc file for
     submodules beneath the root of the directory tree being compiled.
     This fixes a regression introduced with Python 3.5.

   - bpo-36144(38): *note types.MappingProxyType: 414. objects now
     support the merge (‘|’) operator from PEP 584(39).

   - bpo-38691(40): The *note importlib: 6b. module now ignores the
     *note PYTHONCASEOK: 900. environment variable when the *note -E:
     901. or *note -I: 902. command line options are being used.

   - bpo-39719(41): Remove ‘tempfile.SpooledTemporaryFile.softspace()’
     as files no longer have the ‘softspace’ attribute in Python 3.
     Patch by Shantanu.

   - bpo-39667(42): Improve pathlib.Path compatibility on zipfile.Path
     and correct performance degradation as found in zipp 3.0.

   - bpo-39638(43): Keep ASDL signatures in the docstrings for ‘AST’
     nodes.  Patch by Batuhan Taskaya

   - bpo-39639(44): Deprecated ‘ast.Suite’ node class because it's no
     longer used.  Patch by Batuhan Taskaya.

   - bpo-39609(45): Add thread_name_prefix to default asyncio executor

   - bpo-39548(46): Fix handling of header in *note
     urllib.request.AbstractDigestAuthHandler: 1886. when the optional
     ‘qop’ parameter is not present.

   - bpo-39509(47): HTTP status codes ‘103 EARLY_HINTS’ and ‘425
     TOO_EARLY’ are added to *note http.HTTPStatus: 8a5.  Patch by
     Donghee Na.

   - bpo-39507(48): Adding HTTP status 418 "I'm a Teapot" to HTTPStatus
     in http library.  Patch by Ross Rhodes.

   - bpo-39495(49): Remove default value from 'attrs' parameter of *note
     xml.etree.ElementTree.TreeBuilder.start(): 1887. for consistency
     between Python and C implementations.

   - bpo-38971(50): Open issue in the BPO indicated a desire to make the
     implementation of codecs.open() at parity with io.open(), which
     implements a try/except to assure file stream gets closed before an
     exception is raised.

   - bpo-38641(51): Added starred expressions support to ‘return’ and
     ‘yield’ statements for ‘lib2to3’.  Patch by Vlad Emelianov.

   - bpo-37534(52): When using minidom module to generate XML documents
     the ability to add Standalone Document Declaration is added.  All
     the changes are made to generate a document in compliance with
     Extensible Markup Language (XML) 1.0 (Fifth Edition) W3C
     Recommendation (available here:
     ‘https://www.w3.org/TR/xml/#sec-prolog-dtd’).

   - bpo-34788(53): Add support for scoped IPv6 addresses to *note
     ipaddress: 74.  Patch by Oleksandr Pavliuk.

   - bpo-34822(54): Simplified AST for subscription.  Simple indices are
     now represented by their value, extended slices are represented as
     tuples.  *note ast: 7. classes ‘Index’ and ‘ExtSlice’ are
     considered deprecated and will be removed in future Python
     versions.  In the meantime, ‘Index(value)’ now returns a ‘value’
     itself, ‘ExtSlice(slices)’ returns ‘Tuple(slices, Load())’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39830

   (2) https://bugs.python.org/issue?@action=redirect&bpo=40000

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39999

   (4) https://bugs.python.org/issue?@action=redirect&bpo=39991

   (5) https://bugs.python.org/issue?@action=redirect&bpo=39988

   (6) https://bugs.python.org/issue?@action=redirect&bpo=39656

   (7) https://bugs.python.org/issue?@action=redirect&bpo=39969

   (8) https://bugs.python.org/issue?@action=redirect&bpo=39360

   (9) https://bugs.python.org/issue?@action=redirect&bpo=35370

   (10) https://bugs.python.org/issue?@action=redirect&bpo=39936

   (11) https://bugs.python.org/issue?@action=redirect&bpo=36144

   (12) https://peps.python.org/pep-0584/

   (13) https://bugs.python.org/issue?@action=redirect&bpo=39652

   (14) https://bugs.python.org/issue?@action=redirect&bpo=39915

   (15) https://bugs.python.org/issue?@action=redirect&bpo=36144

   (16) https://peps.python.org/pep-0584/

   (17) https://bugs.python.org/issue?@action=redirect&bpo=38662

   (18) https://bugs.python.org/issue?@action=redirect&bpo=38075

   (19) https://bugs.python.org/issue?@action=redirect&bpo=39916

   (20) https://bugs.python.org/issue?@action=redirect&bpo=39850

   (21) https://bugs.python.org/issue?@action=redirect&bpo=36287

   (22) https://bugs.python.org/issue?@action=redirect&bpo=39889

   (23) https://bugs.python.org/issue?@action=redirect&bpo=39828

   (24) https://bugs.python.org/issue?@action=redirect&bpo=13487

   (25) https://bugs.python.org/issue?@action=redirect&bpo=39674

   (26) https://bugs.python.org/issue?@action=redirect&bpo=37330

   (27) https://bugs.python.org/issue?@action=redirect&bpo=28577

   (28) https://bugs.python.org/issue?@action=redirect&bpo=39826

   (29) https://bugs.python.org/issue?@action=redirect&bpo=39763

   (30) https://bugs.python.org/issue?@action=redirect&bpo=39794

   (31) https://bugs.python.org/issue?@action=redirect&bpo=36144

   (32) https://peps.python.org/pep-0584/

   (33) https://bugs.python.org/issue?@action=redirect&bpo=39517

   (34) https://bugs.python.org/issue?@action=redirect&bpo=39775

   (35) https://bugs.python.org/issue?@action=redirect&bpo=39678

   (36) https://bugs.python.org/issue?@action=redirect&bpo=39764

   (37) https://bugs.python.org/issue?@action=redirect&bpo=39769

   (38) https://bugs.python.org/issue?@action=redirect&bpo=36144

   (39) https://peps.python.org/pep-0584/

   (40) https://bugs.python.org/issue?@action=redirect&bpo=38691

   (41) https://bugs.python.org/issue?@action=redirect&bpo=39719

   (42) https://bugs.python.org/issue?@action=redirect&bpo=39667

   (43) https://bugs.python.org/issue?@action=redirect&bpo=39638

   (44) https://bugs.python.org/issue?@action=redirect&bpo=39639

   (45) https://bugs.python.org/issue?@action=redirect&bpo=39609

   (46) https://bugs.python.org/issue?@action=redirect&bpo=39548

   (47) https://bugs.python.org/issue?@action=redirect&bpo=39509

   (48) https://bugs.python.org/issue?@action=redirect&bpo=39507

   (49) https://bugs.python.org/issue?@action=redirect&bpo=39495

   (50) https://bugs.python.org/issue?@action=redirect&bpo=38971

   (51) https://bugs.python.org/issue?@action=redirect&bpo=38641

   (52) https://bugs.python.org/issue?@action=redirect&bpo=37534

   (53) https://bugs.python.org/issue?@action=redirect&bpo=34788

   (54) https://bugs.python.org/issue?@action=redirect&bpo=34822


File: python.info,  Node: Documentation<34>,  Next: Tests<37>,  Prev: Library<39>,  Up: Python 3 9 0 alpha 5

1.23.40.4 Documentation
.......................

   - bpo-39868(1): Updated the Language Reference for PEP 572(2).

   - bpo-13790(3): Change 'string' to 'specification' in format doc.

   - bpo-17422(4): The language reference no longer restricts default
     class namespaces to dicts only.

   - bpo-39530(5): Fix misleading documentation about mixed-type numeric
     comparisons.

   - bpo-39718(6): Update *note token: e3. documentation to reflect
     additions in Python 3.8

   - bpo-39677(7): Changed operand name of 'MAKE_FUNCTION' from 'argc'
     to 'flags' for module *note dis: 30.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39868

   (2) https://peps.python.org/pep-0572/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=13790

   (4) https://bugs.python.org/issue?@action=redirect&bpo=17422

   (5) https://bugs.python.org/issue?@action=redirect&bpo=39530

   (6) https://bugs.python.org/issue?@action=redirect&bpo=39718

   (7) https://bugs.python.org/issue?@action=redirect&bpo=39677


File: python.info,  Node: Tests<37>,  Next: Build<39>,  Prev: Documentation<34>,  Up: Python 3 9 0 alpha 5

1.23.40.5 Tests
...............

   - bpo-40019(1): test_gdb now skips tests if it detects that gdb
     failed to read debug information because the Python binary is
     optimized.

   - bpo-27807(2): ‘test_site.test_startup_imports()’ is now skipped if
     a path of *note sys.path: 37f. contains a ‘.pth’ file.

   - bpo-26067(3): Do not fail test_shutil test_chown test when uid or
     gid of user cannot be resolved to a name.

   - bpo-39855(4): test_subprocess.test_user() now skips the test on an
     user name if the user name doesn't exist.  For example, skip the
     test if the user "nobody" doesn't exist on Linux.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40019

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27807

   (3) https://bugs.python.org/issue?@action=redirect&bpo=26067

   (4) https://bugs.python.org/issue?@action=redirect&bpo=39855


File: python.info,  Node: Build<39>,  Next: Windows<35>,  Prev: Tests<37>,  Up: Python 3 9 0 alpha 5

1.23.40.6 Build
...............

   - bpo-39761(1): Fix build with DTrace but without additional DFLAGS.

   - bpo-39763(2): setup.py now uses a basic implementation of the *note
     subprocess: c1. module if the *note subprocess: c1. module is not
     available: before required C extension modules are built.

   - bpo-1294959(3): Add ‘--with-platlibdir’ option to the configure
     script: name of the platform-specific library directory, stored in
     the new *note sys.platlibdir: 8dc. attribute.  It is used to build
     the path of platform-specific extension modules and the path of the
     standard library.  It is equal to ‘"lib"’ on most platforms.  On
     Fedora and SuSE, it is equal to ‘"lib64"’ on 64-bit platforms.
     Patch by Jan Matějek, Matěj Cepl, Charalampos Stratakis and Victor
     Stinner.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39761

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39763

   (3) https://bugs.python.org/issue?@action=redirect&bpo=1294959


File: python.info,  Node: Windows<35>,  Next: macOS<30>,  Prev: Build<39>,  Up: Python 3 9 0 alpha 5

1.23.40.7 Windows
.................

   - bpo-39930(1): Ensures the required ‘vcruntime140.dll’ is included
     in install packages.

   - bpo-39847(2): Avoid hang when computer is hibernated whilst waiting
     for a mutex (for lock-related objects from *note threading: d6.)
     around 49-day uptime.

   - bpo-38597(3): ‘distutils’ will no longer statically link
     ‘vcruntime140.dll’ when a redistributable version is unavailable.
     All future releases of CPython will include a copy of this DLL to
     ensure distributed extensions can continue to load.

   - bpo-38380(4): Update Windows builds to use SQLite 3.31.1

   - bpo-39789(5): Update Windows release build machines to Visual
     Studio 2019 (MSVC 14.2).

   - bpo-34803(6): Package for nuget.org now includes repository
     reference and bundled icon image.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39930

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39847

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38597

   (4) https://bugs.python.org/issue?@action=redirect&bpo=38380

   (5) https://bugs.python.org/issue?@action=redirect&bpo=39789

   (6) https://bugs.python.org/issue?@action=redirect&bpo=34803


File: python.info,  Node: macOS<30>,  Next: IDLE<26>,  Prev: Windows<35>,  Up: Python 3 9 0 alpha 5

1.23.40.8 macOS
...............

   - bpo-38380(1): Update macOS builds to use SQLite 3.31.1

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38380


File: python.info,  Node: IDLE<26>,  Next: Tools/Demos<18>,  Prev: macOS<30>,  Up: Python 3 9 0 alpha 5

1.23.40.9 IDLE
..............

   - bpo-27115(1): For 'Go to Line', use a Query box subclass with IDLE
     standard behavior and improved error checking.

   - bpo-39885(2): Since clicking to get an IDLE context menu moves the
     cursor, any text selection should be and now is cleared.

   - bpo-39852(3): Edit "Go to line" now clears any selection,
     preventing accidental deletion.  It also updates Ln and Col on the
     status bar.

   - bpo-39781(4): Selecting code context lines no longer causes a jump.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27115

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39885

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39852

   (4) https://bugs.python.org/issue?@action=redirect&bpo=39781


File: python.info,  Node: Tools/Demos<18>,  Next: C API<38>,  Prev: IDLE<26>,  Up: Python 3 9 0 alpha 5

1.23.40.10 Tools/Demos
......................

   - bpo-36184(1): Port python-gdb.py to FreeBSD. python-gdb.py now
     checks for "take_gil" function name to check if a frame tries to
     acquire the GIL, instead of checking for "pthread_cond_timedwait"
     which is specific to Linux and can be a different condition than
     the GIL.

   - bpo-38080(2): Added support to fix ‘getproxies’ in the
     ‘lib2to3.fixes.fix_urllib’ module.  Patch by José Roberto Meza
     Cabrera.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36184

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38080


File: python.info,  Node: C API<38>,  Prev: Tools/Demos<18>,  Up: Python 3 9 0 alpha 5

1.23.40.11 C API
................

   - bpo-40024(1): Add *note PyModule_AddType(): 919. helper function:
     add a type to a module.  Patch by Donghee Na.

   - bpo-39946(2): Remove ‘_PyRuntime.getframe’ hook and remove
     ‘_PyThreadState_GetFrame’ macro which was an alias to
     ‘_PyRuntime.getframe’.  They were only exposed by the internal C
     API. Remove also ‘PyThreadFrameGetter’ type.

   - bpo-39947(3): Add *note PyThreadState_GetFrame(): 732. function:
     get the current frame of a Python thread state.

   - bpo-37207(4): Add _PyArg_NoKwnames helper function.  Patch by
     Donghee Na.

   - bpo-39947(5): Add *note PyThreadState_GetInterpreter(): 915.: get
     the interpreter of a Python thread state.

   - bpo-39947(6): Add *note PyInterpreterState_Get(): 378. function to
     the limited C API.

   - bpo-35370(7): If *note PySys_Audit(): 321. fails in *note
     PyEval_SetProfile(): 146b. or *note PyEval_SetTrace(): 146c, log
     the error as an unraisable exception.

   - bpo-39947(8): Move the static inline function flavor of
     Py_EnterRecursiveCall() and Py_LeaveRecursiveCall() to the internal
     C API: they access PyThreadState attributes.  The limited C API
     provides regular functions which hide implementation details.

   - bpo-39947(9): Py_TRASHCAN_BEGIN_CONDITION and Py_TRASHCAN_END macro
     no longer access PyThreadState attributes, but call new private
     _PyTrash_begin() and _PyTrash_end() functions which hide
     implementation details.

   - bpo-39884(10): *note PyDescr_NewMethod(): 1890. and *note
     PyCFunction_NewEx(): 1891. now include the method name in the
     SystemError "bad call flags" error message to ease debug.

   - bpo-39877(11): Deprecated ‘PyEval_InitThreads()’ and
     ‘PyEval_ThreadsInitialized()’.  Calling ‘PyEval_InitThreads()’ now
     does nothing.

   - bpo-38249(12): *note Py_UNREACHABLE: b5c. is now implemented with
     ‘__builtin_unreachable()’ and analogs in release mode.

   - bpo-38643(13): *note PyNumber_ToBase(): 16ef. now raises a *note
     SystemError: 51b. instead of crashing when called with invalid
     base.

   - bpo-39882(14): The *note Py_FatalError(): 927. function is replaced
     with a macro which logs automatically the name of the current
     function, unless the ‘Py_LIMITED_API’ macro is defined.

   - bpo-39824(15): Extension modules: *note m_traverse: 91e, *note
     m_clear: 91f. and *note m_free: 920. functions of *note
     PyModuleDef: 921. are no longer called if the module state was
     requested but is not allocated yet.  This is the case immediately
     after the module is created and before the module is executed
     (*note Py_mod_exec: 922. function).  More precisely, these
     functions are not called if *note m_size: 923. is greater than 0
     and the module state (as returned by *note PyModule_GetState():
     924.) is ‘NULL’.

     Extension modules without module state (‘m_size <= 0’) are not
     affected.

   - bpo-38913(16): Fixed segfault in ‘Py_BuildValue()’ called with a
     format containing "#" and undefined PY_SSIZE_T_CLEAN whwn an
     exception is set.

   - bpo-38500(17): Add a private API to get and set the frame
     evaluation function: add *note
     _PyInterpreterState_GetEvalFrameFunc(): 1892. and *note
     _PyInterpreterState_SetEvalFrameFunc(): 1893. C functions.  The
     *note _PyFrameEvalFunction: 71a. function type now takes a 'tstate'
     parameter.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=40024

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39946

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39947

   (4) https://bugs.python.org/issue?@action=redirect&bpo=37207

   (5) https://bugs.python.org/issue?@action=redirect&bpo=39947

   (6) https://bugs.python.org/issue?@action=redirect&bpo=39947

   (7) https://bugs.python.org/issue?@action=redirect&bpo=35370

   (8) https://bugs.python.org/issue?@action=redirect&bpo=39947

   (9) https://bugs.python.org/issue?@action=redirect&bpo=39947

   (10) https://bugs.python.org/issue?@action=redirect&bpo=39884

   (11) https://bugs.python.org/issue?@action=redirect&bpo=39877

   (12) https://bugs.python.org/issue?@action=redirect&bpo=38249

   (13) https://bugs.python.org/issue?@action=redirect&bpo=38643

   (14) https://bugs.python.org/issue?@action=redirect&bpo=39882

   (15) https://bugs.python.org/issue?@action=redirect&bpo=39824

   (16) https://bugs.python.org/issue?@action=redirect&bpo=38913

   (17) https://bugs.python.org/issue?@action=redirect&bpo=38500


File: python.info,  Node: Python 3 9 0 alpha 4,  Next: Python 3 9 0 alpha 3,  Prev: Python 3 9 0 alpha 5,  Up: Changelog（更動日誌）

1.23.41 Python 3.9.0 alpha 4
----------------------------

'Release date: 2020-02-25'

* Menu:

* Security: Security<27>.
* Core and Builtins: Core and Builtins<41>.
* Library: Library<40>.
* Documentation: Documentation<35>.
* Tests: Tests<38>.
* Build: Build<40>.
* Windows: Windows<36>.
* IDLE: IDLE<27>.
* C API: C API<39>.


File: python.info,  Node: Security<27>,  Next: Core and Builtins<41>,  Up: Python 3 9 0 alpha 4

1.23.41.1 Security
..................

   - bpo-39184(1): Add audit events to functions in ‘fcntl’, ‘msvcrt’,
     ‘os’, ‘resource’, ‘shutil’, ‘signal’ and ‘syslog’.

   - bpo-39401(2): Avoid unsafe DLL load at startup on Windows 7 and
     earlier.

   - bpo-39184(3): Add audit events to command execution functions in os
     and pty modules.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39184

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39401

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39184


File: python.info,  Node: Core and Builtins<41>,  Next: Library<40>,  Prev: Security<27>,  Up: Python 3 9 0 alpha 4

1.23.41.2 Core and Builtins
...........................

   - bpo-39382(1): Fix a use-after-free in the single inheritance path
     of ‘issubclass()’, when the ‘__bases__’ of an object has a single
     reference, and so does its first item.  Patch by Yonatan
     Goldschmidt.

   - bpo-39573(2): Update clinic tool to use *note Py_IS_TYPE(): 171a.
     Patch by Donghee Na.

   - bpo-39619(3): Enable use of *note os.chroot(): 1897. on HP-UX
     systems.

   - bpo-39573(4): Add *note Py_IS_TYPE(): 171a. static inline function
     to check whether the object 'o' type is 'type'.

   - bpo-39606(5): Fix regression caused by fix for bpo-39386(6), that
     prevented calling ‘aclose’ on an async generator that had already
     been closed or exhausted.

   - bpo-39579(7): Change the ending column offset of ‘Attribute’ nodes
     constructed in ‘ast_for_dotted_name’ to point at the end of the
     current node and not at the end of the last ‘NAME’ node.

   - bpo-1635741(8): Port _crypt extension module to multiphase
     initialization ( PEP 489(9)).

   - bpo-1635741(10): Port _contextvars extension module to multiphase
     initialization ( PEP 489(11)).

   - bpo-39510(12): Fix segfault in ‘readinto()’ method on closed
     BufferedReader.

   - bpo-39502(13): Fix *note time.localtime(): 1467. on 64-bit AIX to
     support years before 1902 and after 2038.  Patch by M Felt.

   - bpo-39492(14): Fix a reference cycle in the C Pickler that was
     preventing the garbage collection of deleted, pickled objects.

   - bpo-39453(15): Fixed a possible crash in ‘list.__contains__()’ when
     a list is changed during comparing items.  Patch by Donghee Na.

   - bpo-39434(16): *note floor division: 8e8. of float operation now
     has a better performance.  Also the message of *note
     ZeroDivisionError: 8e9. for this operation is updated.  Patch by
     Donghee Na.

   - bpo-1635741(17): Port _codecs extension module to multiphase
     initialization ( PEP 489(18)).

   - bpo-1635741(19): Port _bz2 extension module to multiphase
     initialization ( PEP 489(20)).

   - bpo-1635741(21): Port _abc extension module to multiphase
     initialization ( PEP 489(22)).

   - bpo-39320(23): Replace two complex bytecodes for building dicts
     with two simpler ones.  The new bytecodes ‘DICT_MERGE’ and
     ‘DICT_UPDATE’ have been added The old bytecodes ‘BUILD_MAP_UNPACK’
     and ‘BUILD_MAP_UNPACK_WITH_CALL’ have been removed.

   - bpo-39219(24): Syntax errors raised in the tokenizer now always set
     correct "text" and "offset" attributes.

   - bpo-36051(25): Drop the GIL during large ‘bytes.join’ operations.
     Patch by Bruce Merry.

   - bpo-38960(26): Fix DTrace build issues on FreeBSD. Patch by David
     Carlier.

   - bpo-37207(27): Speed up calls to ‘range()’ by about 30%, by using
     the PEP 590 ‘vectorcall’ calling convention.  Patch by Mark
     Shannon.

   - bpo-36144(28): *note dict: 23b. (and *note collections.UserDict:
     1898.) objects now support PEP 584's merge (‘|’) and update (‘|=’)
     operators.  Patch by Brandt Bucher.

   - bpo-32856(29): Optimized the idiom for assignment a temporary
     variable in comprehensions.  Now ‘for y in [expr]’ in
     comprehensions is as fast as a simple assignment ‘y = expr’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39382

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39573

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39619

   (4) https://bugs.python.org/issue?@action=redirect&bpo=39573

   (5) https://bugs.python.org/issue?@action=redirect&bpo=39606

   (6) https://bugs.python.org/issue?@action=redirect&bpo=39386

   (7) https://bugs.python.org/issue?@action=redirect&bpo=39579

   (8) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (9) https://peps.python.org/pep-0489/

   (10) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (11) https://peps.python.org/pep-0489/

   (12) https://bugs.python.org/issue?@action=redirect&bpo=39510

   (13) https://bugs.python.org/issue?@action=redirect&bpo=39502

   (14) https://bugs.python.org/issue?@action=redirect&bpo=39492

   (15) https://bugs.python.org/issue?@action=redirect&bpo=39453

   (16) https://bugs.python.org/issue?@action=redirect&bpo=39434

   (17) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (18) https://peps.python.org/pep-0489/

   (19) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (20) https://peps.python.org/pep-0489/

   (21) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (22) https://peps.python.org/pep-0489/

   (23) https://bugs.python.org/issue?@action=redirect&bpo=39320

   (24) https://bugs.python.org/issue?@action=redirect&bpo=39219

   (25) https://bugs.python.org/issue?@action=redirect&bpo=36051

   (26) https://bugs.python.org/issue?@action=redirect&bpo=38960

   (27) https://bugs.python.org/issue?@action=redirect&bpo=37207

   (28) https://bugs.python.org/issue?@action=redirect&bpo=36144

   (29) https://bugs.python.org/issue?@action=redirect&bpo=32856


File: python.info,  Node: Library<40>,  Next: Documentation<35>,  Prev: Core and Builtins<41>,  Up: Python 3 9 0 alpha 4

1.23.41.3 Library
.................

   - bpo-30566(1): Fix *note IndexError: 14a3. when trying to decode an
     invalid string with punycode codec.

   - bpo-39649(2): Remove obsolete check for ‘__args__’ in
     ‘bdb.Bdb.format_stack_entry’.

   - bpo-39648(3): Expanded *note math.gcd(): 8b5. and *note math.lcm():
     8b6. to handle multiple arguments.

   - bpo-39681(4): Fix a regression where the C pickle module wouldn't
     allow unpickling from a file-like object that doesn't expose a
     readinto() method.

   - bpo-35950(5): Raise *note io.UnsupportedOperation: 189a. in
     ‘io.BufferedReader.truncate()’ when it is called on a read-only
     *note io.BufferedReader: 11a6. instance.

   - bpo-39479(6): Add *note math.lcm(): 8b6. function: least common
     multiple.

   - bpo-39674(7): Revert "Do not expose abstract collection classes in
     the collections module" change (bpo-25988(8)).  Aliases to ABC like
     collections.Mapping are kept in Python 3.9 to ease transition from
     Python 2.7, but will be removed in Python 3.10.

   - bpo-39104(9): Fix hanging ProcessPoolExcutor on
     ‘shutdown(wait=False)’ when a task has failed pickling.

   - bpo-39627(10): Fixed TypedDict totality check for inherited keys.

   - bpo-39474(11): Fixed starting position of AST for expressions like
     ‘(a)(b)’, ‘(a)[b]’ and ‘(a).b’.

   - bpo-21016(12): The *note pydoc: a3. and *note trace: e6. modules
     now use the *note sysconfig: c5. module to get the path to the
     Python standard library, to support uncommon installation path like
     ‘/usr/lib64/python3.9/’ on Fedora.  Patch by Jan Matějek.

   - bpo-39590(13): Collections.deque now holds strong references during
     deque.__contains__ and deque.count, fixing crashes.

   - bpo-39586(14): The distutils ‘bdist_msi’ command is deprecated in
     Python 3.9, use ‘bdist_wheel’ (wheel packages) instead.

   - bpo-39595(15): Improved performance of zipfile.Path for files with
     a large number of entries.  Also improved performance and fixed
     minor issue as published with importlib_metadata 1.5(16).

   - bpo-39350(17): Fix regression in *note fractions.Fraction: 1c7. if
     the numerator and/or the denominator is an *note int: 23c.
     subclass.  The *note math.gcd(): 8b5. function is now used to
     normalize the 'numerator' and 'denominator'.  *note math.gcd():
     8b5. always return a *note int: 23c. type.  Previously, the GCD
     type depended on 'numerator' and 'denominator'.

   - bpo-39567(18): Added audit for *note os.walk(): 451, *note
     os.fwalk(): aff, *note pathlib.Path.glob(): 212. and *note
     pathlib.Path.rglob(): 213.

   - bpo-39559(19): Remove unused, undocumented argument ‘getters’ from
     *note uuid.getnode(): b4e.

   - bpo-38149(20): *note sys.audit(): 1873. is now called only once per
     call of *note glob.glob(): 280. and *note glob.iglob(): 7ab.

   - bpo-39546(21): Fix a regression in *note ArgumentParser: 4de. where
     ‘allow_abbrev=False’ was ignored for long options that used a
     prefix character other than "-".

   - bpo-39450(22): Striped whitespace from docstring before returning
     it from ‘unittest.case.shortDescription()’.

   - bpo-12915(23): A new function ‘resolve_name’ has been added to the
     ‘pkgutil’ module.  This resolves a string of the form ‘'a.b.c.d'’
     or ‘'a.b:c.d'’ to an object.  In the example, ‘a.b’ is a
     package/module and ‘c.d’ is an object within that package/module
     reached via recursive attribute access.

   - bpo-39353(24): The *note binascii.crc_hqx(): 6d8. function is no
     longer deprecated.

   - bpo-39493(25): Mark ‘typing.IO.closed’ as a property

   - bpo-39491(26): Add *note typing.Annotated: 8e1. and
     ‘include_extras’ parameter to *note typing.get_type_hints(): 657.
     as part of PEP 593(27).  Patch by Till Varoquaux, documentation by
     Till Varoquaux and Konstantin Kashin.

   - bpo-39485(28): Fix a bug in *note unittest.mock.create_autospec():
     14fb. that would complain about the wrong number of arguments for
     custom descriptors defined in an extension module returning
     functions.

   - bpo-38932(29): Mock fully resets child objects on reset_mock().
     Patch by Vegard Stikbakke

   - bpo-39082(30): Allow AsyncMock to correctly patch static/class
     methods

   - bpo-39432(31): Implement PEP-489 algorithm for non-ascii
     "PyInit_..."  symbol names in distutils to make it export the
     correct init symbol also on Windows.

   - bpo-18819(32): Omit ‘devmajor’ and ‘devminor’ fields for non-device
     files in *note tarfile: c8. archives, enabling bit-for-bit
     compatibility with GNU ‘tar(1)’.

   - bpo-39349(33): Added a new 'cancel_futures' parameter to *note
     concurrent.futures.Executor.shutdown(): 892. that cancels all
     pending futures which have not started running, instead of waiting
     for them to complete before shutting down the executor.

   - bpo-39274(34): ‘bool(fraction.Fraction)’ now returns a boolean even
     if (numerator != 0) does not return a boolean (ex: numpy number).

   - bpo-34793(35): Remove support for ‘with (await asyncio.lock):’ and
     ‘with (yield from asyncio.lock):’.  The same is correct for
     ‘asyncio.Condition’ and ‘asyncio.Semaphore’.

   - bpo-25597(36): Ensure, if ‘wraps’ is supplied to *note
     unittest.mock.MagicMock: e33, it is used to calculate return values
     for the magic methods instead of using the default return values.
     Patch by Karthikeyan Singaravelan.

   - bpo-36350(37): ‘inspect.Signature.parameters’ and
     ‘inspect.BoundArguments.arguments’ are now dicts instead of
     OrderedDicts.  Patch contributed by Rémi Lapeyre.

   - bpo-35727(38): Fix sys.exit() and sys.exit(None) exit code
     propagation when used in multiprocessing.Process.

   - bpo-32173(39): * Add ‘lazycache’ function to ‘__all__’.  * Use
     ‘dict.clear’ to clear the cache.  * Refactoring ‘getline’ function
     and ‘checkcache’ function.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30566

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39649

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39648

   (4) https://bugs.python.org/issue?@action=redirect&bpo=39681

   (5) https://bugs.python.org/issue?@action=redirect&bpo=35950

   (6) https://bugs.python.org/issue?@action=redirect&bpo=39479

   (7) https://bugs.python.org/issue?@action=redirect&bpo=39674

   (8) https://bugs.python.org/issue?@action=redirect&bpo=25988

   (9) https://bugs.python.org/issue?@action=redirect&bpo=39104

   (10) https://bugs.python.org/issue?@action=redirect&bpo=39627

   (11) https://bugs.python.org/issue?@action=redirect&bpo=39474

   (12) https://bugs.python.org/issue?@action=redirect&bpo=21016

   (13) https://bugs.python.org/issue?@action=redirect&bpo=39590

   (14) https://bugs.python.org/issue?@action=redirect&bpo=39586

   (15) https://bugs.python.org/issue?@action=redirect&bpo=39595

   (16) 
https://importlib-metadata.readthedocs.io/en/latest/history.html#v1-5-0

   (17) https://bugs.python.org/issue?@action=redirect&bpo=39350

   (18) https://bugs.python.org/issue?@action=redirect&bpo=39567

   (19) https://bugs.python.org/issue?@action=redirect&bpo=39559

   (20) https://bugs.python.org/issue?@action=redirect&bpo=38149

   (21) https://bugs.python.org/issue?@action=redirect&bpo=39546

   (22) https://bugs.python.org/issue?@action=redirect&bpo=39450

   (23) https://bugs.python.org/issue?@action=redirect&bpo=12915

   (24) https://bugs.python.org/issue?@action=redirect&bpo=39353

   (25) https://bugs.python.org/issue?@action=redirect&bpo=39493

   (26) https://bugs.python.org/issue?@action=redirect&bpo=39491

   (27) https://peps.python.org/pep-0593/

   (28) https://bugs.python.org/issue?@action=redirect&bpo=39485

   (29) https://bugs.python.org/issue?@action=redirect&bpo=38932

   (30) https://bugs.python.org/issue?@action=redirect&bpo=39082

   (31) https://bugs.python.org/issue?@action=redirect&bpo=39432

   (32) https://bugs.python.org/issue?@action=redirect&bpo=18819

   (33) https://bugs.python.org/issue?@action=redirect&bpo=39349

   (34) https://bugs.python.org/issue?@action=redirect&bpo=39274

   (35) https://bugs.python.org/issue?@action=redirect&bpo=34793

   (36) https://bugs.python.org/issue?@action=redirect&bpo=25597

   (37) https://bugs.python.org/issue?@action=redirect&bpo=36350

   (38) https://bugs.python.org/issue?@action=redirect&bpo=35727

   (39) https://bugs.python.org/issue?@action=redirect&bpo=32173


File: python.info,  Node: Documentation<35>,  Next: Tests<38>,  Prev: Library<40>,  Up: Python 3 9 0 alpha 4

1.23.41.4 Documentation
.......................

   - bpo-17422(1): The language reference now specifies restrictions on
     class namespaces.  Adapted from a patch by Ethan Furman.

   - bpo-39572(2): Updated documentation of ‘total’ flag of ‘TypedDict’.

   - bpo-39654(3): In pyclbr doc, update 'class' to 'module' where
     appropriate and add readmodule comment.  Patch by Hakan Çelik.

   - bpo-39153(4): Clarify refcounting semantics for the following
     functions: - PyObject_SetItem - PyMapping_SetItemString -
     PyDict_SetItem - PyDict_SetItemString

   - bpo-39392(5): Explain that when filling with turtle, overlap
     regions may be left unfilled.

   - bpo-39369(6): Update mmap readline method description.  The fact
     that the readline method does update the file position should not
     be ignored since this might give the impression for the programmer
     that it doesn't update it.

   - bpo-9056(7): Include subsection in TOC for PDF version of docs.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=17422

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39572

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39654

   (4) https://bugs.python.org/issue?@action=redirect&bpo=39153

   (5) https://bugs.python.org/issue?@action=redirect&bpo=39392

   (6) https://bugs.python.org/issue?@action=redirect&bpo=39369

   (7) https://bugs.python.org/issue?@action=redirect&bpo=9056


File: python.info,  Node: Tests<38>,  Next: Build<40>,  Prev: Documentation<35>,  Up: Python 3 9 0 alpha 4

1.23.41.5 Tests
...............

   - bpo-38325(1): Skip tests on non-BMP characters of
     test_winconsoleio.

   - bpo-39502(2): Skip test_zipfile.test_add_file_after_2107() if *note
     time.localtime(): 1467. fails with *note OverflowError: 825.  It is
     the case on AIX 6.1 for example.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38325

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39502


File: python.info,  Node: Build<40>,  Next: Windows<36>,  Prev: Tests<38>,  Up: Python 3 9 0 alpha 4

1.23.41.6 Build
...............

   - bpo-39489(1): Remove ‘COUNT_ALLOCS’ special build.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39489


File: python.info,  Node: Windows<36>,  Next: IDLE<27>,  Prev: Build<40>,  Up: Python 3 9 0 alpha 4

1.23.41.7 Windows
.................

   - bpo-39553(1): Delete unused code related to SxS manifests.

   - bpo-39439(2): Honor the Python path when a virtualenv is active on
     Windows.

   - bpo-39393(3): Improve the error message when attempting to load a
     DLL with unresolved dependencies.

   - bpo-38883(4): *note home(): de9. and *note expanduser(): de8. on
     Windows now prefer ‘USERPROFILE’ and no longer use ‘HOME’, which is
     not normally set for regular user accounts.  This makes them again
     behave like *note os.path.expanduser(): 9b8, which was changed to
     ignore ‘HOME’ in 3.8, see bpo-36264(5).

   - bpo-39185(6): The build.bat script has additional options for
     very-quiet output (-q) and very-verbose output (-vv)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39553

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39439

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39393

   (4) https://bugs.python.org/issue?@action=redirect&bpo=38883

   (5) https://bugs.python.org/issue?@action=redirect&bpo=36264

   (6) https://bugs.python.org/issue?@action=redirect&bpo=39185


File: python.info,  Node: IDLE<27>,  Next: C API<39>,  Prev: Windows<36>,  Up: Python 3 9 0 alpha 4

1.23.41.8 IDLE
..............

   - bpo-39663(1): Add tests for pyparse find_good_parse_start().

   - bpo-39600(2): In the font configuration window, remove duplicated
     font names.

   - bpo-30780(3): Add remaining configdialog tests for buttons and
     highlights and keys tabs.

   - bpo-39388(4): IDLE Settings Cancel button now cancels pending
     changes

   - bpo-38792(5): Close an IDLE shell calltip if a *note
     KeyboardInterrupt: 975. or shell restart occurs.  Patch by Zackery
     Spytz.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39663

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39600

   (3) https://bugs.python.org/issue?@action=redirect&bpo=30780

   (4) https://bugs.python.org/issue?@action=redirect&bpo=39388

   (5) https://bugs.python.org/issue?@action=redirect&bpo=38792


File: python.info,  Node: C API<39>,  Prev: IDLE<27>,  Up: Python 3 9 0 alpha 4

1.23.41.9 C API
...............

   - bpo-35081(1): Move the ‘bytes_methods.h’ header file to the
     internal C API as ‘pycore_bytes_methods.h’: it only contains
     private symbols (prefixed by ‘_Py’), except of the
     ‘PyDoc_STRVAR_shared()’ macro.

   - bpo-35081(2): Move the ‘dtoa.h’ header file to the internal C API
     as ‘pycore_dtoa.h’: it only contains private functions (prefixed by
     ‘_Py’).  The *note math: 81. and *note cmath: 11. modules must now
     be compiled with the ‘Py_BUILD_CORE’ macro defined.

   - bpo-39573(3): Add *note Py_SET_SIZE(): 727. function to set the
     size of an object.

   - bpo-39500(4): *note PyUnicode_IsIdentifier(): 18a1. does not call
     *note Py_FatalError(): 927. anymore if the string is not ready.

   - bpo-39573(5): Add *note Py_SET_TYPE(): 725. function to set the
     type of an object.

   - bpo-39573(6): Add a *note Py_SET_REFCNT(): 84f. function to set the
     reference counter of an object.

   - bpo-39542(7): Convert *note PyType_HasFeature(): 1855, *note
     PyType_Check(): 18a2. and *note PyType_CheckExact(): 18a3. macros
     to static inline functions.

   - bpo-39542(8): In the limited C API, ‘PyObject_INIT()’ and
     ‘PyObject_INIT_VAR()’ are now defined as aliases to *note
     PyObject_Init(): a0d. and *note PyObject_InitVar(): 1857. to make
     their implementation opaque.  It avoids to leak implementation
     details in the limited C API. Exclude the following functions from
     the limited C API: ‘_Py_NewReference()’, ‘_Py_ForgetReference()’,
     ‘_PyTraceMalloc_NewReference()’ and ‘_Py_GetRefTotal()’.

   - bpo-39542(9): Exclude trashcan mechanism from the limited C API: it
     requires access to PyTypeObject and PyThreadState structure fields,
     whereas these structures are opaque in the limited C API.

   - bpo-39511(10): The *note PyThreadState_Clear(): 1515. function now
     calls the ‘PyThreadState.on_delete’ callback.  Previously, that
     happened in *note PyThreadState_Delete(): 18a4.

   - bpo-38076(11): Fix to clear the interpreter state only after
     clearing module globals to guarantee module state access from C
     Extensions during runtime destruction

   - bpo-39245(12): The Vectorcall API (PEP 590) was made public, adding
     the functions ‘PyObject_Vectorcall’, ‘PyObject_VectorcallMethod’,
     ‘PyVectorcall_Function’, ‘PyObject_CallOneArg’,
     ‘PyObject_CallMethodNoArgs’, ‘PyObject_CallMethodOneArg’,
     ‘PyObject_FastCallDict’, and the flag ‘Py_TPFLAGS_HAVE_VECTORCALL’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35081

   (2) https://bugs.python.org/issue?@action=redirect&bpo=35081

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39573

   (4) https://bugs.python.org/issue?@action=redirect&bpo=39500

   (5) https://bugs.python.org/issue?@action=redirect&bpo=39573

   (6) https://bugs.python.org/issue?@action=redirect&bpo=39573

   (7) https://bugs.python.org/issue?@action=redirect&bpo=39542

   (8) https://bugs.python.org/issue?@action=redirect&bpo=39542

   (9) https://bugs.python.org/issue?@action=redirect&bpo=39542

   (10) https://bugs.python.org/issue?@action=redirect&bpo=39511

   (11) https://bugs.python.org/issue?@action=redirect&bpo=38076

   (12) https://bugs.python.org/issue?@action=redirect&bpo=39245


File: python.info,  Node: Python 3 9 0 alpha 3,  Next: Python 3 9 0 alpha 2,  Prev: Python 3 9 0 alpha 4,  Up: Changelog（更動日誌）

1.23.42 Python 3.9.0 alpha 3
----------------------------

'Release date: 2020-01-24'

* Menu:

* Core and Builtins: Core and Builtins<42>.
* Library: Library<41>.
* Documentation: Documentation<36>.
* Build: Build<41>.
* IDLE: IDLE<28>.
* C API: C API<40>.


File: python.info,  Node: Core and Builtins<42>,  Next: Library<41>,  Up: Python 3 9 0 alpha 3

1.23.42.1 Core and Builtins
...........................

   - bpo-39427(1): Document all possibilities for the ‘-X’ options in
     the command line help section.  Patch by Pablo Galindo.

   - bpo-39421(2): Fix possible crashes when operating with the
     functions in the *note heapq: 5f. module and custom comparison
     operators.

   - bpo-39386(3): Prevent double awaiting of async iterator.

   - bpo-17005(4): Add ‘functools.TopologicalSorter’ to the *note
     functools: 55. module to offers functionality to perform
     topological sorting of graphs.  Patch by Pablo Galindo, Tim Peters
     and Larry Hastings.

   - bpo-39320(5): Replace four complex bytecodes for building sequences
     with three simpler ones.

     The following four bytecodes have been removed:

        * BUILD_LIST_UNPACK

        * BUILD_TUPLE_UNPACK

        * BUILD_SET_UNPACK

        * BUILD_TUPLE_UNPACK_WITH_CALL

     The following three bytecodes have been added:

        * LIST_TO_TUPLE

        * LIST_EXTEND

        * SET_UPDATE

   - bpo-39336(6): Import loaders which publish immutable module objects
     can now publish immutable packages in addition to individual
     modules.

   - bpo-39322(7): Added a new function *note gc.is_finalized(): 8a2. to
     check if an object has been finalized by the garbage collector.
     Patch by Pablo Galindo.

   - bpo-39048(8): Improve the displayed error message when incorrect
     types are passed to ‘async with’ statements by looking up the
     ‘__aenter__()’ special method before the ‘__aexit__()’ special
     method when entering an asynchronous context manager.  Patch by
     Géry Ogam.

   - bpo-39235(9): Fix AST end location for lone generator expression in
     function call, e.g.  f(i for i in a).

   - bpo-39209(10): Correctly handle multi-line tokens in interactive
     mode.  Patch by Pablo Galindo.

   - bpo-1635741(11): Port _json extension module to multiphase
     initialization ( PEP 489(12)).

   - bpo-39216(13): Fix constant folding optimization for positional
     only arguments - by Anthony Sottile.

   - bpo-39215(14): Fix ‘SystemError’ when nested function has
     annotation on positional-only argument - by Anthony Sottile.

   - bpo-39200(15): Correct the error message when calling the *note
     min(): eac. or *note max(): ead. with no arguments.  Patch by
     Donghee Na.

   - bpo-39200(16): Correct the error message when trying to construct
     *note range: 8e7. objects with no arguments.  Patch by Pablo
     Galindo.

   - bpo-39166(17): Fix incorrect line execution reporting in trace
     functions when tracing the last iteration of asynchronous for
     loops.  Patch by Pablo Galindo.

   - bpo-39114(18): Fix incorrect line execution reporting in trace
     functions when tracing exception handlers with name binding.  Patch
     by Pablo Galindo.

   - bpo-39156(19): Split the COMPARE_OP bytecode instruction into four
     distinct instructions.

        * COMPARE_OP for rich comparisons

        * IS_OP for 'is' and 'is not' tests

        * CONTAINS_OP for 'in' and 'is not' tests

        * JUMP_IF_NOT_EXC_MATCH for checking exceptions in 'try-except'
          statements.

     This improves the clarity of the interpreter and should provide a
     modest speedup.

   - bpo-38588(20): Fix possible crashes in dict and list when calling
     *note PyObject_RichCompareBool(): 18a7.

   - bpo-13601(21): By default, ‘sys.stderr’ is line-buffered now, even
     if ‘stderr’ is redirected to a file.  You can still make
     ‘sys.stderr’ unbuffered by passing the *note -u: 18a8. command-line
     option or setting the *note PYTHONUNBUFFERED: 18a9. environment
     variable.

     (Contributed by Jendrik Seipp in bpo-13601(22).)

   - bpo-38610(23): Fix possible crashes in several list methods by
     holding strong references to list elements when calling *note
     PyObject_RichCompareBool(): 18a7.

   - bpo-32021(24): Include brotli .br encoding in mimetypes
     encodings_map

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39427

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39421

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39386

   (4) https://bugs.python.org/issue?@action=redirect&bpo=17005

   (5) https://bugs.python.org/issue?@action=redirect&bpo=39320

   (6) https://bugs.python.org/issue?@action=redirect&bpo=39336

   (7) https://bugs.python.org/issue?@action=redirect&bpo=39322

   (8) https://bugs.python.org/issue?@action=redirect&bpo=39048

   (9) https://bugs.python.org/issue?@action=redirect&bpo=39235

   (10) https://bugs.python.org/issue?@action=redirect&bpo=39209

   (11) https://bugs.python.org/issue?@action=redirect&bpo=1635741

   (12) https://peps.python.org/pep-0489/

   (13) https://bugs.python.org/issue?@action=redirect&bpo=39216

   (14) https://bugs.python.org/issue?@action=redirect&bpo=39215

   (15) https://bugs.python.org/issue?@action=redirect&bpo=39200

   (16) https://bugs.python.org/issue?@action=redirect&bpo=39200

   (17) https://bugs.python.org/issue?@action=redirect&bpo=39166

   (18) https://bugs.python.org/issue?@action=redirect&bpo=39114

   (19) https://bugs.python.org/issue?@action=redirect&bpo=39156

   (20) https://bugs.python.org/issue?@action=redirect&bpo=38588

   (21) https://bugs.python.org/issue?@action=redirect&bpo=13601

   (22) https://bugs.python.org/issue?@action=redirect&bpo=13601

   (23) https://bugs.python.org/issue?@action=redirect&bpo=38610

   (24) https://bugs.python.org/issue?@action=redirect&bpo=32021


File: python.info,  Node: Library<41>,  Next: Documentation<36>,  Prev: Core and Builtins<42>,  Up: Python 3 9 0 alpha 3

1.23.42.2 Library
.................

   - bpo-39430(1): Fixed race condition in lazy imports in *note
     tarfile: c8.

   - bpo-39413(2): The *note os.unsetenv(): 8c0. function is now also
     available on Windows.

   - bpo-39390(3): Fixed a regression with the ‘ignore’ callback of
     *note shutil.copytree(): 9cd.  The argument types are now ‘str’ and
     ‘List[str]’ again.

   - bpo-39395(4): The *note os.putenv(): 8c1. and *note os.unsetenv():
     8c0. functions are now always available.

   - bpo-39406(5): If ‘setenv()’ C function is available, *note
     os.putenv(): 8c1. is now implemented with ‘setenv()’ instead of
     ‘putenv()’, so Python doesn't have to handle the environment
     variable memory.

   - bpo-39396(6): Fix ‘math.nextafter(-0.0, +0.0)’ on AIX 7.1.

   - bpo-29435(7): Allow *note tarfile.is_tarfile(): 1749. to be used
     with file and file-like objects, like *note zipfile.is_zipfile():
     12be.  Patch by William Woodruff.

   - bpo-39377(8): Removed ‘encoding’ option from *note json.loads():
     8f9.  It has been deprecated since Python 3.1.

   - bpo-39389(9): Write accurate compression level metadata in *note
     gzip: 5d. archives, rather than always signaling maximum
     compression.

   - bpo-39366(10): The previously deprecated ‘xpath()’ and ‘xgtitle()’
     methods of ‘nntplib.NNTP’ have been removed.

   - bpo-39357(11): Remove the 'buffering' parameter of *note
     bz2.BZ2File: 80b.  Since Python 3.0, it was ignored and using it
     was emitting *note DeprecationWarning: 18b.  Pass an open file
     object, to control how the file is opened.  The 'compresslevel'
     parameter becomes keyword-only.

   - bpo-39353(12): Deprecate binhex4 and hexbin4 standards.  Deprecate
     the ‘binhex’ module and the following *note binascii: c. functions:
     ‘b2a_hqx()’, ‘a2b_hqx()’, ‘rlecode_hqx()’, ‘rledecode_hqx()’, *note
     crc_hqx(): 6d8.

   - bpo-39351(13): Remove ‘base64.encodestring()’ and
     ‘base64.decodestring()’, aliases deprecated since Python 3.1: use
     *note base64.encodebytes(): 8f7. and *note base64.decodebytes():
     8f8. instead.

   - bpo-39350(14): Remove ‘fractions.gcd()’ function, deprecated since
     Python 3.5 (bpo-22486(15)): use *note math.gcd(): 8b5. instead.

   - bpo-39329(16): *note LMTP: 8d3. constructor now has an optional
     'timeout' parameter.  Patch by Donghee Na.

   - bpo-39313(17): Add a new ‘exec_function’ option ('-exec-function'
     in the CLI) to ‘RefactoringTool’ for making ‘exec’ a function.
     Patch by Batuhan Taskaya.

   - bpo-39259(18): *note FTP_TLS: 8a0. and *note FTP_TLS: 8a0. now
     raise a *note ValueError: 1e7. if the given timeout for their
     constructor is zero to prevent the creation of a non-blocking
     socket.  Patch by Donghee Na.

   - bpo-39259(19): *note SMTP: 8d1. and *note SMTP_SSL: 8d2. now raise
     a *note ValueError: 1e7. if the given timeout for their constructor
     is zero to prevent the creation of a non-blocking socket.  Patch by
     Donghee Na.

   - bpo-39310(20): Add *note math.ulp(): 8b7.: return the value of the
     least significant bit of a float.

   - bpo-39297(21): Improved performance of importlib.metadata
     distribution discovery and resilients to inaccessible sys.path
     entries (importlib_metadata v1.4.0).

   - bpo-39259(22): ‘NNTP’ and ‘NNTP_SSL’ now raise a *note ValueError:
     1e7. if the given timeout for their constructor is zero to prevent
     the creation of a non-blocking socket.  Patch by Donghee Na.

   - bpo-38901(23): When you specify prompt='.'  or equivalently python
     -m venv -prompt .  ...  the basename of the current directory is
     used to set the created venv's prompt when it's activated.

   - bpo-39288(24): Add *note math.nextafter(): 440.: return the next
     floating-point value after 'x' towards 'y'.

   - bpo-39259(25): *note POP3: 8c9. and *note POP3_SSL: 8ca. now raise
     a *note ValueError: 1e7. if the given timeout for their constructor
     is zero to prevent the creation of a non-blocking socket.  Patch by
     Donghee Na.

   - bpo-39242(26): Updated the Gmane domain from news.gmane.org to
     news.gmane.io which is used for examples of ‘NNTP’ news reader
     server and nntplib tests.

   - bpo-35292(27): Proxy the ‘SimpleHTTPRequestHandler.guess_type’ to
     ‘mimetypes.guess_type’ so the ‘mimetypes.init’ is called lazily to
     avoid unnecessary costs when *note http.server: 68. module is
     imported.

   - bpo-39239(28): The *note select.epoll.unregister(): 8fe. method no
     longer ignores the *note EBADF: 8ff. error.

   - bpo-38907(29): In http.server script, restore binding to IPv4 on
     Windows.

   - bpo-39152(30): Fix ttk.Scale.configure([name]) to return
     configuration tuple for name or all options.  Giovanni Lombardo
     contributed part of the patch.

   - bpo-39198(31): If an exception were to be thrown in
     ‘Logger.isEnabledFor’ (say, by asyncio timeouts or stopit) , the
     ‘logging’ global lock may not be released appropriately, resulting
     in deadlock.  This change wraps that block of code with
     ‘try...finally’ to ensure the lock is released.

   - bpo-39191(32): Perform a check for running loop before starting a
     new task in ‘loop.run_until_complete()’ to fail fast; it prevents
     the side effect of new task spawning before exception raising.

   - bpo-38871(33): Correctly parenthesize filter-based statements that
     contain lambda expressions in ‘lib2to3’.  Patch by Donghee Na.

   - bpo-39142(34): A change was made to logging.config.dictConfig to
     avoid converting instances of named tuples to ConvertingTuple.
     It's assumed that named tuples are too specialised to be treated
     like ordinary tuples; if a user of named tuples requires
     ConvertingTuple functionality, they will have to implement that
     themselves in their named tuple class.

   - bpo-39158(35): ast.literal_eval() now supports empty sets.

   - bpo-39129(36): Fix import path for ‘asyncio.TimeoutError’

   - bpo-39057(37): ‘urllib.request.proxy_bypass_environment()’ now
     ignores leading dots and no longer ignores a trailing newline.

   - bpo-39056(38): Fixed handling invalid warning category in the -W
     option.  No longer import the re module if it is not needed.

   - bpo-39055(39): *note base64.b64decode(): 18ab. with ‘validate=True’
     raises now a binascii.Error if the input ends with a single ‘\n’.

   - bpo-21600(40): Fix ‘mock.patch.stopall()’ to stop active patches
     that were created with ‘mock.patch.dict()’.

   - bpo-39019(41): Implement dummy ‘__class_getitem__’ for *note
     tempfile.SpooledTemporaryFile: 639.

   - bpo-39019(42): Implement dummy ‘__class_getitem__’ for
     ‘subprocess.Popen’, ‘subprocess.CompletedProcess’

   - bpo-38914(43): Adjusted the wording of the warning issued by
     distutils' ‘check’ command when the ‘author’ and ‘maintainer’
     fields are supplied but no corresponding e-mail field
     (‘author_email’ or ‘maintainer_email’) is found.  The wording now
     reflects the fact that these fields are suggested, but not
     required.  Patch by Juergen Gmach.

   - bpo-38878(44): Fixed __subclasshook__ of *note os.PathLike: bf8. to
     return a correct result upon inheritance.  Patch by Bar Harel.

   - bpo-38615(45): *note IMAP4: 8a8. and *note IMAP4_SSL: 8a9. now have
     an optional 'timeout' parameter for their constructors.  Also, the
     *note open(): 8aa. method now has an optional 'timeout' parameter
     with this change.  The overridden methods of *note IMAP4_SSL: 8a9.
     and *note IMAP4_stream: 8ab. were applied to this change.  Patch by
     Donghee Na.

   - bpo-35182(46): Fixed ‘Popen.communicate()’ subsequent call crash
     when the child process has already closed any piped standard
     stream, but still continues to be running.  Patch by Andriy
     Maletsky.

   - bpo-38630(47): On Unix, *note subprocess.Popen.send_signal(): 134c.
     now polls the process status.  Polling reduces the risk of sending
     a signal to the wrong process if the process completed, the *note
     subprocess.Popen.returncode: 18ac. attribute is still ‘None’, and
     the pid has been reassigned (recycled) to a new different process.

   - bpo-38536(48): Removes trailing space in formatted currency with
     ‘international=True’ and a locale with symbol following value.
     E.g.  ‘locale.currency(12.34, international=True)’ returned ‘'12,34
     EUR '’ instead of ‘'12,34 EUR'’.

   - bpo-38473(49): Use signature from inner mock for autospecced
     methods attached with ‘unittest.mock.attach_mock()’.  Patch by
     Karthikeyan Singaravelan.

   - bpo-38361(50): Fixed an issue where ‘ident’ could include a leading
     path separator when *note syslog.openlog(): 4e4. was called without
     arguments.

   - bpo-38293(51): Add *note copy.copy(): 4d8. and *note
     copy.deepcopy(): b12. support to *note property(): 180. objects.

   - bpo-37958(52): Added the pstats.Stats.get_profile_dict() method to
     return the profile data as a StatsProfile instance.

   - bpo-28367(53): Termios magic constants for the following baud
     rates: - B500000 - B576000 - B921600 - B1000000 - B1152000 -
     B1500000 - B2000000 - B2500000 - B3000000 - B3500000 - B4000000
     Patch by Andrey Smirnov

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39430

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39413

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39390

   (4) https://bugs.python.org/issue?@action=redirect&bpo=39395

   (5) https://bugs.python.org/issue?@action=redirect&bpo=39406

   (6) https://bugs.python.org/issue?@action=redirect&bpo=39396

   (7) https://bugs.python.org/issue?@action=redirect&bpo=29435

   (8) https://bugs.python.org/issue?@action=redirect&bpo=39377

   (9) https://bugs.python.org/issue?@action=redirect&bpo=39389

   (10) https://bugs.python.org/issue?@action=redirect&bpo=39366

   (11) https://bugs.python.org/issue?@action=redirect&bpo=39357

   (12) https://bugs.python.org/issue?@action=redirect&bpo=39353

   (13) https://bugs.python.org/issue?@action=redirect&bpo=39351

   (14) https://bugs.python.org/issue?@action=redirect&bpo=39350

   (15) https://bugs.python.org/issue?@action=redirect&bpo=22486

   (16) https://bugs.python.org/issue?@action=redirect&bpo=39329

   (17) https://bugs.python.org/issue?@action=redirect&bpo=39313

   (18) https://bugs.python.org/issue?@action=redirect&bpo=39259

   (19) https://bugs.python.org/issue?@action=redirect&bpo=39259

   (20) https://bugs.python.org/issue?@action=redirect&bpo=39310

   (21) https://bugs.python.org/issue?@action=redirect&bpo=39297

   (22) https://bugs.python.org/issue?@action=redirect&bpo=39259

   (23) https://bugs.python.org/issue?@action=redirect&bpo=38901

   (24) https://bugs.python.org/issue?@action=redirect&bpo=39288

   (25) https://bugs.python.org/issue?@action=redirect&bpo=39259

   (26) https://bugs.python.org/issue?@action=redirect&bpo=39242

   (27) https://bugs.python.org/issue?@action=redirect&bpo=35292

   (28) https://bugs.python.org/issue?@action=redirect&bpo=39239

   (29) https://bugs.python.org/issue?@action=redirect&bpo=38907

   (30) https://bugs.python.org/issue?@action=redirect&bpo=39152

   (31) https://bugs.python.org/issue?@action=redirect&bpo=39198

   (32) https://bugs.python.org/issue?@action=redirect&bpo=39191

   (33) https://bugs.python.org/issue?@action=redirect&bpo=38871

   (34) https://bugs.python.org/issue?@action=redirect&bpo=39142

   (35) https://bugs.python.org/issue?@action=redirect&bpo=39158

   (36) https://bugs.python.org/issue?@action=redirect&bpo=39129

   (37) https://bugs.python.org/issue?@action=redirect&bpo=39057

   (38) https://bugs.python.org/issue?@action=redirect&bpo=39056

   (39) https://bugs.python.org/issue?@action=redirect&bpo=39055

   (40) https://bugs.python.org/issue?@action=redirect&bpo=21600

   (41) https://bugs.python.org/issue?@action=redirect&bpo=39019

   (42) https://bugs.python.org/issue?@action=redirect&bpo=39019

   (43) https://bugs.python.org/issue?@action=redirect&bpo=38914

   (44) https://bugs.python.org/issue?@action=redirect&bpo=38878

   (45) https://bugs.python.org/issue?@action=redirect&bpo=38615

   (46) https://bugs.python.org/issue?@action=redirect&bpo=35182

   (47) https://bugs.python.org/issue?@action=redirect&bpo=38630

   (48) https://bugs.python.org/issue?@action=redirect&bpo=38536

   (49) https://bugs.python.org/issue?@action=redirect&bpo=38473

   (50) https://bugs.python.org/issue?@action=redirect&bpo=38361

   (51) https://bugs.python.org/issue?@action=redirect&bpo=38293

   (52) https://bugs.python.org/issue?@action=redirect&bpo=37958

   (53) https://bugs.python.org/issue?@action=redirect&bpo=28367


File: python.info,  Node: Documentation<36>,  Next: Build<41>,  Prev: Library<41>,  Up: Python 3 9 0 alpha 3

1.23.42.3 Documentation
.......................

   - bpo-39381(1): Mention in docs that *note asyncio.get_event_loop():
     2a3. implicitly creates new event loop only if called from the main
     thread.

   - bpo-38918(2): Add an entry for ‘__module__’ in the "function" &
     "method" sections of the *note inspect: 72. docs' *note Types and
     members: 18ae. table.

   - bpo-3530(3): In the *note ast: 7. module documentation, fix a
     misleading ‘NodeTransformer’ example and add advice on when to use
     the ‘fix_missing_locations’ function.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39381

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38918

   (3) https://bugs.python.org/issue?@action=redirect&bpo=3530


File: python.info,  Node: Build<41>,  Next: IDLE<28>,  Prev: Documentation<36>,  Up: Python 3 9 0 alpha 3

1.23.42.4 Build
...............

   - bpo-39395(1): On non-Windows platforms, the ‘setenv()’ and
     ‘unsetenv()’ functions are now required to build Python.

   - bpo-39160(2): Updated the documentation in ‘./configure --help’ to
     show default values, reference documentation where required and add
     additional explanation where needed.

   - bpo-39144(3): The ctags and etags build targets both include
     Modules/_ctypes and Python standard library source files.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39395

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39160

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39144


File: python.info,  Node: IDLE<28>,  Next: C API<40>,  Prev: Build<41>,  Up: Python 3 9 0 alpha 3

1.23.42.5 IDLE
..............

   - bpo-39050(1): Make IDLE Settings dialog Help button work again.

   - bpo-34118(2): Tag memoryview, range, and tuple as classes, the same
     as list, etcetera, in the library manual built-in functions list.

   - bpo-32989(3): Add tests for editor newline_and_indent_event method.
     Remove dead code from pyparse find_good_parse_start method.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39050

   (2) https://bugs.python.org/issue?@action=redirect&bpo=34118

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32989


File: python.info,  Node: C API<40>,  Prev: IDLE<28>,  Up: Python 3 9 0 alpha 3

1.23.42.6 C API
...............

   - bpo-39372(1): Clean header files of interfaces defined but with no
     implementation.  The public API symbols being removed are:
     ‘_PyBytes_InsertThousandsGroupingLocale’,
     ‘_PyBytes_InsertThousandsGrouping’, ‘_Py_InitializeFromArgs’,
     ‘_Py_InitializeFromWideArgs’, ‘_PyFloat_Repr’, ‘_PyFloat_Digits’,
     ‘_PyFloat_DigitsInit’, ‘PyFrame_ExtendStack’,
     ‘_PyAIterWrapper_Type’, ‘PyNullImporter_Type’, ‘PyCmpWrapper_Type’,
     ‘PySortWrapper_Type’, ‘PyNoArgsFunction’.

   - bpo-39164(2): Add a private ‘_PyErr_GetExcInfo()’ function to
     retrieve exception information of the specified Python thread
     state.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39372

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39164


File: python.info,  Node: Python 3 9 0 alpha 2,  Next: Python 3 9 0 alpha 1,  Prev: Python 3 9 0 alpha 3,  Up: Changelog（更動日誌）

1.23.43 Python 3.9.0 alpha 2
----------------------------

'Release date: 2019-12-18'

* Menu:

* Security: Security<28>.
* Core and Builtins: Core and Builtins<43>.
* Library: Library<42>.
* Documentation: Documentation<37>.
* Tests: Tests<39>.
* Build: Build<42>.
* Windows: Windows<37>.
* macOS: macOS<31>.
* IDLE: IDLE<29>.
* C API: C API<41>.


File: python.info,  Node: Security<28>,  Next: Core and Builtins<43>,  Up: Python 3 9 0 alpha 2

1.23.43.1 Security
..................

   - bpo-38945(1): Newline characters have been escaped when performing
     uu encoding to prevent them from overflowing into to content
     section of the encoded file.  This prevents malicious or accidental
     modification of data during the decoding process.

   - bpo-37228(2): Due to significant security concerns, the
     'reuse_address' parameter of *note
     asyncio.loop.create_datagram_endpoint(): 6d7. is no longer
     supported.  This is because of the behavior of ‘SO_REUSEADDR’ in
     UDP. For more details, see the documentation for
     ‘loop.create_datagram_endpoint()’.  (Contributed by Kyle Stanley,
     Antoine Pitrou, and Yury Selivanov in bpo-37228(3).)

   - bpo-38804(4): Fixes a ReDoS vulnerability in *note http.cookiejar:
     66.  Patch by Ben Caller.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38945

   (2) https://bugs.python.org/issue?@action=redirect&bpo=37228

   (3) https://bugs.python.org/issue?@action=redirect&bpo=37228

   (4) https://bugs.python.org/issue?@action=redirect&bpo=38804


File: python.info,  Node: Core and Builtins<43>,  Next: Library<42>,  Prev: Security<28>,  Up: Python 3 9 0 alpha 2

1.23.43.2 Core and Builtins
...........................

   - bpo-39028(1): Slightly improve the speed of keyword argument
     parsing with many kwargs by strengthening the assumption that
     kwargs are interned strings.

   - bpo-39080(2): Fix the value of 'end_col_offset' for Starred
     Expression AST nodes when they are among the elements in the 'args'
     attribute of Call AST nodes.

   - bpo-39031(3): When parsing an "elif" node, lineno and col_offset of
     the node now point to the "elif" keyword and not to its condition,
     making it consistent with the "if" node.  Patch by Lysandros
     Nikolaou.

   - bpo-20443(4): In Python 3.9.0a1, sys.argv[0] was made an absolute
     path if a filename was specified on the command line.  Revert this
     change, since most users expect sys.argv to be unmodified.

   - bpo-39008(5): *note PySys_Audit(): 321. now requires ‘Py_ssize_t’
     to be used for size arguments in the format string, regardless of
     whether ‘PY_SSIZE_T_CLEAN’ was defined at include time.

   - bpo-38673(6): In REPL mode, don't switch to PS2 if the line starts
     with comment or whitespace.  Based on work by Batuhan Taşkaya.

   - bpo-38922(7): Calling ‘replace’ on a code object now raises the
     ‘code.__new__’ audit event.

   - bpo-38920(8): Add audit hooks for when *note sys.excepthook(): 7af.
     and *note sys.unraisablehook(): 1dc. are invoked.

   - bpo-38892(9): Improve documentation for audit events table and
     functions.

   - bpo-38852(10): Set the thread stack size to 8 Mb for debug builds
     on android platforms.

   - bpo-38858(11): Each Python subinterpreter now has its own "small
     integer singletons": numbers in [-5; 257] range.  It is no longer
     possible to change the number of small integers at build time by
     overriding ‘NSMALLNEGINTS’ and ‘NSMALLPOSINTS’ macros: macros
     should now be modified manually in ‘pycore_pystate.h’ header file.

   - bpo-36854(12): The garbage collector state becomes per interpreter
     (‘PyInterpreterState.gc’), rather than being global
     (‘_PyRuntimeState.gc’).

   - bpo-38835(13): The ‘PyFPE_START_PROTECT()’ and
     ‘PyFPE_END_PROTECT()’ macros are empty: they have been doing
     nothing for the last year, so stop using them.

   - bpo-38328(14): Sped up the creation time of constant *note list:
     5b6. and *note set: 57d. displays.  Patch by Brandt Bucher.

   - bpo-38707(15): ‘MainThread.native_id’ is now correctly reset in
     child processes spawned using *note multiprocessing.Process: afd,
     instead of retaining the parent's value.

   - bpo-38629(16): Added ‘__floor__’ and ‘__ceil__’ methods to float
     object.  Patch by Batuhan Taşkaya.

   - bpo-27145(17): int + int and int - int operators can now return
     small integer singletons.  Patch by hongweipeng.

   - bpo-38021(18): Provide a platform tag for AIX that is sufficient
     for PEP425 binary distribution identification.  Patch by Michael
     Felt.

   - bpo-35409(19): Ignore GeneratorExit exceptions when throwing an
     exception into the aclose coroutine of an asynchronous generator.

   - bpo-33387(20): Removed WITH_CLEANUP_START, WITH_CLEANUP_FINISH,
     BEGIN_FINALLY, END_FINALLY, CALL_FINALLY and POP_FINALLY bytecodes.
     Replaced with RERAISE and WITH_EXCEPT_START bytecodes.  The
     compiler now generates different code for exceptional and
     non-exceptional branches for 'with' and 'try-except' statements.
     For 'try-finally' statements the 'finally' block is replicated for
     each exit from the 'try' body.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39028

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39080

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39031

   (4) https://bugs.python.org/issue?@action=redirect&bpo=20443

   (5) https://bugs.python.org/issue?@action=redirect&bpo=39008

   (6) https://bugs.python.org/issue?@action=redirect&bpo=38673

   (7) https://bugs.python.org/issue?@action=redirect&bpo=38922

   (8) https://bugs.python.org/issue?@action=redirect&bpo=38920

   (9) https://bugs.python.org/issue?@action=redirect&bpo=38892

   (10) https://bugs.python.org/issue?@action=redirect&bpo=38852

   (11) https://bugs.python.org/issue?@action=redirect&bpo=38858

   (12) https://bugs.python.org/issue?@action=redirect&bpo=36854

   (13) https://bugs.python.org/issue?@action=redirect&bpo=38835

   (14) https://bugs.python.org/issue?@action=redirect&bpo=38328

   (15) https://bugs.python.org/issue?@action=redirect&bpo=38707

   (16) https://bugs.python.org/issue?@action=redirect&bpo=38629

   (17) https://bugs.python.org/issue?@action=redirect&bpo=27145

   (18) https://bugs.python.org/issue?@action=redirect&bpo=38021

   (19) https://bugs.python.org/issue?@action=redirect&bpo=35409

   (20) https://bugs.python.org/issue?@action=redirect&bpo=33387


File: python.info,  Node: Library<42>,  Next: Documentation<37>,  Prev: Core and Builtins<43>,  Up: Python 3 9 0 alpha 2

1.23.43.3 Library
.................

   - bpo-39033(1): Fix *note NameError: 3e5. in *note zipimport: 118.
     Patch by Karthikeyan Singaravelan.

   - bpo-39022(2): Update importlib.metadata to include improvements
     from importlib_metadata 1.3 including better serialization of
     EntryPoints and improved documentation for custom finders.

   - bpo-39006(3): Fix asyncio when the ssl module is missing: only
     check for ssl.SSLSocket instance if the ssl module is available.

   - bpo-38708(4): Fix a potential IndexError in email parser when
     parsing an empty msg-id.

   - bpo-38698(5): Add a new ‘InvalidMessageID’ token to email parser to
     represent invalid Message-ID headers.  Also, add defects when there
     is remaining value after parsing the header.

   - bpo-38994(6): Implement ‘__class_getitem__’ for ‘os.PathLike’,
     ‘pathlib.Path’.

   - bpo-38979(7): Return class from ‘ContextVar.__class_getitem__’ to
     simplify subclassing.

   - bpo-38978(8): Implement ‘__class_getitem__’ on asyncio objects
     (Future, Task, Queue).  Patch by Batuhan Taskaya.

   - bpo-38916(9): *note array.array: 186.: Remove ‘tostring()’ and
     ‘fromstring()’ methods.  They were aliases to ‘tobytes()’ and
     ‘frombytes()’, deprecated since Python 3.2.

   - bpo-38986(10): Make repr of C accelerated TaskWakeupMethWrapper the
     same as of pure Python version.

   - bpo-38982(11): Fix asyncio ‘PidfdChildWatcher’: handle ‘waitpid()’
     error.  If ‘waitpid()’ is called elsewhere, ‘waitpid()’ call fails
     with *note ChildProcessError: ffb.: use return code 255 in this
     case, and log a warning.  It ensures that the pidfd file descriptor
     is closed if this error occurs.

   - bpo-38529(12): Drop too noisy asyncio warning about deletion of a
     stream without explicit ‘.close()’ call.

   - bpo-27413(13): Added ability to pass through ‘ensure_ascii’ options
     to json.dumps in the ‘json.tool’ command-line interface.

   - bpo-38634(14): The *note readline: a8. module now detects if Python
     is linked to libedit at runtime on all platforms.  Previously, the
     check was only done on macOS.

   - bpo-33684(15): Fix ‘json.tool’ failed to read a JSON file with
     non-ASCII characters when locale encoding is not UTF-8.

   - bpo-38698(16): Prevent UnboundLocalError to pop up in
     parse_message_id.

     parse_message_id() was improperly using a token defined inside an
     exception handler, which was raising ‘UnboundLocalError’ on parsing
     an invalid value.  Patch by Claudiu Popa.

   - bpo-38927(17): Use ‘python -m pip’ instead of ‘pip’ to upgrade
     dependencies in venv.

   - bpo-26730(18): Fix ‘SpooledTemporaryFile.rollover()’ might corrupt
     the file when it is in text mode.  Patch by Serhiy Storchaka.

   - bpo-38881(19): random.choices() now raises a ValueError when all
     the weights are zero.

   - bpo-38876(20): Raise pickle.UnpicklingError when loading an item
     from memo for invalid input.

     The previous code was raising a ‘KeyError’ for both the Python and
     C implementation.  This was caused by the specified index of an
     invalid input which did not exist in the memo structure, where the
     pickle stores what objects it has seen.  The malformed input would
     have caused either a ‘BINGET’ or ‘LONG_BINGET’ load from the memo,
     leading to a ‘KeyError’ as the determined index was bogus.  Patch
     by Claudiu Popa.

   - bpo-38688(21): Calling func:‘shutil.copytree’ to copy a directory
     tree from one directory to another subdirectory resulted in an
     endless loop and a RecursionError.  A fix was added to consume an
     iterator and create the list of the entries to be copied, avoiding
     the recursion for newly created directories.  Patch by Bruno P.
     Kinoshita.

   - bpo-38863(22): Improve ‘is_cgi()’ function in *note http.server:
     68, which enables processing the case that cgi directory is a child
     of another directory other than root.

   - bpo-37838(23): *note typing.get_type_hints(): 657. properly handles
     functions decorated with *note functools.wraps(): f00.

   - bpo-38870(24): Expose *note ast.unparse(): 88a. as a function of
     the *note ast: 7. module that can be used to unparse an *note
     ast.AST: 18c. object and produce a string with code that would
     produce an equivalent *note ast.AST: 18c. object when parsed.
     Patch by Pablo Galindo and Batuhan Taskaya.

   - bpo-38859(25): AsyncMock now returns StopAsyncIteration on the
     exhaustion of a side_effects iterable.  Since PEP-479 its
     Impossible to raise a StopIteration exception from a coroutine.

   - bpo-38857(26): AsyncMock fix for return values that are awaitable
     types.  This also covers side_effect iterable values that happened
     to be awaitable, and wraps callables that return an awaitable type.
     Before these awaitables were being awaited instead of being
     returned as is.

   - bpo-38834(27): *note typing.TypedDict: 146. subclasses now track
     which keys are optional using the ‘__required_keys__’ and
     ‘__optional_keys__’ attributes, to enable runtime validation by
     downstream projects.  Patch by Zac Hatfield-Dodds.

   - bpo-38821(28): Fix unhandled exceptions in *note argparse: 5. when
     internationalizing error messages for arguments with ‘nargs’ set to
     special (non-integer) values.  Patch by Federico Bond.

   - bpo-38820(29): Make Python compatible with OpenSSL 3.0.0.  *note
     ssl.SSLSocket.getpeercert(): f5a. no longer returns IPv6 addresses
     with a trailing new line.

   - bpo-38811(30): Fix an unhandled exception in *note pathlib: 93.
     when *note os.link(): 1088. is missing.  Patch by Toke
     Høiland-Jørgensen.

   - bpo-38686(31): Added support for multiple ‘qop’ values in *note
     urllib.request.AbstractDigestAuthHandler: 1886.

   - bpo-38712(32): Add the Linux-specific *note
     signal.pidfd_send_signal(): 8cf. function, which allows sending a
     signal to a process identified by a file descriptor rather than a
     pid.

   - bpo-38348(33): Add ‘-i’ and ‘--indent’ (indentation level), and
     ‘--no-type-comments’ (type comments) command line options to ast
     parsing tool.

   - bpo-37523(34): Change ‘zipfile.ZipExtFile’ to raise ‘ValueError’
     when trying to access the underlying file object after it has been
     closed.  This new behavior is consistent with how accessing closed
     files is handled in other parts of Python.

   - bpo-38045(35): Improve the performance of ‘enum._decompose()’ in
     *note enum: 4c.  Patch by hongweipeng.

   - bpo-36820(36): Break cycle generated when saving an exception in
     socket.py, codeop.py and dyld.py as they keep alive not only the
     exception but user objects through the ‘__traceback__’ attribute.
     Patch by Mario Corchero.

   - bpo-36406(37): Handle namespace packages in *note doctest: 31.
     Patch by Karthikeyan Singaravelan.

   - bpo-34776(38): Fix dataclasses to support forward references in
     type annotations

   - bpo-20928(39): ElementTree supports recursive XInclude processing.
     Patch by Stefan Behnel.

   - bpo-29636(40): Add whitespace options for formatting JSON with the
     ‘json.tool’ CLI. The following mutually exclusive options are now
     supported: ‘--indent’ for setting the indent level in spaces;
     ‘--tab’ for indenting with tabs; ‘--no-indent’ for suppressing
     newlines; and ‘--compact’ for suppressing all whitespace.  The
     default behavior remains the same as ‘--indent=4’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39033

   (2) https://bugs.python.org/issue?@action=redirect&bpo=39022

   (3) https://bugs.python.org/issue?@action=redirect&bpo=39006

   (4) https://bugs.python.org/issue?@action=redirect&bpo=38708

   (5) https://bugs.python.org/issue?@action=redirect&bpo=38698

   (6) https://bugs.python.org/issue?@action=redirect&bpo=38994

   (7) https://bugs.python.org/issue?@action=redirect&bpo=38979

   (8) https://bugs.python.org/issue?@action=redirect&bpo=38978

   (9) https://bugs.python.org/issue?@action=redirect&bpo=38916

   (10) https://bugs.python.org/issue?@action=redirect&bpo=38986

   (11) https://bugs.python.org/issue?@action=redirect&bpo=38982

   (12) https://bugs.python.org/issue?@action=redirect&bpo=38529

   (13) https://bugs.python.org/issue?@action=redirect&bpo=27413

   (14) https://bugs.python.org/issue?@action=redirect&bpo=38634

   (15) https://bugs.python.org/issue?@action=redirect&bpo=33684

   (16) https://bugs.python.org/issue?@action=redirect&bpo=38698

   (17) https://bugs.python.org/issue?@action=redirect&bpo=38927

   (18) https://bugs.python.org/issue?@action=redirect&bpo=26730

   (19) https://bugs.python.org/issue?@action=redirect&bpo=38881

   (20) https://bugs.python.org/issue?@action=redirect&bpo=38876

   (21) https://bugs.python.org/issue?@action=redirect&bpo=38688

   (22) https://bugs.python.org/issue?@action=redirect&bpo=38863

   (23) https://bugs.python.org/issue?@action=redirect&bpo=37838

   (24) https://bugs.python.org/issue?@action=redirect&bpo=38870

   (25) https://bugs.python.org/issue?@action=redirect&bpo=38859

   (26) https://bugs.python.org/issue?@action=redirect&bpo=38857

   (27) https://bugs.python.org/issue?@action=redirect&bpo=38834

   (28) https://bugs.python.org/issue?@action=redirect&bpo=38821

   (29) https://bugs.python.org/issue?@action=redirect&bpo=38820

   (30) https://bugs.python.org/issue?@action=redirect&bpo=38811

   (31) https://bugs.python.org/issue?@action=redirect&bpo=38686

   (32) https://bugs.python.org/issue?@action=redirect&bpo=38712

   (33) https://bugs.python.org/issue?@action=redirect&bpo=38348

   (34) https://bugs.python.org/issue?@action=redirect&bpo=37523

   (35) https://bugs.python.org/issue?@action=redirect&bpo=38045

   (36) https://bugs.python.org/issue?@action=redirect&bpo=36820

   (37) https://bugs.python.org/issue?@action=redirect&bpo=36406

   (38) https://bugs.python.org/issue?@action=redirect&bpo=34776

   (39) https://bugs.python.org/issue?@action=redirect&bpo=20928

   (40) https://bugs.python.org/issue?@action=redirect&bpo=29636


File: python.info,  Node: Documentation<37>,  Next: Tests<39>,  Prev: Library<42>,  Up: Python 3 9 0 alpha 2

1.23.43.4 Documentation
.......................

   - bpo-38928(1): Correct when venv's ‘upgrade_dependencies()’ and
     ‘--upgrade-deps’ are added.

   - bpo-38899(2): Update documentation to state that to activate
     virtual environments under fish one should use ‘source’, not ‘.’ as
     documented at
     ‘https://fishshell.com/docs/current/cmds/source.html’.

   - bpo-22377(3): Improves documentation of the values that *note
     datetime.datetime.strptime(): 14fe. accepts for ‘%Z’.  Patch by
     Karl Dubost.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38928

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38899

   (3) https://bugs.python.org/issue?@action=redirect&bpo=22377


File: python.info,  Node: Tests<39>,  Next: Build<42>,  Prev: Documentation<37>,  Up: Python 3 9 0 alpha 2

1.23.43.5 Tests
...............

   - bpo-38546(1): Fix test_ressources_gced_in_workers() of
     test_concurrent_futures: explicitly stop the manager to prevent
     leaking a child process running in the background after the test
     completes.

   - bpo-38546(2): Multiprocessing and concurrent.futures tests now stop
     the resource tracker process when tests complete.

   - bpo-38614(3): Replace hardcoded timeout constants in tests with new
     *note test.support: cd. constants: *note LOOPBACK_TIMEOUT: 18b8,
     *note INTERNET_TIMEOUT: 18b9, *note SHORT_TIMEOUT: 17b1. and *note
     LONG_TIMEOUT: 18ba.  It becomes easier to adjust these four timeout
     constants for all tests at once, rather than having to adjust every
     single test file.

   - bpo-38547(4): Fix test_pty: if the process is the session leader,
     closing the master file descriptor raises a SIGHUP signal: simply
     ignore SIGHUP when running the tests.

   - bpo-38992(5): Fix a test for *note math.fsum(): 1342. that was
     failing due to constant folding.

   - bpo-38991(6): *note test.support: cd.: ‘run_python_until_end()’,
     ‘assert_python_ok()’ and ‘assert_python_failure()’ functions no
     longer strip whitespaces from stderr.  Remove
     ‘test.support.strip_python_stderr()’ function.

   - bpo-38965(7): Fix test_faulthandler on GCC 10.  Use the "volatile"
     keyword in ‘faulthandler._stack_overflow()’ to prevent tail call
     optimization on any compiler, rather than relying on compiler
     specific pragma.

   - bpo-38875(8): test_capi: trashcan tests now require the test "cpu"
     resource.

   - bpo-38841(9): Skip asyncio
     test_create_datagram_endpoint_existing_sock_unix on platforms
     lacking a functional bind() for named unix domain sockets.

   - bpo-38692(10): Skip the test_posix.test_pidfd_open() test if
     ‘os.pidfd_open()’ fails with a *note PermissionError: ce9.  This
     situation can happen in a Linux sandbox using a syscall whitelist
     which doesn't allow the ‘pidfd_open()’ syscall yet.

   - bpo-38839(11): Fix some unused functions in tests.  Patch by Adam
     Johnson.

   - bpo-38669(12): Raise *note TypeError: 4dd. when passing target as a
     string with *note unittest.mock.patch.object(): 18bb.

   - bpo-37957(13): test.regrtest now can receive a list of test
     patterns to ignore (using the -i/-ignore argument) or a file with a
     list of patterns to ignore (using the -ignore-file argument).
     Patch by Pablo Galindo.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38546

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38546

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38614

   (4) https://bugs.python.org/issue?@action=redirect&bpo=38547

   (5) https://bugs.python.org/issue?@action=redirect&bpo=38992

   (6) https://bugs.python.org/issue?@action=redirect&bpo=38991

   (7) https://bugs.python.org/issue?@action=redirect&bpo=38965

   (8) https://bugs.python.org/issue?@action=redirect&bpo=38875

   (9) https://bugs.python.org/issue?@action=redirect&bpo=38841

   (10) https://bugs.python.org/issue?@action=redirect&bpo=38692

   (11) https://bugs.python.org/issue?@action=redirect&bpo=38839

   (12) https://bugs.python.org/issue?@action=redirect&bpo=38669

   (13) https://bugs.python.org/issue?@action=redirect&bpo=37957


File: python.info,  Node: Build<42>,  Next: Windows<37>,  Prev: Tests<39>,  Up: Python 3 9 0 alpha 2

1.23.43.6 Build
...............

   - bpo-37404(1): *note asyncio: 8. now raises *note TypeError: 4dd.
     when calling incompatible methods with an *note ssl.SSLSocket: 88f.
     socket.  Patch by Ido Michael.

   - bpo-36500(2): Added an optional "regen" project to the Visual
     Studio solution that will regenerate all grammar, tokens, and
     opcodes.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=37404

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36500


File: python.info,  Node: Windows<37>,  Next: macOS<31>,  Prev: Build<42>,  Up: Python 3 9 0 alpha 2

1.23.43.7 Windows
.................

   - bpo-39007(1): Add auditing events to functions in *note winreg: fe.

   - bpo-33125(2): Add support for building and releasing Windows ARM64
     packages.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=39007

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33125


File: python.info,  Node: macOS<31>,  Next: IDLE<29>,  Prev: Windows<37>,  Up: Python 3 9 0 alpha 2

1.23.43.8 macOS
...............

   - bpo-37931(1): Fixed a crash on OSX dynamic builds that occurred
     when re-initializing the posix module after a Py_Finalize if the
     environment had changed since the previous ‘import posix’.  Patch
     by Benoît Hudson.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=37931


File: python.info,  Node: IDLE<29>,  Next: C API<41>,  Prev: macOS<31>,  Up: Python 3 9 0 alpha 2

1.23.43.9 IDLE
..............

   - bpo-38944(1): Escape key now closes IDLE completion windows.  Patch
     by Johnny Najera.

   - bpo-38943(2): Fix IDLE autocomplete windows not always appearing on
     some systems.  Patch by Johnny Najera.

   - bpo-38862(3): 'Strip Trailing Whitespace' on the Format menu
     removes extra newlines at the end of non-shell files.

   - bpo-38636(4): Fix IDLE Format menu tab toggle and file indent
     width.  These functions (default shortcuts Alt-T and Alt-U) were
     mistakenly disabled in 3.7.5 and 3.8.0.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38944

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38943

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38862

   (4) https://bugs.python.org/issue?@action=redirect&bpo=38636


File: python.info,  Node: C API<41>,  Prev: IDLE<29>,  Up: Python 3 9 0 alpha 2

1.23.43.10 C API
................

   - bpo-38896(1): Remove ‘PyUnicode_ClearFreeList()’ function: the
     Unicode free list has been removed in Python 3.3.

   - bpo-37340(2): Remove ‘PyMethod_ClearFreeList()’ and
     ‘PyCFunction_ClearFreeList()’ functions: the free lists of bound
     method objects have been removed.

   - bpo-38835(3): Exclude ‘PyFPE_START_PROTECT()’ and
     ‘PyFPE_END_PROTECT()’ macros of ‘pyfpe.h’ from ‘Py_LIMITED_API’
     (stable API).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38896

   (2) https://bugs.python.org/issue?@action=redirect&bpo=37340

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38835


File: python.info,  Node: Python 3 9 0 alpha 1,  Next: Python 3 8 0 beta 1,  Prev: Python 3 9 0 alpha 2,  Up: Changelog（更動日誌）

1.23.44 Python 3.9.0 alpha 1
----------------------------

'Release date: 2019-11-19'

* Menu:

* Security: Security<29>.
* Core and Builtins: Core and Builtins<44>.
* Library: Library<43>.
* Documentation: Documentation<38>.
* Tests: Tests<40>.
* Build: Build<43>.
* Windows: Windows<38>.
* macOS: macOS<32>.
* IDLE: IDLE<30>.
* Tools/Demos: Tools/Demos<19>.
* C API: C API<42>.


File: python.info,  Node: Security<29>,  Next: Core and Builtins<44>,  Up: Python 3 9 0 alpha 1

1.23.44.1 Security
..................

   - bpo-38722(1): *note runpy: ac. now uses *note io.open_code(): 1625.
     to open code files.  Patch by Jason Killen.

   - bpo-38622(2): Add additional audit events for the *note ctypes: 22.
     module.

   - bpo-38418(3): Fixes audit event for *note os.system(): 13c8. to be
     named ‘os.system’.

   - bpo-38243(4): Escape the server title of *note
     xmlrpc.server.DocXMLRPCServer: 18c3. when rendering the document
     page as HTML. (Contributed by Donghee Na in bpo-38243(5).)

   - bpo-38174(6): Update vendorized expat library version to 2.2.8,
     which resolves CVE-2019-15903(7).

   - bpo-37764(8): Fixes email._header_value_parser.get_unstructured
     going into an infinite loop for a specific case in which the email
     header does not have trailing whitespace, and the case in which it
     contains an invalid encoded word.  Patch by Ashwin Ramaswami.

   - bpo-37461(9): Fix an infinite loop when parsing specially crafted
     email headers.  Patch by Abhilash Raj.

   - bpo-37363(10): Adds audit events for the range of supported run
     commands (see *note 命令列與環境: 18c4.).

   - bpo-37463(11): ssl.match_hostname() no longer accepts IPv4
     addresses with additional text after the address and only
     quad-dotted notation without trailing whitespaces.  Some
     inet_aton() implementations ignore whitespace and all data after
     whitespace, e.g.  '127.0.0.1 whatever'.

   - bpo-37363(12): Adds audit events for *note ensurepip: 4b, *note
     ftplib: 54, *note glob: 5a, *note imaplib: 6a, ‘nntplib’, *note
     pdb: 94, *note poplib: 9a, *note shutil: b3, *note smtplib: b7,
     *note sqlite3: ba, *note subprocess: c1, ‘telnetlib’, *note
     tempfile: c9. and *note webbrowser: fd, as well as *note
     os.listdir(): 1092, *note os.scandir(): a02. and *note
     breakpoint(): 219.

   - bpo-37364(13): *note io.open_code(): 1625. is now used when reading
     ‘.pth’ files.

   - bpo-34631(14): Updated OpenSSL to 1.1.1c in Windows installer

   - bpo-34155(15): Fix parsing of invalid email addresses with more
     than one ‘@’ (e.g.  a@b@c.com.)  to not return the part before 2nd
     ‘@’ as valid email address.  Patch by maxking & jpic.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38722

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38622

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38418

   (4) https://bugs.python.org/issue?@action=redirect&bpo=38243

   (5) https://bugs.python.org/issue?@action=redirect&bpo=38243

   (6) https://bugs.python.org/issue?@action=redirect&bpo=38174

   (7) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15903

   (8) https://bugs.python.org/issue?@action=redirect&bpo=37764

   (9) https://bugs.python.org/issue?@action=redirect&bpo=37461

   (10) https://bugs.python.org/issue?@action=redirect&bpo=37363

   (11) https://bugs.python.org/issue?@action=redirect&bpo=37463

   (12) https://bugs.python.org/issue?@action=redirect&bpo=37363

   (13) https://bugs.python.org/issue?@action=redirect&bpo=37364

   (14) https://bugs.python.org/issue?@action=redirect&bpo=34631

   (15) https://bugs.python.org/issue?@action=redirect&bpo=34155


File: python.info,  Node: Core and Builtins<44>,  Next: Library<43>,  Prev: Security<29>,  Up: Python 3 9 0 alpha 1

1.23.44.2 Core and Builtins
...........................

   - bpo-38631(1): Replace ‘Py_FatalError()’ call with a regular *note
     RuntimeError: 179. exception in ‘float.__getformat__()’.

   - bpo-38639(2): Optimized *note math.floor(): 132f, *note
     math.ceil(): 1330. and *note math.trunc(): 1331. for floats.

   - bpo-38640(3): Fixed a bug in the compiler that was causing to raise
     in the presence of break statements and continue statements inside
     always false while loops.  Patch by Pablo Galindo.

   - bpo-38613(4): Optimized some set operations (e.g.  ‘|’, ‘^’, and
     ‘-’) of ‘dict_keys’.  ‘d.keys() | other’ was slower than ‘set(d) |
     other’ but they are almost same performance for now.

   - bpo-28029(5): ‘"".replace("", s, n)’ now returns ‘s’ instead of an
     empty string for all non-zero ‘n’.  There are similar changes for
     *note bytes: 1a5. and *note bytearray: 4e3. objects.

   - bpo-38535(6): Fixed line numbers and column offsets for AST nodes
     for calls without arguments in decorators.

   - bpo-38525(7): Fix a segmentation fault when using reverse iterators
     of empty ‘dict’ objects.  Patch by Donghee Na and Inada Naoki.

   - bpo-38465(8): *note bytearray: 4e3, *note array: 186. and *note
     mmap: 1f0. objects allow now to export more than ‘2**31’ buffers at
     a time.

   - bpo-38469(9): Fixed a bug where the scope of named expressions was
     not being resolved correctly in the presence of the 'global'
     keyword.  Patch by Pablo Galindo.

   - bpo-38437(10): Activate the ‘GC_DEBUG’ macro for debug builds of
     the interpreter (when ‘Py_DEBUG’ is set).  Patch by Pablo Galindo.

   - bpo-38379(11): When the garbage collector makes a collection in
     which some objects resurrect (they are reachable from outside the
     isolated cycles after the finalizers have been executed), do not
     block the collection of all objects that are still unreachable.
     Patch by Pablo Galindo and Tim Peters.

   - bpo-38379(12): When cyclic garbage collection (gc) runs finalizers
     that resurrect unreachable objects, the current gc run ends,
     without collecting any cyclic trash.  However, the statistics
     reported by ‘collect()’ and ‘get_stats()’ claimed that all cyclic
     trash found was collected, and that the resurrected objects were
     collected.  Changed the stats to report that none were collected.

   - bpo-38392(13): In debug mode, *note PyObject_GC_Track(): 1474. now
     calls ‘tp_traverse()’ of the object type to ensure that the object
     is valid: test that objects visited by ‘tp_traverse()’ are valid.

   - bpo-38210(14): Remove unnecessary intersection and update set
     operation in dictview with empty set.  (Contributed by Donghee Na
     in bpo-38210(15).)

   - bpo-38402(16): Check the error from the system's underlying ‘crypt’
     or ‘crypt_r’.

   - bpo-37474(17): On FreeBSD, Python no longer calls
     ‘fedisableexcept()’ at startup to control the floating-point
     control mode.  The call became useless since FreeBSD 6: it became
     the default mode.

   - bpo-38006(18): Fix a bug due to the interaction of weakrefs and the
     cyclic garbage collector.  We must clear any weakrefs in garbage in
     order to prevent their callbacks from executing and causing a
     crash.

   - bpo-38317(19): Fix warnings options priority:
     ‘PyConfig.warnoptions’ has the highest priority, as stated in the
     PEP 587(20).

   - bpo-38310(21): Predict ‘BUILD_MAP_UNPACK_WITH_CALL’ ->
     ‘CALL_FUNCTION_EX’ opcode pairs in the main interpreter loop.
     Patch by Brandt Bucher.

   - bpo-36871(22): Improve error handling for the assert_has_calls and
     assert_has_awaits methods of mocks.  Fixed a bug where any errors
     encountered while binding the expected calls to the mock's spec
     were silently swallowed, leading to misleading error output.

   - bpo-11410(23): Better control over symbol visibility is provided
     through use of the visibility attributes available in gcc >= 4.0,
     provided in a uniform way across POSIX and Windows.  The POSIX
     build files have been updated to compile with -fvisibility=hidden,
     minimising exported symbols.

   - bpo-38219(24): Optimized the *note dict: 23b. constructor and the
     *note update(): 13d0. method for the case when the argument is a
     dict.

   - bpo-38236(25): Python now dumps path configuration if it fails to
     import the Python codecs of the filesystem and stdio encodings.

   - bpo-38013(26): Allow to call ‘async_generator_athrow().throw(...)’
     even for non-started async generator helper.  It fixes annoying
     warning at the end of *note asyncio.run(): 423. call.

   - bpo-38124(27): Fix an off-by-one error in PyState_AddModule that
     could cause out-of-bounds memory access.

   - bpo-38116(28): The select module is now PEP-384 compliant and no
     longer has static state

   - bpo-38113(29): ast module updated to PEP-384 and all statics
     removed

   - bpo-38076(30): The struct module is now PEP-384 compatible

   - bpo-38075(31): The random module is now PEP-384 compatible

   - bpo-38074(32): zlib module made PEP-384 compatible

   - bpo-38073(33): Make pwd extension module PEP-384 compatible

   - bpo-38072(34): grp module made PEP-384 compatible

   - bpo-38069(35): Make _posixsubprocess PEP-384 compatible

   - bpo-38071(36): Make termios extension module PEP-384 compatible

   - bpo-38005(37): Fixed comparing and creating of InterpreterID and
     ChannelID.

   - bpo-36946(38): Fix possible signed integer overflow when handling
     slices.  Patch by hongweipeng.

   - bpo-37994(39): Fixed silencing arbitrary errors if an attribute
     lookup fails in several sites.  Only AttributeError should be
     silenced.

   - bpo-8425(40): Optimize set difference_update for the case when the
     other set is much larger than the base set.  (Suggested by Evgeny
     Kapun with code contributed by Michele Orrù).

   - bpo-37966(41): The implementation of *note is_normalized(): 9ec.
     has been greatly sped up on strings that aren't normalized, by
     implementing the full normalization-quick-check algorithm from the
     Unicode standard.

   - bpo-37947(42): Adjust correctly the recursion level in the symtable
     generation for named expressions.  Patch by Pablo Galindo.

   - bpo-37812(43): The ‘CHECK_SMALL_INT’ macro used inside
     ‘Object/longobject.c’ has been replaced with an explicit ‘return’
     at each call site.

   - bpo-37751(44): Fix *note codecs.lookup(): 907. to normalize the
     encoding name the same way than ‘encodings.normalize_encoding()’,
     except that *note codecs.lookup(): 907. also converts the name to
     lower case.

   - bpo-37830(45): Fixed compilation of *note break: a4c. and *note
     continue: 96d. in the *note finally: 96e. block when the
     corresponding *note try: 68c. block contains *note return: 972.
     with a non-constant value.

   - bpo-20490(46): Improve import error message for partially
     initialized module on circular ‘from’ imports - by Anthony Sottile.

   - bpo-37840(47): Fix handling of negative indices in *note sq_item:
     182f. of *note bytearray: 4e3.  Patch by Sergey Fedoseev.

   - bpo-37802(48): Slightly improve performance of *note
     PyLong_FromUnsignedLong(): 18c6, *note
     PyLong_FromUnsignedLongLong(): 18c7. and *note PyLong_FromSize_t():
     18c8.  Patch by Sergey Fedoseev.

   - bpo-37409(49): Ensure explicit relative imports from interactive
     sessions and scripts (having no parent package) always raise
     ImportError, rather than treating the current module as the
     package.  Patch by Ben Lewis.

   - bpo-32912(50): Reverted bpo-32912(51): emitting *note
     SyntaxWarning: 40c. instead of *note DeprecationWarning: 18b. for
     invalid escape sequences in string and bytes literals.

   - bpo-37757(52): PEP 572(53): As described in the PEP, assignment
     expressions now raise *note SyntaxError: 173. when their
     interaction with comprehension scoping results in an ambiguous
     target scope.

     The ‘TargetScopeError’ subclass originally proposed by the PEP has
     been removed in favour of just raising regular syntax errors for
     the disallowed cases.

   - bpo-36279(54): Fix potential use of uninitialized memory in *note
     os.wait3(): d3c.

   - bpo-36311(55): Decoding bytes objects larger than 2GiB is faster
     and no longer fails when a multibyte characters spans a chunk
     boundary.

   - bpo-34880(56): The *note assert: 90c. statement now works properly
     if the *note AssertionError: 64e. exception is being shadowed.
     Patch by Zackery Spytz.

   - bpo-37340(57): Removed object cache (‘free_list’) for bound method
     objects.  Temporary bound method objects are less used than before
     thanks to the ‘LOAD_METHOD’ opcode and the
     ‘_PyObject_VectorcallMethod’ C API.

   - bpo-37648(58): Fixed minor inconsistency in ‘list.__contains__()’,
     ‘tuple.__contains__()’ and a few other places.  The collection's
     item is now always at the left and the needle is on the right of
     ‘==’.

   - bpo-37444(59): Update differing exception between
     ‘builtins.__import__()’ and *note importlib.__import__(): 100e.

   - bpo-37619(60): When adding a wrapper descriptor from one class to a
     different class (for example, setting ‘__add__ = str.__add__’ on an
     ‘int’ subclass), an exception is correctly raised when the operator
     is called.

   - bpo-37593(61): Swap the positions of the 'posonlyargs' and 'args'
     parameters in the constructor of ‘ast.parameters’ nodes.

   - bpo-37543(62): Optimized pymalloc for non PGO build.

   - bpo-37537(63): Compute allocated pymalloc blocks inside
     _Py_GetAllocatedBlocks().  This slows down _Py_GetAllocatedBlocks()
     but gives a small speedup to _PyObject_Malloc() and
     _PyObject_Free().

   - bpo-37467(64): Fix *note sys.excepthook(): 7af. and
     ‘PyErr_Display()’ if a filename is a bytes string.  For example,
     for a SyntaxError exception where the filename attribute is a bytes
     string.

   - bpo-37433(65): Fix ‘SyntaxError’ indicator printing too many spaces
     for multi-line strings - by Anthony Sottile.

   - bpo-37417(66): ‘bytearray.extend()’ now correctly handles errors
     that arise during iteration.  Patch by Brandt Bucher.

   - bpo-37414(67): The undocumented ‘sys.callstats()’ function has been
     removed.  Since Python 3.7, it was deprecated and always returned
     ‘None’.  It required a special build option ‘CALL_PROFILE’ which
     was already removed in Python 3.7.

   - bpo-37392(68): Remove ‘sys.getcheckinterval()’ and
     ‘sys.setcheckinterval()’ functions.  They were deprecated since
     Python 3.2.  Use *note sys.getswitchinterval(): 8ed. and *note
     sys.setswitchinterval(): 8ee. instead.  Remove also
     ‘check_interval’ field of the ‘PyInterpreterState’ structure.

   - bpo-37388(69): In development mode and in debug build, 'encoding'
     and 'errors' arguments are now checked on string encoding and
     decoding operations.  Examples: *note open(): 4c0, *note
     str.encode(): 87a. and *note bytes.decode(): 87b.

     By default, for best performances, the 'errors' argument is only
     checked at the first encoding/decoding error, and the 'encoding'
     argument is sometimes ignored for empty strings.

   - bpo-37348(70): Optimized decoding short ASCII string with UTF-8 and
     ascii codecs.  ‘b"foo".decode()’ is about 15% faster.  Patch by
     Inada Naoki.

   - bpo-24214(71): Improved support of the surrogatepass error handler
     in the UTF-8 and UTF-16 incremental decoders.

   - bpo-37330(72): *note open(): 4c0, *note io.open(): 4c1, *note
     codecs.open(): 6e4. and *note fileinput.FileInput: 6db. no longer
     accept ‘'U'’ ("universal newline") in the file mode.  This flag was
     deprecated since Python 3.3.

   - bpo-35224(73): Reverse evaluation order of key: value in dict
     comprehensions as proposed in PEP 572.  I.e.  in ‘{k: v for ...}’,
     ‘k’ will be evaluated before ‘v’.

   - bpo-37316(74): Fix the *note PySys_Audit(): 321. call in *note
     mmap.mmap: 1f0.

   - bpo-37300(75): Remove an unnecessary Py_XINCREF in classobject.c.

   - bpo-37269(76): Fix a bug in the peephole optimizer that was not
     treating correctly constant conditions with binary operators.
     Patch by Pablo Galindo.

   - bpo-20443(77): Python now gets the absolute path of the script
     filename specified on the command line (ex: "python3 script.py"):
     the __file__ attribute of the __main__ module and sys.path[0]
     become an absolute path, rather than a relative path.

   - bpo-37257(78): Python's small object allocator (‘obmalloc.c’) now
     allows (no more than) one empty arena to remain available for
     immediate reuse, without returning it to the OS. This prevents
     thrashing in simple loops where an arena could be created and
     destroyed anew on each iteration.

   - bpo-37231(79): The dispatching of type slots to special methods
     (for example calling ‘__mul__’ when doing ‘x * y’) has been made
     faster.

   - bpo-36974(80): Implemented separate vectorcall functions for every
     calling convention of builtin functions and methods.  This improves
     performance for calls.

   - bpo-37213(81): Handle correctly negative line offsets in the
     peephole optimizer.  Patch by Pablo Galindo.

   - bpo-37219(82): Remove erroneous optimization for empty set
     differences.

   - bpo-15913(83): Implement *note PyBuffer_SizeFromFormat(): 6fe.
     function (previously documented but not implemented): call *note
     struct.calcsize(): 18c9.  Patch by Joannah Nanjekye.

   - bpo-36922(84): Slot functions optimize any callable with
     ‘Py_TPFLAGS_METHOD_DESCRIPTOR’ instead of only instances of
     ‘function’.

   - bpo-36974(85): The slot ‘tp_vectorcall_offset’ is inherited
     unconditionally to support ‘super().__call__()’ when the base class
     uses vectorcall.

   - bpo-37160(86): *note threading.get_native_id(): 9e1. now also
     supports NetBSD.

   - bpo-37077(87): Add *note threading.get_native_id(): 9e1. support
     for AIX. Patch by M. Felt

   - bpo-36781(88): *note sum(): 411. has been optimized for boolean
     values.

   - bpo-34556(89): Add ‘--upgrade-deps’ to venv module.  Patch by
     Cooper Ry Lees

   - bpo-20523(90): ‘pdb.Pdb’ supports ~/.pdbrc in Windows 7.  Patch by
     Tim Hopper and Dan Lidral-Porter.

   - bpo-35551(91): Updated encodings: - Removed the "tis260" encoding,
     which was an alias for the nonexistent "tactis" codec.  - Added
     "mac_centeuro" as an alias for the mac_latin2 encoding.

   - bpo-19072(92): The *note classmethod: 14a. decorator can now wrap
     other descriptors such as property objects.  Adapted from a patch
     written by Graham Dumpleton.

   - bpo-27575(93): Improve speed of dictview intersection by directly
     using set intersection logic.  Patch by David Su.

   - bpo-30773(94): Prohibit parallel running of aclose() / asend() /
     athrow().  Fix ag_running to reflect the actual running status of
     the AG.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38631

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38639

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38640

   (4) https://bugs.python.org/issue?@action=redirect&bpo=38613

   (5) https://bugs.python.org/issue?@action=redirect&bpo=28029

   (6) https://bugs.python.org/issue?@action=redirect&bpo=38535

   (7) https://bugs.python.org/issue?@action=redirect&bpo=38525

   (8) https://bugs.python.org/issue?@action=redirect&bpo=38465

   (9) https://bugs.python.org/issue?@action=redirect&bpo=38469

   (10) https://bugs.python.org/issue?@action=redirect&bpo=38437

   (11) https://bugs.python.org/issue?@action=redirect&bpo=38379

   (12) https://bugs.python.org/issue?@action=redirect&bpo=38379

   (13) https://bugs.python.org/issue?@action=redirect&bpo=38392

   (14) https://bugs.python.org/issue?@action=redirect&bpo=38210

   (15) https://bugs.python.org/issue?@action=redirect&bpo=38210

   (16) https://bugs.python.org/issue?@action=redirect&bpo=38402

   (17) https://bugs.python.org/issue?@action=redirect&bpo=37474

   (18) https://bugs.python.org/issue?@action=redirect&bpo=38006

   (19) https://bugs.python.org/issue?@action=redirect&bpo=38317

   (20) https://peps.python.org/pep-0587/

   (21) https://bugs.python.org/issue?@action=redirect&bpo=38310

   (22) https://bugs.python.org/issue?@action=redirect&bpo=36871

   (23) https://bugs.python.org/issue?@action=redirect&bpo=11410

   (24) https://bugs.python.org/issue?@action=redirect&bpo=38219

   (25) https://bugs.python.org/issue?@action=redirect&bpo=38236

   (26) https://bugs.python.org/issue?@action=redirect&bpo=38013

   (27) https://bugs.python.org/issue?@action=redirect&bpo=38124

   (28) https://bugs.python.org/issue?@action=redirect&bpo=38116

   (29) https://bugs.python.org/issue?@action=redirect&bpo=38113

   (30) https://bugs.python.org/issue?@action=redirect&bpo=38076

   (31) https://bugs.python.org/issue?@action=redirect&bpo=38075

   (32) https://bugs.python.org/issue?@action=redirect&bpo=38074

   (33) https://bugs.python.org/issue?@action=redirect&bpo=38073

   (34) https://bugs.python.org/issue?@action=redirect&bpo=38072

   (35) https://bugs.python.org/issue?@action=redirect&bpo=38069

   (36) https://bugs.python.org/issue?@action=redirect&bpo=38071

   (37) https://bugs.python.org/issue?@action=redirect&bpo=38005

   (38) https://bugs.python.org/issue?@action=redirect&bpo=36946

   (39) https://bugs.python.org/issue?@action=redirect&bpo=37994

   (40) https://bugs.python.org/issue?@action=redirect&bpo=8425

   (41) https://bugs.python.org/issue?@action=redirect&bpo=37966

   (42) https://bugs.python.org/issue?@action=redirect&bpo=37947

   (43) https://bugs.python.org/issue?@action=redirect&bpo=37812

   (44) https://bugs.python.org/issue?@action=redirect&bpo=37751

   (45) https://bugs.python.org/issue?@action=redirect&bpo=37830

   (46) https://bugs.python.org/issue?@action=redirect&bpo=20490

   (47) https://bugs.python.org/issue?@action=redirect&bpo=37840

   (48) https://bugs.python.org/issue?@action=redirect&bpo=37802

   (49) https://bugs.python.org/issue?@action=redirect&bpo=37409

   (50) https://bugs.python.org/issue?@action=redirect&bpo=32912

   (51) https://bugs.python.org/issue?@action=redirect&bpo=32912

   (52) https://bugs.python.org/issue?@action=redirect&bpo=37757

   (53) https://peps.python.org/pep-0572/

   (54) https://bugs.python.org/issue?@action=redirect&bpo=36279

   (55) https://bugs.python.org/issue?@action=redirect&bpo=36311

   (56) https://bugs.python.org/issue?@action=redirect&bpo=34880

   (57) https://bugs.python.org/issue?@action=redirect&bpo=37340

   (58) https://bugs.python.org/issue?@action=redirect&bpo=37648

   (59) https://bugs.python.org/issue?@action=redirect&bpo=37444

   (60) https://bugs.python.org/issue?@action=redirect&bpo=37619

   (61) https://bugs.python.org/issue?@action=redirect&bpo=37593

   (62) https://bugs.python.org/issue?@action=redirect&bpo=37543

   (63) https://bugs.python.org/issue?@action=redirect&bpo=37537

   (64) https://bugs.python.org/issue?@action=redirect&bpo=37467

   (65) https://bugs.python.org/issue?@action=redirect&bpo=37433

   (66) https://bugs.python.org/issue?@action=redirect&bpo=37417

   (67) https://bugs.python.org/issue?@action=redirect&bpo=37414

   (68) https://bugs.python.org/issue?@action=redirect&bpo=37392

   (69) https://bugs.python.org/issue?@action=redirect&bpo=37388

   (70) https://bugs.python.org/issue?@action=redirect&bpo=37348

   (71) https://bugs.python.org/issue?@action=redirect&bpo=24214

   (72) https://bugs.python.org/issue?@action=redirect&bpo=37330

   (73) https://bugs.python.org/issue?@action=redirect&bpo=35224

   (74) https://bugs.python.org/issue?@action=redirect&bpo=37316

   (75) https://bugs.python.org/issue?@action=redirect&bpo=37300

   (76) https://bugs.python.org/issue?@action=redirect&bpo=37269

   (77) https://bugs.python.org/issue?@action=redirect&bpo=20443

   (78) https://bugs.python.org/issue?@action=redirect&bpo=37257

   (79) https://bugs.python.org/issue?@action=redirect&bpo=37231

   (80) https://bugs.python.org/issue?@action=redirect&bpo=36974

   (81) https://bugs.python.org/issue?@action=redirect&bpo=37213

   (82) https://bugs.python.org/issue?@action=redirect&bpo=37219

   (83) https://bugs.python.org/issue?@action=redirect&bpo=15913

   (84) https://bugs.python.org/issue?@action=redirect&bpo=36922

   (85) https://bugs.python.org/issue?@action=redirect&bpo=36974

   (86) https://bugs.python.org/issue?@action=redirect&bpo=37160

   (87) https://bugs.python.org/issue?@action=redirect&bpo=37077

   (88) https://bugs.python.org/issue?@action=redirect&bpo=36781

   (89) https://bugs.python.org/issue?@action=redirect&bpo=34556

   (90) https://bugs.python.org/issue?@action=redirect&bpo=20523

   (91) https://bugs.python.org/issue?@action=redirect&bpo=35551

   (92) https://bugs.python.org/issue?@action=redirect&bpo=19072

   (93) https://bugs.python.org/issue?@action=redirect&bpo=27575

   (94) https://bugs.python.org/issue?@action=redirect&bpo=30773


File: python.info,  Node: Library<43>,  Next: Documentation<38>,  Prev: Core and Builtins<44>,  Up: Python 3 9 0 alpha 1

1.23.44.3 Library
.................

   - bpo-36589(1): The *note curses.update_lines_cols(): d92. function
     now returns ‘None’ instead of ‘1’ on success.

   - bpo-38807(2): Update *note TypeError: 4dd. messages for *note
     os.path.join(): 1527. to include *note os.PathLike: bf8. objects as
     acceptable input types.

   - bpo-38724(3): Add a repr for ‘subprocess.Popen’ objects.  Patch by
     Andrey Doroschenko.

   - bpo-38786(4): pydoc now recognizes and parses HTTPS URLs.  Patch by
     python273.

   - bpo-38785(5): Prevent asyncio from crashing if parent ‘__init__’ is
     not called from a constructor of object derived from
     ‘asyncio.Future’.

   - bpo-38723(6): *note pdb: 94. now uses *note io.open_code(): 1625.
     to trigger auditing events.

   - bpo-27805(7): Allow opening pipes and other non-seekable files in
     append mode with *note open(): 4c0.

   - bpo-38438(8): Simplify the *note argparse: 5. usage message for
     ‘nargs="*"’.

   - bpo-38761(9): WeakSet is now registered as a
     collections.abc.MutableSet.

   - bpo-38716(10): logging: change RotatingHandler namer and rotator to
     class-level attributes.  This stops __init__ from setting them to
     None in the case where a subclass defines them with eponymous
     methods.

   - bpo-38713(11): Add *note os.P_PIDFD: 8bf. constant, which may be
     passed to *note os.waitid(): d3f. to wait on a Linux process file
     descriptor.

   - bpo-38692(12): Add *note asyncio.PidfdChildWatcher: 420, a
     Linux-specific child watcher implementation that polls process file
     descriptors.

   - bpo-38692(13): Expose the Linux ‘pidfd_open’ syscall as *note
     os.pidfd_open(): 421.

   - bpo-38602(14): Added constants ‘F_OFD_GETLK’, ‘F_OFD_SETLK’ and
     ‘F_OFD_SETLKW’ to the *note fcntl: 4f. module.  Patch by Donghee
     Na.

   - bpo-38334(15): Fixed seeking backward on an encrypted
     ‘zipfile.ZipExtFile’.

   - bpo-38312(16): Add *note curses.get_escdelay(): 895, *note
     curses.set_escdelay(): 896, *note curses.get_tabsize(): 897, and
     *note curses.set_tabsize(): 898. functions - by Anthony Sottile.

   - bpo-38586(17): Now *note fileConfig(): af5. correctly sets the
     .name of handlers loaded.

   - bpo-38565(18): Add new cache_parameters() method for
     functools.lru_cache() to better support pickling.

   - bpo-34679(19): asynci.ProactorEventLoop.close() now only calls
     signal.set_wakeup_fd() in the main thread.

   - bpo-31202(20): The case the result of ‘pathlib.WindowsPath.glob()’
     matches now the case of the pattern for literal parts.

   - bpo-36321(21): Remove misspelled attribute.  The 3.8 changelog
     noted that this would be removed in 3.9.

   - bpo-38521(22): Fixed erroneous equality comparison in
     statistics.NormalDist().

   - bpo-38493(23): Added *note CLD_KILLED: 8bd. and *note CLD_STOPPED:
     8be. for ‘si_code’.  Patch by Donghee Na.

   - bpo-38478(24): Fixed a bug in ‘inspect.signature.bind()’ that was
     causing it to fail when handling a keyword argument with same name
     as positional-only parameter.  Patch by Pablo Galindo.

   - bpo-33604(25): Fixed ‘hmac.new’ and ‘hmac.HMAC’ to raise TypeError
     instead of ValueError when the digestmod parameter, now required in
     3.8, is omitted.  Also clarified the hmac module documentation and
     docstrings.

   - bpo-38378(26): Parameters 'out' and 'in' of *note os.sendfile():
     ab2. was renamed to 'out_fd' and 'in_fd'.

   - bpo-38417(27): Added support for setting the umask in the child
     process to the subprocess module on POSIX systems.

   - bpo-38449(28): Revert PR 15522, which introduces a regression in
     *note mimetypes.guess_type(): 1ed. due to improper handling of
     filenames as urls.

   - bpo-38431(29): Fix ‘__repr__’ method for ‘dataclasses.InitVar’ to
     support typing objects, patch by Samuel Colvin.

   - bpo-38109(30): Add missing *note stat.S_IFDOOR: f5d, *note
     stat.S_IFPORT: f5e, *note stat.S_IFWHT: f5f, *note stat.S_ISDOOR():
     18cb, *note stat.S_ISPORT(): 18cc, and *note stat.S_ISWHT(): 18cd.
     values to the Python implementation of *note stat: bc.

   - bpo-38422(31): Clarify docstrings of pathlib suffix(es)

   - bpo-38405(32): Nested subclasses of *note typing.NamedTuple: 291.
     are now pickleable.

   - bpo-38332(33): Prevent *note KeyError: 2fb. thrown by
     ‘_encoded_words.decode()’ when given an encoded-word with invalid
     content-type encoding from propagating all the way to
     ‘email.message.get()’.

   - bpo-38371(34): Deprecated the ‘split()’ method in
     ‘_tkinter.TkappType’ in favour of the ‘splitlist()’ method which
     has more consistent and predictable behavior.

   - bpo-38341(35): Add *note smtplib.SMTPNotSupportedError: 18ce. to
     the *note smtplib: b7. exported names.

   - bpo-38319(36): sendfile() used in socket and shutil modules was
     raising OverflowError for files >= 2GiB on 32-bit architectures.
     (patch by Giampaolo Rodola)

   - bpo-38242(37): Revert the new asyncio Streams API

   - bpo-13153(38): OS native encoding is now used for converting
     between Python strings and Tcl objects.  This allows to display,
     copy and paste to clipboard emoji and other non-BMP characters.
     Converting strings from Tcl to Python and back now never fails
     (except MemoryError).

   - bpo-38019(39): Correctly handle pause/resume reading of closed
     asyncio unix pipe.

   - bpo-38163(40): Child mocks will now detect their type as either
     synchronous or asynchronous, asynchronous child mocks will be
     AsyncMocks and synchronous child mocks will be either MagicMock or
     Mock (depending on their parent type).

   - bpo-38161(41): Removes _AwaitEvent from AsyncMock.

   - bpo-38216(42): Allow the rare code that wants to send invalid http
     requests from the ‘http.client’ library a way to do so.  The fixes
     for bpo-30458(43) led to breakage for some projects that were
     relying on this ability to test their own behavior in the face of
     bad requests.

   - bpo-28286(44): Deprecate opening *note GzipFile: 354. for writing
     implicitly.  Always specify the 'mode' argument for writing.

   - bpo-38108(45): Any synchronous magic methods on an AsyncMock now
     return a MagicMock.  Any asynchronous magic methods on a MagicMock
     now return an AsyncMock.

   - bpo-38265(46): Update the 'length' parameter of *note os.pread():
     b03. to accept *note Py_ssize_t: a03. instead of int.

   - bpo-38112(47): *note compileall: 19. has a higher default recursion
     limit and new command-line arguments for path manipulation,
     symlinks handling, and multiple optimization levels.

   - bpo-38248(48): asyncio: Fix inconsistent immediate Task
     cancellation

   - bpo-38237(49): The arguments for the builtin pow function are more
     descriptive.  They can now also be passed in as keywords.

   - bpo-34002(50): Improve efficiency in parts of email package by
     changing while-pop to a for loop, using isdisjoint instead of set
     intersections.

   - bpo-38191(51): Constructors of *note NamedTuple: 291. and *note
     TypedDict: 146. types now accept arbitrary keyword argument names,
     including "cls", "self", "typename", "_typename", "fields" and
     "_fields".

   - bpo-38155(52): Add ‘__all__’ to *note datetime: 28.  Patch by Tahia
     Khan.

   - bpo-38185(53): Fixed case-insensitive string comparison in *note
     sqlite3.Row: e13. indexing.

   - bpo-38136(54): Changes AsyncMock call count and await count to be
     two different counters.  Now await count only counts when a
     coroutine has been awaited, not when it has been called, and
     vice-versa.  Update the documentation around this.

   - bpo-37828(55): Fix default mock name in *note
     unittest.mock.Mock.assert_called(): c9f. exceptions.  Patch by
     Abraham Toriz Cruz.

   - bpo-38175(56): Fix a memory leak in comparison of *note
     sqlite3.Row: e13. objects.

   - bpo-33936(57): _hashlib no longer calls obsolete OpenSSL
     initialization function with OpenSSL 1.1.0+.

   - bpo-34706(58): Preserve subclassing in
     inspect.Signature.from_callable.

   - bpo-38153(59): Names of hashing algorithms from OpenSSL are now
     normalized to follow Python's naming conventions.  For example
     OpenSSL uses sha3-512 instead of sha3_512 or blake2b512 instead of
     blake2b.

   - bpo-38115(60): Fix a bug in dis.findlinestarts() where it would
     return invalid bytecode offsets.  Document that a code object's
     co_lnotab can contain invalid bytecode offsets.

   - bpo-38148(61): Add slots to *note asyncio: 8. transport classes,
     which can reduce memory usage.

   - bpo-38142(62): The _hashlib OpenSSL wrapper extension module is now
     PEP-384 compliant.

   - bpo-9216(63): hashlib constructors now support usedforsecurity flag
     to signal that a hashing algorithm is not used in a security
     context.

   - bpo-36991(64): Fixes a potential incorrect AttributeError exception
     escaping ZipFile.extract() in some unsupported input error
     situations.

   - bpo-38134(65): Remove obsolete copy of PBKDF2_HMAC_fast.  All
     supported OpenSSL versions contain a fast implementation.

   - bpo-38132(66): The OpenSSL hashlib wrapper uses a simpler
     implementation.  Several Macros and pointless caches are gone.  The
     hash name now comes from OpenSSL's EVP. The algorithm name stays
     the same, except it is now always lower case.

   - bpo-38008(67): Fix parent class check in protocols to correctly
     identify the module that provides a builtin protocol, instead of
     assuming they all come from the *note collections.abc: 17. module

   - bpo-34037(68): For *note asyncio: 8, add a new coroutine
     ‘loop.shutdown_default_executor()’.  The new coroutine provides an
     API to schedule an executor shutdown that waits on the threadpool
     to finish closing.  Also, *note asyncio.run(): 423. has been
     updated to utilize the new coroutine.  Patch by Kyle Stanley.

   - bpo-37405(69): Fixed regression bug for socket.getsockname() for
     non-CAN_ISOTP AF_CAN address family sockets by returning a 1-tuple
     instead of string.

   - bpo-38121(70): Update parameter names on functions in
     importlib.metadata matching the changes in the 0.22 release of
     importlib_metadata.

   - bpo-38110(71): The os.closewalk() implementation now uses the libc
     fdwalk() API on platforms where it is available.

   - bpo-38093(72): Fixes AsyncMock so it doesn't crash when used with
     AsyncContextManagers or AsyncIterators.

   - bpo-37488(73): Add warning to ‘datetime.utctimetuple()’,
     ‘datetime.utcnow()’ and ‘datetime.utcfromtimestamp()’ .

   - bpo-35640(74): Allow passing a *note path-like object: ac2. as
     ‘directory’ argument to the *note
     http.server.SimpleHTTPRequestHandler: ae7. class.  Patch by Géry
     Ogam.

   - bpo-38086(75): Update importlib.metadata with changes from
     importlib_metadata 0.21(76).

   - bpo-37251(77): Remove ‘__code__’ check in AsyncMock that
     incorrectly evaluated function specs as async objects but failed to
     evaluate classes with ‘__await__’ but no ‘__code__’ attribute
     defined as async objects.

   - bpo-38037(78): Fix reference counters in the *note signal: b4.
     module.

   - bpo-38066(79): Hide internal asyncio.Stream methods: feed_eof(),
     feed_data(), set_exception() and set_transport().

   - bpo-38059(80): inspect.py now uses sys.exit() instead of exit()

   - bpo-38049(81): Added command-line interface for the *note ast: 7.
     module.

   - bpo-37953(82): In *note typing: ed, improved the ‘__hash__’ and
     ‘__eq__’ methods for ‘ForwardReferences’.

   - bpo-38026(83): Fixed *note inspect.getattr_static(): 43c. used
     ‘isinstance’ while it should avoid dynamic lookup.

   - bpo-35923(84): Update *note importlib.machinery.BuiltinImporter:
     c56. to use ‘loader._ORIGIN’ instead of a hardcoded value.  Patch
     by Donghee Na.

   - bpo-38010(85): In ‘importlib.metadata’ sync with
     ‘importlib_metadata’ 0.20, clarifying behavior of ‘files()’ and
     fixing issue where only one requirement was returned for
     ‘requires()’ on ‘dist-info’ packages.

   - bpo-38006(86): weakref.WeakValueDictionary defines a local remove()
     function used as callback for weak references.  This function was
     created with a closure.  Modify the implementation to avoid the
     closure.

   - bpo-37995(87): Added the 'indent' option to *note ast.dump(): 889.
     which allows it to produce a multiline indented output.

   - bpo-34410(88): Fixed a crash in the ‘tee()’ iterator when re-enter
     it.  RuntimeError is now raised in this case.

   - bpo-37140(89): Fix a ctypes regression of Python 3.8.  When a
     ctypes.Structure is passed by copy to a function, ctypes internals
     created a temporary object which had the side effect of calling the
     structure finalizer (__del__) twice.  The Python semantics requires
     a finalizer to be called exactly once.  Fix ctypes internals to no
     longer call the finalizer twice.

   - bpo-37587(90): ‘_json.scanstring’ is now up to 3x faster when there
     are many backslash escaped characters in the JSON string.

   - bpo-37834(91): Prevent shutil.rmtree exception when built on
     non-Windows system without fd system call support, like older
     versions of macOS.

   - bpo-10978(92): Semaphores and BoundedSemaphores can now release
     more than one waiting thread at a time.

   - bpo-37972(93): Subscripts to the ‘unittest.mock.call’ objects now
     receive the same chaining mechanism as any other custom attributes,
     so that the following usage no longer raises a ‘TypeError’:

     ‘call().foo().__getitem__('bar')’

     Patch by blhsing

   - bpo-37965(94): Fix C compiler warning caused by
     distutils.ccompiler.CCompiler.has_function.

   - bpo-37964(95): Add ‘F_GETPATH’ command to *note fcntl: 4f.

   - bpo-37960(96): ‘repr()’ of buffered and text streams now silences
     only expected exceptions when get the value of "name" and "mode"
     attributes.

   - bpo-37961(97): Add a ‘total_nframe’ field to the traces collected
     by the tracemalloc module.  This field indicates the original
     number of frames before it was truncated.

   - bpo-37951(98): Most features of the subprocess module now work
     again in subinterpreters.  Only 'preexec_fn' is restricted in
     subinterpreters.

   - bpo-36205(99): Fix the rusage implementation of time.process_time()
     to correctly report the sum of the system and user CPU time.

   - bpo-37950(100): Fix *note ast.dump(): 889. when call with
     incompletely initialized node.

   - bpo-34679(101): Restores instantiation of Windows IOCP event loops
     from the non-main thread.

   - bpo-36917(102): Add default implementation of the *note
     ast.NodeVisitor.visit_Constant(): a11. method which emits a
     deprecation warning and calls corresponding methods ‘visit_Num()’,
     ‘visit_Str()’, etc.

   - bpo-37798(103): Update test_statistics.py to verify that the
     statistics module works well for both C and Python implementations.
     Patch by Donghee Na

   - bpo-26589(104): Added a new status code to the http module: 451
     UNAVAILABLE_FOR_LEGAL_REASONS

   - bpo-37915(105): Fix a segmentation fault that appeared when
     comparing instances of ‘datetime.timezone’ and ‘datetime.tzinfo’
     objects.  Patch by Pablo Galindo.

   - bpo-32554(106): Deprecate having random.seed() call hash on
     arbitrary types.

   - bpo-9938(107): Add optional keyword argument ‘exit_on_error’ for
     ‘ArgumentParser’.

   - bpo-37851(108): The *note faulthandler: 4e. module no longer
     allocates its alternative stack at Python startup.  Now the stack
     is only allocated at the first faulthandler usage.

   - bpo-32793(109): Fix a duplicated debug message when *note
     smtplib.SMTP.connect(): 18cf. is called.

   - bpo-37885(110): venv: Don't generate unset variable warning on
     deactivate.

   - bpo-37868(111): Fix dataclasses.is_dataclass when given an instance
     that never raises AttributeError in __getattr__.  That is, an
     object that returns something for __dataclass_fields__ even if it's
     not a dataclass.

   - bpo-37811(112): Fix ‘socket’ module's ‘socket.connect(address)’
     function being unable to establish connection in case of
     interrupted system call.  The problem was observed on all OSes
     which ‘poll(2)’ system call can take only non-negative integers and
     -1 as a timeout value.

   - bpo-37863(113): Optimizations for Fraction.__hash__ suggested by
     Tim Peters.

   - bpo-21131(114): Fix ‘faulthandler.register(chain=True)’ stack.
     faulthandler now allocates a dedicated stack of ‘SIGSTKSZ*2’ bytes,
     instead of just ‘SIGSTKSZ’ bytes.  Calling the previous signal
     handler in faulthandler signal handler uses more than ‘SIGSTKSZ’
     bytes of stack memory on some platforms.

   - bpo-37798(115): Add C fastpath for statistics.NormalDist.inv_cdf()
     Patch by Donghee Na

   - bpo-37804(116): Remove the deprecated method
     ‘threading.Thread.isAlive()’.  Patch by Donghee Na.

   - bpo-37819(117): Add Fraction.as_integer_ratio() to match the
     corresponding methods in bool, int, float, and decimal.

   - bpo-14465(118): Add an xml.etree.ElementTree.indent() function for
     pretty-printing XML trees.  Contributed by Stefan Behnel.

   - bpo-37810(119): Fix *note difflib: 2f. ‘?’ hint in diff output when
     dealing with tabs.  Patch by Anthony Sottile.

   - bpo-37772(120): In ‘zipfile.Path’, when adding implicit dirs,
     ensure that ancestral directories are added and that duplicates are
     excluded.

   - bpo-18578(121): Renamed and documented ‘test.bytecode_helper’ as
     ‘test.support.bytecode_helper’.  Patch by Joannah Nanjekye.

   - bpo-37785(122): Fix xgettext warnings in *note argparse: 5.

   - bpo-34488(123): ‘writelines()’ method of *note io.BytesIO: e46. is
     now slightly faster when many small lines are passed.  Patch by
     Sergey Fedoseev.

   - bpo-37449(124): ‘ensurepip’ now uses
     ‘importlib.resources.read_binary()’ to read data instead of
     ‘pkgutil.get_data()’.  Patch by Joannah Nanjekye.

   - bpo-28292(125): Mark calendar.py helper functions as being private.
     The follows PEP 8 guidance to maintain the style conventions in the
     module and it addresses a known case of user confusion.

   - bpo-18049(126): Add definition of THREAD_STACK_SIZE for AIX in
     Python/thread_pthread.h The default thread stacksize caused crashes
     with the default recursion limit Patch by M Felt

   - bpo-37742(127): The logging.getLogger() API now returns the root
     logger when passed the name 'root', whereas previously it returned
     a non-root logger named 'root'.  This could affect cases where user
     code explicitly wants a non-root logger named 'root', or
     instantiates a logger using logging.getLogger(__name__) in some
     top-level module called 'root.py'.

   - bpo-37738(128): Fix the implementation of curses ‘addch(str,
     color_pair)’: pass the color pair to ‘setcchar()’, instead of
     always passing 0 as the color pair.

   - bpo-37723(129): Fix performance regression on regular expression
     parsing with huge character sets.  Patch by Yann Vaginay.

   - bpo-35943(130): The function *note PyImport_GetModule(): b5a. now
     ensures any module it returns is fully initialized.  Patch by
     Joannah Nanjekye.

   - bpo-32178(131): Fix IndexError in *note email: 32. package when
     trying to parse invalid address fields starting with ‘:’.

   - bpo-37268(132): The ‘parser’ module is deprecated and will be
     removed in future versions of Python.

   - bpo-11953(133): Completing WSA* error codes in *note socket: b8.

   - bpo-37685(134): Fixed comparisons of *note datetime.timedelta: 973.
     and *note datetime.timezone: 1059.

   - bpo-37697(135): Synchronize ‘importlib.metadata’ with
     importlib_metadata 0.19(136), improving handling of EGG-INFO files
     and fixing a crash when entry point names contained colons.

   - bpo-37695(137): Correct *note curses.unget_wch(): 1039. error
     message.  Patch by Anthony Sottile.

   - bpo-37689(138): Add ‘is_relative_to()’ in ‘PurePath’ to determine
     whether or not one path is relative to another.

   - bpo-29553(139): Fixed *note argparse.ArgumentParser.format_usage():
     18d0. for mutually exclusive groups.  Patch by Andrew Nester.

   - bpo-37691(140): Let math.dist() accept coordinates as sequences (or
     iterables) rather than just tuples.

   - bpo-37685(141): Fixed ‘__eq__’, ‘__lt__’ etc implementations in
     some classes.  They now return *note NotImplemented: 776. for
     unsupported type of the other operand.  This allows the other
     operand to play role (for example the equality comparison with
     *note ANY: 18d1. will return ‘True’).

   - bpo-37354(142): Make Activate.ps1 Powershell script static to allow
     for signing it.

   - bpo-37664(143): Update wheels bundled with ensurepip (pip 19.2.3
     and setuptools 41.2.0)

   - bpo-37663(144): Bring consistency to venv shell activation scripts
     by always using __VENV_PROMPT__.

   - bpo-37642(145): Allowed the pure Python implementation of *note
     datetime.timezone: 1059. to represent sub-minute offsets close to
     minimum and maximum boundaries, specifically in the ranges (23:59,
     24:00) and (-23:59, 24:00).  Patch by Ngalim Siregar

   - bpo-36161(146): In *note posix: 9b, use ‘ttyname_r’ instead of
     ‘ttyname’ for thread safety.

   - bpo-36324(147): Make internal attributes for
     statistics.NormalDist() private.

   - bpo-37555(148): Fix ‘NonCallableMock._call_matcher’ returning tuple
     instead of ‘_Call’ object when ‘self._spec_signature’ exists.
     Patch by Elizabeth Uselton

   - bpo-29446(149): Make ‘from tkinter import *’ import only the
     expected objects.

   - bpo-16970(150): Adding a value error when an invalid value in
     passed to nargs Patch by Robert Leenders

   - bpo-34443(151): Exceptions from *note enum: 4c. now use the
     ‘__qualname’ of the enum class in the exception message instead of
     the ‘__name__’.

   - bpo-37491(152): Fix ‘IndexError’ when parsing email headers with
     unexpectedly ending bare-quoted string value.  Patch by Abhilash
     Raj.

   - bpo-37587(153): Make json.loads faster for long strings.  (Patch by
     Marco Paolini)

   - bpo-18378(154): Recognize "UTF-8" as a valid value for LC_CTYPE in
     locale._parse_localename.

   - bpo-37579(155): Return *note NotImplemented: 776. in Python
     implementation of ‘__eq__’ for *note timedelta: 973. and *note
     time: 1b2. when the other object being compared is not of the same
     type to match C implementation.  Patch by Karthikeyan Singaravelan.

   - bpo-21478(156): Record calls to parent when autospecced object is
     attached to a mock using ‘unittest.mock.attach_mock()’.  Patch by
     Karthikeyan Singaravelan.

   - bpo-37531(157): "python3 -m test -jN -timeout=TIMEOUT" now kills a
     worker process if it runs longer than 'TIMEOUT' seconds.

   - bpo-37482(158): Fix serialization of display name in originator or
     destination address fields with both encoded words and special
     chars.

   - bpo-36993(159): Improve error reporting for corrupt zip files with
     bad zip64 extra data.  Patch by Daniel Hillier.

   - bpo-37502(160): pickle.loads() no longer raises TypeError when the
     buffers argument is set to None

   - bpo-37520(161): Correct behavior for zipfile.Path.parent when the
     path object identifies a subdirectory.

   - bpo-18374(162): Fix the ‘.col_offset’ attribute of nested *note
     ast.BinOp: 18d2. instances which had a too large value in some
     situations.

   - bpo-37424(163): Fixes a possible hang when using a timeout on
     ‘subprocess.run()’ while capturing output.  If the child process
     spawned its own children or otherwise connected its stdout or
     stderr handles with another process, we could hang after the
     timeout was reached and our child was killed when attempting to
     read final output from the pipes.

   - bpo-37421(164): Fix ‘multiprocessing.util.get_temp_dir()’
     finalizer: clear also the 'tempdir' configuration of the current
     process, so next call to ‘get_temp_dir()’ will create a new
     temporary directory, rather than reusing the removed temporary
     directory.

   - bpo-37481(165): The distutils ‘bdist_wininst’ command is deprecated
     in Python 3.8, use ‘bdist_wheel’ (wheel packages) instead.

   - bpo-37479(166): When ‘Enum.__str__’ is overridden in a derived
     class, the override will be used by ‘Enum.__format__’ regardless of
     whether mixin classes are present.

   - bpo-37440(167): http.client now enables TLS 1.3 post-handshake
     authentication for default context or if a cert_file is passed to
     HTTPSConnection.

   - bpo-37437(168): Update vendorized expat version to 2.2.7.

   - bpo-37428(169): SSLContext.post_handshake_auth = True no longer
     sets SSL_VERIFY_POST_HANDSHAKE verify flag for client connections.
     Although the option is documented as ignored for clients, OpenSSL
     implicitly enables cert chain validation when the flag is set.

   - bpo-37420(170): *note os.sched_setaffinity(): 10a6. now correctly
     handles errors that arise during iteration over its ‘mask’
     argument.  Patch by Brandt Bucher.

   - bpo-37412(171): The *note os.getcwdb(): a34. function now uses the
     UTF-8 encoding on Windows, rather than the ANSI code page: see PEP
     529(172) for the rationale.  The function is no longer deprecated
     on Windows.

   - bpo-37406(173): The sqlite3 module now raises TypeError, rather
     than ValueError, if operation argument type is not str: execute(),
     executemany() and calling a connection.

   - bpo-29412(174): Fix IndexError in parsing a header value ending
     unexpectedly.  Patch by Abhilash Raj.

   - bpo-36546(175): The 'dist' argument for statistics.quantiles() is
     now positional only.  The current name doesn't reflect that the
     argument can be either a dataset or a distribution.  Marking the
     parameter as positional avoids confusion and makes it possible to
     change the name later.

   - bpo-37394(176): Fix a bug that was causing the *note queue: a4.
     module to fail if the accelerator module was not available.  Patch
     by Pablo Galindo.

   - bpo-37376(177): *note pprint: 9c. now has support for *note
     types.SimpleNamespace: 1b5.  Patch by Carl Bordum Hansen.

   - bpo-26967(178): An *note ArgumentParser: 4de. with
     ‘allow_abbrev=False’ no longer disables grouping of short flags,
     such as ‘-vv’, but only disables abbreviation of long flags as
     documented.  Patch by Zac Hatfield-Dodds.

   - bpo-37212(179): *note unittest.mock.call(): 18d3. now preserves the
     order of keyword arguments in repr output.  Patch by Karthikeyan
     Singaravelan.

   - bpo-37372(180): Fix error unpickling datetime.time objects from
     Python 2 with seconds>=24.  Patch by Justin Blanchard.

   - bpo-37345(181): Add formal support for UDPLITE sockets.  Support
     was present before, but it is now easier to detect support with
     ‘hasattr(socket, 'IPPROTO_UDPLITE')’ and there are constants
     defined for each of the values needed: ‘socket.IPPROTO_UDPLITE’,
     ‘UDPLITE_SEND_CSCOV’, and ‘UDPLITE_RECV_CSCOV’.  Patch by Gabe
     Appleton.

   - bpo-37358(182): Optimized ‘functools.partial’ by using vectorcall.

   - bpo-37347(183): *note sqlite3.Connection.create_aggregate(): 28a,
     *note sqlite3.Connection.create_function(): 289, *note
     sqlite3.Connection.set_authorizer(): 28b, *note
     sqlite3.Connection.set_progress_handler(): 28c. *note
     sqlite3.Connection.set_trace_callback(): 28d. methods lead to
     segfaults if some of these methods are called twice with an equal
     object but not the same.  Now callbacks are stored more carefully.
     Patch by Aleksandr Balezin.

   - bpo-37163(184): The 'obj' argument of *note dataclasses.replace():
     15f4. is positional-only now.

   - bpo-37085(185): Add the optional Linux SocketCAN Broadcast Manager
     constants, used as flags to configure the BCM behaviour, in the
     socket module.  Patch by Karl Ding.

   - bpo-37328(186): ‘HTMLParser.unescape’ is removed.  It was
     undocumented and deprecated since Python 3.4.

   - bpo-37305(187): Add .webmanifest -> application/manifest+json to
     list of recognized file types and content type headers

   - bpo-37320(188): ‘aifc.openfp()’ alias to ‘aifc.open()’,
     ‘sunau.openfp()’ alias to ‘sunau.open()’, and ‘wave.openfp()’ alias
     to ‘wave.open()’ have been removed.  They were deprecated since
     Python 3.7.

   - bpo-37315(189): Deprecated accepting floats with integral value
     (like ‘5.0’) in *note math.factorial(): 8eb.

   - bpo-37312(190): ‘_dummy_thread’ and ‘dummy_threading’ modules have
     been removed.  These modules were deprecated since Python 3.7 which
     requires threading support.

   - bpo-33972(191): Email with single part but content-type set to
     ‘multipart/*’ doesn't raise AttributeError anymore.

   - bpo-37280(192): Use threadpool for reading from file for sendfile
     fallback mode.

   - bpo-37279(193): Fix asyncio sendfile support when sendfile sends
     extra data in fallback mode.

   - bpo-19865(194): *note ctypes.create_unicode_buffer(): 18d4. now
     also supports non-BMP characters on platforms with 16-bit ‘wchar_t’
     (for example, Windows and AIX).

   - bpo-37266(195): In a subinterpreter, spawning a daemon thread now
     raises an exception.  Daemon threads were never supported in
     subinterpreters.  Previously, the subinterpreter finalization
     crashed with a Python fatal error if a daemon thread was still
     running.

   - bpo-37210(196): Allow pure Python implementation of *note pickle:
     95. to work even when the C ‘_pickle’ module is unavailable.

   - bpo-21872(197): Fix *note lzma: 7e.: module decompresses data
     incompletely.  When decompressing a FORMAT_ALONE format file, and
     it doesn't have the end marker, sometimes the last one to dozens
     bytes can't be output.  Patch by Ma Lin.

   - bpo-35922(198): Fix ‘RobotFileParser.crawl_delay()’ and
     ‘RobotFileParser.request_rate()’ to return ‘None’ rather than raise
     *note AttributeError: 2f6. when no relevant rule is defined in the
     robots.txt file.  Patch by Rémi Lapeyre.

   - bpo-35766(199): Change the format of feature_version to be a
     (major, minor) tuple.

   - bpo-36607(200): Eliminate *note RuntimeError: 179. raised by *note
     asyncio.all_tasks(): 8fa. if internal tasks weak set is changed by
     another thread during iteration.

   - bpo-18748(201): ‘_pyio.IOBase’ destructor now does nothing if
     getting the ‘closed’ attribute fails to better mimic ‘_io.IOBase’
     finalizer.

   - bpo-36402(202): Fix a race condition at Python shutdown when
     waiting for threads.  Wait until the Python thread state of all
     non-daemon threads get deleted (join all non-daemon threads),
     rather than just wait until non-daemon Python threads complete.

   - bpo-37206(203): Default values which cannot be represented as
     Python objects no longer improperly represented as ‘None’ in
     function signatures.

   - bpo-37111(204): Added ‘encoding’ and ‘errors’ keyword parameters to
     ‘logging.basicConfig’.

   - bpo-12144(205): Ensure cookies with ‘expires’ attribute are handled
     in ‘CookieJar.make_cookies()’.

   - bpo-34886(206): Fix an unintended ValueError from *note
     subprocess.run(): b2c. when checking for conflicting 'input' and
     'stdin' or 'capture_output' and 'stdout' or 'stderr' args when they
     were explicitly provided but with ‘None’ values within a passed in
     ‘**kwargs’ dict rather than as passed directly by name.  Patch
     contributed by Rémi Lapeyre.

   - bpo-37173(207): The exception message for ‘inspect.getfile()’ now
     correctly reports the passed class rather than the builtins module.

   - bpo-37178(208): Give math.perm() a one argument form that means the
     same as math.factorial().

   - bpo-37178(209): For math.perm(n, k), let k default to n, giving the
     same result as factorial.

   - bpo-37165(210): Converted _collections._count_elements to use the
     Argument Clinic.

   - bpo-34767(211): Do not always create a *note collections.deque:
     580. in *note asyncio.Lock: a14.

   - bpo-37158(212): Speed-up statistics.fmean() by switching from a
     function to a generator.

   - bpo-34282(213): Remove ‘Enum._convert’ method, deprecated in 3.8.

   - bpo-37150(214): ‘argparse._ActionsContainer.add_argument’ now
     throws error, if someone accidentally pass FileType class object
     instead of instance of FileType as ‘type’ argument.

   - bpo-28724(215): The socket module now has the *note
     socket.send_fds(): 8d7. and ‘socket.recv.fds()’ methods.
     Contributed by Joannah Nanjekye, Shinya Okano and Victor Stinner.

   - bpo-35621(216): Support running asyncio subprocesses when execution
     event loop in a thread on UNIX.

   - bpo-36520(217): Lengthy email headers with UTF-8 characters are now
     properly encoded when they are folded.  Patch by Jeffrey Kintscher.

   - bpo-30835(218): Fixed a bug in email parsing where a message with
     invalid bytes in content-transfer-encoding of a multipart message
     can cause an AttributeError.  Patch by Andrew Donnellan.

   - bpo-31163(219): pathlib.Path instance's rename and replace methods
     now return the new Path instance.

   - bpo-25068(220): *note urllib.request.ProxyHandler: 18d5. now
     lowercases the keys of the passed dictionary.

   - bpo-26185(221): Fix *note repr(): 7a1. on empty ‘ZipInfo’ object.
     Patch by Mickaël Schoentgen.

   - bpo-21315(222): Email headers containing RFC2047 encoded words are
     parsed despite the missing whitespace, and a defect registered.
     Also missing trailing whitespace after encoded words is now
     registered as a defect.

   - bpo-31904(223): Port test_datetime to VxWorks: skip zoneinfo tests
     on VxWorks

   - bpo-35805(224): Add parser for Message-ID header and add it to
     default HeaderRegistry.  This should prevent folding of Message-ID
     using RFC 2048 encoded words.

   - bpo-36871(225): Ensure method signature is used instead of
     constructor signature of a class while asserting mock object
     against method calls.  Patch by Karthikeyan Singaravelan.

   - bpo-35070(226): posix.getgrouplist() now works correctly when the
     user belongs to NGROUPS_MAX supplemental groups.  Patch by Jeffrey
     Kintscher.

   - bpo-31783(227): Fix race condition in ThreadPoolExecutor when
     worker threads are created during interpreter shutdown.

   - bpo-36582(228): Fix ‘UserString.encode()’ to correctly return
     ‘bytes’ rather than a ‘UserString’ instance.

   - bpo-32424(229): Deprecate xml.etree.ElementTree.Element.copy() in
     favor of copy.copy().

     Patch by Gordon P. Hemsley

   - bpo-36564(230): Fix infinite loop in email header folding logic
     that would be triggered when an email policy's max_line_length is
     not long enough to include the required markup and any values in
     the message.  Patch by Paul Ganssle

   - bpo-36543(231): Removed methods Element.getchildren(),
     Element.getiterator() and ElementTree.getiterator() and the
     xml.etree.cElementTree module.

   - bpo-36409(232): Remove the old plistlib API deprecated in Python
     3.4

   - bpo-36302(233): distutils sorts source file lists so that Extension
     .so files build more reproducibly by default

   - bpo-36250(234): Ignore ‘ValueError’ from ‘signal’ with
     ‘interaction’ in non-main thread.

   - bpo-36046(235): Added ‘user’, ‘group’ and ‘extra_groups’ parameters
     to the subprocess.Popen constructor.  Patch by Patrick McLean.

   - bpo-32627(236): Fix compile error when ‘_uuid’ headers conflicting
     included.

   - bpo-35800(237): Deprecate ‘smtpd.MailmanProxy’ ready for future
     removal.

   - bpo-35168(238): *note shlex.shlex.punctuation_chars: 18d6. is now a
     read-only property.

   - bpo-8538(239): Add support for boolean actions like ‘--foo’ and
     ‘--no-foo’ to argparse.  Patch contributed by Rémi Lapeyre.

   - bpo-20504(240): Fixes a bug in ‘cgi’ module when a
     multipart/form-data request has no ‘Content-Length’ header.

   - bpo-25988(241): The abstract base classes in *note collections.abc:
     17. no longer are exposed in the regular *note collections: 16.
     module.

   - bpo-11122(242): Distutils won't check for rpmbuild in specified
     paths only.

   - bpo-34775(243): Division handling of PurePath now returns
     NotImplemented instead of raising a TypeError when passed something
     other than an instance of str or PurePath.  Patch by Roger Aiudi.

   - bpo-34749(244): *note binascii.a2b_base64(): 1521. is now up to 2
     times faster.  Patch by Sergey Fedoseev.

   - bpo-34519(245): Add additional aliases for HP Roman 8.  Patch by
     Michael Osipov.

   - bpo-28009(246): Fix uuid.getnode() on platforms with '.'  as MAC
     Addr delimiter as well fix for MAC Addr format that omits a leading
     0 in MAC Addr values.  Currently, AIX is the only know platform
     with these settings.  Patch by Michael Felt.

   - bpo-30618(247): Add *note readlink(): 8c4.  Patch by Girts
     Folkmanis.

   - bpo-32498(248): Made *note urllib.parse.unquote(): 1689. accept
     bytes in addition to strings.  Patch by Stein Karlsen.

   - bpo-33348(249): lib2to3 now recognizes expressions after ‘*’ and
     ‘**’ like in ‘f(*[] or [])’.

   - bpo-32689(250): Update *note shutil.move(): 9ff. function to allow
     for Path objects to be used as source argument.  Patch by Emily
     Morehouse and Maxwell "5.13b" McKinnon.

   - bpo-32820(251): Added ‘__format__’ to IPv4 and IPv6 classes.
     Always outputs a fully zero-padded string.  Supports b/x/n
     modifiers (bin/hex/native format).  Native format for IPv4 is bin,
     native format for IPv6 is hex.  Also supports '#' and '_'
     modifiers.

   - bpo-27657(252): Fix urllib.parse.urlparse() with numeric paths.  A
     string like "path:80" is no longer parsed as a path but as a scheme
     ("path") and a path ("80").

   - bpo-4963(253): Fixed non-deterministic behavior related to
     mimetypes extension mapping and module reinitialization.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36589

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38807

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38724

   (4) https://bugs.python.org/issue?@action=redirect&bpo=38786

   (5) https://bugs.python.org/issue?@action=redirect&bpo=38785

   (6) https://bugs.python.org/issue?@action=redirect&bpo=38723

   (7) https://bugs.python.org/issue?@action=redirect&bpo=27805

   (8) https://bugs.python.org/issue?@action=redirect&bpo=38438

   (9) https://bugs.python.org/issue?@action=redirect&bpo=38761

   (10) https://bugs.python.org/issue?@action=redirect&bpo=38716

   (11) https://bugs.python.org/issue?@action=redirect&bpo=38713

   (12) https://bugs.python.org/issue?@action=redirect&bpo=38692

   (13) https://bugs.python.org/issue?@action=redirect&bpo=38692

   (14) https://bugs.python.org/issue?@action=redirect&bpo=38602

   (15) https://bugs.python.org/issue?@action=redirect&bpo=38334

   (16) https://bugs.python.org/issue?@action=redirect&bpo=38312

   (17) https://bugs.python.org/issue?@action=redirect&bpo=38586

   (18) https://bugs.python.org/issue?@action=redirect&bpo=38565

   (19) https://bugs.python.org/issue?@action=redirect&bpo=34679

   (20) https://bugs.python.org/issue?@action=redirect&bpo=31202

   (21) https://bugs.python.org/issue?@action=redirect&bpo=36321

   (22) https://bugs.python.org/issue?@action=redirect&bpo=38521

   (23) https://bugs.python.org/issue?@action=redirect&bpo=38493

   (24) https://bugs.python.org/issue?@action=redirect&bpo=38478

   (25) https://bugs.python.org/issue?@action=redirect&bpo=33604

   (26) https://bugs.python.org/issue?@action=redirect&bpo=38378

   (27) https://bugs.python.org/issue?@action=redirect&bpo=38417

   (28) https://bugs.python.org/issue?@action=redirect&bpo=38449

   (29) https://bugs.python.org/issue?@action=redirect&bpo=38431

   (30) https://bugs.python.org/issue?@action=redirect&bpo=38109

   (31) https://bugs.python.org/issue?@action=redirect&bpo=38422

   (32) https://bugs.python.org/issue?@action=redirect&bpo=38405

   (33) https://bugs.python.org/issue?@action=redirect&bpo=38332

   (34) https://bugs.python.org/issue?@action=redirect&bpo=38371

   (35) https://bugs.python.org/issue?@action=redirect&bpo=38341

   (36) https://bugs.python.org/issue?@action=redirect&bpo=38319

   (37) https://bugs.python.org/issue?@action=redirect&bpo=38242

   (38) https://bugs.python.org/issue?@action=redirect&bpo=13153

   (39) https://bugs.python.org/issue?@action=redirect&bpo=38019

   (40) https://bugs.python.org/issue?@action=redirect&bpo=38163

   (41) https://bugs.python.org/issue?@action=redirect&bpo=38161

   (42) https://bugs.python.org/issue?@action=redirect&bpo=38216

   (43) https://bugs.python.org/issue?@action=redirect&bpo=30458

   (44) https://bugs.python.org/issue?@action=redirect&bpo=28286

   (45) https://bugs.python.org/issue?@action=redirect&bpo=38108

   (46) https://bugs.python.org/issue?@action=redirect&bpo=38265

   (47) https://bugs.python.org/issue?@action=redirect&bpo=38112

   (48) https://bugs.python.org/issue?@action=redirect&bpo=38248

   (49) https://bugs.python.org/issue?@action=redirect&bpo=38237

   (50) https://bugs.python.org/issue?@action=redirect&bpo=34002

   (51) https://bugs.python.org/issue?@action=redirect&bpo=38191

   (52) https://bugs.python.org/issue?@action=redirect&bpo=38155

   (53) https://bugs.python.org/issue?@action=redirect&bpo=38185

   (54) https://bugs.python.org/issue?@action=redirect&bpo=38136

   (55) https://bugs.python.org/issue?@action=redirect&bpo=37828

   (56) https://bugs.python.org/issue?@action=redirect&bpo=38175

   (57) https://bugs.python.org/issue?@action=redirect&bpo=33936

   (58) https://bugs.python.org/issue?@action=redirect&bpo=34706

   (59) https://bugs.python.org/issue?@action=redirect&bpo=38153

   (60) https://bugs.python.org/issue?@action=redirect&bpo=38115

   (61) https://bugs.python.org/issue?@action=redirect&bpo=38148

   (62) https://bugs.python.org/issue?@action=redirect&bpo=38142

   (63) https://bugs.python.org/issue?@action=redirect&bpo=9216

   (64) https://bugs.python.org/issue?@action=redirect&bpo=36991

   (65) https://bugs.python.org/issue?@action=redirect&bpo=38134

   (66) https://bugs.python.org/issue?@action=redirect&bpo=38132

   (67) https://bugs.python.org/issue?@action=redirect&bpo=38008

   (68) https://bugs.python.org/issue?@action=redirect&bpo=34037

   (69) https://bugs.python.org/issue?@action=redirect&bpo=37405

   (70) https://bugs.python.org/issue?@action=redirect&bpo=38121

   (71) https://bugs.python.org/issue?@action=redirect&bpo=38110

   (72) https://bugs.python.org/issue?@action=redirect&bpo=38093

   (73) https://bugs.python.org/issue?@action=redirect&bpo=37488

   (74) https://bugs.python.org/issue?@action=redirect&bpo=35640

   (75) https://bugs.python.org/issue?@action=redirect&bpo=38086

   (76) 
https://gitlab.com/python-devs/importlib_metadata/blob/0.21/importlib_metadata/docs/changelog.rst

   (77) https://bugs.python.org/issue?@action=redirect&bpo=37251

   (78) https://bugs.python.org/issue?@action=redirect&bpo=38037

   (79) https://bugs.python.org/issue?@action=redirect&bpo=38066

   (80) https://bugs.python.org/issue?@action=redirect&bpo=38059

   (81) https://bugs.python.org/issue?@action=redirect&bpo=38049

   (82) https://bugs.python.org/issue?@action=redirect&bpo=37953

   (83) https://bugs.python.org/issue?@action=redirect&bpo=38026

   (84) https://bugs.python.org/issue?@action=redirect&bpo=35923

   (85) https://bugs.python.org/issue?@action=redirect&bpo=38010

   (86) https://bugs.python.org/issue?@action=redirect&bpo=38006

   (87) https://bugs.python.org/issue?@action=redirect&bpo=37995

   (88) https://bugs.python.org/issue?@action=redirect&bpo=34410

   (89) https://bugs.python.org/issue?@action=redirect&bpo=37140

   (90) https://bugs.python.org/issue?@action=redirect&bpo=37587

   (91) https://bugs.python.org/issue?@action=redirect&bpo=37834

   (92) https://bugs.python.org/issue?@action=redirect&bpo=10978

   (93) https://bugs.python.org/issue?@action=redirect&bpo=37972

   (94) https://bugs.python.org/issue?@action=redirect&bpo=37965

   (95) https://bugs.python.org/issue?@action=redirect&bpo=37964

   (96) https://bugs.python.org/issue?@action=redirect&bpo=37960

   (97) https://bugs.python.org/issue?@action=redirect&bpo=37961

   (98) https://bugs.python.org/issue?@action=redirect&bpo=37951

   (99) https://bugs.python.org/issue?@action=redirect&bpo=36205

   (100) https://bugs.python.org/issue?@action=redirect&bpo=37950

   (101) https://bugs.python.org/issue?@action=redirect&bpo=34679

   (102) https://bugs.python.org/issue?@action=redirect&bpo=36917

   (103) https://bugs.python.org/issue?@action=redirect&bpo=37798

   (104) https://bugs.python.org/issue?@action=redirect&bpo=26589

   (105) https://bugs.python.org/issue?@action=redirect&bpo=37915

   (106) https://bugs.python.org/issue?@action=redirect&bpo=32554

   (107) https://bugs.python.org/issue?@action=redirect&bpo=9938

   (108) https://bugs.python.org/issue?@action=redirect&bpo=37851

   (109) https://bugs.python.org/issue?@action=redirect&bpo=32793

   (110) https://bugs.python.org/issue?@action=redirect&bpo=37885

   (111) https://bugs.python.org/issue?@action=redirect&bpo=37868

   (112) https://bugs.python.org/issue?@action=redirect&bpo=37811

   (113) https://bugs.python.org/issue?@action=redirect&bpo=37863

   (114) https://bugs.python.org/issue?@action=redirect&bpo=21131

   (115) https://bugs.python.org/issue?@action=redirect&bpo=37798

   (116) https://bugs.python.org/issue?@action=redirect&bpo=37804

   (117) https://bugs.python.org/issue?@action=redirect&bpo=37819

   (118) https://bugs.python.org/issue?@action=redirect&bpo=14465

   (119) https://bugs.python.org/issue?@action=redirect&bpo=37810

   (120) https://bugs.python.org/issue?@action=redirect&bpo=37772

   (121) https://bugs.python.org/issue?@action=redirect&bpo=18578

   (122) https://bugs.python.org/issue?@action=redirect&bpo=37785

   (123) https://bugs.python.org/issue?@action=redirect&bpo=34488

   (124) https://bugs.python.org/issue?@action=redirect&bpo=37449

   (125) https://bugs.python.org/issue?@action=redirect&bpo=28292

   (126) https://bugs.python.org/issue?@action=redirect&bpo=18049

   (127) https://bugs.python.org/issue?@action=redirect&bpo=37742

   (128) https://bugs.python.org/issue?@action=redirect&bpo=37738

   (129) https://bugs.python.org/issue?@action=redirect&bpo=37723

   (130) https://bugs.python.org/issue?@action=redirect&bpo=35943

   (131) https://bugs.python.org/issue?@action=redirect&bpo=32178

   (132) https://bugs.python.org/issue?@action=redirect&bpo=37268

   (133) https://bugs.python.org/issue?@action=redirect&bpo=11953

   (134) https://bugs.python.org/issue?@action=redirect&bpo=37685

   (135) https://bugs.python.org/issue?@action=redirect&bpo=37697

   (136) 
https://gitlab.com/python-devs/importlib_metadata/-/milestones/20

   (137) https://bugs.python.org/issue?@action=redirect&bpo=37695

   (138) https://bugs.python.org/issue?@action=redirect&bpo=37689

   (139) https://bugs.python.org/issue?@action=redirect&bpo=29553

   (140) https://bugs.python.org/issue?@action=redirect&bpo=37691

   (141) https://bugs.python.org/issue?@action=redirect&bpo=37685

   (142) https://bugs.python.org/issue?@action=redirect&bpo=37354

   (143) https://bugs.python.org/issue?@action=redirect&bpo=37664

   (144) https://bugs.python.org/issue?@action=redirect&bpo=37663

   (145) https://bugs.python.org/issue?@action=redirect&bpo=37642

   (146) https://bugs.python.org/issue?@action=redirect&bpo=36161

   (147) https://bugs.python.org/issue?@action=redirect&bpo=36324

   (148) https://bugs.python.org/issue?@action=redirect&bpo=37555

   (149) https://bugs.python.org/issue?@action=redirect&bpo=29446

   (150) https://bugs.python.org/issue?@action=redirect&bpo=16970

   (151) https://bugs.python.org/issue?@action=redirect&bpo=34443

   (152) https://bugs.python.org/issue?@action=redirect&bpo=37491

   (153) https://bugs.python.org/issue?@action=redirect&bpo=37587

   (154) https://bugs.python.org/issue?@action=redirect&bpo=18378

   (155) https://bugs.python.org/issue?@action=redirect&bpo=37579

   (156) https://bugs.python.org/issue?@action=redirect&bpo=21478

   (157) https://bugs.python.org/issue?@action=redirect&bpo=37531

   (158) https://bugs.python.org/issue?@action=redirect&bpo=37482

   (159) https://bugs.python.org/issue?@action=redirect&bpo=36993

   (160) https://bugs.python.org/issue?@action=redirect&bpo=37502

   (161) https://bugs.python.org/issue?@action=redirect&bpo=37520

   (162) https://bugs.python.org/issue?@action=redirect&bpo=18374

   (163) https://bugs.python.org/issue?@action=redirect&bpo=37424

   (164) https://bugs.python.org/issue?@action=redirect&bpo=37421

   (165) https://bugs.python.org/issue?@action=redirect&bpo=37481

   (166) https://bugs.python.org/issue?@action=redirect&bpo=37479

   (167) https://bugs.python.org/issue?@action=redirect&bpo=37440

   (168) https://bugs.python.org/issue?@action=redirect&bpo=37437

   (169) https://bugs.python.org/issue?@action=redirect&bpo=37428

   (170) https://bugs.python.org/issue?@action=redirect&bpo=37420

   (171) https://bugs.python.org/issue?@action=redirect&bpo=37412

   (172) https://peps.python.org/pep-0529/

   (173) https://bugs.python.org/issue?@action=redirect&bpo=37406

   (174) https://bugs.python.org/issue?@action=redirect&bpo=29412

   (175) https://bugs.python.org/issue?@action=redirect&bpo=36546

   (176) https://bugs.python.org/issue?@action=redirect&bpo=37394

   (177) https://bugs.python.org/issue?@action=redirect&bpo=37376

   (178) https://bugs.python.org/issue?@action=redirect&bpo=26967

   (179) https://bugs.python.org/issue?@action=redirect&bpo=37212

   (180) https://bugs.python.org/issue?@action=redirect&bpo=37372

   (181) https://bugs.python.org/issue?@action=redirect&bpo=37345

   (182) https://bugs.python.org/issue?@action=redirect&bpo=37358

   (183) https://bugs.python.org/issue?@action=redirect&bpo=37347

   (184) https://bugs.python.org/issue?@action=redirect&bpo=37163

   (185) https://bugs.python.org/issue?@action=redirect&bpo=37085

   (186) https://bugs.python.org/issue?@action=redirect&bpo=37328

   (187) https://bugs.python.org/issue?@action=redirect&bpo=37305

   (188) https://bugs.python.org/issue?@action=redirect&bpo=37320

   (189) https://bugs.python.org/issue?@action=redirect&bpo=37315

   (190) https://bugs.python.org/issue?@action=redirect&bpo=37312

   (191) https://bugs.python.org/issue?@action=redirect&bpo=33972

   (192) https://bugs.python.org/issue?@action=redirect&bpo=37280

   (193) https://bugs.python.org/issue?@action=redirect&bpo=37279

   (194) https://bugs.python.org/issue?@action=redirect&bpo=19865

   (195) https://bugs.python.org/issue?@action=redirect&bpo=37266

   (196) https://bugs.python.org/issue?@action=redirect&bpo=37210

   (197) https://bugs.python.org/issue?@action=redirect&bpo=21872

   (198) https://bugs.python.org/issue?@action=redirect&bpo=35922

   (199) https://bugs.python.org/issue?@action=redirect&bpo=35766

   (200) https://bugs.python.org/issue?@action=redirect&bpo=36607

   (201) https://bugs.python.org/issue?@action=redirect&bpo=18748

   (202) https://bugs.python.org/issue?@action=redirect&bpo=36402

   (203) https://bugs.python.org/issue?@action=redirect&bpo=37206

   (204) https://bugs.python.org/issue?@action=redirect&bpo=37111

   (205) https://bugs.python.org/issue?@action=redirect&bpo=12144

   (206) https://bugs.python.org/issue?@action=redirect&bpo=34886

   (207) https://bugs.python.org/issue?@action=redirect&bpo=37173

   (208) https://bugs.python.org/issue?@action=redirect&bpo=37178

   (209) https://bugs.python.org/issue?@action=redirect&bpo=37178

   (210) https://bugs.python.org/issue?@action=redirect&bpo=37165

   (211) https://bugs.python.org/issue?@action=redirect&bpo=34767

   (212) https://bugs.python.org/issue?@action=redirect&bpo=37158

   (213) https://bugs.python.org/issue?@action=redirect&bpo=34282

   (214) https://bugs.python.org/issue?@action=redirect&bpo=37150

   (215) https://bugs.python.org/issue?@action=redirect&bpo=28724

   (216) https://bugs.python.org/issue?@action=redirect&bpo=35621

   (217) https://bugs.python.org/issue?@action=redirect&bpo=36520

   (218) https://bugs.python.org/issue?@action=redirect&bpo=30835

   (219) https://bugs.python.org/issue?@action=redirect&bpo=31163

   (220) https://bugs.python.org/issue?@action=redirect&bpo=25068

   (221) https://bugs.python.org/issue?@action=redirect&bpo=26185

   (222) https://bugs.python.org/issue?@action=redirect&bpo=21315

   (223) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (224) https://bugs.python.org/issue?@action=redirect&bpo=35805

   (225) https://bugs.python.org/issue?@action=redirect&bpo=36871

   (226) https://bugs.python.org/issue?@action=redirect&bpo=35070

   (227) https://bugs.python.org/issue?@action=redirect&bpo=31783

   (228) https://bugs.python.org/issue?@action=redirect&bpo=36582

   (229) https://bugs.python.org/issue?@action=redirect&bpo=32424

   (230) https://bugs.python.org/issue?@action=redirect&bpo=36564

   (231) https://bugs.python.org/issue?@action=redirect&bpo=36543

   (232) https://bugs.python.org/issue?@action=redirect&bpo=36409

   (233) https://bugs.python.org/issue?@action=redirect&bpo=36302

   (234) https://bugs.python.org/issue?@action=redirect&bpo=36250

   (235) https://bugs.python.org/issue?@action=redirect&bpo=36046

   (236) https://bugs.python.org/issue?@action=redirect&bpo=32627

   (237) https://bugs.python.org/issue?@action=redirect&bpo=35800

   (238) https://bugs.python.org/issue?@action=redirect&bpo=35168

   (239) https://bugs.python.org/issue?@action=redirect&bpo=8538

   (240) https://bugs.python.org/issue?@action=redirect&bpo=20504

   (241) https://bugs.python.org/issue?@action=redirect&bpo=25988

   (242) https://bugs.python.org/issue?@action=redirect&bpo=11122

   (243) https://bugs.python.org/issue?@action=redirect&bpo=34775

   (244) https://bugs.python.org/issue?@action=redirect&bpo=34749

   (245) https://bugs.python.org/issue?@action=redirect&bpo=34519

   (246) https://bugs.python.org/issue?@action=redirect&bpo=28009

   (247) https://bugs.python.org/issue?@action=redirect&bpo=30618

   (248) https://bugs.python.org/issue?@action=redirect&bpo=32498

   (249) https://bugs.python.org/issue?@action=redirect&bpo=33348

   (250) https://bugs.python.org/issue?@action=redirect&bpo=32689

   (251) https://bugs.python.org/issue?@action=redirect&bpo=32820

   (252) https://bugs.python.org/issue?@action=redirect&bpo=27657

   (253) https://bugs.python.org/issue?@action=redirect&bpo=4963


File: python.info,  Node: Documentation<38>,  Next: Tests<40>,  Prev: Library<43>,  Up: Python 3 9 0 alpha 1

1.23.44.4 Documentation
.......................

   - bpo-21767(1): Explicitly mention abc support in
     functools.singledispatch

   - bpo-38816(2): Provides more details about the interaction between
     ‘fork()’ and CPython's runtime, focusing just on the C-API. This
     includes cautions about where ‘fork()’ should and shouldn't be
     called.

   - bpo-38351(3): Modernize *note email: 32. examples from %-formatting
     to f-strings.

   - bpo-38778(4): Document the fact that *note RuntimeError: 179. is
     raised if *note os.fork(): 17b. is called in a subinterpreter.

   - bpo-38592(5): Add Brazilian Portuguese to the language switcher at
     Python Documentation website.

   - bpo-38294(6): Add list of no-longer-escaped chars to re.escape
     documentation

   - bpo-38053(7): Modernized the plistlib documentation

   - bpo-26868(8): Fix example usage of *note PyModule_AddObject(): 309.
     to properly handle errors.

   - bpo-36797(9): Fix a dead link in the distutils API Reference.

   - bpo-37977(10): Warn more strongly and clearly about pickle
     insecurity

   - bpo-37979(11): Added a link to dateutil.parser.isoparse in the
     datetime.fromisoformat documentation.  Patch by Paul Ganssle

   - bpo-12707(12): Deprecate info(), geturl(), getcode() methods in
     favor of the headers, url, and status properties, respectively, for
     HTTPResponse and addinfourl.  Also deprecate the code attribute of
     addinfourl in favor of the status attribute.  Patch by Ashwin
     Ramaswami

   - bpo-37937(13): Mention ‘frame.f_trace’ in *note sys.settrace():
     146e. docs.

   - bpo-37878(14): Make *note PyThreadState_DeleteCurrent(): 18d8.
     Internal.

   - bpo-37759(15): Beginning edits to Whatsnew 3.8

   - bpo-37726(16): Stop recommending getopt in the tutorial for command
     line argument parsing and promote argparse.

   - bpo-32910(17): Remove implementation-specific behaviour of how
     venv's Deactivate works.

   - bpo-37256(18): Fix wording of arguments for ‘Request’ in *note
     urllib.request: f4.

   - bpo-37284(19): Add a brief note to indicate that any new
     ‘sys.implementation’ required attributes must go through the PEP
     process.

   - bpo-30088(20): Documented that *note mailbox.Maildir: 353.
     constructor doesn't attempt to verify the maildir folder layout
     correctness.  Patch by Sviatoslav Sydorenko.

   - bpo-37521(21): Fix ‘importlib’ examples to insert any newly created
     modules via importlib.util.module_from_spec() immediately into
     sys.modules instead of after calling loader.exec_module().

     Thanks to Benjamin Mintz for finding the bug.

   - bpo-37456(22): Slash ('/') is now part of syntax.

   - bpo-37487(23): Fix PyList_GetItem index description to include 0.

   - bpo-37149(24): Replace the dead link to the Tkinter 8.5 reference
     by John Shipman, New Mexico Tech, with a link to the archive.org
     copy.

   - bpo-37478(25): Added possible exceptions to the description of
     os.chdir().

   - bpo-34903(26): Documented that in *note
     datetime.datetime.strptime(): 14fe, the leading zero in some
     two-digit formats is optional.  Patch by Mike Gleen.

   - bpo-36260(27): Add decompression pitfalls to zipfile module
     documentation.

   - bpo-37004(28): In the documentation for difflib, a note was added
     explicitly warning that the results of SequenceMatcher's ratio
     method may depend on the order of the input strings.

   - bpo-36960(29): Restructured the *note datetime: 28. docs in the
     interest of making them more user-friendly and improving
     readability.  Patch by Brad Solomon.

   - bpo-36487(30): Make C-API docs clear about what the "main"
     interpreter is.

   - bpo-23460(31): The documentation for decimal string formatting
     using the ‘:g’ specifier has been updated to reflect the correct
     exponential notation cutoff point.  Original patch contributed by
     Tuomas Suutari.

   - bpo-35803(32): Document and test that ‘tempfile’ functions may
     accept a *note path-like object: ac2. for the ‘dir’ argument.
     Patch by Anthony Sottile.

   - bpo-33944(33): Added a note about the intended use of code in .pth
     files.

   - bpo-34293(34): Fix the Doc/Makefile regarding PAPER environment
     variable and PDF builds

   - bpo-25237(35): Add documentation for tkinter modules

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21767

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38816

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38351

   (4) https://bugs.python.org/issue?@action=redirect&bpo=38778

   (5) https://bugs.python.org/issue?@action=redirect&bpo=38592

   (6) https://bugs.python.org/issue?@action=redirect&bpo=38294

   (7) https://bugs.python.org/issue?@action=redirect&bpo=38053

   (8) https://bugs.python.org/issue?@action=redirect&bpo=26868

   (9) https://bugs.python.org/issue?@action=redirect&bpo=36797

   (10) https://bugs.python.org/issue?@action=redirect&bpo=37977

   (11) https://bugs.python.org/issue?@action=redirect&bpo=37979

   (12) https://bugs.python.org/issue?@action=redirect&bpo=12707

   (13) https://bugs.python.org/issue?@action=redirect&bpo=37937

   (14) https://bugs.python.org/issue?@action=redirect&bpo=37878

   (15) https://bugs.python.org/issue?@action=redirect&bpo=37759

   (16) https://bugs.python.org/issue?@action=redirect&bpo=37726

   (17) https://bugs.python.org/issue?@action=redirect&bpo=32910

   (18) https://bugs.python.org/issue?@action=redirect&bpo=37256

   (19) https://bugs.python.org/issue?@action=redirect&bpo=37284

   (20) https://bugs.python.org/issue?@action=redirect&bpo=30088

   (21) https://bugs.python.org/issue?@action=redirect&bpo=37521

   (22) https://bugs.python.org/issue?@action=redirect&bpo=37456

   (23) https://bugs.python.org/issue?@action=redirect&bpo=37487

   (24) https://bugs.python.org/issue?@action=redirect&bpo=37149

   (25) https://bugs.python.org/issue?@action=redirect&bpo=37478

   (26) https://bugs.python.org/issue?@action=redirect&bpo=34903

   (27) https://bugs.python.org/issue?@action=redirect&bpo=36260

   (28) https://bugs.python.org/issue?@action=redirect&bpo=37004

   (29) https://bugs.python.org/issue?@action=redirect&bpo=36960

   (30) https://bugs.python.org/issue?@action=redirect&bpo=36487

   (31) https://bugs.python.org/issue?@action=redirect&bpo=23460

   (32) https://bugs.python.org/issue?@action=redirect&bpo=35803

   (33) https://bugs.python.org/issue?@action=redirect&bpo=33944

   (34) https://bugs.python.org/issue?@action=redirect&bpo=34293

   (35) https://bugs.python.org/issue?@action=redirect&bpo=25237


File: python.info,  Node: Tests<40>,  Next: Build<43>,  Prev: Documentation<38>,  Up: Python 3 9 0 alpha 1

1.23.44.5 Tests
...............

   - bpo-38614(1): Fix test_communicate() of
     test_asyncio.test_subprocess: use ‘support.LONG_TIMEOUT’ (5
     minutes), instead of just 1 minute.

   - bpo-38614(2): Add timeout constants to *note test.support: cd.:
     *note LOOPBACK_TIMEOUT: 18b8, *note INTERNET_TIMEOUT: 18b9, *note
     SHORT_TIMEOUT: 17b1. and *note LONG_TIMEOUT: 18ba.

   - bpo-38502(3): test.regrtest now uses process groups in the
     multiprocessing mode (-jN command line option) if process groups
     are available: if *note os.setsid(): 18da. and *note os.killpg():
     18db. functions are available.

   - bpo-35998(4): Fix a race condition in
     test_asyncio.test_start_tls_server_1().  Previously, there was a
     race condition between the test main() function which replaces the
     protocol and the test ServerProto protocol which sends ANSWER once
     it gets HELLO. Now, only the test main() function is responsible to
     send data, ServerProto no longer sends data.

   - bpo-38470(5): Fix ‘test_compileall.test_compile_dir_maxlevels()’ on
     Windows without long path support: only create 3 subdirectories
     instead of between 20 and 100 subdirectories.

   - bpo-37531(6): On timeout, regrtest no longer attempts to call
     ‘popen.communicate()’ again: it can hang until all child processes
     using stdout and stderr pipes completes.  Kill the worker process
     and ignores its output.  Change also the faulthandler timeout of
     the main process from 1 minute to 5 minutes, for Python slowest
     buildbots.

   - bpo-38239(7): Fix test_gdb for Link Time Optimization (LTO) builds.

   - bpo-38275(8): test_ssl now handles disabled TLS/SSL versions
     better.  OpenSSL's crypto policy and run-time settings are
     recognized and tests for disabled versions are skipped.  Tests also
     accept more TLS minimum_versions for platforms that override
     OpenSSL's default with strict settings.

   - bpo-38271(9): The private keys for test_ssl were encrypted with
     3DES in traditional PKCS#5 format.  3DES and the digest algorithm
     of PKCS#5 are blocked by some strict crypto policies.  Use PKCS#8
     format with AES256 encryption instead.

   - bpo-38270(10): test.support now has a helper function to check for
     availability of a hash digest function.  Several tests are
     refactored avoid MD5 and use SHA256 instead.  Other tests are
     marked to use MD5 and skipped when MD5 is disabled.

   - bpo-37123(11): Multiprocessing test test_mymanager() now also
     expects -SIGTERM, not only exitcode 0.
     BaseManager._finalize_manager() sends SIGTERM to the manager
     process if it takes longer than 1 second to stop, which happens on
     slow buildbots.

   - bpo-38212(12): Multiprocessing tests: increase
     test_queue_feeder_donot_stop_onexc() timeout from 1 to 60 seconds.

   - bpo-38117(13): Test with OpenSSL 1.1.1d

   - bpo-38018(14): Increase code coverage for
     multiprocessing.shared_memory.

   - bpo-37805(15): Add tests for json.dump(..., skipkeys=True).  Patch
     by Donghee Na.

   - bpo-37531(16): Enhance regrtest multiprocess timeout: write a
     message when killing a worker process, catch popen.kill() and
     popen.wait() exceptions, put a timeout on the second call to
     popen.communicate().

   - bpo-37876(17): Add tests for ROT-13 codec.

   - bpo-36833(18): Added tests for ‘PyDateTime_XXX_GET_XXX()’ macros of
     the C API of the *note datetime: 28. module.  Patch by Joannah
     Nanjekye.

   - bpo-37558(19): Fix
     test_shared_memory_cleaned_after_process_termination name handling

   - bpo-37526(20): Add ‘test.support.catch_threading_exception()’:
     context manager catching *note threading.Thread: 8f0. exception
     using *note threading.excepthook(): 7ef.

   - bpo-37421(21): test_concurrent_futures now explicitly stops the
     ForkServer instance if it's running.

   - bpo-37421(22): multiprocessing tests now stop the ForkServer
     instance if it's running: close the "alive" file descriptor to ask
     the server to stop and then remove its UNIX address.

   - bpo-37421(23): test_distutils.test_build_ext() is now able to
     remove the temporary directory on Windows: don't import the newly
     built C extension ("xx") in the current process, but test it in a
     separated process.

   - bpo-37421(24): test_concurrent_futures now cleans up
     multiprocessing to remove immediately temporary directories created
     by multiprocessing.util.get_temp_dir().

   - bpo-37421(25): test_winconsoleio doesn't leak a temporary file
     anymore: use tempfile.TemporaryFile() to remove it when the test
     completes.

   - bpo-37421(26): multiprocessing tests now explicitly call
     ‘_run_finalizers()’ to immediately remove temporary directories
     created by tests.

   - bpo-37421(27): urllib.request tests now call *note urlcleanup():
     18dc. to remove temporary files created by ‘urlretrieve()’ tests
     and to clear the ‘_opener’ global variable set by ‘urlopen()’ and
     functions calling indirectly ‘urlopen()’.

   - bpo-37472(28): Remove ‘Lib/test/outstanding_bugs.py’.

   - bpo-37199(29): Fix test failures when IPv6 is unavailable or
     disabled.

   - bpo-19696(30): Replace deprecated method "random.choose" with
     "random.choice" in "test_pkg_import.py".

   - bpo-37335(31): Remove no longer necessary code from c locale
     coercion tests

   - bpo-37421(32): Fix test_shutil to no longer leak temporary files.

   - bpo-37411(33): Fix test_wsgiref.testEnviron() to no longer depend
     on the environment variables (don't fail if "X" variable is set).

   - bpo-37400(34): Fix test_os.test_chown(): use os.getgroups() rather
     than grp.getgrall() to get groups.  Rename also the test to
     test_chown_gid().

   - bpo-37359(35): Add -cleanup option to python3 -m test to remove
     ‘test_python_*’ directories of previous failed jobs.  Add "make
     cleantest" to run ‘python3 -m test --cleanup’.

   - bpo-37362(36): test_gdb no longer fails if it gets an "unexpected"
     message on stderr: it now ignores stderr.  The purpose of test_gdb
     is to test that python-gdb.py commands work as expected, not to
     test gdb.

   - bpo-35998(37): Avoid TimeoutError in test_asyncio:
     test_start_tls_server_1()

   - bpo-37278(38): Fix test_asyncio ProactorLoopCtrlC: join the thread
     to prevent leaking a running thread and leaking a reference.

   - bpo-37261(39): Fix *note test.support.catch_unraisable_exception():
     18dd.: its __exit__() method now ignores unraisable exception
     raised when clearing its ‘unraisable’ attribute.

   - bpo-37069(40): regrtest now uses *note sys.unraisablehook(): 1dc.
     to mark a test as "environment altered" (ENV_CHANGED) if it emits
     an "unraisable exception".  Moreover, regrtest logs a warning in
     this case.

     Use ‘python3 -m test --fail-env-changed’ to catch unraisable
     exceptions in tests.

   - bpo-37252(41): Fix assertions in ‘test_close’ and
     ‘test_events_mask_overflow’ devpoll tests.

   - bpo-37169(42): Rewrite ‘_PyObject_IsFreed()’ unit tests.

   - bpo-37153(43): ‘test_venv.test_multiprocessing()’ now explicitly
     calls ‘pool.terminate()’ to wait until the pool completes.

   - bpo-34001(44): Make test_ssl pass with LibreSSL. LibreSSL handles
     minimum and maximum TLS version differently than OpenSSL.

   - bpo-36919(45): Make ‘test_source_encoding.test_issue2301’
     implementation independent.  The test will work now for both
     CPython and IronPython.

   - bpo-30202(46): Update ‘test.test_importlib.test_abc’ to test
     ‘find_spec()’.

   - bpo-28009(47): Modify the test_uuid logic to test when a program is
     available AND can be used to obtain a MACADDR as basis for an UUID.
     Patch by M. Felt

   - bpo-34596(48): Fallback to a default reason when *note
     unittest.skip(): 18de. is uncalled.  Patch by Naitree Zhu.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38614

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38614

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38502

   (4) https://bugs.python.org/issue?@action=redirect&bpo=35998

   (5) https://bugs.python.org/issue?@action=redirect&bpo=38470

   (6) https://bugs.python.org/issue?@action=redirect&bpo=37531

   (7) https://bugs.python.org/issue?@action=redirect&bpo=38239

   (8) https://bugs.python.org/issue?@action=redirect&bpo=38275

   (9) https://bugs.python.org/issue?@action=redirect&bpo=38271

   (10) https://bugs.python.org/issue?@action=redirect&bpo=38270

   (11) https://bugs.python.org/issue?@action=redirect&bpo=37123

   (12) https://bugs.python.org/issue?@action=redirect&bpo=38212

   (13) https://bugs.python.org/issue?@action=redirect&bpo=38117

   (14) https://bugs.python.org/issue?@action=redirect&bpo=38018

   (15) https://bugs.python.org/issue?@action=redirect&bpo=37805

   (16) https://bugs.python.org/issue?@action=redirect&bpo=37531

   (17) https://bugs.python.org/issue?@action=redirect&bpo=37876

   (18) https://bugs.python.org/issue?@action=redirect&bpo=36833

   (19) https://bugs.python.org/issue?@action=redirect&bpo=37558

   (20) https://bugs.python.org/issue?@action=redirect&bpo=37526

   (21) https://bugs.python.org/issue?@action=redirect&bpo=37421

   (22) https://bugs.python.org/issue?@action=redirect&bpo=37421

   (23) https://bugs.python.org/issue?@action=redirect&bpo=37421

   (24) https://bugs.python.org/issue?@action=redirect&bpo=37421

   (25) https://bugs.python.org/issue?@action=redirect&bpo=37421

   (26) https://bugs.python.org/issue?@action=redirect&bpo=37421

   (27) https://bugs.python.org/issue?@action=redirect&bpo=37421

   (28) https://bugs.python.org/issue?@action=redirect&bpo=37472

   (29) https://bugs.python.org/issue?@action=redirect&bpo=37199

   (30) https://bugs.python.org/issue?@action=redirect&bpo=19696

   (31) https://bugs.python.org/issue?@action=redirect&bpo=37335

   (32) https://bugs.python.org/issue?@action=redirect&bpo=37421

   (33) https://bugs.python.org/issue?@action=redirect&bpo=37411

   (34) https://bugs.python.org/issue?@action=redirect&bpo=37400

   (35) https://bugs.python.org/issue?@action=redirect&bpo=37359

   (36) https://bugs.python.org/issue?@action=redirect&bpo=37362

   (37) https://bugs.python.org/issue?@action=redirect&bpo=35998

   (38) https://bugs.python.org/issue?@action=redirect&bpo=37278

   (39) https://bugs.python.org/issue?@action=redirect&bpo=37261

   (40) https://bugs.python.org/issue?@action=redirect&bpo=37069

   (41) https://bugs.python.org/issue?@action=redirect&bpo=37252

   (42) https://bugs.python.org/issue?@action=redirect&bpo=37169

   (43) https://bugs.python.org/issue?@action=redirect&bpo=37153

   (44) https://bugs.python.org/issue?@action=redirect&bpo=34001

   (45) https://bugs.python.org/issue?@action=redirect&bpo=36919

   (46) https://bugs.python.org/issue?@action=redirect&bpo=30202

   (47) https://bugs.python.org/issue?@action=redirect&bpo=28009

   (48) https://bugs.python.org/issue?@action=redirect&bpo=34596


File: python.info,  Node: Build<43>,  Next: Windows<38>,  Prev: Tests<40>,  Up: Python 3 9 0 alpha 1

1.23.44.6 Build
...............

   - bpo-38809(1): On Windows, build scripts will now recognize and use
     python.exe from an active virtual env.

   - bpo-38684(2): Fix _hashlib build when Blake2 is disabled, but
     OpenSSL supports it.

   - bpo-38468(3): Misc/python-config.in now uses ‘getvar()’ for all
     still existing ‘sysconfig.get_config_var()’ calls.  Patch by
     Joannah Nanjekye.

   - bpo-37415(4): Fix stdatomic.h header check for ICC compiler: the
     ICC implementation lacks atomic_uintptr_t type which is needed by
     Python.

   - bpo-38301(5): In Solaris family, we must be sure to use
     ‘-D_REENTRANT’.  Patch by Jesús Cea Avión.

   - bpo-36002(6): Locate ‘llvm-profdata’ and ‘llvm-ar’ binaries using
     ‘AC_PATH_TOOL’ rather than ‘AC_PATH_TARGET_TOOL’.

   - bpo-37936(7): The ‘.gitignore’ file systematically keeps "rooted",
     with a non-trailing slash, all the rules that are meant to apply to
     files in a specific place in the repo.  Previously, when the
     intended file to ignore happened to be at the root of the repo,
     we'd most often accidentally also ignore files and directories with
     the same name anywhere in the tree.

   - bpo-37760(8): The ‘Tools/unicode/makeunicodedata.py’ script, which
     is used for converting information from the Unicode Character
     Database into generated code and data used by the methods of *note
     str: 3f2. and by the *note unicodedata: ee. module, now handles
     each character's data as a ‘dataclass’ with named attributes,
     rather than a length-18 list of different fields.

   - bpo-37936(9): The ‘.gitignore’ file no longer applies to any files
     that are in fact tracked in the Git repository.  Patch by Greg
     Price.

   - bpo-37725(10): Change "clean" makefile target to also clean the
     program guided optimization (PGO) data.  Previously you would have
     to use "make clean" and "make profile-removal", or "make clobber".

   - bpo-37707(11): Mark some individual tests to skip when -pgo is
     used.  The tests marked increase the PGO task time significantly
     and likely don't help improve optimization of the final executable.

   - bpo-36044(12): Reduce the number of unit tests run for the PGO
     generation task.  This speeds up the task by a factor of about 15x.
     Running the full unit test suite is slow.  This change may result
     in a slightly less optimized build since not as many code branches
     will be executed.  If you are willing to wait for the much slower
     build, the old behavior can be restored using './configure [..]
     PROFILE_TASK="-m test -pgo-extended"'.  We make no guarantees as to
     which PGO task set produces a faster build.  Users who care should
     run their own relevant benchmarks as results can depend on the
     environment, workload, and compiler tool chain.

   - bpo-37468(13): ‘make install’ no longer installs ‘wininst-*.exe’
     files used by distutils bdist_wininst: bdist_wininst only works on
     Windows.

   - bpo-37189(14): Many ‘PyRun_XXX()’ functions like *note
     PyRun_String(): 18e0. were no longer exported in ‘libpython38.dll’
     by mistake.  Export them again to fix the ABI compatibility.

   - bpo-25361(15): Enables use of SSE2 instructions in Windows 32-bit
     build.

   - bpo-36210(16): Update optional extension module detection for AIX.
     ossaudiodev and spwd are not applicable for AIX, and are no longer
     reported as missing.  3rd-party packaging of ncurses (with ASIS
     support) conflicts with officially supported AIX curses library, so
     configure AIX to use libcurses.a.  However, skip trying to build
     _curses_panel.

     patch by M Felt

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38809

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38684

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38468

   (4) https://bugs.python.org/issue?@action=redirect&bpo=37415

   (5) https://bugs.python.org/issue?@action=redirect&bpo=38301

   (6) https://bugs.python.org/issue?@action=redirect&bpo=36002

   (7) https://bugs.python.org/issue?@action=redirect&bpo=37936

   (8) https://bugs.python.org/issue?@action=redirect&bpo=37760

   (9) https://bugs.python.org/issue?@action=redirect&bpo=37936

   (10) https://bugs.python.org/issue?@action=redirect&bpo=37725

   (11) https://bugs.python.org/issue?@action=redirect&bpo=37707

   (12) https://bugs.python.org/issue?@action=redirect&bpo=36044

   (13) https://bugs.python.org/issue?@action=redirect&bpo=37468

   (14) https://bugs.python.org/issue?@action=redirect&bpo=37189

   (15) https://bugs.python.org/issue?@action=redirect&bpo=25361

   (16) https://bugs.python.org/issue?@action=redirect&bpo=36210


File: python.info,  Node: Windows<38>,  Next: macOS<32>,  Prev: Build<43>,  Up: Python 3 9 0 alpha 1

1.23.44.7 Windows
.................

   - bpo-38589(1): Fixes HTML Help shortcut when Windows is not
     installed to C drive

   - bpo-38453(2): Ensure ntpath.realpath() correctly resolves relative
     paths.

   - bpo-38519(3): Restores the internal C headers that were missing
     from the nuget.org and Microsoft Store packages.

   - bpo-38492(4): Remove ‘pythonw.exe’ dependency on the Microsoft C++
     runtime.

   - bpo-38344(5): Fix error message in activate.bat

   - bpo-38359(6): Ensures ‘pyw.exe’ launcher reads correct registry
     key.

   - bpo-38355(7): Fixes ‘ntpath.realpath’ failing on ‘sys.executable’.

   - bpo-38117(8): Update bundled OpenSSL to 1.1.1d

   - bpo-38092(9): Reduce overhead when using multiprocessing in a
     Windows virtual environment.

   - bpo-38133(10): Allow py.exe launcher to locate installations from
     the Microsoft Store and improve display of active virtual
     environments.

   - bpo-38114(11): The ‘pip.ini’ is no longer included in the Nuget
     package.

   - bpo-32592(12): Set Windows 8 as the minimum required version for
     API support

   - bpo-36634(13): *note os.cpu_count(): 1a8. now returns active
     processors rather than maximum processors.

   - bpo-36634(14): venv activate.bat now works when the existing
     variables contain double quote characters.

   - bpo-38081(15): Prevent error calling *note os.path.realpath(): 20a.
     on ‘'NUL'’.

   - bpo-38087(16): Fix case sensitivity in test_pathlib and
     test_ntpath.

   - bpo-38088(17): Fixes distutils not finding vcruntime140.dll with
     only the v142 toolset installed.

   - bpo-37283(18): Ensure command-line and unattend.xml setting
     override previously detected states in Windows installer.

   - bpo-38030(19): Fixes *note os.stat(): 448. failing for block
     devices on Windows

   - bpo-38020(20): Fixes potential crash when calling *note
     os.readlink(): 8c5. (or indirectly through *note realpath(): 20a.)
     on a file that is not a supported link.

   - bpo-37705(21): Improve the implementation of ‘winerror_to_errno()’.

   - bpo-37549(22): *note os.dup(): 18e2. no longer fails for standard
     streams on Windows 7.

   - bpo-1311(23): The ‘nul’ file on Windows now returns True from *note
     exists(): 9b2. and a valid result from *note os.stat(): 448. with
     ‘S_IFCHR’ set.

   - bpo-9949(24): Enable support for following symlinks in
     ‘os.realpath()’.

   - bpo-37834(25): Treat all name surrogate reparse points on Windows
     in *note os.lstat(): 449. and other reparse points as regular files
     in *note os.stat(): 448.

   - bpo-36266(26): Add the module name in the formatted error message
     when DLL load fail happens during module import in
     ‘_PyImport_FindSharedFuncptrWindows()’.  Patch by Srinivas
     Nyayapati.

   - bpo-25172(27): Trying to import the ‘crypt’ module on Windows will
     result in an *note ImportError: 352. with a message explaining that
     the module isn't supported on Windows.  On other platforms, if the
     underlying ‘_crypt’ module is not available, the ImportError will
     include a message explaining the problem.

   - bpo-37778(28): Fixes the icons used for file associations to the
     Microsoft Store package.

   - bpo-37734(29): Fix use of registry values to launch Python from
     Microsoft Store app.

   - bpo-37702(30): Fix memory leak on Windows in creating an SSLContext
     object or running ‘urllib.request.urlopen('https://...')’.

   - bpo-37672(31): Switch Windows Store package's pip to use bundled
     ‘pip.ini’ instead of ‘PIP_USER’ variable.

   - bpo-10945(32): Officially drop support for creating bdist_wininst
     installers on non-Windows systems.

   - bpo-37445(33): Include the ‘FORMAT_MESSAGE_IGNORE_INSERTS’ flag in
     ‘FormatMessageW()’ calls.

   - bpo-37369(34): Fixes path for *note sys.executable: 383. when
     running from the Microsoft Store.

   - bpo-37380(35): Don't collect unfinished processes with
     ‘subprocess._active’ on Windows to cleanup later.  Patch by Ruslan
     Kuprieiev.

   - bpo-37351(36): Removes libpython38.a from standard Windows
     distribution.

   - bpo-35360(37): Update Windows builds to use SQLite 3.28.0.

   - bpo-37267(38): On Windows, *note os.dup(): 18e2. no longer creates
     an inheritable fd when handling a character file.

   - bpo-36779(39): Ensure ‘time.tzname’ is correct on Windows when the
     active code page is set to CP_UTF7 or CP_UTF8.

   - bpo-32587(40): Make *note winreg.REG_MULTI_SZ: 18e3. support
     zero-length strings.

   - bpo-28269(41): Replace use of ‘strcasecmp()’ for the system
     function ‘_stricmp()’.  Patch by Minmin Gong.

   - bpo-36590(42): Add native Bluetooth RFCOMM support to socket
     module.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38589

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38453

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38519

   (4) https://bugs.python.org/issue?@action=redirect&bpo=38492

   (5) https://bugs.python.org/issue?@action=redirect&bpo=38344

   (6) https://bugs.python.org/issue?@action=redirect&bpo=38359

   (7) https://bugs.python.org/issue?@action=redirect&bpo=38355

   (8) https://bugs.python.org/issue?@action=redirect&bpo=38117

   (9) https://bugs.python.org/issue?@action=redirect&bpo=38092

   (10) https://bugs.python.org/issue?@action=redirect&bpo=38133

   (11) https://bugs.python.org/issue?@action=redirect&bpo=38114

   (12) https://bugs.python.org/issue?@action=redirect&bpo=32592

   (13) https://bugs.python.org/issue?@action=redirect&bpo=36634

   (14) https://bugs.python.org/issue?@action=redirect&bpo=36634

   (15) https://bugs.python.org/issue?@action=redirect&bpo=38081

   (16) https://bugs.python.org/issue?@action=redirect&bpo=38087

   (17) https://bugs.python.org/issue?@action=redirect&bpo=38088

   (18) https://bugs.python.org/issue?@action=redirect&bpo=37283

   (19) https://bugs.python.org/issue?@action=redirect&bpo=38030

   (20) https://bugs.python.org/issue?@action=redirect&bpo=38020

   (21) https://bugs.python.org/issue?@action=redirect&bpo=37705

   (22) https://bugs.python.org/issue?@action=redirect&bpo=37549

   (23) https://bugs.python.org/issue?@action=redirect&bpo=1311

   (24) https://bugs.python.org/issue?@action=redirect&bpo=9949

   (25) https://bugs.python.org/issue?@action=redirect&bpo=37834

   (26) https://bugs.python.org/issue?@action=redirect&bpo=36266

   (27) https://bugs.python.org/issue?@action=redirect&bpo=25172

   (28) https://bugs.python.org/issue?@action=redirect&bpo=37778

   (29) https://bugs.python.org/issue?@action=redirect&bpo=37734

   (30) https://bugs.python.org/issue?@action=redirect&bpo=37702

   (31) https://bugs.python.org/issue?@action=redirect&bpo=37672

   (32) https://bugs.python.org/issue?@action=redirect&bpo=10945

   (33) https://bugs.python.org/issue?@action=redirect&bpo=37445

   (34) https://bugs.python.org/issue?@action=redirect&bpo=37369

   (35) https://bugs.python.org/issue?@action=redirect&bpo=37380

   (36) https://bugs.python.org/issue?@action=redirect&bpo=37351

   (37) https://bugs.python.org/issue?@action=redirect&bpo=35360

   (38) https://bugs.python.org/issue?@action=redirect&bpo=37267

   (39) https://bugs.python.org/issue?@action=redirect&bpo=36779

   (40) https://bugs.python.org/issue?@action=redirect&bpo=32587

   (41) https://bugs.python.org/issue?@action=redirect&bpo=28269

   (42) https://bugs.python.org/issue?@action=redirect&bpo=36590


File: python.info,  Node: macOS<32>,  Next: IDLE<30>,  Prev: Windows<38>,  Up: Python 3 9 0 alpha 1

1.23.44.8 macOS
...............

   - bpo-38117(1): Updated OpenSSL to 1.1.1d in macOS installer.

   - bpo-38089(2): Move Azure Pipelines to latest VM versions and make
     macOS tests optional

   - bpo-18049(3): Increase the default stack size of threads from 5MB
     to 16MB on macOS, to match the stack size of the main thread.  This
     avoids crashes on deep recursion in threads.

   - bpo-34602(4): Avoid test suite failures on macOS by no longer
     calling resource.setrlimit to increase the process stack size limit
     at runtime.  The runtime change is no longer needed since the
     interpreter is being built with a larger default stack size.

   - bpo-35360(5): Update macOS installer to use SQLite 3.28.0.

   - bpo-34631(6): Updated OpenSSL to 1.1.1c in macOS installer.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38117

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38089

   (3) https://bugs.python.org/issue?@action=redirect&bpo=18049

   (4) https://bugs.python.org/issue?@action=redirect&bpo=34602

   (5) https://bugs.python.org/issue?@action=redirect&bpo=35360

   (6) https://bugs.python.org/issue?@action=redirect&bpo=34631


File: python.info,  Node: IDLE<30>,  Next: Tools/Demos<19>,  Prev: macOS<32>,  Up: Python 3 9 0 alpha 1

1.23.44.9 IDLE
..............

   - bpo-26353(1): Stop adding newline when saving an IDLE shell window.

   - bpo-4630(2): Add an option to toggle IDLE's cursor blink for shell,
     editor, and output windows.  See Settings, General, Window
     Preferences, Cursor Blink.  Patch by Zackery Spytz.

   - bpo-38598(3): Do not try to compile IDLE shell or output windows

   - bpo-36698(4): IDLE no longer fails when write non-encodable
     characters to stderr.  It now escapes them with a backslash, as the
     regular Python interpreter.  Added the ‘errors’ field to the
     standard streams.

   - bpo-35379(5): When exiting IDLE, catch any AttributeError.  One
     happens when EditorWindow.close is called twice.  Printing a
     traceback, when IDLE is run from a terminal, is useless and
     annoying.

   - bpo-38183(6): To avoid problems, test_idle ignores the user config
     directory.  It no longer tries to create or access .idlerc or any
     files within.  Users must run IDLE to discover problems with saving
     settings.

   - bpo-38077(7): IDLE no longer adds 'argv' to the user namespace when
     initializing it.  This bug only affected 3.7.4 and 3.8.0b2 to
     3.8.0b4.

   - bpo-38041(8): Shell restart lines now fill the window width, always
     start with '=', and avoid wrapping unnecessarily.  The line will
     still wrap if the included file name is long relative to the width.

   - bpo-35771(9): To avoid occasional spurious test_idle failures on
     slower machines, increase the ‘hover_delay’ in test_tooltip.

   - bpo-37824(10): Properly handle user input warnings in IDLE shell.
     Cease turning SyntaxWarnings into SyntaxErrors.

   - bpo-37929(11): IDLE Settings dialog now closes properly when there
     is no shell window.

   - bpo-37902(12): Add mousewheel scrolling for IDLE module, path, and
     stack browsers.  Patch by George Zhang.

   - bpo-37849(13): Fixed completions list appearing too high or low
     when shown above the current line.

   - bpo-36419(14): Refactor IDLE autocomplete and improve testing.

   - bpo-37748(15): Reorder the Run menu.  Put the most common choice,
     Run Module, at the top.

   - bpo-37692(16): Improve highlight config sample with example shell
     interaction and better labels for shell elements.

   - bpo-37628(17): Settings dialog no longer expands with font size.

   - bpo-37627(18): Initialize the Customize Run dialog with the command
     line arguments most recently entered before.  The user can
     optionally edit before submitting them.

   - bpo-33610(19): Fix code context not showing the correct context
     when first toggled on.

   - bpo-37530(20): Optimize code context to reduce unneeded background
     activity.  Font and highlight changes now occur along with text
     changes instead of after a random delay.

   - bpo-27452(21): Cleanup ‘config.py’ by inlining ‘RemoveFile’ and
     simplifying the handling of ‘file’ in ‘CreateConfigHandlers’.

   - bpo-37325(22): Fix tab focus traversal order for help source and
     custom run dialogs.

   - bpo-37321(23): Both subprocess connection error messages now refer
     to the 'Startup failure' section of the IDLE doc.

   - bpo-17535(24): Add optional line numbers for IDLE editor windows.
     Windows open without line numbers unless set otherwise in the
     General tab of the configuration dialog.

   - bpo-26806(25): To compensate for stack frames added by IDLE and
     avoid possible problems with low recursion limits, add 30 to limits
     in the user code execution process.  Subtract 30 when reporting
     recursion limits to make this addition mostly transparent.

   - bpo-37177(26): Properly 'attach' search dialogs to their main
     window so that they behave like other dialogs and do not get hidden
     behind their main window.

   - bpo-37039(27): Adjust "Zoom Height" to individual screens by
     momentarily maximizing the window on first use with a particular
     screen.  Changing screen settings may invalidate the saved height.
     While a window is maximized, "Zoom Height" has no effect.

   - bpo-35763(28): Make calltip reminder about '/' meaning
     positional-only less obtrusive by only adding it when there is room
     on the first line.

   - bpo-5680(29): Add 'Run...  Customized' to the Run menu to run a
     module with customized settings.  Any 'command line arguments'
     entered are added to sys.argv.  One can suppress the normal Shell
     main module restart.

   - bpo-36390(30): Gather Format menu functions into format.py.
     Combine paragraph.py, rstrip.py, and format methods from editor.py.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26353

   (2) https://bugs.python.org/issue?@action=redirect&bpo=4630

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38598

   (4) https://bugs.python.org/issue?@action=redirect&bpo=36698

   (5) https://bugs.python.org/issue?@action=redirect&bpo=35379

   (6) https://bugs.python.org/issue?@action=redirect&bpo=38183

   (7) https://bugs.python.org/issue?@action=redirect&bpo=38077

   (8) https://bugs.python.org/issue?@action=redirect&bpo=38041

   (9) https://bugs.python.org/issue?@action=redirect&bpo=35771

   (10) https://bugs.python.org/issue?@action=redirect&bpo=37824

   (11) https://bugs.python.org/issue?@action=redirect&bpo=37929

   (12) https://bugs.python.org/issue?@action=redirect&bpo=37902

   (13) https://bugs.python.org/issue?@action=redirect&bpo=37849

   (14) https://bugs.python.org/issue?@action=redirect&bpo=36419

   (15) https://bugs.python.org/issue?@action=redirect&bpo=37748

   (16) https://bugs.python.org/issue?@action=redirect&bpo=37692

   (17) https://bugs.python.org/issue?@action=redirect&bpo=37628

   (18) https://bugs.python.org/issue?@action=redirect&bpo=37627

   (19) https://bugs.python.org/issue?@action=redirect&bpo=33610

   (20) https://bugs.python.org/issue?@action=redirect&bpo=37530

   (21) https://bugs.python.org/issue?@action=redirect&bpo=27452

   (22) https://bugs.python.org/issue?@action=redirect&bpo=37325

   (23) https://bugs.python.org/issue?@action=redirect&bpo=37321

   (24) https://bugs.python.org/issue?@action=redirect&bpo=17535

   (25) https://bugs.python.org/issue?@action=redirect&bpo=26806

   (26) https://bugs.python.org/issue?@action=redirect&bpo=37177

   (27) https://bugs.python.org/issue?@action=redirect&bpo=37039

   (28) https://bugs.python.org/issue?@action=redirect&bpo=35763

   (29) https://bugs.python.org/issue?@action=redirect&bpo=5680

   (30) https://bugs.python.org/issue?@action=redirect&bpo=36390


File: python.info,  Node: Tools/Demos<19>,  Next: C API<42>,  Prev: IDLE<30>,  Up: Python 3 9 0 alpha 1

1.23.44.10 Tools/Demos
......................

   - bpo-38118(1): Update Valgrind suppression file to ignore a false
     alarm in *note PyUnicode_Decode(): 18e7. when using GCC builtin
     strcmp().

   - bpo-38347(2): pathfix.py: Assume all files that end on '.py' are
     Python scripts when working recursively.

   - bpo-37803(3): pdb's ‘--help’ and ‘--version’ long options now work.

   - bpo-37942(4): Improve ArgumentClinic converter for floats.

   - bpo-37704(5): Remove ‘Tools/scripts/h2py.py’: use cffi to access a
     C API in Python.

   - bpo-37675(6): 2to3 now works when run from a zipped standard
     library.

   - bpo-37034(7): Argument Clinic now uses the argument name on errors
     with keyword-only argument instead of their position.  Patch
     contributed by Rémi Lapeyre.

   - bpo-37064(8): Add option -k to pathscript.py script: preserve
     shebang flags.  Add option -a to pathscript.py script: add flags.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=38118

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38347

   (3) https://bugs.python.org/issue?@action=redirect&bpo=37803

   (4) https://bugs.python.org/issue?@action=redirect&bpo=37942

   (5) https://bugs.python.org/issue?@action=redirect&bpo=37704

   (6) https://bugs.python.org/issue?@action=redirect&bpo=37675

   (7) https://bugs.python.org/issue?@action=redirect&bpo=37034

   (8) https://bugs.python.org/issue?@action=redirect&bpo=37064


File: python.info,  Node: C API<42>,  Prev: Tools/Demos<19>,  Up: Python 3 9 0 alpha 1

1.23.44.11 C API
................

   - bpo-37633(1): Re-export some function compatibility wrappers for
     macros in ‘pythonrun.h’.

   - bpo-38644(2): Provide *note Py_EnterRecursiveCall(): 917. and *note
     Py_LeaveRecursiveCall(): 918. as regular functions for the limited
     API. Previously, there were defined as macros, but these macros
     didn't work with the limited API which cannot access
     ‘PyThreadState.recursion_depth’ field.  Remove
     ‘_Py_CheckRecursionLimit’ from the stable ABI.

   - bpo-38650(3): The global variable *note
     PyStructSequence_UnnamedField: 926. is now a constant and refers to
     a constant string.

   - bpo-38540(4): Fixed possible leak in *note PyArg_Parse(): 18e9. and
     similar functions for format units ‘"es#"’ and ‘"et#"’ when the
     macro ‘PY_SSIZE_T_CLEAN’ is not defined.

   - bpo-38395(5): Fix a crash in *note weakref.proxy: 9f5. objects due
     to incorrect lifetime management when calling some associated
     methods that may delete the last reference to object being
     referenced by the proxy.  Patch by Pablo Galindo.

   - bpo-36389(6): The ‘_PyObject_CheckConsistency()’ function is now
     also available in release mode.  For example, it can be used to
     debug a crash in the ‘visit_decref()’ function of the GC.

   - bpo-38266(7): Revert the removal of PyThreadState_DeleteCurrent()
     with documentation.

   - bpo-38303(8): Update audioop extension module to use the stable ABI
     (PEP-384).  Patch by Tyler Kieft.

   - bpo-38234(9): ‘Py_SetPath()’ now sets *note sys.executable: 383. to
     the program full path (*note Py_GetProgramFullPath(): 382.) rather
     than to the program name (*note Py_GetProgramName(): 384.).

   - bpo-38234(10): Python ignored arguments passed to ‘Py_SetPath()’,
     ‘Py_SetPythonHome()’ and ‘Py_SetProgramName()’: fix Python
     initialization to use specified arguments.

   - bpo-38205(11): The *note Py_UNREACHABLE(): b5c. macro now calls
     *note Py_FatalError(): 927.

   - bpo-38140(12): Make dict and weakref offsets opaque for C heap
     types by passing the offsets through PyMemberDef

   - bpo-15088(13): The C function ‘PyGen_NeedsFinalizing’ has been
     removed.  It was not documented, tested or used anywhere within
     CPython after the implementation of PEP 442(14).  Patch by Joannah
     Nanjekye.  (Patch by Joannah Nanjekye)

   - bpo-36763(15): Options added by ‘PySys_AddXOption()’ are now
     handled the same way than ‘PyConfig.xoptions’ and command line ‘-X’
     options.

   - bpo-37926(16): Fix a crash in ‘PySys_SetArgvEx(0, NULL, 0)’.

   - bpo-37879(17): Fix subtype_dealloc to suppress the type decref when
     the base type is a C heap type

   - bpo-37645(18): Add ‘_PyObject_FunctionStr()’ to get a user-friendly
     string representation of a function-like object.  Patch by Jeroen
     Demeyer.

   - bpo-29548(19): The functions ‘PyEval_CallObject’,
     ‘PyEval_CallFunction’, ‘PyEval_CallMethod’ and
     ‘PyEval_CallObjectWithKeywords’ are deprecated.  Use *note
     PyObject_Call(): 363. and its variants instead.

   - bpo-37151(20): ‘PyCFunction_Call’ is now a deprecated alias of
     *note PyObject_Call(): 363.

   - bpo-37540(21): The vectorcall protocol now requires that the caller
     passes only strings as keyword names.

   - bpo-37207(22): The vectorcall protocol is now enabled for ‘type’
     objects: set ‘tp_vectorcall’ to a vectorcall function to be used
     instead of ‘tp_new’ and ‘tp_init’ when calling the class itself.

   - bpo-21120(23): Exclude Python-ast.h, ast.h and asdl.h from the
     limited API.

   - bpo-37483(24): Add new function ‘_PyObject_CallOneArg’ for calling
     an object with one positional argument.

   - bpo-36763(25): Add *note PyConfig_SetWideStringList(): 18ea.
     function.

   - bpo-37337(26): Add fast functions for calling methods:
     ‘_PyObject_VectorcallMethod()’, ‘_PyObject_CallMethodNoArgs()’ and
     ‘_PyObject_CallMethodOneArg()’.

   - bpo-28805(27): The *note METH_FASTCALL: 151b. calling convention
     has been documented.

   - bpo-37221(28): The new function ‘PyCode_NewWithPosOnlyArgs()’
     allows to create code objects like ‘PyCode_New()’, but with an
     extra 'posonlyargcount' parameter for indicating the number of
     positonal-only arguments.

   - bpo-37215(29): Fix dtrace issue introduce by bpo-36842(30)

   - bpo-37194(31): Add a new public *note PyObject_CallNoArgs(): 362.
     function to the C API: call a callable Python object without any
     arguments.  It is the most efficient way to call a callback without
     any argument.  On x86-64, for example,
     ‘PyObject_CallFunctionObjArgs(func, NULL)’ allocates 960 bytes on
     the stack per call, whereas ‘PyObject_CallNoArgs(func)’ only
     allocates 624 bytes per call.

   - bpo-37170(32): Fix the cast on error in *note
     PyLong_AsUnsignedLongLongMask(): 18eb.

   - bpo-35381(33): Convert posixmodule.c statically allocated types
     ‘DirEntryType’ and ‘ScandirIteratorType’ to heap-allocated types.

   - bpo-34331(34): Use singular/plural noun in error message when
     instantiating an abstract class with non-overridden abstract
     method(s).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=37633

   (2) https://bugs.python.org/issue?@action=redirect&bpo=38644

   (3) https://bugs.python.org/issue?@action=redirect&bpo=38650

   (4) https://bugs.python.org/issue?@action=redirect&bpo=38540

   (5) https://bugs.python.org/issue?@action=redirect&bpo=38395

   (6) https://bugs.python.org/issue?@action=redirect&bpo=36389

   (7) https://bugs.python.org/issue?@action=redirect&bpo=38266

   (8) https://bugs.python.org/issue?@action=redirect&bpo=38303

   (9) https://bugs.python.org/issue?@action=redirect&bpo=38234

   (10) https://bugs.python.org/issue?@action=redirect&bpo=38234

   (11) https://bugs.python.org/issue?@action=redirect&bpo=38205

   (12) https://bugs.python.org/issue?@action=redirect&bpo=38140

   (13) https://bugs.python.org/issue?@action=redirect&bpo=15088

   (14) https://peps.python.org/pep-0442/

   (15) https://bugs.python.org/issue?@action=redirect&bpo=36763

   (16) https://bugs.python.org/issue?@action=redirect&bpo=37926

   (17) https://bugs.python.org/issue?@action=redirect&bpo=37879

   (18) https://bugs.python.org/issue?@action=redirect&bpo=37645

   (19) https://bugs.python.org/issue?@action=redirect&bpo=29548

   (20) https://bugs.python.org/issue?@action=redirect&bpo=37151

   (21) https://bugs.python.org/issue?@action=redirect&bpo=37540

   (22) https://bugs.python.org/issue?@action=redirect&bpo=37207

   (23) https://bugs.python.org/issue?@action=redirect&bpo=21120

   (24) https://bugs.python.org/issue?@action=redirect&bpo=37483

   (25) https://bugs.python.org/issue?@action=redirect&bpo=36763

   (26) https://bugs.python.org/issue?@action=redirect&bpo=37337

   (27) https://bugs.python.org/issue?@action=redirect&bpo=28805

   (28) https://bugs.python.org/issue?@action=redirect&bpo=37221

   (29) https://bugs.python.org/issue?@action=redirect&bpo=37215

   (30) https://bugs.python.org/issue?@action=redirect&bpo=36842

   (31) https://bugs.python.org/issue?@action=redirect&bpo=37194

   (32) https://bugs.python.org/issue?@action=redirect&bpo=37170

   (33) https://bugs.python.org/issue?@action=redirect&bpo=35381

   (34) https://bugs.python.org/issue?@action=redirect&bpo=34331


File: python.info,  Node: Python 3 8 0 beta 1,  Next: Python 3 8 0 alpha 4,  Prev: Python 3 9 0 alpha 1,  Up: Changelog（更動日誌）

1.23.45 Python 3.8.0 beta 1
---------------------------

'Release date: 2019-06-04'

* Menu:

* Security: Security<30>.
* Core and Builtins: Core and Builtins<45>.
* Library: Library<44>.
* Documentation: Documentation<39>.
* Tests: Tests<41>.
* Build: Build<44>.
* Windows: Windows<39>.
* macOS: macOS<33>.
* IDLE: IDLE<31>.
* Tools/Demos: Tools/Demos<20>.
* C API: C API<43>.


File: python.info,  Node: Security<30>,  Next: Core and Builtins<45>,  Up: Python 3 8 0 beta 1

1.23.45.1 Security
..................

   - bpo-35907(1): CVE-2019-9948(2): Avoid file reading by disallowing
     ‘local-file://’ and ‘local_file://’ URL schemes in
     ‘URLopener().open()’ and ‘URLopener().retrieve()’ of *note
     urllib.request: f4.

   - bpo-33529(3): Prevent fold function used in email header encoding
     from entering infinite loop when there are too many non-ASCII
     characters in a header.

   - bpo-33164(4): Updated blake2 implementation which uses secure
     memset implementation provided by platform.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35907

   (2) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9948

   (3) https://bugs.python.org/issue?@action=redirect&bpo=33529

   (4) https://bugs.python.org/issue?@action=redirect&bpo=33164


File: python.info,  Node: Core and Builtins<45>,  Next: Library<44>,  Prev: Security<30>,  Up: Python 3 8 0 beta 1

1.23.45.2 Core and Builtins
...........................

   - bpo-35814(1): Allow unpacking in the right hand side of annotated
     assignments.  In particular, ‘t: Tuple[int, ...] = x, y, *z’ is now
     allowed.

   - bpo-37126(2): All structseq objects are now tracked by the garbage
     collector.  Patch by Pablo Galindo.

   - bpo-37122(3): Make the 'co_argcount' attribute of code objects
     represent the total number of positional arguments (including
     positional-only arguments).  The value of 'co_posonlyargcount' can
     be used to distinguish which arguments are positional only, and the
     difference ('co_argcount' - 'co_posonlyargcount') is the number of
     positional-or-keyword arguments.  Patch by Pablo Galindo.

   - bpo-20092(4): Constructors of *note int: 23c, *note float: 2c8. and
     *note complex: 2c9. will now use the *note __index__(): 6c1.
     special method, if available and the corresponding method *note
     __int__(): 6c0, *note __float__(): 970. or *note __complex__():
     58d. is not available.

   - bpo-37087(5): Add native thread ID (TID) support to OpenBSD.

   - bpo-26219(6): Implemented per opcode cache mechanism and
     ‘LOAD_GLOBAL’ instruction use it.  ‘LOAD_GLOBAL’ is now about 40%
     faster.  Contributed by Yury Selivanov, and Inada Naoki.

   - bpo-37072(7): Fix crash in PyAST_FromNodeObject() when flags is
     NULL.

   - bpo-37029(8): Freeing a great many small objects could take time
     quadratic in the number of arenas, due to using linear search to
     keep ‘obmalloc.c’'s list of usable arenas sorted by order of number
     of free memory pools.  This is accomplished without search now,
     leaving the worst-case time linear in the number of arenas.  For
     programs where this quite visibly matters (typically with more than
     100 thousand small objects alive simultaneously), this can greatly
     reduce the time needed to release their memory.

   - bpo-26423(9): Fix possible overflow in ‘wrap_lenfunc()’ when
     ‘sizeof(long) < sizeof(Py_ssize_t)’ (e.g., 64-bit Windows).

   - bpo-37050(10): Improve the AST for "debug" f-strings, which use '='
     to print out the source of the expression being evaluated.  Delete
     expr_text from the FormattedValue node, and instead use a Constant
     string node (possibly merged with adjacent constant expressions
     inside the f-string).

   - bpo-22385(11): The ‘bytes.hex’, ‘bytearray.hex’, and
     ‘memoryview.hex’ methods as well as the ‘binascii.hexlify’ and
     ‘b2a_hex’ functions now have the ability to include an optional
     separator between hex bytes.  This functionality was inspired by
     MicroPython's hexlify implementation.

   - bpo-26836(12): Add *note os.memfd_create(): 9af.

   - bpo-37032(13): Added new ‘replace()’ method to the code type (*note
     types.CodeType: 2b6.).

   - bpo-37007(14): Implement *note socket.if_nameindex(): 9d1, *note
     socket.if_nametoindex(): 9d2, and *note socket.if_indextoname():
     9d3. on Windows.

   - bpo-36829(15): *note PyErr_WriteUnraisable(): 328. now creates a
     traceback object if there is no current traceback.  Moreover, call
     *note PyErr_NormalizeException(): 3bd. and *note
     PyException_SetTraceback(): 18ef. to normalize the exception value.
     Ignore any error.

   - bpo-36878(16): Only accept text after ‘# type: ignore’ if the first
     character is ASCII. This is to disallow things like ‘# type:
     ignoreé’.

   - bpo-36878(17): Store text appearing after a ‘# type: ignore’
     comment in the AST. For example a type ignore like ‘# type:
     ignore[E1000]’ will have the string ‘"[E1000]"’ stored in its AST
     node.

   - bpo-2180(18): Treat line continuation at EOF as a ‘SyntaxError’ by
     Anthony Sottile.

   - bpo-36907(19): Fix a crash when calling a C function with a keyword
     dict (‘f(**kwargs)’) and changing the dict ‘kwargs’ while that
     function is running.

   - bpo-36946(20): Fix possible signed integer overflow when handling
     slices.

   - bpo-36826(21): Add NamedExpression kind support to ast_unparse.c

   - bpo-1875(22): A *note SyntaxError: 173. is now raised if a code
     blocks that will be optimized away (e.g.  if conditions that are
     always false) contains syntax errors.  Patch by Pablo Galindo.

   - bpo-36027(23): Allow computation of modular inverses via
     three-argument ‘pow’: the second argument is now permitted to be
     negative in the case where the first and third arguments are
     relatively prime.

   - bpo-36861(24): Update the Unicode database to version 12.1.0.

   - bpo-28866(25): Avoid caching attributes of classes which type
     defines mro() to avoid a hard cache invalidation problem.

   - bpo-36851(26): The ‘FrameType’ stack is now correctly cleaned up if
     the execution ends with a return and the stack is not empty.

   - bpo-34616(27): The ‘compile()’ builtin functions now support the
     ‘ast.PyCF_ALLOW_TOP_LEVEL_AWAIT’ flag, which allow to compile
     sources that contains top-level ‘await’, ‘async with’ or ‘async
     for’.  This is useful to evaluate async-code from with an already
     async functions; for example in a custom REPL.

   - bpo-36842(28): Implement PEP 578, adding sys.audit, io.open_code
     and related APIs.

   - bpo-27639(29): Correct return type for UserList slicing operations.
     Patch by Michael Blahay, Erick Cervantes, and vaultah

   - bpo-36737(30): Move PyRuntimeState.warnings into per-interpreter
     state (via "module state").

   - bpo-36793(31): Removed ‘__str__’ implementations from builtin types
     *note bool: 40e, *note int: 23c, *note float: 2c8, *note complex:
     2c9. and few classes from the standard library.  They now inherit
     ‘__str__()’ from *note object: a2f.

   - bpo-36817(32): Add a ‘=’ feature f-strings for debugging.  This can
     precede ‘!s’, ‘!r’, or ‘!a’.  It produces the text of the
     expression, followed by an equal sign, followed by the repr of the
     value of the expression.  So ‘f'{3*9+15=}'’ would be equal to the
     string ‘'3*9+15=42'’.  If ‘=’ is specified, the default conversion
     is set to ‘!r’, unless a format spec is given, in which case the
     formatting behavior is unchanged, and __format__ will be used.

   - bpo-24048(33): Save the live exception during import.c's
     ‘remove_module()’.

   - bpo-27987(34): pymalloc returns memory blocks aligned by 16 bytes,
     instead of 8 bytes, on 64-bit platforms to conform x86-64 ABI.
     Recent compilers assume this alignment more often.  Patch by Inada
     Naoki.

   - bpo-36601(35): A long-since-meaningless check for ‘getpid() ==
     main_pid’ was removed from Python's internal C signal handler.

   - bpo-36594(36): Fix incorrect use of ‘%p’ in format strings.  Patch
     by Zackery Spytz.

   - bpo-36045(37): ‘builtins.help()’ now prefixes ‘async’ for async
     functions.

   - bpo-36084(38): Add native thread ID (TID) to threading.Thread
     objects (supported platforms: Windows, FreeBSD, Linux, macOS)

   - bpo-36035(39): Added fix for broken symlinks in combination with
     pathlib

   - bpo-35983(40): Added new trashcan macros to deal with a double
     deallocation that could occur when the ‘tp_dealloc’ of a subclass
     calls the ‘tp_dealloc’ of a base class and that base class uses the
     trashcan mechanism.  Patch by Jeroen Demeyer.

   - bpo-20602(41): Do not clear *note sys.flags: 632. and *note
     sys.float_info: 18f0. during shutdown.  Patch by Zackery Spytz.

   - bpo-26826(42): Expose ‘copy_file_range()’ as a low level API in the
     *note os: 91. module.

   - bpo-32388(43): Remove cross-version binary compatibility
     requirement in tp_flags.

   - bpo-31862(44): Port binascii to PEP 489 multiphase initialization.
     Patch by Marcel Plch.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35814

   (2) https://bugs.python.org/issue?@action=redirect&bpo=37126

   (3) https://bugs.python.org/issue?@action=redirect&bpo=37122

   (4) https://bugs.python.org/issue?@action=redirect&bpo=20092

   (5) https://bugs.python.org/issue?@action=redirect&bpo=37087

   (6) https://bugs.python.org/issue?@action=redirect&bpo=26219

   (7) https://bugs.python.org/issue?@action=redirect&bpo=37072

   (8) https://bugs.python.org/issue?@action=redirect&bpo=37029

   (9) https://bugs.python.org/issue?@action=redirect&bpo=26423

   (10) https://bugs.python.org/issue?@action=redirect&bpo=37050

   (11) https://bugs.python.org/issue?@action=redirect&bpo=22385

   (12) https://bugs.python.org/issue?@action=redirect&bpo=26836

   (13) https://bugs.python.org/issue?@action=redirect&bpo=37032

   (14) https://bugs.python.org/issue?@action=redirect&bpo=37007

   (15) https://bugs.python.org/issue?@action=redirect&bpo=36829

   (16) https://bugs.python.org/issue?@action=redirect&bpo=36878

   (17) https://bugs.python.org/issue?@action=redirect&bpo=36878

   (18) https://bugs.python.org/issue?@action=redirect&bpo=2180

   (19) https://bugs.python.org/issue?@action=redirect&bpo=36907

   (20) https://bugs.python.org/issue?@action=redirect&bpo=36946

   (21) https://bugs.python.org/issue?@action=redirect&bpo=36826

   (22) https://bugs.python.org/issue?@action=redirect&bpo=1875

   (23) https://bugs.python.org/issue?@action=redirect&bpo=36027

   (24) https://bugs.python.org/issue?@action=redirect&bpo=36861

   (25) https://bugs.python.org/issue?@action=redirect&bpo=28866

   (26) https://bugs.python.org/issue?@action=redirect&bpo=36851

   (27) https://bugs.python.org/issue?@action=redirect&bpo=34616

   (28) https://bugs.python.org/issue?@action=redirect&bpo=36842

   (29) https://bugs.python.org/issue?@action=redirect&bpo=27639

   (30) https://bugs.python.org/issue?@action=redirect&bpo=36737

   (31) https://bugs.python.org/issue?@action=redirect&bpo=36793

   (32) https://bugs.python.org/issue?@action=redirect&bpo=36817

   (33) https://bugs.python.org/issue?@action=redirect&bpo=24048

   (34) https://bugs.python.org/issue?@action=redirect&bpo=27987

   (35) https://bugs.python.org/issue?@action=redirect&bpo=36601

   (36) https://bugs.python.org/issue?@action=redirect&bpo=36594

   (37) https://bugs.python.org/issue?@action=redirect&bpo=36045

   (38) https://bugs.python.org/issue?@action=redirect&bpo=36084

   (39) https://bugs.python.org/issue?@action=redirect&bpo=36035

   (40) https://bugs.python.org/issue?@action=redirect&bpo=35983

   (41) https://bugs.python.org/issue?@action=redirect&bpo=20602

   (42) https://bugs.python.org/issue?@action=redirect&bpo=26826

   (43) https://bugs.python.org/issue?@action=redirect&bpo=32388

   (44) https://bugs.python.org/issue?@action=redirect&bpo=31862


File: python.info,  Node: Library<44>,  Next: Documentation<39>,  Prev: Core and Builtins<45>,  Up: Python 3 8 0 beta 1

1.23.45.3 Library
.................

   - bpo-37128(1): Added *note math.perm(): 675.

   - bpo-37120(2): Add SSLContext.num_tickets to control the number of
     TLSv1.3 session tickets.

   - bpo-12202(3): Fix the error handling in
     ‘msilib.SummaryInformation.GetProperty()’.  Patch by Zackery Spytz.

   - bpo-26835(4): The fcntl module now contains file sealing constants
     for sealing of memfds.

   - bpo-29262(5): Add ‘get_origin()’ and ‘get_args()’ introspection
     helpers to ‘typing’ module.

   - bpo-12639(6): ‘msilib.Directory.start_component()’ no longer fails
     if 'keyfile' is not ‘None’.

   - bpo-36999(7): Add the ‘asyncio.Task.get_coro()’ method to publicly
     expose the tasks's coroutine object.

   - bpo-35246(8): Make *note asyncio.create_subprocess_exec(): a1a.
     accept path-like arguments.

   - bpo-35279(9): Change default 'max_workers' of ‘ThreadPoolExecutor’
     from ‘cpu_count() * 5’ to ‘min(32, cpu_count() + 4)’.  Previous
     value was unreasonably large on many cores machines.

   - bpo-37076(10): *note _thread.start_new_thread(): 17a. now logs
     uncaught exception raised by the function using *note
     sys.unraisablehook(): 1dc, rather than *note sys.excepthook(): 7af,
     so the hook gets access to the function which raised the exception.

   - bpo-33725(11): On macOS, the *note multiprocessing: 86. module now
     uses 'spawn' start method by default.

   - bpo-37054(12): Fix destructor ‘_pyio.BytesIO’ and
     ‘_pyio.TextIOWrapper’: initialize their ‘_buffer’ attribute as soon
     as possible (in the class body), because it's used by ‘__del__()’
     which calls ‘close()’.

   - bpo-37058(13): PEP 544: Add ‘Protocol’ and ‘@runtime_checkable’ to
     the ‘typing’ module.

   - bpo-36933(14): The functions ‘sys.set_coroutine_wrapper’ and
     ‘sys.get_coroutine_wrapper’ that were deprecated and marked for
     removal in 3.8 have been removed.

   - bpo-37047(15): Handle late binding and attribute access in *note
     unittest.mock.AsyncMock: 9ee. setup for autospeccing.  Document
     newly implemented async methods in *note unittest.mock.MagicMock:
     e33.

   - bpo-37049(16): PEP 589: Add ‘TypedDict’ to the ‘typing’ module.

   - bpo-37046(17): PEP 586: Add ‘Literal’ to the ‘typing’ module.

   - bpo-37045(18): PEP 591: Add ‘Final’ qualifier and ‘@final’
     decorator to the ‘typing’ module.

   - bpo-37035(19): Don't log OSError based exceptions if a fatal error
     has occurred in asyncio transport.  Peer can generate almost any
     OSError, user cannot avoid these exceptions by fixing own code.
     Errors are still propagated to user code, it's just logging them is
     pointless and pollute asyncio logs.

   - bpo-37001(20): *note symtable.symtable(): 18f2. now accepts the
     same input types for source code as the built-in *note compile():
     178. function.  Patch by Dino Viehland.

   - bpo-37028(21): Implement asyncio REPL

   - bpo-37027(22): Return safe to use proxy socket object from
     transport.get_extra_info('socket')

   - bpo-32528(23): Make asyncio.CancelledError a BaseException.

     This will address the common mistake many asyncio users make: an
     "except Exception" clause breaking Tasks cancellation.

     In addition to this change, we stop inheriting asyncio.TimeoutError
     and asyncio.InvalidStateError from their concurrent.futures.*
     counterparts.  There's no point for these exceptions to share the
     inheritance chain.

   - bpo-1230540(24): Add a new *note threading.excepthook(): 7ef.
     function which handles uncaught *note threading.Thread.run(): 9e0.
     exception.  It can be overridden to control how uncaught *note
     threading.Thread.run(): 9e0. exceptions are handled.

   - bpo-36996(25): Handle *note unittest.mock.patch(): e34. used as a
     decorator on async functions.

   - bpo-37008(26): Add support for calling *note next(): 77c. with the
     mock resulting from *note unittest.mock.mock_open(): 1606.

   - bpo-27737(27): Allow whitespace only header encoding in
     ‘email.header’ - by Batuhan Taskaya

   - bpo-36969(28): PDB command ‘args’ now display positional only
     arguments.  Patch contributed by Rémi Lapeyre.

   - bpo-36969(29): PDB command ‘args’ now display keyword only
     arguments.  Patch contributed by Rémi Lapeyre.

   - bpo-36983(30): Add missing names to ‘typing.__all__’: ‘ChainMap’,
     ‘ForwardRef’, ‘OrderedDict’ - by Anthony Sottile.

   - bpo-36972(31): Add SupportsIndex protocol to the typing module to
     allow type checking to detect classes that can be passed to
     ‘hex()’, ‘oct()’ and ‘bin()’.

   - bpo-32972(32): Implement ‘unittest.IsolatedAsyncioTestCase’ to help
     testing asyncio-based code.

   - bpo-36952(33): *note fileinput.input(): 7a3. and *note
     fileinput.FileInput: 6db. 'bufsize' argument has been removed (was
     deprecated and ignored since Python 3.6), and as a result the
     'mode' and 'openhook' arguments have been made keyword-only.

   - bpo-36952(34): Starting with Python 3.3, importing ABCs from *note
     collections: 16. is deprecated, and import should be done from
     *note collections.abc: 17.  Still being able to import from *note
     collections: 16. was marked for removal in 3.8, but has been
     delayed to 3.9; documentation and ‘DeprecationWarning’ clarified.

   - bpo-36949(35): Implement __repr__ for WeakSet objects.

   - bpo-36948(36): Fix *note NameError: 3e5. in *note
     urllib.request.URLopener.retrieve(): 18f3.  Patch by Karthikeyan
     Singaravelan.

   - bpo-33524(37): Fix the folding of email header when the
     max_line_length is 0 or None and the header contains non-ascii
     characters.  Contributed by Licht Takeuchi (@Licht-T).

   - bpo-24564(38): *note shutil.copystat(): 10c7. now ignores *note
     errno.EINVAL: 18f4. on *note os.setxattr(): 109f. which may occur
     when copying files on filesystems without extended attributes
     support.

     Original patch by Giampaolo Rodola, updated by Ying Wang.

   - bpo-36888(39): Python child processes can now access the status of
     their parent process using multiprocessing.process.parent_process

   - bpo-36921(40): Deprecate ‘@coroutine’ for sake of ‘async def’.

   - bpo-25652(41): Fix bug in ‘__rmod__’ of ‘UserString’ - by Batuhan
     Taskaya.

   - bpo-36916(42): Remove a message about an unhandled exception in a
     task when writer.write() is used without await and writer.drain()
     fails with an exception.

   - bpo-36889(43): Introduce ‘asyncio.Stream’ class that merges *note
     asyncio.StreamReader: 17c8. and *note asyncio.StreamWriter: 15fc.
     functionality.  ‘asyncio.Stream’ can work in readonly, writeonly
     and readwrite modes.  Provide ‘asyncio.connect()’,
     ‘asyncio.connect_unix()’, ‘asyncio.connect_read_pipe()’ and
     ‘asyncio.connect_write_pipe()’ factories to open ‘asyncio.Stream’
     connections.  Provide ‘asyncio.StreamServer’ and ‘UnixStreamServer’
     to serve servers with asyncio.Stream API. Modify *note
     asyncio.create_subprocess_shell(): a1b. and *note
     asyncio.create_subprocess_exec(): a1a. to use ‘asyncio.Stream’
     instead of deprecated ‘StreamReader’ and ‘StreamWriter’.  Deprecate
     *note asyncio.StreamReader: 17c8. and *note asyncio.StreamWriter:
     15fc.  Deprecate usage of private classes, e.g.
     ‘asyncio.FlowControlMixing’ and ‘asyncio.StreamReaderProtocol’
     outside of asyncio package.

   - bpo-36845(44): Added validation of integer prefixes to the
     construction of IP networks and interfaces in the ipaddress module.

   - bpo-23378(45): Add an extend action to argparser.

   - bpo-36867(46): Fix a bug making a SharedMemoryManager instance and
     its parent process use two separate resource_tracker processes.

   - bpo-23896(47): Adds a grammar to lib2to3.pygram that contains exec
     as a function not as statement.

   - bpo-36895(48): The function ‘time.clock()’ was deprecated in 3.3 in
     favor of ‘time.perf_counter()’ and marked for removal in 3.8, it
     has removed.

   - bpo-35545(49): Fix asyncio discarding IPv6 scopes when ensuring
     hostname resolutions internally

   - bpo-36887(50): Add new function *note math.isqrt(): 9a9. to compute
     integer square roots.

   - bpo-34632(51): Introduce the ‘importlib.metadata’ module with
     (provisional) support for reading metadata from third-party
     packages.

   - bpo-36878(52): When using ‘type_comments=True’ in ‘ast.parse’,
     treat ‘# type: ignore’ followed by a non-alphanumeric character and
     then arbitrary text as a type ignore, instead of requiring nothing
     but whitespace or another comment.  This is to permit formations
     such as ‘# type: ignore[E1000]’.

   - bpo-36778(53): ‘cp65001’ encoding (Windows code page 65001) becomes
     an alias to ‘utf_8’ encoding.

   - bpo-36867(54): The multiprocessing.resource_tracker replaces the
     multiprocessing.semaphore_tracker module.  Other than semaphores,
     resource_tracker also tracks shared_memory segments.

   - bpo-30262(55): The ‘Cache’ and ‘Statement’ objects of the *note
     sqlite3: ba. module are not exposed to the user.  Patch by Aviv
     Palivoda.

   - bpo-24538(56): In ‘shutil.copystat()’, first copy extended file
     attributes and then file permissions, since extended attributes can
     only be set on the destination while it is still writeable.

   - bpo-36829(57): Add new *note sys.unraisablehook(): 1dc. function
     which can be overridden to control how "unraisable exceptions" are
     handled.  It is called when an exception has occurred but there is
     no way for Python to handle it.  For example, when a destructor
     raises an exception or during garbage collection (*note
     gc.collect(): 16b.).

   - bpo-36832(58): Introducing ‘zipfile.Path’, a pathlib-compatible
     wrapper for traversing zip files.

   - bpo-36814(59): Fix an issue where os.posix_spawnp() would
     incorrectly raise a TypeError when file_actions is None.

   - bpo-33110(60): Handle exceptions raised by functions added by
     concurrent.futures add_done_callback correctly when the Future has
     already completed.

   - bpo-26903(61): Limit ‘max_workers’ in ‘ProcessPoolExecutor’ to 61
     to work around a WaitForMultipleObjects limitation.

   - bpo-36813(62): Fix *note QueueListener: dd2. to call
     ‘queue.task_done()’ upon stopping.  Patch by Bar Harel.

   - bpo-36806(63): Forbid creation of asyncio stream objects like
     StreamReader, StreamWriter, Process, and their protocols outside of
     asyncio package.

   - bpo-36802(64): Provide both sync and async calls for
     StreamWriter.write() and StreamWriter.close()

   - bpo-36801(65): Properly handle SSL connection closing in asyncio
     StreamWriter.drain() call.

   - bpo-36785(66): Implement PEP 574 (pickle protocol 5 with
     out-of-band buffers).

   - bpo-36772(67): functools.lru_cache() can now be used as a straight
     decorator in addition to its existing usage as a function that
     returns a decorator.

   - bpo-6584(68): Add a *note BadGzipFile: 99b. exception to the *note
     gzip: 5d. module.

   - bpo-36748(69): Optimized write buffering in C implementation of
     ‘TextIOWrapper’.  Writing ASCII string to ‘TextIOWrapper’ with
     ascii, latin1, or utf-8 encoding is about 20% faster.  Patch by
     Inada Naoki.

   - bpo-8138(70): Don't mark ‘wsgiref.simple_server.SimpleServer’ as
     multi-threaded since ‘wsgiref.simple_server.WSGIServer’ is
     single-threaded.

   - bpo-22640(71): *note py_compile.compile(): 9c9. now supports silent
     mode.  Patch by Joannah Nanjekye

   - bpo-29183(72): Fix double exceptions in *note
     wsgiref.handlers.BaseHandler: 18f5. by calling its ‘close()’ method
     only when no exception is raised.

   - bpo-36548(73): Improved the repr of regular expression flags.

   - bpo-36542(74): The signature of Python functions can now be
     overridden by specifying the ‘__text_signature__’ attribute.

   - bpo-36533(75): Reinitialize logging.Handler locks in forked child
     processes instead of attempting to acquire them all in the parent
     before forking only to be released in the child process.  The
     acquire/release pattern was leading to deadlocks in code that has
     implemented any form of chained logging handlers that depend upon
     one another as the lock acquisition order cannot be guaranteed.

   - bpo-35252(76): Throw a TypeError instead of an AssertionError when
     using an invalid type annotation with singledispatch.

   - bpo-35900(77): Allow reduction methods to return a 6-item tuple
     where the 6th item specifies a custom state-setting method that's
     called instead of the regular ‘__setstate__’ method.

   - bpo-35900(78): enable custom reduction callback registration for
     functions and classes in _pickle.c, using the new Pickler's
     attribute ‘reducer_override’

   - bpo-36368(79): Fix a bug crashing SharedMemoryManager instances in
     interactive sessions after a ctrl-c (KeyboardInterrupt) was sent

   - bpo-31904(80): Fix mmap fail for VxWorks

   - bpo-27497(81): *note csv.DictWriter.writeheader(): 1197. now
     returns the return value of the underlying ‘csv.Writer.writerow()’
     method.  Patch contributed by Ashish Nitin Patil.

   - bpo-36239(82): Parsing .mo files now ignores comments starting and
     ending with #-#-#-#-#.

   - bpo-26707(83): Enable plistlib to read and write binary plist files
     that were created as a KeyedArchive file.  Specifically, this
     allows the plistlib to process 0x80 tokens as UID objects.

   - bpo-31904(84): Add posix module support for VxWorks.

   - bpo-35125(85): Asyncio: Remove inner callback on outer cancellation
     in shield

   - bpo-35721(86): Fix ‘asyncio.SelectorEventLoop.subprocess_exec()’
     leaks file descriptors if ‘Popen’ fails and called with
     ‘stdin=subprocess.PIPE’.  Patch by Niklas Fiekas.

   - bpo-31855(87): *note unittest.mock.mock_open(): 1606. results now
     respects the argument of read([size]).  Patch contributed by Rémi
     Lapeyre.

   - bpo-35431(88): Implement *note math.comb(): 674. that returns
     binomial coefficient, that computes the number of ways to choose k
     items from n items without repetition and without order.  Patch by
     Yash Aggarwal and Keller Fuchs.

   - bpo-26660(89): Fixed permission errors in *note TemporaryDirectory:
     11cc. clean up.  Previously ‘TemporaryDirectory.cleanup()’ failed
     when non-writeable or non-searchable files or directories were
     created inside a temporary directory.

   - bpo-34271(90): Add debugging helpers to ssl module.  It's now
     possible to dump key material and to trace TLS protocol.  The
     default and stdlib contexts also support SSLKEYLOGFILE env var.

   - bpo-26467(91): Added AsyncMock to support using unittest to mock
     asyncio coroutines.  Patch by Lisa Roach.

   - bpo-33569(92): dataclasses.InitVar: Exposes the type used to create
     the init var.

   - bpo-34424(93): Fix serialization of messages containing encoded
     strings when the policy.linesep is set to a multi-character string.
     Patch by Jens Troeger.

   - bpo-34303(94): Performance of *note functools.reduce(): 126f. is
     slightly improved.  Patch by Sergey Fedoseev.

   - bpo-33361(95): Fix a bug in *note codecs.StreamRecoder: 18f6. where
     seeking might leave old data in a buffer and break subsequent read
     calls.  Patch by Ammar Askar.

   - bpo-22454(96): The *note shlex: b2. module now exposes *note
     shlex.join(): 9cb, the inverse of *note shlex.split(): 4e1.  Patch
     by Bo Bayles.

   - bpo-31922(97):
     ‘asyncio.AbstractEventLoop.create_datagram_endpoint()’: Do not
     connect UDP socket when broadcast is allowed.  This allows to
     receive replies after a UDP broadcast.

   - bpo-24882(98): Change ThreadPoolExecutor to use existing idle
     threads before spinning up new ones.

   - bpo-31961(99): Added support for bytes and path-like objects in
     *note subprocess.Popen(): 17d. on Windows.  The 'args' parameter
     now accepts a *note path-like object: ac2. if 'shell' is ‘False’
     and a sequence containing bytes and path-like objects.  The
     'executable' parameter now accepts a bytes and *note path-like
     object: ac2.  The 'cwd' parameter now accepts a bytes object.
     Based on patch by Anders Lorentsen.

   - bpo-33123(100): *note pathlib.Path.unlink: 18f7. now accepts a
     'missing_ok' parameter to avoid a *note FileNotFoundError: e67.
     from being raised.  Patch by Robert Buchholz.

   - bpo-32941(101): Allow *note mmap.mmap: 1f0. objects to access the
     madvise() system call (through *note mmap.mmap.madvise(): 9ac.).

   - bpo-22102(102): Added support for ZIP files with disks set to 0.
     Such files are commonly created by builtin tools on Windows when
     use ZIP64 extension.  Patch by Francisco Facioni.

   - bpo-32515(103): trace.py can now run modules via python3 -m trace
     -t -module module_name

   - bpo-32299(104): Changed *note unittest.mock.patch.dict(): 18f8. to
     return the patched dictionary when used as context manager.  Patch
     by Vadim Tsander.

   - bpo-27141(105): Added a ‘__copy__()’ to ‘collections.UserList’ and
     ‘collections.UserDict’ in order to correctly implement shallow
     copying of the objects.  Patch by Bar Harel.

   - bpo-31829(106): ‘\r’, ‘\0’ and ‘\x1a’ (end-of-file on Windows) are
     now escaped in protocol 0 pickles of Unicode strings.  This allows
     to load them without loss from files open in text mode in Python 2.

   - bpo-23395(107): ‘_thread.interrupt_main()’ now avoids setting the
     Python error status if the ‘SIGINT’ signal is ignored or not
     handled by Python.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=37128

   (2) https://bugs.python.org/issue?@action=redirect&bpo=37120

   (3) https://bugs.python.org/issue?@action=redirect&bpo=12202

   (4) https://bugs.python.org/issue?@action=redirect&bpo=26835

   (5) https://bugs.python.org/issue?@action=redirect&bpo=29262

   (6) https://bugs.python.org/issue?@action=redirect&bpo=12639

   (7) https://bugs.python.org/issue?@action=redirect&bpo=36999

   (8) https://bugs.python.org/issue?@action=redirect&bpo=35246

   (9) https://bugs.python.org/issue?@action=redirect&bpo=35279

   (10) https://bugs.python.org/issue?@action=redirect&bpo=37076

   (11) https://bugs.python.org/issue?@action=redirect&bpo=33725

   (12) https://bugs.python.org/issue?@action=redirect&bpo=37054

   (13) https://bugs.python.org/issue?@action=redirect&bpo=37058

   (14) https://bugs.python.org/issue?@action=redirect&bpo=36933

   (15) https://bugs.python.org/issue?@action=redirect&bpo=37047

   (16) https://bugs.python.org/issue?@action=redirect&bpo=37049

   (17) https://bugs.python.org/issue?@action=redirect&bpo=37046

   (18) https://bugs.python.org/issue?@action=redirect&bpo=37045

   (19) https://bugs.python.org/issue?@action=redirect&bpo=37035

   (20) https://bugs.python.org/issue?@action=redirect&bpo=37001

   (21) https://bugs.python.org/issue?@action=redirect&bpo=37028

   (22) https://bugs.python.org/issue?@action=redirect&bpo=37027

   (23) https://bugs.python.org/issue?@action=redirect&bpo=32528

   (24) https://bugs.python.org/issue?@action=redirect&bpo=1230540

   (25) https://bugs.python.org/issue?@action=redirect&bpo=36996

   (26) https://bugs.python.org/issue?@action=redirect&bpo=37008

   (27) https://bugs.python.org/issue?@action=redirect&bpo=27737

   (28) https://bugs.python.org/issue?@action=redirect&bpo=36969

   (29) https://bugs.python.org/issue?@action=redirect&bpo=36969

   (30) https://bugs.python.org/issue?@action=redirect&bpo=36983

   (31) https://bugs.python.org/issue?@action=redirect&bpo=36972

   (32) https://bugs.python.org/issue?@action=redirect&bpo=32972

   (33) https://bugs.python.org/issue?@action=redirect&bpo=36952

   (34) https://bugs.python.org/issue?@action=redirect&bpo=36952

   (35) https://bugs.python.org/issue?@action=redirect&bpo=36949

   (36) https://bugs.python.org/issue?@action=redirect&bpo=36948

   (37) https://bugs.python.org/issue?@action=redirect&bpo=33524

   (38) https://bugs.python.org/issue?@action=redirect&bpo=24564

   (39) https://bugs.python.org/issue?@action=redirect&bpo=36888

   (40) https://bugs.python.org/issue?@action=redirect&bpo=36921

   (41) https://bugs.python.org/issue?@action=redirect&bpo=25652

   (42) https://bugs.python.org/issue?@action=redirect&bpo=36916

   (43) https://bugs.python.org/issue?@action=redirect&bpo=36889

   (44) https://bugs.python.org/issue?@action=redirect&bpo=36845

   (45) https://bugs.python.org/issue?@action=redirect&bpo=23378

   (46) https://bugs.python.org/issue?@action=redirect&bpo=36867

   (47) https://bugs.python.org/issue?@action=redirect&bpo=23896

   (48) https://bugs.python.org/issue?@action=redirect&bpo=36895

   (49) https://bugs.python.org/issue?@action=redirect&bpo=35545

   (50) https://bugs.python.org/issue?@action=redirect&bpo=36887

   (51) https://bugs.python.org/issue?@action=redirect&bpo=34632

   (52) https://bugs.python.org/issue?@action=redirect&bpo=36878

   (53) https://bugs.python.org/issue?@action=redirect&bpo=36778

   (54) https://bugs.python.org/issue?@action=redirect&bpo=36867

   (55) https://bugs.python.org/issue?@action=redirect&bpo=30262

   (56) https://bugs.python.org/issue?@action=redirect&bpo=24538

   (57) https://bugs.python.org/issue?@action=redirect&bpo=36829

   (58) https://bugs.python.org/issue?@action=redirect&bpo=36832

   (59) https://bugs.python.org/issue?@action=redirect&bpo=36814

   (60) https://bugs.python.org/issue?@action=redirect&bpo=33110

   (61) https://bugs.python.org/issue?@action=redirect&bpo=26903

   (62) https://bugs.python.org/issue?@action=redirect&bpo=36813

   (63) https://bugs.python.org/issue?@action=redirect&bpo=36806

   (64) https://bugs.python.org/issue?@action=redirect&bpo=36802

   (65) https://bugs.python.org/issue?@action=redirect&bpo=36801

   (66) https://bugs.python.org/issue?@action=redirect&bpo=36785

   (67) https://bugs.python.org/issue?@action=redirect&bpo=36772

   (68) https://bugs.python.org/issue?@action=redirect&bpo=6584

   (69) https://bugs.python.org/issue?@action=redirect&bpo=36748

   (70) https://bugs.python.org/issue?@action=redirect&bpo=8138

   (71) https://bugs.python.org/issue?@action=redirect&bpo=22640

   (72) https://bugs.python.org/issue?@action=redirect&bpo=29183

   (73) https://bugs.python.org/issue?@action=redirect&bpo=36548

   (74) https://bugs.python.org/issue?@action=redirect&bpo=36542

   (75) https://bugs.python.org/issue?@action=redirect&bpo=36533

   (76) https://bugs.python.org/issue?@action=redirect&bpo=35252

   (77) https://bugs.python.org/issue?@action=redirect&bpo=35900

   (78) https://bugs.python.org/issue?@action=redirect&bpo=35900

   (79) https://bugs.python.org/issue?@action=redirect&bpo=36368

   (80) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (81) https://bugs.python.org/issue?@action=redirect&bpo=27497

   (82) https://bugs.python.org/issue?@action=redirect&bpo=36239

   (83) https://bugs.python.org/issue?@action=redirect&bpo=26707

   (84) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (85) https://bugs.python.org/issue?@action=redirect&bpo=35125

   (86) https://bugs.python.org/issue?@action=redirect&bpo=35721

   (87) https://bugs.python.org/issue?@action=redirect&bpo=31855

   (88) https://bugs.python.org/issue?@action=redirect&bpo=35431

   (89) https://bugs.python.org/issue?@action=redirect&bpo=26660

   (90) https://bugs.python.org/issue?@action=redirect&bpo=34271

   (91) https://bugs.python.org/issue?@action=redirect&bpo=26467

   (92) https://bugs.python.org/issue?@action=redirect&bpo=33569

   (93) https://bugs.python.org/issue?@action=redirect&bpo=34424

   (94) https://bugs.python.org/issue?@action=redirect&bpo=34303

   (95) https://bugs.python.org/issue?@action=redirect&bpo=33361

   (96) https://bugs.python.org/issue?@action=redirect&bpo=22454

   (97) https://bugs.python.org/issue?@action=redirect&bpo=31922

   (98) https://bugs.python.org/issue?@action=redirect&bpo=24882

   (99) https://bugs.python.org/issue?@action=redirect&bpo=31961

   (100) https://bugs.python.org/issue?@action=redirect&bpo=33123

   (101) https://bugs.python.org/issue?@action=redirect&bpo=32941

   (102) https://bugs.python.org/issue?@action=redirect&bpo=22102

   (103) https://bugs.python.org/issue?@action=redirect&bpo=32515

   (104) https://bugs.python.org/issue?@action=redirect&bpo=32299

   (105) https://bugs.python.org/issue?@action=redirect&bpo=27141

   (106) https://bugs.python.org/issue?@action=redirect&bpo=31829

   (107) https://bugs.python.org/issue?@action=redirect&bpo=23395


File: python.info,  Node: Documentation<39>,  Next: Tests<41>,  Prev: Library<44>,  Up: Python 3 8 0 beta 1

1.23.45.4 Documentation
.......................

   - bpo-36896(1): Clarify that some types have unstable constructor
     signature between Python versions.

   - bpo-36686(2): Improve documentation of the stdin, stdout, and
     stderr arguments of the ‘asyncio.subprocess_exec’ function to
     specify which values are supported.  Also mention that decoding as
     text is not supported.

     Add a few tests to verify that the various values passed to the
     std* arguments actually work.

   - bpo-36984(3): Improve version added references in ‘typing’ module -
     by Anthony Sottile.

   - bpo-36868(4): What's new now mentions
     SSLContext.hostname_checks_common_name instead of
     SSLContext.host_flags.

   - bpo-35924(5): Add a note to the ‘curses.addstr()’ documentation to
     warn that multiline strings can cause segfaults because of an
     ncurses bug.

   - bpo-36783(6): Added C API Documentation for Time_FromTimeAndFold
     and PyDateTime_FromDateAndTimeAndFold as per PEP 495.  Patch by
     Edison Abahurire.

   - bpo-36797(7): More of the legacy distutils documentation has been
     either pruned, or else more clearly marked as being retained solely
     until the setuptools documentation covers it independently.

   - bpo-22865(8): Add detail to the documentation on the ‘pty.spawn’
     function.

   - bpo-35397(9): Remove deprecation and document
     urllib.parse.unwrap().  Patch contributed by Rémi Lapeyre.

   - bpo-32995(10): Added the context variable in glossary.

   - bpo-33519(11): Clarify that ‘copy()’ is not part of the
     ‘MutableSequence’ ABC.

   - bpo-33482(12): Make ‘codecs.StreamRecoder.writelines’ take a list
     of bytes.

   - bpo-25735(13): Added documentation for func factorial to indicate
     that returns integer values

   - bpo-20285(14): Expand object.__doc__ (docstring) to make it
     clearer.  Modify pydoc.py so that help(object) lists object methods
     (for other classes, help omits methods of the object base class.)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36896

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36686

   (3) https://bugs.python.org/issue?@action=redirect&bpo=36984

   (4) https://bugs.python.org/issue?@action=redirect&bpo=36868

   (5) https://bugs.python.org/issue?@action=redirect&bpo=35924

   (6) https://bugs.python.org/issue?@action=redirect&bpo=36783

   (7) https://bugs.python.org/issue?@action=redirect&bpo=36797

   (8) https://bugs.python.org/issue?@action=redirect&bpo=22865

   (9) https://bugs.python.org/issue?@action=redirect&bpo=35397

   (10) https://bugs.python.org/issue?@action=redirect&bpo=32995

   (11) https://bugs.python.org/issue?@action=redirect&bpo=33519

   (12) https://bugs.python.org/issue?@action=redirect&bpo=33482

   (13) https://bugs.python.org/issue?@action=redirect&bpo=25735

   (14) https://bugs.python.org/issue?@action=redirect&bpo=20285


File: python.info,  Node: Tests<41>,  Next: Build<44>,  Prev: Documentation<39>,  Up: Python 3 8 0 beta 1

1.23.45.5 Tests
...............

   - bpo-37069(1): Modify test_coroutines, test_cprofile,
     test_generators, test_raise, test_ssl and test_yield_from to use
     *note test.support.catch_unraisable_exception(): 18dd. rather than
     *note test.support.captured_stderr(): 18fb.

   - bpo-37098(2): Fix test_memfd_create on older Linux Kernels.

   - bpo-37081(3): Test with OpenSSL 1.1.1c

   - bpo-36829(4): Add *note test.support.catch_unraisable_exception():
     18dd.: context manager catching unraisable exception using *note
     sys.unraisablehook(): 1dc.

   - bpo-36915(5): The main regrtest process now always removes all
     temporary directories of worker processes even if they crash or if
     they are killed on KeyboardInterrupt (CTRL+c).

   - bpo-36719(6): "python3 -m test -jN ..."  now continues the
     execution of next tests when a worker process crash (CHILD_ERROR
     state).  Previously, the test suite stopped immediately.  Use
     -failfast to stop at the first error.

   - bpo-36816(7): Update Lib/test/selfsigned_pythontestdotnet.pem to
     match self-signed.pythontest.net's new TLS certificate.

   - bpo-35925(8): Skip httplib and nntplib networking tests when they
     would otherwise fail due to a modern OS or distro with a default
     OpenSSL policy of rejecting connections to servers with weak
     certificates.

   - bpo-36782(9): Add tests for several C API functions in the *note
     datetime: 28. module.  Patch by Edison Abahurire.

   - bpo-36342(10): Fix test_multiprocessing in test_venv if platform
     lacks functioning sem_open.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=37069

   (2) https://bugs.python.org/issue?@action=redirect&bpo=37098

   (3) https://bugs.python.org/issue?@action=redirect&bpo=37081

   (4) https://bugs.python.org/issue?@action=redirect&bpo=36829

   (5) https://bugs.python.org/issue?@action=redirect&bpo=36915

   (6) https://bugs.python.org/issue?@action=redirect&bpo=36719

   (7) https://bugs.python.org/issue?@action=redirect&bpo=36816

   (8) https://bugs.python.org/issue?@action=redirect&bpo=35925

   (9) https://bugs.python.org/issue?@action=redirect&bpo=36782

   (10) https://bugs.python.org/issue?@action=redirect&bpo=36342


File: python.info,  Node: Build<44>,  Next: Windows<39>,  Prev: Tests<41>,  Up: Python 3 8 0 beta 1

1.23.45.6 Build
...............

   - bpo-36721(1): To embed Python into an application, a new ‘--embed’
     option must be passed to ‘python3-config --libs --embed’ to get
     ‘-lpython3.8’ (link the application to libpython).  To support both
     3.8 and older, try ‘python3-config --libs --embed’ first and
     fallback to ‘python3-config --libs’ (without ‘--embed’) if the
     previous command fails.

     Add a pkg-config ‘python-3.8-embed’ module to embed Python into an
     application: ‘pkg-config python-3.8-embed --libs’ includes
     ‘-lpython3.8’.  To support both 3.8 and older, try ‘pkg-config
     python-X.Y-embed --libs’ first and fallback to ‘pkg-config
     python-X.Y --libs’ (without ‘--embed’) if the previous command
     fails (replace ‘X.Y’ with the Python version).

     On the other hand, ‘pkg-config python3.8 --libs’ no longer contains
     ‘-lpython3.8’.  C extensions must not be linked to libpython
     (except on Android, case handled by the script); this change is
     backward incompatible on purpose.

   - bpo-36786(2): "make install" now runs compileall in parallel.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36721

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36786


File: python.info,  Node: Windows<39>,  Next: macOS<33>,  Prev: Build<44>,  Up: Python 3 8 0 beta 1

1.23.45.7 Windows
.................

   - bpo-36965(1): include of STATUS_CONTROL_C_EXIT without depending on
     MSC compiler

   - bpo-35926(2): Update to OpenSSL 1.1.1b for Windows.

   - bpo-29883(3): Add Windows support for UDP transports for the
     Proactor Event Loop.  Patch by Adam Meily.

   - bpo-33407(4): The *note Py_DEPRECATED(): a47. macro has been
     implemented for MSVC.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36965

   (2) https://bugs.python.org/issue?@action=redirect&bpo=35926

   (3) https://bugs.python.org/issue?@action=redirect&bpo=29883

   (4) https://bugs.python.org/issue?@action=redirect&bpo=33407


File: python.info,  Node: macOS<33>,  Next: IDLE<31>,  Prev: Windows<39>,  Up: Python 3 8 0 beta 1

1.23.45.8 macOS
...............

   - bpo-36231(1): Support building Python on macOS without /usr/include
     installed.  As of macOS 10.14, system header files are only
     available within an SDK provided by either the Command Line Tools
     or the Xcode app.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36231


File: python.info,  Node: IDLE<31>,  Next: Tools/Demos<20>,  Prev: macOS<33>,  Up: Python 3 8 0 beta 1

1.23.45.9 IDLE
..............

   - bpo-35610(1): Replace now redundant .context_use_ps1 with
     .prompt_last_line.  This finishes change started in bpo-31858(2).

   - bpo-37038(3): Make idlelib.run runnable; add test clause.

   - bpo-36958(4): Print any argument other than None or int passed to
     SystemExit or sys.exit().

   - bpo-36807(5): When saving a file, call os.fsync() so bits are
     flushed to e.g.  USB drive.

   - bpo-32411(6): In browser.py, remove extraneous sorting by line
     number since dictionary was created in line number order.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35610

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31858

   (3) https://bugs.python.org/issue?@action=redirect&bpo=37038

   (4) https://bugs.python.org/issue?@action=redirect&bpo=36958

   (5) https://bugs.python.org/issue?@action=redirect&bpo=36807

   (6) https://bugs.python.org/issue?@action=redirect&bpo=32411


File: python.info,  Node: Tools/Demos<20>,  Next: C API<43>,  Prev: IDLE<31>,  Up: Python 3 8 0 beta 1

1.23.45.10 Tools/Demos
......................

   - bpo-37053(1): Handle strings like u"bar" correctly in
     Tools/parser/unparse.py.  Patch by Chih-Hsuan Yen.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=37053


File: python.info,  Node: C API<43>,  Prev: Tools/Demos<20>,  Up: Python 3 8 0 beta 1

1.23.45.11 C API
................

   - bpo-36763(1): Implement the PEP 587(2) "Python Initialization
     Configuration".

   - bpo-36379(3): Fix crashes when attempting to use the 'modulo'
     parameter when ‘__ipow__’ is implemented in C.

   - bpo-37107(4): Update *note PyObject_CallMethodObjArgs(): 1902. and
     ‘_PyObject_CallMethodIdObjArgs’ to use ‘_PyObject_GetMethod’ to
     avoid creating a bound method object in many cases.  Patch by
     Michael J. Sullivan.

   - bpo-36974(5): Implement PEP 590(6): Vectorcall: a fast calling
     protocol for CPython.  This is a new protocol to optimize calls of
     custom callable objects.

   - bpo-36763(7): ‘Py_Main()’ now returns the exitcode rather than
     calling ‘Py_Exit(exitcode)’ when calling ‘PyErr_Print()’ if the
     current exception type is ‘SystemExit’.

   - bpo-36922(8): Add new type flag ‘Py_TPFLAGS_METHOD_DESCRIPTOR’ for
     objects behaving like unbound methods.  These are objects
     supporting the optimization given by the
     ‘LOAD_METHOD’/‘CALL_METHOD’ opcodes.  See PEP 590.

   - bpo-36728(9): The ‘PyEval_ReInitThreads()’ function has been
     removed from the C API. It should not be called explicitly: use
     *note PyOS_AfterFork_Child(): 3c3. instead.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36763

   (2) https://peps.python.org/pep-0587/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=36379

   (4) https://bugs.python.org/issue?@action=redirect&bpo=37107

   (5) https://bugs.python.org/issue?@action=redirect&bpo=36974

   (6) https://peps.python.org/pep-0590/

   (7) https://bugs.python.org/issue?@action=redirect&bpo=36763

   (8) https://bugs.python.org/issue?@action=redirect&bpo=36922

   (9) https://bugs.python.org/issue?@action=redirect&bpo=36728


File: python.info,  Node: Python 3 8 0 alpha 4,  Next: Python 3 8 0 alpha 3,  Prev: Python 3 8 0 beta 1,  Up: Changelog（更動日誌）

1.23.46 Python 3.8.0 alpha 4
----------------------------

'Release date: 2019-05-06'

* Menu:

* Security: Security<31>.
* Core and Builtins: Core and Builtins<46>.
* Library: Library<45>.
* Documentation: Documentation<40>.
* Tests: Tests<42>.
* Build: Build<45>.
* Windows: Windows<40>.
* macOS: macOS<34>.
* IDLE: IDLE<32>.
* Tools/Demos: Tools/Demos<21>.
* C API: C API<44>.


File: python.info,  Node: Security<31>,  Next: Core and Builtins<46>,  Up: Python 3 8 0 alpha 4

1.23.46.1 Security
..................

   - bpo-36742(1): Fixes mishandling of pre-normalization characters in
     urlsplit().

   - bpo-30458(2): Address CVE-2019-9740(3) by disallowing URL paths
     with embedded whitespace or control characters through into the
     underlying http client request.  Such potentially malicious header
     injection URLs now cause an http.client.InvalidURL exception to be
     raised.

   - bpo-35755(4): *note shutil.which(): 45b. now uses
     ‘os.confstr("CS_PATH")’ if available and if the ‘PATH’ environment
     variable is not set.  Remove also the current directory from
     ‘posixpath.defpath’.  On Unix, *note shutil.which(): 45b. and the
     *note subprocess: c1. module no longer search the executable in the
     current directory if the ‘PATH’ environment variable is not set.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36742

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30458

   (3) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9740

   (4) https://bugs.python.org/issue?@action=redirect&bpo=35755


File: python.info,  Node: Core and Builtins<46>,  Next: Library<45>,  Prev: Security<31>,  Up: Python 3 8 0 alpha 4

1.23.46.2 Core and Builtins
...........................

   - bpo-36722(1): In debug build, import now also looks for C
     extensions compiled in release mode and for C extensions compiled
     in the stable ABI.

   - bpo-32849(2): Fix Python Initialization code on FreeBSD to detect
     properly when stdin file descriptor (fd 0) is invalid.

   - bpo-36623(3): Remove parser headers and related function
     declarations that lack implementations after the removal of pgen.

   - bpo-20180(4): ‘dict.pop()’ is now up to 33% faster thanks to
     Argument Clinic.  Patch by Inada Naoki.

   - bpo-36611(5): Debug memory allocators: disable serialno field by
     default from debug hooks on Python memory allocators to reduce the
     memory footprint by 5%.  Enable *note tracemalloc: e8. to get the
     traceback where a memory block has been allocated when a fatal
     memory error is logged to decide where to put a breakpoint.
     Compile Python with ‘PYMEM_DEBUG_SERIALNO’ defined to get back the
     field.

   - bpo-36588(6): On AIX, *note sys.platform: a30. doesn't contain the
     major version anymore.  Always return ‘'aix'’, instead of ‘'aix3'’
     ..  ‘'aix7'’.  Since older Python versions include the version
     number, it is recommended to always use
     ‘sys.platform.startswith('aix')’.  Contributed by M. Felt.

   - bpo-36549(7): Change str.capitalize to use titlecase for the first
     character instead of uppercase.

   - bpo-36540(8): Implement PEP 570(9) (Python positional-only
     parameters).  Patch by Pablo Galindo.

   - bpo-36475(10): ‘PyEval_AcquireLock()’ and ‘PyEval_AcquireThread()’
     now terminate the current thread if called while the interpreter is
     finalizing, making them consistent with *note
     PyEval_RestoreThread(): 374, *note Py_END_ALLOW_THREADS(): a31, and
     *note PyGILState_Ensure(): 376.

   - bpo-36504(11): Fix signed integer overflow in _ctypes.c's
     ‘PyCArrayType_new()’.

   - bpo-20844(12): Fix running script with encoding cookie and LF line
     ending may fail on Windows.

   - bpo-24214(13): Fixed support of the surrogatepass error handler in
     the UTF-8 incremental decoder.

   - bpo-36452(14): Changing ‘dict’ keys during iteration of the dict
     itself, ‘keys()’, ‘values()’, or ‘items()’ will now be detected in
     certain corner cases where keys are deleted/added so that the
     number of keys isn't changed.  A ‘RuntimeError’ will be raised
     after ‘len(dict)’ iterations.  Contributed by Thomas Perl.

   - bpo-36459(15): Fix a possible double ‘PyMem_FREE()’ due to
     tokenizer.c's ‘tok_nextc()’.

   - bpo-36433(16): Fixed TypeError message in classmethoddescr_call.

   - bpo-36430(17): Fix a possible reference leak in *note
     itertools.count(): 121b.

   - bpo-36440(18): Include node names in ‘ParserError’ messages,
     instead of numeric IDs.  Patch by A. Skrobov.

   - bpo-36143(19): Regenerate *note keyword: 78. from the Grammar and
     Tokens file using pgen.  Patch by Pablo Galindo.

   - bpo-18372(20): Add missing *note PyObject_GC_Track(): 1474. calls
     in the *note pickle: 95. module.  Patch by Zackery Spytz.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36722

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32849

   (3) https://bugs.python.org/issue?@action=redirect&bpo=36623

   (4) https://bugs.python.org/issue?@action=redirect&bpo=20180

   (5) https://bugs.python.org/issue?@action=redirect&bpo=36611

   (6) https://bugs.python.org/issue?@action=redirect&bpo=36588

   (7) https://bugs.python.org/issue?@action=redirect&bpo=36549

   (8) https://bugs.python.org/issue?@action=redirect&bpo=36540

   (9) https://peps.python.org/pep-0570/

   (10) https://bugs.python.org/issue?@action=redirect&bpo=36475

   (11) https://bugs.python.org/issue?@action=redirect&bpo=36504

   (12) https://bugs.python.org/issue?@action=redirect&bpo=20844

   (13) https://bugs.python.org/issue?@action=redirect&bpo=24214

   (14) https://bugs.python.org/issue?@action=redirect&bpo=36452

   (15) https://bugs.python.org/issue?@action=redirect&bpo=36459

   (16) https://bugs.python.org/issue?@action=redirect&bpo=36433

   (17) https://bugs.python.org/issue?@action=redirect&bpo=36430

   (18) https://bugs.python.org/issue?@action=redirect&bpo=36440

   (19) https://bugs.python.org/issue?@action=redirect&bpo=36143

   (20) https://bugs.python.org/issue?@action=redirect&bpo=18372


File: python.info,  Node: Library<45>,  Next: Documentation<40>,  Prev: Core and Builtins<46>,  Up: Python 3 8 0 alpha 4

1.23.46.3 Library
.................

   - bpo-35952(1): Fix pythoninfo when the compiler is missing.

   - bpo-28238(2): The ‘.find*()’ methods of xml.etree.ElementTree can
     now search for wildcards like ‘{*}tag’ and ‘{ns}*’ that match a tag
     in any namespace or all tags in a namespace.  Patch by Stefan
     Behnel.

   - bpo-26978(3): ‘pathlib.path.link_to()’ is now implemented.  It
     creates a hard link pointing to a path.

   - bpo-1613500(4): *note fileinput.FileInput: 6db. now uses the input
     file mode to correctly set the output file mode (previously it was
     hardcoded to ‘'w'’) when ‘inplace=True’ is passed to its
     constructor.

   - bpo-36734(5): Fix compilation of ‘faulthandler.c’ on HP-UX.
     Initialize ‘stack_t current_stack’ to zero using ‘memset()’.

   - bpo-13611(6): The xml.etree.ElementTree packages gained support for
     C14N 2.0 serialisation.  Patch by Stefan Behnel.

   - bpo-36669(7): Add missing matrix multiplication operator support to
     weakref.proxy.

   - bpo-36676(8): The XMLParser() in xml.etree.ElementTree provides
     namespace prefix context to the parser target if it defines the
     callback methods "start_ns()" and/or "end_ns()".  Patch by Stefan
     Behnel.

   - bpo-36673(9): The TreeBuilder and XMLPullParser in
     xml.etree.ElementTree gained support for parsing comments and
     processing instructions.  Patch by Stefan Behnel.

   - bpo-36650(10): The C version of functools.lru_cache() was treating
     calls with an empty ‘**kwargs’ dictionary as being distinct from
     calls with no keywords at all.  This did not result in an incorrect
     answer, but it did trigger an unexpected cache miss.

   - bpo-28552(11): Fix ‘distutils.sysconfig’ if *note sys.executable:
     383. is ‘None’ or an empty string: use *note os.getcwd(): 1907. to
     initialize ‘project_base’.  Fix also the distutils build command:
     don't use *note sys.executable: 383. if it is ‘None’ or an empty
     string.

   - bpo-35755(12): *note shutil.which(): 45b. and
     ‘distutils.spawn.find_executable’ now use ‘os.confstr("CS_PATH")’
     if available instead of *note os.defpath: 1908, if the ‘PATH’
     environment variable is not set.  Moreover, don't use
     ‘os.confstr("CS_PATH")’ nor *note os.defpath: 1908. if the ‘PATH’
     environment variable is set to an empty string.

   - bpo-25430(13): improve performance of ‘IPNetwork.__contains__()’

   - bpo-30485(14): Path expressions in xml.etree.ElementTree can now
     avoid explicit namespace prefixes for tags (or the "{namespace}tag"
     notation) by passing a default namespace with an empty string
     prefix.

   - bpo-36613(15): Fix *note asyncio: 8. wait() not removing callback
     if exception

   - bpo-36598(16): Fix ‘isinstance’ check for Mock objects with spec
     when the code is executed under tracing.  Patch by Karthikeyan
     Singaravelan.

   - bpo-18748(17): In development mode (*note -X: 15a. ‘dev’) and in
     debug build, the *note io.IOBase: 1da. destructor now logs
     ‘close()’ exceptions.  These exceptions are silent by default in
     release mode.

   - bpo-36575(18): The ‘_lsprof’ module now uses internal timer same to
     ‘time.perf_counter()’ by default.  ‘gettimeofday(2)’ was used on
     Unix.  New timer has better resolution on most Unix platforms and
     timings are no longer impacted by system clock updates since
     ‘perf_counter()’ is monotonic.  Patch by Inada Naoki.

   - bpo-33461(19): ‘json.loads’ now emits ‘DeprecationWarning’ when
     ‘encoding’ option is specified.  Patch by Matthias Bussonnier.

   - bpo-36559(20): The random module now prefers the lean internal
     _sha512 module over hashlib for seed(version=2) to optimize import
     time.

   - bpo-17561(21): Set backlog=None as the default for
     socket.create_server.

   - bpo-34373(22): Fix *note time.mktime(): 1180. error handling on AIX
     for year before 1970.

   - bpo-36232(23): Improve error message when trying to open existing
     DBM database that actually doesn't exist.  Patch by Marco Rougeth.

   - bpo-36546(24): Add statistics.quantiles()

   - bpo-36050(25): Optimized ‘http.client.HTTPResponse.read()’ for
     large response.  Patch by Inada Naoki.

   - bpo-36522(26): If 'debuglevel' is set to >0 in *note http.client:
     65, print all values for headers with multiple values for the same
     header name.  Patch by Matt Houglum.

   - bpo-36492(27): Deprecated passing required arguments like 'func' as
     keyword arguments in functions which should accept arbitrary
     keyword arguments and pass them to other function.  Arbitrary
     keyword arguments (even with names "self" and "func") can now be
     passed to these functions if the required arguments are passed as
     positional arguments.

   - bpo-27181(28): Add statistics.geometric_mean().

   - bpo-30427(29): ‘os.path.normcase()’ relies on ‘os.fspath()’ to
     check the type of its argument.  Redundant checks have been removed
     from its ‘posixpath.normcase()’ and ‘ntpath.normcase()’
     implementations.  Patch by Wolfgang Maier.

   - bpo-36385(30): Stop rejecting IPv4 octets for being ambiguously
     octal.  Leading zeros are ignored, and no longer are assumed to
     specify octal octets.  Octets are always decimal numbers.  Octets
     must still be no more than three digits, including leading zeroes.

   - bpo-36434(31): Errors during writing to a ZIP file no longer
     prevent to properly close it.

   - bpo-36407(32): Fixed wrong indentation writing for CDATA section in
     xml.dom.minidom.  Patch by Vladimir Surjaninov.

   - bpo-36326(33): inspect.getdoc() can now find docstrings for member
     objects when __slots__ is a dictionary.

   - bpo-36366(34): Calling ‘stop()’ on an unstarted or stopped *note
     unittest.mock.patch(): e34. object will now return ‘None’ instead
     of raising *note RuntimeError: 179, making the method idempotent.
     Patch by Karthikeyan Singaravelan.

   - bpo-36348(35): The ‘imap.IMAP4.logout()’ method no longer ignores
     silently arbitrary exceptions.

   - bpo-31904(36): Add time module support and fix test_time failures
     for VxWorks.

   - bpo-36227(37): Added support for keyword arguments
     ‘default_namespace’ and ‘xml_declaration’ in functions
     ‘ElementTree.tostring()’ and ‘ElementTree.tostringlist()’.

   - bpo-36004(38): Added new alternate constructors *note
     datetime.date.fromisocalendar(): 990. and *note
     datetime.datetime.fromisocalendar(): 991, which construct date
     objects from ISO year, week number and weekday; these are the
     inverse of each class's ‘isocalendar’ method.  Patch by Paul
     Ganssle.

   - bpo-35936(39): *note modulefinder: 84. no longer depends on the
     deprecated ‘imp’ module, and the initializer for *note
     modulefinder.ModuleFinder: 1909. now has immutable default
     arguments.  Patch by Brandt Bucher.

   - bpo-35376(40): *note modulefinder: 84. correctly handles modules
     that have the same name as a bad package.  Patch by Brandt Bucher.

   - bpo-17396(41): *note modulefinder: 84. no longer crashes when
     encountering syntax errors in followed imports.  Patch by Brandt
     Bucher.

   - bpo-35934(42): Added *note create_server(): 9cf. and *note
     has_dualstack_ipv6(): 9d0. convenience functions to automate the
     necessary tasks usually involved when creating a server socket,
     including accepting both IPv4 and IPv6 connections on the same
     socket.  (Contributed by Giampaolo Rodola in bpo-17561(43).)

   - bpo-23078(44): Add support for *note classmethod(): 14a. and *note
     staticmethod(): 358. to *note unittest.mock.create_autospec():
     14fb.  Initial patch by Felipe Ochoa.

   - bpo-35416(45): Fix potential resource warnings in distutils.  Patch
     by Mickaël Schoentgen.

   - bpo-25451(46): Add transparency methods to ‘tkinter.PhotoImage’.
     Patch by Zackery Spytz.

   - bpo-35082(47): Don't return deleted attributes when calling dir on
     a *note unittest.mock.Mock: 9ef.

   - bpo-34547(48): *note wsgiref.handlers.BaseHandler: 18f5. now
     handles abrupt client connection terminations gracefully.  Patch by
     Petter Strandmark.

   - bpo-31658(49): *note xml.sax.parse(): 190a. now supports *note
     path-like: ac2.  Patch by Mickaël Schoentgen.

   - bpo-34139(50): Remove stale unix datagram socket before binding

   - bpo-33530(51): Implemented Happy Eyeballs in
     ‘asyncio.create_connection()’.  Added two new arguments,
     'happy_eyeballs_delay' and 'interleave', to specify Happy Eyeballs
     behavior.

   - bpo-33291(52): Do not raise AttributeError when calling the inspect
     functions isgeneratorfunction, iscoroutinefunction,
     isasyncgenfunction on a method created from an arbitrary callable.
     Instead, return False.

   - bpo-31310(53): Fix the multiprocessing.semaphore_tracker so it is
     reused by child processes

   - bpo-31292(54): Fix ‘setup.py check --restructuredtext’ for files
     containing ‘include’ directives.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35952

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28238

   (3) https://bugs.python.org/issue?@action=redirect&bpo=26978

   (4) https://bugs.python.org/issue?@action=redirect&bpo=1613500

   (5) https://bugs.python.org/issue?@action=redirect&bpo=36734

   (6) https://bugs.python.org/issue?@action=redirect&bpo=13611

   (7) https://bugs.python.org/issue?@action=redirect&bpo=36669

   (8) https://bugs.python.org/issue?@action=redirect&bpo=36676

   (9) https://bugs.python.org/issue?@action=redirect&bpo=36673

   (10) https://bugs.python.org/issue?@action=redirect&bpo=36650

   (11) https://bugs.python.org/issue?@action=redirect&bpo=28552

   (12) https://bugs.python.org/issue?@action=redirect&bpo=35755

   (13) https://bugs.python.org/issue?@action=redirect&bpo=25430

   (14) https://bugs.python.org/issue?@action=redirect&bpo=30485

   (15) https://bugs.python.org/issue?@action=redirect&bpo=36613

   (16) https://bugs.python.org/issue?@action=redirect&bpo=36598

   (17) https://bugs.python.org/issue?@action=redirect&bpo=18748

   (18) https://bugs.python.org/issue?@action=redirect&bpo=36575

   (19) https://bugs.python.org/issue?@action=redirect&bpo=33461

   (20) https://bugs.python.org/issue?@action=redirect&bpo=36559

   (21) https://bugs.python.org/issue?@action=redirect&bpo=17561

   (22) https://bugs.python.org/issue?@action=redirect&bpo=34373

   (23) https://bugs.python.org/issue?@action=redirect&bpo=36232

   (24) https://bugs.python.org/issue?@action=redirect&bpo=36546

   (25) https://bugs.python.org/issue?@action=redirect&bpo=36050

   (26) https://bugs.python.org/issue?@action=redirect&bpo=36522

   (27) https://bugs.python.org/issue?@action=redirect&bpo=36492

   (28) https://bugs.python.org/issue?@action=redirect&bpo=27181

   (29) https://bugs.python.org/issue?@action=redirect&bpo=30427

   (30) https://bugs.python.org/issue?@action=redirect&bpo=36385

   (31) https://bugs.python.org/issue?@action=redirect&bpo=36434

   (32) https://bugs.python.org/issue?@action=redirect&bpo=36407

   (33) https://bugs.python.org/issue?@action=redirect&bpo=36326

   (34) https://bugs.python.org/issue?@action=redirect&bpo=36366

   (35) https://bugs.python.org/issue?@action=redirect&bpo=36348

   (36) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (37) https://bugs.python.org/issue?@action=redirect&bpo=36227

   (38) https://bugs.python.org/issue?@action=redirect&bpo=36004

   (39) https://bugs.python.org/issue?@action=redirect&bpo=35936

   (40) https://bugs.python.org/issue?@action=redirect&bpo=35376

   (41) https://bugs.python.org/issue?@action=redirect&bpo=17396

   (42) https://bugs.python.org/issue?@action=redirect&bpo=35934

   (43) https://bugs.python.org/issue?@action=redirect&bpo=17561

   (44) https://bugs.python.org/issue?@action=redirect&bpo=23078

   (45) https://bugs.python.org/issue?@action=redirect&bpo=35416

   (46) https://bugs.python.org/issue?@action=redirect&bpo=25451

   (47) https://bugs.python.org/issue?@action=redirect&bpo=35082

   (48) https://bugs.python.org/issue?@action=redirect&bpo=34547

   (49) https://bugs.python.org/issue?@action=redirect&bpo=31658

   (50) https://bugs.python.org/issue?@action=redirect&bpo=34139

   (51) https://bugs.python.org/issue?@action=redirect&bpo=33530

   (52) https://bugs.python.org/issue?@action=redirect&bpo=33291

   (53) https://bugs.python.org/issue?@action=redirect&bpo=31310

   (54) https://bugs.python.org/issue?@action=redirect&bpo=31292


File: python.info,  Node: Documentation<40>,  Next: Tests<42>,  Prev: Library<45>,  Up: Python 3 8 0 alpha 4

1.23.46.4 Documentation
.......................

   - bpo-36625(1): Remove obsolete comments from docstrings in
     fractions.Fraction

   - bpo-30840(2): Document relative imports

   - bpo-36523(3): Add docstring for io.IOBase.writelines().

   - bpo-36425(4): New documentation translation: Simplified Chinese(5).

   - bpo-36345(6): Avoid the duplication of code from
     ‘Tools/scripts/serve.py’ in using the ‘literalinclude’ directive
     for the basic wsgiref-based web server in the documentation of
     *note wsgiref: 100.  Contributed by Stéphane Wirtel.

   - bpo-36345(7): Using the code of the ‘Tools/scripts/serve.py’ script
     as an example in the *note wsgiref: 100. documentation.
     Contributed by Stéphane Wirtel.

   - bpo-36157(8): Added documentation for PyInterpreterState_Main().

   - bpo-33043(9): Updates the docs.python.org page with the addition of
     a 'Contributing to Docs' link at the end of the page (between
     'Reporting Bugs' and 'About Documentation').  Updates the 'Found a
     Bug' page with additional links and information in the
     Documentation Bugs section.

   - bpo-35581(10): @typing.type_check_only now allows type stubs to
     mark functions and classes not available during runtime.

   - bpo-33832(11): Add glossary entry for 'magic method'.

   - bpo-32913(12): Added re.Match.groupdict example to regex HOWTO.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36625

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30840

   (3) https://bugs.python.org/issue?@action=redirect&bpo=36523

   (4) https://bugs.python.org/issue?@action=redirect&bpo=36425

   (5) https://docs.python.org/zh-cn/

   (6) https://bugs.python.org/issue?@action=redirect&bpo=36345

   (7) https://bugs.python.org/issue?@action=redirect&bpo=36345

   (8) https://bugs.python.org/issue?@action=redirect&bpo=36157

   (9) https://bugs.python.org/issue?@action=redirect&bpo=33043

   (10) https://bugs.python.org/issue?@action=redirect&bpo=35581

   (11) https://bugs.python.org/issue?@action=redirect&bpo=33832

   (12) https://bugs.python.org/issue?@action=redirect&bpo=32913


File: python.info,  Node: Tests<42>,  Next: Build<45>,  Prev: Documentation<40>,  Up: Python 3 8 0 alpha 4

1.23.46.5 Tests
...............

   - bpo-36719(1): regrtest now always detects uncollectable objects.
     Previously, the check was only enabled by ‘--findleaks’.  The check
     now also works with ‘-jN/--multiprocess N’.  ‘--findleaks’ becomes
     a deprecated alias to ‘--fail-env-changed’.

   - bpo-36725(2): When using multiprocessing mode (-jN), regrtest now
     better reports errors if a worker process fails, and it exits
     immediately on a worker thread failure or when interrupted.

   - bpo-36454(3): Change test_time.test_monotonic() to test only the
     lower bound of elapsed time after a sleep command rather than the
     upper bound.  This prevents unnecessary test failures on slow
     buildbots.  Patch by Victor Stinner.

   - bpo-32424(4): Improve test coverage for xml.etree.ElementTree.
     Patch by Gordon P. Hemsley.

   - bpo-32424(5): Fix typo in test_cyclic_gc() test for
     xml.etree.ElementTree.  Patch by Gordon P. Hemsley.

   - bpo-36635(6): Add a new ‘_testinternalcapi’ module to test the
     internal C API.

   - bpo-36629(7): Fix ‘test_imap4_host_default_value()’ of
     ‘test_imaplib’: catch also *note errno.ENETUNREACH: 190d. error.

   - bpo-36611(8): Fix ‘test_sys.test_getallocatedblocks()’ when *note
     tracemalloc: e8. is enabled.

   - bpo-36560(9): Fix reference leak hunting in regrtest: compute also
     deltas (of reference count, allocated memory blocks, file
     descriptor count) during warmup, to ensure that everything is
     initialized before starting to hunt reference leaks.

   - bpo-36565(10): Fix reference hunting (‘python3 -m test -R 3:3’)
     when Python has no built-in abc module.

   - bpo-31904(11): Port test_resource to VxWorks: skip tests cases
     setting RLIMIT_FSIZE and RLIMIT_CPU.

   - bpo-31904(12): Fix test_tabnanny on VxWorks: adjust ENOENT error
     message.

   - bpo-36436(13): Fix ‘_testcapi.pymem_buffer_overflow()’: handle
     memory allocation failure.

   - bpo-31904(14): Fix test_utf8_mode on VxWorks: Python always use
     UTF-8 on VxWorks.

   - bpo-36341(15): Fix tests that may fail with PermissionError upon
     calling bind() on AF_UNIX sockets.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36719

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36725

   (3) https://bugs.python.org/issue?@action=redirect&bpo=36454

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32424

   (5) https://bugs.python.org/issue?@action=redirect&bpo=32424

   (6) https://bugs.python.org/issue?@action=redirect&bpo=36635

   (7) https://bugs.python.org/issue?@action=redirect&bpo=36629

   (8) https://bugs.python.org/issue?@action=redirect&bpo=36611

   (9) https://bugs.python.org/issue?@action=redirect&bpo=36560

   (10) https://bugs.python.org/issue?@action=redirect&bpo=36565

   (11) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (12) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (13) https://bugs.python.org/issue?@action=redirect&bpo=36436

   (14) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (15) https://bugs.python.org/issue?@action=redirect&bpo=36341


File: python.info,  Node: Build<45>,  Next: Windows<40>,  Prev: Tests<42>,  Up: Python 3 8 0 alpha 4

1.23.46.6 Build
...............

   - bpo-36747(1): Remove the stale scriptsinstall Makefile target.

   - bpo-21536(2): On Unix, C extensions are no longer linked to
     libpython except on Android and Cygwin.

     It is now possible for a statically linked Python to load a C
     extension built using a shared library Python.

     When Python is embedded, ‘libpython’ must not be loaded with
     ‘RTLD_LOCAL’, but ‘RTLD_GLOBAL’ instead.  Previously, using
     ‘RTLD_LOCAL’, it was already not possible to load C extensions
     which were not linked to ‘libpython’, such as C extensions of the
     standard library built by the ‘*shared*’ section of
     ‘Modules/Setup’.

     distutils, python-config and python-config.py have been modified.

   - bpo-36707(3): ‘./configure --with-pymalloc’ no longer adds the ‘m’
     flag to SOABI (sys.implementation.cache_tag).  Enabling or
     disabling pymalloc has no impact on the ABI.

   - bpo-36635(4): Change ‘PyAPI_FUNC(type)’, ‘PyAPI_DATA(type)’ and
     ‘PyMODINIT_FUNC’ macros of ‘pyport.h’ when ‘Py_BUILD_CORE_MODULE’
     is defined.  The ‘Py_BUILD_CORE_MODULE’ define must be now be used
     to build a C extension as a dynamic library accessing Python
     internals: export the ‘PyInit_XXX()’ function in DLL exports on
     Windows.

   - bpo-31904(5): Don't build the ‘_crypt’ extension on VxWorks.

   - bpo-36618(6): Add ‘-fmax-type-align=8’ to CFLAGS when clang
     compiler is detected.  The pymalloc memory allocator aligns memory
     on 8 bytes.  On x86-64, clang expects alignment on 16 bytes by
     default and so uses MOVAPS instruction which can lead to
     segmentation fault.  Instruct clang that Python is limited to
     alignment on 8 bytes to use MOVUPS instruction instead: slower but
     don't trigger a SIGSEGV if the memory is not aligned on 16 bytes.
     Sadly, the flag must be added to ‘CFLAGS’ and not just
     ‘CFLAGS_NODIST’, since third party C extensions can have the same
     issue.

   - bpo-36605(7): ‘make tags’ and ‘make TAGS’ now also parse
     ‘Modules/_io/*.c’ and ‘Modules/_io/*.h’.

   - bpo-36465(8): Release builds and debug builds are now ABI
     compatible: defining the ‘Py_DEBUG’ macro no longer implies the
     ‘Py_TRACE_REFS’ macro, which introduces the only ABI
     incompatibility.  The ‘Py_TRACE_REFS’ macro, which adds the
     ‘sys.getobjects()’ function and the *note PYTHONDUMPREFS: 94a.
     environment variable, can be set using the new ‘./configure
     --with-trace-refs’ build option.

   - bpo-36577(9): setup.py now correctly reports missing OpenSSL
     headers and libraries again.

   - bpo-36544(10): Fix regression introduced in bpo-36146(11)
     refactoring setup.py

   - bpo-36508(12): ‘python-config --ldflags’ no longer includes flags
     of the ‘LINKFORSHARED’ variable.  The ‘LINKFORSHARED’ variable must
     only be used to build executables.

   - bpo-36503(13): Remove references to "aix3" and "aix4".  Patch by M.
     Felt.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36747

   (2) https://bugs.python.org/issue?@action=redirect&bpo=21536

   (3) https://bugs.python.org/issue?@action=redirect&bpo=36707

   (4) https://bugs.python.org/issue?@action=redirect&bpo=36635

   (5) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (6) https://bugs.python.org/issue?@action=redirect&bpo=36618

   (7) https://bugs.python.org/issue?@action=redirect&bpo=36605

   (8) https://bugs.python.org/issue?@action=redirect&bpo=36465

   (9) https://bugs.python.org/issue?@action=redirect&bpo=36577

   (10) https://bugs.python.org/issue?@action=redirect&bpo=36544

   (11) https://bugs.python.org/issue?@action=redirect&bpo=36146

   (12) https://bugs.python.org/issue?@action=redirect&bpo=36508

   (13) https://bugs.python.org/issue?@action=redirect&bpo=36503


File: python.info,  Node: Windows<40>,  Next: macOS<34>,  Prev: Build<45>,  Up: Python 3 8 0 alpha 4

1.23.46.7 Windows
.................

   - bpo-35920(1): Added platform.win32_edition() and
     platform.win32_is_iot().  Added support for cross-compiling
     packages for Windows ARM32.  Skip tests that are not expected to
     work on Windows IoT Core ARM32.

   - bpo-36649(2): Remove trailing spaces for registry keys when
     installed via the Store.

   - bpo-34144(3): Fixed activate.bat to correctly update codepage when
     chcp.com returns dots in output.  Patch by Lorenz Mende.

   - bpo-36509(4): Added preset-iot layout for Windows IoT ARM
     containers.  This layout doesn't contain UI components like tkinter
     or IDLE. It also doesn't contain files to support on-target builds
     since Windows ARM32 builds must be cross-compiled when using MSVC.

   - bpo-35941(5): enum_certificates function of the ssl module now
     returns certificates from all available certificate stores inside
     windows in a query instead of returning only certificates from the
     system wide certificate store.  This includes certificates from
     these certificate stores: local machine, local machine enterprise,
     local machine group policy, current user, current user group
     policy, services, users.  ssl.enum_crls() function is changed in
     the same way to return all certificate revocation lists inside the
     windows certificate revocation list stores.

   - bpo-36441(6): Fixes creating a venv when debug binaries are
     installed.

   - bpo-36085(7): Enable better DLL resolution on Windows by using safe
     DLL search paths and adding *note os.add_dll_directory(): 98e.

   - bpo-36010(8): Add the venv standard library module to the nuget
     distribution for Windows.

   - bpo-29515(9): Add the following socket module constants on Windows:
     IPPROTO_AH IPPROTO_CBT IPPROTO_DSTOPTS IPPROTO_EGP IPPROTO_ESP
     IPPROTO_FRAGMENT IPPROTO_GGP IPPROTO_HOPOPTS IPPROTO_ICLFXBM
     IPPROTO_ICMPV6 IPPROTO_IDP IPPROTO_IGMP IPPROTO_IGP IPPROTO_IPV4
     IPPROTO_IPV6 IPPROTO_L2TP IPPROTO_MAX IPPROTO_ND IPPROTO_NONE
     IPPROTO_PGM IPPROTO_PIM IPPROTO_PUP IPPROTO_RDP IPPROTO_ROUTING
     IPPROTO_SCTP IPPROTO_ST

   - bpo-35947(10): Added current version of libffi to
     cpython-source-deps.  Change _ctypes to use current version of
     libffi on Windows.

   - bpo-34060(11): Report system load when running test suite on
     Windows.  Patch by Ammar Askar.  Based on prior work by Jeremy
     Kloth.

   - bpo-31512(12): With the Windows 10 Creators Update, non-elevated
     users can now create symlinks as long as the computer has Developer
     Mode enabled.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35920

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36649

   (3) https://bugs.python.org/issue?@action=redirect&bpo=34144

   (4) https://bugs.python.org/issue?@action=redirect&bpo=36509

   (5) https://bugs.python.org/issue?@action=redirect&bpo=35941

   (6) https://bugs.python.org/issue?@action=redirect&bpo=36441

   (7) https://bugs.python.org/issue?@action=redirect&bpo=36085

   (8) https://bugs.python.org/issue?@action=redirect&bpo=36010

   (9) https://bugs.python.org/issue?@action=redirect&bpo=29515

   (10) https://bugs.python.org/issue?@action=redirect&bpo=35947

   (11) https://bugs.python.org/issue?@action=redirect&bpo=34060

   (12) https://bugs.python.org/issue?@action=redirect&bpo=31512


File: python.info,  Node: macOS<34>,  Next: IDLE<32>,  Prev: Windows<40>,  Up: Python 3 8 0 alpha 4

1.23.46.8 macOS
...............

   - bpo-34602(1): Avoid failures setting macOS stack resource limit
     with resource.setrlimit.  This reverts an earlier fix for
     bpo-18075(2) which forced a non-default stack size when building
     the interpreter executable on macOS.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=34602

   (2) https://bugs.python.org/issue?@action=redirect&bpo=18075


File: python.info,  Node: IDLE<32>,  Next: Tools/Demos<21>,  Prev: macOS<34>,  Up: Python 3 8 0 alpha 4

1.23.46.9 IDLE
..............

   - bpo-36429(1): Fix starting IDLE with pyshell.  Add idlelib.pyshell
     alias at top; remove pyshell alias at bottom.  Remove obsolete
     __name__=='__main__' command.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36429


File: python.info,  Node: Tools/Demos<21>,  Next: C API<44>,  Prev: IDLE<32>,  Up: Python 3 8 0 alpha 4

1.23.46.10 Tools/Demos
......................

   - bpo-14546(1): Fix the argument handling in Tools/scripts/lll.py.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=14546


File: python.info,  Node: C API<44>,  Prev: Tools/Demos<21>,  Up: Python 3 8 0 alpha 4

1.23.46.11 C API
................

   - bpo-36763(1): Fix memory leak in ‘Py_SetStandardStreamEncoding()’:
     release memory if the function is called twice.

   - bpo-36641(2): PyDoc_VAR(name) and *note PyDoc_STRVAR: 1876.(name,
     str) now create ‘static const char name[]’ instead of ‘static char
     name[]’.  Patch by Inada Naoki.

   - bpo-36389(3): Change the value of ‘CLEANBYTE’, ‘DEADDYTE’ and
     ‘FORBIDDENBYTE’ internal constants used by debug hooks on Python
     memory allocators (*note PyMem_SetupDebugHooks(): c11. function).
     Byte patterns ‘0xCB’, ‘0xDB’ and ‘0xFB’ have been replaced with
     ‘0xCD’, ‘0xDD’ and ‘0xFD’ to use the same values than Windows CRT
     debug ‘malloc()’ and ‘free()’.

   - bpo-36443(4): Since Python 3.7.0, calling *note Py_DecodeLocale():
     b6e. before *note Py_Initialize(): 851. produces mojibake if the
     ‘LC_CTYPE’ locale is coerced and/or if the UTF-8 Mode is enabled by
     the user configuration.  The LC_CTYPE coercion and UTF-8 Mode are
     now disabled by default to fix the mojibake issue.  They must now
     be enabled explicitly (opt-in) using the new ‘_Py_PreInitialize()’
     API with ‘_PyPreConfig’.

   - bpo-36025(5): Fixed an accidental change to the datetime C API
     where the arguments to the *note PyDate_FromTimestamp(): 1914.
     function were incorrectly interpreted as a single timestamp rather
     than an arguments tuple, which causes existing code to start
     raising *note TypeError: 4dd.  The backwards-incompatible change
     was only present in alpha releases of Python 3.8.  Patch by Paul
     Ganssle.

   - bpo-35810(6): Modify ‘PyObject_Init’ to correctly increase the
     refcount of heap-allocated Type objects.  Also fix the refcounts of
     the heap-allocated types that were either doing this manually or
     not decreasing the type's refcount in tp_dealloc

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36763

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36641

   (3) https://bugs.python.org/issue?@action=redirect&bpo=36389

   (4) https://bugs.python.org/issue?@action=redirect&bpo=36443

   (5) https://bugs.python.org/issue?@action=redirect&bpo=36025

   (6) https://bugs.python.org/issue?@action=redirect&bpo=35810


File: python.info,  Node: Python 3 8 0 alpha 3,  Next: Python 3 8 0 alpha 2,  Prev: Python 3 8 0 alpha 4,  Up: Changelog（更動日誌）

1.23.47 Python 3.8.0 alpha 3
----------------------------

'Release date: 2019-03-25'

* Menu:

* Security: Security<32>.
* Core and Builtins: Core and Builtins<47>.
* Library: Library<46>.
* Documentation: Documentation<41>.
* Tests: Tests<43>.
* Build: Build<46>.
* Windows: Windows<41>.
* IDLE: IDLE<33>.
* Tools/Demos: Tools/Demos<22>.
* C API: C API<45>.


File: python.info,  Node: Security<32>,  Next: Core and Builtins<47>,  Up: Python 3 8 0 alpha 3

1.23.47.1 Security
..................

   - bpo-36216(1): Changes urlsplit() to raise ValueError when the URL
     contains characters that decompose under IDNA encoding
     (NFKC-normalization) into characters that affect how the URL is
     parsed.

   - bpo-35121(2): Don't send cookies of domain A without Domain
     attribute to domain B when domain A is a suffix match of domain B
     while using a cookiejar with *note
     http.cookiejar.DefaultCookiePolicy: 1917. policy.  Patch by
     Karthikeyan Singaravelan.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36216

   (2) https://bugs.python.org/issue?@action=redirect&bpo=35121


File: python.info,  Node: Core and Builtins<47>,  Next: Library<46>,  Prev: Security<32>,  Up: Python 3 8 0 alpha 3

1.23.47.2 Core and Builtins
...........................

   - bpo-36421(1): Fix a possible double decref in _ctypes.c's
     ‘PyCArrayType_new()’.

   - bpo-36412(2): Fix a possible crash when creating a new dictionary.

   - bpo-36398(3): Fix a possible crash in ‘structseq_repr()’.

   - bpo-36256(4): Fix bug in parsermodule when parsing a state in a DFA
     that has two or more arcs with labels of the same type.  Patch by
     Pablo Galindo.

   - bpo-36365(5): repr(structseq) is no longer limited to 512 bytes.

   - bpo-36374(6): Fix a possible null pointer dereference in
     ‘merge_consts_recursive()’.  Patch by Zackery Spytz.

   - bpo-36236(7): At Python initialization, the current directory is no
     longer prepended to *note sys.path: 37f. if it has been removed.

   - bpo-36352(8): Python initialization now fails with an error, rather
     than silently truncating paths, if a path is too long.

   - bpo-36301(9): Python initialization now fails if decoding
     ‘pybuilddir.txt’ configuration file fails at startup.

   - bpo-36333(10): Fix leak in _PyRuntimeState_Fini.  Contributed by
     Stéphane Wirtel.

   - bpo-36332(11): The builtin *note compile(): 178. can now handle AST
     objects that contain assignment expressions.  Patch by Pablo
     Galindo.

   - bpo-36282(12): Improved error message for too much positional
     arguments in some builtin functions.

   - bpo-30040(13): New empty dict uses fewer memory for now.  It used
     more memory than empty dict created by ‘dict.clear()’.  And empty
     dict creation and deletion is about 2x faster.  Patch by Inada
     Naoki.

   - bpo-36262(14): Fix an unlikely memory leak on conversion from
     string to float in the function ‘_Py_dg_strtod()’ used by
     ‘float(str)’, ‘complex(str)’, *note pickle.load(): cb7, *note
     marshal.load(): 1919, etc.

   - bpo-36252(15): Update Unicode databases to version 12.0.0.

   - bpo-36218(16): Fix a segfault occurring when sorting a list of
     heterogeneous values.  Patch contributed by Rémi Lapeyre and Elliot
     Gorokhovsky.

   - bpo-36188(17): Cleaned up left-over vestiges of Python 2 unbound
     method handling in method objects and documentation.  Patch by
     Martijn Pieters

   - bpo-36124(18): Add a new interpreter-specific dict and expose it in
     the C-API via PyInterpreterState_GetDict().  This parallels
     PyThreadState_GetDict().  However, extension modules should
     continue using PyModule_GetState() for their own internal
     per-interpreter state.

   - bpo-35975(19): Add a ‘feature_version’ flag to ‘ast.parse()’
     (documented) and ‘compile()’ (hidden) that allows tweaking the
     parser to support older versions of the grammar.  In particular, if
     ‘feature_version’ is 5 or 6, the hacks for the ‘async’ and ‘await’
     keyword from PEP 492 are reinstated.  (For 7 or higher, these are
     unconditionally treated as keywords, but they are still special
     tokens rather than ‘NAME’ tokens that the parser driver
     recognizes.)

   - bpo-31904(20): Use UTF-8 as the system encoding on VxWorks.

   - bpo-36048(21): The *note __index__(): 6c1. special method will be
     used instead of *note __int__(): 6c0. for implicit conversion of
     Python numbers to C integers.  Using the ‘__int__()’ method in
     implicit conversions has been deprecated.

   - bpo-35808(22): Retire pgen and use a modified version of pgen2 to
     generate the parser.  Patch by Pablo Galindo.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36421

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36412

   (3) https://bugs.python.org/issue?@action=redirect&bpo=36398

   (4) https://bugs.python.org/issue?@action=redirect&bpo=36256

   (5) https://bugs.python.org/issue?@action=redirect&bpo=36365

   (6) https://bugs.python.org/issue?@action=redirect&bpo=36374

   (7) https://bugs.python.org/issue?@action=redirect&bpo=36236

   (8) https://bugs.python.org/issue?@action=redirect&bpo=36352

   (9) https://bugs.python.org/issue?@action=redirect&bpo=36301

   (10) https://bugs.python.org/issue?@action=redirect&bpo=36333

   (11) https://bugs.python.org/issue?@action=redirect&bpo=36332

   (12) https://bugs.python.org/issue?@action=redirect&bpo=36282

   (13) https://bugs.python.org/issue?@action=redirect&bpo=30040

   (14) https://bugs.python.org/issue?@action=redirect&bpo=36262

   (15) https://bugs.python.org/issue?@action=redirect&bpo=36252

   (16) https://bugs.python.org/issue?@action=redirect&bpo=36218

   (17) https://bugs.python.org/issue?@action=redirect&bpo=36188

   (18) https://bugs.python.org/issue?@action=redirect&bpo=36124

   (19) https://bugs.python.org/issue?@action=redirect&bpo=35975

   (20) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (21) https://bugs.python.org/issue?@action=redirect&bpo=36048

   (22) https://bugs.python.org/issue?@action=redirect&bpo=35808


File: python.info,  Node: Library<46>,  Next: Documentation<41>,  Prev: Core and Builtins<47>,  Up: Python 3 8 0 alpha 3

1.23.47.3 Library
.................

   - bpo-36401(1): The class documentation created by pydoc now has a
     separate section for readonly properties.

   - bpo-36320(2): The typing.NamedTuple() class has deprecated the
     _field_types attribute in favor of the __annotations__ attribute
     which carried the same information.  Also, both attributes were
     converted from OrderedDict to a regular dict.

   - bpo-34745(3): Fix *note asyncio: 8. ssl memory issues caused by
     circular references

   - bpo-36324(4): Add method to statistics.NormalDist for computing the
     inverse cumulative normal distribution.

   - bpo-36321(5): collections.namedtuple() misspelled the name of an
     attribute.  To be consistent with typing.NamedTuple, the attribute
     name should have been "_field_defaults" instead of
     "_fields_defaults".  For backwards compatibility, both spellings
     are now created.  The misspelled version may be removed in the
     future.

   - bpo-36297(6): "unicode_internal" codec is removed.  It was
     deprecated since Python 3.3.  Patch by Inada Naoki.

   - bpo-36298(7): Raise ModuleNotFoundError in pyclbr when a module
     can't be found.  Thanks to 'mental' for the bug report.

   - bpo-36268(8): Switch the default format used for writing tars with
     *note tarfile: c8. to the modern POSIX.1-2001 pax standard, from
     the vendor-specific GNU. Contributed by C.A.M. Gerlach.

   - bpo-36285(9): Fix integer overflows in the array module.  Patch by
     Stephan Hohe.

   - bpo-31904(10): Add _signal module support for VxWorks.

   - bpo-36272(11): *note logging: 7b. does not silently ignore
     RecursionError anymore.  Patch contributed by Rémi Lapeyre.

   - bpo-36280(12): Add a kind field to ast.Constant.  It is 'u' if the
     literal has a 'u' prefix (i.e.  a Python 2 style unicode literal),
     else None.

   - bpo-35931(13): The *note pdb: 94. ‘debug’ command now gracefully
     handles all exceptions.

   - bpo-36251(14): Fix format strings used for stderrprinter and
     re.Match reprs.  Patch by Stephan Hohe.

   - bpo-36235(15): Fix ‘CFLAGS’ in ‘customize_compiler()’ of
     ‘distutils.sysconfig’: when the ‘CFLAGS’ environment variable is
     defined, don't override ‘CFLAGS’ variable with the ‘OPT’ variable
     anymore.  Initial patch written by David Malcolm.

   - bpo-35807(16): Update ensurepip to install pip 19.0.3 and
     setuptools 40.8.0.

   - bpo-36139(17): Release GIL when closing *note mmap: 1f0. objects.

   - bpo-36179(18): Fix two unlikely reference leaks in _hashopenssl.
     The leaks only occur in out-of-memory cases.

   - bpo-36169(19): Add overlap() method to statistics.NormalDist.
     Computes the overlapping coefficient for two normal distributions.

   - bpo-36103(20): Default buffer size used by ‘shutil.copyfileobj()’
     is changed from 16 KiB to 64 KiB on non-Windows platform to reduce
     system call overhead.  Contributed by Inada Naoki.

   - bpo-36130(21): Fix ‘pdb’ with ‘skip=...’ when stepping into a frame
     without a ‘__name__’ global.  Patch by Anthony Sottile.

   - bpo-35652(22): shutil.copytree(copy_function=...)  erroneously pass
     DirEntry instead of a path string.

   - bpo-35178(23): Ensure custom *note warnings.formatwarning(): 191b.
     function can receive ‘line’ as positional argument.  Based on patch
     by Tashrif Billah.

   - bpo-36106(24): Resolve potential name clash with libm's sinpi().
     Patch by Dmitrii Pasechnik.

   - bpo-36091(25): Clean up reference to async generator in Lib/types.
     Patch by Henry Chen.

   - bpo-36043(26): ‘FileCookieJar’ supports *note path-like object:
     ac2.  Contributed by Stéphane Wirtel

   - bpo-35899(27): Enum has been fixed to correctly handle empty
     strings and strings with non-Latin characters (ie.  'α', 'א')
     without crashing.  Original patch contributed by Maxwell.  Assisted
     by Stéphane Wirtel.

   - bpo-21269(28): Add ‘args’ and ‘kwargs’ properties to mock call
     objects.  Contributed by Kumar Akshay.

   - bpo-30670(29): ‘pprint.pp’ has been added to pretty-print objects
     with dictionary keys being sorted with their insertion order by
     default.  Parameter 'sort_dicts' has been added to ‘pprint.pprint’,
     ‘pprint.pformat’ and ‘pprint.PrettyPrinter’.  Contributed by Rémi
     Lapeyre.

   - bpo-35843(30): Implement ‘__getitem__’ for ‘_NamespacePath’.  Patch
     by Anthony Sottile.

   - bpo-35802(31): Clean up code which checked presence of ‘os.stat’ /
     ‘os.lstat’ / ‘os.chmod’ which are always present.  Patch by Anthony
     Sottile.

   - bpo-35715(32): Librates the return value of a ProcessPoolExecutor
     _process_worker after it's no longer needed to free memory

   - bpo-35493(33): Use *note multiprocessing.connection.wait(): 1079.
     instead of polling each 0.2 seconds for worker updates in
     ‘multiprocessing.Pool’.  Patch by Pablo Galindo.

   - bpo-35661(34): Store the venv prompt in pyvenv.cfg.

   - bpo-35121(35): Don't set cookie for a request when the request path
     is a prefix match of the cookie's path attribute but doesn't end
     with "/".  Patch by Karthikeyan Singaravelan.

   - bpo-21478(36): Calls to a child function created with *note
     unittest.mock.create_autospec(): 14fb. should propagate to the
     parent.  Patch by Karthikeyan Singaravelan.

   - bpo-35198(37): Fix C++ extension compilation on AIX

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36401

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36320

   (3) https://bugs.python.org/issue?@action=redirect&bpo=34745

   (4) https://bugs.python.org/issue?@action=redirect&bpo=36324

   (5) https://bugs.python.org/issue?@action=redirect&bpo=36321

   (6) https://bugs.python.org/issue?@action=redirect&bpo=36297

   (7) https://bugs.python.org/issue?@action=redirect&bpo=36298

   (8) https://bugs.python.org/issue?@action=redirect&bpo=36268

   (9) https://bugs.python.org/issue?@action=redirect&bpo=36285

   (10) https://bugs.python.org/issue?@action=redirect&bpo=31904

   (11) https://bugs.python.org/issue?@action=redirect&bpo=36272

   (12) https://bugs.python.org/issue?@action=redirect&bpo=36280

   (13) https://bugs.python.org/issue?@action=redirect&bpo=35931

   (14) https://bugs.python.org/issue?@action=redirect&bpo=36251

   (15) https://bugs.python.org/issue?@action=redirect&bpo=36235

   (16) https://bugs.python.org/issue?@action=redirect&bpo=35807

   (17) https://bugs.python.org/issue?@action=redirect&bpo=36139

   (18) https://bugs.python.org/issue?@action=redirect&bpo=36179

   (19) https://bugs.python.org/issue?@action=redirect&bpo=36169

   (20) https://bugs.python.org/issue?@action=redirect&bpo=36103

   (21) https://bugs.python.org/issue?@action=redirect&bpo=36130

   (22) https://bugs.python.org/issue?@action=redirect&bpo=35652

   (23) https://bugs.python.org/issue?@action=redirect&bpo=35178

   (24) https://bugs.python.org/issue?@action=redirect&bpo=36106

   (25) https://bugs.python.org/issue?@action=redirect&bpo=36091

   (26) https://bugs.python.org/issue?@action=redirect&bpo=36043

   (27) https://bugs.python.org/issue?@action=redirect&bpo=35899

   (28) https://bugs.python.org/issue?@action=redirect&bpo=21269

   (29) https://bugs.python.org/issue?@action=redirect&bpo=30670

   (30) https://bugs.python.org/issue?@action=redirect&bpo=35843

   (31) https://bugs.python.org/issue?@action=redirect&bpo=35802

   (32) https://bugs.python.org/issue?@action=redirect&bpo=35715

   (33) https://bugs.python.org/issue?@action=redirect&bpo=35493

   (34) https://bugs.python.org/issue?@action=redirect&bpo=35661

   (35) https://bugs.python.org/issue?@action=redirect&bpo=35121

   (36) https://bugs.python.org/issue?@action=redirect&bpo=21478

   (37) https://bugs.python.org/issue?@action=redirect&bpo=35198


File: python.info,  Node: Documentation<41>,  Next: Tests<43>,  Prev: Library<46>,  Up: Python 3 8 0 alpha 3

1.23.47.4 Documentation
.......................

   - bpo-36329(1): Declare the path of the Python binary for the usage
     of ‘Tools/scripts/serve.py’ when executing ‘make -C Doc/ serve’.
     Contributed by Stéphane Wirtel

   - bpo-36138(2): Improve documentation about converting
     datetime.timedelta to scalars.

   - bpo-21314(3): A new entry was added to the Core Language Section of
     the Programming FAQ, which explaines the usage of slash(/) in the
     signature of a function.  Patch by Lysandros Nikolaou

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36329

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36138

   (3) https://bugs.python.org/issue?@action=redirect&bpo=21314


File: python.info,  Node: Tests<43>,  Next: Build<46>,  Prev: Documentation<41>,  Up: Python 3 8 0 alpha 3

1.23.47.5 Tests
...............

   - bpo-36234(1): test_posix.PosixUidGidTests: add tests for invalid
     uid/gid type (str).  Initial patch written by David Malcolm.

   - bpo-29571(2): Fix ‘test_re.test_locale_flag()’: use
     ‘locale.getpreferredencoding()’ rather than ‘locale.getlocale()’ to
     get the locale encoding.  With some locales, ‘locale.getlocale()’
     returns the wrong encoding.

   - bpo-36123(3): Fix race condition in test_socket.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36234

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29571

   (3) https://bugs.python.org/issue?@action=redirect&bpo=36123


File: python.info,  Node: Build<46>,  Next: Windows<41>,  Prev: Tests<43>,  Up: Python 3 8 0 alpha 3

1.23.47.6 Build
...............

   - bpo-36356(1): Fix leaks that led to build failure when configured
     with address sanitizer.

   - bpo-36146(2): Add ‘TEST_EXTENSIONS’ constant to ‘setup.py’ to allow
     to not build test extensions like ‘_testcapi’.

   - bpo-36146(3): Fix setup.py on macOS: only add ‘/usr/include/ffi’ to
     include directories of _ctypes, not for all extensions.

   - bpo-31904(4): Enable build system to cross-build for VxWorks RTOS.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36356

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36146

   (3) https://bugs.python.org/issue?@action=redirect&bpo=36146

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31904


File: python.info,  Node: Windows<41>,  Next: IDLE<33>,  Prev: Build<46>,  Up: Python 3 8 0 alpha 3

1.23.47.7 Windows
.................

   - bpo-36312(1): Fixed decoders for the following code pages: 50220,
     50221, 50222, 50225, 50227, 50229, 57002 through 57011, 65000 and
     42.

   - bpo-36264(2): Don't honor POSIX ‘HOME’ in ‘os.path.expanduser’ on
     windows.  Patch by Anthony Sottile.

   - bpo-24643(3): Fix name collisions due to ‘#define timezone
     _timezone’ in PC/pyconfig.h.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36312

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36264

   (3) https://bugs.python.org/issue?@action=redirect&bpo=24643


File: python.info,  Node: IDLE<33>,  Next: Tools/Demos<22>,  Prev: Windows<41>,  Up: Python 3 8 0 alpha 3

1.23.47.8 IDLE
..............

   - bpo-36405(1): Use dict unpacking in idlelib.

   - bpo-36396(2): Remove fgBg param of idlelib.config.GetHighlight().
     This param was only used twice and changed the return type.

   - bpo-36176(3): Fix IDLE autocomplete & calltip popup colors.
     Prevent conflicts with Linux dark themes (and slightly darken
     calltip background).

   - bpo-23205(4): For the grep module, add tests for findfiles,
     refactor findfiles to be a module-level function, and refactor
     findfiles to use os.walk.

   - bpo-23216(5): Add docstrings to IDLE search modules.

   - bpo-36152(6): Remove colorizer.ColorDelegator.close_when_done and
     the corresponding argument of .close().  In IDLE, both have always
     been None or False since 2007.

   - bpo-32129(7): Avoid blurry IDLE application icon on macOS with Tk
     8.6.  Patch by Kevin Walzer.

   - bpo-36096(8): Refactor class variables to instance variables in
     colorizer.

   - bpo-30348(9): Increase test coverage of idlelib.autocomplete by
     30%.  Patch by Louie Lu

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36405

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36396

   (3) https://bugs.python.org/issue?@action=redirect&bpo=36176

   (4) https://bugs.python.org/issue?@action=redirect&bpo=23205

   (5) https://bugs.python.org/issue?@action=redirect&bpo=23216

   (6) https://bugs.python.org/issue?@action=redirect&bpo=36152

   (7) https://bugs.python.org/issue?@action=redirect&bpo=32129

   (8) https://bugs.python.org/issue?@action=redirect&bpo=36096

   (9) https://bugs.python.org/issue?@action=redirect&bpo=30348


File: python.info,  Node: Tools/Demos<22>,  Next: C API<45>,  Prev: IDLE<33>,  Up: Python 3 8 0 alpha 3

1.23.47.9 Tools/Demos
.....................

   - bpo-35132(1): Fix py-list and py-bt commands of python-gdb.py on
     gdb7.

   - bpo-32217(2): Fix freeze script on Windows.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35132

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32217


File: python.info,  Node: C API<45>,  Prev: Tools/Demos<22>,  Up: Python 3 8 0 alpha 3

1.23.47.10 C API
................

   - bpo-36381(1): Raise ‘DeprecationWarning’ when '#' formats are used
     for building or parsing values without ‘PY_SSIZE_T_CLEAN’.

   - bpo-36142(2): The whole coreconfig.h header is now excluded from
     Py_LIMITED_API. Move functions definitions into a new internal
     pycore_coreconfig.h header.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36381

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36142


File: python.info,  Node: Python 3 8 0 alpha 2,  Next: Python 3 8 0 alpha 1,  Prev: Python 3 8 0 alpha 3,  Up: Changelog（更動日誌）

1.23.48 Python 3.8.0 alpha 2
----------------------------

'Release date: 2019-02-25'

* Menu:

* Core and Builtins: Core and Builtins<48>.
* Library: Library<47>.
* Documentation: Documentation<42>.
* Tests: Tests<44>.
* Windows: Windows<42>.
* IDLE: IDLE<34>.


File: python.info,  Node: Core and Builtins<48>,  Next: Library<47>,  Up: Python 3 8 0 alpha 2

1.23.48.1 Core and Builtins
...........................

   - bpo-36052(1): Raise a *note SyntaxError: 173. when assigning a
     value to ‘__debug__’ with the Assignment Operator.  Contributed by
     Stéphane Wirtel and Pablo Galindo.

   - bpo-36012(2): Doubled the speed of class variable writes.  When a
     non-dunder attribute was updated, there was an unnecessary call to
     update slots.

   - bpo-35942(3): The error message emitted when returning invalid
     types from ‘__fspath__’ in interfaces that allow passing *note
     PathLike: bf8. objects has been improved and now it does explain
     the origin of the error.

   - bpo-36016(4): ‘gc.get_objects’ can now receive an optional
     parameter indicating a generation to get objects from.  Patch by
     Pablo Galindo.

   - bpo-1054041(5): When the main interpreter exits due to an uncaught
     KeyboardInterrupt, the process now exits in the appropriate manner
     for its parent process to detect that a SIGINT or ^C terminated the
     process.  This allows shells and batch scripts to understand that
     the user has asked them to stop.

   - bpo-35992(6): Fix ‘__class_getitem__()’ not being called on a class
     with a custom non-subscriptable metaclass.

   - bpo-35993(7): Fix a crash on fork when using subinterpreters.
     Contributed by Stéphane Wirtel

   - bpo-35991(8): Fix a potential double free in
     Modules/_randommodule.c.

   - bpo-35961(9): Fix a crash in slice_richcompare(): use strong
     references rather than stolen references for the two temporary
     internal tuples.

   - bpo-35911(10): Enable the creation of cell objects by adding a
     ‘cell.__new__’ method, and expose the type ‘cell’ in ‘Lib/types.py’
     under the name CellType.  Patch by Pierre Glaser.

   - bpo-12822(11): Use monotonic clock for ‘pthread_cond_timedwait’
     when ‘pthread_condattr_setclock’ and ‘CLOCK_MONOTONIC’ are
     available.

   - bpo-15248(12): The compiler emits now syntax warnings in the case
     when a comma is likely missed before tuple or list.

   - bpo-35886(13): The implementation of PyInterpreterState has been
     moved into the internal header files (guarded by Py_BUILD_CORE).

   - bpo-31506(14): Clarify the errors reported when ‘object.__new__’
     and ‘object.__init__’ receive more than one argument.  Contributed
     by Sanyam Khurana.

   - bpo-35724(15): Signal-handling is now guaranteed to happen relative
     to the main interpreter.

   - bpo-33608(16): We added a new internal _Py_AddPendingCall() that
     operates relative to the provided interpreter.  This allows us to
     use the existing implementation to ask another interpreter to do
     work that cannot be done in the current interpreter, like decref an
     object the other interpreter owns.  The existing
     Py_AddPendingCall() only operates relative to the main interpreter.

   - bpo-33989(17): Fix a possible crash in *note list.sort(): b76. when
     sorting objects with ‘ob_type->tp_richcompare == NULL’.  Patch by
     Zackery Spytz.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36052

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36012

   (3) https://bugs.python.org/issue?@action=redirect&bpo=35942

   (4) https://bugs.python.org/issue?@action=redirect&bpo=36016

   (5) https://bugs.python.org/issue?@action=redirect&bpo=1054041

   (6) https://bugs.python.org/issue?@action=redirect&bpo=35992

   (7) https://bugs.python.org/issue?@action=redirect&bpo=35993

   (8) https://bugs.python.org/issue?@action=redirect&bpo=35991

   (9) https://bugs.python.org/issue?@action=redirect&bpo=35961

   (10) https://bugs.python.org/issue?@action=redirect&bpo=35911

   (11) https://bugs.python.org/issue?@action=redirect&bpo=12822

   (12) https://bugs.python.org/issue?@action=redirect&bpo=15248

   (13) https://bugs.python.org/issue?@action=redirect&bpo=35886

   (14) https://bugs.python.org/issue?@action=redirect&bpo=31506

   (15) https://bugs.python.org/issue?@action=redirect&bpo=35724

   (16) https://bugs.python.org/issue?@action=redirect&bpo=33608

   (17) https://bugs.python.org/issue?@action=redirect&bpo=33989


File: python.info,  Node: Library<47>,  Next: Documentation<42>,  Prev: Core and Builtins<48>,  Up: Python 3 8 0 alpha 2

1.23.48.2 Library
.................

   - bpo-35512(1): *note unittest.mock.patch.dict(): 18f8. used as a
     decorator with string target resolves the target during function
     call instead of during decorator construction.  Patch by
     Karthikeyan Singaravelan.

   - bpo-36018(2): Add statistics.NormalDist, a tool for creating and
     manipulating normal distributions of random variable.  Features a
     composite class that treats the mean and standard deviation of
     measurement data as single entity.

   - bpo-35904(3): Added statistics.fmean() as a faster, floating-point
     variant of the existing mean() function.

   - bpo-35918(4): Removed broken ‘has_key’ method from
     multiprocessing.managers.SyncManager.dict.  Contributed by Rémi
     Lapeyre.

   - bpo-18283(5): Add support for bytes to *note shutil.which(): 45b.

   - bpo-35960(6): Fix *note dataclasses.field(): 1926. throwing away
     empty mapping objects passed as metadata.

   - bpo-35500(7): Write expected and actual call parameters on separate
     lines in *note unittest.mock.Mock.assert_called_with(): 1927.
     assertion errors.  Contributed by Susan Su.

   - bpo-35931(8): The *note pdb: 94. ‘debug’ command now gracefully
     handles syntax errors.

   - bpo-24209(9): In http.server script, rely on getaddrinfo to bind to
     preferred address based on the bind parameter.  Now default bind or
     binding to a name may bind to IPv6 or dual-stack, depending on the
     environment.

   - bpo-35321(10): Set ‘__spec__.origin’ of ‘_frozen_importlib’ to
     frozen so that it matches the behavior of
     ‘_frozen_importlib_external’.  Patch by Nina Zakharenko.

   - bpo-35378(11): Fix a reference issue inside ‘multiprocessing.Pool’
     that caused the pool to remain alive if it was deleted without
     being closed or terminated explicitly.  A new strong reference is
     added to the pool iterators to link the lifetime of the pool to the
     lifetime of its iterators so the pool does not get destroyed if a
     pool iterator is still alive.

   - bpo-34294(12): re module, fix wrong capturing groups in rare cases.
     *note re.search(): 11c4, *note re.findall(): fcd, *note re.sub():
     283. and other functions that scan through string looking for a
     match, should reset capturing groups between two match attempts.
     Patch by Ma Lin.

   - bpo-35615(13): *note weakref: fc.: Fix a RuntimeError when copying
     a WeakKeyDictionary or a WeakValueDictionary, due to some keys or
     values disappearing while iterating.

   - bpo-35606(14): Implement *note math.prod(): 9a8. as analogous
     function to *note sum(): 411. that returns the product of a 'start'
     value (default: 1) times an iterable of numbers.  Patch by Pablo
     Galindo.

   - bpo-32417(15): Performing arithmetic between *note
     datetime.datetime: 1b0. subclasses and *note datetime.timedelta:
     973. now returns an object of the same type as the *note
     datetime.datetime: 1b0. subclass.  As a result, *note
     datetime.datetime.astimezone(): 974. and alternate constructors
     like *note datetime.datetime.now(): 494. and
     ‘datetime.fromtimestamp()’ called with a ‘tz’ argument now 'also'
     retain their subclass.

   - bpo-35153(16): Add 'headers' optional keyword-only parameter to
     *note xmlrpc.client.ServerProxy: 9fa, ‘xmlrpc.client.Transport’ and
     ‘xmlrpc.client.SafeTransport’.  Patch by Cédric Krier.

   - bpo-34572(17): Fix C implementation of pickle.loads to use
     importlib's locking mechanisms, and thereby avoid using partially
     loaded modules.  Patch by Tim Burgess.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35512

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36018

   (3) https://bugs.python.org/issue?@action=redirect&bpo=35904

   (4) https://bugs.python.org/issue?@action=redirect&bpo=35918

   (5) https://bugs.python.org/issue?@action=redirect&bpo=18283

   (6) https://bugs.python.org/issue?@action=redirect&bpo=35960

   (7) https://bugs.python.org/issue?@action=redirect&bpo=35500

   (8) https://bugs.python.org/issue?@action=redirect&bpo=35931

   (9) https://bugs.python.org/issue?@action=redirect&bpo=24209

   (10) https://bugs.python.org/issue?@action=redirect&bpo=35321

   (11) https://bugs.python.org/issue?@action=redirect&bpo=35378

   (12) https://bugs.python.org/issue?@action=redirect&bpo=34294

   (13) https://bugs.python.org/issue?@action=redirect&bpo=35615

   (14) https://bugs.python.org/issue?@action=redirect&bpo=35606

   (15) https://bugs.python.org/issue?@action=redirect&bpo=32417

   (16) https://bugs.python.org/issue?@action=redirect&bpo=35153

   (17) https://bugs.python.org/issue?@action=redirect&bpo=34572


File: python.info,  Node: Documentation<42>,  Next: Tests<44>,  Prev: Library<47>,  Up: Python 3 8 0 alpha 2

1.23.48.3 Documentation
.......................

   - bpo-36083(1): Fix formatting of -check-hash-based-pycs options in
     the manpage Synopsis.

   - bpo-36007(2): Bump minimum sphinx version to 1.8.  Patch by Anthony
     Sottile.

   - bpo-22062(3): Update documentation and docstrings for pathlib.
     Original patch by Mike Short.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=36083

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36007

   (3) https://bugs.python.org/issue?@action=redirect&bpo=22062


File: python.info,  Node: Tests<44>,  Next: Windows<42>,  Prev: Documentation<42>,  Up: Python 3 8 0 alpha 2

1.23.48.4 Tests
...............

   - bpo-27313(1): Avoid test_ttk_guionly ComboboxTest failure with
     macOS Cocoa Tk.

   - bpo-36019(2): Add test.support.TEST_HTTP_URL and replace references
     of ‘http://www.example.com’ by this new constant.  Contributed by
     Stéphane Wirtel.

   - bpo-36037(3): Fix test_ssl for strict OpenSSL configuration like
     RHEL8 strict crypto policy.  Use older TLS version for minimum TLS
     version of the server SSL context if needed, to test TLS version
     older than default minimum TLS version.

   - bpo-35798(4): Added ‘test.support.check_syntax_warning()’.

   - bpo-35505(5): Make test_imap4_host_default_value independent on
     whether the local IMAP server is running.

   - bpo-35917(6): multiprocessing: provide unit tests for SyncManager
     and SharedMemoryManager classes + all the shareable types which are
     supposed to be supported by them.  (patch by Giampaolo Rodola)

   - bpo-35704(7): Skip ‘test_shutil.test_unpack_archive_xztar’ to
     prevent a MemoryError on 32-bit AIX when MAXDATA setting is less
     than 0x20000000.

     Patch by Michael Felt (aixtools)

   - bpo-34720(8): Assert m_state != NULL to mimic GC traversal
     functions that do not correctly handle module creation when the
     module state has not been created.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27313

   (2) https://bugs.python.org/issue?@action=redirect&bpo=36019

   (3) https://bugs.python.org/issue?@action=redirect&bpo=36037

   (4) https://bugs.python.org/issue?@action=redirect&bpo=35798

   (5) https://bugs.python.org/issue?@action=redirect&bpo=35505

   (6) https://bugs.python.org/issue?@action=redirect&bpo=35917

   (7) https://bugs.python.org/issue?@action=redirect&bpo=35704

   (8) https://bugs.python.org/issue?@action=redirect&bpo=34720


File: python.info,  Node: Windows<42>,  Next: IDLE<34>,  Prev: Tests<44>,  Up: Python 3 8 0 alpha 2

1.23.48.5 Windows
.................

   - bpo-35976(1): Added ARM build support to Windows build files in
     PCBuild.

   - bpo-35692(2): ‘pathlib’ no longer raises when checking file and
     directory existence on drives that are not ready

   - bpo-35872(3): Uses the base Python executable when invoking venv in
     a virtual environment

   - bpo-35873(4): Prevents venv paths being inherited by child
     processes

   - bpo-35299(5): Fix sysconfig detection of the source directory and
     distutils handling of pyconfig.h during PGO profiling

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35976

   (2) https://bugs.python.org/issue?@action=redirect&bpo=35692

   (3) https://bugs.python.org/issue?@action=redirect&bpo=35872

   (4) https://bugs.python.org/issue?@action=redirect&bpo=35873

   (5) https://bugs.python.org/issue?@action=redirect&bpo=35299


File: python.info,  Node: IDLE<34>,  Prev: Windows<42>,  Up: Python 3 8 0 alpha 2

1.23.48.6 IDLE
..............

   - bpo-24310(1): IDLE - Document settings dialog font tab sample.

   - bpo-35833(2): Revise IDLE doc for control codes sent to Shell.  Add
     a code example block.

   - bpo-35689(3): Add docstrings and unittests for colorizer.py.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24310

   (2) https://bugs.python.org/issue?@action=redirect&bpo=35833

   (3) https://bugs.python.org/issue?@action=redirect&bpo=35689


File: python.info,  Node: Python 3 8 0 alpha 1,  Next: Python 3 7 0 final,  Prev: Python 3 8 0 alpha 2,  Up: Changelog（更動日誌）

1.23.49 Python 3.8.0 alpha 1
----------------------------

'Release date: 2019-02-03'

* Menu:

* Security: Security<33>.
* Core and Builtins: Core and Builtins<49>.
* Library: Library<48>.
* Documentation: Documentation<43>.
* Tests: Tests<45>.
* Build: Build<47>.
* Windows: Windows<43>.
* macOS: macOS<35>.
* IDLE: IDLE<35>.
* Tools/Demos: Tools/Demos<23>.
* C API: C API<46>.


File: python.info,  Node: Security<33>,  Next: Core and Builtins<49>,  Up: Python 3 8 0 alpha 1

1.23.49.1 Security
..................

   - bpo-35746(1): CVE-2019-5010(2): Fix a NULL pointer deref in ssl
     module.  The cert parser did not handle CRL distribution points
     with empty DP or URI correctly.  A malicious or buggy certificate
     can result into segfault.  Vulnerability (TALOS-2018-0758) reported
     by Colin Read and Nicolas Edet of Cisco.

   - bpo-34812(3): The *note -I: 902. command line option (run Python in
     isolated mode) is now also copied by the *note multiprocessing: 86.
     and ‘distutils’ modules when spawning child processes.  Previously,
     only *note -E: 901. and *note -s: 1319. options (enabled by *note
     -I: 902.) were copied.

   - bpo-34791(4): The xml.sax and xml.dom.domreg no longer use
     environment variables to override parser implementations when
     sys.flags.ignore_environment is set by -E or -I arguments.

   - bpo-17239(5): The xml.sax and xml.dom.minidom parsers no longer
     processes external entities by default.  External DTD and ENTITY
     declarations no longer load files or create network connections.

   - bpo-34623(6): CVE-2018-14647(7): The C accelerated _elementtree
     module now initializes hash randomization salt from _Py_HashSecret
     instead of libexpat's default CSPRNG.

   - bpo-34405(8): Updated to OpenSSL 1.1.0i for Windows builds.

   - bpo-33871(9): Fixed sending the part of the file in *note
     os.sendfile(): ab2. on macOS. Using the 'trailers' argument could
     cause sending more bytes from the input file than was specified.

   - bpo-32533(10): Fixed thread-safety of error handling in _ssl.

   - bpo-33136(11): Harden ssl module against LibreSSL
     CVE-2018-8970(12).  X509_VERIFY_PARAM_set1_host() is called with an
     explicit namelen.  A new test ensures that NULL bytes are not
     allowed.

   - bpo-33001(13): Minimal fix to prevent buffer overrun in os.symlink
     on Windows

   - bpo-32981(14): Regexes in difflib and poplib were vulnerable to
     catastrophic backtracking.  These regexes formed potential DOS
     vectors (REDOS). They have been refactored.  This resolves
     CVE-2018-1060(15) and CVE-2018-1061(16).  Patch by Jamie Davis.

   - bpo-28414(17): The ssl module now allows users to perform their own
     IDN en/decoding when using SNI.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35746

   (2) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5010

   (3) https://bugs.python.org/issue?@action=redirect&bpo=34812

   (4) https://bugs.python.org/issue?@action=redirect&bpo=34791

   (5) https://bugs.python.org/issue?@action=redirect&bpo=17239

   (6) https://bugs.python.org/issue?@action=redirect&bpo=34623

   (7) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14647

   (8) https://bugs.python.org/issue?@action=redirect&bpo=34405

   (9) https://bugs.python.org/issue?@action=redirect&bpo=33871

   (10) https://bugs.python.org/issue?@action=redirect&bpo=32533

   (11) https://bugs.python.org/issue?@action=redirect&bpo=33136

   (12) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8970

   (13) https://bugs.python.org/issue?@action=redirect&bpo=33001

   (14) https://bugs.python.org/issue?@action=redirect&bpo=32981

   (15) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1060

   (16) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1061

   (17) https://bugs.python.org/issue?@action=redirect&bpo=28414


File: python.info,  Node: Core and Builtins<49>,  Next: Library<48>,  Prev: Security<33>,  Up: Python 3 8 0 alpha 1

1.23.49.2 Core and Builtins
...........................

   - bpo-35877(1): Make parenthesis optional for named expressions in
     while statement.  Patch by Karthikeyan Singaravelan.

   - bpo-35814(2): Allow same right hand side expressions in annotated
     assignments as in normal ones.  In particular, ‘x: Tuple[int, int]
     = 1, 2’ (without parentheses on the right) is now allowed.

   - bpo-35766(3): Add the option to parse PEP 484 type comments in the
     ast module.  (Off by default.)  This is merging the key
     functionality of the third party fork thereof,
     [typed_ast](‘https://github.com/python/typed_ast’).

   - bpo-35713(4): Reorganize Python initialization to get working
     exceptions and sys.stderr earlier.

   - bpo-33416(5): Add end line and end column position information to
     the Python AST nodes.  This is a C-level backwards incompatible
     change.

   - bpo-35720(6): Fixed a minor memory leak in
     pymain_parse_cmdline_impl function in Modules/main.c

   - bpo-35634(7): ‘func(**kwargs)’ will now raise an error when
     ‘kwargs’ is a mapping containing multiple entries with the same
     key.  An error was already raised when other keyword arguments are
     passed before ‘**kwargs’ since Python 3.6.

   - bpo-35623(8): Fix a crash when sorting very long lists.  Patch by
     Stephan Hohe.

   - bpo-35214(9): clang Memory Sanitizer build instrumentation was
     added to work around false positives from posix, socket, time,
     test_io, and test_faulthandler.

   - bpo-35560(10): Fix an assertion error in *note format(): 5c3. in
     debug build for floating-point formatting with "n" format, zero
     padding and small width.  Release build is not impacted.  Patch by
     Karthikeyan Singaravelan.

   - bpo-35552(11): Format characters ‘%s’ and ‘%V’ in *note
     PyUnicode_FromFormat(): 33f. and ‘%s’ in *note
     PyBytes_FromFormat(): 192f. no longer read memory past the limit if
     'precision' is specified.

   - bpo-35504(12): Fix segfaults and *note SystemError: 51b.s when
     deleting certain attributes.  Patch by Zackery Spytz.

   - bpo-35504(13): Fixed a SystemError when delete the
     characters_written attribute of an OSError.

   - bpo-35494(14): Improved syntax error messages for unbalanced
     parentheses in f-string.

   - bpo-35444(15): Fixed error handling in pickling methods when fail
     to look up builtin "getattr".  Sped up pickling iterators.

   - bpo-35436(16): Fix various issues with memory allocation error
     handling.  Patch by Zackery Spytz.

   - bpo-35423(17): Separate the signal handling trigger in the eval
     loop from the "pending calls" machinery.  There is no semantic
     change and the difference in performance is insignificant.

   - bpo-35357(18): Internal attributes' names of unittest.mock._Call
     and unittest.mock.MagicProxy (name, parent & from_kall) are now
     prefixed with _mock_ in order to prevent clashes with widely used
     object attributes.  Fixed minor typo in test function name.

   - bpo-35372(19): Fixed the code page decoder for input longer than 2
     GiB containing undecodable bytes.

   - bpo-35336(20): Fix PYTHONCOERCECLOCALE=1 environment variable: only
     coerce the C locale if the LC_CTYPE locale is "C".

   - bpo-31241(21): The 'lineno' and 'col_offset' attributes of AST
     nodes for list comprehensions, generator expressions and tuples are
     now point to the opening parenthesis or square brace.  For tuples
     without parenthesis they point to the position of the first item.

   - bpo-33954(22): For *note str.format(): 5c7, ‘float.__format__()’
     and ‘complex.__format__()’ methods for non-ASCII decimal point when
     using the "n" formatter.

   - bpo-35269(23): Fix a possible segfault involving a newly created
     coroutine.  Patch by Zackery Spytz.

   - bpo-35224(24): Implement PEP 572(25) (assignment expressions).
     Patch by Emily Morehouse.

   - bpo-32492(26): Speed up ‘namedtuple()’ attribute access by 1.6x
     using a C fast-path for the name descriptors.  Patch by Pablo
     Galindo.

   - bpo-35214(27): Fixed an out of bounds memory access when parsing a
     truncated unicode escape sequence at the end of a string such as
     ‘'\N'’.  It would read one byte beyond the end of the memory
     allocation.

   - bpo-35214(28): The interpreter and extension modules have had
     annotations added so that they work properly under clang's Memory
     Sanitizer.  A new configure flag -with-memory-sanitizer has been
     added to make test builds of this nature easier to perform.

   - bpo-35193(29): Fix an off by one error in the bytecode peephole
     optimizer where it could read bytes beyond the end of bounds of an
     array when removing unreachable code.  This bug was present in
     every release of Python 3.6 and 3.7 until now.

   - bpo-35169(30): Improved error messages for forbidden assignments.

   - bpo-34022(31): Fix handling of hash-based bytecode files in *note
     zipimport: 118.  Patch by Elvis Pranskevichus.

   - bpo-28401(32): Debug builds will no longer to attempt to import
     extension modules built for the ABI as they were never compatible
     to begin with.  Patch by Stefano Rivera.

   - bpo-29341(33): Clarify in the docstrings of *note os: 91. methods
     that path-like objects are also accepted as input parameters.

   - bpo-35050(34): *note socket: b8.: Fix off-by-one bug in length
     check for ‘AF_ALG’ name and type.

   - bpo-29743(35): Raise *note ValueError: 1e7. instead of *note
     OverflowError: 825. in case of a negative ‘_length_’ in a *note
     ctypes.Array: 1930. subclass.  Also raise *note TypeError: 4dd.
     instead of *note AttributeError: 2f6. for non-integer ‘_length_’.
     Original patch by Oren Milman.

   - bpo-16806(36): Fix ‘lineno’ and ‘col_offset’ for multi-line string
     tokens.

   - bpo-35029(37): *note SyntaxWarning: 40c. raised as an exception at
     code generation time will be now replaced with a *note SyntaxError:
     173. for better error reporting.

   - bpo-34983(38): Expose *note symtable.Symbol.is_nonlocal(): 1931. in
     the symtable module.  Patch by Pablo Galindo.

   - bpo-34974(39): *note bytes: 1a5. and *note bytearray: 4e3.
     constructors no longer convert unexpected exceptions (e.g.  *note
     MemoryError: 15bc. and *note KeyboardInterrupt: 975.) to *note
     TypeError: 4dd.

   - bpo-34939(40): Allow annotated names in module namespace that are
     declared global before the annotation happens.  Patch by Pablo
     Galindo.

   - bpo-34973(41): Fixed crash in *note bytes(): 1a5. when the *note
     list: 5b6. argument is mutated while it is iterated.

   - bpo-34876(42): The 'lineno' and 'col_offset' attributes of the AST
     for decorated function and class refer now to the position of the
     corresponding ‘def’, ‘async def’ and ‘class’ instead of the
     position of the first decorator.  This leads to more correct line
     reporting in tracing.  This is the only case when the position of
     child AST nodes can precede the position of the parent AST node.

   - bpo-34879(43): Fix a possible null pointer dereference in
     bytesobject.c.  Patch by Zackery Spytz.

   - bpo-34784(44): Fix the implementation of PyStructSequence_NewType
     in order to create heap allocated StructSequences.

   - bpo-32912(45): A *note SyntaxWarning: 40c. is now emitted instead
     of a *note DeprecationWarning: 18b. for invalid escape sequences in
     string and bytes literals.

   - bpo-34854(46): Fixed a crash in compiling string annotations
     containing a lambda with a keyword-only argument that doesn't have
     a default value.

   - bpo-34850(47): The compiler now produces a *note SyntaxWarning:
     40c. when identity checks (‘is’ and ‘is not’) are used with certain
     types of literals (e.g.  strings, ints).  These can often work by
     accident in CPython, but are not guaranteed by the language spec.
     The warning advises users to use equality tests (‘==’ and ‘!=’)
     instead.

   - bpo-34824(48): Fix a possible null pointer dereference in
     Modules/_ssl.c.  Patch by Zackery Spytz.

   - bpo-30156(49): The C function ‘property_descr_get()’ uses a
     "cached" tuple to optimize function calls.  But this tuple can be
     discovered in debug mode with ‘sys.getobjects()’.  Remove the
     optimization, it's not really worth it and it causes 3 different
     crashes last years.

   - bpo-34762(50): Fix contextvars C API to use PyObject* pointer
     types.

   - bpo-34751(51): The hash function for tuples is now based on xxHash
     which gives better collision results on (formerly) pathological
     cases.  Additionally, on 64-bit systems it improves tuple hashes in
     general.  Patch by Jeroen Demeyer with substantial contributions by
     Tim Peters.

   - bpo-34735(52): Fix a memory leak in Modules/timemodule.c.  Patch by
     Zackery Spytz.

   - bpo-34683(53): Fixed a bug where some SyntaxError error pointed to
     locations that were off-by-one.

   - bpo-34651(54): Only allow the main interpreter to fork.  The avoids
     the possibility of affecting the main interpreter, which is
     critical to operation of the runtime.

   - bpo-34653(55): Remove unused function
     PyParser_SimpleParseStringFilename.

   - bpo-32236(56): Warn that line buffering is not supported if *note
     open(): 4c0. is called with binary mode and ‘buffering=1’.

   - bpo-34641(57): Further restrict the syntax of the left-hand side of
     keyword arguments in function calls.  In particular,
     ‘f((keyword)=arg)’ is now disallowed.

   - bpo-34637(58): Make the 'start' argument to 'sum()' visible as a
     keyword argument.

   - bpo-1621(59): Do not assume signed integer overflow behavior (C
     undefined behavior) when performing set hash table resizing.

   - bpo-34588(60): Fix an off-by-one in the recursive call pruning
     feature of traceback formatting.

   - bpo-34485(61): On Windows, the LC_CTYPE is now set to the user
     preferred locale at startup.  Previously, the LC_CTYPE locale was
     "C" at startup, but changed when calling setlocale(LC_CTYPE, "") or
     setlocale(LC_ALL, "").

   - bpo-34485(62): Standard streams like sys.stdout now use the
     "surrogateescape" error handler, instead of "strict", on the POSIX
     locale (when the C locale is not coerced and the UTF-8 Mode is
     disabled).

   - bpo-34485(63): Fix the error handler of standard streams like
     sys.stdout: PYTHONIOENCODING=":" is now ignored instead of setting
     the error handler to "strict".

   - bpo-34485(64): Python now gets the locale encoding with C code to
     initialize the encoding of standard streams like sys.stdout.
     Moreover, the encoding is now initialized to the Python codec name
     to get a normalized encoding name and to ensure that the codec is
     loaded.  The change avoids importing _bootlocale and _locale
     modules at startup by default.

   - bpo-34527(65): On FreeBSD, Py_DecodeLocale() and Py_EncodeLocale()
     now also forces the ASCII encoding if the LC_CTYPE locale is
     "POSIX", not only if the LC_CTYPE locale is "C".

   - bpo-34527(66): The UTF-8 Mode is now also enabled by the "POSIX"
     locale, not only by the "C" locale.

   - bpo-34403(67): On HP-UX with C or POSIX locale,
     sys.getfilesystemencoding() now returns "ascii" instead of "roman8"
     (when the UTF-8 Mode is disabled and the C locale is not coerced).

   - bpo-34523(68): The Python filesystem encoding is now read earlier
     during the Python initialization.

   - bpo-12458(69): Tracebacks show now correct line number for
     subexpressions in multiline expressions.  Tracebacks show now the
     line number of the first line for multiline expressions instead of
     the line number of the last subexpression.

   - bpo-34408(70): Prevent a null pointer dereference and resource
     leakage in ‘PyInterpreterState_New()’.

   - bpo-34400(71): Fix undefined behavior in parsetok.c.  Patch by
     Zackery Spytz.

   - bpo-33073(72): Added as_integer_ratio to ints to make them more
     interoperable with floats.

   - bpo-34377(73): Update valgrind suppression list to use
     ‘_PyObject_Free’/‘_PyObject_Realloc’ instead of
     ‘PyObject_Free’/‘PyObject_Realloc’.

   - bpo-34353(74): Added the "socket" option in the ‘stat.filemode()’
     Python implementation to match the C implementation.

   - bpo-34320(75): Fix ‘dict(od)’ didn't copy iteration order of
     OrderedDict.

   - bpo-34113(76): Fixed crash on debug builds when opcode stack was
     adjusted with negative numbers.  Patch by Constantin Petrisor.

   - bpo-34100(77): Compiler now merges constants in tuples and
     frozensets recursively.  Code attributes like ‘co_names’ are merged
     too.

   - bpo-34151(78): Performance of list concatenation, repetition and
     slicing operations is slightly improved.  Patch by Sergey Fedoseev.

   - bpo-34170(79): -X dev: it is now possible to override the memory
     allocator using PYTHONMALLOC even if the developer mode is enabled.

   - bpo-33237(80): Improved *note AttributeError: 2f6. message for
     partially initialized module.

   - bpo-34149(81): Fix min and max functions to get default behavior
     when key is None.

   - bpo-34125(82): Profiling of unbound built-in methods now works when
     ‘**kwargs’ is given.

   - bpo-34141(83): Optimized pickling atomic types (None, bool, int,
     float, bytes, str).

   - bpo-34126(84): Fix crashes when profiling certain invalid calls of
     unbound methods.  Patch by Jeroen Demeyer.

   - bpo-24618(85): Fixed reading invalid memory when create the code
     object with too small varnames tuple or too large argument counts.

   - bpo-34068(86): In *note io.IOBase.close(): 1db, ensure that the
     *note closed: 1932. attribute is not set with a live exception.
     Patch by Zackery Spytz and Serhiy Storchaka.

   - bpo-34087(87): Fix buffer overflow while converting unicode to
     numeric values.

   - bpo-34080(88): Fixed a memory leak in the compiler when it raised
     some uncommon errors during tokenizing.

   - bpo-34066(89): Disabled interruption by Ctrl-C between calling
     ‘open()’ and entering a 'with' block in ‘with open()’.

   - bpo-34042(90): Fix dict.copy() to maintain correct total refcount
     (as reported by sys.gettotalrefcount()).

   - bpo-33418(91): Fix potential memory leak in function object when it
     creates reference cycle.

   - bpo-33985(92): Implement contextvars.ContextVar.name attribute.

   - bpo-33956(93): Update vendored Expat library copy to version 2.2.5.

   - bpo-24596(94): Decref the module object in *note
     PyRun_SimpleFileExFlags(): 180b. before calling *note
     PyErr_Print(): 1847.  Patch by Zackery Spytz.

   - bpo-33451(95): Close directly executed pyc files before calling
     ‘PyEval_EvalCode()’.

   - bpo-1617161(96): The hash of ‘BuiltinMethodType’ instances (methods
     of built-in classes) now depends on the hash of the identity of
     '__self__' instead of its value.  The hash and equality of
     ‘ModuleType’ and ‘MethodWrapperType’ instances (methods of
     user-defined classes and some methods of built-in classes like
     ‘str.__add__’) now depend on the hash and equality of the identity
     of '__self__' instead of its value.  ‘MethodWrapperType’ instances
     no longer support ordering.

   - bpo-33824(97): Fix "LC_ALL=C python3.7 -V": reset properly the
     command line parser when the encoding changes after reading the
     Python configuration.

   - bpo-33803(98): Fix a crash in hamt.c caused by enabling GC tracking
     for an object that hadn't all of its fields set to NULL.

   - bpo-33738(99): Seven macro incompatibilities with the Limited API
     were fixed, and the macros *note PyIter_Check(): 17f7, *note
     PyIndex_Check(): 92e. and ‘PyExceptionClass_Name()’ were added as
     functions.  A script for automatic macro checks was added.

   - bpo-33786(100): Fix asynchronous generators to handle GeneratorExit
     in athrow() correctly

   - bpo-30167(101): ‘PyRun_SimpleFileExFlags’ removes ‘__cached__’ from
     module in addition to ‘__file__’.

   - bpo-33706(102): Fix a crash in Python initialization when parsing
     the command line options.  Thanks Christoph Gohlke for the bug
     report and the fix!

   - bpo-33597(103): Reduce ‘PyGC_Head’ size from 3 words to 2 words.

   - bpo-30654(104): Fixed reset of the SIGINT handler to SIG_DFL on
     interpreter shutdown even when there was a custom handler set
     previously.  Patch by Philipp Kerling.

   - bpo-33622(105): Fixed a leak when the garbage collector fails to
     add an object with the ‘__del__’ method or referenced by it into
     the *note gc.garbage: 1159. list.  *note PyGC_Collect(): 932. can
     now be called when an exception is set and preserves it.

   - bpo-33462(106): Make dict and dict views reversible.  Patch by Rémi
     Lapeyre.

   - bpo-23722(107): A *note RuntimeError: 179. is now raised when the
     custom metaclass doesn't provide the ‘__classcell__’ entry in the
     namespace passed to ‘type.__new__’.  A *note DeprecationWarning:
     18b. was emitted in Python 3.6-3.7.

   - bpo-33499(108): Add *note PYTHONPYCACHEPREFIX: 947. environment
     variable and *note -X: 15a. ‘pycache_prefix’ command-line option to
     set an alternate root directory for writing module bytecode cache
     files.

   - bpo-25711(109): The *note zipimport: 118. module has been rewritten
     in pure Python.

   - bpo-33509(110): Fix module_globals parameter of
     warnings.warn_explicit(): don't crash if module_globals is not a
     dict.

   - bpo-31849(111): Fix signed/unsigned comparison warning in pyhash.c.

   - bpo-33475(112): Fixed miscellaneous bugs in converting annotations
     to strings and optimized parentheses in the string representation.

   - bpo-20104(113): Added support for the ‘setpgroup’, ‘resetids’,
     ‘setsigmask’, ‘setsigdef’ and ‘scheduler’ parameters of
     ‘posix_spawn’.  Patch by Pablo Galindo.

   - bpo-33391(114): Fix a leak in set_symmetric_difference().

   - bpo-33363(115): Raise a SyntaxError for ‘async with’ and ‘async
     for’ statements outside of async functions.

   - bpo-28055(116): Fix unaligned accesses in siphash24().  Patch by
     Rolf Eike Beer.

   - bpo-33128(117): Fix a bug that causes PathFinder to appear twice on
     sys.meta_path.  Patch by Pablo Galindo Salgado.

   - bpo-33331(118): Modules imported last are now cleared first at
     interpreter shutdown.

   - bpo-33312(119): Fixed clang ubsan (undefined behavior sanitizer)
     warnings in dictobject.c by adjusting how the internal struct
     _dictkeysobject shared keys structure is declared.

   - bpo-33305(120): Improved syntax error messages for invalid
     numerical literals.

   - bpo-33306(121): Improved syntax error messages for unbalanced
     parentheses.

   - bpo-33234(122): The list constructor will pre-size and not
     over-allocate when the input length is known.

   - bpo-33270(123): Intern the names for all anonymous code objects.
     Patch by Zackery Spytz.

   - bpo-30455(124): The C and Python code and the documentation related
     to tokens are now generated from a single source file
     ‘Grammar/Tokens’.

   - bpo-33176(125): Add a ‘toreadonly()’ method to memoryviews.

   - bpo-33231(126): Fix potential memory leak in ‘normalizestring()’.

   - bpo-33205(127): Change dict growth function from
     ‘round_up_to_power_2(used*2+hashtable_size/2)’ to
     ‘round_up_to_power_2(used*3)’.  Previously, dict is shrinked only
     when ‘used == 0’.  Now dict has more chance to be shrinked.

   - bpo-29922(128): Improved error messages in 'async with' when
     ‘__aenter__()’ or ‘__aexit__()’ return non-awaitable object.

   - bpo-33199(129): Fix ‘ma_version_tag’ in dict implementation is
     uninitialized when copying from key-sharing dict.

   - bpo-33053(130): When using the -m switch, sys.path[0] is now
     explicitly expanded as the 'starting' working directory, rather
     than being left as the empty path (which allows imports from the
     current working directory at the time of the import)

   - bpo-33138(131): Changed standard error message for non-pickleable
     and non-copyable types.  It now says "cannot pickle" instead of
     "can't pickle" or "cannot serialize".

   - bpo-33018(132): Improve consistency of errors raised by
     ‘issubclass()’ when called with a non-class and an abstract base
     class as the first and second arguments, respectively.  Patch by
     Josh Bronson.

   - bpo-33083(133): ‘math.factorial’ no longer accepts arguments that
     are not int-like.  Patch by Pablo Galindo.

   - bpo-33041(134): Added new opcode *note END_ASYNC_FOR: a4d. and
     fixes the following issues:

        * Setting global *note StopAsyncIteration: 1933. no longer
          breaks ‘async for’ loops.

        * Jumping into an ‘async for’ loop is now disabled.

        * Jumping out of an ‘async for’ loop no longer corrupts the
          stack.

   - bpo-25750(135): Fix rare Python crash due to bad refcounting in
     ‘type_getattro()’ if a descriptor deletes itself from the class.
     Patch by Jeroen Demeyer.

   - bpo-33041(136): Fixed bytecode generation for "async for" with a
     complex target.  A StopAsyncIteration raised on assigning or
     unpacking will be now propagated instead of stopping the iteration.

   - bpo-33026(137): Fixed jumping out of "with" block by setting
     f_lineno.

   - bpo-33005(138): Fix a crash on fork when using a custom memory
     allocator (ex: using PYTHONMALLOC env var).  _PyGILState_Reinit()
     and _PyInterpreterState_Enable() now use the default RAW memory
     allocator to allocate a new interpreters mutex on fork.

   - bpo-32911(139): Due to unexpected compatibility issues discovered
     during downstream beta testing, reverted bpo-29463(140).
     ‘docstring’ field is removed from Module, ClassDef, FunctionDef,
     and AsyncFunctionDef ast nodes which was added in 3.7a1.  Docstring
     expression is restored as a first statement in their body.  Based
     on patch by Inada Naoki.

   - bpo-17288(141): Prevent jumps from 'return' and 'exception' trace
     events.

   - bpo-32946(142): Importing names from already imported module with
     "from ...  import ..."  is now 30% faster if the module is not a
     package.

   - bpo-32932(143): Make error message more revealing when there are
     non-str objects in ‘__all__’.

   - bpo-32925(144): Optimized iterating and containing test for literal
     lists consisting of non-constants: ‘x in [a, b]’ and ‘for x in [a,
     b]’.  The case of all constant elements already was optimized.

   - bpo-32889(145): Update Valgrind suppression list to account for the
     rename of ‘Py_ADDRESS_IN_RANG’ to ‘address_in_range’.

   - bpo-32836(146): Don't use temporary variables in cases of
     list/dict/set comprehensions

   - bpo-31356(147): Remove the new API added in bpo-31356(148)
     (gc.ensure_disabled() context manager).

   - bpo-32305(149): For namespace packages, ensure that both ‘__file__’
     and ‘__spec__.origin’ are set to None.

   - bpo-32303(150): Make sure ‘__spec__.loader’ matches ‘__loader__’
     for namespace packages.

   - bpo-32711(151): Fix the warning messages for Python/ast_unparse.c.
     Patch by Stéphane Wirtel

   - bpo-32583(152): Fix possible crashing in builtin Unicode decoders
     caused by write out-of-bound errors when using customized decode
     error handlers.

   - bpo-32489(153): A *note continue: 96d. statement is now allowed in
     the *note finally: 96e. clause.

   - bpo-17611(154): Simplified the interpreter loop by moving the logic
     of unrolling the stack of blocks into the compiler.  The compiler
     emits now explicit instructions for adjusting the stack of values
     and calling the cleaning up code for *note break: a4c, *note
     continue: 96d. and *note return: 972.

     Removed opcodes ‘BREAK_LOOP’, ‘CONTINUE_LOOP’, ‘SETUP_LOOP’ and
     ‘SETUP_EXCEPT’.  Added new opcodes ‘ROT_FOUR’, ‘BEGIN_FINALLY’ and
     ‘CALL_FINALLY’ and ‘POP_FINALLY’.  Changed the behavior of
     ‘END_FINALLY’ and ‘WITH_CLEANUP_START’.

   - bpo-32285(155): New function unicodedata.is_normalized, which can
     check whether a string is in a specific normal form.

   - bpo-10544(156): Yield expressions are now disallowed in
     comprehensions and generator expressions except the expression for
     the outermost iterable.

   - bpo-32117(157): Iterable unpacking is now allowed without
     parentheses in yield and return statements, e.g.  ‘yield 1, 2, 3,
     *rest’.  Thanks to David Cuthbert for the change and Jordan Chapman
     for added tests.

   - bpo-31902(158): Fix the ‘col_offset’ attribute for ast nodes
     ‘ast.AsyncFor’, ‘ast.AsyncFunctionDef’, and ‘ast.AsyncWith’.
     Previously, ‘col_offset’ pointed to the keyword after ‘async’.

   - bpo-25862(159): Fix assertion failures in the ‘tell()’ method of
     ‘io.TextIOWrapper’.  Patch by Zackery Spytz.

   - bpo-21983(160): Fix a crash in ‘ctypes.cast()’ in case the type
     argument is a ctypes structured data type.  Patch by Eryk Sun and
     Oren Milman.

   - bpo-31577(161): Fix a crash in ‘os.utime()’ in case of a bad ns
     argument.  Patch by Oren Milman.

   - bpo-29832(162): Remove references to 'getsockaddrarg' from various
     socket error messages.  Patch by Oren Milman.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35877

   (2) https://bugs.python.org/issue?@action=redirect&bpo=35814

   (3) https://bugs.python.org/issue?@action=redirect&bpo=35766

   (4) https://bugs.python.org/issue?@action=redirect&bpo=35713

   (5) https://bugs.python.org/issue?@action=redirect&bpo=33416

   (6) https://bugs.python.org/issue?@action=redirect&bpo=35720

   (7) https://bugs.python.org/issue?@action=redirect&bpo=35634

   (8) https://bugs.python.org/issue?@action=redirect&bpo=35623

   (9) https://bugs.python.org/issue?@action=redirect&bpo=35214

   (10) https://bugs.python.org/issue?@action=redirect&bpo=35560

   (11) https://bugs.python.org/issue?@action=redirect&bpo=35552

   (12) https://bugs.python.org/issue?@action=redirect&bpo=35504

   (13) https://bugs.python.org/issue?@action=redirect&bpo=35504

   (14) https://bugs.python.org/issue?@action=redirect&bpo=35494

   (15) https://bugs.python.org/issue?@action=redirect&bpo=35444

   (16) https://bugs.python.org/issue?@action=redirect&bpo=35436

   (17) https://bugs.python.org/issue?@action=redirect&bpo=35423

   (18) https://bugs.python.org/issue?@action=redirect&bpo=35357

   (19) https://bugs.python.org/issue?@action=redirect&bpo=35372

   (20) https://bugs.python.org/issue?@action=redirect&bpo=35336

   (21) https://bugs.python.org/issue?@action=redirect&bpo=31241

   (22) https://bugs.python.org/issue?@action=redirect&bpo=33954

   (23) https://bugs.python.org/issue?@action=redirect&bpo=35269

   (24) https://bugs.python.org/issue?@action=redirect&bpo=35224

   (25) https://peps.python.org/pep-0572/

   (26) https://bugs.python.org/issue?@action=redirect&bpo=32492

   (27) https://bugs.python.org/issue?@action=redirect&bpo=35214

   (28) https://bugs.python.org/issue?@action=redirect&bpo=35214

   (29) https://bugs.python.org/issue?@action=redirect&bpo=35193

   (30) https://bugs.python.org/issue?@action=redirect&bpo=35169

   (31) https://bugs.python.org/issue?@action=redirect&bpo=34022

   (32) https://bugs.python.org/issue?@action=redirect&bpo=28401

   (33) https://bugs.python.org/issue?@action=redirect&bpo=29341

   (34) https://bugs.python.org/issue?@action=redirect&bpo=35050

   (35) https://bugs.python.org/issue?@action=redirect&bpo=29743

   (36) https://bugs.python.org/issue?@action=redirect&bpo=16806

   (37) https://bugs.python.org/issue?@action=redirect&bpo=35029

   (38) https://bugs.python.org/issue?@action=redirect&bpo=34983

   (39) https://bugs.python.org/issue?@action=redirect&bpo=34974

   (40) https://bugs.python.org/issue?@action=redirect&bpo=34939

   (41) https://bugs.python.org/issue?@action=redirect&bpo=34973

   (42) https://bugs.python.org/issue?@action=redirect&bpo=34876

   (43) https://bugs.python.org/issue?@action=redirect&bpo=34879

   (44) https://bugs.python.org/issue?@action=redirect&bpo=34784

   (45) https://bugs.python.org/issue?@action=redirect&bpo=32912

   (46) https://bugs.python.org/issue?@action=redirect&bpo=34854

   (47) https://bugs.python.org/issue?@action=redirect&bpo=34850

   (48) https://bugs.python.org/issue?@action=redirect&bpo=34824

   (49) https://bugs.python.org/issue?@action=redirect&bpo=30156

   (50) https://bugs.python.org/issue?@action=redirect&bpo=34762

   (51) https://bugs.python.org/issue?@action=redirect&bpo=34751

   (52) https://bugs.python.org/issue?@action=redirect&bpo=34735

   (53) https://bugs.python.org/issue?@action=redirect&bpo=34683

   (54) https://bugs.python.org/issue?@action=redirect&bpo=34651

   (55) https://bugs.python.org/issue?@action=redirect&bpo=34653

   (56) https://bugs.python.org/issue?@action=redirect&bpo=32236

   (57) https://bugs.python.org/issue?@action=redirect&bpo=34641

   (58) https://bugs.python.org/issue?@action=redirect&bpo=34637

   (59) https://bugs.python.org/issue?@action=redirect&bpo=1621

   (60) https://bugs.python.org/issue?@action=redirect&bpo=34588

   (61) https://bugs.python.org/issue?@action=redirect&bpo=34485

   (62) https://bugs.python.org/issue?@action=redirect&bpo=34485

   (63) https://bugs.python.org/issue?@action=redirect&bpo=34485

   (64) https://bugs.python.org/issue?@action=redirect&bpo=34485

   (65) https://bugs.python.org/issue?@action=redirect&bpo=34527

   (66) https://bugs.python.org/issue?@action=redirect&bpo=34527

   (67) https://bugs.python.org/issue?@action=redirect&bpo=34403

   (68) https://bugs.python.org/issue?@action=redirect&bpo=34523

   (69) https://bugs.python.org/issue?@action=redirect&bpo=12458

   (70) https://bugs.python.org/issue?@action=redirect&bpo=34408

   (71) https://bugs.python.org/issue?@action=redirect&bpo=34400

   (72) https://bugs.python.org/issue?@action=redirect&bpo=33073

   (73) https://bugs.python.org/issue?@action=redirect&bpo=34377

   (74) https://bugs.python.org/issue?@action=redirect&bpo=34353

   (75) https://bugs.python.org/issue?@action=redirect&bpo=34320

   (76) https://bugs.python.org/issue?@action=redirect&bpo=34113

   (77) https://bugs.python.org/issue?@action=redirect&bpo=34100

   (78) https://bugs.python.org/issue?@action=redirect&bpo=34151

   (79) https://bugs.python.org/issue?@action=redirect&bpo=34170

   (80) https://bugs.python.org/issue?@action=redirect&bpo=33237

   (81) https://bugs.python.org/issue?@action=redirect&bpo=34149

   (82) https://bugs.python.org/issue?@action=redirect&bpo=34125

   (83) https://bugs.python.org/issue?@action=redirect&bpo=34141

   (84) https://bugs.python.org/issue?@action=redirect&bpo=34126

   (85) https://bugs.python.org/issue?@action=redirect&bpo=24618

   (86) https://bugs.python.org/issue?@action=redirect&bpo=34068

   (87) https://bugs.python.org/issue?@action=redirect&bpo=34087

   (88) https://bugs.python.org/issue?@action=redirect&bpo=34080

   (89) https://bugs.python.org/issue?@action=redirect&bpo=34066

   (90) https://bugs.python.org/issue?@action=redirect&bpo=34042

   (91) https://bugs.python.org/issue?@action=redirect&bpo=33418

   (92) https://bugs.python.org/issue?@action=redirect&bpo=33985

   (93) https://bugs.python.org/issue?@action=redirect&bpo=33956

   (94) https://bugs.python.org/issue?@action=redirect&bpo=24596

   (95) https://bugs.python.org/issue?@action=redirect&bpo=33451

   (96) https://bugs.python.org/issue?@action=redirect&bpo=1617161

   (97) https://bugs.python.org/issue?@action=redirect&bpo=33824

   (98) https://bugs.python.org/issue?@action=redirect&bpo=33803

   (99) https://bugs.python.org/issue?@action=redirect&bpo=33738

   (100) https://bugs.python.org/issue?@action=redirect&bpo=33786

   (101) https://bugs.python.org/issue?@action=redirect&bpo=30167

   (102) https://bugs.python.org/issue?@action=redirect&bpo=33706

   (103) https://bugs.python.org/issue?@action=redirect&bpo=33597

   (104) https://bugs.python.org/issue?@action=redirect&bpo=30654

   (105) https://bugs.python.org/issue?@action=redirect&bpo=33622

   (106) https://bugs.python.org/issue?@action=redirect&bpo=33462

   (107) https://bugs.python.org/issue?@action=redirect&bpo=23722

   (108) https://bugs.python.org/issue?@action=redirect&bpo=33499

   (109) https://bugs.python.org/issue?@action=redirect&bpo=25711

   (110) https://bugs.python.org/issue?@action=redirect&bpo=33509

   (111) https://bugs.python.org/issue?@action=redirect&bpo=31849

   (112) https://bugs.python.org/issue?@action=redirect&bpo=33475

   (113) https://bugs.python.org/issue?@action=redirect&bpo=20104

   (114) https://bugs.python.org/issue?@action=redirect&bpo=33391

   (115) https://bugs.python.org/issue?@action=redirect&bpo=33363

   (116) https://bugs.python.org/issue?@action=redirect&bpo=28055

   (117) https://bugs.python.org/issue?@action=redirect&bpo=33128

   (118) https://bugs.python.org/issue?@action=redirect&bpo=33331

   (119) https://bugs.python.org/issue?@action=redirect&bpo=33312

   (120) https://bugs.python.org/issue?@action=redirect&bpo=33305

   (121) https://bugs.python.org/issue?@action=redirect&bpo=33306

   (122) https://bugs.python.org/issue?@action=redirect&bpo=33234

   (123) https://bugs.python.org/issue?@action=redirect&bpo=33270

   (124) https://bugs.python.org/issue?@action=redirect&bpo=30455

   (125) https://bugs.python.org/issue?@action=redirect&bpo=33176

   (126) https://bugs.python.org/issue?@action=redirect&bpo=33231

   (127) https://bugs.python.org/issue?@action=redirect&bpo=33205

   (128) https://bugs.python.org/issue?@action=redirect&bpo=29922

   (129) https://bugs.python.org/issue?@action=redirect&bpo=33199

   (130) https://bugs.python.org/issue?@action=redirect&bpo=33053

   (131) https://bugs.python.org/issue?@action=redirect&bpo=33138

   (132) https://bugs.python.org/issue?@action=redirect&bpo=33018

   (133) https://bugs.python.org/issue?@action=redirect&bpo=33083

   (134) https://bugs.python.org/issue?@action=redirect&bpo=33041

   (135) https://bugs.python.org/issue?@action=redirect&bpo=25750

   (136) https://bugs.python.org/issue?@action=redirect&bpo=33041

   (137) https://bugs.python.org/issue?@action=redirect&bpo=33026

   (138) https://bugs.python.org/issue?@action=redirect&bpo=33005

   (139) https://bugs.python.org/issue?@action=redirect&bpo=32911

   (140) https://bugs.python.org/issue?@action=redirect&bpo=29463

   (141) https://bugs.python.org/issue?@action=redirect&bpo=17288

   (142) https://bugs.python.org/issue?@action=redirect&bpo=32946

   (143) https://bugs.python.org/issue?@action=redirect&bpo=32932

   (144) https://bugs.python.org/issue?@action=redirect&bpo=32925

   (145) https://bugs.python.org/issue?@action=redirect&bpo=32889

   (146) https://bugs.python.org/issue?@action=redirect&bpo=32836

   (147) https://bugs.python.org/issue?@action=redirect&bpo=31356

   (148) https://bugs.python.org/issue?@action=redirect&bpo=31356

   (149) https://bugs.python.org/issue?@action=redirect&bpo=32305

   (150) https://bugs.python.org/issue?@action=redirect&bpo=32303

   (151) https://bugs.python.org/issue?@action=redirect&bpo=32711

   (152) https://bugs.python.org/issue?@action=redirect&bpo=32583

   (153) https://bugs.python.org/issue?@action=redirect&bpo=32489

   (154) https://bugs.python.org/issue?@action=redirect&bpo=17611

   (155) https://bugs.python.org/issue?@action=redirect&bpo=32285

   (156) https://bugs.python.org/issue?@action=redirect&bpo=10544

   (157) https://bugs.python.org/issue?@action=redirect&bpo=32117

   (158) https://bugs.python.org/issue?@action=redirect&bpo=31902

   (159) https://bugs.python.org/issue?@action=redirect&bpo=25862

   (160) https://bugs.python.org/issue?@action=redirect&bpo=21983

   (161) https://bugs.python.org/issue?@action=redirect&bpo=31577

   (162) https://bugs.python.org/issue?@action=redirect&bpo=29832


File: python.info,  Node: Library<48>,  Next: Documentation<43>,  Prev: Core and Builtins<49>,  Up: Python 3 8 0 alpha 1

1.23.49.3 Library
.................

   - bpo-35845(1): Add 'order' parameter to memoryview.tobytes().

   - bpo-35864(2): The _asdict() method for collections.namedtuple now
     returns a regular dict instead of an OrderedDict.

   - bpo-35537(3): An ExitStack is now used internally within
     subprocess.Popen to clean up pipe file handles.  No behavior change
     in normal operation.  But if closing one handle were ever to cause
     an exception, the others will now be closed instead of leaked.
     (patch by Giampaolo Rodola)

   - bpo-35847(4): RISC-V needed the CTYPES_PASS_BY_REF_HACK. Fixes
     ctypes Structure test_pass_by_value.

   - bpo-35813(5): Shared memory submodule added to multiprocessing to
     avoid need for serialization between processes

   - bpo-35780(6): Fix lru_cache() errors arising in recursive,
     reentrant, or multi-threaded code.  These errors could result in
     orphan links and in the cache being trapped in a state with fewer
     than the specified maximum number of links.  Fix handling of
     negative maxsize which should have been treated as zero.  Fix
     errors in toggling the "full" status flag.  Fix misordering of
     links when errors are encountered.  Sync-up the C code and pure
     Python code for the space saving path in functions with a single
     positional argument.  In this common case, the space overhead of an
     lru cache entry is reduced by almost half.  Fix counting of cache
     misses.  In error cases, the miss count was out of sync with the
     actual number of times the underlying user function was called.

   - bpo-35537(7): *note os.posix_spawn(): 205. and *note
     os.posix_spawnp(): 1935. now have a 'setsid' parameter.

   - bpo-23846(8): *note asyncio.ProactorEventLoop: 5ae. now catches and
     logs send errors when the self-pipe is full.

   - bpo-34323(9): *note asyncio: 8.: Enhance ‘IocpProactor.close()’
     log: wait 1 second before the first log, then log every second.
     Log also the number of seconds since ‘close()’ was called.

   - bpo-35674(10): Add a new *note os.posix_spawnp(): 1935. function.
     Patch by Joannah Nanjekye.

   - bpo-35733(11): ‘ast.Constant(boolean)’ no longer an instance of
     ‘ast.Num’.  Patch by Anthony Sottile.

   - bpo-35726(12): QueueHandler.prepare() now makes a copy of the
     record before modifying and enqueueing it, to avoid affecting other
     handlers in the chain.

   - bpo-35719(13): Sped up multi-argument *note math: 81. functions
     atan2(), copysign(), remainder() and hypot() by 1.3-2.5 times.

   - bpo-35717(14): Fix KeyError exception raised when using enums and
     compile.  Patch contributed by Rémi Lapeyre.

   - bpo-35699(15): Fixed detection of Visual Studio Build Tools 2017 in
     distutils

   - bpo-32710(16): Fix memory leaks in asyncio ProactorEventLoop on
     overlapped operation failure.

   - bpo-35702(17): The *note time.CLOCK_UPTIME_RAW: 9e6. constant is
     now available for macOS 10.12.

   - bpo-32710(18): Fix a memory leak in asyncio in the
     ProactorEventLoop when ‘ReadFile()’ or ‘WSASend()’ overlapped
     operation fail immediately: release the internal buffer.

   - bpo-35682(19): Fix ‘asyncio.ProactorEventLoop.sendfile()’: don't
     attempt to set the result of an internal future if it's already
     done.

   - bpo-35283(20): Add a deprecated warning for the
     ‘threading.Thread.isAlive()’ method.  Patch by Donghee Na.

   - bpo-35664(21): Improve operator.itemgetter() performance by 33%
     with optimized argument handling and with adding a fast path for
     the common case of a single non-negative integer index into a tuple
     (which is the typical use case in the standard library).

   - bpo-35643(22): Fixed a SyntaxWarning: invalid escape sequence in
     Modules/_sha3/cleanup.py.  Patch by Mickaël Schoentgen.

   - bpo-35619(23): Improved support of custom data descriptors in *note
     help(): 87c. and *note pydoc: a3.

   - bpo-28503(24): The ‘crypt’ module now internally uses the
     ‘crypt_r()’ library function instead of ‘crypt()’ when available.

   - bpo-35614(25): Fixed help() on metaclasses.  Patch by Sanyam
     Khurana.

   - bpo-35568(26): Expose ‘raise(signum)’ as ‘raise_signal’

   - bpo-35588(27): The floor division and modulo operations and the
     *note divmod(): 945. function on *note fractions.Fraction: 1c7.
     types are 2-4x faster.  Patch by Stefan Behnel.

   - bpo-35585(28): Speed-up building enums by value, e.g.
     http.HTTPStatus(200).

   - bpo-30561(29): random.gammavariate(1.0, beta) now computes the same
     result as random.expovariate(1.0 / beta).  This synchronizes the
     two algorithms and eliminates some idiosyncrasies in the old
     implementation.  It does however produce a difference stream of
     random variables than it used to.

   - bpo-35537(30): The *note subprocess: c1. module can now use the
     *note os.posix_spawn(): 205. function in some cases for better
     performance.

   - bpo-35526(31): Delaying the 'joke' of barry_as_FLUFL.mandatory to
     Python version 4.0

   - bpo-35523(32): Remove *note ctypes: 22. callback workaround: no
     longer create a callback at startup.  Avoid SELinux alert on
     ‘import ctypes’ and ‘import uuid’.

   - bpo-31784(33): *note uuid.uuid1(): b4f. now calls *note
     time.time_ns(): a8a. rather than ‘int(time.time() * 1e9)’.

   - bpo-35513(34): ‘TextTestRunner’ of ‘unittest.runner’ now uses *note
     time.perf_counter(): a2b. rather than *note time.time(): 239. to
     measure the execution time of a test: *note time.time(): 239. can
     go backwards, whereas *note time.perf_counter(): a2b. is monotonic.

   - bpo-35502(35): Fixed reference leaks in *note
     xml.etree.ElementTree.TreeBuilder: 9f8. in case of unfinished
     building of the tree (in particular when an error was raised during
     parsing XML).

   - bpo-35348(36): Make *note platform.architecture(): 1581. parsing of
     ‘file’ command output more reliable: add the ‘-b’ option to the
     ‘file’ command to omit the filename, force the usage of the C
     locale, and search also the "shared object" pattern.

   - bpo-35491(37): *note multiprocessing: 86.: Add ‘Pool.__repr__()’
     and enhance ‘BaseProcess.__repr__()’ (add pid and parent pid) to
     ease debugging.  Pool state constant values are now strings instead
     of integers, for example ‘RUN’ value becomes ‘'RUN'’ instead of
     ‘0’.

   - bpo-35477(38): ‘multiprocessing.Pool.__enter__()’ now fails if the
     pool is not running: ‘with pool:’ fails if used more than once.

   - bpo-31446(39): Copy command line that was passed to CreateProcessW
     since this function can change the content of the input buffer.

   - bpo-35471(40): Python 2.4 dropped MacOS 9 support.  The macpath
     module was deprecated in Python 3.7.  The module is now removed.

   - bpo-23057(41): Unblock Proactor event loop when keyboard interrupt
     is received on Windows

   - bpo-35052(42): Fix xml.dom.minidom cloneNode() on a document with
     an entity: pass the correct arguments to the user data handler of
     an entity.

   - bpo-20239(43): Allow repeated assignment deletion of *note
     unittest.mock.Mock: 9ef. attributes.  Patch by Pablo Galindo.

   - bpo-17185(44): Set ‘__signature__’ on mock for *note inspect: 72.
     to get signature.  Patch by Karthikeyan Singaravelan.

   - bpo-35445(45): Memory errors during creating posix.environ no
     longer ignored.

   - bpo-35415(46): Validate fileno= argument to socket.socket().

   - bpo-35424(47): ‘multiprocessing.Pool’ destructor now emits *note
     ResourceWarning: 229. if the pool is still running.

   - bpo-35330(48): When a ‘Mock’ instance was used to wrap an object,
     if ‘side_effect’ is used in one of the mocks of it methods, don't
     call the original implementation and return the result of using the
     side effect the same way that it is done with return_value.

   - bpo-35346(49): Drop Mac OS 9 and Rhapsody support from the *note
     platform: 98. module.  Rhapsody last release was in 2000.  Mac OS 9
     last release was in 2001.

   - bpo-10496(50): ‘check_environ()’ of ‘distutils.utils’ now catches
     *note KeyError: 2fb. on calling *note pwd.getpwuid(): 1936.: don't
     create the ‘HOME’ environment variable in this case.

   - bpo-10496(51): ‘posixpath.expanduser()’ now returns the input
     'path' unchanged if the ‘HOME’ environment variable is not set and
     the current user has no home directory (if the current user
     identifier doesn't exist in the password database).  This change
     fix the *note site: b5. module if the current user doesn't exist in
     the password database (if the user has no home directory).

   - bpo-35389(52): *note platform.libc_ver(): 1937. now uses
     ‘os.confstr('CS_GNU_LIBC_VERSION')’ if available and the
     'executable' parameter is not set.

   - bpo-35394(53): Add empty slots to asyncio abstract protocols.

   - bpo-35310(54): Fix a bug in *note select.select(): d46. where, in
     some cases, the file descriptor sequences were returned unmodified
     after a signal interruption, even though the file descriptors might
     not be ready yet.  *note select.select(): d46. will now always
     return empty lists if a timeout has occurred.  Patch by Oran
     Avraham.

   - bpo-35380(55): Enable TCP_NODELAY on Windows for proactor asyncio
     event loop.

   - bpo-35341(56): Add generic version of ‘collections.OrderedDict’ to
     the ‘typing’ module.  Patch by Ismo Toijala.

   - bpo-35371(57): Fixed possible crash in ‘os.utime()’ on Windows when
     pass incorrect arguments.

   - bpo-35346(58): *note platform.uname(): 1938. now redirects ‘stderr’
     to *note os.devnull: 1939. when running external programs like ‘cmd
     /c ver’.

   - bpo-35066(59): Previously, calling the strftime() method on a
     datetime object with a trailing '%' in the format string would
     result in an exception.  However, this only occurred when the
     datetime C module was being used; the python implementation did not
     match this behavior.  Datetime is now PEP-399 compliant, and will
     not throw an exception on a trailing '%'.

   - bpo-35345(60): The function ‘platform.popen’ has been removed, it
     was deprecated since Python 3.3: use *note os.popen(): a2a.
     instead.

   - bpo-35344(61): On macOS, *note platform.platform(): 1657. now uses
     *note platform.mac_ver(): 193a, if it returns a non-empty release
     string, to get the macOS version rather than the darwin version.

   - bpo-35312(62): Make ‘lib2to3.pgen2.parse.ParseError’ round-trip
     pickle-able.  Patch by Anthony Sottile.

   - bpo-35308(63): Fix regression in ‘webbrowser’ where default
     browsers may be preferred over browsers in the ‘BROWSER’
     environment variable.

   - bpo-24746(64): Avoid stripping trailing whitespace in doctest fancy
     diff.  Original patch by R. David Murray & Jairo Trad.  Enhanced by
     Sanyam Khurana.

   - bpo-28604(65): *note locale.localeconv(): ba5. now sets temporarily
     the ‘LC_CTYPE’ locale to the ‘LC_MONETARY’ locale if the two
     locales are different and monetary strings are non-ASCII. This
     temporary change affects other threads.

   - bpo-35277(66): Update ensurepip to install pip 18.1 and setuptools
     40.6.2.

   - bpo-24209(67): Adds IPv6 support when invoking http.server
     directly.

   - bpo-35226(68): Recursively check arguments when testing for
     equality of *note unittest.mock.call: 18d3. objects and add note
     that tracking of parameters used to create ancestors of mocks in
     ‘mock_calls’ is not possible.

   - bpo-29564(69): The warnings module now suggests to enable
     tracemalloc if the source is specified, the tracemalloc module is
     available, but tracemalloc is not tracing memory allocations.

   - bpo-35189(70): Modify the following fnctl function to retry if
     interrupted by a signal (EINTR): flock, lockf, fnctl

   - bpo-30064(71): Use add_done_callback() in sock_* asyncio API to
     unsubscribe reader/writer early on calcellation.

   - bpo-35186(72): Removed the "built with" comment added when
     ‘setup.py upload’ is used with either ‘bdist_rpm’ or ‘bdist_dumb’.

   - bpo-35152(73): Allow sending more than 2 GB at once on a
     multiprocessing connection on non-Windows systems.

   - bpo-35062(74): Fix incorrect parsing of *note
     io.IncrementalNewlineDecoder: 15c3.'s 'translate' argument.

   - bpo-35065(75): Remove ‘StreamReaderProtocol._untrack_reader’.  The
     call to ‘_untrack_reader’ is currently performed too soon, causing
     the protocol to forget about the reader before ‘connection_lost’
     can run and feed the EOF to the reader.

   - bpo-34160(76): ElementTree and minidom now preserve the attribute
     order specified by the user.

   - bpo-35079(77): Improve difflib.SequenceManager.get_matching_blocks
     doc by adding 'non-overlapping' and changing '!=' to '<'.

   - bpo-33710(78): Deprecated ‘l*gettext()’ functions and methods in
     the *note gettext: 59. module.  They return encoded bytes instead
     of Unicode strings and are artifacts from Python 2 times.  Also
     deprecated functions and methods related to setting the charset for
     ‘l*gettext()’ functions and methods.

   - bpo-35017(79): *note socketserver.BaseServer.serve_forever(): 10d8.
     now exits immediately if it's *note shutdown(): 193b. method is
     called while it is polling for new events.

   - bpo-35024(80): ‘importlib’ no longer logs ‘wrote <bytecode path>’
     redundantly after ‘(created|could not create) <bytecode path>’ is
     already logged.  Patch by Quentin Agren.

   - bpo-35047(81): ‘unittest.mock’ now includes mock calls in exception
     messages if ‘assert_not_called’, ‘assert_called_once’, or
     ‘assert_called_once_with’ fails.  Patch by Petter Strandmark.

   - bpo-31047(82): Fix ‘ntpath.abspath’ regression where it didn't
     remove a trailing separator on Windows.  Patch by Tim Graham.

   - bpo-35053(83): tracemalloc now tries to update the traceback when
     an object is reused from a "free list" (optimization for faster
     object creation, used by the builtin list type for example).

   - bpo-31553(84): Add the -json-lines option to json.tool.  Patch by
     hongweipeng.

   - bpo-34794(85): Fixed a leak in Tkinter when pass the Python wrapper
     around Tcl_Obj back to Tcl/Tk.

   - bpo-34909(86): Enum: fix grandchildren subclassing when parent
     mixed with concrete data types.

   - bpo-35022(87): *note unittest.mock.MagicMock: e33. now supports the
     ‘__fspath__’ method (from *note os.PathLike: bf8.).

   - bpo-35008(88): Fixed references leaks when call the
     ‘__setstate__()’ method of *note xml.etree.ElementTree.Element:
     2e2. in the C implementation for already initialized element.

   - bpo-23420(89): Verify the value for the parameter '-s' of the
     cProfile CLI. Patch by Robert Kuska

   - bpo-33947(90): dataclasses now handle recursive reprs without
     raising RecursionError.

   - bpo-34890(91): Make *note inspect.iscoroutinefunction(): 439, *note
     inspect.isgeneratorfunction(): 16d6. and *note
     inspect.isasyncgenfunction(): 16d7. work with *note
     functools.partial(): 356.  Patch by Pablo Galindo.

   - bpo-34521(92): Use *note socket.CMSG_SPACE(): 193c. to calculate
     ancillary data size instead of *note socket.CMSG_LEN(): 193d. in
     ‘multiprocessing.reduction.recvfds()’ as RFC 3542(93) requires the
     use of the former for portable applications.

   - bpo-31522(94): The ‘mailbox.mbox.get_string’ function 'from_'
     parameter can now successfully be set to a non-default value.

   - bpo-34970(95): Protect tasks weak set manipulation in
     ‘asyncio.all_tasks()’

   - bpo-34969(96): gzip: Add -fast, -best on the gzip CLI, these
     parameters will be used for the fast compression method (quick) or
     the best method compress (slower, but smaller file).  Also, change
     the default compression level to 6 (tradeoff).

   - bpo-16965(97): The 2to3 ‘execfile’ fixer now opens the file with
     mode ‘'rb'’.  Patch by Zackery Spytz.

   - bpo-34966(98): *note pydoc: a3. now supports aliases not only to
     methods defined in the end class, but also to inherited methods.
     The docstring is not duplicated for aliases.

   - bpo-34926(99): *note mimetypes.MimeTypes.guess_type(): 193e. now
     accepts *note path-like object: ac2. in addition to url strings.
     Patch by Mayank Asthana.

   - bpo-23831(100): Add ‘moveto()’ method to the ‘tkinter.Canvas’
     widget.  Patch by Juliette Monsel.

   - bpo-34941(101): Methods ‘find()’, ‘findtext()’ and ‘findall()’ of
     the ‘Element’ class in the *note xml.etree.ElementTree: 10c. module
     are now able to find children which are instances of ‘Element’
     subclasses.

   - bpo-32680(102): *note smtplib.SMTP: 8d1. objects now always have a
     ‘sock’ attribute present

   - bpo-34769(103): Fix for async generators not finalizing when event
     loop is in debug mode and garbage collector runs in another thread.

   - bpo-34936(104): Fix ‘TclError’ in
     ‘tkinter.Spinbox.selection_element()’.  Patch by Juliette Monsel.

   - bpo-34829(105): Add methods ‘selection_from’, ‘selection_range’,
     ‘selection_present’ and ‘selection_to’ to the ‘tkinter.Spinbox’ for
     consistency with the ‘tkinter.Entry’ widget.  Patch by Juliette
     Monsel.

   - bpo-34911(106): Added 'secure_protocols' argument to
     'http.cookiejar.DefaultCookiePolicy' to allow for tweaking of
     protocols and also to add support by default for 'wss', the secure
     websocket protocol.

   - bpo-34922(107): Fixed integer overflow in the *note digest(): 193f.
     and *note hexdigest(): 1940. methods for the SHAKE algorithm in the
     *note hashlib: 5e. module.

   - bpo-34925(108): 25% speedup in argument parsing for the functions
     in the bisect module.

   - bpo-34900(109): Fixed *note unittest.TestCase.debug(): 1797. when
     used to call test methods with subtests.  Patch by Bruno Oliveira.

   - bpo-34844(110): logging.Formatter enhancement - Ensure styles and
     fmt matches in logging.Formatter - Added validate method in each
     format style class: StrFormatStyle, PercentStyle,
     StringTemplateStyle.  - This method is called in the constructor of
     logging.Formatter class - Also re-raise the KeyError in the format
     method of each style class, so it would a bit clear that it's an
     error with the invalid format fields.

   - bpo-34897(111): Adjust test.support.missing_compiler_executable
     check so that a nominal command name of "" is ignored.  Patch by
     Michael Felt.

   - bpo-34871(112): Fix inspect module polluted ‘sys.modules’ when
     parsing ‘__text_signature__’ of callable.

   - bpo-34898(113): Add ‘mtime’ argument to ‘gzip.compress’ for
     reproducible output.  Patch by Guo Ci Teo.

   - bpo-28441(114): On Cygwin and MinGW, ensure that ‘sys.executable’
     always includes the full filename in the path, including the ‘.exe’
     suffix (unless it is a symbolic link).

   - bpo-34866(115): Adding ‘max_num_fields’ to ‘cgi.FieldStorage’ to
     make DOS attacks harder by limiting the number of
     ‘MiniFieldStorage’ objects created by ‘FieldStorage’.

   - bpo-34711(116): http.server ensures it reports HTTPStatus.NOT_FOUND
     when the local path ends with "/" and is not a directory, even if
     the underlying OS (e.g.  AIX) accepts such paths as a valid file
     reference.  Patch by Michael Felt.

   - bpo-34872(117): Fix self-cancellation in C implementation of
     asyncio.Task

   - bpo-34849(118): Don't log waiting for ‘selector.select’ in asyncio
     loop iteration.  The waiting is pretty normal for any asyncio
     program, logging its time just adds a noise to logs without any
     useful information provided.

   - bpo-34022(119): The ‘SOURCE_DATE_EPOCH’ environment variable no
     longer overrides the value of the 'invalidation_mode' argument to
     *note py_compile.compile(): 9c9, and determines its default value
     instead.

   - bpo-34819(120): Use a monotonic clock to compute timeouts in
     ‘Executor.map()’ and ‘as_completed()’, in order to prevent timeouts
     from deviating when the system clock is adjusted.

   - bpo-34758(121): Add .wasm -> application/wasm to list of recognized
     file types and content type headers

   - bpo-34789(122): *note xml.sax.make_parser(): 1941. now accepts any
     iterable as its 'parser_list' argument.  Patch by Andrés Delfino.

   - bpo-34334(123): In ‘QueueHandler’, clear ‘exc_text’ from
     ‘LogRecord’ to prevent traceback from being written twice.

   - bpo-34687(124): On Windows, asyncio now uses ProactorEventLoop,
     instead of SelectorEventLoop, by default.

   - bpo-5950(125): Support reading zip files with archive comments in
     *note zipimport: 118.

   - bpo-32892(126): The parser now represents all constants as *note
     ast.Constant: 29a. instead of using specific constant AST types
     (‘Num’, ‘Str’, ‘Bytes’, ‘NameConstant’ and ‘Ellipsis’).  These
     classes are considered deprecated and will be removed in future
     Python versions.

   - bpo-34728(127): Add deprecation warning when ‘loop’ is used in
     methods: ‘asyncio.sleep’, ‘asyncio.wait’ and ‘asyncio.wait_for’.

   - bpo-34738(128): ZIP files created by ‘distutils’ will now include
     entries for directories.

   - bpo-34659(129): Add an optional 'initial' argument to
     itertools.accumulate().

   - bpo-29577(130): Support multiple mixin classes when creating Enums.

   - bpo-34670(131): Add SSLContext.post_handshake_auth and
     SSLSocket.verify_client_post_handshake for TLS 1.3's post handshake
     authentication feature.

   - bpo-32718(132): The Activate.ps1 script from venv works with
     PowerShell Core 6.1 and is now available under all operating
     systems.

   - bpo-31177(133): Fix bug that prevented using *note reset_mock: ca1.
     on mock instances with deleted attributes

   - bpo-34672(134): Add a workaround, so the ‘'Z'’ *note
     time.strftime(): 1181. specifier on the musl C library can work in
     some cases.

   - bpo-34666(135): Implement ‘asyncio.StreamWriter.awrite’ and
     ‘asyncio.StreamWriter.aclose()’ coroutines.  Methods are needed for
     providing a consistent stream API with control flow switched on by
     default.

   - bpo-6721(136): Acquire the logging module's commonly used internal
     locks while fork()ing to avoid deadlocks in the child process.

   - bpo-34658(137): Fix a rare interpreter unhandled exception state
     SystemError only seen when using subprocess with a preexec_fn while
     an after_parent handler has been registered with
     os.register_at_fork and the fork system call fails.

   - bpo-34652(138): Ensure *note os.lchmod(): 1ff. is never defined on
     Linux.

   - bpo-34638(139): Store a weak reference to stream reader to break
     strong references loop between reader and protocol.  It allows to
     detect and close the socket if the stream is deleted (garbage
     collected) without ‘close()’ call.

   - bpo-34536(140): ‘Enum._missing_’: raise ‘ValueError’ if None
     returned and ‘TypeError’ if non-member is returned.

   - bpo-34636(141): Speed up re scanning of many non-matching
     characters for s w and d within bytes objects.  (microoptimization)

   - bpo-24412(142): Add *note addModuleCleanup(): 9f0. and *note
     addClassCleanup(): 9f1. to unittest to support cleanups for
     ‘setUpModule()’ and *note setUpClass(): 9f2.  Patch by Lisa Roach.

   - bpo-34630(143): Don't log SSL certificate errors in asyncio code
     (connection error logging is skipped already).

   - bpo-32490(144): Prevent filename duplication in *note subprocess:
     c1. exception messages.  Patch by Zackery Spytz.

   - bpo-34363(145): dataclasses.asdict() and .astuple() now handle
     namedtuples correctly.

   - bpo-34625(146): Update vendorized expat library version to 2.2.6.

   - bpo-32270(147): The subprocess module no longer mistakenly closes
     redirected fds even when they were in pass_fds when outside of the
     default {0, 1, 2} set.

   - bpo-34622(148): Create a dedicated ‘asyncio.CancelledError’,
     ‘asyncio.InvalidStateError’ and ‘asyncio.TimeoutError’ exception
     classes.  Inherit them from corresponding exceptions from
     ‘concurrent.futures’ package.  Extract ‘asyncio’ exceptions into a
     separate file.

   - bpo-34610(149): Fixed iterator of
     ‘multiprocessing.managers.DictProxy’.

   - bpo-34421(150): Fix distutils logging for non-ASCII strings.  This
     caused installation issues on Windows.

   - bpo-34604(151): Fix possible mojibake in the error message of
     ‘pwd.getpwnam’ and ‘grp.getgrnam’ using string representation
     because of invisible characters or trailing whitespaces.  Patch by
     William Grzybowski.

   - bpo-30977(152): Make uuid.UUID use ‘__slots__’ to reduce its memory
     footprint.  Based on original patch by Wouter Bolsterlee.

   - bpo-34574(153): OrderedDict iterators are not exhausted during
     pickling anymore.  Patch by Sergey Fedoseev.

   - bpo-8110(154): Refactored *note subprocess: c1. to check for
     Windows-specific modules rather than ‘sys.platform == 'win32'’.

   - bpo-34530(155): ‘distutils.spawn.find_executable()’ now falls back
     on *note os.defpath: 1908. if the ‘PATH’ environment variable is
     not set.

   - bpo-34563(156): On Windows, fix multiprocessing.Connection for very
     large read: fix _winapi.PeekNamedPipe() and _winapi.ReadFile() for
     read larger than INT_MAX (usually ‘2**31-1’).

   - bpo-34558(157): Correct typo in Lib/ctypes/_aix.py

   - bpo-34282(158): Move ‘Enum._convert’ to ‘EnumMeta._convert_’ and
     fix enum members getting shadowed by parent attributes.

   - bpo-22872(159): When the queue is closed, *note ValueError: 1e7. is
     now raised by *note multiprocessing.Queue.put(): 1942. and *note
     multiprocessing.Queue.get(): 1943. instead of *note AssertionError:
     64e. and *note OSError: 350, respectively.  Patch by Zackery Spytz.

   - bpo-34515(160): Fix parsing non-ASCII identifiers in
     ‘lib2to3.pgen2.tokenize’ ( PEP 3131(161)).

   - bpo-13312(162): Avoids a possible integer underflow (undefined
     behavior) in the time module's year handling code when passed a
     very low negative year value.

   - bpo-34472(163): Improved compatibility for streamed files in *note
     zipfile: 117.  Previously an optional signature was not being
     written and certain ZIP applications were not supported.  Patch by
     Silas Sewell.

   - bpo-34454(164): Fix the .fromisoformat() methods of datetime types
     crashing when given unicode with non-UTF-8-encodable code points.
     Specifically, datetime.fromisoformat() now accepts surrogate
     unicode code points used as the separator.  Report and tests by
     Alexey Izbyshev, patch by Paul Ganssle.

   - bpo-6700(165): Fix inspect.getsourcelines for module level
     frames/tracebacks.  Patch by Vladimir Matveev.

   - bpo-34171(166): Running the *note trace: e6. module no longer
     creates the ‘trace.cover’ file.

   - bpo-34441(167): Fix crash when an ‘ABC’-derived class with invalid
     ‘__subclasses__’ is passed as the second argument to *note
     issubclass(): 765.  Patch by Alexey Izbyshev.

   - bpo-34427(168): Fix infinite loop in ‘a.extend(a)’ for
     ‘MutableSequence’ subclasses.

   - bpo-34412(169): Make *note signal.strsignal(): 1944. work on HP-UX.
     Patch by Michael Osipov.

   - bpo-20849(170): shutil.copytree now accepts a new ‘dirs_exist_ok’
     keyword argument.  Patch by Josh Bronson.

   - bpo-31715(171): Associate ‘.mjs’ file extension with
     ‘application/javascript’ MIME Type.

   - bpo-34384(172): *note os.readlink(): 8c5. now accepts *note
     path-like: ac2. and *note bytes: 1a5. objects on Windows.

   - bpo-22602(173): The UTF-7 decoder now raises *note
     UnicodeDecodeError: 9b7. for ill-formed sequences starting with "+"
     (as specified in RFC 2152).  Patch by Zackery Spytz.

   - bpo-2122(174): The *note mmap.flush(): a3b. method now returns
     ‘None’ on success, raises an exception on error under all
     platforms.

   - bpo-34341(175): Appending to the ZIP archive with the ZIP64
     extension no longer grows the size of extra fields of existing
     entries.

   - bpo-34333(176): Fix %-formatting in *note
     pathlib.PurePath.with_suffix(): 150b. when formatting an error
     message.

   - bpo-18540(177): The *note imaplib.IMAP4: 8a8. and *note
     imaplib.IMAP4_SSL: 8a9. classes now resolve to the local host IP
     correctly when the default value of 'host' parameter (‘''’) is
     used.

   - bpo-26502(178): Implement ‘traceback.FrameSummary.__len__()’ method
     to preserve compatibility with the old tuple API.

   - bpo-34318(179): *note assertRaises(): 4d1, *note
     assertRaisesRegex(): 4d3, *note assertWarns(): 10fd. and *note
     assertWarnsRegex(): 10fe. no longer success if the passed callable
     is None.  They no longer ignore unknown keyword arguments in the
     context manager mode.  A DeprecationWarning was raised in these
     cases since Python 3.5.

   - bpo-9372(180): Deprecate *note __getitem__(): 266. methods of *note
     xml.dom.pulldom.DOMEventStream: 6d9, *note
     wsgiref.util.FileWrapper: 6da. and *note fileinput.FileInput: 6db.

   - bpo-33613(181): Fix a race condition in
     ‘multiprocessing.semaphore_tracker’ when the tracker receives
     SIGINT before it can register signal handlers for ignoring it.

   - bpo-34248(182): Report filename in the exception raised when the
     database file cannot be opened by *note dbm.gnu.open(): 1945. and
     *note dbm.ndbm.open(): 1946. due to OS-related error.  Patch by
     Zsolt Cserna.

   - bpo-33089(183): Add math.dist() to compute the Euclidean distance
     between two points.

   - bpo-34246(184): *note smtplib.SMTP.send_message(): dfc. no longer
     modifies the content of the 'mail_options' argument.  Patch by
     Pablo S. Blum de Aguiar.

   - bpo-31047(185): Fix ‘ntpath.abspath’ for invalid paths on windows.
     Patch by Franz Woellert.

   - bpo-32321(186): Add pure Python fallback for functools.reduce.
     Patch by Robert Wright.

   - bpo-34270(187): The default asyncio task class now always has a
     name which can be get or set using two new methods (*note
     get_name(): 982. and *note set_name(): 981.) and is visible in the
     *note repr(): 7a1. output.  An initial name can also be set using
     the new ‘name’ keyword argument to *note asyncio.create_task():
     5a1. or the ‘create_task()’ method of the event loop.  If no
     initial name is set, the default Task implementation generates a
     name like ‘Task-1’ using a monotonic counter.

   - bpo-34263(188): asyncio's event loop will not pass timeouts longer
     than one day to epoll/select etc.

   - bpo-34035(189): Fix several AttributeError in zipfile seek()
     methods.  Patch by Mickaël Schoentgen.

   - bpo-32215(190): Fix performance regression in *note sqlite3: ba.
     when a DML statement appeared in a different line than the rest of
     the SQL query.

   - bpo-34075(191): Deprecate passing non-ThreadPoolExecutor instances
     to ‘AbstractEventLoop.set_default_executor()’.

   - bpo-34251(192): Restore ‘msilib.Win64’ to preserve backwards
     compatibility since it's already used by ‘distutils’' ‘bdist_msi’
     command.

   - bpo-19891(193): Ignore errors caused by missing / non-writable
     homedir while writing history during exit of an interactive
     session.  Patch by Anthony Sottile.

   - bpo-33089(194): Enhanced math.hypot() to support more than two
     dimensions.

   - bpo-34228(195): tracemalloc: PYTHONTRACEMALLOC=0 environment
     variable and -X tracemalloc=0 command line option are now allowed
     to disable explicitly tracemalloc at startup.

   - bpo-13041(196): Use *note shutil.get_terminal_size(): 109b. to
     calculate the terminal width correctly in the
     ‘argparse.HelpFormatter’ class.  Initial patch by Zbyszek
     Jędrzejewski-Szmek.

   - bpo-34213(197): Allow frozen dataclasses to have a field named
     "object".  Previously this conflicted with an internal use of
     "object".

   - bpo-34052(198): *note sqlite3.Connection.create_aggregate(): 28a,
     *note sqlite3.Connection.create_function(): 289, *note
     sqlite3.Connection.set_authorizer(): 28b, *note
     sqlite3.Connection.set_progress_handler(): 28c. methods raises
     TypeError when unhashable objects are passed as callable.  These
     methods now don't pass such objects to SQLite API. Previous
     behavior could lead to segfaults.  Patch by Sergey Fedoseev.

   - bpo-34197(199): Attributes 'skipinitialspace', 'doublequote' and
     'strict' of the 'dialect' attribute of the *note csv: 21. reader
     are now *note bool: 40e. instances instead of integers 0 or 1.

   - bpo-32788(200): Errors other than *note TypeError: 4dd. raised in
     methods ‘__adapt__()’ and ‘__conform__()’ in the *note sqlite3: ba.
     module are now propagated to the user.

   - bpo-21446(201): The ‘reload’ fixer now uses *note
     importlib.reload(): 4bd. instead of deprecated ‘imp.reload()’.

   - bpo-940286(202): pydoc's ‘Helper.showtopic()’ method now prints the
     cross references of a topic correctly.

   - bpo-34164(203): *note base64.b32decode(): fc8. could raise
     UnboundLocalError or OverflowError for incorrect padding.  Now it
     always raises ‘base64.Error’ in these cases.

   - bpo-33729(204): Fixed issues with arguments parsing in *note
     hashlib: 5e.

   - bpo-34097(205): ZipFile can zip files older than 1980-01-01 and
     newer than 2107-12-31 using a new ‘strict_timestamps’ parameter at
     the cost of setting the timestamp to the limit.

   - bpo-34108(206): Remove extraneous CR in 2to3 refactor.

   - bpo-34070(207): Make sure to only check if the handle is a tty,
     when opening a file with ‘buffering=-1’.

   - bpo-27494(208): Reverted bpo-27494(209).  2to3 rejects now a
     trailing comma in generator expressions.

   - bpo-33967(210): functools.singledispatch now raises TypeError
     instead of IndexError when no positional arguments are passed.

   - bpo-34041(211): Add the parameter 'deterministic' to the *note
     sqlite3.Connection.create_function(): 289. method.  Patch by Sergey
     Fedoseev.

   - bpo-34056(212): Ensure the loader shim created by ‘imp.load_module’
     always returns bytes from its ‘get_data()’ function.  This fixes
     using ‘imp.load_module’ with PEP 552(213) hash-based pycs.

   - bpo-34054(214): The multiprocessing module now uses the monotonic
     clock *note time.monotonic(): 238. instead of the system clock
     *note time.time(): 239. to implement timeout.

   - bpo-34043(215): Optimize tarfile uncompress performance about 15%
     when gzip is used.

   - bpo-34044(216): ‘subprocess.Popen’ now copies the 'startupinfo'
     argument to leave it unchanged: it will modify the copy, so that
     the same ‘STARTUPINFO’ object can be used multiple times.

   - bpo-34010(217): Fixed a performance regression for reading streams
     with tarfile.  The buffered read should use a list, instead of
     appending to a bytes object.

   - bpo-34019(218): webbrowser: Correct the arguments passed to Opera
     Browser when opening a new URL using the ‘webbrowser’ module.
     Patch by Bumsik Kim.

   - bpo-34003(219): csv.DictReader now creates dicts instead of
     OrderedDicts.  Patch by Michael Selik.

   - bpo-33978(220): Closed existing logging handlers before
     reconfiguration via fileConfig and dictConfig.  Patch by
     Karthikeyan Singaravelan.

   - bpo-14117(221): Make minor tweaks to turtledemo.  The 'wikipedia'
     example is now 'rosette', describing what it draws.  The 'penrose'
     print output is reduced.  The'1024' output of 'tree' is eliminated.

   - bpo-33974(222): Fixed passing lists and tuples of strings
     containing special characters ‘"’, ‘\’, ‘{’, ‘}’ and ‘\n’ as
     options to *note ttk: e2. widgets.

   - bpo-27500(223): Fix getaddrinfo to resolve IPv6 addresses
     correctly.

   - bpo-24567(224): Improve random.choices() to handle subnormal input
     weights that could occasionally trigger an IndexError.

   - bpo-33871(225): Fixed integer overflow in *note os.readv(): b02,
     *note os.writev(): b05, *note os.preadv(): b01. and *note
     os.pwritev(): b04. and in *note os.sendfile(): ab2. with 'headers'
     or 'trailers' arguments (on BSD-based OSes and macOS).

   - bpo-25007(226): Add *note copy.copy(): 4d8. and *note
     copy.deepcopy(): b12. support to zlib compressors and
     decompressors.  Patch by Zackery Spytz.

   - bpo-33929(227): multiprocessing: Fix a race condition in Popen of
     multiprocessing.popen_spawn_win32.  The child process now
     duplicates the read end of pipe instead of "stealing" it.
     Previously, the read end of pipe was "stolen" by the child process,
     but it leaked a handle if the child process had been terminated
     before it could steal the handle from the parent process.

   - bpo-33899(228): Tokenize module now implicitly emits a NEWLINE when
     provided with input that does not have a trailing new line.  This
     behavior now matches what the C tokenizer does internally.
     Contributed by Ammar Askar.

   - bpo-33897(229): Added a 'force' keyword argument to
     logging.basicConfig().

   - bpo-33695(230): *note shutil.copytree(): 9cd. uses *note
     os.scandir(): a02. function and all copy functions depending from
     it use cached *note os.stat(): 448. values.  The speedup for
     copying a directory with 8000 files is around +9% on Linux, +20% on
     Windows and + 30% on a Windows SMB share.  Also the number of *note
     os.stat(): 448. syscalls is reduced by 38% making *note
     shutil.copytree(): 9cd. especially faster on network filesystems.
     (Contributed by Giampaolo Rodola' in bpo-33695(231).)

   - bpo-33916(232): bz2 and lzma: When Decompressor.__init__() is
     called twice, free the old lock to not leak memory.

   - bpo-32568(233): Make select.epoll() and its documentation
     consistent regarding 'sizehint' and 'flags'.

   - bpo-33833(234): Fixed bug in asyncio where ProactorSocketTransport
     logs AssertionError if force closed during write.

   - bpo-33663(235): Convert content length to string before putting to
     header.

   - bpo-33721(236): *note os.path: 92. functions that return a boolean
     result like *note exists(): 9b2, *note lexists(): 9b3, *note
     isdir(): 9b4, *note isfile(): 9b5, *note islink(): 9b0, and *note
     ismount(): 9b6, and *note pathlib.Path: 20e. methods that return a
     boolean result like *note exists(): 9ba, *note is_dir(): 215, *note
     is_file(): 214, *note is_mount(): 9bb, *note is_symlink(): 9bc,
     *note is_block_device(): 9bd, *note is_char_device(): 9be, *note
     is_fifo(): 9bf, *note is_socket(): 9c0. now return ‘False’ instead
     of raising *note ValueError: 1e7. or its subclasses *note
     UnicodeEncodeError: 61d. and *note UnicodeDecodeError: 9b7. for
     paths that contain characters or bytes unrepresentable at the OS
     level.

   - bpo-26544(237): Fixed implementation of *note platform.libc_ver():
     1937.  It almost always returned version '2.9' for glibc.

   - bpo-33843(238): Remove deprecated ‘cgi.escape’, ‘cgi.parse_qs’ and
     ‘cgi.parse_qsl’.

   - bpo-33842(239): Remove ‘tarfile.filemode’ which is deprecated since
     Python 3.3.

   - bpo-30167(240): Prevent site.main() exception if PYTHONSTARTUP is
     set.  Patch by Steve Weber.

   - bpo-33805(241): Improve error message of dataclasses.replace() when
     an InitVar is not specified

   - bpo-33687(242): Fix the call to ‘os.chmod()’ for ‘uu.decode()’ if a
     mode is given or decoded.  Patch by Timo Furrer.

   - bpo-33812(243): Datetime instance d with non-None tzinfo, but with
     d.tzinfo.utcoffset(d) returning None is now treated as naive by the
     astimezone() method.

   - bpo-32108(244): In configparser, don't clear section when it is
     assigned to itself.

   - bpo-27397(245): Make email module properly handle invalid-length
     base64 strings.

   - bpo-33578(246): Implement multibyte encoder/decoder state methods

   - bpo-30805(247): Avoid race condition with debug logging

   - bpo-33476(248): Fix _header_value_parser.py when address group is
     missing final ';'.  Contributed by Enrique Perez-Terron

   - bpo-33694(249): asyncio: Fix a race condition causing data loss on
     pause_reading()/resume_reading() when using the ProactorEventLoop.

   - bpo-32493(250): Correct test for ‘uuid_enc_be’ availability in
     ‘configure.ac’.  Patch by Michael Felt.

   - bpo-33792(251): Add asyncio.WindowsSelectorEventLoopPolicy and
     asyncio.WindowsProactorEventLoopPolicy.

   - bpo-33274(252): W3C DOM Level 1 specifies return value of
     Element.removeAttributeNode() as "The Attr node that was removed."
     xml.dom.minidom now complies with this requirement.

   - bpo-33778(253): Update ‘unicodedata’'s database to Unicode version
     11.0.0.

   - bpo-33165(254): Added a stacklevel parameter to logging calls to
     allow use of wrapper/helper functions for logging APIs.

   - bpo-33770(255): improve base64 exception message for encoded inputs
     of invalid length

   - bpo-33769(256): asyncio/start_tls: Fix error message; cancel
     callbacks in case of an unhandled error; mark SSLTransport as
     closed if it is aborted.

   - bpo-33767(257): The concatenation (‘+’) and repetition (‘*’)
     sequence operations now raise *note TypeError: 4dd. instead of
     *note SystemError: 51b. when performed on *note mmap.mmap: 1f0.
     objects.  Patch by Zackery Spytz.

   - bpo-33734(258): asyncio/ssl: Fix AttributeError, increase default
     handshake timeout

   - bpo-31014(259): Fixed creating a controller for *note webbrowser:
     fd. when a user specifies a path to an entry in the BROWSER
     environment variable.  Based on patch by John Still.

   - bpo-2504(260): Add gettext.pgettext() and variants.

   - bpo-33197(261): Add description property for _ParameterKind

   - bpo-32751(262): When cancelling the task due to a timeout, *note
     asyncio.wait_for(): 5a4. will now wait until the cancellation is
     complete.

   - bpo-32684(263): Fix gather to propagate cancellation of itself even
     with return_exceptions.

   - bpo-33654(264): Support protocol type switching in
     SSLTransport.set_protocol().

   - bpo-33674(265): Pause the transport as early as possible to further
     reduce the risk of data_received() being called before
     connection_made().

   - bpo-33671(266): *note shutil.copyfile(): 9fc, *note shutil.copy():
     9fd, *note shutil.copy2(): 9fe, *note shutil.copytree(): 9cd. and
     *note shutil.move(): 9ff. use platform-specific fast-copy syscalls
     on Linux and macOS in order to copy the file more efficiently.  On
     Windows *note shutil.copyfile(): 9fc. uses a bigger default buffer
     size (1 MiB instead of 16 KiB) and a *note memoryview(): 40f.-based
     variant of *note shutil.copyfileobj(): a00. is used.  The speedup
     for copying a 512MiB file is about +26% on Linux, +50% on macOS and
     +40% on Windows.  Also, much less CPU cycles are consumed.
     (Contributed by Giampaolo Rodola' in bpo-25427(267).)

   - bpo-33674(268): Fix a race condition in
     SSLProtocol.connection_made() of asyncio.sslproto: start
     immediately the handshake instead of using call_soon().
     Previously, data_received() could be called before the handshake
     started, causing the handshake to hang or fail.

   - bpo-31647(269): Fixed bug where calling write_eof() on a
     _SelectorSocketTransport after it's already closed raises
     AttributeError.

   - bpo-32610(270): Make asyncio.all_tasks() return only pending tasks.

   - bpo-32410(271): Avoid blocking on file IO in sendfile fallback code

   - bpo-33469(272): Fix RuntimeError after closing loop that used
     run_in_executor

   - bpo-33672(273): Fix Task.__repr__ crash with Cython's bogus
     coroutines

   - bpo-33654(274): Fix transport.set_protocol() to support switching
     between asyncio.Protocol and asyncio.BufferedProtocol.  Fix
     loop.start_tls() to work with asyncio.BufferedProtocols.

   - bpo-33652(275): Pickles of type variables and subscripted generics
     are now future-proof and compatible with older Python versions.

   - bpo-32493(276): Fixed *note uuid.uuid1(): b4f. on FreeBSD.

   - bpo-33238(277): Add ‘InvalidStateError’ to *note
     concurrent.futures: 1a.  ‘Future.set_result’ and
     ‘Future.set_exception’ now raise ‘InvalidStateError’ if the futures
     are not pending or running.  Patch by Jason Haydaman.

   - bpo-33618(278): Finalize and document preliminary and experimental
     TLS 1.3 support with OpenSSL 1.1.1

   - bpo-33625(279): Release GIL on ‘grp.getgrnam’, ‘grp.getgrgid’,
     ‘pwd.getpwnam’ and ‘pwd.getpwuid’ if reentrant variants of these
     functions are available.  Patch by William Grzybowski.

   - bpo-33623(280): Fix possible SIGSGV when asyncio.Future is created
     in __del__

   - bpo-11874(281): Use a better regex when breaking usage into
     wrappable parts.  Avoids bogus assertion errors from custom metavar
     strings.

   - bpo-30877(282): Fixed a bug in the Python implementation of the
     JSON decoder that prevented the cache of parsed strings from
     clearing after finishing the decoding.  Based on patch by c-fos.

   - bpo-33604(283): Remove HMAC default to md5 marked for removal in
     3.8 (removal originally planned in 3.6, bump to 3.8 in PR 7062).

   - bpo-33582(284): Emit a deprecation warning for
     inspect.formatargspec

   - bpo-21145(285): Add ‘functools.cached_property’ decorator, for
     computed properties cached for the life of the instance.

   - bpo-33570(286): Change TLS 1.3 cipher suite settings for
     compatibility with OpenSSL 1.1.1-pre6 and newer.  OpenSSL 1.1.1
     will have TLS 1.3 ciphers enabled by default.

   - bpo-28556(287): Do not simplify arguments to ‘typing.Union’.  Now
     ‘Union[Manager, Employee]’ is not simplified to ‘Employee’ at
     runtime.  Such simplification previously caused several bugs and
     limited possibilities for introspection.

   - bpo-12486(288): *note tokenize.generate_tokens(): 482. is now
     documented as a public API to tokenize unicode strings.  It was
     previously present but undocumented.

   - bpo-33540(289): Add a new ‘block_on_close’ class attribute to
     ‘ForkingMixIn’ and ‘ThreadingMixIn’ classes of *note socketserver:
     b9.

   - bpo-33548(290): tempfile._candidate_tempdir_list should consider
     common TEMP locations

   - bpo-33109(291): argparse subparsers are once again not required by
     default, reverting the change in behavior introduced by
     bpo-26510(292) in 3.7.0a2.

   - bpo-33541(293): Remove unused private method
     ‘_strptime.LocaleTime.__pad’ (a.k.a.  ‘_LocaleTime__pad’).

   - bpo-33536(294): dataclasses.make_dataclass now checks for invalid
     field names and duplicate fields.  Also, added a check for invalid
     field specifications.

   - bpo-33542(295): Prevent ‘uuid.get_node’ from using a DUID instead
     of a MAC on Windows.  Patch by Zvi Effron

   - bpo-26819(296): Fix race condition with
     ‘ReadTransport.resume_reading’ in Windows proactor event loop.

   - Fix failure in ‘typing.get_type_hints()’ when ClassVar was provided
     as a string forward reference.

   - bpo-33516(297): *note unittest.mock.MagicMock: e33. now supports
     the ‘__round__’ magic method.

   - bpo-28612(298): Added support for Site Maps to urllib's
     ‘RobotFileParser’ as *note RobotFileParser.site_maps(): 1947.
     Patch by Lady Red, based on patch by Peter Wirtz.

   - bpo-28167(299): Remove platform.linux_distribution, which was
     deprecated since 3.5.

   - bpo-33504(300): Switch the default dictionary implementation for
     *note configparser: 1b. from *note collections.OrderedDict: 57f. to
     the standard *note dict: 23b. type.

   - bpo-33505(301): Optimize asyncio.ensure_future() by reordering if
     checks: 1.17x faster.

   - bpo-33497(302): Add errors param to cgi.parse_multipart and make an
     encoding in FieldStorage use the given errors (needed for Twisted).
     Patch by Amber Brown.

   - bpo-29235(303): The ‘cProfile.Profile’ class can now be used as a
     context manager.  Patch by Scott Sanderson.

   - bpo-33495(304): Change dataclasses.Fields repr to use the repr of
     each of its members, instead of str.  This makes it more clear what
     each field actually represents.  This is especially true for the
     'type' member.

   - bpo-26103(305): Correct ‘inspect.isdatadescriptor’ to look for
     ‘__set__’ or ‘__delete__’.  Patch by Aaron Hall.

   - bpo-29209(306): Removed the ‘doctype()’ method and the 'html'
     parameter of the constructor of *note XMLParser: 9f7.  The
     ‘doctype()’ method defined in a subclass will no longer be called.
     Deprecated methods ‘getchildren()’ and ‘getiterator()’ in the *note
     ElementTree: 10c. module emit now a *note DeprecationWarning: 18b.
     instead of *note PendingDeprecationWarning: 86d.

   - bpo-33453(307): Fix dataclasses to work if using literal string
     type annotations or if using PEP 563 "Postponed Evaluation of
     Annotations".  Only specific string prefixes are detected for both
     ClassVar ("ClassVar" and "typing.ClassVar") and InitVar ("InitVar"
     and "dataclasses.InitVar").

   - bpo-28556(308): Minor fixes in typing module: add annotations to
     ‘NamedTuple.__new__’, pass ‘*args’ and ‘**kwds’ in
     ‘Generic.__new__’.  Original PRs by Paulius Šarka and Chad
     Dombrova.

   - bpo-33365(309): Print the header values besides the header keys
     instead just the header keys if 'debuglevel' is set to >0 in *note
     http.client: 65.  Patch by Marco Strigl.

   - bpo-20087(310): Updated alias mapping with glibc 2.27 supported
     locales.

   - bpo-33422(311): Fix trailing quotation marks getting deleted when
     looking up byte/string literals on pydoc.  Patch by Andrés Delfino.

   - bpo-28167(312): The function ‘platform.linux_distribution’ and
     ‘platform.dist’ now trigger a ‘DeprecationWarning’ and have been
     marked for removal in Python 3.8

   - bpo-33281(313): Fix ctypes.util.find_library regression on macOS.

   - bpo-33311(314): Text and html output generated by cgitb does not
     display parentheses if the current call is done directly in the
     module.  Patch by Stéphane Blondon.

   - bpo-27300(315): The file classes in 'tempfile' now accept an
     'errors' parameter that complements the already existing
     'encoding'.  Patch by Stephan Hohe.

   - bpo-32933(316): *note unittest.mock.mock_open(): 1606. now supports
     iteration over the file contents.  Patch by Tony Flury.

   - bpo-33217(317): Raise *note TypeError: 4dd. when looking up
     non-Enum objects in Enum classes and Enum members.

   - bpo-33197(318): Update error message when constructing invalid
     inspect.Parameters Patch by Donghee Na.

   - bpo-33383(319): Fixed crash in the get() method of the *note
     dbm.ndbm: 2c. database object when it is called with a single
     argument.

   - bpo-33375(320): The warnings module now finds the Python file
     associated with a warning from the code object, rather than the
     frame's global namespace.  This is consistent with how tracebacks
     and pdb find filenames, and should work better for dynamically
     executed code.

   - bpo-33336(321): ‘imaplib’ now allows ‘MOVE’ command in
     ‘IMAP4.uid()’ (RFC 6851: IMAP MOVE Extension) and potentially as a
     name of supported method of ‘IMAP4’ object.

   - bpo-32455(322): Added 'jump' parameter to *note dis.stack_effect():
     ed5.

   - bpo-27485(323): Rename and deprecate undocumented functions in
     *note urllib.parse(): f3.

   - bpo-33332(324): Add ‘signal.valid_signals()’ to expose the POSIX
     sigfillset() functionality.

   - bpo-33251(325): ‘ConfigParser.items()’ was fixed so that key-value
     pairs passed in via *note vars(): 1948. are not included in the
     resulting output.

   - bpo-33329(326): Fix multiprocessing regression on newer glibcs

   - bpo-33334(327): *note dis.stack_effect(): ed5. now supports all
     defined opcodes including NOP and EXTENDED_ARG.

   - bpo-991266(328): Fix quoting of the ‘Comment’ attribute of *note
     http.cookies.SimpleCookie: 1949.

   - bpo-33131(329): Upgrade bundled version of pip to 10.0.1.

   - bpo-33308(330): Fixed a crash in the ‘parser’ module when
     converting an ST object to a tree of tuples or lists with
     ‘line_info=False’ and ‘col_info=True’.

   - bpo-23403(331): lib2to3 now uses pickle protocol 4 for pre-computed
     grammars.

   - bpo-33266(332): lib2to3 now recognizes ‘rf'...'’ strings.

   - bpo-11594(333): Ensure line-endings are respected when using
     lib2to3.

   - bpo-33254(334): Have *note importlib.resources.contents(): 1d7. and
     *note importlib.abc.ResourceReader.contents(): 194a. return an
     *note iterable: 11bf. instead of an *note iterator: 192.

   - bpo-33265(335): ‘contextlib.ExitStack’ and
     ‘contextlib.AsyncExitStack’ now use a method instead of a wrapper
     function for exit callbacks.

   - bpo-33263(336): Fix FD leak in ‘_SelectorSocketTransport’ Patch by
     Vlad Starostin.

   - bpo-33256(337): Fix display of ‘<module>’ call in the html produced
     by ‘cgitb.html()’.  Patch by Stéphane Blondon.

   - bpo-33144(338): ‘random.Random()’ and its subclassing mechanism got
     optimized to check only once at class/subclass instantiation time
     whether its ‘getrandbits()’ method can be relied on by other
     methods, including ‘randrange()’, for the generation of arbitrarily
     large random integers.  Patch by Wolfgang Maier.

   - bpo-33185(339): Fixed regression when running pydoc with the *note
     -m: 585. switch.  (The regression was introduced in 3.7.0b3 by the
     resolution of bpo-33053(340))

     This fix also changed pydoc to add ‘os.getcwd()’ to *note sys.path:
     37f. when necessary, rather than adding ‘"."’.

   - bpo-29613(341): Added support for the ‘SameSite’ cookie flag to the
     ‘http.cookies’ module.

   - bpo-33169(342): Delete entries of ‘None’ in *note
     sys.path_importer_cache: 588. when
     ‘importlib.machinery.invalidate_caches()’ is called.

   - bpo-33203(343): ‘random.Random.choice()’ now raises ‘IndexError’
     for empty sequences consistently even when called from subclasses
     without a ‘getrandbits()’ implementation.

   - bpo-33224(344): Update difflib.mdiff() for PEP 479(345).  Convert
     an uncaught StopIteration in a generator into a return-statement.

   - bpo-33209(346): End framing at the end of C implementation of *note
     pickle.Pickler.dump(): 194b.

   - bpo-32861(347): The urllib.robotparser's ‘__str__’ representation
     now includes wildcard entries and the "Crawl-delay" and
     "Request-rate" fields.  Also removes extra newlines that were being
     appended to the end of the string.  Patch by Michael Lazar.

   - bpo-23403(348): ‘DEFAULT_PROTOCOL’ in *note pickle: 95. was bumped
     to 4.  Protocol 4 is described in PEP 3154(349) and available since
     Python 3.4.  It offers better performance and smaller size compared
     to protocol 3 introduced in Python 3.0.

   - bpo-20104(350): Improved error handling and fixed a reference leak
     in *note os.posix_spawn(): 205.

   - bpo-33106(351): Deleting a key from a read-only dbm database raises
     module specific error instead of KeyError.

   - bpo-33175(352): In dataclasses, Field.__set_name__ now looks up the
     __set_name__ special method on the class, not the instance, of the
     default value.

   - bpo-32380(353): Create functools.singledispatchmethod to support
     generic single dispatch on descriptors and methods.

   - bpo-33141(354): Have Field objects pass through __set_name__ to
     their default values, if they have their own __set_name__.

   - bpo-33096(355): Allow ttk.Treeview.insert to insert iid that has a
     false boolean value.  Note iid=0 and iid=False would be same.
     Patch by Garvit Khatri.

   - bpo-32873(356): Treat type variables and special typing forms as
     immutable by copy and pickle.  This fixes several minor issues and
     inconsistencies, and improves backwards compatibility with Python
     3.6.

   - bpo-33134(357): When computing dataclass's __hash__, use the lookup
     table to contain the function which returns the __hash__ value.
     This is an improvement over looking up a string, and then testing
     that string to see what to do.

   - bpo-33127(358): The ssl module now compiles with LibreSSL 2.7.1.

   - bpo-32505(359): Raise TypeError if a member variable of a dataclass
     is of type Field, but doesn't have a type annotation.

   - bpo-33078(360): Fix the failure on OSX caused by the tests relying
     on sem_getvalue

   - bpo-33116(361): Add 'Field' to dataclasses.__all__.

   - bpo-32896(362): Fix an error where subclassing a dataclass with a
     field that uses a default_factory would generate an incorrect
     class.

   - bpo-33100(363): Dataclasses: If a field has a default value that's
     a MemberDescriptorType, then it's from that field being in
     __slots__, not an actual default value.

   - bpo-32953(364): If a non-dataclass inherits from a frozen
     dataclass, allow attributes to be added to the derived class.  Only
     attributes from the frozen dataclass cannot be assigned to.
     Require all dataclasses in a hierarchy to be either all frozen or
     all non-frozen.

   - bpo-33097(365): Raise RuntimeError when ‘executor.submit’ is called
     during interpreter shutdown.

   - bpo-32968(366): Modulo and floor division involving Fraction and
     float should return float.

   - bpo-33061(367): Add missing ‘NoReturn’ to ‘__all__’ in typing.py

   - bpo-33078(368): Fix the size handling in multiprocessing.Queue when
     a pickling error occurs.

   - bpo-33064(369): lib2to3 now properly supports trailing commas after
     ‘*args’ and ‘**kwargs’ in function signatures.

   - bpo-33056(370): FIX properly close leaking fds in
     concurrent.futures.ProcessPoolExecutor.

   - bpo-33021(371): Release the GIL during fstat() calls, avoiding hang
     of all threads when calling mmap.mmap(), os.urandom(), and
     random.seed().  Patch by Nir Soffer.

   - bpo-31804(372): Avoid failing in multiprocessing.Process if the
     standard streams are closed or None at exit.

   - bpo-33034(373): Providing an explicit error message when casting
     the port property to anything that is not an integer value using
     ‘urlparse()’ and ‘urlsplit()’.  Patch by Matt Eaton.

   - bpo-30249(374): Improve struct.unpack_from() exception messages for
     problems with the buffer size and offset.

   - bpo-33037(375): Skip sending/receiving data after SSL transport
     closing.

   - bpo-27683(376): Fix a regression in *note ipaddress: 74. that
     result of ‘hosts()’ is empty when the network is constructed by a
     tuple containing an integer mask and only 1 bit left for addresses.

   - bpo-22674(377): Add the strsignal() function in the signal module
     that returns the system description of the given signal, as
     returned by strsignal(3).

   - bpo-32999(378): Fix C implementation of ‘ABC.__subclasscheck__(cls,
     subclass)’ crashed when ‘subclass’ is not a type object.

   - bpo-33009(379): Fix inspect.signature() for single-parameter
     partialmethods.

   - bpo-32969(380): Expose several missing constants in zlib and fix
     corresponding documentation.

   - bpo-32056(381): Improved exceptions raised for invalid number of
     channels and sample width when read an audio file in modules
     ‘aifc’, *note wave: fb. and ‘sunau’.

   - bpo-32970(382): Improved disassembly of the MAKE_FUNCTION
     instruction.

   - bpo-32844(383): Fix wrong redirection of a low descriptor (0 or 1)
     to stderr in subprocess if another low descriptor is closed.

   - bpo-32960(384): For dataclasses, disallow inheriting frozen from
     non-frozen classes, and also disallow inheriting non-frozen from
     frozen classes.  This restriction will be relaxed at a future date.

   - bpo-32713(385): Fixed tarfile.itn handling of out-of-bounds float
     values.  Patch by Joffrey Fuhrer.

   - bpo-32257(386): The ssl module now contains OP_NO_RENEGOTIATION
     constant, available with OpenSSL 1.1.0h or 1.1.1.

   - bpo-32951(387): Direct instantiation of SSLSocket and SSLObject
     objects is now prohibited.  The constructors were never documented,
     tested, or designed as public constructors.  Users were suppose to
     use ssl.wrap_socket() or SSLContext.

   - bpo-32929(388): Remove the tri-state parameter "hash", and add the
     boolean "unsafe_hash".  If unsafe_hash is True, add a __hash__
     function, but if a __hash__ exists, raise TypeError.  If
     unsafe_hash is False, add a __hash__ based on the values of eq= and
     frozen=.  The unsafe_hash=False behavior is the same as the old
     hash=None behavior.  unsafe_hash=False is the default, just as
     hash=None used to be.

   - bpo-32947(389): Add OP_ENABLE_MIDDLEBOX_COMPAT and test workaround
     for TLSv1.3 for future compatibility with OpenSSL 1.1.1.

   - bpo-32146(390): Document the interaction between frozen executables
     and the spawn and forkserver start methods in multiprocessing.

   - bpo-30622(391): The ssl module now detects missing NPN support in
     LibreSSL.

   - bpo-32922(392): dbm.open() now encodes filename with the filesystem
     encoding rather than default encoding.

   - bpo-32759(393): Free unused arenas in multiprocessing.heap.

   - bpo-32859(394): In ‘os.dup2’, don't check every call whether the
     ‘dup3’ syscall exists or not.

   - bpo-32556(395): nt._getfinalpathname, nt._getvolumepathname and
     nt._getdiskusage now correctly convert from bytes.

   - bpo-21060(396): Rewrite confusing message from setup.py upload from
     "No dist file created in earlier command" to the more helpful "Must
     create and upload files in one command".

   - bpo-32857(397): In *note tkinter: d9, ‘after_cancel(None)’ now
     raises a *note ValueError: 1e7. instead of canceling the first
     scheduled function.  Patch by Cheryl Sabella.

   - bpo-32852(398): Make sure sys.argv remains as a list when running
     trace.

   - bpo-31333(399): ‘_abc’ module is added.  It is a speedup module
     with C implementations for various functions and methods in ‘abc’.
     Creating an ABC subclass and calling ‘isinstance’ or ‘issubclass’
     with an ABC subclass are up to 1.5x faster.  In addition, this
     makes Python start-up up to 10% faster.

     Note that the new implementation hides internal registry and
     caches, previously accessible via private attributes
     ‘_abc_registry’, ‘_abc_cache’, and ‘_abc_negative_cache’.  There
     are three debugging helper methods that can be used instead
     ‘_dump_registry’, ‘_abc_registry_clear’, and ‘_abc_caches_clear’.

   - bpo-32841(400): Fixed ‘asyncio.Condition’ issue which silently
     ignored cancellation after notifying and cancelling a conditional
     lock.  Patch by Bar Harel.

   - bpo-32819(401): ssl.match_hostname() has been simplified and no
     longer depends on re and ipaddress module for wildcard and IP
     addresses.  Error reporting for invalid wildcards has been
     improved.

   - bpo-19675(402): ‘multiprocessing.Pool’ no longer leaks processes if
     its initialization fails.

   - bpo-32394(403): socket: Remove
     TCP_FASTOPEN,TCP_KEEPCNT,TCP_KEEPIDLE,TCP_KEEPINTVL flags on older
     version Windows during run-time.

   - bpo-31787(404): Fixed refleaks of ‘__init__()’ methods in various
     modules.  (Contributed by Oren Milman)

   - bpo-30157(405): Fixed guessing quote and delimiter in
     csv.Sniffer.sniff() when only the last field is quoted.  Patch by
     Jake Davis.

   - bpo-30688(406): Added support of ‘\N{name}’ escapes in regular
     expressions.  Based on patch by Jonathan Eunice.

   - bpo-32792(407): collections.ChainMap() preserves the order of the
     underlying mappings.

   - bpo-32775(408): *note fnmatch.translate(): 194c. no longer produces
     patterns which contain set operations.  Sets starting with '[' or
     containing '-', '&&', '~~' or '||' will be interpreted differently
     in regular expressions in future versions.  Currently they emit
     warnings.  fnmatch.translate() now avoids producing patterns
     containing such sets by accident.

   - bpo-32622(409): Implement native fast sendfile for Windows proactor
     event loop.

   - bpo-32777(410): Fix a rare but potential pre-exec child process
     deadlock in subprocess on POSIX systems when marking file
     descriptors inheritable on exec in the child process.  This bug
     appears to have been introduced in 3.4.

   - bpo-32647(411): The ctypes module used to depend on indirect
     linking for dlopen.  The shared extension is now explicitly linked
     against libdl on platforms with dl.

   - bpo-32749(412): A *note dbm.dumb: 2a. database opened with flags
     'r' is now read-only.  *note dbm.dumb.open(): a39. with flags 'r'
     and 'w' no longer creates a database if it does not exist.

   - bpo-32741(413): Implement ‘asyncio.TimerHandle.when()’ method.

   - bpo-32691(414): Use mod_spec.parent when running modules with pdb

   - bpo-32734(415): Fixed ‘asyncio.Lock()’ safety issue which allowed
     acquiring and locking the same lock multiple times, without it
     being free.  Patch by Bar Harel.

   - bpo-32727(416): Do not include name field in SMTP envelope from
     address.  Patch by Stéphane Wirtel

   - bpo-31453(417): Add TLSVersion constants and
     SSLContext.maximum_version / minimum_version attributes.  The new
     API wraps OpenSSL 1.1
     ‘https://web.archive.org/web/20180309043602/https://www.openssl.org/docs/man1.1.0/ssl/SSL_CTX_set_min_proto_version.html’
     feature.

   - bpo-24334(418): Internal implementation details of ssl module were
     cleaned up.  The SSLSocket has one less layer of indirection.
     Owner and session information are now handled by the SSLSocket and
     SSLObject constructor.  Channel binding implementation has been
     simplified.

   - bpo-31848(419): Fix the error handling in Aifc_read.initfp() when
     the SSND chunk is not found.  Patch by Zackery Spytz.

   - bpo-32585(420): Add Ttk spinbox widget to *note tkinter.ttk: e2.
     Patch by Alan D Moore.

   - bpo-32512(421): *note profile: 9d. CLI accepts ‘-m module_name’ as
     an alternative to script path.

   - bpo-8525(422): help() on a type now displays builtin subclasses.
     This is intended primarily to help with notification of more
     specific exception subclasses.

     Patch by Sanyam Khurana.

   - bpo-31639(423): http.server now exposes a ThreadingHTTPServer class
     and uses it when the module is run with ‘-m’ to cope with web
     browsers pre-opening sockets.

   - bpo-29877(424): compileall: import ProcessPoolExecutor only when
     needed, preventing hangs on low resource platforms

   - bpo-32221(425): Various functions returning tuple containing IPv6
     addresses now omit ‘%scope’ part since the same information is
     already encoded in 'scopeid' tuple item.  Especially this speeds up
     ‘socket.recvfrom()’ when it receives multicast packet since useless
     resolving of network interface name is omitted.

   - bpo-32147(426): *note binascii.unhexlify(): 194d. is now up to 2
     times faster.  Patch by Sergey Fedoseev.

   - bpo-30693(427): The TarFile class now recurses directories in a
     reproducible way.

   - bpo-30693(428): The ZipFile class now recurses directories in a
     reproducible way.

   - bpo-31680(429): Added *note curses.ncurses_version: 98b.

   - bpo-31908(430): Fix output of cover files for ‘trace’ module
     command-line tool.  Previously emitted cover files only when
     ‘--missing’ option was used.  Patch by Michael Selik.

   - bpo-31608(431): Raise a ‘TypeError’ instead of crashing if a
     ‘collections.deque’ subclass returns a non-deque from ‘__new__’.
     Patch by Oren Milman.

   - bpo-31425(432): Add support for sockets of the AF_QIPCRTR address
     family, supported by the Linux kernel.  This is used to communicate
     with services, such as GPS or radio, running on Qualcomm devices.
     Patch by Bjorn Andersson.

   - bpo-22005(433): Implemented unpickling instances of *note datetime:
     1b0, *note date: 1b1. and *note time: 1b2. pickled by Python 2.
     ‘encoding='latin1'’ should be used for successful decoding.

   - bpo-27645(434): *note sqlite3.Connection: 22a. now exposes a *note
     backup: b1e. method, if the underlying SQLite library is at version
     3.6.11 or higher.  Patch by Lele Gaifax.

   - bpo-16865(435): Support arrays >=2GiB in *note ctypes: 22.  Patch
     by Segev Finer.

   - bpo-31508(436): Removed support of arguments in
     ‘tkinter.ttk.Treeview.selection’.  It was deprecated in 3.6.  Use
     specialized methods like ‘selection_set’ for changing the
     selection.

   - bpo-29456(437): Fix bugs in hangul normalization: u1176, u11a7 and
     u11c3

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35845

   (2) https://bugs.python.org/issue?@action=redirect&bpo=35864

   (3) https://bugs.python.org/issue?@action=redirect&bpo=35537

   (4) https://bugs.python.org/issue?@action=redirect&bpo=35847

   (5) https://bugs.python.org/issue?@action=redirect&bpo=35813

   (6) https://bugs.python.org/issue?@action=redirect&bpo=35780

   (7) https://bugs.python.org/issue?@action=redirect&bpo=35537

   (8) https://bugs.python.org/issue?@action=redirect&bpo=23846

   (9) https://bugs.python.org/issue?@action=redirect&bpo=34323

   (10) https://bugs.python.org/issue?@action=redirect&bpo=35674

   (11) https://bugs.python.org/issue?@action=redirect&bpo=35733

   (12) https://bugs.python.org/issue?@action=redirect&bpo=35726

   (13) https://bugs.python.org/issue?@action=redirect&bpo=35719

   (14) https://bugs.python.org/issue?@action=redirect&bpo=35717

   (15) https://bugs.python.org/issue?@action=redirect&bpo=35699

   (16) https://bugs.python.org/issue?@action=redirect&bpo=32710

   (17) https://bugs.python.org/issue?@action=redirect&bpo=35702

   (18) https://bugs.python.org/issue?@action=redirect&bpo=32710

   (19) https://bugs.python.org/issue?@action=redirect&bpo=35682

   (20) https://bugs.python.org/issue?@action=redirect&bpo=35283

   (21) https://bugs.python.org/issue?@action=redirect&bpo=35664

   (22) https://bugs.python.org/issue?@action=redirect&bpo=35643

   (23) https://bugs.python.org/issue?@action=redirect&bpo=35619

   (24) https://bugs.python.org/issue?@action=redirect&bpo=28503

   (25) https://bugs.python.org/issue?@action=redirect&bpo=35614

   (26) https://bugs.python.org/issue?@action=redirect&bpo=35568

   (27) https://bugs.python.org/issue?@action=redirect&bpo=35588

   (28) https://bugs.python.org/issue?@action=redirect&bpo=35585

   (29) https://bugs.python.org/issue?@action=redirect&bpo=30561

   (30) https://bugs.python.org/issue?@action=redirect&bpo=35537

   (31) https://bugs.python.org/issue?@action=redirect&bpo=35526

   (32) https://bugs.python.org/issue?@action=redirect&bpo=35523

   (33) https://bugs.python.org/issue?@action=redirect&bpo=31784

   (34) https://bugs.python.org/issue?@action=redirect&bpo=35513

   (35) https://bugs.python.org/issue?@action=redirect&bpo=35502

   (36) https://bugs.python.org/issue?@action=redirect&bpo=35348

   (37) https://bugs.python.org/issue?@action=redirect&bpo=35491

   (38) https://bugs.python.org/issue?@action=redirect&bpo=35477

   (39) https://bugs.python.org/issue?@action=redirect&bpo=31446

   (40) https://bugs.python.org/issue?@action=redirect&bpo=35471

   (41) https://bugs.python.org/issue?@action=redirect&bpo=23057

   (42) https://bugs.python.org/issue?@action=redirect&bpo=35052

   (43) https://bugs.python.org/issue?@action=redirect&bpo=20239

   (44) https://bugs.python.org/issue?@action=redirect&bpo=17185

   (45) https://bugs.python.org/issue?@action=redirect&bpo=35445

   (46) https://bugs.python.org/issue?@action=redirect&bpo=35415

   (47) https://bugs.python.org/issue?@action=redirect&bpo=35424

   (48) https://bugs.python.org/issue?@action=redirect&bpo=35330

   (49) https://bugs.python.org/issue?@action=redirect&bpo=35346

   (50) https://bugs.python.org/issue?@action=redirect&bpo=10496

   (51) https://bugs.python.org/issue?@action=redirect&bpo=10496

   (52) https://bugs.python.org/issue?@action=redirect&bpo=35389

   (53) https://bugs.python.org/issue?@action=redirect&bpo=35394

   (54) https://bugs.python.org/issue?@action=redirect&bpo=35310

   (55) https://bugs.python.org/issue?@action=redirect&bpo=35380

   (56) https://bugs.python.org/issue?@action=redirect&bpo=35341

   (57) https://bugs.python.org/issue?@action=redirect&bpo=35371

   (58) https://bugs.python.org/issue?@action=redirect&bpo=35346

   (59) https://bugs.python.org/issue?@action=redirect&bpo=35066

   (60) https://bugs.python.org/issue?@action=redirect&bpo=35345

   (61) https://bugs.python.org/issue?@action=redirect&bpo=35344

   (62) https://bugs.python.org/issue?@action=redirect&bpo=35312

   (63) https://bugs.python.org/issue?@action=redirect&bpo=35308

   (64) https://bugs.python.org/issue?@action=redirect&bpo=24746

   (65) https://bugs.python.org/issue?@action=redirect&bpo=28604

   (66) https://bugs.python.org/issue?@action=redirect&bpo=35277

   (67) https://bugs.python.org/issue?@action=redirect&bpo=24209

   (68) https://bugs.python.org/issue?@action=redirect&bpo=35226

   (69) https://bugs.python.org/issue?@action=redirect&bpo=29564

   (70) https://bugs.python.org/issue?@action=redirect&bpo=35189

   (71) https://bugs.python.org/issue?@action=redirect&bpo=30064

   (72) https://bugs.python.org/issue?@action=redirect&bpo=35186

   (73) https://bugs.python.org/issue?@action=redirect&bpo=35152

   (74) https://bugs.python.org/issue?@action=redirect&bpo=35062

   (75) https://bugs.python.org/issue?@action=redirect&bpo=35065

   (76) https://bugs.python.org/issue?@action=redirect&bpo=34160

   (77) https://bugs.python.org/issue?@action=redirect&bpo=35079

   (78) https://bugs.python.org/issue?@action=redirect&bpo=33710

   (79) https://bugs.python.org/issue?@action=redirect&bpo=35017

   (80) https://bugs.python.org/issue?@action=redirect&bpo=35024

   (81) https://bugs.python.org/issue?@action=redirect&bpo=35047

   (82) https://bugs.python.org/issue?@action=redirect&bpo=31047

   (83) https://bugs.python.org/issue?@action=redirect&bpo=35053

   (84) https://bugs.python.org/issue?@action=redirect&bpo=31553

   (85) https://bugs.python.org/issue?@action=redirect&bpo=34794

   (86) https://bugs.python.org/issue?@action=redirect&bpo=34909

   (87) https://bugs.python.org/issue?@action=redirect&bpo=35022

   (88) https://bugs.python.org/issue?@action=redirect&bpo=35008

   (89) https://bugs.python.org/issue?@action=redirect&bpo=23420

   (90) https://bugs.python.org/issue?@action=redirect&bpo=33947

   (91) https://bugs.python.org/issue?@action=redirect&bpo=34890

   (92) https://bugs.python.org/issue?@action=redirect&bpo=34521

   (93) https://datatracker.ietf.org/doc/html/rfc3542.html

   (94) https://bugs.python.org/issue?@action=redirect&bpo=31522

   (95) https://bugs.python.org/issue?@action=redirect&bpo=34970

   (96) https://bugs.python.org/issue?@action=redirect&bpo=34969

   (97) https://bugs.python.org/issue?@action=redirect&bpo=16965

   (98) https://bugs.python.org/issue?@action=redirect&bpo=34966

   (99) https://bugs.python.org/issue?@action=redirect&bpo=34926

   (100) https://bugs.python.org/issue?@action=redirect&bpo=23831

   (101) https://bugs.python.org/issue?@action=redirect&bpo=34941

   (102) https://bugs.python.org/issue?@action=redirect&bpo=32680

   (103) https://bugs.python.org/issue?@action=redirect&bpo=34769

   (104) https://bugs.python.org/issue?@action=redirect&bpo=34936

   (105) https://bugs.python.org/issue?@action=redirect&bpo=34829

   (106) https://bugs.python.org/issue?@action=redirect&bpo=34911

   (107) https://bugs.python.org/issue?@action=redirect&bpo=34922

   (108) https://bugs.python.org/issue?@action=redirect&bpo=34925

   (109) https://bugs.python.org/issue?@action=redirect&bpo=34900

   (110) https://bugs.python.org/issue?@action=redirect&bpo=34844

   (111) https://bugs.python.org/issue?@action=redirect&bpo=34897

   (112) https://bugs.python.org/issue?@action=redirect&bpo=34871

   (113) https://bugs.python.org/issue?@action=redirect&bpo=34898

   (114) https://bugs.python.org/issue?@action=redirect&bpo=28441

   (115) https://bugs.python.org/issue?@action=redirect&bpo=34866

   (116) https://bugs.python.org/issue?@action=redirect&bpo=34711

   (117) https://bugs.python.org/issue?@action=redirect&bpo=34872

   (118) https://bugs.python.org/issue?@action=redirect&bpo=34849

   (119) https://bugs.python.org/issue?@action=redirect&bpo=34022

   (120) https://bugs.python.org/issue?@action=redirect&bpo=34819

   (121) https://bugs.python.org/issue?@action=redirect&bpo=34758

   (122) https://bugs.python.org/issue?@action=redirect&bpo=34789

   (123) https://bugs.python.org/issue?@action=redirect&bpo=34334

   (124) https://bugs.python.org/issue?@action=redirect&bpo=34687

   (125) https://bugs.python.org/issue?@action=redirect&bpo=5950

   (126) https://bugs.python.org/issue?@action=redirect&bpo=32892

   (127) https://bugs.python.org/issue?@action=redirect&bpo=34728

   (128) https://bugs.python.org/issue?@action=redirect&bpo=34738

   (129) https://bugs.python.org/issue?@action=redirect&bpo=34659

   (130) https://bugs.python.org/issue?@action=redirect&bpo=29577

   (131) https://bugs.python.org/issue?@action=redirect&bpo=34670

   (132) https://bugs.python.org/issue?@action=redirect&bpo=32718

   (133) https://bugs.python.org/issue?@action=redirect&bpo=31177

   (134) https://bugs.python.org/issue?@action=redirect&bpo=34672

   (135) https://bugs.python.org/issue?@action=redirect&bpo=34666

   (136) https://bugs.python.org/issue?@action=redirect&bpo=6721

   (137) https://bugs.python.org/issue?@action=redirect&bpo=34658

   (138) https://bugs.python.org/issue?@action=redirect&bpo=34652

   (139) https://bugs.python.org/issue?@action=redirect&bpo=34638

   (140) https://bugs.python.org/issue?@action=redirect&bpo=34536

   (141) https://bugs.python.org/issue?@action=redirect&bpo=34636

   (142) https://bugs.python.org/issue?@action=redirect&bpo=24412

   (143) https://bugs.python.org/issue?@action=redirect&bpo=34630

   (144) https://bugs.python.org/issue?@action=redirect&bpo=32490

   (145) https://bugs.python.org/issue?@action=redirect&bpo=34363

   (146) https://bugs.python.org/issue?@action=redirect&bpo=34625

   (147) https://bugs.python.org/issue?@action=redirect&bpo=32270

   (148) https://bugs.python.org/issue?@action=redirect&bpo=34622

   (149) https://bugs.python.org/issue?@action=redirect&bpo=34610

   (150) https://bugs.python.org/issue?@action=redirect&bpo=34421

   (151) https://bugs.python.org/issue?@action=redirect&bpo=34604

   (152) https://bugs.python.org/issue?@action=redirect&bpo=30977

   (153) https://bugs.python.org/issue?@action=redirect&bpo=34574

   (154) https://bugs.python.org/issue?@action=redirect&bpo=8110

   (155) https://bugs.python.org/issue?@action=redirect&bpo=34530

   (156) https://bugs.python.org/issue?@action=redirect&bpo=34563

   (157) https://bugs.python.org/issue?@action=redirect&bpo=34558

   (158) https://bugs.python.org/issue?@action=redirect&bpo=34282

   (159) https://bugs.python.org/issue?@action=redirect&bpo=22872

   (160) https://bugs.python.org/issue?@action=redirect&bpo=34515

   (161) https://peps.python.org/pep-3131/

   (162) https://bugs.python.org/issue?@action=redirect&bpo=13312

   (163) https://bugs.python.org/issue?@action=redirect&bpo=34472

   (164) https://bugs.python.org/issue?@action=redirect&bpo=34454

   (165) https://bugs.python.org/issue?@action=redirect&bpo=6700

   (166) https://bugs.python.org/issue?@action=redirect&bpo=34171

   (167) https://bugs.python.org/issue?@action=redirect&bpo=34441

   (168) https://bugs.python.org/issue?@action=redirect&bpo=34427

   (169) https://bugs.python.org/issue?@action=redirect&bpo=34412

   (170) https://bugs.python.org/issue?@action=redirect&bpo=20849

   (171) https://bugs.python.org/issue?@action=redirect&bpo=31715

   (172) https://bugs.python.org/issue?@action=redirect&bpo=34384

   (173) https://bugs.python.org/issue?@action=redirect&bpo=22602

   (174) https://bugs.python.org/issue?@action=redirect&bpo=2122

   (175) https://bugs.python.org/issue?@action=redirect&bpo=34341

   (176) https://bugs.python.org/issue?@action=redirect&bpo=34333

   (177) https://bugs.python.org/issue?@action=redirect&bpo=18540

   (178) https://bugs.python.org/issue?@action=redirect&bpo=26502

   (179) https://bugs.python.org/issue?@action=redirect&bpo=34318

   (180) https://bugs.python.org/issue?@action=redirect&bpo=9372

   (181) https://bugs.python.org/issue?@action=redirect&bpo=33613

   (182) https://bugs.python.org/issue?@action=redirect&bpo=34248

   (183) https://bugs.python.org/issue?@action=redirect&bpo=33089

   (184) https://bugs.python.org/issue?@action=redirect&bpo=34246

   (185) https://bugs.python.org/issue?@action=redirect&bpo=31047

   (186) https://bugs.python.org/issue?@action=redirect&bpo=32321

   (187) https://bugs.python.org/issue?@action=redirect&bpo=34270

   (188) https://bugs.python.org/issue?@action=redirect&bpo=34263

   (189) https://bugs.python.org/issue?@action=redirect&bpo=34035

   (190) https://bugs.python.org/issue?@action=redirect&bpo=32215

   (191) https://bugs.python.org/issue?@action=redirect&bpo=34075

   (192) https://bugs.python.org/issue?@action=redirect&bpo=34251

   (193) https://bugs.python.org/issue?@action=redirect&bpo=19891

   (194) https://bugs.python.org/issue?@action=redirect&bpo=33089

   (195) https://bugs.python.org/issue?@action=redirect&bpo=34228

   (196) https://bugs.python.org/issue?@action=redirect&bpo=13041

   (197) https://bugs.python.org/issue?@action=redirect&bpo=34213

   (198) https://bugs.python.org/issue?@action=redirect&bpo=34052

   (199) https://bugs.python.org/issue?@action=redirect&bpo=34197

   (200) https://bugs.python.org/issue?@action=redirect&bpo=32788

   (201) https://bugs.python.org/issue?@action=redirect&bpo=21446

   (202) https://bugs.python.org/issue?@action=redirect&bpo=940286

   (203) https://bugs.python.org/issue?@action=redirect&bpo=34164

   (204) https://bugs.python.org/issue?@action=redirect&bpo=33729

   (205) https://bugs.python.org/issue?@action=redirect&bpo=34097

   (206) https://bugs.python.org/issue?@action=redirect&bpo=34108

   (207) https://bugs.python.org/issue?@action=redirect&bpo=34070

   (208) https://bugs.python.org/issue?@action=redirect&bpo=27494

   (209) https://bugs.python.org/issue?@action=redirect&bpo=27494

   (210) https://bugs.python.org/issue?@action=redirect&bpo=33967

   (211) https://bugs.python.org/issue?@action=redirect&bpo=34041

   (212) https://bugs.python.org/issue?@action=redirect&bpo=34056

   (213) https://peps.python.org/pep-0552/

   (214) https://bugs.python.org/issue?@action=redirect&bpo=34054

   (215) https://bugs.python.org/issue?@action=redirect&bpo=34043

   (216) https://bugs.python.org/issue?@action=redirect&bpo=34044

   (217) https://bugs.python.org/issue?@action=redirect&bpo=34010

   (218) https://bugs.python.org/issue?@action=redirect&bpo=34019

   (219) https://bugs.python.org/issue?@action=redirect&bpo=34003

   (220) https://bugs.python.org/issue?@action=redirect&bpo=33978

   (221) https://bugs.python.org/issue?@action=redirect&bpo=14117

   (222) https://bugs.python.org/issue?@action=redirect&bpo=33974

   (223) https://bugs.python.org/issue?@action=redirect&bpo=27500

   (224) https://bugs.python.org/issue?@action=redirect&bpo=24567

   (225) https://bugs.python.org/issue?@action=redirect&bpo=33871

   (226) https://bugs.python.org/issue?@action=redirect&bpo=25007

   (227) https://bugs.python.org/issue?@action=redirect&bpo=33929

   (228) https://bugs.python.org/issue?@action=redirect&bpo=33899

   (229) https://bugs.python.org/issue?@action=redirect&bpo=33897

   (230) https://bugs.python.org/issue?@action=redirect&bpo=33695

   (231) https://bugs.python.org/issue?@action=redirect&bpo=33695

   (232) https://bugs.python.org/issue?@action=redirect&bpo=33916

   (233) https://bugs.python.org/issue?@action=redirect&bpo=32568

   (234) https://bugs.python.org/issue?@action=redirect&bpo=33833

   (235) https://bugs.python.org/issue?@action=redirect&bpo=33663

   (236) https://bugs.python.org/issue?@action=redirect&bpo=33721

   (237) https://bugs.python.org/issue?@action=redirect&bpo=26544

   (238) https://bugs.python.org/issue?@action=redirect&bpo=33843

   (239) https://bugs.python.org/issue?@action=redirect&bpo=33842

   (240) https://bugs.python.org/issue?@action=redirect&bpo=30167

   (241) https://bugs.python.org/issue?@action=redirect&bpo=33805

   (242) https://bugs.python.org/issue?@action=redirect&bpo=33687

   (243) https://bugs.python.org/issue?@action=redirect&bpo=33812

   (244) https://bugs.python.org/issue?@action=redirect&bpo=32108

   (245) https://bugs.python.org/issue?@action=redirect&bpo=27397

   (246) https://bugs.python.org/issue?@action=redirect&bpo=33578

   (247) https://bugs.python.org/issue?@action=redirect&bpo=30805

   (248) https://bugs.python.org/issue?@action=redirect&bpo=33476

   (249) https://bugs.python.org/issue?@action=redirect&bpo=33694

   (250) https://bugs.python.org/issue?@action=redirect&bpo=32493

   (251) https://bugs.python.org/issue?@action=redirect&bpo=33792

   (252) https://bugs.python.org/issue?@action=redirect&bpo=33274

   (253) https://bugs.python.org/issue?@action=redirect&bpo=33778

   (254) https://bugs.python.org/issue?@action=redirect&bpo=33165

   (255) https://bugs.python.org/issue?@action=redirect&bpo=33770

   (256) https://bugs.python.org/issue?@action=redirect&bpo=33769

   (257) https://bugs.python.org/issue?@action=redirect&bpo=33767

   (258) https://bugs.python.org/issue?@action=redirect&bpo=33734

   (259) https://bugs.python.org/issue?@action=redirect&bpo=31014

   (260) https://bugs.python.org/issue?@action=redirect&bpo=2504

   (261) https://bugs.python.org/issue?@action=redirect&bpo=33197

   (262) https://bugs.python.org/issue?@action=redirect&bpo=32751

   (263) https://bugs.python.org/issue?@action=redirect&bpo=32684

   (264) https://bugs.python.org/issue?@action=redirect&bpo=33654

   (265) https://bugs.python.org/issue?@action=redirect&bpo=33674

   (266) https://bugs.python.org/issue?@action=redirect&bpo=33671

   (267) https://bugs.python.org/issue?@action=redirect&bpo=25427

   (268) https://bugs.python.org/issue?@action=redirect&bpo=33674

   (269) https://bugs.python.org/issue?@action=redirect&bpo=31647

   (270) https://bugs.python.org/issue?@action=redirect&bpo=32610

   (271) https://bugs.python.org/issue?@action=redirect&bpo=32410

   (272) https://bugs.python.org/issue?@action=redirect&bpo=33469

   (273) https://bugs.python.org/issue?@action=redirect&bpo=33672

   (274) https://bugs.python.org/issue?@action=redirect&bpo=33654

   (275) https://bugs.python.org/issue?@action=redirect&bpo=33652

   (276) https://bugs.python.org/issue?@action=redirect&bpo=32493

   (277) https://bugs.python.org/issue?@action=redirect&bpo=33238

   (278) https://bugs.python.org/issue?@action=redirect&bpo=33618

   (279) https://bugs.python.org/issue?@action=redirect&bpo=33625

   (280) https://bugs.python.org/issue?@action=redirect&bpo=33623

   (281) https://bugs.python.org/issue?@action=redirect&bpo=11874

   (282) https://bugs.python.org/issue?@action=redirect&bpo=30877

   (283) https://bugs.python.org/issue?@action=redirect&bpo=33604

   (284) https://bugs.python.org/issue?@action=redirect&bpo=33582

   (285) https://bugs.python.org/issue?@action=redirect&bpo=21145

   (286) https://bugs.python.org/issue?@action=redirect&bpo=33570

   (287) https://bugs.python.org/issue?@action=redirect&bpo=28556

   (288) https://bugs.python.org/issue?@action=redirect&bpo=12486

   (289) https://bugs.python.org/issue?@action=redirect&bpo=33540

   (290) https://bugs.python.org/issue?@action=redirect&bpo=33548

   (291) https://bugs.python.org/issue?@action=redirect&bpo=33109

   (292) https://bugs.python.org/issue?@action=redirect&bpo=26510

   (293) https://bugs.python.org/issue?@action=redirect&bpo=33541

   (294) https://bugs.python.org/issue?@action=redirect&bpo=33536

   (295) https://bugs.python.org/issue?@action=redirect&bpo=33542

   (296) https://bugs.python.org/issue?@action=redirect&bpo=26819

   (297) https://bugs.python.org/issue?@action=redirect&bpo=33516

   (298) https://bugs.python.org/issue?@action=redirect&bpo=28612

   (299) https://bugs.python.org/issue?@action=redirect&bpo=28167

   (300) https://bugs.python.org/issue?@action=redirect&bpo=33504

   (301) https://bugs.python.org/issue?@action=redirect&bpo=33505

   (302) https://bugs.python.org/issue?@action=redirect&bpo=33497

   (303) https://bugs.python.org/issue?@action=redirect&bpo=29235

   (304) https://bugs.python.org/issue?@action=redirect&bpo=33495

   (305) https://bugs.python.org/issue?@action=redirect&bpo=26103

   (306) https://bugs.python.org/issue?@action=redirect&bpo=29209

   (307) https://bugs.python.org/issue?@action=redirect&bpo=33453

   (308) https://bugs.python.org/issue?@action=redirect&bpo=28556

   (309) https://bugs.python.org/issue?@action=redirect&bpo=33365

   (310) https://bugs.python.org/issue?@action=redirect&bpo=20087

   (311) https://bugs.python.org/issue?@action=redirect&bpo=33422

   (312) https://bugs.python.org/issue?@action=redirect&bpo=28167

   (313) https://bugs.python.org/issue?@action=redirect&bpo=33281

   (314) https://bugs.python.org/issue?@action=redirect&bpo=33311

   (315) https://bugs.python.org/issue?@action=redirect&bpo=27300

   (316) https://bugs.python.org/issue?@action=redirect&bpo=32933

   (317) https://bugs.python.org/issue?@action=redirect&bpo=33217

   (318) https://bugs.python.org/issue?@action=redirect&bpo=33197

   (319) https://bugs.python.org/issue?@action=redirect&bpo=33383

   (320) https://bugs.python.org/issue?@action=redirect&bpo=33375

   (321) https://bugs.python.org/issue?@action=redirect&bpo=33336

   (322) https://bugs.python.org/issue?@action=redirect&bpo=32455

   (323) https://bugs.python.org/issue?@action=redirect&bpo=27485

   (324) https://bugs.python.org/issue?@action=redirect&bpo=33332

   (325) https://bugs.python.org/issue?@action=redirect&bpo=33251

   (326) https://bugs.python.org/issue?@action=redirect&bpo=33329

   (327) https://bugs.python.org/issue?@action=redirect&bpo=33334

   (328) https://bugs.python.org/issue?@action=redirect&bpo=991266

   (329) https://bugs.python.org/issue?@action=redirect&bpo=33131

   (330) https://bugs.python.org/issue?@action=redirect&bpo=33308

   (331) https://bugs.python.org/issue?@action=redirect&bpo=23403

   (332) https://bugs.python.org/issue?@action=redirect&bpo=33266

   (333) https://bugs.python.org/issue?@action=redirect&bpo=11594

   (334) https://bugs.python.org/issue?@action=redirect&bpo=33254

   (335) https://bugs.python.org/issue?@action=redirect&bpo=33265

   (336) https://bugs.python.org/issue?@action=redirect&bpo=33263

   (337) https://bugs.python.org/issue?@action=redirect&bpo=33256

   (338) https://bugs.python.org/issue?@action=redirect&bpo=33144

   (339) https://bugs.python.org/issue?@action=redirect&bpo=33185

   (340) https://bugs.python.org/issue?@action=redirect&bpo=33053

   (341) https://bugs.python.org/issue?@action=redirect&bpo=29613

   (342) https://bugs.python.org/issue?@action=redirect&bpo=33169

   (343) https://bugs.python.org/issue?@action=redirect&bpo=33203

   (344) https://bugs.python.org/issue?@action=redirect&bpo=33224

   (345) https://peps.python.org/pep-0479/

   (346) https://bugs.python.org/issue?@action=redirect&bpo=33209

   (347) https://bugs.python.org/issue?@action=redirect&bpo=32861

   (348) https://bugs.python.org/issue?@action=redirect&bpo=23403

   (349) https://peps.python.org/pep-3154/

   (350) https://bugs.python.org/issue?@action=redirect&bpo=20104

   (351) https://bugs.python.org/issue?@action=redirect&bpo=33106

   (352) https://bugs.python.org/issue?@action=redirect&bpo=33175

   (353) https://bugs.python.org/issue?@action=redirect&bpo=32380

   (354) https://bugs.python.org/issue?@action=redirect&bpo=33141

   (355) https://bugs.python.org/issue?@action=redirect&bpo=33096

   (356) https://bugs.python.org/issue?@action=redirect&bpo=32873

   (357) https://bugs.python.org/issue?@action=redirect&bpo=33134

   (358) https://bugs.python.org/issue?@action=redirect&bpo=33127

   (359) https://bugs.python.org/issue?@action=redirect&bpo=32505

   (360) https://bugs.python.org/issue?@action=redirect&bpo=33078

   (361) https://bugs.python.org/issue?@action=redirect&bpo=33116

   (362) https://bugs.python.org/issue?@action=redirect&bpo=32896

   (363) https://bugs.python.org/issue?@action=redirect&bpo=33100

   (364) https://bugs.python.org/issue?@action=redirect&bpo=32953

   (365) https://bugs.python.org/issue?@action=redirect&bpo=33097

   (366) https://bugs.python.org/issue?@action=redirect&bpo=32968

   (367) https://bugs.python.org/issue?@action=redirect&bpo=33061

   (368) https://bugs.python.org/issue?@action=redirect&bpo=33078

   (369) https://bugs.python.org/issue?@action=redirect&bpo=33064

   (370) https://bugs.python.org/issue?@action=redirect&bpo=33056

   (371) https://bugs.python.org/issue?@action=redirect&bpo=33021

   (372) https://bugs.python.org/issue?@action=redirect&bpo=31804

   (373) https://bugs.python.org/issue?@action=redirect&bpo=33034

   (374) https://bugs.python.org/issue?@action=redirect&bpo=30249

   (375) https://bugs.python.org/issue?@action=redirect&bpo=33037

   (376) https://bugs.python.org/issue?@action=redirect&bpo=27683

   (377) https://bugs.python.org/issue?@action=redirect&bpo=22674

   (378) https://bugs.python.org/issue?@action=redirect&bpo=32999

   (379) https://bugs.python.org/issue?@action=redirect&bpo=33009

   (380) https://bugs.python.org/issue?@action=redirect&bpo=32969

   (381) https://bugs.python.org/issue?@action=redirect&bpo=32056

   (382) https://bugs.python.org/issue?@action=redirect&bpo=32970

   (383) https://bugs.python.org/issue?@action=redirect&bpo=32844

   (384) https://bugs.python.org/issue?@action=redirect&bpo=32960

   (385) https://bugs.python.org/issue?@action=redirect&bpo=32713

   (386) https://bugs.python.org/issue?@action=redirect&bpo=32257

   (387) https://bugs.python.org/issue?@action=redirect&bpo=32951

   (388) https://bugs.python.org/issue?@action=redirect&bpo=32929

   (389) https://bugs.python.org/issue?@action=redirect&bpo=32947

   (390) https://bugs.python.org/issue?@action=redirect&bpo=32146

   (391) https://bugs.python.org/issue?@action=redirect&bpo=30622

   (392) https://bugs.python.org/issue?@action=redirect&bpo=32922

   (393) https://bugs.python.org/issue?@action=redirect&bpo=32759

   (394) https://bugs.python.org/issue?@action=redirect&bpo=32859

   (395) https://bugs.python.org/issue?@action=redirect&bpo=32556

   (396) https://bugs.python.org/issue?@action=redirect&bpo=21060

   (397) https://bugs.python.org/issue?@action=redirect&bpo=32857

   (398) https://bugs.python.org/issue?@action=redirect&bpo=32852

   (399) https://bugs.python.org/issue?@action=redirect&bpo=31333

   (400) https://bugs.python.org/issue?@action=redirect&bpo=32841

   (401) https://bugs.python.org/issue?@action=redirect&bpo=32819

   (402) https://bugs.python.org/issue?@action=redirect&bpo=19675

   (403) https://bugs.python.org/issue?@action=redirect&bpo=32394

   (404) https://bugs.python.org/issue?@action=redirect&bpo=31787

   (405) https://bugs.python.org/issue?@action=redirect&bpo=30157

   (406) https://bugs.python.org/issue?@action=redirect&bpo=30688

   (407) https://bugs.python.org/issue?@action=redirect&bpo=32792

   (408) https://bugs.python.org/issue?@action=redirect&bpo=32775

   (409) https://bugs.python.org/issue?@action=redirect&bpo=32622

   (410) https://bugs.python.org/issue?@action=redirect&bpo=32777

   (411) https://bugs.python.org/issue?@action=redirect&bpo=32647

   (412) https://bugs.python.org/issue?@action=redirect&bpo=32749

   (413) https://bugs.python.org/issue?@action=redirect&bpo=32741

   (414) https://bugs.python.org/issue?@action=redirect&bpo=32691

   (415) https://bugs.python.org/issue?@action=redirect&bpo=32734

   (416) https://bugs.python.org/issue?@action=redirect&bpo=32727

   (417) https://bugs.python.org/issue?@action=redirect&bpo=31453

   (418) https://bugs.python.org/issue?@action=redirect&bpo=24334

   (419) https://bugs.python.org/issue?@action=redirect&bpo=31848

   (420) https://bugs.python.org/issue?@action=redirect&bpo=32585

   (421) https://bugs.python.org/issue?@action=redirect&bpo=32512

   (422) https://bugs.python.org/issue?@action=redirect&bpo=8525

   (423) https://bugs.python.org/issue?@action=redirect&bpo=31639

   (424) https://bugs.python.org/issue?@action=redirect&bpo=29877

   (425) https://bugs.python.org/issue?@action=redirect&bpo=32221

   (426) https://bugs.python.org/issue?@action=redirect&bpo=32147

   (427) https://bugs.python.org/issue?@action=redirect&bpo=30693

   (428) https://bugs.python.org/issue?@action=redirect&bpo=30693

   (429) https://bugs.python.org/issue?@action=redirect&bpo=31680

   (430) https://bugs.python.org/issue?@action=redirect&bpo=31908

   (431) https://bugs.python.org/issue?@action=redirect&bpo=31608

   (432) https://bugs.python.org/issue?@action=redirect&bpo=31425

   (433) https://bugs.python.org/issue?@action=redirect&bpo=22005

   (434) https://bugs.python.org/issue?@action=redirect&bpo=27645

   (435) https://bugs.python.org/issue?@action=redirect&bpo=16865

   (436) https://bugs.python.org/issue?@action=redirect&bpo=31508

   (437) https://bugs.python.org/issue?@action=redirect&bpo=29456


File: python.info,  Node: Documentation<43>,  Next: Tests<45>,  Prev: Library<48>,  Up: Python 3 8 0 alpha 1

1.23.49.4 Documentation
.......................

   - bpo-21257(1): Document *note http.client.parse_headers(): 194f.

   - bpo-34764(2): Improve example of iter() with 2nd sentinel argument.

   - bpo-35564(3): Explicitly set master_doc variable in conf.py for
     compliance with Sphinx 2.0

   - bpo-35511(4): Specified that profile.Profile class doesn't not
     support enable or disable methods.  Also, elaborated that Profile
     object as a context manager is only supported in cProfile module.

   - bpo-10536(5): Enhance the gettext docs.  Patch by Éric Araujo

   - bpo-35089(6): Remove mention of ‘typing.io’ and ‘typing.re’.  Their
     types should be imported from ‘typing’ directly.

   - bpo-35038(7): Fix the documentation about an unexisting
     ‘f_restricted’ attribute in the frame object.  Patch by Stéphane
     Wirtel

   - bpo-35042(8): Replace PEP XYZ by the pep role and allow to use the
     direct links to the PEPs.

   - bpo-35044(9): Fix the documentation with the role ‘exc’ for the
     appropriated exception.  Patch by Stéphane Wirtel

   - bpo-35035(10): Rename documentation for *note email.utils: 47. to
     ‘email.utils.rst’.

   - bpo-34967(11): Use app.add_object_type() instead of the deprecated
     Sphinx function app.description_unit()

   - bpo-34913(12): Add documentation about the new command line
     interface of the gzip module.

   - bpo-32174(13): chm document displays non-ASCII characters properly
     on some MBCS Windows systems.

   - bpo-11233(14): Create availability directive for documentation.
     Original patch by Georg Brandl.

   - bpo-34790(15): Document how passing coroutines to asyncio.wait()
     can be confusing.

   - bpo-34552(16): Make clear that ‘==’ operator sometimes is
     equivalent to ‘is’.  The ‘<’, ‘<=’, ‘>’ and ‘>=’ operators are only
     defined where they make sense.

   - bpo-28617(17): Fixed info in the stdtypes docs concerning the types
     that support membership tests.

   - bpo-20177(18): Migrate datetime.date.fromtimestamp to Argument
     Clinic.  Patch by Tim Hoffmann.

   - bpo-34065(19): Fix wrongly written basicConfig documentation markup
     syntax

   - bpo-33460(20): replaced ellipsis with correct error codes in
     tutorial chapter 3.

   - bpo-33847(21): Add '@' operator entry to index.

   - bpo-33409(22): Clarified the relationship between PEP 538(23)'s
     PYTHONCOERCECLOCALE and PEP 540's PYTHONUTF8 mode.

   - bpo-33197(24): Add versionadded tag to the documentation of
     ParameterKind.description

   - bpo-17045(25): Improve the C-API doc for PyTypeObject.  This
     includes adding several quick-reference tables and a lot of missing
     slot/typedef entries.  The existing entries were also cleaned up
     with a slightly more consistent format.

   - bpo-33736(26): Improve the documentation of *note
     asyncio.open_connection(): abb, *note asyncio.start_server(): abc.
     and their UNIX socket counterparts.

   - bpo-23859(27): Document that ‘asyncio.wait()’ does not cancel its
     futures on timeout.

   - bpo-32436(28): Document PEP 567(29) changes to asyncio.

   - bpo-33604(30): Update HMAC md5 default to a DeprecationWarning,
     bump removal to 3.8.

   - bpo-33594(31): Document ‘getargspec’, ‘from_function’ and
     ‘from_builtin’ as deprecated in their respective docstring, and
     include version since deprecation in DeprecationWarning message.

   - bpo-33503(32): Fix broken pypi link

   - bpo-33421(33): Add missing documentation for
     ‘typing.AsyncContextManager’.

   - bpo-33487(34): BZ2file now emit a DeprecationWarning when
     buffering=None is passed, the deprecation message and documentation
     also now explicitly state it is deprecated since 3.0.

   - bpo-33378(35): Add Korean language switcher for
     ‘https://docs.python.org/3/’

   - bpo-33276(36): Clarify that the ‘__path__’ attribute on modules
     cannot be just any value.

   - bpo-33201(37): Modernize documentation for writing C extension
     types.

   - bpo-33195(38): Deprecate ‘Py_UNICODE’ usage in ‘c-api/arg’
     document.  ‘Py_UNICODE’ related APIs are deprecated since Python
     3.3, but it is missed in the document.

   - bpo-33126(39): Document PyBuffer_ToContiguous().

   - bpo-27212(40): Modify documentation for the ‘islice()’ recipe to
     consume initial values up to the start index.

   - bpo-28247(41): Update *note zipapp: 116. documentation to describe
     how to make standalone applications.

   - bpo-18802(42): Documentation changes for ipaddress.  Patch by Jon
     Foster and Berker Peksag.

   - bpo-27428(43): Update documentation to clarify that
     ‘WindowsRegistryFinder’ implements ‘MetaPathFinder’.  (Patch by
     Himanshu Lakhara)

   - bpo-28124(44): The ssl module function ssl.wrap_socket() has been
     de-emphasized and deprecated in favor of the more secure and
     efficient SSLContext.wrap_socket() method.

   - bpo-17232(45): Clarify docs for -O and -OO. Patch by Terry Reedy.

   - bpo-32436(46): Add documentation for the contextvars module (PEP
     567).

   - bpo-32800(47): Update link to w3c doc for xml default namespaces.

   - bpo-11015(48): Update *note test.support: cd. documentation.

   - bpo-32613(49): Update the faq/windows.html to use the py command
     from PEP 397 instead of python.

   - bpo-8722(50): Document ‘__getattr__()’ behavior when property
     ‘get()’ method raises *note AttributeError: 2f6.

   - bpo-32614(51): Modify RE examples in documentation to use raw
     strings to prevent *note DeprecationWarning: 18b. and add text to
     REGEX HOWTO to highlight the deprecation.

   - bpo-20709(52): Remove the paragraph where we explain that
     os.utime() does not support a directory as path under Windows.
     Patch by Jan-Philip Gehrcke

   - bpo-32722(53): Remove the bad example in the tutorial of the
     Generator Expression.  Patch by Stéphane Wirtel

   - bpo-31972(54): Improve docstrings for ‘pathlib.PurePath’
     subclasses.

   - bpo-30607(55): Use the externalized ‘python-docs-theme’ package
     when building the documentation.

   - bpo-8243(56): Add a note about curses.addch and curses.addstr
     exception behavior when writing outside a window, or pad.

   - bpo-32337(57): Update documentation related with ‘dict’ order.

   - bpo-25041(58): Document ‘AF_PACKET’ in the *note socket: b8.
     module.

   - bpo-31432(59): Clarify meaning of CERT_NONE, CERT_OPTIONAL, and
     CERT_REQUIRED flags for ssl.SSLContext.verify_mode.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21257

   (2) https://bugs.python.org/issue?@action=redirect&bpo=34764

   (3) https://bugs.python.org/issue?@action=redirect&bpo=35564

   (4) https://bugs.python.org/issue?@action=redirect&bpo=35511

   (5) https://bugs.python.org/issue?@action=redirect&bpo=10536

   (6) https://bugs.python.org/issue?@action=redirect&bpo=35089

   (7) https://bugs.python.org/issue?@action=redirect&bpo=35038

   (8) https://bugs.python.org/issue?@action=redirect&bpo=35042

   (9) https://bugs.python.org/issue?@action=redirect&bpo=35044

   (10) https://bugs.python.org/issue?@action=redirect&bpo=35035

   (11) https://bugs.python.org/issue?@action=redirect&bpo=34967

   (12) https://bugs.python.org/issue?@action=redirect&bpo=34913

   (13) https://bugs.python.org/issue?@action=redirect&bpo=32174

   (14) https://bugs.python.org/issue?@action=redirect&bpo=11233

   (15) https://bugs.python.org/issue?@action=redirect&bpo=34790

   (16) https://bugs.python.org/issue?@action=redirect&bpo=34552

   (17) https://bugs.python.org/issue?@action=redirect&bpo=28617

   (18) https://bugs.python.org/issue?@action=redirect&bpo=20177

   (19) https://bugs.python.org/issue?@action=redirect&bpo=34065

   (20) https://bugs.python.org/issue?@action=redirect&bpo=33460

   (21) https://bugs.python.org/issue?@action=redirect&bpo=33847

   (22) https://bugs.python.org/issue?@action=redirect&bpo=33409

   (23) https://peps.python.org/pep-0538/

   (24) https://bugs.python.org/issue?@action=redirect&bpo=33197

   (25) https://bugs.python.org/issue?@action=redirect&bpo=17045

   (26) https://bugs.python.org/issue?@action=redirect&bpo=33736

   (27) https://bugs.python.org/issue?@action=redirect&bpo=23859

   (28) https://bugs.python.org/issue?@action=redirect&bpo=32436

   (29) https://peps.python.org/pep-0567/

   (30) https://bugs.python.org/issue?@action=redirect&bpo=33604

   (31) https://bugs.python.org/issue?@action=redirect&bpo=33594

   (32) https://bugs.python.org/issue?@action=redirect&bpo=33503

   (33) https://bugs.python.org/issue?@action=redirect&bpo=33421

   (34) https://bugs.python.org/issue?@action=redirect&bpo=33487

   (35) https://bugs.python.org/issue?@action=redirect&bpo=33378

   (36) https://bugs.python.org/issue?@action=redirect&bpo=33276

   (37) https://bugs.python.org/issue?@action=redirect&bpo=33201

   (38) https://bugs.python.org/issue?@action=redirect&bpo=33195

   (39) https://bugs.python.org/issue?@action=redirect&bpo=33126

   (40) https://bugs.python.org/issue?@action=redirect&bpo=27212

   (41) https://bugs.python.org/issue?@action=redirect&bpo=28247

   (42) https://bugs.python.org/issue?@action=redirect&bpo=18802

   (43) https://bugs.python.org/issue?@action=redirect&bpo=27428

   (44) https://bugs.python.org/issue?@action=redirect&bpo=28124

   (45) https://bugs.python.org/issue?@action=redirect&bpo=17232

   (46) https://bugs.python.org/issue?@action=redirect&bpo=32436

   (47) https://bugs.python.org/issue?@action=redirect&bpo=32800

   (48) https://bugs.python.org/issue?@action=redirect&bpo=11015

   (49) https://bugs.python.org/issue?@action=redirect&bpo=32613

   (50) https://bugs.python.org/issue?@action=redirect&bpo=8722

   (51) https://bugs.python.org/issue?@action=redirect&bpo=32614

   (52) https://bugs.python.org/issue?@action=redirect&bpo=20709

   (53) https://bugs.python.org/issue?@action=redirect&bpo=32722

   (54) https://bugs.python.org/issue?@action=redirect&bpo=31972

   (55) https://bugs.python.org/issue?@action=redirect&bpo=30607

   (56) https://bugs.python.org/issue?@action=redirect&bpo=8243

   (57) https://bugs.python.org/issue?@action=redirect&bpo=32337

   (58) https://bugs.python.org/issue?@action=redirect&bpo=25041

   (59) https://bugs.python.org/issue?@action=redirect&bpo=31432


File: python.info,  Node: Tests<45>,  Next: Build<47>,  Prev: Documentation<43>,  Up: Python 3 8 0 alpha 1

1.23.49.5 Tests
...............

   - bpo-35772(1): Fix sparse file tests of test_tarfile on ppc64 with
     the tmpfs filesystem.  Fix the function testing if the filesystem
     supports sparse files: create a file which contains data and
     "holes", instead of creating a file which contains no data.  tmpfs
     effective block size is a page size (tmpfs lives in the page
     cache).  RHEL uses 64 KiB pages on aarch64, ppc64, ppc64le, only
     s390x and x86_64 use 4 KiB pages, whereas the test punch holes of 4
     KiB.

   - bpo-35045(2): Make ssl tests less strict and also accept TLSv1 as
     system default.  The changes unbreaks test_min_max_version on
     Fedora 29.

   - bpo-32710(3): ‘test_asyncio/test_sendfile.py’ now resets the event
     loop policy using ‘tearDownModule()’ as done in other tests, to
     prevent a warning when running tests on Windows.

   - bpo-33717(4): test.pythoninfo now logs information of all clocks,
     not only time.time() and time.perf_counter().

   - bpo-35488(5): Add a test to pathlib's Path.match() to verify it
     does not support glob-style ** recursive pattern matching.

   - bpo-31731(6): Fix a race condition in ‘check_interrupted_write()’
     of test_io: create directly the thread with SIGALRM signal blocked,
     rather than blocking the signal later from the thread.  Previously,
     it was possible that the thread gets the signal before the signal
     is blocked.

   - bpo-35424(7): Fix test_multiprocessing_main_handling: use
     ‘multiprocessing.Pool’ with a context manager and then explicitly
     join the pool.

   - bpo-35519(8): Rename ‘test.bisect’ module to ‘test.bisect_cmd’ to
     avoid conflict with *note bisect: d. module when running directly a
     test like ‘./python Lib/test/test_xmlrpc.py’.

   - bpo-35513(9): Replace *note time.time(): 239. with *note
     time.monotonic(): 238. in tests to measure time delta.

   - bpo-34279(10): ‘test.support.run_unittest()’ no longer raise
     ‘TestDidNotRun’ if the test result contains skipped tests.  The
     exception is now only raised if no test have been run and no test
     have been skipped.

   - bpo-35412(11): Add testcase to ‘test_future4’: check unicode
     literal.

   - bpo-26704(12): Added test demonstrating double-patching of an
     instance method.  Patch by Anthony Sottile.

   - bpo-33725(13): test_multiprocessing_fork may crash on recent
     versions of macOS. Until the issue is resolved, skip the test on
     macOS.

   - bpo-35352(14): Modify test_asyncio to use the certificate set from
     the test directory.

   - bpo-35317(15): Fix ‘mktime()’ overflow error in ‘test_email’: run
     ‘test_localtime_daylight_true_dst_true()’ and
     ‘test_localtime_daylight_false_dst_true()’ with a specific
     timezone.

   - bpo-21263(16): After several reports that test_gdb does not work
     properly on macOS and since gdb is not shipped by default anymore,
     test_gdb is now skipped on macOS when LLVM Clang has been used to
     compile Python.  Patch by Lysandros Nikolaou

   - bpo-34279(17): regrtest issue a warning when no tests have been
     executed in a particular test file.  Also, a new final result state
     is issued if no test have been executed across all test files.
     Patch by Pablo Galindo.

   - bpo-34962(18): make docstest in Doc now passes., and is enforced in
     CI

   - bpo-23596(19): Use argparse for the command line of the gzip
     module.  Patch by Antony Lee

   - bpo-34537(20): Fix ‘test_gdb.test_strings()’ when ‘LC_ALL=C’ and
     GDB was compiled with Python 3.6 or earlier.

   - bpo-34587(21): test_socket: Remove RDSTest.testCongestion().  The
     test tries to fill the receiver's socket buffer and expects an
     error.  But the RDS protocol doesn't require that.  Moreover, the
     Linux implementation of RDS expects that the producer of the
     messages reduces its rate, it's not the role of the receiver to
     trigger an error.  The test fails on Fedora 28 by design, so just
     remove it.

   - bpo-34661(22): Fix test_shutil if unzip doesn't support -t.

   - bpo-34200(23): Fixed non-deterministic flakiness of test_pkg by not
     using the scary test.support.module_cleanup() logic to save and
     restore sys.modules contents between test cases.

   - bpo-34569(24): The experimental PEP 554 data channels now correctly
     pass negative PyLong objects between subinterpreters on 32-bit
     systems.  Patch by Michael Felt.

   - bpo-34594(25): Fix usage of hardcoded ‘errno’ values in the tests.

   - bpo-34579(26): Fix test_embed for AIX Patch by Michael Felt

   - bpo-34542(27): Use 3072 RSA keys and SHA-256 signature for test
     certs and keys.

   - bpo-11193(28): Remove special condition for AIX in
     ‘test_subprocess.test_undecodable_env’

   - bpo-34347(29): Fix ‘test_utf8_mode.test_cmd_line’ for AIX

   - bpo-34490(30): On AIX with AF_UNIX family sockets getsockname()
     does not provide 'sockname', so skip calls to
     transport.get_extra_info('sockname')

   - bpo-34391(31): Fix ftplib test for TLS 1.3 by reading from data
     socket.

   - bpo-11192(32): Fix ‘test_socket’ on AIX 6.1 and later IPv6 zone id
     supports only supported by ‘inet_pton6_zone()’.  Switch to
     runtime-based ‘platform.system()’ to establish current platform
     rather than build-time based ‘sys.platform()’

   - bpo-34399(33): Update all RSA keys and DH params to use at least
     2048 bits.

   - bpo-34373(34): Fix ‘test_mktime’ and ‘test_pthread_getcpuclickid’
     tests for AIX Add range checking for ‘_PyTime_localtime’ for AIX
     Patch by Michael Felt

   - bpo-11191(35): Skip the distutils test 'test_search_cpp' when using
     XLC as compiler patch by aixtools (Michael Felt)

   - Improved an error message when mock assert_has_calls fails.

   - bpo-33746(36): Fix test_unittest when run in verbose mode.

   - bpo-33901(37): Fix test_dbm_gnu on macOS with gdbm 1.15: add a
     larger value to make sure that the file size changes.

   - bpo-33873(38): Fix a bug in ‘regrtest’ that caused an extra test to
     run if -huntrleaks/-R was used.  Exit with error in case that
     invalid parameters are specified to -huntrleaks/-R (at least one
     warmup run and one repetition must be used).

   - bpo-33562(39): Check that a global asyncio event loop policy is not
     left behind by any tests.

   - bpo-33655(40): Ignore test_posix_fallocate failures on BSD
     platforms that might be due to running on ZFS.

   - bpo-32962(41): Fixed test_gdb when Python is compiled with flags
     -mcet -fcf-protection -O0.

   - bpo-33358(42): Fix
     ‘test_embed.test_pre_initialization_sys_options()’ when the
     interpreter is built with ‘--enable-shared’.

   - bpo-32872(43): Avoid regrtest compatibility issue with namespace
     packages.

   - bpo-32517(44): Fix failing ‘test_asyncio’ on macOS 10.12.2+ due to
     transport of ‘KqueueSelector’ loop was not being closed.

   - bpo-32663(45): Making sure the ‘SMTPUTF8SimTests’ class of tests
     gets run in ‘test_smtplib.py’.

   - bpo-27643(46): Test_C test case needs "signed short" bitfields, but
     the IBM XLC compiler (on AIX) does not support this Skip the code
     and test when AIX and XLC are used

     Applicable to Python2-2.7 and later

   - bpo-19417(47): Add test_bdb.py.

   - bpo-31809(48): Add tests to verify connection with secp ECDH
     curves.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35772

   (2) https://bugs.python.org/issue?@action=redirect&bpo=35045

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32710

   (4) https://bugs.python.org/issue?@action=redirect&bpo=33717

   (5) https://bugs.python.org/issue?@action=redirect&bpo=35488

   (6) https://bugs.python.org/issue?@action=redirect&bpo=31731

   (7) https://bugs.python.org/issue?@action=redirect&bpo=35424

   (8) https://bugs.python.org/issue?@action=redirect&bpo=35519

   (9) https://bugs.python.org/issue?@action=redirect&bpo=35513

   (10) https://bugs.python.org/issue?@action=redirect&bpo=34279

   (11) https://bugs.python.org/issue?@action=redirect&bpo=35412

   (12) https://bugs.python.org/issue?@action=redirect&bpo=26704

   (13) https://bugs.python.org/issue?@action=redirect&bpo=33725

   (14) https://bugs.python.org/issue?@action=redirect&bpo=35352

   (15) https://bugs.python.org/issue?@action=redirect&bpo=35317

   (16) https://bugs.python.org/issue?@action=redirect&bpo=21263

   (17) https://bugs.python.org/issue?@action=redirect&bpo=34279

   (18) https://bugs.python.org/issue?@action=redirect&bpo=34962

   (19) https://bugs.python.org/issue?@action=redirect&bpo=23596

   (20) https://bugs.python.org/issue?@action=redirect&bpo=34537

   (21) https://bugs.python.org/issue?@action=redirect&bpo=34587

   (22) https://bugs.python.org/issue?@action=redirect&bpo=34661

   (23) https://bugs.python.org/issue?@action=redirect&bpo=34200

   (24) https://bugs.python.org/issue?@action=redirect&bpo=34569

   (25) https://bugs.python.org/issue?@action=redirect&bpo=34594

   (26) https://bugs.python.org/issue?@action=redirect&bpo=34579

   (27) https://bugs.python.org/issue?@action=redirect&bpo=34542

   (28) https://bugs.python.org/issue?@action=redirect&bpo=11193

   (29) https://bugs.python.org/issue?@action=redirect&bpo=34347

   (30) https://bugs.python.org/issue?@action=redirect&bpo=34490

   (31) https://bugs.python.org/issue?@action=redirect&bpo=34391

   (32) https://bugs.python.org/issue?@action=redirect&bpo=11192

   (33) https://bugs.python.org/issue?@action=redirect&bpo=34399

   (34) https://bugs.python.org/issue?@action=redirect&bpo=34373

   (35) https://bugs.python.org/issue?@action=redirect&bpo=11191

   (36) https://bugs.python.org/issue?@action=redirect&bpo=33746

   (37) https://bugs.python.org/issue?@action=redirect&bpo=33901

   (38) https://bugs.python.org/issue?@action=redirect&bpo=33873

   (39) https://bugs.python.org/issue?@action=redirect&bpo=33562

   (40) https://bugs.python.org/issue?@action=redirect&bpo=33655

   (41) https://bugs.python.org/issue?@action=redirect&bpo=32962

   (42) https://bugs.python.org/issue?@action=redirect&bpo=33358

   (43) https://bugs.python.org/issue?@action=redirect&bpo=32872

   (44) https://bugs.python.org/issue?@action=redirect&bpo=32517

   (45) https://bugs.python.org/issue?@action=redirect&bpo=32663

   (46) https://bugs.python.org/issue?@action=redirect&bpo=27643

   (47) https://bugs.python.org/issue?@action=redirect&bpo=19417

   (48) https://bugs.python.org/issue?@action=redirect&bpo=31809


File: python.info,  Node: Build<47>,  Next: Windows<43>,  Prev: Tests<45>,  Up: Python 3 8 0 alpha 1

1.23.49.6 Build
...............

   - bpo-34691(1): The _contextvars module is now built into the core
     Python library on Windows.

   - bpo-35683(2): Improved Azure Pipelines build steps and now
     verifying layouts correctly

   - bpo-35642(3): Remove asynciomodule.c from pythoncore.vcxproj

   - bpo-35550(4): Fix incorrect Solaris #ifdef checks to look for __sun
     && __SVR4 instead of sun when compiling.

   - bpo-35499(5): ‘make profile-opt’ no longer replaces ‘CFLAGS_NODIST’
     with ‘CFLAGS’.  It now adds profile-guided optimization (PGO) flags
     to ‘CFLAGS_NODIST’: existing ‘CFLAGS_NODIST’ flags are kept.

   - bpo-35257(6): Avoid leaking the linker flags from Link Time
     Optimizations (LTO) into distutils when compiling C extensions.

   - bpo-35351(7): When building Python with clang and LTO, LTO flags
     are no longer passed into CFLAGS to build third-party C extensions
     through distutils.

   - bpo-35139(8): Fix a compiler error when statically linking
     ‘pyexpat’ in ‘Modules/Setup’.

   - bpo-35059(9): PCbuild: Set InlineFunctionExpansion to
     OnlyExplicitInline ("/Ob1" option) in pyproject.props in Debug mode
     to expand functions marked as inline.  This change should make
     Python compiled in Debug mode a little bit faster on Windows.

   - bpo-35011(10): Restores the use of pyexpatns.h to isolate our
     embedded copy of the expat C library so that its symbols do not
     conflict at link or dynamic loading time with an embedding
     application or other extension modules with their own version of
     libexpat.

   - bpo-28015(11): Have -with-lto works correctly with clang.

   - bpo-34765(12): Update the outdated install-sh file to the latest
     revision from automake v1.16.1

   - bpo-34585(13): Check for floating-point byte order in configure.ac
     using compilation tests instead of executing code, so that these
     checks work in cross-compiled builds.

   - bpo-34710(14): Fixed SSL module build with OpenSSL & pedantic
     CFLAGS.

   - bpo-34582(15): Add JUnit XML output for regression tests and update
     Azure DevOps builds.

   - bpo-34081(16): Make Sphinx warnings as errors in the Docs Makefile.

   - bpo-34555(17): Fix for case where it was not possible to have both
     ‘HAVE_LINUX_VM_SOCKETS_H’ and ‘HAVE_SOCKADDR_ALG’ be undefined.

   - bpo-33015(18): Fix an undefined behaviour in the pthread
     implementation of ‘PyThread_start_new_thread()’: add a function
     wrapper to always return ‘NULL’.

   - bpo-34245(19): The Python shared library is now installed with
     write permission (mode 0755), which is the standard way of
     installing such libraries.

   - bpo-34121(20): Fix detection of C11 atomic support on clang.

   - bpo-32430(21): Rename Modules/Setup.dist to Modules/Setup, and
     remove the necessity to copy the former manually to the latter when
     updating the local source tree.

   - bpo-30345(22): Add -g to LDFLAGS when compiling with LTO to get
     debug symbols.

   - bpo-5755(23): Move ‘-Wstrict-prototypes’ option to ‘CFLAGS_NODIST’
     from ‘OPT’.  This option emitted annoying warnings when building
     extension modules written in C++.

   - bpo-33614(24): Ensures module definition files for the stable ABI
     on Windows are correctly regenerated.

   - bpo-33648(25): The -with-c-locale-warning configuration flag has
     been removed.  It has had no effect for about a year.

   - bpo-33522(26): Enable CI builds on Visual Studio Team Services at
     ‘https://python.visualstudio.com/cpython’

   - bpo-33512(27): configure's check for "long double" has been
     simplified

   - bpo-33483(28): C compiler is now correctly detected from the
     standard environment variables.  -without-gcc and -with-icc options
     have been removed.

   - bpo-33394(29): Enable the verbose build for extension modules, when
     GNU make is passed macros on the command line.

   - bpo-33393(30): Update config.guess and config.sub files.

   - bpo-33377(31): Add new triplets for mips r6 and riscv variants
     (used in extension suffixes).

   - bpo-32232(32): By default, modules configured in ‘Modules/Setup’
     are no longer built with ‘-DPy_BUILD_CORE’.  Instead, modules that
     specifically need that preprocessor definition include it in their
     individual entries.

   - bpo-33182(33): The embedding tests can once again be built with
     clang 6.0

   - bpo-33163(34): Upgrade pip to 9.0.3 and setuptools to v39.0.1.

   - bpo-33012(35): gcc 8 has added a new warning heuristic to detect
     invalid function casts and a stock python build seems to hit that
     warning quite often.  The most common is the cast of a METH_NOARGS
     function (that uses just one argument) to a PyCFunction.  Fix this
     by adding a dummy argument to all functions that implement
     METH_NOARGS.

   - bpo-32898(36): Fix the python debug build when using COUNT_ALLOCS.

   - bpo-29442(37): Replace optparse with argparse in setup.py

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=34691

   (2) https://bugs.python.org/issue?@action=redirect&bpo=35683

   (3) https://bugs.python.org/issue?@action=redirect&bpo=35642

   (4) https://bugs.python.org/issue?@action=redirect&bpo=35550

   (5) https://bugs.python.org/issue?@action=redirect&bpo=35499

   (6) https://bugs.python.org/issue?@action=redirect&bpo=35257

   (7) https://bugs.python.org/issue?@action=redirect&bpo=35351

   (8) https://bugs.python.org/issue?@action=redirect&bpo=35139

   (9) https://bugs.python.org/issue?@action=redirect&bpo=35059

   (10) https://bugs.python.org/issue?@action=redirect&bpo=35011

   (11) https://bugs.python.org/issue?@action=redirect&bpo=28015

   (12) https://bugs.python.org/issue?@action=redirect&bpo=34765

   (13) https://bugs.python.org/issue?@action=redirect&bpo=34585

   (14) https://bugs.python.org/issue?@action=redirect&bpo=34710

   (15) https://bugs.python.org/issue?@action=redirect&bpo=34582

   (16) https://bugs.python.org/issue?@action=redirect&bpo=34081

   (17) https://bugs.python.org/issue?@action=redirect&bpo=34555

   (18) https://bugs.python.org/issue?@action=redirect&bpo=33015

   (19) https://bugs.python.org/issue?@action=redirect&bpo=34245

   (20) https://bugs.python.org/issue?@action=redirect&bpo=34121

   (21) https://bugs.python.org/issue?@action=redirect&bpo=32430

   (22) https://bugs.python.org/issue?@action=redirect&bpo=30345

   (23) https://bugs.python.org/issue?@action=redirect&bpo=5755

   (24) https://bugs.python.org/issue?@action=redirect&bpo=33614

   (25) https://bugs.python.org/issue?@action=redirect&bpo=33648

   (26) https://bugs.python.org/issue?@action=redirect&bpo=33522

   (27) https://bugs.python.org/issue?@action=redirect&bpo=33512

   (28) https://bugs.python.org/issue?@action=redirect&bpo=33483

   (29) https://bugs.python.org/issue?@action=redirect&bpo=33394

   (30) https://bugs.python.org/issue?@action=redirect&bpo=33393

   (31) https://bugs.python.org/issue?@action=redirect&bpo=33377

   (32) https://bugs.python.org/issue?@action=redirect&bpo=32232

   (33) https://bugs.python.org/issue?@action=redirect&bpo=33182

   (34) https://bugs.python.org/issue?@action=redirect&bpo=33163

   (35) https://bugs.python.org/issue?@action=redirect&bpo=33012

   (36) https://bugs.python.org/issue?@action=redirect&bpo=32898

   (37) https://bugs.python.org/issue?@action=redirect&bpo=29442


File: python.info,  Node: Windows<43>,  Next: macOS<35>,  Prev: Build<47>,  Up: Python 3 8 0 alpha 1

1.23.49.7 Windows
.................

   - bpo-35890(1): Fix API calling consistency of GetVersionEx and
     wcstok.

   - bpo-32560(2): The ‘py’ launcher now forwards its ‘STARTUPINFO’
     structure to child processes.

   - bpo-35854(3): Fix EnvBuilder and -symlinks in venv on Windows

   - bpo-35811(4): Avoid propagating venv settings when launching via
     py.exe

   - bpo-35797(5): Fix default executable used by the multiprocessing
     module

   - bpo-35758(6): Allow building on ARM with MSVC.

   - bpo-29734(7): Fix handle leaks in os.stat on Windows.

   - bpo-35596(8): Use unchecked PYCs for the embeddable distro to avoid
     zipimport restrictions.

   - bpo-35596(9): Fix vcruntime140.dll being added to embeddable distro
     multiple times.

   - bpo-35402(10): Update Windows build to use Tcl and Tk 8.6.9

   - bpo-35401(11): Updates Windows build to OpenSSL 1.1.0j

   - bpo-34977(12): venv on Windows will now use a python.exe redirector
     rather than copying the actual binaries from the base environment.

   - bpo-34977(13): Adds support for building a Windows App Store
     package

   - bpo-35067(14): Remove _distutils_findvs module and use vswhere.exe
     instead.

   - bpo-32557(15): Allow shutil.disk_usage to take a file path on
     Windows

   - bpo-34770(16): Fix a possible null pointer dereference in
     pyshellext.cpp.

   - bpo-34603(17): Fix returning structs from functions produced by
     MSVC

   - bpo-34581(18): Guard MSVC-specific code in socketmodule.c with
     ‘#ifdef _MSC_VER’.

   - bpo-34532(19): Fixes exit code of list version arguments for
     py.exe.

   - bpo-34062(20): Fixed the '-list' and '-list-paths' arguments for
     the py.exe launcher

   - bpo-34225(21): Ensure INCLUDE and LIB directories do not end with a
     backslash.

   - bpo-34011(22): A suite of code has been changed which copied across
     DLLs and init.tcl from the running Python location into a venv
     being created.  These copies are needed only when running from a
     Python source build, and the copying code is now only run when that
     is the case, rather than whenever a venv is created.

   - bpo-34006(23): Revert line length limit for Windows help docs.  The
     line-length limit is not needed because the pages appear in a
     separate app rather than on a browser tab.  It can also interact
     badly with the DPI setting.

   - bpo-31546(24): Restore running PyOS_InputHook while waiting for
     user input at the prompt.  The restores integration of interactive
     GUI windows (such as Matplotlib figures) with the prompt on
     Windows.

   - bpo-30237(25): Output error when ReadConsole is canceled by
     CancelSynchronousIo instead of crashing.

   - bpo-33895(26): GIL is released while calling functions that acquire
     Windows loader lock.

   - bpo-33720(27): Reduces maximum marshal recursion depth on release
     builds.

   - bpo-29097(28): Fix bug where ‘datetime.fromtimestamp()’ erroneously
     throws an *note OSError: 350. on Windows for values between 0 and
     86400.  Patch by Ammar Askar.

   - bpo-33316(29): PyThread_release_lock always fails

   - bpo-33184(30): Update Windows installer to use OpenSSL 1.1.0h.

   - bpo-32890(31): Fix usage of GetLastError() instead of errno in
     os.execve() and os.truncate().

   - bpo-33016(32): Fix potential use of uninitialized memory in
     nt._getfinalpathname

   - bpo-32903(33): Fix a memory leak in os.chdir() on Windows if the
     current directory is set to a UNC path.

   - bpo-32901(34): Update Tcl and Tk versions to 8.6.8

   - bpo-31966(35): Fixed WindowsConsoleIO.write() for writing empty
     data.

   - bpo-32409(36): Ensures activate.bat can handle Unicode contents.

   - bpo-32457(37): Improves handling of denormalized executable path
     when launching Python.

   - bpo-32370(38): Use the correct encoding for ipconfig output in the
     uuid module.  Patch by Segev Finer.

   - bpo-29248(39): Fix *note os.readlink(): 8c5. on Windows, which was
     mistakenly treating the ‘PrintNameOffset’ field of the reparse data
     buffer as a number of characters instead of bytes.  Patch by Craig
     Holmquist and SSE4.

   - bpo-1104(40): Correctly handle string length in
     ‘msilib.SummaryInfo.GetProperty()’ to prevent it from truncating
     the last character.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35890

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32560

   (3) https://bugs.python.org/issue?@action=redirect&bpo=35854

   (4) https://bugs.python.org/issue?@action=redirect&bpo=35811

   (5) https://bugs.python.org/issue?@action=redirect&bpo=35797

   (6) https://bugs.python.org/issue?@action=redirect&bpo=35758

   (7) https://bugs.python.org/issue?@action=redirect&bpo=29734

   (8) https://bugs.python.org/issue?@action=redirect&bpo=35596

   (9) https://bugs.python.org/issue?@action=redirect&bpo=35596

   (10) https://bugs.python.org/issue?@action=redirect&bpo=35402

   (11) https://bugs.python.org/issue?@action=redirect&bpo=35401

   (12) https://bugs.python.org/issue?@action=redirect&bpo=34977

   (13) https://bugs.python.org/issue?@action=redirect&bpo=34977

   (14) https://bugs.python.org/issue?@action=redirect&bpo=35067

   (15) https://bugs.python.org/issue?@action=redirect&bpo=32557

   (16) https://bugs.python.org/issue?@action=redirect&bpo=34770

   (17) https://bugs.python.org/issue?@action=redirect&bpo=34603

   (18) https://bugs.python.org/issue?@action=redirect&bpo=34581

   (19) https://bugs.python.org/issue?@action=redirect&bpo=34532

   (20) https://bugs.python.org/issue?@action=redirect&bpo=34062

   (21) https://bugs.python.org/issue?@action=redirect&bpo=34225

   (22) https://bugs.python.org/issue?@action=redirect&bpo=34011

   (23) https://bugs.python.org/issue?@action=redirect&bpo=34006

   (24) https://bugs.python.org/issue?@action=redirect&bpo=31546

   (25) https://bugs.python.org/issue?@action=redirect&bpo=30237

   (26) https://bugs.python.org/issue?@action=redirect&bpo=33895

   (27) https://bugs.python.org/issue?@action=redirect&bpo=33720

   (28) https://bugs.python.org/issue?@action=redirect&bpo=29097

   (29) https://bugs.python.org/issue?@action=redirect&bpo=33316

   (30) https://bugs.python.org/issue?@action=redirect&bpo=33184

   (31) https://bugs.python.org/issue?@action=redirect&bpo=32890

   (32) https://bugs.python.org/issue?@action=redirect&bpo=33016

   (33) https://bugs.python.org/issue?@action=redirect&bpo=32903

   (34) https://bugs.python.org/issue?@action=redirect&bpo=32901

   (35) https://bugs.python.org/issue?@action=redirect&bpo=31966

   (36) https://bugs.python.org/issue?@action=redirect&bpo=32409

   (37) https://bugs.python.org/issue?@action=redirect&bpo=32457

   (38) https://bugs.python.org/issue?@action=redirect&bpo=32370

   (39) https://bugs.python.org/issue?@action=redirect&bpo=29248

   (40) https://bugs.python.org/issue?@action=redirect&bpo=1104


File: python.info,  Node: macOS<35>,  Next: IDLE<35>,  Prev: Windows<43>,  Up: Python 3 8 0 alpha 1

1.23.49.8 macOS
...............

   - bpo-35401(1): Update macOS installer to use OpenSSL 1.1.0j.

   - bpo-35025(2): Properly guard the use of the ‘CLOCK_GETTIME’ et al.
     macros in ‘timemodule’ on macOS.

   - bpo-24658(3): On macOS, fix reading from and writing into a file
     with a size larger than 2 GiB.

   - bpo-34405(4): Update to OpenSSL 1.1.0i for macOS installer builds.

   - bpo-33635(5): In macOS stat on some file descriptors (/dev/fd/3
     f.e) will result in bad file descriptor OSError.  Guard against
     this exception was added in is_dir, is_file and similar methods.
     DirEntry.is_dir can also throw this exception so
     _RecursiveWildcardSelector._iterate_directories was also extended
     with the same error ignoring pattern.

   - bpo-13631(6): The .editrc file in user's home directory is now
     processed correctly during the readline initialization through
     editline emulation on macOS.

   - bpo-33184(7): Update macOS installer build to use OpenSSL 1.1.0h.

   - bpo-32726(8): Build and link with private copy of Tcl/Tk 8.6 for
     the macOS 10.6+ installer.  The 10.9+ installer variant already
     does this.  This means that the Python 3.7 provided by the
     python.org macOS installers no longer need or use any external
     versions of Tcl/Tk, either system-provided or user-installed, such
     as ActiveTcl.

   - bpo-32901(9): Update macOS 10.9+ installer to Tcl/Tk 8.6.8.

   - bpo-31903(10): In ‘_scproxy’, drop the GIL when calling into
     ‘SystemConfiguration’ to avoid deadlocks.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35401

   (2) https://bugs.python.org/issue?@action=redirect&bpo=35025

   (3) https://bugs.python.org/issue?@action=redirect&bpo=24658

   (4) https://bugs.python.org/issue?@action=redirect&bpo=34405

   (5) https://bugs.python.org/issue?@action=redirect&bpo=33635

   (6) https://bugs.python.org/issue?@action=redirect&bpo=13631

   (7) https://bugs.python.org/issue?@action=redirect&bpo=33184

   (8) https://bugs.python.org/issue?@action=redirect&bpo=32726

   (9) https://bugs.python.org/issue?@action=redirect&bpo=32901

   (10) https://bugs.python.org/issue?@action=redirect&bpo=31903


File: python.info,  Node: IDLE<35>,  Next: Tools/Demos<23>,  Prev: macOS<35>,  Up: Python 3 8 0 alpha 1

1.23.49.9 IDLE
..............

   - bpo-35770(1): IDLE macosx deletes Options => Configure IDLE. It
     previously deleted Window => Zoom Height by mistake.  (Zoom Height
     is now on the Options menu).  On Mac, the settings dialog is
     accessed via Preferences on the IDLE menu.

   - bpo-35769(2): Change IDLE's new file name from 'Untitled' to
     'untitled'

   - bpo-35660(3): Fix imports in idlelib.window.

   - bpo-35641(4): Proper format ‘calltip’ when the function has no
     docstring.

   - bpo-33987(5): Use ttk Frame for ttk widgets.

   - bpo-34055(6): Fix erroneous 'smart' indents and newlines in IDLE
     Shell.

   - bpo-35591(7): Find Selection now works when selection not found.

   - bpo-35196(8): Speed up squeezer line counting.

   - bpo-35598(9): Update config_key: use PEP 8 names and ttk widgets,
     make some objects global, and add tests.

   - bpo-28097(10): Add Previous/Next History entries to Shell menu.

   - bpo-35208(11): Squeezer now properly counts wrapped lines before
     newlines.

   - bpo-35555(12): Gray out Code Context menu entry when it's not
     applicable.

   - bpo-35521(13): Document the IDLE editor code context feature.  Add
     some internal references within the IDLE doc.

   - bpo-22703(14): The Code Context menu label now toggles between
     Show/Hide Code Context.  The Zoom Height menu now toggles between
     Zoom/Restore Height.  Zoom Height has moved from the Window menu to
     the Options menu.

   - bpo-35213(15): Where appropriate, use 'macOS' in idlelib.

   - bpo-34864(16): On macOS, warn if the system preference "Prefer tabs
     when opening documents" is set to "Always".

   - bpo-34864(17): Document two IDLE on MacOS issues.  The System
     Preferences Dock "prefer tabs always" setting disables some IDLE
     features.  Menus are a bit different than as described for Windows
     and Linux.

   - bpo-35202(18): Remove unused imports from lib/idlelib

   - bpo-33000(19): Document that IDLE's shell has no line limit.  A
     program that runs indefinitely can overfill memory.

   - bpo-23220(20): Explain how IDLE's Shell displays output.

   - bpo-35099(21): Improve the doc about IDLE running user code.  The
     section is renamed from "IDLE - console differences" is renamed
     "Running user code".  It mostly covers the implications of using
     custom ‘sys.stdXXX’ objects.

   - bpo-35097(22): Add IDLE doc subsection explaining editor windows.
     Topics include opening, title and status bar, .py* extension, and
     running.

   - bpo-35093(23): Document the IDLE document viewer in the IDLE doc.
     Add a paragraph in "Help and preferences", "Help sources"
     subsection.

   - bpo-35088(24): Update idlelib.help.copy_string docstring.  We now
     use git and backporting instead of hg and forward merging.

   - bpo-35087(25): Update idlelib help files for the current doc build.
     The main change is the elimination of chapter-section numbers.

   - bpo-34548(26): Use configured color theme for read-only text views.

   - bpo-1529353(27): Enable "squeezing" of long outputs in the shell,
     to avoid performance degradation and to clean up the history
     without losing it.  Squeezed outputs may be copied, viewed in a
     separate window, and "unsqueezed".

   - bpo-34047(28): Fixed mousewheel scrolling direction on macOS.

   - bpo-34275(29): Make IDLE calltips always visible on Mac.  Some
     MacOS-tk combinations need .update_idletasks().  Patch by Kevin
     Walzer.

   - bpo-34120(30): Fix unresponsiveness after closing certain windows
     and dialogs.

   - bpo-33975(31): Avoid small type when running htests.  Since part of
     the purpose of human-viewed tests is to determine that widgets look
     right, it is important that they look the same for testing as when
     running IDLE.

   - bpo-33905(32): Add test for idlelib.stackview.StackBrowser.

   - bpo-33924(33): Change mainmenu.menudefs key 'windows' to 'window'.
     Every other menudef key is lowercase version of main menu entry.

   - bpo-33906(34): Rename idlelib.windows as window Match Window on the
     main menu and remove last plural module name.

   - bpo-33917(35): Fix and document idlelib/idle_test/template.py.  The
     revised file compiles, runs, and tests OK. idle_test/README.txt
     explains how to use it to create new IDLE test files.

   - bpo-33904(36): IDLE: In rstrip, rename class RstripExtension as
     Rstrip

   - bpo-33907(37): For consistency and clarity, rename an IDLE module
     and classes.  Module calltips and its class CallTips are now
     calltip and Calltip.  In module calltip_w, class CallTip is now
     CalltipWindow.

   - bpo-33856(38): Add "help" in the welcome message of IDLE

   - bpo-33839(39): IDLE: refactor ToolTip and CallTip and add
     documentation and tests

   - bpo-33855(40): Minimally test all IDLE modules.  Add missing files,
     import module, instantiate classes, and check coverage.  Check
     existing files.

   - bpo-33656(41): On Windows, add API call saying that tk scales for
     DPI. On Windows 8.1+ or 10, with DPI compatibility properties of
     the Python binary unchanged, and a monitor resolution greater than
     96 DPI, this should make text and lines sharper.  It should
     otherwise have no effect.

   - bpo-33768(42): Clicking on a context line moves that line to the
     top of the editor window.

   - bpo-33763(43): IDLE: Use read-only text widget for code context
     instead of label widget.

   - bpo-33664(44): Scroll IDLE editor text by lines.  Previously, the
     mouse wheel and scrollbar slider moved text by a fixed number of
     pixels, resulting in partial lines at the top of the editor box.
     The change also applies to the shell and grep output windows, but
     not to read-only text views.

   - bpo-33679(45): Enable theme-specific color configuration for Code
     Context.  Use the Highlights tab to see the setting for built-in
     themes or add settings to custom themes.

   - bpo-33642(46): Display up to maxlines non-blank lines for Code
     Context.  If there is no current context, show a single blank line.

   - bpo-33628(47): IDLE: Cleanup codecontext.py and its test.

   - bpo-33564(48): IDLE's code context now recognizes async as a block
     opener.

   - bpo-21474(49): Update word/identifier definition from ascii to
     unicode.  In text and entry boxes, this affects selection by
     double-click, movement left/right by control-left/right, and
     deletion left/right by control-BACKSPACE/DEL.

   - bpo-33204(50): IDLE: consistently color invalid string prefixes.  A
     'u' string prefix cannot be paired with either 'r' or 'f'.
     Consistently color as much of the prefix, starting at the right, as
     is valid.  Revise and extend colorizer test.

   - bpo-32984(51): Set ‘__file__’ while running a startup file.  Like
     Python, IDLE optionally runs one startup file in the Shell window
     before presenting the first interactive input prompt.  For IDLE,
     ‘-s’ runs a file named in environmental variable ‘IDLESTARTUP’ or
     *note PYTHONSTARTUP: f6b.; ‘-r file’ runs ‘file’.  Python sets
     ‘__file__’ to the startup file name before running the file and
     unsets it before the first prompt.  IDLE now does the same when run
     normally, without the ‘-n’ option.

   - bpo-32940(52): Simplify and rename StringTranslatePseudoMapping in
     pyparse.

   - bpo-32916(53): Change ‘str’ to ‘code’ in pyparse.

   - bpo-32905(54): Remove unused code in pyparse module.

   - bpo-32874(55): Add tests for pyparse.

   - bpo-32837(56): Using the system and place-dependent default
     encoding for open() is a bad idea for IDLE's system and
     location-independent files.

   - bpo-32826(57): Add "encoding=utf-8" to open() in IDLE's
     test_help_about.  GUI test test_file_buttons() only looks at
     initial ascii-only lines, but failed on systems where open()
     defaults to 'ascii' because readline() internally reads and decodes
     far enough ahead to encounter a non-ascii character in CREDITS.txt.

   - bpo-32831(58): Add docstrings and tests for codecontext.

   - bpo-32765(59): Update configdialog General tab docstring to add new
     widgets to the widget list.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35770

   (2) https://bugs.python.org/issue?@action=redirect&bpo=35769

   (3) https://bugs.python.org/issue?@action=redirect&bpo=35660

   (4) https://bugs.python.org/issue?@action=redirect&bpo=35641

   (5) https://bugs.python.org/issue?@action=redirect&bpo=33987

   (6) https://bugs.python.org/issue?@action=redirect&bpo=34055

   (7) https://bugs.python.org/issue?@action=redirect&bpo=35591

   (8) https://bugs.python.org/issue?@action=redirect&bpo=35196

   (9) https://bugs.python.org/issue?@action=redirect&bpo=35598

   (10) https://bugs.python.org/issue?@action=redirect&bpo=28097

   (11) https://bugs.python.org/issue?@action=redirect&bpo=35208

   (12) https://bugs.python.org/issue?@action=redirect&bpo=35555

   (13) https://bugs.python.org/issue?@action=redirect&bpo=35521

   (14) https://bugs.python.org/issue?@action=redirect&bpo=22703

   (15) https://bugs.python.org/issue?@action=redirect&bpo=35213

   (16) https://bugs.python.org/issue?@action=redirect&bpo=34864

   (17) https://bugs.python.org/issue?@action=redirect&bpo=34864

   (18) https://bugs.python.org/issue?@action=redirect&bpo=35202

   (19) https://bugs.python.org/issue?@action=redirect&bpo=33000

   (20) https://bugs.python.org/issue?@action=redirect&bpo=23220

   (21) https://bugs.python.org/issue?@action=redirect&bpo=35099

   (22) https://bugs.python.org/issue?@action=redirect&bpo=35097

   (23) https://bugs.python.org/issue?@action=redirect&bpo=35093

   (24) https://bugs.python.org/issue?@action=redirect&bpo=35088

   (25) https://bugs.python.org/issue?@action=redirect&bpo=35087

   (26) https://bugs.python.org/issue?@action=redirect&bpo=34548

   (27) https://bugs.python.org/issue?@action=redirect&bpo=1529353

   (28) https://bugs.python.org/issue?@action=redirect&bpo=34047

   (29) https://bugs.python.org/issue?@action=redirect&bpo=34275

   (30) https://bugs.python.org/issue?@action=redirect&bpo=34120

   (31) https://bugs.python.org/issue?@action=redirect&bpo=33975

   (32) https://bugs.python.org/issue?@action=redirect&bpo=33905

   (33) https://bugs.python.org/issue?@action=redirect&bpo=33924

   (34) https://bugs.python.org/issue?@action=redirect&bpo=33906

   (35) https://bugs.python.org/issue?@action=redirect&bpo=33917

   (36) https://bugs.python.org/issue?@action=redirect&bpo=33904

   (37) https://bugs.python.org/issue?@action=redirect&bpo=33907

   (38) https://bugs.python.org/issue?@action=redirect&bpo=33856

   (39) https://bugs.python.org/issue?@action=redirect&bpo=33839

   (40) https://bugs.python.org/issue?@action=redirect&bpo=33855

   (41) https://bugs.python.org/issue?@action=redirect&bpo=33656

   (42) https://bugs.python.org/issue?@action=redirect&bpo=33768

   (43) https://bugs.python.org/issue?@action=redirect&bpo=33763

   (44) https://bugs.python.org/issue?@action=redirect&bpo=33664

   (45) https://bugs.python.org/issue?@action=redirect&bpo=33679

   (46) https://bugs.python.org/issue?@action=redirect&bpo=33642

   (47) https://bugs.python.org/issue?@action=redirect&bpo=33628

   (48) https://bugs.python.org/issue?@action=redirect&bpo=33564

   (49) https://bugs.python.org/issue?@action=redirect&bpo=21474

   (50) https://bugs.python.org/issue?@action=redirect&bpo=33204

   (51) https://bugs.python.org/issue?@action=redirect&bpo=32984

   (52) https://bugs.python.org/issue?@action=redirect&bpo=32940

   (53) https://bugs.python.org/issue?@action=redirect&bpo=32916

   (54) https://bugs.python.org/issue?@action=redirect&bpo=32905

   (55) https://bugs.python.org/issue?@action=redirect&bpo=32874

   (56) https://bugs.python.org/issue?@action=redirect&bpo=32837

   (57) https://bugs.python.org/issue?@action=redirect&bpo=32826

   (58) https://bugs.python.org/issue?@action=redirect&bpo=32831

   (59) https://bugs.python.org/issue?@action=redirect&bpo=32765


File: python.info,  Node: Tools/Demos<23>,  Next: C API<46>,  Prev: IDLE<35>,  Up: Python 3 8 0 alpha 1

1.23.49.10 Tools/Demos
......................

   - bpo-35884(1): Add a benchmark script for timing various ways to
     access variables: ‘Tools/scripts/var_access_benchmark.py’.

   - bpo-34989(2): python-gdb.py now handles errors on computing the
     line number of a Python frame.

   - bpo-20260(3): Argument Clinic now has non-bitwise unsigned int
     converters.

   - bpo-32962(4): python-gdb now catches ‘UnicodeDecodeError’
     exceptions when calling ‘string()’.

   - bpo-32962(5): python-gdb now catches ValueError on read_var(): when
     Python has no debug symbols for example.

   - bpo-33189(6): ‘pygettext.py’ now recognizes only literal strings as
     docstrings and translatable strings, and rejects bytes literals and
     f-string expressions.

   - bpo-31920(7): Fixed handling directories as arguments in the
     ‘pygettext’ script.  Based on patch by Oleg Krasnikov.

   - bpo-29673(8): Fix pystackv and pystack gdbinit macros.

   - bpo-25427(9): Remove the pyvenv script in favor of ‘python3 -m
     venv’ in order to lower confusion as to what Python interpreter a
     virtual environment will be created for.

   - bpo-32885(10): Add an ‘-n’ flag for ‘Tools/scripts/pathfix.py’ to
     disable automatic backup creation (files with ‘~’ suffix).

   - bpo-32222(11): Fix pygettext not extracting docstrings for
     functions with type annotated arguments.  Patch by Toby Harradine.

   - bpo-31583(12): Fix 2to3 for using with -add-suffix option but
     without -output-dir option for relative path to files in current
     directory.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35884

   (2) https://bugs.python.org/issue?@action=redirect&bpo=34989

   (3) https://bugs.python.org/issue?@action=redirect&bpo=20260

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32962

   (5) https://bugs.python.org/issue?@action=redirect&bpo=32962

   (6) https://bugs.python.org/issue?@action=redirect&bpo=33189

   (7) https://bugs.python.org/issue?@action=redirect&bpo=31920

   (8) https://bugs.python.org/issue?@action=redirect&bpo=29673

   (9) https://bugs.python.org/issue?@action=redirect&bpo=25427

   (10) https://bugs.python.org/issue?@action=redirect&bpo=32885

   (11) https://bugs.python.org/issue?@action=redirect&bpo=32222

   (12) https://bugs.python.org/issue?@action=redirect&bpo=31583


File: python.info,  Node: C API<46>,  Prev: Tools/Demos<23>,  Up: Python 3 8 0 alpha 1

1.23.49.11 C API
................

   - bpo-35713(1): The ‘PyByteArray_Init()’ and ‘PyByteArray_Fini()’
     functions have been removed.  They did nothing since Python 2.7.4
     and Python 3.2.0, were excluded from the limited API (stable ABI),
     and were not documented.

   - bpo-33817(2): Fixed *note _PyBytes_Resize(): 1548. for empty bytes
     objects.

   - bpo-35322(3): Fix memory leak in *note PyUnicode_EncodeLocale():
     b71. and *note PyUnicode_EncodeFSDefault(): 1957. on error
     handling.

   - bpo-35059(4): The following C macros have been converted to static
     inline functions: *note Py_INCREF(): 514, *note Py_DECREF(): 515,
     *note Py_XINCREF(): a08, *note Py_XDECREF(): 733,
     ‘PyObject_INIT()’, ‘PyObject_INIT_VAR()’.

   - bpo-35296(5): ‘make install’ now also installs the internal API:
     ‘Include/internal/*.h’ header files.

   - bpo-35081(6): Internal APIs surrounded by ‘#ifdef Py_BUILD_CORE’
     have been moved from ‘Include/*.h’ headers to new header files
     ‘Include/internal/pycore_*.h’.

   - bpo-35259(7): Conditionally declare *note Py_FinalizeEx(): cbc.
     (new in 3.6) based on Py_LIMITED_API. Patch by Arthur Neufeld.

   - bpo-35081(8): The ‘_PyObject_GC_TRACK()’ and
     ‘_PyObject_GC_UNTRACK()’ macros have been removed from the public C
     API.

   - bpo-35134(9): Creation of a new ‘Include/cpython/’ subdirectory.

   - bpo-34725(10): Adds _Py_SetProgramFullPath so embedders may
     override sys.executable

   - bpo-34910(11): Ensure that *note PyObject_Print(): 14e4. always
     returns ‘-1’ on error.  Patch by Zackery Spytz.

   - bpo-34523(12): Py_DecodeLocale() and Py_EncodeLocale() now use the
     UTF-8 encoding on Windows if Py_LegacyWindowsFSEncodingFlag is
     zero.

   - bpo-34193(13): Fix pluralization in TypeError messages in getargs.c
     and typeobject.c: '1 argument' instead of '1 arguments' and '1
     element' instead of '1 elements'.

   - bpo-34127(14): Return grammatically correct error message based on
     argument count.  Patch by Karthikeyan Singaravelan.

   - bpo-23927(15): Fixed *note SystemError: 51b. in *note
     PyArg_ParseTupleAndKeywords(): 2e9. when the ‘w*’ format unit is
     used for optional parameter.

   - bpo-32455(16): Added ‘PyCompile_OpcodeStackEffectWithJump()’.

   - bpo-34008(17): Py_Main() can again be called after Py_Initialize(),
     as in Python 3.6.

   - bpo-32500(18): Fixed error messages for *note PySequence_Size():
     1958, *note PySequence_GetItem(): 1959, *note PySequence_SetItem():
     195a. and *note PySequence_DelItem(): 195b. called with a mapping
     and *note PyMapping_Size(): 195c. called with a sequence.

   - bpo-33818(19): ‘PyExceptionClass_Name()’ will now return ‘const
     char *’ instead of ‘char *’.

   - bpo-33042(20): Embedding applications may once again call
     PySys_ResetWarnOptions, PySys_AddWarnOption, and PySys_AddXOption
     prior to calling Py_Initialize.

   - bpo-32374(21): Document that m_traverse for multi-phase initialized
     modules can be called with m_state=NULL, and add a sanity check

   - bpo-30863(22): *note PyUnicode_AsWideChar(): 195d. and *note
     PyUnicode_AsWideCharString(): 861. no longer cache the ‘wchar_t*’
     representation of string objects.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=35713

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33817

   (3) https://bugs.python.org/issue?@action=redirect&bpo=35322

   (4) https://bugs.python.org/issue?@action=redirect&bpo=35059

   (5) https://bugs.python.org/issue?@action=redirect&bpo=35296

   (6) https://bugs.python.org/issue?@action=redirect&bpo=35081

   (7) https://bugs.python.org/issue?@action=redirect&bpo=35259

   (8) https://bugs.python.org/issue?@action=redirect&bpo=35081

   (9) https://bugs.python.org/issue?@action=redirect&bpo=35134

   (10) https://bugs.python.org/issue?@action=redirect&bpo=34725

   (11) https://bugs.python.org/issue?@action=redirect&bpo=34910

   (12) https://bugs.python.org/issue?@action=redirect&bpo=34523

   (13) https://bugs.python.org/issue?@action=redirect&bpo=34193

   (14) https://bugs.python.org/issue?@action=redirect&bpo=34127

   (15) https://bugs.python.org/issue?@action=redirect&bpo=23927

   (16) https://bugs.python.org/issue?@action=redirect&bpo=32455

   (17) https://bugs.python.org/issue?@action=redirect&bpo=34008

   (18) https://bugs.python.org/issue?@action=redirect&bpo=32500

   (19) https://bugs.python.org/issue?@action=redirect&bpo=33818

   (20) https://bugs.python.org/issue?@action=redirect&bpo=33042

   (21) https://bugs.python.org/issue?@action=redirect&bpo=32374

   (22) https://bugs.python.org/issue?@action=redirect&bpo=30863


File: python.info,  Node: Python 3 7 0 final,  Next: Python 3 7 0 release candidate 1,  Prev: Python 3 8 0 alpha 1,  Up: Changelog（更動日誌）

1.23.50 Python 3.7.0 final
--------------------------

'Release date: 2018-06-27'

* Menu:

* Library: Library<49>.
* C API: C API<47>.


File: python.info,  Node: Library<49>,  Next: C API<47>,  Up: Python 3 7 0 final

1.23.50.1 Library
.................

   - bpo-33851(1): Fix *note ast.get_docstring(): 1960. for a node that
     lacks a docstring.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33851


File: python.info,  Node: C API<47>,  Prev: Library<49>,  Up: Python 3 7 0 final

1.23.50.2 C API
...............

   - bpo-33932(1): Calling Py_Initialize() twice does nothing, instead
     of failing with a fatal error: restore the Python 3.6 behaviour.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33932


File: python.info,  Node: Python 3 7 0 release candidate 1,  Next: Python 3 7 0 beta 5,  Prev: Python 3 7 0 final,  Up: Changelog（更動日誌）

1.23.51 Python 3.7.0 release candidate 1
----------------------------------------

'Release date: 2018-06-12'

* Menu:

* Core and Builtins: Core and Builtins<50>.
* Library: Library<50>.
* Documentation: Documentation<44>.
* Build: Build<48>.
* Windows: Windows<44>.
* IDLE: IDLE<36>.


File: python.info,  Node: Core and Builtins<50>,  Next: Library<50>,  Up: Python 3 7 0 release candidate 1

1.23.51.1 Core and Builtins
...........................

   - bpo-33803(1): Fix a crash in hamt.c caused by enabling GC tracking
     for an object that hadn't all of its fields set to NULL.

   - bpo-33706(2): Fix a crash in Python initialization when parsing the
     command line options.  Thanks Christoph Gohlke for the bug report
     and the fix!

   - bpo-30654(3): Fixed reset of the SIGINT handler to SIG_DFL on
     interpreter shutdown even when there was a custom handler set
     previously.  Patch by Philipp Kerling.

   - bpo-31849(4): Fix signed/unsigned comparison warning in pyhash.c.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33803

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33706

   (3) https://bugs.python.org/issue?@action=redirect&bpo=30654

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31849


File: python.info,  Node: Library<50>,  Next: Documentation<44>,  Prev: Core and Builtins<50>,  Up: Python 3 7 0 release candidate 1

1.23.51.2 Library
.................

   - bpo-30167(1): Prevent site.main() exception if PYTHONSTARTUP is
     set.  Patch by Steve Weber.

   - bpo-33812(2): Datetime instance d with non-None tzinfo, but with
     d.tzinfo.utcoffset(d) returning None is now treated as naive by the
     astimezone() method.

   - bpo-30805(3): Avoid race condition with debug logging

   - bpo-33694(4): asyncio: Fix a race condition causing data loss on
     pause_reading()/resume_reading() when using the ProactorEventLoop.

   - bpo-32493(5): Correct test for ‘uuid_enc_be’ availability in
     ‘configure.ac’.  Patch by Michael Felt.

   - bpo-33792(6): Add asyncio.WindowsSelectorEventLoopPolicy and
     asyncio.WindowsProactorEventLoopPolicy.

   - bpo-33778(7): Update ‘unicodedata’'s database to Unicode version
     11.0.0.

   - bpo-33770(8): improve base64 exception message for encoded inputs
     of invalid length

   - bpo-33769(9): asyncio/start_tls: Fix error message; cancel
     callbacks in case of an unhandled error; mark SSLTransport as
     closed if it is aborted.

   - bpo-33767(10): The concatenation (‘+’) and repetition (‘*’)
     sequence operations now raise *note TypeError: 4dd. instead of
     *note SystemError: 51b. when performed on *note mmap.mmap: 1f0.
     objects.  Patch by Zackery Spytz.

   - bpo-33734(11): asyncio/ssl: Fix AttributeError, increase default
     handshake timeout

   - bpo-11874(12): Use a better regex when breaking usage into
     wrappable parts.  Avoids bogus assertion errors from custom metavar
     strings.

   - bpo-33582(13): Emit a deprecation warning for inspect.formatargspec

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30167

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33812

   (3) https://bugs.python.org/issue?@action=redirect&bpo=30805

   (4) https://bugs.python.org/issue?@action=redirect&bpo=33694

   (5) https://bugs.python.org/issue?@action=redirect&bpo=32493

   (6) https://bugs.python.org/issue?@action=redirect&bpo=33792

   (7) https://bugs.python.org/issue?@action=redirect&bpo=33778

   (8) https://bugs.python.org/issue?@action=redirect&bpo=33770

   (9) https://bugs.python.org/issue?@action=redirect&bpo=33769

   (10) https://bugs.python.org/issue?@action=redirect&bpo=33767

   (11) https://bugs.python.org/issue?@action=redirect&bpo=33734

   (12) https://bugs.python.org/issue?@action=redirect&bpo=11874

   (13) https://bugs.python.org/issue?@action=redirect&bpo=33582


File: python.info,  Node: Documentation<44>,  Next: Build<48>,  Prev: Library<50>,  Up: Python 3 7 0 release candidate 1

1.23.51.3 Documentation
.......................

   - bpo-33409(1): Clarified the relationship between PEP 538(2)'s
     PYTHONCOERCECLOCALE and PEP 540's PYTHONUTF8 mode.

   - bpo-33736(3): Improve the documentation of *note
     asyncio.open_connection(): abb, *note asyncio.start_server(): abc.
     and their UNIX socket counterparts.

   - bpo-31432(4): Clarify meaning of CERT_NONE, CERT_OPTIONAL, and
     CERT_REQUIRED flags for ssl.SSLContext.verify_mode.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33409

   (2) https://peps.python.org/pep-0538/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=33736

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31432


File: python.info,  Node: Build<48>,  Next: Windows<44>,  Prev: Documentation<44>,  Up: Python 3 7 0 release candidate 1

1.23.51.4 Build
...............

   - bpo-5755(1): Move ‘-Wstrict-prototypes’ option to ‘CFLAGS_NODIST’
     from ‘OPT’.  This option emitted annoying warnings when building
     extension modules written in C++.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=5755


File: python.info,  Node: Windows<44>,  Next: IDLE<36>,  Prev: Build<48>,  Up: Python 3 7 0 release candidate 1

1.23.51.5 Windows
.................

   - bpo-33720(1): Reduces maximum marshal recursion depth on release
     builds.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33720


File: python.info,  Node: IDLE<36>,  Prev: Windows<44>,  Up: Python 3 7 0 release candidate 1

1.23.51.6 IDLE
..............

   - bpo-33656(1): On Windows, add API call saying that tk scales for
     DPI. On Windows 8.1+ or 10, with DPI compatibility properties of
     the Python binary unchanged, and a monitor resolution greater than
     96 DPI, this should make text and lines sharper.  It should
     otherwise have no effect.

   - bpo-33768(2): Clicking on a context line moves that line to the top
     of the editor window.

   - bpo-33763(3): IDLE: Use read-only text widget for code context
     instead of label widget.

   - bpo-33664(4): Scroll IDLE editor text by lines.  Previously, the
     mouse wheel and scrollbar slider moved text by a fixed number of
     pixels, resulting in partial lines at the top of the editor box.
     The change also applies to the shell and grep output windows, but
     not to read-only text views.

   - bpo-33679(5): Enable theme-specific color configuration for Code
     Context.  Use the Highlights tab to see the setting for built-in
     themes or add settings to custom themes.

   - bpo-33642(6): Display up to maxlines non-blank lines for Code
     Context.  If there is no current context, show a single blank line.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33656

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33768

   (3) https://bugs.python.org/issue?@action=redirect&bpo=33763

   (4) https://bugs.python.org/issue?@action=redirect&bpo=33664

   (5) https://bugs.python.org/issue?@action=redirect&bpo=33679

   (6) https://bugs.python.org/issue?@action=redirect&bpo=33642


File: python.info,  Node: Python 3 7 0 beta 5,  Next: Python 3 7 0 beta 4,  Prev: Python 3 7 0 release candidate 1,  Up: Changelog（更動日誌）

1.23.52 Python 3.7.0 beta 5
---------------------------

'Release date: 2018-05-30'

* Menu:

* Core and Builtins: Core and Builtins<51>.
* Library: Library<51>.
* Documentation: Documentation<45>.
* Tests: Tests<46>.
* Build: Build<49>.
* macOS: macOS<36>.
* IDLE: IDLE<37>.


File: python.info,  Node: Core and Builtins<51>,  Next: Library<51>,  Up: Python 3 7 0 beta 5

1.23.52.1 Core and Builtins
...........................

   - bpo-33622(1): Fixed a leak when the garbage collector fails to add
     an object with the ‘__del__’ method or referenced by it into the
     *note gc.garbage: 1159. list.  *note PyGC_Collect(): 932. can now
     be called when an exception is set and preserves it.

   - bpo-33509(2): Fix module_globals parameter of
     warnings.warn_explicit(): don't crash if module_globals is not a
     dict.

   - bpo-20104(3): The new ‘os.posix_spawn’ added in 3.7.0b1 was removed
     as we are still working on what the API should look like.  Expect
     this in 3.8 instead.

   - bpo-33475(4): Fixed miscellaneous bugs in converting annotations to
     strings and optimized parentheses in the string representation.

   - bpo-33391(5): Fix a leak in set_symmetric_difference().

   - bpo-28055(6): Fix unaligned accesses in siphash24().  Patch by Rolf
     Eike Beer.

   - bpo-32911(7): Due to unexpected compatibility issues discovered
     during downstream beta testing, reverted bpo-29463(8).  ‘docstring’
     field is removed from Module, ClassDef, FunctionDef, and
     AsyncFunctionDef ast nodes which was added in 3.7a1.  Docstring
     expression is restored as a first statement in their body.  Based
     on patch by Inada Naoki.

   - bpo-21983(9): Fix a crash in ‘ctypes.cast()’ in case the type
     argument is a ctypes structured data type.  Patch by Eryk Sun and
     Oren Milman.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33622

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33509

   (3) https://bugs.python.org/issue?@action=redirect&bpo=20104

   (4) https://bugs.python.org/issue?@action=redirect&bpo=33475

   (5) https://bugs.python.org/issue?@action=redirect&bpo=33391

   (6) https://bugs.python.org/issue?@action=redirect&bpo=28055

   (7) https://bugs.python.org/issue?@action=redirect&bpo=32911

   (8) https://bugs.python.org/issue?@action=redirect&bpo=29463

   (9) https://bugs.python.org/issue?@action=redirect&bpo=21983


File: python.info,  Node: Library<51>,  Next: Documentation<45>,  Prev: Core and Builtins<51>,  Up: Python 3 7 0 beta 5

1.23.52.2 Library
.................

   - bpo-32751(1): When cancelling the task due to a timeout, *note
     asyncio.wait_for(): 5a4. will now wait until the cancellation is
     complete.

   - bpo-32684(2): Fix gather to propagate cancellation of itself even
     with return_exceptions.

   - bpo-33654(3): Support protocol type switching in
     SSLTransport.set_protocol().

   - bpo-33674(4): Pause the transport as early as possible to further
     reduce the risk of data_received() being called before
     connection_made().

   - bpo-33674(5): Fix a race condition in SSLProtocol.connection_made()
     of asyncio.sslproto: start immediately the handshake instead of
     using call_soon().  Previously, data_received() could be called
     before the handshake started, causing the handshake to hang or
     fail.

   - bpo-31647(6): Fixed bug where calling write_eof() on a
     _SelectorSocketTransport after it's already closed raises
     AttributeError.

   - bpo-32610(7): Make asyncio.all_tasks() return only pending tasks.

   - bpo-32410(8): Avoid blocking on file IO in sendfile fallback code

   - bpo-33469(9): Fix RuntimeError after closing loop that used
     run_in_executor

   - bpo-33672(10): Fix Task.__repr__ crash with Cython's bogus
     coroutines

   - bpo-33654(11): Fix transport.set_protocol() to support switching
     between asyncio.Protocol and asyncio.BufferedProtocol.  Fix
     loop.start_tls() to work with asyncio.BufferedProtocols.

   - bpo-33652(12): Pickles of type variables and subscripted generics
     are now future-proof and compatible with older Python versions.

   - bpo-32493(13): Fixed *note uuid.uuid1(): b4f. on FreeBSD.

   - bpo-33618(14): Finalize and document preliminary and experimental
     TLS 1.3 support with OpenSSL 1.1.1

   - bpo-33623(15): Fix possible SIGSGV when asyncio.Future is created
     in __del__

   - bpo-30877(16): Fixed a bug in the Python implementation of the JSON
     decoder that prevented the cache of parsed strings from clearing
     after finishing the decoding.  Based on patch by c-fos.

   - bpo-33570(17): Change TLS 1.3 cipher suite settings for
     compatibility with OpenSSL 1.1.1-pre6 and newer.  OpenSSL 1.1.1
     will have TLS 1.3 ciphers enabled by default.

   - bpo-28556(18): Do not simplify arguments to ‘typing.Union’.  Now
     ‘Union[Manager, Employee]’ is not simplified to ‘Employee’ at
     runtime.  Such simplification previously caused several bugs and
     limited possibilities for introspection.

   - bpo-33540(19): Add a new ‘block_on_close’ class attribute to
     ‘ForkingMixIn’ and ‘ThreadingMixIn’ classes of *note socketserver:
     b9.

   - bpo-33548(20): tempfile._candidate_tempdir_list should consider
     common TEMP locations

   - bpo-33109(21): argparse subparsers are once again not required by
     default, reverting the change in behavior introduced by
     bpo-26510(22) in 3.7.0a2.

   - bpo-33536(23): dataclasses.make_dataclass now checks for invalid
     field names and duplicate fields.  Also, added a check for invalid
     field specifications.

   - bpo-33542(24): Prevent ‘uuid.get_node’ from using a DUID instead of
     a MAC on Windows.  Patch by Zvi Effron

   - bpo-26819(25): Fix race condition with
     ‘ReadTransport.resume_reading’ in Windows proactor event loop.

   - Fix failure in ‘typing.get_type_hints()’ when ClassVar was provided
     as a string forward reference.

   - bpo-33505(26): Optimize asyncio.ensure_future() by reordering if
     checks: 1.17x faster.

   - bpo-33497(27): Add errors param to cgi.parse_multipart and make an
     encoding in FieldStorage use the given errors (needed for Twisted).
     Patch by Amber Brown.

   - bpo-33495(28): Change dataclasses.Fields repr to use the repr of
     each of its members, instead of str.  This makes it more clear what
     each field actually represents.  This is especially true for the
     'type' member.

   - bpo-33453(29): Fix dataclasses to work if using literal string type
     annotations or if using PEP 563 "Postponed Evaluation of
     Annotations".  Only specific string prefixes are detected for both
     ClassVar ("ClassVar" and "typing.ClassVar") and InitVar ("InitVar"
     and "dataclasses.InitVar").

   - bpo-28556(30): Minor fixes in typing module: add annotations to
     ‘NamedTuple.__new__’, pass ‘*args’ and ‘**kwds’ in
     ‘Generic.__new__’.  Original PRs by Paulius Šarka and Chad
     Dombrova.

   - bpo-20087(31): Updated alias mapping with glibc 2.27 supported
     locales.

   - bpo-33422(32): Fix trailing quotation marks getting deleted when
     looking up byte/string literals on pydoc.  Patch by Andrés Delfino.

   - bpo-28167(33): The function ‘platform.linux_distribution’ and
     ‘platform.dist’ now trigger a ‘DeprecationWarning’ and have been
     marked for removal in Python 3.8

   - bpo-33197(34): Update error message when constructing invalid
     inspect.Parameters Patch by Donghee Na.

   - bpo-33263(35): Fix FD leak in ‘_SelectorSocketTransport’ Patch by
     Vlad Starostin.

   - bpo-32861(36): The urllib.robotparser's ‘__str__’ representation
     now includes wildcard entries and the "Crawl-delay" and
     "Request-rate" fields.  Patch by Michael Lazar.

   - bpo-32257(37): The ssl module now contains OP_NO_RENEGOTIATION
     constant, available with OpenSSL 1.1.0h or 1.1.1.

   - bpo-16865(38): Support arrays >=2GiB in *note ctypes: 22.  Patch by
     Segev Finer.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32751

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32684

   (3) https://bugs.python.org/issue?@action=redirect&bpo=33654

   (4) https://bugs.python.org/issue?@action=redirect&bpo=33674

   (5) https://bugs.python.org/issue?@action=redirect&bpo=33674

   (6) https://bugs.python.org/issue?@action=redirect&bpo=31647

   (7) https://bugs.python.org/issue?@action=redirect&bpo=32610

   (8) https://bugs.python.org/issue?@action=redirect&bpo=32410

   (9) https://bugs.python.org/issue?@action=redirect&bpo=33469

   (10) https://bugs.python.org/issue?@action=redirect&bpo=33672

   (11) https://bugs.python.org/issue?@action=redirect&bpo=33654

   (12) https://bugs.python.org/issue?@action=redirect&bpo=33652

   (13) https://bugs.python.org/issue?@action=redirect&bpo=32493

   (14) https://bugs.python.org/issue?@action=redirect&bpo=33618

   (15) https://bugs.python.org/issue?@action=redirect&bpo=33623

   (16) https://bugs.python.org/issue?@action=redirect&bpo=30877

   (17) https://bugs.python.org/issue?@action=redirect&bpo=33570

   (18) https://bugs.python.org/issue?@action=redirect&bpo=28556

   (19) https://bugs.python.org/issue?@action=redirect&bpo=33540

   (20) https://bugs.python.org/issue?@action=redirect&bpo=33548

   (21) https://bugs.python.org/issue?@action=redirect&bpo=33109

   (22) https://bugs.python.org/issue?@action=redirect&bpo=26510

   (23) https://bugs.python.org/issue?@action=redirect&bpo=33536

   (24) https://bugs.python.org/issue?@action=redirect&bpo=33542

   (25) https://bugs.python.org/issue?@action=redirect&bpo=26819

   (26) https://bugs.python.org/issue?@action=redirect&bpo=33505

   (27) https://bugs.python.org/issue?@action=redirect&bpo=33497

   (28) https://bugs.python.org/issue?@action=redirect&bpo=33495

   (29) https://bugs.python.org/issue?@action=redirect&bpo=33453

   (30) https://bugs.python.org/issue?@action=redirect&bpo=28556

   (31) https://bugs.python.org/issue?@action=redirect&bpo=20087

   (32) https://bugs.python.org/issue?@action=redirect&bpo=33422

   (33) https://bugs.python.org/issue?@action=redirect&bpo=28167

   (34) https://bugs.python.org/issue?@action=redirect&bpo=33197

   (35) https://bugs.python.org/issue?@action=redirect&bpo=33263

   (36) https://bugs.python.org/issue?@action=redirect&bpo=32861

   (37) https://bugs.python.org/issue?@action=redirect&bpo=32257

   (38) https://bugs.python.org/issue?@action=redirect&bpo=16865


File: python.info,  Node: Documentation<45>,  Next: Tests<46>,  Prev: Library<51>,  Up: Python 3 7 0 beta 5

1.23.52.3 Documentation
.......................

   - bpo-23859(1): Document that ‘asyncio.wait()’ does not cancel its
     futures on timeout.

   - bpo-32436(2): Document PEP 567(3) changes to asyncio.

   - bpo-33604(4): Update HMAC md5 default to a DeprecationWarning, bump
     removal to 3.8.

   - bpo-33503(5): Fix broken pypi link

   - bpo-33421(6): Add missing documentation for
     ‘typing.AsyncContextManager’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23859

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32436

   (3) https://peps.python.org/pep-0567/

   (4) https://bugs.python.org/issue?@action=redirect&bpo=33604

   (5) https://bugs.python.org/issue?@action=redirect&bpo=33503

   (6) https://bugs.python.org/issue?@action=redirect&bpo=33421


File: python.info,  Node: Tests<46>,  Next: Build<49>,  Prev: Documentation<45>,  Up: Python 3 7 0 beta 5

1.23.52.4 Tests
...............

   - bpo-33655(1): Ignore test_posix_fallocate failures on BSD platforms
     that might be due to running on ZFS.

   - bpo-32604(2): Remove the _xxsubinterpreters module (meant for
     testing) and associated helpers.  This module was originally added
     recently in 3.7b1.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33655

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32604


File: python.info,  Node: Build<49>,  Next: macOS<36>,  Prev: Tests<46>,  Up: Python 3 7 0 beta 5

1.23.52.5 Build
...............

   - bpo-33614(1): Ensures module definition files for the stable ABI on
     Windows are correctly regenerated.

   - bpo-33522(2): Enable CI builds on Visual Studio Team Services at
     ‘https://python.visualstudio.com/cpython’

   - bpo-33012(3): Add ‘-Wno-cast-function-type’ for gcc 8 for silencing
     warnings about function casts like casting to PyCFunction in method
     definition lists.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33614

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33522

   (3) https://bugs.python.org/issue?@action=redirect&bpo=33012


File: python.info,  Node: macOS<36>,  Next: IDLE<37>,  Prev: Build<49>,  Up: Python 3 7 0 beta 5

1.23.52.6 macOS
...............

   - bpo-13631(1): The .editrc file in user's home directory is now
     processed correctly during the readline initialization through
     editline emulation on macOS.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=13631


File: python.info,  Node: IDLE<37>,  Prev: macOS<36>,  Up: Python 3 7 0 beta 5

1.23.52.7 IDLE
..............

   - bpo-33628(1): IDLE: Cleanup codecontext.py and its test.

   - bpo-33564(2): IDLE's code context now recognizes async as a block
     opener.

   - bpo-32831(3): Add docstrings and tests for codecontext.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33628

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33564

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32831


File: python.info,  Node: Python 3 7 0 beta 4,  Next: Python 3 7 0 beta 3,  Prev: Python 3 7 0 beta 5,  Up: Changelog（更動日誌）

1.23.53 Python 3.7.0 beta 4
---------------------------

'Release date: 2018-05-02'

* Menu:

* Core and Builtins: Core and Builtins<52>.
* Library: Library<52>.
* Documentation: Documentation<46>.
* Tests: Tests<47>.
* Build: Build<50>.
* Windows: Windows<45>.
* macOS: macOS<37>.
* IDLE: IDLE<38>.
* Tools/Demos: Tools/Demos<24>.


File: python.info,  Node: Core and Builtins<52>,  Next: Library<52>,  Up: Python 3 7 0 beta 4

1.23.53.1 Core and Builtins
...........................

   - bpo-33363(1): Raise a SyntaxError for ‘async with’ and ‘async for’
     statements outside of async functions.

   - bpo-33128(2): Fix a bug that causes PathFinder to appear twice on
     sys.meta_path.  Patch by Pablo Galindo Salgado.

   - bpo-33312(3): Fixed clang ubsan (undefined behavior sanitizer)
     warnings in dictobject.c by adjusting how the internal struct
     _dictkeysobject shared keys structure is declared.

   - bpo-33231(4): Fix potential memory leak in ‘normalizestring()’.

   - bpo-33205(5): Change dict growth function from
     ‘round_up_to_power_2(used*2+hashtable_size/2)’ to
     ‘round_up_to_power_2(used*3)’.  Previously, dict is shrinked only
     when ‘used == 0’.  Now dict has more chance to be shrinked.

   - bpo-29922(6): Improved error messages in 'async with' when
     ‘__aenter__()’ or ‘__aexit__()’ return non-awaitable object.

   - bpo-33199(7): Fix ‘ma_version_tag’ in dict implementation is
     uninitialized when copying from key-sharing dict.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33363

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33128

   (3) https://bugs.python.org/issue?@action=redirect&bpo=33312

   (4) https://bugs.python.org/issue?@action=redirect&bpo=33231

   (5) https://bugs.python.org/issue?@action=redirect&bpo=33205

   (6) https://bugs.python.org/issue?@action=redirect&bpo=29922

   (7) https://bugs.python.org/issue?@action=redirect&bpo=33199


File: python.info,  Node: Library<52>,  Next: Documentation<46>,  Prev: Core and Builtins<52>,  Up: Python 3 7 0 beta 4

1.23.53.2 Library
.................

   - bpo-33281(1): Fix ctypes.util.find_library regression on macOS.

   - bpo-33383(2): Fixed crash in the get() method of the *note
     dbm.ndbm: 2c. database object when it is called with a single
     argument.

   - bpo-33329(3): Fix multiprocessing regression on newer glibcs

   - bpo-991266(4): Fix quoting of the ‘Comment’ attribute of *note
     http.cookies.SimpleCookie: 1949.

   - bpo-33131(5): Upgrade bundled version of pip to 10.0.1.

   - bpo-33308(6): Fixed a crash in the ‘parser’ module when converting
     an ST object to a tree of tuples or lists with ‘line_info=False’
     and ‘col_info=True’.

   - bpo-33266(7): lib2to3 now recognizes ‘rf'...'’ strings.

   - bpo-11594(8): Ensure line-endings are respected when using lib2to3.

   - bpo-33254(9): Have *note importlib.resources.contents(): 1d7. and
     *note importlib.abc.ResourceReader.contents(): 194a. return an
     *note iterable: 11bf. instead of an *note iterator: 192.

   - bpo-33256(10): Fix display of ‘<module>’ call in the html produced
     by ‘cgitb.html()’.  Patch by Stéphane Blondon.

   - bpo-33185(11): Fixed regression when running pydoc with the *note
     -m: 585. switch.  (The regression was introduced in 3.7.0b3 by the
     resolution of bpo-33053(12)) This fix also changed pydoc to add
     ‘os.getcwd()’ to *note sys.path: 37f. when necessary, rather than
     adding ‘"."’.

   - bpo-33169(13): Delete entries of ‘None’ in *note
     sys.path_importer_cache: 588. when
     ‘importlib.machinery.invalidate_caches()’ is called.

   - bpo-33217(14): Deprecate looking up non-Enum objects in Enum
     classes and Enum members (will raise *note TypeError: 4dd. in
     3.8+).

   - bpo-33203(15): ‘random.Random.choice()’ now raises ‘IndexError’ for
     empty sequences consistently even when called from subclasses
     without a ‘getrandbits()’ implementation.

   - bpo-33224(16): Update difflib.mdiff() for PEP 479(17).  Convert an
     uncaught StopIteration in a generator into a return-statement.

   - bpo-33209(18): End framing at the end of C implementation of *note
     pickle.Pickler.dump(): 194b.

   - bpo-20104(19): Improved error handling and fixed a reference leak
     in *note os.posix_spawn(): 205.

   - bpo-33175(20): In dataclasses, Field.__set_name__ now looks up the
     __set_name__ special method on the class, not the instance, of the
     default value.

   - bpo-33097(21): Raise RuntimeError when ‘executor.submit’ is called
     during interpreter shutdown.

   - bpo-31908(22): Fix output of cover files for ‘trace’ module
     command-line tool.  Previously emitted cover files only when
     ‘--missing’ option was used.  Patch by Michael Selik.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33281

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33383

   (3) https://bugs.python.org/issue?@action=redirect&bpo=33329

   (4) https://bugs.python.org/issue?@action=redirect&bpo=991266

   (5) https://bugs.python.org/issue?@action=redirect&bpo=33131

   (6) https://bugs.python.org/issue?@action=redirect&bpo=33308

   (7) https://bugs.python.org/issue?@action=redirect&bpo=33266

   (8) https://bugs.python.org/issue?@action=redirect&bpo=11594

   (9) https://bugs.python.org/issue?@action=redirect&bpo=33254

   (10) https://bugs.python.org/issue?@action=redirect&bpo=33256

   (11) https://bugs.python.org/issue?@action=redirect&bpo=33185

   (12) https://bugs.python.org/issue?@action=redirect&bpo=33053

   (13) https://bugs.python.org/issue?@action=redirect&bpo=33169

   (14) https://bugs.python.org/issue?@action=redirect&bpo=33217

   (15) https://bugs.python.org/issue?@action=redirect&bpo=33203

   (16) https://bugs.python.org/issue?@action=redirect&bpo=33224

   (17) https://peps.python.org/pep-0479/

   (18) https://bugs.python.org/issue?@action=redirect&bpo=33209

   (19) https://bugs.python.org/issue?@action=redirect&bpo=20104

   (20) https://bugs.python.org/issue?@action=redirect&bpo=33175

   (21) https://bugs.python.org/issue?@action=redirect&bpo=33097

   (22) https://bugs.python.org/issue?@action=redirect&bpo=31908


File: python.info,  Node: Documentation<46>,  Next: Tests<47>,  Prev: Library<52>,  Up: Python 3 7 0 beta 4

1.23.53.3 Documentation
.......................

   - bpo-33378(1): Add Korean language switcher for
     ‘https://docs.python.org/3/’

   - bpo-33276(2): Clarify that the ‘__path__’ attribute on modules
     cannot be just any value.

   - bpo-33201(3): Modernize documentation for writing C extension
     types.

   - bpo-33195(4): Deprecate ‘Py_UNICODE’ usage in ‘c-api/arg’ document.
     ‘Py_UNICODE’ related APIs are deprecated since Python 3.3, but it
     is missed in the document.

   - bpo-8243(5): Add a note about curses.addch and curses.addstr
     exception behavior when writing outside a window, or pad.

   - bpo-32337(6): Update documentation related with ‘dict’ order.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33378

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33276

   (3) https://bugs.python.org/issue?@action=redirect&bpo=33201

   (4) https://bugs.python.org/issue?@action=redirect&bpo=33195

   (5) https://bugs.python.org/issue?@action=redirect&bpo=8243

   (6) https://bugs.python.org/issue?@action=redirect&bpo=32337


File: python.info,  Node: Tests<47>,  Next: Build<50>,  Prev: Documentation<46>,  Up: Python 3 7 0 beta 4

1.23.53.4 Tests
...............

   - bpo-33358(1): Fix
     ‘test_embed.test_pre_initialization_sys_options()’ when the
     interpreter is built with ‘--enable-shared’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33358


File: python.info,  Node: Build<50>,  Next: Windows<45>,  Prev: Tests<47>,  Up: Python 3 7 0 beta 4

1.23.53.5 Build
...............

   - bpo-33394(1): Enable the verbose build for extension modules, when
     GNU make is passed macros on the command line.

   - bpo-33393(2): Update config.guess and config.sub files.

   - bpo-33377(3): Add new triplets for mips r6 and riscv variants (used
     in extension suffixes).

   - bpo-32232(4): By default, modules configured in ‘Modules/Setup’ are
     no longer built with ‘-DPy_BUILD_CORE’.  Instead, modules that
     specifically need that preprocessor definition include it in their
     individual entries.

   - bpo-33182(5): The embedding tests can once again be built with
     clang 6.0

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33394

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33393

   (3) https://bugs.python.org/issue?@action=redirect&bpo=33377

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32232

   (5) https://bugs.python.org/issue?@action=redirect&bpo=33182


File: python.info,  Node: Windows<45>,  Next: macOS<37>,  Prev: Build<50>,  Up: Python 3 7 0 beta 4

1.23.53.6 Windows
.................

   - bpo-33184(1): Update Windows installer to use OpenSSL 1.1.0h.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33184


File: python.info,  Node: macOS<37>,  Next: IDLE<38>,  Prev: Windows<45>,  Up: Python 3 7 0 beta 4

1.23.53.7 macOS
...............

   - bpo-33184(1): Update macOS installer build to use OpenSSL 1.1.0h.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33184


File: python.info,  Node: IDLE<38>,  Next: Tools/Demos<24>,  Prev: macOS<37>,  Up: Python 3 7 0 beta 4

1.23.53.8 IDLE
..............

   - bpo-21474(1): Update word/identifier definition from ascii to
     unicode.  In text and entry boxes, this affects selection by
     double-click, movement left/right by control-left/right, and
     deletion left/right by control-BACKSPACE/DEL.

   - bpo-33204(2): IDLE: consistently color invalid string prefixes.  A
     'u' string prefix cannot be paired with either 'r' or 'f'.
     Consistently color as much of the prefix, starting at the right, as
     is valid.  Revise and extend colorizer test.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21474

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33204


File: python.info,  Node: Tools/Demos<24>,  Prev: IDLE<38>,  Up: Python 3 7 0 beta 4

1.23.53.9 Tools/Demos
.....................

   - bpo-33189(1): ‘pygettext.py’ now recognizes only literal strings as
     docstrings and translatable strings, and rejects bytes literals and
     f-string expressions.

   - bpo-31920(2): Fixed handling directories as arguments in the
     ‘pygettext’ script.  Based on patch by Oleg Krasnikov.

   - bpo-29673(3): Fix pystackv and pystack gdbinit macros.

   - bpo-31583(4): Fix 2to3 for using with -add-suffix option but
     without -output-dir option for relative path to files in current
     directory.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33189

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31920

   (3) https://bugs.python.org/issue?@action=redirect&bpo=29673

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31583


File: python.info,  Node: Python 3 7 0 beta 3,  Next: Python 3 7 0 beta 2,  Prev: Python 3 7 0 beta 4,  Up: Changelog（更動日誌）

1.23.54 Python 3.7.0 beta 3
---------------------------

'Release date: 2018-03-29'

* Menu:

* Security: Security<34>.
* Core and Builtins: Core and Builtins<53>.
* Library: Library<53>.
* Documentation: Documentation<47>.
* Tests: Tests<48>.
* Build: Build<51>.
* Windows: Windows<46>.
* macOS: macOS<38>.
* IDLE: IDLE<39>.
* Tools/Demos: Tools/Demos<25>.
* C API: C API<48>.


File: python.info,  Node: Security<34>,  Next: Core and Builtins<53>,  Up: Python 3 7 0 beta 3

1.23.54.1 Security
..................

   - bpo-33136(1): Harden ssl module against LibreSSL CVE-2018-8970(2).
     X509_VERIFY_PARAM_set1_host() is called with an explicit namelen.
     A new test ensures that NULL bytes are not allowed.

   - bpo-33001(3): Minimal fix to prevent buffer overrun in os.symlink
     on Windows

   - bpo-32981(4): Regexes in difflib and poplib were vulnerable to
     catastrophic backtracking.  These regexes formed potential DOS
     vectors (REDOS). They have been refactored.  This resolves
     CVE-2018-1060(5) and CVE-2018-1061(6).  Patch by Jamie Davis.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33136

   (2) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8970

   (3) https://bugs.python.org/issue?@action=redirect&bpo=33001

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32981

   (5) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1060

   (6) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1061


File: python.info,  Node: Core and Builtins<53>,  Next: Library<53>,  Prev: Security<34>,  Up: Python 3 7 0 beta 3

1.23.54.2 Core and Builtins
...........................

   - bpo-33053(1): When using the -m switch, sys.path[0] is now
     explicitly expanded as the 'starting' working directory, rather
     than being left as the empty path (which allows imports from the
     current working directory at the time of the import)

   - bpo-33018(2): Improve consistency of errors raised by
     ‘issubclass()’ when called with a non-class and an abstract base
     class as the first and second arguments, respectively.  Patch by
     Josh Bronson.

   - bpo-33041(3): Fixed jumping when the function contains an ‘async
     for’ loop.

   - bpo-33026(4): Fixed jumping out of "with" block by setting
     f_lineno.

   - bpo-33005(5): Fix a crash on fork when using a custom memory
     allocator (ex: using PYTHONMALLOC env var).  _PyGILState_Reinit()
     and _PyInterpreterState_Enable() now use the default RAW memory
     allocator to allocate a new interpreters mutex on fork.

   - bpo-17288(6): Prevent jumps from 'return' and 'exception' trace
     events.

   - bpo-32836(7): Don't use temporary variables in cases of
     list/dict/set comprehensions

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33053

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33018

   (3) https://bugs.python.org/issue?@action=redirect&bpo=33041

   (4) https://bugs.python.org/issue?@action=redirect&bpo=33026

   (5) https://bugs.python.org/issue?@action=redirect&bpo=33005

   (6) https://bugs.python.org/issue?@action=redirect&bpo=17288

   (7) https://bugs.python.org/issue?@action=redirect&bpo=32836


File: python.info,  Node: Library<53>,  Next: Documentation<47>,  Prev: Core and Builtins<53>,  Up: Python 3 7 0 beta 3

1.23.54.3 Library
.................

   - bpo-33141(1): Have Field objects pass through __set_name__ to their
     default values, if they have their own __set_name__.

   - bpo-33096(2): Allow ttk.Treeview.insert to insert iid that has a
     false boolean value.  Note iid=0 and iid=False would be same.
     Patch by Garvit Khatri.

   - bpo-32873(3): Treat type variables and special typing forms as
     immutable by copy and pickle.  This fixes several minor issues and
     inconsistencies, and improves backwards compatibility with Python
     3.6.

   - bpo-33134(4): When computing dataclass's __hash__, use the lookup
     table to contain the function which returns the __hash__ value.
     This is an improvement over looking up a string, and then testing
     that string to see what to do.

   - bpo-33127(5): The ssl module now compiles with LibreSSL 2.7.1.

   - bpo-32505(6): Raise TypeError if a member variable of a dataclass
     is of type Field, but doesn't have a type annotation.

   - bpo-33078(7): Fix the failure on OSX caused by the tests relying on
     sem_getvalue

   - bpo-33116(8): Add 'Field' to dataclasses.__all__.

   - bpo-32896(9): Fix an error where subclassing a dataclass with a
     field that uses a default_factory would generate an incorrect
     class.

   - bpo-33100(10): Dataclasses: If a field has a default value that's a
     MemberDescriptorType, then it's from that field being in __slots__,
     not an actual default value.

   - bpo-32953(11): If a non-dataclass inherits from a frozen dataclass,
     allow attributes to be added to the derived class.  Only attributes
     from the frozen dataclass cannot be assigned to.  Require all
     dataclasses in a hierarchy to be either all frozen or all
     non-frozen.

   - bpo-33061(12): Add missing ‘NoReturn’ to ‘__all__’ in typing.py

   - bpo-33078(13): Fix the size handling in multiprocessing.Queue when
     a pickling error occurs.

   - bpo-33064(14): lib2to3 now properly supports trailing commas after
     ‘*args’ and ‘**kwargs’ in function signatures.

   - bpo-33056(15): FIX properly close leaking fds in
     concurrent.futures.ProcessPoolExecutor.

   - bpo-33021(16): Release the GIL during fstat() calls, avoiding hang
     of all threads when calling mmap.mmap(), os.urandom(), and
     random.seed().  Patch by Nir Soffer.

   - bpo-31804(17): Avoid failing in multiprocessing.Process if the
     standard streams are closed or None at exit.

   - bpo-33037(18): Skip sending/receiving data after SSL transport
     closing.

   - bpo-27683(19): Fix a regression in *note ipaddress: 74. that result
     of ‘hosts()’ is empty when the network is constructed by a tuple
     containing an integer mask and only 1 bit left for addresses.

   - bpo-32999(20): Fix C implementation of ‘ABC.__subclasscheck__(cls,
     subclass)’ crashed when ‘subclass’ is not a type object.

   - bpo-33009(21): Fix inspect.signature() for single-parameter
     partialmethods.

   - bpo-32969(22): Expose several missing constants in zlib and fix
     corresponding documentation.

   - bpo-32056(23): Improved exceptions raised for invalid number of
     channels and sample width when read an audio file in modules
     ‘aifc’, *note wave: fb. and ‘sunau’.

   - bpo-32844(24): Fix wrong redirection of a low descriptor (0 or 1)
     to stderr in subprocess if another low descriptor is closed.

   - bpo-32857(25): In *note tkinter: d9, ‘after_cancel(None)’ now
     raises a *note ValueError: 1e7. instead of canceling the first
     scheduled function.  Patch by Cheryl Sabella.

   - bpo-31639(26): http.server now exposes a ThreadedHTTPServer class
     and uses it when the module is run with ‘-m’ to cope with web
     browsers pre-opening sockets.

   - bpo-27645(27): *note sqlite3.Connection: 22a. now exposes a *note
     backup: b1e. method, if the underlying SQLite library is at version
     3.6.11 or higher.  Patch by Lele Gaifax.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33141

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33096

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32873

   (4) https://bugs.python.org/issue?@action=redirect&bpo=33134

   (5) https://bugs.python.org/issue?@action=redirect&bpo=33127

   (6) https://bugs.python.org/issue?@action=redirect&bpo=32505

   (7) https://bugs.python.org/issue?@action=redirect&bpo=33078

   (8) https://bugs.python.org/issue?@action=redirect&bpo=33116

   (9) https://bugs.python.org/issue?@action=redirect&bpo=32896

   (10) https://bugs.python.org/issue?@action=redirect&bpo=33100

   (11) https://bugs.python.org/issue?@action=redirect&bpo=32953

   (12) https://bugs.python.org/issue?@action=redirect&bpo=33061

   (13) https://bugs.python.org/issue?@action=redirect&bpo=33078

   (14) https://bugs.python.org/issue?@action=redirect&bpo=33064

   (15) https://bugs.python.org/issue?@action=redirect&bpo=33056

   (16) https://bugs.python.org/issue?@action=redirect&bpo=33021

   (17) https://bugs.python.org/issue?@action=redirect&bpo=31804

   (18) https://bugs.python.org/issue?@action=redirect&bpo=33037

   (19) https://bugs.python.org/issue?@action=redirect&bpo=27683

   (20) https://bugs.python.org/issue?@action=redirect&bpo=32999

   (21) https://bugs.python.org/issue?@action=redirect&bpo=33009

   (22) https://bugs.python.org/issue?@action=redirect&bpo=32969

   (23) https://bugs.python.org/issue?@action=redirect&bpo=32056

   (24) https://bugs.python.org/issue?@action=redirect&bpo=32844

   (25) https://bugs.python.org/issue?@action=redirect&bpo=32857

   (26) https://bugs.python.org/issue?@action=redirect&bpo=31639

   (27) https://bugs.python.org/issue?@action=redirect&bpo=27645


File: python.info,  Node: Documentation<47>,  Next: Tests<48>,  Prev: Library<53>,  Up: Python 3 7 0 beta 3

1.23.54.4 Documentation
.......................

   - bpo-33126(1): Document PyBuffer_ToContiguous().

   - bpo-27212(2): Modify documentation for the ‘islice()’ recipe to
     consume initial values up to the start index.

   - bpo-28247(3): Update *note zipapp: 116. documentation to describe
     how to make standalone applications.

   - bpo-18802(4): Documentation changes for ipaddress.  Patch by Jon
     Foster and Berker Peksag.

   - bpo-27428(5): Update documentation to clarify that
     ‘WindowsRegistryFinder’ implements ‘MetaPathFinder’.  (Patch by
     Himanshu Lakhara)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33126

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27212

   (3) https://bugs.python.org/issue?@action=redirect&bpo=28247

   (4) https://bugs.python.org/issue?@action=redirect&bpo=18802

   (5) https://bugs.python.org/issue?@action=redirect&bpo=27428


File: python.info,  Node: Tests<48>,  Next: Build<51>,  Prev: Documentation<47>,  Up: Python 3 7 0 beta 3

1.23.54.5 Tests
...............

   - bpo-32872(1): Avoid regrtest compatibility issue with namespace
     packages.

   - bpo-32517(2): Fix failing ‘test_asyncio’ on macOS 10.12.2+ due to
     transport of ‘KqueueSelector’ loop was not being closed.

   - bpo-19417(3): Add test_bdb.py.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32872

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32517

   (3) https://bugs.python.org/issue?@action=redirect&bpo=19417


File: python.info,  Node: Build<51>,  Next: Windows<46>,  Prev: Tests<48>,  Up: Python 3 7 0 beta 3

1.23.54.6 Build
...............

   - bpo-33163(1): Upgrade pip to 9.0.3 and setuptools to v39.0.1.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33163


File: python.info,  Node: Windows<46>,  Next: macOS<38>,  Prev: Build<51>,  Up: Python 3 7 0 beta 3

1.23.54.7 Windows
.................

   - bpo-33016(1): Fix potential use of uninitialized memory in
     nt._getfinalpathname

   - bpo-32903(2): Fix a memory leak in os.chdir() on Windows if the
     current directory is set to a UNC path.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33016

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32903


File: python.info,  Node: macOS<38>,  Next: IDLE<39>,  Prev: Windows<46>,  Up: Python 3 7 0 beta 3

1.23.54.8 macOS
...............

   - bpo-32726(1): Build and link with private copy of Tcl/Tk 8.6 for
     the macOS 10.6+ installer.  The 10.9+ installer variant already
     does this.  This means that the Python 3.7 provided by the
     python.org macOS installers no longer need or use any external
     versions of Tcl/Tk, either system-provided or user-installed, such
     as ActiveTcl.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32726


File: python.info,  Node: IDLE<39>,  Next: Tools/Demos<25>,  Prev: macOS<38>,  Up: Python 3 7 0 beta 3

1.23.54.9 IDLE
..............

   - bpo-32984(1): Set ‘__file__’ while running a startup file.  Like
     Python, IDLE optionally runs one startup file in the Shell window
     before presenting the first interactive input prompt.  For IDLE,
     ‘-s’ runs a file named in environmental variable ‘IDLESTARTUP’ or
     *note PYTHONSTARTUP: f6b.; ‘-r file’ runs ‘file’.  Python sets
     ‘__file__’ to the startup file name before running the file and
     unsets it before the first prompt.  IDLE now does the same when run
     normally, without the ‘-n’ option.

   - bpo-32940(2): Simplify and rename StringTranslatePseudoMapping in
     pyparse.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32984

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32940


File: python.info,  Node: Tools/Demos<25>,  Next: C API<48>,  Prev: IDLE<39>,  Up: Python 3 7 0 beta 3

1.23.54.10 Tools/Demos
......................

   - bpo-32885(1): Add an ‘-n’ flag for ‘Tools/scripts/pathfix.py’ to
     disable automatic backup creation (files with ‘~’ suffix).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32885


File: python.info,  Node: C API<48>,  Prev: Tools/Demos<25>,  Up: Python 3 7 0 beta 3

1.23.54.11 C API
................

   - bpo-33042(1): Embedding applications may once again call
     PySys_ResetWarnOptions, PySys_AddWarnOption, and PySys_AddXOption
     prior to calling Py_Initialize.

   - bpo-32374(2): Document that m_traverse for multi-phase initialized
     modules can be called with m_state=NULL, and add a sanity check

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33042

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32374


File: python.info,  Node: Python 3 7 0 beta 2,  Next: Python 3 7 0 beta 1,  Prev: Python 3 7 0 beta 3,  Up: Changelog（更動日誌）

1.23.55 Python 3.7.0 beta 2
---------------------------

'Release date: 2018-02-27'

* Menu:

* Security: Security<35>.
* Core and Builtins: Core and Builtins<54>.
* Library: Library<54>.
* Documentation: Documentation<48>.
* Tests: Tests<49>.
* Build: Build<52>.
* Windows: Windows<47>.
* macOS: macOS<39>.
* IDLE: IDLE<40>.
* Tools/Demos: Tools/Demos<26>.


File: python.info,  Node: Security<35>,  Next: Core and Builtins<54>,  Up: Python 3 7 0 beta 2

1.23.55.1 Security
..................

   - bpo-28414(1): The ssl module now allows users to perform their own
     IDN en/decoding when using SNI.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28414


File: python.info,  Node: Core and Builtins<54>,  Next: Library<54>,  Prev: Security<35>,  Up: Python 3 7 0 beta 2

1.23.55.2 Core and Builtins
...........................

   - bpo-32889(1): Update Valgrind suppression list to account for the
     rename of ‘Py_ADDRESS_IN_RANG’ to ‘address_in_range’.

   - bpo-31356(2): Remove the new API added in bpo-31356(3)
     (gc.ensure_disabled() context manager).

   - bpo-32305(4): For namespace packages, ensure that both ‘__file__’
     and ‘__spec__.origin’ are set to None.

   - bpo-32303(5): Make sure ‘__spec__.loader’ matches ‘__loader__’ for
     namespace packages.

   - bpo-32711(6): Fix the warning messages for Python/ast_unparse.c.
     Patch by Stéphane Wirtel

   - bpo-32583(7): Fix possible crashing in builtin Unicode decoders
     caused by write out-of-bound errors when using customized decode
     error handlers.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32889

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31356

   (3) https://bugs.python.org/issue?@action=redirect&bpo=31356

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32305

   (5) https://bugs.python.org/issue?@action=redirect&bpo=32303

   (6) https://bugs.python.org/issue?@action=redirect&bpo=32711

   (7) https://bugs.python.org/issue?@action=redirect&bpo=32583


File: python.info,  Node: Library<54>,  Next: Documentation<48>,  Prev: Core and Builtins<54>,  Up: Python 3 7 0 beta 2

1.23.55.3 Library
.................

   - bpo-32960(1): For dataclasses, disallow inheriting frozen from
     non-frozen classes, and also disallow inheriting non-frozen from
     frozen classes.  This restriction will be relaxed at a future date.

   - bpo-32713(2): Fixed tarfile.itn handling of out-of-bounds float
     values.  Patch by Joffrey Fuhrer.

   - bpo-32951(3): Direct instantiation of SSLSocket and SSLObject
     objects is now prohibited.  The constructors were never documented,
     tested, or designed as public constructors.  Users were suppose to
     use ssl.wrap_socket() or SSLContext.

   - bpo-32929(4): Remove the tri-state parameter "hash", and add the
     boolean "unsafe_hash".  If unsafe_hash is True, add a __hash__
     function, but if a __hash__ exists, raise TypeError.  If
     unsafe_hash is False, add a __hash__ based on the values of eq= and
     frozen=.  The unsafe_hash=False behavior is the same as the old
     hash=None behavior.  unsafe_hash=False is the default, just as
     hash=None used to be.

   - bpo-32947(5): Add OP_ENABLE_MIDDLEBOX_COMPAT and test workaround
     for TLSv1.3 for future compatibility with OpenSSL 1.1.1.

   - bpo-30622(6): The ssl module now detects missing NPN support in
     LibreSSL.

   - bpo-32922(7): dbm.open() now encodes filename with the filesystem
     encoding rather than default encoding.

   - bpo-32859(8): In ‘os.dup2’, don't check every call whether the
     ‘dup3’ syscall exists or not.

   - bpo-32556(9): nt._getfinalpathname, nt._getvolumepathname and
     nt._getdiskusage now correctly convert from bytes.

   - bpo-25988(10): Emit a *note DeprecationWarning: 18b. when using or
     importing an ABC directly from *note collections: 16. rather than
     from *note collections.abc: 17.

   - bpo-21060(11): Rewrite confusing message from setup.py upload from
     "No dist file created in earlier command" to the more helpful "Must
     create and upload files in one command".

   - bpo-32852(12): Make sure sys.argv remains as a list when running
     trace.

   - bpo-31333(13): ‘_abc’ module is added.  It is a speedup module with
     C implementations for various functions and methods in ‘abc’.
     Creating an ABC subclass and calling ‘isinstance’ or ‘issubclass’
     with an ABC subclass are up to 1.5x faster.  In addition, this
     makes Python start-up up to 10% faster.  Note that the new
     implementation hides internal registry and caches, previously
     accessible via private attributes ‘_abc_registry’, ‘_abc_cache’,
     and ‘_abc_negative_cache’.  There are three debugging helper
     methods that can be used instead ‘_dump_registry’,
     ‘_abc_registry_clear’, and ‘_abc_caches_clear’.

   - bpo-32841(14): Fixed ‘asyncio.Condition’ issue which silently
     ignored cancellation after notifying and cancelling a conditional
     lock.  Patch by Bar Harel.

   - bpo-32819(15): ssl.match_hostname() has been simplified and no
     longer depends on re and ipaddress module for wildcard and IP
     addresses.  Error reporting for invalid wildcards has been
     improved.

   - bpo-32394(16): socket: Remove
     TCP_FASTOPEN,TCP_KEEPCNT,TCP_KEEPIDLE,TCP_KEEPINTVL flags on older
     version Windows during run-time.

   - bpo-31787(17): Fixed refleaks of ‘__init__()’ methods in various
     modules.  (Contributed by Oren Milman)

   - bpo-30157(18): Fixed guessing quote and delimiter in
     csv.Sniffer.sniff() when only the last field is quoted.  Patch by
     Jake Davis.

   - bpo-32792(19): collections.ChainMap() preserves the order of the
     underlying mappings.

   - bpo-32775(20): *note fnmatch.translate(): 194c. no longer produces
     patterns which contain set operations.  Sets starting with '[' or
     containing '-', '&&', '~~' or '||' will be interpreted differently
     in regular expressions in future versions.  Currently they emit
     warnings.  fnmatch.translate() now avoids producing patterns
     containing such sets by accident.

   - bpo-32622(21): Implement native fast sendfile for Windows proactor
     event loop.

   - bpo-32777(22): Fix a rare but potential pre-exec child process
     deadlock in subprocess on POSIX systems when marking file
     descriptors inheritable on exec in the child process.  This bug
     appears to have been introduced in 3.4.

   - bpo-32647(23): The ctypes module used to depend on indirect linking
     for dlopen.  The shared extension is now explicitly linked against
     libdl on platforms with dl.

   - bpo-32741(24): Implement ‘asyncio.TimerHandle.when()’ method.

   - bpo-32691(25): Use mod_spec.parent when running modules with pdb

   - bpo-32734(26): Fixed ‘asyncio.Lock()’ safety issue which allowed
     acquiring and locking the same lock multiple times, without it
     being free.  Patch by Bar Harel.

   - bpo-32727(27): Do not include name field in SMTP envelope from
     address.  Patch by Stéphane Wirtel

   - bpo-31453(28): Add TLSVersion constants and
     SSLContext.maximum_version / minimum_version attributes.  The new
     API wraps OpenSSL 1.1
     ‘https://web.archive.org/web/20180309043602/https://www.openssl.org/docs/man1.1.0/ssl/SSL_CTX_set_min_proto_version.html’
     feature.

   - bpo-24334(29): Internal implementation details of ssl module were
     cleaned up.  The SSLSocket has one less layer of indirection.
     Owner and session information are now handled by the SSLSocket and
     SSLObject constructor.  Channel binding implementation has been
     simplified.

   - bpo-31848(30): Fix the error handling in Aifc_read.initfp() when
     the SSND chunk is not found.  Patch by Zackery Spytz.

   - bpo-32585(31): Add Ttk spinbox widget to *note tkinter.ttk: e2.
     Patch by Alan D Moore.

   - bpo-32221(32): Various functions returning tuple containing IPv6
     addresses now omit ‘%scope’ part since the same information is
     already encoded in 'scopeid' tuple item.  Especially this speeds up
     ‘socket.recvfrom()’ when it receives multicast packet since useless
     resolving of network interface name is omitted.

   - bpo-30693(33): The TarFile class now recurses directories in a
     reproducible way.

   - bpo-30693(34): The ZipFile class now recurses directories in a
     reproducible way.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32960

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32713

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32951

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32929

   (5) https://bugs.python.org/issue?@action=redirect&bpo=32947

   (6) https://bugs.python.org/issue?@action=redirect&bpo=30622

   (7) https://bugs.python.org/issue?@action=redirect&bpo=32922

   (8) https://bugs.python.org/issue?@action=redirect&bpo=32859

   (9) https://bugs.python.org/issue?@action=redirect&bpo=32556

   (10) https://bugs.python.org/issue?@action=redirect&bpo=25988

   (11) https://bugs.python.org/issue?@action=redirect&bpo=21060

   (12) https://bugs.python.org/issue?@action=redirect&bpo=32852

   (13) https://bugs.python.org/issue?@action=redirect&bpo=31333

   (14) https://bugs.python.org/issue?@action=redirect&bpo=32841

   (15) https://bugs.python.org/issue?@action=redirect&bpo=32819

   (16) https://bugs.python.org/issue?@action=redirect&bpo=32394

   (17) https://bugs.python.org/issue?@action=redirect&bpo=31787

   (18) https://bugs.python.org/issue?@action=redirect&bpo=30157

   (19) https://bugs.python.org/issue?@action=redirect&bpo=32792

   (20) https://bugs.python.org/issue?@action=redirect&bpo=32775

   (21) https://bugs.python.org/issue?@action=redirect&bpo=32622

   (22) https://bugs.python.org/issue?@action=redirect&bpo=32777

   (23) https://bugs.python.org/issue?@action=redirect&bpo=32647

   (24) https://bugs.python.org/issue?@action=redirect&bpo=32741

   (25) https://bugs.python.org/issue?@action=redirect&bpo=32691

   (26) https://bugs.python.org/issue?@action=redirect&bpo=32734

   (27) https://bugs.python.org/issue?@action=redirect&bpo=32727

   (28) https://bugs.python.org/issue?@action=redirect&bpo=31453

   (29) https://bugs.python.org/issue?@action=redirect&bpo=24334

   (30) https://bugs.python.org/issue?@action=redirect&bpo=31848

   (31) https://bugs.python.org/issue?@action=redirect&bpo=32585

   (32) https://bugs.python.org/issue?@action=redirect&bpo=32221

   (33) https://bugs.python.org/issue?@action=redirect&bpo=30693

   (34) https://bugs.python.org/issue?@action=redirect&bpo=30693


File: python.info,  Node: Documentation<48>,  Next: Tests<49>,  Prev: Library<54>,  Up: Python 3 7 0 beta 2

1.23.55.4 Documentation
.......................

   - bpo-28124(1): The ssl module function ssl.wrap_socket() has been
     de-emphasized and deprecated in favor of the more secure and
     efficient SSLContext.wrap_socket() method.

   - bpo-17232(2): Clarify docs for -O and -OO. Patch by Terry Reedy.

   - bpo-32436(3): Add documentation for the contextvars module (PEP
     567).

   - bpo-32800(4): Update link to w3c doc for xml default namespaces.

   - bpo-11015(5): Update *note test.support: cd. documentation.

   - bpo-8722(6): Document ‘__getattr__()’ behavior when property
     ‘get()’ method raises *note AttributeError: 2f6.

   - bpo-32614(7): Modify RE examples in documentation to use raw
     strings to prevent *note DeprecationWarning: 18b. and add text to
     REGEX HOWTO to highlight the deprecation.

   - bpo-31972(8): Improve docstrings for ‘pathlib.PurePath’ subclasses.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28124

   (2) https://bugs.python.org/issue?@action=redirect&bpo=17232

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32436

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32800

   (5) https://bugs.python.org/issue?@action=redirect&bpo=11015

   (6) https://bugs.python.org/issue?@action=redirect&bpo=8722

   (7) https://bugs.python.org/issue?@action=redirect&bpo=32614

   (8) https://bugs.python.org/issue?@action=redirect&bpo=31972


File: python.info,  Node: Tests<49>,  Next: Build<52>,  Prev: Documentation<48>,  Up: Python 3 7 0 beta 2

1.23.55.5 Tests
...............

   - bpo-31809(1): Add tests to verify connection with secp ECDH curves.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31809


File: python.info,  Node: Build<52>,  Next: Windows<47>,  Prev: Tests<49>,  Up: Python 3 7 0 beta 2

1.23.55.6 Build
...............

   - bpo-32898(1): Fix the python debug build when using COUNT_ALLOCS.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32898


File: python.info,  Node: Windows<47>,  Next: macOS<39>,  Prev: Build<52>,  Up: Python 3 7 0 beta 2

1.23.55.7 Windows
.................

   - bpo-32901(1): Update Tcl and Tk versions to 8.6.8

   - bpo-31966(2): Fixed WindowsConsoleIO.write() for writing empty
     data.

   - bpo-32409(3): Ensures activate.bat can handle Unicode contents.

   - bpo-32457(4): Improves handling of denormalized executable path
     when launching Python.

   - bpo-32370(5): Use the correct encoding for ipconfig output in the
     uuid module.  Patch by Segev Finer.

   - bpo-29248(6): Fix *note os.readlink(): 8c5. on Windows, which was
     mistakenly treating the ‘PrintNameOffset’ field of the reparse data
     buffer as a number of characters instead of bytes.  Patch by Craig
     Holmquist and SSE4.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32901

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31966

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32409

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32457

   (5) https://bugs.python.org/issue?@action=redirect&bpo=32370

   (6) https://bugs.python.org/issue?@action=redirect&bpo=29248


File: python.info,  Node: macOS<39>,  Next: IDLE<40>,  Prev: Windows<47>,  Up: Python 3 7 0 beta 2

1.23.55.8 macOS
...............

   - bpo-32901(1): Update macOS 10.9+ installer to Tcl/Tk 8.6.8.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32901


File: python.info,  Node: IDLE<40>,  Next: Tools/Demos<26>,  Prev: macOS<39>,  Up: Python 3 7 0 beta 2

1.23.55.9 IDLE
..............

   - bpo-32916(1): Change ‘str’ to ‘code’ in pyparse.

   - bpo-32905(2): Remove unused code in pyparse module.

   - bpo-32874(3): Add tests for pyparse.

   - bpo-32837(4): Using the system and place-dependent default encoding
     for open() is a bad idea for IDLE's system and location-independent
     files.

   - bpo-32826(5): Add "encoding=utf-8" to open() in IDLE's
     test_help_about.  GUI test test_file_buttons() only looks at
     initial ascii-only lines, but failed on systems where open()
     defaults to 'ascii' because readline() internally reads and decodes
     far enough ahead to encounter a non-ascii character in CREDITS.txt.

   - bpo-32765(6): Update configdialog General tab docstring to add new
     widgets to the widget list.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32916

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32905

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32874

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32837

   (5) https://bugs.python.org/issue?@action=redirect&bpo=32826

   (6) https://bugs.python.org/issue?@action=redirect&bpo=32765


File: python.info,  Node: Tools/Demos<26>,  Prev: IDLE<40>,  Up: Python 3 7 0 beta 2

1.23.55.10 Tools/Demos
......................

   - bpo-32222(1): Fix pygettext not extracting docstrings for functions
     with type annotated arguments.  Patch by Toby Harradine.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32222


File: python.info,  Node: Python 3 7 0 beta 1,  Next: Python 3 7 0 alpha 4,  Prev: Python 3 7 0 beta 2,  Up: Changelog（更動日誌）

1.23.56 Python 3.7.0 beta 1
---------------------------

'Release date: 2018-01-30'

* Menu:

* Core and Builtins: Core and Builtins<55>.
* Library: Library<55>.
* Documentation: Documentation<49>.
* Tests: Tests<50>.
* Build: Build<53>.
* Windows: Windows<48>.
* macOS: macOS<40>.
* C API: C API<49>.


File: python.info,  Node: Core and Builtins<55>,  Next: Library<55>,  Up: Python 3 7 0 beta 1

1.23.56.1 Core and Builtins
...........................

   - bpo-32703(1): Fix coroutine's ResourceWarning when there's an
     active error set when it's being finalized.

   - bpo-32650(2): Pdb and other debuggers dependent on bdb.py will
     correctly step over (next command) native coroutines.  Patch by
     Pablo Galindo.

   - bpo-28685(3): Optimize list.sort() and sorted() by using type
     specialized comparisons when possible.

   - bpo-32685(4): Improve suggestion when the Python 2 form of print
     statement is either present on the same line as the header of a
     compound statement or else terminated by a semi-colon instead of a
     newline.  Patch by Nitish Chandra.

   - bpo-32697(5): Python now explicitly preserves the definition order
     of keyword-only parameters.  It's always preserved their order, but
     this behavior was never guaranteed before; this behavior is now
     guaranteed and tested.

   - bpo-32690(6): The locals() dictionary now displays in the lexical
     order that variables were defined.  Previously, the order was
     reversed.

   - bpo-32677(7): Add ‘.isascii()’ method to ‘str’, ‘bytes’ and
     ‘bytearray’.  It can be used to test that string contains only
     ASCII characters.

   - bpo-32670(8): Enforce PEP 479(9) for all code.  This means that
     manually raising a StopIteration exception from a generator is
     prohibited for all code, regardless of whether 'from __future__
     import generator_stop' was used or not.

   - bpo-32591(10): Added built-in support for tracking the origin of
     coroutine objects; see sys.set_coroutine_origin_tracking_depth and
     CoroutineType.cr_origin.  This replaces the asyncio debug mode's
     use of coroutine wrapping for native coroutine objects.

   - bpo-31368(11): Expose preadv and pwritev system calls in the os
     module.  Patch by Pablo Galindo

   - bpo-32544(12): ‘hasattr(obj, name)’ and ‘getattr(obj, name,
     default)’ are about 4 times faster than before when ‘name’ is not
     found and ‘obj’ doesn't override ‘__getattr__’ or
     ‘__getattribute__’.

   - bpo-26163(13): Improved frozenset() hash to create more distinct
     hash values when faced with datasets containing many similar
     values.

   - bpo-32550(14): Remove the STORE_ANNOTATION bytecode.

   - bpo-20104(15): Expose posix_spawn as a low level API in the os
     module.  (removed before 3.7.0rc1)

   - bpo-24340(16): Fixed estimation of the code stack size.

   - bpo-32436(17): Implement PEP 567(18) Context Variables.

   - bpo-18533(19): ‘repr()’ on a dict containing its own ‘values()’ or
     ‘items()’ no longer raises ‘RecursionError’; OrderedDict similarly.
     Instead, use ‘...’, as for other recursive structures.  Patch by
     Ben North.

   - bpo-20891(20): Py_Initialize() now creates the GIL. The GIL is no
     longer created "on demand" to fix a race condition when
     PyGILState_Ensure() is called in a non-Python thread.

   - bpo-32028(21): Leading whitespace is now correctly ignored when
     generating suggestions for converting Py2 print statements to Py3
     builtin print function calls.  Patch by Sanyam Khurana.

   - bpo-31179(22): Make dict.copy() up to 5.5 times faster.

   - bpo-31113(23): Get rid of recursion in the compiler for normal
     control flow.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32703

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32650

   (3) https://bugs.python.org/issue?@action=redirect&bpo=28685

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32685

   (5) https://bugs.python.org/issue?@action=redirect&bpo=32697

   (6) https://bugs.python.org/issue?@action=redirect&bpo=32690

   (7) https://bugs.python.org/issue?@action=redirect&bpo=32677

   (8) https://bugs.python.org/issue?@action=redirect&bpo=32670

   (9) https://peps.python.org/pep-0479/

   (10) https://bugs.python.org/issue?@action=redirect&bpo=32591

   (11) https://bugs.python.org/issue?@action=redirect&bpo=31368

   (12) https://bugs.python.org/issue?@action=redirect&bpo=32544

   (13) https://bugs.python.org/issue?@action=redirect&bpo=26163

   (14) https://bugs.python.org/issue?@action=redirect&bpo=32550

   (15) https://bugs.python.org/issue?@action=redirect&bpo=20104

   (16) https://bugs.python.org/issue?@action=redirect&bpo=24340

   (17) https://bugs.python.org/issue?@action=redirect&bpo=32436

   (18) https://peps.python.org/pep-0567/

   (19) https://bugs.python.org/issue?@action=redirect&bpo=18533

   (20) https://bugs.python.org/issue?@action=redirect&bpo=20891

   (21) https://bugs.python.org/issue?@action=redirect&bpo=32028

   (22) https://bugs.python.org/issue?@action=redirect&bpo=31179

   (23) https://bugs.python.org/issue?@action=redirect&bpo=31113


File: python.info,  Node: Library<55>,  Next: Documentation<49>,  Prev: Core and Builtins<55>,  Up: Python 3 7 0 beta 1

1.23.56.2 Library
.................

   - bpo-25988(1): Deprecate exposing the contents of collections.abc in
     the regular collections module.

   - bpo-31429(2): The default cipher suite selection of the ssl module
     now uses a blacklist approach rather than a hard-coded whitelist.
     Python no longer re-enables ciphers that have been blocked by
     OpenSSL security update.  Default cipher suite selection can be
     configured on compile time.

   - bpo-30306(3): contextlib.contextmanager now releases the arguments
     passed to the underlying generator as soon as the context manager
     is entered.  Previously it would keep them alive for as long as the
     context manager was alive, even when not being used as a function
     decorator.  Patch by Martin Teichmann.

   - bpo-21417(4): Added support for setting the compression level for
     zipfile.ZipFile.

   - bpo-32251(5): Implement asyncio.BufferedProtocol (provisional API).

   - bpo-32513(6): In dataclasses, allow easier overriding of dunder
     methods without specifying decorator parameters.

   - bpo-32660(7): *note termios: ca. makes available ‘FIONREAD’,
     ‘FIONCLEX’, ‘FIOCLEX’, ‘FIOASYNC’ and ‘FIONBIO’ also under
     Solaris/derivatives.

   - bpo-27931(8): Fix email address header parsing error when the
     username is an empty quoted string.  Patch by Xiang Zhang.

   - bpo-32659(9): Under Solaris and derivatives, *note os.stat_result:
     142c. provides a st_fstype attribute.

   - bpo-32662(10): Implement Server.start_serving(),
     Server.serve_forever(), and Server.is_serving() methods.  Add
     'start_serving' keyword parameter to loop.create_server() and
     loop.create_unix_server().

   - bpo-32391(11): Implement *note asyncio.StreamWriter.wait_closed():
     aaf. and *note asyncio.StreamWriter.is_closing(): ab0. methods

   - bpo-32643(12): Make Task._step, Task._wakeup and
     Future._schedule_callbacks methods private.

   - bpo-32630(13): Refactor decimal module to use contextvars to store
     decimal context.

   - bpo-32622(14): Add ‘asyncio.AbstractEventLoop.sendfile()’ method.

   - bpo-32304(15): distutils' upload command no longer corrupts tar
     files ending with a CR byte, and no longer tries to convert CR to
     CRLF in any of the upload text fields.

   - bpo-32502(16): uuid.uuid1 no longer raises an exception if a 64-bit
     hardware address is encountered.

   - bpo-32596(17): ‘concurrent.futures’ imports ‘ThreadPoolExecutor’
     and ‘ProcessPoolExecutor’ lazily (using PEP 562(18)).  It makes
     ‘import asyncio’ about 15% faster because asyncio uses only
     ‘ThreadPoolExecutor’ by default.

   - bpo-31801(19): Add ‘_ignore_’ to ‘Enum’ so temporary variables can
     be used during class construction without being turned into
     members.

   - bpo-32576(20): Use queue.SimpleQueue() in places where it can be
     invoked from a weakref callback.

   - bpo-32574(21): Fix memory leak in asyncio.Queue, when the queue has
     limited size and it is full, the cancelation of queue.put() can
     cause a memory leak.  Patch by: José Melero.

   - bpo-32521(22): The nis module is now compatible with new libnsl and
     headers location.

   - bpo-32467(23): collections.abc.ValuesView now inherits from
     collections.abc.Collection.

   - bpo-32473(24): Improve ABCMeta._dump_registry() output readability

   - bpo-32102(25): New argument ‘capture_output’ for subprocess.run

   - bpo-32521(26): glibc has removed Sun RPC. Use replacement libtirpc
     headers and library in nis module.

   - bpo-32493(27): UUID module fixes build for FreeBSD/OpenBSD

   - bpo-32503(28): Pickling with protocol 4 no longer creates too small
     frames.

   - bpo-29237(29): Create enum for pstats sorting options

   - bpo-32454(30): Add close(fd) function to the socket module.

   - bpo-25942(31): The subprocess module is now more graceful when
     handling a Ctrl-C KeyboardInterrupt during subprocess.call,
     subprocess.run, or a Popen context manager.  It now waits a short
     amount of time for the child (presumed to have also gotten the
     SIGINT) to exit, before continuing the KeyboardInterrupt exception
     handling.  This still includes a SIGKILL in the call() and run()
     APIs, but at least the child had a chance first.

   - bpo-32433(32): The hmac module now has hmac.digest(), which
     provides an optimized HMAC digest.

   - bpo-28134(33): Sockets now auto-detect family, type and protocol
     from file descriptor by default.

   - bpo-32404(34): Fix bug where *note
     datetime.datetime.fromtimestamp(): 495. did not call __new__ in
     *note datetime.datetime: 1b0. subclasses.

   - bpo-32403(35): Improved speed of *note datetime.date: 1b1. and
     *note datetime.datetime: 1b0. alternate constructors.

   - bpo-32228(36): Ensure that ‘truncate()’ preserves the file position
     (as reported by ‘tell()’) after writes longer than the buffer size.

   - bpo-32410(37): Implement ‘loop.sock_sendfile’ for asyncio event
     loop.

   - bpo-22908(38): Added seek and tell to the ZipExtFile class.  This
     only works if the file object used to open the zipfile is seekable.

   - bpo-32373(39): Add socket.getblocking() method.

   - bpo-32248(40): Add *note importlib.resources: 6f. and *note
     importlib.abc.ResourceReader: aa0. as the unified API for reading
     resources contained within packages.  Loaders wishing to support
     resource reading must implement the ‘get_resource_reader()’ method.
     File-based and zipimport-based loaders both implement these APIs.
     *note importlib.abc.ResourceLoader: b8e. is deprecated in favor of
     these new APIs.

   - bpo-32320(41): collections.namedtuple() now supports default
     values.

   - bpo-29302(42): Add contextlib.AsyncExitStack.  Patch by Alexander
     Mohr and Ilya Kulakov.

   - bpo-31961(43): 'Removed in Python 3.7.0b2.'  The 'args' argument of
     subprocess.Popen can now be a *note path-like object: ac2.  If
     'args' is given as a sequence, it's first element can now be a
     *note path-like object: ac2. as well.

   - bpo-31900(44): The *note locale.localeconv(): ba5. function now
     sets temporarily the ‘LC_CTYPE’ locale to the ‘LC_NUMERIC’ locale
     to decode ‘decimal_point’ and ‘thousands_sep’ byte strings if they
     are non-ASCII or longer than 1 byte, and the ‘LC_NUMERIC’ locale is
     different than the ‘LC_CTYPE’ locale.  This temporary change
     affects other threads.  Same change for the *note str.format():
     5c7. method when formatting a number (*note int: 23c, *note float:
     2c8, *note float: 2c8. and subclasses) with the ‘n’ type (ex:
     ‘'{:n}'.format(1234)’).

   - bpo-31853(45): Use super().method instead of socket.method in
     SSLSocket.  They were there most likely for legacy reasons.

   - bpo-31399(46): The ssl module now uses OpenSSL's
     X509_VERIFY_PARAM_set1_host() and X509_VERIFY_PARAM_set1_ip() API
     to verify hostname and IP addresses.  Subject common name fallback
     can be disabled with SSLContext.hostname_checks_common_name.

   - bpo-14976(47): Add a queue.SimpleQueue class, an unbounded FIFO
     queue with a reentrant C implementation of put().

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25988

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31429

   (3) https://bugs.python.org/issue?@action=redirect&bpo=30306

   (4) https://bugs.python.org/issue?@action=redirect&bpo=21417

   (5) https://bugs.python.org/issue?@action=redirect&bpo=32251

   (6) https://bugs.python.org/issue?@action=redirect&bpo=32513

   (7) https://bugs.python.org/issue?@action=redirect&bpo=32660

   (8) https://bugs.python.org/issue?@action=redirect&bpo=27931

   (9) https://bugs.python.org/issue?@action=redirect&bpo=32659

   (10) https://bugs.python.org/issue?@action=redirect&bpo=32662

   (11) https://bugs.python.org/issue?@action=redirect&bpo=32391

   (12) https://bugs.python.org/issue?@action=redirect&bpo=32643

   (13) https://bugs.python.org/issue?@action=redirect&bpo=32630

   (14) https://bugs.python.org/issue?@action=redirect&bpo=32622

   (15) https://bugs.python.org/issue?@action=redirect&bpo=32304

   (16) https://bugs.python.org/issue?@action=redirect&bpo=32502

   (17) https://bugs.python.org/issue?@action=redirect&bpo=32596

   (18) https://peps.python.org/pep-0562/

   (19) https://bugs.python.org/issue?@action=redirect&bpo=31801

   (20) https://bugs.python.org/issue?@action=redirect&bpo=32576

   (21) https://bugs.python.org/issue?@action=redirect&bpo=32574

   (22) https://bugs.python.org/issue?@action=redirect&bpo=32521

   (23) https://bugs.python.org/issue?@action=redirect&bpo=32467

   (24) https://bugs.python.org/issue?@action=redirect&bpo=32473

   (25) https://bugs.python.org/issue?@action=redirect&bpo=32102

   (26) https://bugs.python.org/issue?@action=redirect&bpo=32521

   (27) https://bugs.python.org/issue?@action=redirect&bpo=32493

   (28) https://bugs.python.org/issue?@action=redirect&bpo=32503

   (29) https://bugs.python.org/issue?@action=redirect&bpo=29237

   (30) https://bugs.python.org/issue?@action=redirect&bpo=32454

   (31) https://bugs.python.org/issue?@action=redirect&bpo=25942

   (32) https://bugs.python.org/issue?@action=redirect&bpo=32433

   (33) https://bugs.python.org/issue?@action=redirect&bpo=28134

   (34) https://bugs.python.org/issue?@action=redirect&bpo=32404

   (35) https://bugs.python.org/issue?@action=redirect&bpo=32403

   (36) https://bugs.python.org/issue?@action=redirect&bpo=32228

   (37) https://bugs.python.org/issue?@action=redirect&bpo=32410

   (38) https://bugs.python.org/issue?@action=redirect&bpo=22908

   (39) https://bugs.python.org/issue?@action=redirect&bpo=32373

   (40) https://bugs.python.org/issue?@action=redirect&bpo=32248

   (41) https://bugs.python.org/issue?@action=redirect&bpo=32320

   (42) https://bugs.python.org/issue?@action=redirect&bpo=29302

   (43) https://bugs.python.org/issue?@action=redirect&bpo=31961

   (44) https://bugs.python.org/issue?@action=redirect&bpo=31900

   (45) https://bugs.python.org/issue?@action=redirect&bpo=31853

   (46) https://bugs.python.org/issue?@action=redirect&bpo=31399

   (47) https://bugs.python.org/issue?@action=redirect&bpo=14976


File: python.info,  Node: Documentation<49>,  Next: Tests<50>,  Prev: Library<55>,  Up: Python 3 7 0 beta 1

1.23.56.3 Documentation
.......................

   - bpo-32724(1): Add references to some commands in the documentation
     of Pdb.  Patch by Stéphane Wirtel

   - bpo-32649(2): Complete the C API documentation, profiling and
     tracing part with the newly added per-opcode events.

   - bpo-17799(3): Explain real behaviour of sys.settrace and
     sys.setprofile and their C-API counterparts regarding which type of
     events are received in each function.  Patch by Pablo Galindo
     Salgado.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32724

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32649

   (3) https://bugs.python.org/issue?@action=redirect&bpo=17799


File: python.info,  Node: Tests<50>,  Next: Build<53>,  Prev: Documentation<49>,  Up: Python 3 7 0 beta 1

1.23.56.4 Tests
...............

   - bpo-32721(1): Fix test_hashlib to not fail if the _md5 module is
     not built.

   - bpo-28414(2): Add test cases for IDNA 2003 and 2008 host names.
     IDNA 2003 internationalized host names are working since
     bpo-31399(3) has landed.  IDNA 2008 are still broken.

   - bpo-32604(4): Add a new "_xxsubinterpreters" extension module that
     exposes the existing subinterpreter C-API and a new
     cross-interpreter data sharing mechanism.  The module is primarily
     intended for more thorough testing of the existing subinterpreter
     support.  Note that the _xxsubinterpreters module has been removed
     in 3.7.0rc1.

   - bpo-32602(5): Add test certs and test for ECDSA cert and EC/RSA
     dual mode.

   - bpo-32549(6): On Travis CI, Python now Compiles and uses a local
     copy of OpenSSL 1.1.0g for testing.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32721

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28414

   (3) https://bugs.python.org/issue?@action=redirect&bpo=31399

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32604

   (5) https://bugs.python.org/issue?@action=redirect&bpo=32602

   (6) https://bugs.python.org/issue?@action=redirect&bpo=32549


File: python.info,  Node: Build<53>,  Next: Windows<48>,  Prev: Tests<50>,  Up: Python 3 7 0 beta 1

1.23.56.5 Build
...............

   - bpo-32635(1): Fix segfault of the crypt module when libxcrypt is
     provided instead of libcrypt at the system.

   - bpo-32598(2): Use autoconf to detect OpenSSL libs, headers and
     supported features.  The ax_check_openssl M4 macro uses pkg-config
     to locate OpenSSL and falls back to manual search.

   - bpo-32593(3): Drop support of FreeBSD 9 and older.

   - bpo-29708(4): If the ‘SOURCE_DATE_EPOCH’ environment variable is
     set, *note py_compile: a1. will always create hash-based ‘.pyc’
     files.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32635

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32598

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32593

   (4) https://bugs.python.org/issue?@action=redirect&bpo=29708


File: python.info,  Node: Windows<48>,  Next: macOS<40>,  Prev: Build<53>,  Up: Python 3 7 0 beta 1

1.23.56.6 Windows
.................

   - bpo-32588(1): Create standalone _distutils_findvs module and add
     missing _queue module to installer.

   - bpo-29911(2): Ensure separate Modify and Uninstall buttons are
     displayed.

   - bpo-32507(3): Use app-local UCRT install rather than the proper
     update for old versions of Windows.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32588

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29911

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32507


File: python.info,  Node: macOS<40>,  Next: C API<49>,  Prev: Windows<48>,  Up: Python 3 7 0 beta 1

1.23.56.7 macOS
...............

   - bpo-32726(1): Provide an additional, more modern macOS installer
     variant that supports macOS 10.9+ systems in 64-bit mode only.
     Upgrade the supplied third-party libraries to OpenSSL 1.1.0g and to
     SQLite 3.22.0.  The 10.9+ installer now links with and supplies its
     own copy of Tcl/Tk 8.6.

   - bpo-28440(2): No longer add /Library/Python/3.x/site-packages to
     sys.path for macOS framework builds to avoid future conflicts.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32726

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28440


File: python.info,  Node: C API<49>,  Prev: macOS<40>,  Up: Python 3 7 0 beta 1

1.23.56.8 C API
...............

   - bpo-32681(1): Fix uninitialized variable 'res' in the C
     implementation of os.dup2.  Patch by Stéphane Wirtel

   - bpo-10381(2): Add C API access to the ‘datetime.timezone’
     constructor and ‘datetime.timzone.UTC’ singleton.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32681

   (2) https://bugs.python.org/issue?@action=redirect&bpo=10381


File: python.info,  Node: Python 3 7 0 alpha 4,  Next: Python 3 7 0 alpha 3,  Prev: Python 3 7 0 beta 1,  Up: Changelog（更動日誌）

1.23.57 Python 3.7.0 alpha 4
----------------------------

'Release date: 2018-01-08'

* Menu:

* Core and Builtins: Core and Builtins<56>.
* Library: Library<56>.
* Documentation: Documentation<50>.
* Tests: Tests<51>.
* Windows: Windows<49>.
* Tools/Demos: Tools/Demos<27>.
* C API: C API<50>.


File: python.info,  Node: Core and Builtins<56>,  Next: Library<56>,  Up: Python 3 7 0 alpha 4

1.23.57.1 Core and Builtins
...........................

   - bpo-31975(1): The default warning filter list now starts with a
     "default::DeprecationWarning:__main__" entry, so deprecation
     warnings are once again shown by default in single-file scripts and
     at the interactive prompt.

   - bpo-32226(2): ‘__class_getitem__’ is now an automatic class method.

   - bpo-32399(3): Add AIX uuid library support for RFC4122 using
     uuid_create() in libc.a

   - bpo-32390(4): Fix the compilation failure on AIX after the f_fsid
     field has been added to the object returned by os.statvfs()
     (bpo-32143(5)).  Original patch by Michael Felt.

   - bpo-32379(6): Make MRO computation faster when a class inherits
     from a single base.

   - bpo-32259(7): The error message of a TypeError raised when unpack
     non-iterable is now more specific.

   - bpo-27169(8): The ‘__debug__’ constant is now optimized out at
     compile time.  This fixes also bpo-22091(9).

   - bpo-32329(10): The *note -R: 199d. option now turns on hash
     randomization when the *note PYTHONHASHSEED: 101e. environment
     variable is set to ‘0’.  Previously, the option was ignored.
     Moreover, ‘sys.flags.hash_randomization’ is now properly set to 0
     when hash randomization is turned off by ‘PYTHONHASHSEED=0’.

   - bpo-30416(11): The optimizer is now protected from spending much
     time doing complex calculations and consuming much memory for
     creating large constants in constant folding.  Increased limits for
     constants that can be produced in constant folding.

   - bpo-32282(12): Fix an unnecessary ifdef in the include of
     VersionHelpers.h in socketmodule on Windows.

   - bpo-30579(13): Implement TracebackType.__new__ to allow
     Python-level creation of traceback objects, and make
     TracebackType.tb_next mutable.

   - bpo-32260(14): Don't byte swap the input keys to the SipHash
     algorithm on big-endian platforms.  This should ensure siphash
     gives consistent results across platforms.

   - bpo-31506(15): Improve the error message logic for object.__new__
     and object.__init__.  Patch by Sanyam Khurana.

   - bpo-20361(16): ‘-b’ and ‘-bb’ now inject ‘'default::BytesWarning'’
     and ‘error::BytesWarning’ entries into ‘sys.warnoptions’, ensuring
     that they take precedence over any other warning filters configured
     via the ‘-W’ option or the ‘PYTHONWARNINGS’ environment variable.

   - bpo-32230(17): ‘-X dev’ now injects a ‘'default'’ entry into
     sys.warnoptions, ensuring that it behaves identically to actually
     passing ‘-Wdefault’ at the command line.

   - bpo-29240(18): Add a new UTF-8 mode: implementation of the PEP
     540(19).

   - bpo-32226(20): PEP 560(21): Add support for ‘__mro_entries__’ and
     ‘__class_getitem__’.  Implemented by Ivan Levkivskyi.

   - bpo-32225(22): PEP 562(23): Add support for module ‘__getattr__’
     and ‘__dir__’.  Implemented by Ivan Levkivskyi.

   - bpo-31901(24): The ‘atexit’ module now has its callback stored per
     interpreter.

   - bpo-31650(25): Implement PEP 552(26) (Deterministic pycs).  Python
     now supports invalidating bytecode cache files bashed on a source
     content hash rather than source last-modified time.

   - bpo-29469(27): Move constant folding from bytecode layer to AST
     layer.  Original patch by Eugene Toder.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31975

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32226

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32399

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32390

   (5) https://bugs.python.org/issue?@action=redirect&bpo=32143

   (6) https://bugs.python.org/issue?@action=redirect&bpo=32379

   (7) https://bugs.python.org/issue?@action=redirect&bpo=32259

   (8) https://bugs.python.org/issue?@action=redirect&bpo=27169

   (9) https://bugs.python.org/issue?@action=redirect&bpo=22091

   (10) https://bugs.python.org/issue?@action=redirect&bpo=32329

   (11) https://bugs.python.org/issue?@action=redirect&bpo=30416

   (12) https://bugs.python.org/issue?@action=redirect&bpo=32282

   (13) https://bugs.python.org/issue?@action=redirect&bpo=30579

   (14) https://bugs.python.org/issue?@action=redirect&bpo=32260

   (15) https://bugs.python.org/issue?@action=redirect&bpo=31506

   (16) https://bugs.python.org/issue?@action=redirect&bpo=20361

   (17) https://bugs.python.org/issue?@action=redirect&bpo=32230

   (18) https://bugs.python.org/issue?@action=redirect&bpo=29240

   (19) https://peps.python.org/pep-0540/

   (20) https://bugs.python.org/issue?@action=redirect&bpo=32226

   (21) https://peps.python.org/pep-0560/

   (22) https://bugs.python.org/issue?@action=redirect&bpo=32225

   (23) https://peps.python.org/pep-0562/

   (24) https://bugs.python.org/issue?@action=redirect&bpo=31901

   (25) https://bugs.python.org/issue?@action=redirect&bpo=31650

   (26) https://peps.python.org/pep-0552/

   (27) https://bugs.python.org/issue?@action=redirect&bpo=29469


File: python.info,  Node: Library<56>,  Next: Documentation<50>,  Prev: Core and Builtins<56>,  Up: Python 3 7 0 alpha 4

1.23.57.2 Library
.................

   - bpo-32506(1): Now that dict is defined as keeping insertion order,
     drop OrderedDict and just use plain dict.

   - bpo-32279(2): Add params to dataclasses.make_dataclasses(): init,
     repr, eq, order, hash, and frozen.  Pass them through to
     dataclass().

   - bpo-32278(3): Make type information optional on
     dataclasses.make_dataclass().  If omitted, the string 'typing.Any'
     is used.

   - bpo-32499(4): Add dataclasses.is_dataclass(obj), which returns True
     if obj is a dataclass or an instance of one.

   - bpo-32468(5): Improve frame repr() to mention filename, code name
     and current line number.

   - bpo-23749(6): asyncio: Implement loop.start_tls()

   - bpo-32441(7): Return the new file descriptor (i.e., the second
     argument) from ‘os.dup2’.  Previously, ‘None’ was always returned.

   - bpo-32422(8): ‘functools.lru_cache’ uses less memory (3 words for
     each cached key) and takes about 1/3 time for cyclic GC.

   - bpo-31721(9): Prevent Python crash from happening when
     Future._log_traceback is set to True manually.  Now it can only be
     set to False, or a ValueError is raised.

   - bpo-32415(10): asyncio: Add Task.get_loop() and Future.get_loop()

   - bpo-26133(11): Don't unsubscribe signals in asyncio UNIX event loop
     on interpreter shutdown.

   - bpo-32363(12): Make asyncio.Task.set_exception() and set_result()
     raise NotImplementedError.  Task._step() and Future.__await__()
     raise proper exceptions when they are in an invalid state, instead
     of raising an AssertionError.

   - bpo-32357(13): Optimize asyncio.iscoroutine() and
     loop.create_task() for non-native coroutines (e.g.  async/await
     compiled with Cython).  'loop.create_task(python_coroutine)' used
     to be 20% faster than 'loop.create_task(cython_coroutine)'.  Now,
     the latter is as fast.

   - bpo-32356(14): asyncio.transport.resume_reading() and
     pause_reading() are now idempotent.  New transport.is_reading()
     method is added.

   - bpo-32355(15): Optimize asyncio.gather(); now up to 15% faster.

   - bpo-32351(16): Use fastpath in asyncio.sleep if delay<0 (2x boost)

   - bpo-32348(17): Optimize asyncio.Future schedule/add/remove
     callback.  The optimization shows 3-6% performance improvements of
     async/await code.

   - bpo-32331(18): Fix socket.settimeout() and socket.setblocking() to
     keep socket.type as is.  Fix socket.socket() constructor to reset
     any bit flags applied to socket's type.  This change only affects
     OSes that have SOCK_NONBLOCK and/or SOCK_CLOEXEC.

   - bpo-32248(19): Add *note importlib.abc.ResourceReader: aa0. as an
     ABC for loaders to provide a unified API for reading resources
     contained within packages.  Also add *note importlib.resources: 6f.
     as the port of ‘importlib_resources’.

   - bpo-32311(20): Implement asyncio.create_task(coro) shortcut

   - bpo-32327(21): Convert asyncio functions that were documented as
     coroutines to coroutines.  Affected functions: loop.sock_sendall,
     loop.sock_recv, loop.sock_accept, loop.getaddrinfo,
     loop.getnameinfo.

   - bpo-32323(22): *note urllib.parse.urlsplit(): ce6. does not convert
     zone-id (scope) to lower case for scoped IPv6 addresses in
     hostnames now.

   - bpo-32302(23): Fix bdist_wininst of distutils for CRT v142: it
     binary compatible with CRT v140.

   - bpo-29711(24): Fix ‘stop_serving’ in asyncio proactor loop kill all
     listening servers

   - bpo-32308(25): *note re.sub(): 283. now replaces empty matches
     adjacent to a previous non-empty match.

   - bpo-29970(26): Abort asyncio SSLProtocol connection if handshake
     not complete within 10 seconds.

   - bpo-32314(27): Implement asyncio.run().

   - bpo-17852(28): Revert incorrect fix based on misunderstanding of
     _Py_PyAtExit() semantics.

   - bpo-32296(29): Implement asyncio._get_running_loop() and
     get_event_loop() in C. This makes them 4x faster.

   - bpo-32250(30): Implement ‘asyncio.current_task()’ and
     ‘asyncio.all_tasks()’.  Add helpers intended to be used by
     alternative task implementations: ‘asyncio._register_task’,
     ‘asyncio._enter_task’, ‘asyncio._leave_task’ and
     ‘asyncio._unregister_task’.  Deprecate
     ‘asyncio.Task.current_task()’ and ‘asyncio.Task.all_tasks()’.

   - bpo-32255(31): A single empty field is now always quoted when
     written into a CSV file.  This allows to distinguish an empty row
     from a row consisting of a single empty field.  Patch by Licht
     Takeuchi.

   - bpo-32277(32): Raise ‘NotImplementedError’ instead of ‘SystemError’
     on platforms where ‘chmod(..., follow_symlinks=False)’ is not
     supported.  Patch by Anthony Sottile.

   - bpo-30050(33): New argument warn_on_full_buffer to
     signal.set_wakeup_fd lets you control whether Python prints a
     warning on stderr when the wakeup fd buffer overflows.

   - bpo-29137(34): The ‘fpectl’ library has been removed.  It was never
     enabled by default, never worked correctly on x86-64, and it
     changed the Python ABI in ways that caused unexpected breakage of C
     extensions.

   - bpo-32273(35): Move asyncio.test_utils to test.test_asyncio.

   - bpo-32272(36): Remove asyncio.async() function.

   - bpo-32269(37): Add asyncio.get_running_loop() function.

   - bpo-32265(38): All class and static methods of builtin types now
     are correctly classified by inspect.classify_class_attrs() and
     grouped in pydoc ouput.  Added types.ClassMethodDescriptorType for
     unbound class methods of builtin types.

   - bpo-32253(39): Deprecate ‘yield from lock’, ‘await lock’, ‘with
     (yield from lock)’ and ‘with await lock’ for asyncio
     synchronization primitives.

   - bpo-22589(40): Changed MIME type of .bmp from 'image/x-ms-bmp' to
     'image/bmp'

   - bpo-32193(41): Convert asyncio to use 'async/await' syntax.  Old
     styled ‘yield from’ is still supported too.

   - bpo-32206(42): Add support to run modules with pdb

   - bpo-32227(43): ‘functools.singledispatch’ now supports registering
     implementations using type annotations.

   - bpo-15873(44): Added new alternate constructors *note
     datetime.datetime.fromisoformat(): 5bc, *note
     datetime.time.fromisoformat(): 5bb. and *note
     datetime.date.fromisoformat(): 5ba. as the inverse operation of
     each classes's respective ‘isoformat’ methods.

   - bpo-32199(45): The getnode() ip getter now uses 'ip link' instead
     of 'ip link list'.

   - bpo-32143(46): os.statvfs() includes the f_fsid field from
     statvfs(2)

   - bpo-26439(47): Fix ctypes.util.find_library() for AIX by
     implementing ctypes._aix.find_library() Patch by: Michael Felt

   - bpo-31993(48): The pickler now uses less memory when serializing
     large bytes and str objects into a file.  Pickles created with
     protocol 4 will require less memory for unpickling large bytes and
     str objects.

   - bpo-27456(49): Ensure TCP_NODELAY is set on Linux.  Tests by Victor
     Stinner.

   - bpo-31778(50): ast.literal_eval() is now more strict.  Addition and
     subtraction of arbitrary numbers no longer allowed.

   - bpo-31802(51): Importing native path module (‘posixpath’, ‘ntpath’)
     now works even if the ‘os’ module still is not imported.

   - bpo-30241(52): Add contextlib.AbstractAsyncContextManager.  Patch
     by Jelle Zijlstra.

   - bpo-31699(53): Fix deadlocks in *note
     concurrent.futures.ProcessPoolExecutor: 893. when task arguments or
     results cause pickling or unpickling errors.  This should make sure
     that calls to the ‘ProcessPoolExecutor’ API always eventually
     return.

   - bpo-15216(54): ‘TextIOWrapper.reconfigure()’ supports changing
     'encoding', 'errors', and 'newline'.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32506

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32279

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32278

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32499

   (5) https://bugs.python.org/issue?@action=redirect&bpo=32468

   (6) https://bugs.python.org/issue?@action=redirect&bpo=23749

   (7) https://bugs.python.org/issue?@action=redirect&bpo=32441

   (8) https://bugs.python.org/issue?@action=redirect&bpo=32422

   (9) https://bugs.python.org/issue?@action=redirect&bpo=31721

   (10) https://bugs.python.org/issue?@action=redirect&bpo=32415

   (11) https://bugs.python.org/issue?@action=redirect&bpo=26133

   (12) https://bugs.python.org/issue?@action=redirect&bpo=32363

   (13) https://bugs.python.org/issue?@action=redirect&bpo=32357

   (14) https://bugs.python.org/issue?@action=redirect&bpo=32356

   (15) https://bugs.python.org/issue?@action=redirect&bpo=32355

   (16) https://bugs.python.org/issue?@action=redirect&bpo=32351

   (17) https://bugs.python.org/issue?@action=redirect&bpo=32348

   (18) https://bugs.python.org/issue?@action=redirect&bpo=32331

   (19) https://bugs.python.org/issue?@action=redirect&bpo=32248

   (20) https://bugs.python.org/issue?@action=redirect&bpo=32311

   (21) https://bugs.python.org/issue?@action=redirect&bpo=32327

   (22) https://bugs.python.org/issue?@action=redirect&bpo=32323

   (23) https://bugs.python.org/issue?@action=redirect&bpo=32302

   (24) https://bugs.python.org/issue?@action=redirect&bpo=29711

   (25) https://bugs.python.org/issue?@action=redirect&bpo=32308

   (26) https://bugs.python.org/issue?@action=redirect&bpo=29970

   (27) https://bugs.python.org/issue?@action=redirect&bpo=32314

   (28) https://bugs.python.org/issue?@action=redirect&bpo=17852

   (29) https://bugs.python.org/issue?@action=redirect&bpo=32296

   (30) https://bugs.python.org/issue?@action=redirect&bpo=32250

   (31) https://bugs.python.org/issue?@action=redirect&bpo=32255

   (32) https://bugs.python.org/issue?@action=redirect&bpo=32277

   (33) https://bugs.python.org/issue?@action=redirect&bpo=30050

   (34) https://bugs.python.org/issue?@action=redirect&bpo=29137

   (35) https://bugs.python.org/issue?@action=redirect&bpo=32273

   (36) https://bugs.python.org/issue?@action=redirect&bpo=32272

   (37) https://bugs.python.org/issue?@action=redirect&bpo=32269

   (38) https://bugs.python.org/issue?@action=redirect&bpo=32265

   (39) https://bugs.python.org/issue?@action=redirect&bpo=32253

   (40) https://bugs.python.org/issue?@action=redirect&bpo=22589

   (41) https://bugs.python.org/issue?@action=redirect&bpo=32193

   (42) https://bugs.python.org/issue?@action=redirect&bpo=32206

   (43) https://bugs.python.org/issue?@action=redirect&bpo=32227

   (44) https://bugs.python.org/issue?@action=redirect&bpo=15873

   (45) https://bugs.python.org/issue?@action=redirect&bpo=32199

   (46) https://bugs.python.org/issue?@action=redirect&bpo=32143

   (47) https://bugs.python.org/issue?@action=redirect&bpo=26439

   (48) https://bugs.python.org/issue?@action=redirect&bpo=31993

   (49) https://bugs.python.org/issue?@action=redirect&bpo=27456

   (50) https://bugs.python.org/issue?@action=redirect&bpo=31778

   (51) https://bugs.python.org/issue?@action=redirect&bpo=31802

   (52) https://bugs.python.org/issue?@action=redirect&bpo=30241

   (53) https://bugs.python.org/issue?@action=redirect&bpo=31699

   (54) https://bugs.python.org/issue?@action=redirect&bpo=15216


File: python.info,  Node: Documentation<50>,  Next: Tests<51>,  Prev: Library<56>,  Up: Python 3 7 0 alpha 4

1.23.57.3 Documentation
.......................

   - bpo-32418(1): Add get_loop() method to Server and AbstractServer
     classes.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32418


File: python.info,  Node: Tests<51>,  Next: Windows<49>,  Prev: Documentation<50>,  Up: Python 3 7 0 alpha 4

1.23.57.4 Tests
...............

   - bpo-32252(1): Fix faulthandler_suppress_crash_report() used to
     prevent core dump files when testing crashes.  getrlimit() returns
     zero on success.

   - bpo-32002(2): Adjust C locale coercion testing for the empty locale
     and POSIX locale cases to more readily adjust to platform dependent
     behaviour.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32252

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32002


File: python.info,  Node: Windows<49>,  Next: Tools/Demos<27>,  Prev: Tests<51>,  Up: Python 3 7 0 alpha 4

1.23.57.5 Windows
.................

   - bpo-19764(1): Implement support for
     ‘subprocess.Popen(close_fds=True)’ on Windows.  Patch by Segev
     Finer.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=19764


File: python.info,  Node: Tools/Demos<27>,  Next: C API<50>,  Prev: Windows<49>,  Up: Python 3 7 0 alpha 4

1.23.57.6 Tools/Demos
.....................

   - bpo-24960(1): 2to3 and lib2to3 can now read pickled grammar files
     using pkgutil.get_data() rather than probing the filesystem.  This
     lets 2to3 and lib2to3 work when run from a zipfile.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24960


File: python.info,  Node: C API<50>,  Prev: Tools/Demos<27>,  Up: Python 3 7 0 alpha 4

1.23.57.7 C API
...............

   - bpo-32030(1): Py_Initialize() doesn't reset the memory allocators
     to default if the ‘PYTHONMALLOC’ environment variable is not set.

   - bpo-29084(2): Undocumented C API for OrderedDict has been excluded
     from the limited C API. It was added by mistake and actually never
     worked in the limited C API.

   - bpo-32264(3): Moved the pygetopt.h header into internal/, since it
     has no public APIs.

   - bpo-32241(4): ‘Py_SetProgramName()’ and ‘Py_SetPythonHome()’ now
     take the ‘const wchar *’ arguments instead of ‘wchar *’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32030

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29084

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32264

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32241


File: python.info,  Node: Python 3 7 0 alpha 3,  Next: Python 3 7 0 alpha 2,  Prev: Python 3 7 0 alpha 4,  Up: Changelog（更動日誌）

1.23.58 Python 3.7.0 alpha 3
----------------------------

'Release date: 2017-12-05'

* Menu:

* Core and Builtins: Core and Builtins<57>.
* Library: Library<57>.
* Documentation: Documentation<51>.
* Tests: Tests<52>.
* Build: Build<54>.
* Windows: Windows<50>.
* macOS: macOS<41>.
* IDLE: IDLE<41>.
* Tools/Demos: Tools/Demos<28>.
* C API: C API<51>.


File: python.info,  Node: Core and Builtins<57>,  Next: Library<57>,  Up: Python 3 7 0 alpha 3

1.23.58.1 Core and Builtins
...........................

   - bpo-32176(1): co_flags.CO_NOFREE is now always set correctly by the
     code object constructor based on freevars and cellvars, rather than
     needing to be set correctly by the caller.  This ensures it will be
     cleared automatically when additional cell references are injected
     into a modified code object and function.

   - bpo-10544(2): Yield expressions are now deprecated in
     comprehensions and generator expressions.  They are still permitted
     in the definition of the outermost iterable, as that is evaluated
     directly in the enclosing scope.

   - bpo-32137(3): The repr of deeply nested dict now raises a
     RecursionError instead of crashing due to a stack overflow.

   - bpo-32096(4): Revert memory allocator changes in the C API: move
     structures back from _PyRuntime to Objects/obmalloc.c.  The memory
     allocators are once again initialized statically, and so
     PyMem_RawMalloc() and Py_DecodeLocale() can be called before
     _PyRuntime_Initialize().

   - bpo-32043(5): Add a new "developer mode": new "-X dev" command line
     option to enable debug checks at runtime.

   - bpo-32023(6): SyntaxError is now correctly raised when a generator
     expression without parenthesis is used instead of an inheritance
     list in a class definition.  The duplication of the parentheses can
     be omitted only on calls.

   - bpo-32012(7): SyntaxError is now correctly raised when a generator
     expression without parenthesis is passed as an argument, but
     followed by a trailing comma.  A generator expression always needs
     to be directly inside a set of parentheses and cannot have a comma
     on either side.

   - bpo-28180(8): A new internal ‘_Py_SetLocaleFromEnv(category)’
     helper function has been added in order to improve the consistency
     of behaviour across different ‘libc’ implementations (e.g.  Android
     doesn't support setting the locale from the environment by
     default).

   - bpo-31949(9): Fixed several issues in printing tracebacks
     (PyTraceBack_Print()).  Setting sys.tracebacklimit to 0 or less now
     suppresses printing tracebacks.  Setting sys.tracebacklimit to None
     now causes using the default limit.  Setting sys.tracebacklimit to
     an integer larger than LONG_MAX now means using the limit LONG_MAX
     rather than the default limit.  Fixed integer overflows in the case
     of more than ‘2**31’ traceback items on Windows.  Fixed output
     errors handling.

   - bpo-30696(10): Fix the interactive interpreter looping endlessly
     when no memory.

   - bpo-20047(11): Bytearray methods partition() and rpartition() now
     accept only bytes-like objects as separator, as documented.  In
     particular they now raise TypeError rather of returning a bogus
     result when an integer is passed as a separator.

   - bpo-21720(12): BytesWarning no longer emitted when the 'fromlist'
     argument of ‘__import__()’ or the ‘__all__’ attribute of the module
     contain bytes instances.

   - bpo-31845(13): Environment variables are once more read correctly
     at interpreter startup.

   - bpo-28936(14): Ensure that lexically first syntax error involving a
     parameter and ‘global’ or ‘nonlocal’ is detected first at a given
     scope.  Patch by Ivan Levkivskyi.

   - bpo-31825(15): Fixed OverflowError in the 'unicode-escape' codec
     and in codecs.escape_decode() when decode an escaped non-ascii
     byte.

   - bpo-31618(16): The per-frame tracing logic added in 3.7a1 has been
     altered so that ‘frame->f_lineno’ is updated before either ‘"line"’
     or ‘"opcode"’ events are emitted.  Previously, opcode events were
     emitted first, and therefore would occasionally see stale line
     numbers on the frame.  The behavior of this feature has changed
     slightly as a result: when both ‘f_trace_lines’ and
     ‘f_trace_opcodes’ are enabled, line events now occur first.

   - bpo-28603(17): Print the full context/cause chain of exceptions on
     interpreter exit, even if an exception in the chain is unhashable
     or compares equal to later ones.  Patch by Zane Bitter.

   - bpo-31786(18): Fix timeout rounding in the select module to round
     correctly negative timeouts between -1.0 and 0.0.  The functions
     now block waiting for events as expected.  Previously, the call was
     incorrectly non-blocking.  Patch by Pablo Galindo.

   - bpo-31781(19): Prevent crashes when calling methods of an
     uninitialized ‘zipimport.zipimporter’ object.  Patch by Oren
     Milman.

   - bpo-30399(20): Standard repr() of BaseException with a single
     argument no longer contains redundant trailing comma.

   - bpo-31626(21): Fixed a bug in debug memory allocator.  There was a
     write to freed memory after shrinking a memory block.

   - bpo-30817(22): ‘PyErr_PrintEx()’ clears now the ignored exception
     that may be raised by ‘_PySys_SetObjectId()’, for example when no
     memory.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32176

   (2) https://bugs.python.org/issue?@action=redirect&bpo=10544

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32137

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32096

   (5) https://bugs.python.org/issue?@action=redirect&bpo=32043

   (6) https://bugs.python.org/issue?@action=redirect&bpo=32023

   (7) https://bugs.python.org/issue?@action=redirect&bpo=32012

   (8) https://bugs.python.org/issue?@action=redirect&bpo=28180

   (9) https://bugs.python.org/issue?@action=redirect&bpo=31949

   (10) https://bugs.python.org/issue?@action=redirect&bpo=30696

   (11) https://bugs.python.org/issue?@action=redirect&bpo=20047

   (12) https://bugs.python.org/issue?@action=redirect&bpo=21720

   (13) https://bugs.python.org/issue?@action=redirect&bpo=31845

   (14) https://bugs.python.org/issue?@action=redirect&bpo=28936

   (15) https://bugs.python.org/issue?@action=redirect&bpo=31825

   (16) https://bugs.python.org/issue?@action=redirect&bpo=31618

   (17) https://bugs.python.org/issue?@action=redirect&bpo=28603

   (18) https://bugs.python.org/issue?@action=redirect&bpo=31786

   (19) https://bugs.python.org/issue?@action=redirect&bpo=31781

   (20) https://bugs.python.org/issue?@action=redirect&bpo=30399

   (21) https://bugs.python.org/issue?@action=redirect&bpo=31626

   (22) https://bugs.python.org/issue?@action=redirect&bpo=30817


File: python.info,  Node: Library<57>,  Next: Documentation<51>,  Prev: Core and Builtins<57>,  Up: Python 3 7 0 alpha 3

1.23.58.2 Library
.................

   - bpo-28556(1): Two minor fixes for ‘typing’ module: allow shallow
     copying instances of generic classes, improve interaction of
     ‘__init_subclass__’ with generics.  Original PRs by Ivan
     Levkivskyi.

   - bpo-32214(2): PEP 557, Data Classes.  Provides a decorator which
     adds boilerplate methods to classes which use type annotations so
     specify fields.

   - bpo-27240(3): The header folding algorithm for the new email
     policies has been rewritten, which also fixes bpo-30788(4),
     bpo-31831(5), and bpo-32182(6).  In particular, RFC2231 folding is
     now done correctly.

   - bpo-32186(7): io.FileIO.readall() and io.FileIO.read() now release
     the GIL when getting the file size.  Fixed hang of all threads with
     inaccessible NFS server.  Patch by Nir Soffer.

   - bpo-32101(8): Add *note sys.flags.dev_mode: 19a7. flag

   - bpo-32154(9): The ‘asyncio.windows_utils.socketpair()’ function has
     been removed: use directly *note socket.socketpair(): b9c. which is
     available on all platforms since Python 3.5 (before, it wasn't
     available on Windows).  ‘asyncio.windows_utils.socketpair()’ was
     just an alias to ‘socket.socketpair’ on Python 3.5 and newer.

   - bpo-32089(10): warnings: In development (-X dev) and debug mode
     (pydebug build), use the "default" action for ResourceWarning,
     rather than the "always" action, in the default warnings filters.

   - bpo-32107(11): ‘uuid.getnode()’ now preferentially returns
     universally administered MAC addresses if available, over locally
     administered MAC addresses.  This makes a better guarantee for
     global uniqueness of UUIDs returned from ‘uuid.uuid1()’.  If only
     locally administered MAC addresses are available, the first such
     one found is returned.

   - bpo-23033(12): Wildcard is now supported in hostname when it is one
     and only character in the left most segment of hostname in second
     argument of ‘ssl.match_hostname()’.  Patch by Mandeep Singh.

   - bpo-12239(13): Make ‘msilib.SummaryInformation.GetProperty()’
     return ‘None’ when the value of property is ‘VT_EMPTY’.  Initial
     patch by Mark Mc Mahon.

   - bpo-28334(14): Use *note os.path.expanduser(): 9b8. to find the
     ‘~/.netrc’ file in *note netrc.netrc: 17c4.  If it does not exist,
     *note FileNotFoundError: e67. is raised.  Patch by Dimitri
     Merejkowsky.

   - bpo-32121(15): Made ‘tracemalloc.Traceback’ behave more like the
     traceback module, sorting the frames from oldest to most recent.
     ‘Traceback.format()’ now accepts negative 'limit', truncating the
     result to the ‘abs(limit)’ oldest frames.  To get the old
     behaviour, one can use the new 'most_recent_first' argument to
     ‘Traceback.format()’.  (Patch by Jesse Bakker.)

   - bpo-31325(16): Fix wrong usage of *note collections.namedtuple():
     1ae. in the *note RobotFileParser.parse(): 19a8. method.  Initial
     patch by Robin Wellner.

   - bpo-12382(17): ‘msilib.OpenDatabase()’ now raises a better
     exception message when it couldn't open or create an MSI file.
     Initial patch by William Tisäter.

   - bpo-19610(18): ‘setup()’ now warns about invalid types for some
     fields.  The ‘distutils.dist.Distribution’ class now warns when
     ‘classifiers’, ‘keywords’ and ‘platforms’ fields are not specified
     as a list or a string.

   - bpo-32071(19): Added the ‘-k’ command-line option to ‘python -m
     unittest’ to run only tests that match the given pattern(s).

   - bpo-10049(20): Added 'nullcontext' no-op context manager to
     contextlib.  This provides a simpler and faster alternative to
     ExitStack() when handling optional context managers.

   - bpo-28684(21): The new test.support.skip_unless_bind_unix_socket()
     decorator is used here to skip asyncio tests that fail because the
     platform lacks a functional bind() function for unix domain sockets
     (as it is the case for non root users on the recent Android
     versions that run now SELinux in enforcing mode).

   - bpo-32110(22): ‘codecs.StreamReader.read(n)’ now returns not more
     than 'n' characters/bytes for non-negative 'n'.  This makes it
     compatible with ‘read()’ methods of other file-like objects.

   - bpo-27535(23): The warnings module doesn't leak memory anymore in
     the hidden warnings registry for the "ignore" action of warnings
     filters.  warn_explicit() function doesn't add the warning key to
     the registry anymore for the "ignore" action.

   - bpo-32088(24): warnings: When Python is build is debug mode
     (‘Py_DEBUG’), *note DeprecationWarning: 18b, *note
     PendingDeprecationWarning: 86d. and *note ImportWarning: 4a2.
     warnings are now displayed by default.

   - bpo-1647489(25): Fixed searching regular expression patterns that
     could match an empty string.  Non-empty string can now be correctly
     found after matching an empty string.

   - bpo-25054(26): Added support of splitting on a pattern that could
     match an empty string.

   - bpo-32072(27): Fixed issues with binary plists: Fixed saving
     bytearrays.  Identical objects will be saved only once.  Equal
     references will be load as identical objects.  Added support for
     saving and loading recursive data structures.

   - bpo-32069(28): Drop legacy SSL transport from asyncio,
     ssl.MemoryBIO is always used anyway.

   - bpo-32066(29): asyncio: Support pathlib.Path in
     create_unix_connection; sock arg should be optional

   - bpo-32046(30): Updates 2to3 to convert from
     operator.isCallable(obj) to callable(obj).  Patch by Donghee Na.

   - bpo-32018(31): inspect.signature should follow PEP 8(32), if the
     parameter has an annotation and a default value.  Patch by Donghee
     Na.

   - bpo-32025(33): Add time.thread_time() and time.thread_time_ns()

   - bpo-32037(34): Integers that fit in a signed 32-bit integer will be
     now pickled with protocol 0 using the INT opcode.  This will
     decrease the size of a pickle, speed up pickling and unpickling,
     and make these integers be unpickled as int instances in Python 2.

   - bpo-32034(35): Make asyncio.IncompleteReadError and
     LimitOverrunError pickleable.

   - bpo-32015(36): Fixed the looping of asyncio in the case of
     reconnection the socket during waiting async read/write from/to the
     socket.

   - bpo-32011(37): Restored support of loading marshal files with the
     TYPE_INT64 code.  These files can be produced in Python 2.7.

   - bpo-28369(38): Enhance add_reader/writer check that socket is not
     used by some transport.  Before, only cases when add_reader/writer
     were called with an int FD were supported.  Now the check is
     implemented correctly for all file-like objects.

   - bpo-31976(39): Fix race condition when flushing a file is slow,
     which can cause a segfault if closing the file from another thread.

   - bpo-31985(40): Formally deprecated aifc.openfp, sunau.openfp, and
     wave.openfp.  Since change 7bc817d5ba917528e8bd07ec461c635291e7b06a
     in 1993, openfp in each of the three modules had been pointing to
     that module's open function as a matter of backwards compatibility,
     though it had been both untested and undocumented.

   - bpo-21862(41): cProfile command line now accepts ‘-m module_name’
     as an alternative to script path.  Patch by Sanyam Khurana.

   - bpo-31970(42): Reduce performance overhead of asyncio debug mode.

   - bpo-31843(43): 'database' argument of sqlite3.connect() now accepts
     a *note path-like object: ac2, instead of just a string.

   - bpo-31945(44): Add Configurable 'blocksize' to ‘HTTPConnection’ and
     ‘HTTPSConnection’ for improved upload throughput.  Patch by Nir
     Soffer.

   - bpo-31943(45): Add a ‘cancelled()’ method to *note asyncio.Handle:
     19a9.  Patch by Marat Sharafutdinov.

   - bpo-9678(46): Fixed determining the MAC address in the uuid module:
     Using ifconfig on NetBSD and OpenBSD. Using arp on Linux, FreeBSD,
     NetBSD and OpenBSD. Based on patch by Takayuki Shimizukawa.

   - bpo-30057(47): Fix potential missed signal in signal.signal().

   - bpo-31933(48): Fix Blake2 params leaf_size and node_offset on big
     endian platforms.  Patch by Jack O'Connor.

   - bpo-21423(49): Add an initializer argument to
     {Process,Thread}PoolExecutor

   - bpo-31927(50): Fixed compilation of the socket module on NetBSD 8.
     Fixed assertion failure or reading arbitrary data when parse a
     AF_BLUETOOTH address on NetBSD and DragonFly BSD.

   - bpo-27666(51): Fixed stack corruption in curses.box() and
     curses.ungetmouse() when the size of types chtype or mmask_t is
     less than the size of C long.  curses.box() now accepts characters
     as arguments.  Based on patch by Steve Fink.

   - bpo-31917(52): Add 3 new clock identifiers: *note
     time.CLOCK_BOOTTIME: b34, *note time.CLOCK_PROF: b36. and *note
     time.CLOCK_UPTIME: b37.

   - bpo-31897(53): plistlib now catches more errors when read binary
     plists and raises InvalidFileException instead of unexpected
     exceptions.

   - bpo-25720(54): Fix the method for checking pad state of curses
     WINDOW. Patch by Masayuki Yamamoto.

   - bpo-31893(55): Fixed the layout of the kqueue_event structure on
     OpenBSD and NetBSD. Fixed the comparison of the kqueue_event
     objects.

   - bpo-31891(56): Fixed building the curses module on NetBSD.

   - bpo-31884(57): added required constants to subprocess module for
     setting priority on windows

   - bpo-28281(58): Remove year (1-9999) limits on the
     Calendar.weekday() function.  Patch by Mark Gollahon.

   - bpo-31702(59): crypt.mksalt() now allows to specify the number of
     rounds for SHA-256 and SHA-512 hashing.

   - bpo-30639(60): *note inspect.getfile(): 19aa. no longer computes
     the repr of unknown objects to display in an error message, to
     protect against badly behaved custom reprs.

   - bpo-30768(61): Fix the pthread+semaphore implementation of
     PyThread_acquire_lock_timed() when called with timeout > 0 and
     intr_flag=0: recompute the timeout if sem_timedwait() is
     interrupted by a signal (EINTR). See also the PEP 475(62).

   - bpo-31854(63): Add ‘mmap.ACCESS_DEFAULT’ constant.

   - bpo-31834(64): Use optimized code for BLAKE2 only with SSSE3+.  The
     pure SSE2 implementation is slower than the pure C reference
     implementation.

   - bpo-28292(65): Calendar.itermonthdates() will now consistently
     raise an exception when a date falls outside of the 0001-01-01
     through 9999-12-31 range.  To support applications that cannot
     tolerate such exceptions, the new methods itermonthdays3() and
     itermonthdays4() are added.  The new methods return tuples and are
     not restricted by the range supported by datetime.date.

   - bpo-28564(66): The shutil.rmtree() function has been sped up to
     20-40%.  This was done using the os.scandir() function.

   - bpo-28416(67): Instances of pickle.Pickler subclass with the
     persistent_id() method and pickle.Unpickler subclass with the
     persistent_load() method no longer create reference cycles.

   - bpo-31653(68): Don't release the GIL if we can acquire a
     multiprocessing semaphore immediately.

   - bpo-28326(69): Fix multiprocessing.Process when stdout and/or
     stderr is closed or None.

   - bpo-20825(70): Add ‘subnet_of’ and ‘superset_of’ containment tests
     to *note ipaddress.IPv6Network: 1e4. and *note
     ipaddress.IPv4Network: 1e3.  Patch by Michel Albert and Cheryl
     Sabella.

   - bpo-31827(71): Remove the os.stat_float_times() function.  It was
     introduced in Python 2.3 for backward compatibility with Python
     2.2, and was deprecated since Python 3.1.

   - bpo-31756(72): Add a ‘subprocess.Popen(text=False)’ keyword
     argument to ‘subprocess’ functions to be more explicit about when
     the library should attempt to decode outputs into text.  Patch by
     Andrew Clegg.

   - bpo-31819(73): Add AbstractEventLoop.sock_recv_into().

   - bpo-31457(74): If nested log adapters are used, the inner
     ‘process()’ methods are no longer omitted.

   - bpo-31457(75): The ‘manager’ property on LoggerAdapter objects is
     now properly settable.

   - bpo-31806(76): Fix timeout rounding in time.sleep(),
     threading.Lock.acquire() and socket.socket.settimeout() to round
     correctly negative timeouts between -1.0 and 0.0.  The functions
     now block waiting for events as expected.  Previously, the call was
     incorrectly non-blocking.  Patch by Pablo Galindo.

   - bpo-31803(77): time.clock() and time.get_clock_info('clock') now
     emit a DeprecationWarning warning.

   - bpo-31800(78): Extended support for parsing UTC offsets.  strptime
     '%z' can now parse the output generated by datetime.isoformat,
     including seconds and microseconds.

   - bpo-28603(79): traceback: Fix a TypeError that occurred during
     printing of exception tracebacks when either the current exception
     or an exception in its context/cause chain is unhashable.  Patch by
     Zane Bitter.

   - bpo-30541(80): Add new function to seal a mock and prevent the
     automatically creation of child mocks.  Patch by Mario Corchero.

   - bpo-31784(81): Implement the PEP 564(82), add new 6 new functions
     with nanosecond resolution to the *note time: d7. module: *note
     clock_gettime_ns(): a85, *note clock_settime_ns(): a86, *note
     monotonic_ns(): a87, *note perf_counter_ns(): a88, *note
     process_time_ns(): a89, *note time_ns(): a8a.

   - bpo-30143(83): 2to3 now generates a code that uses abstract
     collection classes from collections.abc rather than collections.

   - bpo-31770(84): Prevent a crash when calling the ‘__init__()’ method
     of a ‘sqlite3.Cursor’ object more than once.  Patch by Oren Milman.

   - bpo-31764(85): Prevent a crash in ‘sqlite3.Cursor.close()’ in case
     the ‘Cursor’ object is uninitialized.  Patch by Oren Milman.

   - bpo-31752(86): Fix possible crash in timedelta constructor called
     with custom integers.

   - bpo-31620(87): an empty asyncio.Queue now doesn't leak memory when
     queue.get pollers timeout

   - bpo-31690(88): Allow the flags re.ASCII, re.LOCALE, and re.UNICODE
     to be used as group flags for regular expressions.

   - bpo-30349(89): FutureWarning is now emitted if a regular expression
     contains character set constructs that will change semantically in
     the future (nested sets and set operations).

   - bpo-31664(90): Added support for the Blowfish hashing in the crypt
     module.

   - bpo-31632(91): Fix method set_protocol() of class
     _SSLProtocolTransport in asyncio module.  This method was
     previously modifying a wrong reference to the protocol.

   - bpo-15037(92): Added a workaround for getkey() in curses for
     ncurses 5.7 and earlier.

   - bpo-31307(93): Allow use of bytes objects for arguments to *note
     configparser.ConfigParser.read(): 13d3.  Patch by Vincent Michel.

   - bpo-31334(94): Fix ‘poll.poll([timeout])’ in the ‘select’ module
     for arbitrary negative timeouts on all OSes where it can only be a
     non-negative integer or -1.  Patch by Riccardo Coccioli.

   - bpo-31310(95): multiprocessing's semaphore tracker should be
     launched again if crashed.

   - bpo-31308(96): Make multiprocessing's forkserver process immune to
     Ctrl-C and other user interruptions.  If it crashes, restart it
     when necessary.

   - bpo-31245(97): Added support for AF_UNIX socket in asyncio
     ‘create_datagram_endpoint’.

   - bpo-30553(98): Add HTTP/2 status code 421 (Misdirected Request) to
     *note http.HTTPStatus: 8a5.  Patch by Vitor Pereira.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28556

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32214

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27240

   (4) https://bugs.python.org/issue?@action=redirect&bpo=30788

   (5) https://bugs.python.org/issue?@action=redirect&bpo=31831

   (6) https://bugs.python.org/issue?@action=redirect&bpo=32182

   (7) https://bugs.python.org/issue?@action=redirect&bpo=32186

   (8) https://bugs.python.org/issue?@action=redirect&bpo=32101

   (9) https://bugs.python.org/issue?@action=redirect&bpo=32154

   (10) https://bugs.python.org/issue?@action=redirect&bpo=32089

   (11) https://bugs.python.org/issue?@action=redirect&bpo=32107

   (12) https://bugs.python.org/issue?@action=redirect&bpo=23033

   (13) https://bugs.python.org/issue?@action=redirect&bpo=12239

   (14) https://bugs.python.org/issue?@action=redirect&bpo=28334

   (15) https://bugs.python.org/issue?@action=redirect&bpo=32121

   (16) https://bugs.python.org/issue?@action=redirect&bpo=31325

   (17) https://bugs.python.org/issue?@action=redirect&bpo=12382

   (18) https://bugs.python.org/issue?@action=redirect&bpo=19610

   (19) https://bugs.python.org/issue?@action=redirect&bpo=32071

   (20) https://bugs.python.org/issue?@action=redirect&bpo=10049

   (21) https://bugs.python.org/issue?@action=redirect&bpo=28684

   (22) https://bugs.python.org/issue?@action=redirect&bpo=32110

   (23) https://bugs.python.org/issue?@action=redirect&bpo=27535

   (24) https://bugs.python.org/issue?@action=redirect&bpo=32088

   (25) https://bugs.python.org/issue?@action=redirect&bpo=1647489

   (26) https://bugs.python.org/issue?@action=redirect&bpo=25054

   (27) https://bugs.python.org/issue?@action=redirect&bpo=32072

   (28) https://bugs.python.org/issue?@action=redirect&bpo=32069

   (29) https://bugs.python.org/issue?@action=redirect&bpo=32066

   (30) https://bugs.python.org/issue?@action=redirect&bpo=32046

   (31) https://bugs.python.org/issue?@action=redirect&bpo=32018

   (32) https://peps.python.org/pep-0008/

   (33) https://bugs.python.org/issue?@action=redirect&bpo=32025

   (34) https://bugs.python.org/issue?@action=redirect&bpo=32037

   (35) https://bugs.python.org/issue?@action=redirect&bpo=32034

   (36) https://bugs.python.org/issue?@action=redirect&bpo=32015

   (37) https://bugs.python.org/issue?@action=redirect&bpo=32011

   (38) https://bugs.python.org/issue?@action=redirect&bpo=28369

   (39) https://bugs.python.org/issue?@action=redirect&bpo=31976

   (40) https://bugs.python.org/issue?@action=redirect&bpo=31985

   (41) https://bugs.python.org/issue?@action=redirect&bpo=21862

   (42) https://bugs.python.org/issue?@action=redirect&bpo=31970

   (43) https://bugs.python.org/issue?@action=redirect&bpo=31843

   (44) https://bugs.python.org/issue?@action=redirect&bpo=31945

   (45) https://bugs.python.org/issue?@action=redirect&bpo=31943

   (46) https://bugs.python.org/issue?@action=redirect&bpo=9678

   (47) https://bugs.python.org/issue?@action=redirect&bpo=30057

   (48) https://bugs.python.org/issue?@action=redirect&bpo=31933

   (49) https://bugs.python.org/issue?@action=redirect&bpo=21423

   (50) https://bugs.python.org/issue?@action=redirect&bpo=31927

   (51) https://bugs.python.org/issue?@action=redirect&bpo=27666

   (52) https://bugs.python.org/issue?@action=redirect&bpo=31917

   (53) https://bugs.python.org/issue?@action=redirect&bpo=31897

   (54) https://bugs.python.org/issue?@action=redirect&bpo=25720

   (55) https://bugs.python.org/issue?@action=redirect&bpo=31893

   (56) https://bugs.python.org/issue?@action=redirect&bpo=31891

   (57) https://bugs.python.org/issue?@action=redirect&bpo=31884

   (58) https://bugs.python.org/issue?@action=redirect&bpo=28281

   (59) https://bugs.python.org/issue?@action=redirect&bpo=31702

   (60) https://bugs.python.org/issue?@action=redirect&bpo=30639

   (61) https://bugs.python.org/issue?@action=redirect&bpo=30768

   (62) https://peps.python.org/pep-0475/

   (63) https://bugs.python.org/issue?@action=redirect&bpo=31854

   (64) https://bugs.python.org/issue?@action=redirect&bpo=31834

   (65) https://bugs.python.org/issue?@action=redirect&bpo=28292

   (66) https://bugs.python.org/issue?@action=redirect&bpo=28564

   (67) https://bugs.python.org/issue?@action=redirect&bpo=28416

   (68) https://bugs.python.org/issue?@action=redirect&bpo=31653

   (69) https://bugs.python.org/issue?@action=redirect&bpo=28326

   (70) https://bugs.python.org/issue?@action=redirect&bpo=20825

   (71) https://bugs.python.org/issue?@action=redirect&bpo=31827

   (72) https://bugs.python.org/issue?@action=redirect&bpo=31756

   (73) https://bugs.python.org/issue?@action=redirect&bpo=31819

   (74) https://bugs.python.org/issue?@action=redirect&bpo=31457

   (75) https://bugs.python.org/issue?@action=redirect&bpo=31457

   (76) https://bugs.python.org/issue?@action=redirect&bpo=31806

   (77) https://bugs.python.org/issue?@action=redirect&bpo=31803

   (78) https://bugs.python.org/issue?@action=redirect&bpo=31800

   (79) https://bugs.python.org/issue?@action=redirect&bpo=28603

   (80) https://bugs.python.org/issue?@action=redirect&bpo=30541

   (81) https://bugs.python.org/issue?@action=redirect&bpo=31784

   (82) https://peps.python.org/pep-0564/

   (83) https://bugs.python.org/issue?@action=redirect&bpo=30143

   (84) https://bugs.python.org/issue?@action=redirect&bpo=31770

   (85) https://bugs.python.org/issue?@action=redirect&bpo=31764

   (86) https://bugs.python.org/issue?@action=redirect&bpo=31752

   (87) https://bugs.python.org/issue?@action=redirect&bpo=31620

   (88) https://bugs.python.org/issue?@action=redirect&bpo=31690

   (89) https://bugs.python.org/issue?@action=redirect&bpo=30349

   (90) https://bugs.python.org/issue?@action=redirect&bpo=31664

   (91) https://bugs.python.org/issue?@action=redirect&bpo=31632

   (92) https://bugs.python.org/issue?@action=redirect&bpo=15037

   (93) https://bugs.python.org/issue?@action=redirect&bpo=31307

   (94) https://bugs.python.org/issue?@action=redirect&bpo=31334

   (95) https://bugs.python.org/issue?@action=redirect&bpo=31310

   (96) https://bugs.python.org/issue?@action=redirect&bpo=31308

   (97) https://bugs.python.org/issue?@action=redirect&bpo=31245

   (98) https://bugs.python.org/issue?@action=redirect&bpo=30553


File: python.info,  Node: Documentation<51>,  Next: Tests<52>,  Prev: Library<57>,  Up: Python 3 7 0 alpha 3

1.23.58.3 Documentation
.......................

   - bpo-32105(1): Added asyncio.BaseEventLoop.connect_accepted_socket
     versionadded marker.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32105


File: python.info,  Node: Tests<52>,  Next: Build<54>,  Prev: Documentation<51>,  Up: Python 3 7 0 alpha 3

1.23.58.4 Tests
...............

   - bpo-31380(1): Skip test_httpservers test_undecodable_file on macOS:
     fails on APFS.

   - bpo-31705(2): Skip test_socket.test_sha256() on Linux kernel older
     than 4.5.  The test fails with ENOKEY on kernel 3.10 (on ppc64le).
     A fix was merged into the kernel 4.5.

   - bpo-32138(3): Skip on Android test_faulthandler tests that raise
     SIGSEGV and remove the test.support.requires_android_level
     decorator.

   - bpo-32136(4): The runtime embedding tests have been split out from
     ‘Lib/test/test_capi.py’ into a new ‘Lib/test/test_embed.py’ file.

   - bpo-28668(5): test.support.requires_multiprocessing_queue is
     removed.  Skip tests with
     test.support.import_module('multiprocessing.synchronize') instead
     when the semaphore implementation is broken or missing.

   - bpo-32126(6): Skip test_get_event_loop_new_process in
     test.test_asyncio.test_events when sem_open() is not functional.

   - bpo-31174(7): Fix test_tools.test_unparse: DirectoryTestCase now
     stores the names sample to always test the same files.  It prevents
     false alarms when hunting reference leaks.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31380

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31705

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32138

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32136

   (5) https://bugs.python.org/issue?@action=redirect&bpo=28668

   (6) https://bugs.python.org/issue?@action=redirect&bpo=32126

   (7) https://bugs.python.org/issue?@action=redirect&bpo=31174


File: python.info,  Node: Build<54>,  Next: Windows<50>,  Prev: Tests<52>,  Up: Python 3 7 0 alpha 3

1.23.58.5 Build
...............

   - bpo-28538(1): Revert the previous changes, the if_nameindex
     structure is defined by Unified Headers.

   - bpo-28762(2): Revert the last commit, the F_LOCK macro is defined
     by Android Unified Headers.

   - bpo-29040(3): Support building Android with Unified Headers.  The
     first NDK release to support Unified Headers is android-ndk-r14.

   - bpo-32059(4): ‘detect_modules()’ in ‘setup.py’ now also searches
     the sysroot paths when cross-compiling.

   - bpo-31957(5): Fixes Windows SDK version detection when building for
     Windows.

   - bpo-31609(6): Fixes quotes in PCbuild/clean.bat

   - bpo-31934(7): Abort the build when building out of a not clean
     source tree.

   - bpo-31926(8): Fixed Argument Clinic sometimes causing compilation
     errors when there was more than one function and/or method in a .c
     file with the same name.

   - bpo-28791(9): Update Windows builds to use SQLite 3.21.0.

   - bpo-28791(10): Update OS X installer to use SQLite 3.21.0.

   - bpo-28643(11): Record profile-opt build progress with stamp files.

   - bpo-31866(12): Finish removing support for AtheOS.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28538

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28762

   (3) https://bugs.python.org/issue?@action=redirect&bpo=29040

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32059

   (5) https://bugs.python.org/issue?@action=redirect&bpo=31957

   (6) https://bugs.python.org/issue?@action=redirect&bpo=31609

   (7) https://bugs.python.org/issue?@action=redirect&bpo=31934

   (8) https://bugs.python.org/issue?@action=redirect&bpo=31926

   (9) https://bugs.python.org/issue?@action=redirect&bpo=28791

   (10) https://bugs.python.org/issue?@action=redirect&bpo=28791

   (11) https://bugs.python.org/issue?@action=redirect&bpo=28643

   (12) https://bugs.python.org/issue?@action=redirect&bpo=31866


File: python.info,  Node: Windows<50>,  Next: macOS<41>,  Prev: Build<54>,  Up: Python 3 7 0 alpha 3

1.23.58.6 Windows
.................

   - bpo-1102(1): Return ‘None’ when ‘View.Fetch()’ returns
     ‘ERROR_NO_MORE_ITEMS’ instead of raising ‘MSIError’.  Initial patch
     by Anthony Tuininga.

   - bpo-31944(2): Fixes Modify button in Apps and Features dialog.

   - bpo-20486(3): Implement the ‘Database.Close()’ method to help
     closing MSI database objects.

   - bpo-31857(4): Make the behavior of USE_STACKCHECK deterministic in
     a multi-threaded environment.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1102

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31944

   (3) https://bugs.python.org/issue?@action=redirect&bpo=20486

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31857


File: python.info,  Node: macOS<41>,  Next: IDLE<41>,  Prev: Windows<50>,  Up: Python 3 7 0 alpha 3

1.23.58.7 macOS
...............

   - bpo-31392(1): Update macOS installer to use OpenSSL 1.0.2m

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31392


File: python.info,  Node: IDLE<41>,  Next: Tools/Demos<28>,  Prev: macOS<41>,  Up: Python 3 7 0 alpha 3

1.23.58.8 IDLE
..............

   - bpo-32207(1): Improve tk event exception tracebacks in IDLE. When
     tk event handling is driven by IDLE's run loop, a confusing and
     distracting queue.EMPTY traceback context is no longer added to tk
     event exception tracebacks.  The traceback is now the same as when
     event handling is driven by user code.  Patch based on a suggestion
     by Serhiy Storchaka.

   - bpo-32164(2): Delete unused file idlelib/tabbedpages.py.  Use of
     TabbedPageSet in configdialog was replaced by ttk.Notebook.

   - bpo-32100(3): IDLE: Fix old and new bugs in pathbrowser; improve
     tests.  Patch mostly by Cheryl Sabella.

   - bpo-31858(4): IDLE - Restrict shell prompt manipulation to the
     shell.  Editor and output windows only see an empty last prompt
     line.  This simplifies the code and fixes a minor bug when newline
     is inserted.  Sys.ps1, if present, is read on Shell start-up, but
     is not set or changed.

   - bpo-31860(5): The font sample in the IDLE configuration dialog is
     now editable.  Changes persist while IDLE remains open

   - bpo-31836(6): Test_code_module now passes if run after test_idle,
     which sets ps1.  The code module uses sys.ps1 if present or sets it
     to '>>> ' if not.  Test_code_module now properly tests both
     behaviors.  Ditto for ps2.

   - bpo-28603(7): Fix a TypeError that caused a shell restart when
     printing a traceback that includes an exception that is unhashable.
     Patch by Zane Bitter.

   - bpo-13802(8): Use non-Latin characters in the IDLE's Font settings
     sample.  Even if one selects a font that defines a limited subset
     of the unicode Basic Multilingual Plane, tcl/tk will use other
     fonts that define a character.  The expanded example give users of
     non-Latin characters a better idea of what they might see in IDLE's
     shell and editors.  To make room for the expanded sample, frames on
     the Font tab are re-arranged.  The Font/Tabs help explains a bit
     about the additions.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32207

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32164

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32100

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31858

   (5) https://bugs.python.org/issue?@action=redirect&bpo=31860

   (6) https://bugs.python.org/issue?@action=redirect&bpo=31836

   (7) https://bugs.python.org/issue?@action=redirect&bpo=28603

   (8) https://bugs.python.org/issue?@action=redirect&bpo=13802


File: python.info,  Node: Tools/Demos<28>,  Next: C API<51>,  Prev: IDLE<41>,  Up: Python 3 7 0 alpha 3

1.23.58.9 Tools/Demos
.....................

   - bpo-32159(1): Remove CVS and Subversion tools: remove svneol.py and
     treesync.py scripts.  CPython migrated from CVS to Subversion, to
     Mercurial, and then to Git.  CVS and Subversion are no longer used
     to develop CPython.

   - bpo-30722(2): Make redemo work with Python 3.6 and newer versions.
     Also, remove the ‘LOCALE’ option since it doesn't work with string
     patterns in Python 3.  Patch by Christoph Sarnowski.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32159

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30722


File: python.info,  Node: C API<51>,  Prev: Tools/Demos<28>,  Up: Python 3 7 0 alpha 3

1.23.58.10 C API
................

   - bpo-20891(1): Fix PyGILState_Ensure().  When PyGILState_Ensure() is
     called in a non-Python thread before PyEval_InitThreads(), only
     call PyEval_InitThreads() after calling PyThreadState_New() to fix
     a crash.

   - bpo-32125(2): The ‘Py_UseClassExceptionsFlag’ flag has been
     removed.  It was deprecated and wasn't used anymore since Python
     2.0.

   - bpo-25612(3): Move the current exception state from the frame
     object to the co-routine.  This simplifies the interpreter and
     fixes a couple of obscure bugs caused by having swap exception
     state when entering or exiting a generator.

   - bpo-23699(4): Add Py_RETURN_RICHCOMPARE macro to reduce boilerplate
     code in rich comparison functions.

   - bpo-30697(5): The ‘PyExc_RecursionErrorInst’ singleton is removed
     and ‘PyErr_NormalizeException()’ does not use it anymore.  This
     singleton is persistent and its members being never cleared may
     cause a segfault during finalization of the interpreter.  See also
     bpo-22898(6).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=20891

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32125

   (3) https://bugs.python.org/issue?@action=redirect&bpo=25612

   (4) https://bugs.python.org/issue?@action=redirect&bpo=23699

   (5) https://bugs.python.org/issue?@action=redirect&bpo=30697

   (6) https://bugs.python.org/issue?@action=redirect&bpo=22898


File: python.info,  Node: Python 3 7 0 alpha 2,  Next: Python 3 7 0 alpha 1,  Prev: Python 3 7 0 alpha 3,  Up: Changelog（更動日誌）

1.23.59 Python 3.7.0 alpha 2
----------------------------

'Release date: 2017-10-16'

* Menu:

* Core and Builtins: Core and Builtins<58>.
* Library: Library<58>.
* Documentation: Documentation<52>.
* Build: Build<55>.
* IDLE: IDLE<42>.
* C API: C API<52>.


File: python.info,  Node: Core and Builtins<58>,  Next: Library<58>,  Up: Python 3 7 0 alpha 2

1.23.59.1 Core and Builtins
...........................

   - bpo-31558(1): ‘gc.freeze()’ is a new API that allows for moving all
     objects currently tracked by the garbage collector to a permanent
     generation, effectively removing them from future collection
     events.  This can be used to protect those objects from having
     their PyGC_Head mutated.  In effect, this enables great
     copy-on-write stability at fork().

   - bpo-31642(2): Restored blocking "from package import module" by
     setting sys.modules["package.module"] to None.

   - bpo-31708(3): Allow use of asynchronous generator expressions in
     synchronous functions.

   - bpo-31709(4): Drop support of asynchronous __aiter__.

   - bpo-30404(5): The -u option now makes the stdout and stderr streams
     unbuffered rather than line-buffered.

   - bpo-31619(6): Fixed a ValueError when convert a string with large
     number of underscores to integer with binary base.

   - bpo-31602(7): Fix an assertion failure in
     ‘zipimporter.get_source()’ in case of a bad ‘zlib.decompress()’.
     Patch by Oren Milman.

   - bpo-31592(8): Fixed an assertion failure in Python parser in case
     of a bad ‘unicodedata.normalize()’.  Patch by Oren Milman.

   - bpo-31588(9): Raise a ‘TypeError’ with a helpful error message when
     class creation fails due to a metaclass with a bad ‘__prepare__()’
     method.  Patch by Oren Milman.

   - bpo-31574(10): Importlib was instrumented with two dtrace probes to
     profile import timing.

   - bpo-31566(11): Fix an assertion failure in ‘_warnings.warn()’ in
     case of a bad ‘__name__’ global.  Patch by Oren Milman.

   - bpo-31506(12): Improved the error message logic for
     ‘object.__new__’ and ‘object.__init__’.

   - bpo-31505(13): Fix an assertion failure in ‘json’, in case
     ‘_json.make_encoder()’ received a bad ‘encoder()’ argument.  Patch
     by Oren Milman.

   - bpo-31492(14): Fix assertion failures in case of failing to import
     from a module with a bad ‘__name__’ attribute, and in case of
     failing to access an attribute of such a module.  Patch by Oren
     Milman.

   - bpo-31478(15): Fix an assertion failure in ‘_random.Random.seed()’
     in case the argument has a bad ‘__abs__()’ method.  Patch by Oren
     Milman.

   - bpo-31336(16): Speed up class creation by 10-20% by reducing the
     overhead in the necessary special method lookups.  Patch by Stefan
     Behnel.

   - bpo-31415(17): Add ‘-X importtime’ option to show how long each
     import takes.  It can be used to optimize application's startup
     time.  Support the *note PYTHONPROFILEIMPORTTIME: a98. as an
     equivalent way to enable this.

   - bpo-31410(18): Optimized calling wrapper and classmethod
     descriptors.

   - bpo-31353(19): PEP 553(20) - Add a new built-in called
     ‘breakpoint()’ which calls ‘sys.breakpointhook()’.  By default this
     imports ‘pdb’ and calls ‘pdb.set_trace()’, but users may override
     ‘sys.breakpointhook()’ to call whatever debugger they want.  The
     original value of the hook is saved in ‘sys.__breakpointhook__’.

   - bpo-17852(21): Maintain a list of open buffered files, flush them
     before exiting the interpreter.  Based on a patch from Armin Rigo.

   - bpo-31315(22): Fix an assertion failure in imp.create_dynamic(),
     when spec.name is not a string.  Patch by Oren Milman.

   - bpo-31311(23): Fix a crash in the ‘__setstate__()’ method of
     ‘ctypes._CData’, in case of a bad ‘__dict__’.  Patch by Oren
     Milman.

   - bpo-31293(24): Fix crashes in true division and multiplication of a
     timedelta object by a float with a bad as_integer_ratio() method.
     Patch by Oren Milman.

   - bpo-31285(25): Fix an assertion failure in
     ‘warnings.warn_explicit’, when the return value of the received
     loader's ‘get_source()’ has a bad ‘splitlines()’ method.  Patch by
     Oren Milman.

   - bpo-30406(26): Make ‘async’ and ‘await’ proper keywords, as
     specified in PEP 492(27).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31558

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31642

   (3) https://bugs.python.org/issue?@action=redirect&bpo=31708

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31709

   (5) https://bugs.python.org/issue?@action=redirect&bpo=30404

   (6) https://bugs.python.org/issue?@action=redirect&bpo=31619

   (7) https://bugs.python.org/issue?@action=redirect&bpo=31602

   (8) https://bugs.python.org/issue?@action=redirect&bpo=31592

   (9) https://bugs.python.org/issue?@action=redirect&bpo=31588

   (10) https://bugs.python.org/issue?@action=redirect&bpo=31574

   (11) https://bugs.python.org/issue?@action=redirect&bpo=31566

   (12) https://bugs.python.org/issue?@action=redirect&bpo=31506

   (13) https://bugs.python.org/issue?@action=redirect&bpo=31505

   (14) https://bugs.python.org/issue?@action=redirect&bpo=31492

   (15) https://bugs.python.org/issue?@action=redirect&bpo=31478

   (16) https://bugs.python.org/issue?@action=redirect&bpo=31336

   (17) https://bugs.python.org/issue?@action=redirect&bpo=31415

   (18) https://bugs.python.org/issue?@action=redirect&bpo=31410

   (19) https://bugs.python.org/issue?@action=redirect&bpo=31353

   (20) https://peps.python.org/pep-0553/

   (21) https://bugs.python.org/issue?@action=redirect&bpo=17852

   (22) https://bugs.python.org/issue?@action=redirect&bpo=31315

   (23) https://bugs.python.org/issue?@action=redirect&bpo=31311

   (24) https://bugs.python.org/issue?@action=redirect&bpo=31293

   (25) https://bugs.python.org/issue?@action=redirect&bpo=31285

   (26) https://bugs.python.org/issue?@action=redirect&bpo=30406

   (27) https://peps.python.org/pep-0492/


File: python.info,  Node: Library<58>,  Next: Documentation<52>,  Prev: Core and Builtins<58>,  Up: Python 3 7 0 alpha 2

1.23.59.2 Library
.................

   - bpo-30058(1): Fixed buffer overflow in select.kqueue.control().

   - bpo-31672(2): ‘idpattern’ in ‘string.Template’ matched some
     non-ASCII characters.  Now it uses ‘-i’ regular expression local
     flag to avoid non-ASCII characters.

   - bpo-31701(3): On Windows, faulthandler.enable() now ignores MSC and
     COM exceptions.

   - bpo-31728(4): Prevent crashes in ‘_elementtree’ due to unsafe
     cleanup of ‘Element.text’ and ‘Element.tail’.  Patch by Oren
     Milman.

   - bpo-31671(5): Now ‘re.compile()’ converts passed RegexFlag to
     normal int object before compiling.  bm_regex_compile benchmark
     shows 14% performance improvements.

   - bpo-30397(6): The types of compiled regular objects and match
     objects are now exposed as ‘re.Pattern’ and ‘re.Match’.  This adds
     information in pydoc output for the ‘re’ module.

   - bpo-31675(7): Fixed memory leaks in Tkinter's methods splitlist()
     and split() when pass a string larger than 2 GiB.

   - bpo-31673(8): Fixed typo in the name of Tkinter's method
     adderrorinfo().

   - bpo-31648(9): Improvements to path predicates in ElementTree: Allow
     whitespace around predicate parts, i.e.  "[a = 'text']" instead of
     requiring the less readable "[a='text']".  Add support for text
     comparison of the current node, like "[.='text']".  Patch by Stefan
     Behnel.

   - bpo-30806(10): Fix the string representation of a netrc object.

   - bpo-31638(11): Add optional argument ‘compressed’ to
     ‘zipapp.create_archive’, and add option ‘--compress’ to the command
     line interface of ‘zipapp’.

   - bpo-25351(12): Avoid venv activate failures with undefined
     variables

   - bpo-20519(13): Avoid ctypes use (if possible) and improve import
     time for uuid.

   - bpo-28293(14): The regular expression cache is no longer completely
     dumped when it is full.

   - bpo-31596(15): Added pthread_getcpuclockid() to the time module

   - bpo-27494(16): Make 2to3 accept a trailing comma in generator
     expressions.  For example, ‘set(x for x in [],)’ is now allowed.

   - bpo-30347(17): Stop crashes when concurrently iterate over
     itertools.groupby() iterators.

   - bpo-30346(18): An iterator produced by itertools.groupby() iterator
     now becomes exhausted after advancing the groupby iterator.

   - bpo-31556(19): Cancel asyncio.wait_for future faster if timeout <=
     0

   - bpo-31540(20): Allow passing a context object in *note
     concurrent.futures.ProcessPoolExecutor: 893. constructor.  Also,
     free job resources in *note concurrent.futures.ProcessPoolExecutor:
     893. earlier to improve memory usage when a worker waits for new
     jobs.

   - bpo-31516(21): ‘threading.current_thread()’ should not return a
     dummy thread at shutdown.

   - bpo-31525(22): In the sqlite module, require the sqlite3_prepare_v2
     API. Thus, the sqlite module now requires sqlite version at least
     3.3.9.

   - bpo-26510(23): argparse subparsers are now required by default.
     This matches behaviour in Python 2.  For optional subparsers, use
     the new parameter ‘add_subparsers(required=False)’.  Patch by
     Anthony Sottile.  (As of 3.7.0rc1, the default was changed to not
     required as had been the case since Python 3.3.)

   - bpo-27541(24): Reprs of subclasses of some collection and iterator
     classes (‘bytearray’, ‘array.array’, ‘collections.deque’,
     ‘collections.defaultdict’, ‘itertools.count’, ‘itertools.repeat’)
     now contain actual type name instead of hardcoded names of the base
     class.

   - bpo-31351(25): python -m ensurepip now exits with non-zero exit
     code if pip bootstrapping has failed.

   - bpo-31389(26): ‘pdb.set_trace()’ now takes an optional keyword-only
     argument ‘header’.  If given, this is printed to the console just
     before debugging begins.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30058

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31672

   (3) https://bugs.python.org/issue?@action=redirect&bpo=31701

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31728

   (5) https://bugs.python.org/issue?@action=redirect&bpo=31671

   (6) https://bugs.python.org/issue?@action=redirect&bpo=30397

   (7) https://bugs.python.org/issue?@action=redirect&bpo=31675

   (8) https://bugs.python.org/issue?@action=redirect&bpo=31673

   (9) https://bugs.python.org/issue?@action=redirect&bpo=31648

   (10) https://bugs.python.org/issue?@action=redirect&bpo=30806

   (11) https://bugs.python.org/issue?@action=redirect&bpo=31638

   (12) https://bugs.python.org/issue?@action=redirect&bpo=25351

   (13) https://bugs.python.org/issue?@action=redirect&bpo=20519

   (14) https://bugs.python.org/issue?@action=redirect&bpo=28293

   (15) https://bugs.python.org/issue?@action=redirect&bpo=31596

   (16) https://bugs.python.org/issue?@action=redirect&bpo=27494

   (17) https://bugs.python.org/issue?@action=redirect&bpo=30347

   (18) https://bugs.python.org/issue?@action=redirect&bpo=30346

   (19) https://bugs.python.org/issue?@action=redirect&bpo=31556

   (20) https://bugs.python.org/issue?@action=redirect&bpo=31540

   (21) https://bugs.python.org/issue?@action=redirect&bpo=31516

   (22) https://bugs.python.org/issue?@action=redirect&bpo=31525

   (23) https://bugs.python.org/issue?@action=redirect&bpo=26510

   (24) https://bugs.python.org/issue?@action=redirect&bpo=27541

   (25) https://bugs.python.org/issue?@action=redirect&bpo=31351

   (26) https://bugs.python.org/issue?@action=redirect&bpo=31389


File: python.info,  Node: Documentation<52>,  Next: Build<55>,  Prev: Library<58>,  Up: Python 3 7 0 alpha 2

1.23.59.3 Documentation
.......................

   - bpo-31537(1): Fix incorrect usage of ‘get_history_length’ in
     readline documentation example code.  Patch by Brad Smith.

   - bpo-30085(2): The operator functions without double underscores are
     preferred for clarity.  The one with underscores are only kept for
     back-compatibility.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31537

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30085


File: python.info,  Node: Build<55>,  Next: IDLE<42>,  Prev: Documentation<52>,  Up: Python 3 7 0 alpha 2

1.23.59.4 Build
...............

   - bpo-31696(1): Improve compiler version information in *note
     sys.version: 15c. when Python is built with Clang.

   - bpo-31625(2): Stop using ranlib on static libraries.  Instead, we
     assume ar supports the 's' flag.

   - bpo-31624(3): Remove support for BSD/OS.

   - bpo-22140(4): Prevent double substitution of prefix in
     python-config.sh.

   - bpo-31569(5): Correct PCBuild/ case to PCbuild/ in build scripts
     and documentation.

   - bpo-31536(6): Avoid wholesale rebuild after ‘make regen-all’ if
     nothing changed.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31696

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31625

   (3) https://bugs.python.org/issue?@action=redirect&bpo=31624

   (4) https://bugs.python.org/issue?@action=redirect&bpo=22140

   (5) https://bugs.python.org/issue?@action=redirect&bpo=31569

   (6) https://bugs.python.org/issue?@action=redirect&bpo=31536


File: python.info,  Node: IDLE<42>,  Next: C API<52>,  Prev: Build<55>,  Up: Python 3 7 0 alpha 2

1.23.59.5 IDLE
..............

   - bpo-31460(1): Simplify the API of IDLE's Module Browser.  Passing a
     widget instead of an flist with a root widget opens the option of
     creating a browser frame that is only part of a window.  Passing a
     full file name instead of pieces assumed to come from a .py file
     opens the possibility of browsing python files that do not end in
     .py.

   - bpo-31649(2): IDLE - Make _htest, _utest parameters keyword only.

   - bpo-31559(3): Remove test order dependence in
     idle_test.test_browser.

   - bpo-31459(4): Rename IDLE's module browser from Class Browser to
     Module Browser.  The original module-level class and method browser
     became a module browser, with the addition of module-level
     functions, years ago.  Nested classes and functions were added
     yesterday.  For back-compatibility, the virtual event
     <<open-class-browser>>, which appears on the Keys tab of the
     Settings dialog, is not changed.  Patch by Cheryl Sabella.

   - bpo-31500(5): Default fonts now are scaled on HiDPI displays.

   - bpo-1612262(6): IDLE module browser now shows nested classes and
     functions.  Original patches for code and tests by Guilherme Polo
     and Cheryl Sabella, respectively.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31460

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31649

   (3) https://bugs.python.org/issue?@action=redirect&bpo=31559

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31459

   (5) https://bugs.python.org/issue?@action=redirect&bpo=31500

   (6) https://bugs.python.org/issue?@action=redirect&bpo=1612262


File: python.info,  Node: C API<52>,  Prev: IDLE<42>,  Up: Python 3 7 0 alpha 2

1.23.59.6 C API
...............

   - bpo-28280(1): Make ‘PyMapping_Keys()’, ‘PyMapping_Values()’ and
     ‘PyMapping_Items()’ always return a ‘list’ (rather than a ‘list’ or
     a ‘tuple’).  Patch by Oren Milman.

   - bpo-31532(2): Fix memory corruption due to allocator mix in
     getpath.c between Py_GetPath() and Py_SetPath()

   - bpo-25658(3): Implement PEP 539(4) for Thread Specific Storage
     (TSS) API: it is a new Thread Local Storage (TLS) API to CPython
     which would supersede use of the existing TLS API within the
     CPython interpreter, while deprecating the existing API. PEP
     written by Erik M. Bray, patch by Masayuki Yamamoto.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28280

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31532

   (3) https://bugs.python.org/issue?@action=redirect&bpo=25658

   (4) https://peps.python.org/pep-0539/


File: python.info,  Node: Python 3 7 0 alpha 1,  Next: Python 3 6 6 final,  Prev: Python 3 7 0 alpha 2,  Up: Changelog（更動日誌）

1.23.60 Python 3.7.0 alpha 1
----------------------------

'Release date: 2017-09-19'

* Menu:

* Security: Security<36>.
* Core and Builtins: Core and Builtins<59>.
* Library: Library<59>.
* Documentation: Documentation<53>.
* Tests: Tests<53>.
* Build: Build<56>.
* Windows: Windows<51>.
* IDLE: IDLE<43>.
* Tools/Demos: Tools/Demos<29>.
* C API: C API<53>.


File: python.info,  Node: Security<36>,  Next: Core and Builtins<59>,  Up: Python 3 7 0 alpha 1

1.23.60.1 Security
..................

   - bpo-29781(1): SSLObject.version() now correctly returns None when
     handshake over BIO has not been performed yet.

   - bpo-29505(2): Add fuzz tests for float(str), int(str),
     unicode(str); for oss-fuzz.

   - bpo-30947(3): Upgrade libexpat embedded copy from version 2.2.1 to
     2.2.3 to get security fixes.

   - bpo-30730(4): Prevent environment variables injection in subprocess
     on Windows.  Prevent passing other environment variables and
     command arguments.

   - bpo-30694(5): Upgrade expat copy from 2.2.0 to 2.2.1 to get fixes
     of multiple security vulnerabilities including: CVE-2017-9233(6)
     (External entity infinite loop DoS), CVE-2016-9063(7) (Integer
     overflow, re-fix), CVE-2016-0718(8) (Fix regression bugs from
     2.2.0's fix to CVE-2016-0718(9)) and CVE-2012-0876(10) (Counter
     hash flooding with SipHash).  Note: the CVE-2016-5300(11) (Use
     os-specific entropy sources like getrandom) doesn't impact Python,
     since Python already gets entropy from the OS to set the expat
     secret using ‘XML_SetHashSalt()’.

   - bpo-30500(12): Fix urllib.parse.splithost() to correctly parse
     fragments.  For example, ‘splithost('//127.0.0.1#@evil.com/')’ now
     correctly returns the ‘127.0.0.1’ host, instead of treating
     ‘@evil.com’ as the host in an authentication (‘login@host’).

   - bpo-29591(13): Update expat copy from 2.1.1 to 2.2.0 to get fixes
     of CVE-2016-0718(14) and CVE-2016-4472(15).  See
     ‘https://sourceforge.net/p/expat/bugs/537/’ for more information.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29781

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29505

   (3) https://bugs.python.org/issue?@action=redirect&bpo=30947

   (4) https://bugs.python.org/issue?@action=redirect&bpo=30730

   (5) https://bugs.python.org/issue?@action=redirect&bpo=30694

   (6) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9233

   (7) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9063

   (8) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0718

   (9) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0718

   (10) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0876

   (11) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5300

   (12) https://bugs.python.org/issue?@action=redirect&bpo=30500

   (13) https://bugs.python.org/issue?@action=redirect&bpo=29591

   (14) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0718

   (15) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4472


File: python.info,  Node: Core and Builtins<59>,  Next: Library<59>,  Prev: Security<36>,  Up: Python 3 7 0 alpha 1

1.23.60.2 Core and Builtins
...........................

   - bpo-31490(1): Fix an assertion failure in ‘ctypes’ class
     definition, in case the class has an attribute whose name is
     specified in ‘_anonymous_’ but not in ‘_fields_’.  Patch by Oren
     Milman.

   - bpo-31471(2): Fix an assertion failure in ‘subprocess.Popen()’ on
     Windows, in case the env argument has a bad ‘keys()’ method.  Patch
     by Oren Milman.

   - bpo-31418(3): Fix an assertion failure in ‘PyErr_WriteUnraisable()’
     in case of an exception with a bad ‘__module__’ attribute.  Patch
     by Oren Milman.

   - bpo-31416(4): Fix assertion failures in case of a bad
     warnings.filters or warnings.defaultaction.  Patch by Oren Milman.

   - bpo-28411(5): Change direct usage of PyInterpreterState.modules to
     PyImport_GetModuleDict().  Also introduce more uniformity in other
     code that deals with sys.modules.  This helps reduce complications
     when working on sys.modules.

   - bpo-28411(6): Switch to the abstract API when dealing with
     ‘PyInterpreterState.modules’.  This allows later support for all
     dict subclasses and other Mapping implementations.  Also add a
     ‘PyImport_GetModule()’ function to reduce a bunch of duplicated
     code.

   - bpo-31411(7): Raise a TypeError instead of SystemError in case
     warnings.onceregistry is not a dictionary.  Patch by Oren Milman.

   - bpo-31344(8): For finer control of tracing behaviour when testing
     the interpreter, two new frame attributes have been added to
     control the emission of particular trace events: ‘f_trace_lines’
     (‘True’ by default) to turn off per-line trace events; and
     ‘f_trace_opcodes’ (‘False’ by default) to turn on per-opcode trace
     events.

   - bpo-31373(9): Fix several possible instances of undefined behavior
     due to floating-point demotions.

   - bpo-30465(10): Location information (‘lineno’ and ‘col_offset’) in
     f-strings is now (mostly) correct.  This fixes tools like flake8
     from showing warnings on the wrong line (typically the first line
     of the file).

   - bpo-30860(11): Consolidate CPython's global runtime state under a
     single struct.  This improves discoverability of the runtime state.

   - bpo-31347(12): Fix possible undefined behavior in
     _PyObject_FastCall_Prepend.

   - bpo-31343(13): Include sys/sysmacros.h for major(), minor(), and
     makedev().  GNU C libray plans to remove the functions from
     sys/types.h.

   - bpo-31291(14): Fix an assertion failure in
     ‘zipimport.zipimporter.get_data’ on Windows, when the return value
     of ‘pathname.replace('/','\\')’ isn't a string.  Patch by Oren
     Milman.

   - bpo-31271(15): Fix an assertion failure in the ‘write()’ method of
     ‘io.TextIOWrapper’, when the encoder doesn't return a bytes object.
     Patch by Oren Milman.

   - bpo-31243(16): Fix a crash in some methods of ‘io.TextIOWrapper’,
     when the decoder's state is invalid.  Patch by Oren Milman.

   - bpo-30721(17): ‘print’ now shows correct usage hint for using
     Python 2 redirection syntax.  Patch by Sanyam Khurana.

   - bpo-31070(18): Fix a race condition in importlib
     _get_module_lock().

   - bpo-30747(19): Add a non-dummy implementation of _Py_atomic_store
     and _Py_atomic_load on MSVC.

   - bpo-31095(20): Fix potential crash during GC caused by ‘tp_dealloc’
     which doesn't call ‘PyObject_GC_UnTrack()’.

   - bpo-31071(21): Avoid masking original TypeError in call with *
     unpacking when other arguments are passed.

   - bpo-30978(22): str.format_map() now passes key lookup exceptions
     through.  Previously any exception was replaced with a KeyError
     exception.

   - bpo-30808(23): Use _Py_atomic API for concurrency-sensitive signal
     state.

   - bpo-30876(24): Relative import from unloaded package now reimports
     the package instead of failing with SystemError.  Relative import
     from non-package now fails with ImportError rather than
     SystemError.

   - bpo-30703(25): Improve signal delivery.  Avoid using
     Py_AddPendingCall from signal handler, to avoid calling
     signal-unsafe functions.  The tests I'm adding here fail without
     the rest of the patch, on Linux and OS X. This means our signal
     delivery logic had defects (some signals could be lost).

   - bpo-30765(26): Avoid blocking in pthread_mutex_lock() when
     PyThread_acquire_lock() is asked not to block.

   - bpo-31161(27): Make sure the 'Missing parentheses' syntax error
     message is only applied to SyntaxError, not to subclasses.  Patch
     by Martijn Pieters.

   - bpo-30814(28): Fixed a race condition when import a submodule from
     a package.

   - bpo-30736(29): The internal unicodedata database has been upgraded
     to Unicode 10.0.

   - bpo-30604(30): Move co_extra_freefuncs from per-thread to
     per-interpreter to avoid crashes.

   - bpo-30597(31): ‘print’ now shows expected input in custom error
     message when used as a Python 2 statement.  Patch by Sanyam
     Khurana.

   - bpo-30682(32): Removed a too-strict assertion that failed for
     certain f-strings, such as eval("f'\n'") and eval("f'\r'").

   - bpo-30501(33): The compiler now produces more optimal code for
     complex condition expressions in the "if", "while" and "assert"
     statement, the "if" expression, and generator expressions and
     comprehensions.

   - bpo-28180(34): Implement PEP 538(35) (legacy C locale coercion).
     This means that when a suitable coercion target locale is
     available, both the core interpreter and locale-aware C extensions
     will assume the use of UTF-8 as the default text encoding, rather
     than ASCII.

   - bpo-30486(36): Allows setting cell values for __closure__.  Patch
     by Lisa Roach.

   - bpo-30537(37): itertools.islice now accepts integer-like objects
     (having an __index__ method) as start, stop, and slice arguments

   - bpo-25324(38): Tokens needed for parsing in Python moved to C.
     ‘COMMENT’, ‘NL’ and ‘ENCODING’.  This way the tokens and tok_names
     in the token module don't get changed when you import the tokenize
     module.

   - bpo-29104(39): Fixed parsing backslashes in f-strings.

   - bpo-27945(40): Fixed various segfaults with dict when input
     collections are mutated during searching, inserting or comparing.
     Based on patches by Duane Griffin and Tim Mitchell.

   - bpo-25794(41): Fixed type.__setattr__() and type.__delattr__() for
     non-interned attribute names.  Based on patch by Eryk Sun.

   - bpo-30039(42): If a KeyboardInterrupt happens when the interpreter
     is in the middle of resuming a chain of nested 'yield from' or
     'await' calls, it's now correctly delivered to the innermost frame.

   - bpo-28974(43): ‘object.__format__(x, '')’ is now equivalent to
     ‘str(x)’ rather than ‘format(str(self), '')’.

   - bpo-30024(44): Circular imports involving absolute imports with
     binding a submodule to a name are now supported.

   - bpo-12414(45): sys.getsizeof() on a code object now returns the
     sizes which includes the code struct and sizes of objects which it
     references.  Patch by Donghee Na.

   - bpo-29839(46): len() now raises ValueError rather than
     OverflowError if __len__() returned a large negative integer.

   - bpo-11913(47): README.rst is now included in the list of distutils
     standard READMEs and therefore included in source distributions.

   - bpo-29914(48): Fixed default implementations of __reduce__ and
     __reduce_ex__().  object.__reduce__() no longer takes arguments,
     object.__reduce_ex__() now requires one argument.

   - bpo-29949(49): Fix memory usage regression of set and frozenset
     object.

   - bpo-29935(50): Fixed error messages in the index() method of tuple,
     list and deque when pass indices of wrong type.

   - bpo-29816(51): Shift operation now has less opportunity to raise
     OverflowError.  ValueError always is raised rather than
     OverflowError for negative counts.  Shifting zero with non-negative
     count always returns zero.

   - bpo-24821(52): Fixed the slowing down to 25 times in the searching
     of some unlucky Unicode characters.

   - bpo-29102(53): Add a unique ID to PyInterpreterState.  This makes
     it easier to identify each subinterpreter.

   - bpo-29894(54): The deprecation warning is emitted if __complex__
     returns an instance of a strict subclass of complex.  In a future
     versions of Python this can be an error.

   - bpo-29859(55): Show correct error messages when any of the
     pthread_* calls in thread_pthread.h fails.

   - bpo-29849(56): Fix a memory leak when an ImportError is raised
     during from import.

   - bpo-28856(57): Fix an oversight that %b format for bytes should
     support objects follow the buffer protocol.

   - bpo-29723(58): The ‘sys.path[0]’ initialization change for
     bpo-29139(59) caused a regression by revealing an inconsistency in
     how sys.path is initialized when executing ‘__main__’ from a
     zipfile, directory, or other import location.  The interpreter now
     consistently avoids ever adding the import location's parent
     directory to ‘sys.path’, and ensures no other ‘sys.path’ entries
     are inadvertently modified when inserting the import location named
     on the command line.

   - bpo-29568(60): Escaped percent "%%" in the format string for
     classic string formatting no longer allows any characters between
     two percents.

   - bpo-29714(61): Fix a regression that bytes format may fail when
     containing zero bytes inside.

   - bpo-29695(62): bool(), float(), list() and tuple() no longer take
     keyword arguments.  The first argument of int() can now be passes
     only as positional argument.

   - bpo-28893(63): Set correct __cause__ for errors about invalid
     awaitables returned from __aiter__ and __anext__.

   - bpo-28876(64): ‘bool(range)’ works even if ‘len(range)’ raises
     *note OverflowError: 825.

   - bpo-29683(65): Fixes to memory allocation in _PyCode_SetExtra.
     Patch by Brian Coleman.

   - bpo-29684(66): Fix minor regression of
     PyEval_CallObjectWithKeywords.  It should raise TypeError when
     kwargs is not a dict.  But it might cause segv when args=NULL and
     kwargs is not a dict.

   - bpo-28598(67): Support __rmod__ for subclasses of str being called
     before str.__mod__.  Patch by Martijn Pieters.

   - bpo-29607(68): Fix stack_effect computation for CALL_FUNCTION_EX.
     Patch by Matthieu Dartiailh.

   - bpo-29602(69): Fix incorrect handling of signed zeros in complex
     constructor for complex subclasses and for inputs having a
     __complex__ method.  Patch by Serhiy Storchaka.

   - bpo-29347(70): Fixed possibly dereferencing undefined pointers when
     creating weakref objects.

   - bpo-29463(71): Add ‘docstring’ field to Module, ClassDef,
     FunctionDef, and AsyncFunctionDef ast nodes.  docstring is not
     first stmt in their body anymore.  It affects ‘co_firstlineno’ and
     ‘co_lnotab’ of code object for module and class.  (Reverted in
     bpo-32911(72).)

   - bpo-29438(73): Fixed use-after-free problem in key sharing dict.

   - bpo-29546(74): Set the 'path' and 'name' attribute on ImportError
     for ‘from ... import ...’.

   - bpo-29546(75): Improve from-import error message with location

   - bpo-29478(76): If max_line_length=None is specified while using the
     Compat32 policy, it is no longer ignored.  Patch by Mircea Cosbuc.

   - bpo-29319(77): Prevent RunMainFromImporter overwriting sys.path[0].

   - bpo-29337(78): Fixed possible BytesWarning when compare the code
     objects.  Warnings could be emitted at compile time.

   - bpo-29327(79): Fixed a crash when pass the iterable keyword
     argument to sorted().

   - bpo-29034(80): Fix memory leak and use-after-free in os module
     (path_converter).

   - bpo-29159(81): Fix regression in bytes(x) when x.__index__() raises
     Exception.

   - bpo-29049(82): Call _PyObject_GC_TRACK() lazily when calling Python
     function.  Calling function is up to 5% faster.

   - bpo-28927(83): bytes.fromhex() and bytearray.fromhex() now ignore
     all ASCII whitespace, not only spaces.  Patch by Robert Xiao.

   - bpo-28932(84): Do not include <sys/random.h> if it does not exist.

   - bpo-25677(85): Correct the positioning of the syntax error caret
     for indented blocks.  Based on patch by Michael Layzell.

   - bpo-29000(86): Fixed bytes formatting of octals with zero padding
     in alternate form.

   - bpo-18896(87): Python function can now have more than 255
     parameters.  collections.namedtuple() now supports tuples with more
     than 255 elements.

   - bpo-28596(88): The preferred encoding is UTF-8 on Android.  Patch
     written by Chi Hsuan Yen.

   - bpo-22257(89): Clean up interpreter startup (see PEP 432(90)).

   - bpo-26919(91): On Android, operating system data is now always
     encoded/decoded to/from UTF-8, instead of the locale encoding to
     avoid inconsistencies with os.fsencode() and os.fsdecode() which
     are already using UTF-8.

   - bpo-28991(92): functools.lru_cache() was susceptible to an obscure
     reentrancy bug triggerable by a monkey-patched len() function.

   - bpo-28147(93): Fix a memory leak in split-table dictionaries:
     setattr() must not convert combined table into split table.  Patch
     written by INADA Naoki.

   - bpo-28739(94): f-string expressions are no longer accepted as
     docstrings and by ast.literal_eval() even if they do not include
     expressions.

   - bpo-28512(95): Fixed setting the offset attribute of SyntaxError by
     PyErr_SyntaxLocationEx() and PyErr_SyntaxLocationObject().

   - bpo-28918(96): Fix the cross compilation of xxlimited when Python
     has been built with Py_DEBUG defined.

   - bpo-23722(97): Rather than silently producing a class that doesn't
     support zero-argument ‘super()’ in methods, failing to pass the new
     ‘__classcell__’ namespace entry up to ‘type.__new__’ now results in
     a ‘DeprecationWarning’ and a class that supports zero-argument
     ‘super()’.

   - bpo-28797(98): Modifying the class __dict__ inside the __set_name__
     method of a descriptor that is used inside that class no longer
     prevents calling the __set_name__ method of other descriptors.

   - bpo-28799(99): Remove the ‘PyEval_GetCallStats()’ function and
     deprecate the untested and undocumented ‘sys.callstats()’ function.
     Remove the ‘CALL_PROFILE’ special build: use the *note
     sys.setprofile(): 146d. function, *note cProfile: 20. or *note
     profile: 9d. to profile function calls.

   - bpo-12844(100): More than 255 arguments can now be passed to a
     function.

   - bpo-28782(101): Fix a bug in the implementation ‘yield from’ when
     checking if the next instruction is YIELD_FROM. Regression
     introduced by WORDCODE (bpo-26647(102)).

   - bpo-28774(103): Fix error position of the unicode error in ASCII
     and Latin1 encoders when a string returned by the error handler
     contains multiple non-encodable characters (non-ASCII for the ASCII
     codec, characters out of the U+0000-U+00FF range for Latin1).

   - bpo-28731(104): Optimize _PyDict_NewPresized() to create correct
     size dict.  Improve speed of dict literal with constant keys up to
     30%.

   - bpo-28532(105): Show sys.version when -V option is supplied twice.

   - bpo-27100(106): The with-statement now checks for __enter__ before
     it checks for __exit__.  This gives less confusing error messages
     when both methods are missing.  Patch by Jonathan Ellington.

   - bpo-28746(107): Fix the set_inheritable() file descriptor method on
     platforms that do not have the ioctl FIOCLEX and FIONCLEX commands.

   - bpo-26920(108): Fix not getting the locale's charset upon
     initializing the interpreter, on platforms that do not have
     langinfo.

   - bpo-28648(109): Fixed crash in Py_DecodeLocale() in debug build on
     Mac OS X when decode astral characters.  Patch by Xiang Zhang.

   - bpo-28665(110): Improve speed of the STORE_DEREF opcode by 40%.

   - bpo-19398(111): Extra slash no longer added to sys.path components
     in case of empty compile-time PYTHONPATH components.

   - bpo-28621(112): Sped up converting int to float by reusing faster
     bits counting implementation.  Patch by Adrian Wielgosik.

   - bpo-28580(113): Optimize iterating split table values.  Patch by
     Xiang Zhang.

   - bpo-28583(114): PyDict_SetDefault didn't combine split table when
     needed.  Patch by Xiang Zhang.

   - bpo-28128(115): Deprecation warning for invalid str and byte escape
     sequences now prints better information about where the error
     occurs.  Patch by Serhiy Storchaka and Eric Smith.

   - bpo-28509(116): dict.update() no longer allocate unnecessary large
     memory.

   - bpo-28426(117): Fixed potential crash in
     PyUnicode_AsDecodedObject() in debug build.

   - bpo-28517(118): Fixed of-by-one error in the peephole optimizer
     that caused keeping unreachable code.

   - bpo-28214(119): Improved exception reporting for problematic
     __set_name__ attributes.

   - bpo-23782(120): Fixed possible memory leak in _PyTraceback_Add()
     and exception loss in PyTraceBack_Here().

   - bpo-28183(121): Optimize and cleanup dict iteration.

   - bpo-26081(122): Added C implementation of asyncio.Future.  Original
     patch by Yury Selivanov.

   - bpo-28379(123): Added sanity checks and tests for
     PyUnicode_CopyCharacters().  Patch by Xiang Zhang.

   - bpo-28376(124): The type of long range iterator is now registered
     as Iterator.  Patch by Oren Milman.

   - bpo-28376(125): Creating instances of range_iterator by calling
     range_iterator type now is disallowed.  Calling iter() on range
     instance is the only way.  Patch by Oren Milman.

   - bpo-26906(126): Resolving special methods of uninitialized type now
     causes implicit initialization of the type instead of a fail.

   - bpo-18287(127): PyType_Ready() now checks that tp_name is not NULL.
     Original patch by Niklas Koep.

   - bpo-24098(128): Fixed possible crash when AST is changed in process
     of compiling it.

   - bpo-28201(129): Dict reduces possibility of 2nd conflict in hash
     table when hashes have same lower bits.

   - bpo-28350(130): String constants with null character no longer
     interned.

   - bpo-26617(131): Fix crash when GC runs during weakref callbacks.

   - bpo-27942(132): String constants now interned recursively in tuples
     and frozensets.

   - bpo-28289(133): ImportError.__init__ now resets not specified
     attributes.

   - bpo-21578(134): Fixed misleading error message when ImportError
     called with invalid keyword args.

   - bpo-28203(135): Fix incorrect type in complex(1.0, {2:3}) error
     message.  Patch by Soumya Sharma.

   - bpo-28086(136): Single var-positional argument of tuple subtype was
     passed unscathed to the C-defined function.  Now it is converted to
     exact tuple.

   - bpo-28214(137): Now __set_name__ is looked up on the class instead
     of the instance.

   - bpo-27955(138): Fallback on reading /dev/urandom device when the
     getrandom() syscall fails with EPERM, for example when blocked by
     SECCOMP.

   - bpo-28192(139): Don't import readline in isolated mode.

   - bpo-27441(140): Remove some redundant assignments to ob_size in
     longobject.c.  Thanks Oren Milman.

   - bpo-27222(141): Clean up redundant code in long_rshift function.
     Thanks Oren Milman.

   - Upgrade internal unicode databases to Unicode version 9.0.0.

   - bpo-28131(142): Fix a regression in zipimport's compile_source().
     zipimport should use the same optimization level as the
     interpreter.

   - bpo-28126(143): Replace Py_MEMCPY with memcpy().  Visual Studio can
     properly optimize memcpy().

   - bpo-28120(144): Fix dict.pop() for splitted dictionary when trying
     to remove a "pending key" (Not yet inserted in split-table).  Patch
     by Xiang Zhang.

   - bpo-26182(145): Raise DeprecationWarning when async and await
     keywords are used as variable/attribute/class/function name.

   - bpo-26182(146): Fix a refleak in code that raises
     DeprecationWarning.

   - bpo-28721(147): Fix asynchronous generators aclose() and athrow()
     to handle StopAsyncIteration propagation properly.

   - bpo-26110(148): Speed-up method calls: add LOAD_METHOD and
     CALL_METHOD opcodes.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31490

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31471

   (3) https://bugs.python.org/issue?@action=redirect&bpo=31418

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31416

   (5) https://bugs.python.org/issue?@action=redirect&bpo=28411

   (6) https://bugs.python.org/issue?@action=redirect&bpo=28411

   (7) https://bugs.python.org/issue?@action=redirect&bpo=31411

   (8) https://bugs.python.org/issue?@action=redirect&bpo=31344

   (9) https://bugs.python.org/issue?@action=redirect&bpo=31373

   (10) https://bugs.python.org/issue?@action=redirect&bpo=30465

   (11) https://bugs.python.org/issue?@action=redirect&bpo=30860

   (12) https://bugs.python.org/issue?@action=redirect&bpo=31347

   (13) https://bugs.python.org/issue?@action=redirect&bpo=31343

   (14) https://bugs.python.org/issue?@action=redirect&bpo=31291

   (15) https://bugs.python.org/issue?@action=redirect&bpo=31271

   (16) https://bugs.python.org/issue?@action=redirect&bpo=31243

   (17) https://bugs.python.org/issue?@action=redirect&bpo=30721

   (18) https://bugs.python.org/issue?@action=redirect&bpo=31070

   (19) https://bugs.python.org/issue?@action=redirect&bpo=30747

   (20) https://bugs.python.org/issue?@action=redirect&bpo=31095

   (21) https://bugs.python.org/issue?@action=redirect&bpo=31071

   (22) https://bugs.python.org/issue?@action=redirect&bpo=30978

   (23) https://bugs.python.org/issue?@action=redirect&bpo=30808

   (24) https://bugs.python.org/issue?@action=redirect&bpo=30876

   (25) https://bugs.python.org/issue?@action=redirect&bpo=30703

   (26) https://bugs.python.org/issue?@action=redirect&bpo=30765

   (27) https://bugs.python.org/issue?@action=redirect&bpo=31161

   (28) https://bugs.python.org/issue?@action=redirect&bpo=30814

   (29) https://bugs.python.org/issue?@action=redirect&bpo=30736

   (30) https://bugs.python.org/issue?@action=redirect&bpo=30604

   (31) https://bugs.python.org/issue?@action=redirect&bpo=30597

   (32) https://bugs.python.org/issue?@action=redirect&bpo=30682

   (33) https://bugs.python.org/issue?@action=redirect&bpo=30501

   (34) https://bugs.python.org/issue?@action=redirect&bpo=28180

   (35) https://peps.python.org/pep-0538/

   (36) https://bugs.python.org/issue?@action=redirect&bpo=30486

   (37) https://bugs.python.org/issue?@action=redirect&bpo=30537

   (38) https://bugs.python.org/issue?@action=redirect&bpo=25324

   (39) https://bugs.python.org/issue?@action=redirect&bpo=29104

   (40) https://bugs.python.org/issue?@action=redirect&bpo=27945

   (41) https://bugs.python.org/issue?@action=redirect&bpo=25794

   (42) https://bugs.python.org/issue?@action=redirect&bpo=30039

   (43) https://bugs.python.org/issue?@action=redirect&bpo=28974

   (44) https://bugs.python.org/issue?@action=redirect&bpo=30024

   (45) https://bugs.python.org/issue?@action=redirect&bpo=12414

   (46) https://bugs.python.org/issue?@action=redirect&bpo=29839

   (47) https://bugs.python.org/issue?@action=redirect&bpo=11913

   (48) https://bugs.python.org/issue?@action=redirect&bpo=29914

   (49) https://bugs.python.org/issue?@action=redirect&bpo=29949

   (50) https://bugs.python.org/issue?@action=redirect&bpo=29935

   (51) https://bugs.python.org/issue?@action=redirect&bpo=29816

   (52) https://bugs.python.org/issue?@action=redirect&bpo=24821

   (53) https://bugs.python.org/issue?@action=redirect&bpo=29102

   (54) https://bugs.python.org/issue?@action=redirect&bpo=29894

   (55) https://bugs.python.org/issue?@action=redirect&bpo=29859

   (56) https://bugs.python.org/issue?@action=redirect&bpo=29849

   (57) https://bugs.python.org/issue?@action=redirect&bpo=28856

   (58) https://bugs.python.org/issue?@action=redirect&bpo=29723

   (59) https://bugs.python.org/issue?@action=redirect&bpo=29139

   (60) https://bugs.python.org/issue?@action=redirect&bpo=29568

   (61) https://bugs.python.org/issue?@action=redirect&bpo=29714

   (62) https://bugs.python.org/issue?@action=redirect&bpo=29695

   (63) https://bugs.python.org/issue?@action=redirect&bpo=28893

   (64) https://bugs.python.org/issue?@action=redirect&bpo=28876

   (65) https://bugs.python.org/issue?@action=redirect&bpo=29683

   (66) https://bugs.python.org/issue?@action=redirect&bpo=29684

   (67) https://bugs.python.org/issue?@action=redirect&bpo=28598

   (68) https://bugs.python.org/issue?@action=redirect&bpo=29607

   (69) https://bugs.python.org/issue?@action=redirect&bpo=29602

   (70) https://bugs.python.org/issue?@action=redirect&bpo=29347

   (71) https://bugs.python.org/issue?@action=redirect&bpo=29463

   (72) https://bugs.python.org/issue?@action=redirect&bpo=32911

   (73) https://bugs.python.org/issue?@action=redirect&bpo=29438

   (74) https://bugs.python.org/issue?@action=redirect&bpo=29546

   (75) https://bugs.python.org/issue?@action=redirect&bpo=29546

   (76) https://bugs.python.org/issue?@action=redirect&bpo=29478

   (77) https://bugs.python.org/issue?@action=redirect&bpo=29319

   (78) https://bugs.python.org/issue?@action=redirect&bpo=29337

   (79) https://bugs.python.org/issue?@action=redirect&bpo=29327

   (80) https://bugs.python.org/issue?@action=redirect&bpo=29034

   (81) https://bugs.python.org/issue?@action=redirect&bpo=29159

   (82) https://bugs.python.org/issue?@action=redirect&bpo=29049

   (83) https://bugs.python.org/issue?@action=redirect&bpo=28927

   (84) https://bugs.python.org/issue?@action=redirect&bpo=28932

   (85) https://bugs.python.org/issue?@action=redirect&bpo=25677

   (86) https://bugs.python.org/issue?@action=redirect&bpo=29000

   (87) https://bugs.python.org/issue?@action=redirect&bpo=18896

   (88) https://bugs.python.org/issue?@action=redirect&bpo=28596

   (89) https://bugs.python.org/issue?@action=redirect&bpo=22257

   (90) https://peps.python.org/pep-0432/

   (91) https://bugs.python.org/issue?@action=redirect&bpo=26919

   (92) https://bugs.python.org/issue?@action=redirect&bpo=28991

   (93) https://bugs.python.org/issue?@action=redirect&bpo=28147

   (94) https://bugs.python.org/issue?@action=redirect&bpo=28739

   (95) https://bugs.python.org/issue?@action=redirect&bpo=28512

   (96) https://bugs.python.org/issue?@action=redirect&bpo=28918

   (97) https://bugs.python.org/issue?@action=redirect&bpo=23722

   (98) https://bugs.python.org/issue?@action=redirect&bpo=28797

   (99) https://bugs.python.org/issue?@action=redirect&bpo=28799

   (100) https://bugs.python.org/issue?@action=redirect&bpo=12844

   (101) https://bugs.python.org/issue?@action=redirect&bpo=28782

   (102) https://bugs.python.org/issue?@action=redirect&bpo=26647

   (103) https://bugs.python.org/issue?@action=redirect&bpo=28774

   (104) https://bugs.python.org/issue?@action=redirect&bpo=28731

   (105) https://bugs.python.org/issue?@action=redirect&bpo=28532

   (106) https://bugs.python.org/issue?@action=redirect&bpo=27100

   (107) https://bugs.python.org/issue?@action=redirect&bpo=28746

   (108) https://bugs.python.org/issue?@action=redirect&bpo=26920

   (109) https://bugs.python.org/issue?@action=redirect&bpo=28648

   (110) https://bugs.python.org/issue?@action=redirect&bpo=28665

   (111) https://bugs.python.org/issue?@action=redirect&bpo=19398

   (112) https://bugs.python.org/issue?@action=redirect&bpo=28621

   (113) https://bugs.python.org/issue?@action=redirect&bpo=28580

   (114) https://bugs.python.org/issue?@action=redirect&bpo=28583

   (115) https://bugs.python.org/issue?@action=redirect&bpo=28128

   (116) https://bugs.python.org/issue?@action=redirect&bpo=28509

   (117) https://bugs.python.org/issue?@action=redirect&bpo=28426

   (118) https://bugs.python.org/issue?@action=redirect&bpo=28517

   (119) https://bugs.python.org/issue?@action=redirect&bpo=28214

   (120) https://bugs.python.org/issue?@action=redirect&bpo=23782

   (121) https://bugs.python.org/issue?@action=redirect&bpo=28183

   (122) https://bugs.python.org/issue?@action=redirect&bpo=26081

   (123) https://bugs.python.org/issue?@action=redirect&bpo=28379

   (124) https://bugs.python.org/issue?@action=redirect&bpo=28376

   (125) https://bugs.python.org/issue?@action=redirect&bpo=28376

   (126) https://bugs.python.org/issue?@action=redirect&bpo=26906

   (127) https://bugs.python.org/issue?@action=redirect&bpo=18287

   (128) https://bugs.python.org/issue?@action=redirect&bpo=24098

   (129) https://bugs.python.org/issue?@action=redirect&bpo=28201

   (130) https://bugs.python.org/issue?@action=redirect&bpo=28350

   (131) https://bugs.python.org/issue?@action=redirect&bpo=26617

   (132) https://bugs.python.org/issue?@action=redirect&bpo=27942

   (133) https://bugs.python.org/issue?@action=redirect&bpo=28289

   (134) https://bugs.python.org/issue?@action=redirect&bpo=21578

   (135) https://bugs.python.org/issue?@action=redirect&bpo=28203

   (136) https://bugs.python.org/issue?@action=redirect&bpo=28086

   (137) https://bugs.python.org/issue?@action=redirect&bpo=28214

   (138) https://bugs.python.org/issue?@action=redirect&bpo=27955

   (139) https://bugs.python.org/issue?@action=redirect&bpo=28192

   (140) https://bugs.python.org/issue?@action=redirect&bpo=27441

   (141) https://bugs.python.org/issue?@action=redirect&bpo=27222

   (142) https://bugs.python.org/issue?@action=redirect&bpo=28131

   (143) https://bugs.python.org/issue?@action=redirect&bpo=28126

   (144) https://bugs.python.org/issue?@action=redirect&bpo=28120

   (145) https://bugs.python.org/issue?@action=redirect&bpo=26182

   (146) https://bugs.python.org/issue?@action=redirect&bpo=26182

   (147) https://bugs.python.org/issue?@action=redirect&bpo=28721

   (148) https://bugs.python.org/issue?@action=redirect&bpo=26110


File: python.info,  Node: Library<59>,  Next: Documentation<53>,  Prev: Core and Builtins<59>,  Up: Python 3 7 0 alpha 1

1.23.60.3 Library
.................

   - bpo-31499(1): xml.etree: Fix a crash when a parser is part of a
     reference cycle.

   - bpo-31482(2): ‘random.seed()’ now works with bytes in version=1

   - bpo-28556(3): typing.get_type_hints now finds the right globalns
     for classes and modules by default (when no ‘globalns’ was
     specified by the caller).

   - bpo-28556(4): Speed improvements to the ‘typing’ module.  Original
     PRs by Ivan Levkivskyi and Mitar.

   - bpo-31544(5): The C accelerator module of ElementTree ignored
     exceptions raised when looking up TreeBuilder target methods in
     XMLParser().

   - bpo-31234(6): socket.create_connection() now fixes manually a
     reference cycle: clear the variable storing the last exception on
     success.

   - bpo-31457(7): LoggerAdapter objects can now be nested.

   - bpo-31431(8): SSLContext.check_hostname now automatically sets
     SSLContext.verify_mode to ssl.CERT_REQUIRED instead of failing with
     a ValueError.

   - bpo-31233(9): socketserver.ThreadingMixIn now keeps a list of
     non-daemonic threads to wait until all these threads complete in
     server_close().

   - bpo-28638(10): Changed the implementation strategy for
     collections.namedtuple() to substantially reduce the use of exec()
     in favor of precomputed methods.  As a result, the 'verbose'
     parameter and '_source' attribute are no longer supported.  The
     benefits include 1) having a smaller memory footprint for
     applications using multiple named tuples, 2) faster creation of the
     named tuple class (approx 4x to 6x depending on how it is
     measured), and 3) minor speed-ups for instance creation using
     __new__, _make, and _replace.  (The primary patch contributor is
     Jelle Zijlstra with further improvements by INADA Naoki, Serhiy
     Storchaka, and Raymond Hettinger.)

   - bpo-31400(11): Improves SSL error handling to avoid losing error
     numbers.

   - bpo-27629(12): Make return types of SSLContext.wrap_bio() and
     SSLContext.wrap_socket() customizable.

   - bpo-28958(13): ssl.SSLContext() now uses OpenSSL error information
     when a context cannot be instantiated.

   - bpo-28182(14): The SSL module now raises SSLCertVerificationError
     when OpenSSL fails to verify the peer's certificate.  The exception
     contains more information about the error.

   - bpo-27340(15): SSLSocket.sendall() now uses memoryview to create
     slices of data.  This fixes support for all bytes-like object.  It
     is also more efficient and avoids costly copies.

   - bpo-14191(16): A new function
     ‘argparse.ArgumentParser.parse_intermixed_args’ provides the
     ability to parse command lines where there user intermixes options
     and positional arguments.

   - bpo-31178(17): Fix string concatenation bug in rare error path in
     the subprocess module

   - bpo-31350(18): Micro-optimize ‘asyncio._get_running_loop()’ to
     become up to 10% faster.

   - bpo-31170(19): expat: Update libexpat from 2.2.3 to 2.2.4.  Fix
     copying of partial characters for UTF-8 input (libexpat bug 115):
     ‘https://github.com/libexpat/libexpat/issues/115’

   - bpo-29136(20): Add TLS 1.3 cipher suites and OP_NO_TLSv1_3.

   - bpo-1198569(21): ‘string.Template’ subclasses can optionally define
     ‘braceidpattern’ if they want to specify different placeholder
     patterns inside and outside the braces.  If None (the default) it
     falls back to ‘idpattern’.

   - bpo-31326(22): concurrent.futures.ProcessPoolExecutor.shutdown()
     now explicitly closes the call queue.  Moreover,
     shutdown(wait=True) now also join the call queue thread, to prevent
     leaking a dangling thread.

   - bpo-27144(23): The ‘map()’ and ‘as_completed()’ iterators in
     ‘concurrent.futures’ now avoid keeping a reference to yielded
     objects.

   - bpo-31281(24): Fix ‘fileinput.FileInput(files, inplace=True)’ when
     ‘files’ contain ‘pathlib.Path’ objects.

   - bpo-10746(25): Fix ctypes producing wrong PEP 3118(26) type codes
     for integer types.

   - bpo-27584(27): ‘AF_VSOCK’ has been added to the socket interface
     which allows communication between virtual machines and their host.

   - bpo-22536(28): The subprocess module now sets the filename when
     FileNotFoundError is raised on POSIX systems due to the executable
     or cwd not being found.

   - bpo-29741(29): Update some methods in the _pyio module to also
     accept integer types.  Patch by Oren Milman.

   - bpo-31249(30): concurrent.futures: WorkItem.run() used by
     ThreadPoolExecutor now breaks a reference cycle between an
     exception object and the WorkItem object.

   - bpo-31247(31): xmlrpc.server now explicitly breaks reference cycles
     when using sys.exc_info() in code handling exceptions.

   - bpo-23835(32): configparser: reading defaults in the
     ‘ConfigParser()’ constructor is now using ‘read_dict()’, making its
     behavior consistent with the rest of the parser.  Non-string keys
     and values in the defaults dictionary are now being implicitly
     converted to strings.  Patch by James Tocknell.

   - bpo-31238(33): pydoc: the stop() method of the private ServerThread
     class now waits until DocServer.serve_until_quit() completes and
     then explicitly sets its docserver attribute to None to break a
     reference cycle.

   - bpo-5001(34): Many asserts in ‘multiprocessing’ are now more
     informative, and some error types have been changed to more
     specific ones.

   - bpo-31109(35): Convert zipimport to use Argument Clinic.

   - bpo-30102(36): The ssl and hashlib modules now call
     OPENSSL_add_all_algorithms_noconf() on OpenSSL < 1.1.0.  The
     function detects CPU features and enables optimizations on some CPU
     architectures such as POWER8.  Patch is based on research from
     Gustavo Serra Scalet.

   - bpo-18966(37): Non-daemonic threads created by a
     multiprocessing.Process are now joined on child exit.

   - bpo-31183(38): ‘dis’ now works with asynchronous generator and
     coroutine objects.  Patch by George Collins based on diagnosis by
     Luciano Ramalho.

   - bpo-5001(39): There are a number of uninformative asserts in the
     ‘multiprocessing’ module, as noted in issue 5001.  This change
     fixes two of the most potentially problematic ones, since they are
     in error-reporting code, in the
     ‘multiprocessing.managers.convert_to_error’ function.  (It also
     makes more informative a ValueError message.)  The only potentially
     problematic change is that the AssertionError is now a TypeError;
     however, this should also help distinguish it from an
     AssertionError being 'reported' by the function/its caller (such as
     in issue 31169).  - Patch by Allen W. Smith (drallensmith on
     github).

   - bpo-31185(40): Fixed miscellaneous errors in asyncio speedup
     module.

   - bpo-31151(41): socketserver.ForkingMixIn.server_close() now waits
     until all child processes completed to prevent leaking zombie
     processes.

   - bpo-31072(42): Add an ‘include_file’ parameter to
     ‘zipapp.create_archive()’

   - bpo-24700(43): Optimize array.array comparison.  It is now from 10x
     up to 70x faster when comparing arrays holding values of the same
     integer type.

   - bpo-31135(44): ttk: fix the destroy() method of LabeledScale and
     OptionMenu classes.  Call the parent destroy() method even if the
     used attribute doesn't exist.  The LabeledScale.destroy() method
     now also explicitly clears label and scale attributes to help the
     garbage collector to destroy all widgets.

   - bpo-31107(45): Fix ‘copyreg._slotnames()’ mangled attribute
     calculation for classes whose name begins with an underscore.
     Patch by Shane Harvey.

   - bpo-31080(46): Allow ‘logging.config.fileConfig’ to accept kwargs
     and/or args.

   - bpo-30897(47): ‘pathlib.Path’ objects now include an ‘is_mount()’
     method (only implemented on POSIX). This is similar to
     ‘os.path.ismount(p)’.  Patch by Cooper Ry Lees.

   - bpo-31061(48): Fixed a crash when using asyncio and threads.

   - bpo-30987(49): Added support for CAN ISO-TP protocol in the socket
     module.

   - bpo-30522(50): Added a ‘setStream’ method to
     ‘logging.StreamHandler’ to allow the stream to be set after
     creation.

   - bpo-30502(51): Fix handling of long oids in ssl.  Based on patch by
     Christian Heimes.

   - bpo-5288(52): Support tzinfo objects with sub-minute offsets.

   - bpo-30919(53): Fix shared memory performance regression in
     multiprocessing in 3.x.  Shared memory used anonymous memory
     mappings in 2.x, while 3.x mmaps actual files.  Try to be careful
     to do as little disk I/O as possible.

   - bpo-26732(54): Fix too many fds in processes started with the
     "forkserver" method.  A child process would inherit as many fds as
     the number of still-running children.

   - bpo-29403(55): Fix ‘unittest.mock’'s autospec to not fail on
     method-bound builtin functions.  Patch by Aaron Gallagher.

   - bpo-30961(56): Fix decrementing a borrowed reference in
     tracemalloc.

   - bpo-19896(57): Fix multiprocessing.sharedctypes to recognize
     typecodes ‘'q'’ and ‘'Q'’.

   - bpo-30946(58): Remove obsolete code in readline module for
     platforms where GNU readline is older than 2.1 or where select() is
     not available.

   - bpo-25684(59): Change ‘ttk.OptionMenu’ radiobuttons to be unique
     across instances of ‘OptionMenu’.

   - bpo-30886(60): Fix multiprocessing.Queue.join_thread(): it now
     waits until the thread completes, even if the thread was started by
     the same process which created the queue.

   - bpo-29854(61): Fix segfault in readline when using readline's
     history-size option.  Patch by Nir Soffer.

   - bpo-30794(62): Added multiprocessing.Process.kill method to
     terminate using the SIGKILL signal on Unix.

   - bpo-30319(63): socket.close() now ignores ECONNRESET error.

   - bpo-30828(64): Fix out of bounds write in
     ‘asyncio.CFuture.remove_done_callback()’.

   - bpo-30302(65): Use keywords in the ‘repr’ of ‘datetime.timedelta’.

   - bpo-30807(66): signal.setitimer() may disable the timer when passed
     a tiny value.  Tiny values (such as 1e-6) are valid non-zero values
     for setitimer(), which is specified as taking
     microsecond-resolution intervals.  However, on some platform, our
     conversion routine could convert 1e-6 into a zero interval,
     therefore disabling the timer instead of (re-)scheduling it.

   - bpo-30441(67): Fix bug when modifying os.environ while iterating
     over it

   - bpo-29585(68): Avoid importing ‘sysconfig’ from ‘site’ to improve
     startup speed.  Python startup is about 5% faster on Linux and 30%
     faster on macOS.

   - bpo-29293(69): Add missing parameter "n" on
     multiprocessing.Condition.notify().  The doc claims
     multiprocessing.Condition behaves like threading.Condition, but its
     notify() method lacked the optional "n" argument (to specify the
     number of sleepers to wake up) that threading.Condition.notify()
     accepts.

   - bpo-30532(70): Fix email header value parser dropping folding white
     space in certain cases.

   - bpo-30596(71): Add a ‘close()’ method to ‘multiprocessing.Process’.

   - bpo-9146(72): Fix a segmentation fault in _hashopenssl when
     standard hash functions such as md5 are not available in the linked
     OpenSSL library.  As in some special FIPS-140 build environments.

   - bpo-29169(73): Update zlib to 1.2.11.

   - bpo-30119(74): ftplib.FTP.putline() now throws ValueError on
     commands that contains CR or LF. Patch by Donghee Na.

   - bpo-30879(75): os.listdir() and os.scandir() now emit bytes names
     when called with bytes-like argument.

   - bpo-30746(76): Prohibited the '=' character in environment variable
     names in ‘os.putenv()’ and ‘os.spawn*()’.

   - bpo-30664(77): The description of a unittest subtest now preserves
     the order of keyword arguments of TestCase.subTest().

   - bpo-21071(78): struct.Struct.format type is now *note str: 3f2.
     instead of *note bytes: 1a5.

   - bpo-29212(79): Fix concurrent.futures.thread.ThreadPoolExecutor
     threads to have a non repr() based thread name by default when no
     thread_name_prefix is supplied.  They will now identify themselves
     as "ThreadPoolExecutor-y_n".

   - bpo-29755(80): Fixed the lgettext() family of functions in the
     gettext module.  They now always return bytes.

   - bpo-30616(81): Functional API of enum allows to create empty enums.
     Patched by Donghee Na

   - bpo-30038(82): Fix race condition between signal delivery and
     wakeup file descriptor.  Patch by Nathaniel Smith.

   - bpo-23894(83): lib2to3 now recognizes ‘rb'...'’ and ‘f'...'’
     strings.

   - bpo-24744(84): pkgutil.walk_packages function now raises ValueError
     if 'path' is a string.  Patch by Sanyam Khurana.

   - bpo-24484(85): Avoid race condition in multiprocessing cleanup.

   - bpo-30589(86): Fix multiprocessing.Process.exitcode to return the
     opposite of the signal number when the process is killed by a
     signal (instead of 255) when using the "forkserver" method.

   - bpo-28994(87): The traceback no longer displayed for SystemExit
     raised in a callback registered by atexit.

   - bpo-30508(88): Don't log exceptions if Task/Future "cancel()"
     method was called.

   - bpo-30645(89): Fix path calculation in ‘imp.load_package()’, fixing
     it for cases when a package is only shipped with bytecodes.  Patch
     by Alexandru Ardelean.

   - bpo-11822(90): The dis.dis() function now is able to disassemble
     nested code objects.

   - bpo-30624(91): selectors does not take KeyboardInterrupt and
     SystemExit into account, leaving a fd in a bad state in case of
     error.  Patch by Giampaolo Rodola'.

   - bpo-30595(92): multiprocessing.Queue.get() with a timeout now polls
     its reader in non-blocking mode if it succeeded to acquire the lock
     but the acquire took longer than the timeout.

   - bpo-28556(93): Updates to typing module: Add generic
     AsyncContextManager, add support for ContextManager on all
     versions.  Original PRs by Jelle Zijlstra and Ivan Levkivskyi

   - bpo-30605(94): re.compile() no longer raises a BytesWarning when
     compiling a bytes instance with misplaced inline modifier.  Patch
     by Roy Williams.

   - bpo-29870(95): Fix ssl sockets leaks when connection is aborted in
     asyncio/ssl implementation.  Patch by Michaël Sghaïer.

   - bpo-29743(96): Closing transport during handshake process leaks
     open socket.  Patch by Nikolay Kim

   - bpo-27585(97): Fix waiter cancellation in asyncio.Lock.  Patch by
     Mathieu Sornay.

   - bpo-30014(98): modify() method of poll(), epoll() and devpoll()
     based classes of selectors module is around 10% faster.  Patch by
     Giampaolo Rodola'.

   - bpo-30418(99): On Windows, subprocess.Popen.communicate() now also
     ignore EINVAL on stdin.write() if the child process is still
     running but closed the pipe.

   - bpo-30463(100): Addded empty __slots__ to abc.ABC. This allows
     subclassers to deny __dict__ and __weakref__ creation.  Patch by
     Aaron Hall.

   - bpo-30520(101): Loggers are now pickleable.

   - bpo-30557(102): faulthandler now correctly filters and displays
     exception codes on Windows

   - bpo-30526(103): Add TextIOWrapper.reconfigure() and a
     TextIOWrapper.write_through attribute.

   - bpo-30245(104): Fix possible overflow when organize
     struct.pack_into error message.  Patch by Yuan Liu.

   - bpo-30378(105): Fix the problem that logging.handlers.SysLogHandler
     cannot handle IPv6 addresses.

   - bpo-16500(106): Allow registering at-fork handlers.

   - bpo-30470(107): Deprecate invalid ctypes call protection on
     Windows.  Patch by Mariatta Wijaya.

   - bpo-30414(108): multiprocessing.Queue._feed background running
     thread do not break from main loop on exception.

   - bpo-30003(109): Fix handling escape characters in HZ codec.  Based
     on patch by Ma Lin.

   - bpo-30149(110): inspect.signature() now supports callables with
     variable-argument parameters wrapped with partialmethod.  Patch by
     Donghee Na.

   - bpo-30436(111): importlib.find_spec() raises ModuleNotFoundError
     instead of AttributeError if the specified parent module is not a
     package (i.e.  lacks a __path__ attribute).

   - bpo-30301(112): Fix AttributeError when using SimpleQueue.empty()
     under 'spawn' and 'forkserver' start methods.

   - bpo-30375(113): Warnings emitted when compile a regular expression
     now always point to the line in the user code.  Previously they
     could point into inners of the re module if emitted from inside of
     groups or conditionals.

   - bpo-30329(114): imaplib and poplib now catch the Windows socket
     WSAEINVAL error (code 10022) on shutdown(SHUT_RDWR): An invalid
     operation was attempted.  This error occurs sometimes on SSL
     connections.

   - bpo-29196(115): Removed previously deprecated in Python 2.4 classes
     Plist, Dict and _InternalDict in the plistlib module.  Dict values
     in the result of functions readPlist() and readPlistFromBytes() are
     now normal dicts.  You no longer can use attribute access to access
     items of these dictionaries.

   - bpo-9850(116): The ‘macpath’ is now deprecated and will be removed
     in Python 3.8.

   - bpo-30299(117): Compiling regular expression in debug mode on
     CPython now displays the compiled bytecode in human readable form.

   - bpo-30048(118): Fixed ‘Task.cancel()’ can be ignored when the task
     is running coroutine and the coroutine returned without any more
     ‘await’.

   - bpo-30266(119): contextlib.AbstractContextManager now supports
     anti-registration by setting __enter__ = None or __exit__ = None,
     following the pattern introduced in bpo-25958(120).  Patch by Jelle
     Zijlstra.

   - bpo-30340(121): Enhanced regular expressions optimization.  This
     increased the performance of matching some patterns up to 25 times.

   - bpo-30298(122): Weaken the condition of deprecation warnings for
     inline modifiers.  Now allowed several subsequential inline
     modifiers at the start of the pattern (e.g.  ‘'(?i)(?s)...'’).  In
     verbose mode whitespaces and comments now are allowed before and
     between inline modifiers (e.g.  ‘'(?x) (?i) (?s)...'’).

   - bpo-30285(123): Optimized case-insensitive matching and searching
     of regular expressions.

   - bpo-29990(124): Fix range checking in GB18030 decoder.  Original
     patch by Ma Lin.

   - bpo-29979(125): rewrite cgi.parse_multipart, reusing the
     FieldStorage class and making its results consistent with those of
     FieldStorage for multipart/form-data requests.  Patch by Pierre
     Quentel.

   - bpo-30243(126): Removed the __init__ methods of _json's scanner and
     encoder.  Misusing them could cause memory leaks or crashes.  Now
     scanner and encoder objects are completely initialized in the
     __new__ methods.

   - bpo-30215(127): Compiled regular expression objects with the
     re.LOCALE flag no longer depend on the locale at compile time.
     Only the locale at matching time affects the result of matching.

   - bpo-30185(128): Avoid KeyboardInterrupt tracebacks in forkserver
     helper process when Ctrl-C is received.

   - bpo-30103(129): binascii.b2a_uu() and uu.encode() now support using
     ‘'`'’ as zero instead of space.

   - bpo-28556(130): Various updates to typing module: add
     typing.NoReturn type, use WrapperDescriptorType, minor bug-fixes.
     Original PRs by Jim Fasarakis-Hilliard and Ivan Levkivskyi.

   - bpo-30205(131): Fix getsockname() for unbound AF_UNIX sockets on
     Linux.

   - bpo-30228(132): The seek() and tell() methods of io.FileIO now set
     the internal seekable attribute to avoid one syscall on open() (in
     buffered or text mode).

   - bpo-30190(133): unittest's assertAlmostEqual and
     assertNotAlmostEqual provide a better message in case of failure
     which includes the difference between left and right arguments.
     (patch by Giampaolo Rodola')

   - bpo-30101(134): Add support for curses.A_ITALIC.

   - bpo-29822(135): inspect.isabstract() now works during
     __init_subclass__.  Patch by Nate Soares.

   - bpo-29960(136): Preserve generator state when
     _random.Random.setstate() raises an exception.  Patch by Bryan
     Olson.

   - bpo-30070(137): Fixed leaks and crashes in errors handling in the
     parser module.

   - bpo-22352(138): Column widths in the output of dis.dis() are now
     adjusted for large line numbers and instruction offsets.

   - bpo-30061(139): Fixed crashes in IOBase methods __next__() and
     readlines() when readline() or __next__() respectively return
     non-sizeable object.  Fixed possible other errors caused by not
     checking results of PyObject_Size(), PySequence_Size(), or
     PyMapping_Size().

   - bpo-30218(140): Fix PathLike support for shutil.unpack_archive.
     Patch by Jelle Zijlstra.

   - bpo-10076(141): Compiled regular expression and match objects in
     the re module now support copy.copy() and copy.deepcopy() (they are
     considered atomic).

   - bpo-30068(142): _io._IOBase.readlines will check if it's closed
     first when hint is present.

   - bpo-29694(143): Fixed race condition in pathlib mkdir with flags
     parents=True.  Patch by Armin Rigo.

   - bpo-29692(144): Fixed arbitrary unchaining of RuntimeError
     exceptions in contextlib.contextmanager.  Patch by Siddharth
     Velankar.

   - bpo-26187(145): Test that sqlite3 trace callback is not called
     multiple times when schema is changing.  Indirectly fixed by
     switching to use sqlite3_prepare_v2() in bpo-9303(146).  Patch by
     Aviv Palivoda.

   - bpo-30017(147): Allowed calling the close() method of the zip entry
     writer object multiple times.  Writing to a closed writer now
     always produces a ValueError.

   - bpo-29998(148): Pickling and copying ImportError now preserves name
     and path attributes.

   - bpo-29995(149): re.escape() now escapes only regex special
     characters.

   - bpo-29962(150): Add math.remainder operation, implementing
     remainder as specified in IEEE 754.

   - bpo-29649(151): Improve struct.pack_into() exception messages for
     problems with the buffer size and offset.  Patch by Andrew Nester.

   - bpo-29654(152): Support If-Modified-Since HTTP header (browser
     cache).  Patch by Pierre Quentel.

   - bpo-29931(153): Fixed comparison check for ipaddress.ip_interface
     objects.  Patch by Sanjay Sundaresan.

   - bpo-29953(154): Fixed memory leaks in the replace() method of
     datetime and time objects when pass out of bound fold argument.

   - bpo-29942(155): Fix a crash in itertools.chain.from_iterable when
     encountering long runs of empty iterables.

   - bpo-10030(156): Sped up reading encrypted ZIP files by 2 times.

   - bpo-29204(157): Element.getiterator() and the html parameter of
     XMLParser() were deprecated only in the documentation (since Python
     3.2 and 3.4 correspondingly).  Now using them emits a deprecation
     warning.

   - bpo-27863(158): Fixed multiple crashes in ElementTree caused by
     race conditions and wrong types.

   - bpo-25996(159): Added support of file descriptors in os.scandir()
     on Unix.  os.fwalk() is sped up by 2 times by using os.scandir().

   - bpo-28699(160): Fixed a bug in pools in multiprocessing.pool that
     raising an exception at the very first of an iterable may swallow
     the exception or make the program hang.  Patch by Davin Potts and
     Xiang Zhang.

   - bpo-23890(161): unittest.TestCase.assertRaises() now manually
     breaks a reference cycle to not keep objects alive longer than
     expected.

   - bpo-29901(162): The zipapp module now supports general path-like
     objects, not just pathlib.Path.

   - bpo-25803(163): Avoid incorrect errors raised by
     Path.mkdir(exist_ok=True) when the OS gives priority to errors such
     as EACCES over EEXIST.

   - bpo-29861(164): Release references to tasks, their arguments and
     their results as soon as they are finished in multiprocessing.Pool.

   - bpo-19930(165): The mode argument of os.makedirs() no longer
     affects the file permission bits of newly created
     intermediate-level directories.

   - bpo-29884(166): faulthandler: Restore the old sigaltstack during
     teardown.  Patch by Christophe Zeitouny.

   - bpo-25455(167): Fixed crashes in repr of recursive buffered
     file-like objects.

   - bpo-29800(168): Fix crashes in partial.__repr__ if the keys of
     partial.keywords are not strings.  Patch by Michael Seifert.

   - bpo-8256(169): Fixed possible failing or crashing input() if
     attributes "encoding" or "errors" of sys.stdin or sys.stdout are
     not set or are not strings.

   - bpo-28692(170): Using non-integer value for selecting a plural form
     in gettext is now deprecated.

   - bpo-26121(171): Use C library implementation for math functions
     erf() and erfc().

   - bpo-29619(172): os.stat() and os.DirEntry.inode() now convert inode
     (st_ino) using unsigned integers.

   - bpo-28298(173): Fix a bug that prevented array 'Q', 'L' and 'I'
     from accepting big intables (objects that have __int__) as
     elements.

   - bpo-29645(174): Speed up importing the webbrowser module.
     webbrowser.register() is now thread-safe.

   - bpo-28231(175): The zipfile module now accepts path-like objects
     for external paths.

   - bpo-26915(176): index() and count() methods of
     collections.abc.Sequence now check identity before checking
     equality when do comparisons.

   - bpo-28682(177): Added support for bytes paths in os.fwalk().

   - bpo-29728(178): Add new ‘socket.TCP_NOTSENT_LOWAT’ (Linux 3.12)
     constant.  Patch by Nathaniel J. Smith.

   - bpo-29623(179): Allow use of path-like object as a single argument
     in ConfigParser.read().  Patch by David Ellis.

   - bpo-9303(180): Migrate sqlite3 module to _v2 API. Patch by Aviv
     Palivoda.

   - bpo-28963(181): Fix out of bound iteration in
     asyncio.Future.remove_done_callback implemented in C.

   - bpo-29704(182): asyncio.subprocess.SubprocessStreamProtocol no
     longer closes before all pipes are closed.

   - bpo-29271(183): Fix Task.current_task and Task.all_tasks
     implemented in C to accept None argument as their pure Python
     implementation.

   - bpo-29703(184): Fix asyncio to support instantiation of new event
     loops in child processes.

   - bpo-29615(185): SimpleXMLRPCDispatcher no longer chains KeyError
     (or any other exception) to exception(s) raised in the dispatched
     methods.  Patch by Petr Motejlek.

   - bpo-7769(186): Method register_function() of
     xmlrpc.server.SimpleXMLRPCDispatcher and its subclasses can now be
     used as a decorator.

   - bpo-29376(187): Fix assertion error in
     threading._DummyThread.is_alive().

   - bpo-28624(188): Add a test that checks that cwd parameter of
     Popen() accepts PathLike objects.  Patch by Sayan Chowdhury.

   - bpo-28518(189): Start a transaction implicitly before a DML
     statement.  Patch by Aviv Palivoda.

   - bpo-29742(190): get_extra_info() raises exception if get called on
     closed ssl transport.  Patch by Nikolay Kim.

   - bpo-16285(191): urllib.parse.quote is now based on RFC 3986 and
     hence includes '~' in the set of characters that is not quoted by
     default.  Patch by Christian Theune and Ratnadeep Debnath.

   - bpo-29532(192): Altering a kwarg dictionary passed to
     functools.partial() no longer affects a partial object after
     creation.

   - bpo-29110(193): Fix file object leak in aifc.open() when file is
     given as a filesystem path and is not in valid AIFF format.  Patch
     by Anthony Zhang.

   - bpo-22807(194): Add uuid.SafeUUID and uuid.UUID.is_safe to relay
     information from the platform about whether generated UUIDs are
     generated with a multiprocessing safe method.

   - bpo-29576(195): Improve some deprecations in importlib.  Some
     deprecated methods now emit DeprecationWarnings and have better
     descriptive messages.

   - bpo-29534(196): Fixed different behaviour of Decimal.from_float()
     for _decimal and _pydecimal.  Thanks Andrew Nester.

   - bpo-10379(197): locale.format_string now supports the 'monetary'
     keyword argument, and locale.format is deprecated.

   - bpo-29851(198): importlib.reload() now raises ModuleNotFoundError
     if the module lacks a spec.

   - bpo-28556(199): Various updates to typing module: typing.Counter,
     typing.ChainMap, improved ABC caching, etc.  Original PRs by Jelle
     Zijlstra, Ivan Levkivskyi, Manuel Krebber, and Łukasz Langa.

   - bpo-29100(200): Fix datetime.fromtimestamp() regression introduced
     in Python 3.6.0: check minimum and maximum years.

   - bpo-29416(201): Prevent infinite loop in pathlib.Path.mkdir

   - bpo-29444(202): Fixed out-of-bounds buffer access in the group()
     method of the match object.  Based on patch by WGH.

   - bpo-29377(203): Add WrapperDescriptorType, MethodWrapperType, and
     MethodDescriptorType built-in types to types module.  Original
     patch by Manuel Krebber.

   - bpo-29218(204): Unused install_misc command is now removed.  It has
     been documented as unused since 2000.  Patch by Eric N. Vander
     Weele.

   - bpo-29368(205): The extend() method is now called instead of the
     append() method when unpickle collections.deque and other list-like
     objects.  This can speed up unpickling to 2 times.

   - bpo-29338(206): The help of a builtin or extension class now
     includes the constructor signature if __text_signature__ is
     provided for the class.

   - bpo-29335(207): Fix subprocess.Popen.wait() when the child process
     has exited to a stopped instead of terminated state (ex: when under
     ptrace).

   - bpo-29290(208): Fix a regression in argparse that help messages
     would wrap at non-breaking spaces.

   - bpo-28735(209): Fixed the comparison of mock.MagickMock with
     mock.ANY.

   - bpo-29197(210): Removed deprecated function ntpath.splitunc().

   - bpo-29210(211): Removed support of deprecated argument "exclude" in
     tarfile.TarFile.add().

   - bpo-29219(212): Fixed infinite recursion in the repr of
     uninitialized ctypes.CDLL instances.

   - bpo-29192(213): Removed deprecated features in the http.cookies
     module.

   - bpo-29193(214): A format string argument for
     string.Formatter.format() is now positional-only.

   - bpo-29195(215): Removed support of deprecated undocumented keyword
     arguments in methods of regular expression objects.

   - bpo-28969(216): Fixed race condition in C implementation of
     functools.lru_cache.  KeyError could be raised when cached function
     with full cache was simultaneously called from different threads
     with the same uncached arguments.

   - bpo-20804(217): The unittest.mock.sentinel attributes now preserve
     their identity when they are copied or pickled.

   - bpo-29142(218): In urllib.request, suffixes in no_proxy environment
     variable with leading dots could match related hostnames again
     (e.g.  .b.c matches a.b.c).  Patch by Milan Oberkirch.

   - bpo-28961(219): Fix unittest.mock._Call helper: don't ignore the
     name parameter anymore.  Patch written by Jiajun Huang.

   - bpo-15812(220): inspect.getframeinfo() now correctly shows the
     first line of a context.  Patch by Sam Breese.

   - bpo-28985(221): Update authorizer constants in sqlite3 module.
     Patch by Dingyuan Wang.

   - bpo-29079(222): Prevent infinite loop in pathlib.resolve() on
     Windows

   - bpo-13051(223): Fixed recursion errors in large or resized
     curses.textpad.Textbox.  Based on patch by Tycho Andersen.

   - bpo-9770(224): curses.ascii predicates now work correctly with
     negative integers.

   - bpo-28427(225): old keys should not remove new values from
     WeakValueDictionary when collecting from another thread.

   - bpo-28923(226): Remove editor artifacts from Tix.py.

   - bpo-28871(227): Fixed a crash when deallocate deep ElementTree.

   - bpo-19542(228): Fix bugs in WeakValueDictionary.setdefault() and
     WeakValueDictionary.pop() when a GC collection happens in another
     thread.

   - bpo-20191(229): Fixed a crash in resource.prlimit() when passing a
     sequence that doesn't own its elements as limits.

   - bpo-16255(230): subprocess.Popen uses /system/bin/sh on Android as
     the shell, instead of /bin/sh.

   - bpo-28779(231): multiprocessing.set_forkserver_preload() would
     crash the forkserver process if a preloaded module instantiated
     some multiprocessing objects such as locks.

   - bpo-26937(232): The chown() method of the tarfile.TarFile class
     does not fail now when the grp module cannot be imported, as for
     example on Android platforms.

   - bpo-28847(233): dbm.dumb now supports reading read-only files and
     no longer writes the index file when it is not changed.  A
     deprecation warning is now emitted if the index file is missed and
     recreated in the 'r' and 'w' modes (will be an error in future
     Python releases).

   - bpo-27030(234): Unknown escapes consisting of ‘'\'’ and an ASCII
     letter in re.sub() replacement templates regular expressions now
     are errors.

   - bpo-28835(235): Fix a regression introduced in
     warnings.catch_warnings(): call warnings.showwarning() if it was
     overridden inside the context manager.

   - bpo-27172(236): To assist with upgrades from 2.7, the previously
     documented deprecation of ‘inspect.getfullargspec()’ has been
     reversed.  This decision may be revisited again after the Python
     2.7 branch is no longer officially supported.

   - bpo-28740(237): Add sys.getandroidapilevel(): return the build time
     API version of Android as an integer.  Function only available on
     Android.

   - bpo-26273(238): Add new ‘socket.TCP_CONGESTION’ (Linux 2.6.13) and
     ‘socket.TCP_USER_TIMEOUT’ (Linux 2.6.37) constants.  Patch written
     by Omar Sandoval.

   - bpo-28752(239): Restored the __reduce__() methods of datetime
     objects.

   - bpo-28727(240): Regular expression patterns, _sre.SRE_Pattern
     objects created by re.compile(), become comparable (only x==y and
     x!=y operators).  This change should fix the bpo-18383(241): don't
     duplicate warning filters when the warnings module is reloaded
     (thing usually only done in unit tests).

   - bpo-20572(242): Remove the subprocess.Popen.wait endtime parameter.
     It was deprecated in 3.4 and undocumented prior to that.

   - bpo-25659(243): In ctypes, prevent a crash calling the
     from_buffer() and from_buffer_copy() methods on abstract classes
     like Array.

   - bpo-28548(244): In the "http.server" module, parse the protocol
     version if possible, to avoid using HTTP 0.9 in some error
     responses.

   - bpo-19717(245): Makes Path.resolve() succeed on paths that do not
     exist.  Patch by Vajrasky Kok

   - bpo-28563(246): Fixed possible DoS and arbitrary code execution
     when handle plural form selections in the gettext module.  The
     expression parser now supports exact syntax supported by GNU
     gettext.

   - bpo-28387(247): Fixed possible crash in _io.TextIOWrapper
     deallocator when the garbage collector is invoked in other thread.
     Based on patch by Sebastian Cufre.

   - bpo-27517(248): LZMA compressor and decompressor no longer raise
     exceptions if given empty data twice.  Patch by Benjamin Fogle.

   - bpo-28549(249): Fixed segfault in curses's addch() with ncurses6.

   - bpo-28449(250): tarfile.open() with mode "r" or "r:" now tries to
     open a tar file with compression before trying to open it without
     compression.  Otherwise it had 50% chance failed with
     ignore_zeros=True.

   - bpo-23262(251): The webbrowser module now supports Firefox 36+ and
     derived browsers.  Based on patch by Oleg Broytman.

   - bpo-24241(252): The webbrowser in an X environment now prefers
     using the default browser directly.  Also, the webbrowser
     register() function now has a documented 'preferred' argument, to
     specify browsers to be returned by get() with no arguments.  Patch
     by David Steele

   - bpo-27939(253): Fixed bugs in tkinter.ttk.LabeledScale and
     tkinter.Scale caused by representing the scale as float value
     internally in Tk.  tkinter.IntVar now works if float value is set
     to underlying Tk variable.

   - bpo-28255(254): calendar.TextCalendar.prweek() no longer prints a
     space after a weeks's calendar.  calendar.TextCalendar.pryear() no
     longer prints redundant newline after a year's calendar.  Based on
     patch by Xiang Zhang.

   - bpo-28255(255): calendar.TextCalendar.prmonth() no longer prints a
     space at the start of new line after printing a month's calendar.
     Patch by Xiang Zhang.

   - bpo-20491(256): The textwrap.TextWrapper class now honors
     non-breaking spaces.  Based on patch by Kaarle Ritvanen.

   - bpo-28353(257): os.fwalk() no longer fails on broken links.

   - bpo-28430(258): Fix iterator of C implemented asyncio.Future
     doesn't accept non-None value is passed to it.send(val).

   - bpo-27025(259): Generated names for Tkinter widgets now start by
     the "!"  prefix for readability.

   - bpo-25464(260): Fixed HList.header_exists() in tkinter.tix module
     by addin a workaround to Tix library bug.

   - bpo-28488(261): shutil.make_archive() no longer adds entry "./" to
     ZIP archive.

   - bpo-25953(262): re.sub() now raises an error for invalid numerical
     group reference in replacement template even if the pattern is not
     found in the string.  Error message for invalid group reference now
     includes the group index and the position of the reference.  Based
     on patch by SilentGhost.

   - bpo-28469(263): timeit now uses the sequence 1, 2, 5, 10, 20,
     50,...  instead of 1, 10, 100,...  for autoranging.

   - bpo-28115(264): Command-line interface of the zipfile module now
     uses argparse.  Added support of long options.

   - bpo-18219(265): Optimize csv.DictWriter for large number of
     columns.  Patch by Mariatta Wijaya.

   - bpo-28448(266): Fix C implemented asyncio.Future didn't work on
     Windows.

   - bpo-23214(267): In the "io" module, the argument to BufferedReader
     and BytesIO's read1() methods is now optional and can be -1,
     matching the BufferedIOBase specification.

   - bpo-28480(268): Fix error building socket module when
     multithreading is disabled.

   - bpo-28240(269): timeit: remove ‘-c/--clock’ and ‘-t/--time’ command
     line options which were deprecated since Python 3.3.

   - bpo-28240(270): timeit now repeats the benchmarks 5 times instead
     of only 3 to make benchmarks more reliable.

   - bpo-28240(271): timeit autorange now uses a single loop iteration
     if the benchmark takes less than 10 seconds, instead of 10
     iterations.  "python3 -m timeit -s 'import time' 'time.sleep(1)'"
     now takes 4 seconds instead of 40 seconds.

   - Distutils.sdist now looks for README and setup.py files with case
     sensitivity.  This behavior matches that found in Setuptools 6.0
     and later.  See setuptools 100(272) for rationale.

   - bpo-24452(273): Make webbrowser support Chrome on Mac OS X. Patch
     by Ned Batchelder.

   - bpo-20766(274): Fix references leaked by pdb in the handling of
     SIGINT handlers.

   - bpo-27998(275): Fixed bytes path support in os.scandir() on
     Windows.  Patch by Eryk Sun.

   - bpo-28317(276): The disassembler now decodes FORMAT_VALUE argument.

   - bpo-28380(277): unittest.mock Mock autospec functions now properly
     support assert_called, assert_not_called, and assert_called_once.

   - bpo-28229(278): lzma module now supports pathlib.

   - bpo-28321(279): Fixed writing non-BMP characters with binary format
     in plistlib.

   - bpo-28225(280): bz2 module now supports pathlib.  Initial patch by
     Ethan Furman.

   - bpo-28227(281): gzip now supports pathlib.  Patch by Ethan Furman.

   - bpo-28332(282): Deprecated silent truncations in socket.htons and
     socket.ntohs.  Original patch by Oren Milman.

   - bpo-27358(283): Optimized merging var-keyword arguments and
     improved error message when passing a non-mapping as a var-keyword
     argument.

   - bpo-28257(284): Improved error message when passing a non-iterable
     as a var-positional argument.  Added opcode
     BUILD_TUPLE_UNPACK_WITH_CALL.

   - bpo-28322(285): Fixed possible crashes when unpickle itertools
     objects from incorrect pickle data.  Based on patch by John Leitch.

   - bpo-28228(286): imghdr now supports pathlib.

   - bpo-28226(287): compileall now supports pathlib.

   - bpo-28314(288): Fix function declaration (C flags) for the
     getiterator() method of xml.etree.ElementTree.Element.

   - bpo-28148(289): Stop using localtime() and gmtime() in the time
     module.  Introduced platform independent _PyTime_localtime API that
     is similar to POSIX localtime_r, but available on all platforms.
     Patch by Ed Schouten.

   - bpo-28253(290): Fixed calendar functions for extreme months:
     0001-01 and 9999-12.  Methods itermonthdays() and itermonthdays2()
     are reimplemented so that they don't call itermonthdates() which
     can cause datetime.date under/overflow.

   - bpo-28275(291): Fixed possible use after free in the decompress()
     methods of the LZMADecompressor and BZ2Decompressor classes.
     Original patch by John Leitch.

   - bpo-27897(292): Fixed possible crash in
     sqlite3.Connection.create_collation() if pass invalid string-like
     object as a name.  Patch by Xiang Zhang.

   - bpo-18844(293): random.choices() now has k as a keyword-only
     argument to improve the readability of common cases and come into
     line with the signature used in other languages.

   - bpo-18893(294): Fix invalid exception handling in
     Lib/ctypes/macholib/dyld.py.  Patch by Madison May.

   - bpo-27611(295): Fixed support of default root window in the
     tkinter.tix module.  Added the master parameter in the DisplayStyle
     constructor.

   - bpo-27348(296): In the traceback module, restore the formatting of
     exception messages like "Exception: None".  This fixes a regression
     introduced in 3.5a2.

   - bpo-25651(297): Allow false values to be used for msg parameter of
     subTest().

   - bpo-27778(298): Fix a memory leak in os.getrandom() when the
     getrandom() is interrupted by a signal and a signal handler raises
     a Python exception.

   - bpo-28200(299): Fix memory leak on Windows in the os module (fix
     path_converter() function).

   - bpo-25400(300): RobotFileParser now correctly returns default
     values for crawl_delay and request_rate.  Initial patch by Peter
     Wirtz.

   - bpo-27932(301): Prevent memory leak in win32_ver().

   - Fix UnboundLocalError in socket._sendfile_use_sendfile.

   - bpo-28075(302): Check for ERROR_ACCESS_DENIED in Windows
     implementation of os.stat().  Patch by Eryk Sun.

   - bpo-22493(303): Warning message emitted by using inline flags in
     the middle of regular expression now contains a (truncated) regex
     pattern.  Patch by Tim Graham.

   - bpo-25270(304): Prevent codecs.escape_encode() from raising
     SystemError when an empty bytestring is passed.

   - bpo-28181(305): Get antigravity over HTTPS. Patch by Kaartic
     Sivaraam.

   - bpo-25895(306): Enable WebSocket URL schemes in
     urllib.parse.urljoin.  Patch by Gergely Imreh and Markus
     Holtermann.

   - bpo-28114(307): Fix a crash in parse_envlist() when env contains
     byte strings.  Patch by Eryk Sun.

   - bpo-27599(308): Fixed buffer overrun in binascii.b2a_qp() and
     binascii.a2b_qp().

   - bpo-27906(309): Fix socket accept exhaustion during high TCP
     traffic.  Patch by Kevin Conway.

   - bpo-28174(310): Handle when SO_REUSEPORT isn't properly supported.
     Patch by Seth Michael Larson.

   - bpo-26654(311): Inspect functools.partial in
     asyncio.Handle.__repr__.  Patch by iceboy.

   - bpo-26909(312): Fix slow pipes IO in asyncio.  Patch by INADA
     Naoki.

   - bpo-28176(313): Fix callbacks race in
     asyncio.SelectorLoop.sock_connect.

   - bpo-27759(314): Fix selectors incorrectly retain invalid file
     descriptors.  Patch by Mark Williams.

   - bpo-28325(315): Remove vestigial MacOS 9 macurl2path module and its
     tests.

   - bpo-28368(316): Refuse monitoring processes if the child watcher
     has no loop attached.  Patch by Vincent Michel.

   - bpo-28369(317): Raise RuntimeError when transport's FD is used with
     add_reader, add_writer, etc.

   - bpo-28370(318): Speedup asyncio.StreamReader.readexactly.  Patch by
     Коренберг Марк.

   - bpo-28371(319): Deprecate passing asyncio.Handles to
     run_in_executor.

   - bpo-28372(320): Fix asyncio to support formatting of non-python
     coroutines.

   - bpo-28399(321): Remove UNIX socket from FS before binding.  Patch
     by Коренберг Марк.

   - bpo-27972(322): Prohibit Tasks to await on themselves.

   - bpo-24142(323): Reading a corrupt config file left configparser in
     an invalid state.  Original patch by Florian Höch.

   - bpo-29581(324): ABCMeta.__new__ now accepts ‘**kwargs’, allowing
     abstract base classes to use keyword parameters in
     __init_subclass__.  Patch by Nate Soares.

   - bpo-25532(325): inspect.unwrap() will now only try to unwrap an
     object sys.getrecursionlimit() times, to protect against objects
     which create a new object on every attribute access.

   - bpo-30177(326): path.resolve(strict=False) no longer cuts the path
     after the first element not present in the filesystem.  Patch by
     Antoine Pietri.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31499

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31482

   (3) https://bugs.python.org/issue?@action=redirect&bpo=28556

   (4) https://bugs.python.org/issue?@action=redirect&bpo=28556

   (5) https://bugs.python.org/issue?@action=redirect&bpo=31544

   (6) https://bugs.python.org/issue?@action=redirect&bpo=31234

   (7) https://bugs.python.org/issue?@action=redirect&bpo=31457

   (8) https://bugs.python.org/issue?@action=redirect&bpo=31431

   (9) https://bugs.python.org/issue?@action=redirect&bpo=31233

   (10) https://bugs.python.org/issue?@action=redirect&bpo=28638

   (11) https://bugs.python.org/issue?@action=redirect&bpo=31400

   (12) https://bugs.python.org/issue?@action=redirect&bpo=27629

   (13) https://bugs.python.org/issue?@action=redirect&bpo=28958

   (14) https://bugs.python.org/issue?@action=redirect&bpo=28182

   (15) https://bugs.python.org/issue?@action=redirect&bpo=27340

   (16) https://bugs.python.org/issue?@action=redirect&bpo=14191

   (17) https://bugs.python.org/issue?@action=redirect&bpo=31178

   (18) https://bugs.python.org/issue?@action=redirect&bpo=31350

   (19) https://bugs.python.org/issue?@action=redirect&bpo=31170

   (20) https://bugs.python.org/issue?@action=redirect&bpo=29136

   (21) https://bugs.python.org/issue?@action=redirect&bpo=1198569

   (22) https://bugs.python.org/issue?@action=redirect&bpo=31326

   (23) https://bugs.python.org/issue?@action=redirect&bpo=27144

   (24) https://bugs.python.org/issue?@action=redirect&bpo=31281

   (25) https://bugs.python.org/issue?@action=redirect&bpo=10746

   (26) https://peps.python.org/pep-3118/

   (27) https://bugs.python.org/issue?@action=redirect&bpo=27584

   (28) https://bugs.python.org/issue?@action=redirect&bpo=22536

   (29) https://bugs.python.org/issue?@action=redirect&bpo=29741

   (30) https://bugs.python.org/issue?@action=redirect&bpo=31249

   (31) https://bugs.python.org/issue?@action=redirect&bpo=31247

   (32) https://bugs.python.org/issue?@action=redirect&bpo=23835

   (33) https://bugs.python.org/issue?@action=redirect&bpo=31238

   (34) https://bugs.python.org/issue?@action=redirect&bpo=5001

   (35) https://bugs.python.org/issue?@action=redirect&bpo=31109

   (36) https://bugs.python.org/issue?@action=redirect&bpo=30102

   (37) https://bugs.python.org/issue?@action=redirect&bpo=18966

   (38) https://bugs.python.org/issue?@action=redirect&bpo=31183

   (39) https://bugs.python.org/issue?@action=redirect&bpo=5001

   (40) https://bugs.python.org/issue?@action=redirect&bpo=31185

   (41) https://bugs.python.org/issue?@action=redirect&bpo=31151

   (42) https://bugs.python.org/issue?@action=redirect&bpo=31072

   (43) https://bugs.python.org/issue?@action=redirect&bpo=24700

   (44) https://bugs.python.org/issue?@action=redirect&bpo=31135

   (45) https://bugs.python.org/issue?@action=redirect&bpo=31107

   (46) https://bugs.python.org/issue?@action=redirect&bpo=31080

   (47) https://bugs.python.org/issue?@action=redirect&bpo=30897

   (48) https://bugs.python.org/issue?@action=redirect&bpo=31061

   (49) https://bugs.python.org/issue?@action=redirect&bpo=30987

   (50) https://bugs.python.org/issue?@action=redirect&bpo=30522

   (51) https://bugs.python.org/issue?@action=redirect&bpo=30502

   (52) https://bugs.python.org/issue?@action=redirect&bpo=5288

   (53) https://bugs.python.org/issue?@action=redirect&bpo=30919

   (54) https://bugs.python.org/issue?@action=redirect&bpo=26732

   (55) https://bugs.python.org/issue?@action=redirect&bpo=29403

   (56) https://bugs.python.org/issue?@action=redirect&bpo=30961

   (57) https://bugs.python.org/issue?@action=redirect&bpo=19896

   (58) https://bugs.python.org/issue?@action=redirect&bpo=30946

   (59) https://bugs.python.org/issue?@action=redirect&bpo=25684

   (60) https://bugs.python.org/issue?@action=redirect&bpo=30886

   (61) https://bugs.python.org/issue?@action=redirect&bpo=29854

   (62) https://bugs.python.org/issue?@action=redirect&bpo=30794

   (63) https://bugs.python.org/issue?@action=redirect&bpo=30319

   (64) https://bugs.python.org/issue?@action=redirect&bpo=30828

   (65) https://bugs.python.org/issue?@action=redirect&bpo=30302

   (66) https://bugs.python.org/issue?@action=redirect&bpo=30807

   (67) https://bugs.python.org/issue?@action=redirect&bpo=30441

   (68) https://bugs.python.org/issue?@action=redirect&bpo=29585

   (69) https://bugs.python.org/issue?@action=redirect&bpo=29293

   (70) https://bugs.python.org/issue?@action=redirect&bpo=30532

   (71) https://bugs.python.org/issue?@action=redirect&bpo=30596

   (72) https://bugs.python.org/issue?@action=redirect&bpo=9146

   (73) https://bugs.python.org/issue?@action=redirect&bpo=29169

   (74) https://bugs.python.org/issue?@action=redirect&bpo=30119

   (75) https://bugs.python.org/issue?@action=redirect&bpo=30879

   (76) https://bugs.python.org/issue?@action=redirect&bpo=30746

   (77) https://bugs.python.org/issue?@action=redirect&bpo=30664

   (78) https://bugs.python.org/issue?@action=redirect&bpo=21071

   (79) https://bugs.python.org/issue?@action=redirect&bpo=29212

   (80) https://bugs.python.org/issue?@action=redirect&bpo=29755

   (81) https://bugs.python.org/issue?@action=redirect&bpo=30616

   (82) https://bugs.python.org/issue?@action=redirect&bpo=30038

   (83) https://bugs.python.org/issue?@action=redirect&bpo=23894

   (84) https://bugs.python.org/issue?@action=redirect&bpo=24744

   (85) https://bugs.python.org/issue?@action=redirect&bpo=24484

   (86) https://bugs.python.org/issue?@action=redirect&bpo=30589

   (87) https://bugs.python.org/issue?@action=redirect&bpo=28994

   (88) https://bugs.python.org/issue?@action=redirect&bpo=30508

   (89) https://bugs.python.org/issue?@action=redirect&bpo=30645

   (90) https://bugs.python.org/issue?@action=redirect&bpo=11822

   (91) https://bugs.python.org/issue?@action=redirect&bpo=30624

   (92) https://bugs.python.org/issue?@action=redirect&bpo=30595

   (93) https://bugs.python.org/issue?@action=redirect&bpo=28556

   (94) https://bugs.python.org/issue?@action=redirect&bpo=30605

   (95) https://bugs.python.org/issue?@action=redirect&bpo=29870

   (96) https://bugs.python.org/issue?@action=redirect&bpo=29743

   (97) https://bugs.python.org/issue?@action=redirect&bpo=27585

   (98) https://bugs.python.org/issue?@action=redirect&bpo=30014

   (99) https://bugs.python.org/issue?@action=redirect&bpo=30418

   (100) https://bugs.python.org/issue?@action=redirect&bpo=30463

   (101) https://bugs.python.org/issue?@action=redirect&bpo=30520

   (102) https://bugs.python.org/issue?@action=redirect&bpo=30557

   (103) https://bugs.python.org/issue?@action=redirect&bpo=30526

   (104) https://bugs.python.org/issue?@action=redirect&bpo=30245

   (105) https://bugs.python.org/issue?@action=redirect&bpo=30378

   (106) https://bugs.python.org/issue?@action=redirect&bpo=16500

   (107) https://bugs.python.org/issue?@action=redirect&bpo=30470

   (108) https://bugs.python.org/issue?@action=redirect&bpo=30414

   (109) https://bugs.python.org/issue?@action=redirect&bpo=30003

   (110) https://bugs.python.org/issue?@action=redirect&bpo=30149

   (111) https://bugs.python.org/issue?@action=redirect&bpo=30436

   (112) https://bugs.python.org/issue?@action=redirect&bpo=30301

   (113) https://bugs.python.org/issue?@action=redirect&bpo=30375

   (114) https://bugs.python.org/issue?@action=redirect&bpo=30329

   (115) https://bugs.python.org/issue?@action=redirect&bpo=29196

   (116) https://bugs.python.org/issue?@action=redirect&bpo=9850

   (117) https://bugs.python.org/issue?@action=redirect&bpo=30299

   (118) https://bugs.python.org/issue?@action=redirect&bpo=30048

   (119) https://bugs.python.org/issue?@action=redirect&bpo=30266

   (120) https://bugs.python.org/issue?@action=redirect&bpo=25958

   (121) https://bugs.python.org/issue?@action=redirect&bpo=30340

   (122) https://bugs.python.org/issue?@action=redirect&bpo=30298

   (123) https://bugs.python.org/issue?@action=redirect&bpo=30285

   (124) https://bugs.python.org/issue?@action=redirect&bpo=29990

   (125) https://bugs.python.org/issue?@action=redirect&bpo=29979

   (126) https://bugs.python.org/issue?@action=redirect&bpo=30243

   (127) https://bugs.python.org/issue?@action=redirect&bpo=30215

   (128) https://bugs.python.org/issue?@action=redirect&bpo=30185

   (129) https://bugs.python.org/issue?@action=redirect&bpo=30103

   (130) https://bugs.python.org/issue?@action=redirect&bpo=28556

   (131) https://bugs.python.org/issue?@action=redirect&bpo=30205

   (132) https://bugs.python.org/issue?@action=redirect&bpo=30228

   (133) https://bugs.python.org/issue?@action=redirect&bpo=30190

   (134) https://bugs.python.org/issue?@action=redirect&bpo=30101

   (135) https://bugs.python.org/issue?@action=redirect&bpo=29822

   (136) https://bugs.python.org/issue?@action=redirect&bpo=29960

   (137) https://bugs.python.org/issue?@action=redirect&bpo=30070

   (138) https://bugs.python.org/issue?@action=redirect&bpo=22352

   (139) https://bugs.python.org/issue?@action=redirect&bpo=30061

   (140) https://bugs.python.org/issue?@action=redirect&bpo=30218

   (141) https://bugs.python.org/issue?@action=redirect&bpo=10076

   (142) https://bugs.python.org/issue?@action=redirect&bpo=30068

   (143) https://bugs.python.org/issue?@action=redirect&bpo=29694

   (144) https://bugs.python.org/issue?@action=redirect&bpo=29692

   (145) https://bugs.python.org/issue?@action=redirect&bpo=26187

   (146) https://bugs.python.org/issue?@action=redirect&bpo=9303

   (147) https://bugs.python.org/issue?@action=redirect&bpo=30017

   (148) https://bugs.python.org/issue?@action=redirect&bpo=29998

   (149) https://bugs.python.org/issue?@action=redirect&bpo=29995

   (150) https://bugs.python.org/issue?@action=redirect&bpo=29962

   (151) https://bugs.python.org/issue?@action=redirect&bpo=29649

   (152) https://bugs.python.org/issue?@action=redirect&bpo=29654

   (153) https://bugs.python.org/issue?@action=redirect&bpo=29931

   (154) https://bugs.python.org/issue?@action=redirect&bpo=29953

   (155) https://bugs.python.org/issue?@action=redirect&bpo=29942

   (156) https://bugs.python.org/issue?@action=redirect&bpo=10030

   (157) https://bugs.python.org/issue?@action=redirect&bpo=29204

   (158) https://bugs.python.org/issue?@action=redirect&bpo=27863

   (159) https://bugs.python.org/issue?@action=redirect&bpo=25996

   (160) https://bugs.python.org/issue?@action=redirect&bpo=28699

   (161) https://bugs.python.org/issue?@action=redirect&bpo=23890

   (162) https://bugs.python.org/issue?@action=redirect&bpo=29901

   (163) https://bugs.python.org/issue?@action=redirect&bpo=25803

   (164) https://bugs.python.org/issue?@action=redirect&bpo=29861

   (165) https://bugs.python.org/issue?@action=redirect&bpo=19930

   (166) https://bugs.python.org/issue?@action=redirect&bpo=29884

   (167) https://bugs.python.org/issue?@action=redirect&bpo=25455

   (168) https://bugs.python.org/issue?@action=redirect&bpo=29800

   (169) https://bugs.python.org/issue?@action=redirect&bpo=8256

   (170) https://bugs.python.org/issue?@action=redirect&bpo=28692

   (171) https://bugs.python.org/issue?@action=redirect&bpo=26121

   (172) https://bugs.python.org/issue?@action=redirect&bpo=29619

   (173) https://bugs.python.org/issue?@action=redirect&bpo=28298

   (174) https://bugs.python.org/issue?@action=redirect&bpo=29645

   (175) https://bugs.python.org/issue?@action=redirect&bpo=28231

   (176) https://bugs.python.org/issue?@action=redirect&bpo=26915

   (177) https://bugs.python.org/issue?@action=redirect&bpo=28682

   (178) https://bugs.python.org/issue?@action=redirect&bpo=29728

   (179) https://bugs.python.org/issue?@action=redirect&bpo=29623

   (180) https://bugs.python.org/issue?@action=redirect&bpo=9303

   (181) https://bugs.python.org/issue?@action=redirect&bpo=28963

   (182) https://bugs.python.org/issue?@action=redirect&bpo=29704

   (183) https://bugs.python.org/issue?@action=redirect&bpo=29271

   (184) https://bugs.python.org/issue?@action=redirect&bpo=29703

   (185) https://bugs.python.org/issue?@action=redirect&bpo=29615

   (186) https://bugs.python.org/issue?@action=redirect&bpo=7769

   (187) https://bugs.python.org/issue?@action=redirect&bpo=29376

   (188) https://bugs.python.org/issue?@action=redirect&bpo=28624

   (189) https://bugs.python.org/issue?@action=redirect&bpo=28518

   (190) https://bugs.python.org/issue?@action=redirect&bpo=29742

   (191) https://bugs.python.org/issue?@action=redirect&bpo=16285

   (192) https://bugs.python.org/issue?@action=redirect&bpo=29532

   (193) https://bugs.python.org/issue?@action=redirect&bpo=29110

   (194) https://bugs.python.org/issue?@action=redirect&bpo=22807

   (195) https://bugs.python.org/issue?@action=redirect&bpo=29576

   (196) https://bugs.python.org/issue?@action=redirect&bpo=29534

   (197) https://bugs.python.org/issue?@action=redirect&bpo=10379

   (198) https://bugs.python.org/issue?@action=redirect&bpo=29851

   (199) https://bugs.python.org/issue?@action=redirect&bpo=28556

   (200) https://bugs.python.org/issue?@action=redirect&bpo=29100

   (201) https://bugs.python.org/issue?@action=redirect&bpo=29416

   (202) https://bugs.python.org/issue?@action=redirect&bpo=29444

   (203) https://bugs.python.org/issue?@action=redirect&bpo=29377

   (204) https://bugs.python.org/issue?@action=redirect&bpo=29218

   (205) https://bugs.python.org/issue?@action=redirect&bpo=29368

   (206) https://bugs.python.org/issue?@action=redirect&bpo=29338

   (207) https://bugs.python.org/issue?@action=redirect&bpo=29335

   (208) https://bugs.python.org/issue?@action=redirect&bpo=29290

   (209) https://bugs.python.org/issue?@action=redirect&bpo=28735

   (210) https://bugs.python.org/issue?@action=redirect&bpo=29197

   (211) https://bugs.python.org/issue?@action=redirect&bpo=29210

   (212) https://bugs.python.org/issue?@action=redirect&bpo=29219

   (213) https://bugs.python.org/issue?@action=redirect&bpo=29192

   (214) https://bugs.python.org/issue?@action=redirect&bpo=29193

   (215) https://bugs.python.org/issue?@action=redirect&bpo=29195

   (216) https://bugs.python.org/issue?@action=redirect&bpo=28969

   (217) https://bugs.python.org/issue?@action=redirect&bpo=20804

   (218) https://bugs.python.org/issue?@action=redirect&bpo=29142

   (219) https://bugs.python.org/issue?@action=redirect&bpo=28961

   (220) https://bugs.python.org/issue?@action=redirect&bpo=15812

   (221) https://bugs.python.org/issue?@action=redirect&bpo=28985

   (222) https://bugs.python.org/issue?@action=redirect&bpo=29079

   (223) https://bugs.python.org/issue?@action=redirect&bpo=13051

   (224) https://bugs.python.org/issue?@action=redirect&bpo=9770

   (225) https://bugs.python.org/issue?@action=redirect&bpo=28427

   (226) https://bugs.python.org/issue?@action=redirect&bpo=28923

   (227) https://bugs.python.org/issue?@action=redirect&bpo=28871

   (228) https://bugs.python.org/issue?@action=redirect&bpo=19542

   (229) https://bugs.python.org/issue?@action=redirect&bpo=20191

   (230) https://bugs.python.org/issue?@action=redirect&bpo=16255

   (231) https://bugs.python.org/issue?@action=redirect&bpo=28779

   (232) https://bugs.python.org/issue?@action=redirect&bpo=26937

   (233) https://bugs.python.org/issue?@action=redirect&bpo=28847

   (234) https://bugs.python.org/issue?@action=redirect&bpo=27030

   (235) https://bugs.python.org/issue?@action=redirect&bpo=28835

   (236) https://bugs.python.org/issue?@action=redirect&bpo=27172

   (237) https://bugs.python.org/issue?@action=redirect&bpo=28740

   (238) https://bugs.python.org/issue?@action=redirect&bpo=26273

   (239) https://bugs.python.org/issue?@action=redirect&bpo=28752

   (240) https://bugs.python.org/issue?@action=redirect&bpo=28727

   (241) https://bugs.python.org/issue?@action=redirect&bpo=18383

   (242) https://bugs.python.org/issue?@action=redirect&bpo=20572

   (243) https://bugs.python.org/issue?@action=redirect&bpo=25659

   (244) https://bugs.python.org/issue?@action=redirect&bpo=28548

   (245) https://bugs.python.org/issue?@action=redirect&bpo=19717

   (246) https://bugs.python.org/issue?@action=redirect&bpo=28563

   (247) https://bugs.python.org/issue?@action=redirect&bpo=28387

   (248) https://bugs.python.org/issue?@action=redirect&bpo=27517

   (249) https://bugs.python.org/issue?@action=redirect&bpo=28549

   (250) https://bugs.python.org/issue?@action=redirect&bpo=28449

   (251) https://bugs.python.org/issue?@action=redirect&bpo=23262

   (252) https://bugs.python.org/issue?@action=redirect&bpo=24241

   (253) https://bugs.python.org/issue?@action=redirect&bpo=27939

   (254) https://bugs.python.org/issue?@action=redirect&bpo=28255

   (255) https://bugs.python.org/issue?@action=redirect&bpo=28255

   (256) https://bugs.python.org/issue?@action=redirect&bpo=20491

   (257) https://bugs.python.org/issue?@action=redirect&bpo=28353

   (258) https://bugs.python.org/issue?@action=redirect&bpo=28430

   (259) https://bugs.python.org/issue?@action=redirect&bpo=27025

   (260) https://bugs.python.org/issue?@action=redirect&bpo=25464

   (261) https://bugs.python.org/issue?@action=redirect&bpo=28488

   (262) https://bugs.python.org/issue?@action=redirect&bpo=25953

   (263) https://bugs.python.org/issue?@action=redirect&bpo=28469

   (264) https://bugs.python.org/issue?@action=redirect&bpo=28115

   (265) https://bugs.python.org/issue?@action=redirect&bpo=18219

   (266) https://bugs.python.org/issue?@action=redirect&bpo=28448

   (267) https://bugs.python.org/issue?@action=redirect&bpo=23214

   (268) https://bugs.python.org/issue?@action=redirect&bpo=28480

   (269) https://bugs.python.org/issue?@action=redirect&bpo=28240

   (270) https://bugs.python.org/issue?@action=redirect&bpo=28240

   (271) https://bugs.python.org/issue?@action=redirect&bpo=28240

   (272) https://github.com/pypa/setuptools/issues/100

   (273) https://bugs.python.org/issue?@action=redirect&bpo=24452

   (274) https://bugs.python.org/issue?@action=redirect&bpo=20766

   (275) https://bugs.python.org/issue?@action=redirect&bpo=27998

   (276) https://bugs.python.org/issue?@action=redirect&bpo=28317

   (277) https://bugs.python.org/issue?@action=redirect&bpo=28380

   (278) https://bugs.python.org/issue?@action=redirect&bpo=28229

   (279) https://bugs.python.org/issue?@action=redirect&bpo=28321

   (280) https://bugs.python.org/issue?@action=redirect&bpo=28225

   (281) https://bugs.python.org/issue?@action=redirect&bpo=28227

   (282) https://bugs.python.org/issue?@action=redirect&bpo=28332

   (283) https://bugs.python.org/issue?@action=redirect&bpo=27358

   (284) https://bugs.python.org/issue?@action=redirect&bpo=28257

   (285) https://bugs.python.org/issue?@action=redirect&bpo=28322

   (286) https://bugs.python.org/issue?@action=redirect&bpo=28228

   (287) https://bugs.python.org/issue?@action=redirect&bpo=28226

   (288) https://bugs.python.org/issue?@action=redirect&bpo=28314

   (289) https://bugs.python.org/issue?@action=redirect&bpo=28148

   (290) https://bugs.python.org/issue?@action=redirect&bpo=28253

   (291) https://bugs.python.org/issue?@action=redirect&bpo=28275

   (292) https://bugs.python.org/issue?@action=redirect&bpo=27897

   (293) https://bugs.python.org/issue?@action=redirect&bpo=18844

   (294) https://bugs.python.org/issue?@action=redirect&bpo=18893

   (295) https://bugs.python.org/issue?@action=redirect&bpo=27611

   (296) https://bugs.python.org/issue?@action=redirect&bpo=27348

   (297) https://bugs.python.org/issue?@action=redirect&bpo=25651

   (298) https://bugs.python.org/issue?@action=redirect&bpo=27778

   (299) https://bugs.python.org/issue?@action=redirect&bpo=28200

   (300) https://bugs.python.org/issue?@action=redirect&bpo=25400

   (301) https://bugs.python.org/issue?@action=redirect&bpo=27932

   (302) https://bugs.python.org/issue?@action=redirect&bpo=28075

   (303) https://bugs.python.org/issue?@action=redirect&bpo=22493

   (304) https://bugs.python.org/issue?@action=redirect&bpo=25270

   (305) https://bugs.python.org/issue?@action=redirect&bpo=28181

   (306) https://bugs.python.org/issue?@action=redirect&bpo=25895

   (307) https://bugs.python.org/issue?@action=redirect&bpo=28114

   (308) https://bugs.python.org/issue?@action=redirect&bpo=27599

   (309) https://bugs.python.org/issue?@action=redirect&bpo=27906

   (310) https://bugs.python.org/issue?@action=redirect&bpo=28174

   (311) https://bugs.python.org/issue?@action=redirect&bpo=26654

   (312) https://bugs.python.org/issue?@action=redirect&bpo=26909

   (313) https://bugs.python.org/issue?@action=redirect&bpo=28176

   (314) https://bugs.python.org/issue?@action=redirect&bpo=27759

   (315) https://bugs.python.org/issue?@action=redirect&bpo=28325

   (316) https://bugs.python.org/issue?@action=redirect&bpo=28368

   (317) https://bugs.python.org/issue?@action=redirect&bpo=28369

   (318) https://bugs.python.org/issue?@action=redirect&bpo=28370

   (319) https://bugs.python.org/issue?@action=redirect&bpo=28371

   (320) https://bugs.python.org/issue?@action=redirect&bpo=28372

   (321) https://bugs.python.org/issue?@action=redirect&bpo=28399

   (322) https://bugs.python.org/issue?@action=redirect&bpo=27972

   (323) https://bugs.python.org/issue?@action=redirect&bpo=24142

   (324) https://bugs.python.org/issue?@action=redirect&bpo=29581

   (325) https://bugs.python.org/issue?@action=redirect&bpo=25532

   (326) https://bugs.python.org/issue?@action=redirect&bpo=30177


File: python.info,  Node: Documentation<53>,  Next: Tests<53>,  Prev: Library<59>,  Up: Python 3 7 0 alpha 1

1.23.60.4 Documentation
.......................

   - bpo-31294(1): Fix incomplete code snippet in the
     ZeroMQSocketListener and ZeroMQSocketHandler examples and adapt
     them to Python 3.

   - bpo-21649(2): Add RFC 7525 and Mozilla server side TLS links to SSL
     documentation.

   - bpo-31128(3): Allow the pydoc server to bind to arbitrary
     hostnames.

   - bpo-30803(4): Clarify doc on truth value testing.  Original patch
     by Peter Thomassen.

   - bpo-30176(5): Add missing attribute related constants in curses
     documentation.

   - bpo-30052(6): the link targets for *note bytes(): 1a5. and *note
     bytearray(): 4e3. are now their respective type definitions, rather
     than the corresponding builtin function entries.  Use *note bytes:
     19bf. and *note bytearray: 19c0. to reference the latter.  In order
     to ensure this and future cross-reference updates are applied
     automatically, the daily documentation builds now disable the
     default output caching features in Sphinx.

   - bpo-26985(7): Add missing info of code object in inspect
     documentation.

   - bpo-19824(8): Improve the documentation for, and links to, template
     strings by emphasizing their utility for internationalization, and
     by clarifying some usage constraints.  (See also: bpo-20314(9),
     bpo-12518(10))

   - bpo-28929(11): Link the documentation to its source file on GitHub.

   - bpo-25008(12): Document smtpd.py as effectively deprecated and add
     a pointer to aiosmtpd, a third-party asyncio-based replacement.

   - bpo-26355(13): Add canonical header link on each page to
     corresponding major version of the documentation.  Patch by
     Matthias Bussonnier.

   - bpo-29349(14): Fix Python 2 syntax in code for building the
     documentation.

   - bpo-23722(15): The data model reference and the porting section in
     the 3.6 What's New guide now cover the additional ‘__classcell__’
     handling needed for custom metaclasses to fully support PEP 487(16)
     and zero-argument ‘super()’.

   - bpo-28513(17): Documented command-line interface of zipfile.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31294

   (2) https://bugs.python.org/issue?@action=redirect&bpo=21649

   (3) https://bugs.python.org/issue?@action=redirect&bpo=31128

   (4) https://bugs.python.org/issue?@action=redirect&bpo=30803

   (5) https://bugs.python.org/issue?@action=redirect&bpo=30176

   (6) https://bugs.python.org/issue?@action=redirect&bpo=30052

   (7) https://bugs.python.org/issue?@action=redirect&bpo=26985

   (8) https://bugs.python.org/issue?@action=redirect&bpo=19824

   (9) https://bugs.python.org/issue?@action=redirect&bpo=20314

   (10) https://bugs.python.org/issue?@action=redirect&bpo=12518

   (11) https://bugs.python.org/issue?@action=redirect&bpo=28929

   (12) https://bugs.python.org/issue?@action=redirect&bpo=25008

   (13) https://bugs.python.org/issue?@action=redirect&bpo=26355

   (14) https://bugs.python.org/issue?@action=redirect&bpo=29349

   (15) https://bugs.python.org/issue?@action=redirect&bpo=23722

   (16) https://peps.python.org/pep-0487/

   (17) https://bugs.python.org/issue?@action=redirect&bpo=28513


File: python.info,  Node: Tests<53>,  Next: Build<56>,  Prev: Documentation<53>,  Up: Python 3 7 0 alpha 1

1.23.60.5 Tests
...............

   - bpo-29639(1): test.support.HOST is now "localhost", a new HOSTv4
     constant has been added for your ‘127.0.0.1’ needs, similar to the
     existing HOSTv6 constant.

   - bpo-31320(2): Silence traceback in test_ssl

   - bpo-31346(3): Prefer PROTOCOL_TLS_CLIENT and PROTOCOL_TLS_SERVER
     protocols for SSLContext.

   - bpo-25674(4): Remove sha256.tbs-internet.com ssl test

   - bpo-30715(5): Address ALPN callback changes for OpenSSL 1.1.0f.
     The latest version behaves like OpenSSL 1.0.2 and no longer aborts
     handshake.

   - bpo-30822(6): regrtest: Exclude tzdata from regrtest -all.  When
     running the test suite using -use=all / -u all, exclude tzdata
     since it makes test_datetime too slow (15-20 min on some buildbots)
     which then times out on some buildbots.  Fix also regrtest command
     line parser to allow passing -u extralargefile to run
     test_zipfile64.

   - bpo-30695(7): Add the ‘set_nomemory(start, stop)’ and
     ‘remove_mem_hooks()’ functions to the ‘_testcapi’ module.

   - bpo-30357(8): test_thread: setUp() now uses
     support.threading_setup() and support.threading_cleanup() to wait
     until threads complete to avoid random side effects on following
     tests.  Initial patch written by Grzegorz Grzywacz.

   - bpo-30197(9): Enhanced functions swap_attr() and swap_item() in the
     test.support module.  They now work when delete replaced attribute
     or item inside the with statement.  The old value of the attribute
     or item (or None if it doesn't exist) now will be assigned to the
     target of the "as" clause, if there is one.

   - bpo-24932(10): Use proper command line parsing in _testembed

   - bpo-28950(11): Disallow -j0 to be combined with -T/-l in regrtest
     command line arguments.

   - bpo-28683(12): Fix the tests that bind() a unix socket and raise
     PermissionError on Android for a non-root user.

   - bpo-26936(13): Fix the test_socket failures on Android -
     getservbyname(), getservbyport() and getaddrinfo() are broken on
     some Android API levels.

   - bpo-28666(14): Now test.support.rmtree is able to remove unwritable
     or unreadable directories.

   - bpo-23839(15): Various caches now are cleared before running every
     test file.

   - bpo-26944(16): Fix test_posix for Android where 'id -G' is entirely
     wrong or missing the effective gid.

   - bpo-28409(17): regrtest: fix the parser of command line arguments.

   - bpo-28217(18): Adds _testconsole module to test console input.

   - bpo-26939(19): Add the support.setswitchinterval() function to fix
     test_functools hanging on the Android armv7 qemu emulator.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29639

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31320

   (3) https://bugs.python.org/issue?@action=redirect&bpo=31346

   (4) https://bugs.python.org/issue?@action=redirect&bpo=25674

   (5) https://bugs.python.org/issue?@action=redirect&bpo=30715

   (6) https://bugs.python.org/issue?@action=redirect&bpo=30822

   (7) https://bugs.python.org/issue?@action=redirect&bpo=30695

   (8) https://bugs.python.org/issue?@action=redirect&bpo=30357

   (9) https://bugs.python.org/issue?@action=redirect&bpo=30197

   (10) https://bugs.python.org/issue?@action=redirect&bpo=24932

   (11) https://bugs.python.org/issue?@action=redirect&bpo=28950

   (12) https://bugs.python.org/issue?@action=redirect&bpo=28683

   (13) https://bugs.python.org/issue?@action=redirect&bpo=26936

   (14) https://bugs.python.org/issue?@action=redirect&bpo=28666

   (15) https://bugs.python.org/issue?@action=redirect&bpo=23839

   (16) https://bugs.python.org/issue?@action=redirect&bpo=26944

   (17) https://bugs.python.org/issue?@action=redirect&bpo=28409

   (18) https://bugs.python.org/issue?@action=redirect&bpo=28217

   (19) https://bugs.python.org/issue?@action=redirect&bpo=26939


File: python.info,  Node: Build<56>,  Next: Windows<51>,  Prev: Tests<53>,  Up: Python 3 7 0 alpha 1

1.23.60.6 Build
...............

   - bpo-31354(1): Allow ‘--with-lto’ to be used on all builds, not just
     ‘make profile-opt’.

   - bpo-31370(2): Remove support for building -without-threads.  This
     option is not really useful anymore in the 21st century.  Removing
     lots of conditional paths allows us to simplify the code base,
     including in difficult to maintain low-level internal code.

   - bpo-31341(3): Per PEP 11(4), support for the IRIX operating system
     was removed.

   - bpo-30854(5): Fix compile error when compiling -without-threads.
     Patch by Masayuki Yamamoto.

   - bpo-30687(6): Locate msbuild.exe on Windows when building rather
     than vcvarsall.bat

   - bpo-20210(7): Support the 'disabled' marker in Setup files.
     Extension modules listed after this marker are not built at all,
     neither by the Makefile nor by setup.py.

   - bpo-29941(8): Add ‘--with-assertions’ configure flag to explicitly
     enable C ‘assert()’ checks.  Defaults to off.  ‘--with-pydebug’
     implies ‘--with-assertions’.

   - bpo-28787(9): Fix out-of-tree builds of Python when configured with
     ‘--with--dtrace’.

   - bpo-29243(10): Prevent unnecessary rebuilding of Python during
     ‘make test’, ‘make install’ and some other make targets when
     configured with ‘--enable-optimizations’.

   - bpo-23404(11): Don't regenerate generated files based on file
     modification time anymore: the action is now explicit.  Replace
     ‘make touch’ with ‘make regen-all’.

   - bpo-29643(12): Fix ‘--enable-optimization’ didn't work.

   - bpo-27593(13): sys.version and the platform module python_build(),
     python_branch(), and python_revision() functions now use git
     information rather than hg when building from a repo.

   - bpo-29572(14): Update Windows build and OS X installers to use
     OpenSSL 1.0.2k.

   - bpo-27659(15): Prohibit implicit C function declarations: use
     ‘-Werror=implicit-function-declaration’ when possible (GCC and
     Clang, but it depends on the compiler version).  Patch written by
     Chi Hsuan Yen.

   - bpo-29384(16): Remove old Be OS helper scripts.

   - bpo-26851(17): Set Android compilation and link flags.

   - bpo-28768(18): Fix implicit declaration of function _setmode.
     Patch by Masayuki Yamamoto

   - bpo-29080(19): Removes hard dependency on hg.exe from
     PCBuild/build.bat

   - bpo-23903(20): Added missed names to PC/python3.def.

   - bpo-28762(21): lockf() is available on Android API level 24, but
     the F_LOCK macro is not defined in android-ndk-r13.

   - bpo-28538(22): Fix the compilation error that occurs because
     if_nameindex() is available on Android API level 24, but the
     if_nameindex structure is not defined.

   - bpo-20211(23): Do not add the directory for installing C header
     files and the directory for installing object code libraries to the
     cross compilation search paths.  Original patch by Thomas
     Petazzoni.

   - bpo-28849(24): Do not define sys.implementation._multiarch on
     Android.

   - bpo-10656(25): Fix out-of-tree building on AIX. Patch by Tristan
     Carel and Michael Haubenwallner.

   - bpo-26359(26): Rename -with-optimiations to -enable-optimizations.

   - bpo-28444(27): Fix missing extensions modules when cross compiling.

   - bpo-28208(28): Update Windows build and OS X installers to use
     SQLite 3.14.2.

   - bpo-28248(29): Update Windows build and OS X installers to use
     OpenSSL 1.0.2j.

   - bpo-21124(30): Fix building the _struct module on Cygwin by passing
     ‘NULL’ instead of ‘&PyType_Type’ to PyVarObject_HEAD_INIT. Patch by
     Masayuki Yamamoto.

   - bpo-13756(31): Fix building extensions modules on Cygwin.  Patch by
     Roumen Petrov, based on original patch by Jason Tishler.

   - bpo-21085(32): Add configure check for siginfo_t.si_band, which
     Cygwin does not provide.  Patch by Masayuki Yamamoto with review
     and rebase by Erik Bray.

   - bpo-28258(33): Fixed build with Estonian locale (python-config and
     distclean targets in Makefile).  Patch by Arfrever Frehtes
     Taifersar Arahesis.

   - bpo-26661(34): setup.py now detects system libffi with multiarch
     wrapper.

   - bpo-27979(35): A full copy of libffi is no longer bundled for use
     when building _ctypes on non-OSX UNIX platforms.  An installed copy
     of libffi is now required when building _ctypes on such platforms.

   - bpo-15819(36): Remove redundant include search directory option for
     building outside the source tree.

   - bpo-28676(37): Prevent missing 'getentropy' declaration warning on
     macOS. Patch by Gareth Rees.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31354

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31370

   (3) https://bugs.python.org/issue?@action=redirect&bpo=31341

   (4) https://peps.python.org/pep-0011/

   (5) https://bugs.python.org/issue?@action=redirect&bpo=30854

   (6) https://bugs.python.org/issue?@action=redirect&bpo=30687

   (7) https://bugs.python.org/issue?@action=redirect&bpo=20210

   (8) https://bugs.python.org/issue?@action=redirect&bpo=29941

   (9) https://bugs.python.org/issue?@action=redirect&bpo=28787

   (10) https://bugs.python.org/issue?@action=redirect&bpo=29243

   (11) https://bugs.python.org/issue?@action=redirect&bpo=23404

   (12) https://bugs.python.org/issue?@action=redirect&bpo=29643

   (13) https://bugs.python.org/issue?@action=redirect&bpo=27593

   (14) https://bugs.python.org/issue?@action=redirect&bpo=29572

   (15) https://bugs.python.org/issue?@action=redirect&bpo=27659

   (16) https://bugs.python.org/issue?@action=redirect&bpo=29384

   (17) https://bugs.python.org/issue?@action=redirect&bpo=26851

   (18) https://bugs.python.org/issue?@action=redirect&bpo=28768

   (19) https://bugs.python.org/issue?@action=redirect&bpo=29080

   (20) https://bugs.python.org/issue?@action=redirect&bpo=23903

   (21) https://bugs.python.org/issue?@action=redirect&bpo=28762

   (22) https://bugs.python.org/issue?@action=redirect&bpo=28538

   (23) https://bugs.python.org/issue?@action=redirect&bpo=20211

   (24) https://bugs.python.org/issue?@action=redirect&bpo=28849

   (25) https://bugs.python.org/issue?@action=redirect&bpo=10656

   (26) https://bugs.python.org/issue?@action=redirect&bpo=26359

   (27) https://bugs.python.org/issue?@action=redirect&bpo=28444

   (28) https://bugs.python.org/issue?@action=redirect&bpo=28208

   (29) https://bugs.python.org/issue?@action=redirect&bpo=28248

   (30) https://bugs.python.org/issue?@action=redirect&bpo=21124

   (31) https://bugs.python.org/issue?@action=redirect&bpo=13756

   (32) https://bugs.python.org/issue?@action=redirect&bpo=21085

   (33) https://bugs.python.org/issue?@action=redirect&bpo=28258

   (34) https://bugs.python.org/issue?@action=redirect&bpo=26661

   (35) https://bugs.python.org/issue?@action=redirect&bpo=27979

   (36) https://bugs.python.org/issue?@action=redirect&bpo=15819

   (37) https://bugs.python.org/issue?@action=redirect&bpo=28676


File: python.info,  Node: Windows<51>,  Next: IDLE<43>,  Prev: Build<56>,  Up: Python 3 7 0 alpha 1

1.23.60.7 Windows
.................

   - bpo-31392(1): Update Windows build to use OpenSSL 1.1.0f

   - bpo-30389(2): Adds detection of Visual Studio 2017 to distutils on
     Windows.

   - bpo-31358(3): zlib is no longer bundled in the CPython source,
     instead it is downloaded on demand just like bz2, lzma, OpenSSL,
     Tcl/Tk, and SQLite.

   - bpo-31340(4): Change to building with MSVC v141 (included with
     Visual Studio 2017)

   - bpo-30581(5): os.cpu_count() now returns the correct number of
     processors on Windows when the number of logical processors is
     greater than 64.

   - bpo-30916(6): Pre-build OpenSSL, Tcl and Tk and include the
     binaries in the build.

   - bpo-30731(7): Add a missing xmlns to python.manifest so that it
     matches the schema.

   - bpo-30291(8): Allow requiring 64-bit interpreters from py.exe using
     -64 suffix.  Contributed by Steve (Gadget) Barnes.

   - bpo-30362(9): Adds list options (-0, -0p) to py.exe launcher.
     Contributed by Steve Barnes.

   - bpo-23451(10): Fix socket deprecation warnings in socketmodule.c.
     Patch by Segev Finer.

   - bpo-30450(11): The build process on Windows no longer depends on
     Subversion, instead pulling external code from GitHub via a Python
     script.  If Python 3.6 is not found on the system (via ‘py -3.6’),
     NuGet is used to download a copy of 32-bit Python.

   - bpo-29579(12): Removes readme.txt from the installer.

   - bpo-25778(13): winreg does not truncate string correctly (Patch by
     Eryk Sun)

   - bpo-28896(14): Deprecate WindowsRegistryFinder and disable it by
     default

   - bpo-28522(15): Fixes mishandled buffer reallocation in getpathp.c

   - bpo-28402(16): Adds signed catalog files for stdlib on Windows.

   - bpo-28333(17): Enables Unicode for ps1/ps2 and input() prompts.
     (Patch by Eryk Sun)

   - bpo-28251(18): Improvements to help manuals on Windows.

   - bpo-28110(19): launcher.msi has different product codes between
     32-bit and 64-bit

   - bpo-28161(20): Opening CON for write access fails

   - bpo-28162(21): WindowsConsoleIO readall() fails if first line
     starts with Ctrl+Z

   - bpo-28163(22): WindowsConsoleIO fileno() passes wrong flags to
     _open_osfhandle

   - bpo-28164(23): _PyIO_get_console_type fails for various paths

   - bpo-28137(24): Renames Windows path file to ._pth

   - bpo-28138(25): Windows ._pth file should allow import site

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31392

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30389

   (3) https://bugs.python.org/issue?@action=redirect&bpo=31358

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31340

   (5) https://bugs.python.org/issue?@action=redirect&bpo=30581

   (6) https://bugs.python.org/issue?@action=redirect&bpo=30916

   (7) https://bugs.python.org/issue?@action=redirect&bpo=30731

   (8) https://bugs.python.org/issue?@action=redirect&bpo=30291

   (9) https://bugs.python.org/issue?@action=redirect&bpo=30362

   (10) https://bugs.python.org/issue?@action=redirect&bpo=23451

   (11) https://bugs.python.org/issue?@action=redirect&bpo=30450

   (12) https://bugs.python.org/issue?@action=redirect&bpo=29579

   (13) https://bugs.python.org/issue?@action=redirect&bpo=25778

   (14) https://bugs.python.org/issue?@action=redirect&bpo=28896

   (15) https://bugs.python.org/issue?@action=redirect&bpo=28522

   (16) https://bugs.python.org/issue?@action=redirect&bpo=28402

   (17) https://bugs.python.org/issue?@action=redirect&bpo=28333

   (18) https://bugs.python.org/issue?@action=redirect&bpo=28251

   (19) https://bugs.python.org/issue?@action=redirect&bpo=28110

   (20) https://bugs.python.org/issue?@action=redirect&bpo=28161

   (21) https://bugs.python.org/issue?@action=redirect&bpo=28162

   (22) https://bugs.python.org/issue?@action=redirect&bpo=28163

   (23) https://bugs.python.org/issue?@action=redirect&bpo=28164

   (24) https://bugs.python.org/issue?@action=redirect&bpo=28137

   (25) https://bugs.python.org/issue?@action=redirect&bpo=28138


File: python.info,  Node: IDLE<43>,  Next: Tools/Demos<29>,  Prev: Windows<51>,  Up: Python 3 7 0 alpha 1

1.23.60.8 IDLE
..............

   - bpo-31493(1): IDLE code context - fix code update and font update
     timers.  Canceling timers prevents a warning message when test_idle
     completes.

   - bpo-31488(2): IDLE - Update non-key options in former extension
     classes.  When applying configdialog changes, call .reload for each
     feature class.  Change ParenMatch so updated options affect
     existing instances attached to existing editor windows.

   - bpo-31477(3): IDLE - Improve rstrip entry in doc.  Strip trailing
     whitespace strips more than blank spaces.  Multiline string
     literals are not skipped.

   - bpo-31480(4): IDLE - make tests pass with zzdummy extension
     disabled by default.

   - bpo-31421(5): Document how IDLE runs tkinter programs.  IDLE calls
     tcl/tk update in the background in order to make live interaction
     and experimentation with tkinter applications much easier.

   - bpo-31414(6): IDLE - fix tk entry box tests by deleting first.
     Adding to an int entry is not the same as deleting and inserting
     because int('') will fail.

   - bpo-31051(7): Rearrange IDLE configdialog GenPage into Window,
     Editor, and Help sections.

   - bpo-30617(8): IDLE - Add docstrings and tests for outwin subclass
     of editor.  Move some data and functions from the class to module
     level.  Patch by Cheryl Sabella.

   - bpo-31287(9): IDLE - Do not modify tkinter.message in
     test_configdialog.

   - bpo-27099(10): Convert IDLE's built-in 'extensions' to regular
     features.  About 10 IDLE features were implemented as supposedly
     optional extensions.  Their different behavior could be confusing
     or worse for users and not good for maintenance.  Hence the
     conversion.  The main difference for users is that user
     configurable key bindings for builtin features are now handled
     uniformly.  Now, editing a binding in a keyset only affects its
     value in the keyset.  All bindings are defined together in the
     system-specific default keysets in config-extensions.def.  All
     custom keysets are saved as a whole in config-extension.cfg.  All
     take effect as soon as one clicks Apply or Ok.  The affected events
     are '<<force-open-completions>>', '<<expand-word>>',
     '<<force-open-calltip>>', '<<flash-paren>>',
     '<<format-paragraph>>', '<<run-module>>', '<<check-module>>', and
     '<<zoom-height>>'.  Any (global) customizations made before 3.6.3
     will not affect their keyset-specific customization after 3.6.3.
     and vice versa.  Initial patch by Charles Wohlganger.

   - bpo-31206(11): IDLE: Factor HighPage(Frame) class from
     ConfigDialog.  Patch by Cheryl Sabella.

   - bpo-31001(12): Add tests for configdialog highlight tab.  Patch by
     Cheryl Sabella.

   - bpo-31205(13): IDLE: Factor KeysPage(Frame) class from
     ConfigDialog.  The slightly modified tests continue to pass.  Patch
     by Cheryl Sabella.

   - bpo-31130(14): IDLE - stop leaks in test_configdialog.  Initial
     patch by Victor Stinner.

   - bpo-31002(15): Add tests for configdialog keys tab.  Patch by
     Cheryl Sabella.

   - bpo-19903(16): IDLE: Calltips use ‘inspect.signature’ instead of
     ‘inspect.getfullargspec’.  This improves calltips for builtins
     converted to use Argument Clinic.  Patch by Louie Lu.

   - bpo-31083(17): IDLE - Add an outline of a TabPage class in
     configdialog.  Update existing classes to match outline.  Initial
     patch by Cheryl Sabella.

   - bpo-31050(18): Factor GenPage(Frame) class from ConfigDialog.  The
     slightly modified tests continue to pass.  Patch by Cheryl Sabella.

   - bpo-31004(19): IDLE - Factor FontPage(Frame) class from
     ConfigDialog.  Slightly modified tests continue to pass.  Fix
     General tests.  Patch mostly by Cheryl Sabella.

   - bpo-30781(20): IDLE - Use ttk widgets in ConfigDialog.  Patches by
     Terry Jan Reedy and Cheryl Sabella.

   - bpo-31060(21): IDLE - Finish rearranging methods of ConfigDialog
     Grouping methods pertaining to each tab and the buttons will aid
     writing tests and improving the tabs and will enable splitting the
     groups into classes.

   - bpo-30853(22): IDLE - Factor a VarTrace class out of ConfigDialog.
     Instance tracers manages pairs consisting of a tk variable and a
     callback function.  When tracing is turned on, setting the variable
     calls the function.  Test coverage for the new class is 100%.

   - bpo-31003(23): IDLE: Add more tests for General tab.

   - bpo-30993(24): IDLE - Improve configdialog font page and tests.  In
     configdialog: Document causal pathways in create_font_tab
     docstring.  Simplify some attribute names.  Move set_samples calls
     to var_changed_font (idea from Cheryl Sabella).  Move related
     functions to positions after the create widgets function.  In
     test_configdialog: Fix test_font_set so not order dependent.  Fix
     renamed test_indent_scale so it tests the widget.  Adjust tests for
     movement of set_samples call.  Add tests for load functions.  Put
     all font tests in one class and tab indent tests in another.
     Except for two lines, these tests completely cover the related
     functions.

   - bpo-30981(25): IDLE - Add more configdialog font page tests.

   - bpo-28523(26): IDLE: replace 'colour' with 'color' in configdialog.

   - bpo-30917(27): Add tests for idlelib.config.IdleConf.  Increase
     coverage from 46% to 96%.  Patch by Louie Lu.

   - bpo-30934(28): Document coverage details for idlelib tests.  Add
     section to idlelib/idle-test/README.txt.  Include check that
     branches are taken both ways.  Exclude IDLE-specific code that does
     not run during unit tests.

   - bpo-30913(29): IDLE: Document ConfigDialog tk Vars, methods, and
     widgets in docstrings This will facilitate improving the dialog and
     splitting up the class.  Original patch by Cheryl Sabella.

   - bpo-30899(30): IDLE: Add tests for ConfigParser subclasses in
     config.  Patch by Louie Lu.

   - bpo-30881(31): IDLE: Add docstrings to browser.py.  Patch by Cheryl
     Sabella.

   - bpo-30851(32): IDLE: Remove unused variables in configdialog.  One
     is a duplicate, one is set but cannot be altered by users.  Patch
     by Cheryl Sabella.

   - bpo-30870(33): IDLE: In Settings dialog, select font with Up, Down
     keys as well as mouse.  Initial patch by Louie Lu.

   - bpo-8231(34): IDLE: call config.IdleConf.GetUserCfgDir only once.

   - bpo-30779(35): IDLE: Factor ConfigChanges class from configdialog,
     put in config; test.  * In config, put dump test code in a
     function; run it and unittest in 'if __name__ == '__main__'.  * Add
     class config.ConfigChanges based on changes_class_v4.py on bpo
     issue.  * Add class test_config.ChangesTest, partly using
     configdialog_tests_v1.py.  * Revise configdialog to use
     ConfigChanges; see tracker msg297804.  * Revise test_configdialog
     to match configdialog changes.  * Remove configdialog functions
     unused or moved to ConfigChanges.  Cheryl Sabella contributed parts
     of the patch.

   - bpo-30777(36): IDLE: configdialog - Add docstrings and fix
     comments.  Patch by Cheryl Sabella.

   - bpo-30495(37): IDLE: Improve textview with docstrings, PEP8 names,
     and more tests.  Patch by Cheryl Sabella.

   - bpo-30723(38): IDLE: Make several improvements to parenmatch.  Add
     'parens' style to highlight both opener and closer.  Make 'default'
     style, which is not default, a synonym for 'opener'.  Make
     time-delay work the same with all styles.  Add help for config
     dialog extensions tab, including help for parenmatch.  Add new
     tests.  Original patch by Charles Wohlganger.

   - bpo-30674(39): IDLE: add docstrings to grep module.  Patch by
     Cheryl Sabella

   - bpo-21519(40): IDLE's basic custom key entry dialog now detects
     duplicates properly.  Original patch by Saimadhav Heblikar.

   - bpo-29910(41): IDLE no longer deletes a character after commenting
     out a region by a key shortcut.  Add ‘return 'break'’ for this and
     other potential conflicts between IDLE and default key bindings.

   - bpo-30728(42): Review and change idlelib.configdialog names.
     Lowercase method and attribute names.  Replace 'colour' with
     'color', expand overly cryptic names, delete unneeded underscores.
     Replace ‘import *’ with specific imports.  Patches by Cheryl
     Sabella.

   - bpo-6739(43): IDLE: Verify user-entered key sequences by trying to
     bind them with tk.  Add tests for all 3 validation functions.
     Original patch by G Polo.  Tests added by Cheryl Sabella.

   - bpo-15786(44): Fix several problems with IDLE's autocompletion box.
     The following should now work: clicking on selection box items;
     using the scrollbar; selecting an item by hitting Return.  Hangs on
     MacOSX should no longer happen.  Patch by Louie Lu.

   - bpo-25514(45): Add doc subsubsection about IDLE failure to start.
     Popup no-connection message directs users to this section.

   - bpo-30642(46): Fix reference leaks in IDLE tests.  Patches by Louie
     Lu and Terry Jan Reedy.

   - bpo-30495(47): Add docstrings for textview.py and use PEP8 names.
     Patches by Cheryl Sabella and Terry Jan Reedy.

   - bpo-30290(48): Help-about: use pep8 names and add tests.  Increase
     coverage to 100%.  Patches by Louie Lu, Cheryl Sabella, and Terry
     Jan Reedy.

   - bpo-30303(49): Add _utest option to textview; add new tests.
     Increase coverage to 100%.  Patches by Louie Lu and Terry Jan
     Reedy.

   - bpo-29071(50): IDLE colors f-string prefixes (but not invalid ur
     prefixes).

   - bpo-28572(51): Add 10% to coverage of IDLE's test_configdialog.
     Update and augment description of the configuration system.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31493

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31488

   (3) https://bugs.python.org/issue?@action=redirect&bpo=31477

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31480

   (5) https://bugs.python.org/issue?@action=redirect&bpo=31421

   (6) https://bugs.python.org/issue?@action=redirect&bpo=31414

   (7) https://bugs.python.org/issue?@action=redirect&bpo=31051

   (8) https://bugs.python.org/issue?@action=redirect&bpo=30617

   (9) https://bugs.python.org/issue?@action=redirect&bpo=31287

   (10) https://bugs.python.org/issue?@action=redirect&bpo=27099

   (11) https://bugs.python.org/issue?@action=redirect&bpo=31206

   (12) https://bugs.python.org/issue?@action=redirect&bpo=31001

   (13) https://bugs.python.org/issue?@action=redirect&bpo=31205

   (14) https://bugs.python.org/issue?@action=redirect&bpo=31130

   (15) https://bugs.python.org/issue?@action=redirect&bpo=31002

   (16) https://bugs.python.org/issue?@action=redirect&bpo=19903

   (17) https://bugs.python.org/issue?@action=redirect&bpo=31083

   (18) https://bugs.python.org/issue?@action=redirect&bpo=31050

   (19) https://bugs.python.org/issue?@action=redirect&bpo=31004

   (20) https://bugs.python.org/issue?@action=redirect&bpo=30781

   (21) https://bugs.python.org/issue?@action=redirect&bpo=31060

   (22) https://bugs.python.org/issue?@action=redirect&bpo=30853

   (23) https://bugs.python.org/issue?@action=redirect&bpo=31003

   (24) https://bugs.python.org/issue?@action=redirect&bpo=30993

   (25) https://bugs.python.org/issue?@action=redirect&bpo=30981

   (26) https://bugs.python.org/issue?@action=redirect&bpo=28523

   (27) https://bugs.python.org/issue?@action=redirect&bpo=30917

   (28) https://bugs.python.org/issue?@action=redirect&bpo=30934

   (29) https://bugs.python.org/issue?@action=redirect&bpo=30913

   (30) https://bugs.python.org/issue?@action=redirect&bpo=30899

   (31) https://bugs.python.org/issue?@action=redirect&bpo=30881

   (32) https://bugs.python.org/issue?@action=redirect&bpo=30851

   (33) https://bugs.python.org/issue?@action=redirect&bpo=30870

   (34) https://bugs.python.org/issue?@action=redirect&bpo=8231

   (35) https://bugs.python.org/issue?@action=redirect&bpo=30779

   (36) https://bugs.python.org/issue?@action=redirect&bpo=30777

   (37) https://bugs.python.org/issue?@action=redirect&bpo=30495

   (38) https://bugs.python.org/issue?@action=redirect&bpo=30723

   (39) https://bugs.python.org/issue?@action=redirect&bpo=30674

   (40) https://bugs.python.org/issue?@action=redirect&bpo=21519

   (41) https://bugs.python.org/issue?@action=redirect&bpo=29910

   (42) https://bugs.python.org/issue?@action=redirect&bpo=30728

   (43) https://bugs.python.org/issue?@action=redirect&bpo=6739

   (44) https://bugs.python.org/issue?@action=redirect&bpo=15786

   (45) https://bugs.python.org/issue?@action=redirect&bpo=25514

   (46) https://bugs.python.org/issue?@action=redirect&bpo=30642

   (47) https://bugs.python.org/issue?@action=redirect&bpo=30495

   (48) https://bugs.python.org/issue?@action=redirect&bpo=30290

   (49) https://bugs.python.org/issue?@action=redirect&bpo=30303

   (50) https://bugs.python.org/issue?@action=redirect&bpo=29071

   (51) https://bugs.python.org/issue?@action=redirect&bpo=28572


File: python.info,  Node: Tools/Demos<29>,  Next: C API<53>,  Prev: IDLE<43>,  Up: Python 3 7 0 alpha 1

1.23.60.9 Tools/Demos
.....................

   - bpo-30983(1): gdb integration commands (py-bt, etc.)  work on
     optimized shared builds now, too.  PEP 523(2) introduced
     _PyEval_EvalFrameDefault which inlines PyEval_EvalFrameEx on
     non-debug shared builds.  This broke the ability to use py-bt,
     py-up, and a few other Python-specific gdb integrations.  The
     problem is fixed by only looking for _PyEval_EvalFrameDefault
     frames in python-gdb.py.  Original patch by Bruno "Polaco"
     Penteado.

   - bpo-29748(3): Added the slice index converter in Argument Clinic.

   - bpo-24037(4): Argument Clinic now uses the converter
     ‘bool(accept={int})’ rather than ‘int’ for semantical booleans.
     This avoids repeating the default value for Python and C and will
     help in converting to ‘bool’ in future.

   - bpo-29367(5): python-gdb.py now supports also ‘method-wrapper’
     (‘wrapperobject’) objects.

   - bpo-28023(6): Fix python-gdb.py didn't support new dict
     implementation.

   - bpo-15369(7): The pybench and pystone microbenchmark have been
     removed from Tools.  Please use the new Python benchmark suite
     ‘https://github.com/python/pyperformance’ which is more reliable
     and includes a portable version of pybench working on Python 2 and
     Python 3.

   - bpo-28102(8): The zipfile module CLI now prints usage to stderr.
     Patch by Stephen J. Turnbull.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30983

   (2) https://peps.python.org/pep-0523/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=29748

   (4) https://bugs.python.org/issue?@action=redirect&bpo=24037

   (5) https://bugs.python.org/issue?@action=redirect&bpo=29367

   (6) https://bugs.python.org/issue?@action=redirect&bpo=28023

   (7) https://bugs.python.org/issue?@action=redirect&bpo=15369

   (8) https://bugs.python.org/issue?@action=redirect&bpo=28102


File: python.info,  Node: C API<53>,  Prev: Tools/Demos<29>,  Up: Python 3 7 0 alpha 1

1.23.60.10 C API
................

   - bpo-31338(1): Added the ‘Py_UNREACHABLE()’ macro for code paths
     which are never expected to be reached.  This and a few other
     useful macros are now documented in the C API manual.

   - bpo-30832(2): Remove own implementation for thread-local storage.
     CPython has provided the own implementation for thread-local
     storage (TLS) on Python/thread.c, it's used in the case which a
     platform has not supplied native TLS. However, currently all
     supported platforms (Windows and pthreads) have provided native TLS
     and defined the Py_HAVE_NATIVE_TLS macro with unconditional in any
     case.

   - bpo-30708(3): PyUnicode_AsWideCharString() now raises a ValueError
     if the second argument is NULL and the wchar_t* string contains
     null characters.

   - bpo-16500(4): Deprecate PyOS_AfterFork() and add PyOS_BeforeFork(),
     PyOS_AfterFork_Parent() and PyOS_AfterFork_Child().

   - bpo-6532(5): The type of results of PyThread_start_new_thread() and
     PyThread_get_thread_ident(), and the id parameter of
     PyThreadState_SetAsyncExc() changed from "long" to "unsigned long".

   - bpo-27867(6): Function PySlice_GetIndicesEx() is deprecated and
     replaced with a macro if Py_LIMITED_API is not set or set to the
     value between 0x03050400 and 0x03060000 (not including) or
     0x03060100 or higher.  Added functions PySlice_Unpack() and
     PySlice_AdjustIndices().

   - bpo-29083(7): Fixed the declaration of some public API functions.
     PyArg_VaParse() and PyArg_VaParseTupleAndKeywords() were not
     available in limited API. PyArg_ValidateKeywordArguments(),
     PyArg_UnpackTuple() and Py_BuildValue() were not available in
     limited API of version < 3.3 when PY_SSIZE_T_CLEAN is defined.

   - bpo-28769(8): The result of PyUnicode_AsUTF8AndSize() and
     PyUnicode_AsUTF8() is now of type ‘const char *’ rather of ‘char
     *’.

   - bpo-29058(9): All stable API extensions added after Python 3.2 are
     now available only when Py_LIMITED_API is set to the PY_VERSION_HEX
     value of the minimum Python version supporting this API.

   - bpo-28822(10): The index parameters 'start' and 'end' of
     PyUnicode_FindChar() are now adjusted to behave like
     ‘str[start:end]’.

   - bpo-28808(11): PyUnicode_CompareWithASCIIString() now never raises
     exceptions.

   - bpo-28761(12): The fields name and doc of structures PyMemberDef,
     PyGetSetDef, PyStructSequence_Field, PyStructSequence_Desc, and
     wrapperbase are now of type ‘const char *’ rather of ‘char *’.

   - bpo-28748(13): Private variable _Py_PackageContext is now of type
     ‘const char *’ rather of ‘char *’.

   - bpo-19569(14): Compiler warnings are now emitted if use most of
     deprecated functions.

   - bpo-28426(15): Deprecated undocumented functions
     PyUnicode_AsEncodedObject(), PyUnicode_AsDecodedObject(),
     PyUnicode_AsDecodedUnicode() and PyUnicode_AsEncodedUnicode().

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31338

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30832

   (3) https://bugs.python.org/issue?@action=redirect&bpo=30708

   (4) https://bugs.python.org/issue?@action=redirect&bpo=16500

   (5) https://bugs.python.org/issue?@action=redirect&bpo=6532

   (6) https://bugs.python.org/issue?@action=redirect&bpo=27867

   (7) https://bugs.python.org/issue?@action=redirect&bpo=29083

   (8) https://bugs.python.org/issue?@action=redirect&bpo=28769

   (9) https://bugs.python.org/issue?@action=redirect&bpo=29058

   (10) https://bugs.python.org/issue?@action=redirect&bpo=28822

   (11) https://bugs.python.org/issue?@action=redirect&bpo=28808

   (12) https://bugs.python.org/issue?@action=redirect&bpo=28761

   (13) https://bugs.python.org/issue?@action=redirect&bpo=28748

   (14) https://bugs.python.org/issue?@action=redirect&bpo=19569

   (15) https://bugs.python.org/issue?@action=redirect&bpo=28426


File: python.info,  Node: Python 3 6 6 final,  Next: Python 3 6 6 release candidate 1,  Prev: Python 3 7 0 alpha 1,  Up: Changelog（更動日誌）

1.23.61 Python 3.6.6 final
--------------------------

'Release date: 2018-06-27'

There were no new changes in version 3.6.6.


File: python.info,  Node: Python 3 6 6 release candidate 1,  Next: Python 3 6 5 final,  Prev: Python 3 6 6 final,  Up: Changelog（更動日誌）

1.23.62 Python 3.6.6 release candidate 1
----------------------------------------

'Release date: 2018-06-11'

* Menu:

* Core and Builtins: Core and Builtins<60>.
* Library: Library<60>.
* Documentation: Documentation<54>.
* Tests: Tests<54>.
* Build: Build<57>.
* Windows: Windows<52>.
* macOS: macOS<42>.
* IDLE: IDLE<44>.
* Tools/Demos: Tools/Demos<30>.
* C API: C API<54>.


File: python.info,  Node: Core and Builtins<60>,  Next: Library<60>,  Up: Python 3 6 6 release candidate 1

1.23.62.1 Core and Builtins
...........................

   - bpo-33786(1): Fix asynchronous generators to handle GeneratorExit
     in athrow() correctly

   - bpo-30654(2): Fixed reset of the SIGINT handler to SIG_DFL on
     interpreter shutdown even when there was a custom handler set
     previously.  Patch by Philipp Kerling.

   - bpo-33622(3): Fixed a leak when the garbage collector fails to add
     an object with the ‘__del__’ method or referenced by it into the
     *note gc.garbage: 1159. list.  *note PyGC_Collect(): 932. can now
     be called when an exception is set and preserves it.

   - bpo-31849(4): Fix signed/unsigned comparison warning in pyhash.c.

   - bpo-33391(5): Fix a leak in set_symmetric_difference().

   - bpo-28055(6): Fix unaligned accesses in siphash24().  Patch by Rolf
     Eike Beer.

   - bpo-33231(7): Fix potential memory leak in ‘normalizestring()’.

   - bpo-29922(8): Improved error messages in 'async with' when
     ‘__aenter__()’ or ‘__aexit__()’ return non-awaitable object.

   - bpo-33199(9): Fix ‘ma_version_tag’ in dict implementation is
     uninitialized when copying from key-sharing dict.

   - bpo-33041(10): Fixed jumping when the function contains an ‘async
     for’ loop.

   - bpo-32282(11): Fix an unnecessary ifdef in the include of
     VersionHelpers.h in socketmodule on Windows.

   - bpo-21983(12): Fix a crash in ‘ctypes.cast()’ in case the type
     argument is a ctypes structured data type.  Patch by Eryk Sun and
     Oren Milman.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33786

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30654

   (3) https://bugs.python.org/issue?@action=redirect&bpo=33622

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31849

   (5) https://bugs.python.org/issue?@action=redirect&bpo=33391

   (6) https://bugs.python.org/issue?@action=redirect&bpo=28055

   (7) https://bugs.python.org/issue?@action=redirect&bpo=33231

   (8) https://bugs.python.org/issue?@action=redirect&bpo=29922

   (9) https://bugs.python.org/issue?@action=redirect&bpo=33199

   (10) https://bugs.python.org/issue?@action=redirect&bpo=33041

   (11) https://bugs.python.org/issue?@action=redirect&bpo=32282

   (12) https://bugs.python.org/issue?@action=redirect&bpo=21983


File: python.info,  Node: Library<60>,  Next: Documentation<54>,  Prev: Core and Builtins<60>,  Up: Python 3 6 6 release candidate 1

1.23.62.2 Library
.................

   - bpo-30167(1): Prevent site.main() exception if PYTHONSTARTUP is
     set.  Patch by Steve Weber.

   - bpo-33812(2): Datetime instance d with non-None tzinfo, but with
     d.tzinfo.utcoffset(d) returning None is now treated as naive by the
     astimezone() method.

   - bpo-30805(3): Avoid race condition with debug logging

   - bpo-33767(4): The concatenation (‘+’) and repetition (‘*’) sequence
     operations now raise *note TypeError: 4dd. instead of *note
     SystemError: 51b. when performed on *note mmap.mmap: 1f0. objects.
     Patch by Zackery Spytz.

   - bpo-32684(5): Fix gather to propagate cancellation of itself even
     with return_exceptions.

   - bpo-33674(6): Fix a race condition in SSLProtocol.connection_made()
     of asyncio.sslproto: start immediately the handshake instead of
     using call_soon().  Previously, data_received() could be called
     before the handshake started, causing the handshake to hang or
     fail.

   - bpo-31647(7): Fixed bug where calling write_eof() on a
     _SelectorSocketTransport after it's already closed raises
     AttributeError.

   - bpo-33672(8): Fix Task.__repr__ crash with Cython's bogus
     coroutines

   - bpo-33469(9): Fix RuntimeError after closing loop that used
     run_in_executor

   - bpo-11874(10): Use a better regex when breaking usage into
     wrappable parts.  Avoids bogus assertion errors from custom metavar
     strings.

   - bpo-30877(11): Fixed a bug in the Python implementation of the JSON
     decoder that prevented the cache of parsed strings from clearing
     after finishing the decoding.  Based on patch by c-fos.

   - bpo-33548(12): tempfile._candidate_tempdir_list should consider
     common TEMP locations

   - bpo-33542(13): Prevent ‘uuid.get_node’ from using a DUID instead of
     a MAC on Windows.  Patch by Zvi Effron

   - bpo-26819(14): Fix race condition with
     ‘ReadTransport.resume_reading’ in Windows proactor event loop.

   - bpo-28556(15): Minor fixes in typing module: add annotations to
     ‘NamedTuple.__new__’, pass ‘*args’ and ‘**kwds’ in
     ‘Generic.__new__’.  Original PRs by Paulius Šarka and Chad
     Dombrova.

   - bpo-20087(16): Updated alias mapping with glibc 2.27 supported
     locales.

   - bpo-33422(17): Fix trailing quotation marks getting deleted when
     looking up byte/string literals on pydoc.  Patch by Andrés Delfino.

   - bpo-33197(18): Update error message when constructing invalid
     inspect.Parameters Patch by Donghee Na.

   - bpo-33383(19): Fixed crash in the get() method of the *note
     dbm.ndbm: 2c. database object when it is called with a single
     argument.

   - bpo-33329(20): Fix multiprocessing regression on newer glibcs

   - bpo-991266(21): Fix quoting of the ‘Comment’ attribute of *note
     http.cookies.SimpleCookie: 1949.

   - bpo-33131(22): Upgrade bundled version of pip to 10.0.1.

   - bpo-33308(23): Fixed a crash in the ‘parser’ module when converting
     an ST object to a tree of tuples or lists with ‘line_info=False’
     and ‘col_info=True’.

   - bpo-33263(24): Fix FD leak in ‘_SelectorSocketTransport’ Patch by
     Vlad Starostin.

   - bpo-33256(25): Fix display of ‘<module>’ call in the html produced
     by ‘cgitb.html()’.  Patch by Stéphane Blondon.

   - bpo-33203(26): ‘random.Random.choice()’ now raises ‘IndexError’ for
     empty sequences consistently even when called from subclasses
     without a ‘getrandbits()’ implementation.

   - bpo-33224(27): Update difflib.mdiff() for PEP 479(28).  Convert an
     uncaught StopIteration in a generator into a return-statement.

   - bpo-33209(29): End framing at the end of C implementation of *note
     pickle.Pickler.dump(): 194b.

   - bpo-32861(30): The urllib.robotparser's ‘__str__’ representation
     now includes wildcard entries and the "Crawl-delay" and
     "Request-rate" fields.  Patch by Michael Lazar.

   - bpo-33096(31): Allow ttk.Treeview.insert to insert iid that has a
     false boolean value.  Note iid=0 and iid=False would be same.
     Patch by Garvit Khatri.

   - bpo-33127(32): The ssl module now compiles with LibreSSL 2.7.1.

   - bpo-33021(33): Release the GIL during fstat() calls, avoiding hang
     of all threads when calling mmap.mmap(), os.urandom(), and
     random.seed().  Patch by Nir Soffer.

   - bpo-27683(34): Fix a regression in *note ipaddress: 74. that result
     of ‘hosts()’ is empty when the network is constructed by a tuple
     containing an integer mask and only 1 bit left for addresses.

   - bpo-32844(35): Fix wrong redirection of a low descriptor (0 or 1)
     to stderr in subprocess if another low descriptor is closed.

   - bpo-31908(36): Fix output of cover files for ‘trace’ module
     command-line tool.  Previously emitted cover files only when
     ‘--missing’ option was used.  Patch by Michael Selik.

   - bpo-31457(37): If nested log adapters are used, the inner
     ‘process()’ methods are no longer omitted.

   - bpo-16865(38): Support arrays >=2GiB in *note ctypes: 22.  Patch by
     Segev Finer.

   - bpo-31238(39): pydoc: the stop() method of the private ServerThread
     class now waits until DocServer.serve_until_quit() completes and
     then explicitly sets its docserver attribute to None to break a
     reference cycle.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30167

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33812

   (3) https://bugs.python.org/issue?@action=redirect&bpo=30805

   (4) https://bugs.python.org/issue?@action=redirect&bpo=33767

   (5) https://bugs.python.org/issue?@action=redirect&bpo=32684

   (6) https://bugs.python.org/issue?@action=redirect&bpo=33674

   (7) https://bugs.python.org/issue?@action=redirect&bpo=31647

   (8) https://bugs.python.org/issue?@action=redirect&bpo=33672

   (9) https://bugs.python.org/issue?@action=redirect&bpo=33469

   (10) https://bugs.python.org/issue?@action=redirect&bpo=11874

   (11) https://bugs.python.org/issue?@action=redirect&bpo=30877

   (12) https://bugs.python.org/issue?@action=redirect&bpo=33548

   (13) https://bugs.python.org/issue?@action=redirect&bpo=33542

   (14) https://bugs.python.org/issue?@action=redirect&bpo=26819

   (15) https://bugs.python.org/issue?@action=redirect&bpo=28556

   (16) https://bugs.python.org/issue?@action=redirect&bpo=20087

   (17) https://bugs.python.org/issue?@action=redirect&bpo=33422

   (18) https://bugs.python.org/issue?@action=redirect&bpo=33197

   (19) https://bugs.python.org/issue?@action=redirect&bpo=33383

   (20) https://bugs.python.org/issue?@action=redirect&bpo=33329

   (21) https://bugs.python.org/issue?@action=redirect&bpo=991266

   (22) https://bugs.python.org/issue?@action=redirect&bpo=33131

   (23) https://bugs.python.org/issue?@action=redirect&bpo=33308

   (24) https://bugs.python.org/issue?@action=redirect&bpo=33263

   (25) https://bugs.python.org/issue?@action=redirect&bpo=33256

   (26) https://bugs.python.org/issue?@action=redirect&bpo=33203

   (27) https://bugs.python.org/issue?@action=redirect&bpo=33224

   (28) https://peps.python.org/pep-0479/

   (29) https://bugs.python.org/issue?@action=redirect&bpo=33209

   (30) https://bugs.python.org/issue?@action=redirect&bpo=32861

   (31) https://bugs.python.org/issue?@action=redirect&bpo=33096

   (32) https://bugs.python.org/issue?@action=redirect&bpo=33127

   (33) https://bugs.python.org/issue?@action=redirect&bpo=33021

   (34) https://bugs.python.org/issue?@action=redirect&bpo=27683

   (35) https://bugs.python.org/issue?@action=redirect&bpo=32844

   (36) https://bugs.python.org/issue?@action=redirect&bpo=31908

   (37) https://bugs.python.org/issue?@action=redirect&bpo=31457

   (38) https://bugs.python.org/issue?@action=redirect&bpo=16865

   (39) https://bugs.python.org/issue?@action=redirect&bpo=31238


File: python.info,  Node: Documentation<54>,  Next: Tests<54>,  Prev: Library<60>,  Up: Python 3 6 6 release candidate 1

1.23.62.3 Documentation
.......................

   - bpo-33503(1): Fix broken pypi link

   - bpo-33421(2): Add missing documentation for
     ‘typing.AsyncContextManager’.

   - bpo-33378(3): Add Korean language switcher for
     ‘https://docs.python.org/3/’

   - bpo-33276(4): Clarify that the ‘__path__’ attribute on modules
     cannot be just any value.

   - bpo-33201(5): Modernize documentation for writing C extension
     types.

   - bpo-33195(6): Deprecate ‘Py_UNICODE’ usage in ‘c-api/arg’ document.
     ‘Py_UNICODE’ related APIs are deprecated since Python 3.3, but it
     is missed in the document.

   - bpo-33126(7): Document PyBuffer_ToContiguous().

   - bpo-27212(8): Modify documentation for the ‘islice()’ recipe to
     consume initial values up to the start index.

   - bpo-28247(9): Update *note zipapp: 116. documentation to describe
     how to make standalone applications.

   - bpo-18802(10): Documentation changes for ipaddress.  Patch by Jon
     Foster and Berker Peksag.

   - bpo-27428(11): Update documentation to clarify that
     ‘WindowsRegistryFinder’ implements ‘MetaPathFinder’.  (Patch by
     Himanshu Lakhara)

   - bpo-8243(12): Add a note about curses.addch and curses.addstr
     exception behavior when writing outside a window, or pad.

   - bpo-31432(13): Clarify meaning of CERT_NONE, CERT_OPTIONAL, and
     CERT_REQUIRED flags for ssl.SSLContext.verify_mode.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33503

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33421

   (3) https://bugs.python.org/issue?@action=redirect&bpo=33378

   (4) https://bugs.python.org/issue?@action=redirect&bpo=33276

   (5) https://bugs.python.org/issue?@action=redirect&bpo=33201

   (6) https://bugs.python.org/issue?@action=redirect&bpo=33195

   (7) https://bugs.python.org/issue?@action=redirect&bpo=33126

   (8) https://bugs.python.org/issue?@action=redirect&bpo=27212

   (9) https://bugs.python.org/issue?@action=redirect&bpo=28247

   (10) https://bugs.python.org/issue?@action=redirect&bpo=18802

   (11) https://bugs.python.org/issue?@action=redirect&bpo=27428

   (12) https://bugs.python.org/issue?@action=redirect&bpo=8243

   (13) https://bugs.python.org/issue?@action=redirect&bpo=31432


File: python.info,  Node: Tests<54>,  Next: Build<57>,  Prev: Documentation<54>,  Up: Python 3 6 6 release candidate 1

1.23.62.4 Tests
...............

   - bpo-33655(1): Ignore test_posix_fallocate failures on BSD platforms
     that might be due to running on ZFS.

   - bpo-19417(2): Add test_bdb.py.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33655

   (2) https://bugs.python.org/issue?@action=redirect&bpo=19417


File: python.info,  Node: Build<57>,  Next: Windows<52>,  Prev: Tests<54>,  Up: Python 3 6 6 release candidate 1

1.23.62.5 Build
...............

   - bpo-5755(1): Move ‘-Wstrict-prototypes’ option to ‘CFLAGS_NODIST’
     from ‘OPT’.  This option emitted annoying warnings when building
     extension modules written in C++.

   - bpo-33614(2): Ensures module definition files for the stable ABI on
     Windows are correctly regenerated.

   - bpo-33522(3): Enable CI builds on Visual Studio Team Services at
     ‘https://python.visualstudio.com/cpython’

   - bpo-33012(4): Add ‘-Wno-cast-function-type’ for gcc 8 for silencing
     warnings about function casts like casting to PyCFunction in method
     definition lists.

   - bpo-33394(5): Enable the verbose build for extension modules, when
     GNU make is passed macros on the command line.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=5755

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33614

   (3) https://bugs.python.org/issue?@action=redirect&bpo=33522

   (4) https://bugs.python.org/issue?@action=redirect&bpo=33012

   (5) https://bugs.python.org/issue?@action=redirect&bpo=33394


File: python.info,  Node: Windows<52>,  Next: macOS<42>,  Prev: Build<57>,  Up: Python 3 6 6 release candidate 1

1.23.62.6 Windows
.................

   - bpo-33184(1): Update Windows installer to OpenSSL 1.0.2o.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33184


File: python.info,  Node: macOS<42>,  Next: IDLE<44>,  Prev: Windows<52>,  Up: Python 3 6 6 release candidate 1

1.23.62.7 macOS
...............

   - bpo-33184(1): Update macOS installer build to use OpenSSL 1.0.2o.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33184


File: python.info,  Node: IDLE<44>,  Next: Tools/Demos<30>,  Prev: macOS<42>,  Up: Python 3 6 6 release candidate 1

1.23.62.8 IDLE
..............

   - bpo-33656(1): On Windows, add API call saying that tk scales for
     DPI. On Windows 8.1+ or 10, with DPI compatibility properties of
     the Python binary unchanged, and a monitor resolution greater than
     96 DPI, this should make text and lines sharper.  It should
     otherwise have no effect.

   - bpo-33768(2): Clicking on a context line moves that line to the top
     of the editor window.

   - bpo-33763(3): IDLE: Use read-only text widget for code context
     instead of label widget.

   - bpo-33664(4): Scroll IDLE editor text by lines.  Previously, the
     mouse wheel and scrollbar slider moved text by a fixed number of
     pixels, resulting in partial lines at the top of the editor box.
     The change also applies to the shell and grep output windows, but
     not to read-only text views.

   - bpo-33679(5): Enable theme-specific color configuration for Code
     Context.  Use the Highlights tab to see the setting for built-in
     themes or add settings to custom themes.

   - bpo-33642(6): Display up to maxlines non-blank lines for Code
     Context.  If there is no current context, show a single blank line.

   - bpo-33628(7): IDLE: Cleanup codecontext.py and its test.

   - bpo-33564(8): IDLE's code context now recognizes async as a block
     opener.

   - bpo-29706(9): IDLE now colors async and await as keywords in 3.6.
     They become full keywords in 3.7.

   - bpo-21474(10): Update word/identifier definition from ascii to
     unicode.  In text and entry boxes, this affects selection by
     double-click, movement left/right by control-left/right, and
     deletion left/right by control-BACKSPACE/DEL.

   - bpo-33204(11): IDLE: consistently color invalid string prefixes.  A
     'u' string prefix cannot be paired with either 'r' or 'f'.
     Consistently color as much of the prefix, starting at the right, as
     is valid.  Revise and extend colorizer test.

   - bpo-32831(12): Add docstrings and tests for codecontext.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33656

   (2) https://bugs.python.org/issue?@action=redirect&bpo=33768

   (3) https://bugs.python.org/issue?@action=redirect&bpo=33763

   (4) https://bugs.python.org/issue?@action=redirect&bpo=33664

   (5) https://bugs.python.org/issue?@action=redirect&bpo=33679

   (6) https://bugs.python.org/issue?@action=redirect&bpo=33642

   (7) https://bugs.python.org/issue?@action=redirect&bpo=33628

   (8) https://bugs.python.org/issue?@action=redirect&bpo=33564

   (9) https://bugs.python.org/issue?@action=redirect&bpo=29706

   (10) https://bugs.python.org/issue?@action=redirect&bpo=21474

   (11) https://bugs.python.org/issue?@action=redirect&bpo=33204

   (12) https://bugs.python.org/issue?@action=redirect&bpo=32831


File: python.info,  Node: Tools/Demos<30>,  Next: C API<54>,  Prev: IDLE<44>,  Up: Python 3 6 6 release candidate 1

1.23.62.9 Tools/Demos
.....................

   - bpo-33189(1): ‘pygettext.py’ now recognizes only literal strings as
     docstrings and translatable strings, and rejects bytes literals and
     f-string expressions.

   - bpo-31920(2): Fixed handling directories as arguments in the
     ‘pygettext’ script.  Based on patch by Oleg Krasnikov.

   - bpo-29673(3): Fix pystackv and pystack gdbinit macros.

   - bpo-32885(4): Add an ‘-n’ flag for ‘Tools/scripts/pathfix.py’ to
     disable automatic backup creation (files with ‘~’ suffix).

   - bpo-31583(5): Fix 2to3 for using with -add-suffix option but
     without -output-dir option for relative path to files in current
     directory.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33189

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31920

   (3) https://bugs.python.org/issue?@action=redirect&bpo=29673

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32885

   (5) https://bugs.python.org/issue?@action=redirect&bpo=31583


File: python.info,  Node: C API<54>,  Prev: Tools/Demos<30>,  Up: Python 3 6 6 release candidate 1

1.23.62.10 C API
................

   - bpo-32374(1): Document that m_traverse for multi-phase initialized
     modules can be called with m_state=NULL, and add a sanity check

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32374


File: python.info,  Node: Python 3 6 5 final,  Next: Python 3 6 5 release candidate 1,  Prev: Python 3 6 6 release candidate 1,  Up: Changelog（更動日誌）

1.23.63 Python 3.6.5 final
--------------------------

'Release date: 2018-03-28'

* Menu:

* Tests: Tests<55>.
* Build: Build<58>.


File: python.info,  Node: Tests<55>,  Next: Build<58>,  Up: Python 3 6 5 final

1.23.63.1 Tests
...............

   - bpo-32872(1): Avoid regrtest compatibility issue with namespace
     packages.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32872


File: python.info,  Node: Build<58>,  Prev: Tests<55>,  Up: Python 3 6 5 final

1.23.63.2 Build
...............

   - bpo-33163(1): Upgrade pip to 9.0.3 and setuptools to v39.0.1.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33163


File: python.info,  Node: Python 3 6 5 release candidate 1,  Next: Python 3 6 4 final,  Prev: Python 3 6 5 final,  Up: Changelog（更動日誌）

1.23.64 Python 3.6.5 release candidate 1
----------------------------------------

'Release date: 2018-03-13'

* Menu:

* Security: Security<37>.
* Core and Builtins: Core and Builtins<61>.
* Library: Library<61>.
* Documentation: Documentation<55>.
* Tests: Tests<56>.
* Build: Build<59>.
* Windows: Windows<53>.
* macOS: macOS<43>.
* IDLE: IDLE<45>.
* Tools/Demos: Tools/Demos<31>.
* C API: C API<55>.


File: python.info,  Node: Security<37>,  Next: Core and Builtins<61>,  Up: Python 3 6 5 release candidate 1

1.23.64.1 Security
..................

   - bpo-33001(1): Minimal fix to prevent buffer overrun in os.symlink
     on Windows

   - bpo-32981(2): Regexes in difflib and poplib were vulnerable to
     catastrophic backtracking.  These regexes formed potential DOS
     vectors (REDOS). They have been refactored.  This resolves
     CVE-2018-1060(3) and CVE-2018-1061(4).  Patch by Jamie Davis.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33001

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32981

   (3) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1060

   (4) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1061


File: python.info,  Node: Core and Builtins<61>,  Next: Library<61>,  Prev: Security<37>,  Up: Python 3 6 5 release candidate 1

1.23.64.2 Core and Builtins
...........................

   - bpo-33026(1): Fixed jumping out of "with" block by setting
     f_lineno.

   - bpo-17288(2): Prevent jumps from 'return' and 'exception' trace
     events.

   - bpo-32889(3): Update Valgrind suppression list to account for the
     rename of ‘Py_ADDRESS_IN_RANG’ to ‘address_in_range’.

   - bpo-32650(4): Pdb and other debuggers dependent on bdb.py will
     correctly step over (next command) native coroutines.  Patch by
     Pablo Galindo.

   - bpo-32685(5): Improve suggestion when the Python 2 form of print
     statement is either present on the same line as the header of a
     compound statement or else terminated by a semi-colon instead of a
     newline.  Patch by Nitish Chandra.

   - bpo-32583(6): Fix possible crashing in builtin Unicode decoders
     caused by write out-of-bound errors when using customized decode
     error handlers.

   - bpo-26163(7): Improved frozenset() hash to create more distinct
     hash values when faced with datasets containing many similar
     values.

   - bpo-27169(8): The ‘__debug__’ constant is now optimized out at
     compile time.  This fixes also bpo-22091(9).

   - bpo-32329(10): ‘sys.flags.hash_randomization’ is now properly set
     to 0 when hash randomization is turned off by ‘PYTHONHASHSEED=0’.

   - bpo-30416(11): The optimizer is now protected from spending much
     time doing complex calculations and consuming much memory for
     creating large constants in constant folding.

   - bpo-18533(12): ‘repr()’ on a dict containing its own ‘values()’ or
     ‘items()’ no longer raises ‘RecursionError’; OrderedDict similarly.
     Instead, use ‘...’, as for other recursive structures.  Patch by
     Ben North.

   - bpo-32028(13): Leading whitespace is now correctly ignored when
     generating suggestions for converting Py2 print statements to Py3
     builtin print function calls.  Patch by Sanyam Khurana.

   - bpo-32137(14): The repr of deeply nested dict now raises a
     RecursionError instead of crashing due to a stack overflow.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33026

   (2) https://bugs.python.org/issue?@action=redirect&bpo=17288

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32889

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32650

   (5) https://bugs.python.org/issue?@action=redirect&bpo=32685

   (6) https://bugs.python.org/issue?@action=redirect&bpo=32583

   (7) https://bugs.python.org/issue?@action=redirect&bpo=26163

   (8) https://bugs.python.org/issue?@action=redirect&bpo=27169

   (9) https://bugs.python.org/issue?@action=redirect&bpo=22091

   (10) https://bugs.python.org/issue?@action=redirect&bpo=32329

   (11) https://bugs.python.org/issue?@action=redirect&bpo=30416

   (12) https://bugs.python.org/issue?@action=redirect&bpo=18533

   (13) https://bugs.python.org/issue?@action=redirect&bpo=32028

   (14) https://bugs.python.org/issue?@action=redirect&bpo=32137


File: python.info,  Node: Library<61>,  Next: Documentation<55>,  Prev: Core and Builtins<61>,  Up: Python 3 6 5 release candidate 1

1.23.64.3 Library
.................

   - bpo-33064(1): lib2to3 now properly supports trailing commas after
     ‘*args’ and ‘**kwargs’ in function signatures.

   - bpo-31804(2): Avoid failing in multiprocessing.Process if the
     standard streams are closed or None at exit.

   - bpo-33037(3): Skip sending/receiving data after SSL transport
     closing.

   - bpo-30353(4): Fix ctypes pass-by-value for structs on 64-bit
     Cygwin/MinGW.

   - bpo-33009(5): Fix inspect.signature() for single-parameter
     partialmethods.

   - bpo-32969(6): Expose several missing constants in zlib and fix
     corresponding documentation.

   - bpo-32713(7): Fixed tarfile.itn handling of out-of-bounds float
     values.  Patch by Joffrey Fuhrer.

   - bpo-30622(8): The ssl module now detects missing NPN support in
     LibreSSL.

   - bpo-32922(9): dbm.open() now encodes filename with the filesystem
     encoding rather than default encoding.

   - bpo-32859(10): In ‘os.dup2’, don't check every call whether the
     ‘dup3’ syscall exists or not.

   - bpo-21060(11): Rewrite confusing message from setup.py upload from
     "No dist file created in earlier command" to the more helpful "Must
     create and upload files in one command".

   - bpo-32857(12): In *note tkinter: d9, ‘after_cancel(None)’ now
     raises a *note ValueError: 1e7. instead of canceling the first
     scheduled function.  Patch by Cheryl Sabella.

   - bpo-32852(13): Make sure sys.argv remains as a list when running
     trace.

   - bpo-32841(14): Fixed ‘asyncio.Condition’ issue which silently
     ignored cancellation after notifying and cancelling a conditional
     lock.  Patch by Bar Harel.

   - bpo-31787(15): Fixed refleaks of ‘__init__()’ methods in various
     modules.  (Contributed by Oren Milman)

   - bpo-30157(16): Fixed guessing quote and delimiter in
     csv.Sniffer.sniff() when only the last field is quoted.  Patch by
     Jake Davis.

   - bpo-32394(17): socket: Remove TCP_FASTOPEN, TCP_KEEPCNT flags on
     older version Windows during run-time.

   - bpo-32777(18): Fix a rare but potential pre-exec child process
     deadlock in subprocess on POSIX systems when marking file
     descriptors inheritable on exec in the child process.  This bug
     appears to have been introduced in 3.4.

   - bpo-32647(19): The ctypes module used to depend on indirect linking
     for dlopen.  The shared extension is now explicitly linked against
     libdl on platforms with dl.

   - bpo-32734(20): Fixed ‘asyncio.Lock()’ safety issue which allowed
     acquiring and locking the same lock multiple times, without it
     being free.  Patch by Bar Harel.

   - bpo-32727(21): Do not include name field in SMTP envelope from
     address.  Patch by Stéphane Wirtel

   - bpo-27931(22): Fix email address header parsing error when the
     username is an empty quoted string.  Patch by Xiang Zhang.

   - bpo-32304(23): distutils' upload command no longer corrupts tar
     files ending with a CR byte, and no longer tries to convert CR to
     CRLF in any of the upload text fields.

   - bpo-32502(24): uuid.uuid1 no longer raises an exception if a 64-bit
     hardware address is encountered.

   - bpo-31848(25): Fix the error handling in Aifc_read.initfp() when
     the SSND chunk is not found.  Patch by Zackery Spytz.

   - bpo-32555(26): On FreeBSD and Solaris, os.strerror() now always
     decode the byte string from the current locale encoding, rather
     than using ASCII/surrogateescape in some cases.

   - bpo-32521(27): The nis module is now compatible with new libnsl and
     headers location.

   - bpo-32473(28): Improve ABCMeta._dump_registry() output readability

   - bpo-32521(29): glibc has removed Sun RPC. Use replacement libtirpc
     headers and library in nis module.

   - bpo-32228(30): Ensure that ‘truncate()’ preserves the file position
     (as reported by ‘tell()’) after writes longer than the buffer size.

   - bpo-26133(31): Don't unsubscribe signals in asyncio UNIX event loop
     on interpreter shutdown.

   - bpo-32185(32): The SSL module no longer sends IP addresses in SNI
     TLS extension on platforms with OpenSSL 1.0.2+ or inet_pton.

   - bpo-32323(33): *note urllib.parse.urlsplit(): ce6. does not convert
     zone-id (scope) to lower case for scoped IPv6 addresses in
     hostnames now.

   - bpo-32302(34): Fix bdist_wininst of distutils for CRT v142: it
     binary compatible with CRT v140.

   - bpo-32255(35): A single empty field is now always quoted when
     written into a CSV file.  This allows to distinguish an empty row
     from a row consisting of a single empty field.  Patch by Licht
     Takeuchi.

   - bpo-32277(36): Raise ‘NotImplementedError’ instead of ‘SystemError’
     on platforms where ‘chmod(..., follow_symlinks=False)’ is not
     supported.  Patch by Anthony Sottile.

   - bpo-32199(37): The getnode() ip getter now uses 'ip link' instead
     of 'ip link list'.

   - bpo-27456(38): Ensure TCP_NODELAY is set on Linux.  Tests by Victor
     Stinner.

   - bpo-31900(39): The *note locale.localeconv(): ba5. function now
     sets temporarily the ‘LC_CTYPE’ locale to the ‘LC_NUMERIC’ locale
     to decode ‘decimal_point’ and ‘thousands_sep’ byte strings if they
     are non-ASCII or longer than 1 byte, and the ‘LC_NUMERIC’ locale is
     different than the ‘LC_CTYPE’ locale.  This temporary change
     affects other threads.  Same change for the *note str.format():
     5c7. method when formatting a number (*note int: 23c, *note float:
     2c8, *note float: 2c8. and subclasses) with the ‘n’ type (ex:
     ‘'{:n}'.format(1234)’).

   - bpo-31802(40): Importing native path module (‘posixpath’, ‘ntpath’)
     now works even if the ‘os’ module still is not imported.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33064

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31804

   (3) https://bugs.python.org/issue?@action=redirect&bpo=33037

   (4) https://bugs.python.org/issue?@action=redirect&bpo=30353

   (5) https://bugs.python.org/issue?@action=redirect&bpo=33009

   (6) https://bugs.python.org/issue?@action=redirect&bpo=32969

   (7) https://bugs.python.org/issue?@action=redirect&bpo=32713

   (8) https://bugs.python.org/issue?@action=redirect&bpo=30622

   (9) https://bugs.python.org/issue?@action=redirect&bpo=32922

   (10) https://bugs.python.org/issue?@action=redirect&bpo=32859

   (11) https://bugs.python.org/issue?@action=redirect&bpo=21060

   (12) https://bugs.python.org/issue?@action=redirect&bpo=32857

   (13) https://bugs.python.org/issue?@action=redirect&bpo=32852

   (14) https://bugs.python.org/issue?@action=redirect&bpo=32841

   (15) https://bugs.python.org/issue?@action=redirect&bpo=31787

   (16) https://bugs.python.org/issue?@action=redirect&bpo=30157

   (17) https://bugs.python.org/issue?@action=redirect&bpo=32394

   (18) https://bugs.python.org/issue?@action=redirect&bpo=32777

   (19) https://bugs.python.org/issue?@action=redirect&bpo=32647

   (20) https://bugs.python.org/issue?@action=redirect&bpo=32734

   (21) https://bugs.python.org/issue?@action=redirect&bpo=32727

   (22) https://bugs.python.org/issue?@action=redirect&bpo=27931

   (23) https://bugs.python.org/issue?@action=redirect&bpo=32304

   (24) https://bugs.python.org/issue?@action=redirect&bpo=32502

   (25) https://bugs.python.org/issue?@action=redirect&bpo=31848

   (26) https://bugs.python.org/issue?@action=redirect&bpo=32555

   (27) https://bugs.python.org/issue?@action=redirect&bpo=32521

   (28) https://bugs.python.org/issue?@action=redirect&bpo=32473

   (29) https://bugs.python.org/issue?@action=redirect&bpo=32521

   (30) https://bugs.python.org/issue?@action=redirect&bpo=32228

   (31) https://bugs.python.org/issue?@action=redirect&bpo=26133

   (32) https://bugs.python.org/issue?@action=redirect&bpo=32185

   (33) https://bugs.python.org/issue?@action=redirect&bpo=32323

   (34) https://bugs.python.org/issue?@action=redirect&bpo=32302

   (35) https://bugs.python.org/issue?@action=redirect&bpo=32255

   (36) https://bugs.python.org/issue?@action=redirect&bpo=32277

   (37) https://bugs.python.org/issue?@action=redirect&bpo=32199

   (38) https://bugs.python.org/issue?@action=redirect&bpo=27456

   (39) https://bugs.python.org/issue?@action=redirect&bpo=31900

   (40) https://bugs.python.org/issue?@action=redirect&bpo=31802


File: python.info,  Node: Documentation<55>,  Next: Tests<56>,  Prev: Library<61>,  Up: Python 3 6 5 release candidate 1

1.23.64.4 Documentation
.......................

   - bpo-17232(1): Clarify docs for -O and -OO. Patch by Terry Reedy.

   - bpo-32800(2): Update link to w3c doc for xml default namespaces.

   - bpo-8722(3): Document ‘__getattr__()’ behavior when property
     ‘get()’ method raises *note AttributeError: 2f6.

   - bpo-32614(4): Modify RE examples in documentation to use raw
     strings to prevent *note DeprecationWarning: 18b. and add text to
     REGEX HOWTO to highlight the deprecation.

   - bpo-31972(5): Improve docstrings for ‘pathlib.PurePath’ subclasses.

   - bpo-17799(6): Explain real behaviour of sys.settrace and
     sys.setprofile and their C-API counterparts regarding which type of
     events are received in each function.  Patch by Pablo Galindo
     Salgado.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=17232

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32800

   (3) https://bugs.python.org/issue?@action=redirect&bpo=8722

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32614

   (5) https://bugs.python.org/issue?@action=redirect&bpo=31972

   (6) https://bugs.python.org/issue?@action=redirect&bpo=17799


File: python.info,  Node: Tests<56>,  Next: Build<59>,  Prev: Documentation<55>,  Up: Python 3 6 5 release candidate 1

1.23.64.5 Tests
...............

   - bpo-32517(1): Fix failing ‘test_asyncio’ on macOS 10.12.2+ due to
     transport of ‘KqueueSelector’ loop was not being closed.

   - bpo-32721(2): Fix test_hashlib to not fail if the _md5 module is
     not built.

   - bpo-32252(3): Fix faulthandler_suppress_crash_report() used to
     prevent core dump files when testing crashes.  getrlimit() returns
     zero on success.

   - bpo-31518(4): Debian Unstable has disabled TLS 1.0 and 1.1 for
     SSLv23_METHOD().  Change TLS/SSL protocol of some tests to
     PROTOCOL_TLS or PROTOCOL_TLSv1_2 to make them pass on Debian.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32517

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32721

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32252

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31518


File: python.info,  Node: Build<59>,  Next: Windows<53>,  Prev: Tests<56>,  Up: Python 3 6 5 release candidate 1

1.23.64.6 Build
...............

   - bpo-32635(1): Fix segfault of the crypt module when libxcrypt is
     provided instead of libcrypt at the system.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32635


File: python.info,  Node: Windows<53>,  Next: macOS<43>,  Prev: Build<59>,  Up: Python 3 6 5 release candidate 1

1.23.64.7 Windows
.................

   - bpo-33016(1): Fix potential use of uninitialized memory in
     nt._getfinalpathname

   - bpo-32903(2): Fix a memory leak in os.chdir() on Windows if the
     current directory is set to a UNC path.

   - bpo-31966(3): Fixed WindowsConsoleIO.write() for writing empty
     data.

   - bpo-32409(4): Ensures activate.bat can handle Unicode contents.

   - bpo-32457(5): Improves handling of denormalized executable path
     when launching Python.

   - bpo-32370(6): Use the correct encoding for ipconfig output in the
     uuid module.  Patch by Segev Finer.

   - bpo-29248(7): Fix *note os.readlink(): 8c5. on Windows, which was
     mistakenly treating the ‘PrintNameOffset’ field of the reparse data
     buffer as a number of characters instead of bytes.  Patch by Craig
     Holmquist and SSE4.

   - bpo-32588(8): Create standalone _distutils_findvs module.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33016

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32903

   (3) https://bugs.python.org/issue?@action=redirect&bpo=31966

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32409

   (5) https://bugs.python.org/issue?@action=redirect&bpo=32457

   (6) https://bugs.python.org/issue?@action=redirect&bpo=32370

   (7) https://bugs.python.org/issue?@action=redirect&bpo=29248

   (8) https://bugs.python.org/issue?@action=redirect&bpo=32588


File: python.info,  Node: macOS<43>,  Next: IDLE<45>,  Prev: Windows<53>,  Up: Python 3 6 5 release candidate 1

1.23.64.8 macOS
...............

   - bpo-32726(1): Provide an additional, more modern macOS installer
     variant that supports macOS 10.9+ systems in 64-bit mode only.
     Upgrade the supplied third-party libraries to OpenSSL 1.0.2n, XZ
     5.2.3, and SQLite 3.22.0.  The 10.9+ installer now links with and
     supplies its own copy of Tcl/Tk 8.6.8.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32726


File: python.info,  Node: IDLE<45>,  Next: Tools/Demos<31>,  Prev: macOS<43>,  Up: Python 3 6 5 release candidate 1

1.23.64.9 IDLE
..............

   - bpo-32984(1): Set ‘__file__’ while running a startup file.  Like
     Python, IDLE optionally runs one startup file in the Shell window
     before presenting the first interactive input prompt.  For IDLE,
     ‘-s’ runs a file named in environmental variable ‘IDLESTARTUP’ or
     *note PYTHONSTARTUP: f6b.; ‘-r file’ runs ‘file’.  Python sets
     ‘__file__’ to the startup file name before running the file and
     unsets it before the first prompt.  IDLE now does the same when run
     normally, without the ‘-n’ option.

   - bpo-32940(2): Simplify and rename StringTranslatePseudoMapping in
     pyparse.

   - bpo-32916(3): Change ‘str’ to ‘code’ in pyparse.

   - bpo-32905(4): Remove unused code in pyparse module.

   - bpo-32874(5): Add tests for pyparse.

   - bpo-32837(6): Using the system and place-dependent default encoding
     for open() is a bad idea for IDLE's system and location-independent
     files.

   - bpo-32826(7): Add "encoding=utf-8" to open() in IDLE's
     test_help_about.  GUI test test_file_buttons() only looks at
     initial ascii-only lines, but failed on systems where open()
     defaults to 'ascii' because readline() internally reads and decodes
     far enough ahead to encounter a non-ascii character in CREDITS.txt.

   - bpo-32765(8): Update configdialog General tab docstring to add new
     widgets to the widget list.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32984

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32940

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32916

   (4) https://bugs.python.org/issue?@action=redirect&bpo=32905

   (5) https://bugs.python.org/issue?@action=redirect&bpo=32874

   (6) https://bugs.python.org/issue?@action=redirect&bpo=32837

   (7) https://bugs.python.org/issue?@action=redirect&bpo=32826

   (8) https://bugs.python.org/issue?@action=redirect&bpo=32765


File: python.info,  Node: Tools/Demos<31>,  Next: C API<55>,  Prev: IDLE<45>,  Up: Python 3 6 5 release candidate 1

1.23.64.10 Tools/Demos
......................

   - bpo-24960(1): 2to3 and lib2to3 can now read pickled grammar files
     using pkgutil.get_data() rather than probing the filesystem.  This
     lets 2to3 and lib2to3 work when run from a zipfile.

   - bpo-32222(2): Fix pygettext not extracting docstrings for functions
     with type annotated arguments.  Patch by Toby Harradine.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24960

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32222


File: python.info,  Node: C API<55>,  Prev: Tools/Demos<31>,  Up: Python 3 6 5 release candidate 1

1.23.64.11 C API
................

   - bpo-29084(1): Undocumented C API for OrderedDict has been excluded
     from the limited C API. It was added by mistake and actually never
     worked in the limited C API.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29084


File: python.info,  Node: Python 3 6 4 final,  Next: Python 3 6 4 release candidate 1,  Prev: Python 3 6 5 release candidate 1,  Up: Changelog（更動日誌）

1.23.65 Python 3.6.4 final
--------------------------

'Release date: 2017-12-18'

There were no new code changes in version 3.6.4 since v3.6.4rc1.


File: python.info,  Node: Python 3 6 4 release candidate 1,  Next: Python 3 6 3 final,  Prev: Python 3 6 4 final,  Up: Changelog（更動日誌）

1.23.66 Python 3.6.4 release candidate 1
----------------------------------------

'Release date: 2017-12-05'

* Menu:

* Core and Builtins: Core and Builtins<62>.
* Library: Library<62>.
* Documentation: Documentation<56>.
* Tests: Tests<57>.
* Build: Build<60>.
* Windows: Windows<54>.
* macOS: macOS<44>.
* IDLE: IDLE<46>.
* Tools/Demos: Tools/Demos<32>.
* C API: C API<56>.


File: python.info,  Node: Core and Builtins<62>,  Next: Library<62>,  Up: Python 3 6 4 release candidate 1

1.23.66.1 Core and Builtins
...........................

   - bpo-32176(1): co_flags.CO_NOFREE is now always set correctly by the
     code object constructor based on freevars and cellvars, rather than
     needing to be set correctly by the caller.  This ensures it will be
     cleared automatically when additional cell references are injected
     into a modified code object and function.

   - bpo-31949(2): Fixed several issues in printing tracebacks
     (PyTraceBack_Print()).  Setting sys.tracebacklimit to 0 or less now
     suppresses printing tracebacks.  Setting sys.tracebacklimit to None
     now causes using the default limit.  Setting sys.tracebacklimit to
     an integer larger than LONG_MAX now means using the limit LONG_MAX
     rather than the default limit.  Fixed integer overflows in the case
     of more than ‘2**31’ traceback items on Windows.  Fixed output
     errors handling.

   - bpo-30696(3): Fix the interactive interpreter looping endlessly
     when no memory.

   - bpo-20047(4): Bytearray methods partition() and rpartition() now
     accept only bytes-like objects as separator, as documented.  In
     particular they now raise TypeError rather of returning a bogus
     result when an integer is passed as a separator.

   - bpo-31852(5): Fix a segmentation fault caused by a combination of
     the async soft keyword and continuation lines.

   - bpo-21720(6): BytesWarning no longer emitted when the 'fromlist'
     argument of ‘__import__()’ or the ‘__all__’ attribute of the module
     contain bytes instances.

   - bpo-31825(7): Fixed OverflowError in the 'unicode-escape' codec and
     in codecs.escape_decode() when decode an escaped non-ascii byte.

   - bpo-28603(8): Print the full context/cause chain of exceptions on
     interpreter exit, even if an exception in the chain is unhashable
     or compares equal to later ones.  Patch by Zane Bitter.

   - bpo-31786(9): Fix timeout rounding in the select module to round
     correctly negative timeouts between -1.0 and 0.0.  The functions
     now block waiting for events as expected.  Previously, the call was
     incorrectly non-blocking.  Patch by Pablo Galindo.

   - bpo-31642(10): Restored blocking "from package import module" by
     setting sys.modules["package.module"] to None.

   - bpo-31626(11): Fixed a bug in debug memory allocator.  There was a
     write to freed memory after shrinking a memory block.

   - bpo-31619(12): Fixed a ValueError when convert a string with large
     number of underscores to integer with binary base.

   - bpo-31592(13): Fixed an assertion failure in Python parser in case
     of a bad ‘unicodedata.normalize()’.  Patch by Oren Milman.

   - bpo-31588(14): Raise a ‘TypeError’ with a helpful error message
     when class creation fails due to a metaclass with a bad
     ‘__prepare__()’ method.  Patch by Oren Milman.

   - bpo-31566(15): Fix an assertion failure in ‘_warnings.warn()’ in
     case of a bad ‘__name__’ global.  Patch by Oren Milman.

   - bpo-31505(16): Fix an assertion failure in ‘json’, in case
     ‘_json.make_encoder()’ received a bad ‘encoder()’ argument.  Patch
     by Oren Milman.

   - bpo-31492(17): Fix assertion failures in case of failing to import
     from a module with a bad ‘__name__’ attribute, and in case of
     failing to access an attribute of such a module.  Patch by Oren
     Milman.

   - bpo-31490(18): Fix an assertion failure in ‘ctypes’ class
     definition, in case the class has an attribute whose name is
     specified in ‘_anonymous_’ but not in ‘_fields_’.  Patch by Oren
     Milman.

   - bpo-31478(19): Fix an assertion failure in ‘_random.Random.seed()’
     in case the argument has a bad ‘__abs__()’ method.  Patch by Oren
     Milman.

   - bpo-31315(20): Fix an assertion failure in imp.create_dynamic(),
     when spec.name is not a string.  Patch by Oren Milman.

   - bpo-31311(21): Fix a crash in the ‘__setstate__()’ method of
     ‘ctypes._CData’, in case of a bad ‘__dict__’.  Patch by Oren
     Milman.

   - bpo-31293(22): Fix crashes in true division and multiplication of a
     timedelta object by a float with a bad as_integer_ratio() method.
     Patch by Oren Milman.

   - bpo-31285(23): Fix an assertion failure in
     ‘warnings.warn_explicit’, when the return value of the received
     loader's ‘get_source()’ has a bad ‘splitlines()’ method.  Patch by
     Oren Milman.

   - bpo-30817(24): ‘PyErr_PrintEx()’ clears now the ignored exception
     that may be raised by ‘_PySys_SetObjectId()’, for example when no
     memory.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32176

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31949

   (3) https://bugs.python.org/issue?@action=redirect&bpo=30696

   (4) https://bugs.python.org/issue?@action=redirect&bpo=20047

   (5) https://bugs.python.org/issue?@action=redirect&bpo=31852

   (6) https://bugs.python.org/issue?@action=redirect&bpo=21720

   (7) https://bugs.python.org/issue?@action=redirect&bpo=31825

   (8) https://bugs.python.org/issue?@action=redirect&bpo=28603

   (9) https://bugs.python.org/issue?@action=redirect&bpo=31786

   (10) https://bugs.python.org/issue?@action=redirect&bpo=31642

   (11) https://bugs.python.org/issue?@action=redirect&bpo=31626

   (12) https://bugs.python.org/issue?@action=redirect&bpo=31619

   (13) https://bugs.python.org/issue?@action=redirect&bpo=31592

   (14) https://bugs.python.org/issue?@action=redirect&bpo=31588

   (15) https://bugs.python.org/issue?@action=redirect&bpo=31566

   (16) https://bugs.python.org/issue?@action=redirect&bpo=31505

   (17) https://bugs.python.org/issue?@action=redirect&bpo=31492

   (18) https://bugs.python.org/issue?@action=redirect&bpo=31490

   (19) https://bugs.python.org/issue?@action=redirect&bpo=31478

   (20) https://bugs.python.org/issue?@action=redirect&bpo=31315

   (21) https://bugs.python.org/issue?@action=redirect&bpo=31311

   (22) https://bugs.python.org/issue?@action=redirect&bpo=31293

   (23) https://bugs.python.org/issue?@action=redirect&bpo=31285

   (24) https://bugs.python.org/issue?@action=redirect&bpo=30817


File: python.info,  Node: Library<62>,  Next: Documentation<56>,  Prev: Core and Builtins<62>,  Up: Python 3 6 4 release candidate 1

1.23.66.2 Library
.................

   - bpo-28556(1): Two minor fixes for ‘typing’ module: allow shallow
     copying instances of generic classes, improve interaction of
     ‘__init_subclass__’ with generics.  Original PRs by Ivan
     Levkivskyi.

   - bpo-27240(2): The header folding algorithm for the new email
     policies has been rewritten, which also fixes bpo-30788(3),
     bpo-31831(4), and bpo-32182(5).  In particular, RFC2231 folding is
     now done correctly.

   - bpo-32186(6): io.FileIO.readall() and io.FileIO.read() now release
     the GIL when getting the file size.  Fixed hang of all threads with
     inaccessible NFS server.  Patch by Nir Soffer.

   - bpo-12239(7): Make ‘msilib.SummaryInformation.GetProperty()’ return
     ‘None’ when the value of property is ‘VT_EMPTY’.  Initial patch by
     Mark Mc Mahon.

   - bpo-31325(8): Fix wrong usage of *note collections.namedtuple():
     1ae. in the *note RobotFileParser.parse(): 19a8. method.  Initial
     patch by Robin Wellner.

   - bpo-12382(9): ‘msilib.OpenDatabase()’ now raises a better exception
     message when it couldn't open or create an MSI file.  Initial patch
     by William Tisäter.

   - bpo-32110(10): ‘codecs.StreamReader.read(n)’ now returns not more
     than 'n' characters/bytes for non-negative 'n'.  This makes it
     compatible with ‘read()’ methods of other file-like objects.

   - bpo-32072(11): Fixed issues with binary plists: Fixed saving
     bytearrays.  Identical objects will be saved only once.  Equal
     references will be load as identical objects.  Added support for
     saving and loading recursive data structures.

   - bpo-32034(12): Make asyncio.IncompleteReadError and
     LimitOverrunError pickleable.

   - bpo-32015(13): Fixed the looping of asyncio in the case of
     reconnection the socket during waiting async read/write from/to the
     socket.

   - bpo-32011(14): Restored support of loading marshal files with the
     TYPE_INT64 code.  These files can be produced in Python 2.7.

   - bpo-31970(15): Reduce performance overhead of asyncio debug mode.

   - bpo-9678(16): Fixed determining the MAC address in the uuid module:
     Using ifconfig on NetBSD and OpenBSD. Using arp on Linux, FreeBSD,
     NetBSD and OpenBSD. Based on patch by Takayuki Shimizukawa.

   - bpo-30057(17): Fix potential missed signal in signal.signal().

   - bpo-31933(18): Fix Blake2 params leaf_size and node_offset on big
     endian platforms.  Patch by Jack O'Connor.

   - bpo-31927(19): Fixed compilation of the socket module on NetBSD 8.
     Fixed assertion failure or reading arbitrary data when parse a
     AF_BLUETOOTH address on NetBSD and DragonFly BSD.

   - bpo-27666(20): Fixed stack corruption in curses.box() and
     curses.ungetmouse() when the size of types chtype or mmask_t is
     less than the size of C long.  curses.box() now accepts characters
     as arguments.  Based on patch by Steve Fink.

   - bpo-31897(21): plistlib now catches more errors when read binary
     plists and raises InvalidFileException instead of unexpected
     exceptions.

   - bpo-25720(22): Fix the method for checking pad state of curses
     WINDOW. Patch by Masayuki Yamamoto.

   - bpo-31893(23): Fixed the layout of the kqueue_event structure on
     OpenBSD and NetBSD. Fixed the comparison of the kqueue_event
     objects.

   - bpo-31891(24): Fixed building the curses module on NetBSD.

   - bpo-28416(25): Instances of pickle.Pickler subclass with the
     persistent_id() method and pickle.Unpickler subclass with the
     persistent_load() method no longer create reference cycles.

   - bpo-28326(26): Fix multiprocessing.Process when stdout and/or
     stderr is closed or None.

   - bpo-31457(27): If nested log adapters are used, the inner
     ‘process()’ methods are no longer omitted.

   - bpo-31457(28): The ‘manager’ property on LoggerAdapter objects is
     now properly settable.

   - bpo-31806(29): Fix timeout rounding in time.sleep(),
     threading.Lock.acquire() and socket.socket.settimeout() to round
     correctly negative timeouts between -1.0 and 0.0.  The functions
     now block waiting for events as expected.  Previously, the call was
     incorrectly non-blocking.  Patch by Pablo Galindo.

   - bpo-28603(30): traceback: Fix a TypeError that occurred during
     printing of exception tracebacks when either the current exception
     or an exception in its context/cause chain is unhashable.  Patch by
     Zane Bitter.

   - bpo-30058(31): Fixed buffer overflow in select.kqueue.control().

   - bpo-31770(32): Prevent a crash when calling the ‘__init__()’ method
     of a ‘sqlite3.Cursor’ object more than once.  Patch by Oren Milman.

   - bpo-31672(33): ‘idpattern’ in ‘string.Template’ matched some
     non-ASCII characters.  Now it uses ‘-i’ regular expression local
     flag to avoid non-ASCII characters.

   - bpo-31764(34): Prevent a crash in ‘sqlite3.Cursor.close()’ in case
     the ‘Cursor’ object is uninitialized.  Patch by Oren Milman.

   - bpo-31752(35): Fix possible crash in timedelta constructor called
     with custom integers.

   - bpo-31701(36): On Windows, faulthandler.enable() now ignores MSC
     and COM exceptions.

   - bpo-31728(37): Prevent crashes in ‘_elementtree’ due to unsafe
     cleanup of ‘Element.text’ and ‘Element.tail’.  Patch by Oren
     Milman.

   - bpo-31620(38): an empty asyncio.Queue now doesn't leak memory when
     queue.get pollers timeout

   - bpo-31632(39): Fix method set_protocol() of class
     _SSLProtocolTransport in asyncio module.  This method was
     previously modifying a wrong reference to the protocol.

   - bpo-31675(40): Fixed memory leaks in Tkinter's methods splitlist()
     and split() when pass a string larger than 2 GiB.

   - bpo-31673(41): Fixed typo in the name of Tkinter's method
     adderrorinfo().

   - bpo-30806(42): Fix the string representation of a netrc object.

   - bpo-15037(43): Added a workaround for getkey() in curses for
     ncurses 5.7 and earlier.

   - bpo-25351(44): Avoid venv activate failures with undefined
     variables

   - bpo-25532(45): inspect.unwrap() will now only try to unwrap an
     object sys.getrecursionlimit() times, to protect against objects
     which create a new object on every attribute access.

   - bpo-30347(46): Stop crashes when concurrently iterate over
     itertools.groupby() iterators.

   - bpo-31516(47): ‘threading.current_thread()’ should not return a
     dummy thread at shutdown.

   - bpo-31351(48): python -m ensurepip now exits with non-zero exit
     code if pip bootstrapping has failed.

   - bpo-31482(49): ‘random.seed()’ now works with bytes in version=1

   - bpo-31334(50): Fix ‘poll.poll([timeout])’ in the ‘select’ module
     for arbitrary negative timeouts on all OSes where it can only be a
     non-negative integer or -1.  Patch by Riccardo Coccioli.

   - bpo-31310(51): multiprocessing's semaphore tracker should be
     launched again if crashed.

   - bpo-31308(52): Make multiprocessing's forkserver process immune to
     Ctrl-C and other user interruptions.  If it crashes, restart it
     when necessary.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28556

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27240

   (3) https://bugs.python.org/issue?@action=redirect&bpo=30788

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31831

   (5) https://bugs.python.org/issue?@action=redirect&bpo=32182

   (6) https://bugs.python.org/issue?@action=redirect&bpo=32186

   (7) https://bugs.python.org/issue?@action=redirect&bpo=12239

   (8) https://bugs.python.org/issue?@action=redirect&bpo=31325

   (9) https://bugs.python.org/issue?@action=redirect&bpo=12382

   (10) https://bugs.python.org/issue?@action=redirect&bpo=32110

   (11) https://bugs.python.org/issue?@action=redirect&bpo=32072

   (12) https://bugs.python.org/issue?@action=redirect&bpo=32034

   (13) https://bugs.python.org/issue?@action=redirect&bpo=32015

   (14) https://bugs.python.org/issue?@action=redirect&bpo=32011

   (15) https://bugs.python.org/issue?@action=redirect&bpo=31970

   (16) https://bugs.python.org/issue?@action=redirect&bpo=9678

   (17) https://bugs.python.org/issue?@action=redirect&bpo=30057

   (18) https://bugs.python.org/issue?@action=redirect&bpo=31933

   (19) https://bugs.python.org/issue?@action=redirect&bpo=31927

   (20) https://bugs.python.org/issue?@action=redirect&bpo=27666

   (21) https://bugs.python.org/issue?@action=redirect&bpo=31897

   (22) https://bugs.python.org/issue?@action=redirect&bpo=25720

   (23) https://bugs.python.org/issue?@action=redirect&bpo=31893

   (24) https://bugs.python.org/issue?@action=redirect&bpo=31891

   (25) https://bugs.python.org/issue?@action=redirect&bpo=28416

   (26) https://bugs.python.org/issue?@action=redirect&bpo=28326

   (27) https://bugs.python.org/issue?@action=redirect&bpo=31457

   (28) https://bugs.python.org/issue?@action=redirect&bpo=31457

   (29) https://bugs.python.org/issue?@action=redirect&bpo=31806

   (30) https://bugs.python.org/issue?@action=redirect&bpo=28603

   (31) https://bugs.python.org/issue?@action=redirect&bpo=30058

   (32) https://bugs.python.org/issue?@action=redirect&bpo=31770

   (33) https://bugs.python.org/issue?@action=redirect&bpo=31672

   (34) https://bugs.python.org/issue?@action=redirect&bpo=31764

   (35) https://bugs.python.org/issue?@action=redirect&bpo=31752

   (36) https://bugs.python.org/issue?@action=redirect&bpo=31701

   (37) https://bugs.python.org/issue?@action=redirect&bpo=31728

   (38) https://bugs.python.org/issue?@action=redirect&bpo=31620

   (39) https://bugs.python.org/issue?@action=redirect&bpo=31632

   (40) https://bugs.python.org/issue?@action=redirect&bpo=31675

   (41) https://bugs.python.org/issue?@action=redirect&bpo=31673

   (42) https://bugs.python.org/issue?@action=redirect&bpo=30806

   (43) https://bugs.python.org/issue?@action=redirect&bpo=15037

   (44) https://bugs.python.org/issue?@action=redirect&bpo=25351

   (45) https://bugs.python.org/issue?@action=redirect&bpo=25532

   (46) https://bugs.python.org/issue?@action=redirect&bpo=30347

   (47) https://bugs.python.org/issue?@action=redirect&bpo=31516

   (48) https://bugs.python.org/issue?@action=redirect&bpo=31351

   (49) https://bugs.python.org/issue?@action=redirect&bpo=31482

   (50) https://bugs.python.org/issue?@action=redirect&bpo=31334

   (51) https://bugs.python.org/issue?@action=redirect&bpo=31310

   (52) https://bugs.python.org/issue?@action=redirect&bpo=31308


File: python.info,  Node: Documentation<56>,  Next: Tests<57>,  Prev: Library<62>,  Up: Python 3 6 4 release candidate 1

1.23.66.3 Documentation
.......................

   - bpo-32105(1): Added asyncio.BaseEventLoop.connect_accepted_socket
     versionadded marker.

   - bpo-31537(2): Fix incorrect usage of ‘get_history_length’ in
     readline documentation example code.  Patch by Brad Smith.

   - bpo-30085(3): The operator functions without double underscores are
     preferred for clarity.  The one with underscores are only kept for
     back-compatibility.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32105

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31537

   (3) https://bugs.python.org/issue?@action=redirect&bpo=30085


File: python.info,  Node: Tests<57>,  Next: Build<60>,  Prev: Documentation<56>,  Up: Python 3 6 4 release candidate 1

1.23.66.4 Tests
...............

   - bpo-31380(1): Skip test_httpservers test_undecodable_file on macOS:
     fails on APFS.

   - bpo-31705(2): Skip test_socket.test_sha256() on Linux kernel older
     than 4.5.  The test fails with ENOKEY on kernel 3.10 (on ppc64le).
     A fix was merged into the kernel 4.5.

   - bpo-31174(3): Fix test_tools.test_unparse: DirectoryTestCase now
     stores the names sample to always test the same files.  It prevents
     false alarms when hunting reference leaks.

   - bpo-30695(4): Add the ‘set_nomemory(start, stop)’ and
     ‘remove_mem_hooks()’ functions to the ‘_testcapi’ module.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31380

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31705

   (3) https://bugs.python.org/issue?@action=redirect&bpo=31174

   (4) https://bugs.python.org/issue?@action=redirect&bpo=30695


File: python.info,  Node: Build<60>,  Next: Windows<54>,  Prev: Tests<57>,  Up: Python 3 6 4 release candidate 1

1.23.66.5 Build
...............

   - bpo-32059(1): ‘detect_modules()’ in ‘setup.py’ now also searches
     the sysroot paths when cross-compiling.

   - bpo-31957(2): Fixes Windows SDK version detection when building for
     Windows.

   - bpo-31609(3): Fixes quotes in PCbuild/clean.bat

   - bpo-31934(4): Abort the build when building out of a not clean
     source tree.

   - bpo-31926(5): Fixed Argument Clinic sometimes causing compilation
     errors when there was more than one function and/or method in a .c
     file with the same name.

   - bpo-28791(6): Update Windows builds to use SQLite 3.21.0.

   - bpo-28791(7): Update OS X installer to use SQLite 3.21.0.

   - bpo-22140(8): Prevent double substitution of prefix in
     python-config.sh.

   - bpo-31536(9): Avoid wholesale rebuild after ‘make regen-all’ if
     nothing changed.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32059

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31957

   (3) https://bugs.python.org/issue?@action=redirect&bpo=31609

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31934

   (5) https://bugs.python.org/issue?@action=redirect&bpo=31926

   (6) https://bugs.python.org/issue?@action=redirect&bpo=28791

   (7) https://bugs.python.org/issue?@action=redirect&bpo=28791

   (8) https://bugs.python.org/issue?@action=redirect&bpo=22140

   (9) https://bugs.python.org/issue?@action=redirect&bpo=31536


File: python.info,  Node: Windows<54>,  Next: macOS<44>,  Prev: Build<60>,  Up: Python 3 6 4 release candidate 1

1.23.66.6 Windows
.................

   - bpo-1102(1): Return ‘None’ when ‘View.Fetch()’ returns
     ‘ERROR_NO_MORE_ITEMS’ instead of raising ‘MSIError’.  Initial patch
     by Anthony Tuininga.

   - bpo-31944(2): Fixes Modify button in Apps and Features dialog.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=1102

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31944


File: python.info,  Node: macOS<44>,  Next: IDLE<46>,  Prev: Windows<54>,  Up: Python 3 6 4 release candidate 1

1.23.66.7 macOS
...............

   - bpo-31392(1): Update macOS installer to use OpenSSL 1.0.2m

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31392


File: python.info,  Node: IDLE<46>,  Next: Tools/Demos<32>,  Prev: macOS<44>,  Up: Python 3 6 4 release candidate 1

1.23.66.8 IDLE
..............

   - bpo-32207(1): Improve tk event exception tracebacks in IDLE. When
     tk event handling is driven by IDLE's run loop, a confusing and
     distracting queue.EMPTY traceback context is no longer added to tk
     event exception tracebacks.  The traceback is now the same as when
     event handling is driven by user code.  Patch based on a suggestion
     by Serhiy Storchaka.

   - bpo-32164(2): Delete unused file idlelib/tabbedpages.py.  Use of
     TabbedPageSet in configdialog was replaced by ttk.Notebook.

   - bpo-32100(3): IDLE: Fix old and new bugs in pathbrowser; improve
     tests.  Patch mostly by Cheryl Sabella.

   - bpo-31858(4): IDLE - Restrict shell prompt manipulation to the
     shell.  Editor and output windows only see an empty last prompt
     line.  This simplifies the code and fixes a minor bug when newline
     is inserted.  Sys.ps1, if present, is read on Shell start-up, but
     is not set or changed.

   - bpo-31860(5): The font sample in the IDLE configuration dialog is
     now editable.  Changes persist while IDLE remains open

   - bpo-31836(6): Test_code_module now passes if run after test_idle,
     which sets ps1.  The code module uses sys.ps1 if present or sets it
     to '>>> ' if not.  Test_code_module now properly tests both
     behaviors.  Ditto for ps2.

   - bpo-28603(7): Fix a TypeError that caused a shell restart when
     printing a traceback that includes an exception that is unhashable.
     Patch by Zane Bitter.

   - bpo-13802(8): Use non-Latin characters in the IDLE's Font settings
     sample.  Even if one selects a font that defines a limited subset
     of the unicode Basic Multilingual Plane, tcl/tk will use other
     fonts that define a character.  The expanded example give users of
     non-Latin characters a better idea of what they might see in IDLE's
     shell and editors.  To make room for the expanded sample, frames on
     the Font tab are re-arranged.  The Font/Tabs help explains a bit
     about the additions.

   - bpo-31460(9): Simplify the API of IDLE's Module Browser.  Passing a
     widget instead of an flist with a root widget opens the option of
     creating a browser frame that is only part of a window.  Passing a
     full file name instead of pieces assumed to come from a .py file
     opens the possibility of browsing python files that do not end in
     .py.

   - bpo-31649(10): IDLE - Make _htest, _utest parameters keyword only.

   - bpo-31559(11): Remove test order dependence in
     idle_test.test_browser.

   - bpo-31459(12): Rename IDLE's module browser from Class Browser to
     Module Browser.  The original module-level class and method browser
     became a module browser, with the addition of module-level
     functions, years ago.  Nested classes and functions were added
     yesterday.  For back-compatibility, the virtual event
     <<open-class-browser>>, which appears on the Keys tab of the
     Settings dialog, is not changed.  Patch by Cheryl Sabella.

   - bpo-31500(13): Default fonts now are scaled on HiDPI displays.

   - bpo-1612262(14): IDLE module browser now shows nested classes and
     functions.  Original patches for code and tests by Guilherme Polo
     and Cheryl Sabella, respectively.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32207

   (2) https://bugs.python.org/issue?@action=redirect&bpo=32164

   (3) https://bugs.python.org/issue?@action=redirect&bpo=32100

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31858

   (5) https://bugs.python.org/issue?@action=redirect&bpo=31860

   (6) https://bugs.python.org/issue?@action=redirect&bpo=31836

   (7) https://bugs.python.org/issue?@action=redirect&bpo=28603

   (8) https://bugs.python.org/issue?@action=redirect&bpo=13802

   (9) https://bugs.python.org/issue?@action=redirect&bpo=31460

   (10) https://bugs.python.org/issue?@action=redirect&bpo=31649

   (11) https://bugs.python.org/issue?@action=redirect&bpo=31559

   (12) https://bugs.python.org/issue?@action=redirect&bpo=31459

   (13) https://bugs.python.org/issue?@action=redirect&bpo=31500

   (14) https://bugs.python.org/issue?@action=redirect&bpo=1612262


File: python.info,  Node: Tools/Demos<32>,  Next: C API<56>,  Prev: IDLE<46>,  Up: Python 3 6 4 release candidate 1

1.23.66.9 Tools/Demos
.....................

   - bpo-30722(1): Make redemo work with Python 3.6 and newer versions.
     Also, remove the ‘LOCALE’ option since it doesn't work with string
     patterns in Python 3.  Patch by Christoph Sarnowski.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30722


File: python.info,  Node: C API<56>,  Prev: Tools/Demos<32>,  Up: Python 3 6 4 release candidate 1

1.23.66.10 C API
................

   - bpo-20891(1): Fix PyGILState_Ensure().  When PyGILState_Ensure() is
     called in a non-Python thread before PyEval_InitThreads(), only
     call PyEval_InitThreads() after calling PyThreadState_New() to fix
     a crash.

   - bpo-31532(2): Fix memory corruption due to allocator mix in
     getpath.c between Py_GetPath() and Py_SetPath()

   - bpo-30697(3): The ‘PyExc_RecursionErrorInst’ singleton is removed
     and ‘PyErr_NormalizeException()’ does not use it anymore.  This
     singleton is persistent and its members being never cleared may
     cause a segfault during finalization of the interpreter.  See also
     bpo-22898(4).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=20891

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31532

   (3) https://bugs.python.org/issue?@action=redirect&bpo=30697

   (4) https://bugs.python.org/issue?@action=redirect&bpo=22898


File: python.info,  Node: Python 3 6 3 final,  Next: Python 3 6 3 release candidate 1,  Prev: Python 3 6 4 release candidate 1,  Up: Changelog（更動日誌）

1.23.67 Python 3.6.3 final
--------------------------

'Release date: 2017-10-03'

* Menu:

* Library: Library<63>.
* Build: Build<61>.


File: python.info,  Node: Library<63>,  Next: Build<61>,  Up: Python 3 6 3 final

1.23.67.1 Library
.................

   - bpo-31641(1): Re-allow arbitrary iterables in
     ‘concurrent.futures.as_completed()’.  Fixes regression in 3.6.3rc1.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31641


File: python.info,  Node: Build<61>,  Prev: Library<63>,  Up: Python 3 6 3 final

1.23.67.2 Build
...............

   - bpo-31662(1): Fix typos in Windows ‘uploadrelease.bat’ script.  Fix
     Windows Doc build issues in ‘Doc/make.bat’.

   - bpo-31423(2): Fix building the PDF documentation with newer
     versions of Sphinx.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31662

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31423


File: python.info,  Node: Python 3 6 3 release candidate 1,  Next: Python 3 6 2 final,  Prev: Python 3 6 3 final,  Up: Changelog（更動日誌）

1.23.68 Python 3.6.3 release candidate 1
----------------------------------------

'Release date: 2017-09-18'

* Menu:

* Security: Security<38>.
* Core and Builtins: Core and Builtins<63>.
* Library: Library<64>.
* Documentation: Documentation<57>.
* Tests: Tests<58>.
* Build: Build<62>.
* Windows: Windows<55>.
* IDLE: IDLE<47>.
* Tools/Demos: Tools/Demos<33>.


File: python.info,  Node: Security<38>,  Next: Core and Builtins<63>,  Up: Python 3 6 3 release candidate 1

1.23.68.1 Security
..................

   - bpo-29781(1): SSLObject.version() now correctly returns None when
     handshake over BIO has not been performed yet.

   - bpo-30947(2): Upgrade libexpat embedded copy from version 2.2.1 to
     2.2.3 to get security fixes.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29781

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30947


File: python.info,  Node: Core and Builtins<63>,  Next: Library<64>,  Prev: Security<38>,  Up: Python 3 6 3 release candidate 1

1.23.68.2 Core and Builtins
...........................

   - bpo-31471(1): Fix an assertion failure in ‘subprocess.Popen()’ on
     Windows, in case the env argument has a bad ‘keys()’ method.  Patch
     by Oren Milman.

   - bpo-31418(2): Fix an assertion failure in ‘PyErr_WriteUnraisable()’
     in case of an exception with a bad ‘__module__’ attribute.  Patch
     by Oren Milman.

   - bpo-31416(3): Fix assertion failures in case of a bad
     warnings.filters or warnings.defaultaction.  Patch by Oren Milman.

   - bpo-31411(4): Raise a TypeError instead of SystemError in case
     warnings.onceregistry is not a dictionary.  Patch by Oren Milman.

   - bpo-31373(5): Fix several possible instances of undefined behavior
     due to floating-point demotions.

   - bpo-30465(6): Location information (‘lineno’ and ‘col_offset’) in
     f-strings is now (mostly) correct.  This fixes tools like flake8
     from showing warnings on the wrong line (typically the first line
     of the file).

   - bpo-31343(7): Include sys/sysmacros.h for major(), minor(), and
     makedev().  GNU C libray plans to remove the functions from
     sys/types.h.

   - bpo-31291(8): Fix an assertion failure in
     ‘zipimport.zipimporter.get_data’ on Windows, when the return value
     of ‘pathname.replace('/','\\')’ isn't a string.  Patch by Oren
     Milman.

   - bpo-31271(9): Fix an assertion failure in the ‘write()’ method of
     ‘io.TextIOWrapper’, when the encoder doesn't return a bytes object.
     Patch by Oren Milman.

   - bpo-31243(10): Fix a crash in some methods of ‘io.TextIOWrapper’,
     when the decoder's state is invalid.  Patch by Oren Milman.

   - bpo-30721(11): ‘print’ now shows correct usage hint for using
     Python 2 redirection syntax.  Patch by Sanyam Khurana.

   - bpo-31070(12): Fix a race condition in importlib
     _get_module_lock().

   - bpo-31095(13): Fix potential crash during GC caused by ‘tp_dealloc’
     which doesn't call ‘PyObject_GC_UnTrack()’.

   - bpo-31071(14): Avoid masking original TypeError in call with *
     unpacking when other arguments are passed.

   - bpo-30978(15): str.format_map() now passes key lookup exceptions
     through.  Previously any exception was replaced with a KeyError
     exception.

   - bpo-30808(16): Use _Py_atomic API for concurrency-sensitive signal
     state.

   - bpo-30876(17): Relative import from unloaded package now reimports
     the package instead of failing with SystemError.  Relative import
     from non-package now fails with ImportError rather than
     SystemError.

   - bpo-30703(18): Improve signal delivery.  Avoid using
     Py_AddPendingCall from signal handler, to avoid calling
     signal-unsafe functions.  The tests I'm adding here fail without
     the rest of the patch, on Linux and OS X. This means our signal
     delivery logic had defects (some signals could be lost).

   - bpo-30765(19): Avoid blocking in pthread_mutex_lock() when
     PyThread_acquire_lock() is asked not to block.

   - bpo-31161(20): Make sure the 'Missing parentheses' syntax error
     message is only applied to SyntaxError, not to subclasses.  Patch
     by Martijn Pieters.

   - bpo-30814(21): Fixed a race condition when import a submodule from
     a package.

   - bpo-30597(22): ‘print’ now shows expected input in custom error
     message when used as a Python 2 statement.  Patch by Sanyam
     Khurana.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31471

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31418

   (3) https://bugs.python.org/issue?@action=redirect&bpo=31416

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31411

   (5) https://bugs.python.org/issue?@action=redirect&bpo=31373

   (6) https://bugs.python.org/issue?@action=redirect&bpo=30465

   (7) https://bugs.python.org/issue?@action=redirect&bpo=31343

   (8) https://bugs.python.org/issue?@action=redirect&bpo=31291

   (9) https://bugs.python.org/issue?@action=redirect&bpo=31271

   (10) https://bugs.python.org/issue?@action=redirect&bpo=31243

   (11) https://bugs.python.org/issue?@action=redirect&bpo=30721

   (12) https://bugs.python.org/issue?@action=redirect&bpo=31070

   (13) https://bugs.python.org/issue?@action=redirect&bpo=31095

   (14) https://bugs.python.org/issue?@action=redirect&bpo=31071

   (15) https://bugs.python.org/issue?@action=redirect&bpo=30978

   (16) https://bugs.python.org/issue?@action=redirect&bpo=30808

   (17) https://bugs.python.org/issue?@action=redirect&bpo=30876

   (18) https://bugs.python.org/issue?@action=redirect&bpo=30703

   (19) https://bugs.python.org/issue?@action=redirect&bpo=30765

   (20) https://bugs.python.org/issue?@action=redirect&bpo=31161

   (21) https://bugs.python.org/issue?@action=redirect&bpo=30814

   (22) https://bugs.python.org/issue?@action=redirect&bpo=30597


File: python.info,  Node: Library<64>,  Next: Documentation<57>,  Prev: Core and Builtins<63>,  Up: Python 3 6 3 release candidate 1

1.23.68.3 Library
.................

   - bpo-31499(1): xml.etree: Fix a crash when a parser is part of a
     reference cycle.

   - bpo-28556(2): typing.get_type_hints now finds the right globalns
     for classes and modules by default (when no ‘globalns’ was
     specified by the caller).

   - bpo-28556(3): Speed improvements to the ‘typing’ module.  Original
     PRs by Ivan Levkivskyi and Mitar.

   - bpo-31544(4): The C accelerator module of ElementTree ignored
     exceptions raised when looking up TreeBuilder target methods in
     XMLParser().

   - bpo-31234(5): socket.create_connection() now fixes manually a
     reference cycle: clear the variable storing the last exception on
     success.

   - bpo-31457(6): LoggerAdapter objects can now be nested.

   - bpo-31400(7): Improves SSL error handling to avoid losing error
     numbers.

   - bpo-28958(8): ssl.SSLContext() now uses OpenSSL error information
     when a context cannot be instantiated.

   - bpo-27340(9): SSLSocket.sendall() now uses memoryview to create
     slices of data.  This fixes support for all bytes-like object.  It
     is also more efficient and avoids costly copies.

   - bpo-31178(10): Fix string concatenation bug in rare error path in
     the subprocess module

   - bpo-31350(11): Micro-optimize ‘asyncio._get_running_loop()’ to
     become up to 10% faster.

   - bpo-31170(12): expat: Update libexpat from 2.2.3 to 2.2.4.  Fix
     copying of partial characters for UTF-8 input (libexpat bug 115):
     ‘https://github.com/libexpat/libexpat/issues/115’

   - bpo-29136(13): Add TLS 1.3 cipher suites and OP_NO_TLSv1_3.

   - bpo-29212(14): Fix concurrent.futures.thread.ThreadPoolExecutor
     threads to have a non repr() based thread name by default when no
     thread_name_prefix is supplied.  They will now identify themselves
     as "ThreadPoolExecutor-y_n".

   - bpo-9146(15): Fix a segmentation fault in _hashopenssl when
     standard hash functions such as md5 are not available in the linked
     OpenSSL library.  As in some special FIPS-140 build environments.

   - bpo-27144(16): The ‘map()’ and ‘as_completed()’ iterators in
     ‘concurrent.futures’ now avoid keeping a reference to yielded
     objects.

   - bpo-10746(17): Fix ctypes producing wrong PEP 3118(18) type codes
     for integer types.

   - bpo-22536(19): The subprocess module now sets the filename when
     FileNotFoundError is raised on POSIX systems due to the executable
     or cwd not being found.

   - bpo-31249(20): concurrent.futures: WorkItem.run() used by
     ThreadPoolExecutor now breaks a reference cycle between an
     exception object and the WorkItem object.

   - bpo-31247(21): xmlrpc.server now explicitly breaks reference cycles
     when using sys.exc_info() in code handling exceptions.

   - bpo-30102(22): The ssl and hashlib modules now call
     OPENSSL_add_all_algorithms_noconf() on OpenSSL < 1.1.0.  The
     function detects CPU features and enables optimizations on some CPU
     architectures such as POWER8.  Patch is based on research from
     Gustavo Serra Scalet.

   - bpo-31185(23): Fixed miscellaneous errors in asyncio speedup
     module.

   - bpo-31135(24): ttk: fix the destroy() method of LabeledScale and
     OptionMenu classes.  Call the parent destroy() method even if the
     used attribute doesn't exist.  The LabeledScale.destroy() method
     now also explicitly clears label and scale attributes to help the
     garbage collector to destroy all widgets.

   - bpo-31107(25): Fix ‘copyreg._slotnames()’ mangled attribute
     calculation for classes whose name begins with an underscore.
     Patch by Shane Harvey.

   - bpo-31061(26): Fixed a crash when using asyncio and threads.

   - bpo-30502(27): Fix handling of long oids in ssl.  Based on patch by
     Christian Heimes.

   - bpo-30119(28): ftplib.FTP.putline() now throws ValueError on
     commands that contains CR or LF. Patch by Donghee Na.

   - bpo-30595(29): multiprocessing.Queue.get() with a timeout now polls
     its reader in non-blocking mode if it succeeded to acquire the lock
     but the acquire took longer than the timeout.

   - bpo-29403(30): Fix ‘unittest.mock’'s autospec to not fail on
     method-bound builtin functions.  Patch by Aaron Gallagher.

   - bpo-30961(31): Fix decrementing a borrowed reference in
     tracemalloc.

   - bpo-25684(32): Change ‘ttk.OptionMenu’ radiobuttons to be unique
     across instances of ‘OptionMenu’.

   - bpo-30886(33): Fix multiprocessing.Queue.join_thread(): it now
     waits until the thread completes, even if the thread was started by
     the same process which created the queue.

   - bpo-29854(34): Fix segfault in readline when using readline's
     history-size option.  Patch by Nir Soffer.

   - bpo-30319(35): socket.close() now ignores ECONNRESET error.

   - bpo-30828(36): Fix out of bounds write in
     ‘asyncio.CFuture.remove_done_callback()’.

   - bpo-30807(37): signal.setitimer() may disable the timer when passed
     a tiny value.  Tiny values (such as 1e-6) are valid non-zero values
     for setitimer(), which is specified as taking
     microsecond-resolution intervals.  However, on some platform, our
     conversion routine could convert 1e-6 into a zero interval,
     therefore disabling the timer instead of (re-)scheduling it.

   - bpo-30441(38): Fix bug when modifying os.environ while iterating
     over it

   - bpo-30532(39): Fix email header value parser dropping folding white
     space in certain cases.

   - bpo-30879(40): os.listdir() and os.scandir() now emit bytes names
     when called with bytes-like argument.

   - bpo-30746(41): Prohibited the '=' character in environment variable
     names in ‘os.putenv()’ and ‘os.spawn*()’.

   - bpo-29755(42): Fixed the lgettext() family of functions in the
     gettext module.  They now always return bytes.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31499

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28556

   (3) https://bugs.python.org/issue?@action=redirect&bpo=28556

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31544

   (5) https://bugs.python.org/issue?@action=redirect&bpo=31234

   (6) https://bugs.python.org/issue?@action=redirect&bpo=31457

   (7) https://bugs.python.org/issue?@action=redirect&bpo=31400

   (8) https://bugs.python.org/issue?@action=redirect&bpo=28958

   (9) https://bugs.python.org/issue?@action=redirect&bpo=27340

   (10) https://bugs.python.org/issue?@action=redirect&bpo=31178

   (11) https://bugs.python.org/issue?@action=redirect&bpo=31350

   (12) https://bugs.python.org/issue?@action=redirect&bpo=31170

   (13) https://bugs.python.org/issue?@action=redirect&bpo=29136

   (14) https://bugs.python.org/issue?@action=redirect&bpo=29212

   (15) https://bugs.python.org/issue?@action=redirect&bpo=9146

   (16) https://bugs.python.org/issue?@action=redirect&bpo=27144

   (17) https://bugs.python.org/issue?@action=redirect&bpo=10746

   (18) https://peps.python.org/pep-3118/

   (19) https://bugs.python.org/issue?@action=redirect&bpo=22536

   (20) https://bugs.python.org/issue?@action=redirect&bpo=31249

   (21) https://bugs.python.org/issue?@action=redirect&bpo=31247

   (22) https://bugs.python.org/issue?@action=redirect&bpo=30102

   (23) https://bugs.python.org/issue?@action=redirect&bpo=31185

   (24) https://bugs.python.org/issue?@action=redirect&bpo=31135

   (25) https://bugs.python.org/issue?@action=redirect&bpo=31107

   (26) https://bugs.python.org/issue?@action=redirect&bpo=31061

   (27) https://bugs.python.org/issue?@action=redirect&bpo=30502

   (28) https://bugs.python.org/issue?@action=redirect&bpo=30119

   (29) https://bugs.python.org/issue?@action=redirect&bpo=30595

   (30) https://bugs.python.org/issue?@action=redirect&bpo=29403

   (31) https://bugs.python.org/issue?@action=redirect&bpo=30961

   (32) https://bugs.python.org/issue?@action=redirect&bpo=25684

   (33) https://bugs.python.org/issue?@action=redirect&bpo=30886

   (34) https://bugs.python.org/issue?@action=redirect&bpo=29854

   (35) https://bugs.python.org/issue?@action=redirect&bpo=30319

   (36) https://bugs.python.org/issue?@action=redirect&bpo=30828

   (37) https://bugs.python.org/issue?@action=redirect&bpo=30807

   (38) https://bugs.python.org/issue?@action=redirect&bpo=30441

   (39) https://bugs.python.org/issue?@action=redirect&bpo=30532

   (40) https://bugs.python.org/issue?@action=redirect&bpo=30879

   (41) https://bugs.python.org/issue?@action=redirect&bpo=30746

   (42) https://bugs.python.org/issue?@action=redirect&bpo=29755


File: python.info,  Node: Documentation<57>,  Next: Tests<58>,  Prev: Library<64>,  Up: Python 3 6 3 release candidate 1

1.23.68.4 Documentation
.......................

   - bpo-31294(1): Fix incomplete code snippet in the
     ZeroMQSocketListener and ZeroMQSocketHandler examples and adapt
     them to Python 3.

   - bpo-21649(2): Add RFC 7525 and Mozilla server side TLS links to SSL
     documentation.

   - bpo-30803(3): Clarify doc on truth value testing.  Original patch
     by Peter Thomassen.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31294

   (2) https://bugs.python.org/issue?@action=redirect&bpo=21649

   (3) https://bugs.python.org/issue?@action=redirect&bpo=30803


File: python.info,  Node: Tests<58>,  Next: Build<62>,  Prev: Documentation<57>,  Up: Python 3 6 3 release candidate 1

1.23.68.5 Tests
...............

   - bpo-31320(1): Silence traceback in test_ssl

   - bpo-25674(2): Remove sha256.tbs-internet.com ssl test

   - bpo-30715(3): Address ALPN callback changes for OpenSSL 1.1.0f.
     The latest version behaves like OpenSSL 1.0.2 and no longer aborts
     handshake.

   - bpo-30822(4): regrtest: Exclude tzdata from regrtest -all.  When
     running the test suite using -use=all / -u all, exclude tzdata
     since it makes test_datetime too slow (15-20 min on some buildbots)
     which then times out on some buildbots.  Fix also regrtest command
     line parser to allow passing -u extralargefile to run
     test_zipfile64.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31320

   (2) https://bugs.python.org/issue?@action=redirect&bpo=25674

   (3) https://bugs.python.org/issue?@action=redirect&bpo=30715

   (4) https://bugs.python.org/issue?@action=redirect&bpo=30822


File: python.info,  Node: Build<62>,  Next: Windows<55>,  Prev: Tests<58>,  Up: Python 3 6 3 release candidate 1

1.23.68.6 Build
...............

   - bpo-30854(1): Fix compile error when compiling -without-threads.
     Patch by Masayuki Yamamoto.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30854


File: python.info,  Node: Windows<55>,  Next: IDLE<47>,  Prev: Build<62>,  Up: Python 3 6 3 release candidate 1

1.23.68.7 Windows
.................

   - bpo-30389(1): Adds detection of Visual Studio 2017 to distutils on
     Windows.

   - bpo-31340(2): Change to building with MSVC v141 (included with
     Visual Studio 2017)

   - bpo-30581(3): os.cpu_count() now returns the correct number of
     processors on Windows when the number of logical processors is
     greater than 64.

   - bpo-30731(4): Add a missing xmlns to python.manifest so that it
     matches the schema.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30389

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31340

   (3) https://bugs.python.org/issue?@action=redirect&bpo=30581

   (4) https://bugs.python.org/issue?@action=redirect&bpo=30731


File: python.info,  Node: IDLE<47>,  Next: Tools/Demos<33>,  Prev: Windows<55>,  Up: Python 3 6 3 release candidate 1

1.23.68.8 IDLE
..............

   - bpo-31493(1): IDLE code context - fix code update and font update
     timers.  Canceling timers prevents a warning message when test_idle
     completes.

   - bpo-31488(2): IDLE - Update non-key options in former extension
     classes.  When applying configdialog changes, call .reload for each
     feature class.  Change ParenMatch so updated options affect
     existing instances attached to existing editor windows.

   - bpo-31477(3): IDLE - Improve rstrip entry in doc.  Strip trailing
     whitespace strips more than blank spaces.  Multiline string
     literals are not skipped.

   - bpo-31480(4): IDLE - make tests pass with zzdummy extension
     disabled by default.

   - bpo-31421(5): Document how IDLE runs tkinter programs.  IDLE calls
     tcl/tk update in the background in order to make live interaction
     and experimentation with tkinter applications much easier.

   - bpo-31414(6): IDLE - fix tk entry box tests by deleting first.
     Adding to an int entry is not the same as deleting and inserting
     because int('') will fail.

   - bpo-31051(7): Rearrange IDLE configdialog GenPage into Window,
     Editor, and Help sections.

   - bpo-30617(8): IDLE - Add docstrings and tests for outwin subclass
     of editor.  Move some data and functions from the class to module
     level.  Patch by Cheryl Sabella.

   - bpo-31287(9): IDLE - Do not modify tkinter.message in
     test_configdialog.

   - bpo-27099(10): Convert IDLE's built-in 'extensions' to regular
     features.  About 10 IDLE features were implemented as supposedly
     optional extensions.  Their different behavior could be confusing
     or worse for users and not good for maintenance.  Hence the
     conversion.  The main difference for users is that user
     configurable key bindings for builtin features are now handled
     uniformly.  Now, editing a binding in a keyset only affects its
     value in the keyset.  All bindings are defined together in the
     system-specific default keysets in config-extensions.def.  All
     custom keysets are saved as a whole in config-extension.cfg.  All
     take effect as soon as one clicks Apply or Ok.  The affected events
     are '<<force-open-completions>>', '<<expand-word>>',
     '<<force-open-calltip>>', '<<flash-paren>>',
     '<<format-paragraph>>', '<<run-module>>', '<<check-module>>', and
     '<<zoom-height>>'.  Any (global) customizations made before 3.6.3
     will not affect their keyset-specific customization after 3.6.3.
     and vice versa.  Initial patch by Charles Wohlganger.

   - bpo-31206(11): IDLE: Factor HighPage(Frame) class from
     ConfigDialog.  Patch by Cheryl Sabella.

   - bpo-31001(12): Add tests for configdialog highlight tab.  Patch by
     Cheryl Sabella.

   - bpo-31205(13): IDLE: Factor KeysPage(Frame) class from
     ConfigDialog.  The slightly modified tests continue to pass.  Patch
     by Cheryl Sabella.

   - bpo-31130(14): IDLE - stop leaks in test_configdialog.  Initial
     patch by Victor Stinner.

   - bpo-31002(15): Add tests for configdialog keys tab.  Patch by
     Cheryl Sabella.

   - bpo-19903(16): IDLE: Calltips use ‘inspect.signature’ instead of
     ‘inspect.getfullargspec’.  This improves calltips for builtins
     converted to use Argument Clinic.  Patch by Louie Lu.

   - bpo-31083(17): IDLE - Add an outline of a TabPage class in
     configdialog.  Update existing classes to match outline.  Initial
     patch by Cheryl Sabella.

   - bpo-31050(18): Factor GenPage(Frame) class from ConfigDialog.  The
     slightly modified tests continue to pass.  Patch by Cheryl Sabella.

   - bpo-31004(19): IDLE - Factor FontPage(Frame) class from
     ConfigDialog.  Slightly modified tests continue to pass.  Fix
     General tests.  Patch mostly by Cheryl Sabella.

   - bpo-30781(20): IDLE - Use ttk widgets in ConfigDialog.  Patches by
     Terry Jan Reedy and Cheryl Sabella.

   - bpo-31060(21): IDLE - Finish rearranging methods of ConfigDialog
     Grouping methods pertaining to each tab and the buttons will aid
     writing tests and improving the tabs and will enable splitting the
     groups into classes.

   - bpo-30853(22): IDLE - Factor a VarTrace class out of ConfigDialog.
     Instance tracers manages pairs consisting of a tk variable and a
     callback function.  When tracing is turned on, setting the variable
     calls the function.  Test coverage for the new class is 100%.

   - bpo-31003(23): IDLE: Add more tests for General tab.

   - bpo-30993(24): IDLE - Improve configdialog font page and tests.  In
     configdialog: Document causal pathways in create_font_tab
     docstring.  Simplify some attribute names.  Move set_samples calls
     to var_changed_font (idea from Cheryl Sabella).  Move related
     functions to positions after the create widgets function.  In
     test_configdialog: Fix test_font_set so not order dependent.  Fix
     renamed test_indent_scale so it tests the widget.  Adjust tests for
     movement of set_samples call.  Add tests for load functions.  Put
     all font tests in one class and tab indent tests in another.
     Except for two lines, these tests completely cover the related
     functions.

   - bpo-30981(25): IDLE - Add more configdialog font page tests.

   - bpo-28523(26): IDLE: replace 'colour' with 'color' in configdialog.

   - bpo-30917(27): Add tests for idlelib.config.IdleConf.  Increase
     coverage from 46% to 96%.  Patch by Louie Lu.

   - bpo-30934(28): Document coverage details for idlelib tests.  Add
     section to idlelib/idle-test/README.txt.  Include check that
     branches are taken both ways.  Exclude IDLE-specific code that does
     not run during unit tests.

   - bpo-30913(29): IDLE: Document ConfigDialog tk Vars, methods, and
     widgets in docstrings This will facilitate improving the dialog and
     splitting up the class.  Original patch by Cheryl Sabella.

   - bpo-30899(30): IDLE: Add tests for ConfigParser subclasses in
     config.  Patch by Louie Lu.

   - bpo-30881(31): IDLE: Add docstrings to browser.py.  Patch by Cheryl
     Sabella.

   - bpo-30851(32): IDLE: Remove unused variables in configdialog.  One
     is a duplicate, one is set but cannot be altered by users.  Patch
     by Cheryl Sabella.

   - bpo-30870(33): IDLE: In Settings dialog, select font with Up, Down
     keys as well as mouse.  Initial patch by Louie Lu.

   - bpo-8231(34): IDLE: call config.IdleConf.GetUserCfgDir only once.

   - bpo-30779(35): IDLE: Factor ConfigChanges class from configdialog,
     put in config; test.  * In config, put dump test code in a
     function; run it and unittest in 'if __name__ == '__main__'.  * Add
     class config.ConfigChanges based on changes_class_v4.py on bpo
     issue.  * Add class test_config.ChangesTest, partly using
     configdialog_tests_v1.py.  * Revise configdialog to use
     ConfigChanges; see tracker msg297804.  * Revise test_configdialog
     to match configdialog changes.  * Remove configdialog functions
     unused or moved to ConfigChanges.  Cheryl Sabella contributed parts
     of the patch.

   - bpo-30777(36): IDLE: configdialog - Add docstrings and fix
     comments.  Patch by Cheryl Sabella.

   - bpo-30495(37): IDLE: Improve textview with docstrings, PEP8 names,
     and more tests.  Patch by Cheryl Sabella.

   - bpo-30723(38): IDLE: Make several improvements to parenmatch.  Add
     'parens' style to highlight both opener and closer.  Make 'default'
     style, which is not default, a synonym for 'opener'.  Make
     time-delay work the same with all styles.  Add help for config
     dialog extensions tab, including help for parenmatch.  Add new
     tests.  Original patch by Charles Wohlganger.

   - bpo-30674(39): IDLE: add docstrings to grep module.  Patch by
     Cheryl Sabella

   - bpo-21519(40): IDLE's basic custom key entry dialog now detects
     duplicates properly.  Original patch by Saimadhav Heblikar.

   - bpo-29910(41): IDLE no longer deletes a character after commenting
     out a region by a key shortcut.  Add ‘return 'break'’ for this and
     other potential conflicts between IDLE and default key bindings.

   - bpo-30728(42): Review and change idlelib.configdialog names.
     Lowercase method and attribute names.  Replace 'colour' with
     'color', expand overly cryptic names, delete unneeded underscores.
     Replace ‘import *’ with specific imports.  Patches by Cheryl
     Sabella.

   - bpo-6739(43): IDLE: Verify user-entered key sequences by trying to
     bind them with tk.  Add tests for all 3 validation functions.
     Original patch by G Polo.  Tests added by Cheryl Sabella.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31493

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31488

   (3) https://bugs.python.org/issue?@action=redirect&bpo=31477

   (4) https://bugs.python.org/issue?@action=redirect&bpo=31480

   (5) https://bugs.python.org/issue?@action=redirect&bpo=31421

   (6) https://bugs.python.org/issue?@action=redirect&bpo=31414

   (7) https://bugs.python.org/issue?@action=redirect&bpo=31051

   (8) https://bugs.python.org/issue?@action=redirect&bpo=30617

   (9) https://bugs.python.org/issue?@action=redirect&bpo=31287

   (10) https://bugs.python.org/issue?@action=redirect&bpo=27099

   (11) https://bugs.python.org/issue?@action=redirect&bpo=31206

   (12) https://bugs.python.org/issue?@action=redirect&bpo=31001

   (13) https://bugs.python.org/issue?@action=redirect&bpo=31205

   (14) https://bugs.python.org/issue?@action=redirect&bpo=31130

   (15) https://bugs.python.org/issue?@action=redirect&bpo=31002

   (16) https://bugs.python.org/issue?@action=redirect&bpo=19903

   (17) https://bugs.python.org/issue?@action=redirect&bpo=31083

   (18) https://bugs.python.org/issue?@action=redirect&bpo=31050

   (19) https://bugs.python.org/issue?@action=redirect&bpo=31004

   (20) https://bugs.python.org/issue?@action=redirect&bpo=30781

   (21) https://bugs.python.org/issue?@action=redirect&bpo=31060

   (22) https://bugs.python.org/issue?@action=redirect&bpo=30853

   (23) https://bugs.python.org/issue?@action=redirect&bpo=31003

   (24) https://bugs.python.org/issue?@action=redirect&bpo=30993

   (25) https://bugs.python.org/issue?@action=redirect&bpo=30981

   (26) https://bugs.python.org/issue?@action=redirect&bpo=28523

   (27) https://bugs.python.org/issue?@action=redirect&bpo=30917

   (28) https://bugs.python.org/issue?@action=redirect&bpo=30934

   (29) https://bugs.python.org/issue?@action=redirect&bpo=30913

   (30) https://bugs.python.org/issue?@action=redirect&bpo=30899

   (31) https://bugs.python.org/issue?@action=redirect&bpo=30881

   (32) https://bugs.python.org/issue?@action=redirect&bpo=30851

   (33) https://bugs.python.org/issue?@action=redirect&bpo=30870

   (34) https://bugs.python.org/issue?@action=redirect&bpo=8231

   (35) https://bugs.python.org/issue?@action=redirect&bpo=30779

   (36) https://bugs.python.org/issue?@action=redirect&bpo=30777

   (37) https://bugs.python.org/issue?@action=redirect&bpo=30495

   (38) https://bugs.python.org/issue?@action=redirect&bpo=30723

   (39) https://bugs.python.org/issue?@action=redirect&bpo=30674

   (40) https://bugs.python.org/issue?@action=redirect&bpo=21519

   (41) https://bugs.python.org/issue?@action=redirect&bpo=29910

   (42) https://bugs.python.org/issue?@action=redirect&bpo=30728

   (43) https://bugs.python.org/issue?@action=redirect&bpo=6739


File: python.info,  Node: Tools/Demos<33>,  Prev: IDLE<47>,  Up: Python 3 6 3 release candidate 1

1.23.68.9 Tools/Demos
.....................

   - bpo-30983(1): gdb integration commands (py-bt, etc.)  work on
     optimized shared builds now, too.  PEP 523(2) introduced
     _PyEval_EvalFrameDefault which inlines PyEval_EvalFrameEx on
     non-debug shared builds.  This broke the ability to use py-bt,
     py-up, and a few other Python-specific gdb integrations.  The
     problem is fixed by only looking for _PyEval_EvalFrameDefault
     frames in python-gdb.py.  Original patch by Bruno "Polaco"
     Penteado.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30983

   (2) https://peps.python.org/pep-0523/


File: python.info,  Node: Python 3 6 2 final,  Next: Python 3 6 2 release candidate 2,  Prev: Python 3 6 3 release candidate 1,  Up: Changelog（更動日誌）

1.23.69 Python 3.6.2 final
--------------------------

'Release date: 2017-07-17'

No changes since release candidate 2


File: python.info,  Node: Python 3 6 2 release candidate 2,  Next: Python 3 6 2 release candidate 1,  Prev: Python 3 6 2 final,  Up: Changelog（更動日誌）

1.23.70 Python 3.6.2 release candidate 2
----------------------------------------

'Release date: 2017-07-07'

* Menu:

* Security: Security<39>.


File: python.info,  Node: Security<39>,  Up: Python 3 6 2 release candidate 2

1.23.70.1 Security
..................

   - bpo-30730(1): Prevent environment variables injection in subprocess
     on Windows.  Prevent passing other environment variables and
     command arguments.

   - bpo-30694(2): Upgrade expat copy from 2.2.0 to 2.2.1 to get fixes
     of multiple security vulnerabilities including: CVE-2017-9233(3)
     (External entity infinite loop DoS), CVE-2016-9063(4) (Integer
     overflow, re-fix), CVE-2016-0718(5) (Fix regression bugs from
     2.2.0's fix to CVE-2016-0718(6)) and CVE-2012-0876(7) (Counter hash
     flooding with SipHash).  Note: the CVE-2016-5300(8) (Use
     os-specific entropy sources like getrandom) doesn't impact Python,
     since Python already gets entropy from the OS to set the expat
     secret using ‘XML_SetHashSalt()’.

   - bpo-30500(9): Fix urllib.parse.splithost() to correctly parse
     fragments.  For example, ‘splithost('//127.0.0.1#@evil.com/')’ now
     correctly returns the ‘127.0.0.1’ host, instead of treating
     ‘@evil.com’ as the host in an authentication (‘login@host’).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30730

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30694

   (3) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9233

   (4) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9063

   (5) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0718

   (6) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0718

   (7) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0876

   (8) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5300

   (9) https://bugs.python.org/issue?@action=redirect&bpo=30500


File: python.info,  Node: Python 3 6 2 release candidate 1,  Next: Python 3 6 1 final,  Prev: Python 3 6 2 release candidate 2,  Up: Changelog（更動日誌）

1.23.71 Python 3.6.2 release candidate 1
----------------------------------------

'Release date: 2017-06-17'

* Menu:

* Security: Security<40>.
* Core and Builtins: Core and Builtins<64>.
* Library: Library<65>.
* IDLE: IDLE<48>.
* C API: C API<57>.
* Build: Build<63>.
* Documentation: Documentation<58>.
* Tools/Demos: Tools/Demos<34>.
* Tests: Tests<59>.
* Windows: Windows<56>.


File: python.info,  Node: Security<40>,  Next: Core and Builtins<64>,  Up: Python 3 6 2 release candidate 1

1.23.71.1 Security
..................

   - bpo-29591(1): Update expat copy from 2.1.1 to 2.2.0 to get fixes of
     CVE-2016-0718(2) and CVE-2016-4472(3).  See
     ‘https://sourceforge.net/p/expat/bugs/537/’ for more information.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29591

   (2) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0718

   (3) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4472


File: python.info,  Node: Core and Builtins<64>,  Next: Library<65>,  Prev: Security<40>,  Up: Python 3 6 2 release candidate 1

1.23.71.2 Core and Builtins
...........................

   - bpo-30682(1): Removed a too-strict assertion that failed for
     certain f-strings, such as eval("f'\n'") and eval("f'\r'").

   - bpo-30604(2): Move co_extra_freefuncs to not be per-thread to avoid
     crashes

   - bpo-29104(3): Fixed parsing backslashes in f-strings.

   - bpo-27945(4): Fixed various segfaults with dict when input
     collections are mutated during searching, inserting or comparing.
     Based on patches by Duane Griffin and Tim Mitchell.

   - bpo-25794(5): Fixed type.__setattr__() and type.__delattr__() for
     non-interned attribute names.  Based on patch by Eryk Sun.

   - bpo-30039(6): If a KeyboardInterrupt happens when the interpreter
     is in the middle of resuming a chain of nested 'yield from' or
     'await' calls, it's now correctly delivered to the innermost frame.

   - bpo-12414(7): sys.getsizeof() on a code object now returns the
     sizes which includes the code struct and sizes of objects which it
     references.  Patch by Donghee Na.

   - bpo-29949(8): Fix memory usage regression of set and frozenset
     object.

   - bpo-29935(9): Fixed error messages in the index() method of tuple,
     list and deque when pass indices of wrong type.

   - bpo-29859(10): Show correct error messages when any of the
     pthread_* calls in thread_pthread.h fails.

   - bpo-28876(11): ‘bool(range)’ works even if ‘len(range)’ raises
     *note OverflowError: 825.

   - bpo-29600(12): Fix wrapping coroutine return values in
     StopIteration.

   - bpo-28856(13): Fix an oversight that %b format for bytes should
     support objects follow the buffer protocol.

   - bpo-29714(14): Fix a regression that bytes format may fail when
     containing zero bytes inside.

   - bpo-29478(15): If max_line_length=None is specified while using the
     Compat32 policy, it is no longer ignored.  Patch by Mircea Cosbuc.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30682

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30604

   (3) https://bugs.python.org/issue?@action=redirect&bpo=29104

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27945

   (5) https://bugs.python.org/issue?@action=redirect&bpo=25794

   (6) https://bugs.python.org/issue?@action=redirect&bpo=30039

   (7) https://bugs.python.org/issue?@action=redirect&bpo=12414

   (8) https://bugs.python.org/issue?@action=redirect&bpo=29949

   (9) https://bugs.python.org/issue?@action=redirect&bpo=29935

   (10) https://bugs.python.org/issue?@action=redirect&bpo=29859

   (11) https://bugs.python.org/issue?@action=redirect&bpo=28876

   (12) https://bugs.python.org/issue?@action=redirect&bpo=29600

   (13) https://bugs.python.org/issue?@action=redirect&bpo=28856

   (14) https://bugs.python.org/issue?@action=redirect&bpo=29714

   (15) https://bugs.python.org/issue?@action=redirect&bpo=29478


File: python.info,  Node: Library<65>,  Next: IDLE<48>,  Prev: Core and Builtins<64>,  Up: Python 3 6 2 release candidate 1

1.23.71.3 Library
.................

   - bpo-30616(1): Functional API of enum allows to create empty enums.
     Patched by Donghee Na

   - bpo-30038(2): Fix race condition between signal delivery and wakeup
     file descriptor.  Patch by Nathaniel Smith.

   - bpo-23894(3): lib2to3 now recognizes ‘rb'...'’ and ‘f'...'’
     strings.

   - bpo-23890(4): unittest.TestCase.assertRaises() now manually breaks
     a reference cycle to not keep objects alive longer than expected.

   - bpo-30149(5): inspect.signature() now supports callables with
     variable-argument parameters wrapped with partialmethod.  Patch by
     Donghee Na.

   - bpo-30645(6): Fix path calculation in imp.load_package(), fixing it
     for cases when a package is only shipped with bytecodes.  Patch by
     Alexandru Ardelean.

   - bpo-29931(7): Fixed comparison check for ipaddress.ip_interface
     objects.  Patch by Sanjay Sundaresan.

   - bpo-30605(8): re.compile() no longer raises a BytesWarning when
     compiling a bytes instance with misplaced inline modifier.  Patch
     by Roy Williams.

   - bpo-24484(9): Avoid race condition in multiprocessing cleanup
     (#2159)

   - bpo-28994(10): The traceback no longer displayed for SystemExit
     raised in a callback registered by atexit.

   - bpo-30508(11): Don't log exceptions if Task/Future "cancel()"
     method was called.

   - bpo-28556(12): Updates to typing module: Add generic
     AsyncContextManager, add support for ContextManager on all
     versions.  Original PRs by Jelle Zijlstra and Ivan Levkivskyi

   - bpo-29870(13): Fix ssl sockets leaks when connection is aborted in
     asyncio/ssl implementation.  Patch by Michaël Sghaïer.

   - bpo-29743(14): Closing transport during handshake process leaks
     open socket.  Patch by Nikolay Kim

   - bpo-27585(15): Fix waiter cancellation in asyncio.Lock.  Patch by
     Mathieu Sornay.

   - bpo-30418(16): On Windows, subprocess.Popen.communicate() now also
     ignore EINVAL on stdin.write() if the child process is still
     running but closed the pipe.

   - bpo-29822(17): inspect.isabstract() now works during
     __init_subclass__.  Patch by Nate Soares.

   - bpo-29581(18): ABCMeta.__new__ now accepts ‘**kwargs’, allowing
     abstract base classes to use keyword parameters in
     __init_subclass__.  Patch by Nate Soares.

   - bpo-30557(19): faulthandler now correctly filters and displays
     exception codes on Windows

   - bpo-30378(20): Fix the problem that logging.handlers.SysLogHandler
     cannot handle IPv6 addresses.

   - bpo-29960(21): Preserve generator state when
     _random.Random.setstate() raises an exception.  Patch by Bryan
     Olson.

   - bpo-30414(22): multiprocessing.Queue._feed background running
     thread do not break from main loop on exception.

   - bpo-30003(23): Fix handling escape characters in HZ codec.  Based
     on patch by Ma Lin.

   - bpo-30301(24): Fix AttributeError when using SimpleQueue.empty()
     under 'spawn' and 'forkserver' start methods.

   - bpo-30329(25): imaplib and poplib now catch the Windows socket
     WSAEINVAL error (code 10022) on shutdown(SHUT_RDWR): An invalid
     operation was attempted.  This error occurs sometimes on SSL
     connections.

   - bpo-30375(26): Warnings emitted when compile a regular expression
     now always point to the line in the user code.  Previously they
     could point into inners of the re module if emitted from inside of
     groups or conditionals.

   - bpo-30048(27): Fixed ‘Task.cancel()’ can be ignored when the task
     is running coroutine and the coroutine returned without any more
     ‘await’.

   - bpo-30266(28): contextlib.AbstractContextManager now supports
     anti-registration by setting __enter__ = None or __exit__ = None,
     following the pattern introduced in bpo-25958(29).  Patch by Jelle
     Zijlstra.

   - bpo-30298(30): Weaken the condition of deprecation warnings for
     inline modifiers.  Now allowed several subsequential inline
     modifiers at the start of the pattern (e.g.  ‘'(?i)(?s)...'’).  In
     verbose mode whitespaces and comments now are allowed before and
     between inline modifiers (e.g.  ‘'(?x) (?i) (?s)...'’).

   - bpo-29990(31): Fix range checking in GB18030 decoder.  Original
     patch by Ma Lin.

   - bpo-26293(32): Change resulted because of zipfile breakage.  (See
     also: bpo-29094(33))

   - bpo-30243(34): Removed the __init__ methods of _json's scanner and
     encoder.  Misusing them could cause memory leaks or crashes.  Now
     scanner and encoder objects are completely initialized in the
     __new__ methods.

   - bpo-30185(35): Avoid KeyboardInterrupt tracebacks in forkserver
     helper process when Ctrl-C is received.

   - bpo-28556(36): Various updates to typing module: add
     typing.NoReturn type, use WrapperDescriptorType, minor bug-fixes.
     Original PRs by Jim Fasarakis-Hilliard and Ivan Levkivskyi.

   - bpo-30205(37): Fix getsockname() for unbound AF_UNIX sockets on
     Linux.

   - bpo-30070(38): Fixed leaks and crashes in errors handling in the
     parser module.

   - bpo-30061(39): Fixed crashes in IOBase methods __next__() and
     readlines() when readline() or __next__() respectively return
     non-sizeable object.  Fixed possible other errors caused by not
     checking results of PyObject_Size(), PySequence_Size(), or
     PyMapping_Size().

   - bpo-30017(40): Allowed calling the close() method of the zip entry
     writer object multiple times.  Writing to a closed writer now
     always produces a ValueError.

   - bpo-30068(41): _io._IOBase.readlines will check if it's closed
     first when hint is present.

   - bpo-29694(42): Fixed race condition in pathlib mkdir with flags
     parents=True.  Patch by Armin Rigo.

   - bpo-29692(43): Fixed arbitrary unchaining of RuntimeError
     exceptions in contextlib.contextmanager.  Patch by Siddharth
     Velankar.

   - bpo-29998(44): Pickling and copying ImportError now preserves name
     and path attributes.

   - bpo-29953(45): Fixed memory leaks in the replace() method of
     datetime and time objects when pass out of bound fold argument.

   - bpo-29942(46): Fix a crash in itertools.chain.from_iterable when
     encountering long runs of empty iterables.

   - bpo-27863(47): Fixed multiple crashes in ElementTree caused by race
     conditions and wrong types.

   - bpo-28699(48): Fixed a bug in pools in multiprocessing.pool that
     raising an exception at the very first of an iterable may swallow
     the exception or make the program hang.  Patch by Davin Potts and
     Xiang Zhang.

   - bpo-25803(49): Avoid incorrect errors raised by
     Path.mkdir(exist_ok=True) when the OS gives priority to errors such
     as EACCES over EEXIST.

   - bpo-29861(50): Release references to tasks, their arguments and
     their results as soon as they are finished in multiprocessing.Pool.

   - bpo-29884(51): faulthandler: Restore the old sigaltstack during
     teardown.  Patch by Christophe Zeitouny.

   - bpo-25455(52): Fixed crashes in repr of recursive buffered
     file-like objects.

   - bpo-29800(53): Fix crashes in partial.__repr__ if the keys of
     partial.keywords are not strings.  Patch by Michael Seifert.

   - bpo-29742(54): get_extra_info() raises exception if get called on
     closed ssl transport.  Patch by Nikolay Kim.

   - bpo-8256(55): Fixed possible failing or crashing input() if
     attributes "encoding" or "errors" of sys.stdin or sys.stdout are
     not set or are not strings.

   - bpo-28298(56): Fix a bug that prevented array 'Q', 'L' and 'I' from
     accepting big intables (objects that have __int__) as elements.
     Patch by Oren Milman.

   - bpo-28231(57): The zipfile module now accepts path-like objects for
     external paths.

   - bpo-26915(58): index() and count() methods of
     collections.abc.Sequence now check identity before checking
     equality when do comparisons.

   - bpo-29615(59): SimpleXMLRPCDispatcher no longer chains KeyError (or
     any other exception) to exception(s) raised in the dispatched
     methods.  Patch by Petr Motejlek.

   - bpo-30177(60): path.resolve(strict=False) no longer cuts the path
     after the first element not present in the filesystem.  Patch by
     Antoine Pietri.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30616

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30038

   (3) https://bugs.python.org/issue?@action=redirect&bpo=23894

   (4) https://bugs.python.org/issue?@action=redirect&bpo=23890

   (5) https://bugs.python.org/issue?@action=redirect&bpo=30149

   (6) https://bugs.python.org/issue?@action=redirect&bpo=30645

   (7) https://bugs.python.org/issue?@action=redirect&bpo=29931

   (8) https://bugs.python.org/issue?@action=redirect&bpo=30605

   (9) https://bugs.python.org/issue?@action=redirect&bpo=24484

   (10) https://bugs.python.org/issue?@action=redirect&bpo=28994

   (11) https://bugs.python.org/issue?@action=redirect&bpo=30508

   (12) https://bugs.python.org/issue?@action=redirect&bpo=28556

   (13) https://bugs.python.org/issue?@action=redirect&bpo=29870

   (14) https://bugs.python.org/issue?@action=redirect&bpo=29743

   (15) https://bugs.python.org/issue?@action=redirect&bpo=27585

   (16) https://bugs.python.org/issue?@action=redirect&bpo=30418

   (17) https://bugs.python.org/issue?@action=redirect&bpo=29822

   (18) https://bugs.python.org/issue?@action=redirect&bpo=29581

   (19) https://bugs.python.org/issue?@action=redirect&bpo=30557

   (20) https://bugs.python.org/issue?@action=redirect&bpo=30378

   (21) https://bugs.python.org/issue?@action=redirect&bpo=29960

   (22) https://bugs.python.org/issue?@action=redirect&bpo=30414

   (23) https://bugs.python.org/issue?@action=redirect&bpo=30003

   (24) https://bugs.python.org/issue?@action=redirect&bpo=30301

   (25) https://bugs.python.org/issue?@action=redirect&bpo=30329

   (26) https://bugs.python.org/issue?@action=redirect&bpo=30375

   (27) https://bugs.python.org/issue?@action=redirect&bpo=30048

   (28) https://bugs.python.org/issue?@action=redirect&bpo=30266

   (29) https://bugs.python.org/issue?@action=redirect&bpo=25958

   (30) https://bugs.python.org/issue?@action=redirect&bpo=30298

   (31) https://bugs.python.org/issue?@action=redirect&bpo=29990

   (32) https://bugs.python.org/issue?@action=redirect&bpo=26293

   (33) https://bugs.python.org/issue?@action=redirect&bpo=29094

   (34) https://bugs.python.org/issue?@action=redirect&bpo=30243

   (35) https://bugs.python.org/issue?@action=redirect&bpo=30185

   (36) https://bugs.python.org/issue?@action=redirect&bpo=28556

   (37) https://bugs.python.org/issue?@action=redirect&bpo=30205

   (38) https://bugs.python.org/issue?@action=redirect&bpo=30070

   (39) https://bugs.python.org/issue?@action=redirect&bpo=30061

   (40) https://bugs.python.org/issue?@action=redirect&bpo=30017

   (41) https://bugs.python.org/issue?@action=redirect&bpo=30068

   (42) https://bugs.python.org/issue?@action=redirect&bpo=29694

   (43) https://bugs.python.org/issue?@action=redirect&bpo=29692

   (44) https://bugs.python.org/issue?@action=redirect&bpo=29998

   (45) https://bugs.python.org/issue?@action=redirect&bpo=29953

   (46) https://bugs.python.org/issue?@action=redirect&bpo=29942

   (47) https://bugs.python.org/issue?@action=redirect&bpo=27863

   (48) https://bugs.python.org/issue?@action=redirect&bpo=28699

   (49) https://bugs.python.org/issue?@action=redirect&bpo=25803

   (50) https://bugs.python.org/issue?@action=redirect&bpo=29861

   (51) https://bugs.python.org/issue?@action=redirect&bpo=29884

   (52) https://bugs.python.org/issue?@action=redirect&bpo=25455

   (53) https://bugs.python.org/issue?@action=redirect&bpo=29800

   (54) https://bugs.python.org/issue?@action=redirect&bpo=29742

   (55) https://bugs.python.org/issue?@action=redirect&bpo=8256

   (56) https://bugs.python.org/issue?@action=redirect&bpo=28298

   (57) https://bugs.python.org/issue?@action=redirect&bpo=28231

   (58) https://bugs.python.org/issue?@action=redirect&bpo=26915

   (59) https://bugs.python.org/issue?@action=redirect&bpo=29615

   (60) https://bugs.python.org/issue?@action=redirect&bpo=30177


File: python.info,  Node: IDLE<48>,  Next: C API<57>,  Prev: Library<65>,  Up: Python 3 6 2 release candidate 1

1.23.71.4 IDLE
..............

   - bpo-15786(1): Fix several problems with IDLE's autocompletion box.
     The following should now work: clicking on selection box items;
     using the scrollbar; selecting an item by hitting Return.  Hangs on
     MacOSX should no longer happen.  Patch by Louie Lu.

   - bpo-25514(2): Add doc subsubsection about IDLE failure to start.
     Popup no-connection message directs users to this section.

   - bpo-30642(3): Fix reference leaks in IDLE tests.  Patches by Louie
     Lu and Terry Jan Reedy.

   - bpo-30495(4): Add docstrings for textview.py and use PEP8 names.
     Patches by Cheryl Sabella and Terry Jan Reedy.

   - bpo-30290(5): Help-about: use pep8 names and add tests.  Increase
     coverage to 100%.  Patches by Louie Lu, Cheryl Sabella, and Terry
     Jan Reedy.

   - bpo-30303(6): Add _utest option to textview; add new tests.
     Increase coverage to 100%.  Patches by Louie Lu and Terry Jan
     Reedy.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=15786

   (2) https://bugs.python.org/issue?@action=redirect&bpo=25514

   (3) https://bugs.python.org/issue?@action=redirect&bpo=30642

   (4) https://bugs.python.org/issue?@action=redirect&bpo=30495

   (5) https://bugs.python.org/issue?@action=redirect&bpo=30290

   (6) https://bugs.python.org/issue?@action=redirect&bpo=30303


File: python.info,  Node: C API<57>,  Next: Build<63>,  Prev: IDLE<48>,  Up: Python 3 6 2 release candidate 1

1.23.71.5 C API
...............

   - bpo-27867(1): Function PySlice_GetIndicesEx() no longer replaced
     with a macro if Py_LIMITED_API is not set.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27867


File: python.info,  Node: Build<63>,  Next: Documentation<58>,  Prev: C API<57>,  Up: Python 3 6 2 release candidate 1

1.23.71.6 Build
...............

   - bpo-29941(1): Add ‘--with-assertions’ configure flag to explicitly
     enable C ‘assert()’ checks.  Defaults to off.  ‘--with-pydebug’
     implies ‘--with-assertions’.

   - bpo-28787(2): Fix out-of-tree builds of Python when configured with
     ‘--with--dtrace’.

   - bpo-29243(3): Prevent unnecessary rebuilding of Python during ‘make
     test’, ‘make install’ and some other make targets when configured
     with ‘--enable-optimizations’.

   - bpo-23404(4): Don't regenerate generated files based on file
     modification time anymore: the action is now explicit.  Replace
     ‘make touch’ with ‘make regen-all’.

   - bpo-29643(5): Fix ‘--enable-optimization’ didn't work.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29941

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28787

   (3) https://bugs.python.org/issue?@action=redirect&bpo=29243

   (4) https://bugs.python.org/issue?@action=redirect&bpo=23404

   (5) https://bugs.python.org/issue?@action=redirect&bpo=29643


File: python.info,  Node: Documentation<58>,  Next: Tools/Demos<34>,  Prev: Build<63>,  Up: Python 3 6 2 release candidate 1

1.23.71.7 Documentation
.......................

   - bpo-30176(1): Add missing attribute related constants in curses
     documentation.

   - bpo-30052(2): the link targets for *note bytes(): 1a5. and *note
     bytearray(): 4e3. are now their respective type definitions, rather
     than the corresponding builtin function entries.  Use *note bytes:
     19bf. and *note bytearray: 19c0. to reference the latter.  In order
     to ensure this and future cross-reference updates are applied
     automatically, the daily documentation builds now disable the
     default output caching features in Sphinx.

   - bpo-26985(3): Add missing info of code object in inspect
     documentation.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30176

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30052

   (3) https://bugs.python.org/issue?@action=redirect&bpo=26985


File: python.info,  Node: Tools/Demos<34>,  Next: Tests<59>,  Prev: Documentation<58>,  Up: Python 3 6 2 release candidate 1

1.23.71.8 Tools/Demos
.....................

   - bpo-29367(1): python-gdb.py now supports also ‘method-wrapper’
     (‘wrapperobject’) objects.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29367


File: python.info,  Node: Tests<59>,  Next: Windows<56>,  Prev: Tools/Demos<34>,  Up: Python 3 6 2 release candidate 1

1.23.71.9 Tests
...............

   - bpo-30357(1): test_thread: setUp() now uses
     support.threading_setup() and support.threading_cleanup() to wait
     until threads complete to avoid random side effects on following
     tests.  Initial patch written by Grzegorz Grzywacz.

   - bpo-30197(2): Enhanced functions swap_attr() and swap_item() in the
     test.support module.  They now work when delete replaced attribute
     or item inside the with statement.  The old value of the attribute
     or item (or None if it doesn't exist) now will be assigned to the
     target of the "as" clause, if there is one.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30357

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30197


File: python.info,  Node: Windows<56>,  Prev: Tests<59>,  Up: Python 3 6 2 release candidate 1

1.23.71.10 Windows
..................

   - bpo-30687(1): Locate msbuild.exe on Windows when building rather
     than vcvarsall.bat

   - bpo-30450(2): The build process on Windows no longer depends on
     Subversion, instead pulling external code from GitHub via a Python
     script.  If Python 3.6 is not found on the system (via ‘py -3.6’),
     NuGet is used to download a copy of 32-bit Python.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30687

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30450


File: python.info,  Node: Python 3 6 1 final,  Next: Python 3 6 1 release candidate 1,  Prev: Python 3 6 2 release candidate 1,  Up: Changelog（更動日誌）

1.23.72 Python 3.6.1 final
--------------------------

'Release date: 2017-03-21'

* Menu:

* Core and Builtins: Core and Builtins<65>.
* Build: Build<64>.


File: python.info,  Node: Core and Builtins<65>,  Next: Build<64>,  Up: Python 3 6 1 final

1.23.72.1 Core and Builtins
...........................

   - bpo-29723(1): The ‘sys.path[0]’ initialization change for
     bpo-29139(2) caused a regression by revealing an inconsistency in
     how sys.path is initialized when executing ‘__main__’ from a
     zipfile, directory, or other import location.  The interpreter now
     consistently avoids ever adding the import location's parent
     directory to ‘sys.path’, and ensures no other ‘sys.path’ entries
     are inadvertently modified when inserting the import location named
     on the command line.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29723

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29139


File: python.info,  Node: Build<64>,  Prev: Core and Builtins<65>,  Up: Python 3 6 1 final

1.23.72.2 Build
...............

   - bpo-27593(1): fix format of git information used in sys.version

   - Fix incompatible comment in python.h

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27593


File: python.info,  Node: Python 3 6 1 release candidate 1,  Next: Python 3 6 0 final,  Prev: Python 3 6 1 final,  Up: Changelog（更動日誌）

1.23.73 Python 3.6.1 release candidate 1
----------------------------------------

'Release date: 2017-03-04'

* Menu:

* Core and Builtins: Core and Builtins<66>.
* Library: Library<66>.
* IDLE: IDLE<49>.
* Windows: Windows<57>.
* C API: C API<58>.
* Documentation: Documentation<59>.
* Tests: Tests<60>.
* Build: Build<65>.


File: python.info,  Node: Core and Builtins<66>,  Next: Library<66>,  Up: Python 3 6 1 release candidate 1

1.23.73.1 Core and Builtins
...........................

   - bpo-28893(1): Set correct __cause__ for errors about invalid
     awaitables returned from __aiter__ and __anext__.

   - bpo-29683(2): Fixes to memory allocation in _PyCode_SetExtra.
     Patch by Brian Coleman.

   - bpo-29684(3): Fix minor regression of
     PyEval_CallObjectWithKeywords.  It should raise TypeError when
     kwargs is not a dict.  But it might cause segv when args=NULL and
     kwargs is not a dict.

   - bpo-28598(4): Support __rmod__ for subclasses of str being called
     before str.__mod__.  Patch by Martijn Pieters.

   - bpo-29607(5): Fix stack_effect computation for CALL_FUNCTION_EX.
     Patch by Matthieu Dartiailh.

   - bpo-29602(6): Fix incorrect handling of signed zeros in complex
     constructor for complex subclasses and for inputs having a
     __complex__ method.  Patch by Serhiy Storchaka.

   - bpo-29347(7): Fixed possibly dereferencing undefined pointers when
     creating weakref objects.

   - bpo-29438(8): Fixed use-after-free problem in key sharing dict.

   - bpo-29319(9): Prevent RunMainFromImporter overwriting sys.path[0].

   - bpo-29337(10): Fixed possible BytesWarning when compare the code
     objects.  Warnings could be emitted at compile time.

   - bpo-29327(11): Fixed a crash when pass the iterable keyword
     argument to sorted().

   - bpo-29034(12): Fix memory leak and use-after-free in os module
     (path_converter).

   - bpo-29159(13): Fix regression in bytes(x) when x.__index__() raises
     Exception.

   - bpo-28932(14): Do not include <sys/random.h> if it does not exist.

   - bpo-25677(15): Correct the positioning of the syntax error caret
     for indented blocks.  Based on patch by Michael Layzell.

   - bpo-29000(16): Fixed bytes formatting of octals with zero padding
     in alternate form.

   - bpo-26919(17): On Android, operating system data is now always
     encoded/decoded to/from UTF-8, instead of the locale encoding to
     avoid inconsistencies with os.fsencode() and os.fsdecode() which
     are already using UTF-8.

   - bpo-28991(18): functools.lru_cache() was susceptible to an obscure
     reentrancy bug triggerable by a monkey-patched len() function.

   - bpo-28739(19): f-string expressions are no longer accepted as
     docstrings and by ast.literal_eval() even if they do not include
     expressions.

   - bpo-28512(20): Fixed setting the offset attribute of SyntaxError by
     PyErr_SyntaxLocationEx() and PyErr_SyntaxLocationObject().

   - bpo-28918(21): Fix the cross compilation of xxlimited when Python
     has been built with Py_DEBUG defined.

   - bpo-28731(22): Optimize _PyDict_NewPresized() to create correct
     size dict.  Improve speed of dict literal with constant keys up to
     30%.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28893

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29683

   (3) https://bugs.python.org/issue?@action=redirect&bpo=29684

   (4) https://bugs.python.org/issue?@action=redirect&bpo=28598

   (5) https://bugs.python.org/issue?@action=redirect&bpo=29607

   (6) https://bugs.python.org/issue?@action=redirect&bpo=29602

   (7) https://bugs.python.org/issue?@action=redirect&bpo=29347

   (8) https://bugs.python.org/issue?@action=redirect&bpo=29438

   (9) https://bugs.python.org/issue?@action=redirect&bpo=29319

   (10) https://bugs.python.org/issue?@action=redirect&bpo=29337

   (11) https://bugs.python.org/issue?@action=redirect&bpo=29327

   (12) https://bugs.python.org/issue?@action=redirect&bpo=29034

   (13) https://bugs.python.org/issue?@action=redirect&bpo=29159

   (14) https://bugs.python.org/issue?@action=redirect&bpo=28932

   (15) https://bugs.python.org/issue?@action=redirect&bpo=25677

   (16) https://bugs.python.org/issue?@action=redirect&bpo=29000

   (17) https://bugs.python.org/issue?@action=redirect&bpo=26919

   (18) https://bugs.python.org/issue?@action=redirect&bpo=28991

   (19) https://bugs.python.org/issue?@action=redirect&bpo=28739

   (20) https://bugs.python.org/issue?@action=redirect&bpo=28512

   (21) https://bugs.python.org/issue?@action=redirect&bpo=28918

   (22) https://bugs.python.org/issue?@action=redirect&bpo=28731


File: python.info,  Node: Library<66>,  Next: IDLE<49>,  Prev: Core and Builtins<66>,  Up: Python 3 6 1 release candidate 1

1.23.73.2 Library
.................

   - bpo-29169(1): Update zlib to 1.2.11.

   - bpo-29623(2): Allow use of path-like object as a single argument in
     ConfigParser.read().  Patch by David Ellis.

   - bpo-28963(3): Fix out of bound iteration in
     asyncio.Future.remove_done_callback implemented in C.

   - bpo-29704(4): asyncio.subprocess.SubprocessStreamProtocol no longer
     closes before all pipes are closed.

   - bpo-29271(5): Fix Task.current_task and Task.all_tasks implemented
     in C to accept None argument as their pure Python implementation.

   - bpo-29703(6): Fix asyncio to support instantiation of new event
     loops in child processes.

   - bpo-29376(7): Fix assertion error in
     threading._DummyThread.is_alive().

   - bpo-28624(8): Add a test that checks that cwd parameter of Popen()
     accepts PathLike objects.  Patch by Sayan Chowdhury.

   - bpo-28518(9): Start a transaction implicitly before a DML
     statement.  Patch by Aviv Palivoda.

   - bpo-29532(10): Altering a kwarg dictionary passed to
     functools.partial() no longer affects a partial object after
     creation.

   - bpo-29110(11): Fix file object leak in aifc.open() when file is
     given as a filesystem path and is not in valid AIFF format.  Patch
     by Anthony Zhang.

   - bpo-28556(12): Various updates to typing module: typing.Counter,
     typing.ChainMap, improved ABC caching, etc.  Original PRs by Jelle
     Zijlstra, Ivan Levkivskyi, Manuel Krebber, and Łukasz Langa.

   - bpo-29100(13): Fix datetime.fromtimestamp() regression introduced
     in Python 3.6.0: check minimum and maximum years.

   - bpo-29519(14): Fix weakref spewing exceptions during interpreter
     shutdown when used with a rare combination of multiprocessing and
     custom codecs.

   - bpo-29416(15): Prevent infinite loop in pathlib.Path.mkdir

   - bpo-29444(16): Fixed out-of-bounds buffer access in the group()
     method of the match object.  Based on patch by WGH.

   - bpo-29335(17): Fix subprocess.Popen.wait() when the child process
     has exited to a stopped instead of terminated state (ex: when under
     ptrace).

   - bpo-29290(18): Fix a regression in argparse that help messages
     would wrap at non-breaking spaces.

   - bpo-28735(19): Fixed the comparison of mock.MagickMock with
     mock.ANY.

   - bpo-29316(20): Restore the provisional status of typing module, add
     corresponding note to documentation.  Patch by Ivan L.

   - bpo-29219(21): Fixed infinite recursion in the repr of
     uninitialized ctypes.CDLL instances.

   - bpo-29011(22): Fix an important omission by adding Deque to the
     typing module.

   - bpo-28969(23): Fixed race condition in C implementation of
     functools.lru_cache.  KeyError could be raised when cached function
     with full cache was simultaneously called from different threads
     with the same uncached arguments.

   - bpo-29142(24): In urllib.request, suffixes in no_proxy environment
     variable with leading dots could match related hostnames again
     (e.g.  .b.c matches a.b.c).  Patch by Milan Oberkirch.

   - bpo-28961(25): Fix unittest.mock._Call helper: don't ignore the
     name parameter anymore.  Patch written by Jiajun Huang.

   - bpo-29203(26): functools.lru_cache() now respects PEP 468(27) and
     preserves the order of keyword arguments.  f(a=1, b=2) is now
     cached separately from f(b=2, a=1) since both calls could
     potentially give different results.

   - bpo-15812(28): inspect.getframeinfo() now correctly shows the first
     line of a context.  Patch by Sam Breese.

   - bpo-29094(29): Offsets in a ZIP file created with extern file
     object and modes "w" and "x" now are relative to the start of the
     file.

   - bpo-29085(30): Allow random.Random.seed() to use high quality OS
     randomness rather than the pid and time.

   - bpo-29061(31): Fixed bug in secrets.randbelow() which would hang
     when given a negative input.  Patch by Brendan Donegan.

   - bpo-29079(32): Prevent infinite loop in pathlib.resolve() on
     Windows

   - bpo-13051(33): Fixed recursion errors in large or resized
     curses.textpad.Textbox.  Based on patch by Tycho Andersen.

   - bpo-29119(34): Fix weakrefs in the pure python version of
     collections.OrderedDict move_to_end() method.  Contributed by Andra
     Bogildea.

   - bpo-9770(35): curses.ascii predicates now work correctly with
     negative integers.

   - bpo-28427(36): old keys should not remove new values from
     WeakValueDictionary when collecting from another thread.

   - bpo-28923(37): Remove editor artifacts from Tix.py.

   - bpo-29055(38): Neaten-up empty population error on random.choice()
     by suppressing the upstream exception.

   - bpo-28871(39): Fixed a crash when deallocate deep ElementTree.

   - bpo-19542(40): Fix bugs in WeakValueDictionary.setdefault() and
     WeakValueDictionary.pop() when a GC collection happens in another
     thread.

   - bpo-20191(41): Fixed a crash in resource.prlimit() when passing a
     sequence that doesn't own its elements as limits.

   - bpo-28779(42): multiprocessing.set_forkserver_preload() would crash
     the forkserver process if a preloaded module instantiated some
     multiprocessing objects such as locks.

   - bpo-28847(43): dbm.dumb now supports reading read-only files and no
     longer writes the index file when it is not changed.

   - bpo-26937(44): The chown() method of the tarfile.TarFile class does
     not fail now when the grp module cannot be imported, as for example
     on Android platforms.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29169

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29623

   (3) https://bugs.python.org/issue?@action=redirect&bpo=28963

   (4) https://bugs.python.org/issue?@action=redirect&bpo=29704

   (5) https://bugs.python.org/issue?@action=redirect&bpo=29271

   (6) https://bugs.python.org/issue?@action=redirect&bpo=29703

   (7) https://bugs.python.org/issue?@action=redirect&bpo=29376

   (8) https://bugs.python.org/issue?@action=redirect&bpo=28624

   (9) https://bugs.python.org/issue?@action=redirect&bpo=28518

   (10) https://bugs.python.org/issue?@action=redirect&bpo=29532

   (11) https://bugs.python.org/issue?@action=redirect&bpo=29110

   (12) https://bugs.python.org/issue?@action=redirect&bpo=28556

   (13) https://bugs.python.org/issue?@action=redirect&bpo=29100

   (14) https://bugs.python.org/issue?@action=redirect&bpo=29519

   (15) https://bugs.python.org/issue?@action=redirect&bpo=29416

   (16) https://bugs.python.org/issue?@action=redirect&bpo=29444

   (17) https://bugs.python.org/issue?@action=redirect&bpo=29335

   (18) https://bugs.python.org/issue?@action=redirect&bpo=29290

   (19) https://bugs.python.org/issue?@action=redirect&bpo=28735

   (20) https://bugs.python.org/issue?@action=redirect&bpo=29316

   (21) https://bugs.python.org/issue?@action=redirect&bpo=29219

   (22) https://bugs.python.org/issue?@action=redirect&bpo=29011

   (23) https://bugs.python.org/issue?@action=redirect&bpo=28969

   (24) https://bugs.python.org/issue?@action=redirect&bpo=29142

   (25) https://bugs.python.org/issue?@action=redirect&bpo=28961

   (26) https://bugs.python.org/issue?@action=redirect&bpo=29203

   (27) https://peps.python.org/pep-0468/

   (28) https://bugs.python.org/issue?@action=redirect&bpo=15812

   (29) https://bugs.python.org/issue?@action=redirect&bpo=29094

   (30) https://bugs.python.org/issue?@action=redirect&bpo=29085

   (31) https://bugs.python.org/issue?@action=redirect&bpo=29061

   (32) https://bugs.python.org/issue?@action=redirect&bpo=29079

   (33) https://bugs.python.org/issue?@action=redirect&bpo=13051

   (34) https://bugs.python.org/issue?@action=redirect&bpo=29119

   (35) https://bugs.python.org/issue?@action=redirect&bpo=9770

   (36) https://bugs.python.org/issue?@action=redirect&bpo=28427

   (37) https://bugs.python.org/issue?@action=redirect&bpo=28923

   (38) https://bugs.python.org/issue?@action=redirect&bpo=29055

   (39) https://bugs.python.org/issue?@action=redirect&bpo=28871

   (40) https://bugs.python.org/issue?@action=redirect&bpo=19542

   (41) https://bugs.python.org/issue?@action=redirect&bpo=20191

   (42) https://bugs.python.org/issue?@action=redirect&bpo=28779

   (43) https://bugs.python.org/issue?@action=redirect&bpo=28847

   (44) https://bugs.python.org/issue?@action=redirect&bpo=26937


File: python.info,  Node: IDLE<49>,  Next: Windows<57>,  Prev: Library<66>,  Up: Python 3 6 1 release candidate 1

1.23.73.3 IDLE
..............

   - bpo-29071(1): IDLE colors f-string prefixes (but not invalid ur
     prefixes).

   - bpo-28572(2): Add 10% to coverage of IDLE's test_configdialog.
     Update and augment description of the configuration system.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29071

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28572


File: python.info,  Node: Windows<57>,  Next: C API<58>,  Prev: IDLE<49>,  Up: Python 3 6 1 release candidate 1

1.23.73.4 Windows
.................

   - bpo-29579(1): Removes readme.txt from the installer

   - bpo-29326(2): Ignores blank lines in ._pth files (Patch by Alexey
     Izbyshev)

   - bpo-28164(3): Correctly handle special console filenames (patch by
     Eryk Sun)

   - bpo-29409(4): Implement PEP 529(5) for io.FileIO (Patch by Eryk
     Sun)

   - bpo-29392(6): Prevent crash when passing invalid arguments into
     msvcrt module.

   - bpo-25778(7): winreg does not truncate string correctly (Patch by
     Eryk Sun)

   - bpo-28896(8): Deprecate WindowsRegistryFinder and disable it by
     default.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29579

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29326

   (3) https://bugs.python.org/issue?@action=redirect&bpo=28164

   (4) https://bugs.python.org/issue?@action=redirect&bpo=29409

   (5) https://peps.python.org/pep-0529/

   (6) https://bugs.python.org/issue?@action=redirect&bpo=29392

   (7) https://bugs.python.org/issue?@action=redirect&bpo=25778

   (8) https://bugs.python.org/issue?@action=redirect&bpo=28896


File: python.info,  Node: C API<58>,  Next: Documentation<59>,  Prev: Windows<57>,  Up: Python 3 6 1 release candidate 1

1.23.73.5 C API
...............

   - bpo-27867(1): Function PySlice_GetIndicesEx() is replaced with a
     macro if Py_LIMITED_API is not set or set to the value between
     0x03050400 and 0x03060000 (not including) or 0x03060100 or higher.

   - bpo-29083(2): Fixed the declaration of some public API functions.
     PyArg_VaParse() and PyArg_VaParseTupleAndKeywords() were not
     available in limited API. PyArg_ValidateKeywordArguments(),
     PyArg_UnpackTuple() and Py_BuildValue() were not available in
     limited API of version < 3.3 when PY_SSIZE_T_CLEAN is defined.

   - bpo-29058(3): All stable API extensions added after Python 3.2 are
     now available only when Py_LIMITED_API is set to the PY_VERSION_HEX
     value of the minimum Python version supporting this API.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27867

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29083

   (3) https://bugs.python.org/issue?@action=redirect&bpo=29058


File: python.info,  Node: Documentation<59>,  Next: Tests<60>,  Prev: C API<58>,  Up: Python 3 6 1 release candidate 1

1.23.73.6 Documentation
.......................

   - bpo-28929(1): Link the documentation to its source file on GitHub.

   - bpo-25008(2): Document smtpd.py as effectively deprecated and add a
     pointer to aiosmtpd, a third-party asyncio-based replacement.

   - bpo-26355(3): Add canonical header link on each page to
     corresponding major version of the documentation.  Patch by
     Matthias Bussonnier.

   - bpo-29349(4): Fix Python 2 syntax in code for building the
     documentation.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28929

   (2) https://bugs.python.org/issue?@action=redirect&bpo=25008

   (3) https://bugs.python.org/issue?@action=redirect&bpo=26355

   (4) https://bugs.python.org/issue?@action=redirect&bpo=29349


File: python.info,  Node: Tests<60>,  Next: Build<65>,  Prev: Documentation<59>,  Up: Python 3 6 1 release candidate 1

1.23.73.7 Tests
...............

   - bpo-28087(1): Skip test_asyncore and test_eintr poll failures on
     macOS. Skip some tests of select.poll when running on macOS due to
     unresolved issues with the underlying system poll function on some
     macOS versions.

   - bpo-29571(2): to match the behaviour of the ‘re.LOCALE’ flag,
     test_re.test_locale_flag now uses
     ‘locale.getpreferredencoding(False)’ to determine the candidate
     encoding for the test regex (allowing it to correctly skip the test
     when the default locale encoding is a multi-byte encoding)

   - bpo-28950(3): Disallow -j0 to be combined with -T/-l in regrtest
     command line arguments.

   - bpo-28683(4): Fix the tests that bind() a unix socket and raise
     PermissionError on Android for a non-root user.

   - bpo-26939(5): Add the support.setswitchinterval() function to fix
     test_functools hanging on the Android armv7 qemu emulator.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28087

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29571

   (3) https://bugs.python.org/issue?@action=redirect&bpo=28950

   (4) https://bugs.python.org/issue?@action=redirect&bpo=28683

   (5) https://bugs.python.org/issue?@action=redirect&bpo=26939


File: python.info,  Node: Build<65>,  Prev: Tests<60>,  Up: Python 3 6 1 release candidate 1

1.23.73.8 Build
...............

   - bpo-27593(1): sys.version and the platform module python_build(),
     python_branch(), and python_revision() functions now use git
     information rather than hg when building from a repo.

   - bpo-29572(2): Update Windows build and OS X installers to use
     OpenSSL 1.0.2k.

   - bpo-26851(3): Set Android compilation and link flags.

   - bpo-28768(4): Fix implicit declaration of function _setmode.  Patch
     by Masayuki Yamamoto

   - bpo-29080(5): Removes hard dependency on hg.exe from
     PCBuild/build.bat

   - bpo-23903(6): Added missed names to PC/python3.def.

   - bpo-28762(7): lockf() is available on Android API level 24, but the
     F_LOCK macro is not defined in android-ndk-r13.

   - bpo-28538(8): Fix the compilation error that occurs because
     if_nameindex() is available on Android API level 24, but the
     if_nameindex structure is not defined.

   - bpo-20211(9): Do not add the directory for installing C header
     files and the directory for installing object code libraries to the
     cross compilation search paths.  Original patch by Thomas
     Petazzoni.

   - bpo-28849(10): Do not define sys.implementation._multiarch on
     Android.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27593

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29572

   (3) https://bugs.python.org/issue?@action=redirect&bpo=26851

   (4) https://bugs.python.org/issue?@action=redirect&bpo=28768

   (5) https://bugs.python.org/issue?@action=redirect&bpo=29080

   (6) https://bugs.python.org/issue?@action=redirect&bpo=23903

   (7) https://bugs.python.org/issue?@action=redirect&bpo=28762

   (8) https://bugs.python.org/issue?@action=redirect&bpo=28538

   (9) https://bugs.python.org/issue?@action=redirect&bpo=20211

   (10) https://bugs.python.org/issue?@action=redirect&bpo=28849


File: python.info,  Node: Python 3 6 0 final,  Next: Python 3 6 0 release candidate 2,  Prev: Python 3 6 1 release candidate 1,  Up: Changelog（更動日誌）

1.23.74 Python 3.6.0 final
--------------------------

'Release date: 2016-12-23'

No changes since release candidate 2


File: python.info,  Node: Python 3 6 0 release candidate 2,  Next: Python 3 6 0 release candidate 1,  Prev: Python 3 6 0 final,  Up: Changelog（更動日誌）

1.23.75 Python 3.6.0 release candidate 2
----------------------------------------

'Release date: 2016-12-16'

* Menu:

* Core and Builtins: Core and Builtins<67>.
* Tools/Demos: Tools/Demos<35>.
* Windows: Windows<58>.
* Build: Build<66>.


File: python.info,  Node: Core and Builtins<67>,  Next: Tools/Demos<35>,  Up: Python 3 6 0 release candidate 2

1.23.75.1 Core and Builtins
...........................

   - bpo-28147(1): Fix a memory leak in split-table dictionaries:
     setattr() must not convert combined table into split table.  Patch
     written by INADA Naoki.

   - bpo-28990(2): Fix asyncio SSL hanging if connection is closed
     before handshake is completed.  (Patch by HoHo-Ho)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28147

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28990


File: python.info,  Node: Tools/Demos<35>,  Next: Windows<58>,  Prev: Core and Builtins<67>,  Up: Python 3 6 0 release candidate 2

1.23.75.2 Tools/Demos
.....................

   - bpo-28770(1): Fix python-gdb.py for fastcalls.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28770


File: python.info,  Node: Windows<58>,  Next: Build<66>,  Prev: Tools/Demos<35>,  Up: Python 3 6 0 release candidate 2

1.23.75.3 Windows
.................

   - bpo-28896(1): Deprecate WindowsRegistryFinder.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28896


File: python.info,  Node: Build<66>,  Prev: Windows<58>,  Up: Python 3 6 0 release candidate 2

1.23.75.4 Build
...............

   - bpo-28898(1): Prevent gdb build errors due to HAVE_LONG_LONG
     redefinition.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28898


File: python.info,  Node: Python 3 6 0 release candidate 1,  Next: Python 3 6 0 beta 4,  Prev: Python 3 6 0 release candidate 2,  Up: Changelog（更動日誌）

1.23.76 Python 3.6.0 release candidate 1
----------------------------------------

'Release date: 2016-12-06'

* Menu:

* Core and Builtins: Core and Builtins<68>.
* Library: Library<67>.
* C API: C API<59>.
* Documentation: Documentation<60>.
* Tools/Demos: Tools/Demos<36>.


File: python.info,  Node: Core and Builtins<68>,  Next: Library<67>,  Up: Python 3 6 0 release candidate 1

1.23.76.1 Core and Builtins
...........................

   - bpo-23722(1): Rather than silently producing a class that doesn't
     support zero-argument ‘super()’ in methods, failing to pass the new
     ‘__classcell__’ namespace entry up to ‘type.__new__’ now results in
     a ‘DeprecationWarning’ and a class that supports zero-argument
     ‘super()’.

   - bpo-28797(2): Modifying the class __dict__ inside the __set_name__
     method of a descriptor that is used inside that class no longer
     prevents calling the __set_name__ method of other descriptors.

   - bpo-28782(3): Fix a bug in the implementation ‘yield from’ when
     checking if the next instruction is YIELD_FROM. Regression
     introduced by WORDCODE (bpo-26647(4)).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23722

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28797

   (3) https://bugs.python.org/issue?@action=redirect&bpo=28782

   (4) https://bugs.python.org/issue?@action=redirect&bpo=26647


File: python.info,  Node: Library<67>,  Next: C API<59>,  Prev: Core and Builtins<68>,  Up: Python 3 6 0 release candidate 1

1.23.76.2 Library
.................

   - bpo-27030(1): Unknown escapes in re.sub() replacement template are
     allowed again.  But they still are deprecated and will be disabled
     in 3.7.

   - bpo-28835(2): Fix a regression introduced in
     warnings.catch_warnings(): call warnings.showwarning() if it was
     overridden inside the context manager.

   - bpo-27172(3): To assist with upgrades from 2.7, the previously
     documented deprecation of ‘inspect.getfullargspec()’ has been
     reversed.  This decision may be revisited again after the Python
     2.7 branch is no longer officially supported.

   - bpo-26273(4): Add new ‘socket.TCP_CONGESTION’ (Linux 2.6.13) and
     ‘socket.TCP_USER_TIMEOUT’ (Linux 2.6.37) constants.  Patch written
     by Omar Sandoval.

   - bpo-24142(5): Reading a corrupt config file left configparser in an
     invalid state.  Original patch by Florian Höch.

   - bpo-28843(6): Fix asyncio C Task to handle exceptions
     __traceback__.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27030

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28835

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27172

   (4) https://bugs.python.org/issue?@action=redirect&bpo=26273

   (5) https://bugs.python.org/issue?@action=redirect&bpo=24142

   (6) https://bugs.python.org/issue?@action=redirect&bpo=28843


File: python.info,  Node: C API<59>,  Next: Documentation<60>,  Prev: Library<67>,  Up: Python 3 6 0 release candidate 1

1.23.76.3 C API
...............

   - bpo-28808(1): PyUnicode_CompareWithASCIIString() now never raises
     exceptions.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28808


File: python.info,  Node: Documentation<60>,  Next: Tools/Demos<36>,  Prev: C API<59>,  Up: Python 3 6 0 release candidate 1

1.23.76.4 Documentation
.......................

   - bpo-23722(1): The data model reference and the porting section in
     the What's New guide now cover the additional ‘__classcell__’
     handling needed for custom metaclasses to fully support PEP 487(2)
     and zero-argument ‘super()’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23722

   (2) https://peps.python.org/pep-0487/


File: python.info,  Node: Tools/Demos<36>,  Prev: Documentation<60>,  Up: Python 3 6 0 release candidate 1

1.23.76.5 Tools/Demos
.....................

   - bpo-28023(1): Fix python-gdb.py didn't support new dict
     implementation.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28023


File: python.info,  Node: Python 3 6 0 beta 4,  Next: Python 3 6 0 beta 3,  Prev: Python 3 6 0 release candidate 1,  Up: Changelog（更動日誌）

1.23.77 Python 3.6.0 beta 4
---------------------------

'Release date: 2016-11-21'

* Menu:

* Core and Builtins: Core and Builtins<69>.
* Library: Library<68>.
* Documentation: Documentation<61>.
* Tests: Tests<61>.
* Build: Build<67>.


File: python.info,  Node: Core and Builtins<69>,  Next: Library<68>,  Up: Python 3 6 0 beta 4

1.23.77.1 Core and Builtins
...........................

   - bpo-28532(1): Show sys.version when -V option is supplied twice.

   - bpo-27100(2): The with-statement now checks for __enter__ before it
     checks for __exit__.  This gives less confusing error messages when
     both methods are missing.  Patch by Jonathan Ellington.

   - bpo-28746(3): Fix the set_inheritable() file descriptor method on
     platforms that do not have the ioctl FIOCLEX and FIONCLEX commands.

   - bpo-26920(4): Fix not getting the locale's charset upon
     initializing the interpreter, on platforms that do not have
     langinfo.

   - bpo-28648(5): Fixed crash in Py_DecodeLocale() in debug build on
     Mac OS X when decode astral characters.  Patch by Xiang Zhang.

   - bpo-19398(6): Extra slash no longer added to sys.path components in
     case of empty compile-time PYTHONPATH components.

   - bpo-28665(7): Improve speed of the STORE_DEREF opcode by 40%.

   - bpo-28583(8): PyDict_SetDefault didn't combine split table when
     needed.  Patch by Xiang Zhang.

   - bpo-27243(9): Change PendingDeprecationWarning ->
     DeprecationWarning.  As it was agreed in the issue, __aiter__
     returning an awaitable should result in PendingDeprecationWarning
     in 3.5 and in DeprecationWarning in 3.6.

   - bpo-26182(10): Fix a refleak in code that raises
     DeprecationWarning.

   - bpo-28721(11): Fix asynchronous generators aclose() and athrow() to
     handle StopAsyncIteration propagation properly.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28532

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27100

   (3) https://bugs.python.org/issue?@action=redirect&bpo=28746

   (4) https://bugs.python.org/issue?@action=redirect&bpo=26920

   (5) https://bugs.python.org/issue?@action=redirect&bpo=28648

   (6) https://bugs.python.org/issue?@action=redirect&bpo=19398

   (7) https://bugs.python.org/issue?@action=redirect&bpo=28665

   (8) https://bugs.python.org/issue?@action=redirect&bpo=28583

   (9) https://bugs.python.org/issue?@action=redirect&bpo=27243

   (10) https://bugs.python.org/issue?@action=redirect&bpo=26182

   (11) https://bugs.python.org/issue?@action=redirect&bpo=28721


File: python.info,  Node: Library<68>,  Next: Documentation<61>,  Prev: Core and Builtins<69>,  Up: Python 3 6 0 beta 4

1.23.77.2 Library
.................

   - bpo-28752(1): Restored the __reduce__() methods of datetime
     objects.

   - bpo-28727(2): Regular expression patterns, _sre.SRE_Pattern objects
     created by re.compile(), become comparable (only x==y and x!=y
     operators).  This change should fix the bpo-18383(3): don't
     duplicate warning filters when the warnings module is reloaded
     (thing usually only done in unit tests).

   - bpo-20572(4): The subprocess.Popen.wait method's undocumented
     endtime parameter now raises a DeprecationWarning.

   - bpo-25659(5): In ctypes, prevent a crash calling the from_buffer()
     and from_buffer_copy() methods on abstract classes like Array.

   - bpo-19717(6): Makes Path.resolve() succeed on paths that do not
     exist.  Patch by Vajrasky Kok

   - bpo-28563(7): Fixed possible DoS and arbitrary code execution when
     handle plural form selections in the gettext module.  The
     expression parser now supports exact syntax supported by GNU
     gettext.

   - bpo-28387(8): Fixed possible crash in _io.TextIOWrapper deallocator
     when the garbage collector is invoked in other thread.  Based on
     patch by Sebastian Cufre.

   - bpo-28600(9): Optimize loop.call_soon.

   - bpo-28613(10): Fix get_event_loop() return the current loop if
     called from coroutines/callbacks.

   - bpo-28634(11): Fix asyncio.isfuture() to support unittest.Mock.

   - bpo-26081(12): Fix refleak in _asyncio.Future.__iter__().throw.

   - bpo-28639(13): Fix inspect.isawaitable to always return bool Patch
     by Justin Mayfield.

   - bpo-28652(14): Make loop methods reject socket kinds they do not
     support.

   - bpo-28653(15): Fix a refleak in functools.lru_cache.

   - bpo-28703(16): Fix asyncio.iscoroutinefunction to handle Mock
     objects.

   - bpo-28704(17): Fix create_unix_server to support Path-like objects
     (PEP 519).

   - bpo-28720(18): Add collections.abc.AsyncGenerator.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28752

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28727

   (3) https://bugs.python.org/issue?@action=redirect&bpo=18383

   (4) https://bugs.python.org/issue?@action=redirect&bpo=20572

   (5) https://bugs.python.org/issue?@action=redirect&bpo=25659

   (6) https://bugs.python.org/issue?@action=redirect&bpo=19717

   (7) https://bugs.python.org/issue?@action=redirect&bpo=28563

   (8) https://bugs.python.org/issue?@action=redirect&bpo=28387

   (9) https://bugs.python.org/issue?@action=redirect&bpo=28600

   (10) https://bugs.python.org/issue?@action=redirect&bpo=28613

   (11) https://bugs.python.org/issue?@action=redirect&bpo=28634

   (12) https://bugs.python.org/issue?@action=redirect&bpo=26081

   (13) https://bugs.python.org/issue?@action=redirect&bpo=28639

   (14) https://bugs.python.org/issue?@action=redirect&bpo=28652

   (15) https://bugs.python.org/issue?@action=redirect&bpo=28653

   (16) https://bugs.python.org/issue?@action=redirect&bpo=28703

   (17) https://bugs.python.org/issue?@action=redirect&bpo=28704

   (18) https://bugs.python.org/issue?@action=redirect&bpo=28720


File: python.info,  Node: Documentation<61>,  Next: Tests<61>,  Prev: Library<68>,  Up: Python 3 6 0 beta 4

1.23.77.3 Documentation
.......................

   - bpo-28513(1): Documented command-line interface of zipfile.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28513


File: python.info,  Node: Tests<61>,  Next: Build<67>,  Prev: Documentation<61>,  Up: Python 3 6 0 beta 4

1.23.77.4 Tests
...............

   - bpo-28666(1): Now test.support.rmtree is able to remove unwritable
     or unreadable directories.

   - bpo-23839(2): Various caches now are cleared before running every
     test file.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28666

   (2) https://bugs.python.org/issue?@action=redirect&bpo=23839


File: python.info,  Node: Build<67>,  Prev: Tests<61>,  Up: Python 3 6 0 beta 4

1.23.77.5 Build
...............

   - bpo-10656(1): Fix out-of-tree building on AIX. Patch by Tristan
     Carel and Michael Haubenwallner.

   - bpo-26359(2): Rename -with-optimiations to -enable-optimizations.

   - bpo-28676(3): Prevent missing 'getentropy' declaration warning on
     macOS. Patch by Gareth Rees.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=10656

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26359

   (3) https://bugs.python.org/issue?@action=redirect&bpo=28676


File: python.info,  Node: Python 3 6 0 beta 3,  Next: Python 3 6 0 beta 2,  Prev: Python 3 6 0 beta 4,  Up: Changelog（更動日誌）

1.23.78 Python 3.6.0 beta 3
---------------------------

'Release date: 2016-10-31'

* Menu:

* Core and Builtins: Core and Builtins<70>.
* Library: Library<69>.
* Windows: Windows<59>.
* Build: Build<68>.
* Tests: Tests<62>.


File: python.info,  Node: Core and Builtins<70>,  Next: Library<69>,  Up: Python 3 6 0 beta 3

1.23.78.1 Core and Builtins
...........................

   - bpo-28128(1): Deprecation warning for invalid str and byte escape
     sequences now prints better information about where the error
     occurs.  Patch by Serhiy Storchaka and Eric Smith.

   - bpo-28509(2): dict.update() no longer allocate unnecessary large
     memory.

   - bpo-28426(3): Fixed potential crash in PyUnicode_AsDecodedObject()
     in debug build.

   - bpo-28517(4): Fixed of-by-one error in the peephole optimizer that
     caused keeping unreachable code.

   - bpo-28214(5): Improved exception reporting for problematic
     __set_name__ attributes.

   - bpo-23782(6): Fixed possible memory leak in _PyTraceback_Add() and
     exception loss in PyTraceBack_Here().

   - bpo-28471(7): Fix "Python memory allocator called without holding
     the GIL" crash in socket.setblocking.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28128

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28509

   (3) https://bugs.python.org/issue?@action=redirect&bpo=28426

   (4) https://bugs.python.org/issue?@action=redirect&bpo=28517

   (5) https://bugs.python.org/issue?@action=redirect&bpo=28214

   (6) https://bugs.python.org/issue?@action=redirect&bpo=23782

   (7) https://bugs.python.org/issue?@action=redirect&bpo=28471


File: python.info,  Node: Library<69>,  Next: Windows<59>,  Prev: Core and Builtins<70>,  Up: Python 3 6 0 beta 3

1.23.78.2 Library
.................

   - bpo-27517(1): LZMA compressor and decompressor no longer raise
     exceptions if given empty data twice.  Patch by Benjamin Fogle.

   - bpo-28549(2): Fixed segfault in curses's addch() with ncurses6.

   - bpo-28449(3): tarfile.open() with mode "r" or "r:" now tries to
     open a tar file with compression before trying to open it without
     compression.  Otherwise it had 50% chance failed with
     ignore_zeros=True.

   - bpo-23262(4): The webbrowser module now supports Firefox 36+ and
     derived browsers.  Based on patch by Oleg Broytman.

   - bpo-27939(5): Fixed bugs in tkinter.ttk.LabeledScale and
     tkinter.Scale caused by representing the scale as float value
     internally in Tk.  tkinter.IntVar now works if float value is set
     to underlying Tk variable.

   - bpo-18844(6): The various ways of specifying weights for
     random.choices() now produce the same result sequences.

   - bpo-28255(7): calendar.TextCalendar().prmonth() no longer prints a
     space at the start of new line after printing a month's calendar.
     Patch by Xiang Zhang.

   - bpo-20491(8): The textwrap.TextWrapper class now honors
     non-breaking spaces.  Based on patch by Kaarle Ritvanen.

   - bpo-28353(9): os.fwalk() no longer fails on broken links.

   - bpo-28430(10): Fix iterator of C implemented asyncio.Future doesn't
     accept non-None value is passed to it.send(val).

   - bpo-27025(11): Generated names for Tkinter widgets now start by the
     "!"  prefix for readability.

   - bpo-25464(12): Fixed HList.header_exists() in tkinter.tix module by
     addin a workaround to Tix library bug.

   - bpo-28488(13): shutil.make_archive() no longer adds entry "./" to
     ZIP archive.

   - bpo-25953(14): re.sub() now raises an error for invalid numerical
     group reference in replacement template even if the pattern is not
     found in the string.  Error message for invalid group reference now
     includes the group index and the position of the reference.  Based
     on patch by SilentGhost.

   - bpo-18219(15): Optimize csv.DictWriter for large number of columns.
     Patch by Mariatta Wijaya.

   - bpo-28448(16): Fix C implemented asyncio.Future didn't work on
     Windows.

   - bpo-28480(17): Fix error building socket module when multithreading
     is disabled.

   - bpo-24452(18): Make webbrowser support Chrome on Mac OS X.

   - bpo-20766(19): Fix references leaked by pdb in the handling of
     SIGINT handlers.

   - bpo-28492(20): Fix how StopIteration exception is raised in
     _asyncio.Future.

   - bpo-28500(21): Fix asyncio to handle async gens GC from another
     thread.

   - bpo-26923(22): Fix asyncio.Gather to refuse being cancelled once
     all children are done.  Patch by Johannes Ebke.

   - bpo-26796(23): Don't configure the number of workers for default
     threadpool executor.  Initial patch by Hans Lawrenz.

   - bpo-28544(24): Implement asyncio.Task in C.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27517

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28549

   (3) https://bugs.python.org/issue?@action=redirect&bpo=28449

   (4) https://bugs.python.org/issue?@action=redirect&bpo=23262

   (5) https://bugs.python.org/issue?@action=redirect&bpo=27939

   (6) https://bugs.python.org/issue?@action=redirect&bpo=18844

   (7) https://bugs.python.org/issue?@action=redirect&bpo=28255

   (8) https://bugs.python.org/issue?@action=redirect&bpo=20491

   (9) https://bugs.python.org/issue?@action=redirect&bpo=28353

   (10) https://bugs.python.org/issue?@action=redirect&bpo=28430

   (11) https://bugs.python.org/issue?@action=redirect&bpo=27025

   (12) https://bugs.python.org/issue?@action=redirect&bpo=25464

   (13) https://bugs.python.org/issue?@action=redirect&bpo=28488

   (14) https://bugs.python.org/issue?@action=redirect&bpo=25953

   (15) https://bugs.python.org/issue?@action=redirect&bpo=18219

   (16) https://bugs.python.org/issue?@action=redirect&bpo=28448

   (17) https://bugs.python.org/issue?@action=redirect&bpo=28480

   (18) https://bugs.python.org/issue?@action=redirect&bpo=24452

   (19) https://bugs.python.org/issue?@action=redirect&bpo=20766

   (20) https://bugs.python.org/issue?@action=redirect&bpo=28492

   (21) https://bugs.python.org/issue?@action=redirect&bpo=28500

   (22) https://bugs.python.org/issue?@action=redirect&bpo=26923

   (23) https://bugs.python.org/issue?@action=redirect&bpo=26796

   (24) https://bugs.python.org/issue?@action=redirect&bpo=28544


File: python.info,  Node: Windows<59>,  Next: Build<68>,  Prev: Library<69>,  Up: Python 3 6 0 beta 3

1.23.78.3 Windows
.................

   - bpo-28522(1): Fixes mishandled buffer reallocation in getpathp.c

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28522


File: python.info,  Node: Build<68>,  Next: Tests<62>,  Prev: Windows<59>,  Up: Python 3 6 0 beta 3

1.23.78.4 Build
...............

   - bpo-28444(1): Fix missing extensions modules when cross compiling.

   - bpo-28208(2): Update Windows build and OS X installers to use
     SQLite 3.14.2.

   - bpo-28248(3): Update Windows build and OS X installers to use
     OpenSSL 1.0.2j.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28444

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28208

   (3) https://bugs.python.org/issue?@action=redirect&bpo=28248


File: python.info,  Node: Tests<62>,  Prev: Build<68>,  Up: Python 3 6 0 beta 3

1.23.78.5 Tests
...............

   - bpo-26944(1): Fix test_posix for Android where 'id -G' is entirely
     wrong or missing the effective gid.

   - bpo-28409(2): regrtest: fix the parser of command line arguments.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26944

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28409


File: python.info,  Node: Python 3 6 0 beta 2,  Next: Python 3 6 0 beta 1,  Prev: Python 3 6 0 beta 3,  Up: Changelog（更動日誌）

1.23.79 Python 3.6.0 beta 2
---------------------------

'Release date: 2016-10-10'

* Menu:

* Core and Builtins: Core and Builtins<71>.
* Library: Library<70>.
* Windows: Windows<60>.
* C API: C API<60>.
* Build: Build<69>.
* Tests: Tests<63>.


File: python.info,  Node: Core and Builtins<71>,  Next: Library<70>,  Up: Python 3 6 0 beta 2

1.23.79.1 Core and Builtins
...........................

   - bpo-28183(1): Optimize and cleanup dict iteration.

   - bpo-26081(2): Added C implementation of asyncio.Future.  Original
     patch by Yury Selivanov.

   - bpo-28379(3): Added sanity checks and tests for
     PyUnicode_CopyCharacters().  Patch by Xiang Zhang.

   - bpo-28376(4): The type of long range iterator is now registered as
     Iterator.  Patch by Oren Milman.

   - bpo-28376(5): Creating instances of range_iterator by calling
     range_iterator type now is deprecated.  Patch by Oren Milman.

   - bpo-28376(6): The constructor of range_iterator now checks that
     step is not 0.  Patch by Oren Milman.

   - bpo-26906(7): Resolving special methods of uninitialized type now
     causes implicit initialization of the type instead of a fail.

   - bpo-18287(8): PyType_Ready() now checks that tp_name is not NULL.
     Original patch by Niklas Koep.

   - bpo-24098(9): Fixed possible crash when AST is changed in process
     of compiling it.

   - bpo-28201(10): Dict reduces possibility of 2nd conflict in hash
     table when hashes have same lower bits.

   - bpo-28350(11): String constants with null character no longer
     interned.

   - bpo-26617(12): Fix crash when GC runs during weakref callbacks.

   - bpo-27942(13): String constants now interned recursively in tuples
     and frozensets.

   - bpo-21578(14): Fixed misleading error message when ImportError
     called with invalid keyword args.

   - bpo-28203(15): Fix incorrect type in complex(1.0, {2:3}) error
     message.  Patch by Soumya Sharma.

   - bpo-28086(16): Single var-positional argument of tuple subtype was
     passed unscathed to the C-defined function.  Now it is converted to
     exact tuple.

   - bpo-28214(17): Now __set_name__ is looked up on the class instead
     of the instance.

   - bpo-27955(18): Fallback on reading /dev/urandom device when the
     getrandom() syscall fails with EPERM, for example when blocked by
     SECCOMP.

   - bpo-28192(19): Don't import readline in isolated mode.

   - Upgrade internal unicode databases to Unicode version 9.0.0.

   - bpo-28131(20): Fix a regression in zipimport's compile_source().
     zipimport should use the same optimization level as the
     interpreter.

   - bpo-28126(21): Replace Py_MEMCPY with memcpy().  Visual Studio can
     properly optimize memcpy().

   - bpo-28120(22): Fix dict.pop() for splitted dictionary when trying
     to remove a "pending key" (Not yet inserted in split-table).  Patch
     by Xiang Zhang.

   - bpo-26182(23): Raise DeprecationWarning when async and await
     keywords are used as variable/attribute/class/function name.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28183

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26081

   (3) https://bugs.python.org/issue?@action=redirect&bpo=28379

   (4) https://bugs.python.org/issue?@action=redirect&bpo=28376

   (5) https://bugs.python.org/issue?@action=redirect&bpo=28376

   (6) https://bugs.python.org/issue?@action=redirect&bpo=28376

   (7) https://bugs.python.org/issue?@action=redirect&bpo=26906

   (8) https://bugs.python.org/issue?@action=redirect&bpo=18287

   (9) https://bugs.python.org/issue?@action=redirect&bpo=24098

   (10) https://bugs.python.org/issue?@action=redirect&bpo=28201

   (11) https://bugs.python.org/issue?@action=redirect&bpo=28350

   (12) https://bugs.python.org/issue?@action=redirect&bpo=26617

   (13) https://bugs.python.org/issue?@action=redirect&bpo=27942

   (14) https://bugs.python.org/issue?@action=redirect&bpo=21578

   (15) https://bugs.python.org/issue?@action=redirect&bpo=28203

   (16) https://bugs.python.org/issue?@action=redirect&bpo=28086

   (17) https://bugs.python.org/issue?@action=redirect&bpo=28214

   (18) https://bugs.python.org/issue?@action=redirect&bpo=27955

   (19) https://bugs.python.org/issue?@action=redirect&bpo=28192

   (20) https://bugs.python.org/issue?@action=redirect&bpo=28131

   (21) https://bugs.python.org/issue?@action=redirect&bpo=28126

   (22) https://bugs.python.org/issue?@action=redirect&bpo=28120

   (23) https://bugs.python.org/issue?@action=redirect&bpo=26182


File: python.info,  Node: Library<70>,  Next: Windows<60>,  Prev: Core and Builtins<71>,  Up: Python 3 6 0 beta 2

1.23.79.2 Library
.................

   - bpo-27998(1): Fixed bytes path support in os.scandir() on Windows.
     Patch by Eryk Sun.

   - bpo-28317(2): The disassembler now decodes FORMAT_VALUE argument.

   - bpo-26293(3): Fixed writing ZIP files that starts not from the
     start of the file.  Offsets in ZIP file now are relative to the
     start of the archive in conforming to the specification.

   - bpo-28380(4): unittest.mock Mock autospec functions now properly
     support assert_called, assert_not_called, and assert_called_once.

   - bpo-27181(5): remove statistics.geometric_mean and defer until 3.7.

   - bpo-28229(6): lzma module now supports pathlib.

   - bpo-28321(7): Fixed writing non-BMP characters with binary format
     in plistlib.

   - bpo-28225(8): bz2 module now supports pathlib.  Initial patch by
     Ethan Furman.

   - bpo-28227(9): gzip now supports pathlib.  Patch by Ethan Furman.

   - bpo-27358(10): Optimized merging var-keyword arguments and improved
     error message when passing a non-mapping as a var-keyword argument.

   - bpo-28257(11): Improved error message when passing a non-iterable
     as a var-positional argument.  Added opcode
     BUILD_TUPLE_UNPACK_WITH_CALL.

   - bpo-28322(12): Fixed possible crashes when unpickle itertools
     objects from incorrect pickle data.  Based on patch by John Leitch.

   - bpo-28228(13): imghdr now supports pathlib.

   - bpo-28226(14): compileall now supports pathlib.

   - bpo-28314(15): Fix function declaration (C flags) for the
     getiterator() method of xml.etree.ElementTree.Element.

   - bpo-28148(16): Stop using localtime() and gmtime() in the time
     module.  Introduced platform independent _PyTime_localtime API that
     is similar to POSIX localtime_r, but available on all platforms.
     Patch by Ed Schouten.

   - bpo-28253(17): Fixed calendar functions for extreme months: 0001-01
     and 9999-12.  Methods itermonthdays() and itermonthdays2() are
     reimplemented so that they don't call itermonthdates() which can
     cause datetime.date under/overflow.

   - bpo-28275(18): Fixed possible use after free in the decompress()
     methods of the LZMADecompressor and BZ2Decompressor classes.
     Original patch by John Leitch.

   - bpo-27897(19): Fixed possible crash in
     sqlite3.Connection.create_collation() if pass invalid string-like
     object as a name.  Patch by Xiang Zhang.

   - bpo-18844(20): random.choices() now has k as a keyword-only
     argument to improve the readability of common cases and come into
     line with the signature used in other languages.

   - bpo-18893(21): Fix invalid exception handling in
     Lib/ctypes/macholib/dyld.py.  Patch by Madison May.

   - bpo-27611(22): Fixed support of default root window in the
     tkinter.tix module.  Added the master parameter in the DisplayStyle
     constructor.

   - bpo-27348(23): In the traceback module, restore the formatting of
     exception messages like "Exception: None".  This fixes a regression
     introduced in 3.5a2.

   - bpo-25651(24): Allow false values to be used for msg parameter of
     subTest().

   - bpo-27778(25): Fix a memory leak in os.getrandom() when the
     getrandom() is interrupted by a signal and a signal handler raises
     a Python exception.

   - bpo-28200(26): Fix memory leak on Windows in the os module (fix
     path_converter() function).

   - bpo-25400(27): RobotFileParser now correctly returns default values
     for crawl_delay and request_rate.  Initial patch by Peter Wirtz.

   - bpo-27932(28): Prevent memory leak in win32_ver().

   - Fix UnboundLocalError in socket._sendfile_use_sendfile.

   - bpo-28075(29): Check for ERROR_ACCESS_DENIED in Windows
     implementation of os.stat().  Patch by Eryk Sun.

   - bpo-22493(30): Warning message emitted by using inline flags in the
     middle of regular expression now contains a (truncated) regex
     pattern.  Patch by Tim Graham.

   - bpo-25270(31): Prevent codecs.escape_encode() from raising
     SystemError when an empty bytestring is passed.

   - bpo-28181(32): Get antigravity over HTTPS. Patch by Kaartic
     Sivaraam.

   - bpo-25895(33): Enable WebSocket URL schemes in
     urllib.parse.urljoin.  Patch by Gergely Imreh and Markus
     Holtermann.

   - bpo-28114(34): Fix a crash in parse_envlist() when env contains
     byte strings.  Patch by Eryk Sun.

   - bpo-27599(35): Fixed buffer overrun in binascii.b2a_qp() and
     binascii.a2b_qp().

   - bpo-27906(36): Fix socket accept exhaustion during high TCP
     traffic.  Patch by Kevin Conway.

   - bpo-28174(37): Handle when SO_REUSEPORT isn't properly supported.
     Patch by Seth Michael Larson.

   - bpo-26654(38): Inspect functools.partial in
     asyncio.Handle.__repr__.  Patch by iceboy.

   - bpo-26909(39): Fix slow pipes IO in asyncio.  Patch by INADA Naoki.

   - bpo-28176(40): Fix callbacks race in
     asyncio.SelectorLoop.sock_connect.

   - bpo-27759(41): Fix selectors incorrectly retain invalid file
     descriptors.  Patch by Mark Williams.

   - bpo-28368(42): Refuse monitoring processes if the child watcher has
     no loop attached.  Patch by Vincent Michel.

   - bpo-28369(43): Raise RuntimeError when transport's FD is used with
     add_reader, add_writer, etc.

   - bpo-28370(44): Speedup asyncio.StreamReader.readexactly.  Patch by
     Коренберг Марк.

   - bpo-28371(45): Deprecate passing asyncio.Handles to
     run_in_executor.

   - bpo-28372(46): Fix asyncio to support formatting of non-python
     coroutines.

   - bpo-28399(47): Remove UNIX socket from FS before binding.  Patch by
     Коренберг Марк.

   - bpo-27972(48): Prohibit Tasks to await on themselves.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27998

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28317

   (3) https://bugs.python.org/issue?@action=redirect&bpo=26293

   (4) https://bugs.python.org/issue?@action=redirect&bpo=28380

   (5) https://bugs.python.org/issue?@action=redirect&bpo=27181

   (6) https://bugs.python.org/issue?@action=redirect&bpo=28229

   (7) https://bugs.python.org/issue?@action=redirect&bpo=28321

   (8) https://bugs.python.org/issue?@action=redirect&bpo=28225

   (9) https://bugs.python.org/issue?@action=redirect&bpo=28227

   (10) https://bugs.python.org/issue?@action=redirect&bpo=27358

   (11) https://bugs.python.org/issue?@action=redirect&bpo=28257

   (12) https://bugs.python.org/issue?@action=redirect&bpo=28322

   (13) https://bugs.python.org/issue?@action=redirect&bpo=28228

   (14) https://bugs.python.org/issue?@action=redirect&bpo=28226

   (15) https://bugs.python.org/issue?@action=redirect&bpo=28314

   (16) https://bugs.python.org/issue?@action=redirect&bpo=28148

   (17) https://bugs.python.org/issue?@action=redirect&bpo=28253

   (18) https://bugs.python.org/issue?@action=redirect&bpo=28275

   (19) https://bugs.python.org/issue?@action=redirect&bpo=27897

   (20) https://bugs.python.org/issue?@action=redirect&bpo=18844

   (21) https://bugs.python.org/issue?@action=redirect&bpo=18893

   (22) https://bugs.python.org/issue?@action=redirect&bpo=27611

   (23) https://bugs.python.org/issue?@action=redirect&bpo=27348

   (24) https://bugs.python.org/issue?@action=redirect&bpo=25651

   (25) https://bugs.python.org/issue?@action=redirect&bpo=27778

   (26) https://bugs.python.org/issue?@action=redirect&bpo=28200

   (27) https://bugs.python.org/issue?@action=redirect&bpo=25400

   (28) https://bugs.python.org/issue?@action=redirect&bpo=27932

   (29) https://bugs.python.org/issue?@action=redirect&bpo=28075

   (30) https://bugs.python.org/issue?@action=redirect&bpo=22493

   (31) https://bugs.python.org/issue?@action=redirect&bpo=25270

   (32) https://bugs.python.org/issue?@action=redirect&bpo=28181

   (33) https://bugs.python.org/issue?@action=redirect&bpo=25895

   (34) https://bugs.python.org/issue?@action=redirect&bpo=28114

   (35) https://bugs.python.org/issue?@action=redirect&bpo=27599

   (36) https://bugs.python.org/issue?@action=redirect&bpo=27906

   (37) https://bugs.python.org/issue?@action=redirect&bpo=28174

   (38) https://bugs.python.org/issue?@action=redirect&bpo=26654

   (39) https://bugs.python.org/issue?@action=redirect&bpo=26909

   (40) https://bugs.python.org/issue?@action=redirect&bpo=28176

   (41) https://bugs.python.org/issue?@action=redirect&bpo=27759

   (42) https://bugs.python.org/issue?@action=redirect&bpo=28368

   (43) https://bugs.python.org/issue?@action=redirect&bpo=28369

   (44) https://bugs.python.org/issue?@action=redirect&bpo=28370

   (45) https://bugs.python.org/issue?@action=redirect&bpo=28371

   (46) https://bugs.python.org/issue?@action=redirect&bpo=28372

   (47) https://bugs.python.org/issue?@action=redirect&bpo=28399

   (48) https://bugs.python.org/issue?@action=redirect&bpo=27972


File: python.info,  Node: Windows<60>,  Next: C API<60>,  Prev: Library<70>,  Up: Python 3 6 0 beta 2

1.23.79.3 Windows
.................

   - bpo-28402(1): Adds signed catalog files for stdlib on Windows.

   - bpo-28333(2): Enables Unicode for ps1/ps2 and input() prompts.
     (Patch by Eryk Sun)

   - bpo-28251(3): Improvements to help manuals on Windows.

   - bpo-28110(4): launcher.msi has different product codes between
     32-bit and 64-bit

   - bpo-28161(5): Opening CON for write access fails

   - bpo-28162(6): WindowsConsoleIO readall() fails if first line starts
     with Ctrl+Z

   - bpo-28163(7): WindowsConsoleIO fileno() passes wrong flags to
     _open_osfhandle

   - bpo-28164(8): _PyIO_get_console_type fails for various paths

   - bpo-28137(9): Renames Windows path file to ._pth

   - bpo-28138(10): Windows ._pth file should allow import site

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28402

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28333

   (3) https://bugs.python.org/issue?@action=redirect&bpo=28251

   (4) https://bugs.python.org/issue?@action=redirect&bpo=28110

   (5) https://bugs.python.org/issue?@action=redirect&bpo=28161

   (6) https://bugs.python.org/issue?@action=redirect&bpo=28162

   (7) https://bugs.python.org/issue?@action=redirect&bpo=28163

   (8) https://bugs.python.org/issue?@action=redirect&bpo=28164

   (9) https://bugs.python.org/issue?@action=redirect&bpo=28137

   (10) https://bugs.python.org/issue?@action=redirect&bpo=28138


File: python.info,  Node: C API<60>,  Next: Build<69>,  Prev: Windows<60>,  Up: Python 3 6 0 beta 2

1.23.79.4 C API
...............

   - bpo-28426(1): Deprecated undocumented functions
     PyUnicode_AsEncodedObject(), PyUnicode_AsDecodedObject(),
     PyUnicode_AsDecodedUnicode() and PyUnicode_AsEncodedUnicode().

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28426


File: python.info,  Node: Build<69>,  Next: Tests<63>,  Prev: C API<60>,  Up: Python 3 6 0 beta 2

1.23.79.5 Build
...............

   - bpo-28258(1): Fixed build with Estonian locale (python-config and
     distclean targets in Makefile).  Patch by Arfrever Frehtes
     Taifersar Arahesis.

   - bpo-26661(2): setup.py now detects system libffi with multiarch
     wrapper.

   - bpo-15819(3): Remove redundant include search directory option for
     building outside the source tree.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28258

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26661

   (3) https://bugs.python.org/issue?@action=redirect&bpo=15819


File: python.info,  Node: Tests<63>,  Prev: Build<69>,  Up: Python 3 6 0 beta 2

1.23.79.6 Tests
...............

   - bpo-28217(1): Adds _testconsole module to test console input.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28217


File: python.info,  Node: Python 3 6 0 beta 1,  Next: Python 3 6 0 alpha 4,  Prev: Python 3 6 0 beta 2,  Up: Changelog（更動日誌）

1.23.80 Python 3.6.0 beta 1
---------------------------

'Release date: 2016-09-12'

* Menu:

* Core and Builtins: Core and Builtins<72>.
* Library: Library<71>.
* IDLE: IDLE<50>.
* C API: C API<61>.
* Tests: Tests<64>.
* Build: Build<70>.
* Tools/Demos: Tools/Demos<37>.
* Windows: Windows<61>.


File: python.info,  Node: Core and Builtins<72>,  Next: Library<71>,  Up: Python 3 6 0 beta 1

1.23.80.1 Core and Builtins
...........................

   - bpo-23722(1): The __class__ cell used by zero-argument super() is
     now initialized from type.__new__ rather than __build_class__, so
     class methods relying on that will now work correctly when called
     from metaclass methods during class creation.  Patch by Martin
     Teichmann.

   - bpo-25221(2): Fix corrupted result from PyLong_FromLong(0) when
     Python is compiled with NSMALLPOSINTS = 0.

   - bpo-27080(3): Implement formatting support for PEP 515(4).  Initial
     patch by Chris Angelico.

   - bpo-27199(5): In tarfile, expose copyfileobj bufsize to improve
     throughput.  Patch by Jason Fried.

   - bpo-27948(6): In f-strings, only allow backslashes inside the
     braces (where the expressions are).  This is a breaking change from
     the 3.6 alpha releases, where backslashes are allowed anywhere in
     an f-string.  Also, require that expressions inside f-strings be
     enclosed within literal braces, and not escapes like
     ‘f'\x7b"hi"\x7d'’.

   - bpo-28046(7): Remove platform-specific directories from sys.path.

   - bpo-28071(8): Add early-out for differencing from an empty set.

   - bpo-25758(9): Prevents zipimport from unnecessarily encoding a
     filename (patch by Eryk Sun)

   - bpo-25856(10): The __module__ attribute of extension classes and
     functions now is interned.  This leads to more compact pickle data
     with protocol 4.

   - bpo-27213(11): Rework CALL_FUNCTION* opcodes to produce shorter and
     more efficient bytecode.  Patch by Demur Rumed, design by Serhiy
     Storchaka, reviewed by Serhiy Storchaka and Victor Stinner.

   - bpo-26331(12): Implement tokenizing support for PEP 515(13).  Patch
     by Georg Brandl.

   - bpo-27999(14): Make "global after use" a SyntaxError, and ditto for
     nonlocal.  Patch by Ivan Levkivskyi.

   - bpo-28003(15): Implement PEP 525(16) - Asynchronous Generators.

   - bpo-27985(17): Implement PEP 526(18) - Syntax for Variable
     Annotations.  Patch by Ivan Levkivskyi.

   - bpo-26058(19): Add a new private version to the builtin dict type,
     incremented at each dictionary creation and at each dictionary
     change.  Implementation of the PEP 509.

   - bpo-27364(20): A backslash-character pair that is not a valid
     escape sequence now generates a DeprecationWarning.  Patch by
     Emanuel Barry.

   - bpo-27350(21): ‘dict’ implementation is changed like PyPy.  It is
     more compact and preserves insertion order.  (Concept developed by
     Raymond Hettinger and patch by Inada Naoki.)

   - bpo-27911(22): Remove unnecessary error checks in
     ‘exec_builtin_or_dynamic()’.

   - bpo-27078(23): Added BUILD_STRING opcode.  Optimized f-strings
     evaluation.

   - bpo-17884(24): Python now requires systems with inttypes.h and
     stdint.h

   - bpo-27961(25): Require platforms to support ‘long long’.  Python
     hasn't compiled without ‘long long’ for years, so this is basically
     a formality.

   - bpo-27355(26): Removed support for Windows CE. It was never
     finished, and Windows CE is no longer a relevant platform for
     Python.

   - Implement PEP 523(27).

   - bpo-27870(28): A left shift of zero by a large integer no longer
     attempts to allocate large amounts of memory.

   - bpo-25402(29): In int-to-decimal-string conversion, improve the
     estimate of the intermediate memory required, and remove an
     unnecessarily strict overflow check.  Patch by Serhiy Storchaka.

   - bpo-27214(30): In long_invert, be more careful about modifying
     object returned by long_add, and remove an unnecessary check for
     small longs.  Thanks Oren Milman for analysis and patch.

   - bpo-27506(31): Support passing the bytes/bytearray.translate()
     "delete" argument by keyword.

   - bpo-27812(32): Properly clear out a generator's frame's
     backreference to the generator to prevent crashes in frame.clear().

   - bpo-27811(33): Fix a crash when a coroutine that has not been
     awaited is finalized with warnings-as-errors enabled.

   - bpo-27587(34): Fix another issue found by PVS-Studio: Null pointer
     check after use of 'def' in _PyState_AddModule().  Initial patch by
     Christian Heimes.

   - bpo-27792(35): The modulo operation applied to ‘bool’ and other
     ‘int’ subclasses now always returns an ‘int’.  Previously the
     return type depended on the input values.  Patch by Xiang Zhang.

   - bpo-26984(36): int() now always returns an instance of exact int.

   - bpo-25604(37): Fix a minor bug in integer true division; this bug
     could potentially have caused off-by-one-ulp results on platforms
     with unreliable ldexp implementations.

   - bpo-24254(38): Make class definition namespace ordered by default.

   - bpo-27662(39): Fix an overflow check in ‘List_New’: the original
     code was checking against ‘Py_SIZE_MAX’ instead of the correct
     upper bound of ‘Py_SSIZE_T_MAX’.  Patch by Xiang Zhang.

   - bpo-27782(40): Multi-phase extension module import now correctly
     allows the ‘m_methods’ field to be used to add module level
     functions to instances of non-module types returned from
     ‘Py_create_mod’.  Patch by Xiang Zhang.

   - bpo-27936(41): The round() function accepted a second None argument
     for some types but not for others.  Fixed the inconsistency by
     accepting None for all numeric types.

   - bpo-27487(42): Warn if a submodule argument to "python -m" or
     runpy.run_module() is found in sys.modules after parent packages
     are imported, but before the submodule is executed.

   - bpo-27157(43): Make only type() itself accept the one-argument
     form.  Patch by Eryk Sun and Emanuel Barry.

   - bpo-27558(44): Fix a SystemError in the implementation of "raise"
     statement.  In a brand new thread, raise a RuntimeError since there
     is no active exception to reraise.  Patch written by Xiang Zhang.

   - bpo-28008(45): Implement PEP 530(46) - asynchronous comprehensions.

   - bpo-27942(47): Fix memory leak in codeobject.c

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23722

   (2) https://bugs.python.org/issue?@action=redirect&bpo=25221

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27080

   (4) https://peps.python.org/pep-0515/

   (5) https://bugs.python.org/issue?@action=redirect&bpo=27199

   (6) https://bugs.python.org/issue?@action=redirect&bpo=27948

   (7) https://bugs.python.org/issue?@action=redirect&bpo=28046

   (8) https://bugs.python.org/issue?@action=redirect&bpo=28071

   (9) https://bugs.python.org/issue?@action=redirect&bpo=25758

   (10) https://bugs.python.org/issue?@action=redirect&bpo=25856

   (11) https://bugs.python.org/issue?@action=redirect&bpo=27213

   (12) https://bugs.python.org/issue?@action=redirect&bpo=26331

   (13) https://peps.python.org/pep-0515/

   (14) https://bugs.python.org/issue?@action=redirect&bpo=27999

   (15) https://bugs.python.org/issue?@action=redirect&bpo=28003

   (16) https://peps.python.org/pep-0525/

   (17) https://bugs.python.org/issue?@action=redirect&bpo=27985

   (18) https://peps.python.org/pep-0526/

   (19) https://bugs.python.org/issue?@action=redirect&bpo=26058

   (20) https://bugs.python.org/issue?@action=redirect&bpo=27364

   (21) https://bugs.python.org/issue?@action=redirect&bpo=27350

   (22) https://bugs.python.org/issue?@action=redirect&bpo=27911

   (23) https://bugs.python.org/issue?@action=redirect&bpo=27078

   (24) https://bugs.python.org/issue?@action=redirect&bpo=17884

   (25) https://bugs.python.org/issue?@action=redirect&bpo=27961

   (26) https://bugs.python.org/issue?@action=redirect&bpo=27355

   (27) https://peps.python.org/pep-0523/

   (28) https://bugs.python.org/issue?@action=redirect&bpo=27870

   (29) https://bugs.python.org/issue?@action=redirect&bpo=25402

   (30) https://bugs.python.org/issue?@action=redirect&bpo=27214

   (31) https://bugs.python.org/issue?@action=redirect&bpo=27506

   (32) https://bugs.python.org/issue?@action=redirect&bpo=27812

   (33) https://bugs.python.org/issue?@action=redirect&bpo=27811

   (34) https://bugs.python.org/issue?@action=redirect&bpo=27587

   (35) https://bugs.python.org/issue?@action=redirect&bpo=27792

   (36) https://bugs.python.org/issue?@action=redirect&bpo=26984

   (37) https://bugs.python.org/issue?@action=redirect&bpo=25604

   (38) https://bugs.python.org/issue?@action=redirect&bpo=24254

   (39) https://bugs.python.org/issue?@action=redirect&bpo=27662

   (40) https://bugs.python.org/issue?@action=redirect&bpo=27782

   (41) https://bugs.python.org/issue?@action=redirect&bpo=27936

   (42) https://bugs.python.org/issue?@action=redirect&bpo=27487

   (43) https://bugs.python.org/issue?@action=redirect&bpo=27157

   (44) https://bugs.python.org/issue?@action=redirect&bpo=27558

   (45) https://bugs.python.org/issue?@action=redirect&bpo=28008

   (46) https://peps.python.org/pep-0530/

   (47) https://bugs.python.org/issue?@action=redirect&bpo=27942


File: python.info,  Node: Library<71>,  Next: IDLE<50>,  Prev: Core and Builtins<72>,  Up: Python 3 6 0 beta 1

1.23.80.2 Library
.................

   - bpo-28732(1): Fix crash in os.spawnv() with no elements in args

   - bpo-28485(2): Always raise ValueError for negative
     compileall.compile_dir(workers=...)  parameter, even when
     multithreading is unavailable.

   - bpo-28037(3): Use sqlite3_get_autocommit() instead of setting
     Connection->inTransaction manually.

   - bpo-25283(4): Attributes tm_gmtoff and tm_zone are now available on
     all platforms in the return values of time.localtime() and
     time.gmtime().

   - bpo-24454(5): Regular expression match object groups are now
     accessible using __getitem__.  "mo[x]" is equivalent to
     "mo.group(x)".

   - bpo-10740(6): sqlite3 no longer implicitly commit an open
     transaction before DDL statements.

   - bpo-17941(7): Add a 'module' parameter to collections.namedtuple().

   - bpo-22493(8): Inline flags now should be used only at the start of
     the regular expression.  Deprecation warning is emitted if uses
     them in the middle of the regular expression.

   - bpo-26885(9): xmlrpc now supports unmarshalling additional data
     types used by Apache XML-RPC implementation for numerics and None.

   - bpo-28070(10): Fixed parsing inline verbose flag in regular
     expressions.

   - bpo-19500(11): Add client-side SSL session resumption to the ssl
     module.

   - bpo-28022(12): Deprecate ssl-related arguments in favor of
     SSLContext.  The deprecation include manual creation of SSLSocket
     and certfile/keyfile (or similar) in ftplib, httplib, imaplib,
     smtplib, poplib and urllib.

   - bpo-28043(13): SSLContext has improved default settings:
     OP_NO_SSLv2, OP_NO_SSLv3, OP_NO_COMPRESSION,
     OP_CIPHER_SERVER_PREFERENCE, OP_SINGLE_DH_USE, OP_SINGLE_ECDH_USE
     and HIGH ciphers without MD5.

   - bpo-24693(14): Changed some RuntimeError's in the zipfile module to
     more appropriate types.  Improved some error messages and debugging
     output.

   - bpo-17909(15): ‘json.load’ and ‘json.loads’ now support binary
     input encoded as UTF-8, UTF-16 or UTF-32.  Patch by Serhiy
     Storchaka.

   - bpo-27137(16): the pure Python fallback implementation of
     ‘functools.partial’ now matches the behaviour of its accelerated C
     counterpart for subclassing, pickling and text representation
     purposes.  Patch by Emanuel Barry and Serhiy Storchaka.

   - Fix possible integer overflows and crashes in the mmap module with
     unusual usage patterns.

   - bpo-1703178(17): Fix the ability to pass the -link-objects option
     to the distutils build_ext command.

   - bpo-28019(18): itertools.count() no longer rounds non-integer step
     in range between 1.0 and 2.0 to 1.

   - bpo-18401(19): Pdb now supports the 'readrc' keyword argument to
     control whether .pdbrc files should be read.  Patch by Martin
     Matusiak and Sam Kimbrel.

   - bpo-25969(20): Update the lib2to3 grammar to handle the unpacking
     generalizations added in 3.5.

   - bpo-14977(21): mailcap now respects the order of the lines in the
     mailcap files ("first match"), as required by RFC 1542.  Patch by
     Michael Lazar.

   - bpo-28082(22): Convert re flag constants to IntFlag.

   - bpo-28025(23): Convert all ssl module constants to IntEnum and
     IntFlags.  SSLContext properties now return flags and enums.

   - bpo-23591(24): Add Flag, IntFlag, and auto() to enum module.

   - bpo-433028(25): Added support of modifier spans in regular
     expressions.

   - bpo-24594(26): Validates persist parameter when opening MSI
     database

   - bpo-17582(27): xml.etree.ElementTree nows preserves whitespaces in
     attributes (Patch by Duane Griffin.  Reviewed and approved by
     Stefan Behnel.)

   - bpo-28047(28): Fixed calculation of line length used for the base64
     CTE in the new email policies.

   - bpo-27576(29): Fix call order in OrderedDict.__init__().

   - email.generator.DecodedGenerator now supports the policy keyword.

   - bpo-28027(30): Remove undocumented modules from ‘Lib/plat-*’: IN,
     CDROM, DLFCN, TYPES, CDIO, and STROPTS.

   - bpo-27445(31): Don't pass str(_charset) to MIMEText.set_payload().
     Patch by Claude Paroz.

   - bpo-24277(32): The new email API is no longer provisional, and the
     docs have been reorganized and rewritten to emphasize the new API.

   - bpo-22450(33): urllib now includes an ‘Accept: */*’ header among
     the default headers.  This makes the results of REST API requests
     more consistent and predictable especially when proxy servers are
     involved.

   - lib2to3.pgen3.driver.load_grammar() now creates a stable cache file
     between runs given the same Grammar.txt input regardless of the
     hash randomization setting.

   - bpo-28005(34): Allow ImportErrors in encoding implementation to
     propagate.

   - bpo-26667(35): Support path-like objects in importlib.util.

   - bpo-27570(36): Avoid zero-length memcpy() etc calls with null
     source pointers in the "ctypes" and "array" modules.

   - bpo-22233(37): Break email header lines 'only' on the RFC specified
     CR and LF characters, not on arbitrary unicode line breaks.  This
     also fixes a bug in HTTP header parsing.

   - bpo-27331(38): The email.mime classes now all accept an optional
     policy keyword.

   - bpo-27988(39): Fix email iter_attachments incorrect mutation of
     payload list.

   - bpo-16113(40): Add SHA-3 and SHAKE support to hashlib module.

   - Eliminate a tautological-pointer-compare warning in _scproxy.c.

   - bpo-27776(41): The *note os.urandom(): 4c7. function does now block
     on Linux 3.17 and newer until the system urandom entropy pool is
     initialized to increase the security.  This change is part of the
     PEP 524(42).

   - bpo-27778(43): Expose the Linux ‘getrandom()’ syscall as a new
     *note os.getrandom(): c64. function.  This change is part of the
     PEP 524(44).

   - bpo-27691(45): Fix ssl module's parsing of GEN_RID subject
     alternative name fields in X.509 certs.

   - bpo-18844(46): Add random.choices().

   - bpo-25761(47): Improved error reporting about truncated pickle data
     in C implementation of unpickler.  UnpicklingError is now raised
     instead of AttributeError and ValueError in some cases.

   - bpo-26798(48): Add BLAKE2 (blake2b and blake2s) to hashlib.

   - bpo-26032(49): Optimized globbing in pathlib by using os.scandir();
     it is now about 1.5-4 times faster.

   - bpo-25596(50): Optimized glob() and iglob() functions in the glob
     module; they are now about 3-6 times faster.

   - bpo-27928(51): Add scrypt (password-based key derivation function)
     to hashlib module (requires OpenSSL 1.1.0).

   - bpo-27850(52): Remove 3DES from ssl module's default cipher list to
     counter measure sweet32 attack (CVE-2016-2183(53)).

   - bpo-27766(54): Add ChaCha20 Poly1305 to ssl module's default cipher
     list.  (Required OpenSSL 1.1.0 or LibreSSL).

   - bpo-25387(55): Check return value of winsound.MessageBeep.

   - bpo-27866(56): Add SSLContext.get_ciphers() method to get a list of
     all enabled ciphers.

   - bpo-27744(57): Add AF_ALG (Linux Kernel crypto) to socket module.

   - bpo-26470(58): Port ssl and hashlib module to OpenSSL 1.1.0.

   - bpo-11620(59): Fix support for SND_MEMORY in winsound.PlaySound.
     Based on a patch by Tim Lesher.

   - bpo-11734(60): Add support for IEEE 754 half-precision floats to
     the struct module.  Based on a patch by Eli Stevens.

   - bpo-27919(61): Deprecated ‘extra_path’ distribution option in
     distutils packaging.

   - bpo-23229(62): Add new ‘cmath’ constants: ‘cmath.inf’ and
     ‘cmath.nan’ to match ‘math.inf’ and ‘math.nan’, and also
     ‘cmath.infj’ and ‘cmath.nanj’ to match the format used by complex
     repr.

   - bpo-27842(63): The csv.DictReader now returns rows of type
     OrderedDict.  (Contributed by Steve Holden.)

   - Remove support for passing a file descriptor to os.access.  It
     never worked but previously didn't raise.

   - bpo-12885(64): Fix error when distutils encounters symlink.

   - bpo-27881(65): Fixed possible bugs when setting
     sqlite3.Connection.isolation_level.  Based on patch by Xiang Zhang.

   - bpo-27861(66): Fixed a crash in sqlite3.Connection.cursor() when a
     factory creates not a cursor.  Patch by Xiang Zhang.

   - bpo-19884(67): Avoid spurious output on OS X with Gnu Readline.

   - bpo-27706(68): Restore deterministic behavior of
     random.Random().seed() for string seeds using seeding version 1.
     Allows sequences of calls to random() to exactly match those
     obtained in Python 2.  Patch by Nofar Schnider.

   - bpo-10513(69): Fix a regression in Connection.commit().  Statements
     should not be reset after a commit.

   - bpo-12319(70): Chunked transfer encoding support added to
     http.client.HTTPConnection requests.  The
     urllib.request.AbstractHTTPHandler class does not enforce a
     Content-Length header any more.  If a HTTP request has a file or
     iterable body, but no Content-Length header, the library now falls
     back to use chunked transfer-encoding.

   - A new version of typing.py from ‘https://github.com/python/typing’:
     - Collection (only for 3.6) (bpo-27598(71)) - Add FrozenSet to
     __all__ (upstream #261) - fix crash in _get_type_vars() (upstream
     #259) - Remove the dict constraint in ForwardRef._eval_type
     (upstream #252)

   - bpo-27832(72): Make ‘_normalize’ parameter to ‘Fraction’
     constructor keyword-only, so that ‘Fraction(2, 3, 4)’ now raises
     ‘TypeError’.

   - bpo-27539(73): Fix unnormalised ‘Fraction.__pow__’ result in the
     case of negative exponent and negative base.

   - bpo-21718(74): cursor.description is now available for queries
     using CTEs.

   - bpo-27819(75): In distutils sdists, simply produce the "gztar"
     (gzipped tar format) distributions on all platforms unless
     "formats" is supplied.

   - bpo-2466(76): posixpath.ismount now correctly recognizes mount
     points which the user does not have permission to access.

   - bpo-9998(77): On Linux, ctypes.util.find_library now looks in
     LD_LIBRARY_PATH for shared libraries.

   - bpo-27573(78): exit message for code.interact is now configurable.

   - bpo-27930(79): Improved behaviour of
     logging.handlers.QueueListener.  Thanks to Paulo Andrade and Petr
     Viktorin for the analysis and patch.

   - bpo-6766(80): Distributed reference counting added to
     multiprocessing to support nesting of shared values / proxy
     objects.

   - bpo-21201(81): Improves readability of multiprocessing error
     message.  Thanks to Wojciech Walczak for patch.

   - asyncio: Add set_protocol / get_protocol to Transports.

   - bpo-27456(82): asyncio: Set TCP_NODELAY by default.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28732

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28485

   (3) https://bugs.python.org/issue?@action=redirect&bpo=28037

   (4) https://bugs.python.org/issue?@action=redirect&bpo=25283

   (5) https://bugs.python.org/issue?@action=redirect&bpo=24454

   (6) https://bugs.python.org/issue?@action=redirect&bpo=10740

   (7) https://bugs.python.org/issue?@action=redirect&bpo=17941

   (8) https://bugs.python.org/issue?@action=redirect&bpo=22493

   (9) https://bugs.python.org/issue?@action=redirect&bpo=26885

   (10) https://bugs.python.org/issue?@action=redirect&bpo=28070

   (11) https://bugs.python.org/issue?@action=redirect&bpo=19500

   (12) https://bugs.python.org/issue?@action=redirect&bpo=28022

   (13) https://bugs.python.org/issue?@action=redirect&bpo=28043

   (14) https://bugs.python.org/issue?@action=redirect&bpo=24693

   (15) https://bugs.python.org/issue?@action=redirect&bpo=17909

   (16) https://bugs.python.org/issue?@action=redirect&bpo=27137

   (17) https://bugs.python.org/issue?@action=redirect&bpo=1703178

   (18) https://bugs.python.org/issue?@action=redirect&bpo=28019

   (19) https://bugs.python.org/issue?@action=redirect&bpo=18401

   (20) https://bugs.python.org/issue?@action=redirect&bpo=25969

   (21) https://bugs.python.org/issue?@action=redirect&bpo=14977

   (22) https://bugs.python.org/issue?@action=redirect&bpo=28082

   (23) https://bugs.python.org/issue?@action=redirect&bpo=28025

   (24) https://bugs.python.org/issue?@action=redirect&bpo=23591

   (25) https://bugs.python.org/issue?@action=redirect&bpo=433028

   (26) https://bugs.python.org/issue?@action=redirect&bpo=24594

   (27) https://bugs.python.org/issue?@action=redirect&bpo=17582

   (28) https://bugs.python.org/issue?@action=redirect&bpo=28047

   (29) https://bugs.python.org/issue?@action=redirect&bpo=27576

   (30) https://bugs.python.org/issue?@action=redirect&bpo=28027

   (31) https://bugs.python.org/issue?@action=redirect&bpo=27445

   (32) https://bugs.python.org/issue?@action=redirect&bpo=24277

   (33) https://bugs.python.org/issue?@action=redirect&bpo=22450

   (34) https://bugs.python.org/issue?@action=redirect&bpo=28005

   (35) https://bugs.python.org/issue?@action=redirect&bpo=26667

   (36) https://bugs.python.org/issue?@action=redirect&bpo=27570

   (37) https://bugs.python.org/issue?@action=redirect&bpo=22233

   (38) https://bugs.python.org/issue?@action=redirect&bpo=27331

   (39) https://bugs.python.org/issue?@action=redirect&bpo=27988

   (40) https://bugs.python.org/issue?@action=redirect&bpo=16113

   (41) https://bugs.python.org/issue?@action=redirect&bpo=27776

   (42) https://peps.python.org/pep-0524/

   (43) https://bugs.python.org/issue?@action=redirect&bpo=27778

   (44) https://peps.python.org/pep-0524/

   (45) https://bugs.python.org/issue?@action=redirect&bpo=27691

   (46) https://bugs.python.org/issue?@action=redirect&bpo=18844

   (47) https://bugs.python.org/issue?@action=redirect&bpo=25761

   (48) https://bugs.python.org/issue?@action=redirect&bpo=26798

   (49) https://bugs.python.org/issue?@action=redirect&bpo=26032

   (50) https://bugs.python.org/issue?@action=redirect&bpo=25596

   (51) https://bugs.python.org/issue?@action=redirect&bpo=27928

   (52) https://bugs.python.org/issue?@action=redirect&bpo=27850

   (53) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2183

   (54) https://bugs.python.org/issue?@action=redirect&bpo=27766

   (55) https://bugs.python.org/issue?@action=redirect&bpo=25387

   (56) https://bugs.python.org/issue?@action=redirect&bpo=27866

   (57) https://bugs.python.org/issue?@action=redirect&bpo=27744

   (58) https://bugs.python.org/issue?@action=redirect&bpo=26470

   (59) https://bugs.python.org/issue?@action=redirect&bpo=11620

   (60) https://bugs.python.org/issue?@action=redirect&bpo=11734

   (61) https://bugs.python.org/issue?@action=redirect&bpo=27919

   (62) https://bugs.python.org/issue?@action=redirect&bpo=23229

   (63) https://bugs.python.org/issue?@action=redirect&bpo=27842

   (64) https://bugs.python.org/issue?@action=redirect&bpo=12885

   (65) https://bugs.python.org/issue?@action=redirect&bpo=27881

   (66) https://bugs.python.org/issue?@action=redirect&bpo=27861

   (67) https://bugs.python.org/issue?@action=redirect&bpo=19884

   (68) https://bugs.python.org/issue?@action=redirect&bpo=27706

   (69) https://bugs.python.org/issue?@action=redirect&bpo=10513

   (70) https://bugs.python.org/issue?@action=redirect&bpo=12319

   (71) https://bugs.python.org/issue?@action=redirect&bpo=27598

   (72) https://bugs.python.org/issue?@action=redirect&bpo=27832

   (73) https://bugs.python.org/issue?@action=redirect&bpo=27539

   (74) https://bugs.python.org/issue?@action=redirect&bpo=21718

   (75) https://bugs.python.org/issue?@action=redirect&bpo=27819

   (76) https://bugs.python.org/issue?@action=redirect&bpo=2466

   (77) https://bugs.python.org/issue?@action=redirect&bpo=9998

   (78) https://bugs.python.org/issue?@action=redirect&bpo=27573

   (79) https://bugs.python.org/issue?@action=redirect&bpo=27930

   (80) https://bugs.python.org/issue?@action=redirect&bpo=6766

   (81) https://bugs.python.org/issue?@action=redirect&bpo=21201

   (82) https://bugs.python.org/issue?@action=redirect&bpo=27456


File: python.info,  Node: IDLE<50>,  Next: C API<61>,  Prev: Library<71>,  Up: Python 3 6 0 beta 1

1.23.80.3 IDLE
..............

   - bpo-15308(1): Add 'interrupt execution' (^C) to Shell menu.  Patch
     by Roger Serwy, updated by Bayard Randel.

   - bpo-27922(2): Stop IDLE tests from 'flashing' gui widgets on the
     screen.

   - bpo-27891(3): Consistently group and sort imports within idlelib
     modules.

   - bpo-17642(4): add larger font sizes for classroom projection.

   - Add version to title of IDLE help window.

   - bpo-25564(5): In section on IDLE - console differences, mention
     that using exec means that __builtins__ is defined for each
     statement.

   - bpo-27821(6): Fix 3.6.0a3 regression that prevented custom key sets
     from being selected when no custom theme was defined.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=15308

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27922

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27891

   (4) https://bugs.python.org/issue?@action=redirect&bpo=17642

   (5) https://bugs.python.org/issue?@action=redirect&bpo=25564

   (6) https://bugs.python.org/issue?@action=redirect&bpo=27821


File: python.info,  Node: C API<61>,  Next: Tests<64>,  Prev: IDLE<50>,  Up: Python 3 6 0 beta 1

1.23.80.4 C API
...............

   - bpo-26900(1): Excluded underscored names and other private API from
     limited API.

   - bpo-26027(2): Add support for path-like objects in
     PyUnicode_FSConverter() & PyUnicode_FSDecoder().

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26900

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26027


File: python.info,  Node: Tests<64>,  Next: Build<70>,  Prev: C API<61>,  Up: Python 3 6 0 beta 1

1.23.80.5 Tests
...............

   - bpo-27427(1): Additional tests for the math module.  Patch by
     Francisco Couzo.

   - bpo-27953(2): Skip math and cmath tests that fail on OS X 10.4 due
     to a poor libm implementation of tan.

   - bpo-26040(3): Improve test_math and test_cmath coverage and rigour.
     Patch by Jeff Allen.

   - bpo-27787(4): Call gc.collect() before checking each test for
     "dangling threads", since the dangling threads are weak references.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27427

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27953

   (3) https://bugs.python.org/issue?@action=redirect&bpo=26040

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27787


File: python.info,  Node: Build<70>,  Next: Tools/Demos<37>,  Prev: Tests<64>,  Up: Python 3 6 0 beta 1

1.23.80.6 Build
...............

   - bpo-27566(1): Fix clean target in freeze makefile (patch by Lisa
     Roach)

   - bpo-27705(2): Update message in validate_ucrtbase.py

   - bpo-27976(3): Deprecate building _ctypes with the bundled copy of
     libffi on non-OSX UNIX platforms.

   - bpo-27983(4): Cause lack of llvm-profdata tool when using clang as
     required for PGO linking to be a configure time error rather than
     make time when ‘--with-optimizations’ is enabled.  Also improve our
     ability to find the llvm-profdata tool on MacOS and some Linuxes.

   - bpo-21590(5): Support for DTrace and SystemTap probes.

   - bpo-26307(6): The profile-opt build now applies PGO to the built-in
     modules.

   - bpo-26359(7): Add the -with-optimizations flag to turn on LTO and
     PGO build support when available.

   - bpo-27917(8): Set platform triplets for Android builds.

   - bpo-25825(9): Update references to the $(LIBPL) installation path
     on AIX. This path was changed in 3.2a4.

   - Update OS X installer to use SQLite 3.14.1 and XZ 5.2.2.

   - bpo-21122(10): Fix LTO builds on OS X.

   - bpo-17128(11): Build OS X installer with a private copy of OpenSSL.
     Also provide a sample Install Certificates command script to
     install a set of root certificates from the third-party certifi
     module.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27566

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27705

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27976

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27983

   (5) https://bugs.python.org/issue?@action=redirect&bpo=21590

   (6) https://bugs.python.org/issue?@action=redirect&bpo=26307

   (7) https://bugs.python.org/issue?@action=redirect&bpo=26359

   (8) https://bugs.python.org/issue?@action=redirect&bpo=27917

   (9) https://bugs.python.org/issue?@action=redirect&bpo=25825

   (10) https://bugs.python.org/issue?@action=redirect&bpo=21122

   (11) https://bugs.python.org/issue?@action=redirect&bpo=17128


File: python.info,  Node: Tools/Demos<37>,  Next: Windows<61>,  Prev: Build<70>,  Up: Python 3 6 0 beta 1

1.23.80.7 Tools/Demos
.....................

   - bpo-27952(1): Get Tools/scripts/fixcid.py working with Python 3 and
     the current "re" module, avoid invalid Python backslash escapes,
     and fix a bug parsing escaped C quote signs.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27952


File: python.info,  Node: Windows<61>,  Prev: Tools/Demos<37>,  Up: Python 3 6 0 beta 1

1.23.80.8 Windows
.................

   - bpo-28065(1): Update xz dependency to 5.2.2 and build it from
     source.

   - bpo-25144(2): Ensures TargetDir is set before continuing with
     custom install.

   - bpo-1602(3): Windows console doesn't input or print Unicode (PEP
     528)

   - bpo-27781(4): Change file system encoding on Windows to UTF-8 (PEP
     529)

   - bpo-27731(5): Opt-out of MAX_PATH on Windows 10

   - bpo-6135(6): Adds encoding and errors parameters to subprocess.

   - bpo-27959(7): Adds oem encoding, alias ansi to mbcs, move aliasmbcs
     to codec lookup.

   - bpo-27982(8): The functions of the winsound module now accept
     keyword arguments.

   - bpo-20366(9): Build full text search support into SQLite on
     Windows.

   - bpo-27756(10): Adds new icons for Python files and processes on
     Windows.  Designs by Cherry Wang.

   - bpo-27883(11): Update sqlite to 3.14.1.0 on Windows.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28065

   (2) https://bugs.python.org/issue?@action=redirect&bpo=25144

   (3) https://bugs.python.org/issue?@action=redirect&bpo=1602

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27781

   (5) https://bugs.python.org/issue?@action=redirect&bpo=27731

   (6) https://bugs.python.org/issue?@action=redirect&bpo=6135

   (7) https://bugs.python.org/issue?@action=redirect&bpo=27959

   (8) https://bugs.python.org/issue?@action=redirect&bpo=27982

   (9) https://bugs.python.org/issue?@action=redirect&bpo=20366

   (10) https://bugs.python.org/issue?@action=redirect&bpo=27756

   (11) https://bugs.python.org/issue?@action=redirect&bpo=27883


File: python.info,  Node: Python 3 6 0 alpha 4,  Next: Python 3 6 0 alpha 3,  Prev: Python 3 6 0 beta 1,  Up: Changelog（更動日誌）

1.23.81 Python 3.6.0 alpha 4
----------------------------

'Release date: 2016-08-15'

* Menu:

* Core and Builtins: Core and Builtins<73>.
* Library: Library<72>.
* IDLE: IDLE<51>.
* Tests: Tests<65>.
* Windows: Windows<62>.
* Build: Build<71>.


File: python.info,  Node: Core and Builtins<73>,  Next: Library<72>,  Up: Python 3 6 0 alpha 4

1.23.81.1 Core and Builtins
...........................

   - bpo-27704(1): Optimized creating bytes and bytearray from byte-like
     objects and iterables.  Speed up to 3 times for short objects.
     Original patch by Naoki Inada.

   - bpo-26823(2): Large sections of repeated lines in tracebacks are
     now abbreviated as "[Previous line repeated {count} more times]" by
     the builtin traceback rendering.  Patch by Emanuel Barry.

   - bpo-27574(3): Decreased an overhead of parsing keyword arguments in
     functions implemented with using Argument Clinic.

   - bpo-22557(4): Now importing already imported modules is up to 2.5
     times faster.

   - bpo-17596(5): Include <wincrypt.h> to help with Min GW building.

   - bpo-17599(6): On Windows, rename the privately defined
     REPARSE_DATA_BUFFER structure to avoid conflicting with the
     definition from Min GW.

   - bpo-27507(7): Add integer overflow check in bytearray.extend().
     Patch by Xiang Zhang.

   - bpo-27581(8): Don't rely on wrapping for overflow check in
     PySequence_Tuple().  Patch by Xiang Zhang.

   - bpo-1621(9): Avoid signed integer overflow in list and tuple
     operations.  Patch by Xiang Zhang.

   - bpo-27419(10): Standard __import__() no longer look up "__import__"
     in globals or builtins for importing submodules or "from import".
     Fixed a crash if raise a warning about unabling to resolve package
     from __spec__ or __package__.

   - bpo-27083(11): Respect the PYTHONCASEOK environment variable under
     Windows.

   - bpo-27514(12): Make having too many statically nested blocks a
     SyntaxError instead of SystemError.

   - bpo-27366(13): Implemented PEP 487(14) (Simpler customization of
     class creation).  Upon subclassing, the __init_subclass__
     classmethod is called on the base class.  Descriptors are
     initialized with __set_name__ after class creation.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27704

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26823

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27574

   (4) https://bugs.python.org/issue?@action=redirect&bpo=22557

   (5) https://bugs.python.org/issue?@action=redirect&bpo=17596

   (6) https://bugs.python.org/issue?@action=redirect&bpo=17599

   (7) https://bugs.python.org/issue?@action=redirect&bpo=27507

   (8) https://bugs.python.org/issue?@action=redirect&bpo=27581

   (9) https://bugs.python.org/issue?@action=redirect&bpo=1621

   (10) https://bugs.python.org/issue?@action=redirect&bpo=27419

   (11) https://bugs.python.org/issue?@action=redirect&bpo=27083

   (12) https://bugs.python.org/issue?@action=redirect&bpo=27514

   (13) https://bugs.python.org/issue?@action=redirect&bpo=27366

   (14) https://peps.python.org/pep-0487/


File: python.info,  Node: Library<72>,  Next: IDLE<51>,  Prev: Core and Builtins<73>,  Up: Python 3 6 0 alpha 4

1.23.81.2 Library
.................

   - bpo-26027(1): Add PEP 519(2)/__fspath__() support to the os and
     os.path modules.  Includes code from Jelle Zijlstra.  (See also:
     bpo-27524(3))

   - bpo-27598(4): Add Collections to collections.abc.  Patch by Ivan
     Levkivskyi, docs by Neil Girdhar.

   - bpo-25958(5): Support "anti-registration" of special methods from
     various ABCs, like __hash__, __iter__ or __len__.  All these (and
     several more) can be set to None in an implementation class and the
     behavior will be as if the method is not defined at all.
     (Previously, this mechanism existed only for __hash__, to make
     mutable classes unhashable.)  Code contributed by Andrew Barnert
     and Ivan Levkivskyi.

   - bpo-16764(6): Support keyword arguments to zlib.decompress().
     Patch by Xiang Zhang.

   - bpo-27736(7): Prevent segfault after interpreter re-initialization
     due to ref count problem introduced in code for bpo-27038(8) in
     3.6.0a3.  Patch by Xiang Zhang.

   - bpo-25628(9): The 'verbose' and 'rename' parameters for
     collections.namedtuple are now keyword-only.

   - bpo-12345(10): Add mathematical constant tau to math and cmath.
     See also PEP 628(11).

   - bpo-26823(12): traceback.StackSummary.format now abbreviates large
     sections of repeated lines as "[Previous line repeated {count} more
     times]" (this change then further affects other traceback display
     operations in the module).  Patch by Emanuel Barry.

   - bpo-27664(13): Add to
     concurrent.futures.thread.ThreadPoolExecutor() the ability to
     specify a thread name prefix.

   - bpo-27181(14): Add geometric_mean and harmonic_mean to statistics
     module.

   - bpo-27573(15): code.interact now prints an message when exiting.

   - bpo-6422(16): Add autorange method to timeit.Timer objects.

   - bpo-27773(17): Correct some memory management errors
     server_hostname in _ssl.wrap_socket().

   - bpo-26750(18): unittest.mock.create_autospec() now works properly
     for subclasses of property() and other data descriptors.  Removes
     the never publicly used, never documented
     unittest.mock.DescriptorTypes tuple.

   - bpo-26754(19): Undocumented support of general bytes-like objects
     as path in compile() and similar functions is now deprecated.

   - bpo-26800(20): Undocumented support of general bytes-like objects
     as paths in os functions is now deprecated.

   - bpo-26981(21): Add _order_ compatibility shim to enum.Enum for
     Python 2/3 code bases.

   - bpo-27661(22): Added tzinfo keyword argument to datetime.combine.

   - In the curses module, raise an error if window.getstr() or
     window.instr() is passed a negative value.

   - bpo-27783(23): Fix possible usage of uninitialized memory in
     operator.methodcaller.

   - bpo-27774(24): Fix possible Py_DECREF on unowned object in _sre.

   - bpo-27760(25): Fix possible integer overflow in binascii.b2a_qp.

   - bpo-27758(26): Fix possible integer overflow in the _csv module for
     large record lengths.

   - bpo-27568(27): Prevent HTTPoxy attack (CVE-2016-1000110(28)).
     Ignore the HTTP_PROXY variable when REQUEST_METHOD environment is
     set, which indicates that the script is in CGI mode.

   - bpo-7063(29): Remove dead code from the "array" module's slice
     handling.  Patch by Chuck.

   - bpo-27656(30): Do not assume sched.h defines any SCHED_* constants.

   - bpo-27130(31): In the "zlib" module, fix handling of large buffers
     (typically 4 GiB) when compressing and decompressing.  Previously,
     inputs were limited to 4 GiB, and compression and decompression
     operations did not properly handle results of 4 GiB.

   - bpo-24773(32): Implemented PEP 495(33) (Local Time Disambiguation).

   - Expose the EPOLLEXCLUSIVE constant (when it is defined) in the
     select module.

   - bpo-27567(34): Expose the EPOLLRDHUP and POLLRDHUP constants in the
     select module.

   - bpo-1621(35): Avoid signed int negation overflow in the "audioop"
     module.

   - bpo-27533(36): Release GIL in nt._isdir

   - bpo-17711(37): Fixed unpickling by the persistent ID with protocol
     0.  Original patch by Alexandre Vassalotti.

   - bpo-27522(38): Avoid an unintentional reference cycle in
     email.feedparser.

   - bpo-27512(39): Fix a segfault when os.fspath() called an
     __fspath__() method that raised an exception.  Patch by Xiang
     Zhang.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26027

   (2) https://peps.python.org/pep-0519/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27524

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27598

   (5) https://bugs.python.org/issue?@action=redirect&bpo=25958

   (6) https://bugs.python.org/issue?@action=redirect&bpo=16764

   (7) https://bugs.python.org/issue?@action=redirect&bpo=27736

   (8) https://bugs.python.org/issue?@action=redirect&bpo=27038

   (9) https://bugs.python.org/issue?@action=redirect&bpo=25628

   (10) https://bugs.python.org/issue?@action=redirect&bpo=12345

   (11) https://peps.python.org/pep-0628/

   (12) https://bugs.python.org/issue?@action=redirect&bpo=26823

   (13) https://bugs.python.org/issue?@action=redirect&bpo=27664

   (14) https://bugs.python.org/issue?@action=redirect&bpo=27181

   (15) https://bugs.python.org/issue?@action=redirect&bpo=27573

   (16) https://bugs.python.org/issue?@action=redirect&bpo=6422

   (17) https://bugs.python.org/issue?@action=redirect&bpo=27773

   (18) https://bugs.python.org/issue?@action=redirect&bpo=26750

   (19) https://bugs.python.org/issue?@action=redirect&bpo=26754

   (20) https://bugs.python.org/issue?@action=redirect&bpo=26800

   (21) https://bugs.python.org/issue?@action=redirect&bpo=26981

   (22) https://bugs.python.org/issue?@action=redirect&bpo=27661

   (23) https://bugs.python.org/issue?@action=redirect&bpo=27783

   (24) https://bugs.python.org/issue?@action=redirect&bpo=27774

   (25) https://bugs.python.org/issue?@action=redirect&bpo=27760

   (26) https://bugs.python.org/issue?@action=redirect&bpo=27758

   (27) https://bugs.python.org/issue?@action=redirect&bpo=27568

   (28) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000110

   (29) https://bugs.python.org/issue?@action=redirect&bpo=7063

   (30) https://bugs.python.org/issue?@action=redirect&bpo=27656

   (31) https://bugs.python.org/issue?@action=redirect&bpo=27130

   (32) https://bugs.python.org/issue?@action=redirect&bpo=24773

   (33) https://peps.python.org/pep-0495/

   (34) https://bugs.python.org/issue?@action=redirect&bpo=27567

   (35) https://bugs.python.org/issue?@action=redirect&bpo=1621

   (36) https://bugs.python.org/issue?@action=redirect&bpo=27533

   (37) https://bugs.python.org/issue?@action=redirect&bpo=17711

   (38) https://bugs.python.org/issue?@action=redirect&bpo=27522

   (39) https://bugs.python.org/issue?@action=redirect&bpo=27512


File: python.info,  Node: IDLE<51>,  Next: Tests<65>,  Prev: Library<72>,  Up: Python 3 6 0 alpha 4

1.23.81.3 IDLE
..............

   - bpo-27714(1): text_textview and test_autocomplete now pass when
     re-run in the same process.  This occurs when test_idle fails when
     run with the -w option but without -jn.  Fix warning from
     test_config.

   - bpo-27621(2): Put query response validation error messages in the
     query box itself instead of in a separate messagebox.  Redo tests
     to match.  Add Mac OSX refinements.  Original patch by Mark
     Roseman.

   - bpo-27620(3): Escape key now closes Query box as cancelled.

   - bpo-27609(4): IDLE: tab after initial whitespace should tab, not
     autocomplete.  This fixes problem with writing docstrings at least
     twice indented.

   - bpo-27609(5): Explicitly return None when there are also non-None
     returns.  In a few cases, reverse a condition and eliminate a
     return.

   - bpo-25507(6): IDLE no longer runs buggy code because of its tkinter
     imports.  Users must include the same imports required to run
     directly in Python.

   - bpo-27173(7): Add 'IDLE Modern Unix' to the built-in key sets.
     Make the default key set depend on the platform.  Add tests for the
     changes to the config module.

   - bpo-27452(8): add line counter and crc to IDLE configHandler test
     dump.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27714

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27621

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27620

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27609

   (5) https://bugs.python.org/issue?@action=redirect&bpo=27609

   (6) https://bugs.python.org/issue?@action=redirect&bpo=25507

   (7) https://bugs.python.org/issue?@action=redirect&bpo=27173

   (8) https://bugs.python.org/issue?@action=redirect&bpo=27452


File: python.info,  Node: Tests<65>,  Next: Windows<62>,  Prev: IDLE<51>,  Up: Python 3 6 0 alpha 4

1.23.81.4 Tests
...............

   - bpo-25805(1): Skip a test in test_pkgutil as needed that doesn't
     work when ‘__name__ == __main__’.  Patch by SilentGhost.

   - bpo-27472(2): Add test.support.unix_shell as the path to the
     default shell.

   - bpo-27369(3): In test_pyexpat, avoid testing an error message
     detail that changed in Expat 2.2.0.

   - bpo-27594(4): Prevent assertion error when running test_ast with
     coverage enabled: ensure code object has a valid first line number.
     Patch suggested by Ivan Levkivskyi.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25805

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27472

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27369

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27594


File: python.info,  Node: Windows<62>,  Next: Build<71>,  Prev: Tests<65>,  Up: Python 3 6 0 alpha 4

1.23.81.5 Windows
.................

   - bpo-27647(1): Update bundled Tcl/Tk to 8.6.6.

   - bpo-27610(2): Adds PEP 514(3) metadata to Windows installer

   - bpo-27469(4): Adds a shell extension to the launcher so that drag
     and drop works correctly.

   - bpo-27309(5): Enables proper Windows styles in python[w].exe
     manifest.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27647

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27610

   (3) https://peps.python.org/pep-0514/

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27469

   (5) https://bugs.python.org/issue?@action=redirect&bpo=27309


File: python.info,  Node: Build<71>,  Prev: Windows<62>,  Up: Python 3 6 0 alpha 4

1.23.81.6 Build
...............

   - bpo-27713(1): Suppress spurious build warnings when updating
     importlib's bootstrap files.  Patch by Xiang Zhang

   - bpo-25825(2): Correct the references to Modules/python.exp, which
     is required on AIX. The references were accidentally changed in
     3.5.0a1.

   - bpo-27453(3): CPP invocation in configure must use CPPFLAGS. Patch
     by Chi Hsuan Yen.

   - bpo-27641(4): The configure script now inserts comments into the
     makefile to prevent the pgen and _freeze_importlib executables from
     being cross-compiled.

   - bpo-26662(5): Set PYTHON_FOR_GEN in configure as the Python program
     to be used for file generation during the build.

   - bpo-10910(6): Avoid C++ compilation errors on FreeBSD and OS X.
     Also update FreedBSD version checks for the original ctype UTF-8
     workaround.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27713

   (2) https://bugs.python.org/issue?@action=redirect&bpo=25825

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27453

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27641

   (5) https://bugs.python.org/issue?@action=redirect&bpo=26662

   (6) https://bugs.python.org/issue?@action=redirect&bpo=10910


File: python.info,  Node: Python 3 6 0 alpha 3,  Next: Python 3 6 0 alpha 2,  Prev: Python 3 6 0 alpha 4,  Up: Changelog（更動日誌）

1.23.82 Python 3.6.0 alpha 3
----------------------------

'Release date: 2016-07-11'

* Menu:

* Security: Security<41>.
* Core and Builtins: Core and Builtins<74>.
* Library: Library<73>.
* IDLE: IDLE<52>.
* C API: C API<62>.
* Build: Build<72>.
* Tools/Demos: Tools/Demos<38>.
* Documentation: Documentation<62>.
* Tests: Tests<66>.


File: python.info,  Node: Security<41>,  Next: Core and Builtins<74>,  Up: Python 3 6 0 alpha 3

1.23.82.1 Security
..................

   - bpo-27278(1): Fix os.urandom() implementation using getrandom() on
     Linux.  Truncate size to INT_MAX and loop until we collected enough
     random bytes, instead of casting a directly Py_ssize_t to int.

   - bpo-22636(2): Avoid shell injection problems with
     ctypes.util.find_library().

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27278

   (2) https://bugs.python.org/issue?@action=redirect&bpo=22636


File: python.info,  Node: Core and Builtins<74>,  Next: Library<73>,  Prev: Security<41>,  Up: Python 3 6 0 alpha 3

1.23.82.2 Core and Builtins
...........................

   - bpo-27473(1): Fixed possible integer overflow in bytes and
     bytearray concatenations.  Patch by Xiang Zhang.

   - bpo-23034(2): The output of a special Python build with defined
     COUNT_ALLOCS, SHOW_ALLOC_COUNT or SHOW_TRACK_COUNT macros is now
     off by default.  It can be re-enabled using the "-X showalloccount"
     option.  It now outputs to stderr instead of stdout.

   - bpo-27443(3): __length_hint__() of bytearray iterators no longer
     return a negative integer for a resized bytearray.

   - bpo-27007(4): The fromhex() class methods of bytes and bytearray
     subclasses now return an instance of corresponding subclass.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27473

   (2) https://bugs.python.org/issue?@action=redirect&bpo=23034

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27443

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27007


File: python.info,  Node: Library<73>,  Next: IDLE<52>,  Prev: Core and Builtins<74>,  Up: Python 3 6 0 alpha 3

1.23.82.3 Library
.................

   - bpo-26844(1): Fix error message for imp.find_module() to refer to
     'path' instead of 'name'.  Patch by Lev Maximov.

   - bpo-23804(2): Fix SSL zero-length recv() calls to not block and not
     raise an error about unclean EOF.

   - bpo-27466(3): Change time format returned by
     http.cookie.time2netscape, confirming the netscape cookie format
     and making it consistent with documentation.

   - bpo-21708(4): Deprecated dbm.dumb behavior that differs from common
     dbm behavior: creating a database in 'r' and 'w' modes and
     modifying a database in 'r' mode.

   - bpo-26721(5): Change the socketserver.StreamRequestHandler.wfile
     attribute to implement BufferedIOBase.  In particular, the write()
     method no longer does partial writes.

   - bpo-22115(6): Added methods trace_add, trace_remove and trace_info
     in the tkinter.Variable class.  They replace old methods
     trace_variable, trace, trace_vdelete and trace_vinfo that use
     obsolete Tcl commands and might not work in future versions of Tcl.
     Fixed old tracing methods: trace_vdelete() with wrong mode no
     longer break tracing, trace_vinfo() now always returns a list of
     pairs of strings, tracing in the "u" mode now works.

   - bpo-26243(7): Only the level argument to zlib.compress() is keyword
     argument now.  The first argument is positional-only.

   - bpo-27038(8): Expose the DirEntry type as os.DirEntry.  Code patch
     by Jelle Zijlstra.

   - bpo-27186(9): Update os.fspath()/PyOS_FSPath() to check the return
     value of __fspath__() to be either str or bytes.

   - bpo-18726(10): All optional parameters of the dump(), dumps(),
     load() and loads() functions and JSONEncoder and JSONDecoder class
     constructors in the json module are now keyword-only.

   - bpo-27319(11): Methods selection_set(), selection_add(),
     selection_remove() and selection_toggle() of ttk.TreeView now allow
     passing multiple items as multiple arguments instead of passing
     them as a tuple.  Deprecated undocumented ability of calling the
     selection() method with arguments.

   - bpo-27079(12): Fixed curses.ascii functions isblank(), iscntrl()
     and ispunct().

   - bpo-27294(13): Numerical state in the repr for Tkinter event
     objects is now represented as a combination of known flags.

   - bpo-27177(14): Match objects in the re module now support
     index-like objects as group indices.  Based on patches by Jeroen
     Demeyer and Xiang Zhang.

   - bpo-26754(15): Some functions (compile() etc) accepted a filename
     argument encoded as an iterable of integers.  Now only strings and
     byte-like objects are accepted.

   - bpo-26536(16): socket.ioctl now supports SIO_LOOPBACK_FAST_PATH.
     Patch by Daniel Stokes.

   - bpo-27048(17): Prevents distutils failing on Windows when
     environment variables contain non-ASCII characters

   - bpo-27330(18): Fixed possible leaks in the ctypes module.

   - bpo-27238(19): Got rid of bare excepts in the turtle module.
     Original patch by Jelle Zijlstra.

   - bpo-27122(20): When an exception is raised within the context being
     managed by a contextlib.ExitStack() and one of the exit stack
     generators catches and raises it in a chain, do not re-raise the
     original exception when exiting, let the new chained one through.
     This avoids the PEP 479(21) bug described in issue25782.

   - bpo-16864(22): sqlite3.Cursor.lastrowid now supports REPLACE
     statement.  Initial patch by Alex LordThorsen.

   - bpo-26386(23): Fixed ttk.TreeView selection operations with item
     id's containing spaces.

   - bpo-8637(24): Honor a pager set by the env var MANPAGER (in
     preference to one set by the env var PAGER).

   - bpo-16182(25): Fix various functions in the "readline" module to
     use the locale encoding, and fix get_begidx() and get_endidx() to
     return code point indexes.

   - bpo-27392(26): Add loop.connect_accepted_socket().  Patch by Jim
     Fulton.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26844

   (2) https://bugs.python.org/issue?@action=redirect&bpo=23804

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27466

   (4) https://bugs.python.org/issue?@action=redirect&bpo=21708

   (5) https://bugs.python.org/issue?@action=redirect&bpo=26721

   (6) https://bugs.python.org/issue?@action=redirect&bpo=22115

   (7) https://bugs.python.org/issue?@action=redirect&bpo=26243

   (8) https://bugs.python.org/issue?@action=redirect&bpo=27038

   (9) https://bugs.python.org/issue?@action=redirect&bpo=27186

   (10) https://bugs.python.org/issue?@action=redirect&bpo=18726

   (11) https://bugs.python.org/issue?@action=redirect&bpo=27319

   (12) https://bugs.python.org/issue?@action=redirect&bpo=27079

   (13) https://bugs.python.org/issue?@action=redirect&bpo=27294

   (14) https://bugs.python.org/issue?@action=redirect&bpo=27177

   (15) https://bugs.python.org/issue?@action=redirect&bpo=26754

   (16) https://bugs.python.org/issue?@action=redirect&bpo=26536

   (17) https://bugs.python.org/issue?@action=redirect&bpo=27048

   (18) https://bugs.python.org/issue?@action=redirect&bpo=27330

   (19) https://bugs.python.org/issue?@action=redirect&bpo=27238

   (20) https://bugs.python.org/issue?@action=redirect&bpo=27122

   (21) https://peps.python.org/pep-0479/

   (22) https://bugs.python.org/issue?@action=redirect&bpo=16864

   (23) https://bugs.python.org/issue?@action=redirect&bpo=26386

   (24) https://bugs.python.org/issue?@action=redirect&bpo=8637

   (25) https://bugs.python.org/issue?@action=redirect&bpo=16182

   (26) https://bugs.python.org/issue?@action=redirect&bpo=27392


File: python.info,  Node: IDLE<52>,  Next: C API<62>,  Prev: Library<73>,  Up: Python 3 6 0 alpha 3

1.23.82.4 IDLE
..............

   - bpo-27477(1): IDLE search dialogs now use ttk widgets.

   - bpo-27173(2): Add 'IDLE Modern Unix' to the built-in key sets.
     Make the default key set depend on the platform.  Add tests for the
     changes to the config module.

   - bpo-27452(3): make command line "idle-test> python test_help.py"
     work.  __file__ is relative when python is started in the file's
     directory.

   - bpo-27452(4): add line counter and crc to IDLE configHandler test
     dump.

   - bpo-27380(5): IDLE: add query.py with base Query dialog and ttk
     widgets.  Module had subclasses SectionName, ModuleName, and
     HelpSource, which are used to get information from users by
     configdialog and file =>Load Module.  Each subclass has itw own
     validity checks.  Using ModuleName allows users to edit bad module
     names instead of starting over.  Add tests and delete the two files
     combined into the new one.

   - bpo-27372(6): Test_idle no longer changes the locale.

   - bpo-27365(7): Allow non-ascii chars in IDLE NEWS.txt, for
     contributor names.

   - bpo-27245(8): IDLE: Cleanly delete custom themes and key bindings.
     Previously, when IDLE was started from a console or by import, a
     cascade of warnings was emitted.  Patch by Serhiy Storchaka.

   - bpo-24137(9): Run IDLE, test_idle, and htest with tkinter default
     root disabled.  Fix code and tests that fail with this restriction.
     Fix htests to not create a second and redundant root and mainloop.

   - bpo-27310(10): Fix IDLE.app failure to launch on OS X due to
     vestigial import.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27477

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27173

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27452

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27452

   (5) https://bugs.python.org/issue?@action=redirect&bpo=27380

   (6) https://bugs.python.org/issue?@action=redirect&bpo=27372

   (7) https://bugs.python.org/issue?@action=redirect&bpo=27365

   (8) https://bugs.python.org/issue?@action=redirect&bpo=27245

   (9) https://bugs.python.org/issue?@action=redirect&bpo=24137

   (10) https://bugs.python.org/issue?@action=redirect&bpo=27310


File: python.info,  Node: C API<62>,  Next: Build<72>,  Prev: IDLE<52>,  Up: Python 3 6 0 alpha 3

1.23.82.5 C API
...............

   - bpo-26754(1): PyUnicode_FSDecoder() accepted a filename argument
     encoded as an iterable of integers.  Now only strings and byte-like
     objects are accepted.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26754


File: python.info,  Node: Build<72>,  Next: Tools/Demos<38>,  Prev: C API<62>,  Up: Python 3 6 0 alpha 3

1.23.82.6 Build
...............

   - bpo-28066(1): Fix the logic that searches build directories for
     generated include files when building outside the source tree.

   - bpo-27442(2): Expose the Android API level that python was built
     against, in sysconfig.get_config_vars() as 'ANDROID_API_LEVEL'.

   - bpo-27434(3): The interpreter that runs the cross-build, found in
     PATH, must now be of the same feature version (e.g.  3.6) as the
     source being built.

   - bpo-26930(4): Update Windows builds to use OpenSSL 1.0.2h.

   - bpo-23968(5): Rename the platform directory from plat-$(MACHDEP) to
     plat-$(PLATFORM_TRIPLET). Rename the config directory (LIBPL) from
     config-$(LDVERSION) to config-$(LDVERSION)-$(PLATFORM_TRIPLET).
     Install the platform specific _sysconfigdata module into the
     platform directory and rename it to include the ABIFLAGS.

   - Don't use largefile support for GNU/Hurd.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28066

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27442

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27434

   (4) https://bugs.python.org/issue?@action=redirect&bpo=26930

   (5) https://bugs.python.org/issue?@action=redirect&bpo=23968


File: python.info,  Node: Tools/Demos<38>,  Next: Documentation<62>,  Prev: Build<72>,  Up: Python 3 6 0 alpha 3

1.23.82.7 Tools/Demos
.....................

   - bpo-27332(1): Fixed the type of the first argument of module-level
     functions generated by Argument Clinic.  Patch by Petr Viktorin.

   - bpo-27418(2): Fixed Tools/importbench/importbench.py.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27332

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27418


File: python.info,  Node: Documentation<62>,  Next: Tests<66>,  Prev: Tools/Demos<38>,  Up: Python 3 6 0 alpha 3

1.23.82.8 Documentation
.......................

   - bpo-19489(1): Moved the search box from the sidebar to the header
     and footer of each page.  Patch by Ammar Askar.

   - bpo-27285(2): Update documentation to reflect the deprecation of
     ‘pyvenv’ and normalize on the term "virtual environment".  Patch by
     Steve Piercy.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=19489

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27285


File: python.info,  Node: Tests<66>,  Prev: Documentation<62>,  Up: Python 3 6 0 alpha 3

1.23.82.9 Tests
...............

   - bpo-27027(1): Added test.support.is_android that is True when this
     is an Android build.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27027


File: python.info,  Node: Python 3 6 0 alpha 2,  Next: Python 3 6 0 alpha 1,  Prev: Python 3 6 0 alpha 3,  Up: Changelog（更動日誌）

1.23.83 Python 3.6.0 alpha 2
----------------------------

'Release date: 2016-06-13'

* Menu:

* Security: Security<42>.
* Core and Builtins: Core and Builtins<75>.
* Library: Library<74>.
* IDLE: IDLE<53>.
* Documentation: Documentation<63>.
* Tests: Tests<67>.
* Windows: Windows<63>.
* Build: Build<73>.
* C API: C API<63>.
* Tools/Demos: Tools/Demos<39>.


File: python.info,  Node: Security<42>,  Next: Core and Builtins<75>,  Up: Python 3 6 0 alpha 2

1.23.83.1 Security
..................

   - bpo-26556(1): Update expat to 2.1.1, fixes CVE-2015-1283(2).

   - Fix TLS stripping vulnerability in smtplib, CVE-2016-0772(3).
     Reported by Team Oststrom.

   - bpo-26839(4): On Linux, *note os.urandom(): 4c7. now calls
     ‘getrandom()’ with ‘GRND_NONBLOCK’ to fall back on reading
     ‘/dev/urandom’ if the urandom entropy pool is not initialized yet.
     Patch written by Colm Buckley.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26556

   (2) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1283

   (3) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0772

   (4) https://bugs.python.org/issue?@action=redirect&bpo=26839


File: python.info,  Node: Core and Builtins<75>,  Next: Library<74>,  Prev: Security<42>,  Up: Python 3 6 0 alpha 2

1.23.83.2 Core and Builtins
...........................

   - bpo-27095(1): Simplified MAKE_FUNCTION and removed MAKE_CLOSURE
     opcodes.  Patch by Demur Rumed.

   - bpo-27190(2): Raise NotSupportedError if sqlite3 is older than
     3.3.1.  Patch by Dave Sawyer.

   - bpo-27286(3): Fixed compiling BUILD_MAP_UNPACK_WITH_CALL opcode.
     Calling function with generalized unpacking (PEP 448) and
     conflicting keyword names could cause undefined behavior.

   - bpo-27140(4): Added BUILD_CONST_KEY_MAP opcode.

   - bpo-27186(5): Add support for os.PathLike objects to open() (part
     of PEP 519(6)).

   - bpo-27066(7): Fixed SystemError if a custom opener (for open())
     returns a negative number without setting an exception.

   - bpo-26983(8): float() now always return an instance of exact float.
     The deprecation warning is emitted if __float__ returns an instance
     of a strict subclass of float.  In a future versions of Python this
     can be an error.

   - bpo-27097(9): Python interpreter is now about 7% faster due to
     optimized instruction decoding.  Based on patch by Demur Rumed.

   - bpo-26647(10): Python interpreter now uses 16-bit wordcode instead
     of bytecode.  Patch by Demur Rumed.

   - bpo-23275(11): Allow assigning to an empty target list in round
     brackets: () = iterable.

   - bpo-27243(12): Update the __aiter__ protocol: instead of returning
     an awaitable that resolves to an asynchronous iterator, the
     asynchronous iterator should be returned directly.  Doing the
     former will trigger a PendingDeprecationWarning.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27095

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27190

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27286

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27140

   (5) https://bugs.python.org/issue?@action=redirect&bpo=27186

   (6) https://peps.python.org/pep-0519/

   (7) https://bugs.python.org/issue?@action=redirect&bpo=27066

   (8) https://bugs.python.org/issue?@action=redirect&bpo=26983

   (9) https://bugs.python.org/issue?@action=redirect&bpo=27097

   (10) https://bugs.python.org/issue?@action=redirect&bpo=26647

   (11) https://bugs.python.org/issue?@action=redirect&bpo=23275

   (12) https://bugs.python.org/issue?@action=redirect&bpo=27243


File: python.info,  Node: Library<74>,  Next: IDLE<53>,  Prev: Core and Builtins<75>,  Up: Python 3 6 0 alpha 2

1.23.83.3 Library
.................

   - Comment out socket (SO_REUSEPORT) and posix (O_SHLOCK, O_EXLOCK)
     constants exposed on the API which are not implemented on GNU/Hurd.
     They would not work at runtime anyway.

   - bpo-27025(1): Generated names for Tkinter widgets are now more
     meaningful and recognizable.

   - bpo-25455(2): Fixed crashes in repr of recursive
     ElementTree.Element and functools.partial objects.

   - bpo-27294(3): Improved repr for Tkinter event objects.

   - bpo-20508(4): Improve exception message of
     IPv{4,6}Network.__getitem__.  Patch by Gareth Rees.

   - bpo-21386(5): Implement missing IPv4Address.is_global property.  It
     was documented since 07a5610bae9d.  Initial patch by Roger Luethi.

   - bpo-27029(6): Removed deprecated support of universal newlines mode
     from ZipFile.open().

   - bpo-27030(7): Unknown escapes consisting of ‘'\'’ and an ASCII
     letter in regular expressions now are errors.  The re.LOCALE flag
     now can be used only with bytes patterns.

   - bpo-27186(8): Add os.PathLike support to DirEntry (part of PEP
     519(9)).  Initial patch by Jelle Zijlstra.

   - bpo-20900(10): distutils register command now decodes HTTP
     responses correctly.  Initial patch by ingrid.

   - bpo-27186(11): Add os.PathLike support to pathlib, removing its
     provisional status (part of PEP 519).  Initial patch by Dusty
     Phillips.

   - bpo-27186(12): Add support for os.PathLike objects to os.fsencode()
     and os.fsdecode() (part of PEP 519(13)).

   - bpo-27186(14): Introduce os.PathLike and os.fspath() (part of PEP
     519(15)).

   - A new version of typing.py provides several new classes and
     features: @overload outside stubs, Reversible, DefaultDict, Text,
     ContextManager, Type[], NewType(), TYPE_CHECKING, and numerous bug
     fixes (note that some of the new features are not yet implemented
     in mypy or other static analyzers).  Also classes for PEP 492(16)
     (Awaitable, AsyncIterable, AsyncIterator) have been added (in fact
     they made it into 3.5.1 but were never mentioned).

   - bpo-25738(17): Stop http.server.BaseHTTPRequestHandler.send_error()
     from sending a message body for 205 Reset Content.  Also, don't
     send Content header fields in responses that don't have a body.
     Patch by Susumu Koshiba.

   - bpo-21313(18): Fix the "platform" module to tolerate when
     sys.version contains truncated build information.

   - bpo-23883(19): Added missing APIs to __all__ to match the
     documented APIs for the following modules: cgi, mailbox, mimetypes,
     plistlib and smtpd.  Patches by Jacek Kołodziej.

   - bpo-27164(20): In the zlib module, allow decompressing raw Deflate
     streams with a predefined zdict.  Based on patch by Xiang Zhang.

   - bpo-24291(21): Fix wsgiref.simple_server.WSGIRequestHandler to
     completely write data to the client.  Previously it could do
     partial writes and truncate data.  Also,
     wsgiref.handler.ServerHandler can now handle stdout doing partial
     writes, but this is deprecated.

   - bpo-21272(22): Use _sysconfigdata.py to initialize
     distutils.sysconfig.

   - bpo-19611(23): *note inspect: 72. now reports the implicit ‘.0’
     parameters generated by the compiler for comprehension and
     generator expression scopes as if they were positional-only
     parameters called ‘implicit0’.  Patch by Jelle Zijlstra.

   - bpo-26809(24): Add ‘__all__’ to *note string: be.  Patch by Emanuel
     Barry.

   - bpo-26373(25): subprocess.Popen.communicate now correctly ignores
     BrokenPipeError when the child process dies before .communicate()
     is called in more/all circumstances.

   - signal, socket, and ssl module IntEnum constant name lookups now
     return a consistent name for values having multiple names.  Ex:
     signal.Signals(6) now refers to itself as signal.SIGALRM rather
     than flipping between that and signal.SIGIOT based on the
     interpreter's hash randomization seed.

   - bpo-27167(26): Clarify the subprocess.CalledProcessError error
     message text when the child process died due to a signal.

   - bpo-25931(27): Don't define socketserver.Forking* names on
     platforms such as Windows that do not support os.fork().

   - bpo-21776(28): distutils.upload now correctly handles HTTPError.
     Initial patch by Claudiu Popa.

   - bpo-26526(29): Replace custom parse tree validation in the parser
     module with a simple DFA validator.

   - bpo-27114(30): Fix SSLContext._load_windows_store_certs fails with
     PermissionError

   - bpo-18383(31): Avoid creating duplicate filters when using
     filterwarnings and simplefilter.  Based on patch by Alex Shkop.

   - bpo-23026(32): winreg.QueryValueEx() now return an integer for
     REG_QWORD type.

   - bpo-26741(33): subprocess.Popen destructor now emits a
     ResourceWarning warning if the child process is still running.

   - bpo-27056(34): Optimize pickle.load() and pickle.loads(), up to 10%
     faster to deserialize a lot of small objects.

   - bpo-21271(35): New keyword only parameters in reset_mock call.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27025

   (2) https://bugs.python.org/issue?@action=redirect&bpo=25455

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27294

   (4) https://bugs.python.org/issue?@action=redirect&bpo=20508

   (5) https://bugs.python.org/issue?@action=redirect&bpo=21386

   (6) https://bugs.python.org/issue?@action=redirect&bpo=27029

   (7) https://bugs.python.org/issue?@action=redirect&bpo=27030

   (8) https://bugs.python.org/issue?@action=redirect&bpo=27186

   (9) https://peps.python.org/pep-0519/

   (10) https://bugs.python.org/issue?@action=redirect&bpo=20900

   (11) https://bugs.python.org/issue?@action=redirect&bpo=27186

   (12) https://bugs.python.org/issue?@action=redirect&bpo=27186

   (13) https://peps.python.org/pep-0519/

   (14) https://bugs.python.org/issue?@action=redirect&bpo=27186

   (15) https://peps.python.org/pep-0519/

   (16) https://peps.python.org/pep-0492/

   (17) https://bugs.python.org/issue?@action=redirect&bpo=25738

   (18) https://bugs.python.org/issue?@action=redirect&bpo=21313

   (19) https://bugs.python.org/issue?@action=redirect&bpo=23883

   (20) https://bugs.python.org/issue?@action=redirect&bpo=27164

   (21) https://bugs.python.org/issue?@action=redirect&bpo=24291

   (22) https://bugs.python.org/issue?@action=redirect&bpo=21272

   (23) https://bugs.python.org/issue?@action=redirect&bpo=19611

   (24) https://bugs.python.org/issue?@action=redirect&bpo=26809

   (25) https://bugs.python.org/issue?@action=redirect&bpo=26373

   (26) https://bugs.python.org/issue?@action=redirect&bpo=27167

   (27) https://bugs.python.org/issue?@action=redirect&bpo=25931

   (28) https://bugs.python.org/issue?@action=redirect&bpo=21776

   (29) https://bugs.python.org/issue?@action=redirect&bpo=26526

   (30) https://bugs.python.org/issue?@action=redirect&bpo=27114

   (31) https://bugs.python.org/issue?@action=redirect&bpo=18383

   (32) https://bugs.python.org/issue?@action=redirect&bpo=23026

   (33) https://bugs.python.org/issue?@action=redirect&bpo=26741

   (34) https://bugs.python.org/issue?@action=redirect&bpo=27056

   (35) https://bugs.python.org/issue?@action=redirect&bpo=21271


File: python.info,  Node: IDLE<53>,  Next: Documentation<63>,  Prev: Library<74>,  Up: Python 3 6 0 alpha 2

1.23.83.4 IDLE
..............

   - bpo-5124(1): Paste with text selected now replaces the selection on
     X11.  This matches how paste works on Windows, Mac, most modern
     Linux apps, and ttk widgets.  Original patch by Serhiy Storchaka.

   - bpo-24750(2): Switch all scrollbars in IDLE to ttk versions.  Where
     needed, minimal tests are added to cover changes.

   - bpo-24759(3): IDLE requires tk 8.5 and availability ttk widgets.
     Delete now unneeded tk version tests and code for older versions.
     Add test for IDLE syntax colorizer.

   - bpo-27239(4): idlelib.macosx.isXyzTk functions initialize as
     needed.

   - bpo-27262(5): move Aqua unbinding code, which enable context menus,
     to macosx.

   - bpo-24759(6): Make clear in idlelib.idle_test.__init__ that the
     directory is a private implementation of test.test_idle and tool
     for maintainers.

   - bpo-27196(7): Stop 'ThemeChanged' warnings when running IDLE tests.
     These persisted after other warnings were suppressed in #20567.
     Apply Serhiy Storchaka's update_idletasks solution to four test
     files.  Record this additional advice in idle_test/README.txt

   - bpo-20567(8): Revise idle_test/README.txt with advice about
     avoiding tk warning messages from tests.  Apply advice to several
     IDLE tests.

   - bpo-24225(9): Update idlelib/README.txt with new file names and
     event handlers.

   - bpo-27156(10): Remove obsolete code not used by IDLE.

   - bpo-27117(11): Make colorizer htest and turtledemo work with dark
     themes.  Move code for configuring text widget colors to a new
     function.

   - bpo-24225(12): Rename many ‘idlelib/*.py’ and ‘idle_test/test_*.py’
     files.  Edit files to replace old names with new names when the old
     name referred to the module rather than the class it contained.
     See the issue and IDLE section in What's New in 3.6 for more.

   - bpo-26673(13): When tk reports font size as 0, change to size 10.
     Such fonts on Linux prevented the configuration dialog from
     opening.

   - bpo-21939(14): Add test for IDLE's percolator.  Original patch by
     Saimadhav Heblikar.

   - bpo-21676(15): Add test for IDLE's replace dialog.  Original patch
     by Saimadhav Heblikar.

   - bpo-18410(16): Add test for IDLE's search dialog.  Original patch
     by Westley Martínez.

   - bpo-21703(17): Add test for undo delegator.  Patch mostly by
     Saimadhav Heblikar .

   - bpo-27044(18): Add ConfigDialog.remove_var_callbacks to stop memory
     leaks.

   - bpo-23977(19): Add more asserts to test_delegator.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=5124

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24750

   (3) https://bugs.python.org/issue?@action=redirect&bpo=24759

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27239

   (5) https://bugs.python.org/issue?@action=redirect&bpo=27262

   (6) https://bugs.python.org/issue?@action=redirect&bpo=24759

   (7) https://bugs.python.org/issue?@action=redirect&bpo=27196

   (8) https://bugs.python.org/issue?@action=redirect&bpo=20567

   (9) https://bugs.python.org/issue?@action=redirect&bpo=24225

   (10) https://bugs.python.org/issue?@action=redirect&bpo=27156

   (11) https://bugs.python.org/issue?@action=redirect&bpo=27117

   (12) https://bugs.python.org/issue?@action=redirect&bpo=24225

   (13) https://bugs.python.org/issue?@action=redirect&bpo=26673

   (14) https://bugs.python.org/issue?@action=redirect&bpo=21939

   (15) https://bugs.python.org/issue?@action=redirect&bpo=21676

   (16) https://bugs.python.org/issue?@action=redirect&bpo=18410

   (17) https://bugs.python.org/issue?@action=redirect&bpo=21703

   (18) https://bugs.python.org/issue?@action=redirect&bpo=27044

   (19) https://bugs.python.org/issue?@action=redirect&bpo=23977


File: python.info,  Node: Documentation<63>,  Next: Tests<67>,  Prev: IDLE<53>,  Up: Python 3 6 0 alpha 2

1.23.83.5 Documentation
.......................

   - bpo-16484(1): Change the default PYTHONDOCS URL to "https:", and
     fix the resulting links to use lowercase.  Patch by Sean Rodman,
     test by Kaushik Nadikuditi.

   - bpo-24136(2): Document the new PEP 448(3) unpacking syntax of 3.5.

   - bpo-22558(4): Add remaining doc links to source code for
     Python-coded modules.  Patch by Yoni Lavi.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=16484

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24136

   (3) https://peps.python.org/pep-0448/

   (4) https://bugs.python.org/issue?@action=redirect&bpo=22558


File: python.info,  Node: Tests<67>,  Next: Windows<63>,  Prev: Documentation<63>,  Up: Python 3 6 0 alpha 2

1.23.83.6 Tests
...............

   - bpo-25285(1): regrtest now uses subprocesses when the -j1 command
     line option is used: each test file runs in a fresh child process.
     Before, the -j1 option was ignored.

   - bpo-25285(2): Tools/buildbot/test.bat script now uses -j1 by
     default to run each test file in fresh child process.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25285

   (2) https://bugs.python.org/issue?@action=redirect&bpo=25285


File: python.info,  Node: Windows<63>,  Next: Build<73>,  Prev: Tests<67>,  Up: Python 3 6 0 alpha 2

1.23.83.7 Windows
.................

   - bpo-27064(1): The py.exe launcher now defaults to Python 3.  The
     Windows launcher ‘py.exe’ no longer prefers an installed Python 2
     version over Python 3 by default when used interactively.

   - bpo-17500(2): Remove unused and outdated icons.  (See also:
     ‘https://github.com/python/pythondotorg/issues/945’)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27064

   (2) https://bugs.python.org/issue?@action=redirect&bpo=17500


File: python.info,  Node: Build<73>,  Next: C API<63>,  Prev: Windows<63>,  Up: Python 3 6 0 alpha 2

1.23.83.8 Build
...............

   - bpo-27229(1): Fix the cross-compiling pgen rule for in-tree builds.
     Patch by Xavier de Gaye.

   - bpo-26930(2): Update OS X 10.5+ 32-bit-only installer to build and
     link with OpenSSL 1.0.2h.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27229

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26930


File: python.info,  Node: C API<63>,  Next: Tools/Demos<39>,  Prev: Build<73>,  Up: Python 3 6 0 alpha 2

1.23.83.9 C API
...............

   - bpo-27186(1): Add the PyOS_FSPath() function (part of PEP 519(2)).

   - bpo-26282(3): PyArg_ParseTupleAndKeywords() now supports
     positional-only parameters.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27186

   (2) https://peps.python.org/pep-0519/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=26282


File: python.info,  Node: Tools/Demos<39>,  Prev: C API<63>,  Up: Python 3 6 0 alpha 2

1.23.83.10 Tools/Demos
......................

   - bpo-26282(1): Argument Clinic now supports positional-only and
     keyword parameters in the same function.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26282


File: python.info,  Node: Python 3 6 0 alpha 1,  Next: Python 3 5 5 final,  Prev: Python 3 6 0 alpha 2,  Up: Changelog（更動日誌）

1.23.84 Python 3.6.0 alpha 1
----------------------------

'Release date: 2016-05-16'

* Menu:

* Security: Security<43>.
* Core and Builtins: Core and Builtins<76>.
* Library: Library<75>.
* IDLE: IDLE<54>.
* Documentation: Documentation<64>.
* Tests: Tests<68>.
* Build: Build<74>.
* Windows: Windows<64>.
* Tools/Demos: Tools/Demos<40>.
* C API: C API<64>.


File: python.info,  Node: Security<43>,  Next: Core and Builtins<76>,  Up: Python 3 6 0 alpha 1

1.23.84.1 Security
..................

   - bpo-26657(1): Fix directory traversal vulnerability with
     http.server on Windows.  This fixes a regression that was
     introduced in 3.3.4rc1 and 3.4.0rc1.  Based on patch by Philipp
     Hagemeister.

   - bpo-26313(2): ssl.py _load_windows_store_certs fails if windows
     cert store is empty.  Patch by Baji.

   - bpo-25939(3): On Windows open the cert store readonly in
     ssl.enum_certificates.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26657

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26313

   (3) https://bugs.python.org/issue?@action=redirect&bpo=25939


File: python.info,  Node: Core and Builtins<76>,  Next: Library<75>,  Prev: Security<43>,  Up: Python 3 6 0 alpha 1

1.23.84.2 Core and Builtins
...........................

   - bpo-20041(1): Fixed TypeError when frame.f_trace is set to None.
     Patch by Xavier de Gaye.

   - bpo-26168(2): Fixed possible refleaks in failing Py_BuildValue()
     with the "N" format unit.

   - bpo-26991(3): Fix possible refleak when creating a function with
     annotations.

   - bpo-27039(4): Fixed bytearray.remove() for values greater than 127.
     Based on patch by Joe Jevnik.

   - bpo-23640(5): int.from_bytes() no longer bypasses constructors for
     subclasses.

   - bpo-27005(6): Optimized the float.fromhex() class method for exact
     float.  It is now 2 times faster.

   - bpo-18531(7): Single var-keyword argument of dict subtype was
     passed unscathed to the C-defined function.  Now it is converted to
     exact dict.

   - bpo-26811(8): gc.get_objects() no longer contains a broken tuple
     with NULL pointer.

   - bpo-20120(9): Use RawConfigParser for .pypirc parsing, removing
     support for interpolation unintentionally added with move to Python
     3.  Behavior no longer does any interpolation in .pypirc files,
     matching behavior in Python 2.7 and Setuptools 19.0.

   - bpo-26249(10): Memory functions of the *note PyMem_Malloc(): c0d.
     domain (*note PYMEM_DOMAIN_MEM: c10.) now use the *note pymalloc
     allocator: cb6. rather than system ‘malloc()’.  Applications
     calling *note PyMem_Malloc(): c0d. without holding the GIL can now
     crash: use ‘PYTHONMALLOC=debug’ environment variable to validate
     the usage of memory allocators in your application.

   - bpo-26802(11): Optimize function calls only using unpacking like
     ‘func(*tuple)’ (no other positional argument, no keyword): avoid
     copying the tuple.  Patch written by Joe Jevnik.

   - bpo-26659(12): Make the builtin slice type support cycle
     collection.

   - bpo-26718(13): super.__init__ no longer leaks memory if called
     multiple times.  NOTE: A direct call of super.__init__ is not
     endorsed!

   - bpo-27138(14): Fix the doc comment for FileFinder.find_spec().

   - bpo-27147(15): Mention PEP 420(16) in the importlib docs.

   - bpo-25339(17): PYTHONIOENCODING now has priority over locale in
     setting the error handler for stdin and stdout.

   - bpo-26494(18): Fixed crash on iterating exhausting iterators.
     Affected classes are generic sequence iterators, iterators of str,
     bytes, bytearray, list, tuple, set, frozenset, dict, OrderedDict,
     corresponding views and os.scandir() iterator.

   - bpo-26574(19): Optimize ‘bytes.replace(b'', b'.')’ and
     ‘bytearray.replace(b'', b'.')’.  Patch written by Josh Snider.

   - bpo-26581(20): If coding cookie is specified multiple times on a
     line in Python source code file, only the first one is taken to
     account.

   - bpo-19711(21): Add tests for reloading namespace packages.

   - bpo-21099(22): Switch applicable importlib tests to use PEP 451(23)
     API.

   - bpo-26563(24): Debug hooks on Python memory allocators now raise a
     fatal error if functions of the *note PyMem_Malloc(): c0d. family
     are called without holding the GIL.

   - bpo-26564(25): On error, the debug hooks on Python memory
     allocators now use the *note tracemalloc: e8. module to get the
     traceback where a memory block was allocated.

   - bpo-26558(26): The debug hooks on Python memory allocator *note
     PyObject_Malloc(): c0f. now detect when functions are called
     without holding the GIL.

   - bpo-26516(27): Add *note PYTHONMALLOC: c0b. environment variable to
     set the Python memory allocators and/or install debug hooks.

   - bpo-26516(28): The *note PyMem_SetupDebugHooks(): c11. function can
     now also be used on Python compiled in release mode.

   - bpo-26516(29): The *note PYTHONMALLOCSTATS: 1a5c. environment
     variable can now also be used on Python compiled in release mode.
     It now has no effect if set to an empty string.

   - bpo-26516(30): In debug mode, debug hooks are now also installed on
     Python memory allocators when Python is configured without
     pymalloc.

   - bpo-26464(31): Fix str.translate() when string is ASCII and first
     replacements removes character, but next replacement uses a
     non-ASCII character or a string longer than 1 character.
     Regression introduced in Python 3.5.0.

   - bpo-22836(32): Ensure exception reports from PyErr_Display() and
     PyErr_WriteUnraisable() are sensible even when formatting them
     produces secondary errors.  This affects the reports produced by
     sys.__excepthook__() and when __del__() raises an exception.

   - bpo-26302(33): Correct behavior to reject comma as a legal
     character for cookie names.

   - bpo-26136(34): Upgrade the warning when a generator raises
     StopIteration from PendingDeprecationWarning to DeprecationWarning.
     Patch by Anish Shah.

   - bpo-26204(35): The compiler now ignores all constant statements:
     bytes, str, int, float, complex, name constants (None, False,
     True), Ellipsis and ast.Constant; not only str and int.  For
     example, ‘1.0’ is now ignored in ‘def f(): 1.0’.

   - bpo-4806(36): Avoid masking the original TypeError exception when
     using star (‘*’) unpacking in function calls.  Based on patch by
     Hagen Fürstenau and Daniel Urban.

   - bpo-26146(37): Add a new kind of AST node: ‘ast.Constant’.  It can
     be used by external AST optimizers, but the compiler does not emit
     directly such node.

   - bpo-23601(38): Sped-up allocation of dict key objects by using
     Python's small object allocator.  (Contributed by Julian Taylor.)

   - bpo-18018(39): Import raises ImportError instead of SystemError if
     a relative import is attempted without a known parent package.

   - bpo-25843(40): When compiling code, don't merge constants if they
     are equal but have a different types.  For example, ‘f1, f2 =
     lambda: 1, lambda: 1.0’ is now correctly compiled to two different
     functions: ‘f1()’ returns ‘1’ (‘int’) and ‘f2()’ returns ‘1.0’
     (‘float’), even if ‘1’ and ‘1.0’ are equal.

   - bpo-26107(41): The format of the ‘co_lnotab’ attribute of code
     objects changes to support negative line number delta.

   - bpo-26154(42): Add a new private _PyThreadState_UncheckedGet()
     function to get the current Python thread state, but don't issue a
     fatal error if it is NULL. This new function must be used instead
     of accessing directly the _PyThreadState_Current variable.  The
     variable is no more exposed since Python 3.5.1 to hide the exact
     implementation of atomic C types, to avoid compiler issues.

   - bpo-25791(43): If __package__ != __spec__.parent or if neither
     __package__ or __spec__ are defined then ImportWarning is raised.

   - bpo-22995(44): [UPDATE] Comment out the one of the pickleability
     tests in _PyObject_GetState() due to regressions observed in
     Cython-based projects.

   - bpo-25961(45): Disallowed null characters in the type name.

   - bpo-25973(46): Fix segfault when an invalid nonlocal statement
     binds a name starting with two underscores.

   - bpo-22995(47): Instances of extension types with a state that
     aren't subclasses of list or dict and haven't implemented any
     pickle-related methods (__reduce__, __reduce_ex__, __getnewargs__,
     __getnewargs_ex__, or __getstate__), can no longer be pickled.
     Including memoryview.

   - bpo-20440(48): Massive replacing unsafe attribute setting code with
     special macro Py_SETREF.

   - bpo-25766(49): Special method __bytes__() now works in str
     subclasses.

   - bpo-25421(50): __sizeof__ methods of builtin types now use dynamic
     basic size.  This allows sys.getsize() to work correctly with their
     subclasses with __slots__ defined.

   - bpo-25709(51): Fixed problem with in-place string concatenation and
     utf-8 cache.

   - bpo-5319(52): New Py_FinalizeEx() API allowing Python to set an
     exit status of 120 on failure to flush buffered streams.

   - bpo-25485(53): telnetlib.Telnet is now a context manager.

   - bpo-24097(54): Fixed crash in object.__reduce__() if slot name is
     freed inside __getattr__.

   - bpo-24731(55): Fixed crash on converting objects with special
     methods __bytes__, __trunc__, and __float__ returning instances of
     subclasses of bytes, int, and float to subclasses of bytes, int,
     and float correspondingly.

   - bpo-25630(56): Fix a possible segfault during argument parsing in
     functions that accept filesystem paths.

   - bpo-23564(57): Fixed a partially broken sanity check in the
     _posixsubprocess internals regarding how fds_to_pass were passed to
     the child.  The bug had no actual impact as subprocess.py already
     avoided it.

   - bpo-25388(58): Fixed tokenizer crash when processing undecodable
     source code with a null byte.

   - bpo-25462(59): The hash of the key now is calculated only once in
     most operations in C implementation of OrderedDict.

   - bpo-22995(60): Default implementation of __reduce__ and
     __reduce_ex__ now rejects builtin types with not defined __new__.

   - bpo-24802(61): Avoid buffer overreads when int(), float(),
     compile(), exec() and eval() are passed bytes-like objects.  These
     objects are not necessarily terminated by a null byte, but the
     functions assumed they were.

   - bpo-25555(62): Fix parser and AST: fill lineno and col_offset of
     "arg" node when compiling AST from Python objects.

   - bpo-24726(63): Fixed a crash and leaking NULL in repr() of
     OrderedDict that was mutated by direct calls of dict methods.

   - bpo-25449(64): Iterating OrderedDict with keys with unstable hash
     now raises KeyError in C implementations as well as in Python
     implementation.

   - bpo-25395(65): Fixed crash when highly nested OrderedDict
     structures were garbage collected.

   - bpo-25401(66): Optimize bytes.fromhex() and bytearray.fromhex():
     they are now between 2x and 3.5x faster.

   - bpo-25399(67): Optimize bytearray % args using the new private
     _PyBytesWriter API. Formatting is now between 2.5 and 5 times
     faster.

   - bpo-25274(68): sys.setrecursionlimit() now raises a RecursionError
     if the new recursion limit is too low depending at the current
     recursion depth.  Modify also the "lower-water mark" formula to
     make it monotonic.  This mark is used to decide when the overflowed
     flag of the thread state is reset.

   - bpo-24402(69): Fix input() to prompt to the redirected stdout when
     sys.stdout.fileno() fails.

   - bpo-25349(70): Optimize bytes % args using the new private
     _PyBytesWriter API. Formatting is now up to 2 times faster.

   - bpo-24806(71): Prevent builtin types that are not allowed to be
     subclassed from being subclassed through multiple inheritance.

   - bpo-25301(72): The UTF-8 decoder is now up to 15 times as fast for
     error handlers: ‘ignore’, ‘replace’ and ‘surrogateescape’.

   - bpo-24848(73): Fixed a number of bugs in UTF-7 decoding of
     misformed data.

   - bpo-25267(74): The UTF-8 encoder is now up to 75 times as fast for
     error handlers: ‘ignore’, ‘replace’, ‘surrogateescape’,
     ‘surrogatepass’.  Patch co-written with Serhiy Storchaka.

   - bpo-25280(75): Import trace messages emitted in verbose (-v) mode
     are no longer formatted twice.

   - bpo-25227(76): Optimize ASCII and latin1 encoders with the
     ‘surrogateescape’ error handler: the encoders are now up to 3 times
     as fast.  Initial patch written by Serhiy Storchaka.

   - bpo-25003(77): On Solaris 11.3 or newer, os.urandom() now uses the
     getrandom() function instead of the getentropy() function.  The
     getentropy() function is blocking to generate very good quality
     entropy, os.urandom() doesn't need such high-quality entropy.

   - bpo-9232(78): Modify Python's grammar to allow trailing commas in
     the argument list of a function declaration.  For example, "def
     f(*, a = 3,): pass" is now legal.  Patch from Mark Dickinson.

   - bpo-24965(79): Implement PEP 498(80) "Literal String
     Interpolation".  This allows you to embed expressions inside
     f-strings, which are converted to normal strings at run time.
     Given x=3, then f'value={x}' == 'value=3'.  Patch by Eric V. Smith.

   - bpo-26478(81): Fix semantic bugs when using binary operators with
     dictionary views and tuples.

   - bpo-26171(82): Fix possible integer overflow and heap corruption in
     zipimporter.get_data().

   - bpo-25660(83): Fix TAB key behaviour in REPL with readline.

   - bpo-26288(84): Optimize PyLong_AsDouble.

   - bpo-26289(85): Optimize floor and modulo division for single-digit
     longs.  Microbenchmarks show 2-2.5x improvement.  Built-in 'divmod'
     function is now also ~10% faster.  (See also: bpo-26315(86))

   - bpo-25887(87): Raise a RuntimeError when a coroutine object is
     awaited more than once.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=20041

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26168

   (3) https://bugs.python.org/issue?@action=redirect&bpo=26991

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27039

   (5) https://bugs.python.org/issue?@action=redirect&bpo=23640

   (6) https://bugs.python.org/issue?@action=redirect&bpo=27005

   (7) https://bugs.python.org/issue?@action=redirect&bpo=18531

   (8) https://bugs.python.org/issue?@action=redirect&bpo=26811

   (9) https://bugs.python.org/issue?@action=redirect&bpo=20120

   (10) https://bugs.python.org/issue?@action=redirect&bpo=26249

   (11) https://bugs.python.org/issue?@action=redirect&bpo=26802

   (12) https://bugs.python.org/issue?@action=redirect&bpo=26659

   (13) https://bugs.python.org/issue?@action=redirect&bpo=26718

   (14) https://bugs.python.org/issue?@action=redirect&bpo=27138

   (15) https://bugs.python.org/issue?@action=redirect&bpo=27147

   (16) https://peps.python.org/pep-0420/

   (17) https://bugs.python.org/issue?@action=redirect&bpo=25339

   (18) https://bugs.python.org/issue?@action=redirect&bpo=26494

   (19) https://bugs.python.org/issue?@action=redirect&bpo=26574

   (20) https://bugs.python.org/issue?@action=redirect&bpo=26581

   (21) https://bugs.python.org/issue?@action=redirect&bpo=19711

   (22) https://bugs.python.org/issue?@action=redirect&bpo=21099

   (23) https://peps.python.org/pep-0451/

   (24) https://bugs.python.org/issue?@action=redirect&bpo=26563

   (25) https://bugs.python.org/issue?@action=redirect&bpo=26564

   (26) https://bugs.python.org/issue?@action=redirect&bpo=26558

   (27) https://bugs.python.org/issue?@action=redirect&bpo=26516

   (28) https://bugs.python.org/issue?@action=redirect&bpo=26516

   (29) https://bugs.python.org/issue?@action=redirect&bpo=26516

   (30) https://bugs.python.org/issue?@action=redirect&bpo=26516

   (31) https://bugs.python.org/issue?@action=redirect&bpo=26464

   (32) https://bugs.python.org/issue?@action=redirect&bpo=22836

   (33) https://bugs.python.org/issue?@action=redirect&bpo=26302

   (34) https://bugs.python.org/issue?@action=redirect&bpo=26136

   (35) https://bugs.python.org/issue?@action=redirect&bpo=26204

   (36) https://bugs.python.org/issue?@action=redirect&bpo=4806

   (37) https://bugs.python.org/issue?@action=redirect&bpo=26146

   (38) https://bugs.python.org/issue?@action=redirect&bpo=23601

   (39) https://bugs.python.org/issue?@action=redirect&bpo=18018

   (40) https://bugs.python.org/issue?@action=redirect&bpo=25843

   (41) https://bugs.python.org/issue?@action=redirect&bpo=26107

   (42) https://bugs.python.org/issue?@action=redirect&bpo=26154

   (43) https://bugs.python.org/issue?@action=redirect&bpo=25791

   (44) https://bugs.python.org/issue?@action=redirect&bpo=22995

   (45) https://bugs.python.org/issue?@action=redirect&bpo=25961

   (46) https://bugs.python.org/issue?@action=redirect&bpo=25973

   (47) https://bugs.python.org/issue?@action=redirect&bpo=22995

   (48) https://bugs.python.org/issue?@action=redirect&bpo=20440

   (49) https://bugs.python.org/issue?@action=redirect&bpo=25766

   (50) https://bugs.python.org/issue?@action=redirect&bpo=25421

   (51) https://bugs.python.org/issue?@action=redirect&bpo=25709

   (52) https://bugs.python.org/issue?@action=redirect&bpo=5319

   (53) https://bugs.python.org/issue?@action=redirect&bpo=25485

   (54) https://bugs.python.org/issue?@action=redirect&bpo=24097

   (55) https://bugs.python.org/issue?@action=redirect&bpo=24731

   (56) https://bugs.python.org/issue?@action=redirect&bpo=25630

   (57) https://bugs.python.org/issue?@action=redirect&bpo=23564

   (58) https://bugs.python.org/issue?@action=redirect&bpo=25388

   (59) https://bugs.python.org/issue?@action=redirect&bpo=25462

   (60) https://bugs.python.org/issue?@action=redirect&bpo=22995

   (61) https://bugs.python.org/issue?@action=redirect&bpo=24802

   (62) https://bugs.python.org/issue?@action=redirect&bpo=25555

   (63) https://bugs.python.org/issue?@action=redirect&bpo=24726

   (64) https://bugs.python.org/issue?@action=redirect&bpo=25449

   (65) https://bugs.python.org/issue?@action=redirect&bpo=25395

   (66) https://bugs.python.org/issue?@action=redirect&bpo=25401

   (67) https://bugs.python.org/issue?@action=redirect&bpo=25399

   (68) https://bugs.python.org/issue?@action=redirect&bpo=25274

   (69) https://bugs.python.org/issue?@action=redirect&bpo=24402

   (70) https://bugs.python.org/issue?@action=redirect&bpo=25349

   (71) https://bugs.python.org/issue?@action=redirect&bpo=24806

   (72) https://bugs.python.org/issue?@action=redirect&bpo=25301

   (73) https://bugs.python.org/issue?@action=redirect&bpo=24848

   (74) https://bugs.python.org/issue?@action=redirect&bpo=25267

   (75) https://bugs.python.org/issue?@action=redirect&bpo=25280

   (76) https://bugs.python.org/issue?@action=redirect&bpo=25227

   (77) https://bugs.python.org/issue?@action=redirect&bpo=25003

   (78) https://bugs.python.org/issue?@action=redirect&bpo=9232

   (79) https://bugs.python.org/issue?@action=redirect&bpo=24965

   (80) https://peps.python.org/pep-0498/

   (81) https://bugs.python.org/issue?@action=redirect&bpo=26478

   (82) https://bugs.python.org/issue?@action=redirect&bpo=26171

   (83) https://bugs.python.org/issue?@action=redirect&bpo=25660

   (84) https://bugs.python.org/issue?@action=redirect&bpo=26288

   (85) https://bugs.python.org/issue?@action=redirect&bpo=26289

   (86) https://bugs.python.org/issue?@action=redirect&bpo=26315

   (87) https://bugs.python.org/issue?@action=redirect&bpo=25887


File: python.info,  Node: Library<75>,  Next: IDLE<54>,  Prev: Core and Builtins<76>,  Up: Python 3 6 0 alpha 1

1.23.84.3 Library
.................

   - bpo-27057(1): Fix os.set_inheritable() on Android, ioctl() is
     blocked by SELinux and fails with EACCESS. The function now falls
     back to fcntl().  Patch written by Michał Bednarski.

   - bpo-27014(2): Fix infinite recursion using typing.py.  Thanks to
     Kalle Tuure!

   - bpo-27031(3): Removed dummy methods in Tkinter widget classes:
     tk_menuBar() and tk_bindForTraversal().

   - bpo-14132(4): Fix urllib.request redirect handling when the target
     only has a query string.  Original fix by Ján Janech.

   - bpo-17214(5): The "urllib.request" module now percent-encodes
     non-ASCII bytes found in redirect target URLs.  Some servers send
     Location header fields with non-ASCII bytes, but "http.client"
     requires the request target to be ASCII-encodable, otherwise a
     UnicodeEncodeError is raised.  Based on patch by Christian Heimes.

   - bpo-27033(6): The default value of the decode_data parameter for
     smtpd.SMTPChannel and smtpd.SMTPServer constructors is changed to
     False.

   - bpo-27034(7): Removed deprecated class asynchat.fifo.

   - bpo-26870(8): Added readline.set_auto_history(), which can stop
     entries being automatically added to the history list.  Based on
     patch by Tyler Crompton.

   - bpo-26039(9): zipfile.ZipFile.open() can now be used to write data
     into a ZIP file, as well as for extracting data.  Patch by Thomas
     Kluyver.

   - bpo-26892(10): Honor debuglevel flag in urllib.request.HTTPHandler.
     Patch contributed by Chi Hsuan Yen.

   - bpo-22274(11): In the subprocess module, allow stderr to be
     redirected to stdout even when stdout is not redirected.  Patch by
     Akira Li.

   - bpo-26807(12): mock_open 'files' no longer error on readline at end
     of file.  Patch from Yolanda Robla.

   - bpo-25745(13): Fixed leaking a userptr in curses panel destructor.

   - bpo-26977(14): Removed unnecessary, and ignored, call to sum of
     squares helper in statistics.pvariance.

   - bpo-26002(15): Use bisect in statistics.median instead of a linear
     search.  Patch by Upendra Kuma.

   - bpo-25974(16): Make use of new Decimal.as_integer_ratio() method in
     statistics module.  Patch by Stefan Krah.

   - bpo-26996(17): Add secrets module as described in PEP 506(18).

   - bpo-26881(19): The modulefinder module now supports extended opcode
     arguments.

   - bpo-23815(20): Fixed crashes related to directly created instances
     of types in _tkinter and curses.panel modules.

   - bpo-17765(21): weakref.ref() no longer silently ignores keyword
     arguments.  Patch by Georg Brandl.

   - bpo-26873(22): xmlrpc now raises ResponseError on unsupported type
     tags instead of silently return incorrect result.

   - bpo-26915(23): The __contains__ methods in the collections ABCs now
     check for identity before checking equality.  This better matches
     the behavior of the concrete classes, allows sensible handling of
     NaNs, and makes it easier to reason about container invariants.

   - bpo-26711(24): Fixed the comparison of plistlib.Data with other
     types.

   - bpo-24114(25): Fix an uninitialized variable in ‘ctypes.util’.  The
     bug only occurs on SunOS when the ctypes implementation searches
     for the ‘crle’ program.  Patch by Xiang Zhang.  Tested on SunOS by
     Kees Bos.

   - bpo-26864(26): In urllib.request, change the proxy bypass host
     checking against no_proxy to be case-insensitive, and to not match
     unrelated host names that happen to have a bypassed hostname as a
     suffix.  Patch by Xiang Zhang.

   - bpo-24902(27): Print server URL on http.server startup.  Initial
     patch by Felix Kaiser.

   - bpo-25788(28): fileinput.hook_encoded() now supports an "errors"
     argument for passing to open.  Original patch by Joseph Hackman.

   - bpo-26634(29): recursive_repr() now sets __qualname__ of wrapper.
     Patch by Xiang Zhang.

   - bpo-26804(30): urllib.request will prefer lower_case proxy
     environment variables over UPPER_CASE or Mixed_Case ones.  Patch
     contributed by Hans-Peter Jansen.

   - bpo-26837(31): assertSequenceEqual() now correctly outputs
     non-stringified differing items (like bytes in the -b mode).  This
     affects assertListEqual() and assertTupleEqual().

   - bpo-26041(32): Remove "will be removed in Python 3.7" from
     deprecation messages of platform.dist() and
     platform.linux_distribution().  Patch by Kumaripaba Miyurusara
     Athukorala.

   - bpo-26822(33): itemgetter, attrgetter and methodcaller objects no
     longer silently ignore keyword arguments.

   - bpo-26733(34): Disassembling a class now disassembles class and
     static methods.  Patch by Xiang Zhang.

   - bpo-26801(35): Fix error handling in *note
     shutil.get_terminal_size(): 109b, catch *note AttributeError: 2f6.
     instead of *note NameError: 3e5.  Patch written by Emanuel Barry.

   - bpo-24838(36): tarfile's ustar and gnu formats now correctly
     calculate name and link field limits for multibyte character
     encodings like utf-8.

   - bpo-26717(37): Stop encoding Latin-1-ized WSGI paths with UTF-8.
     Patch by Anthony Sottile.

   - bpo-26782(38): Add STARTUPINFO to subprocess.__all__ on Windows.

   - bpo-26404(39): Add context manager to socketserver.  Patch by Aviv
     Palivoda.

   - bpo-26735(40): Fix *note os.urandom(): 4c7. on Solaris 11.3 and
     newer when reading more than 1,024 bytes: call ‘getrandom()’
     multiple times with a limit of 1024 bytes per call.

   - bpo-26585(41): Eliminate http.server._quote_html() and use
     html.escape(quote=False).  Patch by Xiang Zhang.

   - bpo-26685(42): Raise OSError if closing a socket fails.

   - bpo-16329(43): Add .webm to mimetypes.types_map.  Patch by
     Giampaolo Rodola'.

   - bpo-13952(44): Add .csv to mimetypes.types_map.  Patch by Geoff
     Wilson.

   - bpo-26587(45): the site module now allows .pth files to specify
     files to be added to sys.path (e.g.  zip files).

   - bpo-25609(46): Introduce contextlib.AbstractContextManager and
     typing.ContextManager.

   - bpo-26709(47): Fixed Y2038 problem in loading binary PLists.

   - bpo-23735(48): Handle terminal resizing with Readline 6.3+ by
     installing our own SIGWINCH handler.  Patch by Eric Price.

   - bpo-25951(49): Change SSLSocket.sendall() to return None, as
     explicitly documented for plain socket objects.  Patch by Aviv
     Palivoda.

   - bpo-26586(50): In http.server, respond with "413 Request header
     fields too large" if there are too many header fields to parse,
     rather than killing the connection and raising an unhandled
     exception.  Patch by Xiang Zhang.

   - bpo-26676(51): Added missing XMLPullParser to ElementTree.__all__.

   - bpo-22854(52): Change BufferedReader.writable() and
     BufferedWriter.readable() to always return False.

   - bpo-26492(53): Exhausted iterator of array.array now conforms with
     the behavior of iterators of other mutable sequences: it lefts
     exhausted even if iterated array is extended.

   - bpo-26641(54): doctest.DocFileTest and doctest.testfile() now
     support packages (module splitted into multiple directories) for
     the package parameter.

   - bpo-25195(55): Fix a regression in mock.MagicMock.  _Call is a
     subclass of tuple (changeset 3603bae63c13 only works for classes)
     so we need to implement __ne__ ourselves.  Patch by Andrew Plummer.

   - bpo-26644(56): Raise ValueError rather than SystemError when a
     negative length is passed to SSLSocket.recv() or read().

   - bpo-23804(57): Fix SSL recv(0) and read(0) methods to return zero
     bytes instead of up to 1024.

   - bpo-26616(58): Fixed a bug in datetime.astimezone() method.

   - bpo-26637(59): The *note importlib: 6b. module now emits an *note
     ImportError: 352. rather than a *note TypeError: 4dd. if *note
     __import__(): 879. is tried during the Python shutdown process but
     *note sys.path: 37f. is already cleared (set to ‘None’).

   - bpo-21925(60): *note warnings.formatwarning(): 191b. now catches
     exceptions when calling *note linecache.getline(): dc9. and *note
     tracemalloc.get_object_traceback(): 1a5e. to be able to log *note
     ResourceWarning: 229. emitted late during the Python shutdown
     process.

   - bpo-23848(61): On Windows, faulthandler.enable() now also installs
     an exception handler to dump the traceback of all Python threads on
     any Windows exception, not only on UNIX signals (SIGSEGV, SIGFPE,
     SIGABRT).

   - bpo-26530(62): Add C functions ‘_PyTraceMalloc_Track()’ and
     ‘_PyTraceMalloc_Untrack()’ to track memory blocks using the *note
     tracemalloc: e8. module.  Add ‘_PyTraceMalloc_GetTraceback()’ to
     get the traceback of an object.

   - bpo-26588(63): The _tracemalloc now supports tracing memory
     allocations of multiple address spaces (domains).

   - bpo-24266(64): Ctrl+C during Readline history search now cancels
     the search mode when compiled with Readline 7.

   - bpo-26590(65): Implement a safe finalizer for the _socket.socket
     type.  It now releases the GIL to close the socket.

   - bpo-18787(66): spwd.getspnam() now raises a PermissionError if the
     user doesn't have privileges.

   - bpo-26560(67): Avoid potential ValueError in
     BaseHandler.start_response.  Initial patch by Peter Inglesby.

   - bpo-26567(68): Add a new function *note PyErr_ResourceWarning():
     cbe. function to pass the destroyed object.  Add a 'source'
     attribute to ‘warnings.WarningMessage’.  Add
     warnings._showwarnmsg() which uses tracemalloc to get the traceback
     where source object was allocated.

   - bpo-26569(69): Fix *note pyclbr.readmodule(): 7cf. and *note
     pyclbr.readmodule_ex(): 7d0. to support importing packages.

   - bpo-26499(70): Account for remaining Content-Length in
     HTTPResponse.readline() and read1().  Based on patch by Silent
     Ghost.  Also document that HTTPResponse now supports these methods.

   - bpo-25320(71): Handle sockets in directories unittest discovery is
     scanning.  Patch from Victor van den Elzen.

   - bpo-16181(72): cookiejar.http2time() now returns None if year is
     higher than datetime.MAXYEAR.

   - bpo-26513(73): Fixes platform module detection of Windows Server

   - bpo-23718(74): Fixed parsing time in week 0 before Jan 1.  Original
     patch by Tamás Bence Gedai.

   - bpo-26323(75): Add Mock.assert_called() and
     Mock.assert_called_once() methods to unittest.mock.  Patch written
     by Amit Saha.

   - bpo-20589(76): Invoking Path.owner() and Path.group() on Windows
     now raise NotImplementedError instead of ImportError.

   - bpo-26177(77): Fixed the keys() method for Canvas and Scrollbar
     widgets.

   - bpo-15068(78): Got rid of excessive buffering in fileinput.  The
     bufsize parameter is now deprecated and ignored.

   - bpo-19475(79): Added an optional argument timespec to the datetime
     isoformat() method to choose the precision of the time component.

   - bpo-2202(80): Fix UnboundLocalError in
     AbstractDigestAuthHandler.get_algorithm_impls.  Initial patch by
     Mathieu Dupuy.

   - bpo-26167(81): Minimized overhead in copy.copy() and
     copy.deepcopy().  Optimized copying and deepcopying bytearrays,
     NotImplemented, slices, short lists, tuples, dicts, sets.

   - bpo-25718(82): Fixed pickling and copying the accumulate() iterator
     with total is None.

   - bpo-26475(83): Fixed debugging output for regular expressions with
     the (?x) flag.

   - bpo-26482(84): Allowed pickling recursive dequeues.

   - bpo-26335(85): Make mmap.write() return the number of bytes written
     like other write methods.  Patch by Jakub Stasiak.

   - bpo-26457(86): Fixed the subnets() methods in IP network classes
     for the case when resulting prefix length is equal to maximal
     prefix length.  Based on patch by Xiang Zhang.

   - bpo-26385(87): Remove the file if the internal open() call in
     NamedTemporaryFile() fails.  Patch by Silent Ghost.

   - bpo-26402(88): Fix XML-RPC client to retry when the server shuts
     down a persistent connection.  This was a regression related to the
     new http.client.RemoteDisconnected exception in 3.5.0a4.

   - bpo-25913(89): Leading ‘<~’ is optional now in base64.a85decode()
     with adobe=True.  Patch by Swati Jaiswal.

   - bpo-26186(90): Remove an invalid type check in
     importlib.util.LazyLoader.

   - bpo-26367(91): importlib.__import__() raises ImportError like
     builtins.__import__() when ‘level’ is specified but without an
     accompanying package specified.

   - bpo-26309(92): In the "socketserver" module, shut down the request
     (closing the connected socket) when verify_request() returns false.
     Patch by Aviv Palivoda.

   - bpo-23430(93): Change the socketserver module to only catch
     exceptions raised from a request handler that are derived from
     Exception (instead of BaseException).  Therefore SystemExit and
     KeyboardInterrupt no longer trigger the handle_error() method, and
     will now to stop a single-threaded server.

   - bpo-25995(94): os.walk() no longer uses FDs proportional to the
     tree depth.

   - bpo-25994(95): Added the close() method and the support of the
     context manager protocol for the os.scandir() iterator.

   - bpo-23992(96): multiprocessing: make MapResult not fail-fast upon
     exception.

   - bpo-26243(97): Support keyword arguments to zlib.compress().  Patch
     by Aviv Palivoda.

   - bpo-26117(98): The os.scandir() iterator now closes file descriptor
     not only when the iteration is finished, but when it was failed
     with error.

   - bpo-25949(99): __dict__ for an OrderedDict instance is now created
     only when needed.

   - bpo-25911(100): Restored support of bytes paths in os.walk() on
     Windows.

   - bpo-26045(101): Add UTF-8 suggestion to error message when posting
     a non-Latin-1 string with http.client.

   - bpo-26039(102): Added zipfile.ZipInfo.from_file() and
     zipinfo.ZipInfo.is_dir().  Patch by Thomas Kluyver.

   - bpo-12923(103): Reset FancyURLopener's redirect counter even if
     there is an exception.  Based on patches by Brian Brazil and Daniel
     Rocco.

   - bpo-25945(104): Fixed a crash when unpickle the functools.partial
     object with wrong state.  Fixed a leak in failed functools.partial
     constructor.  "args" and "keywords" attributes of functools.partial
     have now always types tuple and dict correspondingly.

   - bpo-26202(105): copy.deepcopy() now correctly copies range()
     objects with non-atomic attributes.

   - bpo-23076(106): Path.glob() now raises a ValueError if it's called
     with an invalid pattern.  Patch by Thomas Nyberg.

   - bpo-19883(107): Fixed possible integer overflows in zipimport.

   - bpo-26227(108): On Windows, getnameinfo(), gethostbyaddr() and
     gethostbyname_ex() functions of the socket module now decode the
     hostname from the ANSI code page rather than UTF-8.

   - bpo-26099(109): The site module now writes an error into stderr if
     sitecustomize module can be imported but executing the module raise
     an ImportError.  Same change for usercustomize.

   - bpo-26147(110): xmlrpc now works with strings not encodable with
     used non-UTF-8 encoding.

   - bpo-25935(111): Garbage collector now breaks reference loops with
     OrderedDict.

   - bpo-16620(112): Fixed AttributeError in msilib.Directory.glob().

   - bpo-26013(113): Added compatibility with broken protocol 2 pickles
     created in old Python 3 versions (3.4.3 and lower).

   - bpo-26129(114): Deprecated accepting non-integers in
     grp.getgrgid().

   - bpo-25850(115): Use cross-compilation by default for 64-bit
     Windows.

   - bpo-25822(116): Add docstrings to the fields of urllib.parse
     results.  Patch contributed by Swati Jaiswal.

   - bpo-22642(117): Convert trace module option parsing mechanism to
     argparse.  Patch contributed by SilentGhost.

   - bpo-24705(118): Fix sysconfig._parse_makefile not expanding ${}
     vars appearing before $() vars.

   - bpo-26069(119): Remove the deprecated apis in the trace module.

   - bpo-22138(120): Fix mock.patch behavior when patching descriptors.
     Restore original values after patching.  Patch contributed by Sean
     McCully.

   - bpo-25672(121): In the ssl module, enable the
     SSL_MODE_RELEASE_BUFFERS mode option if it is safe to do so.

   - bpo-26012(122): Don't traverse into symlinks for ‘**’ pattern in
     pathlib.Path.[r]glob().

   - bpo-24120(123): Ignore PermissionError when traversing a tree with
     pathlib.Path.[r]glob().  Patch by Ulrich Petri.

   - bpo-21815(124): Accept ] characters in the data portion of imap
     responses, in order to handle the flags with square brackets
     accepted and produced by servers such as gmail.

   - bpo-25447(125): fileinput now uses sys.stdin as-is if it does not
     have a buffer attribute (restores backward compatibility).

   - bpo-25971(126): Optimized creating Fractions from floats by 2 times
     and from Decimals by 3 times.

   - bpo-25802(127): Document as deprecated the remaining
     implementations of importlib.abc.Loader.load_module().

   - bpo-25928(128): Add Decimal.as_integer_ratio().

   - bpo-25447(129): Copying the lru_cache() wrapper object now always
     works, independently from the type of the wrapped object (by
     returning the original object unchanged).

   - bpo-25768(130): Have the functions in compileall return booleans
     instead of ints and add proper documentation and tests for the
     return values.

   - bpo-24103(131): Fixed possible use after free in
     ElementTree.XMLPullParser.

   - bpo-25860(132): os.fwalk() no longer skips remaining directories
     when error occurs.  Original patch by Samson Lee.

   - bpo-25914(133): Fixed and simplified OrderedDict.__sizeof__.

   - bpo-25869(134): Optimized deepcopying ElementTree; it is now 20
     times faster.

   - bpo-25873(135): Optimized iterating ElementTree.  Iterating
     elements Element.iter() is now 40% faster, iterating text
     Element.itertext() is now up to 2.5 times faster.

   - bpo-25902(136): Fixed various refcount issues in ElementTree
     iteration.

   - bpo-22227(137): The TarFile iterator is reimplemented using
     generator.  This implementation is simpler that using class.

   - bpo-25638(138): Optimized ElementTree.iterparse(); it is now 2x
     faster.  Optimized ElementTree parsing; it is now 10% faster.

   - bpo-25761(139): Improved detecting errors in broken pickle data.

   - bpo-25717(140): Restore the previous behaviour of tolerating most
     fstat() errors when opening files.  This was a regression in 3.5a1,
     and stopped anonymous temporary files from working in special
     cases.

   - bpo-24903(141): Fix regression in number of arguments compileall
     accepts when '-d' is specified.  The check on the number of
     arguments has been dropped completely as it never worked correctly
     anyway.

   - bpo-25764(142): In the subprocess module, preserve any exception
     caused by fork() failure when preexec_fn is used.

   - bpo-25771(143): Tweak the exception message for
     importlib.util.resolve_name() when 'package' isn't specified but
     necessary.

   - bpo-6478(144): _strptime's regexp cache now is reset after changing
     timezone with time.tzset().

   - bpo-14285(145): When executing a package with the "python -m
     package" option, and package initialization fails, a proper
     traceback is now reported.  The "runpy" module now lets exceptions
     from package initialization pass back to the caller, rather than
     raising ImportError.

   - bpo-19771(146): Also in runpy and the "-m" option, omit the
     irrelevant message ".  .  .  is a package and cannot be directly
     executed" if the package could not even be initialized (e.g.  due
     to a bad ‘*.pyc’ file).

   - bpo-25177(147): Fixed problem with the mean of very small and very
     large numbers.  As a side effect, statistics.mean and
     statistics.variance should be significantly faster.

   - bpo-25718(148): Fixed copying object with state with boolean value
     is false.

   - bpo-10131(149): Fixed deep copying of minidom documents.  Based on
     patch by Marian Ganisin.

   - bpo-7990(150): dir() on ElementTree.Element now lists properties:
     "tag", "text", "tail" and "attrib".  Original patch by Santoso
     Wijaya.

   - bpo-25725(151): Fixed a reference leak in pickle.loads() when
     unpickling invalid data including tuple instructions.

   - bpo-25663(152): In the Readline completer, avoid listing duplicate
     global names, and search the global namespace before searching
     builtins.

   - bpo-25688(153): Fixed file leak in ElementTree.iterparse() raising
     an error.

   - bpo-23914(154): Fixed SystemError raised by unpickler on broken
     pickle data.

   - bpo-25691(155): Fixed crash on deleting ElementTree.Element
     attributes.

   - bpo-25624(156): ZipFile now always writes a ZIP_STORED header for
     directory entries.  Patch by Dingyuan Wang.

   - bpo-25626(157): Change three zlib functions to accept sizes that
     fit in Py_ssize_t, but internally cap those sizes to UINT_MAX. This
     resolves a regression in 3.5 where GzipFile.read() failed to read
     chunks larger than 2 or 4 GiB. The change affects the
     zlib.Decompress.decompress() max_length parameter, the
     zlib.decompress() bufsize parameter, and the
     zlib.Decompress.flush() length parameter.

   - bpo-25583(158): Avoid incorrect errors raised by
     os.makedirs(exist_ok=True) when the OS gives priority to errors
     such as EACCES over EEXIST.

   - bpo-25593(159): Change semantics of EventLoop.stop() in asyncio.

   - bpo-6973(160): When we know a subprocess.Popen process has died, do
     not allow the send_signal(), terminate(), or kill() methods to do
     anything as they could potentially signal a different process.

   - bpo-23883(161): Added missing APIs to __all__ to match the
     documented APIs for the following modules: calendar, csv, enum,
     fileinput, ftplib, logging, optparse, tarfile, threading and wave.
     Also added a test.support.check__all__() helper.  Patches by Jacek
     Kołodziej, Mauro S. M. Rodrigues and Joel Taddei.

   - bpo-25590(162): In the Readline completer, only call getattr() once
     per attribute.  Also complete names of attributes such as
     properties and slots which are listed by dir() but not yet created
     on an instance.

   - bpo-25498(163): Fix a crash when garbage-collecting ctypes objects
     created by wrapping a memoryview.  This was a regression made in
     3.5a1.  Based on patch by Eryksun.

   - bpo-25584(164): Added "escape" to the __all__ list in the glob
     module.

   - bpo-25584(165): Fixed recursive glob() with patterns starting with
     ‘**’.

   - bpo-25446(166): Fix regression in smtplib's AUTH LOGIN support.

   - bpo-18010(167): Fix the pydoc web server's module search function
     to handle exceptions from importing packages.

   - bpo-25554(168): Got rid of circular references in regular
     expression parsing.

   - bpo-18973(169): Command-line interface of the calendar module now
     uses argparse instead of optparse.

   - bpo-25510(170): fileinput.FileInput.readline() now returns b''
     instead of '' at the end if the FileInput was opened with binary
     mode.  Patch by Ryosuke Ito.

   - bpo-25503(171): Fixed inspect.getdoc() for inherited docstrings of
     properties.  Original patch by John Mark Vandenberg.

   - bpo-25515(172): Always use os.urandom as a source of randomness in
     uuid.uuid4.

   - bpo-21827(173): Fixed textwrap.dedent() for the case when largest
     common whitespace is a substring of smallest leading whitespace.
     Based on patch by Robert Li.

   - bpo-25447(174): The lru_cache() wrapper objects now can be copied
     and pickled (by returning the original object unchanged).

   - bpo-25390(175): typing: Don't crash on Union[str, Pattern].

   - bpo-25441(176): asyncio: Raise error from drain() when socket is
     closed.

   - bpo-25410(177): Cleaned up and fixed minor bugs in C implementation
     of OrderedDict.

   - bpo-25411(178): Improved Unicode support in SMTPHandler through
     better use of the email package.  Thanks to user simon04 for the
     patch.

   - Move the imp module from a PendingDeprecationWarning to
     DeprecationWarning.

   - bpo-25407(179): Remove mentions of the formatter module being
     removed in Python 3.6.

   - bpo-25406(180): Fixed a bug in C implementation of
     OrderedDict.move_to_end() that caused segmentation fault or hang in
     iterating after moving several items to the start of ordered dict.

   - bpo-25382(181): pickletools.dis() now outputs implicit memo index
     for the MEMOIZE opcode.

   - bpo-25357(182): Add an optional newline parameter to
     binascii.b2a_base64().  base64.b64encode() uses it to avoid a
     memory copy.

   - bpo-24164(183): Objects that need calling ‘__new__’ with keyword
     arguments, can now be pickled using pickle protocols older than
     protocol version 4.

   - bpo-25364(184): zipfile now works in threads disabled builds.

   - bpo-25328(185): smtpd's SMTPChannel now correctly raises a
     ValueError if both decode_data and enable_SMTPUTF8 are set to true.

   - bpo-16099(186): RobotFileParser now supports Crawl-delay and
     Request-rate extensions.  Patch by Nikolay Bogoychev.

   - bpo-25316(187): distutils raises OSError instead of
     DistutilsPlatformError when MSVC is not installed.

   - bpo-25380(188): Fixed protocol for the STACK_GLOBAL opcode in
     pickletools.opcodes.

   - bpo-23972(189): Updates asyncio datagram create method allowing
     reuseport and reuseaddr socket options to be set prior to binding
     the socket.  Mirroring the existing asyncio create_server method
     the reuseaddr option for datagram sockets defaults to True if the
     O/S is 'posix' (except if the platform is Cygwin).  Patch by Chris
     Laws.

   - bpo-25304(190): Add asyncio.run_coroutine_threadsafe().  This lets
     you submit a coroutine to a loop from another thread, returning a
     concurrent.futures.Future.  By Vincent Michel.

   - bpo-25232(191): Fix CGIRequestHandler to split the query from the
     URL at the first question mark (?)  rather than the last.  Patch
     from Xiang Zhang.

   - bpo-24657(192): Prevent CGIRequestHandler from collapsing slashes
     in the query part of the URL as if it were a path.  Patch from
     Xiang Zhang.

   - bpo-25287(193): Don't add crypt.METHOD_CRYPT to crypt.methods if
     it's not supported.  Check if it is supported, it may not be
     supported on OpenBSD for example.

   - bpo-23600(194): Default implementation of tzinfo.fromutc() was
     returning wrong results in some cases.

   - bpo-25203(195): Failed readline.set_completer_delims() no longer
     left the module in inconsistent state.

   - bpo-25011(196): rlcompleter now omits private and special attribute
     names unless the prefix starts with underscores.

   - bpo-25209(197): rlcompleter now can add a space or a colon after
     completed keyword.

   - bpo-22241(198): timezone.utc name is now plain 'UTC', not
     'UTC-00:00'.

   - bpo-23517(199): fromtimestamp() and utcfromtimestamp() methods of
     datetime.datetime now round microseconds to nearest with ties going
     to nearest even integer (ROUND_HALF_EVEN), as round(float), instead
     of rounding towards -Infinity (ROUND_FLOOR).

   - bpo-23552(200): Timeit now warns when there is substantial (4x)
     variance between best and worst times.  Patch from Serhiy
     Storchaka.

   - bpo-24633(201): site-packages/README -> README.txt.

   - bpo-24879(202): help() and pydoc can now list named tuple fields in
     the order they were defined rather than alphabetically.  The
     ordering is determined by the _fields attribute if present.

   - bpo-24874(203): Improve speed of itertools.cycle() and make its
     pickle more compact.

   - Fix crash in itertools.cycle.__setstate__() when the first argument
     wasn't a list.

   - bpo-20059(204): urllib.parse raises ValueError on all invalid
     ports.  Patch by Martin Panter.

   - bpo-24360(205): Improve __repr__ of argparse.Namespace() for
     invalid identifiers.  Patch by Matthias Bussonnier.

   - bpo-23426(206): run_setup was broken in distutils.  Patch from
     Alexander Belopolsky.

   - bpo-13938(207): 2to3 converts StringTypes to a tuple.  Patch from
     Mark Hammond.

   - bpo-2091(208): open() accepted a 'U' mode string containing '+',
     but 'U' can only be used with 'r'.  Patch from Jeff Balogh and John
     O'Connor.

   - bpo-8585(209): improved tests for zipimporter2.  Patch from Mark
     Lawrence.

   - bpo-18622(210): unittest.mock.mock_open().reset_mock would recurse
     infinitely.  Patch from Nicola Palumbo and Laurent De Buyst.

   - bpo-24426(211): Fast searching optimization in regular expressions
     now works for patterns that starts with capturing groups.  Fast
     searching optimization now can't be disabled at compile time.

   - bpo-23661(212): unittest.mock side_effects can now be exceptions
     again.  This was a regression vs Python 3.4.  Patch from Ignacio
     Rossi

   - bpo-13248(213): Remove deprecated inspect.getmoduleinfo function.

   - bpo-25578(214): Fix (another) memory leak in
     SSLSocket.getpeercer().

   - bpo-25530(215): Disable the vulnerable SSLv3 protocol by default
     when creating ssl.SSLContext.

   - bpo-25569(216): Fix memory leak in SSLSocket.getpeercert().

   - bpo-25471(217): Sockets returned from accept() shouldn't appear to
     be nonblocking.

   - bpo-25319(218): When threading.Event is reinitialized, the
     underlying condition should use a regular lock rather than a
     recursive lock.

   - Skip getaddrinfo if host is already resolved.  Patch by A. Jesse
     Jiryu Davis.

   - bpo-26050(219): Add asyncio.StreamReader.readuntil() method.  Patch
     by Марк Коренберг.

   - bpo-25924(220): Avoid unnecessary serialization of getaddrinfo(3)
     calls on OS X versions 10.5 or higher.  Original patch by A. Jesse
     Jiryu Davis.

   - bpo-26406(221): Avoid unnecessary serialization of getaddrinfo(3)
     calls on current versions of OpenBSD and NetBSD. Patch by A. Jesse
     Jiryu Davis.

   - bpo-26848(222): Fix asyncio/subprocess.communicate() to handle
     empty input.  Patch by Jack O'Connor.

   - bpo-27040(223): Add loop.get_exception_handler method

   - bpo-27041(224): asyncio: Add loop.create_future method

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27057

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27014

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27031

   (4) https://bugs.python.org/issue?@action=redirect&bpo=14132

   (5) https://bugs.python.org/issue?@action=redirect&bpo=17214

   (6) https://bugs.python.org/issue?@action=redirect&bpo=27033

   (7) https://bugs.python.org/issue?@action=redirect&bpo=27034

   (8) https://bugs.python.org/issue?@action=redirect&bpo=26870

   (9) https://bugs.python.org/issue?@action=redirect&bpo=26039

   (10) https://bugs.python.org/issue?@action=redirect&bpo=26892

   (11) https://bugs.python.org/issue?@action=redirect&bpo=22274

   (12) https://bugs.python.org/issue?@action=redirect&bpo=26807

   (13) https://bugs.python.org/issue?@action=redirect&bpo=25745

   (14) https://bugs.python.org/issue?@action=redirect&bpo=26977

   (15) https://bugs.python.org/issue?@action=redirect&bpo=26002

   (16) https://bugs.python.org/issue?@action=redirect&bpo=25974

   (17) https://bugs.python.org/issue?@action=redirect&bpo=26996

   (18) https://peps.python.org/pep-0506/

   (19) https://bugs.python.org/issue?@action=redirect&bpo=26881

   (20) https://bugs.python.org/issue?@action=redirect&bpo=23815

   (21) https://bugs.python.org/issue?@action=redirect&bpo=17765

   (22) https://bugs.python.org/issue?@action=redirect&bpo=26873

   (23) https://bugs.python.org/issue?@action=redirect&bpo=26915

   (24) https://bugs.python.org/issue?@action=redirect&bpo=26711

   (25) https://bugs.python.org/issue?@action=redirect&bpo=24114

   (26) https://bugs.python.org/issue?@action=redirect&bpo=26864

   (27) https://bugs.python.org/issue?@action=redirect&bpo=24902

   (28) https://bugs.python.org/issue?@action=redirect&bpo=25788

   (29) https://bugs.python.org/issue?@action=redirect&bpo=26634

   (30) https://bugs.python.org/issue?@action=redirect&bpo=26804

   (31) https://bugs.python.org/issue?@action=redirect&bpo=26837

   (32) https://bugs.python.org/issue?@action=redirect&bpo=26041

   (33) https://bugs.python.org/issue?@action=redirect&bpo=26822

   (34) https://bugs.python.org/issue?@action=redirect&bpo=26733

   (35) https://bugs.python.org/issue?@action=redirect&bpo=26801

   (36) https://bugs.python.org/issue?@action=redirect&bpo=24838

   (37) https://bugs.python.org/issue?@action=redirect&bpo=26717

   (38) https://bugs.python.org/issue?@action=redirect&bpo=26782

   (39) https://bugs.python.org/issue?@action=redirect&bpo=26404

   (40) https://bugs.python.org/issue?@action=redirect&bpo=26735

   (41) https://bugs.python.org/issue?@action=redirect&bpo=26585

   (42) https://bugs.python.org/issue?@action=redirect&bpo=26685

   (43) https://bugs.python.org/issue?@action=redirect&bpo=16329

   (44) https://bugs.python.org/issue?@action=redirect&bpo=13952

   (45) https://bugs.python.org/issue?@action=redirect&bpo=26587

   (46) https://bugs.python.org/issue?@action=redirect&bpo=25609

   (47) https://bugs.python.org/issue?@action=redirect&bpo=26709

   (48) https://bugs.python.org/issue?@action=redirect&bpo=23735

   (49) https://bugs.python.org/issue?@action=redirect&bpo=25951

   (50) https://bugs.python.org/issue?@action=redirect&bpo=26586

   (51) https://bugs.python.org/issue?@action=redirect&bpo=26676

   (52) https://bugs.python.org/issue?@action=redirect&bpo=22854

   (53) https://bugs.python.org/issue?@action=redirect&bpo=26492

   (54) https://bugs.python.org/issue?@action=redirect&bpo=26641

   (55) https://bugs.python.org/issue?@action=redirect&bpo=25195

   (56) https://bugs.python.org/issue?@action=redirect&bpo=26644

   (57) https://bugs.python.org/issue?@action=redirect&bpo=23804

   (58) https://bugs.python.org/issue?@action=redirect&bpo=26616

   (59) https://bugs.python.org/issue?@action=redirect&bpo=26637

   (60) https://bugs.python.org/issue?@action=redirect&bpo=21925

   (61) https://bugs.python.org/issue?@action=redirect&bpo=23848

   (62) https://bugs.python.org/issue?@action=redirect&bpo=26530

   (63) https://bugs.python.org/issue?@action=redirect&bpo=26588

   (64) https://bugs.python.org/issue?@action=redirect&bpo=24266

   (65) https://bugs.python.org/issue?@action=redirect&bpo=26590

   (66) https://bugs.python.org/issue?@action=redirect&bpo=18787

   (67) https://bugs.python.org/issue?@action=redirect&bpo=26560

   (68) https://bugs.python.org/issue?@action=redirect&bpo=26567

   (69) https://bugs.python.org/issue?@action=redirect&bpo=26569

   (70) https://bugs.python.org/issue?@action=redirect&bpo=26499

   (71) https://bugs.python.org/issue?@action=redirect&bpo=25320

   (72) https://bugs.python.org/issue?@action=redirect&bpo=16181

   (73) https://bugs.python.org/issue?@action=redirect&bpo=26513

   (74) https://bugs.python.org/issue?@action=redirect&bpo=23718

   (75) https://bugs.python.org/issue?@action=redirect&bpo=26323

   (76) https://bugs.python.org/issue?@action=redirect&bpo=20589

   (77) https://bugs.python.org/issue?@action=redirect&bpo=26177

   (78) https://bugs.python.org/issue?@action=redirect&bpo=15068

   (79) https://bugs.python.org/issue?@action=redirect&bpo=19475

   (80) https://bugs.python.org/issue?@action=redirect&bpo=2202

   (81) https://bugs.python.org/issue?@action=redirect&bpo=26167

   (82) https://bugs.python.org/issue?@action=redirect&bpo=25718

   (83) https://bugs.python.org/issue?@action=redirect&bpo=26475

   (84) https://bugs.python.org/issue?@action=redirect&bpo=26482

   (85) https://bugs.python.org/issue?@action=redirect&bpo=26335

   (86) https://bugs.python.org/issue?@action=redirect&bpo=26457

   (87) https://bugs.python.org/issue?@action=redirect&bpo=26385

   (88) https://bugs.python.org/issue?@action=redirect&bpo=26402

   (89) https://bugs.python.org/issue?@action=redirect&bpo=25913

   (90) https://bugs.python.org/issue?@action=redirect&bpo=26186

   (91) https://bugs.python.org/issue?@action=redirect&bpo=26367

   (92) https://bugs.python.org/issue?@action=redirect&bpo=26309

   (93) https://bugs.python.org/issue?@action=redirect&bpo=23430

   (94) https://bugs.python.org/issue?@action=redirect&bpo=25995

   (95) https://bugs.python.org/issue?@action=redirect&bpo=25994

   (96) https://bugs.python.org/issue?@action=redirect&bpo=23992

   (97) https://bugs.python.org/issue?@action=redirect&bpo=26243

   (98) https://bugs.python.org/issue?@action=redirect&bpo=26117

   (99) https://bugs.python.org/issue?@action=redirect&bpo=25949

   (100) https://bugs.python.org/issue?@action=redirect&bpo=25911

   (101) https://bugs.python.org/issue?@action=redirect&bpo=26045

   (102) https://bugs.python.org/issue?@action=redirect&bpo=26039

   (103) https://bugs.python.org/issue?@action=redirect&bpo=12923

   (104) https://bugs.python.org/issue?@action=redirect&bpo=25945

   (105) https://bugs.python.org/issue?@action=redirect&bpo=26202

   (106) https://bugs.python.org/issue?@action=redirect&bpo=23076

   (107) https://bugs.python.org/issue?@action=redirect&bpo=19883

   (108) https://bugs.python.org/issue?@action=redirect&bpo=26227

   (109) https://bugs.python.org/issue?@action=redirect&bpo=26099

   (110) https://bugs.python.org/issue?@action=redirect&bpo=26147

   (111) https://bugs.python.org/issue?@action=redirect&bpo=25935

   (112) https://bugs.python.org/issue?@action=redirect&bpo=16620

   (113) https://bugs.python.org/issue?@action=redirect&bpo=26013

   (114) https://bugs.python.org/issue?@action=redirect&bpo=26129

   (115) https://bugs.python.org/issue?@action=redirect&bpo=25850

   (116) https://bugs.python.org/issue?@action=redirect&bpo=25822

   (117) https://bugs.python.org/issue?@action=redirect&bpo=22642

   (118) https://bugs.python.org/issue?@action=redirect&bpo=24705

   (119) https://bugs.python.org/issue?@action=redirect&bpo=26069

   (120) https://bugs.python.org/issue?@action=redirect&bpo=22138

   (121) https://bugs.python.org/issue?@action=redirect&bpo=25672

   (122) https://bugs.python.org/issue?@action=redirect&bpo=26012

   (123) https://bugs.python.org/issue?@action=redirect&bpo=24120

   (124) https://bugs.python.org/issue?@action=redirect&bpo=21815

   (125) https://bugs.python.org/issue?@action=redirect&bpo=25447

   (126) https://bugs.python.org/issue?@action=redirect&bpo=25971

   (127) https://bugs.python.org/issue?@action=redirect&bpo=25802

   (128) https://bugs.python.org/issue?@action=redirect&bpo=25928

   (129) https://bugs.python.org/issue?@action=redirect&bpo=25447

   (130) https://bugs.python.org/issue?@action=redirect&bpo=25768

   (131) https://bugs.python.org/issue?@action=redirect&bpo=24103

   (132) https://bugs.python.org/issue?@action=redirect&bpo=25860

   (133) https://bugs.python.org/issue?@action=redirect&bpo=25914

   (134) https://bugs.python.org/issue?@action=redirect&bpo=25869

   (135) https://bugs.python.org/issue?@action=redirect&bpo=25873

   (136) https://bugs.python.org/issue?@action=redirect&bpo=25902

   (137) https://bugs.python.org/issue?@action=redirect&bpo=22227

   (138) https://bugs.python.org/issue?@action=redirect&bpo=25638

   (139) https://bugs.python.org/issue?@action=redirect&bpo=25761

   (140) https://bugs.python.org/issue?@action=redirect&bpo=25717

   (141) https://bugs.python.org/issue?@action=redirect&bpo=24903

   (142) https://bugs.python.org/issue?@action=redirect&bpo=25764

   (143) https://bugs.python.org/issue?@action=redirect&bpo=25771

   (144) https://bugs.python.org/issue?@action=redirect&bpo=6478

   (145) https://bugs.python.org/issue?@action=redirect&bpo=14285

   (146) https://bugs.python.org/issue?@action=redirect&bpo=19771

   (147) https://bugs.python.org/issue?@action=redirect&bpo=25177

   (148) https://bugs.python.org/issue?@action=redirect&bpo=25718

   (149) https://bugs.python.org/issue?@action=redirect&bpo=10131

   (150) https://bugs.python.org/issue?@action=redirect&bpo=7990

   (151) https://bugs.python.org/issue?@action=redirect&bpo=25725

   (152) https://bugs.python.org/issue?@action=redirect&bpo=25663

   (153) https://bugs.python.org/issue?@action=redirect&bpo=25688

   (154) https://bugs.python.org/issue?@action=redirect&bpo=23914

   (155) https://bugs.python.org/issue?@action=redirect&bpo=25691

   (156) https://bugs.python.org/issue?@action=redirect&bpo=25624

   (157) https://bugs.python.org/issue?@action=redirect&bpo=25626

   (158) https://bugs.python.org/issue?@action=redirect&bpo=25583

   (159) https://bugs.python.org/issue?@action=redirect&bpo=25593

   (160) https://bugs.python.org/issue?@action=redirect&bpo=6973

   (161) https://bugs.python.org/issue?@action=redirect&bpo=23883

   (162) https://bugs.python.org/issue?@action=redirect&bpo=25590

   (163) https://bugs.python.org/issue?@action=redirect&bpo=25498

   (164) https://bugs.python.org/issue?@action=redirect&bpo=25584

   (165) https://bugs.python.org/issue?@action=redirect&bpo=25584

   (166) https://bugs.python.org/issue?@action=redirect&bpo=25446

   (167) https://bugs.python.org/issue?@action=redirect&bpo=18010

   (168) https://bugs.python.org/issue?@action=redirect&bpo=25554

   (169) https://bugs.python.org/issue?@action=redirect&bpo=18973

   (170) https://bugs.python.org/issue?@action=redirect&bpo=25510

   (171) https://bugs.python.org/issue?@action=redirect&bpo=25503

   (172) https://bugs.python.org/issue?@action=redirect&bpo=25515

   (173) https://bugs.python.org/issue?@action=redirect&bpo=21827

   (174) https://bugs.python.org/issue?@action=redirect&bpo=25447

   (175) https://bugs.python.org/issue?@action=redirect&bpo=25390

   (176) https://bugs.python.org/issue?@action=redirect&bpo=25441

   (177) https://bugs.python.org/issue?@action=redirect&bpo=25410

   (178) https://bugs.python.org/issue?@action=redirect&bpo=25411

   (179) https://bugs.python.org/issue?@action=redirect&bpo=25407

   (180) https://bugs.python.org/issue?@action=redirect&bpo=25406

   (181) https://bugs.python.org/issue?@action=redirect&bpo=25382

   (182) https://bugs.python.org/issue?@action=redirect&bpo=25357

   (183) https://bugs.python.org/issue?@action=redirect&bpo=24164

   (184) https://bugs.python.org/issue?@action=redirect&bpo=25364

   (185) https://bugs.python.org/issue?@action=redirect&bpo=25328

   (186) https://bugs.python.org/issue?@action=redirect&bpo=16099

   (187) https://bugs.python.org/issue?@action=redirect&bpo=25316

   (188) https://bugs.python.org/issue?@action=redirect&bpo=25380

   (189) https://bugs.python.org/issue?@action=redirect&bpo=23972

   (190) https://bugs.python.org/issue?@action=redirect&bpo=25304

   (191) https://bugs.python.org/issue?@action=redirect&bpo=25232

   (192) https://bugs.python.org/issue?@action=redirect&bpo=24657

   (193) https://bugs.python.org/issue?@action=redirect&bpo=25287

   (194) https://bugs.python.org/issue?@action=redirect&bpo=23600

   (195) https://bugs.python.org/issue?@action=redirect&bpo=25203

   (196) https://bugs.python.org/issue?@action=redirect&bpo=25011

   (197) https://bugs.python.org/issue?@action=redirect&bpo=25209

   (198) https://bugs.python.org/issue?@action=redirect&bpo=22241

   (199) https://bugs.python.org/issue?@action=redirect&bpo=23517

   (200) https://bugs.python.org/issue?@action=redirect&bpo=23552

   (201) https://bugs.python.org/issue?@action=redirect&bpo=24633

   (202) https://bugs.python.org/issue?@action=redirect&bpo=24879

   (203) https://bugs.python.org/issue?@action=redirect&bpo=24874

   (204) https://bugs.python.org/issue?@action=redirect&bpo=20059

   (205) https://bugs.python.org/issue?@action=redirect&bpo=24360

   (206) https://bugs.python.org/issue?@action=redirect&bpo=23426

   (207) https://bugs.python.org/issue?@action=redirect&bpo=13938

   (208) https://bugs.python.org/issue?@action=redirect&bpo=2091

   (209) https://bugs.python.org/issue?@action=redirect&bpo=8585

   (210) https://bugs.python.org/issue?@action=redirect&bpo=18622

   (211) https://bugs.python.org/issue?@action=redirect&bpo=24426

   (212) https://bugs.python.org/issue?@action=redirect&bpo=23661

   (213) https://bugs.python.org/issue?@action=redirect&bpo=13248

   (214) https://bugs.python.org/issue?@action=redirect&bpo=25578

   (215) https://bugs.python.org/issue?@action=redirect&bpo=25530

   (216) https://bugs.python.org/issue?@action=redirect&bpo=25569

   (217) https://bugs.python.org/issue?@action=redirect&bpo=25471

   (218) https://bugs.python.org/issue?@action=redirect&bpo=25319

   (219) https://bugs.python.org/issue?@action=redirect&bpo=26050

   (220) https://bugs.python.org/issue?@action=redirect&bpo=25924

   (221) https://bugs.python.org/issue?@action=redirect&bpo=26406

   (222) https://bugs.python.org/issue?@action=redirect&bpo=26848

   (223) https://bugs.python.org/issue?@action=redirect&bpo=27040

   (224) https://bugs.python.org/issue?@action=redirect&bpo=27041


File: python.info,  Node: IDLE<54>,  Next: Documentation<64>,  Prev: Library<75>,  Up: Python 3 6 0 alpha 1

1.23.84.4 IDLE
..............

   - bpo-20640(1): Add tests for idlelib.configHelpSourceEdit.  Patch by
     Saimadhav Heblikar.

   - In the 'IDLE-console differences' section of the IDLE doc, clarify
     how running with IDLE affects sys.modules and the standard streams.

   - bpo-25507(2): fix incorrect change in IOBinding that prevented
     printing.  Augment IOBinding htest to include all major IOBinding
     functions.

   - bpo-25905(3): Revert unwanted conversion of ' to ’ RIGHT SINGLE
     QUOTATION MARK in README.txt and open this and NEWS.txt with
     'ascii'.  Re-encode CREDITS.txt to utf-8 and open it with 'utf-8'.

   - bpo-15348(4): Stop the debugger engine (normally in a user process)
     before closing the debugger window (running in the IDLE process).
     This prevents the RuntimeErrors that were being caught and ignored.

   - bpo-24455(5): Prevent IDLE from hanging when a) closing the shell
     while the debugger is active (15347); b) closing the debugger with
     the [X] button (15348); and c) activating the debugger when already
     active (24455).  The patch by Mark Roseman does this by making two
     changes.  1.  Suspend and resume the gui.interaction method with
     the tcl vwait mechanism intended for this purpose (instead of
     root.mainloop & .quit).  2.  In gui.run, allow any existing
     interaction to terminate first.

   - Change 'The program' to 'Your program' in an IDLE 'kill program?'
     message to make it clearer that the program referred to is the
     currently running user program, not IDLE itself.

   - bpo-24750(6): Improve the appearance of the IDLE editor window
     status bar.  Patch by Mark Roseman.

   - bpo-25313(7): Change the handling of new built-in text color themes
     to better address the compatibility problem introduced by the
     addition of IDLE Dark.  Consistently use the revised
     idleConf.CurrentTheme everywhere in idlelib.

   - bpo-24782(8): Extension configuration is now a tab in the IDLE
     Preferences dialog rather than a separate dialog.  The former tabs
     are now a sorted list.  Patch by Mark Roseman.

   - bpo-22726(9): Re-activate the config dialog help button with some
     content about the other buttons and the new IDLE Dark theme.

   - bpo-24820(10): IDLE now has an 'IDLE Dark' built-in text color
     theme.  It is more or less IDLE Classic inverted, with a cobalt
     blue background.  Strings, comments, keywords, ...  are still
     green, red, orange, ...  .  To use it with IDLEs released before
     November 2015, hit the 'Save as New Custom Theme' button and enter
     a new name, such as 'Custom Dark'.  The custom theme will work with
     any IDLE release, and can be modified.

   - bpo-25224(11): README.txt is now an idlelib index for IDLE
     developers and curious users.  The previous user content is now in
     the IDLE doc chapter.  'IDLE' now means 'Integrated Development and
     Learning Environment'.

   - bpo-24820(12): Users can now set breakpoint colors in Settings ->
     Custom Highlighting.  Original patch by Mark Roseman.

   - bpo-24972(13): Inactive selection background now matches active
     selection background, as configured by users, on all systems.
     Found items are now always highlighted on Windows.  Initial patch
     by Mark Roseman.

   - bpo-24570(14): Idle: make calltip and completion boxes appear on
     Macs affected by a tk regression.  Initial patch by Mark Roseman.

   - bpo-24988(15): Idle ScrolledList context menus (used in debugger)
     now work on Mac Aqua.  Patch by Mark Roseman.

   - bpo-24801(16): Make right-click for context menu work on Mac Aqua.
     Patch by Mark Roseman.

   - bpo-25173(17): Associate tkinter messageboxes with a specific
     widget.  For Mac OSX, make them a 'sheet'.  Patch by Mark Roseman.

   - bpo-25198(18): Enhance the initial html viewer now used for Idle
     Help.  Properly indent fixed-pitch text (patch by Mark Roseman).
     Give code snippet a very Sphinx-like light blueish-gray background.
     Re-use initial width and height set by users for shell and editor.
     When the Table of Contents (TOC) menu is used, put the section
     header at the top of the screen.

   - bpo-25225(19): Condense and rewrite Idle doc section on text
     colors.

   - bpo-21995(20): Explain some differences between IDLE and console
     Python.

   - bpo-22820(21): Explain need for 'print' when running file from Idle
     editor.

   - bpo-25224(22): Doc: augment Idle feature list and no-subprocess
     section.

   - bpo-25219(23): Update doc for Idle command line options.  Some were
     missing and notes were not correct.

   - bpo-24861(24): Most of idlelib is private and subject to change.
     Use idleib.idle.* to start Idle.  See idlelib.__init__.__doc__.

   - bpo-25199(25): Idle: add synchronization comments for future
     maintainers.

   - bpo-16893(26): Replace help.txt with help.html for Idle doc
     display.  The new idlelib/help.html is rstripped
     Doc/build/html/library/idle.html.  It looks better than help.txt
     and will better document Idle as released.  The tkinter html viewer
     that works for this file was written by Rose Roseman.  The now
     unused EditorWindow.HelpDialog class and helt.txt file are
     deprecated.

   - bpo-24199(27): Deprecate unused idlelib.idlever with possible
     removal in 3.6.

   - bpo-24790(28): Remove extraneous code (which also create 2 & 3
     conflicts).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=20640

   (2) https://bugs.python.org/issue?@action=redirect&bpo=25507

   (3) https://bugs.python.org/issue?@action=redirect&bpo=25905

   (4) https://bugs.python.org/issue?@action=redirect&bpo=15348

   (5) https://bugs.python.org/issue?@action=redirect&bpo=24455

   (6) https://bugs.python.org/issue?@action=redirect&bpo=24750

   (7) https://bugs.python.org/issue?@action=redirect&bpo=25313

   (8) https://bugs.python.org/issue?@action=redirect&bpo=24782

   (9) https://bugs.python.org/issue?@action=redirect&bpo=22726

   (10) https://bugs.python.org/issue?@action=redirect&bpo=24820

   (11) https://bugs.python.org/issue?@action=redirect&bpo=25224

   (12) https://bugs.python.org/issue?@action=redirect&bpo=24820

   (13) https://bugs.python.org/issue?@action=redirect&bpo=24972

   (14) https://bugs.python.org/issue?@action=redirect&bpo=24570

   (15) https://bugs.python.org/issue?@action=redirect&bpo=24988

   (16) https://bugs.python.org/issue?@action=redirect&bpo=24801

   (17) https://bugs.python.org/issue?@action=redirect&bpo=25173

   (18) https://bugs.python.org/issue?@action=redirect&bpo=25198

   (19) https://bugs.python.org/issue?@action=redirect&bpo=25225

   (20) https://bugs.python.org/issue?@action=redirect&bpo=21995

   (21) https://bugs.python.org/issue?@action=redirect&bpo=22820

   (22) https://bugs.python.org/issue?@action=redirect&bpo=25224

   (23) https://bugs.python.org/issue?@action=redirect&bpo=25219

   (24) https://bugs.python.org/issue?@action=redirect&bpo=24861

   (25) https://bugs.python.org/issue?@action=redirect&bpo=25199

   (26) https://bugs.python.org/issue?@action=redirect&bpo=16893

   (27) https://bugs.python.org/issue?@action=redirect&bpo=24199

   (28) https://bugs.python.org/issue?@action=redirect&bpo=24790


File: python.info,  Node: Documentation<64>,  Next: Tests<68>,  Prev: IDLE<54>,  Up: Python 3 6 0 alpha 1

1.23.84.5 Documentation
.......................

   - bpo-26736(1): Used HTTPS for external links in the documentation if
     possible.

   - bpo-6953(2): Rework the Readline module documentation to group
     related functions together, and add more details such as what
     underlying Readline functions and variables are accessed.

   - bpo-23606(3): Adds note to ctypes documentation regarding
     cdll.msvcrt.

   - bpo-24952(4): Clarify the default size argument of stack_size() in
     the "threading" and "_thread" modules.  Patch from Mattip.

   - bpo-26014(5): Update 3.x packaging documentation: * "See also"
     links to the new docs are now provided in the legacy pages * links
     to setuptools documentation have been updated

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26736

   (2) https://bugs.python.org/issue?@action=redirect&bpo=6953

   (3) https://bugs.python.org/issue?@action=redirect&bpo=23606

   (4) https://bugs.python.org/issue?@action=redirect&bpo=24952

   (5) https://bugs.python.org/issue?@action=redirect&bpo=26014


File: python.info,  Node: Tests<68>,  Next: Build<74>,  Prev: Documentation<64>,  Up: Python 3 6 0 alpha 1

1.23.84.6 Tests
...............

   - bpo-21916(1): Added tests for the turtle module.  Patch by ingrid,
     Gregory Loyse and Jelle Zijlstra.

   - bpo-26295(2): When using "python3 -m test -testdir=TESTDIR",
     regrtest doesn't add "test."  prefix to test module names.

   - bpo-26523(3): The multiprocessing thread pool
     (multiprocessing.dummy.Pool) was untested.

   - bpo-26015(4): Added new tests for pickling iterators of mutable
     sequences.

   - bpo-26325(5): Added test.support.check_no_resource_warning() to
     check that no ResourceWarning is emitted.

   - bpo-25940(6): Changed test_ssl to use its internal local server
     more.  This avoids relying on svn.python.org, which recently
     changed root certificate.

   - bpo-25616(7): Tests for OrderedDict are extracted from
     test_collections into separate file test_ordered_dict.

   - bpo-25449(8): Added tests for OrderedDict subclasses.

   - bpo-25188(9): Add -P/-pgo to test.regrtest to suppress error output
     when running the test suite for the purposes of a PGO build.
     Initial patch by Alecsandru Patrascu.

   - bpo-22806(10): Add ‘python -m test --list-tests’ command to list
     tests.

   - bpo-18174(11): ‘python -m test --huntrleaks ...’ now also checks
     for leak of file descriptors.  Patch written by Richard Oudkerk.

   - bpo-25260(12): Fix ‘python -m test --coverage’ on Windows.  Remove
     the list of ignored directories.

   - ‘PCbuild\rt.bat’ now accepts an unlimited number of arguments to
     pass along to regrtest.py.  Previously there was a limit of 9.

   - bpo-26583(13): Skip test_timestamp_overflow in test_import if
     bytecode files cannot be written.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21916

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26295

   (3) https://bugs.python.org/issue?@action=redirect&bpo=26523

   (4) https://bugs.python.org/issue?@action=redirect&bpo=26015

   (5) https://bugs.python.org/issue?@action=redirect&bpo=26325

   (6) https://bugs.python.org/issue?@action=redirect&bpo=25940

   (7) https://bugs.python.org/issue?@action=redirect&bpo=25616

   (8) https://bugs.python.org/issue?@action=redirect&bpo=25449

   (9) https://bugs.python.org/issue?@action=redirect&bpo=25188

   (10) https://bugs.python.org/issue?@action=redirect&bpo=22806

   (11) https://bugs.python.org/issue?@action=redirect&bpo=18174

   (12) https://bugs.python.org/issue?@action=redirect&bpo=25260

   (13) https://bugs.python.org/issue?@action=redirect&bpo=26583


File: python.info,  Node: Build<74>,  Next: Windows<64>,  Prev: Tests<68>,  Up: Python 3 6 0 alpha 1

1.23.84.7 Build
...............

   - bpo-21277(1): Don't try to link _ctypes with a ffi_convenience
     library.

   - bpo-26884(2): Fix linking extension modules for cross builds.
     Patch by Xavier de Gaye.

   - bpo-26932(3): Fixed support of RTLD_* constants defined as enum
     values, not via macros (in particular on Android).  Patch by Chi
     Hsuan Yen.

   - bpo-22359(4): Disable the rules for running _freeze_importlib and
     pgen when cross-compiling.  The output of these programs is
     normally saved with the source code anyway, and is still
     regenerated when doing a native build.  Patch by Xavier de Gaye.

   - bpo-21668(5): Link audioop, _datetime, _ctypes_test modules to
     libm, except on Mac OS X. Patch written by Chi Hsuan Yen.

   - bpo-25702(6): A -with-lto configure option has been added that will
     enable link time optimizations at build time during a make
     profile-opt.  Some compilers and toolchains are known to not
     produce stable code when using LTO, be sure to test things
     thoroughly before relying on it.  It can provide a few % speed up
     over profile-opt alone.

   - bpo-26624(7): Adds validation of ucrtbase[d].dll version with
     warning for old versions.

   - bpo-17603(8): Avoid error about nonexistent fileblocks.o file by
     using a lower-level check for st_blocks in struct stat.

   - bpo-26079(9): Fixing the build output folder for tix-8.4.3.6.
     Patch by Bjoern Thiel.

   - bpo-26465(10): Update Windows builds to use OpenSSL 1.0.2g.

   - bpo-25348(11): Added ‘--pgo’ and ‘--pgo-job’ arguments to
     ‘PCbuild\build.bat’ for building with Profile-Guided Optimization.
     The old ‘PCbuild\build_pgo.bat’ script is removed.

   - bpo-25827(12): Add support for building with ICC to ‘configure’,
     including a new ‘--with-icc’ flag.

   - bpo-25696(13): Fix installation of Python on UNIX with make -j9.

   - bpo-24986(14): It is now possible to build Python on Windows
     without errors when external libraries are not available.

   - bpo-24421(15): Compile Modules/_math.c once, before building
     extensions.  Previously it could fail to compile properly if the
     math and cmath builds were concurrent.

   - bpo-26465(16): Update OS X 10.5+ 32-bit-only installer to build and
     link with OpenSSL 1.0.2g.

   - bpo-26268(17): Update Windows builds to use OpenSSL 1.0.2f.

   - bpo-25136(18): Support Apple Xcode 7's new textual SDK stub
     libraries.

   - bpo-24324(19): Do not enable unreachable code warnings when using
     gcc as the option does not work correctly in older versions of gcc
     and has been silently removed as of gcc-4.5.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21277

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26884

   (3) https://bugs.python.org/issue?@action=redirect&bpo=26932

   (4) https://bugs.python.org/issue?@action=redirect&bpo=22359

   (5) https://bugs.python.org/issue?@action=redirect&bpo=21668

   (6) https://bugs.python.org/issue?@action=redirect&bpo=25702

   (7) https://bugs.python.org/issue?@action=redirect&bpo=26624

   (8) https://bugs.python.org/issue?@action=redirect&bpo=17603

   (9) https://bugs.python.org/issue?@action=redirect&bpo=26079

   (10) https://bugs.python.org/issue?@action=redirect&bpo=26465

   (11) https://bugs.python.org/issue?@action=redirect&bpo=25348

   (12) https://bugs.python.org/issue?@action=redirect&bpo=25827

   (13) https://bugs.python.org/issue?@action=redirect&bpo=25696

   (14) https://bugs.python.org/issue?@action=redirect&bpo=24986

   (15) https://bugs.python.org/issue?@action=redirect&bpo=24421

   (16) https://bugs.python.org/issue?@action=redirect&bpo=26465

   (17) https://bugs.python.org/issue?@action=redirect&bpo=26268

   (18) https://bugs.python.org/issue?@action=redirect&bpo=25136

   (19) https://bugs.python.org/issue?@action=redirect&bpo=24324


File: python.info,  Node: Windows<64>,  Next: Tools/Demos<40>,  Prev: Build<74>,  Up: Python 3 6 0 alpha 1

1.23.84.8 Windows
.................

   - bpo-27053(1): Updates make_zip.py to correctly generate library ZIP
     file.

   - bpo-26268(2): Update the prepare_ssl.py script to handle OpenSSL
     releases that don't include the contents of the include directory
     (that is, 1.0.2e and later).

   - bpo-26071(3): bdist_wininst created binaries fail to start and find
     32bit Python

   - bpo-26073(4): Update the list of magic numbers in launcher

   - bpo-26065(5): Excludes venv from library when generating embeddable
     distro.

   - bpo-25022(6): Removed very outdated PC/example_nt/ directory.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27053

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26268

   (3) https://bugs.python.org/issue?@action=redirect&bpo=26071

   (4) https://bugs.python.org/issue?@action=redirect&bpo=26073

   (5) https://bugs.python.org/issue?@action=redirect&bpo=26065

   (6) https://bugs.python.org/issue?@action=redirect&bpo=25022


File: python.info,  Node: Tools/Demos<40>,  Next: C API<64>,  Prev: Windows<64>,  Up: Python 3 6 0 alpha 1

1.23.84.9 Tools/Demos
.....................

   - bpo-26799(1): Fix python-gdb.py: don't get C types once when the
     Python code is loaded, but get C types on demand.  The C types can
     change if python-gdb.py is loaded before the Python executable.
     Patch written by Thomas Ilsche.

   - bpo-26271(2): Fix the Freeze tool to properly use flags passed
     through configure.  Patch by Daniel Shaulov.

   - bpo-26489(3): Add dictionary unpacking support to
     Tools/parser/unparse.py.  Patch by Guo Ci Teo.

   - bpo-26316(4): Fix variable name typo in Argument Clinic.

   - bpo-25440(5): Fix output of python-config -extension-suffix.

   - bpo-25154(6): The pyvenv script has been deprecated in favour of
     ‘python3 -m venv’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26799

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26271

   (3) https://bugs.python.org/issue?@action=redirect&bpo=26489

   (4) https://bugs.python.org/issue?@action=redirect&bpo=26316

   (5) https://bugs.python.org/issue?@action=redirect&bpo=25440

   (6) https://bugs.python.org/issue?@action=redirect&bpo=25154


File: python.info,  Node: C API<64>,  Prev: Tools/Demos<40>,  Up: Python 3 6 0 alpha 1

1.23.84.10 C API
................

   - bpo-26312(1): SystemError is now raised in all programming bugs
     with using PyArg_ParseTupleAndKeywords().  RuntimeError did raised
     before in some programming bugs.

   - bpo-26198(2): ValueError is now raised instead of TypeError on
     buffer overflow in parsing "es#" and "et#" format units.
     SystemError is now raised instead of TypeError on programmatical
     error in parsing format string.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26312

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26198


File: python.info,  Node: Python 3 5 5 final,  Next: Python 3 5 5 release candidate 1,  Prev: Python 3 6 0 alpha 1,  Up: Changelog（更動日誌）

1.23.85 Python 3.5.5 final
--------------------------

'Release date: 2018-02-04'

There were no new changes in version 3.5.5.


File: python.info,  Node: Python 3 5 5 release candidate 1,  Next: Python 3 5 4 final,  Prev: Python 3 5 5 final,  Up: Changelog（更動日誌）

1.23.86 Python 3.5.5 release candidate 1
----------------------------------------

'Release date: 2018-01-23'

* Menu:

* Security: Security<44>.
* Core and Builtins: Core and Builtins<77>.
* Library: Library<76>.


File: python.info,  Node: Security<44>,  Next: Core and Builtins<77>,  Up: Python 3 5 5 release candidate 1

1.23.86.1 Security
..................

   - bpo-32551(1): The ‘sys.path[0]’ initialization change for
     bpo-29139(2) caused a regression by revealing an inconsistency in
     how sys.path is initialized when executing ‘__main__’ from a
     zipfile, directory, or other import location.  This is considered a
     potential security issue, as it may lead to privileged processes
     unexpectedly loading code from user controlled directories in
     situations where that was not previously the case.  The interpreter
     now consistently avoids ever adding the import location's parent
     directory to ‘sys.path’, and ensures no other ‘sys.path’ entries
     are inadvertently modified when inserting the import location named
     on the command line.  (Originally reported as bpo-29723(3) against
     Python 3.6rc1, but it was missed at the time that the then upcoming
     Python 3.5.4 release would also be affected)

   - bpo-30657(4): Fixed possible integer overflow in
     PyBytes_DecodeEscape, CVE-2017-1000158(5).  Original patch by Jay
     Bosamiya; rebased to Python 3 by Miro Hrončok.

   - bpo-30947(6): Upgrade libexpat embedded copy from version 2.2.1 to
     2.2.3 to get security fixes.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32551

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29139

   (3) https://bugs.python.org/issue?@action=redirect&bpo=29723

   (4) https://bugs.python.org/issue?@action=redirect&bpo=30657

   (5) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000158

   (6) https://bugs.python.org/issue?@action=redirect&bpo=30947


File: python.info,  Node: Core and Builtins<77>,  Next: Library<76>,  Prev: Security<44>,  Up: Python 3 5 5 release candidate 1

1.23.86.2 Core and Builtins
...........................

   - bpo-31095(1): Fix potential crash during GC caused by ‘tp_dealloc’
     which doesn't call ‘PyObject_GC_UnTrack()’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=31095


File: python.info,  Node: Library<76>,  Prev: Core and Builtins<77>,  Up: Python 3 5 5 release candidate 1

1.23.86.3 Library
.................

   - bpo-32072(1): Fixed issues with binary plists: Fixed saving
     bytearrays.  Identical objects will be saved only once.  Equal
     references will be load as identical objects.  Added support for
     saving and loading recursive data structures.

   - bpo-31170(2): expat: Update libexpat from 2.2.3 to 2.2.4.  Fix
     copying of partial characters for UTF-8 input (libexpat bug 115):
     ‘https://github.com/libexpat/libexpat/issues/115’

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=32072

   (2) https://bugs.python.org/issue?@action=redirect&bpo=31170


File: python.info,  Node: Python 3 5 4 final,  Next: Python 3 5 4 release candidate 1,  Prev: Python 3 5 5 release candidate 1,  Up: Changelog（更動日誌）

1.23.87 Python 3.5.4 final
--------------------------

'Release date: 2017-08-07'

* Menu:

* Library: Library<77>.


File: python.info,  Node: Library<77>,  Up: Python 3 5 4 final

1.23.87.1 Library
.................

   - bpo-30119(1): ftplib.FTP.putline() now throws ValueError on
     commands that contains CR or LF. Patch by Donghee Na.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30119


File: python.info,  Node: Python 3 5 4 release candidate 1,  Next: Python 3 5 3 final,  Prev: Python 3 5 4 final,  Up: Changelog（更動日誌）

1.23.88 Python 3.5.4 release candidate 1
----------------------------------------

'Release date: 2017-07-23'

* Menu:

* Security: Security<45>.
* Core and Builtins: Core and Builtins<78>.
* Library: Library<78>.
* Documentation: Documentation<65>.
* Tests: Tests<69>.
* Build: Build<75>.
* Windows: Windows<65>.
* C API: C API<65>.


File: python.info,  Node: Security<45>,  Next: Core and Builtins<78>,  Up: Python 3 5 4 release candidate 1

1.23.88.1 Security
..................

   - bpo-30730(1): Prevent environment variables injection in subprocess
     on Windows.  Prevent passing other environment variables and
     command arguments.

   - bpo-30694(2): Upgrade expat copy from 2.2.0 to 2.2.1 to get fixes
     of multiple security vulnerabilities including: CVE-2017-9233(3)
     (External entity infinite loop DoS), CVE-2016-9063(4) (Integer
     overflow, re-fix), CVE-2016-0718(5) (Fix regression bugs from
     2.2.0's fix to CVE-2016-0718(6)) and CVE-2012-0876(7) (Counter hash
     flooding with SipHash).  Note: the CVE-2016-5300(8) (Use
     os-specific entropy sources like getrandom) doesn't impact Python,
     since Python already gets entropy from the OS to set the expat
     secret using ‘XML_SetHashSalt()’.

   - bpo-30500(9): Fix urllib.parse.splithost() to correctly parse
     fragments.  For example, ‘splithost('//127.0.0.1#@evil.com/')’ now
     correctly returns the ‘127.0.0.1’ host, instead of treating
     ‘@evil.com’ as the host in an authentication (‘login@host’).

   - bpo-29591(10): Update expat copy from 2.1.1 to 2.2.0 to get fixes
     of CVE-2016-0718(11) and CVE-2016-4472(12).  See
     ‘https://sourceforge.net/p/expat/bugs/537/’ for more information.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30730

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30694

   (3) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9233

   (4) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9063

   (5) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0718

   (6) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0718

   (7) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0876

   (8) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5300

   (9) https://bugs.python.org/issue?@action=redirect&bpo=30500

   (10) https://bugs.python.org/issue?@action=redirect&bpo=29591

   (11) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0718

   (12) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4472


File: python.info,  Node: Core and Builtins<78>,  Next: Library<78>,  Prev: Security<45>,  Up: Python 3 5 4 release candidate 1

1.23.88.2 Core and Builtins
...........................

   - bpo-30876(1): Relative import from unloaded package now reimports
     the package instead of failing with SystemError.  Relative import
     from non-package now fails with ImportError rather than
     SystemError.

   - bpo-30765(2): Avoid blocking in pthread_mutex_lock() when
     PyThread_acquire_lock() is asked not to block.

   - bpo-27945(3): Fixed various segfaults with dict when input
     collections are mutated during searching, inserting or comparing.
     Based on patches by Duane Griffin and Tim Mitchell.

   - bpo-25794(4): Fixed type.__setattr__() and type.__delattr__() for
     non-interned attribute names.  Based on patch by Eryk Sun.

   - bpo-29935(5): Fixed error messages in the index() method of tuple,
     list and deque when pass indices of wrong type.

   - bpo-28876(6): ‘bool(range)’ works even if ‘len(range)’ raises *note
     OverflowError: 825.

   - bpo-29600(7): Fix wrapping coroutine return values in
     StopIteration.

   - bpo-29537(8): Restore runtime compatibility with bytecode files
     generated by CPython 3.5.0 to 3.5.2, and adjust the eval loop to
     avoid the problems that could be caused by the malformed variant of
     the BUILD_MAP_UNPACK_WITH_CALL opcode that they may contain.  Patch
     by Petr Viktorin, Serhiy Storchaka, and Nick Coghlan.

   - bpo-28598(9): Support __rmod__ for subclasses of str being called
     before str.__mod__.  Patch by Martijn Pieters.

   - bpo-29602(10): Fix incorrect handling of signed zeros in complex
     constructor for complex subclasses and for inputs having a
     __complex__ method.  Patch by Serhiy Storchaka.

   - bpo-29347(11): Fixed possibly dereferencing undefined pointers when
     creating weakref objects.

   - bpo-29438(12): Fixed use-after-free problem in key sharing dict.

   - bpo-29319(13): Prevent RunMainFromImporter overwriting sys.path[0].

   - bpo-29337(14): Fixed possible BytesWarning when compare the code
     objects.  Warnings could be emitted at compile time.

   - bpo-29478(15): If max_line_length=None is specified while using the
     Compat32 policy, it is no longer ignored.  Patch by Mircea Cosbuc.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30876

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30765

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27945

   (4) https://bugs.python.org/issue?@action=redirect&bpo=25794

   (5) https://bugs.python.org/issue?@action=redirect&bpo=29935

   (6) https://bugs.python.org/issue?@action=redirect&bpo=28876

   (7) https://bugs.python.org/issue?@action=redirect&bpo=29600

   (8) https://bugs.python.org/issue?@action=redirect&bpo=29537

   (9) https://bugs.python.org/issue?@action=redirect&bpo=28598

   (10) https://bugs.python.org/issue?@action=redirect&bpo=29602

   (11) https://bugs.python.org/issue?@action=redirect&bpo=29347

   (12) https://bugs.python.org/issue?@action=redirect&bpo=29438

   (13) https://bugs.python.org/issue?@action=redirect&bpo=29319

   (14) https://bugs.python.org/issue?@action=redirect&bpo=29337

   (15) https://bugs.python.org/issue?@action=redirect&bpo=29478


File: python.info,  Node: Library<78>,  Next: Documentation<65>,  Prev: Core and Builtins<78>,  Up: Python 3 5 4 release candidate 1

1.23.88.3 Library
.................

   - bpo-29403(1): Fix ‘unittest.mock’'s autospec to not fail on
     method-bound builtin functions.  Patch by Aaron Gallagher.

   - bpo-30961(2): Fix decrementing a borrowed reference in tracemalloc.

   - bpo-30886(3): Fix multiprocessing.Queue.join_thread(): it now waits
     until the thread completes, even if the thread was started by the
     same process which created the queue.

   - bpo-29854(4): Fix segfault in readline when using readline's
     history-size option.  Patch by Nir Soffer.

   - bpo-30807(5): signal.setitimer() may disable the timer when passed
     a tiny value.  Tiny values (such as 1e-6) are valid non-zero values
     for setitimer(), which is specified as taking
     microsecond-resolution intervals.  However, on some platform, our
     conversion routine could convert 1e-6 into a zero interval,
     therefore disabling the timer instead of (re-)scheduling it.

   - bpo-30441(6): Fix bug when modifying os.environ while iterating
     over it

   - bpo-30532(7): Fix email header value parser dropping folding white
     space in certain cases.

   - bpo-29169(8): Update zlib to 1.2.11.

   - bpo-30879(9): os.listdir() and os.scandir() now emit bytes names
     when called with bytes-like argument.

   - bpo-30746(10): Prohibited the '=' character in environment variable
     names in ‘os.putenv()’ and ‘os.spawn*()’.

   - bpo-29755(11): Fixed the lgettext() family of functions in the
     gettext module.  They now always return bytes.

   - bpo-30645(12): Fix path calculation in imp.load_package(), fixing
     it for cases when a package is only shipped with bytecodes.  Patch
     by Alexandru Ardelean.

   - bpo-23890(13): unittest.TestCase.assertRaises() now manually breaks
     a reference cycle to not keep objects alive longer than expected.

   - bpo-30149(14): inspect.signature() now supports callables with
     variable-argument parameters wrapped with partialmethod.  Patch by
     Donghee Na.

   - bpo-29931(15): Fixed comparison check for ipaddress.ip_interface
     objects.  Patch by Sanjay Sundaresan.

   - bpo-24484(16): Avoid race condition in multiprocessing cleanup.

   - bpo-28994(17): The traceback no longer displayed for SystemExit
     raised in a callback registered by atexit.

   - bpo-30508(18): Don't log exceptions if Task/Future "cancel()"
     method was called.

   - bpo-28556(19): Updates to typing module: Add generic
     AsyncContextManager, add support for ContextManager on all
     versions.  Original PRs by Jelle Zijlstra and Ivan Levkivskyi

   - bpo-29870(20): Fix ssl sockets leaks when connection is aborted in
     asyncio/ssl implementation.  Patch by Michaël Sghaïer.

   - bpo-29743(21): Closing transport during handshake process leaks
     open socket.  Patch by Nikolay Kim

   - bpo-27585(22): Fix waiter cancellation in asyncio.Lock.  Patch by
     Mathieu Sornay.

   - bpo-30418(23): On Windows, subprocess.Popen.communicate() now also
     ignore EINVAL on stdin.write() if the child process is still
     running but closed the pipe.

   - bpo-30378(24): Fix the problem that logging.handlers.SysLogHandler
     cannot handle IPv6 addresses.

   - bpo-29960(25): Preserve generator state when
     _random.Random.setstate() raises an exception.  Patch by Bryan
     Olson.

   - bpo-30414(26): multiprocessing.Queue._feed background running
     thread do not break from main loop on exception.

   - bpo-30003(27): Fix handling escape characters in HZ codec.  Based
     on patch by Ma Lin.

   - bpo-30301(28): Fix AttributeError when using SimpleQueue.empty()
     under 'spawn' and 'forkserver' start methods.

   - bpo-30329(29): imaplib and poplib now catch the Windows socket
     WSAEINVAL error (code 10022) on shutdown(SHUT_RDWR): An invalid
     operation was attempted.  This error occurs sometimes on SSL
     connections.

   - bpo-30375(30): Warnings emitted when compile a regular expression
     now always point to the line in the user code.  Previously they
     could point into inners of the re module if emitted from inside of
     groups or conditionals.

   - bpo-30048(31): Fixed ‘Task.cancel()’ can be ignored when the task
     is running coroutine and the coroutine returned without any more
     ‘await’.

   - bpo-29990(32): Fix range checking in GB18030 decoder.  Original
     patch by Ma Lin.

   - bpo-26293(33): Change resulted because of zipfile breakage.  (See
     also: bpo-29094(34))

   - bpo-30243(35): Removed the __init__ methods of _json's scanner and
     encoder.  Misusing them could cause memory leaks or crashes.  Now
     scanner and encoder objects are completely initialized in the
     __new__ methods.

   - bpo-30185(36): Avoid KeyboardInterrupt tracebacks in forkserver
     helper process when Ctrl-C is received.

   - bpo-28556(37): Various updates to typing module: add
     typing.NoReturn type, use WrapperDescriptorType, minor bug-fixes.
     Original PRs by Jim Fasarakis-Hilliard and Ivan Levkivskyi.

   - bpo-30205(38): Fix getsockname() for unbound AF_UNIX sockets on
     Linux.

   - bpo-30070(39): Fixed leaks and crashes in errors handling in the
     parser module.

   - bpo-30061(40): Fixed crashes in IOBase methods __next__() and
     readlines() when readline() or __next__() respectively return
     non-sizeable object.  Fixed possible other errors caused by not
     checking results of PyObject_Size(), PySequence_Size(), or
     PyMapping_Size().

   - bpo-30068(41): _io._IOBase.readlines will check if it's closed
     first when hint is present.

   - bpo-29694(42): Fixed race condition in pathlib mkdir with flags
     parents=True.  Patch by Armin Rigo.

   - bpo-29692(43): Fixed arbitrary unchaining of RuntimeError
     exceptions in contextlib.contextmanager.  Patch by Siddharth
     Velankar.

   - bpo-29998(44): Pickling and copying ImportError now preserves name
     and path attributes.

   - bpo-29942(45): Fix a crash in itertools.chain.from_iterable when
     encountering long runs of empty iterables.

   - bpo-27863(46): Fixed multiple crashes in ElementTree caused by race
     conditions and wrong types.

   - bpo-28699(47): Fixed a bug in pools in multiprocessing.pool that
     raising an exception at the very first of an iterable may swallow
     the exception or make the program hang.  Patch by Davin Potts and
     Xiang Zhang.

   - bpo-25803(48): Avoid incorrect errors raised by
     Path.mkdir(exist_ok=True) when the OS gives priority to errors such
     as EACCES over EEXIST.

   - bpo-29861(49): Release references to tasks, their arguments and
     their results as soon as they are finished in multiprocessing.Pool.

   - bpo-29884(50): faulthandler: Restore the old sigaltstack during
     teardown.  Patch by Christophe Zeitouny.

   - bpo-25455(51): Fixed crashes in repr of recursive buffered
     file-like objects.

   - bpo-29800(52): Fix crashes in partial.__repr__ if the keys of
     partial.keywords are not strings.  Patch by Michael Seifert.

   - bpo-29742(53): get_extra_info() raises exception if get called on
     closed ssl transport.  Patch by Nikolay Kim.

   - bpo-8256(54): Fixed possible failing or crashing input() if
     attributes "encoding" or "errors" of sys.stdin or sys.stdout are
     not set or are not strings.

   - bpo-28298(55): Fix a bug that prevented array 'Q', 'L' and 'I' from
     accepting big intables (objects that have __int__) as elements.
     Patch by Oren Milman.

   - bpo-29615(56): SimpleXMLRPCDispatcher no longer chains KeyError (or
     any other exception) to exception(s) raised in the dispatched
     methods.  Patch by Petr Motejlek.

   - bpo-29704(57): asyncio.subprocess.SubprocessStreamProtocol no
     longer closes before all pipes are closed.

   - bpo-29703(58): Fix asyncio to support instantiation of new event
     loops in child processes.

   - bpo-29376(59): Fix assertion error in
     threading._DummyThread.is_alive().

   - bpo-29110(60): Fix file object leak in aifc.open() when file is
     given as a filesystem path and is not in valid AIFF format.  Patch
     by Anthony Zhang.

   - bpo-28961(61): Fix unittest.mock._Call helper: don't ignore the
     name parameter anymore.  Patch written by Jiajun Huang.

   - bpo-29532(62): Altering a kwarg dictionary passed to
     functools.partial() no longer affects a partial object after
     creation.

   - bpo-28556(63): Various updates to typing module: typing.Counter,
     typing.ChainMap, improved ABC caching, etc.  Original PRs by Jelle
     Zijlstra, Ivan Levkivskyi, Manuel Krebber, and Łukasz Langa.

   - bpo-29100(64): Fix datetime.fromtimestamp() regression introduced
     in Python 3.6.0: check minimum and maximum years.

   - bpo-29519(65): Fix weakref spewing exceptions during interpreter
     shutdown when used with a rare combination of multiprocessing and
     custom codecs.

   - bpo-29416(66): Prevent infinite loop in pathlib.Path.mkdir

   - bpo-29444(67): Fixed out-of-bounds buffer access in the group()
     method of the match object.  Based on patch by WGH.

   - bpo-29335(68): Fix subprocess.Popen.wait() when the child process
     has exited to a stopped instead of terminated state (ex: when under
     ptrace).

   - bpo-29290(69): Fix a regression in argparse that help messages
     would wrap at non-breaking spaces.

   - bpo-28735(70): Fixed the comparison of mock.MagickMock with
     mock.ANY.

   - bpo-29011(71): Fix an important omission by adding Deque to the
     typing module.

   - bpo-29219(72): Fixed infinite recursion in the repr of
     uninitialized ctypes.CDLL instances.

   - bpo-28969(73): Fixed race condition in C implementation of
     functools.lru_cache.  KeyError could be raised when cached function
     with full cache was simultaneously called from different threads
     with the same uncached arguments.

   - bpo-29142(74): In urllib.request, suffixes in no_proxy environment
     variable with leading dots could match related hostnames again
     (e.g.  .b.c matches a.b.c).  Patch by Milan Oberkirch.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29403

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30961

   (3) https://bugs.python.org/issue?@action=redirect&bpo=30886

   (4) https://bugs.python.org/issue?@action=redirect&bpo=29854

   (5) https://bugs.python.org/issue?@action=redirect&bpo=30807

   (6) https://bugs.python.org/issue?@action=redirect&bpo=30441

   (7) https://bugs.python.org/issue?@action=redirect&bpo=30532

   (8) https://bugs.python.org/issue?@action=redirect&bpo=29169

   (9) https://bugs.python.org/issue?@action=redirect&bpo=30879

   (10) https://bugs.python.org/issue?@action=redirect&bpo=30746

   (11) https://bugs.python.org/issue?@action=redirect&bpo=29755

   (12) https://bugs.python.org/issue?@action=redirect&bpo=30645

   (13) https://bugs.python.org/issue?@action=redirect&bpo=23890

   (14) https://bugs.python.org/issue?@action=redirect&bpo=30149

   (15) https://bugs.python.org/issue?@action=redirect&bpo=29931

   (16) https://bugs.python.org/issue?@action=redirect&bpo=24484

   (17) https://bugs.python.org/issue?@action=redirect&bpo=28994

   (18) https://bugs.python.org/issue?@action=redirect&bpo=30508

   (19) https://bugs.python.org/issue?@action=redirect&bpo=28556

   (20) https://bugs.python.org/issue?@action=redirect&bpo=29870

   (21) https://bugs.python.org/issue?@action=redirect&bpo=29743

   (22) https://bugs.python.org/issue?@action=redirect&bpo=27585

   (23) https://bugs.python.org/issue?@action=redirect&bpo=30418

   (24) https://bugs.python.org/issue?@action=redirect&bpo=30378

   (25) https://bugs.python.org/issue?@action=redirect&bpo=29960

   (26) https://bugs.python.org/issue?@action=redirect&bpo=30414

   (27) https://bugs.python.org/issue?@action=redirect&bpo=30003

   (28) https://bugs.python.org/issue?@action=redirect&bpo=30301

   (29) https://bugs.python.org/issue?@action=redirect&bpo=30329

   (30) https://bugs.python.org/issue?@action=redirect&bpo=30375

   (31) https://bugs.python.org/issue?@action=redirect&bpo=30048

   (32) https://bugs.python.org/issue?@action=redirect&bpo=29990

   (33) https://bugs.python.org/issue?@action=redirect&bpo=26293

   (34) https://bugs.python.org/issue?@action=redirect&bpo=29094

   (35) https://bugs.python.org/issue?@action=redirect&bpo=30243

   (36) https://bugs.python.org/issue?@action=redirect&bpo=30185

   (37) https://bugs.python.org/issue?@action=redirect&bpo=28556

   (38) https://bugs.python.org/issue?@action=redirect&bpo=30205

   (39) https://bugs.python.org/issue?@action=redirect&bpo=30070

   (40) https://bugs.python.org/issue?@action=redirect&bpo=30061

   (41) https://bugs.python.org/issue?@action=redirect&bpo=30068

   (42) https://bugs.python.org/issue?@action=redirect&bpo=29694

   (43) https://bugs.python.org/issue?@action=redirect&bpo=29692

   (44) https://bugs.python.org/issue?@action=redirect&bpo=29998

   (45) https://bugs.python.org/issue?@action=redirect&bpo=29942

   (46) https://bugs.python.org/issue?@action=redirect&bpo=27863

   (47) https://bugs.python.org/issue?@action=redirect&bpo=28699

   (48) https://bugs.python.org/issue?@action=redirect&bpo=25803

   (49) https://bugs.python.org/issue?@action=redirect&bpo=29861

   (50) https://bugs.python.org/issue?@action=redirect&bpo=29884

   (51) https://bugs.python.org/issue?@action=redirect&bpo=25455

   (52) https://bugs.python.org/issue?@action=redirect&bpo=29800

   (53) https://bugs.python.org/issue?@action=redirect&bpo=29742

   (54) https://bugs.python.org/issue?@action=redirect&bpo=8256

   (55) https://bugs.python.org/issue?@action=redirect&bpo=28298

   (56) https://bugs.python.org/issue?@action=redirect&bpo=29615

   (57) https://bugs.python.org/issue?@action=redirect&bpo=29704

   (58) https://bugs.python.org/issue?@action=redirect&bpo=29703

   (59) https://bugs.python.org/issue?@action=redirect&bpo=29376

   (60) https://bugs.python.org/issue?@action=redirect&bpo=29110

   (61) https://bugs.python.org/issue?@action=redirect&bpo=28961

   (62) https://bugs.python.org/issue?@action=redirect&bpo=29532

   (63) https://bugs.python.org/issue?@action=redirect&bpo=28556

   (64) https://bugs.python.org/issue?@action=redirect&bpo=29100

   (65) https://bugs.python.org/issue?@action=redirect&bpo=29519

   (66) https://bugs.python.org/issue?@action=redirect&bpo=29416

   (67) https://bugs.python.org/issue?@action=redirect&bpo=29444

   (68) https://bugs.python.org/issue?@action=redirect&bpo=29335

   (69) https://bugs.python.org/issue?@action=redirect&bpo=29290

   (70) https://bugs.python.org/issue?@action=redirect&bpo=28735

   (71) https://bugs.python.org/issue?@action=redirect&bpo=29011

   (72) https://bugs.python.org/issue?@action=redirect&bpo=29219

   (73) https://bugs.python.org/issue?@action=redirect&bpo=28969

   (74) https://bugs.python.org/issue?@action=redirect&bpo=29142


File: python.info,  Node: Documentation<65>,  Next: Tests<69>,  Prev: Library<78>,  Up: Python 3 5 4 release candidate 1

1.23.88.4 Documentation
.......................

   - bpo-30176(1): Add missing attribute related constants in curses
     documentation.

   - bpo-26985(2): Add missing info of code object in inspect
     documentation.

   - bpo-28929(3): Link the documentation to its source file on GitHub.

   - bpo-25008(4): Document smtpd.py as effectively deprecated and add a
     pointer to aiosmtpd, a third-party asyncio-based replacement.

   - bpo-26355(5): Add canonical header link on each page to
     corresponding major version of the documentation.  Patch by
     Matthias Bussonnier.

   - bpo-29349(6): Fix Python 2 syntax in code for building the
     documentation.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30176

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26985

   (3) https://bugs.python.org/issue?@action=redirect&bpo=28929

   (4) https://bugs.python.org/issue?@action=redirect&bpo=25008

   (5) https://bugs.python.org/issue?@action=redirect&bpo=26355

   (6) https://bugs.python.org/issue?@action=redirect&bpo=29349


File: python.info,  Node: Tests<69>,  Next: Build<75>,  Prev: Documentation<65>,  Up: Python 3 5 4 release candidate 1

1.23.88.5 Tests
...............

   - bpo-30822(1): Fix regrtest command line parser to allow passing -u
     extralargefile to run test_zipfile64.

   - bpo-30383(2): regrtest: Enhance regrtest and backport features from
     the master branch.  Add options: -coverage, -testdir, -list-tests
     (list test files, don't run them), -list-cases (list test
     identifiers, don't run them, bpo-30523(3)), -matchfile (load a list
     of test filters from a text file, bpo-30540(4)), -slowest (alias to
     -slow).  Enhance output: add timestamp, test result, currently
     running tests, "Tests result: xxx" summary with total duration,
     etc.  Fix reference leak hunting in regrtest, -huntrleaks: regrtest
     now warms up caches, create explicitly all internal singletons
     which are created on demand to prevent false positives when
     checking for reference leaks.  (bpo-30675(5)).

   - bpo-30357(6): test_thread: setUp() now uses
     support.threading_setup() and support.threading_cleanup() to wait
     until threads complete to avoid random side effects on following
     tests.  Initial patch written by Grzegorz Grzywacz.

   - bpo-28087(7): Skip test_asyncore and test_eintr poll failures on
     macOS. Skip some tests of select.poll when running on macOS due to
     unresolved issues with the underlying system poll function on some
     macOS versions.

   - bpo-30197(8): Enhanced functions swap_attr() and swap_item() in the
     test.support module.  They now work when delete replaced attribute
     or item inside the with statement.  The old value of the attribute
     or item (or None if it doesn't exist) now will be assigned to the
     target of the "as" clause, if there is one.

   - bpo-29571(9): to match the behaviour of the ‘re.LOCALE’ flag,
     test_re.test_locale_flag now uses
     ‘locale.getpreferredencoding(False)’ to determine the candidate
     encoding for the test regex (allowing it to correctly skip the test
     when the default locale encoding is a multi-byte encoding)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30822

   (2) https://bugs.python.org/issue?@action=redirect&bpo=30383

   (3) https://bugs.python.org/issue?@action=redirect&bpo=30523

   (4) https://bugs.python.org/issue?@action=redirect&bpo=30540

   (5) https://bugs.python.org/issue?@action=redirect&bpo=30675

   (6) https://bugs.python.org/issue?@action=redirect&bpo=30357

   (7) https://bugs.python.org/issue?@action=redirect&bpo=28087

   (8) https://bugs.python.org/issue?@action=redirect&bpo=30197

   (9) https://bugs.python.org/issue?@action=redirect&bpo=29571


File: python.info,  Node: Build<75>,  Next: Windows<65>,  Prev: Tests<69>,  Up: Python 3 5 4 release candidate 1

1.23.88.6 Build
...............

   - bpo-29243(1): Prevent unnecessary rebuilding of Python during ‘make
     test’, ‘make install’ and some other make targets when configured
     with ‘--enable-optimizations’.

   - bpo-23404(2): Don't regenerate generated files based on file
     modification time anymore: the action is now explicit.  Replace
     ‘make touch’ with ‘make regen-all’.

   - bpo-29643(3): Fix ‘--enable-optimization’ didn't work.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29243

   (2) https://bugs.python.org/issue?@action=redirect&bpo=23404

   (3) https://bugs.python.org/issue?@action=redirect&bpo=29643


File: python.info,  Node: Windows<65>,  Next: C API<65>,  Prev: Build<75>,  Up: Python 3 5 4 release candidate 1

1.23.88.7 Windows
.................

   - bpo-30687(1): Locate msbuild.exe on Windows when building rather
     than vcvarsall.bat

   - bpo-29392(2): Prevent crash when passing invalid arguments into
     msvcrt module.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=30687

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29392


File: python.info,  Node: C API<65>,  Prev: Windows<65>,  Up: Python 3 5 4 release candidate 1

1.23.88.8 C API
...............

   - bpo-27867(1): Function PySlice_GetIndicesEx() is replaced with a
     macro if Py_LIMITED_API is set to the value between 0x03050400 and
     0x03060000 (not including) or 0x03060100 or higher.

   - bpo-29083(2): Fixed the declaration of some public API functions.
     PyArg_VaParse() and PyArg_VaParseTupleAndKeywords() were not
     available in limited API. PyArg_ValidateKeywordArguments(),
     PyArg_UnpackTuple() and Py_BuildValue() were not available in
     limited API of version < 3.3 when PY_SSIZE_T_CLEAN is defined.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27867

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29083


File: python.info,  Node: Python 3 5 3 final,  Next: Python 3 5 3 release candidate 1,  Prev: Python 3 5 4 release candidate 1,  Up: Changelog（更動日誌）

1.23.89 Python 3.5.3 final
--------------------------

'Release date: 2017-01-17'

There were no code changes between 3.5.3rc1 and 3.5.3 final.


File: python.info,  Node: Python 3 5 3 release candidate 1,  Next: Python 3 5 2 final,  Prev: Python 3 5 3 final,  Up: Changelog（更動日誌）

1.23.90 Python 3.5.3 release candidate 1
----------------------------------------

'Release date: 2017-01-02'

* Menu:

* Security: Security<46>.
* Core and Builtins: Core and Builtins<79>.
* Library: Library<79>.
* IDLE: IDLE<55>.
* C API: C API<66>.
* Documentation: Documentation<66>.
* Tests: Tests<70>.
* Tools/Demos: Tools/Demos<41>.
* Windows: Windows<66>.
* Build: Build<76>.


File: python.info,  Node: Security<46>,  Next: Core and Builtins<79>,  Up: Python 3 5 3 release candidate 1

1.23.90.1 Security
..................

   - bpo-27278(1): Fix os.urandom() implementation using getrandom() on
     Linux.  Truncate size to INT_MAX and loop until we collected enough
     random bytes, instead of casting a directly Py_ssize_t to int.

   - bpo-22636(2): Avoid shell injection problems with
     ctypes.util.find_library().

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27278

   (2) https://bugs.python.org/issue?@action=redirect&bpo=22636


File: python.info,  Node: Core and Builtins<79>,  Next: Library<79>,  Prev: Security<46>,  Up: Python 3 5 3 release candidate 1

1.23.90.2 Core and Builtins
...........................

   - bpo-29073(1): bytearray formatting no longer truncates on first
     null byte.

   - bpo-28932(2): Do not include <sys/random.h> if it does not exist.

   - bpo-28147(3): Fix a memory leak in split-table dictionaries:
     setattr() must not convert combined table into split table.

   - bpo-25677(4): Correct the positioning of the syntax error caret for
     indented blocks.  Based on patch by Michael Layzell.

   - bpo-29000(5): Fixed bytes formatting of octals with zero padding in
     alternate form.

   - bpo-28512(6): Fixed setting the offset attribute of SyntaxError by
     PyErr_SyntaxLocationEx() and PyErr_SyntaxLocationObject().

   - bpo-28991(7): functools.lru_cache() was susceptible to an obscure
     reentrancy bug caused by a monkey-patched len() function.

   - bpo-28648(8): Fixed crash in Py_DecodeLocale() in debug build on
     Mac OS X when decode astral characters.  Patch by Xiang Zhang.

   - bpo-19398(9): Extra slash no longer added to sys.path components in
     case of empty compile-time PYTHONPATH components.

   - bpo-28426(10): Fixed potential crash in PyUnicode_AsDecodedObject()
     in debug build.

   - bpo-23782(11): Fixed possible memory leak in _PyTraceback_Add() and
     exception loss in PyTraceBack_Here().

   - bpo-28379(12): Added sanity checks and tests for
     PyUnicode_CopyCharacters().  Patch by Xiang Zhang.

   - bpo-28376(13): The type of long range iterator is now registered as
     Iterator.  Patch by Oren Milman.

   - bpo-28376(14): The constructor of range_iterator now checks that
     step is not 0.  Patch by Oren Milman.

   - bpo-26906(15): Resolving special methods of uninitialized type now
     causes implicit initialization of the type instead of a fail.

   - bpo-18287(16): PyType_Ready() now checks that tp_name is not NULL.
     Original patch by Niklas Koep.

   - bpo-24098(17): Fixed possible crash when AST is changed in process
     of compiling it.

   - bpo-28350(18): String constants with null character no longer
     interned.

   - bpo-26617(19): Fix crash when GC runs during weakref callbacks.

   - bpo-27942(20): String constants now interned recursively in tuples
     and frozensets.

   - bpo-21578(21): Fixed misleading error message when ImportError
     called with invalid keyword args.

   - bpo-28203(22): Fix incorrect type in error message from
     ‘complex(1.0, {2:3})’.  Patch by Soumya Sharma.

   - bpo-27955(23): Fallback on reading /dev/urandom device when the
     getrandom() syscall fails with EPERM, for example when blocked by
     SECCOMP.

   - bpo-28131(24): Fix a regression in zipimport's compile_source().
     zipimport should use the same optimization level as the
     interpreter.

   - bpo-25221(25): Fix corrupted result from PyLong_FromLong(0) when
     Python is compiled with NSMALLPOSINTS = 0.

   - bpo-25758(26): Prevents zipimport from unnecessarily encoding a
     filename (patch by Eryk Sun)

   - bpo-28189(27): dictitems_contains no longer swallows compare
     errors.  (Patch by Xiang Zhang)

   - bpo-27812(28): Properly clear out a generator's frame's
     backreference to the generator to prevent crashes in frame.clear().

   - bpo-27811(29): Fix a crash when a coroutine that has not been
     awaited is finalized with warnings-as-errors enabled.

   - bpo-27587(30): Fix another issue found by PVS-Studio: Null pointer
     check after use of 'def' in _PyState_AddModule().  Initial patch by
     Christian Heimes.

   - bpo-26020(31): set literal evaluation order did not match
     documented behaviour.

   - bpo-27782(32): Multi-phase extension module import now correctly
     allows the ‘m_methods’ field to be used to add module level
     functions to instances of non-module types returned from
     ‘Py_create_mod’.  Patch by Xiang Zhang.

   - bpo-27936(33): The round() function accepted a second None argument
     for some types but not for others.  Fixed the inconsistency by
     accepting None for all numeric types.

   - bpo-27487(34): Warn if a submodule argument to "python -m" or
     runpy.run_module() is found in sys.modules after parent packages
     are imported, but before the submodule is executed.

   - bpo-27558(35): Fix a SystemError in the implementation of "raise"
     statement.  In a brand new thread, raise a RuntimeError since there
     is no active exception to reraise.  Patch written by Xiang Zhang.

   - bpo-27419(36): Standard __import__() no longer look up "__import__"
     in globals or builtins for importing submodules or "from import".
     Fixed handling an error of non-string package name.

   - bpo-27083(37): Respect the PYTHONCASEOK environment variable under
     Windows.

   - bpo-27514(38): Make having too many statically nested blocks a
     SyntaxError instead of SystemError.

   - bpo-27473(39): Fixed possible integer overflow in bytes and
     bytearray concatenations.  Patch by Xiang Zhang.

   - bpo-27507(40): Add integer overflow check in bytearray.extend().
     Patch by Xiang Zhang.

   - bpo-27581(41): Don't rely on wrapping for overflow check in
     PySequence_Tuple().  Patch by Xiang Zhang.

   - bpo-27443(42): __length_hint__() of bytearray iterators no longer
     return a negative integer for a resized bytearray.

   - bpo-27942(43): Fix memory leak in codeobject.c

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29073

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28932

   (3) https://bugs.python.org/issue?@action=redirect&bpo=28147

   (4) https://bugs.python.org/issue?@action=redirect&bpo=25677

   (5) https://bugs.python.org/issue?@action=redirect&bpo=29000

   (6) https://bugs.python.org/issue?@action=redirect&bpo=28512

   (7) https://bugs.python.org/issue?@action=redirect&bpo=28991

   (8) https://bugs.python.org/issue?@action=redirect&bpo=28648

   (9) https://bugs.python.org/issue?@action=redirect&bpo=19398

   (10) https://bugs.python.org/issue?@action=redirect&bpo=28426

   (11) https://bugs.python.org/issue?@action=redirect&bpo=23782

   (12) https://bugs.python.org/issue?@action=redirect&bpo=28379

   (13) https://bugs.python.org/issue?@action=redirect&bpo=28376

   (14) https://bugs.python.org/issue?@action=redirect&bpo=28376

   (15) https://bugs.python.org/issue?@action=redirect&bpo=26906

   (16) https://bugs.python.org/issue?@action=redirect&bpo=18287

   (17) https://bugs.python.org/issue?@action=redirect&bpo=24098

   (18) https://bugs.python.org/issue?@action=redirect&bpo=28350

   (19) https://bugs.python.org/issue?@action=redirect&bpo=26617

   (20) https://bugs.python.org/issue?@action=redirect&bpo=27942

   (21) https://bugs.python.org/issue?@action=redirect&bpo=21578

   (22) https://bugs.python.org/issue?@action=redirect&bpo=28203

   (23) https://bugs.python.org/issue?@action=redirect&bpo=27955

   (24) https://bugs.python.org/issue?@action=redirect&bpo=28131

   (25) https://bugs.python.org/issue?@action=redirect&bpo=25221

   (26) https://bugs.python.org/issue?@action=redirect&bpo=25758

   (27) https://bugs.python.org/issue?@action=redirect&bpo=28189

   (28) https://bugs.python.org/issue?@action=redirect&bpo=27812

   (29) https://bugs.python.org/issue?@action=redirect&bpo=27811

   (30) https://bugs.python.org/issue?@action=redirect&bpo=27587

   (31) https://bugs.python.org/issue?@action=redirect&bpo=26020

   (32) https://bugs.python.org/issue?@action=redirect&bpo=27782

   (33) https://bugs.python.org/issue?@action=redirect&bpo=27936

   (34) https://bugs.python.org/issue?@action=redirect&bpo=27487

   (35) https://bugs.python.org/issue?@action=redirect&bpo=27558

   (36) https://bugs.python.org/issue?@action=redirect&bpo=27419

   (37) https://bugs.python.org/issue?@action=redirect&bpo=27083

   (38) https://bugs.python.org/issue?@action=redirect&bpo=27514

   (39) https://bugs.python.org/issue?@action=redirect&bpo=27473

   (40) https://bugs.python.org/issue?@action=redirect&bpo=27507

   (41) https://bugs.python.org/issue?@action=redirect&bpo=27581

   (42) https://bugs.python.org/issue?@action=redirect&bpo=27443

   (43) https://bugs.python.org/issue?@action=redirect&bpo=27942


File: python.info,  Node: Library<79>,  Next: IDLE<55>,  Prev: Core and Builtins<79>,  Up: Python 3 5 3 release candidate 1

1.23.90.3 Library
.................

   - bpo-15812(1): inspect.getframeinfo() now correctly shows the first
     line of a context.  Patch by Sam Breese.

   - bpo-29094(2): Offsets in a ZIP file created with extern file object
     and modes "w" and "x" now are relative to the start of the file.

   - bpo-13051(3): Fixed recursion errors in large or resized
     curses.textpad.Textbox.  Based on patch by Tycho Andersen.

   - bpo-29119(4): Fix weakrefs in the pure python version of
     collections.OrderedDict move_to_end() method.  Contributed by Andra
     Bogildea.

   - bpo-9770(5): curses.ascii predicates now work correctly with
     negative integers.

   - bpo-28427(6): old keys should not remove new values from
     WeakValueDictionary when collecting from another thread.

   - bpo-28923(7): Remove editor artifacts from Tix.py.

   - bpo-28871(8): Fixed a crash when deallocate deep ElementTree.

   - bpo-19542(9): Fix bugs in WeakValueDictionary.setdefault() and
     WeakValueDictionary.pop() when a GC collection happens in another
     thread.

   - bpo-20191(10): Fixed a crash in resource.prlimit() when pass a
     sequence that doesn't own its elements as limits.

   - bpo-28779(11): multiprocessing.set_forkserver_preload() would crash
     the forkserver process if a preloaded module instantiated some
     multiprocessing objects such as locks.

   - bpo-28847(12): dbm.dumb now supports reading read-only files and no
     longer writes the index file when it is not changed.

   - bpo-25659(13): In ctypes, prevent a crash calling the from_buffer()
     and from_buffer_copy() methods on abstract classes like Array.

   - bpo-28732(14): Fix crash in os.spawnv() with no elements in args

   - bpo-28485(15): Always raise ValueError for negative
     compileall.compile_dir(workers=...)  parameter, even when
     multithreading is unavailable.

   - bpo-28387(16): Fixed possible crash in _io.TextIOWrapper
     deallocator when the garbage collector is invoked in other thread.
     Based on patch by Sebastian Cufre.

   - bpo-27517(17): LZMA compressor and decompressor no longer raise
     exceptions if given empty data twice.  Patch by Benjamin Fogle.

   - bpo-28549(18): Fixed segfault in curses's addch() with ncurses6.

   - bpo-28449(19): tarfile.open() with mode "r" or "r:" now tries to
     open a tar file with compression before trying to open it without
     compression.  Otherwise it had 50% chance failed with
     ignore_zeros=True.

   - bpo-23262(20): The webbrowser module now supports Firefox 36+ and
     derived browsers.  Based on patch by Oleg Broytman.

   - bpo-27939(21): Fixed bugs in tkinter.ttk.LabeledScale and
     tkinter.Scale caused by representing the scale as float value
     internally in Tk.  tkinter.IntVar now works if float value is set
     to underlying Tk variable.

   - bpo-28255(22): calendar.TextCalendar().prmonth() no longer prints a
     space at the start of new line after printing a month's calendar.
     Patch by Xiang Zhang.

   - bpo-20491(23): The textwrap.TextWrapper class now honors
     non-breaking spaces.  Based on patch by Kaarle Ritvanen.

   - bpo-28353(24): os.fwalk() no longer fails on broken links.

   - bpo-25464(25): Fixed HList.header_exists() in tkinter.tix module by
     addin a workaround to Tix library bug.

   - bpo-28488(26): shutil.make_archive() no longer add entry "./" to
     ZIP archive.

   - bpo-24452(27): Make webbrowser support Chrome on Mac OS X.

   - bpo-20766(28): Fix references leaked by pdb in the handling of
     SIGINT handlers.

   - bpo-26293(29): Fixed writing ZIP files that starts not from the
     start of the file.  Offsets in ZIP file now are relative to the
     start of the archive in conforming to the specification.

   - bpo-28321(30): Fixed writing non-BMP characters with binary format
     in plistlib.

   - bpo-28322(31): Fixed possible crashes when unpickle itertools
     objects from incorrect pickle data.  Based on patch by John Leitch.

   - Fix possible integer overflows and crashes in the mmap module with
     unusual usage patterns.

   - bpo-1703178(32): Fix the ability to pass the -link-objects option
     to the distutils build_ext command.

   - bpo-28253(33): Fixed calendar functions for extreme months: 0001-01
     and 9999-12.  Methods itermonthdays() and itermonthdays2() are
     reimplemented so that they don't call itermonthdates() which can
     cause datetime.date under/overflow.

   - bpo-28275(34): Fixed possible use after free in the decompress()
     methods of the LZMADecompressor and BZ2Decompressor classes.
     Original patch by John Leitch.

   - bpo-27897(35): Fixed possible crash in
     sqlite3.Connection.create_collation() if pass invalid string-like
     object as a name.  Patch by Xiang Zhang.

   - bpo-18893(36): Fix invalid exception handling in
     Lib/ctypes/macholib/dyld.py.  Patch by Madison May.

   - bpo-27611(37): Fixed support of default root window in the
     tkinter.tix module.

   - bpo-27348(38): In the traceback module, restore the formatting of
     exception messages like "Exception: None".  This fixes a regression
     introduced in 3.5a2.

   - bpo-25651(39): Allow false values to be used for msg parameter of
     subTest().

   - bpo-27932(40): Prevent memory leak in win32_ver().

   - Fix UnboundLocalError in socket._sendfile_use_sendfile.

   - bpo-28075(41): Check for ERROR_ACCESS_DENIED in Windows
     implementation of os.stat().  Patch by Eryk Sun.

   - bpo-25270(42): Prevent codecs.escape_encode() from raising
     SystemError when an empty bytestring is passed.

   - bpo-28181(43): Get antigravity over HTTPS. Patch by Kaartic
     Sivaraam.

   - bpo-25895(44): Enable WebSocket URL schemes in
     urllib.parse.urljoin.  Patch by Gergely Imreh and Markus
     Holtermann.

   - bpo-27599(45): Fixed buffer overrun in binascii.b2a_qp() and
     binascii.a2b_qp().

   - bpo-19003(46): m email.generator now replaces only ‘\r’ and/or ‘\n’
     line endings, per the RFC, instead of all unicode line endings.

   - bpo-28019(47): itertools.count() no longer rounds non-integer step
     in range between 1.0 and 2.0 to 1.

   - bpo-25969(48): Update the lib2to3 grammar to handle the unpacking
     generalizations added in 3.5.

   - bpo-14977(49): mailcap now respects the order of the lines in the
     mailcap files ("first match"), as required by RFC 1542.  Patch by
     Michael Lazar.

   - bpo-24594(50): Validates persist parameter when opening MSI
     database

   - bpo-17582(51): xml.etree.ElementTree nows preserves whitespaces in
     attributes (Patch by Duane Griffin.  Reviewed and approved by
     Stefan Behnel.)

   - bpo-28047(52): Fixed calculation of line length used for the base64
     CTE in the new email policies.

   - bpo-27445(53): Don't pass str(_charset) to MIMEText.set_payload().
     Patch by Claude Paroz.

   - bpo-22450(54): urllib now includes an ‘Accept: */*’ header among
     the default headers.  This makes the results of REST API requests
     more consistent and predictable especially when proxy servers are
     involved.

   - lib2to3.pgen3.driver.load_grammar() now creates a stable cache file
     between runs given the same Grammar.txt input regardless of the
     hash randomization setting.

   - bpo-27570(55): Avoid zero-length memcpy() etc calls with null
     source pointers in the "ctypes" and "array" modules.

   - bpo-22233(56): Break email header lines 'only' on the RFC specified
     CR and LF characters, not on arbitrary unicode line breaks.  This
     also fixes a bug in HTTP header parsing.

   - bpo-27988(57): Fix email iter_attachments incorrect mutation of
     payload list.

   - bpo-27691(58): Fix ssl module's parsing of GEN_RID subject
     alternative name fields in X.509 certs.

   - bpo-27850(59): Remove 3DES from ssl module's default cipher list to
     counter measure sweet32 attack (CVE-2016-2183(60)).

   - bpo-27766(61): Add ChaCha20 Poly1305 to ssl module's default cipher
     list.  (Required OpenSSL 1.1.0 or LibreSSL).

   - bpo-26470(62): Port ssl and hashlib module to OpenSSL 1.1.0.

   - Remove support for passing a file descriptor to os.access.  It
     never worked but previously didn't raise.

   - bpo-12885(63): Fix error when distutils encounters symlink.

   - bpo-27881(64): Fixed possible bugs when setting
     sqlite3.Connection.isolation_level.  Based on patch by Xiang Zhang.

   - bpo-27861(65): Fixed a crash in sqlite3.Connection.cursor() when a
     factory creates not a cursor.  Patch by Xiang Zhang.

   - bpo-19884(66): Avoid spurious output on OS X with Gnu Readline.

   - bpo-27706(67): Restore deterministic behavior of
     random.Random().seed() for string seeds using seeding version 1.
     Allows sequences of calls to random() to exactly match those
     obtained in Python 2.  Patch by Nofar Schnider.

   - bpo-10513(68): Fix a regression in Connection.commit().  Statements
     should not be reset after a commit.

   - A new version of typing.py from ‘https://github.com/python/typing’:
     Collection (only for 3.6) (bpo-27598(69)).  Add FrozenSet to
     __all__ (upstream #261).  Fix crash in _get_type_vars() (upstream
     #259).  Remove the dict constraint in ForwardRef._eval_type
     (upstream #252).

   - bpo-27539(70): Fix unnormalised ‘Fraction.__pow__’ result in the
     case of negative exponent and negative base.

   - bpo-21718(71): cursor.description is now available for queries
     using CTEs.

   - bpo-2466(72): posixpath.ismount now correctly recognizes mount
     points which the user does not have permission to access.

   - bpo-27773(73): Correct some memory management errors
     server_hostname in _ssl.wrap_socket().

   - bpo-26750(74): unittest.mock.create_autospec() now works properly
     for subclasses of property() and other data descriptors.

   - In the curses module, raise an error if window.getstr() or
     window.instr() is passed a negative value.

   - bpo-27783(75): Fix possible usage of uninitialized memory in
     operator.methodcaller.

   - bpo-27774(76): Fix possible Py_DECREF on unowned object in _sre.

   - bpo-27760(77): Fix possible integer overflow in binascii.b2a_qp.

   - bpo-27758(78): Fix possible integer overflow in the _csv module for
     large record lengths.

   - bpo-27568(79): Prevent HTTPoxy attack (CVE-2016-1000110(80)).
     Ignore the HTTP_PROXY variable when REQUEST_METHOD environment is
     set, which indicates that the script is in CGI mode.

   - bpo-27656(81): Do not assume sched.h defines any SCHED_* constants.

   - bpo-27130(82): In the "zlib" module, fix handling of large buffers
     (typically 4 GiB) when compressing and decompressing.  Previously,
     inputs were limited to 4 GiB, and compression and decompression
     operations did not properly handle results of 4 GiB.

   - bpo-27533(83): Release GIL in nt._isdir

   - bpo-17711(84): Fixed unpickling by the persistent ID with protocol
     0.  Original patch by Alexandre Vassalotti.

   - bpo-27522(85): Avoid an unintentional reference cycle in
     email.feedparser.

   - bpo-26844(86): Fix error message for imp.find_module() to refer to
     'path' instead of 'name'.  Patch by Lev Maximov.

   - bpo-23804(87): Fix SSL zero-length recv() calls to not block and
     not raise an error about unclean EOF.

   - bpo-27466(88): Change time format returned by
     http.cookie.time2netscape, confirming the netscape cookie format
     and making it consistent with documentation.

   - bpo-26664(89): Fix activate.fish by removing mis-use of ‘$’.

   - bpo-22115(90): Fixed tracing Tkinter variables: trace_vdelete()
     with wrong mode no longer break tracing, trace_vinfo() now always
     returns a list of pairs of strings, tracing in the "u" mode now
     works.

   - Fix a scoping issue in importlib.util.LazyLoader which triggered an
     UnboundLocalError when lazy-loading a module that was already put
     into sys.modules.

   - bpo-27079(91): Fixed curses.ascii functions isblank(), iscntrl()
     and ispunct().

   - bpo-26754(92): Some functions (compile() etc) accepted a filename
     argument encoded as an iterable of integers.  Now only strings and
     byte-like objects are accepted.

   - bpo-27048(93): Prevents distutils failing on Windows when
     environment variables contain non-ASCII characters

   - bpo-27330(94): Fixed possible leaks in the ctypes module.

   - bpo-27238(95): Got rid of bare excepts in the turtle module.
     Original patch by Jelle Zijlstra.

   - bpo-27122(96): When an exception is raised within the context being
     managed by a contextlib.ExitStack() and one of the exit stack
     generators catches and raises it in a chain, do not re-raise the
     original exception when exiting, let the new chained one through.
     This avoids the PEP 479(97) bug described in issue25782.

   - bpo-26386(98): Fixed ttk.TreeView selection operations with item
     id's containing spaces.

   - bpo-16182(99): Fix various functions in the "readline" module to
     use the locale encoding, and fix get_begidx() and get_endidx() to
     return code point indexes.

   - bpo-27392(100): Add loop.connect_accepted_socket().  Patch by Jim
     Fulton.

   - bpo-27930(101): Improved behaviour of
     logging.handlers.QueueListener.  Thanks to Paulo Andrade and Petr
     Viktorin for the analysis and patch.

   - bpo-21201(102): Improves readability of multiprocessing error
     message.  Thanks to Wojciech Walczak for patch.

   - bpo-27456(103): asyncio: Set TCP_NODELAY by default.

   - bpo-27906(104): Fix socket accept exhaustion during high TCP
     traffic.  Patch by Kevin Conway.

   - bpo-28174(105): Handle when SO_REUSEPORT isn't properly supported.
     Patch by Seth Michael Larson.

   - bpo-26654(106): Inspect functools.partial in
     asyncio.Handle.__repr__.  Patch by iceboy.

   - bpo-26909(107): Fix slow pipes IO in asyncio.  Patch by INADA
     Naoki.

   - bpo-28176(108): Fix callbacks race in
     asyncio.SelectorLoop.sock_connect.

   - bpo-27759(109): Fix selectors incorrectly retain invalid file
     descriptors.  Patch by Mark Williams.

   - bpo-28368(110): Refuse monitoring processes if the child watcher
     has no loop attached.  Patch by Vincent Michel.

   - bpo-28369(111): Raise RuntimeError when transport's FD is used with
     add_reader, add_writer, etc.

   - bpo-28370(112): Speedup asyncio.StreamReader.readexactly.  Patch by
     Коренберг Марк.

   - bpo-28371(113): Deprecate passing asyncio.Handles to
     run_in_executor.

   - bpo-28372(114): Fix asyncio to support formatting of non-python
     coroutines.

   - bpo-28399(115): Remove UNIX socket from FS before binding.  Patch
     by Коренберг Марк.

   - bpo-27972(116): Prohibit Tasks to await on themselves.

   - bpo-26923(117): Fix asyncio.Gather to refuse being cancelled once
     all children are done.  Patch by Johannes Ebke.

   - bpo-26796(118): Don't configure the number of workers for default
     threadpool executor.  Initial patch by Hans Lawrenz.

   - bpo-28600(119): Optimize loop.call_soon().

   - bpo-28613(120): Fix get_event_loop() return the current loop if
     called from coroutines/callbacks.

   - bpo-28639(121): Fix inspect.isawaitable to always return bool Patch
     by Justin Mayfield.

   - bpo-28652(122): Make loop methods reject socket kinds they do not
     support.

   - bpo-28653(123): Fix a refleak in functools.lru_cache.

   - bpo-28703(124): Fix asyncio.iscoroutinefunction to handle Mock
     objects.

   - bpo-24142(125): Reading a corrupt config file left the parser in an
     invalid state.  Original patch by Florian Höch.

   - bpo-28990(126): Fix SSL hanging if connection is closed before
     handshake completed.  (Patch by HoHo-Ho)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=15812

   (2) https://bugs.python.org/issue?@action=redirect&bpo=29094

   (3) https://bugs.python.org/issue?@action=redirect&bpo=13051

   (4) https://bugs.python.org/issue?@action=redirect&bpo=29119

   (5) https://bugs.python.org/issue?@action=redirect&bpo=9770

   (6) https://bugs.python.org/issue?@action=redirect&bpo=28427

   (7) https://bugs.python.org/issue?@action=redirect&bpo=28923

   (8) https://bugs.python.org/issue?@action=redirect&bpo=28871

   (9) https://bugs.python.org/issue?@action=redirect&bpo=19542

   (10) https://bugs.python.org/issue?@action=redirect&bpo=20191

   (11) https://bugs.python.org/issue?@action=redirect&bpo=28779

   (12) https://bugs.python.org/issue?@action=redirect&bpo=28847

   (13) https://bugs.python.org/issue?@action=redirect&bpo=25659

   (14) https://bugs.python.org/issue?@action=redirect&bpo=28732

   (15) https://bugs.python.org/issue?@action=redirect&bpo=28485

   (16) https://bugs.python.org/issue?@action=redirect&bpo=28387

   (17) https://bugs.python.org/issue?@action=redirect&bpo=27517

   (18) https://bugs.python.org/issue?@action=redirect&bpo=28549

   (19) https://bugs.python.org/issue?@action=redirect&bpo=28449

   (20) https://bugs.python.org/issue?@action=redirect&bpo=23262

   (21) https://bugs.python.org/issue?@action=redirect&bpo=27939

   (22) https://bugs.python.org/issue?@action=redirect&bpo=28255

   (23) https://bugs.python.org/issue?@action=redirect&bpo=20491

   (24) https://bugs.python.org/issue?@action=redirect&bpo=28353

   (25) https://bugs.python.org/issue?@action=redirect&bpo=25464

   (26) https://bugs.python.org/issue?@action=redirect&bpo=28488

   (27) https://bugs.python.org/issue?@action=redirect&bpo=24452

   (28) https://bugs.python.org/issue?@action=redirect&bpo=20766

   (29) https://bugs.python.org/issue?@action=redirect&bpo=26293

   (30) https://bugs.python.org/issue?@action=redirect&bpo=28321

   (31) https://bugs.python.org/issue?@action=redirect&bpo=28322

   (32) https://bugs.python.org/issue?@action=redirect&bpo=1703178

   (33) https://bugs.python.org/issue?@action=redirect&bpo=28253

   (34) https://bugs.python.org/issue?@action=redirect&bpo=28275

   (35) https://bugs.python.org/issue?@action=redirect&bpo=27897

   (36) https://bugs.python.org/issue?@action=redirect&bpo=18893

   (37) https://bugs.python.org/issue?@action=redirect&bpo=27611

   (38) https://bugs.python.org/issue?@action=redirect&bpo=27348

   (39) https://bugs.python.org/issue?@action=redirect&bpo=25651

   (40) https://bugs.python.org/issue?@action=redirect&bpo=27932

   (41) https://bugs.python.org/issue?@action=redirect&bpo=28075

   (42) https://bugs.python.org/issue?@action=redirect&bpo=25270

   (43) https://bugs.python.org/issue?@action=redirect&bpo=28181

   (44) https://bugs.python.org/issue?@action=redirect&bpo=25895

   (45) https://bugs.python.org/issue?@action=redirect&bpo=27599

   (46) https://bugs.python.org/issue?@action=redirect&bpo=19003

   (47) https://bugs.python.org/issue?@action=redirect&bpo=28019

   (48) https://bugs.python.org/issue?@action=redirect&bpo=25969

   (49) https://bugs.python.org/issue?@action=redirect&bpo=14977

   (50) https://bugs.python.org/issue?@action=redirect&bpo=24594

   (51) https://bugs.python.org/issue?@action=redirect&bpo=17582

   (52) https://bugs.python.org/issue?@action=redirect&bpo=28047

   (53) https://bugs.python.org/issue?@action=redirect&bpo=27445

   (54) https://bugs.python.org/issue?@action=redirect&bpo=22450

   (55) https://bugs.python.org/issue?@action=redirect&bpo=27570

   (56) https://bugs.python.org/issue?@action=redirect&bpo=22233

   (57) https://bugs.python.org/issue?@action=redirect&bpo=27988

   (58) https://bugs.python.org/issue?@action=redirect&bpo=27691

   (59) https://bugs.python.org/issue?@action=redirect&bpo=27850

   (60) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2183

   (61) https://bugs.python.org/issue?@action=redirect&bpo=27766

   (62) https://bugs.python.org/issue?@action=redirect&bpo=26470

   (63) https://bugs.python.org/issue?@action=redirect&bpo=12885

   (64) https://bugs.python.org/issue?@action=redirect&bpo=27881

   (65) https://bugs.python.org/issue?@action=redirect&bpo=27861

   (66) https://bugs.python.org/issue?@action=redirect&bpo=19884

   (67) https://bugs.python.org/issue?@action=redirect&bpo=27706

   (68) https://bugs.python.org/issue?@action=redirect&bpo=10513

   (69) https://bugs.python.org/issue?@action=redirect&bpo=27598

   (70) https://bugs.python.org/issue?@action=redirect&bpo=27539

   (71) https://bugs.python.org/issue?@action=redirect&bpo=21718

   (72) https://bugs.python.org/issue?@action=redirect&bpo=2466

   (73) https://bugs.python.org/issue?@action=redirect&bpo=27773

   (74) https://bugs.python.org/issue?@action=redirect&bpo=26750

   (75) https://bugs.python.org/issue?@action=redirect&bpo=27783

   (76) https://bugs.python.org/issue?@action=redirect&bpo=27774

   (77) https://bugs.python.org/issue?@action=redirect&bpo=27760

   (78) https://bugs.python.org/issue?@action=redirect&bpo=27758

   (79) https://bugs.python.org/issue?@action=redirect&bpo=27568

   (80) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000110

   (81) https://bugs.python.org/issue?@action=redirect&bpo=27656

   (82) https://bugs.python.org/issue?@action=redirect&bpo=27130

   (83) https://bugs.python.org/issue?@action=redirect&bpo=27533

   (84) https://bugs.python.org/issue?@action=redirect&bpo=17711

   (85) https://bugs.python.org/issue?@action=redirect&bpo=27522

   (86) https://bugs.python.org/issue?@action=redirect&bpo=26844

   (87) https://bugs.python.org/issue?@action=redirect&bpo=23804

   (88) https://bugs.python.org/issue?@action=redirect&bpo=27466

   (89) https://bugs.python.org/issue?@action=redirect&bpo=26664

   (90) https://bugs.python.org/issue?@action=redirect&bpo=22115

   (91) https://bugs.python.org/issue?@action=redirect&bpo=27079

   (92) https://bugs.python.org/issue?@action=redirect&bpo=26754

   (93) https://bugs.python.org/issue?@action=redirect&bpo=27048

   (94) https://bugs.python.org/issue?@action=redirect&bpo=27330

   (95) https://bugs.python.org/issue?@action=redirect&bpo=27238

   (96) https://bugs.python.org/issue?@action=redirect&bpo=27122

   (97) https://peps.python.org/pep-0479/

   (98) https://bugs.python.org/issue?@action=redirect&bpo=26386

   (99) https://bugs.python.org/issue?@action=redirect&bpo=16182

   (100) https://bugs.python.org/issue?@action=redirect&bpo=27392

   (101) https://bugs.python.org/issue?@action=redirect&bpo=27930

   (102) https://bugs.python.org/issue?@action=redirect&bpo=21201

   (103) https://bugs.python.org/issue?@action=redirect&bpo=27456

   (104) https://bugs.python.org/issue?@action=redirect&bpo=27906

   (105) https://bugs.python.org/issue?@action=redirect&bpo=28174

   (106) https://bugs.python.org/issue?@action=redirect&bpo=26654

   (107) https://bugs.python.org/issue?@action=redirect&bpo=26909

   (108) https://bugs.python.org/issue?@action=redirect&bpo=28176

   (109) https://bugs.python.org/issue?@action=redirect&bpo=27759

   (110) https://bugs.python.org/issue?@action=redirect&bpo=28368

   (111) https://bugs.python.org/issue?@action=redirect&bpo=28369

   (112) https://bugs.python.org/issue?@action=redirect&bpo=28370

   (113) https://bugs.python.org/issue?@action=redirect&bpo=28371

   (114) https://bugs.python.org/issue?@action=redirect&bpo=28372

   (115) https://bugs.python.org/issue?@action=redirect&bpo=28399

   (116) https://bugs.python.org/issue?@action=redirect&bpo=27972

   (117) https://bugs.python.org/issue?@action=redirect&bpo=26923

   (118) https://bugs.python.org/issue?@action=redirect&bpo=26796

   (119) https://bugs.python.org/issue?@action=redirect&bpo=28600

   (120) https://bugs.python.org/issue?@action=redirect&bpo=28613

   (121) https://bugs.python.org/issue?@action=redirect&bpo=28639

   (122) https://bugs.python.org/issue?@action=redirect&bpo=28652

   (123) https://bugs.python.org/issue?@action=redirect&bpo=28653

   (124) https://bugs.python.org/issue?@action=redirect&bpo=28703

   (125) https://bugs.python.org/issue?@action=redirect&bpo=24142

   (126) https://bugs.python.org/issue?@action=redirect&bpo=28990


File: python.info,  Node: IDLE<55>,  Next: C API<66>,  Prev: Library<79>,  Up: Python 3 5 3 release candidate 1

1.23.90.4 IDLE
..............

   - bpo-15308(1): Add 'interrupt execution' (^C) to Shell menu.  Patch
     by Roger Serwy, updated by Bayard Randel.

   - bpo-27922(2): Stop IDLE tests from 'flashing' gui widgets on the
     screen.

   - Add version to title of IDLE help window.

   - bpo-25564(3): In section on IDLE - console differences, mention
     that using exec means that __builtins__ is defined for each
     statement.

   - bpo-27714(4): text_textview and test_autocomplete now pass when
     re-run in the same process.  This occurs when test_idle fails when
     run with the -w option but without -jn.  Fix warning from
     test_config.

   - bpo-25507(5): IDLE no longer runs buggy code because of its tkinter
     imports.  Users must include the same imports required to run
     directly in Python.

   - bpo-27452(6): add line counter and crc to IDLE configHandler test
     dump.

   - bpo-27365(7): Allow non-ascii chars in IDLE NEWS.txt, for
     contributor names.

   - bpo-27245(8): IDLE: Cleanly delete custom themes and key bindings.
     Previously, when IDLE was started from a console or by import, a
     cascade of warnings was emitted.  Patch by Serhiy Storchaka.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=15308

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27922

   (3) https://bugs.python.org/issue?@action=redirect&bpo=25564

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27714

   (5) https://bugs.python.org/issue?@action=redirect&bpo=25507

   (6) https://bugs.python.org/issue?@action=redirect&bpo=27452

   (7) https://bugs.python.org/issue?@action=redirect&bpo=27365

   (8) https://bugs.python.org/issue?@action=redirect&bpo=27245


File: python.info,  Node: C API<66>,  Next: Documentation<66>,  Prev: IDLE<55>,  Up: Python 3 5 3 release candidate 1

1.23.90.5 C API
...............

   - bpo-28808(1): PyUnicode_CompareWithASCIIString() now never raises
     exceptions.

   - bpo-26754(2): PyUnicode_FSDecoder() accepted a filename argument
     encoded as an iterable of integers.  Now only strings and
     bytes-like objects are accepted.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28808

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26754


File: python.info,  Node: Documentation<66>,  Next: Tests<70>,  Prev: C API<66>,  Up: Python 3 5 3 release candidate 1

1.23.90.6 Documentation
.......................

   - bpo-28513(1): Documented command-line interface of zipfile.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28513


File: python.info,  Node: Tests<70>,  Next: Tools/Demos<41>,  Prev: Documentation<66>,  Up: Python 3 5 3 release candidate 1

1.23.90.7 Tests
...............

   - bpo-28950(1): Disallow -j0 to be combined with -T/-l/-M in regrtest
     command line arguments.

   - bpo-28666(2): Now test.support.rmtree is able to remove unwritable
     or unreadable directories.

   - bpo-23839(3): Various caches now are cleared before running every
     test file.

   - bpo-28409(4): regrtest: fix the parser of command line arguments.

   - bpo-27787(5): Call gc.collect() before checking each test for
     "dangling threads", since the dangling threads are weak references.

   - bpo-27369(6): In test_pyexpat, avoid testing an error message
     detail that changed in Expat 2.2.0.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28950

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28666

   (3) https://bugs.python.org/issue?@action=redirect&bpo=23839

   (4) https://bugs.python.org/issue?@action=redirect&bpo=28409

   (5) https://bugs.python.org/issue?@action=redirect&bpo=27787

   (6) https://bugs.python.org/issue?@action=redirect&bpo=27369


File: python.info,  Node: Tools/Demos<41>,  Next: Windows<66>,  Prev: Tests<70>,  Up: Python 3 5 3 release candidate 1

1.23.90.8 Tools/Demos
.....................

   - bpo-27952(1): Get Tools/scripts/fixcid.py working with Python 3 and
     the current "re" module, avoid invalid Python backslash escapes,
     and fix a bug parsing escaped C quote signs.

   - bpo-27332(2): Fixed the type of the first argument of module-level
     functions generated by Argument Clinic.  Patch by Petr Viktorin.

   - bpo-27418(3): Fixed Tools/importbench/importbench.py.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27952

   (2) https://bugs.python.org/issue?@action=redirect&bpo=27332

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27418


File: python.info,  Node: Windows<66>,  Next: Build<76>,  Prev: Tools/Demos<41>,  Up: Python 3 5 3 release candidate 1

1.23.90.9 Windows
.................

   - bpo-28251(1): Improvements to help manuals on Windows.

   - bpo-28110(2): launcher.msi has different product codes between
     32-bit and 64-bit

   - bpo-25144(3): Ensures TargetDir is set before continuing with
     custom install.

   - bpo-27469(4): Adds a shell extension to the launcher so that drag
     and drop works correctly.

   - bpo-27309(5): Enabled proper Windows styles in python[w].exe
     manifest.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28251

   (2) https://bugs.python.org/issue?@action=redirect&bpo=28110

   (3) https://bugs.python.org/issue?@action=redirect&bpo=25144

   (4) https://bugs.python.org/issue?@action=redirect&bpo=27469

   (5) https://bugs.python.org/issue?@action=redirect&bpo=27309


File: python.info,  Node: Build<76>,  Prev: Windows<66>,  Up: Python 3 5 3 release candidate 1

1.23.90.10 Build
................

   - bpo-29080(1): Removes hard dependency on hg.exe from
     PCBuild/build.bat

   - bpo-23903(2): Added missed names to PC/python3.def.

   - bpo-10656(3): Fix out-of-tree building on AIX. Patch by Tristan
     Carel and Michael Haubenwallner.

   - bpo-26359(4): Rename -with-optimiations to -enable-optimizations.

   - bpo-28444(5): Fix missing extensions modules when cross compiling.

   - bpo-28248(6): Update Windows build and OS X installers to use
     OpenSSL 1.0.2j.

   - bpo-28258(7): Fixed build with Estonian locale (python-config and
     distclean targets in Makefile).  Patch by Arfrever Frehtes
     Taifersar Arahesis.

   - bpo-26661(8): setup.py now detects system libffi with multiarch
     wrapper.

   - bpo-28066(9): Fix the logic that searches build directories for
     generated include files when building outside the source tree.

   - bpo-15819(10): Remove redundant include search directory option for
     building outside the source tree.

   - bpo-27566(11): Fix clean target in freeze makefile (patch by Lisa
     Roach)

   - bpo-27705(12): Update message in validate_ucrtbase.py

   - bpo-27983(13): Cause lack of llvm-profdata tool when using clang as
     required for PGO linking to be a configure time error rather than
     make time when -with-optimizations is enabled.  Also improve our
     ability to find the llvm-profdata tool on MacOS and some Linuxes.

   - bpo-26307(14): The profile-opt build now applies PGO to the
     built-in modules.

   - bpo-26359(15): Add the -with-optimizations configure flag.

   - bpo-27713(16): Suppress spurious build warnings when updating
     importlib's bootstrap files.  Patch by Xiang Zhang

   - bpo-25825(17): Correct the references to Modules/python.exp and
     ld_so_aix, which are required on AIX. This updates references to an
     installation path that was changed in 3.2a4, and undoes changed
     references to the build tree that were made in 3.5.0a1.

   - bpo-27453(18): CPP invocation in configure must use CPPFLAGS. Patch
     by Chi Hsuan Yen.

   - bpo-27641(19): The configure script now inserts comments into the
     makefile to prevent the pgen and _freeze_importlib executables from
     being cross-compiled.

   - bpo-26662(20): Set PYTHON_FOR_GEN in configure as the Python
     program to be used for file generation during the build.

   - bpo-10910(21): Avoid C++ compilation errors on FreeBSD and OS X.
     Also update FreedBSD version checks for the original ctype UTF-8
     workaround.

   - bpo-28676(22): Prevent missing 'getentropy' declaration warning on
     macOS. Patch by Gareth Rees.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=29080

   (2) https://bugs.python.org/issue?@action=redirect&bpo=23903

   (3) https://bugs.python.org/issue?@action=redirect&bpo=10656

   (4) https://bugs.python.org/issue?@action=redirect&bpo=26359

   (5) https://bugs.python.org/issue?@action=redirect&bpo=28444

   (6) https://bugs.python.org/issue?@action=redirect&bpo=28248

   (7) https://bugs.python.org/issue?@action=redirect&bpo=28258

   (8) https://bugs.python.org/issue?@action=redirect&bpo=26661

   (9) https://bugs.python.org/issue?@action=redirect&bpo=28066

   (10) https://bugs.python.org/issue?@action=redirect&bpo=15819

   (11) https://bugs.python.org/issue?@action=redirect&bpo=27566

   (12) https://bugs.python.org/issue?@action=redirect&bpo=27705

   (13) https://bugs.python.org/issue?@action=redirect&bpo=27983

   (14) https://bugs.python.org/issue?@action=redirect&bpo=26307

   (15) https://bugs.python.org/issue?@action=redirect&bpo=26359

   (16) https://bugs.python.org/issue?@action=redirect&bpo=27713

   (17) https://bugs.python.org/issue?@action=redirect&bpo=25825

   (18) https://bugs.python.org/issue?@action=redirect&bpo=27453

   (19) https://bugs.python.org/issue?@action=redirect&bpo=27641

   (20) https://bugs.python.org/issue?@action=redirect&bpo=26662

   (21) https://bugs.python.org/issue?@action=redirect&bpo=10910

   (22) https://bugs.python.org/issue?@action=redirect&bpo=28676


File: python.info,  Node: Python 3 5 2 final,  Next: Python 3 5 2 release candidate 1,  Prev: Python 3 5 3 release candidate 1,  Up: Changelog（更動日誌）

1.23.91 Python 3.5.2 final
--------------------------

'Release date: 2016-06-26'

* Menu:

* Core and Builtins: Core and Builtins<80>.
* Tests: Tests<71>.
* IDLE: IDLE<56>.


File: python.info,  Node: Core and Builtins<80>,  Next: Tests<71>,  Up: Python 3 5 2 final

1.23.91.1 Core and Builtins
...........................

   - bpo-26930(1): Update Windows builds to use OpenSSL 1.0.2h.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26930


File: python.info,  Node: Tests<71>,  Next: IDLE<56>,  Prev: Core and Builtins<80>,  Up: Python 3 5 2 final

1.23.91.2 Tests
...............

   - bpo-26867(1): Ubuntu's openssl OP_NO_SSLv3 is forced on by default;
     fix test.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26867


File: python.info,  Node: IDLE<56>,  Prev: Tests<71>,  Up: Python 3 5 2 final

1.23.91.3 IDLE
..............

   - bpo-27365(1): Allow non-ascii in idlelib/NEWS.txt - minimal part
     for 3.5.2.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27365


File: python.info,  Node: Python 3 5 2 release candidate 1,  Next: Python 3 5 1 final,  Prev: Python 3 5 2 final,  Up: Changelog（更動日誌）

1.23.92 Python 3.5.2 release candidate 1
----------------------------------------

'Release date: 2016-06-12'

* Menu:

* Security: Security<47>.
* Core and Builtins: Core and Builtins<81>.
* Library: Library<80>.
* IDLE: IDLE<57>.
* Documentation: Documentation<67>.
* Tests: Tests<72>.
* Build: Build<77>.
* Windows: Windows<67>.
* Tools/Demos: Tools/Demos<42>.


File: python.info,  Node: Security<47>,  Next: Core and Builtins<81>,  Up: Python 3 5 2 release candidate 1

1.23.92.1 Security
..................

   - bpo-26556(1): Update expat to 2.1.1, fixes CVE-2015-1283(2).

   - Fix TLS stripping vulnerability in smtplib, CVE-2016-0772(3).
     Reported by Team Oststrom.

   - bpo-26839(4): On Linux, *note os.urandom(): 4c7. now calls
     ‘getrandom()’ with ‘GRND_NONBLOCK’ to fall back on reading
     ‘/dev/urandom’ if the urandom entropy pool is not initialized yet.
     Patch written by Colm Buckley.

   - bpo-26657(5): Fix directory traversal vulnerability with
     http.server on Windows.  This fixes a regression that was
     introduced in 3.3.4rc1 and 3.4.0rc1.  Based on patch by Philipp
     Hagemeister.

   - bpo-26313(6): ssl.py _load_windows_store_certs fails if windows
     cert store is empty.  Patch by Baji.

   - bpo-25939(7): On Windows open the cert store readonly in
     ssl.enum_certificates.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26556

   (2) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1283

   (3) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0772

   (4) https://bugs.python.org/issue?@action=redirect&bpo=26839

   (5) https://bugs.python.org/issue?@action=redirect&bpo=26657

   (6) https://bugs.python.org/issue?@action=redirect&bpo=26313

   (7) https://bugs.python.org/issue?@action=redirect&bpo=25939


File: python.info,  Node: Core and Builtins<81>,  Next: Library<80>,  Prev: Security<47>,  Up: Python 3 5 2 release candidate 1

1.23.92.2 Core and Builtins
...........................

   - bpo-27066(1): Fixed SystemError if a custom opener (for open())
     returns a negative number without setting an exception.

   - bpo-20041(2): Fixed TypeError when frame.f_trace is set to None.
     Patch by Xavier de Gaye.

   - bpo-26168(3): Fixed possible refleaks in failing Py_BuildValue()
     with the "N" format unit.

   - bpo-26991(4): Fix possible refleak when creating a function with
     annotations.

   - bpo-27039(5): Fixed bytearray.remove() for values greater than 127.
     Patch by Joe Jevnik.

   - bpo-23640(6): int.from_bytes() no longer bypasses constructors for
     subclasses.

   - bpo-26811(7): gc.get_objects() no longer contains a broken tuple
     with NULL pointer.

   - bpo-20120(8): Use RawConfigParser for .pypirc parsing, removing
     support for interpolation unintentionally added with move to Python
     3.  Behavior no longer does any interpolation in .pypirc files,
     matching behavior in Python 2.7 and Setuptools 19.0.

   - bpo-26659(9): Make the builtin slice type support cycle collection.

   - bpo-26718(10): super.__init__ no longer leaks memory if called
     multiple times.  NOTE: A direct call of super.__init__ is not
     endorsed!

   - bpo-25339(11): PYTHONIOENCODING now has priority over locale in
     setting the error handler for stdin and stdout.

   - bpo-26494(12): Fixed crash on iterating exhausting iterators.
     Affected classes are generic sequence iterators, iterators of str,
     bytes, bytearray, list, tuple, set, frozenset, dict, OrderedDict,
     corresponding views and os.scandir() iterator.

   - bpo-26581(13): If coding cookie is specified multiple times on a
     line in Python source code file, only the first one is taken to
     account.

   - bpo-26464(14): Fix str.translate() when string is ASCII and first
     replacements removes character, but next replacement uses a
     non-ASCII character or a string longer than 1 character.
     Regression introduced in Python 3.5.0.

   - bpo-22836(15): Ensure exception reports from PyErr_Display() and
     PyErr_WriteUnraisable() are sensible even when formatting them
     produces secondary errors.  This affects the reports produced by
     sys.__excepthook__() and when __del__() raises an exception.

   - bpo-26302(16): Correct behavior to reject comma as a legal
     character for cookie names.

   - bpo-4806(17): Avoid masking the original TypeError exception when
     using star (‘*’) unpacking in function calls.  Based on patch by
     Hagen Fürstenau and Daniel Urban.

   - bpo-27138(18): Fix the doc comment for FileFinder.find_spec().

   - bpo-26154(19): Add a new private _PyThreadState_UncheckedGet()
     function to get the current Python thread state, but don't issue a
     fatal error if it is NULL. This new function must be used instead
     of accessing directly the _PyThreadState_Current variable.  The
     variable is no more exposed since Python 3.5.1 to hide the exact
     implementation of atomic C types, to avoid compiler issues.

   - bpo-26194(20): Deque.insert() gave odd results for bounded deques
     that had reached their maximum size.  Now an IndexError will be
     raised when attempting to insert into a full deque.

   - bpo-25843(21): When compiling code, don't merge constants if they
     are equal but have a different types.  For example, ‘f1, f2 =
     lambda: 1, lambda: 1.0’ is now correctly compiled to two different
     functions: ‘f1()’ returns ‘1’ (‘int’) and ‘f2()’ returns ‘1.0’
     (‘int’), even if ‘1’ and ‘1.0’ are equal.

   - bpo-22995(22): [UPDATE] Comment out the one of the pickleability
     tests in _PyObject_GetState() due to regressions observed in
     Cython-based projects.

   - bpo-25961(23): Disallowed null characters in the type name.

   - bpo-25973(24): Fix segfault when an invalid nonlocal statement
     binds a name starting with two underscores.

   - bpo-22995(25): Instances of extension types with a state that
     aren't subclasses of list or dict and haven't implemented any
     pickle-related methods (__reduce__, __reduce_ex__, __getnewargs__,
     __getnewargs_ex__, or __getstate__), can no longer be pickled.
     Including memoryview.

   - bpo-20440(26): Massive replacing unsafe attribute setting code with
     special macro Py_SETREF.

   - bpo-25766(27): Special method __bytes__() now works in str
     subclasses.

   - bpo-25421(28): __sizeof__ methods of builtin types now use dynamic
     basic size.  This allows sys.getsize() to work correctly with their
     subclasses with __slots__ defined.

   - bpo-25709(29): Fixed problem with in-place string concatenation and
     utf-8 cache.

   - bpo-27147(30): Mention PEP 420(31) in the importlib docs.

   - bpo-24097(32): Fixed crash in object.__reduce__() if slot name is
     freed inside __getattr__.

   - bpo-24731(33): Fixed crash on converting objects with special
     methods __bytes__, __trunc__, and __float__ returning instances of
     subclasses of bytes, int, and float to subclasses of bytes, int,
     and float correspondingly.

   - bpo-26478(34): Fix semantic bugs when using binary operators with
     dictionary views and tuples.

   - bpo-26171(35): Fix possible integer overflow and heap corruption in
     zipimporter.get_data().

   - bpo-25660(36): Fix TAB key behaviour in REPL with readline.

   - bpo-25887(37): Raise a RuntimeError when a coroutine object is
     awaited more than once.

   - bpo-27243(38): Update the __aiter__ protocol: instead of returning
     an awaitable that resolves to an asynchronous iterator, the
     asynchronous iterator should be returned directly.  Doing the
     former will trigger a PendingDeprecationWarning.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27066

   (2) https://bugs.python.org/issue?@action=redirect&bpo=20041

   (3) https://bugs.python.org/issue?@action=redirect&bpo=26168

   (4) https://bugs.python.org/issue?@action=redirect&bpo=26991

   (5) https://bugs.python.org/issue?@action=redirect&bpo=27039

   (6) https://bugs.python.org/issue?@action=redirect&bpo=23640

   (7) https://bugs.python.org/issue?@action=redirect&bpo=26811

   (8) https://bugs.python.org/issue?@action=redirect&bpo=20120

   (9) https://bugs.python.org/issue?@action=redirect&bpo=26659

   (10) https://bugs.python.org/issue?@action=redirect&bpo=26718

   (11) https://bugs.python.org/issue?@action=redirect&bpo=25339

   (12) https://bugs.python.org/issue?@action=redirect&bpo=26494

   (13) https://bugs.python.org/issue?@action=redirect&bpo=26581

   (14) https://bugs.python.org/issue?@action=redirect&bpo=26464

   (15) https://bugs.python.org/issue?@action=redirect&bpo=22836

   (16) https://bugs.python.org/issue?@action=redirect&bpo=26302

   (17) https://bugs.python.org/issue?@action=redirect&bpo=4806

   (18) https://bugs.python.org/issue?@action=redirect&bpo=27138

   (19) https://bugs.python.org/issue?@action=redirect&bpo=26154

   (20) https://bugs.python.org/issue?@action=redirect&bpo=26194

   (21) https://bugs.python.org/issue?@action=redirect&bpo=25843

   (22) https://bugs.python.org/issue?@action=redirect&bpo=22995

   (23) https://bugs.python.org/issue?@action=redirect&bpo=25961

   (24) https://bugs.python.org/issue?@action=redirect&bpo=25973

   (25) https://bugs.python.org/issue?@action=redirect&bpo=22995

   (26) https://bugs.python.org/issue?@action=redirect&bpo=20440

   (27) https://bugs.python.org/issue?@action=redirect&bpo=25766

   (28) https://bugs.python.org/issue?@action=redirect&bpo=25421

   (29) https://bugs.python.org/issue?@action=redirect&bpo=25709

   (30) https://bugs.python.org/issue?@action=redirect&bpo=27147

   (31) https://peps.python.org/pep-0420/

   (32) https://bugs.python.org/issue?@action=redirect&bpo=24097

   (33) https://bugs.python.org/issue?@action=redirect&bpo=24731

   (34) https://bugs.python.org/issue?@action=redirect&bpo=26478

   (35) https://bugs.python.org/issue?@action=redirect&bpo=26171

   (36) https://bugs.python.org/issue?@action=redirect&bpo=25660

   (37) https://bugs.python.org/issue?@action=redirect&bpo=25887

   (38) https://bugs.python.org/issue?@action=redirect&bpo=27243


File: python.info,  Node: Library<80>,  Next: IDLE<57>,  Prev: Core and Builtins<81>,  Up: Python 3 5 2 release candidate 1

1.23.92.3 Library
.................

   - bpo-21386(1): Implement missing IPv4Address.is_global property.  It
     was documented since 07a5610bae9d.  Initial patch by Roger Luethi.

   - bpo-20900(2): distutils register command now decodes HTTP responses
     correctly.  Initial patch by ingrid.

   - A new version of typing.py provides several new classes and
     features: @overload outside stubs, Reversible, DefaultDict, Text,
     ContextManager, Type[], NewType(), TYPE_CHECKING, and numerous bug
     fixes (note that some of the new features are not yet implemented
     in mypy or other static analyzers).  Also classes for PEP 492(3)
     (Awaitable, AsyncIterable, AsyncIterator) have been added (in fact
     they made it into 3.5.1 but were never mentioned).

   - bpo-25738(4): Stop http.server.BaseHTTPRequestHandler.send_error()
     from sending a message body for 205 Reset Content.  Also, don't
     send Content header fields in responses that don't have a body.
     Patch by Susumu Koshiba.

   - bpo-21313(5): Fix the "platform" module to tolerate when
     sys.version contains truncated build information.

   - bpo-27164(6): In the zlib module, allow decompressing raw Deflate
     streams with a predefined zdict.  Based on patch by Xiang Zhang.

   - bpo-24291(7): Fix wsgiref.simple_server.WSGIRequestHandler to
     completely write data to the client.  Previously it could do
     partial writes and truncate data.  Also,
     wsgiref.handler.ServerHandler can now handle stdout doing partial
     writes, but this is deprecated.

   - bpo-26809(8): Add ‘__all__’ to *note string: be.  Patch by Emanuel
     Barry.

   - bpo-26373(9): subprocess.Popen.communicate now correctly ignores
     BrokenPipeError when the child process dies before .communicate()
     is called in more/all circumstances.

   - bpo-21776(10): distutils.upload now correctly handles HTTPError.
     Initial patch by Claudiu Popa.

   - bpo-27114(11): Fix SSLContext._load_windows_store_certs fails with
     PermissionError

   - bpo-18383(12): Avoid creating duplicate filters when using
     filterwarnings and simplefilter.  Based on patch by Alex Shkop.

   - bpo-27057(13): Fix os.set_inheritable() on Android, ioctl() is
     blocked by SELinux and fails with EACCESS. The function now falls
     back to fcntl().  Patch written by Michał Bednarski.

   - bpo-27014(14): Fix infinite recursion using typing.py.  Thanks to
     Kalle Tuure!

   - bpo-14132(15): Fix urllib.request redirect handling when the target
     only has a query string.  Original fix by Ján Janech.

   - bpo-17214(16): The "urllib.request" module now percent-encodes
     non-ASCII bytes found in redirect target URLs.  Some servers send
     Location header fields with non-ASCII bytes, but "http.client"
     requires the request target to be ASCII-encodable, otherwise a
     UnicodeEncodeError is raised.  Based on patch by Christian Heimes.

   - bpo-26892(17): Honor debuglevel flag in urllib.request.HTTPHandler.
     Patch contributed by Chi Hsuan Yen.

   - bpo-22274(18): In the subprocess module, allow stderr to be
     redirected to stdout even when stdout is not redirected.  Patch by
     Akira Li.

   - bpo-26807(19): mock_open 'files' no longer error on readline at end
     of file.  Patch from Yolanda Robla.

   - bpo-25745(20): Fixed leaking a userptr in curses panel destructor.

   - bpo-26977(21): Removed unnecessary, and ignored, call to sum of
     squares helper in statistics.pvariance.

   - bpo-26881(22): The modulefinder module now supports extended opcode
     arguments.

   - bpo-23815(23): Fixed crashes related to directly created instances
     of types in _tkinter and curses.panel modules.

   - bpo-17765(24): weakref.ref() no longer silently ignores keyword
     arguments.  Patch by Georg Brandl.

   - bpo-26873(25): xmlrpc now raises ResponseError on unsupported type
     tags instead of silently return incorrect result.

   - bpo-26711(26): Fixed the comparison of plistlib.Data with other
     types.

   - bpo-24114(27): Fix an uninitialized variable in ‘ctypes.util’.  The
     bug only occurs on SunOS when the ctypes implementation searches
     for the ‘crle’ program.  Patch by Xiang Zhang.  Tested on SunOS by
     Kees Bos.

   - bpo-26864(28): In urllib.request, change the proxy bypass host
     checking against no_proxy to be case-insensitive, and to not match
     unrelated host names that happen to have a bypassed hostname as a
     suffix.  Patch by Xiang Zhang.

   - bpo-26634(29): recursive_repr() now sets __qualname__ of wrapper.
     Patch by Xiang Zhang.

   - bpo-26804(30): urllib.request will prefer lower_case proxy
     environment variables over UPPER_CASE or Mixed_Case ones.  Patch
     contributed by Hans-Peter Jansen.

   - bpo-26837(31): assertSequenceEqual() now correctly outputs
     non-stringified differing items (like bytes in the -b mode).  This
     affects assertListEqual() and assertTupleEqual().

   - bpo-26041(32): Remove "will be removed in Python 3.7" from
     deprecation messages of platform.dist() and
     platform.linux_distribution().  Patch by Kumaripaba Miyurusara
     Athukorala.

   - bpo-26822(33): itemgetter, attrgetter and methodcaller objects no
     longer silently ignore keyword arguments.

   - bpo-26733(34): Disassembling a class now disassembles class and
     static methods.  Patch by Xiang Zhang.

   - bpo-26801(35): Fix error handling in *note
     shutil.get_terminal_size(): 109b, catch *note AttributeError: 2f6.
     instead of *note NameError: 3e5.  Patch written by Emanuel Barry.

   - bpo-24838(36): tarfile's ustar and gnu formats now correctly
     calculate name and link field limits for multibyte character
     encodings like utf-8.

   - bpo-26717(37): Stop encoding Latin-1-ized WSGI paths with UTF-8.
     Patch by Anthony Sottile.

   - bpo-26735(38): Fix *note os.urandom(): 4c7. on Solaris 11.3 and
     newer when reading more than 1,024 bytes: call ‘getrandom()’
     multiple times with a limit of 1024 bytes per call.

   - bpo-16329(39): Add .webm to mimetypes.types_map.  Patch by
     Giampaolo Rodola'.

   - bpo-13952(40): Add .csv to mimetypes.types_map.  Patch by Geoff
     Wilson.

   - bpo-26709(41): Fixed Y2038 problem in loading binary PLists.

   - bpo-23735(42): Handle terminal resizing with Readline 6.3+ by
     installing our own SIGWINCH handler.  Patch by Eric Price.

   - bpo-26586(43): In http.server, respond with "413 Request header
     fields too large" if there are too many header fields to parse,
     rather than killing the connection and raising an unhandled
     exception.  Patch by Xiang Zhang.

   - bpo-22854(44): Change BufferedReader.writable() and
     BufferedWriter.readable() to always return False.

   - bpo-25195(45): Fix a regression in mock.MagicMock.  _Call is a
     subclass of tuple (changeset 3603bae63c13 only works for classes)
     so we need to implement __ne__ ourselves.  Patch by Andrew Plummer.

   - bpo-26644(46): Raise ValueError rather than SystemError when a
     negative length is passed to SSLSocket.recv() or read().

   - bpo-23804(47): Fix SSL recv(0) and read(0) methods to return zero
     bytes instead of up to 1024.

   - bpo-26616(48): Fixed a bug in datetime.astimezone() method.

   - bpo-21925(49): *note warnings.formatwarning(): 191b. now catches
     exceptions on ‘linecache.getline(...)’ to be able to log *note
     ResourceWarning: 229. emitted late during the Python shutdown
     process.

   - bpo-24266(50): Ctrl+C during Readline history search now cancels
     the search mode when compiled with Readline 7.

   - bpo-26560(51): Avoid potential ValueError in
     BaseHandler.start_response.  Initial patch by Peter Inglesby.

   - bpo-26569(52): Fix *note pyclbr.readmodule(): 7cf. and *note
     pyclbr.readmodule_ex(): 7d0. to support importing packages.

   - bpo-26499(53): Account for remaining Content-Length in
     HTTPResponse.readline() and read1().  Based on patch by Silent
     Ghost.  Also document that HTTPResponse now supports these methods.

   - bpo-25320(54): Handle sockets in directories unittest discovery is
     scanning.  Patch from Victor van den Elzen.

   - bpo-16181(55): cookiejar.http2time() now returns None if year is
     higher than datetime.MAXYEAR.

   - bpo-26513(56): Fixes platform module detection of Windows Server

   - bpo-23718(57): Fixed parsing time in week 0 before Jan 1.  Original
     patch by Tamás Bence Gedai.

   - bpo-20589(58): Invoking Path.owner() and Path.group() on Windows
     now raise NotImplementedError instead of ImportError.

   - bpo-26177(59): Fixed the keys() method for Canvas and Scrollbar
     widgets.

   - bpo-15068(60): Got rid of excessive buffering in the fileinput
     module.  The bufsize parameter is no longer used.

   - bpo-2202(61): Fix UnboundLocalError in
     AbstractDigestAuthHandler.get_algorithm_impls.  Initial patch by
     Mathieu Dupuy.

   - bpo-25718(62): Fixed pickling and copying the accumulate() iterator
     with total is None.

   - bpo-26475(63): Fixed debugging output for regular expressions with
     the (?x) flag.

   - bpo-26457(64): Fixed the subnets() methods in IP network classes
     for the case when resulting prefix length is equal to maximal
     prefix length.  Based on patch by Xiang Zhang.

   - bpo-26385(65): Remove the file if the internal open() call in
     NamedTemporaryFile() fails.  Patch by Silent Ghost.

   - bpo-26402(66): Fix XML-RPC client to retry when the server shuts
     down a persistent connection.  This was a regression related to the
     new http.client.RemoteDisconnected exception in 3.5.0a4.

   - bpo-25913(67): Leading ‘<~’ is optional now in base64.a85decode()
     with adobe=True.  Patch by Swati Jaiswal.

   - bpo-26186(68): Remove an invalid type check in
     importlib.util.LazyLoader.

   - bpo-26367(69): importlib.__import__() raises SystemError like
     builtins.__import__() when ‘level’ is specified but without an
     accompanying package specified.

   - bpo-26309(70): In the "socketserver" module, shut down the request
     (closing the connected socket) when verify_request() returns false.
     Patch by Aviv Palivoda.

   - bpo-25995(71): os.walk() no longer uses FDs proportional to the
     tree depth.

   - bpo-26117(72): The os.scandir() iterator now closes file descriptor
     not only when the iteration is finished, but when it was failed
     with error.

   - bpo-25911(73): Restored support of bytes paths in os.walk() on
     Windows.

   - bpo-26045(74): Add UTF-8 suggestion to error message when posting a
     non-Latin-1 string with http.client.

   - bpo-12923(75): Reset FancyURLopener's redirect counter even if
     there is an exception.  Based on patches by Brian Brazil and Daniel
     Rocco.

   - bpo-25945(76): Fixed a crash when unpickle the functools.partial
     object with wrong state.  Fixed a leak in failed functools.partial
     constructor.  "args" and "keywords" attributes of functools.partial
     have now always types tuple and dict correspondingly.

   - bpo-26202(77): copy.deepcopy() now correctly copies range() objects
     with non-atomic attributes.

   - bpo-23076(78): Path.glob() now raises a ValueError if it's called
     with an invalid pattern.  Patch by Thomas Nyberg.

   - bpo-19883(79): Fixed possible integer overflows in zipimport.

   - bpo-26227(80): On Windows, getnameinfo(), gethostbyaddr() and
     gethostbyname_ex() functions of the socket module now decode the
     hostname from the ANSI code page rather than UTF-8.

   - bpo-26147(81): xmlrpc now works with strings not encodable with
     used non-UTF-8 encoding.

   - bpo-25935(82): Garbage collector now breaks reference loops with
     OrderedDict.

   - bpo-16620(83): Fixed AttributeError in msilib.Directory.glob().

   - bpo-26013(84): Added compatibility with broken protocol 2 pickles
     created in old Python 3 versions (3.4.3 and lower).

   - bpo-25850(85): Use cross-compilation by default for 64-bit Windows.

   - bpo-17633(86): Improve zipimport's support for namespace packages.

   - bpo-24705(87): Fix sysconfig._parse_makefile not expanding ${} vars
     appearing before $() vars.

   - bpo-22138(88): Fix mock.patch behavior when patching descriptors.
     Restore original values after patching.  Patch contributed by Sean
     McCully.

   - bpo-25672(89): In the ssl module, enable the
     SSL_MODE_RELEASE_BUFFERS mode option if it is safe to do so.

   - bpo-26012(90): Don't traverse into symlinks for ‘**’ pattern in
     pathlib.Path.[r]glob().

   - bpo-24120(91): Ignore PermissionError when traversing a tree with
     pathlib.Path.[r]glob().  Patch by Ulrich Petri.

   - bpo-25447(92): fileinput now uses sys.stdin as-is if it does not
     have a buffer attribute (restores backward compatibility).

   - bpo-25447(93): Copying the lru_cache() wrapper object now always
     works, independently from the type of the wrapped object (by
     returning the original object unchanged).

   - bpo-24103(94): Fixed possible use after free in
     ElementTree.XMLPullParser.

   - bpo-25860(95): os.fwalk() no longer skips remaining directories
     when error occurs.  Original patch by Samson Lee.

   - bpo-25914(96): Fixed and simplified OrderedDict.__sizeof__.

   - bpo-25902(97): Fixed various refcount issues in ElementTree
     iteration.

   - bpo-25717(98): Restore the previous behaviour of tolerating most
     fstat() errors when opening files.  This was a regression in 3.5a1,
     and stopped anonymous temporary files from working in special
     cases.

   - bpo-24903(99): Fix regression in number of arguments compileall
     accepts when '-d' is specified.  The check on the number of
     arguments has been dropped completely as it never worked correctly
     anyway.

   - bpo-25764(100): In the subprocess module, preserve any exception
     caused by fork() failure when preexec_fn is used.

   - bpo-6478(101): _strptime's regexp cache now is reset after changing
     timezone with time.tzset().

   - bpo-14285(102): When executing a package with the "python -m
     package" option, and package initialization fails, a proper
     traceback is now reported.  The "runpy" module now lets exceptions
     from package initialization pass back to the caller, rather than
     raising ImportError.

   - bpo-19771(103): Also in runpy and the "-m" option, omit the
     irrelevant message ".  .  .  is a package and cannot be directly
     executed" if the package could not even be initialized (e.g.  due
     to a bad ‘*.pyc’ file).

   - bpo-25177(104): Fixed problem with the mean of very small and very
     large numbers.  As a side effect, statistics.mean and
     statistics.variance should be significantly faster.

   - bpo-25718(105): Fixed copying object with state with boolean value
     is false.

   - bpo-10131(106): Fixed deep copying of minidom documents.  Based on
     patch by Marian Ganisin.

   - bpo-25725(107): Fixed a reference leak in pickle.loads() when
     unpickling invalid data including tuple instructions.

   - bpo-25663(108): In the Readline completer, avoid listing duplicate
     global names, and search the global namespace before searching
     builtins.

   - bpo-25688(109): Fixed file leak in ElementTree.iterparse() raising
     an error.

   - bpo-23914(110): Fixed SystemError raised by unpickler on broken
     pickle data.

   - bpo-25691(111): Fixed crash on deleting ElementTree.Element
     attributes.

   - bpo-25624(112): ZipFile now always writes a ZIP_STORED header for
     directory entries.  Patch by Dingyuan Wang.

   - Skip getaddrinfo if host is already resolved.  Patch by A. Jesse
     Jiryu Davis.

   - bpo-26050(113): Add asyncio.StreamReader.readuntil() method.  Patch
     by Марк Коренберг.

   - bpo-25924(114): Avoid unnecessary serialization of getaddrinfo(3)
     calls on OS X versions 10.5 or higher.  Original patch by A. Jesse
     Jiryu Davis.

   - bpo-26406(115): Avoid unnecessary serialization of getaddrinfo(3)
     calls on current versions of OpenBSD and NetBSD. Patch by A. Jesse
     Jiryu Davis.

   - bpo-26848(116): Fix asyncio/subprocess.communicate() to handle
     empty input.  Patch by Jack O'Connor.

   - bpo-27040(117): Add loop.get_exception_handler method

   - bpo-27041(118): asyncio: Add loop.create_future method

   - bpo-27223(119): asyncio: Fix _read_ready and _write_ready to
     respect _conn_lost.  Patch by Łukasz Langa.

   - bpo-22970(120): asyncio: Fix inconsistency cancelling
     Condition.wait.  Patch by David Coles.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21386

   (2) https://bugs.python.org/issue?@action=redirect&bpo=20900

   (3) https://peps.python.org/pep-0492/

   (4) https://bugs.python.org/issue?@action=redirect&bpo=25738

   (5) https://bugs.python.org/issue?@action=redirect&bpo=21313

   (6) https://bugs.python.org/issue?@action=redirect&bpo=27164

   (7) https://bugs.python.org/issue?@action=redirect&bpo=24291

   (8) https://bugs.python.org/issue?@action=redirect&bpo=26809

   (9) https://bugs.python.org/issue?@action=redirect&bpo=26373

   (10) https://bugs.python.org/issue?@action=redirect&bpo=21776

   (11) https://bugs.python.org/issue?@action=redirect&bpo=27114

   (12) https://bugs.python.org/issue?@action=redirect&bpo=18383

   (13) https://bugs.python.org/issue?@action=redirect&bpo=27057

   (14) https://bugs.python.org/issue?@action=redirect&bpo=27014

   (15) https://bugs.python.org/issue?@action=redirect&bpo=14132

   (16) https://bugs.python.org/issue?@action=redirect&bpo=17214

   (17) https://bugs.python.org/issue?@action=redirect&bpo=26892

   (18) https://bugs.python.org/issue?@action=redirect&bpo=22274

   (19) https://bugs.python.org/issue?@action=redirect&bpo=26807

   (20) https://bugs.python.org/issue?@action=redirect&bpo=25745

   (21) https://bugs.python.org/issue?@action=redirect&bpo=26977

   (22) https://bugs.python.org/issue?@action=redirect&bpo=26881

   (23) https://bugs.python.org/issue?@action=redirect&bpo=23815

   (24) https://bugs.python.org/issue?@action=redirect&bpo=17765

   (25) https://bugs.python.org/issue?@action=redirect&bpo=26873

   (26) https://bugs.python.org/issue?@action=redirect&bpo=26711

   (27) https://bugs.python.org/issue?@action=redirect&bpo=24114

   (28) https://bugs.python.org/issue?@action=redirect&bpo=26864

   (29) https://bugs.python.org/issue?@action=redirect&bpo=26634

   (30) https://bugs.python.org/issue?@action=redirect&bpo=26804

   (31) https://bugs.python.org/issue?@action=redirect&bpo=26837

   (32) https://bugs.python.org/issue?@action=redirect&bpo=26041

   (33) https://bugs.python.org/issue?@action=redirect&bpo=26822

   (34) https://bugs.python.org/issue?@action=redirect&bpo=26733

   (35) https://bugs.python.org/issue?@action=redirect&bpo=26801

   (36) https://bugs.python.org/issue?@action=redirect&bpo=24838

   (37) https://bugs.python.org/issue?@action=redirect&bpo=26717

   (38) https://bugs.python.org/issue?@action=redirect&bpo=26735

   (39) https://bugs.python.org/issue?@action=redirect&bpo=16329

   (40) https://bugs.python.org/issue?@action=redirect&bpo=13952

   (41) https://bugs.python.org/issue?@action=redirect&bpo=26709

   (42) https://bugs.python.org/issue?@action=redirect&bpo=23735

   (43) https://bugs.python.org/issue?@action=redirect&bpo=26586

   (44) https://bugs.python.org/issue?@action=redirect&bpo=22854

   (45) https://bugs.python.org/issue?@action=redirect&bpo=25195

   (46) https://bugs.python.org/issue?@action=redirect&bpo=26644

   (47) https://bugs.python.org/issue?@action=redirect&bpo=23804

   (48) https://bugs.python.org/issue?@action=redirect&bpo=26616

   (49) https://bugs.python.org/issue?@action=redirect&bpo=21925

   (50) https://bugs.python.org/issue?@action=redirect&bpo=24266

   (51) https://bugs.python.org/issue?@action=redirect&bpo=26560

   (52) https://bugs.python.org/issue?@action=redirect&bpo=26569

   (53) https://bugs.python.org/issue?@action=redirect&bpo=26499

   (54) https://bugs.python.org/issue?@action=redirect&bpo=25320

   (55) https://bugs.python.org/issue?@action=redirect&bpo=16181

   (56) https://bugs.python.org/issue?@action=redirect&bpo=26513

   (57) https://bugs.python.org/issue?@action=redirect&bpo=23718

   (58) https://bugs.python.org/issue?@action=redirect&bpo=20589

   (59) https://bugs.python.org/issue?@action=redirect&bpo=26177

   (60) https://bugs.python.org/issue?@action=redirect&bpo=15068

   (61) https://bugs.python.org/issue?@action=redirect&bpo=2202

   (62) https://bugs.python.org/issue?@action=redirect&bpo=25718

   (63) https://bugs.python.org/issue?@action=redirect&bpo=26475

   (64) https://bugs.python.org/issue?@action=redirect&bpo=26457

   (65) https://bugs.python.org/issue?@action=redirect&bpo=26385

   (66) https://bugs.python.org/issue?@action=redirect&bpo=26402

   (67) https://bugs.python.org/issue?@action=redirect&bpo=25913

   (68) https://bugs.python.org/issue?@action=redirect&bpo=26186

   (69) https://bugs.python.org/issue?@action=redirect&bpo=26367

   (70) https://bugs.python.org/issue?@action=redirect&bpo=26309

   (71) https://bugs.python.org/issue?@action=redirect&bpo=25995

   (72) https://bugs.python.org/issue?@action=redirect&bpo=26117

   (73) https://bugs.python.org/issue?@action=redirect&bpo=25911

   (74) https://bugs.python.org/issue?@action=redirect&bpo=26045

   (75) https://bugs.python.org/issue?@action=redirect&bpo=12923

   (76) https://bugs.python.org/issue?@action=redirect&bpo=25945

   (77) https://bugs.python.org/issue?@action=redirect&bpo=26202

   (78) https://bugs.python.org/issue?@action=redirect&bpo=23076

   (79) https://bugs.python.org/issue?@action=redirect&bpo=19883

   (80) https://bugs.python.org/issue?@action=redirect&bpo=26227

   (81) https://bugs.python.org/issue?@action=redirect&bpo=26147

   (82) https://bugs.python.org/issue?@action=redirect&bpo=25935

   (83) https://bugs.python.org/issue?@action=redirect&bpo=16620

   (84) https://bugs.python.org/issue?@action=redirect&bpo=26013

   (85) https://bugs.python.org/issue?@action=redirect&bpo=25850

   (86) https://bugs.python.org/issue?@action=redirect&bpo=17633

   (87) https://bugs.python.org/issue?@action=redirect&bpo=24705

   (88) https://bugs.python.org/issue?@action=redirect&bpo=22138

   (89) https://bugs.python.org/issue?@action=redirect&bpo=25672

   (90) https://bugs.python.org/issue?@action=redirect&bpo=26012

   (91) https://bugs.python.org/issue?@action=redirect&bpo=24120

   (92) https://bugs.python.org/issue?@action=redirect&bpo=25447

   (93) https://bugs.python.org/issue?@action=redirect&bpo=25447

   (94) https://bugs.python.org/issue?@action=redirect&bpo=24103

   (95) https://bugs.python.org/issue?@action=redirect&bpo=25860

   (96) https://bugs.python.org/issue?@action=redirect&bpo=25914

   (97) https://bugs.python.org/issue?@action=redirect&bpo=25902

   (98) https://bugs.python.org/issue?@action=redirect&bpo=25717

   (99) https://bugs.python.org/issue?@action=redirect&bpo=24903

   (100) https://bugs.python.org/issue?@action=redirect&bpo=25764

   (101) https://bugs.python.org/issue?@action=redirect&bpo=6478

   (102) https://bugs.python.org/issue?@action=redirect&bpo=14285

   (103) https://bugs.python.org/issue?@action=redirect&bpo=19771

   (104) https://bugs.python.org/issue?@action=redirect&bpo=25177

   (105) https://bugs.python.org/issue?@action=redirect&bpo=25718

   (106) https://bugs.python.org/issue?@action=redirect&bpo=10131

   (107) https://bugs.python.org/issue?@action=redirect&bpo=25725

   (108) https://bugs.python.org/issue?@action=redirect&bpo=25663

   (109) https://bugs.python.org/issue?@action=redirect&bpo=25688

   (110) https://bugs.python.org/issue?@action=redirect&bpo=23914

   (111) https://bugs.python.org/issue?@action=redirect&bpo=25691

   (112) https://bugs.python.org/issue?@action=redirect&bpo=25624

   (113) https://bugs.python.org/issue?@action=redirect&bpo=26050

   (114) https://bugs.python.org/issue?@action=redirect&bpo=25924

   (115) https://bugs.python.org/issue?@action=redirect&bpo=26406

   (116) https://bugs.python.org/issue?@action=redirect&bpo=26848

   (117) https://bugs.python.org/issue?@action=redirect&bpo=27040

   (118) https://bugs.python.org/issue?@action=redirect&bpo=27041

   (119) https://bugs.python.org/issue?@action=redirect&bpo=27223

   (120) https://bugs.python.org/issue?@action=redirect&bpo=22970


File: python.info,  Node: IDLE<57>,  Next: Documentation<67>,  Prev: Library<80>,  Up: Python 3 5 2 release candidate 1

1.23.92.4 IDLE
..............

   - bpo-5124(1): Paste with text selected now replaces the selection on
     X11.  This matches how paste works on Windows, Mac, most modern
     Linux apps, and ttk widgets.  Original patch by Serhiy Storchaka.

   - bpo-24759(2): Make clear in idlelib.idle_test.__init__ that the
     directory is a private implementation of test.test_idle and tool
     for maintainers.

   - bpo-27196(3): Stop 'ThemeChanged' warnings when running IDLE tests.
     These persisted after other warnings were suppressed in #20567.
     Apply Serhiy Storchaka's update_idletasks solution to four test
     files.  Record this additional advice in idle_test/README.txt

   - bpo-20567(4): Revise idle_test/README.txt with advice about
     avoiding tk warning messages from tests.  Apply advice to several
     IDLE tests.

   - bpo-27117(5): Make colorizer htest and turtledemo work with dark
     themes.  Move code for configuring text widget colors to a new
     function.

   - bpo-26673(6): When tk reports font size as 0, change to size 10.
     Such fonts on Linux prevented the configuration dialog from
     opening.

   - bpo-21939(7): Add test for IDLE's percolator.  Original patch by
     Saimadhav Heblikar.

   - bpo-21676(8): Add test for IDLE's replace dialog.  Original patch
     by Saimadhav Heblikar.

   - bpo-18410(9): Add test for IDLE's search dialog.  Original patch by
     Westley Martínez.

   - bpo-21703(10): Add test for IDLE's undo delegator.  Original patch
     by Saimadhav Heblikar .

   - bpo-27044(11): Add ConfigDialog.remove_var_callbacks to stop memory
     leaks.

   - bpo-23977(12): Add more asserts to test_delegator.

   - bpo-20640(13): Add tests for idlelib.configHelpSourceEdit.  Patch
     by Saimadhav Heblikar.

   - In the 'IDLE-console differences' section of the IDLE doc, clarify
     how running with IDLE affects sys.modules and the standard streams.

   - bpo-25507(14): fix incorrect change in IOBinding that prevented
     printing.  Augment IOBinding htest to include all major IOBinding
     functions.

   - bpo-25905(15): Revert unwanted conversion of ' to ’ RIGHT SINGLE
     QUOTATION MARK in README.txt and open this and NEWS.txt with
     'ascii'.  Re-encode CREDITS.txt to utf-8 and open it with 'utf-8'.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=5124

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24759

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27196

   (4) https://bugs.python.org/issue?@action=redirect&bpo=20567

   (5) https://bugs.python.org/issue?@action=redirect&bpo=27117

   (6) https://bugs.python.org/issue?@action=redirect&bpo=26673

   (7) https://bugs.python.org/issue?@action=redirect&bpo=21939

   (8) https://bugs.python.org/issue?@action=redirect&bpo=21676

   (9) https://bugs.python.org/issue?@action=redirect&bpo=18410

   (10) https://bugs.python.org/issue?@action=redirect&bpo=21703

   (11) https://bugs.python.org/issue?@action=redirect&bpo=27044

   (12) https://bugs.python.org/issue?@action=redirect&bpo=23977

   (13) https://bugs.python.org/issue?@action=redirect&bpo=20640

   (14) https://bugs.python.org/issue?@action=redirect&bpo=25507

   (15) https://bugs.python.org/issue?@action=redirect&bpo=25905


File: python.info,  Node: Documentation<67>,  Next: Tests<72>,  Prev: IDLE<57>,  Up: Python 3 5 2 release candidate 1

1.23.92.5 Documentation
.......................

   - bpo-19489(1): Moved the search box from the sidebar to the header
     and footer of each page.  Patch by Ammar Askar.

   - bpo-24136(2): Document the new PEP 448(3) unpacking syntax of 3.5.

   - bpo-26736(4): Used HTTPS for external links in the documentation if
     possible.

   - bpo-6953(5): Rework the Readline module documentation to group
     related functions together, and add more details such as what
     underlying Readline functions and variables are accessed.

   - bpo-23606(6): Adds note to ctypes documentation regarding
     cdll.msvcrt.

   - bpo-25500(7): Fix documentation to not claim that __import__ is
     searched for in the global scope.

   - bpo-26014(8): Update 3.x packaging documentation: * "See also"
     links to the new docs are now provided in the legacy pages * links
     to setuptools documentation have been updated

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=19489

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24136

   (3) https://peps.python.org/pep-0448/

   (4) https://bugs.python.org/issue?@action=redirect&bpo=26736

   (5) https://bugs.python.org/issue?@action=redirect&bpo=6953

   (6) https://bugs.python.org/issue?@action=redirect&bpo=23606

   (7) https://bugs.python.org/issue?@action=redirect&bpo=25500

   (8) https://bugs.python.org/issue?@action=redirect&bpo=26014


File: python.info,  Node: Tests<72>,  Next: Build<77>,  Prev: Documentation<67>,  Up: Python 3 5 2 release candidate 1

1.23.92.6 Tests
...............

   - bpo-21916(1): Added tests for the turtle module.  Patch by ingrid,
     Gregory Loyse and Jelle Zijlstra.

   - bpo-26523(2): The multiprocessing thread pool
     (multiprocessing.dummy.Pool) was untested.

   - bpo-26015(3): Added new tests for pickling iterators of mutable
     sequences.

   - bpo-26325(4): Added test.support.check_no_resource_warning() to
     check that no ResourceWarning is emitted.

   - bpo-25940(5): Changed test_ssl to use self-signed.pythontest.net.
     This avoids relying on svn.python.org, which recently changed root
     certificate.

   - bpo-25616(6): Tests for OrderedDict are extracted from
     test_collections into separate file test_ordered_dict.

   - bpo-26583(7): Skip test_timestamp_overflow in test_import if
     bytecode files cannot be written.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21916

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26523

   (3) https://bugs.python.org/issue?@action=redirect&bpo=26015

   (4) https://bugs.python.org/issue?@action=redirect&bpo=26325

   (5) https://bugs.python.org/issue?@action=redirect&bpo=25940

   (6) https://bugs.python.org/issue?@action=redirect&bpo=25616

   (7) https://bugs.python.org/issue?@action=redirect&bpo=26583


File: python.info,  Node: Build<77>,  Next: Windows<67>,  Prev: Tests<72>,  Up: Python 3 5 2 release candidate 1

1.23.92.7 Build
...............

   - bpo-26884(1): Fix linking extension modules for cross builds.
     Patch by Xavier de Gaye.

   - bpo-22359(2): Disable the rules for running _freeze_importlib and
     pgen when cross-compiling.  The output of these programs is
     normally saved with the source code anyway, and is still
     regenerated when doing a native build.  Patch by Xavier de Gaye.

   - bpo-27229(3): Fix the cross-compiling pgen rule for in-tree builds.
     Patch by Xavier de Gaye.

   - bpo-21668(4): Link audioop, _datetime, _ctypes_test modules to
     libm, except on Mac OS X. Patch written by Xavier de Gaye.

   - bpo-25702(5): A -with-lto configure option has been added that will
     enable link time optimizations at build time during a make
     profile-opt.  Some compilers and toolchains are known to not
     produce stable code when using LTO, be sure to test things
     thoroughly before relying on it.  It can provide a few % speed up
     over profile-opt alone.

   - bpo-26624(6): Adds validation of ucrtbase[d].dll version with
     warning for old versions.

   - bpo-17603(7): Avoid error about nonexistent fileblocks.o file by
     using a lower-level check for st_blocks in struct stat.

   - bpo-26079(8): Fixing the build output folder for tix-8.4.3.6.
     Patch by Bjoern Thiel.

   - bpo-26465(9): Update Windows builds to use OpenSSL 1.0.2g.

   - bpo-24421(10): Compile Modules/_math.c once, before building
     extensions.  Previously it could fail to compile properly if the
     math and cmath builds were concurrent.

   - bpo-25348(11): Added ‘--pgo’ and ‘--pgo-job’ arguments to
     ‘PCbuild\build.bat’ for building with Profile-Guided Optimization.
     The old ‘PCbuild\build_pgo.bat’ script is now deprecated, and
     simply calls ‘PCbuild\build.bat --pgo %*’.

   - bpo-25827(12): Add support for building with ICC to ‘configure’,
     including a new ‘--with-icc’ flag.

   - bpo-25696(13): Fix installation of Python on UNIX with make -j9.

   - bpo-26930(14): Update OS X 10.5+ 32-bit-only installer to build and
     link with OpenSSL 1.0.2h.

   - bpo-26268(15): Update Windows builds to use OpenSSL 1.0.2f.

   - bpo-25136(16): Support Apple Xcode 7's new textual SDK stub
     libraries.

   - bpo-24324(17): Do not enable unreachable code warnings when using
     gcc as the option does not work correctly in older versions of gcc
     and has been silently removed as of gcc-4.5.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26884

   (2) https://bugs.python.org/issue?@action=redirect&bpo=22359

   (3) https://bugs.python.org/issue?@action=redirect&bpo=27229

   (4) https://bugs.python.org/issue?@action=redirect&bpo=21668

   (5) https://bugs.python.org/issue?@action=redirect&bpo=25702

   (6) https://bugs.python.org/issue?@action=redirect&bpo=26624

   (7) https://bugs.python.org/issue?@action=redirect&bpo=17603

   (8) https://bugs.python.org/issue?@action=redirect&bpo=26079

   (9) https://bugs.python.org/issue?@action=redirect&bpo=26465

   (10) https://bugs.python.org/issue?@action=redirect&bpo=24421

   (11) https://bugs.python.org/issue?@action=redirect&bpo=25348

   (12) https://bugs.python.org/issue?@action=redirect&bpo=25827

   (13) https://bugs.python.org/issue?@action=redirect&bpo=25696

   (14) https://bugs.python.org/issue?@action=redirect&bpo=26930

   (15) https://bugs.python.org/issue?@action=redirect&bpo=26268

   (16) https://bugs.python.org/issue?@action=redirect&bpo=25136

   (17) https://bugs.python.org/issue?@action=redirect&bpo=24324


File: python.info,  Node: Windows<67>,  Next: Tools/Demos<42>,  Prev: Build<77>,  Up: Python 3 5 2 release candidate 1

1.23.92.8 Windows
.................

   - bpo-27053(1): Updates make_zip.py to correctly generate library ZIP
     file.

   - bpo-26268(2): Update the prepare_ssl.py script to handle OpenSSL
     releases that don't include the contents of the include directory
     (that is, 1.0.2e and later).

   - bpo-26071(3): bdist_wininst created binaries fail to start and find
     32bit Python

   - bpo-26073(4): Update the list of magic numbers in launcher

   - bpo-26065(5): Excludes venv from library when generating embeddable
     distro.

   - bpo-17500(6): Remove unused and outdated icons.  (See also:
     ‘https://github.com/python/pythondotorg/issues/945’)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=27053

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26268

   (3) https://bugs.python.org/issue?@action=redirect&bpo=26071

   (4) https://bugs.python.org/issue?@action=redirect&bpo=26073

   (5) https://bugs.python.org/issue?@action=redirect&bpo=26065

   (6) https://bugs.python.org/issue?@action=redirect&bpo=17500


File: python.info,  Node: Tools/Demos<42>,  Prev: Windows<67>,  Up: Python 3 5 2 release candidate 1

1.23.92.9 Tools/Demos
.....................

   - bpo-26799(1): Fix python-gdb.py: don't get C types once when the
     Python code is loaded, but get C types on demand.  The C types can
     change if python-gdb.py is loaded before the Python executable.
     Patch written by Thomas Ilsche.

   - bpo-26271(2): Fix the Freeze tool to properly use flags passed
     through configure.  Patch by Daniel Shaulov.

   - bpo-26489(3): Add dictionary unpacking support to
     Tools/parser/unparse.py.  Patch by Guo Ci Teo.

   - bpo-26316(4): Fix variable name typo in Argument Clinic.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=26799

   (2) https://bugs.python.org/issue?@action=redirect&bpo=26271

   (3) https://bugs.python.org/issue?@action=redirect&bpo=26489

   (4) https://bugs.python.org/issue?@action=redirect&bpo=26316


File: python.info,  Node: Python 3 5 1 final,  Next: Python 3 5 1 release candidate 1,  Prev: Python 3 5 2 release candidate 1,  Up: Changelog（更動日誌）

1.23.93 Python 3.5.1 final
--------------------------

'Release date: 2015-12-06'

* Menu:

* Core and Builtins: Core and Builtins<82>.
* Windows: Windows<68>.


File: python.info,  Node: Core and Builtins<82>,  Next: Windows<68>,  Up: Python 3 5 1 final

1.23.93.1 Core and Builtins
...........................

   - bpo-25709(1): Fixed problem with in-place string concatenation and
     utf-8 cache.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25709


File: python.info,  Node: Windows<68>,  Prev: Core and Builtins<82>,  Up: Python 3 5 1 final

1.23.93.2 Windows
.................

   - bpo-25715(1): Python 3.5.1 installer shows wrong upgrade path and
     incorrect logic for launcher detection.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25715


File: python.info,  Node: Python 3 5 1 release candidate 1,  Next: Python 3 5 0 final,  Prev: Python 3 5 1 final,  Up: Changelog（更動日誌）

1.23.94 Python 3.5.1 release candidate 1
----------------------------------------

'Release date: 2015-11-22'

* Menu:

* Core and Builtins: Core and Builtins<83>.
* Library: Library<81>.
* IDLE: IDLE<58>.
* Documentation: Documentation<68>.
* Tests: Tests<73>.
* Build: Build<78>.
* Windows: Windows<69>.
* Tools/Demos: Tools/Demos<43>.


File: python.info,  Node: Core and Builtins<83>,  Next: Library<81>,  Up: Python 3 5 1 release candidate 1

1.23.94.1 Core and Builtins
...........................

   - bpo-25630(1): Fix a possible segfault during argument parsing in
     functions that accept filesystem paths.

   - bpo-23564(2): Fixed a partially broken sanity check in the
     _posixsubprocess internals regarding how fds_to_pass were passed to
     the child.  The bug had no actual impact as subprocess.py already
     avoided it.

   - bpo-25388(3): Fixed tokenizer crash when processing undecodable
     source code with a null byte.

   - bpo-25462(4): The hash of the key now is calculated only once in
     most operations in C implementation of OrderedDict.

   - bpo-22995(5): Default implementation of __reduce__ and
     __reduce_ex__ now rejects builtin types with not defined __new__.

   - bpo-25555(6): Fix parser and AST: fill lineno and col_offset of
     "arg" node when compiling AST from Python objects.

   - bpo-24802(7): Avoid buffer overreads when int(), float(),
     compile(), exec() and eval() are passed bytes-like objects.  These
     objects are not necessarily terminated by a null byte, but the
     functions assumed they were.

   - bpo-24726(8): Fixed a crash and leaking NULL in repr() of
     OrderedDict that was mutated by direct calls of dict methods.

   - bpo-25449(9): Iterating OrderedDict with keys with unstable hash
     now raises KeyError in C implementations as well as in Python
     implementation.

   - bpo-25395(10): Fixed crash when highly nested OrderedDict
     structures were garbage collected.

   - bpo-25274(11): sys.setrecursionlimit() now raises a RecursionError
     if the new recursion limit is too low depending at the current
     recursion depth.  Modify also the "lower-water mark" formula to
     make it monotonic.  This mark is used to decide when the overflowed
     flag of the thread state is reset.

   - bpo-24402(12): Fix input() to prompt to the redirected stdout when
     sys.stdout.fileno() fails.

   - bpo-24806(13): Prevent builtin types that are not allowed to be
     subclassed from being subclassed through multiple inheritance.

   - bpo-24848(14): Fixed a number of bugs in UTF-7 decoding of
     misformed data.

   - bpo-25280(15): Import trace messages emitted in verbose (-v) mode
     are no longer formatted twice.

   - bpo-25003(16): On Solaris 11.3 or newer, os.urandom() now uses the
     getrandom() function instead of the getentropy() function.  The
     getentropy() function is blocking to generate very good quality
     entropy, os.urandom() doesn't need such high-quality entropy.

   - bpo-25182(17): The stdprinter (used as sys.stderr before the io
     module is imported at startup) now uses the backslashreplace error
     handler.

   - bpo-25131(18): Make the line number and column offset of set/dict
     literals and comprehensions correspond to the opening brace.

   - bpo-25150(19): Hide the private ‘_Py_atomic_XXX’ symbols from the
     public Python.h header to fix a compilation error with OpenMP.
     PyThreadState_GET() becomes an alias to PyThreadState_Get() to
     avoid ABI incompatibilities.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25630

   (2) https://bugs.python.org/issue?@action=redirect&bpo=23564

   (3) https://bugs.python.org/issue?@action=redirect&bpo=25388

   (4) https://bugs.python.org/issue?@action=redirect&bpo=25462

   (5) https://bugs.python.org/issue?@action=redirect&bpo=22995

   (6) https://bugs.python.org/issue?@action=redirect&bpo=25555

   (7) https://bugs.python.org/issue?@action=redirect&bpo=24802

   (8) https://bugs.python.org/issue?@action=redirect&bpo=24726

   (9) https://bugs.python.org/issue?@action=redirect&bpo=25449

   (10) https://bugs.python.org/issue?@action=redirect&bpo=25395

   (11) https://bugs.python.org/issue?@action=redirect&bpo=25274

   (12) https://bugs.python.org/issue?@action=redirect&bpo=24402

   (13) https://bugs.python.org/issue?@action=redirect&bpo=24806

   (14) https://bugs.python.org/issue?@action=redirect&bpo=24848

   (15) https://bugs.python.org/issue?@action=redirect&bpo=25280

   (16) https://bugs.python.org/issue?@action=redirect&bpo=25003

   (17) https://bugs.python.org/issue?@action=redirect&bpo=25182

   (18) https://bugs.python.org/issue?@action=redirect&bpo=25131

   (19) https://bugs.python.org/issue?@action=redirect&bpo=25150


File: python.info,  Node: Library<81>,  Next: IDLE<58>,  Prev: Core and Builtins<83>,  Up: Python 3 5 1 release candidate 1

1.23.94.2 Library
.................

   - bpo-25626(1): Change three zlib functions to accept sizes that fit
     in Py_ssize_t, but internally cap those sizes to UINT_MAX. This
     resolves a regression in 3.5 where GzipFile.read() failed to read
     chunks larger than 2 or 4 GiB. The change affects the
     zlib.Decompress.decompress() max_length parameter, the
     zlib.decompress() bufsize parameter, and the
     zlib.Decompress.flush() length parameter.

   - bpo-25583(2): Avoid incorrect errors raised by
     os.makedirs(exist_ok=True) when the OS gives priority to errors
     such as EACCES over EEXIST.

   - bpo-25593(3): Change semantics of EventLoop.stop() in asyncio.

   - bpo-6973(4): When we know a subprocess.Popen process has died, do
     not allow the send_signal(), terminate(), or kill() methods to do
     anything as they could potentially signal a different process.

   - bpo-25590(5): In the Readline completer, only call getattr() once
     per attribute.

   - bpo-25498(6): Fix a crash when garbage-collecting ctypes objects
     created by wrapping a memoryview.  This was a regression made in
     3.5a1.  Based on patch by Eryksun.

   - bpo-25584(7): Added "escape" to the __all__ list in the glob
     module.

   - bpo-25584(8): Fixed recursive glob() with patterns starting with
     ‘**’.

   - bpo-25446(9): Fix regression in smtplib's AUTH LOGIN support.

   - bpo-18010(10): Fix the pydoc web server's module search function to
     handle exceptions from importing packages.

   - bpo-25554(11): Got rid of circular references in regular expression
     parsing.

   - bpo-25510(12): fileinput.FileInput.readline() now returns b''
     instead of '' at the end if the FileInput was opened with binary
     mode.  Patch by Ryosuke Ito.

   - bpo-25503(13): Fixed inspect.getdoc() for inherited docstrings of
     properties.  Original patch by John Mark Vandenberg.

   - bpo-25515(14): Always use os.urandom as a source of randomness in
     uuid.uuid4.

   - bpo-21827(15): Fixed textwrap.dedent() for the case when largest
     common whitespace is a substring of smallest leading whitespace.
     Based on patch by Robert Li.

   - bpo-25447(16): The lru_cache() wrapper objects now can be copied
     and pickled (by returning the original object unchanged).

   - bpo-25390(17): typing: Don't crash on Union[str, Pattern].

   - bpo-25441(18): asyncio: Raise error from drain() when socket is
     closed.

   - bpo-25410(19): Cleaned up and fixed minor bugs in C implementation
     of OrderedDict.

   - bpo-25411(20): Improved Unicode support in SMTPHandler through
     better use of the email package.  Thanks to user simon04 for the
     patch.

   - bpo-25407(21): Remove mentions of the formatter module being
     removed in Python 3.6.

   - bpo-25406(22): Fixed a bug in C implementation of
     OrderedDict.move_to_end() that caused segmentation fault or hang in
     iterating after moving several items to the start of ordered dict.

   - bpo-25364(23): zipfile now works in threads disabled builds.

   - bpo-25328(24): smtpd's SMTPChannel now correctly raises a
     ValueError if both decode_data and enable_SMTPUTF8 are set to true.

   - bpo-25316(25): distutils raises OSError instead of
     DistutilsPlatformError when MSVC is not installed.

   - bpo-25380(26): Fixed protocol for the STACK_GLOBAL opcode in
     pickletools.opcodes.

   - bpo-23972(27): Updates asyncio datagram create method allowing
     reuseport and reuseaddr socket options to be set prior to binding
     the socket.  Mirroring the existing asyncio create_server method
     the reuseaddr option for datagram sockets defaults to True if the
     O/S is 'posix' (except if the platform is Cygwin).  Patch by Chris
     Laws.

   - bpo-25304(28): Add asyncio.run_coroutine_threadsafe().  This lets
     you submit a coroutine to a loop from another thread, returning a
     concurrent.futures.Future.  By Vincent Michel.

   - bpo-25232(29): Fix CGIRequestHandler to split the query from the
     URL at the first question mark (?)  rather than the last.  Patch
     from Xiang Zhang.

   - bpo-24657(30): Prevent CGIRequestHandler from collapsing slashes in
     the query part of the URL as if it were a path.  Patch from Xiang
     Zhang.

   - bpo-24483(31): C implementation of functools.lru_cache() now
     calculates key's hash only once.

   - bpo-22958(32): Constructor and update method of
     weakref.WeakValueDictionary now accept the self and the dict
     keyword arguments.

   - bpo-22609(33): Constructor of collections.UserDict now accepts the
     self keyword argument.

   - bpo-25111(34): Fixed comparison of traceback.FrameSummary.

   - bpo-25262(35): Added support for BINBYTES8 opcode in Python
     implementation of unpickler.  Highest 32 bits of 64-bit size for
     BINUNICODE8 and BINBYTES8 opcodes no longer silently ignored on
     32-bit platforms in C implementation.

   - bpo-25034(36): Fix string.Formatter problem with auto-numbering and
     nested format_specs.  Patch by Anthon van der Neut.

   - bpo-25233(37): Rewrite the guts of asyncio.Queue and
     asyncio.Semaphore to be more understandable and correct.

   - bpo-25203(38): Failed readline.set_completer_delims() no longer
     left the module in inconsistent state.

   - bpo-23600(39): Default implementation of tzinfo.fromutc() was
     returning wrong results in some cases.

   - bpo-23329(40): Allow the ssl module to be built with older versions
     of LibreSSL.

   - Prevent overflow in _Unpickler_Read.

   - bpo-25047(41): The XML encoding declaration written by Element Tree
     now respects the letter case given by the user.  This restores the
     ability to write encoding names in uppercase like "UTF-8", which
     worked in Python 2.

   - bpo-25135(42): Make deque_clear() safer by emptying the deque
     before clearing.  This helps avoid possible reentrancy issues.

   - bpo-19143(43): platform module now reads Windows version from
     kernel32.dll to avoid compatibility shims.

   - bpo-25092(44): Fix datetime.strftime() failure when errno was
     already set to EINVAL.

   - bpo-23517(45): Fix rounding in fromtimestamp() and
     utcfromtimestamp() methods of datetime.datetime: microseconds are
     now rounded to nearest with ties going to nearest even integer
     (ROUND_HALF_EVEN), instead of being rounding towards minus infinity
     (ROUND_FLOOR). It's important that these methods use the same
     rounding mode than datetime.timedelta to keep the property:
     (datetime(1970,1,1) + timedelta(seconds=t)) ==
     datetime.utcfromtimestamp(t).  It also the rounding mode used by
     round(float) for example.

   - bpo-25155(46): Fix datetime.datetime.now() and
     datetime.datetime.utcnow() on Windows to support date after year
     2038.  It was a regression introduced in Python 3.5.0.

   - bpo-25108(47): Omitted internal frames in traceback functions
     print_stack(), format_stack(), and extract_stack() called without
     arguments.

   - bpo-25118(48): Fix a regression of Python 3.5.0 in os.waitpid() on
     Windows.

   - bpo-24684(49): socket.socket.getaddrinfo() now calls
     PyUnicode_AsEncodedString() instead of calling the encode() method
     of the host, to handle correctly custom string with an encode()
     method which doesn't return a byte string.  The encoder of the IDNA
     codec is now called directly instead of calling the encode() method
     of the string.

   - bpo-25060(50): Correctly compute stack usage of the BUILD_MAP
     opcode.

   - bpo-24857(51): Comparing call_args to a long sequence now correctly
     returns a boolean result instead of raising an exception.  Patch by
     A Kaptur.

   - bpo-23144(52): Make sure that HTMLParser.feed() returns all the
     data, even when convert_charrefs is True.

   - bpo-24982(53): shutil.make_archive() with the "zip" format now adds
     entries for directories (including empty directories) in ZIP file.

   - bpo-25019(54): Fixed a crash caused by setting non-string key of
     expat parser.  Based on patch by John Leitch.

   - bpo-16180(55): Exit pdb if file has syntax error, instead of
     trapping user in an infinite loop.  Patch by Xavier de Gaye.

   - bpo-24891(56): Fix a race condition at Python startup if the file
     descriptor of stdin (0), stdout (1) or stderr (2) is closed while
     Python is creating sys.stdin, sys.stdout and sys.stderr objects.
     These attributes are now set to None if the creation of the object
     failed, instead of raising an OSError exception.  Initial patch
     written by Marco Paolini.

   - bpo-24992(57): Fix error handling and a race condition (related to
     garbage collection) in collections.OrderedDict constructor.

   - bpo-24881(58): Fixed setting binary mode in Python implementation
     of FileIO on Windows and Cygwin.  Patch from Akira Li.

   - bpo-25578(59): Fix (another) memory leak in SSLSocket.getpeercer().

   - bpo-25530(60): Disable the vulnerable SSLv3 protocol by default
     when creating ssl.SSLContext.

   - bpo-25569(61): Fix memory leak in SSLSocket.getpeercert().

   - bpo-25471(62): Sockets returned from accept() shouldn't appear to
     be nonblocking.

   - bpo-25319(63): When threading.Event is reinitialized, the
     underlying condition should use a regular lock rather than a
     recursive lock.

   - bpo-21112(64): Fix regression in unittest.expectedFailure on
     subclasses.  Patch from Berker Peksag.

   - bpo-24764(65): cgi.FieldStorage.read_multi() now ignores the
     Content-Length header in part headers.  Patch written by Peter
     Landry and reviewed by Pierre Quentel.

   - bpo-24913(66): Fix overrun error in deque.index().  Found by John
     Leitch and Bryce Darling.

   - bpo-24774(67): Fix docstring in http.server.test.  Patch from
     Chiu-Hsiang Hsu.

   - bpo-21159(68): Improve message in
     configparser.InterpolationMissingOptionError.  Patch from Łukasz
     Langa.

   - bpo-20362(69): Honour TestCase.longMessage correctly in
     assertRegex.  Patch from Ilia Kurenkov.

   - bpo-23572(70): Fixed functools.singledispatch on classes with false
     metaclasses.  Patch by Ethan Furman.

   - asyncio: ensure_future() now accepts awaitable objects.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25626

   (2) https://bugs.python.org/issue?@action=redirect&bpo=25583

   (3) https://bugs.python.org/issue?@action=redirect&bpo=25593

   (4) https://bugs.python.org/issue?@action=redirect&bpo=6973

   (5) https://bugs.python.org/issue?@action=redirect&bpo=25590

   (6) https://bugs.python.org/issue?@action=redirect&bpo=25498

   (7) https://bugs.python.org/issue?@action=redirect&bpo=25584

   (8) https://bugs.python.org/issue?@action=redirect&bpo=25584

   (9) https://bugs.python.org/issue?@action=redirect&bpo=25446

   (10) https://bugs.python.org/issue?@action=redirect&bpo=18010

   (11) https://bugs.python.org/issue?@action=redirect&bpo=25554

   (12) https://bugs.python.org/issue?@action=redirect&bpo=25510

   (13) https://bugs.python.org/issue?@action=redirect&bpo=25503

   (14) https://bugs.python.org/issue?@action=redirect&bpo=25515

   (15) https://bugs.python.org/issue?@action=redirect&bpo=21827

   (16) https://bugs.python.org/issue?@action=redirect&bpo=25447

   (17) https://bugs.python.org/issue?@action=redirect&bpo=25390

   (18) https://bugs.python.org/issue?@action=redirect&bpo=25441

   (19) https://bugs.python.org/issue?@action=redirect&bpo=25410

   (20) https://bugs.python.org/issue?@action=redirect&bpo=25411

   (21) https://bugs.python.org/issue?@action=redirect&bpo=25407

   (22) https://bugs.python.org/issue?@action=redirect&bpo=25406

   (23) https://bugs.python.org/issue?@action=redirect&bpo=25364

   (24) https://bugs.python.org/issue?@action=redirect&bpo=25328

   (25) https://bugs.python.org/issue?@action=redirect&bpo=25316

   (26) https://bugs.python.org/issue?@action=redirect&bpo=25380

   (27) https://bugs.python.org/issue?@action=redirect&bpo=23972

   (28) https://bugs.python.org/issue?@action=redirect&bpo=25304

   (29) https://bugs.python.org/issue?@action=redirect&bpo=25232

   (30) https://bugs.python.org/issue?@action=redirect&bpo=24657

   (31) https://bugs.python.org/issue?@action=redirect&bpo=24483

   (32) https://bugs.python.org/issue?@action=redirect&bpo=22958

   (33) https://bugs.python.org/issue?@action=redirect&bpo=22609

   (34) https://bugs.python.org/issue?@action=redirect&bpo=25111

   (35) https://bugs.python.org/issue?@action=redirect&bpo=25262

   (36) https://bugs.python.org/issue?@action=redirect&bpo=25034

   (37) https://bugs.python.org/issue?@action=redirect&bpo=25233

   (38) https://bugs.python.org/issue?@action=redirect&bpo=25203

   (39) https://bugs.python.org/issue?@action=redirect&bpo=23600

   (40) https://bugs.python.org/issue?@action=redirect&bpo=23329

   (41) https://bugs.python.org/issue?@action=redirect&bpo=25047

   (42) https://bugs.python.org/issue?@action=redirect&bpo=25135

   (43) https://bugs.python.org/issue?@action=redirect&bpo=19143

   (44) https://bugs.python.org/issue?@action=redirect&bpo=25092

   (45) https://bugs.python.org/issue?@action=redirect&bpo=23517

   (46) https://bugs.python.org/issue?@action=redirect&bpo=25155

   (47) https://bugs.python.org/issue?@action=redirect&bpo=25108

   (48) https://bugs.python.org/issue?@action=redirect&bpo=25118

   (49) https://bugs.python.org/issue?@action=redirect&bpo=24684

   (50) https://bugs.python.org/issue?@action=redirect&bpo=25060

   (51) https://bugs.python.org/issue?@action=redirect&bpo=24857

   (52) https://bugs.python.org/issue?@action=redirect&bpo=23144

   (53) https://bugs.python.org/issue?@action=redirect&bpo=24982

   (54) https://bugs.python.org/issue?@action=redirect&bpo=25019

   (55) https://bugs.python.org/issue?@action=redirect&bpo=16180

   (56) https://bugs.python.org/issue?@action=redirect&bpo=24891

   (57) https://bugs.python.org/issue?@action=redirect&bpo=24992

   (58) https://bugs.python.org/issue?@action=redirect&bpo=24881

   (59) https://bugs.python.org/issue?@action=redirect&bpo=25578

   (60) https://bugs.python.org/issue?@action=redirect&bpo=25530

   (61) https://bugs.python.org/issue?@action=redirect&bpo=25569

   (62) https://bugs.python.org/issue?@action=redirect&bpo=25471

   (63) https://bugs.python.org/issue?@action=redirect&bpo=25319

   (64) https://bugs.python.org/issue?@action=redirect&bpo=21112

   (65) https://bugs.python.org/issue?@action=redirect&bpo=24764

   (66) https://bugs.python.org/issue?@action=redirect&bpo=24913

   (67) https://bugs.python.org/issue?@action=redirect&bpo=24774

   (68) https://bugs.python.org/issue?@action=redirect&bpo=21159

   (69) https://bugs.python.org/issue?@action=redirect&bpo=20362

   (70) https://bugs.python.org/issue?@action=redirect&bpo=23572


File: python.info,  Node: IDLE<58>,  Next: Documentation<68>,  Prev: Library<81>,  Up: Python 3 5 1 release candidate 1

1.23.94.3 IDLE
..............

   - bpo-15348(1): Stop the debugger engine (normally in a user process)
     before closing the debugger window (running in the IDLE process).
     This prevents the RuntimeErrors that were being caught and ignored.

   - bpo-24455(2): Prevent IDLE from hanging when a) closing the shell
     while the debugger is active (15347); b) closing the debugger with
     the [X] button (15348); and c) activating the debugger when already
     active (24455).  The patch by Mark Roseman does this by making two
     changes.  1.  Suspend and resume the gui.interaction method with
     the tcl vwait mechanism intended for this purpose (instead of
     root.mainloop & .quit).  2.  In gui.run, allow any existing
     interaction to terminate first.

   - Change 'The program' to 'Your program' in an IDLE 'kill program?'
     message to make it clearer that the program referred to is the
     currently running user program, not IDLE itself.

   - bpo-24750(3): Improve the appearance of the IDLE editor window
     status bar.  Patch by Mark Roseman.

   - bpo-25313(4): Change the handling of new built-in text color themes
     to better address the compatibility problem introduced by the
     addition of IDLE Dark.  Consistently use the revised
     idleConf.CurrentTheme everywhere in idlelib.

   - bpo-24782(5): Extension configuration is now a tab in the IDLE
     Preferences dialog rather than a separate dialog.  The former tabs
     are now a sorted list.  Patch by Mark Roseman.

   - bpo-22726(6): Re-activate the config dialog help button with some
     content about the other buttons and the new IDLE Dark theme.

   - bpo-24820(7): IDLE now has an 'IDLE Dark' built-in text color
     theme.  It is more or less IDLE Classic inverted, with a cobalt
     blue background.  Strings, comments, keywords, ...  are still
     green, red, orange, ...  .  To use it with IDLEs released before
     November 2015, hit the 'Save as New Custom Theme' button and enter
     a new name, such as 'Custom Dark'.  The custom theme will work with
     any IDLE release, and can be modified.

   - bpo-25224(8): README.txt is now an idlelib index for IDLE
     developers and curious users.  The previous user content is now in
     the IDLE doc chapter.  'IDLE' now means 'Integrated Development and
     Learning Environment'.

   - bpo-24820(9): Users can now set breakpoint colors in Settings ->
     Custom Highlighting.  Original patch by Mark Roseman.

   - bpo-24972(10): Inactive selection background now matches active
     selection background, as configured by users, on all systems.
     Found items are now always highlighted on Windows.  Initial patch
     by Mark Roseman.

   - bpo-24570(11): Idle: make calltip and completion boxes appear on
     Macs affected by a tk regression.  Initial patch by Mark Roseman.

   - bpo-24988(12): Idle ScrolledList context menus (used in debugger)
     now work on Mac Aqua.  Patch by Mark Roseman.

   - bpo-24801(13): Make right-click for context menu work on Mac Aqua.
     Patch by Mark Roseman.

   - bpo-25173(14): Associate tkinter messageboxes with a specific
     widget.  For Mac OSX, make them a 'sheet'.  Patch by Mark Roseman.

   - bpo-25198(15): Enhance the initial html viewer now used for Idle
     Help.  Properly indent fixed-pitch text (patch by Mark Roseman).
     Give code snippet a very Sphinx-like light blueish-gray background.
     Re-use initial width and height set by users for shell and editor.
     When the Table of Contents (TOC) menu is used, put the section
     header at the top of the screen.

   - bpo-25225(16): Condense and rewrite Idle doc section on text
     colors.

   - bpo-21995(17): Explain some differences between IDLE and console
     Python.

   - bpo-22820(18): Explain need for 'print' when running file from Idle
     editor.

   - bpo-25224(19): Doc: augment Idle feature list and no-subprocess
     section.

   - bpo-25219(20): Update doc for Idle command line options.  Some were
     missing and notes were not correct.

   - bpo-24861(21): Most of idlelib is private and subject to change.
     Use idleib.idle.* to start Idle.  See idlelib.__init__.__doc__.

   - bpo-25199(22): Idle: add synchronization comments for future
     maintainers.

   - bpo-16893(23): Replace help.txt with help.html for Idle doc
     display.  The new idlelib/help.html is rstripped
     Doc/build/html/library/idle.html.  It looks better than help.txt
     and will better document Idle as released.  The tkinter html viewer
     that works for this file was written by Mark Roseman.  The now
     unused EditorWindow.HelpDialog class and helt.txt file are
     deprecated.

   - bpo-24199(24): Deprecate unused idlelib.idlever with possible
     removal in 3.6.

   - bpo-24790(25): Remove extraneous code (which also create 2 & 3
     conflicts).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=15348

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24455

   (3) https://bugs.python.org/issue?@action=redirect&bpo=24750

   (4) https://bugs.python.org/issue?@action=redirect&bpo=25313

   (5) https://bugs.python.org/issue?@action=redirect&bpo=24782

   (6) https://bugs.python.org/issue?@action=redirect&bpo=22726

   (7) https://bugs.python.org/issue?@action=redirect&bpo=24820

   (8) https://bugs.python.org/issue?@action=redirect&bpo=25224

   (9) https://bugs.python.org/issue?@action=redirect&bpo=24820

   (10) https://bugs.python.org/issue?@action=redirect&bpo=24972

   (11) https://bugs.python.org/issue?@action=redirect&bpo=24570

   (12) https://bugs.python.org/issue?@action=redirect&bpo=24988

   (13) https://bugs.python.org/issue?@action=redirect&bpo=24801

   (14) https://bugs.python.org/issue?@action=redirect&bpo=25173

   (15) https://bugs.python.org/issue?@action=redirect&bpo=25198

   (16) https://bugs.python.org/issue?@action=redirect&bpo=25225

   (17) https://bugs.python.org/issue?@action=redirect&bpo=21995

   (18) https://bugs.python.org/issue?@action=redirect&bpo=22820

   (19) https://bugs.python.org/issue?@action=redirect&bpo=25224

   (20) https://bugs.python.org/issue?@action=redirect&bpo=25219

   (21) https://bugs.python.org/issue?@action=redirect&bpo=24861

   (22) https://bugs.python.org/issue?@action=redirect&bpo=25199

   (23) https://bugs.python.org/issue?@action=redirect&bpo=16893

   (24) https://bugs.python.org/issue?@action=redirect&bpo=24199

   (25) https://bugs.python.org/issue?@action=redirect&bpo=24790


File: python.info,  Node: Documentation<68>,  Next: Tests<73>,  Prev: IDLE<58>,  Up: Python 3 5 1 release candidate 1

1.23.94.4 Documentation
.......................

   - bpo-22558(1): Add remaining doc links to source code for
     Python-coded modules.  Patch by Yoni Lavi.

   - bpo-12067(2): Rewrite Comparisons section in the Expressions
     chapter of the language reference.  Some of the details of
     comparing mixed types were incorrect or ambiguous.  NotImplemented
     is only relevant at a lower level than the Expressions chapter.
     Added details of comparing range() objects, and default behaviour
     and consistency suggestions for user-defined classes.  Patch from
     Andy Maier.

   - bpo-24952(3): Clarify the default size argument of stack_size() in
     the "threading" and "_thread" modules.  Patch from Mattip.

   - bpo-23725(4): Overhaul tempfile docs.  Note deprecated status of
     mktemp.  Patch from Zbigniew Jędrzejewski-Szmek.

   - bpo-24808(5): Update the types of some PyTypeObject fields.  Patch
     by Joseph Weston.

   - bpo-22812(6): Fix unittest discovery examples.  Patch from Pam
     McA'Nulty.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22558

   (2) https://bugs.python.org/issue?@action=redirect&bpo=12067

   (3) https://bugs.python.org/issue?@action=redirect&bpo=24952

   (4) https://bugs.python.org/issue?@action=redirect&bpo=23725

   (5) https://bugs.python.org/issue?@action=redirect&bpo=24808

   (6) https://bugs.python.org/issue?@action=redirect&bpo=22812


File: python.info,  Node: Tests<73>,  Next: Build<78>,  Prev: Documentation<68>,  Up: Python 3 5 1 release candidate 1

1.23.94.5 Tests
...............

   - bpo-25449(1): Added tests for OrderedDict subclasses.

   - bpo-25099(2): Make test_compileall not fail when an entry on
     sys.path cannot be written to (commonly seen in administrative
     installs on Windows).

   - bpo-23919(3): Prevents assert dialogs appearing in the test suite.

   - ‘PCbuild\rt.bat’ now accepts an unlimited number of arguments to
     pass along to regrtest.py.  Previously there was a limit of 9.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25449

   (2) https://bugs.python.org/issue?@action=redirect&bpo=25099

   (3) https://bugs.python.org/issue?@action=redirect&bpo=23919


File: python.info,  Node: Build<78>,  Next: Windows<69>,  Prev: Tests<73>,  Up: Python 3 5 1 release candidate 1

1.23.94.6 Build
...............

   - bpo-24915(1): Add LLVM support for PGO builds and use the test
     suite to generate the profile data.  Initial patch by Alecsandru
     Patrascu of Intel.

   - bpo-24910(2): Windows MSIs now have unique display names.

   - bpo-24986(3): It is now possible to build Python on Windows without
     errors when external libraries are not available.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24915

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24910

   (3) https://bugs.python.org/issue?@action=redirect&bpo=24986


File: python.info,  Node: Windows<69>,  Next: Tools/Demos<43>,  Prev: Build<78>,  Up: Python 3 5 1 release candidate 1

1.23.94.7 Windows
.................

   - bpo-25450(1): Updates shortcuts to start Python in installation
     directory.

   - bpo-25164(2): Changes default all-users install directory to match
     per-user directory.

   - bpo-25143(3): Improves installer error messages for unsupported
     platforms.

   - bpo-25163(4): Display correct directory in installer when using
     non-default settings.

   - bpo-25361(5): Disables use of SSE2 instructions in Windows 32-bit
     build

   - bpo-25089(6): Adds logging to installer for case where launcher is
     not selected on upgrade.

   - bpo-25165(7): Windows uninstallation should not remove launcher if
     other versions remain

   - bpo-25112(8): py.exe launcher is missing icons

   - bpo-25102(9): Windows installer does not precompile for -O or -OO.

   - bpo-25081(10): Makes Back button in installer go back to upgrade
     page when upgrading.

   - bpo-25091(11): Increases font size of the installer.

   - bpo-25126(12): Clarifies that the non-web installer will download
     some components.

   - bpo-25213(13): Restores requestedExecutionLevel to manifest to
     disable UAC virtualization.

   - bpo-25022(14): Removed very outdated PC/example_nt/ directory.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25450

   (2) https://bugs.python.org/issue?@action=redirect&bpo=25164

   (3) https://bugs.python.org/issue?@action=redirect&bpo=25143

   (4) https://bugs.python.org/issue?@action=redirect&bpo=25163

   (5) https://bugs.python.org/issue?@action=redirect&bpo=25361

   (6) https://bugs.python.org/issue?@action=redirect&bpo=25089

   (7) https://bugs.python.org/issue?@action=redirect&bpo=25165

   (8) https://bugs.python.org/issue?@action=redirect&bpo=25112

   (9) https://bugs.python.org/issue?@action=redirect&bpo=25102

   (10) https://bugs.python.org/issue?@action=redirect&bpo=25081

   (11) https://bugs.python.org/issue?@action=redirect&bpo=25091

   (12) https://bugs.python.org/issue?@action=redirect&bpo=25126

   (13) https://bugs.python.org/issue?@action=redirect&bpo=25213

   (14) https://bugs.python.org/issue?@action=redirect&bpo=25022


File: python.info,  Node: Tools/Demos<43>,  Prev: Windows<69>,  Up: Python 3 5 1 release candidate 1

1.23.94.8 Tools/Demos
.....................

   - bpo-25440(1): Fix output of python-config -extension-suffix.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25440


File: python.info,  Node: Python 3 5 0 final,  Next: Python 3 5 0 release candidate 4,  Prev: Python 3 5 1 release candidate 1,  Up: Changelog（更動日誌）

1.23.95 Python 3.5.0 final
--------------------------

'Release date: 2015-09-13'

* Menu:

* Build: Build<79>.


File: python.info,  Node: Build<79>,  Up: Python 3 5 0 final

1.23.95.1 Build
...............

   - bpo-25071(1): Windows installer should not require TargetDir
     parameter when installing quietly.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25071


File: python.info,  Node: Python 3 5 0 release candidate 4,  Next: Python 3 5 0 release candidate 3,  Prev: Python 3 5 0 final,  Up: Changelog（更動日誌）

1.23.96 Python 3.5.0 release candidate 4
----------------------------------------

'Release date: 2015-09-09'

* Menu:

* Library: Library<82>.
* Build: Build<80>.


File: python.info,  Node: Library<82>,  Next: Build<80>,  Up: Python 3 5 0 release candidate 4

1.23.96.1 Library
.................

   - bpo-25029(1): Fixes MemoryError in test_strptime.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25029


File: python.info,  Node: Build<80>,  Prev: Library<82>,  Up: Python 3 5 0 release candidate 4

1.23.96.2 Build
...............

   - bpo-25027(1): Reverts partial-static build options and adds
     vcruntime140.dll to Windows installation.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=25027


File: python.info,  Node: Python 3 5 0 release candidate 3,  Next: Python 3 5 0 release candidate 2,  Prev: Python 3 5 0 release candidate 4,  Up: Changelog（更動日誌）

1.23.97 Python 3.5.0 release candidate 3
----------------------------------------

'Release date: 2015-09-07'

* Menu:

* Core and Builtins: Core and Builtins<84>.
* Library: Library<83>.


File: python.info,  Node: Core and Builtins<84>,  Next: Library<83>,  Up: Python 3 5 0 release candidate 3

1.23.97.1 Core and Builtins
...........................

   - bpo-24305(1): Prevent import subsystem stack frames from being
     counted by the warnings.warn(stacklevel=) parameter.

   - bpo-24912(2): Prevent __class__ assignment to immutable built-in
     objects.

   - bpo-24975(3): Fix AST compilation for PEP 448(4) syntax.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24305

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24912

   (3) https://bugs.python.org/issue?@action=redirect&bpo=24975

   (4) https://peps.python.org/pep-0448/


File: python.info,  Node: Library<83>,  Prev: Core and Builtins<84>,  Up: Python 3 5 0 release candidate 3

1.23.97.2 Library
.................

   - bpo-24917(1): time_strftime() buffer over-read.

   - bpo-24748(2): To resolve a compatibility problem found with py2exe
     and pywin32, imp.load_dynamic() once again ignores previously
     loaded modules to support Python modules replacing themselves with
     extension modules.  Patch by Petr Viktorin.

   - bpo-24635(3): Fixed a bug in typing.py where isinstance([],
     typing.Iterable) would return True once, then False on subsequent
     calls.

   - bpo-24989(4): Fixed buffer overread in BytesIO.readline() if a
     position is set beyond size.  Based on patch by John Leitch.

   - bpo-24913(5): Fix overrun error in deque.index().  Found by John
     Leitch and Bryce Darling.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24917

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24748

   (3) https://bugs.python.org/issue?@action=redirect&bpo=24635

   (4) https://bugs.python.org/issue?@action=redirect&bpo=24989

   (5) https://bugs.python.org/issue?@action=redirect&bpo=24913


File: python.info,  Node: Python 3 5 0 release candidate 2,  Next: Python 3 5 0 release candidate 1,  Prev: Python 3 5 0 release candidate 3,  Up: Changelog（更動日誌）

1.23.98 Python 3.5.0 release candidate 2
----------------------------------------

'Release date: 2015-08-25'

* Menu:

* Core and Builtins: Core and Builtins<85>.
* Library: Library<84>.


File: python.info,  Node: Core and Builtins<85>,  Next: Library<84>,  Up: Python 3 5 0 release candidate 2

1.23.98.1 Core and Builtins
...........................

   - bpo-24769(1): Interpreter now starts properly when dynamic loading
     is disabled.  Patch by Petr Viktorin.

   - bpo-21167(2): NAN operations are now handled correctly when python
     is compiled with ICC even if -fp-model strict is not specified.

   - bpo-24492(3): A "package" lacking a __name__ attribute when trying
     to perform a ‘from .. import ...’ statement will trigger an
     ImportError instead of an AttributeError.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24769

   (2) https://bugs.python.org/issue?@action=redirect&bpo=21167

   (3) https://bugs.python.org/issue?@action=redirect&bpo=24492


File: python.info,  Node: Library<84>,  Prev: Core and Builtins<85>,  Up: Python 3 5 0 release candidate 2

1.23.98.2 Library
.................

   - bpo-24847(1): Removes vcruntime140.dll dependency from Tcl/Tk.

   - bpo-24839(2): platform._syscmd_ver raises DeprecationWarning

   - bpo-24867(3): Fix Task.get_stack() for 'async def' coroutines

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24847

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24839

   (3) https://bugs.python.org/issue?@action=redirect&bpo=24867


File: python.info,  Node: Python 3 5 0 release candidate 1,  Next: Python 3 5 0 beta 4,  Prev: Python 3 5 0 release candidate 2,  Up: Changelog（更動日誌）

1.23.99 Python 3.5.0 release candidate 1
----------------------------------------

'Release date: 2015-08-09'

* Menu:

* Core and Builtins: Core and Builtins<86>.
* Library: Library<85>.
* IDLE: IDLE<59>.
* Documentation: Documentation<69>.
* Tests: Tests<74>.


File: python.info,  Node: Core and Builtins<86>,  Next: Library<85>,  Up: Python 3 5 0 release candidate 1

1.23.99.1 Core and Builtins
...........................

   - bpo-24667(1): Resize odict in all cases that the underlying dict
     resizes.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24667


File: python.info,  Node: Library<85>,  Next: IDLE<59>,  Prev: Core and Builtins<86>,  Up: Python 3 5 0 release candidate 1

1.23.99.2 Library
.................

   - bpo-24824(1): Signatures of codecs.encode() and codecs.decode() now
     are compatible with pydoc.

   - bpo-24634(2): Importing uuid should not try to load libc on Windows

   - bpo-24798(3): _msvccompiler.py doesn't properly support manifests

   - bpo-4395(4): Better testing and documentation of binary operators.
     Patch by Martin Panter.

   - bpo-23973(5): Update typing.py from GitHub repo.

   - bpo-23004(6): mock_open() now reads binary data correctly when the
     type of read_data is bytes.  Initial patch by Aaron Hill.

   - bpo-23888(7): Handle fractional time in cookie expiry.  Patch by
     ssh.

   - bpo-23652(8): Make it possible to compile the select module against
     the libc headers from the Linux Standard Base, which do not include
     some EPOLL macros.  Patch by Matt Frank.

   - bpo-22932(9): Fix timezones in email.utils.formatdate.  Patch from
     Dmitry Shachnev.

   - bpo-23779(10): imaplib raises TypeError if authenticator tries to
     abort.  Patch from Craig Holmquist.

   - bpo-23319(11): Fix ctypes.BigEndianStructure, swap correctly bytes.
     Patch written by Matthieu Gautier.

   - bpo-23254(12): Document how to close the TCPServer listening
     socket.  Patch from Martin Panter.

   - bpo-19450(13): Update Windows and OS X installer builds to use
     SQLite 3.8.11.

   - bpo-17527(14): Add PATCH to wsgiref.validator.  Patch from Luca
     Sbardella.

   - bpo-24791(15): Fix grammar regression for call syntax: 'g(*a or
     b)'.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24824

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24634

   (3) https://bugs.python.org/issue?@action=redirect&bpo=24798

   (4) https://bugs.python.org/issue?@action=redirect&bpo=4395

   (5) https://bugs.python.org/issue?@action=redirect&bpo=23973

   (6) https://bugs.python.org/issue?@action=redirect&bpo=23004

   (7) https://bugs.python.org/issue?@action=redirect&bpo=23888

   (8) https://bugs.python.org/issue?@action=redirect&bpo=23652

   (9) https://bugs.python.org/issue?@action=redirect&bpo=22932

   (10) https://bugs.python.org/issue?@action=redirect&bpo=23779

   (11) https://bugs.python.org/issue?@action=redirect&bpo=23319

   (12) https://bugs.python.org/issue?@action=redirect&bpo=23254

   (13) https://bugs.python.org/issue?@action=redirect&bpo=19450

   (14) https://bugs.python.org/issue?@action=redirect&bpo=17527

   (15) https://bugs.python.org/issue?@action=redirect&bpo=24791


File: python.info,  Node: IDLE<59>,  Next: Documentation<69>,  Prev: Library<85>,  Up: Python 3 5 0 release candidate 1

1.23.99.3 IDLE
..............

   - bpo-23672(1): Allow Idle to edit and run files with astral chars in
     name.  Patch by Mohd Sanad Zaki Rizvi.

   - bpo-24745(2): Idle editor default font.  Switch from Courier to
     platform-sensitive TkFixedFont.  This should not affect current
     customized font selections.  If there is a problem, edit
     $HOME/.idlerc/config-main.cfg and remove '‘fontXXX’' entries from
     [Editor Window].  Patch by Mark Roseman.

   - bpo-21192(3): Idle editor.  When a file is run, put its name in the
     restart bar.  Do not print false prompts.  Original patch by Adnan
     Umer.

   - bpo-13884(4): Idle menus.  Remove tearoff lines.  Patch by Roger
     Serwy.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23672

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24745

   (3) https://bugs.python.org/issue?@action=redirect&bpo=21192

   (4) https://bugs.python.org/issue?@action=redirect&bpo=13884


File: python.info,  Node: Documentation<69>,  Next: Tests<74>,  Prev: IDLE<59>,  Up: Python 3 5 0 release candidate 1

1.23.99.4 Documentation
.......................

   - bpo-24129(1): Clarify the reference documentation for name
     resolution.  This includes removing the assumption that readers
     will be familiar with the name resolution scheme Python used prior
     to the introduction of lexical scoping for function namespaces.
     Patch by Ivan Levkivskyi.

   - bpo-20769(2): Improve reload() docs.  Patch by Dorian Pula.

   - bpo-23589(3): Remove duplicate sentence from the FAQ. Patch by
     Yongzhi Pan.

   - bpo-24729(4): Correct IO tutorial to match implementation regarding
     encoding parameter to open function.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24129

   (2) https://bugs.python.org/issue?@action=redirect&bpo=20769

   (3) https://bugs.python.org/issue?@action=redirect&bpo=23589

   (4) https://bugs.python.org/issue?@action=redirect&bpo=24729


File: python.info,  Node: Tests<74>,  Prev: Documentation<69>,  Up: Python 3 5 0 release candidate 1

1.23.99.5 Tests
...............

   - bpo-24751(1): When running regrtest with the ‘-w’ command line
     option, a test run is no longer marked as a failure if all tests
     succeed when re-run.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24751


File: python.info,  Node: Python 3 5 0 beta 4,  Next: Python 3 5 0 beta 3,  Prev: Python 3 5 0 release candidate 1,  Up: Changelog（更動日誌）

1.23.100 Python 3.5.0 beta 4
----------------------------

'Release date: 2015-07-26'

* Menu:

* Core and Builtins: Core and Builtins<87>.
* Library: Library<86>.
* Build: Build<81>.


File: python.info,  Node: Core and Builtins<87>,  Next: Library<86>,  Up: Python 3 5 0 beta 4

1.23.100.1 Core and Builtins
............................

   - bpo-23573(1): Restored optimization of bytes.rfind() and
     bytearray.rfind() for single-byte argument on Linux.

   - bpo-24569(2): Make PEP 448(3) dictionary evaluation more
     consistent.

   - bpo-24583(4): Fix crash when set is mutated while being updated.

   - bpo-24407(5): Fix crash when dict is mutated while being updated.

   - bpo-24619(6): New approach for tokenizing async/await.  As a
     consequence, it is now possible to have one-line 'async def foo():
     await ..'  functions.

   - bpo-24687(7): Plug refleak on SyntaxError in function parameters
     annotations.

   - bpo-15944(8): memoryview: Allow arbitrary formats when casting to
     bytes.  Patch by Martin Panter.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23573

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24569

   (3) https://peps.python.org/pep-0448/

   (4) https://bugs.python.org/issue?@action=redirect&bpo=24583

   (5) https://bugs.python.org/issue?@action=redirect&bpo=24407

   (6) https://bugs.python.org/issue?@action=redirect&bpo=24619

   (7) https://bugs.python.org/issue?@action=redirect&bpo=24687

   (8) https://bugs.python.org/issue?@action=redirect&bpo=15944


File: python.info,  Node: Library<86>,  Next: Build<81>,  Prev: Core and Builtins<87>,  Up: Python 3 5 0 beta 4

1.23.100.2 Library
..................

   - bpo-23441(1): rcompleter now prints a tab character instead of
     displaying possible completions for an empty word.  Initial patch
     by Martin Sekera.

   - bpo-24683(2): Fixed crashes in _json functions called with
     arguments of inappropriate type.

   - bpo-21697(3): shutil.copytree() now correctly handles symbolic
     links that point to directories.  Patch by Eduardo Seabra and
     Thomas Kluyver.

   - bpo-14373(4): Fixed segmentation fault when gc.collect() is called
     during constructing lru_cache (C implementation).

   - bpo-24695(5): Fix a regression in traceback.print_exception().  If
     exc_traceback is None we shouldn't print a traceback header like
     described in the documentation.

   - bpo-24620(6): Random.setstate() now validates the value of state
     last element.

   - bpo-22485(7): Fixed an issue that caused ‘inspect.getsource’ to
     return incorrect results on nested functions.

   - bpo-22153(8): Improve unittest docs.  Patch from Martin Panter and
     evilzero.

   - bpo-24580(9): Symbolic group references to open group in re
     patterns now are explicitly forbidden as well as numeric group
     references.

   - bpo-24206(10): Fixed __eq__ and __ne__ methods of inspect classes.

   - bpo-24631(11): Fixed regression in the timeit module with multiline
     setup.

   - bpo-18622(12): unittest.mock.mock_open().reset_mock would recurse
     infinitely.  Patch from Nicola Palumbo and Laurent De Buyst.

   - bpo-23661(13): unittest.mock side_effects can now be exceptions
     again.  This was a regression vs Python 3.4.  Patch from Ignacio
     Rossi

   - bpo-24608(14): chunk.Chunk.read() now always returns bytes, not
     str.

   - bpo-18684(15): Fixed reading out of the buffer in the re module.

   - bpo-24259(16): tarfile now raises a ReadError if an archive is
     truncated inside a data segment.

   - bpo-15014(17): SMTP.auth() and SMTP.login() now support RFC 4954's
     optional initial-response argument to the SMTP AUTH command.

   - bpo-24669(18): Fix inspect.getsource() for 'async def' functions.
     Patch by Kai Groner.

   - bpo-24688(19): ast.get_docstring() for 'async def' functions.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23441

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24683

   (3) https://bugs.python.org/issue?@action=redirect&bpo=21697

   (4) https://bugs.python.org/issue?@action=redirect&bpo=14373

   (5) https://bugs.python.org/issue?@action=redirect&bpo=24695

   (6) https://bugs.python.org/issue?@action=redirect&bpo=24620

   (7) https://bugs.python.org/issue?@action=redirect&bpo=22485

   (8) https://bugs.python.org/issue?@action=redirect&bpo=22153

   (9) https://bugs.python.org/issue?@action=redirect&bpo=24580

   (10) https://bugs.python.org/issue?@action=redirect&bpo=24206

   (11) https://bugs.python.org/issue?@action=redirect&bpo=24631

   (12) https://bugs.python.org/issue?@action=redirect&bpo=18622

   (13) https://bugs.python.org/issue?@action=redirect&bpo=23661

   (14) https://bugs.python.org/issue?@action=redirect&bpo=24608

   (15) https://bugs.python.org/issue?@action=redirect&bpo=18684

   (16) https://bugs.python.org/issue?@action=redirect&bpo=24259

   (17) https://bugs.python.org/issue?@action=redirect&bpo=15014

   (18) https://bugs.python.org/issue?@action=redirect&bpo=24669

   (19) https://bugs.python.org/issue?@action=redirect&bpo=24688


File: python.info,  Node: Build<81>,  Prev: Library<86>,  Up: Python 3 5 0 beta 4

1.23.100.3 Build
................

   - bpo-24603(1): Update Windows builds and OS X 10.5 installer to use
     OpenSSL 1.0.2d.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24603


File: python.info,  Node: Python 3 5 0 beta 3,  Next: Python 3 5 0 beta 2,  Prev: Python 3 5 0 beta 4,  Up: Changelog（更動日誌）

1.23.101 Python 3.5.0 beta 3
----------------------------

'Release date: 2015-07-05'

* Menu:

* Core and Builtins: Core and Builtins<88>.
* Library: Library<87>.
* Tests: Tests<75>.
* Documentation: Documentation<70>.
* Build: Build<82>.


File: python.info,  Node: Core and Builtins<88>,  Next: Library<87>,  Up: Python 3 5 0 beta 3

1.23.101.1 Core and Builtins
............................

   - bpo-24467(1): Fixed possible buffer over-read in bytearray.  The
     bytearray object now always allocates place for trailing null byte
     and it's buffer now is always null-terminated.

   - Upgrade to Unicode 8.0.0.

   - bpo-24345(2): Add Py_tp_finalize slot for the stable ABI.

   - bpo-24400(3): Introduce a distinct type for PEP 492(4) coroutines;
     add types.CoroutineType, inspect.getcoroutinestate,
     inspect.getcoroutinelocals; coroutines no longer use CO_GENERATOR
     flag; sys.set_coroutine_wrapper works only for 'async def'
     coroutines; inspect.iscoroutine no longer uses
     collections.abc.Coroutine, it's intended to test for pure 'async
     def' coroutines only; add new opcode: GET_YIELD_FROM_ITER; fix
     generators wrapper used in types.coroutine to be instance of
     collections.abc.Generator; collections.abc.Awaitable and
     collections.abc.Coroutine can no longer be used to detect
     generator-based coroutines-use inspect.isawaitable instead.

   - bpo-24450(5): Add gi_yieldfrom to generators and cr_await to
     coroutines.  Contributed by Benno Leslie and Yury Selivanov.

   - bpo-19235(6): Add new RecursionError exception.  Patch by Georg
     Brandl.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24467

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24345

   (3) https://bugs.python.org/issue?@action=redirect&bpo=24400

   (4) https://peps.python.org/pep-0492/

   (5) https://bugs.python.org/issue?@action=redirect&bpo=24450

   (6) https://bugs.python.org/issue?@action=redirect&bpo=19235


File: python.info,  Node: Library<87>,  Next: Tests<75>,  Prev: Core and Builtins<88>,  Up: Python 3 5 0 beta 3

1.23.101.2 Library
..................

   - bpo-21750(1): mock_open.read_data can now be read from each
     instance, as it could in Python 3.3.

   - bpo-24552(2): Fix use after free in an error case of the _pickle
     module.

   - bpo-24514(3): tarfile now tolerates number fields consisting of
     only whitespace.

   - bpo-19176(4): Fixed doctype() related bugs in C implementation of
     ElementTree.  A deprecation warning no longer issued by XMLParser
     subclass with default doctype() method.  Direct call of doctype()
     now issues a warning.  Parser's doctype() now is not called if
     target's doctype() is called.  Based on patch by Martin Panter.

   - bpo-20387(5): Restore semantic round-trip correctness in
     tokenize/untokenize for tab-indented blocks.

   - bpo-24456(6): Fixed possible buffer over-read in adpcm2lin() and
     lin2adpcm() functions of the audioop module.

   - bpo-24336(7): The contextmanager decorator now works with functions
     with keyword arguments called "func" and "self".  Patch by Martin
     Panter.

   - bpo-24522(8): Fix possible integer overflow in json accelerator
     module.

   - bpo-24489(9): ensure a previously set C errno doesn't disturb
     cmath.polar().

   - bpo-24408(10): Fixed AttributeError in measure() and metrics()
     methods of tkinter.Font.

   - bpo-14373(11): C implementation of functools.lru_cache() now can be
     used with methods.

   - bpo-24347(12): Set KeyError if PyDict_GetItemWithError returns
     NULL.

   - bpo-24348(13): Drop superfluous incref/decref.

   - bpo-24359(14): Check for changed OrderedDict size during iteration.

   - bpo-24368(15): Support keyword arguments in OrderedDict methods.

   - bpo-24362(16): Simplify the C OrderedDict fast nodes resize logic.

   - bpo-24377(17): Fix a ref leak in OrderedDict.__repr__.

   - bpo-24369(18): Defend against key-changes during iteration.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21750

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24552

   (3) https://bugs.python.org/issue?@action=redirect&bpo=24514

   (4) https://bugs.python.org/issue?@action=redirect&bpo=19176

   (5) https://bugs.python.org/issue?@action=redirect&bpo=20387

   (6) https://bugs.python.org/issue?@action=redirect&bpo=24456

   (7) https://bugs.python.org/issue?@action=redirect&bpo=24336

   (8) https://bugs.python.org/issue?@action=redirect&bpo=24522

   (9) https://bugs.python.org/issue?@action=redirect&bpo=24489

   (10) https://bugs.python.org/issue?@action=redirect&bpo=24408

   (11) https://bugs.python.org/issue?@action=redirect&bpo=14373

   (12) https://bugs.python.org/issue?@action=redirect&bpo=24347

   (13) https://bugs.python.org/issue?@action=redirect&bpo=24348

   (14) https://bugs.python.org/issue?@action=redirect&bpo=24359

   (15) https://bugs.python.org/issue?@action=redirect&bpo=24368

   (16) https://bugs.python.org/issue?@action=redirect&bpo=24362

   (17) https://bugs.python.org/issue?@action=redirect&bpo=24377

   (18) https://bugs.python.org/issue?@action=redirect&bpo=24369


File: python.info,  Node: Tests<75>,  Next: Documentation<70>,  Prev: Library<87>,  Up: Python 3 5 0 beta 3

1.23.101.3 Tests
................

   - bpo-24373(1): _testmultiphase and xxlimited now use tp_traverse and
     tp_finalize to avoid reference leaks encountered when combining
     tp_dealloc with PyType_FromSpec (see bpo-16690(2) for details)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24373

   (2) https://bugs.python.org/issue?@action=redirect&bpo=16690


File: python.info,  Node: Documentation<70>,  Next: Build<82>,  Prev: Tests<75>,  Up: Python 3 5 0 beta 3

1.23.101.4 Documentation
........................

   - bpo-24458(1): Update documentation to cover multi-phase
     initialization for extension modules (PEP 489).  Patch by Petr
     Viktorin.

   - bpo-24351(2): Clarify what is meant by "identifier" in the context
     of string.Template instances.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24458

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24351


File: python.info,  Node: Build<82>,  Prev: Documentation<70>,  Up: Python 3 5 0 beta 3

1.23.101.5 Build
................

   - bpo-24432(1): Update Windows builds and OS X 10.5 installer to use
     OpenSSL 1.0.2c.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24432


File: python.info,  Node: Python 3 5 0 beta 2,  Next: Python 3 5 0 beta 1,  Prev: Python 3 5 0 beta 3,  Up: Changelog（更動日誌）

1.23.102 Python 3.5.0 beta 2
----------------------------

'Release date: 2015-05-31'

* Menu:

* Core and Builtins: Core and Builtins<89>.
* Library: Library<88>.


File: python.info,  Node: Core and Builtins<89>,  Next: Library<88>,  Up: Python 3 5 0 beta 2

1.23.102.1 Core and Builtins
............................

   - bpo-24284(1): The startswith and endswith methods of the str class
     no longer return True when finding the empty string and the indexes
     are completely out of range.

   - bpo-24115(2): Update uses of PyObject_IsTrue(), PyObject_Not(),
     PyObject_IsInstance(), PyObject_RichCompareBool() and
     _PyDict_Contains() to check for and handle errors correctly.

   - bpo-24328(3): Fix importing one character extension modules.

   - bpo-11205(4): In dictionary displays, evaluate the key before the
     value.

   - bpo-24285(5): Fixed regression that prevented importing extension
     modules from inside packages.  Patch by Petr Viktorin.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24284

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24115

   (3) https://bugs.python.org/issue?@action=redirect&bpo=24328

   (4) https://bugs.python.org/issue?@action=redirect&bpo=11205

   (5) https://bugs.python.org/issue?@action=redirect&bpo=24285


File: python.info,  Node: Library<88>,  Prev: Core and Builtins<89>,  Up: Python 3 5 0 beta 2

1.23.102.2 Library
..................

   - bpo-23247(1): Fix a crash in the StreamWriter.reset() of CJK
     codecs.

   - bpo-24270(2): Add math.isclose() and cmath.isclose() functions as
     per PEP 485(3).  Contributed by Chris Barker and Tal Einat.

   - bpo-5633(4): Fixed timeit when the statement is a string and the
     setup is not.

   - bpo-24326(5): Fixed audioop.ratecv() with non-default weightB
     argument.  Original patch by David Moore.

   - bpo-16991(6): Add a C implementation of OrderedDict.

   - bpo-23934(7): Fix inspect.signature to fail correctly for builtin
     types lacking signature information.  Initial patch by James
     Powell.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23247

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24270

   (3) https://peps.python.org/pep-0485/

   (4) https://bugs.python.org/issue?@action=redirect&bpo=5633

   (5) https://bugs.python.org/issue?@action=redirect&bpo=24326

   (6) https://bugs.python.org/issue?@action=redirect&bpo=16991

   (7) https://bugs.python.org/issue?@action=redirect&bpo=23934


File: python.info,  Node: Python 3 5 0 beta 1,  Next: Python 3 5 0 alpha 4,  Prev: Python 3 5 0 beta 2,  Up: Changelog（更動日誌）

1.23.103 Python 3.5.0 beta 1
----------------------------

'Release date: 2015-05-24'

* Menu:

* Core and Builtins: Core and Builtins<90>.
* Library: Library<89>.
* IDLE: IDLE<60>.
* Tests: Tests<76>.
* Documentation: Documentation<71>.
* Tools/Demos: Tools/Demos<44>.


File: python.info,  Node: Core and Builtins<90>,  Next: Library<89>,  Up: Python 3 5 0 beta 1

1.23.103.1 Core and Builtins
............................

   - bpo-24276(1): Fixed optimization of property descriptor getter.

   - bpo-24268(2): PEP 489: Multi-phase extension module initialization.
     Patch by Petr Viktorin.

   - bpo-23955(3): Add pyvenv.cfg option to suppress
     registry/environment lookup for generating sys.path on Windows.

   - bpo-24257(4): Fixed system error in the comparison of faked
     types.SimpleNamespace.

   - bpo-22939(5): Fixed integer overflow in iterator object.  Patch by
     Clement Rouault.

   - bpo-23985(6): Fix a possible buffer overrun when deleting a slice
     from the front of a bytearray and then appending some other bytes
     data.

   - bpo-24102(7): Fixed exception type checking in standard error
     handlers.

   - bpo-15027(8): The UTF-32 encoder is now 3x to 7x faster.

   - bpo-23290(9): Optimize set_merge() for cases where the target is
     empty.  (Contributed by Serhiy Storchaka.)

   - bpo-2292(10): PEP 448: Additional Unpacking Generalizations.

   - bpo-24096(11): Make warnings.warn_explicit more robust against
     mutation of the warnings.filters list.

   - bpo-23996(12): Avoid a crash when a delegated generator raises an
     unnormalized StopIteration exception.  Patch by Stefan Behnel.

   - bpo-23910(13): Optimize property() getter calls.  Patch by Joe
     Jevnik.

   - bpo-23911(14): Move path-based importlib bootstrap code to a
     separate frozen module.

   - bpo-24192(15): Fix namespace package imports.

   - bpo-24022(16): Fix tokenizer crash when processing undecodable
     source code.

   - bpo-9951(17): Added a hex() method to bytes, bytearray, and
     memoryview.

   - bpo-22906(18): PEP 479: Change StopIteration handling inside
     generators.

   - bpo-24017(19): PEP 492: Coroutines with async and await syntax.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24276

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24268

   (3) https://bugs.python.org/issue?@action=redirect&bpo=23955

   (4) https://bugs.python.org/issue?@action=redirect&bpo=24257

   (5) https://bugs.python.org/issue?@action=redirect&bpo=22939

   (6) https://bugs.python.org/issue?@action=redirect&bpo=23985

   (7) https://bugs.python.org/issue?@action=redirect&bpo=24102

   (8) https://bugs.python.org/issue?@action=redirect&bpo=15027

   (9) https://bugs.python.org/issue?@action=redirect&bpo=23290

   (10) https://bugs.python.org/issue?@action=redirect&bpo=2292

   (11) https://bugs.python.org/issue?@action=redirect&bpo=24096

   (12) https://bugs.python.org/issue?@action=redirect&bpo=23996

   (13) https://bugs.python.org/issue?@action=redirect&bpo=23910

   (14) https://bugs.python.org/issue?@action=redirect&bpo=23911

   (15) https://bugs.python.org/issue?@action=redirect&bpo=24192

   (16) https://bugs.python.org/issue?@action=redirect&bpo=24022

   (17) https://bugs.python.org/issue?@action=redirect&bpo=9951

   (18) https://bugs.python.org/issue?@action=redirect&bpo=22906

   (19) https://bugs.python.org/issue?@action=redirect&bpo=24017


File: python.info,  Node: Library<89>,  Next: IDLE<60>,  Prev: Core and Builtins<90>,  Up: Python 3 5 0 beta 1

1.23.103.2 Library
..................

   - bpo-14373(1): Added C implementation of functools.lru_cache().
     Based on patches by Matt Joiner and Alexey Kachayev.

   - bpo-24230(2): The tempfile module now accepts bytes for prefix,
     suffix and dir parameters and returns bytes in such situations
     (matching the os module APIs).

   - bpo-22189(3): collections.UserString now supports __getnewargs__(),
     __rmod__(), casefold(), format_map(), isprintable(), and
     maketrans().  Patch by Joe Jevnik.

   - bpo-24244(4): Prevents termination when an invalid format string is
     encountered on Windows in strftime.

   - bpo-23973(5): PEP 484: Add the typing module.

   - bpo-23086(6): The collections.abc.Sequence() abstract base class
     added 'start' and 'stop' parameters to the index() mixin.  Patch by
     Devin Jeanpierre.

   - bpo-20035(7): Replaced the ‘tkinter._fix’ module used for setting
     up the Tcl/Tk environment on Windows with a private function in the
     ‘_tkinter’ module that makes no permanent changes to the
     environment.

   - bpo-24257(8): Fixed segmentation fault in sqlite3.Row constructor
     with faked cursor type.

   - bpo-15836(9): assertRaises(), assertRaisesRegex(), assertWarns()
     and assertWarnsRegex() assertments now check the type of the first
     argument to prevent possible user error.  Based on patch by Daniel
     Wagner-Hall.

   - bpo-9858(10): Add missing method stubs to _io.RawIOBase.  Patch by
     Laura Rupprecht.

   - bpo-22955(11): attrgetter, itemgetter and methodcaller objects in
     the operator module now support pickling.  Added readable and
     evaluable repr for these objects.  Based on patch by Josh
     Rosenberg.

   - bpo-22107(12): tempfile.gettempdir() and tempfile.mkdtemp() now try
     again when a directory with the chosen name already exists on
     Windows as well as on Unix.  tempfile.mkstemp() now fails early if
     parent directory is not valid (not exists or is a file) on Windows.

   - bpo-23780(13): Improved error message in os.path.join() with single
     argument.

   - bpo-6598(14): Increased time precision and random number range in
     email.utils.make_msgid() to strengthen the uniqueness of the
     message ID.

   - bpo-24091(15): Fixed various crashes in corner cases in C
     implementation of ElementTree.

   - bpo-21931(16): msilib.FCICreate() now raises TypeError in the case
     of a bad argument instead of a ValueError with a bogus FCI error
     number.  Patch by Jeffrey Armstrong.

   - bpo-13866(17): 'quote_via' argument added to
     urllib.parse.urlencode.

   - bpo-20098(18): New mangle_from policy option for email, default
     True for compat32, but False for all other policies.

   - bpo-24211(19): The email library now supports RFC 6532: it can
     generate headers using utf-8 instead of encoded words.

   - bpo-16314(20): Added support for the LZMA compression in distutils.

   - bpo-21804(21): poplib now supports RFC 6856 (UTF8).

   - bpo-18682(22): Optimized pprint functions for builtin scalar types.

   - bpo-22027(23): smtplib now supports RFC 6531 (SMTPUTF8).

   - bpo-23488(24): Random generator objects now consume 2x less memory
     on 64-bit.

   - bpo-1322(25): platform.dist() and platform.linux_distribution()
     functions are now deprecated.  Initial patch by Vajrasky Kok.

   - bpo-22486(26): Added the math.gcd() function.  The fractions.gcd()
     function now is deprecated.  Based on patch by Mark Dickinson.

   - bpo-24064(27): Property() docstrings are now writeable.  (Patch by
     Berker Peksag.)

   - bpo-22681(28): Added support for the koi8_t encoding.

   - bpo-22682(29): Added support for the kz1048 encoding.

   - bpo-23796(30): peek and read1 methods of BufferedReader now raise
     ValueError if they called on a closed object.  Patch by John
     Hergenroeder.

   - bpo-21795(31): smtpd now supports the 8BITMIME extension whenever
     the new 'decode_data' constructor argument is set to False.

   - bpo-24155(32): optimize heapq.heapify() for better cache
     performance when heapifying large lists.

   - bpo-21800(33): imaplib now supports RFC 5161 (enable), RFC 6855
     (utf8/internationalized email) and automatically encodes non-ASCII
     usernames and passwords to UTF8.

   - bpo-20274(34): When calling a _sqlite.Connection, it now complains
     if passed any keyword arguments.  Previously it silently ignored
     them.

   - bpo-20274(35): Remove ignored and erroneous "kwargs" parameters
     from three METH_VARARGS methods on _sqlite.Connection.

   - bpo-24134(36): assertRaises(), assertRaisesRegex(), assertWarns()
     and assertWarnsRegex() checks now emits a deprecation warning when
     callable is None or keyword arguments except msg is passed in the
     context manager mode.

   - bpo-24018(37): Add a collections.abc.Generator abstract base class.
     Contributed by Stefan Behnel.

   - bpo-23880(38): Tkinter's getint() and getdouble() now support
     Tcl_Obj.  Tkinter's getdouble() now supports any numbers (in
     particular int).

   - bpo-22619(39): Added negative limit support in the traceback
     module.  Based on patch by Dmitry Kazakov.

   - bpo-24094(40): Fix possible crash in json.encode with poorly
     behaved dict subclasses.

   - bpo-9246(41): On POSIX, os.getcwd() now supports paths longer than
     1025 bytes.  Patch written by William Orr.

   - bpo-17445(42): add difflib.diff_bytes() to support comparison of
     byte strings (fixes a regression from Python 2).

   - bpo-23917(43): Fall back to sequential compilation when
     ProcessPoolExecutor doesn't exist.  Patch by Claudiu Popa.

   - bpo-23008(44): Fixed resolving attributes with boolean value is
     False in pydoc.

   - Fix asyncio issue 235: LifoQueue and PriorityQueue's put didn't
     increment unfinished tasks (this bug was introduced when
     JoinableQueue was merged with Queue).

   - bpo-23908(45): os functions now reject paths with embedded null
     character on Windows instead of silently truncating them.

   - bpo-23728(46): binascii.crc_hqx() could return an integer outside
     of the range 0-0xffff for empty data.

   - bpo-23887(47): urllib.error.HTTPError now has a proper repr()
     representation.  Patch by Berker Peksag.

   - asyncio: New event loop APIs: set_task_factory() and
     get_task_factory().

   - asyncio: async() function is deprecated in favour of
     ensure_future().

   - bpo-24178(48): asyncio.Lock, Condition, Semaphore, and
     BoundedSemaphore support new 'async with' syntax.  Contributed by
     Yury Selivanov.

   - bpo-24179(49): Support 'async for' for asyncio.StreamReader.
     Contributed by Yury Selivanov.

   - bpo-24184(50): Add AsyncIterator and AsyncIterable ABCs to
     collections.abc.  Contributed by Yury Selivanov.

   - bpo-22547(51): Implement informative __repr__ for
     inspect.BoundArguments.  Contributed by Yury Selivanov.

   - bpo-24190(52): Implement inspect.BoundArgument.apply_defaults()
     method.  Contributed by Yury Selivanov.

   - bpo-20691(53): Add 'follow_wrapped' argument to
     inspect.Signature.from_callable() and inspect.signature().
     Contributed by Yury Selivanov.

   - bpo-24248(54): Deprecate inspect.Signature.from_function() and
     inspect.Signature.from_builtin().

   - bpo-23898(55): Fix inspect.classify_class_attrs() to support
     attributes with overloaded __eq__ and __bool__.  Patch by Mike
     Bayer.

   - bpo-24298(56): Fix inspect.signature() to correctly unwrap wrappers
     around bound methods.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=14373

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24230

   (3) https://bugs.python.org/issue?@action=redirect&bpo=22189

   (4) https://bugs.python.org/issue?@action=redirect&bpo=24244

   (5) https://bugs.python.org/issue?@action=redirect&bpo=23973

   (6) https://bugs.python.org/issue?@action=redirect&bpo=23086

   (7) https://bugs.python.org/issue?@action=redirect&bpo=20035

   (8) https://bugs.python.org/issue?@action=redirect&bpo=24257

   (9) https://bugs.python.org/issue?@action=redirect&bpo=15836

   (10) https://bugs.python.org/issue?@action=redirect&bpo=9858

   (11) https://bugs.python.org/issue?@action=redirect&bpo=22955

   (12) https://bugs.python.org/issue?@action=redirect&bpo=22107

   (13) https://bugs.python.org/issue?@action=redirect&bpo=23780

   (14) https://bugs.python.org/issue?@action=redirect&bpo=6598

   (15) https://bugs.python.org/issue?@action=redirect&bpo=24091

   (16) https://bugs.python.org/issue?@action=redirect&bpo=21931

   (17) https://bugs.python.org/issue?@action=redirect&bpo=13866

   (18) https://bugs.python.org/issue?@action=redirect&bpo=20098

   (19) https://bugs.python.org/issue?@action=redirect&bpo=24211

   (20) https://bugs.python.org/issue?@action=redirect&bpo=16314

   (21) https://bugs.python.org/issue?@action=redirect&bpo=21804

   (22) https://bugs.python.org/issue?@action=redirect&bpo=18682

   (23) https://bugs.python.org/issue?@action=redirect&bpo=22027

   (24) https://bugs.python.org/issue?@action=redirect&bpo=23488

   (25) https://bugs.python.org/issue?@action=redirect&bpo=1322

   (26) https://bugs.python.org/issue?@action=redirect&bpo=22486

   (27) https://bugs.python.org/issue?@action=redirect&bpo=24064

   (28) https://bugs.python.org/issue?@action=redirect&bpo=22681

   (29) https://bugs.python.org/issue?@action=redirect&bpo=22682

   (30) https://bugs.python.org/issue?@action=redirect&bpo=23796

   (31) https://bugs.python.org/issue?@action=redirect&bpo=21795

   (32) https://bugs.python.org/issue?@action=redirect&bpo=24155

   (33) https://bugs.python.org/issue?@action=redirect&bpo=21800

   (34) https://bugs.python.org/issue?@action=redirect&bpo=20274

   (35) https://bugs.python.org/issue?@action=redirect&bpo=20274

   (36) https://bugs.python.org/issue?@action=redirect&bpo=24134

   (37) https://bugs.python.org/issue?@action=redirect&bpo=24018

   (38) https://bugs.python.org/issue?@action=redirect&bpo=23880

   (39) https://bugs.python.org/issue?@action=redirect&bpo=22619

   (40) https://bugs.python.org/issue?@action=redirect&bpo=24094

   (41) https://bugs.python.org/issue?@action=redirect&bpo=9246

   (42) https://bugs.python.org/issue?@action=redirect&bpo=17445

   (43) https://bugs.python.org/issue?@action=redirect&bpo=23917

   (44) https://bugs.python.org/issue?@action=redirect&bpo=23008

   (45) https://bugs.python.org/issue?@action=redirect&bpo=23908

   (46) https://bugs.python.org/issue?@action=redirect&bpo=23728

   (47) https://bugs.python.org/issue?@action=redirect&bpo=23887

   (48) https://bugs.python.org/issue?@action=redirect&bpo=24178

   (49) https://bugs.python.org/issue?@action=redirect&bpo=24179

   (50) https://bugs.python.org/issue?@action=redirect&bpo=24184

   (51) https://bugs.python.org/issue?@action=redirect&bpo=22547

   (52) https://bugs.python.org/issue?@action=redirect&bpo=24190

   (53) https://bugs.python.org/issue?@action=redirect&bpo=20691

   (54) https://bugs.python.org/issue?@action=redirect&bpo=24248

   (55) https://bugs.python.org/issue?@action=redirect&bpo=23898

   (56) https://bugs.python.org/issue?@action=redirect&bpo=24298


File: python.info,  Node: IDLE<60>,  Next: Tests<76>,  Prev: Library<89>,  Up: Python 3 5 0 beta 1

1.23.103.3 IDLE
...............

   - bpo-23184(1): remove unused names and imports in idlelib.  Initial
     patch by Al Sweigart.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23184


File: python.info,  Node: Tests<76>,  Next: Documentation<71>,  Prev: IDLE<60>,  Up: Python 3 5 0 beta 1

1.23.103.4 Tests
................

   - bpo-21520(1): test_zipfile no longer fails if the word 'bad'
     appears anywhere in the name of the current directory.

   - bpo-9517(2): Move script_helper into the support package.  Patch by
     Christie Wilson.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=21520

   (2) https://bugs.python.org/issue?@action=redirect&bpo=9517


File: python.info,  Node: Documentation<71>,  Next: Tools/Demos<44>,  Prev: Tests<76>,  Up: Python 3 5 0 beta 1

1.23.103.5 Documentation
........................

   - bpo-22155(1): Add File Handlers subsection with createfilehandler
     to tkinter doc.  Remove obsolete example from FAQ. Patch by Martin
     Panter.

   - bpo-24029(2): Document the name binding behavior for submodule
     imports.

   - bpo-24077(3): Fix typo in man page for -I command option: -s, not
     -S

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22155

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24029

   (3) https://bugs.python.org/issue?@action=redirect&bpo=24077


File: python.info,  Node: Tools/Demos<44>,  Prev: Documentation<71>,  Up: Python 3 5 0 beta 1

1.23.103.6 Tools/Demos
......................

   - bpo-24000(1): Improved Argument Clinic's mapping of converters to
     legacy "format units".  Updated the documentation to match.

   - bpo-24001(2): Argument Clinic converters now use accept={type}
     instead of types={'type'} to specify the types the converter
     accepts.

   - bpo-23330(3): h2py now supports arbitrary filenames in #include.

   - bpo-24031(4): make patchcheck now supports git checkouts, too.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=24000

   (2) https://bugs.python.org/issue?@action=redirect&bpo=24001

   (3) https://bugs.python.org/issue?@action=redirect&bpo=23330

   (4) https://bugs.python.org/issue?@action=redirect&bpo=24031


File: python.info,  Node: Python 3 5 0 alpha 4,  Next: Python 3 5 0 alpha 3,  Prev: Python 3 5 0 beta 1,  Up: Changelog（更動日誌）

1.23.104 Python 3.5.0 alpha 4
-----------------------------

'Release date: 2015-04-19'

* Menu:

* Core and Builtins: Core and Builtins<91>.
* Library: Library<90>.
* Build: Build<83>.
* Tests: Tests<77>.
* Tools/Demos: Tools/Demos<45>.
* C API: C API<67>.


File: python.info,  Node: Core and Builtins<91>,  Next: Library<90>,  Up: Python 3 5 0 alpha 4

1.23.104.1 Core and Builtins
............................

   - bpo-22980(1): Under Linux, GNU/KFreeBSD and the Hurd, C extensions
     now include the architecture triplet in the extension name, to make
     it easy to test builds for different ABIs in the same working tree.
     Under OS X, the extension name now includes PEP 3149(2)-style
     information.

   - bpo-22631(3): Added Linux-specific socket constant
     CAN_RAW_FD_FRAMES. Patch courtesy of Joe Jevnik.

   - bpo-23731(4): Implement PEP 488(5): removal of .pyo files.

   - bpo-23726(6): Don't enable GC for user subclasses of non-GC types
     that don't add any new fields.  Patch by Eugene Toder.

   - bpo-23309(7): Avoid a deadlock at shutdown if a daemon thread is
     aborted while it is holding a lock to a buffered I/O object, and
     the main thread tries to use the same I/O object (typically stdout
     or stderr).  A fatal error is emitted instead.

   - bpo-22977(8): Fixed formatting Windows error messages on Wine.
     Patch by Martin Panter.

   - bpo-23466(9): %c, %o, %x, and %X in bytes formatting now raise
     TypeError on non-integer input.

   - bpo-24044(10): Fix possible null pointer dereference in list.sort
     in out of memory conditions.

   - bpo-21354(11): PyCFunction_New function is exposed by python DLL
     again.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22980

   (2) https://peps.python.org/pep-3149/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=22631

   (4) https://bugs.python.org/issue?@action=redirect&bpo=23731

   (5) https://peps.python.org/pep-0488/

   (6) https://bugs.python.org/issue?@action=redirect&bpo=23726

   (7) https://bugs.python.org/issue?@action=redirect&bpo=23309

   (8) https://bugs.python.org/issue?@action=redirect&bpo=22977

   (9) https://bugs.python.org/issue?@action=redirect&bpo=23466

   (10) https://bugs.python.org/issue?@action=redirect&bpo=24044

   (11) https://bugs.python.org/issue?@action=redirect&bpo=21354


File: python.info,  Node: Library<90>,  Next: Build<83>,  Prev: Core and Builtins<91>,  Up: Python 3 5 0 alpha 4

1.23.104.2 Library
..................

   - bpo-23840(1): tokenize.open() now closes the temporary binary file
     on error to fix a resource warning.

   - bpo-16914(2): new debuglevel 2 in smtplib adds timestamps to debug
     output.

   - bpo-7159(3): urllib.request now supports sending auth credentials
     automatically after the first 401.  This enhancement is a superset
     of the enhancement from bpo-19494(4) and supersedes that change.

   - bpo-23703(5): Fix a regression in urljoin() introduced in
     901e4e52b20a.  Patch by Demian Brecht.

   - bpo-4254(6): Adds _curses.update_lines_cols().  Patch by Arnon
     Yaari

   - bpo-19933(7): Provide default argument for ndigits in round.  Patch
     by Vajrasky Kok.

   - bpo-23193(8): Add a numeric_owner parameter to
     tarfile.TarFile.extract and tarfile.TarFile.extractall.  Patch by
     Michael Vogt and Eric Smith.

   - bpo-23342(9): Add a subprocess.run() function than returns a
     CalledProcess instance for a more consistent API than the existing
     call* functions.

   - bpo-21217(10): inspect.getsourcelines() now tries to compute the
     start and end lines from the code object, fixing an issue when a
     lambda function is used as decorator argument.  Patch by Thomas
     Ballinger and Allison Kaptur.

   - bpo-24521(11): Fix possible integer overflows in the pickle module.

   - bpo-22931(12): Allow '[' and ']' in cookie values.

   - The keywords attribute of functools.partial is now always a
     dictionary.

   - bpo-23811(13): Add missing newline to the PyCompileError error
     message.  Patch by Alex Shkop.

   - bpo-21116(14): Avoid blowing memory when allocating a
     multiprocessing shared array that's larger than 50% of the
     available RAM. Patch by Médéric Boquien.

   - bpo-22982(15): Improve BOM handling when seeking to multiple
     positions of a writable text file.

   - bpo-23464(16): Removed deprecated asyncio JoinableQueue.

   - bpo-23529(17): Limit the size of decompressed data when reading
     from GzipFile, BZ2File or LZMAFile.  This defeats denial of service
     attacks using compressed bombs (i.e.  compressed payloads which
     decompress to a huge size).  Patch by Martin Panter and Nikolaus
     Rath.

   - bpo-21859(18): Added Python implementation of io.FileIO.

   - bpo-23865(19): close() methods in multiple modules now are
     idempotent and more robust at shutdown.  If they need to release
     multiple resources, all are released even if errors occur.

   - bpo-23400(20): Raise same exception on both Python 2 and 3 if
     sem_open is not available.  Patch by Davin Potts.

   - bpo-10838(21): The subprocess now module includes SubprocessError
     and TimeoutError in its list of exported names for the users wild
     enough to use ‘from subprocess import *’.

   - bpo-23411(22): Added DefragResult, ParseResult, SplitResult,
     DefragResultBytes, ParseResultBytes, and SplitResultBytes to
     urllib.parse.__all__.  Patch by Martin Panter.

   - bpo-23881(23): urllib.request.ftpwrapper constructor now closes the
     socket if the FTP connection failed to fix a ResourceWarning.

   - bpo-23853(24): *note socket.socket.sendall(): d4e. does no more
     reset the socket timeout each time data is sent successfully.  The
     socket timeout is now the maximum total duration to send all data.

   - bpo-22721(25): An order of multiline pprint output of set or dict
     containing orderable and non-orderable elements no longer depends
     on iteration order of set or dict.

   - bpo-15133(26): _tkinter.tkapp.getboolean() now supports Tcl_Obj and
     always returns bool.  tkinter.BooleanVar now validates input values
     (accepted bool, int, str, and Tcl_Obj).  tkinter.BooleanVar.get()
     now always returns bool.

   - bpo-10590(27): xml.sax.parseString() now supports string argument.

   - bpo-23338(28): Fixed formatting ctypes error messages on Cygwin.
     Patch by Makoto Kato.

   - bpo-15582(29): inspect.getdoc() now follows inheritance chains.

   - bpo-2175(30): SAX parsers now support a character stream of
     InputSource object.

   - bpo-16840(31): Tkinter now supports 64-bit integers added in Tcl
     8.4 and arbitrary precision integers added in Tcl 8.5.

   - bpo-23834(32): Fix socket.sendto(), use the C Py_ssize_t type to
     store the result of sendto() instead of the C int type.

   - bpo-23618(33): *note socket.socket.connect(): d49. now waits until
     the connection completes instead of raising *note InterruptedError:
     d2e. if the connection is interrupted by signals, signal handlers
     don't raise an exception and the socket is blocking or has a
     timeout.  *note socket.socket.connect(): d49. still raise *note
     InterruptedError: d2e. for non-blocking sockets.

   - bpo-21526(34): Tkinter now supports new boolean type in Tcl 8.5.

   - bpo-23836(35): Fix the faulthandler module to handle reentrant
     calls to its signal handlers.

   - bpo-23838(36): linecache now clears the cache and returns an empty
     result on MemoryError.

   - bpo-10395(37): Added os.path.commonpath().  Implemented in
     posixpath and ntpath.  Based on patch by Rafik Draoui.

   - bpo-23611(38): Serializing more "lookupable" objects (such as
     unbound methods or nested classes) now are supported with pickle
     protocols < 4.

   - bpo-13583(39): sqlite3.Row now supports slice indexing.

   - bpo-18473(40): Fixed 2to3 and 3to2 compatible pickle mappings.
     Fixed ambiguous reverse mappings.  Added many new mappings.  Import
     mapping is no longer applied to modules already mapped with full
     name mapping.

   - bpo-23485(41): select.select() is now retried automatically with
     the recomputed timeout when interrupted by a signal, except if the
     signal handler raises an exception.  This change is part of the PEP
     475(42).

   - bpo-23752(43): When built from an existing file descriptor,
     io.FileIO() now only calls fstat() once.  Before fstat() was called
     twice, which was not necessary.

   - bpo-23704(44): collections.deque() objects now support __add__,
     __mul__, and __imul__().

   - bpo-23171(45): csv.Writer.writerow() now supports arbitrary
     iterables.

   - bpo-23745(46): The new email header parser now handles duplicate
     MIME parameter names without error, similar to how get_param
     behaves.

   - bpo-22117(47): Fix os.utime(), it now rounds the timestamp towards
     minus infinity (-inf) instead of rounding towards zero.

   - bpo-23310(48): Fix MagicMock's initializer to work with
     __methods__, just like configure_mock().  Patch by Kasia Jachim.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23840

   (2) https://bugs.python.org/issue?@action=redirect&bpo=16914

   (3) https://bugs.python.org/issue?@action=redirect&bpo=7159

   (4) https://bugs.python.org/issue?@action=redirect&bpo=19494

   (5) https://bugs.python.org/issue?@action=redirect&bpo=23703

   (6) https://bugs.python.org/issue?@action=redirect&bpo=4254

   (7) https://bugs.python.org/issue?@action=redirect&bpo=19933

   (8) https://bugs.python.org/issue?@action=redirect&bpo=23193

   (9) https://bugs.python.org/issue?@action=redirect&bpo=23342

   (10) https://bugs.python.org/issue?@action=redirect&bpo=21217

   (11) https://bugs.python.org/issue?@action=redirect&bpo=24521

   (12) https://bugs.python.org/issue?@action=redirect&bpo=22931

   (13) https://bugs.python.org/issue?@action=redirect&bpo=23811

   (14) https://bugs.python.org/issue?@action=redirect&bpo=21116

   (15) https://bugs.python.org/issue?@action=redirect&bpo=22982

   (16) https://bugs.python.org/issue?@action=redirect&bpo=23464

   (17) https://bugs.python.org/issue?@action=redirect&bpo=23529

   (18) https://bugs.python.org/issue?@action=redirect&bpo=21859

   (19) https://bugs.python.org/issue?@action=redirect&bpo=23865

   (20) https://bugs.python.org/issue?@action=redirect&bpo=23400

   (21) https://bugs.python.org/issue?@action=redirect&bpo=10838

   (22) https://bugs.python.org/issue?@action=redirect&bpo=23411

   (23) https://bugs.python.org/issue?@action=redirect&bpo=23881

   (24) https://bugs.python.org/issue?@action=redirect&bpo=23853

   (25) https://bugs.python.org/issue?@action=redirect&bpo=22721

   (26) https://bugs.python.org/issue?@action=redirect&bpo=15133

   (27) https://bugs.python.org/issue?@action=redirect&bpo=10590

   (28) https://bugs.python.org/issue?@action=redirect&bpo=23338

   (29) https://bugs.python.org/issue?@action=redirect&bpo=15582

   (30) https://bugs.python.org/issue?@action=redirect&bpo=2175

   (31) https://bugs.python.org/issue?@action=redirect&bpo=16840

   (32) https://bugs.python.org/issue?@action=redirect&bpo=23834

   (33) https://bugs.python.org/issue?@action=redirect&bpo=23618

   (34) https://bugs.python.org/issue?@action=redirect&bpo=21526

   (35) https://bugs.python.org/issue?@action=redirect&bpo=23836

   (36) https://bugs.python.org/issue?@action=redirect&bpo=23838

   (37) https://bugs.python.org/issue?@action=redirect&bpo=10395

   (38) https://bugs.python.org/issue?@action=redirect&bpo=23611

   (39) https://bugs.python.org/issue?@action=redirect&bpo=13583

   (40) https://bugs.python.org/issue?@action=redirect&bpo=18473

   (41) https://bugs.python.org/issue?@action=redirect&bpo=23485

   (42) https://peps.python.org/pep-0475/

   (43) https://bugs.python.org/issue?@action=redirect&bpo=23752

   (44) https://bugs.python.org/issue?@action=redirect&bpo=23704

   (45) https://bugs.python.org/issue?@action=redirect&bpo=23171

   (46) https://bugs.python.org/issue?@action=redirect&bpo=23745

   (47) https://bugs.python.org/issue?@action=redirect&bpo=22117

   (48) https://bugs.python.org/issue?@action=redirect&bpo=23310


File: python.info,  Node: Build<83>,  Next: Tests<77>,  Prev: Library<90>,  Up: Python 3 5 0 alpha 4

1.23.104.3 Build
................

   - bpo-23817(1): FreeBSD now uses "1.0" in the SOVERSION as other
     operating systems, instead of just "1".

   - bpo-23501(2): Argument Clinic now generates code into separate
     files by default.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23817

   (2) https://bugs.python.org/issue?@action=redirect&bpo=23501


File: python.info,  Node: Tests<77>,  Next: Tools/Demos<45>,  Prev: Build<83>,  Up: Python 3 5 0 alpha 4

1.23.104.4 Tests
................

   - bpo-23799(1): Added test.support.start_threads() for running and
     cleaning up multiple threads.

   - bpo-22390(2): test.regrtest now emits a warning if temporary files
     or directories are left after running a test.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23799

   (2) https://bugs.python.org/issue?@action=redirect&bpo=22390


File: python.info,  Node: Tools/Demos<45>,  Next: C API<67>,  Prev: Tests<77>,  Up: Python 3 5 0 alpha 4

1.23.104.5 Tools/Demos
......................

   - bpo-18128(1): pygettext now uses standard +NNNN format in the
     POT-Creation-Date header.

   - bpo-23935(2): Argument Clinic's understanding of format units
     accepting bytes, bytearrays, and buffers is now consistent with
     both the documentation and the implementation.

   - bpo-23944(3): Argument Clinic now wraps long impl prototypes at
     column 78.

   - bpo-20586(4): Argument Clinic now ensures that functions without
     docstrings have signatures.

   - bpo-23492(5): Argument Clinic now generates argument parsing code
     with PyArg_Parse instead of PyArg_ParseTuple if possible.

   - bpo-23500(6): Argument Clinic is now smarter about generating the
     "#ifndef" (empty) definition of the methoddef macro: it's only
     generated once, even if Argument Clinic processes the same symbol
     multiple times, and it's emitted at the end of all processing
     rather than immediately after the first use.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=18128

   (2) https://bugs.python.org/issue?@action=redirect&bpo=23935

   (3) https://bugs.python.org/issue?@action=redirect&bpo=23944

   (4) https://bugs.python.org/issue?@action=redirect&bpo=20586

   (5) https://bugs.python.org/issue?@action=redirect&bpo=23492

   (6) https://bugs.python.org/issue?@action=redirect&bpo=23500


File: python.info,  Node: C API<67>,  Prev: Tools/Demos<45>,  Up: Python 3 5 0 alpha 4

1.23.104.6 C API
................

   - bpo-23998(1): PyImport_ReInitLock() now checks for lock allocation
     error

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23998


File: python.info,  Node: Python 3 5 0 alpha 3,  Next: Python 3 5 0 alpha 2,  Prev: Python 3 5 0 alpha 4,  Up: Changelog（更動日誌）

1.23.105 Python 3.5.0 alpha 3
-----------------------------

'Release date: 2015-03-28'

* Menu:

* Core and Builtins: Core and Builtins<92>.
* Library: Library<91>.
* Build: Build<84>.
* Tests: Tests<78>.
* Tools/Demos: Tools/Demos<46>.


File: python.info,  Node: Core and Builtins<92>,  Next: Library<91>,  Up: Python 3 5 0 alpha 3

1.23.105.1 Core and Builtins
............................

   - bpo-23573(1): Increased performance of string search operations
     (str.find, str.index, str.count, the in operator, str.split,
     str.partition) with arguments of different kinds (UCS1, UCS2,
     UCS4).

   - bpo-23753(2): Python doesn't support anymore platforms without
     stat() or fstat(), these functions are always required.

   - bpo-23681(3): The -b option now affects comparisons of bytes with
     int.

   - bpo-23632(4): Memoryviews now allow tuple indexing (including for
     multi-dimensional memoryviews).

   - bpo-23192(5): Fixed generator lambdas.  Patch by Bruno Cauet.

   - bpo-23629(6): Fix the default __sizeof__ implementation for
     variable-sized objects.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23573

   (2) https://bugs.python.org/issue?@action=redirect&bpo=23753

   (3) https://bugs.python.org/issue?@action=redirect&bpo=23681

   (4) https://bugs.python.org/issue?@action=redirect&bpo=23632

   (5) https://bugs.python.org/issue?@action=redirect&bpo=23192

   (6) https://bugs.python.org/issue?@action=redirect&bpo=23629


File: python.info,  Node: Library<91>,  Next: Build<84>,  Prev: Core and Builtins<92>,  Up: Python 3 5 0 alpha 3

1.23.105.2 Library
..................

   - bpo-14260(1): The groupindex attribute of regular expression
     pattern object now is non-modifiable mapping.

   - bpo-23792(2): Ignore KeyboardInterrupt when the pydoc pager is
     active.  This mimics the behavior of the standard unix pagers, and
     prevents pipepager from shutting down while the pager itself is
     still running.

   - bpo-23775(3): pprint() of OrderedDict now outputs the same
     representation as repr().

   - bpo-23765(4): Removed IsBadStringPtr calls in ctypes

   - bpo-22364(5): Improved some re error messages using regex for
     hints.

   - bpo-23742(6): ntpath.expandvars() no longer loses unbalanced single
     quotes.

   - bpo-21717(7): The zipfile.ZipFile.open function now supports 'x'
     (exclusive creation) mode.

   - bpo-21802(8): The reader in BufferedRWPair now is closed even when
     closing writer failed in BufferedRWPair.close().

   - bpo-23622(9): Unknown escapes in regular expressions that consist
     of ‘'\'’ and ASCII letter now raise a deprecation warning and will
     be forbidden in Python 3.6.

   - bpo-23671(10): string.Template now allows specifying the "self"
     parameter as a keyword argument.  string.Formatter now allows
     specifying the "self" and the "format_string" parameters as keyword
     arguments.

   - bpo-23502(11): The pprint module now supports mapping proxies.

   - bpo-17530(12): pprint now wraps long bytes objects and bytearrays.

   - bpo-22687(13): Fixed some corner cases in breaking words in
     tetxtwrap.  Got rid of quadratic complexity in breaking long words.

   - bpo-4727(14): The copy module now uses pickle protocol 4 (PEP 3154)
     and supports copying of instances of classes whose __new__ method
     takes keyword-only arguments.

   - bpo-23491(15): Added a zipapp module to support creating executable
     zip file archives of Python code.  Registered ".pyz" and ".pyzw"
     extensions on Windows for these archives (PEP 441).

   - bpo-23657(16): Avoid explicit checks for str in zipapp, adding
     support for pathlib.Path objects as arguments.

   - bpo-23688(17): Added support of arbitrary bytes-like objects and
     avoided unnecessary copying of memoryview in gzip.GzipFile.write().
     Original patch by Wolfgang Maier.

   - bpo-23252(18): Added support for writing ZIP files to unseekable
     streams.

   - bpo-23647(19): Increase imaplib's MAXLINE to accommodate modern
     mailbox sizes.

   - bpo-23539(20): If body is None, http.client.HTTPConnection.request
     now sets Content-Length to 0 for PUT, POST, and PATCH headers to
     avoid 411 errors from some web servers.

   - bpo-22351(21): The nntplib.NNTP constructor no longer leaves the
     connection and socket open until the garbage collector cleans them
     up.  Patch by Martin Panter.

   - bpo-23704(22): collections.deque() objects now support methods for
     index(), insert(), and copy().  This allows deques to be registered
     as a MutableSequence and it improves their substitutability for
     lists.

   - bpo-23715(23): *note signal.sigwaitinfo(): d51. and *note
     signal.sigtimedwait(): d50. are now retried when interrupted by a
     signal not in the 'sigset' parameter, if the signal handler does
     not raise an exception.  signal.sigtimedwait() recomputes the
     timeout with a monotonic clock when it is retried.

   - bpo-23001(24): Few functions in modules mmap, ossaudiodev, socket,
     ssl, and codecs, that accepted only read-only bytes-like object now
     accept writable bytes-like object too.

   - bpo-23646(25): If time.sleep() is interrupted by a signal, the
     sleep is now retried with the recomputed delay, except if the
     signal handler raises an exception (PEP 475).

   - bpo-23136(26): _strptime now uniformly handles all days in week 0,
     including Dec 30 of previous year.  Based on patch by Jim Carroll.

   - bpo-23700(27): Iterator of NamedTemporaryFile now keeps a reference
     to NamedTemporaryFile instance.  Patch by Bohuslav Kabrda.

   - bpo-22903(28): The fake test case created by unittest.loader when
     it fails importing a test module is now picklable.

   - bpo-22181(29): On Linux, os.urandom() now uses the new getrandom()
     syscall if available, syscall introduced in the Linux kernel 3.17.
     It is more reliable and more secure, because it avoids the need of
     a file descriptor and waits until the kernel has enough entropy.

   - bpo-2211(30): Updated the implementation of the http.cookies.Morsel
     class.  Setting attributes key, value and coded_value directly now
     is deprecated.  update() and setdefault() now transform and check
     keys.  Comparing for equality now takes into account attributes
     key, value and coded_value.  copy() now returns a Morsel, not a
     dict.  repr() now contains all attributes.  Optimized checking keys
     and quoting values.  Added new tests.  Original patch by Demian
     Brecht.

   - bpo-18983(31): Allow selection of output units in timeit.  Patch by
     Julian Gindi.

   - bpo-23631(32): Fix traceback.format_list when a traceback has been
     mutated.

   - bpo-23568(33): Add rdivmod support to MagicMock() objects.  Patch
     by Håkan Lövdahl.

   - bpo-2052(34): Add charset parameter to HtmlDiff.make_file().

   - bpo-23668(35): Support os.truncate and os.ftruncate on Windows.

   - bpo-23138(36): Fixed parsing cookies with absent keys or values in
     cookiejar.  Patch by Demian Brecht.

   - bpo-23051(37): multiprocessing.Pool methods imap() and
     imap_unordered() now handle exceptions raised by an iterator.
     Patch by Alon Diamant and Davin Potts.

   - bpo-23581(38): Add matmul support to MagicMock.  Patch by Håkan
     Lövdahl.

   - bpo-23566(39): enable(), register(), dump_traceback() and
     dump_traceback_later() functions of faulthandler now accept file
     descriptors.  Patch by Wei Wu.

   - bpo-22928(40): Disabled HTTP header injections in http.client.
     Original patch by Demian Brecht.

   - bpo-23615(41): Modules bz2, tarfile and tokenize now can be
     reloaded with imp.reload().  Patch by Thomas Kluyver.

   - bpo-23605(42): os.walk() now calls os.scandir() instead of
     os.listdir().  The usage of os.scandir() reduces the number of
     calls to os.stat().  Initial patch written by Ben Hoyt.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=14260

   (2) https://bugs.python.org/issue?@action=redirect&bpo=23792

   (3) https://bugs.python.org/issue?@action=redirect&bpo=23775

   (4) https://bugs.python.org/issue?@action=redirect&bpo=23765

   (5) https://bugs.python.org/issue?@action=redirect&bpo=22364

   (6) https://bugs.python.org/issue?@action=redirect&bpo=23742

   (7) https://bugs.python.org/issue?@action=redirect&bpo=21717

   (8) https://bugs.python.org/issue?@action=redirect&bpo=21802

   (9) https://bugs.python.org/issue?@action=redirect&bpo=23622

   (10) https://bugs.python.org/issue?@action=redirect&bpo=23671

   (11) https://bugs.python.org/issue?@action=redirect&bpo=23502

   (12) https://bugs.python.org/issue?@action=redirect&bpo=17530

   (13) https://bugs.python.org/issue?@action=redirect&bpo=22687

   (14) https://bugs.python.org/issue?@action=redirect&bpo=4727

   (15) https://bugs.python.org/issue?@action=redirect&bpo=23491

   (16) https://bugs.python.org/issue?@action=redirect&bpo=23657

   (17) https://bugs.python.org/issue?@action=redirect&bpo=23688

   (18) https://bugs.python.org/issue?@action=redirect&bpo=23252

   (19) https://bugs.python.org/issue?@action=redirect&bpo=23647

   (20) https://bugs.python.org/issue?@action=redirect&bpo=23539

   (21) https://bugs.python.org/issue?@action=redirect&bpo=22351

   (22) https://bugs.python.org/issue?@action=redirect&bpo=23704

   (23) https://bugs.python.org/issue?@action=redirect&bpo=23715

   (24) https://bugs.python.org/issue?@action=redirect&bpo=23001

   (25) https://bugs.python.org/issue?@action=redirect&bpo=23646

   (26) https://bugs.python.org/issue?@action=redirect&bpo=23136

   (27) https://bugs.python.org/issue?@action=redirect&bpo=23700

   (28) https://bugs.python.org/issue?@action=redirect&bpo=22903

   (29) https://bugs.python.org/issue?@action=redirect&bpo=22181

   (30) https://bugs.python.org/issue?@action=redirect&bpo=2211

   (31) https://bugs.python.org/issue?@action=redirect&bpo=18983

   (32) https://bugs.python.org/issue?@action=redirect&bpo=23631

   (33) https://bugs.python.org/issue?@action=redirect&bpo=23568

   (34) https://bugs.python.org/issue?@action=redirect&bpo=2052

   (35) https://bugs.python.org/issue?@action=redirect&bpo=23668

   (36) https://bugs.python.org/issue?@action=redirect&bpo=23138

   (37) https://bugs.python.org/issue?@action=redirect&bpo=23051

   (38) https://bugs.python.org/issue?@action=redirect&bpo=23581

   (39) https://bugs.python.org/issue?@action=redirect&bpo=23566

   (40) https://bugs.python.org/issue?@action=redirect&bpo=22928

   (41) https://bugs.python.org/issue?@action=redirect&bpo=23615

   (42) https://bugs.python.org/issue?@action=redirect&bpo=23605


File: python.info,  Node: Build<84>,  Next: Tests<78>,  Prev: Library<91>,  Up: Python 3 5 0 alpha 3

1.23.105.3 Build
................

   - bpo-23585(1): make patchcheck will ensure the interpreter is built.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23585


File: python.info,  Node: Tests<78>,  Next: Tools/Demos<46>,  Prev: Build<84>,  Up: Python 3 5 0 alpha 3

1.23.105.4 Tests
................

   - bpo-23583(1): Added tests for standard IO streams in IDLE.

   - bpo-22289(2): Prevent test_urllib2net failures due to ftp
     connection timeout.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23583

   (2) https://bugs.python.org/issue?@action=redirect&bpo=22289


File: python.info,  Node: Tools/Demos<46>,  Prev: Tests<78>,  Up: Python 3 5 0 alpha 3

1.23.105.5 Tools/Demos
......................

   - bpo-22826(1): The result of open() in Tools/freeze/bkfile.py is now
     better compatible with regular files (in particular it now supports
     the context management protocol).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22826


File: python.info,  Node: Python 3 5 0 alpha 2,  Next: Python 3 5 0 alpha 1,  Prev: Python 3 5 0 alpha 3,  Up: Changelog（更動日誌）

1.23.106 Python 3.5.0 alpha 2
-----------------------------

'Release date: 2015-03-09'

* Menu:

* Core and Builtins: Core and Builtins<93>.
* Library: Library<92>.
* Build: Build<85>.
* C API: C API<68>.
* Windows: Windows<70>.


File: python.info,  Node: Core and Builtins<93>,  Next: Library<92>,  Up: Python 3 5 0 alpha 2

1.23.106.1 Core and Builtins
............................

   - bpo-23571(1): PyObject_Call() and PyCFunction_Call() now raise a
     SystemError if a function returns a result and raises an exception.
     The SystemError is chained to the previous exception.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23571


File: python.info,  Node: Library<92>,  Next: Build<85>,  Prev: Core and Builtins<93>,  Up: Python 3 5 0 alpha 2

1.23.106.2 Library
..................

   - bpo-22524(1): New os.scandir() function, part of the PEP 471(2):
     "os.scandir() function - a better and faster directory iterator".
     Patch written by Ben Hoyt.

   - bpo-23103(3): Reduced the memory consumption of IPv4Address and
     IPv6Address.

   - bpo-21793(4): BaseHTTPRequestHandler again logs response code as
     numeric, not as stringified enum.  Patch by Demian Brecht.

   - bpo-23476(5): In the ssl module, enable OpenSSL's
     X509_V_FLAG_TRUSTED_FIRST flag on certificate stores when it is
     available.

   - bpo-23576(6): Avoid stalling in SSL reads when EOF has been reached
     in the SSL layer but the underlying connection hasn't been closed.

   - bpo-23504(7): Added an __all__ to the types module.

   - bpo-23563(8): Optimized utility functions in urllib.parse.

   - bpo-7830(9): Flatten nested functools.partial.

   - bpo-20204(10): Added the __module__ attribute to _tkinter classes.

   - bpo-19980(11): Improved help() for non-recognized strings.
     help('') now shows the help on str.  help('help') now shows the
     help on help().  Original patch by Mark Lawrence.

   - bpo-23521(12): Corrected pure python implementation of timedelta
     division.  Eliminated OverflowError from ‘timedelta * float’ for
     some floats; Corrected rounding in timedelta true division.

   - bpo-21619(13): Popen objects no longer leave a zombie after exit in
     the with statement if the pipe was broken.  Patch by Martin Panter.

   - bpo-22936(14): Make it possible to show local variables in
     tracebacks for both the traceback module and unittest.

   - bpo-15955(15): Add an option to limit the output size in
     bz2.decompress().  Patch by Nikolaus Rath.

   - bpo-6639(16): Module-level turtle functions no longer raise
     TclError after closing the window.

   - bpo-814253(17): Group references and conditional group references
     now work in lookbehind assertions in regular expressions.  (See
     also: bpo-9179(18))

   - bpo-23215(19): Multibyte codecs with custom error handlers that
     ignores errors consumed too much memory and raised SystemError or
     MemoryError.  Original patch by Aleksi Torhamo.

   - bpo-5700(20): io.FileIO() called flush() after closing the file.
     flush() was not called in close() if closefd=False.

   - bpo-23374(21): Fixed pydoc failure with non-ASCII files when stdout
     encoding differs from file system encoding (e.g.  on Mac OS).

   - bpo-23481(22): Remove RC4 from the SSL module's default cipher
     list.

   - bpo-21548(23): Fix pydoc.synopsis() and pydoc.apropos() on modules
     with empty docstrings.

   - bpo-22885(24): Fixed arbitrary code execution vulnerability in the
     dbm.dumb module.  Original patch by Claudiu Popa.

   - bpo-23239(25): ssl.match_hostname() now supports matching of IP
     addresses.

   - bpo-23146(26): Fix mishandling of absolute Windows paths with
     forward slashes in pathlib.

   - bpo-23096(27): Pickle representation of floats with protocol 0 now
     is the same for both Python and C implementations.

   - bpo-19105(28): pprint now more efficiently uses free space at the
     right.

   - bpo-14910(29): Add allow_abbrev parameter to
     argparse.ArgumentParser.  Patch by Jonathan Paugh, Steven Bethard,
     paul j3 and Daniel Eriksson.

   - bpo-21717(30): tarfile.open() now supports 'x' (exclusive creation)
     mode.

   - bpo-23344(31): marshal.dumps() is now 20-25% faster on average.

   - bpo-20416(32): marshal.dumps() with protocols 3 and 4 is now 40-50%
     faster on average.

   - bpo-23421(33): Fixed compression in tarfile CLI. Patch by wdv4758h.

   - bpo-23367(34): Fix possible overflows in the unicodedata module.

   - bpo-23361(35): Fix possible overflow in Windows subprocess creation
     code.

   - logging.handlers.QueueListener now takes a respect_handler_level
     keyword argument which, if set to True, will pass messages to
     handlers taking handler levels into account.

   - bpo-19705(36): turtledemo now has a visual sorting algorithm demo.
     Original patch from Jason Yeo.

   - bpo-23801(37): Fix issue where cgi.FieldStorage did not always
     ignore the entire preamble to a multipart body.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22524

   (2) https://peps.python.org/pep-0471/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=23103

   (4) https://bugs.python.org/issue?@action=redirect&bpo=21793

   (5) https://bugs.python.org/issue?@action=redirect&bpo=23476

   (6) https://bugs.python.org/issue?@action=redirect&bpo=23576

   (7) https://bugs.python.org/issue?@action=redirect&bpo=23504

   (8) https://bugs.python.org/issue?@action=redirect&bpo=23563

   (9) https://bugs.python.org/issue?@action=redirect&bpo=7830

   (10) https://bugs.python.org/issue?@action=redirect&bpo=20204

   (11) https://bugs.python.org/issue?@action=redirect&bpo=19980

   (12) https://bugs.python.org/issue?@action=redirect&bpo=23521

   (13) https://bugs.python.org/issue?@action=redirect&bpo=21619

   (14) https://bugs.python.org/issue?@action=redirect&bpo=22936

   (15) https://bugs.python.org/issue?@action=redirect&bpo=15955

   (16) https://bugs.python.org/issue?@action=redirect&bpo=6639

   (17) https://bugs.python.org/issue?@action=redirect&bpo=814253

   (18) https://bugs.python.org/issue?@action=redirect&bpo=9179

   (19) https://bugs.python.org/issue?@action=redirect&bpo=23215

   (20) https://bugs.python.org/issue?@action=redirect&bpo=5700

   (21) https://bugs.python.org/issue?@action=redirect&bpo=23374

   (22) https://bugs.python.org/issue?@action=redirect&bpo=23481

   (23) https://bugs.python.org/issue?@action=redirect&bpo=21548

   (24) https://bugs.python.org/issue?@action=redirect&bpo=22885

   (25) https://bugs.python.org/issue?@action=redirect&bpo=23239

   (26) https://bugs.python.org/issue?@action=redirect&bpo=23146

   (27) https://bugs.python.org/issue?@action=redirect&bpo=23096

   (28) https://bugs.python.org/issue?@action=redirect&bpo=19105

   (29) https://bugs.python.org/issue?@action=redirect&bpo=14910

   (30) https://bugs.python.org/issue?@action=redirect&bpo=21717

   (31) https://bugs.python.org/issue?@action=redirect&bpo=23344

   (32) https://bugs.python.org/issue?@action=redirect&bpo=20416

   (33) https://bugs.python.org/issue?@action=redirect&bpo=23421

   (34) https://bugs.python.org/issue?@action=redirect&bpo=23367

   (35) https://bugs.python.org/issue?@action=redirect&bpo=23361

   (36) https://bugs.python.org/issue?@action=redirect&bpo=19705

   (37) https://bugs.python.org/issue?@action=redirect&bpo=23801


File: python.info,  Node: Build<85>,  Next: C API<68>,  Prev: Library<92>,  Up: Python 3 5 0 alpha 2

1.23.106.3 Build
................

   - bpo-23445(1): pydebug builds now use "gcc -Og" where possible, to
     make the resulting executable faster.

   - bpo-23686(2): Update OS X 10.5 installer build to use OpenSSL
     1.0.2a.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23445

   (2) https://bugs.python.org/issue?@action=redirect&bpo=23686


File: python.info,  Node: C API<68>,  Next: Windows<70>,  Prev: Build<85>,  Up: Python 3 5 0 alpha 2

1.23.106.4 C API
................

   - bpo-20204(1): Deprecation warning is now raised for builtin types
     without the __module__ attribute.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=20204


File: python.info,  Node: Windows<70>,  Prev: C API<68>,  Up: Python 3 5 0 alpha 2

1.23.106.5 Windows
..................

   - bpo-23465(1): Implement PEP 486(2) - Make the Python Launcher aware
     of virtual environments.  Patch by Paul Moore.

   - bpo-23437(3): Make user scripts directory versioned on Windows.
     Patch by Paul Moore.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23465

   (2) https://peps.python.org/pep-0486/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=23437


File: python.info,  Node: Python 3 5 0 alpha 1,  Prev: Python 3 5 0 alpha 2,  Up: Changelog（更動日誌）

1.23.107 Python 3.5.0 alpha 1
-----------------------------

'Release date: 2015-02-08'

* Menu:

* Core and Builtins: Core and Builtins<94>.
* Library: Library<93>.
* IDLE: IDLE<61>.
* Build: Build<86>.
* C API: C API<69>.
* Documentation: Documentation<72>.
* Tests: Tests<79>.
* Tools/Demos: Tools/Demos<47>.
* Windows: Windows<71>.


File: python.info,  Node: Core and Builtins<94>,  Next: Library<93>,  Up: Python 3 5 0 alpha 1

1.23.107.1 Core and Builtins
............................

   - bpo-23285(1): PEP 475 - EINTR handling.

   - bpo-22735(2): Fix many edge cases (including crashes) involving
     custom mro() implementations.

   - bpo-22896(3): Avoid using PyObject_AsCharBuffer(),
     PyObject_AsReadBuffer() and PyObject_AsWriteBuffer().

   - bpo-21295(4): Revert some changes (bpo-16795(5)) to AST line
     numbers and column offsets that constituted a regression.

   - bpo-22986(6): Allow changing an object's __class__ between a
     dynamic type and static type in some cases.

   - bpo-15859(7): PyUnicode_EncodeFSDefault(), PyUnicode_EncodeMBCS()
     and PyUnicode_EncodeCodePage() now raise an exception if the object
     is not a Unicode object.  For PyUnicode_EncodeFSDefault(), it was
     already the case on platforms other than Windows.  Patch written by
     Campbell Barton.

   - bpo-21408(8): The default __ne__() now returns NotImplemented if
     __eq__() returned NotImplemented.  Original patch by Martin Panter.

   - bpo-23321(9): Fixed a crash in str.decode() when error handler
     returned replacement string longer than malformed input data.

   - bpo-22286(10): The "backslashreplace" error handlers now works with
     decoding and translating.

   - bpo-23253(11): Delay-load ShellExecute[AW] in os.startfile for
     reduced startup overhead on Windows.

   - bpo-22038(12): pyatomic.h now uses stdatomic.h or GCC built-in
     functions for atomic memory access if available.  Patch written by
     Vitor de Lima and Gustavo Temple.

   - bpo-20284(13): %-interpolation (aka printf) formatting added for
     bytes and bytearray.

   - bpo-23048(14): Fix jumping out of an infinite while loop in the
     pdb.

   - bpo-20335(15): bytes constructor now raises TypeError when encoding
     or errors is specified with non-string argument.  Based on patch by
     Renaud Blanch.

   - bpo-22834(16): If the current working directory ends up being set
     to a non-existent directory then import will no longer raise
     FileNotFoundError.

   - bpo-22869(17): Move the interpreter startup & shutdown code to a
     new dedicated pylifecycle.c module

   - bpo-22847(18): Improve method cache efficiency.

   - bpo-22335(19): Fix crash when trying to enlarge a bytearray to
     0x7fffffff bytes on a 32-bit platform.

   - bpo-22653(20): Fix an assertion failure in debug mode when doing a
     reentrant dict insertion in debug mode.

   - bpo-22643(21): Fix integer overflow in Unicode case operations
     (upper, lower, title, swapcase, casefold).

   - bpo-17636(22): Circular imports involving relative imports are now
     supported.

   - bpo-22604(23): Fix assertion error in debug mode when dividing a
     complex number by (nan+0j).

   - bpo-21052(24): Do not raise ImportWarning when sys.path_hooks or
     sys.meta_path are set to None.

   - bpo-16518(25): Use 'bytes-like object required' in error messages
     that previously used the far more cryptic "'x' does not support the
     buffer protocol.

   - bpo-22470(26): Fixed integer overflow issues in "backslashreplace",
     "xmlcharrefreplace", and "surrogatepass" error handlers.

   - bpo-22540(27): speed up ‘PyObject_IsInstance’ and
     ‘PyObject_IsSubclass’ in the common case that the second argument
     has metaclass ‘type’.

   - bpo-18711(28): Add a new ‘PyErr_FormatV’ function, similar to
     ‘PyErr_Format’ but accepting a ‘va_list’ argument.

   - bpo-22520(29): Fix overflow checking when generating the repr of a
     unicode object.

   - bpo-22519(30): Fix overflow checking in PyBytes_Repr.

   - bpo-22518(31): Fix integer overflow issues in latin-1 encoding.

   - bpo-16324(32): _charset parameter of MIMEText now also accepts
     email.charset.Charset instances.  Initial patch by Claude Paroz.

   - bpo-1764286(33): Fix inspect.getsource() to support decorated
     functions.  Patch by Claudiu Popa.

   - bpo-18554(34): os.__all__ includes posix functions.

   - bpo-21391(35): Use os.path.abspath in the shutil module.

   - bpo-11471(36): avoid generating a JUMP_FORWARD instruction at the
     end of an if-block if there is no else-clause.  Original patch by
     Eugene Toder.

   - bpo-22215(37): Now ValueError is raised instead of TypeError when
     str or bytes argument contains not permitted null character or
     byte.

   - bpo-22258(38): Fix the internal function set_inheritable() on
     Illumos.  This platform exposes the function ‘ioctl(FIOCLEX)’, but
     calling it fails with errno is ENOTTY: "Inappropriate ioctl for
     device".  set_inheritable() now falls back to the slower ‘fcntl()’
     (‘F_GETFD’ and then ‘F_SETFD’).

   - bpo-21389(39): Displaying the __qualname__ of the underlying
     function in the repr of a bound method.

   - bpo-22206(40): Using pthread, PyThread_create_key() now sets errno
     to ENOMEM and returns -1 (error) on integer overflow.

   - bpo-20184(41): Argument Clinic based signature introspection added
     for 30 of the builtin functions.

   - bpo-22116(42): C functions and methods (of the
     'builtin_function_or_method' type) can now be weakref'ed.  Patch by
     Wei Wu.

   - bpo-22077(43): Improve index error messages for bytearrays, bytes,
     lists, and tuples by adding 'or slices'.  Added ', not <typename>'
     for bytearrays.  Original patch by Claudiu Popa.

   - bpo-20179(44): Apply Argument Clinic to bytes and bytearray.  Patch
     by Tal Einat.

   - bpo-22082(45): Clear interned strings in slotdefs.

   - Upgrade Unicode database to Unicode 7.0.0.

   - bpo-21897(46): Fix a crash with the f_locals attribute with closure
     variables when frame.clear() has been called.

   - bpo-21205(47): Add a new ‘__qualname__’ attribute to generator, the
     qualified name, and use it in the representation of a generator
     (‘repr(gen)’).  The default name of the generator (‘__name__’
     attribute) is now get from the function instead of the code.  Use
     ‘gen.gi_code.co_name’ to get the name of the code.

   - bpo-21669(48): With the aid of heuristics in SyntaxError.__init__,
     the parser now attempts to generate more meaningful (or at least
     more search engine friendly) error messages when "exec" and "print"
     are used as statements.

   - bpo-21642(49): In the conditional if-else expression, allow an
     integer written with no space between itself and the ‘else’ keyword
     (e.g.  ‘True if 42else False’) to be valid syntax.

   - bpo-21523(50): Fix over-pessimistic computation of the stack effect
     of some opcodes in the compiler.  This also fixes a quadratic
     compilation time issue noticeable when compiling code with a large
     number of "and" and "or" operators.

   - bpo-21418(51): Fix a crash in the builtin function super() when
     called without argument and without current frame (ex: embedded
     Python).

   - bpo-21425(52): Fix flushing of standard streams in the interactive
     interpreter.

   - bpo-21435(53): In rare cases, when running finalizers on objects in
     cyclic trash a bad pointer dereference could occur due to a subtle
     flaw in internal iteration logic.

   - bpo-21377(54): PyBytes_Concat() now tries to concatenate in-place
     when the first argument has a reference count of 1.  Patch by
     Nikolaus Rath.

   - bpo-20355(55): -W command line options now have higher priority
     than the PYTHONWARNINGS environment variable.  Patch by Arfrever.

   - bpo-21274(56): Define PATH_MAX for GNU/Hurd in Python/pythonrun.c.

   - bpo-20904(57): Support setting FPU precision on m68k.

   - bpo-21209(58): Fix sending tuples to custom generator objects with
     the yield from syntax.

   - bpo-21193(59): pow(a, b, c) now raises ValueError rather than
     TypeError when b is negative.  Patch by Josh Rosenberg.

   - bpo-21176(60): PEP 465: Add the '@' operator for matrix
     multiplication.

   - bpo-21134(61): Fix segfault when str is called on an uninitialized
     UnicodeEncodeError, UnicodeDecodeError, or UnicodeTranslateError
     object.

   - bpo-19537(62): Fix PyUnicode_DATA() alignment under m68k.  Patch by
     Andreas Schwab.

   - bpo-20929(63): Add a type cast to avoid shifting a negative number.

   - bpo-20731(64): Properly position in source code files even if they
     are opened in text mode.  Patch by Serhiy Storchaka.

   - bpo-20637(65): Key-sharing now also works for instance dictionaries
     of subclasses.  Patch by Peter Ingebretson.

   - bpo-8297(66): Attributes missing from modules now include the
     module name in the error text.  Original patch by ysj.ray.

   - bpo-19995(67): %c, %o, %x, and %X now raise TypeError on
     non-integer input.

   - bpo-19655(68): The ASDL parser - used by the build process to
     generate code for managing the Python AST in C - was rewritten.
     The new parser is self contained and does not require to carry long
     the spark.py parser-generator library; spark.py was removed from
     the source base.

   - bpo-12546(69): Allow ‘\x00’ to be used as a fill character when
     using str, int, float, and complex __format__ methods.

   - bpo-20480(70): Add ipaddress.reverse_pointer.  Patch by Leon Weber.

   - bpo-13598(71): Modify string.Formatter to support auto-numbering of
     replacement fields.  It now matches the behavior of str.format() in
     this regard.  Patches by Phil Elson and Ramchandra Apte.

   - bpo-8931(72): Make alternate formatting ('#') for type 'c' raise an
     exception.  In versions prior to 3.5, '#' with 'c' had no effect.
     Now specifying it is an error.  Patch by Torsten Landschoff.

   - bpo-23165(73): Perform overflow checks before allocating memory in
     the _Py_char2wchar function.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23285

   (2) https://bugs.python.org/issue?@action=redirect&bpo=22735

   (3) https://bugs.python.org/issue?@action=redirect&bpo=22896

   (4) https://bugs.python.org/issue?@action=redirect&bpo=21295

   (5) https://bugs.python.org/issue?@action=redirect&bpo=16795

   (6) https://bugs.python.org/issue?@action=redirect&bpo=22986

   (7) https://bugs.python.org/issue?@action=redirect&bpo=15859

   (8) https://bugs.python.org/issue?@action=redirect&bpo=21408

   (9) https://bugs.python.org/issue?@action=redirect&bpo=23321

   (10) https://bugs.python.org/issue?@action=redirect&bpo=22286

   (11) https://bugs.python.org/issue?@action=redirect&bpo=23253

   (12) https://bugs.python.org/issue?@action=redirect&bpo=22038

   (13) https://bugs.python.org/issue?@action=redirect&bpo=20284

   (14) https://bugs.python.org/issue?@action=redirect&bpo=23048

   (15) https://bugs.python.org/issue?@action=redirect&bpo=20335

   (16) https://bugs.python.org/issue?@action=redirect&bpo=22834

   (17) https://bugs.python.org/issue?@action=redirect&bpo=22869

   (18) https://bugs.python.org/issue?@action=redirect&bpo=22847

   (19) https://bugs.python.org/issue?@action=redirect&bpo=22335

   (20) https://bugs.python.org/issue?@action=redirect&bpo=22653

   (21) https://bugs.python.org/issue?@action=redirect&bpo=22643

   (22) https://bugs.python.org/issue?@action=redirect&bpo=17636

   (23) https://bugs.python.org/issue?@action=redirect&bpo=22604

   (24) https://bugs.python.org/issue?@action=redirect&bpo=21052

   (25) https://bugs.python.org/issue?@action=redirect&bpo=16518

   (26) https://bugs.python.org/issue?@action=redirect&bpo=22470

   (27) https://bugs.python.org/issue?@action=redirect&bpo=22540

   (28) https://bugs.python.org/issue?@action=redirect&bpo=18711

   (29) https://bugs.python.org/issue?@action=redirect&bpo=22520

   (30) https://bugs.python.org/issue?@action=redirect&bpo=22519

   (31) https://bugs.python.org/issue?@action=redirect&bpo=22518

   (32) https://bugs.python.org/issue?@action=redirect&bpo=16324

   (33) https://bugs.python.org/issue?@action=redirect&bpo=1764286

   (34) https://bugs.python.org/issue?@action=redirect&bpo=18554

   (35) https://bugs.python.org/issue?@action=redirect&bpo=21391

   (36) https://bugs.python.org/issue?@action=redirect&bpo=11471

   (37) https://bugs.python.org/issue?@action=redirect&bpo=22215

   (38) https://bugs.python.org/issue?@action=redirect&bpo=22258

   (39) https://bugs.python.org/issue?@action=redirect&bpo=21389

   (40) https://bugs.python.org/issue?@action=redirect&bpo=22206

   (41) https://bugs.python.org/issue?@action=redirect&bpo=20184

   (42) https://bugs.python.org/issue?@action=redirect&bpo=22116

   (43) https://bugs.python.org/issue?@action=redirect&bpo=22077

   (44) https://bugs.python.org/issue?@action=redirect&bpo=20179

   (45) https://bugs.python.org/issue?@action=redirect&bpo=22082

   (46) https://bugs.python.org/issue?@action=redirect&bpo=21897

   (47) https://bugs.python.org/issue?@action=redirect&bpo=21205

   (48) https://bugs.python.org/issue?@action=redirect&bpo=21669

   (49) https://bugs.python.org/issue?@action=redirect&bpo=21642

   (50) https://bugs.python.org/issue?@action=redirect&bpo=21523

   (51) https://bugs.python.org/issue?@action=redirect&bpo=21418

   (52) https://bugs.python.org/issue?@action=redirect&bpo=21425

   (53) https://bugs.python.org/issue?@action=redirect&bpo=21435

   (54) https://bugs.python.org/issue?@action=redirect&bpo=21377

   (55) https://bugs.python.org/issue?@action=redirect&bpo=20355

   (56) https://bugs.python.org/issue?@action=redirect&bpo=21274

   (57) https://bugs.python.org/issue?@action=redirect&bpo=20904

   (58) https://bugs.python.org/issue?@action=redirect&bpo=21209

   (59) https://bugs.python.org/issue?@action=redirect&bpo=21193

   (60) https://bugs.python.org/issue?@action=redirect&bpo=21176

   (61) https://bugs.python.org/issue?@action=redirect&bpo=21134

   (62) https://bugs.python.org/issue?@action=redirect&bpo=19537

   (63) https://bugs.python.org/issue?@action=redirect&bpo=20929

   (64) https://bugs.python.org/issue?@action=redirect&bpo=20731

   (65) https://bugs.python.org/issue?@action=redirect&bpo=20637

   (66) https://bugs.python.org/issue?@action=redirect&bpo=8297

   (67) https://bugs.python.org/issue?@action=redirect&bpo=19995

   (68) https://bugs.python.org/issue?@action=redirect&bpo=19655

   (69) https://bugs.python.org/issue?@action=redirect&bpo=12546

   (70) https://bugs.python.org/issue?@action=redirect&bpo=20480

   (71) https://bugs.python.org/issue?@action=redirect&bpo=13598

   (72) https://bugs.python.org/issue?@action=redirect&bpo=8931

   (73) https://bugs.python.org/issue?@action=redirect&bpo=23165


File: python.info,  Node: Library<93>,  Next: IDLE<61>,  Prev: Core and Builtins<94>,  Up: Python 3 5 0 alpha 1

1.23.107.2 Library
..................

   - bpo-23399(1): pyvenv creates relative symlinks where possible.

   - bpo-20289(2): cgi.FieldStorage() now supports the context
     management protocol.

   - bpo-13128(3): Print response headers for CONNECT requests when
     debuglevel > 0.  Patch by Demian Brecht.

   - bpo-15381(4): Optimized io.BytesIO to make less allocations and
     copyings.

   - bpo-22818(5): Splitting on a pattern that could match an empty
     string now raises a warning.  Patterns that can only match empty
     strings are now rejected.

   - bpo-23099(6): Closing io.BytesIO with exported buffer is rejected
     now to prevent corrupting exported buffer.

   - bpo-23326(7): Removed __ne__ implementations.  Since fixing default
     __ne__ implementation in bpo-21408(8) they are redundant.

   - bpo-23363(9): Fix possible overflow in itertools.permutations.

   - bpo-23364(10): Fix possible overflow in itertools.product.

   - bpo-23366(11): Fixed possible integer overflow in
     itertools.combinations.

   - bpo-23369(12): Fixed possible integer overflow in
     _json.encode_basestring_ascii.

   - bpo-23353(13): Fix the exception handling of generators in
     PyEval_EvalFrameEx().  At entry, save or swap the exception state
     even if PyEval_EvalFrameEx() is called with throwflag=0.  At exit,
     the exception state is now always restored or swapped, not only if
     why is WHY_YIELD or WHY_RETURN. Patch co-written with Antoine
     Pitrou.

   - bpo-14099(14): Restored support of writing ZIP files to tellable
     but non-seekable streams.

   - bpo-14099(15): Writing to ZipFile and reading multiple ZipExtFiles
     is threadsafe now.

   - bpo-19361(16): JSON decoder now raises JSONDecodeError instead of
     ValueError.

   - bpo-18518(17): timeit now rejects statements which can't be
     compiled outside a function or a loop (e.g.  "return" or "break").

   - bpo-23094(18): Fixed readline with frames in Python implementation
     of pickle.

   - bpo-23268(19): Fixed bugs in the comparison of ipaddress classes.

   - bpo-21408(20): Removed incorrect implementations of __ne__() which
     didn't returned NotImplemented if __eq__() returned NotImplemented.
     The default __ne__() now works correctly.

   - bpo-19996(21): ‘email.feedparser.FeedParser’ now handles
     (malformed) headers with no key rather than assuming the body has
     started.

   - bpo-20188(22): Support Application-Layer Protocol Negotiation
     (ALPN) in the ssl module.

   - bpo-23133(23): Pickling of ipaddress objects now produces more
     compact and portable representation.

   - bpo-23248(24): Update ssl error codes from latest OpenSSL git
     master.

   - bpo-23266(25): Much faster implementation of
     ipaddress.collapse_addresses() when there are many non-consecutive
     addresses.

   - bpo-23098(26): 64-bit dev_t is now supported in the os module.

   - bpo-21817(27): When an exception is raised in a task submitted to a
     ProcessPoolExecutor, the remote traceback is now displayed in the
     parent process.  Patch by Claudiu Popa.

   - bpo-15955(28): Add an option to limit output size when
     decompressing LZMA data.  Patch by Nikolaus Rath and Martin Panter.

   - bpo-23250(29): In the http.cookies module, capitalize "HttpOnly"
     and "Secure" as they are written in the standard.

   - bpo-23063(30): In the distutils' check command, fix parsing of reST
     with code or code-block directives.

   - bpo-23209(31): selectors.BaseSelector.get_key() now raises a
     RuntimeError if the selector is closed.  And
     selectors.BaseSelector.close() now clears its internal reference to
     the selector mapping to break a reference cycle.  Initial patch
     written by Martin Richard.  (See also: bpo-23225(32))

   - bpo-17911(33): Provide a way to seed the linecache for a PEP-302
     module without actually loading the code.

   - bpo-17911(34): Provide a new object API for traceback, including
     the ability to not lookup lines at all until the traceback is
     actually rendered, without any trace of the original objects being
     kept alive.

   - bpo-19777(35): Provide a home() classmethod on Path objects.
     Contributed by Victor Salgado and Mayank Tripathi.

   - bpo-23206(36): Make ‘json.dumps(..., ensure_ascii=False)’ as fast
     as the default case of ‘ensure_ascii=True’.  Patch by Naoki Inada.

   - bpo-23185(37): Add math.inf and math.nan constants.

   - bpo-23186(38): Add ssl.SSLObject.shared_ciphers() and
     ssl.SSLSocket.shared_ciphers() to fetch the client's list ciphers
     sent at handshake.

   - bpo-23143(39): Remove compatibility with OpenSSLs older than 0.9.8.

   - bpo-23132(40): Improve performance and introspection support of
     comparison methods created by functool.total_ordering.

   - bpo-19776(41): Add an expanduser() method on Path objects.

   - bpo-23112(42): Fix SimpleHTTPServer to correctly carry the query
     string and fragment when it redirects to add a trailing slash.

   - bpo-21793(43): Added http.HTTPStatus enums (i.e.  HTTPStatus.OK,
     HTTPStatus.NOT_FOUND). Patch by Demian Brecht.

   - bpo-23093(44): In the io, module allow more operations to work on
     detached streams.

   - bpo-23111(45): In the ftplib, make ssl.PROTOCOL_SSLv23 the default
     protocol version.

   - bpo-22585(46): On OpenBSD 5.6 and newer, os.urandom() now calls
     getentropy(), instead of reading /dev/urandom, to get pseudo-random
     bytes.

   - bpo-19104(47): pprint now produces evaluable output for wrapped
     strings.

   - bpo-23071(48): Added missing names to codecs.__all__.  Patch by
     Martin Panter.

   - bpo-22783(49): Pickling now uses the NEWOBJ opcode instead of the
     NEWOBJ_EX opcode if possible.

   - bpo-15513(50): Added a __sizeof__ implementation for pickle
     classes.

   - bpo-19858(51): pickletools.optimize() now aware of the MEMOIZE
     opcode, can produce more compact result and no longer produces
     invalid output if input data contains MEMOIZE opcodes together with
     PUT or BINPUT opcodes.

   - bpo-22095(52): Fixed HTTPConnection.set_tunnel with default port.
     The port value in the host header was set to "None".  Patch by
     Demian Brecht.

   - bpo-23016(53): A warning no longer produces an AttributeError when
     the program is run with pythonw.exe.

   - bpo-21775(54): shutil.copytree(): fix crash when copying to VFAT.
     An exception handler assumed that OSError objects always have a
     'winerror' attribute.  That is not the case, so the exception
     handler itself raised AttributeError when run on Linux (and,
     presumably, any other non-Windows OS). Patch by Greg Ward.

   - bpo-1218234(55): Fix inspect.getsource() to load updated source of
     reloaded module.  Initial patch by Berker Peksag.

   - bpo-21740(56): Support wrapped callables in doctest.  Patch by
     Claudiu Popa.

   - bpo-23009(57): Make sure selectors.EpollSelector.select() works
     when no FD is registered.

   - bpo-22959(58): In the constructor of http.client.HTTPSConnection,
     prefer the context's check_hostname attribute over the
     'check_hostname' parameter.

   - bpo-22696(59): Add function *note sys.is_finalizing(): a32. to know
     about interpreter shutdown.

   - bpo-16043(60): Add a default limit for the amount of data
     xmlrpclib.gzip_decode will return.  This resolves
     CVE-2013-1753(61).

   - bpo-14099(62): ZipFile.open() no longer reopen the underlying file.
     Objects returned by ZipFile.open() can now operate independently of
     the ZipFile even if the ZipFile was created by passing in a
     file-like object as the first argument to the constructor.

   - bpo-22966(63): Fix __pycache__ pyc file name clobber when
     pyc_compile is asked to compile a source file containing multiple
     dots in the source file name.

   - bpo-21971(64): Update turtledemo doc and add module to the index.

   - bpo-21032(65): Fixed socket leak if HTTPConnection.getresponse()
     fails.  Original patch by Martin Panter.

   - bpo-22407(66): Deprecated the use of re.LOCALE flag with str
     patterns or re.ASCII. It was newer worked.

   - bpo-22902(67): The "ip" command is now used on Linux to determine
     MAC address in uuid.getnode().  Pach by Bruno Cauet.

   - bpo-22960(68): Add a context argument to xmlrpclib.ServerProxy
     constructor.

   - bpo-22389(69): Add contextlib.redirect_stderr().

   - bpo-21356(70): Make ssl.RAND_egd() optional to support LibreSSL.
     The availability of the function is checked during the compilation.
     Patch written by Bernard Spil.

   - bpo-22915(71): SAX parser now supports files opened with file
     descriptor or bytes path.

   - bpo-22609(72): Constructors and update methods of mapping classes
     in the collections module now accept the self keyword argument.

   - bpo-22940(73): Add readline.append_history_file.

   - bpo-19676(74): Added the "namereplace" error handler.

   - bpo-22788(75): Add 'context' parameter to
     logging.handlers.HTTPHandler.

   - bpo-22921(76): Allow SSLContext to take the 'hostname' parameter
     even if OpenSSL doesn't support SNI.

   - bpo-22894(77): TestCase.subTest() would cause the test suite to be
     stopped when in failfast mode, even in the absence of failures.

   - bpo-22796(78): HTTP cookie parsing is now stricter, in order to
     protect against potential injection attacks.

   - bpo-22370(79): Windows detection in pathlib is now more robust.

   - bpo-22841(80): Reject coroutines in asyncio add_signal_handler().
     Patch by Ludovic.Gasc.

   - bpo-19494(81): Added urllib.request.HTTPBasicPriorAuthHandler.
     Patch by Matej Cepl.

   - bpo-22578(82): Added attributes to the re.error class.

   - bpo-22849(83): Fix possible double free in the io.TextIOWrapper
     constructor.

   - bpo-12728(84): Different Unicode characters having the same
     uppercase but different lowercase are now matched in
     case-insensitive regular expressions.

   - bpo-22821(85): Fixed fcntl() with integer argument on 64-bit
     big-endian platforms.

   - bpo-21650(86): Add an ‘--sort-keys’ option to ‘json.tool’ CLI.

   - bpo-22824(87): Updated reprlib output format for sets to use set
     literals.  Patch contributed by Berker Peksag.

   - bpo-22824(88): Updated reprlib output format for arrays to display
     empty arrays without an unnecessary empty list.  Suggested by
     Serhiy Storchaka.

   - bpo-22406(89): Fixed the uu_codec codec incorrectly ported to 3.x.
     Based on patch by Martin Panter.

   - bpo-17293(90): uuid.getnode() now determines MAC address on AIX
     using netstat.  Based on patch by Aivars Kalvāns.

   - bpo-22769(91): Fixed ttk.Treeview.tag_has() when called without
     arguments.

   - bpo-22417(92): Verify certificates by default in httplib (PEP 476).

   - bpo-22775(93): Fixed unpickling of http.cookies.SimpleCookie with
     protocol 2 and above.  Patch by Tim Graham.

   - bpo-22776(94): Brought excluded code into the scope of a try block
     in SysLogHandler.emit().

   - bpo-22665(95): Add missing get_terminal_size and SameFileError to
     shutil.__all__.

   - bpo-6623(96): Remove deprecated Netrc class in the ftplib module.
     Patch by Matt Chaput.

   - bpo-17381(97): Fixed handling of case-insensitive ranges in regular
     expressions.

   - bpo-22410(98): Module level functions in the re module now cache
     compiled locale-dependent regular expressions taking into account
     the locale.

   - bpo-22759(99): Query methods on pathlib.Path() (exists(), is_dir(),
     etc.)  now return False when the underlying stat call raises
     NotADirectoryError.

   - bpo-8876(100): distutils now falls back to copying files when hard
     linking doesn't work.  This allows use with special filesystems
     such as VirtualBox shared folders.

   - bpo-22217(101): Implemented reprs of classes in the zipfile module.

   - bpo-22457(102): Honour load_tests in the start_dir of discovery.

   - bpo-18216(103): gettext now raises an error when a .mo file has an
     unsupported major version number.  Patch by Aaron Hill.

   - bpo-13918(104): Provide a locale.delocalize() function which can
     remove locale-specific number formatting from a string representing
     a number, without then converting it to a specific type.  Patch by
     Cédric Krier.

   - bpo-22676(105): Make the pickling of global objects which don't
     have a __module__ attribute less slow.

   - bpo-18853(106): Fixed ResourceWarning in shlex.__nain__.

   - bpo-9351(107): Defaults set with set_defaults on an argparse
     subparser are no longer ignored when also set on the parent parser.

   - bpo-7559(108): unittest test loading ImportErrors are reported as
     import errors with their import exception rather than as attribute
     errors after the import has already failed.

   - bpo-19746(109): Make it possible to examine the errors from
     unittest discovery without executing the test suite.  The new
     ‘errors’ attribute on ‘TestLoader’ exposes these non-fatal errors
     encountered during discovery.

   - bpo-21991(110): Make email.headerregistry's header 'params'
     attributes be read-only (MappingProxyType).  Previously the
     dictionary was modifiable but a new one was created on each access
     of the attribute.

   - bpo-22638(111): SSLv3 is now disabled throughout the standard
     library.  It can still be enabled by instantiating a SSLContext
     manually.

   - bpo-22641(112): In asyncio, the default SSL context for client
     connections is now created using ssl.create_default_context(), for
     stronger security.

   - bpo-17401(113): Include closefd in io.FileIO repr.

   - bpo-21338(114): Add silent mode for compileall.  quiet parameters
     of compile_{dir, file, path} functions now have a multilevel value.
     Also, -q option of the CLI now have a multilevel value.  Patch by
     Thomas Kluyver.

   - bpo-20152(115): Convert the array and cmath modules to Argument
     Clinic.

   - bpo-18643(116): Add socket.socketpair() on Windows.

   - bpo-22435(117): Fix a file descriptor leak when socketserver bind
     fails.

   - bpo-13096(118): Fixed segfault in CTypes POINTER handling of large
     values.

   - bpo-11694(119): Raise ConversionError in xdrlib as documented.
     Patch by Filip Gruszczyński and Claudiu Popa.

   - bpo-19380(120): Optimized parsing of regular expressions.

   - bpo-1519638(121): Now unmatched groups are replaced with empty
     strings in re.sub() and re.subn().

   - bpo-18615(122): sndhdr.what/whathdr now return a namedtuple.

   - bpo-22462(123): Fix pyexpat's creation of a dummy frame to make it
     appear in exception tracebacks.

   - bpo-21965(124): Add support for in-memory SSL to the ssl module.
     Patch by Geert Jansen.

   - bpo-21173(125): Fix len() on a WeakKeyDictionary when .clear() was
     called with an iterator alive.

   - bpo-11866(126): Eliminated race condition in the computation of
     names for new threads.

   - bpo-21905(127): Avoid RuntimeError in pickle.whichmodule() when
     sys.modules is mutated while iterating.  Patch by Olivier Grisel.

   - bpo-11271(128): concurrent.futures.Executor.map() now takes a
     'chunksize' argument to allow batching of tasks in child processes
     and improve performance of ProcessPoolExecutor.  Patch by Dan
     O'Reilly.

   - bpo-21883(129): os.path.join() and os.path.relpath() now raise a
     TypeError with more helpful error message for unsupported or
     mismatched types of arguments.

   - bpo-22219(130): The zipfile module CLI now adds entries for
     directories (including empty directories) in ZIP file.

   - bpo-22449(131): In the ssl.SSLContext.load_default_certs, consult
     the environmental variables SSL_CERT_DIR and SSL_CERT_FILE on
     Windows.

   - bpo-22508(132): The email.__version__ variable has been removed;
     the email code is no longer shipped separately from the stdlib, and
     __version__ hasn't been updated in several releases.

   - bpo-20076(133): Added non derived UTF-8 aliases to locale aliases
     table.

   - bpo-20079(134): Added locales supported in glibc 2.18 to locale
     alias table.

   - bpo-20218(135): Added convenience methods read_text/write_text and
     read_bytes/ write_bytes to pathlib.Path objects.

   - bpo-22396(136): On 32-bit AIX platform, don't expose
     os.posix_fadvise() nor os.posix_fallocate() because their
     prototypes in system headers are wrong.

   - bpo-22517(137): When an io.BufferedRWPair object is deallocated,
     clear its weakrefs.

   - bpo-22437(138): Number of capturing groups in regular expression is
     no longer limited by 100.

   - bpo-17442(139): InteractiveInterpreter now displays the full
     chained traceback in its showtraceback method, to match the built
     in interactive interpreter.

   - bpo-23392(140): Added tests for marshal C API that works with
     FILE*.

   - bpo-10510(141): distutils register and upload methods now use HTML
     standards compliant CRLF line endings.

   - bpo-9850(142): Fixed macpath.join() for empty first component.
     Patch by Oleg Oshmyan.

   - bpo-5309(143): distutils' build and build_ext commands now accept a
     ‘-j’ option to enable parallel building of extension modules.

   - bpo-22448(144): Improve canceled timer handles cleanup to prevent
     unbound memory usage.  Patch by Joshua Moore-Oliva.

   - bpo-22427(145): TemporaryDirectory no longer attempts to clean up
     twice when used in the with statement in generator.

   - bpo-22362(146): Forbidden ambiguous octal escapes out of range
     0-0o377 in regular expressions.

   - bpo-20912(147): Now directories added to ZIP file have correct Unix
     and MS-DOS directory attributes.

   - bpo-21866(148): ZipFile.close() no longer writes ZIP64 central
     directory records if allowZip64 is false.

   - bpo-22278(149): Fix urljoin problem with relative urls, a
     regression observed after changes to issue22118 were submitted.

   - bpo-22415(150): Fixed debugging output of the GROUPREF_EXISTS
     opcode in the re module.  Removed trailing spaces in debugging
     output.

   - bpo-22423(151): Unhandled exception in thread no longer causes
     unhandled AttributeError when sys.stderr is None.

   - bpo-21332(152): Ensure that ‘bufsize=1’ in subprocess.Popen()
     selects line buffering, rather than block buffering.  Patch by
     Akira Li.

   - bpo-21091(153): Fix API bug:
     email.message.EmailMessage.is_attachment is now a method.

   - bpo-21079(154): Fix email.message.EmailMessage.is_attachment to
     return the correct result when the header has parameters as well as
     a value.

   - bpo-22247(155): Add NNTPError to nntplib.__all__.

   - bpo-22366(156): urllib.request.urlopen will accept a context object
     (SSLContext) as an argument which will then be used for HTTPS
     connection.  Patch by Alex Gaynor.

   - bpo-4180(157): The warnings registries are now reset when the
     filters are modified.

   - bpo-22419(158): Limit the length of incoming HTTP request in
     wsgiref server to 65536 bytes and send a 414 error code for higher
     lengths.  Patch contributed by Devin Cook.

   - Lax cookie parsing in http.cookies could be a security issue when
     combined with non-standard cookie handling in some web browsers.
     Reported by Sergey Bobrov.

   - bpo-20537(159): logging methods now accept an exception instance as
     well as a Boolean value or exception tuple.  Thanks to Yury
     Selivanov for the patch.

   - bpo-22384(160): An exception in Tkinter callback no longer crashes
     the program when it is run with pythonw.exe.

   - bpo-22168(161): Prevent turtle AttributeError with non-default
     Canvas on OS X.

   - bpo-21147(162): sqlite3 now raises an exception if the request
     contains a null character instead of truncating it.  Based on patch
     by Victor Stinner.

   - bpo-13968(163): The glob module now supports recursive search in
     subdirectories using the ‘**’ pattern.

   - bpo-21951(164): Fixed a crash in Tkinter on AIX when called Tcl
     command with empty string or tuple argument.

   - bpo-21951(165): Tkinter now most likely raises MemoryError instead
     of crash if the memory allocation fails.

   - bpo-22338(166): Fix a crash in the json module on memory allocation
     failure.

   - bpo-12410(167): imaplib.IMAP4 now supports the context management
     protocol.  Original patch by Tarek Ziadé.

   - bpo-21270(168): We now override tuple methods in mock.call objects
     so that they can be used as normal call attributes.

   - bpo-16662(169): ‘load_tests()’ is now unconditionally run when it
     is present in a package's ‘__init__.py’.
     ‘TestLoader.loadTestsFromModule()’ still accepts use_load_tests,
     but it is deprecated and ignored.  A new keyword-only attribute
     ‘pattern’ is added and documented.  Patch given by Robert Collins,
     tweaked by Barry Warsaw.

   - bpo-22226(170): First letter no longer is stripped from the
     "status" key in the result of Treeview.heading().

   - bpo-19524(171): Fixed resource leak in the HTTP connection when an
     invalid response is received.  Patch by Martin Panter.

   - bpo-20421(172): Add a .version() method to SSL sockets exposing the
     actual protocol version in use.

   - bpo-19546(173): configparser exceptions no longer expose
     implementation details.  Chained KeyErrors are removed, which leads
     to cleaner tracebacks.  Patch by Claudiu Popa.

   - bpo-22051(174): turtledemo no longer reloads examples to re-run
     them.  Initialization of variables and gui setup should be done in
     main(), which is called each time a demo is run, but not on import.

   - bpo-21933(175): Turtledemo users can change the code font size with
     a menu selection or control(command) '-' or '+' or
     control-mousewheel.  Original patch by Lita Cho.

   - bpo-21597(176): The separator between the turtledemo text pane and
     the drawing canvas can now be grabbed and dragged with a mouse.
     The code text pane can be widened to easily view or copy the full
     width of the text.  The canvas can be widened on small screens.
     Original patches by Jan Kanis and Lita Cho.

   - bpo-18132(177): Turtledemo buttons no longer disappear when the
     window is shrunk.  Original patches by Jan Kanis and Lita Cho.

   - bpo-22043(178): time.monotonic() is now always available.
     ‘threading.Lock.acquire()’, ‘threading.RLock.acquire()’ and socket
     operations now use a monotonic clock, instead of the system clock,
     when a timeout is used.

   - bpo-21527(179): Add a default number of workers to
     ThreadPoolExecutor equal to 5 times the number of CPUs.  Patch by
     Claudiu Popa.

   - bpo-22216(180): smtplib now resets its state more completely after
     a quit.  The most obvious consequence of the previous behavior was
     a STARTTLS failure during a connect/starttls/quit/connect/starttls
     sequence.

   - bpo-22098(181): ctypes' BigEndianStructure and
     LittleEndianStructure now define an empty __slots__ so that
     subclasses don't always get an instance dict.  Patch by Claudiu
     Popa.

   - bpo-22185(182): Fix an occasional RuntimeError in
     threading.Condition.wait() caused by mutation of the waiters queue
     without holding the lock.  Patch by Doug Zongker.

   - bpo-22287(183): On UNIX, _PyTime_gettimeofday() now uses
     clock_gettime(CLOCK_REALTIME) if available.  As a side effect,
     Python now depends on the librt library on Solaris and on Linux
     (only with glibc older than 2.17).

   - bpo-22182(184): Use e.args to unpack exceptions correctly in
     distutils.file_util.move_file.  Patch by Claudiu Popa.

   - The webbrowser module now uses subprocess's start_new_session=True
     rather than a potentially risky preexec_fn=os.setsid call.

   - bpo-22042(185): signal.set_wakeup_fd(fd) now raises an exception if
     the file descriptor is in blocking mode.

   - bpo-16808(186): inspect.stack() now returns a named tuple instead
     of a tuple.  Patch by Daniel Shahaf.

   - bpo-22236(187): Fixed Tkinter images copying operations in
     NoDefaultRoot mode.

   - bpo-2527(188): Add a 'globals' argument to timeit functions, in
     order to override the globals namespace in which the timed code is
     executed.  Patch by Ben Roberts.

   - bpo-22118(189): Switch urllib.parse to use RFC 3986 semantics for
     the resolution of relative URLs, rather than RFCs 1808 and 2396.
     Patch by Demian Brecht.

   - bpo-21549(190): Added the "members" parameter to TarFile.list().

   - bpo-19628(191): Allow compileall recursion depth to be specified
     with a -r option.

   - bpo-15696(192): Add a __sizeof__ implementation for mmap objects on
     Windows.

   - bpo-22068(193): Avoided reference loops with Variables and Fonts in
     Tkinter.

   - bpo-22165(194): SimpleHTTPRequestHandler now supports undecodable
     file names.

   - bpo-15381(195): Optimized line reading in io.BytesIO.

   - bpo-8797(196): Raise HTTPError on failed Basic Authentication
     immediately.  Initial patch by Sam Bull.

   - bpo-20729(197): Restored the use of lazy
     iterkeys()/itervalues()/iteritems() in the mailbox module.

   - bpo-21448(198): Changed FeedParser feed() to avoid 'O'('n'^2)
     behavior when parsing long line.  Original patch by Raymond
     Hettinger.

   - bpo-22184(199): The functools LRU Cache decorator factory now gives
     an earlier and clearer error message when the user forgets the
     required parameters.

   - bpo-17923(200): glob() patterns ending with a slash no longer match
     non-dirs on AIX. Based on patch by Delhallt.

   - bpo-21725(201): Added support for RFC 6531 (SMTPUTF8) in smtpd.

   - bpo-22176(202): Update the ctypes module's libffi to v3.1.  This
     release adds support for the Linux AArch64 and POWERPC ELF ABIv2
     little endian architectures.

   - bpo-5411(203): Added support for the "xztar" format in the shutil
     module.

   - bpo-21121(204): Don't force 3rd party C extensions to be built with
     -Werror=declaration-after-statement.

   - bpo-21975(205): Fixed crash when using uninitialized sqlite3.Row
     (in particular when unpickling pickled sqlite3.Row).  sqlite3.Row
     is now initialized in the __new__() method.

   - bpo-20170(206): Convert posixmodule to use Argument Clinic.

   - bpo-21539(207): Add an 'exists_ok' argument to ‘Pathlib.mkdir()’ to
     mimic ‘mkdir -p’ and ‘os.makedirs()’ functionality.  When true,
     ignore ‘FileExistsErrors’.  Patch by Berker Peksag.

   - bpo-22127(208): Bypass IDNA for pure-ASCII host names in the socket
     module (in particular for numeric IPs).

   - bpo-21047(209): set the default value for the 'convert_charrefs'
     argument of HTMLParser to True.  Patch by Berker Peksag.

   - Add an __all__ to html.entities.

   - bpo-15114(210): the strict mode and argument of HTMLParser,
     HTMLParser.error, and the HTMLParserError exception have been
     removed.

   - bpo-22085(211): Dropped support of Tk 8.3 in Tkinter.

   - bpo-21580(212): Now Tkinter correctly handles bytes arguments
     passed to Tk.  In particular this allows initializing images from
     binary data.

   - bpo-22003(213): When initialized from a bytes object, io.BytesIO()
     now defers making a copy until it is mutated, improving performance
     and memory use on some use cases.  Patch by David Wilson.

   - bpo-22018(214): On Windows, signal.set_wakeup_fd() now also
     supports sockets.  A side effect is that Python depends to the
     WinSock library.

   - bpo-22054(215): Add os.get_blocking() and os.set_blocking()
     functions to get and set the blocking mode of a file descriptor
     (False if the O_NONBLOCK flag is set, True otherwise).  These
     functions are not available on Windows.

   - bpo-17172(216): Make turtledemo start as active on OS X even when
     run with subprocess.  Patch by Lita Cho.

   - bpo-21704(217): Fix build error for _multiprocessing when
     semaphores are not available.  Patch by Arfrever Frehtes Taifersar
     Arahesis.

   - bpo-20173(218): Convert sha1, sha256, sha512 and md5 to
     ArgumentClinic.  Patch by Vajrasky Kok.

   - Fix repr(_socket.socket) on Windows 64-bit: don't fail with
     OverflowError on closed socket.  repr(socket.socket) already works
     fine.

   - bpo-22033(219): Reprs of most Python implemented classes now
     contain actual class name instead of hardcoded one.

   - bpo-21947(220): The dis module can now disassemble
     generator-iterator objects based on their gi_code attribute.  Patch
     by Clement Rouault.

   - bpo-16133(221): The asynchat.async_chat.handle_read() method now
     ignores BlockingIOError exceptions.

   - bpo-22044(222): Fixed premature DECREF in call_tzinfo_method.
     Patch by Tom Flanagan.

   - bpo-19884(223): readline: Disable the meta modifier key if stdout
     is not a terminal to not write the ANSI sequence ‘"\033[1034h"’
     into stdout.  This sequence is used on some terminal (ex:
     TERM=xterm-256color") to enable support of 8 bit characters.

   - bpo-4350(224): Removed a number of out-of-dated and non-working for
     a long time Tkinter methods.

   - bpo-6167(225): Scrollbar.activate() now returns the name of active
     element if the argument is not specified.  Scrollbar.set() now
     always accepts only 2 arguments.

   - bpo-15275(226): Clean up and speed up the ntpath module.

   - bpo-21888(227): plistlib's load() and loads() now work if the fmt
     parameter is specified.

   - bpo-22032(228): __qualname__ instead of __name__ is now always used
     to format fully qualified class names of Python implemented
     classes.

   - bpo-22031(229): Reprs now always use hexadecimal format with the
     "0x" prefix when contain an id in form " at 0x...".

   - bpo-22018(230): signal.set_wakeup_fd() now raises an OSError
     instead of a ValueError on ‘fstat()’ failure.

   - bpo-21044(231): tarfile.open() now handles fileobj with an integer
     'name' attribute.  Based on patch by Antoine Pietri.

   - bpo-21966(232): Respect -q command-line option when code module is
     ran.

   - bpo-19076(233): Don't pass the redundant 'file' argument to
     self.error().

   - bpo-16382(234): Improve exception message of warnings.warn() for
     bad category.  Initial patch by Phil Elson.

   - bpo-21932(235): os.read() now uses a *note Py_ssize_t(): a03. type
     instead of int for the size to support reading more than 2 GB at
     once.  On Windows, the size is truncated to INT_MAX. As any call to
     os.read(), the OS may read less bytes than the number of requested
     bytes.

   - bpo-21942(236): Fixed source file viewing in pydoc's server mode on
     Windows.

   - bpo-11259(237): asynchat.async_chat().set_terminator() now raises a
     ValueError if the number of received bytes is negative.

   - bpo-12523(238): asynchat.async_chat.push() now raises a TypeError
     if it doesn't get a bytes string

   - bpo-21707(239): Add missing kwonlyargcount argument to
     ModuleFinder.replace_paths_in_code().

   - bpo-20639(240): calling Path.with_suffix('') allows removing the
     suffix again.  Patch by July Tikhonov.

   - bpo-21714(241): Disallow the construction of invalid paths using
     Path.with_name().  Original patch by Antony Lee.

   - bpo-15014(242): Added 'auth' method to smtplib to make implementing
     auth mechanisms simpler, and used it internally in the login
     method.

   - bpo-21151(243): Fixed a segfault in the winreg module when ‘None’
     is passed as a ‘REG_BINARY’ value to SetValueEx.  Patch by John
     Ehresman.

   - bpo-21090(244): io.FileIO.readall() does not ignore I/O errors
     anymore.  Before, it ignored I/O errors if at least the first C
     call read() succeed.

   - bpo-5800(245): headers parameter of wsgiref.headers.Headers is now
     optional.  Initial patch by Pablo Torres Navarrete and SilentGhost.

   - bpo-21781(246): ssl.RAND_add() now supports strings longer than 2
     GB.

   - bpo-21679(247): Prevent extraneous fstat() calls during open().
     Patch by Bohuslav Kabrda.

   - bpo-21863(248): cProfile now displays the module name of C
     extension functions, in addition to their own name.

   - bpo-11453(249): asyncore: emit a ResourceWarning when an unclosed
     file_wrapper object is destroyed.  The destructor now closes the
     file if needed.  The close() method can now be called twice: the
     second call does nothing.

   - bpo-21858(250): Better handling of Python exceptions in the sqlite3
     module.

   - bpo-21476(251): Make sure the email.parser.BytesParser
     TextIOWrapper is discarded after parsing, so the input file isn't
     unexpectedly closed.

   - bpo-20295(252): imghdr now recognizes OpenEXR format images.

   - bpo-21729(253): Used the "with" statement in the dbm.dumb module to
     ensure files closing.  Patch by Claudiu Popa.

   - bpo-21491(254): socketserver: Fix a race condition in child
     processes reaping.

   - bpo-21719(255): Added the ‘st_file_attributes’ field to
     os.stat_result on Windows.

   - bpo-21832(256): Require named tuple inputs to be exact strings.

   - bpo-21722(257): The distutils "upload" command now exits with a
     non-zero return code when uploading fails.  Patch by Martin
     Dengler.

   - bpo-21723(258): asyncio.Queue: support any type of number (ex:
     float) for the maximum size.  Patch written by Vajrasky Kok.

   - bpo-21711(259): support for "site-python" directories has now been
     removed from the site module (it was deprecated in 3.4).

   - bpo-17552(260): new socket.sendfile() method allowing a file to be
     sent over a socket by using high-performance os.sendfile() on UNIX.
     Patch by Giampaolo Rodola'.

   - bpo-18039(261): dbm.dump.open() now always creates a new database
     when the flag has the value 'n'.  Patch by Claudiu Popa.

   - bpo-21326(262): Add a new is_closed() method to
     asyncio.BaseEventLoop.  run_forever() and run_until_complete()
     methods of asyncio.BaseEventLoop now raise an exception if the
     event loop was closed.

   - bpo-21766(263): Prevent a security hole in CGIHTTPServer by URL
     unquoting paths before checking for a CGI script at that path.

   - bpo-21310(264): Fixed possible resource leak in failed open().

   - bpo-21256(265): Printout of keyword args should be in deterministic
     order in a mock function call.  This will help to write better
     doctests.

   - bpo-21677(266): Fixed chaining nonnormalized exceptions in io
     close() methods.

   - bpo-11709(267): Fix the pydoc.help function to not fail when
     sys.stdin is not a valid file.

   - bpo-21515(268): tempfile.TemporaryFile now uses os.O_TMPFILE flag
     is available.

   - bpo-13223(269): Fix pydoc.writedoc so that the HTML documentation
     for methods that use 'self' in the example code is generated
     correctly.

   - bpo-21463(270): In urllib.request, fix pruning of the FTP cache.

   - bpo-21618(271): The subprocess module could fail to close open fds
     that were inherited by the calling process and already higher than
     POSIX resource limits would otherwise allow.  On systems with a
     functioning /proc/self/fd or /dev/fd interface the max is now
     ignored and all fds are closed.

   - bpo-20383(272): Introduce importlib.util.module_from_spec() as the
     preferred way to create a new module.

   - bpo-21552(273): Fixed possible integer overflow of too long string
     lengths in the tkinter module on 64-bit platforms.

   - bpo-14315(274): The zipfile module now ignores extra fields in the
     central directory that are too short to be parsed instead of
     letting a struct.unpack error bubble up as this "bad data" appears
     in many real world zip files in the wild and is ignored by other
     zip tools.

   - bpo-13742(275): Added "key" and "reverse" parameters to
     heapq.merge().  (First draft of patch contributed by Simon Sapin.)

   - bpo-21402(276): tkinter.ttk now works when default root window is
     not set.

   - bpo-3015(277): ‘_tkinter.create()’ now creates ‘tkapp’ object with
     ‘wantobjects=1’ by default.

   - bpo-10203(278): sqlite3.Row now truly supports sequence protocol.
     In particular it supports reverse() and negative indices.  Original
     patch by Claudiu Popa.

   - bpo-18807(279): If copying (no symlinks) specified for a venv, then
     the python interpreter aliases (python, python3) are now created by
     copying rather than symlinking.

   - bpo-20197(280): Added support for the WebP image type in the imghdr
     module.  Patch by Fabrice Aneche and Claudiu Popa.

   - bpo-21513(281): Speedup some properties of IP addresses
     (IPv4Address, IPv6Address) such as .is_private or .is_multicast.

   - bpo-21137(282): Improve the repr for threading.Lock() and its
     variants by showing the "locked" or "unlocked" status.  Patch by
     Berker Peksag.

   - bpo-21538(283): The plistlib module now supports loading of binary
     plist files when reference or offset size is not a power of two.

   - bpo-21455(284): Add a default backlog to socket.listen().

   - bpo-21525(285): Most Tkinter methods which accepted tuples now
     accept lists too.

   - bpo-22166(286): With the assistance of a new internal
     _codecs._forget_codec helping function, test_codecs now clears the
     encoding caches to avoid the appearance of a reference leak

   - bpo-22236(287): Tkinter tests now don't reuse default root window.
     New root window is created for every test class.

   - bpo-10744(288): Fix PEP 3118(289) format strings on ctypes objects
     with a nontrivial shape.

   - bpo-20826(290): Optimize ipaddress.collapse_addresses().

   - bpo-21487(291): Optimize ipaddress.summarize_address_range() and
     ipaddress.{IPv4Network,IPv6Network}.subnets().

   - bpo-21486(292): Optimize parsing of netmasks in
     ipaddress.IPv4Network and ipaddress.IPv6Network.

   - bpo-13916(293): Disallowed the surrogatepass error handler for non
     UTF-* encodings.

   - bpo-20998(294): Fixed re.fullmatch() of repeated single character
     pattern with ignore case.  Original patch by Matthew Barnett.

   - bpo-21075(295): fileinput.FileInput now reads bytes from standard
     stream if binary mode is specified.  Patch by Sam Kimbrel.

   - bpo-19775(296): Add a samefile() method to pathlib Path objects.
     Initial patch by Vajrasky Kok.

   - bpo-21226(297): Set up modules properly in
     PyImport_ExecCodeModuleObject (and friends).

   - bpo-21398(298): Fix a unicode error in the pydoc pager when the
     documentation contains characters not encodable to the stdout
     encoding.

   - bpo-16531(299): ipaddress.IPv4Network and ipaddress.IPv6Network now
     accept an (address, netmask) tuple argument, so as to easily
     construct network objects from existing addresses.

   - bpo-21156(300): importlib.abc.InspectLoader.source_to_code() is now
     a staticmethod.

   - bpo-21424(301): Simplified and optimized heaqp.nlargest() and
     nmsmallest() to make fewer tuple comparisons.

   - bpo-21396(302): Fix TextIOWrapper(..., write_through=True) to not
     force a flush() on the underlying binary stream.  Patch by akira.

   - bpo-18314(303): Unlink now removes junctions on Windows.  Patch by
     Kim Gräsman

   - bpo-21088(304): Bugfix for curses.window.addch() regression in
     3.4.0.  In porting to Argument Clinic, the first two arguments were
     reversed.

   - bpo-21407(305): _decimal: The module now supports function
     signatures.

   - bpo-10650(306): Remove the non-standard 'watchexp' parameter from
     the Decimal.quantize() method in the Python version.  It had never
     been present in the C version.

   - bpo-21469(307): Reduced the risk of false positives in robotparser
     by checking to make sure that robots.txt has been read or does not
     exist prior to returning True in can_fetch().

   - bpo-19414(308): Have the OrderedDict mark deleted links as
     unusable.  This gives an early failure if the link is deleted
     during iteration.

   - bpo-21421(309): Add __slots__ to the MappingViews ABC. Patch by
     Josh Rosenberg.

   - bpo-21101(310): Eliminate double hashing in the C speed-up code for
     collections.Counter().

   - bpo-21321(311): itertools.islice() now releases the reference to
     the source iterator when the slice is exhausted.  Patch by Anton
     Afanasyev.

   - bpo-21057(312): TextIOWrapper now allows the underlying binary
     stream's read() or read1() method to return an arbitrary bytes-like
     object (such as a memoryview).  Patch by Nikolaus Rath.

   - bpo-20951(313): SSLSocket.send() now raises either SSLWantReadError
     or SSLWantWriteError on a non-blocking socket if the operation
     would block.  Previously, it would return 0.  Patch by Nikolaus
     Rath.

   - bpo-13248(314): removed previously deprecated asyncore.dispatcher
     __getattr__ cheap inheritance hack.

   - bpo-9815(315): assertRaises now tries to clear references to local
     variables in the exception's traceback.

   - bpo-19940(316): ssl.cert_time_to_seconds() now interprets the given
     time string in the UTC timezone (as specified in RFC 5280), not the
     local timezone.

   - bpo-13204(317): Calling sys.flags.__new__ would crash the
     interpreter, now it raises a TypeError.

   - bpo-19385(318): Make operations on a closed dbm.dumb database
     always raise the same exception.

   - bpo-21207(319): Detect when the os.urandom cached fd has been
     closed or replaced, and open it anew.

   - bpo-21291(320): subprocess's Popen.wait() is now thread safe so
     that multiple threads may be calling wait() or poll() on a Popen
     instance at the same time without losing the Popen.returncode
     value.

   - bpo-21127(321): Path objects can now be instantiated from str
     subclass instances (such as ‘numpy.str_’).

   - bpo-15002(322): urllib.response object to use _TemporaryFileWrapper
     (and _TemporaryFileCloser) facility.  Provides a better way to
     handle file descriptor close.  Patch contributed by Christian
     Theune.

   - bpo-12220(323): mindom now raises a custom ValueError indicating it
     doesn't support spaces in URIs instead of letting a 'split'
     ValueError bubble up.

   - bpo-21068(324): The ssl.PROTOCOL* constants are now enum members.

   - bpo-21276(325): posixmodule: Don't define USE_XATTRS on KFreeBSD
     and the Hurd.

   - bpo-21262(326): New method assert_not_called for Mock.  It raises
     AssertionError if the mock has been called.

   - bpo-21238(327): New keyword argument ‘unsafe’ to Mock.  It raises
     ‘AttributeError’ incase of an attribute startswith assert or
     assret.

   - bpo-20896(328): ssl.get_server_certificate() now uses
     PROTOCOL_SSLv23, not PROTOCOL_SSLv3, for maximum compatibility.

   - bpo-21239(329): patch.stopall() didn't work deterministically when
     the same name was patched more than once.

   - bpo-21203(330): Updated fileConfig and dictConfig to remove
     inconsistencies.  Thanks to Jure Koren for the patch.

   - bpo-21222(331): Passing name keyword argument to
     mock.create_autospec now works.

   - bpo-21197(332): Add lib64 -> lib symlink in venvs on 64-bit non-OS
     X POSIX.

   - bpo-17498(333): Some SMTP servers disconnect after certain errors,
     violating strict RFC conformance.  Instead of losing the error code
     when we issue the subsequent RSET, smtplib now returns the error
     code and defers raising the SMTPServerDisconnected error until the
     next command is issued.

   - bpo-17826(334): setting an iterable side_effect on a mock function
     created by create_autospec now works.  Patch by Kushal Das.

   - bpo-7776(335): Fix ‘Host:’ header and reconnection when using
     http.client.HTTPConnection.set_tunnel().  Patch by Nikolaus Rath.

   - bpo-20968(336): unittest.mock.MagicMock now supports division.
     Patch by Johannes Baiter.

   - bpo-21529(337): Fix arbitrary memory access in
     JSONDecoder.raw_decode with a negative second parameter.  Bug
     reported by Guido Vranken.  (See also: CVE-2014-4616(338))

   - bpo-21169(339): getpass now handles non-ascii characters that the
     input stream encoding cannot encode by re-encoding using the
     replace error handler.

   - bpo-21171(340): Fixed undocumented filter API of the rot13 codec.
     Patch by Berker Peksag.

   - bpo-20539(341): Improved math.factorial error message for large
     positive inputs and changed exception type (OverflowError ->
     ValueError) for large negative inputs.

   - bpo-21172(342): isinstance check relaxed from dict to
     collections.Mapping.

   - bpo-21155(343): asyncio.EventLoop.create_unix_server() now raises a
     ValueError if path and sock are specified at the same time.

   - bpo-21136(344): Avoid unnecessary normalization of Fractions
     resulting from power and other operations.  Patch by Raymond
     Hettinger.

   - bpo-17621(345): Introduce importlib.util.LazyLoader.

   - bpo-21076(346): signal module constants were turned into enums.
     Patch by Giampaolo Rodola'.

   - bpo-20636(347): Improved the repr of Tkinter widgets.

   - bpo-19505(348): The items, keys, and values views of OrderedDict
     now support reverse iteration using reversed().

   - bpo-21149(349): Improved thread-safety in logging cleanup during
     interpreter shutdown.  Thanks to Devin Jeanpierre for the patch.

   - bpo-21058(350): Fix a leak of file descriptor in *note
     tempfile.NamedTemporaryFile(): 46d, close the file descriptor if
     *note io.open(): 4c1. fails

   - bpo-21200(351): Return None from pkgutil.get_loader() when __spec__
     is missing.

   - bpo-21013(352): Enhance ssl.create_default_context() when used for
     server side sockets to provide better security by default.

   - bpo-20145(353): ‘assertRaisesRegex’ and ‘assertWarnsRegex’ now
     raise a ‘TypeError’ if the second argument is not a string or
     compiled regex.

   - bpo-20633(354): Replace relative import by absolute import.

   - bpo-20980(355): Stop wrapping exception when using ThreadPool.

   - bpo-21082(356): In os.makedirs, do not set the process-wide umask.
     Note this changes behavior of makedirs when exist_ok=True.

   - bpo-20990(357): Fix issues found by pyflakes for multiprocessing.

   - bpo-21015(358): SSL contexts will now automatically select an
     elliptic curve for ECDH key exchange on OpenSSL 1.0.2 and later,
     and otherwise default to "prime256v1".

   - bpo-21000(359): Improve the command-line interface of json.tool.

   - bpo-20995(360): Enhance default ciphers used by the ssl module to
     enable better security and prioritize perfect forward secrecy.

   - bpo-20884(361): Don't assume that __file__ is defined on
     importlib.__init__.

   - bpo-21499(362): Ignore __builtins__ in several
     test_importlib.test_api tests.

   - bpo-20627(363): xmlrpc.client.ServerProxy is now a context manager.

   - bpo-19165(364): The formatter module now raises DeprecationWarning
     instead of PendingDeprecationWarning.

   - bpo-13936(365): Remove the ability of datetime.time instances to be
     considered false in boolean contexts.

   - bpo-18931(366): selectors module now supports /dev/poll on Solaris.
     Patch by Giampaolo Rodola'.

   - bpo-19977(367): When the ‘LC_TYPE’ locale is the POSIX locale (‘C’
     locale), *note sys.stdin: 4e2. and *note sys.stdout: a79. are now
     using the ‘surrogateescape’ error handler, instead of the ‘strict’
     error handler.

   - bpo-20574(368): Implement incremental decoder for cp65001 code
     (Windows code page 65001, Microsoft UTF-8).

   - bpo-20879(369): Delay the initialization of encoding and decoding
     tables for base32, ascii85 and base85 codecs in the base64 module,
     and delay the initialization of the unquote_to_bytes() table of the
     urllib.parse module, to not waste memory if these modules are not
     used.

   - bpo-19157(370): Include the broadcast address in the usuable hosts
     for IPv6 in ipaddress.

   - bpo-11599(371): When an external command (e.g.  compiler) fails,
     distutils now prints out the whole command line (instead of just
     the command name) if the environment variable DISTUTILS_DEBUG is
     set.

   - bpo-4931(372): distutils should not produce unhelpful "error: None"
     messages anymore.  distutils.util.grok_environment_error is kept
     but doc-deprecated.

   - bpo-20875(373): Prevent possible gzip "'read' is not defined"
     NameError.  Patch by Claudiu Popa.

   - bpo-11558(374): ‘email.message.Message.attach’ now returns a more
     useful error message if ‘attach’ is called on a message for which
     ‘is_multipart’ is False.

   - bpo-20283(375): RE pattern methods now accept the string keyword
     parameters as documented.  The pattern and source keyword
     parameters are left as deprecated aliases.

   - bpo-20778(376): Fix modulefinder to work with bytecode-only
     modules.

   - bpo-20791(377): copy.copy() now doesn't make a copy when the input
     is a bytes object.  Initial patch by Peter Otten.

   - bpo-19748(378): On AIX, time.mktime() now raises an OverflowError
     for year outsize range [1902; 2037].

   - bpo-19573(379): inspect.signature: Use enum for parameter kind
     constants.

   - bpo-20726(380): inspect.signature: Make Signature and Parameter
     picklable.

   - bpo-17373(381): Add inspect.Signature.from_callable method.

   - bpo-20378(382): Improve repr of inspect.Signature and
     inspect.Parameter.

   - bpo-20816(383): Fix inspect.getcallargs() to raise correct
     TypeError for missing keyword-only arguments.  Patch by Jeremiah
     Lowin.

   - bpo-20817(384): Fix inspect.getcallargs() to fail correctly if more
     than 3 arguments are missing.  Patch by Jeremiah Lowin.

   - bpo-6676(385): Ensure a meaningful exception is raised when
     attempting to parse more than one XML document per pyexpat
     xmlparser instance.  (Original patches by Hirokazu Yamamoto and
     Amaury Forgeot d'Arc, with suggested wording by David Gutteridge)

   - bpo-21117(386): Fix inspect.signature to better support
     functools.partial.  Due to the specifics of functools.partial
     implementation, positional-or-keyword arguments passed as keyword
     arguments become keyword-only.

   - bpo-20334(387): inspect.Signature and inspect.Parameter are now
     hashable.  Thanks to Antony Lee for bug reports and suggestions.

   - bpo-15916(388): doctest.DocTestSuite returns an empty
     unittest.TestSuite instead of raising ValueError if it finds no
     tests

   - bpo-21209(389): Fix asyncio.tasks.CoroWrapper to workaround a bug
     in yield-from implementation in CPythons prior to 3.4.1.

   - asyncio: Add gi_{frame,running,code} properties to CoroWrapper
     (upstream bpo-163(390)).

   - bpo-21311(391): Avoid exception in _osx_support with non-standard
     compiler configurations.  Patch by John Szakmeister.

   - bpo-11571(392): Ensure that the turtle window becomes the topmost
     window when launched on OS X.

   - bpo-21801(393): Validate that __signature__ is None or an instance
     of Signature.

   - bpo-21923(394): Prevent AttributeError in
     distutils.sysconfig.customize_compiler due to possible
     uninitialized _config_vars.

   - bpo-21323(395): Fix http.server to again handle scripts in CGI
     subdirectories, broken by the fix for security bpo-19435(396).
     Patch by Zach Byrne.

   - bpo-22733(397): Fix ffi_prep_args not zero-extending argument
     values correctly on 64-bit Windows.

   - bpo-23302(398): Default to TCP_NODELAY=1 upon establishing an
     HTTPConnection.  Removed use of hard-coded MSS as it's an
     optimization that's no longer needed with Nagle disabled.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23399

   (2) https://bugs.python.org/issue?@action=redirect&bpo=20289

   (3) https://bugs.python.org/issue?@action=redirect&bpo=13128

   (4) https://bugs.python.org/issue?@action=redirect&bpo=15381

   (5) https://bugs.python.org/issue?@action=redirect&bpo=22818

   (6) https://bugs.python.org/issue?@action=redirect&bpo=23099

   (7) https://bugs.python.org/issue?@action=redirect&bpo=23326

   (8) https://bugs.python.org/issue?@action=redirect&bpo=21408

   (9) https://bugs.python.org/issue?@action=redirect&bpo=23363

   (10) https://bugs.python.org/issue?@action=redirect&bpo=23364

   (11) https://bugs.python.org/issue?@action=redirect&bpo=23366

   (12) https://bugs.python.org/issue?@action=redirect&bpo=23369

   (13) https://bugs.python.org/issue?@action=redirect&bpo=23353

   (14) https://bugs.python.org/issue?@action=redirect&bpo=14099

   (15) https://bugs.python.org/issue?@action=redirect&bpo=14099

   (16) https://bugs.python.org/issue?@action=redirect&bpo=19361

   (17) https://bugs.python.org/issue?@action=redirect&bpo=18518

   (18) https://bugs.python.org/issue?@action=redirect&bpo=23094

   (19) https://bugs.python.org/issue?@action=redirect&bpo=23268

   (20) https://bugs.python.org/issue?@action=redirect&bpo=21408

   (21) https://bugs.python.org/issue?@action=redirect&bpo=19996

   (22) https://bugs.python.org/issue?@action=redirect&bpo=20188

   (23) https://bugs.python.org/issue?@action=redirect&bpo=23133

   (24) https://bugs.python.org/issue?@action=redirect&bpo=23248

   (25) https://bugs.python.org/issue?@action=redirect&bpo=23266

   (26) https://bugs.python.org/issue?@action=redirect&bpo=23098

   (27) https://bugs.python.org/issue?@action=redirect&bpo=21817

   (28) https://bugs.python.org/issue?@action=redirect&bpo=15955

   (29) https://bugs.python.org/issue?@action=redirect&bpo=23250

   (30) https://bugs.python.org/issue?@action=redirect&bpo=23063

   (31) https://bugs.python.org/issue?@action=redirect&bpo=23209

   (32) https://bugs.python.org/issue?@action=redirect&bpo=23225

   (33) https://bugs.python.org/issue?@action=redirect&bpo=17911

   (34) https://bugs.python.org/issue?@action=redirect&bpo=17911

   (35) https://bugs.python.org/issue?@action=redirect&bpo=19777

   (36) https://bugs.python.org/issue?@action=redirect&bpo=23206

   (37) https://bugs.python.org/issue?@action=redirect&bpo=23185

   (38) https://bugs.python.org/issue?@action=redirect&bpo=23186

   (39) https://bugs.python.org/issue?@action=redirect&bpo=23143

   (40) https://bugs.python.org/issue?@action=redirect&bpo=23132

   (41) https://bugs.python.org/issue?@action=redirect&bpo=19776

   (42) https://bugs.python.org/issue?@action=redirect&bpo=23112

   (43) https://bugs.python.org/issue?@action=redirect&bpo=21793

   (44) https://bugs.python.org/issue?@action=redirect&bpo=23093

   (45) https://bugs.python.org/issue?@action=redirect&bpo=23111

   (46) https://bugs.python.org/issue?@action=redirect&bpo=22585

   (47) https://bugs.python.org/issue?@action=redirect&bpo=19104

   (48) https://bugs.python.org/issue?@action=redirect&bpo=23071

   (49) https://bugs.python.org/issue?@action=redirect&bpo=22783

   (50) https://bugs.python.org/issue?@action=redirect&bpo=15513

   (51) https://bugs.python.org/issue?@action=redirect&bpo=19858

   (52) https://bugs.python.org/issue?@action=redirect&bpo=22095

   (53) https://bugs.python.org/issue?@action=redirect&bpo=23016

   (54) https://bugs.python.org/issue?@action=redirect&bpo=21775

   (55) https://bugs.python.org/issue?@action=redirect&bpo=1218234

   (56) https://bugs.python.org/issue?@action=redirect&bpo=21740

   (57) https://bugs.python.org/issue?@action=redirect&bpo=23009

   (58) https://bugs.python.org/issue?@action=redirect&bpo=22959

   (59) https://bugs.python.org/issue?@action=redirect&bpo=22696

   (60) https://bugs.python.org/issue?@action=redirect&bpo=16043

   (61) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-1753

   (62) https://bugs.python.org/issue?@action=redirect&bpo=14099

   (63) https://bugs.python.org/issue?@action=redirect&bpo=22966

   (64) https://bugs.python.org/issue?@action=redirect&bpo=21971

   (65) https://bugs.python.org/issue?@action=redirect&bpo=21032

   (66) https://bugs.python.org/issue?@action=redirect&bpo=22407

   (67) https://bugs.python.org/issue?@action=redirect&bpo=22902

   (68) https://bugs.python.org/issue?@action=redirect&bpo=22960

   (69) https://bugs.python.org/issue?@action=redirect&bpo=22389

   (70) https://bugs.python.org/issue?@action=redirect&bpo=21356

   (71) https://bugs.python.org/issue?@action=redirect&bpo=22915

   (72) https://bugs.python.org/issue?@action=redirect&bpo=22609

   (73) https://bugs.python.org/issue?@action=redirect&bpo=22940

   (74) https://bugs.python.org/issue?@action=redirect&bpo=19676

   (75) https://bugs.python.org/issue?@action=redirect&bpo=22788

   (76) https://bugs.python.org/issue?@action=redirect&bpo=22921

   (77) https://bugs.python.org/issue?@action=redirect&bpo=22894

   (78) https://bugs.python.org/issue?@action=redirect&bpo=22796

   (79) https://bugs.python.org/issue?@action=redirect&bpo=22370

   (80) https://bugs.python.org/issue?@action=redirect&bpo=22841

   (81) https://bugs.python.org/issue?@action=redirect&bpo=19494

   (82) https://bugs.python.org/issue?@action=redirect&bpo=22578

   (83) https://bugs.python.org/issue?@action=redirect&bpo=22849

   (84) https://bugs.python.org/issue?@action=redirect&bpo=12728

   (85) https://bugs.python.org/issue?@action=redirect&bpo=22821

   (86) https://bugs.python.org/issue?@action=redirect&bpo=21650

   (87) https://bugs.python.org/issue?@action=redirect&bpo=22824

   (88) https://bugs.python.org/issue?@action=redirect&bpo=22824

   (89) https://bugs.python.org/issue?@action=redirect&bpo=22406

   (90) https://bugs.python.org/issue?@action=redirect&bpo=17293

   (91) https://bugs.python.org/issue?@action=redirect&bpo=22769

   (92) https://bugs.python.org/issue?@action=redirect&bpo=22417

   (93) https://bugs.python.org/issue?@action=redirect&bpo=22775

   (94) https://bugs.python.org/issue?@action=redirect&bpo=22776

   (95) https://bugs.python.org/issue?@action=redirect&bpo=22665

   (96) https://bugs.python.org/issue?@action=redirect&bpo=6623

   (97) https://bugs.python.org/issue?@action=redirect&bpo=17381

   (98) https://bugs.python.org/issue?@action=redirect&bpo=22410

   (99) https://bugs.python.org/issue?@action=redirect&bpo=22759

   (100) https://bugs.python.org/issue?@action=redirect&bpo=8876

   (101) https://bugs.python.org/issue?@action=redirect&bpo=22217

   (102) https://bugs.python.org/issue?@action=redirect&bpo=22457

   (103) https://bugs.python.org/issue?@action=redirect&bpo=18216

   (104) https://bugs.python.org/issue?@action=redirect&bpo=13918

   (105) https://bugs.python.org/issue?@action=redirect&bpo=22676

   (106) https://bugs.python.org/issue?@action=redirect&bpo=18853

   (107) https://bugs.python.org/issue?@action=redirect&bpo=9351

   (108) https://bugs.python.org/issue?@action=redirect&bpo=7559

   (109) https://bugs.python.org/issue?@action=redirect&bpo=19746

   (110) https://bugs.python.org/issue?@action=redirect&bpo=21991

   (111) https://bugs.python.org/issue?@action=redirect&bpo=22638

   (112) https://bugs.python.org/issue?@action=redirect&bpo=22641

   (113) https://bugs.python.org/issue?@action=redirect&bpo=17401

   (114) https://bugs.python.org/issue?@action=redirect&bpo=21338

   (115) https://bugs.python.org/issue?@action=redirect&bpo=20152

   (116) https://bugs.python.org/issue?@action=redirect&bpo=18643

   (117) https://bugs.python.org/issue?@action=redirect&bpo=22435

   (118) https://bugs.python.org/issue?@action=redirect&bpo=13096

   (119) https://bugs.python.org/issue?@action=redirect&bpo=11694

   (120) https://bugs.python.org/issue?@action=redirect&bpo=19380

   (121) https://bugs.python.org/issue?@action=redirect&bpo=1519638

   (122) https://bugs.python.org/issue?@action=redirect&bpo=18615

   (123) https://bugs.python.org/issue?@action=redirect&bpo=22462

   (124) https://bugs.python.org/issue?@action=redirect&bpo=21965

   (125) https://bugs.python.org/issue?@action=redirect&bpo=21173

   (126) https://bugs.python.org/issue?@action=redirect&bpo=11866

   (127) https://bugs.python.org/issue?@action=redirect&bpo=21905

   (128) https://bugs.python.org/issue?@action=redirect&bpo=11271

   (129) https://bugs.python.org/issue?@action=redirect&bpo=21883

   (130) https://bugs.python.org/issue?@action=redirect&bpo=22219

   (131) https://bugs.python.org/issue?@action=redirect&bpo=22449

   (132) https://bugs.python.org/issue?@action=redirect&bpo=22508

   (133) https://bugs.python.org/issue?@action=redirect&bpo=20076

   (134) https://bugs.python.org/issue?@action=redirect&bpo=20079

   (135) https://bugs.python.org/issue?@action=redirect&bpo=20218

   (136) https://bugs.python.org/issue?@action=redirect&bpo=22396

   (137) https://bugs.python.org/issue?@action=redirect&bpo=22517

   (138) https://bugs.python.org/issue?@action=redirect&bpo=22437

   (139) https://bugs.python.org/issue?@action=redirect&bpo=17442

   (140) https://bugs.python.org/issue?@action=redirect&bpo=23392

   (141) https://bugs.python.org/issue?@action=redirect&bpo=10510

   (142) https://bugs.python.org/issue?@action=redirect&bpo=9850

   (143) https://bugs.python.org/issue?@action=redirect&bpo=5309

   (144) https://bugs.python.org/issue?@action=redirect&bpo=22448

   (145) https://bugs.python.org/issue?@action=redirect&bpo=22427

   (146) https://bugs.python.org/issue?@action=redirect&bpo=22362

   (147) https://bugs.python.org/issue?@action=redirect&bpo=20912

   (148) https://bugs.python.org/issue?@action=redirect&bpo=21866

   (149) https://bugs.python.org/issue?@action=redirect&bpo=22278

   (150) https://bugs.python.org/issue?@action=redirect&bpo=22415

   (151) https://bugs.python.org/issue?@action=redirect&bpo=22423

   (152) https://bugs.python.org/issue?@action=redirect&bpo=21332

   (153) https://bugs.python.org/issue?@action=redirect&bpo=21091

   (154) https://bugs.python.org/issue?@action=redirect&bpo=21079

   (155) https://bugs.python.org/issue?@action=redirect&bpo=22247

   (156) https://bugs.python.org/issue?@action=redirect&bpo=22366

   (157) https://bugs.python.org/issue?@action=redirect&bpo=4180

   (158) https://bugs.python.org/issue?@action=redirect&bpo=22419

   (159) https://bugs.python.org/issue?@action=redirect&bpo=20537

   (160) https://bugs.python.org/issue?@action=redirect&bpo=22384

   (161) https://bugs.python.org/issue?@action=redirect&bpo=22168

   (162) https://bugs.python.org/issue?@action=redirect&bpo=21147

   (163) https://bugs.python.org/issue?@action=redirect&bpo=13968

   (164) https://bugs.python.org/issue?@action=redirect&bpo=21951

   (165) https://bugs.python.org/issue?@action=redirect&bpo=21951

   (166) https://bugs.python.org/issue?@action=redirect&bpo=22338

   (167) https://bugs.python.org/issue?@action=redirect&bpo=12410

   (168) https://bugs.python.org/issue?@action=redirect&bpo=21270

   (169) https://bugs.python.org/issue?@action=redirect&bpo=16662

   (170) https://bugs.python.org/issue?@action=redirect&bpo=22226

   (171) https://bugs.python.org/issue?@action=redirect&bpo=19524

   (172) https://bugs.python.org/issue?@action=redirect&bpo=20421

   (173) https://bugs.python.org/issue?@action=redirect&bpo=19546

   (174) https://bugs.python.org/issue?@action=redirect&bpo=22051

   (175) https://bugs.python.org/issue?@action=redirect&bpo=21933

   (176) https://bugs.python.org/issue?@action=redirect&bpo=21597

   (177) https://bugs.python.org/issue?@action=redirect&bpo=18132

   (178) https://bugs.python.org/issue?@action=redirect&bpo=22043

   (179) https://bugs.python.org/issue?@action=redirect&bpo=21527

   (180) https://bugs.python.org/issue?@action=redirect&bpo=22216

   (181) https://bugs.python.org/issue?@action=redirect&bpo=22098

   (182) https://bugs.python.org/issue?@action=redirect&bpo=22185

   (183) https://bugs.python.org/issue?@action=redirect&bpo=22287

   (184) https://bugs.python.org/issue?@action=redirect&bpo=22182

   (185) https://bugs.python.org/issue?@action=redirect&bpo=22042

   (186) https://bugs.python.org/issue?@action=redirect&bpo=16808

   (187) https://bugs.python.org/issue?@action=redirect&bpo=22236

   (188) https://bugs.python.org/issue?@action=redirect&bpo=2527

   (189) https://bugs.python.org/issue?@action=redirect&bpo=22118

   (190) https://bugs.python.org/issue?@action=redirect&bpo=21549

   (191) https://bugs.python.org/issue?@action=redirect&bpo=19628

   (192) https://bugs.python.org/issue?@action=redirect&bpo=15696

   (193) https://bugs.python.org/issue?@action=redirect&bpo=22068

   (194) https://bugs.python.org/issue?@action=redirect&bpo=22165

   (195) https://bugs.python.org/issue?@action=redirect&bpo=15381

   (196) https://bugs.python.org/issue?@action=redirect&bpo=8797

   (197) https://bugs.python.org/issue?@action=redirect&bpo=20729

   (198) https://bugs.python.org/issue?@action=redirect&bpo=21448

   (199) https://bugs.python.org/issue?@action=redirect&bpo=22184

   (200) https://bugs.python.org/issue?@action=redirect&bpo=17923

   (201) https://bugs.python.org/issue?@action=redirect&bpo=21725

   (202) https://bugs.python.org/issue?@action=redirect&bpo=22176

   (203) https://bugs.python.org/issue?@action=redirect&bpo=5411

   (204) https://bugs.python.org/issue?@action=redirect&bpo=21121

   (205) https://bugs.python.org/issue?@action=redirect&bpo=21975

   (206) https://bugs.python.org/issue?@action=redirect&bpo=20170

   (207) https://bugs.python.org/issue?@action=redirect&bpo=21539

   (208) https://bugs.python.org/issue?@action=redirect&bpo=22127

   (209) https://bugs.python.org/issue?@action=redirect&bpo=21047

   (210) https://bugs.python.org/issue?@action=redirect&bpo=15114

   (211) https://bugs.python.org/issue?@action=redirect&bpo=22085

   (212) https://bugs.python.org/issue?@action=redirect&bpo=21580

   (213) https://bugs.python.org/issue?@action=redirect&bpo=22003

   (214) https://bugs.python.org/issue?@action=redirect&bpo=22018

   (215) https://bugs.python.org/issue?@action=redirect&bpo=22054

   (216) https://bugs.python.org/issue?@action=redirect&bpo=17172

   (217) https://bugs.python.org/issue?@action=redirect&bpo=21704

   (218) https://bugs.python.org/issue?@action=redirect&bpo=20173

   (219) https://bugs.python.org/issue?@action=redirect&bpo=22033

   (220) https://bugs.python.org/issue?@action=redirect&bpo=21947

   (221) https://bugs.python.org/issue?@action=redirect&bpo=16133

   (222) https://bugs.python.org/issue?@action=redirect&bpo=22044

   (223) https://bugs.python.org/issue?@action=redirect&bpo=19884

   (224) https://bugs.python.org/issue?@action=redirect&bpo=4350

   (225) https://bugs.python.org/issue?@action=redirect&bpo=6167

   (226) https://bugs.python.org/issue?@action=redirect&bpo=15275

   (227) https://bugs.python.org/issue?@action=redirect&bpo=21888

   (228) https://bugs.python.org/issue?@action=redirect&bpo=22032

   (229) https://bugs.python.org/issue?@action=redirect&bpo=22031

   (230) https://bugs.python.org/issue?@action=redirect&bpo=22018

   (231) https://bugs.python.org/issue?@action=redirect&bpo=21044

   (232) https://bugs.python.org/issue?@action=redirect&bpo=21966

   (233) https://bugs.python.org/issue?@action=redirect&bpo=19076

   (234) https://bugs.python.org/issue?@action=redirect&bpo=16382

   (235) https://bugs.python.org/issue?@action=redirect&bpo=21932

   (236) https://bugs.python.org/issue?@action=redirect&bpo=21942

   (237) https://bugs.python.org/issue?@action=redirect&bpo=11259

   (238) https://bugs.python.org/issue?@action=redirect&bpo=12523

   (239) https://bugs.python.org/issue?@action=redirect&bpo=21707

   (240) https://bugs.python.org/issue?@action=redirect&bpo=20639

   (241) https://bugs.python.org/issue?@action=redirect&bpo=21714

   (242) https://bugs.python.org/issue?@action=redirect&bpo=15014

   (243) https://bugs.python.org/issue?@action=redirect&bpo=21151

   (244) https://bugs.python.org/issue?@action=redirect&bpo=21090

   (245) https://bugs.python.org/issue?@action=redirect&bpo=5800

   (246) https://bugs.python.org/issue?@action=redirect&bpo=21781

   (247) https://bugs.python.org/issue?@action=redirect&bpo=21679

   (248) https://bugs.python.org/issue?@action=redirect&bpo=21863

   (249) https://bugs.python.org/issue?@action=redirect&bpo=11453

   (250) https://bugs.python.org/issue?@action=redirect&bpo=21858

   (251) https://bugs.python.org/issue?@action=redirect&bpo=21476

   (252) https://bugs.python.org/issue?@action=redirect&bpo=20295

   (253) https://bugs.python.org/issue?@action=redirect&bpo=21729

   (254) https://bugs.python.org/issue?@action=redirect&bpo=21491

   (255) https://bugs.python.org/issue?@action=redirect&bpo=21719

   (256) https://bugs.python.org/issue?@action=redirect&bpo=21832

   (257) https://bugs.python.org/issue?@action=redirect&bpo=21722

   (258) https://bugs.python.org/issue?@action=redirect&bpo=21723

   (259) https://bugs.python.org/issue?@action=redirect&bpo=21711

   (260) https://bugs.python.org/issue?@action=redirect&bpo=17552

   (261) https://bugs.python.org/issue?@action=redirect&bpo=18039

   (262) https://bugs.python.org/issue?@action=redirect&bpo=21326

   (263) https://bugs.python.org/issue?@action=redirect&bpo=21766

   (264) https://bugs.python.org/issue?@action=redirect&bpo=21310

   (265) https://bugs.python.org/issue?@action=redirect&bpo=21256

   (266) https://bugs.python.org/issue?@action=redirect&bpo=21677

   (267) https://bugs.python.org/issue?@action=redirect&bpo=11709

   (268) https://bugs.python.org/issue?@action=redirect&bpo=21515

   (269) https://bugs.python.org/issue?@action=redirect&bpo=13223

   (270) https://bugs.python.org/issue?@action=redirect&bpo=21463

   (271) https://bugs.python.org/issue?@action=redirect&bpo=21618

   (272) https://bugs.python.org/issue?@action=redirect&bpo=20383

   (273) https://bugs.python.org/issue?@action=redirect&bpo=21552

   (274) https://bugs.python.org/issue?@action=redirect&bpo=14315

   (275) https://bugs.python.org/issue?@action=redirect&bpo=13742

   (276) https://bugs.python.org/issue?@action=redirect&bpo=21402

   (277) https://bugs.python.org/issue?@action=redirect&bpo=3015

   (278) https://bugs.python.org/issue?@action=redirect&bpo=10203

   (279) https://bugs.python.org/issue?@action=redirect&bpo=18807

   (280) https://bugs.python.org/issue?@action=redirect&bpo=20197

   (281) https://bugs.python.org/issue?@action=redirect&bpo=21513

   (282) https://bugs.python.org/issue?@action=redirect&bpo=21137

   (283) https://bugs.python.org/issue?@action=redirect&bpo=21538

   (284) https://bugs.python.org/issue?@action=redirect&bpo=21455

   (285) https://bugs.python.org/issue?@action=redirect&bpo=21525

   (286) https://bugs.python.org/issue?@action=redirect&bpo=22166

   (287) https://bugs.python.org/issue?@action=redirect&bpo=22236

   (288) https://bugs.python.org/issue?@action=redirect&bpo=10744

   (289) https://peps.python.org/pep-3118/

   (290) https://bugs.python.org/issue?@action=redirect&bpo=20826

   (291) https://bugs.python.org/issue?@action=redirect&bpo=21487

   (292) https://bugs.python.org/issue?@action=redirect&bpo=21486

   (293) https://bugs.python.org/issue?@action=redirect&bpo=13916

   (294) https://bugs.python.org/issue?@action=redirect&bpo=20998

   (295) https://bugs.python.org/issue?@action=redirect&bpo=21075

   (296) https://bugs.python.org/issue?@action=redirect&bpo=19775

   (297) https://bugs.python.org/issue?@action=redirect&bpo=21226

   (298) https://bugs.python.org/issue?@action=redirect&bpo=21398

   (299) https://bugs.python.org/issue?@action=redirect&bpo=16531

   (300) https://bugs.python.org/issue?@action=redirect&bpo=21156

   (301) https://bugs.python.org/issue?@action=redirect&bpo=21424

   (302) https://bugs.python.org/issue?@action=redirect&bpo=21396

   (303) https://bugs.python.org/issue?@action=redirect&bpo=18314

   (304) https://bugs.python.org/issue?@action=redirect&bpo=21088

   (305) https://bugs.python.org/issue?@action=redirect&bpo=21407

   (306) https://bugs.python.org/issue?@action=redirect&bpo=10650

   (307) https://bugs.python.org/issue?@action=redirect&bpo=21469

   (308) https://bugs.python.org/issue?@action=redirect&bpo=19414

   (309) https://bugs.python.org/issue?@action=redirect&bpo=21421

   (310) https://bugs.python.org/issue?@action=redirect&bpo=21101

   (311) https://bugs.python.org/issue?@action=redirect&bpo=21321

   (312) https://bugs.python.org/issue?@action=redirect&bpo=21057

   (313) https://bugs.python.org/issue?@action=redirect&bpo=20951

   (314) https://bugs.python.org/issue?@action=redirect&bpo=13248

   (315) https://bugs.python.org/issue?@action=redirect&bpo=9815

   (316) https://bugs.python.org/issue?@action=redirect&bpo=19940

   (317) https://bugs.python.org/issue?@action=redirect&bpo=13204

   (318) https://bugs.python.org/issue?@action=redirect&bpo=19385

   (319) https://bugs.python.org/issue?@action=redirect&bpo=21207

   (320) https://bugs.python.org/issue?@action=redirect&bpo=21291

   (321) https://bugs.python.org/issue?@action=redirect&bpo=21127

   (322) https://bugs.python.org/issue?@action=redirect&bpo=15002

   (323) https://bugs.python.org/issue?@action=redirect&bpo=12220

   (324) https://bugs.python.org/issue?@action=redirect&bpo=21068

   (325) https://bugs.python.org/issue?@action=redirect&bpo=21276

   (326) https://bugs.python.org/issue?@action=redirect&bpo=21262

   (327) https://bugs.python.org/issue?@action=redirect&bpo=21238

   (328) https://bugs.python.org/issue?@action=redirect&bpo=20896

   (329) https://bugs.python.org/issue?@action=redirect&bpo=21239

   (330) https://bugs.python.org/issue?@action=redirect&bpo=21203

   (331) https://bugs.python.org/issue?@action=redirect&bpo=21222

   (332) https://bugs.python.org/issue?@action=redirect&bpo=21197

   (333) https://bugs.python.org/issue?@action=redirect&bpo=17498

   (334) https://bugs.python.org/issue?@action=redirect&bpo=17826

   (335) https://bugs.python.org/issue?@action=redirect&bpo=7776

   (336) https://bugs.python.org/issue?@action=redirect&bpo=20968

   (337) https://bugs.python.org/issue?@action=redirect&bpo=21529

   (338) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-4616

   (339) https://bugs.python.org/issue?@action=redirect&bpo=21169

   (340) https://bugs.python.org/issue?@action=redirect&bpo=21171

   (341) https://bugs.python.org/issue?@action=redirect&bpo=20539

   (342) https://bugs.python.org/issue?@action=redirect&bpo=21172

   (343) https://bugs.python.org/issue?@action=redirect&bpo=21155

   (344) https://bugs.python.org/issue?@action=redirect&bpo=21136

   (345) https://bugs.python.org/issue?@action=redirect&bpo=17621

   (346) https://bugs.python.org/issue?@action=redirect&bpo=21076

   (347) https://bugs.python.org/issue?@action=redirect&bpo=20636

   (348) https://bugs.python.org/issue?@action=redirect&bpo=19505

   (349) https://bugs.python.org/issue?@action=redirect&bpo=21149

   (350) https://bugs.python.org/issue?@action=redirect&bpo=21058

   (351) https://bugs.python.org/issue?@action=redirect&bpo=21200

   (352) https://bugs.python.org/issue?@action=redirect&bpo=21013

   (353) https://bugs.python.org/issue?@action=redirect&bpo=20145

   (354) https://bugs.python.org/issue?@action=redirect&bpo=20633

   (355) https://bugs.python.org/issue?@action=redirect&bpo=20980

   (356) https://bugs.python.org/issue?@action=redirect&bpo=21082

   (357) https://bugs.python.org/issue?@action=redirect&bpo=20990

   (358) https://bugs.python.org/issue?@action=redirect&bpo=21015

   (359) https://bugs.python.org/issue?@action=redirect&bpo=21000

   (360) https://bugs.python.org/issue?@action=redirect&bpo=20995

   (361) https://bugs.python.org/issue?@action=redirect&bpo=20884

   (362) https://bugs.python.org/issue?@action=redirect&bpo=21499

   (363) https://bugs.python.org/issue?@action=redirect&bpo=20627

   (364) https://bugs.python.org/issue?@action=redirect&bpo=19165

   (365) https://bugs.python.org/issue?@action=redirect&bpo=13936

   (366) https://bugs.python.org/issue?@action=redirect&bpo=18931

   (367) https://bugs.python.org/issue?@action=redirect&bpo=19977

   (368) https://bugs.python.org/issue?@action=redirect&bpo=20574

   (369) https://bugs.python.org/issue?@action=redirect&bpo=20879

   (370) https://bugs.python.org/issue?@action=redirect&bpo=19157

   (371) https://bugs.python.org/issue?@action=redirect&bpo=11599

   (372) https://bugs.python.org/issue?@action=redirect&bpo=4931

   (373) https://bugs.python.org/issue?@action=redirect&bpo=20875

   (374) https://bugs.python.org/issue?@action=redirect&bpo=11558

   (375) https://bugs.python.org/issue?@action=redirect&bpo=20283

   (376) https://bugs.python.org/issue?@action=redirect&bpo=20778

   (377) https://bugs.python.org/issue?@action=redirect&bpo=20791

   (378) https://bugs.python.org/issue?@action=redirect&bpo=19748

   (379) https://bugs.python.org/issue?@action=redirect&bpo=19573

   (380) https://bugs.python.org/issue?@action=redirect&bpo=20726

   (381) https://bugs.python.org/issue?@action=redirect&bpo=17373

   (382) https://bugs.python.org/issue?@action=redirect&bpo=20378

   (383) https://bugs.python.org/issue?@action=redirect&bpo=20816

   (384) https://bugs.python.org/issue?@action=redirect&bpo=20817

   (385) https://bugs.python.org/issue?@action=redirect&bpo=6676

   (386) https://bugs.python.org/issue?@action=redirect&bpo=21117

   (387) https://bugs.python.org/issue?@action=redirect&bpo=20334

   (388) https://bugs.python.org/issue?@action=redirect&bpo=15916

   (389) https://bugs.python.org/issue?@action=redirect&bpo=21209

   (390) https://bugs.python.org/issue?@action=redirect&bpo=163

   (391) https://bugs.python.org/issue?@action=redirect&bpo=21311

   (392) https://bugs.python.org/issue?@action=redirect&bpo=11571

   (393) https://bugs.python.org/issue?@action=redirect&bpo=21801

   (394) https://bugs.python.org/issue?@action=redirect&bpo=21923

   (395) https://bugs.python.org/issue?@action=redirect&bpo=21323

   (396) https://bugs.python.org/issue?@action=redirect&bpo=19435

   (397) https://bugs.python.org/issue?@action=redirect&bpo=22733

   (398) https://bugs.python.org/issue?@action=redirect&bpo=23302


File: python.info,  Node: IDLE<61>,  Next: Build<86>,  Prev: Library<93>,  Up: Python 3 5 0 alpha 1

1.23.107.3 IDLE
...............

   - bpo-20577(1): Configuration of the max line length for the
     FormatParagraph extension has been moved from the General tab of
     the Idle preferences dialog to the FormatParagraph tab of the
     Config Extensions dialog.  Patch by Tal Einat.

   - bpo-16893(2): Update Idle doc chapter to match current Idle and add
     new information.

   - bpo-3068(3): Add Idle extension configuration dialog to Options
     menu.  Changes are written to HOME/.idlerc/config-extensions.cfg.
     Original patch by Tal Einat.

   - bpo-16233(4): A module browser (File : Class Browser, Alt+C)
     requires an editor window with a filename.  When Class Browser is
     requested otherwise, from a shell, output window, or 'Untitled'
     editor, Idle no longer displays an error box.  It now pops up an
     Open Module box (Alt+M). If a valid name is entered and a module is
     opened, a corresponding browser is also opened.

   - bpo-4832(5): Save As to type Python files automatically adds .py to
     the name you enter (even if your system does not display it).  Some
     systems automatically add .txt when type is Text files.

   - bpo-21986(6): Code objects are not normally pickled by the pickle
     module.  To match this, they are no longer pickled when running
     under Idle.

   - bpo-17390(7): Adjust Editor window title; remove 'Python', move
     version to end.

   - bpo-14105(8): Idle debugger breakpoints no longer disappear when
     inserting or deleting lines.

   - bpo-17172(9): Turtledemo can now be run from Idle.  Currently, the
     entry is on the Help menu, but it may move to Run.  Patch by
     Ramchandra Apt and Lita Cho.

   - bpo-21765(10): Add support for non-ascii identifiers to
     HyperParser.

   - bpo-21940(11): Add unittest for WidgetRedirector.  Initial patch by
     Saimadhav Heblikar.

   - bpo-18592(12): Add unittest for SearchDialogBase.  Patch by Phil
     Webster.

   - bpo-21694(13): Add unittest for ParenMatch.  Patch by Saimadhav
     Heblikar.

   - bpo-21686(14): add unittest for HyperParser.  Original patch by
     Saimadhav Heblikar.

   - bpo-12387(15): Add missing upper(lower)case versions of default
     Windows key bindings for Idle so Caps Lock does not disable them.
     Patch by Roger Serwy.

   - bpo-21695(16): Closing a Find-in-files output window while the
     search is still in progress no longer closes Idle.

   - bpo-18910(17): Add unittest for textView.  Patch by Phil Webster.

   - bpo-18292(18): Add unittest for AutoExpand.  Patch by Saihadhav
     Heblikar.

   - bpo-18409(19): Add unittest for AutoComplete.  Patch by Phil
     Webster.

   - bpo-21477(20): htest.py - Improve framework, complete set of tests.
     Patches by Saimadhav Heblikar

   - bpo-18104(21): Add idlelib/idle_test/htest.py with a few sample
     tests to begin consolidating and improving human-validated tests of
     Idle.  Change other files as needed to work with htest.  Running
     the module as __main__ runs all tests.

   - bpo-21139(22): Change default paragraph width to 72, the PEP 8(23)
     recommendation.

   - bpo-21284(24): Paragraph reformat test passes after user changes
     reformat width.

   - bpo-17654(25): Ensure IDLE menus are customized properly on OS X
     for non-framework builds and for all variants of Tk.

   - bpo-23180(26): Rename IDLE "Windows" menu item to "Window".  Patch
     by Al Sweigart.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=20577

   (2) https://bugs.python.org/issue?@action=redirect&bpo=16893

   (3) https://bugs.python.org/issue?@action=redirect&bpo=3068

   (4) https://bugs.python.org/issue?@action=redirect&bpo=16233

   (5) https://bugs.python.org/issue?@action=redirect&bpo=4832

   (6) https://bugs.python.org/issue?@action=redirect&bpo=21986

   (7) https://bugs.python.org/issue?@action=redirect&bpo=17390

   (8) https://bugs.python.org/issue?@action=redirect&bpo=14105

   (9) https://bugs.python.org/issue?@action=redirect&bpo=17172

   (10) https://bugs.python.org/issue?@action=redirect&bpo=21765

   (11) https://bugs.python.org/issue?@action=redirect&bpo=21940

   (12) https://bugs.python.org/issue?@action=redirect&bpo=18592

   (13) https://bugs.python.org/issue?@action=redirect&bpo=21694

   (14) https://bugs.python.org/issue?@action=redirect&bpo=21686

   (15) https://bugs.python.org/issue?@action=redirect&bpo=12387

   (16) https://bugs.python.org/issue?@action=redirect&bpo=21695

   (17) https://bugs.python.org/issue?@action=redirect&bpo=18910

   (18) https://bugs.python.org/issue?@action=redirect&bpo=18292

   (19) https://bugs.python.org/issue?@action=redirect&bpo=18409

   (20) https://bugs.python.org/issue?@action=redirect&bpo=21477

   (21) https://bugs.python.org/issue?@action=redirect&bpo=18104

   (22) https://bugs.python.org/issue?@action=redirect&bpo=21139

   (23) https://peps.python.org/pep-0008/

   (24) https://bugs.python.org/issue?@action=redirect&bpo=21284

   (25) https://bugs.python.org/issue?@action=redirect&bpo=17654

   (26) https://bugs.python.org/issue?@action=redirect&bpo=23180


File: python.info,  Node: Build<86>,  Next: C API<69>,  Prev: IDLE<61>,  Up: Python 3 5 0 alpha 1

1.23.107.4 Build
................

   - bpo-15506(1): Use standard PKG_PROG_PKG_CONFIG autoconf macro in
     the configure script.

   - bpo-22935(2): Allow the ssl module to be compiled if openssl
     doesn't support SSL 3.

   - bpo-22592(3): Drop support of the Borland C compiler to build
     Python.  The distutils module still supports it to build
     extensions.

   - bpo-22591(4): Drop support of MS-DOS, especially of the DJGPP
     compiler (MS-DOS port of GCC).

   - bpo-16537(5): Check whether self.extensions is empty in setup.py.
     Patch by Jonathan Hosmer.

   - bpo-22359(6): Remove incorrect uses of recursive make.  Patch by
     Jonas Wagner.

   - bpo-21958(7): Define HAVE_ROUND when building with Visual Studio
     2013 and above.  Patch by Zachary Turner.

   - bpo-18093(8): the programs that embed the CPython runtime are now
     in a separate "Programs" directory, rather than being kept in the
     Modules directory.

   - bpo-15759(9): "make suspicious", "make linkcheck" and "make
     doctest" in Doc/ now display special message when and only when
     there are failures.

   - bpo-21141(10): The Windows build process no longer attempts to find
     Perl, instead relying on OpenSSL source being configured and ready
     to build.  The ‘PCbuild\build_ssl.py’ script has been re-written
     and re-named to ‘PCbuild\prepare_ssl.py’, and takes care of
     configuring OpenSSL source for both 32 and 64 bit platforms.
     OpenSSL sources obtained from svn.python.org will always be
     pre-configured and ready to build.

   - bpo-21037(11): Add a build option to enable AddressSanitizer
     support.

   - bpo-19962(12): The Windows build process now creates "python.bat"
     in the root of the source tree, which passes all arguments through
     to the most recently built interpreter.

   - bpo-21285(13): Refactor and fix curses configure check to always
     search in a ncursesw directory.

   - bpo-15234(14): For BerkeleyDB and Sqlite, only add the found
     library and include directories if they aren't already being
     searched.  This avoids an explicit runtime library dependency.

   - bpo-17861(15): Tools/scripts/generate_opcode_h.py automatically
     regenerates Include/opcode.h from Lib/opcode.py if the latter gets
     any change.

   - bpo-20644(16): OS X installer build support for documentation build
     changes in 3.4.1: assume externally supplied sphinx-build is
     available in /usr/bin.

   - bpo-20022(17): Eliminate use of deprecated bundlebuilder in OS X
     builds.

   - bpo-15968(18): Incorporated Tcl, Tk, and Tix builds into the
     Windows build solution.

   - bpo-17095(19): Fix Modules/Setup 'shared' support.

   - bpo-21811(20): Anticipated fixes to support OS X versions > 10.9.

   - bpo-21166(21): Prevent possible segfaults and other random failures
     of python -generate-posix-vars in pybuilddir.txt build target.

   - bpo-18096(22): Fix library order returned by python-config.

   - bpo-17219(23): Add library build dir for Python extension
     cross-builds.

   - bpo-22919(24): Windows build updated to support VC 14.0 (Visual
     Studio 2015), which will be used for the official release.

   - bpo-21236(25): Build _msi.pyd with cabinet.lib instead of fci.lib

   - bpo-17128(26): Use private version of OpenSSL for OS X 10.5+
     installer.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=15506

   (2) https://bugs.python.org/issue?@action=redirect&bpo=22935

   (3) https://bugs.python.org/issue?@action=redirect&bpo=22592

   (4) https://bugs.python.org/issue?@action=redirect&bpo=22591

   (5) https://bugs.python.org/issue?@action=redirect&bpo=16537

   (6) https://bugs.python.org/issue?@action=redirect&bpo=22359

   (7) https://bugs.python.org/issue?@action=redirect&bpo=21958

   (8) https://bugs.python.org/issue?@action=redirect&bpo=18093

   (9) https://bugs.python.org/issue?@action=redirect&bpo=15759

   (10) https://bugs.python.org/issue?@action=redirect&bpo=21141

   (11) https://bugs.python.org/issue?@action=redirect&bpo=21037

   (12) https://bugs.python.org/issue?@action=redirect&bpo=19962

   (13) https://bugs.python.org/issue?@action=redirect&bpo=21285

   (14) https://bugs.python.org/issue?@action=redirect&bpo=15234

   (15) https://bugs.python.org/issue?@action=redirect&bpo=17861

   (16) https://bugs.python.org/issue?@action=redirect&bpo=20644

   (17) https://bugs.python.org/issue?@action=redirect&bpo=20022

   (18) https://bugs.python.org/issue?@action=redirect&bpo=15968

   (19) https://bugs.python.org/issue?@action=redirect&bpo=17095

   (20) https://bugs.python.org/issue?@action=redirect&bpo=21811

   (21) https://bugs.python.org/issue?@action=redirect&bpo=21166

   (22) https://bugs.python.org/issue?@action=redirect&bpo=18096

   (23) https://bugs.python.org/issue?@action=redirect&bpo=17219

   (24) https://bugs.python.org/issue?@action=redirect&bpo=22919

   (25) https://bugs.python.org/issue?@action=redirect&bpo=21236

   (26) https://bugs.python.org/issue?@action=redirect&bpo=17128


File: python.info,  Node: C API<69>,  Next: Documentation<72>,  Prev: Build<86>,  Up: Python 3 5 0 alpha 1

1.23.107.5 C API
................

   - bpo-14203(1): Remove obsolete support for view==NULL in
     PyBuffer_FillInfo(), bytearray_getbuffer(), bytesiobuf_getbuffer()
     and array_buffer_getbuf().  All functions now raise BufferError in
     that case.

   - bpo-22445(2): PyBuffer_IsContiguous() now implements precise
     contiguity tests, compatible with NumPy's
     NPY_RELAXED_STRIDES_CHECKING compilation flag.  Previously the
     function reported false negatives for corner cases.

   - bpo-22079(3): PyType_Ready() now checks that statically allocated
     type has no dynamically allocated bases.

   - bpo-22453(4): Removed non-documented macro PyObject_REPR().

   - bpo-18395(5): Rename ‘_Py_char2wchar()’ to *note Py_DecodeLocale():
     b6e, rename ‘_Py_wchar2char()’ to *note Py_EncodeLocale(): b6f, and
     document these functions.

   - bpo-21233(6): Add new C functions: PyMem_RawCalloc(),
     PyMem_Calloc(), PyObject_Calloc(), _PyObject_GC_Calloc().
     bytes(int) is now using ‘calloc()’ instead of ‘malloc()’ for large
     objects which is faster and use less memory.

   - bpo-20942(7): PyImport_ImportFrozenModuleObject() no longer sets
     __file__ to match what importlib does; this affects
     _frozen_importlib as well as any module loaded using
     imp.init_frozen().

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=14203

   (2) https://bugs.python.org/issue?@action=redirect&bpo=22445

   (3) https://bugs.python.org/issue?@action=redirect&bpo=22079

   (4) https://bugs.python.org/issue?@action=redirect&bpo=22453

   (5) https://bugs.python.org/issue?@action=redirect&bpo=18395

   (6) https://bugs.python.org/issue?@action=redirect&bpo=21233

   (7) https://bugs.python.org/issue?@action=redirect&bpo=20942


File: python.info,  Node: Documentation<72>,  Next: Tests<79>,  Prev: C API<69>,  Up: Python 3 5 0 alpha 1

1.23.107.6 Documentation
........................

   - bpo-19548(1): Update the codecs module documentation to better
     cover the distinction between text encodings and other codecs,
     together with other clarifications.  Patch by Martin Panter.

   - bpo-22394(2): Doc/Makefile now supports ‘make venv
     PYTHON=../python’ to create a venv for generating the
     documentation, e.g., ‘make html PYTHON=venv/bin/python3’.

   - bpo-21514(3): The documentation of the json module now refers to
     new JSON RFC 7159 instead of obsoleted RFC 4627.

   - bpo-21777(4): The binary sequence methods on bytes and bytearray
     are now documented explicitly, rather than assuming users will be
     able to derive the expected behaviour from the behaviour of the
     corresponding str methods.

   - bpo-6916(5): undocument deprecated asynchat.fifo class.

   - bpo-17386(6): Expanded functionality of the ‘Doc/make.bat’ script
     to make it much more comparable to ‘Doc/Makefile’.

   - bpo-21312(7): Update the thread_foobar.h template file to include
     newer threading APIs.  Patch by Jack McCracken.

   - bpo-21043(8): Remove the recommendation for specific CA
     organizations and to mention the ability to load the OS
     certificates.

   - bpo-20765(9): Add missing documentation for PurePath.with_name()
     and PurePath.with_suffix().

   - bpo-19407(10): New package installation and distribution guides
     based on the Python Packaging Authority tools.  Existing guides
     have been retained as legacy links from the distutils docs, as they
     still contain some required reference material for tool developers
     that isn't recorded anywhere else.

   - bpo-19697(11): Document cases where __main__.__spec__ is None.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=19548

   (2) https://bugs.python.org/issue?@action=redirect&bpo=22394

   (3) https://bugs.python.org/issue?@action=redirect&bpo=21514

   (4) https://bugs.python.org/issue?@action=redirect&bpo=21777

   (5) https://bugs.python.org/issue?@action=redirect&bpo=6916

   (6) https://bugs.python.org/issue?@action=redirect&bpo=17386

   (7) https://bugs.python.org/issue?@action=redirect&bpo=21312

   (8) https://bugs.python.org/issue?@action=redirect&bpo=21043

   (9) https://bugs.python.org/issue?@action=redirect&bpo=20765

   (10) https://bugs.python.org/issue?@action=redirect&bpo=19407

   (11) https://bugs.python.org/issue?@action=redirect&bpo=19697


File: python.info,  Node: Tests<79>,  Next: Tools/Demos<47>,  Prev: Documentation<72>,  Up: Python 3 5 0 alpha 1

1.23.107.7 Tests
................

   - bpo-18982(1): Add tests for CLI of the calendar module.

   - bpo-19548(2): Added some additional checks to test_codecs to ensure
     that statements in the updated documentation remain accurate.
     Patch by Martin Panter.

   - bpo-22838(3): All test_re tests now work with unittest test
     discovery.

   - bpo-22173(4): Update lib2to3 tests to use unittest test discovery.

   - bpo-16000(5): Convert test_curses to use unittest.

   - bpo-21456(6): Skip two tests in test_urllib2net.py if _ssl module
     not present.  Patch by Remi Pointel.

   - bpo-20746(7): Fix test_pdb to run in refleak mode (-R). Patch by
     Xavier de Gaye.

   - bpo-22060(8): test_ctypes has been somewhat cleaned up and
     simplified; it now uses unittest test discovery to find its tests.

   - bpo-22104(9): regrtest.py no longer holds a reference to the suite
     of tests loaded from test modules that don't define test_main().

   - bpo-22111(10): Assorted cleanups in test_imaplib.  Patch by Milan
     Oberkirch.

   - bpo-22002(11): Added ‘load_package_tests’ function to test.support
     and used it to implement/augment test discovery in test_asyncio,
     test_email, test_importlib, test_json, and test_tools.

   - bpo-21976(12): Fix test_ssl to accept LibreSSL version strings.
     Thanks to William Orr.

   - bpo-21918(13): Converted test_tools from a module to a package
     containing separate test files for each tested script.

   - bpo-9554(14): Use modern unittest features in test_argparse.
     Initial patch by Denver Coneybeare and Radu Voicilas.

   - bpo-20155(15): Changed HTTP method names in failing tests in
     test_httpservers so that packet filtering software (specifically
     Windows Base Filtering Engine) does not interfere with the
     transaction semantics expected by the tests.

   - bpo-19493(16): Refactored the ctypes test package to skip tests
     explicitly rather than silently.

   - bpo-18492(17): All resources are now allowed when tests are not run
     by regrtest.py.

   - bpo-21634(18): Fix pystone micro-benchmark: use floor division
     instead of true division to benchmark integers instead of
     floating-point numbers.  Set pystone version to 1.2.  Patch written
     by Lennart Regebro.

   - bpo-21605(19): Added tests for Tkinter images.

   - bpo-21493(20): Added test for ntpath.expanduser().  Original patch
     by Claudiu Popa.

   - bpo-19925(21): Added tests for the spwd module.  Original patch by
     Vajrasky Kok.

   - bpo-21522(22): Added Tkinter tests for Listbox.itemconfigure(),
     PanedWindow.paneconfigure(), and Menu.entryconfigure().

   - bpo-17756(23): Fix test_code test when run from the installed
     location.

   - bpo-17752(24): Fix distutils tests when run from the installed
     location.

   - bpo-18604(25): Consolidated checks for GUI availability.  All
     platforms now at least check whether Tk can be instantiated when
     the GUI resource is requested.

   - bpo-21275(26): Fix a socket test on KFreeBSD.

   - bpo-21223(27): Pass test_site/test_startup_imports when some of the
     extensions are built as builtins.

   - bpo-20635(28): Added tests for Tk geometry managers.

   - Add test case for freeze.

   - bpo-20743(29): Fix a reference leak in test_tcl.

   - bpo-21097(30): Move test_namespace_pkgs into test_importlib.

   - bpo-21503(31): Use test_both() consistently in test_importlib.

   - bpo-20939(32): Avoid various network test failures due to new
     redirect of ‘http://www.python.org/’ to ‘https://www.python.org’:
     use ‘http://www.example.com’ instead.

   - bpo-20668(33): asyncio tests no longer rely on tests.txt file.
     (Patch by Vajrasky Kok)

   - bpo-21093(34): Prevent failures of ctypes test_macholib on OS X if
     a copy of libz exists in $HOME/lib or /usr/local/lib.

   - bpo-22770(35): Prevent some Tk segfaults on OS X when running gui
     tests.

   - bpo-23211(36): Workaround test_logging failure on some OS X 10.6
     systems.

   - bpo-23345(37): Prevent test_ssl failures with large OpenSSL patch
     level values (like 0.9.8zc).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=18982

   (2) https://bugs.python.org/issue?@action=redirect&bpo=19548

   (3) https://bugs.python.org/issue?@action=redirect&bpo=22838

   (4) https://bugs.python.org/issue?@action=redirect&bpo=22173

   (5) https://bugs.python.org/issue?@action=redirect&bpo=16000

   (6) https://bugs.python.org/issue?@action=redirect&bpo=21456

   (7) https://bugs.python.org/issue?@action=redirect&bpo=20746

   (8) https://bugs.python.org/issue?@action=redirect&bpo=22060

   (9) https://bugs.python.org/issue?@action=redirect&bpo=22104

   (10) https://bugs.python.org/issue?@action=redirect&bpo=22111

   (11) https://bugs.python.org/issue?@action=redirect&bpo=22002

   (12) https://bugs.python.org/issue?@action=redirect&bpo=21976

   (13) https://bugs.python.org/issue?@action=redirect&bpo=21918

   (14) https://bugs.python.org/issue?@action=redirect&bpo=9554

   (15) https://bugs.python.org/issue?@action=redirect&bpo=20155

   (16) https://bugs.python.org/issue?@action=redirect&bpo=19493

   (17) https://bugs.python.org/issue?@action=redirect&bpo=18492

   (18) https://bugs.python.org/issue?@action=redirect&bpo=21634

   (19) https://bugs.python.org/issue?@action=redirect&bpo=21605

   (20) https://bugs.python.org/issue?@action=redirect&bpo=21493

   (21) https://bugs.python.org/issue?@action=redirect&bpo=19925

   (22) https://bugs.python.org/issue?@action=redirect&bpo=21522

   (23) https://bugs.python.org/issue?@action=redirect&bpo=17756

   (24) https://bugs.python.org/issue?@action=redirect&bpo=17752

   (25) https://bugs.python.org/issue?@action=redirect&bpo=18604

   (26) https://bugs.python.org/issue?@action=redirect&bpo=21275

   (27) https://bugs.python.org/issue?@action=redirect&bpo=21223

   (28) https://bugs.python.org/issue?@action=redirect&bpo=20635

   (29) https://bugs.python.org/issue?@action=redirect&bpo=20743

   (30) https://bugs.python.org/issue?@action=redirect&bpo=21097

   (31) https://bugs.python.org/issue?@action=redirect&bpo=21503

   (32) https://bugs.python.org/issue?@action=redirect&bpo=20939

   (33) https://bugs.python.org/issue?@action=redirect&bpo=20668

   (34) https://bugs.python.org/issue?@action=redirect&bpo=21093

   (35) https://bugs.python.org/issue?@action=redirect&bpo=22770

   (36) https://bugs.python.org/issue?@action=redirect&bpo=23211

   (37) https://bugs.python.org/issue?@action=redirect&bpo=23345


File: python.info,  Node: Tools/Demos<47>,  Next: Windows<71>,  Prev: Tests<79>,  Up: Python 3 5 0 alpha 1

1.23.107.8 Tools/Demos
......................

   - bpo-22314(1): pydoc now works when the LINES environment variable
     is set.

   - bpo-22615(2): Argument Clinic now supports the "type" argument for
     the int converter.  This permits using the int converter with enums
     and typedefs.

   - bpo-20076(3): The makelocalealias.py script no longer ignores UTF-8
     mapping.

   - bpo-20079(4): The makelocalealias.py script now can parse the
     SUPPORTED file from glibc sources and supports command line options
     for source paths.

   - bpo-22201(5): Command-line interface of the zipfile module now
     correctly extracts ZIP files with directory entries.  Patch by Ryan
     Wilson.

   - bpo-22120(6): For functions using an unsigned integer return
     converter, Argument Clinic now generates a cast to that type for
     the comparison to -1 in the generated code.  (This suppresses a
     compilation warning.)

   - bpo-18974(7): Tools/scripts/diff.py now uses argparse instead of
     optparse.

   - bpo-21906(8): Make Tools/scripts/md5sum.py work in Python 3.  Patch
     by Zachary Ware.

   - bpo-21629(9): Fix Argument Clinic's "-converters" feature.

   - Add support for ‘yield from’ to 2to3.

   - Add support for the PEP 465(10) matrix multiplication operator to
     2to3.

   - bpo-16047(11): Fix module exception list and __file__ handling in
     freeze.  Patch by Meador Inge.

   - bpo-11824(12): Consider ABI tags in freeze.  Patch by Meador Inge.

   - bpo-20535(13): PYTHONWARNING no longer affects the run_tests.py
     script.  Patch by Arfrever Frehtes Taifersar Arahesis.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=22314

   (2) https://bugs.python.org/issue?@action=redirect&bpo=22615

   (3) https://bugs.python.org/issue?@action=redirect&bpo=20076

   (4) https://bugs.python.org/issue?@action=redirect&bpo=20079

   (5) https://bugs.python.org/issue?@action=redirect&bpo=22201

   (6) https://bugs.python.org/issue?@action=redirect&bpo=22120

   (7) https://bugs.python.org/issue?@action=redirect&bpo=18974

   (8) https://bugs.python.org/issue?@action=redirect&bpo=21906

   (9) https://bugs.python.org/issue?@action=redirect&bpo=21629

   (10) https://peps.python.org/pep-0465/

   (11) https://bugs.python.org/issue?@action=redirect&bpo=16047

   (12) https://bugs.python.org/issue?@action=redirect&bpo=11824

   (13) https://bugs.python.org/issue?@action=redirect&bpo=20535


File: python.info,  Node: Windows<71>,  Prev: Tools/Demos<47>,  Up: Python 3 5 0 alpha 1

1.23.107.9 Windows
..................

   - bpo-23260(1): Update Windows installer

   - The bundled version of Tcl/Tk has been updated to 8.6.3.  The most
     visible result of this change is the addition of new native file
     dialogs when running on Windows Vista or newer.  See Tcl/Tk's TIP
     432 for more information.  Also, this version of Tcl/Tk includes
     support for Windows 10.

   - bpo-17896(2): The Windows build scripts now expect external library
     sources to be in ‘PCbuild\..\externals’ rather than
     ‘PCbuild\..\..’.

   - bpo-17717(3): The Windows build scripts now use a copy of NASM
     pulled from svn.python.org to build OpenSSL.

   - bpo-21907(4): Improved the batch scripts provided for building
     Python.

   - bpo-22644(5): The bundled version of OpenSSL has been updated to
     1.0.1j.

   - bpo-10747(6): Use versioned labels in the Windows start menu.
     Patch by Olive Kilburn.

   - bpo-22980(7): .pyd files with a version and platform tag (for
     example, ".cp35-win32.pyd") will now be loaded in preference to
     those without tags.

'(For information about older versions, consult the HISTORY file.)'

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=23260

   (2) https://bugs.python.org/issue?@action=redirect&bpo=17896

   (3) https://bugs.python.org/issue?@action=redirect&bpo=17717

   (4) https://bugs.python.org/issue?@action=redirect&bpo=21907

   (5) https://bugs.python.org/issue?@action=redirect&bpo=22644

   (6) https://bugs.python.org/issue?@action=redirect&bpo=10747

   (7) https://bugs.python.org/issue?@action=redirect&bpo=22980


File: python.info,  Node: Python 教學,  Next: Python 的設置與使用,  Prev: Python 有什麼新功能？,  Up: Top

2 Python 教學
*************

Python 是一種易學、功能強大的程式語言。它有高效能的高階資料結構，也有簡
單但有效的方法去實現物件導向程式設計。Python 優雅的語法和動態型別，結合
其直譯特性，使它成為眾多領域和大多數平臺上，撰寫腳本和快速開發應用程式的
理想語言。

使用者可以自由且免費地從 Python 官網上 (‘https://www.python.org/’) 取得
各大平台上用的 Python 直譯器和標準函式庫，下載其源碼或二進位形式執行檔，
同時，也可以將其自由地散佈。另外，Python 官網也提供了許多自由且免費的第
三方 Python 模組、程式與工具、以及額外說明文件，有興趣的使用者，可在官網
上找到相關的發行版本與連結網址。

使用 C 或 C++（或其他可被 C 呼叫的程式語言），可以很容易在 Python 直譯器
內新增功能函式及資料型別。同時，對可讓使用者自製功能的應用程式來說，
Python 也適合作為其擴充用界面語言 (extension language)。

這份教學將簡介 Python 語言與系統的基本概念及功能。除了閱讀之外、實際用
Python 直譯器寫程式跑範例，將有助於學習。但如果只用讀的，也是可行的學習
方式，因為所有範例的內容皆獨立且完整。

若想了解 Python 標準物件和模組的描述，請參閱 *note Python 標準函式庫
(Standard Library): 12a.。在 *note Python 語言參考手冊: 12b. 中，你可以
學到 Python 語言更正規的定義。想用 C 或 C++ 寫延伸套件 (extensions) 的讀
者，請閱讀 *note 擴充和嵌入 Python 直譯器: 1ae1. 和 *note Python/C API
參考手冊: 1ae2. 。此外，市面上也能找到更深入的 Python 學習書。

這份教學中，我們不會介紹每一個功能，甚至，也不打算介紹完每一個常用功能。
取而代之，我們的重心將放在介紹 Python 中最值得一提的那些功能，幫助你了解
Python 語言的特色與風格。讀完教學後，你將有能力閱讀和撰寫 Python 模組與
程式，也做好進一步學習 *note Python 標準函式庫 (Standard Library): 12a.
中各類型的 Python 函式庫模組的準備。

*note 術語表: 1ae3. 頁面也值得細讀。

* Menu:

* 淺嘗滋味::
* 使用 Python 直譯器::
* 一個非正式的 Python 簡介::
* 深入了解流程控制::
* 資料結構::
* 模組 (Module): 模組 Module.
* 輸入和輸出::
* 錯誤和例外::
* Class（類別）::
* Python 標準函式庫概覽::
* Python 標準函式庫概覽——第二部份::
* 虛擬環境與套件::
* 現在可以來學習些什麼？::
* 互動式輸入編輯和歷史記錄替換::
* 浮點數運算：問題與限制::
* 附錄::


File: python.info,  Node: 淺嘗滋味,  Next: 使用 Python 直譯器,  Up: Python 教學

2.1 淺嘗滋味
============

如果你經常在電腦上工作，最終總能發現有些工作你會想要自動化。舉例來說，你
會想在很多文字檔案裡做相同的搜尋取代，或者是用個複雜的規則重新命名或整理
一群照片。也有可能你想寫個自己的小資料庫，一個專門的 GUI 應用程式，或一
個小遊戲。

如果你是一個職業軟體開發者，你可能要操作數個 C/C++/Java 程式庫，卻覺得平
常寫程式碼、編譯、測試、再編譯的流程太慢；有可能你正為了一個程式庫撰寫一
套測試集，但發現寫測試單調乏味；也有可能你正在開發一個能使用某一語言擴充
的程式，但並不想要為了這程式特別設計一個全新的擴充語言。

在上述的例子中，Python 正是你合適的語言。

也許你可以為了某些任務而寫個 Unix shell 腳本或者 Windows 批次檔來處理，
但 shell 腳本最適合於搬動檔案或更動文字內容，而不適於圖形應用程式或遊戲
。你可以為此寫個 C/C++/Java 程式，但僅僅是完成個草稿也需要很長的開發時間
。相較而言，Python 更易於使用，並能在 Windows、macOS、Unix 作業系統上執
行，且能更快速地幫助你完成工作。

Python 即便易用也是個貨真價實的程式語言。它提供比 shell 腳本、批次檔更多
樣的程式架構與更多的支援。另一方面，Python 提供比 C 更豐富的錯語檢查。相
較於 C，Python 作為一個「非常高階的程式語言」，它內建了高階的資料型別如
彈性的數列與字典。因為這些多用途的資料型別，Python 適用解決比 Awk（甚至
是 Perl）能處理的更多問題上。至少在許多事情中，使用 Python 處理起來跟其
他語言是同樣容易的。

Python 允許你把程式切割成許多模組 (module) 並將他們重覆運用至其他 Python
程式中。Python 自帶了一個很大集合的標準模組，它們能做為你程式的基礎——或
把它們當作一開始學寫 Python 程式的範例。有些模組提供了如檔案 I/O、系統呼
叫、socket 的功能，甚至提供了 Tk 等圖形介面工具庫 (GUI toolkit) 的介面。

Python 是個直譯式語言，因為不需要編譯與連結，能為你在開發過程中省下可觀
的時間。它的直譯器能互動地使用，因此能很方便地實驗每個語言的功能、寫些用
完即丟的程式、幫助測試一些從細部開始開發的函式。它也是個好用的計算機。

Python 讓程式寫得精簡並易讀。用 Python 實作的程式長度往往遠比用 C、C++、
Java 實作的短。這有以下幾個原因：

   * Python 高階的資料型別能在一陳述式 (statement) 中表達很複雜的操作；

   * 陳述式的段落以縮排為區隔而非括號；

   * 不需要宣告變數和引數。

Python 是'可擴充的'：如果你會寫 C 程式，那麼要加個新的內建函式或模組到直
譯器中是很容易的。無論是為了用最快速的執行速度完成一些關鍵的操作，或是讓
Python 連結到一些僅以二進位形式 (binary form) 釋出的程式庫（例如特定供應
商的繪圖程式庫）。如果你想更多這樣的結合，你其實也可以把 Python 直譯器連
結到用 C 寫的應用程式，並在該應用程式中使用 Python 寫擴充或者作為下達指
令的語言。

順帶一提，這個語言是以 BBC 的戲劇《Monty Python's Flying Circus》命名，
與爬蟲類完全沒有關係。在說明文件中引用他們的喜劇不但沒問題，這甚至是個被
鼓勵的行為！

如果你現在已經躍躍欲試，你會想了解 Python 更多細節，而學習語言的最好方式
就是直接使用它。接下來這個教學就將帶領你，一邊閱讀，一邊將所學用在
Python 直譯器中玩耍。

在下個章節中，將會解說如何使用該直譯器。這也許只是個普通的資訊，但你必須
試著操作接下來呈現的範例。

接下來的教學裡，將會透過許多範例介紹 Python 語言與其系統的諸多特色。一開
始是簡單的運算式 (expression)、陳述式 (statement) 和資料型別 (data
type)；接著是函式 (function) 與模組 (module)；最後會接觸一些較進階的主題
如例外 (exception) 與使用者自定義類別 (class)。


File: python.info,  Node: 使用 Python 直譯器,  Next: 一個非正式的 Python 簡介,  Prev: 淺嘗滋味,  Up: Python 教學

2.2 使用 Python 直譯器
======================

* Menu:

* 啟動直譯器::
* 直譯器與它的環境::


File: python.info,  Node: 啟動直譯器,  Next: 直譯器與它的環境,  Up: 使用 Python 直譯器

2.2.1 啟動直譯器
----------------

The Python interpreter is usually installed as
‘/usr/local/bin/python3.13’ on those machines where it is available;
putting ‘/usr/local/bin’ in your Unix shell's search path makes it
possible to start it by typing the command:

     python3.13

能啟動 Python (1)。因為直譯器存放的目錄是個安裝選項，其他的目錄也是有可
能的；請洽談在地的 Python 達人或者系統管理員。（例如：
‘/usr/local/python’ 是個很常見的另類存放路徑。）

On Windows machines where you have installed Python from the *note
Microsoft Store: 1aec, the ‘python3.13’ command will be available.  If
you have the *note py.exe launcher: 562. installed, you can use the ‘py’
command.  See *note Excursus; Setting environment variables: 1aed. for
other ways to launch Python.

在主提示符輸入一個 end-of-file 字元（在 Unix 上為 ‘Control-D’；在
Windows 上為 ‘Control-Z’）會使得直譯器以零退出狀況 (zero exit status) 離
開。如果上述的做法沒有效，也可以輸入指令 ‘quit()’ 離開直譯器。

直譯器的指令列編輯功能有很多，在支援 GNU Readline(2) 函式庫的系統上包含
：互動編輯、歷史取代、指令補完等功能。最快檢查有無支援指令列編輯的方法為
：在第一個 Python 提示符後輸入 ‘Control-P’，如果出現嗶嗶聲，就代表有支援
；見附錄*note 互動式輸入編輯和歷史記錄替換: 1aee.介紹相關的快速鍵。如果
什麼事都沒有發生，或者出現一個 ‘^P’，就代表並沒有指令列編輯功能；此時只
能使用 backspace 去除該行的字元。

這個直譯器使用起來像是 Unix shell：如果它被呼叫時連結至一個 tty 裝置，它
會互動式地讀取並執行指令；如果被呼叫時給定檔名為引數或者使用 stdin 傳入
檔案內容，它會將這個檔案視為'腳本'來閱讀。

另一個啟動直譯器的方式為 ‘python -c command [arg] ...’，它會執行在
'command' 裡的指令（們），行為如同 shell 的 *note -c: 584. 選項。因為
Python 的指令包含空白等 shell 用到的特殊字元，通常建議用引號把 'command'
包起來。

有些 Python 模組使用上如腳本般一樣方便。透過 ‘python -m module [arg]
...’ 可以執行 'module' 模組的原始碼，就如同直接傳入那個模組的完整路徑一
樣的行為。

當要執行一個腳本檔時，有時候會希望在腳本結束時進入互動模式。此時可在執行
腳本的指令加入 *note -i: 144a.。

所有指令可用的參數都詳記在*note 命令列與環境: 18c4.。

* Menu:

* 傳遞引數::
* 互動模式::

   ---------- Footnotes ----------

   (1) 在 Unix 中，Python 3.x 直譯器預設安裝不會以 ‘python’ 作為執行檔名
稱，以避免與現有的 Python 2.x 執行檔名稱衝突。

   (2) https://tiswww.case.edu/php/chet/readline/rltop.html


File: python.info,  Node: 傳遞引數,  Next: 互動模式,  Up: 啟動直譯器

2.2.1.1 傳遞引數
................

當直擇器收到腳本的名稱和額外的引數後，他們會轉換為由字串所組成的 list（
串列）並指派給 ‘sys’ 模組的 ‘argv’ 變數。你可以執行 ‘import sys’ 取得這
個串列。這個串列的長度至少為一；當沒有給任何腳本名稱和引數時，
‘sys.argv[0]’ 為空字串。當腳本名為 ‘'-'’（指標準輸入）時， ‘sys.argv[0]’
為 ‘'-'’。當使用 *note -c: 584. 'command' 時， ‘sys.argv[0]’ 為 ‘'-c'’。
當使用 *note -m: 585. 'module' 時， ‘sys.argv[0]’ 為該模組存在的完整路徑
。其餘非 *note -c: 584. 'command' 或 *note -m: 585. 'module' 的選項不會
被 Python 直譯器吸收掉，而是留在 ‘sys.argv’ 變數中給後續的 command 或
module 使用。


File: python.info,  Node: 互動模式,  Prev: 傳遞引數,  Up: 啟動直譯器

2.2.1.2 互動模式
................

在終端 (tty) 輸入並執行指令時，直譯器在'互動模式（interactive mode）'中
運行。在這種模式中，會顯示'主提示符'，提示輸入下一條指令，主提示符通常用
三個大於號（‘>>>’）表示；輸入連續行時，顯示'次要提示符'，預設是三個點（
‘...’）。進入直譯器時，首先顯示歡迎訊息、版本訊息、版權聲明，然後才是提
示符：

     $ python3.13
     Python 3.13 (default, April 4 2023, 09:25:04)
     [GCC 10.2.0] on linux
     Type "help", "copyright", "credits" or "license" for more information.
     >>>

接續多行的情況出現在需要多行才能建立完整指令時。舉例來說，像是 *note if:
2c4. 敘述：

     >>> the_world_is_flat = True
     >>> if the_world_is_flat:
     ...     print("Be careful not to fall off!")
     ...
     Be careful not to fall off!

更多有關互動模式的使用，請見*note 互動模式: 153.。


File: python.info,  Node: 直譯器與它的環境,  Prev: 啟動直譯器,  Up: 使用 Python 直譯器

2.2.2 直譯器與它的環境
----------------------

* Menu:

* 原始碼的字元編碼 (encoding): 原始碼的字元編碼 encoding.


File: python.info,  Node: 原始碼的字元編碼 encoding,  Up: 直譯器與它的環境

2.2.2.1 原始碼的字元編碼 (encoding)
...................................

預設 Python 原始碼檔案的字元編碼使用 UTF-8。在這個編碼中，世界上多數語言
的文字可以同時被使用在字串內容、識別名 (identifier) 及註解中 -- 雖然在標
準函式庫中只使用 ASCII 字元作為識別名，這也是個任何 portable 程式碼需遵
守的慣例。如果要正確地顯示所有字元，你的編輯器需要能夠認識檔案為 UTF-8，
並且需要能顯示檔案中所有字元的字型。

如果不使用預設編碼，則要聲明檔案的編碼，檔案的'第一'行要寫成特殊註解。語
法如下：

     # -*- coding: encoding -*-

其中， 'encoding' 可以是 Python 支援的任意一種 *note codecs: 14.。

比如，聲明使用 Windows-1252 編碼，源碼檔案要寫成：

     # -*- coding: cp1252 -*-

'第一行'的規則也有一種例外情況，在源碼以 *note UNIX "shebang" line:
1af6. 行開頭時。此時，編碼聲明要寫在檔案的第二行。例如：

     #!/usr/bin/env python3
     # -*- coding: cp1252 -*-

註解
....


File: python.info,  Node: 一個非正式的 Python 簡介,  Next: 深入了解流程控制,  Prev: 使用 Python 直譯器,  Up: Python 教學

2.3 一個非正式的 Python 簡介
============================

在下面的例子中，輸入與輸出的區別在於有無提示字元（prompt，*note >>>:
150. 和 *note ...: 151.）：如果要重做範例，你必須在提示字元出現的時候，
輸入提示字元後方的所有內容；那些非提示字元開始的文字行是直譯器的輸出。注
意到在範例中，若出現單行只有次提示字元時，代表該行你必須直接換行；這被使
用在多行指令結束輸入時。

在本手冊中的許多範例中，即便他們為互動式地輸入，仍然包含註解。Python 中
的註解 (comments) 由 hash 字元 ‘#’ 開始一直到該行結束。註解可以從該行之
首、空白後、或程式碼之後開始，但不會出現在字串文本 (string literal) 之中
。hash 字元在字串文本之中時仍視為一 hash 字元。因為註解只是用來說明程式
而不會被 Python 解讀，在練習範例時不一定要輸入。

一些範例如下：

     # this is the first comment
     spam = 1  # and this is the second comment
               # ... and now a third!
     text = "# This is not a comment because it's inside quotes."

* Menu:

* 把 Python 當作計算機使用::
* 初探程式設計的前幾步::


File: python.info,  Node: 把 Python 當作計算機使用,  Next: 初探程式設計的前幾步,  Up: 一個非正式的 Python 簡介

2.3.1 把 Python 當作計算機使用
------------------------------

讓我們來試試一些簡單的 Python 指令。啟動直譯器並等待第一個主提示字元
‘>>>’ 出現。（應該不會等太久）

* Menu:

* 數字 (Number): 數字 Number.
* 文字::
* List（串列）::


File: python.info,  Node: 數字 Number,  Next: 文字,  Up: 把 Python 當作計算機使用

2.3.1.1 數字 (Number)
.....................

直譯器如同一台簡單的計算機：你可以輸入一個 expression（運算式），它會寫
出該式的值。Expression 的語法可以使用：運算子 ‘+’、‘-’、‘*’ 和 ‘/’ 可以
用來執行運算；括號 ‘()’ 可以用來分群。例如：

     >>> 2 + 2
     4
     >>> 50 - 5*6
     20
     >>> (50 - 5*6) / 4
     5.0
     >>> 8 / 5  # division always returns a floating-point number
     1.6

整數數字（即 ‘2’、‘4’、‘20’）為 *note int: 23c. 型態，數字有小數點部份的
（即 ‘5.0’、‘1.6’）為 *note float: 2c8. 型態。我們將在之後的教學中看到更
多數字相關的型態。

除法 (‘/’) 永遠回傳一個 float。如果要做 *note floor division: 8e8. 並拿
到整數的結果，你可以使用 ‘//’ 運算子；計算餘數可以使用 ‘%’：

     >>> 17 / 3  # classic division returns a float
     5.666666666666667
     >>>
     >>> 17 // 3  # floor division discards the fractional part
     5
     >>> 17 % 3  # the % operator returns the remainder of the division
     2
     >>> 5 * 3 + 2  # floored quotient * divisor + remainder
     17

在 Python 中，計算冪次 (powers) 可以使用 ‘**’ 運算子 (1)：

     >>> 5 ** 2  # 5 squared
     25
     >>> 2 ** 7  # 2 to the power of 7
     128

等於符號 (‘=’) 可以用於為變數賦值。賦值完之後，在下個指示字元前並不會顯
示任何結果：

     >>> width = 20
     >>> height = 5 * 9
     >>> width * height
     900

如果一個變數未被「定義 (defined)」（即變數未被賦值），試著使用它時會出現
一個錯誤：

     >>> n  # try to access an undefined variable
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     NameError: name 'n' is not defined

浮點數的運算有完善的支援，運算子 (operator) 遇上混合的運算元 (operand) 時
會把整數的運算元轉換為浮點數：

     >>> 4 * 3.75 - 1
     14.0

在互動式模式中，最後一個印出的運算式的結果會被指派至變數 ‘_’ 中。這表示
當你把 Python 當作桌上計算機使用者，要接續計算變得容易許多：

     >>> tax = 12.5 / 100
     >>> price = 100.50
     >>> price * tax
     12.5625
     >>> price + _
     113.0625
     >>> round(_, 2)
     113.06

這個變數應該被使用者視為只能讀取。不應該明確地為它賦值 -- 你可以創一個獨
立但名稱相同的本地變數來覆蓋掉預設變數和它的神奇行為。

除了 *note int: 23c. 和 *note float: 2c8.，Python 還支援了其他的數字型態
，包含 *note Decimal: 27c. 和 *note Fraction: 1c7.。Python 亦內建支援
*note 複數 (complex numbers): 1afe.，並使用 ‘j’ 和 ‘J’ 後綴來指定虛數的
部份（即 ‘3+5j’）。

   ---------- Footnotes ----------

   (1) 因為 ‘**’ 擁有較 ‘-’ 高的優先次序，‘-3**2’ 會被解釋為 ‘-(3**2)’ 並
得到 ‘-9’。如果要避免這樣的優先順序以得到 ‘9’，你可以使用 ‘(-3)**2’。


File: python.info,  Node: 文字,  Next: List（串列）,  Prev: 數字 Number,  Up: 把 Python 當作計算機使用

2.3.1.2 文字
............

Python 可以操作文本（由 *note str: 3f2. 型別表示，即所謂的「字串
(strings)」）和數字。這包括字元 "‘!’"、單詞 "‘rabbit’"、名稱 "‘Paris’"、
句子 "‘Got your back.’" 等等。"‘Yay! :)’"。它們可以用單引號 (‘'...'’) 或
雙引號 (‘"..."’) 括起來，會具有相同的結果 (1)。

     >>> 'spam eggs'  # single quotes
     'spam eggs'
     >>> "Paris rabbit got your back :)! Yay!"  # double quotes
     'Paris rabbit got your back :)! Yay!'
     >>> '1975'  # digits and numerals enclosed in quotes are also strings
     '1975'

要引用引文，我們需要在其前面加上 ‘\’ 來「跳脫」它。或者我們也可以使用其
他種類的引號：

     >>> 'doesn\'t'  # use \' to escape the single quote...
     "doesn't"
     >>> "doesn't"  # ...or use double quotes instead
     "doesn't"
     >>> '"Yes," they said.'
     '"Yes," they said.'
     >>> "\"Yes,\" they said."
     '"Yes," they said.'
     >>> '"Isn\'t," they said.'
     '"Isn\'t," they said.'

在 Python shell 中，字串定義和輸出字串可能看起來不同。*note print():
f18. 函式透過省略引號並印出跳脫字元和特殊字元來生成更具可讀性的輸出：

     >>> s = 'First line.\nSecond line.'  # \n means newline
     >>> s  # without print(), special characters are included in the string
     'First line.\nSecond line.'
     >>> print(s)  # with print(), special characters are interpreted, so \n produces new line
     First line.
     Second line.

如果你不希望字元前出現 ‘\’ 就被當成特殊字元時，可以改使用 'raw string'，
在第一個包圍引號前加上 ‘r’ ：

     >>> print('C:\some\name')  # here \n means newline!
     C:\some
     ame
     >>> print(r'C:\some\name')  # note the r before the quote
     C:\some\name

原始字串有一個微妙的地方：原始字串可能不會以奇數個 ‘\’ 字元結尾；請參閱
*note 常見問答集: 1b01.來了解更多資訊和解決方法。

字串文本可以跨越數行。其中一方式是使用三個重覆引號：‘"""..."""’ 或
‘'''...'''’。此時換行會被自動加入字串值中，但也可以在換行前加入 ‘\’ 來取
消這個行為。在以下的例子中：

     print("""\
     Usage: thingy [OPTIONS]
          -h                        Display this usage message
          -H hostname               Hostname to connect to
     """)

會產生以下的輸出（注意第一個換行並沒有被包含進字串值中）：

     Usage: thingy [OPTIONS]
          -h                        Display this usage message
          -H hostname               Hostname to connect to

字串可以使用 ‘+’ 運算子連接 (concatenate)，並用 ‘*’ 重覆該字串的內容：

     >>> # 3 times 'un', followed by 'ium'
     >>> 3 * 'un' + 'ium'
     'unununium'

兩個以上相鄰的字串文本（'string literal'，即被引號包圍的字串）會被自動連
接起來：

     >>> 'Py' 'thon'
     'Python'

當你想要分段一個非常長的字串時，兩相鄰字串值自動連接的特性十分有用：

     >>> text = ('Put several strings within parentheses '
     ...         'to have them joined together.')
     >>> text
     'Put several strings within parentheses to have them joined together.'

但這特性只限於兩相鄰的字串值間，而非兩相鄰變數或表達式：

     >>> prefix = 'Py'
     >>> prefix 'thon'  # can't concatenate a variable and a string literal
       File "<stdin>", line 1
         prefix 'thon'
                ^^^^^^
     SyntaxError: invalid syntax
     >>> ('un' * 3) 'ium'
       File "<stdin>", line 1
         ('un' * 3) 'ium'
                    ^^^^^
     SyntaxError: invalid syntax

如果要連接變數們或一個變數與一個字串值，使用 ‘+’：

     >>> prefix + 'thon'
     'Python'

字串可以被「索引 'indexed'」(下標，即 subscripted)，第一個字元的索引值為
0。沒有獨立表示字元的型別；一個字元就是一個大小為 1 的字串：

     >>> word = 'Python'
     >>> word[0]  # character in position 0
     'P'
     >>> word[5]  # character in position 5
     'n'

索引值可以是負的，此時改成從右開始計數：

     >>> word[-1]  # last character
     'n'
     >>> word[-2]  # second-last character
     'o'
     >>> word[-6]
     'P'

注意到因為 -0 等同於 0，負的索引值由 -1 開始。

除了索引外，字串亦支援「切片 'slicing'」。索引用來拿到單獨的字元，而切片
則可以讓你拿到一個子字串 (substring)：

     >>> word[0:2]  # characters from position 0 (included) to 2 (excluded)
     'Py'
     >>> word[2:5]  # characters from position 2 (included) to 5 (excluded)
     'tho'

切片索引 (slice indices) 有很常用的預設值，省略起點索引值時預設為 0，而
省略第二個索引值時預設整個字串被包含在 slice 中：

     >>> word[:2]   # character from the beginning to position 2 (excluded)
     'Py'
     >>> word[4:]   # characters from position 4 (included) to the end
     'on'
     >>> word[-2:]  # characters from the second-last (included) to the end
     'on'

注意到起點永遠被包含，而結尾永遠不被包含。這確保了 ‘s[:i] + s[i:]’ 永遠
等於 ‘s’：

     >>> word[:2] + word[2:]
     'Python'
     >>> word[:4] + word[4:]
     'Python'

這裡有個簡單記住 slice 是如何運作的方式。想像 slice 的索引值指著字元們之
間，其中第一個字元的左側邊緣由 0 計數。則 'n' 個字元的字串中最後一個字元
的右側邊緣會有索引值 'n'，例如：

      +---+---+---+---+---+---+
      | P | y | t | h | o | n |
      +---+---+---+---+---+---+
      0   1   2   3   4   5   6
     -6  -5  -4  -3  -2  -1

第一行數字給定字串索引值為 0...6 的位置；第二行則標示了負索引值的位置。
由 'i' 至 'j' 的 slice 包含了標示 'i' 和 'j' 邊緣間的所有字元。

對非負數的索引值而言，一個 slice 的長度等於其索引值之差，如果索引值落在
字串邊界內。例如，‘word[1:3]’ 的長度是 2。

嘗試使用一個過大的索引值會造成錯誤：

     >>> word[42]  # the word only has 6 characters
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     IndexError: string index out of range

然而，超出範圍的索引值在 slice 中會被妥善的處理：

     >>> word[4:42]
     'on'
     >>> word[42:]
     ''

Python 字串無法被改變 -- 它們是 *note immutable: 1b02.。因此，嘗試對字串
中某個索引位置賦值會產生錯誤：

     >>> word[0] = 'J'
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: 'str' object does not support item assignment
     >>> word[2:] = 'py'
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: 'str' object does not support item assignment

如果你需要一個不一樣的字串，你必須建立一個新的：

     >>> 'J' + word[1:]
     'Jython'
     >>> word[:2] + 'py'
     'Pypy'

內建的函式 *note len(): 5d4. 回傳一個字串的長度：

     >>> s = 'supercalifragilisticexpialidocious'
     >>> len(s)
     34

也參考
......

*note Text Sequence Type -- str: 1b03.

     字串是 'sequence 型別'的範例之一，並支援該型別常用的操作。

*note String Methods: 1b04.

     字串支援非常多種基本轉換和搜尋的 method（方法）。

*note f-string（f 字串）: 94d.

     包含有運算式的字串文本。

*note 格式化文字語法: 131e.

     關於透過 *note str.format(): 5c7. 字串格式化 (string formatting) 的
     資訊。

*note printf-style String Formatting: 671.

     在字串為 ‘%’ 運算子的左運算元時，將觸發舊的字串格式化操作，更多的細
     節在本連結中介紹。

   ---------- Footnotes ----------

   (1) 不像其他語言，特殊符號如 ‘\n’ 在單 (‘'...'’) 和雙 (‘"..."’) 引號
中有相同的意思。兩種引號的唯一差別，在於使用單引號時，不需要跳脫 ‘"’（但
必須跳脫 ‘\'’），反之亦同。


File: python.info,  Node: List（串列）,  Prev: 文字,  Up: 把 Python 當作計算機使用

2.3.1.3 List（串列）
....................

Python 理解數種複合型資料型別，用來組合不同的數值。當中最多樣變化的型別
為 'list'，可以寫成一系列以逗號分隔的數值（稱之元素，即 item），包含在方
括號之中。List 可以包合不同型別的元素，但通常這些元素會有相同的型別：

     >>> squares = [1, 4, 9, 16, 25]
     >>> squares
     [1, 4, 9, 16, 25]

如同字串（以及其他內建的 *note sequence: 499. 型別），list 可以被索引和
切片 (slice)：

     >>> squares[0]  # indexing returns the item
     1
     >>> squares[-1]
     25
     >>> squares[-3:]  # slicing returns a new list
     [9, 16, 25]

List 對支援如接合 (concatenation) 等操作：

     >>> squares + [36, 49, 64, 81, 100]
     [1, 4, 9, 16, 25, 36, 49, 64, 81, 100]

不同於字串是 *note immutable: 1b02.，list 是 *note mutable: 1b07. 型別，
即改變 list 的內容是可能的：

     >>> cubes = [1, 8, 27, 65, 125]  # something's wrong here
     >>> 4 ** 3  # the cube of 4 is 64, not 65!
     64
     >>> cubes[3] = 64  # replace the wrong value
     >>> cubes
     [1, 8, 27, 64, 125]

你也可以在 list 的最後加入新元素，透過使用 ‘list.append()’ '方法'
(method)（我們稍後會看到更多方法的說明）：

     >>> cubes.append(216)  # add the cube of 6
     >>> cubes.append(7 ** 3)  # and the cube of 7
     >>> cubes
     [1, 8, 27, 64, 125, 216, 343]

Python 中的簡單賦值永遠不會複製資料。當你將 list 指派給變數時，該變數會
參照'現有 list'。任何透過一個變數對 list 所做的更改都將能夠透過參照該變
數的所有其他變數看到。

     >>> rgb = ["Red", "Green", "Blue"]
     >>> rgba = rgb
     >>> id(rgb) == id(rgba)  # they reference the same object
     True
     >>> rgba.append("Alph")
     >>> rgb
     ["Red", "Green", "Blue", "Alph"]

所有切片操作都會回傳一個新的 list ，包含要求的元素。這意謂著以下這個切片
回傳了原本 list 的*note 淺複製: 1b08.：

     >>> correct_rgba = rgba[:]
     >>> correct_rgba[-1] = "Alpha"
     >>> correct_rgba
     ["Red", "Green", "Blue", "Alpha"]
     >>> rgba
     ["Red", "Green", "Blue", "Alph"]

也可以對 slice 賦值，這能改變 list 的大小，甚至是清空一個 list：

     >>> letters = ['a', 'b', 'c', 'd', 'e', 'f', 'g']
     >>> letters
     ['a', 'b', 'c', 'd', 'e', 'f', 'g']
     >>> # replace some values
     >>> letters[2:5] = ['C', 'D', 'E']
     >>> letters
     ['a', 'b', 'C', 'D', 'E', 'f', 'g']
     >>> # now remove them
     >>> letters[2:5] = []
     >>> letters
     ['a', 'b', 'f', 'g']
     >>> # clear the list by replacing all the elements with an empty list
     >>> letters[:] = []
     >>> letters
     []

內建的函式 *note len(): 5d4. 亦可以作用在 list 上：

     >>> letters = ['a', 'b', 'c', 'd']
     >>> len(letters)
     4

也可以嵌套多層 list （建立 list 包含其他 list），例如：

     >>> a = ['a', 'b', 'c']
     >>> n = [1, 2, 3]
     >>> x = [a, n]
     >>> x
     [['a', 'b', 'c'], [1, 2, 3]]
     >>> x[0]
     ['a', 'b', 'c']
     >>> x[0][1]
     'b'


File: python.info,  Node: 初探程式設計的前幾步,  Prev: 把 Python 當作計算機使用,  Up: 一個非正式的 Python 簡介

2.3.2 初探程式設計的前幾步
--------------------------

當然，我們可以用 Python 來處理比 2 加 2 更複雜的工作。例如，我們可以印出
費氏數列(1)的首幾項序列：

     >>> # Fibonacci series:
     >>> # the sum of two elements defines the next
     >>> a, b = 0, 1
     >>> while a < 10:
     ...     print(a)
     ...     a, b = b, a+b
     ...
     0
     1
     1
     2
     3
     5
     8

這例子引入了許多新的特性。

   * 第一行出現了多重賦值：變數 ‘a’ 與 ‘b’ 同時得到了新的值 0 與 1。在最
     後一行同樣的賦值再被使用了一次，示範了等號的右項運算 (expression) 會
     先被計算 (evaluate)，賦值再發生。右項的運算式由左至右依序被計算。

   * *note while: 1b0b. 迴圈只要它的條件為真（此範例：‘a < 10’），將會一
     直重覆執行。在 Python 中如同 C 語言，任何非零的整數值為真 (true)；
     零為假 (false)。條件可以是字串、list、甚至是任何序列型別；任何非零
     長度的序列為真，空的序列即為假。本例子使用的條件是個簡單的比較。標
     準的比較運算子 (comparison operators) 使用如同 C 語言一樣的符號：
     ‘<’（小於）、‘>’（大於）、‘==’（等於）、‘<=’（小於等於）、‘>=’（大
     於等於）以及 ‘!=’（不等於）。

   * 迴圈的主體會'縮排'：縮排在 Python 中用來關連一群陳述式。在互動式提
     示字元中，你必須在迴圈內的每一行一開始鍵入 tab 或者（數個）空白來維
     持縮排。實務上，你會先在文字編輯器中準備好比較複雜的輸入；多數編輯
     器都有自動縮排的功能。當一個複合陳述式以互動地方式輸入，必須在結束
     時多加一行空行來代表結束（因為語法剖析器無法判斷你何時輸入複合陳述
     的最後一行）。注意在一個縮排段落內的縮排方式與數量必須維持一致。

   * *note print(): f18. 函式印出它接收到引數（們）的值。不同於先前僅我
     們寫下想要的運算（像是先前的計算機範例），它可以處理複數個引數、浮
     點數數值和字串。印出的字串將不帶有引號，並且不同項目間會插入一個空
     白，因此可以讓你容易格式化輸出，例如：

          >>> i = 256*256
          >>> print('The value of i is', i)
          The value of i is 65536

     關鍵字引數 'end' 可以被用來避免額外的換行符加入到輸出中，或者以不同
     的字串結束輸出：

          >>> a, b = 0, 1
          >>> while a < 1000:
          ...     print(a, end=',')
          ...     a, b = b, a+b
          ...
          0,1,1,2,3,5,8,13,21,34,55,89,144,233,377,610,987,

註解
....

   ---------- Footnotes ----------

   (1) 
https://zh.wikipedia.org/zh-tw/%E6%96%90%E6%B3%A2%E9%82%A3%E5%A5%91%E6%95%B0%E5%88%97


File: python.info,  Node: 深入了解流程控制,  Next: 資料結構,  Prev: 一個非正式的 Python 簡介,  Up: Python 教學

2.4 深入了解流程控制
====================

除了剛才介紹的 *note while: 1b0b.，這章節還會介紹一些 Python 的陳述式語
法。

* Menu:

* if 陳述式::
* for 陳述式::
* range() 函式: range 函式.
* 迴圈內的 break 和 continue 陳述式及 else 子句::
* pass 陳述式::
* match 陳述式::
* 定義函式 (function): 定義函式 function.
* 深入了解函式定義::
* 間奏曲：程式碼風格 (Coding Style): 間奏曲：程式碼風格 Coding Style.


File: python.info,  Node: if 陳述式,  Next: for 陳述式,  Up: 深入了解流程控制

2.4.1 ‘if’ 陳述式
-----------------

或許最常見的陳述式種類就是 *note if: 2c4. 了。舉例來說：

     >>> x = int(input("Please enter an integer: "))
     Please enter an integer: 42
     >>> if x < 0:
     ...     x = 0
     ...     print('Negative changed to zero')
     ... elif x == 0:
     ...     print('Zero')
     ... elif x == 1:
     ...     print('Single')
     ... else:
     ...     print('More')
     ...
     More

在陳述式中，可以沒有或有許多個 *note elif: 1b11. 敘述，且 *note else:
172. 敘述並不是必要的。關鍵字 ‘elif’ 是「else if」的縮寫，用來避免過多的
縮排。一個 ‘if’ ...  ‘elif’ ...  ‘elif’ ...  序列可以用來替代其他程式語
言中的 ‘switch’ 或 ‘case’ 陳述式。

如果你要將同一個值與多個常數進行比較，或者檢查特定的型別或屬性，你可能會
發現 ‘match’ 陳述式也很有用。更多的細節，請參閱 *note match 陳述式:
1b12.。


File: python.info,  Node: for 陳述式,  Next: range 函式,  Prev: if 陳述式,  Up: 深入了解流程控制

2.4.2 ‘for’ 陳述式
------------------

在 Python 中的 *note for: 2c3. 陳述式有點不同於在 C 或 Pascal 中的慣用方
式。相較於只能疊代 (iterate) 一個等差數列（如 Pascal），或給予使用者定義
疊代步驟與終止條件（如 C），Python 的 ‘for’ 陳述式疊代任何序列（list 或
者字串）的元素，順序與它們出現在序列中的順序相同。例如（無意雙關）：

     >>> # Measure some strings:
     >>> words = ['cat', 'window', 'defenestrate']
     >>> for w in words:
     ...     print(w, len(w))
     ...
     cat 3
     window 6
     defenestrate 12

在疊代一個集合的同時修改該集合的內容，很難獲取想要的結果。比較直觀的替代
方式，是疊代該集合的副本，或建立一個新的集合：

     # Create a sample collection
     users = {'Hans': 'active', 'Éléonore': 'inactive', '景太郎': 'active'}

     # Strategy:  Iterate over a copy
     for user, status in users.copy().items():
         if status == 'inactive':
             del users[user]

     # Strategy:  Create a new collection
     active_users = {}
     for user, status in users.items():
         if status == 'active':
             active_users[user] = status


File: python.info,  Node: range 函式,  Next: 迴圈內的 break 和 continue 陳述式及 else 子句,  Prev: for 陳述式,  Up: 深入了解流程控制

2.4.3 ‘range()’ 函式
--------------------

如果你需要疊代一個數列的話，使用內建 *note range(): 8e7. 函式就很方便。
它可以生成一等差數列：

     >>> for i in range(5):
     ...     print(i)
     ...
     0
     1
     2
     3
     4

給定的結束值永遠不會出現在生成的序列中；‘range(10)’ 生成的 10 個數值，即
對應存取一個長度為 10 的序列內每一個項目的索引值。也可以讓 range 從其他
數值開始計數，或者給定不同的公差（甚至為負；有時稱之為 step）：

     >>> list(range(5, 10))
     [5, 6, 7, 8, 9]

     >>> list(range(0, 10, 3))
     [0, 3, 6, 9]

     >>> list(range(-10, -100, -30))
     [-10, -40, -70]

欲疊代一個序列的索引值，你可以搭配使用 *note range(): 8e7. 和 *note
len(): 5d4. 如下：

     >>> a = ['Mary', 'had', 'a', 'little', 'lamb']
     >>> for i in range(len(a)):
     ...     print(i, a[i])
     ...
     0 Mary
     1 had
     2 a
     3 little
     4 lamb

然而，在多數的情況，使用 *note enumerate(): 13ea. 函式將更為方便，詳見
*note 迴圈技巧: 1b17.。

如果直接印出一個 range 則會出現奇怪的輸出：

     >>> range(10)
     range(0, 10)

在很多情況下，由 *note range(): 8e7. 回傳的物件表現得像是一個 list（串列
）一樣，但實際上它並不是。它是一個在疊代時能夠回傳所要求的序列中所有項目
的物件，但它不會真正建出這個序列的 list，以節省空間。

我們稱這樣的物件為 *note iterable: 11bf.（可疊代物件），意即能作為函式及
架構中可以一直獲取項目直到取盡的對象。我們已經了解 *note for: 2c3. 陳述
式就是如此的架構，另一個使用 iterable 的函式範例是 *note sum(): 411.：

     >>> sum(range(4))  # 0 + 1 + 2 + 3
     6

待會我們可以看到更多回傳 iterable 和使用 iterable 為引數的函式。在*note
資料結構: 1b18.章節中，我們會討論更多關於 *note list(): 5b6. 的細節。


File: python.info,  Node: 迴圈內的 break 和 continue 陳述式及 else 子句,  Next: pass 陳述式,  Prev: range 函式,  Up: 深入了解流程控制

2.4.4 迴圈內的 ‘break’ 和 ‘continue’ 陳述式及 ‘else’ 子句
---------------------------------------------------------

*note break: a4c. 陳述式，終止包含它的最內部 *note for: 2c3. 或 *note
while: 1b0b. 迴圈。

‘for’ 和 ‘while’ 迴圈可帶有一個 ‘else’ 子句

在 *note for: 2c3. 迴圈中，‘else’ 子句會在迴圈到達最終的疊代後執行。

在 *note while: 1b0b. 迴圈中，它會在迴圈條件變為 false 後執行。

在任何一種迴圈中，如果迴圈由 *note break: a4c. 終止，則不會執行 ‘else’ 子
句。

下面的 ‘for’ 迴圈對此進行了舉例說明，該迴圈用以搜索質數：

     >>> for n in range(2, 10):
     ...     for x in range(2, n):
     ...         if n % x == 0:
     ...             print(n, 'equals', x, '*', n//x)
     ...             break
     ...     else:
     ...         # loop fell through without finding a factor
     ...         print(n, 'is a prime number')
     ...
     2 is a prime number
     3 is a prime number
     4 equals 2 * 2
     5 is a prime number
     6 equals 2 * 3
     7 is a prime number
     8 equals 2 * 4
     9 equals 3 * 3

（沒錯，這是正確的程式碼。請看仔細：‘else’ 子句屬於 *note for: 2c3. 迴圈
，'並非' *note if: 2c4. 陳述式。）

當 ‘else’ 子句用於迴圈時，相較於搭配 *note if: 2c4. 陳述式使用，它的行為
與 *note try: 68c. 陳述式中的 ‘else’ 子句更為相似：*note try: 68c. 陳述
式的 ‘else’ 子句在沒有發生例外 (exception) 時執行，而迴圈的 ‘else’ 子句
在沒有任何 ‘break’ 發生時執行。更多有關 ‘try’ 陳述式和例外的介紹，見
*note 處理例外: 1b1b.。

*note continue: 96d. 陳述式，亦承襲於 C 語言，讓所屬的迴圈繼續執行下個疊
代：

     >>> for num in range(2, 10):
     ...     if num % 2 == 0:
     ...         print("Found an even number", num)
     ...         continue
     ...     print("Found an odd number", num)
     ...
     Found an even number 2
     Found an odd number 3
     Found an even number 4
     Found an odd number 5
     Found an even number 6
     Found an odd number 7
     Found an even number 8
     Found an odd number 9


File: python.info,  Node: pass 陳述式,  Next: match 陳述式,  Prev: 迴圈內的 break 和 continue 陳述式及 else 子句,  Up: 深入了解流程控制

2.4.5 ‘pass’ 陳述式
-------------------

*note pass: 1b1e. 陳述式不執行任何動作。它可用在語法上需要一個陳述式但程
式不需要執行任何動作的時候。例如：

     >>> while True:
     ...     pass  # Busy-wait for keyboard interrupt (Ctrl+C)
     ...

這經常用於建立簡單的 class（類別）：

     >>> class MyEmptyClass:
     ...     pass
     ...

*note pass: 1b1e. 亦可作為一個函式或條件判斷主體的預留位置，在你撰寫新的
程式碼時讓你保持在更抽象的思維層次。‘pass’ 會直接被忽略：

     >>> def initlog(*args):
     ...     pass   # Remember to implement this!
     ...


File: python.info,  Node: match 陳述式,  Next: 定義函式 function,  Prev: pass 陳述式,  Up: 深入了解流程控制

2.4.6 ‘match’ 陳述式
--------------------

*note match: 7b1. 陳述式會拿取一個運算式，並將其值與多個連續的模式
(pattern) 進行比較，這些模式是以一個或多個 case 區塊來表示。表面上，這類
似 C、Java 或 JavaScript（以及許多其他語言）中的 switch 陳述式，但它與
Rust 或 Haskell 等語言中的模式匹配 (pattern matching) 更為相近。只有第一
個匹配成功的模式會被執行，而它也可以將成分（序列元素或物件屬性）從值中提
取到變數中。

最簡單的形式，是將一個主題值 (subject value) 與一個或多個字面值
(literal) 進行比較：

     def http_error(status):
         match status:
             case 400:
                 return "Bad request"
             case 404:
                 return "Not found"
             case 418:
                 return "I'm a teapot"
             case _:
                 return "Something's wrong with the internet"

請注意最後一段：「變數名稱」‘_’ 是作為'通用字元 (wildcard)'的角色，且永
遠不會匹配失敗。如果沒有 case 匹配成功，則不會執行任何的分支。

你可以使用 ‘|’（「或」）來將多個字面值組合在單一模式中：

     case 401 | 403 | 404:
         return "Not allowed"

模式可以看起來像是拆解賦值 (unpacking assignment)，且可以用來連結變數：

     # point is an (x, y) tuple
     match point:
         case (0, 0):
             print("Origin")
         case (0, y):
             print(f"Y={y}")
         case (x, 0):
             print(f"X={x}")
         case (x, y):
             print(f"X={x}, Y={y}")
         case _:
             raise ValueError("Not a point")

請仔細研究那個例子！第一個模式有兩個字面值，可以想作是之前所述的字面值模
式的延伸。但是接下來的兩個模式結合了一個字面值和一個變數，且該變數'繫結
(bind)' 了來自主題 (‘point’) 的一個值。第四個模式會擷取兩個值，這使得它
在概念上類似於拆解賦值 ‘(x, y) = point’。

如果你要用 class 來結構化你的資料，你可以使用該 class 的名稱加上一個引數
列表，類似一個建構式 (constructor)，但它能夠將屬性擷取到變數中：

     class Point:
         def __init__(self, x, y):
             self.x = x
             self.y = y

     def where_is(point):
         match point:
             case Point(x=0, y=0):
                 print("Origin")
             case Point(x=0, y=y):
                 print(f"Y={y}")
             case Point(x=x, y=0):
                 print(f"X={x}")
             case Point():
                 print("Somewhere else")
             case _:
                 print("Not a point")

你可以將位置參數 (positional parameter) 與一些能夠排序其屬性的內建
class（例如 dataclasses）一起使用。你也可以透過在 class 中設定特殊屬性
‘__match_args__’，來定義模式中屬性們的特定位置。如果它被設定為 ("x",
"y")，則以下的模式都是等價的（且都會將屬性 ‘y’ 連結到變數 ‘var’）：

     Point(1, var)
     Point(1, y=var)
     Point(x=1, y=var)
     Point(y=var, x=1)

理解模式的一種推薦方法，是將它們看作是你會放在賦值 (assignment) 左側內容
的一種延伸形式，這樣就可以了解哪些變數會被設為何值。只有獨立的名稱（像是
上面的 ‘var’）能被 match 陳述式賦值。點分隔名稱（如 ‘foo.bar’）、屬性名
稱（上面的 ‘x=’ 及 ‘y=’）或 class 名稱（由它們後面的 "(...)"  被辨識，如
上面的 ‘Point’）則永遠無法被賦值。

模式可以任意地被巢套 (nested)。例如，如果我們有一個由某些點所組成的簡短
list，我們就可以像這樣加入 ‘__match_args__’ 來對它進行匹配：

     class Point:
         __match_args__ = ('x', 'y')
         def __init__(self, x, y):
             self.x = x
             self.y = y

     match points:
         case []:
             print("No points")
         case [Point(0, 0)]:
             print("The origin")
         case [Point(x, y)]:
             print(f"Single point {x}, {y}")
         case [Point(0, y1), Point(0, y2)]:
             print(f"Two on the Y axis at {y1}, {y2}")
         case _:
             print("Something else")

我們可以在模式中加入一個 ‘if’ 子句，稱為「防護 (guard)」。如果該防護為假
，則 ‘match’ 會繼續嘗試下一個 case 區塊。請注意，值的擷取會發生在防護的
評估之前：

     match point:
         case Point(x, y) if x == y:
             print(f"Y=X at {x}")
         case Point(x, y):
             print(f"Not on the diagonal")

此種陳述式的其他幾個重要特色：

   - 與拆解賦值的情況類似，tuple（元組）和 list 模式具有完全相同的意義，
     而且實際上可以匹配任意的序列。一個重要的例外，是它們不能匹配疊代器
     (iterator) 或字串。

   - 序列模式 (sequence pattern) 可支援擴充拆解 (extended unpacking)：
     ‘[x, y, *rest]’ 與 ‘(x, y, *rest)’ 的作用類似於拆解賦值。‘*’ 後面的
     名稱也可以是 ‘_’，所以 ‘(x, y, *_)’ 會匹配一個至少兩項的序列，且不
     會連結那兩項以外的其餘項。

   - 映射模式 (mapping pattern)：‘{"bandwidth": b, "latency": l}’ 能從一
     個 dictionary（字典）中擷取 ‘"bandwidth"’ 及 ‘"latency"’ 的值。與序
     列模式不同，額外的鍵 (key) 會被忽略。一種像是 ‘**rest’ 的拆解方式，
     也是可被支援的。（但 ‘**_’ 則是多餘的做法，所以它並不被允許。）

   - 使用關鍵字 ‘as’ 可以擷取子模式 (subpattern)：

          case (Point(x1, y1), Point(x2, y2) as p2): ...

     將會擷取輸入的第二個元素作為 ‘p2’（只要該輸入是一個由兩個點所組成的
     序列）。

   - 大部分的字面值是藉由相等性 (equality) 來比較，但是單例物件
     (singleton) ‘True’、‘False’ 和 ‘None’ 是藉由標識值 (identity) 來比
     較。

   - 模式可以使用附名常數 (named constant)。這些模式必須是點分隔名稱，以
     免它們被解釋為擷取變數：

          from enum import Enum
          class Color(Enum):
              RED = 'red'
              GREEN = 'green'
              BLUE = 'blue'

          color = Color(input("Enter your choice of 'red', 'blue' or 'green': "))

          match color:
              case Color.RED:
                  print("I see red!")
              case Color.GREEN:
                  print("Grass is green")
              case Color.BLUE:
                  print("I'm feeling the blues :(")

關於更詳細的解釋和其他範例，你可以閱讀 PEP 636(1)，它是以教學的格式編寫
而成。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0636/


File: python.info,  Node: 定義函式 function,  Next: 深入了解函式定義,  Prev: match 陳述式,  Up: 深入了解流程控制

2.4.7 定義函式 (function)
-------------------------

我們可以建立一個函式來產生費式數列到任何一個上界：

     >>> def fib(n):    # write Fibonacci series up to n
     ...     """Print a Fibonacci series up to n."""
     ...     a, b = 0, 1
     ...     while a < n:
     ...         print(a, end=' ')
     ...         a, b = b, a+b
     ...     print()
     ...
     >>> # Now call the function we just defined:
     >>> fib(2000)
     0 1 1 2 3 5 8 13 21 34 55 89 144 233 377 610 987 1597

關鍵字 *note def: 13c5. 介紹一個函式的'定義'。它之後必須連著該函式的名稱
和置於括號之中的一串參數。自下一行起，所有縮排的陳述式成為該函式的主體。

一個函式的第一個陳述式可以是一個字串文本；該字串文本被視為該函式的說明文
件字串，即 'docstring'。（關於 docstring 的細節請參見*note 說明文件字串
(Documentation Strings): 1b22.段落。）有些工具可以使用 docstring 來自動
產生線上或可列印的文件，或讓使用者能以互動的方式在原始碼中瀏覽文件。在原
始碼中加入 docstring 是個好慣例，應該養成這樣的習慣。

函式'執行'時會建立一個新的符號表 (symbol table) 來儲存該函式內的區域變數
(local variable)。更精確地說，所有在函式內的變數賦值都會把該值儲存在一個
區域符號表。然而，在引用一個變數時，會先從區域符號表開始搜尋，其次為外層
函式的區域符號表，其次為全域符號表 (global symbol table)，最後為所有內建
的名稱。因此，在函式中，全域變數及外層函式變數雖然可以被引用，但無法被直
接賦值（除非全域變數是在 *note global: 170. 陳述式中被定義，或外層函式變
數在 *note nonlocal: 123e. 陳述式中被定義）。

在一個函式被呼叫的時候，實際傳入的參數（引數）會被加入至該函式的區域符號
表。因此，引數傳入的方式為'傳值呼叫 (call by value)'（這裡傳遞的'值'永遠
是一個物件的'參照 (reference)'，而不是該物件的值）。 (1) 當一個函式呼叫
別的函式或遞迴呼叫它自己時，在被呼叫的函式中會建立一個新的區域符號表。

函式定義時，會把該函式名稱加入至當前的符號表。函式名稱的值帶有一個型別，
並被直譯器辨識為使用者自定函式 (user-defined function)。該值可以被指定給
別的變數名，使該變數名也可以被當作函式使用。這是常見的重新命名方式：

     >>> fib
     <function fib at 10042ed0>
     >>> f = fib
     >>> f(100)
     0 1 1 2 3 5 8 13 21 34 55 89

如果你是來自別的語言，你可能不同意 ‘fib’ 是個函式，而是個程序
(procedure)，因為它並沒有回傳值。實際上，即使一個函式缺少一個 *note
return: 972. 陳述式，它亦有一個固定的回傳值。這個值稱為 ‘None’（它是一個
內建名稱）。在直譯器中單獨使用 ‘None’ 時，通常不會被顯示。你可以使用
*note print(): f18. 來看到它：

     >>> fib(0)
     >>> print(fib(0))
     None

如果要寫一個函式回傳費式數列的 list 而不是直接印出它，這也很容易：

     >>> def fib2(n):  # return Fibonacci series up to n
     ...     """Return a list containing the Fibonacci series up to n."""
     ...     result = []
     ...     a, b = 0, 1
     ...     while a < n:
     ...         result.append(a)    # see below
     ...         a, b = b, a+b
     ...     return result
     ...
     >>> f100 = fib2(100)    # call it
     >>> f100                # write the result
     [0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89]

這個例子一樣示範了一些新的 Python 特性：

   * *note return: 972. 陳述式會讓一個函式回傳一個值。單獨使用 ‘return’
     不外加一個運算式作為引數時會回傳 ‘None’。一個函式執行到結束也會回傳
     ‘None’。

   * ‘result.append(a)’ 陳述式呼叫了一個 list 物件 ‘result’ 的 'method（
     方法）'。method 為「屬於」一個物件的函式，命名規則為
     ‘obj.methodname’，其中 ‘obj’ 為某個物件（亦可為一運算式），而
     ‘methodname’ 為該 method 的名稱，並由該物件的型別所定義。不同的型別
     定義不同的 method。不同型別的 method 可以擁有一樣的名稱而不會讓
     Python 混淆。（你可以使用 'class'（類別）定義自己的物件型別和
     method，見 *note Class（類別）: 1b23.）範例中的 ‘append()’ method 定
     義在 list 物件中；它會在該 list 的末端加入一個新的元素。這個例子等
     同於 ‘result = result + [a]’，但更有效率。

   ---------- Footnotes ----------

   (1) 實際上，'傳址呼叫 (call by object reference)' 的說法可能較為貼切
。因為，若傳遞的是一個可變物件時，呼叫者將看得見被呼叫者對物件做出的任何
改變（例如被插入 list 內的新項目）。


File: python.info,  Node: 深入了解函式定義,  Next: 間奏曲：程式碼風格 Coding Style,  Prev: 定義函式 function,  Up: 深入了解流程控制

2.4.8 深入了解函式定義
----------------------

定義函式時使用的引數 (argument) 數量是可變的。總共有三種可以組合使用的形
式。

* Menu:

* 預設引數值::
* 關鍵字引數::
* 特殊參數::
* 任意引數列表 (Arbitrary Argument Lists): 任意引數列表 Arbitrary Argument Lists.
* 拆解引數列表（Unpacking Argument Lists）::
* Lambda 運算式::
* 說明文件字串 (Documentation Strings): 說明文件字串 Documentation Strings.
* 函式註釋 (Function Annotations): 函式註釋 Function Annotations.


File: python.info,  Node: 預設引數值,  Next: 關鍵字引數,  Up: 深入了解函式定義

2.4.8.1 預設引數值
..................

為一個或多個引數指定預設值是很有用的方式。函式建立後，可以用比定義時更少
的引數呼叫該函式。例如：

     def ask_ok(prompt, retries=4, reminder='Please try again!'):
         while True:
             reply = input(prompt)
             if reply in {'y', 'ye', 'yes'}:
                 return True
             if reply in {'n', 'no', 'nop', 'nope'}:
                 return False
             retries = retries - 1
             if retries < 0:
                 raise ValueError('invalid user response')
             print(reminder)

該函式可以用以下幾種方式被呼叫：

   * 只給必要引數：‘ask_ok('Do you really want to quit?')’

   * 給予一個選擇性引數：‘ask_ok('OK to overwrite the file?', 2)’

   * 給予所有引數：‘ask_ok('OK to overwrite the file?', 2, 'Come on,
     only yes or no!')’

此例也使用了關鍵字 *note in: 2c5.，用於測試序列中是否包含某個特定值。

預設值是在函式定義當下，於'定義時'的作用域中求值，所以：

     i = 5

     def f(arg=i):
         print(arg)

     i = 6
     f()

將會輸出 ‘5’。

'重要警告'：預設值只求值一次。當預設值為可變物件，例如 list、
dictionary（字典）或許多類別實例時，會產生不同的結果。例如，以下函式於後
續呼叫時會累積曾經傳遞的引數：

     def f(a, L=[]):
         L.append(a)
         return L

     print(f(1))
     print(f(2))
     print(f(3))

將會輸出：

     [1]
     [1, 2]
     [1, 2, 3]

如果不想在後續呼叫之間共用預設值，應以如下方式編寫函式：

     def f(a, L=None):
         if L is None:
             L = []
         L.append(a)
         return L


File: python.info,  Node: 關鍵字引數,  Next: 特殊參數,  Prev: 預設引數值,  Up: 深入了解函式定義

2.4.8.2 關鍵字引數
..................

函式也可以使用*note 關鍵字引數: cb9.，以 ‘kwarg=value’ 的形式呼叫。舉例
來說，以下函式：

     def parrot(voltage, state='a stiff', action='voom', type='Norwegian Blue'):
         print("-- This parrot wouldn't", action, end=' ')
         print("if you put", voltage, "volts through it.")
         print("-- Lovely plumage, the", type)
         print("-- It's", state, "!")

接受一個必要引數 (‘voltage’) 和三個選擇性引數 (‘state’，‘action’，和
‘type’)。該函式可用下列任一方式呼叫：

     parrot(1000)                                          # 1 positional argument
     parrot(voltage=1000)                                  # 1 keyword argument
     parrot(voltage=1000000, action='VOOOOOM')             # 2 keyword arguments
     parrot(action='VOOOOOM', voltage=1000000)             # 2 keyword arguments
     parrot('a million', 'bereft of life', 'jump')         # 3 positional arguments
     parrot('a thousand', state='pushing up the daisies')  # 1 positional, 1 keyword

但以下呼叫方式都無效：

     parrot()                     # required argument missing
     parrot(voltage=5.0, 'dead')  # non-keyword argument after a keyword argument
     parrot(110, voltage=220)     # duplicate value for the same argument
     parrot(actor='John Cleese')  # unknown keyword argument

函式呼叫時，關鍵字引數 (keyword argument) 必須在位置引數 (positional
argument) 後面。所有傳遞的關鍵字引數都必須匹配一個可被函式接受的引數（
‘actor’ 不是 ‘parrot’ 函式的有效引數），而關鍵字引數的順序並不重要。此規
則也包括必要引數，（‘parrot(voltage=1000)’ 也有效）。一個引數不可多次被
賦值，下面就是一個因此限制而無效的例子：

     >>> def function(a):
     ...     pass
     ...
     >>> function(0, a=0)
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: function() got multiple values for argument 'a'

當最後一個參數為 ‘**name’ 形式時，它接收一個 dictionary（字典，詳見
*note Mapping Types -- dict: a69.），該字典包含所有可對應形式參數以外的
關鍵字引數。‘**name’ 可以與 ‘*name’ 參數（下一小節介紹）組合使用，
‘*name’ 接收一個 *note tuple: 1b2a.，該 tuple 包含一般參數以外的位置引數
（‘*name’ 必須出現在 ‘**name’ 前面）。例如，若我們定義這樣的函式：

     def cheeseshop(kind, *arguments, **keywords):
         print("-- Do you have any", kind, "?")
         print("-- I'm sorry, we're all out of", kind)
         for arg in arguments:
             print(arg)
         print("-" * 40)
         for kw in keywords:
             print(kw, ":", keywords[kw])

它可以被如此呼叫：

     cheeseshop("Limburger", "It's very runny, sir.",
                "It's really very, VERY runny, sir.",
                shopkeeper="Michael Palin",
                client="John Cleese",
                sketch="Cheese Shop Sketch")

輸出結果如下：

     -- Do you have any Limburger ?
     -- I'm sorry, we're all out of Limburger
     It's very runny, sir.
     It's really very, VERY runny, sir.
     ----------------------------------------
     shopkeeper : Michael Palin
     client : John Cleese
     sketch : Cheese Shop Sketch

注意，關鍵字引數的輸出順序與呼叫函式時被提供的順序必定一致。


File: python.info,  Node: 特殊參數,  Next: 任意引數列表 Arbitrary Argument Lists,  Prev: 關鍵字引數,  Up: 深入了解函式定義

2.4.8.3 特殊參數
................

在預設情況，引數能以位置或明確地以關鍵字傳遞给 Python 函式。為了程式的可
讀性及效能，限制引數的傳遞方式是合理的，如此，開發者只需查看函式定義，即
可確定各項目是按位置，按位置或關鍵字，還是按關鍵字傳遞。

函式定義可能如以下樣式：

     def f(pos1, pos2, /, pos_or_kwd, *, kwd1, kwd2):
           -----------    ----------     ----------
             |             |                  |
             |        Positional or keyword   |
             |                                - Keyword only
              -- Positional only

‘/’ 和 ‘*’ 是選擇性的。這些符號若被使用，是表明引數被傳遞給函式的參數種
類：僅限位置、位置或關鍵字、僅限關鍵字。關鍵字參數也稱為附名參數 (named
parameters)。

* Menu:

* 位置或關鍵字引數 (Positional-or-Keyword Arguments): 位置或關鍵字引數 Positional-or-Keyword Arguments.
* 僅限位置參數 (Positional-Only Parameters): 僅限位置參數 Positional-Only Parameters.
* 僅限關鍵字引數 (Keyword-Only Arguments): 僅限關鍵字引數 Keyword-Only Arguments.
* 函式範例::
* 回顧::


File: python.info,  Node: 位置或關鍵字引數 Positional-or-Keyword Arguments,  Next: 僅限位置參數 Positional-Only Parameters,  Up: 特殊參數

2.4.8.4 位置或關鍵字引數 (Positional-or-Keyword Arguments)
..........................................................

若函式定義中未使用 ‘/’ 和 ‘*’ 時，引數可以按位置或關鍵字傳遞給函式。


File: python.info,  Node: 僅限位置參數 Positional-Only Parameters,  Next: 僅限關鍵字引數 Keyword-Only Arguments,  Prev: 位置或關鍵字引數 Positional-or-Keyword Arguments,  Up: 特殊參數

2.4.8.5 僅限位置參數 (Positional-Only Parameters)
.................................................

此處再詳述一些細節，特定參數可以標記為'僅限位置'。若參數為'僅限位置'時，
它們的順序很重要，且這些參數不能用關鍵字傳遞。僅限位置參數必須放在 ‘/’（
斜線）之前。‘/’ 用於在邏輯上分開僅限位置參數與其餘參數。如果函式定義中沒
有 ‘/’，則表示沒有任何僅限位置參數。

‘/’ 後面的參數可以是'位置或關鍵字'或'僅限關鍵字'參數。


File: python.info,  Node: 僅限關鍵字引數 Keyword-Only Arguments,  Next: 函式範例,  Prev: 僅限位置參數 Positional-Only Parameters,  Up: 特殊參數

2.4.8.6 僅限關鍵字引數 (Keyword-Only Arguments)
...............................................

要把參數標記為'僅限關鍵字'，表明參數必須以關鍵字引數傳遞，必須在引數列表
中第一個'僅限關鍵字'參數前放上 ‘*’。


File: python.info,  Node: 函式範例,  Next: 回顧,  Prev: 僅限關鍵字引數 Keyword-Only Arguments,  Up: 特殊參數

2.4.8.7 函式範例
................

請看以下的函式定義範例，注意 ‘/’ 和 ‘*’ 記號：

     >>> def standard_arg(arg):
     ...     print(arg)
     ...
     >>> def pos_only_arg(arg, /):
     ...     print(arg)
     ...
     >>> def kwd_only_arg(*, arg):
     ...     print(arg)
     ...
     >>> def combined_example(pos_only, /, standard, *, kwd_only):
     ...     print(pos_only, standard, kwd_only)

第一個函式定義 ‘standard_arg’ 是我們最熟悉的形式，對呼叫方式沒有任何限制
，可以按位置或關鍵字傳遞引數：

     >>> standard_arg(2)
     2

     >>> standard_arg(arg=2)
     2

第二個函式 ‘pos_only_arg’ 的函式定義中有 ‘/’，因此僅限使用位置參數：

     >>> pos_only_arg(1)
     1

     >>> pos_only_arg(arg=1)
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: pos_only_arg() got some positional-only arguments passed as keyword arguments: 'arg'

第三個函式 ‘kwd_only_args’ 的函式定義透過 ‘*’ 表明僅限關鍵字引數：

     >>> kwd_only_arg(3)
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: kwd_only_arg() takes 0 positional arguments but 1 was given

     >>> kwd_only_arg(arg=3)
     3

最後一個函式在同一個函式定義中，使用了全部三種呼叫方式：

     >>> combined_example(1, 2, 3)
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: combined_example() takes 2 positional arguments but 3 were given

     >>> combined_example(1, 2, kwd_only=3)
     1 2 3

     >>> combined_example(1, standard=2, kwd_only=3)
     1 2 3

     >>> combined_example(pos_only=1, standard=2, kwd_only=3)
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: combined_example() got some positional-only arguments passed as keyword arguments: 'pos_only'

最後，請看這個函式定義，如果 ‘**kwds’ 內有 ‘name’ 這個鍵，可能與位置引數
‘name’ 產生潛在衝突：

     def foo(name, **kwds):
         return 'name' in kwds

呼叫該函式不可能回傳 ‘True’，因為關鍵字 ‘'name'’ 永遠是連結在第一個參數
。例如：

     >>> foo(1, **{'name': 2})
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: foo() got multiple values for argument 'name'
     >>>

使用 ‘/’（僅限位置引數）後，就可以了。函式定義會允許 ‘name’ 當作位置引數
，而 ‘'name'’ 也可以當作關鍵字引數中的鍵：

     >>> def foo(name, /, **kwds):
     ...     return 'name' in kwds
     ...
     >>> foo(1, **{'name': 2})
     True

換句話說，僅限位置參數的名稱可以在 ‘**kwds’ 中使用，而不產生歧義。


File: python.info,  Node: 回顧,  Prev: 函式範例,  Up: 特殊參數

2.4.8.8 回顧
............

此用例決定哪些參數可以用於函式定義：

     def f(pos1, pos2, /, pos_or_kwd, *, kwd1, kwd2):

說明：

   * 如果不想讓使用者使用參數名稱，請使用僅限位置。當參數名稱沒有實際意
     義時，若你想控制引數在函式呼叫的排列順序，或同時使用位置參數和任意
     關鍵字時，這種方式很有用。

   * 當參數名稱有意義，且明確的名稱可讓函式定義更易理解，或是你不希望使
     用者依賴引數被傳遞時的位置時，請使用僅限關鍵字。

   * 對於應用程式介面 (API)，使用僅限位置，以防止未來參數名稱被修改時造
     成 API 的中斷性變更。


File: python.info,  Node: 任意引數列表 Arbitrary Argument Lists,  Next: 拆解引數列表（Unpacking Argument Lists）,  Prev: 特殊參數,  Up: 深入了解函式定義

2.4.8.9 任意引數列表 (Arbitrary Argument Lists)
...............................................

最後，有個較不常用的選項，是規定函式被呼叫時，可以使用任意數量的引數。這
些引數會被包裝進一個 tuple 中（詳見 *note Tuples 和序列 (Sequences):
1b2a.）。在可變數量的引數之前，可能有零個或多個普通引數：

     def write_multiple_items(file, separator, *args):
         file.write(separator.join(args))

通常，這些 'variadic'（可變的）引數會出現在參數列表的最末端，這樣它們就
可以把所有傳遞給函式的剩餘輸入引數都撈起來。出現在 ‘*args’ 參數後面的任
何參數必須是「僅限關鍵字」引數，意即它們只能作為關鍵字引數，而不能用作位
置引數。

     >>> def concat(*args, sep="/"):
     ...     return sep.join(args)
     ...
     >>> concat("earth", "mars", "venus")
     'earth/mars/venus'
     >>> concat("earth", "mars", "venus", sep=".")
     'earth.mars.venus'


File: python.info,  Node: 拆解引數列表（Unpacking Argument Lists）,  Next: Lambda 運算式,  Prev: 任意引數列表 Arbitrary Argument Lists,  Up: 深入了解函式定義

2.4.8.10 拆解引數列表（Unpacking Argument Lists）
.................................................

當引數們已經存在一個 list 或 tuple 裡，但為了滿足一個需要個別位置引數的
函式呼叫，而去拆解它們時，情況就剛好相反。例如，內建的 *note range():
8e7. 函式要求分開的 'start' 和 'stop' 引數。如果這些引數不是分開的，則要
在呼叫函式時，用 ‘*’ 運算子把引數們從 list 或 tuple 中拆解出來：

     >>> list(range(3, 6))            # normal call with separate arguments
     [3, 4, 5]
     >>> args = [3, 6]
     >>> list(range(*args))            # call with arguments unpacked from a list
     [3, 4, 5]

同樣地，dictionary（字典）可以用 ‘**’ 運算子傳遞關鍵字引數：

     >>> def parrot(voltage, state='a stiff', action='voom'):
     ...     print("-- This parrot wouldn't", action, end=' ')
     ...     print("if you put", voltage, "volts through it.", end=' ')
     ...     print("E's", state, "!")
     ...
     >>> d = {"voltage": "four million", "state": "bleedin' demised", "action": "VOOM"}
     >>> parrot(**d)
     -- This parrot wouldn't VOOM if you put four million volts through it. E's bleedin' demised !


File: python.info,  Node: Lambda 運算式,  Next: 說明文件字串 Documentation Strings,  Prev: 拆解引數列表（Unpacking Argument Lists）,  Up: 深入了解函式定義

2.4.8.11 Lambda 運算式
......................

*note lambda: 1234. 關鍵字用於建立小巧的匿名函式。‘lambda a, b: a+b’ 函
式返回兩個引數的和。Lambda 函式可用於任何需要函式物件的地方。在語法上，
它們被限定只能是單一運算式。在語義上，它就是一個普通函式定義的語法糖
(syntactic sugar)。與巢狀函式定義一樣，lambda 函式可以從包含它的作用域中
引用變數：

     >>> def make_incrementor(n):
     ...     return lambda x: x + n
     ...
     >>> f = make_incrementor(42)
     >>> f(0)
     42
     >>> f(1)
     43

上面的例子用 lambda 運算式回傳了一個函式。另外的用法是傳遞一個小函式當作
引數：

     >>> pairs = [(1, 'one'), (2, 'two'), (3, 'three'), (4, 'four')]
     >>> pairs.sort(key=lambda pair: pair[1])
     >>> pairs
     [(4, 'four'), (1, 'one'), (3, 'three'), (2, 'two')]


File: python.info,  Node: 說明文件字串 Documentation Strings,  Next: 函式註釋 Function Annotations,  Prev: Lambda 運算式,  Up: 深入了解函式定義

2.4.8.12 說明文件字串 (Documentation Strings)
.............................................

以下是關於說明文件字串內容和格式的慣例。

第一行都是一段關於此物件目的之簡短摘要。為保持簡潔，不應在這裡明確地陳述
物件的名稱或型別，因為有其他方法可以達到相同目的（除非該名稱剛好是一個描
述函式運算的動詞）。這一行應以大寫字母開頭，以句號結尾。

文件字串為多行時，第二行應為空白行，在視覺上將摘要與其餘描述分開。後面幾
行可包含一或多個段落，描述此物件的呼叫慣例、副作用等。

Python 剖析器 (parser) 不會去除 Python 中多行字串的縮排，因此，處理說明
文件的工具應在必要時去除縮排。這項操作遵循以下慣例：在字串第一行'之後'的
第一個非空白行決定了整個說明文件字串的縮排量（不能用第一行的縮排，因為它
通常與字串的開頭引號們相鄰，其縮排在字串文本中並不明顯），然後，所有字串
行開頭處與此縮排量「等價」的空白字元會被去除。不應出現比上述縮進量更少的
字串行，但若真的出現了，這些行的全部前導空白字元都應被去除。展開 tab 鍵
後（通常為八個空格），應測試空白字元量是否等價。

下面是多行說明字串的一個範例：

     >>> def my_function():
     ...     """Do nothing, but document it.
     ...
     ...     No, really, it doesn't do anything.
     ...     """
     ...     pass
     ...
     >>> print(my_function.__doc__)
     Do nothing, but document it.

         No, really, it doesn't do anything.


File: python.info,  Node: 函式註釋 Function Annotations,  Prev: 說明文件字串 Documentation Strings,  Up: 深入了解函式定義

2.4.8.13 函式註釋 (Function Annotations)
........................................

*note 函式註釋: 1b3a.是選擇性的元資料（metadata）資訊，描述使用者定義函
式所使用的型別（更多資訊詳見 PEP 3107(1) 和 PEP 484(2)）。

*note 註釋: 1b3b.以 dictionary（字典）的形式存放在函式的
‘__annotations__’ 屬性中，且不會影響函式的任何其他部分。參數註釋的定義方
式是在參數名稱後加一個冒號，冒號後面跟著一個對註釋求值的運算式。回傳註釋
的定義方式是在參數列表和 *note def: 13c5. 陳述式結尾的冒號中間，用一個
‘->’ 文字接著一個運算式。以下範例註釋了一個必要引數、一個選擇性引數，以
及回傳值：

     >>> def f(ham: str, eggs: str = 'eggs') -> str:
     ...     print("Annotations:", f.__annotations__)
     ...     print("Arguments:", ham, eggs)
     ...     return ham + ' and ' + eggs
     ...
     >>> f('spam')
     Annotations: {'ham': <class 'str'>, 'return': <class 'str'>, 'eggs': <class 'str'>}
     Arguments: spam eggs
     'spam and eggs'

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3107/

   (2) https://peps.python.org/pep-0484/


File: python.info,  Node: 間奏曲：程式碼風格 Coding Style,  Prev: 深入了解函式定義,  Up: 深入了解流程控制

2.4.9 間奏曲：程式碼風格 (Coding Style)
---------------------------------------

現在你即將要寫更長、更複雜的 Python 程式，是時候討論一下'編碼樣式'了。大
多數語言都能以不同的樣式被書寫（或更精確地說，被'格式化'），而有些樣式比
其他的更具可讀性。能讓其他人輕鬆閱讀你的程式碼永遠是一個好主意，而使用優
良的編碼樣式對此有極大的幫助。

對於 Python，大多數的專案都遵循 PEP 8(1) 的樣式指南；它推行的編碼樣式相
當可讀且賞心悅目。每個 Python 開發者都應該花點時間研讀；這裡是該指南的核
心重點：

   * 用 4 個空格縮排，不要用 tab 鍵。

     4 個空格是小縮排（容許更大的巢套深度）和大縮排（較易閱讀）之間的折
     衷方案。Tab 鍵會造成混亂，最好別用。

   * 換行，使一行不超過 79 個字元。

     換行能讓使用小顯示器的使用者方便閱讀，也可以在較大顯示器上並排陳列
     多個程式碼檔案。

   * 用空行分隔函式和 class（類別），及函式內較大塊的程式碼。

   * 如果可以，把註解放在單獨一行。

   * 使用說明字串。

   * 運算子前後、逗號後要加空格，但不要直接放在括號內側：‘a = f(1, 2) +
     g(3, 4)’。

   * Class 和函式的命名樣式要一致；按慣例，命名 class 用
     ‘UpperCamelCase’（駝峰式大小寫），命名函式與 method 用
     ‘lowercase_with_underscores’（小寫加底線）。永遠用 ‘self’ 作為
     method 第一個引數的名稱（關於 class 和 method，詳見 *note 初見
     class: 1b3e.）。

   * 若程式碼是為了用於國際環境時，不要用花俏的編碼。Python 預設的 UTF-8
     或甚至普通的 ASCII，就可以勝任各種情況。

   * 同樣地，若不同語言使用者閱讀或維護程式碼的可能性微乎其微，就不要在
     命名時使用非 ASCII 字元。

註解
....

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0008/


File: python.info,  Node: 資料結構,  Next: 模組 Module,  Prev: 深入了解流程控制,  Up: Python 教學

2.5 資料結構
============

這個章節將會更深入的介紹一些你已經學過的東西的細節上，並且加入一些你還沒
有接觸過的部分。

* Menu:

* 進一步了解 List（串列）::
* del 陳述式::
* Tuples 和序列 (Sequences): Tuples 和序列 Sequences.
* 集合 (Sets): 集合 Sets.
* 字典（Dictionary）::
* 迴圈技巧::
* 深入了解條件 (Condition): 深入了解條件 Condition.
* 序列和其他資料類型之比較::


File: python.info,  Node: 進一步了解 List（串列）,  Next: del 陳述式,  Up: 資料結構

2.5.1 進一步了解 List（串列）
-----------------------------

List（串列）這個資料型態，具有更多操作的方法。下面條列了所有關於 list 物
件的 method：

 -- 方法: list.append (x)

     將一個新的項目加到 list 的尾端。等同於 ‘a[len(a):] = [x]’。

 -- 方法: list.extend (iterable)

     將 iterable（可疊代物件）接到 list 的尾端。等同於 ‘a[len(a):] =
     iterable’。

 -- 方法: list.insert (i, x)

     將一個項目插入至 list 中給定的位置。第一個引數為插入處前元素的索引
     值，所以 ‘a.insert(0, x)’ 會插入在 list 首位，而 ‘a.insert(len(a),
     x)’ 則相當於 ‘a.append(x)’。

 -- 方法: list.remove (x)

     刪除 list 中第一個值等於 'x' 的元素。若 list 中無此元素則會觸發
     *note ValueError: 1e7.。

 -- 方法: list.pop ([i])

     移除 list 中給定位置的項目，並回傳它。如果沒有指定位置， ‘a.pop()’
     將會移除 list 中最後的項目並回傳它。若 list 是空的或是索引值超出範
     圍，則會引發 *note IndexError: 14a3. 例外。

 -- 方法: list.clear ()

     刪除 list 中所有項目。這等同於 ‘del a[:]’。

 -- 方法: list.index (x[, start[, end]])

     回傳 list 中第一個值等於 'x' 的項目之索引值（從零開始的索引）。若
     list 中無此項目，則丟出 *note ValueError: 1e7. 錯誤。

     引數 'start' 和 'end' 的定義跟在 slice 表示法中相同，搜尋的動作被這
     兩個引數限定在 list 中特定的子序列。但要注意的是，回傳的索引值是從
     list 的開頭開始算，而不是從 'start' 開始算。

 -- 方法: list.count (x)

     回傳 'x' 在 list 中所出現的次數。

 -- 方法: list.sort (*, key=None, reverse=False)

     將 list 中的項目排序。（可使用引數來進行客製化的排序，請參考 *note
     sorted(): b75. 部分的解釋）

 -- 方法: list.reverse ()

     將 list 中的項目前後順序反過來。

 -- 方法: list.copy ()

     回傳一個淺複製 (shallow copy) 的 list。等同於 ‘a[:]’。

以下是一個使用到許多 list 物件方法的例子：

     >>> fruits = ['orange', 'apple', 'pear', 'banana', 'kiwi', 'apple', 'banana']
     >>> fruits.count('apple')
     2
     >>> fruits.count('tangerine')
     0
     >>> fruits.index('banana')
     3
     >>> fruits.index('banana', 4)  # Find next banana starting at position 4
     6
     >>> fruits.reverse()
     >>> fruits
     ['banana', 'apple', 'kiwi', 'banana', 'pear', 'apple', 'orange']
     >>> fruits.append('grape')
     >>> fruits
     ['banana', 'apple', 'kiwi', 'banana', 'pear', 'apple', 'orange', 'grape']
     >>> fruits.sort()
     >>> fruits
     ['apple', 'apple', 'banana', 'banana', 'grape', 'kiwi', 'orange', 'pear']
     >>> fruits.pop()
     'pear'

你可能會注意到一些方法，像是 ‘insert’、‘remove’ 或者是 ‘sort’，並沒有印
出回傳值，事實上，他們回傳預設值 ‘None’ (1)。這是一個用於 Python 中所有
可變資料結構的設計法則。

另外你可能也會發現，不是所有資料都可以被排序或比較。例如，‘[None,
'hello', 10]’ 就不可排序，因為整數不能與字串比較，而 ‘None’ 不能與其他型
別比較。有些型別根本就沒有被定義彼此之間的大小順序，例如，‘3+4j < 5+7j’
就是一個無效的比較。

* Menu:

* 將 List 作為 Stack（堆疊）使用::
* 將 List 作為 Queue（佇列）使用::
* List Comprehensions（串列綜合運算）::
* 巢狀的 List Comprehensions::

   ---------- Footnotes ----------

   (1) 其他語言可以回傳變更後的物件，這就允許 method 的串連，例如
‘d->insert("a")->remove("b")->sort();’。


File: python.info,  Node: 將 List 作為 Stack（堆疊）使用,  Next: 將 List 作為 Queue（佇列）使用,  Up: 進一步了解 List（串列）

2.5.1.1 將 List 作為 Stack（堆疊）使用
......................................

List 的操作方法使得它非常簡單可以用來實作 stack（堆疊）。Stack 為一個遵
守最後加入元素最先被取回（後進先出，"last-in, first-out"）規則的資料結構
。你可以使用方法 ‘append()’ 將一個項目放到堆疊的頂層。而使用方法 ‘pop()’
且不給定索引值去取得堆疊最上面的項目。舉例而言：

     >>> stack = [3, 4, 5]
     >>> stack.append(6)
     >>> stack.append(7)
     >>> stack
     [3, 4, 5, 6, 7]
     >>> stack.pop()
     7
     >>> stack
     [3, 4, 5, 6]
     >>> stack.pop()
     6
     >>> stack.pop()
     5
     >>> stack
     [3, 4]


File: python.info,  Node: 將 List 作為 Queue（佇列）使用,  Next: List Comprehensions（串列綜合運算）,  Prev: 將 List 作為 Stack（堆疊）使用,  Up: 進一步了解 List（串列）

2.5.1.2 將 List 作為 Queue（佇列）使用
......................................

我們也可以將 list 當作 queue（佇列）使用，即最先加入元素最先被取回（先進
先出，"first-in, first-out"）的資料結構。然而，list 在這種使用方式下效率
較差。使用 ‘append’ 和 ‘pop’ 來加入和取出尾端的元素較快，而使用 ‘insert’
和 ‘pop’ 來插入和取出頭端的元素較慢（因為其他元素都需要挪動一格）。

如果要實作 queue，請使用 *note collections.deque: 580.，其被設計成能快速
的從頭尾兩端加入和取出。例如：

     >>> from collections import deque
     >>> queue = deque(["Eric", "John", "Michael"])
     >>> queue.append("Terry")           # Terry arrives
     >>> queue.append("Graham")          # Graham arrives
     >>> queue.popleft()                 # The first to arrive now leaves
     'Eric'
     >>> queue.popleft()                 # The second to arrive now leaves
     'John'
     >>> queue                           # Remaining queue in order of arrival
     deque(['Michael', 'Terry', 'Graham'])


File: python.info,  Node: List Comprehensions（串列綜合運算）,  Next: 巢狀的 List Comprehensions,  Prev: 將 List 作為 Queue（佇列）使用,  Up: 進一步了解 List（串列）

2.5.1.3 List Comprehensions（串列綜合運算）
...........................................

List comprehension（串列綜合運算）讓你可以用簡潔的方法建立 list。常見的
應用是基於一個序列或 iterable（可疊代物件），將每一個元素經過某個運算的
結果串接起來成為新的 list，或是建立一個子序列，其每一個元素皆滿足一個特
定的條件。

舉例來說，假設我們要建立一個「平方的 list」：

     >>> squares = []
     >>> for x in range(10):
     ...     squares.append(x**2)
     ...
     >>> squares
     [0, 1, 4, 9, 16, 25, 36, 49, 64, 81]

注意這是建立（或覆寫）一個變數叫 ‘x’，其在迴圈結束後仍然存在。我們可以這
樣產生平方串列而不造成任何 side effects（副作用）：

     squares = list(map(lambda x: x**2, range(10)))

或與此相等的：

     squares = [x**2 for x in range(10)]

這樣更簡潔和易讀。

一個 list comprehension 的組成，是在一對方括號內，放入一個 expression（
運算式）、一個 ‘for’ 子句、再接著零個或多個 ‘for’ 或 ‘if’ 子句。結果會是
一個新的 list，內容是在後面的 ‘for’ 和 ‘if’ 子句情境下，對前面運算式求值
的結果。例如，這個 list comprehension 組合了兩個 list 中彼此相異的元素：

     >>> [(x, y) for x in [1,2,3] for y in [3,1,4] if x != y]
     [(1, 3), (1, 4), (2, 3), (2, 1), (2, 4), (3, 1), (3, 4)]

而它就等於：

     >>> combs = []
     >>> for x in [1,2,3]:
     ...     for y in [3,1,4]:
     ...         if x != y:
     ...             combs.append((x, y))
     ...
     >>> combs
     [(1, 3), (1, 4), (2, 3), (2, 1), (2, 4), (3, 1), (3, 4)]

注意 *note for: 2c3. 和 *note if: 2c4. 在這兩段程式裡的順序是相同的。

如果 expression 是一個 tuple（例如上面例子中的 ‘(x, y)’），它必須加上括
號：

     >>> vec = [-4, -2, 0, 2, 4]
     >>> # create a new list with the values doubled
     >>> [x*2 for x in vec]
     [-8, -4, 0, 4, 8]
     >>> # filter the list to exclude negative numbers
     >>> [x for x in vec if x >= 0]
     [0, 2, 4]
     >>> # apply a function to all the elements
     >>> [abs(x) for x in vec]
     [4, 2, 0, 2, 4]
     >>> # call a method on each element
     >>> freshfruit = ['  banana', '  loganberry ', 'passion fruit  ']
     >>> [weapon.strip() for weapon in freshfruit]
     ['banana', 'loganberry', 'passion fruit']
     >>> # create a list of 2-tuples like (number, square)
     >>> [(x, x**2) for x in range(6)]
     [(0, 0), (1, 1), (2, 4), (3, 9), (4, 16), (5, 25)]
     >>> # the tuple must be parenthesized, otherwise an error is raised
     >>> [x, x**2 for x in range(6)]
       File "<stdin>", line 1
         [x, x**2 for x in range(6)]
          ^^^^^^^
     SyntaxError: did you forget parentheses around the comprehension target?
     >>> # flatten a list using a listcomp with two 'for'
     >>> vec = [[1,2,3], [4,5,6], [7,8,9]]
     >>> [num for elem in vec for num in elem]
     [1, 2, 3, 4, 5, 6, 7, 8, 9]

List comprehensions 可以含有複雜的 expression 和巢狀的函式：

     >>> from math import pi
     >>> [str(round(pi, i)) for i in range(1, 6)]
     ['3.1', '3.14', '3.142', '3.1416', '3.14159']


File: python.info,  Node: 巢狀的 List Comprehensions,  Prev: List Comprehensions（串列綜合運算）,  Up: 進一步了解 List（串列）

2.5.1.4 巢狀的 List Comprehensions
..................................

在 list comprehesion 中開頭的 expression 可以是任何形式的 expression，包
括再寫一個 list comprehension。

考慮以下表示 3x4 矩陣的範例，使用 list 包含 3 個長度為 4 的 list ：

     >>> matrix = [
     ...     [1, 2, 3, 4],
     ...     [5, 6, 7, 8],
     ...     [9, 10, 11, 12],
     ... ]

以下的 list comprehesion 會將矩陣的行與列作轉置：

     >>> [[row[i] for row in matrix] for i in range(4)]
     [[1, 5, 9], [2, 6, 10], [3, 7, 11], [4, 8, 12]]

如同我們在上一節看到的，內部的 list comprehension 會依據後面的 *note
for: 2c3. 環境被求值，所以這個例子就等於：

     >>> transposed = []
     >>> for i in range(4):
     ...     transposed.append([row[i] for row in matrix])
     ...
     >>> transposed
     [[1, 5, 9], [2, 6, 10], [3, 7, 11], [4, 8, 12]]

而它也和這一段相同：

     >>> transposed = []
     >>> for i in range(4):
     ...     # the following 3 lines implement the nested listcomp
     ...     transposed_row = []
     ...     for row in matrix:
     ...         transposed_row.append(row[i])
     ...     transposed.append(transposed_row)
     ...
     >>> transposed
     [[1, 5, 9], [2, 6, 10], [3, 7, 11], [4, 8, 12]]

在實際運用上，我們傾向於使用內建函式 (built-in functions) 而不是複雜的流
程控制陳述式。在這個例子中，使用 *note zip(): 774. 函式會非常有效率：

     >>> list(zip(*matrix))
     [(1, 5, 9), (2, 6, 10), (3, 7, 11), (4, 8, 12)]

關於星號的更多細節，請參考*note 拆解引數列表（Unpacking Argument
Lists）: 1b33.。


File: python.info,  Node: del 陳述式,  Next: Tuples 和序列 Sequences,  Prev: 進一步了解 List（串列）,  Up: 資料結構

2.5.2 ‘del’ 陳述式
------------------

有一個方法可以藉由索引而不是值來刪除 list 中的項目：*note del: 16a9. 陳
述式。這和 ‘pop()’ method 傳回一個值不同，‘del’ 陳述式可以用來刪除 list
中的片段或者清空整個 list（我們之前藉由指派一個空的 list 給想刪除的片段
來完成這件事）。例如：

     >>> a = [-1, 1, 66.25, 333, 333, 1234.5]
     >>> del a[0]
     >>> a
     [1, 66.25, 333, 333, 1234.5]
     >>> del a[2:4]
     >>> a
     [1, 66.25, 1234.5]
     >>> del a[:]
     >>> a
     []

*note del: 16a9. 也可以用來刪除整個變數：

     >>> del a

刪除之後，對 ‘a’ 的參照將會造成錯誤（至少在另一個值又被指派到它之前）。
我們將在後面看到更多關於 *note del: 16a9. 的其他用法。


File: python.info,  Node: Tuples 和序列 Sequences,  Next: 集合 Sets,  Prev: del 陳述式,  Up: 資料結構

2.5.3 Tuples 和序列 (Sequences)
-------------------------------

我們看到 list 和字串 (string) 有許多共同的特性，像是索引操作 (indexing)
以及切片操作 (slicing) 。他們是'序列'資料類型中的兩個例子（請參考*note
Sequence Types -- list, tuple, range: 1b4d.）。由於 Python 是個持續發展
中的語言，未來可能還會有其他的序列資料類型加入。接著要介紹是下一個標準序
列資料類型：'tuple'。

一個 tuple 是由若干個值藉由逗號區隔而組成，例如：

     >>> t = 12345, 54321, 'hello!'
     >>> t[0]
     12345
     >>> t
     (12345, 54321, 'hello!')
     >>> # Tuples may be nested:
     >>> u = t, (1, 2, 3, 4, 5)
     >>> u
     ((12345, 54321, 'hello!'), (1, 2, 3, 4, 5))
     >>> # Tuples are immutable:
     >>> t[0] = 88888
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: 'tuple' object does not support item assignment
     >>> # but they can contain mutable objects:
     >>> v = ([1, 2, 3], [3, 2, 1])
     >>> v
     ([1, 2, 3], [3, 2, 1])

如同我們看到的，被輸出的 tuple 總是以括號包著，如此巢狀的 tuple 才能被正
確的直譯 (interpret)；他們可以是以被括號包著或不被包著的方式當作輸入，雖
然括號的使用常常是有其必要的（譬如此 tuple 是一個較大的運算式的一部分）
。指派東西給 tuple 中的個別項目是不行的，但是可以建立含有可變物件（譬如
list）的 tuple。

雖然 tuple 和 list 看起來很類似，但是他們通常用在不同的情況與不同目的。
tuple 是 *note immutable: 1b02.（不可變的），通常儲存異質的元素序列，並
可經由拆解 (unpacking)（請參考本節後段）或索引 (indexing) 來存取（或者在
使用 *note namedtuples: 1ae. 的時候藉由屬性 (attribute) 來存取）。List 是
*note mutable: 1b07.（可變的），其元素通常是同質的且可藉由疊代整個 list
來存取。

一個特別的議題是，關於建立一個含有 0 個或 1 個項目的 tuple：語法上會採納
一些奇怪的用法。空的 tuple 藉由一對空括號來建立；含有一個項目的 tuple 經
由一個值加上一個逗點來建立（用括號把一個單一的值包住是不夠的）。醜，但有
效率。例如：

     >>> empty = ()
     >>> singleton = 'hello',    # <-- note trailing comma
     >>> len(empty)
     0
     >>> len(singleton)
     1
     >>> singleton
     ('hello',)

陳述式 ‘t = 12345, 54321, 'hello!'’ 就是一個 'tuple packing' 的例子：
‘12345’，‘54321’ 和 ‘'hello!'’ 一起被放進 tuple 裡。反向操作也可以：

     >>> x, y, z = t

這個正是我們所說序列拆解 ('sequence unpacking')，可運用在任何位在等號右
邊的序列。序列拆解要求等號左邊的變數數量必須與等號右邊的序列中的元素數量
相同。注意，多重指派就只是 tuple packing 和序列拆解的結合而已。


File: python.info,  Node: 集合 Sets,  Next: 字典（Dictionary）,  Prev: Tuples 和序列 Sequences,  Up: 資料結構

2.5.4 集合 (Sets)
-----------------

Python 也包含了一種用在 'set'（集合）的資料類型。一個 set 是一組無序且沒
有重複的元素。基本的使用方式包括了隸屬資格檢測和消除重複元素。 Set 物件
也支援聯集、交集、差集和互斥等數學運算。

大括號或 *note set(): 57d. 函式都可以用來建立 set。注意：要建立一個空的
set，你必須使用 ‘set()’ 而不是 ‘{}’；後者會建立一個空的 dictionary，一種
我們將在下一節討論的資料結構。

這裡是一個簡單的演示：

     >>> basket = {'apple', 'orange', 'apple', 'pear', 'orange', 'banana'}
     >>> print(basket)                      # show that duplicates have been removed
     {'orange', 'banana', 'pear', 'apple'}
     >>> 'orange' in basket                 # fast membership testing
     True
     >>> 'crabgrass' in basket
     False

     >>> # Demonstrate set operations on unique letters from two words
     >>>
     >>> a = set('abracadabra')
     >>> b = set('alacazam')
     >>> a                                  # unique letters in a
     {'a', 'r', 'b', 'c', 'd'}
     >>> a - b                              # letters in a but not in b
     {'r', 'd', 'b'}
     >>> a | b                              # letters in a or b or both
     {'a', 'c', 'r', 'd', 'b', 'm', 'z', 'l'}
     >>> a & b                              # letters in both a and b
     {'a', 'c'}
     >>> a ^ b                              # letters in a or b but not both
     {'r', 'd', 'b', 'm', 'z', 'l'}

和 *note list comprehensions: 1b48. 類似，也有 set comprehensions（集合
綜合運算）：

     >>> a = {x for x in 'abracadabra' if x not in 'abc'}
     >>> a
     {'r', 'd'}


File: python.info,  Node: 字典（Dictionary）,  Next: 迴圈技巧,  Prev: 集合 Sets,  Up: 資料結構

2.5.5 字典（Dictionary）
------------------------

下一個常用的 Python 內建資料類型為 'dictionary'（請參考*note Mapping
Types -- dict: a69.）。 Dictionary 有時被稱為「關聯記憶體」(associative
memories) 或「關聯陣列」(associative arrays)。不像序列是由一個範圍內的數
字當作索引，dictionary 是由'鍵' (key) 來當索引，鍵可以是任何不可變的類型
；字串和數字都可以當作鍵。Tuple 也可以當作鍵，如果他們只含有字串、數字或
tuple；若一個 tuple 直接或間接地含有任何可變的物件，它就不能當作鍵。你無
法使用 list 當作鍵，因為 list 可以經由索引指派 (index assignment)、切片
指派 (slice assignment) 或是像 ‘append()’ 和 ‘extend()’ 等 method 被修改
。

思考 dictionary 最好的方式是把它想成是一組'鍵值'對 ('key: value' pair) 的
set，其中鍵在同一個 dictionary 裡必須是獨一無二的。使用一對大括號可建立
一個空的 dictionary：‘{}’。將一串由逗號分隔的鍵值對置於大括號則可初始化
字典的鍵值對。這同樣也是字典輸出時的格式。

Dictionary 主要的操作為藉由鍵來儲存一個值並且可藉由該鍵來取出該值。也可
以使用 ‘del’ 來刪除鍵值對。如果我們使用用過的鍵來儲存，該鍵所對應的較舊
的值會被覆蓋。使用不存在的鍵來取出值會造成錯誤。

對 dictionary 使用 ‘list(d)’ 會得到一個包含該字典所有鍵的 list，其排列順
序為插入時的順序。（若想要排序，則使用 ‘sorted(d)’ 代替即可）。如果想確
認一個鍵是否已存在於字典中，可使用關鍵字 *note in: 2c5.。

這是個使用一個 dictionary 的簡單範例：

     >>> tel = {'jack': 4098, 'sape': 4139}
     >>> tel['guido'] = 4127
     >>> tel
     {'jack': 4098, 'sape': 4139, 'guido': 4127}
     >>> tel['jack']
     4098
     >>> del tel['sape']
     >>> tel['irv'] = 4127
     >>> tel
     {'jack': 4098, 'guido': 4127, 'irv': 4127}
     >>> list(tel)
     ['jack', 'guido', 'irv']
     >>> sorted(tel)
     ['guido', 'irv', 'jack']
     >>> 'guido' in tel
     True
     >>> 'jack' not in tel
     False

函式 *note dict(): 23b. 可直接透過一串鍵值對序列來建立 dictionary：

     >>> dict([('sape', 4139), ('guido', 4127), ('jack', 4098)])
     {'sape': 4139, 'guido': 4127, 'jack': 4098}

此外，dict comprehensions 也可以透過任意鍵與值的運算式來建立 dictionary
：

     >>> {x: x**2 for x in (2, 4, 6)}
     {2: 4, 4: 16, 6: 36}

當鍵是簡單的字串時，使用關鍵字引數 (keyword arguments) 有時會較為簡潔：

     >>> dict(sape=4139, guido=4127, jack=4098)
     {'sape': 4139, 'guido': 4127, 'jack': 4098}


File: python.info,  Node: 迴圈技巧,  Next: 深入了解條件 Condition,  Prev: 字典（Dictionary）,  Up: 資料結構

2.5.6 迴圈技巧
--------------

當對 dictionary 作迴圈時，鍵以及其對應的值可以藉由使用 *note items():
773. method 來同時取得：

     >>> knights = {'gallahad': 'the pure', 'robin': 'the brave'}
     >>> for k, v in knights.items():
     ...     print(k, v)
     ...
     gallahad the pure
     robin the brave

當對序列作迴圈時，位置索引及其對應的值可以藉由使用 *note enumerate():
13ea. 函式來同時取得：

     >>> for i, v in enumerate(['tic', 'tac', 'toe']):
     ...     print(i, v)
     ...
     0 tic
     1 tac
     2 toe

要同時對兩個以上的序列作迴圈，可以將其以成對的方式放入 *note zip(): 774.
函式：

     >>> questions = ['name', 'quest', 'favorite color']
     >>> answers = ['lancelot', 'the holy grail', 'blue']
     >>> for q, a in zip(questions, answers):
     ...     print('What is your {0}?  It is {1}.'.format(q, a))
     ...
     What is your name?  It is lancelot.
     What is your quest?  It is the holy grail.
     What is your favorite color?  It is blue.

要對序列作反向的迴圈，首先先寫出正向的序列，再對其使用 *note reversed():
80a. 函式：

     >>> for i in reversed(range(1, 10, 2)):
     ...     print(i)
     ...
     9
     7
     5
     3
     1

要以迴圈對序列作排序，使用 *note sorted(): b75. 函式會得到一個新的經排序
過的 list ，但不會改變原本的序列：

     >>> basket = ['apple', 'orange', 'apple', 'pear', 'orange', 'banana']
     >>> for i in sorted(basket):
     ...     print(i)
     ...
     apple
     apple
     banana
     orange
     orange
     pear

對序列使用 *note set(): 57d. 可去除重複元素。對序列使用 *note sorted():
b75. 加上 *note set(): 57d.，則是對經過排序後的非重複元素跑迴圈的慣用方
法：

     >>> basket = ['apple', 'orange', 'apple', 'pear', 'orange', 'banana']
     >>> for f in sorted(set(basket)):
     ...     print(f)
     ...
     apple
     banana
     orange
     pear

有時我們會想要以迴圈來改變的一個 list，但是，通常建立一個新的 list 會更
簡單且安全：

     >>> import math
     >>> raw_data = [56.2, float('NaN'), 51.7, 55.3, 52.5, float('NaN'), 47.8]
     >>> filtered_data = []
     >>> for value in raw_data:
     ...     if not math.isnan(value):
     ...         filtered_data.append(value)
     ...
     >>> filtered_data
     [56.2, 51.7, 55.3, 52.5, 47.8]


File: python.info,  Node: 深入了解條件 Condition,  Next: 序列和其他資料類型之比較,  Prev: 迴圈技巧,  Up: 資料結構

2.5.7 深入了解條件 (Condition)
------------------------------

使用在 ‘while’ 和 ‘if’ 陳述式的條件句可以包含任何運算子，而不是只有比較
運算子 (comparisons) 。

比較運算子 ‘in’ 和 ‘not in’ 用於隸屬資格檢測，在容器中檢查一個值是否存在
（或不存在）。運算子 ‘is’ 和 ‘is not’ 比較兩個物件是否真的是相同的物件。
所有比較運算子的優先度都相同且都低於數值運算子。

比較運算是可以串連在一起的。例如， ‘a < b == c’ 就是在測試 ‘a’ 是否小於
‘b’ 和 ‘b’ 是否等於 ‘c’。

比較運算可以結合布林運算子 ‘and’ 和 ‘or’，且一個比較運算的結果（或任何其
他布林運算式）可以加上 ‘not’ 來否定。這些運算子的優先度都比比較運算子還
低，其中，‘not’ 的優先度最高，‘or’ 的優先度最低，因此 ‘A and not B or C’
等同於 ‘(A and (not B)) or C’。一如往常，括號可以用來表示任何想要的組合
。

布林運算子 ‘and’ 和 ‘or’ 也被稱為'短路 (short-circuit)' 運算子：會將其引
數從左至右進行運算，當結果出現時即結束運算。例如，若 ‘A’ 和 ‘C’ 為真但
‘B’ 為假，則 ‘A and B and C’ 的運算並不會執行到 ‘C’。當運算結果被當成一
般值而非布林值時，短路運算子的回傳值為最後被求值的引數。

將一個比較運算或其他布林運算式的結果指派給一個變數是可以的。例如：

     >>> string1, string2, string3 = '', 'Trondheim', 'Hammer Dance'
     >>> non_null = string1 or string2 or string3
     >>> non_null
     'Trondheim'

注意，Python 與 C 語言不一樣，在運算式裡進行指派必須外顯地使用*note
海象運算子: 1b55. ‘:=’。 這樣做避免了在 C 語言裡常見的一種問題：想要打
‘==’ 卻在運算式裡輸入 ‘=’。


File: python.info,  Node: 序列和其他資料類型之比較,  Prev: 深入了解條件 Condition,  Up: 資料結構

2.5.8 序列和其他資料類型之比較
------------------------------

序列物件通常可以拿來和其他相同類型的物件做比較。這種比較使用'詞典式
(lexicographical)' 順序：首先比較各自最前面的那項，若不相同，便可決定結
果；若相同，則比較下一項，以此類推，直到其中一個序列完全用完。如果被拿出
來比較的兩項本身又是相同的序列類型，則詞典式比較會遞迴地執行。如果兩個序
列所有的項目都相等，則此兩個序列被認為是相等的。如果其中一個序列是另一個
的子序列，則較短的那個序列為較小的序列。字串的詞典式順序使用 Unicode 的
碼位 (code point) 編號來排序個別字元。以下是一些相同序列類型的比較：

     (1, 2, 3)              < (1, 2, 4)
     [1, 2, 3]              < [1, 2, 4]
     'ABC' < 'C' < 'Pascal' < 'Python'
     (1, 2, 3, 4)           < (1, 2, 4)
     (1, 2)                 < (1, 2, -1)
     (1, 2, 3)             == (1.0, 2.0, 3.0)
     (1, 2, ('aa', 'ab'))   < (1, 2, ('abc', 'a'), 4)

注意，若使用 ‘<’ 或 ‘>’ 來比較不同類型的物件是合法的，表示物件擁有適當的
比較方法。例如，混合的數值類型是根據它們數值來做比較，所以 0 等於 0.0，
等等。否則直譯器會選擇丟出一個 *note TypeError: 4dd. 錯誤而不是提供一個
任意的排序。

註解
....


File: python.info,  Node: 模組 Module,  Next: 輸入和輸出,  Prev: 資料結構,  Up: Python 教學

2.6 模組 (Module)
=================

如果從 Python 直譯器離開後又再次進入，之前（幫函式或變數）做的定義都會消
失。因此，想要寫一些比較長的程式時，你最好使用編輯器來準備要輸入給直譯器
的內容，並且用該檔案來運行它。這就是一個'腳本 (script)'。隨著你的程式越
變越長，你可能會想要把它分開成幾個檔案，讓它比較好維護。你可能也會想用一
個你之前已經在其他程式寫好的函式，但不想要複製該函式的原始定義到所有使用
它的程式裡。

為了支援這一點，Python 有一種方法可以將定義放入檔案中，並在互動模式下的
直譯器中使用它們。這種檔案稱為'模組 (module)'；模組中的定義可以被
'import' 到其他模組中，或是被 'import' 至'主 (main)' 模組（在最頂層執行
的腳本，以及互動模式下，所使用的變數集合）。

模組是指包含 Python 定義和語句的檔案，檔案名稱是模組名稱加上 ‘.py’。在模
組中，模組的名稱（作為字串）會是全域變數 ‘__name__’ 的值。例如，用你喜歡
的文字編輯器在資料夾中創一個名為 ‘fibo.py’ 的檔案，內容如下：

     # 費波那契數模組

     def fib(n):    # 寫出費波那契數列至第 n 位
         a, b = 0, 1
         while a < n:
             print(a, end=' ')
             a, b = b, a+b
         print()

     def fib2(n):   # 回傳費波那契數列至第 n 位
         result = []
         a, b = 0, 1
         while a < n:
             result.append(a)
             a, b = b, a+b
         return result

現在進入 Python 直譯器並用以下指令 import 這個模組：

     >>> import fibo

這並不會將 ‘fibo’ 中定義的函式名稱直接加入當前的 *note namespace: 1b5b.
中（詳情請見 *note Python 作用域 (Scope) 及命名空間 (Namespace): 1b5c.）
；它只會加入 ‘fibo’ 的模組名稱。使用此模組名稱，就可以存取函式：

     >>> fibo.fib(1000)
     0 1 1 2 3 5 8 13 21 34 55 89 144 233 377 610 987
     >>> fibo.fib2(100)
     [0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89]
     >>> fibo.__name__
     'fibo'

如果你打算經常使用其中某個函式，可以將其指定至區域變數：

     >>> fib = fibo.fib
     >>> fib(500)
     0 1 1 2 3 5 8 13 21 34 55 89 144 233 377

* Menu:

* 深入了解模組::
* 標準模組::
* dir() 函式: dir 函式.
* 套件 (Package): 套件 Package.


File: python.info,  Node: 深入了解模組,  Next: 標準模組,  Up: 模組 Module

2.6.1 深入了解模組
------------------

模組可以包含可執行的陳述式以及函式的定義。這些陳述式是作為模組的初始化，
它們只會在'第一次'被 import 時才會執行。(1)（如果檔案被當成腳本執行，也
會執行它們）。

每個模組都有它自己的私有命名空間 (namespace)，模組內定義的函式會把該模組
的私有符號表當成全域命名空間使用。因此，模組的作者可以在模組中使用全域變
數，而不必擔心和使用者的全域變數發生意外的名稱衝突。另一方面，如果你知道
自己在做什麼，你可以用這個方式取用模組的全域變數，以和引用函式一樣的寫法
，‘modname.itemname’。

在一個模組中可以 import 其他模組。把所有的 *note import: 586. 陳述式放在
模組（就這邊來說，腳本也是一樣）的最開頭是個慣例，但並沒有強制。如放置在
模組的最高層（不在任何函式或 class 中），被 import 的模組名稱將被加入全
域命名空間中。

*note import: 586. 陳述式有另一種變形寫法，可以直接將名稱從欲 import 的
模組，直接 import 至原模組的命名空間中。例如：

     >>> from fibo import fib, fib2
     >>> fib(500)
     0 1 1 2 3 5 8 13 21 34 55 89 144 233 377

在 import 之後的名稱會被導入，但定義該函式的整個模組名稱並不會被引入在區
域命名空間中（因此，示例中的 ‘fibo’ 未被定義）。

甚至還有另一種變形寫法，可以 import 模組定義的所有名稱：

     >>> from fibo import *
     >>> fib(500)
     0 1 1 2 3 5 8 13 21 34 55 89 144 233 377

這個寫法會 import 模組中所有的名稱，除了使用底線 (‘_’) 開頭的名稱。大多
數情況下，Python 程式設計師不大使用這個功能，因為它在直譯器中引入了一組
未知的名稱，並且可能覆蓋了某些你已經定義的內容。

請注意，一般情況下並不建議從模組或套件中 import ‘*’ 的做法，因為它通常會
導致可讀性較差的程式碼。但若是使用它來在互動模式中節省打字時間，則是可以
接受的。

如果模組名稱後面出現 ‘as’，則 ‘as’ 之後的名稱將直接和被 import 模組綁定
在一起。

     >>> import fibo as fib
     >>> fib.fib(500)
     0 1 1 2 3 5 8 13 21 34 55 89 144 233 377

這個 import 方式和 ‘import fibo’ 實質上是一樣的，唯一的差別是現在要用
‘fib’ 使用模組。

在使用 *note from: 1242. 時也可以用同樣的方式獲得類似的效果：

     >>> from fibo import fib as fibonacci
     >>> fibonacci(500)
     0 1 1 2 3 5 8 13 21 34 55 89 144 233 377

     備註: 出於效率原因，每個模組在每個直譯器 session 中僅會被 import 一
     次。因此，如果你更改了模組，則必須重啟直譯器——或者，如果只是一個想
     要在互動模式下測試的模組，可以使用 *note importlib.reload(): 4bd.。
     例如：‘import importlib; importlib.reload(modulename)’。

* Menu:

* 把模組當作腳本執行::
* 模組的搜尋路徑::
* 「編譯」Python 檔案::

   ---------- Footnotes ----------

   (1) 實際上，函式定義也是「被執行」的「陳述式」；在執行模組階層的函式
定義時，會將函式名稱加到模組的全域命名空間。


File: python.info,  Node: 把模組當作腳本執行,  Next: 模組的搜尋路徑,  Up: 深入了解模組

2.6.1.1 把模組當作腳本執行
..........................

當使用以下內容運行 Python 模組時：

     python fibo.py <arguments>

如同使用 import 指令，模組中的程式碼會被執行，但 ‘__name__’ 被設為
‘"__main__"’。這意味著，透過在模組的末尾添加以下程式碼：

     if __name__ == "__main__":
         import sys
         fib(int(sys.argv[1]))

你可以將檔案作為腳本也同時可以作為被 import 的模組，因為剖析 (parse) 命
令列的程式碼只會在當模組是「主」檔案時，才會執行：

     $ python fibo.py 50
     0 1 1 2 3 5 8 13 21 34

如果此模組是被 import 的，則該段程式碼不會被執行：

     >>> import fibo
     >>>

這通常是用來為模組提供方便的使用者介面，或者用於測試目的（執行測試套件時
，以腳本的方式執行模組）。


File: python.info,  Node: 模組的搜尋路徑,  Next: 「編譯」Python 檔案,  Prev: 把模組當作腳本執行,  Up: 深入了解模組

2.6.1.2 模組的搜尋路徑
......................

Import 一個名為 ‘spam’ 的模組時，直譯器首先會搜尋具有該名稱的內建模組。
模組名稱列在 *note sys.builtin_module_names: 1b63. 當中。如果找不到，接
下來會在變數 *note sys.path: 37f. 所給定的資料夾清單之中，搜尋一個名為
‘spam.py’ 的檔案。*note sys.path: 37f. 從這些位置開始進行初始化：

   * 輸入腳本所位在的資料夾（如未指定檔案時，則是當前資料夾）。

   * *note PYTHONPATH: fbe.（一連串和 shell 變數 ‘PATH’ 的語法相同的資料
     夾名稱）。

   * 與安裝相關的預設值（按慣例會包含一個 ‘site-packages’ 資料夾，它是由
     *note site: b5. 模組所處理）。

在 *note The initialization of the sys.path module search path: 1b64. 有
更多的細節。

     備註: 在支援符號連結 (symlink) 的檔案系統中，輸入腳本的所在資料夾是
     在跟隨符號連結之後才被計算的。換言之，包含符號連結的資料夾'並沒有
     '增加到模組的搜尋路徑中。

初始化之後，Python 程式可以修改 *note sys.path: 37f.。執行中腳本的所在資
料夾會在搜尋路徑的開頭，在標準函式庫路徑之前。這代表該資料夾中的腳本會優
先被載入，而不是函式庫資料夾中相同名稱的模組。除非是有意要做這樣的替換，
否則這是一個錯誤。 請參見*note 標準模組: 1b65.以瞭解更多資訊。


File: python.info,  Node: 「編譯」Python 檔案,  Prev: 模組的搜尋路徑,  Up: 深入了解模組

2.6.1.3 「編譯」Python 檔案
...........................

為了加快載入模組的速度，Python 將每個模組的編譯版本暫存在 ‘__pycache__’
資料夾下，並命名為 ‘module.`version'.pyc’， 這裡的 version 是編譯後的檔
案的格式名稱，且名稱通常會包含 Python 的版本編號。例如，在 CPython 3.3 中
，spam.py 的編譯版本將被暫存為 ‘__pycache__/spam.cpython-33.pyc’。此命名
準則可以讓來自不同版本的編譯模組和 Python 的不同版本同時共存。

Python 根據原始碼最後修改的日期，檢查編譯版本是否過期而需要重新編譯。這
是一個完全自動的過程。另外，編譯後的模組獨立於平台，因此不同架構的作業系
統之間可以共用同一函式庫。

Python 在兩種情況下不檢查快取 (cache)。首先，它總是重新編譯且不儲存直接
從命令列載入的模組的結果。第二，如果沒有源模組，則不會檢查快取。要支援非
源模組（僅編譯）的發布，編譯後的模組必須位於原始資料夾中，並且不能有源模
組。

一些給專家的秘訣：

   * 可以在 Python 指令上使用開關參數 (switch) *note -O: d5b. 或 *note
     -OO: d5c. 來減小已編譯模組的大小。開關參數 ‘-O’ 刪除 assert（斷言）
     陳述式，而 ‘-OO’ 同時刪除 assert 陳述式和 __doc__ 字串。由於有些程
     式可能依賴於上述這些內容，因此只有在你知道自己在做什麼時，才應使用
     此參數。「已優化」模組有 ‘opt-’ 標記，且通常較小。未來的版本可能會
     改變優化的效果。

   * 讀取 ‘.pyc’ 檔案時，程式的執行速度並不會比讀取 ‘.py’ 檔案快。唯一比
     較快的地方是載入的速度。

   * 模組 *note compileall: 19. 可以為資料夾中的所有模組建立 .pyc 檔。

   * 更多的細節，包括決策流程圖，請參考 PEP 3147(1)。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3147/


File: python.info,  Node: 標準模組,  Next: dir 函式,  Prev: 深入了解模組,  Up: 模組 Module

2.6.2 標準模組
--------------

Python 附帶了一個標準模組庫，詳細的介紹在另一份文件，稱為「Python 函式庫
參考手冊」（簡稱為「函式庫參考手冊」）。有些模組是直譯器中內建的；它們使
一些不屬於語言核心但依然內建的運算得以存取，其目的是為了提高效率，或提供
作業系統基本操作（例如系統呼叫）。這些模組的集合是一個組態選項，它們取決
於底層平台。例如：*note winreg: fe. 模組僅供 Windows 使用。值得注意的模
組是 *note sys: c3.，它被內建在每個 Python 直譯器中。變數 ‘sys.ps1’ 和
‘sys.ps2’ 則用來定義主、次提示字元的字串：

     >>> import sys
     >>> sys.ps1
     '>>> '
     >>> sys.ps2
     '... '
     >>> sys.ps1 = 'C> '
     C> print('Yuck!')
     Yuck!
     C>

只有直譯器在互動模式時，才需要定義這兩個變數。

變數 ‘sys.path’ 是一個字串 list，它決定直譯器的模組搜尋路徑。它的初始值
為環境變數 *note PYTHONPATH: fbe. 中提取的預設路徑，或是當 *note
PYTHONPATH: fbe. 未設定時，從內建預設值提取。你可以用標準的 list 操作修
改該變數：

     >>> import sys
     >>> sys.path.append('/ufs/guido/lib/python')


File: python.info,  Node: dir 函式,  Next: 套件 Package,  Prev: 標準模組,  Up: 模組 Module

2.6.3 ‘dir()’ 函式
------------------

內建函式 *note dir(): 5d8. 用於找出模組定義的所有名稱。它回傳一個排序後
的字串 list：

     >>> import fibo, sys
     >>> dir(fibo)
     ['__name__', 'fib', 'fib2']
     >>> dir(sys)
     ['__breakpointhook__', '__displayhook__', '__doc__', '__excepthook__',
      '__interactivehook__', '__loader__', '__name__', '__package__', '__spec__',
      '__stderr__', '__stdin__', '__stdout__', '__unraisablehook__',
      '_clear_type_cache', '_current_frames', '_debugmallocstats', '_framework',
      '_getframe', '_git', '_home', '_xoptions', 'abiflags', 'addaudithook',
      'api_version', 'argv', 'audit', 'base_exec_prefix', 'base_prefix',
      'breakpointhook', 'builtin_module_names', 'byteorder', 'call_tracing',
      'callstats', 'copyright', 'displayhook', 'dont_write_bytecode', 'exc_info',
      'excepthook', 'exec_prefix', 'executable', 'exit', 'flags', 'float_info',
      'float_repr_style', 'get_asyncgen_hooks', 'get_coroutine_origin_tracking_depth',
      'getallocatedblocks', 'getdefaultencoding', 'getdlopenflags',
      'getfilesystemencodeerrors', 'getfilesystemencoding', 'getprofile',
      'getrecursionlimit', 'getrefcount', 'getsizeof', 'getswitchinterval',
      'gettrace', 'hash_info', 'hexversion', 'implementation', 'int_info',
      'intern', 'is_finalizing', 'last_traceback', 'last_type', 'last_value',
      'maxsize', 'maxunicode', 'meta_path', 'modules', 'path', 'path_hooks',
      'path_importer_cache', 'platform', 'prefix', 'ps1', 'ps2', 'pycache_prefix',
      'set_asyncgen_hooks', 'set_coroutine_origin_tracking_depth', 'setdlopenflags',
      'setprofile', 'setrecursionlimit', 'setswitchinterval', 'settrace', 'stderr',
      'stdin', 'stdout', 'thread_info', 'unraisablehook', 'version', 'version_info',
      'warnoptions']

沒有給引數時，*note dir(): 5d8. 列出目前已定義的名稱：

     >>> a = [1, 2, 3, 4, 5]
     >>> import fibo
     >>> fib = fibo.fib
     >>> dir()
     ['__builtins__', '__name__', 'a', 'fib', 'fibo', 'sys']

請注意，它列出所有類型的名稱：變數、模組、函式等。

*note dir(): 5d8. 不會列出內建函式和變數的名稱。如果你想要列出它們，它們
被定義在標準模組 *note builtins: e. 內：

     >>> import builtins
     >>> dir(builtins)
     ['ArithmeticError', 'AssertionError', 'AttributeError', 'BaseException',
      'BlockingIOError', 'BrokenPipeError', 'BufferError', 'BytesWarning',
      'ChildProcessError', 'ConnectionAbortedError', 'ConnectionError',
      'ConnectionRefusedError', 'ConnectionResetError', 'DeprecationWarning',
      'EOFError', 'Ellipsis', 'EnvironmentError', 'Exception', 'False',
      'FileExistsError', 'FileNotFoundError', 'FloatingPointError',
      'FutureWarning', 'GeneratorExit', 'IOError', 'ImportError',
      'ImportWarning', 'IndentationError', 'IndexError', 'InterruptedError',
      'IsADirectoryError', 'KeyError', 'KeyboardInterrupt', 'LookupError',
      'MemoryError', 'NameError', 'None', 'NotADirectoryError', 'NotImplemented',
      'NotImplementedError', 'OSError', 'OverflowError',
      'PendingDeprecationWarning', 'PermissionError', 'ProcessLookupError',
      'ReferenceError', 'ResourceWarning', 'RuntimeError', 'RuntimeWarning',
      'StopIteration', 'SyntaxError', 'SyntaxWarning', 'SystemError',
      'SystemExit', 'TabError', 'TimeoutError', 'True', 'TypeError',
      'UnboundLocalError', 'UnicodeDecodeError', 'UnicodeEncodeError',
      'UnicodeError', 'UnicodeTranslateError', 'UnicodeWarning', 'UserWarning',
      'ValueError', 'Warning', 'ZeroDivisionError', '_', '__build_class__',
      '__debug__', '__doc__', '__import__', '__name__', '__package__', 'abs',
      'all', 'any', 'ascii', 'bin', 'bool', 'bytearray', 'bytes', 'callable',
      'chr', 'classmethod', 'compile', 'complex', 'copyright', 'credits',
      'delattr', 'dict', 'dir', 'divmod', 'enumerate', 'eval', 'exec', 'exit',
      'filter', 'float', 'format', 'frozenset', 'getattr', 'globals', 'hasattr',
      'hash', 'help', 'hex', 'id', 'input', 'int', 'isinstance', 'issubclass',
      'iter', 'len', 'license', 'list', 'locals', 'map', 'max', 'memoryview',
      'min', 'next', 'object', 'oct', 'open', 'ord', 'pow', 'print', 'property',
      'quit', 'range', 'repr', 'reversed', 'round', 'set', 'setattr', 'slice',
      'sorted', 'staticmethod', 'str', 'sum', 'super', 'tuple', 'type', 'vars',
      'zip']


File: python.info,  Node: 套件 Package,  Prev: dir 函式,  Up: 模組 Module

2.6.4 套件 (Package)
--------------------

套件是一種使用「點分隔模組名稱」組織 Python 模組命名空間的方法。例如，模
組名稱 ‘A.B’ 表示套件 ‘A’ 中名為 ‘B’ 的子模組。正如模組使用時，不同模組
的作者不需擔心與其他模組的全域變數名稱重複，點分隔模組名稱的使用，也讓多
模組套件（像 NumPy 或 Pillow）的作者們不須擔心其他套件的模組名稱。

假設你想設計一個能統一處理音訊檔案及音訊數據的模組集（「套件」）。因為音
訊檔案有很多的不同的格式（通常以它們的副檔名來辨識，例如：‘.wav’、
‘.aiff’、‘.au’），因此，為了不同檔案格式之間的轉換，你會需要建立和維護一
個不斷增長的模組集合。為了要達成對音訊數據的許多不同作業（例如，音訊混合
、增加回聲、套用等化器功能、創造人工立體音效），你將編寫一系列無止盡的模
組來執行這些作業。以下是你的套件可能的架構（以階層式檔案系統的方式表示）
：

     sound/                          Top-level package
           __init__.py               Initialize the sound package
           formats/                  Subpackage for file format conversions
                   __init__.py
                   wavread.py
                   wavwrite.py
                   aiffread.py
                   aiffwrite.py
                   auread.py
                   auwrite.py
                   ...
           effects/                  Subpackage for sound effects
                   __init__.py
                   echo.py
                   surround.py
                   reverse.py
                   ...
           filters/                  Subpackage for filters
                   __init__.py
                   equalizer.py
                   vocoder.py
                   karaoke.py
                   ...

Import 套件時，Python 會搜尋 ‘sys.path’ 裡的目錄，尋找套件的子目錄。

目錄中必須含有 ‘__init__.py’ 檔案，才會被 Pyhon 當成套件（除非有使用
*note namespace package: 1b6c.，為一個相對進階的功能）；這樣可以避免一些
以常用名稱命名（例如 ‘string’）的目錄，無意中隱藏了較晚出現在模組搜尋路
徑中的有效模組。在最簡單的情況，‘__init__.py’ 可以只是一個空白檔案；但它
也可以執行套件的初始化程式碼，或設置 ‘__all__’ 變數，之後會詳述。

套件使用者可以從套件中 import 個別模組，例如：

     import sound.effects.echo

這樣就載入了子模組 ‘sound.effects.echo’。引用時必須用它的全名：

     sound.effects.echo.echofilter(input, output, delay=0.7, atten=4)

另一種 import 子模組的方法是：

     from sound.effects import echo

這段程式碼一樣可以載入子模組 ‘echo’，並且不加套件前綴也可以使用，因此能
以如下方式使用：

     echo.echofilter(input, output, delay=0.7, atten=4)

另一種變化是直接 import 所需的函式或變數：

     from sound.effects.echo import echofilter

同樣地，這樣也會載入子模組 ‘echo’，但它的函式 ‘echofilter()’ 就可以直接
使用：

     echofilter(input, output, delay=0.7, atten=4)

請注意，使用 ‘from package import item’ 時，item 可以是套件的子模組（或
子套件），也可以是套件中被定義的名稱，像是函式、class （類別）或變數。
‘import’ 陳述式首先測試套件中有沒有定義該 item；如果沒有，則會假設它是模
組，並嘗試載入。如果還是找不到 item，則會引發 *note ImportError: 352. 例
外。

相反地，使用 ‘import item.subitem.subsubitem’ 語法時，除了最後一項之外，
每一項都必須是套件；最後一項可以是模組或套件，但不能是前一項中定義的
class、函式或變數。

* Menu:

* 從套件中 import *::
* 套件內引用::
* 多目錄中的套件::


File: python.info,  Node: 從套件中 import *,  Next: 套件內引用,  Up: 套件 Package

2.6.4.1 從套件中 import *
.........................

當使用者寫下 ‘from sound.effects import *’ 時，會發生什麼事？理想情況下
，我們可能希望程式碼會去檔案系統，尋找套件中存在的子模組，並將它們全部
import。這會花費較長的時間，且 import 子模組的過程可能會有不必要的副作用
，這些副作用只有在明確地 import 子模組時才會發生。

唯一的解法是由套件作者為套件提供明確的索引。*note import: 586. 陳述式使
用以下慣例：如果套件的 ‘__init__.py’ 程式碼有定義一個名為 ‘__all__’ 的
list，若遇到 ‘from package import *’ 的時候，它就會是要被 import 的模組
名稱。發布套件的新版本時，套件作者可自行決定是否更新此 list。如果套件作
者認為沒有人會從他的套件中 import *，他也可能會決定不支援這個 list。舉例
來說，‘sound/effects/__init__.py’ 檔案可包含以下程式碼：

     __all__ = ["echo", "surround", "reverse"]

意思是，‘from sound.effects import *’ 將會 import ‘sound.effects’ 套件中
，這三個被提名的子模組。

請注意，子模組可能會被區域定義 (locally defined) 的名稱遮蔽。例如，如果
你在 ‘sound/effects/__init__.py’ 檔案中新增了一個 ‘reverse’ 函式，則
‘from sound.effects import *’ 只會引入兩個子模組 ‘echo’ 和 ‘surround’，
但'不是' ‘reverse’ 子模組，因為它被區域定義的 ‘reverse’ 函式遮蔽了：

     __all__ = [
         "echo",      # refers to the 'echo.py' file
         "surround",  # refers to the 'surround.py' file
         "reverse",   # !!! refers to the 'reverse' function now !!!
     ]

     def reverse(msg: str):  # <-- this name shadows the 'reverse.py' submodule
         return msg[::-1]    #     in the case of a 'from sound.effects import *'

如果 ‘__all__’ 沒有被定義，‘from sound.effects import *’ 陳述式'並不會
'把 ‘sound.effects’ 套件中所有子模組都 import 到當前的命名空間；它只保證
‘sound.effects’ 套件有被 import（可能會運行 ‘__init__.py’ 中的初始化程式
碼），然後 import 套件中被定義的全部名稱。這包含 ‘__init__.py’ 定義（以
及被明確載入的子模組）的任何名稱。它也包括任何之前被 *note import: 586.
陳述式明確載入的套件子模組。請看以下程式碼：

     import sound.effects.echo
     import sound.effects.surround
     from sound.effects import *

此例中，當 ‘from...import’ 陳述式被執行時，‘echo’ 和 ‘surround’ 模組被
import 進當前的命名空間，因為它們是在 ‘sound.effects’ 套件裡定義的。（當
‘__all__’ 有被定義時，這規則也有效。）

雖然，有些特定模組的設計，讓你使用 ‘import *’ 時，該模組只會輸出遵循特定
樣式的名稱，但在正式環境 (production) 的程式碼中這仍然被視為是不良習慣。

記住，使用 ‘from package import specific_submodule’ 不會有任何問題！實際
上，這是推薦用法，除非 import 的模組需要用到的子模組和其他套件的子模組同
名。


File: python.info,  Node: 套件內引用,  Next: 多目錄中的套件,  Prev: 從套件中 import *,  Up: 套件 Package

2.6.4.2 套件內引用
..................

當套件的結構為多個子套件的組合時（如同範例中的 ‘sound’ 套件），可以使用
「絕對 (absolute) import」，引用同層套件中的子模組。例如，要在
‘sound.filters.vocoder’ 模組中使用 ‘sound.effects’ 中的 ‘echo’ 模組時，
可以用 ‘from sound.effects import echo’。

你也可以用 ‘from module import name’ 的 import 陳述式，編寫「相對
(relative) import」。這些 import 使用前導句號指示相對 import 中的當前套
件和母套件。例如，在 ‘urround’ 模組中，你可以使用：

     from . import echo
     from .. import formats
     from ..filters import equalizer

請注意，相對 import 的運作是以目前的模組名稱為依據。因為主模組的名稱永遠
是 ‘"__main__"’，所以如果一個模組預期被用作 Python 應用程式的主模組，那
它必須永遠使用絕對 import。


File: python.info,  Node: 多目錄中的套件,  Prev: 套件內引用,  Up: 套件 Package

2.6.4.3 多目錄中的套件
......................

套件也支援一個特殊屬性 *note __path__: 1b72.。它在初始化時是一個 list，
包含該套件的 ‘__init__.py’ 檔案所在的目錄名稱，初始化時機是在這個檔案的
程式碼被執行之前。這個變數可以被修改，但這樣做會影響將來對套件內的模組和
子套件的搜尋。

雖然這個特色不太常被需要，但它可用於擴充套件中的模組集合。

註解
....


File: python.info,  Node: 輸入和輸出,  Next: 錯誤和例外,  Prev: 模組 Module,  Up: Python 教學

2.7 輸入和輸出
==============

有數種方式可以顯示程式的輸出；資料可以以人類易讀的形式印出，或是寫入檔案
以供未來所使用。這章節會討論幾種不同的方式。

* Menu:

* 更華麗的輸出格式::
* 讀寫檔案::


File: python.info,  Node: 更華麗的輸出格式,  Next: 讀寫檔案,  Up: 輸入和輸出

2.7.1 更華麗的輸出格式
----------------------

目前為止我們已經學過兩種寫值的方式：'運算式陳述 (expression statements)'
與 *note print(): f18. 函式。（第三種方法是使用檔案物件的 *note write():
1b78. 方法；標準輸出的檔案是使用 ‘sys.stdout’ 來達成的。詳細的資訊請參考
對應的函式庫說明。）

通常你會想要對輸出格式有更多地控制，而不是僅列印出以空格隔開的值。以下是
幾種格式化輸出的方式。

   * 要使用*note 格式化字串文本 (formatted string literals): 1b79.，需在
     字串開始前的引號或連續三個引號前加上 ‘f’ 或 ‘F’。你可以在這個字串中
     使用 ‘{’ 與 ‘}’ 包夾 Python 的運算式，引用變數或其他字面值 (literal
     values)。

          >>> year = 2016
          >>> event = 'Referendum'
          >>> f'Results of the {year} {event}'
          'Results of the 2016 Referendum'

   * 字串的 *note str.format(): 5c7. method 需要更多手動操作。你還是可以
     用 ‘{’ 和 ‘}’ 標示欲替代變數的位置，且可給予詳細的格式指令，但你也
     需提供要被格式化的資訊。在以下程式碼區塊中，有兩個如何格式化變數的
     範例：

          >>> yes_votes = 42_572_654
          >>> total_votes = 85_705_149
          >>> percentage = yes_votes / total_votes
          >>> '{:-9} YES votes  {:2.2%}'.format(yes_votes, percentage)
          ' 42572654 YES votes  49.67%'

     請注意 ‘yes_votes’ 如何對於負數用空格和負號填補。該範例還會列出
     ‘percentage’ 乘以 100，並保留 2 位小數且後面跟著一個百分號（有關詳
     細資訊，請參閱 *note 格式規格 (Format Specification) 迷你語言:
     1c8.）。

   * 最後，你還可以自己用字串切片 (slicing) 和串接 (concatenation) 操作
     ，完成所有的字串處理，建立任何你能想像的排版格式。字串型別有一些
     method，能以給定的欄寬填補字串，這些運算也很有用。

如果你不需要華麗的輸出，只想快速顯示變數以進行除錯，可以用 *note repr():
7a1. 或 *note str(): 3f2. 函式把任何的值轉換為字串。

*note str(): 3f2. 函式的用意是回傳一個人類易讀的表示法，而 *note repr():
7a1. 的用意是產生直譯器可讀取的表示法（如果沒有等效的語法，則造成 *note
SyntaxError: 173.）。如果物件沒有人類易讀的特定表示法，*note str(): 3f2.
會回傳與 *note repr(): 7a1. 相同的值。有許多的值，像是數字，或 list 及
dictionary 等結構，使用這兩個函式會有相同的表示法。而字串，則較為特別，
有兩種不同的表示法。

一些範例：

     >>> s = 'Hello, world.'
     >>> str(s)
     'Hello, world.'
     >>> repr(s)
     "'Hello, world.'"
     >>> str(1/7)
     '0.14285714285714285'
     >>> x = 10 * 3.25
     >>> y = 200 * 200
     >>> s = 'The value of x is ' + repr(x) + ', and y is ' + repr(y) + '...'
     >>> print(s)
     The value of x is 32.5, and y is 40000...
     >>> # The repr() of a string adds string quotes and backslashes:
     >>> hello = 'hello, world\n'
     >>> hellos = repr(hello)
     >>> print(hellos)
     'hello, world\n'
     >>> # The argument to repr() may be any Python object:
     >>> repr((x, y, ('spam', 'eggs')))
     "(32.5, 40000, ('spam', 'eggs'))"

*note string: be. 模組包含一個 *note Template: 62d. class（類別），提供
了將值替代為字串的另一種方法。該方法使用 ‘$x’ 佔位符號，並以 dictionary
的值進行取代，但對格式的控制明顯較少。

* Menu:

* 格式化的字串文本 (Formatted String Literals): 格式化的字串文本 Formatted String Literals.
* 字串的 format() method: 字串的 format method.
* 手動格式化字串::
* 格式化字串的舊方法::


File: python.info,  Node: 格式化的字串文本 Formatted String Literals,  Next: 字串的 format method,  Up: 更華麗的輸出格式

2.7.1.1 格式化的字串文本 (Formatted String Literals)
....................................................

*note 格式化的字串文本: 94d.（簡稱為 f-字串），透過在字串加入前綴 ‘f’ 或
‘F’，並將運算式編寫為 ‘{expression}’，讓你可以在字串內加入 Python 運算式
的值。

格式說明符 (format specifier) 是選擇性的，寫在運算式後面，可以更好地控制
值的格式化方式。以下範例將 pi 捨入到小數點後三位：

     >>> import math
     >>> print(f'The value of pi is approximately {math.pi:.3f}.')
     The value of pi is approximately 3.142.

在 ‘':'’ 後傳遞一個整數，可以設定該欄位至少為幾個字元寬，常用於將每一欄
對齊。

     >>> table = {'Sjoerd': 4127, 'Jack': 4098, 'Dcab': 7678}
     >>> for name, phone in table.items():
     ...     print(f'{name:10} ==> {phone:10d}')
     ...
     Sjoerd     ==>       4127
     Jack       ==>       4098
     Dcab       ==>       7678

還有一些修飾符號可以在格式化前先將值轉換過。‘'!a'’ 會套用 *note ascii():
1354.，‘'!s'’ 會套用 *note str(): 3f2.，‘'!r'’ 會套用 *note repr():
7a1.：

     >>> animals = 'eels'
     >>> print(f'My hovercraft is full of {animals}.')
     My hovercraft is full of eels.
     >>> print(f'My hovercraft is full of {animals!r}.')
     My hovercraft is full of 'eels'.

‘=’ 說明符可用於將一個運算式擴充為該運算式的文字、一個等號、以及對該運算
式求值 (evaluate) 後的表示法：

     >>> bugs = 'roaches'
     >>> count = 13
     >>> area = 'living room'
     >>> print(f'Debugging {bugs=} {count=} {area=}')
     Debugging bugs='roaches' count=13 area='living room'

更多關於 ‘=’ 說明符的資訊請見*note 自文件性運算式 (self-documenting
expressions): 94b.。若要參考這些格式化字串的規格，詳見 *note 格式規格
(Format Specification) 迷你語言: 1c8. 參考指南。


File: python.info,  Node: 字串的 format method,  Next: 手動格式化字串,  Prev: 格式化的字串文本 Formatted String Literals,  Up: 更華麗的輸出格式

2.7.1.2 字串的 format() method
..............................

*note str.format(): 5c7. method 的基本用法如下：

     >>> print('We are the {} who say "{}!"'.format('knights', 'Ni'))
     We are the knights who say "Ni!"

大括號及其內的字元（稱為格式欄位）會被取代為傳遞給 *note str.format():
5c7. method 的物件。大括號中的數字表示該物件在傳遞給 *note str.format():
5c7. method 時所在的位置。

     >>> print('{0} and {1}'.format('spam', 'eggs'))
     spam and eggs
     >>> print('{1} and {0}'.format('spam', 'eggs'))
     eggs and spam

如果在 *note str.format(): 5c7. method 中使用關鍵字引數，可以使用引數名
稱去引用它們的值。

     >>> print('This {food} is {adjective}.'.format(
     ...       food='spam', adjective='absolutely horrible'))
     This spam is absolutely horrible.

位置引數和關鍵字引數可以任意組合：

     >>> print('The story of {0}, {1}, and {other}.'.format('Bill', 'Manfred',
     ...                                                    other='Georg'))
     The story of Bill, Manfred, and Georg.

如果你有一個不想分割的長格式化字串，比較好的方式是按名稱而不是按位置來引
用變數。這項操作可以透過傳遞字典 (dict)，並用方括號 ‘'[]'’ 使用鍵 (key)
來輕鬆完成。

     >>> table = {'Sjoerd': 4127, 'Jack': 4098, 'Dcab': 8637678}
     >>> print('Jack: {0[Jack]:d}; Sjoerd: {0[Sjoerd]:d}; '
     ...       'Dcab: {0[Dcab]:d}'.format(table))
     Jack: 4098; Sjoerd: 4127; Dcab: 8637678

用 '**' 符號，把 ‘table’ 字典當作關鍵字引數來傳遞，也有一樣的結果。

     >>> table = {'Sjoerd': 4127, 'Jack': 4098, 'Dcab': 8637678}
     >>> print('Jack: {Jack:d}; Sjoerd: {Sjoerd:d}; Dcab: {Dcab:d}'.format(**table))
     Jack: 4098; Sjoerd: 4127; Dcab: 8637678

與內建函式 *note vars(): 1948. 組合使用時，這種方式特別實用。該函式可以
回傳一個包含所有區域變數的 dictionary：

     >>> table = {k: str(v) for k, v in vars().items()}
     >>> message = " ".join([f'{k}: ' + '{' + k +'};' for k in table.keys()])
     >>> print(message.format(**table))
     __name__: __main__; __doc__: None; __package__: None; __loader__: ...

例如，下面的程式碼產生一組排列整齊的欄，列出整數及其平方與立方：

     >>> for x in range(1, 11):
     ...     print('{0:2d} {1:3d} {2:4d}'.format(x, x*x, x*x*x))
     ...
      1   1    1
      2   4    8
      3   9   27
      4  16   64
      5  25  125
      6  36  216
      7  49  343
      8  64  512
      9  81  729
     10 100 1000

關於使用 *note str.format(): 5c7. 進行字串格式化的完整概述，請見*note
格式化文字語法: 131e.。


File: python.info,  Node: 手動格式化字串,  Next: 格式化字串的舊方法,  Prev: 字串的 format method,  Up: 更華麗的輸出格式

2.7.1.3 手動格式化字串
......................

下面是以手動格式化完成的同一個平方及立方的表：

     >>> for x in range(1, 11):
     ...     print(repr(x).rjust(2), repr(x*x).rjust(3), end=' ')
     ...     # 注意前一列使用的 'end'
     ...     print(repr(x*x*x).rjust(4))
     ...
      1   1    1
      2   4    8
      3   9   27
      4  16   64
      5  25  125
      6  36  216
      7  49  343
      8  64  512
      9  81  729
     10 100 1000

（請注意，使用 *note print(): f18. 讓每欄之間加入一個空格的方法：這種方
法總是在其引數間加入空格。）

字串物件的 *note str.rjust(): 1b7e. method 透過在左側填補空格，使字串以
給定的欄寬進行靠右對齊。類似的 method 還有 *note str.ljust(): 1b7f. 和
*note str.center(): 1b80.。這些 method 不寫入任何內容，只回傳一個新字串
，如果輸入的字串太長，它們不會截斷字串，而是不做任何改變地回傳；雖然這樣
會弄亂欄的編排，但這通常還是比另一種情況好，那種情況會讓值變得不正確。（
如果你真的想截斷字串，可以加入像 ‘x.ljust(n)[:n]’ 這樣的切片運算。）

另一種 method 是 *note str.zfill(): 141d.，可在數值字串的左邊填補零，且
能識別正負號：

     >>> '12'.zfill(5)
     '00012'
     >>> '-3.14'.zfill(7)
     '-003.14'
     >>> '3.14159265359'.zfill(5)
     '3.14159265359'


File: python.info,  Node: 格式化字串的舊方法,  Prev: 手動格式化字串,  Up: 更華麗的輸出格式

2.7.1.4 格式化字串的舊方法
..........................

% 運算子（modulo，模數）也可用於字串格式化。在 ‘format % values’ 中（其
中 'format' 是個字串），'format' 內的 ‘%’ 轉換規格會被 'values' 的零個或
多個元素所取代。此運算常被稱為字串插值 (string interpolation)。例如：

     >>> import math
     >>> print('The value of pi is approximately %5.3f.' % math.pi)
     The value of pi is approximately 3.142.

更多資訊請見 *note printf-style String Formatting: 671.小節。


File: python.info,  Node: 讀寫檔案,  Prev: 更華麗的輸出格式,  Up: 輸入和輸出

2.7.2 讀寫檔案
--------------

*note open(): 4c0. 回傳一個 *note file object: 115b.，而它最常使用的兩個
位置引數和一個關鍵字引數是：‘open(filename, mode, encoding=None)’

     >>> f = open('workfile', 'w', encoding="utf-8")

第一個引數是一個包含檔案名稱的字串。第二個引數是另一個字串，包含了描述檔
案使用方式的幾個字元。'mode' 為 ‘'r'’ 時，表示以唯讀模式開啟檔案；為
‘'w'’ 時，表示以唯寫模式開啟檔案（已存在的同名檔案會被抹除）；為 ‘'a'’ 時
，以附加內容為目的開啟檔案，任何寫入檔案的資料會自動被加入到檔案的結尾。
‘'r+'’ 可以開啟檔案並進行讀取和寫入。'mode' 引數是選擇性的，若省略時會預
設為 ‘'r'’。

通常，檔案以 'text mode' 開啟，意即，從檔案中讀取或寫入字串時，都以特定
編碼方式 'encoding' 進行編碼。如未指定 'encoding'，則預設值會取決於系統
平台（見 *note open(): 4c0.）。因為 UTF-8 是現時的標準，除非你很清楚該用
什麼編碼，否則推薦使用 ‘encoding="utf-8"’。在 mode 後面加上 ‘'b'’ 會以
'binary mode'（二進制模式）開啟檔案，二進制模式資料以 *note bytes: 1a5.
物件的形式被讀寫。以二進制模式開啟檔案時不可以指定 'encoding'。

在文字模式 (text mode) 下，讀取時會預設把平台特定的行尾符號（Unix 上為
‘\n’，Windows 上為 ‘\r\n’）轉換為 ‘\n’。在文字模式下寫入時，預設會把
‘\n’ 出現之處轉換回平台特定的行尾符號。這種在幕後對檔案資料的修改方式對
文字檔案來說沒有問題，但會毀壞像是 ‘JPEG’ 或 ‘EXE’ 檔案中的二進制資料。
在讀寫此類檔案時，注意一定要使用二進制模式。

在處理檔案物件時，使用 *note with: 577. 關鍵字是個好習慣。優點是，當它的
套件結束後，即使在某個時刻引發了例外，檔案仍會正確地被關閉。使用 ‘with’
也比寫等效的 *note try: 68c.-*note finally: 96e. 區塊，來得簡短許多：

     >>> with open('workfile', encoding="utf-8") as f:
     ...     read_data = f.read()

     >>> # 我們可以檢查確認該檔案已經自動被關閉。
     >>> f.closed
     True

如果你沒有使用 *note with: 577. 關鍵字，則應呼叫 ‘f.close()’ 關閉檔案，
可以立即釋放被它所使用的系統資源。

     警告: 呼叫 ‘f.write()’ 時，若未使用 ‘with’ 關鍵字或呼叫
     ‘f.close()’，即使程式成功退出，也'可能'導致 ‘f.write()’ 的引數沒有
     被完全寫入硬碟。

不論是透過 *note with: 577. 陳述式，或呼叫 ‘f.close()’ 關閉一個檔案物件
之後，嘗試使用該檔案物件將會自動失效。

     >>> f.close()
     >>> f.read()
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     ValueError: I/O operation on closed file.

* Menu:

* 檔案物件的 method::
* 使用 json 儲存結構化資料::


File: python.info,  Node: 檔案物件的 method,  Next: 使用 json 儲存結構化資料,  Up: 讀寫檔案

2.7.2.1 檔案物件的 method
.........................

本節其餘的範例皆假設一個名為 ‘f’ 的檔案物件已被建立。

要讀取檔案的內容，可呼叫 ‘f.read(size)’，它可讀取一部份的資料，並以字串
（文字模式）或位元組串物件（二進制模式）形式回傳。'size' 是個選擇性的數
字引數。當 'size' 被省略或為負數時，檔案的全部內容會被讀取並回傳；如果檔
案是機器記憶體容量的兩倍大時，這會是你的問題。否則，最多只有等同於
'size' 數量的字元（文字模式）或 'size' 數量的位元組串（二進制模式）會被
讀取及回傳。如果之前已經到達檔案的末端，‘f.read()’ 會回傳空字串（‘''’）
。

     >>> f.read()
     'This is the entire file.\n'
     >>> f.read()
     ''

‘f.readline()’ 從檔案中讀取單獨一行；換行字元（‘\n’）會被留在字串的結尾
，只有當檔案末端不是換行字元時，它才會在檔案的最後一行被省略。這種方式讓
回傳值清晰明確；只要 ‘f.readline()’ 回傳一個空字串，就表示已經到達了檔案
末端，而空白行的表示法是 ‘'\n'’，也就是只含一個換行字元的字串。

     >>> f.readline()
     'This is the first line of the file.\n'
     >>> f.readline()
     'Second line of the file\n'
     >>> f.readline()
     ''

想從檔案中讀取多行時，可以對檔案物件進行迴圈。這種方法能有效地使用記憶體
、快速，且程式碼簡潔：

     >>> for line in f:
     ...     print(line, end='')
     ...
     This is the first line of the file.
     Second line of the file

如果你想把一個檔案的所有行讀進一個 list 裡，可以用 ‘list(f)’ 或
‘f.readlines()’。

‘f.write(string)’ 把 'string' 的內容寫入檔案，並回傳寫入的字元數。

     >>> f.write('This is a test\n')
     15

寫入其他類型的物件之前，要先把它們轉換為字串（文字模式）或位元組串物件（
二進制模式）：

     >>> value = ('the answer', 42)
     >>> s = str(value)  # 將元組轉換成字串
     >>> f.write(s)
     18

‘f.tell()’ 回傳一個整數，它給出檔案物件在檔案中的當前位置，在二進制模式
下表示為檔案開始至今的位元組數，在文字模式下表示為一個意義不明的數字。

使用 ‘f.seek(offset, whence)’ 可以改變檔案物件的位置。位置計算方法是從一
個參考點增加 'offset' 的偏移量；參考點則由引數 'whence' 來選擇。當
'whence' 值為 0 時，表示使用檔案開頭，1 表示使用當前的檔案位置，2 表示使
用檔案末端作為參考點。'whence' 可省略，其預設值為 0，即以檔案開頭作為參
考點。

     >>> f = open('workfile', 'rb+')
     >>> f.write(b'0123456789abcdef')
     16
     >>> f.seek(5)      # 跳到檔案中的第六個位元組
     5
     >>> f.read(1)
     b'5'
     >>> f.seek(-3, 2)  # 跳到結尾前的第三個位元組
     13
     >>> f.read(1)
     b'd'

在文字檔案（開啟時模式字串未加入 ‘b’ 的檔案）中，只允許以檔案開頭為參考
點進行尋找（但 ‘seek(0, 2)’ 尋找檔案最末端是例外），且只有從 ‘f.tell()’
回傳的值，或是 0，才是有效的 'offset' 值。其他任何 'offset' 值都會產生未
定義的行為。

檔案物件還有一些附加的 method，像是較不常使用的 *note isatty(): 1b86. 和
*note truncate(): 12a5.；檔案物件的完整指南詳見程式庫參考手冊。


File: python.info,  Node: 使用 json 儲存結構化資料,  Prev: 檔案物件的 method,  Up: 讀寫檔案

2.7.2.2 使用 ‘json’ 儲存結構化資料
..................................

字串可以簡單地從檔案中被寫入和讀取。數字則稍嫌麻煩，因為 *note read():
1b89. method 只回傳字串，這些字串必須傳遞給像 *note int(): 23c. 這樣的函
式，它接受 ‘'123'’ 這樣的字串，並回傳數值 123。當你想儲存像是巢狀 list 和
dictionary（字典）等複雜的資料類型時，手動剖析 (parsing) 和序列化
(serializing) 就變得複雜。

相較於讓使用者不斷地編寫和除錯程式碼才能把複雜的資料類型儲存到檔案，
Python 支援一個普及的資料交換格式，稱為 JSON (JavaScript Object
Notation)(1)。標準模組 *note json: 76. 可接收 Python 資料階層，並將它們
轉換為字串表示法；這個過程稱為 'serializing'（序列化）。從字串表示法中重
建資料則稱為 'deserializing'（反序列化）。在序列化和反序列化之間，表示物
件的字串可以被儲存在檔案或資料中，或通過網路連接發送到遠端的機器。

     備註: JSON 格式經常地使用於現代應用程式的資料交換。許多程序設計師早
     已對它耳熟能詳，使它成為提升互操作性 (interoperability) 的好選擇。

如果你有一個物件 ‘x’，只需一行簡單的程式碼即可檢視它的 JSON 字串表示法：

     >>> import json
     >>> x = [1, 'simple', 'list']
     >>> json.dumps(x)
     '[1, "simple", "list"]'

*note dumps(): cec. 函式有一個變體，稱為 *note dump(): ceb.，它單純地將
物件序列化為 *note text file: 1b8a.。因此，如果 ‘f’ 是一個為了寫入而開啟
的 *note text file: 1b8a. 物件，我們可以這樣做：

     json.dump(x, f)

若 ‘f’ 是一個已開啟、可讀取的 *note binary file: 1b8b. 或 *note text
file: 1b8a. 物件，要再次解碼物件的話：

     x = json.load(f)

     備註: JSON 檔案必須以 UTF-8 格式編碼。在開啟 JSON 檔案以作為一個可
     讀取與寫入的 *note text file: 1b8a. 時，要用 ‘encoding="utf-8"’。

這種簡單的序列化技術可以處理 list 和 dictionary，但要在 JSON 中序列化任
意的 class（類別）實例，則需要一些額外的工作。*note json: 76. 模組的參考
資料包含對此的說明。

也參考
......

*note pickle: 95. - pickle 模組

與 *note JSON: 1b88. 不同，'pickle' 是一種允許對任意的複雜 Python 物件進
行序列化的協定。因此，它為 Python 所特有，不能用於與其他語言編寫的應用程
式溝通。在預設情況，它也是不安全的：如果資料是由手段高明的攻擊者精心設計
，將這段來自於不受信任來源的 pickle 資料反序列化，可以執行任意的程式碼。

   ---------- Footnotes ----------

   (1) https://json.org


File: python.info,  Node: 錯誤和例外,  Next: Class（類別）,  Prev: 輸入和輸出,  Up: Python 教學

2.8 錯誤和例外
==============

到目前為止還沒有提到錯誤訊息，但如果你嘗試運行範例，你可能會發現一些錯誤
訊息。常見的（至少）兩種不同的錯誤類別為：'語法錯誤 (syntax error)' 和
'例外 (exception)'。

* Menu:

* 語法錯誤 (Syntax Error): 語法錯誤 Syntax Error.
* 例外 (Exception): 例外 Exception.
* 處理例外::
* 引發例外::
* 例外鏈接 (Exception Chaining): 例外鏈接 Exception Chaining.
* 使用者自定的例外::
* 定義清理動作::
* 預定義的清理動作::
* 引發及處理多個無關的例外::
* 用註解使例外更詳細::


File: python.info,  Node: 語法錯誤 Syntax Error,  Next: 例外 Exception,  Up: 錯誤和例外

2.8.1 語法錯誤 (Syntax Error)
-----------------------------

語法錯誤又稱剖析錯誤 (parsing error)，它或許是學習 Python 的過程最常聽見
的抱怨：

     >>> while True print('Hello world')
       File "<stdin>", line 1
         while True print('Hello world')
                    ^^^^^
     SyntaxError: invalid syntax

The parser repeats the offending line and displays little 'arrow's
pointing at the token in the line where the error was detected.  The
error may be caused by the absence of a token 'before' the indicated
token.  In the example, the error is detected at the function *note
print(): f18, since a colon (‘':'’) is missing before it.  File name and
line number are printed so you know where to look in case the input came
from a script.


File: python.info,  Node: 例外 Exception,  Next: 處理例外,  Prev: 語法錯誤 Syntax Error,  Up: 錯誤和例外

2.8.2 例外 (Exception)
----------------------

即使一段陳述式或運算式使用了正確的語法，嘗試執行時仍可能導致錯誤。執行時
檢測到的錯誤稱為'例外'，例外不一定都很嚴重：你很快就能學會在 Python 程式
中如何處理它們。不過大多數的例外不會被程式處理，並且會顯示如下的錯誤訊息
：

     >>> 10 * (1/0)
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     ZeroDivisionError: division by zero
     >>> 4 + spam*3
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     NameError: name 'spam' is not defined
     >>> '2' + 2
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: can only concatenate str (not "int") to str

錯誤訊息的最後一行指示發生了什麼事。例外有不同的類型，而類型名稱會作為訊
息的一部份被印出。範例中的例外類型為：*note ZeroDivisionError: 8e9.、
*note NameError: 3e5. 和 *note TypeError: 4dd.。作為例外類型被印出的字串
，就是發生的內建例外 (built-in exception) 的名稱。所有的內建例外都是如此
運作，但對於使用者自定的例外則不一定需要遵守（雖然這是一個有用的慣例）。
標準例外名稱是內建的識別字 (identifier)，不是保留關鍵字 (reserved
keyword)。

此行其餘部分，根據例外的類型及導致例外的原因，說明例外的細節。

錯誤訊息的開頭，用堆疊回溯 (stack traceback) 的形式顯示發生例外的語境。
一般來說，它含有一個列出源程式碼行 (source line) 的堆疊回溯；但它不會顯
示從標準輸入中讀取的程式碼。

*note 內建的例外: 1786.章節列出內建的例外及它們的意義。


File: python.info,  Node: 處理例外,  Next: 引發例外,  Prev: 例外 Exception,  Up: 錯誤和例外

2.8.3 處理例外
--------------

編寫程式處理選定的例外是可行的。以下範例會要求使用者輸入內容，直到有效的
整數被輸入為止，但它允許使用者中斷程式（使用 ‘Control-C’ 或作業系統支援
的指令）；請注意，由使用者產生的程式中斷會引發 *note KeyboardInterrupt:
975. 例外信號。

     >>> while True:
     ...     try:
     ...         x = int(input("Please enter a number: "))
     ...         break
     ...     except ValueError:
     ...         print("Oops!  That was no valid number.  Try again...")
     ...

*note try: 68c. 陳述式運作方式如下。

   * 首先，執行 'try 子句'（*note try: 68c. 和 *note except: 171. 關鍵字
     之間的陳述式）。

   * 如果沒有發生例外，則 'except 子句'會被跳過，*note try: 68c. 陳述式
     執行完畢。

   * 如果執行 *note try: 68c. 子句時發生了例外，則該子句中剩下的部分會被
     跳過。如果例外的類型與 *note except: 171. 關鍵字後面的例外名稱相符
     ，則 'except 子句'被執行，然後，繼續執行 try/except 區塊之後的程式
     碼。

   * 如果發生的例外未符合 'except 子句' 中的例外名稱，則將其傳遞到外層的
     *note try: 68c. 陳述式；如果仍無法找到處理者，則它是一個'未處理例外
     (unhandled exception)'，執行將停止，並顯示錯誤訊息。

*note try: 68c. 陳述式可以有不只一個 'except 子句'，為不同的例外指定處理
者，而最多只有一個處理者會被執行。處理者只處理對應的 try 子句中發生的例
外，而不會處理同一 ‘try’ 陳述式裡其他處理者內的例外。一個 'except 子句
'可以用一組括號內的 tuple 列舉多個例外，例如：

     ... except (RuntimeError, TypeError, NameError):
     ...     pass

A class in an *note except: 171. clause matches exceptions which are
instances of the class itself or one of its derived classes (but not the
other way around -- an 'except clause' listing a derived class does not
match instances of its base classes).  For example, the following code
will print B, C, D in that order:

     class B(Exception):
         pass

     class C(B):
         pass

     class D(C):
         pass

     for cls in [B, C, D]:
         try:
             raise cls()
         except D:
             print("D")
         except C:
             print("C")
         except B:
             print("B")

請注意，如果 'except 子句'的順序被反轉（把 ‘except B’ 放到第一個），則會
印出 B、B、B ­­——第一個符合的 'except 子句'會被觸發。

當例外發生時，它可能有相關聯的值，也就是例外的'引數'。引數的存在與否及它
的類型，是取決於例外的類型。

'except 子句'可以在例外名稱後面指定一個變數。這個變數被綁定到一個例外實
例 (instance)，其引數通常儲存在 ‘args’ 屬性中。為了方便，內建例外型別定
義了 *note __str__(): 5c4. 以印出所有引數而不需顯式地取用 ‘.args’：

     >>> try:
     ...     raise Exception('spam', 'eggs')
     ... except Exception as inst:
     ...     print(type(inst))    # the exception type
     ...     print(inst.args)     # arguments stored in .args
     ...     print(inst)          # __str__ allows args to be printed directly,
     ...                          # but may be overridden in exception subclasses
     ...     x, y = inst.args     # unpack args
     ...     print('x =', x)
     ...     print('y =', y)
     ...
     <class 'Exception'>
     ('spam', 'eggs')
     ('spam', 'eggs')
     x = spam
     y = eggs

例外的 *note __str__(): 5c4. 輸出會被印在未處理例外訊息的最後一部分（「
細節」）。

*note BaseException: 55f. 是由全部的例外所共用的 base class。它的
subclass（子類別）之一，*note Exception: 97d.，則是所有非嚴重例外
(non-fatal exception) 的 base class。有些例外不是 *note Exception: 97d.
的 subclass，而它們通常不會被處理，因為它們是用來指示程式應該終止。這些
例外包括了由 *note sys.exit(): 12dd. 所引發的 *note SystemExit: ce7.，以
及當使用者想要中斷程式時所引發的 *note KeyboardInterrupt: 975.。

*note Exception: 97d. 可以用作通配符 (wildcard) 來捕獲（幾乎）所有的例外
。然而，比較好的做法是盡可能具體地說明我們打算處理的例外類型，並容許任何
非預期例外的傳遞 (propagate)。

處理 *note Exception: 97d. 的最常見模式，是先將該例外印出或記錄，然後再
重新引發它（也允許一個呼叫函式 (caller) 來處理該例外）：

     import sys

     try:
         f = open('myfile.txt')
         s = f.readline()
         i = int(s.strip())
     except OSError as err:
         print("OS error:", err)
     except ValueError:
         print("Could not convert data to an integer.")
     except Exception as err:
         print(f"Unexpected {err=}, {type(err)=}")
         raise

*note try: 68c. ...  *note except: 171. 陳述式有一個選擇性的 'else 子句
'，使用時，該子句必須放在所有 'except 子句'之後。如果一段程式碼必須被執
行，但 'try 子句'又沒有引發例外時，這個子句很有用。例如：

     for arg in sys.argv[1:]:
         try:
             f = open(arg, 'r')
         except OSError:
             print('cannot open', arg)
         else:
             print(arg, 'has', len(f.readlines()), 'lines')
             f.close()

使用 ‘else’ 子句比向 *note try: 68c. 子句添加額外的程式碼要好，因為這可
以避免意外地捕獲不是由 ‘try’ ...  ‘except’ 陳述式保護的程式碼所引發的例
外。

例外的處理者不僅處理 'try 子句'內立即發生的例外，還處理 'try 子句'內（即
使是間接地）呼叫的函式內部發生的例外。例如：

     >>> def this_fails():
     ...     x = 1/0
     ...
     >>> try:
     ...     this_fails()
     ... except ZeroDivisionError as err:
     ...     print('Handling run-time error:', err)
     ...
     Handling run-time error: division by zero


File: python.info,  Node: 引發例外,  Next: 例外鏈接 Exception Chaining,  Prev: 處理例外,  Up: 錯誤和例外

2.8.4 引發例外
--------------

*note raise: 591. 陳述式可讓程式設計師強制引發指定的例外。例如：

     >>> raise NameError('HiThere')
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     NameError: HiThere

*note raise: 591. 唯一的引數就是要引發的例外。該引數必須是一個例外實例或
例外 class（衍生自 *note BaseException: 55f. 的 class，例如 *note
Exception: 97d. 與它的 subclass）。如果一個例外 class 被傳遞，它會不含引
數地呼叫它的建構函式 (constructor) ，使它被自動建立實例 (implicitly
instantiated)：

     raise ValueError  # 'raise ValueError()' 的簡寫

如果你只想判斷是否引發了例外，但並不打算處理它，則可以使用簡單的 *note
raise: 591. 陳述式來重新引發該例外：

     >>> try:
     ...     raise NameError('HiThere')
     ... except NameError:
     ...     print('An exception flew by!')
     ...     raise
     ...
     An exception flew by!
     Traceback (most recent call last):
       File "<stdin>", line 2, in <module>
     NameError: HiThere


File: python.info,  Node: 例外鏈接 Exception Chaining,  Next: 使用者自定的例外,  Prev: 引發例外,  Up: 錯誤和例外

2.8.5 例外鏈接 (Exception Chaining)
-----------------------------------

如果在 *note except: 171. 段落內部發生了一個未處理的例外，則它會讓這個將
要被處理的例外附加在後，並將其包含在錯誤訊息中：

     >>> try:
     ...     open("database.sqlite")
     ... except OSError:
     ...     raise RuntimeError("unable to handle error")
     ...
     Traceback (most recent call last):
       File "<stdin>", line 2, in <module>
     FileNotFoundError: [Errno 2] No such file or directory: 'database.sqlite'

     During handling of the above exception, another exception occurred:

     Traceback (most recent call last):
       File "<stdin>", line 4, in <module>
     RuntimeError: unable to handle error

為了表明一個例外是另一個例外直接造成的結果，*note raise: 591. 陳述式容許
一個選擇性的 *note from: 591. 子句：

     # exc 必須是例外實例或 None。
     raise RuntimeError from exc

要變換例外時，這種方式很有用。例如：

     >>> def func():
     ...     raise ConnectionError
     ...
     >>> try:
     ...     func()
     ... except ConnectionError as exc:
     ...     raise RuntimeError('Failed to open database') from exc
     ...
     Traceback (most recent call last):
       File "<stdin>", line 2, in <module>
       File "<stdin>", line 2, in func
     ConnectionError

     The above exception was the direct cause of the following exception:

     Traceback (most recent call last):
       File "<stdin>", line 4, in <module>
     RuntimeError: Failed to open database

它也容許使用慣用語 ‘from None’ 來停用自動例外鏈接：

     >>> try:
     ...     open('database.sqlite')
     ... except OSError:
     ...     raise RuntimeError from None
     ...
     Traceback (most recent call last):
       File "<stdin>", line 4, in <module>
     RuntimeError

更多關於鏈接機制的資訊，詳見*note 內建的例外: 1786.。


File: python.info,  Node: 使用者自定的例外,  Next: 定義清理動作,  Prev: 例外鏈接 Exception Chaining,  Up: 錯誤和例外

2.8.6 使用者自定的例外
----------------------

程式可以通過建立新的例外 class 來命名自己的例外（深入了解 Python class，
詳見*note Class（類別）: 1b23.）。不論是直接還是間接地，例外通常應該從
*note Exception: 97d. class 衍生出來。

例外 class 可被定義來做任何其他 class 能夠做的事，但通常會讓它維持簡單，
只提供一些屬性，讓關於錯誤的資訊可被例外的處理者抽取出來。

大多數的例外定義，都會以「Error」作為名稱結尾，類似於標準例外的命名。

許多標準模組會定義它們自己的例外，以報告在其定義的函式中發生的錯誤。


File: python.info,  Node: 定義清理動作,  Next: 預定義的清理動作,  Prev: 使用者自定的例外,  Up: 錯誤和例外

2.8.7 定義清理動作
------------------

*note try: 68c. 陳述式有另一個選擇性子句，用於定義在所有情況下都必須被執
行的清理動作。例如：

     >>> try:
     ...     raise KeyboardInterrupt
     ... finally:
     ...     print('Goodbye, world!')
     ...
     Goodbye, world!
     Traceback (most recent call last):
       File "<stdin>", line 2, in <module>
     KeyboardInterrupt

如果 *note finally: 96e. 子句存在，則 ‘finally’ 子句會是 *note try: 68c.
陳述式結束前執行的最後一項任務。不論 ‘try’ 陳述式是否產生例外，都會執行
‘finally’ 子句。以下幾點將探討例外發生時，比較複雜的情況：

   * 若一個例外發生於 ‘try’ 子句的執行過程，則該例外會被某個 *note
     except: 171. 子句處理。如果該例外沒有被 ‘except’ 子句處理，它會在
     ‘finally’ 子句執行後被重新引發。

   * 一個例外可能發生於 ‘except’ 或 ‘else’ 子句的執行過程。同樣地，該例
     外會在 ‘finally’ 子句執行後被重新引發。

   * 如果 ‘finally’ 子句執行 *note break: a4c.、*note continue: 96d. 或
     *note return: 972. 陳述式，則例外不會被重新引發。

   * 如果 ‘try’ 陳述式遇到 *note break: a4c.、*note continue: 96d. 或
     *note return: 972. 陳述式，則 ‘finally’ 子句會在執行 ‘break’、
     ‘continue’ 或 ‘return’ 陳述式之前先執行。

   * 如果 ‘finally’ 子句中包含 ‘return’ 陳述式，則回傳值會是來自
     ‘finally’ 子句的 ‘return’ 陳述式的回傳值，而不是來自 ‘try’ 子句的
     ‘return’ 陳述式的回傳值。

例如：

     >>> def bool_return():
     ...     try:
     ...         return True
     ...     finally:
     ...         return False
     ...
     >>> bool_return()
     False

另一個比較複雜的範例：

     >>> def divide(x, y):
     ...     try:
     ...         result = x / y
     ...     except ZeroDivisionError:
     ...         print("division by zero!")
     ...     else:
     ...         print("result is", result)
     ...     finally:
     ...         print("executing finally clause")
     ...
     >>> divide(2, 1)
     result is 2.0
     executing finally clause
     >>> divide(2, 0)
     division by zero!
     executing finally clause
     >>> divide("2", "1")
     executing finally clause
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
       File "<stdin>", line 3, in divide
     TypeError: unsupported operand type(s) for /: 'str' and 'str'

如你所見，*note finally: 96e. 子句在任何情況下都會被執行。兩個字串相除所
引發的 *note TypeError: 4dd. 沒有被 *note except: 171. 子句處理，因此會
在 ‘finally’ 子句執行後被重新引發。

在真實應用程式中，*note finally: 96e. 子句對於釋放外部資源（例如檔案或網
路連線）很有用，無論該資源的使用是否成功。


File: python.info,  Node: 預定義的清理動作,  Next: 引發及處理多個無關的例外,  Prev: 定義清理動作,  Up: 錯誤和例外

2.8.8 預定義的清理動作
----------------------

某些物件定義了在物件不再被需要時的標準清理動作，無論使用該物件的作業是成
功或失敗。請看以下範例，它嘗試開啟一個檔案，並印出檔案內容至螢幕。

     for line in open("myfile.txt"):
         print(line, end="")

這段程式碼的問題在於，執行完該程式碼後，它讓檔案在一段不確定的時間內處於
開啟狀態。在簡單腳本中這不是問題，但對於較大的應用程式來說可能會是個問題
。*note with: 577. 陳述式讓物件（例如檔案）在被使用時，能保證它們總是及
時、正確地被清理。

     with open("myfile.txt") as f:
         for line in f:
             print(line, end="")

陳述式執行完畢後，就算是在處理內容時遇到問題，檔案 'f' 總是會被關閉。和
檔案一樣，提供預定義清理動作的物件會在說明文件中表明這一點。


File: python.info,  Node: 引發及處理多個無關的例外,  Next: 用註解使例外更詳細,  Prev: 預定義的清理動作,  Up: 錯誤和例外

2.8.9 引發及處理多個無關的例外
------------------------------

在某些情況下，必須回報已經發生的多個例外。在並行框架 (concurrency
framework) 中經常會出現這種情況，當平行的 (parallel) 某些任務可能已經失
效，但還有其他用例 (use case) 希望能繼續執行並收集多個例外，而不是只有引
發第一個例外時。

內建的 *note ExceptionGroup: 19c. 會包裝一個例外實例 (exception
instance) 的 list（串列），使得它們可以一起被引發。由於它本身就是一個例
外，因此它也可以像任何其他例外一樣被捕獲。

     >>> def f():
     ...     excs = [OSError('error 1'), SystemError('error 2')]
     ...     raise ExceptionGroup('there were problems', excs)
     ...
     >>> f()
       + Exception Group Traceback (most recent call last):
       |   File "<stdin>", line 1, in <module>
       |   File "<stdin>", line 3, in f
       | ExceptionGroup: there were problems
       +-+---------------- 1 ----------------
         | OSError: error 1
         +---------------- 2 ----------------
         | SystemError: error 2
         +------------------------------------
     >>> try:
     ...     f()
     ... except Exception as e:
     ...     print(f'caught {type(e)}: e')
     ...
     caught <class 'ExceptionGroup'>: e
     >>>

若使用 ‘except*’ 代替 ‘except’，我們可以選擇性地只處理該群組中與特定類型
匹配的例外。在以下範例中，展示了一個巢狀的例外群組 (exception group)，每
個 ‘except*’ 子句分別從該群組中提取一個特定類型的例外，同時讓所有其他的
例外都傳遞到其他子句，最後再被重新引發。

     >>> def f():
     ...     raise ExceptionGroup(
     ...         "group1",
     ...         [
     ...             OSError(1),
     ...             SystemError(2),
     ...             ExceptionGroup(
     ...                 "group2",
     ...                 [
     ...                     OSError(3),
     ...                     RecursionError(4)
     ...                 ]
     ...             )
     ...         ]
     ...     )
     ...
     >>> try:
     ...     f()
     ... except* OSError as e:
     ...     print("There were OSErrors")
     ... except* SystemError as e:
     ...     print("There were SystemErrors")
     ...
     There were OSErrors
     There were SystemErrors
       + Exception Group Traceback (most recent call last):
       |   File "<stdin>", line 2, in <module>
       |   File "<stdin>", line 2, in f
       | ExceptionGroup: group1
       +-+---------------- 1 ----------------
         | ExceptionGroup: group2
         +-+---------------- 1 ----------------
           | RecursionError: 4
           +------------------------------------
     >>>

請注意，被巢套在例外群組中的例外必須是實例，而不是類型。這是因為在實務上
，這些例外通常是已經被程式引發並捕獲的例外，類似以下的模式：

     >>> excs = []
     ... for test in tests:
     ...     try:
     ...         test.run()
     ...     except Exception as e:
     ...         excs.append(e)
     ...
     >>> if excs:
     ...    raise ExceptionGroup("Test Failures", excs)
     ...


File: python.info,  Node: 用註解使例外更詳細,  Prev: 引發及處理多個無關的例外,  Up: 錯誤和例外

2.8.10 用註解使例外更詳細
-------------------------

當一個例外是為了被引發而建立時，它通常會伴隨著一些資訊被初始化，這些資訊
描述了當下發生的錯誤。在某些情況，在例外被捕獲之後添加資訊會很有用。為此
，例外具有一個 ‘add_note(note)’ method（方法），它可以接受一個字串並將其
添加到例外的註解清單中。標準的回溯呈現會在例外之後列出所有的註解，並按照
其被添加的順序來排列。

     >>> try:
     ...     raise TypeError('bad type')
     ... except Exception as e:
     ...     e.add_note('Add some information')
     ...     e.add_note('Add some more information')
     ...     raise
     ...
     Traceback (most recent call last):
       File "<stdin>", line 2, in <module>
     TypeError: bad type
     Add some information
     Add some more information
     >>>

例如，在將例外收集到例外群組中時，我們可能希望為各個錯誤添加一些上下文的
資訊。在以下範例中，群組中的每個例外都有一條註解，指示此錯誤是在何時發生
。

     >>> def f():
     ...     raise OSError('operation failed')
     ...
     >>> excs = []
     >>> for i in range(3):
     ...     try:
     ...         f()
     ...     except Exception as e:
     ...         e.add_note(f'Happened in Iteration {i+1}')
     ...         excs.append(e)
     ...
     >>> raise ExceptionGroup('We have some problems', excs)
       + Exception Group Traceback (most recent call last):
       |   File "<stdin>", line 1, in <module>
       | ExceptionGroup: We have some problems (3 sub-exceptions)
       +-+---------------- 1 ----------------
         | Traceback (most recent call last):
         |   File "<stdin>", line 3, in <module>
         |   File "<stdin>", line 2, in f
         | OSError: operation failed
         | Happened in Iteration 1
         +---------------- 2 ----------------
         | Traceback (most recent call last):
         |   File "<stdin>", line 3, in <module>
         |   File "<stdin>", line 2, in f
         | OSError: operation failed
         | Happened in Iteration 2
         +---------------- 3 ----------------
         | Traceback (most recent call last):
         |   File "<stdin>", line 3, in <module>
         |   File "<stdin>", line 2, in f
         | OSError: operation failed
         | Happened in Iteration 3
         +------------------------------------
     >>>


File: python.info,  Node: Class（類別）,  Next: Python 標準函式庫概覽,  Prev: 錯誤和例外,  Up: Python 教學

2.9 Class（類別）
=================

Class 提供了一種結合資料與功能的手段。建立一個 class 將會新增一個物件的
'型別 (type)'，並且允許建立該型別的新'實例 (instance)'。每一個 class 實
例可以擁有一些維持該實例狀態的屬性 (attribute)。Class 實例也可以有一些（
由其 class 所定義的）method（方法），用於修改該實例的狀態。

與其他程式語言相比，Python 的 class 機制為 class 增加了最少的新語法跟語
意。他混合了 C++ 和 Modula-3 的 class 機制。Python 的 class 提供了所有物
件導向程式設計 (Object Oriented Programming) 的標準特色：class 繼承機制
允許多個 base class（基底類別），一個 derived class（衍生類別）可以覆寫
(override) 其 base class 的任何 method，且一個 method 可以用相同的名稱呼
叫其 base class 的 method。物件可以包含任意數量及任意種類的資料。如同模
組一樣，class 也具有 Python 的動態特性：他們在執行期 (runtime) 被建立，
且可以在建立之後被修改。

在 C++ 的術語中，class 成員（包含資料成員）通常都是'公開'的（除了以下內
容：*note 私有變數: 1ba4.），而所有的成員函式都是'虛擬'的。如同在
Modula-3 中一樣，Python 並沒有提供簡寫可以從物件的 method 裡參照其成員：
method 函式與一個外顯的 (explicit)、第一個代表物件的引數被宣告，而此引數
是在呼叫時隱性地 (implicitly) 被提供。如同在 Smalltak 中，class 都是物件
，這為 import 及重新命名提供了語意。不像 C++ 和 Modula-3，Pyhon 內建的型
別可以被使用者以 base class 用於其他擴充 (extension)。另外，如同在 C++ 中
，大多數有著特別語法的內建運算子（算術運算子、下標等）都可以為了 class 實
例而被重新定義。

（由於缺乏普遍能接受的術語來討論 class，我偶爾會使用 Smalltalk 和 C++ 的
術語。我會使用 Modula-3 的術語，因為它比 C++ 更接近 Python 的物件導向語
意，但我預期比較少的讀者會聽過它。）

* Menu:

* 關於名稱與物件的一段話::
* Python 作用域 (Scope) 及命名空間 (Namespace): Python 作用域 Scope 及命名空間 Namespace.
* 初見 class::
* 隨意的備註::
* 繼承 (Inheritance): 繼承 Inheritance.
* 私有變數::
* 補充說明::
* 疊代器 (Iterator): 疊代器 Iterator.
* 產生器 (Generator): 產生器 Generator.
* 產生器運算式::


File: python.info,  Node: 關於名稱與物件的一段話,  Next: Python 作用域 Scope 及命名空間 Namespace,  Up: Class（類別）

2.9.1 關於名稱與物件的一段話
----------------------------

物件有個體性 (individuality)，且多個名稱（在多個作用域 (scope) ）可以被
連結到相同的物件。這在其他語言中被稱為別名 (aliasing)。初次接觸 Python 時
通常不會注意這件事，而在處理不可變的基本型別（數值、字串、tuple）時，它
也可以安全地被忽略。然而，別名在含有可變物件（如 list（串列）、
dictionary（字典）、和大多數其他的型別）的 Python 程式碼語意中，可能會有
意外的效果。這通常有利於程式，因為別名在某些方面表現得像指標 (pointer)。
舉例來說，在實作時傳遞一個物件是便宜的，因為只有指標被傳遞；假如函式修改
了一個作為引數傳遞的物件，呼叫函式者 (caller) 能夠見到這些改變——這消除了
在 Pascal 中兩個相異引數傳遞機制的需求。


File: python.info,  Node: Python 作用域 Scope 及命名空間 Namespace,  Next: 初見 class,  Prev: 關於名稱與物件的一段話,  Up: Class（類別）

2.9.2 Python 作用域 (Scope) 及命名空間 (Namespace)
--------------------------------------------------

在介紹 class 之前，我必須先告訴你一些關於 Python 作用域的規則。Class
definition（類別定義）以命名空間展現了一些俐落的技巧，而你需要了解作用域
和命名空間的運作才能完整理解正在發生的事情。順帶一提，關於這個主題的知識
對任何進階的 Python 程式設計師都是很有用的。

讓我們從一些定義開始。

'命名空間'是從名稱到物件的映射。大部分的命名空間現在都是以 Python 的
dictionary 被實作，但通常不會以任何方式被察覺（除了性能），且它可能會在
未來改變。命名空間的例子有：內建名稱的集合（包含如 *note abs(): 1ba8. 的
函式，和內建的例外名稱）；模組中的全域 (global) 名稱；和在函式調用中的區
域 (local) 名稱。某種意義上，物件中的屬性集合也會形成一個命名空間。關於
命名空間的重要一點是，不同命名空間中的名稱之間絕對沒有關係；舉例來說，兩
個不一樣的模組都可以定義一個 ‘maximize’ 函式而不會混淆——模組的使用者必須
為它加上前綴 (prefix) 模組名稱。

順帶一提，我使用'屬性 (attribute)' 這個字，統稱句號 (dot) 後面的任何名稱
——例如，運算式中的 ‘z.real’，‘real’ 是物件 ‘z’ 的一個屬性。嚴格來說，模
組中名稱的參照都是屬性參照：在運算式 ‘modname.funcname’ 中，‘modname’ 是
模組物件而 ‘funcname’ 是它的屬性。在這種情況下，模組的屬性和模組中定義的
全域名稱碰巧有一個直接的對映：他們共享了相同的命名空間！(1)

屬性可以是唯讀的或可寫的。在後者的情況下，對屬性的賦值是可能的。模組屬性
是可寫的：你可以寫 ‘modname.the_answer = 42’。可寫屬性也可以用 *note
del: 16a9. 陳述式刪除。例如，‘del modname.the_answer’ 將從名為 ‘modname’
的物件中刪除屬性 ‘the_answer’。

命名空間在不同的時刻被建立，並且有不同的壽命。當 Python 直譯器啟動時，含
有內建名稱的命名空間會被建立，並且永遠不會被刪除。當模組定義被讀入時，模
組的全域命名空間會被建立；一般情況下，模組的命名空間也會持續到直譯器結束
。被直譯器的頂層調用 (top-level invocation) 執行的陳述式，不論是從腳本檔
案讀取的或是互動模式中的，會被視為一個稱為 *note __main__: 1. 的模組的一
部分，因此它們具有自己的全域命名空間。（內建名稱實際上也存在一個模組中，
它被稱為 *note builtins: e.。）

函式的區域命名空間是在呼叫函式時建立的，而當函式返回，或引發了未在函式中
處理的例外時，此命名空間將會被刪除。（實際上，忘記是描述實際發生的事情的
更好方法。） 當然，每個遞迴調用 (recursive invocation) 都有自己的區域命
名空間。

'作用域'是 Python 程式中的一個文本區域 (textual region)，在此區域，命名
空間是可直接存取的。這裡的「可直接存取的」意思是，對一個名稱的非限定參照
(unqualified reference) 可以在命名空間內嘗試尋找該名稱。

儘管作用域是靜態地被決定，但它們是動態地被使用的。在執行期間內的任何時間
點，都會有 3 或 4 個巢狀的作用域，其命名空間是可以被直接存取的：

   * 最內層作用域，會最先被搜尋，而它包含了區域名稱

   * 任何外圍函式 (enclosing function) 的作用域，會從最近的外圍作用域開
     始搜尋，它包含了非區域 (non-local) 和非全域 (non-global) 的名稱

   * 倒數第二個作用域，包含當前模組的全域名稱

   * 最外面的作用域（最後搜尋），是包含內建名稱的命名空間

如果一個名稱被宣告為全域，則所有的參照和賦值將直接轉到包含模組全域名稱的
倒數第二個作用域。要重新連結最內層作用域以外找到的變數，可以使用 *note
nonlocal: 123e. 陳述式；如果那些變數沒有被宣告為 nonlocal，則它們會是唯
讀的（嘗試寫入這樣的變數只會在最內層的作用域內建立一個'新的'區域變數，同
名的外部變數則維持不變）。

通常，區域作用域會參照（文本的）當前函式的區域名稱。在函式外部，區域作用
域與全域作用域參照相同的命名空間：模組的命名空間。然而，Class definition
會在區域作用域中放置另一個命名空間。

務必要了解，作用域是按文本被決定的：在模組中定義的函式，其全域作用域便是
該模組的命名空間，無論函式是從何處或以什麼別名被呼叫。另一方面，對名稱的
實際搜尋是在執行時期 (run time) 動態完成的——但是，語言定義的發展，正朝向
在「編譯」時期 (compile time) 的靜態名稱解析 (static name resolution)，
所以不要太依賴動態名稱解析 (dynamic name resolution)！ （事實上，局部變
數已經是靜態地被決定。）

一個 Python 的特殊癖好是——假如沒有 *note global: 170. 或 *note nonlocal:
123e. 陳述式的效果——名稱的賦值 (assignment) 都會指向最內層作用域。賦值不
會複製資料——它們只會把名稱連結至物件。刪除也是一樣：陳述式 ‘del x’ 會從
區域作用域參照的命名空間移除 ‘x’ 的連結。事實上，引入新名稱的所有運算都
使用區域作用域：特別是 *note import: 586. 陳述式和函式定義，會連結區域作
用域內的模組或函式名稱。

*note global: 170. 陳述式可以用來表示特定變數存活在全域作用域，應該被重
新綁定到那裡；*note nonlocal: 123e. 陳述式表示特定變數存活在外圍作用域內
，應該被重新綁定到那裡。

* Menu:

* 作用域和命名空間的範例::

   ---------- Footnotes ----------

   (1) 有一個例外。模組物件有一個秘密的唯讀屬性，稱為 *note __dict__:
c04.，它回傳用於實作模組命名空間的 dictionary；*note __dict__: c04. 這個
名稱是一個屬性但不是全域名稱。顯然，使用此屬性將違反命名空間實作的抽象化
，而應該僅限用於事後除錯器 (post-mortem debugger) 之類的東西。


File: python.info,  Node: 作用域和命名空間的範例,  Up: Python 作用域 Scope 及命名空間 Namespace

2.9.2.1 作用域和命名空間的範例
..............................

這是一個範例，演示如何參照不同的作用域和命名空間，以及 *note global:
170. 和 *note nonlocal: 123e. 如何影響變數的綁定：

     def scope_test():
         def do_local():
             spam = "local spam"

         def do_nonlocal():
             nonlocal spam
             spam = "nonlocal spam"

         def do_global():
             global spam
             spam = "global spam"

         spam = "test spam"
         do_local()
         print("After local assignment:", spam)
         do_nonlocal()
         print("After nonlocal assignment:", spam)
         do_global()
         print("After global assignment:", spam)

     scope_test()
     print("In global scope:", spam)

範例程式碼的輸出是：

     After local assignment: test spam
     After nonlocal assignment: nonlocal spam
     After global assignment: nonlocal spam
     In global scope: global spam

請注意，'區域'賦值（預設情況）不會改變 'scope_test' 對 'spam' 的連結。
*note nonlocal: 123e. 賦值改變了 'scope_test' 對 'spam' 的連結，而 *note
global: 170. 賦值改變了模組層次的連結。

你還可以發現，在 *note global: 170. 賦值之前，沒有對 'spam' 的連結。


File: python.info,  Node: 初見 class,  Next: 隨意的備註,  Prev: Python 作用域 Scope 及命名空間 Namespace,  Up: Class（類別）

2.9.3 初見 class
----------------

Class 採用一些新的語法，三個新的物件型別，以及一些新的語意。

* Menu:

* Class definition（類別定義）語法::
* Class 物件::
* 實例物件::
* Method 物件::
* Class 及實例變數::


File: python.info,  Node: Class definition（類別定義）語法,  Next: Class 物件,  Up: 初見 class

2.9.3.1 Class definition（類別定義）語法
........................................

Class definition 最簡單的形式如下：

     class ClassName:
         <statement-1>
         .
         .
         .
         <statement-N>

Class definition，如同函式定義（*note def: 13c5. 陳述式），必須在它們有
任何效果前先執行。（你可以想像把 class definition 放在一個 *note if:
2c4. 陳述式的分支，或在函式裡。）

在實作時，class definition 內的陳述式通常會是函式定義，但其他陳述式也是
允許的，有時很有用——我們稍後會回到這裡。Class 中的函式定義通常會有一個獨
特的引數列表形式，取決於 method 的呼叫慣例——再一次地，這將會在稍後解釋。

當進入 class definition，一個新的命名空間將會被建立，並且作為區域作用域
——因此，所有區域變數的賦值將進入這個新的命名空間。特別是，函式定義會在這
裡連結新函式的名稱。

正常地（從結尾處）離開 class definition 時，一個 'class 物件'會被建立。
基本上這是一個包裝器 (wrapper)，裝著 class definition 建立的命名空間內容
；我們將在下一節中更加了解 class 物件。原始的區域作用域（在進入 class
definition 之前已生效的作用域）會恢復，在此 class 物件會被連結到 class
definition 標頭中給出的 class 名稱（在範例中為 ‘ClassName’）。


File: python.info,  Node: Class 物件,  Next: 實例物件,  Prev: Class definition（類別定義）語法,  Up: 初見 class

2.9.3.2 Class 物件
..................

Class 物件支援兩種運算：屬性參照 (attribute reference) 和實例化
(instantiation)。

'屬性參照'使用 Python 中所有屬性參照的標準語法：‘obj.name’。有效的屬性名
稱是 class 物件被建立時，class 的命名空間中所有的名稱。所以，如果 class
definition 看起來像這樣：

     class MyClass:
         """一個簡單的類別範例"""
         i = 12345

         def f(self):
             return 'hello world'

那麼 ‘MyClass.i’ 和 ‘MyClass.f’ 都是有效的屬性參照，會分別回傳一個整數和
一個函式物件。Class 屬性也可以被指派 (assign)，所以你可以透過賦值改變
‘MyClass.i’ 的值。‘__doc__’ 也是一個有效的屬性，會回傳屬於該 class 的說
明字串 (docstring)：‘"A simple example class"’。

Class '實例化'使用了函式記法 (function notation)。就好像 class 物件是一
個沒有參數的函式，它回傳一個新的 class 實例。例如（假設是上述的 class）
：

     x = MyClass()

建立 class 的一個新'實例'，並將此物件指派給區域變數 ‘x’。

實例化運算（「呼叫」一個 class 物件）會建立一個空的物件。許多 class 喜歡
在建立物件時有著自訂的特定實例初始狀態。因此，class 可以定義一個名為
*note __init__(): 655. 的特別 method，像這樣：

     def __init__(self):
         self.data = []

當 class 定義了 *note __init__(): 655. method，class 實例化會為新建的
class 實例自動調用 ‘__init__()’。所以在這個範例中，一個新的、初始化的實
例可以如此獲得：

     x = MyClass()

當然，*note __init__(): 655. method 可能為了更多的彈性而有引數。在這種情
況下，要給 class 實例化運算子的引數會被傳遞給 ‘__init__()’。例如：

     >>> class Complex:
     ...     def __init__(self, realpart, imagpart):
     ...         self.r = realpart
     ...         self.i = imagpart
     ...
     >>> x = Complex(3.0, -4.5)
     >>> x.r, x.i
     (3.0, -4.5)


File: python.info,  Node: 實例物件,  Next: Method 物件,  Prev: Class 物件,  Up: 初見 class

2.9.3.3 實例物件
................

現在，我們可以如何處理實例物件？實例物件能理解的唯一運算就是屬性參照。有
兩種有效的屬性名稱：資料屬性 (data attribute) 和 method。

'資料屬性'對應 Smalltalk 中的「實例變數」，以及 C++ 中的「資料成員」。資
料屬性不需要被宣告；和區域變數一樣，它們在第一次被賦值時就會立即存在。例
如，如果 ‘x’ 是 ‘MyClass’ 在上述例子中建立的實例，下面的程式碼將印出值
‘16’，而不留下蹤跡：

     x.counter = 1
     while x.counter < 10:
         x.counter = x.counter * 2
     print(x.counter)
     del x.counter

The other kind of instance attribute reference is a 'method'.  A method
is a function that "belongs to" an object.

實例物件的有效 method 名稱取決於其 class。根據定義，一個 class 中所有的
函式物件屬性，就定義了實例的對應 method。所以在我們的例子中，‘x.f’ 是一
個有效的 method 參照，因為 ‘MyClass.f’ 是一個函式，但 ‘x.i’ 不是，因為
‘MyClass.i’ 不是。但 ‘x.f’ 與 ‘MyClass.f’ 是不一樣的——它是一個 'method 物
件'，而不是函式物件。


File: python.info,  Node: Method 物件,  Next: Class 及實例變數,  Prev: 實例物件,  Up: 初見 class

2.9.3.4 Method 物件
...................

通常，一個 method 在它被連結後隨即被呼叫：

     x.f()

在 ‘MyClass’ 的例子中，這將回傳字串 ‘'hello world'’。然而，並沒有必要立
即呼叫一個 method：‘x.f’ 是一個 method 物件，並且可以被儲藏起來，之後再
被呼叫。舉例來說：

     xf = x.f
     while True:
         print(xf())

將會持續印出 ‘hello world’ 直到天荒地老。

當一個 method 被呼叫時究竟會發生什麼事？你可能已經注意到 ‘x.f()’ 被呼叫
時沒有任何的引數，儘管 ‘f()’ 的函式定義有指定一個引數。這個引數發生了什
麼事？當一個需要引數的函式被呼叫而沒有給任何引數時，Python 肯定會引發例
外——即使該引數實際上沒有被使用...

事實上，你可能已經猜到了答案：method 的特殊之處在於，實例物件會作為函式
中的第一個引數被傳遞。在我們的例子中，‘x.f()’ 這個呼叫等同於
‘MyClass.f(x)’。一般來說，呼叫一個有 'n' 個引數的 method，等同於呼叫一個
對應函式，其引數列表 (argument list) 被建立時，會在第一個引數前插入該
method 的實例物件。

一般來說，方法的工作原理如下。當一個實例的非資料屬性被參照時，將會搜尋該
實例的 class。如果該名稱是一個有效的 class 屬性，而且是一個函式物件，則
對實例物件和函式物件的參照都會被打包到方法物件中。當使用引數串列呼叫方法
物件時，會根據實例物件和引數串列來建構一個新的引數串列，並使用該新引數串
列來呼叫函式物件。


File: python.info,  Node: Class 及實例變數,  Prev: Method 物件,  Up: 初見 class

2.9.3.5 Class 及實例變數
........................

一般來說，實例變數用於每一個實例的獨特資料，而 class 變數用於該 class 的
所有實例共享的屬性和 method：

     class Dog:

         kind = 'canine'         # class variable shared by all instances

         def __init__(self, name):
             self.name = name    # instance variable unique to each instance

     >>> d = Dog('Fido')
     >>> e = Dog('Buddy')
     >>> d.kind                  # shared by all dogs
     'canine'
     >>> e.kind                  # shared by all dogs
     'canine'
     >>> d.name                  # unique to d
     'Fido'
     >>> e.name                  # unique to e
     'Buddy'

如同在*note 關於名稱與物件的一段話: 1ba6.的討論，共享的資料若涉及 *note
mutable: 1b07. 物件，如 list 和 dictionary，可能會產生意外的影響。舉例來
說，下列程式碼的 'tricks' list 不應該作為一個 class 變數使用，因為這個
list 將會被所有的 'Dog' 實例所共享：

     class Dog:

         tricks = []             # mistaken use of a class variable

         def __init__(self, name):
             self.name = name

         def add_trick(self, trick):
             self.tricks.append(trick)

     >>> d = Dog('Fido')
     >>> e = Dog('Buddy')
     >>> d.add_trick('roll over')
     >>> e.add_trick('play dead')
     >>> d.tricks                # unexpectedly shared by all dogs
     ['roll over', 'play dead']

正確的 class 設計應該使用實例變數：

     class Dog:

         def __init__(self, name):
             self.name = name
             self.tricks = []    # creates a new empty list for each dog

         def add_trick(self, trick):
             self.tricks.append(trick)

     >>> d = Dog('Fido')
     >>> e = Dog('Buddy')
     >>> d.add_trick('roll over')
     >>> e.add_trick('play dead')
     >>> d.tricks
     ['roll over']
     >>> e.tricks
     ['play dead']


File: python.info,  Node: 隨意的備註,  Next: 繼承 Inheritance,  Prev: 初見 class,  Up: Class（類別）

2.9.4 隨意的備註
----------------

如果屬性名稱同時出現在一個實例和一個 class 中，則屬性的尋找會以實例為優
先：

     >>> class Warehouse:
     ...    purpose = 'storage'
     ...    region = 'west'
     ...
     >>> w1 = Warehouse()
     >>> print(w1.purpose, w1.region)
     storage west
     >>> w2 = Warehouse()
     >>> w2.region = 'east'
     >>> print(w2.purpose, w2.region)
     storage east

資料屬性可能被 method 或是被物件的一般使用者（「客戶端」）所參照。也就是
說，class 不可用於實作純粹抽象的資料型別。事實上，在 Python 中沒有任何可
能的方法，可強制隱藏資料——這都是基於慣例。（另一方面，以 C 編寫的 Python
實作可以完全隱藏實作細節並且在必要時控制物件的存取；這可以被以 C 編寫的
Python 擴充所使用。）

客戶端應該小心使用資料屬性——客戶端可能會因為覆寫他們的資料屬性，而破壞了
被 method 維護的不變性。注意，客戶端可以增加他們自己的資料屬性到實例物件
，但不影響 method 的有效性，只要避免名稱衝突即可——再一次提醒，命名慣例可
以在這裡節省很多麻煩。

在 method 中參照資料屬性（或其他 method！）是沒有簡寫的。我發現這實際上
增加了 method 的可閱讀性：在瀏覽 method 時，絕不會混淆區域變數和實例變數
。

通常，方法的第一個引數稱為 ‘self’。這僅僅只是一個慣例：‘self’ 這個名字對
Python 來說完全沒有特別的意義。但請注意，如果不遵循慣例，你的程式碼可能
對其他 Python 程式設計師來說可讀性較低，此外，也可以想像一個可能因信任此
慣例而編寫的 'class 瀏覽器 (browser)' 程式。

任何一個作為 class 屬性的函式物件都為該 class 的實例定義了一個相應的
method。函式定義不一定要包含在 class definition 的文本中：將函式物件指定
給 class 中的區域變數也是可以的。例如：

     # Function defined outside the class
     def f1(self, x, y):
         return min(x, x+y)

     class C:
         f = f1

         def g(self):
             return 'hello world'

         h = g

現在 ‘f’、‘g’ 和 ‘h’ 都是 class ‘C’ 的屬性，並指向函式物件，所以他們都是
class ‘C’ 實例的 method —— ‘h’ 與 ‘g’ 是完全一樣的。請注意，這種做法通常
只會使該程式的讀者感到困惑。

Method 可以藉由使用 ‘self’ 引數的 method 屬性，呼叫其他 method：

     class Bag:
         def __init__(self):
             self.data = []

         def add(self, x):
             self.data.append(x)

         def addtwice(self, x):
             self.add(x)
             self.add(x)

Method 可以用與一般函式相同的方式參照全域名稱。與 method 相關的全域作用
域，就是包含其定義的模組。（class 永遠不會被用作全域作用域。）雖然人們很
少有在 method 中使用全域資料的充分理由，但全域作用域仍有許多合法的使用：
比方說，被 import 至全域作用域的函式和模組，可以被 method 以及在該作用域
中定義的函式和 class 所使用。通常，包含 method 的 class，它本身就是被定
義在這個全域作用域，在下一節，我們將看到 method 想要參照自己的 class 的
一些好原因。

每個值都是一個物件，因此都具有一個 'class'，也可以稱為它的 'type（型別）
'。它以 ‘object.__class__’ 被儲存。


File: python.info,  Node: 繼承 Inheritance,  Next: 私有變數,  Prev: 隨意的備註,  Up: Class（類別）

2.9.5 繼承 (Inheritance)
------------------------

當然，如果沒有支援繼承，「class」這個語言特色就不值得被稱為 class。一個
derived class（衍生類別）定義的語法看起來如下：

     class DerivedClassName(BaseClassName):
         <statement-1>
         .
         .
         .
         <statement-N>

名稱 ‘BaseClassName’ 必須被定義於作用域可及的命名空間，且該作用域要包含
derived class 定義。要代替 base class（基底類別）的名稱，用其他任意的運
算式也是被允許的。這會很有用，例如，當一個 base class 是在另一個模組中被
定義時：

     class DerivedClassName(modname.BaseClassName):

執行 derived class 定義的過程，與執行 base class 相同。當 class 物件被建
構時，base class 會被記住。這是用於解析屬性參照：如果一個要求的屬性無法
在該 class 中找到，則會繼續在 base class 中搜尋。假如該 base class 本身
也是衍生自其他 class，則這個規則會遞迴地被應用。

關於 derived class 的實例化並沒有特別之處：‘DerivedClassName()’ 會建立該
class 的一個新實例。Method 的參照被解析如下：對應的 class 屬性會被搜尋，
如果需要，沿著 base class 的繼承鍊往下走，如果這產生了一個函式物件，則該
method 的參照是有效的。

Derived class 可以覆寫其 base class 的 method。因為 method 在呼叫同一個
物件的其他 method 時沒有特別的特權，所以當 base class 的一個 method 在呼
叫相同 base class 中定義的另一個 method 時，最終可能會呼叫到一個覆寫它的
derived class 中的 method。（給 C++ 程式設計師：Python 中所有 method 實
際上都是 ‘virtual’。）

一個在 derived class 覆寫的 method 可能事實上是想要擴充而非單純取代 base
class 中相同名稱的 method。要直接呼叫 base class 的 method 有一個簡單的
方法：只要呼叫 ‘BaseClassName.methodname(self, arguments)’。這有時對客戶
端也很有用。（請注意，只有在 base class 在全域作用域可以用
‘BaseClassName’ 被存取時，這方法才有效。）

Python 有兩個內建函式可以用於繼承：

   * 使用 *note isinstance(): 3e8. 判斷一個實例的型別：‘isinstance(obj,
     int)’ 只有在 ‘obj.__class__’ 是 *note int: 23c. 或衍伸自 *note int:
     23c. 時，結果才會是 ‘True’。

   * 使用 *note issubclass(): 765. 判斷 class 繼承：‘issubclass(bool,
     int)’ 會是 ‘True’，因為 *note bool: 40e. 是 *note int: 23c. 的
     subclass（子類別）。但是，‘issubclass(float, int)’ 是 ‘False’，因為
     *note float: 2c8. 並不是 *note int: 23c. 的 subclass。

* Menu:

* 多重繼承::


File: python.info,  Node: 多重繼承,  Up: 繼承 Inheritance

2.9.5.1 多重繼承
................

Python 也支援多重繼承的形式。一個有多個 base class 的 class definition 看
起來像這樣子：

     class DerivedClassName(Base1, Base2, Base3):
         <statement-1>
         .
         .
         .
         <statement-N>

在大多數情況下，最簡單的例子裡，你可以這樣思考，對於繼承自 parent class（
父類別）的屬性，其搜尋規則為：深度優先、從左到右、在階層裡重疊的相同
class 中不重複搜尋。因此，假如有一個屬性在 ‘DerivedClassName’ 沒有被找到
，則在 ‘Base1’ 搜尋它，接著（遞迴地）在 ‘Base1’ 的 base class 中搜尋，假
如在那裡又沒有找到的話，會在 ‘Base2’ 搜尋，依此類推。

事實上，它稍微複雜一些；method 的解析順序是動態地變化，以支援對 *note
super(): 483. 的合作呼叫。這個方式在其他的多重繼承語言中，稱為呼叫下一個
方法 (call-next-method)，且比在單一繼承語言中的 super call（超級呼叫）來
得更強大。

動態排序是必要的，因為多重繼承的所有情況都表現一或多的菱形關係（其中至少
一個 parent class 可以從最底層 class 透過多個路徑存取）。例如，所有的
class 都繼承自 *note object: a2f.，因此任何多重繼承的情況都提供了多個到
達 *note object: a2f. 的路徑。為了避免 base class 被多次存取，動態演算法
以這些方式將搜尋順序線性化 (linearize)：保留每個 class 中規定的從左到右
的順序、對每個 parent 只會呼叫一次、使用單調的 (monotonic) 方式（意思是
，一個 class 可以被 subclassed（子類別化），而不會影響其 parent 的搜尋優
先順序）。總之，這些特性使設計出可靠又可擴充、具有多重繼承的 class 成為
可能。更多資訊，請見 *note The Python 2.3 Method Resolution Order:
1415.。


File: python.info,  Node: 私有變數,  Next: 補充說明,  Prev: 繼承 Inheritance,  Up: Class（類別）

2.9.6 私有變數
--------------

「私有」(private) 實例變數，指的是不在物件內部便無法存取的變數，這在
Python 中是不存在的。但是，大多數 Python 的程式碼都遵守一個慣例：前綴為
一個底線的名稱（如：‘_spam’）應被視為 API （應用程式介面）的非公有
(non-public) 部分（無論它是函式、方法或是資料成員）。這被視為一個實作細
節，如有調整，亦不另行通知。

既然 class 私有的成員已有一個有效的用例（即避免名稱與 subclass 定義的名
稱衝突），這種機制也存在另一個有限的支援，稱為 'name mangling'（名稱修飾
）。任何格式為 ‘__spam’（至少兩個前導下底線，最多一個尾隨下底線）的物件
名稱 (identifier) 會被文本地被替換為 ‘_classname__spam’，在此
‘classname’ 就是去掉前導下底線的當前 class 名稱。只要這個修飾是在 class
的定義之中發生，它就會在不考慮該物件名稱的語法位置的情況下完成。

也參考
......

參閱*note 私有名稱修飾規格: 1bbd.的詳情與特殊情況。

名稱修飾對於讓 subclass 覆寫 method 而不用破壞 class 內部的 method 呼叫
，是有幫助的。舉例來說：

     class Mapping:
         def __init__(self, iterable):
             self.items_list = []
             self.__update(iterable)

         def update(self, iterable):
             for item in iterable:
                 self.items_list.append(item)

         __update = update   # private copy of original update() method

     class MappingSubclass(Mapping):

         def update(self, keys, values):
             # provides new signature for update()
             # but does not break __init__()
             for item in zip(keys, values):
                 self.items_list.append(item)

在上例中，就算在 ‘MappingSubclass’ 當中加入 ‘__update’ 識別符，也能順利
運作，因為在 ‘Mapping’ class 中，它會被替換為 ‘_Mapping__update’，而在
‘MappingSubclass’ class 中，它會被替換為 ‘_MappingSubclass__update’。

請注意，修飾規則是被設計來避免意外；它仍可能存取或修改一個被視為私有的變
數。這在特殊情況下甚至可能很有用，例如在除錯器 (debugger)。

另外也注意，傳遞給 ‘exec()’ 或 ‘eval()’ 的程式碼不會把調用 class 的名稱
視為當前的 class；這和 ‘global’ 陳述式的效果類似，該效果同樣僅限於整體被
位元組編譯後 (byte-compiled) 的程式碼。同樣的限制適用於 ‘getattr()’，
‘setattr()’ 和 ‘delattr()’，以及直接參照 ‘__dict__’ 時。


File: python.info,  Node: 補充說明,  Next: 疊代器 Iterator,  Prev: 私有變數,  Up: Class（類別）

2.9.7 補充說明
--------------

如果有一種資料型別，類似於 Pascal 的「record」或 C 的「struct」，可以將
一些有名稱的資料項目捆綁在一起，有時候這會很有用。符合語言習慣的做法是使
用 *note dataclasses: 27.：

     from dataclasses import dataclass

     @dataclass
     class Employee:
         name: str
         dept: str
         salary: int

     >>> john = Employee('john', 'computer lab', 1000)
     >>> john.dept
     'computer lab'
     >>> john.salary
     1000

用來處理特殊抽象資料型別的一段 Python 程式碼，經常能以傳遞一個 class 來
替代，此 class 模擬該資料型別的多種 method。例如，如果你有一個函式，它會
從一個檔案物件來格式化某些資料，你也可以定義一個有 *note read(): 1b89. 和
*note readline(): 1bc0. method 的 class 作為替代方式，從字串緩衝區取得資
料，並將其作為引數來傳遞。

*note 實例的 method 物件: 1bc1.也具有屬性：*note m.__self__: 1336. 就是
帶有 method ‘m()’ 的實例物件，而 *note m.__func__: 128f. 則是該 method 所
對應的*note 函式物件: 295.。


File: python.info,  Node: 疊代器 Iterator,  Next: 產生器 Generator,  Prev: 補充說明,  Up: Class（類別）

2.9.8 疊代器 (Iterator)
-----------------------

到目前為止，你可能已經注意到大多數的容器 (container) 物件都可以使用
*note for: 2c3. 陳述式來進行迴圈：

     for element in [1, 2, 3]:
         print(element)
     for element in (1, 2, 3):
         print(element)
     for key in {'one':1, 'two':2}:
         print(key)
     for char in "123":
         print(char)
     for line in open("myfile.txt"):
         print(line, end='')

這種存取風格清晰、簡潔且方便。疊代器的使用在 Python 中處處可見且用法一致
。在幕後，*note for: 2c3. 陳述式會在容器物件上呼叫 *note iter(): 77b.。
該函式回傳一個疊代器物件，此物件定義了 *note __next__(): 1260. method，
而此 method 會逐一存取容器中的元素。當元素用盡時，*note __next__():
1260. 將引發 *note StopIteration: ba1. 例外，來通知 ‘for’ 終止迴圈。你可
以使用內建函式 *note next(): 77c. 來呼叫 *note __next__(): 1260. method；
這個例子展示了它的運作方式：

     >>> s = 'abc'
     >>> it = iter(s)
     >>> it
     <str_iterator object at 0x10c90e650>
     >>> next(it)
     'a'
     >>> next(it)
     'b'
     >>> next(it)
     'c'
     >>> next(it)
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
         next(it)
     StopIteration

看過疊代器協定的幕後機制後，在你的 class 加入疊代器的行為就很容易了。定
義一個 *note __iter__(): 1bc4. method 來回傳一個帶有 *note __next__():
1260. method 的物件。如果 class 已定義了 ‘__next__()’，則 ‘__iter__()’ 可
以只回傳 ‘self’：

     class Reverse:
         """Iterator for looping over a sequence backwards."""
         def __init__(self, data):
             self.data = data
             self.index = len(data)

         def __iter__(self):
             return self

         def __next__(self):
             if self.index == 0:
                 raise StopIteration
             self.index = self.index - 1
             return self.data[self.index]

     >>> rev = Reverse('spam')
     >>> iter(rev)
     <__main__.Reverse object at 0x00A1DB50>
     >>> for char in rev:
     ...     print(char)
     ...
     m
     a
     p
     s


File: python.info,  Node: 產生器 Generator,  Next: 產生器運算式,  Prev: 疊代器 Iterator,  Up: Class（類別）

2.9.9 產生器 (Generator)
------------------------

*note 產生器: 1004.是一個用於建立疊代器的簡單而強大的工具。它們的寫法和
常規的函式一樣，但當它們要回傳資料時，會使用 *note yield: 971. 陳述式。
每次在產生器上呼叫 *note next(): 77c. 時，它會從上次離開的位置恢復執行（
它會記得所有資料值以及上一個被執行的陳述式）。以下範例顯示，建立產生器可
以相當地容易：

     def reverse(data):
         for index in range(len(data)-1, -1, -1):
             yield data[index]

     >>> for char in reverse('golf'):
     ...     print(char)
     ...
     f
     l
     o
     g

任何可以用產生器來完成的事，也能用以 class 為基礎的疊代器來完成，如同前
一節的描述。而讓產生器的程式碼更為精簡的原因是，*note __iter__(): 1bc7.
和 *note __next__(): 1bc8. method 會自動被建立。

另一個關鍵的特性在於，區域變數和執行狀態會在每次呼叫之間自動被儲存。這使
得該函式比使用 ‘self.index’ 和 ‘self.data’ 這種實例變數的方式更容易編寫
且更為清晰。

除了會自動建立 method 和儲存程式狀態，當產生器終止時，它們還會自動引發
*note StopIteration: ba1.。這些特性結合在一起，使建立疊代器能與編寫常規
函式一樣容易。


File: python.info,  Node: 產生器運算式,  Prev: 產生器 Generator,  Up: Class（類別）

2.9.10 產生器運算式
-------------------

某些簡單的產生器可以寫成如運算式一般的簡潔程式碼，所用的語法類似 list
comprehension（串列綜合運算），但外層為括號而非方括號。這種運算式被設計
用於產生器將立即被外圍函式 (enclosing function) 所使用的情況。產生器運算
式與完整的產生器定義相比，程式碼較精簡但功能較少，也比等效的 list
comprehension 更為節省記憶體。

例如：

     >>> sum(i*i for i in range(10))                 # sum of squares
     285

     >>> xvec = [10, 20, 30]
     >>> yvec = [7, 5, 3]
     >>> sum(x*y for x,y in zip(xvec, yvec))         # dot product
     260

     >>> unique_words = set(word for line in page  for word in line.split())

     >>> valedictorian = max((student.gpa, student.name) for student in graduates)

     >>> data = 'golf'
     >>> list(data[i] for i in range(len(data)-1, -1, -1))
     ['f', 'l', 'o', 'g']

註解
....


File: python.info,  Node: Python 標準函式庫概覽,  Next: Python 標準函式庫概覽——第二部份,  Prev: Class（類別）,  Up: Python 教學

2.10 Python 標準函式庫概覽
==========================

* Menu:

* 作業系統介面::
* 檔案之萬用字元 (File Wildcards): 檔案之萬用字元 File Wildcards.
* 命令列引數::
* 錯誤輸出重新導向與程式終止::
* 字串樣式比對::
* 數學相關::
* 網路存取::
* 日期與時間::
* 資料壓縮::
* 效能量測::
* 品質控管::
* 標準模組庫::


File: python.info,  Node: 作業系統介面,  Next: 檔案之萬用字元 File Wildcards,  Up: Python 標準函式庫概覽

2.10.1 作業系統介面
-------------------

*note os: 91. 模組提供了數十個與作業系統溝通的函式：

     >>> import os
     >>> os.getcwd()      # Return the current working directory
     'C:\\Python313'
     >>> os.chdir('/server/accesslogs')   # Change current working directory
     >>> os.system('mkdir today')   # Run the command mkdir in the system shell
     0

務必使用 ‘import os’ 而非 ‘from os import *’。這將避免因系統不同而有實作
差異的 *note os.open(): d38. 覆蓋內建函式 *note open(): 4c0.。

在使用 *note os: 91. 諸如此類大型模組時搭配內建函式 *note dir(): 5d8. 和
*note help(): 87c. 是非常有用的：

     >>> import os
     >>> dir(os)
     <returns a list of all module functions>
     >>> help(os)
     <returns an extensive manual page created from the module's docstrings>

對於日常檔案和目錄管理任務，*note shutil: b3. 模組提供了更容易使用的高階
介面：

     >>> import shutil
     >>> shutil.copyfile('data.db', 'archive.db')
     'archive.db'
     >>> shutil.move('/build/executables', 'installdir')
     'installdir'


File: python.info,  Node: 檔案之萬用字元 File Wildcards,  Next: 命令列引數,  Prev: 作業系統介面,  Up: Python 標準函式庫概覽

2.10.2 檔案之萬用字元 (File Wildcards)
--------------------------------------

*note glob: 5a. 模組提供了一函式可以從目錄萬用字元中搜尋並產生檔案列表：

     >>> import glob
     >>> glob.glob('*.py')
     ['primes.py', 'random.py', 'quote.py']


File: python.info,  Node: 命令列引數,  Next: 錯誤輸出重新導向與程式終止,  Prev: 檔案之萬用字元 File Wildcards,  Up: Python 標準函式庫概覽

2.10.3 命令列引數
-----------------

通用工具腳本常需要處理命令列引數。這些引數會以 list（串列）形式存放在
*note sys: c3. 模組的 'argv' 屬性中。例如以下 ‘demo.py’ 檔案：

     # demo.py 檔案
     import sys
     print(sys.argv)

以下是在命令列運行 ‘python demo.py one two three’ 的輸出：

     ['demo.py', 'one', 'two', 'three']

*note argparse: 5. 模組提供了一種更複雜的機制來處理命令列引數。以下腳本
可擷取一個或多個檔案名稱，並可選擇要顯示的行數：

     import argparse

     parser = argparse.ArgumentParser(
         prog='top',
         description='Show top lines from each file')
     parser.add_argument('filenames', nargs='+')
     parser.add_argument('-l', '--lines', type=int, default=10)
     args = parser.parse_args()
     print(args)

當 ‘python top.py --lines=5 alpha.txt beta.txt’ 在命令列執行時，該腳本會
將 ‘args.lines’ 設為 ‘5’，並將 ‘args.filenames’ 設為 ‘['alpha.txt',
'beta.txt']’。


File: python.info,  Node: 錯誤輸出重新導向與程式終止,  Next: 字串樣式比對,  Prev: 命令列引數,  Up: Python 標準函式庫概覽

2.10.4 錯誤輸出重新導向與程式終止
---------------------------------

*note sys: c3. 模組也有 'stdin'，'stdout'，和 'stderr' 等屬性。即使當
'stdout' 被重新導向時，後者 'stderr' 可輸出警告和錯誤訊息：

     >>> sys.stderr.write('Warning, log file not found starting a new one\n')
     Warning, log file not found starting a new one

終止腳本最直接的方式就是利用 ‘sys.exit()’。


File: python.info,  Node: 字串樣式比對,  Next: 數學相關,  Prev: 錯誤輸出重新導向與程式終止,  Up: Python 標準函式庫概覽

2.10.5 字串樣式比對
-------------------

*note re: a7. 模組提供正規表示式 (regular expression) 做進階的字串處理。
當要處理複雜的比對以及操作時，正規表示式是簡潔且經過最佳化的解決方案：

     >>> import re
     >>> re.findall(r'\bf[a-z]*', 'which foot or hand fell fastest')
     ['foot', 'fell', 'fastest']
     >>> re.sub(r'(\b[a-z]+) \1', r'\1', 'cat in the the hat')
     'cat in the hat'

當只需要簡單的字串操作時，因為可讀性以及方便除錯，字串本身的 method 是比
較建議的：

     >>> 'tea for too'.replace('too', 'two')
     'tea for two'


File: python.info,  Node: 數學相關,  Next: 網路存取,  Prev: 字串樣式比對,  Up: Python 標準函式庫概覽

2.10.6 數學相關
---------------

*note math: 81. 模組提供了 C 函式庫中底層的浮點數運算的函式：

     >>> import math
     >>> math.cos(math.pi / 4)
     0.70710678118654757
     >>> math.log(1024, 2)
     10.0

*note random: a6. 模組提供了隨機選擇的工具：

     >>> import random
     >>> random.choice(['apple', 'pear', 'banana'])
     'apple'
     >>> random.sample(range(100), 10)   # sampling without replacement
     [30, 83, 16, 4, 8, 81, 41, 50, 18, 33]
     >>> random.random()    # random float from the interval [0.0, 1.0)
     0.17970987693706186
     >>> random.randrange(6)    # random integer chosen from range(6)
     4

*note statistics: bd. 模組提供了替數值資料計算基本統計量（包括平均、中位
數、變異量數等）的功能：

     >>> import statistics
     >>> data = [2.75, 1.75, 1.25, 0.25, 0.5, 1.25, 3.5]
     >>> statistics.mean(data)
     1.6071428571428572
     >>> statistics.median(data)
     1.25
     >>> statistics.variance(data)
     1.3720238095238095

SciPy 專案 <‘https://scipy.org’> 上也有許多數值計算相關的模組。


File: python.info,  Node: 網路存取,  Next: 日期與時間,  Prev: 數學相關,  Up: Python 標準函式庫概覽

2.10.7 網路存取
---------------

Python 中有許多存取網路以及處理網路協定。最簡單的兩個例子包括 *note
urllib.request: f4. 模組可以從網址抓取資料以及 *note smtplib: b7. 可以用
來寄郵件：

     >>> from urllib.request import urlopen
     >>> with urlopen('http://worldtimeapi.org/api/timezone/etc/UTC.txt') as response:
     ...     for line in response:
     ...         line = line.decode()             # Convert bytes to a str
     ...         if line.startswith('datetime'):
     ...             print(line.rstrip())         # Remove trailing newline
     ...
     datetime: 2022-01-01T01:36:47.689215+00:00

     >>> import smtplib
     >>> server = smtplib.SMTP('localhost')
     >>> server.sendmail('soothsayer@example.org', 'jcaesar@example.org',
     ... """To: jcaesar@example.org
     ... From: soothsayer@example.org
     ...
     ... Beware the Ides of March.
     ... """)
     >>> server.quit()

（注意第二個例子中需要在本地端執行一個郵件伺服器。）


File: python.info,  Node: 日期與時間,  Next: 資料壓縮,  Prev: 網路存取,  Up: Python 標準函式庫概覽

2.10.8 日期與時間
-----------------

*note datetime: 28. 模組提供許多 class 可以操作日期以及時間，從簡單從複
雜都有。模組支援日期與時間的運算，而實作的重點是有效率的成員擷取以達到輸
出格式化以及操作。模組也提供支援時區換算的類別。

     >>> # dates are easily constructed and formatted
     >>> from datetime import date
     >>> now = date.today()
     >>> now
     datetime.date(2003, 12, 2)
     >>> now.strftime("%m-%d-%y. %d %b %Y is a %A on the %d day of %B.")
     '12-02-03. 02 Dec 2003 is a Tuesday on the 02 day of December.'

     >>> # dates support calendar arithmetic
     >>> birthday = date(1964, 7, 31)
     >>> age = now - birthday
     >>> age.days
     14368


File: python.info,  Node: 資料壓縮,  Next: 效能量測,  Prev: 日期與時間,  Up: Python 標準函式庫概覽

2.10.9 資料壓縮
---------------

常見的解壓縮以及壓縮格式都有直接支援的模組。包括：*note zlib: 119.、
*note gzip: 5d.、*note bz2: f.、*note lzma: 7e.、*note zipfile: 117. 以
及 *note tarfile: c8.。

     >>> import zlib
     >>> s = b'witch which has which witches wrist watch'
     >>> len(s)
     41
     >>> t = zlib.compress(s)
     >>> len(t)
     37
     >>> zlib.decompress(t)
     b'witch which has which witches wrist watch'
     >>> zlib.crc32(s)
     226805979


File: python.info,  Node: 效能量測,  Next: 品質控管,  Prev: 資料壓縮,  Up: Python 標準函式庫概覽

2.10.10 效能量測
----------------

有一些 Python 使用者很想了解同個問題的不同實作方法的效能差異。Python 提
供了評估效能差異的工具。

舉例來說，有人可能會試著用 tuple 的打包機制來交換引數代替傳統的方式。
*note timeit: d8. 模組可以迅速地展示效能的進步：

     >>> from timeit import Timer
     >>> Timer('t=a; a=b; b=t', 'a=1; b=2').timeit()
     0.57535828626024577
     >>> Timer('a,b = b,a', 'a=1; b=2').timeit()
     0.54962537085770791

相對於 *note timeit: d8. 模組提供這麼細的粒度，*note profile: 9d. 模組以
及 *note pstats: 9e. 模組則提供了一些在大型的程式碼識別時間使用上關鍵的
區塊 (time critical section) 的工具。


File: python.info,  Node: 品質控管,  Next: 標準模組庫,  Prev: 效能量測,  Up: Python 標準函式庫概覽

2.10.11 品質控管
----------------

達到高品質軟體的一個方法，是在開發時對每個函式寫測試，以及在開發過程中要
不斷地跑這些測試。

*note doctest: 31. 模組提供了一個工具，掃描模組並根據程式中內嵌的文件字
串執行測試。撰寫測試如同簡單地將它的呼叫及輸出結果剪下並貼上到文件字串中
。透過提供範例給使用者，它強化了說明文件，並允許 doctest 模組確認程式碼
的結果與說明文件一致：

     def average(values):
         """Computes the arithmetic mean of a list of numbers.

         >>> print(average([20, 30, 70]))
         40.0
         """
         return sum(values) / len(values)

     import doctest
     doctest.testmod()   # automatically validate the embedded tests

*note unittest: ef. 模組不像 *note doctest: 31. 模組這般容易，但是它讓你
可以在另外一個檔案裡撰寫更完整的測試集：

     import unittest

     class TestStatisticalFunctions(unittest.TestCase):

         def test_average(self):
             self.assertEqual(average([20, 30, 70]), 40.0)
             self.assertEqual(round(average([1, 5, 7]), 1), 4.3)
             with self.assertRaises(ZeroDivisionError):
                 average([])
             with self.assertRaises(TypeError):
                 average(20, 30, 70)

     unittest.main()  # Calling from the command line invokes all tests


File: python.info,  Node: 標準模組庫,  Prev: 品質控管,  Up: Python 標準函式庫概覽

2.10.12 標準模組庫
------------------

"Batteries included" 是 Python 的設計哲學。這個理念可以透過使用它的大型
套件，感受複雜與強大的功能，來得到印證。例如：

   * 使用 *note xmlrpc.client: 114. 和 *note xmlrpc.server: 115. 模組使
     實作遠端程序呼叫變得更為容易。即使模組名稱裡有 XML，使用者並不需要
     直接操作 XML 檔案或事先具備相關知識。

   * 函式庫 *note email: 32. 套件用來管理 MIME 和其他 RFC 2822(1) 相關電
     子郵件訊息的文件。相異於 *note smtplib: b7. 和 *note poplib: 9a. 這
     些實際用來發送與接收訊息的模組，email 套件擁有更完整的工具集，可用
     於建立與解碼複雜訊息結構（包含附件檔案）以及實作編碼與標頭協定。

   * *note json: 76. 套件對 JSON 資料交換格式的剖析，提供強大的支援。
     *note csv: 21. 模組則提供直接讀寫 CSV（以逗號分隔值的檔案格式，通常
     資料庫和電子表格都有支援）。*note xml.etree.ElementTree: 10c.、
     *note xml.dom: 108. 與 *note xml.sax: 110. 套件則支援 XML 的處理。
     綜觀所有，這些模組和套件都簡化了 Python 應用程式與其他工具之間的資
     料交換。

   * ‘sqllite3’ 模組是 SQLite 資料庫函式庫的一層包裝，提供一個具持久性的
     資料庫，可以使用稍微非標準的 SQL 語法來對它進行更新與存取。

   * 有數種支援國際化的模組，包括 *note gettext: 59.、*note locale: 7a.
     和 *note codecs: 14. 等套件。

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2822.html


File: python.info,  Node: Python 標準函式庫概覽——第二部份,  Next: 虛擬環境與套件,  Prev: Python 標準函式庫概覽,  Up: Python 教學

2.11 Python 標準函式庫概覽——第二部份
====================================

第二部分涵蓋更多支援專業程式設計所需要的進階模組。這些模組很少出現在小腳
本中。

* Menu:

* 輸出格式化 (Output Formatting): 輸出格式化 Output Formatting.
* 模板化 (Templating): 模板化 Templating.
* 二進制資料記錄編排 (Binary Data Record Layouts): 二進制資料記錄編排 Binary Data Record Layouts.
* 多執行緒 (Multi-threading): 多執行緒 Multi-threading.
* 日誌記錄 (Logging): 日誌記錄 Logging.
* 弱引用 (Weak References): 弱引用 Weak References.
* 使用於 List 的工具::
* 十進制浮點數運算 (Decimal Floating-Point Arithmetic): 十進制浮點數運算 Decimal Floating-Point Arithmetic.


File: python.info,  Node: 輸出格式化 Output Formatting,  Next: 模板化 Templating,  Up: Python 標準函式庫概覽——第二部份

2.11.1 輸出格式化 (Output Formatting)
-------------------------------------

*note reprlib: a9. 模組提供了一個 *note repr(): 7a1. 的版本，專門用來以
簡短的形式顯示大型或深層的巢狀容器：

     >>> import reprlib
     >>> reprlib.repr(set('supercalifragilisticexpialidocious'))
     "{'a', 'c', 'd', 'e', 'f', 'g', ...}"

*note pprint: 9c. 模組能對內建和使用者自定的物件提供更複雜的列印控制，並
且是以直譯器可讀的方式。當結果超過一行時，「漂亮的印表機」會加入換行和縮
排，以更清楚地顯示資料結構：

     >>> import pprint
     >>> t = [[[['black', 'cyan'], 'white', ['green', 'red']], [['magenta',
     ...     'yellow'], 'blue']]]
     ...
     >>> pprint.pprint(t, width=30)
     [[[['black', 'cyan'],
        'white',
        ['green', 'red']],
       [['magenta', 'yellow'],
        'blue']]]

*note textwrap: d5. 模組能夠格式化文本的段落，以符合指定的螢幕寬度：

     >>> import textwrap
     >>> doc = """The wrap() method is just like fill() except that it returns
     ... a list of strings instead of one big string with newlines to separate
     ... the wrapped lines."""
     ...
     >>> print(textwrap.fill(doc, width=40))
     The wrap() method is just like fill()
     except that it returns a list of strings
     instead of one big string with newlines
     to separate the wrapped lines.

*note locale: 7a. 模組能存取一個含有特定文化相關資料格式的資料庫。locale
模組的 format 函式有一個 grouping 屬性，可直接以群分隔符 (group
separator) 將數字格式化：

     >>> import locale
     >>> locale.setlocale(locale.LC_ALL, 'English_United States.1252')
     'English_United States.1252'
     >>> conv = locale.localeconv()          # get a mapping of conventions
     >>> x = 1234567.8
     >>> locale.format_string("%d", x, grouping=True)
     '1,234,567'
     >>> locale.format_string("%s%.*f", (conv['currency_symbol'],
     ...                      conv['frac_digits'], x), grouping=True)
     '$1,234,567.80'


File: python.info,  Node: 模板化 Templating,  Next: 二進制資料記錄編排 Binary Data Record Layouts,  Prev: 輸出格式化 Output Formatting,  Up: Python 標準函式庫概覽——第二部份

2.11.2 模板化 (Templating)
--------------------------

*note string: be. 模組包含一個多功能的 *note Template: 62d. class，提供
的簡化語法適合使用者進行編輯時使用。它容許使用者客製化自己的應用程式，但
不必對原應用程式做出變更。

格式化方式是使用佔位符號名稱 (placeholder name)，它是由 ‘$’ 加上合法的
Python 識別符（字母、數字和下底線）構成。使用大括號包覆佔位符號以允許在
後面接上更多的字母和數字而無需插入空格。使用 ‘$$’ 將會跳脫為單一字元
‘$’：

     >>> from string import Template
     >>> t = Template('${village}folk send $$10 to $cause.')
     >>> t.substitute(village='Nottingham', cause='the ditch fund')
     'Nottinghamfolk send $10 to the ditch fund.'

如果在 dictionary 或關鍵字引數中未提供某個佔位符號的值，那麼 *note
substitute(): 1bed. method 將引發 *note KeyError: 2fb.。對於郵件合併
(mail-merge) 類型的應用程式，使用者提供的資料有可能是不完整的，此時使用
*note safe_substitute(): 1bee. method 會更適當——如果資料有缺少，它會保持
佔位符號不變：

     >>> t = Template('Return the $item to $owner.')
     >>> d = dict(item='unladen swallow')
     >>> t.substitute(d)
     Traceback (most recent call last):
       ...
     KeyError: 'owner'
     >>> t.safe_substitute(d)
     'Return the unladen swallow to $owner.'

Template 的 subclass（子類別）可以指定自訂的分隔符號 (delimiter)。例如，
一個相片瀏覽器的批次重新命名功能，可以選擇用百分號作為現在日期、照片序號
或檔案格式的佔位符號：

     >>> import time, os.path
     >>> photofiles = ['img_1074.jpg', 'img_1076.jpg', 'img_1077.jpg']
     >>> class BatchRename(Template):
     ...     delimiter = '%'
     ...
     >>> fmt = input('Enter rename style (%d-date %n-seqnum %f-format):  ')
     Enter rename style (%d-date %n-seqnum %f-format):  Ashley_%n%f

     >>> t = BatchRename(fmt)
     >>> date = time.strftime('%d%b%y')
     >>> for i, filename in enumerate(photofiles):
     ...     base, ext = os.path.splitext(filename)
     ...     newname = t.substitute(d=date, n=i, f=ext)
     ...     print('{0} --> {1}'.format(filename, newname))

     img_1074.jpg --> Ashley_0.jpg
     img_1076.jpg --> Ashley_1.jpg
     img_1077.jpg --> Ashley_2.jpg

模板化的另一個應用，是將程式邏輯與多樣的輸出格式細節分離開來。這樣就可以
為 XML 檔案、純文字報表和 HTML 網路報表替換自訂的模板。


File: python.info,  Node: 二進制資料記錄編排 Binary Data Record Layouts,  Next: 多執行緒 Multi-threading,  Prev: 模板化 Templating,  Up: Python 標準函式庫概覽——第二部份

2.11.3 二進制資料記錄編排 (Binary Data Record Layouts)
------------------------------------------------------

*note struct: c0. 模組提供了 *note pack(): 120f. 和 *note unpack():
16cb. 函式，用於處理可變動長度的二進制記錄格式。以下範例說明，如何在不使
用 *note zipfile: 117. 模組的情況下，使用迴圈瀏覽一個 ZIP 檔案中的標頭資
訊 (header information)。壓縮程式碼 ‘"H"’ 和 ‘"I"’ 分別代表兩個和四個位
元組的無符號數 (unsigned number)。‘"<"’ 表示它們是標準大小，並使用小端
(little-endian) 位元組順序：

     import struct

     with open('myfile.zip', 'rb') as f:
         data = f.read()

     start = 0
     for i in range(3):                      # show the first 3 file headers
         start += 14
         fields = struct.unpack('<IIIHH', data[start:start+16])
         crc32, comp_size, uncomp_size, filenamesize, extra_size = fields

         start += 16
         filename = data[start:start+filenamesize]
         start += filenamesize
         extra = data[start:start+extra_size]
         print(filename, hex(crc32), comp_size, uncomp_size)

         start += extra_size + comp_size     # skip to the next header


File: python.info,  Node: 多執行緒 Multi-threading,  Next: 日誌記錄 Logging,  Prev: 二進制資料記錄編排 Binary Data Record Layouts,  Up: Python 標準函式庫概覽——第二部份

2.11.4 多執行緒 (Multi-threading)
---------------------------------

執行緒是一種用來對非順序相依 (sequentially dependent) 的多個任務進行解耦
(decoupling) 的技術。當其他任務在背景執行時，多執行緒可以用來提升應用程
式在接收使用者輸入時的反應能力。一個相關的用例是，運行 I/O 的同時，在另
一個執行緒中進行計算。

以下程式碼顯示了高階的 *note threading: d6. 模組如何在背景運行任務，而主
程式同時繼續運行：

     import threading, zipfile

     class AsyncZip(threading.Thread):
         def __init__(self, infile, outfile):
             threading.Thread.__init__(self)
             self.infile = infile
             self.outfile = outfile

         def run(self):
             f = zipfile.ZipFile(self.outfile, 'w', zipfile.ZIP_DEFLATED)
             f.write(self.infile)
             f.close()
             print('Finished background zip of:', self.infile)

     background = AsyncZip('mydata.txt', 'myarchive.zip')
     background.start()
     print('The main program continues to run in foreground.')

     background.join()    # 等待背景任務結束
     print('Main program waited until background was done.')

多執行緒應用程式的主要挑戰是，要協調多個彼此共享資料或資源的執行緒。為此
，threading 模組提供了多個同步處理原始物件 (synchronization primitive)，
包括鎖 (lock)、事件 (event)、條件變數 (condition variable) 和號誌
(semaphore)。

儘管這些工具很強大，但很小的設計錯誤也可能導致一些難以重現的問題。所以，
任務協調的首選方法是，把所有對資源的存取集中到單一的執行緒中，然後使用
*note queue: a4. 模組向該執行緒饋送來自其他執行緒的請求。應用程式若使用
*note Queue: 131c. 物件進行執行緒間的通信和協調，會更易於設計、更易讀、
更可靠。


File: python.info,  Node: 日誌記錄 Logging,  Next: 弱引用 Weak References,  Prev: 多執行緒 Multi-threading,  Up: Python 標準函式庫概覽——第二部份

2.11.5 日誌記錄 (Logging)
-------------------------

*note logging: 7b. 模組提供功能齊全且富彈性的日誌記錄系統。在最簡單的情
況下，日誌訊息會被發送到檔案或 ‘sys.stderr’：

     import logging
     logging.debug('Debugging information')
     logging.info('Informational message')
     logging.warning('Warning:config file %s not found', 'server.conf')
     logging.error('Error occurred')
     logging.critical('Critical error -- shutting down')

這會產生以下輸出：

     WARNING:root:Warning:config file server.conf not found
     ERROR:root:Error occurred
     CRITICAL:root:Critical error -- shutting down

在預設情況，資訊和除錯訊息不會被顯示，其輸出會被發送到標準錯誤 (standard
error)。其他輸出選項包括，將訊息轉發到電子郵件、資料報 (datagram)、網路
插座 (socket) 或 HTTP 伺服器。新的過濾器可以根據訊息的優先順序，選擇不同
的路由 (routing) 方式：*note DEBUG: 1bf5.、*note INFO: 1bf6.、*note
WARNING: 1bf7.、*note ERROR: 1bf8. 及 *note CRITICAL: 1bf9.。

日誌記錄系統可以直接從 Python 配置，也可以透過載入使用者可編輯的配置檔案
以進行客製化的日誌記錄，而無須對應用程式做出變更。


File: python.info,  Node: 弱引用 Weak References,  Next: 使用於 List 的工具,  Prev: 日誌記錄 Logging,  Up: Python 標準函式庫概覽——第二部份

2.11.6 弱引用 (Weak References)
-------------------------------

Python 會自動進行記憶體管理（對大多數物件進行參照計數 (reference
counting) 並使用 *note garbage collection: 181c. 來消除循環參照）。當一
個參照從記憶體被移除後不久，該記憶體就會被釋出。

此方式對大多數應用程式來說都沒問題，但偶爾也需要在物件仍然被其他物件所使
用時持續追蹤它們。可惜的是，儘管只是追蹤它們，也會建立一個使它們永久化
(permanent) 的參照。*note weakref: fc. 模組提供的工具可以不必建立參照就
能追蹤物件。當該物件不再被需要時，它會自動從一個弱引用表 (weakref table)
中被移除，並為弱引用物件觸發一個回呼 (callback)。典型的應用包括暫存
(cache) 那些成本較為昂貴的物件：

     >>> import weakref, gc
     >>> class A:
     ...     def __init__(self, value):
     ...         self.value = value
     ...     def __repr__(self):
     ...         return str(self.value)
     ...
     >>> a = A(10)                   # create a reference
     >>> d = weakref.WeakValueDictionary()
     >>> d['primary'] = a            # does not create a reference
     >>> d['primary']                # fetch the object if it is still alive
     10
     >>> del a                       # remove the one reference
     >>> gc.collect()                # run garbage collection right away
     0
     >>> d['primary']                # entry was automatically removed
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
         d['primary']                # entry was automatically removed
       File "C:/python313/lib/weakref.py", line 46, in __getitem__
         o = self.data[key]()
     KeyError: 'primary'


File: python.info,  Node: 使用於 List 的工具,  Next: 十進制浮點數運算 Decimal Floating-Point Arithmetic,  Prev: 弱引用 Weak References,  Up: Python 標準函式庫概覽——第二部份

2.11.7 使用於 List 的工具
-------------------------

許多對於資料結構的需求，可以透過內建的 list（串列）型別來滿足。但是，有
時也會根據效能的各種取捨，需要一些替代的實作。

*note array: 6. 模組提供了一個 *note array: 186. 物件，它像是 list，但只
能儲存同類的資料且能緊密地儲存。下面的範例展示一個數值陣列 (array)，以兩
個位元組的無符號二進數 (unsigned binary numbers) 為儲存單位（類型碼為
‘"H"’），而在 Python 整數物件的正規 list 中，每個項目通常使用 16 個位元
組：

     >>> from array import array
     >>> a = array('H', [4000, 10, 700, 22222])
     >>> sum(a)
     26932
     >>> a[1:3]
     array('H', [10, 700])

*note collections: 16. 模組提供了一個 *note deque: 580. 物件，它像是
list，但從左側加入 (append) 和彈出 (pop) 的速度較快，而在中間查找的速度
則較慢。這種物件適用於實作佇列 (queue) 和廣度優先搜尋法 (breadth first
tree search)：

     >>> from collections import deque
     >>> d = deque(["task1", "task2", "task3"])
     >>> d.append("task4")
     >>> print("Handling", d.popleft())
     Handling task1

     unsearched = deque([starting_node])
     def breadth_first_search(unsearched):
         node = unsearched.popleft()
         for m in gen_moves(node):
             if is_goal(m):
                 return m
             unsearched.append(m)

除了替代的 list 實作以外，函式庫也提供了其他工具，例如 *note bisect: d.
模組，具有能夠操作 sorted list（已排序串列）的函式：

     >>> import bisect
     >>> scores = [(100, 'perl'), (200, 'tcl'), (400, 'lua'), (500, 'python')]
     >>> bisect.insort(scores, (300, 'ruby'))
     >>> scores
     [(100, 'perl'), (200, 'tcl'), (300, 'ruby'), (400, 'lua'), (500, 'python')]

*note heapq: 5f. 模組提供了一些函式，能基於正規 list 來實作堆積 (heap)。
最小值的項目會永遠保持在位置零。對於一些需要多次存取最小元素，但不想要對
整個 list 進行排序的應用程式來說，這會很有用：

     >>> from heapq import heapify, heappop, heappush
     >>> data = [1, 3, 5, 7, 9, 2, 4, 6, 8, 0]
     >>> heapify(data)                      # rearrange the list into heap order
     >>> heappush(data, -5)                 # add a new entry
     >>> [heappop(data) for i in range(3)]  # fetch the three smallest entries
     [-5, 0, 1]


File: python.info,  Node: 十進制浮點數運算 Decimal Floating-Point Arithmetic,  Prev: 使用於 List 的工具,  Up: Python 標準函式庫概覽——第二部份

2.11.8 十進制浮點數運算 (Decimal Floating-Point Arithmetic)
-----------------------------------------------------------

*note decimal: 2e. 模組提供了一個 *note Decimal: 27c. 資料類型，用於十進
制浮點數運算。相較於內建的二進制浮點數 *note float: 2c8. 實作，該 class
特別適用於下列情境

   * 金融應用程式及其他需要準確十進位制表示法的應用，

   * 對於精確度 (precision) 的控制，

   * 控制四捨五入，以滿足法律或監管規範，

   * 追蹤有效的小數位數 (decimal place)，或

   * 使用者會期望計算結果與手工計算相符的應用程式。

例如，要計算 70 美分的手機充電加上 5％ 稅金的總價，使用十進制浮點數和二
進制浮點數，會算出不同的答案。如果把計算結果四捨五入到最接近的美分，兩者
的差異會更顯著：

     >>> from decimal import *
     >>> round(Decimal('0.70') * Decimal('1.05'), 2)
     Decimal('0.74')
     >>> round(.70 * 1.05, 2)
     0.73

*note Decimal: 27c. 的運算結果會保留尾部的零，也會根據有兩個有效位數的被
乘數自動推斷出有四個有效位數的乘積。Decimal 可以重現手工計算的結果，以避
免產生二進制浮點數無法準確表示十進制數值時會導致的問題。

準確的表示法使得 *note Decimal: 27c. class 能夠執行對於二進制浮點數不適
用的模數計算和相等性檢測：

     >>> Decimal('1.00') % Decimal('.10')
     Decimal('0.00')
     >>> 1.00 % 0.10
     0.09999999999999995

     >>> sum([Decimal('0.1')]*10) == Decimal('1.0')
     True
     >>> 0.1 + 0.1 + 0.1 + 0.1 + 0.1 + 0.1 + 0.1 + 0.1 + 0.1 + 0.1 == 1.0
     False

*note decimal: 2e. 模組可提供運算中需要的足夠精確度：

     >>> getcontext().prec = 36
     >>> Decimal(1) / Decimal(7)
     Decimal('0.142857142857142857142857142857142857')


File: python.info,  Node: 虛擬環境與套件,  Next: 現在可以來學習些什麼？,  Prev: Python 標準函式庫概覽——第二部份,  Up: Python 教學

2.12 虛擬環境與套件
===================

* Menu:

* 簡介: 簡介<4>.
* 建立虛擬環境::
* 用 pip 管理套件::


File: python.info,  Node: 簡介<4>,  Next: 建立虛擬環境,  Up: 虛擬環境與套件

2.12.1 簡介
-----------

Python 應用程式通常會用到不在標準函式庫的套件和模組。應用程式有時候會需
要某個特定版本的函式庫，因為這個應用程式可能需要某個特殊的臭蟲修正，或是
這個應用程式是根據該函式庫特定版本的介面所撰寫。

這意味著不太可能安裝一套 Python 就可以滿足所有應用程式的要求。如果應用程
式 A 需要一個特定的模組的 1.0 版，但另外一個應用程式 B 需要 2.0 版，那麼
這整個需求不管安裝 1.0 或是 2.0 都會衝突，以致於應用程式無法使用。

解決方案是建立一個*note 虛擬環境 (virtual environment): 1c04.，這是一個
獨立的資料夾，並且裡面裝好了特定版本的 Python，以及一系列相關的套件。

不同的應用程式可以使用不同的虛擬環境。以前述中需要被解決的例子中，應用程
式 A 能夠擁有它自己的虛擬環境，並且是裝好 1.0 版，然而應用程式 B 則可以
是用另外一個有 2.0 版的虛擬環境。要是應用程式 B 需要某個函式庫被升級到
3.0 版，這並不會影響到應用程式 A 的環境。


File: python.info,  Node: 建立虛擬環境,  Next: 用 pip 管理套件,  Prev: 簡介<4>,  Up: 虛擬環境與套件

2.12.2 建立虛擬環境
-------------------

用來建立與管理虛擬環境的模組叫做 *note venv: f9.。*note venv: f9. 將安裝
執行命令的 Python 版本（如 *note -version: cc2. 選項所報告的）。例如使用
‘python3.12’ 執行命令將安裝 3.12 版本。

在建立虛擬環境的時候，在你決定要放該虛擬環境的資料夾之後，以腳本
(script) 執行 *note venv: f9. 模組並且給定資料夾路徑：

     python -m venv tutorial-env

如果 ‘tutorial-env’ 不存在的話，這會建立 ‘tutorial-env’ 資料夾，並且也會
在裡面建立一個有 Python 直譯器的複本以及不同的支援檔案的資料夾。

虛擬環境的常用資料夾位置是 ‘.venv’。這個名稱通常會使該資料夾在你的 shell
中保持隱藏，因此這樣命名既可以解釋資料夾存在的原因，也不會造成任何困擾。
它還能防止與某些工具所支援的 ‘.env’ 環境變數定義檔案發生衝突。

一旦你建立了一個虛擬環境，你可以啟動它。

在 Windows 系統中，使用：

     tutorial-env\Scripts\activate

在 Unix 或 MacOS 系統，使用：

     source tutorial-env/bin/activate

（這段程式碼適用於 bash shell。如果你是用 ‘csh’ 或者 ‘fish’ shell，應當
使用替代的 ‘activate.csh’ 與 ‘activate.fish’ 腳本。）

啟動虛擬環境會改變你的 shell 提示字元來顯示你正在使用的虛擬環境，並且修
改環境以讓你在執行 ‘python’ 的時候可以得到特定的 Python 版本，例如：

     $ source ~/envs/tutorial-env/bin/activate
     (tutorial-env) $ python
     Python 3.5.1 (default, May  6 2016, 10:59:36)
       ...
     >>> import sys
     >>> sys.path
     ['', '/usr/local/lib/python35.zip', ...,
     '~/envs/tutorial-env/lib/python3.5/site-packages']
     >>>

要停用虛擬環境，輸入：

     deactivate

於終端機中。


File: python.info,  Node: 用 pip 管理套件,  Prev: 建立虛擬環境,  Up: 虛擬環境與套件

2.12.3 用 pip 管理套件
----------------------

你可以使用一個叫做 ‘pip’ 的程式來安裝、升級和移除套件。‘pip’ 預設會從
Python Package Index(1) 安裝套件。你可以透過你的網頁瀏覽器瀏覽 Python
Package Index。

‘pip’ 有好幾個子命令："install"、"uninstall"、"freeze" 等等。（可以參考
*note 安裝 Python 模組: e99.指南，來取得 ‘pip’ 的完整說明文件。）

你可以透過指定套件名字來安裝最新版本的套件：

     (tutorial-env) $ python -m pip install novas
     Collecting novas
       Downloading novas-3.1.1.3.tar.gz (136kB)
     Installing collected packages: novas
       Running setup.py install for novas
     Successfully installed novas-3.1.1.3

你也可以透過在套件名稱之後接上 ‘==’ 和版號來指定特定版本：

     (tutorial-env) $ python -m pip install requests==2.6.0
     Collecting requests==2.6.0
       Using cached requests-2.6.0-py2.py3-none-any.whl
     Installing collected packages: requests
     Successfully installed requests-2.6.0

要是你重新執行此命令，‘pip’ 會知道該版本已經安裝過，然後什麼也不做。你可
以提供不同的版本號碼來取得該版本，或是可以執行 ‘python -m pip install
--upgrade’ 來把套件升級到最新的版本：

     (tutorial-env) $ python -m pip install --upgrade requests
     Collecting requests
     Installing collected packages: requests
       Found existing installation: requests 2.6.0
         Uninstalling requests-2.6.0:
           Successfully uninstalled requests-2.6.0
     Successfully installed requests-2.7.0

‘python -m pip uninstall’ 後面接一個或是多個套件名稱可以從虛擬環境中移除
套件。

‘python -m pip show’ 可以顯示一個特定套件的資訊：

     (tutorial-env) $ python -m pip show requests
     ---
     Metadata-Version: 2.0
     Name: requests
     Version: 2.7.0
     Summary: Python HTTP for Humans.
     Home-page: http://python-requests.org
     Author: Kenneth Reitz
     Author-email: me@kennethreitz.com
     License: Apache 2.0
     Location: /Users/akuchling/envs/tutorial-env/lib/python3.4/site-packages
     Requires:

‘python -m pip list’ 會顯示虛擬環境中所有已經安裝的套件：

     (tutorial-env) $ python -m pip list
     novas (3.1.1.3)
     numpy (1.9.2)
     pip (7.0.3)
     requests (2.7.0)
     setuptools (16.0)

‘python -m pip freeze’ 可以複製一整個已經安裝的套件清單，但是輸出使用
‘python -m pip install’ 可以讀懂的格式。一個常見的慣例是放這整個清單到一
個叫做 ‘requirements.txt’ 的檔案：

     (tutorial-env) $ python -m pip freeze > requirements.txt
     (tutorial-env) $ cat requirements.txt
     novas==3.1.1.3
     numpy==1.9.2
     requests==2.7.0

‘requirements.txt’ 可以提交到版本控制，並且作為釋出應用程式的一部分。使
用者可以透過 ‘install -r’ 安裝對應的的套件：

     (tutorial-env) $ python -m pip install -r requirements.txt
     Collecting novas==3.1.1.3 (from -r requirements.txt (line 1))
       ...
     Collecting numpy==1.9.2 (from -r requirements.txt (line 2))
       ...
     Collecting requests==2.7.0 (from -r requirements.txt (line 3))
       ...
     Installing collected packages: novas, numpy, requests
       Running setup.py install for novas
     Successfully installed novas-3.1.1.3 numpy-1.9.2 requests-2.7.0

‘pip’ 還有更多功能。可以參考*note 安裝 Python 模組: e99.指南，來取得完整
的 ‘pip’ 說明文件。當你撰寫了一個套件並且想要讓它在 Python Package Index
上可以取得的話，可以參考 Python packaging user guide(2)。

   ---------- Footnotes ----------

   (1) https://pypi.org

   (2) 
https://packaging.python.org/en/latest/tutorials/packaging-projects/


File: python.info,  Node: 現在可以來學習些什麼？,  Next: 互動式輸入編輯和歷史記錄替換,  Prev: 虛擬環境與套件,  Up: Python 教學

2.13 現在可以來學習些什麼？
===========================

閱讀本教學可能增強你對於使用 Python 的興趣——你應該非常渴望使用 Python 來
解決在現實生活中所遭遇的問題。該從哪裡學習更多呢？

本教學是 Python 文件中的一部分。這份文件集裡頭的其他文件包含：

   * *note Python 標準函式庫 (Standard Library): 12a.：

     你該好好的瀏覽這份手冊，它提供了完整（但簡潔）的參考素材像是型別、
     函式與標準函式庫裡的模組。標準的 Python 發行版本會包含'大量'的附加
     程式碼。有些模組可以讀取 Unix 信箱、通過 HTTP 來檢索文件、產生亂數
     、分析命令列選項、壓縮資料、及許多其他任務。瀏覽函式庫參考手冊可以
     讓你了解有哪些模組可以用。

   * *note 安裝 Python 模組: e99.：說明與解釋如何安裝其他 Python 使用者
     所編寫的模組。

   * *note Python 語言參考手冊: 12b.：Python 語法以及語意的詳細說明。這
     份文件閱讀起來會有些吃力，但作為一個語言本身的完整指南是非常有用的
     。

更多 Python 的資源：

   * ‘https://www.python.org’：Python 的主要網站。它包含程式碼、文件以及
     連結到 Python 相關聯的網頁。

   * ‘https://docs.python.org’：快速訪問 Python 的文件。

   * ‘https://pypi.org’：Python 套件索引 (Python Package Index)，之前也
     被暱稱為 Cheese Shop (1)，彙總了使用者開發 Python 模組的索引，並提
     供模組能夠被下載。一旦開始發佈相關程式碼，你可以將開發的作品註冊到
     這裡並且讓其他人找到。

   * ‘https://code.activestate.com/recipes/langs/python/’：Python
     Cookbook 是一個相當大的程式碼集，包含程式碼範例、較大的模組以及有用
     的腳本。特別值得注意的貢獻則被收集在一本名為 Python Cookbook
     (O'Reilly & Associates, ISBN 0-596-00797-3.)  的書籍中。

   * ‘https://pyvideo.org’ 從研討會與使用者群組聚會裡收集與 Python 相關
     的影片連結。

   * ‘https://scipy.org’：The Scientific Python 專案是一個包含用於高速陣
     列運算與操作的模組，以及用於如線性代數、傅利葉變換、非線性求解器、
     隨機數分佈、統計分析等一系列的套件。

對於 Python 相關的疑問與問題回報，你可以張貼到新聞群組
‘comp.lang.python’，或將它們寄至 <python-list@python.org> 的郵寄清單
(mailing list)。新聞群組和郵寄清單是個閘道，因此張貼到其中的郵件都將自動
轉發給另一個。每天會有數以百計的內容，詢問（和回答）問題、建議新功能與發
佈新的模組。郵寄清單會存檔在 ‘https://mail.python.org/pipermail/’。

在張貼之前，請先確認問題是否在*note 常見問題: 1c0a.（也被稱為 FAQ）這個
清單內。FAQ 會回答出現很多次的問題及解答，有很多問題甚至已經包含解決問題
的方法。

註解
....

   ---------- Footnotes ----------

   (1) 「Cheese Shop（起司店）」是 Monty Python 的一個短劇：一位顧客進入
一家起司店，但無論他要哪種起司，店員都說沒有貨。


File: python.info,  Node: 互動式輸入編輯和歷史記錄替換,  Next: 浮點數運算：問題與限制,  Prev: 現在可以來學習些什麼？,  Up: Python 教學

2.14 互動式輸入編輯和歷史記錄替換
=================================

有些版本的 Python 直譯器支援當前輸入內容的編輯和歷史記錄的替換 (history
substitution)，類似在 Korn shell 和 GNU Bash shell 中的功能。這個功能是
用 GNU Readline(1) 函式庫來實作，它支援多種編輯的風格。這個函式庫有它自
己的說明文件，在這裡我們就不重複了。

* Menu:

* Tab 鍵自動完成 (Tab Completion) 和歷史記錄編輯 (History Editing): Tab 鍵自動完成 Tab Completion 和歷史記錄編輯 History Editing.
* 互動式直譯器的替代方案::

   ---------- Footnotes ----------

   (1) https://tiswww.case.edu/php/chet/readline/rltop.html


File: python.info,  Node: Tab 鍵自動完成 Tab Completion 和歷史記錄編輯 History Editing,  Next: 互動式直譯器的替代方案,  Up: 互動式輸入編輯和歷史記錄替換

2.14.1 Tab 鍵自動完成 (Tab Completion) 和歷史記錄編輯 (History Editing)
-----------------------------------------------------------------------

在直譯器啟動的時候，變數和模組名稱的自動完成功能會被*note 自動啟用:
f6c.，所以可以用 ‘Tab’ 鍵來呼叫自動完成函式；它會查看 Python 的陳述式名
稱、當前區域變數名稱和可用模組名稱。對於像是 ‘string.a’ 的點分隔運算式
(dotted expression)，它會對最後一個 ‘'.'’ 之前的運算式求值，然後根據求值
結果物件的屬性，給予自動完成的建議。請注意，如果一個物件有 *note
__getattr__(): 47a. method（方法），同時又是該運算式的一部份，這樣可能會
執行應用程式自定義的程式碼。預設設定也會把你的指令歷史記錄儲存在你的使用
者資料夾內，一個名為 ‘.python_history’ 的檔案中。在下一次啟動互動式直譯
器時，這些歷史記錄依然可以被使用。


File: python.info,  Node: 互動式直譯器的替代方案,  Prev: Tab 鍵自動完成 Tab Completion 和歷史記錄編輯 History Editing,  Up: 互動式輸入編輯和歷史記錄替換

2.14.2 互動式直譯器的替代方案
-----------------------------

與早期版本的直譯器相比，上述功能的出現的確是一個巨大的進步；但還是有一些
願望沒有被實現：如果能在每次換行時給予適當的縮排建議（剖析器 (parser) 知
道下一行是否需要縮排標記 (indent token)），那就更棒了。自動完成機制可能
會使用直譯器的符號表。若有一個命令能夠檢查（或甚至建議）括號、引號和其他
符號的匹配，那也會很有用。

有一個功能增強的互動式直譯器替代方案，已經存在一段時間，稱為 IPython(1)，
它具有 Tab 鍵自動完成、物件探索和進階歷史記錄管理等特色。它也可以完全客
製化並被嵌入到其他應用程式中。另一個類似的增強型互動式環境，稱為
bpython(2)。

   ---------- Footnotes ----------

   (1) https://ipython.org/

   (2) https://bpython-interpreter.org/


File: python.info,  Node: 浮點數運算：問題與限制,  Next: 附錄,  Prev: 互動式輸入編輯和歷史記錄替換,  Up: Python 教學

2.15 浮點數運算：問題與限制
===========================

在計算機架構中，浮點數 (floating-point number) 是以基數為 2（二進位）的
小數表示。例如說，在'十進位'小數中 ‘0.625’ 可被分為 6/10 + 2/100 +
5/1000，同樣的道理，'二進位'小數 ‘0.101’ 可被分為 1/2 + 0/4 + 1/8。這兩
個小數有相同的數值，而唯一真正的不同在於前者以十進位表示，後者以二進位表
示。

不幸的是，大多數十進位小數無法精準地以二進位小數表示。一般的結果為，你輸
入的十進位浮點數只能由實際儲存在計算機中的二進位浮點數近似。

在十進位中，這個問題更容易被理解。以分數 1/3 為例，你可以將其近似為十進
位小數：

     0.3

或者，更好的近似：

     0.33

或者，更好的近似：

     0.333

依此類推，不論你使用多少位數表示小數，最後的結果都無法精準地表示 1/3，但
你還是能越來越精準地表示 1/3。

同樣的道理，不論你願意以多少位數表示二進位小數，十進位小數 0.1 都無法被
二進位小數精準地表達。在二進位小數中，1/10 會是一個無限循環小數：

     0.0001100110011001100110011001100110011001100110011...

只要你停在任何有限的位數，你就只會得到近似值。而現在大多數的計算機中，浮
點數是透過二進位分數近似的，其中分子是從最高有效位元開始，用 53 個位元表
示，分母則是以二為底的指數。在 1/10 的例子中，二進位分數為
‘3602879701896397 / 2 ** 55’，而這樣的表示十分地接近，但不完全等同於
1/10 的真正數值。

由於數值顯示的方式，很多使用者並沒有發現數值是個近似值。Python 只會印出
一個十進位近似值，其近似了儲存在計算機中的二進位近似值的真正十進位數值。
在大多數的計算機中，如果 Python 真的會印出完整的十進位數值，其表示儲存在
計算機中的 0.1 的二進位近似值，它將顯示為：

     >>> 0.1
     0.1000000000000000055511151231257827021181583404541015625

這比一般人感到有用的位數還多，所以 Python 將位數保持在可以接受的範圍，只
顯示捨入後的數值：

     >>> 1 / 10
     0.1

一定要記住，雖然印出的數字看起來是精準的 1/10，但真正儲存的數值是能表示
的二進位分數中，最接近精準數值的數。

有趣的是，有許多不同的十進位數，共用同一個最接近的二進位近似分數。例如說
：數字 ‘0.1’ 和 ‘0.10000000000000001’ 和
‘0.1000000000000000055511151231257827021181583404541015625’，都由
‘3602879701896397 / 2 ** 55’ 近似。由於這三個十進位數值共用同一個近似值
，任何一個數值都可以被顯示，同時保持 ‘eval(repr(x)) == x’。

歷史上，Python 的提示字元 (prompt) 與內建的 *note repr(): 7a1. 函式會選
擇上段說明中有 17 個有效位元的數：‘0.10000000000000001’。從 Python 3.1 版
開始，Python（在大部分的系統上）現在能選擇其中最短的數並簡單地顯示為
‘0.1’。

注意，這是二進位浮點數理所當然的特性，並不是 Python 的錯誤 (bug)，更不是
你程式碼的錯誤。只要程式語言有支援硬體的浮點數運算，你將會看到同樣的事情
出現在其中（雖然有些程式語言預設不會'顯示'該差異，有些甚至是在所有的輸出
模式中都不會顯示。）

為求更優雅的輸出，你可能想要使用字串的格式化 (string formatting) 產生限
定的有效位數：

     >>> format(math.pi, '.12g')  # give 12 significant digits
     '3.14159265359'

     >>> format(math.pi, '.2f')   # give 2 digits after the point
     '3.14'

     >>> repr(math.pi)
     '3.141592653589793'

要了解一件很重要的事，在真正意義上，浮點數的表示是一種幻覺：你基本上在捨
入真正機器數值所'展示的值'。

這種幻覺可能會產生下一個幻覺。舉例來說，因為 0.1 不是真正的 1/10，把三個
0.1 的值相加，也不會產生精準的 0.3：

     >>> 0.1 + 0.1 + 0.1 == 0.3
     False

同時，因為 0.1 不能再更接近精準的 1/10，還有 0.3 不能再更接近精準的
3/10，預先用 *note round(): 126d. 函式捨入並不會有幫助：

     >>> round(0.1, 1) + round(0.1, 1) + round(0.1, 1) == round(0.3, 1)
     False

雖然數字不會再更接近他們的精準數值，但 *note math.isclose(): d56. 函式可
以用來比較不精確的值：

     >>> math.isclose(0.1 + 0.1 + 0.1, 0.3)
     True

或者，可以使用 *note round(): 126d. 函式來比較粗略的近似值：

     >>> round(math.pi, ndigits=2) == round(22 / 7, ndigits=2)
     True

二進位浮點數架構下還有很多這樣的意外。底下的「表示法誤差 (Representation
Error)」章節，詳細地解釋了「0.1」的問題。Examples of Floating Point
Problems（浮點數問題範例）(1)一文提供了二進位浮點數的作用方式與現實中這
類常見問題的摘錄。如果想要其他常見問題的更完整描述，可以參考 The Perils
of Floating Point（浮點數的風險）(2)。

如同上文的末段所述，「這個問題並沒有簡單的答案。」不過，也不必對浮點過度
擔心！Python 的 float（浮點數）運算中的誤差，是從浮點硬體繼承而來，而在
大多數的計算機上，每次運算的誤差範圍不會大於 2**53 分之 1。這對大多數的
任務來說已經相當足夠，但你需要記住，它並非十進位運算，且每一次 float 運
算都可能會承受新的捨入誤差。

雖然浮點運算確實存在一些問題，但在一般情況下，如果你只是把最終結果的顯示
值，以十進位方式捨入至預期的位數，那麼仍會得到你預期的結果。*note str():
3f2. 通常就能滿足要求，而若想要更細緻的控制，可參閱*note 格式化文字語法:
131e.中關於 *note str.format(): 5c7. method（方法）的格式規範。

對於需要精準十進位表示法的用例，可以試著用 *note decimal: 2e. 模組，它可
實作適用於會計應用程式與高精確度應用程式的十進位運算。

另一種支援精準運算的格式為 *note fractions: 53. 模組，該模組基於有理數來
實作運算（因此可以精確表示像 1/3 這樣的數字）。

如果你是浮點運算的重度使用者，你應該看一下 NumPy 套件，以及由 SciPy 專案
提供的許多用於數學和統計學運算的其他套件。請參閱 <‘https://scipy.org’>。

在罕見情況下，當你'真的'想知道一個 float 的精準值，Python 提供的工具可協
助達成。*note float.as_integer_ratio(): 1c14. method 可將一個 float 的值
表示為分數：

     >>> x = 3.14159
     >>> x.as_integer_ratio()
     (3537115888337719, 1125899906842624)

由於該比率是精準的，它可無損地再現該原始值：

     >>> x == 3537115888337719 / 1125899906842624
     True

*note float.hex(): 1c15. method 以十六進位（基數為 16）表示 float，一樣
可以給出你的電腦所儲存的精準值：

     >>> x.hex()
     '0x1.921f9f01b866ep+1'

這種精確的十六進位表示法可用於精準地重建 float 值：

     >>> x == float.fromhex('0x1.921f9f01b866ep+1')
     True

由於該表示法是精準的，因此適用於在不同版本的 Python 之間可靠地傳送數值（
獨立於系統平台），並與支援相同格式的其他語言（如 JAVA 和 C99）交換資料。

另一個有用的工具是 *note sum(): 411. 函式，能在計算總和時幫忙減少精確度
的損失。當數值被加到運行中的總計值時，它會追蹤「失去的位數 (lost
digits)」。這可以明顯改善總體準確度 (overall accuracy)，使得誤差不至於累
積到影響最終總計值的程度：

     >>> 0.1 + 0.1 + 0.1 + 0.1 + 0.1 + 0.1 + 0.1 + 0.1 + 0.1 + 0.1 == 1.0
     False
     >>> sum([0.1] * 10) == 1.0
     True

*note math.fsum(): 1342. 更進一步將數值被加到運行總計中的總計時追蹤所有
「失去的位數」，以便結果僅有一次捨入。這比 *note sum(): 411. 慢，但在不
常見的情況下會更準確，在這種情況下，大量輸入大多相互抵消，最終的總和會接
近於零：

     >>> arr = [-0.10430216751806065, -266310978.67179024, 143401161448607.16,
     ...        -143401161400469.7, 266262841.31058735, -0.003244936839808227]
     >>> float(sum(map(Fraction, arr)))   # Exact summation with single rounding
     8.042173697819788e-13
     >>> math.fsum(arr)                   # Single rounding
     8.042173697819788e-13
     >>> sum(arr)                         # Multiple roundings in extended precision
     8.042178034628478e-13
     >>> total = 0.0
     >>> for x in arr:
     ...     total += x                   # Multiple roundings in standard precision
     ...
     >>> total                            # Straight addition has no correct digits!
     -0.0051575902860057365

* Menu:

* 表示法誤差 (Representation Error): 表示法誤差 Representation Error.

   ---------- Footnotes ----------

   (1) 
https://jvns.ca/blog/2023/01/13/examples-of-floating-point-problems/

   (2) http://www.indowsway.com/floatingpoint.htm


File: python.info,  Node: 表示法誤差 Representation Error,  Up: 浮點數運算：問題與限制

2.15.1 表示法誤差 (Representation Error)
----------------------------------------

本節將會詳細解釋「0.1」的例子，並說明你自己要如何對類似案例執行精準的分
析。 以下假設你對二進位浮點表示法已有基本程度的熟悉。

'Representation error'（表示法誤差）是指在真實情況中，有些（實際上是大多
數）十進位小數並不能精準地以二進位（基數為 2）小數表示。這是 Python（或
Perl、C、C++、JAVA、Fortran 和其他許多）通常不會顯示你期望的精準十進位數
字的主要原因。

為什麼呢？因為 1/10 無法精準地以一個二進位小數來表示。至少自從 2000 年以
來，幾乎所有的計算機皆使用 IEEE-754 浮點數運算標準，並且幾乎所有的平台都
以 IEEE 754 binary64 標準中的「雙精度 (double precision)」來作為 Python
的 float。IEEE 754 binary64 的值包含 53 位元的精度，所以在輸入時，電腦會
努力把 0.1 轉換到最接近的分數，以 'J'/2**'N' 的形式表示，此處 'J' 是一個
正好包含 53 位元的整數。可以將：

     1 / 10 ~= J / (2**N)

重寫為：

     J ~= 2**N / 10

而前面提到 'J' 有精準的 53 位元（即 ‘>= 2**52’ 但 ‘< 2**53’），所以 'N'
的最佳數值是 56：

     >>> 2**52 <=  2**56 // 10  < 2**53
     True

意即，要使 'J' 正好有 53 位元，則 56 會是 'N' 的唯一值。而 'J' 最有可能
的數值就是經過捨入後的該商數：

     >>> q, r = divmod(2**56, 10)
     >>> r
     6

由於餘數超過 10 的一半，所以最佳的近似值是透過進位而得：

     >>> q+1
     7205759403792794

所以，在 IEEE 754 雙精度下，1/10 的最佳近似值是：

     7205759403792794 / 2 ** 56

將分子和分母同除以二，會約分為：

     3602879701896397 / 2 ** 55

請注意，由於我們有進位，所以這實際上比 1/10 大了一點；如果我們沒有進位，
商數將會有點小於 1/10。但在任何情況下都不可能是'精準的' 1/10！

所以電腦從來沒有「看到」1/10：它看到的是上述的精準分數，也就是它能得到的
IEEE 754 double 最佳近似值：

     >>> 0.1 * 2 ** 55
     3602879701896397.0

如果將該分數乘以 10**55，則可以看到該值以 55 個十進位數字顯示：

     >>> 3602879701896397 * 10 ** 55 // 2 ** 55
     1000000000000000055511151231257827021181583404541015625

這表示儲存在電腦中的精準數值等於十進位值
0.1000000000000000055511151231257827021181583404541015625。與其顯示完整
的十進位數值，許多語言（包括 Python 的舊版本）選擇將結果捨入至 17 個有效
位數：

     >>> format(0.1, '.17f')
     '0.10000000000000001'

*note fractions: 53. 與 *note decimal: 2e. 模組能使這些計算變得容易：

     >>> from decimal import Decimal
     >>> from fractions import Fraction

     >>> Fraction.from_float(0.1)
     Fraction(3602879701896397, 36028797018963968)

     >>> (0.1).as_integer_ratio()
     (3602879701896397, 36028797018963968)

     >>> Decimal.from_float(0.1)
     Decimal('0.1000000000000000055511151231257827021181583404541015625')

     >>> format(Decimal.from_float(0.1), '.17')
     '0.10000000000000001'


File: python.info,  Node: 附錄,  Prev: 浮點數運算：問題與限制,  Up: Python 教學

2.16 附錄
=========

* Menu:

* 互動模式: 互動模式<2>.


File: python.info,  Node: 互動模式<2>,  Up: 附錄

2.16.1 互動模式
---------------

There are two variants of the interactive *note REPL: 14e.  The classic
basic interpreter is supported on all platforms with minimal line
control capabilities.

On Windows, or Unix-like systems with *note curses: 23. support, a new
interactive shell is used by default.  This one supports color,
multiline editing, history browsing, and paste mode.  To disable color,
see *note Controlling color: 14f. for details.  Function keys provide
some additional functionality.  ‘F1’ enters the interactive help browser
*note pydoc: a3.  ‘F2’ allows for browsing command-line history without
output nor the *note >>>: 150. and *note ...: 151. prompts.  ‘F3’ enters
"paste mode", which makes pasting larger blocks of code easier.  Press
‘F3’ to return to the regular prompt.

When using the new interactive shell, exit the shell by typing ‘exit’ or
‘quit’.  Adding call parentheses after those commands is not required.

If the new interactive shell is not desired, it can be disabled via the
*note PYTHON_BASIC_REPL: 152. environment variable.

* Menu:

* 錯誤處理::
* 可執行的 Python 腳本::
* 互動式啟動檔案::
* 客製化模組::


File: python.info,  Node: 錯誤處理,  Next: 可執行的 Python 腳本,  Up: 互動模式<2>

2.16.1.1 錯誤處理
.................

當一個錯誤發生時，直譯器會印出一個錯誤訊息和堆疊回溯。在互動模式下，它將
返回主提示字元；當輸入來自檔案時，它在印出堆疊回溯後以非零退出狀態
(nonzero exit status) 退出。 (由 *note except: 171. 子句在 *note try:
68c. 陳述式中處理的例外在這種情況下不是錯誤。) 有些錯誤是無條件嚴重的，
會導致非零退出狀態；這適用於內部不一致和一些記憶體耗盡的情況。所有的錯誤
訊息都被寫入標準錯誤輸出；被執行指令的正常輸出被寫入標準輸出。

向主提示字元或次提示字元輸入中斷字元（通常是 ‘Control-C’ 或 ‘Delete’ ）
會取消輸入並返回到主提示字元。 (1) 在指令執行過程中輸入一個中斷，會引發
*note KeyboardInterrupt: 975. 例外，但可以通過 *note try: 68c. 陳述式來
處理。

   ---------- Footnotes ----------

   (1) GNU Readline 套件的一個問題可能會阻止這一點。


File: python.info,  Node: 可執行的 Python 腳本,  Next: 互動式啟動檔案,  Prev: 錯誤處理,  Up: 互動模式<2>

2.16.1.2 可執行的 Python 腳本
.............................

在類 BSD 的 Unix 系統上，Python 腳本可以直接執行，就像 shell 腳本一樣，
通過放置以下這行：

     #!/usr/bin/env python3

（假設直譯器在用戶的 ‘PATH’ 上）在腳本的開頭並給檔案一個可執行模式。
‘#!’ 必須是檔案的前兩個字元。 在某些平台上，第一行必須以 Unix 樣式的換行
(‘'\n'’) 結尾，而不是 Windows (‘'\r\n'’) 換行。 請注意，井號 ‘'#'’ 用於
在 Python 中開始註解。

可以使用 ‘chmod’ 指令為腳本賦予可執行模式或權限。

     $ chmod +x myscript.py

在 Windows 系統上，沒有「可執行模式」的概念。 Python 安裝程式會自動將
‘.py’ 檔案與 ‘python.exe’ 聯繫起來，這樣雙擊 Python 檔案就會作為腳本運行
。副檔名也可以是 ‘.pyw’，在這種情況下，通常會出現的控制台視窗會被隱藏。


File: python.info,  Node: 互動式啟動檔案,  Next: 客製化模組,  Prev: 可執行的 Python 腳本,  Up: 互動模式<2>

2.16.1.3 互動式啟動檔案
.......................

當你互動式地使用 Python 時，每次啟動直譯器時執行一些標準指令是非常方便的
。你可以通過設置一個名為 *note PYTHONSTARTUP: f6b. 的環境變數來實現，該
變數是一個包含啟動指令的檔案名。它的功能類似 Unix shell 的 ‘.profile’ 。

這個檔案只在互動模式中被讀取，當 Python 從腳本中讀取指令時，此檔案不會被
讀取，當 ‘/dev/tty’ 作為指令的明確來源時也不會（否則表現得像互動模式）。
它在執行互動式指令的同一命名空間中執行，因此它所定義或 import 的物件可以
在互動模式中不加限定地使用。你也可以在這個檔案中改變 ‘sys.ps1’ 和
‘sys.ps2’ 等提示字元。

如果你想從當前目錄中讀取一個額外的啟動檔案，你可以在全域啟動檔案中使用類
似 ‘if os.path.isfile('.pythonrc.py'): exec(open('.pythonrc.py').read()’
的程式碼設定這個行為。如果你想在一個腳本中使用啟動檔案，你必須在腳本中明
確地這樣做：

     import os
     filename = os.environ.get('PYTHONSTARTUP')
     if filename and os.path.isfile(filename):
         with open(filename) as fobj:
             startup_file = fobj.read()
         exec(startup_file)


File: python.info,  Node: 客製化模組,  Prev: 互動式啟動檔案,  Up: 互動模式<2>

2.16.1.4 客製化模組
...................

Python 提供了兩個鉤子 (hook) 讓你可以將它客製化： sitecustomize 和
usercustomize 。要看它是如何運作的，你首先需要找到你的 site-packages 的
位置。啟動 Python 並運行這段程式碼：

     >>> import site
     >>> site.getusersitepackages()
     '/home/user/.local/lib/python3.x/site-packages'

現在，你可以在該目錄中建立一個名為 ‘usercustomize.py’ 的檔案，並將你想要
的任何內容放入其中。它會影響 Python 的每次呼叫，除非它以 *note -s: 1319.
選項啟動以禁用自動 import 。

sitecustomize 的運作方式相同，但通常是由電腦的管理員在全域 site-packages
目錄下建立，並在 usercustomize 之前 import 。更多細節請參閱 *note site:
b5. 模組的文件。

註解
....


File: python.info,  Node: Python 的設置與使用,  Next: Python 語言參考手冊,  Prev: Python 教學,  Up: Top

3 Python 的設置與使用
*********************

這部分的說明文件是關於在不同平台上設定 Python 環境的綜合資訊、直譯器的呼
叫，以及讓 Python 更容易使用的一些方法。

* Menu:

* 命令列與環境::
* 在 Unix 平臺上使用 Python::
* 配置 Python::
* 在 Windows 上使用 Python::
* 在 Mac 系統使用 Python::
* Using Python on iOS::
* 編輯器與 IDE::


File: python.info,  Node: 命令列與環境,  Next: 在 Unix 平臺上使用 Python,  Up: Python 的設置與使用

3.1 命令列與環境
================

The CPython interpreter scans the command line and the environment for
various settings.

'CPython 實作細節：' Other implementations' command line schemes may
differ.  See *note Alternate Implementations: 1c28. for further
resources.

* Menu:

* 命令列::
* 環境變數::


File: python.info,  Node: 命令列,  Next: 環境變數,  Up: 命令列與環境

3.1.1 命令列
------------

When invoking Python, you may specify any of these options:

     python [-bBdEhiIOPqRsSuvVWx?] [-c command | -m module-name | script | - ] [args]

The most common use case is, of course, a simple invocation of a script:

     python myscript.py

* Menu:

* 介面選項::
* Generic options::
* Miscellaneous options::
* Controlling color::
* 你不該使用的選項::


File: python.info,  Node: 介面選項,  Next: Generic options,  Up: 命令列

3.1.1.1 介面選項
................

The interpreter interface resembles that of the UNIX shell, but provides
some additional methods of invocation:

   * When called with standard input connected to a tty device, it
     prompts for commands and executes them until an EOF (an end-of-file
     character, you can produce that with ‘Ctrl-D’ on UNIX or ‘Ctrl-Z,
     Enter’ on Windows) is read.  For more on interactive mode, see
     *note 互動模式: 153.

   * When called with a file name argument or with a file as standard
     input, it reads and executes a script from that file.

   * When called with a directory name argument, it reads and executes
     an appropriately named script from that directory.

   * When called with ‘-c command’, it executes the Python statement(s)
     given as 'command'.  Here 'command' may contain multiple statements
     separated by newlines.  Leading whitespace is significant in Python
     statements!

   * When called with ‘-m module-name’, the given module is located on
     the Python module path and executed as a script.

In non-interactive mode, the entire input is parsed before it is
executed.

An interface option terminates the list of options consumed by the
interpreter, all consecutive arguments will end up in *note sys.argv:
11fd. - note that the first element, subscript zero (‘sys.argv[0]’), is
a string reflecting the program's source.

 -- Option: -c <command>

     Execute the Python code in 'command'.  'command' can be one or more
     statements separated by newlines, with significant leading
     whitespace as in normal module code.

     If this option is given, the first element of *note sys.argv: 11fd.
     will be ‘"-c"’ and the current directory will be added to the start
     of *note sys.path: 37f. (allowing modules in that directory to be
     imported as top level modules).

     引發一個附帶引數 ‘command’ 的*note 稽核事件: 17bd.
     ‘cpython.run_command’。

 -- Option: -m <module-name>

     Search *note sys.path: 37f. for the named module and execute its
     contents as the *note __main__: 1. module.

     Since the argument is a 'module' name, you must not give a file
     extension (‘.py’).  The module name should be a valid absolute
     Python module name, but the implementation may not always enforce
     this (e.g.  it may allow you to use a name that includes a hyphen).

     Package names (including namespace packages) are also permitted.
     When a package name is supplied instead of a normal module, the
     interpreter will execute ‘<pkg>.__main__’ as the main module.  This
     behaviour is deliberately similar to the handling of directories
     and zipfiles that are passed to the interpreter as the script
     argument.

          備註: This option cannot be used with built-in modules and
          extension modules written in C, since they do not have Python
          module files.  However, it can still be used for precompiled
          modules, even if the original source file is not available.

     If this option is given, the first element of *note sys.argv: 11fd.
     will be the full path to the module file (while the module file is
     being located, the first element will be set to ‘"-m"’).  As with
     the *note -c: 584. option, the current directory will be added to
     the start of *note sys.path: 37f.

     *note -I: 902. option can be used to run the script in isolated
     mode where *note sys.path: 37f. contains neither the current
     directory nor the user's site-packages directory.  All ‘PYTHON*’
     environment variables are ignored, too.

     Many standard library modules contain code that is invoked on their
     execution as a script.  An example is the *note timeit: d8. module:

          python -m timeit -s "setup here" "benchmarked code here"
          python -m timeit -h # for details

     引發一個附帶引數 ‘module-name’ 的*note 稽核事件: 17bd.
     ‘cpython.run_module’。

     也參考
     ......

     *note runpy.run_module(): 1711.

          Equivalent functionality directly available to Python code

     PEP 338(1) - Executing modules as scripts

     在 3.1 版的變更: Supply the package name to run a ‘__main__’
     submodule.

     在 3.4 版的變更: namespace packages are also supported

 -- Describe: -

     Read commands from standard input (*note sys.stdin: 4e2.).  If
     standard input is a terminal, *note -i: 144a. is implied.

     If this option is given, the first element of *note sys.argv: 11fd.
     will be ‘"-"’ and the current directory will be added to the start
     of *note sys.path: 37f.

     引發一個不附帶引數的*note 稽核事件: 17bd. ‘cpython.run_stdin’。

 -- Describe: <script>

     Execute the Python code contained in 'script', which must be a
     filesystem path (absolute or relative) referring to either a Python
     file, a directory containing a ‘__main__.py’ file, or a zipfile
     containing a ‘__main__.py’ file.

     If this option is given, the first element of *note sys.argv: 11fd.
     will be the script name as given on the command line.

     If the script name refers directly to a Python file, the directory
     containing that file is added to the start of *note sys.path: 37f,
     and the file is executed as the *note __main__: 1. module.

     If the script name refers to a directory or zipfile, the script
     name is added to the start of *note sys.path: 37f. and the
     ‘__main__.py’ file in that location is executed as the *note
     __main__: 1. module.

     *note -I: 902. option can be used to run the script in isolated
     mode where *note sys.path: 37f. contains neither the script's
     directory nor the user's site-packages directory.  All ‘PYTHON*’
     environment variables are ignored, too.

     引發一個附帶引數 ‘filename’ 的*note 稽核事件: 17bd.
     ‘cpython.run_file’。

     也參考
     ......

     *note runpy.run_path(): 164.

          Equivalent functionality directly available to Python code

If no interface option is given, *note -i: 144a. is implied,
‘sys.argv[0]’ is an empty string (‘""’) and the current directory will
be added to the start of *note sys.path: 37f.  Also, tab-completion and
history editing is automatically enabled, if available on your platform
(see *note Readline configuration: f6c.).

也參考
......

*note 啟動直譯器: 1aeb.

在 3.4 版的變更: Automatic enabling of tab-completion and history
editing.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0338/


File: python.info,  Node: Generic options,  Next: Miscellaneous options,  Prev: 介面選項,  Up: 命令列

3.1.1.2 Generic options
.......................

 -- Option: -?
 -- Option: -h
 -- Option: --help

     Print a short description of all command line options and
     corresponding environment variables and exit.

 -- Option: --help-env

     Print a short description of Python-specific environment variables
     and exit.

     在 3.11 版被加入.

 -- Option: --help-xoptions

     Print a description of implementation-specific *note -X: 15a.
     options and exit.

     在 3.11 版被加入.

 -- Option: --help-all

     印出完整使用資訊並離開。

     在 3.11 版被加入.

 -- Option: -V
 -- Option: --version

     Print the Python version number and exit.  Example output could be:

          Python 3.8.0b2+

     When given twice, print more information about the build, like:

          Python 3.8.0b2+ (3.8:0c076caaa8, Apr 20 2019, 21:55:00)
          [GCC 6.2.0 20161005]

     在 3.6 版被加入: ‘-VV’ 選項


File: python.info,  Node: Miscellaneous options,  Next: Controlling color,  Prev: Generic options,  Up: 命令列

3.1.1.3 Miscellaneous options
.............................

 -- Option: -b

     Issue a warning when converting *note bytes: 1a5. or *note
     bytearray: 4e3. to *note str: 3f2. without specifying encoding or
     comparing ‘bytes’ or ‘bytearray’ with ‘str’ or ‘bytes’ with *note
     int: 23c.  Issue an error when the option is given twice (‘-bb’).

     在 3.5 版的變更: Affects also comparisons of *note bytes: 1a5. with
     *note int: 23c.

 -- Option: -B

     If given, Python won't try to write ‘.pyc’ files on the import of
     source modules.  See also *note PYTHONDONTWRITEBYTECODE: 133c.

 -- Option: --check-hash-based-pycs default|always|never

     Control the validation behavior of hash-based ‘.pyc’ files.  See
     *note Cached bytecode invalidation: 590.  When set to ‘default’,
     checked and unchecked hash-based bytecode cache files are validated
     according to their default semantics.  When set to ‘always’, all
     hash-based ‘.pyc’ files, whether checked or unchecked, are
     validated against their corresponding source file.  When set to
     ‘never’, hash-based ‘.pyc’ files are not validated against their
     corresponding source files.

     The semantics of timestamp-based ‘.pyc’ files are unaffected by
     this option.

 -- Option: -d

     Turn on parser debugging output (for expert only).  See also the
     *note PYTHONDEBUG: 1c34. environment variable.

     This option requires a *note debug build of Python: 1de, otherwise
     it's ignored.

 -- Option: -E

     Ignore all ‘PYTHON*’ environment variables, e.g.  *note PYTHONPATH:
     fbe. and *note PYTHONHOME: 387, that might be set.

     另請參閱 *note -P: 548. 和 *note -I: 902. (isolated) 選項。

 -- Option: -i

     When a script is passed as first argument or the *note -c: 584.
     option is used, enter interactive mode after executing the script
     or the command, even when *note sys.stdin: 4e2. does not appear to
     be a terminal.  The *note PYTHONSTARTUP: f6b. file is not read.

     This can be useful to inspect global variables or a stack trace
     when a script raises an exception.  See also *note PYTHONINSPECT:
     1449.

 -- Option: -I

     Run Python in isolated mode.  This also implies *note -E: 901,
     *note -P: 548. and *note -s: 1319. options.

     In isolated mode *note sys.path: 37f. contains neither the script's
     directory nor the user's site-packages directory.  All ‘PYTHON*’
     environment variables are ignored, too.  Further restrictions may
     be imposed to prevent the user from injecting malicious code.

     在 3.4 版被加入.

 -- Option: -O

     Remove assert statements and any code conditional on the value of
     *note __debug__: 77e.  Augment the filename for compiled (*note
     bytecode: 16d.) files by adding ‘.opt-1’ before the ‘.pyc’
     extension (see PEP 488(1)).  See also *note PYTHONOPTIMIZE: 1c35.

     在 3.5 版的變更: 根據 PEP 488(2) 修改 ‘.pyc’ 檔案名稱。

 -- Option: -OO

     Do *note -O: d5b. and also discard docstrings.  Augment the
     filename for compiled (*note bytecode: 16d.) files by adding
     ‘.opt-2’ before the ‘.pyc’ extension (see PEP 488(3)).

     在 3.5 版的變更: 根據 PEP 488(4) 修改 ‘.pyc’ 檔案名稱。

 -- Option: -P

     Don't prepend a potentially unsafe path to *note sys.path: 37f.:

        * ‘python -m module’ command line: Don't prepend the current
          working directory.

        * ‘python script.py’ command line: Don't prepend the script's
          directory.  If it's a symbolic link, resolve symbolic links.

        * ‘python -c code’ and ‘python’ (REPL) command lines: Don't
          prepend an empty string, which means the current working
          directory.

     See also the *note PYTHONSAFEPATH: 549. environment variable, and
     *note -E: 901. and *note -I: 902. (isolated) options.

     在 3.11 版被加入.

 -- Option: -q

     Don't display the copyright and version messages even in
     interactive mode.

     在 3.2 版被加入.

 -- Option: -R

     Turn on hash randomization.  This option only has an effect if the
     *note PYTHONHASHSEED: 101e. environment variable is set to ‘0’,
     since hash randomization is enabled by default.

     On previous versions of Python, this option turns on hash
     randomization, so that the *note __hash__(): a9e. values of str and
     bytes objects are "salted" with an unpredictable random value.
     Although they remain constant within an individual Python process,
     they are not predictable between repeated invocations of Python.

     Hash randomization is intended to provide protection against a
     denial-of-service caused by carefully chosen inputs that exploit
     the worst case performance of a dict construction, 'O'('n'^2)
     complexity.  See ‘http://ocert.org/advisories/ocert-2011-003.html’
     for details.

     *note PYTHONHASHSEED: 101e. allows you to set a fixed value for the
     hash seed secret.

     在 3.2.3 版被加入.

     在 3.7 版的變更: The option is no longer ignored.

 -- Option: -s

     Don't add the *note user site-packages directory: 1c37. to *note
     sys.path: 37f.

     另請參閱 *note PYTHONNOUSERSITE: 131a.。

     也參考
     ......

     PEP 370(5) - Per user site-packages directory

 -- Option: -S

     Disable the import of the module *note site: b5. and the
     site-dependent manipulations of *note sys.path: 37f. that it
     entails.  Also disable these manipulations if *note site: b5. is
     explicitly imported later (call *note site.main(): 1c38. if you
     want them to be triggered).

 -- Option: -u

     Force the stdout and stderr streams to be unbuffered.  This option
     has no effect on the stdin stream.

     另請參閱 *note PYTHONUNBUFFERED: 18a9.。

     在 3.7 版的變更: The text layer of the stdout and stderr streams
     now is unbuffered.

 -- Option: -v

     Print a message each time a module is initialized, showing the
     place (filename or built-in module) from which it is loaded.  When
     given twice (‘-vv’), print a message for each file that is checked
     for when searching for a module.  Also provides information on
     module cleanup at exit.

     在 3.10 版的變更: The *note site: b5. module reports the
     site-specific paths and ‘.pth’ files being processed.

     另請參閱 *note PYTHONVERBOSE: 1c39.。

 -- Option: -W arg

     Warning control.  Python's warning machinery by default prints
     warning messages to *note sys.stderr: 8dd.

     The simplest settings apply a particular action unconditionally to
     all warnings emitted by a process (even those that are otherwise
     ignored by default):

          -Wdefault  # Warn once per call location
          -Werror    # Convert to exceptions
          -Walways   # Warn every time
          -Wall      # Same as -Walways
          -Wmodule   # Warn once per calling module
          -Wonce     # Warn once per Python process
          -Wignore   # Never warn

     The action names can be abbreviated as desired and the interpreter
     will resolve them to the appropriate action name.  For example,
     ‘-Wi’ is the same as ‘-Wignore’.

     完整的引數形式為：

          action:message:category:module:lineno

     Empty fields match all values; trailing empty fields may be
     omitted.  For example ‘-W ignore::DeprecationWarning’ ignores all
     DeprecationWarning warnings.

     The 'action' field is as explained above but only applies to
     warnings that match the remaining fields.

     The 'message' field must match the whole warning message; this
     match is case-insensitive.

     The 'category' field matches the warning category (ex:
     ‘DeprecationWarning’).  This must be a class name; the match test
     whether the actual warning category of the message is a subclass of
     the specified warning category.

     The 'module' field matches the (fully qualified) module name; this
     match is case-sensitive.

     The 'lineno' field matches the line number, where zero matches all
     line numbers and is thus equivalent to an omitted line number.

     Multiple *note -W: 86c. options can be given; when a warning
     matches more than one option, the action for the last matching
     option is performed.  Invalid *note -W: 86c. options are ignored
     (though, a warning message is printed about invalid options when
     the first warning is issued).

     Warnings can also be controlled using the *note PYTHONWARNINGS:
     b51. environment variable and from within a Python program using
     the *note warnings: fa. module.  For example, the *note
     warnings.filterwarnings(): 1414. function can be used to use a
     regular expression on the warning message.

     See *note The Warnings Filter: 86e. and *note Describing Warning
     Filters: 1c3b. for more details.

 -- Option: -x

     Skip the first line of the source, allowing use of non-Unix forms
     of ‘#!cmd’.  This is intended for a DOS specific hack only.

 -- Option: -X

     Reserved for various implementation-specific options.  CPython
     currently defines the following possible values:

        * ‘-X faulthandler’ to enable *note faulthandler: 4e.  See also
          *note PYTHONFAULTHANDLER: 1021.

          在 3.3 版被加入.

        * ‘-X showrefcount’ to output the total reference count and
          number of used memory blocks when the program finishes or
          after each statement in the interactive interpreter.  This
          only works on *note debug builds: 1de.

          在 3.4 版被加入.

        * ‘-X tracemalloc’ to start tracing Python memory allocations
          using the *note tracemalloc: e8. module.  By default, only the
          most recent frame is stored in a traceback of a trace.  Use
          ‘-X tracemalloc=NFRAME’ to start tracing with a traceback
          limit of 'NFRAME' frames.  See *note tracemalloc.start():
          1c3d. and *note PYTHONTRACEMALLOC: 1c3e. for more information.

          在 3.4 版被加入.

        * ‘-X int_max_str_digits’ configures the *note integer string
          conversion length limitation: 599.  See also *note
          PYTHONINTMAXSTRDIGITS: 16c0.

          在 3.11 版被加入.

        * ‘-X importtime’ to show how long each import takes.  It shows
          module name, cumulative time (including nested imports) and
          self time (excluding nested imports).  Note that its output
          may be broken in multi-threaded application.  Typical usage is
          ‘python3 -X importtime -c 'import asyncio'’.  See also *note
          PYTHONPROFILEIMPORTTIME: a98.

          在 3.7 版被加入.

        * ‘-X dev’: enable *note Python Development Mode: 1dd,
          introducing additional runtime checks that are too expensive
          to be enabled by default.  See also *note PYTHONDEVMODE: a90.

          在 3.7 版被加入.

        * ‘-X utf8’ enables the *note Python UTF-8 Mode: 5fc.  ‘-X
          utf8=0’ explicitly disables *note Python UTF-8 Mode: 5fc.
          (even when it would otherwise activate automatically).  See
          also *note PYTHONUTF8: a7b.

          在 3.7 版被加入.

        * ‘-X pycache_prefix=PATH’ enables writing ‘.pyc’ files to a
          parallel tree rooted at the given directory instead of to the
          code tree.  See also *note PYTHONPYCACHEPREFIX: 947.

          在 3.8 版被加入.

        * ‘-X warn_default_encoding’ issues a *note EncodingWarning:
          1c3f. when the locale-specific default encoding is used for
          opening files.  See also *note PYTHONWARNDEFAULTENCODING: 760.

          在 3.10 版被加入.

        * ‘-X no_debug_ranges’ disables the inclusion of the tables
          mapping extra location information (end line, start column
          offset and end column offset) to every instruction in code
          objects.  This is useful when smaller code objects and pyc
          files are desired as well as suppressing the extra visual
          location indicators when the interpreter displays tracebacks.
          See also *note PYTHONNODEBUGRANGES: 55a.

          在 3.11 版被加入.

        * ‘-X frozen_modules’ determines whether or not frozen modules
          are ignored by the import machinery.  A value of ‘on’ means
          they get imported and ‘off’ means they are ignored.  The
          default is ‘on’ if this is an installed Python (the normal
          case).  If it's under development (running from the source
          tree) then the default is ‘off’.  Note that the
          ‘importlib_bootstrap’ and ‘importlib_bootstrap_external’
          frozen modules are always used, even if this flag is set to
          ‘off’.  See also *note PYTHON_FROZEN_MODULES: 174.

          在 3.11 版被加入.

        * ‘-X perf’ enables support for the Linux ‘perf’ profiler.  When
          this option is provided, the ‘perf’ profiler will be able to
          report Python calls.  This option is only available on some
          platforms and will do nothing if is not supported on the
          current system.  The default value is "off".  See also *note
          PYTHONPERFSUPPORT: 415. and *note Python 對 Linux perf
          分析器的支援: 175.

          在 3.12 版被加入.

        * ‘-X perf_jit’ enables support for the Linux ‘perf’ profiler
          with DWARF support.  When this option is provided, the ‘perf’
          profiler will be able to report Python calls using DWARF
          information.  This option is only available on some platforms
          and will do nothing if is not supported on the current system.
          The default value is "off".  See also *note
          PYTHON_PERF_JIT_SUPPORT: 176. and *note Python 對 Linux perf
          分析器的支援: 175.

          在 3.13 版被加入.

        * ‘-X cpu_count=N’ overrides *note os.cpu_count(): 1a8, *note
          os.process_cpu_count(): 1a7, and *note
          multiprocessing.cpu_count(): f12.  'n' must be greater than or
          equal to 1.  This option may be useful for users who need to
          limit CPU resources of a container system.  See also *note
          PYTHON_CPU_COUNT: 1f5.  If 'n' is ‘default’, nothing is
          overridden.

          在 3.13 版被加入.

        * ‘-X presite=PACKAGE.MODULE’ specifies a module that should be
          imported before the *note site: b5. module is executed and
          before the *note __main__: 1. module exists.  Therefore, the
          imported module isn't *note __main__: 1.  This can be used to
          execute code early during Python initialization.  Python needs
          to be *note built in debug mode: 1de. for this option to
          exist.  See also *note PYTHON_PRESITE: 1c40.

          在 3.13 版被加入.

        * ‘-X gil=0,1’ forces the GIL to be disabled or enabled,
          respectively.  Setting to ‘0’ is only available in builds
          configured with *note -disable-gil: 158.  See also *note
          PYTHON_GIL: 159. and *note Free-threaded CPython: 125.

          在 3.13 版被加入.

     It also allows passing arbitrary values and retrieving them through
     the *note sys._xoptions: 1c41. dictionary.

     在 3.2 版被加入.

     在 3.9 版的變更: 移除 ‘-X showalloccount’ 選項。

     在 3.10 版的變更: 移除 ‘-X oldparser’ 選項。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0488/

   (2) https://peps.python.org/pep-0488/

   (3) https://peps.python.org/pep-0488/

   (4) https://peps.python.org/pep-0488/

   (5) https://peps.python.org/pep-0370/


File: python.info,  Node: Controlling color,  Next: 你不該使用的選項,  Prev: Miscellaneous options,  Up: 命令列

3.1.1.4 Controlling color
.........................

The Python interpreter is configured by default to use colors to
highlight output in certain situations such as when displaying
tracebacks.  This behavior can be controlled by setting different
environment variables.

Setting the environment variable ‘TERM’ to ‘dumb’ will disable color.

If the FORCE_COLOR(1) environment variable is set, then color will be
enabled regardless of the value of TERM. This is useful on CI systems
which aren’t terminals but can still display ANSI escape sequences.

If the NO_COLOR(2) environment variable is set, Python will disable all
color in the output.  This takes precedence over ‘FORCE_COLOR’.

All these environment variables are used also by other tools to control
color output.  To control the color output only in the Python
interpreter, the *note PYTHON_COLORS: 130. environment variable can be
used.  This variable takes precedence over ‘NO_COLOR’, which in turn
takes precedence over ‘FORCE_COLOR’.

   ---------- Footnotes ----------

   (1) https://force-color.org/

   (2) https://no-color.org/


File: python.info,  Node: 你不該使用的選項,  Prev: Controlling color,  Up: 命令列

3.1.1.5 你不該使用的選項
........................

 -- Option: -J

     Reserved for use by Jython(1).

   ---------- Footnotes ----------

   (1) https://www.jython.org/


File: python.info,  Node: 環境變數,  Prev: 命令列,  Up: 命令列與環境

3.1.2 環境變數
--------------

These environment variables influence Python's behavior, they are
processed before the command-line switches other than -E or -I. It is
customary that command-line switches override environmental variables
where there is a conflict.

 -- 環境變數: PYTHONHOME

     Change the location of the standard Python libraries.  By default,
     the libraries are searched in ‘`prefix'/lib/python`version'’ and
     ‘`exec_prefix'/lib/python`version'’, where ‘`prefix'’ and
     ‘`exec_prefix'’ are installation-dependent directories, both
     defaulting to ‘/usr/local’.

     When *note PYTHONHOME: 387. is set to a single directory, its value
     replaces both ‘`prefix'’ and ‘`exec_prefix'’.  To specify different
     values for these, set *note PYTHONHOME: 387. to
     ‘`prefix':`exec_prefix'’.

 -- 環境變數: PYTHONPATH

     Augment the default search path for module files.  The format is
     the same as the shell's ‘PATH’: one or more directory pathnames
     separated by *note os.pathsep: 1c46. (e.g.  colons on Unix or
     semicolons on Windows).  Non-existent directories are silently
     ignored.

     In addition to normal directories, individual *note PYTHONPATH:
     fbe. entries may refer to zipfiles containing pure Python modules
     (in either source or compiled form).  Extension modules cannot be
     imported from zipfiles.

     The default search path is installation dependent, but generally
     begins with ‘`prefix'/lib/python`version'’ (see *note PYTHONHOME:
     387. above).  It is 'always' appended to *note PYTHONPATH: fbe.

     An additional directory will be inserted in the search path in
     front of *note PYTHONPATH: fbe. as described above under *note
     介面選項: 1c2b.  The search path can be manipulated from within a
     Python program as the variable *note sys.path: 37f.

 -- 環境變數: PYTHONSAFEPATH

     If this is set to a non-empty string, don't prepend a potentially
     unsafe path to *note sys.path: 37f.: see the *note -P: 548. option
     for details.

     在 3.11 版被加入.

 -- 環境變數: PYTHONPLATLIBDIR

     If this is set to a non-empty string, it overrides the *note
     sys.platlibdir: 8dc. value.

     在 3.9 版被加入.

 -- 環境變數: PYTHONSTARTUP

     If this is the name of a readable file, the Python commands in that
     file are executed before the first prompt is displayed in
     interactive mode.  The file is executed in the same namespace where
     interactive commands are executed so that objects defined or
     imported in it can be used without qualification in the interactive
     session.  You can also change the prompts *note sys.ps1: 1c47. and
     *note sys.ps2: 1c48. and the hook *note sys.__interactivehook__:
     f6a. in this file.

     引發一個附帶呼叫啟動時的檔案名稱為引數的*note 稽核事件: 17bd.
     ‘cpython.run_startup’。

 -- 環境變數: PYTHONOPTIMIZE

     If this is set to a non-empty string it is equivalent to specifying
     the *note -O: d5b. option.  If set to an integer, it is equivalent
     to specifying *note -O: d5b. multiple times.

 -- 環境變數: PYTHONBREAKPOINT

     If this is set, it names a callable using dotted-path notation.
     The module containing the callable will be imported and then the
     callable will be run by the default implementation of *note
     sys.breakpointhook(): a7d. which itself is called by built-in *note
     breakpoint(): 219.  If not set, or set to the empty string, it is
     equivalent to the value "pdb.set_trace".  Setting this to the
     string "0" causes the default implementation of *note
     sys.breakpointhook(): a7d. to do nothing but return immediately.

     在 3.7 版被加入.

 -- 環境變數: PYTHONDEBUG

     If this is set to a non-empty string it is equivalent to specifying
     the *note -d: 1c33. option.  If set to an integer, it is equivalent
     to specifying *note -d: 1c33. multiple times.

     This environment variable requires a *note debug build of Python:
     1de, otherwise it's ignored.

 -- 環境變數: PYTHONINSPECT

     If this is set to a non-empty string it is equivalent to specifying
     the *note -i: 144a. option.

     This variable can also be modified by Python code using *note
     os.environ: 1152. to force inspect mode on program termination.

     引發一個不附帶引數的*note 稽核事件: 17bd. ‘cpython.run_stdin’。

     在 3.12.5 版的變更: (also 3.11.10, 3.10.15, 3.9.20, and 3.8.20)
     Emits audit events.

     在 3.13 版的變更: Uses PyREPL if possible, in which case *note
     PYTHONSTARTUP: f6b. is also executed.  Emits audit events.

 -- 環境變數: PYTHONUNBUFFERED

     If this is set to a non-empty string it is equivalent to specifying
     the *note -u: 18a8. option.

 -- 環境變數: PYTHONVERBOSE

     If this is set to a non-empty string it is equivalent to specifying
     the *note -v: 1392. option.  If set to an integer, it is equivalent
     to specifying *note -v: 1392. multiple times.

 -- 環境變數: PYTHONCASEOK

     If this is set, Python ignores case in *note import: 586.
     statements.  This only works on Windows and macOS.

 -- 環境變數: PYTHONDONTWRITEBYTECODE

     If this is set to a non-empty string, Python won't try to write
     ‘.pyc’ files on the import of source modules.  This is equivalent
     to specifying the *note -B: 133b. option.

 -- 環境變數: PYTHONPYCACHEPREFIX

     If this is set, Python will write ‘.pyc’ files in a mirror
     directory tree at this path, instead of in ‘__pycache__’
     directories within the source tree.  This is equivalent to
     specifying the *note -X: 15a. ‘pycache_prefix=PATH’ option.

     在 3.8 版被加入.

 -- 環境變數: PYTHONHASHSEED

     If this variable is not set or set to ‘random’, a random value is
     used to seed the hashes of str and bytes objects.

     If *note PYTHONHASHSEED: 101e. is set to an integer value, it is
     used as a fixed seed for generating the hash() of the types covered
     by the hash randomization.

     Its purpose is to allow repeatable hashing, such as for selftests
     for the interpreter itself, or to allow a cluster of python
     processes to share hash values.

     The integer must be a decimal number in the range [0,4294967295].
     Specifying the value 0 will disable hash randomization.

     在 3.2.3 版被加入.

 -- 環境變數: PYTHONINTMAXSTRDIGITS

     If this variable is set to an integer, it is used to configure the
     interpreter's global *note integer string conversion length
     limitation: 599.

     在 3.11 版被加入.

 -- 環境變數: PYTHONIOENCODING

     If this is set before running the interpreter, it overrides the
     encoding used for stdin/stdout/stderr, in the syntax
     ‘encodingname:errorhandler’.  Both the ‘encodingname’ and the
     ‘:errorhandler’ parts are optional and have the same meaning as in
     *note str.encode(): 87a.

     For stderr, the ‘:errorhandler’ part is ignored; the handler will
     always be ‘'backslashreplace'’.

     在 3.4 版的變更: The ‘encodingname’ part is now optional.

     在 3.6 版的變更: On Windows, the encoding specified by this
     variable is ignored for interactive console buffers unless *note
     PYTHONLEGACYWINDOWSSTDIO: c02. is also specified.  Files and pipes
     redirected through the standard streams are not affected.

 -- 環境變數: PYTHONNOUSERSITE

     If this is set, Python won't add the *note user site-packages
     directory: 1c37. to *note sys.path: 37f.

     也參考
     ......

     PEP 370(1) - Per user site-packages directory

 -- 環境變數: PYTHONUSERBASE

     Defines the *note user base directory: 12b0, which is used to
     compute the path of the *note user site-packages directory: 1c37.
     and *note installation paths: 1c49. for ‘python -m pip install
     --user’.

     也參考
     ......

     PEP 370(2) - Per user site-packages directory

 -- 環境變數: PYTHONEXECUTABLE

     If this environment variable is set, ‘sys.argv[0]’ will be set to
     its value instead of the value got through the C runtime.  Only
     works on macOS.

 -- 環境變數: PYTHONWARNINGS

     This is equivalent to the *note -W: 86c. option.  If set to a comma
     separated string, it is equivalent to specifying *note -W: 86c.
     multiple times, with filters later in the list taking precedence
     over those earlier in the list.

     The simplest settings apply a particular action unconditionally to
     all warnings emitted by a process (even those that are otherwise
     ignored by default):

          PYTHONWARNINGS=default  # Warn once per call location
          PYTHONWARNINGS=error    # Convert to exceptions
          PYTHONWARNINGS=always   # Warn every time
          PYTHONWARNINGS=all      # Same as PYTHONWARNINGS=always
          PYTHONWARNINGS=module   # Warn once per calling module
          PYTHONWARNINGS=once     # Warn once per Python process
          PYTHONWARNINGS=ignore   # Never warn

     See *note The Warnings Filter: 86e. and *note Describing Warning
     Filters: 1c3b. for more details.

 -- 環境變數: PYTHONFAULTHANDLER

     If this environment variable is set to a non-empty string, *note
     faulthandler.enable(): c45. is called at startup: install a handler
     for *note SIGSEGV: 1c4b, *note SIGFPE: 1c4c, *note SIGABRT: 1c4d,
     *note SIGBUS: 1c4e. and *note SIGILL: 1c4f. signals to dump the
     Python traceback.  This is equivalent to *note -X: 15a.
     ‘faulthandler’ option.

     在 3.3 版被加入.

 -- 環境變數: PYTHONTRACEMALLOC

     If this environment variable is set to a non-empty string, start
     tracing Python memory allocations using the *note tracemalloc: e8.
     module.  The value of the variable is the maximum number of frames
     stored in a traceback of a trace.  For example,
     ‘PYTHONTRACEMALLOC=1’ stores only the most recent frame.  See the
     *note tracemalloc.start(): 1c3d. function for more information.
     This is equivalent to setting the *note -X: 15a. ‘tracemalloc’
     option.

     在 3.4 版被加入.

 -- 環境變數: PYTHONPROFILEIMPORTTIME

     If this environment variable is set to a non-empty string, Python
     will show how long each import takes.  This is equivalent to
     setting the *note -X: 15a. ‘importtime’ option.

     在 3.7 版被加入.

 -- 環境變數: PYTHONASYNCIODEBUG

     If this environment variable is set to a non-empty string, enable
     the *note debug mode: 1c51. of the *note asyncio: 8. module.

     在 3.4 版被加入.

 -- 環境變數: PYTHONMALLOC

     Set the Python memory allocators and/or install debug hooks.

     Set the family of memory allocators used by Python:

        * ‘default’: use the *note default memory allocators: 1c52.

        * ‘malloc’: use the ‘malloc()’ function of the C library for all
          domains (*note PYMEM_DOMAIN_RAW: 1c53, *note PYMEM_DOMAIN_MEM:
          c10, *note PYMEM_DOMAIN_OBJ: c0e.).

        * ‘pymalloc’: use the *note pymalloc allocator: cb6. for *note
          PYMEM_DOMAIN_MEM: c10. and *note PYMEM_DOMAIN_OBJ: c0e.
          domains and use the ‘malloc()’ function for the *note
          PYMEM_DOMAIN_RAW: 1c53. domain.

        * ‘mimalloc’: use the *note mimalloc allocator: 1c54. for *note
          PYMEM_DOMAIN_MEM: c10. and *note PYMEM_DOMAIN_OBJ: c0e.
          domains and use the ‘malloc()’ function for the *note
          PYMEM_DOMAIN_RAW: 1c53. domain.

     Install *note debug hooks: 1c55.:

        * ‘debug’: install debug hooks on top of the *note default
          memory allocators: 1c52.

        * ‘malloc_debug’: same as ‘malloc’ but also install debug hooks.

        * ‘pymalloc_debug’: same as ‘pymalloc’ but also install debug
          hooks.

        * ‘mimalloc_debug’: same as ‘mimalloc’ but also install debug
          hooks.

     在 3.6 版被加入.

     在 3.7 版的變更: Added the ‘"default"’ allocator.

 -- 環境變數: PYTHONMALLOCSTATS

     If set to a non-empty string, Python will print statistics of the
     *note pymalloc memory allocator: cb6. every time a new pymalloc
     object arena is created, and on shutdown.

     This variable is ignored if the *note PYTHONMALLOC: c0b.
     environment variable is used to force the ‘malloc()’ allocator of
     the C library, or if Python is configured without ‘pymalloc’
     support.

     在 3.6 版的變更: This variable can now also be used on Python
     compiled in release mode.  It now has no effect if set to an empty
     string.

 -- 環境變數: PYTHONLEGACYWINDOWSFSENCODING

     If set to a non-empty string, the default *note filesystem encoding
     and error handler: 4e0. mode will revert to their pre-3.6 values of
     'mbcs' and 'replace', respectively.  Otherwise, the new defaults
     'utf-8' and 'surrogatepass' are used.

     This may also be enabled at runtime with *note
     sys._enablelegacywindowsfsencoding(): 28e.

     *note 適用: 1c56.：Windows。

     在 3.6 版被加入: 更多細節請見 PEP 529(3)。

 -- 環境變數: PYTHONLEGACYWINDOWSSTDIO

     If set to a non-empty string, does not use the new console reader
     and writer.  This means that Unicode characters will be encoded
     according to the active console code page, rather than using utf-8.

     This variable is ignored if the standard streams are redirected (to
     files or pipes) rather than referring to console buffers.

     *note 適用: 1c56.：Windows。

     在 3.6 版被加入.

 -- 環境變數: PYTHONCOERCECLOCALE

     If set to the value ‘0’, causes the main Python command line
     application to skip coercing the legacy ASCII-based C and POSIX
     locales to a more capable UTF-8 based alternative.

     If this variable is 'not' set (or is set to a value other than
     ‘0’), the ‘LC_ALL’ locale override environment variable is also not
     set, and the current locale reported for the ‘LC_CTYPE’ category is
     either the default ‘C’ locale, or else the explicitly ASCII-based
     ‘POSIX’ locale, then the Python CLI will attempt to configure the
     following locales for the ‘LC_CTYPE’ category in the order listed
     before loading the interpreter runtime:

        * ‘C.UTF-8’

        * ‘C.utf8’

        * ‘UTF-8’

     If setting one of these locale categories succeeds, then the
     ‘LC_CTYPE’ environment variable will also be set accordingly in the
     current process environment before the Python runtime is
     initialized.  This ensures that in addition to being seen by both
     the interpreter itself and other locale-aware components running in
     the same process (such as the GNU ‘readline’ library), the updated
     setting is also seen in subprocesses (regardless of whether or not
     those processes are running a Python interpreter), as well as in
     operations that query the environment rather than the current C
     locale (such as Python's own *note locale.getdefaultlocale():
     2ba.).

     Configuring one of these locales (either explicitly or via the
     above implicit locale coercion) automatically enables the
     ‘surrogateescape’ *note error handler: 16eb. for *note sys.stdin:
     4e2. and *note sys.stdout: a79. (*note sys.stderr: 8dd. continues
     to use ‘backslashreplace’ as it does in any other locale).  This
     stream handling behavior can be overridden using *note
     PYTHONIOENCODING: fab. as usual.

     For debugging purposes, setting ‘PYTHONCOERCECLOCALE=warn’ will
     cause Python to emit warning messages on ‘stderr’ if either the
     locale coercion activates, or else if a locale that 'would' have
     triggered coercion is still active when the Python runtime is
     initialized.

     Also note that even when locale coercion is disabled, or when it
     fails to find a suitable target locale, *note PYTHONUTF8: a7b. will
     still activate by default in legacy ASCII-based locales.  Both
     features must be disabled in order to force the interpreter to use
     ‘ASCII’ instead of ‘UTF-8’ for system interfaces.

     *note 適用: 1c56.：Unix。

     在 3.7 版被加入: 更多細節請見 PEP 538(4)。

 -- 環境變數: PYTHONDEVMODE

     If this environment variable is set to a non-empty string, enable
     *note Python Development Mode: 1dd, introducing additional runtime
     checks that are too expensive to be enabled by default.  This is
     equivalent to setting the *note -X: 15a. ‘dev’ option.

     在 3.7 版被加入.

 -- 環境變數: PYTHONUTF8

     如果設為 ‘1’，則啟用 *note Python UTF-8 Mode: 5fc.。

     如果設為 ‘0’，則停用 *note Python UTF-8 Mode: 5fc.。

     Setting any other non-empty string causes an error during
     interpreter initialisation.

     在 3.7 版被加入.

 -- 環境變數: PYTHONWARNDEFAULTENCODING

     If this environment variable is set to a non-empty string, issue a
     *note EncodingWarning: 1c3f. when the locale-specific default
     encoding is used.

     細節請見 *note 選擇性加入的編碼警告: 1c57.。

     在 3.10 版被加入.

 -- 環境變數: PYTHONNODEBUGRANGES

     If this variable is set, it disables the inclusion of the tables
     mapping extra location information (end line, start column offset
     and end column offset) to every instruction in code objects.  This
     is useful when smaller code objects and pyc files are desired as
     well as suppressing the extra visual location indicators when the
     interpreter displays tracebacks.

     在 3.11 版被加入.

 -- 環境變數: PYTHONPERFSUPPORT

     If this variable is set to a nonzero value, it enables support for
     the Linux ‘perf’ profiler so Python calls can be detected by it.

     If set to ‘0’, disable Linux ‘perf’ profiler support.

     See also the *note -X perf: 15a. command-line option and *note
     Python 對 Linux perf 分析器的支援: 175.

     在 3.12 版被加入.

 -- 環境變數: PYTHON_PERF_JIT_SUPPORT

     If this variable is set to a nonzero value, it enables support for
     the Linux ‘perf’ profiler so Python calls can be detected by it
     using DWARF information.

     If set to ‘0’, disable Linux ‘perf’ profiler support.

     See also the *note -X perf_jit: 15a. command-line option and *note
     Python 對 Linux perf 分析器的支援: 175.

     在 3.13 版被加入.

 -- 環境變數: PYTHON_CPU_COUNT

     If this variable is set to a positive integer, it overrides the
     return values of *note os.cpu_count(): 1a8. and *note
     os.process_cpu_count(): 1a7.

     See also the *note -X cpu_count: 15a. command-line option.

     在 3.13 版被加入.

 -- 環境變數: PYTHON_FROZEN_MODULES

     If this variable is set to ‘on’ or ‘off’, it determines whether or
     not frozen modules are ignored by the import machinery.  A value of
     ‘on’ means they get imported and ‘off’ means they are ignored.  The
     default is ‘on’ for non-debug builds (the normal case) and ‘off’
     for debug builds.  Note that the ‘importlib_bootstrap’ and
     ‘importlib_bootstrap_external’ frozen modules are always used, even
     if this flag is set to ‘off’.

     See also the *note -X frozen_modules: 15a. command-line option.

     在 3.13 版被加入.

 -- 環境變數: PYTHON_COLORS

     If this variable is set to ‘1’, the interpreter will colorize
     various kinds of output.  Setting it to ‘0’ deactivates this
     behavior.  See also *note Controlling color: 14f.

     在 3.13 版被加入.

 -- 環境變數: PYTHON_BASIC_REPL

     If this variable is set to ‘1’, the interpreter will not attempt to
     load the Python-based *note REPL: 14e. that requires *note curses:
     23. and *note readline: a8, and will instead use the traditional
     parser-based *note REPL: 14e.

     在 3.13 版被加入.

 -- 環境變數: PYTHON_HISTORY

     This environment variable can be used to set the location of a
     ‘.python_history’ file (by default, it is ‘.python_history’ in the
     user's home directory).

     在 3.13 版被加入.

 -- 環境變數: PYTHON_GIL

     If this variable is set to ‘1’, the global interpreter lock (GIL)
     will be forced on.  Setting it to ‘0’ forces the GIL off (needs
     Python configured with the *note -disable-gil: 158. build option).

     See also the *note -X gil: 15a. command-line option, which takes
     precedence over this variable, and *note Free-threaded CPython:
     125.

     在 3.13 版被加入.

* Menu:

* 除錯模式變數::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0370/

   (2) https://peps.python.org/pep-0370/

   (3) https://peps.python.org/pep-0529/

   (4) https://peps.python.org/pep-0538/


File: python.info,  Node: 除錯模式變數,  Up: 環境變數

3.1.2.1 除錯模式變數
....................

 -- 環境變數: PYTHONDUMPREFS

     If set, Python will dump objects and reference counts still alive
     after shutting down the interpreter.

     Needs Python configured with the *note -with-trace-refs: 317. build
     option.

 -- 環境變數: PYTHONDUMPREFSFILE

     If set, Python will dump objects and reference counts still alive
     after shutting down the interpreter into a file under the path
     given as the value to this environment variable.

     Needs Python configured with the *note -with-trace-refs: 317. build
     option.

     在 3.11 版被加入.

 -- 環境變數: PYTHON_PRESITE

     If this variable is set to a module, that module will be imported
     early in the interpreter lifecycle, before the *note site: b5.
     module is executed, and before the *note __main__: 1. module is
     created.  Therefore, the imported module is not treated as *note
     __main__: 1.

     This can be used to execute code early during Python
     initialization.

     To import a submodule, use ‘package.module’ as the value, like in
     an import statement.

     See also the *note -X presite: 15a. command-line option, which
     takes precedence over this variable.

     Needs Python configured with the *note -with-pydebug: 3d8. build
     option.

     在 3.13 版被加入.


File: python.info,  Node: 在 Unix 平臺上使用 Python,  Next: 配置 Python,  Prev: 命令列與環境,  Up: Python 的設置與使用

3.2 在 Unix 平臺上使用 Python
=============================

* Menu:

* 獲得並安裝 Python 的最新版本::
* 建置 Python::
* 與 Python 相關的路徑和檔案::
* 雜項: 雜項<2>.
* 客製化 OpenSSL::


File: python.info,  Node: 獲得並安裝 Python 的最新版本,  Next: 建置 Python,  Up: 在 Unix 平臺上使用 Python

3.2.1 獲得並安裝 Python 的最新版本
----------------------------------

* Menu:

* 在 Linux 上::
* 在 FreeBSD 和 OpenBSD 上::


File: python.info,  Node: 在 Linux 上,  Next: 在 FreeBSD 和 OpenBSD 上,  Up: 獲得並安裝 Python 的最新版本

3.2.1.1 在 Linux 上
...................

在大多數 Linux 發行版上會預先安裝 Python，並作為一個套件提供給所有其他使
用者。但是發行版提供的套件可能沒有你想要使用的某些功能，這時你可以選擇從
原始碼編譯最新版本的 Python，做法相當容易。

如果 Python 沒有預先安裝，並且不在發行版提供的儲存庫 (repository) 中，你
可以輕鬆地為自己使用的發行版建立套件。參閱以下連結：

也參考
......

‘https://www.debian.org/doc/manuals/maint-guide/first.en.html’

     對於 Debian 用戶

‘https://en.opensuse.org/Portal:Packaging’

     對於 OpenSuse 用戶

‘https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial_GNU_Hello/’

     對於 Fedora 用戶

‘https://slackbook.org/html/package-management-making-packages.html’

     對於 Slackware 用戶


File: python.info,  Node: 在 FreeBSD 和 OpenBSD 上,  Prev: 在 Linux 上,  Up: 獲得並安裝 Python 的最新版本

3.2.1.2 在 FreeBSD 和 OpenBSD 上
................................

   * FreeBSD 用戶應使用以下命令增加套件：

          pkg install python3

   * OpenBSD 用戶應使用以下命令增加套件：

          pkg_add -r python

          pkg_add ftp://ftp.openbsd.org/pub/OpenBSD/4.2/packages/<insert your architecture here>/python-<version>.tgz

     例如 i386 使用者要獲取 Python 2.5.1 的可用版本：

          pkg_add ftp://ftp.openbsd.org/pub/OpenBSD/4.2/packages/i386/python-2.5.1p2.tgz


File: python.info,  Node: 建置 Python,  Next: 與 Python 相關的路徑和檔案,  Prev: 獲得並安裝 Python 的最新版本,  Up: 在 Unix 平臺上使用 Python

3.2.2 建置 Python
-----------------

如果你想自己編譯 CPython，首先要做的是獲取原始碼(1)。你可以下載最新版本
的原始碼，也可以直接提取最新的 clone（克隆）(2)。（如果你想要貢獻修補程
式碼，也會需要一份 clone。）

建置過程由幾個常用命令組成：

     ./configure
     make
     make install

特定 Unix 平臺的*note 配置選項: 1c60.和注意事項通常會詳細地記錄在 Python
原始碼樹 (source tree) 根目錄下的 README.rst(3) 檔案中。

     警告: ‘make install’ 可以覆蓋或偽裝 ‘python3’ 二進位制檔案。因此，
     建議使用 ‘make altinstall’ 而不是 ‘make install’，因為它只安裝
     ‘`exec_prefix'/bin/python`version'’。

   ---------- Footnotes ----------

   (1) https://www.python.org/downloads/source/

   (2) https://devguide.python.org/setup/#getting-the-source-code

   (3) https://github.com/python/cpython/tree/3.13/README.rst


File: python.info,  Node: 與 Python 相關的路徑和檔案,  Next: 雜項<2>,  Prev: 建置 Python,  Up: 在 Unix 平臺上使用 Python

3.2.3 與 Python 相關的路徑和檔案
--------------------------------

這取決於本地安裝慣例；*note prefix: 1c62. 和 *note exec_prefix: 1c63. 相
依於安裝方式，應被直譯來讓 GNU 軟體使用；它們也可能相同。

例如，在大多數 Linux 系統上，兩者的預設值皆是 ‘/usr’。

檔案/目錄                                           含意
                                                    
---------------------------------------------------------------------------------------------------
                                                    
‘`exec_prefix'/bin/python3’                         直譯器的推薦位置。
                                                    
                                                    
‘`prefix'/lib/python`version'’、                    包含標準模組目錄的推薦位置。
‘`exec_prefix'/lib/python`version'’                 

‘`prefix'/include/python`version'’、                包含開發 Python 擴充套件和嵌入直譯器所需
‘`exec_prefix'/include/python`version'’             include 檔案之目錄的推薦位置。
                                                    


File: python.info,  Node: 雜項<2>,  Next: 客製化 OpenSSL,  Prev: 與 Python 相關的路徑和檔案,  Up: 在 Unix 平臺上使用 Python

3.2.4 雜項
----------

要在 Unix 上使用 Python 腳本，你需要讓他們是可執行的 (executable)，例如
用

     $ chmod +x script

並在腳本的頂部放一個合適的 Shebang。以下通常是個好選擇：

     #!/usr/bin/env python3

將在整個 ‘PATH’ 中搜索 Python 直譯器。然而某些 Unix 系統可能沒有 ‘env’ 命
令，因此你可能需要將 ‘/usr/bin/python3’ 寫死 (hardcode) 成直譯器路徑。

要在 Python 腳本中使用 shell 命令，請見 *note subprocess: c1. 模組。


File: python.info,  Node: 客製化 OpenSSL,  Prev: 雜項<2>,  Up: 在 Unix 平臺上使用 Python

3.2.5 客製化 OpenSSL
--------------------

  1. 要使用你所選擇發行商 (vendor) 的 OpenSSL 配置和系統信任儲存區
     (system trust store)，請找到包含 ‘openssl.cnf’ 檔案的目錄或位於
     ‘/etc’ 的符號連結 (symlink)。在大多數發行版上，該檔案會是在
     ‘/etc/ssl’ 或者 ‘/etc/pki/tls’ 中。該目錄亦應包含一個 ‘cert.pem’ 檔
     案和/或一個 ‘certs’ 目錄。

          $ find /etc/ -name openssl.cnf -printf "%h\n"
          /etc/ssl

  2. 下載、建置並安裝 OpenSSL。請確保你使用 ‘install_sw’ 而不是
     ‘install’。‘install_sw’ 的目標不會覆蓋 ‘openssl.cnf’。

          $ curl -O https://www.openssl.org/source/openssl-VERSION.tar.gz
          $ tar xzf openssl-VERSION
          $ pushd openssl-VERSION
          $ ./config \
              --prefix=/usr/local/custom-openssl \
              --libdir=lib \
              --openssldir=/etc/ssl
          $ make -j1 depend
          $ make -j8
          $ make install_sw
          $ popd

  3. 使用客製化 OpenSSL 建置 Python（參見配置 ‘--with-openssl’ 和
     ‘--with-openssl-rpath’ 選項）

          $ pushd python-3.x.x
          $ ./configure -C \
              --with-openssl=/usr/local/custom-openssl \
              --with-openssl-rpath=auto \
              --prefix=/usr/local/python-3.x.x
          $ make -j8
          $ make altinstall

     備註: OpenSSL 的修補釋出版 (patch releases) 具有向後相容的 ABI。你
     不需要重新編譯 Python 來更新 OpenSSL。使用一個新的版本來替代客製化
     OpenSSL 安裝版就可以了。


File: python.info,  Node: 配置 Python,  Next: 在 Windows 上使用 Python,  Prev: 在 Unix 平臺上使用 Python,  Up: Python 的設置與使用

3.3 配置 Python
===============

* Menu:

* 建置需求::
* 產生的檔案::
* 設定選項::
* Python Build System::
* Compiler and linker flags::


File: python.info,  Node: 建置需求,  Next: 產生的檔案,  Up: 配置 Python

3.3.1 建置需求
--------------

Features and minimum versions required to build CPython:

   * A C11(1) compiler.  Optional C11 features(2) are not required.

   * 在 Windows 上需要 Microsoft Visual Studio 2017 或更新版本。

   * Support for IEEE 754(3) floating-point numbers and floating-point
     Not-a-Number (NaN)(4).

   * thread 的支援。

   * OpenSSL 1.1.1 is the minimum version and OpenSSL 3.0.9 is the
     recommended minimum version for the *note ssl: bb. and *note
     hashlib: 5e. extension modules.

   * SQLite 3.15.2 for the *note sqlite3: ba. extension module.

   * Tcl/Tk 8.5.12 for the *note tkinter: d9. module.

   * Autoconf 2.71 and aclocal 1.16.4 are required to regenerate the
     ‘configure’ script.

在 3.1 版的變更: Tcl/Tk version 8.3.1 is now required.

在 3.5 版的變更: On Windows, Visual Studio 2015 or later is now
required.  Tcl/Tk version 8.4 is now required.

在 3.6 版的變更: Selected C99 features are now required, like
‘<stdint.h>’ and ‘static inline’ functions.

在 3.7 版的變更: 對執行緒與 OpenSSL 1.0.2 的支援現在是必要的。

在 3.10 版的變更: OpenSSL 1.1.1 is now required.  Require SQLite 3.7.15.

在 3.11 版的變更: C11 compiler, IEEE 754 and NaN support are now
required.  On Windows, Visual Studio 2017 or later is required.  Tcl/Tk
version 8.5.12 is now required for the *note tkinter: d9. module.

在 3.13 版的變更: Autoconf 2.71, aclocal 1.16.4 and SQLite 3.15.2 are
now required.

See also PEP 7(5) "Style Guide for C Code" and PEP 11(6) "CPython
platform support".

   ---------- Footnotes ----------

   (1) https://en.cppreference.com/w/c/11

   (2) 
https://en.wikipedia.org/wiki/C11_(C_standard_revision)#Optional_features

   (3) https://en.wikipedia.org/wiki/IEEE_754

   (4) https://en.wikipedia.org/wiki/NaN#Floating_point

   (5) https://peps.python.org/pep-0007/

   (6) https://peps.python.org/pep-0011/


File: python.info,  Node: 產生的檔案,  Next: 設定選項,  Prev: 建置需求,  Up: 配置 Python

3.3.2 產生的檔案
----------------

To reduce build dependencies, Python source code contains multiple
generated files.  Commands to regenerate all generated files:

     make regen-all
     make regen-stdlib-module-names
     make regen-limited-abi
     make regen-configure

The ‘Makefile.pre.in’ file documents generated files, their inputs, and
tools used to regenerate them.  Search for ‘regen-*’ make targets.

* Menu:

* 設定腳本::


File: python.info,  Node: 設定腳本,  Up: 產生的檔案

3.3.2.1 設定腳本
................

The ‘make regen-configure’ command regenerates the ‘aclocal.m4’ file and
the ‘configure’ script using the ‘Tools/build/regen-configure.sh’ shell
script which uses an Ubuntu container to get the same tools versions and
have a reproducible output.

The container is optional, the following command can be run locally:

     autoreconf -ivf -Werror

The generated files can change depending on the exact
‘autoconf-archive’, ‘aclocal’ and ‘pkg-config’ versions.


File: python.info,  Node: 設定選項,  Next: Python Build System,  Prev: 產生的檔案,  Up: 配置 Python

3.3.3 設定選項
--------------

List all ‘configure’ script options using:

     ./configure --help

請見 Python 原始碼發行版中的 ‘Misc/SpecialBuilds.txt’。

* Menu:

* 一般選項::
* C compiler options::
* Linker options::
* Options for third-party dependencies::
* WebAssembly 選項::
* 安裝選項::
* Performance options::
* Python Debug Build::
* Debug options::
* Linker options: Linker options<2>.
* 函式庫選項::
* Security Options::
* macOS 選項::
* iOS Options::
* Cross Compiling Options::


File: python.info,  Node: 一般選項,  Next: C compiler options,  Up: 設定選項

3.3.3.1 一般選項
................

 -- Option: --enable-loadable-sqlite-extensions

     Support loadable extensions in the ‘_sqlite’ extension module
     (default is no) of the *note sqlite3: ba. module.

     請見 *note sqlite3: ba. 模組的 *note
     sqlite3.Connection.enable_load_extension(): 7e2. 方法。

     在 3.6 版被加入.

 -- Option: --disable-ipv6

     停用 IPv6 支援（如果支援的話預設是啟用的），請見 *note socket: b8.
     模組。

 -- Option: --enable-big-digits=[15|30]

     Define the size in bits of Python *note int: 23c. digits: 15 or 30
     bits.

     By default, the digit size is 30.

     將 ‘PYLONG_BITS_IN_DIGIT’ 定義為 ‘15’ 或 ‘30’。

     參閱 *note sys.int_info.bits_per_digit: 122b.。

 -- Option: --with-suffix=SUFFIX

     將 Python 執行檔的後綴設定為 'SUFFIX'。

     在 Windows 和 macOS 上預設的後綴是 ‘.exe’ （‘python.exe’ 執行檔）、
     在 Emscripten node 上為 ‘.js’、在 Emscripten 瀏覽器為 ‘.html’、在
     WASI 上為 ‘.wasm’，以及在其他平台為空字串（‘python’ 執行檔）。

     在 3.11 版的變更: 在 WASM 平台上預設的後綴是 ‘.js’、‘.html’ 或
     ‘.wasm’ 中的一個。

 -- Option: --with-tzpath=<list of absolute paths separated by pathsep>

     Select the default time zone search path for *note zoneinfo.TZPATH:
     1c72.  See the *note Compile-time configuration: 1c73. of the *note
     zoneinfo: 11a. module.

     預設值：
     ‘/usr/share/zoneinfo:/usr/lib/zoneinfo:/usr/share/lib/zoneinfo:/etc/zoneinfo’。

     請見 *note os.pathsep: 1c46. 路徑分隔符號。

     在 3.9 版被加入.

 -- Option: --without-decimal-contextvar

     Build the ‘_decimal’ extension module using a thread-local context
     rather than a coroutine-local context (default), see the *note
     decimal: 2e. module.

     請見 *note decimal.HAVE_CONTEXTVAR: 1c75. 與 *note contextvars: 1d.
     模組。

     在 3.9 版被加入.

 -- Option: --with-dbmliborder=<list of backend names>

     Override order to check db backends for the *note dbm: 29. module

     A valid value is a colon (‘:’) separated string with the backend
     names:

        * ‘ndbm’;

        * ‘gdbm’;

        * ‘bdb’.

 -- Option: --without-c-locale-coercion

     Disable C locale coercion to a UTF-8 based locale (enabled by
     default).

     不要定義 ‘PY_COERCE_C_LOCALE’ 巨集。

     請見 *note PYTHONCOERCECLOCALE: a78. 與 PEP 538(1)。

 -- Option: --without-freelists

     Disable all freelists except the empty tuple singleton.

     在 3.11 版被加入.

 -- Option: --with-platlibdir=DIRNAME

     Python 函式庫目錄名稱（預設為 ‘lib’ ）。

     Fedora 和 SuSE 在 64 位元平台上使用 ‘lib64’。

     參閱 *note sys.platlibdir: 8dc.。

     在 3.9 版被加入.

 -- Option: --with-wheel-pkg-dir=PATH

     Directory of wheel packages used by the *note ensurepip: 4b. module
     (none by default).

     Some Linux distribution packaging policies recommend against
     bundling dependencies.  For example, Fedora installs wheel packages
     in the ‘/usr/share/python-wheels/’ directory and don't install the
     ‘ensurepip._bundled’ package.

     在 3.10 版被加入.

 -- Option: --with-pkg-config=[check|yes|no]

     Whether configure should use ‘pkg-config’ to detect build
     dependencies.

        * ‘check’ （預設）：‘pkg-config’ 是可選的

        * ‘yes’：‘pkg-config’ 是必要的

        * ‘no’：即使存在也不使用 ‘pkg-config’ 來配置

     在 3.11 版被加入.

 -- Option: --enable-pystats

     Turn on internal Python performance statistics gathering.

     By default, statistics gathering is off.  Use ‘python3 -X pystats’
     command or set ‘PYTHONSTATS=1’ environment variable to turn on
     statistics gathering at Python startup.

     At Python exit, dump statistics if statistics gathering was on and
     not cleared.

     效果：

        * Add *note -X pystats: 15a. command line option.

        * Add ‘PYTHONSTATS’ environment variable.

        * Define the ‘Py_STATS’ macro.

        * Add functions to the *note sys: c3. module:

             * ‘sys._stats_on()’: Turns on statistics gathering.

             * ‘sys._stats_off()’: Turns off statistics gathering.

             * ‘sys._stats_clear()’: Clears the statistics.

             * ‘sys._stats_dump()’: Dump statistics to file, and clears
               the statistics.

     The statistics will be dumped to a arbitrary (probably unique) file
     in ‘/tmp/py_stats/’ (Unix) or ‘C:\temp\py_stats\’ (Windows).  If
     that directory does not exist, results will be printed on stderr.

     使用 ‘Tools/scripts/summarize_stats.py’ 來讀取統計資料。

     Statistics:

        * Opcode:

             * Specialization: success, failure, hit, deferred, miss,
               deopt, failures;

             * Execution count;

             * Pair count.

        * Call:

             * Inlined Python calls;

             * PyEval calls;

             * Frames pushed;

             * Frame object created;

             * Eval calls: vector, generator, legacy, function
               VECTORCALL, build class, slot, function "ex", API,
               method.

        * Object:

             * incref and decref;

             * interpreter incref and decref;

             * allocations: all, 512 bytes, 4 kiB, big;

             * free;

             * to/from free lists;

             * dictionary materialized/dematerialized;

             * type cache;

             * optimization attempts;

             * optimization traces created/executed;

             * uops executed.

        * Garbage collector:

             * Garbage collections;

             * Objects visited;

             * Objects collected.

     在 3.11 版被加入.

 -- Option: --disable-gil

     Enables 'experimental' support for running Python without the *note
     global interpreter lock: 12e. (GIL): free threading build.

     Defines the ‘Py_GIL_DISABLED’ macro and adds ‘"t"’ to *note
     sys.abiflags: a07.

     See *note Free-threaded CPython: 125. for more detail.

     在 3.13 版被加入.

 -- Option: PKG_CONFIG

     Path to ‘pkg-config’ utility.

 -- Option: PKG_CONFIG_LIBDIR

 -- Option: PKG_CONFIG_PATH

     ‘pkg-config’ options.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0538/


File: python.info,  Node: C compiler options,  Next: Linker options,  Prev: 一般選項,  Up: 設定選項

3.3.3.2 C compiler options
..........................

 -- Option: CC

     C 編譯器指令。

 -- Option: CFLAGS

     C 編譯器旗標。

 -- Option: CPP

     C preprocessor command.

 -- Option: CPPFLAGS

     C preprocessor flags, e.g.  ‘-IINCLUDE_DIR’.


File: python.info,  Node: Linker options,  Next: Options for third-party dependencies,  Prev: C compiler options,  Up: 設定選項

3.3.3.3 Linker options
......................

 -- Option: LDFLAGS

     Linker flags, e.g.  ‘-LLIBRARY_DIRECTORY’.

 -- Option: LIBS

     Libraries to pass to the linker, e.g.  ‘-lLIBRARY’.

 -- Option: MACHDEP

     Name for machine-dependent library files.


File: python.info,  Node: Options for third-party dependencies,  Next: WebAssembly 選項,  Prev: Linker options,  Up: 設定選項

3.3.3.4 Options for third-party dependencies
............................................

在 3.11 版被加入.

 -- Option: BZIP2_CFLAGS

 -- Option: BZIP2_LIBS

     C compiler and linker flags to link Python to ‘libbz2’, used by
     *note bz2: f. module, overriding ‘pkg-config’.

 -- Option: CURSES_CFLAGS

 -- Option: CURSES_LIBS

     C compiler and linker flags for ‘libncurses’ or ‘libncursesw’, used
     by *note curses: 23. module, overriding ‘pkg-config’.

 -- Option: GDBM_CFLAGS

 -- Option: GDBM_LIBS

     C compiler and linker flags for ‘gdbm’.

 -- Option: LIBB2_CFLAGS

 -- Option: LIBB2_LIBS

     C compiler and linker flags for ‘libb2’ (*note BLAKE2: 1c90.), used
     by *note hashlib: 5e. module, overriding ‘pkg-config’.

 -- Option: LIBEDIT_CFLAGS

 -- Option: LIBEDIT_LIBS

     C compiler and linker flags for ‘libedit’, used by *note readline:
     a8. module, overriding ‘pkg-config’.

 -- Option: LIBFFI_CFLAGS

 -- Option: LIBFFI_LIBS

     C compiler and linker flags for ‘libffi’, used by *note ctypes: 22.
     module, overriding ‘pkg-config’.

 -- Option: LIBMPDEC_CFLAGS

 -- Option: LIBMPDEC_LIBS

     C compiler and linker flags for ‘libmpdec’, used by *note decimal:
     2e. module, overriding ‘pkg-config’.

          備註: These environment variables have no effect unless *note
          -with-system-libmpdec: 34d. is specified.

 -- Option: LIBLZMA_CFLAGS

 -- Option: LIBLZMA_LIBS

     C compiler and linker flags for ‘liblzma’, used by *note lzma: 7e.
     module, overriding ‘pkg-config’.

 -- Option: LIBREADLINE_CFLAGS

 -- Option: LIBREADLINE_LIBS

     C compiler and linker flags for ‘libreadline’, used by *note
     readline: a8. module, overriding ‘pkg-config’.

 -- Option: LIBSQLITE3_CFLAGS

 -- Option: LIBSQLITE3_LIBS

     C compiler and linker flags for ‘libsqlite3’, used by *note
     sqlite3: ba. module, overriding ‘pkg-config’.

 -- Option: LIBUUID_CFLAGS

 -- Option: LIBUUID_LIBS

     C compiler and linker flags for ‘libuuid’, used by *note uuid: f8.
     module, overriding ‘pkg-config’.

 -- Option: PANEL_CFLAGS

 -- Option: PANEL_LIBS

     C compiler and linker flags for PANEL, overriding ‘pkg-config’.

     C compiler and linker flags for ‘libpanel’ or ‘libpanelw’, used by
     *note curses.panel: 25. module, overriding ‘pkg-config’.

 -- Option: TCLTK_CFLAGS

 -- Option: TCLTK_LIBS

     C compiler and linker flags for TCLTK, overriding ‘pkg-config’.

 -- Option: ZLIB_CFLAGS

 -- Option: ZLIB_LIBS

     C compiler and linker flags for ‘libzlib’, used by *note gzip: 5d.
     module, overriding ‘pkg-config’.


File: python.info,  Node: WebAssembly 選項,  Next: 安裝選項,  Prev: Options for third-party dependencies,  Up: 設定選項

3.3.3.5 WebAssembly 選項
........................

 -- Option: --with-emscripten-target=[browser|node]

     Set build flavor for ‘wasm32-emscripten’.

        * ‘browser’ (default): preload minimal stdlib, default MEMFS.

        * ‘node’：對 NODERAWFS 和 pthread 支援。

     在 3.11 版被加入.

 -- Option: --enable-wasm-dynamic-linking

     Turn on dynamic linking support for WASM.

     Dynamic linking enables ‘dlopen’.  File size of the executable
     increases due to limited dead code elimination and additional
     features.

     在 3.11 版被加入.

 -- Option: --enable-wasm-pthreads

     Turn on pthreads support for WASM.

     在 3.11 版被加入.


File: python.info,  Node: 安裝選項,  Next: Performance options,  Prev: WebAssembly 選項,  Up: 設定選項

3.3.3.6 安裝選項
................

 -- Option: --prefix=PREFIX

     Install architecture-independent files in PREFIX. On Unix, it
     defaults to ‘/usr/local’.

     這個值可以在 runtime 使用 *note sys.prefix: 381. 取得。

     As an example, one can use ‘--prefix="$HOME/.local/"’ to install a
     Python in its home directory.

 -- Option: --exec-prefix=EPREFIX

     Install architecture-dependent files in EPREFIX, defaults to *note
     -prefix: 1c62.

     這個值可以在 runtime 使用 *note sys.exec_prefix: 37d. 取得

 -- Option: --disable-test-modules

     Don't build nor install test modules, like the *note test: cb.
     package or the ‘_testcapi’ extension module (built and installed by
     default).

     在 3.10 版被加入.

 -- Option: --with-ensurepip=[upgrade|install|no]

     選擇在 Python 安裝時執行的 *note ensurepip: 4b. 命令：

        * ‘upgrade’ （預設）：執行 ‘python -m ensurepip --altinstall
          --upgrade’ 命令。

        * ‘install’：執行 ‘python -m ensurepip --altinstall’ 命令；

        * ‘no’：不要執行 ensurepip；

     在 3.6 版被加入.


File: python.info,  Node: Performance options,  Next: Python Debug Build,  Prev: 安裝選項,  Up: 設定選項

3.3.3.7 Performance options
...........................

Configuring Python using ‘--enable-optimizations --with-lto’ (PGO + LTO)
is recommended for best performance.  The experimental ‘--enable-bolt’
flag can also be used to improve performance.

 -- Option: --enable-optimizations

     Enable Profile Guided Optimization (PGO) using *note PROFILE_TASK:
     160d. (disabled by default).

     The C compiler Clang requires ‘llvm-profdata’ program for PGO. On
     macOS, GCC also requires it: GCC is just an alias to Clang on
     macOS.

     Disable also semantic interposition in libpython if
     ‘--enable-shared’ and GCC is used: add
     ‘-fno-semantic-interposition’ to the compiler and linker flags.

          備註: During the build, you may encounter compiler warnings
          about profile data not being available for some source files.
          These warnings are harmless, as only a subset of the code is
          exercised during profile data acquisition.  To disable these
          warnings on Clang, manually suppress them by adding
          ‘-Wno-profile-instr-unprofiled’ to *note CFLAGS: 1422.

     在 3.6 版被加入.

     在 3.10 版的變更: 在 GCC 上使用 ‘-fno-semantic-interposition’。

 -- 環境變數: PROFILE_TASK

     Environment variable used in the Makefile: Python command line
     arguments for the PGO generation task.

     預設值：‘-m test --pgo --timeout=$(TESTTIMEOUT)’。

     在 3.8 版被加入.

     在 3.13 版的變更: Task failure is no longer ignored silently.

 -- Option: --with-lto=[full|thin|no|yes]

     Enable Link Time Optimization (LTO) in any build (disabled by
     default).

     The C compiler Clang requires ‘llvm-ar’ for LTO (‘ar’ on macOS), as
     well as an LTO-aware linker (‘ld.gold’ or ‘lld’).

     在 3.6 版被加入.

     在 3.11 版被加入: To use ThinLTO feature, use ‘--with-lto=thin’ on
     Clang.

     在 3.12 版的變更: Use ThinLTO as the default optimization policy on
     Clang if the compiler accepts the flag.

 -- Option: --enable-bolt

     Enable usage of the BOLT post-link binary optimizer(1) (disabled by
     default).

     BOLT is part of the LLVM project but is not always included in
     their binary distributions.  This flag requires that ‘llvm-bolt’
     and ‘merge-fdata’ are available.

     BOLT is still a fairly new project so this flag should be
     considered experimental for now.  Because this tool operates on
     machine code its success is dependent on a combination of the build
     environment + the other optimization configure args + the CPU
     architecture, and not all combinations are supported.  BOLT
     versions before LLVM 16 are known to crash BOLT under some
     scenarios.  Use of LLVM 16 or newer for BOLT optimization is
     strongly encouraged.

     The ‘BOLT_INSTRUMENT_FLAGS’ and ‘BOLT_APPLY_FLAGS’ ‘configure’
     variables can be defined to override the default set of arguments
     for ‘llvm-bolt’ to instrument and apply BOLT data to binaries,
     respectively.

     在 3.12 版被加入.

 -- Option: BOLT_APPLY_FLAGS

     Arguments to ‘llvm-bolt’ when creating a BOLT optimized binary(2).

     在 3.12 版被加入.

 -- Option: BOLT_INSTRUMENT_FLAGS

     Arguments to ‘llvm-bolt’ when instrumenting binaries.

     在 3.12 版被加入.

 -- Option: --with-computed-gotos

     Enable computed gotos in evaluation loop (enabled by default on
     supported compilers).

 -- Option: --without-mimalloc

     Disable the fast *note mimalloc: 1c54. allocator (enabled by
     default).

     另請參閱 *note PYTHONMALLOC: c0b. 環境變數。

 -- Option: --without-pymalloc

     Disable the specialized Python memory allocator *note pymalloc:
     cb6. (enabled by default).

     另請參閱 *note PYTHONMALLOC: c0b. 環境變數。

 -- Option: --without-doc-strings

     Disable static documentation strings to reduce the memory footprint
     (enabled by default).  Documentation strings defined in Python are
     not affected.

     不要定義 ‘WITH_DOC_STRINGS’ 巨集。

     請見 ‘PyDoc_STRVAR()’ 巨集。

 -- Option: --enable-profiling

     Enable C-level code profiling with ‘gprof’ (disabled by default).

 -- Option: --with-strict-overflow

     Add ‘-fstrict-overflow’ to the C compiler flags (by default we add
     ‘-fno-strict-overflow’ instead).

   ---------- Footnotes ----------

   (1) https://github.com/llvm/llvm-project/tree/main/bolt

   (2) https://github.com/facebookarchive/BOLT


File: python.info,  Node: Python Debug Build,  Next: Debug options,  Prev: Performance options,  Up: 設定選項

3.3.3.8 Python Debug Build
..........................

A debug build is Python built with the *note -with-pydebug: 3d8.
configure option.

Effects of a debug build:

   * Display all warnings by default: the list of default warning
     filters is empty in the *note warnings: fa. module.

   * 新增 ‘d’ 到 *note sys.abiflags: a07.。

   * 新增 ‘sys.gettotalrefcount()’ 函式。

   * 新增 *note -X showrefcount: 15a. 命令列選項。

   * Add *note -d: 1c33. command line option and *note PYTHONDEBUG:
     1c34. environment variable to debug the parser.

   * Add support for the ‘__lltrace__’ variable: enable low-level
     tracing in the bytecode evaluation loop if the variable is defined.

   * Install *note debug hooks on memory allocators: 1c52. to detect
     buffer overflow and other memory errors.

   * 定義 ‘Py_DEBUG’ 和 ‘Py_REF_DEBUG’ 巨集。

   * Add runtime checks: code surrounded by ‘#ifdef Py_DEBUG’ and
     ‘#endif’.  Enable ‘assert(...)’ and ‘_PyObject_ASSERT(...)’
     assertions: don't set the ‘NDEBUG’ macro (see also the *note
     -with-assertions: 304. configure option).  Main runtime checks:

        * Add sanity checks on the function arguments.

        * Unicode and int objects are created with their memory filled
          with a pattern to detect usage of uninitialized objects.

        * Ensure that functions which can clear or replace the current
          exception are not called with an exception raised.

        * Check that deallocator functions don't change the current
          exception.

        * The garbage collector (*note gc.collect(): 16b. function) runs
          some basic checks on objects consistency.

        * The ‘Py_SAFE_DOWNCAST()’ macro checks for integer underflow
          and overflow when downcasting from wide types to narrow types.

See also the *note Python Development Mode: 1dd. and the *note
-with-trace-refs: 317. configure option.

在 3.8 版的變更: Release builds and debug builds are now ABI compatible:
defining the ‘Py_DEBUG’ macro no longer implies the ‘Py_TRACE_REFS’
macro (see the *note -with-trace-refs: 317. option).


File: python.info,  Node: Debug options,  Next: Linker options<2>,  Prev: Python Debug Build,  Up: 設定選項

3.3.3.9 Debug options
.....................

 -- Option: --with-pydebug

     *note Build Python in debug mode: 1de.: define the ‘Py_DEBUG’ macro
     (disabled by default).

 -- Option: --with-trace-refs

     Enable tracing references for debugging purpose (disabled by
     default).

     效果：

        * 定義 ‘Py_TRACE_REFS’ 巨集。

        * 新增 ‘sys.getobjects()’ 函式。

        * 新增 *note PYTHONDUMPREFS: 94a. 環境變數。

     The *note PYTHONDUMPREFS: 94a. environment variable can be used to
     dump objects and reference counts still alive at Python exit.

     *note Statically allocated objects: 723. are not traced.

     在 3.8 版被加入.

     在 3.13 版的變更: This build is now ABI compatible with release
     build and *note debug build: 1de.

 -- Option: --with-assertions

     Build with C assertions enabled (default is no): ‘assert(...);’ and
     ‘_PyObject_ASSERT(...);’.

     If set, the ‘NDEBUG’ macro is not defined in the *note OPT: 1cb4.
     compiler variable.

     See also the *note -with-pydebug: 3d8. option (*note debug build:
     1de.) which also enables assertions.

     在 3.6 版被加入.

 -- Option: --with-valgrind

     啟用 Valgrind 支援（預設不啟用）。

 -- Option: --with-dtrace

     啟用 DTrace 支援（預設不啟用）。

     See *note Instrumenting CPython with DTrace and SystemTap: c13.

     在 3.6 版被加入.

 -- Option: --with-address-sanitizer

     Enable AddressSanitizer memory error detector, ‘asan’ (default is
     no).

     在 3.6 版被加入.

 -- Option: --with-memory-sanitizer

     Enable MemorySanitizer allocation error detector, ‘msan’ (default
     is no).

     在 3.6 版被加入.

 -- Option: --with-undefined-behavior-sanitizer

     Enable UndefinedBehaviorSanitizer undefined behaviour detector,
     ‘ubsan’ (default is no).

     在 3.6 版被加入.

 -- Option: --with-thread-sanitizer

     Enable ThreadSanitizer data race detector, ‘tsan’ (default is no).

     在 3.13 版被加入.


File: python.info,  Node: Linker options<2>,  Next: 函式庫選項,  Prev: Debug options,  Up: 設定選項

3.3.3.10 Linker options
.......................

 -- Option: --enable-shared

     Enable building a shared Python library: ‘libpython’ (default is
     no).

 -- Option: --without-static-libpython

     Do not build ‘libpythonMAJOR.MINOR.a’ and do not install ‘python.o’
     (built and enabled by default).

     在 3.10 版被加入.


File: python.info,  Node: 函式庫選項,  Next: Security Options,  Prev: Linker options<2>,  Up: 設定選項

3.3.3.11 函式庫選項
...................

 -- Option: --with-libs='lib1 ...'

     Link against additional libraries (default is no).

 -- Option: --with-system-expat

     Build the ‘pyexpat’ module using an installed ‘expat’ library
     (default is no).

 -- Option: --with-system-libmpdec

     Build the ‘_decimal’ extension module using an installed
     ‘mpdecimal’ library, see the *note decimal: 2e. module (default is
     yes).

     在 3.3 版被加入.

     在 3.13 版的變更: Default to using the installed ‘mpdecimal’
     library.

     Deprecated since version 3.13, will be removed in version 3.15: A
     copy of the ‘mpdecimal’ library sources will no longer be
     distributed with Python 3.15.

     也參考
     ......

     *note LIBMPDEC_CFLAGS: 1c95. and *note LIBMPDEC_LIBS: 1c96.

 -- Option: --with-readline=readline|editline

     Designate a backend library for the *note readline: a8. module.

        * readline: Use readline as the backend.

        * editline: Use editline as the backend.

     在 3.10 版被加入.

 -- Option: --without-readline

     Don't build the *note readline: a8. module (built by default).

     不要定義 ‘HAVE_LIBREADLINE’ 巨集。

     在 3.10 版被加入.

 -- Option: --with-libm=STRING

     Override ‘libm’ math library to 'STRING' (default is
     system-dependent).

 -- Option: --with-libc=STRING

     Override ‘libc’ C library to 'STRING' (default is
     system-dependent).

 -- Option: --with-openssl=DIR

     Root of the OpenSSL directory.

     在 3.7 版被加入.

 -- Option: --with-openssl-rpath=[no|auto|DIR]

     Set runtime library directory (rpath) for OpenSSL libraries:

        * ‘no’ (default): don't set rpath;

        * ‘auto’: auto-detect rpath from *note -with-openssl: 1cc2. and
          ‘pkg-config’;

        * 'DIR': set an explicit rpath.

     在 3.10 版被加入.


File: python.info,  Node: Security Options,  Next: macOS 選項,  Prev: 函式庫選項,  Up: 設定選項

3.3.3.12 Security Options
.........................

 -- Option: --with-hash-algorithm=[fnv|siphash13|siphash24]

     Select hash algorithm for use in ‘Python/pyhash.c’:

        * ‘siphash13’ (default);

        * ‘siphash24’；

        * ‘fnv’。

     在 3.4 版被加入.

     在 3.11 版被加入: ‘siphash13’ is added and it is the new default.

 -- Option:
          --with-builtin-hashlib-hashes=md5,sha1,sha256,sha512,sha3,blake2

     內建雜湊模組：

        * ‘md5’；

        * ‘sha1’；

        * ‘sha256’；

        * ‘sha512’；

        * ‘sha3’ (with shake);

        * ‘blake2’。

     在 3.9 版被加入.

 -- Option: --with-ssl-default-suites=[python|openssl|STRING]

     Override the OpenSSL default cipher suites string:

        * ‘python’ (default): use Python's preferred selection;

        * ‘openssl’: leave OpenSSL's defaults untouched;

        * 'STRING': use a custom string

     請見 *note ssl: bb. 模組。

     在 3.7 版被加入.

     在 3.10 版的變更: The settings ‘python’ and 'STRING' also set TLS
     1.2 as minimum protocol version.


File: python.info,  Node: macOS 選項,  Next: iOS Options,  Prev: Security Options,  Up: 設定選項

3.3.3.13 macOS 選項
...................

See Mac/README.rst(1).

 -- Option: --enable-universalsdk

 -- Option: --enable-universalsdk=SDKDIR

     Create a universal binary build.  'SDKDIR' specifies which macOS
     SDK should be used to perform the build (default is no).

 -- Option: --enable-framework

 -- Option: --enable-framework=INSTALLDIR

     Create a Python.framework rather than a traditional Unix install.
     Optional 'INSTALLDIR' specifies the installation path (default is
     no).

 -- Option: --with-universal-archs=ARCH

     Specify the kind of universal binary that should be created.  This
     option is only valid when *note -enable-universalsdk: 90f. is set.

     選項：

        * ‘universal2’；

        * ‘32-bit’；

        * ‘64-bit’；

        * ‘3-way’；

        * ‘intel’；

        * ‘intel-32’；

        * ‘intel-64’；

        * ‘all’。

 -- Option: --with-framework-name=FRAMEWORK

     Specify the name for the python framework on macOS only valid when
     *note -enable-framework: 1cc9. is set (default: ‘Python’).

 -- Option: --with-app-store-compliance

 -- Option: --with-app-store-compliance=PATCH-FILE

     The Python standard library contains strings that are known to
     trigger automated inspection tool errors when submitted for
     distribution by the macOS and iOS App Stores.  If enabled, this
     option will apply the list of patches that are known to correct app
     store compliance.  A custom patch file can also be specified.  This
     option is disabled by default.

     在 3.13 版被加入.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Mac/README.rst


File: python.info,  Node: iOS Options,  Next: Cross Compiling Options,  Prev: macOS 選項,  Up: 設定選項

3.3.3.14 iOS Options
....................

See iOS/README.rst(1).

 -- Option: --enable-framework=INSTALLDIR

     Create a Python.framework.  Unlike macOS, the 'INSTALLDIR' argument
     specifying the installation path is mandatory.

 -- Option: --with-framework-name=FRAMEWORK

     Specify the name for the framework (default: ‘Python’).

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/iOS/README.rst


File: python.info,  Node: Cross Compiling Options,  Prev: iOS Options,  Up: 設定選項

3.3.3.15 Cross Compiling Options
................................

Cross compiling, also known as cross building, can be used to build
Python for another CPU architecture or platform.  Cross compiling
requires a Python interpreter for the build platform.  The version of
the build Python must match the version of the cross compiled host
Python.

 -- Option: --build=BUILD

     configure for building on BUILD, usually guessed by ‘config.guess’.

 -- Option: --host=HOST

     cross-compile to build programs to run on HOST (target platform)

 -- Option: --with-build-python=path/to/python

     path to build ‘python’ binary for cross compiling

     在 3.11 版被加入.

 -- Option: CONFIG_SITE=file

     An environment variable that points to a file with configure
     overrides.

     Example 'config.site' file:

          # config.site-aarch64
          ac_cv_buggy_getaddrinfo=no
          ac_cv_file__dev_ptmx=yes
          ac_cv_file__dev_ptc=no

 -- Option: HOSTRUNNER

     Program to run CPython for the host platform for cross-compilation.

     在 3.11 版被加入.

Cross compiling example:

     CONFIG_SITE=config.site-aarch64 ../configure \
         --build=x86_64-pc-linux-gnu \
         --host=aarch64-unknown-linux-gnu \
         --with-build-python=../x86_64/python


File: python.info,  Node: Python Build System,  Next: Compiler and linker flags,  Prev: 設定選項,  Up: 配置 Python

3.3.4 Python Build System
-------------------------

* Menu:

* Main files of the build system::
* 主要建置步驟::
* 主要 Makefile 目標::
* C 擴充模組::


File: python.info,  Node: Main files of the build system,  Next: 主要建置步驟,  Up: Python Build System

3.3.4.1 Main files of the build system
......................................

   * ‘configure.ac’ => ‘configure’；

   * ‘Makefile.pre.in’ => ‘Makefile’ (created by ‘configure’);

   * ‘pyconfig.h’ (created by ‘configure’)；

   * ‘Modules/Setup’: C extensions built by the Makefile using
     ‘Module/makesetup’ shell script;


File: python.info,  Node: 主要建置步驟,  Next: 主要 Makefile 目標,  Prev: Main files of the build system,  Up: Python Build System

3.3.4.2 主要建置步驟
....................

   * C files (‘.c’) are built as object files (‘.o’).

   * A static ‘libpython’ library (‘.a’) is created from objects files.

   * ‘python.o’ and the static ‘libpython’ library are linked into the
     final ‘python’ program.

   * C extensions are built by the Makefile (see ‘Modules/Setup’).


File: python.info,  Node: 主要 Makefile 目標,  Next: C 擴充模組,  Prev: 主要建置步驟,  Up: Python Build System

3.3.4.3 主要 Makefile 目標
..........................

* Menu:

* make::
* make platform::
* make profile-opt::
* make clean::
* make distclean::
* make install::
* make test::
* make buildbottest::
* make regen-all::


File: python.info,  Node: make,  Next: make platform,  Up: 主要 Makefile 目標

3.3.4.4 make
............

For the most part, when rebuilding after editing some code or refreshing
your checkout from upstream, all you need to do is execute ‘make’, which
(per Make's semantics) builds the default target, the first one defined
in the Makefile.  By tradition (including in the CPython project) this
is usually the ‘all’ target.  The ‘configure’ script expands an
‘autoconf’ variable, ‘@DEF_MAKE_ALL_RULE@’ to describe precisely which
targets ‘make all’ will build.  The three choices are:

   * ‘profile-opt’ (configured with ‘--enable-optimizations’)

   * ‘build_wasm’ (configured with ‘--with-emscripten-target’)

   * ‘build_all’ (configured without explicitly using either of the
     others)

Depending on the most recent source file changes, Make will rebuild any
targets (object files and executables) deemed out-of-date, including
running ‘configure’ again if necessary.  Source/target dependencies are
many and maintained manually however, so Make sometimes doesn't have all
the information necessary to correctly detect all targets which need to
be rebuilt.  Depending on which targets aren't rebuilt, you might
experience a number of problems.  If you have build or test problems
which you can't otherwise explain, ‘make clean && make’ should work
around most dependency problems, at the expense of longer build times.


File: python.info,  Node: make platform,  Next: make profile-opt,  Prev: make,  Up: 主要 Makefile 目標

3.3.4.5 make platform
.....................

Build the ‘python’ program, but don't build the standard library
extension modules.  This generates a file named ‘platform’ which
contains a single line describing the details of the build platform,
e.g., ‘macosx-14.3-arm64-3.12’ or ‘linux-x86_64-3.13’.


File: python.info,  Node: make profile-opt,  Next: make clean,  Prev: make platform,  Up: 主要 Makefile 目標

3.3.4.6 make profile-opt
........................

Build Python using profile-guided optimization (PGO). You can use the
configure *note -enable-optimizations: 806. option to make this the
default target of the ‘make’ command (‘make all’ or just ‘make’).


File: python.info,  Node: make clean,  Next: make distclean,  Prev: make profile-opt,  Up: 主要 Makefile 目標

3.3.4.7 make clean
..................

Remove built files.


File: python.info,  Node: make distclean,  Next: make install,  Prev: make clean,  Up: 主要 Makefile 目標

3.3.4.8 make distclean
......................

In addition to the work done by ‘make clean’, remove files created by
the configure script.  ‘configure’ will have to be run before building
again.  (1)

   ---------- Footnotes ----------

   (1) ‘git clean -fdx’ is an even more extreme way to "clean" your
checkout.  It removes all files not known to Git.  When bug hunting
using ‘git bisect’, this is recommended between probes
(https://github.com/python/cpython/issues/114505#issuecomment-1907021718)
to guarantee a completely clean build.  'Use with care', as it will
delete all files not checked into Git, including your new, uncommitted
work.


File: python.info,  Node: make install,  Next: make test,  Prev: make distclean,  Up: 主要 Makefile 目標

3.3.4.9 make install
....................

Build the ‘all’ target and install Python.


File: python.info,  Node: make test,  Next: make buildbottest,  Prev: make install,  Up: 主要 Makefile 目標

3.3.4.10 make test
..................

Build the ‘all’ target and run the Python test suite with the
‘--fast-ci’ option.  Variables:

   * ‘TESTOPTS’: additional regrtest command-line options.

   * ‘TESTPYTHONOPTS’: additional Python command-line options.

   * ‘TESTTIMEOUT’: timeout in seconds (default: 10 minutes).


File: python.info,  Node: make buildbottest,  Next: make regen-all,  Prev: make test,  Up: 主要 Makefile 目標

3.3.4.11 make buildbottest
..........................

This is similar to ‘make test’, but uses the ‘--slow-ci’ option and
default timeout of 20 minutes, instead of ‘--fast-ci’ option.


File: python.info,  Node: make regen-all,  Prev: make buildbottest,  Up: 主要 Makefile 目標

3.3.4.12 make regen-all
.......................

Regenerate (almost) all generated files.  These include (but are not
limited to) bytecode cases, and parser generator file.  ‘make
regen-stdlib-module-names’ and ‘autoconf’ must be run separately for the
remaining *note generated files: 1c6a.


File: python.info,  Node: C 擴充模組,  Prev: 主要 Makefile 目標,  Up: Python Build System

3.3.4.13 C 擴充模組
...................

Some C extensions are built as built-in modules, like the ‘sys’ module.
They are built with the ‘Py_BUILD_CORE_BUILTIN’ macro defined.  Built-in
modules have no ‘__file__’ attribute:

     >>> import sys
     >>> sys
     <module 'sys' (built-in)>
     >>> sys.__file__
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     AttributeError: module 'sys' has no attribute '__file__'

Other C extensions are built as dynamic libraries, like the ‘_asyncio’
module.  They are built with the ‘Py_BUILD_CORE_MODULE’ macro defined.
Example on Linux x86-64:

     >>> import _asyncio
     >>> _asyncio
     <module '_asyncio' from '/usr/lib64/python3.9/lib-dynload/_asyncio.cpython-39-x86_64-linux-gnu.so'>
     >>> _asyncio.__file__
     '/usr/lib64/python3.9/lib-dynload/_asyncio.cpython-39-x86_64-linux-gnu.so'

‘Modules/Setup’ is used to generate Makefile targets to build C
extensions.  At the beginning of the files, C extensions are built as
built-in modules.  Extensions defined after the ‘*shared*’ marker are
built as dynamic libraries.

The ‘PyAPI_FUNC()’, ‘PyAPI_DATA()’ and *note PyMODINIT_FUNC: 1442.
macros of ‘Include/exports.h’ are defined differently depending if the
‘Py_BUILD_CORE_MODULE’ macro is defined:

   * 如果定義了 ‘Py_BUILD_CORE_MODULE’，則使用 ‘Py_EXPORTED_SYMBOL’

   * 否則使用 ‘Py_IMPORTED_SYMBOL’。

If the ‘Py_BUILD_CORE_BUILTIN’ macro is used by mistake on a C extension
built as a shared library, its ‘PyInit_XXX()’ function is not exported,
causing an *note ImportError: 352. on import.


File: python.info,  Node: Compiler and linker flags,  Prev: Python Build System,  Up: 配置 Python

3.3.5 Compiler and linker flags
-------------------------------

Options set by the ‘./configure’ script and environment variables and
used by ‘Makefile’.

* Menu:

* Preprocessor flags::
* 編譯器旗標::
* Linker flags::


File: python.info,  Node: Preprocessor flags,  Next: 編譯器旗標,  Up: Compiler and linker flags

3.3.5.1 Preprocessor flags
..........................

 -- 環境變數: CONFIGURE_CPPFLAGS

     Value of *note CPPFLAGS: 1424. variable passed to the ‘./configure’
     script.

     在 3.6 版被加入.

 -- 環境變數: CPPFLAGS

     (Objective) C/C++ preprocessor flags, e.g.  ‘-IINCLUDE_DIR’ if you
     have headers in a nonstandard directory 'include_dir'.

     Both *note CPPFLAGS: 1424. and *note LDFLAGS: 1423. need to contain
     the shell's value to be able to build extension modules using the
     directories specified in the environment variables.

 -- 環境變數: BASECPPFLAGS

     在 3.4 版被加入.

 -- 環境變數: PY_CPPFLAGS

     Extra preprocessor flags added for building the interpreter object
     files.

     Default: ‘$(BASECPPFLAGS) -I. -I$(srcdir)/Include
     $(CONFIGURE_CPPFLAGS) $(CPPFLAGS)’.

     在 3.2 版被加入.


File: python.info,  Node: 編譯器旗標,  Next: Linker flags,  Prev: Preprocessor flags,  Up: Compiler and linker flags

3.3.5.2 編譯器旗標
..................

 -- 環境變數: CC

     C 編譯器指令。

     Example: ‘gcc -pthread’.

 -- 環境變數: CXX

     C++ 編譯器指令。

     範例：‘g++ -pthread’。

 -- 環境變數: CFLAGS

     C 編譯器旗標。

 -- 環境變數: CFLAGS_NODIST

     *note CFLAGS_NODIST: 1cec. is used for building the interpreter and
     stdlib C extensions.  Use it when a compiler flag should 'not' be
     part of *note CFLAGS: 1422. once Python is installed (gh-65320(1)).

     In particular, *note CFLAGS: 1422. should not contain:

        * the compiler flag ‘-I’ (for setting the search path for
          include files).  The ‘-I’ flags are processed from left to
          right, and any flags in *note CFLAGS: 1422. would take
          precedence over user- and package-supplied ‘-I’ flags.

        * hardening flags such as ‘-Werror’ because distributions cannot
          control whether packages installed by users conform to such
          heightened standards.

     在 3.5 版被加入.

 -- 環境變數: COMPILEALL_OPTS

     Options passed to the *note compileall: 19. command line when
     building PYC files in ‘make install’.  Default: ‘-j0’.

     在 3.12 版被加入.

 -- 環境變數: EXTRA_CFLAGS

     額外的 C 編譯器旗標。

 -- 環境變數: CONFIGURE_CFLAGS

     Value of *note CFLAGS: 1422. variable passed to the ‘./configure’
     script.

     在 3.2 版被加入.

 -- 環境變數: CONFIGURE_CFLAGS_NODIST

     Value of *note CFLAGS_NODIST: 1cec. variable passed to the
     ‘./configure’ script.

     在 3.5 版被加入.

 -- 環境變數: BASECFLAGS

     基本編譯器旗標。

 -- 環境變數: OPT

     最佳化旗標。

 -- 環境變數: CFLAGS_ALIASING

     Strict or non-strict aliasing flags used to compile
     ‘Python/dtoa.c’.

     在 3.7 版被加入.

 -- 環境變數: CCSHARED

     Compiler flags used to build a shared library.

     例如說 ‘-fPIC’ 被使用於 Linux 與 BSD 上。

 -- 環境變數: CFLAGSFORSHARED

     Extra C flags added for building the interpreter object files.

     Default: ‘$(CCSHARED)’ when *note -enable-shared: 807. is used, or
     an empty string otherwise.

 -- 環境變數: PY_CFLAGS

     Default: ‘$(BASECFLAGS) $(OPT) $(CONFIGURE_CFLAGS) $(CFLAGS)
     $(EXTRA_CFLAGS)’.

 -- 環境變數: PY_CFLAGS_NODIST

     Default: ‘$(CONFIGURE_CFLAGS_NODIST) $(CFLAGS_NODIST)
     -I$(srcdir)/Include/internal’.

     在 3.5 版被加入.

 -- 環境變數: PY_STDMODULE_CFLAGS

     C flags used for building the interpreter object files.

     Default: ‘$(PY_CFLAGS) $(PY_CFLAGS_NODIST) $(PY_CPPFLAGS)
     $(CFLAGSFORSHARED)’.

     在 3.7 版被加入.

 -- 環境變數: PY_CORE_CFLAGS

     Default: ‘$(PY_STDMODULE_CFLAGS) -DPy_BUILD_CORE’.

     在 3.2 版被加入.

 -- 環境變數: PY_BUILTIN_MODULE_CFLAGS

     Compiler flags to build a standard library extension module as a
     built-in module, like the *note posix: 9b. module.

     Default: ‘$(PY_STDMODULE_CFLAGS) -DPy_BUILD_CORE_BUILTIN’.

     在 3.8 版被加入.

 -- 環境變數: PURIFY

     Purify command.  Purify is a memory debugger program.

     Default: empty string (not used).

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/65320


File: python.info,  Node: Linker flags,  Prev: 編譯器旗標,  Up: Compiler and linker flags

3.3.5.3 Linker flags
....................

 -- 環境變數: LINKCC

     Linker command used to build programs like ‘python’ and
     ‘_testembed’.

     Default: ‘$(PURIFY) $(CC)’.

 -- 環境變數: CONFIGURE_LDFLAGS

     Value of *note LDFLAGS: 1423. variable passed to the ‘./configure’
     script.

     Avoid assigning *note CFLAGS: 1422, *note LDFLAGS: 1423, etc.  so
     users can use them on the command line to append to these values
     without stomping the pre-set values.

     在 3.2 版被加入.

 -- 環境變數: LDFLAGS_NODIST

     *note LDFLAGS_NODIST: 1cfe. is used in the same manner as *note
     CFLAGS_NODIST: 1cec.  Use it when a linker flag should 'not' be
     part of *note LDFLAGS: 1423. once Python is installed
     (gh-65320(1)).

     In particular, *note LDFLAGS: 1423. should not contain:

        * the compiler flag ‘-L’ (for setting the search path for
          libraries).  The ‘-L’ flags are processed from left to right,
          and any flags in *note LDFLAGS: 1423. would take precedence
          over user- and package-supplied ‘-L’ flags.

 -- 環境變數: CONFIGURE_LDFLAGS_NODIST

     Value of *note LDFLAGS_NODIST: 1cfe. variable passed to the
     ‘./configure’ script.

     在 3.8 版被加入.

 -- 環境變數: LDFLAGS

     Linker flags, e.g.  ‘-LLIB_DIR’ if you have libraries in a
     nonstandard directory 'lib_dir'.

     Both *note CPPFLAGS: 1424. and *note LDFLAGS: 1423. need to contain
     the shell's value to be able to build extension modules using the
     directories specified in the environment variables.

 -- 環境變數: LIBS

     Linker flags to pass libraries to the linker when linking the
     Python executable.

     範例：‘-lrt’。

 -- 環境變數: LDSHARED

     Command to build a shared library.

     預設值：‘@LDSHARED@ $(PY_LDFLAGS)’。

 -- 環境變數: BLDSHARED

     Command to build ‘libpython’ shared library.

     預設值：‘@BLDSHARED@ $(PY_CORE_LDFLAGS)’。

 -- 環境變數: PY_LDFLAGS

     預設值：‘$(CONFIGURE_LDFLAGS) $(LDFLAGS)’。

 -- 環境變數: PY_LDFLAGS_NODIST

     預設值：‘$(CONFIGURE_LDFLAGS_NODIST) $(LDFLAGS_NODIST)’。

     在 3.8 版被加入.

 -- 環境變數: PY_CORE_LDFLAGS

     Linker flags used for building the interpreter object files.

     在 3.8 版被加入.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/65320


File: python.info,  Node: 在 Windows 上使用 Python,  Next: 在 Mac 系統使用 Python,  Prev: 配置 Python,  Up: Python 的設置與使用

3.4 在 Windows 上使用 Python
============================

This document aims to give an overview of Windows-specific behaviour you
should know about when using Python on Microsoft Windows.

Unlike most Unix systems and services, Windows does not include a system
supported installation of Python.  To make Python available, the CPython
team has compiled Windows installers with every release(1) for many
years.  These installers are primarily intended to add a per-user
installation of Python, with the core interpreter and library being used
by a single user.  The installer is also able to install for all users
of a single machine, and a separate ZIP file is available for
application-local distributions.

As specified in PEP 11(2), a Python release only supports a Windows
platform while Microsoft considers the platform under extended support.
This means that Python 3.13 supports Windows 8.1 and newer.  If you
require Windows 7 support, please install Python 3.8.

There are a number of different installers available for Windows, each
with certain benefits and downsides.

*note The full installer: 1d08. contains all components and is the best
option for developers using Python for any kind of project.

*note The Microsoft Store package: 1aec. is a simple installation of
Python that is suitable for running scripts and packages, and using IDLE
or other development environments.  It requires Windows 10 and above,
but can be safely installed without corrupting other programs.  It also
provides many convenient commands for launching Python and its tools.

*note nuget.org 套件: 1d09. are lightweight installations intended for
continuous integration systems.  It can be used to build Python packages
or run scripts, but is not updateable and has no user interface tools.

*note The embeddable package: 1d0a. is a minimal package of Python
suitable for embedding into a larger application.

* Menu:

* The full installer::
* The Microsoft Store package::
* nuget.org 套件: nuget org 套件.
* The embeddable package::
* Alternative bundles::
* 設定 Python::
* UTF-8 模式::
* Python Launcher for Windows::
* 找尋模組::
* 額外的模組::
* 編譯 Python 在 Windows::
* 其他平台::

   ---------- Footnotes ----------

   (1) https://www.python.org/downloads/

   (2) https://peps.python.org/pep-0011/


File: python.info,  Node: The full installer,  Next: The Microsoft Store package,  Up: 在 Windows 上使用 Python

3.4.1 The full installer
------------------------

* Menu:

* 安裝步驟::
* Removing the MAX_PATH Limitation::
* 安裝排除使用者介面::
* 當安裝時不下載::
* Modifying an install::
* Installing Free-threaded Binaries::


File: python.info,  Node: 安裝步驟,  Next: Removing the MAX_PATH Limitation,  Up: The full installer

3.4.1.1 安裝步驟
................

Four Python 3.13 installers are available for download - two each for
the 32-bit and 64-bit versions of the interpreter.  The 'web installer'
is a small initial download, and it will automatically download the
required components as necessary.  The 'offline installer' includes the
components necessary for a default installation and only requires an
internet connection for optional features.  See *note 當安裝時不下載:
1d0d. for other ways to avoid downloading during installation.

After starting the installer, one of two options may be selected:

[image src="python-figures/win_installer.png"]


如果你選擇「馬上安裝」：

   * You will 'not' need to be an administrator (unless a system update
     for the C Runtime Library is required or you install the *note
     Python Launcher for Windows: 562. for all users)

   * Python will be installed into your user directory

   * The *note Python Launcher for Windows: 562. will be installed
     according to the option at the bottom of the first page

   * The standard library, test suite, launcher and pip will be
     installed

   * 如果選擇，安裝目錄將被加入到你的 ‘PATH’

   * 安裝捷徑將只能被目前使用者所看見

選擇「客製化安裝」將允許你選擇所需的項目進行安裝，安裝位置與其他選擇或安
裝後的所需進行的動作。你將需要使用此選項「除錯特徵」或「二進位方式」進行
安裝。

To perform an all-users installation, you should select "Customize
installation".  In this case:

   * You may be required to provide administrative credentials or
     approval

   * Python will be installed into the Program Files directory

   * The *note Python Launcher for Windows: 562. will be installed into
     the Windows directory

   * Optional features may be selected during installation

   * The standard library can be pre-compiled to bytecode

   * If selected, the install directory will be added to the system
     ‘PATH’

   * 捷徑將被所有使用者所見


File: python.info,  Node: Removing the MAX_PATH Limitation,  Next: 安裝排除使用者介面,  Prev: 安裝步驟,  Up: The full installer

3.4.1.2 Removing the MAX_PATH Limitation
........................................

Windows historically has limited path lengths to 260 characters.  This
meant that paths longer than this would not resolve and errors would
result.

In the latest versions of Windows, this limitation can be expanded to
approximately 32,000 characters.  Your administrator will need to
activate the "Enable Win32 long paths" group policy, or set
‘LongPathsEnabled’ to ‘1’ in the registry key
‘HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem’.

This allows the *note open(): 4c0. function, the *note os: 91. module
and most other path functionality to accept and return paths longer than
260 characters.

After changing the above option, no further configuration is required.

在 3.6 版的變更: Support for long paths was enabled in Python.


File: python.info,  Node: 安裝排除使用者介面,  Next: 當安裝時不下載,  Prev: Removing the MAX_PATH Limitation,  Up: The full installer

3.4.1.3 安裝排除使用者介面
..........................

All of the options available in the installer UI can also be specified
from the command line, allowing scripted installers to replicate an
installation on many machines without user interaction.  These options
may also be set without suppressing the UI in order to change some of
the defaults.

The following options (found by executing the installer with ‘/?’) can
be passed into the installer:

名稱                      描述
                          
---------------------------------------------------------------------------------------
                          
/passive                  to display progress without requiring user interaction
                          
                          
/quiet                    to install/uninstall without displaying any UI
                          
                          
/simple                   to prevent user customization
                          
                          
/uninstall                to remove Python (without confirmation)
                          
                          
/layout [directory]       to pre-download all components
                          
                          
/log [filename]           to specify log files location
                          

All other options are passed as ‘name=value’, where the value is usually
‘0’ to disable a feature, ‘1’ to enable a feature, or a path.  The full
list of available options is shown below.

名稱                            描述                                       預設
                                                                           
----------------------------------------------------------------------------------------------------------
                                                                           
InstallAllUsers                 Perform a system-wide installation.        0
                                                                           
                                                                           
TargetDir                       安裝目錄                                   Selected based on
                                                                           InstallAllUsers
                                                                           
                                                                           
DefaultAllUsersTargetDir        The default installation directory for     ‘%ProgramFiles%\Python X.Y’
                                all-user installs                          或
                                                                           ‘%ProgramFiles(x86)%\Python
                                                                           X.Y’
                                                                           
                                                                           
DefaultJustForMeTargetDir       預設安裝目錄給 只有給我 安裝方式           ‘%LocalAppData%\Programs\Python\PythonXY’
                                                                           或
                                                                           ‘%LocalAppData%\Programs\Python\PythonXY-32’
                                                                           或
                                                                           ‘%LocalAppData%\Programs\Python\PythonXY-64’
                                                                           
                                                                           
DefaultCustomTargetDir          The default custom install directory       (empty)
                                displayed in the UI                        
                                
                                                                           
AssociateFiles                  當執行程序也被安裝時創造檔案關聯           1
                                                                           
                                                                           
CompileAll                      編譯所有 ‘.py’ 檔案為 ‘.pyc’。             0
                                                                           
                                                                           
PrependPath                     Prepend install and Scripts directories    0
                                to ‘PATH’ and add ‘.PY’ to ‘PATHEXT’       
                                
                                                                           
AppendPath                      Append install and Scripts directories     0
                                to ‘PATH’ and add ‘.PY’ to ‘PATHEXT’       
                                
                                                                           
Shortcuts                       Create shortcuts for the interpreter,      1
                                documentation and IDLE if installed.       
                                
                                                                           
Include_doc                     安裝Python文件                             1
                                                                           
                                                                           
Include_debug                   Install debug binaries                     0
                                                                           
                                                                           
Include_dev                     Install developer headers and libraries.   1
                                Omitting this may lead to an unusable      
                                installation.
                                
                                                                           
Include_exe                     Install ‘python.exe’ and related files.    1
                                Omitting this may lead to an unusable      
                                installation.
                                
                                                                           
Include_launcher                安裝                                       1
                                *note Python Launcher for Windows: 562.。  
                                
                                                                           
InstallLauncherAllUsers         Installs the launcher for all users.       1
                                Also requires ‘Include_launcher’ to be     
                                set to 1
                                
                                                                           
Include_lib                     Install standard library and extension     1
                                modules.  Omitting this may lead to an     
                                unusable installation.
                                
                                                                           
Include_pip                     Install bundled pip and setuptools         1
                                                                           
                                                                           
Include_symbols                 Install debugging symbols (‘*.pdb’)        0
                                                                           
                                                                           
Include_tcltk                   Install Tcl/Tk support and IDLE            1
                                                                           
                                                                           
Include_test                    Install standard library test suite        1
                                                                           
                                                                           
Include_tools                   Install utility scripts                    1
                                                                           
                                                                           
LauncherOnly                    Only installs the launcher.  This will     0
                                override most other options.               
                                
                                                                           
SimpleInstall                   Disable most install UI                    0
                                                                           
                                                                           
SimpleInstallDescription        A custom message to display when the       (empty)
                                simplified install UI is used.             
                                

For example, to silently install a default, system-wide Python
installation, you could use the following command (from an elevated
command prompt):

     python-3.9.0.exe /quiet InstallAllUsers=1 PrependPath=1 Include_test=0

To allow users to easily install a personal copy of Python without the
test suite, you could provide a shortcut with the following command.
This will display a simplified initial page and disallow customization:

     python-3.9.0.exe InstallAllUsers=0 Include_launcher=0 Include_test=0
         SimpleInstall=1 SimpleInstallDescription="Just for me, no test suite."

(Note that omitting the launcher also omits file associations, and is
only recommended for per-user installs when there is also a system-wide
installation that included the launcher.)

The options listed above can also be provided in a file named
‘unattend.xml’ alongside the executable.  This file specifies a list of
options and values.  When a value is provided as an attribute, it will
be converted to a number if possible.  Values provided as element text
are always left as strings.  This example file sets the same options as
the previous example:

     <Options>
         <Option Name="InstallAllUsers" Value="no" />
         <Option Name="Include_launcher" Value="0" />
         <Option Name="Include_test" Value="no" />
         <Option Name="SimpleInstall" Value="yes" />
         <Option Name="SimpleInstallDescription">Just for me, no test suite</Option>
     </Options>


File: python.info,  Node: 當安裝時不下載,  Next: Modifying an install,  Prev: 安裝排除使用者介面,  Up: The full installer

3.4.1.4 當安裝時不下載
......................

As some features of Python are not included in the initial installer
download, selecting those features may require an internet connection.
To avoid this need, all possible components may be downloaded on-demand
to create a complete 'layout' that will no longer require an internet
connection regardless of the selected features.  Note that this download
may be bigger than required, but where a large number of installations
are going to be performed it is very useful to have a locally cached
copy.

Execute the following command from Command Prompt to download all
possible required files.  Remember to substitute ‘python-3.9.0.exe’ for
the actual name of your installer, and to create layouts in their own
directories to avoid collisions between files with the same name.

     python-3.9.0.exe /layout [optional target directory]

You may also specify the ‘/quiet’ option to hide the progress display.


File: python.info,  Node: Modifying an install,  Next: Installing Free-threaded Binaries,  Prev: 當安裝時不下載,  Up: The full installer

3.4.1.5 Modifying an install
............................

Once Python has been installed, you can add or remove features through
the Programs and Features tool that is part of Windows.  Select the
Python entry and choose "Uninstall/Change" to open the installer in
maintenance mode.

"Modify" allows you to add or remove features by modifying the
checkboxes - unchanged checkboxes will not install or remove anything.
Some options cannot be changed in this mode, such as the install
directory; to modify these, you will need to remove and then reinstall
Python completely.

"Repair" will verify all the files that should be installed using the
current settings and replace any that have been removed or modified.

"Uninstall" will remove Python entirely, with the exception of the *note
Python Launcher for Windows: 562, which has its own entry in Programs
and Features.


File: python.info,  Node: Installing Free-threaded Binaries,  Prev: Modifying an install,  Up: The full installer

3.4.1.6 Installing Free-threaded Binaries
.........................................

在 3.13 版被加入: (Experimental)

     備註: Everything described in this section is considered
     experimental, and should be expected to change in future releases.

To install pre-built binaries with free-threading enabled (see PEP
703(1)), you should select "Customize installation".  The second page of
options includes the "Download free-threaded binaries" checkbox.

[image src="python-figures/win_install_freethreaded.png"]


Selecting this option will download and install additional binaries to
the same location as the main Python install.  The main executable is
called ‘python3.13t.exe’, and other binaries either receive a ‘t’ suffix
or a full ABI suffix.  Python source files and bundled third-party
dependencies are shared with the main install.

The free-threaded version is registered as a regular Python install with
the tag ‘3.13t’ (with a ‘-32’ or ‘-arm64’ suffix as normal for those
platforms).  This allows tools to discover it, and for the *note Python
Launcher for Windows: 562. to support ‘py.exe -3.13t’.  Note that the
launcher will interpret ‘py.exe -3’ (or a ‘python3’ shebang) as "the
latest 3.x install", which will prefer the free-threaded binaries over
the regular ones, while ‘py.exe -3.13’ will not.  If you use the short
style of option, you may prefer to not install the free-threaded
binaries at this time.

To specify the install option at the command line, use
‘Include_freethreaded=1’.  See *note 當安裝時不下載: 1d0d. for
instructions on pre-emptively downloading the additional binaries for
offline install.  The options to include debug symbols and binaries also
apply to the free-threaded builds.

Free-threaded binaries are also available *note on nuget.org: 1d09.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0703/


File: python.info,  Node: The Microsoft Store package,  Next: nuget org 套件,  Prev: The full installer,  Up: 在 Windows 上使用 Python

3.4.2 The Microsoft Store package
---------------------------------

在 3.7.2 版被加入.

The Microsoft Store package is an easily installable Python interpreter
that is intended mainly for interactive use, for example, by students.

To install the package, ensure you have the latest Windows 10 updates
and search the Microsoft Store app for "Python 3.13".  Ensure that the
app you select is published by the Python Software Foundation, and
install it.

     警告: Python will always be available for free on the Microsoft
     Store.  If you are asked to pay for it, you have not selected the
     correct package.

After installation, Python may be launched by finding it in Start.
Alternatively, it will be available from any Command Prompt or
PowerShell session by typing ‘python’.  Further, pip and IDLE may be
used by typing ‘pip’ or ‘idle’.  IDLE can also be found in Start.

All three commands are also available with version number suffixes, for
example, as ‘python3.exe’ and ‘python3.x.exe’ as well as ‘python.exe’
(where ‘3.x’ is the specific version you want to launch, such as 3.13).
Open "Manage App Execution Aliases" through Start to select which
version of Python is associated with each command.  It is recommended to
make sure that ‘pip’ and ‘idle’ are consistent with whichever version of
‘python’ is selected.

Virtual environments can be created with ‘python -m venv’ and activated
and used as normal.

If you have installed another version of Python and added it to your
‘PATH’ variable, it will be available as ‘python.exe’ rather than the
one from the Microsoft Store.  To access the new installation, use
‘python3.exe’ or ‘python3.x.exe’.

The ‘py.exe’ launcher will detect this Python installation, but will
prefer installations from the traditional installer.

To remove Python, open Settings and use Apps and Features, or else find
Python in Start and right-click to select Uninstall.  Uninstalling will
remove all packages you installed directly into this Python
installation, but will not remove any virtual environments

* Menu:

* Known issues::


File: python.info,  Node: Known issues,  Up: The Microsoft Store package

3.4.2.1 Known issues
....................

* Menu:

* Redirection of local data, registry, and temporary paths: Redirection of local data registry and temporary paths.


File: python.info,  Node: Redirection of local data registry and temporary paths,  Up: Known issues

3.4.2.2 Redirection of local data, registry, and temporary paths
................................................................

Because of restrictions on Microsoft Store apps, Python scripts may not
have full write access to shared locations such as ‘TEMP’ and the
registry.  Instead, it will write to a private copy.  If your scripts
must modify the shared locations, you will need to install the full
installer.

At runtime, Python will use a private copy of well-known Windows folders
and the registry.  For example, if the environment variable ‘%APPDATA%’
is ‘c:\Users\<user>\AppData\’, then when writing to
‘C:\Users\<user>\AppData\Local’ will write to
‘C:\Users\<user>\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0\LocalCache\Local\’.

When reading files, Windows will return the file from the private
folder, or if that does not exist, the real Windows directory.  For
example reading ‘C:\Windows\System32’ returns the contents of
‘C:\Windows\System32’ plus the contents of ‘C:\Program
Files\WindowsApps\package_name\VFS\SystemX86’.

You can find the real path of any existing file using *note
os.path.realpath(): 20a.:

     >>> import os
     >>> test_file = 'C:\\Users\\example\\AppData\\Local\\test.txt'
     >>> os.path.realpath(test_file)
     'C:\\Users\\example\\AppData\\Local\\Packages\\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0\\LocalCache\\Local\\test.txt'

When writing to the Windows Registry, the following behaviors exist:

   * Reading from ‘HKLM\\Software’ is allowed and results are merged
     with the ‘registry.dat’ file in the package.

   * Writing to ‘HKLM\\Software’ is not allowed if the corresponding
     key/value exists, i.e.  modifying existing keys.

   * Writing to ‘HKLM\\Software’ is allowed as long as a corresponding
     key/value does not exist in the package and the user has the
     correct access permissions.

For more detail on the technical basis for these limitations, please
consult Microsoft's documentation on packaged full-trust apps, currently
available at
docs.microsoft.com/en-us/windows/msix/desktop/desktop-to-uwp-behind-the-scenes(1)

   ---------- Footnotes ----------

   (1) 
https://docs.microsoft.com/en-us/windows/msix/desktop/desktop-to-uwp-behind-the-scenes


File: python.info,  Node: nuget org 套件,  Next: The embeddable package,  Prev: The Microsoft Store package,  Up: 在 Windows 上使用 Python

3.4.3 nuget.org 套件
--------------------

在 3.5.2 版被加入.

The nuget.org package is a reduced size Python environment intended for
use on continuous integration and build systems that do not have a
system-wide install of Python.  While nuget is "the package manager for
.NET", it also works perfectly fine for packages containing build-time
tools.

Visit nuget.org(1) for the most up-to-date information on using nuget.
What follows is a summary that is sufficient for Python developers.

The ‘nuget.exe’ command line tool may be downloaded directly from
‘https://aka.ms/nugetclidl’, for example, using curl or PowerShell.
With the tool, the latest version of Python for 64-bit or 32-bit
machines is installed using:

     nuget.exe install python -ExcludeVersion -OutputDirectory .
     nuget.exe install pythonx86 -ExcludeVersion -OutputDirectory .

To select a particular version, add a ‘-Version 3.x.y’.  The output
directory may be changed from ‘.’, and the package will be installed
into a subdirectory.  By default, the subdirectory is named the same as
the package, and without the ‘-ExcludeVersion’ option this name will
include the specific version installed.  Inside the subdirectory is a
‘tools’ directory that contains the Python installation:

     # Without -ExcludeVersion
     > .\python.3.5.2\tools\python.exe -V
     Python 3.5.2

     # With -ExcludeVersion
     > .\python\tools\python.exe -V
     Python 3.5.2

In general, nuget packages are not upgradeable, and newer versions
should be installed side-by-side and referenced using the full path.
Alternatively, delete the package directory manually and install it
again.  Many CI systems will do this automatically if they do not
preserve files between builds.

Alongside the ‘tools’ directory is a ‘build\native’ directory.  This
contains a MSBuild properties file ‘python.props’ that can be used in a
C++ project to reference the Python install.  Including the settings
will automatically use the headers and import libraries in your build.

The package information pages on nuget.org are
www.nuget.org/packages/python(2) for the 64-bit version,
www.nuget.org/packages/pythonx86(3) for the 32-bit version, and
www.nuget.org/packages/pythonarm64(4) for the ARM64 version

* Menu:

* Free-threaded packages::

   ---------- Footnotes ----------

   (1) https://www.nuget.org/

   (2) https://www.nuget.org/packages/python

   (3) https://www.nuget.org/packages/pythonx86

   (4) https://www.nuget.org/packages/pythonarm64


File: python.info,  Node: Free-threaded packages,  Up: nuget org 套件

3.4.3.1 Free-threaded packages
..............................

在 3.13 版被加入: (Experimental)

     備註: Everything described in this section is considered
     experimental, and should be expected to change in future releases.

Packages containing free-threaded binaries are named
python-freethreaded(1) for the 64-bit version, pythonx86-freethreaded(2)
for the 32-bit version, and pythonarm64-freethreaded(3) for the ARM64
version.  These packages contain both the ‘python3.13t.exe’ and
‘python.exe’ entry points, both of which run free threaded.

   ---------- Footnotes ----------

   (1) https://www.nuget.org/packages/python-freethreaded

   (2) https://www.nuget.org/packages/pythonx86-freethreaded

   (3) https://www.nuget.org/packages/pythonarm64-freethreaded


File: python.info,  Node: The embeddable package,  Next: Alternative bundles,  Prev: nuget org 套件,  Up: 在 Windows 上使用 Python

3.4.4 The embeddable package
----------------------------

在 3.5 版被加入.

The embedded distribution is a ZIP file containing a minimal Python
environment.  It is intended for acting as part of another application,
rather than being directly accessed by end-users.

When extracted, the embedded distribution is (almost) fully isolated
from the user's system, including environment variables, system registry
settings, and installed packages.  The standard library is included as
pre-compiled and optimized ‘.pyc’ files in a ZIP, and ‘python3.dll’,
‘python37.dll’, ‘python.exe’ and ‘pythonw.exe’ are all provided.  Tcl/tk
(including all dependents, such as Idle), pip and the Python
documentation are not included.

     備註: The embedded distribution does not include the Microsoft C
     Runtime(1) and it is the responsibility of the application
     installer to provide this.  The runtime may have already been
     installed on a user's system previously or automatically via
     Windows Update, and can be detected by finding ‘ucrtbase.dll’ in
     the system directory.

Third-party packages should be installed by the application installer
alongside the embedded distribution.  Using pip to manage dependencies
as for a regular Python installation is not supported with this
distribution, though with some care it may be possible to include and
use pip for automatic updates.  In general, third-party packages should
be treated as part of the application ("vendoring") so that the
developer can ensure compatibility with newer versions before providing
updates to users.

The two recommended use cases for this distribution are described below.

* Menu:

* Python Application::
* 嵌入 Python::

   ---------- Footnotes ----------

   (1) 
https://docs.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist#visual-studio-2015-2017-2019-and-2022


File: python.info,  Node: Python Application,  Next: 嵌入 Python,  Up: The embeddable package

3.4.4.1 Python Application
..........................

An application written in Python does not necessarily require users to
be aware of that fact.  The embedded distribution may be used in this
case to include a private version of Python in an install package.
Depending on how transparent it should be (or conversely, how
professional it should appear), there are two options.

Using a specialized executable as a launcher requires some coding, but
provides the most transparent experience for users.  With a customized
launcher, there are no obvious indications that the program is running
on Python: icons can be customized, company and version information can
be specified, and file associations behave properly.  In most cases, a
custom launcher should simply be able to call ‘Py_Main’ with a
hard-coded command line.

The simpler approach is to provide a batch file or generated shortcut
that directly calls the ‘python.exe’ or ‘pythonw.exe’ with the required
command-line arguments.  In this case, the application will appear to be
Python and not its actual name, and users may have trouble
distinguishing it from other running Python processes or file
associations.

With the latter approach, packages should be installed as directories
alongside the Python executable to ensure they are available on the
path.  With the specialized launcher, packages can be located in other
locations as there is an opportunity to specify the search path before
launching the application.


File: python.info,  Node: 嵌入 Python,  Prev: Python Application,  Up: The embeddable package

3.4.4.2 嵌入 Python
...................

Applications written in native code often require some form of scripting
language, and the embedded Python distribution can be used for this
purpose.  In general, the majority of the application is in native code,
and some part will either invoke ‘python.exe’ or directly use
‘python3.dll’.  For either case, extracting the embedded distribution to
a subdirectory of the application installation is sufficient to provide
a loadable Python interpreter.

As with the application use, packages can be installed to any location
as there is an opportunity to specify search paths before initializing
the interpreter.  Otherwise, there is no fundamental differences between
using the embedded distribution and a regular installation.


File: python.info,  Node: Alternative bundles,  Next: 設定 Python,  Prev: The embeddable package,  Up: 在 Windows 上使用 Python

3.4.5 Alternative bundles
-------------------------

Besides the standard CPython distribution, there are modified packages
including additional functionality.  The following is a list of popular
versions and their key features:

ActivePython(1)

     Installer with multi-platform compatibility, documentation, PyWin32

Anaconda(2)

     Popular scientific modules (such as numpy, scipy and pandas) and
     the ‘conda’ package manager.

Enthought Deployment Manager(3)

     "The Next Generation Python Environment and Package Manager".

     Previously Enthought provided Canopy, but it reached end of life in
     2016(4).

WinPython(5)

     Windows-specific distribution with prebuilt scientific packages and
     tools for building packages.

Note that these packages may not include the latest versions of Python
or other libraries, and are not maintained or supported by the core
Python team.

   ---------- Footnotes ----------

   (1) https://www.activestate.com/products/python/

   (2) https://www.anaconda.com/download/

   (3) https://www.enthought.com/edm/

   (4) 
https://support.enthought.com/hc/en-us/articles/360038600051-Canopy-GUI-end-of-life-transition-to-the-Enthought-Deployment-Manager-EDM-and-Visual-Studio-Code

   (5) https://winpython.github.io/


File: python.info,  Node: 設定 Python,  Next: UTF-8 模式,  Prev: Alternative bundles,  Up: 在 Windows 上使用 Python

3.4.6 設定 Python
-----------------

To run Python conveniently from a command prompt, you might consider
changing some default environment variables in Windows.  While the
installer provides an option to configure the PATH and PATHEXT variables
for you, this is only reliable for a single, system-wide installation.
If you regularly use multiple versions of Python, consider using the
*note Python Launcher for Windows: 562.

* Menu:

* Excursus; Setting environment variables: Excursus Setting environment variables.
* Finding the Python executable::


File: python.info,  Node: Excursus Setting environment variables,  Next: Finding the Python executable,  Up: 設定 Python

3.4.6.1 Excursus: Setting environment variables
...............................................

Windows allows environment variables to be configured permanently at
both the User level and the System level, or temporarily in a command
prompt.

To temporarily set environment variables, open Command Prompt and use
the ‘set’ command:

     C:\>set PATH=C:\Program Files\Python 3.9;%PATH%
     C:\>set PYTHONPATH=%PYTHONPATH%;C:\My_python_lib
     C:\>python

These changes will apply to any further commands executed in that
console, and will be inherited by any applications started from the
console.

Including the variable name within percent signs will expand to the
existing value, allowing you to add your new value at either the start
or the end.  Modifying ‘PATH’ by adding the directory containing
‘python.exe’ to the start is a common way to ensure the correct version
of Python is launched.

To permanently modify the default environment variables, click Start and
search for 'edit environment variables', or open System properties,
Advanced system settings and click the Environment Variables button.  In
this dialog, you can add or modify User and System variables.  To change
System variables, you need non-restricted access to your machine (i.e.
Administrator rights).

     備註: Windows will concatenate User variables 'after' System
     variables, which may cause unexpected results when modifying
     ‘PATH’.

     The *note PYTHONPATH: fbe. variable is used by all versions of
     Python, so you should not permanently configure it unless the
     listed paths only include code that is compatible with all of your
     installed Python versions.

也參考
......

‘https://docs.microsoft.com/en-us/windows/win32/procthread/environment-variables’

     Windows 上的環境變數概要

‘https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/set_1’

     The ‘set’ command, for temporarily modifying environment variables

‘https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/setx’

     The ‘setx’ command, for permanently modifying environment variables


File: python.info,  Node: Finding the Python executable,  Prev: Excursus Setting environment variables,  Up: 設定 Python

3.4.6.2 Finding the Python executable
.....................................

在 3.5 版的變更.

Besides using the automatically created start menu entry for the Python
interpreter, you might want to start Python in the command prompt.  The
installer has an option to set that up for you.

On the first page of the installer, an option labelled "Add Python to
PATH" may be selected to have the installer add the install location
into the ‘PATH’.  The location of the ‘Scripts\’ folder is also added.
This allows you to type ‘python’ to run the interpreter, and ‘pip’ for
the package installer.  Thus, you can also execute your scripts with
command line options, see *note 命令列: fa8. documentation.

If you don't enable this option at install time, you can always re-run
the installer, select Modify, and enable it.  Alternatively, you can
manually modify the ‘PATH’ using the directions in *note Excursus;
Setting environment variables: 1aed.  You need to set your ‘PATH’
environment variable to include the directory of your Python
installation, delimited by a semicolon from other entries.  An example
variable could look like this (assuming the first two entries already
existed):

     C:\WINDOWS\system32;C:\WINDOWS;C:\Program Files\Python 3.9


File: python.info,  Node: UTF-8 模式,  Next: Python Launcher for Windows,  Prev: 設定 Python,  Up: 在 Windows 上使用 Python

3.4.7 UTF-8 模式
----------------

在 3.7 版被加入.

Windows still uses legacy encodings for the system encoding (the ANSI
Code Page).  Python uses it for the default encoding of text files (e.g.
*note locale.getencoding(): 2bc.).

This may cause issues because UTF-8 is widely used on the internet and
most Unix systems, including WSL (Windows Subsystem for Linux).

You can use the *note Python UTF-8 Mode: 5fc. to change the default text
encoding to UTF-8.  You can enable the *note Python UTF-8 Mode: 5fc. via
the ‘-X utf8’ command line option, or the ‘PYTHONUTF8=1’ environment
variable.  See *note PYTHONUTF8: a7b. for enabling UTF-8 mode, and *note
Excursus; Setting environment variables: 1aed. for how to modify
environment variables.

When the *note Python UTF-8 Mode: 5fc. is enabled, you can still use the
system encoding (the ANSI Code Page) via the "mbcs" codec.

Note that adding ‘PYTHONUTF8=1’ to the default environment variables
will affect all Python 3.7+ applications on your system.  If you have
any Python 3.7+ applications which rely on the legacy system encoding,
it is recommended to set the environment variable temporarily or use the
‘-X utf8’ command line option.

     備註: Even when UTF-8 mode is disabled, Python uses UTF-8 by
     default on Windows for:

        * Console I/O including standard I/O (see PEP 528(1) for
          details).

        * The *note filesystem encoding: 4e0. (see PEP 529(2) for
          details).

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0528/

   (2) https://peps.python.org/pep-0529/


File: python.info,  Node: Python Launcher for Windows,  Next: 找尋模組,  Prev: UTF-8 模式,  Up: 在 Windows 上使用 Python

3.4.8 Python Launcher for Windows
---------------------------------

在 3.3 版被加入.

The Python launcher for Windows is a utility which aids in locating and
executing of different Python versions.  It allows scripts (or the
command-line) to indicate a preference for a specific Python version,
and will locate and execute that version.

Unlike the ‘PATH’ variable, the launcher will correctly select the most
appropriate version of Python.  It will prefer per-user installations
over system-wide ones, and orders by language version rather than using
the most recently installed version.

The launcher was originally specified in PEP 397(1).

* Menu:

* 開始::
* Shebang Lines::
* Arguments in shebang lines::
* Customization::
* Diagnostics::
* Dry Run::
* 安裝隨選::
* Return codes::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0397/


File: python.info,  Node: 開始,  Next: Shebang Lines,  Up: Python Launcher for Windows

3.4.8.1 開始
............

* Menu:

* From the command-line::
* 虛擬環境（Virtual environment）::
* From a script::
* 從檔案關聯::


File: python.info,  Node: From the command-line,  Next: 虛擬環境（Virtual environment）,  Up: 開始

3.4.8.2 From the command-line
.............................

在 3.6 版的變更.

System-wide installations of Python 3.3 and later will put the launcher
on your ‘PATH’.  The launcher is compatible with all available versions
of Python, so it does not matter which version is installed.  To check
that the launcher is available, execute the following command in Command
Prompt:

     py

You should find that the latest version of Python you have installed is
started - it can be exited as normal, and any additional command-line
arguments specified will be sent directly to Python.

If you have multiple versions of Python installed (e.g., 3.7 and 3.13)
you will have noticed that Python 3.13 was started - to launch Python
3.7, try the command:

     py -3.7

If you want the latest version of Python 2 you have installed, try the
command:

     py -2

If you see the following error, you do not have the launcher installed:

     'py' is not recognized as an internal or external command,
     operable program or batch file.

指令：

     py --list

displays the currently installed version(s) of Python.

The ‘-x.y’ argument is the short form of the ‘-V:Company/Tag’ argument,
which allows selecting a specific Python runtime, including those that
may have come from somewhere other than python.org.  Any runtime
registered by following PEP 514(1) will be discoverable.  The ‘--list’
command lists all available runtimes using the ‘-V:’ format.

When using the ‘-V:’ argument, specifying the Company will limit
selection to runtimes from that provider, while specifying only the Tag
will select from all providers.  Note that omitting the slash implies a
tag:

     # Select any '3.*' tagged runtime
     py -V:3

     # Select any 'PythonCore' released runtime
     py -V:PythonCore/

     # Select PythonCore's latest Python 3 runtime
     py -V:PythonCore/3

The short form of the argument (‘-3’) only ever selects from core Python
releases, and not other distributions.  However, the longer form
(‘-V:3’) will select from any.

The Company is matched on the full string, case-insenitive.  The Tag is
matched oneither the full string, or a prefix, provided the next
character is a dot or a hyphen.  This allows ‘-V:3.1’ to match ‘3.1-32’,
but not ‘3.10’.  Tags are sorted using numerical ordering (‘3.10’ is
newer than ‘3.1’), but are compared using text (‘-V:3.01’ does not match
‘3.1’).

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0514/


File: python.info,  Node: 虛擬環境（Virtual environment）,  Next: From a script,  Prev: From the command-line,  Up: 開始

3.4.8.3 虛擬環境（Virtual environment）
.......................................

在 3.5 版被加入.

If the launcher is run with no explicit Python version specification,
and a virtual environment (created with the standard library *note venv:
f9. module or the external ‘virtualenv’ tool) active, the launcher will
run the virtual environment's interpreter rather than the global one.
To run the global interpreter, either deactivate the virtual
environment, or explicitly specify the global Python version.


File: python.info,  Node: From a script,  Next: 從檔案關聯,  Prev: 虛擬環境（Virtual environment）,  Up: 開始

3.4.8.4 From a script
.....................

Let's create a test Python script - create a file called ‘hello.py’ with
the following contents

     #! python
     import sys
     sys.stdout.write("hello from Python %s\n" % (sys.version,))

From the directory in which hello.py lives, execute the command:

     py hello.py

You should notice the version number of your latest Python 2.x
installation is printed.  Now try changing the first line to be:

     #! python3

Re-executing the command should now print the latest Python 3.x
information.  As with the above command-line examples, you can specify a
more explicit version qualifier.  Assuming you have Python 3.7
installed, try changing the first line to ‘#! python3.7’ and you should
find the 3.7 version information printed.

Note that unlike interactive use, a bare "python" will use the latest
version of Python 2.x that you have installed.  This is for backward
compatibility and for compatibility with Unix, where the command
‘python’ typically refers to Python 2.


File: python.info,  Node: 從檔案關聯,  Prev: From a script,  Up: 開始

3.4.8.5 從檔案關聯
..................

The launcher should have been associated with Python files (i.e.  ‘.py’,
‘.pyw’, ‘.pyc’ files) when it was installed.  This means that when you
double-click on one of these files from Windows explorer the launcher
will be used, and therefore you can use the same facilities described
above to have the script specify the version which should be used.

The key benefit of this is that a single launcher can support multiple
Python versions at the same time depending on the contents of the first
line.


File: python.info,  Node: Shebang Lines,  Next: Arguments in shebang lines,  Prev: 開始,  Up: Python Launcher for Windows

3.4.8.6 Shebang Lines
.....................

If the first line of a script file starts with ‘#!’, it is known as a
"shebang" line.  Linux and other Unix like operating systems have native
support for such lines and they are commonly used on such systems to
indicate how a script should be executed.  This launcher allows the same
facilities to be used with Python scripts on Windows and the examples
above demonstrate their use.

To allow shebang lines in Python scripts to be portable between Unix and
Windows, this launcher supports a number of 'virtual' commands to
specify which interpreter to use.  The supported virtual commands are:

   * ‘/usr/bin/env’

   * ‘/usr/bin/python’

   * ‘/usr/local/bin/python’

   * ‘python’

For example, if the first line of your script starts with

     #! /usr/bin/python

The default Python or an active virtual environment will be located and
used.  As many Python scripts written to work on Unix will already have
this line, you should find these scripts can be used by the launcher
without modification.  If you are writing a new script on Windows which
you hope will be useful on Unix, you should use one of the shebang lines
starting with ‘/usr’.

Any of the above virtual commands can be suffixed with an explicit
version (either just the major version, or the major and minor version).
Furthermore the 32-bit version can be requested by adding "-32" after
the minor version.  I.e.  ‘/usr/bin/python3.7-32’ will request usage of
the 32-bit Python 3.7.  If a virtual environment is active, the version
will be ignored and the environment will be used.

在 3.7 版被加入: Beginning with python launcher 3.7 it is possible to
request 64-bit version by the "-64" suffix.  Furthermore it is possible
to specify a major and architecture without minor (i.e.
‘/usr/bin/python3-64’).

在 3.11 版的變更: The "-64" suffix is deprecated, and now implies "any
architecture that is not provably i386/32-bit".  To request a specific
environment, use the new ‘-V:TAG’ argument with the complete tag.

在 3.13 版的變更: Virtual commands referencing ‘python’ now prefer an
active virtual environment rather than searching ‘PATH’.  This handles
cases where the shebang specifies ‘/usr/bin/env python3’ but
‘python3.exe’ is not present in the active environment.

The ‘/usr/bin/env’ form of shebang line has one further special
property.  Before looking for installed Python interpreters, this form
will search the executable ‘PATH’ for a Python executable matching the
name provided as the first argument.  This corresponds to the behaviour
of the Unix ‘env’ program, which performs a ‘PATH’ search.  If an
executable matching the first argument after the ‘env’ command cannot be
found, but the argument starts with ‘python’, it will be handled as
described for the other virtual commands.  The environment variable
‘PYLAUNCHER_NO_SEARCH_PATH’ may be set (to any value) to skip this
search of ‘PATH’.

Shebang lines that do not match any of these patterns are looked up in
the ‘[commands]’ section of the launcher's *note .INI file: 1d28.  This
may be used to handle certain commands in a way that makes sense for
your system.  The name of the command must be a single argument (no
spaces in the shebang executable), and the value substituted is the full
path to the executable (additional arguments specified in the .INI will
be quoted as part of the filename).

     [commands]
     /bin/xpython=C:\Program Files\XPython\python.exe

Any commands not found in the .INI file are treated as 'Windows'
executable paths that are absolute or relative to the directory
containing the script file.  This is a convenience for Windows-only
scripts, such as those generated by an installer, since the behavior is
not compatible with Unix-style shells.  These paths may be quoted, and
may include multiple arguments, after which the path to the script and
any additional arguments will be appended.


File: python.info,  Node: Arguments in shebang lines,  Next: Customization,  Prev: Shebang Lines,  Up: Python Launcher for Windows

3.4.8.7 Arguments in shebang lines
..................................

The shebang lines can also specify additional options to be passed to
the Python interpreter.  For example, if you have a shebang line:

     #! /usr/bin/python -v

Then Python will be started with the ‘-v’ option


File: python.info,  Node: Customization,  Next: Diagnostics,  Prev: Arguments in shebang lines,  Up: Python Launcher for Windows

3.4.8.8 Customization
.....................

* Menu:

* Customization via INI files::
* Customizing default Python versions::


File: python.info,  Node: Customization via INI files,  Next: Customizing default Python versions,  Up: Customization

3.4.8.9 Customization via INI files
...................................

Two .ini files will be searched by the launcher - ‘py.ini’ in the
current user's application data directory (‘%LOCALAPPDATA%’ or
‘$env:LocalAppData’) and ‘py.ini’ in the same directory as the launcher.
The same .ini files are used for both the 'console' version of the
launcher (i.e.  py.exe) and for the 'windows' version (i.e.  pyw.exe).

Customization specified in the "application directory" will have
precedence over the one next to the executable, so a user, who may not
have write access to the .ini file next to the launcher, can override
commands in that global .ini file.


File: python.info,  Node: Customizing default Python versions,  Prev: Customization via INI files,  Up: Customization

3.4.8.10 Customizing default Python versions
............................................

In some cases, a version qualifier can be included in a command to
dictate which version of Python will be used by the command.  A version
qualifier starts with a major version number and can optionally be
followed by a period ('.')  and a minor version specifier.  Furthermore
it is possible to specify if a 32 or 64 bit implementation shall be
requested by adding "-32" or "-64".

For example, a shebang line of ‘#!python’ has no version qualifier,
while ‘#!python3’ has a version qualifier which specifies only a major
version.

If no version qualifiers are found in a command, the environment
variable ‘PY_PYTHON’ can be set to specify the default version
qualifier.  If it is not set, the default is "3".  The variable can
specify any value that may be passed on the command line, such as "3",
"3.7", "3.7-32" or "3.7-64".  (Note that the "-64" option is only
available with the launcher included with Python 3.7 or newer.)

If no minor version qualifiers are found, the environment variable
‘PY_PYTHON{major}’ (where ‘{major}’ is the current major version
qualifier as determined above) can be set to specify the full version.
If no such option is found, the launcher will enumerate the installed
Python versions and use the latest minor release found for the major
version, which is likely, although not guaranteed, to be the most
recently installed version in that family.

On 64-bit Windows with both 32-bit and 64-bit implementations of the
same (major.minor) Python version installed, the 64-bit version will
always be preferred.  This will be true for both 32-bit and 64-bit
implementations of the launcher - a 32-bit launcher will prefer to
execute a 64-bit Python installation of the specified version if
available.  This is so the behavior of the launcher can be predicted
knowing only what versions are installed on the PC and without regard to
the order in which they were installed (i.e., without knowing whether a
32 or 64-bit version of Python and corresponding launcher was installed
last).  As noted above, an optional "-32" or "-64" suffix can be used on
a version specifier to change this behaviour.

範例：

   * If no relevant options are set, the commands ‘python’ and ‘python2’
     will use the latest Python 2.x version installed and the command
     ‘python3’ will use the latest Python 3.x installed.

   * The command ‘python3.7’ will not consult any options at all as the
     versions are fully specified.

   * If ‘PY_PYTHON=3’, the commands ‘python’ and ‘python3’ will both use
     the latest installed Python 3 version.

   * If ‘PY_PYTHON=3.7-32’, the command ‘python’ will use the 32-bit
     implementation of 3.7 whereas the command ‘python3’ will use the
     latest installed Python (PY_PYTHON was not considered at all as a
     major version was specified.)

   * If ‘PY_PYTHON=3’ and ‘PY_PYTHON3=3.7’, the commands ‘python’ and
     ‘python3’ will both use specifically 3.7

In addition to environment variables, the same settings can be
configured in the .INI file used by the launcher.  The section in the
INI file is called ‘[defaults]’ and the key name will be the same as the
environment variables without the leading ‘PY_’ prefix (and note that
the key names in the INI file are case insensitive.)  The contents of an
environment variable will override things specified in the INI file.

舉例來說：

   * Setting ‘PY_PYTHON=3.7’ is equivalent to the INI file containing:

     [defaults]
     python=3.7

   * Setting ‘PY_PYTHON=3’ and ‘PY_PYTHON3=3.7’ is equivalent to the INI
     file containing:

     [defaults]
     python=3
     python3=3.7


File: python.info,  Node: Diagnostics,  Next: Dry Run,  Prev: Customization,  Up: Python Launcher for Windows

3.4.8.11 Diagnostics
....................

If an environment variable ‘PYLAUNCHER_DEBUG’ is set (to any value), the
launcher will print diagnostic information to stderr (i.e.  to the
console).  While this information manages to be simultaneously verbose
'and' terse, it should allow you to see what versions of Python were
located, why a particular version was chosen and the exact command-line
used to execute the target Python.  It is primarily intended for testing
and debugging.


File: python.info,  Node: Dry Run,  Next: 安裝隨選,  Prev: Diagnostics,  Up: Python Launcher for Windows

3.4.8.12 Dry Run
................

If an environment variable ‘PYLAUNCHER_DRYRUN’ is set (to any value),
the launcher will output the command it would have run, but will not
actually launch Python.  This may be useful for tools that want to use
the launcher to detect and then launch Python directly.  Note that the
command written to standard output is always encoded using UTF-8, and
may not render correctly in the console.


File: python.info,  Node: 安裝隨選,  Next: Return codes,  Prev: Dry Run,  Up: Python Launcher for Windows

3.4.8.13 安裝隨選
.................

If an environment variable ‘PYLAUNCHER_ALLOW_INSTALL’ is set (to any
value), and the requested Python version is not installed but is
available on the Microsoft Store, the launcher will attempt to install
it.  This may require user interaction to complete, and you may need to
run the command again.

An additional ‘PYLAUNCHER_ALWAYS_INSTALL’ variable causes the launcher
to always try to install Python, even if it is detected.  This is mainly
intended for testing (and should be used with ‘PYLAUNCHER_DRYRUN’).


File: python.info,  Node: Return codes,  Prev: 安裝隨選,  Up: Python Launcher for Windows

3.4.8.14 Return codes
.....................

The following exit codes may be returned by the Python launcher.
Unfortunately, there is no way to distinguish these from the exit code
of Python itself.

The names of codes are as used in the sources, and are only for
reference.  There is no way to access or resolve them apart from reading
this page.  Entries are listed in alphabetical order of names.

名稱                    Value       描述
                                    
----------------------------------------------------------------------------------------
                                    
RC_BAD_VENV_CFG         107         A ‘pyvenv.cfg’ was found but is corrupt.
                                    
                                    
RC_CREATE_PROCESS       101         Failed to launch Python.
                                    
                                    
RC_INSTALLING           111         An install was started, but the command will need
                                    to be re-run after it completes.
                                    
                                    
RC_INTERNAL_ERROR       109         Unexpected error.  Please report a bug.
                                    
                                    
RC_NO_COMMANDLINE       108         Unable to obtain command line from the operating
                                    system.
                                    
                                    
RC_NO_PYTHON            103         Unable to locate the requested version.
                                    
                                    
RC_NO_VENV_CFG          106         A ‘pyvenv.cfg’ was required but not found.
                                    


File: python.info,  Node: 找尋模組,  Next: 額外的模組,  Prev: Python Launcher for Windows,  Up: 在 Windows 上使用 Python

3.4.9 找尋模組
--------------

These notes supplement the description at *note The initialization of
the sys.path module search path: 1b64. with detailed Windows notes.

When no ‘._pth’ file is found, this is how *note sys.path: 37f. is
populated on Windows:

   * An empty entry is added at the start, which corresponds to the
     current directory.

   * If the environment variable *note PYTHONPATH: fbe. exists, as
     described in *note 環境變數: 595, its entries are added next.  Note
     that on Windows, paths in this variable must be separated by
     semicolons, to distinguish them from the colon used in drive
     identifiers (‘C:\’ etc.).

   * Additional "application paths" can be added in the registry as
     subkeys of ‘\SOFTWARE\Python\PythonCore{version}\PythonPath’ under
     both the ‘HKEY_CURRENT_USER’ and ‘HKEY_LOCAL_MACHINE’ hives.
     Subkeys which have semicolon-delimited path strings as their
     default value will cause each path to be added to *note sys.path:
     37f.  (Note that all known installers only use HKLM, so HKCU is
     typically empty.)

   * If the environment variable *note PYTHONHOME: 387. is set, it is
     assumed as "Python Home".  Otherwise, the path of the main Python
     executable is used to locate a "landmark file" (either ‘Lib\os.py’
     or ‘pythonXY.zip’) to deduce the "Python Home".  If a Python home
     is found, the relevant sub-directories added to *note sys.path:
     37f. (‘Lib’, ‘plat-win’, etc) are based on that folder.  Otherwise,
     the core Python path is constructed from the PythonPath stored in
     the registry.

   * If the Python Home cannot be located, no *note PYTHONPATH: fbe. is
     specified in the environment, and no registry entries can be found,
     a default path with relative entries is used (e.g.
     ‘.\Lib;.\plat-win’, etc).

If a ‘pyvenv.cfg’ file is found alongside the main executable or in the
directory one level above the executable, the following variations
apply:

   * If ‘home’ is an absolute path and *note PYTHONHOME: 387. is not
     set, this path is used instead of the path to the main executable
     when deducing the home location.

最終這所有的結果為：

   * When running ‘python.exe’, or any other .exe in the main Python
     directory (either an installed version, or directly from the
     PCbuild directory), the core path is deduced, and the core paths in
     the registry are ignored.  Other "application paths" in the
     registry are always read.

   * When Python is hosted in another .exe (different directory,
     embedded via COM, etc), the "Python Home" will not be deduced, so
     the core path from the registry is used.  Other "application paths"
     in the registry are always read.

   * If Python can't find its home and there are no registry value
     (frozen .exe, some very strange installation setup) you get a path
     with some default, but relative, paths.

For those who want to bundle Python into their application or
distribution, the following advice will prevent conflicts with other
installations:

   * Include a ‘._pth’ file alongside your executable containing the
     directories to include.  This will ignore paths listed in the
     registry and environment variables, and also ignore *note site: b5.
     unless ‘import site’ is listed.

   * If you are loading ‘python3.dll’ or ‘python37.dll’ in your own
     executable, explicitly set *note PyConfig.module_search_paths: 36d.
     before *note Py_InitializeFromConfig(): 390.

   * Clear and/or overwrite *note PYTHONPATH: fbe. and set *note
     PYTHONHOME: 387. before launching ‘python.exe’ from your
     application.

   * If you cannot use the previous suggestions (for example, you are a
     distribution that allows people to run ‘python.exe’ directly),
     ensure that the landmark file (‘Lib\os.py’) exists in your install
     directory.  (Note that it will not be detected inside a ZIP file,
     but a correctly named ZIP file will be detected instead.)

These will ensure that the files in a system-wide installation will not
take precedence over the copy of the standard library bundled with your
application.  Otherwise, your users may experience problems using your
application.  Note that the first suggestion is the best, as the others
may still be susceptible to non-standard paths in the registry and user
site-packages.

在 3.6 版的變更: Add ‘._pth’ file support and removes ‘applocal’ option
from ‘pyvenv.cfg’.

在 3.6 版的變更: Add ‘python`XX'.zip’ as a potential landmark when
directly adjacent to the executable.

在 3.6 版之後被棄用: Modules specified in the registry under ‘Modules’
(not ‘PythonPath’) may be imported by *note
importlib.machinery.WindowsRegistryFinder: cd1.  This finder is enabled
on Windows in 3.6.0 and earlier, but may need to be explicitly added to
*note sys.meta_path: cd2. in the future.


File: python.info,  Node: 額外的模組,  Next: 編譯 Python 在 Windows,  Prev: 找尋模組,  Up: 在 Windows 上使用 Python

3.4.10 額外的模組
-----------------

Even though Python aims to be portable among all platforms, there are
features that are unique to Windows.  A couple of modules, both in the
standard library and external, and snippets exist to use these features.

The Windows-specific standard modules are documented in *note MS Windows
特有服務: 1d33.

* Menu:

* PyWin32::
* cx_Freeze::


File: python.info,  Node: PyWin32,  Next: cx_Freeze,  Up: 額外的模組

3.4.10.1 PyWin32
................

The PyWin32(1) module by Mark Hammond is a collection of modules for
advanced Windows-specific support.  This includes utilities for:

   * Component Object Model(2) (COM)

   * Win32 API 呼叫

   * 登錄檔（Registry）

   * 事件日誌（Event log）

   * Microsoft Foundation Classes(3) (MFC) user interfaces

PythonWin(4) is a sample MFC application shipped with PyWin32.  It is an
embeddable IDE with a built-in debugger.

也參考
......

Win32 How Do I...?(5)

     由 Tim Golden 所著

Python and COM(6)

     由 David 與 Paul Boddie 所著

   ---------- Footnotes ----------

   (1) https://pypi.org/project/PyWin32/

   (2) 
https://docs.microsoft.com/en-us/windows/win32/com/component-object-model-com-portal

   (3) https://docs.microsoft.com/en-us/cpp/mfc/mfc-desktop-applications

   (4) 
https://web.archive.org/web/20060524042422/https://www.python.org/windows/pythonwin/

   (5) http://timgolden.me.uk/python/win32_how_do_i.html

   (6) https://www.boddie.org.uk/python/COM.html


File: python.info,  Node: cx_Freeze,  Prev: PyWin32,  Up: 額外的模組

3.4.10.2 cx_Freeze
..................

cx_Freeze(1) wraps Python scripts into executable Windows programs
(‘`*'.exe’ files).  When you have done this, you can distribute your
application without requiring your users to install Python.

   ---------- Footnotes ----------

   (1) https://cx-freeze.readthedocs.io/en/latest/


File: python.info,  Node: 編譯 Python 在 Windows,  Next: 其他平台,  Prev: 額外的模組,  Up: 在 Windows 上使用 Python

3.4.11 編譯 Python 在 Windows
-----------------------------

If you want to compile CPython yourself, first thing you should do is
get the source(1).  You can download either the latest release's source
or just grab a fresh checkout(2).

The source tree contains a build solution and project files for
Microsoft Visual Studio, which is the compiler used to build the
official Python releases.  These files are in the ‘PCbuild’ directory.

Check ‘PCbuild/readme.txt’ for general information on the build process.

For extension modules, consult *note 建置 Windows 上的 C 和 C++ 擴充:
1d37.

   ---------- Footnotes ----------

   (1) https://www.python.org/downloads/source/

   (2) https://devguide.python.org/setup/#get-the-source-code


File: python.info,  Node: 其他平台,  Prev: 編譯 Python 在 Windows,  Up: 在 Windows 上使用 Python

3.4.12 其他平台
---------------

With ongoing development of Python, some platforms that used to be
supported earlier are no longer supported (due to the lack of users or
developers).  Check PEP 11(1) for details on all unsupported platforms.

   * Windows CE(2) is no longer supported(3) since Python 3 (if it ever
     was).

   * The Cygwin(4) installer offers to install the Python interpreter(5)
     as well

See Python for Windows(6) for detailed information about platforms with
pre-compiled installers.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0011/

   (2) https://pythonce.sourceforge.net/

   (3) https://github.com/python/cpython/issues/71542

   (4) https://cygwin.com/

   (5) https://cygwin.com/packages/summary/python3.html

   (6) https://www.python.org/downloads/windows/


File: python.info,  Node: 在 Mac 系統使用 Python,  Next: Using Python on iOS,  Prev: 在 Windows 上使用 Python,  Up: Python 的設置與使用

3.5 在 Mac 系統使用 Python
==========================


作者: Bob Savage <<bobsavage@mac.com>>

Python 在 Mac 的 macOS 上執行和在其他 Unix 平台上執行的原理非常相似，但
值得一提的是在 macOS 上有其他額外的功能，例如整合開發環境 (IDE) 與套件管
理。
* Menu:

* 取得和安裝 Python::
* 整合化開發工具 (IDE): 整合化開發工具 IDE.
* 安裝額外的 Python 套件::
* 開發 GUI 程式::
* 發行 Python 應用程式::
* 其他資源::


File: python.info,  Node: 取得和安裝 Python,  Next: 整合化開發工具 IDE,  Up: 在 Mac 系統使用 Python

3.5.1 取得和安裝 Python
-----------------------

macOS 自 10.8 版本開始至 12.3 版本(1)之間預設安裝 Python 2.7。你也可以到
Python 網站(2)安裝最新的 Python 3 版本。你可以找到建立在"通用二進位
(universal2 binary)" 上的 Python 建置版本，它能夠原生地運行在 Mac 新的
Apple Silicon CPU 與過去的 Intel CPU 上。

在安裝後你必須要做幾件事：

   * 會有一個 ‘Python 3.13’ 資料夾在你的 ‘Applications’ 資料夾中。在這裡
     你可以找到 IDLE，它是作為官方 Python 發行版標準組成的開發環境；以及
     ‘Python Launcher’，它負責處理在 Finder 中雙擊 Python 腳本的操作。

   * ‘/Library/Frameworks/Python.framework’ 框架，包括 Python 可執行檔案
     (executable) 和函式庫 (library)。安裝程式將此位置新增到 shell 路徑
     。要解除安裝 Python ，你可以移除這三個專案。Python 可執行檔案的符號
     連結 (symlink) 則放在 ‘/usr/local/bin/’ 中。

     備註: 在 macOS 10.8-12.3，Apple 提供的 Python 建置版本分別安裝在
     ‘/System/Library/Frameworks/Python.framework’ 和 ‘/usr/bin/python’
     中。你不應該去修改或刪除這些內容，因為它們由 Apple 控制並且被 Apple
     或第三方軟體使用。請記住，如果你選擇從 python.org 安裝較新的 Python
     版本，那麼你的計算機上將安裝兩個不同但都可運作的 Python，因此你的路
     徑和用法與你想要執行的操作一致非常重要。

IDLE 包含一個幫助 (Help) 選單，讓你可以參閱 Python 文件。如果你是 Python
的新手，你應該開始閱讀該文件中的教學介紹。

如果你熟悉其他 Unix 平臺上的 Python，那麼你應該閱讀有關從 Unix shell 執
行 Python 腳本的部分。

* Menu:

* 如何執行 Python 腳本::
* 透過 GUI 執行腳本::
* 設定::

   ---------- Footnotes ----------

   (1) 
https://developer.apple.com/documentation/macos-release-notes/macos-12_3-release-notes#Python

   (2) https://www.python.org/downloads/macos/


File: python.info,  Node: 如何執行 Python 腳本,  Next: 透過 GUI 執行腳本,  Up: 取得和安裝 Python

3.5.1.1 如何執行 Python 腳本
............................

在 macOS 上開始使用 Python 的最佳方法是透過 IDLE 整合開發環境；參見
*note 整合化開發工具 (IDE): 1d3f. 部分，並在 IDE 執行時使用幫助選單。

如果要從終端機視窗命令列或 Finder 執行 Python 腳本，首先需要一個編輯器來
建立腳本。macOS 附帶了許多標準的 Unix 命令列編輯器，如 ‘vim’ 和 ‘nano’。
如果你想要一個更 Mac 化的編輯器，那麼來自 Bare Bones Software 的
‘BBEdit’（參見 ‘http://www.barebones.com/products/bbedit/index.html’） 是
不錯的選擇，‘TextMate’ （參見 ‘https://macromates.com/’）也是個選擇。其
他編輯器包括 ‘MacVim’ (‘https://macvim.org’) 和 ‘Aquamacs’
(‘https://aquamacs.org/’)。

要從終端機視窗執行腳本，你必須確保 ‘/usr/local/bin’ 位於 shell 搜尋路徑
中。

從 Finder 執行你的腳本時，你有兩個選項：

   * 把它拖曳到 ‘Python Launcher’

   * 透過 finder Info 視窗選擇 ‘Python Launcher’ 作為開啟腳本（或任何
     ‘.py’ 腳本）的預設應用程式，然後雙擊腳本。‘Python Launcher’ 有各種
     用來控制腳本啟動方式的選項。拖曳選項可以讓你一次更改多個選項，或使
     用其偏好設定選單以全域性地更改內容。


File: python.info,  Node: 透過 GUI 執行腳本,  Next: 設定,  Prev: 如何執行 Python 腳本,  Up: 取得和安裝 Python

3.5.1.2 透過 GUI 執行腳本
.........................

對於舊版本的 Python，你需要注意一個 macOS 的怪異之處：與 Aqua 視窗管理器
溝通的程式（換而言之，任何具有 GUI（圖形化使用者介面）的程式）需要以特殊
方式執行。使用 ‘pythonw’ 而不是 ‘python’ 來啟動這樣的腳本。

Python 3.9 上，你可以使用 ‘python’ 或者 ‘pythonw’。


File: python.info,  Node: 設定,  Prev: 透過 GUI 執行腳本,  Up: 取得和安裝 Python

3.5.1.3 設定
............

macOS 上的 Python 遵循所有標準的 Unix 環境變數，例如 *note PYTHONPATH:
fbe.，但是為 Finder 啟動的程式設定這些變數並非是標準做法，因為 Finder 在
啟動時不會讀取你的 ‘.profile’ 或 ‘.cshrc’。你需要建立一個檔案
‘~/.MacOSX/environment.plist’。相關資訊請參閱 Apple 的技術問答集
QA1067(1)。

更多關於安裝 Python 套件的資訊，參閱 *note 安裝額外的 Python 套件: 1d43.
部分。

   ---------- Footnotes ----------

   (1) https://developer.apple.com/library/archive/qa/qa1067/_index.html


File: python.info,  Node: 整合化開發工具 IDE,  Next: 安裝額外的 Python 套件,  Prev: 取得和安裝 Python,  Up: 在 Mac 系統使用 Python

3.5.2 整合化開發工具 (IDE)
--------------------------

Python 附帶標準的 IDLE 開發環境。有關使用 IDLE 的詳細介紹，請見
‘https://www.hashcollision.org/hkn/python/idle_intro/index.html’。


File: python.info,  Node: 安裝額外的 Python 套件,  Next: 開發 GUI 程式,  Prev: 整合化開發工具 IDE,  Up: 在 Mac 系統使用 Python

3.5.3 安裝額外的 Python 套件
----------------------------

這個章節已經被移動到 Python Packaging User Guide(1)。

   ---------- Footnotes ----------

   (1) 
https://packaging.python.org/en/latest/tutorials/installing-packages/


File: python.info,  Node: 開發 GUI 程式,  Next: 發行 Python 應用程式,  Prev: 安裝額外的 Python 套件,  Up: 在 Mac 系統使用 Python

3.5.4 開發 GUI 程式
-------------------

於 Mac 上使用 Python 來建立 GUI 應用程式有許多選項。

'PyObjC' 是一個 Apple Objective-C/Cocoa 框架的 Python 繫結 (binding)，這
是大多數現代 Mac 開發的基礎。有關 PyObjC 的資訊，請見 pyobjc(1)。

標準的 Python GUI 工具套件是 *note tkinter: d9.，基於跨平臺的 Tk 工具套
件 (‘https://www.tcl.tk’)。Apple 的 macOS 包含了 Aqua 原生版本的 Tk，最
新版本可以從 ‘https://www.activestate.com’ 下載和安裝；它也可以從原始碼
開始建置。

有許多替代 macOS GUI 工具套件可用：

   * PySide(2)：Qt GUI 工具包(3)的官方 Python 繫結。

   * PyQt(4)：Qt 的替代 Python 繫結。

   * Kivy(5)：一個支援桌面和行動平臺的跨平臺 GUI 工具包。

   * Toga(6)：BeeWare 專案(7)的一部分；支援桌面、行動、網頁和控制台應用
     程式。

   * wxPython(8)：一個支援桌面作業系統的跨平臺工具包。

   ---------- Footnotes ----------

   (1) https://pypi.org/project/pyobjc/

   (2) https://www.qt.io/qt-for-python

   (3) https://qt.io

   (4) https://riverbankcomputing.com/software/pyqt/intro

   (5) https://kivy.org

   (6) https://toga.readthedocs.io

   (7) https://beeware.org

   (8) https://www.wxpython.org


File: python.info,  Node: 發行 Python 應用程式,  Next: 其他資源,  Prev: 開發 GUI 程式,  Up: 在 Mac 系統使用 Python

3.5.5 發行 Python 應用程式
--------------------------

A range of tools exist for converting your Python code into a standalone
distributable application:

   * py2app(1)：支援從 Python 專案打包成 macOS ‘.app’。

   * Briefcase(2): Part of the BeeWare Project(3); a cross-platform
     packaging tool that supports creation of ‘.app’ bundles on macOS,
     as well as managing signing and notarization.

   * PyInstaller(4)：一個跨平臺打包工具，可以將單一檔案或資料夾打包成可
     分發的檔案。

* Menu:

* App Store Compliance::

   ---------- Footnotes ----------

   (1) https://pypi.org/project/py2app/

   (2) https://briefcase.readthedocs.io

   (3) https://beeware.org

   (4) https://pyinstaller.org/


File: python.info,  Node: App Store Compliance,  Up: 發行 Python 應用程式

3.5.5.1 App Store Compliance
............................

Apps submitted for distribution through the macOS App Store must pass
Apple's app review process.  This process includes a set of automated
validation rules that inspect the submitted application bundle for
problematic code.

The Python standard library contains some code that is known to violate
these automated rules.  While these violations appear to be false
positives, Apple's review rules cannot be challenged.  Therefore, it is
necessary to modify the Python standard library for an app to pass App
Store review.

The Python source tree contains a patch file(1) that will remove all
code that is known to cause issues with the App Store review process.
This patch is applied automatically when CPython is configured with the
*note -with-app-store-compliance: 14e6. option.

This patch is not normally required to use CPython on a Mac; nor is it
required if you are distributing an app 'outside' the macOS App Store.
It is 'only' required if you are using the macOS App Store as a
distribution channel.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Mac/Resources/app-store-compliance.patch


File: python.info,  Node: 其他資源,  Prev: 發行 Python 應用程式,  Up: 在 Mac 系統使用 Python

3.5.6 其他資源
--------------

Pythonmac-SIG 郵件清單對於 Mac 上的 Python 使用者和開發者是一個極佳的支
援資源：

‘https://www.python.org/community/sigs/current/pythonmac-sig/’

另一個好用資源是 MacPython wiki：

‘https://wiki.python.org/moin/MacPython’


File: python.info,  Node: Using Python on iOS,  Next: 編輯器與 IDE,  Prev: 在 Mac 系統使用 Python,  Up: Python 的設置與使用

3.6 Using Python on iOS
=======================


Authors: Russell Keith-Magee (2024-03)

Python on iOS is unlike Python on desktop platforms.  On a desktop
platform, Python is generally installed as a system resource that can be
used by any user of that computer.  Users then interact with Python by
running a ‘python’ executable and entering commands at an interactive
prompt, or by running a Python script.

On iOS, there is no concept of installing as a system resource.  The
only unit of software distribution is an "app".  There is also no
console where you could run a ‘python’ executable, or interact with a
Python REPL.

As a result, the only way you can use Python on iOS is in embedded mode
- that is, by writing a native iOS application, and embedding a Python
interpreter using ‘libPython’, and invoking Python code using the *note
Python embedding API: 1d4f.  The full Python interpreter, the standard
library, and all your Python code is then packaged as a standalone
bundle that can be distributed via the iOS App Store.

If you're looking to experiment for the first time with writing an iOS
app in Python, projects such as BeeWare(1) and Kivy(2) will provide a
much more approachable user experience.  These projects manage the
complexities associated with getting an iOS project running, so you only
need to deal with the Python code itself.

* Menu:

* Python at runtime on iOS::
* Installing Python on iOS::
* App Store Compliance: App Store Compliance<2>.

   ---------- Footnotes ----------

   (1) https://beeware.org

   (2) https://kivy.org


File: python.info,  Node: Python at runtime on iOS,  Next: Installing Python on iOS,  Up: Using Python on iOS

3.6.1 Python at runtime on iOS
------------------------------

* Menu:

* iOS version compatibility::
* Platform identification::
* Standard library availability::
* Binary extension modules::
* Compiler stub binaries::


File: python.info,  Node: iOS version compatibility,  Next: Platform identification,  Up: Python at runtime on iOS

3.6.1.1 iOS version compatibility
.................................

The minimum supported iOS version is specified at compile time, using
the *note -host: 1cd3. option to ‘configure’.  By default, when compiled
for iOS, Python will be compiled with a minimum supported iOS version of
13.0.  To use a different minimum iOS version, provide the version
number as part of the ‘--host’ argument - for example,
‘--host=arm64-apple-ios15.4-simulator’ would compile an ARM64 simulator
build with a deployment target of 15.4.


File: python.info,  Node: Platform identification,  Next: Standard library availability,  Prev: iOS version compatibility,  Up: Python at runtime on iOS

3.6.1.2 Platform identification
...............................

When executing on iOS, ‘sys.platform’ will report as ‘ios’.  This value
will be returned on an iPhone or iPad, regardless of whether the app is
running on the simulator or a physical device.

Information about the specific runtime environment, including the iOS
version, device model, and whether the device is a simulator, can be
obtained using *note platform.ios_ver(): 1d53.  *note platform.system():
1d54. will report ‘iOS’ or ‘iPadOS’, depending on the device.

*note os.uname(): 10ae. reports kernel-level details; it will report a
name of ‘Darwin’.


File: python.info,  Node: Standard library availability,  Next: Binary extension modules,  Prev: Platform identification,  Up: Python at runtime on iOS

3.6.1.3 Standard library availability
.....................................

The Python standard library has some notable omissions and restrictions
on iOS. See the *note API availability guide for iOS: 1d56. for details.


File: python.info,  Node: Binary extension modules,  Next: Compiler stub binaries,  Prev: Standard library availability,  Up: Python at runtime on iOS

3.6.1.4 Binary extension modules
................................

One notable difference about iOS as a platform is that App Store
distribution imposes hard requirements on the packaging of an
application.  One of these requirements governs how binary extension
modules are distributed.

The iOS App Store requires that 'all' binary modules in an iOS app must
be dynamic libraries, contained in a framework with appropriate
metadata, stored in the ‘Frameworks’ folder of the packaged app.  There
can be only a single binary per framework, and there can be no
executable binary material outside the ‘Frameworks’ folder.

This conflicts with the usual Python approach for distributing binaries,
which allows a binary extension module to be loaded from any location on
‘sys.path’.  To ensure compliance with App Store policies, an iOS
project must post-process any Python packages, converting ‘.so’ binary
modules into individual standalone frameworks with appropriate metadata
and signing.  For details on how to perform this post-processing, see
the guide for *note adding Python to your project: 1d58.

To help Python discover binaries in their new location, the original
‘.so’ file on ‘sys.path’ is replaced with a ‘.fwork’ file.  This file is
a text file containing the location of the framework binary, relative to
the app bundle.  To allow the framework to resolve back to the original
location, the framework must contain a ‘.origin’ file that contains the
location of the ‘.fwork’ file, relative to the app bundle.

For example, consider the case of an import ‘from foo.bar import _whiz’,
where ‘_whiz’ is implemented with the binary module
‘sources/foo/bar/_whiz.abi3.so’, with ‘sources’ being the location
registered on ‘sys.path’, relative to the application bundle.  This
module 'must' be distributed as
‘Frameworks/foo.bar._whiz.framework/foo.bar._whiz’ (creating the
framework name from the full import path of the module), with an
‘Info.plist’ file in the ‘.framework’ directory identifying the binary
as a framework.  The ‘foo.bar._whiz’ module would be represented in the
original location with a ‘sources/foo/bar/_whiz.abi3.fwork’ marker file,
containing the path ‘Frameworks/foo.bar._whiz/foo.bar._whiz’.  The
framework would also contain
‘Frameworks/foo.bar._whiz.framework/foo.bar._whiz.origin’, containing
the path to the ‘.fwork’ file.

When running on iOS, the Python interpreter will install an *note
AppleFrameworkLoader: 1d59. that is able to read and import ‘.fwork’
files.  Once imported, the ‘__file__’ attribute of the binary module
will report as the location of the ‘.fwork’ file.  However, the *note
ModuleSpec: 1d5a. for the loaded module will report the ‘origin’ as the
location of the binary in the framework folder.


File: python.info,  Node: Compiler stub binaries,  Prev: Binary extension modules,  Up: Python at runtime on iOS

3.6.1.5 Compiler stub binaries
..............................

Xcode doesn't expose explicit compilers for iOS; instead, it uses an
‘xcrun’ script that resolves to a full compiler path (e.g., ‘xcrun --sdk
iphoneos clang’ to get the ‘clang’ for an iPhone device).  However,
using this script poses two problems:

   * The output of ‘xcrun’ includes paths that are machine specific,
     resulting in a sysconfig module that cannot be shared between
     users; and

   * It results in ‘CC’/‘CPP’/‘LD’/‘AR’ definitions that include spaces.
     There is a lot of C ecosystem tooling that assumes that you can
     split a command line at the first space to get the path to the
     compiler executable; this isn't the case when using ‘xcrun’.

To avoid these problems, Python provided stubs for these tools.  These
stubs are shell script wrappers around the underingly ‘xcrun’ tools,
distributed in a ‘bin’ folder distributed alongside the compiled iOS
framework.  These scripts are relocatable, and will always resolve to
the appropriate local system paths.  By including these scripts in the
bin folder that accompanies a framework, the contents of the ‘sysconfig’
module becomes useful for end-users to compile their own modules.  When
compiling third-party Python modules for iOS, you should ensure these
stub binaries are on your path.


File: python.info,  Node: Installing Python on iOS,  Next: App Store Compliance<2>,  Prev: Python at runtime on iOS,  Up: Using Python on iOS

3.6.2 Installing Python on iOS
------------------------------

* Menu:

* Tools for building iOS apps::
* Adding Python to an iOS project::


File: python.info,  Node: Tools for building iOS apps,  Next: Adding Python to an iOS project,  Up: Installing Python on iOS

3.6.2.1 Tools for building iOS apps
...................................

Building for iOS requires the use of Apple's Xcode tooling.  It is
strongly recommended that you use the most recent stable release of
Xcode.  This will require the use of the most (or second-most) recently
released macOS version, as Apple does not maintain Xcode for older macOS
versions.  The Xcode Command Line Tools are not sufficient for iOS
development; you need a 'full' Xcode install.

If you want to run your code on the iOS simulator, you'll also need to
install an iOS Simulator Platform.  You should be prompted to select an
iOS Simulator Platform when you first run Xcode.  Alternatively, you can
add an iOS Simulator Platform by selecting from the Platforms tab of the
Xcode Settings panel.


File: python.info,  Node: Adding Python to an iOS project,  Prev: Tools for building iOS apps,  Up: Installing Python on iOS

3.6.2.2 Adding Python to an iOS project
.......................................

Python can be added to any iOS project, using either Swift or Objective
C. The following examples will use Objective C; if you are using Swift,
you may find a library like PythonKit(1) to be helpful.

To add Python to an iOS Xcode project:

  1. Build or obtain a Python ‘XCFramework’.  See the instructions in
     iOS/README.rst(2) (in the CPython source distribution) for details
     on how to build a Python ‘XCFramework’.  At a minimum, you will
     need a build that supports ‘arm64-apple-ios’, plus one of either
     ‘arm64-apple-ios-simulator’ or ‘x86_64-apple-ios-simulator’.

  2. Drag the ‘XCframework’ into your iOS project.  In the following
     instructions, we'll assume you've dropped the ‘XCframework’ into
     the root of your project; however, you can use any other location
     that you want by adjusting paths as needed.

  3. Drag the ‘iOS/Resources/dylib-Info-template.plist’ file into your
     project, and ensure it is associated with the app target.

  4. Add your application code as a folder in your Xcode project.  In
     the following instructions, we'll assume that your user code is in
     a folder named ‘app’ in the root of your project; you can use any
     other location by adjusting paths as needed.  Ensure that this
     folder is associated with your app target.

  5. Select the app target by selecting the root node of your Xcode
     project, then the target name in the sidebar that appears.

  6. In the "General" settings, under "Frameworks, Libraries and
     Embedded Content", add ‘Python.xcframework’, with "Embed & Sign"
     selected.

  7. In the "Build Settings" tab, modify the following:

        - Build Options

             * User Script Sandboxing: No

             * Enable Testability: Yes

        - Search Paths

             * Framework Search Paths: ‘$(PROJECT_DIR)’

             * Header Search Paths:
               ‘"$(BUILT_PRODUCTS_DIR)/Python.framework/Headers"’

        - Apple Clang - Warnings - All languages

             * Quoted Include In Framework Header: No

  8. Add a build step that copies the Python standard library into your
     app.  In the "Build Phases" tab, add a new "Run Script" build step
     'before' the "Embed Frameworks" step, but 'after' the "Copy Bundle
     Resources" step.  Name the step "Install Target Specific Python
     Standard Library", disable the "Based on dependency analysis"
     checkbox, and set the script content to:

          set -e

          mkdir -p "$CODESIGNING_FOLDER_PATH/python/lib"
          if [ "$EFFECTIVE_PLATFORM_NAME" = "-iphonesimulator" ]; then
              echo "Installing Python modules for iOS Simulator"
              rsync -au --delete "$PROJECT_DIR/Python.xcframework/ios-arm64_x86_64-simulator/lib/" "$CODESIGNING_FOLDER_PATH/python/lib/"
          else
              echo "Installing Python modules for iOS Device"
              rsync -au --delete "$PROJECT_DIR/Python.xcframework/ios-arm64/lib/" "$CODESIGNING_FOLDER_PATH/python/lib/"
          fi

     Note that the name of the simulator "slice" in the XCframework may
     be different, depending the CPU architectures your ‘XCFramework’
     supports.

  9. Add a second build step that processes the binary extension modules
     in the standard library into "Framework" format.  Add a "Run
     Script" build step 'directly after' the one you added in step 8,
     named "Prepare Python Binary Modules".  It should also have "Based
     on dependency analysis" unchecked, with the following script
     content:

          set -e

          install_dylib () {
              INSTALL_BASE=$1
              FULL_EXT=$2

              # The name of the extension file
              EXT=$(basename "$FULL_EXT")
              # The location of the extension file, relative to the bundle
              RELATIVE_EXT=${FULL_EXT#$CODESIGNING_FOLDER_PATH/}
              # The path to the extension file, relative to the install base
              PYTHON_EXT=${RELATIVE_EXT/$INSTALL_BASE/}
              # The full dotted name of the extension module, constructed from the file path.
              FULL_MODULE_NAME=$(echo $PYTHON_EXT | cut -d "." -f 1 | tr "/" ".");
              # A bundle identifier; not actually used, but required by Xcode framework packaging
              FRAMEWORK_BUNDLE_ID=$(echo $PRODUCT_BUNDLE_IDENTIFIER.$FULL_MODULE_NAME | tr "_" "-")
              # The name of the framework folder.
              FRAMEWORK_FOLDER="Frameworks/$FULL_MODULE_NAME.framework"

              # If the framework folder doesn't exist, create it.
              if [ ! -d "$CODESIGNING_FOLDER_PATH/$FRAMEWORK_FOLDER" ]; then
                  echo "Creating framework for $RELATIVE_EXT"
                  mkdir -p "$CODESIGNING_FOLDER_PATH/$FRAMEWORK_FOLDER"
                  cp "$CODESIGNING_FOLDER_PATH/dylib-Info-template.plist" "$CODESIGNING_FOLDER_PATH/$FRAMEWORK_FOLDER/Info.plist"
                  plutil -replace CFBundleExecutable -string "$FULL_MODULE_NAME" "$CODESIGNING_FOLDER_PATH/$FRAMEWORK_FOLDER/Info.plist"
                  plutil -replace CFBundleIdentifier -string "$FRAMEWORK_BUNDLE_ID" "$CODESIGNING_FOLDER_PATH/$FRAMEWORK_FOLDER/Info.plist"
              fi

              echo "Installing binary for $FRAMEWORK_FOLDER/$FULL_MODULE_NAME"
              mv "$FULL_EXT" "$CODESIGNING_FOLDER_PATH/$FRAMEWORK_FOLDER/$FULL_MODULE_NAME"
              # Create a placeholder .fwork file where the .so was
              echo "$FRAMEWORK_FOLDER/$FULL_MODULE_NAME" > ${FULL_EXT%.so}.fwork
              # Create a back reference to the .so file location in the framework
              echo "${RELATIVE_EXT%.so}.fwork" > "$CODESIGNING_FOLDER_PATH/$FRAMEWORK_FOLDER/$FULL_MODULE_NAME.origin"
           }

           PYTHON_VER=$(ls -1 "$CODESIGNING_FOLDER_PATH/python/lib")
           echo "Install Python $PYTHON_VER standard library extension modules..."
           find "$CODESIGNING_FOLDER_PATH/python/lib/$PYTHON_VER/lib-dynload" -name "*.so" | while read FULL_EXT; do
              install_dylib python/lib/$PYTHON_VER/lib-dynload/ "$FULL_EXT"
           done

           # Clean up dylib template
           rm -f "$CODESIGNING_FOLDER_PATH/dylib-Info-template.plist"

           echo "Signing frameworks as $EXPANDED_CODE_SIGN_IDENTITY_NAME ($EXPANDED_CODE_SIGN_IDENTITY)..."
           find "$CODESIGNING_FOLDER_PATH/Frameworks" -name "*.framework" -exec /usr/bin/codesign --force --sign "$EXPANDED_CODE_SIGN_IDENTITY" ${OTHER_CODE_SIGN_FLAGS:-} -o runtime --timestamp=none --preserve-metadata=identifier,entitlements,flags --generate-entitlement-der "{}" \;

  10. Add Objective C code to initialize and use a Python interpreter in
     embedded mode.  You should ensure that:

        * *note UTF-8 mode: 3b5. is 'enabled';

        * *note Buffered stdio: 3aa. is 'disabled';

        * *note Writing bytecode: 3a6. is 'disabled';

        * *note Signal handlers: 863. are 'enabled';

        * ‘PYTHONHOME’ for the interpreter is configured to point at the
          ‘python’ subfolder of your app's bundle; and

        * The ‘PYTHONPATH’ for the interpreter includes:

             - the ‘python/lib/python3.X’ subfolder of your app's
               bundle,

             - the ‘python/lib/python3.X/lib-dynload’ subfolder of your
               app's bundle, and

             - the ‘app’ subfolder of your app's bundle

     Your app's bundle location can be determined using ‘[[NSBundle
     mainBundle] resourcePath]’.

Steps 8, 9 and 10 of these instructions assume that you have a single
folder of pure Python application code, named ‘app’.  If you have
third-party binary modules in your app, some additional steps will be
required:

   * You need to ensure that any folders containing third-party binaries
     are either associated with the app target, or copied in as part of
     step 8.  Step 8 should also purge any binaries that are not
     appropriate for the platform a specific build is targeting (i.e.,
     delete any device binaries if you're building an app targeting the
     simulator).

   * Any folders that contain third-party binaries must be processed
     into framework form by step 9.  The invocation of ‘install_dylib’
     that processes the ‘lib-dynload’ folder can be copied and adapted
     for this purpose.

   * If you're using a separate folder for third-party packages, ensure
     that folder is included as part of the ‘PYTHONPATH’ configuration
     in step 10.

   ---------- Footnotes ----------

   (1) https://github.com/pvieito/PythonKit

   (2) https://github.com/python/cpython/tree/3.13/iOS/README.rst


File: python.info,  Node: App Store Compliance<2>,  Prev: Installing Python on iOS,  Up: Using Python on iOS

3.6.3 App Store Compliance
--------------------------

The only mechanism for distributing apps to third-party iOS devices is
to submit the app to the iOS App Store; apps submitted for distribution
must pass Apple's app review process.  This process includes a set of
automated validation rules that inspect the submitted application bundle
for problematic code.

The Python standard library contains some code that is known to violate
these automated rules.  While these violations appear to be false
positives, Apple's review rules cannot be challenged; so, it is
necessary to modify the Python standard library for an app to pass App
Store review.

The Python source tree contains a patch file(1) that will remove all
code that is known to cause issues with the App Store review process.
This patch is applied automatically when building for iOS.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Mac/Resources/app-store-compliance.patch


File: python.info,  Node: 編輯器與 IDE,  Prev: Using Python on iOS,  Up: Python 的設置與使用

3.7 編輯器與 IDE
================

There are a number of IDEs that support Python programming language.
Many editors and IDEs provide syntax highlighting, debugging tools, and
PEP 8(1) checks.

Please go to Python Editors(2) and Integrated Development
Environments(3) for a comprehensive list.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0008/

   (2) https://wiki.python.org/moin/PythonEditors

   (3) https://wiki.python.org/moin/IntegratedDevelopmentEnvironments


File: python.info,  Node: Python 語言參考手冊,  Next: Python 標準函式庫 Standard Library,  Prev: Python 的設置與使用,  Up: Top

4 Python 語言參考手冊
*********************

這份參考手冊會描述 Python 語言的語法及「核心語意」。它雖然簡潔，但也盡量
保持精確並完整。關於非必要的 (non-essential) 內建物件型別、內建函式及模
組的語意，則在 *note Python 標準函式庫 (Standard Library): 12a. 中說明。
關於此語言的非正式介紹，請參閱 *note Python 教學: 1ae0.。對於 C 或 C++ 程
式設計師，還有另外兩個手冊：*note 擴充和嵌入 Python 直譯器: 1ae1.以高階
的視野說明如何編寫 Python 擴充模組，而 *note Python/C API 參考手冊:
1ae2.則詳細說明 C/C++ 程式設計師可用的介面。

* Menu:

* 簡介: 簡介<5>.
* 詞法分析::
* 資料模型::
* 執行模型::
* 模組引入系統::
* 運算式::
* 簡單陳述式::
* 複合陳述式::
* 最高層級元件::
* 完整的語法規格書::


File: python.info,  Node: 簡介<5>,  Next: 詞法分析,  Up: Python 語言參考手冊

4.1 簡介
========

This reference manual describes the Python programming language.  It is
not intended as a tutorial.

While I am trying to be as precise as possible, I chose to use English
rather than formal specifications for everything except syntax and
lexical analysis.  This should make the document more understandable to
the average reader, but will leave room for ambiguities.  Consequently,
if you were coming from Mars and tried to re-implement Python from this
document alone, you might have to guess things and in fact you would
probably end up implementing quite a different language.  On the other
hand, if you are using Python and wonder what the precise rules about a
particular area of the language are, you should definitely be able to
find them here.  If you would like to see a more formal definition of
the language, maybe you could volunteer your time -- or invent a cloning
machine :-).

It is dangerous to add too many implementation details to a language
reference document -- the implementation may change, and other
implementations of the same language may work differently.  On the other
hand, CPython is the one Python implementation in widespread use
(although alternate implementations continue to gain support), and its
particular quirks are sometimes worth being mentioned, especially where
the implementation imposes additional limitations.  Therefore, you'll
find short "implementation notes" sprinkled throughout the text.

Every Python implementation comes with a number of built-in and standard
modules.  These are documented in *note Python 標準函式庫 (Standard
Library): 12a.  A few built-in modules are mentioned when they interact
in a significant way with the language definition.

* Menu:

* Alternate Implementations::
* Notation::


File: python.info,  Node: Alternate Implementations,  Next: Notation,  Up: 簡介<5>

4.1.1 Alternate Implementations
-------------------------------

Though there is one Python implementation which is by far the most
popular, there are some alternate implementations which are of
particular interest to different audiences.

Known implementations include:

CPython

     This is the original and most-maintained implementation of Python,
     written in C. New language features generally appear here first.

Jython

     Python implemented in Java.  This implementation can be used as a
     scripting language for Java applications, or can be used to create
     applications using the Java class libraries.  It is also often used
     to create tests for Java libraries.  More information can be found
     at the Jython website(1).

Python for .NET

     This implementation actually uses the CPython implementation, but
     is a managed .NET application and makes .NET libraries available.
     It was created by Brian Lloyd.  For more information, see the
     Python for .NET home page(2).

IronPython

     An alternate Python for .NET. Unlike Python.NET, this is a complete
     Python implementation that generates IL, and compiles Python code
     directly to .NET assemblies.  It was created by Jim Hugunin, the
     original creator of Jython.  For more information, see the
     IronPython website(3).

PyPy

     An implementation of Python written completely in Python.  It
     supports several advanced features not found in other
     implementations like stackless support and a Just in Time compiler.
     One of the goals of the project is to encourage experimentation
     with the language itself by making it easier to modify the
     interpreter (since it is written in Python).  Additional
     information is available on the PyPy project's home page(4).

Each of these implementations varies in some way from the language as
documented in this manual, or introduces specific information beyond
what's covered in the standard Python documentation.  Please refer to
the implementation-specific documentation to determine what else you
need to know about the specific implementation you're using.

   ---------- Footnotes ----------

   (1) https://www.jython.org/

   (2) https://pythonnet.github.io/

   (3) https://ironpython.net/

   (4) https://www.pypy.org/


File: python.info,  Node: Notation,  Prev: Alternate Implementations,  Up: 簡介<5>

4.1.2 Notation
--------------

The descriptions of lexical analysis and syntax use a modified
Backus–Naur form (BNF)(1) grammar notation.  This uses the following
style of definition:

     name      ::= lc_letter (lc_letter | "_")*
     lc_letter ::= "a"..."z"

The first line says that a ‘name’ is an ‘lc_letter’ followed by a
sequence of zero or more ‘lc_letter’s and underscores.  An ‘lc_letter’
in turn is any of the single characters ‘'a'’ through ‘'z'’.  (This rule
is actually adhered to for the names defined in lexical and grammar
rules in this document.)

Each rule begins with a name (which is the name defined by the rule) and
‘::=’.  A vertical bar (‘|’) is used to separate alternatives; it is the
least binding operator in this notation.  A star (‘*’) means zero or
more repetitions of the preceding item; likewise, a plus (‘+’) means one
or more repetitions, and a phrase enclosed in square brackets (‘[ ]’)
means zero or one occurrences (in other words, the enclosed phrase is
optional).  The ‘*’ and ‘+’ operators bind as tightly as possible;
parentheses are used for grouping.  Literal strings are enclosed in
quotes.  White space is only meaningful to separate tokens.  Rules are
normally contained on a single line; rules with many alternatives may be
formatted alternatively with each line after the first beginning with a
vertical bar.

In lexical definitions (as the example above), two more conventions are
used: Two literal characters separated by three dots mean a choice of
any single character in the given (inclusive) range of ASCII characters.
A phrase between angular brackets (‘<...>’) gives an informal
description of the symbol defined; e.g., this could be used to describe
the notion of 'control character' if needed.

Even though the notation used is almost the same, there is a big
difference between the meaning of lexical and syntactic definitions: a
lexical definition operates on the individual characters of the input
source, while a syntax definition operates on the stream of tokens
generated by the lexical analysis.  All uses of BNF in the next chapter
("Lexical Analysis") are lexical definitions; uses in subsequent
chapters are syntactic definitions.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Backus%E2%80%93Naur_form


File: python.info,  Node: 詞法分析,  Next: 資料模型,  Prev: 簡介<5>,  Up: Python 語言參考手冊

4.2 詞法分析
============

A Python program is read by a 'parser'.  Input to the parser is a stream
of 'tokens', generated by the 'lexical analyzer'.  This chapter
describes how the lexical analyzer breaks a file into tokens.

Python reads program text as Unicode code points; the encoding of a
source file can be given by an encoding declaration and defaults to
UTF-8, see PEP 3120(1) for details.  If the source file cannot be
decoded, a *note SyntaxError: 173. is raised.

* Menu:

* Line structure::
* Other tokens::
* Identifiers and keywords::
* Literals::
* Operators::
* Delimiters::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3120/


File: python.info,  Node: Line structure,  Next: Other tokens,  Up: 詞法分析

4.2.1 Line structure
--------------------

A Python program is divided into a number of 'logical lines'.

* Menu:

* Logical lines::
* Physical lines::
* Comments::
* Encoding declarations::
* Explicit line joining::
* Implicit line joining::
* Blank lines::
* Indentation::
* Whitespace between tokens::


File: python.info,  Node: Logical lines,  Next: Physical lines,  Up: Line structure

4.2.1.1 Logical lines
.....................

The end of a logical line is represented by the token NEWLINE.
Statements cannot cross logical line boundaries except where NEWLINE is
allowed by the syntax (e.g., between statements in compound statements).
A logical line is constructed from one or more 'physical lines' by
following the explicit or implicit 'line joining' rules.


File: python.info,  Node: Physical lines,  Next: Comments,  Prev: Logical lines,  Up: Line structure

4.2.1.2 Physical lines
......................

A physical line is a sequence of characters terminated by an end-of-line
sequence.  In source files and strings, any of the standard platform
line termination sequences can be used - the Unix form using ASCII LF
(linefeed), the Windows form using the ASCII sequence CR LF (return
followed by linefeed), or the old Macintosh form using the ASCII CR
(return) character.  All of these forms can be used equally, regardless
of platform.  The end of input also serves as an implicit terminator for
the final physical line.

When embedding Python, source code strings should be passed to Python
APIs using the standard C conventions for newline characters (the ‘\n’
character, representing ASCII LF, is the line terminator).


File: python.info,  Node: Comments,  Next: Encoding declarations,  Prev: Physical lines,  Up: Line structure

4.2.1.3 Comments
................

A comment starts with a hash character (‘#’) that is not part of a
string literal, and ends at the end of the physical line.  A comment
signifies the end of the logical line unless the implicit line joining
rules are invoked.  Comments are ignored by the syntax.


File: python.info,  Node: Encoding declarations,  Next: Explicit line joining,  Prev: Comments,  Up: Line structure

4.2.1.4 Encoding declarations
.............................

If a comment in the first or second line of the Python script matches
the regular expression ‘coding[=:]\s*([-\w.]+)’, this comment is
processed as an encoding declaration; the first group of this expression
names the encoding of the source code file.  The encoding declaration
must appear on a line of its own.  If it is the second line, the first
line must also be a comment-only line.  The recommended forms of an
encoding expression are

     # -*- coding: <encoding-name> -*-

which is recognized also by GNU Emacs, and

     # vim:fileencoding=<encoding-name>

which is recognized by Bram Moolenaar's VIM.

If no encoding declaration is found, the default encoding is UTF-8.  If
the implicit or explicit encoding of a file is UTF-8, an initial UTF-8
byte-order mark (b'xefxbbxbf') is ignored rather than being a syntax
error.

If an encoding is declared, the encoding name must be recognized by
Python (see *note Standard Encodings: d5f.).  The encoding is used for
all lexical analysis, including string literals, comments and
identifiers.


File: python.info,  Node: Explicit line joining,  Next: Implicit line joining,  Prev: Encoding declarations,  Up: Line structure

4.2.1.5 Explicit line joining
.............................

Two or more physical lines may be joined into logical lines using
backslash characters (‘\’), as follows: when a physical line ends in a
backslash that is not part of a string literal or comment, it is joined
with the following forming a single logical line, deleting the backslash
and the following end-of-line character.  For example:

     if 1900 < year < 2100 and 1 <= month <= 12 \
        and 1 <= day <= 31 and 0 <= hour < 24 \
        and 0 <= minute < 60 and 0 <= second < 60:   # 看起來像個有效日期
             return 1

A line ending in a backslash cannot carry a comment.  A backslash does
not continue a comment.  A backslash does not continue a token except
for string literals (i.e., tokens other than string literals cannot be
split across physical lines using a backslash).  A backslash is illegal
elsewhere on a line outside a string literal.


File: python.info,  Node: Implicit line joining,  Next: Blank lines,  Prev: Explicit line joining,  Up: Line structure

4.2.1.6 Implicit line joining
.............................

Expressions in parentheses, square brackets or curly braces can be split
over more than one physical line without using backslashes.  For
example:

     month_names = ['Januari', 'Februari', 'Maart',      # These are the
                    'April',   'Mei',      'Juni',       # Dutch names
                    'Juli',    'Augustus', 'September',  # for the months
                    'Oktober', 'November', 'December']   # of the year

Implicitly continued lines can carry comments.  The indentation of the
continuation lines is not important.  Blank continuation lines are
allowed.  There is no NEWLINE token between implicit continuation lines.
Implicitly continued lines can also occur within triple-quoted strings
(see below); in that case they cannot carry comments.


File: python.info,  Node: Blank lines,  Next: Indentation,  Prev: Implicit line joining,  Up: Line structure

4.2.1.7 Blank lines
...................

A logical line that contains only spaces, tabs, formfeeds and possibly a
comment, is ignored (i.e., no NEWLINE token is generated).  During
interactive input of statements, handling of a blank line may differ
depending on the implementation of the read-eval-print loop.  In the
standard interactive interpreter, an entirely blank logical line (i.e.
one containing not even whitespace or a comment) terminates a multi-line
statement.


File: python.info,  Node: Indentation,  Next: Whitespace between tokens,  Prev: Blank lines,  Up: Line structure

4.2.1.8 Indentation
...................

Leading whitespace (spaces and tabs) at the beginning of a logical line
is used to compute the indentation level of the line, which in turn is
used to determine the grouping of statements.

Tabs are replaced (from left to right) by one to eight spaces such that
the total number of characters up to and including the replacement is a
multiple of eight (this is intended to be the same rule as used by
Unix).  The total number of spaces preceding the first non-blank
character then determines the line's indentation.  Indentation cannot be
split over multiple physical lines using backslashes; the whitespace up
to the first backslash determines the indentation.

Indentation is rejected as inconsistent if a source file mixes tabs and
spaces in a way that makes the meaning dependent on the worth of a tab
in spaces; a *note TabError: 4e9. is raised in that case.

'Cross-platform compatibility note:' because of the nature of text
editors on non-UNIX platforms, it is unwise to use a mixture of spaces
and tabs for the indentation in a single source file.  It should also be
noted that different platforms may explicitly limit the maximum
indentation level.

A formfeed character may be present at the start of the line; it will be
ignored for the indentation calculations above.  Formfeed characters
occurring elsewhere in the leading whitespace have an undefined effect
(for instance, they may reset the space count to zero).

The indentation levels of consecutive lines are used to generate INDENT
and DEDENT tokens, using a stack, as follows.

Before the first line of the file is read, a single zero is pushed on
the stack; this will never be popped off again.  The numbers pushed on
the stack will always be strictly increasing from bottom to top.  At the
beginning of each logical line, the line's indentation level is compared
to the top of the stack.  If it is equal, nothing happens.  If it is
larger, it is pushed on the stack, and one INDENT token is generated.
If it is smaller, it 'must' be one of the numbers occurring on the
stack; all numbers on the stack that are larger are popped off, and for
each number popped off a DEDENT token is generated.  At the end of the
file, a DEDENT token is generated for each number remaining on the stack
that is larger than zero.

Here is an example of a correctly (though confusingly) indented piece of
Python code:

     def perm(l):
             # Compute the list of all permutations of l
         if len(l) <= 1:
                       return [l]
         r = []
         for i in range(len(l)):
                  s = l[:i] + l[i+1:]
                  p = perm(s)
                  for x in p:
                   r.append(l[i:i+1] + x)
         return r

The following example shows various indentation errors:

      def perm(l):                       # error: first line indented
     for i in range(len(l)):             # error: not indented
         s = l[:i] + l[i+1:]
             p = perm(l[:i] + l[i+1:])   # error: unexpected indent
             for x in p:
                     r.append(l[i:i+1] + x)
                 return r                # error: inconsistent dedent

(Actually, the first three errors are detected by the parser; only the
last error is found by the lexical analyzer -- the indentation of
‘return r’ does not match a level popped off the stack.)


File: python.info,  Node: Whitespace between tokens,  Prev: Indentation,  Up: Line structure

4.2.1.9 Whitespace between tokens
.................................

Except at the beginning of a logical line or in string literals, the
whitespace characters space, tab and formfeed can be used
interchangeably to separate tokens.  Whitespace is needed between two
tokens only if their concatenation could otherwise be interpreted as a
different token (e.g., ab is one token, but a b is two tokens).


File: python.info,  Node: Other tokens,  Next: Identifiers and keywords,  Prev: Line structure,  Up: 詞法分析

4.2.2 Other tokens
------------------

Besides NEWLINE, INDENT and DEDENT, the following categories of tokens
exist: 'identifiers', 'keywords', 'literals', 'operators', and
'delimiters'.  Whitespace characters (other than line terminators,
discussed earlier) are not tokens, but serve to delimit tokens.  Where
ambiguity exists, a token comprises the longest possible string that
forms a legal token, when read from left to right.


File: python.info,  Node: Identifiers and keywords,  Next: Literals,  Prev: Other tokens,  Up: 詞法分析

4.2.3 Identifiers and keywords
------------------------------

Identifiers (also referred to as 'names') are described by the following
lexical definitions.

The syntax of identifiers in Python is based on the Unicode standard
annex UAX-31, with elaboration and changes as defined below; see also
PEP 3131(1) for further details.

Within the ASCII range (U+0001..U+007F), the valid characters for
identifiers are the same as in Python 2.x: the uppercase and lowercase
letters ‘A’ through ‘Z’, the underscore ‘_’ and, except for the first
character, the digits ‘0’ through ‘9’.

Python 3.0 introduces additional characters from outside the ASCII range
(see PEP 3131(2)).  For these characters, the classification uses the
version of the Unicode Character Database as included in the *note
unicodedata: ee. module.

Identifiers are unlimited in length.  Case is significant.

     identifier   ::= xid_start xid_continue*
     id_start     ::= <all characters in general categories Lu, Ll, Lt, Lm, Lo, Nl, the underscore, and characters with the Other_ID_Start property>
     id_continue  ::= <all characters in id_start, plus characters in the categories Mn, Mc, Nd, Pc and others with the Other_ID_Continue property>
     xid_start    ::= <all characters in id_start whose NFKC normalization is in "id_start xid_continue*">
     xid_continue ::= <all characters in id_continue whose NFKC normalization is in "id_continue*">

The Unicode category codes mentioned above stand for:

   * 'Lu' - 大寫字母

   * 'Ll' - 小寫字母

   * 'Lt' - titlecase letters

   * 'Lm' - modifier letters

   * 'Lo' - 其他字母

   * 'Nl' - letter numbers

   * 'Mn' - nonspacing marks

   * 'Mc' - spacing combining marks

   * 'Nd' - 十進位數字

   * 'Pc' - connector punctuations

   * 'Other_ID_Start' - explicit list of characters in PropList.txt(3)
     to support backwards compatibility

   * 'Other_ID_Continue' - likewise

All identifiers are converted into the normal form NFKC while parsing;
comparison of identifiers is based on NFKC.

A non-normative HTML file listing all valid identifier characters for
Unicode 15.1.0 can be found at
‘https://www.unicode.org/Public/15.1.0/ucd/DerivedCoreProperties.txt’

* Menu:

* 關鍵字::
* 軟關鍵字::
* Reserved classes of identifiers::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3131/

   (2) https://peps.python.org/pep-3131/

   (3) https://www.unicode.org/Public/15.1.0/ucd/PropList.txt


File: python.info,  Node: 關鍵字,  Next: 軟關鍵字,  Up: Identifiers and keywords

4.2.3.1 關鍵字
..............

The following identifiers are used as reserved words, or 'keywords' of
the language, and cannot be used as ordinary identifiers.  They must be
spelled exactly as written here:

     False      await      else       import     pass
     None       break      except     in         raise
     True       class      finally    is         return
     and        continue   for        lambda     try
     as         def        from       nonlocal   while
     assert     del        global     not        with
     async      elif       if         or         yield


File: python.info,  Node: 軟關鍵字,  Next: Reserved classes of identifiers,  Prev: 關鍵字,  Up: Identifiers and keywords

4.2.3.2 軟關鍵字
................

在 3.10 版被加入.

Some identifiers are only reserved under specific contexts.  These are
known as 'soft keywords'.  The identifiers ‘match’, ‘case’, ‘type’ and
‘_’ can syntactically act as keywords in certain contexts, but this
distinction is done at the parser level, not when tokenizing.

As soft keywords, their use in the grammar is possible while still
preserving compatibility with existing code that uses these names as
identifier names.

‘match’, ‘case’, and ‘_’ are used in the *note match: 7b1. statement.
‘type’ is used in the *note type: 3de. statement.

在 3.12 版的變更: ‘type’ 現在是軟關鍵字。


File: python.info,  Node: Reserved classes of identifiers,  Prev: 軟關鍵字,  Up: Identifiers and keywords

4.2.3.3 Reserved classes of identifiers
.......................................

Certain classes of identifiers (besides keywords) have special meanings.
These classes are identified by the patterns of leading and trailing
underscore characters:

‘_*’

     Not imported by ‘from module import *’.

‘_’

     In a ‘case’ pattern within a *note match: 7b1. statement, ‘_’ is a
     *note soft keyword: 7b0. that denotes a *note wildcard: 7b2.

     Separately, the interactive interpreter makes the result of the
     last evaluation available in the variable ‘_’.  (It is stored in
     the *note builtins: e. module, alongside built-in functions like
     ‘print’.)

     Elsewhere, ‘_’ is a regular identifier.  It is often used to name
     "special" items, but it is not special to Python itself.

          備註: The name ‘_’ is often used in conjunction with
          internationalization; refer to the documentation for the *note
          gettext: 59. module for more information on this convention.

          It is also commonly used for unused variables.

‘__*__’

     System-defined names, informally known as "dunder" names.  These
     names are defined by the interpreter and its implementation
     (including the standard library).  Current system names are
     discussed in the *note Special method names: c15. section and
     elsewhere.  More will likely be defined in future versions of
     Python.  'Any' use of ‘__*__’ names, in any context, that does not
     follow explicitly documented use, is subject to breakage without
     warning.

‘__*’

     Class-private names.  Names in this category, when used within the
     context of a class definition, are re-written to use a mangled form
     to help avoid name clashes between "private" attributes of base and
     derived classes.  See section *note Identifiers (Names): 1d92.


File: python.info,  Node: Literals,  Next: Operators,  Prev: Identifiers and keywords,  Up: 詞法分析

4.2.4 Literals
--------------

Literals are notations for constant values of some built-in types.

* Menu:

* String and Bytes literals::
* String literal concatenation::
* f-string（f 字串）::
* Numeric literals::
* Integer literals::
* 浮點數常數 (Floating-point literals): 浮點數常數 Floating-point literals.
* Imaginary literals::


File: python.info,  Node: String and Bytes literals,  Next: String literal concatenation,  Up: Literals

4.2.4.1 String and Bytes literals
.................................

String literals are described by the following lexical definitions:

     stringliteral   ::= [stringprefix](shortstring | longstring)
     stringprefix    ::= "r" | "u" | "R" | "U" | "f" | "F"
                         | "fr" | "Fr" | "fR" | "FR" | "rf" | "rF" | "Rf" | "RF"
     shortstring     ::= "'" shortstringitem* "'" | '"' shortstringitem* '"'
     longstring      ::= "'''" longstringitem* "'''" | '"""' longstringitem* '"""'
     shortstringitem ::= shortstringchar | stringescapeseq
     longstringitem  ::= longstringchar | stringescapeseq
     shortstringchar ::= <any source character except "\" or newline or the quote>
     longstringchar  ::= <any source character except "\">
     stringescapeseq ::= "\" <any source character>

     bytesliteral   ::= bytesprefix(shortbytes | longbytes)
     bytesprefix    ::= "b" | "B" | "br" | "Br" | "bR" | "BR" | "rb" | "rB" | "Rb" | "RB"
     shortbytes     ::= "'" shortbytesitem* "'" | '"' shortbytesitem* '"'
     longbytes      ::= "'''" longbytesitem* "'''" | '"""' longbytesitem* '"""'
     shortbytesitem ::= shortbyteschar | bytesescapeseq
     longbytesitem  ::= longbyteschar | bytesescapeseq
     shortbyteschar ::= <any ASCII character except "\" or newline or the quote>
     longbyteschar  ::= <any ASCII character except "\">
     bytesescapeseq ::= "\" <any ASCII character>

One syntactic restriction not indicated by these productions is that
whitespace is not allowed between the *note stringprefix: 1d98. or *note
bytesprefix: 1da1. and the rest of the literal.  The source character
set is defined by the encoding declaration; it is UTF-8 if no encoding
declaration is given in the source file; see section *note Encoding
declarations: 1d79.

In plain English: Both types of literals can be enclosed in matching
single quotes (‘'’) or double quotes (‘"’).  They can also be enclosed
in matching groups of three single or double quotes (these are generally
referred to as 'triple-quoted strings').  The backslash (‘\’) character
is used to give special meaning to otherwise ordinary characters like
‘n’, which means 'newline' when escaped (‘\n’).  It can also be used to
escape characters that otherwise have a special meaning, such as
newline, backslash itself, or the quote character.  See *note escape
sequences: 400. below for examples.

Bytes literals are always prefixed with ‘'b'’ or ‘'B'’; they produce an
instance of the *note bytes: 1a5. type instead of the *note str: 3f2.
type.  They may only contain ASCII characters; bytes with a numeric
value of 128 or greater must be expressed with escapes.

Both string and bytes literals may optionally be prefixed with a letter
‘'r'’ or ‘'R'’; such constructs are called 'raw string literals' and
'raw bytes literals' respectively and treat backslashes as literal
characters.  As a result, in raw string literals, ‘'\U'’ and ‘'\u'’
escapes are not treated specially.

在 3.3 版被加入: The ‘'rb'’ prefix of raw bytes literals has been added
as a synonym of ‘'br'’.

Support for the unicode legacy literal (‘u'value'’) was reintroduced to
simplify the maintenance of dual Python 2.x and 3.x codebases.  See PEP
414(1) for more information.

A string literal with ‘'f'’ or ‘'F'’ in its prefix is a 'formatted
string literal'; see *note f-string（f 字串）: 94d.  The ‘'f'’ may be
combined with ‘'r'’, but not with ‘'b'’ or ‘'u'’, therefore raw
formatted strings are possible, but formatted bytes literals are not.

In triple-quoted literals, unescaped newlines and quotes are allowed
(and are retained), except that three unescaped quotes in a row
terminate the literal.  (A "quote" is the character used to open the
literal, i.e.  either ‘'’ or ‘"’.)

* Menu:

* 跳脫序列::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0414/


File: python.info,  Node: 跳脫序列,  Up: String and Bytes literals

4.2.4.2 跳脫序列
................

Unless an ‘'r'’ or ‘'R'’ prefix is present, escape sequences in string
and bytes literals are interpreted according to rules similar to those
used by Standard C. The recognized escape sequences are:

Escape Sequence               含義                                  註解
                                                                    
--------------------------------------------------------------------------------
                                                                    
‘\’<newline>                  Backslash and newline ignored         (1)
                                                                    
                                                                    
‘\\’                          Backslash (‘\’)
                              
                                                                    
‘\'’                          單引號 (‘'’)
                              
                                                                    
‘\"’                          雙引號 (‘"’)
                              
                                                                    
‘\a’                          ASCII Bell (BEL)
                              
                                                                    
‘\b’                          ASCII Backspace (BS)
                              
                                                                    
‘\f’                          ASCII Formfeed (FF)
                              
                                                                    
‘\n’                          ASCII Linefeed (LF)
                              
                                                                    
‘\r’                          ASCII Carriage Return (CR)
                              
                                                                    
‘\t’                          ASCII Horizontal Tab (TAB)
                              
                                                                    
‘\v’                          ASCII Vertical Tab (VT)
                              
                                                                    
‘\OOO’                        Character with octal value 'ooo'      (2,4)
                                                                    
                                                                    
‘\xHH’                        Character with hex value 'hh'         (3,4)
                                                                    

Escape sequences only recognized in string literals are:

Escape Sequence               含義                                  註解
                                                                    
--------------------------------------------------------------------------------
                                                                    
‘\N{NAME}’                    Character named 'name' in the         (5)
                              Unicode database                      
                              
                                                                    
‘\uXXXX’                      Character with 16-bit hex value       (6)
                              'xxxx'                                
                              
                                                                    
‘\UXXXXXXXX’                  Character with 32-bit hex value       (7)
                              'xxxxxxxx'                            
                              

註解：

  1. A backslash can be added at the end of a line to ignore the
     newline:

          >>> 'This string will not include \
          ... backslashes or newline characters.'
          'This string will not include backslashes or newline characters.'

     The same result can be achieved using *note triple-quoted strings:
     1d96, or parentheses and *note string literal concatenation: 1daa.

  2. As in Standard C, up to three octal digits are accepted.

     在 3.11 版的變更: Octal escapes with value larger than ‘0o377’
     produce a *note DeprecationWarning: 18b.

     在 3.12 版的變更: Octal escapes with value larger than ‘0o377’
     produce a *note SyntaxWarning: 40c.  In a future Python version
     they will be eventually a *note SyntaxError: 173.

  3. Unlike in Standard C, exactly two hex digits are required.

  4. In a bytes literal, hexadecimal and octal escapes denote the byte
     with the given value.  In a string literal, these escapes denote a
     Unicode character with the given value.

  5. 
     在 3.3 版的變更: Support for name aliases (1) has been added.

  6. Exactly four hex digits are required.

  7. Any Unicode character can be encoded this way.  Exactly eight hex
     digits are required.

Unlike Standard C, all unrecognized escape sequences are left in the
string unchanged, i.e., 'the backslash is left in the result'.  (This
behavior is useful when debugging: if an escape sequence is mistyped,
the resulting output is more easily recognized as broken.)  It is also
important to note that the escape sequences only recognized in string
literals fall into the category of unrecognized escapes for bytes
literals.

在 3.6 版的變更: Unrecognized escape sequences produce a *note
DeprecationWarning: 18b.

在 3.12 版的變更: Unrecognized escape sequences produce a *note
SyntaxWarning: 40c.  In a future Python version they will be eventually
a *note SyntaxError: 173.

Even in a raw literal, quotes can be escaped with a backslash, but the
backslash remains in the result; for example, ‘r"\""’ is a valid string
literal consisting of two characters: a backslash and a double quote;
‘r"\"’ is not a valid string literal (even a raw string cannot end in an
odd number of backslashes).  Specifically, 'a raw literal cannot end in
a single backslash' (since the backslash would escape the following
quote character).  Note also that a single backslash followed by a
newline is interpreted as those two characters as part of the literal,
'not' as a line continuation.

   ---------- Footnotes ----------

   (1) ‘https://www.unicode.org/Public/15.1.0/ucd/NameAliases.txt’


File: python.info,  Node: String literal concatenation,  Next: f-string（f 字串）,  Prev: String and Bytes literals,  Up: Literals

4.2.4.3 String literal concatenation
....................................

Multiple adjacent string or bytes literals (delimited by whitespace),
possibly using different quoting conventions, are allowed, and their
meaning is the same as their concatenation.  Thus, ‘"hello" 'world'’ is
equivalent to ‘"helloworld"’.  This feature can be used to reduce the
number of backslashes needed, to split long strings conveniently across
long lines, or even to add comments to parts of strings, for example:

     re.compile("[A-Za-z_]"       # letter or underscore
                "[A-Za-z0-9_]*"   # letter, digit or underscore
               )

Note that this feature is defined at the syntactical level, but
implemented at compile time.  The '+' operator must be used to
concatenate string expressions at run time.  Also note that literal
concatenation can use different quoting styles for each component (even
mixing raw strings and triple quoted strings), and formatted string
literals may be concatenated with plain string literals.


File: python.info,  Node: f-string（f 字串）,  Next: Numeric literals,  Prev: String literal concatenation,  Up: Literals

4.2.4.4 f-string（f 字串）
..........................

在 3.6 版被加入.

A 'formatted string literal' or 'f-string' is a string literal that is
prefixed with ‘'f'’ or ‘'F'’.  These strings may contain replacement
fields, which are expressions delimited by curly braces ‘{}’.  While
other string literals always have a constant value, formatted strings
are really expressions evaluated at run time.

Escape sequences are decoded like in ordinary string literals (except
when a literal is also marked as a raw string).  After decoding, the
grammar for the contents of the string is:

     f_string          ::= (literal_char | "{{" | "}}" | replacement_field)*
     replacement_field ::= "{" f_expression ["="] ["!" conversion] [":" format_spec] "}"
     f_expression      ::= (conditional_expression | "*" or_expr)
                             ("," conditional_expression | "," "*" or_expr)* [","]
                           | yield_expression
     conversion        ::= "s" | "r" | "a"
     format_spec       ::= (literal_char | replacement_field)*
     literal_char      ::= <any code point except "{", "}" or NULL>

The parts of the string outside curly braces are treated literally,
except that any doubled curly braces ‘'{{'’ or ‘'}}'’ are replaced with
the corresponding single curly brace.  A single opening curly bracket
‘'{'’ marks a replacement field, which starts with a Python expression.
To display both the expression text and its value after evaluation,
(useful in debugging), an equal sign ‘'='’ may be added after the
expression.  A conversion field, introduced by an exclamation point
‘'!'’ may follow.  A format specifier may also be appended, introduced
by a colon ‘':'’.  A replacement field ends with a closing curly bracket
‘'}'’.

Expressions in formatted string literals are treated like regular Python
expressions surrounded by parentheses, with a few exceptions.  An empty
expression is not allowed, and both *note lambda: 1234. and assignment
expressions ‘:=’ must be surrounded by explicit parentheses.  Each
expression is evaluated in the context where the formatted string
literal appears, in order from left to right.  Replacement expressions
can contain newlines in both single-quoted and triple-quoted f-strings
and they can contain comments.  Everything that comes after a ‘#’ inside
a replacement field is a comment (even closing braces and quotes).  In
that case, replacement fields must be closed in a different line.

     >>> f"abc{a # This is a comment }"
     ... + 3}"
     'abc5'

在 3.7 版的變更: Prior to Python 3.7, an *note await: 19f. expression
and comprehensions containing an *note async for: a4e. clause were
illegal in the expressions in formatted string literals due to a problem
with the implementation.

在 3.12 版的變更: Prior to Python 3.12, comments were not allowed inside
f-string replacement fields.

When the equal sign ‘'='’ is provided, the output will have the
expression text, the ‘'='’ and the evaluated value.  Spaces after the
opening brace ‘'{'’, within the expression and after the ‘'='’ are all
retained in the output.  By default, the ‘'='’ causes the *note repr():
7a1. of the expression to be provided, unless there is a format
specified.  When a format is specified it defaults to the *note str():
3f2. of the expression unless a conversion ‘'!r'’ is declared.

在 3.8 版被加入: 等號 ‘'='’。

If a conversion is specified, the result of evaluating the expression is
converted before formatting.  Conversion ‘'!s'’ calls *note str(): 3f2.
on the result, ‘'!r'’ calls *note repr(): 7a1, and ‘'!a'’ calls *note
ascii(): 1354.

The result is then formatted using the *note format(): 5c3. protocol.
The format specifier is passed to the *note __format__(): 5c5. method of
the expression or conversion result.  An empty string is passed when the
format specifier is omitted.  The formatted result is then included in
the final value of the whole string.

Top-level format specifiers may include nested replacement fields.
These nested fields may include their own conversion fields and *note
format specifiers: 1c8, but may not include more deeply nested
replacement fields.  The *note format specifier mini-language: 1c8. is
the same as that used by the *note str.format(): 5c7. method.

Formatted string literals may be concatenated, but replacement fields
cannot be split across literals.

Some examples of formatted string literals:

     >>> name = "Fred"
     >>> f"He said his name is {name!r}."
     "He said his name is 'Fred'."
     >>> f"He said his name is {repr(name)}."  # repr() is equivalent to !r
     "He said his name is 'Fred'."
     >>> width = 10
     >>> precision = 4
     >>> value = decimal.Decimal("12.34567")
     >>> f"result: {value:{width}.{precision}}"  # nested fields
     'result:      12.35'
     >>> today = datetime(year=2017, month=1, day=27)
     >>> f"{today:%B %d, %Y}"  # using date format specifier
     'January 27, 2017'
     >>> f"{today=:%B %d, %Y}" # using date format specifier and debugging
     'today=January 27, 2017'
     >>> number = 1024
     >>> f"{number:#0x}"  # using integer format specifier
     '0x400'
     >>> foo = "bar"
     >>> f"{ foo = }" # preserves whitespace
     " foo = 'bar'"
     >>> line = "The mill's closed"
     >>> f"{line = }"
     'line = "The mill\'s closed"'
     >>> f"{line = :20}"
     "line = The mill's closed   "
     >>> f"{line = !r:20}"
     'line = "The mill\'s closed" '

Reusing the outer f-string quoting type inside a replacement field is
permitted:

     >>> a = dict(x=2)
     >>> f"abc {a["x"]} def"
     'abc 2 def'

在 3.12 版的變更: Prior to Python 3.12, reuse of the same quoting type
of the outer f-string inside a replacement field was not possible.

Backslashes are also allowed in replacement fields and are evaluated the
same way as in any other context:

     >>> a = ["a", "b", "c"]
     >>> print(f"List a contains:\n{"\n".join(a)}")
     List a contains:
     a
     b
     c

在 3.12 版的變更: Prior to Python 3.12, backslashes were not permitted
inside an f-string replacement field.

Formatted string literals cannot be used as docstrings, even if they do
not include expressions.

     >>> def foo():
     ...     f"Not a docstring"
     ...
     >>> foo.__doc__ is None
     True

See also PEP 498(1) for the proposal that added formatted string
literals, and *note str.format(): 5c7, which uses a related format
string mechanism.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0498/


File: python.info,  Node: Numeric literals,  Next: Integer literals,  Prev: f-string（f 字串）,  Up: Literals

4.2.4.5 Numeric literals
........................

There are three types of numeric literals: integers, floating-point
numbers, and imaginary numbers.  There are no complex literals (complex
numbers can be formed by adding a real number and an imaginary number).

Note that numeric literals do not include a sign; a phrase like ‘-1’ is
actually an expression composed of the unary operator '‘-’' and the
literal ‘1’.


File: python.info,  Node: Integer literals,  Next: 浮點數常數 Floating-point literals,  Prev: Numeric literals,  Up: Literals

4.2.4.6 Integer literals
........................

Integer literals are described by the following lexical definitions:

     integer      ::= decinteger | bininteger | octinteger | hexinteger
     decinteger   ::= nonzerodigit (["_"] digit)* | "0"+ (["_"] "0")*
     bininteger   ::= "0" ("b" | "B") (["_"] bindigit)+
     octinteger   ::= "0" ("o" | "O") (["_"] octdigit)+
     hexinteger   ::= "0" ("x" | "X") (["_"] hexdigit)+
     nonzerodigit ::= "1"..."9"
     digit        ::= "0"..."9"
     bindigit     ::= "0" | "1"
     octdigit     ::= "0"..."7"
     hexdigit     ::= digit | "a"..."f" | "A"..."F"

There is no limit for the length of integer literals apart from what can
be stored in available memory.

Underscores are ignored for determining the numeric value of the
literal.  They can be used to group digits for enhanced readability.
One underscore can occur between digits, and after base specifiers like
‘0x’.

Note that leading zeros in a non-zero decimal number are not allowed.
This is for disambiguation with C-style octal literals, which Python
used before version 3.0.

Some examples of integer literals:

     7     2147483647                        0o177    0b100110111
     3     79228162514264337593543950336     0o377    0xdeadbeef
           100_000_000_000                   0b_1110_0101

在 3.6 版的變更: Underscores are now allowed for grouping purposes in
literals.


File: python.info,  Node: 浮點數常數 Floating-point literals,  Next: Imaginary literals,  Prev: Integer literals,  Up: Literals

4.2.4.7 浮點數常數 (Floating-point literals)
............................................

Floating-point literals are described by the following lexical
definitions:

     floatnumber   ::= pointfloat | exponentfloat
     pointfloat    ::= [digitpart] fraction | digitpart "."
     exponentfloat ::= (digitpart | pointfloat) exponent
     digitpart     ::= digit (["_"] digit)*
     fraction      ::= "." digitpart
     exponent      ::= ("e" | "E") ["+" | "-"] digitpart

Note that the integer and exponent parts are always interpreted using
radix 10.  For example, ‘077e010’ is legal, and denotes the same number
as ‘77e10’.  The allowed range of floating-point literals is
implementation-dependent.  As in integer literals, underscores are
supported for digit grouping.

一些浮點數常數的範例：

     3.14    10.    .001    1e100    3.14e-10    0e0    3.14_15_93

在 3.6 版的變更: Underscores are now allowed for grouping purposes in
literals.


File: python.info,  Node: Imaginary literals,  Prev: 浮點數常數 Floating-point literals,  Up: Literals

4.2.4.8 Imaginary literals
..........................

Imaginary literals are described by the following lexical definitions:

     imagnumber ::= (floatnumber | digitpart) ("j" | "J")

An imaginary literal yields a complex number with a real part of 0.0.
Complex numbers are represented as a pair of floating-point numbers and
have the same restrictions on their range.  To create a complex number
with a nonzero real part, add a floating-point number to it, e.g.,
‘(3+4j)’.  Some examples of imaginary literals:

     3.14j   10.j    10j     .001j   1e100j   3.14e-10j   3.14_15_93j


File: python.info,  Node: Operators,  Next: Delimiters,  Prev: Literals,  Up: 詞法分析

4.2.5 Operators
---------------

The following tokens are operators:

     +       -       *       **      /       //      %      @
     <<      >>      &       |       ^       ~       :=
     <       >       <=      >=      ==      !=


File: python.info,  Node: Delimiters,  Prev: Operators,  Up: 詞法分析

4.2.6 Delimiters
----------------

The following tokens serve as delimiters in the grammar:

     (       )       [       ]       {       }
     ,       :       !       .       ;       @       =
     ->      +=      -=      *=      /=      //=     %=
     @=      &=      |=      ^=      >>=     <<=     **=

The period can also occur in floating-point and imaginary literals.  A
sequence of three periods has a special meaning as an ellipsis literal.
The second half of the list, the augmented assignment operators, serve
lexically as delimiters, but also perform an operation.

The following printing ASCII characters have special meaning as part of
other tokens or are otherwise significant to the lexical analyzer:

     '       "       #       \

The following printing ASCII characters are not used in Python.  Their
occurrence outside string literals and comments is an unconditional
error:

     $       ?       `

註解
....


File: python.info,  Node: 資料模型,  Next: 執行模型,  Prev: 詞法分析,  Up: Python 語言參考手冊

4.3 資料模型
============

* Menu:

* Objects, values and types: Objects values and types.
* 標準型別階層::
* Special method names::
* 協程::


File: python.info,  Node: Objects values and types,  Next: 標準型別階層,  Up: 資料模型

4.3.1 Objects, values and types
-------------------------------

'Objects' are Python's abstraction for data.  All data in a Python
program is represented by objects or by relations between objects.  (In
a sense, and in conformance to Von Neumann's model of a "stored program
computer", code is also represented by objects.)

Every object has an identity, a type and a value.  An object's
'identity' never changes once it has been created; you may think of it
as the object's address in memory.  The *note is: 2c6. operator compares
the identity of two objects; the *note id(): 1390. function returns an
integer representing its identity.

'CPython 實作細節：' For CPython, ‘id(x)’ is the memory address where
‘x’ is stored.

An object's type determines the operations that the object supports
(e.g., "does it have a length?")  and also defines the possible values
for objects of that type.  The *note type(): cef. function returns an
object's type (which is an object itself).  Like its identity, an
object's 'type' is also unchangeable.  (1)

The 'value' of some objects can change.  Objects whose value can change
are said to be 'mutable'; objects whose value is unchangeable once they
are created are called 'immutable'.  (The value of an immutable
container object that contains a reference to a mutable object can
change when the latter's value is changed; however the container is
still considered immutable, because the collection of objects it
contains cannot be changed.  So, immutability is not strictly the same
as having an unchangeable value, it is more subtle.)  An object's
mutability is determined by its type; for instance, numbers, strings and
tuples are immutable, while dictionaries and lists are mutable.

Objects are never explicitly destroyed; however, when they become
unreachable they may be garbage-collected.  An implementation is allowed
to postpone garbage collection or omit it altogether -- it is a matter
of implementation quality how garbage collection is implemented, as long
as no objects are collected that are still reachable.

'CPython 實作細節：' CPython currently uses a reference-counting scheme
with (optional) delayed detection of cyclically linked garbage, which
collects most objects as soon as they become unreachable, but is not
guaranteed to collect garbage containing circular references.  See the
documentation of the *note gc: 56. module for information on controlling
the collection of cyclic garbage.  Other implementations act differently
and CPython may change.  Do not depend on immediate finalization of
objects when they become unreachable (so you should always close files
explicitly).

Note that the use of the implementation's tracing or debugging
facilities may keep objects alive that would normally be collectable.
Also note that catching an exception with a *note try: 68c...*note
except: 171. statement may keep objects alive.

Some objects contain references to "external" resources such as open
files or windows.  It is understood that these resources are freed when
the object is garbage-collected, but since garbage collection is not
guaranteed to happen, such objects also provide an explicit way to
release the external resource, usually a ‘close()’ method.  Programs are
strongly recommended to explicitly close such objects.  The *note try:
68c...*note finally: 96e. statement and the *note with: 577. statement
provide convenient ways to do this.

Some objects contain references to other objects; these are called
'containers'.  Examples of containers are tuples, lists and
dictionaries.  The references are part of a container's value.  In most
cases, when we talk about the value of a container, we imply the values,
not the identities of the contained objects; however, when we talk about
the mutability of a container, only the identities of the immediately
contained objects are implied.  So, if an immutable container (like a
tuple) contains a reference to a mutable object, its value changes if
that mutable object is changed.

Types affect almost all aspects of object behavior.  Even the importance
of object identity is affected in some sense: for immutable types,
operations that compute new values may actually return a reference to
any existing object with the same type and value, while for mutable
objects this is not allowed.  For example, after ‘a = 1; b = 1’, 'a' and
'b' may or may not refer to the same object with the value one,
depending on the implementation.  This is because *note int: 23c. is an
immutable type, so the reference to ‘1’ can be reused.  This behaviour
depends on the implementation used, so should not be relied upon, but is
something to be aware of when making use of object identity tests.
However, after ‘c = []; d = []’, 'c' and 'd' are guaranteed to refer to
two different, unique, newly created empty lists.  (Note that ‘e = f =
[]’ assigns the 'same' object to both 'e' and 'f'.)

   ---------- Footnotes ----------

   (1) It 'is' possible in some cases to change an object's type, under
certain controlled conditions.  It generally isn't a good idea though,
since it can lead to some very strange behaviour if it is handled
incorrectly.


File: python.info,  Node: 標準型別階層,  Next: Special method names,  Prev: Objects values and types,  Up: 資料模型

4.3.2 標準型別階層
------------------

Below is a list of the types that are built into Python.  Extension
modules (written in C, Java, or other languages, depending on the
implementation) can define additional types.  Future versions of Python
may add types to the type hierarchy (e.g., rational numbers, efficiently
stored arrays of integers, etc.), although such additions will often be
provided via the standard library instead.

Some of the type descriptions below contain a paragraph listing 'special
attributes.'  These are attributes that provide access to the
implementation and are not intended for general use.  Their definition
may change in the future.

* Menu:

* None::
* NotImplemented::
* Ellipsis::
* numbers.Number: numbers Number.
* Sequences::
* Set types::
* Mappings::
* Callable types::
* 模組: 模組<2>.
* Custom classes::
* Class instances::
* I/O objects (also known as file objects): I/O objects also known as file objects.
* Internal types::


File: python.info,  Node: None,  Next: NotImplemented,  Up: 標準型別階層

4.3.2.1 None
............

This type has a single value.  There is a single object with this value.
This object is accessed through the built-in name ‘None’.  It is used to
signify the absence of a value in many situations, e.g., it is returned
from functions that don't explicitly return anything.  Its truth value
is false.


File: python.info,  Node: NotImplemented,  Next: Ellipsis,  Prev: None,  Up: 標準型別階層

4.3.2.2 NotImplemented
......................

This type has a single value.  There is a single object with this value.
This object is accessed through the built-in name *note NotImplemented:
776.  Numeric methods and rich comparison methods should return this
value if they do not implement the operation for the operands provided.
(The interpreter will then try the reflected operation, or some other
fallback, depending on the operator.)  It should not be evaluated in a
boolean context.

更多細節請見 *note 實作算術操作: 1dd9.。

在 3.9 版的變更: Evaluating *note NotImplemented: 776. in a boolean
context is deprecated.  While it currently evaluates as true, it will
emit a *note DeprecationWarning: 18b.  It will raise a *note TypeError:
4dd. in a future version of Python.


File: python.info,  Node: Ellipsis,  Next: numbers Number,  Prev: NotImplemented,  Up: 標準型別階層

4.3.2.3 Ellipsis
................

This type has a single value.  There is a single object with this value.
This object is accessed through the literal ‘...’ or the built-in name
‘Ellipsis’.  Its truth value is true.


File: python.info,  Node: numbers Number,  Next: Sequences,  Prev: Ellipsis,  Up: 標準型別階層

4.3.2.4 ‘numbers.Number’
........................

These are created by numeric literals and returned as results by
arithmetic operators and arithmetic built-in functions.  Numeric objects
are immutable; once created their value never changes.  Python numbers
are of course strongly related to mathematical numbers, but subject to
the limitations of numerical representation in computers.

The string representations of the numeric classes, computed by *note
__repr__(): 5c2. and *note __str__(): 5c4, have the following
properties:

   * They are valid numeric literals which, when passed to their class
     constructor, produce an object having the value of the original
     numeric.

   * The representation is in base 10, when possible.

   * Leading zeros, possibly excepting a single zero before a decimal
     point, are not shown.

   * Trailing zeros, possibly excepting a single zero after a decimal
     point, are not shown.

   * A sign is shown only when the number is negative.

Python distinguishes between integers, floating-point numbers, and
complex numbers:

* Menu:

* numbers.Integral: numbers Integral.
* numbers.Real (float): numbers Real float.
* numbers.Complex (complex): numbers Complex complex.


File: python.info,  Node: numbers Integral,  Next: numbers Real float,  Up: numbers Number

4.3.2.5 ‘numbers.Integral’
..........................

These represent elements from the mathematical set of integers (positive
and negative).

     備註: 
     The rules for integer representation are intended to give the most
     meaningful interpretation of shift and mask operations involving
     negative integers.

There are two types of integers:

Integers (*note int: 23c.)

     These represent numbers in an unlimited range, subject to available
     (virtual) memory only.  For the purpose of shift and mask
     operations, a binary representation is assumed, and negative
     numbers are represented in a variant of 2's complement which gives
     the illusion of an infinite string of sign bits extending to the
     left.

Booleans (*note bool: 40e.)

     These represent the truth values False and True.  The two objects
     representing the values ‘False’ and ‘True’ are the only Boolean
     objects.  The Boolean type is a subtype of the integer type, and
     Boolean values behave like the values 0 and 1, respectively, in
     almost all contexts, the exception being that when converted to a
     string, the strings ‘"False"’ or ‘"True"’ are returned,
     respectively.


File: python.info,  Node: numbers Real float,  Next: numbers Complex complex,  Prev: numbers Integral,  Up: numbers Number

4.3.2.6 ‘numbers.Real’ (‘float’)
................................

These represent machine-level double precision floating-point numbers.
You are at the mercy of the underlying machine architecture (and C or
Java implementation) for the accepted range and handling of overflow.
Python does not support single-precision floating-point numbers; the
savings in processor and memory usage that are usually the reason for
using these are dwarfed by the overhead of using objects in Python, so
there is no reason to complicate the language with two kinds of
floating-point numbers.


File: python.info,  Node: numbers Complex complex,  Prev: numbers Real float,  Up: numbers Number

4.3.2.7 ‘numbers.Complex’ (‘complex’)
.....................................

These represent complex numbers as a pair of machine-level double
precision floating-point numbers.  The same caveats apply as for
floating-point numbers.  The real and imaginary parts of a complex
number ‘z’ can be retrieved through the read-only attributes ‘z.real’
and ‘z.imag’.


File: python.info,  Node: Sequences,  Next: Set types,  Prev: numbers Number,  Up: 標準型別階層

4.3.2.8 Sequences
.................

These represent finite ordered sets indexed by non-negative numbers.
The built-in function *note len(): 5d4. returns the number of items of a
sequence.  When the length of a sequence is 'n', the index set contains
the numbers 0, 1, ..., 'n'-1.  Item 'i' of sequence 'a' is selected by
‘a[i]’.  Some sequences, including built-in sequences, interpret
negative subscripts by adding the sequence length.  For example, ‘a[-2]’
equals ‘a[n-2]’, the second to last item of sequence a with length ‘n’.

Sequences also support slicing: ‘a[i:j]’ selects all items with index
'k' such that 'i' ‘<=’ 'k' ‘<’ 'j'.  When used as an expression, a slice
is a sequence of the same type.  The comment above about negative
indexes also applies to negative slice positions.

Some sequences also support "extended slicing" with a third "step"
parameter: ‘a[i:j:k]’ selects all items of 'a' with index 'x' where ‘x =
i + n*k’, 'n' ‘>=’ ‘0’ and 'i' ‘<=’ 'x' ‘<’ 'j'.

Sequences are distinguished according to their mutability:

* Menu:

* Immutable sequences::
* Mutable sequences::


File: python.info,  Node: Immutable sequences,  Next: Mutable sequences,  Up: Sequences

4.3.2.9 Immutable sequences
...........................

An object of an immutable sequence type cannot change once it is
created.  (If the object contains references to other objects, these
other objects may be mutable and may be changed; however, the collection
of objects directly referenced by an immutable object cannot change.)

The following types are immutable sequences:

字串 (String)

     A string is a sequence of values that represent Unicode code
     points.  All the code points in the range ‘U+0000 - U+10FFFF’ can
     be represented in a string.  Python doesn't have a char type;
     instead, every code point in the string is represented as a string
     object with length ‘1’.  The built-in function *note ord(): 1de1.
     converts a code point from its string form to an integer in the
     range ‘0 - 10FFFF’; *note chr(): 1568. converts an integer in the
     range ‘0 - 10FFFF’ to the corresponding length ‘1’ string object.
     *note str.encode(): 87a. can be used to convert a *note str: 3f2.
     to *note bytes: 1a5. using the given text encoding, and *note
     bytes.decode(): 87b. can be used to achieve the opposite.

Tuples

     The items of a tuple are arbitrary Python objects.  Tuples of two
     or more items are formed by comma-separated lists of expressions.
     A tuple of one item (a 'singleton') can be formed by affixing a
     comma to an expression (an expression by itself does not create a
     tuple, since parentheses must be usable for grouping of
     expressions).  An empty tuple can be formed by an empty pair of
     parentheses.

Bytes

     A bytes object is an immutable array.  The items are 8-bit bytes,
     represented by integers in the range 0 <= x < 256.  Bytes literals
     (like ‘b'abc'’) and the built-in *note bytes(): 1a5. constructor
     can be used to create bytes objects.  Also, bytes objects can be
     decoded to strings via the *note decode(): 87b. method.


File: python.info,  Node: Mutable sequences,  Prev: Immutable sequences,  Up: Sequences

4.3.2.10 Mutable sequences
..........................

Mutable sequences can be changed after they are created.  The
subscription and slicing notations can be used as the target of
assignment and *note del: 16a9. (delete) statements.

     備註: 
     The *note collections: 16. and *note array: 6. module provide
     additional examples of mutable sequence types.

There are currently two intrinsic mutable sequence types:

List（串列）

     The items of a list are arbitrary Python objects.  Lists are formed
     by placing a comma-separated list of expressions in square
     brackets.  (Note that there are no special cases needed to form
     lists of length 0 or 1.)

Byte Arrays

     A bytearray object is a mutable array.  They are created by the
     built-in *note bytearray(): 4e3. constructor.  Aside from being
     mutable (and hence unhashable), byte arrays otherwise provide the
     same interface and functionality as immutable *note bytes: 1a5.
     objects.


File: python.info,  Node: Set types,  Next: Mappings,  Prev: Sequences,  Up: 標準型別階層

4.3.2.11 Set types
..................

These represent unordered, finite sets of unique, immutable objects.  As
such, they cannot be indexed by any subscript.  However, they can be
iterated over, and the built-in function *note len(): 5d4. returns the
number of items in a set.  Common uses for sets are fast membership
testing, removing duplicates from a sequence, and computing mathematical
operations such as intersection, union, difference, and symmetric
difference.

For set elements, the same immutability rules apply as for dictionary
keys.  Note that numeric types obey the normal rules for numeric
comparison: if two numbers compare equal (e.g., ‘1’ and ‘1.0’), only one
of them can be contained in a set.

There are currently two intrinsic set types:

Sets

     These represent a mutable set.  They are created by the built-in
     *note set(): 57d. constructor and can be modified afterwards by
     several methods, such as ‘add()’.

Frozen sets

     These represent an immutable set.  They are created by the built-in
     *note frozenset(): 57e. constructor.  As a frozenset is immutable
     and *note hashable: 5b5, it can be used again as an element of
     another set, or as a dictionary key.


File: python.info,  Node: Mappings,  Next: Callable types,  Prev: Set types,  Up: 標準型別階層

4.3.2.12 Mappings
.................

These represent finite sets of objects indexed by arbitrary index sets.
The subscript notation ‘a[k]’ selects the item indexed by ‘k’ from the
mapping ‘a’; this can be used in expressions and as the target of
assignments or *note del: 16a9. statements.  The built-in function *note
len(): 5d4. returns the number of items in a mapping.

There is currently a single intrinsic mapping type:

* Menu:

* 字典::


File: python.info,  Node: 字典,  Up: Mappings

4.3.2.13 字典
.............

These represent finite sets of objects indexed by nearly arbitrary
values.  The only types of values not acceptable as keys are values
containing lists or dictionaries or other mutable types that are
compared by value rather than by object identity, the reason being that
the efficient implementation of dictionaries requires a key's hash value
to remain constant.  Numeric types used for keys obey the normal rules
for numeric comparison: if two numbers compare equal (e.g., ‘1’ and
‘1.0’) then they can be used interchangeably to index the same
dictionary entry.

Dictionaries preserve insertion order, meaning that keys will be
produced in the same order they were added sequentially over the
dictionary.  Replacing an existing key does not change the order,
however removing a key and re-inserting it will add it to the end
instead of keeping its old place.

Dictionaries are mutable; they can be created by the ‘{}’ notation (see
section *note Dictionary displays: d25.).

The extension modules *note dbm.ndbm: 2c. and *note dbm.gnu: 2b. provide
additional examples of mapping types, as does the *note collections: 16.
module.

在 3.7 版的變更: Dictionaries did not preserve insertion order in
versions of Python before 3.6.  In CPython 3.6, insertion order was
preserved, but it was considered an implementation detail at that time
rather than a language guarantee.


File: python.info,  Node: Callable types,  Next: 模組<2>,  Prev: Mappings,  Up: 標準型別階層

4.3.2.14 Callable types
.......................

These are the types to which the function call operation (see section
*note Calls: d23.) can be applied:

* Menu:

* 自訂函式::
* Instance methods::
* Generator functions::
* Coroutine functions::
* Asynchronous generator functions::
* Built-in functions::
* Built-in methods::
* Classes::
* Class Instances::


File: python.info,  Node: 自訂函式,  Next: Instance methods,  Up: Callable types

4.3.2.15 自訂函式
.................

A user-defined function object is created by a function definition (see
section *note 函式定義: 1b3a.).  It should be called with an argument
list containing the same number of items as the function's formal
parameter list.

* Menu:

* 特殊唯讀屬性::
* 特殊可寫屬性::


File: python.info,  Node: 特殊唯讀屬性,  Next: 特殊可寫屬性,  Up: 自訂函式

4.3.2.16 特殊唯讀屬性
.....................

屬性                                                   含義
                                                       
--------------------------------------------------------------------------------------------------------------
                                                       
 -- 屬性: function.__globals__                         A reference to the *note dictionary: 23b. that holds
                                                       the function's *note global variables: 1de9. - the
                                                       global namespace of the module in which the function
                                                       was defined.
                                                       
                                                       
 -- 屬性: function.__closure__                         ‘None’ or a *note tuple: 322. of cells that contain
                                                       bindings for the function's free variables.
                                                       
                                                       A cell object has the attribute ‘cell_contents’.
                                                       This can be used to get the value of the cell, as
                                                       well as set the value.
                                                       


File: python.info,  Node: 特殊可寫屬性,  Prev: 特殊唯讀屬性,  Up: 自訂函式

4.3.2.17 特殊可寫屬性
.....................

Most of these attributes check the type of the assigned value:

屬性                                                   含義
                                                       
--------------------------------------------------------------------------------------------------------------
                                                       
 -- 屬性: function.__doc__                             The function's documentation string, or ‘None’ if
                                                       unavailable.  Not inherited by subclasses.
                                                       
                                                       
 -- 屬性: function.__name__                            The function's name.  See also:
                                                       *note __name__ attributes: 1416.
                                                       
                                                       
 -- 屬性: function.__qualname__                        The function's *note qualified name: 1843.  See
                                                       also: *note __qualname__ attributes: 1dec.
                                                       
                                                       在 3.3 版被加入.
                                                       
                                                       
 -- 屬性: function.__module__                          The name of the module the function was defined in,
                                                       or ‘None’ if unavailable.
                                                       
                                                       
 -- 屬性: function.__defaults__                        A *note tuple: 322. containing default
                                                       *note parameter: 1dee. values for those parameters
                                                       that have defaults, or ‘None’ if no parameters have
                                                       a default value.
                                                       
                                                       
 -- 屬性: function.__code__                            代表編譯函式主體的*note 程式碼物件: 1b6.。
                                                       
                                                       
 -- 屬性: function.__dict__                            The namespace supporting arbitrary function
                                                       attributes.  See also:
                                                       *note __dict__ attributes: c04.
                                                       
                                                       
 -- 屬性: function.__annotations__                     A *note dictionary: 23b. containing annotations of
                                                       *note parameters: 1dee.  The keys of the dictionary
                                                       are the parameter names, and ‘'return'’ for the
                                                       return annotation, if provided.  See also:
                                                       *note 註釋 (annotation) 最佳實踐: 77d.
                                                       
                                                       
 -- 屬性: function.__kwdefaults__                      A *note dictionary: 23b. containing defaults for
                                                       keyword-only *note parameters: 1dee.
                                                       
                                                       
 -- 屬性: function.__type_params__                     A *note tuple: 322. containing the
                                                       *note type parameters: 294. of a
                                                       *note generic function: 3f9.
                                                       
                                                       在 3.12 版被加入.
                                                       

Function objects also support getting and setting arbitrary attributes,
which can be used, for example, to attach metadata to functions.
Regular attribute dot-notation is used to get and set such attributes.

'CPython 實作細節：' CPython's current implementation only supports
function attributes on user-defined functions.  Function attributes on
*note built-in functions: 1df0. may be supported in the future.

Additional information about a function's definition can be retrieved
from its *note code object: 1b6. (accessible via the *note __code__:
296. attribute).


File: python.info,  Node: Instance methods,  Next: Generator functions,  Prev: 自訂函式,  Up: Callable types

4.3.2.18 Instance methods
.........................

An instance method object combines a class, a class instance and any
callable object (normally a user-defined function).

特殊唯讀屬性：

 -- 屬性: method.__self__                              Refers to the class instance object to which the
                                                       method is *note bound: 1df2.
                                                       
                                                       
 -- 屬性: method.__func__                              Refers to the original *note function object: 295.
                                                       
                                                       
 -- 屬性: method.__doc__                               The method's documentation (same as
                                                       *note method.__func__.__doc__: 1171.).  A
                                                       *note string: 3f2. if the original function had a
                                                       docstring, else ‘None’.
                                                       
                                                       
 -- 屬性: method.__name__                              The name of the method (same as
                                                       *note method.__func__.__name__: 1267.)
                                                       
                                                       
 -- 屬性: method.__module__                            The name of the module the method was defined in, or
                                                       ‘None’ if unavailable.
                                                       

Methods also support accessing (but not setting) the arbitrary function
attributes on the underlying *note function object: 295.

User-defined method objects may be created when getting an attribute of
a class (perhaps via an instance of that class), if that attribute is a
user-defined *note function object: 295. or a *note classmethod: 14a.
object.  When an instance method object is created by retrieving a
user-defined *note function object: 295. from a class via one of its
instances, its *note __self__: 1336. attribute is the instance, and the
method object is said to be 'bound'.  The new method's *note __func__:
128f. attribute is the original function object.

When an instance method object is created by retrieving a *note
classmethod: 14a. object from a class or instance, its *note __self__:
1336. attribute is the class itself, and its *note __func__: 128f.
attribute is the function object underlying the class method.

When an instance method object is called, the underlying function (*note
__func__: 128f.) is called, inserting the class instance (*note
__self__: 1336.) in front of the argument list.  For instance, when ‘C’
is a class which contains a definition for a function ‘f()’, and ‘x’ is
an instance of ‘C’, calling ‘x.f(1)’ is equivalent to calling ‘C.f(x,
1)’.

When an instance method object is derived from a *note classmethod: 14a.
object, the "class instance" stored in *note __self__: 1336. will
actually be the class itself, so that calling either ‘x.f(1)’ or
‘C.f(1)’ is equivalent to calling ‘f(C,1)’ where ‘f’ is the underlying
function.

It is important to note that user-defined functions which are attributes
of a class instance are not converted to bound methods; this 'only'
happens when the function is an attribute of the class.


File: python.info,  Node: Generator functions,  Next: Coroutine functions,  Prev: Instance methods,  Up: Callable types

4.3.2.19 Generator functions
............................

A function or method which uses the *note yield: 971. statement (see
section *note yield 陳述式: 971.) is called a 'generator function'.
Such a function, when called, always returns an *note iterator: 192.
object which can be used to execute the body of the function: calling
the iterator's *note iterator.__next__(): 1260. method will cause the
function to execute until it provides a value using the ‘yield’
statement.  When the function executes a *note return: 972. statement or
falls off the end, a *note StopIteration: ba1. exception is raised and
the iterator will have reached the end of the set of values to be
returned.


File: python.info,  Node: Coroutine functions,  Next: Asynchronous generator functions,  Prev: Generator functions,  Up: Callable types

4.3.2.20 Coroutine functions
............................

A function or method which is defined using *note async def: 575. is
called a 'coroutine function'.  Such a function, when called, returns a
*note coroutine: 438. object.  It may contain *note await: 19f.
expressions, as well as *note async with: 57a. and *note async for: a4e.
statements.  See also the *note Coroutine Objects: 1df8. section.


File: python.info,  Node: Asynchronous generator functions,  Next: Built-in functions,  Prev: Coroutine functions,  Up: Callable types

4.3.2.21 Asynchronous generator functions
.........................................

A function or method which is defined using *note async def: 575. and
which uses the *note yield: 971. statement is called a 'asynchronous
generator function'.  Such a function, when called, returns an *note
asynchronous iterator: 191. object which can be used in an *note async
for: a4e. statement to execute the body of the function.

Calling the asynchronous iterator's *note aiterator.__anext__: 1dfa.
method will return an *note awaitable: 193. which when awaited will
execute until it provides a value using the *note yield: 971.
expression.  When the function executes an empty *note return: 972.
statement or falls off the end, a *note StopAsyncIteration: 1933.
exception is raised and the asynchronous iterator will have reached the
end of the set of values to be yielded.


File: python.info,  Node: Built-in functions,  Next: Built-in methods,  Prev: Asynchronous generator functions,  Up: Callable types

4.3.2.22 Built-in functions
...........................

A built-in function object is a wrapper around a C function.  Examples
of built-in functions are *note len(): 5d4. and *note math.sin(): 1429.
(*note math: 81. is a standard built-in module).  The number and type of
the arguments are determined by the C function.  Special read-only
attributes:

   * ‘__doc__’ 是函式的文件字串，若不可用則為 ‘None’。請見 *note
     function.__doc__: 1171.。

   * ‘__name__’ 是函式的名稱。請見 *note function.__name__: 1267.。

   * ‘__self__’ is set to ‘None’ (but see the next item).

   * ‘__module__’ is the name of the module the function was defined in
     or ‘None’ if unavailable.  See *note function.__module__: 1ded.


File: python.info,  Node: Built-in methods,  Next: Classes,  Prev: Built-in functions,  Up: Callable types

4.3.2.23 Built-in methods
.........................

This is really a different disguise of a built-in function, this time
containing an object passed to the C function as an implicit extra
argument.  An example of a built-in method is ‘alist.append()’, assuming
'alist' is a list object.  In this case, the special read-only attribute
‘__self__’ is set to the object denoted by 'alist'.  (The attribute has
the same semantics as it does with *note other instance methods: 1336.)


File: python.info,  Node: Classes,  Next: Class Instances,  Prev: Built-in methods,  Up: Callable types

4.3.2.24 Classes
................

Classes are callable.  These objects normally act as factories for new
instances of themselves, but variations are possible for class types
that override *note __new__(): 526.  The arguments of the call are
passed to ‘__new__()’ and, in the typical case, to *note __init__():
655. to initialize the new instance.


File: python.info,  Node: Class Instances,  Prev: Classes,  Up: Callable types

4.3.2.25 Class Instances
........................

Instances of arbitrary classes can be made callable by defining a *note
__call__(): 4fe. method in their class.


File: python.info,  Node: 模組<2>,  Next: Custom classes,  Prev: Callable types,  Up: 標準型別階層

4.3.2.26 模組
.............

Modules are a basic organizational unit of Python code, and are created
by the *note import system: 1e01. as invoked either by the *note import:
586. statement, or by calling functions such as *note
importlib.import_module(): 4bc. and built-in *note __import__(): 879.  A
module object has a namespace implemented by a *note dictionary: 23b.
object (this is the dictionary referenced by the *note __globals__:
1266. attribute of functions defined in the module).  Attribute
references are translated to lookups in this dictionary, e.g., ‘m.x’ is
equivalent to ‘m.__dict__["x"]’.  A module object does not contain the
code object used to initialize the module (since it isn't needed once
the initialization is done).

Attribute assignment updates the module's namespace dictionary, e.g.,
‘m.x = 1’ is equivalent to ‘m.__dict__["x"] = 1’.

Predefined (writable) attributes:

     *note __name__: 1316.

          The module's name.

     ‘__doc__’

          The module's documentation string, or ‘None’ if unavailable.

     *note __file__: 1e02.

          The pathname of the file from which the module was loaded, if
          it was loaded from a file.  The *note __file__: 1e02.
          attribute may be missing for certain types of modules, such as
          C modules that are statically linked into the interpreter.
          For extension modules loaded dynamically from a shared
          library, it's the pathname of the shared library file.

     ‘__annotations__’

          A dictionary containing *note variable annotations: cfc.
          collected during module body execution.  For best practices on
          working with ‘__annotations__’, please see *note 註釋
          (annotation) 最佳實踐: 77d.

Special read-only attribute: *note __dict__: c04. is the module's
namespace as a dictionary object.

'CPython 實作細節：' Because of the way CPython clears module
dictionaries, the module dictionary will be cleared when the module
falls out of scope even if the dictionary still has live references.  To
avoid this, copy the dictionary or keep the module around while using
its dictionary directly.


File: python.info,  Node: Custom classes,  Next: Class instances,  Prev: 模組<2>,  Up: 標準型別階層

4.3.2.27 Custom classes
.......................

Custom class types are typically created by class definitions (see
section *note 類別定義: 126a.).  A class has a namespace implemented by
a dictionary object.  Class attribute references are translated to
lookups in this dictionary, e.g., ‘C.x’ is translated to
‘C.__dict__["x"]’ (although there are a number of hooks which allow for
other means of locating attributes).  When the attribute name is not
found there, the attribute search continues in the base classes.  This
search of the base classes uses the C3 method resolution order which
behaves correctly even in the presence of 'diamond' inheritance
structures where there are multiple inheritance paths leading back to a
common ancestor.  Additional details on the C3 MRO used by Python can be
found at *note The Python 2.3 Method Resolution Order: 1415.

When a class attribute reference (for class ‘C’, say) would yield a
class method object, it is transformed into an instance method object
whose *note __self__: 1336. attribute is ‘C’.  When it would yield a
*note staticmethod: 358. object, it is transformed into the object
wrapped by the static method object.  See section *note Implementing
Descriptors: bf6. for another way in which attributes retrieved from a
class may differ from those actually contained in its *note __dict__:
c04.

Class attribute assignments update the class's dictionary, never the
dictionary of a base class.

A class object can be called (see above) to yield a class instance (see
below).

Special attributes:

     *note __name__: 1416.

          The class name.

     ‘__module__’

          The name of the module in which the class was defined.

     *note __dict__: c04.

          The dictionary containing the class's namespace.

     *note __bases__: 1417.

          A tuple containing the base classes, in the order of their
          occurrence in the base class list.

     ‘__doc__’

          The class's documentation string, or ‘None’ if undefined.

     ‘__annotations__’

          A dictionary containing *note variable annotations: cfc.
          collected during class body execution.  For best practices on
          working with ‘__annotations__’, please see *note 註釋
          (annotation) 最佳實踐: 77d.

     ‘__type_params__’

          A tuple containing the *note type parameters: 294. of a *note
          generic class: 3f8.

     *note __static_attributes__: 131.

          A tuple containing names of attributes of this class which are
          assigned through ‘self.X’ from any function in its body.

     ‘__firstlineno__’

          The line number of the first line of the class definition,
          including decorators.


File: python.info,  Node: Class instances,  Next: I/O objects also known as file objects,  Prev: Custom classes,  Up: 標準型別階層

4.3.2.28 Class instances
........................

A class instance is created by calling a class object (see above).  A
class instance has a namespace implemented as a dictionary which is the
first place in which attribute references are searched.  When an
attribute is not found there, and the instance's class has an attribute
by that name, the search continues with the class attributes.  If a
class attribute is found that is a user-defined function object, it is
transformed into an instance method object whose *note __self__: 1336.
attribute is the instance.  Static method and class method objects are
also transformed; see above under "Classes".  See section *note
Implementing Descriptors: bf6. for another way in which attributes of a
class retrieved via its instances may differ from the objects actually
stored in the class's *note __dict__: c04.  If no class attribute is
found, and the object's class has a *note __getattr__(): 47a. method,
that is called to satisfy the lookup.

Attribute assignments and deletions update the instance's dictionary,
never a class's dictionary.  If the class has a *note __setattr__():
1e05. or *note __delattr__(): 1e06. method, this is called instead of
updating the instance dictionary directly.

Class instances can pretend to be numbers, sequences, or mappings if
they have methods with certain special names.  See section *note Special
method names: c15.

Special attributes: *note __dict__: c04. is the attribute dictionary;
*note __class__: 1418. is the instance's class.


File: python.info,  Node: I/O objects also known as file objects,  Next: Internal types,  Prev: Class instances,  Up: 標準型別階層

4.3.2.29 I/O objects (also known as file objects)
.................................................

A *note file object: 115b. represents an open file.  Various shortcuts
are available to create file objects: the *note open(): 4c0. built-in
function, and also *note os.popen(): a2a, *note os.fdopen(): 1e08, and
the *note makefile(): 1137. method of socket objects (and perhaps by
other functions or methods provided by extension modules).

The objects ‘sys.stdin’, ‘sys.stdout’ and ‘sys.stderr’ are initialized
to file objects corresponding to the interpreter's standard input,
output and error streams; they are all open in text mode and therefore
follow the interface defined by the *note io.TextIOBase: 63b. abstract
class.


File: python.info,  Node: Internal types,  Prev: I/O objects also known as file objects,  Up: 標準型別階層

4.3.2.30 Internal types
.......................

A few types used internally by the interpreter are exposed to the user.
Their definitions may change with future versions of the interpreter,
but they are mentioned here for completeness.

* Menu:

* Code objects::
* Frame objects::
* Traceback objects::
* Slice objects::
* Static method objects::
* Class method objects::


File: python.info,  Node: Code objects,  Next: Frame objects,  Up: Internal types

4.3.2.31 Code objects
.....................

Code objects represent 'byte-compiled' executable Python code, or *note
bytecode: 16d.  The difference between a code object and a function
object is that the function object contains an explicit reference to the
function's globals (the module in which it was defined), while a code
object contains no context; also the default argument values are stored
in the function object, not in the code object (because they represent
values calculated at run-time).  Unlike function objects, code objects
are immutable and contain no references (directly or indirectly) to
mutable objects.

* Menu:

* 特殊唯讀屬性: 特殊唯讀屬性<2>.
* 用於程式碼物件的方法::


File: python.info,  Node: 特殊唯讀屬性<2>,  Next: 用於程式碼物件的方法,  Up: Code objects

4.3.2.32 特殊唯讀屬性
.....................

 -- 屬性: codeobject.co_name                           函式名稱
                                                       
                                                       
 -- 屬性: codeobject.co_qualname                       The fully qualified function name
                                                       
                                                       在 3.11 版被加入.
                                                       
                                                       
 -- 屬性: codeobject.co_argcount                       The total number of positional
                                                       *note parameters: 1dee. (including positional-only
                                                       parameters and parameters with default values) that
                                                       the function has
                                                       
                                                       
 -- 屬性: codeobject.co_posonlyargcount                The number of positional-only
                                                       *note parameters: 1dee. (including arguments with
                                                       default values) that the function has
                                                       
                                                       
 -- 屬性: codeobject.co_kwonlyargcount                 The number of keyword-only *note parameters: 1dee.
                                                       (including arguments with default values) that the
                                                       function has
                                                       
                                                       
 -- 屬性: codeobject.co_nlocals                        The number of *note local variables: 1de9. used by
                                                       the function (including parameters)
                                                       
                                                       
 -- 屬性: codeobject.co_varnames                       A *note tuple: 322. containing the names of the
                                                       local variables in the function (starting with the
                                                       parameter names)
                                                       
                                                       
 -- 屬性: codeobject.co_cellvars                       A *note tuple: 322. containing the names of
                                                       *note local variables: 1de9. that are referenced by
                                                       nested functions inside the function
                                                       
                                                       
 -- 屬性: codeobject.co_freevars                       A *note tuple: 322. containing the names of free
                                                       variables in the function
                                                       
                                                       
 -- 屬性: codeobject.co_code                           A string representing the sequence of
                                                       *note bytecode: 16d. instructions in the function
                                                       
                                                       
 -- 屬性: codeobject.co_consts                         A *note tuple: 322. containing the literals used by
                                                       the *note bytecode: 16d. in the function
                                                       
                                                       
 -- 屬性: codeobject.co_names                          A *note tuple: 322. containing the names used by the
                                                       *note bytecode: 16d. in the function
                                                       
                                                       
 -- 屬性: codeobject.co_filename                       The name of the file from which the code was
                                                       compiled
                                                       
                                                       
 -- 屬性: codeobject.co_firstlineno                    The line number of the first line of the function
                                                       
                                                       
 -- 屬性: codeobject.co_lnotab                         A string encoding the mapping from
                                                       *note bytecode: 16d. offsets to line numbers.  For
                                                       details, see the source code of the interpreter.
                                                       
                                                       在 3.12 版之後被棄用: This attribute of code objects
                                                       is deprecated, and may be removed in Python 3.14.
                                                       
                                                       
 -- 屬性: codeobject.co_stacksize                      The required stack size of the code object
                                                       
                                                       
 -- 屬性: codeobject.co_flags                          An *note integer: 23c. encoding a number of flags
                                                       for the interpreter.
                                                       

The following flag bits are defined for *note co_flags: 1e1a.: bit
‘0x04’ is set if the function uses the ‘*arguments’ syntax to accept an
arbitrary number of positional arguments; bit ‘0x08’ is set if the
function uses the ‘**keywords’ syntax to accept arbitrary keyword
arguments; bit ‘0x20’ is set if the function is a generator.  See *note
Code Objects Bit Flags: 1e1b. for details on the semantics of each flags
that might be present.

Future feature declarations (‘from __future__ import division’) also use
bits in *note co_flags: 1e1a. to indicate whether a code object was
compiled with a particular feature enabled: bit ‘0x2000’ is set if the
function was compiled with future division enabled; bits ‘0x10’ and
‘0x1000’ were used in earlier versions of Python.

Other bits in *note co_flags: 1e1a. are reserved for internal use.

If a code object represents a function, the first item in *note
co_consts: 1e16. is the documentation string of the function, or ‘None’
if undefined.


File: python.info,  Node: 用於程式碼物件的方法,  Prev: 特殊唯讀屬性<2>,  Up: Code objects

4.3.2.33 用於程式碼物件的方法
.............................

 -- 方法: codeobject.co_positions ()

     Returns an iterable over the source code positions of each *note
     bytecode: 16d. instruction in the code object.

     The iterator returns *note tuple: 322.s containing the
     ‘(start_line, end_line, start_column, end_column)’.  The 'i-th'
     tuple corresponds to the position of the source code that compiled
     to the 'i-th' code unit.  Column information is 0-indexed utf-8
     byte offsets on the given source line.

     This positional information can be missing.  A non-exhaustive lists
     of cases where this may happen:

        - Running the interpreter with *note -X: 15a. ‘no_debug_ranges’.

        - Loading a pyc file compiled while using *note -X: 15a.
          ‘no_debug_ranges’.

        - Position tuples corresponding to artificial instructions.

        - Line and column numbers that can't be represented due to
          implementation specific limitations.

     When this occurs, some or all of the tuple elements can be *note
     None: 61b.

     在 3.11 版被加入.

          備註: This feature requires storing column positions in code
          objects which may result in a small increase of disk usage of
          compiled Python files or interpreter memory usage.  To avoid
          storing the extra information and/or deactivate printing the
          extra traceback information, the *note -X: 15a.
          ‘no_debug_ranges’ command line flag or the *note
          PYTHONNODEBUGRANGES: 55a. environment variable can be used.

 -- 方法: codeobject.co_lines ()

     Returns an iterator that yields information about successive ranges
     of *note bytecode: 16d.s.  Each item yielded is a ‘(start, end,
     lineno)’ *note tuple: 322.:

        * ‘start’ (an *note int: 23c.) represents the offset (inclusive)
          of the start of the *note bytecode: 16d. range

        * ‘end’ (an *note int: 23c.) represents the offset (exclusive)
          of the end of the *note bytecode: 16d. range

        * ‘lineno’ is an *note int: 23c. representing the line number of
          the *note bytecode: 16d. range, or ‘None’ if the bytecodes in
          the given range have no line number

     The items yielded will have the following properties:

        * The first range yielded will have a ‘start’ of 0.

        * The ‘(start, end)’ ranges will be non-decreasing and
          consecutive.  That is, for any pair of *note tuple: 322.s, the
          ‘start’ of the second will be equal to the ‘end’ of the first.

        * No range will be backwards: ‘end >= start’ for all triples.

        * The last *note tuple: 322. yielded will have ‘end’ equal to
          the size of the *note bytecode: 16d.

     Zero-width ranges, where ‘start == end’, are allowed.  Zero-width
     ranges are used for lines that are present in the source code, but
     have been eliminated by the *note bytecode: 16d. compiler.

     在 3.10 版被加入.

     也參考
     ......

     PEP 626(1) - Precise line numbers for debugging and other tools.

          The PEP that introduced the ‘co_lines()’ method.

 -- 方法: codeobject.replace (**kwargs)

     Return a copy of the code object with new values for the specified
     fields.

     Code objects are also supported by the generic function *note
     copy.replace(): 136.

     在 3.8 版被加入.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0626/


File: python.info,  Node: Frame objects,  Next: Traceback objects,  Prev: Code objects,  Up: Internal types

4.3.2.34 Frame objects
......................

Frame objects represent execution frames.  They may occur in *note
traceback objects: a97, and are also passed to registered trace
functions.

* Menu:

* 特殊唯讀屬性: 特殊唯讀屬性<3>.
* 特殊可寫屬性: 特殊可寫屬性<2>.
* Frame object methods::


File: python.info,  Node: 特殊唯讀屬性<3>,  Next: 特殊可寫屬性<2>,  Up: Frame objects

4.3.2.35 特殊唯讀屬性
.....................

 -- 屬性: frame.f_back                                 Points to the previous stack frame (towards the
                                                       caller), or ‘None’ if this is the bottom stack frame
                                                       
                                                       
 -- 屬性: frame.f_code                                 在這個 frame 中執行的
                                                       *note 程式碼物件 (code object): 1b6.。存取這個屬性會
                                                       引發一個附帶引數 ‘obj’ 與 ‘"f_code"’ 的
                                                       *note 稽核事件: 17bd. ‘object.__getattr__’。
                                                       
                                                       
 -- 屬性: frame.f_locals                               The mapping used by the frame to look up
                                                       *note local variables: 1de9.  If the frame refers to
                                                       an *note optimized scope: 161, this may return a
                                                       write-through proxy object.
                                                       
                                                       在 3.13 版的變更: Return a proxy for optimized
                                                       scopes.
                                                       
                                                       
 -- 屬性: frame.f_globals                              The dictionary used by the frame to look up
                                                       *note global variables: 1de9.
                                                       
                                                       
 -- 屬性: frame.f_builtins                             The dictionary used by the frame to look up
                                                       *note built-in (intrinsic) names: 1de9.
                                                       
                                                       
 -- 屬性: frame.f_lasti                                The "precise instruction" of the frame object (this
                                                       is an index into the *note bytecode: 16d. string of
                                                       the *note code object: 1b6.)
                                                       


File: python.info,  Node: 特殊可寫屬性<2>,  Next: Frame object methods,  Prev: 特殊唯讀屬性<3>,  Up: Frame objects

4.3.2.36 特殊可寫屬性
.....................

 -- 屬性: frame.f_trace                                If not ‘None’, this is a function called for various
                                                       events during code execution (this is used by
                                                       debuggers).  Normally an event is triggered for each
                                                       new source line (see *note f_trace_lines: b82.).
                                                       
                                                       
 -- 屬性: frame.f_trace_lines                          Set this attribute to *note False: adb. to disable
                                                       triggering a tracing event for each source line.
                                                       
                                                       
 -- 屬性: frame.f_trace_opcodes                        Set this attribute to *note True: bb4. to allow
                                                       per-opcode events to be requested.  Note that this
                                                       may lead to undefined interpreter behaviour if
                                                       exceptions raised by the trace function escape to
                                                       the function being traced.
                                                       
                                                       
 -- 屬性: frame.f_lineno                               The current line number of the frame - writing to
                                                       this from within a trace function jumps to the given
                                                       line (only for the bottom-most frame).  A debugger
                                                       can implement a Jump command (aka Set Next
                                                       Statement) by writing to this attribute.
                                                       


File: python.info,  Node: Frame object methods,  Prev: 特殊可寫屬性<2>,  Up: Frame objects

4.3.2.37 Frame object methods
.............................

Frame objects support one method:

 -- 方法: frame.clear ()

     This method clears all references to *note local variables: 1de9.
     held by the frame.  Also, if the frame belonged to a *note
     generator: 1004, the generator is finalized.  This helps break
     reference cycles involving frame objects (for example when catching
     an *note exception: 1786. and storing its *note traceback: a97. for
     later use).

     *note RuntimeError: 179. is raised if the frame is currently
     executing or suspended.

     在 3.4 版被加入.

     在 3.13 版的變更: Attempting to clear a suspended frame raises
     *note RuntimeError: 179. (as has always been the case for executing
     frames).


File: python.info,  Node: Traceback objects,  Next: Slice objects,  Prev: Frame objects,  Up: Internal types

4.3.2.38 Traceback objects
..........................

Traceback objects represent the stack trace of an *note exception: 1b8e.
A traceback object is implicitly created when an exception occurs, and
may also be explicitly created by calling *note types.TracebackType:
a95.

在 3.7 版的變更: Traceback objects can now be explicitly instantiated
from Python code.

For implicitly created tracebacks, when the search for an exception
handler unwinds the execution stack, at each unwound level a traceback
object is inserted in front of the current traceback.  When an exception
handler is entered, the stack trace is made available to the program.
(See section *note The try statement: 68c.)  It is accessible as the
third item of the tuple returned by *note sys.exc_info(): 630, and as
the *note __traceback__: 125b. attribute of the caught exception.

When the program contains no suitable handler, the stack trace is
written (nicely formatted) to the standard error stream; if the
interpreter is interactive, it is also made available to the user as
*note sys.last_traceback: 468.

For explicitly created tracebacks, it is up to the creator of the
traceback to determine how the *note tb_next: a96. attributes should be
linked to form a full stack trace.

特殊唯讀屬性：

 -- 屬性: traceback.tb_frame                           Points to the execution *note frame: 27e. of the
                                                       current level.
                                                       
                                                       存取此屬性會引發一個附帶引數 ‘obj’ 與 ‘"tb_frame"’ 的
                                                       *note 稽核事件: 17bd. ‘object.__getattr__’。
                                                       
                                                       
 -- 屬性: traceback.tb_lineno                          Gives the line number where the exception occurred
                                                       
                                                       
 -- 屬性: traceback.tb_lasti                           Indicates the "precise instruction".
                                                       

The line number and last instruction in the traceback may differ from
the line number of its *note frame object: 27e. if the exception
occurred in a *note try: 68c. statement with no matching except clause
or with a *note finally: 96e. clause.

 -- 屬性: traceback.tb_next

     The special writable attribute ‘tb_next’ is the next level in the
     stack trace (towards the frame where the exception occurred), or
     ‘None’ if there is no next level.

     在 3.7 版的變更: This attribute is now writable


File: python.info,  Node: Slice objects,  Next: Static method objects,  Prev: Traceback objects,  Up: Internal types

4.3.2.39 Slice objects
......................

Slice objects are used to represent slices for *note __getitem__(): 266.
methods.  They are also created by the built-in *note slice(): 410.
function.

Special read-only attributes: *note start: 1e2b. is the lower bound;
*note stop: 1e2c. is the upper bound; *note step: 1e2d. is the step
value; each is ‘None’ if omitted.  These attributes can have any type.

Slice objects support one method:

 -- 方法: slice.indices (self, length)

     This method takes a single integer argument 'length' and computes
     information about the slice that the slice object would describe if
     applied to a sequence of 'length' items.  It returns a tuple of
     three integers; respectively these are the 'start' and 'stop'
     indices and the 'step' or stride length of the slice.  Missing or
     out-of-bounds indices are handled in a manner consistent with
     regular slices.


File: python.info,  Node: Static method objects,  Next: Class method objects,  Prev: Slice objects,  Up: Internal types

4.3.2.40 Static method objects
..............................

Static method objects provide a way of defeating the transformation of
function objects to method objects described above.  A static method
object is a wrapper around any other object, usually a user-defined
method object.  When a static method object is retrieved from a class or
a class instance, the object actually returned is the wrapped object,
which is not subject to any further transformation.  Static method
objects are also callable.  Static method objects are created by the
built-in *note staticmethod(): 358. constructor.


File: python.info,  Node: Class method objects,  Prev: Static method objects,  Up: Internal types

4.3.2.41 Class method objects
.............................

A class method object, like a static method object, is a wrapper around
another object that alters the way in which that object is retrieved
from classes and class instances.  The behaviour of class method objects
upon such retrieval is described above, under *note "instance methods":
1bc1.  Class method objects are created by the built-in *note
classmethod(): 14a. constructor.


File: python.info,  Node: Special method names,  Next: 協程,  Prev: 標準型別階層,  Up: 資料模型

4.3.3 Special method names
--------------------------

A class can implement certain operations that are invoked by special
syntax (such as arithmetic operations or subscripting and slicing) by
defining methods with special names.  This is Python's approach to
'operator overloading', allowing classes to define their own behavior
with respect to language operators.  For instance, if a class defines a
method named *note __getitem__(): 266, and ‘x’ is an instance of this
class, then ‘x[i]’ is roughly equivalent to ‘type(x).__getitem__(x, i)’.
Except where mentioned, attempts to execute an operation raise an
exception when no appropriate method is defined (typically *note
AttributeError: 2f6. or *note TypeError: 4dd.).

Setting a special method to ‘None’ indicates that the corresponding
operation is not available.  For example, if a class sets *note
__iter__(): 1e31. to ‘None’, the class is not iterable, so calling *note
iter(): 77b. on its instances will raise a *note TypeError: 4dd.
(without falling back to *note __getitem__(): 266.).  (1)

When implementing a class that emulates any built-in type, it is
important that the emulation only be implemented to the degree that it
makes sense for the object being modelled.  For example, some sequences
may work well with retrieval of individual elements, but extracting a
slice may not make sense.  (One example of this is the ‘NodeList’
interface in the W3C's Document Object Model.)

* Menu:

* Basic customization::
* Customizing attribute access::
* Customizing class creation::
* Customizing instance and subclass checks::
* Emulating generic types::
* Emulating callable objects::
* Emulating container types::
* Emulating numeric types::
* With Statement Context Managers::
* Customizing positional arguments in class pattern matching::
* Emulating buffer types::
* Special method lookup::

   ---------- Footnotes ----------

   (1) The *note __hash__(): a9e, *note __iter__(): 1e31, *note
__reversed__(): 1e32, *note __contains__(): 1e33, *note
__class_getitem__(): 6df. and *note __fspath__(): bf9. methods have
special handling for this.  Others will still raise a *note TypeError:
4dd, but may do so by relying on the behavior that ‘None’ is not
callable.


File: python.info,  Node: Basic customization,  Next: Customizing attribute access,  Up: Special method names

4.3.3.1 Basic customization
...........................

 -- 方法: object.__new__ (cls[, ...])

     Called to create a new instance of class 'cls'.  *note __new__():
     526. is a static method (special-cased so you need not declare it
     as such) that takes the class of which an instance was requested as
     its first argument.  The remaining arguments are those passed to
     the object constructor expression (the call to the class).  The
     return value of *note __new__(): 526. should be the new object
     instance (usually an instance of 'cls').

     Typical implementations create a new instance of the class by
     invoking the superclass's *note __new__(): 526. method using
     ‘super().__new__(cls[, ...])’ with appropriate arguments and then
     modifying the newly created instance as necessary before returning
     it.

     If *note __new__(): 526. is invoked during object construction and
     it returns an instance of 'cls', then the new instance’s *note
     __init__(): 655. method will be invoked like ‘__init__(self[,
     ...])’, where 'self' is the new instance and the remaining
     arguments are the same as were passed to the object constructor.

     If *note __new__(): 526. does not return an instance of 'cls', then
     the new instance's *note __init__(): 655. method will not be
     invoked.

     *note __new__(): 526. is intended mainly to allow subclasses of
     immutable types (like int, str, or tuple) to customize instance
     creation.  It is also commonly overridden in custom metaclasses in
     order to customize class creation.

 -- 方法: object.__init__ (self[, ...])

     Called after the instance has been created (by *note __new__():
     526.), but before it is returned to the caller.  The arguments are
     those passed to the class constructor expression.  If a base class
     has an *note __init__(): 655. method, the derived class's *note
     __init__(): 655. method, if any, must explicitly call it to ensure
     proper initialization of the base class part of the instance; for
     example: ‘super().__init__([args...])’.

     Because *note __new__(): 526. and *note __init__(): 655. work
     together in constructing objects (*note __new__(): 526. to create
     it, and *note __init__(): 655. to customize it), no non-‘None’
     value may be returned by *note __init__(): 655.; doing so will
     cause a *note TypeError: 4dd. to be raised at runtime.

 -- 方法: object.__del__ (self)

     Called when the instance is about to be destroyed.  This is also
     called a finalizer or (improperly) a destructor.  If a base class
     has a *note __del__(): 1e36. method, the derived class's *note
     __del__(): 1e36. method, if any, must explicitly call it to ensure
     proper deletion of the base class part of the instance.

     It is possible (though not recommended!)  for the *note __del__():
     1e36. method to postpone destruction of the instance by creating a
     new reference to it.  This is called object 'resurrection'.  It is
     implementation-dependent whether *note __del__(): 1e36. is called a
     second time when a resurrected object is about to be destroyed; the
     current *note CPython: 699. implementation only calls it once.

     It is not guaranteed that *note __del__(): 1e36. methods are called
     for objects that still exist when the interpreter exits.  *note
     weakref.finalize: a1f. provides a straightforward way to register a
     cleanup function to be called when an object is garbage collected.

          備註: ‘del x’ doesn't directly call ‘x.__del__()’ -- the
          former decrements the reference count for ‘x’ by one, and the
          latter is only called when ‘x’'s reference count reaches zero.

     'CPython 實作細節：' It is possible for a reference cycle to
     prevent the reference count of an object from going to zero.  In
     this case, the cycle will be later detected and deleted by the
     *note cyclic garbage collector: 181c.  A common cause of reference
     cycles is when an exception has been caught in a local variable.
     The frame's locals then reference the exception, which references
     its own traceback, which references the locals of all frames caught
     in the traceback.

     也參考
     ......

     Documentation for the *note gc: 56. module.

          警告: Due to the precarious circumstances under which *note
          __del__(): 1e36. methods are invoked, exceptions that occur
          during their execution are ignored, and a warning is printed
          to ‘sys.stderr’ instead.  In particular:

             * *note __del__(): 1e36. can be invoked when arbitrary code
               is being executed, including from any arbitrary thread.
               If *note __del__(): 1e36. needs to take a lock or invoke
               any other blocking resource, it may deadlock as the
               resource may already be taken by the code that gets
               interrupted to execute *note __del__(): 1e36.

             * *note __del__(): 1e36. can be executed during interpreter
               shutdown.  As a consequence, the global variables it
               needs to access (including other modules) may already
               have been deleted or set to ‘None’.  Python guarantees
               that globals whose name begins with a single underscore
               are deleted from their module before other globals are
               deleted; if no other references to such globals exist,
               this may help in assuring that imported modules are still
               available at the time when the *note __del__(): 1e36.
               method is called.

 -- 方法: object.__repr__ (self)

     Called by the *note repr(): 7a1. built-in function to compute the
     "official" string representation of an object.  If at all possible,
     this should look like a valid Python expression that could be used
     to recreate an object with the same value (given an appropriate
     environment).  If this is not possible, a string of the form
     ‘<...some useful description...>’ should be returned.  The return
     value must be a string object.  If a class defines *note
     __repr__(): 5c2. but not *note __str__(): 5c4, then *note
     __repr__(): 5c2. is also used when an "informal" string
     representation of instances of that class is required.

     This is typically used for debugging, so it is important that the
     representation is information-rich and unambiguous.

 -- 方法: object.__str__ (self)

     Called by *note str(object): 3f2. and the built-in functions *note
     format(): 5c3. and *note print(): f18. to compute the "informal" or
     nicely printable string representation of an object.  The return
     value must be a *note string: 1b03. object.

     This method differs from *note object.__repr__(): 5c2. in that
     there is no expectation that *note __str__(): 5c4. return a valid
     Python expression: a more convenient or concise representation can
     be used.

     The default implementation defined by the built-in type *note
     object: a2f. calls *note object.__repr__(): 5c2.

 -- 方法: object.__bytes__ (self)

     Called by *note bytes: 19bf. to compute a byte-string
     representation of an object.  This should return a *note bytes:
     1a5. object.

 -- 方法: object.__format__ (self, format_spec)

     Called by the *note format(): 5c3. built-in function, and by
     extension, evaluation of *note formatted string literals: 94d. and
     the *note str.format(): 5c7. method, to produce a "formatted"
     string representation of an object.  The 'format_spec' argument is
     a string that contains a description of the formatting options
     desired.  The interpretation of the 'format_spec' argument is up to
     the type implementing *note __format__(): 5c5, however most classes
     will either delegate formatting to one of the built-in types, or
     use a similar formatting option syntax.

     See *note 格式規格 (Format Specification) 迷你語言: 1c8. for a
     description of the standard formatting syntax.

     The return value must be a string object.

     在 3.4 版的變更: The __format__ method of ‘object’ itself raises a
     *note TypeError: 4dd. if passed any non-empty string.

     在 3.7 版的變更: ‘object.__format__(x, '')’ is now equivalent to
     ‘str(x)’ rather than ‘format(str(x), '')’.

 -- 方法: object.__lt__ (self, other)
 -- 方法: object.__le__ (self, other)
 -- 方法: object.__eq__ (self, other)
 -- 方法: object.__ne__ (self, other)
 -- 方法: object.__gt__ (self, other)
 -- 方法: object.__ge__ (self, other)

     These are the so-called "rich comparison" methods.  The
     correspondence between operator symbols and method names is as
     follows: ‘x<y’ calls ‘x.__lt__(y)’, ‘x<=y’ calls ‘x.__le__(y)’,
     ‘x==y’ calls ‘x.__eq__(y)’, ‘x!=y’ calls ‘x.__ne__(y)’, ‘x>y’ calls
     ‘x.__gt__(y)’, and ‘x>=y’ calls ‘x.__ge__(y)’.

     A rich comparison method may return the singleton *note
     NotImplemented: 776. if it does not implement the operation for a
     given pair of arguments.  By convention, ‘False’ and ‘True’ are
     returned for a successful comparison.  However, these methods can
     return any value, so if the comparison operator is used in a
     Boolean context (e.g., in the condition of an ‘if’ statement),
     Python will call *note bool(): 40e. on the value to determine if
     the result is true or false.

     By default, ‘object’ implements *note __eq__(): a9d. by using ‘is’,
     returning *note NotImplemented: 776. in the case of a false
     comparison: ‘True if x is y else NotImplemented’.  For *note
     __ne__(): 1486, by default it delegates to *note __eq__(): a9d. and
     inverts the result unless it is ‘NotImplemented’.  There are no
     other implied relationships among the comparison operators or
     default implementations; for example, the truth of ‘(x<y or x==y)’
     does not imply ‘x<=y’.  To automatically generate ordering
     operations from a single root operation, see *note
     functools.total_ordering(): ee6.

     See the paragraph on *note __hash__(): a9e. for some important
     notes on creating *note hashable: 5b5. objects which support custom
     comparison operations and are usable as dictionary keys.

     There are no swapped-argument versions of these methods (to be used
     when the left argument does not support the operation but the right
     argument does); rather, *note __lt__(): 129e. and *note __gt__():
     12a0. are each other's reflection, *note __le__(): 129f. and *note
     __ge__(): 12a1. are each other's reflection, and *note __eq__():
     a9d. and *note __ne__(): 1486. are their own reflection.  If the
     operands are of different types, and the right operand's type is a
     direct or indirect subclass of the left operand's type, the
     reflected method of the right operand has priority, otherwise the
     left operand's method has priority.  Virtual subclassing is not
     considered.

     When no appropriate method returns any value other than *note
     NotImplemented: 776, the ‘==’ and ‘!=’ operators will fall back to
     ‘is’ and ‘is not’, respectively.

 -- 方法: object.__hash__ (self)

     Called by built-in function *note hash(): 58f. and for operations
     on members of hashed collections including *note set: 57d, *note
     frozenset: 57e, and *note dict: 23b.  The ‘__hash__()’ method
     should return an integer.  The only required property is that
     objects which compare equal have the same hash value; it is advised
     to mix together the hash values of the components of the object
     that also play a part in comparison of objects by packing them into
     a tuple and hashing the tuple.  Example:

          def __hash__(self):
              return hash((self.name, self.nick, self.color))

          備註: *note hash(): 58f. truncates the value returned from an
          object's custom *note __hash__(): a9e. method to the size of a
          *note Py_ssize_t: a03.  This is typically 8 bytes on 64-bit
          builds and 4 bytes on 32-bit builds.  If an object's *note
          __hash__(): a9e. must interoperate on builds of different bit
          sizes, be sure to check the width on all supported builds.  An
          easy way to do this is with ‘python -c "import sys;
          print(sys.hash_info.width)"’.

     If a class does not define an *note __eq__(): a9d. method it should
     not define a *note __hash__(): a9e. operation either; if it defines
     *note __eq__(): a9d. but not *note __hash__(): a9e, its instances
     will not be usable as items in hashable collections.  If a class
     defines mutable objects and implements an *note __eq__(): a9d.
     method, it should not implement *note __hash__(): a9e, since the
     implementation of *note hashable: 5b5. collections requires that a
     key's hash value is immutable (if the object's hash value changes,
     it will be in the wrong hash bucket).

     User-defined classes have *note __eq__(): a9d. and *note
     __hash__(): a9e. methods by default; with them, all objects compare
     unequal (except with themselves) and ‘x.__hash__()’ returns an
     appropriate value such that ‘x == y’ implies both that ‘x is y’ and
     ‘hash(x) == hash(y)’.

     A class that overrides *note __eq__(): a9d. and does not define
     *note __hash__(): a9e. will have its *note __hash__(): a9e.
     implicitly set to ‘None’.  When the *note __hash__(): a9e. method
     of a class is ‘None’, instances of the class will raise an
     appropriate *note TypeError: 4dd. when a program attempts to
     retrieve their hash value, and will also be correctly identified as
     unhashable when checking ‘isinstance(obj,
     collections.abc.Hashable)’.

     If a class that overrides *note __eq__(): a9d. needs to retain the
     implementation of *note __hash__(): a9e. from a parent class, the
     interpreter must be told this explicitly by setting ‘__hash__ =
     <ParentClass>.__hash__’.

     If a class that does not override *note __eq__(): a9d. wishes to
     suppress hash support, it should include ‘__hash__ = None’ in the
     class definition.  A class which defines its own *note __hash__():
     a9e. that explicitly raises a *note TypeError: 4dd. would be
     incorrectly identified as hashable by an ‘isinstance(obj,
     collections.abc.Hashable)’ call.

          備註: By default, the *note __hash__(): a9e. values of str and
          bytes objects are "salted" with an unpredictable random value.
          Although they remain constant within an individual Python
          process, they are not predictable between repeated invocations
          of Python.

          This is intended to provide protection against a
          denial-of-service caused by carefully chosen inputs that
          exploit the worst case performance of a dict insertion,
          'O'('n'^2) complexity.  See
          ‘http://ocert.org/advisories/ocert-2011-003.html’ for details.

          Changing hash values affects the iteration order of sets.
          Python has never made guarantees about this ordering (and it
          typically varies between 32-bit and 64-bit builds).

          另請參閱 *note PYTHONHASHSEED: 101e.。

     在 3.3 版的變更: Hash randomization is enabled by default.

 -- 方法: object.__bool__ (self)

     Called to implement truth value testing and the built-in operation
     ‘bool()’; should return ‘False’ or ‘True’.  When this method is not
     defined, *note __len__(): 1e38. is called, if it is defined, and
     the object is considered true if its result is nonzero.  If a class
     defines neither ‘__len__()’ nor ‘__bool__()’, all its instances are
     considered true.


File: python.info,  Node: Customizing attribute access,  Next: Customizing class creation,  Prev: Basic customization,  Up: Special method names

4.3.3.2 Customizing attribute access
....................................

The following methods can be defined to customize the meaning of
attribute access (use of, assignment to, or deletion of ‘x.name’) for
class instances.

 -- 方法: object.__getattr__ (self, name)

     Called when the default attribute access fails with an *note
     AttributeError: 2f6. (either *note __getattribute__(): b79. raises
     an *note AttributeError: 2f6. because 'name' is not an instance
     attribute or an attribute in the class tree for ‘self’; or *note
     __get__(): 16c3. of a 'name' property raises *note AttributeError:
     2f6.).  This method should either return the (computed) attribute
     value or raise an *note AttributeError: 2f6. exception.

     Note that if the attribute is found through the normal mechanism,
     *note __getattr__(): 47a. is not called.  (This is an intentional
     asymmetry between *note __getattr__(): 47a. and *note
     __setattr__(): 1e05.)  This is done both for efficiency reasons and
     because otherwise *note __getattr__(): 47a. would have no way to
     access other attributes of the instance.  Note that at least for
     instance variables, you can take total control by not inserting any
     values in the instance attribute dictionary (but instead inserting
     them in another object).  See the *note __getattribute__(): b79.
     method below for a way to actually get total control over attribute
     access.

 -- 方法: object.__getattribute__ (self, name)

     Called unconditionally to implement attribute accesses for
     instances of the class.  If the class also defines *note
     __getattr__(): 47a, the latter will not be called unless *note
     __getattribute__(): b79. either calls it explicitly or raises an
     *note AttributeError: 2f6.  This method should return the
     (computed) attribute value or raise an *note AttributeError: 2f6.
     exception.  In order to avoid infinite recursion in this method,
     its implementation should always call the base class method with
     the same name to access any attributes it needs, for example,
     ‘object.__getattribute__(self, name)’.

          備註: This method may still be bypassed when looking up
          special methods as the result of implicit invocation via
          language syntax or *note built-in functions: 1df0.  See *note
          Special method lookup: 1e3b.

     For certain sensitive attribute accesses, raises an *note auditing
     event: 17bd. ‘object.__getattr__’ with arguments ‘obj’ and ‘name’.

 -- 方法: object.__setattr__ (self, name, value)

     Called when an attribute assignment is attempted.  This is called
     instead of the normal mechanism (i.e.  store the value in the
     instance dictionary).  'name' is the attribute name, 'value' is the
     value to be assigned to it.

     If *note __setattr__(): 1e05. wants to assign to an instance
     attribute, it should call the base class method with the same name,
     for example, ‘object.__setattr__(self, name, value)’.

     For certain sensitive attribute assignments, raises an *note
     auditing event: 17bd. ‘object.__setattr__’ with arguments ‘obj’,
     ‘name’, ‘value’.

 -- 方法: object.__delattr__ (self, name)

     Like *note __setattr__(): 1e05. but for attribute deletion instead
     of assignment.  This should only be implemented if ‘del obj.name’
     is meaningful for the object.

     For certain sensitive attribute deletions, raises an *note auditing
     event: 17bd. ‘object.__delattr__’ with arguments ‘obj’ and ‘name’.

 -- 方法: object.__dir__ (self)

     Called when *note dir(): 5d8. is called on the object.  An iterable
     must be returned.  *note dir(): 5d8. converts the returned iterable
     to a list and sorts it.

* Menu:

* Customizing module attribute access::
* Implementing Descriptors::
* Invoking Descriptors::
* __slots__: __slots__<2>.


File: python.info,  Node: Customizing module attribute access,  Next: Implementing Descriptors,  Up: Customizing attribute access

4.3.3.3 Customizing module attribute access
...........................................

Special names ‘__getattr__’ and ‘__dir__’ can be also used to customize
access to module attributes.  The ‘__getattr__’ function at the module
level should accept one argument which is the name of an attribute and
return the computed value or raise an *note AttributeError: 2f6.  If an
attribute is not found on a module object through the normal lookup,
i.e.  *note object.__getattribute__(): b79, then ‘__getattr__’ is
searched in the module ‘__dict__’ before raising an *note
AttributeError: 2f6.  If found, it is called with the attribute name and
the result is returned.

The ‘__dir__’ function should accept no arguments, and return an
iterable of strings that represents the names accessible on module.  If
present, this function overrides the standard *note dir(): 5d8. search
on a module.

For a more fine grained customization of the module behavior (setting
attributes, properties, etc.), one can set the ‘__class__’ attribute of
a module object to a subclass of *note types.ModuleType: db9.  For
example:

     import sys
     from types import ModuleType

     class VerboseModule(ModuleType):
         def __repr__(self):
             return f'Verbose {self.__name__}'

         def __setattr__(self, attr, value):
             print(f'Setting {attr}...')
             super().__setattr__(attr, value)

     sys.modules[__name__].__class__ = VerboseModule

     備註: Defining module ‘__getattr__’ and setting module ‘__class__’
     only affect lookups made using the attribute access syntax -
     directly accessing the module globals (whether by code within the
     module, or via a reference to the module's globals dictionary) is
     unaffected.

在 3.5 版的變更: ‘__class__’ module attribute is now writable.

在 3.7 版被加入: ‘__getattr__’ and ‘__dir__’ module attributes.

也參考
......

PEP 562(1) - 模組 __getattr__ 和 __dir__

     Describes the ‘__getattr__’ and ‘__dir__’ functions on modules.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0562/


File: python.info,  Node: Implementing Descriptors,  Next: Invoking Descriptors,  Prev: Customizing module attribute access,  Up: Customizing attribute access

4.3.3.4 Implementing Descriptors
................................

The following methods only apply when an instance of the class
containing the method (a so-called 'descriptor' class) appears in an
'owner' class (the descriptor must be in either the owner's class
dictionary or in the class dictionary for one of its parents).  In the
examples below, "the attribute" refers to the attribute whose name is
the key of the property in the owner class' *note __dict__: c04.

 -- 方法: object.__get__ (self, instance, owner=None)

     Called to get the attribute of the owner class (class attribute
     access) or of an instance of that class (instance attribute
     access).  The optional 'owner' argument is the owner class, while
     'instance' is the instance that the attribute was accessed through,
     or ‘None’ when the attribute is accessed through the 'owner'.

     This method should return the computed attribute value or raise an
     *note AttributeError: 2f6. exception.

     PEP 252(1) specifies that *note __get__(): 16c3. is callable with
     one or two arguments.  Python's own built-in descriptors support
     this specification; however, it is likely that some third-party
     tools have descriptors that require both arguments.  Python's own
     *note __getattribute__(): b79. implementation always passes in both
     arguments whether they are required or not.

 -- 方法: object.__set__ (self, instance, value)

     Called to set the attribute on an instance 'instance' of the owner
     class to a new value, 'value'.

     Note, adding *note __set__(): 1e3f. or *note __delete__(): 14fc.
     changes the kind of descriptor to a "data descriptor".  See *note
     Invoking Descriptors: 1e40. for more details.

 -- 方法: object.__delete__ (self, instance)

     Called to delete the attribute on an instance 'instance' of the
     owner class.

Instances of descriptors may also have the ‘__objclass__’ attribute
present:

 -- 屬性: object.__objclass__

     The attribute ‘__objclass__’ is interpreted by the *note inspect:
     72. module as specifying the class where this object was defined
     (setting this appropriately can assist in runtime introspection of
     dynamic class attributes).  For callables, it may indicate that an
     instance of the given type (or a subclass) is expected or required
     as the first positional argument (for example, CPython sets this
     attribute for unbound methods that are implemented in C).

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0252/


File: python.info,  Node: Invoking Descriptors,  Next: __slots__<2>,  Prev: Implementing Descriptors,  Up: Customizing attribute access

4.3.3.5 Invoking Descriptors
............................

In general, a descriptor is an object attribute with "binding behavior",
one whose attribute access has been overridden by methods in the
descriptor protocol: *note __get__(): 16c3, *note __set__(): 1e3f, and
*note __delete__(): 14fc.  If any of those methods are defined for an
object, it is said to be a descriptor.

The default behavior for attribute access is to get, set, or delete the
attribute from an object's dictionary.  For instance, ‘a.x’ has a lookup
chain starting with ‘a.__dict__['x']’, then ‘type(a).__dict__['x']’, and
continuing through the base classes of ‘type(a)’ excluding metaclasses.

However, if the looked-up value is an object defining one of the
descriptor methods, then Python may override the default behavior and
invoke the descriptor method instead.  Where this occurs in the
precedence chain depends on which descriptor methods were defined and
how they were called.

The starting point for descriptor invocation is a binding, ‘a.x’.  How
the arguments are assembled depends on ‘a’:

Direct Call

     The simplest and least common call is when user code directly
     invokes a descriptor method: ‘x.__get__(a)’.

Instance Binding

     If binding to an object instance, ‘a.x’ is transformed into the
     call: ‘type(a).__dict__['x'].__get__(a, type(a))’.

Class Binding

     If binding to a class, ‘A.x’ is transformed into the call:
     ‘A.__dict__['x'].__get__(None, A)’.

Super Binding

     A dotted lookup such as ‘super(A, a).x’ searches
     ‘a.__class__.__mro__’ for a base class ‘B’ following ‘A’ and then
     returns ‘B.__dict__['x'].__get__(a, A)’.  If not a descriptor, ‘x’
     is returned unchanged.

For instance bindings, the precedence of descriptor invocation depends
on which descriptor methods are defined.  A descriptor can define any
combination of *note __get__(): 16c3, *note __set__(): 1e3f. and *note
__delete__(): 14fc.  If it does not define ‘__get__()’, then accessing
the attribute will return the descriptor object itself unless there is a
value in the object's instance dictionary.  If the descriptor defines
‘__set__()’ and/or ‘__delete__()’, it is a data descriptor; if it
defines neither, it is a non-data descriptor.  Normally, data
descriptors define both ‘__get__()’ and ‘__set__()’, while non-data
descriptors have just the ‘__get__()’ method.  Data descriptors with
‘__get__()’ and ‘__set__()’ (and/or ‘__delete__()’) defined always
override a redefinition in an instance dictionary.  In contrast,
non-data descriptors can be overridden by instances.

Python methods (including those decorated with *note @staticmethod: 358.
and *note @classmethod: 14a.) are implemented as non-data descriptors.
Accordingly, instances can redefine and override methods.  This allows
individual instances to acquire behaviors that differ from other
instances of the same class.

The *note property(): 180. function is implemented as a data descriptor.
Accordingly, instances cannot override the behavior of a property.


File: python.info,  Node: __slots__<2>,  Prev: Invoking Descriptors,  Up: Customizing attribute access

4.3.3.6 __slots__
.................

'__slots__' allow us to explicitly declare data members (like
properties) and deny the creation of *note __dict__: c04. and
'__weakref__' (unless explicitly declared in '__slots__' or available in
a parent.)

The space saved over using *note __dict__: c04. can be significant.
Attribute lookup speed can be significantly improved as well.

 -- 資料: object.__slots__

     This class variable can be assigned a string, iterable, or sequence
     of strings with variable names used by instances.  '__slots__'
     reserves space for the declared variables and prevents the
     automatic creation of *note __dict__: c04. and '__weakref__' for
     each instance.
Notes on using '__slots__':

   * When inheriting from a class without '__slots__', the *note
     __dict__: c04. and '__weakref__' attribute of the instances will
     always be accessible.

   * Without a *note __dict__: c04. variable, instances cannot be
     assigned new variables not listed in the '__slots__' definition.
     Attempts to assign to an unlisted variable name raises *note
     AttributeError: 2f6.  If dynamic assignment of new variables is
     desired, then add ‘'__dict__'’ to the sequence of strings in the
     '__slots__' declaration.

   * Without a '__weakref__' variable for each instance, classes
     defining '__slots__' do not support *note weak references: fc. to
     its instances.  If weak reference support is needed, then add
     ‘'__weakref__'’ to the sequence of strings in the '__slots__'
     declaration.

   * '__slots__' are implemented at the class level by creating *note
     descriptors: bf6. for each variable name.  As a result, class
     attributes cannot be used to set default values for instance
     variables defined by '__slots__'; otherwise, the class attribute
     would overwrite the descriptor assignment.

   * The action of a '__slots__' declaration is not limited to the class
     where it is defined.  '__slots__' declared in parents are available
     in child classes.  However, child subclasses will get a *note
     __dict__: c04. and '__weakref__' unless they also define
     '__slots__' (which should only contain names of any 'additional'
     slots).

   * If a class defines a slot also defined in a base class, the
     instance variable defined by the base class slot is inaccessible
     (except by retrieving its descriptor directly from the base class).
     This renders the meaning of the program undefined.  In the future,
     a check may be added to prevent this.

   * *note TypeError: 4dd. will be raised if nonempty '__slots__' are
     defined for a class derived from a *note "variable-length" built-in
     type: 1e46. such as *note int: 23c, *note bytes: 1a5, and *note
     tuple: 322.

   * Any non-string *note iterable: 11bf. may be assigned to
     '__slots__'.

   * If a *note dictionary: 23b. is used to assign '__slots__', the
     dictionary keys will be used as the slot names.  The values of the
     dictionary can be used to provide per-attribute docstrings that
     will be recognised by *note inspect.getdoc(): 99e. and displayed in
     the output of *note help(): 87c.

   * *note __class__: 1418. assignment works only if both classes have
     the same '__slots__'.

   * *note Multiple inheritance: 1bbb. with multiple slotted parent
     classes can be used, but only one parent is allowed to have
     attributes created by slots (the other bases must have empty slot
     layouts) - violations raise *note TypeError: 4dd.

   * If an *note iterator: 192. is used for '__slots__' then a *note
     descriptor: 1e47. is created for each of the iterator's values.
     However, the '__slots__' attribute will be an empty iterator.


File: python.info,  Node: Customizing class creation,  Next: Customizing instance and subclass checks,  Prev: Customizing attribute access,  Up: Special method names

4.3.3.7 Customizing class creation
..................................

Whenever a class inherits from another class, *note __init_subclass__():
5d7. is called on the parent class.  This way, it is possible to write
classes which change the behavior of subclasses.  This is closely
related to class decorators, but where class decorators only affect the
specific class they're applied to, ‘__init_subclass__’ solely applies to
future subclasses of the class defining the method.

 -- 方法: classmethod object.__init_subclass__ (cls)

     This method is called whenever the containing class is subclassed.
     'cls' is then the new subclass.  If defined as a normal instance
     method, this method is implicitly converted to a class method.

     Keyword arguments which are given to a new class are passed to the
     parent class's ‘__init_subclass__’.  For compatibility with other
     classes using ‘__init_subclass__’, one should take out the needed
     keyword arguments and pass the others over to the base class, as
     in:

          class Philosopher:
              def __init_subclass__(cls, /, default_name, **kwargs):
                  super().__init_subclass__(**kwargs)
                  cls.default_name = default_name

          class AustralianPhilosopher(Philosopher, default_name="Bruce"):
              pass

     The default implementation ‘object.__init_subclass__’ does nothing,
     but raises an error if it is called with any arguments.

          備註: The metaclass hint ‘metaclass’ is consumed by the rest
          of the type machinery, and is never passed to
          ‘__init_subclass__’ implementations.  The actual metaclass
          (rather than the explicit hint) can be accessed as
          ‘type(cls)’.

     在 3.6 版被加入.

When a class is created, ‘type.__new__()’ scans the class variables and
makes callbacks to those with a *note __set_name__(): bf5. hook.

 -- 方法: object.__set_name__ (self, owner, name)

     Automatically called at the time the owning class 'owner' is
     created.  The object has been assigned to 'name' in that class:

          class A:
              x = C()  # 自動呼叫：x.__set_name__(A, 'x')

     If the class variable is assigned after the class is created, *note
     __set_name__(): bf5. will not be called automatically.  If needed,
     *note __set_name__(): bf5. can be called directly:

          class A:
             pass

          c = C()
          A.x = c                  # The hook is not called
          c.__set_name__(A, 'x')   # Manually invoke the hook

     更多細節請見 *note Creating the class object: bf1.。

     在 3.6 版被加入.

* Menu:

* Metaclasses::
* Resolving MRO entries::
* Determining the appropriate metaclass::
* Preparing the class namespace::
* Executing the class body::
* Creating the class object::
* Uses for metaclasses::


File: python.info,  Node: Metaclasses,  Next: Resolving MRO entries,  Up: Customizing class creation

4.3.3.8 Metaclasses
...................

By default, classes are constructed using *note type(): cef.  The class
body is executed in a new namespace and the class name is bound locally
to the result of ‘type(name, bases, namespace)’.

The class creation process can be customized by passing the ‘metaclass’
keyword argument in the class definition line, or by inheriting from an
existing class that included such an argument.  In the following
example, both ‘MyClass’ and ‘MySubclass’ are instances of ‘Meta’:

     class Meta(type):
         pass

     class MyClass(metaclass=Meta):
         pass

     class MySubclass(MyClass):
         pass

Any other keyword arguments that are specified in the class definition
are passed through to all metaclass operations described below.

When a class definition is executed, the following steps occur:

   * MRO entries are resolved;

   * the appropriate metaclass is determined;

   * the class namespace is prepared;

   * the class body is executed;

   * the class object is created.


File: python.info,  Node: Resolving MRO entries,  Next: Determining the appropriate metaclass,  Prev: Metaclasses,  Up: Customizing class creation

4.3.3.9 Resolving MRO entries
.............................

 -- 方法: object.__mro_entries__ (self, bases)

     If a base that appears in a class definition is not an instance of
     *note type: cef, then an ‘__mro_entries__()’ method is searched on
     the base.  If an ‘__mro_entries__()’ method is found, the base is
     substituted with the result of a call to ‘__mro_entries__()’ when
     creating the class.  The method is called with the original bases
     tuple passed to the 'bases' parameter, and must return a tuple of
     classes that will be used instead of the base.  The returned tuple
     may be empty: in these cases, the original base is ignored.

也參考
......

*note types.resolve_bases(): b43.

     Dynamically resolve bases that are not instances of *note type:
     cef.

*note types.get_original_bases(): 475.

     Retrieve a class's "original bases" prior to modifications by *note
     __mro_entries__(): 1e4c.

PEP 560(1)

     Core support for typing module and generic types.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0560/


File: python.info,  Node: Determining the appropriate metaclass,  Next: Preparing the class namespace,  Prev: Resolving MRO entries,  Up: Customizing class creation

4.3.3.10 Determining the appropriate metaclass
..............................................

The appropriate metaclass for a class definition is determined as
follows:

   * if no bases and no explicit metaclass are given, then *note type():
     cef. is used;

   * if an explicit metaclass is given and it is 'not' an instance of
     *note type(): cef, then it is used directly as the metaclass;

   * if an instance of *note type(): cef. is given as the explicit
     metaclass, or bases are defined, then the most derived metaclass is
     used.

The most derived metaclass is selected from the explicitly specified
metaclass (if any) and the metaclasses (i.e.  ‘type(cls)’) of all
specified base classes.  The most derived metaclass is one which is a
subtype of 'all' of these candidate metaclasses.  If none of the
candidate metaclasses meets that criterion, then the class definition
will fail with ‘TypeError’.


File: python.info,  Node: Preparing the class namespace,  Next: Executing the class body,  Prev: Determining the appropriate metaclass,  Up: Customizing class creation

4.3.3.11 Preparing the class namespace
......................................

Once the appropriate metaclass has been identified, then the class
namespace is prepared.  If the metaclass has a ‘__prepare__’ attribute,
it is called as ‘namespace = metaclass.__prepare__(name, bases, **kwds)’
(where the additional keyword arguments, if any, come from the class
definition).  The ‘__prepare__’ method should be implemented as a *note
classmethod: 14a.  The namespace returned by ‘__prepare__’ is passed in
to ‘__new__’, but when the final class object is created the namespace
is copied into a new ‘dict’.

If the metaclass has no ‘__prepare__’ attribute, then the class
namespace is initialised as an empty ordered mapping.

也參考
......

PEP 3115(1) - Metaclasses in Python 3000

     Introduced the ‘__prepare__’ namespace hook

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3115/


File: python.info,  Node: Executing the class body,  Next: Creating the class object,  Prev: Preparing the class namespace,  Up: Customizing class creation

4.3.3.12 Executing the class body
.................................

The class body is executed (approximately) as ‘exec(body, globals(),
namespace)’.  The key difference from a normal call to *note exec():
162. is that lexical scoping allows the class body (including any
methods) to reference names from the current and outer scopes when the
class definition occurs inside a function.

However, even when the class definition occurs inside the function,
methods defined inside the class still cannot see names defined at the
class scope.  Class variables must be accessed through the first
parameter of instance or class methods, or through the implicit
lexically scoped ‘__class__’ reference described in the next section.


File: python.info,  Node: Creating the class object,  Next: Uses for metaclasses,  Prev: Executing the class body,  Up: Customizing class creation

4.3.3.13 Creating the class object
..................................

Once the class namespace has been populated by executing the class body,
the class object is created by calling ‘metaclass(name, bases,
namespace, **kwds)’ (the additional keywords passed here are the same as
those passed to ‘__prepare__’).

This class object is the one that will be referenced by the
zero-argument form of *note super(): 483.  ‘__class__’ is an implicit
closure reference created by the compiler if any methods in a class body
refer to either ‘__class__’ or ‘super’.  This allows the zero argument
form of *note super(): 483. to correctly identify the class being
defined based on lexical scoping, while the class or instance that was
used to make the current call is identified based on the first argument
passed to the method.

'CPython 實作細節：' In CPython 3.6 and later, the ‘__class__’ cell is
passed to the metaclass as a ‘__classcell__’ entry in the class
namespace.  If present, this must be propagated up to the ‘type.__new__’
call in order for the class to be initialised correctly.  Failing to do
so will result in a *note RuntimeError: 179. in Python 3.8.

When using the default metaclass *note type: cef, or any metaclass that
ultimately calls ‘type.__new__’, the following additional customization
steps are invoked after creating the class object:

  1. The ‘type.__new__’ method collects all of the attributes in the
     class namespace that define a *note __set_name__(): bf5. method;

  2. Those ‘__set_name__’ methods are called with the class being
     defined and the assigned name of that particular attribute;

  3. The *note __init_subclass__(): 5d7. hook is called on the immediate
     parent of the new class in its method resolution order.

After the class object is created, it is passed to the class decorators
included in the class definition (if any) and the resulting object is
bound in the local namespace as the defined class.

When a new class is created by ‘type.__new__’, the object provided as
the namespace parameter is copied to a new ordered mapping and the
original object is discarded.  The new copy is wrapped in a read-only
proxy, which becomes the *note __dict__: c04. attribute of the class
object.

也參考
......

PEP 3135(1) - New super

     Describes the implicit ‘__class__’ closure reference

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3135/


File: python.info,  Node: Uses for metaclasses,  Prev: Creating the class object,  Up: Customizing class creation

4.3.3.14 Uses for metaclasses
.............................

The potential uses for metaclasses are boundless.  Some ideas that have
been explored include enum, logging, interface checking, automatic
delegation, automatic property creation, proxies, frameworks, and
automatic resource locking/synchronization.


File: python.info,  Node: Customizing instance and subclass checks,  Next: Emulating generic types,  Prev: Customizing class creation,  Up: Special method names

4.3.3.15 Customizing instance and subclass checks
.................................................

The following methods are used to override the default behavior of the
*note isinstance(): 3e8. and *note issubclass(): 765. built-in
functions.

In particular, the metaclass *note abc.ABCMeta: ebc. implements these
methods in order to allow the addition of Abstract Base Classes (ABCs)
as "virtual base classes" to any class or type (including built-in
types), including other ABCs.

 -- 方法: class.__instancecheck__ (self, instance)

     Return true if 'instance' should be considered a (direct or
     indirect) instance of 'class'.  If defined, called to implement
     ‘isinstance(instance, class)’.

 -- 方法: class.__subclasscheck__ (self, subclass)

     Return true if 'subclass' should be considered a (direct or
     indirect) subclass of 'class'.  If defined, called to implement
     ‘issubclass(subclass, class)’.

Note that these methods are looked up on the type (metaclass) of a
class.  They cannot be defined as class methods in the actual class.
This is consistent with the lookup of special methods that are called on
instances, only in this case the instance is itself a class.

也參考
......

PEP 3119(1) - Introducing Abstract Base Classes

     Includes the specification for customizing *note isinstance(): 3e8.
     and *note issubclass(): 765. behavior through *note
     __instancecheck__(): 1e53. and *note __subclasscheck__(): 1e54,
     with motivation for this functionality in the context of adding
     Abstract Base Classes (see the *note abc: 4. module) to the
     language.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3119/


File: python.info,  Node: Emulating generic types,  Next: Emulating callable objects,  Prev: Customizing instance and subclass checks,  Up: Special method names

4.3.3.16 Emulating generic types
................................

When using *note type annotations: 3fe, it is often useful to
'parameterize' a *note generic type: 3df. using Python's square-brackets
notation.  For example, the annotation ‘list[int]’ might be used to
signify a *note list: 5b6. in which all the elements are of type *note
int: 23c.

也參考
......

PEP 484(1) - Type Hints

     Introducing Python's framework for type annotations

*note 泛型別名型別: 656.

     Documentation for objects representing parameterized generic
     classes

*note 泛型: 1e56, *note user-defined generics: 476. and *note typing.Generic: 150c.

     Documentation on how to implement generic classes that can be
     parameterized at runtime and understood by static type-checkers.

A class can 'generally' only be parameterized if it defines the special
class method ‘__class_getitem__()’.

 -- 方法: classmethod object.__class_getitem__ (cls, key)

     Return an object representing the specialization of a generic class
     by type arguments found in 'key'.

     When defined on a class, ‘__class_getitem__()’ is automatically a
     class method.  As such, there is no need for it to be decorated
     with *note @classmethod: 14a. when it is defined.

* Menu:

* The purpose of __class_getitem__::
* __class_getitem__ versus __getitem__::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0484/


File: python.info,  Node: The purpose of __class_getitem__,  Next: __class_getitem__ versus __getitem__,  Up: Emulating generic types

4.3.3.17 The purpose of '__class_getitem__'
...........................................

The purpose of *note __class_getitem__(): 6df. is to allow runtime
parameterization of standard-library generic classes in order to more
easily apply *note type hints: 1e58. to these classes.

To implement custom generic classes that can be parameterized at runtime
and understood by static type-checkers, users should either inherit from
a standard library class that already implements *note
__class_getitem__(): 6df, or inherit from *note typing.Generic: 150c,
which has its own implementation of ‘__class_getitem__()’.

Custom implementations of *note __class_getitem__(): 6df. on classes
defined outside of the standard library may not be understood by
third-party type-checkers such as mypy.  Using ‘__class_getitem__()’ on
any class for purposes other than type hinting is discouraged.


File: python.info,  Node: __class_getitem__ versus __getitem__,  Prev: The purpose of __class_getitem__,  Up: Emulating generic types

4.3.3.18 '__class_getitem__' versus '__getitem__'
.................................................

Usually, the *note subscription: 1e5b. of an object using square
brackets will call the *note __getitem__(): 266. instance method defined
on the object's class.  However, if the object being subscribed is
itself a class, the class method *note __class_getitem__(): 6df. may be
called instead.  ‘__class_getitem__()’ should return a *note
GenericAlias: 656. object if it is properly defined.

Presented with the *note expression: 1e5c. ‘obj[x]’, the Python
interpreter follows something like the following process to decide
whether *note __getitem__(): 266. or *note __class_getitem__(): 6df.
should be called:

     from inspect import isclass

     def subscribe(obj, x):
         """Return the result of the expression 'obj[x]'"""

         class_of_obj = type(obj)

         # If the class of obj defines __getitem__,
         # call class_of_obj.__getitem__(obj, x)
         if hasattr(class_of_obj, '__getitem__'):
             return class_of_obj.__getitem__(obj, x)

         # Else, if obj is a class and defines __class_getitem__,
         # call obj.__class_getitem__(x)
         elif isclass(obj) and hasattr(obj, '__class_getitem__'):
             return obj.__class_getitem__(x)

         # Else, raise an exception
         else:
             raise TypeError(
                 f"'{class_of_obj.__name__}' object is not subscriptable"
             )

In Python, all classes are themselves instances of other classes.  The
class of a class is known as that class's *note metaclass: 1e5d, and
most classes have the *note type: cef. class as their metaclass.  *note
type: cef. does not define *note __getitem__(): 266, meaning that
expressions such as ‘list[int]’, ‘dict[str, float]’ and ‘tuple[str,
bytes]’ all result in *note __class_getitem__(): 6df. being called:

     >>> # list has class "type" as its metaclass, like most classes:
     >>> type(list)
     <class 'type'>
     >>> type(dict) == type(list) == type(tuple) == type(str) == type(bytes)
     True
     >>> # "list[int]" calls "list.__class_getitem__(int)"
     >>> list[int]
     list[int]
     >>> # list.__class_getitem__ returns a GenericAlias object:
     >>> type(list[int])
     <class 'types.GenericAlias'>

However, if a class has a custom metaclass that defines *note
__getitem__(): 266, subscribing the class may result in different
behaviour.  An example of this can be found in the *note enum: 4c.
module:

     >>> from enum import Enum
     >>> class Menu(Enum):
     ...     """A breakfast menu"""
     ...     SPAM = 'spam'
     ...     BACON = 'bacon'
     ...
     >>> # Enum classes have a custom metaclass:
     >>> type(Menu)
     <class 'enum.EnumMeta'>
     >>> # EnumMeta defines __getitem__,
     >>> # so __class_getitem__ is not called,
     >>> # and the result is not a GenericAlias object:
     >>> Menu['SPAM']
     <Menu.SPAM: 'spam'>
     >>> type(Menu['SPAM'])
     <enum 'Menu'>

也參考
......

PEP 560(1) - Core Support for typing module and generic types

     Introducing *note __class_getitem__(): 6df, and outlining when a
     *note subscription: 1e5b. results in ‘__class_getitem__()’ being
     called instead of *note __getitem__(): 266.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0560/


File: python.info,  Node: Emulating callable objects,  Next: Emulating container types,  Prev: Emulating generic types,  Up: Special method names

4.3.3.19 Emulating callable objects
...................................

 -- 方法: object.__call__ (self[, args...])

     Called when the instance is "called" as a function; if this method
     is defined, ‘x(arg1, arg2, ...)’ roughly translates to
     ‘type(x).__call__(x, arg1, ...)’.


File: python.info,  Node: Emulating container types,  Next: Emulating numeric types,  Prev: Emulating callable objects,  Up: Special method names

4.3.3.20 Emulating container types
..................................

The following methods can be defined to implement container objects.
Containers usually are *note sequences: 499. (such as *note lists: 5b6.
or *note tuples: 322.) or *note mappings: 1154. (like *note
dictionaries: 23b.), but can represent other containers as well.  The
first set of methods is used either to emulate a sequence or to emulate
a mapping; the difference is that for a sequence, the allowable keys
should be the integers 'k' for which ‘0 <= k < N’ where 'N' is the
length of the sequence, or *note slice: 410. objects, which define a
range of items.  It is also recommended that mappings provide the
methods ‘keys()’, ‘values()’, ‘items()’, ‘get()’, ‘clear()’,
‘setdefault()’, ‘pop()’, ‘popitem()’, ‘copy()’, and ‘update()’ behaving
similar to those for Python's standard *note dictionary: 23b. objects.
The *note collections.abc: 17. module provides a *note MutableMapping:
1048. *note abstract base class: 114e. to help create those methods from
a base set of *note __getitem__(): 266, *note __setitem__(): 1434, *note
__delitem__(): 1435, and ‘keys()’.  Mutable sequences should provide
methods ‘append()’, ‘count()’, ‘index()’, ‘extend()’, ‘insert()’,
‘pop()’, ‘remove()’, ‘reverse()’ and ‘sort()’, like Python standard
*note list: 5b6. objects.  Finally, sequence types should implement
addition (meaning concatenation) and multiplication (meaning repetition)
by defining the methods *note __add__(): 1e62, *note __radd__(): 1e63,
*note __iadd__(): 1e64, *note __mul__(): 1e65, *note __rmul__(): 1e66.
and *note __imul__(): 1e67. described below; they should not define
other numerical operators.  It is recommended that both mappings and
sequences implement the *note __contains__(): 1e33. method to allow
efficient use of the ‘in’ operator; for mappings, ‘in’ should search the
mapping's keys; for sequences, it should search through the values.  It
is further recommended that both mappings and sequences implement the
*note __iter__(): 1e31. method to allow efficient iteration through the
container; for mappings, ‘__iter__()’ should iterate through the
object's keys; for sequences, it should iterate through the values.

 -- 方法: object.__len__ (self)

     Called to implement the built-in function *note len(): 5d4.  Should
     return the length of the object, an integer ‘>=’ 0.  Also, an
     object that doesn't define a *note __bool__(): 1268. method and
     whose ‘__len__()’ method returns zero is considered to be false in
     a Boolean context.

     'CPython 實作細節：' In CPython, the length is required to be at
     most *note sys.maxsize: 115d.  If the length is larger than
     ‘sys.maxsize’ some features (such as *note len(): 5d4.) may raise
     *note OverflowError: 825.  To prevent raising ‘OverflowError’ by
     truth value testing, an object must define a *note __bool__():
     1268. method.

 -- 方法: object.__length_hint__ (self)

     Called to implement *note operator.length_hint(): f10.  Should
     return an estimated length for the object (which may be greater or
     less than the actual length).  The length must be an integer ‘>=’
     0.  The return value may also be *note NotImplemented: 776, which
     is treated the same as if the ‘__length_hint__’ method didn't exist
     at all.  This method is purely an optimization and is never
     required for correctness.

     在 3.4 版被加入.

     備註: Slicing is done exclusively with the following three methods.
     A call like

          a[1:2] = b

     is translated to

          a[slice(1, 2, None)] = b

     and so forth.  Missing slice items are always filled in with
     ‘None’.

 -- 方法: object.__getitem__ (self, key)

     Called to implement evaluation of ‘self[key]’.  For *note sequence:
     499. types, the accepted keys should be integers.  Optionally, they
     may support *note slice: 410. objects as well.  Negative index
     support is also optional.  If 'key' is of an inappropriate type,
     *note TypeError: 4dd. may be raised; if 'key' is a value outside
     the set of indexes for the sequence (after any special
     interpretation of negative values), *note IndexError: 14a3. should
     be raised.  For *note mapping: 1154. types, if 'key' is missing
     (not in the container), *note KeyError: 2fb. should be raised.

          備註: *note for: 2c3. loops expect that an *note IndexError:
          14a3. will be raised for illegal indexes to allow proper
          detection of the end of the sequence.

          備註: When *note subscripting: 1e5b. a 'class', the special
          class method *note __class_getitem__(): 6df. may be called
          instead of ‘__getitem__()’.  See *note __class_getitem__
          versus __getitem__: 1e5a. for more details.

 -- 方法: object.__setitem__ (self, key, value)

     Called to implement assignment to ‘self[key]’.  Same note as for
     *note __getitem__(): 266.  This should only be implemented for
     mappings if the objects support changes to the values for keys, or
     if new keys can be added, or for sequences if elements can be
     replaced.  The same exceptions should be raised for improper 'key'
     values as for the *note __getitem__(): 266. method.

 -- 方法: object.__delitem__ (self, key)

     Called to implement deletion of ‘self[key]’.  Same note as for
     *note __getitem__(): 266.  This should only be implemented for
     mappings if the objects support removal of keys, or for sequences
     if elements can be removed from the sequence.  The same exceptions
     should be raised for improper 'key' values as for the *note
     __getitem__(): 266. method.

 -- 方法: object.__missing__ (self, key)

     Called by *note dict: 23b.*note __getitem__(): 266. to implement
     ‘self[key]’ for dict subclasses when key is not in the dictionary.

 -- 方法: object.__iter__ (self)

     This method is called when an *note iterator: 192. is required for
     a container.  This method should return a new iterator object that
     can iterate over all the objects in the container.  For mappings,
     it should iterate over the keys of the container.

 -- 方法: object.__reversed__ (self)

     Called (if present) by the *note reversed(): 80a. built-in to
     implement reverse iteration.  It should return a new iterator
     object that iterates over all the objects in the container in
     reverse order.

     If the *note __reversed__(): 1e32. method is not provided, the
     *note reversed(): 80a. built-in will fall back to using the
     sequence protocol (*note __len__(): 1e38. and *note __getitem__():
     266.).  Objects that support the sequence protocol should only
     provide *note __reversed__(): 1e32. if they can provide an
     implementation that is more efficient than the one provided by
     *note reversed(): 80a.

The membership test operators (*note in: 2c5. and *note not in: 5d5.)
are normally implemented as an iteration through a container.  However,
container objects can supply the following special method with a more
efficient implementation, which also does not require the object be
iterable.

 -- 方法: object.__contains__ (self, item)

     Called to implement membership test operators.  Should return true
     if 'item' is in 'self', false otherwise.  For mapping objects, this
     should consider the keys of the mapping rather than the values or
     the key-item pairs.

     For objects that don't define *note __contains__(): 1e33, the
     membership test first tries iteration via *note __iter__(): 1e31,
     then the old sequence iteration protocol via *note __getitem__():
     266, see *note this section in the language reference: 1e69.


File: python.info,  Node: Emulating numeric types,  Next: With Statement Context Managers,  Prev: Emulating container types,  Up: Special method names

4.3.3.21 Emulating numeric types
................................

The following methods can be defined to emulate numeric objects.
Methods corresponding to operations that are not supported by the
particular kind of number implemented (e.g., bitwise operations for
non-integral numbers) should be left undefined.

 -- 方法: object.__add__ (self, other)
 -- 方法: object.__sub__ (self, other)
 -- 方法: object.__mul__ (self, other)
 -- 方法: object.__matmul__ (self, other)
 -- 方法: object.__truediv__ (self, other)
 -- 方法: object.__floordiv__ (self, other)
 -- 方法: object.__mod__ (self, other)
 -- 方法: object.__divmod__ (self, other)
 -- 方法: object.__pow__ (self, other[, modulo])
 -- 方法: object.__lshift__ (self, other)
 -- 方法: object.__rshift__ (self, other)
 -- 方法: object.__and__ (self, other)
 -- 方法: object.__xor__ (self, other)
 -- 方法: object.__or__ (self, other)

     These methods are called to implement the binary arithmetic
     operations (‘+’, ‘-’, ‘*’, ‘@’, ‘/’, ‘//’, ‘%’, *note divmod():
     945, *note pow(): 976, ‘**’, ‘<<’, ‘>>’, ‘&’, ‘^’, ‘|’).  For
     instance, to evaluate the expression ‘x + y’, where 'x' is an
     instance of a class that has an *note __add__(): 1e62. method,
     ‘type(x).__add__(x, y)’ is called.  The *note __divmod__(): 1e6f.
     method should be the equivalent to using *note __floordiv__():
     1462. and *note __mod__(): 1e6e.; it should not be related to *note
     __truediv__(): 1461.  Note that *note __pow__(): 777. should be
     defined to accept an optional third argument if the ternary version
     of the built-in *note pow(): 976. function is to be supported.

     If one of those methods does not support the operation with the
     supplied arguments, it should return *note NotImplemented: 776.

 -- 方法: object.__radd__ (self, other)
 -- 方法: object.__rsub__ (self, other)
 -- 方法: object.__rmul__ (self, other)
 -- 方法: object.__rmatmul__ (self, other)
 -- 方法: object.__rtruediv__ (self, other)
 -- 方法: object.__rfloordiv__ (self, other)
 -- 方法: object.__rmod__ (self, other)
 -- 方法: object.__rdivmod__ (self, other)
 -- 方法: object.__rpow__ (self, other[, modulo])
 -- 方法: object.__rlshift__ (self, other)
 -- 方法: object.__rrshift__ (self, other)
 -- 方法: object.__rand__ (self, other)
 -- 方法: object.__rxor__ (self, other)
 -- 方法: object.__ror__ (self, other)

     These methods are called to implement the binary arithmetic
     operations (‘+’, ‘-’, ‘*’, ‘@’, ‘/’, ‘//’, ‘%’, *note divmod():
     945, *note pow(): 976, ‘**’, ‘<<’, ‘>>’, ‘&’, ‘^’, ‘|’) with
     reflected (swapped) operands.  These functions are only called if
     the left operand does not support the corresponding operation (1)
     and the operands are of different types.  (2)  For instance, to
     evaluate the expression ‘x - y’, where 'y' is an instance of a
     class that has an *note __rsub__(): 1e75. method,
     ‘type(y).__rsub__(y, x)’ is called if ‘type(x).__sub__(x, y)’
     returns *note NotImplemented: 776.

     Note that ternary *note pow(): 976. will not try calling *note
     __rpow__(): 778. (the coercion rules would become too complicated).

          備註: If the right operand's type is a subclass of the left
          operand's type and that subclass provides a different
          implementation of the reflected method for the operation, this
          method will be called before the left operand's non-reflected
          method.  This behavior allows subclasses to override their
          ancestors' operations.

 -- 方法: object.__iadd__ (self, other)
 -- 方法: object.__isub__ (self, other)
 -- 方法: object.__imul__ (self, other)
 -- 方法: object.__imatmul__ (self, other)
 -- 方法: object.__itruediv__ (self, other)
 -- 方法: object.__ifloordiv__ (self, other)
 -- 方法: object.__imod__ (self, other)
 -- 方法: object.__ipow__ (self, other[, modulo])
 -- 方法: object.__ilshift__ (self, other)
 -- 方法: object.__irshift__ (self, other)
 -- 方法: object.__iand__ (self, other)
 -- 方法: object.__ixor__ (self, other)
 -- 方法: object.__ior__ (self, other)

     These methods are called to implement the augmented arithmetic
     assignments (‘+=’, ‘-=’, ‘*=’, ‘@=’, ‘/=’, ‘//=’, ‘%=’, ‘**=’,
     ‘<<=’, ‘>>=’, ‘&=’, ‘^=’, ‘|=’).  These methods should attempt to
     do the operation in-place (modifying 'self') and return the result
     (which could be, but does not have to be, 'self').  If a specific
     method is not defined, or if that method returns *note
     NotImplemented: 776, the augmented assignment falls back to the
     normal methods.  For instance, if 'x' is an instance of a class
     with an *note __iadd__(): 1e64. method, ‘x += y’ is equivalent to
     ‘x = x.__iadd__(y)’ .  If *note __iadd__(): 1e64. does not exist,
     or if ‘x.__iadd__(y)’ returns ‘NotImplemented’, ‘x.__add__(y)’ and
     ‘y.__radd__(x)’ are considered, as with the evaluation of ‘x + y’.
     In certain situations, augmented assignment can result in
     unexpected errors (see *note Why does a_tuple[i] += ['item'] raise
     an exception when the addition works?: 1e8a.), but this behavior is
     in fact part of the data model.

 -- 方法: object.__neg__ (self)
 -- 方法: object.__pos__ (self)
 -- 方法: object.__abs__ (self)
 -- 方法: object.__invert__ (self)

     Called to implement the unary arithmetic operations (‘-’, ‘+’,
     *note abs(): 1ba8. and ‘~’).

 -- 方法: object.__complex__ (self)
 -- 方法: object.__int__ (self)
 -- 方法: object.__float__ (self)

     Called to implement the built-in functions *note complex(): 2c9,
     *note int(): 23c. and *note float(): 2c8.  Should return a value of
     the appropriate type.

 -- 方法: object.__index__ (self)

     Called to implement *note operator.index(): 1811, and whenever
     Python needs to losslessly convert the numeric object to an integer
     object (such as in slicing, or in the built-in *note bin(): 123f,
     *note hex(): 1262. and *note oct(): 1261. functions).  Presence of
     this method indicates that the numeric object is an integer type.
     Must return an integer.

     If *note __int__(): 6c0, *note __float__(): 970. and *note
     __complex__(): 58d. are not defined then corresponding built-in
     functions *note int(): 23c, *note float(): 2c8. and *note
     complex(): 2c9. fall back to *note __index__(): 6c1.

 -- 方法: object.__round__ (self[, ndigits])
 -- 方法: object.__trunc__ (self)
 -- 方法: object.__floor__ (self)
 -- 方法: object.__ceil__ (self)

     Called to implement the built-in function *note round(): 126d. and
     *note math: 81. functions *note trunc(): 1331, *note floor(): 132f.
     and *note ceil(): 1330.  Unless 'ndigits' is passed to
     ‘__round__()’ all these methods should return the value of the
     object truncated to an *note Integral: 1e92. (typically an *note
     int: 23c.).

     The built-in function *note int(): 23c. falls back to *note
     __trunc__(): 6bf. if neither *note __int__(): 6c0. nor *note
     __index__(): 6c1. is defined.

     在 3.11 版的變更: The delegation of *note int(): 23c. to *note
     __trunc__(): 6bf. is deprecated.

   ---------- Footnotes ----------

   (1) "Does not support" here means that the class has no such method,
or the method returns *note NotImplemented: 776.  Do not set the method
to ‘None’ if you want to force fallback to the right operand's reflected
method—that will instead have the opposite effect of explicitly
'blocking' such fallback.

   (2) For operands of the same type, it is assumed that if the
non-reflected method - such as *note __add__(): 1e62. - fails then the
overall operation is not supported, which is why the reflected method is
not called.


File: python.info,  Node: With Statement Context Managers,  Next: Customizing positional arguments in class pattern matching,  Prev: Emulating numeric types,  Up: Special method names

4.3.3.22 With Statement Context Managers
........................................

A 'context manager' is an object that defines the runtime context to be
established when executing a *note with: 577. statement.  The context
manager handles the entry into, and the exit from, the desired runtime
context for the execution of the block of code.  Context managers are
normally invoked using the ‘with’ statement (described in section *note
The with statement: 577.), but can also be used by directly invoking
their methods.

Typical uses of context managers include saving and restoring various
kinds of global state, locking and unlocking resources, closing opened
files, etc.

For more information on context managers, see *note 情境管理器型別:
1e95.

 -- 方法: object.__enter__ (self)

     Enter the runtime context related to this object.  The *note with:
     577. statement will bind this method's return value to the
     target(s) specified in the ‘as’ clause of the statement, if any.

 -- 方法: object.__exit__ (self, exc_type, exc_value, traceback)

     Exit the runtime context related to this object.  The parameters
     describe the exception that caused the context to be exited.  If
     the context was exited without an exception, all three arguments
     will be *note None: 61b.

     If an exception is supplied, and the method wishes to suppress the
     exception (i.e., prevent it from being propagated), it should
     return a true value.  Otherwise, the exception will be processed
     normally upon exit from this method.

     Note that *note __exit__(): 1293. methods should not reraise the
     passed-in exception; this is the caller's responsibility.

也參考
......

PEP 343(1) - "with" 陳述式

     The specification, background, and examples for the Python *note
     with: 577. statement.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0343/


File: python.info,  Node: Customizing positional arguments in class pattern matching,  Next: Emulating buffer types,  Prev: With Statement Context Managers,  Up: Special method names

4.3.3.23 Customizing positional arguments in class pattern matching
...................................................................

When using a class name in a pattern, positional arguments in the
pattern are not allowed by default, i.e.  ‘case MyClass(x, y)’ is
typically invalid without special support in ‘MyClass’.  To be able to
use that kind of pattern, the class needs to define a '__match_args__'
attribute.

 -- 資料: object.__match_args__

     This class variable can be assigned a tuple of strings.  When this
     class is used in a class pattern with positional arguments, each
     positional argument will be converted into a keyword argument,
     using the corresponding value in '__match_args__' as the keyword.
     The absence of this attribute is equivalent to setting it to ‘()’.

For example, if ‘MyClass.__match_args__’ is ‘("left", "center",
"right")’ that means that ‘case MyClass(x, y)’ is equivalent to ‘case
MyClass(left=x, center=y)’.  Note that the number of arguments in the
pattern must be smaller than or equal to the number of elements in
'__match_args__'; if it is larger, the pattern match attempt will raise
a *note TypeError: 4dd.

在 3.10 版被加入.

也參考
......

PEP 634(1) - Structural Pattern Matching

     The specification for the Python ‘match’ statement.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0634/


File: python.info,  Node: Emulating buffer types,  Next: Special method lookup,  Prev: Customizing positional arguments in class pattern matching,  Up: Special method names

4.3.3.24 Emulating buffer types
...............................

The *note buffer protocol: 367. provides a way for Python objects to
expose efficient access to a low-level memory array.  This protocol is
implemented by builtin types such as *note bytes: 1a5. and *note
memoryview: 40f, and third-party libraries may define additional buffer
types.

While buffer types are usually implemented in C, it is also possible to
implement the protocol in Python.

 -- 方法: object.__buffer__ (self, flags)

     Called when a buffer is requested from 'self' (for example, by the
     *note memoryview: 40f. constructor).  The 'flags' argument is an
     integer representing the kind of buffer requested, affecting for
     example whether the returned buffer is read-only or writable.
     *note inspect.BufferFlags: 406. provides a convenient way to
     interpret the flags.  The method must return a *note memoryview:
     40f. object.

 -- 方法: object.__release_buffer__ (self, buffer)

     Called when a buffer is no longer needed.  The 'buffer' argument is
     a *note memoryview: 40f. object that was previously returned by
     *note __buffer__(): 405.  The method must release any resources
     associated with the buffer.  This method should return ‘None’.
     Buffer objects that do not need to perform any cleanup are not
     required to implement this method.

在 3.12 版被加入.

也參考
......

PEP 688(1) - Making the buffer protocol accessible in Python

     Introduces the Python ‘__buffer__’ and ‘__release_buffer__’
     methods.

*note collections.abc.Buffer: 2a5.

     ABC for buffer types.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0688/


File: python.info,  Node: Special method lookup,  Prev: Emulating buffer types,  Up: Special method names

4.3.3.25 Special method lookup
..............................

For custom classes, implicit invocations of special methods are only
guaranteed to work correctly if defined on an object's type, not in the
object's instance dictionary.  That behaviour is the reason why the
following code raises an exception:

     >>> class C:
     ...     pass
     ...
     >>> c = C()
     >>> c.__len__ = lambda: 5
     >>> len(c)
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: object of type 'C' has no len()

The rationale behind this behaviour lies with a number of special
methods such as *note __hash__(): a9e. and *note __repr__(): 5c2. that
are implemented by all objects, including type objects.  If the implicit
lookup of these methods used the conventional lookup process, they would
fail when invoked on the type object itself:

     >>> 1 .__hash__() == hash(1)
     True
     >>> int.__hash__() == hash(int)
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: descriptor '__hash__' of 'int' object needs an argument

Incorrectly attempting to invoke an unbound method of a class in this
way is sometimes referred to as 'metaclass confusion', and is avoided by
bypassing the instance when looking up special methods:

     >>> type(1).__hash__(1) == hash(1)
     True
     >>> type(int).__hash__(int) == hash(int)
     True

In addition to bypassing any instance attributes in the interest of
correctness, implicit special method lookup generally also bypasses the
*note __getattribute__(): b79. method even of the object's metaclass:

     >>> class Meta(type):
     ...     def __getattribute__(*args):
     ...         print("Metaclass getattribute invoked")
     ...         return type.__getattribute__(*args)
     ...
     >>> class C(object, metaclass=Meta):
     ...     def __len__(self):
     ...         return 10
     ...     def __getattribute__(*args):
     ...         print("Class getattribute invoked")
     ...         return object.__getattribute__(*args)
     ...
     >>> c = C()
     >>> c.__len__()                 # Explicit lookup via instance
     Class getattribute invoked
     10
     >>> type(c).__len__(c)          # Explicit lookup via type
     Metaclass getattribute invoked
     10
     >>> len(c)                      # Implicit lookup
     10

Bypassing the *note __getattribute__(): b79. machinery in this fashion
provides significant scope for speed optimisations within the
interpreter, at the cost of some flexibility in the handling of special
methods (the special method 'must' be set on the class object itself in
order to be consistently invoked by the interpreter).


File: python.info,  Node: 協程,  Prev: Special method names,  Up: 資料模型

4.3.4 協程
----------

* Menu:

* Awaitable Objects::
* Coroutine Objects::
* Asynchronous Iterators::
* Asynchronous Context Managers::


File: python.info,  Node: Awaitable Objects,  Next: Coroutine Objects,  Up: 協程

4.3.4.1 Awaitable Objects
.........................

An *note awaitable: 193. object generally implements an *note
__await__(): 1e9d. method.  *note Coroutine objects: 438. returned from
*note async def: 575. functions are awaitable.

     備註: The *note generator iterator: b85. objects returned from
     generators decorated with *note types.coroutine(): e2c. are also
     awaitable, but they do not implement *note __await__(): 1e9d.

 -- 方法: object.__await__ (self)

     Must return an *note iterator: 192.  Should be used to implement
     *note awaitable: 193. objects.  For instance, *note asyncio.Future:
     b74. implements this method to be compatible with the *note await:
     19f. expression.

          備註: The language doesn't place any restriction on the type
          or value of the objects yielded by the iterator returned by
          ‘__await__’, as this is specific to the implementation of the
          asynchronous execution framework (e.g.  *note asyncio: 8.)
          that will be managing the *note awaitable: 193. object.

在 3.5 版被加入.

也參考
......

PEP 492(1) for additional information about awaitable objects.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0492/


File: python.info,  Node: Coroutine Objects,  Next: Asynchronous Iterators,  Prev: Awaitable Objects,  Up: 協程

4.3.4.2 Coroutine Objects
.........................

*note Coroutine objects: 438. are *note awaitable: 193. objects.  A
coroutine's execution can be controlled by calling *note __await__():
1e9d. and iterating over the result.  When the coroutine has finished
executing and returns, the iterator raises *note StopIteration: ba1, and
the exception's *note value: 1e9f. attribute holds the return value.  If
the coroutine raises an exception, it is propagated by the iterator.
Coroutines should not directly raise unhandled *note StopIteration: ba1.
exceptions.

Coroutines also have the methods listed below, which are analogous to
those of generators (see *note Generator-iterator methods: 1ea0.).
However, unlike generators, coroutines do not directly support
iteration.

在 3.5.2 版的變更: It is a *note RuntimeError: 179. to await on a
coroutine more than once.

 -- 方法: coroutine.send (value)

     Starts or resumes execution of the coroutine.  If 'value' is
     ‘None’, this is equivalent to advancing the iterator returned by
     *note __await__(): 1e9d.  If 'value' is not ‘None’, this method
     delegates to the *note send(): 1ea2. method of the iterator that
     caused the coroutine to suspend.  The result (return value, *note
     StopIteration: ba1, or other exception) is the same as when
     iterating over the ‘__await__()’ return value, described above.

 -- 方法: coroutine.throw (value)

 -- 方法: coroutine.throw (type[, value[, traceback]])

     Raises the specified exception in the coroutine.  This method
     delegates to the *note throw(): 4a0. method of the iterator that
     caused the coroutine to suspend, if it has such a method.
     Otherwise, the exception is raised at the suspension point.  The
     result (return value, *note StopIteration: ba1, or other exception)
     is the same as when iterating over the *note __await__(): 1e9d.
     return value, described above.  If the exception is not caught in
     the coroutine, it propagates back to the caller.

     在 3.12 版的變更: The second signature (type[, value[, traceback]])
     is deprecated and may be removed in a future version of Python.

 -- 方法: coroutine.close ()

     Causes the coroutine to clean itself up and exit.  If the coroutine
     is suspended, this method first delegates to the *note close():
     15ee. method of the iterator that caused the coroutine to suspend,
     if it has such a method.  Then it raises *note GeneratorExit: 1335.
     at the suspension point, causing the coroutine to immediately clean
     itself up.  Finally, the coroutine is marked as having finished
     executing, even if it was never started.

     Coroutine objects are automatically closed using the above process
     when they are about to be destroyed.


File: python.info,  Node: Asynchronous Iterators,  Next: Asynchronous Context Managers,  Prev: Coroutine Objects,  Up: 協程

4.3.4.3 Asynchronous Iterators
..............................

An 'asynchronous iterator' can call asynchronous code in its ‘__anext__’
method.

Asynchronous iterators can be used in an *note async for: a4e.
statement.

 -- 方法: object.__aiter__ (self)

     Must return an 'asynchronous iterator' object.

 -- 方法: object.__anext__ (self)

     Must return an 'awaitable' resulting in a next value of the
     iterator.  Should raise a *note StopAsyncIteration: 1933. error
     when the iteration is over.

An example of an asynchronous iterable object:

     class Reader:
         async def readline(self):
             ...

         def __aiter__(self):
             return self

         async def __anext__(self):
             val = await self.readline()
             if val == b'':
                 raise StopAsyncIteration
             return val

在 3.5 版被加入.

在 3.7 版的變更: Prior to Python 3.7, *note __aiter__(): ba2. could
return an 'awaitable' that would resolve to an *note asynchronous
iterator: 191.

Starting with Python 3.7, *note __aiter__(): ba2. must return an
asynchronous iterator object.  Returning anything else will result in a
*note TypeError: 4dd. error.


File: python.info,  Node: Asynchronous Context Managers,  Prev: Asynchronous Iterators,  Up: 協程

4.3.4.4 Asynchronous Context Managers
.....................................

An 'asynchronous context manager' is a 'context manager' that is able to
suspend execution in its ‘__aenter__’ and ‘__aexit__’ methods.

Asynchronous context managers can be used in an *note async with: 57a.
statement.

 -- 方法: object.__aenter__ (self)

     Semantically similar to *note __enter__(): 56c, the only difference
     being that it must return an 'awaitable'.

 -- 方法: object.__aexit__ (self, exc_type, exc_value, traceback)

     Semantically similar to *note __exit__(): 1293, the only difference
     being that it must return an 'awaitable'.

An example of an asynchronous context manager class:

     class AsyncContextManager:
         async def __aenter__(self):
             await log('entering context')

         async def __aexit__(self, exc_type, exc, tb):
             await log('exiting context')

在 3.5 版被加入.

註解
....


File: python.info,  Node: 執行模型,  Next: 模組引入系統,  Prev: 資料模型,  Up: Python 語言參考手冊

4.4 執行模型
============

* Menu:

* Structure of a program::
* Naming and binding::
* 例外::


File: python.info,  Node: Structure of a program,  Next: Naming and binding,  Up: 執行模型

4.4.1 Structure of a program
----------------------------

A Python program is constructed from code blocks.  A 'block' is a piece
of Python program text that is executed as a unit.  The following are
blocks: a module, a function body, and a class definition.  Each command
typed interactively is a block.  A script file (a file given as standard
input to the interpreter or specified as a command line argument to the
interpreter) is a code block.  A script command (a command specified on
the interpreter command line with the *note -c: 584. option) is a code
block.  A module run as a top level script (as module ‘__main__’) from
the command line using a *note -m: 585. argument is also a code block.
The string argument passed to the built-in functions *note eval(): 163.
and *note exec(): 162. is a code block.

A code block is executed in an 'execution frame'.  A frame contains some
administrative information (used for debugging) and determines where and
how execution continues after the code block's execution has completed.


File: python.info,  Node: Naming and binding,  Next: 例外,  Prev: Structure of a program,  Up: 執行模型

4.4.2 Naming and binding
------------------------

* Menu:

* Binding of names::
* Resolution of names::
* Annotation scopes::
* Lazy evaluation::
* Builtins and restricted execution::
* Interaction with dynamic features::


File: python.info,  Node: Binding of names,  Next: Resolution of names,  Up: Naming and binding

4.4.2.1 Binding of names
........................

'Names' refer to objects.  Names are introduced by name binding
operations.

The following constructs bind names:

   * formal parameters to functions,

   * class definitions,

   * function definitions,

   * assignment expressions,

   * *note targets: 1eaf. that are identifiers if occurring in an
     assignment:

        + *note for: 2c3. loop header,

        + after ‘as’ in a *note with: 577. statement, *note except: 171.
          clause, *note except*: 55c. clause, or in the as-pattern in
          structural pattern matching,

        + in a capture pattern in structural pattern matching

   * *note import: 586. 陳述式。

   * *note type: 3de. 陳述式。

   * *note type parameter lists: 294.

The ‘import’ statement of the form ‘from ... import *’ binds all names
defined in the imported module, except those beginning with an
underscore.  This form may only be used at the module level.

A target occurring in a *note del: 16a9. statement is also considered
bound for this purpose (though the actual semantics are to unbind the
name).

Each assignment or import statement occurs within a block defined by a
class or function definition or at the module level (the top-level code
block).

If a name is bound in a block, it is a local variable of that block,
unless declared as *note nonlocal: 123e. or *note global: 170.  If a
name is bound at the module level, it is a global variable.  (The
variables of the module code block are local and global.)  If a variable
is used in a code block but not defined there, it is a 'free variable'.

Each occurrence of a name in the program text refers to the 'binding' of
that name established by the following name resolution rules.


File: python.info,  Node: Resolution of names,  Next: Annotation scopes,  Prev: Binding of names,  Up: Naming and binding

4.4.2.2 Resolution of names
...........................

A 'scope' defines the visibility of a name within a block.  If a local
variable is defined in a block, its scope includes that block.  If the
definition occurs in a function block, the scope extends to any blocks
contained within the defining one, unless a contained block introduces a
different binding for the name.

When a name is used in a code block, it is resolved using the nearest
enclosing scope.  The set of all such scopes visible to a code block is
called the block's 'environment'.

When a name is not found at all, a *note NameError: 3e5. exception is
raised.  If the current scope is a function scope, and the name refers
to a local variable that has not yet been bound to a value at the point
where the name is used, an *note UnboundLocalError: 14a4. exception is
raised.  *note UnboundLocalError: 14a4. is a subclass of *note
NameError: 3e5.

If a name binding operation occurs anywhere within a code block, all
uses of the name within the block are treated as references to the
current block.  This can lead to errors when a name is used within a
block before it is bound.  This rule is subtle.  Python lacks
declarations and allows name binding operations to occur anywhere within
a code block.  The local variables of a code block can be determined by
scanning the entire text of the block for name binding operations.  See
*note the FAQ entry on UnboundLocalError: 1eb2. for examples.

If the *note global: 170. statement occurs within a block, all uses of
the names specified in the statement refer to the bindings of those
names in the top-level namespace.  Names are resolved in the top-level
namespace by searching the global namespace, i.e.  the namespace of the
module containing the code block, and the builtins namespace, the
namespace of the module *note builtins: e.  The global namespace is
searched first.  If the names are not found there, the builtins
namespace is searched next.  If the names are also not found in the
builtins namespace, new variables are created in the global namespace.
The global statement must precede all uses of the listed names.

The *note global: 170. statement has the same scope as a name binding
operation in the same block.  If the nearest enclosing scope for a free
variable contains a global statement, the free variable is treated as a
global.

The *note nonlocal: 123e. statement causes corresponding names to refer
to previously bound variables in the nearest enclosing function scope.
*note SyntaxError: 173. is raised at compile time if the given name does
not exist in any enclosing function scope.  *note Type parameters: 294.
cannot be rebound with the ‘nonlocal’ statement.

The namespace for a module is automatically created the first time a
module is imported.  The main module for a script is always called *note
__main__: 1.

Class definition blocks and arguments to *note exec(): 162. and *note
eval(): 163. are special in the context of name resolution.  A class
definition is an executable statement that may use and define names.
These references follow the normal rules for name resolution with an
exception that unbound local variables are looked up in the global
namespace.  The namespace of the class definition becomes the attribute
dictionary of the class.  The scope of names defined in a class block is
limited to the class block; it does not extend to the code blocks of
methods.  This includes comprehensions and generator expressions, but it
does not include *note annotation scopes: 16e, which have access to
their enclosing class scopes.  This means that the following will fail:

     class A:
         a = 42
         b = list(a + i for i in range(10))

However, the following will succeed:

     class A:
         type Alias = Nested
         class Nested: pass

     print(A.Alias.__value__)  # <type 'A.Nested'>


File: python.info,  Node: Annotation scopes,  Next: Lazy evaluation,  Prev: Resolution of names,  Up: Naming and binding

4.4.2.3 Annotation scopes
.........................

*note Type parameter lists: 294. and *note type: 3de. statements
introduce 'annotation scopes', which behave mostly like function scopes,
but with some exceptions discussed below.  *note Annotations: 3fe.
currently do not use annotation scopes, but they are expected to use
annotation scopes in Python 3.13 when PEP 649(1) is implemented.

Annotation scopes are used in the following contexts:

   * Type parameter lists for *note generic type aliases: 3fc.

   * Type parameter lists for *note generic functions: 3f9.  A generic
     function's annotations are executed within the annotation scope,
     but its defaults and decorators are not.

   * Type parameter lists for *note generic classes: 3f8.  A generic
     class's base classes and keyword arguments are executed within the
     annotation scope, but its decorators are not.

   * The bounds, constraints, and default values for type parameters
     (*note lazily evaluated: 3fd.).

   * The value of type aliases (*note lazily evaluated: 3fd.).

Annotation scopes differ from function scopes in the following ways:

   * Annotation scopes have access to their enclosing class namespace.
     If an annotation scope is immediately within a class scope, or
     within another annotation scope that is immediately within a class
     scope, the code in the annotation scope can use names defined in
     the class scope as if it were executed directly within the class
     body.  This contrasts with regular functions defined within
     classes, which cannot access names defined in the class scope.

   * Expressions in annotation scopes cannot contain *note yield: 971,
     ‘yield from’, *note await: 19f, or *note ;=: 1eb4. expressions.
     (These expressions are allowed in other scopes contained within the
     annotation scope.)

   * Names defined in annotation scopes cannot be rebound with *note
     nonlocal: 123e. statements in inner scopes.  This includes only
     type parameters, as no other syntactic elements that can appear
     within annotation scopes can introduce new names.

   * While annotation scopes have an internal name, that name is not
     reflected in the *note __qualname__: 1843. of objects defined
     within the scope.  Instead, the ‘__qualname__’ of such objects is
     as if the object were defined in the enclosing scope.

在 3.12 版被加入: Annotation scopes were introduced in Python 3.12 as
part of PEP 695(2).

在 3.13 版的變更: Annotation scopes are also used for type parameter
defaults, as introduced by PEP 696(3).

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0649/

   (2) https://peps.python.org/pep-0695/

   (3) https://peps.python.org/pep-0696/


File: python.info,  Node: Lazy evaluation,  Next: Builtins and restricted execution,  Prev: Annotation scopes,  Up: Naming and binding

4.4.2.4 Lazy evaluation
.......................

The values of type aliases created through the *note type: 3de.
statement are 'lazily evaluated'.  The same applies to the bounds,
constraints, and default values of type variables created through the
*note type parameter syntax: 294.  This means that they are not
evaluated when the type alias or type variable is created.  Instead,
they are only evaluated when doing so is necessary to resolve an
attribute access.

舉例來說：

     >>> type Alias = 1/0
     >>> Alias.__value__
     Traceback (most recent call last):
       ...
     ZeroDivisionError: division by zero
     >>> def func[T: 1/0](): pass
     >>> T = func.__type_params__[0]
     >>> T.__bound__
     Traceback (most recent call last):
       ...
     ZeroDivisionError: division by zero

Here the exception is raised only when the ‘__value__’ attribute of the
type alias or the ‘__bound__’ attribute of the type variable is
accessed.

This behavior is primarily useful for references to types that have not
yet been defined when the type alias or type variable is created.  For
example, lazy evaluation enables creation of mutually recursive type
aliases:

     from typing import Literal

     type SimpleExpr = int | Parenthesized
     type Parenthesized = tuple[Literal["("], Expr, Literal[")"]]
     type Expr = SimpleExpr | tuple[SimpleExpr, Literal["+", "-"], Expr]

Lazily evaluated values are evaluated in *note annotation scope: 16e,
which means that names that appear inside the lazily evaluated value are
looked up as if they were used in the immediately enclosing scope.

在 3.12 版被加入.


File: python.info,  Node: Builtins and restricted execution,  Next: Interaction with dynamic features,  Prev: Lazy evaluation,  Up: Naming and binding

4.4.2.5 Builtins and restricted execution
.........................................

'CPython 實作細節：' Users should not touch ‘__builtins__’; it is
strictly an implementation detail.  Users wanting to override values in
the builtins namespace should *note import: 586. the *note builtins: e.
module and modify its attributes appropriately.

The builtins namespace associated with the execution of a code block is
actually found by looking up the name ‘__builtins__’ in its global
namespace; this should be a dictionary or a module (in the latter case
the module's dictionary is used).  By default, when in the *note
__main__: 1. module, ‘__builtins__’ is the built-in module *note
builtins: e.; when in any other module, ‘__builtins__’ is an alias for
the dictionary of the *note builtins: e. module itself.


File: python.info,  Node: Interaction with dynamic features,  Prev: Builtins and restricted execution,  Up: Naming and binding

4.4.2.6 Interaction with dynamic features
.........................................

Name resolution of free variables occurs at runtime, not at compile
time.  This means that the following code will print 42:

     i = 10
     def f():
         print(i)
     i = 42
     f()

The *note eval(): 163. and *note exec(): 162. functions do not have
access to the full environment for resolving names.  Names may be
resolved in the local and global namespaces of the caller.  Free
variables are not resolved in the nearest enclosing namespace, but in
the global namespace.  (1)  The *note exec(): 162. and *note eval():
163. functions have optional arguments to override the global and local
namespace.  If only one namespace is specified, it is used for both.

   ---------- Footnotes ----------

   (1) This limitation occurs because the code that is executed by these
operations is not available at the time the module is compiled.


File: python.info,  Node: 例外,  Prev: Naming and binding,  Up: 執行模型

4.4.3 例外
----------

Exceptions are a means of breaking out of the normal flow of control of
a code block in order to handle errors or other exceptional conditions.
An exception is 'raised' at the point where the error is detected; it
may be 'handled' by the surrounding code block or by any code block that
directly or indirectly invoked the code block where the error occurred.

The Python interpreter raises an exception when it detects a run-time
error (such as division by zero).  A Python program can also explicitly
raise an exception with the *note raise: 591. statement.  Exception
handlers are specified with the *note try: 68c. ...  *note except: 171.
statement.  The *note finally: 96e. clause of such a statement can be
used to specify cleanup code which does not handle the exception, but is
executed whether an exception occurred or not in the preceding code.

Python uses the "termination" model of error handling: an exception
handler can find out what happened and continue execution at an outer
level, but it cannot repair the cause of the error and retry the failing
operation (except by re-entering the offending piece of code from the
top).

When an exception is not handled at all, the interpreter terminates
execution of the program, or returns to its interactive main loop.  In
either case, it prints a stack traceback, except when the exception is
*note SystemExit: ce7.

Exceptions are identified by class instances.  The *note except: 171.
clause is selected depending on the class of the instance: it must
reference the class of the instance or a *note non-virtual base class:
114e. thereof.  The instance can be received by the handler and can
carry additional information about the exceptional condition.

     備註: Exception messages are not part of the Python API. Their
     contents may change from one version of Python to the next without
     warning and should not be relied on by code which will run under
     multiple versions of the interpreter.

See also the description of the *note try: 68c. statement in section
*note The try statement: 68c. and *note raise: 591. statement in section
*note raise 陳述式: 591.

註解
....


File: python.info,  Node: 模組引入系統,  Next: 運算式,  Prev: 執行模型,  Up: Python 語言參考手冊

4.5 模組引入系統
================

Python code in one *note module: 1555. gains access to the code in
another module by the process of *note importing: 1ebe. it.  The *note
import: 586. statement is the most common way of invoking the import
machinery, but it is not the only way.  Functions such as *note
importlib.import_module(): 4bc. and built-in *note __import__(): 879.
can also be used to invoke the import machinery.

The *note import: 586. statement combines two operations; it searches
for the named module, then it binds the results of that search to a name
in the local scope.  The search operation of the ‘import’ statement is
defined as a call to the *note __import__(): 879. function, with the
appropriate arguments.  The return value of *note __import__(): 879. is
used to perform the name binding operation of the ‘import’ statement.
See the ‘import’ statement for the exact details of that name binding
operation.

A direct call to *note __import__(): 879. performs only the module
search and, if found, the module creation operation.  While certain
side-effects may occur, such as the importing of parent packages, and
the updating of various caches (including *note sys.modules: 186e.),
only the *note import: 586. statement performs a name binding operation.

When an *note import: 586. statement is executed, the standard builtin
*note __import__(): 879. function is called.  Other mechanisms for
invoking the import system (such as *note importlib.import_module():
4bc.) may choose to bypass *note __import__(): 879. and use their own
solutions to implement import semantics.

When a module is first imported, Python searches for the module and if
found, it creates a module object (1), initializing it.  If the named
module cannot be found, a *note ModuleNotFoundError: aeb. is raised.
Python implements various strategies to search for the named module when
the import machinery is invoked.  These strategies can be modified and
extended by using various hooks described in the sections below.

在 3.3 版的變更: The import system has been updated to fully implement
the second phase of PEP 302(2).  There is no longer any implicit import
machinery - the full import system is exposed through *note
sys.meta_path: cd2.  In addition, native namespace package support has
been implemented (see PEP 420(3)).

* Menu:

* importlib: importlib<10>.
* 套件::
* Searching::
* Loading::
* The Path Based Finder::
* Replacing the standard import system::
* Package Relative Imports::
* Special considerations for __main__::
* References::

   ---------- Footnotes ----------

   (1) 參閱 *note types.ModuleType: db9.。

   (2) https://peps.python.org/pep-0302/

   (3) https://peps.python.org/pep-0420/


File: python.info,  Node: importlib<10>,  Next: 套件,  Up: 模組引入系統

4.5.1 ‘importlib’
-----------------

The *note importlib: 6b. module provides a rich API for interacting with
the import system.  For example *note importlib.import_module(): 4bc.
provides a recommended, simpler API than built-in *note __import__():
879. for invoking the import machinery.  Refer to the *note importlib:
6b. library documentation for additional detail.


File: python.info,  Node: 套件,  Next: Searching,  Prev: importlib<10>,  Up: 模組引入系統

4.5.2 套件
----------

Python has only one type of module object, and all modules are of this
type, regardless of whether the module is implemented in Python, C, or
something else.  To help organize modules and provide a naming
hierarchy, Python has a concept of *note packages: 1ec1.

You can think of packages as the directories on a file system and
modules as files within directories, but don't take this analogy too
literally since packages and modules need not originate from the file
system.  For the purposes of this documentation, we'll use this
convenient analogy of directories and files.  Like file system
directories, packages are organized hierarchically, and packages may
themselves contain subpackages, as well as regular modules.

It's important to keep in mind that all packages are modules, but not
all modules are packages.  Or put another way, packages are just a
special kind of module.  Specifically, any module that contains a
‘__path__’ attribute is considered a package.

All modules have a name.  Subpackage names are separated from their
parent package name by a dot, akin to Python's standard attribute access
syntax.  Thus you might have a package called *note email: 32, which in
turn has a subpackage called *note email.mime: 3c. and a module within
that subpackage called *note email.mime.text: 44.

* Menu:

* Regular packages::
* Namespace packages::


File: python.info,  Node: Regular packages,  Next: Namespace packages,  Up: 套件

4.5.2.1 Regular packages
........................

Python defines two types of packages, *note regular packages: 1ec3. and
*note namespace packages: 1b6c.  Regular packages are traditional
packages as they existed in Python 3.2 and earlier.  A regular package
is typically implemented as a directory containing an ‘__init__.py’
file.  When a regular package is imported, this ‘__init__.py’ file is
implicitly executed, and the objects it defines are bound to names in
the package's namespace.  The ‘__init__.py’ file can contain the same
Python code that any other module can contain, and Python will add some
additional attributes to the module when it is imported.

For example, the following file system layout defines a top level
‘parent’ package with three subpackages:

     parent/
         __init__.py
         one/
             __init__.py
         two/
             __init__.py
         three/
             __init__.py

Importing ‘parent.one’ will implicitly execute ‘parent/__init__.py’ and
‘parent/one/__init__.py’.  Subsequent imports of ‘parent.two’ or
‘parent.three’ will execute ‘parent/two/__init__.py’ and
‘parent/three/__init__.py’ respectively.


File: python.info,  Node: Namespace packages,  Prev: Regular packages,  Up: 套件

4.5.2.2 Namespace packages
..........................

A namespace package is a composite of various *note portions: 1ec5,
where each portion contributes a subpackage to the parent package.
Portions may reside in different locations on the file system.  Portions
may also be found in zip files, on the network, or anywhere else that
Python searches during import.  Namespace packages may or may not
correspond directly to objects on the file system; they may be virtual
modules that have no concrete representation.

Namespace packages do not use an ordinary list for their ‘__path__’
attribute.  They instead use a custom iterable type which will
automatically perform a new search for package portions on the next
import attempt within that package if the path of their parent package
(or *note sys.path: 37f. for a top level package) changes.

With namespace packages, there is no ‘parent/__init__.py’ file.  In
fact, there may be multiple ‘parent’ directories found during import
search, where each one is provided by a different portion.  Thus
‘parent/one’ may not be physically located next to ‘parent/two’.  In
this case, Python will create a namespace package for the top-level
‘parent’ package whenever it or one of its subpackages is imported.

See also PEP 420(1) for the namespace package specification.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0420/


File: python.info,  Node: Searching,  Next: Loading,  Prev: 套件,  Up: 模組引入系統

4.5.3 Searching
---------------

To begin the search, Python needs the *note fully qualified: 1843. name
of the module (or package, but for the purposes of this discussion, the
difference is immaterial) being imported.  This name may come from
various arguments to the *note import: 586. statement, or from the
parameters to the *note importlib.import_module(): 4bc. or *note
__import__(): 879. functions.

This name will be used in various phases of the import search, and it
may be the dotted path to a submodule, e.g.  ‘foo.bar.baz’.  In this
case, Python first tries to import ‘foo’, then ‘foo.bar’, and finally
‘foo.bar.baz’.  If any of the intermediate imports fail, a *note
ModuleNotFoundError: aeb. is raised.

* Menu:

* The module cache::
* Finders and loaders::
* Import hooks::
* The meta path::


File: python.info,  Node: The module cache,  Next: Finders and loaders,  Up: Searching

4.5.3.1 The module cache
........................

The first place checked during import search is *note sys.modules: 186e.
This mapping serves as a cache of all modules that have been previously
imported, including the intermediate paths.  So if ‘foo.bar.baz’ was
previously imported, *note sys.modules: 186e. will contain entries for
‘foo’, ‘foo.bar’, and ‘foo.bar.baz’.  Each key will have as its value
the corresponding module object.

During import, the module name is looked up in *note sys.modules: 186e.
and if present, the associated value is the module satisfying the
import, and the process completes.  However, if the value is ‘None’,
then a *note ModuleNotFoundError: aeb. is raised.  If the module name is
missing, Python will continue searching for the module.

*note sys.modules: 186e. is writable.  Deleting a key may not destroy
the associated module (as other modules may hold references to it), but
it will invalidate the cache entry for the named module, causing Python
to search anew for the named module upon its next import.  The key can
also be assigned to ‘None’, forcing the next import of the module to
result in a *note ModuleNotFoundError: aeb.

Beware though, as if you keep a reference to the module object,
invalidate its cache entry in *note sys.modules: 186e, and then
re-import the named module, the two module objects will 'not' be the
same.  By contrast, *note importlib.reload(): 4bd. will reuse the 'same'
module object, and simply reinitialise the module contents by rerunning
the module's code.


File: python.info,  Node: Finders and loaders,  Next: Import hooks,  Prev: The module cache,  Up: Searching

4.5.3.2 Finders and loaders
...........................

If the named module is not found in *note sys.modules: 186e, then
Python's import protocol is invoked to find and load the module.  This
protocol consists of two conceptual objects, *note finders: 1eca. and
*note loaders: 15a8.  A finder's job is to determine whether it can find
the named module using whatever strategy it knows about.  Objects that
implement both of these interfaces are referred to as *note importers:
1ecb. - they return themselves when they find that they can load the
requested module.

Python includes a number of default finders and importers.  The first
one knows how to locate built-in modules, and the second knows how to
locate frozen modules.  A third default finder searches an *note import
path: 1ecc. for modules.  The *note import path: 1ecc. is a list of
locations that may name file system paths or zip files.  It can also be
extended to search for any locatable resource, such as those identified
by URLs.

The import machinery is extensible, so new finders can be added to
extend the range and scope of module searching.

Finders do not actually load modules.  If they can find the named
module, they return a 'module spec', an encapsulation of the module's
import-related information, which the import machinery then uses when
loading the module.

The following sections describe the protocol for finders and loaders in
more detail, including how you can create and register new ones to
extend the import machinery.

在 3.4 版的變更: In previous versions of Python, finders returned *note
loaders: 15a8. directly, whereas now they return module specs which
'contain' loaders.  Loaders are still used during import but have fewer
responsibilities.


File: python.info,  Node: Import hooks,  Next: The meta path,  Prev: Finders and loaders,  Up: Searching

4.5.3.3 Import hooks
....................

The import machinery is designed to be extensible; the primary mechanism
for this are the 'import hooks'.  There are two types of import hooks:
'meta hooks' and 'import path hooks'.

Meta hooks are called at the start of import processing, before any
other import processing has occurred, other than *note sys.modules:
186e. cache look up.  This allows meta hooks to override *note sys.path:
37f. processing, frozen modules, or even built-in modules.  Meta hooks
are registered by adding new finder objects to *note sys.meta_path: cd2,
as described below.

Import path hooks are called as part of *note sys.path: 37f. (or
‘package.__path__’) processing, at the point where their associated path
item is encountered.  Import path hooks are registered by adding new
callables to *note sys.path_hooks: fc7. as described below.


File: python.info,  Node: The meta path,  Prev: Import hooks,  Up: Searching

4.5.3.4 The meta path
.....................

When the named module is not found in *note sys.modules: 186e, Python
next searches *note sys.meta_path: cd2, which contains a list of meta
path finder objects.  These finders are queried in order to see if they
know how to handle the named module.  Meta path finders must implement a
method called *note find_spec(): 80d. which takes three arguments: a
name, an import path, and (optionally) a target module.  The meta path
finder can use any strategy it wants to determine whether it can handle
the named module or not.

If the meta path finder knows how to handle the named module, it returns
a spec object.  If it cannot handle the named module, it returns ‘None’.
If *note sys.meta_path: cd2. processing reaches the end of its list
without returning a spec, then a *note ModuleNotFoundError: aeb. is
raised.  Any other exceptions raised are simply propagated up, aborting
the import process.

The *note find_spec(): 80d. method of meta path finders is called with
two or three arguments.  The first is the fully qualified name of the
module being imported, for example ‘foo.bar.baz’.  The second argument
is the path entries to use for the module search.  For top-level
modules, the second argument is ‘None’, but for submodules or
subpackages, the second argument is the value of the parent package's
‘__path__’ attribute.  If the appropriate ‘__path__’ attribute cannot be
accessed, a *note ModuleNotFoundError: aeb. is raised.  The third
argument is an existing module object that will be the target of loading
later.  The import system passes in a target module only during reload.

The meta path may be traversed multiple times for a single import
request.  For example, assuming none of the modules involved has already
been cached, importing ‘foo.bar.baz’ will first perform a top level
import, calling ‘mpf.find_spec("foo", None, None)’ on each meta path
finder (‘mpf’).  After ‘foo’ has been imported, ‘foo.bar’ will be
imported by traversing the meta path a second time, calling
‘mpf.find_spec("foo.bar", foo.__path__, None)’.  Once ‘foo.bar’ has been
imported, the final traversal will call ‘mpf.find_spec("foo.bar.baz",
foo.bar.__path__, None)’.

Some meta path finders only support top level imports.  These importers
will always return ‘None’ when anything other than ‘None’ is passed as
the second argument.

Python's default *note sys.meta_path: cd2. has three meta path finders,
one that knows how to import built-in modules, one that knows how to
import frozen modules, and one that knows how to import modules from an
*note import path: 1ecc. (i.e.  the *note path based finder: 1ecf.).

在 3.4 版的變更: The *note find_spec(): 80d. method of meta path finders
replaced ‘find_module()’, which is now deprecated.  While it will
continue to work without change, the import machinery will try it only
if the finder does not implement *note find_spec(): 80d.

在 3.10 版的變更: Use of ‘find_module()’ by the import system now raises
*note ImportWarning: 4a2.

在 3.12 版的變更: ‘find_module()’ has been removed.  Use *note
find_spec(): 80d. instead.


File: python.info,  Node: Loading,  Next: The Path Based Finder,  Prev: Searching,  Up: 模組引入系統

4.5.4 Loading
-------------

If and when a module spec is found, the import machinery will use it
(and the loader it contains) when loading the module.  Here is an
approximation of what happens during the loading portion of import:

     module = None
     if spec.loader is not None and hasattr(spec.loader, 'create_module'):
         # It is assumed 'exec_module' will also be defined on the loader.
         module = spec.loader.create_module(spec)
     if module is None:
         module = ModuleType(spec.name)
     # The import-related module attributes get set here:
     _init_module_attrs(spec, module)

     if spec.loader is None:
         # unsupported
         raise ImportError
     if spec.origin is None and spec.submodule_search_locations is not None:
         # namespace package
         sys.modules[spec.name] = module
     elif not hasattr(spec.loader, 'exec_module'):
         module = spec.loader.load_module(spec.name)
     else:
         sys.modules[spec.name] = module
         try:
             spec.loader.exec_module(module)
         except BaseException:
             try:
                 del sys.modules[spec.name]
             except KeyError:
                 pass
             raise
     return sys.modules[spec.name]

Note the following details:

   * If there is an existing module object with the given name in *note
     sys.modules: 186e, import will have already returned it.

   * The module will exist in *note sys.modules: 186e. before the loader
     executes the module code.  This is crucial because the module code
     may (directly or indirectly) import itself; adding it to *note
     sys.modules: 186e. beforehand prevents unbounded recursion in the
     worst case and multiple loading in the best.

   * If loading fails, the failing module - and only the failing module
     - gets removed from *note sys.modules: 186e.  Any module already in
     the *note sys.modules: 186e. cache, and any module that was
     successfully loaded as a side-effect, must remain in the cache.
     This contrasts with reloading where even the failing module is left
     in *note sys.modules: 186e.

   * After the module is created but before execution, the import
     machinery sets the import-related module attributes
     ("_init_module_attrs" in the pseudo-code example above), as
     summarized in a *note later section: 1ed1.

   * Module execution is the key moment of loading in which the module's
     namespace gets populated.  Execution is entirely delegated to the
     loader, which gets to decide what gets populated and how.

   * The module created during loading and passed to exec_module() may
     not be the one returned at the end of import (1).

在 3.4 版的變更: The import system has taken over the boilerplate
responsibilities of loaders.  These were previously performed by the
*note importlib.abc.Loader.load_module(): 80e. method.

* Menu:

* Loaders::
* 子模組::
* Module spec::
* Import-related module attributes::
* module.__path__: module __path__.
* Module reprs::
* Cached bytecode invalidation::

   ---------- Footnotes ----------

   (1) The importlib implementation avoids using the return value
directly.  Instead, it gets the module object by looking the module name
up in *note sys.modules: 186e.  The indirect effect of this is that an
imported module may replace itself in *note sys.modules: 186e.  This is
implementation-specific behavior that is not guaranteed to work in other
Python implementations.


File: python.info,  Node: Loaders,  Next: 子模組,  Up: Loading

4.5.4.1 Loaders
...............

Module loaders provide the critical function of loading: module
execution.  The import machinery calls the *note
importlib.abc.Loader.exec_module(): 80f. method with a single argument,
the module object to execute.  Any value returned from *note
exec_module(): 80f. is ignored.

Loaders must satisfy the following requirements:

   * If the module is a Python module (as opposed to a built-in module
     or a dynamically loaded extension), the loader should execute the
     module's code in the module's global name space
     (‘module.__dict__’).

   * If the loader cannot execute the module, it should raise an *note
     ImportError: 352, although any other exception raised during *note
     exec_module(): 80f. will be propagated.

In many cases, the finder and loader can be the same object; in such
cases the *note find_spec(): 80d. method would just return a spec with
the loader set to ‘self’.

Module loaders may opt in to creating the module object during loading
by implementing a *note create_module(): c55. method.  It takes one
argument, the module spec, and returns the new module object to use
during loading.  ‘create_module()’ does not need to set any attributes
on the module object.  If the method returns ‘None’, the import
machinery will create the new module itself.

在 3.4 版被加入: The *note create_module(): c55. method of loaders.

在 3.4 版的變更: The *note load_module(): 80e. method was replaced by
*note exec_module(): 80f. and the import machinery assumed all the
boilerplate responsibilities of loading.

For compatibility with existing loaders, the import machinery will use
the ‘load_module()’ method of loaders if it exists and the loader does
not also implement ‘exec_module()’.  However, ‘load_module()’ has been
deprecated and loaders should implement ‘exec_module()’ instead.

The ‘load_module()’ method must implement all the boilerplate loading
functionality described above in addition to executing the module.  All
the same constraints apply, with some additional clarification:

   * If there is an existing module object with the given name in *note
     sys.modules: 186e, the loader must use that existing module.
     (Otherwise, *note importlib.reload(): 4bd. will not work
     correctly.)  If the named module does not exist in *note
     sys.modules: 186e, the loader must create a new module object and
     add it to *note sys.modules: 186e.

   * The module 'must' exist in *note sys.modules: 186e. before the
     loader executes the module code, to prevent unbounded recursion or
     multiple loading.

   * If loading fails, the loader must remove any modules it has
     inserted into *note sys.modules: 186e, but it must remove 'only'
     the failing module(s), and only if the loader itself has loaded the
     module(s) explicitly.

在 3.5 版的變更: A *note DeprecationWarning: 18b. is raised when
‘exec_module()’ is defined but ‘create_module()’ is not.

在 3.6 版的變更: An *note ImportError: 352. is raised when
‘exec_module()’ is defined but ‘create_module()’ is not.

在 3.10 版的變更: Use of ‘load_module()’ will raise *note ImportWarning:
4a2.


File: python.info,  Node: 子模組,  Next: Module spec,  Prev: Loaders,  Up: Loading

4.5.4.2 子模組
..............

When a submodule is loaded using any mechanism (e.g.  ‘importlib’ APIs,
the ‘import’ or ‘import-from’ statements, or built-in ‘__import__()’) a
binding is placed in the parent module's namespace to the submodule
object.  For example, if package ‘spam’ has a submodule ‘foo’, after
importing ‘spam.foo’, ‘spam’ will have an attribute ‘foo’ which is bound
to the submodule.  Let's say you have the following directory structure:

     spam/
         __init__.py
         foo.py

and ‘spam/__init__.py’ has the following line in it:

     from .foo import Foo

then executing the following puts name bindings for ‘foo’ and ‘Foo’ in
the ‘spam’ module:

     >>> import spam
     >>> spam.foo
     <module 'spam.foo' from '/tmp/imports/spam/foo.py'>
     >>> spam.Foo
     <class 'spam.foo.Foo'>

Given Python's familiar name binding rules this might seem surprising,
but it's actually a fundamental feature of the import system.  The
invariant holding is that if you have ‘sys.modules['spam']’ and
‘sys.modules['spam.foo']’ (as you would after the above import), the
latter must appear as the ‘foo’ attribute of the former.


File: python.info,  Node: Module spec,  Next: Import-related module attributes,  Prev: 子模組,  Up: Loading

4.5.4.3 Module spec
...................

The import machinery uses a variety of information about each module
during import, especially before loading.  Most of the information is
common to all modules.  The purpose of a module's spec is to encapsulate
this import-related information on a per-module basis.

Using a spec during import allows state to be transferred between import
system components, e.g.  between the finder that creates the module spec
and the loader that executes it.  Most importantly, it allows the import
machinery to perform the boilerplate operations of loading, whereas
without a module spec the loader had that responsibility.

The module's spec is exposed as the ‘__spec__’ attribute on a module
object.  See *note ModuleSpec: 1d5a. for details on the contents of the
module spec.

在 3.4 版被加入.


File: python.info,  Node: Import-related module attributes,  Next: module __path__,  Prev: Module spec,  Up: Loading

4.5.4.4 Import-related module attributes
........................................

The import machinery fills in these attributes on each module object
during loading, based on the module's spec, before the loader executes
the module.

It is 'strongly' recommended that you rely on *note __spec__: 1ed6. and
its attributes instead of any of the other individual attributes listed
below.

 -- 屬性: __name__

     The ‘__name__’ attribute must be set to the fully qualified name of
     the module.  This name is used to uniquely identify the module in
     the import system.

 -- 屬性: __loader__

     The ‘__loader__’ attribute must be set to the loader object that
     the import machinery used when loading the module.  This is mostly
     for introspection, but can be used for additional loader-specific
     functionality, for example getting data associated with a loader.

     It is 'strongly' recommended that you rely on *note __spec__: 1ed6.
     instead of this attribute.

     在 3.12 版的變更: The value of ‘__loader__’ is expected to be the
     same as ‘__spec__.loader’.  The use of ‘__loader__’ is deprecated
     and slated for removal in Python 3.14.

 -- 屬性: __package__

     The module's ‘__package__’ attribute may be set.  Its value must be
     a string, but it can be the same value as its ‘__name__’.  When the
     module is a package, its ‘__package__’ value should be set to its
     ‘__name__’.  When the module is not a package, ‘__package__’ should
     be set to the empty string for top-level modules, or for
     submodules, to the parent package's name.  See PEP 366(1) for
     further details.

     This attribute is used instead of ‘__name__’ to calculate explicit
     relative imports for main modules, as defined in PEP 366(2).

     It is 'strongly' recommended that you rely on *note __spec__: 1ed6.
     instead of this attribute.

     在 3.6 版的變更: The value of ‘__package__’ is expected to be the
     same as ‘__spec__.parent’.

     在 3.10 版的變更: *note ImportWarning: 4a2. is raised if import
     falls back to ‘__package__’ instead of *note parent: 1ed7.

     在 3.12 版的變更: Raise *note DeprecationWarning: 18b. instead of
     *note ImportWarning: 4a2. when falling back to ‘__package__’.

 -- 屬性: __spec__

     The ‘__spec__’ attribute must be set to the module spec that was
     used when importing the module.  Setting ‘__spec__’ appropriately
     applies equally to *note modules initialized during interpreter
     startup: 1ed8.  The one exception is ‘__main__’, where ‘__spec__’
     is *note set to None in some cases: 1ed9.

     When ‘__spec__.parent’ is not set, ‘__package__’ is used as a
     fallback.

     在 3.4 版被加入.

     在 3.6 版的變更: ‘__spec__.parent’ is used as a fallback when
     ‘__package__’ is not defined.

 -- 屬性: __path__

     If the module is a package (either regular or namespace), the
     module object's ‘__path__’ attribute must be set.  The value must
     be iterable, but may be empty if ‘__path__’ has no further
     significance.  If ‘__path__’ is not empty, it must produce strings
     when iterated over.  More details on the semantics of ‘__path__’
     are given *note below: 1eda.

     Non-package modules should not have a ‘__path__’ attribute.

 -- 屬性: __file__

 -- 屬性: __cached__

     ‘__file__’ is optional (if set, value must be a string).  It
     indicates the pathname of the file from which the module was loaded
     (if loaded from a file), or the pathname of the shared library file
     for extension modules loaded dynamically from a shared library.  It
     might be missing for certain types of modules, such as C modules
     that are statically linked into the interpreter, and the import
     system may opt to leave it unset if it has no semantic meaning
     (e.g.  a module loaded from a database).

     If ‘__file__’ is set then the ‘__cached__’ attribute might also be
     set, which is the path to any compiled version of the code (e.g.
     byte-compiled file).  The file does not need to exist to set this
     attribute; the path can simply point to where the compiled file
     would exist (see PEP 3147(3)).

     Note that ‘__cached__’ may be set even if ‘__file__’ is not set.
     However, that scenario is quite atypical.  Ultimately, the loader
     is what makes use of the module spec provided by the finder (from
     which ‘__file__’ and ‘__cached__’ are derived).  So if a loader can
     load from a cached module but otherwise does not load from a file,
     that atypical scenario may be appropriate.

     It is 'strongly' recommended that you rely on *note __spec__: 1ed6.
     instead of ‘__cached__’.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0366/

   (2) https://peps.python.org/pep-0366/

   (3) https://peps.python.org/pep-3147/


File: python.info,  Node: module __path__,  Next: Module reprs,  Prev: Import-related module attributes,  Up: Loading

4.5.4.5 module.__path__
.......................

By definition, if a module has a ‘__path__’ attribute, it is a package.

A package's ‘__path__’ attribute is used during imports of its
subpackages.  Within the import machinery, it functions much the same as
*note sys.path: 37f, i.e.  providing a list of locations to search for
modules during import.  However, ‘__path__’ is typically much more
constrained than *note sys.path: 37f.

‘__path__’ must be an iterable of strings, but it may be empty.  The
same rules used for *note sys.path: 37f. also apply to a package's
‘__path__’, and *note sys.path_hooks: fc7. (described below) are
consulted when traversing a package's ‘__path__’.

A package's ‘__init__.py’ file may set or alter the package's ‘__path__’
attribute, and this was typically the way namespace packages were
implemented prior to PEP 420(1).  With the adoption of PEP 420(2),
namespace packages no longer need to supply ‘__init__.py’ files
containing only ‘__path__’ manipulation code; the import machinery
automatically sets ‘__path__’ correctly for the namespace package.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0420/

   (2) https://peps.python.org/pep-0420/


File: python.info,  Node: Module reprs,  Next: Cached bytecode invalidation,  Prev: module __path__,  Up: Loading

4.5.4.6 Module reprs
....................

By default, all modules have a usable repr, however depending on the
attributes set above, and in the module's spec, you can more explicitly
control the repr of module objects.

If the module has a spec (‘__spec__’), the import machinery will try to
generate a repr from it.  If that fails or there is no spec, the import
system will craft a default repr using whatever information is available
on the module.  It will try to use the ‘module.__name__’,
‘module.__file__’, and ‘module.__loader__’ as input into the repr, with
defaults for whatever information is missing.

Here are the exact rules used:

   * If the module has a ‘__spec__’ attribute, the information in the
     spec is used to generate the repr.  The "name", "loader", "origin",
     and "has_location" attributes are consulted.

   * If the module has a ‘__file__’ attribute, this is used as part of
     the module's repr.

   * If the module has no ‘__file__’ but does have a ‘__loader__’ that
     is not ‘None’, then the loader's repr is used as part of the
     module's repr.

   * Otherwise, just use the module's ‘__name__’ in the repr.

在 3.12 版的變更: Use of ‘module_repr()’, having been deprecated since
Python 3.4, was removed in Python 3.12 and is no longer called during
the resolution of a module's repr.


File: python.info,  Node: Cached bytecode invalidation,  Prev: Module reprs,  Up: Loading

4.5.4.7 Cached bytecode invalidation
....................................

Before Python loads cached bytecode from a ‘.pyc’ file, it checks
whether the cache is up-to-date with the source ‘.py’ file.  By default,
Python does this by storing the source's last-modified timestamp and
size in the cache file when writing it.  At runtime, the import system
then validates the cache file by checking the stored metadata in the
cache file against the source's metadata.

Python also supports "hash-based" cache files, which store a hash of the
source file's contents rather than its metadata.  There are two variants
of hash-based ‘.pyc’ files: checked and unchecked.  For checked
hash-based ‘.pyc’ files, Python validates the cache file by hashing the
source file and comparing the resulting hash with the hash in the cache
file.  If a checked hash-based cache file is found to be invalid, Python
regenerates it and writes a new checked hash-based cache file.  For
unchecked hash-based ‘.pyc’ files, Python simply assumes the cache file
is valid if it exists.  Hash-based ‘.pyc’ files validation behavior may
be overridden with the *note -check-hash-based-pycs: 1c32. flag.

在 3.7 版的變更: Added hash-based ‘.pyc’ files.  Previously, Python only
supported timestamp-based invalidation of bytecode caches.


File: python.info,  Node: The Path Based Finder,  Next: Replacing the standard import system,  Prev: Loading,  Up: 模組引入系統

4.5.5 The Path Based Finder
---------------------------

As mentioned previously, Python comes with several default meta path
finders.  One of these, called the *note path based finder: 1ecf. (*note
PathFinder: fc6.), searches an *note import path: 1ecc, which contains a
list of *note path entries: 1edf.  Each path entry names a location to
search for modules.

The path based finder itself doesn't know how to import anything.
Instead, it traverses the individual path entries, associating each of
them with a path entry finder that knows how to handle that particular
kind of path.

The default set of path entry finders implement all the semantics for
finding modules on the file system, handling special file types such as
Python source code (‘.py’ files), Python byte code (‘.pyc’ files) and
shared libraries (e.g.  ‘.so’ files).  When supported by the *note
zipimport: 118. module in the standard library, the default path entry
finders also handle loading all of these file types (other than shared
libraries) from zipfiles.

Path entries need not be limited to file system locations.  They can
refer to URLs, database queries, or any other location that can be
specified as a string.

The path based finder provides additional hooks and protocols so that
you can extend and customize the types of searchable path entries.  For
example, if you wanted to support path entries as network URLs, you
could write a hook that implements HTTP semantics to find modules on the
web.  This hook (a callable) would return a *note path entry finder:
1012. supporting the protocol described below, which was then used to
get a loader for the module from the web.

A word of warning: this section and the previous both use the term
'finder', distinguishing between them by using the terms *note meta path
finder: 1011. and *note path entry finder: 1012.  These two types of
finders are very similar, support similar protocols, and function in
similar ways during the import process, but it's important to keep in
mind that they are subtly different.  In particular, meta path finders
operate at the beginning of the import process, as keyed off the *note
sys.meta_path: cd2. traversal.

By contrast, path entry finders are in a sense an implementation detail
of the path based finder, and in fact, if the path based finder were to
be removed from *note sys.meta_path: cd2, none of the path entry finder
semantics would be invoked.

* Menu:

* Path entry finders::
* Path entry finder protocol::


File: python.info,  Node: Path entry finders,  Next: Path entry finder protocol,  Up: The Path Based Finder

4.5.5.1 Path entry finders
..........................

The *note path based finder: 1ecf. is responsible for finding and
loading Python modules and packages whose location is specified with a
string *note path entry: 1edf.  Most path entries name locations in the
file system, but they need not be limited to this.

As a meta path finder, the *note path based finder: 1ecf. implements the
*note find_spec(): 80d. protocol previously described, however it
exposes additional hooks that can be used to customize how modules are
found and loaded from the *note import path: 1ecc.

Three variables are used by the *note path based finder: 1ecf, *note
sys.path: 37f, *note sys.path_hooks: fc7. and *note
sys.path_importer_cache: 588.  The ‘__path__’ attributes on package
objects are also used.  These provide additional ways that the import
machinery can be customized.

*note sys.path: 37f. contains a list of strings providing search
locations for modules and packages.  It is initialized from the *note
PYTHONPATH: fbe. environment variable and various other installation-
and implementation-specific defaults.  Entries in *note sys.path: 37f.
can name directories on the file system, zip files, and potentially
other "locations" (see the *note site: b5. module) that should be
searched for modules, such as URLs, or database queries.  Only strings
should be present on *note sys.path: 37f.; all other data types are
ignored.

The *note path based finder: 1ecf. is a *note meta path finder: 1011, so
the import machinery begins the *note import path: 1ecc. search by
calling the path based finder's *note find_spec(): fb2. method as
described previously.  When the ‘path’ argument to *note find_spec():
fb2. is given, it will be a list of string paths to traverse - typically
a package's ‘__path__’ attribute for an import within that package.  If
the ‘path’ argument is ‘None’, this indicates a top level import and
*note sys.path: 37f. is used.

The path based finder iterates over every entry in the search path, and
for each of these, looks for an appropriate *note path entry finder:
1012. (*note PathEntryFinder: 814.) for the path entry.  Because this
can be an expensive operation (e.g.  there may be ‘stat()’ call
overheads for this search), the path based finder maintains a cache
mapping path entries to path entry finders.  This cache is maintained in
*note sys.path_importer_cache: 588. (despite the name, this cache
actually stores finder objects rather than being limited to *note
importer: 1ecb. objects).  In this way, the expensive search for a
particular *note path entry: 1edf. location's *note path entry finder:
1012. need only be done once.  User code is free to remove cache entries
from *note sys.path_importer_cache: 588. forcing the path based finder
to perform the path entry search again.

If the path entry is not present in the cache, the path based finder
iterates over every callable in *note sys.path_hooks: fc7.  Each of the
*note path entry hooks: 1ee1. in this list is called with a single
argument, the path entry to be searched.  This callable may either
return a *note path entry finder: 1012. that can handle the path entry,
or it may raise *note ImportError: 352.  An *note ImportError: 352. is
used by the path based finder to signal that the hook cannot find a
*note path entry finder: 1012. for that *note path entry: 1edf.  The
exception is ignored and *note import path: 1ecc. iteration continues.
The hook should expect either a string or bytes object; the encoding of
bytes objects is up to the hook (e.g.  it may be a file system encoding,
UTF-8, or something else), and if the hook cannot decode the argument,
it should raise *note ImportError: 352.

If *note sys.path_hooks: fc7. iteration ends with no *note path entry
finder: 1012. being returned, then the path based finder's *note
find_spec(): fb2. method will store ‘None’ in *note
sys.path_importer_cache: 588. (to indicate that there is no finder for
this path entry) and return ‘None’, indicating that this *note meta path
finder: 1011. could not find the module.

If a *note path entry finder: 1012. 'is' returned by one of the *note
path entry hook: 1ee1. callables on *note sys.path_hooks: fc7, then the
following protocol is used to ask the finder for a module spec, which is
then used when loading the module.

The current working directory - denoted by an empty string - is handled
slightly differently from other entries on *note sys.path: 37f.  First,
if the current working directory is found to not exist, no value is
stored in *note sys.path_importer_cache: 588.  Second, the value for the
current working directory is looked up fresh for each module lookup.
Third, the path used for *note sys.path_importer_cache: 588. and
returned by *note importlib.machinery.PathFinder.find_spec(): fb2. will
be the actual current working directory and not the empty string.


File: python.info,  Node: Path entry finder protocol,  Prev: Path entry finders,  Up: The Path Based Finder

4.5.5.2 Path entry finder protocol
..................................

In order to support imports of modules and initialized packages and also
to contribute portions to namespace packages, path entry finders must
implement the *note find_spec(): 811. method.

*note find_spec(): 811. takes two arguments: the fully qualified name of
the module being imported, and the (optional) target module.
‘find_spec()’ returns a fully populated spec for the module.  This spec
will always have "loader" set (with one exception).

To indicate to the import machinery that the spec represents a namespace
*note portion: 1ec5, the path entry finder sets
‘submodule_search_locations’ to a list containing the portion.

在 3.4 版的變更: *note find_spec(): 811. replaced ‘find_loader()’ and
‘find_module()’, both of which are now deprecated, but will be used if
‘find_spec()’ is not defined.

Older path entry finders may implement one of these two deprecated
methods instead of ‘find_spec()’.  The methods are still respected for
the sake of backward compatibility.  However, if ‘find_spec()’ is
implemented on the path entry finder, the legacy methods are ignored.

‘find_loader()’ takes one argument, the fully qualified name of the
module being imported.  ‘find_loader()’ returns a 2-tuple where the
first item is the loader and the second item is a namespace *note
portion: 1ec5.

For backwards compatibility with other implementations of the import
protocol, many path entry finders also support the same, traditional
‘find_module()’ method that meta path finders support.  However path
entry finder ‘find_module()’ methods are never called with a ‘path’
argument (they are expected to record the appropriate path information
from the initial call to the path hook).

The ‘find_module()’ method on path entry finders is deprecated, as it
does not allow the path entry finder to contribute portions to namespace
packages.  If both ‘find_loader()’ and ‘find_module()’ exist on a path
entry finder, the import system will always call ‘find_loader()’ in
preference to ‘find_module()’.

在 3.10 版的變更: Calls to ‘find_module()’ and ‘find_loader()’ by the
import system will raise *note ImportWarning: 4a2.

在 3.12 版的變更: ‘find_module()’ and ‘find_loader()’ have been removed.


File: python.info,  Node: Replacing the standard import system,  Next: Package Relative Imports,  Prev: The Path Based Finder,  Up: 模組引入系統

4.5.6 Replacing the standard import system
------------------------------------------

The most reliable mechanism for replacing the entire import system is to
delete the default contents of *note sys.meta_path: cd2, replacing them
entirely with a custom meta path hook.

If it is acceptable to only alter the behaviour of import statements
without affecting other APIs that access the import system, then
replacing the builtin *note __import__(): 879. function may be
sufficient.  This technique may also be employed at the module level to
only alter the behaviour of import statements within that module.

To selectively prevent the import of some modules from a hook early on
the meta path (rather than disabling the standard import system
entirely), it is sufficient to raise *note ModuleNotFoundError: aeb.
directly from *note find_spec(): 80d. instead of returning ‘None’.  The
latter indicates that the meta path search should continue, while
raising an exception terminates it immediately.


File: python.info,  Node: Package Relative Imports,  Next: Special considerations for __main__,  Prev: Replacing the standard import system,  Up: 模組引入系統

4.5.7 Package Relative Imports
------------------------------

Relative imports use leading dots.  A single leading dot indicates a
relative import, starting with the current package.  Two or more leading
dots indicate a relative import to the parent(s) of the current package,
one level per dot after the first.  For example, given the following
package layout:

     package/
         __init__.py
         subpackage1/
             __init__.py
             moduleX.py
             moduleY.py
         subpackage2/
             __init__.py
             moduleZ.py
         moduleA.py

In either ‘subpackage1/moduleX.py’ or ‘subpackage1/__init__.py’, the
following are valid relative imports:

     from .moduleY import spam
     from .moduleY import spam as ham
     from . import moduleY
     from ..subpackage1 import moduleY
     from ..subpackage2.moduleZ import eggs
     from ..moduleA import foo

Absolute imports may use either the ‘import <>’ or ‘from <> import <>’
syntax, but relative imports may only use the second form; the reason
for this is that:

     import XXX.YYY.ZZZ

should expose ‘XXX.YYY.ZZZ’ as a usable expression, but .moduleY is not
a valid expression.


File: python.info,  Node: Special considerations for __main__,  Next: References,  Prev: Package Relative Imports,  Up: 模組引入系統

4.5.8 Special considerations for __main__
-----------------------------------------

The *note __main__: 1. module is a special case relative to Python's
import system.  As noted *note elsewhere: 1ed8, the ‘__main__’ module is
directly initialized at interpreter startup, much like *note sys: c3.
and *note builtins: e.  However, unlike those two, it doesn't strictly
qualify as a built-in module.  This is because the manner in which
‘__main__’ is initialized depends on the flags and other options with
which the interpreter is invoked.

* Menu:

* __main__.__spec__: __main__ __spec__.


File: python.info,  Node: __main__ __spec__,  Up: Special considerations for __main__

4.5.8.1 __main__.__spec__
.........................

Depending on how *note __main__: 1. is initialized, ‘__main__.__spec__’
gets set appropriately or to ‘None’.

When Python is started with the *note -m: 585. option, ‘__spec__’ is set
to the module spec of the corresponding module or package.  ‘__spec__’
is also populated when the ‘__main__’ module is loaded as part of
executing a directory, zipfile or other *note sys.path: 37f. entry.

In *note the remaining cases: 1c2b. ‘__main__.__spec__’ is set to
‘None’, as the code used to populate the *note __main__: 1. does not
correspond directly with an importable module:

   - interactive prompt

   - *note -c: 584. 選項

   - running from stdin

   - running directly from a source or bytecode file

Note that ‘__main__.__spec__’ is always ‘None’ in the last case, 'even
if' the file could technically be imported directly as a module instead.
Use the *note -m: 585. switch if valid module metadata is desired in
*note __main__: 1.

Note also that even when ‘__main__’ corresponds with an importable
module and ‘__main__.__spec__’ is set accordingly, they're still
considered 'distinct' modules.  This is due to the fact that blocks
guarded by ‘if __name__ == "__main__":’ checks only execute when the
module is used to populate the ‘__main__’ namespace, and not during
normal import.


File: python.info,  Node: References,  Prev: Special considerations for __main__,  Up: 模組引入系統

4.5.9 References
----------------

The import machinery has evolved considerably since Python's early days.
The original specification for packages(1) is still available to read,
although some details have changed since the writing of that document.

The original specification for *note sys.meta_path: cd2. was PEP 302(2),
with subsequent extension in PEP 420(3).

PEP 420(4) introduced *note namespace packages: 1b6c. for Python 3.3.
PEP 420(5) also introduced the ‘find_loader()’ protocol as an
alternative to ‘find_module()’.

PEP 366(6) describes the addition of the ‘__package__’ attribute for
explicit relative imports in main modules.

PEP 328(7) introduced absolute and explicit relative imports and
initially proposed ‘__name__’ for semantics PEP 366(8) would eventually
specify for ‘__package__’.

PEP 338(9) defines executing modules as scripts.

PEP 451(10) adds the encapsulation of per-module import state in spec
objects.  It also off-loads most of the boilerplate responsibilities of
loaders back onto the import machinery.  These changes allow the
deprecation of several APIs in the import system and also addition of
new methods to finders and loaders.

註解
....

   ---------- Footnotes ----------

   (1) https://www.python.org/doc/essays/packages/

   (2) https://peps.python.org/pep-0302/

   (3) https://peps.python.org/pep-0420/

   (4) https://peps.python.org/pep-0420/

   (5) https://peps.python.org/pep-0420/

   (6) https://peps.python.org/pep-0366/

   (7) https://peps.python.org/pep-0328/

   (8) https://peps.python.org/pep-0366/

   (9) https://peps.python.org/pep-0338/

   (10) https://peps.python.org/pep-0451/


File: python.info,  Node: 運算式,  Next: 簡單陳述式,  Prev: 模組引入系統,  Up: Python 語言參考手冊

4.6 運算式
==========

This chapter explains the meaning of the elements of expressions in
Python.

'Syntax Notes:' In this and the following chapters, extended BNF
notation will be used to describe syntax, not lexical analysis.  When
(one alternative of) a syntax rule has the form

     name ::= othername

and no semantics are given, the semantics of this form of ‘name’ are the
same as for ‘othername’.

* Menu:

* Arithmetic conversions::
* Atoms::
* Primaries::
* Await expression::
* The power operator::
* Unary arithmetic and bitwise operations::
* Binary arithmetic operations::
* Shifting operations::
* Binary bitwise operations::
* Comparisons::
* Boolean operations::
* Assignment expressions: Assignment expressions<2>.
* Conditional expressions::
* Lambdas::
* Expression lists::
* Evaluation order::
* Operator precedence::


File: python.info,  Node: Arithmetic conversions,  Next: Atoms,  Up: 運算式

4.6.1 Arithmetic conversions
----------------------------

When a description of an arithmetic operator below uses the phrase "the
numeric arguments are converted to a common type", this means that the
operator implementation for built-in types works as follows:

   * If either argument is a complex number, the other is converted to
     complex;

   * otherwise, if either argument is a floating-point number, the other
     is converted to floating point;

   * otherwise, both must be integers and no conversion is necessary.

Some additional rules apply for certain operators (e.g., a string as a
left argument to the '%' operator).  Extensions must define their own
conversion behavior.


File: python.info,  Node: Atoms,  Next: Primaries,  Prev: Arithmetic conversions,  Up: 運算式

4.6.2 Atoms
-----------

Atoms are the most basic elements of expressions.  The simplest atoms
are identifiers or literals.  Forms enclosed in parentheses, brackets or
braces are also categorized syntactically as atoms.  The syntax for
atoms is:

     atom      ::= identifier | literal | enclosure
     enclosure ::= parenth_form | list_display | dict_display | set_display
                   | generator_expression | yield_atom

* Menu:

* Identifiers (Names): Identifiers Names.
* Literals: Literals<2>.
* Parenthesized forms::
* Displays for lists, sets and dictionaries: Displays for lists sets and dictionaries.
* List displays::
* Set displays::
* Dictionary displays::
* Generator expressions::
* Yield expressions::


File: python.info,  Node: Identifiers Names,  Next: Literals<2>,  Up: Atoms

4.6.2.1 Identifiers (Names)
...........................

An identifier occurring as an atom is a name.  See section *note
Identifiers and keywords: 1d86. for lexical definition and section *note
Naming and binding: 1de9. for documentation of naming and binding.

When the name is bound to an object, evaluation of the atom yields that
object.  When a name is not bound, an attempt to evaluate it raises a
*note NameError: 3e5. exception.

* Menu:

* Private name mangling::


File: python.info,  Node: Private name mangling,  Up: Identifiers Names

4.6.2.2 Private name mangling
.............................

When an identifier that textually occurs in a class definition begins
with two or more underscore characters and does not end in two or more
underscores, it is considered a 'private name' of that class.

也參考
......

The *note class specifications: 126a.

More precisely, private names are transformed to a longer form before
code is generated for them.  If the transformed name is longer than 255
characters, implementation-defined truncation may happen.

The transformation is independent of the syntactical context in which
the identifier is used but only the following private identifiers are
mangled:

   - Any name used as the name of a variable that is assigned or read or
     any name of an attribute being accessed.

     The ‘__name__’ attribute of nested functions, classes, and type
     aliases is however not mangled.

   - The name of imported modules, e.g., ‘__spam’ in ‘import __spam’.
     If the module is part of a package (i.e., its name contains a dot),
     the name is 'not' mangled, e.g., the ‘__foo’ in ‘import __foo.bar’
     is not mangled.

   - The name of an imported member, e.g., ‘__f’ in ‘from spam import
     __f’.

The transformation rule is defined as follows:

   - The class name, with leading underscores removed and a single
     leading underscore inserted, is inserted in front of the
     identifier, e.g., the identifier ‘__spam’ occurring in a class
     named ‘Foo’, ‘_Foo’ or ‘__Foo’ is transformed to ‘_Foo__spam’.

   - If the class name consists only of underscores, the transformation
     is the identity, e.g., the identifier ‘__spam’ occurring in a class
     named ‘_’ or ‘__’ is left as is.


File: python.info,  Node: Literals<2>,  Next: Parenthesized forms,  Prev: Identifiers Names,  Up: Atoms

4.6.2.3 Literals
................

Python supports string and bytes literals and various numeric literals:

     literal ::= stringliteral | bytesliteral
                 | integer | floatnumber | imagnumber

Evaluation of a literal yields an object of the given type (string,
bytes, integer, floating-point number, complex number) with the given
value.  The value may be approximated in the case of floating-point and
imaginary (complex) literals.  See section *note Literals: 1d94. for
details.

All literals correspond to immutable data types, and hence the object's
identity is less important than its value.  Multiple evaluations of
literals with the same value (either the same occurrence in the program
text or a different occurrence) may obtain the same object or a
different object with the same value.


File: python.info,  Node: Parenthesized forms,  Next: Displays for lists sets and dictionaries,  Prev: Literals<2>,  Up: Atoms

4.6.2.4 Parenthesized forms
...........................

A parenthesized form is an optional expression list enclosed in
parentheses:

     parenth_form ::= "(" [starred_expression] ")"

A parenthesized expression list yields whatever that expression list
yields: if the list contains at least one comma, it yields a tuple;
otherwise, it yields the single expression that makes up the expression
list.

An empty pair of parentheses yields an empty tuple object.  Since tuples
are immutable, the same rules as for literals apply (i.e., two
occurrences of the empty tuple may or may not yield the same object).

Note that tuples are not formed by the parentheses, but rather by use of
the comma.  The exception is the empty tuple, for which parentheses
'are' required -- allowing unparenthesized "nothing" in expressions
would cause ambiguities and allow common typos to pass uncaught.


File: python.info,  Node: Displays for lists sets and dictionaries,  Next: List displays,  Prev: Parenthesized forms,  Up: Atoms

4.6.2.5 Displays for lists, sets and dictionaries
.................................................

For constructing a list, a set or a dictionary Python provides special
syntax called "displays", each of them in two flavors:

   * either the container contents are listed explicitly, or

   * they are computed via a set of looping and filtering instructions,
     called a 'comprehension'.

Common syntax elements for comprehensions are:

     comprehension ::= assignment_expression comp_for
     comp_for      ::= ["async"] "for" target_list "in" or_test [comp_iter]
     comp_iter     ::= comp_for | comp_if
     comp_if       ::= "if" or_test [comp_iter]

The comprehension consists of a single expression followed by at least
one ‘for’ clause and zero or more ‘for’ or ‘if’ clauses.  In this case,
the elements of the new container are those that would be produced by
considering each of the ‘for’ or ‘if’ clauses a block, nesting from left
to right, and evaluating the expression to produce an element each time
the innermost block is reached.

However, aside from the iterable expression in the leftmost ‘for’
clause, the comprehension is executed in a separate implicitly nested
scope.  This ensures that names assigned to in the target list don't
"leak" into the enclosing scope.

The iterable expression in the leftmost ‘for’ clause is evaluated
directly in the enclosing scope and then passed as an argument to the
implicitly nested scope.  Subsequent ‘for’ clauses and any filter
condition in the leftmost ‘for’ clause cannot be evaluated in the
enclosing scope as they may depend on the values obtained from the
leftmost iterable.  For example: ‘[x*y for x in range(10) for y in
range(x, x+10)]’.

To ensure the comprehension always results in a container of the
appropriate type, ‘yield’ and ‘yield from’ expressions are prohibited in
the implicitly nested scope.

Since Python 3.6, in an *note async def: 575. function, an ‘async for’
clause may be used to iterate over a *note asynchronous iterator: 191.
A comprehension in an ‘async def’ function may consist of either a ‘for’
or ‘async for’ clause following the leading expression, may contain
additional ‘for’ or ‘async for’ clauses, and may also use *note await:
19f. expressions.

If a comprehension contains ‘async for’ clauses, or if it contains
‘await’ expressions or other asynchronous comprehensions anywhere except
the iterable expression in the leftmost ‘for’ clause, it is called an
'asynchronous comprehension'.  An asynchronous comprehension may suspend
the execution of the coroutine function in which it appears.  See also
PEP 530(1).

在 3.6 版被加入: Asynchronous comprehensions were introduced.

在 3.8 版的變更: ‘yield’ and ‘yield from’ prohibited in the implicitly
nested scope.

在 3.11 版的變更: Asynchronous comprehensions are now allowed inside
comprehensions in asynchronous functions.  Outer comprehensions
implicitly become asynchronous.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0530/


File: python.info,  Node: List displays,  Next: Set displays,  Prev: Displays for lists sets and dictionaries,  Up: Atoms

4.6.2.6 List displays
.....................

A list display is a possibly empty series of expressions enclosed in
square brackets:

     list_display ::= "[" [starred_list | comprehension] "]"

A list display yields a new list object, the contents being specified by
either a list of expressions or a comprehension.  When a comma-separated
list of expressions is supplied, its elements are evaluated from left to
right and placed into the list object in that order.  When a
comprehension is supplied, the list is constructed from the elements
resulting from the comprehension.


File: python.info,  Node: Set displays,  Next: Dictionary displays,  Prev: List displays,  Up: Atoms

4.6.2.7 Set displays
....................

A set display is denoted by curly braces and distinguishable from
dictionary displays by the lack of colons separating keys and values:

     set_display ::= "{" (starred_list | comprehension) "}"

A set display yields a new mutable set object, the contents being
specified by either a sequence of expressions or a comprehension.  When
a comma-separated list of expressions is supplied, its elements are
evaluated from left to right and added to the set object.  When a
comprehension is supplied, the set is constructed from the elements
resulting from the comprehension.

An empty set cannot be constructed with ‘{}’; this literal constructs an
empty dictionary.


File: python.info,  Node: Dictionary displays,  Next: Generator expressions,  Prev: Set displays,  Up: Atoms

4.6.2.8 Dictionary displays
...........................

A dictionary display is a possibly empty series of dict items (key/value
pairs) enclosed in curly braces:

     dict_display       ::= "{" [dict_item_list | dict_comprehension] "}"
     dict_item_list     ::= dict_item ("," dict_item)* [","]
     dict_item          ::= expression ":" expression | "**" or_expr
     dict_comprehension ::= expression ":" expression comp_for

A dictionary display yields a new dictionary object.

If a comma-separated sequence of dict items is given, they are evaluated
from left to right to define the entries of the dictionary: each key
object is used as a key into the dictionary to store the corresponding
value.  This means that you can specify the same key multiple times in
the dict item list, and the final dictionary's value for that key will
be the last one given.

A double asterisk ‘**’ denotes 'dictionary unpacking'.  Its operand must
be a *note mapping: 1154.  Each mapping item is added to the new
dictionary.  Later values replace values already set by earlier dict
items and earlier dictionary unpackings.

在 3.5 版被加入: Unpacking into dictionary displays, originally proposed
by PEP 448(1).

A dict comprehension, in contrast to list and set comprehensions, needs
two expressions separated with a colon followed by the usual "for" and
"if" clauses.  When the comprehension is run, the resulting key and
value elements are inserted in the new dictionary in the order they are
produced.

Restrictions on the types of the key values are listed earlier in
section *note 標準型別階層: 1dd6.  (To summarize, the key type should be
*note hashable: 5b5, which excludes all mutable objects.)  Clashes
between duplicate keys are not detected; the last value (textually
rightmost in the display) stored for a given key value prevails.

在 3.8 版的變更: Prior to Python 3.8, in dict comprehensions, the
evaluation order of key and value was not well-defined.  In CPython, the
value was evaluated before the key.  Starting with 3.8, the key is
evaluated before the value, as proposed by PEP 572(2).

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0448/

   (2) https://peps.python.org/pep-0572/


File: python.info,  Node: Generator expressions,  Next: Yield expressions,  Prev: Dictionary displays,  Up: Atoms

4.6.2.9 Generator expressions
.............................

A generator expression is a compact generator notation in parentheses:

     generator_expression ::= "(" expression comp_for ")"

A generator expression yields a new generator object.  Its syntax is the
same as for comprehensions, except that it is enclosed in parentheses
instead of brackets or curly braces.

Variables used in the generator expression are evaluated lazily when the
*note __next__(): 1bc8. method is called for the generator object (in
the same fashion as normal generators).  However, the iterable
expression in the leftmost ‘for’ clause is immediately evaluated, so
that an error produced by it will be emitted at the point where the
generator expression is defined, rather than at the point where the
first value is retrieved.  Subsequent ‘for’ clauses and any filter
condition in the leftmost ‘for’ clause cannot be evaluated in the
enclosing scope as they may depend on the values obtained from the
leftmost iterable.  For example: ‘(x*y for x in range(10) for y in
range(x, x+10))’.

The parentheses can be omitted on calls with only one argument.  See
section *note Calls: d23. for details.

To avoid interfering with the expected operation of the generator
expression itself, ‘yield’ and ‘yield from’ expressions are prohibited
in the implicitly defined generator.

If a generator expression contains either ‘async for’ clauses or *note
await: 19f. expressions it is called an 'asynchronous generator
expression'.  An asynchronous generator expression returns a new
asynchronous generator object, which is an asynchronous iterator (see
*note Asynchronous Iterators: d20.).

在 3.6 版被加入: Asynchronous generator expressions were introduced.

在 3.7 版的變更: Prior to Python 3.7, asynchronous generator expressions
could only appear in *note async def: 575. coroutines.  Starting with
3.7, any function can use asynchronous generator expressions.

在 3.8 版的變更: ‘yield’ and ‘yield from’ prohibited in the implicitly
nested scope.


File: python.info,  Node: Yield expressions,  Prev: Generator expressions,  Up: Atoms

4.6.2.10 Yield expressions
..........................

     yield_atom       ::= "(" yield_expression ")"
     yield_from       ::= "yield" "from" expression
     yield_expression ::= "yield" expression_list | yield_from

The yield expression is used when defining a *note generator: 1004.
function or an *note asynchronous generator: 1f14. function and thus can
only be used in the body of a function definition.  Using a yield
expression in a function's body causes that function to be a generator
function, and using it in an *note async def: 575. function's body
causes that coroutine function to be an asynchronous generator function.
For example:

     def gen():  # defines a generator function
         yield 123

     async def agen(): # defines an asynchronous generator function
         yield 123

Due to their side effects on the containing scope, ‘yield’ expressions
are not permitted as part of the implicitly defined scopes used to
implement comprehensions and generator expressions.

在 3.8 版的變更: Yield expressions prohibited in the implicitly nested
scopes used to implement comprehensions and generator expressions.

Generator functions are described below, while asynchronous generator
functions are described separately in section *note Asynchronous
generator functions: 1f15.

When a generator function is called, it returns an iterator known as a
generator.  That generator then controls the execution of the generator
function.  The execution starts when one of the generator's methods is
called.  At that time, the execution proceeds to the first yield
expression, where it is suspended again, returning the value of *note
expression_list: 1f16. to the generator's caller, or ‘None’ if *note
expression_list: 1f16. is omitted.  By suspended, we mean that all local
state is retained, including the current bindings of local variables,
the instruction pointer, the internal evaluation stack, and the state of
any exception handling.  When the execution is resumed by calling one of
the generator's methods, the function can proceed exactly as if the
yield expression were just another external call.  The value of the
yield expression after resuming depends on the method which resumed the
execution.  If *note __next__(): 1bc8. is used (typically via either a
*note for: 2c3. or the *note next(): 77c. builtin) then the result is
*note None: 61b.  Otherwise, if *note send(): 1ea2. is used, then the
result will be the value passed in to that method.

All of this makes generator functions quite similar to coroutines; they
yield multiple times, they have more than one entry point and their
execution can be suspended.  The only difference is that a generator
function cannot control where the execution should continue after it
yields; the control is always transferred to the generator's caller.

Yield expressions are allowed anywhere in a *note try: 68c. construct.
If the generator is not resumed before it is finalized (by reaching a
zero reference count or by being garbage collected), the
generator-iterator's *note close(): 15ee. method will be called,
allowing any pending *note finally: 96e. clauses to execute.

When ‘yield from <expr>’ is used, the supplied expression must be an
iterable.  The values produced by iterating that iterable are passed
directly to the caller of the current generator's methods.  Any values
passed in with *note send(): 1ea2. and any exceptions passed in with
*note throw(): 4a0. are passed to the underlying iterator if it has the
appropriate methods.  If this is not the case, then *note send(): 1ea2.
will raise *note AttributeError: 2f6. or *note TypeError: 4dd, while
*note throw(): 4a0. will just raise the passed in exception immediately.

When the underlying iterator is complete, the *note value: 1e9f.
attribute of the raised *note StopIteration: ba1. instance becomes the
value of the yield expression.  It can be either set explicitly when
raising *note StopIteration: ba1, or automatically when the subiterator
is a generator (by returning a value from the subgenerator).

在 3.3 版的變更: Added ‘yield from <expr>’ to delegate control flow to a
subiterator.

The parentheses may be omitted when the yield expression is the sole
expression on the right hand side of an assignment statement.

也參考
......

PEP 255(1) - Simple Generators

     The proposal for adding generators and the *note yield: 971.
     statement to Python.

PEP 342(2) - Coroutines via Enhanced Generators

     The proposal to enhance the API and syntax of generators, making
     them usable as simple coroutines.

PEP 380(3) - Syntax for Delegating to a Subgenerator

     The proposal to introduce the *note yield_from: 1f12. syntax,
     making delegation to subgenerators easy.

PEP 525(4) - Asynchronous Generators

     The proposal that expanded on PEP 492(5) by adding generator
     capabilities to coroutine functions.

* Menu:

* Generator-iterator methods::
* 模組: 模組<3>.
* Asynchronous generator functions: Asynchronous generator functions<2>.
* Asynchronous generator-iterator methods::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0255/

   (2) https://peps.python.org/pep-0342/

   (3) https://peps.python.org/pep-0380/

   (4) https://peps.python.org/pep-0525/

   (5) https://peps.python.org/pep-0492/


File: python.info,  Node: Generator-iterator methods,  Next: 模組<3>,  Up: Yield expressions

4.6.2.11 Generator-iterator methods
...................................

This subsection describes the methods of a generator iterator.  They can
be used to control the execution of a generator function.

Note that calling any of the generator methods below when the generator
is already executing raises a *note ValueError: 1e7. exception.

 -- 方法: generator.__next__ ()

     Starts the execution of a generator function or resumes it at the
     last executed yield expression.  When a generator function is
     resumed with a *note __next__(): 1bc8. method, the current yield
     expression always evaluates to *note None: 61b.  The execution then
     continues to the next yield expression, where the generator is
     suspended again, and the value of the *note expression_list: 1f16.
     is returned to *note __next__(): 1bc8.'s caller.  If the generator
     exits without yielding another value, a *note StopIteration: ba1.
     exception is raised.

     This method is normally called implicitly, e.g.  by a *note for:
     2c3. loop, or by the built-in *note next(): 77c. function.

 -- 方法: generator.send (value)

     Resumes the execution and "sends" a value into the generator
     function.  The 'value' argument becomes the result of the current
     yield expression.  The *note send(): 1ea2. method returns the next
     value yielded by the generator, or raises *note StopIteration: ba1.
     if the generator exits without yielding another value.  When *note
     send(): 1ea2. is called to start the generator, it must be called
     with *note None: 61b. as the argument, because there is no yield
     expression that could receive the value.

 -- 方法: generator.throw (value)

 -- 方法: generator.throw (type[, value[, traceback]])

     Raises an exception at the point where the generator was paused,
     and returns the next value yielded by the generator function.  If
     the generator exits without yielding another value, a *note
     StopIteration: ba1. exception is raised.  If the generator function
     does not catch the passed-in exception, or raises a different
     exception, then that exception propagates to the caller.

     In typical use, this is called with a single exception instance
     similar to the way the *note raise: 591. keyword is used.

     For backwards compatibility, however, the second signature is
     supported, following a convention from older versions of Python.
     The 'type' argument should be an exception class, and 'value'
     should be an exception instance.  If the 'value' is not provided,
     the 'type' constructor is called to get an instance.  If
     'traceback' is provided, it is set on the exception, otherwise any
     existing *note __traceback__: 125b. attribute stored in 'value' may
     be cleared.

     在 3.12 版的變更: The second signature (type[, value[, traceback]])
     is deprecated and may be removed in a future version of Python.

 -- 方法: generator.close ()

     Raises a *note GeneratorExit: 1335. at the point where the
     generator function was paused.  If the generator function catches
     the exception and returns a value, this value is returned from
     *note close(): 15ee.  If the generator function is already closed,
     or raises *note GeneratorExit: 1335. (by not catching the
     exception), *note close(): 15ee. returns *note None: 61b.  If the
     generator yields a value, a *note RuntimeError: 179. is raised.  If
     the generator raises any other exception, it is propagated to the
     caller.  If the generator has already exited due to an exception or
     normal exit, *note close(): 15ee. returns *note None: 61b. and has
     no other effect.

     在 3.13 版的變更: If a generator returns a value upon being closed,
     the value is returned by *note close(): 15ee.


File: python.info,  Node: 模組<3>,  Next: Asynchronous generator functions<2>,  Prev: Generator-iterator methods,  Up: Yield expressions

4.6.2.12 模組
.............

Here is a simple example that demonstrates the behavior of generators
and generator functions:

     >>> def echo(value=None):
     ...     print("Execution starts when 'next()' is called for the first time.")
     ...     try:
     ...         while True:
     ...             try:
     ...                 value = (yield value)
     ...             except Exception as e:
     ...                 value = e
     ...     finally:
     ...         print("Don't forget to clean up when 'close()' is called.")
     ...
     >>> generator = echo(1)
     >>> print(next(generator))
     Execution starts when 'next()' is called for the first time.
     1
     >>> print(next(generator))
     None
     >>> print(generator.send(2))
     2
     >>> generator.throw(TypeError, "spam")
     TypeError('spam',)
     >>> generator.close()
     Don't forget to clean up when 'close()' is called.

For examples using ‘yield from’, see *note PEP 380; Syntax for
Delegating to a Subgenerator: fdc. in "What's New in Python."


File: python.info,  Node: Asynchronous generator functions<2>,  Next: Asynchronous generator-iterator methods,  Prev: 模組<3>,  Up: Yield expressions

4.6.2.13 Asynchronous generator functions
.........................................

The presence of a yield expression in a function or method defined using
*note async def: 575. further defines the function as an *note
asynchronous generator: 1f14. function.

When an asynchronous generator function is called, it returns an
asynchronous iterator known as an asynchronous generator object.  That
object then controls the execution of the generator function.  An
asynchronous generator object is typically used in an *note async for:
a4e. statement in a coroutine function analogously to how a generator
object would be used in a *note for: 2c3. statement.

Calling one of the asynchronous generator's methods returns an *note
awaitable: 193. object, and the execution starts when this object is
awaited on.  At that time, the execution proceeds to the first yield
expression, where it is suspended again, returning the value of *note
expression_list: 1f16. to the awaiting coroutine.  As with a generator,
suspension means that all local state is retained, including the current
bindings of local variables, the instruction pointer, the internal
evaluation stack, and the state of any exception handling.  When the
execution is resumed by awaiting on the next object returned by the
asynchronous generator's methods, the function can proceed exactly as if
the yield expression were just another external call.  The value of the
yield expression after resuming depends on the method which resumed the
execution.  If *note __anext__(): 1f1a. is used then the result is *note
None: 61b.  Otherwise, if *note asend(): 87e. is used, then the result
will be the value passed in to that method.

If an asynchronous generator happens to exit early by *note break: a4c,
the caller task being cancelled, or other exceptions, the generator's
async cleanup code will run and possibly raise exceptions or access
context variables in an unexpected context-perhaps after the lifetime of
tasks it depends, or during the event loop shutdown when the
async-generator garbage collection hook is called.  To prevent this, the
caller must explicitly close the async generator by calling *note
aclose(): 87d. method to finalize the generator and ultimately detach it
from the event loop.

In an asynchronous generator function, yield expressions are allowed
anywhere in a *note try: 68c. construct.  However, if an asynchronous
generator is not resumed before it is finalized (by reaching a zero
reference count or by being garbage collected), then a yield expression
within a ‘try’ construct could result in a failure to execute pending
*note finally: 96e. clauses.  In this case, it is the responsibility of
the event loop or scheduler running the asynchronous generator to call
the asynchronous generator-iterator's *note aclose(): 87d. method and
run the resulting coroutine object, thus allowing any pending ‘finally’
clauses to execute.

To take care of finalization upon event loop termination, an event loop
should define a 'finalizer' function which takes an asynchronous
generator-iterator and presumably calls *note aclose(): 87d. and
executes the coroutine.  This 'finalizer' may be registered by calling
*note sys.set_asyncgen_hooks(): 151a.  When first iterated over, an
asynchronous generator-iterator will store the registered 'finalizer' to
be called upon finalization.  For a reference example of a 'finalizer'
method see the implementation of ‘asyncio.Loop.shutdown_asyncgens’ in
Lib/asyncio/base_events.py(1).

The expression ‘yield from <expr>’ is a syntax error when used in an
asynchronous generator function.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/asyncio/base_events.py


File: python.info,  Node: Asynchronous generator-iterator methods,  Prev: Asynchronous generator functions<2>,  Up: Yield expressions

4.6.2.14 Asynchronous generator-iterator methods
................................................

This subsection describes the methods of an asynchronous generator
iterator, which are used to control the execution of a generator
function.

 -- 方法: coroutine agen.__anext__ ()

     Returns an awaitable which when run starts to execute the
     asynchronous generator or resumes it at the last executed yield
     expression.  When an asynchronous generator function is resumed
     with an *note __anext__(): 1f1a. method, the current yield
     expression always evaluates to *note None: 61b. in the returned
     awaitable, which when run will continue to the next yield
     expression.  The value of the *note expression_list: 1f16. of the
     yield expression is the value of the *note StopIteration: ba1.
     exception raised by the completing coroutine.  If the asynchronous
     generator exits without yielding another value, the awaitable
     instead raises a *note StopAsyncIteration: 1933. exception,
     signalling that the asynchronous iteration has completed.

     This method is normally called implicitly by a *note async for:
     a4e. loop.

 -- 方法: coroutine agen.asend (value)

     Returns an awaitable which when run resumes the execution of the
     asynchronous generator.  As with the *note send(): 1ea2. method for
     a generator, this "sends" a value into the asynchronous generator
     function, and the 'value' argument becomes the result of the
     current yield expression.  The awaitable returned by the *note
     asend(): 87e. method will return the next value yielded by the
     generator as the value of the raised *note StopIteration: ba1, or
     raises *note StopAsyncIteration: 1933. if the asynchronous
     generator exits without yielding another value.  When *note
     asend(): 87e. is called to start the asynchronous generator, it
     must be called with *note None: 61b. as the argument, because there
     is no yield expression that could receive the value.

 -- 方法: coroutine agen.athrow (value)

 -- 方法: coroutine agen.athrow (type[, value[, traceback]])

     Returns an awaitable that raises an exception of type ‘type’ at the
     point where the asynchronous generator was paused, and returns the
     next value yielded by the generator function as the value of the
     raised *note StopIteration: ba1. exception.  If the asynchronous
     generator exits without yielding another value, a *note
     StopAsyncIteration: 1933. exception is raised by the awaitable.  If
     the generator function does not catch the passed-in exception, or
     raises a different exception, then when the awaitable is run that
     exception propagates to the caller of the awaitable.

     在 3.12 版的變更: The second signature (type[, value[, traceback]])
     is deprecated and may be removed in a future version of Python.

 -- 方法: coroutine agen.aclose ()

     Returns an awaitable that when run will throw a *note
     GeneratorExit: 1335. into the asynchronous generator function at
     the point where it was paused.  If the asynchronous generator
     function then exits gracefully, is already closed, or raises *note
     GeneratorExit: 1335. (by not catching the exception), then the
     returned awaitable will raise a *note StopIteration: ba1.
     exception.  Any further awaitables returned by subsequent calls to
     the asynchronous generator will raise a *note StopAsyncIteration:
     1933. exception.  If the asynchronous generator yields a value, a
     *note RuntimeError: 179. is raised by the awaitable.  If the
     asynchronous generator raises any other exception, it is propagated
     to the caller of the awaitable.  If the asynchronous generator has
     already exited due to an exception or normal exit, then further
     calls to *note aclose(): 87d. will return an awaitable that does
     nothing.


File: python.info,  Node: Primaries,  Next: Await expression,  Prev: Atoms,  Up: 運算式

4.6.3 Primaries
---------------

Primaries represent the most tightly bound operations of the language.
Their syntax is:

     primary ::= atom | attributeref | subscription | slicing | call

* Menu:

* Attribute references::
* Subscriptions::
* Slicings::
* Calls::


File: python.info,  Node: Attribute references,  Next: Subscriptions,  Up: Primaries

4.6.3.1 Attribute references
............................

An attribute reference is a primary followed by a period and a name:

     attributeref ::= primary "." identifier

The primary must evaluate to an object of a type that supports attribute
references, which most objects do.  This object is then asked to produce
the attribute whose name is the identifier.  The type and value produced
is determined by the object.  Multiple evaluations of the same attribute
reference may yield different objects.

This production can be customized by overriding the *note
__getattribute__(): b79. method or the *note __getattr__(): 47a. method.
The ‘__getattribute__()’ method is called first and either returns a
value or raises *note AttributeError: 2f6. if the attribute is not
available.

If an *note AttributeError: 2f6. is raised and the object has a
‘__getattr__()’ method, that method is called as a fallback.


File: python.info,  Node: Subscriptions,  Next: Slicings,  Prev: Attribute references,  Up: Primaries

4.6.3.2 Subscriptions
.....................

The subscription of an instance of a *note container class: 1e61. will
generally select an element from the container.  The subscription of a
*note generic class: 3df. will generally return a *note GenericAlias:
656. object.

     subscription ::= primary "[" expression_list "]"

When an object is subscripted, the interpreter will evaluate the primary
and the expression list.

The primary must evaluate to an object that supports subscription.  An
object may support subscription through defining one or both of *note
__getitem__(): 266. and *note __class_getitem__(): 6df.  When the
primary is subscripted, the evaluated result of the expression list will
be passed to one of these methods.  For more details on when
‘__class_getitem__’ is called instead of ‘__getitem__’, see *note
__class_getitem__ versus __getitem__: 1e5a.

If the expression list contains at least one comma, it will evaluate to
a *note tuple: 322. containing the items of the expression list.
Otherwise, the expression list will evaluate to the value of the list's
sole member.

For built-in objects, there are two types of objects that support
subscription via *note __getitem__(): 266.:

  1. Mappings.  If the primary is a *note mapping: 1154, the expression
     list must evaluate to an object whose value is one of the keys of
     the mapping, and the subscription selects the value in the mapping
     that corresponds to that key.  An example of a builtin mapping
     class is the *note dict: 23b. class.

  2. Sequences.  If the primary is a *note sequence: 499, the expression
     list must evaluate to an *note int: 23c. or a *note slice: 410. (as
     discussed in the following section).  Examples of builtin sequence
     classes include the *note str: 3f2, *note list: 5b6. and *note
     tuple: 322. classes.

The formal syntax makes no special provision for negative indices in
*note sequences: 499.  However, built-in sequences all provide a *note
__getitem__(): 266. method that interprets negative indices by adding
the length of the sequence to the index so that, for example, ‘x[-1]’
selects the last item of ‘x’.  The resulting value must be a nonnegative
integer less than the number of items in the sequence, and the
subscription selects the item whose index is that value (counting from
zero).  Since the support for negative indices and slicing occurs in the
object's *note __getitem__(): 266. method, subclasses overriding this
method will need to explicitly add that support.

A *note string: 3f2. is a special kind of sequence whose items are
'characters'.  A character is not a separate data type but a string of
exactly one character.


File: python.info,  Node: Slicings,  Next: Calls,  Prev: Subscriptions,  Up: Primaries

4.6.3.3 Slicings
................

A slicing selects a range of items in a sequence object (e.g., a string,
tuple or list).  Slicings may be used as expressions or as targets in
assignment or *note del: 16a9. statements.  The syntax for a slicing:

     slicing      ::= primary "[" slice_list "]"
     slice_list   ::= slice_item ("," slice_item)* [","]
     slice_item   ::= expression | proper_slice
     proper_slice ::= [lower_bound] ":" [upper_bound] [ ":" [stride] ]
     lower_bound  ::= expression
     upper_bound  ::= expression
     stride       ::= expression

There is ambiguity in the formal syntax here: anything that looks like
an expression list also looks like a slice list, so any subscription can
be interpreted as a slicing.  Rather than further complicating the
syntax, this is disambiguated by defining that in this case the
interpretation as a subscription takes priority over the interpretation
as a slicing (this is the case if the slice list contains no proper
slice).

The semantics for a slicing are as follows.  The primary is indexed
(using the same *note __getitem__(): 266. method as normal subscription)
with a key that is constructed from the slice list, as follows.  If the
slice list contains at least one comma, the key is a tuple containing
the conversion of the slice items; otherwise, the conversion of the lone
slice item is the key.  The conversion of a slice item that is an
expression is that expression.  The conversion of a proper slice is a
slice object (see section *note 標準型別階層: 1dd6.) whose *note start:
1e2b, *note stop: 1e2c. and *note step: 1e2d. attributes are the values
of the expressions given as lower bound, upper bound and stride,
respectively, substituting ‘None’ for missing expressions.


File: python.info,  Node: Calls,  Prev: Slicings,  Up: Primaries

4.6.3.4 Calls
.............

A call calls a callable object (e.g., a *note function: 1f2f.) with a
possibly empty series of *note arguments: 3ef.:

     call                 ::= primary "(" [argument_list [","] | comprehension] ")"
     argument_list        ::= positional_arguments ["," starred_and_keywords]
                                ["," keywords_arguments]
                              | starred_and_keywords ["," keywords_arguments]
                              | keywords_arguments
     positional_arguments ::= positional_item ("," positional_item)*
     positional_item      ::= assignment_expression | "*" expression
     starred_and_keywords ::= ("*" expression | keyword_item)
                              ("," "*" expression | "," keyword_item)*
     keywords_arguments   ::= (keyword_item | "**" expression)
                              ("," keyword_item | "," "**" expression)*
     keyword_item         ::= identifier "=" expression

An optional trailing comma may be present after the positional and
keyword arguments but does not affect the semantics.

The primary must evaluate to a callable object (user-defined functions,
built-in functions, methods of built-in objects, class objects, methods
of class instances, and all objects having a *note __call__(): 4fe.
method are callable).  All argument expressions are evaluated before the
call is attempted.  Please refer to section *note 函式定義: 1b3a. for
the syntax of formal *note parameter: 1dee. lists.

If keyword arguments are present, they are first converted to positional
arguments, as follows.  First, a list of unfilled slots is created for
the formal parameters.  If there are N positional arguments, they are
placed in the first N slots.  Next, for each keyword argument, the
identifier is used to determine the corresponding slot (if the
identifier is the same as the first formal parameter name, the first
slot is used, and so on).  If the slot is already filled, a *note
TypeError: 4dd. exception is raised.  Otherwise, the argument is placed
in the slot, filling it (even if the expression is ‘None’, it fills the
slot).  When all arguments have been processed, the slots that are still
unfilled are filled with the corresponding default value from the
function definition.  (Default values are calculated, once, when the
function is defined; thus, a mutable object such as a list or dictionary
used as default value will be shared by all calls that don't specify an
argument value for the corresponding slot; this should usually be
avoided.)  If there are any unfilled slots for which no default value is
specified, a *note TypeError: 4dd. exception is raised.  Otherwise, the
list of filled slots is used as the argument list for the call.

'CPython 實作細節：' An implementation may provide built-in functions
whose positional parameters do not have names, even if they are 'named'
for the purpose of documentation, and which therefore cannot be supplied
by keyword.  In CPython, this is the case for functions implemented in C
that use *note PyArg_ParseTuple(): 517. to parse their arguments.

If there are more positional arguments than there are formal parameter
slots, a *note TypeError: 4dd. exception is raised, unless a formal
parameter using the syntax ‘*identifier’ is present; in this case, that
formal parameter receives a tuple containing the excess positional
arguments (or an empty tuple if there were no excess positional
arguments).

If any keyword argument does not correspond to a formal parameter name,
a *note TypeError: 4dd. exception is raised, unless a formal parameter
using the syntax ‘**identifier’ is present; in this case, that formal
parameter receives a dictionary containing the excess keyword arguments
(using the keywords as keys and the argument values as corresponding
values), or a (new) empty dictionary if there were no excess keyword
arguments.

If the syntax ‘*expression’ appears in the function call, ‘expression’
must evaluate to an *note iterable: 11bf.  Elements from these iterables
are treated as if they were additional positional arguments.  For the
call ‘f(x1, x2, *y, x3, x4)’, if 'y' evaluates to a sequence 'y1', ...,
'yM', this is equivalent to a call with M+4 positional arguments 'x1',
'x2', 'y1', ..., 'yM', 'x3', 'x4'.

A consequence of this is that although the ‘*expression’ syntax may
appear 'after' explicit keyword arguments, it is processed 'before' the
keyword arguments (and any ‘**expression’ arguments - see below).  So:

     >>> def f(a, b):
     ...     print(a, b)
     ...
     >>> f(b=1, *(2,))
     2 1
     >>> f(a=1, *(2,))
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: f() got multiple values for keyword argument 'a'
     >>> f(1, *(2,))
     1 2

It is unusual for both keyword arguments and the ‘*expression’ syntax to
be used in the same call, so in practice this confusion does not often
arise.

If the syntax ‘**expression’ appears in the function call, ‘expression’
must evaluate to a *note mapping: 1154, the contents of which are
treated as additional keyword arguments.  If a parameter matching a key
has already been given a value (by an explicit keyword argument, or from
another unpacking), a *note TypeError: 4dd. exception is raised.

When ‘**expression’ is used, each key in this mapping must be a string.
Each value from the mapping is assigned to the first formal parameter
eligible for keyword assignment whose name is equal to the key.  A key
need not be a Python identifier (e.g.  ‘"max-temp °F"’ is acceptable,
although it will not match any formal parameter that could be declared).
If there is no match to a formal parameter the key-value pair is
collected by the ‘**’ parameter, if there is one, or if there is not, a
*note TypeError: 4dd. exception is raised.

Formal parameters using the syntax ‘*identifier’ or ‘**identifier’
cannot be used as positional argument slots or as keyword argument
names.

在 3.5 版的變更: Function calls accept any number of ‘*’ and ‘**’
unpackings, positional arguments may follow iterable unpackings (‘*’),
and keyword arguments may follow dictionary unpackings (‘**’).
Originally proposed by PEP 448(1).

A call always returns some value, possibly ‘None’, unless it raises an
exception.  How this value is computed depends on the type of the
callable object.

If it is--

a user-defined function:

     The code block for the function is executed, passing it the
     argument list.  The first thing the code block will do is bind the
     formal parameters to the arguments; this is described in section
     *note 函式定義: 1b3a.  When the code block executes a *note return:
     972. statement, this specifies the return value of the function
     call.

a built-in function or method:

     The result is up to the interpreter; see *note 內建函式: 11f5. for
     the descriptions of built-in functions and methods.

a class object:

     A new instance of that class is returned.

a class instance method:

     The corresponding user-defined function is called, with an argument
     list that is one longer than the argument list of the call: the
     instance becomes the first argument.

a class instance:

     The class must define a *note __call__(): 4fe. method; the effect
     is then the same as if that method was called.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0448/


File: python.info,  Node: Await expression,  Next: The power operator,  Prev: Primaries,  Up: 運算式

4.6.4 Await expression
----------------------

Suspend the execution of *note coroutine: 438. on an *note awaitable:
193. object.  Can only be used inside a *note coroutine function: d1d.

     await_expr ::= "await" primary

在 3.5 版被加入.


File: python.info,  Node: The power operator,  Next: Unary arithmetic and bitwise operations,  Prev: Await expression,  Up: 運算式

4.6.5 The power operator
------------------------

The power operator binds more tightly than unary operators on its left;
it binds less tightly than unary operators on its right.  The syntax is:

     power ::= (await_expr | primary) ["**" u_expr]

Thus, in an unparenthesized sequence of power and unary operators, the
operators are evaluated from right to left (this does not constrain the
evaluation order for the operands): ‘-1**2’ results in ‘-1’.

The power operator has the same semantics as the built-in *note pow():
976. function, when called with two arguments: it yields its left
argument raised to the power of its right argument.  The numeric
arguments are first converted to a common type, and the result is of
that type.

For int operands, the result has the same type as the operands unless
the second argument is negative; in that case, all arguments are
converted to float and a float result is delivered.  For example,
‘10**2’ returns ‘100’, but ‘10**-2’ returns ‘0.01’.

Raising ‘0.0’ to a negative power results in a *note ZeroDivisionError:
8e9.  Raising a negative number to a fractional power results in a *note
complex: 2c9. number.  (In earlier versions it raised a *note
ValueError: 1e7.)

This operation can be customized using the special *note __pow__(): 777.
and *note __rpow__(): 778. methods.


File: python.info,  Node: Unary arithmetic and bitwise operations,  Next: Binary arithmetic operations,  Prev: The power operator,  Up: 運算式

4.6.6 Unary arithmetic and bitwise operations
---------------------------------------------

All unary arithmetic and bitwise operations have the same priority:

     u_expr ::= power | "-" u_expr | "+" u_expr | "~" u_expr

The unary ‘-’ (minus) operator yields the negation of its numeric
argument; the operation can be overridden with the *note __neg__():
1e8b. special method.

The unary ‘+’ (plus) operator yields its numeric argument unchanged; the
operation can be overridden with the *note __pos__(): 1e8c. special
method.

The unary ‘~’ (invert) operator yields the bitwise inversion of its
integer argument.  The bitwise inversion of ‘x’ is defined as ‘-(x+1)’.
It only applies to integral numbers or to custom objects that override
the *note __invert__(): 1e8e. special method.

In all three cases, if the argument does not have the proper type, a
*note TypeError: 4dd. exception is raised.


File: python.info,  Node: Binary arithmetic operations,  Next: Shifting operations,  Prev: Unary arithmetic and bitwise operations,  Up: 運算式

4.6.7 Binary arithmetic operations
----------------------------------

The binary arithmetic operations have the conventional priority levels.
Note that some of these operations also apply to certain non-numeric
types.  Apart from the power operator, there are only two levels, one
for multiplicative operators and one for additive operators:

     m_expr ::= u_expr | m_expr "*" u_expr | m_expr "@" m_expr |
                m_expr "//" u_expr | m_expr "/" u_expr |
                m_expr "%" u_expr
     a_expr ::= m_expr | a_expr "+" m_expr | a_expr "-" m_expr

The ‘*’ (multiplication) operator yields the product of its arguments.
The arguments must either both be numbers, or one argument must be an
integer and the other must be a sequence.  In the former case, the
numbers are converted to a common type and then multiplied together.  In
the latter case, sequence repetition is performed; a negative repetition
factor yields an empty sequence.

This operation can be customized using the special *note __mul__():
1e65. and *note __rmul__(): 1e66. methods.

The ‘@’ (at) operator is intended to be used for matrix multiplication.
No builtin Python types implement this operator.

This operation can be customized using the special *note __matmul__():
1e6d. and *note __rmatmul__(): 1e76. methods.

在 3.5 版被加入.

The ‘/’ (division) and ‘//’ (floor division) operators yield the
quotient of their arguments.  The numeric arguments are first converted
to a common type.  Division of integers yields a float, while floor
division of integers results in an integer; the result is that of
mathematical division with the 'floor' function applied to the result.
Division by zero raises the *note ZeroDivisionError: 8e9. exception.

The division operation can be customized using the special *note
__truediv__(): 1461. and *note __rtruediv__(): 1e77. methods.  The floor
division operation can be customized using the special *note
__floordiv__(): 1462. and *note __rfloordiv__(): 1e78. methods.

The ‘%’ (modulo) operator yields the remainder from the division of the
first argument by the second.  The numeric arguments are first converted
to a common type.  A zero right argument raises the *note
ZeroDivisionError: 8e9. exception.  The arguments may be floating-point
numbers, e.g., ‘3.14%0.7’ equals ‘0.34’ (since ‘3.14’ equals ‘4*0.7 +
0.34’.)  The modulo operator always yields a result with the same sign
as its second operand (or zero); the absolute value of the result is
strictly smaller than the absolute value of the second operand (1).

The floor division and modulo operators are connected by the following
identity: ‘x == (x//y)*y + (x%y)’.  Floor division and modulo are also
connected with the built-in function *note divmod(): 945.: ‘divmod(x, y)
== (x//y, x%y)’.  (2).

In addition to performing the modulo operation on numbers, the ‘%’
operator is also overloaded by string objects to perform old-style
string formatting (also known as interpolation).  The syntax for string
formatting is described in the Python Library Reference, section *note
printf-style String Formatting: 671.

The 'modulo' operation can be customized using the special *note
__mod__(): 1e6e. and *note __rmod__(): 1e79. methods.

The floor division operator, the modulo operator, and the *note
divmod(): 945. function are not defined for complex numbers.  Instead,
convert to a floating-point number using the *note abs(): 1ba8. function
if appropriate.

The ‘+’ (addition) operator yields the sum of its arguments.  The
arguments must either both be numbers or both be sequences of the same
type.  In the former case, the numbers are converted to a common type
and then added together.  In the latter case, the sequences are
concatenated.

This operation can be customized using the special *note __add__():
1e62. and *note __radd__(): 1e63. methods.

The ‘-’ (subtraction) operator yields the difference of its arguments.
The numeric arguments are first converted to a common type.

This operation can be customized using the special *note __sub__():
1e6c. and *note __rsub__(): 1e75. methods.

   ---------- Footnotes ----------

   (1) While ‘abs(x%y) < abs(y)’ is true mathematically, for floats it
may not be true numerically due to roundoff.  For example, and assuming
a platform on which a Python float is an IEEE 754 double-precision
number, in order that ‘-1e-100 % 1e100’ have the same sign as ‘1e100’,
the computed result is ‘-1e-100 + 1e100’, which is numerically exactly
equal to ‘1e100’.  The function *note math.fmod(): 1f43. returns a
result whose sign matches the sign of the first argument instead, and so
returns ‘-1e-100’ in this case.  Which approach is more appropriate
depends on the application.

   (2) If x is very close to an exact integer multiple of y, it's
possible for ‘x//y’ to be one larger than ‘(x-x%y)//y’ due to rounding.
In such cases, Python returns the latter result, in order to preserve
that ‘divmod(x,y)[0] * y + x % y’ be very close to ‘x’.


File: python.info,  Node: Shifting operations,  Next: Binary bitwise operations,  Prev: Binary arithmetic operations,  Up: 運算式

4.6.8 Shifting operations
-------------------------

The shifting operations have lower priority than the arithmetic
operations:

     shift_expr ::= a_expr | shift_expr ("<<" | ">>") a_expr

These operators accept integers as arguments.  They shift the first
argument to the left or right by the number of bits given by the second
argument.

The left shift operation can be customized using the special *note
__lshift__(): 1e70. and *note __rlshift__(): 1e7b. methods.  The right
shift operation can be customized using the special *note __rshift__():
1e71. and *note __rrshift__(): 1e7c. methods.

A right shift by 'n' bits is defined as floor division by ‘pow(2,n)’.  A
left shift by 'n' bits is defined as multiplication with ‘pow(2,n)’.


File: python.info,  Node: Binary bitwise operations,  Next: Comparisons,  Prev: Shifting operations,  Up: 運算式

4.6.9 Binary bitwise operations
-------------------------------

Each of the three bitwise operations has a different priority level:

     and_expr ::= shift_expr | and_expr "&" shift_expr
     xor_expr ::= and_expr | xor_expr "^" and_expr
     or_expr  ::= xor_expr | or_expr "|" xor_expr

The ‘&’ operator yields the bitwise AND of its arguments, which must be
integers or one of them must be a custom object overriding *note
__and__(): 1e72. or *note __rand__(): 1e7d. special methods.

The ‘^’ operator yields the bitwise XOR (exclusive OR) of its arguments,
which must be integers or one of them must be a custom object overriding
*note __xor__(): 1e73. or *note __rxor__(): 1e7e. special methods.

The ‘|’ operator yields the bitwise (inclusive) OR of its arguments,
which must be integers or one of them must be a custom object overriding
*note __or__(): 1e74. or *note __ror__(): 1e7f. special methods.


File: python.info,  Node: Comparisons,  Next: Boolean operations,  Prev: Binary bitwise operations,  Up: 運算式

4.6.10 Comparisons
------------------

Unlike C, all comparison operations in Python have the same priority,
which is lower than that of any arithmetic, shifting or bitwise
operation.  Also unlike C, expressions like ‘a < b < c’ have the
interpretation that is conventional in mathematics:

     comparison    ::= or_expr (comp_operator or_expr)*
     comp_operator ::= "<" | ">" | "==" | ">=" | "<=" | "!="
                       | "is" ["not"] | ["not"] "in"

Comparisons yield boolean values: ‘True’ or ‘False’.  Custom 'rich
comparison methods' may return non-boolean values.  In this case Python
will call *note bool(): 40e. on such value in boolean contexts.

Comparisons can be chained arbitrarily, e.g., ‘x < y <= z’ is equivalent
to ‘x < y and y <= z’, except that ‘y’ is evaluated only once (but in
both cases ‘z’ is not evaluated at all when ‘x < y’ is found to be
false).

Formally, if 'a', 'b', 'c', ..., 'y', 'z' are expressions and 'op1',
'op2', ..., 'opN' are comparison operators, then ‘a op1 b op2 c ... y
opN z’ is equivalent to ‘a op1 b and b op2 c and ... y opN z’, except
that each expression is evaluated at most once.

Note that ‘a op1 b op2 c’ doesn't imply any kind of comparison between
'a' and 'c', so that, e.g., ‘x < y > z’ is perfectly legal (though
perhaps not pretty).

* Menu:

* Value comparisons::
* Membership test operations::
* Identity comparisons::


File: python.info,  Node: Value comparisons,  Next: Membership test operations,  Up: Comparisons

4.6.10.1 Value comparisons
..........................

The operators ‘<’, ‘>’, ‘==’, ‘>=’, ‘<=’, and ‘!=’ compare the values of
two objects.  The objects do not need to have the same type.

Chapter *note Objects, values and types: 1dd3. states that objects have
a value (in addition to type and identity).  The value of an object is a
rather abstract notion in Python: For example, there is no canonical
access method for an object's value.  Also, there is no requirement that
the value of an object should be constructed in a particular way, e.g.
comprised of all its data attributes.  Comparison operators implement a
particular notion of what the value of an object is.  One can think of
them as defining the value of an object indirectly, by means of their
comparison implementation.

Because all types are (direct or indirect) subtypes of *note object:
a2f, they inherit the default comparison behavior from *note object:
a2f.  Types can customize their comparison behavior by implementing
'rich comparison methods' like *note __lt__(): 129e, described in *note
Basic customization: 1e35.

The default behavior for equality comparison (‘==’ and ‘!=’) is based on
the identity of the objects.  Hence, equality comparison of instances
with the same identity results in equality, and equality comparison of
instances with different identities results in inequality.  A motivation
for this default behavior is the desire that all objects should be
reflexive (i.e.  ‘x is y’ implies ‘x == y’).

A default order comparison (‘<’, ‘>’, ‘<=’, and ‘>=’) is not provided;
an attempt raises *note TypeError: 4dd.  A motivation for this default
behavior is the lack of a similar invariant as for equality.

The behavior of the default equality comparison, that instances with
different identities are always unequal, may be in contrast to what
types will need that have a sensible definition of object value and
value-based equality.  Such types will need to customize their
comparison behavior, and in fact, a number of built-in types have done
that.

The following list describes the comparison behavior of the most
important built-in types.

   * Numbers of built-in numeric types (*note 數值型別 --
     int、float、complex: 1afe.) and of the standard library types *note
     fractions.Fraction: 1c7. and *note decimal.Decimal: 27c. can be
     compared within and across their types, with the restriction that
     complex numbers do not support order comparison.  Within the limits
     of the types involved, they compare mathematically
     (algorithmically) correct without loss of precision.

     The not-a-number values ‘float('NaN')’ and ‘decimal.Decimal('NaN')’
     are special.  Any ordered comparison of a number to a not-a-number
     value is false.  A counter-intuitive implication is that
     not-a-number values are not equal to themselves.  For example, if
     ‘x = float('NaN')’, ‘3 < x’, ‘x < 3’ and ‘x == x’ are all false,
     while ‘x != x’ is true.  This behavior is compliant with IEEE 754.

   * ‘None’ and *note NotImplemented: 776. are singletons.  PEP 8(1)
     advises that comparisons for singletons should always be done with
     ‘is’ or ‘is not’, never the equality operators.

   * Binary sequences (instances of *note bytes: 1a5. or *note
     bytearray: 4e3.) can be compared within and across their types.
     They compare lexicographically using the numeric values of their
     elements.

   * Strings (instances of *note str: 3f2.) compare lexicographically
     using the numerical Unicode code points (the result of the built-in
     function *note ord(): 1de1.) of their characters.  (2)

     Strings and binary sequences cannot be directly compared.

   * Sequences (instances of *note tuple: 322, *note list: 5b6, or *note
     range: 8e7.) can be compared only within each of their types, with
     the restriction that ranges do not support order comparison.
     Equality comparison across these types results in inequality, and
     ordering comparison across these types raises *note TypeError: 4dd.

     Sequences compare lexicographically using comparison of
     corresponding elements.  The built-in containers typically assume
     identical objects are equal to themselves.  That lets them bypass
     equality tests for identical objects to improve performance and to
     maintain their internal invariants.

     Lexicographical comparison between built-in collections works as
     follows:

        - For two collections to compare equal, they must be of the same
          type, have the same length, and each pair of corresponding
          elements must compare equal (for example, ‘[1,2] == (1,2)’ is
          false because the type is not the same).

        - Collections that support order comparison are ordered the same
          as their first unequal elements (for example, ‘[1,2,x] <=
          [1,2,y]’ has the same value as ‘x <= y’).  If a corresponding
          element does not exist, the shorter collection is ordered
          first (for example, ‘[1,2] < [1,2,3]’ is true).

   * Mappings (instances of *note dict: 23b.) compare equal if and only
     if they have equal ‘(key, value)’ pairs.  Equality comparison of
     the keys and values enforces reflexivity.

     Order comparisons (‘<’, ‘>’, ‘<=’, and ‘>=’) raise *note TypeError:
     4dd.

   * Sets (instances of *note set: 57d. or *note frozenset: 57e.) can be
     compared within and across their types.

     They define order comparison operators to mean subset and superset
     tests.  Those relations do not define total orderings (for example,
     the two sets ‘{1,2}’ and ‘{2,3}’ are not equal, nor subsets of one
     another, nor supersets of one another).  Accordingly, sets are not
     appropriate arguments for functions which depend on total ordering
     (for example, *note min(): eac, *note max(): ead, and *note
     sorted(): b75. produce undefined results given a list of sets as
     inputs).

     Comparison of sets enforces reflexivity of its elements.

   * Most other built-in types have no comparison methods implemented,
     so they inherit the default comparison behavior.

User-defined classes that customize their comparison behavior should
follow some consistency rules, if possible:

   * Equality comparison should be reflexive.  In other words, identical
     objects should compare equal:

          ‘x is y’ implies ‘x == y’

   * Comparison should be symmetric.  In other words, the following
     expressions should have the same result:

          ‘x == y’ 和 ‘y == x’

          ‘x != y’ 和 ‘y != x’

          ‘x < y’ 和 ‘y > x’

          ‘x <= y’ 和 ‘y >= x’

   * Comparison should be transitive.  The following (non-exhaustive)
     examples illustrate that:

          ‘x > y and y > z’ 暗示了 ‘x > z’

          ‘x < y and y <= z’ 暗示了 ‘x < z’

   * Inverse comparison should result in the boolean negation.  In other
     words, the following expressions should have the same result:

          ‘x == y’ 和 ‘not x != y’

          ‘x < y’ and ‘not x >= y’ (for total ordering)

          ‘x > y’ and ‘not x <= y’ (for total ordering)

     The last two expressions apply to totally ordered collections (e.g.
     to sequences, but not to sets or mappings).  See also the *note
     total_ordering(): ee6. decorator.

   * The *note hash(): 58f. result should be consistent with equality.
     Objects that are equal should either have the same hash value, or
     be marked as unhashable.

Python does not enforce these consistency rules.  In fact, the
not-a-number values are an example for not following these rules.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0008/

   (2) The Unicode standard distinguishes between 'code points' (e.g.
U+0041) and 'abstract characters' (e.g.  "LATIN CAPITAL LETTER A").
While most abstract characters in Unicode are only represented using one
code point, there is a number of abstract characters that can in
addition be represented using a sequence of more than one code point.
For example, the abstract character "LATIN CAPITAL LETTER C WITH
CEDILLA" can be represented as a single 'precomposed character' at code
position U+00C7, or as a sequence of a 'base character' at code position
U+0043 (LATIN CAPITAL LETTER C), followed by a 'combining character' at
code position U+0327 (COMBINING CEDILLA).

The comparison operators on strings compare at the level of Unicode code
points.  This may be counter-intuitive to humans.  For example,
‘"\u00C7" == "\u0043\u0327"’ is ‘False’, even though both strings
represent the same abstract character "LATIN CAPITAL LETTER C WITH
CEDILLA".

To compare strings at the level of abstract characters (that is, in a
way intuitive to humans), use *note unicodedata.normalize(): 679.


File: python.info,  Node: Membership test operations,  Next: Identity comparisons,  Prev: Value comparisons,  Up: Comparisons

4.6.10.2 Membership test operations
...................................

The operators *note in: 2c5. and *note not in: 5d5. test for membership.
‘x in s’ evaluates to ‘True’ if 'x' is a member of 's', and ‘False’
otherwise.  ‘x not in s’ returns the negation of ‘x in s’.  All built-in
sequences and set types support this as well as dictionary, for which
‘in’ tests whether the dictionary has a given key.  For container types
such as list, tuple, set, frozenset, dict, or collections.deque, the
expression ‘x in y’ is equivalent to ‘any(x is e or x == e for e in y)’.

For the string and bytes types, ‘x in y’ is ‘True’ if and only if 'x' is
a substring of 'y'.  An equivalent test is ‘y.find(x) != -1’.  Empty
strings are always considered to be a substring of any other string, so
‘"" in "abc"’ will return ‘True’.

For user-defined classes which define the *note __contains__(): 1e33.
method, ‘x in y’ returns ‘True’ if ‘y.__contains__(x)’ returns a true
value, and ‘False’ otherwise.

For user-defined classes which do not define *note __contains__(): 1e33.
but do define *note __iter__(): 1e31, ‘x in y’ is ‘True’ if some value
‘z’, for which the expression ‘x is z or x == z’ is true, is produced
while iterating over ‘y’.  If an exception is raised during the
iteration, it is as if *note in: 2c5. raised that exception.

Lastly, the old-style iteration protocol is tried: if a class defines
*note __getitem__(): 266, ‘x in y’ is ‘True’ if and only if there is a
non-negative integer index 'i' such that ‘x is y[i] or x == y[i]’, and
no lower integer index raises the *note IndexError: 14a3. exception.
(If any other exception is raised, it is as if *note in: 2c5. raised
that exception).

The operator *note not in: 5d5. is defined to have the inverse truth
value of *note in: 2c5.


File: python.info,  Node: Identity comparisons,  Prev: Membership test operations,  Up: Comparisons

4.6.10.3 Identity comparisons
.............................

The operators *note is: 2c6. and *note is not: 1f53. test for an
object's identity: ‘x is y’ is true if and only if 'x' and 'y' are the
same object.  An Object's identity is determined using the *note id():
1390. function.  ‘x is not y’ yields the inverse truth value.  (1)

   ---------- Footnotes ----------

   (1) Due to automatic garbage-collection, free lists, and the dynamic
nature of descriptors, you may notice seemingly unusual behaviour in
certain uses of the *note is: 2c6. operator, like those involving
comparisons between instance methods, or constants.  Check their
documentation for more info.


File: python.info,  Node: Boolean operations,  Next: Assignment expressions<2>,  Prev: Comparisons,  Up: 運算式

4.6.11 Boolean operations
-------------------------

     or_test  ::= and_test | or_test "or" and_test
     and_test ::= not_test | and_test "and" not_test
     not_test ::= comparison | "not" not_test

In the context of Boolean operations, and also when expressions are used
by control flow statements, the following values are interpreted as
false: ‘False’, ‘None’, numeric zero of all types, and empty strings and
containers (including strings, tuples, lists, dictionaries, sets and
frozensets).  All other values are interpreted as true.  User-defined
objects can customize their truth value by providing a *note __bool__():
1268. method.

The operator *note not: 1f56. yields ‘True’ if its argument is false,
‘False’ otherwise.

The expression ‘x and y’ first evaluates 'x'; if 'x' is false, its value
is returned; otherwise, 'y' is evaluated and the resulting value is
returned.

The expression ‘x or y’ first evaluates 'x'; if 'x' is true, its value
is returned; otherwise, 'y' is evaluated and the resulting value is
returned.

Note that neither *note and: 2c2. nor *note or: 2c7. restrict the value
and type they return to ‘False’ and ‘True’, but rather return the last
evaluated argument.  This is sometimes useful, e.g., if ‘s’ is a string
that should be replaced by a default value if it is empty, the
expression ‘s or 'foo'’ yields the desired value.  Because *note not:
1f56. has to create a new value, it returns a boolean value regardless
of the type of its argument (for example, ‘not 'foo'’ produces ‘False’
rather than ‘''’.)


File: python.info,  Node: Assignment expressions<2>,  Next: Conditional expressions,  Prev: Boolean operations,  Up: 運算式

4.6.12 Assignment expressions
-----------------------------

     assignment_expression ::= [identifier ":="] expression

An assignment expression (sometimes also called a "named expression" or
"walrus") assigns an *note expression: 1f5b. to an *note identifier:
1d88, while also returning the value of the *note expression: 1f5b.

One common use case is when handling matched regular expressions:

     if matching := pattern.search(data):
         do_something(matching)

Or, when processing a file stream in chunks:

     while chunk := file.read(9000):
         process(chunk)

Assignment expressions must be surrounded by parentheses when used as
expression statements and when used as sub-expressions in slicing,
conditional, lambda, keyword-argument, and comprehension-if expressions
and in ‘assert’, ‘with’, and ‘assignment’ statements.  In all other
places where they can be used, parentheses are not required, including
in ‘if’ and ‘while’ statements.

在 3.8 版被加入: See PEP 572(1) for more details about assignment
expressions.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0572/


File: python.info,  Node: Conditional expressions,  Next: Lambdas,  Prev: Assignment expressions<2>,  Up: 運算式

4.6.13 Conditional expressions
------------------------------

     conditional_expression ::= or_test ["if" or_test "else" expression]
     expression             ::= conditional_expression | lambda_expr

Conditional expressions (sometimes called a "ternary operator") have the
lowest priority of all Python operations.

The expression ‘x if C else y’ first evaluates the condition, 'C' rather
than 'x'.  If 'C' is true, 'x' is evaluated and its value is returned;
otherwise, 'y' is evaluated and its value is returned.

See PEP 308(1) for more details about conditional expressions.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0308/


File: python.info,  Node: Lambdas,  Next: Expression lists,  Prev: Conditional expressions,  Up: 運算式

4.6.14 Lambdas
--------------

     lambda_expr ::= "lambda" [parameter_list] ":" expression

Lambda expressions (sometimes called lambda forms) are used to create
anonymous functions.  The expression ‘lambda parameters: expression’
yields a function object.  The unnamed object behaves like a function
object defined with:

     def <lambda>(parameters):
         return expression

See section *note 函式定義: 1b3a. for the syntax of parameter lists.
Note that functions created with lambda expressions cannot contain
statements or annotations.


File: python.info,  Node: Expression lists,  Next: Evaluation order,  Prev: Lambdas,  Up: 運算式

4.6.15 Expression lists
-----------------------

     expression_list    ::= expression ("," expression)* [","]
     starred_list       ::= starred_item ("," starred_item)* [","]
     starred_expression ::= expression | (starred_item ",")* [starred_item]
     starred_item       ::= assignment_expression | "*" or_expr

Except when part of a list or set display, an expression list containing
at least one comma yields a tuple.  The length of the tuple is the
number of expressions in the list.  The expressions are evaluated from
left to right.

An asterisk ‘*’ denotes 'iterable unpacking'.  Its operand must be an
*note iterable: 11bf.  The iterable is expanded into a sequence of
items, which are included in the new tuple, list, or set, at the site of
the unpacking.

在 3.5 版被加入: Iterable unpacking in expression lists, originally
proposed by PEP 448(1).

A trailing comma is required only to create a one-item tuple, such as
‘1,’; it is optional in all other cases.  A single expression without a
trailing comma doesn't create a tuple, but rather yields the value of
that expression.  (To create an empty tuple, use an empty pair of
parentheses: ‘()’.)

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0448/


File: python.info,  Node: Evaluation order,  Next: Operator precedence,  Prev: Expression lists,  Up: 運算式

4.6.16 Evaluation order
-----------------------

Python evaluates expressions from left to right.  Notice that while
evaluating an assignment, the right-hand side is evaluated before the
left-hand side.

In the following lines, expressions will be evaluated in the arithmetic
order of their suffixes:

     expr1, expr2, expr3, expr4
     (expr1, expr2, expr3, expr4)
     {expr1: expr2, expr3: expr4}
     expr1 + expr2 * (expr3 - expr4)
     expr1(expr2, expr3, *expr4, **expr5)
     expr3, expr4 = expr1, expr2


File: python.info,  Node: Operator precedence,  Prev: Evaluation order,  Up: 運算式

4.6.17 Operator precedence
--------------------------

The following table summarizes the operator precedence in Python, from
highest precedence (most binding) to lowest precedence (least binding).
Operators in the same box have the same precedence.  Unless the syntax
is explicitly given, operators are binary.  Operators in the same box
group left to right (except for exponentiation and conditional
expressions, which group from right to left).

Note that comparisons, membership tests, and identity tests, all have
the same precedence and have a left-to-right chaining feature as
described in the *note Comparisons: 1f4c. section.

Operator                                            描述
                                                    
----------------------------------------------------------------------------------------------
                                                    
‘(expressions...)’,                                 Binding or parenthesized expression,
                                                    list display, dictionary display, set
‘[expressions...]’, ‘{key: value...}’,              display
‘{expressions...}’                                  

‘x[index]’, ‘x[index:index]’, ‘x(arguments...)’,    Subscription, slicing, call, attribute
‘x.attribute’                                       reference
                                                    
                                                    
*note await x: 19f.                                 Await expression
                                                    
                                                    
‘**’                                                Exponentiation (1)
                                                    
                                                    
‘+x’, ‘-x’, ‘~x’                                    Positive, negative, bitwise NOT
                                                    
                                                    
‘*’, ‘@’, ‘/’, ‘//’, ‘%’                            Multiplication, matrix multiplication,
                                                    division, floor division, remainder (2)
                                                    
                                                    
‘+’, ‘-’                                            Addition and subtraction
                                                    
                                                    
‘<<’, ‘>>’                                          Shifts
                                                    
                                                    
‘&’                                                 Bitwise AND
                                                    
                                                    
‘^’                                                 Bitwise XOR
                                                    
                                                    
‘|’                                                 Bitwise OR
                                                    
                                                    
*note in: 2c5, *note not in: 5d5, *note is: 2c6,    Comparisons, including membership tests
*note is not: 1f53, ‘<’, ‘<=’, ‘>’, ‘>=’, ‘!=’,     and identity tests
‘==’                                                

*note not x: 1f56.                                  Boolean NOT
                                                    
                                                    
*note and: 2c2.                                     Boolean AND
                                                    
                                                    
*note or: 2c7.                                      Boolean OR
                                                    
                                                    
*note if: 1f5d. - ‘else’                            Conditional expression
                                                    
                                                    
*note lambda: 1234.                                 Lambda expression
                                                    
                                                    
‘:=’                                                Assignment expression
                                                    

註解
....

   ---------- Footnotes ----------

   (1) The power operator ‘**’ binds less tightly than an arithmetic or
bitwise unary operator on its right, that is, ‘2**-1’ is ‘0.5’.

   (2) The ‘%’ operator is also used for string formatting; the same
precedence applies.


File: python.info,  Node: 簡單陳述式,  Next: 複合陳述式,  Prev: 運算式,  Up: Python 語言參考手冊

4.7 簡單陳述式
==============

A simple statement is comprised within a single logical line.  Several
simple statements may occur on a single line separated by semicolons.
The syntax for simple statements is:

     simple_stmt ::= expression_stmt
                     | assert_stmt
                     | assignment_stmt
                     | augmented_assignment_stmt
                     | annotated_assignment_stmt
                     | pass_stmt
                     | del_stmt
                     | return_stmt
                     | yield_stmt
                     | raise_stmt
                     | break_stmt
                     | continue_stmt
                     | import_stmt
                     | future_stmt
                     | global_stmt
                     | nonlocal_stmt
                     | type_stmt

* Menu:

* Expression statements::
* Assignment statements::
* assert 陳述式::
* pass 陳述式: pass 陳述式<2>.
* del 陳述式: del 陳述式<2>.
* return 陳述式::
* yield 陳述式::
* raise 陳述式::
* break 陳述式::
* continue 陳述式::
* import 陳述式::
* global 陳述式::
* nonlocal 陳述式::
* type 陳述式::


File: python.info,  Node: Expression statements,  Next: Assignment statements,  Up: 簡單陳述式

4.7.1 Expression statements
---------------------------

Expression statements are used (mostly interactively) to compute and
write a value, or (usually) to call a procedure (a function that returns
no meaningful result; in Python, procedures return the value ‘None’).
Other uses of expression statements are allowed and occasionally useful.
The syntax for an expression statement is:

     expression_stmt ::= starred_expression

An expression statement evaluates the expression list (which may be a
single expression).

In interactive mode, if the value is not ‘None’, it is converted to a
string using the built-in *note repr(): 7a1. function and the resulting
string is written to standard output on a line by itself (except if the
result is ‘None’, so that procedure calls do not cause any output.)


File: python.info,  Node: Assignment statements,  Next: assert 陳述式,  Prev: Expression statements,  Up: 簡單陳述式

4.7.2 Assignment statements
---------------------------

Assignment statements are used to (re)bind names to values and to modify
attributes or items of mutable objects:

     assignment_stmt ::= (target_list "=")+ (starred_expression | yield_expression)
     target_list     ::= target ("," target)* [","]
     target          ::= identifier
                         | "(" [target_list] ")"
                         | "[" [target_list] "]"
                         | attributeref
                         | subscription
                         | slicing
                         | "*" target

(See section *note Primaries: 1f1e. for the syntax definitions for
'attributeref', 'subscription', and 'slicing'.)

An assignment statement evaluates the expression list (remember that
this can be a single expression or a comma-separated list, the latter
yielding a tuple) and assigns the single resulting object to each of the
target lists, from left to right.

Assignment is defined recursively depending on the form of the target
(list).  When a target is part of a mutable object (an attribute
reference, subscription or slicing), the mutable object must ultimately
perform the assignment and decide about its validity, and may raise an
exception if the assignment is unacceptable.  The rules observed by
various types and the exceptions raised are given with the definition of
the object types (see section *note 標準型別階層: 1dd6.).

Assignment of an object to a target list, optionally enclosed in
parentheses or square brackets, is recursively defined as follows.

   * If the target list is a single target with no trailing comma,
     optionally in parentheses, the object is assigned to that target.

   * Else:

        * If the target list contains one target prefixed with an
          asterisk, called a "starred" target: The object must be an
          iterable with at least as many items as there are targets in
          the target list, minus one.  The first items of the iterable
          are assigned, from left to right, to the targets before the
          starred target.  The final items of the iterable are assigned
          to the targets after the starred target.  A list of the
          remaining items in the iterable is then assigned to the
          starred target (the list can be empty).

        * Else: The object must be an iterable with the same number of
          items as there are targets in the target list, and the items
          are assigned, from left to right, to the corresponding
          targets.

Assignment of an object to a single target is recursively defined as
follows.

   * If the target is an identifier (name):

        * If the name does not occur in a *note global: 170. or *note
          nonlocal: 123e. statement in the current code block: the name
          is bound to the object in the current local namespace.

        * Otherwise: the name is bound to the object in the global
          namespace or the outer namespace determined by *note nonlocal:
          123e, respectively.

     The name is rebound if it was already bound.  This may cause the
     reference count for the object previously bound to the name to
     reach zero, causing the object to be deallocated and its destructor
     (if it has one) to be called.

   * If the target is an attribute reference: The primary expression in
     the reference is evaluated.  It should yield an object with
     assignable attributes; if this is not the case, *note TypeError:
     4dd. is raised.  That object is then asked to assign the assigned
     object to the given attribute; if it cannot perform the assignment,
     it raises an exception (usually but not necessarily *note
     AttributeError: 2f6.).  Note: If the object is a class instance and
     the attribute reference occurs on both sides of the assignment
     operator, the right-hand side expression, ‘a.x’ can access either
     an instance attribute or (if no instance attribute exists) a class
     attribute.  The left-hand side target ‘a.x’ is always set as an
     instance attribute, creating it if necessary.  Thus, the two
     occurrences of ‘a.x’ do not necessarily refer to the same
     attribute: if the right-hand side expression refers to a class
     attribute, the left-hand side creates a new instance attribute as
     the target of the assignment:

          class Cls:
              x = 3             # class variable
          inst = Cls()
          inst.x = inst.x + 1   # writes inst.x as 4 leaving Cls.x as 3

     This description does not necessarily apply to descriptor
     attributes, such as properties created with *note property(): 180.

   * If the target is a subscription: The primary expression in the
     reference is evaluated.  It should yield either a mutable sequence
     object (such as a list) or a mapping object (such as a dictionary).
     Next, the subscript expression is evaluated.

     If the primary is a mutable sequence object (such as a list), the
     subscript must yield an integer.  If it is negative, the sequence's
     length is added to it.  The resulting value must be a nonnegative
     integer less than the sequence's length, and the sequence is asked
     to assign the assigned object to its item with that index.  If the
     index is out of range, *note IndexError: 14a3. is raised
     (assignment to a subscripted sequence cannot add new items to a
     list).

     If the primary is a mapping object (such as a dictionary), the
     subscript must have a type compatible with the mapping's key type,
     and the mapping is then asked to create a key/value pair which maps
     the subscript to the assigned object.  This can either replace an
     existing key/value pair with the same key value, or insert a new
     key/value pair (if no key with the same value existed).

     For user-defined objects, the *note __setitem__(): 1434. method is
     called with appropriate arguments.

   * If the target is a slicing: The primary expression in the reference
     is evaluated.  It should yield a mutable sequence object (such as a
     list).  The assigned object should be a sequence object of the same
     type.  Next, the lower and upper bound expressions are evaluated,
     insofar they are present; defaults are zero and the sequence's
     length.  The bounds should evaluate to integers.  If either bound
     is negative, the sequence's length is added to it.  The resulting
     bounds are clipped to lie between zero and the sequence's length,
     inclusive.  Finally, the sequence object is asked to replace the
     slice with the items of the assigned sequence.  The length of the
     slice may be different from the length of the assigned sequence,
     thus changing the length of the target sequence, if the target
     sequence allows it.

'CPython 實作細節：' In the current implementation, the syntax for
targets is taken to be the same as for expressions, and invalid syntax
is rejected during the code generation phase, causing less detailed
error messages.

Although the definition of assignment implies that overlaps between the
left-hand side and the right-hand side are 'simultaneous' (for example
‘a, b = b, a’ swaps two variables), overlaps 'within' the collection of
assigned-to variables occur left-to-right, sometimes resulting in
confusion.  For instance, the following program prints ‘[0, 2]’:

     x = [0, 1]
     i = 0
     i, x[i] = 1, 2         # i is updated, then x[i] is updated
     print(x)

也參考
......

PEP 3132(1) - Extended Iterable Unpacking

     The specification for the ‘*target’ feature.

* Menu:

* Augmented assignment statements::
* Annotated assignment statements::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3132/


File: python.info,  Node: Augmented assignment statements,  Next: Annotated assignment statements,  Up: Assignment statements

4.7.2.1 Augmented assignment statements
.......................................

Augmented assignment is the combination, in a single statement, of a
binary operation and an assignment statement:

     augmented_assignment_stmt ::= augtarget augop (expression_list | yield_expression)
     augtarget                 ::= identifier | attributeref | subscription | slicing
     augop                     ::= "+=" | "-=" | "*=" | "@=" | "/=" | "//=" | "%=" | "**="
                                   | ">>=" | "<<=" | "&=" | "^=" | "|="

(See section *note Primaries: 1f1e. for the syntax definitions of the
last three symbols.)

An augmented assignment evaluates the target (which, unlike normal
assignment statements, cannot be an unpacking) and the expression list,
performs the binary operation specific to the type of assignment on the
two operands, and assigns the result to the original target.  The target
is only evaluated once.

An augmented assignment statement like ‘x += 1’ can be rewritten as ‘x =
x + 1’ to achieve a similar, but not exactly equal effect.  In the
augmented version, ‘x’ is only evaluated once.  Also, when possible, the
actual operation is performed 'in-place', meaning that rather than
creating a new object and assigning that to the target, the old object
is modified instead.

Unlike normal assignments, augmented assignments evaluate the left-hand
side 'before' evaluating the right-hand side.  For example, ‘a[i] +=
f(x)’ first looks-up ‘a[i]’, then it evaluates ‘f(x)’ and performs the
addition, and lastly, it writes the result back to ‘a[i]’.

With the exception of assigning to tuples and multiple targets in a
single statement, the assignment done by augmented assignment statements
is handled the same way as normal assignments.  Similarly, with the
exception of the possible 'in-place' behavior, the binary operation
performed by augmented assignment is the same as the normal binary
operations.

For targets which are attribute references, the same *note caveat about
class and instance attributes: 1f75. applies as for regular assignments.


File: python.info,  Node: Annotated assignment statements,  Prev: Augmented assignment statements,  Up: Assignment statements

4.7.2.2 Annotated assignment statements
.......................................

*note Annotation: cfc. assignment is the combination, in a single
statement, of a variable or attribute annotation and an optional
assignment statement:

     annotated_assignment_stmt ::= augtarget ":" expression
                                   ["=" (starred_expression | yield_expression)]

The difference from normal *note Assignment statements: 1eaf. is that
only a single target is allowed.

The assignment target is considered "simple" if it consists of a single
name that is not enclosed in parentheses.  For simple assignment
targets, if in class or module scope, the annotations are evaluated and
stored in a special class or module attribute ‘__annotations__’ that is
a dictionary mapping from variable names (mangled if private) to
evaluated annotations.  This attribute is writable and is automatically
created at the start of class or module body execution, if annotations
are found statically.

If the assignment target is not simple (an attribute, subscript node, or
parenthesized name), the annotation is evaluated if in class or module
scope, but not stored.

If a name is annotated in a function scope, then this name is local for
that scope.  Annotations are never evaluated and stored in function
scopes.

If the right hand side is present, an annotated assignment performs the
actual assignment before evaluating annotations (where applicable).  If
the right hand side is not present for an expression target, then the
interpreter evaluates the target except for the last *note
__setitem__(): 1434. or *note __setattr__(): 1e05. call.

也參考
......

PEP 526(1) - Syntax for Variable Annotations

     The proposal that added syntax for annotating the types of
     variables (including class variables and instance variables),
     instead of expressing them through comments.

PEP 484(2) - Type hints

     The proposal that added the *note typing: ed. module to provide a
     standard syntax for type annotations that can be used in static
     analysis tools and IDEs.

在 3.8 版的變更: Now annotated assignments allow the same expressions in
the right hand side as regular assignments.  Previously, some
expressions (like un-parenthesized tuple expressions) caused a syntax
error.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0526/

   (2) https://peps.python.org/pep-0484/


File: python.info,  Node: assert 陳述式,  Next: pass 陳述式<2>,  Prev: Assignment statements,  Up: 簡單陳述式

4.7.3 ‘assert’ 陳述式
---------------------

Assert statements are a convenient way to insert debugging assertions
into a program:

     assert_stmt ::= "assert" expression ["," expression]

The simple form, ‘assert expression’, is equivalent to

     if __debug__:
         if not expression: raise AssertionError

The extended form, ‘assert expression1, expression2’, is equivalent to

     if __debug__:
         if not expression1: raise AssertionError(expression2)

These equivalences assume that *note __debug__: 77e. and *note
AssertionError: 64e. refer to the built-in variables with those names.
In the current implementation, the built-in variable *note __debug__:
77e. is ‘True’ under normal circumstances, ‘False’ when optimization is
requested (command line option *note -O: d5b.).  The current code
generator emits no code for an assert statement when optimization is
requested at compile time.  Note that it is unnecessary to include the
source code for the expression that failed in the error message; it will
be displayed as part of the stack trace.

Assignments to *note __debug__: 77e. are illegal.  The value for the
built-in variable is determined when the interpreter starts.


File: python.info,  Node: pass 陳述式<2>,  Next: del 陳述式<2>,  Prev: assert 陳述式,  Up: 簡單陳述式

4.7.4 ‘pass’ 陳述式
-------------------

     pass_stmt ::= "pass"

*note pass: 1b1e. is a null operation -- when it is executed, nothing
happens.  It is useful as a placeholder when a statement is required
syntactically, but no code needs to be executed, for example:

     def f(arg): pass    # a function that does nothing (yet)

     class C: pass       # a class with no methods (yet)


File: python.info,  Node: del 陳述式<2>,  Next: return 陳述式,  Prev: pass 陳述式<2>,  Up: 簡單陳述式

4.7.5 ‘del’ 陳述式
------------------

     del_stmt ::= "del" target_list

Deletion is recursively defined very similar to the way assignment is
defined.  Rather than spelling it out in full details, here are some
hints.

Deletion of a target list recursively deletes each target, from left to
right.

Deletion of a name removes the binding of that name from the local or
global namespace, depending on whether the name occurs in a *note
global: 170. statement in the same code block.  If the name is unbound,
a *note NameError: 3e5. exception will be raised.

Deletion of attribute references, subscriptions and slicings is passed
to the primary object involved; deletion of a slicing is in general
equivalent to assignment of an empty slice of the right type (but even
this is determined by the sliced object).

在 3.2 版的變更: Previously it was illegal to delete a name from the
local namespace if it occurs as a free variable in a nested block.


File: python.info,  Node: return 陳述式,  Next: yield 陳述式,  Prev: del 陳述式<2>,  Up: 簡單陳述式

4.7.6 ‘return’ 陳述式
---------------------

     return_stmt ::= "return" [expression_list]

*note return: 972. may only occur syntactically nested in a function
definition, not within a nested class definition.

If an expression list is present, it is evaluated, else ‘None’ is
substituted.

*note return: 972. leaves the current function call with the expression
list (or ‘None’) as return value.

When *note return: 972. passes control out of a *note try: 68c.
statement with a *note finally: 96e. clause, that ‘finally’ clause is
executed before really leaving the function.

In a generator function, the *note return: 972. statement indicates that
the generator is done and will cause *note StopIteration: ba1. to be
raised.  The returned value (if any) is used as an argument to construct
*note StopIteration: ba1. and becomes the *note StopIteration.value:
1e9f. attribute.

In an asynchronous generator function, an empty *note return: 972.
statement indicates that the asynchronous generator is done and will
cause *note StopAsyncIteration: 1933. to be raised.  A non-empty
‘return’ statement is a syntax error in an asynchronous generator
function.


File: python.info,  Node: yield 陳述式,  Next: raise 陳述式,  Prev: return 陳述式,  Up: 簡單陳述式

4.7.7 ‘yield’ 陳述式
--------------------

     yield_stmt ::= yield_expression

A *note yield: 971. statement is semantically equivalent to a *note
yield expression: 1f10.  The yield statement can be used to omit the
parentheses that would otherwise be required in the equivalent yield
expression statement.  For example, the yield statements

     yield <expr>
     yield from <expr>

are equivalent to the yield expression statements

     (yield <expr>)
     (yield from <expr>)

Yield expressions and statements are only used when defining a *note
generator: 1004. function, and are only used in the body of the
generator function.  Using yield in a function definition is sufficient
to cause that definition to create a generator function instead of a
normal function.

For full details of *note yield: 971. semantics, refer to the *note
Yield expressions: 1f10. section.


File: python.info,  Node: raise 陳述式,  Next: break 陳述式,  Prev: yield 陳述式,  Up: 簡單陳述式

4.7.8 ‘raise’ 陳述式
--------------------

     raise_stmt ::= "raise" [expression ["from" expression]]

If no expressions are present, *note raise: 591. re-raises the exception
that is currently being handled, which is also known as the 'active
exception'.  If there isn't currently an active exception, a *note
RuntimeError: 179. exception is raised indicating that this is an error.

Otherwise, *note raise: 591. evaluates the first expression as the
exception object.  It must be either a subclass or an instance of *note
BaseException: 55f.  If it is a class, the exception instance will be
obtained when needed by instantiating the class with no arguments.

The 'type' of the exception is the exception instance's class, the
'value' is the instance itself.

A traceback object is normally created automatically when an exception
is raised and attached to it as the *note __traceback__: 125b.
attribute.  You can create an exception and set your own traceback in
one step using the *note with_traceback(): 1f8a. exception method (which
returns the same exception instance, with its traceback set to its
argument), like so:

     raise Exception("foo occurred").with_traceback(tracebackobj)

The ‘from’ clause is used for exception chaining: if given, the second
'expression' must be another exception class or instance.  If the second
expression is an exception instance, it will be attached to the raised
exception as the *note __cause__: 125d. attribute (which is writable).
If the expression is an exception class, the class will be instantiated
and the resulting exception instance will be attached to the raised
exception as the ‘__cause__’ attribute.  If the raised exception is not
handled, both exceptions will be printed:

     >>> try:
     ...     print(1 / 0)
     ... except Exception as exc:
     ...     raise RuntimeError("Something bad happened") from exc
     ...
     Traceback (most recent call last):
       File "<stdin>", line 2, in <module>
         print(1 / 0)
               ~~^~~
     ZeroDivisionError: division by zero

     The above exception was the direct cause of the following exception:

     Traceback (most recent call last):
       File "<stdin>", line 4, in <module>
         raise RuntimeError("Something bad happened") from exc
     RuntimeError: Something bad happened

A similar mechanism works implicitly if a new exception is raised when
an exception is already being handled.  An exception may be handled when
an *note except: 171. or *note finally: 96e. clause, or a *note with:
577. statement, is used.  The previous exception is then attached as the
new exception's *note __context__: 125c. attribute:

     >>> try:
     ...     print(1 / 0)
     ... except:
     ...     raise RuntimeError("Something bad happened")
     ...
     Traceback (most recent call last):
       File "<stdin>", line 2, in <module>
         print(1 / 0)
               ~~^~~
     ZeroDivisionError: division by zero

     During handling of the above exception, another exception occurred:

     Traceback (most recent call last):
       File "<stdin>", line 4, in <module>
         raise RuntimeError("Something bad happened")
     RuntimeError: Something bad happened

Exception chaining can be explicitly suppressed by specifying *note
None: 61b. in the ‘from’ clause:

     >>> try:
     ...     print(1 / 0)
     ... except:
     ...     raise RuntimeError("Something bad happened") from None
     ...
     Traceback (most recent call last):
       File "<stdin>", line 4, in <module>
     RuntimeError: Something bad happened

Additional information on exceptions can be found in section *note 例外:
1eba, and information about handling exceptions is in section *note The
try statement: 68c.

在 3.3 版的變更: *note None: 61b. is now permitted as ‘Y’ in ‘raise X
from Y’.

Added the *note __suppress_context__: 1f8b. attribute to suppress
automatic display of the exception context.

在 3.11 版的變更: If the traceback of the active exception is modified
in an *note except: 171. clause, a subsequent ‘raise’ statement
re-raises the exception with the modified traceback.  Previously, the
exception was re-raised with the traceback it had when it was caught.


File: python.info,  Node: break 陳述式,  Next: continue 陳述式,  Prev: raise 陳述式,  Up: 簡單陳述式

4.7.9 ‘break’ 陳述式
--------------------

     break_stmt ::= "break"

*note break: a4c. may only occur syntactically nested in a *note for:
2c3. or *note while: 1b0b. loop, but not nested in a function or class
definition within that loop.

It terminates the nearest enclosing loop, skipping the optional ‘else’
clause if the loop has one.

If a *note for: 2c3. loop is terminated by *note break: a4c, the loop
control target keeps its current value.

When *note break: a4c. passes control out of a *note try: 68c. statement
with a *note finally: 96e. clause, that ‘finally’ clause is executed
before really leaving the loop.


File: python.info,  Node: continue 陳述式,  Next: import 陳述式,  Prev: break 陳述式,  Up: 簡單陳述式

4.7.10 ‘continue’ 陳述式
------------------------

     continue_stmt ::= "continue"

*note continue: 96d. may only occur syntactically nested in a *note for:
2c3. or *note while: 1b0b. loop, but not nested in a function or class
definition within that loop.  It continues with the next cycle of the
nearest enclosing loop.

When *note continue: 96d. passes control out of a *note try: 68c.
statement with a *note finally: 96e. clause, that ‘finally’ clause is
executed before really starting the next loop cycle.


File: python.info,  Node: import 陳述式,  Next: global 陳述式,  Prev: continue 陳述式,  Up: 簡單陳述式

4.7.11 ‘import’ 陳述式
----------------------

     import_stmt     ::= "import" module ["as" identifier] ("," module ["as" identifier])*
                         | "from" relative_module "import" identifier ["as" identifier]
                         ("," identifier ["as" identifier])*
                         | "from" relative_module "import" "(" identifier ["as" identifier]
                         ("," identifier ["as" identifier])* [","] ")"
                         | "from" relative_module "import" "*"
     module          ::= (identifier ".")* identifier
     relative_module ::= "."* module | "."+

The basic import statement (no *note from: 1242. clause) is executed in
two steps:

  1. find a module, loading and initializing it if necessary

  2. define a name or names in the local namespace for the scope where
     the *note import: 586. statement occurs.

When the statement contains multiple clauses (separated by commas) the
two steps are carried out separately for each clause, just as though the
clauses had been separated out into individual import statements.

The details of the first step, finding and loading modules, are
described in greater detail in the section on the *note import system:
1e01, which also describes the various types of packages and modules
that can be imported, as well as all the hooks that can be used to
customize the import system.  Note that failures in this step may
indicate either that the module could not be located, 'or' that an error
occurred while initializing the module, which includes execution of the
module's code.

If the requested module is retrieved successfully, it will be made
available in the local namespace in one of three ways:

   * If the module name is followed by ‘as’, then the name following
     ‘as’ is bound directly to the imported module.

   * If no other name is specified, and the module being imported is a
     top level module, the module's name is bound in the local namespace
     as a reference to the imported module

   * If the module being imported is 'not' a top level module, then the
     name of the top level package that contains the module is bound in
     the local namespace as a reference to the top level package.  The
     imported module must be accessed using its full qualified name
     rather than directly

The *note from: 1242. form uses a slightly more complex process:

  1. find the module specified in the *note from: 1242. clause, loading
     and initializing it if necessary;

  2. for each of the identifiers specified in the *note import: 586.
     clauses:

       1. check if the imported module has an attribute by that name

       2. if not, attempt to import a submodule with that name and then
          check the imported module again for that attribute

       3. if the attribute is not found, *note ImportError: 352. is
          raised.

       4. otherwise, a reference to that value is stored in the local
          namespace, using the name in the ‘as’ clause if it is present,
          otherwise using the attribute name

範例：

     import foo                 # foo imported and bound locally
     import foo.bar.baz         # foo, foo.bar, and foo.bar.baz imported, foo bound locally
     import foo.bar.baz as fbb  # foo, foo.bar, and foo.bar.baz imported, foo.bar.baz bound as fbb
     from foo.bar import baz    # foo, foo.bar, and foo.bar.baz imported, foo.bar.baz bound as baz
     from foo import attr       # foo imported and foo.attr bound as attr

If the list of identifiers is replaced by a star (‘'*'’), all public
names defined in the module are bound in the local namespace for the
scope where the *note import: 586. statement occurs.

The 'public names' defined by a module are determined by checking the
module's namespace for a variable named ‘__all__’; if defined, it must
be a sequence of strings which are names defined or imported by that
module.  The names given in ‘__all__’ are all considered public and are
required to exist.  If ‘__all__’ is not defined, the set of public names
includes all names found in the module's namespace which do not begin
with an underscore character (‘'_'’).  ‘__all__’ should contain the
entire public API. It is intended to avoid accidentally exporting items
that are not part of the API (such as library modules which were
imported and used within the module).

The wild card form of import -- ‘from module import *’ -- is only
allowed at the module level.  Attempting to use it in class or function
definitions will raise a *note SyntaxError: 173.

When specifying what module to import you do not have to specify the
absolute name of the module.  When a module or package is contained
within another package it is possible to make a relative import within
the same top package without having to mention the package name.  By
using leading dots in the specified module or package after *note from:
1242. you can specify how high to traverse up the current package
hierarchy without specifying exact names.  One leading dot means the
current package where the module making the import exists.  Two dots
means up one package level.  Three dots is up two levels, etc.  So if
you execute ‘from . import mod’ from a module in the ‘pkg’ package then
you will end up importing ‘pkg.mod’.  If you execute ‘from ..subpkg2
import mod’ from within ‘pkg.subpkg1’ you will import ‘pkg.subpkg2.mod’.
The specification for relative imports is contained in the *note Package
Relative Imports: 1ee5. section.

*note importlib.import_module(): 4bc. is provided to support
applications that determine dynamically the modules to be loaded.

引發一個附帶引數 ‘module’、‘filename’、‘sys.path’、‘sys.meta_path’、
‘sys.path_hooks’ 的*note 稽核事件: 17bd. ‘import’。

* Menu:

* Future statements::


File: python.info,  Node: Future statements,  Up: import 陳述式

4.7.11.1 Future statements
..........................

A 'future statement' is a directive to the compiler that a particular
module should be compiled using syntax or semantics that will be
available in a specified future release of Python where the feature
becomes standard.

The future statement is intended to ease migration to future versions of
Python that introduce incompatible changes to the language.  It allows
use of the new features on a per-module basis before the release in
which the feature becomes standard.

     future_stmt ::= "from" "__future__" "import" feature ["as" identifier]
                     ("," feature ["as" identifier])*
                     | "from" "__future__" "import" "(" feature ["as" identifier]
                     ("," feature ["as" identifier])* [","] ")"
     feature     ::= identifier

A future statement must appear near the top of the module.  The only
lines that can appear before a future statement are:

   * the module docstring (if any),

   * comments,

   * blank lines, and

   * other future statements.

The only feature that requires using the future statement is
‘annotations’ (see PEP 563(1)).

All historical features enabled by the future statement are still
recognized by Python 3.  The list includes ‘absolute_import’,
‘division’, ‘generators’, ‘generator_stop’, ‘unicode_literals’,
‘print_function’, ‘nested_scopes’ and ‘with_statement’.  They are all
redundant because they are always enabled, and only kept for backwards
compatibility.

A future statement is recognized and treated specially at compile time:
Changes to the semantics of core constructs are often implemented by
generating different code.  It may even be the case that a new feature
introduces new incompatible syntax (such as a new reserved word), in
which case the compiler may need to parse the module differently.  Such
decisions cannot be pushed off until runtime.

For any given release, the compiler knows which feature names have been
defined, and raises a compile-time error if a future statement contains
a feature not known to it.

The direct runtime semantics are the same as for any import statement:
there is a standard module *note __future__: 0, described later, and it
will be imported in the usual way at the time the future statement is
executed.

The interesting runtime semantics depend on the specific feature enabled
by the future statement.

Note that there is nothing special about the statement:

     import __future__ [as name]

That is not a future statement; it's an ordinary import statement with
no special semantics or syntax restrictions.

Code compiled by calls to the built-in functions *note exec(): 162. and
*note compile(): 178. that occur in a module ‘M’ containing a future
statement will, by default, use the new syntax or semantics associated
with the future statement.  This can be controlled by optional arguments
to *note compile(): 178. -- see the documentation of that function for
details.

A future statement typed at an interactive interpreter prompt will take
effect for the rest of the interpreter session.  If an interpreter is
started with the *note -i: 144a. option, is passed a script name to
execute, and the script includes a future statement, it will be in
effect in the interactive session started after the script is executed.

也參考
......

PEP 236(2) - Back to the __future__

     The original proposal for the __future__ mechanism.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0563/

   (2) https://peps.python.org/pep-0236/


File: python.info,  Node: global 陳述式,  Next: nonlocal 陳述式,  Prev: import 陳述式,  Up: 簡單陳述式

4.7.12 ‘global’ 陳述式
----------------------

     global_stmt ::= "global" identifier ("," identifier)*

The *note global: 170. statement is a declaration which holds for the
entire current code block.  It means that the listed identifiers are to
be interpreted as globals.  It would be impossible to assign to a global
variable without ‘global’, although free variables may refer to globals
without being declared global.

Names listed in a *note global: 170. statement must not be used in the
same code block textually preceding that ‘global’ statement.

Names listed in a *note global: 170. statement must not be defined as
formal parameters, or as targets in *note with: 577. statements or *note
except: 171. clauses, or in a *note for: 2c3. target list, *note class:
126a. definition, function definition, *note import: 586. statement, or
variable annotation.

'CPython 實作細節：' The current implementation does not enforce some of
these restrictions, but programs should not abuse this freedom, as
future implementations may enforce them or silently change the meaning
of the program.

'Programmer's note:' *note global: 170. is a directive to the parser.
It applies only to code parsed at the same time as the ‘global’
statement.  In particular, a ‘global’ statement contained in a string or
code object supplied to the built-in *note exec(): 162. function does
not affect the code block 'containing' the function call, and code
contained in such a string is unaffected by ‘global’ statements in the
code containing the function call.  The same applies to the *note
eval(): 163. and *note compile(): 178. functions.


File: python.info,  Node: nonlocal 陳述式,  Next: type 陳述式,  Prev: global 陳述式,  Up: 簡單陳述式

4.7.13 ‘nonlocal’ 陳述式
------------------------

     nonlocal_stmt ::= "nonlocal" identifier ("," identifier)*

When the definition of a function or class is nested (enclosed) within
the definitions of other functions, its nonlocal scopes are the local
scopes of the enclosing functions.  The *note nonlocal: 123e. statement
causes the listed identifiers to refer to names previously bound in
nonlocal scopes.  It allows encapsulated code to rebind such nonlocal
identifiers.  If a name is bound in more than one nonlocal scope, the
nearest binding is used.  If a name is not bound in any nonlocal scope,
or if there is no nonlocal scope, a *note SyntaxError: 173. is raised.

The nonlocal statement applies to the entire scope of a function or
class body.  A *note SyntaxError: 173. is raised if a variable is used
or assigned to prior to its nonlocal declaration in the scope.

也參考
......

PEP 3104(1) - Access to Names in Outer Scopes

     The specification for the *note nonlocal: 123e. statement.

'Programmer's note:' *note nonlocal: 123e. is a directive to the parser
and applies only to code parsed along with it.  See the note for the
*note global: 170. statement.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3104/


File: python.info,  Node: type 陳述式,  Prev: nonlocal 陳述式,  Up: 簡單陳述式

4.7.14 ‘type’ 陳述式
--------------------

     type_stmt ::= 'type' identifier [type_params] "=" expression

The ‘type’ statement declares a type alias, which is an instance of
*note typing.TypeAliasType: 3fb.

For example, the following statement creates a type alias:

     type Point = tuple[float, float]

This code is roughly equivalent to:

     annotation-def VALUE_OF_Point():
         return tuple[float, float]
     Point = typing.TypeAliasType("Point", VALUE_OF_Point())

‘annotation-def’ indicates an *note annotation scope: 16e, which behaves
mostly like a function, but with several small differences.

The value of the type alias is evaluated in the annotation scope.  It is
not evaluated when the type alias is created, but only when the value is
accessed through the type alias's ‘__value__’ attribute (see *note Lazy
evaluation: 3fd.).  This allows the type alias to refer to names that
are not yet defined.

Type aliases may be made generic by adding a *note type parameter list:
294. after the name.  See *note Generic type aliases: 3fc. for more.

‘type’ is a *note soft keyword: 7b0.

在 3.12 版被加入.

也參考
......

PEP 695(1) - Type Parameter Syntax

     Introduced the ‘type’ statement and syntax for generic classes and
     functions.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0695/


File: python.info,  Node: 複合陳述式,  Next: 最高層級元件,  Prev: 簡單陳述式,  Up: Python 語言參考手冊

4.8 複合陳述式
==============

Compound statements contain (groups of) other statements; they affect or
control the execution of those other statements in some way.  In
general, compound statements span multiple lines, although in simple
incarnations a whole compound statement may be contained in one line.

The *note if: 2c4, *note while: 1b0b. and *note for: 2c3. statements
implement traditional control flow constructs.  *note try: 68c.
specifies exception handlers and/or cleanup code for a group of
statements, while the *note with: 577. statement allows the execution of
initialization and finalization code around a block of code.  Function
and class definitions are also syntactically compound statements.

A compound statement consists of one or more 'clauses.'  A clause
consists of a header and a 'suite.'  The clause headers of a particular
compound statement are all at the same indentation level.  Each clause
header begins with a uniquely identifying keyword and ends with a colon.
A suite is a group of statements controlled by a clause.  A suite can be
one or more semicolon-separated simple statements on the same line as
the header, following the header's colon, or it can be one or more
indented statements on subsequent lines.  Only the latter form of a
suite can contain nested compound statements; the following is illegal,
mostly because it wouldn't be clear to which *note if: 2c4. clause a
following *note else: 172. clause would belong:

     if test1: if test2: print(x)

Also note that the semicolon binds tighter than the colon in this
context, so that in the following example, either all or none of the
*note print(): f18. calls are executed:

     if x < y < z: print(x); print(y); print(z)

Summarizing:

     compound_stmt ::= if_stmt
                       | while_stmt
                       | for_stmt
                       | try_stmt
                       | with_stmt
                       | match_stmt
                       | funcdef
                       | classdef
                       | async_with_stmt
                       | async_for_stmt
                       | async_funcdef
     suite         ::= stmt_list NEWLINE | NEWLINE INDENT statement+ DEDENT
     statement     ::= stmt_list NEWLINE | compound_stmt
     stmt_list     ::= simple_stmt (";" simple_stmt)* [";"]

Note that statements always end in a ‘NEWLINE’ possibly followed by a
‘DEDENT’.  Also note that optional continuation clauses always begin
with a keyword that cannot start a statement, thus there are no
ambiguities (the 'dangling *note else: 172.' problem is solved in Python
by requiring nested *note if: 2c4. statements to be indented).

The formatting of the grammar rules in the following sections places
each clause on a separate line for clarity.
* Menu:

* The if statement::
* The while statement::
* The for statement::
* The try statement::
* The with statement::
* The match statement::
* 函式定義::
* 類別定義::
* 協程: 協程<2>.
* Type parameter lists::


File: python.info,  Node: The if statement,  Next: The while statement,  Up: 複合陳述式

4.8.1 The ‘if’ statement
------------------------

The *note if: 2c4. statement is used for conditional execution:

     if_stmt ::= "if" assignment_expression ":" suite
                 ("elif" assignment_expression ":" suite)*
                 ["else" ":" suite]

It selects exactly one of the suites by evaluating the expressions one
by one until one is found to be true (see section *note Boolean
operations: 1f54. for the definition of true and false); then that suite
is executed (and no other part of the *note if: 2c4. statement is
executed or evaluated).  If all expressions are false, the suite of the
*note else: 172. clause, if present, is executed.


File: python.info,  Node: The while statement,  Next: The for statement,  Prev: The if statement,  Up: 複合陳述式

4.8.2 The ‘while’ statement
---------------------------

The *note while: 1b0b. statement is used for repeated execution as long
as an expression is true:

     while_stmt ::= "while" assignment_expression ":" suite
                    ["else" ":" suite]

This repeatedly tests the expression and, if it is true, executes the
first suite; if the expression is false (which may be the first time it
is tested) the suite of the ‘else’ clause, if present, is executed and
the loop terminates.

A *note break: a4c. statement executed in the first suite terminates the
loop without executing the ‘else’ clause's suite.  A *note continue:
96d. statement executed in the first suite skips the rest of the suite
and goes back to testing the expression.


File: python.info,  Node: The for statement,  Next: The try statement,  Prev: The while statement,  Up: 複合陳述式

4.8.3 The ‘for’ statement
-------------------------

The *note for: 2c3. statement is used to iterate over the elements of a
sequence (such as a string, tuple or list) or other iterable object:

     for_stmt ::= "for" target_list "in" starred_list ":" suite
                  ["else" ":" suite]

The ‘starred_list’ expression is evaluated once; it should yield an
*note iterable: 11bf. object.  An *note iterator: 192. is created for
that iterable.  The first item provided by the iterator is then assigned
to the target list using the standard rules for assignments (see *note
Assignment statements: 1eaf.), and the suite is executed.  This repeats
for each item provided by the iterator.  When the iterator is exhausted,
the suite in the ‘else’ clause, if present, is executed, and the loop
terminates.

A *note break: a4c. statement executed in the first suite terminates the
loop without executing the ‘else’ clause's suite.  A *note continue:
96d. statement executed in the first suite skips the rest of the suite
and continues with the next item, or with the ‘else’ clause if there is
no next item.

The for-loop makes assignments to the variables in the target list.
This overwrites all previous assignments to those variables including
those made in the suite of the for-loop:

     for i in range(10):
         print(i)
         i = 5             # this will not affect the for-loop
                           # because i will be overwritten with the next
                           # index in the range

Names in the target list are not deleted when the loop is finished, but
if the sequence is empty, they will not have been assigned to at all by
the loop.  Hint: the built-in type *note range(): 8e7. represents
immutable arithmetic sequences of integers.  For instance, iterating
‘range(3)’ successively yields 0, 1, and then 2.

在 3.11 版的變更: Starred elements are now allowed in the expression
list.


File: python.info,  Node: The try statement,  Next: The with statement,  Prev: The for statement,  Up: 複合陳述式

4.8.4 The ‘try’ statement
-------------------------

The ‘try’ statement specifies exception handlers and/or cleanup code for
a group of statements:

     try_stmt  ::= try1_stmt | try2_stmt | try3_stmt
     try1_stmt ::= "try" ":" suite
                   ("except" [expression ["as" identifier]] ":" suite)+
                   ["else" ":" suite]
                   ["finally" ":" suite]
     try2_stmt ::= "try" ":" suite
                   ("except" "*" expression ["as" identifier] ":" suite)+
                   ["else" ":" suite]
                   ["finally" ":" suite]
     try3_stmt ::= "try" ":" suite
                   "finally" ":" suite

Additional information on exceptions can be found in section *note 例外:
1eba, and information on using the *note raise: 591. statement to
generate exceptions may be found in section *note raise 陳述式: 591.

* Menu:

* except clause::
* except* 子句::
* else clause::
* finally clause::


File: python.info,  Node: except clause,  Next: except* 子句,  Up: The try statement

4.8.4.1 ‘except’ clause
.......................

The ‘except’ clause(s) specify one or more exception handlers.  When no
exception occurs in the *note try: 68c. clause, no exception handler is
executed.  When an exception occurs in the ‘try’ suite, a search for an
exception handler is started.  This search inspects the ‘except’ clauses
in turn until one is found that matches the exception.  An
expression-less ‘except’ clause, if present, must be last; it matches
any exception.

For an ‘except’ clause with an expression, the expression must evaluate
to an exception type or a tuple of exception types.  The raised
exception matches an ‘except’ clause whose expression evaluates to the
class or a *note non-virtual base class: 114e. of the exception object,
or to a tuple that contains such a class.

If no ‘except’ clause matches the exception, the search for an exception
handler continues in the surrounding code and on the invocation stack.
(1)

If the evaluation of an expression in the header of an ‘except’ clause
raises an exception, the original search for a handler is canceled and a
search starts for the new exception in the surrounding code and on the
call stack (it is treated as if the entire *note try: 68c. statement
raised the exception).

When a matching ‘except’ clause is found, the exception is assigned to
the target specified after the ‘as’ keyword in that ‘except’ clause, if
present, and the ‘except’ clause's suite is executed.  All ‘except’
clauses must have an executable block.  When the end of this block is
reached, execution continues normally after the entire *note try: 68c.
statement.  (This means that if two nested handlers exist for the same
exception, and the exception occurs in the ‘try’ clause of the inner
handler, the outer handler will not handle the exception.)

When an exception has been assigned using ‘as target’, it is cleared at
the end of the ‘except’ clause.  This is as if

     except E as N:
         foo

was translated to

     except E as N:
         try:
             foo
         finally:
             del N

This means the exception must be assigned to a different name to be able
to refer to it after the ‘except’ clause.  Exceptions are cleared
because with the traceback attached to them, they form a reference cycle
with the stack frame, keeping all locals in that frame alive until the
next garbage collection occurs.

Before an ‘except’ clause's suite is executed, the exception is stored
in the *note sys: c3. module, where it can be accessed from within the
body of the ‘except’ clause by calling *note sys.exception(): 631.  When
leaving an exception handler, the exception stored in the *note sys: c3.
module is reset to its previous value:

     >>> print(sys.exception())
     None
     >>> try:
     ...     raise TypeError
     ... except:
     ...     print(repr(sys.exception()))
     ...     try:
     ...          raise ValueError
     ...     except:
     ...         print(repr(sys.exception()))
     ...     print(repr(sys.exception()))
     ...
     TypeError()
     ValueError()
     TypeError()
     >>> print(sys.exception())
     None

   ---------- Footnotes ----------

   (1) The exception is propagated to the invocation stack unless there
is a *note finally: 96e. clause which happens to raise another
exception.  That new exception causes the old one to be lost.


File: python.info,  Node: except* 子句,  Next: else clause,  Prev: except clause,  Up: The try statement

4.8.4.2 ‘except*’ 子句
......................

The ‘except*’ clause(s) are used for handling *note ExceptionGroup:
19c.s.  The exception type for matching is interpreted as in the case of
*note except: 171, but in the case of exception groups we can have
partial matches when the type matches some of the exceptions in the
group.  This means that multiple ‘except*’ clauses can execute, each
handling part of the exception group.  Each clause executes at most once
and handles an exception group of all matching exceptions.  Each
exception in the group is handled by at most one ‘except*’ clause, the
first that matches it.

     >>> try:
     ...     raise ExceptionGroup("eg",
     ...         [ValueError(1), TypeError(2), OSError(3), OSError(4)])
     ... except* TypeError as e:
     ...     print(f'caught {type(e)} with nested {e.exceptions}')
     ... except* OSError as e:
     ...     print(f'caught {type(e)} with nested {e.exceptions}')
     ...
     caught <class 'ExceptionGroup'> with nested (TypeError(2),)
     caught <class 'ExceptionGroup'> with nested (OSError(3), OSError(4))
       + Exception Group Traceback (most recent call last):
       |   File "<stdin>", line 2, in <module>
       | ExceptionGroup: eg
       +-+---------------- 1 ----------------
         | ValueError: 1
         +------------------------------------

Any remaining exceptions that were not handled by any ‘except*’ clause
are re-raised at the end, along with all exceptions that were raised
from within the ‘except*’ clauses.  If this list contains more than one
exception to reraise, they are combined into an exception group.

If the raised exception is not an exception group and its type matches
one of the ‘except*’ clauses, it is caught and wrapped by an exception
group with an empty message string.

     >>> try:
     ...     raise BlockingIOError
     ... except* BlockingIOError as e:
     ...     print(repr(e))
     ...
     ExceptionGroup('', (BlockingIOError()))

An ‘except*’ clause must have a matching expression; it cannot be
‘except*:’.  Furthermore, this expression cannot contain exception group
types, because that would have ambiguous semantics.

It is not possible to mix *note except: 171. and ‘except*’ in the same
*note try: 68c.  *note break: a4c, *note continue: 96d. and *note
return: 972. cannot appear in an ‘except*’ clause.


File: python.info,  Node: else clause,  Next: finally clause,  Prev: except* 子句,  Up: The try statement

4.8.4.3 ‘else’ clause
.....................

The optional ‘else’ clause is executed if the control flow leaves the
*note try: 68c. suite, no exception was raised, and no *note return:
972, *note continue: 96d, or *note break: a4c. statement was executed.
Exceptions in the ‘else’ clause are not handled by the preceding *note
except: 171. clauses.


File: python.info,  Node: finally clause,  Prev: else clause,  Up: The try statement

4.8.4.4 ‘finally’ clause
........................

If ‘finally’ is present, it specifies a 'cleanup' handler.  The *note
try: 68c. clause is executed, including any *note except: 171. and *note
else: 172. clauses.  If an exception occurs in any of the clauses and is
not handled, the exception is temporarily saved.  The ‘finally’ clause
is executed.  If there is a saved exception it is re-raised at the end
of the ‘finally’ clause.  If the ‘finally’ clause raises another
exception, the saved exception is set as the context of the new
exception.  If the ‘finally’ clause executes a *note return: 972, *note
break: a4c. or *note continue: 96d. statement, the saved exception is
discarded:

     >>> def f():
     ...     try:
     ...         1/0
     ...     finally:
     ...         return 42
     ...
     >>> f()
     42

The exception information is not available to the program during
execution of the ‘finally’ clause.

When a *note return: 972, *note break: a4c. or *note continue: 96d.
statement is executed in the *note try: 68c. suite of a
‘try’...‘finally’ statement, the ‘finally’ clause is also executed 'on
the way out.'

The return value of a function is determined by the last *note return:
972. statement executed.  Since the ‘finally’ clause always executes, a
‘return’ statement executed in the ‘finally’ clause will always be the
last one executed:

     >>> def foo():
     ...     try:
     ...         return 'try'
     ...     finally:
     ...         return 'finally'
     ...
     >>> foo()
     'finally'

在 3.8 版的變更: Prior to Python 3.8, a *note continue: 96d. statement
was illegal in the ‘finally’ clause due to a problem with the
implementation.


File: python.info,  Node: The with statement,  Next: The match statement,  Prev: The try statement,  Up: 複合陳述式

4.8.5 The ‘with’ statement
--------------------------

The *note with: 577. statement is used to wrap the execution of a block
with methods defined by a context manager (see section *note With
Statement Context Managers: 1e93.).  This allows common *note try:
68c...*note except: 171...*note finally: 96e. usage patterns to be
encapsulated for convenient reuse.

     with_stmt          ::= "with" ( "(" with_stmt_contents ","? ")" | with_stmt_contents ) ":" suite
     with_stmt_contents ::= with_item ("," with_item)*
     with_item          ::= expression ["as" target]

The execution of the *note with: 577. statement with one "item" proceeds
as follows:

  1. The context expression (the expression given in the *note
     with_item: 1fb8.) is evaluated to obtain a context manager.

  2. The context manager's *note __enter__(): 56c. is loaded for later
     use.

  3. The context manager's *note __exit__(): 1293. is loaded for later
     use.

  4. The context manager's *note __enter__(): 56c. method is invoked.

  5. If a target was included in the *note with: 577. statement, the
     return value from *note __enter__(): 56c. is assigned to it.

          備註: The *note with: 577. statement guarantees that if the
          *note __enter__(): 56c. method returns without an error, then
          *note __exit__(): 1293. will always be called.  Thus, if an
          error occurs during the assignment to the target list, it will
          be treated the same as an error occurring within the suite
          would be.  See step 7 below.

  6. The suite is executed.

  7. The context manager's *note __exit__(): 1293. method is invoked.
     If an exception caused the suite to be exited, its type, value, and
     traceback are passed as arguments to *note __exit__(): 1293.
     Otherwise, three *note None: 61b. arguments are supplied.

     If the suite was exited due to an exception, and the return value
     from the *note __exit__(): 1293. method was false, the exception is
     reraised.  If the return value was true, the exception is
     suppressed, and execution continues with the statement following
     the *note with: 577. statement.

     If the suite was exited for any reason other than an exception, the
     return value from *note __exit__(): 1293. is ignored, and execution
     proceeds at the normal location for the kind of exit that was
     taken.

The following code:

     with EXPRESSION as TARGET:
         SUITE

is semantically equivalent to:

     manager = (EXPRESSION)
     enter = type(manager).__enter__
     exit = type(manager).__exit__
     value = enter(manager)
     hit_except = False

     try:
         TARGET = value
         SUITE
     except:
         hit_except = True
         if not exit(manager, *sys.exc_info()):
             raise
     finally:
         if not hit_except:
             exit(manager, None, None, None)

With more than one item, the context managers are processed as if
multiple *note with: 577. statements were nested:

     with A() as a, B() as b:
         SUITE

is semantically equivalent to:

     with A() as a:
         with B() as b:
             SUITE

You can also write multi-item context managers in multiple lines if the
items are surrounded by parentheses.  For example:

     with (
         A() as a,
         B() as b,
     ):
         SUITE

在 3.1 版的變更: Support for multiple context expressions.

在 3.10 版的變更: Support for using grouping parentheses to break the
statement in multiple lines.

也參考
......

PEP 343(1) - The "with" statement

     The specification, background, and examples for the Python *note
     with: 577. statement.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0343/


File: python.info,  Node: The match statement,  Next: 函式定義,  Prev: The with statement,  Up: 複合陳述式

4.8.6 The ‘match’ statement
---------------------------

在 3.10 版被加入.

The match statement is used for pattern matching.  Syntax:

     match_stmt   ::= 'match' subject_expr ":" NEWLINE INDENT case_block+ DEDENT
     subject_expr ::= star_named_expression "," star_named_expressions?
                      | named_expression
     case_block   ::= 'case' patterns [guard] ":" block

     備註: This section uses single quotes to denote *note soft
     keywords: 7b0.

Pattern matching takes a pattern as input (following ‘case’) and a
subject value (following ‘match’).  The pattern (which may contain
subpatterns) is matched against the subject value.  The outcomes are:

   * A match success or failure (also termed a pattern success or
     failure).

   * Possible binding of matched values to a name.  The prerequisites
     for this are further discussed below.

The ‘match’ and ‘case’ keywords are *note soft keywords: 7b0.

也參考
......

   * PEP 634(1) - Structural Pattern Matching: Specification

   * PEP 636(2) - Structural Pattern Matching: Tutorial

* Menu:

* Overview::
* Guards::
* Irrefutable Case Blocks::
* Patterns::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0634/

   (2) https://peps.python.org/pep-0636/


File: python.info,  Node: Overview,  Next: Guards,  Up: The match statement

4.8.6.1 Overview
................

Here's an overview of the logical flow of a match statement:

  1. The subject expression ‘subject_expr’ is evaluated and a resulting
     subject value obtained.  If the subject expression contains a
     comma, a tuple is constructed using *note the standard rules: 1fbe.

  2. Each pattern in a ‘case_block’ is attempted to match with the
     subject value.  The specific rules for success or failure are
     described below.  The match attempt can also bind some or all of
     the standalone names within the pattern.  The precise pattern
     binding rules vary per pattern type and are specified below.  'Name
     bindings made during a successful pattern match outlive the
     executed block and can be used after the match statement'.

          備註: During failed pattern matches, some subpatterns may
          succeed.  Do not rely on bindings being made for a failed
          match.  Conversely, do not rely on variables remaining
          unchanged after a failed match.  The exact behavior is
          dependent on implementation and may vary.  This is an
          intentional decision made to allow different implementations
          to add optimizations.

  3. If the pattern succeeds, the corresponding guard (if present) is
     evaluated.  In this case all name bindings are guaranteed to have
     happened.

        * If the guard evaluates as true or is missing, the ‘block’
          inside ‘case_block’ is executed.

        * Otherwise, the next ‘case_block’ is attempted as described
          above.

        * If there are no further case blocks, the match statement is
          completed.

     備註: Users should generally never rely on a pattern being
     evaluated.  Depending on implementation, the interpreter may cache
     values or use other optimizations which skip repeated evaluations.

A sample match statement:

     >>> flag = False
     >>> match (100, 200):
     ...    case (100, 300):  # Mismatch: 200 != 300
     ...        print('Case 1')
     ...    case (100, 200) if flag:  # Successful match, but guard fails
     ...        print('Case 2')
     ...    case (100, y):  # Matches and binds y to 200
     ...        print(f'Case 3, y: {y}')
     ...    case _:  # Pattern not attempted
     ...        print('Case 4, I match anything!')
     ...
     Case 3, y: 200

In this case, ‘if flag’ is a guard.  Read more about that in the next
section.


File: python.info,  Node: Guards,  Next: Irrefutable Case Blocks,  Prev: Overview,  Up: The match statement

4.8.6.2 Guards
..............

     guard ::= "if" named_expression

A ‘guard’ (which is part of the ‘case’) must succeed for code inside the
‘case’ block to execute.  It takes the form: *note if: 2c4. followed by
an expression.

The logical flow of a ‘case’ block with a ‘guard’ follows:

  1. Check that the pattern in the ‘case’ block succeeded.  If the
     pattern failed, the ‘guard’ is not evaluated and the next ‘case’
     block is checked.

  2. If the pattern succeeded, evaluate the ‘guard’.

        * If the ‘guard’ condition evaluates as true, the case block is
          selected.

        * If the ‘guard’ condition evaluates as false, the case block is
          not selected.

        * If the ‘guard’ raises an exception during evaluation, the
          exception bubbles up.

Guards are allowed to have side effects as they are expressions.  Guard
evaluation must proceed from the first to the last case block, one at a
time, skipping case blocks whose pattern(s) don't all succeed.  (I.e.,
guard evaluation must happen in order.)  Guard evaluation must stop once
a case block is selected.


File: python.info,  Node: Irrefutable Case Blocks,  Next: Patterns,  Prev: Guards,  Up: The match statement

4.8.6.3 Irrefutable Case Blocks
...............................

An irrefutable case block is a match-all case block.  A match statement
may have at most one irrefutable case block, and it must be last.

A case block is considered irrefutable if it has no guard and its
pattern is irrefutable.  A pattern is considered irrefutable if we can
prove from its syntax alone that it will always succeed.  Only the
following patterns are irrefutable:

   * *note AS Patterns: 1fc3. whose left-hand side is irrefutable

   * *note OR Patterns: 1fc4. containing at least one irrefutable
     pattern

   * *note Capture Patterns: 1fc5.

   * *note Wildcard Patterns: 7b2.

   * parenthesized irrefutable patterns


File: python.info,  Node: Patterns,  Prev: Irrefutable Case Blocks,  Up: The match statement

4.8.6.4 Patterns
................

     備註: This section uses grammar notations beyond standard EBNF:

        * the notation ‘SEP.RULE+’ is shorthand for ‘RULE (SEP RULE)*’

        * the notation ‘!RULE’ is shorthand for a negative lookahead
          assertion

The top-level syntax for ‘patterns’ is:

     patterns       ::= open_sequence_pattern | pattern
     pattern        ::= as_pattern | or_pattern
     closed_pattern ::= | literal_pattern
                        | capture_pattern
                        | wildcard_pattern
                        | value_pattern
                        | group_pattern
                        | sequence_pattern
                        | mapping_pattern
                        | class_pattern

The descriptions below will include a description "in simple terms" of
what a pattern does for illustration purposes (credits to Raymond
Hettinger for a document that inspired most of the descriptions).  Note
that these descriptions are purely for illustration purposes and 'may
not' reflect the underlying implementation.  Furthermore, they do not
cover all valid forms.

* Menu:

* OR Patterns::
* AS Patterns::
* Literal Patterns::
* Capture Patterns::
* Wildcard Patterns::
* Value Patterns::
* Group Patterns::
* Sequence Patterns::
* Mapping Patterns::
* Class Patterns::


File: python.info,  Node: OR Patterns,  Next: AS Patterns,  Up: Patterns

4.8.6.5 OR Patterns
...................

An OR pattern is two or more patterns separated by vertical bars ‘|’.
Syntax:

     or_pattern ::= "|".closed_pattern+

Only the final subpattern may be *note irrefutable: 1fc1, and each
subpattern must bind the same set of names to avoid ambiguity.

An OR pattern matches each of its subpatterns in turn to the subject
value, until one succeeds.  The OR pattern is then considered
successful.  Otherwise, if none of the subpatterns succeed, the OR
pattern fails.

In simple terms, ‘P1 | P2 | ...’ will try to match ‘P1’, if it fails it
will try to match ‘P2’, succeeding immediately if any succeeds, failing
otherwise.


File: python.info,  Node: AS Patterns,  Next: Literal Patterns,  Prev: OR Patterns,  Up: Patterns

4.8.6.6 AS Patterns
...................

An AS pattern matches an OR pattern on the left of the *note as: 1fb4.
keyword against a subject.  Syntax:

     as_pattern ::= or_pattern "as" capture_pattern

If the OR pattern fails, the AS pattern fails.  Otherwise, the AS
pattern binds the subject to the name on the right of the as keyword and
succeeds.  ‘capture_pattern’ cannot be a ‘_’.

In simple terms ‘P as NAME’ will match with ‘P’, and on success it will
set ‘NAME = <subject>’.


File: python.info,  Node: Literal Patterns,  Next: Capture Patterns,  Prev: AS Patterns,  Up: Patterns

4.8.6.7 Literal Patterns
........................

A literal pattern corresponds to most *note literals: 1d94. in Python.
Syntax:

     literal_pattern ::= signed_number
                         | signed_number "+" NUMBER
                         | signed_number "-" NUMBER
                         | strings
                         | "None"
                         | "True"
                         | "False"
     signed_number   ::= ["-"] NUMBER

The rule ‘strings’ and the token ‘NUMBER’ are defined in the *note
standard Python grammar: 1fd2.  Triple-quoted strings are supported.
Raw strings and byte strings are supported.  *note f-string（f 字串）:
94d. are not supported.

The forms ‘signed_number '+' NUMBER’ and ‘signed_number '-' NUMBER’ are
for expressing *note complex numbers: 1dca.; they require a real number
on the left and an imaginary number on the right.  E.g.  ‘3 + 4j’.

In simple terms, ‘LITERAL’ will succeed only if ‘<subject> == LITERAL’.
For the singletons ‘None’, ‘True’ and ‘False’, the *note is: 2c6.
operator is used.


File: python.info,  Node: Capture Patterns,  Next: Wildcard Patterns,  Prev: Literal Patterns,  Up: Patterns

4.8.6.8 Capture Patterns
........................

A capture pattern binds the subject value to a name.  Syntax:

     capture_pattern ::= !'_' NAME

A single underscore ‘_’ is not a capture pattern (this is what ‘!'_'’
expresses).  It is instead treated as a *note wildcard_pattern: 1fd5.

In a given pattern, a given name can only be bound once.  E.g.  ‘case x,
x: ...’ is invalid while ‘case [x] | x: ...’ is allowed.

Capture patterns always succeed.  The binding follows scoping rules
established by the assignment expression operator in PEP 572(1); the
name becomes a local variable in the closest containing function scope
unless there's an applicable *note global: 170. or *note nonlocal: 123e.
statement.

In simple terms ‘NAME’ will always succeed and it will set ‘NAME =
<subject>’.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0572/


File: python.info,  Node: Wildcard Patterns,  Next: Value Patterns,  Prev: Capture Patterns,  Up: Patterns

4.8.6.9 Wildcard Patterns
.........................

A wildcard pattern always succeeds (matches anything) and binds no name.
Syntax:

     wildcard_pattern ::= '_'

‘_’ is a *note soft keyword: 7b0. within any pattern, but only within
patterns.  It is an identifier, as usual, even within ‘match’ subject
expressions, ‘guard’s, and ‘case’ blocks.

In simple terms, ‘_’ will always succeed.


File: python.info,  Node: Value Patterns,  Next: Group Patterns,  Prev: Wildcard Patterns,  Up: Patterns

4.8.6.10 Value Patterns
.......................

A value pattern represents a named value in Python.  Syntax:

     value_pattern ::= attr
     attr          ::= name_or_attr "." NAME
     name_or_attr  ::= attr | NAME

The dotted name in the pattern is looked up using standard Python *note
name resolution rules: 1eb1.  The pattern succeeds if the value found
compares equal to the subject value (using the ‘==’ equality operator).

In simple terms ‘NAME1.NAME2’ will succeed only if ‘<subject> ==
NAME1.NAME2’

     備註: If the same value occurs multiple times in the same match
     statement, the interpreter may cache the first value found and
     reuse it rather than repeat the same lookup.  This cache is
     strictly tied to a given execution of a given match statement.


File: python.info,  Node: Group Patterns,  Next: Sequence Patterns,  Prev: Value Patterns,  Up: Patterns

4.8.6.11 Group Patterns
.......................

A group pattern allows users to add parentheses around patterns to
emphasize the intended grouping.  Otherwise, it has no additional
syntax.  Syntax:

     group_pattern ::= "(" pattern ")"

In simple terms ‘(P)’ has the same effect as ‘P’.


File: python.info,  Node: Sequence Patterns,  Next: Mapping Patterns,  Prev: Group Patterns,  Up: Patterns

4.8.6.12 Sequence Patterns
..........................

A sequence pattern contains several subpatterns to be matched against
sequence elements.  The syntax is similar to the unpacking of a list or
tuple.

     sequence_pattern       ::= "[" [maybe_sequence_pattern] "]"
                                | "(" [open_sequence_pattern] ")"
     open_sequence_pattern  ::= maybe_star_pattern "," [maybe_sequence_pattern]
     maybe_sequence_pattern ::= ",".maybe_star_pattern+ ","?
     maybe_star_pattern     ::= star_pattern | pattern
     star_pattern           ::= "*" (capture_pattern | wildcard_pattern)

There is no difference if parentheses or square brackets are used for
sequence patterns (i.e.  ‘(...)’ vs ‘[...]’ ).

     備註: A single pattern enclosed in parentheses without a trailing
     comma (e.g.  ‘(3 | 4)’) is a *note group pattern: 1fdc.  While a
     single pattern enclosed in square brackets (e.g.  ‘[3 | 4]’) is
     still a sequence pattern.

At most one star subpattern may be in a sequence pattern.  The star
subpattern may occur in any position.  If no star subpattern is present,
the sequence pattern is a fixed-length sequence pattern; otherwise it is
a variable-length sequence pattern.

The following is the logical flow for matching a sequence pattern
against a subject value:

  1. If the subject value is not a sequence (1), the sequence pattern
     fails.

  2. If the subject value is an instance of ‘str’, ‘bytes’ or
     ‘bytearray’ the sequence pattern fails.

  3. The subsequent steps depend on whether the sequence pattern is
     fixed or variable-length.

     If the sequence pattern is fixed-length:

       1. If the length of the subject sequence is not equal to the
          number of subpatterns, the sequence pattern fails

       2. Subpatterns in the sequence pattern are matched to their
          corresponding items in the subject sequence from left to
          right.  Matching stops as soon as a subpattern fails.  If all
          subpatterns succeed in matching their corresponding item, the
          sequence pattern succeeds.

     Otherwise, if the sequence pattern is variable-length:

       1. If the length of the subject sequence is less than the number
          of non-star subpatterns, the sequence pattern fails.

       2. The leading non-star subpatterns are matched to their
          corresponding items as for fixed-length sequences.

       3. If the previous step succeeds, the star subpattern matches a
          list formed of the remaining subject items, excluding the
          remaining items corresponding to non-star subpatterns
          following the star subpattern.

       4. Remaining non-star subpatterns are matched to their
          corresponding subject items, as for a fixed-length sequence.

          備註: The length of the subject sequence is obtained via *note
          len(): 5d4. (i.e.  via the ‘__len__()’ protocol).  This length
          may be cached by the interpreter in a similar manner as *note
          value patterns: 1fd8.

In simple terms ‘[P1, P2, P3,’ ...  ‘, P<N>]’ matches only if all the
following happens:

   * check ‘<subject>’ is a sequence

   * ‘len(subject) == <N>’

   * ‘P1’ matches ‘<subject>[0]’ (note that this match can also bind
     names)

   * ‘P2’ matches ‘<subject>[1]’ (note that this match can also bind
     names)

   * ...  and so on for the corresponding pattern/element.

   ---------- Footnotes ----------

   (1) In pattern matching, a sequence is defined as one of the
following:

   * a class that inherits from *note collections.abc.Sequence: 115c.

   * a Python class that has been registered as *note
     collections.abc.Sequence: 115c.

   * a builtin class that has its (CPython) *note Py_TPFLAGS_SEQUENCE:
     17a7. bit set

   * a class that inherits from any of the above

The following standard library classes are sequences:

   * *note array.array: 186.

   * *note collections.deque: 580.

   * *note list: 5b6.

   * *note memoryview: 40f.

   * *note range: 8e7.

   * *note tuple: 322.

     備註: Subject values of type ‘str’, ‘bytes’, and ‘bytearray’ do not
     match sequence patterns.


File: python.info,  Node: Mapping Patterns,  Next: Class Patterns,  Prev: Sequence Patterns,  Up: Patterns

4.8.6.13 Mapping Patterns
.........................

A mapping pattern contains one or more key-value patterns.  The syntax
is similar to the construction of a dictionary.  Syntax:

     mapping_pattern     ::= "{" [items_pattern] "}"
     items_pattern       ::= ",".key_value_pattern+ ","?
     key_value_pattern   ::= (literal_pattern | value_pattern) ":" pattern
                             | double_star_pattern
     double_star_pattern ::= "**" capture_pattern

At most one double star pattern may be in a mapping pattern.  The double
star pattern must be the last subpattern in the mapping pattern.

Duplicate keys in mapping patterns are disallowed.  Duplicate literal
keys will raise a *note SyntaxError: 173.  Two keys that otherwise have
the same value will raise a *note ValueError: 1e7. at runtime.

The following is the logical flow for matching a mapping pattern against
a subject value:

  1. If the subject value is not a mapping (1),the mapping pattern
     fails.

  2. If every key given in the mapping pattern is present in the subject
     mapping, and the pattern for each key matches the corresponding
     item of the subject mapping, the mapping pattern succeeds.

  3. If duplicate keys are detected in the mapping pattern, the pattern
     is considered invalid.  A *note SyntaxError: 173. is raised for
     duplicate literal values; or a *note ValueError: 1e7. for named
     keys of the same value.

     備註: Key-value pairs are matched using the two-argument form of
     the mapping subject's ‘get()’ method.  Matched key-value pairs must
     already be present in the mapping, and not created on-the-fly via
     ‘__missing__()’ or *note __getitem__(): 266.

In simple terms ‘{KEY1: P1, KEY2: P2, ... }’ matches only if all the
following happens:

   * check ‘<subject>’ is a mapping

   * ‘KEY1 in <subject>’

   * ‘P1’ matches ‘<subject>[KEY1]’

   * ...  and so on for the corresponding KEY/pattern pair.

   ---------- Footnotes ----------

   (1) In pattern matching, a mapping is defined as one of the
following:

   * a class that inherits from *note collections.abc.Mapping: 86f.

   * a Python class that has been registered as *note
     collections.abc.Mapping: 86f.

   * a builtin class that has its (CPython) *note Py_TPFLAGS_MAPPING:
     17a6. bit set

   * a class that inherits from any of the above

The standard library classes *note dict: 23b. and *note
types.MappingProxyType: 414. are mappings.


File: python.info,  Node: Class Patterns,  Prev: Mapping Patterns,  Up: Patterns

4.8.6.14 Class Patterns
.......................

A class pattern represents a class and its positional and keyword
arguments (if any).  Syntax:

     class_pattern       ::= name_or_attr "(" [pattern_arguments ","?] ")"
     pattern_arguments   ::= positional_patterns ["," keyword_patterns]
                             | keyword_patterns
     positional_patterns ::= ",".pattern+
     keyword_patterns    ::= ",".keyword_pattern+
     keyword_pattern     ::= NAME "=" pattern

The same keyword should not be repeated in class patterns.

The following is the logical flow for matching a class pattern against a
subject value:

  1. If ‘name_or_attr’ is not an instance of the builtin *note type:
     cef. , raise *note TypeError: 4dd.

  2. If the subject value is not an instance of ‘name_or_attr’ (tested
     via *note isinstance(): 3e8.), the class pattern fails.

  3. If no pattern arguments are present, the pattern succeeds.
     Otherwise, the subsequent steps depend on whether keyword or
     positional argument patterns are present.

     For a number of built-in types (specified below), a single
     positional subpattern is accepted which will match the entire
     subject; for these types keyword patterns also work as for other
     types.

     If only keyword patterns are present, they are processed as
     follows, one by one:

     I. The keyword is looked up as an attribute on the subject.

             * If this raises an exception other than *note
               AttributeError: 2f6, the exception bubbles up.

             * If this raises *note AttributeError: 2f6, the class
               pattern has failed.

             * Else, the subpattern associated with the keyword pattern
               is matched against the subject's attribute value.  If
               this fails, the class pattern fails; if this succeeds,
               the match proceeds to the next keyword.

     II. If all keyword patterns succeed, the class pattern succeeds.

     If any positional patterns are present, they are converted to
     keyword patterns using the *note __match_args__: 17c2. attribute on
     the class ‘name_or_attr’ before matching:

     I. The equivalent of ‘getattr(cls, "__match_args__", ())’ is
     called.

             * If this raises an exception, the exception bubbles up.

             * If the returned value is not a tuple, the conversion
               fails and *note TypeError: 4dd. is raised.

             * If there are more positional patterns than
               ‘len(cls.__match_args__)’, *note TypeError: 4dd. is
               raised.

             * Otherwise, positional pattern ‘i’ is converted to a
               keyword pattern using ‘__match_args__[i]’ as the keyword.
               ‘__match_args__[i]’ must be a string; if not *note
               TypeError: 4dd. is raised.

             * If there are duplicate keywords, *note TypeError: 4dd. is
               raised.

          也參考
          ......

          *note Customizing positional arguments in class pattern
          matching: 1e96.

     II. Once all positional patterns have been converted to keyword patterns,

          the match proceeds as if there were only keyword patterns.

     For the following built-in types the handling of positional
     subpatterns is different:

        * *note bool: 40e.

        * *note bytearray: 4e3.

        * *note bytes: 1a5.

        * *note dict: 23b.

        * *note float: 2c8.

        * *note frozenset: 57e.

        * *note int: 23c.

        * *note list: 5b6.

        * *note set: 57d.

        * *note str: 3f2.

        * *note tuple: 322.

     These classes accept a single positional argument, and the pattern
     there is matched against the whole object rather than an attribute.
     For example ‘int(0|1)’ matches the value ‘0’, but not the value
     ‘0.0’.

In simple terms ‘CLS(P1, attr=P2)’ matches only if the following
happens:

   * ‘isinstance(<subject>, CLS)’

   * convert ‘P1’ to a keyword pattern using ‘CLS.__match_args__’

   * For each keyword argument ‘attr=P2’:

        * ‘hasattr(<subject>, "attr")’

        * ‘P2’ matches ‘<subject>.attr’

   * ...  and so on for the corresponding keyword argument/pattern pair.

也參考
......

   * PEP 634(1) - Structural Pattern Matching: Specification

   * PEP 636(2) - Structural Pattern Matching: Tutorial

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0634/

   (2) https://peps.python.org/pep-0636/


File: python.info,  Node: 函式定義,  Next: 類別定義,  Prev: The match statement,  Up: 複合陳述式

4.8.7 函式定義
--------------

A function definition defines a user-defined function object (see
section *note 標準型別階層: 1dd6.):

     funcdef                   ::= [decorators] "def" funcname [type_params] "(" [parameter_list] ")"
                                   ["->" expression] ":" suite
     decorators                ::= decorator+
     decorator                 ::= "@" assignment_expression NEWLINE
     parameter_list            ::= defparameter ("," defparameter)* "," "/" ["," [parameter_list_no_posonly]]
                                     | parameter_list_no_posonly
     parameter_list_no_posonly ::= defparameter ("," defparameter)* ["," [parameter_list_starargs]]
                                   | parameter_list_starargs
     parameter_list_starargs   ::= "*" [parameter] ("," defparameter)* ["," ["**" parameter [","]]]
                                   | "**" parameter [","]
     parameter                 ::= identifier [":" expression]
     defparameter              ::= parameter ["=" expression]
     funcname                  ::= identifier

A function definition is an executable statement.  Its execution binds
the function name in the current local namespace to a function object (a
wrapper around the executable code for the function).  This function
object contains a reference to the current global namespace as the
global namespace to be used when the function is called.

The function definition does not execute the function body; this gets
executed only when the function is called.  (1)

A function definition may be wrapped by one or more *note decorator:
6d5. expressions.  Decorator expressions are evaluated when the function
is defined, in the scope that contains the function definition.  The
result must be a callable, which is invoked with the function object as
the only argument.  The returned value is bound to the function name
instead of the function object.  Multiple decorators are applied in
nested fashion.  For example, the following code

     @f1(arg)
     @f2
     def func(): pass

大致等價於：

     def func(): pass
     func = f1(arg)(f2(func))

except that the original function is not temporarily bound to the name
‘func’.

在 3.9 版的變更: Functions may be decorated with any valid *note
assignment_expression: 1eb4.  Previously, the grammar was much more
restrictive; see PEP 614(2) for details.

A list of *note type parameters: 294. may be given in square brackets
between the function's name and the opening parenthesis for its
parameter list.  This indicates to static type checkers that the
function is generic.  At runtime, the type parameters can be retrieved
from the function's *note __type_params__: 1def. attribute.  See *note
Generic functions: 3f9. for more.

在 3.12 版的變更: Type parameter lists are new in Python 3.12.

When one or more *note parameters: 1dee. have the form 'parameter' ‘=’
'expression', the function is said to have "default parameter values."
For a parameter with a default value, the corresponding *note argument:
3ef. may be omitted from a call, in which case the parameter's default
value is substituted.  If a parameter has a default value, all following
parameters up until the "‘*’" must also have a default value -- this is
a syntactic restriction that is not expressed by the grammar.

'Default parameter values are evaluated from left to right when the
function definition is executed.'  This means that the expression is
evaluated once, when the function is defined, and that the same
"pre-computed" value is used for each call.  This is especially
important to understand when a default parameter value is a mutable
object, such as a list or a dictionary: if the function modifies the
object (e.g.  by appending an item to a list), the default parameter
value is in effect modified.  This is generally not what was intended.
A way around this is to use ‘None’ as the default, and explicitly test
for it in the body of the function, e.g.:

     def whats_on_the_telly(penguin=None):
         if penguin is None:
             penguin = []
         penguin.append("property of the zoo")
         return penguin

Function call semantics are described in more detail in section *note
Calls: d23.  A function call always assigns values to all parameters
mentioned in the parameter list, either from positional arguments, from
keyword arguments, or from default values.  If the form "‘*identifier’"
is present, it is initialized to a tuple receiving any excess positional
parameters, defaulting to the empty tuple.  If the form "‘**identifier’"
is present, it is initialized to a new ordered mapping receiving any
excess keyword arguments, defaulting to a new empty mapping of the same
type.  Parameters after "‘*’" or "‘*identifier’" are keyword-only
parameters and may only be passed by keyword arguments.  Parameters
before "‘/’" are positional-only parameters and may only be passed by
positional arguments.

在 3.8 版的變更: The ‘/’ function parameter syntax may be used to
indicate positional-only parameters.  See PEP 570(3) for details.

Parameters may have an *note annotation: 1b3b. of the form "‘:
expression’" following the parameter name.  Any parameter may have an
annotation, even those of the form ‘*identifier’ or ‘**identifier’.
Functions may have "return" annotation of the form "‘-> expression’"
after the parameter list.  These annotations can be any valid Python
expression.  The presence of annotations does not change the semantics
of a function.  The annotation values are available as values of a
dictionary keyed by the parameters' names in the ‘__annotations__’
attribute of the function object.  If the ‘annotations’ import from
*note __future__: 0. is used, annotations are preserved as strings at
runtime which enables postponed evaluation.  Otherwise, they are
evaluated when the function definition is executed.  In this case
annotations may be evaluated in a different order than they appear in
the source code.

It is also possible to create anonymous functions (functions not bound
to a name), for immediate use in expressions.  This uses lambda
expressions, described in section *note Lambdas: 1234.  Note that the
lambda expression is merely a shorthand for a simplified function
definition; a function defined in a "*note def: 13c5." statement can be
passed around or assigned to another name just like a function defined
by a lambda expression.  The "‘def’" form is actually more powerful
since it allows the execution of multiple statements and annotations.

'Programmer's note:' Functions are first-class objects.  A "‘def’"
statement executed inside a function definition defines a local function
that can be returned or passed around.  Free variables used in the
nested function can access the local variables of the function
containing the def.  See section *note Naming and binding: 1de9. for
details.

也參考
......

PEP 3107(4) - Function Annotations

     The original specification for function annotations.

PEP 484(5) - Type Hints

     Definition of a standard meaning for annotations: type hints.

PEP 526(6) - Syntax for Variable Annotations

     Ability to type hint variable declarations, including class
     variables and instance variables.

PEP 563(7) - Postponed Evaluation of Annotations

     Support for forward references within annotations by preserving
     annotations in a string form at runtime instead of eager
     evaluation.

PEP 318(8) - Decorators for Functions and Methods

     Function and method decorators were introduced.  Class decorators
     were introduced in PEP 3129(9).

   ---------- Footnotes ----------

   (1) A string literal appearing as the first statement in the function
body is transformed into the function's *note __doc__: 1171. attribute
and therefore the function's *note docstring: 1ffd.

   (2) https://peps.python.org/pep-0614/

   (3) https://peps.python.org/pep-0570/

   (4) https://peps.python.org/pep-3107/

   (5) https://peps.python.org/pep-0484/

   (6) https://peps.python.org/pep-0526/

   (7) https://peps.python.org/pep-0563/

   (8) https://peps.python.org/pep-0318/

   (9) https://peps.python.org/pep-3129/


File: python.info,  Node: 類別定義,  Next: 協程<2>,  Prev: 函式定義,  Up: 複合陳述式

4.8.8 類別定義
--------------

A class definition defines a class object (see section *note
標準型別階層: 1dd6.):

     classdef    ::= [decorators] "class" classname [type_params] [inheritance] ":" suite
     inheritance ::= "(" [argument_list] ")"
     classname   ::= identifier

A class definition is an executable statement.  The inheritance list
usually gives a list of base classes (see *note Metaclasses: 1e4a. for
more advanced uses), so each item in the list should evaluate to a class
object which allows subclassing.  Classes without an inheritance list
inherit, by default, from the base class *note object: a2f.; hence,

     class Foo:
         pass

is equivalent to

     class Foo(object):
         pass

The class's suite is then executed in a new execution frame (see *note
Naming and binding: 1de9.), using a newly created local namespace and
the original global namespace.  (Usually, the suite contains mostly
function definitions.)  When the class's suite finishes execution, its
execution frame is discarded but its local namespace is saved.  (1)  A
class object is then created using the inheritance list for the base
classes and the saved local namespace for the attribute dictionary.  The
class name is bound to this class object in the original local
namespace.

The order in which attributes are defined in the class body is preserved
in the new class's ‘__dict__’.  Note that this is reliable only right
after the class is created and only for classes that were defined using
the definition syntax.

Class creation can be customized heavily using *note metaclasses: 1e4a.

Classes can also be decorated: just like when decorating functions,

     @f1(arg)
     @f2
     class Foo: pass

大致等價於：

     class Foo: pass
     Foo = f1(arg)(f2(Foo))

The evaluation rules for the decorator expressions are the same as for
function decorators.  The result is then bound to the class name.

在 3.9 版的變更: Classes may be decorated with any valid *note
assignment_expression: 1eb4.  Previously, the grammar was much more
restrictive; see PEP 614(2) for details.

A list of *note type parameters: 294. may be given in square brackets
immediately after the class's name.  This indicates to static type
checkers that the class is generic.  At runtime, the type parameters can
be retrieved from the class's ‘__type_params__’ attribute.  See *note
Generic classes: 3f8. for more.

在 3.12 版的變更: Type parameter lists are new in Python 3.12.

'Programmer's note:' Variables defined in the class definition are class
attributes; they are shared by instances.  Instance attributes can be
set in a method with ‘self.name = value’.  Both class and instance
attributes are accessible through the notation "‘self.name’", and an
instance attribute hides a class attribute with the same name when
accessed in this way.  Class attributes can be used as defaults for
instance attributes, but using mutable values there can lead to
unexpected results.  *note Descriptors: bf6. can be used to create
instance variables with different implementation details.

也參考
......

PEP 3115(3) - Metaclasses in Python 3000

     The proposal that changed the declaration of metaclasses to the
     current syntax, and the semantics for how classes with metaclasses
     are constructed.

PEP 3129(4) - 類別裝飾器

     The proposal that added class decorators.  Function and method
     decorators were introduced in PEP 318(5).

   ---------- Footnotes ----------

   (1) A string literal appearing as the first statement in the class
body is transformed into the namespace's ‘__doc__’ item and therefore
the class's *note docstring: 1ffd.

   (2) https://peps.python.org/pep-0614/

   (3) https://peps.python.org/pep-3115/

   (4) https://peps.python.org/pep-3129/

   (5) https://peps.python.org/pep-0318/


File: python.info,  Node: 協程<2>,  Next: Type parameter lists,  Prev: 類別定義,  Up: 複合陳述式

4.8.9 協程
----------

在 3.5 版被加入.

* Menu:

* 協程函式定義::
* async for 陳述式::
* async with 陳述式::


File: python.info,  Node: 協程函式定義,  Next: async for 陳述式,  Up: 協程<2>

4.8.9.1 協程函式定義
....................

     async_funcdef ::= [decorators] "async" "def" funcname "(" [parameter_list] ")"
                       ["->" expression] ":" suite

Execution of Python coroutines can be suspended and resumed at many
points (see *note coroutine: 438.).  *note await: 19f. expressions,
*note async for: a4e. and *note async with: 57a. can only be used in the
body of a coroutine function.

Functions defined with ‘async def’ syntax are always coroutine
functions, even if they do not contain ‘await’ or ‘async’ keywords.

It is a *note SyntaxError: 173. to use a ‘yield from’ expression inside
the body of a coroutine function.

一個協程函式範例：

     async def func(param1, param2):
         do_stuff()
         await some_coroutine()

在 3.7 版的變更: ‘await’ and ‘async’ are now keywords; previously they
were only treated as such inside the body of a coroutine function.


File: python.info,  Node: async for 陳述式,  Next: async with 陳述式,  Prev: 協程函式定義,  Up: 協程<2>

4.8.9.2 ‘async for’ 陳述式
..........................

     async_for_stmt ::= "async" for_stmt

An *note asynchronous iterable: d1e. provides an ‘__aiter__’ method that
directly returns an *note asynchronous iterator: 191, which can call
asynchronous code in its ‘__anext__’ method.

The ‘async for’ statement allows convenient iteration over asynchronous
iterables.

The following code:

     async for TARGET in ITER:
         SUITE
     else:
         SUITE2

Is semantically equivalent to:

     iter = (ITER)
     iter = type(iter).__aiter__(iter)
     running = True

     while running:
         try:
             TARGET = await type(iter).__anext__(iter)
         except StopAsyncIteration:
             running = False
         else:
             SUITE
     else:
         SUITE2

更多細節請見 *note __aiter__(): ba2. 與 *note __anext__(): 1dfa.。

It is a *note SyntaxError: 173. to use an ‘async for’ statement outside
the body of a coroutine function.


File: python.info,  Node: async with 陳述式,  Prev: async for 陳述式,  Up: 協程<2>

4.8.9.3 ‘async with’ 陳述式
...........................

     async_with_stmt ::= "async" with_stmt

An *note asynchronous context manager: 579. is a *note context manager:
576. that is able to suspend execution in its 'enter' and 'exit'
methods.

The following code:

     async with EXPRESSION as TARGET:
         SUITE

is semantically equivalent to:

     manager = (EXPRESSION)
     aenter = type(manager).__aenter__
     aexit = type(manager).__aexit__
     value = await aenter(manager)
     hit_except = False

     try:
         TARGET = value
         SUITE
     except:
         hit_except = True
         if not await aexit(manager, *sys.exc_info()):
             raise
     finally:
         if not hit_except:
             await aexit(manager, None, None, None)

更多細節請見 *note __aenter__(): 1ea6. 與 *note __aexit__(): 151e.。

It is a *note SyntaxError: 173. to use an ‘async with’ statement outside
the body of a coroutine function.

也參考
......

PEP 492(1) - Coroutines with async and await syntax

     The proposal that made coroutines a proper standalone concept in
     Python, and added supporting syntax.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0492/


File: python.info,  Node: Type parameter lists,  Prev: 協程<2>,  Up: 複合陳述式

4.8.10 Type parameter lists
---------------------------

在 3.12 版被加入.

在 3.13 版的變更: Support for default values was added (see PEP 696(1)).

     type_params  ::= "[" type_param ("," type_param)* "]"
     type_param   ::= typevar | typevartuple | paramspec
     typevar      ::= identifier (":" expression)? ("=" expression)?
     typevartuple ::= "*" identifier ("=" expression)?
     paramspec    ::= "**" identifier ("=" expression)?

*note Functions: 13c5. (including *note coroutines: 575.), *note
classes: 126a. and *note type aliases: 3de. may contain a type parameter
list:

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

     async def amax[T](args: list[T]) -> T:
         ...

     class Bag[T]:
         def __iter__(self) -> Iterator[T]:
             ...

         def add(self, arg: T) -> None:
             ...

     type ListOrSet[T] = list[T] | set[T]

Semantically, this indicates that the function, class, or type alias is
generic over a type variable.  This information is primarily used by
static type checkers, and at runtime, generic objects behave much like
their non-generic counterparts.

Type parameters are declared in square brackets (‘[]’) immediately after
the name of the function, class, or type alias.  The type parameters are
accessible within the scope of the generic object, but not elsewhere.
Thus, after a declaration ‘def func[T](): pass’, the name ‘T’ is not
available in the module scope.  Below, the semantics of generic objects
are described with more precision.  The scope of type parameters is
modeled with a special function (technically, an *note annotation scope:
16e.) that wraps the creation of the generic object.

Generic functions, classes, and type aliases have a ‘__type_params__’
attribute listing their type parameters.

Type parameters come in three kinds:

   * *note typing.TypeVar: 141, introduced by a plain name (e.g., ‘T’).
     Semantically, this represents a single type to a type checker.

   * *note typing.TypeVarTuple: 143, introduced by a name prefixed with
     a single asterisk (e.g., ‘*Ts’).  Semantically, this stands for a
     tuple of any number of types.

   * *note typing.ParamSpec: 142, introduced by a name prefixed with two
     asterisks (e.g., ‘**P’).  Semantically, this stands for the
     parameters of a callable.

*note typing.TypeVar: 141. declarations can define 'bounds' and
'constraints' with a colon (‘:’) followed by an expression.  A single
expression after the colon indicates a bound (e.g.  ‘T: int’).
Semantically, this means that the ‘typing.TypeVar’ can only represent
types that are a subtype of this bound.  A parenthesized tuple of
expressions after the colon indicates a set of constraints (e.g.  ‘T:
(str, bytes)’).  Each member of the tuple should be a type (again, this
is not enforced at runtime).  Constrained type variables can only take
on one of the types in the list of constraints.

For ‘typing.TypeVar’s declared using the type parameter list syntax, the
bound and constraints are not evaluated when the generic object is
created, but only when the value is explicitly accessed through the
attributes ‘__bound__’ and ‘__constraints__’.  To accomplish this, the
bounds or constraints are evaluated in a separate *note annotation
scope: 16e.

*note typing.TypeVarTuple: 143.s and *note typing.ParamSpec: 142.s
cannot have bounds or constraints.

All three flavors of type parameters can also have a 'default value',
which is used when the type parameter is not explicitly provided.  This
is added by appending a single equals sign (‘=’) followed by an
expression.  Like the bounds and constraints of type variables, the
default value is not evaluated when the object is created, but only when
the type parameter's ‘__default__’ attribute is accessed.  To this end,
the default value is evaluated in a separate *note annotation scope:
16e.  If no default value is specified for a type parameter, the
‘__default__’ attribute is set to the special sentinel object *note
typing.NoDefault: 247.

The following example indicates the full set of allowed type parameter
declarations:

     def overly_generic[
        SimpleTypeVar,
        TypeVarWithDefault = int,
        TypeVarWithBound: int,
        TypeVarWithConstraints: (str, bytes),
        *SimpleTypeVarTuple = (int, float),
        **SimpleParamSpec = (str, bytearray),
     ](
        a: SimpleTypeVar,
        b: TypeVarWithDefault,
        c: TypeVarWithBound,
        d: Callable[SimpleParamSpec, TypeVarWithConstraints],
        *e: SimpleTypeVarTuple,
     ): ...

* Menu:

* Generic functions::
* Generic classes::
* Generic type aliases::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0696/


File: python.info,  Node: Generic functions,  Next: Generic classes,  Up: Type parameter lists

4.8.10.1 Generic functions
..........................

Generic functions are declared as follows:

     def func[T](arg: T): ...

語法大致等價於：

     annotation-def TYPE_PARAMS_OF_func():
         T = typing.TypeVar("T")
         def func(arg: T): ...
         func.__type_params__ = (T,)
         return func
     func = TYPE_PARAMS_OF_func()

Here ‘annotation-def’ indicates an *note annotation scope: 16e, which is
not actually bound to any name at runtime.  (One other liberty is taken
in the translation: the syntax does not go through attribute access on
the *note typing: ed. module, but creates an instance of *note
typing.TypeVar: 141. directly.)

The annotations of generic functions are evaluated within the annotation
scope used for declaring the type parameters, but the function's
defaults and decorators are not.

The following example illustrates the scoping rules for these cases, as
well as for additional flavors of type parameters:

     @decorator
     def func[T: int, *Ts, **P](*args: *Ts, arg: Callable[P, T] = some_default):
         ...

Except for the *note lazy evaluation: 3fd. of the *note TypeVar: 141.
bound, this is equivalent to:

     DEFAULT_OF_arg = some_default

     annotation-def TYPE_PARAMS_OF_func():

         annotation-def BOUND_OF_T():
             return int
         # In reality, BOUND_OF_T() is evaluated only on demand.
         T = typing.TypeVar("T", bound=BOUND_OF_T())

         Ts = typing.TypeVarTuple("Ts")
         P = typing.ParamSpec("P")

         def func(*args: *Ts, arg: Callable[P, T] = DEFAULT_OF_arg):
             ...

         func.__type_params__ = (T, Ts, P)
         return func
     func = decorator(TYPE_PARAMS_OF_func())

The capitalized names like ‘DEFAULT_OF_arg’ are not actually bound at
runtime.


File: python.info,  Node: Generic classes,  Next: Generic type aliases,  Prev: Generic functions,  Up: Type parameter lists

4.8.10.2 Generic classes
........................

Generic classes are declared as follows:

     class Bag[T]: ...

語法大致等價於：

     annotation-def TYPE_PARAMS_OF_Bag():
         T = typing.TypeVar("T")
         class Bag(typing.Generic[T]):
             __type_params__ = (T,)
             ...
         return Bag
     Bag = TYPE_PARAMS_OF_Bag()

Here again ‘annotation-def’ (not a real keyword) indicates an *note
annotation scope: 16e, and the name ‘TYPE_PARAMS_OF_Bag’ is not actually
bound at runtime.

Generic classes implicitly inherit from *note typing.Generic: 150c.  The
base classes and keyword arguments of generic classes are evaluated
within the type scope for the type parameters, and decorators are
evaluated outside that scope.  This is illustrated by this example:

     @decorator
     class Bag(Base[T], arg=T): ...

這等價於：

     annotation-def TYPE_PARAMS_OF_Bag():
         T = typing.TypeVar("T")
         class Bag(Base[T], typing.Generic[T], arg=T):
             __type_params__ = (T,)
             ...
         return Bag
     Bag = decorator(TYPE_PARAMS_OF_Bag())


File: python.info,  Node: Generic type aliases,  Prev: Generic classes,  Up: Type parameter lists

4.8.10.3 Generic type aliases
.............................

The *note type: 3de. statement can also be used to create a generic type
alias:

     type ListOrSet[T] = list[T] | set[T]

Except for the *note lazy evaluation: 3fd. of the value, this is
equivalent to:

     annotation-def TYPE_PARAMS_OF_ListOrSet():
         T = typing.TypeVar("T")

         annotation-def VALUE_OF_ListOrSet():
             return list[T] | set[T]
         # In reality, the value is lazily evaluated
         return typing.TypeAliasType("ListOrSet", VALUE_OF_ListOrSet(), type_params=(T,))
     ListOrSet = TYPE_PARAMS_OF_ListOrSet()

Here, ‘annotation-def’ (not a real keyword) indicates an *note
annotation scope: 16e.  The capitalized names like
‘TYPE_PARAMS_OF_ListOrSet’ are not actually bound at runtime.

註解
....


File: python.info,  Node: 最高層級元件,  Next: 完整的語法規格書,  Prev: 複合陳述式,  Up: Python 語言參考手冊

4.9 最高層級元件
================

Python 直譯器可以從多種來源獲得輸入：作為標準輸入或程式引數自腳本傳入、
以互動式鍵入、自模組原始檔引入等等。這一章將給出在這些情況下所用的語法。

* Menu:

* 完整的 Python 程式::
* 檔案輸入::
* 互動式輸入::
* 運算式輸入::


File: python.info,  Node: 完整的 Python 程式,  Next: 檔案輸入,  Up: 最高層級元件

4.9.1 完整的 Python 程式
------------------------

雖然語言規範描述不必規定語言直譯器是如何被調用（invoke）的，但對完整的
Python 程式加以說明還是很有用的。一個完整的 Python 程式會在最小初始化環
境中被執行：所有內建和標準模組均為可用，但均處於未初始化狀態，只有 *note
sys: c3.（各種系統服務）、*note builtins: e.（內建函式、例外和 ‘None’）
和 *note __main__: 1. 除外。後者用於為完整程式的執行提供區域性和全域性命
名空間 (namespace)。

用於一個完整 Python 程式的語法，即下節所描述的檔案輸入。

直譯器也可以透過互動模式被調用；在此情況下，它並不讀取和執行一個完整程式
，而是每讀取一條陳述式就執行一次（可能為複合陳述式）。此時的初始環境與一
個完整程式的相同；每條陳述式會在 *note __main__: 1. 的命名空間中被執行。

一個完整程式可透過三種形式被傳遞給直譯器：使用 *note -c: 584. '字串'命令
列選項、使用一個檔案作為第一個命令列引數、或者使用標準輸入。如果檔案或標
準輸入是一個 tty 裝置，直譯器會進入互動模式；否則它會將檔案當作一個完整
程式來執行。


File: python.info,  Node: 檔案輸入,  Next: 互動式輸入,  Prev: 完整的 Python 程式,  Up: 最高層級元件

4.9.2 檔案輸入
--------------

所有從非互動式檔案讀取的輸入都具有相同的形式：

     file_input ::= (NEWLINE | statement)*

此語法用於下列幾種情況：

   * 剖析一個完整 Python 程式時（從檔案或字串）；

   * 剖析一個模組時；

   * 剖析一個傳遞给 *note exec(): 162. 函数的字串時；


File: python.info,  Node: 互動式輸入,  Next: 運算式輸入,  Prev: 檔案輸入,  Up: 最高層級元件

4.9.3 互動式輸入
----------------

互動模式下的輸入使用以下語法進行剖析：

     interactive_input ::= [stmt_list] NEWLINE | compound_stmt NEWLINE

注意在互動模式下，一條（最高層級）複合陳述式最後必須帶有一個空行；這能夠
幫助剖析器確定輸入已經結束。


File: python.info,  Node: 運算式輸入,  Prev: 互動式輸入,  Up: 最高層級元件

4.9.4 運算式輸入
----------------

*note eval(): 163. 被用於運算式輸入，它會忽略開頭的空白。傳遞給 *note
eval(): 163. 的字串引數必須具有以下形式：

     eval_input ::= expression_list NEWLINE*


File: python.info,  Node: 完整的語法規格書,  Prev: 最高層級元件,  Up: Python 語言參考手冊

4.10 完整的語法規格書
=====================

This is the full Python grammar, derived directly from the grammar used
to generate the CPython parser (see Grammar/python.gram(1)).  The
version here omits details related to code generation and error
recovery.

The notation is a mixture of EBNF(2) and PEG(3). In particular, ‘&’
followed by a symbol, token or parenthesized group indicates a positive
lookahead (i.e., is required to match but not consumed), while ‘!’
indicates a negative lookahead (i.e., is required 'not' to match).  We
use the ‘|’ separator to mean PEG's "ordered choice" (written as ‘/’ in
traditional PEG grammars).  See PEP 617(4) for more details on the
grammar's syntax.

     # PEG grammar for Python

     @trailer '''
     void *
     _PyPegen_parse(Parser *p)
     {
         // Initialize keywords
         p->keywords = reserved_keywords;
         p->n_keyword_lists = n_keyword_lists;
         p->soft_keywords = soft_keywords;

         // Run parser
         void *result = NULL;
         if (p->start_rule == Py_file_input) {
             result = file_rule(p);
         } else if (p->start_rule == Py_single_input) {
             result = interactive_rule(p);
         } else if (p->start_rule == Py_eval_input) {
             result = eval_rule(p);
         } else if (p->start_rule == Py_func_type_input) {
             result = func_type_rule(p);
         }

         return result;
     }
     '''

     # ========================= START OF THE GRAMMAR =========================

     # General grammatical elements and rules:
     #
     # * Strings with double quotes (") denote SOFT KEYWORDS
     # * Strings with single quotes (') denote KEYWORDS
     # * Upper case names (NAME) denote tokens in the Grammar/Tokens file
     # * Rule names starting with "invalid_" are used for specialized syntax errors
     #     - These rules are NOT used in the first pass of the parser.
     #     - Only if the first pass fails to parse, a second pass including the invalid
     #       rules will be executed.
     #     - If the parser fails in the second phase with a generic syntax error, the
     #       location of the generic failure of the first pass will be used (this avoids
     #       reporting incorrect locations due to the invalid rules).
     #     - The order of the alternatives involving invalid rules matter
     #       (like any rule in PEG).
     #
     # Grammar Syntax (see PEP 617 for more information):
     #
     # rule_name: expression
     #   Optionally, a type can be included right after the rule name, which
     #   specifies the return type of the C or Python function corresponding to the
     #   rule:
     # rule_name[return_type]: expression
     #   If the return type is omitted, then a void * is returned in C and an Any in
     #   Python.
     # e1 e2
     #   Match e1, then match e2.
     # e1 | e2
     #   Match e1 or e2.
     #   The first alternative can also appear on the line after the rule name for
     #   formatting purposes. In that case, a | must be used before the first
     #   alternative, like so:
     #       rule_name[return_type]:
     #            | first_alt
     #            | second_alt
     # ( e )
     #   Match e (allows also to use other operators in the group like '(e)*')
     # [ e ] or e?
     #   Optionally match e.
     # e*
     #   Match zero or more occurrences of e.
     # e+
     #   Match one or more occurrences of e.
     # s.e+
     #   Match one or more occurrences of e, separated by s. The generated parse tree
     #   does not include the separator. This is otherwise identical to (e (s e)*).
     # &e
     #   Succeed if e can be parsed, without consuming any input.
     # !e
     #   Fail if e can be parsed, without consuming any input.
     # ~
     #   Commit to the current alternative, even if it fails to parse.
     # &&e
     #   Eager parse e. The parser will not backtrack and will immediately
     #   fail with SyntaxError if e cannot be parsed.
     #

     # STARTING RULES
     # ==============

     file[mod_ty]: a=[statements] ENDMARKER { _PyPegen_make_module(p, a) }
     interactive[mod_ty]: a=statement_newline { _PyAST_Interactive(a, p->arena) }
     eval[mod_ty]: a=expressions NEWLINE* ENDMARKER { _PyAST_Expression(a, p->arena) }
     func_type[mod_ty]: '(' a=[type_expressions] ')' '->' b=expression NEWLINE* ENDMARKER { _PyAST_FunctionType(a, b, p->arena) }

     # GENERAL STATEMENTS
     # ==================

     statements[asdl_stmt_seq*]: a=statement+ { (asdl_stmt_seq*)_PyPegen_seq_flatten(p, a) }

     statement[asdl_stmt_seq*]: a=compound_stmt { (asdl_stmt_seq*)_PyPegen_singleton_seq(p, a) } | a[asdl_stmt_seq*]=simple_stmts { a }

     statement_newline[asdl_stmt_seq*]:
         | a=compound_stmt NEWLINE { (asdl_stmt_seq*)_PyPegen_singleton_seq(p, a) }
         | simple_stmts
         | NEWLINE { (asdl_stmt_seq*)_PyPegen_singleton_seq(p, CHECK(stmt_ty, _PyAST_Pass(EXTRA))) }
         | ENDMARKER { _PyPegen_interactive_exit(p) }

     simple_stmts[asdl_stmt_seq*]:
         | a=simple_stmt !';' NEWLINE { (asdl_stmt_seq*)_PyPegen_singleton_seq(p, a) } # Not needed, there for speedup
         | a[asdl_stmt_seq*]=';'.simple_stmt+ [';'] NEWLINE { a }

     # NOTE: assignment MUST precede expression, else parsing a simple assignment
     # will throw a SyntaxError.
     simple_stmt[stmt_ty] (memo):
         | assignment
         | &"type" type_alias
         | e=star_expressions { _PyAST_Expr(e, EXTRA) }
         | &'return' return_stmt
         | &('import' | 'from') import_stmt
         | &'raise' raise_stmt
         | 'pass' { _PyAST_Pass(EXTRA) }
         | &'del' del_stmt
         | &'yield' yield_stmt
         | &'assert' assert_stmt
         | 'break' { _PyAST_Break(EXTRA) }
         | 'continue' { _PyAST_Continue(EXTRA) }
         | &'global' global_stmt
         | &'nonlocal' nonlocal_stmt

     compound_stmt[stmt_ty]:
         | &('def' | '@' | 'async') function_def
         | &'if' if_stmt
         | &('class' | '@') class_def
         | &('with' | 'async') with_stmt
         | &('for' | 'async') for_stmt
         | &'try' try_stmt
         | &'while' while_stmt
         | match_stmt

     # SIMPLE STATEMENTS
     # =================

     # NOTE: annotated_rhs may start with 'yield'; yield_expr must start with 'yield'
     assignment[stmt_ty]:
         | a=NAME ':' b=expression c=['=' d=annotated_rhs { d }] {
             CHECK_VERSION(
                 stmt_ty,
                 6,
                 "Variable annotation syntax is",
                 _PyAST_AnnAssign(CHECK(expr_ty, _PyPegen_set_expr_context(p, a, Store)), b, c, 1, EXTRA)
             ) }
         | a=('(' b=single_target ')' { b }
              | single_subscript_attribute_target) ':' b=expression c=['=' d=annotated_rhs { d }] {
             CHECK_VERSION(stmt_ty, 6, "Variable annotations syntax is", _PyAST_AnnAssign(a, b, c, 0, EXTRA)) }
         | a[asdl_expr_seq*]=(z=star_targets '=' { z })+ b=(yield_expr | star_expressions) !'=' tc=[TYPE_COMMENT] {
              _PyAST_Assign(a, b, NEW_TYPE_COMMENT(p, tc), EXTRA) }
         | a=single_target b=augassign ~ c=(yield_expr | star_expressions) {
              _PyAST_AugAssign(a, b->kind, c, EXTRA) }
         | invalid_assignment

     annotated_rhs[expr_ty]: yield_expr | star_expressions

     augassign[AugOperator*]:
         | '+=' { _PyPegen_augoperator(p, Add) }
         | '-=' { _PyPegen_augoperator(p, Sub) }
         | '*=' { _PyPegen_augoperator(p, Mult) }
         | '@=' { CHECK_VERSION(AugOperator*, 5, "The '@' operator is", _PyPegen_augoperator(p, MatMult)) }
         | '/=' { _PyPegen_augoperator(p, Div) }
         | '%=' { _PyPegen_augoperator(p, Mod) }
         | '&=' { _PyPegen_augoperator(p, BitAnd) }
         | '|=' { _PyPegen_augoperator(p, BitOr) }
         | '^=' { _PyPegen_augoperator(p, BitXor) }
         | '<<=' { _PyPegen_augoperator(p, LShift) }
         | '>>=' { _PyPegen_augoperator(p, RShift) }
         | '**=' { _PyPegen_augoperator(p, Pow) }
         | '//=' { _PyPegen_augoperator(p, FloorDiv) }

     return_stmt[stmt_ty]:
         | 'return' a=[star_expressions] { _PyAST_Return(a, EXTRA) }

     raise_stmt[stmt_ty]:
         | 'raise' a=expression b=['from' z=expression { z }] { _PyAST_Raise(a, b, EXTRA) }
         | 'raise' { _PyAST_Raise(NULL, NULL, EXTRA) }

     global_stmt[stmt_ty]: 'global' a[asdl_expr_seq*]=','.NAME+ {
         _PyAST_Global(CHECK(asdl_identifier_seq*, _PyPegen_map_names_to_ids(p, a)), EXTRA) }

     nonlocal_stmt[stmt_ty]: 'nonlocal' a[asdl_expr_seq*]=','.NAME+ {
         _PyAST_Nonlocal(CHECK(asdl_identifier_seq*, _PyPegen_map_names_to_ids(p, a)), EXTRA) }

     del_stmt[stmt_ty]:
         | 'del' a=del_targets &(';' | NEWLINE) { _PyAST_Delete(a, EXTRA) }
         | invalid_del_stmt

     yield_stmt[stmt_ty]: y=yield_expr { _PyAST_Expr(y, EXTRA) }

     assert_stmt[stmt_ty]: 'assert' a=expression b=[',' z=expression { z }] { _PyAST_Assert(a, b, EXTRA) }

     import_stmt[stmt_ty]:
         | invalid_import
         | import_name
         | import_from

     # Import statements
     # -----------------

     import_name[stmt_ty]: 'import' a=dotted_as_names { _PyAST_Import(a, EXTRA) }
     # note below: the ('.' | '...') is necessary because '...' is tokenized as ELLIPSIS
     import_from[stmt_ty]:
         | 'from' a=('.' | '...')* b=dotted_name 'import' c=import_from_targets {
             _PyAST_ImportFrom(b->v.Name.id, c, _PyPegen_seq_count_dots(a), EXTRA) }
         | 'from' a=('.' | '...')+ 'import' b=import_from_targets {
             _PyAST_ImportFrom(NULL, b, _PyPegen_seq_count_dots(a), EXTRA) }
     import_from_targets[asdl_alias_seq*]:
         | '(' a=import_from_as_names [','] ')' { a }
         | import_from_as_names !','
         | '*' { (asdl_alias_seq*)_PyPegen_singleton_seq(p, CHECK(alias_ty, _PyPegen_alias_for_star(p, EXTRA))) }
         | invalid_import_from_targets
     import_from_as_names[asdl_alias_seq*]:
         | a[asdl_alias_seq*]=','.import_from_as_name+ { a }
     import_from_as_name[alias_ty]:
         | a=NAME b=['as' z=NAME { z }] { _PyAST_alias(a->v.Name.id,
                                                    (b) ? ((expr_ty) b)->v.Name.id : NULL,
                                                    EXTRA) }
     dotted_as_names[asdl_alias_seq*]:
         | a[asdl_alias_seq*]=','.dotted_as_name+ { a }
     dotted_as_name[alias_ty]:
         | a=dotted_name b=['as' z=NAME { z }] { _PyAST_alias(a->v.Name.id,
                                                           (b) ? ((expr_ty) b)->v.Name.id : NULL,
                                                           EXTRA) }
     dotted_name[expr_ty]:
         | a=dotted_name '.' b=NAME { _PyPegen_join_names_with_dot(p, a, b) }
         | NAME

     # COMPOUND STATEMENTS
     # ===================

     # Common elements
     # ---------------

     block[asdl_stmt_seq*] (memo):
         | NEWLINE INDENT a=statements DEDENT { a }
         | simple_stmts
         | invalid_block

     decorators[asdl_expr_seq*]: a[asdl_expr_seq*]=('@' f=named_expression NEWLINE { f })+ { a }

     # Class definitions
     # -----------------

     class_def[stmt_ty]:
         | a=decorators b=class_def_raw { _PyPegen_class_def_decorators(p, a, b) }
         | class_def_raw

     class_def_raw[stmt_ty]:
         | invalid_class_def_raw
         | 'class' a=NAME t=[type_params] b=['(' z=[arguments] ')' { z }] ':' c=block {
             _PyAST_ClassDef(a->v.Name.id,
                          (b) ? ((expr_ty) b)->v.Call.args : NULL,
                          (b) ? ((expr_ty) b)->v.Call.keywords : NULL,
                          c, NULL, t, EXTRA) }

     # Function definitions
     # --------------------

     function_def[stmt_ty]:
         | d=decorators f=function_def_raw { _PyPegen_function_def_decorators(p, d, f) }
         | function_def_raw

     function_def_raw[stmt_ty]:
         | invalid_def_raw
         | 'def' n=NAME t=[type_params] '(' params=[params] ')' a=['->' z=expression { z }] ':' tc=[func_type_comment] b=block {
             _PyAST_FunctionDef(n->v.Name.id,
                             (params) ? params : CHECK(arguments_ty, _PyPegen_empty_arguments(p)),
                             b, NULL, a, NEW_TYPE_COMMENT(p, tc), t, EXTRA) }
         | 'async' 'def' n=NAME t=[type_params] '(' params=[params] ')' a=['->' z=expression { z }] ':' tc=[func_type_comment] b=block {
             CHECK_VERSION(
                 stmt_ty,
                 5,
                 "Async functions are",
                 _PyAST_AsyncFunctionDef(n->v.Name.id,
                                 (params) ? params : CHECK(arguments_ty, _PyPegen_empty_arguments(p)),
                                 b, NULL, a, NEW_TYPE_COMMENT(p, tc), t, EXTRA)
             ) }

     # Function parameters
     # -------------------

     params[arguments_ty]:
         | invalid_parameters
         | parameters

     parameters[arguments_ty]:
         | a=slash_no_default b[asdl_arg_seq*]=param_no_default* c=param_with_default* d=[star_etc] {
             CHECK_VERSION(arguments_ty, 8, "Positional-only parameters are", _PyPegen_make_arguments(p, a, NULL, b, c, d)) }
         | a=slash_with_default b=param_with_default* c=[star_etc] {
             CHECK_VERSION(arguments_ty, 8, "Positional-only parameters are", _PyPegen_make_arguments(p, NULL, a, NULL, b, c)) }
         | a[asdl_arg_seq*]=param_no_default+ b=param_with_default* c=[star_etc] {
             _PyPegen_make_arguments(p, NULL, NULL, a, b, c) }
         | a=param_with_default+ b=[star_etc] { _PyPegen_make_arguments(p, NULL, NULL, NULL, a, b)}
         | a=star_etc { _PyPegen_make_arguments(p, NULL, NULL, NULL, NULL, a) }

     # Some duplication here because we can't write (',' | &')'),
     # which is because we don't support empty alternatives (yet).

     slash_no_default[asdl_arg_seq*]:
         | a[asdl_arg_seq*]=param_no_default+ '/' ',' { a }
         | a[asdl_arg_seq*]=param_no_default+ '/' &')' { a }
     slash_with_default[SlashWithDefault*]:
         | a=param_no_default* b=param_with_default+ '/' ',' { _PyPegen_slash_with_default(p, (asdl_arg_seq *)a, b) }
         | a=param_no_default* b=param_with_default+ '/' &')' { _PyPegen_slash_with_default(p, (asdl_arg_seq *)a, b) }

     star_etc[StarEtc*]:
         | invalid_star_etc
         | '*' a=param_no_default b=param_maybe_default* c=[kwds] {
             _PyPegen_star_etc(p, a, b, c) }
         | '*' a=param_no_default_star_annotation b=param_maybe_default* c=[kwds] {
             _PyPegen_star_etc(p, a, b, c) }
         | '*' ',' b=param_maybe_default+ c=[kwds] {
             _PyPegen_star_etc(p, NULL, b, c) }
         | a=kwds { _PyPegen_star_etc(p, NULL, NULL, a) }

     kwds[arg_ty]:
         | invalid_kwds
         | '**' a=param_no_default { a }

     # One parameter.  This *includes* a following comma and type comment.
     #
     # There are three styles:
     # - No default
     # - With default
     # - Maybe with default
     #
     # There are two alternative forms of each, to deal with type comments:
     # - Ends in a comma followed by an optional type comment
     # - No comma, optional type comment, must be followed by close paren
     # The latter form is for a final parameter without trailing comma.
     #

     param_no_default[arg_ty]:
         | a=param ',' tc=TYPE_COMMENT? { _PyPegen_add_type_comment_to_arg(p, a, tc) }
         | a=param tc=TYPE_COMMENT? &')' { _PyPegen_add_type_comment_to_arg(p, a, tc) }
     param_no_default_star_annotation[arg_ty]:
         | a=param_star_annotation ',' tc=TYPE_COMMENT? { _PyPegen_add_type_comment_to_arg(p, a, tc) }
         | a=param_star_annotation tc=TYPE_COMMENT? &')' { _PyPegen_add_type_comment_to_arg(p, a, tc) }
     param_with_default[NameDefaultPair*]:
         | a=param c=default ',' tc=TYPE_COMMENT? { _PyPegen_name_default_pair(p, a, c, tc) }
         | a=param c=default tc=TYPE_COMMENT? &')' { _PyPegen_name_default_pair(p, a, c, tc) }
     param_maybe_default[NameDefaultPair*]:
         | a=param c=default? ',' tc=TYPE_COMMENT? { _PyPegen_name_default_pair(p, a, c, tc) }
         | a=param c=default? tc=TYPE_COMMENT? &')' { _PyPegen_name_default_pair(p, a, c, tc) }
     param[arg_ty]: a=NAME b=annotation? { _PyAST_arg(a->v.Name.id, b, NULL, EXTRA) }
     param_star_annotation[arg_ty]: a=NAME b=star_annotation { _PyAST_arg(a->v.Name.id, b, NULL, EXTRA) }
     annotation[expr_ty]: ':' a=expression { a }
     star_annotation[expr_ty]: ':' a=star_expression { a }
     default[expr_ty]: '=' a=expression { a } | invalid_default

     # If statement
     # ------------

     if_stmt[stmt_ty]:
         | invalid_if_stmt
         | 'if' a=named_expression ':' b=block c=elif_stmt {
             _PyAST_If(a, b, CHECK(asdl_stmt_seq*, _PyPegen_singleton_seq(p, c)), EXTRA) }
         | 'if' a=named_expression ':' b=block c=[else_block] { _PyAST_If(a, b, c, EXTRA) }
     elif_stmt[stmt_ty]:
         | invalid_elif_stmt
         | 'elif' a=named_expression ':' b=block c=elif_stmt {
             _PyAST_If(a, b, CHECK(asdl_stmt_seq*, _PyPegen_singleton_seq(p, c)), EXTRA) }
         | 'elif' a=named_expression ':' b=block c=[else_block] { _PyAST_If(a, b, c, EXTRA) }
     else_block[asdl_stmt_seq*]:
         | invalid_else_stmt
         | 'else' &&':' b=block { b }

     # While statement
     # ---------------

     while_stmt[stmt_ty]:
         | invalid_while_stmt
         | 'while' a=named_expression ':' b=block c=[else_block] { _PyAST_While(a, b, c, EXTRA) }

     # For statement
     # -------------

     for_stmt[stmt_ty]:
         | invalid_for_stmt
         | 'for' t=star_targets 'in' ~ ex=star_expressions ':' tc=[TYPE_COMMENT] b=block el=[else_block] {
             _PyAST_For(t, ex, b, el, NEW_TYPE_COMMENT(p, tc), EXTRA) }
         | 'async' 'for' t=star_targets 'in' ~ ex=star_expressions ':' tc=[TYPE_COMMENT] b=block el=[else_block] {
             CHECK_VERSION(stmt_ty, 5, "Async for loops are", _PyAST_AsyncFor(t, ex, b, el, NEW_TYPE_COMMENT(p, tc), EXTRA)) }
         | invalid_for_target

     # With statement
     # --------------

     with_stmt[stmt_ty]:
         | invalid_with_stmt_indent
         | 'with' '(' a[asdl_withitem_seq*]=','.with_item+ ','? ')' ':' tc=[TYPE_COMMENT] b=block {
            _PyAST_With(a, b, NEW_TYPE_COMMENT(p, tc), EXTRA) }
         | 'with' a[asdl_withitem_seq*]=','.with_item+ ':' tc=[TYPE_COMMENT] b=block {
             _PyAST_With(a, b, NEW_TYPE_COMMENT(p, tc), EXTRA) }
         | 'async' 'with' '(' a[asdl_withitem_seq*]=','.with_item+ ','? ')' ':' b=block {
            CHECK_VERSION(stmt_ty, 5, "Async with statements are", _PyAST_AsyncWith(a, b, NULL, EXTRA)) }
         | 'async' 'with' a[asdl_withitem_seq*]=','.with_item+ ':' tc=[TYPE_COMMENT] b=block {
            CHECK_VERSION(stmt_ty, 5, "Async with statements are", _PyAST_AsyncWith(a, b, NEW_TYPE_COMMENT(p, tc), EXTRA)) }
         | invalid_with_stmt

     with_item[withitem_ty]:
         | e=expression 'as' t=star_target &(',' | ')' | ':') { _PyAST_withitem(e, t, p->arena) }
         | invalid_with_item
         | e=expression { _PyAST_withitem(e, NULL, p->arena) }

     # Try statement
     # -------------

     try_stmt[stmt_ty]:
         | invalid_try_stmt
         | 'try' &&':' b=block f=finally_block { _PyAST_Try(b, NULL, NULL, f, EXTRA) }
         | 'try' &&':' b=block ex[asdl_excepthandler_seq*]=except_block+ el=[else_block] f=[finally_block] { _PyAST_Try(b, ex, el, f, EXTRA) }
         | 'try' &&':' b=block ex[asdl_excepthandler_seq*]=except_star_block+ el=[else_block] f=[finally_block] {
             CHECK_VERSION(stmt_ty, 11, "Exception groups are",
                           _PyAST_TryStar(b, ex, el, f, EXTRA)) }


     # Except statement
     # ----------------

     except_block[excepthandler_ty]:
         | invalid_except_stmt_indent
         | 'except' e=expression t=['as' z=NAME { z }] ':' b=block {
             _PyAST_ExceptHandler(e, (t) ? ((expr_ty) t)->v.Name.id : NULL, b, EXTRA) }
         | 'except' ':' b=block { _PyAST_ExceptHandler(NULL, NULL, b, EXTRA) }
         | invalid_except_stmt
     except_star_block[excepthandler_ty]:
         | invalid_except_star_stmt_indent
         | 'except' '*' e=expression t=['as' z=NAME { z }] ':' b=block {
             _PyAST_ExceptHandler(e, (t) ? ((expr_ty) t)->v.Name.id : NULL, b, EXTRA) }
         | invalid_except_stmt
     finally_block[asdl_stmt_seq*]:
         | invalid_finally_stmt
         | 'finally' &&':' a=block { a }

     # Match statement
     # ---------------

     match_stmt[stmt_ty]:
         | "match" subject=subject_expr ':' NEWLINE INDENT cases[asdl_match_case_seq*]=case_block+ DEDENT {
             CHECK_VERSION(stmt_ty, 10, "Pattern matching is", _PyAST_Match(subject, cases, EXTRA)) }
         | invalid_match_stmt

     subject_expr[expr_ty]:
         | value=star_named_expression ',' values=star_named_expressions? {
             _PyAST_Tuple(CHECK(asdl_expr_seq*, _PyPegen_seq_insert_in_front(p, value, values)), Load, EXTRA) }
         | named_expression

     case_block[match_case_ty]:
         | invalid_case_block
         | "case" pattern=patterns guard=guard? ':' body=block {
             _PyAST_match_case(pattern, guard, body, p->arena) }

     guard[expr_ty]: 'if' guard=named_expression { guard }

     patterns[pattern_ty]:
         | patterns[asdl_pattern_seq*]=open_sequence_pattern {
             _PyAST_MatchSequence(patterns, EXTRA) }
         | pattern

     pattern[pattern_ty]:
         | as_pattern
         | or_pattern

     as_pattern[pattern_ty]:
         | pattern=or_pattern 'as' target=pattern_capture_target {
             _PyAST_MatchAs(pattern, target->v.Name.id, EXTRA) }
         | invalid_as_pattern

     or_pattern[pattern_ty]:
         | patterns[asdl_pattern_seq*]='|'.closed_pattern+ {
             asdl_seq_LEN(patterns) == 1 ? asdl_seq_GET(patterns, 0) : _PyAST_MatchOr(patterns, EXTRA) }

     closed_pattern[pattern_ty] (memo):
         | literal_pattern
         | capture_pattern
         | wildcard_pattern
         | value_pattern
         | group_pattern
         | sequence_pattern
         | mapping_pattern
         | class_pattern

     # Literal patterns are used for equality and identity constraints
     literal_pattern[pattern_ty]:
         | value=signed_number !('+' | '-') { _PyAST_MatchValue(value, EXTRA) }
         | value=complex_number { _PyAST_MatchValue(value, EXTRA) }
         | value=strings { _PyAST_MatchValue(value, EXTRA) }
         | 'None' { _PyAST_MatchSingleton(Py_None, EXTRA) }
         | 'True' { _PyAST_MatchSingleton(Py_True, EXTRA) }
         | 'False' { _PyAST_MatchSingleton(Py_False, EXTRA) }

     # Literal expressions are used to restrict permitted mapping pattern keys
     literal_expr[expr_ty]:
         | signed_number !('+' | '-')
         | complex_number
         | strings
         | 'None' { _PyAST_Constant(Py_None, NULL, EXTRA) }
         | 'True' { _PyAST_Constant(Py_True, NULL, EXTRA) }
         | 'False' { _PyAST_Constant(Py_False, NULL, EXTRA) }

     complex_number[expr_ty]:
         | real=signed_real_number '+' imag=imaginary_number {
             _PyAST_BinOp(real, Add, imag, EXTRA) }
         | real=signed_real_number '-' imag=imaginary_number  {
             _PyAST_BinOp(real, Sub, imag, EXTRA) }

     signed_number[expr_ty]:
         | NUMBER
         | '-' number=NUMBER { _PyAST_UnaryOp(USub, number, EXTRA) }

     signed_real_number[expr_ty]:
         | real_number
         | '-' real=real_number { _PyAST_UnaryOp(USub, real, EXTRA) }

     real_number[expr_ty]:
         | real=NUMBER { _PyPegen_ensure_real(p, real) }

     imaginary_number[expr_ty]:
         | imag=NUMBER { _PyPegen_ensure_imaginary(p, imag) }

     capture_pattern[pattern_ty]:
         | target=pattern_capture_target { _PyAST_MatchAs(NULL, target->v.Name.id, EXTRA) }

     pattern_capture_target[expr_ty]:
         | !"_" name=NAME !('.' | '(' | '=') {
             _PyPegen_set_expr_context(p, name, Store) }

     wildcard_pattern[pattern_ty]:
         | "_" { _PyAST_MatchAs(NULL, NULL, EXTRA) }

     value_pattern[pattern_ty]:
         | attr=attr !('.' | '(' | '=') { _PyAST_MatchValue(attr, EXTRA) }

     attr[expr_ty]:
         | value=name_or_attr '.' attr=NAME {
             _PyAST_Attribute(value, attr->v.Name.id, Load, EXTRA) }

     name_or_attr[expr_ty]:
         | attr
         | NAME

     group_pattern[pattern_ty]:
         | '(' pattern=pattern ')' { pattern }

     sequence_pattern[pattern_ty]:
         | '[' patterns=maybe_sequence_pattern? ']' { _PyAST_MatchSequence(patterns, EXTRA) }
         | '(' patterns=open_sequence_pattern? ')' { _PyAST_MatchSequence(patterns, EXTRA) }

     open_sequence_pattern[asdl_seq*]:
         | pattern=maybe_star_pattern ',' patterns=maybe_sequence_pattern? {
             _PyPegen_seq_insert_in_front(p, pattern, patterns) }

     maybe_sequence_pattern[asdl_seq*]:
         | patterns=','.maybe_star_pattern+ ','? { patterns }

     maybe_star_pattern[pattern_ty]:
         | star_pattern
         | pattern

     star_pattern[pattern_ty] (memo):
         | '*' target=pattern_capture_target {
             _PyAST_MatchStar(target->v.Name.id, EXTRA) }
         | '*' wildcard_pattern {
             _PyAST_MatchStar(NULL, EXTRA) }

     mapping_pattern[pattern_ty]:
         | '{' '}' {
             _PyAST_MatchMapping(NULL, NULL, NULL, EXTRA) }
         | '{' rest=double_star_pattern ','? '}' {
             _PyAST_MatchMapping(NULL, NULL, rest->v.Name.id, EXTRA) }
         | '{' items=items_pattern ',' rest=double_star_pattern ','? '}' {
             _PyAST_MatchMapping(
                 CHECK(asdl_expr_seq*, _PyPegen_get_pattern_keys(p, items)),
                 CHECK(asdl_pattern_seq*, _PyPegen_get_patterns(p, items)),
                 rest->v.Name.id,
                 EXTRA) }
         | '{' items=items_pattern ','? '}' {
             _PyAST_MatchMapping(
                 CHECK(asdl_expr_seq*, _PyPegen_get_pattern_keys(p, items)),
                 CHECK(asdl_pattern_seq*, _PyPegen_get_patterns(p, items)),
                 NULL,
                 EXTRA) }

     items_pattern[asdl_seq*]:
         | ','.key_value_pattern+

     key_value_pattern[KeyPatternPair*]:
         | key=(literal_expr | attr) ':' pattern=pattern {
             _PyPegen_key_pattern_pair(p, key, pattern) }

     double_star_pattern[expr_ty]:
         | '**' target=pattern_capture_target { target }

     class_pattern[pattern_ty]:
         | cls=name_or_attr '(' ')' {
             _PyAST_MatchClass(cls, NULL, NULL, NULL, EXTRA) }
         | cls=name_or_attr '(' patterns=positional_patterns ','? ')' {
             _PyAST_MatchClass(cls, patterns, NULL, NULL, EXTRA) }
         | cls=name_or_attr '(' keywords=keyword_patterns ','? ')' {
             _PyAST_MatchClass(
                 cls, NULL,
                 CHECK(asdl_identifier_seq*, _PyPegen_map_names_to_ids(p,
                     CHECK(asdl_expr_seq*, _PyPegen_get_pattern_keys(p, keywords)))),
                 CHECK(asdl_pattern_seq*, _PyPegen_get_patterns(p, keywords)),
                 EXTRA) }
         | cls=name_or_attr '(' patterns=positional_patterns ',' keywords=keyword_patterns ','? ')' {
             _PyAST_MatchClass(
                 cls,
                 patterns,
                 CHECK(asdl_identifier_seq*, _PyPegen_map_names_to_ids(p,
                     CHECK(asdl_expr_seq*, _PyPegen_get_pattern_keys(p, keywords)))),
                 CHECK(asdl_pattern_seq*, _PyPegen_get_patterns(p, keywords)),
                 EXTRA) }
         | invalid_class_pattern

     positional_patterns[asdl_pattern_seq*]:
         | args[asdl_pattern_seq*]=','.pattern+ { args }

     keyword_patterns[asdl_seq*]:
         | ','.keyword_pattern+

     keyword_pattern[KeyPatternPair*]:
         | arg=NAME '=' value=pattern { _PyPegen_key_pattern_pair(p, arg, value) }

     # Type statement
     # ---------------

     type_alias[stmt_ty]:
         | "type" n=NAME t=[type_params] '=' b=expression {
             CHECK_VERSION(stmt_ty, 12, "Type statement is",
             _PyAST_TypeAlias(CHECK(expr_ty, _PyPegen_set_expr_context(p, n, Store)), t, b, EXTRA)) }

     # Type parameter declaration
     # --------------------------

     type_params[asdl_type_param_seq*]:
         | invalid_type_params
         | '[' t=type_param_seq ']' {
             CHECK_VERSION(asdl_type_param_seq *, 12, "Type parameter lists are", t) }

     type_param_seq[asdl_type_param_seq*]: a[asdl_type_param_seq*]=','.type_param+ [','] { a }

     type_param[type_param_ty] (memo):
         | a=NAME b=[type_param_bound] c=[type_param_default] { _PyAST_TypeVar(a->v.Name.id, b, c, EXTRA) }
         | '*' a=NAME colon=':' e=expression {
                 RAISE_SYNTAX_ERROR_STARTING_FROM(colon, e->kind == Tuple_kind
                     ? "cannot use constraints with TypeVarTuple"
                     : "cannot use bound with TypeVarTuple")
             }
         | '*' a=NAME b=[type_param_starred_default] { _PyAST_TypeVarTuple(a->v.Name.id, b, EXTRA) }
         | '**' a=NAME colon=':' e=expression {
                 RAISE_SYNTAX_ERROR_STARTING_FROM(colon, e->kind == Tuple_kind
                     ? "cannot use constraints with ParamSpec"
                     : "cannot use bound with ParamSpec")
             }
         | '**' a=NAME b=[type_param_default] { _PyAST_ParamSpec(a->v.Name.id, b, EXTRA) }

     type_param_bound[expr_ty]: ':' e=expression { e }
     type_param_default[expr_ty]: '=' e=expression {
         CHECK_VERSION(expr_ty, 13, "Type parameter defaults are", e) }
     type_param_starred_default[expr_ty]: '=' e=star_expression {
         CHECK_VERSION(expr_ty, 13, "Type parameter defaults are", e) }

     # EXPRESSIONS
     # -----------

     expressions[expr_ty]:
         | a=expression b=(',' c=expression { c })+ [','] {
             _PyAST_Tuple(CHECK(asdl_expr_seq*, _PyPegen_seq_insert_in_front(p, a, b)), Load, EXTRA) }
         | a=expression ',' { _PyAST_Tuple(CHECK(asdl_expr_seq*, _PyPegen_singleton_seq(p, a)), Load, EXTRA) }
         | expression

     expression[expr_ty] (memo):
         | invalid_expression
         | invalid_legacy_expression
         | a=disjunction 'if' b=disjunction 'else' c=expression { _PyAST_IfExp(b, a, c, EXTRA) }
         | disjunction
         | lambdef

     yield_expr[expr_ty]:
         | 'yield' 'from' a=expression { _PyAST_YieldFrom(a, EXTRA) }
         | 'yield' a=[star_expressions] { _PyAST_Yield(a, EXTRA) }

     star_expressions[expr_ty]:
         | a=star_expression b=(',' c=star_expression { c })+ [','] {
             _PyAST_Tuple(CHECK(asdl_expr_seq*, _PyPegen_seq_insert_in_front(p, a, b)), Load, EXTRA) }
         | a=star_expression ',' { _PyAST_Tuple(CHECK(asdl_expr_seq*, _PyPegen_singleton_seq(p, a)), Load, EXTRA) }
         | star_expression

     star_expression[expr_ty] (memo):
         | '*' a=bitwise_or { _PyAST_Starred(a, Load, EXTRA) }
         | expression

     star_named_expressions[asdl_expr_seq*]: a[asdl_expr_seq*]=','.star_named_expression+ [','] { a }

     star_named_expression[expr_ty]:
         | '*' a=bitwise_or { _PyAST_Starred(a, Load, EXTRA) }
         | named_expression

     assignment_expression[expr_ty]:
         | a=NAME ':=' ~ b=expression {
             CHECK_VERSION(expr_ty, 8, "Assignment expressions are",
             _PyAST_NamedExpr(CHECK(expr_ty, _PyPegen_set_expr_context(p, a, Store)), b, EXTRA)) }

     named_expression[expr_ty]:
         | assignment_expression
         | invalid_named_expression
         | expression !':='

     disjunction[expr_ty] (memo):
         | a=conjunction b=('or' c=conjunction { c })+ { _PyAST_BoolOp(
             Or,
             CHECK(asdl_expr_seq*, _PyPegen_seq_insert_in_front(p, a, b)),
             EXTRA) }
         | conjunction

     conjunction[expr_ty] (memo):
         | a=inversion b=('and' c=inversion { c })+ { _PyAST_BoolOp(
             And,
             CHECK(asdl_expr_seq*, _PyPegen_seq_insert_in_front(p, a, b)),
             EXTRA) }
         | inversion

     inversion[expr_ty] (memo):
         | 'not' a=inversion { _PyAST_UnaryOp(Not, a, EXTRA) }
         | comparison

     # Comparison operators
     # --------------------

     comparison[expr_ty]:
         | a=bitwise_or b=compare_op_bitwise_or_pair+ {
             _PyAST_Compare(
                 a,
                 CHECK(asdl_int_seq*, _PyPegen_get_cmpops(p, b)),
                 CHECK(asdl_expr_seq*, _PyPegen_get_exprs(p, b)),
                 EXTRA) }
         | bitwise_or

     compare_op_bitwise_or_pair[CmpopExprPair*]:
         | eq_bitwise_or
         | noteq_bitwise_or
         | lte_bitwise_or
         | lt_bitwise_or
         | gte_bitwise_or
         | gt_bitwise_or
         | notin_bitwise_or
         | in_bitwise_or
         | isnot_bitwise_or
         | is_bitwise_or

     eq_bitwise_or[CmpopExprPair*]: '==' a=bitwise_or { _PyPegen_cmpop_expr_pair(p, Eq, a) }
     noteq_bitwise_or[CmpopExprPair*]:
         | (tok='!=' { _PyPegen_check_barry_as_flufl(p, tok) ? NULL : tok}) a=bitwise_or {_PyPegen_cmpop_expr_pair(p, NotEq, a) }
     lte_bitwise_or[CmpopExprPair*]: '<=' a=bitwise_or { _PyPegen_cmpop_expr_pair(p, LtE, a) }
     lt_bitwise_or[CmpopExprPair*]: '<' a=bitwise_or { _PyPegen_cmpop_expr_pair(p, Lt, a) }
     gte_bitwise_or[CmpopExprPair*]: '>=' a=bitwise_or { _PyPegen_cmpop_expr_pair(p, GtE, a) }
     gt_bitwise_or[CmpopExprPair*]: '>' a=bitwise_or { _PyPegen_cmpop_expr_pair(p, Gt, a) }
     notin_bitwise_or[CmpopExprPair*]: 'not' 'in' a=bitwise_or { _PyPegen_cmpop_expr_pair(p, NotIn, a) }
     in_bitwise_or[CmpopExprPair*]: 'in' a=bitwise_or { _PyPegen_cmpop_expr_pair(p, In, a) }
     isnot_bitwise_or[CmpopExprPair*]: 'is' 'not' a=bitwise_or { _PyPegen_cmpop_expr_pair(p, IsNot, a) }
     is_bitwise_or[CmpopExprPair*]: 'is' a=bitwise_or { _PyPegen_cmpop_expr_pair(p, Is, a) }

     # Bitwise operators
     # -----------------

     bitwise_or[expr_ty]:
         | a=bitwise_or '|' b=bitwise_xor { _PyAST_BinOp(a, BitOr, b, EXTRA) }
         | bitwise_xor

     bitwise_xor[expr_ty]:
         | a=bitwise_xor '^' b=bitwise_and { _PyAST_BinOp(a, BitXor, b, EXTRA) }
         | bitwise_and

     bitwise_and[expr_ty]:
         | a=bitwise_and '&' b=shift_expr { _PyAST_BinOp(a, BitAnd, b, EXTRA) }
         | shift_expr

     shift_expr[expr_ty]:
         | a=shift_expr '<<' b=sum { _PyAST_BinOp(a, LShift, b, EXTRA) }
         | a=shift_expr '>>' b=sum { _PyAST_BinOp(a, RShift, b, EXTRA) }
         | invalid_arithmetic
         | sum

     # Arithmetic operators
     # --------------------

     sum[expr_ty]:
         | a=sum '+' b=term { _PyAST_BinOp(a, Add, b, EXTRA) }
         | a=sum '-' b=term { _PyAST_BinOp(a, Sub, b, EXTRA) }
         | term

     term[expr_ty]:
         | a=term '*' b=factor { _PyAST_BinOp(a, Mult, b, EXTRA) }
         | a=term '/' b=factor { _PyAST_BinOp(a, Div, b, EXTRA) }
         | a=term '//' b=factor { _PyAST_BinOp(a, FloorDiv, b, EXTRA) }
         | a=term '%' b=factor { _PyAST_BinOp(a, Mod, b, EXTRA) }
         | a=term '@' b=factor { CHECK_VERSION(expr_ty, 5, "The '@' operator is", _PyAST_BinOp(a, MatMult, b, EXTRA)) }
         | invalid_factor
         | factor

     factor[expr_ty] (memo):
         | '+' a=factor { _PyAST_UnaryOp(UAdd, a, EXTRA) }
         | '-' a=factor { _PyAST_UnaryOp(USub, a, EXTRA) }
         | '~' a=factor { _PyAST_UnaryOp(Invert, a, EXTRA) }
         | power

     power[expr_ty]:
         | a=await_primary '**' b=factor { _PyAST_BinOp(a, Pow, b, EXTRA) }
         | await_primary

     # Primary elements
     # ----------------

     # Primary elements are things like "obj.something.something", "obj[something]", "obj(something)", "obj" ...

     await_primary[expr_ty] (memo):
         | 'await' a=primary { CHECK_VERSION(expr_ty, 5, "Await expressions are", _PyAST_Await(a, EXTRA)) }
         | primary

     primary[expr_ty]:
         | a=primary '.' b=NAME { _PyAST_Attribute(a, b->v.Name.id, Load, EXTRA) }
         | a=primary b=genexp { _PyAST_Call(a, CHECK(asdl_expr_seq*, (asdl_expr_seq*)_PyPegen_singleton_seq(p, b)), NULL, EXTRA) }
         | a=primary '(' b=[arguments] ')' {
             _PyAST_Call(a,
                      (b) ? ((expr_ty) b)->v.Call.args : NULL,
                      (b) ? ((expr_ty) b)->v.Call.keywords : NULL,
                      EXTRA) }
         | a=primary '[' b=slices ']' { _PyAST_Subscript(a, b, Load, EXTRA) }
         | atom

     slices[expr_ty]:
         | a=slice !',' { a }
         | a[asdl_expr_seq*]=','.(slice | starred_expression)+ [','] { _PyAST_Tuple(a, Load, EXTRA) }

     slice[expr_ty]:
         | a=[expression] ':' b=[expression] c=[':' d=[expression] { d }] { _PyAST_Slice(a, b, c, EXTRA) }
         | a=named_expression { a }

     atom[expr_ty]:
         | NAME
         | 'True' { _PyAST_Constant(Py_True, NULL, EXTRA) }
         | 'False' { _PyAST_Constant(Py_False, NULL, EXTRA) }
         | 'None' { _PyAST_Constant(Py_None, NULL, EXTRA) }
         | &(STRING|FSTRING_START) strings
         | NUMBER
         | &'(' (tuple | group | genexp)
         | &'[' (list | listcomp)
         | &'{' (dict | set | dictcomp | setcomp)
         | '...' { _PyAST_Constant(Py_Ellipsis, NULL, EXTRA) }

     group[expr_ty]:
         | '(' a=(yield_expr | named_expression) ')' { a }
         | invalid_group

     # Lambda functions
     # ----------------

     lambdef[expr_ty]:
         | 'lambda' a=[lambda_params] ':' b=expression {
             _PyAST_Lambda((a) ? a : CHECK(arguments_ty, _PyPegen_empty_arguments(p)), b, EXTRA) }

     lambda_params[arguments_ty]:
         | invalid_lambda_parameters
         | lambda_parameters

     # lambda_parameters etc. duplicates parameters but without annotations
     # or type comments, and if there's no comma after a parameter, we expect
     # a colon, not a close parenthesis.  (For more, see parameters above.)
     #
     lambda_parameters[arguments_ty]:
         | a=lambda_slash_no_default b[asdl_arg_seq*]=lambda_param_no_default* c=lambda_param_with_default* d=[lambda_star_etc] {
             CHECK_VERSION(arguments_ty, 8, "Positional-only parameters are", _PyPegen_make_arguments(p, a, NULL, b, c, d)) }
         | a=lambda_slash_with_default b=lambda_param_with_default* c=[lambda_star_etc] {
             CHECK_VERSION(arguments_ty, 8, "Positional-only parameters are", _PyPegen_make_arguments(p, NULL, a, NULL, b, c)) }
         | a[asdl_arg_seq*]=lambda_param_no_default+ b=lambda_param_with_default* c=[lambda_star_etc] {
             _PyPegen_make_arguments(p, NULL, NULL, a, b, c) }
         | a=lambda_param_with_default+ b=[lambda_star_etc] { _PyPegen_make_arguments(p, NULL, NULL, NULL, a, b)}
         | a=lambda_star_etc { _PyPegen_make_arguments(p, NULL, NULL, NULL, NULL, a) }

     lambda_slash_no_default[asdl_arg_seq*]:
         | a[asdl_arg_seq*]=lambda_param_no_default+ '/' ',' { a }
         | a[asdl_arg_seq*]=lambda_param_no_default+ '/' &':' { a }

     lambda_slash_with_default[SlashWithDefault*]:
         | a=lambda_param_no_default* b=lambda_param_with_default+ '/' ',' { _PyPegen_slash_with_default(p, (asdl_arg_seq *)a, b) }
         | a=lambda_param_no_default* b=lambda_param_with_default+ '/' &':' { _PyPegen_slash_with_default(p, (asdl_arg_seq *)a, b) }

     lambda_star_etc[StarEtc*]:
         | invalid_lambda_star_etc
         | '*' a=lambda_param_no_default b=lambda_param_maybe_default* c=[lambda_kwds] {
             _PyPegen_star_etc(p, a, b, c) }
         | '*' ',' b=lambda_param_maybe_default+ c=[lambda_kwds] {
             _PyPegen_star_etc(p, NULL, b, c) }
         | a=lambda_kwds { _PyPegen_star_etc(p, NULL, NULL, a) }

     lambda_kwds[arg_ty]:
         | invalid_lambda_kwds
         | '**' a=lambda_param_no_default { a }

     lambda_param_no_default[arg_ty]:
         | a=lambda_param ',' { a }
         | a=lambda_param &':' { a }
     lambda_param_with_default[NameDefaultPair*]:
         | a=lambda_param c=default ',' { _PyPegen_name_default_pair(p, a, c, NULL) }
         | a=lambda_param c=default &':' { _PyPegen_name_default_pair(p, a, c, NULL) }
     lambda_param_maybe_default[NameDefaultPair*]:
         | a=lambda_param c=default? ',' { _PyPegen_name_default_pair(p, a, c, NULL) }
         | a=lambda_param c=default? &':' { _PyPegen_name_default_pair(p, a, c, NULL) }
     lambda_param[arg_ty]: a=NAME { _PyAST_arg(a->v.Name.id, NULL, NULL, EXTRA) }

     # LITERALS
     # ========

     fstring_middle[expr_ty]:
         | fstring_replacement_field
         | t=FSTRING_MIDDLE { _PyPegen_constant_from_token(p, t) }
     fstring_replacement_field[expr_ty]:
         | '{' a=annotated_rhs debug_expr='='? conversion=[fstring_conversion] format=[fstring_full_format_spec] rbrace='}' {
             _PyPegen_formatted_value(p, a, debug_expr, conversion, format, rbrace, EXTRA) }
         | invalid_replacement_field
     fstring_conversion[ResultTokenWithMetadata*]:
         | conv_token="!" conv=NAME { _PyPegen_check_fstring_conversion(p, conv_token, conv) }
     fstring_full_format_spec[ResultTokenWithMetadata*]:
         | colon=':' spec=fstring_format_spec* { _PyPegen_setup_full_format_spec(p, colon, (asdl_expr_seq *) spec, EXTRA) }
     fstring_format_spec[expr_ty]:
         | t=FSTRING_MIDDLE { _PyPegen_decoded_constant_from_token(p, t) }
         | fstring_replacement_field
     fstring[expr_ty]:
         | a=FSTRING_START b=fstring_middle* c=FSTRING_END { _PyPegen_joined_str(p, a, (asdl_expr_seq*)b, c) }

     string[expr_ty]: s[Token*]=STRING { _PyPegen_constant_from_string(p, s) }
     strings[expr_ty] (memo): a[asdl_expr_seq*]=(fstring|string)+ { _PyPegen_concatenate_strings(p, a, EXTRA) }

     list[expr_ty]:
         | '[' a=[star_named_expressions] ']' { _PyAST_List(a, Load, EXTRA) }

     tuple[expr_ty]:
         | '(' a=[y=star_named_expression ',' z=[star_named_expressions] { _PyPegen_seq_insert_in_front(p, y, z) } ] ')' {
             _PyAST_Tuple(a, Load, EXTRA) }

     set[expr_ty]: '{' a=star_named_expressions '}' { _PyAST_Set(a, EXTRA) }

     # Dicts
     # -----

     dict[expr_ty]:
         | '{' a=[double_starred_kvpairs] '}' {
             _PyAST_Dict(
                 CHECK(asdl_expr_seq*, _PyPegen_get_keys(p, a)),
                 CHECK(asdl_expr_seq*, _PyPegen_get_values(p, a)),
                 EXTRA) }
         | '{' invalid_double_starred_kvpairs '}'

     double_starred_kvpairs[asdl_seq*]: a=','.double_starred_kvpair+ [','] { a }

     double_starred_kvpair[KeyValuePair*]:
         | '**' a=bitwise_or { _PyPegen_key_value_pair(p, NULL, a) }
         | kvpair

     kvpair[KeyValuePair*]: a=expression ':' b=expression { _PyPegen_key_value_pair(p, a, b) }

     # Comprehensions & Generators
     # ---------------------------

     for_if_clauses[asdl_comprehension_seq*]:
         | a[asdl_comprehension_seq*]=for_if_clause+ { a }

     for_if_clause[comprehension_ty]:
         | 'async' 'for' a=star_targets 'in' ~ b=disjunction c[asdl_expr_seq*]=('if' z=disjunction { z })* {
             CHECK_VERSION(comprehension_ty, 6, "Async comprehensions are", _PyAST_comprehension(a, b, c, 1, p->arena)) }
         | 'for' a=star_targets 'in' ~ b=disjunction c[asdl_expr_seq*]=('if' z=disjunction { z })* {
             _PyAST_comprehension(a, b, c, 0, p->arena) }
         | 'async'? 'for' (bitwise_or (',' bitwise_or)* [',']) !'in' {
             RAISE_SYNTAX_ERROR("'in' expected after for-loop variables") }
         | invalid_for_target

     listcomp[expr_ty]:
         | '[' a=named_expression b=for_if_clauses ']' { _PyAST_ListComp(a, b, EXTRA) }
         | invalid_comprehension

     setcomp[expr_ty]:
         | '{' a=named_expression b=for_if_clauses '}' { _PyAST_SetComp(a, b, EXTRA) }
         | invalid_comprehension

     genexp[expr_ty]:
         | '(' a=( assignment_expression | expression !':=') b=for_if_clauses ')' { _PyAST_GeneratorExp(a, b, EXTRA) }
         | invalid_comprehension

     dictcomp[expr_ty]:
         | '{' a=kvpair b=for_if_clauses '}' { _PyAST_DictComp(a->key, a->value, b, EXTRA) }
         | invalid_dict_comprehension

     # FUNCTION CALL ARGUMENTS
     # =======================

     arguments[expr_ty] (memo):
         | a=args [','] &')' { a }
         | invalid_arguments

     args[expr_ty]:
         | a[asdl_expr_seq*]=','.(starred_expression | ( assignment_expression | expression !':=') !'=')+ b=[',' k=kwargs {k}] {
             _PyPegen_collect_call_seqs(p, a, b, EXTRA) }
         | a=kwargs { _PyAST_Call(_PyPegen_dummy_name(p),
                               CHECK_NULL_ALLOWED(asdl_expr_seq*, _PyPegen_seq_extract_starred_exprs(p, a)),
                               CHECK_NULL_ALLOWED(asdl_keyword_seq*, _PyPegen_seq_delete_starred_exprs(p, a)),
                               EXTRA) }

     kwargs[asdl_seq*]:
         | a=','.kwarg_or_starred+ ',' b=','.kwarg_or_double_starred+ { _PyPegen_join_sequences(p, a, b) }
         | ','.kwarg_or_starred+
         | ','.kwarg_or_double_starred+

     starred_expression[expr_ty]:
         | invalid_starred_expression
         | '*' a=expression { _PyAST_Starred(a, Load, EXTRA) }
         | '*' { RAISE_SYNTAX_ERROR("Invalid star expression") }

     kwarg_or_starred[KeywordOrStarred*]:
         | invalid_kwarg
         | a=NAME '=' b=expression {
             _PyPegen_keyword_or_starred(p, CHECK(keyword_ty, _PyAST_keyword(a->v.Name.id, b, EXTRA)), 1) }
         | a=starred_expression { _PyPegen_keyword_or_starred(p, a, 0) }

     kwarg_or_double_starred[KeywordOrStarred*]:
         | invalid_kwarg
         | a=NAME '=' b=expression {
             _PyPegen_keyword_or_starred(p, CHECK(keyword_ty, _PyAST_keyword(a->v.Name.id, b, EXTRA)), 1) }
         | '**' a=expression { _PyPegen_keyword_or_starred(p, CHECK(keyword_ty, _PyAST_keyword(NULL, a, EXTRA)), 1) }

     # ASSIGNMENT TARGETS
     # ==================

     # Generic targets
     # ---------------

     # NOTE: star_targets may contain *bitwise_or, targets may not.
     star_targets[expr_ty]:
         | a=star_target !',' { a }
         | a=star_target b=(',' c=star_target { c })* [','] {
             _PyAST_Tuple(CHECK(asdl_expr_seq*, _PyPegen_seq_insert_in_front(p, a, b)), Store, EXTRA) }

     star_targets_list_seq[asdl_expr_seq*]: a[asdl_expr_seq*]=','.star_target+ [','] { a }

     star_targets_tuple_seq[asdl_expr_seq*]:
         | a=star_target b=(',' c=star_target { c })+ [','] { (asdl_expr_seq*) _PyPegen_seq_insert_in_front(p, a, b) }
         | a=star_target ',' { (asdl_expr_seq*) _PyPegen_singleton_seq(p, a) }

     star_target[expr_ty] (memo):
         | '*' a=(!'*' star_target) {
             _PyAST_Starred(CHECK(expr_ty, _PyPegen_set_expr_context(p, a, Store)), Store, EXTRA) }
         | target_with_star_atom

     target_with_star_atom[expr_ty] (memo):
         | a=t_primary '.' b=NAME !t_lookahead { _PyAST_Attribute(a, b->v.Name.id, Store, EXTRA) }
         | a=t_primary '[' b=slices ']' !t_lookahead { _PyAST_Subscript(a, b, Store, EXTRA) }
         | star_atom

     star_atom[expr_ty]:
         | a=NAME { _PyPegen_set_expr_context(p, a, Store) }
         | '(' a=target_with_star_atom ')' { _PyPegen_set_expr_context(p, a, Store) }
         | '(' a=[star_targets_tuple_seq] ')' { _PyAST_Tuple(a, Store, EXTRA) }
         | '[' a=[star_targets_list_seq] ']' { _PyAST_List(a, Store, EXTRA) }

     single_target[expr_ty]:
         | single_subscript_attribute_target
         | a=NAME { _PyPegen_set_expr_context(p, a, Store) }
         | '(' a=single_target ')' { a }

     single_subscript_attribute_target[expr_ty]:
         | a=t_primary '.' b=NAME !t_lookahead { _PyAST_Attribute(a, b->v.Name.id, Store, EXTRA) }
         | a=t_primary '[' b=slices ']' !t_lookahead { _PyAST_Subscript(a, b, Store, EXTRA) }

     t_primary[expr_ty]:
         | a=t_primary '.' b=NAME &t_lookahead { _PyAST_Attribute(a, b->v.Name.id, Load, EXTRA) }
         | a=t_primary '[' b=slices ']' &t_lookahead { _PyAST_Subscript(a, b, Load, EXTRA) }
         | a=t_primary b=genexp &t_lookahead {
             _PyAST_Call(a, CHECK(asdl_expr_seq*, (asdl_expr_seq*)_PyPegen_singleton_seq(p, b)), NULL, EXTRA) }
         | a=t_primary '(' b=[arguments] ')' &t_lookahead {
             _PyAST_Call(a,
                      (b) ? ((expr_ty) b)->v.Call.args : NULL,
                      (b) ? ((expr_ty) b)->v.Call.keywords : NULL,
                      EXTRA) }
         | a=atom &t_lookahead { a }

     t_lookahead: '(' | '[' | '.'

     # Targets for del statements
     # --------------------------

     del_targets[asdl_expr_seq*]: a[asdl_expr_seq*]=','.del_target+ [','] { a }

     del_target[expr_ty] (memo):
         | a=t_primary '.' b=NAME !t_lookahead { _PyAST_Attribute(a, b->v.Name.id, Del, EXTRA) }
         | a=t_primary '[' b=slices ']' !t_lookahead { _PyAST_Subscript(a, b, Del, EXTRA) }
         | del_t_atom

     del_t_atom[expr_ty]:
         | a=NAME { _PyPegen_set_expr_context(p, a, Del) }
         | '(' a=del_target ')' { _PyPegen_set_expr_context(p, a, Del) }
         | '(' a=[del_targets] ')' { _PyAST_Tuple(a, Del, EXTRA) }
         | '[' a=[del_targets] ']' { _PyAST_List(a, Del, EXTRA) }

     # TYPING ELEMENTS
     # ---------------

     # type_expressions allow */** but ignore them
     type_expressions[asdl_expr_seq*]:
         | a=','.expression+ ',' '*' b=expression ',' '**' c=expression {
             (asdl_expr_seq*)_PyPegen_seq_append_to_end(
                 p,
                 CHECK(asdl_seq*, _PyPegen_seq_append_to_end(p, a, b)),
                 c) }
         | a=','.expression+ ',' '*' b=expression { (asdl_expr_seq*)_PyPegen_seq_append_to_end(p, a, b) }
         | a=','.expression+ ',' '**' b=expression { (asdl_expr_seq*)_PyPegen_seq_append_to_end(p, a, b) }
         | '*' a=expression ',' '**' b=expression {
             (asdl_expr_seq*)_PyPegen_seq_append_to_end(
                 p,
                 CHECK(asdl_seq*, _PyPegen_singleton_seq(p, a)),
                 b) }
         | '*' a=expression { (asdl_expr_seq*)_PyPegen_singleton_seq(p, a) }
         | '**' a=expression { (asdl_expr_seq*)_PyPegen_singleton_seq(p, a) }
         | a[asdl_expr_seq*]=','.expression+ {a}

     func_type_comment[Token*]:
         | NEWLINE t=TYPE_COMMENT &(NEWLINE INDENT) { t }  # Must be followed by indented block
         | invalid_double_type_comments
         | TYPE_COMMENT

     # ========================= END OF THE GRAMMAR ===========================



     # ========================= START OF INVALID RULES =======================

     # From here on, there are rules for invalid syntax with specialised error messages
     invalid_arguments:
         | ((','.(starred_expression | ( assignment_expression | expression !':=') !'=')+ ',' kwargs) | kwargs) a=',' ','.(starred_expression !'=')+ {
             RAISE_SYNTAX_ERROR_STARTING_FROM(a, "iterable argument unpacking follows keyword argument unpacking") }
         | a=expression b=for_if_clauses ',' [args | expression for_if_clauses] {
             RAISE_SYNTAX_ERROR_KNOWN_RANGE(a, _PyPegen_get_last_comprehension_item(PyPegen_last_item(b, comprehension_ty)), "Generator expression must be parenthesized") }
         | a=NAME b='=' expression for_if_clauses {
             RAISE_SYNTAX_ERROR_KNOWN_RANGE(a, b, "invalid syntax. Maybe you meant '==' or ':=' instead of '='?")}
         | (args ',')? a=NAME b='=' &(',' | ')') {
             RAISE_SYNTAX_ERROR_KNOWN_RANGE(a, b, "expected argument value expression")}
         | a=args b=for_if_clauses { _PyPegen_nonparen_genexp_in_call(p, a, b) }
         | args ',' a=expression b=for_if_clauses {
             RAISE_SYNTAX_ERROR_KNOWN_RANGE(a, _PyPegen_get_last_comprehension_item(PyPegen_last_item(b, comprehension_ty)), "Generator expression must be parenthesized") }
         | a=args ',' args { _PyPegen_arguments_parsing_error(p, a) }
     invalid_kwarg:
         | a[Token*]=('True'|'False'|'None') b='=' {
             RAISE_SYNTAX_ERROR_KNOWN_RANGE(a, b, "cannot assign to %s", PyBytes_AS_STRING(a->bytes)) }
         | a=NAME b='=' expression for_if_clauses {
             RAISE_SYNTAX_ERROR_KNOWN_RANGE(a, b, "invalid syntax. Maybe you meant '==' or ':=' instead of '='?")}
         | !(NAME '=') a=expression b='=' {
             RAISE_SYNTAX_ERROR_KNOWN_RANGE(
                 a, b, "expression cannot contain assignment, perhaps you meant \"==\"?") }
         | a='**' expression '=' b=expression {
             RAISE_SYNTAX_ERROR_KNOWN_RANGE(a, b, "cannot assign to keyword argument unpacking") }

     # IMPORTANT: Note that the "_without_invalid" suffix causes the rule to not call invalid rules under it
     expression_without_invalid[expr_ty]:
         | a=disjunction 'if' b=disjunction 'else' c=expression { _PyAST_IfExp(b, a, c, EXTRA) }
         | disjunction
         | lambdef
     invalid_legacy_expression:
         | a=NAME !'(' b=star_expressions {
             _PyPegen_check_legacy_stmt(p, a) ? RAISE_SYNTAX_ERROR_KNOWN_RANGE(a, b,
                 "Missing parentheses in call to '%U'. Did you mean %U(...)?", a->v.Name.id, a->v.Name.id) : NULL}

     invalid_expression:
         # !(NAME STRING) is not matched so we don't show this error with some invalid string prefixes like: kf"dsfsdf"
         # Soft keywords need to also be ignored because they can be parsed as NAME NAME
        | !(NAME STRING | SOFT_KEYWORD) a=disjunction b=expression_without_invalid {
             _PyPegen_check_legacy_stmt(p, a) ? NULL : p->tokens[p->mark-1]->level == 0 ? NULL :
             RAISE_SYNTAX_ERROR_KNOWN_RANGE(a, b, "invalid syntax. Perhaps you forgot a comma?") }
        | a=disjunction 'if' b=disjunction !('else'|':') { RAISE_SYNTAX_ERROR_KNOWN_RANGE(a, b, "expected 'else' after 'if' expression") }
        | a='lambda' [lambda_params] b=':' &FSTRING_MIDDLE  {
             RAISE_SYNTAX_ERROR_KNOWN_RANGE(a, b, "f-string: lambda expressions are not allowed without parentheses") }

     invalid_named_expression(memo):
         | a=expression ':=' expression {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(
                 a, "cannot use assignment expressions with %s", _PyPegen_get_expr_name(a)) }
         | a=NAME '=' b=bitwise_or !('='|':=') {
             RAISE_SYNTAX_ERROR_KNOWN_RANGE(a, b, "invalid syntax. Maybe you meant '==' or ':=' instead of '='?") }
         | !(list|tuple|genexp|'True'|'None'|'False') a=bitwise_or b='=' bitwise_or !('='|':=') {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "cannot assign to %s here. Maybe you meant '==' instead of '='?",
                                               _PyPegen_get_expr_name(a)) }

     invalid_assignment:
         | a=invalid_ann_assign_target ':' expression {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(
                 a,
                 "only single target (not %s) can be annotated",
                 _PyPegen_get_expr_name(a)
             )}
         | a=star_named_expression ',' star_named_expressions* ':' expression {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "only single target (not tuple) can be annotated") }
         | a=expression ':' expression {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "illegal target for annotation") }
         | (star_targets '=')* a=star_expressions '=' {
             RAISE_SYNTAX_ERROR_INVALID_TARGET(STAR_TARGETS, a) }
         | (star_targets '=')* a=yield_expr '=' { RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "assignment to yield expression not possible") }
         | a=star_expressions augassign annotated_rhs {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(
                 a,
                 "'%s' is an illegal expression for augmented assignment",
                 _PyPegen_get_expr_name(a)
             )}
     invalid_ann_assign_target[expr_ty]:
         | list
         | tuple
         | '(' a=invalid_ann_assign_target ')' { a }
     invalid_del_stmt:
         | 'del' a=star_expressions {
             RAISE_SYNTAX_ERROR_INVALID_TARGET(DEL_TARGETS, a) }
     invalid_block:
         | NEWLINE !INDENT { RAISE_INDENTATION_ERROR("expected an indented block") }
     invalid_comprehension:
         | ('[' | '(' | '{') a=starred_expression for_if_clauses {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "iterable unpacking cannot be used in comprehension") }
         | ('[' | '{') a=star_named_expression ',' b=star_named_expressions for_if_clauses {
             RAISE_SYNTAX_ERROR_KNOWN_RANGE(a, PyPegen_last_item(b, expr_ty),
             "did you forget parentheses around the comprehension target?") }
         | ('[' | '{') a=star_named_expression b=',' for_if_clauses {
             RAISE_SYNTAX_ERROR_KNOWN_RANGE(a, b, "did you forget parentheses around the comprehension target?") }
     invalid_dict_comprehension:
         | '{' a='**' bitwise_or for_if_clauses '}' {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "dict unpacking cannot be used in dict comprehension") }
     invalid_parameters:
         | a="/" ',' {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "at least one argument must precede /") }
         | (slash_no_default | slash_with_default) param_maybe_default* a='/' {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "/ may appear only once") }
         | slash_no_default? param_no_default* invalid_parameters_helper a=param_no_default {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "parameter without a default follows parameter with a default") }
         | param_no_default* a='(' param_no_default+ ','? b=')' {
             RAISE_SYNTAX_ERROR_KNOWN_RANGE(a, b, "Function parameters cannot be parenthesized") }
         | (slash_no_default | slash_with_default)? param_maybe_default* '*' (',' | param_no_default) param_maybe_default* a='/' {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "/ must be ahead of *") }
         | param_maybe_default+ '/' a='*' {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "expected comma between / and *") }
     invalid_default:
         | a='=' &(')'|',') { RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "expected default value expression") }
     invalid_star_etc:
         | a='*' (')' | ',' (')' | '**')) { RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "named arguments must follow bare *") }
         | '*' ',' TYPE_COMMENT { RAISE_SYNTAX_ERROR("bare * has associated type comment") }
         | '*' param a='=' { RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "var-positional argument cannot have default value") }
         | '*' (param_no_default | ',') param_maybe_default* a='*' (param_no_default | ',') {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "* argument may appear only once") }
     invalid_kwds:
         | '**' param a='=' { RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "var-keyword argument cannot have default value") }
         | '**' param ',' a=param { RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "arguments cannot follow var-keyword argument") }
         | '**' param ',' a[Token*]=('*'|'**'|'/') { RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "arguments cannot follow var-keyword argument") }
     invalid_parameters_helper: # This is only there to avoid type errors
         | a=slash_with_default { _PyPegen_singleton_seq(p, a) }
         | param_with_default+
     invalid_lambda_parameters:
         | a="/" ',' {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "at least one argument must precede /") }
         | (lambda_slash_no_default | lambda_slash_with_default) lambda_param_maybe_default* a='/' {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "/ may appear only once") }
         | lambda_slash_no_default? lambda_param_no_default* invalid_lambda_parameters_helper a=lambda_param_no_default {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "parameter without a default follows parameter with a default") }
         | lambda_param_no_default* a='(' ','.lambda_param+ ','? b=')' {
             RAISE_SYNTAX_ERROR_KNOWN_RANGE(a, b, "Lambda expression parameters cannot be parenthesized") }
         | (lambda_slash_no_default | lambda_slash_with_default)? lambda_param_maybe_default* '*' (',' | lambda_param_no_default) lambda_param_maybe_default* a='/' {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "/ must be ahead of *") }
         | lambda_param_maybe_default+ '/' a='*' {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "expected comma between / and *") }
     invalid_lambda_parameters_helper:
         | a=lambda_slash_with_default { _PyPegen_singleton_seq(p, a) }
         | lambda_param_with_default+
     invalid_lambda_star_etc:
         | '*' (':' | ',' (':' | '**')) { RAISE_SYNTAX_ERROR("named arguments must follow bare *") }
         | '*' lambda_param a='=' { RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "var-positional argument cannot have default value") }
         | '*' (lambda_param_no_default | ',') lambda_param_maybe_default* a='*' (lambda_param_no_default | ',') {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "* argument may appear only once") }
     invalid_lambda_kwds:
         | '**' lambda_param a='=' { RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "var-keyword argument cannot have default value") }
         | '**' lambda_param ',' a=lambda_param { RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "arguments cannot follow var-keyword argument") }
         | '**' lambda_param ',' a[Token*]=('*'|'**'|'/') { RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "arguments cannot follow var-keyword argument") }
     invalid_double_type_comments:
         | TYPE_COMMENT NEWLINE TYPE_COMMENT NEWLINE INDENT {
             RAISE_SYNTAX_ERROR("Cannot have two type comments on def") }
     invalid_with_item:
         | expression 'as' a=expression &(',' | ')' | ':') {
             RAISE_SYNTAX_ERROR_INVALID_TARGET(STAR_TARGETS, a) }

     invalid_for_target:
         | 'async'? 'for' a=star_expressions {
             RAISE_SYNTAX_ERROR_INVALID_TARGET(FOR_TARGETS, a) }

     invalid_group:
         | '(' a=starred_expression ')' {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "cannot use starred expression here") }
         | '(' a='**' expression ')' {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "cannot use double starred expression here") }
     invalid_import:
         | a='import' ','.dotted_name+ 'from' dotted_name {
             RAISE_SYNTAX_ERROR_STARTING_FROM(a, "Did you mean to use 'from ... import ...' instead?") }
         | 'import' token=NEWLINE {
             RAISE_SYNTAX_ERROR_STARTING_FROM(token, "Expected one or more names after 'import'") }

     invalid_import_from_targets:
         | import_from_as_names ',' NEWLINE {
             RAISE_SYNTAX_ERROR("trailing comma not allowed without surrounding parentheses") }
         | token=NEWLINE {
             RAISE_SYNTAX_ERROR_STARTING_FROM(token, "Expected one or more names after 'import'") }

     invalid_with_stmt:
         | ['async'] 'with' ','.(expression ['as' star_target])+ NEWLINE { RAISE_SYNTAX_ERROR("expected ':'") }
         | ['async'] 'with' '(' ','.(expressions ['as' star_target])+ ','? ')' NEWLINE { RAISE_SYNTAX_ERROR("expected ':'") }
     invalid_with_stmt_indent:
         | ['async'] a='with' ','.(expression ['as' star_target])+ ':' NEWLINE !INDENT {
             RAISE_INDENTATION_ERROR("expected an indented block after 'with' statement on line %d", a->lineno) }
         | ['async'] a='with' '(' ','.(expressions ['as' star_target])+ ','? ')' ':' NEWLINE !INDENT {
             RAISE_INDENTATION_ERROR("expected an indented block after 'with' statement on line %d", a->lineno) }

     invalid_try_stmt:
         | a='try' ':' NEWLINE !INDENT {
             RAISE_INDENTATION_ERROR("expected an indented block after 'try' statement on line %d", a->lineno) }
         | 'try' ':' block !('except' | 'finally') { RAISE_SYNTAX_ERROR("expected 'except' or 'finally' block") }
         | 'try' ':' block* except_block+ a='except' b='*' expression ['as' NAME] ':' {
             RAISE_SYNTAX_ERROR_KNOWN_RANGE(a, b, "cannot have both 'except' and 'except*' on the same 'try'") }
         | 'try' ':' block* except_star_block+ a='except' [expression ['as' NAME]] ':' {
             RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "cannot have both 'except' and 'except*' on the same 'try'") }
     invalid_except_stmt:
         | 'except' '*'? a=expression ',' expressions ['as' NAME ] ':' {
             RAISE_SYNTAX_ERROR_STARTING_FROM(a, "multiple exception types must be parenthesized") }
         | a='except' '*'? expression ['as' NAME ] NEWLINE { RAISE_SYNTAX_ERROR("expected ':'") }
         | a='except' NEWLINE { RAISE_SYNTAX_ERROR("expected ':'") }
         | a='except' '*' (NEWLINE | ':') { RAISE_SYNTAX_ERROR("expected one or more exception types") }
     invalid_finally_stmt:
         | a='finally' ':' NEWLINE !INDENT {
             RAISE_INDENTATION_ERROR("expected an indented block after 'finally' statement on line %d", a->lineno) }
     invalid_except_stmt_indent:
         | a='except' expression ['as' NAME ] ':' NEWLINE !INDENT {
             RAISE_INDENTATION_ERROR("expected an indented block after 'except' statement on line %d", a->lineno) }
         | a='except' ':' NEWLINE !INDENT { RAISE_INDENTATION_ERROR("expected an indented block after 'except' statement on line %d", a->lineno) }
     invalid_except_star_stmt_indent:
         | a='except' '*' expression ['as' NAME ] ':' NEWLINE !INDENT {
             RAISE_INDENTATION_ERROR("expected an indented block after 'except*' statement on line %d", a->lineno) }
     invalid_match_stmt:
         | "match" subject_expr NEWLINE { CHECK_VERSION(void*, 10, "Pattern matching is", RAISE_SYNTAX_ERROR("expected ':'") ) }
         | a="match" subject=subject_expr ':' NEWLINE !INDENT {
             RAISE_INDENTATION_ERROR("expected an indented block after 'match' statement on line %d", a->lineno) }
     invalid_case_block:
         | "case" patterns guard? NEWLINE { RAISE_SYNTAX_ERROR("expected ':'") }
         | a="case" patterns guard? ':' NEWLINE !INDENT {
             RAISE_INDENTATION_ERROR("expected an indented block after 'case' statement on line %d", a->lineno) }
     invalid_as_pattern:
         | or_pattern 'as' a="_" { RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "cannot use '_' as a target") }
         | or_pattern 'as' !NAME a=expression { RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "invalid pattern target") }
     invalid_class_pattern:
         | name_or_attr '(' a=invalid_class_argument_pattern  { RAISE_SYNTAX_ERROR_KNOWN_RANGE(
             PyPegen_first_item(a, pattern_ty),
             PyPegen_last_item(a, pattern_ty),
             "positional patterns follow keyword patterns") }
     invalid_class_argument_pattern[asdl_pattern_seq*]:
         | [positional_patterns ','] keyword_patterns ',' a=positional_patterns { a }
     invalid_if_stmt:
         | 'if' named_expression NEWLINE { RAISE_SYNTAX_ERROR("expected ':'") }
         | a='if' a=named_expression ':' NEWLINE !INDENT {
             RAISE_INDENTATION_ERROR("expected an indented block after 'if' statement on line %d", a->lineno) }
     invalid_elif_stmt:
         | 'elif' named_expression NEWLINE { RAISE_SYNTAX_ERROR("expected ':'") }
         | a='elif' named_expression ':' NEWLINE !INDENT {
             RAISE_INDENTATION_ERROR("expected an indented block after 'elif' statement on line %d", a->lineno) }
     invalid_else_stmt:
         | a='else' ':' NEWLINE !INDENT {
             RAISE_INDENTATION_ERROR("expected an indented block after 'else' statement on line %d", a->lineno) }
     invalid_while_stmt:
         | 'while' named_expression NEWLINE { RAISE_SYNTAX_ERROR("expected ':'") }
         | a='while' named_expression ':' NEWLINE !INDENT {
             RAISE_INDENTATION_ERROR("expected an indented block after 'while' statement on line %d", a->lineno) }
     invalid_for_stmt:
         | ['async'] 'for' star_targets 'in' star_expressions NEWLINE { RAISE_SYNTAX_ERROR("expected ':'") }
         | ['async'] a='for' star_targets 'in' star_expressions ':' NEWLINE !INDENT {
             RAISE_INDENTATION_ERROR("expected an indented block after 'for' statement on line %d", a->lineno) }
     invalid_def_raw:
         | ['async'] a='def' NAME [type_params] '(' [params] ')' ['->' expression] ':' NEWLINE !INDENT {
             RAISE_INDENTATION_ERROR("expected an indented block after function definition on line %d", a->lineno) }
         | ['async'] 'def' NAME [type_params] &&'(' [params] ')' ['->' expression] &&':' [func_type_comment] block
     invalid_class_def_raw:
         | 'class' NAME [type_params] ['(' [arguments] ')'] NEWLINE { RAISE_SYNTAX_ERROR("expected ':'") }
         | a='class' NAME [type_params] ['(' [arguments] ')'] ':' NEWLINE !INDENT {
             RAISE_INDENTATION_ERROR("expected an indented block after class definition on line %d", a->lineno) }

     invalid_double_starred_kvpairs:
         | ','.double_starred_kvpair+ ',' invalid_kvpair
         | expression ':' a='*' bitwise_or { RAISE_SYNTAX_ERROR_STARTING_FROM(a, "cannot use a starred expression in a dictionary value") }
         | expression a=':' &('}'|',') { RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "expression expected after dictionary key and ':'") }
     invalid_kvpair:
         | a=expression !(':') {
             RAISE_ERROR_KNOWN_LOCATION(p, PyExc_SyntaxError, a->lineno, a->end_col_offset - 1, a->end_lineno, -1, "':' expected after dictionary key") }
         | expression ':' a='*' bitwise_or { RAISE_SYNTAX_ERROR_STARTING_FROM(a, "cannot use a starred expression in a dictionary value") }
         | expression a=':' &('}'|',') {RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "expression expected after dictionary key and ':'") }
     invalid_starred_expression:
         | a='*' expression '=' b=expression { RAISE_SYNTAX_ERROR_KNOWN_RANGE(a, b, "cannot assign to iterable argument unpacking") }

     invalid_replacement_field:
         | '{' a='=' { RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "f-string: valid expression required before '='") }
         | '{' a='!' { RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "f-string: valid expression required before '!'") }
         | '{' a=':' { RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "f-string: valid expression required before ':'") }
         | '{' a='}' { RAISE_SYNTAX_ERROR_KNOWN_LOCATION(a, "f-string: valid expression required before '}'") }
         | '{' !annotated_rhs { RAISE_SYNTAX_ERROR_ON_NEXT_TOKEN("f-string: expecting a valid expression after '{'")}
         | '{' annotated_rhs !('=' | '!' | ':' | '}') {
             PyErr_Occurred() ? NULL : RAISE_SYNTAX_ERROR_ON_NEXT_TOKEN("f-string: expecting '=', or '!', or ':', or '}'") }
         | '{' annotated_rhs '=' !('!' | ':' | '}') {
             PyErr_Occurred() ? NULL : RAISE_SYNTAX_ERROR_ON_NEXT_TOKEN("f-string: expecting '!', or ':', or '}'") }
         | '{' annotated_rhs '='? invalid_conversion_character
         | '{' annotated_rhs '='? ['!' NAME] !(':' | '}') {
             PyErr_Occurred() ? NULL : RAISE_SYNTAX_ERROR_ON_NEXT_TOKEN("f-string: expecting ':' or '}'") }
         | '{' annotated_rhs '='? ['!' NAME] ':' fstring_format_spec* !'}' {
             PyErr_Occurred() ? NULL : RAISE_SYNTAX_ERROR_ON_NEXT_TOKEN("f-string: expecting '}', or format specs") }
         | '{' annotated_rhs '='? ['!' NAME] !'}' {
             PyErr_Occurred() ? NULL : RAISE_SYNTAX_ERROR_ON_NEXT_TOKEN("f-string: expecting '}'") }

     invalid_conversion_character:
         | '!' &(':' | '}') { RAISE_SYNTAX_ERROR_ON_NEXT_TOKEN("f-string: missing conversion character") }
         | '!' !NAME { RAISE_SYNTAX_ERROR_ON_NEXT_TOKEN("f-string: invalid conversion character") }

     invalid_arithmetic:
         | sum ('+'|'-'|'*'|'/'|'%'|'//'|'@') a='not' b=inversion { RAISE_SYNTAX_ERROR_KNOWN_RANGE(a, b, "'not' after an operator must be parenthesized") }
     invalid_factor:
         | ('+' | '-' | '~') a='not' b=factor { RAISE_SYNTAX_ERROR_KNOWN_RANGE(a, b, "'not' after an operator must be parenthesized") }

     invalid_type_params:
         | '[' token=']' {
             RAISE_SYNTAX_ERROR_STARTING_FROM(
                 token,
                 "Type parameter list cannot be empty")}

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Grammar/python.gram

   (2) https://en.wikipedia.org/wiki/Extended_Backus%E2%80%93Naur_form

   (3) https://en.wikipedia.org/wiki/Parsing_expression_grammar

   (4) https://peps.python.org/pep-0617/


File: python.info,  Node: Python 標準函式庫 Standard Library,  Next: 擴充和嵌入 Python 直譯器,  Prev: Python 語言參考手冊,  Up: Top

5 Python 標準函式庫 (Standard Library)
**************************************

*note Python 語言參考手冊: 12b.說明 Python 這門語言確切的文法及語意，而
這份函式庫參考手冊則是說明隨著 Python 一起發佈的標準函式庫，除此之外，其
內容也包含一些時常出現在 Python 發佈版本中的非必要套件。

Python 的標準函式庫是非常龐大的，其提供了如下所述極多且涵蓋用途極廣的許
多模組。包含一些用 C 語言撰寫，可以操作像是檔案讀寫等系統相關功能的內建
模組，當然也有用 Python 撰寫，並使用標準解法解決許多常見問題的模組。其中
有些模組則是特別針對 Python 的可攜性去設計的，為此特地將一些平台特殊相依
性的功能抽象化成可跨平台的 API。

Python 的 Windows 安裝檔基本上包含整個標準函式庫，且通常也包含許多附加的
組件；而在類 Unix 作業系統方面，Python 通常是以一系列的套件被安裝，因此
對於某些或全部的可選組件，可能都必須使用該作業系統提供的套件管理工具來安
裝。

在標準函式庫之外，還有成千上萬且不斷增加的組件（從個別的程式、模組、套件
到完整的應用程式開發框架），可以從 Python 套件索引 (Python Package
Index)(1) 中取得。

* Menu:

* 簡介: 簡介<6>.
* 內建函式::
* 內建常數::
* 內建型別::
* 內建的例外::
* 文本處理 (Text Processing) 服務: 文本處理 Text Processing 服務.
* 二進位資料服務::
* 資料型別::
* 數值與數學模組::
* 函式編程模組::
* 檔案與目錄存取::
* 資料持久性 (Data Persistence): 資料持久性 Data Persistence.
* 資料壓縮與保存::
* 檔案格式::
* 加密服務::
* 通用作業系統服務::
* 並行執行 (Concurrent Execution): 並行執行 Concurrent Execution.
* Networking and Interprocess Communication::
* 網際網路資料處理::
* Structured Markup Processing Tools::
* 網路協定 (Internet protocols) 及支援: 網路協定 Internet protocols 及支援.
* 多媒體服務::
* 國際化::
* 程式框架::
* 以 Tk 打造圖形使用者介面 (Graphical User Interfaces): 以 Tk 打造圖形使用者介面 Graphical User Interfaces.
* 開發工具::
* 除錯與效能分析::
* 軟體封裝與發布::
* Python Runtime 服務::
* 自訂 Python 直譯器::
* 引入模組::
* Python 語言服務::
* MS Windows 特有服務::
* Unix 特有服務::
* 模組命令列介面::
* 已被取代的模組::
* 安全性注意事項: 安全性注意事項<4>.

   ---------- Footnotes ----------

   (1) https://pypi.org


File: python.info,  Node: 簡介<6>,  Next: 內建函式,  Up: Python 標準函式庫 Standard Library

5.1 簡介
========

「Python 函式庫」包含了許多不同的部分。

函式庫中包括被視為程式語言「核心」部分的資料型態，像是數字 (number) 或是
串列 (list)。對於這些型別，Python 核心對這些字面值 (literal) 的形式做定
義，並對它們的語意制定了一些限制，但在此同時卻不把文字對應的語意完全定義
。（另一方面，Python 在語法面上有確實的定義，例如拼字或是運算元次序）

Python 函式庫也囊括了內建函式與例外處理——這些物件都可以不用透過 *note
import: 586. 陳述式來引入 Python 程式中就能使用。函式庫中有部份是被
Python 核心所定義的，但在這裡僅解釋最核心的語意部分。

整個函式庫中包含了許多模組，有許多方法可以從函式庫中取用這些模組。有些模
組是以 C 語言撰寫並建置於 Python 編譯器之中，其他的是由 Python 撰寫並以
源碼的方式 (source form) 引入。有些模組提供的功能是專屬於 Python 的，像
是把 stack trace 印出來；有些則是針對特定作業系統，去試著存取特定硬體；
還有些提供對特定應用的功能與操作介面，像是 World Wide Web。模組的使用情
況會因機器與 Python 的版本而不同，部分模組是開放所有版本以及 Port 的
Python 來使用的，但有些會因系統支援或需求在某些版本或系統下無法使用，甚
至有些僅限在特定的設定環境下才能使用。

這個手冊會「深入淺出」地介紹 Python 函式庫。它會先介紹一些內建函式、資料
型態、和一些例外處理，再來一章章的主題式介紹相關模組。

這代表如果你從這個手冊的最開始讀起，並在感到無聊時跳到下一個章節，你仍然
可以得到一個對 Python 函式庫所支援的模組與其合理應用的概觀。當然，你'沒
有必要'像是在讀一本小說一樣讀這本手冊——你可以快速瀏覽目錄（在手冊的最前
頭）、或是你可以利用最後面的索引來查詢特定的函式或模組。最後，如果你享受
閱讀一些隨機的主題，你可以選擇一個隨機的數字並開始閱讀（見 *note random:
a6. 模組) 。不管你想要以什麼順序來閱讀這個手冊，*note 內建函式: 11f5.會
是一個很好的入門，因為手冊中其他章節都預設你已經對這個章節有一定的熟悉程
度。

讓我們開始吧！

* Menu:

* 可用性之註釋::


File: python.info,  Node: 可用性之註釋,  Up: 簡介<6>

5.1.1 可用性之註釋
------------------

   * 如果出現「適用：Unix」註釋，則代表該函式普遍存在於 Unix 系統中，但
     這並不保證其存在於某特定作業系統。

   * If not separately noted, all functions that claim "Availability:
     Unix" are supported on macOS and iOS, both of which build on a Unix
     core.

   * If an availability note contains both a minimum Kernel version and
     a minimum libc version, then both conditions must hold.  For
     example a feature with note 'Availability: Linux >= 3.17 with glibc
     >= 2.27' requires both Linux 3.17 or newer and glibc 2.27 or newer.

* Menu:

* WebAssembly 平台::
* iOS::


File: python.info,  Node: WebAssembly 平台,  Next: iOS,  Up: 可用性之註釋

5.1.1.1 WebAssembly 平台
........................

The WebAssembly(1) platforms ‘wasm32-emscripten’ (Emscripten(2)) and
‘wasm32-wasi’ (WASI(3)) provide a subset of POSIX APIs.  WebAssembly
runtimes and browsers are sandboxed and have limited access to the host
and external resources.  Any Python standard library module that uses
processes, threading, networking, signals, or other forms of
inter-process communication (IPC), is either not available or may not
work as on other Unix-like systems.  File I/O, file system, and Unix
permission-related functions are restricted, too.  Emscripten does not
permit blocking I/O. Other blocking operations like *note sleep(): 642.
block the browser event loop.

The properties and behavior of Python on WebAssembly platforms depend on
the Emscripten(4)-SDK or WASI(5)-SDK version, WASM runtimes (browser,
NodeJS, wasmtime(6)), and Python build time flags.  WebAssembly,
Emscripten, and WASI are evolving standards; some features like
networking may be supported in the future.

For Python in the browser, users should consider Pyodide(7) or
PyScript(8).  PyScript is built on top of Pyodide, which itself is built
on top of CPython and Emscripten.  Pyodide provides access to browsers'
JavaScript and DOM APIs as well as limited networking capabilities with
JavaScript's ‘XMLHttpRequest’ and ‘Fetch’ APIs.

   * Process-related APIs are not available or always fail with an
     error.  That includes APIs that spawn new processes (*note fork():
     17b, *note execve(): 1091.), wait for processes (*note waitpid():
     d40.), send signals (*note kill(): 12f4.), or otherwise interact
     with processes.  The *note subprocess: c1. is importable but does
     not work.

   * The *note socket: b8. module is available, but is limited and
     behaves differently from other platforms.  On Emscripten, sockets
     are always non-blocking and require additional JavaScript code and
     helpers on the server to proxy TCP through WebSockets; see
     Emscripten Networking(9) for more information.  WASI snapshot
     preview 1 only permits sockets from an existing file descriptor.

   * Some functions are stubs that either don't do anything and always
     return hardcoded values.

   * Functions related to file descriptors, file permissions, file
     ownership, and links are limited and don't support some operations.
     For example, WASI does not permit symlinks with absolute file
     names.

   ---------- Footnotes ----------

   (1) https://webassembly.org/

   (2) https://emscripten.org/

   (3) https://wasi.dev/

   (4) https://emscripten.org/

   (5) https://wasi.dev/

   (6) https://wasmtime.dev/

   (7) https://pyodide.org/

   (8) https://pyscript.net/

   (9) https://emscripten.org/docs/porting/networking.html


File: python.info,  Node: iOS,  Prev: WebAssembly 平台,  Up: 可用性之註釋

5.1.1.2 iOS
...........

iOS is, in most respects, a POSIX operating system.  File I/O, socket
handling, and threading all behave as they would on any POSIX operating
system.  However, there are several major differences between iOS and
other POSIX systems.

   * iOS can only use Python in "embedded" mode.  There is no Python
     REPL, and no ability to execute binaries that are part of the
     normal Python developer experience, such as ‘pip’.  To add Python
     code to your iOS app, you must use the *note Python embedding API:
     1d4f. to add a Python interpreter to an iOS app created with Xcode.
     See the *note iOS usage guide: 1d4d. for more details.

   * An iOS app cannot use any form of subprocessing, background
     processing, or inter-process communication.  If an iOS app attempts
     to create a subprocess, the process creating the subprocess will
     either lock up, or crash.  An iOS app has no visibility of other
     applications that are running, nor any ability to communicate with
     other running applications, outside of the iOS-specific APIs that
     exist for this purpose.

   * iOS apps have limited access to modify system resources (such as
     the system clock).  These resources will often be 'readable', but
     attempts to modify those resources will usually fail.

   * iOS apps have a limited concept of console input and output.
     ‘stdout’ and ‘stderr’ 'exist', and content written to ‘stdout’ and
     ‘stderr’ will be visible in logs when running in Xcode, but this
     content 'won't' be recorded in the system log.  If a user who has
     installed your app provides their app logs as a diagnostic aid,
     they will not include any detail written to ‘stdout’ or ‘stderr’.

     iOS apps have no concept of ‘stdin’ at all.  While iOS apps can
     have a keyboard, this is a software feature, not something that is
     attached to ‘stdin’.

     As a result, Python library that involve console manipulation (such
     as *note curses: 23. and *note readline: a8.) are not available on
     iOS.


File: python.info,  Node: 內建函式,  Next: 內建常數,  Prev: 簡介<6>,  Up: Python 標準函式庫 Standard Library

5.2 內建函式
============

Python 直譯器有內建多個可隨時使用的函式和型別。以下按照英文字母排序列出
。

內建函式

--------------------------------------------------------------------------------------------------------------------
                                                                                      
     'A'                           'E'                         'L'                         'R'
     *note abs(): 1ba8.            *note enumerate(): 13ea.     *note len(): 5d4.          *note range(): 2030.
     *note aiter(): 779.           *note eval(): 163.          *note list(): 202e.         *note repr(): 7a1.
     *note all(): 138f.            *note exec(): 162.          *note locals(): 127.        *note reversed(): 80a.
     *note anext(): 77a.                                                                   *note round(): 126d.
     *note any(): 138e.            'F'                         'M'                         
     *note ascii(): 1354.          *note filter(): 809.        *note map(): 808.           'S'
                                   *note float(): 2c8.         *note max(): ead.           *note set(): 2031.
     'B'                           *note format(): 5c3.        *note memoryview(): 202f.     *note setattr(): 2032.
     *note bin(): 123f.            *note frozenset(): 202d.     *note min(): eac.          *note slice(): 410.
     *note bool(): 40e.                                                                    *note sorted(): b75.
     *note breakpoint(): 219.      'G'                         'N'                         *note staticmethod(): 358.
     *note bytearray(): 19c0.      *note getattr(): b78.       *note next(): 77c.          *note str(): 2033.
     *note bytes(): 19bf.          *note globals(): 176a.                                  *note sum(): 411.
                                                               'O'                         *note super(): 483.
     'C'                           'H'                         *note object(): a2f.        
     *note callable(): 115e.       *note hasattr(): 479.       *note oct(): 1261.          'T'
     *note chr(): 1568.            *note hash(): 58f.          *note open(): 4c0.          *note tuple(): 2034.
     *note classmethod(): 14a.     *note help(): 87c.          *note ord(): 1de1.          *note type(): cef.
     *note compile(): 178.         *note hex(): 1262.                                      
     *note complex(): 2c9.                                     'P'                         'V'
                                   'I'                         *note pow(): 976.           *note vars(): 1948.
     'D'                           *note id(): 1390.           *note print(): f18.         
     *note delattr(): 202b.        *note input(): 126b.        *note property(): 180.      'Z'
     *note dict(): 202c.           *note int(): 23c.                                       *note zip(): 774.
     *note dir(): 5d8.             *note isinstance(): 3e8.                                
     *note divmod(): 945.          *note issubclass(): 765.                                '_'
                                   *note iter(): 77b.                                      *note __import__(): 879.
                                                                                      

 -- 函式: abs (x)

     回傳一個數的絕對值，引數可以是整數、浮點數或有實現 *note __abs__():
     1e8d. 的物件。如果引數是一個複數，回傳它的純量（大小）。

 -- 函式: aiter (async_iterable)

     回傳 *note 非同步疊代器: 191. 做為 *note 非同步可疊代物件: d1e.。相
     當於呼叫 x.__aiter__()。

     注意：與 *note iter(): 77b. 不同，*note aiter(): 779. 沒有兩個引數
     的變體。

     在 3.10 版被加入.

 -- 函式: all (iterable)

     如果 'iterable' 的所有元素皆為真（或 iterable 為空）則回傳 ‘True’。
     等價於：

          def all(iterable):
              for element in iterable:
                  if not element:
                      return False
              return True

 -- 函式: awaitable anext (async_iterator)

 -- 函式: awaitable anext (async_iterator, default)

     當進入 await 時，從給定的 *note asynchronous iterator: 191. 中回傳
     下一個項目（item），疊代完畢則回傳 'default' 。

     這是內建函式 *note next(): 77c. 的非同步版本，其行為類似於：

     呼叫 'async_iterator' 的 *note __anext__(): 1dfa. 方法，回傳 *note
     awaitable: 193.。等待返回疊代器的下一個值。如果指定 'default'，當疊
     代器結束時會返回該值，否則會引發 *note StopAsyncIteration: 1933. 。

     在 3.10 版被加入.

 -- 函式: any (iterable)

     如果 'iterable' 的任一元素為真，回傳 ‘True’。如果 iterable 是空的，
     則回傳 ‘False’。等價於：

          def any(iterable):
              for element in iterable:
                  if element:
                      return True
              return False

 -- 函式: ascii (object)

     就像函式 *note repr(): 7a1.，回傳一個表示物件的字串，但是 *note
     repr(): 7a1. 回傳的字串中非 ASCII 編碼的字元會被跳脫 (escape)，像是
     ‘\x’、‘\u’ 和 ‘\U’。這個函式生成的字串和 Python 2 的 *note repr():
     7a1. 回傳的結果相似。

 -- 函式: bin (x)

     將一個整數轉變為一個前綴為 "0b" 的二進位制字串。結果是一個有效的
     Python 運算式。如果 'x' 不是 Python 的 *note int: 23c. 物件，那它需
     要定義 *note __index__(): 6c1. method 回傳一個整數。舉例來說：

          >>> bin(3)
          '0b11'
          >>> bin(-10)
          '-0b1010'

     如果不一定需要 "0b" 前綴，還可以使用如下的方法。

          >>> format(14, '#b'), format(14, 'b')
          ('0b1110', '1110')
          >>> f'{14:#b}', f'{14:b}'
          ('0b1110', '1110')

     可參考 *note format(): 5c3. 獲取更多資訊。

 -- 類別: bool (object=False, /)

     Return a Boolean value, i.e.  one of ‘True’ or ‘False’.  The
     argument is converted using the standard *note truth testing
     procedure: 2035.  If the argument is false or omitted, this returns
     ‘False’; otherwise, it returns ‘True’.  The *note bool: 40e. class
     is a subclass of *note int: 23c. (see *note 數值型別 --
     int、float、complex: 1afe.).  It cannot be subclassed further.  Its
     only instances are ‘False’ and ‘True’ (see *note Boolean 型別 -
     bool: 2036.).

     在 3.7 版的變更: 現在為僅限位置參數。

 -- 函式: breakpoint (*args, **kws)

     這個函式將呼叫 *note sys.breakpointhook(): a7d. 函式，並將 ‘args’ 和
     ‘kws’ 傳遞給它。這將有效地讓你在特定的呼叫點進入除錯器。預設情況下
     ，‘sys.breakpointhook()’ 呼叫 *note pdb.set_trace(): 21a. 不須帶任
     何引數。這樣的設計是為了方便使用者，讓他們不需要額外地導入 *note
     pdb: 94. 模組或輸入太多程式就可以進入除錯器。然而，可以將 *note
     sys.breakpointhook(): a7d. 設置為其他函式，並且 *note breakpoint():
     219. 將自動呼叫該函式，讓你進入所選擇的除錯器。如果無法存取 *note
     sys.breakpointhook(): a7d. 這個函式，則此函式將引發 *note
     RuntimeError: 179.。

     預設情況下，*note breakpoint(): 219. 的行為可以透過 *note
     PYTHONBREAKPOINT: a7e. 環境變數來更改。有關使用詳情，請參考 *note
     sys.breakpointhook(): a7d.。

     請注意，如果 *note sys.breakpointhook(): a7d. 被替換了，則無法保證
     此功能。

     引發一個附帶引數 ‘breakpointhook’ 的*note 稽核事件: 17bd.
     ‘builtins.breakpoint’。

     在 3.7 版被加入.

 -- 類別: bytearray (source=b'')

 -- 類別: bytearray (source, encoding)

 -- 類別: bytearray (source, encoding, errors)

     回傳一個新的 bytes 陣列。*note bytearray: 4e3. class 是一個可變的整
     數序列，包含範圍為 0 <= x < 256 的整數。它有可變序列大部分常見的
     method（如在 *note Mutable Sequence Types: 2037. 中所述），同時也有
     *note bytes: 1a5. 型別大部分的 method，參見 *note Bytes and
     Bytearray Operations: 2038.。

     選擇性參數 'source' 可以被用來以不同的方式初始化陣列：

        * 如果是一個 'string'，你必須提供 'encoding' 參數（以及選擇性地
          提供 'errors' ）；*note bytearray(): 4e3. 會使用 *note
          str.encode(): 87a. method 來將 string 轉變成 bytes。

        * 如果是一個 'integer'，陣列則會有該數值的長度，並以 null bytes
          來當作初始值。

        * 如果是一個符合 *note buffer 介面: 367.的物件，該物件的唯讀
          buffer 會被用來初始化 bytes 陣列。

        * 如果是一個 'iterable'，它的元素必須是範圍為 ‘0 <= x < 256’ 的
          整數，並且會被用作陣列的初始值。

     如果沒有引數，則建立長度為 0 的陣列。

     可參考 *note Binary Sequence Types -- bytes, bytearray, memoryview:
     2039. 和 *note Bytearray Objects: 203a.。

 -- 類別: bytes (source=b'')

 -- 類別: bytes (source, encoding)

 -- 類別: bytes (source, encoding, errors)

     回傳一個新的 "bytes" 物件，會是一個元素是範圍為 ‘0 <= x < 256’ 整數
     的不可變序列。*note bytes: 1a5. 是 *note bytearray: 4e3. 的不可變版
     本 — 它的同樣具備不改變物件的 method，也有相同的索引和切片操作。

     因此，建構函式的引數和 *note bytearray(): 4e3. 相同。

     Bytes 物件還可以用文字建立，參見 *note String and Bytes literals:
     1d96.。

     可參考 *note Binary Sequence Types -- bytes, bytearray, memoryview:
     2039.、*note Bytes Objects: 203b. 和 *note Bytes and Bytearray
     Operations: 2038.。

 -- 函式: callable (object)

     如果引數 'object' 是可呼叫的，回傳 *note True: bb4.，否則回傳 *note
     False: adb.。如果回傳 ‘True’，呼叫仍可能會失敗；但如果回傳 ‘False’，
     則呼叫 'object' 肯定會失敗。注意 class 是可呼叫的（呼叫 class 會回
     傳一個新的實例）；如果實例的 class 有定義 *note __call__(): 4fe.
     method，則它是可呼叫的。

     在 3.2 版被加入: 這個函式一開始在 Python 3.0 被移除，但在 Python
     3.2 又被重新加入。

 -- 函式: chr (i)

     回傳代表字元之 Unicode 編碼位置為整數 'i' 的字串。例如，‘chr(97)’ 回
     傳字串 ‘'a'’，而 ‘chr(8364)’ 回傳字串 ‘'€'’。這是 *note ord():
     1de1. 的逆函式。

     引數的有效範圍是 0 到 1,114,111（16 進制表示為 0x10FFFF）。如果 'i'
     超過這個範圍，會引發 *note ValueError: 1e7.。

 -- 函式: @classmethod

     把一個 method 封裝成 class method（類別方法）。

     一個 class method 把自己的 class 作為第一個引數，就像一個實例
     method 把實例自己作為第一個引數。請用以下慣例來宣告 class method：

          class C:
              @classmethod
              def f(cls, arg1, arg2): ...

     ‘@classmethod’ 語法是一個函式 *note decorator: 6d5. — 參見 *note
     函式定義: 1b3a. 中關於函式定義的詳細介紹。

     一個 class method 可以在 class（如 ‘C.f()’）或實例（如 ‘C().f()’）
     上呼叫。實例除了它的 class 資訊，其他都會被忽略。如果一個 class
     method 在 subclass 上呼叫，subclass 會作為第一個引數傳入。

     Class method 和 C++ 與 Java 的 static method 是有區別的。如果你想瞭
     解 static method，請看本節的 *note staticmethod(): 358.。關於 class
     method 的更多資訊，請參考*note 標準型別階層: 1dd6.。

     在 3.9 版的變更: Class methods 現在可以包裝其他*note 描述器: 1e47.，
     例如 *note property(): 180.

     在 3.10 版的變更: Class method 現在繼承了 method 屬性（
     ‘__module__’、‘__name__’、‘__qualname__’、‘__doc__’ 和
     ‘__annotations__’），並擁有一個新的 ‘__wrapped__’ 屬性。

     Deprecated since version 3.11, removed in version 3.13: Class
     methods 不能再包裝其他的*note 描述器: 1e47.，例如 *note property():
     180.。

 -- 函式: compile (source, filename, mode, flags=0, dont_inherit=False,
          optimize=-1)

     將 'source' 編譯成程式碼或 AST 物件。程式碼物件可以被 *note exec():
     162. 或 *note eval(): 163. 執行。'source' 可以是一般的字串、bytes 字
     串、或者 AST 物件。參見 *note ast: 7. module（模組）的說明文件瞭解
     如何使用 AST 物件。

     'filename' 引數必須是程式碼的檔名；如果程式碼不是從檔案中讀取，可以
     傳入一些可辨識的值（經常會使用 ‘'<string>'’ 來替代）。

     'mode' 引數指定了編譯程式碼時必須用的模式。如果 'source' 是一系列的
     陳述式，可以是 ‘'exec'’；如果是單一運算式，可以是 ‘'eval'’；如果是
     單個互動式陳述式，可以是 ‘'single'’（在最後一種情況下，如果運算式執
     行結果不是 ‘None’ 則會被印出來）。

     可選引數 'flags' 和 'dont_inherit' 控制啟用哪個*note 編譯器選項:
     203c.以及允許哪個*note 未來功能: 16f.。如果兩者都不存在（或兩者都為
     零），則會呼叫與 *note compile(): 178. 相同旗標的程式碼來編譯。如果
     給定 'flags' 引數而未給定 'dont_inherit*（或為零）則無論如何都會使
     用由 *flags' 引數所指定的編譯器選項和未來陳述式。如果
     'dont_inherit' 是一個非零整數，則使用 'flags' 引數 －－ 周圍程式碼
     中的旗標（未來功能和編譯器選項）將被忽略。

     編譯器選項和 future 陳述式使用 bits 來表示，可以一起被位元操作 OR 來
     表示複數個選項。需要被具體定義特徵的位元域可以透過 *note
     __future__: 0. module 中 *note _Feature: 203d. 實例中的 *note
     compiler_flag: 203e. 屬性來獲得。*note 編譯器旗標: 203c.可以在
     *note ast: 7. module 中搜尋有 ‘PyCF_’ 前綴的名稱。

     引數 'optimize' 用來指定編譯器的最佳化級別；預設值 ‘-1’ 選擇與直譯
     器的 *note -O: d5b. 選項相同的最佳化級別。其他級別為 ‘0’（沒有最佳
     化；‘__debug__’ 為真值）、‘1’（assert 被刪除，‘__debug__’ 為假值）
     或 ‘2’（說明字串 (docstring) 也被刪除）。

     如果編譯的原始碼無效，此函式會引發 *note SyntaxError: 173.，如果原
     始碼包含 null bytes，則會引發 *note ValueError: 1e7.。

     如果你想解析 Python 程式碼為 AST 運算式，請參閱 *note ast.parse():
     18e.。

     引發一個附帶引數 ‘source’、‘filename’ 的*note 稽核事件: 17bd.
     ‘compile’。此事件也可能由隱式編譯 (implicit compilation) 所引發。

          備註: 在 ‘'single'’ 或 ‘'eval'’ 模式編譯多行程式碼時，輸入必須
          以至少一個換行符結尾。這使 *note code: 13. module 更容易檢測陳
          述式的完整性。

          警告: 如果編譯足夠大或者足夠複雜的字串成 AST 物件時，Python 直
          譯器會因為 Python AST 編譯器的 stack 深度限制而崩潰。

     在 3.2 版的變更: 允許使用 Windows 和 Mac 的換行符號。此外，在
     ‘'exec'’ 模式不需要以換行符號結尾。增加了 'optimize' 參數。

     在 3.5 版的變更: 在之前的版本，'source' 中包含 null bytes 會引發
     *note TypeError: 4dd.。

     在 3.8 版被加入: ‘ast.PyCF_ALLOW_TOP_LEVEL_AWAIT’ 現在可以傳遞旗標
     以啟用對頂層 ‘await’、‘async for’ 和 ‘async with’ 的支援。

 -- 類別: complex (number=0, /)

 -- 類別: complex (string, /)

 -- 類別: complex (real=0, imag=0)

     Convert a single string or number to a complex number, or create a
     complex number from real and imaginary parts.

     例如：

          >>> complex('+1.23')
          (1.23+0j)
          >>> complex('-4.5j')
          -4.5j
          >>> complex('-1.23+4.5j')
          (-1.23+4.5j)
          >>> complex('\t( -1.23+4.5J )\n')
          (-1.23+4.5j)
          >>> complex('-Infinity+NaNj')
          (-inf+nanj)
          >>> complex(1.23)
          (1.23+0j)
          >>> complex(imag=-4.5)
          -4.5j
          >>> complex(-1.23, 4.5)
          (-1.23+4.5j)

     If the argument is a string, it must contain either a real part (in
     the same format as for *note float(): 2c8.) or an imaginary part
     (in the same format but with a ‘'j'’ or ‘'J'’ suffix), or both real
     and imaginary parts (the sign of the imaginary part is mandatory in
     this case).  The string can optionally be surrounded by whitespaces
     and the round parentheses ‘'('’ and ‘')'’, which are ignored.  The
     string must not contain whitespace between ‘'+'’, ‘'-'’, the ‘'j'’
     or ‘'J'’ suffix, and the decimal number.  For example,
     ‘complex('1+2j')’ is fine, but ‘complex('1 + 2j')’ raises *note
     ValueError: 1e7.  More precisely, the input must conform to the
     *note complexvalue: 203f. production rule in the following grammar,
     after parentheses and leading and trailing whitespace characters
     are removed:

          complexvalue ::= floatvalue |
                           floatvalue ("j" | "J") |
                           floatvalue sign absfloatvalue ("j" | "J")

     If the argument is a number, the constructor serves as a numeric
     conversion like *note int: 23c. and *note float: 2c8.  For a
     general Python object ‘x’, ‘complex(x)’ delegates to
     ‘x.__complex__()’.  If *note __complex__(): 58d. is not defined
     then it falls back to *note __float__(): 970.  If ‘__float__()’ is
     not defined then it falls back to *note __index__(): 6c1.

     If two arguments are provided or keyword arguments are used, each
     argument may be any numeric type (including complex).  If both
     arguments are real numbers, return a complex number with the real
     component 'real' and the imaginary component 'imag'.  If both
     arguments are complex numbers, return a complex number with the
     real component ‘real.real-imag.imag’ and the imaginary component
     ‘real.imag+imag.real’.  If one of arguments is a real number, only
     its real component is used in the above expressions.

     If all arguments are omitted, returns ‘0j’.

     複數型別在 *note 數值型別 -- int、float、complex: 1afe. 中有相關描
     述。

     在 3.6 版的變更: 可以使用底線將程式碼文字中的數字進行分組。

     在 3.8 版的變更: 如果 *note __complex__(): 58d. 和 *note
     __float__(): 970. 未定義，則會回退到 *note __index__(): 6c1.。

 -- 函式: delattr (object, name)

     這是 *note setattr(): 2032. 相關的函式。引數是一個物件和一個字串，
     該字串必須是物件中某個屬性名稱。如果物件允許，該函式將刪除指定的屬
     性。例如 ‘delattr(x, 'foobar')’ 等價於 ‘del x.foobar’。'name' 不必
     是個 Python 識別符 (identifier)（請見 *note setattr(): 2032.）。

 -- 類別: dict (**kwarg)

 -- 類別: dict (mapping, **kwarg)

 -- 類別: dict (iterable, **kwarg)

     建立一個新的 dictionary（字典）。*note dict: 23b. 物件是一個
     dictionary class。參見 *note dict: 23b. 和 *note Mapping Types --
     dict: a69. 來瞭解這個 class。

     其他容器型別，請參見內建的 *note list: 5b6.、*note set: 57d. 和
     *note tuple: 322. class，以及 *note collections: 16. module。

 -- 函式: dir ()

 -- 函式: dir (object)

     如果沒有引數，則回傳當前區域作用域 (local scope) 中的名稱列表。如果
     有引數，它會嘗試回傳該物件的有效屬性列表。

     如果物件有一個名為 *note __dir__(): 1e3c. 的 method，那麼該 method
     將被呼叫，並且必須回傳一個屬性列表。這允許實現自定義 *note
     __getattr__(): 47a. 或 *note __getattribute__(): b79. 函式的物件能
     夠自定義 *note dir(): 5d8. 來報告它們的屬性。

     如果物件不提供 *note __dir__(): 1e3c.，這個函式會嘗試從物件已定義的
     *note __dict__: c04. 屬性和型別物件收集資訊。結果列表並不總是完整的
     ，如果物件有自定義 *note __getattr__(): 47a.，那結果可能不準確。

     預設的 *note dir(): 5d8. 機制對不同型別的物件有不同行為，它會試圖回
     傳最相關而非最完整的資訊：

        * 如果物件是 module 物件，則列表包含 module 的屬性名稱。

        * 如果物件是型別或 class 物件，則列表包含它們的屬性名稱，並且遞
          迴查詢其基礎的所有屬性。

        * 否則，包含物件的屬性名稱列表、它的 class 屬性名稱，並且遞迴查
          詢它的 class 的所有基礎 class 的屬性。

     回傳的列表按字母表排序，例如：

          >>> import struct
          >>> dir()   # show the names in the module namespace
          ['__builtins__', '__name__', 'struct']
          >>> dir(struct)   # show the names in the struct module
          ['Struct', '__all__', '__builtins__', '__cached__', '__doc__', '__file__',
           '__initializing__', '__loader__', '__name__', '__package__',
           '_clearcache', 'calcsize', 'error', 'pack', 'pack_into',
           'unpack', 'unpack_from']
          >>> class Shape:
          ...     def __dir__(self):
          ...         return ['area', 'perimeter', 'location']
          ...
          >>> s = Shape()
          >>> dir(s)
          ['area', 'location', 'perimeter']

          備註: 因為 *note dir(): 5d8. 主要是為了便於在互動式提示字元時
          使用，所以它會試圖回傳人們感興趣的名稱集合，而不是試圖保證結果
          的嚴格性或一致性，它具體的行為也可能在不同版本之間改變。例如，
          當引數是一個 class 時，metaclass 的屬性不包含在結果列表中。

 -- 函式: divmod (a, b)

     它將兩個（非複數）數字作為引數，並在執行整數除法時回傳一對商和餘數
     。對於混合運算元型別，適用二進位算術運算子的規則。對於整數，運算結
     果和 ‘(a // b, a % b)’ 一致。對於浮點數，運算結果是 ‘(q, a % b)’，
     'q' 通常是 ‘math.floor(a / b)’ 但可能會比 1 小。在任何情況下，‘q *
     b + a % b’ 和 'a' 基本相等，如果 ‘a % b’ 非零，則它的符號和 'b' 一
     樣，且 ‘0 <= abs(a % b) < abs(b)’。

 -- 函式: enumerate (iterable, start=0)

     回傳一個列舉 (enumerate) 物件。'iterable' 必須是一個序列、*note
     iterator: 192. 或其他支援疊代的物件。*note enumerate(): 13ea. 回傳
     之 iterator 的 *note __next__(): 1260. method 回傳一個 tuple（元組
     ），裡面包含一個計數值（從 'start' 開始，預設為 0）和透過疊代
     'iterable' 獲得的值。

          >>> seasons = ['Spring', 'Summer', 'Fall', 'Winter']
          >>> list(enumerate(seasons))
          [(0, 'Spring'), (1, 'Summer'), (2, 'Fall'), (3, 'Winter')]
          >>> list(enumerate(seasons, start=1))
          [(1, 'Spring'), (2, 'Summer'), (3, 'Fall'), (4, 'Winter')]

     等價於：

          def enumerate(iterable, start=0):
              n = start
              for elem in iterable:
                  yield n, elem
                  n += 1

 -- 函式: eval (source, /, globals=None, locals=None)


     參數:

        * ‘source’ (*note str: 3f2. | *note code object: 1b6.) - A
          Python expression.

        * ‘globals’ (*note dict: 23b. | ‘None’) - The global namespace
          (default: ‘None’).

        * ‘locals’ (*note mapping: 1154. | ‘None’) - The local namespace
          (default: ‘None’).


     回傳: The result of the evaluated expression.


     引發: Syntax errors are reported as exceptions.

     The 'expression' argument is parsed and evaluated as a Python
     expression (technically speaking, a condition list) using the
     'globals' and 'locals' mappings as global and local namespace.  If
     the 'globals' dictionary is present and does not contain a value
     for the key ‘__builtins__’, a reference to the dictionary of the
     built-in module *note builtins: e. is inserted under that key
     before 'expression' is parsed.  That way you can control what
     builtins are available to the executed code by inserting your own
     ‘__builtins__’ dictionary into 'globals' before passing it to *note
     eval(): 163.  If the 'locals' mapping is omitted it defaults to the
     'globals' dictionary.  If both mappings are omitted, the expression
     is executed with the 'globals' and 'locals' in the environment
     where *note eval(): 163. is called.  Note, 'eval()' will only have
     access to the *note nested scopes: 2041. (non-locals) in the
     enclosing environment if they are already referenced in the scope
     that is calling *note eval(): 163. (e.g.  via a *note nonlocal:
     123e. statement).

     範例：

          >>> x = 1
          >>> eval('x+1')
          2

     這個函式也可以用來執行任意程式碼物件（如被 *note compile(): 178. 建
     立的那些）。這種情況下，傳入的引數是程式碼物件而不是字串。如果編譯
     該物件時的 'mode' 引數是 ‘'exec'’，那麼 *note eval(): 163. 回傳值為
     ‘None’。

     提示：*note exec(): 162. 函式支援動態執行陳述式。*note globals():
     176a. 和 *note locals(): 127. 函式分別回傳當前的全域性和局部性
     dictionary，它們對於將引數傳遞給 *note eval(): 163. 或 *note
     exec(): 162. 可能會方便許多。

     如果給定來源是一個字串，那麼其前後的空格和定位字元會被移除。

     另外可以參閱 *note ast.literal_eval(): bbf.，該函式可以安全執行僅包
     含文字的運算式字串。

     引發一個附帶程式碼物件為引數的*note 稽核事件: 17bd. ‘exec’。也可能
     會引發程式碼編譯事件。

     在 3.13 版的變更: The 'globals' and 'locals' arguments can now be
     passed as keywords.

     在 3.13 版的變更: The semantics of the default 'locals' namespace
     have been adjusted as described for the *note locals(): 127.
     builtin.

 -- 函式: exec (source, /, globals=None, locals=None, *, closure=None)

     This function supports dynamic execution of Python code.  'source'
     must be either a string or a code object.  If it is a string, the
     string is parsed as a suite of Python statements which is then
     executed (unless a syntax error occurs).  (1)  If it is a code
     object, it is simply executed.  In all cases, the code that's
     executed is expected to be valid as file input (see the section
     *note 檔案輸入: 2016. in the Reference Manual).  Be aware that the
     *note nonlocal: 123e, *note yield: 971, and *note return: 972.
     statements may not be used outside of function definitions even
     within the context of code passed to the *note exec(): 162.
     function.  The return value is ‘None’.

     In all cases, if the optional parts are omitted, the code is
     executed in the current scope.  If only 'globals' is provided, it
     must be a dictionary (and not a subclass of dictionary), which will
     be used for both the global and the local variables.  If 'globals'
     and 'locals' are given, they are used for the global and local
     variables, respectively.  If provided, 'locals' can be any mapping
     object.  Remember that at the module level, globals and locals are
     the same dictionary.

          備註: When ‘exec’ gets two separate objects as 'globals' and
          'locals', the code will be executed as if it were embedded in
          a class definition.  This means functions and classes defined
          in the executed code will not be able to access variables
          assigned at the top level (as the "top level" variables are
          treated as class variables in a class definition).

     如果 'globals' dictionary 不包含 ‘__builtins__’ 鍵值，則將為該鍵插
     入對內建 *note builtins: e. module dictionary 的引用。這麼一來，在
     將 ‘__builtins__’ dictionary 傳入 *note exec(): 162. 之前，你可以透
     過將它插入 'globals' 來控制你需要哪些內建函式來執行程式碼。

     'closure' 引數會指定一個閉包 (closure) — 它是一個 cellvar（格變數）
     的 tuple。只有在 'object' 是一個含有自由變數 (free variable) 的程式
     碼物件時，它才有效。Tuple 的長度必須與程式碼物件所引用的自由變數數
     量完全匹配。

     引發一個附帶程式碼物件為引數的*note 稽核事件: 17bd. ‘exec’。也可能
     會引發程式碼編譯事件。

          備註: The built-in functions *note globals(): 176a. and *note
          locals(): 127. return the current global and local namespace,
          respectively, which may be useful to pass around for use as
          the second and third argument to *note exec(): 162.

          備註: The default 'locals' act as described for function *note
          locals(): 127. below.  Pass an explicit 'locals' dictionary if
          you need to see effects of the code on 'locals' after function
          *note exec(): 162. returns.

     在 3.11 版的變更: 增加了 'closure' 參數。

     在 3.13 版的變更: The 'globals' and 'locals' arguments can now be
     passed as keywords.

     在 3.13 版的變更: The semantics of the default 'locals' namespace
     have been adjusted as described for the *note locals(): 127.
     builtin.

 -- 函式: filter (function, iterable)

     用 'iterable' 中函式 'function' 為 True 的那些元素，構建一個新的
     iterator。'iterable' 可以是一個序列、一個支援疊代的容器、或一個
     iterator。如果 'function' 是 ‘None’，則會假設它是一個識別性函式，即
     'iterable' 中所有假值元素會被移除。

     請注意，‘filter(function, iterable)’ 相當於一個生成器運算式，當
     function 不是 ‘None’ 的時候為 ‘(item for item in iterable if
     function(item))’；function 是 ‘None’ 的時候為 ‘(item for item in
     iterable if item)’。

     請參閱 *note itertools.filterfalse(): 2042.，只有 'function' 為
     false 時才選取 'iterable' 中元素的互補函式。

 -- 類別: float (number=0.0, /)

 -- 類別: float (string, /)

     回傳從數字或字串生成的浮點數。

     例如：

          >>> float('+1.23')
          1.23
          >>> float('   -12345\n')
          -12345.0
          >>> float('1e-003')
          0.001
          >>> float('+1E6')
          1000000.0
          >>> float('-Infinity')
          -inf

     如果引數是字串，則它必須是包含十進位制數字的字串，字串前面可以有符
     號，之前也可以有空格。選擇性的符號有 ‘'+'’ 和 ‘'-'’；‘'+'’ 對建立的
     值沒有影響。引數也可以是 NaN（非數字）或正負無窮大的字串。確切地說
     ，除去首尾的空格後，輸入必須遵循以下語法中 *note floatvalue: 2043.
     的生成規則：

          sign          ::= "+" | "-"
          infinity      ::= "Infinity" | "inf"
          nan           ::= "nan"
          digit         ::= <a Unicode decimal digit, i.e. characters in Unicode general category Nd>
          digitpart     ::= digit (["_"] digit)*
          number        ::= [digitpart] "." digitpart | digitpart ["."]
          exponent      ::= ("e" | "E") [sign] digitpart
          floatnumber   ::= number [exponent]
          absfloatvalue ::= floatnumber | infinity | nan
          floatvalue    ::= [sign] absfloatvalue

     字母大小寫不影響，例如，"inf"、"Inf"、"INFINITY"、"iNfINity" 都可以
     表示正無窮大。

     否則，如果引數是整數或浮點數，則回傳具有相同值（在 Python 浮點精度
     範圍內）的浮點數。如果引數在 Python 浮點精度範圍外，則會引發 *note
     OverflowError: 825.。

     對於一般的 Python 物件 ‘x’，‘float(x)’ 會委派給 ‘x.__float__()’。如
     果未定義 *note __float__(): 970. 則會回退到 *note __index__():
     6c1.。

     如果沒有引數，則回傳 ‘0.0’。

     *note 數值型別 -- int、float、complex: 1afe. 描述了浮點數型別。

     在 3.6 版的變更: 可以使用底線將程式碼文字中的數字進行分組。

     在 3.7 版的變更: 現在為僅限位置參數。

     在 3.8 版的變更: 如果 *note __float__(): 970. 未定義，則會回退到
     *note __index__(): 6c1.。

 -- 函式: format (value, format_spec='')

     將 'value' 轉換為 'format_spec' 控制的 "格式化" 表示。'format_spec'
     的解釋取決於 'value' 引數的型別，但是大多數內建型別使用標準格式化語
     法：*note 格式規格 (Format Specification) 迷你語言: 1c8.。

     預設的 'format_spec' 是一個空字串，它通常和呼叫 *note str(value):
     3f2. 的效果相同。

     呼叫 ‘format(value, format_spec)’ 會轉換成
     ‘type(value).__format__(value, format_spec)’，當搜尋 value 的 *note
     __format__(): 5c5. method 時，會忽略實例中的字典。如果搜尋到 *note
     object: a2f. 這個 method 但 'format_spec' 不為空，或是
     'format_spec' 或回傳值不是字串，則會引發 *note TypeError: 4dd.。

     在 3.4 版的變更: 當 'format_spec' 不是空字串時，
     ‘object().__format__(format_spec)’ 會引發 *note TypeError: 4dd.。

 -- 類別: frozenset (iterable=set())

     回傳一個新的 *note frozenset: 57e. 物件，它包含選擇性引數
     'iterable' 中的元素。‘frozenset’ 是一個內建的 class。有關此 class 的
     文件，請參閱 *note frozenset: 57e. 和 *note Set Types -- set,
     frozenset: 204d.。

     請參閱內建的 *note set: 57d.、*note list: 5b6.、*note tuple: 322. 和
     *note dict: 23b. class，以及 *note collections: 16. module 來了解其
     它的容器。

 -- 函式: getattr (object, name)

 -- 函式: getattr (object, name, default)

     回傳 'object' 之具名屬性的值。'name' 必須是字串。如果該字串是物件屬
     性之一的名稱，則回傳該屬性的值。例如，‘getattr(x, 'foobar')’ 等同於
     ‘x.foobar’。如果指定的屬性不存在，且提供了 'default' 值，則回傳其值
     ，否則引發 *note AttributeError: 2f6.。'name' 不必是個 Python 識別
     符 (identifier)（請見 *note setattr(): 2032.）。

          備註: 由於*note 私有名稱改編 (private name mangling): 1bbd. 是
          發生在編譯期，因此你必須手動改編私有屬性（有兩個前導底線的屬性
          ）的名稱，才能使用 *note getattr(): b78. 來取得它。

 -- 函式: globals ()

     回傳代表當前 module 命名空間的 dictionary。對於在函式中的程式碼來說
     ，這在定義函式時設定且不論該函式是在何處呼叫都會保持相同。

 -- 函式: hasattr (object, name)

     該引數是一個物件和一個字串。如果字串是物件屬性之一的名稱，則回傳
     ‘True’，否則回傳 ‘False’。（此功能是透過呼叫 ‘getattr(object,
     name)’ 並檢查是否引發 *note AttributeError: 2f6. 來實作的。）

 -- 函式: hash (object)

     回傳該物件的雜湊值（如果它有的話）。雜湊值是整數。它們在 dictionary
     查詢元素時用來快速比較 dictionary 的鍵。相同大小的數字數值有相同的
     雜湊值（即使它們型別不同，如 1 和 1.0）。

          備註: 請注意，如果物件帶有自訂的 *note __hash__(): a9e. 方法，
          *note hash(): 58f. 將根據運行機器的位元長度來截斷回傳值。

 -- 函式: help ()

 -- 函式: help (request)

     啟動內建的幫助系統（此函式主要以互動式使用）。如果沒有引數，直譯器
     控制台裡會啟動互動式幫助系統。如果引數是一個字串，則會在 module、函
     式、class、method、關鍵字或說明文件主題中搜索該字串，並在控制台上列
     印幫助資訊。如果引數是其他任意物件，則會生成該物件的幫助頁。

     請注意，呼叫 *note help(): 87c. 時，如果斜線 (/) 出現在函式的參數列
     表中，這表示斜線前面的參數是僅限位置 (positional-only) 參數。有關更
     多資訊，請參閱*note 常見問答集中的僅限位置參數條目: 204e.。

     此函式會被 *note site: b5. module 加入到內建命名空間。

     在 3.4 版的變更: 對於 *note pydoc: a3. 和 *note inspect: 72. 的變更
     ，使得可呼叫物件回報的的簽名 (signature) 更加全面和一致。

 -- 函式: hex (x)

     將整數轉換為以 "0x" 為前綴的小寫十六進位制字串。如果 'x' 不是
     Python *note int: 23c. 物件，則必須定義一個 *note __index__(): 6c1.
     method 並且回傳一個整數。舉例來說：

          >>> hex(255)
          '0xff'
          >>> hex(-42)
          '-0x2a'

     如果要將整數轉換為大寫或小寫的十六進位制字串，並可選擇有無 "0x" 前
     綴，則可以使用如下方法：

          >>> '%#x' % 255, '%x' % 255, '%X' % 255
          ('0xff', 'ff', 'FF')
          >>> format(255, '#x'), format(255, 'x'), format(255, 'X')
          ('0xff', 'ff', 'FF')
          >>> f'{255:#x}', f'{255:x}', f'{255:X}'
          ('0xff', 'ff', 'FF')

     可參考 *note format(): 5c3. 獲取更多資訊。

     另請參閱 *note int(): 23c. 將十六進位制字串轉換為以 16 為基數的整數
     。

          備註: 如果要獲取浮點數的十六進位制字串形式，請使用 *note
          float.hex(): 1c15. method。

 -- 函式: id (object)

     回傳物件的 "識別性" 。該值是一個整數，在此物件的生命週期中保證是唯
     一且恆定的。兩個生命期不重疊的物件可能具有相同的 *note id(): 1390.
     值。

     'CPython 實作細節：' 這是該物件在記憶體中的位址。

     引發一個附帶引數 ‘id’ 的*note 稽核事件: 17bd. ‘builtins.id’。

 -- 函式: input ()

 -- 函式: input (prompt)

     如果有提供 'prompt' 引數，則將其寫入標準輸出，末尾不帶換行符。接下
     來，該函式從輸入中讀取一行，將其轉換為字串（去除末尾的換行符）並回
     傳。當讀取到 EOF 時，則引發 *note EOFError: 126c.。例如：

          >>> s = input('--> ')
          --> Monty Python's Flying Circus
          >>> s
          "Monty Python's Flying Circus"

     如果載入了 *note readline: a8. module，*note input(): 126b. 將使用
     它來提供複雜的行編輯和歷史記錄功能。

     引發一個附帶讀取輸入前的引數 ‘prompt’ 的*note 稽核事件: 17bd.
     ‘builtins.input’。

     引發一個附帶成功讀取結果的*note 稽核事件: 17bd.
     ‘builtins.input/result’。

 -- 類別: int (number=0, /)

 -- 類別: int (string, /, base=10)

     Return an integer object constructed from a number or a string, or
     return ‘0’ if no arguments are given.

     例如：

          >>> int(123.45)
          123
          >>> int('123')
          123
          >>> int('   -12_345\n')
          -12345
          >>> int('FACE', 16)
          64206
          >>> int('0xface', 0)
          64206
          >>> int('01110011', base=2)
          115

     如果引數定義了 *note __int__(): 6c0.，則 ‘int(x)’ 回傳
     ‘x.__int__()’。如果引數定義了 *note __index__(): 6c1. 則回傳
     ‘x.__index__()’。如果引數定義了 *note __trunc__(): 6bf. 則回傳
     ‘x.__trunc__()’。對於浮點數，則會向零的方向無條件捨去。

     如果引數不是數字或如果有給定 'base'，則它必須是個字串、*note bytes:
     1a5. 或 *note bytearray: 4e3. 實例，表示基數 (radix) 'base' 中的整
     數。可選地，字串之前可以有 ‘+’ 或 ‘-’（中間沒有空格）、可有個前導的
     零、也可被空格包圍、或在數字間有單一底線。

     一個 n 進制的整數字串，包含各個代表 0 到 n-1 的數字，0–9 可以用任何
     Unicode 十進制數字表示，10–35 可以用 ‘a’ 到 ‘z’（或 ‘A’ 到 ‘Z’）表
     示。預設的 'base' 是 10。允許的進位制有 0、2–36。2、8、16 進位制的
     字串可以在程式碼中用 ‘0b’/‘0B’、‘0o’/‘0O’、‘0x’/‘0X’ 前綴來表示，如
     同程式碼中的整數文字。進位制為 0 的字串將以和*note 程式碼整數字面值
     (integer literal in code): 1db7. 類似的方式來直譯，最後由前綴決定的
     結果會是 2、8、10、16 進制中的一個，所以 ‘int('010', 0)’ 是非法的，
     但 ‘int('010')’ 和 ‘int('010', 8)’ 是有效的。

     整數型別定義請參閱*note 數值型別 -- int、float、complex: 1afe.。

     在 3.4 版的變更: 如果 'base' 不是 *note int: 23c. 的實例，但 'base'
     物件有 *note base.__index__: 6c1. method，則會呼叫該 method 來獲取
     此進位制所需的整數。以前的版本使用 *note base.__int__: 6c0. 而不是
     *note base.__index__: 6c1.。

     在 3.6 版的變更: 可以使用底線將程式碼文字中的數字進行分組。

     在 3.7 版的變更: 第一個參數為僅限位置參數。

     在 3.8 版的變更: 如果未定義 *note __int__(): 6c0. 則會回退到 *note
     __index__(): 6c1.。

     在 3.11 版的變更: 對 *note __trunc__(): 6bf. 的委派已棄用。

     在 3.11 版的變更: *note int: 23c. 的字串輸入和字串表示法可以被限制
     ，以避免阻斷服務攻擊 (denial of service attack)。在字串 'x' 轉換為
     *note int: 23c. 時已超出限制，或是在 *note int: 23c. 轉換為字串時將
     會超出限制時，會引發 *note ValueError: 1e7.。請參閱*note
     整數字串轉換的長度限制: 599.說明文件。

 -- 函式: isinstance (object, classinfo)

     如果 'object' 引數是 'classinfo' 引數的實例，或者是（直接、間接或
     *note virtual: 114e.）subclass 的實例，則回傳 ‘True’。如果 'object'
     不是給定型別的物件，函式始終回傳 ‘False’。如果 'classinfo' 是包含物
     件型別的 tuple（或多個遞迴 tuple）或一個包含多種型別的 *note
     聯合型別 (Union Type): 766.，若 'object' 是其中的任何一個物件的實例
     則回傳 ‘True’。如果 'classinfo' 既不是型別，也不是型別 tuple 或型別
     的遞迴 tuple，那麼會引發 *note TypeError: 4dd. 異常。若是先前檢查已
     經成功，*note TypeError: 4dd. 可能不會再因為不合格的型別而被引發。

     在 3.10 版的變更: 'classinfo' 可以是一個 *note 聯合型別 (Union
     Type): 766.。

 -- 函式: issubclass (class, classinfo)

     如果 'class' 是 'classinfo' 的 subclass（直接、間接或 *note
     virtual: 114e.），則回傳 ‘True’。'classinfo' 可以是 class 物件的
     tuple（或遞迴地其他類似 tuple）或是一個 *note 聯合型別 (Union
     Type): 766.，此時若 'class' 是 'classinfo' 中任一元素的 subclass 時
     則回傳 ‘True’。其他情況，會引發 *note TypeError: 4dd.。

     在 3.10 版的變更: 'classinfo' 可以是一個 *note 聯合型別 (Union
     Type): 766.。

 -- 函式: iter (object)

 -- 函式: iter (object, sentinel)

     回傳一個 *note iterator: 192. 物件。根據是否存在第二個引數，第一個
     引數的意義是非常不同的。如果沒有第二個引數，'object' 必須是支援
     *note iterable: 11bf. 協定（有 *note __iter__(): 1e31. method）的集
     合物件，或必須支援序列協定（有 *note __getitem__(): 266. 方法，且數
     字引數從 ‘0’ 開始）。如果它不支援這些協定，會引發 *note TypeError:
     4dd.。如果有第二個引數 'sentinel'，那麼 'object' 必須是可呼叫的物件
     ，這種情況下生成的 iterator，每次疊代呼叫 *note __next__(): 1260. 時
     會不帶引數地呼叫 'object'；如果回傳的結果是 'sentinel' 則引發 *note
     StopIteration: ba1.，否則回傳呼叫結果。

     另請參閱 *note 疊代器型別: 204f.。

     *note iter(): 77b. 的第二種形式有一個好用的應用，是能夠建立一個區塊
     閱讀器 (block-reader)。例如，從二進位資料庫檔案中讀取固定寬度的區塊
     ，直到檔案的結尾：

          from functools import partial
          with open('mydata.db', 'rb') as f:
              for block in iter(partial(f.read, 64), b''):
                  process_block(block)

 -- 函式: len (s)

     回傳物件的長度（元素個數）。引數可以是序列（如 string、bytes、
     tuple、list 或 range）或集合（如 dictionary、set 或 frozen set）。

     'CPython 實作細節：' 如果物件長度大於 *note sys.maxsize: 115d.，像
     是 *note range(2 ** 100): 8e7.，則 ‘len’ 會引發 *note
     OverflowError: 825.。

 -- 類別: list

 -- 類別: list (iterable)

     除了是函式，*note list: 5b6. 也是可變序列型別，詳情請參閱 *note
     List（串列）: 2050. 和 *note Sequence Types -- list, tuple, range:
     1b4d.。

 -- 函式: locals ()

          Return a mapping object representing the current local symbol
          table, with variable names as the keys, and their currently
          bound references as the values.

          At module scope, as well as when using *note exec(): 162. or
          *note eval(): 163. with a single namespace, this function
          returns the same namespace as *note globals(): 176a.

          At class scope, it returns the namespace that will be passed
          to the metaclass constructor.

          When using ‘exec()’ or ‘eval()’ with separate local and global
          arguments, it returns the local namespace passed in to the
          function call.

          In all of the above cases, each call to ‘locals()’ in a given
          frame of execution will return the 'same' mapping object.
          Changes made through the mapping object returned from
          ‘locals()’ will be visible as assigned, reassigned, or deleted
          local variables, and assigning, reassigning, or deleting local
          variables will immediately affect the contents of the returned
          mapping object.

          In an *note optimized scope: 161. (including functions,
          generators, and coroutines), each call to ‘locals()’ instead
          returns a fresh dictionary containing the current bindings of
          the function's local variables and any nonlocal cell
          references.  In this case, name binding changes made via the
          returned dict are 'not' written back to the corresponding
          local variables or nonlocal cell references, and assigning,
          reassigning, or deleting local variables and nonlocal cell
          references does 'not' affect the contents of previously
          returned dictionaries.

          Calling ‘locals()’ as part of a comprehension in a function,
          generator, or coroutine is equivalent to calling it in the
          containing scope, except that the comprehension's initialised
          iteration variables will be included.  In other scopes, it
          behaves as if the comprehension were running as a nested
          function.

          Calling ‘locals()’ as part of a generator expression is
          equivalent to calling it in a nested generator function.

     在 3.12 版的變更: The behaviour of ‘locals()’ in a comprehension
     has been updated as described in PEP 709(2).

     在 3.13 版的變更: As part of PEP 667(3), the semantics of mutating
     the mapping objects returned from this function are now defined.
     The behavior in *note optimized scopes: 161. is now as described
     above.  Aside from being defined, the behaviour in other scopes
     remains unchanged from previous versions.

 -- 函式: map (function, iterable, *iterables)

     產生一個將 'function' 應用於 'iterable' 中所有元素，並收集回傳結果
     的 iterator。如果傳遞了額外的 'iterables' 引數，則 'function' 必須
     接受相同個數的引數，並使用所有從 iterables 中同時獲取的元素。當有多
     個 iterables 時，最短的 iteratable 耗盡時 iterator 也會結束。如果函
     式的輸入已經被編排為引數的 tuple，請參閱 *note itertools.starmap():
     107d.。

 -- 函式: max (iterable, *, key=None)

 -- 函式: max (iterable, *, default, key=None)

 -- 函式: max (arg1, arg2, *args, key=None)

     回傳 iterable 中最大的元素，或者回傳兩個以上的引數中最大的。

     如果只提供了一個位置引數，它必須是個 *note iterable: 11bf.，
     iterable 中最大的元素會被回傳。如果提供了兩個或以上的位置引數，則回
     傳最大的位置引數。

     這個函式有兩個選擇性的僅限關鍵字引數。'key' 引數能指定單一引數所使
     用的排序函式，如同 *note list.sort(): b76. 的使用方式。'default' 引
     數是當 iterable 為空時回傳的物件。如果 iterable 為空，並且沒有提供
     'default'，則會引發 *note ValueError: 1e7.。

     如果有多個最大元素，則此函式將回傳第一個找到的。這和其他穩定排序工
     具如 ‘sorted(iterable, key=keyfunc, reverse=True)[0]’ 和
     ‘heapq.nlargest(1, iterable, key=keyfunc)’ 一致。

     在 3.4 版的變更: 新增 'default' 僅限關鍵字參數。

     在 3.8 版的變更: 'key' 可以為 ‘None’。

 -- 類別: memoryview (object)

     回傳由給定的引數所建立之「memory view（記憶體檢視）」物件。有關詳細
     資訊，請參閱*note Memory Views: 2051.。

 -- 函式: min (iterable, *, key=None)

 -- 函式: min (iterable, *, default, key=None)

 -- 函式: min (arg1, arg2, *args, key=None)

     回傳 iterable 中最小的元素，或者回傳兩個以上的引數中最小的。

     如果只提供了一個位置引數，它必須是 *note iterable: 11bf.，iterable
     中最小的元素會被回傳。如果提供了兩個以上的位置引數，則回傳最小的位
     置引數。

     這個函式有兩個選擇性的僅限關鍵字引數。'key' 引數能指定單一引數所使
     用的排序函式，如同 *note list.sort(): b76. 的使用方式。'default' 引
     數是當 iterable 為空時回傳的物件。如果 iterable 為空，並且沒有提供
     'default'，則會引發 *note ValueError: 1e7.。

     如果有多個最小元素，則此函式將回傳第一個找到的。這和其他穩定排序工
     具如 ‘sorted(iterable, key=keyfunc)[0]’ 和 ‘heapq.nsmallest(1,
     iterable, key=keyfunc)’ 一致。

     在 3.4 版的變更: 新增 'default' 僅限關鍵字參數。

     在 3.8 版的變更: 'key' 可以為 ‘None’。

 -- 函式: next (iterator)

 -- 函式: next (iterator, default)

     透過呼叫 *note iterator: 192. 的 *note __next__(): 1260. method 獲
     取下一個元素。如果 iterator 耗盡，則回傳給定的預設值 'default'，如
     果沒有預設值則引發 *note StopIteration: ba1.。

 -- 類別: object

     回傳一個沒有特徵的新物件。*note object: a2f. 是所有 class 的基礎，
     它具有所有 Python class 實例的通用 method。這個函式不接受任何引數。

          備註: 由於 *note object: a2f. '沒有' *note __dict__: c04.，因
          此無法將任意屬性賦給 *note object: a2f. class 的實例。

 -- 函式: oct (x)

     將一個整數轉變為一個前綴為 "0o" 的八進位制字串。回傳結果是一個有效
     的 Python 運算式。如果 'x' 不是 Python 的 *note int: 23c. 物件，那
     它需要定義 *note __index__(): 6c1. method 回傳一個整數。舉例來說：

          >>> oct(8)
          '0o10'
          >>> oct(-56)
          '-0o70'

     如果要將整數轉換為八進位制字串，不論是否具備 "0o" 前綴，都可以使用
     下面的方法。

          >>> '%#o' % 10, '%o' % 10
          ('0o12', '12')
          >>> format(10, '#o'), format(10, 'o')
          ('0o12', '12')
          >>> f'{10:#o}', f'{10:o}'
          ('0o12', '12')

     可參考 *note format(): 5c3. 獲取更多資訊。

 -- 函式: open (file, mode='r', buffering=-1, encoding=None,
          errors=None, newline=None, closefd=True, opener=None)

     開啟 'file' 並回傳對應的*note 檔案物件: 115b.。如果該檔案不能開啟，
     則引發 *note OSError: 350.。關於使用此函式的更多方法，請參閱*note
     讀寫檔案: 1b83.。

     'file' 是一個*note 類路徑物件: ac2.，是將被開啟之檔案的路徑（絕對路
     徑或當前工作目錄的相對路徑），或是要被包裝 (wrap) 檔案的整數檔案描
     述器 (file descriptor)。（如果有給定檔案描述器，它會隨著回傳的 I/O
     物件關閉而關閉，除非 'closefd' 被設為 ‘False’。）

     'mode' 是一個選擇性字串，用於指定開啟檔案的模式。預設值是 ‘'r'’，這
     意味著它以文字模式開啟並讀取。其他常見模式有：寫入 ‘'w'’（會捨去已
     經存在的檔案）、唯一性建立 ‘'x'’、追加寫入 ‘'a'’（在'一些' Unix 系
     統上，無論當前的檔案指標在什麼位置，'所有' 寫入都會追加到檔案末尾）
     。在文字模式，如果沒有指定 'encoding'，則根據電腦平臺來決定使用的編
     碼：呼叫 *note locale.getencoding(): 2bc. 來獲取當前的本地編碼。（
     要讀取和寫入原始 bytes，請使用二進位制模式且不要指定 'encoding'。）
     可用的模式有：

     字元          意義
                   
     ----------------------------------------------------------------------------------
                   
     ‘'r'’         讀取（預設）
                   
                   
     ‘'w'’         寫入，會先清除檔案內容
                   
                   
     ‘'x'’         唯一性建立，如果文件已存在則會失敗
                   
                   
     ‘'a'’         寫入，如果檔案存在則在其末端附加內容
                   
                   
     ‘'b'’         二進制模式
                   
                   
     ‘'t'’         文字模式（預設）
                   
                   
     ‘'+'’         更新（讀取並寫入）
                   

     預設的模式是 ‘'r'’（開啟並讀取文字，同 ‘'rt'’）。‘'w+'’ 和 ‘'w+b'’
     模式會開啟並清除檔案。‘'r+'’ 和 ‘'r+b'’ 模式會開啟且保留檔案內容。

     如*note 總覽: 2053.中所述，Python 能區分二進制和文字的 I/O。在二進
     制模式下開啟的檔案（'mode' 引數中含有 ‘'b'’）會將其內容以 *note
     bytes: 1a5. 物件回傳，而不進行任何解碼。在文字模式（預設情況，或當
     'mode' 引數中含有 ‘'t'’），檔案的內容會以 *note str: 3f2. 回傳，其
     位元組已經先被解碼，使用的是取決於平台的編碼系統或是給定的
     'encoding'。

          備註: Python 不會使用底層作業系統對於文字檔案的操作概念；所有
          的處理都是由 Python 獨自完成的，因此能獨立於不同平台。

     'buffering' 是一個選擇性的整數，用於設定緩衝策略。傳入 0 表示關閉緩
     衝（僅在二進制模式下被允許），1 表示行緩衝（line buffering，僅在文
     字模式下可用），而 >1 的整數是指示一個大小固定的區塊緩衝區 (chunk
     buffer)，其位元組的數量。請注意，此類指定緩衝區大小的方式適用於二進
     制緩衝 I/O，但是 ‘TextIOWrapper’（以 ‘mode='r+'’ 開啟的檔案）會有另
     一種緩衝方式。若要在 ‘TextIOWrapper’ 中停用緩衝，可考慮使用 *note
     io.TextIOWrapper.reconfigure(): aed. 的 ‘write_through’ 旗標。若未
     給定 'buffering' 引數，則預設的緩衝策略會運作如下：

        * 二進制檔案會以固定大小的區塊進行緩衝；緩衝區的大小是使用啟發式
          嘗試 (heuristic trying) 來決定底層設備的「區塊大小」，並會回退
          到 *note io.DEFAULT_BUFFER_SIZE: 15c2.。在許多系統上，緩衝區的
          長度通常為 4096 或 8192 個位元組。

        * 「互動式」文字檔（*note isatty(): 1b86. 回傳 ‘True’ 的檔案）會
          使用列緩衝。其他文字檔則使用上述的二進制檔案緩衝策略。

     'encoding' 是用於解碼或編碼檔案的編碼系統之名稱。它只應該在文字模式
     下使用。預設的編碼系統會取決於平台（根據 *note
     locale.getencoding(): 2bc. 回傳的內容），但 Python 支援的任何 *note
     text encoding: 2054.（文字編碼）都是可以使用的。關於支援的編碼系統
     清單，請參閱 *note codecs: 14. module。

     'errors' 是一個選擇性的字串，用於指定要如何處理編碼和解碼的錯誤——它
     不能在二進制模式下使用。有許多不同的標準錯誤處理程式（error
     handler，在*note Error Handlers: 16eb.有列出清單），不過任何已註冊
     到 *note codecs.register_error(): 1404. 的錯誤處理程式名稱也都是有
     效的。標準的名稱包括：

        * ‘'strict'’ 如果發生編碼錯誤，則引發 *note ValueError: 1e7. 例
          外。預設值 ‘None’ 也有相同的效果。

        * ‘'ignore'’ 忽略錯誤。請注意，忽略編碼錯誤可能導致資料遺失。

        * ‘'replace'’ 會在格式不正確的資料位置插入一個替換標誌（像是
          ‘'?'’）。

        * ‘'surrogateescape'’ 會將任何不正確的位元組表示為低位代理碼元
          (low surrogate code unit)，範圍從 U+DC80 到 U+DCFF。在寫入資料
          時，這些代理碼元將會被還原回 ‘surrogateescape’ 錯誤處理程式當
          時所處理的那些相同位元組。這對於處理未知編碼方式的檔案會很好用
          。

        * ‘'xmlcharrefreplace'’ 僅在寫入檔案時可支援。編碼系統不支援的字
          元會被替換為適當的 XML 字元參考 (character reference)
          ‘&#nnn;’。

        * ‘'backslashreplace'’ 會用 Python 的反斜線跳脫序列 (backslashed
          escape sequence) 替換格式不正確的資料。

        * ‘'namereplace'’（也僅在寫入時支援）會將不支援的字元替換為
          ‘\N{...}’ 跳脫序列。

     'newline' 會決定如何剖析資料串流 (stream) 中的換行字元。它可以是
     ‘None’、‘''’、‘'\n'’、‘'\r'’ 或 ‘'\r\n'’。它的運作規則如下：

        * 從資料串流讀取輸入時，如果 'newline' 是 ‘None’，則會啟用通用換
          行模式。輸入資料中的行結尾可以是 ‘'\n'’、‘'\r'’ 或 ‘'\r\n'’，
          這些符號會被轉換為 ‘'\n'’ 之後再回傳給呼叫方。如果是 ‘''’，也
          會啟用通用換行模式，但在回傳給呼叫方時，行尾符號不會被轉換。如
          果它是任何其他有效的值，則輸入資料的行只會由給定的字串做結尾，
          且在回傳給呼叫方時，行尾符號不會被轉換。

        * 將輸出寫入資料串流時，如果 'newline' 是 ‘None’，則被寫入的任何
          ‘'\n'’ 字元都會轉換為系統預設的行分隔符號 *note os.linesep:
          2055.。如果 'newline' 是 ‘''’ 或 ‘'\n'’，則不做任何轉換。如果
          'newline' 是任何其他有效的值，則寫入的任何 ‘'\n'’ 字元都將轉換
          為給定的字串。

     如果 'closefd' 是 ‘False’，且給定的 'file' 引數是一個檔案描述器而不
     是檔名，則當檔案關閉時，底層的檔案描述器會保持開啟狀態。如果有給定
     一個檔名，則 'closefd' 必須是 ‘True’（預設值）；否則將引發錯誤。

     透過以 'opener' 傳遞一個可呼叫物件，就可以自訂開啟函式。然後透過以
     引數 ('file', 'flags') 呼叫 'opener'，就能取得檔案物件的底層檔案描
     述器。'opener' 必須回傳一個開啟的檔案描述器（將 *note os.open: d38.
     作為 'opener' 傳入，在功能上的結果會相當於傳入 ‘None’）。

     新建立的檔案是*note 不可繼承的: e9d.。

     下面的範例使用 *note os.open(): d38. 函式回傳值當作 *note dir_fd:
     1083. 的參數，從給定的目錄中用相對路徑開啟檔案：

          >>> import os
          >>> dir_fd = os.open('somedir', os.O_RDONLY)
          >>> def opener(path, flags):
          ...     return os.open(path, flags, dir_fd=dir_fd)
          ...
          >>> with open('spamspam.txt', 'w', opener=opener) as f:
          ...     print('This will be written to somedir/spamspam.txt', file=f)
          ...
          >>> os.close(dir_fd)  # don't leak a file descriptor

     *note open(): 4c0. 函式回傳的 *note file object: 115b. 型別取決於模
     式。當 *note open(): 4c0. 是在文字模式中開啟檔案時（‘'w'’、‘'r'’、
     ‘'wt'’、‘'rt'’ 等），它會回傳 *note io.TextIOBase: 63b. 的一個
     subclass（具體來說，就是 *note io.TextIOWrapper: 75f.）。使用有緩衝
     的二進制模式開啟檔案時，回傳的 class 則會是 *note
     io.BufferedIOBase: 63a. 的 subclass。確切的 class 各不相同：在讀取
     的二進制模式，它會回傳 *note io.BufferedReader: 11a6.；在寫入和附加
     的二進制模式，它會回傳 *note io.BufferedWriter: 2056.，而在讀／寫模
     式，它會回傳 *note io.BufferedRandom: 2057.。當緩衝被停用時，會回傳
     原始資料串流 *note io.FileIO: 12a4.，它是 *note io.RawIOBase: 106a.
     的一個 subclass。

     另請參閱檔案操作模組，例如 *note fileinput: 51.、*note io: 73.（定
     義了 *note open(): 4c0. 的 module ）、*note os: 91.、*note os.path:
     92.、*note tempfile: c9. 以及 *note shutil: b3.。

     引發一個附帶引數 ‘path’、‘mode’、‘flags’ 的*note 稽核事件: 17bd.
     ‘open’。

     ‘mode’ 和 ‘flags’ 引數可能會被原始的呼叫所修改或推論 (infer)。

     在 3.3 版的變更:

        * 增加了 'opener' 參數。

        * 增加了 ‘'x'’ 模式。

        * 過去引發的 *note IOError: ff5.，現在是 *note OSError: 350. 的
          別名。

        * 如果檔案已存在但使用了唯一性建立模式 (‘'x'’)，現在會引發 *note
          FileExistsError: fc3.。

     在 3.4 版的變更:

        * 檔案在此版本開始是不可繼承的。

     在 3.5 版的變更:

        * 如果系統呼叫被中斷，但訊號處理程式沒有引發例外，此函式現在會重
          試系統呼叫，而不是引發 *note InterruptedError: d2e. 例外（原因
          詳見 PEP 475(4)）。

        * 增加了 ‘'namereplace'’ 錯誤處理程式。

     在 3.6 版的變更:

        * 增加對於實作 *note os.PathLike: bf8. 物件的支援。

        * 在 Windows 上，開啟一個控制臺緩衝區可能會回傳 *note
          io.RawIOBase: 106a. 的 subclass，而不是 *note io.FileIO:
          12a4.。

     在 3.11 版的變更: ‘'U'’ 模式被移除。

 -- 函式: ord (c)

     對於代表單個 Unicode 字元的字串，回傳代表它 Unicode 編碼位置的整數
     。例如 ‘ord('a')’ 回傳整數 ‘97’、‘ord('€')’（歐元符號）回傳 ‘8364’。
     這是 *note chr(): 1568. 的逆函式。

 -- 函式: pow (base, exp, mod=None)

     回傳 'base' 的 'exp' 次方；如果 'mod' 存在，則回傳 'base' 的 'exp'
     次方對 'mod' 取餘數（比直接呼叫 ‘pow(base, exp) % mod’ 計算更高效）
     。兩個引數形式的 ‘pow(exp, exp)’ 等價於次方運算子：‘base**exp’。

     The arguments must have numeric types.  With mixed operand types,
     the coercion rules for binary arithmetic operators apply.  For
     *note int: 23c. operands, the result has the same type as the
     operands (after coercion) unless the second argument is negative;
     in that case, all arguments are converted to float and a float
     result is delivered.  For example, ‘pow(10, 2)’ returns ‘100’, but
     ‘pow(10, -2)’ returns ‘0.01’.  For a negative base of type *note
     int: 23c. or *note float: 2c8. and a non-integral exponent, a
     complex result is delivered.  For example, ‘pow(-9, 0.5)’ returns a
     value close to ‘3j’.  Whereas, for a negative base of type *note
     int: 23c. or *note float: 2c8. with an integral exponent, a float
     result is delivered.  For example, ‘pow(-9, 2.0)’ returns ‘81.0’.

     對於 *note int: 23c. 運算元 'base' 和 'exp'，如果有給定 'mod'，則
     'mod' 也必須是整數型別，且 'mod' 必須不為零。如果有給定 'mod' 且
     'exp' 為負，則 'base' 必須與 'mod' 互質。在這種情況下，會回傳
     ‘pow(inv_base, -exp, mod)’，其中 'inv_base' 是 'base' 對 'mod' 的模
     倒數 (inverse modulo)。

     以下是一個計算 ‘38’ 對 ‘97’ 取模倒數的範例：

          >>> pow(38, -1, mod=97)
          23
          >>> 23 * 38 % 97 == 1
          True

     在 3.8 版的變更: 對於 *note int: 23c. 運算元，現在 ‘pow’ 的三引數形
     式允許第二個引數為負數，也容許模倒數的計算。

     在 3.8 版的變更: 允許關鍵字引數。在此之前只支援位置引數。

 -- 函式: print (*objects, sep=' ', end='\n', file=None, flush=False)

     將 'objects' 列印到文字資料串流 'file'，用 'sep' 分隔並以 'end' 結
     尾。如果有給定 'sep'、'end'、'file' 和 'flush'，那麼它們必須是關鍵
     字引數的形式。

     所有的非關鍵字引數都會像是 *note str(): 3f2. 操作一樣地被轉換為字串
     ，並寫入資料串流，彼此以 'sep' 分隔，並以 'end' 結尾。'sep' 和
     'end' 都必須是字串；它們也可以是 ‘None’，這表示使用預設值。如果沒有
     給定 'objects'，*note print(): f18. 就只會寫入 'end'。

     'file' 引數必須是一個有 ‘write(string)’ method 的物件；如果沒有給定
     或被設為 ‘None’，則將使用 *note sys.stdout: a79.。因為要列印的引數
     會被轉換為文字字串，所以 *note print(): f18. 不能用於二進位模式的檔
     案物件。對於此類物件，請改用 ‘file.write(...)’。

     輸出緩衝通常會由 'file' 決定。但是如果 'flush' 為 true，則資料串流
     會被強制清除。

     在 3.3 版的變更: 增加了 'flush' 關鍵字引數。

 -- 類別: property (fget=None, fset=None, fdel=None, doc=None)

     回傳 property 屬性。

     'fget' 是一個用於取得屬性值的函式，'fset' 是一個用於設定屬性值的函
     式，'fdel' 是一個用於刪除屬性值的函式，而 'doc' 會為該屬性建立一個
     說明字串。

     一個典型的用途是定義一個受管理的屬性 ‘x’：

          class C:
              def __init__(self):
                  self._x = None

              def getx(self):
                  return self._x

              def setx(self, value):
                  self._x = value

              def delx(self):
                  del self._x

              x = property(getx, setx, delx, "I'm the 'x' property.")

     如果 'c' 是 'C' 的一個實例，則 ‘c.x’ 將會呼叫取得器 (getter)，‘c.x
     = value’ 會呼叫設定器 (setter)，而 ‘del c.x’ 會呼叫刪除器
     (deleter)。

     如果有給定 'doc'，它將會是 property 屬性的說明字串。否則，property
     會複製 'fget' 的說明字串（如果它存在的話）。這樣一來，就能夠輕鬆地
     使用 *note property(): 180. 作為*note 裝飾器: 6d5.來建立唯讀屬性：

          class Parrot:
              def __init__(self):
                  self._voltage = 100000

              @property
              def voltage(self):
                  """Get the current voltage."""
                  return self._voltage

     The ‘@property’ decorator turns the ‘voltage()’ method into a
     "getter" for a read-only attribute with the same name, and it sets
     the docstring for 'voltage' to "Get the current voltage."

      -- 函式: @getter

      -- 函式: @setter

      -- 函式: @deleter

          A property object has ‘getter’, ‘setter’, and ‘deleter’
          methods usable as decorators that create a copy of the
          property with the corresponding accessor function set to the
          decorated function.  This is best explained with an example:

               class C:
                   def __init__(self):
                       self._x = None

                   @property
                   def x(self):
                       """I'm the 'x' property."""
                       return self._x

                   @x.setter
                   def x(self, value):
                       self._x = value

                   @x.deleter
                   def x(self):
                       del self._x

          This code is exactly equivalent to the first example.  Be sure
          to give the additional functions the same name as the original
          property (‘x’ in this case.)

          The returned property object also has the attributes ‘fget’,
          ‘fset’, and ‘fdel’ corresponding to the constructor arguments.

     在 3.5 版的變更: The docstrings of property objects are now
     writeable.

      -- 屬性: __name__

          Attribute holding the name of the property.  The name of the
          property can be changed at runtime.

          在 3.13 版被加入.

 -- 類別: range (stop)

 -- 類別: range (start, stop, step=1)

     Rather than being a function, *note range: 8e7. is actually an
     immutable sequence type, as documented in *note Ranges: 2058. and
     *note Sequence Types -- list, tuple, range: 1b4d.

 -- 函式: repr (object)

     Return a string containing a printable representation of an object.
     For many types, this function makes an attempt to return a string
     that would yield an object with the same value when passed to *note
     eval(): 163.; otherwise, the representation is a string enclosed in
     angle brackets that contains the name of the type of the object
     together with additional information often including the name and
     address of the object.  A class can control what this function
     returns for its instances by defining a *note __repr__(): 5c2.
     method.  If *note sys.displayhook(): 148e. is not accessible, this
     function will raise *note RuntimeError: 179.

     This class has a custom representation that can be evaluated:

          class Person:
             def __init__(self, name, age):
                self.name = name
                self.age = age

             def __repr__(self):
                return f"Person('{self.name}', {self.age})"

 -- 函式: reversed (seq)

     Return a reverse *note iterator: 192.  'seq' must be an object
     which has a *note __reversed__(): 1e32. method or supports the
     sequence protocol (the *note __len__(): 1e38. method and the *note
     __getitem__(): 266. method with integer arguments starting at ‘0’).

 -- 函式: round (number, ndigits=None)

     Return 'number' rounded to 'ndigits' precision after the decimal
     point.  If 'ndigits' is omitted or is ‘None’, it returns the
     nearest integer to its input.

     For the built-in types supporting *note round(): 126d, values are
     rounded to the closest multiple of 10 to the power minus 'ndigits';
     if two multiples are equally close, rounding is done toward the
     even choice (so, for example, both ‘round(0.5)’ and ‘round(-0.5)’
     are ‘0’, and ‘round(1.5)’ is ‘2’).  Any integer value is valid for
     'ndigits' (positive, zero, or negative).  The return value is an
     integer if 'ndigits' is omitted or ‘None’.  Otherwise, the return
     value has the same type as 'number'.

     For a general Python object ‘number’, ‘round’ delegates to
     ‘number.__round__’.

          備註: The behavior of *note round(): 126d. for floats can be
          surprising: for example, ‘round(2.675, 2)’ gives ‘2.67’
          instead of the expected ‘2.68’.  This is not a bug: it's a
          result of the fact that most decimal fractions can't be
          represented exactly as a float.  See *note
          浮點數運算：問題與限制: 1c13. for more information.

 -- 類別: set

 -- 類別: set (iterable)

     Return a new *note set: 57d. object, optionally with elements taken
     from 'iterable'.  ‘set’ is a built-in class.  See *note set: 57d.
     and *note Set Types -- set, frozenset: 204d. for documentation
     about this class.

     For other containers see the built-in *note frozenset: 57e, *note
     list: 5b6, *note tuple: 322, and *note dict: 23b. classes, as well
     as the *note collections: 16. module.

 -- 函式: setattr (object, name, value)

     This is the counterpart of *note getattr(): b78.  The arguments are
     an object, a string, and an arbitrary value.  The string may name
     an existing attribute or a new attribute.  The function assigns the
     value to the attribute, provided the object allows it.  For
     example, ‘setattr(x, 'foobar', 123)’ is equivalent to ‘x.foobar =
     123’.

     'name' need not be a Python identifier as defined in *note
     Identifiers and keywords: 1d86. unless the object chooses to
     enforce that, for example in a custom *note __getattribute__():
     b79. or via *note __slots__: 1458.  An attribute whose name is not
     an identifier will not be accessible using the dot notation, but is
     accessible through *note getattr(): b78. etc..

          備註: Since *note private name mangling: 1bbd. happens at
          compilation time, one must manually mangle a private
          attribute's (attributes with two leading underscores) name in
          order to set it with *note setattr(): 2032.

 -- 類別: slice (stop)

 -- 類別: slice (start, stop, step=None)

     Return a *note slice: 2059. object representing the set of indices
     specified by ‘range(start, stop, step)’.  The 'start' and 'step'
     arguments default to ‘None’.

      -- 屬性: start

      -- 屬性: stop

      -- 屬性: step

          Slice objects have read-only data attributes ‘start’, ‘stop’,
          and ‘step’ which merely return the argument values (or their
          default).  They have no other explicit functionality; however,
          they are used by NumPy and other third-party packages.

     Slice objects are also generated when extended indexing syntax is
     used.  For example: ‘a[start:stop:step]’ or ‘a[start:stop, i]’.
     See *note itertools.islice(): af0. for an alternate version that
     returns an *note iterator: 192.

     在 3.12 版的變更: Slice objects are now *note hashable: 5b5.
     (provided *note start: 1e2b, *note stop: 1e2c, and *note step:
     1e2d. are hashable).

 -- 函式: sorted (iterable, /, *, key=None, reverse=False)

     Return a new sorted list from the items in 'iterable'.

     有兩個選擇性引數，只能使用關鍵字引數來指定。

     'key' specifies a function of one argument that is used to extract
     a comparison key from each element in 'iterable' (for example,
     ‘key=str.lower’).  The default value is ‘None’ (compare the
     elements directly).

     'reverse' is a boolean value.  If set to ‘True’, then the list
     elements are sorted as if each comparison were reversed.

     Use *note functools.cmp_to_key(): 1172. to convert an old-style
     'cmp' function to a 'key' function.

     The built-in *note sorted(): b75. function is guaranteed to be
     stable.  A sort is stable if it guarantees not to change the
     relative order of elements that compare equal -- this is helpful
     for sorting in multiple passes (for example, sort by department,
     then by salary grade).

     The sort algorithm uses only ‘<’ comparisons between items.  While
     defining an *note __lt__(): 129e. method will suffice for sorting,
     PEP 8(5) recommends that all six *note rich comparisons: 1f4c. be
     implemented.  This will help avoid bugs when using the same data
     with other ordering tools such as *note max(): ead. that rely on a
     different underlying method.  Implementing all six comparisons also
     helps avoid confusion for mixed type comparisons which can call
     reflected the *note __gt__(): 12a0. method.

     For sorting examples and a brief sorting tutorial, see *note
     排序技法: 205a.

 -- 函式: @staticmethod

     Transform a method into a static method.

     A static method does not receive an implicit first argument.  To
     declare a static method, use this idiom:

          class C:
              @staticmethod
              def f(arg1, arg2, argN): ...

     ‘@staticmethod’ 語法是一個函式 *note decorator: 6d5. - 參見 *note
     函式定義: 1b3a. 中的詳細介紹。

     A static method can be called either on the class (such as ‘C.f()’)
     or on an instance (such as ‘C().f()’).  Moreover, the static method
     *note descriptor: 1e47. is also callable, so it can be used in the
     class definition (such as ‘f()’).

     Static methods in Python are similar to those found in Java or C++.
     Also, see *note classmethod(): 14a. for a variant that is useful
     for creating alternate class constructors.

     Like all decorators, it is also possible to call ‘staticmethod’ as
     a regular function and do something with its result.  This is
     needed in some cases where you need a reference to a function from
     a class body and you want to avoid the automatic transformation to
     instance method.  For these cases, use this idiom:

          def regular_function():
              ...

          class C:
              method = staticmethod(regular_function)

     關於 static method 的更多資訊，請參考 *note 標準型別階層: 1dd6.。

     在 3.10 版的變更: Static methods now inherit the method attributes
     (‘__module__’, ‘__name__’, ‘__qualname__’, ‘__doc__’ and
     ‘__annotations__’), have a new ‘__wrapped__’ attribute, and are now
     callable as regular functions.

 -- 類別: str (object='')

 -- 類別: str (object=b'', encoding='utf-8', errors='strict')

     Return a *note str: 3f2. version of 'object'.  See *note str():
     3f2. for details.

     ‘str’ is the built-in string *note class: 1834.  For general
     information about strings, see *note Text Sequence Type -- str:
     1b03.

 -- 函式: sum (iterable, /, start=0)

     Sums 'start' and the items of an 'iterable' from left to right and
     returns the total.  The 'iterable"s items are normally numbers, and
     the start value is not allowed to be a string.

     For some use cases, there are good alternatives to *note sum():
     411.  The preferred, fast way to concatenate a sequence of strings
     is by calling ‘''.join(sequence)’.  To add floating-point values
     with extended precision, see *note math.fsum(): 1342.  To
     concatenate a series of iterables, consider using *note
     itertools.chain(): 205b.

     在 3.8 版的變更: 'start' 參數可被指定為關鍵字引數。

     在 3.12 版的變更: Summation of floats switched to an algorithm that
     gives higher accuracy and better commutativity on most builds.

 -- 類別: super

 -- 類別: super (type, object_or_type=None)

     Return a proxy object that delegates method calls to a parent or
     sibling class of 'type'.  This is useful for accessing inherited
     methods that have been overridden in a class.

     The 'object_or_type' determines the *note method resolution order:
     205c. to be searched.  The search starts from the class right after
     the 'type'.

     For example, if *note __mro__: 205d. of 'object_or_type' is ‘D -> B
     -> C -> A -> object’ and the value of 'type' is ‘B’, then *note
     super(): 483. searches ‘C -> A -> object’.

     The *note __mro__: 205d. attribute of the class corresponding to
     'object_or_type' lists the method resolution search order used by
     both *note getattr(): b78. and *note super(): 483.  The attribute
     is dynamic and can change whenever the inheritance hierarchy is
     updated.

     If the second argument is omitted, the super object returned is
     unbound.  If the second argument is an object, ‘isinstance(obj,
     type)’ must be true.  If the second argument is a type,
     ‘issubclass(type2, type)’ must be true (this is useful for
     classmethods).

     When called directly within an ordinary method of a class, both
     arguments may be omitted ("zero-argument ‘super()’").  In this
     case, 'type' will be the enclosing class, and 'obj' will be the
     first argument of the immediately enclosing function (typically
     ‘self’).  (This means that zero-argument ‘super()’ will not work as
     expected within nested functions, including generator expressions,
     which implicitly create nested functions.)

     There are two typical use cases for 'super'.  In a class hierarchy
     with single inheritance, 'super' can be used to refer to parent
     classes without naming them explicitly, thus making the code more
     maintainable.  This use closely parallels the use of 'super' in
     other programming languages.

     The second use case is to support cooperative multiple inheritance
     in a dynamic execution environment.  This use case is unique to
     Python and is not found in statically compiled languages or
     languages that only support single inheritance.  This makes it
     possible to implement "diamond diagrams" where multiple base
     classes implement the same method.  Good design dictates that such
     implementations have the same calling signature in every case
     (because the order of calls is determined at runtime, because that
     order adapts to changes in the class hierarchy, and because that
     order can include sibling classes that are unknown prior to
     runtime).

     For both use cases, a typical superclass call looks like this:

          class C(B):
              def method(self, arg):
                  super().method(arg)    # This does the same thing as:
                                         # super(C, self).method(arg)

     In addition to method lookups, *note super(): 483. also works for
     attribute lookups.  One possible use case for this is calling *note
     descriptors: 1e47. in a parent or sibling class.

     Note that *note super(): 483. is implemented as part of the binding
     process for explicit dotted attribute lookups such as
     ‘super().__getitem__(name)’.  It does so by implementing its own
     *note __getattribute__(): b79. method for searching classes in a
     predictable order that supports cooperative multiple inheritance.
     Accordingly, *note super(): 483. is undefined for implicit lookups
     using statements or operators such as ‘super()[name]’.

     Also note that, aside from the zero argument form, *note super():
     483. is not limited to use inside methods.  The two argument form
     specifies the arguments exactly and makes the appropriate
     references.  The zero argument form only works inside a class
     definition, as the compiler fills in the necessary details to
     correctly retrieve the class being defined, as well as accessing
     the current instance for ordinary methods.

     For practical suggestions on how to design cooperative classes
     using *note super(): 483, see guide to using super()(6).

 -- 類別: tuple

 -- 類別: tuple (iterable)

     Rather than being a function, *note tuple: 322. is actually an
     immutable sequence type, as documented in *note Tuples: 1fbe. and
     *note Sequence Types -- list, tuple, range: 1b4d.

 -- 類別: type (object)

 -- 類別: type (name, bases, dict, **kwds)

     With one argument, return the type of an 'object'.  The return
     value is a type object and generally the same object as returned by
     *note object.__class__: 1418.

     The *note isinstance(): 3e8. built-in function is recommended for
     testing the type of an object, because it takes subclasses into
     account.

     With three arguments, return a new type object.  This is
     essentially a dynamic form of the *note class: 126a. statement.
     The 'name' string is the class name and becomes the *note __name__:
     1416. attribute.  The 'bases' tuple contains the base classes and
     becomes the *note __bases__: 1417. attribute; if empty, *note
     object: a2f, the ultimate base of all classes, is added.  The
     'dict' dictionary contains attribute and method definitions for the
     class body; it may be copied or wrapped before becoming the *note
     __dict__: c04. attribute.  The following two statements create
     identical *note type: cef. objects:

          >>> class X:
          ...     a = 1
          ...
          >>> X = type('X', (), dict(a=1))

     另請參閱 *note Type Objects: 205e.。

     Keyword arguments provided to the three argument form are passed to
     the appropriate metaclass machinery (usually *note
     __init_subclass__(): 5d7.) in the same way that keywords in a class
     definition (besides 'metaclass') would.

     另請參閱 *note Customizing class creation: bf2.。

     在 3.6 版的變更: Subclasses of *note type: cef. which don't
     override ‘type.__new__’ may no longer use the one-argument form to
     get the type of an object.

 -- 函式: vars ()

 -- 函式: vars (object)

     Return the *note __dict__: c04. attribute for a module, class,
     instance, or any other object with a *note __dict__: c04.
     attribute.

     Objects such as modules and instances have an updateable *note
     __dict__: c04. attribute; however, other objects may have write
     restrictions on their *note __dict__: c04. attributes (for example,
     classes use a *note types.MappingProxyType: 414. to prevent direct
     dictionary updates).

     Without an argument, *note vars(): 1948. acts like *note locals():
     127.

     A *note TypeError: 4dd. exception is raised if an object is
     specified but it doesn't have a *note __dict__: c04. attribute (for
     example, if its class defines the *note __slots__: 1458.
     attribute).

     在 3.13 版的變更: The result of calling this function without an
     argument has been updated as described for the *note locals(): 127.
     builtin.

 -- 函式: zip (*iterables, strict=False)

     Iterate over several iterables in parallel, producing tuples with
     an item from each one.

     例如：

          >>> for item in zip([1, 2, 3], ['sugar', 'spice', 'everything nice']):
          ...     print(item)
          ...
          (1, 'sugar')
          (2, 'spice')
          (3, 'everything nice')

     More formally: *note zip(): 774. returns an iterator of tuples,
     where the 'i'-th tuple contains the 'i'-th element from each of the
     argument iterables.

     Another way to think of *note zip(): 774. is that it turns rows
     into columns, and columns into rows.  This is similar to
     transposing a matrix(7).

     *note zip(): 774. is lazy: The elements won't be processed until
     the iterable is iterated on, e.g.  by a ‘for’ loop or by wrapping
     in a *note list: 5b6.

     One thing to consider is that the iterables passed to *note zip():
     774. could have different lengths; sometimes by design, and
     sometimes because of a bug in the code that prepared these
     iterables.  Python offers three different approaches to dealing
     with this issue:

        * By default, *note zip(): 774. stops when the shortest iterable
          is exhausted.  It will ignore the remaining items in the
          longer iterables, cutting off the result to the length of the
          shortest iterable:

               >>> list(zip(range(3), ['fee', 'fi', 'fo', 'fum']))
               [(0, 'fee'), (1, 'fi'), (2, 'fo')]

        * *note zip(): 774. is often used in cases where the iterables
          are assumed to be of equal length.  In such cases, it's
          recommended to use the ‘strict=True’ option.  Its output is
          the same as regular *note zip(): 774.:

               >>> list(zip(('a', 'b', 'c'), (1, 2, 3), strict=True))
               [('a', 1), ('b', 2), ('c', 3)]

          Unlike the default behavior, it raises a *note ValueError:
          1e7. if one iterable is exhausted before the others:

               >>> for item in zip(range(3), ['fee', 'fi', 'fo', 'fum'], strict=True):
               ...     print(item)
               ...
               (0, 'fee')
               (1, 'fi')
               (2, 'fo')
               Traceback (most recent call last):
                 ...
               ValueError: zip() argument 2 is longer than argument 1

          Without the ‘strict=True’ argument, any bug that results in
          iterables of different lengths will be silenced, possibly
          manifesting as a hard-to-find bug in another part of the
          program.

        * Shorter iterables can be padded with a constant value to make
          all the iterables have the same length.  This is done by *note
          itertools.zip_longest(): 1235.

     Edge cases: With a single iterable argument, *note zip(): 774.
     returns an iterator of 1-tuples.  With no arguments, it returns an
     empty iterator.

     Tips and tricks:

        * The left-to-right evaluation order of the iterables is
          guaranteed.  This makes possible an idiom for clustering a
          data series into n-length groups using ‘zip(*[iter(s)]*n,
          strict=True)’.  This repeats the 'same' iterator ‘n’ times so
          that each output tuple has the result of ‘n’ calls to the
          iterator.  This has the effect of dividing the input into
          n-length chunks.

        * *note zip(): 774. in conjunction with the ‘*’ operator can be
          used to unzip a list:

               >>> x = [1, 2, 3]
               >>> y = [4, 5, 6]
               >>> list(zip(x, y))
               [(1, 4), (2, 5), (3, 6)]
               >>> x2, y2 = zip(*zip(x, y))
               >>> x == list(x2) and y == list(y2)
               True

     在 3.10 版的變更: 增加了 ‘strict’ 引數。

 -- 函式: __import__ (name, globals=None, locals=None, fromlist=(),
          level=0)

          備註: This is an advanced function that is not needed in
          everyday Python programming, unlike *note
          importlib.import_module(): 4bc.

     This function is invoked by the *note import: 586. statement.  It
     can be replaced (by importing the *note builtins: e. module and
     assigning to ‘builtins.__import__’) in order to change semantics of
     the ‘import’ statement, but doing so is 'strongly' discouraged as
     it is usually simpler to use import hooks (see PEP 302(8)) to
     attain the same goals and does not cause issues with code which
     assumes the default import implementation is in use.  Direct use of
     *note __import__(): 879. is also discouraged in favor of *note
     importlib.import_module(): 4bc.

     The function imports the module 'name', potentially using the given
     'globals' and 'locals' to determine how to interpret the name in a
     package context.  The 'fromlist' gives the names of objects or
     submodules that should be imported from the module given by 'name'.
     The standard implementation does not use its 'locals' argument at
     all and uses its 'globals' only to determine the package context of
     the *note import: 586. statement.

     'level' specifies whether to use absolute or relative imports.  ‘0’
     (the default) means only perform absolute imports.  Positive values
     for 'level' indicate the number of parent directories to search
     relative to the directory of the module calling *note __import__():
     879. (see PEP 328(9) for the details).

     When the 'name' variable is of the form ‘package.module’, normally,
     the top-level package (the name up till the first dot) is returned,
     'not' the module named by 'name'.  However, when a non-empty
     'fromlist' argument is given, the module named by 'name' is
     returned.

     For example, the statement ‘import spam’ results in bytecode
     resembling the following code:

          spam = __import__('spam', globals(), locals(), [], 0)

     The statement ‘import spam.ham’ results in this call:

          spam = __import__('spam.ham', globals(), locals(), [], 0)

     Note how *note __import__(): 879. returns the toplevel module here
     because this is the object that is bound to a name by the *note
     import: 586. statement.

     On the other hand, the statement ‘from spam.ham import eggs,
     sausage as saus’ results in

          _temp = __import__('spam.ham', globals(), locals(), ['eggs', 'sausage'], 0)
          eggs = _temp.eggs
          saus = _temp.sausage

     Here, the ‘spam.ham’ module is returned from *note __import__():
     879.  From this object, the names to import are retrieved and
     assigned to their respective names.

     If you simply want to import a module (potentially within a
     package) by name, use *note importlib.import_module(): 4bc.

     在 3.3 版的變更: Negative values for 'level' are no longer
     supported (which also changes the default value to 0).

     在 3.9 版的變更: When the command line options *note -E: 901. or
     *note -I: 902. are being used, the environment variable *note
     PYTHONCASEOK: 900. is now ignored.

註解
....

   ---------- Footnotes ----------

   (1) 剖析器只接受 Unix 風格的行結束符。如果你從檔案中讀取程式碼，請確
保用換行符號轉換模式轉換 Windows 或 Mac 風格的換行符號。

   (2) https://peps.python.org/pep-0709/

   (3) https://peps.python.org/pep-0667/

   (4) https://peps.python.org/pep-0475/

   (5) https://peps.python.org/pep-0008/

   (6) 
https://rhettinger.wordpress.com/2011/05/26/super-considered-super/

   (7) https://en.wikipedia.org/wiki/Transpose

   (8) https://peps.python.org/pep-0302/

   (9) https://peps.python.org/pep-0328/


File: python.info,  Node: 內建常數,  Next: 內建型別,  Prev: 內建函式,  Up: Python 標準函式庫 Standard Library

5.3 內建常數
============

有一小部分的常數存在於內建命名空間中。他們是：

 -- 資料: False

     在 *note bool: 40e. 型別中的 false 值。對於 ‘False’ 的賦值是不合法
     的，並且會拋出 *note SyntaxError: 173.。

 -- 資料: True

     在 *note bool: 40e. 型別中的 true 值。對於 ‘True’ 的賦值是不合法的
     ，並且會拋出 *note SyntaxError: 173.。

 -- 資料: None

     型別 ‘NoneType’ 的唯一值。‘None’ 經常被使用來表達缺少值，例如未傳送
     預設的引數至函式時，相對應參數即會被賦予 ‘None’。對於 ‘None’ 的賦值
     是不合法的，並且會拋出 *note SyntaxError: 173.。‘None’ 是型別 *note
     NoneType: 7f6. 的唯一實例。

 -- 資料: NotImplemented

     會被二元特殊方法 (binary special methods)（如：*note __eq__():
     a9d.、*note __lt__(): 129e.、*note __add__(): 1e62.、*note
     __rsub__(): 1e75. 等）所回傳的特殊值，代表著該運算沒有針對其他型別
     的實作。同理也可以被原地二元特殊方法 (in-place binary special
     methods) （如：*note __imul__(): 1e67.、*note __iand__(): 1e87. 等
     ）回傳。它不應該被作為 boolean（布林）來解讀。‘NotImplemented’ 是型
     別 *note types.NotImplementedType: 7f7. 的唯一實例。

          備註: 當一個二元 (binary) 或原地 (in-place) 方法回傳
          ‘NotImplemented’，直譯器會嘗試反映該操作到其他型別（或是其他後
          援 (fallback)，取決於是哪種運算子）。如果所有的常識都回傳
          ‘NotImplemented’，直譯器會拋出適當的例外。不正確的回傳
          ‘NotImplemented’ 會造成誤導的錯誤訊息或是 ‘NotImplemented’ 值
          被傳回到 Python 程式碼中。

          請參見 *note 實作算術操作: 1dd9. 以找到更多範例。

          備註: ‘NotImplementedError’ 與 ‘NotImplemented’ 並不一樣且不可
          互換。即使它們有相似的名稱與用途。欲知更多如何使用它們的細節，
          請參見 *note NotImplementedError: 20d.。

     在 3.9 版的變更: 在 boolean（布林）上下文中解讀 ‘NotImplemented’ 已
     經被棄用。雖然目前會被解讀成 true，但會發出一個 *note
     DeprecationWarning: 18b.。在未來版本的 Python 將會拋出 *note
     TypeError: 4dd.。

 -- 資料: Ellipsis

     與刪節號 "‘...’" 字面相同。為一特殊值，大多用於結合使用者定義資料型
     別的延伸切片語法 (extended slicing syntax)。‘Ellipsis’ 是型別 *note
     types.EllipsisType: 7f5. 的唯一實例。

 -- 資料: __debug__

     如果 Python 沒有被以 *note -O: d5b. 選項啟動，則此常數為 true。請參
     見 *note assert: 90c. 陳述式。

     備註: *note None: 61b.，*note False: adb.，*note True: bb4.，以及
     *note __debug__: 77e. 都是不能被重新賦值的（任何對它們的賦值，即使
     是屬性的名稱，也會拋出 *note SyntaxError: 173.）。因此，它們可以被
     視為”真正的”常數。

* Menu:

* 由 site module（模組）所添增的常數::


File: python.info,  Node: 由 site module（模組）所添增的常數,  Up: 內建常數

5.3.1 由 ‘site’ module（模組）所添增的常數
------------------------------------------

*note site: b5. module（模組）（在啟動期間自動 import ，除非有給予 *note
-S: 1140. 指令行選項）會添增一些常數到內建命名空間 (built-in namespace)
中。它們在互動式直譯器中是很有幫助的，但不應該在程式 (programs) 中被使用
。

 -- 資料: quit (code=None)
 -- 資料: exit (code=None)

     當印出物件時，會印出一個訊息： "Use quit() or Ctrl-D (i.e.  EOF) to
     exit" 。當被呼叫時，則會拋出 *note SystemExit: ce7. 並帶有指定的返
     回碼（exit code）。

 -- 資料: help

     當印出此物件時，會印出訊息 "Type help() for interactive help, or
     help(object) for help about object."，並在呼叫時按所述的方式操作
     *note elsewhere: 87c.。

 -- 資料: copyright
 -- 資料: credits

     當印出或是呼叫此物件時，分別會印出版權與致謝的文字。

 -- 資料: license

     當印出此物件時，會印出訊息 "Type license() to see the full license
     text"，並在呼叫時以分頁形式印出完整的許可證文字（一次一整個畫面）。


File: python.info,  Node: 內建型別,  Next: 內建的例外,  Prev: 內建常數,  Up: Python 標準函式庫 Standard Library

5.4 內建型別
============

以下章節描述了直譯器中内建的標準型別。

主要內建型別為數字、序列、映射、class（類別）、實例和例外。

有些集合類別是 mutable（可變的）。那些用於原地 (in-place) 加入、移除或重
新排列其成員且不回傳特定項的 method（方法），也只會回傳 ‘None’ 而非集合
實例自己。

某些操作已被多種物件型別支援；特別是實務上所有物件都已經可以做相等性比較
、真值檢測及被轉換為字串（使用 *note repr(): 7a1. 函式或稍有差異的 *note
str(): 3f2. 函式），後者為當物件傳入 *note print(): f18. 函式印出時在背
後被呼叫的函式。

* Menu:

* 真值檢測::
* Boolean（布林）運算: Boolean（布林）運算 --- and or not. and, or, not
* 比較運算::
* 數值型別: 數值型別 --- int、float、complex. int、float、complex
* Boolean 型別 - bool::
* 疊代器型別::
* Sequence Types: Sequence Types --- list tuple range. list, tuple, range
* Text Sequence Type: Text Sequence Type --- str. str
* Binary Sequence Types: Binary Sequence Types --- bytes bytearray memoryview. bytes, bytearray, memoryview
* Set Types: Set Types --- set frozenset. set, frozenset
* Mapping Types: Mapping Types --- dict. dict
* 情境管理器型別::
* 型別註釋的型別: 型別註釋的型別 --- 泛型別名 Generic Alias 、聯合 Union. 泛型別名 (Generic Alias)、聯合 (Union)
* Other Built-in Types::
* 特殊屬性::
* Integer string conversion length limitation::


File: python.info,  Node: 真值檢測,  Next: Boolean（布林）運算 --- and or not,  Up: 內建型別

5.4.1 真值檢測
--------------

任何物件都可以進行檢測以判斷是否為真值，以便在 *note if: 2c4. 或 *note
while: 1b0b. 條件中使用，或是作為如下所述 boolean（布林）運算之運算元所
用。

預設情況下，一個物件會被視為真值，除非它的 class 定義了會回傳 ‘False’ 的
*note __bool__(): 1268. method 或是定義了會回傳零的 *note __len__():
1e38. method。(1) 以下列出了大部分會被視為 false 的內建物件：

   * 定義為 false 之常數：‘None’ 與 ‘False’

   * 任何數值型別的零：‘0’、‘0.0’、‘0j’、‘Decimal(0)’、‘Fraction(0, 1)’

   * 空的序列和集合：‘''’、‘()’、‘[]’、‘{}’、‘set()’、‘range(0)’

除非另有特別說明，產生 boolean 結果的操作或內建函式都會回傳 ‘0’ 或
‘False’ 作為假值、‘1’ 或 ‘True’ 作為真值。（重要例外： boolean 運算 ‘or’
和 ‘and’ 回傳的是其中一個運算元。）

   ---------- Footnotes ----------

   (1) Additional information on these special methods may be found in
the Python Reference Manual (*note Basic customization: 1e35.).


File: python.info,  Node: Boolean（布林）運算 --- and or not,  Next: 比較運算,  Prev: 真值檢測,  Up: 內建型別

5.4.2 Boolean（布林）運算 -- ‘and’, ‘or’, ‘not’
-----------------------------------------------

下方為 Boolean 運算，按優先順序排序：

運算              結果                                  註解
                                                        
--------------------------------------------------------------------
                                                        
‘x or y’          假如 'x' 為真，則 'x'，否則 'y'       (1)
                                                        
                                                        
‘x and y’         假如 'x' 為假，則 'x'，否則 'y'       (2)
                                                        
                                                        
‘not x’           假如 'x' 為假，則 ‘True’，否則        (3)
                  ‘False’                               
                  

註解：

  1. 這是一個短路運算子，所以他只有在第一個引數為假時，才會對第二個引數
     求值。

  2. 這是一個短路運算子，所以他只有在第一個引數為真時，才會對第二個引數
     求值。

  3. ‘not’ 比非 Boolean 運算子有較低的優先權，因此 ‘not a == b’ 可直譯為
     ‘not (a == b)’，而 ‘a == not b’ 會導致語法錯誤。


File: python.info,  Node: 比較運算,  Next: 數值型別 --- int、float、complex,  Prev: Boolean（布林）運算 --- and or not,  Up: 內建型別

5.4.3 比較運算
--------------

在 Python 裡共有 8 種比較運算。他們的優先順序都相同（皆優先於 Boolean 運
算）。比較運算可以任意的串連；例如，‘x < y <= z’ 等同於 ‘x < y and y <=
z’，差異只在於前者的 'y' 只有被求值一次（但在這兩個例子中，當 ‘x < y’ 為
假時，'z' 皆不會被求值）。

這個表格統整所有比較運算：

運算             含義
                 
-----------------------------------------------
                 
‘<’              小於
                 
                 
‘<=’             小於等於
                 
                 
‘>’              大於
                 
                 
‘>=’             大於等於
                 
                 
‘==’             等於
                 
                 
‘!=’             不等於
                 
                 
‘is’             物件識別性
                 
                 
‘is not’         否定的物件識別性
                 

除了不同的數值型別外，不同型別的物件不能進行相等比較。運算子 ‘==’ 總有定
義，但在某些物件型別（例如，class 物件）時，運算子會等同於 *note is:
2c6.。其他運算子 ‘<’、‘<=’、‘>’ 及 ‘>=’ 皆僅在有意義的部分有所定義；例如
，當其中一個引數為複數時，將引發一個 *note TypeError: 4dd. 的例外。

一個 class 的非相同實例通常會比較為不相等，除非 class 有定義 *note
__eq__(): a9d. method。

一個 class 的實例不可以與其他相同 class 的實例或其他物件型別進行排序，除
非 class 定義足夠的 method ，包含 *note __lt__(): 129e.、*note __le__():
129f.、*note __gt__(): 12a0. 及 *note __ge__(): 12a1.（一般來說，使用
*note __lt__(): 129e. 及 *note __eq__(): a9d. 就可以滿足常規意義上的比較
運算子）。

無法自定義 *note is: 2c6. 與 *note is not: 1f53. 運算子的行為；這兩個運
算子也可以運用在任意兩個物件且不會引發例外。

此外，擁有相同的語法優先序的 *note in: 2c5. 及 *note not in: 5d5. 兩種運
算皆被*note 可疊代物件: 11bf.或者有實作 *note __contains__(): 1e33.
method 的型別所支援。


File: python.info,  Node: 數值型別 --- int、float、complex,  Next: Boolean 型別 - bool,  Prev: 比較運算,  Up: 內建型別

5.4.4 數值型別 -- ‘int’、‘float’、‘complex’
-------------------------------------------

數值型別共有三種：'整數'、'浮點數' 及 '複數'。此外，Boolean 為整數中的一
個子型別。整數有無限的精度。浮點數通常使用 C 裡面的 double 實作。關於在
你程式所運作的機器上之浮點數的精度及內部表示法可以在 *note
sys.float_info: 18f0. 進行查找。複數包含實數及虛數的部分，這兩部分各自是
一個浮點數。若要從一個複數 'z' 提取這兩部分，需使用 ‘z.real’ 及
‘z.imag’。（標準函式庫包含額外的數值型別，像是 *note fractions.Fraction:
1c7. 表示有理數，而 *note decimal.Decimal: 27c. 表示可由使用者制定精度的
浮點數。）

數字是由字面數值或內建公式及運算子的結果所產生的。未經修飾的字面數值（含
十六進位、八進位及二進位數值）會 yield 整數。包含小數點或指數符號的字面
數值會 yield 浮點數。在數值後面加上 ‘'j'’ 或是 ‘'J'’ 會 yield 一個虛數（
意即一個實數為 0 的複數）。你也可以將整數與浮點數相加以得到一個有實部與
虛部的複數。

Python 完全支援混和運算：當一個二元運算子的運算元有不同數值型別時，「較
窄」型別的運算元會被拓寬到另一個型別的運算元；在此處，整數窄於浮點數，浮
點數又窄於複數。不同型別的數字間的比較等同於這些數字的精確值進行比較。
(1)

建構函式： *note int(): 23c.、*note float(): 2c8. 及 *note complex():
2c9. 可以用來產生特定型別的數字。

所有數值型別（除複數外）皆支援以下的運算（有關運算的先後順序，詳見 *note
Operator precedence: 1f69.）：

運算                      結果                                  註解          完整文件
                                                                              
-------------------------------------------------------------------------------------------------------
                                                                              
‘x + y’                   'x' 及 'y' 的加總
                          
                                                                              
‘x - y’                   'x' 及 'y' 的相減
                          
                                                                              
‘x * y’                   'x' 及 'y' 的相乘
                          
                                                                              
‘x / y’                   'x' 及 'y' 相除之商
                          
                                                                              
‘x // y’                  'x' 及 'y' 的整數除法                 (1)(2)
                                                                
                                                                              
‘x % y’                   ‘x / y’ 的餘數                        (2)
                                                                
                                                                              
‘-x’                      'x' 的負數
                          
                                                                              
‘+x’                      'x' 不變
                          
                                                                              
‘abs(x)’                  'x' 的絕對值或量 (magnitude)                        *note abs(): 1ba8.
                                                                              
                                                                              
‘int(x)’                  將 'x' 轉為整數                       (3)(6)        *note int(): 23c.
                                                                              
                                                                              
‘float(x)’                將 'x' 轉為浮點數                     (4)(6)        *note float(): 2c8.
                                                                              
                                                                              
‘complex(re, im)’         一個複數，其實部為 're'，虛部為       (6)           *note complex(): 2c9.
                          'im'。'im' 預設為零。                               
                          
                                                                              
‘c.conjugate()’           為複數 'c' 的共軛複數
                          
                                                                              
‘divmod(x, y)’            一對 ‘(x // y, x % y)’                (2)           *note divmod(): 945.
                                                                              
                                                                              
‘pow(x, y)’               'x' 的 'y' 次方                       (5)           *note pow(): 976.
                                                                              
                                                                              
‘x ** y’                  'x' 的 'y' 次方                       (5)
                                                                

註解：

  1. 也被稱為整數除法。對於型別為 *note int: 23c. 的運算元來說，結果之型
     別會是 *note int: 23c.。對於型別為 *note float: 2c8. 的運算元來說，
     結果之型別會是 *note float: 2c8.。一般來說，結果會是一個整數，但其
     型別不一定會是 *note int: 23c.。結果總是會往負無窮大的方向取整數值
     ： ‘1//2’ 為 ‘0’、‘(-1)//2’ 為 ‘-1’、‘1//(-2)’ 為 ‘-1’ 及
     ‘(-1)//(-2)’ 為 ‘0’。

  2. 不可用於複數。在適當情形下，可使用 *note abs(): 1ba8. 轉換為浮點數
     。

  3. 
     從 *note float: 2c8. 轉換為 *note int: 23c. 會導致截斷並排除小數部
     分。詳見 *note math.floor(): 132f. 及 *note math.ceil(): 1330. 以了
     解更多轉換方式。

  4. 浮點數也接受帶有可選的前綴 "+" 及 "-" 的 "nan" 及 "inf" 字串，其分
     別代表非數字（NaN）及正負無窮。

  5. Python 將 ‘pow(0, 0)’ 及 ‘0 ** 0’ 定義為 ‘1’ 這是程式語言的普遍做法
     。

  6. 字面數值接受包含數字 ‘0’ 到 ‘9’ 或任何等效的 Unicode 字元（具有
     ‘Nd’ 屬性的 code points（碼位））。

     請參閱 Unicode 標準(2)以了解具有 ‘Nd’ 屬性的 code points 完整列表。

所有 *note numbers.Real: 2073. 型別（*note int: 23c. 及 *note float:
2c8.）也適用下列運算：

運算                     結果
                         
---------------------------------------------------------------------------
                         
*note math.trunc(x): 1331.'x' 截斷為 *note Integral: 1e92.
                         
                         
*note round(x[, n]): 126d.'x' 進位至小數點後第 'n' 位，使用偶數捨入法。若
                         省略 'n' ，則預設為 0。
                         
                         
*note math.floor(x): 132f.小於等於 'x' 的最大 *note Integral: 1e92.
                         
                         
*note math.ceil(x): 1330.大於等於 'x' 的最小 *note Integral: 1e92.
                         

關於其他數值運算請詳見 *note math: 81. 及 *note cmath: 11. modules（模組
）。

* Menu:

* 整數型別的位元運算::
* 整數型別的附加 methods::
* 浮點數的附加 methods::
* 數值型別的雜湊::

   ---------- Footnotes ----------

   (1) As a consequence, the list ‘[1, 2]’ is considered equal to ‘[1.0,
2.0]’, and similarly for tuples.

   (2) 
https://unicode.org/Public/UNIDATA/extracted/DerivedNumericType.txt


File: python.info,  Node: 整數型別的位元運算,  Next: 整數型別的附加 methods,  Up: 數值型別 --- int、float、complex

5.4.4.1 整數型別的位元運算
..........................

位元運算只對整數有意義。位元運算的計算結果就如同對二的補數執行無窮多個符
號位元。

二元位元運算的優先順序皆低於數字運算，但高於比較運算；一元運算 ‘~’ 與其
他一元數值運算有一致的優先順序（‘+’ 及 ‘-’）。

這個表格列出所有位元運算並以優先順序由先至後排序。

運算             結果                                 註解
                                                      
---------------------------------------------------------------------
                                                      
‘x | y’          'x' 及 'y' 的位元 '或'               (4)
                                                      
                                                      
‘x ^ y’          'x' 及 'y' 的位元 '邏輯互斥或'       (4)
                                                      
                                                      
‘x & y’          'x' 及 'y' 的位元 '與'               (4)
                                                      
                                                      
‘x << n’         'x' 往左移動 'n' 個位元              (1)(2)
                                                      
                                                      
‘x >> n’         'x' 往右移動 'n' 個位元              (1)(3)
                                                      
                                                      
‘~x’             反轉 'x' 的位元
                 

註解：

  1. 負數位移是不被允許並會引發 *note ValueError: 1e7. 的錯誤。

  2. 向左移動 'n' 個位元等同於乘以 ‘pow(2, n)’。

  3. 向右移動 'n' 個位元等同於向下除法除以 ‘pow(2, n)’。

  4. 在有限的二的補數表示法中執行這些計算（一個有效位元寬度為 ‘1 +
     max(x.bit_length(), y.bit_length())’ 或以上）並至少有一個額外的符號
     擴展位元，便足以得到與無窮多個符號位元相同的結果。


File: python.info,  Node: 整數型別的附加 methods,  Next: 浮點數的附加 methods,  Prev: 整數型別的位元運算,  Up: 數值型別 --- int、float、complex

5.4.4.2 整數型別的附加 methods
..............................

整數型別實作了 *note numbers.Integral: 1e92. *note 抽象基底類別: 114e.。
此外，它提供了一些 methods：

 -- 方法: int.bit_length ()

     回傳以二進位表示一個整數所需要的位元數，不包括符號及首位的零：

          >>> n = -37
          >>> bin(n)
          '-0b100101'
          >>> n.bit_length()
          6

     更準確來說，若 ‘x’ 非為零，則 ‘x.bit_length()’ 會得出滿足 ‘2**(k-1)
     <= abs(x) < 2**k’ 的單一正整數 ‘k’。同樣地，當 ‘abs(x)’ 足夠小到能
     正確地取得捨入的對數，則 ‘k = 1 + int(log(abs(x), 2))’。若 ‘x’ 為零
     ，則 ‘x.bit_length()’ 會回傳 ‘0’。

     等同於：

          def bit_length(self):
              s = bin(self)       # binary representation:  bin(-37) --> '-0b100101'
              s = s.lstrip('-0b') # remove leading zeros and minus sign
              return len(s)       # len('100101') --> 6

     在 3.1 版被加入.

 -- 方法: int.bit_count ()

     回傳在絕對值表示的二進位中 1 的個數。這也被稱作母體計數。舉例來說：

          >>> n = 19
          >>> bin(n)
          '0b10011'
          >>> n.bit_count()
          3
          >>> (-n).bit_count()
          3

     等同於：

          def bit_count(self):
              return bin(self).count("1")

     在 3.10 版被加入.

 -- 方法: int.to_bytes (length=1, byteorder='big', *, signed=False)

     回傳表示一個整數的一列位元組。

          >>> (1024).to_bytes(2, byteorder='big')
          b'\x04\x00'
          >>> (1024).to_bytes(10, byteorder='big')
          b'\x00\x00\x00\x00\x00\x00\x00\x00\x04\x00'
          >>> (-1024).to_bytes(10, byteorder='big', signed=True)
          b'\xff\xff\xff\xff\xff\xff\xff\xff\xfc\x00'
          >>> x = 1000
          >>> x.to_bytes((x.bit_length() + 7) // 8, byteorder='little')
          b'\xe8\x03'

     此整數會使用 'length' 位元組表示，並且預設為 1。如果該整數無法用給
     定的位元組數來表示，則會引發 *note OverflowError: 825.。

     'byteorder' 引數決定了用來表示整數的位元組順序並且預設為 ‘"big"’。
     如果 byteorder 是 ‘"big"’，最重要的位元組位於位元組陣列的開頭。如果
     byteorder 是 ‘"little"’，最重要的位元組位於位元組陣列的結尾。

     'signed' 引數決定是否使用二的補數來表示整數。如果 'signed' 是
     ‘False’ 並且給定了一個負整數，則會引發 *note OverflowError: 825.。
     'signed' 的預設值是 ‘False’。

     預設值可以方便地將一個整數轉換為單一位元組物件：

          >>> (65).to_bytes()
          b'A'

     然而，使用預設引數時，不要嘗試轉換大於 255 的值，否則你將會得到一個
     *note OverflowError: 825.。

     等同於：

          def to_bytes(n, length=1, byteorder='big', signed=False):
              if byteorder == 'little':
                  order = range(length)
              elif byteorder == 'big':
                  order = reversed(range(length))
              else:
                  raise ValueError("byteorder must be either 'little' or 'big'")

              return bytes((n >> i*8) & 0xff for i in order)

     在 3.2 版被加入.

     在 3.11 版的變更: 為 ‘length’ 和 ‘byteorder’ 添加了預設引數值。

 -- 方法: classmethod int.from_bytes (bytes, byteorder='big', *,
          signed=False)

     回傳由給定的位元組陣列表示的整數。

          >>> int.from_bytes(b'\x00\x10', byteorder='big')
          16
          >>> int.from_bytes(b'\x00\x10', byteorder='little')
          4096
          >>> int.from_bytes(b'\xfc\x00', byteorder='big', signed=True)
          -1024
          >>> int.from_bytes(b'\xfc\x00', byteorder='big', signed=False)
          64512
          >>> int.from_bytes([255, 0, 0], byteorder='big')
          16711680

     引數 'bytes' 必須是一個*note 類位元組物件: cd4.或是一個產生位元組的
     可疊代物件。

     'byteorder' 引數決定了用來表示整數的位元組順序並且預設為 ‘"big"’。
     如果 'byteorder' 是 ‘"big"’，最重要的位元組位於位元組陣列的開頭。如
     果 'byteorder' 是 ‘"little"’，最重要的位元組位於位元組陣列的結尾。
     若要請求主機系統的本機位元組順序，請使用 *note sys.byteorder: 2078.
     作為位元組順序值。

     'signed' 引數指示是否使用二的補數來表示整數。

     等同於：

          def from_bytes(bytes, byteorder='big', signed=False):
              if byteorder == 'little':
                  little_ordered = list(bytes)
              elif byteorder == 'big':
                  little_ordered = list(reversed(bytes))
              else:
                  raise ValueError("byteorder must be either 'little' or 'big'")

              n = sum(b << i*8 for i, b in enumerate(little_ordered))
              if signed and little_ordered and (little_ordered[-1] & 0x80):
                  n -= 1 << 8*len(little_ordered)

              return n

     在 3.2 版被加入.

     在 3.11 版的變更: 為 ‘byteorder’ 添加了預設引數值。

 -- 方法: int.as_integer_ratio ()

     回傳一對整數，其比率等於原始整數並且有一個正分母。整數（整個數值）
     的整數比率總是整數作為分子，並且 ‘1’ 作為分母。

     在 3.8 版被加入.

 -- 方法: int.is_integer ()

     回傳 ‘True’。為了與 *note float.is_integer(): 2079. 的鴨子型別相容
     而存在。

     在 3.12 版被加入.


File: python.info,  Node: 浮點數的附加 methods,  Next: 數值型別的雜湊,  Prev: 整數型別的附加 methods,  Up: 數值型別 --- int、float、complex

5.4.4.3 浮點數的附加 methods
............................

浮點數型別實作了 *note numbers.Real: 2073. *note 抽象基底類別: 114e.。浮
點數也有下列附加 methods。

 -- 方法: float.as_integer_ratio ()

     回傳一對整數，其比率完全等於原始浮點數。比率是在最低條件下並且有一
     個正分母。在無窮大時引發 *note OverflowError: 825.，在 NaN 時引發
     *note ValueError: 1e7.。

 -- 方法: float.is_integer ()

     如果浮點數實例是有限的並且具有整數值，則回傳 ‘True’，否則回傳
     ‘False’：

          >>> (-2.0).is_integer()
          True
          >>> (3.2).is_integer()
          False

兩個 methods 皆支援十六進位字串之間的轉換。由於 Python 的浮點數內部以二
進位數值儲存，將浮點數轉換為或從 '十進位' 字串通常涉及一個小的四捨五入誤
差。相反地，十六進位字串允許精確表示和指定浮點數。這在除錯和數值工作中可
能會有用。

 -- 方法: float.hex ()

     回傳浮點數的十六進位字串表示。對於有限浮點數，此表示方式總是包含一
     個前導 ‘0x’ 及一個尾部 ‘p’ 和指數。

 -- 方法: classmethod float.fromhex (s)

     Class method 回傳由十六進位字串 's' 表示的浮點數。字串 's' 可能有前
     導及尾部的空白。

請注意 *note float.hex(): 1c15. 是一個實例 method，而 *note
float.fromhex(): 207b. 是一個 class method。

一個十六進位字串的形式如下：

     [sign] ['0x'] integer ['.' fraction] ['p' exponent]

其中可選的 ‘sign’ 可以是 ‘+’ 或 ‘-’，‘integer’ 和 ‘fraction’ 是十六進位
數字的字串，而 ‘exponent’ 是一個十進位整數並且有一個可選的前導符號。大小
寫不重要，並且整數或小數部分至少有一個十六進位數字。這個語法與 C99 標準
的第 6.4.4.2 節指定的語法相似，也與 Java 1.5 以後的語法相似。特別是
*note float.hex(): 1c15. 的輸出可用作 C 或 Java 程式碼中的十六進位浮點數
文字，並且 C 的 ‘%a’ 格式字元或 Java 的 ‘Double.toHexString’ 產生的十六
進位字串可被 *note float.fromhex(): 207b. 接受。

請注意指數是以十進位而非十六進位寫入，並且它給出了乘以係數的 2 的次方。
例如，十六進位字串 ‘0x3.a7p10’ 表示浮點數 ‘(3 + 10./16 + 7./16**2) *
2.0**10’，或 ‘3740.0’：

     >>> float.fromhex('0x3.a7p10')
     3740.0

對 ‘3740.0’ 應用反向轉換會給出一個不同的十六進位字串，它表示相同的數字：

     >>> float.hex(3740.0)
     '0x1.d380000000000p+11'


File: python.info,  Node: 數值型別的雜湊,  Prev: 浮點數的附加 methods,  Up: 數值型別 --- int、float、complex

5.4.4.4 數值型別的雜湊
......................

對於數字 ‘x’ 和 ‘y’，可能是不同型別，當 ‘x == y’ 時，‘hash(x) ==
hash(y)’ 是一個要求（ 詳見 *note __hash__(): a9e. method 的文件以獲得更
多細節）。為了實作的便利性和效率跨越各種數值型別（包括 *note int: 23c.、
*note float: 2c8.、*note decimal.Decimal: 27c. 和 *note
fractions.Fraction: 1c7.）Python 的數值型別的雜湊是基於一個數學函式，它
對於任何有理數都是定義的，因此適用於所有 *note int: 23c. 和 *note
fractions.Fraction: 1c7. 的實例，以及所有有限的 *note float: 2c8. 和
*note decimal.Decimal: 27c. 的實例。基本上，這個函式是由簡化的 modulo（
模數） ‘P’ 給出的一個固定的質數 ‘P’。‘P’ 的值作為 *note sys.hash_info:
fa0. 的 *note modulus: 207e. 屬性提供給 Python。

'CPython 實作細節：' 目前在具有 32 位元 C longs 的機器上所使用的質數是
‘P = 2**31 - 1’，而在具有 64 位元 C longs 的機器上為 ‘P = 2**61 - 1’ 。

以下是詳細的規則：

   - 如果 ‘x = m / n’ 是一個非負的有理數，並且 ‘n’ 不可被 ‘P’ 整除，則將
     ‘hash(x)’ 定義為 ‘m * invmod(n, P) % P’。其中 ‘invmod(n, P)’ 為 ‘n’
     對模數 ‘P’ 的倒數。

   - 如果 ‘x = m / n’ 是一個非負的有理數，並且 ‘n’ 可被 ‘P’ 整除（但 ‘m’
     不行），則 ‘n’ 沒有 inverse modulo（模倒數） ‘P’ ，並且不適用於上述
     規則；在這種情況下，將 ‘hash(x)’ 定義為常數值 ‘sys.hash_info.inf’。

   - 如果 ‘x = m / n’ 是一個負的有理數，則將 ‘hash(x)’ 定義為
     ‘-hash(-x)’。如果結果的雜湊是 ‘-1’，則將其替換為 ‘-2’。

   - 特定值 ‘sys.hash_info.inf’ 和 ‘-sys.hash_info.inf’ （分別）被用作正
     無窮大或負無窮大的雜湊值。

   - 對於一個 *note complex: 2c9. 值 ‘z’，實部和虛部的雜湊值藉由
     ‘hash(z.real) + sys.hash_info.imag * hash(z.imag)’ 的計算進行組合，
     對 ‘2**sys.hash_info.width’ 取模數使其介於
     ‘range(-2**(sys.hash_info.width - 1), 2**(sys.hash_info.width -
     1))’。同樣地，如果結果是 ‘-1’，則將其替換為 ‘-2’。

為了闡明上述規則，這裡有一些 Python 程式碼範例，等同於內建的雜湊，用於計
算有理數、*note float: 2c8. 或 *note complex: 2c9. 的雜湊：

     import sys, math

     def hash_fraction(m, n):
         """Compute the hash of a rational number m / n.

         Assumes m and n are integers, with n positive.
         Equivalent to hash(fractions.Fraction(m, n)).

         """
         P = sys.hash_info.modulus
         # Remove common factors of P.  (Unnecessary if m and n already coprime.)
         while m % P == n % P == 0:
             m, n = m // P, n // P

         if n % P == 0:
             hash_value = sys.hash_info.inf
         else:
             # Fermat's Little Theorem: pow(n, P-1, P) is 1, so
             # pow(n, P-2, P) gives the inverse of n modulo P.
             hash_value = (abs(m) % P) * pow(n, P - 2, P) % P
         if m < 0:
             hash_value = -hash_value
         if hash_value == -1:
             hash_value = -2
         return hash_value

     def hash_float(x):
         """Compute the hash of a float x."""

         if math.isnan(x):
             return object.__hash__(x)
         elif math.isinf(x):
             return sys.hash_info.inf if x > 0 else -sys.hash_info.inf
         else:
             return hash_fraction(*x.as_integer_ratio())

     def hash_complex(z):
         """Compute the hash of a complex number z."""

         hash_value = hash_float(z.real) + sys.hash_info.imag * hash_float(z.imag)
         # do a signed reduction modulo 2**sys.hash_info.width
         M = 2**(sys.hash_info.width - 1)
         hash_value = (hash_value & (M - 1)) - (hash_value & M)
         if hash_value == -1:
             hash_value = -2
         return hash_value


File: python.info,  Node: Boolean 型別 - bool,  Next: 疊代器型別,  Prev: 數值型別 --- int、float、complex,  Up: 內建型別

5.4.5 Boolean 型別 - ‘bool’
---------------------------

Boolean 值代表 truth values（真值）。*note bool: 40e. 型別有兩個常數實例
：‘True’ 和 ‘False’。

內建函式 *note bool(): 40e. 將任何值轉換為 boolean 值，如果該值可以被直
譯為一個 truth value（真值）（見上面的*note 真值檢測: 2035.章節）。

對於邏輯運算，使用 *note boolean 運算子: 206e. ‘and’、‘or’ 和 ‘not’。當
將位元運算子 ‘&’、‘|’、‘^’ 應用於兩個 boolean 值時，它們會回傳一個等同於
邏輯運算 "and"、"or"、"xor" 的 boolean 值。然而，應該優先使用邏輯運算子
‘and’、‘or’ 和 ‘!=’ 而不是 ‘&’、‘|’ 和 ‘^’。

在 3.12 版之後被棄用: 位元反轉運算子 ‘~’ 的使用已被棄用並且將在 Python
3.16 中引發錯誤。

*note bool: 40e. 是 *note int: 23c. 的子類別（見*note 數值型別 --
int、float、complex: 1afe.）。在許多數值情境中，‘False’ 和 ‘True’ 分別像
整數 0 和 1 一樣。然而，不鼓勵依賴這一點；請使用 *note int(): 23c. 進行
顯式轉換。


File: python.info,  Node: 疊代器型別,  Next: Sequence Types --- list tuple range,  Prev: Boolean 型別 - bool,  Up: 內建型別

5.4.6 疊代器型別
----------------

Python 支援對容器的疊代概念。這是實作兩種不同的 methods；這些方法被用於
允許使用者自定義的 classes 以支援疊代。序列則總是支援這些疊代 methods，
在下方有更詳細的描述。

需要為容器物件定義一個 method 來提供*note 可疊代物件: 11bf.支援：

 -- 方法: container.__iter__ ()

     回傳一個*note 疊代器: 192.物件。該物件需要支援下述的疊代器協定。如
     果一個容器支援不同型別的疊代，則可以提供額外的 methods 來專門請求這
     些疊代型別的疊代器。（支援多種形式疊代的物件的一個例子是支援廣度優
     先和深度優先遍歷的樹結構。）此 method 對應 Python/C API 中 Python 物
     件的型別結構的 *note tp_iter: 145c. 插槽。

疊代器物件本身需要支援下列兩個 methods，他們一起形成了 '疊代器協定'：

 -- 方法: iterator.__iter__ ()

     回傳*note 疊代器: 192.物件本身。這是為了允許容器和疊代器都可以與
     *note for: 2c3. 和 *note in: 2c5. 在陳述式中使用。此 method 對應於
     Python/C API 中 Python 物件的型別結構的 *note tp_iter: 145c. 插槽。

 -- 方法: iterator.__next__ ()

     從*note 疊代器: 192.回傳下一個項目。如果沒有更多項目，則引發 *note
     StopIteration: ba1. 例外。此 method 對應於 Python/C API 中Python 物
     件的型別結構的 *note tp_iternext: 145d. 插槽。

Python 定義了幾個疊代器物件來支援對一般和特定序列型別、字典和其他更專門
的形式的疊代。這些特定型別除了實作疊代器協定外並不重要。

一旦疊代器的 *note __next__(): 1260. method 引發 *note StopIteration:
ba1.，則它必須在後續呼叫中繼續這樣做。不遵守此屬性的實作被認為是有問題的
。

* Menu:

* Generator Types::


File: python.info,  Node: Generator Types,  Up: 疊代器型別

5.4.6.1 Generator Types
.......................

Python's *note generator: 1004.s provide a convenient way to implement
the iterator protocol.  If a container object's *note __iter__(): 1bc7.
method is implemented as a generator, it will automatically return an
iterator object (technically, a generator object) supplying the
‘__iter__()’ and *note __next__(): 1bc8. methods.  More information
about generators can be found in *note the documentation for the yield
expression: 1f10.


File: python.info,  Node: Sequence Types --- list tuple range,  Next: Text Sequence Type --- str,  Prev: 疊代器型別,  Up: 內建型別

5.4.7 Sequence Types -- ‘list’, ‘tuple’, ‘range’
------------------------------------------------

There are three basic sequence types: lists, tuples, and range objects.
Additional sequence types tailored for processing of *note binary data:
2039. and *note text strings: 1b03. are described in dedicated sections.

* Menu:

* Common Sequence Operations::
* Immutable Sequence Types::
* Mutable Sequence Types::
* List（串列）: List（串列）<2>.
* Tuples::
* Ranges::


File: python.info,  Node: Common Sequence Operations,  Next: Immutable Sequence Types,  Up: Sequence Types --- list tuple range

5.4.7.1 Common Sequence Operations
..................................

The operations in the following table are supported by most sequence
types, both mutable and immutable.  The *note collections.abc.Sequence:
115c. ABC is provided to make it easier to correctly implement these
operations on custom sequence types.

This table lists the sequence operations sorted in ascending priority.
In the table, 's' and 't' are sequences of the same type, 'n', 'i', 'j'
and 'k' are integers and 'x' is an arbitrary object that meets any type
and value restrictions imposed by 's'.

The ‘in’ and ‘not in’ operations have the same priorities as the
comparison operations.  The ‘+’ (concatenation) and ‘*’ (repetition)
operations have the same priority as the corresponding numeric
operations.  (1)

運算                           結果                                 註解
                                                                    
-----------------------------------------------------------------------------------
                                                                    
‘x in s’                       ‘True’ if an item of 's' is equal    (1)
                               to 'x', else ‘False’                 
                               
                                                                    
‘x not in s’                   ‘False’ if an item of 's' is equal   (1)
                               to 'x', else ‘True’                  
                               
                                                                    
‘s + t’                        the concatenation of 's' and 't'     (6)(7)
                                                                    
                                                                    
‘s * n’ 或 ‘n * s’             equivalent to adding 's' to itself   (2)(7)
                               'n' times                            
                               
                                                                    
‘s[i]’                         'i'th item of 's', origin 0          (3)
                                                                    
                                                                    
‘s[i:j]’                       slice of 's' from 'i' to 'j'         (3)(4)
                                                                    
                                                                    
‘s[i:j:k]’                     slice of 's' from 'i' to 'j' with    (3)(5)
                               step 'k'                             
                               
                                                                    
‘len(s)’                       's' 的長度
                               
                                                                    
‘min(s)’                       's' 中最小的項目
                               
                                                                    
‘max(s)’                       's' 中最大的項目
                               
                                                                    
‘s.index(x[, i[, j]])’         index of the first occurrence of     (8)
                               'x' in 's' (at or after index 'i'    
                               and before index 'j')
                               
                                                                    
‘s.count(x)’                   total number of occurrences of 'x'
                               in 's'
                               

Sequences of the same type also support comparisons.  In particular,
tuples and lists are compared lexicographically by comparing
corresponding elements.  This means that to compare equal, every element
must compare equal and the two sequences must be of the same type and
have the same length.  (For full details see *note Comparisons: 1f4c. in
the language reference.)

Forward and reversed iterators over mutable sequences access values
using an index.  That index will continue to march forward (or backward)
even if the underlying sequence is mutated.  The iterator terminates
only when an *note IndexError: 14a3. or a *note StopIteration: ba1. is
encountered (or when the index drops below zero).

註解：

  1. While the ‘in’ and ‘not in’ operations are used only for simple
     containment testing in the general case, some specialised sequences
     (such as *note str: 3f2, *note bytes: 1a5. and *note bytearray:
     4e3.) also use them for subsequence testing:

          >>> "gg" in "eggs"
          True

  2. Values of 'n' less than ‘0’ are treated as ‘0’ (which yields an
     empty sequence of the same type as 's').  Note that items in the
     sequence 's' are not copied; they are referenced multiple times.
     This often haunts new Python programmers; consider:

          >>> lists = [[]] * 3
          >>> lists
          [[], [], []]
          >>> lists[0].append(3)
          >>> lists
          [[3], [3], [3]]

     What has happened is that ‘[[]]’ is a one-element list containing
     an empty list, so all three elements of ‘[[]] * 3’ are references
     to this single empty list.  Modifying any of the elements of
     ‘lists’ modifies this single list.  You can create a list of
     different lists this way:

          >>> lists = [[] for i in range(3)]
          >>> lists[0].append(3)
          >>> lists[1].append(5)
          >>> lists[2].append(7)
          >>> lists
          [[3], [5], [7]]

     Further explanation is available in the FAQ entry *note How do I
     create a multidimensional list?: 2087.

  3. If 'i' or 'j' is negative, the index is relative to the end of
     sequence 's': ‘len(s) + i’ or ‘len(s) + j’ is substituted.  But
     note that ‘-0’ is still ‘0’.

  4. The slice of 's' from 'i' to 'j' is defined as the sequence of
     items with index 'k' such that ‘i <= k < j’.  If 'i' or 'j' is
     greater than ‘len(s)’, use ‘len(s)’.  If 'i' is omitted or ‘None’,
     use ‘0’.  If 'j' is omitted or ‘None’, use ‘len(s)’.  If 'i' is
     greater than or equal to 'j', the slice is empty.

  5. The slice of 's' from 'i' to 'j' with step 'k' is defined as the
     sequence of items with index ‘x = i + n*k’ such that ‘0 <= n <
     (j-i)/k’.  In other words, the indices are ‘i’, ‘i+k’, ‘i+2*k’,
     ‘i+3*k’ and so on, stopping when 'j' is reached (but never
     including 'j').  When 'k' is positive, 'i' and 'j' are reduced to
     ‘len(s)’ if they are greater.  When 'k' is negative, 'i' and 'j'
     are reduced to ‘len(s) - 1’ if they are greater.  If 'i' or 'j' are
     omitted or ‘None’, they become "end" values (which end depends on
     the sign of 'k').  Note, 'k' cannot be zero.  If 'k' is ‘None’, it
     is treated like ‘1’.

  6. Concatenating immutable sequences always results in a new object.
     This means that building up a sequence by repeated concatenation
     will have a quadratic runtime cost in the total sequence length.
     To get a linear runtime cost, you must switch to one of the
     alternatives below:

        * if concatenating *note str: 3f2. objects, you can build a list
          and use *note str.join(): 2088. at the end or else write to an
          *note io.StringIO: ecb. instance and retrieve its value when
          complete

        * if concatenating *note bytes: 1a5. objects, you can similarly
          use *note bytes.join(): 2089. or *note io.BytesIO: e46, or you
          can do in-place concatenation with a *note bytearray: 4e3.
          object.  *note bytearray: 4e3. objects are mutable and have an
          efficient overallocation mechanism

        * if concatenating *note tuple: 322. objects, extend a *note
          list: 5b6. instead

        * for other types, investigate the relevant class documentation

  7. Some sequence types (such as *note range: 8e7.) only support item
     sequences that follow specific patterns, and hence don't support
     sequence concatenation or repetition.

  8. ‘index’ raises *note ValueError: 1e7. when 'x' is not found in 's'.
     Not all implementations support passing the additional arguments
     'i' and 'j'.  These arguments allow efficient searching of
     subsections of the sequence.  Passing the extra arguments is
     roughly equivalent to using ‘s[i:j].index(x)’, only without copying
     any data and with the returned index being relative to the start of
     the sequence rather than the start of the slice.

   ---------- Footnotes ----------

   (1) They must have since the parser can't tell the type of the
operands.


File: python.info,  Node: Immutable Sequence Types,  Next: Mutable Sequence Types,  Prev: Common Sequence Operations,  Up: Sequence Types --- list tuple range

5.4.7.2 Immutable Sequence Types
................................

The only operation that immutable sequence types generally implement
that is not also implemented by mutable sequence types is support for
the *note hash(): 58f. built-in.

This support allows immutable sequences, such as *note tuple: 322.
instances, to be used as *note dict: 23b. keys and stored in *note set:
57d. and *note frozenset: 57e. instances.

Attempting to hash an immutable sequence that contains unhashable values
will result in *note TypeError: 4dd.


File: python.info,  Node: Mutable Sequence Types,  Next: List（串列）<2>,  Prev: Immutable Sequence Types,  Up: Sequence Types --- list tuple range

5.4.7.3 Mutable Sequence Types
..............................

The operations in the following table are defined on mutable sequence
types.  The *note collections.abc.MutableSequence: 187. ABC is provided
to make it easier to correctly implement these operations on custom
sequence types.

In the table 's' is an instance of a mutable sequence type, 't' is any
iterable object and 'x' is an arbitrary object that meets any type and
value restrictions imposed by 's' (for example, *note bytearray: 4e3.
only accepts integers that meet the value restriction ‘0 <= x <= 255’).

運算                               結果                                 註解
                                                                        
--------------------------------------------------------------------------------------------------
                                                                        
‘s[i] = x’                         item 'i' of 's' is replaced by 'x'
                                   
                                                                        
‘s[i:j] = t’                       slice of 's' from 'i' to 'j' is
                                   replaced by the contents of the
                                   iterable 't'
                                   
                                                                        
‘del s[i:j]’                       same as ‘s[i:j] = []’
                                   
                                                                        
‘s[i:j:k] = t’                     the elements of ‘s[i:j:k]’ are       (1)
                                   replaced by those of 't'             
                                   
                                                                        
‘del s[i:j:k]’                     removes the elements of ‘s[i:j:k]’
                                   from the list
                                   
                                                                        
‘s.append(x)’                      appends 'x' to the end of the
                                   sequence (same as
                                   ‘s[len(s):len(s)] = [x]’)
                                   
                                                                        
‘s.clear()’                        removes all items from 's' (same     (5)
                                   as ‘del s[:]’)                       
                                   
                                                                        
‘s.copy()’                         creates a shallow copy of 's'        (5)
                                   (same as ‘s[:]’)                     
                                   
                                                                        
‘s.extend(t)’ 或 ‘s += t’          extends 's' with the contents of
                                   't' (for the most part the same as
                                   ‘s[len(s):len(s)] = t’)
                                   
                                                                        
‘s *= n’                           updates 's' with its contents        (6)
                                   repeated 'n' times                   
                                   
                                                                        
‘s.insert(i, x)’                   inserts 'x' into 's' at the index
                                   given by 'i' (same as ‘s[i:i] =
                                   [x]’)
                                   
                                                                        
‘s.pop()’ 或 ‘s.pop(i)’            retrieves the item at 'i' and also   (2)
                                   removes it from 's'                  
                                   
                                                                        
‘s.remove(x)’                      removes the first item from 's'      (3)
                                   where ‘s[i]’ is equal to 'x'         
                                   
                                                                        
‘s.reverse()’                      reverses the items of 's' in place   (4)
                                                                        

註解：

  1. If 'k' is not equal to ‘1’, 't' must have the same length as the
     slice it is replacing.

  2. The optional argument 'i' defaults to ‘-1’, so that by default the
     last item is removed and returned.

  3. ‘remove()’ raises *note ValueError: 1e7. when 'x' is not found in
     's'.

  4. The ‘reverse()’ method modifies the sequence in place for economy
     of space when reversing a large sequence.  To remind users that it
     operates by side effect, it does not return the reversed sequence.

  5. ‘clear()’ and ‘copy()’ are included for consistency with the
     interfaces of mutable containers that don't support slicing
     operations (such as *note dict: 23b. and *note set: 57d.).
     ‘copy()’ is not part of the *note collections.abc.MutableSequence:
     187. ABC, but most concrete mutable sequence classes provide it.

     在 3.3 版被加入: ‘clear()’ and ‘copy()’ methods.

  6. The value 'n' is an integer, or an object implementing *note
     __index__(): 6c1.  Zero and negative values of 'n' clear the
     sequence.  Items in the sequence are not copied; they are
     referenced multiple times, as explained for ‘s * n’ under *note
     Common Sequence Operations: 2086.


File: python.info,  Node: List（串列）<2>,  Next: Tuples,  Prev: Mutable Sequence Types,  Up: Sequence Types --- list tuple range

5.4.7.4 List（串列）
....................

Lists are mutable sequences, typically used to store collections of
homogeneous items (where the precise degree of similarity will vary by
application).

 -- 類別: list ([iterable])

     Lists may be constructed in several ways:

        * Using a pair of square brackets to denote the empty list: ‘[]’

        * Using square brackets, separating items with commas: ‘[a]’,
          ‘[a, b, c]’

        * Using a list comprehension: ‘[x for x in iterable]’

        * Using the type constructor: ‘list()’ or ‘list(iterable)’

     The constructor builds a list whose items are the same and in the
     same order as 'iterable"s items.  'iterable' may be either a
     sequence, a container that supports iteration, or an iterator
     object.  If 'iterable' is already a list, a copy is made and
     returned, similar to ‘iterable[:]’.  For example, ‘list('abc')’
     returns ‘['a', 'b', 'c']’ and ‘list( (1, 2, 3) )’ returns ‘[1, 2,
     3]’.  If no argument is given, the constructor creates a new empty
     list, ‘[]’.

     Many other operations also produce lists, including the *note
     sorted(): b75. built-in.

     Lists implement all of the *note common: 2086. and *note mutable:
     2037. sequence operations.  Lists also provide the following
     additional method:

      -- 方法: sort (*, key=None, reverse=False)

          This method sorts the list in place, using only ‘<’
          comparisons between items.  Exceptions are not suppressed - if
          any comparison operations fail, the entire sort operation will
          fail (and the list will likely be left in a partially modified
          state).

          *note sort(): b76. accepts two arguments that can only be
          passed by keyword (*note keyword-only arguments: 285.):

          'key' specifies a function of one argument that is used to
          extract a comparison key from each list element (for example,
          ‘key=str.lower’).  The key corresponding to each item in the
          list is calculated once and then used for the entire sorting
          process.  The default value of ‘None’ means that list items
          are sorted directly without calculating a separate key value.

          The *note functools.cmp_to_key(): 1172. utility is available
          to convert a 2.x style 'cmp' function to a 'key' function.

          'reverse' is a boolean value.  If set to ‘True’, then the list
          elements are sorted as if each comparison were reversed.

          This method modifies the sequence in place for economy of
          space when sorting a large sequence.  To remind users that it
          operates by side effect, it does not return the sorted
          sequence (use *note sorted(): b75. to explicitly request a new
          sorted list instance).

          The *note sort(): b76. method is guaranteed to be stable.  A
          sort is stable if it guarantees not to change the relative
          order of elements that compare equal -- this is helpful for
          sorting in multiple passes (for example, sort by department,
          then by salary grade).

          For sorting examples and a brief sorting tutorial, see *note
          排序技法: 205a.

          'CPython 實作細節：' While a list is being sorted, the effect
          of attempting to mutate, or even inspect, the list is
          undefined.  The C implementation of Python makes the list
          appear empty for the duration, and raises *note ValueError:
          1e7. if it can detect that the list has been mutated during a
          sort.


File: python.info,  Node: Tuples,  Next: Ranges,  Prev: List（串列）<2>,  Up: Sequence Types --- list tuple range

5.4.7.5 Tuples
..............

Tuples are immutable sequences, typically used to store collections of
heterogeneous data (such as the 2-tuples produced by the *note
enumerate(): 13ea. built-in).  Tuples are also used for cases where an
immutable sequence of homogeneous data is needed (such as allowing
storage in a *note set: 57d. or *note dict: 23b. instance).

 -- 類別: tuple ([iterable])

     Tuples may be constructed in a number of ways:

        * Using a pair of parentheses to denote the empty tuple: ‘()’

        * Using a trailing comma for a singleton tuple: ‘a,’ or ‘(a,)’

        * Separating items with commas: ‘a, b, c’ or ‘(a, b, c)’

        * Using the *note tuple(): 322. built-in: ‘tuple()’ or
          ‘tuple(iterable)’

     The constructor builds a tuple whose items are the same and in the
     same order as 'iterable"s items.  'iterable' may be either a
     sequence, a container that supports iteration, or an iterator
     object.  If 'iterable' is already a tuple, it is returned
     unchanged.  For example, ‘tuple('abc')’ returns ‘('a', 'b', 'c')’
     and ‘tuple( [1, 2, 3] )’ returns ‘(1, 2, 3)’.  If no argument is
     given, the constructor creates a new empty tuple, ‘()’.

     Note that it is actually the comma which makes a tuple, not the
     parentheses.  The parentheses are optional, except in the empty
     tuple case, or when they are needed to avoid syntactic ambiguity.
     For example, ‘f(a, b, c)’ is a function call with three arguments,
     while ‘f((a, b, c))’ is a function call with a 3-tuple as the sole
     argument.

     Tuples implement all of the *note common: 2086. sequence
     operations.

For heterogeneous collections of data where access by name is clearer
than access by index, *note collections.namedtuple(): 1ae. may be a more
appropriate choice than a simple tuple object.


File: python.info,  Node: Ranges,  Prev: Tuples,  Up: Sequence Types --- list tuple range

5.4.7.6 Ranges
..............

The *note range: 8e7. type represents an immutable sequence of numbers
and is commonly used for looping a specific number of times in *note
for: 2c3. loops.

 -- 類別: range (stop)

 -- 類別: range (start, stop[, step])

     The arguments to the range constructor must be integers (either
     built-in *note int: 23c. or any object that implements the *note
     __index__(): 6c1. special method).  If the 'step' argument is
     omitted, it defaults to ‘1’.  If the 'start' argument is omitted,
     it defaults to ‘0’.  If 'step' is zero, *note ValueError: 1e7. is
     raised.

     For a positive 'step', the contents of a range ‘r’ are determined
     by the formula ‘r[i] = start + step*i’ where ‘i >= 0’ and ‘r[i] <
     stop’.

     For a negative 'step', the contents of the range are still
     determined by the formula ‘r[i] = start + step*i’, but the
     constraints are ‘i >= 0’ and ‘r[i] > stop’.

     A range object will be empty if ‘r[0]’ does not meet the value
     constraint.  Ranges do support negative indices, but these are
     interpreted as indexing from the end of the sequence determined by
     the positive indices.

     Ranges containing absolute values larger than *note sys.maxsize:
     115d. are permitted but some features (such as *note len(): 5d4.)
     may raise *note OverflowError: 825.

     Range examples:

          >>> list(range(10))
          [0, 1, 2, 3, 4, 5, 6, 7, 8, 9]
          >>> list(range(1, 11))
          [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]
          >>> list(range(0, 30, 5))
          [0, 5, 10, 15, 20, 25]
          >>> list(range(0, 10, 3))
          [0, 3, 6, 9]
          >>> list(range(0, -10, -1))
          [0, -1, -2, -3, -4, -5, -6, -7, -8, -9]
          >>> list(range(0))
          []
          >>> list(range(1, 0))
          []

     Ranges implement all of the *note common: 2086. sequence operations
     except concatenation and repetition (due to the fact that range
     objects can only represent sequences that follow a strict pattern
     and repetition and concatenation will usually violate that
     pattern).

      -- 屬性: start

          The value of the 'start' parameter (or ‘0’ if the parameter
          was not supplied)

      -- 屬性: stop

          The value of the 'stop' parameter

      -- 屬性: step

          The value of the 'step' parameter (or ‘1’ if the parameter was
          not supplied)

The advantage of the *note range: 8e7. type over a regular *note list:
5b6. or *note tuple: 322. is that a *note range: 8e7. object will always
take the same (small) amount of memory, no matter the size of the range
it represents (as it only stores the ‘start’, ‘stop’ and ‘step’ values,
calculating individual items and subranges as needed).

Range objects implement the *note collections.abc.Sequence: 115c. ABC,
and provide features such as containment tests, element index lookup,
slicing and support for negative indices (see *note Sequence Types --
list, tuple, range: 1b4d.):

     >>> r = range(0, 20, 2)
     >>> r
     range(0, 20, 2)
     >>> 11 in r
     False
     >>> 10 in r
     True
     >>> r.index(10)
     5
     >>> r[5]
     10
     >>> r[:5]
     range(0, 10, 2)
     >>> r[-1]
     18

Testing range objects for equality with ‘==’ and ‘!=’ compares them as
sequences.  That is, two range objects are considered equal if they
represent the same sequence of values.  (Note that two range objects
that compare equal might have different *note start: 2090, *note stop:
2091. and *note step: 2092. attributes, for example ‘range(0) ==
range(2, 1, 3)’ or ‘range(0, 3, 2) == range(0, 4, 2)’.)

在 3.2 版的變更: Implement the Sequence ABC. Support slicing and
negative indices.  Test *note int: 23c. objects for membership in
constant time instead of iterating through all items.

在 3.3 版的變更: Define '==' and '!=' to compare range objects based on
the sequence of values they define (instead of comparing based on object
identity).

Added the *note start: 2090, *note stop: 2091. and *note step: 2092.
attributes.

也參考
......

   * The linspace recipe(1) shows how to implement a lazy version of
     range suitable for floating-point applications.

   ---------- Footnotes ----------

   (1) 
https://code.activestate.com/recipes/579000-equally-spaced-numbers-linspace/


File: python.info,  Node: Text Sequence Type --- str,  Next: Binary Sequence Types --- bytes bytearray memoryview,  Prev: Sequence Types --- list tuple range,  Up: 內建型別

5.4.8 Text Sequence Type -- ‘str’
---------------------------------

Textual data in Python is handled with *note str: 3f2. objects, or
'strings'.  Strings are immutable *note sequences: 1b4d. of Unicode code
points.  String literals are written in a variety of ways:

   * Single quotes: ‘'allows embedded "double" quotes'’

   * Double quotes: ‘"allows embedded 'single' quotes"’

   * Triple quoted: ‘'''Three single quotes'''’, ‘"""Three double
     quotes"""’

Triple quoted strings may span multiple lines - all associated
whitespace will be included in the string literal.

String literals that are part of a single expression and have only
whitespace between them will be implicitly converted to a single string
literal.  That is, ‘("spam " "eggs") == "spam eggs"’.

See *note String and Bytes literals: 1d96. for more about the various
forms of string literal, including supported *note escape sequences:
400, and the ‘r’ ("raw") prefix that disables most escape sequence
processing.

Strings may also be created from other objects using the *note str: 3f2.
constructor.

Since there is no separate "character" type, indexing a string produces
strings of length 1.  That is, for a non-empty string 's', ‘s[0] ==
s[0:1]’.

There is also no mutable string type, but *note str.join(): 2088. or
*note io.StringIO: ecb. can be used to efficiently construct strings
from multiple fragments.

在 3.3 版的變更: For backwards compatibility with the Python 2 series,
the ‘u’ prefix is once again permitted on string literals.  It has no
effect on the meaning of string literals and cannot be combined with the
‘r’ prefix.

 -- 類別: str (object='')

 -- 類別: str (object=b'', encoding='utf-8', errors='strict')

     Return a *note string: 1b03. version of 'object'.  If 'object' is
     not provided, returns the empty string.  Otherwise, the behavior of
     ‘str()’ depends on whether 'encoding' or 'errors' is given, as
     follows.

     If neither 'encoding' nor 'errors' is given, ‘str(object)’ returns
     *note type(object).__str__(object): 5c4, which is the "informal" or
     nicely printable string representation of 'object'.  For string
     objects, this is the string itself.  If 'object' does not have a
     *note __str__(): 5c4. method, then *note str(): 3f2. falls back to
     returning *note repr(object): 7a1.

     If at least one of 'encoding' or 'errors' is given, 'object' should
     be a *note bytes-like object: cd4. (e.g.  *note bytes: 1a5. or
     *note bytearray: 4e3.).  In this case, if 'object' is a *note
     bytes: 1a5. (or *note bytearray: 4e3.) object, then ‘str(bytes,
     encoding, errors)’ is equivalent to *note bytes.decode(encoding,
     errors): 87b.  Otherwise, the bytes object underlying the buffer
     object is obtained before calling *note bytes.decode(): 87b.  See
     *note Binary Sequence Types -- bytes, bytearray, memoryview: 2039.
     and *note 緩衝協定 (Buffer Protocol): 367. for information on
     buffer objects.

     Passing a *note bytes: 1a5. object to *note str(): 3f2. without the
     'encoding' or 'errors' arguments falls under the first case of
     returning the informal string representation (see also the *note
     -b: 587. command-line option to Python).  For example:

          >>> str(b'Zoot!')
          "b'Zoot!'"

     For more information on the ‘str’ class and its methods, see *note
     Text Sequence Type -- str: 1b03. and the *note String Methods:
     1b04. section below.  To output formatted strings, see the *note
     f-string（f 字串）: 94d. and *note 格式化文字語法: 131e. sections.
     In addition, see the *note 文本處理 (Text Processing) 服務: 2094.
     section.

* Menu:

* String Methods: String Methods<2>.
* printf-style String Formatting::


File: python.info,  Node: String Methods<2>,  Next: printf-style String Formatting,  Up: Text Sequence Type --- str

5.4.8.1 String Methods
......................

Strings implement all of the *note common: 2086. sequence operations,
along with the additional methods described below.

Strings also support two styles of string formatting, one providing a
large degree of flexibility and customization (see *note str.format():
5c7, *note 格式化文字語法: 131e. and *note 自訂字串格式: 2096.) and the
other based on C ‘printf’ style formatting that handles a narrower range
of types and is slightly harder to use correctly, but is often faster
for the cases it can handle (*note printf-style String Formatting:
671.).

The *note 文本處理 (Text Processing) 服務: 2097. section of the standard
library covers a number of other modules that provide various text
related utilities (including regular expression support in the *note re:
a7. module).

 -- 方法: str.capitalize ()

     Return a copy of the string with its first character capitalized
     and the rest lowercased.

     在 3.8 版的變更: The first character is now put into titlecase
     rather than uppercase.  This means that characters like digraphs
     will only have their first letter capitalized, instead of the full
     character.

 -- 方法: str.casefold ()

     Return a casefolded copy of the string.  Casefolded strings may be
     used for caseless matching.

     Casefolding is similar to lowercasing but more aggressive because
     it is intended to remove all case distinctions in a string.  For
     example, the German lowercase letter ‘'ß'’ is equivalent to ‘"ss"’.
     Since it is already lowercase, *note lower(): 16f2. would do
     nothing to ‘'ß'’; *note casefold(): d7c. converts it to ‘"ss"’.

     The casefolding algorithm is described in section 3.13 'Default
     Case Folding' of the Unicode Standard(1).

     在 3.3 版被加入.

 -- 方法: str.center (width[, fillchar])

     Return centered in a string of length 'width'.  Padding is done
     using the specified 'fillchar' (default is an ASCII space).  The
     original string is returned if 'width' is less than or equal to
     ‘len(s)’.

 -- 方法: str.count (sub[, start[, end]])

     Return the number of non-overlapping occurrences of substring 'sub'
     in the range ['start', 'end'].  Optional arguments 'start' and
     'end' are interpreted as in slice notation.

     If 'sub' is empty, returns the number of empty strings between
     characters which is the length of the string plus one.

 -- 方法: str.encode (encoding='utf-8', errors='strict')

     Return the string encoded to *note bytes: 1a5.

     'encoding' defaults to ‘'utf-8'’; see *note Standard Encodings:
     d5f. for possible values.

     'errors' controls how encoding errors are handled.  If ‘'strict'’
     (the default), a *note UnicodeError: 123a. exception is raised.
     Other possible values are ‘'ignore'’, ‘'replace'’,
     ‘'xmlcharrefreplace'’, ‘'backslashreplace'’ and any other name
     registered via *note codecs.register_error(): 1404.  See *note
     Error Handlers: 16eb. for details.

     For performance reasons, the value of 'errors' is not checked for
     validity unless an encoding error actually occurs, *note Python
     開發模式: 1dd. is enabled or a *note debug build: 1de. is used.

     在 3.1 版的變更: 新增關鍵字引數的支援。

     在 3.9 版的變更: The value of the 'errors' argument is now checked
     in *note Python 開發模式: 1dd. and in *note debug mode: 1de.

 -- 方法: str.endswith (suffix[, start[, end]])

     Return ‘True’ if the string ends with the specified 'suffix',
     otherwise return ‘False’.  'suffix' can also be a tuple of suffixes
     to look for.  With optional 'start', test beginning at that
     position.  With optional 'end', stop comparing at that position.

 -- 方法: str.expandtabs (tabsize=8)

     Return a copy of the string where all tab characters are replaced
     by one or more spaces, depending on the current column and the
     given tab size.  Tab positions occur every 'tabsize' characters
     (default is 8, giving tab positions at columns 0, 8, 16 and so on).
     To expand the string, the current column is set to zero and the
     string is examined character by character.  If the character is a
     tab (‘\t’), one or more space characters are inserted in the result
     until the current column is equal to the next tab position.  (The
     tab character itself is not copied.)  If the character is a newline
     (‘\n’) or return (‘\r’), it is copied and the current column is
     reset to zero.  Any other character is copied unchanged and the
     current column is incremented by one regardless of how the
     character is represented when printed.

          >>> '01\t012\t0123\t01234'.expandtabs()
          '01      012     0123    01234'
          >>> '01\t012\t0123\t01234'.expandtabs(4)
          '01  012 0123    01234'

 -- 方法: str.find (sub[, start[, end]])

     Return the lowest index in the string where substring 'sub' is
     found within the slice ‘s[start:end]’.  Optional arguments 'start'
     and 'end' are interpreted as in slice notation.  Return ‘-1’ if
     'sub' is not found.

          備註: The *note find(): e4a. method should be used only if you
          need to know the position of 'sub'.  To check if 'sub' is a
          substring or not, use the *note in: 2c5. operator:

               >>> 'Py' in 'Python'
               True

 -- 方法: str.format (*args, **kwargs)

     Perform a string formatting operation.  The string on which this
     method is called can contain literal text or replacement fields
     delimited by braces ‘{}’.  Each replacement field contains either
     the numeric index of a positional argument, or the name of a
     keyword argument.  Returns a copy of the string where each
     replacement field is replaced with the string value of the
     corresponding argument.

          >>> "The sum of 1 + 2 is {0}".format(1+2)
          'The sum of 1 + 2 is 3'

     See *note 格式化文字語法: 131e. for a description of the various
     formatting options that can be specified in format strings.

          備註: When formatting a number (*note int: 23c, *note float:
          2c8, *note complex: 2c9, *note decimal.Decimal: 27c. and
          subclasses) with the ‘n’ type (ex: ‘'{:n}'.format(1234)’), the
          function temporarily sets the ‘LC_CTYPE’ locale to the
          ‘LC_NUMERIC’ locale to decode ‘decimal_point’ and
          ‘thousands_sep’ fields of ‘localeconv()’ if they are non-ASCII
          or longer than 1 byte, and the ‘LC_NUMERIC’ locale is
          different than the ‘LC_CTYPE’ locale.  This temporary change
          affects other threads.

     在 3.7 版的變更: When formatting a number with the ‘n’ type, the
     function sets temporarily the ‘LC_CTYPE’ locale to the ‘LC_NUMERIC’
     locale in some cases.

 -- 方法: str.format_map (mapping, /)

     Similar to ‘str.format(**mapping)’, except that ‘mapping’ is used
     directly and not copied to a *note dict: 23b.  This is useful if
     for example ‘mapping’ is a dict subclass:

          >>> class Default(dict):
          ...     def __missing__(self, key):
          ...         return key
          ...
          >>> '{name} was born in {country}'.format_map(Default(name='Guido'))
          'Guido was born in country'

     在 3.2 版被加入.

 -- 方法: str.index (sub[, start[, end]])

     Like *note find(): e4a, but raise *note ValueError: 1e7. when the
     substring is not found.

 -- 方法: str.isalnum ()

     Return ‘True’ if all characters in the string are alphanumeric and
     there is at least one character, ‘False’ otherwise.  A character
     ‘c’ is alphanumeric if one of the following returns ‘True’:
     ‘c.isalpha()’, ‘c.isdecimal()’, ‘c.isdigit()’, or ‘c.isnumeric()’.

 -- 方法: str.isalpha ()

     Return ‘True’ if all characters in the string are alphabetic and
     there is at least one character, ‘False’ otherwise.  Alphabetic
     characters are those characters defined in the Unicode character
     database as "Letter", i.e., those with general category property
     being one of "Lm", "Lt", "Lu", "Ll", or "Lo".  Note that this is
     different from the Alphabetic property defined in the section 4.10
     'Letters, Alphabetic, and Ideographic' of the Unicode Standard(2).

 -- 方法: str.isascii ()

     Return ‘True’ if the string is empty or all characters in the
     string are ASCII, ‘False’ otherwise.  ASCII characters have code
     points in the range U+0000-U+007F.

     在 3.7 版被加入.

 -- 方法: str.isdecimal ()

     Return ‘True’ if all characters in the string are decimal
     characters and there is at least one character, ‘False’ otherwise.
     Decimal characters are those that can be used to form numbers in
     base 10, e.g.  U+0660, ARABIC-INDIC DIGIT ZERO. Formally a decimal
     character is a character in the Unicode General Category "Nd".

 -- 方法: str.isdigit ()

     Return ‘True’ if all characters in the string are digits and there
     is at least one character, ‘False’ otherwise.  Digits include
     decimal characters and digits that need special handling, such as
     the compatibility superscript digits.  This covers digits which
     cannot be used to form numbers in base 10, like the Kharosthi
     numbers.  Formally, a digit is a character that has the property
     value Numeric_Type=Digit or Numeric_Type=Decimal.

 -- 方法: str.isidentifier ()

     Return ‘True’ if the string is a valid identifier according to the
     language definition, section *note Identifiers and keywords: 1d86.

     *note keyword.iskeyword(): 209e. can be used to test whether string
     ‘s’ is a reserved identifier, such as *note def: 13c5. and *note
     class: 126a.

     範例：

          >>> from keyword import iskeyword

          >>> 'hello'.isidentifier(), iskeyword('hello')
          (True, False)
          >>> 'def'.isidentifier(), iskeyword('def')
          (True, True)

 -- 方法: str.islower ()

     Return ‘True’ if all cased characters (3) in the string are
     lowercase and there is at least one cased character, ‘False’
     otherwise.

 -- 方法: str.isnumeric ()

     Return ‘True’ if all characters in the string are numeric
     characters, and there is at least one character, ‘False’ otherwise.
     Numeric characters include digit characters, and all characters
     that have the Unicode numeric value property, e.g.  U+2155, VULGAR
     FRACTION ONE FIFTH. Formally, numeric characters are those with the
     property value Numeric_Type=Digit, Numeric_Type=Decimal or
     Numeric_Type=Numeric.

 -- 方法: str.isprintable ()

     Return ‘True’ if all characters in the string are printable or the
     string is empty, ‘False’ otherwise.  Nonprintable characters are
     those characters defined in the Unicode character database as
     "Other" or "Separator", excepting the ASCII space (0x20) which is
     considered printable.  (Note that printable characters in this
     context are those which should not be escaped when *note repr():
     7a1. is invoked on a string.  It has no bearing on the handling of
     strings written to *note sys.stdout: a79. or *note sys.stderr:
     8dd.)

 -- 方法: str.isspace ()

     Return ‘True’ if there are only whitespace characters in the string
     and there is at least one character, ‘False’ otherwise.

     A character is 'whitespace' if in the Unicode character database
     (see *note unicodedata: ee.), either its general category is ‘Zs’
     ("Separator, space"), or its bidirectional class is one of ‘WS’,
     ‘B’, or ‘S’.

 -- 方法: str.istitle ()

     Return ‘True’ if the string is a titlecased string and there is at
     least one character, for example uppercase characters may only
     follow uncased characters and lowercase characters only cased ones.
     Return ‘False’ otherwise.

 -- 方法: str.isupper ()

     Return ‘True’ if all cased characters (4) in the string are
     uppercase and there is at least one cased character, ‘False’
     otherwise.

          >>> 'BANANA'.isupper()
          True
          >>> 'banana'.isupper()
          False
          >>> 'baNana'.isupper()
          False
          >>> ' '.isupper()
          False

 -- 方法: str.join (iterable)

     Return a string which is the concatenation of the strings in
     'iterable'.  A *note TypeError: 4dd. will be raised if there are
     any non-string values in 'iterable', including *note bytes: 1a5.
     objects.  The separator between elements is the string providing
     this method.

 -- 方法: str.ljust (width[, fillchar])

     Return the string left justified in a string of length 'width'.
     Padding is done using the specified 'fillchar' (default is an ASCII
     space).  The original string is returned if 'width' is less than or
     equal to ‘len(s)’.

 -- 方法: str.lower ()

     Return a copy of the string with all the cased characters (5)
     converted to lowercase.

     The lowercasing algorithm used is described in section 3.13
     'Default Case Folding' of the Unicode Standard(6).

 -- 方法: str.lstrip ([chars])

     Return a copy of the string with leading characters removed.  The
     'chars' argument is a string specifying the set of characters to be
     removed.  If omitted or ‘None’, the 'chars' argument defaults to
     removing whitespace.  The 'chars' argument is not a prefix; rather,
     all combinations of its values are stripped:

          >>> '   spacious   '.lstrip()
          'spacious   '
          >>> 'www.example.com'.lstrip('cmowz.')
          'example.com'

     See *note str.removeprefix(): 874. for a method that will remove a
     single prefix string rather than all of a set of characters.  For
     example:

          >>> 'Arthur: three!'.lstrip('Arthur: ')
          'ee!'
          >>> 'Arthur: three!'.removeprefix('Arthur: ')
          'three!'

 -- 方法: static str.maketrans (x[, y[, z]])

     This static method returns a translation table usable for *note
     str.translate(): 20a5.

     If there is only one argument, it must be a dictionary mapping
     Unicode ordinals (integers) or characters (strings of length 1) to
     Unicode ordinals, strings (of arbitrary lengths) or ‘None’.
     Character keys will then be converted to ordinals.

     If there are two arguments, they must be strings of equal length,
     and in the resulting dictionary, each character in x will be mapped
     to the character at the same position in y.  If there is a third
     argument, it must be a string, whose characters will be mapped to
     ‘None’ in the result.

 -- 方法: str.partition (sep)

     Split the string at the first occurrence of 'sep', and return a
     3-tuple containing the part before the separator, the separator
     itself, and the part after the separator.  If the separator is not
     found, return a 3-tuple containing the string itself, followed by
     two empty strings.

 -- 方法: str.removeprefix (prefix, /)

     If the string starts with the 'prefix' string, return
     ‘string[len(prefix):]’.  Otherwise, return a copy of the original
     string:

          >>> 'TestHook'.removeprefix('Test')
          'Hook'
          >>> 'BaseTestCase'.removeprefix('Test')
          'BaseTestCase'

     在 3.9 版被加入.

 -- 方法: str.removesuffix (suffix, /)

     If the string ends with the 'suffix' string and that 'suffix' is
     not empty, return ‘string[:-len(suffix)]’.  Otherwise, return a
     copy of the original string:

          >>> 'MiscTests'.removesuffix('Tests')
          'Misc'
          >>> 'TmpDirMixin'.removesuffix('Tests')
          'TmpDirMixin'

     在 3.9 版被加入.

 -- 方法: str.replace (old, new, count=-1)

     Return a copy of the string with all occurrences of substring 'old'
     replaced by 'new'.  If 'count' is given, only the first 'count'
     occurrences are replaced.  If 'count' is not specified or ‘-1’,
     then all occurrences are replaced.

     在 3.13 版的變更: 'count' is now supported as a keyword argument.

 -- 方法: str.rfind (sub[, start[, end]])

     Return the highest index in the string where substring 'sub' is
     found, such that 'sub' is contained within ‘s[start:end]’.
     Optional arguments 'start' and 'end' are interpreted as in slice
     notation.  Return ‘-1’ on failure.

 -- 方法: str.rindex (sub[, start[, end]])

     Like *note rfind(): e4b. but raises *note ValueError: 1e7. when the
     substring 'sub' is not found.

 -- 方法: str.rjust (width[, fillchar])

     Return the string right justified in a string of length 'width'.
     Padding is done using the specified 'fillchar' (default is an ASCII
     space).  The original string is returned if 'width' is less than or
     equal to ‘len(s)’.

 -- 方法: str.rpartition (sep)

     Split the string at the last occurrence of 'sep', and return a
     3-tuple containing the part before the separator, the separator
     itself, and the part after the separator.  If the separator is not
     found, return a 3-tuple containing two empty strings, followed by
     the string itself.

 -- 方法: str.rsplit (sep=None, maxsplit=-1)

     Return a list of the words in the string, using 'sep' as the
     delimiter string.  If 'maxsplit' is given, at most 'maxsplit'
     splits are done, the 'rightmost' ones.  If 'sep' is not specified
     or ‘None’, any whitespace string is a separator.  Except for
     splitting from the right, *note rsplit(): 11ee. behaves like *note
     split(): e4c. which is described in detail below.

 -- 方法: str.rstrip ([chars])

     Return a copy of the string with trailing characters removed.  The
     'chars' argument is a string specifying the set of characters to be
     removed.  If omitted or ‘None’, the 'chars' argument defaults to
     removing whitespace.  The 'chars' argument is not a suffix; rather,
     all combinations of its values are stripped:

          >>> '   spacious   '.rstrip()
          '   spacious'
          >>> 'mississippi'.rstrip('ipz')
          'mississ'

     See *note str.removesuffix(): 875. for a method that will remove a
     single suffix string rather than all of a set of characters.  For
     example:

          >>> 'Monty Python'.rstrip(' Python')
          'M'
          >>> 'Monty Python'.removesuffix(' Python')
          'Monty'

 -- 方法: str.split (sep=None, maxsplit=-1)

     Return a list of the words in the string, using 'sep' as the
     delimiter string.  If 'maxsplit' is given, at most 'maxsplit'
     splits are done (thus, the list will have at most ‘maxsplit+1’
     elements).  If 'maxsplit' is not specified or ‘-1’, then there is
     no limit on the number of splits (all possible splits are made).

     If 'sep' is given, consecutive delimiters are not grouped together
     and are deemed to delimit empty strings (for example,
     ‘'1,,2'.split(',')’ returns ‘['1', '', '2']’).  The 'sep' argument
     may consist of multiple characters as a single delimiter (to split
     with multiple delimiters, use *note re.split(): 282.).  Splitting
     an empty string with a specified separator returns ‘['']’.

     舉例來說：

          >>> '1,2,3'.split(',')
          ['1', '2', '3']
          >>> '1,2,3'.split(',', maxsplit=1)
          ['1', '2,3']
          >>> '1,2,,3,'.split(',')
          ['1', '2', '', '3', '']
          >>> '1<>2<>3<4'.split('<>')
          ['1', '2', '3<4']

     If 'sep' is not specified or is ‘None’, a different splitting
     algorithm is applied: runs of consecutive whitespace are regarded
     as a single separator, and the result will contain no empty strings
     at the start or end if the string has leading or trailing
     whitespace.  Consequently, splitting an empty string or a string
     consisting of just whitespace with a ‘None’ separator returns ‘[]’.

     舉例來說：

          >>> '1 2 3'.split()
          ['1', '2', '3']
          >>> '1 2 3'.split(maxsplit=1)
          ['1', '2 3']
          >>> '   1   2   3   '.split()
          ['1', '2', '3']

 -- 方法: str.splitlines (keepends=False)

     Return a list of the lines in the string, breaking at line
     boundaries.  Line breaks are not included in the resulting list
     unless 'keepends' is given and true.

     This method splits on the following line boundaries.  In
     particular, the boundaries are a superset of *note universal
     newlines: ce1.

     Representation              描述
                                 
     --------------------------------------------------------------
                                 
     ‘\n’                        Line Feed
                                 
                                 
     ‘\r’                        Carriage Return
                                 
                                 
     ‘\r\n’                      Carriage Return + Line Feed
                                 
                                 
     ‘\v’ 或 ‘\x0b’              Line Tabulation
                                 
                                 
     ‘\f’ 或 ‘\x0c’              Form Feed
                                 
                                 
     ‘\x1c’                      File Separator
                                 
                                 
     ‘\x1d’                      Group Separator
                                 
                                 
     ‘\x1e’                      Record Separator
                                 
                                 
     ‘\x85’                      Next Line (C1 Control Code)
                                 
                                 
     ‘\u2028’                    Line Separator
                                 
                                 
     ‘\u2029’                    Paragraph Separator
                                 

     在 3.2 版的變更: ‘\v’ and ‘\f’ added to list of line boundaries.

     舉例來說：

          >>> 'ab c\n\nde fg\rkl\r\n'.splitlines()
          ['ab c', '', 'de fg', 'kl']
          >>> 'ab c\n\nde fg\rkl\r\n'.splitlines(keepends=True)
          ['ab c\n', '\n', 'de fg\r', 'kl\r\n']

     Unlike *note split(): e4c. when a delimiter string 'sep' is given,
     this method returns an empty list for the empty string, and a
     terminal line break does not result in an extra line:

          >>> "".splitlines()
          []
          >>> "One line\n".splitlines()
          ['One line']

     For comparison, ‘split('\n')’ gives:

          >>> ''.split('\n')
          ['']
          >>> 'Two lines\n'.split('\n')
          ['Two lines', '']

 -- 方法: str.startswith (prefix[, start[, end]])

     Return ‘True’ if string starts with the 'prefix', otherwise return
     ‘False’.  'prefix' can also be a tuple of prefixes to look for.
     With optional 'start', test string beginning at that position.
     With optional 'end', stop comparing string at that position.

 -- 方法: str.strip ([chars])

     Return a copy of the string with the leading and trailing
     characters removed.  The 'chars' argument is a string specifying
     the set of characters to be removed.  If omitted or ‘None’, the
     'chars' argument defaults to removing whitespace.  The 'chars'
     argument is not a prefix or suffix; rather, all combinations of its
     values are stripped:

          >>> '   spacious   '.strip()
          'spacious'
          >>> 'www.example.com'.strip('cmowz.')
          'example'

     The outermost leading and trailing 'chars' argument values are
     stripped from the string.  Characters are removed from the leading
     end until reaching a string character that is not contained in the
     set of characters in 'chars'.  A similar action takes place on the
     trailing end.  For example:

          >>> comment_string = '#....... Section 3.2.1 Issue #32 .......'
          >>> comment_string.strip('.#! ')
          'Section 3.2.1 Issue #32'

 -- 方法: str.swapcase ()

     Return a copy of the string with uppercase characters converted to
     lowercase and vice versa.  Note that it is not necessarily true
     that ‘s.swapcase().swapcase() == s’.

 -- 方法: str.title ()

     Return a titlecased version of the string where words start with an
     uppercase character and the remaining characters are lowercase.

     舉例來說：

          >>> 'Hello world'.title()
          'Hello World'

     The algorithm uses a simple language-independent definition of a
     word as groups of consecutive letters.  The definition works in
     many contexts but it means that apostrophes in contractions and
     possessives form word boundaries, which may not be the desired
     result:

          >>> "they're bill's friends from the UK".title()
          "They'Re Bill'S Friends From The Uk"

     The *note string.capwords(): 20a8. function does not have this
     problem, as it splits words on spaces only.

     Alternatively, a workaround for apostrophes can be constructed
     using regular expressions:

          >>> import re
          >>> def titlecase(s):
          ...     return re.sub(r"[A-Za-z]+('[A-Za-z]+)?",
          ...                   lambda mo: mo.group(0).capitalize(),
          ...                   s)
          ...
          >>> titlecase("they're bill's friends.")
          "They're Bill's Friends."

 -- 方法: str.translate (table)

     Return a copy of the string in which each character has been mapped
     through the given translation table.  The table must be an object
     that implements indexing via *note __getitem__(): 266, typically a
     *note mapping: 1154. or *note sequence: 499.  When indexed by a
     Unicode ordinal (an integer), the table object can do any of the
     following: return a Unicode ordinal or a string, to map the
     character to one or more other characters; return ‘None’, to delete
     the character from the return string; or raise a *note LookupError:
     20a9. exception, to map the character to itself.

     You can use *note str.maketrans(): d7f. to create a translation map
     from character-to-character mappings in different formats.

     See also the *note codecs: 14. module for a more flexible approach
     to custom character mappings.

 -- 方法: str.upper ()

     Return a copy of the string with all the cased characters (7)
     converted to uppercase.  Note that ‘s.upper().isupper()’ might be
     ‘False’ if ‘s’ contains uncased characters or if the Unicode
     category of the resulting character(s) is not "Lu" (Letter,
     uppercase), but e.g.  "Lt" (Letter, titlecase).

     The uppercasing algorithm used is described in section 3.13
     'Default Case Folding' of the Unicode Standard(8).

 -- 方法: str.zfill (width)

     Return a copy of the string left filled with ASCII ‘'0'’ digits to
     make a string of length 'width'.  A leading sign prefix
     (‘'+'’/‘'-'’) is handled by inserting the padding 'after' the sign
     character rather than before.  The original string is returned if
     'width' is less than or equal to ‘len(s)’.

     舉例來說：

          >>> "42".zfill(5)
          '00042'
          >>> "-42".zfill(5)
          '-0042'

   ---------- Footnotes ----------

   (1) https://www.unicode.org/versions/Unicode15.1.0/ch03.pdf

   (2) https://www.unicode.org/versions/Unicode15.1.0/ch04.pdf

   (3) Cased characters are those with general category property being
one of "Lu" (Letter, uppercase), "Ll" (Letter, lowercase), or "Lt"
(Letter, titlecase).

   (4) Cased characters are those with general category property being
one of "Lu" (Letter, uppercase), "Ll" (Letter, lowercase), or "Lt"
(Letter, titlecase).

   (5) Cased characters are those with general category property being
one of "Lu" (Letter, uppercase), "Ll" (Letter, lowercase), or "Lt"
(Letter, titlecase).

   (6) https://www.unicode.org/versions/Unicode15.1.0/ch03.pdf

   (7) Cased characters are those with general category property being
one of "Lu" (Letter, uppercase), "Ll" (Letter, lowercase), or "Lt"
(Letter, titlecase).

   (8) https://www.unicode.org/versions/Unicode15.1.0/ch03.pdf


File: python.info,  Node: printf-style String Formatting,  Prev: String Methods<2>,  Up: Text Sequence Type --- str

5.4.8.2 ‘printf’-style String Formatting
........................................

     備註: The formatting operations described here exhibit a variety of
     quirks that lead to a number of common errors (such as failing to
     display tuples and dictionaries correctly).  Using the newer *note
     formatted string literals: 94d, the *note str.format(): 5c7.
     interface, or *note template strings: 20ac. may help avoid these
     errors.  Each of these alternatives provides their own trade-offs
     and benefits of simplicity, flexibility, and/or extensibility.

String objects have one unique built-in operation: the ‘%’ operator
(modulo).  This is also known as the string 'formatting' or
'interpolation' operator.  Given ‘format % values’ (where 'format' is a
string), ‘%’ conversion specifications in 'format' are replaced with
zero or more elements of 'values'.  The effect is similar to using the
‘sprintf()’ function in the C language.  For example:

     >>> print('%s has %d quote types.' % ('Python', 2))
     Python has 2 quote types.

If 'format' requires a single argument, 'values' may be a single
non-tuple object.  (1)  Otherwise, 'values' must be a tuple with exactly
the number of items specified by the format string, or a single mapping
object (for example, a dictionary).

A conversion specifier contains two or more characters and has the
following components, which must occur in this order:

  1. The ‘'%'’ character, which marks the start of the specifier.

  2. Mapping key (optional), consisting of a parenthesised sequence of
     characters (for example, ‘(somename)’).

  3. Conversion flags (optional), which affect the result of some
     conversion types.

  4. Minimum field width (optional).  If specified as an ‘'*'’
     (asterisk), the actual width is read from the next element of the
     tuple in 'values', and the object to convert comes after the
     minimum field width and optional precision.

  5. Precision (optional), given as a ‘'.'’ (dot) followed by the
     precision.  If specified as ‘'*'’ (an asterisk), the actual
     precision is read from the next element of the tuple in 'values',
     and the value to convert comes after the precision.

  6. Length modifier (optional).

  7. Conversion type.

When the right argument is a dictionary (or other mapping type), then
the formats in the string 'must' include a parenthesised mapping key
into that dictionary inserted immediately after the ‘'%'’ character.
The mapping key selects the value to be formatted from the mapping.  For
example:

     >>> print('%(language)s has %(number)03d quote types.' %
     ...       {'language': "Python", "number": 2})
     Python has 002 quote types.

In this case no ‘*’ specifiers may occur in a format (since they require
a sequential parameter list).

The conversion flag characters are:

Flag          含義
              
----------------------------------------------------------------------------------------
              
‘'#'’         The value conversion will use the "alternate form" (where defined
              below).
              
              
‘'0'’         The conversion will be zero padded for numeric values.
              
              
‘'-'’         The converted value is left adjusted (overrides the ‘'0'’ conversion if
              both are given).
              
              
‘' '’         (a space) A blank should be left before a positive number (or empty
              string) produced by a signed conversion.
              
              
‘'+'’         A sign character (‘'+'’ or ‘'-'’) will precede the conversion
              (overrides a "space" flag).
              

A length modifier (‘h’, ‘l’, or ‘L’) may be present, but is ignored as
it is not necessary for Python - so e.g.  ‘%ld’ is identical to ‘%d’.

The conversion types are:

Conversion       含義                                                      註解
                                                                           
---------------------------------------------------------------------------------------
                                                                           
‘'d'’            Signed integer decimal.
                 
                                                                           
‘'i'’            Signed integer decimal.
                 
                                                                           
‘'o'’            Signed octal value.                                       (1)
                                                                           
                                                                           
‘'u'’            Obsolete type - it is identical to ‘'d'’.                 (6)
                                                                           
                                                                           
‘'x'’            Signed hexadecimal (lowercase).                           (2)
                                                                           
                                                                           
‘'X'’            Signed hexadecimal (uppercase).                           (2)
                                                                           
                                                                           
‘'e'’            Floating-point exponential format (lowercase).            (3)
                                                                           
                                                                           
‘'E'’            Floating-point exponential format (uppercase).            (3)
                                                                           
                                                                           
‘'f'’            Floating-point decimal format.                            (3)
                                                                           
                                                                           
‘'F'’            Floating-point decimal format.                            (3)
                                                                           
                                                                           
‘'g'’            Floating-point format.  Uses lowercase exponential        (4)
                 format if exponent is less than -4 or not less than       
                 precision, decimal format otherwise.
                 
                                                                           
‘'G'’            Floating-point format.  Uses uppercase exponential        (4)
                 format if exponent is less than -4 or not less than       
                 precision, decimal format otherwise.
                 
                                                                           
‘'c'’            Single character (accepts integer or single character
                 string).
                 
                                                                           
‘'r'’            String (converts any Python object using                  (5)
                 *note repr(): 7a1.).                                      
                 
                                                                           
‘'s'’            String (converts any Python object using                  (5)
                 *note str(): 3f2.).                                       
                 
                                                                           
‘'a'’            String (converts any Python object using                  (5)
                 *note ascii(): 1354.).                                    
                 
                                                                           
‘'%'’            No argument is converted, results in a ‘'%'’ character
                 in the result.
                 

註解：

  1. The alternate form causes a leading octal specifier (‘'0o'’) to be
     inserted before the first digit.

  2. The alternate form causes a leading ‘'0x'’ or ‘'0X'’ (depending on
     whether the ‘'x'’ or ‘'X'’ format was used) to be inserted before
     the first digit.

  3. The alternate form causes the result to always contain a decimal
     point, even if no digits follow it.

     The precision determines the number of digits after the decimal
     point and defaults to 6.

  4. The alternate form causes the result to always contain a decimal
     point, and trailing zeroes are not removed as they would otherwise
     be.

     The precision determines the number of significant digits before
     and after the decimal point and defaults to 6.

  5. If precision is ‘N’, the output is truncated to ‘N’ characters.

  6. 參閱 PEP 237(2)。

Since Python strings have an explicit length, ‘%s’ conversions do not
assume that ‘'\0'’ is the end of the string.

在 3.1 版的變更: ‘%f’ conversions for numbers whose absolute value is
over 1e50 are no longer replaced by ‘%g’ conversions.

   ---------- Footnotes ----------

   (1) To format only a tuple you should therefore provide a singleton
tuple whose only element is the tuple to be formatted.

   (2) https://peps.python.org/pep-0237/


File: python.info,  Node: Binary Sequence Types --- bytes bytearray memoryview,  Next: Set Types --- set frozenset,  Prev: Text Sequence Type --- str,  Up: 內建型別

5.4.9 Binary Sequence Types -- ‘bytes’, ‘bytearray’, ‘memoryview’
-----------------------------------------------------------------

The core built-in types for manipulating binary data are *note bytes:
1a5. and *note bytearray: 4e3.  They are supported by *note memoryview:
40f. which uses the *note buffer protocol: 367. to access the memory of
other binary objects without needing to make a copy.

The *note array: 6. module supports efficient storage of basic data
types like 32-bit integers and IEEE754 double-precision floating values.

* Menu:

* Bytes Objects::
* Bytearray Objects::
* Bytes and Bytearray Operations::
* printf-style Bytes Formatting::
* Memory Views::


File: python.info,  Node: Bytes Objects,  Next: Bytearray Objects,  Up: Binary Sequence Types --- bytes bytearray memoryview

5.4.9.1 Bytes Objects
.....................

Bytes objects are immutable sequences of single bytes.  Since many major
binary protocols are based on the ASCII text encoding, bytes objects
offer several methods that are only valid when working with ASCII
compatible data and are closely related to string objects in a variety
of other ways.

 -- 類別: bytes ([source[, encoding[, errors]]])

     Firstly, the syntax for bytes literals is largely the same as that
     for string literals, except that a ‘b’ prefix is added:

        * Single quotes: ‘b'still allows embedded "double" quotes'’

        * Double quotes: ‘b"still allows embedded 'single' quotes"’

        * Triple quoted: ‘b'''3 single quotes'''’, ‘b"""3 double
          quotes"""’

     Only ASCII characters are permitted in bytes literals (regardless
     of the declared source code encoding).  Any binary values over 127
     must be entered into bytes literals using the appropriate escape
     sequence.

     As with string literals, bytes literals may also use a ‘r’ prefix
     to disable processing of escape sequences.  See *note String and
     Bytes literals: 1d96. for more about the various forms of bytes
     literal, including supported escape sequences.

     While bytes literals and representations are based on ASCII text,
     bytes objects actually behave like immutable sequences of integers,
     with each value in the sequence restricted such that ‘0 <= x < 256’
     (attempts to violate this restriction will trigger *note
     ValueError: 1e7.).  This is done deliberately to emphasise that
     while many binary formats include ASCII based elements and can be
     usefully manipulated with some text-oriented algorithms, this is
     not generally the case for arbitrary binary data (blindly applying
     text processing algorithms to binary data formats that are not
     ASCII compatible will usually lead to data corruption).

     In addition to the literal forms, bytes objects can be created in a
     number of other ways:

        * A zero-filled bytes object of a specified length: ‘bytes(10)’

        * From an iterable of integers: ‘bytes(range(20))’

        * Copying existing binary data via the buffer protocol:
          ‘bytes(obj)’

     Also see the *note bytes: 19bf. built-in.

     Since 2 hexadecimal digits correspond precisely to a single byte,
     hexadecimal numbers are a commonly used format for describing
     binary data.  Accordingly, the bytes type has an additional class
     method to read data in that format:

      -- 方法: classmethod fromhex (string)

          This *note bytes: 1a5. class method returns a bytes object,
          decoding the given string object.  The string must contain two
          hexadecimal digits per byte, with ASCII whitespace being
          ignored.

               >>> bytes.fromhex('2Ef0 F1f2  ')
               b'.\xf0\xf1\xf2'

          在 3.7 版的變更: *note bytes.fromhex(): a92. now skips all
          ASCII whitespace in the string, not just spaces.

     A reverse conversion function exists to transform a bytes object
     into its hexadecimal representation.

      -- 方法: hex ([sep[, bytes_per_sep]])

          Return a string object containing two hexadecimal digits for
          each byte in the instance.

               >>> b'\xf0\xf1\xf2'.hex()
               'f0f1f2'

          If you want to make the hex string easier to read, you can
          specify a single character separator 'sep' parameter to
          include in the output.  By default, this separator will be
          included between each byte.  A second optional 'bytes_per_sep'
          parameter controls the spacing.  Positive values calculate the
          separator position from the right, negative values from the
          left.

               >>> value = b'\xf0\xf1\xf2'
               >>> value.hex('-')
               'f0-f1-f2'
               >>> value.hex('_', 2)
               'f0_f1f2'
               >>> b'UUDDLRLRAB'.hex(' ', -4)
               '55554444 4c524c52 4142'

          在 3.5 版被加入.

          在 3.8 版的變更: *note bytes.hex(): d0f. now supports optional
          'sep' and 'bytes_per_sep' parameters to insert separators
          between bytes in the hex output.

Since bytes objects are sequences of integers (akin to a tuple), for a
bytes object 'b', ‘b[0]’ will be an integer, while ‘b[0:1]’ will be a
bytes object of length 1.  (This contrasts with text strings, where both
indexing and slicing will produce a string of length 1)

The representation of bytes objects uses the literal format (‘b'...'’)
since it is often more useful than e.g.  ‘bytes([46, 46, 46])’.  You can
always convert a bytes object into a list of integers using ‘list(b)’.


File: python.info,  Node: Bytearray Objects,  Next: Bytes and Bytearray Operations,  Prev: Bytes Objects,  Up: Binary Sequence Types --- bytes bytearray memoryview

5.4.9.2 Bytearray Objects
.........................

*note bytearray: 4e3. objects are a mutable counterpart to *note bytes:
1a5. objects.

 -- 類別: bytearray ([source[, encoding[, errors]]])

     There is no dedicated literal syntax for bytearray objects, instead
     they are always created by calling the constructor:

        * Creating an empty instance: ‘bytearray()’

        * Creating a zero-filled instance with a given length:
          ‘bytearray(10)’

        * From an iterable of integers: ‘bytearray(range(20))’

        * Copying existing binary data via the buffer protocol:
          ‘bytearray(b'Hi!')’

     As bytearray objects are mutable, they support the *note mutable:
     2037. sequence operations in addition to the common bytes and
     bytearray operations described in *note Bytes and Bytearray
     Operations: 2038.

     Also see the *note bytearray: 19c0. built-in.

     Since 2 hexadecimal digits correspond precisely to a single byte,
     hexadecimal numbers are a commonly used format for describing
     binary data.  Accordingly, the bytearray type has an additional
     class method to read data in that format:

      -- 方法: classmethod fromhex (string)

          This *note bytearray: 4e3. class method returns bytearray
          object, decoding the given string object.  The string must
          contain two hexadecimal digits per byte, with ASCII whitespace
          being ignored.

               >>> bytearray.fromhex('2Ef0 F1f2  ')
               bytearray(b'.\xf0\xf1\xf2')

          在 3.7 版的變更: *note bytearray.fromhex(): a93. now skips all
          ASCII whitespace in the string, not just spaces.

     A reverse conversion function exists to transform a bytearray
     object into its hexadecimal representation.

      -- 方法: hex ([sep[, bytes_per_sep]])

          Return a string object containing two hexadecimal digits for
          each byte in the instance.

               >>> bytearray(b'\xf0\xf1\xf2').hex()
               'f0f1f2'

          在 3.5 版被加入.

          在 3.8 版的變更: Similar to *note bytes.hex(): d0f, *note
          bytearray.hex(): d10. now supports optional 'sep' and
          'bytes_per_sep' parameters to insert separators between bytes
          in the hex output.

Since bytearray objects are sequences of integers (akin to a list), for
a bytearray object 'b', ‘b[0]’ will be an integer, while ‘b[0:1]’ will
be a bytearray object of length 1.  (This contrasts with text strings,
where both indexing and slicing will produce a string of length 1)

The representation of bytearray objects uses the bytes literal format
(‘bytearray(b'...')’) since it is often more useful than e.g.
‘bytearray([46, 46, 46])’.  You can always convert a bytearray object
into a list of integers using ‘list(b)’.


File: python.info,  Node: Bytes and Bytearray Operations,  Next: printf-style Bytes Formatting,  Prev: Bytearray Objects,  Up: Binary Sequence Types --- bytes bytearray memoryview

5.4.9.3 Bytes and Bytearray Operations
......................................

Both bytes and bytearray objects support the *note common: 2086.
sequence operations.  They interoperate not just with operands of the
same type, but with any *note bytes-like object: cd4.  Due to this
flexibility, they can be freely mixed in operations without causing
errors.  However, the return type of the result may depend on the order
of operands.

     備註: The methods on bytes and bytearray objects don't accept
     strings as their arguments, just as the methods on strings don't
     accept bytes as their arguments.  For example, you have to write:

          a = "abc"
          b = a.replace("a", "f")

     和：

          a = b"abc"
          b = a.replace(b"a", b"f")

Some bytes and bytearray operations assume the use of ASCII compatible
binary formats, and hence should be avoided when working with arbitrary
binary data.  These restrictions are covered below.

     備註: Using these ASCII based operations to manipulate binary data
     that is not stored in an ASCII based format may lead to data
     corruption.

The following methods on bytes and bytearray objects can be used with
arbitrary binary data.

 -- 方法: bytes.count (sub[, start[, end]])
 -- 方法: bytearray.count (sub[, start[, end]])

     Return the number of non-overlapping occurrences of subsequence
     'sub' in the range ['start', 'end'].  Optional arguments 'start'
     and 'end' are interpreted as in slice notation.

     The subsequence to search for may be any *note bytes-like object:
     cd4. or an integer in the range 0 to 255.

     If 'sub' is empty, returns the number of empty slices between
     characters which is the length of the bytes object plus one.

     在 3.3 版的變更: Also accept an integer in the range 0 to 255 as
     the subsequence.

 -- 方法: bytes.removeprefix (prefix, /)
 -- 方法: bytearray.removeprefix (prefix, /)

     If the binary data starts with the 'prefix' string, return
     ‘bytes[len(prefix):]’.  Otherwise, return a copy of the original
     binary data:

          >>> b'TestHook'.removeprefix(b'Test')
          b'Hook'
          >>> b'BaseTestCase'.removeprefix(b'Test')
          b'BaseTestCase'

     The 'prefix' may be any *note bytes-like object: cd4.

          備註: The bytearray version of this method does 'not' operate
          in place - it always produces a new object, even if no changes
          were made.

     在 3.9 版被加入.

 -- 方法: bytes.removesuffix (suffix, /)
 -- 方法: bytearray.removesuffix (suffix, /)

     If the binary data ends with the 'suffix' string and that 'suffix'
     is not empty, return ‘bytes[:-len(suffix)]’.  Otherwise, return a
     copy of the original binary data:

          >>> b'MiscTests'.removesuffix(b'Tests')
          b'Misc'
          >>> b'TmpDirMixin'.removesuffix(b'Tests')
          b'TmpDirMixin'

     The 'suffix' may be any *note bytes-like object: cd4.

          備註: The bytearray version of this method does 'not' operate
          in place - it always produces a new object, even if no changes
          were made.

     在 3.9 版被加入.

 -- 方法: bytes.decode (encoding='utf-8', errors='strict')
 -- 方法: bytearray.decode (encoding='utf-8', errors='strict')

     Return the bytes decoded to a *note str: 3f2.

     'encoding' defaults to ‘'utf-8'’; see *note Standard Encodings:
     d5f. for possible values.

     'errors' controls how decoding errors are handled.  If ‘'strict'’
     (the default), a *note UnicodeError: 123a. exception is raised.
     Other possible values are ‘'ignore'’, ‘'replace'’, and any other
     name registered via *note codecs.register_error(): 1404.  See *note
     Error Handlers: 16eb. for details.

     For performance reasons, the value of 'errors' is not checked for
     validity unless a decoding error actually occurs, *note Python
     開發模式: 1dd. is enabled or a *note debug build: 1de. is used.

          備註: Passing the 'encoding' argument to *note str: 3f2.
          allows decoding any *note bytes-like object: cd4. directly,
          without needing to make a temporary ‘bytes’ or ‘bytearray’
          object.

     在 3.1 版的變更: 新增關鍵字引數的支援。

     在 3.9 版的變更: The value of the 'errors' argument is now checked
     in *note Python 開發模式: 1dd. and in *note debug mode: 1de.

 -- 方法: bytes.endswith (suffix[, start[, end]])
 -- 方法: bytearray.endswith (suffix[, start[, end]])

     Return ‘True’ if the binary data ends with the specified 'suffix',
     otherwise return ‘False’.  'suffix' can also be a tuple of suffixes
     to look for.  With optional 'start', test beginning at that
     position.  With optional 'end', stop comparing at that position.

     The suffix(es) to search for may be any *note bytes-like object:
     cd4.

 -- 方法: bytes.find (sub[, start[, end]])
 -- 方法: bytearray.find (sub[, start[, end]])

     Return the lowest index in the data where the subsequence 'sub' is
     found, such that 'sub' is contained in the slice ‘s[start:end]’.
     Optional arguments 'start' and 'end' are interpreted as in slice
     notation.  Return ‘-1’ if 'sub' is not found.

     The subsequence to search for may be any *note bytes-like object:
     cd4. or an integer in the range 0 to 255.

          備註: The *note find(): 1742. method should be used only if
          you need to know the position of 'sub'.  To check if 'sub' is
          a substring or not, use the *note in: 2c5. operator:

               >>> b'Py' in b'Python'
               True

     在 3.3 版的變更: Also accept an integer in the range 0 to 255 as
     the subsequence.

 -- 方法: bytes.index (sub[, start[, end]])
 -- 方法: bytearray.index (sub[, start[, end]])

     Like *note find(): 1742, but raise *note ValueError: 1e7. when the
     subsequence is not found.

     The subsequence to search for may be any *note bytes-like object:
     cd4. or an integer in the range 0 to 255.

     在 3.3 版的變更: Also accept an integer in the range 0 to 255 as
     the subsequence.

 -- 方法: bytes.join (iterable)
 -- 方法: bytearray.join (iterable)

     Return a bytes or bytearray object which is the concatenation of
     the binary data sequences in 'iterable'.  A *note TypeError: 4dd.
     will be raised if there are any values in 'iterable' that are not
     *note bytes-like objects: cd4, including *note str: 3f2. objects.
     The separator between elements is the contents of the bytes or
     bytearray object providing this method.

 -- 方法: static bytes.maketrans (from, to)
 -- 方法: static bytearray.maketrans (from, to)

     This static method returns a translation table usable for *note
     bytes.translate(): 20be. that will map each character in 'from'
     into the character at the same position in 'to'; 'from' and 'to'
     must both be *note bytes-like objects: cd4. and have the same
     length.

     在 3.1 版被加入.

 -- 方法: bytes.partition (sep)
 -- 方法: bytearray.partition (sep)

     Split the sequence at the first occurrence of 'sep', and return a
     3-tuple containing the part before the separator, the separator
     itself or its bytearray copy, and the part after the separator.  If
     the separator is not found, return a 3-tuple containing a copy of
     the original sequence, followed by two empty bytes or bytearray
     objects.

     The separator to search for may be any *note bytes-like object:
     cd4.

 -- 方法: bytes.replace (old, new[, count])
 -- 方法: bytearray.replace (old, new[, count])

     Return a copy of the sequence with all occurrences of subsequence
     'old' replaced by 'new'.  If the optional argument 'count' is
     given, only the first 'count' occurrences are replaced.

     The subsequence to search for and its replacement may be any *note
     bytes-like object: cd4.

          備註: The bytearray version of this method does 'not' operate
          in place - it always produces a new object, even if no changes
          were made.

 -- 方法: bytes.rfind (sub[, start[, end]])
 -- 方法: bytearray.rfind (sub[, start[, end]])

     Return the highest index in the sequence where the subsequence
     'sub' is found, such that 'sub' is contained within ‘s[start:end]’.
     Optional arguments 'start' and 'end' are interpreted as in slice
     notation.  Return ‘-1’ on failure.

     The subsequence to search for may be any *note bytes-like object:
     cd4. or an integer in the range 0 to 255.

     在 3.3 版的變更: Also accept an integer in the range 0 to 255 as
     the subsequence.

 -- 方法: bytes.rindex (sub[, start[, end]])
 -- 方法: bytearray.rindex (sub[, start[, end]])

     Like *note rfind(): 1743. but raises *note ValueError: 1e7. when
     the subsequence 'sub' is not found.

     The subsequence to search for may be any *note bytes-like object:
     cd4. or an integer in the range 0 to 255.

     在 3.3 版的變更: Also accept an integer in the range 0 to 255 as
     the subsequence.

 -- 方法: bytes.rpartition (sep)
 -- 方法: bytearray.rpartition (sep)

     Split the sequence at the last occurrence of 'sep', and return a
     3-tuple containing the part before the separator, the separator
     itself or its bytearray copy, and the part after the separator.  If
     the separator is not found, return a 3-tuple containing two empty
     bytes or bytearray objects, followed by a copy of the original
     sequence.

     The separator to search for may be any *note bytes-like object:
     cd4.

 -- 方法: bytes.startswith (prefix[, start[, end]])
 -- 方法: bytearray.startswith (prefix[, start[, end]])

     Return ‘True’ if the binary data starts with the specified
     'prefix', otherwise return ‘False’.  'prefix' can also be a tuple
     of prefixes to look for.  With optional 'start', test beginning at
     that position.  With optional 'end', stop comparing at that
     position.

     The prefix(es) to search for may be any *note bytes-like object:
     cd4.

 -- 方法: bytes.translate (table, /, delete=b'')
 -- 方法: bytearray.translate (table, /, delete=b'')

     Return a copy of the bytes or bytearray object where all bytes
     occurring in the optional argument 'delete' are removed, and the
     remaining bytes have been mapped through the given translation
     table, which must be a bytes object of length 256.

     You can use the *note bytes.maketrans(): 120d. method to create a
     translation table.

     Set the 'table' argument to ‘None’ for translations that only
     delete characters:

          >>> b'read this short text'.translate(None, b'aeiou')
          b'rd ths shrt txt'

     在 3.6 版的變更: 'delete' is now supported as a keyword argument.

The following methods on bytes and bytearray objects have default
behaviours that assume the use of ASCII compatible binary formats, but
can still be used with arbitrary binary data by passing appropriate
arguments.  Note that all of the bytearray methods in this section do
'not' operate in place, and instead produce new objects.

 -- 方法: bytes.center (width[, fillbyte])
 -- 方法: bytearray.center (width[, fillbyte])

     Return a copy of the object centered in a sequence of length
     'width'.  Padding is done using the specified 'fillbyte' (default
     is an ASCII space).  For *note bytes: 1a5. objects, the original
     sequence is returned if 'width' is less than or equal to ‘len(s)’.

          備註: The bytearray version of this method does 'not' operate
          in place - it always produces a new object, even if no changes
          were made.

 -- 方法: bytes.ljust (width[, fillbyte])
 -- 方法: bytearray.ljust (width[, fillbyte])

     Return a copy of the object left justified in a sequence of length
     'width'.  Padding is done using the specified 'fillbyte' (default
     is an ASCII space).  For *note bytes: 1a5. objects, the original
     sequence is returned if 'width' is less than or equal to ‘len(s)’.

          備註: The bytearray version of this method does 'not' operate
          in place - it always produces a new object, even if no changes
          were made.

 -- 方法: bytes.lstrip ([chars])
 -- 方法: bytearray.lstrip ([chars])

     Return a copy of the sequence with specified leading bytes removed.
     The 'chars' argument is a binary sequence specifying the set of
     byte values to be removed - the name refers to the fact this method
     is usually used with ASCII characters.  If omitted or ‘None’, the
     'chars' argument defaults to removing ASCII whitespace.  The
     'chars' argument is not a prefix; rather, all combinations of its
     values are stripped:

          >>> b'   spacious   '.lstrip()
          b'spacious   '
          >>> b'www.example.com'.lstrip(b'cmowz.')
          b'example.com'

     The binary sequence of byte values to remove may be any *note
     bytes-like object: cd4.  See *note removeprefix(): 20b3. for a
     method that will remove a single prefix string rather than all of a
     set of characters.  For example:

          >>> b'Arthur: three!'.lstrip(b'Arthur: ')
          b'ee!'
          >>> b'Arthur: three!'.removeprefix(b'Arthur: ')
          b'three!'

          備註: The bytearray version of this method does 'not' operate
          in place - it always produces a new object, even if no changes
          were made.

 -- 方法: bytes.rjust (width[, fillbyte])
 -- 方法: bytearray.rjust (width[, fillbyte])

     Return a copy of the object right justified in a sequence of length
     'width'.  Padding is done using the specified 'fillbyte' (default
     is an ASCII space).  For *note bytes: 1a5. objects, the original
     sequence is returned if 'width' is less than or equal to ‘len(s)’.

          備註: The bytearray version of this method does 'not' operate
          in place - it always produces a new object, even if no changes
          were made.

 -- 方法: bytes.rsplit (sep=None, maxsplit=-1)
 -- 方法: bytearray.rsplit (sep=None, maxsplit=-1)

     Split the binary sequence into subsequences of the same type, using
     'sep' as the delimiter string.  If 'maxsplit' is given, at most
     'maxsplit' splits are done, the 'rightmost' ones.  If 'sep' is not
     specified or ‘None’, any subsequence consisting solely of ASCII
     whitespace is a separator.  Except for splitting from the right,
     *note rsplit(): 20d3. behaves like *note split(): 20d4. which is
     described in detail below.

 -- 方法: bytes.rstrip ([chars])
 -- 方法: bytearray.rstrip ([chars])

     Return a copy of the sequence with specified trailing bytes
     removed.  The 'chars' argument is a binary sequence specifying the
     set of byte values to be removed - the name refers to the fact this
     method is usually used with ASCII characters.  If omitted or
     ‘None’, the 'chars' argument defaults to removing ASCII whitespace.
     The 'chars' argument is not a suffix; rather, all combinations of
     its values are stripped:

          >>> b'   spacious   '.rstrip()
          b'   spacious'
          >>> b'mississippi'.rstrip(b'ipz')
          b'mississ'

     The binary sequence of byte values to remove may be any *note
     bytes-like object: cd4.  See *note removesuffix(): 20b5. for a
     method that will remove a single suffix string rather than all of a
     set of characters.  For example:

          >>> b'Monty Python'.rstrip(b' Python')
          b'M'
          >>> b'Monty Python'.removesuffix(b' Python')
          b'Monty'

          備註: The bytearray version of this method does 'not' operate
          in place - it always produces a new object, even if no changes
          were made.

 -- 方法: bytes.split (sep=None, maxsplit=-1)
 -- 方法: bytearray.split (sep=None, maxsplit=-1)

     Split the binary sequence into subsequences of the same type, using
     'sep' as the delimiter string.  If 'maxsplit' is given and
     non-negative, at most 'maxsplit' splits are done (thus, the list
     will have at most ‘maxsplit+1’ elements).  If 'maxsplit' is not
     specified or is ‘-1’, then there is no limit on the number of
     splits (all possible splits are made).

     If 'sep' is given, consecutive delimiters are not grouped together
     and are deemed to delimit empty subsequences (for example,
     ‘b'1,,2'.split(b',')’ returns ‘[b'1', b'', b'2']’).  The 'sep'
     argument may consist of a multibyte sequence as a single delimiter.
     Splitting an empty sequence with a specified separator returns
     ‘[b'']’ or ‘[bytearray(b'')]’ depending on the type of object being
     split.  The 'sep' argument may be any *note bytes-like object: cd4.

     舉例來說：

          >>> b'1,2,3'.split(b',')
          [b'1', b'2', b'3']
          >>> b'1,2,3'.split(b',', maxsplit=1)
          [b'1', b'2,3']
          >>> b'1,2,,3,'.split(b',')
          [b'1', b'2', b'', b'3', b'']
          >>> b'1<>2<>3<4'.split(b'<>')
          [b'1', b'2', b'3<4']

     If 'sep' is not specified or is ‘None’, a different splitting
     algorithm is applied: runs of consecutive ASCII whitespace are
     regarded as a single separator, and the result will contain no
     empty strings at the start or end if the sequence has leading or
     trailing whitespace.  Consequently, splitting an empty sequence or
     a sequence consisting solely of ASCII whitespace without a
     specified separator returns ‘[]’.

     舉例來說：

          >>> b'1 2 3'.split()
          [b'1', b'2', b'3']
          >>> b'1 2 3'.split(maxsplit=1)
          [b'1', b'2 3']
          >>> b'   1   2   3   '.split()
          [b'1', b'2', b'3']

 -- 方法: bytes.strip ([chars])
 -- 方法: bytearray.strip ([chars])

     Return a copy of the sequence with specified leading and trailing
     bytes removed.  The 'chars' argument is a binary sequence
     specifying the set of byte values to be removed - the name refers
     to the fact this method is usually used with ASCII characters.  If
     omitted or ‘None’, the 'chars' argument defaults to removing ASCII
     whitespace.  The 'chars' argument is not a prefix or suffix;
     rather, all combinations of its values are stripped:

          >>> b'   spacious   '.strip()
          b'spacious'
          >>> b'www.example.com'.strip(b'cmowz.')
          b'example'

     The binary sequence of byte values to remove may be any *note
     bytes-like object: cd4.

          備註: The bytearray version of this method does 'not' operate
          in place - it always produces a new object, even if no changes
          were made.

The following methods on bytes and bytearray objects assume the use of
ASCII compatible binary formats and should not be applied to arbitrary
binary data.  Note that all of the bytearray methods in this section do
'not' operate in place, and instead produce new objects.

 -- 方法: bytes.capitalize ()
 -- 方法: bytearray.capitalize ()

     Return a copy of the sequence with each byte interpreted as an
     ASCII character, and the first byte capitalized and the rest
     lowercased.  Non-ASCII byte values are passed through unchanged.

          備註: The bytearray version of this method does 'not' operate
          in place - it always produces a new object, even if no changes
          were made.

 -- 方法: bytes.expandtabs (tabsize=8)
 -- 方法: bytearray.expandtabs (tabsize=8)

     Return a copy of the sequence where all ASCII tab characters are
     replaced by one or more ASCII spaces, depending on the current
     column and the given tab size.  Tab positions occur every 'tabsize'
     bytes (default is 8, giving tab positions at columns 0, 8, 16 and
     so on).  To expand the sequence, the current column is set to zero
     and the sequence is examined byte by byte.  If the byte is an ASCII
     tab character (‘b'\t'’), one or more space characters are inserted
     in the result until the current column is equal to the next tab
     position.  (The tab character itself is not copied.)  If the
     current byte is an ASCII newline (‘b'\n'’) or carriage return
     (‘b'\r'’), it is copied and the current column is reset to zero.
     Any other byte value is copied unchanged and the current column is
     incremented by one regardless of how the byte value is represented
     when printed:

          >>> b'01\t012\t0123\t01234'.expandtabs()
          b'01      012     0123    01234'
          >>> b'01\t012\t0123\t01234'.expandtabs(4)
          b'01  012 0123    01234'

          備註: The bytearray version of this method does 'not' operate
          in place - it always produces a new object, even if no changes
          were made.

 -- 方法: bytes.isalnum ()
 -- 方法: bytearray.isalnum ()

     Return ‘True’ if all bytes in the sequence are alphabetical ASCII
     characters or ASCII decimal digits and the sequence is not empty,
     ‘False’ otherwise.  Alphabetic ASCII characters are those byte
     values in the sequence
     ‘b'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ'’.  ASCII
     decimal digits are those byte values in the sequence
     ‘b'0123456789'’.

     舉例來說：

          >>> b'ABCabc1'.isalnum()
          True
          >>> b'ABC abc1'.isalnum()
          False

 -- 方法: bytes.isalpha ()
 -- 方法: bytearray.isalpha ()

     Return ‘True’ if all bytes in the sequence are alphabetic ASCII
     characters and the sequence is not empty, ‘False’ otherwise.
     Alphabetic ASCII characters are those byte values in the sequence
     ‘b'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ'’.

     舉例來說：

          >>> b'ABCabc'.isalpha()
          True
          >>> b'ABCabc1'.isalpha()
          False

 -- 方法: bytes.isascii ()
 -- 方法: bytearray.isascii ()

     Return ‘True’ if the sequence is empty or all bytes in the sequence
     are ASCII, ‘False’ otherwise.  ASCII bytes are in the range 0-0x7F.

     在 3.7 版被加入.

 -- 方法: bytes.isdigit ()
 -- 方法: bytearray.isdigit ()

     Return ‘True’ if all bytes in the sequence are ASCII decimal digits
     and the sequence is not empty, ‘False’ otherwise.  ASCII decimal
     digits are those byte values in the sequence ‘b'0123456789'’.

     舉例來說：

          >>> b'1234'.isdigit()
          True
          >>> b'1.23'.isdigit()
          False

 -- 方法: bytes.islower ()
 -- 方法: bytearray.islower ()

     Return ‘True’ if there is at least one lowercase ASCII character in
     the sequence and no uppercase ASCII characters, ‘False’ otherwise.

     舉例來說：

          >>> b'hello world'.islower()
          True
          >>> b'Hello world'.islower()
          False

     Lowercase ASCII characters are those byte values in the sequence
     ‘b'abcdefghijklmnopqrstuvwxyz'’.  Uppercase ASCII characters are
     those byte values in the sequence ‘b'ABCDEFGHIJKLMNOPQRSTUVWXYZ'’.

 -- 方法: bytes.isspace ()
 -- 方法: bytearray.isspace ()

     Return ‘True’ if all bytes in the sequence are ASCII whitespace and
     the sequence is not empty, ‘False’ otherwise.  ASCII whitespace
     characters are those byte values in the sequence ‘b' \t\n\r\x0b\f'’
     (space, tab, newline, carriage return, vertical tab, form feed).

 -- 方法: bytes.istitle ()
 -- 方法: bytearray.istitle ()

     Return ‘True’ if the sequence is ASCII titlecase and the sequence
     is not empty, ‘False’ otherwise.  See *note bytes.title(): 20ec.
     for more details on the definition of "titlecase".

     舉例來說：

          >>> b'Hello World'.istitle()
          True
          >>> b'Hello world'.istitle()
          False

 -- 方法: bytes.isupper ()
 -- 方法: bytearray.isupper ()

     Return ‘True’ if there is at least one uppercase alphabetic ASCII
     character in the sequence and no lowercase ASCII characters,
     ‘False’ otherwise.

     舉例來說：

          >>> b'HELLO WORLD'.isupper()
          True
          >>> b'Hello world'.isupper()
          False

     Lowercase ASCII characters are those byte values in the sequence
     ‘b'abcdefghijklmnopqrstuvwxyz'’.  Uppercase ASCII characters are
     those byte values in the sequence ‘b'ABCDEFGHIJKLMNOPQRSTUVWXYZ'’.

 -- 方法: bytes.lower ()
 -- 方法: bytearray.lower ()

     Return a copy of the sequence with all the uppercase ASCII
     characters converted to their corresponding lowercase counterpart.

     舉例來說：

          >>> b'Hello World'.lower()
          b'hello world'

     Lowercase ASCII characters are those byte values in the sequence
     ‘b'abcdefghijklmnopqrstuvwxyz'’.  Uppercase ASCII characters are
     those byte values in the sequence ‘b'ABCDEFGHIJKLMNOPQRSTUVWXYZ'’.

          備註: The bytearray version of this method does 'not' operate
          in place - it always produces a new object, even if no changes
          were made.

 -- 方法: bytes.splitlines (keepends=False)
 -- 方法: bytearray.splitlines (keepends=False)

     Return a list of the lines in the binary sequence, breaking at
     ASCII line boundaries.  This method uses the *note universal
     newlines: ce1. approach to splitting lines.  Line breaks are not
     included in the resulting list unless 'keepends' is given and true.

     舉例來說：

          >>> b'ab c\n\nde fg\rkl\r\n'.splitlines()
          [b'ab c', b'', b'de fg', b'kl']
          >>> b'ab c\n\nde fg\rkl\r\n'.splitlines(keepends=True)
          [b'ab c\n', b'\n', b'de fg\r', b'kl\r\n']

     Unlike *note split(): 20d7. when a delimiter string 'sep' is given,
     this method returns an empty list for the empty string, and a
     terminal line break does not result in an extra line:

          >>> b"".split(b'\n'), b"Two lines\n".split(b'\n')
          ([b''], [b'Two lines', b''])
          >>> b"".splitlines(), b"One line\n".splitlines()
          ([], [b'One line'])

 -- 方法: bytes.swapcase ()
 -- 方法: bytearray.swapcase ()

     Return a copy of the sequence with all the lowercase ASCII
     characters converted to their corresponding uppercase counterpart
     and vice-versa.

     舉例來說：

          >>> b'Hello World'.swapcase()
          b'hELLO wORLD'

     Lowercase ASCII characters are those byte values in the sequence
     ‘b'abcdefghijklmnopqrstuvwxyz'’.  Uppercase ASCII characters are
     those byte values in the sequence ‘b'ABCDEFGHIJKLMNOPQRSTUVWXYZ'’.

     Unlike *note str.swapcase(): 20a6, it is always the case that
     ‘bin.swapcase().swapcase() == bin’ for the binary versions.  Case
     conversions are symmetrical in ASCII, even though that is not
     generally true for arbitrary Unicode code points.

          備註: The bytearray version of this method does 'not' operate
          in place - it always produces a new object, even if no changes
          were made.

 -- 方法: bytes.title ()
 -- 方法: bytearray.title ()

     Return a titlecased version of the binary sequence where words
     start with an uppercase ASCII character and the remaining
     characters are lowercase.  Uncased byte values are left unmodified.

     舉例來說：

          >>> b'Hello world'.title()
          b'Hello World'

     Lowercase ASCII characters are those byte values in the sequence
     ‘b'abcdefghijklmnopqrstuvwxyz'’.  Uppercase ASCII characters are
     those byte values in the sequence ‘b'ABCDEFGHIJKLMNOPQRSTUVWXYZ'’.
     All other byte values are uncased.

     The algorithm uses a simple language-independent definition of a
     word as groups of consecutive letters.  The definition works in
     many contexts but it means that apostrophes in contractions and
     possessives form word boundaries, which may not be the desired
     result:

          >>> b"they're bill's friends from the UK".title()
          b"They'Re Bill'S Friends From The Uk"

     A workaround for apostrophes can be constructed using regular
     expressions:

          >>> import re
          >>> def titlecase(s):
          ...     return re.sub(rb"[A-Za-z]+('[A-Za-z]+)?",
          ...                   lambda mo: mo.group(0)[0:1].upper() +
          ...                              mo.group(0)[1:].lower(),
          ...                   s)
          ...
          >>> titlecase(b"they're bill's friends.")
          b"They're Bill's Friends."

          備註: The bytearray version of this method does 'not' operate
          in place - it always produces a new object, even if no changes
          were made.

 -- 方法: bytes.upper ()
 -- 方法: bytearray.upper ()

     Return a copy of the sequence with all the lowercase ASCII
     characters converted to their corresponding uppercase counterpart.

     舉例來說：

          >>> b'Hello World'.upper()
          b'HELLO WORLD'

     Lowercase ASCII characters are those byte values in the sequence
     ‘b'abcdefghijklmnopqrstuvwxyz'’.  Uppercase ASCII characters are
     those byte values in the sequence ‘b'ABCDEFGHIJKLMNOPQRSTUVWXYZ'’.

          備註: The bytearray version of this method does 'not' operate
          in place - it always produces a new object, even if no changes
          were made.

 -- 方法: bytes.zfill (width)
 -- 方法: bytearray.zfill (width)

     Return a copy of the sequence left filled with ASCII ‘b'0'’ digits
     to make a sequence of length 'width'.  A leading sign prefix
     (‘b'+'’/ ‘b'-'’) is handled by inserting the padding 'after' the
     sign character rather than before.  For *note bytes: 1a5. objects,
     the original sequence is returned if 'width' is less than or equal
     to ‘len(seq)’.

     舉例來說：

          >>> b"42".zfill(5)
          b'00042'
          >>> b"-42".zfill(5)
          b'-0042'

          備註: The bytearray version of this method does 'not' operate
          in place - it always produces a new object, even if no changes
          were made.


File: python.info,  Node: printf-style Bytes Formatting,  Next: Memory Views,  Prev: Bytes and Bytearray Operations,  Up: Binary Sequence Types --- bytes bytearray memoryview

5.4.9.4 ‘printf’-style Bytes Formatting
.......................................

     備註: The formatting operations described here exhibit a variety of
     quirks that lead to a number of common errors (such as failing to
     display tuples and dictionaries correctly).  If the value being
     printed may be a tuple or dictionary, wrap it in a tuple.

Bytes objects (‘bytes’/‘bytearray’) have one unique built-in operation:
the ‘%’ operator (modulo).  This is also known as the bytes 'formatting'
or 'interpolation' operator.  Given ‘format % values’ (where 'format' is
a bytes object), ‘%’ conversion specifications in 'format' are replaced
with zero or more elements of 'values'.  The effect is similar to using
the ‘sprintf()’ in the C language.

If 'format' requires a single argument, 'values' may be a single
non-tuple object.  (1)  Otherwise, 'values' must be a tuple with exactly
the number of items specified by the format bytes object, or a single
mapping object (for example, a dictionary).

A conversion specifier contains two or more characters and has the
following components, which must occur in this order:

  1. The ‘'%'’ character, which marks the start of the specifier.

  2. Mapping key (optional), consisting of a parenthesised sequence of
     characters (for example, ‘(somename)’).

  3. Conversion flags (optional), which affect the result of some
     conversion types.

  4. Minimum field width (optional).  If specified as an ‘'*'’
     (asterisk), the actual width is read from the next element of the
     tuple in 'values', and the object to convert comes after the
     minimum field width and optional precision.

  5. Precision (optional), given as a ‘'.'’ (dot) followed by the
     precision.  If specified as ‘'*'’ (an asterisk), the actual
     precision is read from the next element of the tuple in 'values',
     and the value to convert comes after the precision.

  6. Length modifier (optional).

  7. Conversion type.

When the right argument is a dictionary (or other mapping type), then
the formats in the bytes object 'must' include a parenthesised mapping
key into that dictionary inserted immediately after the ‘'%'’ character.
The mapping key selects the value to be formatted from the mapping.  For
example:

     >>> print(b'%(language)s has %(number)03d quote types.' %
     ...       {b'language': b"Python", b"number": 2})
     b'Python has 002 quote types.'

In this case no ‘*’ specifiers may occur in a format (since they require
a sequential parameter list).

The conversion flag characters are:

Flag          含義
              
----------------------------------------------------------------------------------------
              
‘'#'’         The value conversion will use the "alternate form" (where defined
              below).
              
              
‘'0'’         The conversion will be zero padded for numeric values.
              
              
‘'-'’         The converted value is left adjusted (overrides the ‘'0'’ conversion if
              both are given).
              
              
‘' '’         (a space) A blank should be left before a positive number (or empty
              string) produced by a signed conversion.
              
              
‘'+'’         A sign character (‘'+'’ or ‘'-'’) will precede the conversion
              (overrides a "space" flag).
              

A length modifier (‘h’, ‘l’, or ‘L’) may be present, but is ignored as
it is not necessary for Python - so e.g.  ‘%ld’ is identical to ‘%d’.

The conversion types are:

Conversion       含義                                                      註解
                                                                           
---------------------------------------------------------------------------------------
                                                                           
‘'d'’            Signed integer decimal.
                 
                                                                           
‘'i'’            Signed integer decimal.
                 
                                                                           
‘'o'’            Signed octal value.                                       (1)
                                                                           
                                                                           
‘'u'’            Obsolete type - it is identical to ‘'d'’.                 (8)
                                                                           
                                                                           
‘'x'’            Signed hexadecimal (lowercase).                           (2)
                                                                           
                                                                           
‘'X'’            Signed hexadecimal (uppercase).                           (2)
                                                                           
                                                                           
‘'e'’            Floating-point exponential format (lowercase).            (3)
                                                                           
                                                                           
‘'E'’            Floating-point exponential format (uppercase).            (3)
                                                                           
                                                                           
‘'f'’            Floating-point decimal format.                            (3)
                                                                           
                                                                           
‘'F'’            Floating-point decimal format.                            (3)
                                                                           
                                                                           
‘'g'’            Floating-point format.  Uses lowercase exponential        (4)
                 format if exponent is less than -4 or not less than       
                 precision, decimal format otherwise.
                 
                                                                           
‘'G'’            Floating-point format.  Uses uppercase exponential        (4)
                 format if exponent is less than -4 or not less than       
                 precision, decimal format otherwise.
                 
                                                                           
‘'c'’            Single byte (accepts integer or single byte objects).
                 
                                                                           
‘'b'’            Bytes (any object that follows the                        (5)
                 *note buffer protocol: 367. or has                        
                 *note __bytes__(): 58e.).
                 
                                                                           
‘'s'’            ‘'s'’ is an alias for ‘'b'’ and should only be used for   (6)
                 Python2/3 code bases.                                     
                 
                                                                           
‘'a'’            Bytes (converts any Python object using                   (5)
                 ‘repr(obj).encode('ascii', 'backslashreplace')’).         
                 
                                                                           
‘'r'’            ‘'r'’ is an alias for ‘'a'’ and should only be used for   (7)
                 Python2/3 code bases.                                     
                 
                                                                           
‘'%'’            No argument is converted, results in a ‘'%'’ character
                 in the result.
                 

註解：

  1. The alternate form causes a leading octal specifier (‘'0o'’) to be
     inserted before the first digit.

  2. The alternate form causes a leading ‘'0x'’ or ‘'0X'’ (depending on
     whether the ‘'x'’ or ‘'X'’ format was used) to be inserted before
     the first digit.

  3. The alternate form causes the result to always contain a decimal
     point, even if no digits follow it.

     The precision determines the number of digits after the decimal
     point and defaults to 6.

  4. The alternate form causes the result to always contain a decimal
     point, and trailing zeroes are not removed as they would otherwise
     be.

     The precision determines the number of significant digits before
     and after the decimal point and defaults to 6.

  5. If precision is ‘N’, the output is truncated to ‘N’ characters.

  6. ‘b'%s'’ is deprecated, but will not be removed during the 3.x
     series.

  7. ‘b'%r'’ is deprecated, but will not be removed during the 3.x
     series.

  8. 參閱 PEP 237(2)。

     備註: The bytearray version of this method does 'not' operate in
     place - it always produces a new object, even if no changes were
     made.

也參考
......

PEP 461(3) - Adding % formatting to bytes and bytearray

在 3.5 版被加入.

   ---------- Footnotes ----------

   (1) To format only a tuple you should therefore provide a singleton
tuple whose only element is the tuple to be formatted.

   (2) https://peps.python.org/pep-0237/

   (3) https://peps.python.org/pep-0461/


File: python.info,  Node: Memory Views,  Prev: printf-style Bytes Formatting,  Up: Binary Sequence Types --- bytes bytearray memoryview

5.4.9.5 Memory Views
....................

*note memoryview: 40f. objects allow Python code to access the internal
data of an object that supports the *note buffer protocol: 367. without
copying.

 -- 類別: memoryview (object)

     Create a *note memoryview: 40f. that references 'object'.  'object'
     must support the buffer protocol.  Built-in objects that support
     the buffer protocol include *note bytes: 1a5. and *note bytearray:
     4e3.

     A *note memoryview: 40f. has the notion of an 'element', which is
     the atomic memory unit handled by the originating 'object'.  For
     many simple types such as *note bytes: 1a5. and *note bytearray:
     4e3, an element is a single byte, but other types such as *note
     array.array: 186. may have bigger elements.

     ‘len(view)’ is equal to the length of *note tolist: 20fc, which is
     the nested list representation of the view.  If ‘view.ndim = 1’,
     this is equal to the number of elements in the view.

     在 3.12 版的變更: If ‘view.ndim == 0’, ‘len(view)’ now raises *note
     TypeError: 4dd. instead of returning 1.

     The *note itemsize: 20fd. attribute will give you the number of
     bytes in a single element.

     A *note memoryview: 40f. supports slicing and indexing to expose
     its data.  One-dimensional slicing will result in a subview:

          >>> v = memoryview(b'abcefg')
          >>> v[1]
          98
          >>> v[-1]
          103
          >>> v[1:4]
          <memory at 0x7f3ddc9f4350>
          >>> bytes(v[1:4])
          b'bce'

     If *note format: 20fe. is one of the native format specifiers from
     the *note struct: c0. module, indexing with an integer or a tuple
     of integers is also supported and returns a single 'element' with
     the correct type.  One-dimensional memoryviews can be indexed with
     an integer or a one-integer tuple.  Multi-dimensional memoryviews
     can be indexed with tuples of exactly 'ndim' integers where 'ndim'
     is the number of dimensions.  Zero-dimensional memoryviews can be
     indexed with the empty tuple.

     Here is an example with a non-byte format:

          >>> import array
          >>> a = array.array('l', [-11111111, 22222222, -33333333, 44444444])
          >>> m = memoryview(a)
          >>> m[0]
          -11111111
          >>> m[-1]
          44444444
          >>> m[::2].tolist()
          [-11111111, -33333333]

     If the underlying object is writable, the memoryview supports
     one-dimensional slice assignment.  Resizing is not allowed:

          >>> data = bytearray(b'abcefg')
          >>> v = memoryview(data)
          >>> v.readonly
          False
          >>> v[0] = ord(b'z')
          >>> data
          bytearray(b'zbcefg')
          >>> v[1:4] = b'123'
          >>> data
          bytearray(b'z123fg')
          >>> v[2:3] = b'spam'
          Traceback (most recent call last):
            File "<stdin>", line 1, in <module>
          ValueError: memoryview assignment: lvalue and rvalue have different structures
          >>> v[2:6] = b'spam'
          >>> data
          bytearray(b'z1spam')

     One-dimensional memoryviews of *note hashable: 5b5. (read-only)
     types with formats 'B', 'b' or 'c' are also hashable.  The hash is
     defined as ‘hash(m) == hash(m.tobytes())’:

          >>> v = memoryview(b'abcefg')
          >>> hash(v) == hash(b'abcefg')
          True
          >>> hash(v[2:4]) == hash(b'ce')
          True
          >>> hash(v[::-2]) == hash(b'abcefg'[::-2])
          True

     在 3.3 版的變更: One-dimensional memoryviews can now be sliced.
     One-dimensional memoryviews with formats 'B', 'b' or 'c' are now
     *note hashable: 5b5.

     在 3.4 版的變更: memoryview is now registered automatically with
     *note collections.abc.Sequence: 115c.

     在 3.5 版的變更: memoryviews can now be indexed with tuple of
     integers.

     *note memoryview: 40f. has several methods:

      -- 方法: __eq__ (exporter)

          A memoryview and a PEP 3118(1) exporter are equal if their
          shapes are equivalent and if all corresponding values are
          equal when the operands' respective format codes are
          interpreted using *note struct: c0. syntax.

          For the subset of *note struct: c0. format strings currently
          supported by *note tolist(): 20fc, ‘v’ and ‘w’ are equal if
          ‘v.tolist() == w.tolist()’:

               >>> import array
               >>> a = array.array('I', [1, 2, 3, 4, 5])
               >>> b = array.array('d', [1.0, 2.0, 3.0, 4.0, 5.0])
               >>> c = array.array('b', [5, 3, 1])
               >>> x = memoryview(a)
               >>> y = memoryview(b)
               >>> x == a == y == b
               True
               >>> x.tolist() == a.tolist() == y.tolist() == b.tolist()
               True
               >>> z = y[::-2]
               >>> z == c
               True
               >>> z.tolist() == c.tolist()
               True

          If either format string is not supported by the *note struct:
          c0. module, then the objects will always compare as unequal
          (even if the format strings and buffer contents are
          identical):

               >>> from ctypes import BigEndianStructure, c_long
               >>> class BEPoint(BigEndianStructure):
               ...     _fields_ = [("x", c_long), ("y", c_long)]
               ...
               >>> point = BEPoint(100, 200)
               >>> a = memoryview(point)
               >>> b = memoryview(point)
               >>> a == point
               False
               >>> a == b
               False

          Note that, as with floating-point numbers, ‘v is w’ does 'not'
          imply ‘v == w’ for memoryview objects.

          在 3.3 版的變更: Previous versions compared the raw memory
          disregarding the item format and the logical array structure.

      -- 方法: tobytes (order='C')

          Return the data in the buffer as a bytestring.  This is
          equivalent to calling the *note bytes: 1a5. constructor on the
          memoryview.

               >>> m = memoryview(b"abc")
               >>> m.tobytes()
               b'abc'
               >>> bytes(m)
               b'abc'

          For non-contiguous arrays the result is equal to the flattened
          list representation with all elements converted to bytes.
          *note tobytes(): 2100. supports all format strings, including
          those that are not in *note struct: c0. module syntax.

          在 3.8 版被加入: 'order' can be {'C', 'F', 'A'}.  When 'order'
          is 'C' or 'F', the data of the original array is converted to
          C or Fortran order.  For contiguous views, 'A' returns an
          exact copy of the physical memory.  In particular, in-memory
          Fortran order is preserved.  For non-contiguous views, the
          data is converted to C first.  'order=None' is the same as
          'order='C".

      -- 方法: hex ([sep[, bytes_per_sep]])

          Return a string object containing two hexadecimal digits for
          each byte in the buffer.

               >>> m = memoryview(b"abc")
               >>> m.hex()
               '616263'

          在 3.5 版被加入.

          在 3.8 版的變更: Similar to *note bytes.hex(): d0f, *note
          memoryview.hex(): d11. now supports optional 'sep' and
          'bytes_per_sep' parameters to insert separators between bytes
          in the hex output.

      -- 方法: tolist ()

          Return the data in the buffer as a list of elements.

               >>> memoryview(b'abc').tolist()
               [97, 98, 99]
               >>> import array
               >>> a = array.array('d', [1.1, 2.2, 3.3])
               >>> m = memoryview(a)
               >>> m.tolist()
               [1.1, 2.2, 3.3]

          在 3.3 版的變更: *note tolist(): 20fc. now supports all single
          character native formats in *note struct: c0. module syntax as
          well as multi-dimensional representations.

      -- 方法: toreadonly ()

          Return a readonly version of the memoryview object.  The
          original memoryview object is unchanged.

               >>> m = memoryview(bytearray(b'abc'))
               >>> mm = m.toreadonly()
               >>> mm.tolist()
               [97, 98, 99]
               >>> mm[0] = 42
               Traceback (most recent call last):
                 File "<stdin>", line 1, in <module>
               TypeError: cannot modify read-only memory
               >>> m[0] = 43
               >>> mm.tolist()
               [43, 98, 99]

          在 3.8 版被加入.

      -- 方法: release ()

          Release the underlying buffer exposed by the memoryview
          object.  Many objects take special actions when a view is held
          on them (for example, a *note bytearray: 4e3. would
          temporarily forbid resizing); therefore, calling release() is
          handy to remove these restrictions (and free any dangling
          resources) as soon as possible.

          After this method has been called, any further operation on
          the view raises a *note ValueError: 1e7. (except *note
          release(): 1156. itself which can be called multiple times):

               >>> m = memoryview(b'abc')
               >>> m.release()
               >>> m[0]
               Traceback (most recent call last):
                 File "<stdin>", line 1, in <module>
               ValueError: operation forbidden on released memoryview object

          The context management protocol can be used for a similar
          effect, using the ‘with’ statement:

               >>> with memoryview(b'abc') as m:
               ...     m[0]
               ...
               97
               >>> m[0]
               Traceback (most recent call last):
                 File "<stdin>", line 1, in <module>
               ValueError: operation forbidden on released memoryview object

          在 3.2 版被加入.

      -- 方法: cast (format[, shape])

          Cast a memoryview to a new format or shape.  'shape' defaults
          to ‘[byte_length//new_itemsize]’, which means that the result
          view will be one-dimensional.  The return value is a new
          memoryview, but the buffer itself is not copied.  Supported
          casts are 1D -> C-*note contiguous: 2103. and C-contiguous ->
          1D.

          The destination format is restricted to a single element
          native format in *note struct: c0. syntax.  One of the formats
          must be a byte format ('B', 'b' or 'c').  The byte length of
          the result must be the same as the original length.  Note that
          all byte lengths may depend on the operating system.

          Cast 1D/long to 1D/unsigned bytes:

               >>> import array
               >>> a = array.array('l', [1,2,3])
               >>> x = memoryview(a)
               >>> x.format
               'l'
               >>> x.itemsize
               8
               >>> len(x)
               3
               >>> x.nbytes
               24
               >>> y = x.cast('B')
               >>> y.format
               'B'
               >>> y.itemsize
               1
               >>> len(y)
               24
               >>> y.nbytes
               24

          Cast 1D/unsigned bytes to 1D/char:

               >>> b = bytearray(b'zyz')
               >>> x = memoryview(b)
               >>> x[0] = b'a'
               Traceback (most recent call last):
                 ...
               TypeError: memoryview: invalid type for format 'B'
               >>> y = x.cast('c')
               >>> y[0] = b'a'
               >>> b
               bytearray(b'ayz')

          Cast 1D/bytes to 3D/ints to 1D/signed char:

               >>> import struct
               >>> buf = struct.pack("i"*12, *list(range(12)))
               >>> x = memoryview(buf)
               >>> y = x.cast('i', shape=[2,2,3])
               >>> y.tolist()
               [[[0, 1, 2], [3, 4, 5]], [[6, 7, 8], [9, 10, 11]]]
               >>> y.format
               'i'
               >>> y.itemsize
               4
               >>> len(y)
               2
               >>> y.nbytes
               48
               >>> z = y.cast('b')
               >>> z.format
               'b'
               >>> z.itemsize
               1
               >>> len(z)
               48
               >>> z.nbytes
               48

          Cast 1D/unsigned long to 2D/unsigned long:

               >>> buf = struct.pack("L"*6, *list(range(6)))
               >>> x = memoryview(buf)
               >>> y = x.cast('L', shape=[2,3])
               >>> len(y)
               2
               >>> y.nbytes
               48
               >>> y.tolist()
               [[0, 1, 2], [3, 4, 5]]

          在 3.3 版被加入.

          在 3.5 版的變更: The source format is no longer restricted
          when casting to a byte view.

     There are also several readonly attributes available:

      -- 屬性: obj

          The underlying object of the memoryview:

               >>> b  = bytearray(b'xyz')
               >>> m = memoryview(b)
               >>> m.obj is b
               True

          在 3.3 版被加入.

      -- 屬性: nbytes

          ‘nbytes == product(shape) * itemsize == len(m.tobytes())’.
          This is the amount of space in bytes that the array would use
          in a contiguous representation.  It is not necessarily equal
          to ‘len(m)’:

               >>> import array
               >>> a = array.array('i', [1,2,3,4,5])
               >>> m = memoryview(a)
               >>> len(m)
               5
               >>> m.nbytes
               20
               >>> y = m[::2]
               >>> len(y)
               3
               >>> y.nbytes
               12
               >>> len(y.tobytes())
               12

          Multi-dimensional arrays:

               >>> import struct
               >>> buf = struct.pack("d"*12, *[1.5*x for x in range(12)])
               >>> x = memoryview(buf)
               >>> y = x.cast('d', shape=[3,4])
               >>> y.tolist()
               [[0.0, 1.5, 3.0, 4.5], [6.0, 7.5, 9.0, 10.5], [12.0, 13.5, 15.0, 16.5]]
               >>> len(y)
               3
               >>> y.nbytes
               96

          在 3.3 版被加入.

      -- 屬性: readonly

          A bool indicating whether the memory is read only.

      -- 屬性: format

          A string containing the format (in *note struct: c0. module
          style) for each element in the view.  A memoryview can be
          created from exporters with arbitrary format strings, but some
          methods (e.g.  *note tolist(): 20fc.) are restricted to native
          single element formats.

          在 3.3 版的變更: format ‘'B'’ is now handled according to the
          struct module syntax.  This means that ‘memoryview(b'abc')[0]
          == b'abc'[0] == 97’.

      -- 屬性: itemsize

          The size in bytes of each element of the memoryview:

               >>> import array, struct
               >>> m = memoryview(array.array('H', [32000, 32001, 32002]))
               >>> m.itemsize
               2
               >>> m[0]
               32000
               >>> struct.calcsize('H') == m.itemsize
               True

      -- 屬性: ndim

          An integer indicating how many dimensions of a
          multi-dimensional array the memory represents.

      -- 屬性: shape

          A tuple of integers the length of *note ndim: 2107. giving the
          shape of the memory as an N-dimensional array.

          在 3.3 版的變更: An empty tuple instead of ‘None’ when ndim =
          0.

      -- 屬性: strides

          A tuple of integers the length of *note ndim: 2107. giving the
          size in bytes to access each element for each dimension of the
          array.

          在 3.3 版的變更: An empty tuple instead of ‘None’ when ndim =
          0.

      -- 屬性: suboffsets

          Used internally for PIL-style arrays.  The value is
          informational only.

      -- 屬性: c_contiguous

          A bool indicating whether the memory is C-*note contiguous:
          2103.

          在 3.3 版被加入.

      -- 屬性: f_contiguous

          A bool indicating whether the memory is Fortran *note
          contiguous: 2103.

          在 3.3 版被加入.

      -- 屬性: contiguous

          A bool indicating whether the memory is *note contiguous:
          2103.

          在 3.3 版被加入.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3118/


File: python.info,  Node: Set Types --- set frozenset,  Next: Mapping Types --- dict,  Prev: Binary Sequence Types --- bytes bytearray memoryview,  Up: 內建型別

5.4.10 Set Types -- ‘set’, ‘frozenset’
--------------------------------------

A 'set' object is an unordered collection of distinct *note hashable:
5b5. objects.  Common uses include membership testing, removing
duplicates from a sequence, and computing mathematical operations such
as intersection, union, difference, and symmetric difference.  (For
other containers see the built-in *note dict: 23b, *note list: 5b6, and
*note tuple: 322. classes, and the *note collections: 16. module.)

Like other collections, sets support ‘x in set’, ‘len(set)’, and ‘for x
in set’.  Being an unordered collection, sets do not record element
position or order of insertion.  Accordingly, sets do not support
indexing, slicing, or other sequence-like behavior.

There are currently two built-in set types, *note set: 57d. and *note
frozenset: 57e.  The *note set: 57d. type is mutable -- the contents can
be changed using methods like ‘add()’ and ‘remove()’.  Since it is
mutable, it has no hash value and cannot be used as either a dictionary
key or as an element of another set.  The *note frozenset: 57e. type is
immutable and *note hashable: 5b5. -- its contents cannot be altered
after it is created; it can therefore be used as a dictionary key or as
an element of another set.

Non-empty sets (not frozensets) can be created by placing a
comma-separated list of elements within braces, for example: ‘{'jack',
'sjoerd'}’, in addition to the *note set: 57d. constructor.

The constructors for both classes work the same:

 -- 類別: set ([iterable])
 -- 類別: frozenset ([iterable])

     Return a new set or frozenset object whose elements are taken from
     'iterable'.  The elements of a set must be *note hashable: 5b5.  To
     represent sets of sets, the inner sets must be *note frozenset:
     57e. objects.  If 'iterable' is not specified, a new empty set is
     returned.

     Sets can be created by several means:

        * Use a comma-separated list of elements within braces:
          ‘{'jack', 'sjoerd'}’

        * Use a set comprehension: ‘{c for c in 'abracadabra' if c not
          in 'abc'}’

        * Use the type constructor: ‘set()’, ‘set('foobar')’, ‘set(['a',
          'b', 'foo'])’

     Instances of *note set: 57d. and *note frozenset: 57e. provide the
     following operations:

      -- Describe: len(s)

          Return the number of elements in set 's' (cardinality of 's').

      -- Describe: x in s

          Test 'x' for membership in 's'.

      -- Describe: x not in s

          Test 'x' for non-membership in 's'.

      -- 方法: isdisjoint (other)

          Return ‘True’ if the set has no elements in common with
          'other'.  Sets are disjoint if and only if their intersection
          is the empty set.

      -- 方法: issubset (other)

      -- 方法: set <= other

          Test whether every element in the set is in 'other'.

      -- 方法: set < other

          Test whether the set is a proper subset of 'other', that is,
          ‘set <= other and set != other’.

      -- 方法: issuperset (other)

      -- 方法: set >= other

          Test whether every element in 'other' is in the set.

      -- 方法: set > other

          Test whether the set is a proper superset of 'other', that is,
          ‘set >= other and set != other’.

      -- 方法: union (*others)

      -- 方法: set | other | ...

          Return a new set with elements from the set and all others.

      -- 方法: intersection (*others)

      -- 方法: set & other & ...

          Return a new set with elements common to the set and all
          others.

      -- 方法: difference (*others)

      -- 方法: set - other - ...

          Return a new set with elements in the set that are not in the
          others.

      -- 方法: symmetric_difference (other)

      -- 方法: set ^ other

          Return a new set with elements in either the set or 'other'
          but not both.

      -- 方法: copy ()

          Return a shallow copy of the set.

     Note, the non-operator versions of *note union(): 13ec, *note
     intersection(): 13ed, *note difference(): 2112, *note
     symmetric_difference(): 2113, *note issubset(): 2110, and *note
     issuperset(): 2111. methods will accept any iterable as an
     argument.  In contrast, their operator based counterparts require
     their arguments to be sets.  This precludes error-prone
     constructions like ‘set('abc') & 'cbs'’ in favor of the more
     readable ‘set('abc').intersection('cbs')’.

     Both *note set: 57d. and *note frozenset: 57e. support set to set
     comparisons.  Two sets are equal if and only if every element of
     each set is contained in the other (each is a subset of the other).
     A set is less than another set if and only if the first set is a
     proper subset of the second set (is a subset, but is not equal).  A
     set is greater than another set if and only if the first set is a
     proper superset of the second set (is a superset, but is not
     equal).

     Instances of *note set: 57d. are compared to instances of *note
     frozenset: 57e. based on their members.  For example, ‘set('abc')
     == frozenset('abc')’ returns ‘True’ and so does ‘set('abc') in
     set([frozenset('abc')])’.

     The subset and equality comparisons do not generalize to a total
     ordering function.  For example, any two nonempty disjoint sets are
     not equal and are not subsets of each other, so 'all' of the
     following return ‘False’: ‘a<b’, ‘a==b’, or ‘a>b’.

     Since sets only define partial ordering (subset relationships), the
     output of the *note list.sort(): b76. method is undefined for lists
     of sets.

     Set elements, like dictionary keys, must be *note hashable: 5b5.

     Binary operations that mix *note set: 57d. instances with *note
     frozenset: 57e. return the type of the first operand.  For example:
     ‘frozenset('ab') | set('bc')’ returns an instance of *note
     frozenset: 57e.

     The following table lists operations available for *note set: 57d.
     that do not apply to immutable instances of *note frozenset: 57e.:

      -- 方法: update (*others)

      -- 方法: set |= other | ...

          Update the set, adding elements from all others.

      -- 方法: intersection_update (*others)

      -- 方法: set &= other & ...

          Update the set, keeping only elements found in it and all
          others.

      -- 方法: difference_update (*others)

      -- 方法: set -= other | ...

          Update the set, removing elements found in others.

      -- 方法: symmetric_difference_update (other)

      -- 方法: set ^= other

          Update the set, keeping only elements found in either set, but
          not in both.

      -- 方法: add (elem)

          Add element 'elem' to the set.

      -- 方法: remove (elem)

          Remove element 'elem' from the set.  Raises *note KeyError:
          2fb. if 'elem' is not contained in the set.

      -- 方法: discard (elem)

          Remove element 'elem' from the set if it is present.

      -- 方法: pop ()

          Remove and return an arbitrary element from the set.  Raises
          *note KeyError: 2fb. if the set is empty.

      -- 方法: clear ()

          Remove all elements from the set.

     Note, the non-operator versions of the *note update(): 2115, *note
     intersection_update(): 13ee, *note difference_update(): 2116, and
     *note symmetric_difference_update(): 13ef. methods will accept any
     iterable as an argument.

     Note, the 'elem' argument to the *note __contains__(): 1e33, *note
     remove(): 2118, and *note discard(): 2119. methods may be a set.
     To support searching for an equivalent frozenset, a temporary one
     is created from 'elem'.


File: python.info,  Node: Mapping Types --- dict,  Next: 情境管理器型別,  Prev: Set Types --- set frozenset,  Up: 內建型別

5.4.11 Mapping Types -- ‘dict’
------------------------------

A *note mapping: 1154. object maps *note hashable: 5b5. values to
arbitrary objects.  Mappings are mutable objects.  There is currently
only one standard mapping type, the 'dictionary'.  (For other containers
see the built-in *note list: 5b6, *note set: 57d, and *note tuple: 322.
classes, and the *note collections: 16. module.)

A dictionary's keys are 'almost' arbitrary values.  Values that are not
*note hashable: 5b5, that is, values containing lists, dictionaries or
other mutable types (that are compared by value rather than by object
identity) may not be used as keys.  Values that compare equal (such as
‘1’, ‘1.0’, and ‘True’) can be used interchangeably to index the same
dictionary entry.

 -- 類別: dict (**kwargs)

 -- 類別: dict (mapping, **kwargs)

 -- 類別: dict (iterable, **kwargs)

     Return a new dictionary initialized from an optional positional
     argument and a possibly empty set of keyword arguments.

     Dictionaries can be created by several means:

        * Use a comma-separated list of ‘key: value’ pairs within
          braces: ‘{'jack': 4098, 'sjoerd': 4127}’ or ‘{4098: 'jack',
          4127: 'sjoerd'}’

        * Use a dict comprehension: ‘{}’, ‘{x: x ** 2 for x in
          range(10)}’

        * Use the type constructor: ‘dict()’, ‘dict([('foo', 100),
          ('bar', 200)])’, ‘dict(foo=100, bar=200)’

     If no positional argument is given, an empty dictionary is created.
     If a positional argument is given and it is a mapping object, a
     dictionary is created with the same key-value pairs as the mapping
     object.  Otherwise, the positional argument must be an *note
     iterable: 11bf. object.  Each item in the iterable must itself be
     an iterable with exactly two objects.  The first object of each
     item becomes a key in the new dictionary, and the second object the
     corresponding value.  If a key occurs more than once, the last
     value for that key becomes the corresponding value in the new
     dictionary.

     If keyword arguments are given, the keyword arguments and their
     values are added to the dictionary created from the positional
     argument.  If a key being added is already present, the value from
     the keyword argument replaces the value from the positional
     argument.

     To illustrate, the following examples all return a dictionary equal
     to ‘{"one": 1, "two": 2, "three": 3}’:

          >>> a = dict(one=1, two=2, three=3)
          >>> b = {'one': 1, 'two': 2, 'three': 3}
          >>> c = dict(zip(['one', 'two', 'three'], [1, 2, 3]))
          >>> d = dict([('two', 2), ('one', 1), ('three', 3)])
          >>> e = dict({'three': 3, 'one': 1, 'two': 2})
          >>> f = dict({'one': 1, 'three': 3}, two=2)
          >>> a == b == c == d == e == f
          True

     Providing keyword arguments as in the first example only works for
     keys that are valid Python identifiers.  Otherwise, any valid keys
     can be used.

     These are the operations that dictionaries support (and therefore,
     custom mapping types should support too):

      -- Describe: list(d)

          Return a list of all the keys used in the dictionary 'd'.

      -- Describe: len(d)

          Return the number of items in the dictionary 'd'.

      -- Describe: d[key]

          Return the item of 'd' with key 'key'.  Raises a *note
          KeyError: 2fb. if 'key' is not in the map.

          If a subclass of dict defines a method ‘__missing__()’ and
          'key' is not present, the ‘d[key]’ operation calls that method
          with the key 'key' as argument.  The ‘d[key]’ operation then
          returns or raises whatever is returned or raised by the
          ‘__missing__(key)’ call.  No other operations or methods
          invoke ‘__missing__()’.  If ‘__missing__()’ is not defined,
          *note KeyError: 2fb. is raised.  ‘__missing__()’ must be a
          method; it cannot be an instance variable:

               >>> class Counter(dict):
               ...     def __missing__(self, key):
               ...         return 0
               ...
               >>> c = Counter()
               >>> c['red']
               0
               >>> c['red'] += 1
               >>> c['red']
               1

          The example above shows part of the implementation of *note
          collections.Counter: 1033.  A different ‘__missing__’ method
          is used by *note collections.defaultdict: 1155.

      -- Describe: d[key] = value

          Set ‘d[key]’ to 'value'.

      -- Describe: del d[key]

          Remove ‘d[key]’ from 'd'.  Raises a *note KeyError: 2fb. if
          'key' is not in the map.

      -- Describe: key in d

          Return ‘True’ if 'd' has a key 'key', else ‘False’.

      -- Describe: key not in d

          Equivalent to ‘not key in d’.

      -- Describe: iter(d)

          Return an iterator over the keys of the dictionary.  This is a
          shortcut for ‘iter(d.keys())’.

      -- 方法: clear ()

          Remove all items from the dictionary.

      -- 方法: copy ()

          Return a shallow copy of the dictionary.

      -- 方法: classmethod fromkeys (iterable, value=None, /)

          Create a new dictionary with keys from 'iterable' and values
          set to 'value'.

          *note fromkeys(): 211e. is a class method that returns a new
          dictionary.  'value' defaults to ‘None’.  All of the values
          refer to just a single instance, so it generally doesn't make
          sense for 'value' to be a mutable object such as an empty
          list.  To get distinct values, use a *note dict comprehension:
          d25. instead.

      -- 方法: get (key, default=None)

          Return the value for 'key' if 'key' is in the dictionary, else
          'default'.  If 'default' is not given, it defaults to ‘None’,
          so that this method never raises a *note KeyError: 2fb.

      -- 方法: items ()

          Return a new view of the dictionary's items (‘(key, value)’
          pairs).  See the *note documentation of view objects: 2120.

      -- 方法: keys ()

          Return a new view of the dictionary's keys.  See the *note
          documentation of view objects: 2120.

      -- 方法: pop (key[, default])

          If 'key' is in the dictionary, remove it and return its value,
          else return 'default'.  If 'default' is not given and 'key' is
          not in the dictionary, a *note KeyError: 2fb. is raised.

      -- 方法: popitem ()

          Remove and return a ‘(key, value)’ pair from the dictionary.
          Pairs are returned in LIFO (last-in, first-out) order.

          *note popitem(): 1495. is useful to destructively iterate over
          a dictionary, as often used in set algorithms.  If the
          dictionary is empty, calling *note popitem(): 1495. raises a
          *note KeyError: 2fb.

          在 3.7 版的變更: LIFO order is now guaranteed.  In prior
          versions, *note popitem(): 1495. would return an arbitrary
          key/value pair.

      -- Describe: reversed(d)

          Return a reverse iterator over the keys of the dictionary.
          This is a shortcut for ‘reversed(d.keys())’.

          在 3.8 版被加入.

      -- 方法: setdefault (key, default=None)

          If 'key' is in the dictionary, return its value.  If not,
          insert 'key' with a value of 'default' and return 'default'.
          'default' defaults to ‘None’.

      -- 方法: update ([other])

          Update the dictionary with the key/value pairs from 'other',
          overwriting existing keys.  Return ‘None’.

          *note update(): 13d0. accepts either another dictionary object
          or an iterable of key/value pairs (as tuples or other
          iterables of length two).  If keyword arguments are specified,
          the dictionary is then updated with those key/value pairs:
          ‘d.update(red=1, blue=2)’.

      -- 方法: values ()

          Return a new view of the dictionary's values.  See the *note
          documentation of view objects: 2120.

          An equality comparison between one ‘dict.values()’ view and
          another will always return ‘False’.  This also applies when
          comparing ‘dict.values()’ to itself:

               >>> d = {'a': 1}
               >>> d.values() == d.values()
               False

      -- Describe: d | other

          Create a new dictionary with the merged keys and values of 'd'
          and 'other', which must both be dictionaries.  The values of
          'other' take priority when 'd' and 'other' share keys.

          在 3.9 版被加入.

      -- Describe: d |= other

          Update the dictionary 'd' with keys and values from 'other',
          which may be either a *note mapping: 1154. or an *note
          iterable: 11bf. of key/value pairs.  The values of 'other'
          take priority when 'd' and 'other' share keys.

          在 3.9 版被加入.

     Dictionaries compare equal if and only if they have the same ‘(key,
     value)’ pairs (regardless of ordering).  Order comparisons ('<',
     '<=', '>=', '>') raise *note TypeError: 4dd.

     Dictionaries preserve insertion order.  Note that updating a key
     does not affect the order.  Keys added after deletion are inserted
     at the end.

          >>> d = {"one": 1, "two": 2, "three": 3, "four": 4}
          >>> d
          {'one': 1, 'two': 2, 'three': 3, 'four': 4}
          >>> list(d)
          ['one', 'two', 'three', 'four']
          >>> list(d.values())
          [1, 2, 3, 4]
          >>> d["one"] = 42
          >>> d
          {'one': 42, 'two': 2, 'three': 3, 'four': 4}
          >>> del d["two"]
          >>> d["two"] = None
          >>> d
          {'one': 42, 'three': 3, 'four': 4, 'two': None}

     在 3.7 版的變更: Dictionary order is guaranteed to be insertion
     order.  This behavior was an implementation detail of CPython from
     3.6.

     Dictionaries and dictionary views are reversible.

          >>> d = {"one": 1, "two": 2, "three": 3, "four": 4}
          >>> d
          {'one': 1, 'two': 2, 'three': 3, 'four': 4}
          >>> list(reversed(d))
          ['four', 'three', 'two', 'one']
          >>> list(reversed(d.values()))
          [4, 3, 2, 1]
          >>> list(reversed(d.items()))
          [('four', 4), ('three', 3), ('two', 2), ('one', 1)]

     在 3.8 版的變更: Dictionaries are now reversible.

也參考
......

*note types.MappingProxyType: 414. can be used to create a read-only
view of a *note dict: 23b.

* Menu:

* 字典視圖物件::


File: python.info,  Node: 字典視圖物件,  Up: Mapping Types --- dict

5.4.11.1 字典視圖物件
.....................

The objects returned by *note dict.keys(): 771, *note dict.values():
772. and *note dict.items(): 773. are 'view objects'.  They provide a
dynamic view on the dictionary's entries, which means that when the
dictionary changes, the view reflects these changes.

Dictionary views can be iterated over to yield their respective data,
and support membership tests:

 -- Describe: len(dictview)

     Return the number of entries in the dictionary.

 -- Describe: iter(dictview)

     Return an iterator over the keys, values or items (represented as
     tuples of ‘(key, value)’) in the dictionary.

     Keys and values are iterated over in insertion order.  This allows
     the creation of ‘(value, key)’ pairs using *note zip(): 774.:
     ‘pairs = zip(d.values(), d.keys())’.  Another way to create the
     same list is ‘pairs = [(v, k) for (k, v) in d.items()]’.

     Iterating views while adding or deleting entries in the dictionary
     may raise a *note RuntimeError: 179. or fail to iterate over all
     entries.

     在 3.7 版的變更: Dictionary order is guaranteed to be insertion
     order.

 -- Describe: x in dictview

     Return ‘True’ if 'x' is in the underlying dictionary's keys, values
     or items (in the latter case, 'x' should be a ‘(key, value)’
     tuple).

 -- Describe: reversed(dictview)

     Return a reverse iterator over the keys, values or items of the
     dictionary.  The view will be iterated in reverse order of the
     insertion.

     在 3.8 版的變更: Dictionary views are now reversible.

 -- Describe: dictview.mapping

     Return a *note types.MappingProxyType: 414. that wraps the original
     dictionary to which the view refers.

     在 3.10 版被加入.

Keys views are set-like since their entries are unique and *note
hashable: 5b5.  Items views also have set-like operations since the
(key, value) pairs are unique and the keys are hashable.  If all values
in an items view are hashable as well, then the items view can
interoperate with other sets.  (Values views are not treated as set-like
since the entries are generally not unique.)  For set-like views, all of
the operations defined for the abstract base class *note
collections.abc.Set: 2122. are available (for example, ‘==’, ‘<’, or
‘^’).  While using set operators, set-like views accept any iterable as
the other operand, unlike sets which only accept sets as the input.

An example of dictionary view usage:

     >>> dishes = {'eggs': 2, 'sausage': 1, 'bacon': 1, 'spam': 500}
     >>> keys = dishes.keys()
     >>> values = dishes.values()

     >>> # iteration
     >>> n = 0
     >>> for val in values:
     ...     n += val
     ...
     >>> print(n)
     504

     >>> # keys and values are iterated over in the same order (insertion order)
     >>> list(keys)
     ['eggs', 'sausage', 'bacon', 'spam']
     >>> list(values)
     [2, 1, 1, 500]

     >>> # view objects are dynamic and reflect dict changes
     >>> del dishes['eggs']
     >>> del dishes['sausage']
     >>> list(keys)
     ['bacon', 'spam']

     >>> # set operations
     >>> keys & {'eggs', 'bacon', 'salad'}
     {'bacon'}
     >>> keys ^ {'sausage', 'juice'} == {'juice', 'sausage', 'bacon', 'spam'}
     True
     >>> keys | ['juice', 'juice', 'juice'] == {'bacon', 'spam', 'juice'}
     True

     >>> # get back a read-only proxy for the original dictionary
     >>> values.mapping
     mappingproxy({'bacon': 1, 'spam': 500})
     >>> values.mapping['spam']
     500


File: python.info,  Node: 情境管理器型別,  Next: 型別註釋的型別 --- 泛型別名 Generic Alias 、聯合 Union,  Prev: Mapping Types --- dict,  Up: 內建型別

5.4.12 情境管理器型別
---------------------

Python 的 *note with: 577. 陳述式支援了由情境管理器定義之 runtime 情境的
概念，要使用兩個方法來實作，該方法讓使用者定義類別能夠去定義 runtime 情
境，且該情境在執行陳述式主體 (statement body) 之前進入、在陳述式結束時退
出：

 -- 方法: contextmanager.__enter__ ()

     輸入 runtime 情境並回傳此物件或者與 runtime 情境相關的另一個物件。
     此方法回傳的值有被綁定到使用此情境管理器的 *note with: 577. 陳述式
     的 ‘as’ 子句中的識別字。

     一個會回傳自己的情境管理器範例是 *note file object: 115b.。檔案物件
     從 __enter__() 回傳自己，以允許將 *note open(): 4c0. 用作 *note
     with: 577. 陳述式中的情境運算式。

     一個會回傳相關物件的情境管理器範例是由 *note
     decimal.localcontext(): 1709. 回傳的管理器。這些管理器將有效的十進
     位情境設定為原始十進位情境的副本，然後回傳該副本。這允許對 *note
     with: 577. 陳述式主體中的當前十進位情境進行更改，而不會影響 ‘with’
     陳述式外部的程式碼。

 -- 方法: contextmanager.__exit__ (exc_type, exc_val, exc_tb)

     退出 runtime 情境並回傳布林旗標以表示是否應抑制曾發生的任何例外。如
     果在執行 *note with: 577. 陳述式主體時發生例外，則引數包含例外型別
     、值和回溯 (traceback) 資訊。否則，所有三個引數都是 ‘None’。

     從此方法回傳 true 值將導致 *note with: 577. 陳述式抑制例外並繼續執
     行緊接著 ‘with’ 陳述式之後的陳述式。否則，該例外將在該方法執行完畢
     後繼續傳播 (propagate)。執行此方法期間發生的例外會取代 ‘with’ 陳述
     式主體中發生的任何例外。

     傳入的例外不應明確重新引發 - 取而代之的是，此方法應回傳 false 值以
     指示該方法已成功完成且不希望抑制引發的例外。這讓情境管理程式碼能輕
     鬆檢測 ‘__exit__()’ 方法是否曾實際失敗過。

Python 定義了多個情境管理器來支援簡單的執行緒同步、檔案或其他物件的提示
關閉以及對有效十進位算術情境的更簡單操作。除了情境管理協定的實作之外，不
會對特定型別進行特殊處理。更多範例請參閱 *note contextlib: 1c. 模組。

Python 的 *note generator: 1004. 和 *note contextlib.contextmanager:
119a. 裝飾器提供了一種便捷的方法來實作這些協定。如果產生器函式以 *note
contextlib.contextmanager: 119a. 裝飾器裝飾，它將回傳一個有實作出需要的
*note __enter__(): 2124. 和 *note __exit__(): 2125. 方法的情境管理器，而
不是由未裝飾產生器函式產生的疊代器。

請注意，Python/C API 中 Python 物件的型別結構中的任何方法都沒有特定的槽
。想要定義這些方法的擴充型別必須將它們作為普通的 Python 可存取方法提供。
與設定 runtime 情境的開銷相比，單一類別字典查找的開銷可以忽略不計。


File: python.info,  Node: 型別註釋的型別 --- 泛型別名 Generic Alias 、聯合 Union,  Next: Other Built-in Types,  Prev: 情境管理器型別,  Up: 內建型別

5.4.13 型別註釋的型別 -- 泛型別名 (Generic Alias)、聯合 (Union)
---------------------------------------------------------------

*note 型別註釋: 3fe. 的核心內建型別是*note 泛型別名: 656.和*note 聯合:
766.。

* Menu:

* 泛型別名型別::
* 聯合型別 (Union Type): 聯合型別 Union Type.


File: python.info,  Node: 泛型別名型別,  Next: 聯合型別 Union Type,  Up: 型別註釋的型別 --- 泛型別名 Generic Alias 、聯合 Union

5.4.13.1 泛型別名型別
.....................

‘GenericAlias’ 物件通常是透過*note 下標 (subscripting): 1e5b. 一個類別來
建立的。它們最常與*note 容器類別: 1e61. 一起使用，像是 *note list: 5b6.
或 *note dict: 23b.。例如 ‘list[int]’ 是一個''GenericAlias'' 物件，它是
透過使用引數 *note int: 23c. 來下標 ‘list’ 類別而建立的。‘GenericAlias’
物件主要會與*note 型別註釋: 3fe. 一起使用。

     備註: 通常只有當類別有實作特殊方法 *note __class_getitem__(): 6df.
     時才可以去下標該類別。

將一個 ‘GenericAlias’ 物件用作 *note generic type: 3df. 的代理，實作'參
數化泛型 (parameterized generics)'。

對於一個容器類別，提供給該類別的*note 下標: 1e5b.引數可以代表物件所包含
元素的型別。例如 ‘set[bytes]’ 可以用於型別註釋來表示一個 *note set:
57d.，其中所有元素的型別都是 *note bytes: 1a5.。

對於定義 *note __class_getitem__(): 6df. 但不是容器的類別，提供給該類別
的下標引數通常會指示物件上有定義的一個或多個方法的回傳型別。例如*note
正規表示式: a7.可以用於 *note str: 3f2. 和 *note bytes: 1a5. 資料型別：

   * 如果 ‘x = re.search('foo', 'foo')’，‘x’ 將會是一個 *note re.Match:
     f2a. 物件，其中 ‘x.group(0)’ 和 ‘x[0]’ 的回傳值都是 *note str: 3f2.
     型別。我們就可以用 ‘GenericAlias’ ‘re.Match[str]’ 在型別註釋中表示
     這種物件。

   * 如果 ‘y = re.search(b'bar', b'bar')’（注意 *note bytes: 1a5. 的
     ‘b’）， ‘y’ 也會是 ‘re.Match’ 的實例，但 ‘y.group(0)’ 和 ‘y[0]’ 的
     回傳值的型別都是 *note bytes: 1a5.。在型別註釋中，我們將用
     ‘re.Match[bytes]’ 來表示各種 *note re.Match: f2a. 物件。

‘GenericAlias’ 物件是 *note types.GenericAlias: 78f. 類別的實例，也可以
用來直接建立 ‘GenericAlias’ 物件。

 -- Describe: T[X, Y, ...]

     建立一個 ‘GenericAlias’ 來表示一個型別 ‘T’，其以型別 'X'、'Y' 等（
     取決於所使用的 ‘T’）來參數化。例如，一個函式需要一個包含 *note
     float: 2c8. 元素的 *note list: 5b6.：

          def average(values: list[float]) -> float:
              return sum(values) / len(values)

     *note 對映: 1154.物件的另一個範例，使用 *note dict: 23b.，它是一個
     泛型型別，需要兩個型別參數，分別表示鍵型別和值型別。在此範例中，函
     式需要一個 ‘dict’，其帶有 *note str: 3f2. 型別的鍵和 *note int:
     23c. 型別的值：

          def send_post_request(url: str, body: dict[str, int]) -> None:
              ...

內建函式 *note isinstance(): 3e8. 和 *note issubclass(): 765. 不接受
‘GenericAlias’ 型別作為第二個引數：

     >>> isinstance([1, 2], list[str])
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: isinstance() argument 2 cannot be a parameterized generic

Python runtime 不強制執行*note 型別註釋: 3fe.。這也擴展到泛型型別及其型
別參數。當從 ‘GenericAlias’ 建立容器物件時，不會檢查容器中元素的型別。例
如，不鼓勵使用以下程式碼，但 runtime 不會出現錯誤：

     >>> t = list[str]
     >>> t([1, 2, 3])
     [1, 2, 3]

此外，參數化泛型在物件建立期間會擦除 (erase) 型別參數：

     >>> t = list[str]
     >>> type(t)
     <class 'types.GenericAlias'>

     >>> l = t()
     >>> type(l)
     <class 'list'>

在泛型上呼叫 *note repr(): 7a1. 或 *note str(): 3f2. 會顯示參數化型別：

     >>> repr(list[int])
     'list[int]'

     >>> str(list[int])
     'list[int]'

為防止像是 ‘dict[str][str]’ 的錯誤出現，泛型容器的 *note __getitem__():
266. 方法會在這種情況下引發例外：

     >>> dict[str][str]
     Traceback (most recent call last):
       ...
     TypeError: dict[str] is not a generic class

然而當使用*note 型別變數 (type variable): 1e56. 時，此類運算式是有效的。
索引的元素數量必須與 ‘GenericAlias’ 物件的 *note __args__: 2128. 中的型
別變數項目一樣多：

     >>> from typing import TypeVar
     >>> Y = TypeVar('Y')
     >>> dict[str, Y][int]
     dict[str, int]

* Menu:

* 標準泛型類別::
* GenericAlias 物件的特殊屬性::


File: python.info,  Node: 標準泛型類別,  Next: GenericAlias 物件的特殊屬性,  Up: 泛型別名型別

5.4.13.2 標準泛型類別
.....................

以下標準函式庫類別有支援參數化泛型。此列表並非詳盡無遺。

   * *note tuple: 322.

   * *note list: 5b6.

   * *note dict: 23b.

   * *note set: 57d.

   * *note frozenset: 57e.

   * *note type: cef.

   * *note collections.deque: 580.

   * *note collections.defaultdict: 1155.

   * *note collections.OrderedDict: 57f.

   * *note collections.Counter: 1033.

   * *note collections.ChainMap: bc3.

   * *note collections.abc.Awaitable: d82.

   * *note collections.abc.Coroutine: d83.

   * *note collections.abc.AsyncIterable: d85.

   * *note collections.abc.AsyncIterator: d84.

   * *note collections.abc.AsyncGenerator: c31.

   * *note collections.abc.Iterable: 212a.

   * *note collections.abc.Iterator: 212b.

   * *note collections.abc.Generator: d81.

   * *note collections.abc.Reversible: c30.

   * *note collections.abc.Container: 212c.

   * *note collections.abc.Collection: c2f.

   * *note collections.abc.Callable: 78e.

   * *note collections.abc.Set: 2122.

   * *note collections.abc.MutableSet: 212d.

   * *note collections.abc.Mapping: 86f.

   * *note collections.abc.MutableMapping: 1048.

   * *note collections.abc.Sequence: 115c.

   * *note collections.abc.MutableSequence: 187.

   * *note collections.abc.ByteString: 2a4.

   * *note collections.abc.MappingView: 212e.

   * *note collections.abc.KeysView: 212f.

   * *note collections.abc.ItemsView: 2130.

   * *note collections.abc.ValuesView: 2131.

   * *note contextlib.AbstractContextManager: c34.

   * *note contextlib.AbstractAsyncContextManager: acf.

   * *note dataclasses.Field: 2132.

   * *note functools.cached_property: 4e7.

   * *note functools.partialmethod: a1e.

   * *note os.PathLike: bf8.

   * *note queue.LifoQueue: 2133.

   * *note queue.Queue: 131c.

   * *note queue.PriorityQueue: 2134.

   * *note queue.SimpleQueue: b0e.

   * *note re.Pattern: f29.

   * *note re.Match: f2a.

   * *note shelve.BsdDbShelf: 2135.

   * *note shelve.DbfilenameShelf: 2136.

   * *note shelve.Shelf: f3d.

   * *note types.MappingProxyType: 414.

   * *note weakref.WeakKeyDictionary: 1871.

   * *note weakref.WeakMethod: f90.

   * *note weakref.WeakSet: 581.

   * *note weakref.WeakValueDictionary: 1870.


File: python.info,  Node: GenericAlias 物件的特殊屬性,  Prev: 標準泛型類別,  Up: 泛型別名型別

5.4.13.3 ‘GenericAlias’ 物件的特殊屬性
......................................

所有參數化泛型都有實作特殊的唯讀屬性。

 -- 屬性: genericalias.__origin__

     此屬性指向非參數化泛型類別：

          >>> list[int].__origin__
          <class 'list'>

 -- 屬性: genericalias.__args__

     此屬性是傳遞給泛型類別之原始 *note __class_getitem__(): 6df. 的泛型
     型別 *note tuple: 322.（長度可以為 1）：

          >>> dict[str, list[int]].__args__
          (<class 'str'>, list[int])

 -- 屬性: genericalias.__parameters__

     此屬性是個會被延遲計算 (lazily computed) 的元組（可能為空），包含了
     在 ‘__args__’ 中找得到的不重複型別變數：

          >>> from typing import TypeVar

          >>> T = TypeVar('T')
          >>> list[T].__parameters__
          (~T,)

          備註: 具有 *note typing.ParamSpec: 142. 參數的一個
          ‘GenericAlias’ 物件在替換後可能沒有正確的 ‘__parameters__’，因
          為 *note typing.ParamSpec: 142. 主要用於靜態型別檢查。

 -- 屬性: genericalias.__unpacked__

     如果別名已使用 ‘*’ 運算子解包 (unpack) 則為 true 的布林值（請參閱
     *note TypeVarTuple: 143.）。

     在 3.11 版被加入.

也參考
......

PEP 484(1) - 型別提示

     引入 Python 的型別註釋框架。

PEP 585(2) - 標準集合 (Standard Collections) 中的型別提示泛型

     引入原生參數化標準函式庫類別的能力，前提是它們有實作特殊的類別方法
     *note __class_getitem__(): 6df.。

*note 泛型: 1e56.、*note 使用者定義泛型: 476.和 *note typing.Generic: 150c.

     有關如何實作可以在 runtime 參數化並能被靜態型別檢查器理解的泛型類別
     的文件。

在 3.9 版被加入.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0484/

   (2) https://peps.python.org/pep-0585/


File: python.info,  Node: 聯合型別 Union Type,  Prev: 泛型別名型別,  Up: 型別註釋的型別 --- 泛型別名 Generic Alias 、聯合 Union

5.4.13.4 聯合型別 (Union Type)
..............................

一個聯合物件可以保存多個*note 型別物件 (type object): 205e.之 ‘|’（位元
or）運算的值。這些型別主要用於*note 型別註釋 (type annotation): 3fe.。與
*note typing.Union: 5e1. 相比，聯合型別運算式可以讓型別提示語法更清晰簡
潔。

 -- Describe: X | Y | ...

     定義一個包含 'X'、'Y' 等型別的聯合物件。‘X | Y’ 表示 X 或 Y。它相當
     於 ‘typing.Union[X, Y]’。舉例來說，下列函式需要一個型別為 *note
     int: 23c. 或 *note float: 2c8. 的引數：

          def square(number: int | float) -> int | float:
              return number ** 2

          備註: 不能在 runtime 使用 ‘|’ 運算元 (operand) 來定義有一個以
          上的成員為向前參照 (forward reference) 的聯合。例如 ‘int |
          "Foo"’，其中 ‘"Foo"’ 是對未定義類別的參照，將在 runtime 失敗。
          對於包含向前參照的聯合，請將整個運算式以字串呈現，例如 ‘"int |
          Foo"’。

 -- Describe: union_object == other

     聯合物件可以與其他聯合物件一起進行相等性測試。細節如下：

        * 聯合的聯合會被扁平化：

               (int | str) | float == int | str | float

        * 冗餘型別會被刪除：

               int | str | int == int | str

        * 比較聯合時，順序會被忽略：

               int | str == str | int

        * 它與 *note typing.Union: 5e1. 相容：

               int | str == typing.Union[int, str]

        * 可選型別可以表示為與 ‘None’ 的聯合：

               str | None == typing.Optional[str]

 -- Describe: isinstance(obj, union_object)

 -- Describe: issubclass(obj, union_object)

     聯合物件也支援 *note isinstance(): 3e8. 和 *note issubclass(): 765.
     的呼叫：

          >>> isinstance("", int | str)
          True

     然而聯合物件中的*note 參數化泛型: 656.則無法被檢查：

          >>> isinstance(1, int | list[int])  # short-circuit evaluation
          True
          >>> isinstance([1], int | list[int])
          Traceback (most recent call last):
            ...
          TypeError: isinstance() argument 2 cannot be a parameterized generic

構成聯合物件的對使用者公開型別 (user-exposed type) 可以透過 *note
types.UnionType: 5e0. 存取並用於 *note isinstance(): 3e8. 檢查。物件不能
以型別來實例化：

     >>> import types
     >>> isinstance(int | str, types.UnionType)
     True
     >>> types.UnionType()
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: cannot create 'types.UnionType' instances

     備註: 新增了型別物件的 ‘__or__()’ 方法來支援 ‘X | Y’ 語法。如果元類
     別有實作 ‘__or__()’，則 Union 可以覆寫 (override) 它：

          >>> class M(type):
          ...     def __or__(self, other):
          ...         return "Hello"
          ...
          >>> class C(metaclass=M):
          ...     pass
          ...
          >>> C | int
          'Hello'
          >>> int | C
          int | C

也參考
......

PEP 604(1) - PEP 提出 ‘X | Y’ 語法和聯合型別。

在 3.10 版被加入.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0604/


File: python.info,  Node: Other Built-in Types,  Next: 特殊屬性,  Prev: 型別註釋的型別 --- 泛型別名 Generic Alias 、聯合 Union,  Up: 內建型別

5.4.14 Other Built-in Types
---------------------------

The interpreter supports several other kinds of objects.  Most of these
support only one or two operations.

* Menu:

* 模組: 模組<4>.
* Classes and Class Instances::
* 函式::
* Methods::
* Code Objects::
* Type Objects::
* The Null Object::
* The Ellipsis Object::
* NotImplemented 物件::
* Internal Objects::


File: python.info,  Node: 模組<4>,  Next: Classes and Class Instances,  Up: Other Built-in Types

5.4.14.1 模組
.............

The only special operation on a module is attribute access: ‘m.name’,
where 'm' is a module and 'name' accesses a name defined in 'm"s symbol
table.  Module attributes can be assigned to.  (Note that the *note
import: 586. statement is not, strictly speaking, an operation on a
module object; ‘import foo’ does not require a module object named 'foo'
to exist, rather it requires an (external) 'definition' for a module
named 'foo' somewhere.)

A special attribute of every module is *note __dict__: c04.  This is the
dictionary containing the module's symbol table.  Modifying this
dictionary will actually change the module's symbol table, but direct
assignment to the *note __dict__: c04. attribute is not possible (you
can write ‘m.__dict__['a'] = 1’, which defines ‘m.a’ to be ‘1’, but you
can't write ‘m.__dict__ = {}’).  Modifying *note __dict__: c04. directly
is not recommended.

Modules built into the interpreter are written like this: ‘<module 'sys'
(built-in)>’.  If loaded from a file, they are written as ‘<module 'os'
from '/usr/local/lib/pythonX.Y/os.pyc'>’.


File: python.info,  Node: Classes and Class Instances,  Next: 函式,  Prev: 模組<4>,  Up: Other Built-in Types

5.4.14.2 Classes and Class Instances
....................................

See *note Objects, values and types: 1dd3. and *note 類別定義: 126a. for
these.


File: python.info,  Node: 函式,  Next: Methods,  Prev: Classes and Class Instances,  Up: Other Built-in Types

5.4.14.3 函式
.............

Function objects are created by function definitions.  The only
operation on a function object is to call it: ‘func(argument-list)’.

There are really two flavors of function objects: built-in functions and
user-defined functions.  Both support the same operation (to call the
function), but the implementation is different, hence the different
object types.

更多資訊請見 *note 函式定義: 1b3a.。


File: python.info,  Node: Methods,  Next: Code Objects,  Prev: 函式,  Up: Other Built-in Types

5.4.14.4 Methods
................

Methods are functions that are called using the attribute notation.
There are two flavors: *note built-in methods: 1dfd. (such as ‘append()’
on lists) and *note class instance method: 1bc1.  Built-in methods are
described with the types that support them.

If you access a method (a function defined in a class namespace) through
an instance, you get a special object: a 'bound method' (also called
*note instance method: 1bc1.) object.  When called, it will add the
‘self’ argument to the argument list.  Bound methods have two special
read-only attributes: *note m.__self__: 1336. is the object on which the
method operates, and *note m.__func__: 128f. is the function
implementing the method.  Calling ‘m(arg-1, arg-2, ..., arg-n)’ is
completely equivalent to calling ‘m.__func__(m.__self__, arg-1, arg-2,
..., arg-n)’.

Like *note function objects: 295, bound method objects support getting
arbitrary attributes.  However, since method attributes are actually
stored on the underlying function object (*note method.__func__: 128f.),
setting method attributes on bound methods is disallowed.  Attempting to
set an attribute on a method results in an *note AttributeError: 2f6.
being raised.  In order to set a method attribute, you need to
explicitly set it on the underlying function object:

     >>> class C:
     ...     def method(self):
     ...         pass
     ...
     >>> c = C()
     >>> c.method.whoami = 'my name is method'  # 不得設定於方法
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     AttributeError: 'method' object has no attribute 'whoami'
     >>> c.method.__func__.whoami = 'my name is method'
     >>> c.method.whoami
     'my name is method'

更多資訊請見 *note Instance methods: 1bc1.。


File: python.info,  Node: Code Objects,  Next: Type Objects,  Prev: Methods,  Up: Other Built-in Types

5.4.14.5 Code Objects
.....................

Code objects are used by the implementation to represent
"pseudo-compiled" executable Python code such as a function body.  They
differ from function objects because they don't contain a reference to
their global execution environment.  Code objects are returned by the
built-in *note compile(): 178. function and can be extracted from
function objects through their *note __code__: 296. attribute.  See also
the *note code: 13. module.

存取 *note __code__: 296. 會引發一個附帶引數 ‘obj’ 與 ‘"__code__"’ 的
*note 稽核事件: 17bd. ‘object.__getattr__’。

A code object can be executed or evaluated by passing it (instead of a
source string) to the *note exec(): 162. or *note eval(): 163. built-in
functions.

更多資訊請見 *note 標準型別階層: 1dd6.。


File: python.info,  Node: Type Objects,  Next: The Null Object,  Prev: Code Objects,  Up: Other Built-in Types

5.4.14.6 Type Objects
.....................

Type objects represent the various object types.  An object's type is
accessed by the built-in function *note type(): cef.  There are no
special operations on types.  The standard module *note types: ec.
defines names for all standard built-in types.

Types are written like this: ‘<class 'int'>’.


File: python.info,  Node: The Null Object,  Next: The Ellipsis Object,  Prev: Type Objects,  Up: Other Built-in Types

5.4.14.7 The Null Object
........................

This object is returned by functions that don't explicitly return a
value.  It supports no special operations.  There is exactly one null
object, named ‘None’ (a built-in name).  ‘type(None)()’ produces the
same singleton.

它被寫為 ‘None’。


File: python.info,  Node: The Ellipsis Object,  Next: NotImplemented 物件,  Prev: The Null Object,  Up: Other Built-in Types

5.4.14.8 The Ellipsis Object
............................

This object is commonly used by slicing (see *note Slicings: 1f26.).  It
supports no special operations.  There is exactly one ellipsis object,
named *note Ellipsis: 2062. (a built-in name).  ‘type(Ellipsis)()’
produces the *note Ellipsis: 2062. singleton.

它被寫為 ‘Ellipsis’ 或 ‘...’。


File: python.info,  Node: NotImplemented 物件,  Next: Internal Objects,  Prev: The Ellipsis Object,  Up: Other Built-in Types

5.4.14.9 NotImplemented 物件
............................

This object is returned from comparisons and binary operations when they
are asked to operate on types they don't support.  See *note
Comparisons: 1f4c. for more information.  There is exactly one *note
NotImplemented: 776. object.  ‘type(NotImplemented)()’ produces the
singleton instance.

It is written as ‘NotImplemented’.


File: python.info,  Node: Internal Objects,  Prev: NotImplemented 物件,  Up: Other Built-in Types

5.4.14.10 Internal Objects
..........................

See *note 標準型別階層: 1dd6. for this information.  It describes *note
stack frame objects: 27e, *note traceback objects: a97, and slice
objects.


File: python.info,  Node: 特殊屬性,  Next: Integer string conversion length limitation,  Prev: Other Built-in Types,  Up: 內建型別

5.4.15 特殊屬性
---------------

The implementation adds a few special read-only attributes to several
object types, where they are relevant.  Some of these are not reported
by the *note dir(): 5d8. built-in function.

 -- 屬性: object.__dict__

     A dictionary or other mapping object used to store an object's
     (writable) attributes.

 -- 屬性: instance.__class__

     The class to which a class instance belongs.

 -- 屬性: class.__bases__

     The tuple of base classes of a class object.

 -- 屬性: definition.__name__

     The name of the class, function, method, descriptor, or generator
     instance.

 -- 屬性: definition.__qualname__

     The *note qualified name: 1843. of the class, function, method,
     descriptor, or generator instance.

     在 3.3 版被加入.

 -- 屬性: definition.__type_params__

     The *note type parameters: 294. of generic classes, functions, and
     *note type aliases: 3fa.

     在 3.12 版被加入.

 -- 屬性: class.__mro__

     This attribute is a tuple of classes that are considered when
     looking for base classes during method resolution.

 -- 方法: class.mro ()

     This method can be overridden by a metaclass to customize the
     method resolution order for its instances.  It is called at class
     instantiation, and its result is stored in *note __mro__: 205d.

 -- 方法: class.__subclasses__ ()

     Each class keeps a list of weak references to its immediate
     subclasses.  This method returns a list of all those references
     still alive.  The list is in definition order.  Example:

          >>> int.__subclasses__()
          [<class 'bool'>, <enum 'IntEnum'>, <flag 'IntFlag'>, <class 're._constants._NamedIntConstant'>]

 -- 屬性: class.__static_attributes__

     A tuple containing names of attributes of this class which are
     accessed through ‘self.X’ from any function in its body.

     在 3.13 版被加入.


File: python.info,  Node: Integer string conversion length limitation,  Prev: 特殊屬性,  Up: 內建型別

5.4.16 Integer string conversion length limitation
--------------------------------------------------

CPython has a global limit for converting between *note int: 23c. and
*note str: 3f2. to mitigate denial of service attacks.  This limit
'only' applies to decimal or other non-power-of-two number bases.
Hexadecimal, octal, and binary conversions are unlimited.  The limit can
be configured.

The *note int: 23c. type in CPython is an arbitrary length number stored
in binary form (commonly known as a "bignum").  There exists no
algorithm that can convert a string to a binary integer or a binary
integer to a string in linear time, 'unless' the base is a power of 2.
Even the best known algorithms for base 10 have sub-quadratic
complexity.  Converting a large value such as ‘int('1' * 500_000)’ can
take over a second on a fast CPU.

Limiting conversion size offers a practical way to avoid
CVE-2020-10735(1).

The limit is applied to the number of digit characters in the input or
output string when a non-linear conversion algorithm would be involved.
Underscores and the sign are not counted towards the limit.

When an operation would exceed the limit, a *note ValueError: 1e7. is
raised:

     >>> import sys
     >>> sys.set_int_max_str_digits(4300)  # Illustrative, this is the default.
     >>> _ = int('2' * 5432)
     Traceback (most recent call last):
     ...
     ValueError: Exceeds the limit (4300 digits) for integer string conversion: value has 5432 digits; use sys.set_int_max_str_digits() to increase the limit
     >>> i = int('2' * 4300)
     >>> len(str(i))
     4300
     >>> i_squared = i*i
     >>> len(str(i_squared))
     Traceback (most recent call last):
     ...
     ValueError: Exceeds the limit (4300 digits) for integer string conversion; use sys.set_int_max_str_digits() to increase the limit
     >>> len(hex(i_squared))
     7144
     >>> assert int(hex(i_squared), base=16) == i*i  # Hexadecimal is unlimited.

The default limit is 4300 digits as provided in *note
sys.int_info.default_max_str_digits: 122b.  The lowest limit that can be
configured is 640 digits as provided in *note
sys.int_info.str_digits_check_threshold: 122b.

Verification:

     >>> import sys
     >>> assert sys.int_info.default_max_str_digits == 4300, sys.int_info
     >>> assert sys.int_info.str_digits_check_threshold == 640, sys.int_info
     >>> msg = int('578966293710682886880994035146873798396722250538762761564'
     ...           '9252925514383915483333812743580549779436104706260696366600'
     ...           '571186405732').to_bytes(53, 'big')
     ...

在 3.11 版被加入.

* Menu:

* 受影響的 API::
* 設定限制::
* 建議的配置::

   ---------- Footnotes ----------

   (1) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10735


File: python.info,  Node: 受影響的 API,  Next: 設定限制,  Up: Integer string conversion length limitation

5.4.16.1 受影響的 API
.....................

The limitation only applies to potentially slow conversions between
*note int: 23c. and *note str: 3f2. or *note bytes: 1a5.:

   * ‘int(string)’ 以預設的 10 為底。

   * ‘int(string, base)’ for all bases that are not a power of 2.

   * ‘str(integer)’。

   * ‘repr(integer)’。

   * any other string conversion to base 10, for example ‘f"{integer}"’,
     ‘"{}".format(integer)’, or ‘b"%d" % integer’.

The limitations do not apply to functions with a linear algorithm:

   * ‘int(string, base)’ with base 2, 4, 8, 16, or 32.

   * *note int.from_bytes(): 1754. 和 *note int.to_bytes(): 1792.。

   * *note hex(): 1262.、*note oct(): 1261.、*note bin(): 123f.。

   * *note 格式規格 (Format Specification) 迷你語言: 1c8. for hex,
     octal, and binary numbers.

   * *note str: 3f2. to *note float: 2c8.

   * *note str: 3f2. to *note decimal.Decimal: 27c.


File: python.info,  Node: 設定限制,  Next: 建議的配置,  Prev: 受影響的 API,  Up: Integer string conversion length limitation

5.4.16.2 設定限制
.................

Before Python starts up you can use an environment variable or an
interpreter command line flag to configure the limit:

   * *note PYTHONINTMAXSTRDIGITS: 16c0, e.g.  ‘PYTHONINTMAXSTRDIGITS=640
     python3’ to set the limit to 640 or ‘PYTHONINTMAXSTRDIGITS=0
     python3’ to disable the limitation.

   * *note -X int_max_str_digits: 15a.，例如 ‘python3 -X
     int_max_str_digits=640’

   * *note sys.flags.int_max_str_digits: 2158. contains the value of
     *note PYTHONINTMAXSTRDIGITS: 16c0. or *note -X int_max_str_digits:
     15a.  If both the env var and the ‘-X’ option are set, the ‘-X’
     option takes precedence.  A value of '-1' indicates that both were
     unset, thus a value of *note sys.int_info.default_max_str_digits:
     2159. was used during initialization.

From code, you can inspect the current limit and set a new one using
these *note sys: c3. APIs:

   * *note sys.get_int_max_str_digits(): 215a. and *note
     sys.set_int_max_str_digits(): 16c1. are a getter and setter for the
     interpreter-wide limit.  Subinterpreters have their own limit.

Information about the default and minimum can be found in *note
sys.int_info: 122b.:

   * *note sys.int_info.default_max_str_digits: 122b. is the compiled-in
     default limit.

   * *note sys.int_info.str_digits_check_threshold: 122b. is the lowest
     accepted value for the limit (other than 0 which disables it).

在 3.11 版被加入.

     警示: Setting a low limit 'can' lead to problems.  While rare, code
     exists that contains integer constants in decimal in their source
     that exceed the minimum threshold.  A consequence of setting the
     limit is that Python source code containing decimal integer
     literals longer than the limit will encounter an error during
     parsing, usually at startup time or import time or even at
     installation time - anytime an up to date ‘.pyc’ does not already
     exist for the code.  A workaround for source that contains such
     large constants is to convert them to ‘0x’ hexadecimal form as it
     has no limit.

     Test your application thoroughly if you use a low limit.  Ensure
     your tests run with the limit set early via the environment or flag
     so that it applies during startup and even during any installation
     step that may invoke Python to precompile ‘.py’ sources to ‘.pyc’
     files.


File: python.info,  Node: 建議的配置,  Prev: 設定限制,  Up: Integer string conversion length limitation

5.4.16.3 建議的配置
...................

The default *note sys.int_info.default_max_str_digits: 2159. is expected
to be reasonable for most applications.  If your application requires a
different limit, set it from your main entry point using Python version
agnostic code as these APIs were added in security patch releases in
versions before 3.12.

範例：

     >>> import sys
     >>> if hasattr(sys, "set_int_max_str_digits"):
     ...     upper_bound = 68000
     ...     lower_bound = 4004
     ...     current_limit = sys.get_int_max_str_digits()
     ...     if current_limit == 0 or current_limit > upper_bound:
     ...         sys.set_int_max_str_digits(upper_bound)
     ...     elif current_limit < lower_bound:
     ...         sys.set_int_max_str_digits(lower_bound)

If you need to disable it entirely, set it to ‘0’.


File: python.info,  Node: 內建的例外,  Next: 文本處理 Text Processing 服務,  Prev: 內建型別,  Up: Python 標準函式庫 Standard Library

5.5 內建的例外
==============

在 Python 中，所有例外必須是從 *note BaseException: 55f. 衍生的類別的實
例。在陳述式 *note try: 68c. 搭配 *note except: 171. 子句裡提到一個特定
的類別時，那個子句也會處理任何從該類別衍生的例外類別（但不會處理該類別
'衍生自'的例外類別）。兩個不是由子類別關係關聯起來的例外類別永遠不相等，
就算它們有相同的名稱也是如此。

此章節裡列出的內建例外可以從直譯器或內建函式產生。除了特別提到的地方之外
，它們會有一個'關聯值'表示錯誤發生的詳細原因。這可能是一個字串，或者是一
些資訊項目組成的元組（例如一個錯誤代碼及一個解釋該代碼的字串）。這個關聯
值通常當作引數傳遞給例外類別的建構函式。

使用者的程式碼可以引發內建例外。這可以用來測試例外處理器或者用來回報一個
錯誤條件，'就像'直譯器會引發相同例外的情況；但需要注意的是沒有任何方式可
以避免使用者的程式碼引發不適當的錯誤。

可以從內建的例外類別定義新的例外子類別；程式設計師被鼓勵從 *note
Exception: 97d. 類別或其子類別衍生新的例外，而不是從 *note
BaseException: 55f. 來衍生。更多關於定義例外的資訊可以在 Python 教學中的
*note 使用者自定的例外: 1b98.裡取得。

* Menu:

* 例外的情境::
* 繼承自內建的例外::
* 基底類別 (base classes): 基底類別 base classes.
* 實體例外::
* 警告::
* 例外群組::
* 例外階層::


File: python.info,  Node: 例外的情境,  Next: 繼承自內建的例外,  Up: 內建的例外

5.5.1 例外的情境
----------------

三個例外物件上的屬性提供關於引發此例外的情境的資訊：

 -- 屬性: BaseException.__context__
 -- 屬性: BaseException.__cause__
 -- 屬性: BaseException.__suppress_context__

     當引發一個新的例外而同時有另一個例外已經正在被處理時，這個新例外的
     ‘__context__’ 屬性會自動被設成那個已處理的例外。當使用 *note
     except: 171. 或 *note finally: 96e. 子句或 *note with: 577. 陳述式
     的時候例外會被處理。

     這個隱含的例外情境可以透過使用 ‘from’ 搭配 *note raise: 591. 來補充
     明確的原因：

          raise new_exc from original_exc

     在 *note from: 591. 後面的運算式必須是一個例外或 ‘None’。它將會被設
     定成所引發例外的 ‘__cause__’。設定 ‘__cause__’ 也隱含地設定
     ‘__suppress_context__’ 屬性為 ‘True’，因此使用 ‘raise new_exc from
     None’ 實際上會以新的例外取代舊的例外以利於顯示（例如轉換 *note
     KeyError: 2fb. 為 *note AttributeError: 2f6.），同時保持舊的例外可
     以透過 ‘__context__’ 取得以方便 debug 的時候檢查。

     預設的回溯 (traceback) 顯示程式碼會顯示這些連鎖的例外 (chained
     exception) 加上例外本身的回溯。當存在的時候，在 ‘__cause__’ 中明確
     地連鎖的例外總是會被顯示。而在 ‘__context__’ 中隱含地連鎖的例外只有
     當 ‘__cause__’ 是 *note None: 61b. 且 ‘__suppress_context__’ 是
     false 時才會顯示。

     在任一種情況下，例外本身總是會顯示在任何連鎖例外的後面，因此回溯的
     最後一列總是顯示最後一個被引發的例外。


File: python.info,  Node: 繼承自內建的例外,  Next: 基底類別 base classes,  Prev: 例外的情境,  Up: 內建的例外

5.5.2 繼承自內建的例外
----------------------

使用者的程式碼可以建立繼承自例外類型的子類別。建議一次只繼承一種例外類型
以避免在基底類別之間如何處理 ‘args’ 屬性的任何可能衝突，以及可能的記憶體
佈局 (memory layout) 不相容。

'CPython 實作細節：' 為了效率，大部分的內建例外使用 C 來實作，參考
Objects/exceptions.c(1)。一些例外有客製化的記憶體佈局，使其不可能建立一
個繼承多種例外類型的子類別。類型的記憶體佈局是實作細節且可能會在不同
Python 版本間改變，造成未來新的衝突。因此，總之建議避免繼承多種例外類型
。

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Objects/exceptions.c


File: python.info,  Node: 基底類別 base classes,  Next: 實體例外,  Prev: 繼承自內建的例外,  Up: 內建的例外

5.5.3 基底類別 (base classes)
-----------------------------

以下的例外大部分被用在當作其他例外的基底類別。

 -- 例外: BaseException

     所有內建例外的基底類別。這不是為了讓使用者定義的類別直接繼承（可以
     使用 *note Exception: 97d.）。如果在這個類別的實例上呼叫 *note
     str(): 3f2.，會回傳實例的引數的表示，或者沒有引數的時候會回傳空字串
     。

      -- 屬性: args

          提供給該例外建構函式的引數元組。一些內建的例外（像是 *note
          OSError: 350.）預期接受特定數量的引數並賦予該元組的每一個元素
          一個特別的意義，其他例外則通常用一個提供錯誤訊息的單一字串來呼
          叫。

      -- 方法: with_traceback (tb)

          此方法設定 'tb' 為該例外的新的回溯並回傳該例外物件。在 PEP
          3134(1) 的例外連鎖功能變得可用之前，此方法曾被更普遍使用。下面
          的範例顯示我們如何將 ‘SomeException’ 的實例轉換為
          ‘OtherException’ 的實例同時保留回溯。一旦被引發，目前的 frame
          會被加進 ‘OtherException’ 的回溯，就像原來 ‘SomeException’ 的
          回溯會發生的一樣，我們允許它被傳遞給呼叫者：

               try:
                   ...
               except SomeException:
                   tb = sys.exception().__traceback__
                   raise OtherException(...).with_traceback(tb)

      -- 屬性: __traceback__

          可寫入的欄位，儲存關聯到該例外的*note 回溯物件: a97.。也可以參
          考 *note raise 陳述式: 591.。

      -- 方法: add_note (note)

          新增字串 ‘note’ 到例外的備註，在標準的回溯裡，備註出現在例外字
          串的後面。如果 ‘note’ 不是字串則引發 *note TypeError: 4dd.。

          在 3.11 版被加入.

      -- 屬性: __notes__

          該例外的備註串列，使用 *note add_note(): 55e. 來新增。此屬性在
          *note add_note(): 55e. 被呼叫的時候建立。

          在 3.11 版被加入.

 -- 例外: Exception

     所有內建、非系統退出 (non-system-exiting) 的例外都衍生自此類別。所
     有使用者定義的例外應該也要衍生自此類別。

 -- 例外: ArithmeticError

     各種運算錯誤所引發的那些內建例外：*note OverflowError: 825.、*note
     ZeroDivisionError: 8e9.、*note FloatingPointError: 2163. 的基底類別
     。

 -- 例外: BufferError

     當*note 緩衝 (buffer): 367. 相關的操作無法被執行時會引發此例外。

 -- 例外: LookupError

     當使用在對映或序列上的鍵或索引是無效的時候所引發的例外：*note
     IndexError: 14a3.、*note KeyError: 2fb. 的基底類別。這可以被 *note
     codecs.lookup(): 907. 直接引發。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3134/


File: python.info,  Node: 實體例外,  Next: 警告,  Prev: 基底類別 base classes,  Up: 內建的例外

5.5.4 實體例外
--------------

以下的例外是通常會被引發的例外。

 -- 例外: AssertionError

     當 *note assert: 90c. 陳述式失敗的時候被引發。

 -- 例外: AttributeError

     當屬性參照（參考 *note Attribute references: 1f20.）或賦值失敗的時
     候被引發。（當物件根本不支援屬性參照或屬性賦值的時候，*note
     TypeError: 4dd. 會被引發。）

     ‘name’ 和 ‘obj’ 屬性可以使用建構函式的僅限關鍵字 (keyword-only) 引
     數來設定。當被設定的時候，它們分別代表被嘗試存取的屬性名稱以及被以
     該屬性存取的物件。

     在 3.10 版的變更: 新增 ‘name’ 與 ‘obj’ 屬性。

 -- 例外: EOFError

     當 *note input(): 126b. 函式在沒有讀到任何資料而到達檔案結尾
     (end-of-file, EOF) 條件的時候被引發。（注意：‘io.IOBase.read()’ 和
     *note io.IOBase.readline(): 12bd. 方法當達到 EOF 時會回傳空字串。）

 -- 例外: FloatingPointError

     目前沒有被使用。

 -- 例外: GeneratorExit

     當 *note generator: 1004. 或 *note coroutine: 438. 被關閉的時候被引
     發；參考 *note generator.close(): 15ee. 和 *note coroutine.close():
     1ea3.。此例外直接繼承自 *note BaseException: 55f. 而不是 *note
     Exception: 97d.，因為技術上來說這不是一個錯誤。

 -- 例外: ImportError

     當 *note import: 586. 陳述式嘗試載入模組遇到問題的時候會被引發。當
     ‘from ... import’ 裡的 "from list" 包含找不到的名稱時也會被引發。

     可選的僅限關鍵字引數 'name' 和 'path' 設定對應的屬性：

      -- 屬性: name

          嘗試引入 (import) 的模組名稱。

      -- 屬性: path

          觸發此例外的任何檔案的路徑。

     在 3.3 版的變更: 新增 *note name: 2165. 與 *note path: 2166. 屬性。

 -- 例外: ModuleNotFoundError

     *note ImportError: 352. 的子類別，當模組不能被定位的時候會被 *note
     import: 586. 所引發。當在 *note sys.modules: 186e. 裡找到 ‘None’ 時
     也會被引發。

     在 3.6 版被加入.

 -- 例外: IndexError

     當序列的索引超出範圍的時候會被引發。（切片索引 (slice indices) 會默
     默地被截短使其能落在允許的範圍內；如果索引不是整數，*note
     TypeError: 4dd. 會被引發。）

 -- 例外: KeyError

     當對映（字典）的鍵無法在已存在的鍵的集合中被找到時會被引發。

 -- 例外: KeyboardInterrupt

     當使用者輸入中斷鍵 (interrupt key)（一般來說是 ‘Control-C’ 或
     ‘Delete’）時會被引發。在執行過程中，會定期檢查是否產生中斷。此例外
     繼承自 *note BaseException: 55f. 以防止意外地被捕捉 *note
     Exception: 97d. 的程式碼所捕捉，而因此讓直譯器無法結束。

          備註: 捕捉 *note KeyboardInterrupt: 975. 需要特殊的考量。因為
          它可以在無法預期的時間點被引發，可能在某些情況下讓正在跑的程式
          處在一個不一致的狀態。一般來說最好讓 *note KeyboardInterrupt:
          975. 越快結束程式越好，或者完全避免引發它。（參考 *note Note
          on Signal Handlers and Exceptions: 2167.。）

 -- 例外: MemoryError

     當一個操作用光了記憶體但情況還可能被修復 (rescued)（透過刪除一些物
     件）的時候被引發。關聯值是一個字串，表示什麼類型的（內部）操作用光
     了記憶體。需注意的是因為底層的記憶體管理架構（C 的 ‘malloc()’ 函式
     ），直譯器可能無法總是完整地從該情況中修復；僅管如此，它還是引發例
     外以讓堆疊回溯可以被印出，以防原因出在失控的程式。

 -- 例外: NameError

     當找不到本地或全域的名稱時會被引發。這只應用在不合格的名稱
     (unqualified name) 上。關聯值是一個錯誤訊息，包含那個無法被找到的名
     稱。

     ‘name’ 屬性可以使用僅限關鍵字引數來設定到建構函式。當被設定的時候它
     代表被嘗試存取的變數名稱。

     在 3.10 版的變更: 新增 ‘name’ 屬性。

 -- 例外: NotImplementedError

     此例外衍生自 *note RuntimeError: 179.。在使用者定義的基礎類別裡，當
     抽象方法要求衍生類別覆寫該方法時應該要引發此例外，或者當類別正在開
     發中，可用此例外表示還需要加入真正的實作。

          備註: 此例外不應該用來表示根本沒有要支援的運算子或方法 ── 在這
          個情況下可以讓該運算子或方法保持未定義，或者如果是子類別的話將
          其設成 *note None: 61b.。

          備註: ‘NotImplementedError’ 和 *note NotImplemented: 776. 雖然
          有相似的名稱和目的但並不是可互換的。參考 ‘NotImplemented’ 裡關
          於何時使用的細節。

 -- 例外: OSError ([arg])

 -- 例外: OSError (errno, strerror[, filename[, winerror[, filename2]]])

     當系統函式回傳系統相關錯誤，包含像"找不到檔案"或"硬碟已滿"的 I/O 失
     敗會引發此例外（而非不合法的引數或其他次要的錯誤）。

     建構函式的第二種形式會設定以下描述的相對應屬性。如果沒有給定則屬性
     預設為 *note None: 61b.。為了向後相容，如果傳入三個引數，*note
     args: 512. 屬性只會是包含建構函式前兩個引數的雙元素元組。

     如同下面的*note 作業系統例外: 2168.所描述，實際上建構函式通常回傳
     *note OSError: 350. 的子類別。會依據最後 *note errno: 2169. 的值決
     定特定子類別。這個行為只發生在直接建構 *note OSError: 350. 或透過別
     名，且產生子類別的時候不會被繼承。

      -- 屬性: errno

          從 C 變數 ‘errno’ 而來的數值錯誤代碼。

      -- 屬性: winerror

          在 Windows 下，這會提供你原生的 Windows 錯誤代碼。而 *note
          errno: 2169. 屬性是一個該原生錯誤代碼對於 POSIX 來說的近似翻譯
          。

          在 Windows 下，如果建構函式引數 'winerror' 是整數，則 *note
          errno: 2169. 屬性會根據該 Windows 錯誤代碼來決定，且 'errno' 引
          數會被忽略。在其他平台上，'winerror' 引數會被忽略，而 *note
          winerror: 216a. 屬性會不存在。

      -- 屬性: strerror

          作業系統提供的對應錯誤訊息。在 POSIX 下會使用 C 函式
          ‘perror()’ 做格式化，而在 Windows 下會使用 ‘FormatMessage()’。

      -- 屬性: filename
      -- 屬性: filename2

          對於包含檔案系統路徑的例外（像是 *note open(): 4c0. 或 *note
          os.unlink(): 108e.），*note filename: 216c. 是傳入函式的檔案名
          稱。對於包含兩個檔案系統路徑的函式（像是 *note os.rename():
          108a.），*note filename2: 216d. 對應到傳入函式的第二個檔案名稱
          。

     在 3.3 版的變更: *note EnvironmentError: ff6.、*note IOError: ff5.、
     *note WindowsError: ff7.、*note socket.error: ff8.、*note
     select.error: ff9. 及 ‘mmap.error’ 已合併進 *note OSError: 350.，而
     建構函式可能會回傳子類別。

     在 3.4 版的變更: *note filename: 216c. 屬性現在是傳入函式的原始檔名
     ，而不是從*note 檔案系統編碼和錯誤處理函式: 4e0.編碼或解碼過的名稱
     。並且新增 'filename2' 建構函式引數與屬性。

 -- 例外: OverflowError

     當運算操作的結果太大而無法表示的時候會引發此例外。這不會發生在整數
     上（會改成引發 *note MemoryError: 15bc. 而不是放棄）。然而，因為一
     些歷史因素，OverflowError 有時候會因為整數在要求範圍之外而引發。因
     為在 C 裡面缺乏浮點數例外處理的標準化，大部分的浮點數運算都沒有被檢
     查。

 -- 例外: PythonFinalizationError

     This exception is derived from *note RuntimeError: 179.  It is
     raised when an operation is blocked during interpreter shutdown
     also known as *note Python finalization: 133.

     Examples of operations which can be blocked with a *note
     PythonFinalizationError: 132. during the Python finalization:

        * Creating a new Python thread.

        * *note os.fork(): 17b.

     See also the *note sys.is_finalizing(): a32. function.

     在 3.13 版被加入: 在之前，會引發一般的 *note RuntimeError: 179.。

 -- 例外: RecursionError

     此例外衍生自 *note RuntimeError: 179.。當直譯器偵測到超過最大的遞迴
     深度（參考 *note sys.getrecursionlimit(): 46b.）時會引發此例外。

     在 3.5 版被加入: 在之前，會引發一般的 *note RuntimeError: 179.。

 -- 例外: ReferenceError

     當一個被 *note weakref.proxy(): 9f5. 函式建立的弱參照代理 (weak
     reference proxy) 被用來存取已經被垃圾回收 (garbage collected) 的參
     照物屬性時會引發此例外。更多關於弱參照的資訊參考 *note weakref: fc.
     模組。

 -- 例外: RuntimeError

     當偵測到一個不屬於任何其他種類的錯誤時會引發此例外。關聯值是一個表
     示確切什麼地方出錯的字串。

 -- 例外: StopIteration

     會被內建函式 *note next(): 77c. 及 *note iterator: 192. 的 *note
     __next__(): 1260. 方法引發，用來表示疊代器沒有更多項目可以產生。

      -- 屬性: value

          此例外物件有單一屬性 ‘value’，當建構此例外時會以引數給定，預設
          為 *note None: 61b.。

     當 *note generator: 1004. 或 *note coroutine: 438. 函式回傳時，新的
     *note StopIteration: ba1. 實例會被引發，而該函式的回傳值會被用來當
     作此例外建構函式的 *note value: 1e9f. 參數。

     如果產生器程式直接或間接引發 *note StopIteration: ba1.，則其會被轉
     換成 *note RuntimeError: 179.（保留 *note StopIteration: ba1. 作為
     新例外的成因）。

     在 3.3 版的變更: 新增 ‘value’ 屬性且產生器函式可以用它來回傳值。

     在 3.5 版的變更: 透過 ‘from __future__ import generator_stop’ 引入
     RuntimeError 的轉換，參考 PEP 479(1)。

     在 3.7 版的變更: 預設對所有程式啟用 PEP 479(2)：在產生器引發的
     *note StopIteration: ba1. 錯誤會轉換成 *note RuntimeError: 179.。

 -- 例外: StopAsyncIteration

     此例外必須被 *note asynchronous iterator: 191. 物件的 *note
     __anext__(): 1dfa. 方法引發來停止疊代。

     在 3.5 版被加入.

 -- 例外: SyntaxError (message, details)

     當剖析器遇到語法錯誤時會引發此例外。這可能發生在 *note import: 586.
     陳述式、在呼叫內建函式 *note compile(): 178.、*note exec(): 162. 或
     *note eval(): 163. 的時候，或者在讀取初始腳本或標準輸入（也包含互動
     式）的時候。

     例外實例的 *note str(): 3f2. 只回傳錯誤訊息。Details 是個元組，其成
     員也能夠以分開的屬性取得。

      -- 屬性: filename

          發生語法錯誤所在的檔案名稱。

      -- 屬性: lineno

          發生錯誤所在檔案的列號。這是以 1 開始的索引：檔案第一列的
          ‘lineno’ 是 1。

      -- 屬性: offset

          發生錯誤所在該列的欄號 (column)。這是以 1 開始的索引：該列第一
          個字元的 ‘offset’ 是 1。

      -- 屬性: text

          涉及該錯誤的原始程式碼文字。

      -- 屬性: end_lineno

          發生錯誤所在檔案的結束列號。這是以 1 開始的索引：檔案第一列的
          ‘lineno’ 是 1。

      -- 屬性: end_offset

          發生錯誤所在該結束列的欄號。這是以 1 開始的索引：該列第一個字
          元的 ‘offset’ 是 1。

     對於發生在 f-string 欄位的錯誤，訊息會以 "f-string: " 為前綴，而偏
     移量 (offset) 是從替代表達式建構的文字的偏移量。例如編譯 f'Bad {a
     b} field' 會得到這個 args 屬性：('f-string: ...', ('', 1, 2, '(a
     b)n', 1, 5))。

     在 3.10 版的變更: 新增 *note end_lineno: 2172. 與 *note end_offset:
     2173. 屬性。

 -- 例外: IndentationError

     與不正確的縮排有關的語法錯誤的基礎類別。這是 *note SyntaxError:
     173. 的子類別。

 -- 例外: TabError

     當縮排包含製表符號 (tab) 和空白的不一致用法時會引發此例外。這是
     *note IndentationError: 74c. 的子類別。

 -- 例外: SystemError

     當直譯器找到一個內部錯誤，但該情況看起來沒有嚴重到要讓它放棄所有的
     希望時會引發此例外。關聯值是一個表示什麼地方出錯的字串（以低階的方
     式表達）。

     你應該向你的 Python 直譯器作者或維護者回報此錯誤。務必要回報該
     Python 直譯器的版本（‘sys.version’；這也會在互動式 Python 會話的開
     頭被印出）、確切的錯誤訊息（該例外的關聯值）及如果可能的話，觸發此
     錯誤的程式來源。

 -- 例外: SystemExit

     此例外會被 *note sys.exit(): 12dd. 函式引發。它繼承自 *note
     BaseException: 55f. 而不是 *note Exception: 97d. 因此不會被捕捉
     *note Exception: 97d. 的程式意外地捕捉。這允許例外可以正確地向上傳
     遞並導致直譯器結束。當它未被處理時，Python 直譯器會結束；不會印出堆
     疊回溯。建構函式接受跟傳入 *note sys.exit(): 12dd. 一樣的可選引數。
     如果該值是整數，它會指定系統的結束狀態（傳入 C 的 ‘exit()’ 函式 ）
     ；如果它是 ‘None’，結束狀態會是 0；如果它是其他類型（例如字串），則
     物件的值會被印出而結束狀態是 1。

     對 *note sys.exit(): 12dd. 的呼叫會轉譯成例外讓負責清理的處理函式（
     *note try: 68c. 陳述式的 *note finally: 96e. 子句）可以被執行，且讓
     除錯器可以在不冒著失去控制的風險下執行腳本。如果在絕對有必要立即結
     束的情況（例如在子行程呼叫完 *note os.fork(): 17b. 之後 ）可以使用
     *note os._exit(): 2174. 函式。

      -- 屬性: code

          傳入建構函式的結束狀態或錯誤訊息。（預設是 ‘None’。 ）

 -- 例外: TypeError

     當一個操作或函式被用在不適合的類型的物件時會引發此例外。關聯值是一
     個字串，提供關於不相符類型的細節。

     此例外可能被使用者程式碼引發，以表示並不支援物件上所嘗試的操作，且
     本來就無意這樣做。如果一個物件有意要支援某個給定的操作但尚未提供實
     作，該引發的正確例外是 *note NotImplementedError: 20d.。

     傳入錯誤類型的引數（例如當預期傳入 *note int: 23c. 卻傳入 *note
     list: 5b6.）應該要導致 *note TypeError: 4dd.，但傳入帶有錯誤值的引
     數（例如超出預期範圍的數值）應該要導致 *note ValueError: 1e7.。

 -- 例外: UnboundLocalError

     當在函式或方法裡引用某個區域變數，但該變數尚未被繫結到任何值的時候
     會引發此例外。這是 *note NameError: 3e5. 的子類別。

 -- 例外: UnicodeError

     當 Unicode 相關的編碼或解碼錯誤發生時會引發此例外。這是 *note
     ValueError: 1e7. 的子類別。

     *note UnicodeError: 123a. 有屬性描述編碼或解碼錯誤。例如
     ‘err.object[err.start:err.end]’ 會提供讓編解碼器失敗的具體無效輸入
     。

      -- 屬性: encoding

          引發錯誤的編碼名稱。

      -- 屬性: reason

          描述特定編解碼器錯誤的字串。

      -- 屬性: object

          編解碼器嘗試編碼或解碼的物件。

      -- 屬性: start

          在 *note object: a2f. 中無效資料的開始索引。

      -- 屬性: end

          在 *note object: a2f. 中最後的無效資料後的索引。

 -- 例外: UnicodeEncodeError

     在編碼當中發生 Unicode 相關錯誤時會引發此例外。這是 *note
     UnicodeError: 123a. 的子類別。

 -- 例外: UnicodeDecodeError

     在解碼當中發生 Unicode 相關錯誤時會引發此例外。這是 *note
     UnicodeError: 123a. 的子類別。

 -- 例外: UnicodeTranslateError

     在轉譯當中發生 Unicode 相關錯誤時會引發此例外。這是 *note
     UnicodeError: 123a. 的子類別。

 -- 例外: ValueError

     當一個操作或函式收到引數是正確類型但是不適合的值，且該情況無法被更
     精確的例外例如 *note IndexError: 14a3. 所描述時會引發此例外。

 -- 例外: ZeroDivisionError

     當除法或模數運算 (modulo operation) 的第二個引數是 0 的時候會引發此
     例外。關聯值是一個字串，表示運算元及運算的類型。

以下例外是為了相容於之前版本而保留；從 Python 3.3 開始，它們是 *note
OSError: 350. 的別名。

 -- 例外: EnvironmentError

 -- 例外: IOError

 -- 例外: WindowsError

     僅限於在 Windows 中使用。

* Menu:

* 作業系統例外::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0479/

   (2) https://peps.python.org/pep-0479/


File: python.info,  Node: 作業系統例外,  Up: 實體例外

5.5.4.1 作業系統例外
....................

以下的例外是 *note OSError: 350. 的子類別，它們根據系統錯誤代碼來引發。

 -- 例外: BlockingIOError

     當設置為非阻塞操作的物件（例如 socket）上的操作將要阻塞時會引發此例
     外。對應到 ‘errno’ *note EAGAIN: 217c.、*note EALREADY: 217d.、
     *note EWOULDBLOCK: 217e. 及 *note EINPROGRESS: 217f.。

     除了 *note OSError: 350. 的那些屬性之外，*note BlockingIOError:
     ffa. 有多一個屬性：

      -- 屬性: characters_written

          一個整數，內容為在其阻塞之前，已寫進串流的字元數。當使用 *note
          io: 73. 模組裡的緩衝 I/O 類別時這個屬性是可用的。

 -- 例外: ChildProcessError

     當子行程上的操作失敗時會引發此例外。對應到 ‘errno’ *note ECHILD:
     2181.。

 -- 例外: ConnectionError

     連線相關問題的基礎類別。

     子類別有 *note BrokenPipeError: fff.、*note ConnectionAbortedError:
     1000.、*note ConnectionRefusedError: 1001. 及 *note
     ConnectionResetError: 1002.。

 -- 例外: BrokenPipeError

     *note ConnectionError: db0. 的子類別，當嘗試寫入管道 (pipe) 同時另
     一端已經被關閉時會引發此例外，或者當嘗試寫入已關閉寫入的 socket 時
     也會引發。對應到 ‘errno’ *note EPIPE: 2182. 及 *note ESHUTDOWN:
     2183.。

 -- 例外: ConnectionAbortedError

     *note ConnectionError: db0. 的子類別。當一個連線的嘗試被對等端點
     (peer) 中斷時會引發此例外。對應到 ‘errno’ *note ECONNABORTED:
     2184.。

 -- 例外: ConnectionRefusedError

     *note ConnectionError: db0. 的子類別。當一個連線的嘗試被對等端點拒
     絕時會引發此例外。對應到 ‘errno’ *note ECONNREFUSED: 2185.。

 -- 例外: ConnectionResetError

     *note ConnectionError: db0. 的子類別。當一個連線被對等端點重置時會
     引發此例外。對應到 ‘errno’ *note ECONNRESET: 2186.。

 -- 例外: FileExistsError

     當嘗試建立已存在的檔案或目錄時會引發此例外。對應到 ‘errno’ *note
     EEXIST: 2187.。

 -- 例外: FileNotFoundError

     當請求不存在的檔案或目錄時會引發此例外。對應到 ‘errno’ *note
     ENOENT: 2188.。

 -- 例外: InterruptedError

     當系統呼叫被傳入的信號中斷時會引發此例外。對應到 ‘errno’ *note
     EINTR: d2d.。

     在 3.5 版的變更: 現在當 syscall 被信號中斷時 Python 會重試系統呼叫
     而不會引發 *note InterruptedError: d2e.，除非信號處理器引發例外（理
     由可參考 PEP 475(1)）。

 -- 例外: IsADirectoryError

     當在目錄上請求檔案操作（例如 *note os.remove(): 1089.）時會引發此例
     外。對應到 ‘errno’ *note EISDIR: 2189.。

 -- 例外: NotADirectoryError

     當在某個不是目錄的東西上請求目錄操作（例如 *note os.listdir():
     1092.）時會引發此例外。在大多數的 POSIX 平台上，如果嘗試操作開啟或
     遍歷一個當作目錄的非目錄檔案也會引發此例外。對應到 ‘errno’ *note
     ENOTDIR: 218a.。

 -- 例外: PermissionError

     當嘗試執行一個沒有合乎存取權限的操作時會引發此例外 — 例如檔案系統權
     限。對應到 ‘errno’ *note EACCES: 218b.、*note EPERM: 16d1. 及 *note
     ENOTCAPABLE: 16c2.。

     在 3.11.1 版的變更: WASI 的 *note ENOTCAPABLE: 16c2. 現在對應到
     *note PermissionError: ce9.。

 -- 例外: ProcessLookupError

     當給定的行程不存在時會引發此例外。對應到 ‘errno’ *note ESRCH:
     218c.。

 -- 例外: TimeoutError

     當系統函式在系統層級超時會引發此例外。對應到 ‘errno’ *note
     ETIMEDOUT: 218d.。

在 3.3 版被加入: 加入以上所有的 *note OSError: 350. 子類別。

也參考
......

PEP 3151(2) — 改寫作業系統與 IO 例外階層

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0475/

   (2) https://peps.python.org/pep-3151/


File: python.info,  Node: 警告,  Next: 例外群組,  Prev: 實體例外,  Up: 內建的例外

5.5.5 警告
----------

以下的例外是當作警告的種類使用；更多細節參考 *note Warning Categories:
2190. 文件。

 -- 例外: Warning

     警告種類的基礎類別。

 -- 例外: UserWarning

     使用者程式碼產生的警告的基礎類別。

 -- 例外: DeprecationWarning

     關於已棄用功能的警告的基礎類別，且當那些警告是針對其他 Python 開發
     者。

     會被預設的警告過濾器忽略，在 ‘__main__’ 模組裡除外 ( PEP 565(1))。
     啟用 *note Python 開發模式: 1dd.會顯示此警告。

     棄用原則描述在 PEP 387(2) 裡。

 -- 例外: PendingDeprecationWarning

     關於過時且預期未來要被棄用，但目前尚未被棄用的功能的警告的基礎類別
     。

     因為發出關於可能即將被棄用的警告是不尋常的，此類別很少被使用，而對
     已經被棄用的情況會優先使用 *note DeprecationWarning: 18b.。

     會被預設的警告過濾器忽略。啟用 *note Python 開發模式: 1dd.會顯示此
     警告。

     棄用原則描述在 PEP 387(3) 裡。

 -- 例外: SyntaxWarning

     關於可疑語法的警告的基礎類別。

 -- 例外: RuntimeWarning

     關於可疑執行環境行為的警告的基礎類別。

 -- 例外: FutureWarning

     關於已棄用功能的警告的基礎類別，且當那些警告是針對以 Python 寫的應
     用程式的終端使用者。

 -- 例外: ImportWarning

     關於在模組引入的可能錯誤的警告的基礎類別。

     會被預設的警告過濾器忽略。啟用 *note Python 開發模式: 1dd.會顯示此
     警告。

 -- 例外: UnicodeWarning

     Unicode 相關警告的基礎類別。

 -- 例外: EncodingWarning

     編碼相關警告的基礎類別。

     細節參考*note 選擇性加入的編碼警告: 1c57.。

     在 3.10 版被加入.

 -- 例外: BytesWarning

     *note bytes: 1a5. 及 *note bytearray: 4e3. 相關警告的基礎類別。

 -- 例外: ResourceWarning

     資源用法相關警告的基礎類別。

     會被預設的警告過濾器忽略。啟用 *note Python 開發模式: 1dd.會顯示此
     警告。

     在 3.2 版被加入.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0565/

   (2) https://peps.python.org/pep-0387/

   (3) https://peps.python.org/pep-0387/


File: python.info,  Node: 例外群組,  Next: 例外階層,  Prev: 警告,  Up: 內建的例外

5.5.6 例外群組
--------------

當需要引發多個不相關例外時會使用下列的類別。它們是例外階層的一部分所以可
以像所有其他例外一樣使用 *note except: 171. 來處理。此外，它們會以包含的
例外類型為基礎來比對其子群組而被 *note except*: 55c. 辨認出來。

 -- 例外: ExceptionGroup (msg, excs)

 -- 例外: BaseExceptionGroup (msg, excs)

     這兩個例外類型都將例外包裝在序列 ‘excs’ 中。‘msg’ 參數必須是字串。
     這兩個類別的差異是 *note BaseExceptionGroup: 244. 擴充了 *note
     BaseException: 55f. 且可以包裝任何例外，而 *note ExceptionGroup:
     19c. 擴充了 *note Exception: 97d. 且只能包裝 *note Exception: 97d.
     的子類別。這個設計使得 ‘except Exception’ 可以捕捉 *note
     ExceptionGroup: 19c. 但不能捕捉 *note BaseExceptionGroup: 244.。

     如果所有包含的例外都是 *note Exception: 97d. 實例，*note
     BaseExceptionGroup: 244. 建構函式會回傳 *note ExceptionGroup: 19c.
     而不是 *note BaseExceptionGroup: 244.，因此可以被使用來讓這樣的選擇
     自動化。另一方面來說，如果任何包含的例外不是 *note Exception: 97d.
     的子類別，*note ExceptionGroup: 19c. 建構函式會引發 *note
     TypeError: 4dd.。

      -- 屬性: message

          建構函式的 ‘msg’ 引數。這是一個唯讀的屬性。

      -- 屬性: exceptions

          指定給建構函式 ‘excs’ 序列中的例外組成的元組。這是一個唯讀的屬
          性。

      -- 方法: subgroup (condition)

          回傳只包含從現有群組比對到 'condition' 的例外的例外群組，或者
          當結果為空時回傳 ‘None’。

          The condition can be an exception type or tuple of exception
          types, in which case each exception is checked for a match
          using the same check that is used in an ‘except’ clause.  The
          condition can also be a callable (other than a type object)
          that accepts an exception as its single argument and returns
          true for the exceptions that should be in the subgroup.

          現有例外的巢狀結構會保留在結果裡，其 *note message: 2195.、
          *note __traceback__: 125b.、*note __cause__: 125d.、*note
          __context__: 125c. 及 *note __notes__: 2161. 欄位的值也一樣。
          空的巢狀群組會從結果裡排除。

          條件會對巢狀例外群組裡的所有例外做檢查，包括頂層及任何巢狀的例
          外群組。如果條件對這樣的例外群組為 true，它會被完整包含在結果
          裡。

          在 3.13 版被加入: ‘condition’ can be any callable which is not
          a type object.

      -- 方法: split (condition)

          像 *note subgroup(): 15b9. 一樣，但回傳一對 ‘(match, rest)’，
          其中 ‘match’ 是 ‘subgroup(condition)’ 而 ‘rest’ 是剩下沒有比對
          到的部分。

      -- 方法: derive (excs)

          回傳有相同 *note message: 2195. 但將例外包裝在 ‘excs’ 的例外群
          組。

          此方法被 *note subgroup(): 15b9. 及 *note split(): 15ba. 使用
          ，被用來在各種情境下拆分例外群組。子類別需要覆寫它來讓 *note
          subgroup(): 15b9. 及 *note split(): 15ba. 回傳子類別而不是
          *note ExceptionGroup: 19c. 的實例。

          *note subgroup(): 15b9. 及 *note split(): 15ba. 會從原始的例外
          群組複製 *note __traceback__: 125b.、*note __cause__: 125d.、
          *note __context__: 125c. 和 *note __notes__: 2161. 欄位到
          *note derive(): 15b8. 所回傳的例外群組上，因此這些欄位不需要被
          *note derive(): 15b8. 更新。

               >>> class MyGroup(ExceptionGroup):
               ...     def derive(self, excs):
               ...         return MyGroup(self.message, excs)
               ...
               >>> e = MyGroup("eg", [ValueError(1), TypeError(2)])
               >>> e.add_note("a note")
               >>> e.__context__ = Exception("context")
               >>> e.__cause__ = Exception("cause")
               >>> try:
               ...    raise e
               ... except Exception as e:
               ...    exc = e
               ...
               >>> match, rest = exc.split(ValueError)
               >>> exc, exc.__context__, exc.__cause__, exc.__notes__
               (MyGroup('eg', [ValueError(1), TypeError(2)]), Exception('context'), Exception('cause'), ['a note'])
               >>> match, match.__context__, match.__cause__, match.__notes__
               (MyGroup('eg', [ValueError(1)]), Exception('context'), Exception('cause'), ['a note'])
               >>> rest, rest.__context__, rest.__cause__, rest.__notes__
               (MyGroup('eg', [TypeError(2)]), Exception('context'), Exception('cause'), ['a note'])
               >>> exc.__traceback__ is match.__traceback__ is rest.__traceback__
               True

     需注意 *note BaseExceptionGroup: 244. 定義了 *note __new__(): 526.，
     因此需要不同建構函式簽名的子類別需要覆寫它而不是 *note __init__():
     655.。例如下面定義了一個例外群組子類別接受 exit_code 並從中建構群組
     的訊息。：

          class Errors(ExceptionGroup):
             def __new__(cls, errors, exit_code):
                self = super().__new__(Errors, f"exit code: {exit_code}", errors)
                self.exit_code = exit_code
                return self

             def derive(self, excs):
                return Errors(excs, self.exit_code)

     像 *note ExceptionGroup: 19c. 一樣，任何 *note BaseExceptionGroup:
     244. 的子類別且也是 *note Exception: 97d. 的子類別只能包裝 *note
     Exception: 97d. 的實例。

     在 3.11 版被加入.


File: python.info,  Node: 例外階層,  Prev: 例外群組,  Up: 內建的例外

5.5.7 例外階層
--------------

內建例外的類別階層如下：

     BaseException
      ├── BaseExceptionGroup
      ├── GeneratorExit
      ├── KeyboardInterrupt
      ├── SystemExit
      └── Exception
           ├── ArithmeticError
           │    ├── FloatingPointError
           │    ├── OverflowError
           │    └── ZeroDivisionError
           ├── AssertionError
           ├── AttributeError
           ├── BufferError
           ├── EOFError
           ├── ExceptionGroup [BaseExceptionGroup]
           ├── ImportError
           │    └── ModuleNotFoundError
           ├── LookupError
           │    ├── IndexError
           │    └── KeyError
           ├── MemoryError
           ├── NameError
           │    └── UnboundLocalError
           ├── OSError
           │    ├── BlockingIOError
           │    ├── ChildProcessError
           │    ├── ConnectionError
           │    │    ├── BrokenPipeError
           │    │    ├── ConnectionAbortedError
           │    │    ├── ConnectionRefusedError
           │    │    └── ConnectionResetError
           │    ├── FileExistsError
           │    ├── FileNotFoundError
           │    ├── InterruptedError
           │    ├── IsADirectoryError
           │    ├── NotADirectoryError
           │    ├── PermissionError
           │    ├── ProcessLookupError
           │    └── TimeoutError
           ├── ReferenceError
           ├── RuntimeError
           │    ├── NotImplementedError
           │    ├── PythonFinalizationError
           │    └── RecursionError
           ├── StopAsyncIteration
           ├── StopIteration
           ├── SyntaxError
           │    └── IndentationError
           │         └── TabError
           ├── SystemError
           ├── TypeError
           ├── ValueError
           │    └── UnicodeError
           │         ├── UnicodeDecodeError
           │         ├── UnicodeEncodeError
           │         └── UnicodeTranslateError
           └── Warning
                ├── BytesWarning
                ├── DeprecationWarning
                ├── EncodingWarning
                ├── FutureWarning
                ├── ImportWarning
                ├── PendingDeprecationWarning
                ├── ResourceWarning
                ├── RuntimeWarning
                ├── SyntaxWarning
                ├── UnicodeWarning
                └── UserWarning


File: python.info,  Node: 文本處理 Text Processing 服務,  Next: 二進位資料服務,  Prev: 內建的例外,  Up: Python 標準函式庫 Standard Library

5.6 文本處理 (Text Processing) 服務
===================================

本章節介紹的模組 (module) 提供了廣泛的字串操作與其他文本處理服務。

在 *note 二進位資料服務: 219a. 下所描述的 *note codecs: 14. 模組也與文本
處理高度相關。另外也請參閱在 *note Text Sequence Type -- str: 1b03. 中所
描述的 Python 內建字串型別。

* Menu:

* string: string --- 常見的字串操作. 常見的字串操作
* re: re --- 正規表示式 regular expression 操作. 正規表示式 (regular expression) 操作
* difflib: difflib --- 計算差異的輔助工具. 計算差異的輔助工具
* textwrap: textwrap --- 文字包裝與填充. 文字包裝與填充
* unicodedata: unicodedata --- Unicode 資料庫. Unicode 資料庫
* stringprep: stringprep --- 網際網路字串準備. 網際網路字串準備
* readline: readline --- GNU readline 介面. GNU readline 介面
* rlcompleter: rlcompleter --- GNU readline 的補全函式. GNU readline 的補全函式


File: python.info,  Node: string --- 常見的字串操作,  Next: re --- 正規表示式 regular expression 操作,  Up: 文本處理 Text Processing 服務

5.6.1 ‘string’ -- 常見的字串操作
--------------------------------

'原始碼：'Lib/string.py(1)

__________________________________________________________________

也參考
......

*note Text Sequence Type -- str: 1b03.

*note String Methods: 1b04.

* Menu:

* 字串常數::
* 自訂字串格式::
* 格式化文字語法::
* 模板字串::
* 輔助函式::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/string.py


File: python.info,  Node: 字串常數,  Next: 自訂字串格式,  Up: string --- 常見的字串操作

5.6.1.1 字串常數
................

此模組中定義的常數為：

 -- 資料: string.ascii_letters

     下文描述的 *note ascii_lowercase: 219e. 和 *note ascii_uppercase:
     219f. 常數的串接，該值不依賴於區域設定。

 -- 資料: string.ascii_lowercase

     小寫字母 ‘'abcdefghijklmnopqrstuvwxyz'’。該值與地區設定無關且不會改
     變。

 -- 資料: string.ascii_uppercase

     大寫字母 ‘’ABCDEFGHIJKLMNOPQRSTUVWXYZ’’。 此值與地區設定無關且不會
     改變。

 -- 資料: string.digits

     字串 ‘’0123456789’’。

 -- 資料: string.hexdigits

     字串 ‘’0123456789abcdefABCDEF’’。

 -- 資料: string.octdigits

     字串 ‘'01234567'’。

 -- 資料: string.punctuation

     在 ‘C’ 語言中被視為標點符號的 ASCII 字元的字串：
     ‘!”#$%&’()*+,-./:;<=>?@[\]^_`{|}~’。

 -- 資料: string.printable

     ASCII 字元的字串是可被列印輸出的。 這是 *note digits: 21a0.、*note
     ascii_letters: 1258.、*note punctuation: 21a3. 和 *note whitespace:
     21a5. 的組合。

 -- 資料: string.whitespace

     包含所有 ASCII 字元的字串都視為空白字元 (whitespace)。 包含空格
     (space)、製表符號 (tab)、換行符號 (linefeed)、return、換頁符號
     (formfeed) 和垂直製表符號 (vertical tab) 這些字元。


File: python.info,  Node: 自訂字串格式,  Next: 格式化文字語法,  Prev: 字串常數,  Up: string --- 常見的字串操作

5.6.1.2 自訂字串格式
....................

透過 PEP 3101(1) 中描述的 *note format(): 5c7. 方法，內建字串類別提供了
進行複雜變數替換和數值格式化的能力。*note string: be. 模組中的 *note
Formatter: e5e. 類別模組可讓你使用與內建 *note format(): 5c7. 方法相同的
實作來建立和自訂你自己的字串格式化行為。

 -- 類別: string.Formatter

     *note Formatter: e5e. 類別有以下的公開方法：

      -- 方法: format (format_string, /, *args, **kwargs)

          主要的 API 方法。它接收一個格式字串及一組任意的位置引數與關鍵
          字引數，是呼叫 *note vformat(): 21a7. 的包裝器 (wrapper)。

          在 3.7 版的變更: 現在格式字串引數是*note 僅限位置參數: a28.。

      -- 方法: vformat (format_string, args, kwargs)

          This function does the actual work of formatting.  It is
          exposed as a separate function for cases where you want to
          pass in a predefined dictionary of arguments, rather than
          unpacking and repacking the dictionary as individual arguments
          using the ‘*args’ and ‘**kwargs’ syntax.  *note vformat():
          21a7. does the work of breaking up the format string into
          character data and replacement fields.  It calls the various
          methods described below.

     In addition, the *note Formatter: e5e. defines a number of methods
     that are intended to be replaced by subclasses:

      -- 方法: parse (format_string)

          將 format_string 放入迴圈，並回傳一個可疊代物件，其元素為
          ('literal_text', 'field_name', 'format_spec', 'conversion')。
          這會被 *note vformat(): 21a7. 用於將字串裁切為字面文本或替換欄
          位。

          The values in the tuple conceptually represent a span of
          literal text followed by a single replacement field.  If there
          is no literal text (which can happen if two replacement fields
          occur consecutively), then 'literal_text' will be a
          zero-length string.  If there is no replacement field, then
          the values of 'field_name', 'format_spec' and 'conversion'
          will be ‘None’.

      -- 方法: get_field (field_name, args, kwargs)

          Given 'field_name' as returned by *note parse(): 21a8. (see
          above), convert it to an object to be formatted.  Returns a
          tuple (obj, used_key).  The default version takes strings of
          the form defined in PEP 3101(2), such as "0[name]" or
          "label.title".  'args' and 'kwargs' are as passed in to *note
          vformat(): 21a7.  The return value 'used_key' has the same
          meaning as the 'key' parameter to *note get_value(): 21aa.

      -- 方法: get_value (key, args, kwargs)

          Retrieve a given field value.  The 'key' argument will be
          either an integer or a string.  If it is an integer, it
          represents the index of the positional argument in 'args'; if
          it is a string, then it represents a named argument in
          'kwargs'.

          The 'args' parameter is set to the list of positional
          arguments to *note vformat(): 21a7, and the 'kwargs' parameter
          is set to the dictionary of keyword arguments.

          For compound field names, these functions are only called for
          the first component of the field name; subsequent components
          are handled through normal attribute and indexing operations.

          So for example, the field expression '0.name' would cause
          *note get_value(): 21aa. to be called with a 'key' argument of
          0.  The ‘name’ attribute will be looked up after *note
          get_value(): 21aa. returns by calling the built-in *note
          getattr(): b78. function.

          If the index or keyword refers to an item that does not exist,
          then an *note IndexError: 14a3. or *note KeyError: 2fb. should
          be raised.

      -- 方法: check_unused_args (used_args, args, kwargs)

          Implement checking for unused arguments if desired.  The
          arguments to this function is the set of all argument keys
          that were actually referred to in the format string (integers
          for positional arguments, and strings for named arguments),
          and a reference to the 'args' and 'kwargs' that was passed to
          vformat.  The set of unused args can be calculated from these
          parameters.  *note check_unused_args(): 21ab. is assumed to
          raise an exception if the check fails.

      -- 方法: format_field (value, format_spec)

          *note format_field(): 21ac. simply calls the global *note
          format(): 5c3. built-in.  The method is provided so that
          subclasses can override it.

      -- 方法: convert_field (value, conversion)

          Converts the value (returned by *note get_field(): 21a9.)
          given a conversion type (as in the tuple returned by the *note
          parse(): 21a8. method).  The default version understands 's'
          (str), 'r' (repr) and 'a' (ascii) conversion types.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3101/

   (2) https://peps.python.org/pep-3101/


File: python.info,  Node: 格式化文字語法,  Next: 模板字串,  Prev: 自訂字串格式,  Up: string --- 常見的字串操作

5.6.1.3 格式化文字語法
......................

The *note str.format(): 5c7. method and the *note Formatter: e5e. class
share the same syntax for format strings (although in the case of *note
Formatter: e5e, subclasses can define their own format string syntax).
The syntax is related to that of *note formatted string literals: 94d,
but it is less sophisticated and, in particular, does not support
arbitrary expressions.

Format strings contain "replacement fields" surrounded by curly braces
‘{}’.  Anything that is not contained in braces is considered literal
text, which is copied unchanged to the output.  If you need to include a
brace character in the literal text, it can be escaped by doubling: ‘{{’
and ‘}}’.

The grammar for a replacement field is as follows:

     replacement_field ::= "{" [field_name] ["!" conversion] [":" format_spec] "}"
     field_name        ::= arg_name ("." attribute_name | "[" element_index "]")*
     arg_name          ::= [identifier | digit+]
     attribute_name    ::= identifier
     element_index     ::= digit+ | index_string
     index_string      ::= <any source character except "]"> +
     conversion        ::= "r" | "s" | "a"
     format_spec       ::= format-spec:format_spec

In less formal terms, the replacement field can start with a
'field_name' that specifies the object whose value is to be formatted
and inserted into the output instead of the replacement field.  The
'field_name' is optionally followed by a 'conversion' field, which is
preceded by an exclamation point ‘'!'’, and a 'format_spec', which is
preceded by a colon ‘':'’.  These specify a non-default format for the
replacement value.

另請參閱 *note 格式規格 (Format Specification) 迷你語言: 1c8. 部份。

The 'field_name' itself begins with an 'arg_name' that is either a
number or a keyword.  If it's a number, it refers to a positional
argument, and if it's a keyword, it refers to a named keyword argument.
An 'arg_name' is treated as a number if a call to *note str.isdecimal():
209c. on the string would return true.  If the numerical arg_names in a
format string are 0, 1, 2, ...  in sequence, they can all be omitted
(not just some) and the numbers 0, 1, 2, ...  will be automatically
inserted in that order.  Because 'arg_name' is not quote-delimited, it
is not possible to specify arbitrary dictionary keys (e.g., the strings
‘'10'’ or ‘':-]'’) within a format string.  The 'arg_name' can be
followed by any number of index or attribute expressions.  An expression
of the form ‘'.name'’ selects the named attribute using *note getattr():
b78, while an expression of the form ‘'[index]'’ does an index lookup
using *note __getitem__(): 266.

在 3.1 版的變更: The positional argument specifiers can be omitted for
*note str.format(): 5c7, so ‘'{} {}'.format(a, b)’ is equivalent to
‘'{0} {1}'.format(a, b)’.

在 3.4 版的變更: The positional argument specifiers can be omitted for
*note Formatter: e5e.

Some simple format string examples:

     "First, thou shalt count to {0}"  # References first positional argument
     "Bring me a {}"                   # Implicitly references the first positional argument
     "From {} to {}"                   # Same as "From {0} to {1}"
     "My quest is {name}"              # References keyword argument 'name'
     "Weight in tons {0.weight}"       # 'weight' attribute of first positional arg
     "Units destroyed: {players[0]}"   # First element of keyword argument 'players'.

The 'conversion' field causes a type coercion before formatting.
Normally, the job of formatting a value is done by the *note
__format__(): 5c5. method of the value itself.  However, in some cases
it is desirable to force a type to be formatted as a string, overriding
its own definition of formatting.  By converting the value to a string
before calling *note __format__(): 5c5, the normal formatting logic is
bypassed.

目前支援三種轉換旗標：‘'!s'’ 會對該值呼叫 *note str(): 3f2.，‘'!r'’ 會對
該值呼叫 *note repr(): 7a1.，而 ‘'!a'’ 則會對該值呼叫 *note ascii():
1354.。

一些範例：

     "Harold's a clever {0!s}"        # Calls str() on the argument first
     "Bring out the holy {name!r}"    # Calls repr() on the argument first
     "More {!a}"                      # Calls ascii() on the argument first

'format_spec' 欄位描述了值的呈現規格，例如欄位寬度、對齊、填充
(padding)、小數精度等細節資訊。每種值類型都可以定義自己的「格式化迷你語
言 (formatting mini-language)」或對 'format_spec' 的解釋。

大多數內建型別都支援常見的格式化迷你語言，下一節將會詳細說明。

'format_spec' 欄位還可以在其內部包含巢狀的替換欄位。這些巢狀的替換欄位可
能包含欄位名稱、轉換旗標、格式規格描述，但是不允許再更深層的巢狀結構。
format_spec 内部的替換欄位會在 'format_spec' 字串被直譯前被替換。這讓數
值的格式能夠被動態地指定。

範例請見 *note 格式範例: 21b7.。

* Menu:

* 格式規格 (Format Specification) 迷你語言: 格式規格 Format Specification 迷你語言.
* 格式範例::


File: python.info,  Node: 格式規格 Format Specification 迷你語言,  Next: 格式範例,  Up: 格式化文字語法

5.6.1.4 格式規格 (Format Specification) 迷你語言
................................................

「格式規格」在格式字串 (format string) 中包含的替換欄位中使用，以定義各
個值如何被呈現（請參考 *note 格式化文字語法: 131e. 和 *note f-string（f
字串）: 94d.）。它們也能夠直接傳遞給內建的 *note format(): 5c3. 函式。每
個可格式化型別 (formattable type) 可以定義格式規格如何被直譯。

大部分內建型別為了格式規格實作了下列選項，不過有些選項只被數值型別支援。

一般來說，輸入空格式規格會產生和對值呼叫 *note str(): 3f2. 函式相同的結
果，非空的格式規格才會修改結果。

'標準格式說明符號 (standard format specifier)' 的一般型式如下：

     format_spec     ::= [[fill]align][sign]["z"]["#"]["0"][width][grouping_option]["." precision][type]
     fill            ::= <any character>
     align           ::= "<" | ">" | "=" | "^"
     sign            ::= "+" | "-" | " "
     width           ::= digit+
     grouping_option ::= "_" | ","
     precision       ::= digit+
     type            ::= "b" | "c" | "d" | "e" | "E" | "f" | "F" | "g" | "G" | "n" | "o" | "s" | "x" | "X" | "%"

如果給定了一個有效的 'align' 值，則可以在它之前加一個 'fill' 字元，且該
字元可為任意字元，若不加的話預設為空格。使用*note 格式字串: 94d.或 *note
str.format(): 5c7. 時是無法在其中使用大括號（"‘{’" 或 "‘}’"）作為 'fill'
字元的，但仍可透過巢狀替換欄位的方式插入大括號。此限制不影響 *note
format(): 5c3. 函式。

The meaning of the various alignment options is as follows:

選項          含義
              
-----------------------------------------------------------------------------
              
‘'<'’         強制欄位在可用空間內靠左對齊（這是大多數物件的預設值）。
              
              
‘'>'’         強制欄位在可用空間內靠右對齊（這是數字的預設值）。
              
              
‘'='’         Forces the padding to be placed after the sign (if any) but
              before the digits.  This is used for printing fields in the
              form '+000000120'.  This alignment option is only valid for
              numeric types.  It becomes the default for numbers when '0'
              immediately precedes the field width.
              
              
‘'^'’         強制欄位在可用空間內置中。
              

請注意，除非有定義了最小欄位寬度，否則欄位寬度將始終與填充它的資料大小相
同，故在該情況下的對齊選項是沒有意義的。

'sign' 選項只適用於數字型別，並可為以下之一：

選項          含義
              
-----------------------------------------------------------------------------
              
‘'+'’         表示正數與負數均需使用符號。
              
              
‘'-'’         indicates that a sign should be used only for negative
              numbers (this is the default behavior).
              
              
space         表示正數應使用前導空格，負數應使用減號。
              

The ‘'z'’ option coerces negative zero floating-point values to positive
zero after rounding to the format precision.  This option is only valid
for floating-point presentation types.

在 3.11 版的變更: 新增 ‘'z'’ 選項（請見 PEP 682(1)）。

The ‘'#'’ option causes the "alternate form" to be used for the
conversion.  The alternate form is defined differently for different
types.  This option is only valid for integer, float and complex types.
For integers, when binary, octal, or hexadecimal output is used, this
option adds the respective prefix ‘'0b'’, ‘'0o'’, ‘'0x'’, or ‘'0X'’ to
the output value.  For float and complex the alternate form causes the
result of the conversion to always contain a decimal-point character,
even if no digits follow it.  Normally, a decimal-point character
appears in the result of these conversions only if a digit follows it.
In addition, for ‘'g'’ and ‘'G'’ conversions, trailing zeros are not
removed from the result.

The ‘','’ option signals the use of a comma for a thousands separator.
For a locale aware separator, use the ‘'n'’ integer presentation type
instead.

在 3.1 版的變更: 新增 ‘','’ 選項（請見 PEP 378(2)）。

‘'_'’ 選項表示對於浮點表示型別和整數表示型別 ‘'d'’ 使用底線作為千位分隔
符號。對於整數表示型別 ‘'b'’，‘'o'’，‘'x'’ 和 ‘'X'’，每 4 位數字會插入底
線。對於其他表示型別，指定此選項會出錯。

在 3.6 版的變更: 新增 ‘'_'’ 選項（請見 PEP 515(3)）。

'width' 是一個十進位整數，定義了最小總欄位寬度，包括任何前綴、分隔符號和
其他格式字元。如果未指定，則欄位寬度將由內容決定。

當未給予明確的對齊指示，在 'width' 欄位前面填入零 (‘'0'’) 字元將會為數值
型別啟用有符號察覺的零填充 (sign-aware zero-padding)。這相當於使用 ‘'0'’
為 'fill' 字元且對齊類型為 ‘'='’。

在 3.10 版的變更: 在 'width' 欄位前面加上 ‘'0'’ 不再影響字串的預設對齊方
式。

'precision' 是一個十進位整數，指定表示類型 ‘'f'’ 和 ‘'F'’ 的小數點後應顯
示多少位，或表示類型 ‘'g'’ 或 ‘'G'’ 的小數點前後應顯示多少位。對於字串表
示類型，該欄位指定最大欄位大小 - 換言之，將使用欄位中的多少字元。整數表
示類型不允許使用 'precision'。

最終，型別決定了資料將會如何呈現

可用的字串表示型別有：

     型別          含義
                   
     -----------------------------------------------------------------------------
                   
     ‘'s'’         String format.  This is the default type for strings and may
                   be omitted.
                   
                   
     None          The same as ‘'s'’.
                   

The available integer presentation types are:

     型別          含義
                   
     -----------------------------------------------------------------------------
                   
     ‘'b'’         Binary format.  Outputs the number in base 2.
                   
                   
     ‘'c'’         Character.  Converts the integer to the corresponding
                   unicode character before printing.
                   
                   
     ‘'d'’         Decimal Integer.  Outputs the number in base 10.
                   
                   
     ‘'o'’         Octal format.  Outputs the number in base 8.
                   
                   
     ‘'x'’         十六進位格式。輸出以 16 為基數的數字，9 以上的數字使用小寫字
                   母。
                   
                   
     ‘'X'’         十六進位格式。輸出以 16 為基數的數字，9 以上的數字使用大寫字
                   母。如果指定了 ‘'#'’，則前綴 ‘'0x'’ 也會被轉成大寫的 ‘'0X'’。
                   
                   
     ‘'n'’         Number.  This is the same as ‘'d'’, except that it uses the
                   current locale setting to insert the appropriate number
                   separator characters.
                   
                   
     None          The same as ‘'d'’.
                   

In addition to the above presentation types, integers can be formatted
with the floating-point presentation types listed below (except ‘'n'’
and ‘None’).  When doing so, *note float(): 2c8. is used to convert the
integer to a floating-point number before formatting.

The available presentation types for *note float: 2c8. and *note
Decimal: 27c. values are:

     型別          含義
                   
     -----------------------------------------------------------------------------
                   
     ‘'e'’         Scientific notation.  For a given precision ‘p’, formats the
                   number in scientific notation with the letter 'e' separating
                   the coefficient from the exponent.  The coefficient has one
                   digit before and ‘p’ digits after the decimal point, for a
                   total of ‘p + 1’ significant digits.  With no precision
                   given, uses a precision of ‘6’ digits after the decimal
                   point for *note float: 2c8, and shows all coefficient digits
                   for *note Decimal: 27c.  If no digits follow the decimal
                   point, the decimal point is also removed unless the ‘#’
                   option is used.
                   
                   
     ‘'E'’         Scientific notation.  Same as ‘'e'’ except it uses an upper
                   case 'E' as the separator character.
                   
                   
     ‘'f'’         Fixed-point notation.  For a given precision ‘p’, formats
                   the number as a decimal number with exactly ‘p’ digits
                   following the decimal point.  With no precision given, uses
                   a precision of ‘6’ digits after the decimal point for
                   *note float: 2c8, and uses a precision large enough to show
                   all coefficient digits for *note Decimal: 27c.  If no digits
                   follow the decimal point, the decimal point is also removed
                   unless the ‘#’ option is used.
                   
                   
     ‘'F'’         Fixed-point notation.  Same as ‘'f'’, but converts ‘nan’ to
                   ‘NAN’ and ‘inf’ to ‘INF’.
                   
                   
     ‘'g'’         General format.  For a given precision ‘p >= 1’, this rounds
                   the number to ‘p’ significant digits and then formats the
                   result in either fixed-point format or in scientific
                   notation, depending on its magnitude.  A precision of ‘0’ is
                   treated as equivalent to a precision of ‘1’.
                   
                   The precise rules are as follows: suppose that the result
                   formatted with presentation type ‘'e'’ and precision ‘p-1’
                   would have exponent ‘exp’.  Then, if ‘m <= exp < p’, where
                   ‘m’ is -4 for floats and -6 for *note Decimals: 27c, the
                   number is formatted with presentation type ‘'f'’ and
                   precision ‘p-1-exp’.  Otherwise, the number is formatted
                   with presentation type ‘'e'’ and precision ‘p-1’.  In both
                   cases insignificant trailing zeros are removed from the
                   significand, and the decimal point is also removed if there
                   are no remaining digits following it, unless the ‘'#'’
                   option is used.
                   
                   With no precision given, uses a precision of ‘6’ significant
                   digits for *note float: 2c8.  For *note Decimal: 27c, the
                   coefficient of the result is formed from the coefficient
                   digits of the value; scientific notation is used for values
                   smaller than ‘1e-6’ in absolute value and values where the
                   place value of the least significant digit is larger than 1,
                   and fixed-point notation is used otherwise.
                   
                   Positive and negative infinity, positive and negative zero,
                   and nans, are formatted as ‘inf’, ‘-inf’, ‘0’, ‘-0’ and
                   ‘nan’ respectively, regardless of the precision.
                   
                   
     ‘'G'’         General format.  Same as ‘'g'’ except switches to ‘'E'’ if
                   the number gets too large.  The representations of infinity
                   and NaN are uppercased, too.
                   
                   
     ‘'n'’         Number.  This is the same as ‘'g'’, except that it uses the
                   current locale setting to insert the appropriate number
                   separator characters.
                   
                   
     ‘'%'’         Percentage.  Multiplies the number by 100 and displays in
                   fixed (‘'f'’) format, followed by a percent sign.
                   
                   
     None          For *note float: 2c8. this is the same as ‘'g'’, except that
                   when fixed-point notation is used to format the result, it
                   always includes at least one digit past the decimal point.
                   The precision used is as large as needed to represent the
                   given value faithfully.
                   
                   For *note Decimal: 27c, this is the same as either ‘'g'’ or
                   ‘'G'’ depending on the value of ‘context.capitals’ for the
                   current decimal context.
                   
                   The overall effect is to match the output of
                   *note str(): 3f2. as altered by the other format modifiers.
                   

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0682/

   (2) https://peps.python.org/pep-0378/

   (3) https://peps.python.org/pep-0515/


File: python.info,  Node: 格式範例,  Prev: 格式規格 Format Specification 迷你語言,  Up: 格式化文字語法

5.6.1.5 格式範例
................

本節包含 *note str.format(): 5c7. 語法以及與舊式 ‘%’ 格式的比較。

此語法在大多情況下與舊式的 ‘%’ 格式類似，只是增加了 ‘{}’ 和 ‘:’ 來取代
‘%’。例如，‘'%03.2f'’ 可以改寫為 ‘'{:03.2f}'’。

新的語法還支援新的選項，將在以下的範例中說明。

按位置存取引數：

     >>> '{0}, {1}, {2}'.format('a', 'b', 'c')
     'a, b, c'
     >>> '{}, {}, {}'.format('a', 'b', 'c')  # 3.1+ only
     'a, b, c'
     >>> '{2}, {1}, {0}'.format('a', 'b', 'c')
     'c, b, a'
     >>> '{2}, {1}, {0}'.format(*'abc')      # unpacking argument sequence
     'c, b, a'
     >>> '{0}{1}{0}'.format('abra', 'cad')   # arguments' indices can be repeated
     'abracadabra'

按名稱存取引數：

     >>> 'Coordinates: {latitude}, {longitude}'.format(latitude='37.24N', longitude='-115.81W')
     'Coordinates: 37.24N, -115.81W'
     >>> coord = {'latitude': '37.24N', 'longitude': '-115.81W'}
     >>> 'Coordinates: {latitude}, {longitude}'.format(**coord)
     'Coordinates: 37.24N, -115.81W'

存取引數的屬性：

     >>> c = 3-5j
     >>> ('The complex number {0} is formed from the real part {0.real} '
     ...  'and the imaginary part {0.imag}.').format(c)
     'The complex number (3-5j) is formed from the real part 3.0 and the imaginary part -5.0.'
     >>> class Point:
     ...     def __init__(self, x, y):
     ...         self.x, self.y = x, y
     ...     def __str__(self):
     ...         return 'Point({self.x}, {self.y})'.format(self=self)
     ...
     >>> str(Point(4, 2))
     'Point(4, 2)'

存取引數的內容：

     >>> coord = (3, 5)
     >>> 'X: {0[0]};  Y: {0[1]}'.format(coord)
     'X: 3;  Y: 5'

替換 ‘%s’ 和 ‘%r’：

     >>> "repr() shows quotes: {!r}; str() doesn't: {!s}".format('test1', 'test2')
     "repr() shows quotes: 'test1'; str() doesn't: test2"

對齊文字以及指定寬度：

     >>> '{:<30}'.format('left aligned')
     'left aligned                  '
     >>> '{:>30}'.format('right aligned')
     '                 right aligned'
     >>> '{:^30}'.format('centered')
     '           centered           '
     >>> '{:*^30}'.format('centered')  # use '*' as a fill char
     '***********centered***********'

替換 ‘%+f’、‘%-f’ 和 ‘% f’ 以及指定正負號：

     >>> '{:+f}; {:+f}'.format(3.14, -3.14)  # show it always
     '+3.140000; -3.140000'
     >>> '{: f}; {: f}'.format(3.14, -3.14)  # show a space for positive numbers
     ' 3.140000; -3.140000'
     >>> '{:-f}; {:-f}'.format(3.14, -3.14)  # show only the minus -- same as '{:f}; {:f}'
     '3.140000; -3.140000'

替換 ‘%x’ 和 ‘%o’ 並將其值轉換為不同的進位制：

     >>> # format also supports binary numbers
     >>> "int: {0:d};  hex: {0:x};  oct: {0:o};  bin: {0:b}".format(42)
     'int: 42;  hex: 2a;  oct: 52;  bin: 101010'
     >>> # with 0x, 0o, or 0b as prefix:
     >>> "int: {0:d};  hex: {0:#x};  oct: {0:#o};  bin: {0:#b}".format(42)
     'int: 42;  hex: 0x2a;  oct: 0o52;  bin: 0b101010'

使用逗號作為千位分隔符：

     >>> '{:,}'.format(1234567890)
     '1,234,567,890'

表示為百分比：

     >>> points = 19
     >>> total = 22
     >>> 'Correct answers: {:.2%}'.format(points/total)
     'Correct answers: 86.36%'

作為特定型別格式：

     >>> import datetime
     >>> d = datetime.datetime(2010, 7, 4, 12, 15, 58)
     >>> '{:%Y-%m-%d %H:%M:%S}'.format(d)
     '2010-07-04 12:15:58'

巢狀引數及更多複雜範例：

     >>> for align, text in zip('<^>', ['left', 'center', 'right']):
     ...     '{0:{fill}{align}16}'.format(text, fill=align, align=align)
     ...
     'left<<<<<<<<<<<<'
     '^^^^^center^^^^^'
     '>>>>>>>>>>>right'
     >>>
     >>> octets = [192, 168, 0, 1]
     >>> '{:02X}{:02X}{:02X}{:02X}'.format(*octets)
     'C0A80001'
     >>> int(_, 16)
     3232235521
     >>>
     >>> width = 5
     >>> for num in range(5,12):
     ...     for base in 'dXob':
     ...         print('{0:{width}{base}}'.format(num, base=base, width=width), end=' ')
     ...     print()
     ...
         5     5     5   101
         6     6     6   110
         7     7     7   111
         8     8    10  1000
         9     9    11  1001
        10     A    12  1010
        11     B    13  1011


File: python.info,  Node: 模板字串,  Next: 輔助函式,  Prev: 格式化文字語法,  Up: string --- 常見的字串操作

5.6.1.6 模板字串
................

模板字串提供如 PEP 292(1) 所述更簡單的字串替換。模板字串的主要用例是國際
化 (i18n)，因為在這種情況下，更簡單的語法和功能使得它比其他 Python 內建
字串格式化工具更容易翻譯。基於模板字串建構的 i18n 函式庫範例，請參閱
flufl.i18n(2) 套件。

Template strings support ‘$’-based substitutions, using the following
rules:

   * ‘$$’ is an escape; it is replaced with a single ‘$’.

   * ‘$identifier’ names a substitution placeholder matching a mapping
     key of ‘"identifier"’.  By default, ‘"identifier"’ is restricted to
     any case-insensitive ASCII alphanumeric string (including
     underscores) that starts with an underscore or ASCII letter.  The
     first non-identifier character after the ‘$’ character terminates
     this placeholder specification.

   * ‘${identifier}’ is equivalent to ‘$identifier’.  It is required
     when valid identifier characters follow the placeholder but are not
     part of the placeholder, such as ‘"${noun}ification"’.

Any other appearance of ‘$’ in the string will result in a *note
ValueError: 1e7. being raised.

The *note string: be. module provides a *note Template: 62d. class that
implements these rules.  The methods of *note Template: 62d. are:

 -- 類別: string.Template (template)

     The constructor takes a single argument which is the template
     string.

      -- 方法: substitute (mapping={}, /, **kwds)

          進行模板替換，並回傳一個新的字串。 'mapping' 是任何有金鑰並符
          合模板裡佔位符號的字典型物件。或者如果關鍵字就是佔位符號時，你
          也可以改提供關鍵字引數。當 'mapping' 跟 'kwds' 同時給定並存在
          重複時，'kwds' 的佔位符號會被優先使用。

      -- 方法: safe_substitute (mapping={}, /, **kwds)

          類似於 *note substitute(): 1bed.，但如果 'mapping' 與 'kwds' 中
          缺少佔位符號的話，原始的佔位符號會完整地出現在結果字串裡，而不
          會引發 *note KeyError: 2fb. 例外。此外，與 *note substitute():
          1bed. 不同的是，任何包含 ‘$’ 的字句會直接回傳 ‘$’ 而非引發
          *note ValueError: 1e7.。

          雖然仍可能發生其他例外，但這個方法被認為是「安全」的，因為它總
          是試圖回傳一個有用的字串而不是引發例外。從另一個角度來看，
          *note safe_substitute(): 1bee. 可能並非完全安全，因為它會默默
          忽略格式錯誤的模板，這些模板包含了多餘的左右定界符、不匹配的括
          號，或者不是有效的 Python 識別字的佔位符號。

      -- 方法: is_valid ()

          如果模板有將導致 *note substitute(): 1bed. 引發 *note
          ValueError: 1e7. 的無效佔位符號，就會回傳 false。

          在 3.11 版被加入.

      -- 方法: get_identifiers ()

          回傳模板中有效識別字的串列，按照它們首次出現的順序，並忽略任何
          無效的識別字。

          在 3.11 版被加入.

     *note Template: 62d. 實例也提供一個公開的資料屬性：

      -- 屬性: template

          這是傳遞給建構函式 'template' 引數的物件。一般來說，你不應該改
          變它，但並沒有強制設定成唯讀。

以下是如何使用 Template 的一個範例：

     >>> from string import Template
     >>> s = Template('$who likes $what')
     >>> s.substitute(who='tim', what='kung pao')
     'tim likes kung pao'
     >>> d = dict(who='tim')
     >>> Template('Give $who $100').substitute(d)
     Traceback (most recent call last):
     ...
     ValueError: Invalid placeholder in string: line 1, col 11
     >>> Template('$who likes $what').substitute(d)
     Traceback (most recent call last):
     ...
     KeyError: 'what'
     >>> Template('$who likes $what').safe_substitute(d)
     'tim likes $what'

進階用法：你可以衍生 *note Template: 62d. 類別來自定義佔位符號語法、左右
定界符字元，或者用於剖析模板字串的正規表示式。你可以透過覆寫這些類別屬性
來達成：

   * 'delimiter' - 這是描述引入左右定界符的文字字串。預設值是 ‘$’。請注
     意這'不是'正規表示式，因為實作會在需要時對這個字串呼叫 *note
     re.escape(): bb0.。也請注意你不能在建立類別後修改左右定界符。（意即
     在子類別的命名空間中必須設置不同的左右定界符）

   * 'idpattern' - This is the regular expression describing the pattern
     for non-braced placeholders.  The default value is the regular
     expression ‘(?a:[_a-z][_a-z0-9]*)’.  If this is given and
     'braceidpattern' is ‘None’ this pattern will also apply to braced
     placeholders.

          備註: Since default 'flags' is ‘re.IGNORECASE’, pattern
          ‘[a-z]’ can match with some non-ASCII characters.  That's why
          we use the local ‘a’ flag here.

     在 3.7 版的變更: 'braceidpattern' can be used to define separate
     patterns used inside and outside the braces.

   * 'braceidpattern' - This is like 'idpattern' but describes the
     pattern for braced placeholders.  Defaults to ‘None’ which means to
     fall back to 'idpattern' (i.e.  the same pattern is used both
     inside and outside braces).  If given, this allows you to define
     different patterns for braced and unbraced placeholders.

     在 3.7 版被加入.

   * 'flags' - The regular expression flags that will be applied when
     compiling the regular expression used for recognizing
     substitutions.  The default value is ‘re.IGNORECASE’.  Note that
     ‘re.VERBOSE’ will always be added to the flags, so custom
     'idpattern's must follow conventions for verbose regular
     expressions.

     在 3.2 版被加入.

Alternatively, you can provide the entire regular expression pattern by
overriding the class attribute 'pattern'.  If you do this, the value
must be a regular expression object with four named capturing groups.
The capturing groups correspond to the rules given above, along with the
invalid placeholder rule:

   * 'escaped' - 此群組與跳脫序列匹配，例如在預設模式下為 ‘$$’。

   * 'named' - 此群組與不帶大括號的佔位符號名稱匹配；它不應包含擷取群組
     中的左右定界符號。

   * 'braced' - 此群組與大括號括起來的佔位符號名稱匹配；它不應在擷取群組
     中包含左右定界符或大括號。

   * 'invalid' - 此群組與任何其他左右定界符模式（通常是單一左右定界符）
     匹配，且它應該出現在正規表示式的最後。

當此模式有匹配於模板但這些命名組中卻有任一個不匹配，此類別的方法將引發
*note ValueError: 1e7.。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0292/

   (2) https://flufli18n.readthedocs.io/en/latest/


File: python.info,  Node: 輔助函式,  Prev: 模板字串,  Up: string --- 常見的字串操作

5.6.1.7 輔助函式
................

 -- 函式: string.capwords (s, sep=None)

     使用 *note str.split(): e4c. 將引數分割為字詞，使用 *note
     str.capitalize(): 2098. 將每個單字大寫，並使用 *note str.join():
     2088. 將大寫字詞連接起來。如果可選的第二引數 'sep' 不存在或為
     ‘None’，則連續的空白字元將替換為單一空格，並且刪除前導和尾隨空白；
     在其他情況下則使用 'sep' 來分割和連接單字。


File: python.info,  Node: re --- 正規表示式 regular expression 操作,  Next: difflib --- 計算差異的輔助工具,  Prev: string --- 常見的字串操作,  Up: 文本處理 Text Processing 服務

5.6.2 ‘re’ -- 正規表示式 (regular expression) 操作
--------------------------------------------------

'原始碼：'Lib/re/(1)

__________________________________________________________________

此模組提供類似於 Perl 中正規表示式的配對操作。

被搜尋的模式 (pattern) 與字串可以是 Unicode 字串 (*note str: 3f2.)，也可
以是 8-bit 字串 (*note bytes: 1a5.)。然而，Unicode 字串和 8-bit 字串不能
混用：也就是，你不能用 byte 模式配對 Unicode 字串，反之亦然；同樣地，替
換時，用來替換的字串必須與模式和搜尋字串是相同的型別 (type)。

正規表示式使用反斜線字元 (‘'\'’) 表示特別的形式，或是使用特殊字元而不調
用它們的特殊意義。這與 Python 在字串文本 (literal) 中，為了一樣的目的使
用同一個字元的目的相衝突；舉例來說，為了配對一個反斜線文字，一個人可能需
要寫 ‘'\\\\'’ 當作模式字串，因為正規表示式必須是 ‘\\’，而且每個反斜線在
一個普通的 Python 字串文本中必須表示為 ‘\\’。另外，請注意在 Python 的字
串文本中使用反斜線的任何無效跳脫序列目前會產生一個 *note SyntaxWarning:
40c.，而在未來這會變成一個 *note SyntaxError: 173.。儘管它對正規表示式是
一個有效的跳脫序列，這種行為也會發生。

解決方法是對正規表示式模式使用 Python 的原始字串符號；反斜線在一個以
‘'r'’ 為前綴的字串文本中不會被用任何特別的方式處理。所以 ‘r"\n"’ 是一個
兩個字元的字串，包含 ‘'\'’ 和 ‘'n'’，同時 ‘"\n"’ 是一個單個字元的字串，
包含一個換行符號。通常模式在 Python 程式中會使用這個原始字串符號表示。

請務必注意到大部分的正規表示式操作是可以在模組層級的函式和 *note
compiled regular expressions: f29. 中的方法使用的。這些函式是個捷徑且讓
你不需要先編譯一個正規表示式物件，但是會缺少一些微調參數。

也參考
......

第三方的 regex(2) 模組，有著和標準函式庫 *note re: a7. 模組相容的 API，
但是提供額外的功能以及更完整的 Unicode 支援。

* Menu:

* 正規表示式語法::
* 模組內容::
* Regular Expression Objects::
* Match Objects::
* Regular Expression Examples::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/re/

   (2) https://pypi.org/project/regex/


File: python.info,  Node: 正規表示式語法,  Next: 模組內容,  Up: re --- 正規表示式 regular expression 操作

5.6.2.1 正規表示式語法
......................

A regular expression (or RE) specifies a set of strings that matches it;
the functions in this module let you check if a particular string
matches a given regular expression (or if a given regular expression
matches a particular string, which comes down to the same thing).

Regular expressions can be concatenated to form new regular expressions;
if 'A' and 'B' are both regular expressions, then 'AB' is also a regular
expression.  In general, if a string 'p' matches 'A' and another string
'q' matches 'B', the string 'pq' will match AB. This holds unless 'A' or
'B' contain low precedence operations; boundary conditions between 'A'
and 'B'; or have numbered group references.  Thus, complex expressions
can easily be constructed from simpler primitive expressions like the
ones described here.  For details of the theory and implementation of
regular expressions, consult the Friedl book *note [Frie09]: 21c8, or
almost any textbook about compiler construction.

A brief explanation of the format of regular expressions follows.  For
further information and a gentler presentation, consult the *note
如何使用正規表示式: 21c9.

Regular expressions can contain both special and ordinary characters.
Most ordinary characters, like ‘'A'’, ‘'a'’, or ‘'0'’, are the simplest
regular expressions; they simply match themselves.  You can concatenate
ordinary characters, so ‘last’ matches the string ‘'last'’.  (In the
rest of this section, we'll write RE's in ‘this special style’, usually
without quotes, and strings to be matched ‘'in single quotes'’.)

Some characters, like ‘'|'’ or ‘'('’, are special.  Special characters
either stand for classes of ordinary characters, or affect how the
regular expressions around them are interpreted.

Repetition operators or quantifiers (‘*’, ‘+’, ‘?’, ‘{m,n}’, etc) cannot
be directly nested.  This avoids ambiguity with the non-greedy modifier
suffix ‘?’, and with other modifiers in other implementations.  To apply
a second repetition to an inner repetition, parentheses may be used.
For example, the expression ‘(?:a{6})*’ matches any multiple of six
‘'a'’ characters.

The special characters are:

‘.’

     (Dot.)  In the default mode, this matches any character except a
     newline.  If the *note DOTALL: 21ca. flag has been specified, this
     matches any character including a newline.  ‘(?s:.)’ matches any
     character regardless of flags.

‘^’

     (Caret.)  Matches the start of the string, and in *note MULTILINE:
     21cb. mode also matches immediately after each newline.

‘$’

     Matches the end of the string or just before the newline at the end
     of the string, and in *note MULTILINE: 21cb. mode also matches
     before a newline.  ‘foo’ matches both 'foo' and 'foobar', while the
     regular expression ‘foo$’ matches only 'foo'.  More interestingly,
     searching for ‘foo.$’ in ‘'foo1\nfoo2\n'’ matches 'foo2' normally,
     but 'foo1' in *note MULTILINE: 21cb. mode; searching for a single
     ‘$’ in ‘'foo\n'’ will find two (empty) matches: one just before the
     newline, and one at the end of the string.

‘*’

     Causes the resulting RE to match 0 or more repetitions of the
     preceding RE, as many repetitions as are possible.  ‘ab*’ will
     match 'a', 'ab', or 'a' followed by any number of 'b's.

‘+’

     Causes the resulting RE to match 1 or more repetitions of the
     preceding RE. ‘ab+’ will match 'a' followed by any non-zero number
     of 'b's; it will not match just 'a'.

‘?’

     Causes the resulting RE to match 0 or 1 repetitions of the
     preceding RE. ‘ab?’ will match either 'a' or 'ab'.

‘*?’, ‘+?’, ‘??’

     The ‘'*'’, ‘'+'’, and ‘'?'’ quantifiers are all 'greedy'; they
     match as much text as possible.  Sometimes this behaviour isn't
     desired; if the RE ‘<.*>’ is matched against ‘'<a> b <c>'’, it will
     match the entire string, and not just ‘'<a>'’.  Adding ‘?’ after
     the quantifier makes it perform the match in 'non-greedy' or
     'minimal' fashion; as 'few' characters as possible will be matched.
     Using the RE ‘<.*?>’ will match only ‘'<a>'’.

‘*+’, ‘++’, ‘?+’

     Like the ‘'*'’, ‘'+'’, and ‘'?'’ quantifiers, those where ‘'+'’ is
     appended also match as many times as possible.  However, unlike the
     true greedy quantifiers, these do not allow back-tracking when the
     expression following it fails to match.  These are known as
     'possessive' quantifiers.  For example, ‘a*a’ will match ‘'aaaa'’
     because the ‘a*’ will match all 4 ‘'a'’s, but, when the final ‘'a'’
     is encountered, the expression is backtracked so that in the end
     the ‘a*’ ends up matching 3 ‘'a'’s total, and the fourth ‘'a'’ is
     matched by the final ‘'a'’.  However, when ‘a*+a’ is used to match
     ‘'aaaa'’, the ‘a*+’ will match all 4 ‘'a'’, but when the final
     ‘'a'’ fails to find any more characters to match, the expression
     cannot be backtracked and will thus fail to match.  ‘x*+’, ‘x++’
     and ‘x?+’ are equivalent to ‘(?>x*)’, ‘(?>x+)’ and ‘(?>x?)’
     correspondingly.

     在 3.11 版被加入.

‘{m}’

     Specifies that exactly 'm' copies of the previous RE should be
     matched; fewer matches cause the entire RE not to match.  For
     example, ‘a{6}’ will match exactly six ‘'a'’ characters, but not
     five.

‘{m,n}’

     Causes the resulting RE to match from 'm' to 'n' repetitions of the
     preceding RE, attempting to match as many repetitions as possible.
     For example, ‘a{3,5}’ will match from 3 to 5 ‘'a'’ characters.
     Omitting 'm' specifies a lower bound of zero, and omitting 'n'
     specifies an infinite upper bound.  As an example, ‘a{4,}b’ will
     match ‘'aaaab'’ or a thousand ‘'a'’ characters followed by a ‘'b'’,
     but not ‘'aaab'’.  The comma may not be omitted or the modifier
     would be confused with the previously described form.

‘{m,n}?’

     Causes the resulting RE to match from 'm' to 'n' repetitions of the
     preceding RE, attempting to match as 'few' repetitions as possible.
     This is the non-greedy version of the previous quantifier.  For
     example, on the 6-character string ‘'aaaaaa'’, ‘a{3,5}’ will match
     5 ‘'a'’ characters, while ‘a{3,5}?’ will only match 3 characters.

‘{m,n}+’

     Causes the resulting RE to match from 'm' to 'n' repetitions of the
     preceding RE, attempting to match as many repetitions as possible
     'without' establishing any backtracking points.  This is the
     possessive version of the quantifier above.  For example, on the
     6-character string ‘'aaaaaa'’, ‘a{3,5}+aa’ attempt to match 5 ‘'a'’
     characters, then, requiring 2 more ‘'a'’s, will need more
     characters than available and thus fail, while ‘a{3,5}aa’ will
     match with ‘a{3,5}’ capturing 5, then 4 ‘'a'’s by backtracking and
     then the final 2 ‘'a'’s are matched by the final ‘aa’ in the
     pattern.  ‘x{m,n}+’ is equivalent to ‘(?>x{m,n})’.

     在 3.11 版被加入.

‘\’

     Either escapes special characters (permitting you to match
     characters like ‘'*'’, ‘'?'’, and so forth), or signals a special
     sequence; special sequences are discussed below.

     If you're not using a raw string to express the pattern, remember
     that Python also uses the backslash as an escape sequence in string
     literals; if the escape sequence isn't recognized by Python's
     parser, the backslash and subsequent character are included in the
     resulting string.  However, if Python would recognize the resulting
     sequence, the backslash should be repeated twice.  This is
     complicated and hard to understand, so it's highly recommended that
     you use raw strings for all but the simplest expressions.

‘[]’

     Used to indicate a set of characters.  In a set:

        * Characters can be listed individually, e.g.  ‘[amk]’ will
          match ‘'a'’, ‘'m'’, or ‘'k'’.

        * Ranges of characters can be indicated by giving two characters
          and separating them by a ‘'-'’, for example ‘[a-z]’ will match
          any lowercase ASCII letter, ‘[0-5][0-9]’ will match all the
          two-digits numbers from ‘00’ to ‘59’, and ‘[0-9A-Fa-f]’ will
          match any hexadecimal digit.  If ‘-’ is escaped (e.g.
          ‘[a\-z]’) or if it's placed as the first or last character
          (e.g.  ‘[-a]’ or ‘[a-]’), it will match a literal ‘'-'’.

        * Special characters lose their special meaning inside sets.
          For example, ‘[(+*)]’ will match any of the literal characters
          ‘'('’, ‘'+'’, ‘'*'’, or ‘')'’.

        * Character classes such as ‘\w’ or ‘\S’ (defined below) are
          also accepted inside a set, although the characters they match
          depend on the *note flags: 21cc. used.

        * Characters that are not within a range can be matched by
          'complementing' the set.  If the first character of the set is
          ‘'^'’, all the characters that are 'not' in the set will be
          matched.  For example, ‘[^5]’ will match any character except
          ‘'5'’, and ‘[^^]’ will match any character except ‘'^'’.  ‘^’
          has no special meaning if it's not the first character in the
          set.

        * To match a literal ‘']'’ inside a set, precede it with a
          backslash, or place it at the beginning of the set.  For
          example, both ‘[()[\]{}]’ and ‘[]()[{}]’ will match a right
          bracket, as well as left bracket, braces, and parentheses.

        * Support of nested sets and set operations as in Unicode
          Technical Standard #18(1) might be added in the future.  This
          would change the syntax, so to facilitate this change a *note
          FutureWarning: 357. will be raised in ambiguous cases for the
          time being.  That includes sets starting with a literal ‘'['’
          or containing literal character sequences ‘'--'’, ‘'&&'’,
          ‘'~~'’, and ‘'||'’.  To avoid a warning escape them with a
          backslash.

     在 3.7 版的變更: *note FutureWarning: 357. is raised if a character
     set contains constructs that will change semantically in the
     future.

‘|’

     ‘A|B’, where 'A' and 'B' can be arbitrary REs, creates a regular
     expression that will match either 'A' or 'B'. An arbitrary number
     of REs can be separated by the ‘'|'’ in this way.  This can be used
     inside groups (see below) as well.  As the target string is
     scanned, REs separated by ‘'|'’ are tried from left to right.  When
     one pattern completely matches, that branch is accepted.  This
     means that once 'A' matches, 'B' will not be tested further, even
     if it would produce a longer overall match.  In other words, the
     ‘'|'’ operator is never greedy.  To match a literal ‘'|'’, use
     ‘\|’, or enclose it inside a character class, as in ‘[|]’.

‘(...)’

     Matches whatever regular expression is inside the parentheses, and
     indicates the start and end of a group; the contents of a group can
     be retrieved after a match has been performed, and can be matched
     later in the string with the ‘\number’ special sequence, described
     below.  To match the literals ‘'('’ or ‘')'’, use ‘\(’ or ‘\)’, or
     enclose them inside a character class: ‘[(]’, ‘[)]’.

‘(?...)’

     This is an extension notation (a ‘'?'’ following a ‘'('’ is not
     meaningful otherwise).  The first character after the ‘'?'’
     determines what the meaning and further syntax of the construct is.
     Extensions usually do not create a new group; ‘(?P<name>...)’ is
     the only exception to this rule.  Following are the currently
     supported extensions.

‘(?aiLmsux)’

     (One or more letters from the set ‘'a'’, ‘'i'’, ‘'L'’, ‘'m'’,
     ‘'s'’, ‘'u'’, ‘'x'’.)  The group matches the empty string; the
     letters set the corresponding flags for the entire regular
     expression:

        * *note re.A: 21cd. (ASCII-only matching)

        * *note re.I: 21ce. (ignore case)

        * *note re.L: 21cf. (locale dependent)

        * *note re.M: 21d0. (multi-line)

        * *note re.S: 21d1. (dot matches all)

        * *note re.U: 21d2. (Unicode matching)

        * *note re.X: 21d3. (verbose)

     (The flags are described in *note 模組內容: 21d4.)  This is useful
     if you wish to include the flags as part of the regular expression,
     instead of passing a 'flag' argument to the *note re.compile():
     b7a. function.  Flags should be used first in the expression
     string.

     在 3.11 版的變更: This construction can only be used at the start
     of the expression.

‘(?:...)’

     A non-capturing version of regular parentheses.  Matches whatever
     regular expression is inside the parentheses, but the substring
     matched by the group 'cannot' be retrieved after performing a match
     or referenced later in the pattern.

‘(?aiLmsux-imsx:...)’

     (Zero or more letters from the set ‘'a'’, ‘'i'’, ‘'L'’, ‘'m'’,
     ‘'s'’, ‘'u'’, ‘'x'’, optionally followed by ‘'-'’ followed by one
     or more letters from the ‘'i'’, ‘'m'’, ‘'s'’, ‘'x'’.)  The letters
     set or remove the corresponding flags for the part of the
     expression:

        * *note re.A: 21cd. (ASCII-only matching)

        * *note re.I: 21ce. (ignore case)

        * *note re.L: 21cf. (locale dependent)

        * *note re.M: 21d0. (multi-line)

        * *note re.S: 21d1. (dot matches all)

        * *note re.U: 21d2. (Unicode matching)

        * *note re.X: 21d3. (verbose)

     (The flags are described in *note 模組內容: 21d4.)

     The letters ‘'a'’, ‘'L'’ and ‘'u'’ are mutually exclusive when used
     as inline flags, so they can't be combined or follow ‘'-'’.
     Instead, when one of them appears in an inline group, it overrides
     the matching mode in the enclosing group.  In Unicode patterns
     ‘(?a:...)’ switches to ASCII-only matching, and ‘(?u:...)’ switches
     to Unicode matching (default).  In bytes patterns ‘(?L:...)’
     switches to locale dependent matching, and ‘(?a:...)’ switches to
     ASCII-only matching (default).  This override is only in effect for
     the narrow inline group, and the original matching mode is restored
     outside of the group.

     在 3.6 版被加入.

     在 3.7 版的變更: The letters ‘'a'’, ‘'L'’ and ‘'u'’ also can be
     used in a group.

‘(?>...)’

     Attempts to match ‘...’ as if it was a separate regular expression,
     and if successful, continues to match the rest of the pattern
     following it.  If the subsequent pattern fails to match, the stack
     can only be unwound to a point 'before' the ‘(?>...)’ because once
     exited, the expression, known as an 'atomic group', has thrown away
     all stack points within itself.  Thus, ‘(?>.*).’ would never match
     anything because first the ‘.*’ would match all characters
     possible, then, having nothing left to match, the final ‘.’ would
     fail to match.  Since there are no stack points saved in the Atomic
     Group, and there is no stack point before it, the entire expression
     would thus fail to match.

     在 3.11 版被加入.

‘(?P<name>...)’

     Similar to regular parentheses, but the substring matched by the
     group is accessible via the symbolic group name 'name'.  Group
     names must be valid Python identifiers, and in *note bytes: 1a5.
     patterns they can only contain bytes in the ASCII range.  Each
     group name must be defined only once within a regular expression.
     A symbolic group is also a numbered group, just as if the group
     were not named.

     Named groups can be referenced in three contexts.  If the pattern
     is ‘(?P<quote>['"]).*?(?P=quote)’ (i.e.  matching a string quoted
     with either single or double quotes):

     Context of reference to group "quote"       Ways to reference it
                                                 
     -----------------------------------------------------------------------------------
                                                 
     in the same pattern itself                     * ‘(?P=quote)’ (as shown)
                                                 
                                                    * ‘\1’
                                                 
                                                 
     when processing match object 'm'               * ‘m.group('quote')’
                                                 
                                                    * ‘m.end('quote')’ (etc.)
                                                 
                                                 
     in a string passed to the 'repl' argument      * ‘\g<quote>’
     of ‘re.sub()’                               
                                                    * ‘\g<1>’
                                                 
                                                    * ‘\1’
                                                 

     在 3.12 版的變更: In *note bytes: 1a5. patterns, group 'name' can
     only contain bytes in the ASCII range (‘b'\x00'’-‘b'\x7f'’).

‘(?P=name)’

     A backreference to a named group; it matches whatever text was
     matched by the earlier group named 'name'.

‘(?#...)’

     A comment; the contents of the parentheses are simply ignored.

‘(?=...)’

     Matches if ‘...’ matches next, but doesn't consume any of the
     string.  This is called a 'lookahead assertion'.  For example,
     ‘Isaac (?=Asimov)’ will match ‘'Isaac '’ only if it's followed by
     ‘'Asimov'’.

‘(?!...)’

     Matches if ‘...’ doesn't match next.  This is a 'negative lookahead
     assertion'.  For example, ‘Isaac (?!Asimov)’ will match ‘'Isaac '’
     only if it's 'not' followed by ‘'Asimov'’.

‘(?<=...)’

     Matches if the current position in the string is preceded by a
     match for ‘...’ that ends at the current position.  This is called
     a 'positive lookbehind assertion'.  ‘(?<=abc)def’ will find a match
     in ‘'abcdef'’, since the lookbehind will back up 3 characters and
     check if the contained pattern matches.  The contained pattern must
     only match strings of some fixed length, meaning that ‘abc’ or
     ‘a|b’ are allowed, but ‘a*’ and ‘a{3,4}’ are not.  Note that
     patterns which start with positive lookbehind assertions will not
     match at the beginning of the string being searched; you will most
     likely want to use the *note search(): 11c4. function rather than
     the *note match(): 11c5. function:

          >>> import re
          >>> m = re.search('(?<=abc)def', 'abcdef')
          >>> m.group(0)
          'def'

     This example looks for a word following a hyphen:

          >>> m = re.search(r'(?<=-)\w+', 'spam-egg')
          >>> m.group(0)
          'egg'

     在 3.5 版的變更: Added support for group references of fixed
     length.

‘(?<!...)’

     Matches if the current position in the string is not preceded by a
     match for ‘...’.  This is called a 'negative lookbehind assertion'.
     Similar to positive lookbehind assertions, the contained pattern
     must only match strings of some fixed length.  Patterns which start
     with negative lookbehind assertions may match at the beginning of
     the string being searched.

‘(?(id/name)yes-pattern|no-pattern)’

     Will try to match with ‘yes-pattern’ if the group with given 'id'
     or 'name' exists, and with ‘no-pattern’ if it doesn't.
     ‘no-pattern’ is optional and can be omitted.  For example,
     ‘(<)?(\w+@\w+(?:\.\w+)+)(?(1)>|$)’ is a poor email matching
     pattern, which will match with ‘'<user@host.com>'’ as well as
     ‘'user@host.com'’, but not with ‘'<user@host.com'’ nor
     ‘'user@host.com>'’.

     在 3.12 版的變更: Group 'id' can only contain ASCII digits.  In
     *note bytes: 1a5. patterns, group 'name' can only contain bytes in
     the ASCII range (‘b'\x00'’-‘b'\x7f'’).

The special sequences consist of ‘'\'’ and a character from the list
below.  If the ordinary character is not an ASCII digit or an ASCII
letter, then the resulting RE will match the second character.  For
example, ‘\$’ matches the character ‘'$'’.

‘\number’

     Matches the contents of the group of the same number.  Groups are
     numbered starting from 1.  For example, ‘(.+) \1’ matches ‘'the
     the'’ or ‘'55 55'’, but not ‘'thethe'’ (note the space after the
     group).  This special sequence can only be used to match one of the
     first 99 groups.  If the first digit of 'number' is 0, or 'number'
     is 3 octal digits long, it will not be interpreted as a group
     match, but as the character with octal value 'number'.  Inside the
     ‘'['’ and ‘']'’ of a character class, all numeric escapes are
     treated as characters.

‘\A’

     Matches only at the start of the string.

‘\b’

     Matches the empty string, but only at the beginning or end of a
     word.  A word is defined as a sequence of word characters.  Note
     that formally, ‘\b’ is defined as the boundary between a ‘\w’ and a
     ‘\W’ character (or vice versa), or between ‘\w’ and the beginning
     or end of the string.  This means that ‘r'\bat\b'’ matches ‘'at'’,
     ‘'at.'’, ‘'(at)'’, and ‘'as at ay'’ but not ‘'attempt'’ or
     ‘'atlas'’.

     The default word characters in Unicode (str) patterns are Unicode
     alphanumerics and the underscore, but this can be changed by using
     the *note ASCII: 5d3. flag.  Word boundaries are determined by the
     current locale if the *note LOCALE: b10. flag is used.

          備註: Inside a character range, ‘\b’ represents the backspace
          character, for compatibility with Python's string literals.

‘\B’

     Matches the empty string, but only when it is 'not' at the
     beginning or end of a word.  This means that ‘r'at\B'’ matches
     ‘'athens'’, ‘'atom'’, ‘'attorney'’, but not ‘'at'’, ‘'at.'’, or
     ‘'at!'’.  ‘\B’ is the opposite of ‘\b’, so word characters in
     Unicode (str) patterns are Unicode alphanumerics or the underscore,
     although this can be changed by using the *note ASCII: 5d3. flag.
     Word boundaries are determined by the current locale if the *note
     LOCALE: b10. flag is used.

‘\d’

     For Unicode (str) patterns:

          Matches any Unicode decimal digit (that is, any character in
          Unicode character category [Nd](2)).  This includes ‘[0-9]’,
          and also many other digit characters.

          Matches ‘[0-9]’ if the *note ASCII: 5d3. flag is used.

     For 8-bit (bytes) patterns:

          Matches any decimal digit in the ASCII character set; this is
          equivalent to ‘[0-9]’.

‘\D’

     Matches any character which is not a decimal digit.  This is the
     opposite of ‘\d’.

     Matches ‘[^0-9]’ if the *note ASCII: 5d3. flag is used.

‘\s’

     For Unicode (str) patterns:

          Matches Unicode whitespace characters (as defined by *note
          str.isspace(): 20a1.).  This includes ‘[ \t\n\r\f\v]’, and
          also many other characters, for example the non-breaking
          spaces mandated by typography rules in many languages.

          Matches ‘[ \t\n\r\f\v]’ if the *note ASCII: 5d3. flag is used.

     For 8-bit (bytes) patterns:

          Matches characters considered whitespace in the ASCII
          character set; this is equivalent to ‘[ \t\n\r\f\v]’.

‘\S’

     Matches any character which is not a whitespace character.  This is
     the opposite of ‘\s’.

     Matches ‘[^ \t\n\r\f\v]’ if the *note ASCII: 5d3. flag is used.

‘\w’

     For Unicode (str) patterns:

          Matches Unicode word characters; this includes all Unicode
          alphanumeric characters (as defined by *note str.isalnum():
          209a.), as well as the underscore (‘_’).

          Matches ‘[a-zA-Z0-9_]’ if the *note ASCII: 5d3. flag is used.

     For 8-bit (bytes) patterns:

          Matches characters considered alphanumeric in the ASCII
          character set; this is equivalent to ‘[a-zA-Z0-9_]’.  If the
          *note LOCALE: b10. flag is used, matches characters considered
          alphanumeric in the current locale and the underscore.

‘\W’

     Matches any character which is not a word character.  This is the
     opposite of ‘\w’.  By default, matches non-underscore (‘_’)
     characters for which *note str.isalnum(): 209a. returns ‘False’.

     Matches ‘[^a-zA-Z0-9_]’ if the *note ASCII: 5d3. flag is used.

     If the *note LOCALE: b10. flag is used, matches characters which
     are neither alphanumeric in the current locale nor the underscore.

‘\Z’

     Matches only at the end of the string.

Most of the *note escape sequences: 400. supported by Python string
literals are also accepted by the regular expression parser:

     \a      \b      \f      \n
     \N      \r      \t      \u
     \U      \v      \x      \\

(Note that ‘\b’ is used to represent word boundaries, and means
"backspace" only inside character classes.)

‘'\u'’, ‘'\U'’, and ‘'\N'’ escape sequences are only recognized in
Unicode (str) patterns.  In bytes patterns they are errors.  Unknown
escapes of ASCII letters are reserved for future use and treated as
errors.

Octal escapes are included in a limited form.  If the first digit is a
0, or if there are three octal digits, it is considered an octal escape.
Otherwise, it is a group reference.  As for string literals, octal
escapes are always at most three digits in length.

在 3.3 版的變更: The ‘'\u'’ and ‘'\U'’ escape sequences have been added.

在 3.6 版的變更: Unknown escapes consisting of ‘'\'’ and an ASCII letter
now are errors.

在 3.8 版的變更: The ‘'\N{NAME}'’ escape sequence has been added.  As in
string literals, it expands to the named Unicode character (e.g.
‘'\N{EM DASH}'’).

   ---------- Footnotes ----------

   (1) https://unicode.org/reports/tr18/

   (2) https://www.unicode.org/versions/Unicode15.0.0/ch04.pdf#G134153


File: python.info,  Node: 模組內容,  Next: Regular Expression Objects,  Prev: 正規表示式語法,  Up: re --- 正規表示式 regular expression 操作

5.6.2.2 模組內容
................

The module defines several functions, constants, and an exception.  Some
of the functions are simplified versions of the full featured methods
for compiled regular expressions.  Most non-trivial applications always
use the compiled form.

* Menu:

* 旗標::
* Functions::
* Exceptions::


File: python.info,  Node: 旗標,  Next: Functions,  Up: 模組內容

5.6.2.3 旗標
............

在 3.6 版的變更: Flag constants are now instances of *note RegexFlag:
5d2, which is a subclass of *note enum.IntFlag: 21d7.

 -- 類別: re.RegexFlag

     An *note enum.IntFlag: 21d7. class containing the regex options
     listed below.

     在 3.11 版被加入: - added to ‘__all__’

 -- 資料: re.A
 -- 資料: re.ASCII

     Make ‘\w’, ‘\W’, ‘\b’, ‘\B’, ‘\d’, ‘\D’, ‘\s’ and ‘\S’ perform
     ASCII-only matching instead of full Unicode matching.  This is only
     meaningful for Unicode (str) patterns, and is ignored for bytes
     patterns.

     Corresponds to the inline flag ‘(?a)’.

          備註: The *note U: 21d2. flag still exists for backward
          compatibility, but is redundant in Python 3 since matches are
          Unicode by default for ‘str’ patterns, and Unicode matching
          isn't allowed for bytes patterns.  *note UNICODE: b11. and the
          inline flag ‘(?u)’ are similarly redundant.

 -- 資料: re.DEBUG

     Display debug information about compiled expression.

     No corresponding inline flag.

 -- 資料: re.I
 -- 資料: re.IGNORECASE

     Perform case-insensitive matching; expressions like ‘[A-Z]’ will
     also match lowercase letters.  Full Unicode matching (such as ‘Ü’
     matching ‘ü’) also works unless the *note ASCII: 5d3. flag is used
     to disable non-ASCII matches.  The current locale does not change
     the effect of this flag unless the *note LOCALE: b10. flag is also
     used.

     Corresponds to the inline flag ‘(?i)’.

     Note that when the Unicode patterns ‘[a-z]’ or ‘[A-Z]’ are used in
     combination with the *note IGNORECASE: 1623. flag, they will match
     the 52 ASCII letters and 4 additional non-ASCII letters: 'İ'
     (U+0130, Latin capital letter I with dot above), 'ı' (U+0131, Latin
     small letter dotless i), 'ſ' (U+017F, Latin small letter long s)
     and 'K' (U+212A, Kelvin sign).  If the *note ASCII: 5d3. flag is
     used, only letters 'a' to 'z' and 'A' to 'Z' are matched.

 -- 資料: re.L
 -- 資料: re.LOCALE

     Make ‘\w’, ‘\W’, ‘\b’, ‘\B’ and case-insensitive matching dependent
     on the current locale.  This flag can be used only with bytes
     patterns.

     Corresponds to the inline flag ‘(?L)’.

          警告: This flag is discouraged; consider Unicode matching
          instead.  The locale mechanism is very unreliable as it only
          handles one "culture" at a time and only works with 8-bit
          locales.  Unicode matching is enabled by default for Unicode
          (str) patterns and it is able to handle different locales and
          languages.

     在 3.6 版的變更: *note LOCALE: b10. can be used only with bytes
     patterns and is not compatible with *note ASCII: 5d3.

     在 3.7 版的變更: Compiled regular expression objects with the *note
     LOCALE: b10. flag no longer depend on the locale at compile time.
     Only the locale at matching time affects the result of matching.

 -- 資料: re.M
 -- 資料: re.MULTILINE

     When specified, the pattern character ‘'^'’ matches at the
     beginning of the string and at the beginning of each line
     (immediately following each newline); and the pattern character
     ‘'$'’ matches at the end of the string and at the end of each line
     (immediately preceding each newline).  By default, ‘'^'’ matches
     only at the beginning of the string, and ‘'$'’ only at the end of
     the string and immediately before the newline (if any) at the end
     of the string.

     Corresponds to the inline flag ‘(?m)’.

 -- 資料: re.NOFLAG

     Indicates no flag being applied, the value is ‘0’.  This flag may
     be used as a default value for a function keyword argument or as a
     base value that will be conditionally ORed with other flags.
     Example of use as a default value:

          def myfunc(text, flag=re.NOFLAG):
              return re.match(text, flag)

     在 3.11 版被加入.

 -- 資料: re.S
 -- 資料: re.DOTALL

     Make the ‘'.'’ special character match any character at all,
     including a newline; without this flag, ‘'.'’ will match anything
     'except' a newline.

     Corresponds to the inline flag ‘(?s)’.

 -- 資料: re.U
 -- 資料: re.UNICODE

     In Python 3, Unicode characters are matched by default for ‘str’
     patterns.  This flag is therefore redundant with 'no effect' and is
     only kept for backward compatibility.

     See *note ASCII: 5d3. to restrict matching to ASCII characters
     instead.

 -- 資料: re.X
 -- 資料: re.VERBOSE

     This flag allows you to write regular expressions that look nicer
     and are more readable by allowing you to visually separate logical
     sections of the pattern and add comments.  Whitespace within the
     pattern is ignored, except when in a character class, or when
     preceded by an unescaped backslash, or within tokens like ‘*?’,
     ‘(?:’ or ‘(?P<...>’.  For example, ‘(? :’ and ‘* ?’ are not
     allowed.  When a line contains a ‘#’ that is not in a character
     class and is not preceded by an unescaped backslash, all characters
     from the leftmost such ‘#’ through the end of the line are ignored.

     This means that the two following regular expression objects that
     match a decimal number are functionally equal:

          a = re.compile(r"""\d +  # the integral part
                             \.    # the decimal point
                             \d *  # some fractional digits""", re.X)
          b = re.compile(r"\d+\.\d*")

     Corresponds to the inline flag ‘(?x)’.


File: python.info,  Node: Functions,  Next: Exceptions,  Prev: 旗標,  Up: 模組內容

5.6.2.4 Functions
.................

 -- 函式: re.compile (pattern, flags=0)

     Compile a regular expression pattern into a *note regular
     expression object: f29, which can be used for matching using its
     *note match(): 21dc, *note search(): 21dd. and other methods,
     described below.

     The expression's behaviour can be modified by specifying a 'flags'
     value.  Values can be any of the *note flags: 21cc. variables,
     combined using bitwise OR (the ‘|’ operator).

     The sequence

          prog = re.compile(pattern)
          result = prog.match(string)

     等價於：

          result = re.match(pattern, string)

     but using *note re.compile(): b7a. and saving the resulting regular
     expression object for reuse is more efficient when the expression
     will be used several times in a single program.

          備註: The compiled versions of the most recent patterns passed
          to *note re.compile(): b7a. and the module-level matching
          functions are cached, so programs that use only a few regular
          expressions at a time needn't worry about compiling regular
          expressions.

 -- 函式: re.search (pattern, string, flags=0)

     Scan through 'string' looking for the first location where the
     regular expression 'pattern' produces a match, and return a
     corresponding *note Match: c6f.  Return ‘None’ if no position in
     the string matches the pattern; note that this is different from
     finding a zero-length match at some point in the string.

     The expression's behaviour can be modified by specifying a 'flags'
     value.  Values can be any of the *note flags: 21cc. variables,
     combined using bitwise OR (the ‘|’ operator).

 -- 函式: re.match (pattern, string, flags=0)

     If zero or more characters at the beginning of 'string' match the
     regular expression 'pattern', return a corresponding *note Match:
     c6f.  Return ‘None’ if the string does not match the pattern; note
     that this is different from a zero-length match.

     Note that even in *note MULTILINE: 21cb. mode, *note re.match():
     11c5. will only match at the beginning of the string and not at the
     beginning of each line.

     If you want to locate a match anywhere in 'string', use *note
     search(): 11c4. instead (see also *note search() vs.  match():
     21de.).

     The expression's behaviour can be modified by specifying a 'flags'
     value.  Values can be any of the *note flags: 21cc. variables,
     combined using bitwise OR (the ‘|’ operator).

 -- 函式: re.fullmatch (pattern, string, flags=0)

     If the whole 'string' matches the regular expression 'pattern',
     return a corresponding *note Match: c6f.  Return ‘None’ if the
     string does not match the pattern; note that this is different from
     a zero-length match.

     The expression's behaviour can be modified by specifying a 'flags'
     value.  Values can be any of the *note flags: 21cc. variables,
     combined using bitwise OR (the ‘|’ operator).

     在 3.4 版被加入.

 -- 函式: re.split (pattern, string, maxsplit=0, flags=0)

     Split 'string' by the occurrences of 'pattern'.  If capturing
     parentheses are used in 'pattern', then the text of all groups in
     the pattern are also returned as part of the resulting list.  If
     'maxsplit' is nonzero, at most 'maxsplit' splits occur, and the
     remainder of the string is returned as the final element of the
     list.

          >>> re.split(r'\W+', 'Words, words, words.')
          ['Words', 'words', 'words', '']
          >>> re.split(r'(\W+)', 'Words, words, words.')
          ['Words', ', ', 'words', ', ', 'words', '.', '']
          >>> re.split(r'\W+', 'Words, words, words.', maxsplit=1)
          ['Words', 'words, words.']
          >>> re.split('[a-f]+', '0a3B9', flags=re.IGNORECASE)
          ['0', '3', '9']

     If there are capturing groups in the separator and it matches at
     the start of the string, the result will start with an empty
     string.  The same holds for the end of the string:

          >>> re.split(r'(\W+)', '...words, words...')
          ['', '...', 'words', ', ', 'words', '...', '']

     That way, separator components are always found at the same
     relative indices within the result list.

     Empty matches for the pattern split the string only when not
     adjacent to a previous empty match.

          >>> re.split(r'\b', 'Words, words, words.')
          ['', 'Words', ', ', 'words', ', ', 'words', '.']
          >>> re.split(r'\W*', '...words...')
          ['', '', 'w', 'o', 'r', 'd', 's', '', '']
          >>> re.split(r'(\W*)', '...words...')
          ['', '...', '', '', 'w', '', 'o', '', 'r', '', 'd', '', 's', '...', '', '', '']

     The expression's behaviour can be modified by specifying a 'flags'
     value.  Values can be any of the *note flags: 21cc. variables,
     combined using bitwise OR (the ‘|’ operator).

     在 3.1 版的變更: 新增可選的旗標引數。

     在 3.7 版的變更: Added support of splitting on a pattern that could
     match an empty string.

     在 3.13 版之後被棄用: Passing 'maxsplit' and 'flags' as positional
     arguments is deprecated.  In future Python versions they will be
     *note keyword-only parameters: 285.

 -- 函式: re.findall (pattern, string, flags=0)

     Return all non-overlapping matches of 'pattern' in 'string', as a
     list of strings or tuples.  The 'string' is scanned left-to-right,
     and matches are returned in the order found.  Empty matches are
     included in the result.

     The result depends on the number of capturing groups in the
     pattern.  If there are no groups, return a list of strings matching
     the whole pattern.  If there is exactly one group, return a list of
     strings matching that group.  If multiple groups are present,
     return a list of tuples of strings matching the groups.
     Non-capturing groups do not affect the form of the result.

          >>> re.findall(r'\bf[a-z]*', 'which foot or hand fell fastest')
          ['foot', 'fell', 'fastest']
          >>> re.findall(r'(\w+)=(\d+)', 'set width=20 and height=10')
          [('width', '20'), ('height', '10')]

     The expression's behaviour can be modified by specifying a 'flags'
     value.  Values can be any of the *note flags: 21cc. variables,
     combined using bitwise OR (the ‘|’ operator).

     在 3.7 版的變更: Non-empty matches can now start just after a
     previous empty match.

 -- 函式: re.finditer (pattern, string, flags=0)

     Return an *note iterator: 192. yielding *note Match: c6f. objects
     over all non-overlapping matches for the RE 'pattern' in 'string'.
     The 'string' is scanned left-to-right, and matches are returned in
     the order found.  Empty matches are included in the result.

     The expression's behaviour can be modified by specifying a 'flags'
     value.  Values can be any of the *note flags: 21cc. variables,
     combined using bitwise OR (the ‘|’ operator).

     在 3.7 版的變更: Non-empty matches can now start just after a
     previous empty match.

 -- 函式: re.sub (pattern, repl, string, count=0, flags=0)

     Return the string obtained by replacing the leftmost
     non-overlapping occurrences of 'pattern' in 'string' by the
     replacement 'repl'.  If the pattern isn't found, 'string' is
     returned unchanged.  'repl' can be a string or a function; if it is
     a string, any backslash escapes in it are processed.  That is, ‘\n’
     is converted to a single newline character, ‘\r’ is converted to a
     carriage return, and so forth.  Unknown escapes of ASCII letters
     are reserved for future use and treated as errors.  Other unknown
     escapes such as ‘\&’ are left alone.  Backreferences, such as ‘\6’,
     are replaced with the substring matched by group 6 in the pattern.
     For example:

          >>> re.sub(r'def\s+([a-zA-Z_][a-zA-Z_0-9]*)\s*\(\s*\):',
          ...        r'static PyObject*\npy_\1(void)\n{',
          ...        'def myfunc():')
          'static PyObject*\npy_myfunc(void)\n{'

     If 'repl' is a function, it is called for every non-overlapping
     occurrence of 'pattern'.  The function takes a single *note Match:
     c6f. argument, and returns the replacement string.  For example:

          >>> def dashrepl(matchobj):
          ...     if matchobj.group(0) == '-': return ' '
          ...     else: return '-'
          ...
          >>> re.sub('-{1,2}', dashrepl, 'pro----gram-files')
          'pro--gram files'
          >>> re.sub(r'\sAND\s', ' & ', 'Baked Beans And Spam', flags=re.IGNORECASE)
          'Baked Beans & Spam'

     The pattern may be a string or a *note Pattern: 16e2.

     The optional argument 'count' is the maximum number of pattern
     occurrences to be replaced; 'count' must be a non-negative integer.
     If omitted or zero, all occurrences will be replaced.  Empty
     matches for the pattern are replaced only when not adjacent to a
     previous empty match, so ‘sub('x*', '-', 'abxd')’ returns
     ‘'-a-b--d-'’.

     In string-type 'repl' arguments, in addition to the character
     escapes and backreferences described above, ‘\g<name>’ will use the
     substring matched by the group named ‘name’, as defined by the
     ‘(?P<name>...)’ syntax.  ‘\g<number>’ uses the corresponding group
     number; ‘\g<2>’ is therefore equivalent to ‘\2’, but isn't
     ambiguous in a replacement such as ‘\g<2>0’.  ‘\20’ would be
     interpreted as a reference to group 20, not a reference to group 2
     followed by the literal character ‘'0'’.  The backreference ‘\g<0>’
     substitutes in the entire substring matched by the RE.

     The expression's behaviour can be modified by specifying a 'flags'
     value.  Values can be any of the *note flags: 21cc. variables,
     combined using bitwise OR (the ‘|’ operator).

     在 3.1 版的變更: 新增可選的旗標引數。

     在 3.5 版的變更: Unmatched groups are replaced with an empty
     string.

     在 3.6 版的變更: Unknown escapes in 'pattern' consisting of ‘'\'’
     and an ASCII letter now are errors.

     在 3.7 版的變更: Unknown escapes in 'repl' consisting of ‘'\'’ and
     an ASCII letter now are errors.  Empty matches for the pattern are
     replaced when adjacent to a previous non-empty match.

     在 3.12 版的變更: Group 'id' can only contain ASCII digits.  In
     *note bytes: 1a5. replacement strings, group 'name' can only
     contain bytes in the ASCII range (‘b'\x00'’-‘b'\x7f'’).

     在 3.13 版之後被棄用: Passing 'count' and 'flags' as positional
     arguments is deprecated.  In future Python versions they will be
     *note keyword-only parameters: 285.

 -- 函式: re.subn (pattern, repl, string, count=0, flags=0)

     Perform the same operation as *note sub(): 283, but return a tuple
     ‘(new_string, number_of_subs_made)’.

     The expression's behaviour can be modified by specifying a 'flags'
     value.  Values can be any of the *note flags: 21cc. variables,
     combined using bitwise OR (the ‘|’ operator).

 -- 函式: re.escape (pattern)

     Escape special characters in 'pattern'.  This is useful if you want
     to match an arbitrary literal string that may have regular
     expression metacharacters in it.  For example:

          >>> print(re.escape('https://www.python.org'))
          https://www\.python\.org

          >>> legal_chars = string.ascii_lowercase + string.digits + "!#$%&'*+-.^_`|~:"
          >>> print('[%s]+' % re.escape(legal_chars))
          [abcdefghijklmnopqrstuvwxyz0123456789!\#\$%\&'\*\+\-\.\^_`\|\~:]+

          >>> operators = ['+', '-', '*', '/', '**']
          >>> print('|'.join(map(re.escape, sorted(operators, reverse=True))))
          /|\-|\+|\*\*|\*

     This function must not be used for the replacement string in *note
     sub(): 283. and *note subn(): 284, only backslashes should be
     escaped.  For example:

          >>> digits_re = r'\d+'
          >>> sample = '/usr/sbin/sendmail - 0 errors, 12 warnings'
          >>> print(re.sub(digits_re, digits_re.replace('\\', r'\\'), sample))
          /usr/sbin/sendmail - \d+ errors, \d+ warnings

     在 3.3 版的變更: The ‘'_'’ character is no longer escaped.

     在 3.7 版的變更: Only characters that can have special meaning in a
     regular expression are escaped.  As a result, ‘'!'’, ‘'"'’, ‘'%'’,
     ‘"'"’, ‘','’, ‘'/'’, ‘':'’, ‘';'’, ‘'<'’, ‘'='’, ‘'>'’, ‘'@'’, and
     ‘"`"’ are no longer escaped.

 -- 函式: re.purge ()

     Clear the regular expression cache.


File: python.info,  Node: Exceptions,  Prev: Functions,  Up: 模組內容

5.6.2.5 Exceptions
..................

 -- 例外: re.PatternError (msg, pattern=None, pos=None)

     Exception raised when a string passed to one of the functions here
     is not a valid regular expression (for example, it might contain
     unmatched parentheses) or when some other error occurs during
     compilation or matching.  It is never an error if a string contains
     no match for a pattern.  The ‘PatternError’ instance has the
     following additional attributes:

      -- 屬性: msg

          The unformatted error message.

      -- 屬性: pattern

          The regular expression pattern.

      -- 屬性: pos

          The index in 'pattern' where compilation failed (may be
          ‘None’).

      -- 屬性: lineno

          The line corresponding to 'pos' (may be ‘None’).

      -- 屬性: colno

          The column corresponding to 'pos' (may be ‘None’).

     在 3.5 版的變更: 新增額外屬性。

     在 3.13 版的變更: ‘PatternError’ was originally named ‘error’; the
     latter is kept as an alias for backward compatibility.


File: python.info,  Node: Regular Expression Objects,  Next: Match Objects,  Prev: 模組內容,  Up: re --- 正規表示式 regular expression 操作

5.6.2.6 Regular Expression Objects
..................................

 -- 類別: re.Pattern

     Compiled regular expression object returned by *note re.compile():
     b7a.

     在 3.9 版的變更: *note re.Pattern: 16e2. supports ‘[]’ to indicate
     a Unicode (str) or bytes pattern.  See *note 泛型別名型別: 656.

 -- 方法: Pattern.search (string[, pos[, endpos]])

     Scan through 'string' looking for the first location where this
     regular expression produces a match, and return a corresponding
     *note Match: c6f.  Return ‘None’ if no position in the string
     matches the pattern; note that this is different from finding a
     zero-length match at some point in the string.

     The optional second parameter 'pos' gives an index in the string
     where the search is to start; it defaults to ‘0’.  This is not
     completely equivalent to slicing the string; the ‘'^'’ pattern
     character matches at the real beginning of the string and at
     positions just after a newline, but not necessarily at the index
     where the search is to start.

     The optional parameter 'endpos' limits how far the string will be
     searched; it will be as if the string is 'endpos' characters long,
     so only the characters from 'pos' to ‘endpos - 1’ will be searched
     for a match.  If 'endpos' is less than 'pos', no match will be
     found; otherwise, if 'rx' is a compiled regular expression object,
     ‘rx.search(string, 0, 50)’ is equivalent to ‘rx.search(string[:50],
     0)’.

          >>> pattern = re.compile("d")
          >>> pattern.search("dog")     # Match at index 0
          <re.Match object; span=(0, 1), match='d'>
          >>> pattern.search("dog", 1)  # No match; search doesn't include the "d"

 -- 方法: Pattern.match (string[, pos[, endpos]])

     If zero or more characters at the 'beginning' of 'string' match
     this regular expression, return a corresponding *note Match: c6f.
     Return ‘None’ if the string does not match the pattern; note that
     this is different from a zero-length match.

     The optional 'pos' and 'endpos' parameters have the same meaning as
     for the *note search(): 21dd. method.

          >>> pattern = re.compile("o")
          >>> pattern.match("dog")      # No match as "o" is not at the start of "dog".
          >>> pattern.match("dog", 1)   # Match as "o" is the 2nd character of "dog".
          <re.Match object; span=(1, 2), match='o'>

     If you want to locate a match anywhere in 'string', use *note
     search(): 21dd. instead (see also *note search() vs.  match():
     21de.).

 -- 方法: Pattern.fullmatch (string[, pos[, endpos]])

     If the whole 'string' matches this regular expression, return a
     corresponding *note Match: c6f.  Return ‘None’ if the string does
     not match the pattern; note that this is different from a
     zero-length match.

     The optional 'pos' and 'endpos' parameters have the same meaning as
     for the *note search(): 21dd. method.

          >>> pattern = re.compile("o[gh]")
          >>> pattern.fullmatch("dog")      # No match as "o" is not at the start of "dog".
          >>> pattern.fullmatch("ogre")     # No match as not the full string matches.
          >>> pattern.fullmatch("doggie", 1, 3)   # Matches within given limits.
          <re.Match object; span=(1, 3), match='og'>

     在 3.4 版被加入.

 -- 方法: Pattern.split (string, maxsplit=0)

     Identical to the *note split(): 282. function, using the compiled
     pattern.

 -- 方法: Pattern.findall (string[, pos[, endpos]])

     Similar to the *note findall(): fcd. function, using the compiled
     pattern, but also accepts optional 'pos' and 'endpos' parameters
     that limit the search region like for *note search(): 11c4.

 -- 方法: Pattern.finditer (string[, pos[, endpos]])

     Similar to the *note finditer(): 1468. function, using the compiled
     pattern, but also accepts optional 'pos' and 'endpos' parameters
     that limit the search region like for *note search(): 11c4.

 -- 方法: Pattern.sub (repl, string, count=0)

     Identical to the *note sub(): 283. function, using the compiled
     pattern.

 -- 方法: Pattern.subn (repl, string, count=0)

     Identical to the *note subn(): 284. function, using the compiled
     pattern.

 -- 屬性: Pattern.flags

     The regex matching flags.  This is a combination of the flags given
     to *note compile(): b7a, any ‘(?...)’ inline flags in the pattern,
     and implicit flags such as *note UNICODE: b11. if the pattern is a
     Unicode string.

 -- 屬性: Pattern.groups

     The number of capturing groups in the pattern.

 -- 屬性: Pattern.groupindex

     A dictionary mapping any symbolic group names defined by ‘(?P<id>)’
     to group numbers.  The dictionary is empty if no symbolic groups
     were used in the pattern.

 -- 屬性: Pattern.pattern

     The pattern string from which the pattern object was compiled.

在 3.7 版的變更: Added support of *note copy.copy(): 4d8. and *note
copy.deepcopy(): b12.  Compiled regular expression objects are
considered atomic.


File: python.info,  Node: Match Objects,  Next: Regular Expression Examples,  Prev: Regular Expression Objects,  Up: re --- 正規表示式 regular expression 操作

5.6.2.7 Match Objects
.....................

Match objects always have a boolean value of ‘True’.  Since *note
match(): 21dc. and *note search(): 21dd. return ‘None’ when there is no
match, you can test whether there was a match with a simple ‘if’
statement:

     match = re.search(pattern, string)
     if match:
         process(match)

 -- 類別: re.Match

     Match object returned by successful ‘match’es and ‘search’es.

     在 3.9 版的變更: *note re.Match: c6f. supports ‘[]’ to indicate a
     Unicode (str) or bytes match.  See *note 泛型別名型別: 656.

 -- 方法: Match.expand (template)

     Return the string obtained by doing backslash substitution on the
     template string 'template', as done by the *note sub(): 21ea.
     method.  Escapes such as ‘\n’ are converted to the appropriate
     characters, and numeric backreferences (‘\1’, ‘\2’) and named
     backreferences (‘\g<1>’, ‘\g<name>’) are replaced by the contents
     of the corresponding group.  The backreference ‘\g<0>’ will be
     replaced by the entire match.

     在 3.5 版的變更: Unmatched groups are replaced with an empty
     string.

 -- 方法: Match.group ([group1, ...])

     Returns one or more subgroups of the match.  If there is a single
     argument, the result is a single string; if there are multiple
     arguments, the result is a tuple with one item per argument.
     Without arguments, 'group1' defaults to zero (the whole match is
     returned).  If a 'groupN' argument is zero, the corresponding
     return value is the entire matching string; if it is in the
     inclusive range [1..99], it is the string matching the
     corresponding parenthesized group.  If a group number is negative
     or larger than the number of groups defined in the pattern, an
     *note IndexError: 14a3. exception is raised.  If a group is
     contained in a part of the pattern that did not match, the
     corresponding result is ‘None’.  If a group is contained in a part
     of the pattern that matched multiple times, the last match is
     returned.

          >>> m = re.match(r"(\w+) (\w+)", "Isaac Newton, physicist")
          >>> m.group(0)       # The entire match
          'Isaac Newton'
          >>> m.group(1)       # The first parenthesized subgroup.
          'Isaac'
          >>> m.group(2)       # The second parenthesized subgroup.
          'Newton'
          >>> m.group(1, 2)    # Multiple arguments give us a tuple.
          ('Isaac', 'Newton')

     If the regular expression uses the ‘(?P<name>...)’ syntax, the
     'groupN' arguments may also be strings identifying groups by their
     group name.  If a string argument is not used as a group name in
     the pattern, an *note IndexError: 14a3. exception is raised.

     A moderately complicated example:

          >>> m = re.match(r"(?P<first_name>\w+) (?P<last_name>\w+)", "Malcolm Reynolds")
          >>> m.group('first_name')
          'Malcolm'
          >>> m.group('last_name')
          'Reynolds'

     Named groups can also be referred to by their index:

          >>> m.group(1)
          'Malcolm'
          >>> m.group(2)
          'Reynolds'

     If a group matches multiple times, only the last match is
     accessible:

          >>> m = re.match(r"(..)+", "a1b2c3")  # Matches 3 times.
          >>> m.group(1)                        # Returns only the last match.
          'c3'

 -- 方法: Match.__getitem__ (g)

     This is identical to ‘m.group(g)’.  This allows easier access to an
     individual group from a match:

          >>> m = re.match(r"(\w+) (\w+)", "Isaac Newton, physicist")
          >>> m[0]       # The entire match
          'Isaac Newton'
          >>> m[1]       # The first parenthesized subgroup.
          'Isaac'
          >>> m[2]       # The second parenthesized subgroup.
          'Newton'

     Named groups are supported as well:

          >>> m = re.match(r"(?P<first_name>\w+) (?P<last_name>\w+)", "Isaac Newton")
          >>> m['first_name']
          'Isaac'
          >>> m['last_name']
          'Newton'

     在 3.6 版被加入.

 -- 方法: Match.groups (default=None)

     Return a tuple containing all the subgroups of the match, from 1 up
     to however many groups are in the pattern.  The 'default' argument
     is used for groups that did not participate in the match; it
     defaults to ‘None’.

     舉例來說：

          >>> m = re.match(r"(\d+)\.(\d+)", "24.1632")
          >>> m.groups()
          ('24', '1632')

     If we make the decimal place and everything after it optional, not
     all groups might participate in the match.  These groups will
     default to ‘None’ unless the 'default' argument is given:

          >>> m = re.match(r"(\d+)\.?(\d+)?", "24")
          >>> m.groups()      # Second group defaults to None.
          ('24', None)
          >>> m.groups('0')   # Now, the second group defaults to '0'.
          ('24', '0')

 -- 方法: Match.groupdict (default=None)

     Return a dictionary containing all the 'named' subgroups of the
     match, keyed by the subgroup name.  The 'default' argument is used
     for groups that did not participate in the match; it defaults to
     ‘None’.  For example:

          >>> m = re.match(r"(?P<first_name>\w+) (?P<last_name>\w+)", "Malcolm Reynolds")
          >>> m.groupdict()
          {'first_name': 'Malcolm', 'last_name': 'Reynolds'}

 -- 方法: Match.start ([group])
 -- 方法: Match.end ([group])

     Return the indices of the start and end of the substring matched by
     'group'; 'group' defaults to zero (meaning the whole matched
     substring).  Return ‘-1’ if 'group' exists but did not contribute
     to the match.  For a match object 'm', and a group 'g' that did
     contribute to the match, the substring matched by group 'g'
     (equivalent to ‘m.group(g)’) is

          m.string[m.start(g):m.end(g)]

     Note that ‘m.start(group)’ will equal ‘m.end(group)’ if 'group'
     matched a null string.  For example, after ‘m = re.search('b(c?)',
     'cba')’, ‘m.start(0)’ is 1, ‘m.end(0)’ is 2, ‘m.start(1)’ and
     ‘m.end(1)’ are both 2, and ‘m.start(2)’ raises an *note IndexError:
     14a3. exception.

     An example that will remove 'remove_this' from email addresses:

          >>> email = "tony@tiremove_thisger.net"
          >>> m = re.search("remove_this", email)
          >>> email[:m.start()] + email[m.end():]
          'tony@tiger.net'

 -- 方法: Match.span ([group])

     For a match 'm', return the 2-tuple ‘(m.start(group),
     m.end(group))’.  Note that if 'group' did not contribute to the
     match, this is ‘(-1, -1)’.  'group' defaults to zero, the entire
     match.

 -- 屬性: Match.pos

     The value of 'pos' which was passed to the *note search(): 21dd. or
     *note match(): 21dc. method of a *note regex object: f29.  This is
     the index into the string at which the RE engine started looking
     for a match.

 -- 屬性: Match.endpos

     The value of 'endpos' which was passed to the *note search(): 21dd.
     or *note match(): 21dc. method of a *note regex object: f29.  This
     is the index into the string beyond which the RE engine will not
     go.

 -- 屬性: Match.lastindex

     The integer index of the last matched capturing group, or ‘None’ if
     no group was matched at all.  For example, the expressions ‘(a)b’,
     ‘((a)(b))’, and ‘((ab))’ will have ‘lastindex == 1’ if applied to
     the string ‘'ab'’, while the expression ‘(a)(b)’ will have
     ‘lastindex == 2’, if applied to the same string.

 -- 屬性: Match.lastgroup

     The name of the last matched capturing group, or ‘None’ if the
     group didn't have a name, or if no group was matched at all.

 -- 屬性: Match.re

     The *note regular expression object: f29. whose *note match():
     21dc. or *note search(): 21dd. method produced this match instance.

 -- 屬性: Match.string

     The string passed to *note match(): 21dc. or *note search(): 21dd.

在 3.7 版的變更: Added support of *note copy.copy(): 4d8. and *note
copy.deepcopy(): b12.  Match objects are considered atomic.


File: python.info,  Node: Regular Expression Examples,  Prev: Match Objects,  Up: re --- 正規表示式 regular expression 操作

5.6.2.8 Regular Expression Examples
...................................

* Menu:

* Checking for a Pair::
* 模擬 scanf(): 模擬 scanf.
* search() vs. match(): search vs match.
* Making a Phonebook::
* Text Munging::
* Finding all Adverbs::
* Finding all Adverbs and their Positions::
* Raw String Notation::
* Writing a Tokenizer::


File: python.info,  Node: Checking for a Pair,  Next: 模擬 scanf,  Up: Regular Expression Examples

5.6.2.9 Checking for a Pair
...........................

In this example, we'll use the following helper function to display
match objects a little more gracefully:

     def displaymatch(match):
         if match is None:
             return None
         return '<Match: %r, groups=%r>' % (match.group(), match.groups())

Suppose you are writing a poker program where a player's hand is
represented as a 5-character string with each character representing a
card, "a" for ace, "k" for king, "q" for queen, "j" for jack, "t" for
10, and "2" through "9" representing the card with that value.

To see if a given string is a valid hand, one could do the following:

     >>> valid = re.compile(r"^[a2-9tjqk]{5}$")
     >>> displaymatch(valid.match("akt5q"))  # Valid.
     "<Match: 'akt5q', groups=()>"
     >>> displaymatch(valid.match("akt5e"))  # Invalid.
     >>> displaymatch(valid.match("akt"))    # Invalid.
     >>> displaymatch(valid.match("727ak"))  # Valid.
     "<Match: '727ak', groups=()>"

That last hand, ‘"727ak"’, contained a pair, or two of the same valued
cards.  To match this with a regular expression, one could use
backreferences as such:

     >>> pair = re.compile(r".*(.).*\1")
     >>> displaymatch(pair.match("717ak"))     # Pair of 7s.
     "<Match: '717', groups=('7',)>"
     >>> displaymatch(pair.match("718ak"))     # No pairs.
     >>> displaymatch(pair.match("354aa"))     # Pair of aces.
     "<Match: '354aa', groups=('a',)>"

To find out what card the pair consists of, one could use the *note
group(): 21f2. method of the match object in the following manner:

     >>> pair = re.compile(r".*(.).*\1")
     >>> pair.match("717ak").group(1)
     '7'

     # Error because re.match() returns None, which doesn't have a group() method:
     >>> pair.match("718ak").group(1)
     Traceback (most recent call last):
       File "<pyshell#23>", line 1, in <module>
         re.match(r".*(.).*\1", "718ak").group(1)
     AttributeError: 'NoneType' object has no attribute 'group'

     >>> pair.match("354aa").group(1)
     'a'


File: python.info,  Node: 模擬 scanf,  Next: search vs match,  Prev: Checking for a Pair,  Up: Regular Expression Examples

5.6.2.10 模擬 scanf()
.....................

Python does not currently have an equivalent to ‘scanf()’.  Regular
expressions are generally more powerful, though also more verbose, than
‘scanf()’ format strings.  The table below offers some more-or-less
equivalent mappings between ‘scanf()’ format tokens and regular
expressions.

‘scanf()’ Token                      Regular Expression
                                     
---------------------------------------------------------------------------------------
                                     
‘%c’                                 ‘.’
                                     
                                     
‘%5c’                                ‘.{5}’
                                     
                                     
‘%d’                                 ‘[-+]?\d+’
                                     
                                     
‘%e’, ‘%E’, ‘%f’, ‘%g’               ‘[-+]?(\d+(\.\d*)?|\.\d+)([eE][-+]?\d+)?’
                                     
                                     
‘%i’                                 ‘[-+]?(0[xX][\dA-Fa-f]+|0[0-7]*|\d+)’
                                     
                                     
‘%o’                                 ‘[-+]?[0-7]+’
                                     
                                     
‘%s’                                 ‘\S+’
                                     
                                     
‘%u’                                 ‘\d+’
                                     
                                     
‘%x’、‘%X’                           ‘[-+]?(0[xX])?[\dA-Fa-f]+’
                                     

To extract the filename and numbers from a string like

     /usr/sbin/sendmail - 0 errors, 4 warnings

you would use a ‘scanf()’ format like

     %s - %d errors, %d warnings

The equivalent regular expression would be

     (\S+) - (\d+) errors, (\d+) warnings


File: python.info,  Node: search vs match,  Next: Making a Phonebook,  Prev: 模擬 scanf,  Up: Regular Expression Examples

5.6.2.11 search() vs. match()
.............................

Python offers different primitive operations based on regular
expressions:

   + *note re.match(): 11c5. checks for a match only at the beginning of
     the string

   + *note re.search(): 11c4. checks for a match anywhere in the string
     (this is what Perl does by default)

   + *note re.fullmatch(): f28. checks for entire string to be a match

舉例來說：

     >>> re.match("c", "abcdef")    # No match
     >>> re.search("c", "abcdef")   # Match
     <re.Match object; span=(2, 3), match='c'>
     >>> re.fullmatch("p.*n", "python") # Match
     <re.Match object; span=(0, 6), match='python'>
     >>> re.fullmatch("r.*n", "python") # No match

Regular expressions beginning with ‘'^'’ can be used with *note
search(): 11c4. to restrict the match at the beginning of the string:

     >>> re.match("c", "abcdef")    # No match
     >>> re.search("^c", "abcdef")  # No match
     >>> re.search("^a", "abcdef")  # Match
     <re.Match object; span=(0, 1), match='a'>

Note however that in *note MULTILINE: 21cb. mode *note match(): 11c5.
only matches at the beginning of the string, whereas using *note
search(): 11c4. with a regular expression beginning with ‘'^'’ will
match at the beginning of each line.

     >>> re.match("X", "A\nB\nX", re.MULTILINE)  # No match
     >>> re.search("^X", "A\nB\nX", re.MULTILINE)  # Match
     <re.Match object; span=(4, 5), match='X'>


File: python.info,  Node: Making a Phonebook,  Next: Text Munging,  Prev: search vs match,  Up: Regular Expression Examples

5.6.2.12 Making a Phonebook
...........................

*note split(): 282. splits a string into a list delimited by the passed
pattern.  The method is invaluable for converting textual data into data
structures that can be easily read and modified by Python as
demonstrated in the following example that creates a phonebook.

First, here is the input.  Normally it may come from a file, here we are
using triple-quoted string syntax

     >>> text = """Ross McFluff: 834.345.1254 155 Elm Street
     ...
     ... Ronald Heathmore: 892.345.3428 436 Finley Avenue
     ... Frank Burger: 925.541.7625 662 South Dogwood Way
     ...
     ...
     ... Heather Albrecht: 548.326.4584 919 Park Place"""

The entries are separated by one or more newlines.  Now we convert the
string into a list with each nonempty line having its own entry:

     >>> entries = re.split("\n+", text)
     >>> entries
     ['Ross McFluff: 834.345.1254 155 Elm Street',
     'Ronald Heathmore: 892.345.3428 436 Finley Avenue',
     'Frank Burger: 925.541.7625 662 South Dogwood Way',
     'Heather Albrecht: 548.326.4584 919 Park Place']

Finally, split each entry into a list with first name, last name,
telephone number, and address.  We use the ‘maxsplit’ parameter of *note
split(): 282. because the address has spaces, our splitting pattern, in
it:

     >>> [re.split(":? ", entry, maxsplit=3) for entry in entries]
     [['Ross', 'McFluff', '834.345.1254', '155 Elm Street'],
     ['Ronald', 'Heathmore', '892.345.3428', '436 Finley Avenue'],
     ['Frank', 'Burger', '925.541.7625', '662 South Dogwood Way'],
     ['Heather', 'Albrecht', '548.326.4584', '919 Park Place']]

The ‘:?’ pattern matches the colon after the last name, so that it does
not occur in the result list.  With a ‘maxsplit’ of ‘4’, we could
separate the house number from the street name:

     >>> [re.split(":? ", entry, maxsplit=4) for entry in entries]
     [['Ross', 'McFluff', '834.345.1254', '155', 'Elm Street'],
     ['Ronald', 'Heathmore', '892.345.3428', '436', 'Finley Avenue'],
     ['Frank', 'Burger', '925.541.7625', '662', 'South Dogwood Way'],
     ['Heather', 'Albrecht', '548.326.4584', '919', 'Park Place']]


File: python.info,  Node: Text Munging,  Next: Finding all Adverbs,  Prev: Making a Phonebook,  Up: Regular Expression Examples

5.6.2.13 Text Munging
.....................

*note sub(): 283. replaces every occurrence of a pattern with a string
or the result of a function.  This example demonstrates using *note
sub(): 283. with a function to "munge" text, or randomize the order of
all the characters in each word of a sentence except for the first and
last characters:

     >>> def repl(m):
     ...     inner_word = list(m.group(2))
     ...     random.shuffle(inner_word)
     ...     return m.group(1) + "".join(inner_word) + m.group(3)
     ...
     >>> text = "Professor Abdolmalek, please report your absences promptly."
     >>> re.sub(r"(\w)(\w+)(\w)", repl, text)
     'Poefsrosr Aealmlobdk, pslaee reorpt your abnseces plmrptoy.'
     >>> re.sub(r"(\w)(\w+)(\w)", repl, text)
     'Pofsroser Aodlambelk, plasee reoprt yuor asnebces potlmrpy.'


File: python.info,  Node: Finding all Adverbs,  Next: Finding all Adverbs and their Positions,  Prev: Text Munging,  Up: Regular Expression Examples

5.6.2.14 Finding all Adverbs
............................

*note findall(): fcd. matches 'all' occurrences of a pattern, not just
the first one as *note search(): 11c4. does.  For example, if a writer
wanted to find all of the adverbs in some text, they might use *note
findall(): fcd. in the following manner:

     >>> text = "He was carefully disguised but captured quickly by police."
     >>> re.findall(r"\w+ly\b", text)
     ['carefully', 'quickly']


File: python.info,  Node: Finding all Adverbs and their Positions,  Next: Raw String Notation,  Prev: Finding all Adverbs,  Up: Regular Expression Examples

5.6.2.15 Finding all Adverbs and their Positions
................................................

If one wants more information about all matches of a pattern than the
matched text, *note finditer(): 1468. is useful as it provides *note
Match: c6f. objects instead of strings.  Continuing with the previous
example, if a writer wanted to find all of the adverbs 'and their
positions' in some text, they would use *note finditer(): 1468. in the
following manner:

     >>> text = "He was carefully disguised but captured quickly by police."
     >>> for m in re.finditer(r"\w+ly\b", text):
     ...     print('%02d-%02d: %s' % (m.start(), m.end(), m.group(0)))
     07-16: carefully
     40-47: quickly


File: python.info,  Node: Raw String Notation,  Next: Writing a Tokenizer,  Prev: Finding all Adverbs and their Positions,  Up: Regular Expression Examples

5.6.2.16 Raw String Notation
............................

Raw string notation (‘r"text"’) keeps regular expressions sane.  Without
it, every backslash (‘'\'’) in a regular expression would have to be
prefixed with another one to escape it.  For example, the two following
lines of code are functionally identical:

     >>> re.match(r"\W(.)\1\W", " ff ")
     <re.Match object; span=(0, 4), match=' ff '>
     >>> re.match("\\W(.)\\1\\W", " ff ")
     <re.Match object; span=(0, 4), match=' ff '>

When one wants to match a literal backslash, it must be escaped in the
regular expression.  With raw string notation, this means ‘r"\\"’.
Without raw string notation, one must use ‘"\\\\"’, making the following
lines of code functionally identical:

     >>> re.match(r"\\", r"\\")
     <re.Match object; span=(0, 1), match='\\'>
     >>> re.match("\\\\", r"\\")
     <re.Match object; span=(0, 1), match='\\'>


File: python.info,  Node: Writing a Tokenizer,  Prev: Raw String Notation,  Up: Regular Expression Examples

5.6.2.17 Writing a Tokenizer
............................

A tokenizer or scanner(1) analyzes a string to categorize groups of
characters.  This is a useful first step in writing a compiler or
interpreter.

The text categories are specified with regular expressions.  The
technique is to combine those into a single master regular expression
and to loop over successive matches:

     from typing import NamedTuple
     import re

     class Token(NamedTuple):
         type: str
         value: str
         line: int
         column: int

     def tokenize(code):
         keywords = {'IF', 'THEN', 'ENDIF', 'FOR', 'NEXT', 'GOSUB', 'RETURN'}
         token_specification = [
             ('NUMBER',   r'\d+(\.\d*)?'),  # Integer or decimal number
             ('ASSIGN',   r':='),           # Assignment operator
             ('END',      r';'),            # Statement terminator
             ('ID',       r'[A-Za-z]+'),    # Identifiers
             ('OP',       r'[+\-*/]'),      # Arithmetic operators
             ('NEWLINE',  r'\n'),           # Line endings
             ('SKIP',     r'[ \t]+'),       # Skip over spaces and tabs
             ('MISMATCH', r'.'),            # Any other character
         ]
         tok_regex = '|'.join('(?P<%s>%s)' % pair for pair in token_specification)
         line_num = 1
         line_start = 0
         for mo in re.finditer(tok_regex, code):
             kind = mo.lastgroup
             value = mo.group()
             column = mo.start() - line_start
             if kind == 'NUMBER':
                 value = float(value) if '.' in value else int(value)
             elif kind == 'ID' and value in keywords:
                 kind = value
             elif kind == 'NEWLINE':
                 line_start = mo.end()
                 line_num += 1
                 continue
             elif kind == 'SKIP':
                 continue
             elif kind == 'MISMATCH':
                 raise RuntimeError(f'{value!r} unexpected on line {line_num}')
             yield Token(kind, value, line_num, column)

     statements = '''
         IF quantity THEN
             total := total + price * quantity;
             tax := price * 0.05;
         ENDIF;
     '''

     for token in tokenize(statements):
         print(token)

The tokenizer produces the following output:

     Token(type='IF', value='IF', line=2, column=4)
     Token(type='ID', value='quantity', line=2, column=7)
     Token(type='THEN', value='THEN', line=2, column=16)
     Token(type='ID', value='total', line=3, column=8)
     Token(type='ASSIGN', value=':=', line=3, column=14)
     Token(type='ID', value='total', line=3, column=17)
     Token(type='OP', value='+', line=3, column=23)
     Token(type='ID', value='price', line=3, column=25)
     Token(type='OP', value='*', line=3, column=31)
     Token(type='ID', value='quantity', line=3, column=33)
     Token(type='END', value=';', line=3, column=41)
     Token(type='ID', value='tax', line=4, column=8)
     Token(type='ASSIGN', value=':=', line=4, column=12)
     Token(type='ID', value='price', line=4, column=15)
     Token(type='OP', value='*', line=4, column=21)
     Token(type='NUMBER', value=0.05, line=4, column=23)
     Token(type='END', value=';', line=4, column=27)
     Token(type='ENDIF', value='ENDIF', line=5, column=4)
     Token(type='END', value=';', line=5, column=9)

(Frie09) Friedl, Jeffrey.  Mastering Regular Expressions.  3rd ed.,
O'Reilly Media, 2009.  The third edition of the book no longer covers
Python at all, but the first edition covered writing good regular
expression patterns in great detail.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Lexical_analysis


File: python.info,  Node: difflib --- 計算差異的輔助工具,  Next: textwrap --- 文字包裝與填充,  Prev: re --- 正規表示式 regular expression 操作,  Up: 文本處理 Text Processing 服務

5.6.3 ‘difflib’ -- 計算差異的輔助工具
-------------------------------------

'原始碼：'Lib/difflib.py(1)

__________________________________________________________________

This module provides classes and functions for comparing sequences.  It
can be used for example, for comparing files, and can produce
information about file differences in various formats, including HTML
and context and unified diffs.  For comparing directories and files, see
also, the *note filecmp: 50. module.

 -- 類別: difflib.SequenceMatcher

     This is a flexible class for comparing pairs of sequences of any
     type, so long as the sequence elements are *note hashable: 5b5.
     The basic algorithm predates, and is a little fancier than, an
     algorithm published in the late 1980's by Ratcliff and Obershelp
     under the hyperbolic name "gestalt pattern matching."  The idea is
     to find the longest contiguous matching subsequence that contains
     no "junk" elements; these "junk" elements are ones that are
     uninteresting in some sense, such as blank lines or whitespace.
     (Handling junk is an extension to the Ratcliff and Obershelp
     algorithm.)  The same idea is then applied recursively to the
     pieces of the sequences to the left and to the right of the
     matching subsequence.  This does not yield minimal edit sequences,
     but does tend to yield matches that "look right" to people.

     'Timing:' The basic Ratcliff-Obershelp algorithm is cubic time in
     the worst case and quadratic time in the expected case.  *note
     SequenceMatcher: fba. is quadratic time for the worst case and has
     expected-case behavior dependent in a complicated way on how many
     elements the sequences have in common; best case time is linear.

     'Automatic junk heuristic:' *note SequenceMatcher: fba. supports a
     heuristic that automatically treats certain sequence items as junk.
     The heuristic counts how many times each individual item appears in
     the sequence.  If an item's duplicates (after the first one)
     account for more than 1% of the sequence and the sequence is at
     least 200 items long, this item is marked as "popular" and is
     treated as junk for the purpose of sequence matching.  This
     heuristic can be turned off by setting the ‘autojunk’ argument to
     ‘False’ when creating the *note SequenceMatcher: fba.

     在 3.2 版的變更: 新增 'autojunk' 參數。

 -- 類別: difflib.Differ

     This is a class for comparing sequences of lines of text, and
     producing human-readable differences or deltas.  Differ uses *note
     SequenceMatcher: fba. both to compare sequences of lines, and to
     compare sequences of characters within similar (near-matching)
     lines.

     Each line of a *note Differ: 220b. delta begins with a two-letter
     code:

     Code           含義
                    
     ---------------------------------------------------------------
                    
     ‘'- '’         line unique to sequence 1
                    
                    
     ‘'+ '’         line unique to sequence 2
                    
                    
     ‘' '’          line common to both sequences
                    
                    
     ‘'? '’         line not present in either input sequence
                    

     Lines beginning with '‘?’' attempt to guide the eye to intraline
     differences, and were not present in either input sequence.  These
     lines can be confusing if the sequences contain whitespace
     characters, such as spaces, tabs or line breaks.

 -- 類別: difflib.HtmlDiff

     This class can be used to create an HTML table (or a complete HTML
     file containing the table) showing a side by side, line by line
     comparison of text with inter-line and intra-line change
     highlights.  The table can be generated in either full or
     contextual difference mode.

     The constructor for this class is:

      -- 方法: __init__ (tabsize=8, wrapcolumn=None, linejunk=None,
               charjunk=IS_CHARACTER_JUNK)

          Initializes instance of *note HtmlDiff: 220c.

          'tabsize' is an optional keyword argument to specify tab stop
          spacing and defaults to ‘8’.

          'wrapcolumn' is an optional keyword to specify column number
          where lines are broken and wrapped, defaults to ‘None’ where
          lines are not wrapped.

          'linejunk' and 'charjunk' are optional keyword arguments
          passed into *note ndiff(): 220e. (used by *note HtmlDiff:
          220c. to generate the side by side HTML differences).  See
          *note ndiff(): 220e. documentation for argument default values
          and descriptions.

     The following methods are public:

      -- 方法: make_file (fromlines, tolines, fromdesc='', todesc='',
               context=False, numlines=5, *, charset='utf-8')

          Compares 'fromlines' and 'tolines' (lists of strings) and
          returns a string which is a complete HTML file containing a
          table showing line by line differences with inter-line and
          intra-line changes highlighted.

          'fromdesc' and 'todesc' are optional keyword arguments to
          specify from/to file column header strings (both default to an
          empty string).

          'context' and 'numlines' are both optional keyword arguments.
          Set 'context' to ‘True’ when contextual differences are to be
          shown, else the default is ‘False’ to show the full files.
          'numlines' defaults to ‘5’.  When 'context' is ‘True’
          'numlines' controls the number of context lines which surround
          the difference highlights.  When 'context' is ‘False’
          'numlines' controls the number of lines which are shown before
          a difference highlight when using the "next" hyperlinks
          (setting to zero would cause the "next" hyperlinks to place
          the next difference highlight at the top of the browser
          without any leading context).

               備註: 'fromdesc' and 'todesc' are interpreted as
               unescaped HTML and should be properly escaped while
               receiving input from untrusted sources.

          在 3.5 版的變更: 'charset' keyword-only argument was added.
          The default charset of HTML document changed from
          ‘'ISO-8859-1'’ to ‘'utf-8'’.

      -- 方法: make_table (fromlines, tolines, fromdesc='', todesc='',
               context=False, numlines=5)

          Compares 'fromlines' and 'tolines' (lists of strings) and
          returns a string which is a complete HTML table showing line
          by line differences with inter-line and intra-line changes
          highlighted.

          The arguments for this method are the same as those for the
          *note make_file(): d95. method.

 -- 函式: difflib.context_diff (a, b, fromfile='', tofile='',
          fromfiledate='', tofiledate='', n=3, lineterm='\n')

     Compare 'a' and 'b' (lists of strings); return a delta (a *note
     generator: 1004. generating the delta lines) in context diff
     format.

     Context diffs are a compact way of showing just the lines that have
     changed plus a few lines of context.  The changes are shown in a
     before/after style.  The number of context lines is set by 'n'
     which defaults to three.

     By default, the diff control lines (those with ‘***’ or ‘---’) are
     created with a trailing newline.  This is helpful so that inputs
     created from *note io.IOBase.readlines(): 2211. result in diffs
     that are suitable for use with *note io.IOBase.writelines(): 2212.
     since both the inputs and outputs have trailing newlines.

     For inputs that do not have trailing newlines, set the 'lineterm'
     argument to ‘""’ so that the output will be uniformly newline free.

     The context diff format normally has a header for filenames and
     modification times.  Any or all of these may be specified using
     strings for 'fromfile', 'tofile', 'fromfiledate', and 'tofiledate'.
     The modification times are normally expressed in the ISO 8601
     format.  If not specified, the strings default to blanks.

          >>> import sys
          >>> from difflib import *
          >>> s1 = ['bacon\n', 'eggs\n', 'ham\n', 'guido\n']
          >>> s2 = ['python\n', 'eggy\n', 'hamster\n', 'guido\n']
          >>> sys.stdout.writelines(context_diff(s1, s2, fromfile='before.py',
          ...                        tofile='after.py'))
          *** before.py
          --- after.py
          ***************
          *** 1,4 ****
          ! bacon
          ! eggs
          ! ham
            guido
          --- 1,4 ----
          ! python
          ! eggy
          ! hamster
            guido

     一個更詳盡的範例請見 *note A command-line interface to difflib:
     2213.。

 -- 函式: difflib.get_close_matches (word, possibilities, n=3,
          cutoff=0.6)

     Return a list of the best "good enough" matches.  'word' is a
     sequence for which close matches are desired (typically a string),
     and 'possibilities' is a list of sequences against which to match
     'word' (typically a list of strings).

     Optional argument 'n' (default ‘3’) is the maximum number of close
     matches to return; 'n' must be greater than ‘0’.

     Optional argument 'cutoff' (default ‘0.6’) is a float in the range
     [0, 1].  Possibilities that don't score at least that similar to
     'word' are ignored.

     The best (no more than 'n') matches among the possibilities are
     returned in a list, sorted by similarity score, most similar first.

          >>> get_close_matches('appel', ['ape', 'apple', 'peach', 'puppy'])
          ['apple', 'ape']
          >>> import keyword
          >>> get_close_matches('wheel', keyword.kwlist)
          ['while']
          >>> get_close_matches('pineapple', keyword.kwlist)
          []
          >>> get_close_matches('accept', keyword.kwlist)
          ['except']

 -- 函式: difflib.ndiff (a, b, linejunk=None,
          charjunk=IS_CHARACTER_JUNK)

     Compare 'a' and 'b' (lists of strings); return a *note Differ:
     220b.-style delta (a *note generator: 1004. generating the delta
     lines).

     Optional keyword parameters 'linejunk' and 'charjunk' are filtering
     functions (or ‘None’):

     'linejunk': A function that accepts a single string argument, and
     returns true if the string is junk, or false if not.  The default
     is ‘None’.  There is also a module-level function *note
     IS_LINE_JUNK(): 2215, which filters out lines without visible
     characters, except for at most one pound character (‘'#'’) -
     however the underlying *note SequenceMatcher: fba. class does a
     dynamic analysis of which lines are so frequent as to constitute
     noise, and this usually works better than using this function.

     'charjunk': A function that accepts a character (a string of length
     1), and returns if the character is junk, or false if not.  The
     default is module-level function *note IS_CHARACTER_JUNK(): 2216,
     which filters out whitespace characters (a blank or tab; it's a bad
     idea to include newline in this!).

          >>> diff = ndiff('one\ntwo\nthree\n'.splitlines(keepends=True),
          ...              'ore\ntree\nemu\n'.splitlines(keepends=True))
          >>> print(''.join(diff), end="")
          - one
          ?  ^
          + ore
          ?  ^
          - two
          - three
          ?  -
          + tree
          + emu

 -- 函式: difflib.restore (sequence, which)

     Return one of the two sequences that generated a delta.

     Given a 'sequence' produced by *note Differ.compare(): 2218. or
     *note ndiff(): 220e, extract lines originating from file 1 or 2
     (parameter 'which'), stripping off line prefixes.

     範例：

          >>> diff = ndiff('one\ntwo\nthree\n'.splitlines(keepends=True),
          ...              'ore\ntree\nemu\n'.splitlines(keepends=True))
          >>> diff = list(diff) # materialize the generated delta into a list
          >>> print(''.join(restore(diff, 1)), end="")
          one
          two
          three
          >>> print(''.join(restore(diff, 2)), end="")
          ore
          tree
          emu

 -- 函式: difflib.unified_diff (a, b, fromfile='', tofile='',
          fromfiledate='', tofiledate='', n=3, lineterm='\n')

     Compare 'a' and 'b' (lists of strings); return a delta (a *note
     generator: 1004. generating the delta lines) in unified diff
     format.

     Unified diffs are a compact way of showing just the lines that have
     changed plus a few lines of context.  The changes are shown in an
     inline style (instead of separate before/after blocks).  The number
     of context lines is set by 'n' which defaults to three.

     By default, the diff control lines (those with ‘---’, ‘+++’, or
     ‘@@’) are created with a trailing newline.  This is helpful so that
     inputs created from *note io.IOBase.readlines(): 2211. result in
     diffs that are suitable for use with *note io.IOBase.writelines():
     2212. since both the inputs and outputs have trailing newlines.

     For inputs that do not have trailing newlines, set the 'lineterm'
     argument to ‘""’ so that the output will be uniformly newline free.

     The unified diff format normally has a header for filenames and
     modification times.  Any or all of these may be specified using
     strings for 'fromfile', 'tofile', 'fromfiledate', and 'tofiledate'.
     The modification times are normally expressed in the ISO 8601
     format.  If not specified, the strings default to blanks.

          >>> s1 = ['bacon\n', 'eggs\n', 'ham\n', 'guido\n']
          >>> s2 = ['python\n', 'eggy\n', 'hamster\n', 'guido\n']
          >>> sys.stdout.writelines(unified_diff(s1, s2, fromfile='before.py', tofile='after.py'))
          --- before.py
          +++ after.py
          @@ -1,4 +1,4 @@
          -bacon
          -eggs
          -ham
          +python
          +eggy
          +hamster
           guido

     一個更詳盡的範例請見 *note A command-line interface to difflib:
     2213.。

 -- 函式: difflib.diff_bytes (dfunc, a, b, fromfile=b'', tofile=b'',
          fromfiledate=b'', tofiledate=b'', n=3, lineterm=b'\n')

     Compare 'a' and 'b' (lists of bytes objects) using 'dfunc'; yield a
     sequence of delta lines (also bytes) in the format returned by
     'dfunc'.  'dfunc' must be a callable, typically either *note
     unified_diff(): 2219. or *note context_diff(): 2210.

     Allows you to compare data with unknown or inconsistent encoding.
     All inputs except 'n' must be bytes objects, not str.  Works by
     losslessly converting all inputs (except 'n') to str, and calling
     ‘dfunc(a, b, fromfile, tofile, fromfiledate, tofiledate, n,
     lineterm)’.  The output of 'dfunc' is then converted back to bytes,
     so the delta lines that you receive have the same
     unknown/inconsistent encodings as 'a' and 'b'.

     在 3.5 版被加入.

 -- 函式: difflib.IS_LINE_JUNK (line)

     Return ‘True’ for ignorable lines.  The line 'line' is ignorable if
     'line' is blank or contains a single ‘'#'’, otherwise it is not
     ignorable.  Used as a default for parameter 'linejunk' in *note
     ndiff(): 220e. in older versions.

 -- 函式: difflib.IS_CHARACTER_JUNK (ch)

     Return ‘True’ for ignorable characters.  The character 'ch' is
     ignorable if 'ch' is a space or tab, otherwise it is not ignorable.
     Used as a default for parameter 'charjunk' in *note ndiff(): 220e.

也參考
......

Pattern Matching: The Gestalt Approach(2)

     Discussion of a similar algorithm by John W. Ratcliff and D. E.
     Metzener.  This was published in Dr.  Dobb's Journal(3) in July,
     1988.

* Menu:

* SequenceMatcher 物件::
* SequenceMatcher 範例::
* Differ Objects::
* Differ Example::
* A command-line interface to difflib::
* ndiff 範例：::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/difflib.py

   (2) 
https://www.drdobbs.com/database/pattern-matching-the-gestalt-approach/184407970

   (3) https://www.drdobbs.com/


File: python.info,  Node: SequenceMatcher 物件,  Next: SequenceMatcher 範例,  Up: difflib --- 計算差異的輔助工具

5.6.3.1 SequenceMatcher 物件
............................

The *note SequenceMatcher: fba. class has this constructor:

 -- 類別: difflib.SequenceMatcher (isjunk=None, a='', b='',
          autojunk=True)

     Optional argument 'isjunk' must be ‘None’ (the default) or a
     one-argument function that takes a sequence element and returns
     true if and only if the element is "junk" and should be ignored.
     Passing ‘None’ for 'isjunk' is equivalent to passing ‘lambda x:
     False’; in other words, no elements are ignored.  For example,
     pass:

          lambda x: x in " \t"

     if you're comparing lines as sequences of characters, and don't
     want to synch up on blanks or hard tabs.

     The optional arguments 'a' and 'b' are sequences to be compared;
     both default to empty strings.  The elements of both sequences must
     be *note hashable: 5b5.

     The optional argument 'autojunk' can be used to disable the
     automatic junk heuristic.

     在 3.2 版的變更: 新增 'autojunk' 參數。

     SequenceMatcher objects get three data attributes: 'bjunk' is the
     set of elements of 'b' for which 'isjunk' is ‘True’; 'bpopular' is
     the set of non-junk elements considered popular by the heuristic
     (if it is not disabled); 'b2j' is a dict mapping the remaining
     elements of 'b' to a list of positions where they occur.  All three
     are reset whenever 'b' is reset with *note set_seqs(): 221c. or
     *note set_seq2(): 221d.

     在 3.2 版被加入: The 'bjunk' and 'bpopular' attributes.

     *note SequenceMatcher: fba. objects have the following methods:

      -- 方法: set_seqs (a, b)

          Set the two sequences to be compared.

     *note SequenceMatcher: fba. computes and caches detailed
     information about the second sequence, so if you want to compare
     one sequence against many sequences, use *note set_seq2(): 221d. to
     set the commonly used sequence once and call *note set_seq1():
     221e. repeatedly, once for each of the other sequences.

      -- 方法: set_seq1 (a)

          Set the first sequence to be compared.  The second sequence to
          be compared is not changed.

      -- 方法: set_seq2 (b)

          Set the second sequence to be compared.  The first sequence to
          be compared is not changed.

      -- 方法: find_longest_match (alo=0, ahi=None, blo=0, bhi=None)

          Find longest matching block in ‘a[alo:ahi]’ and ‘b[blo:bhi]’.

          If 'isjunk' was omitted or ‘None’, *note find_longest_match():
          1861. returns ‘(i, j, k)’ such that ‘a[i:i+k]’ is equal to
          ‘b[j:j+k]’, where ‘alo <= i <= i+k <= ahi’ and ‘blo <= j <=
          j+k <= bhi’.  For all ‘(i', j', k')’ meeting those conditions,
          the additional conditions ‘k >= k'’, ‘i <= i'’, and if ‘i ==
          i'’, ‘j <= j'’ are also met.  In other words, of all maximal
          matching blocks, return one that starts earliest in 'a', and
          of all those maximal matching blocks that start earliest in
          'a', return the one that starts earliest in 'b'.

               >>> s = SequenceMatcher(None, " abcd", "abcd abcd")
               >>> s.find_longest_match(0, 5, 0, 9)
               Match(a=0, b=4, size=5)

          If 'isjunk' was provided, first the longest matching block is
          determined as above, but with the additional restriction that
          no junk element appears in the block.  Then that block is
          extended as far as possible by matching (only) junk elements
          on both sides.  So the resulting block never matches on junk
          except as identical junk happens to be adjacent to an
          interesting match.

          Here's the same example as before, but considering blanks to
          be junk.  That prevents ‘' abcd'’ from matching the ‘' abcd'’
          at the tail end of the second sequence directly.  Instead only
          the ‘'abcd'’ can match, and matches the leftmost ‘'abcd'’ in
          the second sequence:

               >>> s = SequenceMatcher(lambda x: x==" ", " abcd", "abcd abcd")
               >>> s.find_longest_match(0, 5, 0, 9)
               Match(a=1, b=0, size=4)

          If no blocks match, this returns ‘(alo, blo, 0)’.

          This method returns a *note named tuple: 5f4. ‘Match(a, b,
          size)’.

          在 3.9 版的變更: 新增預設引數。

      -- 方法: get_matching_blocks ()

          Return list of triples describing non-overlapping matching
          subsequences.  Each triple is of the form ‘(i, j, n)’, and
          means that ‘a[i:i+n] == b[j:j+n]’.  The triples are
          monotonically increasing in 'i' and 'j'.

          The last triple is a dummy, and has the value ‘(len(a),
          len(b), 0)’.  It is the only triple with ‘n == 0’.  If ‘(i, j,
          n)’ and ‘(i', j', n')’ are adjacent triples in the list, and
          the second is not the last triple in the list, then ‘i+n < i'’
          or ‘j+n < j'’; in other words, adjacent triples always
          describe non-adjacent equal blocks.

               >>> s = SequenceMatcher(None, "abxcd", "abcd")
               >>> s.get_matching_blocks()
               [Match(a=0, b=0, size=2), Match(a=3, b=2, size=2), Match(a=5, b=4, size=0)]

      -- 方法: get_opcodes ()

          Return list of 5-tuples describing how to turn 'a' into 'b'.
          Each tuple is of the form ‘(tag, i1, i2, j1, j2)’.  The first
          tuple has ‘i1 == j1 == 0’, and remaining tuples have 'i1'
          equal to the 'i2' from the preceding tuple, and, likewise,
          'j1' equal to the previous 'j2'.

          The 'tag' values are strings, with these meanings:

          Value               含義
                              
          ----------------------------------------------------------------------
                              
          ‘'replace'’         ‘a[i1:i2]’ should be replaced by ‘b[j1:j2]’.
                              
                              
          ‘'delete'’          ‘a[i1:i2]’ should be deleted.  Note that ‘j1 ==
                              j2’ in this case.
                              
                              
          ‘'insert'’          ‘b[j1:j2]’ should be inserted at ‘a[i1:i1]’.
                              Note that ‘i1 == i2’ in this case.
                              
                              
          ‘'equal'’           ‘a[i1:i2] == b[j1:j2]’ (the sub-sequences are
                              equal).
                              

          舉例來說：

               >>> a = "qabxcd"
               >>> b = "abycdf"
               >>> s = SequenceMatcher(None, a, b)
               >>> for tag, i1, i2, j1, j2 in s.get_opcodes():
               ...     print('{:7}   a[{}:{}] --> b[{}:{}] {!r:>8} --> {!r}'.format(
               ...         tag, i1, i2, j1, j2, a[i1:i2], b[j1:j2]))
               delete    a[0:1] --> b[0:0]      'q' --> ''
               equal     a[1:3] --> b[0:2]     'ab' --> 'ab'
               replace   a[3:4] --> b[2:3]      'x' --> 'y'
               equal     a[4:6] --> b[3:5]     'cd' --> 'cd'
               insert    a[6:6] --> b[5:6]       '' --> 'f'

      -- 方法: get_grouped_opcodes (n=3)

          Return a *note generator: 1004. of groups with up to 'n' lines
          of context.

          Starting with the groups returned by *note get_opcodes():
          2220, this method splits out smaller change clusters and
          eliminates intervening ranges which have no changes.

          The groups are returned in the same format as *note
          get_opcodes(): 2220.

      -- 方法: ratio ()

          Return a measure of the sequences' similarity as a float in
          the range [0, 1].

          Where T is the total number of elements in both sequences, and
          M is the number of matches, this is 2.0*M / T. Note that this
          is ‘1.0’ if the sequences are identical, and ‘0.0’ if they
          have nothing in common.

          This is expensive to compute if *note get_matching_blocks():
          221f. or *note get_opcodes(): 2220. hasn't already been
          called, in which case you may want to try *note quick_ratio():
          2223. or *note real_quick_ratio(): 2224. first to get an upper
          bound.

               備註: Caution: The result of a *note ratio(): 2222. call
               may depend on the order of the arguments.  For instance:

                    >>> SequenceMatcher(None, 'tide', 'diet').ratio()
                    0.25
                    >>> SequenceMatcher(None, 'diet', 'tide').ratio()
                    0.5

      -- 方法: quick_ratio ()

          Return an upper bound on *note ratio(): 2222. relatively
          quickly.

      -- 方法: real_quick_ratio ()

          Return an upper bound on *note ratio(): 2222. very quickly.

The three methods that return the ratio of matching to total characters
can give different results due to differing levels of approximation,
although *note quick_ratio(): 2223. and *note real_quick_ratio(): 2224.
are always at least as large as *note ratio(): 2222.:

     >>> s = SequenceMatcher(None, "abcd", "bcde")
     >>> s.ratio()
     0.75
     >>> s.quick_ratio()
     0.75
     >>> s.real_quick_ratio()
     1.0


File: python.info,  Node: SequenceMatcher 範例,  Next: Differ Objects,  Prev: SequenceMatcher 物件,  Up: difflib --- 計算差異的輔助工具

5.6.3.2 SequenceMatcher 範例
............................

This example compares two strings, considering blanks to be "junk":

     >>> s = SequenceMatcher(lambda x: x == " ",
     ...                     "private Thread currentThread;",
     ...                     "private volatile Thread currentThread;")

*note ratio(): 2222. returns a float in [0, 1], measuring the similarity
of the sequences.  As a rule of thumb, a *note ratio(): 2222. value over
0.6 means the sequences are close matches:

     >>> print(round(s.ratio(), 3))
     0.866

If you're only interested in where the sequences match, *note
get_matching_blocks(): 221f. is handy:

     >>> for block in s.get_matching_blocks():
     ...     print("a[%d] and b[%d] match for %d elements" % block)
     a[0] and b[0] match for 8 elements
     a[8] and b[17] match for 21 elements
     a[29] and b[38] match for 0 elements

Note that the last tuple returned by *note get_matching_blocks(): 221f.
is always a dummy, ‘(len(a), len(b), 0)’, and this is the only case in
which the last tuple element (number of elements matched) is ‘0’.

If you want to know how to change the first sequence into the second,
use *note get_opcodes(): 2220.:

     >>> for opcode in s.get_opcodes():
     ...     print("%6s a[%d:%d] b[%d:%d]" % opcode)
      equal a[0:8] b[0:8]
     insert a[8:8] b[8:17]
      equal a[8:29] b[17:38]

也參考
......

   * The *note get_close_matches(): 2214. function in this module which
     shows how simple code building on *note SequenceMatcher: fba. can
     be used to do useful work.

   * Simple version control recipe(1) for a small application built with
     *note SequenceMatcher: fba.

   ---------- Footnotes ----------

   (1) 
https://code.activestate.com/recipes/576729-simple-version-control/


File: python.info,  Node: Differ Objects,  Next: Differ Example,  Prev: SequenceMatcher 範例,  Up: difflib --- 計算差異的輔助工具

5.6.3.3 Differ Objects
......................

Note that *note Differ: 220b.-generated deltas make no claim to be
'minimal' diffs.  To the contrary, minimal diffs are often
counter-intuitive, because they synch up anywhere possible, sometimes
accidental matches 100 pages apart.  Restricting synch points to
contiguous matches preserves some notion of locality, at the occasional
cost of producing a longer diff.

The *note Differ: 220b. class has this constructor:

 -- 類別: difflib.Differ (linejunk=None, charjunk=None)

     Optional keyword parameters 'linejunk' and 'charjunk' are for
     filter functions (or ‘None’):

     'linejunk': A function that accepts a single string argument, and
     returns true if the string is junk.  The default is ‘None’, meaning
     that no line is considered junk.

     'charjunk': A function that accepts a single character argument (a
     string of length 1), and returns true if the character is junk.
     The default is ‘None’, meaning that no character is considered
     junk.

     These junk-filtering functions speed up matching to find
     differences and do not cause any differing lines or characters to
     be ignored.  Read the description of the *note
     find_longest_match(): 1861. method's 'isjunk' parameter for an
     explanation.

     *note Differ: 220b. objects are used (deltas generated) via a
     single method:

      -- 方法: compare (a, b)

          Compare two sequences of lines, and generate the delta (a
          sequence of lines).

          Each sequence must contain individual single-line strings
          ending with newlines.  Such sequences can be obtained from the
          *note readlines(): 2211. method of file-like objects.  The
          delta generated also consists of newline-terminated strings,
          ready to be printed as-is via the *note writelines(): 2212.
          method of a file-like object.


File: python.info,  Node: Differ Example,  Next: A command-line interface to difflib,  Prev: Differ Objects,  Up: difflib --- 計算差異的輔助工具

5.6.3.4 Differ Example
......................

This example compares two texts.  First we set up the texts, sequences
of individual single-line strings ending with newlines (such sequences
can also be obtained from the *note readlines(): 2211. method of
file-like objects):

     >>> text1 = '''  1. Beautiful is better than ugly.
     ...   2. Explicit is better than implicit.
     ...   3. Simple is better than complex.
     ...   4. Complex is better than complicated.
     ... '''.splitlines(keepends=True)
     >>> len(text1)
     4
     >>> text1[0][-1]
     '\n'
     >>> text2 = '''  1. Beautiful is better than ugly.
     ...   3.   Simple is better than complex.
     ...   4. Complicated is better than complex.
     ...   5. Flat is better than nested.
     ... '''.splitlines(keepends=True)

Next we instantiate a Differ object:

     >>> d = Differ()

Note that when instantiating a *note Differ: 220b. object we may pass
functions to filter out line and character "junk."  See the *note
Differ(): 220b. constructor for details.

Finally, we compare the two:

     >>> result = list(d.compare(text1, text2))

‘result’ is a list of strings, so let's pretty-print it:

     >>> from pprint import pprint
     >>> pprint(result)
     ['    1. Beautiful is better than ugly.\n',
      '-   2. Explicit is better than implicit.\n',
      '-   3. Simple is better than complex.\n',
      '+   3.   Simple is better than complex.\n',
      '?     ++\n',
      '-   4. Complex is better than complicated.\n',
      '?            ^                     ---- ^\n',
      '+   4. Complicated is better than complex.\n',
      '?           ++++ ^                      ^\n',
      '+   5. Flat is better than nested.\n']

As a single multi-line string it looks like this:

     >>> import sys
     >>> sys.stdout.writelines(result)
         1. Beautiful is better than ugly.
     -   2. Explicit is better than implicit.
     -   3. Simple is better than complex.
     +   3.   Simple is better than complex.
     ?     ++
     -   4. Complex is better than complicated.
     ?            ^                     ---- ^
     +   4. Complicated is better than complex.
     ?           ++++ ^                      ^
     +   5. Flat is better than nested.


File: python.info,  Node: A command-line interface to difflib,  Next: ndiff 範例：,  Prev: Differ Example,  Up: difflib --- 計算差異的輔助工具

5.6.3.5 A command-line interface to difflib
...........................................

This example shows how to use difflib to create a ‘diff’-like utility.

     """ Command line interface to difflib.py providing diffs in four formats:

     * ndiff:    lists every line and highlights interline changes.
     * context:  highlights clusters of changes in a before/after format.
     * unified:  highlights clusters of changes in an inline format.
     * html:     generates side by side comparison with change highlights.

     """

     import sys, os, difflib, argparse
     from datetime import datetime, timezone

     def file_mtime(path):
         t = datetime.fromtimestamp(os.stat(path).st_mtime,
                                    timezone.utc)
         return t.astimezone().isoformat()

     def main():

         parser = argparse.ArgumentParser()
         parser.add_argument('-c', action='store_true', default=False,
                             help='Produce a context format diff (default)')
         parser.add_argument('-u', action='store_true', default=False,
                             help='Produce a unified format diff')
         parser.add_argument('-m', action='store_true', default=False,
                             help='Produce HTML side by side diff '
                                  '(can use -c and -l in conjunction)')
         parser.add_argument('-n', action='store_true', default=False,
                             help='Produce a ndiff format diff')
         parser.add_argument('-l', '--lines', type=int, default=3,
                             help='Set number of context lines (default 3)')
         parser.add_argument('fromfile')
         parser.add_argument('tofile')
         options = parser.parse_args()

         n = options.lines
         fromfile = options.fromfile
         tofile = options.tofile

         fromdate = file_mtime(fromfile)
         todate = file_mtime(tofile)
         with open(fromfile) as ff:
             fromlines = ff.readlines()
         with open(tofile) as tf:
             tolines = tf.readlines()

         if options.u:
             diff = difflib.unified_diff(fromlines, tolines, fromfile, tofile, fromdate, todate, n=n)
         elif options.n:
             diff = difflib.ndiff(fromlines, tolines)
         elif options.m:
             diff = difflib.HtmlDiff().make_file(fromlines,tolines,fromfile,tofile,context=options.c,numlines=n)
         else:
             diff = difflib.context_diff(fromlines, tolines, fromfile, tofile, fromdate, todate, n=n)

         sys.stdout.writelines(diff)

     if __name__ == '__main__':
         main()


File: python.info,  Node: ndiff 範例：,  Prev: A command-line interface to difflib,  Up: difflib --- 計算差異的輔助工具

5.6.3.6 ndiff 範例：
....................

This example shows how to use *note difflib.ndiff(): 220e.

     """ndiff [-q] file1 file2
         or
     ndiff (-r1 | -r2) < ndiff_output > file1_or_file2

     Print a human-friendly file difference report to stdout.  Both inter-
     and intra-line differences are noted.  In the second form, recreate file1
     (-r1) or file2 (-r2) on stdout, from an ndiff report on stdin.

     In the first form, if -q ("quiet") is not specified, the first two lines
     of output are

     -: file1
     +: file2

     Each remaining line begins with a two-letter code:

         "- "    line unique to file1
         "+ "    line unique to file2
         "  "    line common to both files
         "? "    line not present in either input file

     Lines beginning with "? " attempt to guide the eye to intraline
     differences, and were not present in either input file.  These lines can be
     confusing if the source files contain tab characters.

     The first file can be recovered by retaining only lines that begin with
     "  " or "- ", and deleting those 2-character prefixes; use ndiff with -r1.

     The second file can be recovered similarly, but by retaining only "  " and
     "+ " lines; use ndiff with -r2; or, on Unix, the second file can be
     recovered by piping the output through

         sed -n '/^[+ ] /s/^..//p'
     """

     __version__ = 1, 7, 0

     import difflib, sys

     def fail(msg):
         out = sys.stderr.write
         out(msg + "\n\n")
         out(__doc__)
         return 0

     # open a file & return the file object; gripe and return 0 if it
     # couldn't be opened
     def fopen(fname):
         try:
             return open(fname)
         except IOError as detail:
             return fail("couldn't open " + fname + ": " + str(detail))

     # open two files & spray the diff to stdout; return false iff a problem
     def fcompare(f1name, f2name):
         f1 = fopen(f1name)
         f2 = fopen(f2name)
         if not f1 or not f2:
             return 0

         a = f1.readlines(); f1.close()
         b = f2.readlines(); f2.close()
         for line in difflib.ndiff(a, b):
             print(line, end=' ')

         return 1

     # crack args (sys.argv[1:] is normal) & compare;
     # return false iff a problem

     def main(args):
         import getopt
         try:
             opts, args = getopt.getopt(args, "qr:")
         except getopt.error as detail:
             return fail(str(detail))
         noisy = 1
         qseen = rseen = 0
         for opt, val in opts:
             if opt == "-q":
                 qseen = 1
                 noisy = 0
             elif opt == "-r":
                 rseen = 1
                 whichfile = val
         if qseen and rseen:
             return fail("can't specify both -q and -r")
         if rseen:
             if args:
                 return fail("no args allowed with -r option")
             if whichfile in ("1", "2"):
                 restore(whichfile)
                 return 1
             return fail("-r value must be 1 or 2")
         if len(args) != 2:
             return fail("need 2 filename args")
         f1name, f2name = args
         if noisy:
             print('-:', f1name)
             print('+:', f2name)
         return fcompare(f1name, f2name)

     # read ndiff output from stdin, and print file1 (which=='1') or
     # file2 (which=='2') to stdout

     def restore(which):
         restored = difflib.restore(sys.stdin.readlines(), which)
         sys.stdout.writelines(restored)

     if __name__ == '__main__':
         main(sys.argv[1:])


File: python.info,  Node: textwrap --- 文字包裝與填充,  Next: unicodedata --- Unicode 資料庫,  Prev: difflib --- 計算差異的輔助工具,  Up: 文本處理 Text Processing 服務

5.6.4 ‘textwrap’ -- 文字包裝與填充
----------------------------------

'原始碼：'Lib/textwrap.py(1)

__________________________________________________________________

The *note textwrap: d5. module provides some convenience functions, as
well as *note TextWrapper: f70, the class that does all the work.  If
you're just wrapping or filling one or two text strings, the convenience
functions should be good enough; otherwise, you should use an instance
of *note TextWrapper: f70. for efficiency.

 -- 函式: textwrap.wrap (text, width=70, *, initial_indent='',
          subsequent_indent='', expand_tabs=True,
          replace_whitespace=True, fix_sentence_endings=False,
          break_long_words=True, drop_whitespace=True,
          break_on_hyphens=True, tabsize=8, max_lines=None,
          placeholder=' [...]')

     Wraps the single paragraph in 'text' (a string) so every line is at
     most 'width' characters long.  Returns a list of output lines,
     without final newlines.

     Optional keyword arguments correspond to the instance attributes of
     *note TextWrapper: f70, documented below.

     See the *note TextWrapper.wrap(): 222f. method for additional
     details on how *note wrap(): 1432. behaves.

 -- 函式: textwrap.fill (text, width=70, *, initial_indent='',
          subsequent_indent='', expand_tabs=True,
          replace_whitespace=True, fix_sentence_endings=False,
          break_long_words=True, drop_whitespace=True,
          break_on_hyphens=True, tabsize=8, max_lines=None,
          placeholder=' [...]')

     Wraps the single paragraph in 'text', and returns a single string
     containing the wrapped paragraph.  *note fill(): 1431. is shorthand
     for

          "\n".join(wrap(text, ...))

     In particular, *note fill(): 1431. accepts exactly the same keyword
     arguments as *note wrap(): 1432.

 -- 函式: textwrap.shorten (text, width, *, fix_sentence_endings=False,
          break_long_words=True, break_on_hyphens=True, placeholder='
          [...]')

     Collapse and truncate the given 'text' to fit in the given 'width'.

     First the whitespace in 'text' is collapsed (all whitespace is
     replaced by single spaces).  If the result fits in the 'width', it
     is returned.  Otherwise, enough words are dropped from the end so
     that the remaining words plus the 'placeholder' fit within 'width':

          >>> textwrap.shorten("Hello  world!", width=12)
          'Hello world!'
          >>> textwrap.shorten("Hello  world!", width=11)
          'Hello [...]'
          >>> textwrap.shorten("Hello world", width=10, placeholder="...")
          'Hello...'

     Optional keyword arguments correspond to the instance attributes of
     *note TextWrapper: f70, documented below.  Note that the whitespace
     is collapsed before the text is passed to the *note TextWrapper:
     f70. *note fill(): 1431. function, so changing the value of *note
     tabsize: 2230, *note expand_tabs: 2231, *note drop_whitespace:
     2232, and *note replace_whitespace: 2233. will have no effect.

     在 3.4 版被加入.

 -- 函式: textwrap.dedent (text)

     Remove any common leading whitespace from every line in 'text'.

     This can be used to make triple-quoted strings line up with the
     left edge of the display, while still presenting them in the source
     code in indented form.

     Note that tabs and spaces are both treated as whitespace, but they
     are not equal: the lines ‘" hello"’ and ‘"\thello"’ are considered
     to have no common leading whitespace.

     Lines containing only whitespace are ignored in the input and
     normalized to a single newline character in the output.

     舉例來說：

          def test():
              # end first line with \ to avoid the empty line!
              s = '''\
              hello
                world
              '''
              print(repr(s))          # prints '    hello\n      world\n    '
              print(repr(dedent(s)))  # prints 'hello\n  world\n'

 -- 函式: textwrap.indent (text, prefix, predicate=None)

     Add 'prefix' to the beginning of selected lines in 'text'.

     Lines are separated by calling ‘text.splitlines(True)’.

     By default, 'prefix' is added to all lines that do not consist
     solely of whitespace (including any line endings).

     舉例來說：

          >>> s = 'hello\n\n \nworld'
          >>> indent(s, '  ')
          '  hello\n\n \n  world'

     The optional 'predicate' argument can be used to control which
     lines are indented.  For example, it is easy to add 'prefix' to
     even empty and whitespace-only lines:

          >>> print(indent(s, '+ ', lambda line: True))
          + hello
          +
          +
          + world

     在 3.3 版被加入.

*note wrap(): 1432, *note fill(): 1431. and *note shorten(): f73. work
by creating a *note TextWrapper: f70. instance and calling a single
method on it.  That instance is not reused, so for applications that
process many text strings using *note wrap(): 1432. and/or *note fill():
1431, it may be more efficient to create your own *note TextWrapper:
f70. object.

Text is preferably wrapped on whitespaces and right after the hyphens in
hyphenated words; only then will long words be broken if necessary,
unless *note TextWrapper.break_long_words: 2235. is set to false.

 -- 類別: textwrap.TextWrapper (**kwargs)

     The *note TextWrapper: f70. constructor accepts a number of
     optional keyword arguments.  Each keyword argument corresponds to
     an instance attribute, so for example

          wrapper = TextWrapper(initial_indent="* ")

     is the same as

          wrapper = TextWrapper()
          wrapper.initial_indent = "* "

     You can reuse the same *note TextWrapper: f70. object many times,
     and you can change any of its options through direct assignment to
     instance attributes between uses.

     The *note TextWrapper: f70. instance attributes (and keyword
     arguments to the constructor) are as follows:

      -- 屬性: width

          (default: ‘70’) The maximum length of wrapped lines.  As long
          as there are no individual words in the input text longer than
          *note width: 2236, *note TextWrapper: f70. guarantees that no
          output line will be longer than *note width: 2236. characters.

      -- 屬性: expand_tabs

          (default: ‘True’) If true, then all tab characters in 'text'
          will be expanded to spaces using the *note expandtabs(): 2099.
          method of 'text'.

      -- 屬性: tabsize

          (default: ‘8’) If *note expand_tabs: 2231. is true, then all
          tab characters in 'text' will be expanded to zero or more
          spaces, depending on the current column and the given tab
          size.

          在 3.3 版被加入.

      -- 屬性: replace_whitespace

          (default: ‘True’) If true, after tab expansion but before
          wrapping, the *note wrap(): 1432. method will replace each
          whitespace character with a single space.  The whitespace
          characters replaced are as follows: tab, newline, vertical
          tab, formfeed, and carriage return (‘'\t\n\v\f\r'’).

               備註: If *note expand_tabs: 2231. is false and *note
               replace_whitespace: 2233. is true, each tab character
               will be replaced by a single space, which is 'not' the
               same as tab expansion.

               備註: If *note replace_whitespace: 2233. is false,
               newlines may appear in the middle of a line and cause
               strange output.  For this reason, text should be split
               into paragraphs (using *note str.splitlines(): 11ef. or
               similar) which are wrapped separately.

      -- 屬性: drop_whitespace

          (default: ‘True’) If true, whitespace at the beginning and
          ending of every line (after wrapping but before indenting) is
          dropped.  Whitespace at the beginning of the paragraph,
          however, is not dropped if non-whitespace follows it.  If
          whitespace being dropped takes up an entire line, the whole
          line is dropped.

      -- 屬性: initial_indent

          (default: ‘''’) String that will be prepended to the first
          line of wrapped output.  Counts towards the length of the
          first line.  The empty string is not indented.

      -- 屬性: subsequent_indent

          (default: ‘''’) String that will be prepended to all lines of
          wrapped output except the first.  Counts towards the length of
          each line except the first.

      -- 屬性: fix_sentence_endings

          (default: ‘False’) If true, *note TextWrapper: f70. attempts
          to detect sentence endings and ensure that sentences are
          always separated by exactly two spaces.  This is generally
          desired for text in a monospaced font.  However, the sentence
          detection algorithm is imperfect: it assumes that a sentence
          ending consists of a lowercase letter followed by one of
          ‘'.'’, ‘'!'’, or ‘'?'’, possibly followed by one of ‘'"'’ or
          ‘"'"’, followed by a space.  One problem with this algorithm
          is that it is unable to detect the difference between "Dr."
          in

               [...] Dr. Frankenstein's monster [...]

          and "Spot."  in

               [...] See Spot. See Spot run [...]

          *note fix_sentence_endings: 2239. is false by default.

          Since the sentence detection algorithm relies on
          ‘string.lowercase’ for the definition of "lowercase letter",
          and a convention of using two spaces after a period to
          separate sentences on the same line, it is specific to
          English-language texts.

      -- 屬性: break_long_words

          (default: ‘True’) If true, then words longer than *note width:
          2236. will be broken in order to ensure that no lines are
          longer than *note width: 2236.  If it is false, long words
          will not be broken, and some lines may be longer than *note
          width: 2236.  (Long words will be put on a line by themselves,
          in order to minimize the amount by which *note width: 2236. is
          exceeded.)

      -- 屬性: break_on_hyphens

          (default: ‘True’) If true, wrapping will occur preferably on
          whitespaces and right after hyphens in compound words, as it
          is customary in English.  If false, only whitespaces will be
          considered as potentially good places for line breaks, but you
          need to set *note break_long_words: 2235. to false if you want
          truly insecable words.  Default behaviour in previous versions
          was to always allow breaking hyphenated words.

      -- 屬性: max_lines

          (default: ‘None’) If not ‘None’, then the output will contain
          at most 'max_lines' lines, with 'placeholder' appearing at the
          end of the output.

          在 3.4 版被加入.

      -- 屬性: placeholder

          (default: ‘' [...]'’) String that will appear at the end of
          the output text if it has been truncated.

          在 3.4 版被加入.

     *note TextWrapper: f70. also provides some public methods,
     analogous to the module-level convenience functions:

      -- 方法: wrap (text)

          Wraps the single paragraph in 'text' (a string) so every line
          is at most *note width: 2236. characters long.  All wrapping
          options are taken from instance attributes of the *note
          TextWrapper: f70. instance.  Returns a list of output lines,
          without final newlines.  If the wrapped output has no content,
          the returned list is empty.

      -- 方法: fill (text)

          Wraps the single paragraph in 'text', and returns a single
          string containing the wrapped paragraph.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/textwrap.py


File: python.info,  Node: unicodedata --- Unicode 資料庫,  Next: stringprep --- 網際網路字串準備,  Prev: textwrap --- 文字包裝與填充,  Up: 文本處理 Text Processing 服務

5.6.5 ‘unicodedata’ -- Unicode 資料庫
-------------------------------------

__________________________________________________________________

This module provides access to the Unicode Character Database (UCD)
which defines character properties for all Unicode characters.  The data
contained in this database is compiled from the UCD version 15.1.0(1).

The module uses the same names and symbols as defined by Unicode
Standard Annex #44, "Unicode Character Database"(2).  It defines the
following functions:

 -- 函式: unicodedata.lookup (name)

     Look up character by name.  If a character with the given name is
     found, return the corresponding character.  If not found, *note
     KeyError: 2fb. is raised.

     在 3.3 版的變更: Support for name aliases (3) and named sequences
     (4) has been added.

 -- 函式: unicodedata.name (chr[, default])

     Returns the name assigned to the character 'chr' as a string.  If
     no name is defined, 'default' is returned, or, if not given, *note
     ValueError: 1e7. is raised.

 -- 函式: unicodedata.decimal (chr[, default])

     Returns the decimal value assigned to the character 'chr' as
     integer.  If no such value is defined, 'default' is returned, or,
     if not given, *note ValueError: 1e7. is raised.

 -- 函式: unicodedata.digit (chr[, default])

     Returns the digit value assigned to the character 'chr' as integer.
     If no such value is defined, 'default' is returned, or, if not
     given, *note ValueError: 1e7. is raised.

 -- 函式: unicodedata.numeric (chr[, default])

     Returns the numeric value assigned to the character 'chr' as float.
     If no such value is defined, 'default' is returned, or, if not
     given, *note ValueError: 1e7. is raised.

 -- 函式: unicodedata.category (chr)

     Returns the general category assigned to the character 'chr' as
     string.

 -- 函式: unicodedata.bidirectional (chr)

     Returns the bidirectional class assigned to the character 'chr' as
     string.  If no such value is defined, an empty string is returned.

 -- 函式: unicodedata.combining (chr)

     Returns the canonical combining class assigned to the character
     'chr' as integer.  Returns ‘0’ if no combining class is defined.

 -- 函式: unicodedata.east_asian_width (chr)

     Returns the east asian width assigned to the character 'chr' as
     string.

 -- 函式: unicodedata.mirrored (chr)

     Returns the mirrored property assigned to the character 'chr' as
     integer.  Returns ‘1’ if the character has been identified as a
     "mirrored" character in bidirectional text, ‘0’ otherwise.

 -- 函式: unicodedata.decomposition (chr)

     Returns the character decomposition mapping assigned to the
     character 'chr' as string.  An empty string is returned in case no
     such mapping is defined.

 -- 函式: unicodedata.normalize (form, unistr)

     Return the normal form 'form' for the Unicode string 'unistr'.
     Valid values for 'form' are 'NFC', 'NFKC', 'NFD', and 'NFKD'.

     The Unicode standard defines various normalization forms of a
     Unicode string, based on the definition of canonical equivalence
     and compatibility equivalence.  In Unicode, several characters can
     be expressed in various way.  For example, the character U+00C7
     (LATIN CAPITAL LETTER C WITH CEDILLA) can also be expressed as the
     sequence U+0043 (LATIN CAPITAL LETTER C) U+0327 (COMBINING
     CEDILLA).

     For each character, there are two normal forms: normal form C and
     normal form D. Normal form D (NFD) is also known as canonical
     decomposition, and translates each character into its decomposed
     form.  Normal form C (NFC) first applies a canonical decomposition,
     then composes pre-combined characters again.

     In addition to these two forms, there are two additional normal
     forms based on compatibility equivalence.  In Unicode, certain
     characters are supported which normally would be unified with other
     characters.  For example, U+2160 (ROMAN NUMERAL ONE) is really the
     same thing as U+0049 (LATIN CAPITAL LETTER I). However, it is
     supported in Unicode for compatibility with existing character sets
     (e.g.  gb2312).

     The normal form KD (NFKD) will apply the compatibility
     decomposition, i.e.  replace all compatibility characters with
     their equivalents.  The normal form KC (NFKC) first applies the
     compatibility decomposition, followed by the canonical composition.

     Even if two unicode strings are normalized and look the same to a
     human reader, if one has combining characters and the other
     doesn't, they may not compare equal.

 -- 函式: unicodedata.is_normalized (form, unistr)

     Return whether the Unicode string 'unistr' is in the normal form
     'form'.  Valid values for 'form' are 'NFC', 'NFKC', 'NFD', and
     'NFKD'.

     在 3.8 版被加入.

In addition, the module exposes the following constant:

 -- 資料: unicodedata.unidata_version

     The version of the Unicode database used in this module.

 -- 資料: unicodedata.ucd_3_2_0

     This is an object that has the same methods as the entire module,
     but uses the Unicode database version 3.2 instead, for applications
     that require this specific version of the Unicode database (such as
     IDNA).

範例：

     >>> import unicodedata
     >>> unicodedata.lookup('LEFT CURLY BRACKET')
     '{'
     >>> unicodedata.name('/')
     'SOLIDUS'
     >>> unicodedata.decimal('9')
     9
     >>> unicodedata.decimal('a')
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     ValueError: not a decimal
     >>> unicodedata.category('A')  # 'L'etter, 'u'ppercase
     'Lu'
     >>> unicodedata.bidirectional('\u0660') # 'A'rabic, 'N'umber
     'AN'

註解
....

   ---------- Footnotes ----------

   (1) https://www.unicode.org/Public/15.1.0/ucd

   (2) https://www.unicode.org/reports/tr44/

   (3) ‘https://www.unicode.org/Public/15.1.0/ucd/NameAliases.txt’

   (4) ‘https://www.unicode.org/Public/15.1.0/ucd/NamedSequences.txt’


File: python.info,  Node: stringprep --- 網際網路字串準備,  Next: readline --- GNU readline 介面,  Prev: unicodedata --- Unicode 資料庫,  Up: 文本處理 Text Processing 服務

5.6.6 ‘stringprep’ -- 網際網路字串準備
--------------------------------------

'原始碼：'Lib/stringprep.py(1)

__________________________________________________________________

When identifying things (such as host names) in the internet, it is
often necessary to compare such identifications for "equality".  Exactly
how this comparison is executed may depend on the application domain,
e.g.  whether it should be case-insensitive or not.  It may be also
necessary to restrict the possible identifications, to allow only
identifications consisting of "printable" characters.

RFC 3454(2) defines a procedure for "preparing" Unicode strings in
internet protocols.  Before passing strings onto the wire, they are
processed with the preparation procedure, after which they have a
certain normalized form.  The RFC defines a set of tables, which can be
combined into profiles.  Each profile must define which tables it uses,
and what other optional parts of the ‘stringprep’ procedure are part of
the profile.  One example of a ‘stringprep’ profile is ‘nameprep’, which
is used for internationalized domain names.

The module *note stringprep: bf. only exposes the tables from RFC
3454(3).  As these tables would be very large to represent as
dictionaries or lists, the module uses the Unicode character database
internally.  The module source code itself was generated using the
‘mkstringprep.py’ utility.

As a result, these tables are exposed as functions, not as data
structures.  There are two kinds of tables in the RFC: sets and
mappings.  For a set, *note stringprep: bf. provides the "characteristic
function", i.e.  a function that returns ‘True’ if the parameter is part
of the set.  For mappings, it provides the mapping function: given the
key, it returns the associated value.  Below is a list of all functions
available in the module.

 -- 函式: stringprep.in_table_a1 (code)

     Determine whether 'code' is in tableA.1 (Unassigned code points in
     Unicode 3.2).

 -- 函式: stringprep.in_table_b1 (code)

     Determine whether 'code' is in tableB.1 (Commonly mapped to
     nothing).

 -- 函式: stringprep.map_table_b2 (code)

     Return the mapped value for 'code' according to tableB.2 (Mapping
     for case-folding used with NFKC).

 -- 函式: stringprep.map_table_b3 (code)

     Return the mapped value for 'code' according to tableB.3 (Mapping
     for case-folding used with no normalization).

 -- 函式: stringprep.in_table_c11 (code)

     Determine whether 'code' is in tableC.1.1 (ASCII space characters).

 -- 函式: stringprep.in_table_c12 (code)

     Determine whether 'code' is in tableC.1.2 (Non-ASCII space
     characters).

 -- 函式: stringprep.in_table_c11_c12 (code)

     Determine whether 'code' is in tableC.1 (Space characters, union of
     C.1.1 and C.1.2).

 -- 函式: stringprep.in_table_c21 (code)

     Determine whether 'code' is in tableC.2.1 (ASCII control
     characters).

 -- 函式: stringprep.in_table_c22 (code)

     Determine whether 'code' is in tableC.2.2 (Non-ASCII control
     characters).

 -- 函式: stringprep.in_table_c21_c22 (code)

     Determine whether 'code' is in tableC.2 (Control characters, union
     of C.2.1 and C.2.2).

 -- 函式: stringprep.in_table_c3 (code)

     Determine whether 'code' is in tableC.3 (Private use).

 -- 函式: stringprep.in_table_c4 (code)

     Determine whether 'code' is in tableC.4 (Non-character code
     points).

 -- 函式: stringprep.in_table_c5 (code)

     Determine whether 'code' is in tableC.5 (Surrogate codes).

 -- 函式: stringprep.in_table_c6 (code)

     Determine whether 'code' is in tableC.6 (Inappropriate for plain
     text).

 -- 函式: stringprep.in_table_c7 (code)

     Determine whether 'code' is in tableC.7 (Inappropriate for
     canonical representation).

 -- 函式: stringprep.in_table_c8 (code)

     Determine whether 'code' is in tableC.8 (Change display properties
     or are deprecated).

 -- 函式: stringprep.in_table_c9 (code)

     Determine whether 'code' is in tableC.9 (Tagging characters).

 -- 函式: stringprep.in_table_d1 (code)

     Determine whether 'code' is in tableD.1 (Characters with
     bidirectional property "R" or "AL").

 -- 函式: stringprep.in_table_d2 (code)

     Determine whether 'code' is in tableD.2 (Characters with
     bidirectional property "L").

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/stringprep.py

   (2) https://datatracker.ietf.org/doc/html/rfc3454.html

   (3) https://datatracker.ietf.org/doc/html/rfc3454.html


File: python.info,  Node: readline --- GNU readline 介面,  Next: rlcompleter --- GNU readline 的補全函式,  Prev: stringprep --- 網際網路字串準備,  Up: 文本處理 Text Processing 服務

5.6.7 ‘readline’ -- GNU readline 介面
-------------------------------------

__________________________________________________________________

The *note readline: a8. module defines a number of functions to
facilitate completion and reading/writing of history files from the
Python interpreter.  This module can be used directly, or via the *note
rlcompleter: ab. module, which supports completion of Python identifiers
at the interactive prompt.  Settings made using this module affect the
behaviour of both the interpreter's interactive prompt and the prompts
offered by the built-in *note input(): 126b. function.

Readline keybindings may be configured via an initialization file,
typically ‘.inputrc’ in your home directory.  See Readline Init File(1)
in the GNU Readline manual for information about the format and
allowable constructs of that file, and the capabilities of the Readline
library in general.

*note Availability: 1c56.: not WASI, not iOS.

This module does not work or is not available on WebAssembly platforms,
or on iOS. See *note WebAssembly 平台: 16e6. for more information on
WASM availability; see *note iOS: 1d56. for more information on iOS
availability.

     備註: The underlying Readline library API may be implemented by the
     ‘editline’ (‘libedit’) library instead of GNU readline.  On macOS
     the *note readline: a8. module detects which library is being used
     at run time.

     The configuration file for ‘editline’ is different from that of GNU
     readline.  If you programmatically load configuration strings you
     can use *note backend: 15a7. to determine which library is being
     used.

     If you use ‘editline’/‘libedit’ readline emulation on macOS, the
     initialization file located in your home directory is named
     ‘.editrc’.  For example, the following content in ‘~/.editrc’ will
     turn ON 'vi' keybindings and TAB completion:

          python:bind -v
          python:bind ^I rl_complete

     Also note that different libraries may use different history file
     formats.  When switching the underlying library, existing history
     files may become unusable.

 -- 資料: readline.backend

     The name of the underlying Readline library being used, either
     ‘"readline"’ or ‘"editline"’.

     在 3.13 版被加入.

* Menu:

* Init file::
* Line buffer::
* History file::
* History list::
* Startup hooks::
* Completion::
* 範例::

   ---------- Footnotes ----------

   (1) 
https://tiswww.cwru.edu/php/chet/readline/rluserman.html#Readline-Init-File


File: python.info,  Node: Init file,  Next: Line buffer,  Up: readline --- GNU readline 介面

5.6.7.1 Init file
.................

The following functions relate to the init file and user configuration:

 -- 函式: readline.parse_and_bind (string)

     Execute the init line provided in the 'string' argument.  This
     calls ‘rl_parse_and_bind()’ in the underlying library.

 -- 函式: readline.read_init_file ([filename])

     Execute a readline initialization file.  The default filename is
     the last filename used.  This calls ‘rl_read_init_file()’ in the
     underlying library.


File: python.info,  Node: Line buffer,  Next: History file,  Prev: Init file,  Up: readline --- GNU readline 介面

5.6.7.2 Line buffer
...................

The following functions operate on the line buffer:

 -- 函式: readline.get_line_buffer ()

     Return the current contents of the line buffer (‘rl_line_buffer’ in
     the underlying library).

 -- 函式: readline.insert_text (string)

     Insert text into the line buffer at the cursor position.  This
     calls ‘rl_insert_text()’ in the underlying library, but ignores the
     return value.

 -- 函式: readline.redisplay ()

     Change what's displayed on the screen to reflect the current
     contents of the line buffer.  This calls ‘rl_redisplay()’ in the
     underlying library.


File: python.info,  Node: History file,  Next: History list,  Prev: Line buffer,  Up: readline --- GNU readline 介面

5.6.7.3 History file
....................

The following functions operate on a history file:

 -- 函式: readline.read_history_file ([filename])

     Load a readline history file, and append it to the history list.
     The default filename is ‘~/.history’.  This calls ‘read_history()’
     in the underlying library.

 -- 函式: readline.write_history_file ([filename])

     Save the history list to a readline history file, overwriting any
     existing file.  The default filename is ‘~/.history’.  This calls
     ‘write_history()’ in the underlying library.

 -- 函式: readline.append_history_file (nelements[, filename])

     Append the last 'nelements' items of history to a file.  The
     default filename is ‘~/.history’.  The file must already exist.
     This calls ‘append_history()’ in the underlying library.  This
     function only exists if Python was compiled for a version of the
     library that supports it.

     在 3.5 版被加入.

 -- 函式: readline.get_history_length ()
 -- 函式: readline.set_history_length (length)

     Set or return the desired number of lines to save in the history
     file.  The *note write_history_file(): 2267. function uses this
     value to truncate the history file, by calling
     ‘history_truncate_file()’ in the underlying library.  Negative
     values imply unlimited history file size.


File: python.info,  Node: History list,  Next: Startup hooks,  Prev: History file,  Up: readline --- GNU readline 介面

5.6.7.4 History list
....................

The following functions operate on a global history list:

 -- 函式: readline.clear_history ()

     Clear the current history.  This calls ‘clear_history()’ in the
     underlying library.  The Python function only exists if Python was
     compiled for a version of the library that supports it.

 -- 函式: readline.get_current_history_length ()

     Return the number of items currently in the history.  (This is
     different from *note get_history_length(): 2268, which returns the
     maximum number of lines that will be written to a history file.)

 -- 函式: readline.get_history_item (index)

     Return the current contents of history item at 'index'.  The item
     index is one-based.  This calls ‘history_get()’ in the underlying
     library.

 -- 函式: readline.remove_history_item (pos)

     Remove history item specified by its position from the history.
     The position is zero-based.  This calls ‘remove_history()’ in the
     underlying library.

 -- 函式: readline.replace_history_item (pos, line)

     Replace history item specified by its position with 'line'.  The
     position is zero-based.  This calls ‘replace_history_entry()’ in
     the underlying library.

 -- 函式: readline.add_history (line)

     Append 'line' to the history buffer, as if it was the last line
     typed.  This calls ‘add_history()’ in the underlying library.

 -- 函式: readline.set_auto_history (enabled)

     Enable or disable automatic calls to ‘add_history()’ when reading
     input via readline.  The 'enabled' argument should be a Boolean
     value that when true, enables auto history, and that when false,
     disables auto history.

     在 3.6 版被加入.

     'CPython 實作細節：' Auto history is enabled by default, and
     changes to this do not persist across multiple sessions.


File: python.info,  Node: Startup hooks,  Next: Completion,  Prev: History list,  Up: readline --- GNU readline 介面

5.6.7.5 Startup hooks
.....................

 -- 函式: readline.set_startup_hook ([function])

     Set or remove the function invoked by the ‘rl_startup_hook’
     callback of the underlying library.  If 'function' is specified, it
     will be used as the new hook function; if omitted or ‘None’, any
     function already installed is removed.  The hook is called with no
     arguments just before readline prints the first prompt.

 -- 函式: readline.set_pre_input_hook ([function])

     Set or remove the function invoked by the ‘rl_pre_input_hook’
     callback of the underlying library.  If 'function' is specified, it
     will be used as the new hook function; if omitted or ‘None’, any
     function already installed is removed.  The hook is called with no
     arguments after the first prompt has been printed and just before
     readline starts reading input characters.  This function only
     exists if Python was compiled for a version of the library that
     supports it.


File: python.info,  Node: Completion,  Next: 範例,  Prev: Startup hooks,  Up: readline --- GNU readline 介面

5.6.7.6 Completion
..................

The following functions relate to implementing a custom word completion
function.  This is typically operated by the Tab key, and can suggest
and automatically complete a word being typed.  By default, Readline is
set up to be used by *note rlcompleter: ab. to complete Python
identifiers for the interactive interpreter.  If the *note readline: a8.
module is to be used with a custom completer, a different set of word
delimiters should be set.

 -- 函式: readline.set_completer ([function])

     Set or remove the completer function.  If 'function' is specified,
     it will be used as the new completer function; if omitted or
     ‘None’, any completer function already installed is removed.  The
     completer function is called as ‘function(text, state)’, for
     'state' in ‘0’, ‘1’, ‘2’, ..., until it returns a non-string value.
     It should return the next possible completion starting with 'text'.

     The installed completer function is invoked by the 'entry_func'
     callback passed to ‘rl_completion_matches()’ in the underlying
     library.  The 'text' string comes from the first parameter to the
     ‘rl_attempted_completion_function’ callback of the underlying
     library.

 -- 函式: readline.get_completer ()

     Get the completer function, or ‘None’ if no completer function has
     been set.

 -- 函式: readline.get_completion_type ()

     Get the type of completion being attempted.  This returns the
     ‘rl_completion_type’ variable in the underlying library as an
     integer.

 -- 函式: readline.get_begidx ()
 -- 函式: readline.get_endidx ()

     Get the beginning or ending index of the completion scope.  These
     indexes are the 'start' and 'end' arguments passed to the
     ‘rl_attempted_completion_function’ callback of the underlying
     library.  The values may be different in the same input editing
     scenario based on the underlying C readline implementation.  Ex:
     libedit is known to behave differently than libreadline.

 -- 函式: readline.set_completer_delims (string)
 -- 函式: readline.get_completer_delims ()

     Set or get the word delimiters for completion.  These determine the
     start of the word to be considered for completion (the completion
     scope).  These functions access the
     ‘rl_completer_word_break_characters’ variable in the underlying
     library.

 -- 函式: readline.set_completion_display_matches_hook ([function])

     Set or remove the completion display function.  If 'function' is
     specified, it will be used as the new completion display function;
     if omitted or ‘None’, any completion display function already
     installed is removed.  This sets or clears the
     ‘rl_completion_display_matches_hook’ callback in the underlying
     library.  The completion display function is called as
     ‘function(substitution, [matches], longest_match_length)’ once each
     time matches need to be displayed.


File: python.info,  Node: 範例,  Prev: Completion,  Up: readline --- GNU readline 介面

5.6.7.7 範例
............

The following example demonstrates how to use the *note readline: a8.
module's history reading and writing functions to automatically load and
save a history file named ‘.python_history’ from the user's home
directory.  The code below would normally be executed automatically
during interactive sessions from the user's *note PYTHONSTARTUP: f6b.
file.

     import atexit
     import os
     import readline

     histfile = os.path.join(os.path.expanduser("~"), ".python_history")
     try:
         readline.read_history_file(histfile)
         # default history len is -1 (infinite), which may grow unruly
         readline.set_history_length(1000)
     except FileNotFoundError:
         pass

     atexit.register(readline.write_history_file, histfile)

This code is actually automatically run when Python is run in *note
interactive mode: f69. (see *note Readline configuration: f6c.).

The following example achieves the same goal but supports concurrent
interactive sessions, by only appending the new history.

     import atexit
     import os
     import readline
     histfile = os.path.join(os.path.expanduser("~"), ".python_history")

     try:
         readline.read_history_file(histfile)
         h_len = readline.get_current_history_length()
     except FileNotFoundError:
         open(histfile, 'wb').close()
         h_len = 0

     def save(prev_h_len, histfile):
         new_h_len = readline.get_current_history_length()
         readline.set_history_length(1000)
         readline.append_history_file(new_h_len - prev_h_len, histfile)
     atexit.register(save, h_len, histfile)

The following example extends the *note code.InteractiveConsole: 227a.
class to support history save/restore.

     import atexit
     import code
     import os
     import readline

     class HistoryConsole(code.InteractiveConsole):
         def __init__(self, locals=None, filename="<console>",
                      histfile=os.path.expanduser("~/.console-history")):
             code.InteractiveConsole.__init__(self, locals, filename)
             self.init_history(histfile)

         def init_history(self, histfile):
             readline.parse_and_bind("tab: complete")
             if hasattr(readline, "read_history_file"):
                 try:
                     readline.read_history_file(histfile)
                 except FileNotFoundError:
                     pass
                 atexit.register(self.save_history, histfile)

         def save_history(self, histfile):
             readline.set_history_length(1000)
             readline.write_history_file(histfile)


File: python.info,  Node: rlcompleter --- GNU readline 的補全函式,  Prev: readline --- GNU readline 介面,  Up: 文本處理 Text Processing 服務

5.6.8 ‘rlcompleter’ -- GNU readline 的補全函式
----------------------------------------------

'原始碼：'Lib/rlcompleter.py(1)

__________________________________________________________________

The ‘rlcompleter’ module defines a completion function suitable to be
passed to *note set_completer(): 2273. in the *note readline: a8.
module.

When this module is imported on a Unix platform with the *note readline:
a8. module available, an instance of the *note Completer: 1846. class is
automatically created and its *note complete(): 227d. method is set as
the *note readline completer: 2272.  The method provides completion of
valid Python *note identifiers and keywords: 1d86.

範例：

     >>> import rlcompleter
     >>> import readline
     >>> readline.parse_and_bind("tab: complete")
     >>> readline. <TAB PRESSED>
     readline.__doc__          readline.get_line_buffer(  readline.read_init_file(
     readline.__file__         readline.insert_text(      readline.set_completer(
     readline.__name__         readline.parse_and_bind(
     >>> readline.

The ‘rlcompleter’ module is designed for use with Python's *note
interactive mode: f69.  Unless Python is run with the *note -S: 1140.
option, the module is automatically imported and configured (see *note
Readline configuration: f6c.).

On platforms without *note readline: a8, the *note Completer: 1846.
class defined by this module can still be used for custom purposes.

 -- 類別: rlcompleter.Completer

     Completer objects have the following method:

      -- 方法: complete (text, state)

          Return the next possible completion for 'text'.

          When called by the *note readline: a8. module, this method is
          called successively with ‘state == 0, 1, 2, ...’ until the
          method returns ‘None’.

          If called for 'text' that doesn't include a period character
          (‘'.'’), it will complete from names currently defined in
          *note __main__: 1, *note builtins: e. and keywords (as defined
          by the *note keyword: 78. module).

          If called for a dotted name, it will try to evaluate anything
          without obvious side-effects (functions will not be evaluated,
          but it can generate calls to *note __getattr__(): 47a.) up to
          the last part, and find matches for the rest via the *note
          dir(): 5d8. function.  Any exception raised during the
          evaluation of the expression is caught, silenced and *note
          None: 61b. is returned.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/rlcompleter.py


File: python.info,  Node: 二進位資料服務,  Next: 資料型別,  Prev: 文本處理 Text Processing 服務,  Up: Python 標準函式庫 Standard Library

5.7 二進位資料服務
==================

本章所描述的模組提供了一些基本的二進位資料操作服務。而針對二進位資料的其
他操作──尤其是關於檔案格式和網路協定的部分──則會在相關章節中詳細描述。

一些在 *note 文本處理 (Text Processing) 服務: 2097. 中提及的函式庫也可處
理 ASCII 相容的二進位格式（例如，*note re: a7.）及所有的二進位資料（例如
，*note difflib: 2f.）。

此外，請參閱 Python 內建的二進位資料類型的文件，詳情請參考 *note Binary
Sequence Types -- bytes, bytearray, memoryview: 2039.。

* Menu:

* struct: struct --- 將位元組直譯為打包起來的二進位資料. 將位元組直譯為打包起來的二進位資料
* codecs: codecs --- 編解碼器註冊表和基底類別. 編解碼器註冊表和基底類別


File: python.info,  Node: struct --- 將位元組直譯為打包起來的二進位資料,  Next: codecs --- 編解碼器註冊表和基底類別,  Up: 二進位資料服務

5.7.1 ‘struct’ -- 將位元組直譯為打包起來的二進位資料
----------------------------------------------------

'原始碼：'Lib/struct.py(1)

__________________________________________________________________

This module converts between Python values and C structs represented as
Python *note bytes: 1a5. objects.  Compact *note format strings: 2283.
describe the intended conversions to/from Python values.  The module's
functions and objects can be used for two largely distinct applications,
data exchange with external sources (files or network connections), or
data transfer between the Python application and the C layer.

     備註: When no prefix character is given, native mode is the
     default.  It packs or unpacks data based on the platform and
     compiler on which the Python interpreter was built.  The result of
     packing a given C struct includes pad bytes which maintain proper
     alignment for the C types involved; similarly, alignment is taken
     into account when unpacking.  In contrast, when communicating data
     between external sources, the programmer is responsible for
     defining byte ordering and padding between elements.  See *note
     Byte Order, Size, and Alignment: 2284. for details.

Several *note struct: c0. functions (and methods of *note Struct: 15a9.)
take a 'buffer' argument.  This refers to objects that implement the
*note 緩衝協定 (Buffer Protocol): 367. and provide either a readable or
read-writable buffer.  The most common types used for that purpose are
*note bytes: 1a5. and *note bytearray: 4e3, but many other types that
can be viewed as an array of bytes implement the buffer protocol, so
that they can be read/filled without additional copying from a *note
bytes: 1a5. object.

* Menu:

* 函式與例外::
* Format Strings::
* Applications::
* Classes: Classes<2>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/struct.py


File: python.info,  Node: 函式與例外,  Next: Format Strings,  Up: struct --- 將位元組直譯為打包起來的二進位資料

5.7.1.1 函式與例外
..................

The module defines the following exception and functions:

 -- 例外: struct.error

     Exception raised on various occasions; argument is a string
     describing what is wrong.

 -- 函式: struct.pack (format, v1, v2, ...)

     Return a bytes object containing the values 'v1', 'v2', ...  packed
     according to the format string 'format'.  The arguments must match
     the values required by the format exactly.

 -- 函式: struct.pack_into (format, buffer, offset, v1, v2, ...)

     Pack the values 'v1', 'v2', ...  according to the format string
     'format' and write the packed bytes into the writable buffer
     'buffer' starting at position 'offset'.  Note that 'offset' is a
     required argument.

 -- 函式: struct.unpack (format, buffer)

     Unpack from the buffer 'buffer' (presumably packed by ‘pack(format,
     ...)’) according to the format string 'format'.  The result is a
     tuple even if it contains exactly one item.  The buffer's size in
     bytes must match the size required by the format, as reflected by
     *note calcsize(): 18c9.

 -- 函式: struct.unpack_from (format, /, buffer, offset=0)

     Unpack from 'buffer' starting at position 'offset', according to
     the format string 'format'.  The result is a tuple even if it
     contains exactly one item.  The buffer's size in bytes, starting at
     position 'offset', must be at least the size required by the
     format, as reflected by *note calcsize(): 18c9.

 -- 函式: struct.iter_unpack (format, buffer)

     Iteratively unpack from the buffer 'buffer' according to the format
     string 'format'.  This function returns an iterator which will read
     equally sized chunks from the buffer until all its contents have
     been consumed.  The buffer's size in bytes must be a multiple of
     the size required by the format, as reflected by *note calcsize():
     18c9.

     Each iteration yields a tuple as specified by the format string.

     在 3.4 版被加入.

 -- 函式: struct.calcsize (format)

     Return the size of the struct (and hence of the bytes object
     produced by ‘pack(format, ...)’) corresponding to the format string
     'format'.


File: python.info,  Node: Format Strings,  Next: Applications,  Prev: 函式與例外,  Up: struct --- 將位元組直譯為打包起來的二進位資料

5.7.1.2 Format Strings
......................

Format strings describe the data layout when packing and unpacking data.
They are built up from *note format characters: 2289, which specify the
type of data being packed/unpacked.  In addition, special characters
control the *note byte order, size and alignment: 2284.  Each format
string consists of an optional prefix character which describes the
overall properties of the data and one or more format characters which
describe the actual data values and padding.

* Menu:

* Byte Order, Size, and Alignment: Byte Order Size and Alignment.
* Format Characters::
* 範例: 範例<2>.


File: python.info,  Node: Byte Order Size and Alignment,  Next: Format Characters,  Up: Format Strings

5.7.1.3 Byte Order, Size, and Alignment
.......................................

By default, C types are represented in the machine's native format and
byte order, and properly aligned by skipping pad bytes if necessary
(according to the rules used by the C compiler).  This behavior is
chosen so that the bytes of a packed struct correspond exactly to the
memory layout of the corresponding C struct.  Whether to use native byte
ordering and padding or standard formats depends on the application.

Alternatively, the first character of the format string can be used to
indicate the byte order, size and alignment of the packed data,
according to the following table:

Character       Byte order                   Size           Alignment
                                                            
----------------------------------------------------------------------------
                                                            
‘@’             native                       native         native
                                                            
                                                            
‘=’             native                       standard       none
                                                            
                                                            
‘<’             little-endian                standard       none
                                                            
                                                            
‘>’             big-endian                   standard       none
                                                            
                                                            
‘!’             network (= big-endian)       standard       none
                                                            

If the first character is not one of these, ‘'@'’ is assumed.

     備註: The number 1023 (‘0x3ff’ in hexadecimal) has the following
     byte representations:

        * ‘03 ff’ in big-endian (‘>’)

        * ‘ff 03’ in little-endian (‘<’)

     Python example:

          >>> import struct
          >>> struct.pack('>h', 1023)
          b'\x03\xff'
          >>> struct.pack('<h', 1023)
          b'\xff\x03'

Native byte order is big-endian or little-endian, depending on the host
system.  For example, Intel x86, AMD64 (x86-64), and Apple M1 are
little-endian; IBM z and many legacy architectures are big-endian.  Use
*note sys.byteorder: 2078. to check the endianness of your system.

Native size and alignment are determined using the C compiler's ‘sizeof’
expression.  This is always combined with native byte order.

Standard size depends only on the format character; see the table in the
*note Format Characters: 2289. section.

Note the difference between ‘'@'’ and ‘'='’: both use native byte order,
but the size and alignment of the latter is standardized.

The form ‘'!'’ represents the network byte order which is always
big-endian as defined in IETF RFC 1700(1).

There is no way to indicate non-native byte order (force byte-swapping);
use the appropriate choice of ‘'<'’ or ‘'>'’.

註解：

  1. Padding is only automatically added between successive structure
     members.  No padding is added at the beginning or the end of the
     encoded struct.

  2. No padding is added when using non-native size and alignment, e.g.
     with '<', '>', '=', and '!'.

  3. To align the end of a structure to the alignment requirement of a
     particular type, end the format with the code for that type with a
     repeat count of zero.  See *note 範例: 228b.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc1700


File: python.info,  Node: Format Characters,  Next: 範例<2>,  Prev: Byte Order Size and Alignment,  Up: Format Strings

5.7.1.4 Format Characters
.........................

Format characters have the following meaning; the conversion between C
and Python values should be obvious given their types.  The 'Standard
size' column refers to the size of the packed value in bytes when using
standard size; that is, when the format string starts with one of ‘'<'’,
‘'>'’, ‘'!'’ or ‘'='’.  When using native size, the size of the packed
value is platform-dependent.

Format       C Type                         Python type              Standard size        註解
                                                                                          
-----------------------------------------------------------------------------------------------------------
                                                                                          
‘x’          pad byte                       no value                                      (7)
                                                                                          
                                                                                          
‘c’          char                           bytes of length 1        1
                                                                     
                                                                                          
‘b’          signed char                    integer                  1                    (1), (2)
                                                                                          
                                                                                          
‘B’          unsigned char                  integer                  1                    (2)
                                                                                          
                                                                                          
‘?’          _Bool                          bool                     1                    (1)
                                                                                          
                                                                                          
‘h’          short                          integer                  2                    (2)
                                                                                          
                                                                                          
‘H’          unsigned short                 integer                  2                    (2)
                                                                                          
                                                                                          
‘i’          int                            integer                  4                    (2)
                                                                                          
                                                                                          
‘I’          unsigned int                   integer                  4                    (2)
                                                                                          
                                                                                          
‘l’          long                           integer                  4                    (2)
                                                                                          
                                                                                          
‘L’          unsigned long                  integer                  4                    (2)
                                                                                          
                                                                                          
‘q’          long long                      integer                  8                    (2)
                                                                                          
                                                                                          
‘Q’          unsigned long long             integer                  8                    (2)
                                                                                          
                                                                                          
‘n’          ‘ssize_t’                      integer                                       (3)
                                                                                          
                                                                                          
‘N’          ‘size_t’                       integer                                       (3)
                                                                                          
                                                                                          
‘e’          (6)                            float                    2                    (4)
                                                                                          
                                                                                          
‘f’          float                          float                    4                    (4)
                                                                                          
                                                                                          
‘d’          double                         float                    8                    (4)
                                                                                          
                                                                                          
‘s’          char[]                         bytes                                         (9)
                                                                                          
                                                                                          
‘p’          char[]                         bytes                                         (8)
                                                                                          
                                                                                          
‘P’          void*                          integer                                       (5)
                                                                                          

在 3.3 版的變更: 新增 ‘'n'’ 與 ‘'N'’ 格式的支援。

在 3.6 版的變更: 新增 ‘'e'’ 格式的支援。

註解：

  1. 
     The ‘'?'’ conversion code corresponds to the _Bool type defined by
     C standards since C99.  In standard mode, it is represented by one
     byte.

  2. When attempting to pack a non-integer using any of the integer
     conversion codes, if the non-integer has a *note __index__(): 6c1.
     method then that method is called to convert the argument to an
     integer before packing.

     在 3.2 版的變更: Added use of the *note __index__(): 6c1. method
     for non-integers.

  3. The ‘'n'’ and ‘'N'’ conversion codes are only available for the
     native size (selected as the default or with the ‘'@'’ byte order
     character).  For the standard size, you can use whichever of the
     other integer formats fits your application.

  4. For the ‘'f'’, ‘'d'’ and ‘'e'’ conversion codes, the packed
     representation uses the IEEE 754 binary32, binary64 or binary16
     format (for ‘'f'’, ‘'d'’ or ‘'e'’ respectively), regardless of the
     floating-point format used by the platform.

  5. The ‘'P'’ format character is only available for the native byte
     ordering (selected as the default or with the ‘'@'’ byte order
     character).  The byte order character ‘'='’ chooses to use little-
     or big-endian ordering based on the host system.  The struct module
     does not interpret this as native ordering, so the ‘'P'’ format is
     not available.

  6. The IEEE 754 binary16 "half precision" type was introduced in the
     2008 revision of the IEEE 754 standard(1).  It has a sign bit, a
     5-bit exponent and 11-bit precision (with 10 bits explicitly
     stored), and can represent numbers between approximately ‘6.1e-05’
     and ‘6.5e+04’ at full precision.  This type is not widely supported
     by C compilers: on a typical machine, an unsigned short can be used
     for storage, but not for math operations.  See the Wikipedia page
     on the half-precision floating-point format(2) for more
     information.

  7. When packing, ‘'x'’ inserts one NUL byte.

  8. The ‘'p'’ format character encodes a "Pascal string", meaning a
     short variable-length string stored in a 'fixed number of bytes',
     given by the count.  The first byte stored is the length of the
     string, or 255, whichever is smaller.  The bytes of the string
     follow.  If the string passed in to *note pack(): 120f. is too long
     (longer than the count minus 1), only the leading ‘count-1’ bytes
     of the string are stored.  If the string is shorter than ‘count-1’,
     it is padded with null bytes so that exactly count bytes in all are
     used.  Note that for *note unpack(): 16cb, the ‘'p'’ format
     character consumes ‘count’ bytes, but that the string returned can
     never contain more than 255 bytes.

  9. For the ‘'s'’ format character, the count is interpreted as the
     length of the bytes, not a repeat count like for the other format
     characters; for example, ‘'10s'’ means a single 10-byte string
     mapping to or from a single Python byte string, while ‘'10c'’ means
     10 separate one byte character elements (e.g., ‘cccccccccc’)
     mapping to or from ten different Python byte objects.  (See *note
     範例: 228b. for a concrete demonstration of the difference.)  If a
     count is not given, it defaults to 1.  For packing, the string is
     truncated or padded with null bytes as appropriate to make it fit.
     For unpacking, the resulting bytes object always has exactly the
     specified number of bytes.  As a special case, ‘'0s'’ means a
     single, empty string (while ‘'0c'’ means 0 characters).

A format character may be preceded by an integral repeat count.  For
example, the format string ‘'4h'’ means exactly the same as ‘'hhhh'’.

Whitespace characters between formats are ignored; a count and its
format must not contain whitespace though.

When packing a value ‘x’ using one of the integer formats (‘'b'’, ‘'B'’,
‘'h'’, ‘'H'’, ‘'i'’, ‘'I'’, ‘'l'’, ‘'L'’, ‘'q'’, ‘'Q'’), if ‘x’ is
outside the valid range for that format then *note struct.error: 12b7.
is raised.

在 3.1 版的變更: Previously, some of the integer formats wrapped
out-of-range values and raised *note DeprecationWarning: 18b. instead of
*note struct.error: 12b7.

For the ‘'?'’ format character, the return value is either *note True:
bb4. or *note False: adb.  When packing, the truth value of the argument
object is used.  Either 0 or 1 in the native or standard bool
representation will be packed, and any non-zero value will be ‘True’
when unpacking.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/IEEE_754-2008_revision

   (2) 
https://en.wikipedia.org/wiki/Half-precision_floating-point_format


File: python.info,  Node: 範例<2>,  Prev: Format Characters,  Up: Format Strings

5.7.1.5 範例
............

     備註: Native byte order examples (designated by the ‘'@'’ format
     prefix or lack of any prefix character) may not match what the
     reader's machine produces as that depends on the platform and
     compiler.

Pack and unpack integers of three different sizes, using big endian
ordering:

     >>> from struct import *
     >>> pack(">bhl", 1, 2, 3)
     b'\x01\x00\x02\x00\x00\x00\x03'
     >>> unpack('>bhl', b'\x01\x00\x02\x00\x00\x00\x03')
     (1, 2, 3)
     >>> calcsize('>bhl')
     7

Attempt to pack an integer which is too large for the defined field:

     >>> pack(">h", 99999)
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     struct.error: 'h' format requires -32768 <= number <= 32767

Demonstrate the difference between ‘'s'’ and ‘'c'’ format characters:

     >>> pack("@ccc", b'1', b'2', b'3')
     b'123'
     >>> pack("@3s", b'123')
     b'123'

Unpacked fields can be named by assigning them to variables or by
wrapping the result in a named tuple:

     >>> record = b'raymond   \x32\x12\x08\x01\x08'
     >>> name, serialnum, school, gradelevel = unpack('<10sHHb', record)

     >>> from collections import namedtuple
     >>> Student = namedtuple('Student', 'name serialnum school gradelevel')
     >>> Student._make(unpack('<10sHHb', record))
     Student(name=b'raymond   ', serialnum=4658, school=264, gradelevel=8)

The ordering of format characters may have an impact on size in native
mode since padding is implicit.  In standard mode, the user is
responsible for inserting any desired padding.  Note in the first ‘pack’
call below that three NUL bytes were added after the packed ‘'#'’ to
align the following integer on a four-byte boundary.  In this example,
the output was produced on a little endian machine:

     >>> pack('@ci', b'#', 0x12131415)
     b'#\x00\x00\x00\x15\x14\x13\x12'
     >>> pack('@ic', 0x12131415, b'#')
     b'\x15\x14\x13\x12#'
     >>> calcsize('@ci')
     8
     >>> calcsize('@ic')
     5

The following format ‘'llh0l'’ results in two pad bytes being added at
the end, assuming the platform's longs are aligned on 4-byte boundaries:

     >>> pack('@llh0l', 1, 2, 3)
     b'\x00\x00\x00\x01\x00\x00\x00\x02\x00\x03\x00\x00'

也參考
......

*note array: 6. 模組

     Packed binary storage of homogeneous data.

*note json: 76. 模組

     JSON encoder and decoder.

*note pickle: 95. 模組

     Python object serialization.


File: python.info,  Node: Applications,  Next: Classes<2>,  Prev: Format Strings,  Up: struct --- 將位元組直譯為打包起來的二進位資料

5.7.1.6 Applications
....................

Two main applications for the *note struct: c0. module exist, data
interchange between Python and C code within an application or another
application compiled using the same compiler (*note native formats:
2290.), and data interchange between applications using agreed upon data
layout (*note standard formats: 2291.).  Generally speaking, the format
strings constructed for these two domains are distinct.

* Menu:

* Native Formats::
* Standard Formats::


File: python.info,  Node: Native Formats,  Next: Standard Formats,  Up: Applications

5.7.1.7 Native Formats
......................

When constructing format strings which mimic native layouts, the
compiler and machine architecture determine byte ordering and padding.
In such cases, the ‘@’ format character should be used to specify native
byte ordering and data sizes.  Internal pad bytes are normally inserted
automatically.  It is possible that a zero-repeat format code will be
needed at the end of a format string to round up to the correct byte
boundary for proper alignment of consecutive chunks of data.

Consider these two simple examples (on a 64-bit, little-endian machine):

     >>> calcsize('@lhl')
     24
     >>> calcsize('@llh')
     18

Data is not padded to an 8-byte boundary at the end of the second format
string without the use of extra padding.  A zero-repeat format code
solves that problem:

     >>> calcsize('@llh0l')
     24

The ‘'x'’ format code can be used to specify the repeat, but for native
formats it is better to use a zero-repeat format like ‘'0l'’.

By default, native byte ordering and alignment is used, but it is better
to be explicit and use the ‘'@'’ prefix character.


File: python.info,  Node: Standard Formats,  Prev: Native Formats,  Up: Applications

5.7.1.8 Standard Formats
........................

When exchanging data beyond your process such as networking or storage,
be precise.  Specify the exact byte order, size, and alignment.  Do not
assume they match the native order of a particular machine.  For
example, network byte order is big-endian, while many popular CPUs are
little-endian.  By defining this explicitly, the user need not care
about the specifics of the platform their code is running on.  The first
character should typically be ‘<’ or ‘>’ (or ‘!’).  Padding is the
responsibility of the programmer.  The zero-repeat format character
won't work.  Instead, the user must explicitly add ‘'x'’ pad bytes where
needed.  Revisiting the examples from the previous section, we have:

     >>> calcsize('<qh6xq')
     24
     >>> pack('<qh6xq', 1, 2, 3) == pack('@lhl', 1, 2, 3)
     True
     >>> calcsize('@llh')
     18
     >>> pack('@llh', 1, 2, 3) == pack('<qqh', 1, 2, 3)
     True
     >>> calcsize('<qqh6x')
     24
     >>> calcsize('@llh0l')
     24
     >>> pack('@llh0l', 1, 2, 3) == pack('<qqh6x', 1, 2, 3)
     True

The above results (executed on a 64-bit machine) aren't guaranteed to
match when executed on different machines.  For example, the examples
below were executed on a 32-bit machine:

     >>> calcsize('<qqh6x')
     24
     >>> calcsize('@llh0l')
     12
     >>> pack('@llh0l', 1, 2, 3) == pack('<qqh6x', 1, 2, 3)
     False


File: python.info,  Node: Classes<2>,  Prev: Applications,  Up: struct --- 將位元組直譯為打包起來的二進位資料

5.7.1.9 Classes
...............

The *note struct: c0. module also defines the following type:

 -- 類別: struct.Struct (format)

     Return a new Struct object which writes and reads binary data
     according to the format string 'format'.  Creating a ‘Struct’
     object once and calling its methods is more efficient than calling
     module-level functions with the same format since the format string
     is only compiled once.

          備註: The compiled versions of the most recent format strings
          passed to the module-level functions are cached, so programs
          that use only a few format strings needn't worry about reusing
          a single *note Struct: 15a9. instance.

     Compiled Struct objects support the following methods and
     attributes:

      -- 方法: pack (v1, v2, ...)

          Identical to the *note pack(): 120f. function, using the
          compiled format.  (‘len(result)’ will equal *note size: 2297.)

      -- 方法: pack_into (buffer, offset, v1, v2, ...)

          Identical to the *note pack_into(): 2286. function, using the
          compiled format.

      -- 方法: unpack (buffer)

          Identical to the *note unpack(): 16cb. function, using the
          compiled format.  The buffer's size in bytes must equal *note
          size: 2297.

      -- 方法: unpack_from (buffer, offset=0)

          Identical to the *note unpack_from(): 2287. function, using
          the compiled format.  The buffer's size in bytes, starting at
          position 'offset', must be at least *note size: 2297.

      -- 方法: iter_unpack (buffer)

          Identical to the *note iter_unpack(): f61. function, using the
          compiled format.  The buffer's size in bytes must be a
          multiple of *note size: 2297.

          在 3.4 版被加入.

      -- 屬性: format

          The format string used to construct this Struct object.

          在 3.7 版的變更: The format string type is now *note str: 3f2.
          instead of *note bytes: 1a5.

      -- 屬性: size

          The calculated size of the struct (and hence of the bytes
          object produced by the *note pack(): 120f. method)
          corresponding to *note format: 5c3.

     在 3.13 版的變更: The 'repr()' of structs has changed.  It is now:

          >>> Struct('i')
          Struct('i')


File: python.info,  Node: codecs --- 編解碼器註冊表和基底類別,  Prev: struct --- 將位元組直譯為打包起來的二進位資料,  Up: 二進位資料服務

5.7.2 ‘codecs’ -- 編解碼器註冊表和基底類別
------------------------------------------

'原始碼：'Lib/codecs.py(1)

__________________________________________________________________

This module defines base classes for standard Python codecs (encoders
and decoders) and provides access to the internal Python codec registry,
which manages the codec and error handling lookup process.  Most
standard codecs are *note text encodings: 2054, which encode text to
bytes (and decode bytes to text), but there are also codecs provided
that encode text to text, and bytes to bytes.  Custom codecs may encode
and decode between arbitrary types, but some module features are
restricted to be used specifically with *note text encodings: 2054. or
with codecs that encode to *note bytes: 1a5.

The module defines the following functions for encoding and decoding
with any codec:

 -- 函式: codecs.encode (obj, encoding='utf-8', errors='strict')

     Encodes 'obj' using the codec registered for 'encoding'.

     'Errors' may be given to set the desired error handling scheme.
     The default error handler is ‘'strict'’ meaning that encoding
     errors raise *note ValueError: 1e7. (or a more codec specific
     subclass, such as *note UnicodeEncodeError: 61d.).  Refer to *note
     Codec Base Classes: 229d. for more information on codec error
     handling.

 -- 函式: codecs.decode (obj, encoding='utf-8', errors='strict')

     Decodes 'obj' using the codec registered for 'encoding'.

     'Errors' may be given to set the desired error handling scheme.
     The default error handler is ‘'strict'’ meaning that decoding
     errors raise *note ValueError: 1e7. (or a more codec specific
     subclass, such as *note UnicodeDecodeError: 9b7.).  Refer to *note
     Codec Base Classes: 229d. for more information on codec error
     handling.

The full details for each codec can also be looked up directly:

 -- 函式: codecs.lookup (encoding)

     Looks up the codec info in the Python codec registry and returns a
     *note CodecInfo: 15f6. object as defined below.

     Encodings are first looked up in the registry's cache.  If not
     found, the list of registered search functions is scanned.  If no
     *note CodecInfo: 15f6. object is found, a *note LookupError: 20a9.
     is raised.  Otherwise, the *note CodecInfo: 15f6. object is stored
     in the cache and returned to the caller.

 -- 類別: codecs.CodecInfo (encode, decode, streamreader=None,
          streamwriter=None, incrementalencoder=None,
          incrementaldecoder=None, name=None)

     Codec details when looking up the codec registry.  The constructor
     arguments are stored in attributes of the same name:

      -- 屬性: name

          The name of the encoding.

      -- 屬性: encode
      -- 屬性: decode

          The stateless encoding and decoding functions.  These must be
          functions or methods which have the same interface as the
          *note encode(): 22a1. and *note decode(): 22a2. methods of
          Codec instances (see *note Codec Interface: 22a3.).  The
          functions or methods are expected to work in a stateless mode.

      -- 屬性: incrementalencoder
      -- 屬性: incrementaldecoder

          Incremental encoder and decoder classes or factory functions.
          These have to provide the interface defined by the base
          classes *note IncrementalEncoder: 22a6. and *note
          IncrementalDecoder: 22a7, respectively.  Incremental codecs
          can maintain state.

      -- 屬性: streamwriter
      -- 屬性: streamreader

          Stream writer and reader classes or factory functions.  These
          have to provide the interface defined by the base classes
          *note StreamWriter: 22aa. and *note StreamReader: 22ab,
          respectively.  Stream codecs can maintain state.

To simplify access to the various codec components, the module provides
these additional functions which use *note lookup(): 907. for the codec
lookup:

 -- 函式: codecs.getencoder (encoding)

     Look up the codec for the given encoding and return its encoder
     function.

     Raises a *note LookupError: 20a9. in case the encoding cannot be
     found.

 -- 函式: codecs.getdecoder (encoding)

     Look up the codec for the given encoding and return its decoder
     function.

     Raises a *note LookupError: 20a9. in case the encoding cannot be
     found.

 -- 函式: codecs.getincrementalencoder (encoding)

     Look up the codec for the given encoding and return its incremental
     encoder class or factory function.

     Raises a *note LookupError: 20a9. in case the encoding cannot be
     found or the codec doesn't support an incremental encoder.

 -- 函式: codecs.getincrementaldecoder (encoding)

     Look up the codec for the given encoding and return its incremental
     decoder class or factory function.

     Raises a *note LookupError: 20a9. in case the encoding cannot be
     found or the codec doesn't support an incremental decoder.

 -- 函式: codecs.getreader (encoding)

     Look up the codec for the given encoding and return its *note
     StreamReader: 22ab. class or factory function.

     Raises a *note LookupError: 20a9. in case the encoding cannot be
     found.

 -- 函式: codecs.getwriter (encoding)

     Look up the codec for the given encoding and return its *note
     StreamWriter: 22aa. class or factory function.

     Raises a *note LookupError: 20a9. in case the encoding cannot be
     found.

Custom codecs are made available by registering a suitable codec search
function:

 -- 函式: codecs.register (search_function)

     Register a codec search function.  Search functions are expected to
     take one argument, being the encoding name in all lower case
     letters with hyphens and spaces converted to underscores, and
     return a *note CodecInfo: 15f6. object.  In case a search function
     cannot find a given encoding, it should return ‘None’.

     在 3.9 版的變更: Hyphens and spaces are converted to underscore.

 -- 函式: codecs.unregister (search_function)

     Unregister a codec search function and clear the registry's cache.
     If the search function is not registered, do nothing.

     在 3.10 版被加入.

While the builtin *note open(): 4c0. and the associated *note io: 73.
module are the recommended approach for working with encoded text files,
this module provides additional utility functions and classes that allow
the use of a wider range of codecs when working with binary files:

 -- 函式: codecs.open (filename, mode='r', encoding=None,
          errors='strict', buffering=-1)

     Open an encoded file using the given 'mode' and return an instance
     of *note StreamReaderWriter: 22b3, providing transparent
     encoding/decoding.  The default file mode is ‘'r'’, meaning to open
     the file in read mode.

          備註: If 'encoding' is not ‘None’, then the underlying encoded
          files are always opened in binary mode.  No automatic
          conversion of ‘'\n'’ is done on reading and writing.  The
          'mode' argument may be any binary mode acceptable to the
          built-in *note open(): 4c0. function; the ‘'b'’ is
          automatically added.

     'encoding' specifies the encoding which is to be used for the file.
     Any encoding that encodes to and decodes from bytes is allowed, and
     the data types supported by the file methods depend on the codec
     used.

     'errors' may be given to define the error handling.  It defaults to
     ‘'strict'’ which causes a *note ValueError: 1e7. to be raised in
     case an encoding error occurs.

     'buffering' has the same meaning as for the built-in *note open():
     4c0. function.  It defaults to -1 which means that the default
     buffer size will be used.

     在 3.11 版的變更: The ‘'U'’ mode has been removed.

 -- 函式: codecs.EncodedFile (file, data_encoding, file_encoding=None,
          errors='strict')

     Return a *note StreamRecoder: 18f6. instance, a wrapped version of
     'file' which provides transparent transcoding.  The original file
     is closed when the wrapped version is closed.

     Data written to the wrapped file is decoded according to the given
     'data_encoding' and then written to the original file as bytes
     using 'file_encoding'.  Bytes read from the original file are
     decoded according to 'file_encoding', and the result is encoded
     using 'data_encoding'.

     If 'file_encoding' is not given, it defaults to 'data_encoding'.

     'errors' may be given to define the error handling.  It defaults to
     ‘'strict'’, which causes *note ValueError: 1e7. to be raised in
     case an encoding error occurs.

 -- 函式: codecs.iterencode (iterator, encoding, errors='strict',
          **kwargs)

     Uses an incremental encoder to iteratively encode the input
     provided by 'iterator'.  This function is a *note generator: 1004.
     The 'errors' argument (as well as any other keyword argument) is
     passed through to the incremental encoder.

     This function requires that the codec accept text *note str: 3f2.
     objects to encode.  Therefore it does not support bytes-to-bytes
     encoders such as ‘base64_codec’.

 -- 函式: codecs.iterdecode (iterator, encoding, errors='strict',
          **kwargs)

     Uses an incremental decoder to iteratively decode the input
     provided by 'iterator'.  This function is a *note generator: 1004.
     The 'errors' argument (as well as any other keyword argument) is
     passed through to the incremental decoder.

     This function requires that the codec accept *note bytes: 1a5.
     objects to decode.  Therefore it does not support text-to-text
     encoders such as ‘rot_13’, although ‘rot_13’ may be used
     equivalently with *note iterencode(): 22b5.

The module also provides the following constants which are useful for
reading and writing to platform dependent files:

 -- 資料: codecs.BOM
 -- 資料: codecs.BOM_BE
 -- 資料: codecs.BOM_LE
 -- 資料: codecs.BOM_UTF8
 -- 資料: codecs.BOM_UTF16
 -- 資料: codecs.BOM_UTF16_BE
 -- 資料: codecs.BOM_UTF16_LE
 -- 資料: codecs.BOM_UTF32
 -- 資料: codecs.BOM_UTF32_BE
 -- 資料: codecs.BOM_UTF32_LE

     These constants define various byte sequences, being Unicode byte
     order marks (BOMs) for several encodings.  They are used in UTF-16
     and UTF-32 data streams to indicate the byte order used, and in
     UTF-8 as a Unicode signature.  *note BOM_UTF16: 22bb. is either
     *note BOM_UTF16_BE: 22bc. or *note BOM_UTF16_LE: 22bd. depending on
     the platform's native byte order, *note BOM: 22b7. is an alias for
     *note BOM_UTF16: 22bb, *note BOM_LE: 22b9. for *note BOM_UTF16_LE:
     22bd. and *note BOM_BE: 22b8. for *note BOM_UTF16_BE: 22bc.  The
     others represent the BOM in UTF-8 and UTF-32 encodings.

* Menu:

* Codec Base Classes::
* Encodings and Unicode::
* Standard Encodings::
* Python Specific Encodings::
* encodings.idna: encodings idna --- Internationalized Domain Names in Applications. Internationalized Domain Names in Applications
* encodings.mbcs: encodings mbcs --- Windows ANSI codepage. Windows ANSI codepage
* encodings.utf_8_sig: encodings utf_8_sig --- UTF-8 codec with BOM signature. UTF-8 codec with BOM signature

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/codecs.py


File: python.info,  Node: Codec Base Classes,  Next: Encodings and Unicode,  Up: codecs --- 編解碼器註冊表和基底類別

5.7.2.1 Codec Base Classes
..........................

The *note codecs: 14. module defines a set of base classes which define
the interfaces for working with codec objects, and can also be used as
the basis for custom codec implementations.

Each codec has to define four interfaces to make it usable as codec in
Python: stateless encoder, stateless decoder, stream reader and stream
writer.  The stream reader and writers typically reuse the stateless
encoder/decoder to implement the file protocols.  Codec authors also
need to define how the codec will handle encoding and decoding errors.
* Menu:

* Error Handlers::
* Stateless Encoding and Decoding::
* Incremental Encoding and Decoding::
* Stream Encoding and Decoding::


File: python.info,  Node: Error Handlers,  Next: Stateless Encoding and Decoding,  Up: Codec Base Classes

5.7.2.2 Error Handlers
......................

To simplify and standardize error handling, codecs may implement
different error handling schemes by accepting the 'errors' string
argument:

     >>> 'German ß, ♬'.encode(encoding='ascii', errors='backslashreplace')
     b'German \\xdf, \\u266c'
     >>> 'German ß, ♬'.encode(encoding='ascii', errors='xmlcharrefreplace')
     b'German &#223;, &#9836;'

The following error handlers can be used with all Python *note Standard
Encodings: d5f. codecs:

Value                         含義
                              
----------------------------------------------------------------------------------
                              
‘'strict'’                    Raise *note UnicodeError: 123a. (or a subclass),
                              this is the default.  Implemented in
                              *note strict_errors(): 22c4.
                              
                              
‘'ignore'’                    Ignore the malformed data and continue without
                              further notice.  Implemented in
                              *note ignore_errors(): 22c5.
                              
                              
‘'replace'’                   Replace with a replacement marker.  On encoding,
                              use ‘?’ (ASCII character).  On decoding, use ‘�’
                              (U+FFFD, the official REPLACEMENT CHARACTER).
                              Implemented in *note replace_errors(): 22c6.
                              
                              
‘'backslashreplace'’          Replace with backslashed escape sequences.  On
                              encoding, use hexadecimal form of Unicode code
                              point with formats ‘\xHH’ ‘\uXXXX’ ‘\UXXXXXXXX’.
                              On decoding, use hexadecimal form of byte value
                              with format ‘\xHH’.  Implemented in
                              *note backslashreplace_errors(): 22c7.
                              
                              
‘'surrogateescape'’           On decoding, replace byte with individual
                              surrogate code ranging from ‘U+DC80’ to ‘U+DCFF’.
                              This code will then be turned back into the same
                              byte when the ‘'surrogateescape'’ error handler
                              is used when encoding the data.  (See PEP 383(1)
                              for more.)
                              

The following error handlers are only applicable to encoding (within
*note text encodings: 2054.):

Value                         含義
                              
----------------------------------------------------------------------------------
                              
‘'xmlcharrefreplace'’         Replace with XML/HTML numeric character
                              reference, which is a decimal form of Unicode
                              code point with format ‘&#NUM;’.  Implemented in
                              *note xmlcharrefreplace_errors(): 22c8.
                              
                              
‘'namereplace'’               Replace with ‘\N{...}’ escape sequences, what
                              appears in the braces is the Name property from
                              Unicode Character Database.  Implemented in
                              *note namereplace_errors(): 22c9.
                              

In addition, the following error handler is specific to the given
codecs:

Value                   Codecs                       含義
                                                     
-----------------------------------------------------------------------------------------------------
                                                     
‘'surrogatepass'’       utf-8, utf-16, utf-32,       Allow encoding and decoding surrogate code
                        utf-16-be, utf-16-le,        point (‘U+D800’ - ‘U+DFFF’) as normal code
                        utf-32-be, utf-32-le         point.  Otherwise these codecs treat the
                                                     presence of surrogate code point in
                                                     *note str: 3f2. as an error.
                                                     

在 3.1 版被加入: The ‘'surrogateescape'’ and ‘'surrogatepass'’ error
handlers.

在 3.4 版的變更: The ‘'surrogatepass'’ error handler now works with
utf-16* and utf-32* codecs.

在 3.5 版被加入: The ‘'namereplace'’ error handler.

在 3.5 版的變更: The ‘'backslashreplace'’ error handler now works with
decoding and translating.

The set of allowed values can be extended by registering a new named
error handler:

 -- 函式: codecs.register_error (name, error_handler)

     Register the error handling function 'error_handler' under the name
     'name'.  The 'error_handler' argument will be called during
     encoding and decoding in case of an error, when 'name' is specified
     as the errors parameter.

     For encoding, 'error_handler' will be called with a *note
     UnicodeEncodeError: 61d. instance, which contains information about
     the location of the error.  The error handler must either raise
     this or a different exception, or return a tuple with a replacement
     for the unencodable part of the input and a position where encoding
     should continue.  The replacement may be either *note str: 3f2. or
     *note bytes: 1a5.  If the replacement is bytes, the encoder will
     simply copy them into the output buffer.  If the replacement is a
     string, the encoder will encode the replacement.  Encoding
     continues on original input at the specified position.  Negative
     position values will be treated as being relative to the end of the
     input string.  If the resulting position is out of bound an *note
     IndexError: 14a3. will be raised.

     Decoding and translating works similarly, except *note
     UnicodeDecodeError: 9b7. or *note UnicodeTranslateError: 217b. will
     be passed to the handler and that the replacement from the error
     handler will be put into the output directly.

Previously registered error handlers (including the standard error
handlers) can be looked up by name:

 -- 函式: codecs.lookup_error (name)

     Return the error handler previously registered under the name
     'name'.

     Raises a *note LookupError: 20a9. in case the handler cannot be
     found.

The following standard error handlers are also made available as module
level functions:

 -- 函式: codecs.strict_errors (exception)

     Implements the ‘'strict'’ error handling.

     Each encoding or decoding error raises a *note UnicodeError: 123a.

 -- 函式: codecs.ignore_errors (exception)

     Implements the ‘'ignore'’ error handling.

     Malformed data is ignored; encoding or decoding is continued
     without further notice.

 -- 函式: codecs.replace_errors (exception)

     Implements the ‘'replace'’ error handling.

     Substitutes ‘?’ (ASCII character) for encoding errors or ‘�’
     (U+FFFD, the official REPLACEMENT CHARACTER) for decoding errors.

 -- 函式: codecs.backslashreplace_errors (exception)

     Implements the ‘'backslashreplace'’ error handling.

     Malformed data is replaced by a backslashed escape sequence.  On
     encoding, use the hexadecimal form of Unicode code point with
     formats ‘\xHH’ ‘\uXXXX’ ‘\UXXXXXXXX’.  On decoding, use the
     hexadecimal form of byte value with format ‘\xHH’.

     在 3.5 版的變更: Works with decoding and translating.

 -- 函式: codecs.xmlcharrefreplace_errors (exception)

     Implements the ‘'xmlcharrefreplace'’ error handling (for encoding
     within *note text encoding: 2054. only).

     The unencodable character is replaced by an appropriate XML/HTML
     numeric character reference, which is a decimal form of Unicode
     code point with format ‘&#NUM;’ .

 -- 函式: codecs.namereplace_errors (exception)

     Implements the ‘'namereplace'’ error handling (for encoding within
     *note text encoding: 2054. only).

     The unencodable character is replaced by a ‘\N{...}’ escape
     sequence.  The set of characters that appear in the braces is the
     Name property from Unicode Character Database.  For example, the
     German lowercase letter ‘'ß'’ will be converted to byte sequence
     ‘\N{LATIN SMALL LETTER SHARP S}’ .

     在 3.5 版被加入.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0383/


File: python.info,  Node: Stateless Encoding and Decoding,  Next: Incremental Encoding and Decoding,  Prev: Error Handlers,  Up: Codec Base Classes

5.7.2.3 Stateless Encoding and Decoding
.......................................

The base *note Codec: 22cb. class defines these methods which also
define the function interfaces of the stateless encoder and decoder:

 -- 類別: codecs.Codec

      -- 方法: encode (input, errors='strict')

          Encodes the object 'input' and returns a tuple (output object,
          length consumed).  For instance, *note text encoding: 2054.
          converts a string object to a bytes object using a particular
          character set encoding (e.g., ‘cp1252’ or ‘iso-8859-1’).

          The 'errors' argument defines the error handling to apply.  It
          defaults to ‘'strict'’ handling.

          The method may not store state in the *note Codec: 22cb.
          instance.  Use *note StreamWriter: 22aa. for codecs which have
          to keep state in order to make encoding efficient.

          The encoder must be able to handle zero length input and
          return an empty object of the output object type in this
          situation.

      -- 方法: decode (input, errors='strict')

          Decodes the object 'input' and returns a tuple (output object,
          length consumed).  For instance, for a *note text encoding:
          2054, decoding converts a bytes object encoded using a
          particular character set encoding to a string object.

          For text encodings and bytes-to-bytes codecs, 'input' must be
          a bytes object or one which provides the read-only buffer
          interface - for example, buffer objects and memory mapped
          files.

          The 'errors' argument defines the error handling to apply.  It
          defaults to ‘'strict'’ handling.

          The method may not store state in the *note Codec: 22cb.
          instance.  Use *note StreamReader: 22ab. for codecs which have
          to keep state in order to make decoding efficient.

          The decoder must be able to handle zero length input and
          return an empty object of the output object type in this
          situation.


File: python.info,  Node: Incremental Encoding and Decoding,  Next: Stream Encoding and Decoding,  Prev: Stateless Encoding and Decoding,  Up: Codec Base Classes

5.7.2.4 Incremental Encoding and Decoding
.........................................

The *note IncrementalEncoder: 22a6. and *note IncrementalDecoder: 22a7.
classes provide the basic interface for incremental encoding and
decoding.  Encoding/decoding the input isn't done with one call to the
stateless encoder/decoder function, but with multiple calls to the *note
encode(): 22cd./*note decode(): 22ce. method of the incremental
encoder/decoder.  The incremental encoder/decoder keeps track of the
encoding/decoding process during method calls.

The joined output of calls to the *note encode(): 22cd./*note decode():
22ce. method is the same as if all the single inputs were joined into
one, and this input was encoded/decoded with the stateless
encoder/decoder.

* Menu:

* IncrementalEncoder 物件::
* IncrementalDecoder 物件::


File: python.info,  Node: IncrementalEncoder 物件,  Next: IncrementalDecoder 物件,  Up: Incremental Encoding and Decoding

5.7.2.5 IncrementalEncoder 物件
...............................

The *note IncrementalEncoder: 22a6. class is used for encoding an input
in multiple steps.  It defines the following methods which every
incremental encoder must define in order to be compatible with the
Python codec registry.

 -- 類別: codecs.IncrementalEncoder (errors='strict')

     Constructor for an *note IncrementalEncoder: 22a6. instance.

     All incremental encoders must provide this constructor interface.
     They are free to add additional keyword arguments, but only the
     ones defined here are used by the Python codec registry.

     The *note IncrementalEncoder: 22a6. may implement different error
     handling schemes by providing the 'errors' keyword argument.  See
     *note Error Handlers: 16eb. for possible values.

     The 'errors' argument will be assigned to an attribute of the same
     name.  Assigning to this attribute makes it possible to switch
     between different error handling strategies during the lifetime of
     the *note IncrementalEncoder: 22a6. object.

      -- 方法: encode (object, final=False)

          Encodes 'object' (taking the current state of the encoder into
          account) and returns the resulting encoded object.  If this is
          the last call to *note encode(): ea5. 'final' must be true
          (the default is false).

      -- 方法: reset ()

          Reset the encoder to the initial state.  The output is
          discarded: call ‘.encode(object, final=True)’, passing an
          empty byte or text string if necessary, to reset the encoder
          and to get the output.

      -- 方法: getstate ()

          Return the current state of the encoder which must be an
          integer.  The implementation should make sure that ‘0’ is the
          most common state.  (States that are more complicated than
          integers can be converted into an integer by
          marshaling/pickling the state and encoding the bytes of the
          resulting string into an integer.)

      -- 方法: setstate (state)

          Set the state of the encoder to 'state'.  'state' must be an
          encoder state returned by *note getstate(): 22d2.


File: python.info,  Node: IncrementalDecoder 物件,  Prev: IncrementalEncoder 物件,  Up: Incremental Encoding and Decoding

5.7.2.6 IncrementalDecoder 物件
...............................

The *note IncrementalDecoder: 22a7. class is used for decoding an input
in multiple steps.  It defines the following methods which every
incremental decoder must define in order to be compatible with the
Python codec registry.

 -- 類別: codecs.IncrementalDecoder (errors='strict')

     Constructor for an *note IncrementalDecoder: 22a7. instance.

     All incremental decoders must provide this constructor interface.
     They are free to add additional keyword arguments, but only the
     ones defined here are used by the Python codec registry.

     The *note IncrementalDecoder: 22a7. may implement different error
     handling schemes by providing the 'errors' keyword argument.  See
     *note Error Handlers: 16eb. for possible values.

     The 'errors' argument will be assigned to an attribute of the same
     name.  Assigning to this attribute makes it possible to switch
     between different error handling strategies during the lifetime of
     the *note IncrementalDecoder: 22a7. object.

      -- 方法: decode (object, final=False)

          Decodes 'object' (taking the current state of the decoder into
          account) and returns the resulting decoded object.  If this is
          the last call to *note decode(): ea6. 'final' must be true
          (the default is false).  If 'final' is true the decoder must
          decode the input completely and must flush all buffers.  If
          this isn't possible (e.g.  because of incomplete byte
          sequences at the end of the input) it must initiate error
          handling just like in the stateless case (which might raise an
          exception).

      -- 方法: reset ()

          Reset the decoder to the initial state.

      -- 方法: getstate ()

          Return the current state of the decoder.  This must be a tuple
          with two items, the first must be the buffer containing the
          still undecoded input.  The second must be an integer and can
          be additional state info.  (The implementation should make
          sure that ‘0’ is the most common additional state info.)  If
          this additional state info is ‘0’ it must be possible to set
          the decoder to the state which has no input buffered and ‘0’
          as the additional state info, so that feeding the previously
          buffered input to the decoder returns it to the previous state
          without producing any output.  (Additional state info that is
          more complicated than integers can be converted into an
          integer by marshaling/pickling the info and encoding the bytes
          of the resulting string into an integer.)

      -- 方法: setstate (state)

          Set the state of the decoder to 'state'.  'state' must be a
          decoder state returned by *note getstate(): 22d7.


File: python.info,  Node: Stream Encoding and Decoding,  Prev: Incremental Encoding and Decoding,  Up: Codec Base Classes

5.7.2.7 Stream Encoding and Decoding
....................................

The *note StreamWriter: 22aa. and *note StreamReader: 22ab. classes
provide generic working interfaces which can be used to implement new
encoding submodules very easily.  See ‘encodings.utf_8’ for an example
of how this is done.

* Menu:

* StreamWriter 物件::
* StreamReader 物件::
* StreamReaderWriter 物件::
* StreamRecoder 物件::


File: python.info,  Node: StreamWriter 物件,  Next: StreamReader 物件,  Up: Stream Encoding and Decoding

5.7.2.8 StreamWriter 物件
.........................

The *note StreamWriter: 22aa. class is a subclass of *note Codec: 22cb.
and defines the following methods which every stream writer must define
in order to be compatible with the Python codec registry.

 -- 類別: codecs.StreamWriter (stream, errors='strict')

     Constructor for a *note StreamWriter: 22aa. instance.

     All stream writers must provide this constructor interface.  They
     are free to add additional keyword arguments, but only the ones
     defined here are used by the Python codec registry.

     The 'stream' argument must be a file-like object open for writing
     text or binary data, as appropriate for the specific codec.

     The *note StreamWriter: 22aa. may implement different error
     handling schemes by providing the 'errors' keyword argument.  See
     *note Error Handlers: 16eb. for the standard error handlers the
     underlying stream codec may support.

     The 'errors' argument will be assigned to an attribute of the same
     name.  Assigning to this attribute makes it possible to switch
     between different error handling strategies during the lifetime of
     the *note StreamWriter: 22aa. object.

      -- 方法: write (object)

          Writes the object's contents encoded to the stream.

      -- 方法: writelines (list)

          Writes the concatenated iterable of strings to the stream
          (possibly by reusing the *note write(): 22dc. method).
          Infinite or very large iterables are not supported.  The
          standard bytes-to-bytes codecs do not support this method.

      -- 方法: reset ()

          Resets the codec buffers used for keeping internal state.

          Calling this method should ensure that the data on the output
          is put into a clean state that allows appending of new fresh
          data without having to rescan the whole stream to recover
          state.

In addition to the above methods, the *note StreamWriter: 22aa. must
also inherit all other methods and attributes from the underlying
stream.


File: python.info,  Node: StreamReader 物件,  Next: StreamReaderWriter 物件,  Prev: StreamWriter 物件,  Up: Stream Encoding and Decoding

5.7.2.9 StreamReader 物件
.........................

The *note StreamReader: 22ab. class is a subclass of *note Codec: 22cb.
and defines the following methods which every stream reader must define
in order to be compatible with the Python codec registry.

 -- 類別: codecs.StreamReader (stream, errors='strict')

     Constructor for a *note StreamReader: 22ab. instance.

     All stream readers must provide this constructor interface.  They
     are free to add additional keyword arguments, but only the ones
     defined here are used by the Python codec registry.

     The 'stream' argument must be a file-like object open for reading
     text or binary data, as appropriate for the specific codec.

     The *note StreamReader: 22ab. may implement different error
     handling schemes by providing the 'errors' keyword argument.  See
     *note Error Handlers: 16eb. for the standard error handlers the
     underlying stream codec may support.

     The 'errors' argument will be assigned to an attribute of the same
     name.  Assigning to this attribute makes it possible to switch
     between different error handling strategies during the lifetime of
     the *note StreamReader: 22ab. object.

     The set of allowed values for the 'errors' argument can be extended
     with *note register_error(): 1404.

      -- 方法: read (size=-1, chars=-1, firstline=False)

          Decodes data from the stream and returns the resulting object.

          The 'chars' argument indicates the number of decoded code
          points or bytes to return.  The *note read(): 22e1. method
          will never return more data than requested, but it might
          return less, if there is not enough available.

          The 'size' argument indicates the approximate maximum number
          of encoded bytes or code points to read for decoding.  The
          decoder can modify this setting as appropriate.  The default
          value -1 indicates to read and decode as much as possible.
          This parameter is intended to prevent having to decode huge
          files in one step.

          The 'firstline' flag indicates that it would be sufficient to
          only return the first line, if there are decoding errors on
          later lines.

          The method should use a greedy read strategy meaning that it
          should read as much data as is allowed within the definition
          of the encoding and the given size, e.g.  if optional encoding
          endings or state markers are available on the stream, these
          should be read too.

      -- 方法: readline (size=None, keepends=True)

          Read one line from the input stream and return the decoded
          data.

          'size', if given, is passed as size argument to the stream's
          *note read(): 22e1. method.

          If 'keepends' is false line-endings will be stripped from the
          lines returned.

      -- 方法: readlines (sizehint=None, keepends=True)

          Read all lines available on the input stream and return them
          as a list of lines.

          Line-endings are implemented using the codec's *note decode():
          ea6. method and are included in the list entries if 'keepends'
          is true.

          'sizehint', if given, is passed as the 'size' argument to the
          stream's *note read(): 22e1. method.

      -- 方法: reset ()

          Resets the codec buffers used for keeping internal state.

          Note that no stream repositioning should take place.  This
          method is primarily intended to be able to recover from
          decoding errors.

In addition to the above methods, the *note StreamReader: 22ab. must
also inherit all other methods and attributes from the underlying
stream.


File: python.info,  Node: StreamReaderWriter 物件,  Next: StreamRecoder 物件,  Prev: StreamReader 物件,  Up: Stream Encoding and Decoding

5.7.2.10 StreamReaderWriter 物件
................................

The *note StreamReaderWriter: 22b3. is a convenience class that allows
wrapping streams which work in both read and write modes.

The design is such that one can use the factory functions returned by
the *note lookup(): 907. function to construct the instance.

 -- 類別: codecs.StreamReaderWriter (stream, Reader, Writer,
          errors='strict')

     Creates a *note StreamReaderWriter: 22b3. instance.  'stream' must
     be a file-like object.  'Reader' and 'Writer' must be factory
     functions or classes providing the *note StreamReader: 22ab. and
     *note StreamWriter: 22aa. interface resp.  Error handling is done
     in the same way as defined for the stream readers and writers.

*note StreamReaderWriter: 22b3. instances define the combined interfaces
of *note StreamReader: 22ab. and *note StreamWriter: 22aa. classes.
They inherit all other methods and attributes from the underlying
stream.


File: python.info,  Node: StreamRecoder 物件,  Prev: StreamReaderWriter 物件,  Up: Stream Encoding and Decoding

5.7.2.11 StreamRecoder 物件
...........................

The *note StreamRecoder: 18f6. translates data from one encoding to
another, which is sometimes useful when dealing with different encoding
environments.

The design is such that one can use the factory functions returned by
the *note lookup(): 907. function to construct the instance.

 -- 類別: codecs.StreamRecoder (stream, encode, decode, Reader, Writer,
          errors='strict')

     Creates a *note StreamRecoder: 18f6. instance which implements a
     two-way conversion: 'encode' and 'decode' work on the frontend —
     the data visible to code calling *note read(): 22e1. and *note
     write(): 22dc, while 'Reader' and 'Writer' work on the backend —
     the data in 'stream'.

     You can use these objects to do transparent transcodings, e.g.,
     from Latin-1 to UTF-8 and back.

     The 'stream' argument must be a file-like object.

     The 'encode' and 'decode' arguments must adhere to the *note Codec:
     22cb. interface.  'Reader' and 'Writer' must be factory functions
     or classes providing objects of the *note StreamReader: 22ab. and
     *note StreamWriter: 22aa. interface respectively.

     Error handling is done in the same way as defined for the stream
     readers and writers.

*note StreamRecoder: 18f6. instances define the combined interfaces of
*note StreamReader: 22ab. and *note StreamWriter: 22aa. classes.  They
inherit all other methods and attributes from the underlying stream.


File: python.info,  Node: Encodings and Unicode,  Next: Standard Encodings,  Prev: Codec Base Classes,  Up: codecs --- 編解碼器註冊表和基底類別

5.7.2.12 Encodings and Unicode
..............................

Strings are stored internally as sequences of code points in range
‘U+0000’-‘U+10FFFF’.  (See PEP 393(1) for more details about the
implementation.)  Once a string object is used outside of CPU and
memory, endianness and how these arrays are stored as bytes become an
issue.  As with other codecs, serialising a string into a sequence of
bytes is known as 'encoding', and recreating the string from the
sequence of bytes is known as 'decoding'.  There are a variety of
different text serialisation codecs, which are collectivity referred to
as *note text encodings: 2054.

The simplest text encoding (called ‘'latin-1'’ or ‘'iso-8859-1'’) maps
the code points 0-255 to the bytes ‘0x0’-‘0xff’, which means that a
string object that contains code points above ‘U+00FF’ can't be encoded
with this codec.  Doing so will raise a *note UnicodeEncodeError: 61d.
that looks like the following (although the details of the error message
may differ): ‘UnicodeEncodeError: 'latin-1' codec can't encode character
'\u1234' in position 3: ordinal not in range(256)’.

There's another group of encodings (the so called charmap encodings)
that choose a different subset of all Unicode code points and how these
code points are mapped to the bytes ‘0x0’-‘0xff’.  To see how this is
done simply open e.g.  ‘encodings/cp1252.py’ (which is an encoding that
is used primarily on Windows).  There's a string constant with 256
characters that shows you which character is mapped to which byte value.

All of these encodings can only encode 256 of the 1114112 code points
defined in Unicode.  A simple and straightforward way that can store
each Unicode code point, is to store each code point as four consecutive
bytes.  There are two possibilities: store the bytes in big endian or in
little endian order.  These two encodings are called ‘UTF-32-BE’ and
‘UTF-32-LE’ respectively.  Their disadvantage is that if e.g.  you use
‘UTF-32-BE’ on a little endian machine you will always have to swap
bytes on encoding and decoding.  ‘UTF-32’ avoids this problem: bytes
will always be in natural endianness.  When these bytes are read by a
CPU with a different endianness, then bytes have to be swapped though.
To be able to detect the endianness of a ‘UTF-16’ or ‘UTF-32’ byte
sequence, there's the so called BOM ("Byte Order Mark").  This is the
Unicode character ‘U+FEFF’.  This character can be prepended to every
‘UTF-16’ or ‘UTF-32’ byte sequence.  The byte swapped version of this
character (‘0xFFFE’) is an illegal character that may not appear in a
Unicode text.  So when the first character in a ‘UTF-16’ or ‘UTF-32’
byte sequence appears to be a ‘U+FFFE’ the bytes have to be swapped on
decoding.  Unfortunately the character ‘U+FEFF’ had a second purpose as
a ‘ZERO WIDTH NO-BREAK SPACE’: a character that has no width and doesn't
allow a word to be split.  It can e.g.  be used to give hints to a
ligature algorithm.  With Unicode 4.0 using ‘U+FEFF’ as a ‘ZERO WIDTH
NO-BREAK SPACE’ has been deprecated (with ‘U+2060’ (‘WORD JOINER’)
assuming this role).  Nevertheless Unicode software still must be able
to handle ‘U+FEFF’ in both roles: as a BOM it's a device to determine
the storage layout of the encoded bytes, and vanishes once the byte
sequence has been decoded into a string; as a ‘ZERO WIDTH NO-BREAK
SPACE’ it's a normal character that will be decoded like any other.

There's another encoding that is able to encode the full range of
Unicode characters: UTF-8.  UTF-8 is an 8-bit encoding, which means
there are no issues with byte order in UTF-8.  Each byte in a UTF-8 byte
sequence consists of two parts: marker bits (the most significant bits)
and payload bits.  The marker bits are a sequence of zero to four ‘1’
bits followed by a ‘0’ bit.  Unicode characters are encoded like this
(with x being payload bits, which when concatenated give the Unicode
character):

Range                                   Encoding
                                        
-------------------------------------------------------------------------------------------
                                        
‘U-00000000’ ...  ‘U-0000007F’          0xxxxxxx
                                        
                                        
‘U-00000080’ ...  ‘U-000007FF’          110xxxxx 10xxxxxx
                                        
                                        
‘U-00000800’ ...  ‘U-0000FFFF’          1110xxxx 10xxxxxx 10xxxxxx
                                        
                                        
‘U-00010000’ ...  ‘U-0010FFFF’          11110xxx 10xxxxxx 10xxxxxx 10xxxxxx
                                        

The least significant bit of the Unicode character is the rightmost x
bit.

As UTF-8 is an 8-bit encoding no BOM is required and any ‘U+FEFF’
character in the decoded string (even if it's the first character) is
treated as a ‘ZERO WIDTH NO-BREAK SPACE’.

Without external information it's impossible to reliably determine which
encoding was used for encoding a string.  Each charmap encoding can
decode any random byte sequence.  However that's not possible with
UTF-8, as UTF-8 byte sequences have a structure that doesn't allow
arbitrary byte sequences.  To increase the reliability with which a
UTF-8 encoding can be detected, Microsoft invented a variant of UTF-8
(that Python calls ‘"utf-8-sig"’) for its Notepad program: Before any of
the Unicode characters is written to the file, a UTF-8 encoded BOM
(which looks like this as a byte sequence: ‘0xef’, ‘0xbb’, ‘0xbf’) is
written.  As it's rather improbable that any charmap encoded file starts
with these byte values (which would e.g.  map to

          LATIN SMALL LETTER I WITH DIAERESIS
          RIGHT-POINTING DOUBLE ANGLE QUOTATION MARK
          INVERTED QUESTION MARK

in iso-8859-1), this increases the probability that a ‘utf-8-sig’
encoding can be correctly guessed from the byte sequence.  So here the
BOM is not used to be able to determine the byte order used for
generating the byte sequence, but as a signature that helps in guessing
the encoding.  On encoding the utf-8-sig codec will write ‘0xef’,
‘0xbb’, ‘0xbf’ as the first three bytes to the file.  On decoding
‘utf-8-sig’ will skip those three bytes if they appear as the first
three bytes in the file.  In UTF-8, the use of the BOM is discouraged
and should generally be avoided.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0393/


File: python.info,  Node: Standard Encodings,  Next: Python Specific Encodings,  Prev: Encodings and Unicode,  Up: codecs --- 編解碼器註冊表和基底類別

5.7.2.13 Standard Encodings
...........................

Python comes with a number of codecs built-in, either implemented as C
functions or with dictionaries as mapping tables.  The following table
lists the codecs by name, together with a few common aliases, and the
languages for which the encoding is likely used.  Neither the list of
aliases nor the list of languages is meant to be exhaustive.  Notice
that spelling alternatives that only differ in case or use a hyphen
instead of an underscore are also valid aliases; therefore, e.g.
‘'utf-8'’ is a valid alias for the ‘'utf_8'’ codec.

'CPython 實作細節：' Some common encodings can bypass the codecs lookup
machinery to improve performance.  These optimization opportunities are
only recognized by CPython for a limited set of (case insensitive)
aliases: utf-8, utf8, latin-1, latin1, iso-8859-1, iso8859-1, mbcs
(Windows only), ascii, us-ascii, utf-16, utf16, utf-32, utf32, and the
same using underscores instead of dashes.  Using alternative aliases for
these encodings may result in slower execution.

在 3.6 版的變更: Optimization opportunity recognized for us-ascii.

Many of the character sets support the same languages.  They vary in
individual characters (e.g.  whether the EURO SIGN is supported or not),
and in the assignment of characters to code positions.  For the European
languages in particular, the following variants typically exist:

   * an ISO 8859 codeset

   * a Microsoft Windows code page, which is typically derived from an
     8859 codeset, but replaces control characters with additional
     graphic characters

   * an IBM EBCDIC code page

   * an IBM PC code page, which is ASCII compatible

Codec                 Aliases                              語言
                                                           
------------------------------------------------------------------------------------------------
                                                           
ascii                 646, us-ascii                        英文
                                                           
                                                           
big5                  big5-tw, csbig5                      繁體中文
                                                           
                                                           
big5hkscs             big5-hkscs, hkscs                    繁體中文
                                                           
                                                           
cp037                 IBM037, IBM039                       英文
                                                           
                                                           
cp273                 273, IBM273, csIBM273                德文
                                                           
                                                           在 3.4 版被加入.
                                                           
                                                           
cp424                 EBCDIC-CP-HE, IBM424                 希伯來文
                                                           
                                                           
cp437                 437, IBM437                          英文
                                                           
                                                           
cp500                 EBCDIC-CP-BE, EBCDIC-CP-CH, IBM500   Western Europe
                                                           
                                                           
cp720                                                      阿拉伯文
                                                           
                                                           
cp737                                                      希臘文
                                                           
                                                           
cp775                 IBM775                               Baltic languages
                                                           
                                                           
cp850                 850, IBM850                          Western Europe
                                                           
                                                           
cp852                 852, IBM852                          Central and Eastern Europe
                                                           
                                                           
cp855                 855, IBM855                          Bulgarian, Byelorussian,
                                                           Macedonian, Russian, Serbian
                                                           
                                                           
cp856                                                      希伯來文
                                                           
                                                           
cp857                 857, IBM857                          土耳其文
                                                           
                                                           
cp858                 858, IBM858                          Western Europe
                                                           
                                                           
cp860                 860, IBM860                          Portuguese
                                                           
                                                           
cp861                 861, CP-IS, IBM861                   Icelandic
                                                           
                                                           
cp862                 862, IBM862                          希伯來文
                                                           
                                                           
cp863                 863, IBM863                          Canadian
                                                           
                                                           
cp864                 IBM864                               阿拉伯文
                                                           
                                                           
cp865                 865, IBM865                          Danish, Norwegian
                                                           
                                                           
cp866                 866, IBM866                          俄羅斯文
                                                           
                                                           
cp869                 869, CP-GR, IBM869                   希臘文
                                                           
                                                           
cp874                                                      泰文
                                                           
                                                           
cp875                                                      希臘文
                                                           
                                                           
cp932                 932, ms932, mskanji, ms-kanji,       日文
                      windows-31j                          
                      
                                                           
cp949                 949, ms949, uhc                      韓文
                                                           
                                                           
cp950                 950, ms950                           繁體中文
                                                           
                                                           
cp1006                                                     Urdu
                                                           
                                                           
cp1026                ibm1026                              土耳其文
                                                           
                                                           
cp1125                1125, ibm1125, cp866u, ruscii        烏克蘭文
                                                           
                                                           在 3.4 版被加入.
                                                           
                                                           
cp1140                ibm1140                              Western Europe
                                                           
                                                           
cp1250                windows-1250                         Central and Eastern Europe
                                                           
                                                           
cp1251                windows-1251                         Bulgarian, Byelorussian,
                                                           Macedonian, Russian, Serbian
                                                           
                                                           
cp1252                windows-1252                         Western Europe
                                                           
                                                           
cp1253                windows-1253                         希臘文
                                                           
                                                           
cp1254                windows-1254                         土耳其文
                                                           
                                                           
cp1255                windows-1255                         希伯來文
                                                           
                                                           
cp1256                windows-1256                         阿拉伯文
                                                           
                                                           
cp1257                windows-1257                         Baltic languages
                                                           
                                                           
cp1258                windows-1258                         越南文
                                                           
                                                           
euc_jp                eucjp, ujis, u-jis                   日文
                                                           
                                                           
euc_jis_2004          jisx0213, eucjis2004                 日文
                                                           
                                                           
euc_jisx0213          eucjisx0213                          日文
                                                           
                                                           
euc_kr                euckr, korean, ksc5601, ks_c-5601,   韓文
                      ks_c-5601-1987, ksx1001, ks_x-1001   
                      
                                                           
gb2312                chinese, csiso58gb231280, euc-cn,    簡體中文
                      euccn, eucgb2312-cn, gb2312-1980,    
                      gb2312-80, iso-ir-58
                      
                                                           
gbk                   936, cp936, ms936                    Unified Chinese
                                                           
                                                           
gb18030               gb18030-2000                         Unified Chinese
                                                           
                                                           
hz                    hzgb, hz-gb, hz-gb-2312              簡體中文
                                                           
                                                           
iso2022_jp            csiso2022jp, iso2022jp,              日文
                      iso-2022-jp                          
                      
                                                           
iso2022_jp_1          iso2022jp-1, iso-2022-jp-1           日文
                                                           
                                                           
iso2022_jp_2          iso2022jp-2, iso-2022-jp-2           Japanese, Korean, Simplified
                                                           Chinese, Western Europe, Greek
                                                           
                                                           
iso2022_jp_2004       iso2022jp-2004, iso-2022-jp-2004     日文
                                                           
                                                           
iso2022_jp_3          iso2022jp-3, iso-2022-jp-3           日文
                                                           
                                                           
iso2022_jp_ext        iso2022jp-ext, iso-2022-jp-ext       日文
                                                           
                                                           
iso2022_kr            csiso2022kr, iso2022kr,              韓文
                      iso-2022-kr                          
                      
                                                           
latin_1               iso-8859-1, iso8859-1, 8859,         Western Europe
                      cp819, latin, latin1, L1             
                      
                                                           
iso8859_2             iso-8859-2, latin2, L2               Central and Eastern Europe
                                                           
                                                           
iso8859_3             iso-8859-3, latin3, L3               Esperanto, Maltese
                                                           
                                                           
iso8859_4             iso-8859-4, latin4, L4               Baltic languages
                                                           
                                                           
iso8859_5             iso-8859-5, cyrillic                 Bulgarian, Byelorussian,
                                                           Macedonian, Russian, Serbian
                                                           
                                                           
iso8859_6             iso-8859-6, arabic                   阿拉伯文
                                                           
                                                           
iso8859_7             iso-8859-7, greek, greek8            希臘文
                                                           
                                                           
iso8859_8             iso-8859-8, hebrew                   希伯來文
                                                           
                                                           
iso8859_9             iso-8859-9, latin5, L5               土耳其文
                                                           
                                                           
iso8859_10            iso-8859-10, latin6, L6              Nordic languages
                                                           
                                                           
iso8859_11            iso-8859-11, thai                    Thai languages
                                                           
                                                           
iso8859_13            iso-8859-13, latin7, L7              Baltic languages
                                                           
                                                           
iso8859_14            iso-8859-14, latin8, L8              Celtic languages
                                                           
                                                           
iso8859_15            iso-8859-15, latin9, L9              Western Europe
                                                           
                                                           
iso8859_16            iso-8859-16, latin10, L10            South-Eastern Europe
                                                           
                                                           
johab                 cp1361, ms1361                       韓文
                                                           
                                                           
koi8_r                                                     俄羅斯文
                                                           
                                                           
koi8_t                                                     Tajik
                                                           
                                                           在 3.5 版被加入.
                                                           
                                                           
koi8_u                                                     烏克蘭文
                                                           
                                                           
kz1048                kz_1048, strk1048_2002, rk1048       Kazakh
                                                           
                                                           在 3.5 版被加入.
                                                           
                                                           
mac_cyrillic          maccyrillic                          Bulgarian, Byelorussian,
                                                           Macedonian, Russian, Serbian
                                                           
                                                           
mac_greek             macgreek                             希臘文
                                                           
                                                           
mac_iceland           maciceland                           Icelandic
                                                           
                                                           
mac_latin2            maclatin2, maccentraleurope,         Central and Eastern Europe
                      mac_centeuro                         
                      
                                                           
mac_roman             macroman, macintosh                  Western Europe
                                                           
                                                           
mac_turkish           macturkish                           土耳其文
                                                           
                                                           
ptcp154               csptcp154, pt154, cp154,             Kazakh
                      cyrillic-asian                       
                      
                                                           
shift_jis             csshiftjis, shiftjis, sjis, s_jis    日文
                                                           
                                                           
shift_jis_2004        shiftjis2004, sjis_2004, sjis2004    日文
                                                           
                                                           
shift_jisx0213        shiftjisx0213, sjisx0213,            日文
                      s_jisx0213                           
                      
                                                           
utf_32                U32, utf32                           all languages
                                                           
                                                           
utf_32_be             UTF-32BE                             all languages
                                                           
                                                           
utf_32_le             UTF-32LE                             all languages
                                                           
                                                           
utf_16                U16, utf16                           all languages
                                                           
                                                           
utf_16_be             UTF-16BE                             all languages
                                                           
                                                           
utf_16_le             UTF-16LE                             all languages
                                                           
                                                           
utf_7                 U7, unicode-1-1-utf-7                all languages
                                                           
                                                           
utf_8                 U8, UTF, utf8, cp65001               all languages
                                                           
                                                           
utf_8_sig                                                  all languages
                                                           

在 3.4 版的變更: The utf-16* and utf-32* encoders no longer allow
surrogate code points (‘U+D800’-‘U+DFFF’) to be encoded.  The utf-32*
decoders no longer decode byte sequences that correspond to surrogate
code points.

在 3.8 版的變更: ‘cp65001’ is now an alias to ‘utf_8’.


File: python.info,  Node: Python Specific Encodings,  Next: encodings idna --- Internationalized Domain Names in Applications,  Prev: Standard Encodings,  Up: codecs --- 編解碼器註冊表和基底類別

5.7.2.14 Python Specific Encodings
..................................

A number of predefined codecs are specific to Python, so their codec
names have no meaning outside Python.  These are listed in the tables
below based on the expected input and output types (note that while text
encodings are the most common use case for codecs, the underlying codec
infrastructure supports arbitrary data transforms rather than just text
encodings).  For asymmetric codecs, the stated meaning describes the
encoding direction.

* Menu:

* Text Encodings::
* Binary Transforms::
* Text Transforms::


File: python.info,  Node: Text Encodings,  Next: Binary Transforms,  Up: Python Specific Encodings

5.7.2.15 Text Encodings
.......................

The following codecs provide *note str: 3f2. to *note bytes: 1a5.
encoding and *note bytes-like object: cd4. to *note str: 3f2. decoding,
similar to the Unicode text encodings.

Codec                    Aliases       含義
                                       
-----------------------------------------------------------------------
                                       
idna                                   Implement RFC 3490(1), see
                                       also
                                       *note encodings.idna: 48.
                                       Only ‘errors='strict'’ is
                                       supported.
                                       
                                       
mbcs                     ansi, dbcs    Windows only: Encode the
                                       operand according to the ANSI
                                       codepage (CP_ACP).
                                       
                                       
oem                                    Windows only: Encode the
                                       operand according to the OEM
                                       codepage (CP_OEMCP).
                                       
                                       在 3.6 版被加入.
                                       
                                       
palmos                                 Encoding of PalmOS 3.5.
                                       
                                       
punycode                               Implement RFC 3492(2).
                                       Stateful codecs are not
                                       supported.
                                       
                                       
raw_unicode_escape                     Latin-1 encoding with
                                       ‘\uXXXX’ and ‘\UXXXXXXXX’ for
                                       other code points.  Existing
                                       backslashes are not escaped
                                       in any way.  It is used in
                                       the Python pickle protocol.
                                       
                                       
undefined                              Raise an exception for all
                                       conversions, even empty
                                       strings.  The error handler
                                       is ignored.
                                       
                                       
unicode_escape                         Encoding suitable as the
                                       contents of a Unicode literal
                                       in ASCII-encoded Python
                                       source code, except that
                                       quotes are not escaped.
                                       Decode from Latin-1 source
                                       code.  Beware that Python
                                       source code actually uses
                                       UTF-8 by default.
                                       

在 3.8 版的變更: "unicode_internal" codec is removed.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc3490.html

   (2) https://datatracker.ietf.org/doc/html/rfc3492.html


File: python.info,  Node: Binary Transforms,  Next: Text Transforms,  Prev: Text Encodings,  Up: Python Specific Encodings

5.7.2.16 Binary Transforms
..........................

The following codecs provide binary transforms: *note bytes-like object:
cd4. to *note bytes: 1a5. mappings.  They are not supported by *note
bytes.decode(): 87b. (which only produces *note str: 3f2. output).

Codec                      Aliases                含義                               Encoder / decoder
                                                                                     
------------------------------------------------------------------------------------------------------------------------
                                                                                     
base64_codec (1)           base64, base_64        Convert the operand to multiline   *note base64.encodebytes(): 8f7.
                                                  MIME base64 (the result always     /
                                                  includes a trailing ‘'\n'’).       *note base64.decodebytes(): 8f8.
                                                                                     
                                                  在 3.4 版的變更: accepts any
                                                  *note bytes-like object: cd4. as
                                                  input for encoding and decoding
                                                  
                                                                                     
bz2_codec                  bz2                    Compress the operand using bz2.    *note bz2.compress(): 22ef. /
                                                                                     *note bz2.decompress(): 1030.
                                                                                     
                                                                                     
hex_codec                  hex                    Convert the operand to             *note binascii.b2a_hex(): 22f0.
                                                  hexadecimal representation, with   /
                                                  two digits per byte.               *note binascii.a2b_hex(): 22f1.
                                                                                     
                                                                                     
quopri_codec               quopri,                Convert the operand to MIME        *note quopri.encode(): 22f2.
                           quotedprintable,       quoted printable.                  with ‘quotetabs=True’ /
                           quoted_printable                                          *note quopri.decode(): 22f3.
                                                                                     
                                                                                     
uu_codec                   uu                     Convert the operand using
                                                  uuencode.
                                                  
                                                                                     
zlib_codec                 zip, zlib              Compress the operand using gzip.   *note zlib.compress(): 5e5. /
                                                                                     *note zlib.decompress(): cb4.
                                                                                     

在 3.2 版被加入: Restoration of the binary transforms.

在 3.4 版的變更: Restoration of the aliases for the binary transforms.

   ---------- Footnotes ----------

   (1) In addition to *note bytes-like objects: cd4, ‘'base64_codec'’
also accepts ASCII-only instances of *note str: 3f2. for decoding


File: python.info,  Node: Text Transforms,  Prev: Binary Transforms,  Up: Python Specific Encodings

5.7.2.17 Text Transforms
........................

The following codec provides a text transform: a *note str: 3f2. to
*note str: 3f2. mapping.  It is not supported by *note str.encode():
87a. (which only produces *note bytes: 1a5. output).

Codec                    Aliases       含義
                                       
-----------------------------------------------------------------------
                                       
rot_13                   rot13         Return the Caesar-cypher
                                       encryption of the operand.
                                       

在 3.2 版被加入: Restoration of the ‘rot_13’ text transform.

在 3.4 版的變更: Restoration of the ‘rot13’ alias.


File: python.info,  Node: encodings idna --- Internationalized Domain Names in Applications,  Next: encodings mbcs --- Windows ANSI codepage,  Prev: Python Specific Encodings,  Up: codecs --- 編解碼器註冊表和基底類別

5.7.2.18 ‘encodings.idna’ -- Internationalized Domain Names in Applications
...........................................................................

This module implements RFC 3490(1) (Internationalized Domain Names in
Applications) and RFC 3492(2) (Nameprep: A Stringprep Profile for
Internationalized Domain Names (IDN)). It builds upon the ‘punycode’
encoding and *note stringprep: bf.

If you need the IDNA 2008 standard from RFC 5891(3) and RFC 5895(4), use
the third-party idna(5) module.

These RFCs together define a protocol to support non-ASCII characters in
domain names.  A domain name containing non-ASCII characters (such as
‘www.Alliancefrançaise.nu’) is converted into an ASCII-compatible
encoding (ACE, such as ‘www.xn--alliancefranaise-npb.nu’).  The ACE form
of the domain name is then used in all places where arbitrary characters
are not allowed by the protocol, such as DNS queries, HTTP ‘Host’
fields, and so on.  This conversion is carried out in the application;
if possible invisible to the user: The application should transparently
convert Unicode domain labels to IDNA on the wire, and convert back ACE
labels to Unicode before presenting them to the user.

Python supports this conversion in several ways: the ‘idna’ codec
performs conversion between Unicode and ACE, separating an input string
into labels based on the separator characters defined in section 3.1 of
RFC 3490(6) and converting each label to ACE as required, and conversely
separating an input byte string into labels based on the ‘.’ separator
and converting any ACE labels found into unicode.  Furthermore, the
*note socket: b8. module transparently converts Unicode host names to
ACE, so that applications need not be concerned about converting host
names themselves when they pass them to the socket module.  On top of
that, modules that have host names as function parameters, such as *note
http.client: 65. and *note ftplib: 54, accept Unicode host names (*note
http.client: 65. then also transparently sends an IDNA hostname in the
‘Host’ field if it sends that field at all).

When receiving host names from the wire (such as in reverse name
lookup), no automatic conversion to Unicode is performed: applications
wishing to present such host names to the user should decode them to
Unicode.

The module *note encodings.idna: 48. also implements the nameprep
procedure, which performs certain normalizations on host names, to
achieve case-insensitivity of international domain names, and to unify
similar characters.  The nameprep functions can be used directly if
desired.

 -- 函式: encodings.idna.nameprep (label)

     Return the nameprepped version of 'label'.  The implementation
     currently assumes query strings, so ‘AllowUnassigned’ is true.

 -- 函式: encodings.idna.ToASCII (label)

     Convert a label to ASCII, as specified in RFC 3490(7).
     ‘UseSTD3ASCIIRules’ is assumed to be false.

 -- 函式: encodings.idna.ToUnicode (label)

     Convert a label to Unicode, as specified in RFC 3490(8).

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc3490.html

   (2) https://datatracker.ietf.org/doc/html/rfc3492.html

   (3) https://datatracker.ietf.org/doc/html/rfc5891.html

   (4) https://datatracker.ietf.org/doc/html/rfc5895.html

   (5) https://pypi.org/project/idna/

   (6) https://datatracker.ietf.org/doc/html/rfc3490.html#section-3.1

   (7) https://datatracker.ietf.org/doc/html/rfc3490.html

   (8) https://datatracker.ietf.org/doc/html/rfc3490.html


File: python.info,  Node: encodings mbcs --- Windows ANSI codepage,  Next: encodings utf_8_sig --- UTF-8 codec with BOM signature,  Prev: encodings idna --- Internationalized Domain Names in Applications,  Up: codecs --- 編解碼器註冊表和基底類別

5.7.2.19 ‘encodings.mbcs’ -- Windows ANSI codepage
..................................................

This module implements the ANSI codepage (CP_ACP).

*note 適用: 1c56.：Windows。

在 3.2 版的變更: Before 3.2, the 'errors' argument was ignored;
‘'replace'’ was always used to encode, and ‘'ignore'’ to decode.

在 3.3 版的變更: Support any error handler.


File: python.info,  Node: encodings utf_8_sig --- UTF-8 codec with BOM signature,  Prev: encodings mbcs --- Windows ANSI codepage,  Up: codecs --- 編解碼器註冊表和基底類別

5.7.2.20 ‘encodings.utf_8_sig’ -- UTF-8 codec with BOM signature
................................................................

This module implements a variant of the UTF-8 codec.  On encoding, a
UTF-8 encoded BOM will be prepended to the UTF-8 encoded bytes.  For the
stateful encoder this is only done once (on the first write to the byte
stream).  On decoding, an optional UTF-8 encoded BOM at the start of the
data will be skipped.


File: python.info,  Node: 資料型別,  Next: 數值與數學模組,  Prev: 二進位資料服務,  Up: Python 標準函式庫 Standard Library

5.8 資料型別
============

本章節所描述的模組 (module) 提供了多樣的專門資料型別，例如日期與時間、固
定型別陣列 (fixed-type arrays)、堆積佇列 (heap queues)、雙端佇列
(double-ended queues) 與列舉 (enumerations)。

Python 也有提供一些內建資料型別，特別是 *note dict: 23b.、*note list:
5b6.、*note set: 57d. 與 *note frozenset: 57e. 和 *note tuple: 322.。
*note str: 3f2. 類別是用來儲存 Unicode 字串，*note bytes: 1a5. 與 *note
bytearray: 4e3. 類別則是用來儲存二進位制資料。

本章節包含下列模組的文件：

* Menu:

* datetime: datetime --- 日期與時間的基本型別. 日期與時間的基本型別
* zoneinfo: zoneinfo --- IANA 時區支援. IANA 時區支援
* calendar: calendar --- 日曆相關函式. 日曆相關函式
* collections: collections --- 容器資料型態. 容器資料型態
* collections.abc: collections abc --- 容器的抽象基底類別. 容器的抽象基底類別
* heapq: heapq --- 堆積佇列 heap queue 演算法. 堆積佇列 (heap queue) 演算法
* bisect: bisect --- 陣列二分演算法 Array bisection algorithm. 陣列二分演算法 (Array bisection algorithm)
* array: array --- 高效率的數值型陣列. 高效率的數值型陣列
* weakref: weakref --- 弱參照. 弱參照
* types: types --- 動態型別建立與內建型別名稱. 動態型別建立與內建型別名稱
* copy: copy --- 淺層 shallow 和深層 deep 複製操作. 淺層 (shallow) 和深層 (deep) 複製操作
* pprint: pprint --- 資料美化列印器. 資料美化列印器
* reprlib: reprlib --- repr 的替代實作. repr() 的替代實作
* enum: enum --- 對列舉的支援. 對列舉的支援
* graphlib —- 使用類圖 (graph-like) 結構進行操作的功能: graphlib —-- 使用類圖 graph-like 結構進行操作的功能.


File: python.info,  Node: datetime --- 日期與時間的基本型別,  Next: zoneinfo --- IANA 時區支援,  Up: 資料型別

5.8.1 ‘datetime’ -- 日期與時間的基本型別
----------------------------------------

'原始碼：'Lib/datetime.py(1)

__________________________________________________________________

‘datetime’ 模組提供操作日期與時間的類別。

While date and time arithmetic is supported, the focus of the
implementation is on efficient attribute extraction for output
formatting and manipulation.

     小訣竅: 跳轉至*note 格式碼 (format codes): 2300.。

也參考
......

*note calendar: 10. 模組

     與日曆相關的一般函式。

*note time: d7. 模組

     Time access and conversions.

*note zoneinfo: 11a. 模組

     Concrete time zones representing the IANA time zone database.

Package dateutil(2)

     帶有時區與剖析擴充支援的第三方函式庫。

DateType(3) 套件

     Third-party library that introduces distinct static types to e.g.
     allow *note static type checkers: 252. to differentiate between
     naive and aware datetimes.

* Menu:

* Aware and Naive Objects::
* 常數::
* Available Types::
* timedelta 物件::
* date 物件::
* datetime 物件::
* time 物件::
* tzinfo 物件::
* timezone 物件::
* strftime() 與 strptime() 的行為: strftime 與 strptime 的行為.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/datetime.py

   (2) https://dateutil.readthedocs.io/en/stable/

   (3) https://pypi.org/project/DateType/


File: python.info,  Node: Aware and Naive Objects,  Next: 常數,  Up: datetime --- 日期與時間的基本型別

5.8.1.1 Aware and Naive Objects
...............................

Date and time objects may be categorized as "aware" or "naive" depending
on whether or not they include time zone information.

With sufficient knowledge of applicable algorithmic and political time
adjustments, such as time zone and daylight saving time information, an
'aware' object can locate itself relative to other aware objects.  An
aware object represents a specific moment in time that is not open to
interpretation.  (1)

A 'naive' object does not contain enough information to unambiguously
locate itself relative to other date/time objects.  Whether a naive
object represents Coordinated Universal Time (UTC), local time, or time
in some other time zone is purely up to the program, just like it is up
to the program whether a particular number represents metres, miles, or
mass.  Naive objects are easy to understand and to work with, at the
cost of ignoring some aspects of reality.

For applications requiring aware objects, *note datetime: 1b0. and *note
time: 1b2. objects have an optional time zone information attribute,
‘tzinfo’, that can be set to an instance of a subclass of the abstract
*note tzinfo: 582. class.  These *note tzinfo: 582. objects capture
information about the offset from UTC time, the time zone name, and
whether daylight saving time is in effect.

Only one concrete *note tzinfo: 582. class, the *note timezone: 1059.
class, is supplied by the ‘datetime’ module.  The ‘timezone’ class can
represent simple time zones with fixed offsets from UTC, such as UTC
itself or North American EST and EDT time zones.  Supporting time zones
at deeper levels of detail is up to the application.  The rules for time
adjustment across the world are more political than rational, change
frequently, and there is no standard suitable for every application
aside from UTC.

   ---------- Footnotes ----------

   (1) 也就是說，我們會忽略相對論的效應


File: python.info,  Node: 常數,  Next: Available Types,  Prev: Aware and Naive Objects,  Up: datetime --- 日期與時間的基本型別

5.8.1.2 常數
............

‘datetime’ 模組匯出以下常數：

 -- 資料: datetime.MINYEAR

     The smallest year number allowed in a *note date: 1b1. or *note
     datetime: 1b0. object.  *note MINYEAR: 2304. is 1.

 -- 資料: datetime.MAXYEAR

     The largest year number allowed in a *note date: 1b1. or *note
     datetime: 1b0. object.  *note MAXYEAR: 2305. is 9999.

 -- 屬性: datetime.UTC

     Alias for the UTC time zone singleton *note datetime.timezone.utc:
     5b9.

     在 3.11 版被加入.


File: python.info,  Node: Available Types,  Next: timedelta 物件,  Prev: 常數,  Up: datetime --- 日期與時間的基本型別

5.8.1.3 Available Types
.......................

 -- 類別: datetime.date

     An idealized naive date, assuming the current Gregorian calendar
     always was, and always will be, in effect.  Attributes: *note year:
     2307, *note month: 2308, and *note day: 2309.

 -- 類別: datetime.time

     An idealized time, independent of any particular day, assuming that
     every day has exactly 24*60*60 seconds.  (There is no notion of
     "leap seconds" here.)  Attributes: *note hour: 230a, *note minute:
     230b, *note second: 230c, *note microsecond: 230d, and *note
     tzinfo: 230e.

 -- 類別: datetime.datetime

     A combination of a date and a time.  Attributes: *note year: 230f,
     *note month: 2310, *note day: 2311, *note hour: 2312, *note minute:
     2313, *note second: 2314, *note microsecond: 2315, and *note
     tzinfo: 2316.

 -- 類別: datetime.timedelta

     表示兩個 *note datetime: 1b0. 或 *note date: 1b1. 實例之間時間的差
     異，以微秒為解析度。

 -- 類別: datetime.tzinfo

     An abstract base class for time zone information objects.  These
     are used by the *note datetime: 1b0. and *note time: 1b2. classes
     to provide a customizable notion of time adjustment (for example,
     to account for time zone and/or daylight saving time).

 -- 類別: datetime.timezone

     A class that implements the *note tzinfo: 582. abstract base class
     as a fixed offset from the UTC.

     在 3.2 版被加入.

Objects of these types are immutable.

Subclass relationships:

     object
         timedelta
         tzinfo
             timezone
         time
         date
             datetime

* Menu:

* 常見屬性::
* Determining if an Object is Aware or Naive::


File: python.info,  Node: 常見屬性,  Next: Determining if an Object is Aware or Naive,  Up: Available Types

5.8.1.4 常見屬性
................

The *note date: 1b1, *note datetime: 1b0, *note time: 1b2, and *note
timezone: 1059. types share these common features:

   - Objects of these types are immutable.

   - Objects of these types are *note hashable: 5b5, meaning that they
     can be used as dictionary keys.

   - Objects of these types support efficient pickling via the *note
     pickle: 95. module.


File: python.info,  Node: Determining if an Object is Aware or Naive,  Prev: 常見屬性,  Up: Available Types

5.8.1.5 Determining if an Object is Aware or Naive
..................................................

Objects of the *note date: 1b1. type are always naive.

An object of type *note time: 1b2. or *note datetime: 1b0. may be aware
or naive.

A *note datetime: 1b0. object 'd' is aware if both of the following
hold:

  1. ‘d.tzinfo’ 不是 ‘None’

  2. ‘d.tzinfo.utcoffset(d)’ 不會回傳 ‘None’

否則 'd' 會是 naive 的。

A *note time: 1b2. object 't' is aware if both of the following hold:

  1. ‘t.tzinfo’ 不是 ‘None’

  2. ‘t.tzinfo.utcoffset(None)’ 沒有回傳 ‘None’。

Otherwise, 't' is naive.

The distinction between aware and naive doesn't apply to *note
timedelta: 973. objects.


File: python.info,  Node: timedelta 物件,  Next: date 物件,  Prev: Available Types,  Up: datetime --- 日期與時間的基本型別

5.8.1.6 ‘timedelta’ 物件
........................

一個 *note timedelta: 973. 物件代表著一段持續時間，即兩個 *note
datetime: 1b0. 或 *note date: 1b1. 之間的差異。

 -- 類別: datetime.timedelta (days=0, seconds=0, microseconds=0,
          milliseconds=0, minutes=0, hours=0, weeks=0)

     All arguments are optional and default to 0.  Arguments may be
     integers or floats, and may be positive or negative.

     Only 'days', 'seconds' and 'microseconds' are stored internally.
     Arguments are converted to those units:

        * 一毫秒會被轉換為 1000 微秒。

        * 一分鐘會被轉換為 60 秒。

        * 一小時會被轉換為 3600 秒。

        * 一週會被轉換為 7 天。

     and days, seconds and microseconds are then normalized so that the
     representation is unique, with

        * ‘0 <= microseconds < 1000000’

        * ‘0 <= seconds < 3600*24’ (the number of seconds in one day)

        * ‘-999999999 <= days <= 999999999’

     The following example illustrates how any arguments besides 'days',
     'seconds' and 'microseconds' are "merged" and normalized into those
     three resulting attributes:

          >>> from datetime import timedelta
          >>> delta = timedelta(
          ...     days=50,
          ...     seconds=27,
          ...     microseconds=10,
          ...     milliseconds=29000,
          ...     minutes=5,
          ...     hours=8,
          ...     weeks=2
          ... )
          >>> # Only days, seconds, and microseconds remain
          >>> delta
          datetime.timedelta(days=64, seconds=29156, microseconds=10)

     If any argument is a float and there are fractional microseconds,
     the fractional microseconds left over from all arguments are
     combined and their sum is rounded to the nearest microsecond using
     round-half-to-even tiebreaker.  If no argument is a float, the
     conversion and normalization processes are exact (no information is
     lost).

     If the normalized value of days lies outside the indicated range,
     *note OverflowError: 825. is raised.

     Note that normalization of negative values may be surprising at
     first.  For example:

          >>> from datetime import timedelta
          >>> d = timedelta(microseconds=-1)
          >>> (d.days, d.seconds, d.microseconds)
          (-1, 86399, 999999)

類別屬性：

 -- 屬性: timedelta.min

     The most negative *note timedelta: 973. object,
     ‘timedelta(-999999999)’.

 -- 屬性: timedelta.max

     The most positive *note timedelta: 973. object,
     ‘timedelta(days=999999999, hours=23, minutes=59, seconds=59,
     microseconds=999999)’.

 -- 屬性: timedelta.resolution

     The smallest possible difference between non-equal *note timedelta:
     973. objects, ‘timedelta(microseconds=1)’.

Note that, because of normalization, ‘timedelta.max’ is greater than
‘-timedelta.min’.  ‘-timedelta.max’ is not representable as a *note
timedelta: 973. object.

Instance attributes (read-only):

 -- 屬性: timedelta.days

     在 -999,999,999 到 999,999,999 （含）之間

 -- 屬性: timedelta.seconds

     在 0 到 86,399 （含）之間

 -- 屬性: timedelta.microseconds

     在 0 到 999,999 （含）之間

Supported operations:

Operation                            Result
                                     
-----------------------------------------------------------------------------------------
                                     
‘t1 = t2 + t3’                       Sum of ‘t2’ and ‘t3’.  Afterwards ‘t1 - t2 == t3’
                                     and ‘t1 - t3 == t2’ are true.  (1)
                                     
                                     
‘t1 = t2 - t3’                       Difference of ‘t2’ and ‘t3’.  Afterwards ‘t1 ==
                                     t2 - t3’ and ‘t2 == t1 + t3’ are true.  (1)(6)
                                     
                                     
‘t1 = t2 * i or t1 = i * t2’         Delta multiplied by an integer.  Afterwards ‘t1
                                     // i == t2’ is true, provided ‘i != 0’.
                                     
                                     
                                     In general, ‘t1 * i == t1 * (i-1) + t1’ is true.
                                     (1)
                                     
                                     
‘t1 = t2 * f or t1 = f * t2’         Delta multiplied by a float.  The result is
                                     rounded to the nearest multiple of
                                     timedelta.resolution using round-half-to-even.
                                     
                                     
‘f = t2 / t3’                        Division (3) of overall duration ‘t2’ by interval
                                     unit ‘t3’.  Returns a *note float: 2c8. object.
                                     
                                     
‘t1 = t2 / f or t1 = t2 / i’         Delta divided by a float or an int.  The result
                                     is rounded to the nearest multiple of
                                     timedelta.resolution using round-half-to-even.
                                     
                                     
‘t1 = t2 // i’ or ‘t1 = t2 // t3’    The floor is computed and the remainder (if any)
                                     is thrown away.  In the second case, an integer
                                     is returned.  (3)
                                     
                                     
‘t1 = t2 % t3’                       The remainder is computed as a
                                     *note timedelta: 973. object.  (3)
                                     
                                     
‘q, r = divmod(t1, t2)’              Computes the quotient and the remainder: ‘q = t1
                                     // t2’ (3) and ‘r = t1 % t2’.  q is an integer
                                     and r is a *note timedelta: 973. object.
                                     
                                     
‘+t1’                                Returns a *note timedelta: 973. object with the
                                     same value.  (2)
                                     
                                     
‘-t1’                                Equivalent to ‘timedelta(-t1.days, -t1.seconds*,
                                     -t1.microseconds)’, and to ‘t1 * -1’.  (1)(4)
                                     
                                     
‘abs(t)’                             Equivalent to ‘+t’ when ‘t.days >= 0’, and to
                                     ‘-t’ when ‘t.days < 0’.  (2)
                                     
                                     
‘str(t)’                             Returns a string in the form ‘[D day[s],
                                     ][H]H:MM:SS[.UUUUUU]’, where D is negative for
                                     negative ‘t’.  (5)
                                     
                                     
‘repr(t)’                            Returns a string representation of the
                                     *note timedelta: 973. object as a constructor
                                     call with canonical attribute values.
                                     

註解：

  1. 這是精確的，但可能會溢位。

  2. 這是精確的，且不會溢位。

  3. Division by zero raises *note ZeroDivisionError: 8e9.

  4. ‘-timedelta.max’ is not representable as a *note timedelta: 973.
     object.

  5. String representations of *note timedelta: 973. objects are
     normalized similarly to their internal representation.  This leads
     to somewhat unusual results for negative timedeltas.  For example:

          >>> timedelta(hours=-5)
          datetime.timedelta(days=-1, seconds=68400)
          >>> print(_)
          -1 day, 19:00:00

  6. The expression ‘t2 - t3’ will always be equal to the expression ‘t2
     + (-t3)’ except when t3 is equal to ‘timedelta.max’; in that case
     the former will produce a result while the latter will overflow.

In addition to the operations listed above, *note timedelta: 973.
objects support certain additions and subtractions with *note date: 1b1.
and *note datetime: 1b0. objects (see below).

在 3.2 版的變更: Floor division and true division of a *note timedelta:
973. object by another *note timedelta: 973. object are now supported,
as are remainder operations and the *note divmod(): 945. function.  True
division and multiplication of a *note timedelta: 973. object by a *note
float: 2c8. object are now supported.

*note timedelta: 973. objects support equality and order comparisons.

In Boolean contexts, a *note timedelta: 973. object is considered to be
true if and only if it isn't equal to ‘timedelta(0)’.

實例方法：

 -- 方法: timedelta.total_seconds ()

     Return the total number of seconds contained in the duration.
     Equivalent to ‘td / timedelta(seconds=1)’.  For interval units
     other than seconds, use the division form directly (e.g.  ‘td /
     timedelta(microseconds=1)’).

     Note that for very large time intervals (greater than 270 years on
     most platforms) this method will lose microsecond accuracy.

     在 3.2 版被加入.

* Menu:

* 用法範例：timedelta::


File: python.info,  Node: 用法範例：timedelta,  Up: timedelta 物件

5.8.1.7 用法範例：‘timedelta’
.............................

An additional example of normalization:

     >>> # Components of another_year add up to exactly 365 days
     >>> from datetime import timedelta
     >>> year = timedelta(days=365)
     >>> another_year = timedelta(weeks=40, days=84, hours=23,
     ...                          minutes=50, seconds=600)
     >>> year == another_year
     True
     >>> year.total_seconds()
     31536000.0

Examples of *note timedelta: 973. arithmetic:

     >>> from datetime import timedelta
     >>> year = timedelta(days=365)
     >>> ten_years = 10 * year
     >>> ten_years
     datetime.timedelta(days=3650)
     >>> ten_years.days // 365
     10
     >>> nine_years = ten_years - year
     >>> nine_years
     datetime.timedelta(days=3285)
     >>> three_years = nine_years // 3
     >>> three_years, three_years.days // 365
     (datetime.timedelta(days=1095), 3)


File: python.info,  Node: date 物件,  Next: datetime 物件,  Prev: timedelta 物件,  Up: datetime --- 日期與時間的基本型別

5.8.1.8 ‘date’ 物件
...................

A *note date: 1b1. object represents a date (year, month and day) in an
idealized calendar, the current Gregorian calendar indefinitely extended
in both directions.

January 1 of year 1 is called day number 1, January 2 of year 1 is
called day number 2, and so on.  (1)

 -- 類別: datetime.date (year, month, day)

     All arguments are required.  Arguments must be integers, in the
     following ranges:

        * ‘MINYEAR <= year <= MAXYEAR’

        * ‘1 <= month <= 12’

        * ‘1 <= day <= number of days in the given month and year’

     If an argument outside those ranges is given, *note ValueError:
     1e7. is raised.

Other constructors, all class methods:

 -- 方法: classmethod date.today ()

     回傳目前的本地日期。

     這等同於 ‘date.fromtimestamp(time.time())’。

 -- 方法: classmethod date.fromtimestamp (timestamp)

     Return the local date corresponding to the POSIX timestamp, such as
     is returned by *note time.time(): 239.

     This may raise *note OverflowError: 825, if the timestamp is out of
     the range of values supported by the platform C ‘localtime()’
     function, and *note OSError: 350. on ‘localtime()’ failure.  It's
     common for this to be restricted to years from 1970 through 2038.
     Note that on non-POSIX systems that include leap seconds in their
     notion of a timestamp, leap seconds are ignored by *note
     fromtimestamp(): 14fd.

     在 3.3 版的變更: Raise *note OverflowError: 825. instead of *note
     ValueError: 1e7. if the timestamp is out of the range of values
     supported by the platform C ‘localtime()’ function.  Raise *note
     OSError: 350. instead of *note ValueError: 1e7. on ‘localtime()’
     failure.

 -- 方法: classmethod date.fromordinal (ordinal)

     Return the date corresponding to the proleptic Gregorian ordinal,
     where January 1 of year 1 has ordinal 1.

     *note ValueError: 1e7. is raised unless ‘1 <= ordinal <=
     date.max.toordinal()’.  For any date 'd',
     ‘date.fromordinal(d.toordinal()) == d’.

 -- 方法: classmethod date.fromisoformat (date_string)

     Return a *note date: 1b1. corresponding to a 'date_string' given in
     any valid ISO 8601 format, with the following exceptions:

       1. Reduced precision dates are not currently supported
          (‘YYYY-MM’, ‘YYYY’).

       2. Extended date representations are not currently supported
          (‘±YYYYYY-MM-DD’).

       3. Ordinal dates are not currently supported (‘YYYY-OOO’).

     範例：

          >>> from datetime import date
          >>> date.fromisoformat('2019-12-04')
          datetime.date(2019, 12, 4)
          >>> date.fromisoformat('20191204')
          datetime.date(2019, 12, 4)
          >>> date.fromisoformat('2021-W01-1')
          datetime.date(2021, 1, 4)

     在 3.7 版被加入.

     在 3.11 版的變更: Previously, this method only supported the format
     ‘YYYY-MM-DD’.

 -- 方法: classmethod date.fromisocalendar (year, week, day)

     Return a *note date: 1b1. corresponding to the ISO calendar date
     specified by year, week and day.  This is the inverse of the
     function *note date.isocalendar(): 89a.

     在 3.8 版被加入.

類別屬性：

 -- 屬性: date.min

     The earliest representable date, ‘date(MINYEAR, 1, 1)’.

 -- 屬性: date.max

     The latest representable date, ‘date(MAXYEAR, 12, 31)’.

 -- 屬性: date.resolution

     The smallest possible difference between non-equal date objects,
     ‘timedelta(days=1)’.

Instance attributes (read-only):

 -- 屬性: date.year

     Between *note MINYEAR: 2304. and *note MAXYEAR: 2305. inclusive.

 -- 屬性: date.month

     在 1 到 12 （含）之間。

 -- 屬性: date.day

     Between 1 and the number of days in the given month of the given
     year.

Supported operations:

Operation                           Result
                                    
---------------------------------------------------------------------------------------
                                    
‘date2 = date1 + timedelta’         ‘date2’ will be ‘timedelta.days’ days after
                                    ‘date1’.  (1)
                                    
                                    
‘date2 = date1 - timedelta’         Computes ‘date2’ such that ‘date2 + timedelta ==
                                    date1’.  (2)
                                    
                                    
‘timedelta = date1 - date2’         (3)
                                    
                                    
     ‘date1 == date2’               Equality comparison.  (4)
     ‘date1 != date2’               

     ‘date1 < date2’                Order comparison.  (5)
     ‘date1 > date2’                
     ‘date1 <= date2’
     ‘date1 >= date2’

註解：

  1. 'date2' is moved forward in time if ‘timedelta.days > 0’, or
     backward if ‘timedelta.days < 0’.  Afterward ‘date2 - date1 ==
     timedelta.days’.  ‘timedelta.seconds’ and ‘timedelta.microseconds’
     are ignored.  *note OverflowError: 825. is raised if ‘date2.year’
     would be smaller than *note MINYEAR: 2304. or larger than *note
     MAXYEAR: 2305.

  2. ‘timedelta.seconds’ 和 ‘timedelta.microseconds’ 被忽略。

  3. This is exact, and cannot overflow.  ‘timedelta.seconds’ and
     ‘timedelta.microseconds’ are 0, and ‘date2 + timedelta == date1’
     after.

  4. *note date: 1b1. objects are equal if they represent the same date.

     ‘date’ objects that are not also *note datetime: 1b0. instances are
     never equal to ‘datetime’ objects, even if they represent the same
     date.

  5. 'date1' is considered less than 'date2' when 'date1' precedes
     'date2' in time.  In other words, ‘date1 < date2’ if and only if
     ‘date1.toordinal() < date2.toordinal()’.

     Order comparison between a ‘date’ object that is not also a *note
     datetime: 1b0. instance and a ‘datetime’ object raises *note
     TypeError: 4dd.

在 3.13 版的變更: Comparison between *note datetime: 1b0. object and an
instance of the *note date: 1b1. subclass that is not a ‘datetime’
subclass no longer converts the latter to ‘date’, ignoring the time part
and the time zone.  The default behavior can be changed by overriding
the special comparison methods in subclasses.

In Boolean contexts, all *note date: 1b1. objects are considered to be
true.

實例方法：

 -- 方法: date.replace (year=self.year, month=self.month, day=self.day)

     Return a date with the same value, except for those parameters
     given new values by whichever keyword arguments are specified.

     範例：

          >>> from datetime import date
          >>> d = date(2002, 12, 31)
          >>> d.replace(day=26)
          datetime.date(2002, 12, 26)

     *note date: 1b1. objects are also supported by generic function
     *note copy.replace(): 136.

 -- 方法: date.timetuple ()

     回傳一個 *note time.struct_time: c91.，如同 *note time.localtime():
     1467. 所回傳。

     The hours, minutes and seconds are 0, and the DST flag is -1.

     ‘d.timetuple()’ 等價於：

          time.struct_time((d.year, d.month, d.day, 0, 0, 0, d.weekday(), yday, -1))

     where ‘yday = d.toordinal() - date(d.year, 1, 1).toordinal() + 1’
     is the day number within the current year starting with 1 for
     January 1st.

 -- 方法: date.toordinal ()

     Return the proleptic Gregorian ordinal of the date, where January 1
     of year 1 has ordinal 1.  For any *note date: 1b1. object 'd',
     ‘date.fromordinal(d.toordinal()) == d’.

 -- 方法: date.weekday ()

     回傳一個代表星期幾的整數，星期一為 0、星期日為 6。例如 ‘date(2002,
     12, 4).weekday() == 2’ 為星期三。也請參考 *note isoweekday():
     232b.。

 -- 方法: date.isoweekday ()

     Return the day of the week as an integer, where Monday is 1 and
     Sunday is 7.  For example, ‘date(2002, 12, 4).isoweekday() == 3’, a
     Wednesday.  See also *note weekday(): 232a, *note isocalendar():
     89a.

 -- 方法: date.isocalendar ()

     Return a *note named tuple: 5f4. object with three components:
     ‘year’, ‘week’ and ‘weekday’.

     The ISO calendar is a widely used variant of the Gregorian
     calendar.  (2)

     The ISO year consists of 52 or 53 full weeks, and where a week
     starts on a Monday and ends on a Sunday.  The first week of an ISO
     year is the first (Gregorian) calendar week of a year containing a
     Thursday.  This is called week number 1, and the ISO year of that
     Thursday is the same as its Gregorian year.

     For example, 2004 begins on a Thursday, so the first week of ISO
     year 2004 begins on Monday, 29 Dec 2003 and ends on Sunday, 4 Jan
     2004:

          >>> from datetime import date
          >>> date(2003, 12, 29).isocalendar()
          datetime.IsoCalendarDate(year=2004, week=1, weekday=1)
          >>> date(2004, 1, 4).isocalendar()
          datetime.IsoCalendarDate(year=2004, week=1, weekday=7)

     在 3.9 版的變更: Result changed from a tuple to a *note named
     tuple: 5f4.

 -- 方法: date.isoformat ()

     回傳一以 ISO 8601 格式 ‘YYYY-MM-DD’ 表示的日期字串：

          >>> from datetime import date
          >>> date(2002, 12, 4).isoformat()
          '2002-12-04'

 -- 方法: date.__str__ ()

     For a date 'd', ‘str(d)’ is equivalent to ‘d.isoformat()’.

 -- 方法: date.ctime ()

     Return a string representing the date:

          >>> from datetime import date
          >>> date(2002, 12, 4).ctime()
          'Wed Dec  4 00:00:00 2002'

     ‘d.ctime()’ 等價於：

          time.ctime(time.mktime(d.timetuple()))

     on platforms where the native C ‘ctime()’ function (which *note
     time.ctime(): 232f. invokes, but which *note date.ctime(): 232e.
     does not invoke) conforms to the C standard.

 -- 方法: date.strftime (format)

     Return a string representing the date, controlled by an explicit
     format string.  Format codes referring to hours, minutes or seconds
     will see 0 values.  See also *note strftime() 與 strptime() 的行為:
     16ce. and *note date.isoformat(): 232c.

 -- 方法: date.__format__ (format)

     Same as *note date.strftime(): c38.  This makes it possible to
     specify a format string for a *note date: 1b1. object in *note
     formatted string literals: 94d. and when using *note str.format():
     5c7.  See also *note strftime() 與 strptime() 的行為: 16ce. and
     *note date.isoformat(): 232c.

* Menu:

* 用法範例：date::

   ---------- Footnotes ----------

   (1) This matches the definition of the "proleptic Gregorian" calendar
in Dershowitz and Reingold's book 'Calendrical Calculations', where it's
the base calendar for all computations.  See the book for algorithms for
converting between proleptic Gregorian ordinals and many other calendar
systems.

   (2) See R. H. van Gent's guide to the mathematics of the ISO 8601
calendar
(https://web.archive.org/web/20220531051136/https://webspace.science.uu.nl/~gent0113/calendar/isocalendar.htm)
for a good explanation.


File: python.info,  Node: 用法範例：date,  Up: date 物件

5.8.1.9 用法範例：‘date’
........................

計算一個事件的天數的範例：

     >>> import time
     >>> from datetime import date
     >>> today = date.today()
     >>> today
     datetime.date(2007, 12, 5)
     >>> today == date.fromtimestamp(time.time())
     True
     >>> my_birthday = date(today.year, 6, 24)
     >>> if my_birthday < today:
     ...     my_birthday = my_birthday.replace(year=today.year + 1)
     ...
     >>> my_birthday
     datetime.date(2008, 6, 24)
     >>> time_to_birthday = abs(my_birthday - today)
     >>> time_to_birthday.days
     202

更多 *note date: 1b1. 的用法範例：

     >>> from datetime import date
     >>> d = date.fromordinal(730920) # 730920th day after 1. 1. 0001
     >>> d
     datetime.date(2002, 3, 11)

     >>> # Methods related to formatting string output
     >>> d.isoformat()
     '2002-03-11'
     >>> d.strftime("%d/%m/%y")
     '11/03/02'
     >>> d.strftime("%A %d. %B %Y")
     'Monday 11. March 2002'
     >>> d.ctime()
     'Mon Mar 11 00:00:00 2002'
     >>> 'The {1} is {0:%d}, the {2} is {0:%B}.'.format(d, "day", "month")
     'The day is 11, the month is March.'

     >>> # Methods for to extracting 'components' under different calendars
     >>> t = d.timetuple()
     >>> for i in t:
     ...     print(i)
     2002                # year
     3                   # month
     11                  # day
     0
     0
     0
     0                   # weekday (0 = Monday)
     70                  # 70th day in the year
     -1
     >>> ic = d.isocalendar()
     >>> for i in ic:
     ...     print(i)
     2002                # ISO year
     11                  # ISO week number
     1                   # ISO day number ( 1 = Monday )

     >>> # A date object is immutable; all operations produce a new object
     >>> d.replace(year=2005)
     datetime.date(2005, 3, 11)


File: python.info,  Node: datetime 物件,  Next: time 物件,  Prev: date 物件,  Up: datetime --- 日期與時間的基本型別

5.8.1.10 ‘datetime’ 物件
........................

A *note datetime: 1b0. object is a single object containing all the
information from a *note date: 1b1. object and a *note time: 1b2.
object.

Like a *note date: 1b1. object, *note datetime: 1b0. assumes the current
Gregorian calendar extended in both directions; like a *note time: 1b2.
object, *note datetime: 1b0. assumes there are exactly 3600*24 seconds
in every day.

Constructor:

 -- 類別: datetime.datetime (year, month, day, hour=0, minute=0,
          second=0, microsecond=0, tzinfo=None, *, fold=0)

     The 'year', 'month' and 'day' arguments are required.  'tzinfo' may
     be ‘None’, or an instance of a *note tzinfo: 582. subclass.  The
     remaining arguments must be integers in the following ranges:

        * ‘MINYEAR <= year <= MAXYEAR’,

        * ‘1 <= month <= 12’,

        * ‘1 <= day <= number of days in the given month and year’,

        * ‘0 <= hour < 24’,

        * ‘0 <= minute < 60’,

        * ‘0 <= second < 60’,

        * ‘0 <= microsecond < 1000000’,

        * ‘fold in [0, 1]’.

     If an argument outside those ranges is given, *note ValueError:
     1e7. is raised.

     在 3.6 版的變更: 新增 'fold' 參數。

Other constructors, all class methods:

 -- 方法: classmethod datetime.today ()

     回傳目前的本地日期與時間，且 *note tzinfo: 2316. 為 ‘None’。

     等價於：

          datetime.fromtimestamp(time.time())

     也請見 *note now(): 494.、*note fromtimestamp(): 495.。

     This method is functionally equivalent to *note now(): 494, but
     without a ‘tz’ parameter.

 -- 方法: classmethod datetime.now (tz=None)

     Return the current local date and time.

     如果選用的引數 'tz' 為 ‘None’ 或未指定，則會像是 *note today():
     2334.，但盡可能提供比透過 *note time.time(): 239. 取得的時間戳記更
     多位數的資訊（例如，這在有提供 C ‘gettimeofday()’ 函式的平台上可能
     可行）。

     If 'tz' is not ‘None’, it must be an instance of a *note tzinfo:
     582. subclass, and the current date and time are converted to
     'tz'’s time zone.

     This function is preferred over *note today(): 2334. and *note
     utcnow(): 2cd.

 -- 方法: classmethod datetime.utcnow ()

     Return the current UTC date and time, with *note tzinfo: 2316.
     ‘None’.

     This is like *note now(): 494, but returns the current UTC date and
     time, as a naive *note datetime: 1b0. object.  An aware current UTC
     datetime can be obtained by calling ‘datetime.now(timezone.utc)’.
     See also *note now(): 494.

          警告: Because naive ‘datetime’ objects are treated by many
          ‘datetime’ methods as local times, it is preferred to use
          aware datetimes to represent times in UTC. As such, the
          recommended way to create an object representing the current
          time in UTC is by calling ‘datetime.now(timezone.utc)’.

     在 3.12 版之後被棄用: Use *note datetime.now(): 494. with *note
     UTC: 496. instead.

 -- 方法: classmethod datetime.fromtimestamp (timestamp, tz=None)

     Return the local date and time corresponding to the POSIX
     timestamp, such as is returned by *note time.time(): 239.  If
     optional argument 'tz' is ‘None’ or not specified, the timestamp is
     converted to the platform's local date and time, and the returned
     *note datetime: 1b0. object is naive.

     If 'tz' is not ‘None’, it must be an instance of a *note tzinfo:
     582. subclass, and the timestamp is converted to 'tz'’s time zone.

     *note fromtimestamp(): 495. may raise *note OverflowError: 825, if
     the timestamp is out of the range of values supported by the
     platform C ‘localtime()’ or ‘gmtime()’ functions, and *note
     OSError: 350. on ‘localtime()’ or ‘gmtime()’ failure.  It's common
     for this to be restricted to years in 1970 through 2038.  Note that
     on non-POSIX systems that include leap seconds in their notion of a
     timestamp, leap seconds are ignored by *note fromtimestamp(): 495,
     and then it's possible to have two timestamps differing by a second
     that yield identical *note datetime: 1b0. objects.  This method is
     preferred over *note utcfromtimestamp(): 2ce.

     在 3.3 版的變更: Raise *note OverflowError: 825. instead of *note
     ValueError: 1e7. if the timestamp is out of the range of values
     supported by the platform C ‘localtime()’ or ‘gmtime()’ functions.
     Raise *note OSError: 350. instead of *note ValueError: 1e7. on
     ‘localtime()’ or ‘gmtime()’ failure.

     在 3.6 版的變更: *note fromtimestamp(): 495. may return instances
     with *note fold: bfe. set to 1.

 -- 方法: classmethod datetime.utcfromtimestamp (timestamp)

     Return the UTC *note datetime: 1b0. corresponding to the POSIX
     timestamp, with *note tzinfo: 2316. ‘None’.  (The resulting object
     is naive.)

     This may raise *note OverflowError: 825, if the timestamp is out of
     the range of values supported by the platform C ‘gmtime()’
     function, and *note OSError: 350. on ‘gmtime()’ failure.  It's
     common for this to be restricted to years in 1970 through 2038.

     To get an aware *note datetime: 1b0. object, call *note
     fromtimestamp(): 495.:

          datetime.fromtimestamp(timestamp, timezone.utc)

     On the POSIX compliant platforms, it is equivalent to the following
     expression:

          datetime(1970, 1, 1, tzinfo=timezone.utc) + timedelta(seconds=timestamp)

     except the latter formula always supports the full years range:
     between *note MINYEAR: 2304. and *note MAXYEAR: 2305. inclusive.

          警告: Because naive ‘datetime’ objects are treated by many
          ‘datetime’ methods as local times, it is preferred to use
          aware datetimes to represent times in UTC. As such, the
          recommended way to create an object representing a specific
          timestamp in UTC is by calling
          ‘datetime.fromtimestamp(timestamp, tz=timezone.utc)’.

     在 3.3 版的變更: Raise *note OverflowError: 825. instead of *note
     ValueError: 1e7. if the timestamp is out of the range of values
     supported by the platform C ‘gmtime()’ function.  Raise *note
     OSError: 350. instead of *note ValueError: 1e7. on ‘gmtime()’
     failure.

     在 3.12 版之後被棄用: Use *note datetime.fromtimestamp(): 495. with
     *note UTC: 496. instead.

 -- 方法: classmethod datetime.fromordinal (ordinal)

     Return the *note datetime: 1b0. corresponding to the proleptic
     Gregorian ordinal, where January 1 of year 1 has ordinal 1.  *note
     ValueError: 1e7. is raised unless ‘1 <= ordinal <=
     datetime.max.toordinal()’.  The hour, minute, second and
     microsecond of the result are all 0, and *note tzinfo: 2316. is
     ‘None’.

 -- 方法: classmethod datetime.combine (date, time, tzinfo=time.tzinfo)

     Return a new *note datetime: 1b0. object whose date components are
     equal to the given *note date: 1b1. object's, and whose time
     components are equal to the given *note time: 1b2. object's.  If
     the 'tzinfo' argument is provided, its value is used to set the
     *note tzinfo: 2316. attribute of the result, otherwise the *note
     tzinfo: 230e. attribute of the 'time' argument is used.  If the
     'date' argument is a *note datetime: 1b0. object, its time
     components and *note tzinfo: 2316. attributes are ignored.

     For any *note datetime: 1b0. object 'd', ‘d ==
     datetime.combine(d.date(), d.time(), d.tzinfo)’.

     在 3.6 版的變更: 新增 'tzinfo' 引數。

 -- 方法: classmethod datetime.fromisoformat (date_string)

     Return a *note datetime: 1b0. corresponding to a 'date_string' in
     any valid ISO 8601 format, with the following exceptions:

       1. Time zone offsets may have fractional seconds.

       2. The ‘T’ separator may be replaced by any single unicode
          character.

       3. Fractional hours and minutes are not supported.

       4. Reduced precision dates are not currently supported
          (‘YYYY-MM’, ‘YYYY’).

       5. Extended date representations are not currently supported
          (‘±YYYYYY-MM-DD’).

       6. Ordinal dates are not currently supported (‘YYYY-OOO’).

     範例：

          >>> from datetime import datetime
          >>> datetime.fromisoformat('2011-11-04')
          datetime.datetime(2011, 11, 4, 0, 0)
          >>> datetime.fromisoformat('20111104')
          datetime.datetime(2011, 11, 4, 0, 0)
          >>> datetime.fromisoformat('2011-11-04T00:05:23')
          datetime.datetime(2011, 11, 4, 0, 5, 23)
          >>> datetime.fromisoformat('2011-11-04T00:05:23Z')
          datetime.datetime(2011, 11, 4, 0, 5, 23, tzinfo=datetime.timezone.utc)
          >>> datetime.fromisoformat('20111104T000523')
          datetime.datetime(2011, 11, 4, 0, 5, 23)
          >>> datetime.fromisoformat('2011-W01-2T00:05:23.283')
          datetime.datetime(2011, 1, 4, 0, 5, 23, 283000)
          >>> datetime.fromisoformat('2011-11-04 00:05:23.283')
          datetime.datetime(2011, 11, 4, 0, 5, 23, 283000)
          >>> datetime.fromisoformat('2011-11-04 00:05:23.283+00:00')
          datetime.datetime(2011, 11, 4, 0, 5, 23, 283000, tzinfo=datetime.timezone.utc)
          >>> datetime.fromisoformat('2011-11-04T00:05:23+04:00')
          datetime.datetime(2011, 11, 4, 0, 5, 23,
              tzinfo=datetime.timezone(datetime.timedelta(seconds=14400)))

     在 3.7 版被加入.

     在 3.11 版的變更: Previously, this method only supported formats
     that could be emitted by *note date.isoformat(): 232c. or *note
     datetime.isoformat(): ad4.

 -- 方法: classmethod datetime.fromisocalendar (year, week, day)

     Return a *note datetime: 1b0. corresponding to the ISO calendar
     date specified by year, week and day.  The non-date components of
     the datetime are populated with their normal default values.  This
     is the inverse of the function *note datetime.isocalendar(): 89b.

     在 3.8 版被加入.

 -- 方法: classmethod datetime.strptime (date_string, format)

     Return a *note datetime: 1b0. corresponding to 'date_string',
     parsed according to 'format'.

     If 'format' does not contain microseconds or time zone information,
     this is equivalent to:

          datetime(*(time.strptime(date_string, format)[0:6]))

     *note ValueError: 1e7. is raised if the date_string and format
     can't be parsed by *note time.strptime(): 139a. or if it returns a
     value which isn't a time tuple.  See also *note strftime() 與
     strptime() 的行為: 16ce. and *note datetime.fromisoformat(): 5bc.

     在 3.13 版的變更: If 'format' specifies a day of month without a
     year a *note DeprecationWarning: 18b. is now emitted.  This is to
     avoid a quadrennial leap year bug in code seeking to parse only a
     month and day as the default year used in absence of one in the
     format is not a leap year.  Such 'format' values may raise an error
     as of Python 3.15.  The workaround is to always include a year in
     your 'format'.  If parsing 'date_string' values that do not have a
     year, explicitly add a year that is a leap year before parsing:

          >>> from datetime import datetime
          >>> date_string = "02/29"
          >>> when = datetime.strptime(f"{date_string};1984", "%m/%d;%Y")  # Avoids leap year bug.
          >>> when.strftime("%B %d")
          'February 29'

類別屬性：

 -- 屬性: datetime.min

     The earliest representable *note datetime: 1b0, ‘datetime(MINYEAR,
     1, 1, tzinfo=None)’.

 -- 屬性: datetime.max

     The latest representable *note datetime: 1b0, ‘datetime(MAXYEAR,
     12, 31, 23, 59, 59, 999999, tzinfo=None)’.

 -- 屬性: datetime.resolution

     The smallest possible difference between non-equal *note datetime:
     1b0. objects, ‘timedelta(microseconds=1)’.

Instance attributes (read-only):

 -- 屬性: datetime.year

     Between *note MINYEAR: 2304. and *note MAXYEAR: 2305. inclusive.

 -- 屬性: datetime.month

     在 1 到 12 （含）之間。

 -- 屬性: datetime.day

     Between 1 and the number of days in the given month of the given
     year.

 -- 屬性: datetime.hour

     In ‘range(24)’.

 -- 屬性: datetime.minute

     In ‘range(60)’.

 -- 屬性: datetime.second

     In ‘range(60)’.

 -- 屬性: datetime.microsecond

     In ‘range(1000000)’.

 -- 屬性: datetime.tzinfo

     The object passed as the 'tzinfo' argument to the *note datetime:
     1b0. constructor, or ‘None’ if none was passed.

 -- 屬性: datetime.fold

     In ‘[0, 1]’.  Used to disambiguate wall times during a repeated
     interval.  (A repeated interval occurs when clocks are rolled back
     at the end of daylight saving time or when the UTC offset for the
     current zone is decreased for political reasons.)  The values 0 and
     1 represent, respectively, the earlier and later of the two moments
     with the same wall time representation.

     在 3.6 版被加入.

Supported operations:

Operation                                   Result
                                            
---------------------------------------------------------------------------------
                                            
‘datetime2 = datetime1 + timedelta’         (1)
                                            
                                            
‘datetime2 = datetime1 - timedelta’         (2)
                                            
                                            
‘timedelta = datetime1 - datetime2’         (3)
                                            
                                            
     ‘datetime1 == datetime2’               Equality comparison.  (4)
     ‘datetime1 != datetime2’               

     ‘datetime1 < datetime2’                Order comparison.  (5)
     ‘datetime1 > datetime2’                
     ‘datetime1 <= datetime2’
     ‘datetime1 >= datetime2’

  1. ‘datetime2’ is a duration of ‘timedelta’ removed from ‘datetime1’,
     moving forward in time if ‘timedelta.days > 0’, or backward if
     ‘timedelta.days < 0’.  The result has the same *note tzinfo: 2316.
     attribute as the input datetime, and ‘datetime2 - datetime1 ==
     timedelta’ after.  *note OverflowError: 825. is raised if
     ‘datetime2.year’ would be smaller than *note MINYEAR: 2304. or
     larger than *note MAXYEAR: 2305.  Note that no time zone
     adjustments are done even if the input is an aware object.

  2. Computes the ‘datetime2’ such that ‘datetime2 + timedelta ==
     datetime1’.  As for addition, the result has the same *note tzinfo:
     2316. attribute as the input datetime, and no time zone adjustments
     are done even if the input is aware.

  3. Subtraction of a *note datetime: 1b0. from a *note datetime: 1b0.
     is defined only if both operands are naive, or if both are aware.
     If one is aware and the other is naive, *note TypeError: 4dd. is
     raised.

     If both are naive, or both are aware and have the same *note
     tzinfo: 2316. attribute, the *note tzinfo: 2316. attributes are
     ignored, and the result is a *note timedelta: 973. object 't' such
     that ‘datetime2 + t == datetime1’.  No time zone adjustments are
     done in this case.

     If both are aware and have different *note tzinfo: 2316.
     attributes, ‘a-b’ acts as if 'a' and 'b' were first converted to
     naive UTC datetimes.  The result is ‘(a.replace(tzinfo=None) -
     a.utcoffset()) - (b.replace(tzinfo=None) - b.utcoffset())’ except
     that the implementation never overflows.

  4. *note datetime: 1b0. objects are equal if they represent the same
     date and time, taking into account the time zone.

     Naive and aware ‘datetime’ objects are never equal.

     If both comparands are aware, and have the same ‘tzinfo’ attribute,
     the ‘tzinfo’ and *note fold: bfe. attributes are ignored and the
     base datetimes are compared.  If both comparands are aware and have
     different *note tzinfo: 2316. attributes, the comparison acts as
     comparands were first converted to UTC datetimes except that the
     implementation never overflows.  ‘datetime’ instances in a repeated
     interval are never equal to ‘datetime’ instances in other time
     zone.

  5. 'datetime1' is considered less than 'datetime2' when 'datetime1'
     precedes 'datetime2' in time, taking into account the time zone.

     Order comparison between naive and aware *note datetime: 1b0.
     objects raises *note TypeError: 4dd.

     If both comparands are aware, and have the same ‘tzinfo’ attribute,
     the ‘tzinfo’ and *note fold: bfe. attributes are ignored and the
     base datetimes are compared.  If both comparands are aware and have
     different *note tzinfo: 2316. attributes, the comparison acts as
     comparands were first converted to UTC datetimes except that the
     implementation never overflows.

在 3.3 版的變更: Equality comparisons between aware and naive *note
datetime: 1b0. instances don't raise *note TypeError: 4dd.

在 3.13 版的變更: Comparison between *note datetime: 1b0. object and an
instance of the *note date: 1b1. subclass that is not a ‘datetime’
subclass no longer converts the latter to ‘date’, ignoring the time part
and the time zone.  The default behavior can be changed by overriding
the special comparison methods in subclasses.

實例方法：

 -- 方法: datetime.date ()

     Return *note date: 1b1. object with same year, month and day.

 -- 方法: datetime.time ()

     Return *note time: 1b2. object with same hour, minute, second,
     microsecond and fold.  *note tzinfo: 2316. is ‘None’.  See also
     method *note timetz(): 233a.

     在 3.6 版的變更: The fold value is copied to the returned *note
     time: 1b2. object.

 -- 方法: datetime.timetz ()

     Return *note time: 1b2. object with same hour, minute, second,
     microsecond, fold, and tzinfo attributes.  See also method *note
     time(): d7.

     在 3.6 版的變更: The fold value is copied to the returned *note
     time: 1b2. object.

 -- 方法: datetime.replace (year=self.year, month=self.month,
          day=self.day, hour=self.hour, minute=self.minute,
          second=self.second, microsecond=self.microsecond,
          tzinfo=self.tzinfo, *, fold=0)

     Return a datetime with the same attributes, except for those
     attributes given new values by whichever keyword arguments are
     specified.  Note that ‘tzinfo=None’ can be specified to create a
     naive datetime from an aware datetime with no conversion of date
     and time data.

     *note datetime: 1b0. objects are also supported by generic function
     *note copy.replace(): 136.

     在 3.6 版的變更: 新增 'fold' 參數。

 -- 方法: datetime.astimezone (tz=None)

     Return a *note datetime: 1b0. object with new *note tzinfo: 2316.
     attribute 'tz', adjusting the date and time data so the result is
     the same UTC time as 'self', but in 'tz"s local time.

     If provided, 'tz' must be an instance of a *note tzinfo: 582.
     subclass, and its *note utcoffset(): 233b. and *note dst(): 233c.
     methods must not return ‘None’.  If 'self' is naive, it is presumed
     to represent time in the system time zone.

     If called without arguments (or with ‘tz=None’) the system local
     time zone is assumed for the target time zone.  The ‘.tzinfo’
     attribute of the converted datetime instance will be set to an
     instance of *note timezone: 1059. with the zone name and offset
     obtained from the OS.

     If ‘self.tzinfo’ is 'tz', ‘self.astimezone(tz)’ is equal to 'self':
     no adjustment of date or time data is performed.  Else the result
     is local time in the time zone 'tz', representing the same UTC time
     as 'self': after ‘astz = dt.astimezone(tz)’, ‘astz -
     astz.utcoffset()’ will have the same date and time data as ‘dt -
     dt.utcoffset()’.

     If you merely want to attach a *note timezone: 1059. object 'tz' to
     a datetime 'dt' without adjustment of date and time data, use
     ‘dt.replace(tzinfo=tz)’.  If you merely want to remove the
     ‘timezone’ object from an aware datetime 'dt' without conversion of
     date and time data, use ‘dt.replace(tzinfo=None)’.

     Note that the default *note tzinfo.fromutc(): 233d. method can be
     overridden in a *note tzinfo: 582. subclass to affect the result
     returned by *note astimezone(): 974.  Ignoring error cases, *note
     astimezone(): 974. acts like:

          def astimezone(self, tz):
              if self.tzinfo is tz:
                  return self
              # Convert self to UTC, and attach the new timezone object.
              utc = (self - self.utcoffset()).replace(tzinfo=tz)
              # Convert from UTC to tz's local time.
              return tz.fromutc(utc)

     在 3.3 版的變更: 'tz' now can be omitted.

     在 3.6 版的變更: The *note astimezone(): 974. method can now be
     called on naive instances that are presumed to represent system
     local time.

 -- 方法: datetime.utcoffset ()

     If *note tzinfo: 2316. is ‘None’, returns ‘None’, else returns
     ‘self.tzinfo.utcoffset(self)’, and raises an exception if the
     latter doesn't return ‘None’ or a *note timedelta: 973. object with
     magnitude less than one day.

     在 3.7 版的變更: The UTC offset is not restricted to a whole number
     of minutes.

 -- 方法: datetime.dst ()

     If *note tzinfo: 2316. is ‘None’, returns ‘None’, else returns
     ‘self.tzinfo.dst(self)’, and raises an exception if the latter
     doesn't return ‘None’ or a *note timedelta: 973. object with
     magnitude less than one day.

     在 3.7 版的變更: The DST offset is not restricted to a whole number
     of minutes.

 -- 方法: datetime.tzname ()

     If *note tzinfo: 2316. is ‘None’, returns ‘None’, else returns
     ‘self.tzinfo.tzname(self)’, raises an exception if the latter
     doesn't return ‘None’ or a string object,

 -- 方法: datetime.timetuple ()

     回傳一個 *note time.struct_time: c91.，如同 *note time.localtime():
     1467. 所回傳。

     ‘d.timetuple()’ 等價於：

          time.struct_time((d.year, d.month, d.day,
                            d.hour, d.minute, d.second,
                            d.weekday(), yday, dst))

     where ‘yday = d.toordinal() - date(d.year, 1, 1).toordinal() + 1’
     is the day number within the current year starting with 1 for
     January 1st.  The *note tm_isdst: 2340. flag of the result is set
     according to the *note dst(): 233c. method: *note tzinfo: 2316. is
     ‘None’ or *note dst(): 233c. returns ‘None’, ‘tm_isdst’ is set to
     ‘-1’; else if *note dst(): 233c. returns a non-zero value,
     ‘tm_isdst’ is set to 1; else ‘tm_isdst’ is set to 0.

 -- 方法: datetime.utctimetuple ()

     If *note datetime: 1b0. instance 'd' is naive, this is the same as
     ‘d.timetuple()’ except that *note tm_isdst: 2340. is forced to 0
     regardless of what ‘d.dst()’ returns.  DST is never in effect for a
     UTC time.

     If 'd' is aware, 'd' is normalized to UTC time, by subtracting
     ‘d.utcoffset()’, and a *note time.struct_time: c91. for the
     normalized time is returned.  ‘tm_isdst’ is forced to 0.  Note that
     an *note OverflowError: 825. may be raised if ‘d.year’ was
     ‘MINYEAR’ or ‘MAXYEAR’ and UTC adjustment spills over a year
     boundary.

          警告: Because naive ‘datetime’ objects are treated by many
          ‘datetime’ methods as local times, it is preferred to use
          aware datetimes to represent times in UTC; as a result, using
          *note datetime.utctimetuple(): 2341. may give misleading
          results.  If you have a naive ‘datetime’ representing UTC, use
          ‘datetime.replace(tzinfo=timezone.utc)’ to make it aware, at
          which point you can use *note datetime.timetuple(): 233f.

 -- 方法: datetime.toordinal ()

     Return the proleptic Gregorian ordinal of the date.  The same as
     ‘self.date().toordinal()’.

 -- 方法: datetime.timestamp ()

     Return POSIX timestamp corresponding to the *note datetime: 1b0.
     instance.  The return value is a *note float: 2c8. similar to that
     returned by *note time.time(): 239.

     Naive *note datetime: 1b0. instances are assumed to represent local
     time and this method relies on the platform C ‘mktime()’ function
     to perform the conversion.  Since *note datetime: 1b0. supports
     wider range of values than ‘mktime()’ on many platforms, this
     method may raise *note OverflowError: 825. or *note OSError: 350.
     for times far in the past or far in the future.

     For aware *note datetime: 1b0. instances, the return value is
     computed as:

          (dt - datetime(1970, 1, 1, tzinfo=timezone.utc)).total_seconds()

     在 3.3 版被加入.

     在 3.6 版的變更: The *note timestamp(): 103b. method uses the *note
     fold: bfe. attribute to disambiguate the times during a repeated
     interval.

          備註: There is no method to obtain the POSIX timestamp
          directly from a naive *note datetime: 1b0. instance
          representing UTC time.  If your application uses this
          convention and your system time zone is not set to UTC, you
          can obtain the POSIX timestamp by supplying
          ‘tzinfo=timezone.utc’:

               timestamp = dt.replace(tzinfo=timezone.utc).timestamp()

          or by calculating the timestamp directly:

               timestamp = (dt - datetime(1970, 1, 1)) / timedelta(seconds=1)

 -- 方法: datetime.weekday ()

     Return the day of the week as an integer, where Monday is 0 and
     Sunday is 6.  The same as ‘self.date().weekday()’.  See also *note
     isoweekday(): 2344.

 -- 方法: datetime.isoweekday ()

     Return the day of the week as an integer, where Monday is 1 and
     Sunday is 7.  The same as ‘self.date().isoweekday()’.  See also
     *note weekday(): 2343, *note isocalendar(): 89b.

 -- 方法: datetime.isocalendar ()

     Return a *note named tuple: 5f4. with three components: ‘year’,
     ‘week’ and ‘weekday’.  The same as ‘self.date().isocalendar()’.

 -- 方法: datetime.isoformat (sep='T', timespec='auto')

     Return a string representing the date and time in ISO 8601 format:

        - ‘YYYY-MM-DDTHH:MM:SS.ffffff’，如果 *note microsecond: 2315. 不
          是 0

        - ‘YYYY-MM-DDTHH:MM:SS’，如果 *note microsecond: 2315. 是 0

     如果 *note utcoffset(): 233b. 没有回傳 ‘None’，則會附加一个字串，給
     出 UTC 偏移：

        - ‘YYYY-MM-DDTHH:MM:SS.ffffff+HH:MM[:SS[.ffffff]]’，如果 *note
          microsecond: 2315. 不是 0

        - ‘YYYY-MM-DDTHH:MM:SS+HH:MM[:SS[.ffffff]]’，如果 *note
          microsecond: 2315. 是 0

     範例：

          >>> from datetime import datetime, timezone
          >>> datetime(2019, 5, 18, 15, 17, 8, 132263).isoformat()
          '2019-05-18T15:17:08.132263'
          >>> datetime(2019, 5, 18, 15, 17, tzinfo=timezone.utc).isoformat()
          '2019-05-18T15:17:00+00:00'

     The optional argument 'sep' (default ‘'T'’) is a one-character
     separator, placed between the date and time portions of the result.
     For example:

          >>> from datetime import tzinfo, timedelta, datetime
          >>> class TZ(tzinfo):
          ...     """A time zone with an arbitrary, constant -06:39 offset."""
          ...     def utcoffset(self, dt):
          ...         return timedelta(hours=-6, minutes=-39)
          ...
          >>> datetime(2002, 12, 25, tzinfo=TZ()).isoformat(' ')
          '2002-12-25 00:00:00-06:39'
          >>> datetime(2009, 11, 27, microsecond=100, tzinfo=TZ()).isoformat()
          '2009-11-27T00:00:00.000100-06:39'

     The optional argument 'timespec' specifies the number of additional
     components of the time to include (the default is ‘'auto'’).  It
     can be one of the following:

        - ‘'auto'’: Same as ‘'seconds'’ if *note microsecond: 2315. is
          0, same as ‘'microseconds'’ otherwise.

        - ‘'hours'’: Include the *note hour: 2312. in the two-digit ‘HH’
          format.

        - ‘'minutes'’: Include *note hour: 2312. and *note minute: 2313.
          in ‘HH:MM’ format.

        - ‘'seconds'’: Include *note hour: 2312, *note minute: 2313, and
          *note second: 2314. in ‘HH:MM:SS’ format.

        - ‘'milliseconds'’: Include full time, but truncate fractional
          second part to milliseconds.  ‘HH:MM:SS.sss’ format.

        - ‘'microseconds'’: Include full time in ‘HH:MM:SS.ffffff’
          format.

          備註: Excluded time components are truncated, not rounded.

     *note ValueError: 1e7. will be raised on an invalid 'timespec'
     argument:

          >>> from datetime import datetime
          >>> datetime.now().isoformat(timespec='minutes')
          '2002-12-25T00:00'
          >>> dt = datetime(2015, 1, 1, 12, 30, 59, 0)
          >>> dt.isoformat(timespec='microseconds')
          '2015-01-01T12:30:59.000000'

     在 3.6 版的變更: 新增 'timespec' 參數。

 -- 方法: datetime.__str__ ()

     For a *note datetime: 1b0. instance 'd', ‘str(d)’ is equivalent to
     ‘d.isoformat(' ')’.

 -- 方法: datetime.ctime ()

     Return a string representing the date and time:

          >>> from datetime import datetime
          >>> datetime(2002, 12, 4, 20, 30, 40).ctime()
          'Wed Dec  4 20:30:40 2002'

     The output string will 'not' include time zone information,
     regardless of whether the input is aware or naive.

     ‘d.ctime()’ 等價於：

          time.ctime(time.mktime(d.timetuple()))

     on platforms where the native C ‘ctime()’ function (which *note
     time.ctime(): 232f. invokes, but which *note datetime.ctime():
     2346. does not invoke) conforms to the C standard.

 -- 方法: datetime.strftime (format)

     Return a string representing the date and time, controlled by an
     explicit format string.  See also *note strftime() 與 strptime()
     的行為: 16ce. and *note datetime.isoformat(): ad4.

 -- 方法: datetime.__format__ (format)

     Same as *note datetime.strftime(): c37.  This makes it possible to
     specify a format string for a *note datetime: 1b0. object in *note
     formatted string literals: 94d. and when using *note str.format():
     5c7.  See also *note strftime() 與 strptime() 的行為: 16ce. and
     *note datetime.isoformat(): ad4.

* Menu:

* 用法範例：datetime::


File: python.info,  Node: 用法範例：datetime,  Up: datetime 物件

5.8.1.11 用法範例：‘datetime’
.............................

更多 *note datetime: 1b0. 的用法範例：

     >>> from datetime import datetime, date, time, timezone

     >>> # Using datetime.combine()
     >>> d = date(2005, 7, 14)
     >>> t = time(12, 30)
     >>> datetime.combine(d, t)
     datetime.datetime(2005, 7, 14, 12, 30)

     >>> # Using datetime.now()
     >>> datetime.now()
     datetime.datetime(2007, 12, 6, 16, 29, 43, 79043)   # GMT +1
     >>> datetime.now(timezone.utc)
     datetime.datetime(2007, 12, 6, 15, 29, 43, 79060, tzinfo=datetime.timezone.utc)

     >>> # Using datetime.strptime()
     >>> dt = datetime.strptime("21/11/06 16:30", "%d/%m/%y %H:%M")
     >>> dt
     datetime.datetime(2006, 11, 21, 16, 30)

     >>> # Using datetime.timetuple() to get tuple of all attributes
     >>> tt = dt.timetuple()
     >>> for it in tt:
     ...     print(it)
     ...
     2006    # year
     11      # month
     21      # day
     16      # hour
     30      # minute
     0       # second
     1       # weekday (0 = Monday)
     325     # number of days since 1st January
     -1      # dst - method tzinfo.dst() returned None

     >>> # Date in ISO format
     >>> ic = dt.isocalendar()
     >>> for it in ic:
     ...     print(it)
     ...
     2006    # ISO year
     47      # ISO week
     2       # ISO weekday

     >>> # Formatting a datetime
     >>> dt.strftime("%A, %d. %B %Y %I:%M%p")
     'Tuesday, 21. November 2006 04:30PM'
     >>> 'The {1} is {0:%d}, the {2} is {0:%B}, the {3} is {0:%I:%M%p}.'.format(dt, "day", "month", "time")
     'The day is 21, the month is November, the time is 04:30PM.'

The example below defines a *note tzinfo: 582. subclass capturing time
zone information for Kabul, Afghanistan, which used +4 UTC until 1945
and then +4:30 UTC thereafter:

     from datetime import timedelta, datetime, tzinfo, timezone

     class KabulTz(tzinfo):
         # Kabul used +4 until 1945, when they moved to +4:30
         UTC_MOVE_DATE = datetime(1944, 12, 31, 20, tzinfo=timezone.utc)

         def utcoffset(self, dt):
             if dt.year < 1945:
                 return timedelta(hours=4)
             elif (1945, 1, 1, 0, 0) <= dt.timetuple()[:5] < (1945, 1, 1, 0, 30):
                 # An ambiguous ("imaginary") half-hour range representing
                 # a 'fold' in time due to the shift from +4 to +4:30.
                 # If dt falls in the imaginary range, use fold to decide how
                 # to resolve. See PEP495.
                 return timedelta(hours=4, minutes=(30 if dt.fold else 0))
             else:
                 return timedelta(hours=4, minutes=30)

         def fromutc(self, dt):
             # Follow same validations as in datetime.tzinfo
             if not isinstance(dt, datetime):
                 raise TypeError("fromutc() requires a datetime argument")
             if dt.tzinfo is not self:
                 raise ValueError("dt.tzinfo is not self")

             # A custom implementation is required for fromutc as
             # the input to this function is a datetime with utc values
             # but with a tzinfo set to self.
             # See datetime.astimezone or fromtimestamp.
             if dt.replace(tzinfo=timezone.utc) >= self.UTC_MOVE_DATE:
                 return dt + timedelta(hours=4, minutes=30)
             else:
                 return dt + timedelta(hours=4)

         def dst(self, dt):
             # Kabul does not observe daylight saving time.
             return timedelta(0)

         def tzname(self, dt):
             if dt >= self.UTC_MOVE_DATE:
                 return "+04:30"
             return "+04"

Usage of ‘KabulTz’ from above:

     >>> tz1 = KabulTz()

     >>> # Datetime before the change
     >>> dt1 = datetime(1900, 11, 21, 16, 30, tzinfo=tz1)
     >>> print(dt1.utcoffset())
     4:00:00

     >>> # Datetime after the change
     >>> dt2 = datetime(2006, 6, 14, 13, 0, tzinfo=tz1)
     >>> print(dt2.utcoffset())
     4:30:00

     >>> # Convert datetime to another time zone
     >>> dt3 = dt2.astimezone(timezone.utc)
     >>> dt3
     datetime.datetime(2006, 6, 14, 8, 30, tzinfo=datetime.timezone.utc)
     >>> dt2
     datetime.datetime(2006, 6, 14, 13, 0, tzinfo=KabulTz())
     >>> dt2 == dt3
     True


File: python.info,  Node: time 物件,  Next: tzinfo 物件,  Prev: datetime 物件,  Up: datetime --- 日期與時間的基本型別

5.8.1.12 ‘time’ 物件
....................

A *note time: 1b2. object represents a (local) time of day, independent
of any particular day, and subject to adjustment via a *note tzinfo:
582. object.

 -- 類別: datetime.time (hour=0, minute=0, second=0, microsecond=0,
          tzinfo=None, *, fold=0)

     All arguments are optional.  'tzinfo' may be ‘None’, or an instance
     of a *note tzinfo: 582. subclass.  The remaining arguments must be
     integers in the following ranges:

        * ‘0 <= hour < 24’,

        * ‘0 <= minute < 60’,

        * ‘0 <= second < 60’,

        * ‘0 <= microsecond < 1000000’,

        * ‘fold in [0, 1]’.

     If an argument outside those ranges is given, *note ValueError:
     1e7. is raised.  All default to 0 except 'tzinfo', which defaults
     to ‘None’.

類別屬性：

 -- 屬性: time.min

     The earliest representable *note time: 1b2, ‘time(0, 0, 0, 0)’.

 -- 屬性: time.max

     The latest representable *note time: 1b2, ‘time(23, 59, 59,
     999999)’.

 -- 屬性: time.resolution

     The smallest possible difference between non-equal *note time: 1b2.
     objects, ‘timedelta(microseconds=1)’, although note that arithmetic
     on *note time: 1b2. objects is not supported.

Instance attributes (read-only):

 -- 屬性: time.hour

     In ‘range(24)’.

 -- 屬性: time.minute

     In ‘range(60)’.

 -- 屬性: time.second

     In ‘range(60)’.

 -- 屬性: time.microsecond

     In ‘range(1000000)’.

 -- 屬性: time.tzinfo

     The object passed as the tzinfo argument to the *note time: 1b2.
     constructor, or ‘None’ if none was passed.

 -- 屬性: time.fold

     In ‘[0, 1]’.  Used to disambiguate wall times during a repeated
     interval.  (A repeated interval occurs when clocks are rolled back
     at the end of daylight saving time or when the UTC offset for the
     current zone is decreased for political reasons.)  The values 0 and
     1 represent, respectively, the earlier and later of the two moments
     with the same wall time representation.

     在 3.6 版被加入.

*note time: 1b2. objects support equality and order comparisons, where
'a' is considered less than 'b' when 'a' precedes 'b' in time.

Naive and aware ‘time’ objects are never equal.  Order comparison
between naive and aware ‘time’ objects raises *note TypeError: 4dd.

If both comparands are aware, and have the same *note tzinfo: 230e.
attribute, the ‘tzinfo’ and ‘fold’ attributes are ignored and the base
times are compared.  If both comparands are aware and have different
‘tzinfo’ attributes, the comparands are first adjusted by subtracting
their UTC offsets (obtained from ‘self.utcoffset()’).

在 3.3 版的變更: Equality comparisons between aware and naive *note
time: 1b2. instances don't raise *note TypeError: 4dd.

In Boolean contexts, a *note time: 1b2. object is always considered to
be true.

在 3.5 版的變更: Before Python 3.5, a *note time: 1b2. object was
considered to be false if it represented midnight in UTC. This behavior
was considered obscure and error-prone and has been removed in Python
3.5.  See bpo-13936(1) for full details.

Other constructor:

 -- 方法: classmethod time.fromisoformat (time_string)

     Return a *note time: 1b2. corresponding to a 'time_string' in any
     valid ISO 8601 format, with the following exceptions:

       1. Time zone offsets may have fractional seconds.

       2. The leading ‘T’, normally required in cases where there may be
          ambiguity between a date and a time, is not required.

       3. Fractional seconds may have any number of digits (anything
          beyond 6 will be truncated).

       4. Fractional hours and minutes are not supported.

     範例：

          >>> from datetime import time
          >>> time.fromisoformat('04:23:01')
          datetime.time(4, 23, 1)
          >>> time.fromisoformat('T04:23:01')
          datetime.time(4, 23, 1)
          >>> time.fromisoformat('T042301')
          datetime.time(4, 23, 1)
          >>> time.fromisoformat('04:23:01.000384')
          datetime.time(4, 23, 1, 384)
          >>> time.fromisoformat('04:23:01,000384')
          datetime.time(4, 23, 1, 384)
          >>> time.fromisoformat('04:23:01+04:00')
          datetime.time(4, 23, 1, tzinfo=datetime.timezone(datetime.timedelta(seconds=14400)))
          >>> time.fromisoformat('04:23:01Z')
          datetime.time(4, 23, 1, tzinfo=datetime.timezone.utc)
          >>> time.fromisoformat('04:23:01+00:00')
          datetime.time(4, 23, 1, tzinfo=datetime.timezone.utc)

     在 3.7 版被加入.

     在 3.11 版的變更: Previously, this method only supported formats
     that could be emitted by *note time.isoformat(): 234f.

實例方法：

 -- 方法: time.replace (hour=self.hour, minute=self.minute,
          second=self.second, microsecond=self.microsecond,
          tzinfo=self.tzinfo, *, fold=0)

     Return a *note time: 1b2. with the same value, except for those
     attributes given new values by whichever keyword arguments are
     specified.  Note that ‘tzinfo=None’ can be specified to create a
     naive *note time: 1b2. from an aware *note time: 1b2, without
     conversion of the time data.

     *note time: 1b2. objects are also supported by generic function
     *note copy.replace(): 136.

     在 3.6 版的變更: 新增 'fold' 參數。

 -- 方法: time.isoformat (timespec='auto')

     Return a string representing the time in ISO 8601 format, one of:

        - ‘HH:MM:SS.ffffff’, if *note microsecond: 230d. is not 0

        - ‘HH:MM:SS’, if *note microsecond: 230d. is 0

        - ‘HH:MM:SS.ffffff+HH:MM[:SS[.ffffff]]’, if *note utcoffset():
          2350. does not return ‘None’

        - ‘HH:MM:SS+HH:MM[:SS[.ffffff]]’, if *note microsecond: 230d. is
          0 and *note utcoffset(): 2350. does not return ‘None’

     The optional argument 'timespec' specifies the number of additional
     components of the time to include (the default is ‘'auto'’).  It
     can be one of the following:

        - ‘'auto'’: Same as ‘'seconds'’ if *note microsecond: 230d. is
          0, same as ‘'microseconds'’ otherwise.

        - ‘'hours'’: Include the *note hour: 230a. in the two-digit ‘HH’
          format.

        - ‘'minutes'’: Include *note hour: 230a. and *note minute: 230b.
          in ‘HH:MM’ format.

        - ‘'seconds'’: Include *note hour: 230a, *note minute: 230b, and
          *note second: 230c. in ‘HH:MM:SS’ format.

        - ‘'milliseconds'’: Include full time, but truncate fractional
          second part to milliseconds.  ‘HH:MM:SS.sss’ format.

        - ‘'microseconds'’: Include full time in ‘HH:MM:SS.ffffff’
          format.

          備註: Excluded time components are truncated, not rounded.

     *note ValueError: 1e7. will be raised on an invalid 'timespec'
     argument.

     範例：

          >>> from datetime import time
          >>> time(hour=12, minute=34, second=56, microsecond=123456).isoformat(timespec='minutes')
          '12:34'
          >>> dt = time(hour=12, minute=34, second=56, microsecond=0)
          >>> dt.isoformat(timespec='microseconds')
          '12:34:56.000000'
          >>> dt.isoformat(timespec='auto')
          '12:34:56'

     在 3.6 版的變更: 新增 'timespec' 參數。

 -- 方法: time.__str__ ()

     For a time 't', ‘str(t)’ is equivalent to ‘t.isoformat()’.

 -- 方法: time.strftime (format)

     Return a string representing the time, controlled by an explicit
     format string.  See also *note strftime() 與 strptime() 的行為:
     16ce. and *note time.isoformat(): 234f.

 -- 方法: time.__format__ (format)

     Same as *note time.strftime(): 1686.  This makes it possible to
     specify a format string for a *note time: 1b2. object in *note
     formatted string literals: 94d. and when using *note str.format():
     5c7.  See also *note strftime() 與 strptime() 的行為: 16ce. and
     *note time.isoformat(): 234f.

 -- 方法: time.utcoffset ()

     If *note tzinfo: 230e. is ‘None’, returns ‘None’, else returns
     ‘self.tzinfo.utcoffset(None)’, and raises an exception if the
     latter doesn't return ‘None’ or a *note timedelta: 973. object with
     magnitude less than one day.

     在 3.7 版的變更: The UTC offset is not restricted to a whole number
     of minutes.

 -- 方法: time.dst ()

     If *note tzinfo: 230e. is ‘None’, returns ‘None’, else returns
     ‘self.tzinfo.dst(None)’, and raises an exception if the latter
     doesn't return ‘None’, or a *note timedelta: 973. object with
     magnitude less than one day.

     在 3.7 版的變更: The DST offset is not restricted to a whole number
     of minutes.

 -- 方法: time.tzname ()

     If *note tzinfo: 230e. is ‘None’, returns ‘None’, else returns
     ‘self.tzinfo.tzname(None)’, or raises an exception if the latter
     doesn't return ‘None’ or a string object.

* Menu:

* 用法範例：time::

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=13936


File: python.info,  Node: 用法範例：time,  Up: time 物件

5.8.1.13 用法範例：‘time’
.........................

Examples of working with a *note time: 1b2. object:

     >>> from datetime import time, tzinfo, timedelta
     >>> class TZ1(tzinfo):
     ...     def utcoffset(self, dt):
     ...         return timedelta(hours=1)
     ...     def dst(self, dt):
     ...         return timedelta(0)
     ...     def tzname(self,dt):
     ...         return "+01:00"
     ...     def  __repr__(self):
     ...         return f"{self.__class__.__name__}()"
     ...
     >>> t = time(12, 10, 30, tzinfo=TZ1())
     >>> t
     datetime.time(12, 10, 30, tzinfo=TZ1())
     >>> t.isoformat()
     '12:10:30+01:00'
     >>> t.dst()
     datetime.timedelta(0)
     >>> t.tzname()
     '+01:00'
     >>> t.strftime("%H:%M:%S %Z")
     '12:10:30 +01:00'
     >>> 'The {} is {:%H:%M}.'.format("time", t)
     'The time is 12:10.'


File: python.info,  Node: tzinfo 物件,  Next: timezone 物件,  Prev: time 物件,  Up: datetime --- 日期與時間的基本型別

5.8.1.14 ‘tzinfo’ 物件
......................

 -- 類別: datetime.tzinfo

     This is an abstract base class, meaning that this class should not
     be instantiated directly.  Define a subclass of *note tzinfo: 582.
     to capture information about a particular time zone.

     An instance of (a concrete subclass of) *note tzinfo: 582. can be
     passed to the constructors for *note datetime: 1b0. and *note time:
     1b2. objects.  The latter objects view their attributes as being in
     local time, and the *note tzinfo: 582. object supports methods
     revealing offset of local time from UTC, the name of the time zone,
     and DST offset, all relative to a date or time object passed to
     them.

     You need to derive a concrete subclass, and (at least) supply
     implementations of the standard *note tzinfo: 582. methods needed
     by the *note datetime: 1b0. methods you use.  The ‘datetime’ module
     provides *note timezone: 1059, a simple concrete subclass of *note
     tzinfo: 582. which can represent time zones with fixed offset from
     UTC such as UTC itself or North American EST and EDT.

     Special requirement for pickling: A *note tzinfo: 582. subclass
     must have an *note __init__(): 655. method that can be called with
     no arguments, otherwise it can be pickled but possibly not
     unpickled again.  This is a technical requirement that may be
     relaxed in the future.

     A concrete subclass of *note tzinfo: 582. may need to implement the
     following methods.  Exactly which methods are needed depends on the
     uses made of aware ‘datetime’ objects.  If in doubt, simply
     implement all of them.

 -- 方法: tzinfo.utcoffset (dt)

     Return offset of local time from UTC, as a *note timedelta: 973.
     object that is positive east of UTC. If local time is west of UTC,
     this should be negative.

     This represents the 'total' offset from UTC; for example, if a
     *note tzinfo: 582. object represents both time zone and DST
     adjustments, *note utcoffset(): 2358. should return their sum.  If
     the UTC offset isn't known, return ‘None’.  Else the value returned
     must be a *note timedelta: 973. object strictly between
     ‘-timedelta(hours=24)’ and ‘timedelta(hours=24)’ (the magnitude of
     the offset must be less than one day).  Most implementations of
     *note utcoffset(): 2358. will probably look like one of these two:

          return CONSTANT                 # fixed-offset class
          return CONSTANT + self.dst(dt)  # daylight-aware class

     If *note utcoffset(): 2358. does not return ‘None’, *note dst():
     2359. should not return ‘None’ either.

     The default implementation of *note utcoffset(): 2358. raises *note
     NotImplementedError: 20d.

     在 3.7 版的變更: The UTC offset is not restricted to a whole number
     of minutes.

 -- 方法: tzinfo.dst (dt)

     Return the daylight saving time (DST) adjustment, as a *note
     timedelta: 973. object or ‘None’ if DST information isn't known.

     Return ‘timedelta(0)’ if DST is not in effect.  If DST is in
     effect, return the offset as a *note timedelta: 973. object (see
     *note utcoffset(): 2358. for details).  Note that DST offset, if
     applicable, has already been added to the UTC offset returned by
     *note utcoffset(): 2358, so there's no need to consult *note dst():
     2359. unless you're interested in obtaining DST info separately.
     For example, *note datetime.timetuple(): 233f. calls its *note
     tzinfo: 2316. attribute's *note dst(): 2359. method to determine
     how the *note tm_isdst: 2340. flag should be set, and *note
     tzinfo.fromutc(): 233d. calls *note dst(): 2359. to account for DST
     changes when crossing time zones.

     An instance 'tz' of a *note tzinfo: 582. subclass that models both
     standard and daylight times must be consistent in this sense:

     ‘tz.utcoffset(dt) - tz.dst(dt)’

     must return the same result for every *note datetime: 1b0. 'dt'
     with ‘dt.tzinfo == tz’.  For sane *note tzinfo: 582. subclasses,
     this expression yields the time zone's "standard offset", which
     should not depend on the date or the time, but only on geographic
     location.  The implementation of *note datetime.astimezone(): 974.
     relies on this, but cannot detect violations; it's the programmer's
     responsibility to ensure it.  If a *note tzinfo: 582. subclass
     cannot guarantee this, it may be able to override the default
     implementation of *note tzinfo.fromutc(): 233d. to work correctly
     with *note astimezone(): 974. regardless.

     Most implementations of *note dst(): 2359. will probably look like
     one of these two:

          def dst(self, dt):
              # a fixed-offset class:  doesn't account for DST
              return timedelta(0)

     或是：

          def dst(self, dt):
              # Code to set dston and dstoff to the time zone's DST
              # transition times based on the input dt.year, and expressed
              # in standard local time.

              if dston <= dt.replace(tzinfo=None) < dstoff:
                  return timedelta(hours=1)
              else:
                  return timedelta(0)

     The default implementation of *note dst(): 2359. raises *note
     NotImplementedError: 20d.

     在 3.7 版的變更: The DST offset is not restricted to a whole number
     of minutes.

 -- 方法: tzinfo.tzname (dt)

     Return the time zone name corresponding to the *note datetime: 1b0.
     object 'dt', as a string.  Nothing about string names is defined by
     the ‘datetime’ module, and there's no requirement that it mean
     anything in particular.  For example, ‘"GMT"’, ‘"UTC"’, ‘"-500"’,
     ‘"-5:00"’, ‘"EDT"’, ‘"US/Eastern"’, ‘"America/New York"’ are all
     valid replies.  Return ‘None’ if a string name isn't known.  Note
     that this is a method rather than a fixed string primarily because
     some *note tzinfo: 582. subclasses will wish to return different
     names depending on the specific value of 'dt' passed, especially if
     the *note tzinfo: 582. class is accounting for daylight time.

     The default implementation of *note tzname(): 235a. raises *note
     NotImplementedError: 20d.

These methods are called by a *note datetime: 1b0. or *note time: 1b2.
object, in response to their methods of the same names.  A *note
datetime: 1b0. object passes itself as the argument, and a *note time:
1b2. object passes ‘None’ as the argument.  A *note tzinfo: 582.
subclass's methods should therefore be prepared to accept a 'dt'
argument of ‘None’, or of class *note datetime: 1b0.

When ‘None’ is passed, it's up to the class designer to decide the best
response.  For example, returning ‘None’ is appropriate if the class
wishes to say that time objects don't participate in the *note tzinfo:
582. protocols.  It may be more useful for ‘utcoffset(None)’ to return
the standard UTC offset, as there is no other convention for discovering
the standard offset.

When a *note datetime: 1b0. object is passed in response to a *note
datetime: 1b0. method, ‘dt.tzinfo’ is the same object as 'self'.  *note
tzinfo: 582. methods can rely on this, unless user code calls *note
tzinfo: 582. methods directly.  The intent is that the *note tzinfo:
582. methods interpret 'dt' as being in local time, and not need worry
about objects in other time zones.

There is one more *note tzinfo: 582. method that a subclass may wish to
override:

 -- 方法: tzinfo.fromutc (dt)

     This is called from the default *note datetime.astimezone(): 974.
     implementation.  When called from that, ‘dt.tzinfo’ is 'self', and
     'dt"s date and time data are to be viewed as expressing a UTC time.
     The purpose of *note fromutc(): 233d. is to adjust the date and
     time data, returning an equivalent datetime in 'self"s local time.

     Most *note tzinfo: 582. subclasses should be able to inherit the
     default *note fromutc(): 233d. implementation without problems.
     It's strong enough to handle fixed-offset time zones, and time
     zones accounting for both standard and daylight time, and the
     latter even if the DST transition times differ in different years.
     An example of a time zone the default *note fromutc(): 233d.
     implementation may not handle correctly in all cases is one where
     the standard offset (from UTC) depends on the specific date and
     time passed, which can happen for political reasons.  The default
     implementations of *note astimezone(): 974. and *note fromutc():
     233d. may not produce the result you want if the result is one of
     the hours straddling the moment the standard offset changes.

     Skipping code for error cases, the default *note fromutc(): 233d.
     implementation acts like:

          def fromutc(self, dt):
              # raise ValueError error if dt.tzinfo is not self
              dtoff = dt.utcoffset()
              dtdst = dt.dst()
              # raise ValueError if dtoff is None or dtdst is None
              delta = dtoff - dtdst  # this is self's standard offset
              if delta:
                  dt += delta   # convert to standard local time
                  dtdst = dt.dst()
                  # raise ValueError if dtdst is None
              if dtdst:
                  return dt + dtdst
              else:
                  return dt

In the following ‘tzinfo_examples.py’ file there are some examples of
*note tzinfo: 582. classes:

     from datetime import tzinfo, timedelta, datetime

     ZERO = timedelta(0)
     HOUR = timedelta(hours=1)
     SECOND = timedelta(seconds=1)

     # A class capturing the platform's idea of local time.
     # (May result in wrong values on historical times in
     #  timezones where UTC offset and/or the DST rules had
     #  changed in the past.)
     import time as _time

     STDOFFSET = timedelta(seconds = -_time.timezone)
     if _time.daylight:
         DSTOFFSET = timedelta(seconds = -_time.altzone)
     else:
         DSTOFFSET = STDOFFSET

     DSTDIFF = DSTOFFSET - STDOFFSET

     class LocalTimezone(tzinfo):

         def fromutc(self, dt):
             assert dt.tzinfo is self
             stamp = (dt - datetime(1970, 1, 1, tzinfo=self)) // SECOND
             args = _time.localtime(stamp)[:6]
             dst_diff = DSTDIFF // SECOND
             # Detect fold
             fold = (args == _time.localtime(stamp - dst_diff))
             return datetime(*args, microsecond=dt.microsecond,
                             tzinfo=self, fold=fold)

         def utcoffset(self, dt):
             if self._isdst(dt):
                 return DSTOFFSET
             else:
                 return STDOFFSET

         def dst(self, dt):
             if self._isdst(dt):
                 return DSTDIFF
             else:
                 return ZERO

         def tzname(self, dt):
             return _time.tzname[self._isdst(dt)]

         def _isdst(self, dt):
             tt = (dt.year, dt.month, dt.day,
                   dt.hour, dt.minute, dt.second,
                   dt.weekday(), 0, 0)
             stamp = _time.mktime(tt)
             tt = _time.localtime(stamp)
             return tt.tm_isdst > 0

     Local = LocalTimezone()


     # A complete implementation of current DST rules for major US time zones.

     def first_sunday_on_or_after(dt):
         days_to_go = 6 - dt.weekday()
         if days_to_go:
             dt += timedelta(days_to_go)
         return dt


     # US DST Rules
     #
     # This is a simplified (i.e., wrong for a few cases) set of rules for US
     # DST start and end times. For a complete and up-to-date set of DST rules
     # and timezone definitions, visit the Olson Database (or try pytz):
     # http://www.twinsun.com/tz/tz-link.htm
     # https://sourceforge.net/projects/pytz/ (might not be up-to-date)
     #
     # In the US, since 2007, DST starts at 2am (standard time) on the second
     # Sunday in March, which is the first Sunday on or after Mar 8.
     DSTSTART_2007 = datetime(1, 3, 8, 2)
     # and ends at 2am (DST time) on the first Sunday of Nov.
     DSTEND_2007 = datetime(1, 11, 1, 2)
     # From 1987 to 2006, DST used to start at 2am (standard time) on the first
     # Sunday in April and to end at 2am (DST time) on the last
     # Sunday of October, which is the first Sunday on or after Oct 25.
     DSTSTART_1987_2006 = datetime(1, 4, 1, 2)
     DSTEND_1987_2006 = datetime(1, 10, 25, 2)
     # From 1967 to 1986, DST used to start at 2am (standard time) on the last
     # Sunday in April (the one on or after April 24) and to end at 2am (DST time)
     # on the last Sunday of October, which is the first Sunday
     # on or after Oct 25.
     DSTSTART_1967_1986 = datetime(1, 4, 24, 2)
     DSTEND_1967_1986 = DSTEND_1987_2006

     def us_dst_range(year):
         # Find start and end times for US DST. For years before 1967, return
         # start = end for no DST.
         if 2006 < year:
             dststart, dstend = DSTSTART_2007, DSTEND_2007
         elif 1986 < year < 2007:
             dststart, dstend = DSTSTART_1987_2006, DSTEND_1987_2006
         elif 1966 < year < 1987:
             dststart, dstend = DSTSTART_1967_1986, DSTEND_1967_1986
         else:
             return (datetime(year, 1, 1), ) * 2

         start = first_sunday_on_or_after(dststart.replace(year=year))
         end = first_sunday_on_or_after(dstend.replace(year=year))
         return start, end


     class USTimeZone(tzinfo):

         def __init__(self, hours, reprname, stdname, dstname):
             self.stdoffset = timedelta(hours=hours)
             self.reprname = reprname
             self.stdname = stdname
             self.dstname = dstname

         def __repr__(self):
             return self.reprname

         def tzname(self, dt):
             if self.dst(dt):
                 return self.dstname
             else:
                 return self.stdname

         def utcoffset(self, dt):
             return self.stdoffset + self.dst(dt)

         def dst(self, dt):
             if dt is None or dt.tzinfo is None:
                 # An exception may be sensible here, in one or both cases.
                 # It depends on how you want to treat them.  The default
                 # fromutc() implementation (called by the default astimezone()
                 # implementation) passes a datetime with dt.tzinfo is self.
                 return ZERO
             assert dt.tzinfo is self
             start, end = us_dst_range(dt.year)
             # Can't compare naive to aware objects, so strip the timezone from
             # dt first.
             dt = dt.replace(tzinfo=None)
             if start + HOUR <= dt < end - HOUR:
                 # DST is in effect.
                 return HOUR
             if end - HOUR <= dt < end:
                 # Fold (an ambiguous hour): use dt.fold to disambiguate.
                 return ZERO if dt.fold else HOUR
             if start <= dt < start + HOUR:
                 # Gap (a non-existent hour): reverse the fold rule.
                 return HOUR if dt.fold else ZERO
             # DST is off.
             return ZERO

         def fromutc(self, dt):
             assert dt.tzinfo is self
             start, end = us_dst_range(dt.year)
             start = start.replace(tzinfo=self)
             end = end.replace(tzinfo=self)
             std_time = dt + self.stdoffset
             dst_time = std_time + HOUR
             if end <= dst_time < end + HOUR:
                 # Repeated hour
                 return std_time.replace(fold=1)
             if std_time < start or dst_time >= end:
                 # Standard time
                 return std_time
             if start <= std_time < end - HOUR:
                 # Daylight saving time
                 return dst_time


     Eastern  = USTimeZone(-5, "Eastern",  "EST", "EDT")
     Central  = USTimeZone(-6, "Central",  "CST", "CDT")
     Mountain = USTimeZone(-7, "Mountain", "MST", "MDT")
     Pacific  = USTimeZone(-8, "Pacific",  "PST", "PDT")

Note that there are unavoidable subtleties twice per year in a *note
tzinfo: 582. subclass accounting for both standard and daylight time, at
the DST transition points.  For concreteness, consider US Eastern (UTC
-0500), where EDT begins the minute after 1:59 (EST) on the second
Sunday in March, and ends the minute after 1:59 (EDT) on the first
Sunday in November:

       UTC   3:MM  4:MM  5:MM  6:MM  7:MM  8:MM
       EST  22:MM 23:MM  0:MM  1:MM  2:MM  3:MM
       EDT  23:MM  0:MM  1:MM  2:MM  3:MM  4:MM

     start  22:MM 23:MM  0:MM  1:MM  3:MM  4:MM

       end  23:MM  0:MM  1:MM  1:MM  2:MM  3:MM

When DST starts (the "start" line), the local wall clock leaps from 1:59
to 3:00.  A wall time of the form 2:MM doesn't really make sense on that
day, so ‘astimezone(Eastern)’ won't deliver a result with ‘hour == 2’ on
the day DST begins.  For example, at the Spring forward transition of
2016, we get:

     >>> from datetime import datetime, timezone
     >>> from tzinfo_examples import HOUR, Eastern
     >>> u0 = datetime(2016, 3, 13, 5, tzinfo=timezone.utc)
     >>> for i in range(4):
     ...     u = u0 + i*HOUR
     ...     t = u.astimezone(Eastern)
     ...     print(u.time(), 'UTC =', t.time(), t.tzname())
     ...
     05:00:00 UTC = 00:00:00 EST
     06:00:00 UTC = 01:00:00 EST
     07:00:00 UTC = 03:00:00 EDT
     08:00:00 UTC = 04:00:00 EDT

When DST ends (the "end" line), there's a potentially worse problem:
there's an hour that can't be spelled unambiguously in local wall time:
the last hour of daylight time.  In Eastern, that's times of the form
5:MM UTC on the day daylight time ends.  The local wall clock leaps from
1:59 (daylight time) back to 1:00 (standard time) again.  Local times of
the form 1:MM are ambiguous.  *note astimezone(): 974. mimics the local
clock's behavior by mapping two adjacent UTC hours into the same local
hour then.  In the Eastern example, UTC times of the form 5:MM and 6:MM
both map to 1:MM when converted to Eastern, but earlier times have the
*note fold: bfe. attribute set to 0 and the later times have it set to
1.  For example, at the Fall back transition of 2016, we get:

     >>> u0 = datetime(2016, 11, 6, 4, tzinfo=timezone.utc)
     >>> for i in range(4):
     ...     u = u0 + i*HOUR
     ...     t = u.astimezone(Eastern)
     ...     print(u.time(), 'UTC =', t.time(), t.tzname(), t.fold)
     ...
     04:00:00 UTC = 00:00:00 EDT 0
     05:00:00 UTC = 01:00:00 EDT 0
     06:00:00 UTC = 01:00:00 EST 1
     07:00:00 UTC = 02:00:00 EST 0

Note that the *note datetime: 1b0. instances that differ only by the
value of the *note fold: bfe. attribute are considered equal in
comparisons.

Applications that can't bear wall-time ambiguities should explicitly
check the value of the *note fold: bfe. attribute or avoid using hybrid
*note tzinfo: 582. subclasses; there are no ambiguities when using *note
timezone: 1059, or any other fixed-offset *note tzinfo: 582. subclass
(such as a class representing only EST (fixed offset -5 hours), or only
EDT (fixed offset -4 hours)).

也參考
......

     *note zoneinfo: 11a.

          The ‘datetime’ module has a basic *note timezone: 1059. class
          (for handling arbitrary fixed offsets from UTC) and its *note
          timezone.utc: 5b9. attribute (a UTC ‘timezone’ instance).

          ‘zoneinfo’ brings the 'IANA time zone database' (also known as
          the Olson database) to Python, and its usage is recommended.

IANA 時區資料庫(1)

     The Time Zone Database (often called tz, tzdata or zoneinfo)
     contains code and data that represent the history of local time for
     many representative locations around the globe.  It is updated
     periodically to reflect changes made by political bodies to time
     zone boundaries, UTC offsets, and daylight-saving rules.

   ---------- Footnotes ----------

   (1) https://www.iana.org/time-zones


File: python.info,  Node: timezone 物件,  Next: strftime 與 strptime 的行為,  Prev: tzinfo 物件,  Up: datetime --- 日期與時間的基本型別

5.8.1.15 ‘timezone’ 物件
........................

The *note timezone: 1059. class is a subclass of *note tzinfo: 582, each
instance of which represents a time zone defined by a fixed offset from
UTC.

Objects of this class cannot be used to represent time zone information
in the locations where different offsets are used in different days of
the year or where historical changes have been made to civil time.

 -- 類別: datetime.timezone (offset, name=None)

     The 'offset' argument must be specified as a *note timedelta: 973.
     object representing the difference between the local time and UTC.
     It must be strictly between ‘-timedelta(hours=24)’ and
     ‘timedelta(hours=24)’, otherwise *note ValueError: 1e7. is raised.

     The 'name' argument is optional.  If specified it must be a string
     that will be used as the value returned by the *note
     datetime.tzname(): 233e. method.

     在 3.2 版被加入.

     在 3.7 版的變更: The UTC offset is not restricted to a whole number
     of minutes.

 -- 方法: timezone.utcoffset (dt)

     Return the fixed value specified when the *note timezone: 1059.
     instance is constructed.

     The 'dt' argument is ignored.  The return value is a *note
     timedelta: 973. instance equal to the difference between the local
     time and UTC.

     在 3.7 版的變更: The UTC offset is not restricted to a whole number
     of minutes.

 -- 方法: timezone.tzname (dt)

     Return the fixed value specified when the *note timezone: 1059.
     instance is constructed.

     If 'name' is not provided in the constructor, the name returned by
     ‘tzname(dt)’ is generated from the value of the ‘offset’ as
     follows.  If 'offset' is ‘timedelta(0)’, the name is "UTC",
     otherwise it is a string in the format ‘UTC±HH:MM’, where ± is the
     sign of ‘offset’, HH and MM are two digits of ‘offset.hours’ and
     ‘offset.minutes’ respectively.

     在 3.6 版的變更: Name generated from ‘offset=timedelta(0)’ is now
     plain ‘'UTC'’, not ‘'UTC+00:00'’.

 -- 方法: timezone.dst (dt)

     總是回傳 ‘None’。

 -- 方法: timezone.fromutc (dt)

     Return ‘dt + offset’.  The 'dt' argument must be an aware *note
     datetime: 1b0. instance, with ‘tzinfo’ set to ‘self’.

類別屬性：

 -- 屬性: timezone.utc

     UTC 時區，‘timezone(timedelta(0))’。


File: python.info,  Node: strftime 與 strptime 的行為,  Prev: timezone 物件,  Up: datetime --- 日期與時間的基本型別

5.8.1.16 ‘strftime()’ 與 ‘strptime()’ 的行為
............................................

*note date: 1b1, *note datetime: 1b0, and *note time: 1b2. objects all
support a ‘strftime(format)’ method, to create a string representing the
time under the control of an explicit format string.

Conversely, the *note datetime.strptime(): 14fe. class method creates a
*note datetime: 1b0. object from a string representing a date and time
and a corresponding format string.

The table below provides a high-level comparison of *note strftime():
c37. versus *note strptime(): 14fe.:

                     ‘strftime’                                                   ‘strptime’
                                                                                  
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
                                                                                  
用法                 Convert object to a string according to a given format       Parse a string into a *note datetime: 1b0. object given a corresponding format
                                                                                  
                                                                                  
Type of method       實例方法                                                     類別方法
                                                                                  
                                                                                  
Method of            *note date: 1b1.; *note datetime: 1b0.; *note time: 1b2.     *note datetime: 1b0.
                                                                                  
                                                                                  
Signature            ‘strftime(format)’                                           ‘strptime(date_string, format)’
                                                                                  

* Menu:

* strftime() 與 strptime() 格式碼: strftime 與 strptime 格式碼.
* 技術細節::


File: python.info,  Node: strftime 與 strptime 格式碼,  Next: 技術細節,  Up: strftime 與 strptime 的行為

5.8.1.17 ‘strftime()’ 與 ‘strptime()’ 格式碼
............................................

These methods accept format codes that can be used to parse and format
dates:

     >>> datetime.strptime('31/01/22 23:59:59.999999',
     ...                   '%d/%m/%y %H:%M:%S.%f')
     datetime.datetime(2022, 1, 31, 23, 59, 59, 999999)
     >>> _.strftime('%a %d %b %Y, %I:%M%p')
     'Mon 31 Jan 2022, 11:59PM'

The following is a list of all the format codes that the 1989 C standard
requires, and these work on all platforms with a standard C
implementation.

Directive       含義                                 範例                         註解
                                                                                  
----------------------------------------------------------------------------------------------
                                                                                  
‘%a’            Weekday as locale's abbreviated           Sun, Mon, ..., Sat (en_US);(1)
                name.                                     So, Mo, ..., Sa (de_DE) 
                                                     
                                                                                  
‘%A’            Weekday as locale's full name.            Sunday, Monday, ..., Saturday (en_US);(1)
                                                          Sonntag, Montag, ..., Samstag (de_DE)
                                                     
                                                                                  
‘%w’            Weekday as a decimal number, where   0, 1, ..., 6
                0 is Sunday and 6 is Saturday.       
                
                                                                                  
‘%d’            Day of the month as a zero-padded    01, 02, ..., 31              (9)
                decimal number.                                                   
                
                                                                                  
‘%b’            Month as locale's abbreviated             Jan, Feb, ..., Dec (en_US);(1)
                name.                                     Jan, Feb, ..., Dez (de_DE)
                                                     
                                                                                  
‘%B’            Month as locale's full name.              January, February, ..., December (en_US);(1)
                                                          Januar, Februar, ..., Dezember (de_DE)
                                                     
                                                                                  
‘%m’            以零填充的並以十進位數字表示的月份   01, 02, ..., 12              (9)
                。                                                                
                
                                                                                  
‘%y’            Year without century as a            00, 01, ..., 99              (9)
                zero-padded decimal number.                                       
                
                                                                                  
‘%Y’            Year with century as a decimal       0001, 0002, ..., 2013,       (2)
                number.                              2014, ..., 9998, 9999        
                                                     
                                                                                  
‘%H’            Hour (24-hour clock) as a            00, 01, ..., 23              (9)
                zero-padded decimal number.                                       
                
                                                                                  
‘%I’            Hour (12-hour clock) as a            01, 02, ..., 12              (9)
                zero-padded decimal number.                                       
                
                                                                                  
‘%p’            Locale's equivalent of either AM          AM, PM (en_US);         (1), (3)
                or PM.                                    am, pm (de_DE)          
                                                     
                                                                                  
‘%M’            Minute as a zero-padded decimal      00, 01, ..., 59              (9)
                number.                                                           
                
                                                                                  
‘%S’            Second as a zero-padded decimal      00, 01, ..., 59              (4), (9)
                number.                                                           
                
                                                                                  
‘%f’            Microsecond as a decimal number,     000000, 000001, ...,         (5)
                zero-padded to 6 digits.             999999                       
                                                     
                                                                                  
‘%z’            UTC offset in the form               (empty), +0000, -0400,       (6)
                ‘±HHMM[SS[.ffffff]]’ (empty string   +1030, +063415,              
                if the object is naive).             -030712.345216
                                                     
                                                                                  
‘%Z’            Time zone name (empty string if      (empty), UTC, GMT            (6)
                the object is naive).                                             
                
                                                                                  
‘%j’            Day of the year as a zero-padded     001, 002, ..., 366           (9)
                decimal number.                                                   
                
                                                                                  
‘%U’            Week number of the year (Sunday as   00, 01, ..., 53              (7), (9)
                the first day of the week) as a                                   
                zero-padded decimal number.  All
                days in a new year preceding the
                first Sunday are considered to be
                in week 0.
                
                                                                                  
‘%W’            Week number of the year (Monday as   00, 01, ..., 53              (7), (9)
                the first day of the week) as a                                   
                zero-padded decimal number.  All
                days in a new year preceding the
                first Monday are considered to be
                in week 0.
                
                                                                                  
‘%c’            Locale's appropriate date and time        Tue Aug 16 21:30:00 1988 (en_US);(1)
                representation.                           Di 16 Aug 21:30:00 1988 (de_DE)
                                                     
                                                                                  
‘%x’            Locale's appropriate date                 08/16/88 (None);        (1)
                representation.                           08/16/1988 (en_US);     
                                                          16.08.1988 (de_DE)
                                                     
                                                                                  
‘%X’            Locale's appropriate time                 21:30:00 (en_US);       (1)
                representation.                           21:30:00 (de_DE)        
                                                     
                                                                                  
‘%%’            A literal ‘'%'’ character.           %
                                                     

Several additional directives not required by the C89 standard are
included for convenience.  These parameters all correspond to ISO 8601
date values.

Directive       含義                                 範例                         註解
                                                                                  
----------------------------------------------------------------------------------------------
                                                                                  
‘%G’            ISO 8601 year with century           0001, 0002, ..., 2013,       (8)
                representing the year that           2014, ..., 9998, 9999        
                contains the greater part of the     
                ISO week (‘%V’).
                
                                                                                  
‘%u’            ISO 8601 weekday as a decimal        1, 2, ..., 7
                number where 1 is Monday.            
                
                                                                                  
‘%V’            ISO 8601 week as a decimal number    01, 02, ..., 53              (8), (9)
                with Monday as the first day of                                   
                the week.  Week 01 is the week
                containing Jan 4.
                
                                                                                  
‘%:z’           UTC offset in the form               (empty), +00:00, -04:00,     (6)
                ‘±HH:MM[:SS[.ffffff]]’ (empty        +10:30, +06:34:15,           
                string if the object is naive).      -03:07:12.345216
                                                     

These may not be available on all platforms when used with the *note
strftime(): c37. method.  The ISO 8601 year and ISO 8601 week directives
are not interchangeable with the year and week number directives above.
Calling *note strptime(): 14fe. with incomplete or ambiguous ISO 8601
directives will raise a *note ValueError: 1e7.

The full set of format codes supported varies across platforms, because
Python calls the platform C library's ‘strftime()’ function, and
platform variations are common.  To see the full set of format codes
supported on your platform, consult the ‘strftime(3)(1)’ documentation.
There are also differences between platforms in handling of unsupported
format specifiers.

在 3.6 版被加入: 新增 ‘%G’、‘%u’ 與 ‘%V’。

在 3.12 版被加入: 新增 ‘%:z’。

   ---------- Footnotes ----------

   (1) https://manpages.debian.org/strftime(3)


File: python.info,  Node: 技術細節,  Prev: strftime 與 strptime 格式碼,  Up: strftime 與 strptime 的行為

5.8.1.18 技術細節
.................

Broadly speaking, ‘d.strftime(fmt)’ acts like the *note time: d7.
module's ‘time.strftime(fmt, d.timetuple())’ although not all objects
support a *note timetuple(): 2328. method.

For the *note datetime.strptime(): 14fe. class method, the default value
is ‘1900-01-01T00:00:00.000’: any components not specified in the format
string will be pulled from the default value.  (1)

Using ‘datetime.strptime(date_string, format)’ is equivalent to:

     datetime(*(time.strptime(date_string, format)[0:6]))

except when the format includes sub-second components or time zone
offset information, which are supported in ‘datetime.strptime’ but are
discarded by ‘time.strptime’.

對 *note time: 1b2. 物件來說，不應該使用年、月、日的格式碼，因為 ‘time’
物件並沒有這些值。如果使用這些格式碼，年份會以 1900 代替、月及日會以 1 代
替。

對 *note date: 1b1. 物件來說，不應該使用時、分、秒、微秒的格式碼，因為
*note date: 1b1. 物件並沒有這些值。如果使用這些格式碼，這些值都會以 0 代
替。

For the same reason, handling of format strings containing Unicode code
points that can't be represented in the charset of the current locale is
also platform-dependent.  On some platforms such code points are
preserved intact in the output, while on others ‘strftime’ may raise
*note UnicodeError: 123a. or return an empty string instead.

註解：

  1. Because the format depends on the current locale, care should be
     taken when making assumptions about the output value.  Field
     orderings will vary (for example, "month/day/year" versus
     "day/month/year"), and the output may contain non-ASCII characters.

  2. The *note strptime(): 14fe. method can parse years in the full [1,
     9999] range, but years < 1000 must be zero-filled to 4-digit width.

     在 3.2 版的變更: In previous versions, *note strftime(): c37.
     method was restricted to years >= 1900.

     在 3.3 版的變更: In version 3.2, *note strftime(): c37. method was
     restricted to years >= 1000.

  3. When used with the *note strptime(): 14fe. method, the ‘%p’
     directive only affects the output hour field if the ‘%I’ directive
     is used to parse the hour.

  4. Unlike the *note time: d7. module, the ‘datetime’ module does not
     support leap seconds.

  5. When used with the *note strptime(): 14fe. method, the ‘%f’
     directive accepts from one to six digits and zero pads on the
     right.  ‘%f’ is an extension to the set of format characters in the
     C standard (but implemented separately in datetime objects, and
     therefore always available).

  6. For a naive object, the ‘%z’, ‘%:z’ and ‘%Z’ format codes are
     replaced by empty strings.

     For an aware object:

     ‘%z’

          *note utcoffset(): 233b. is transformed into a string of the
          form ‘±HHMM[SS[.ffffff]]’, where ‘HH’ is a 2-digit string
          giving the number of UTC offset hours, ‘MM’ is a 2-digit
          string giving the number of UTC offset minutes, ‘SS’ is a
          2-digit string giving the number of UTC offset seconds and
          ‘ffffff’ is a 6-digit string giving the number of UTC offset
          microseconds.  The ‘ffffff’ part is omitted when the offset is
          a whole number of seconds and both the ‘ffffff’ and the ‘SS’
          part is omitted when the offset is a whole number of minutes.
          For example, if *note utcoffset(): 233b. returns
          ‘timedelta(hours=-3, minutes=-30)’, ‘%z’ is replaced with the
          string ‘'-0330'’.

     在 3.7 版的變更: The UTC offset is not restricted to a whole number
     of minutes.

     在 3.7 版的變更: When the ‘%z’ directive is provided to the *note
     strptime(): 14fe. method, the UTC offsets can have a colon as a
     separator between hours, minutes and seconds.  For example,
     ‘'+01:00:00'’ will be parsed as an offset of one hour.  In
     addition, providing ‘'Z'’ is identical to ‘'+00:00'’.

     ‘%:z’

          Behaves exactly as ‘%z’, but has a colon separator added
          between hours, minutes and seconds.

     ‘%Z’

          In *note strftime(): c37, ‘%Z’ is replaced by an empty string
          if *note tzname(): 233e. returns ‘None’; otherwise ‘%Z’ is
          replaced by the returned value, which must be a string.

          *note strptime(): 14fe. only accepts certain values for ‘%Z’:

            1. any value in ‘time.tzname’ for your machine's locale

            2. the hard-coded values ‘UTC’ and ‘GMT’

          So someone living in Japan may have ‘JST’, ‘UTC’, and ‘GMT’ as
          valid values, but probably not ‘EST’.  It will raise
          ‘ValueError’ for invalid values.

     在 3.2 版的變更: When the ‘%z’ directive is provided to the *note
     strptime(): 14fe. method, an aware *note datetime: 1b0. object will
     be produced.  The ‘tzinfo’ of the result will be set to a *note
     timezone: 1059. instance.

  7. When used with the *note strptime(): 14fe. method, ‘%U’ and ‘%W’
     are only used in calculations when the day of the week and the
     calendar year (‘%Y’) are specified.

  8. Similar to ‘%U’ and ‘%W’, ‘%V’ is only used in calculations when
     the day of the week and the ISO year (‘%G’) are specified in a
     *note strptime(): 14fe. format string.  Also note that ‘%G’ and
     ‘%Y’ are not interchangeable.

  9. When used with the *note strptime(): 14fe. method, the leading zero
     is optional for formats ‘%d’, ‘%m’, ‘%H’, ‘%I’, ‘%M’, ‘%S’, ‘%j’,
     ‘%U’, ‘%W’, and ‘%V’.  Format ‘%y’ does require a leading zero.

  10. When parsing a month and day using *note strptime(): 14fe, always
     include a year in the format.  If the value you need to parse lacks
     a year, append an explicit dummy leap year.  Otherwise your code
     will raise an exception when it encounters leap day because the
     default year used by the parser is not a leap year.  Users run into
     this bug every four years...

          >>> month_day = "02/29"
          >>> datetime.strptime(f"{month_day};1984", "%m/%d;%Y")  # No leap year bug.
          datetime.datetime(1984, 2, 29, 0, 0)

     Deprecated since version 3.13, will be removed in version 3.15:
     *note strptime(): 14fe. calls using a format string containing a
     day of month without a year now emit a *note DeprecationWarning:
     18b.  In 3.15 or later we may change this into an error or change
     the default year to a leap year.  See gh-70647(2).

註解
....

   ---------- Footnotes ----------

   (1) Passing ‘datetime.strptime('Feb 29', '%b %d')’ will fail since
1900 is not a leap year.

   (2) https://github.com/python/cpython/issues/70647


File: python.info,  Node: zoneinfo --- IANA 時區支援,  Next: calendar --- 日曆相關函式,  Prev: datetime --- 日期與時間的基本型別,  Up: 資料型別

5.8.2 ‘zoneinfo’ -- IANA 時區支援
---------------------------------

在 3.9 版被加入.

'原始碼：'Lib/zoneinfo(1)

__________________________________________________________________

The *note zoneinfo: 11a. module provides a concrete time zone
implementation to support the IANA time zone database as originally
specified in PEP 615(2).  By default, *note zoneinfo: 11a. uses the
system's time zone data if available; if no system time zone data is
available, the library will fall back to using the first-party tzdata(3)
package available on PyPI.

也參考
......

*note datetime: 28. 模組

     Provides the *note time: 1b2. and *note datetime: 1b0. types with
     which the *note ZoneInfo: 884. class is designed to be used.

Package tzdata(4)

     First-party package maintained by the CPython core developers to
     supply time zone data via PyPI.

*note Availability: 1c56.: not WASI.

This module does not work or is not available on WebAssembly.  See *note
WebAssembly 平台: 16e6. for more information.

* Menu:

* Using ZoneInfo::
* Data sources::
* The ZoneInfo class::
* 函式: 函式<2>.
* Globals::
* Exceptions and warnings::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/zoneinfo

   (2) https://peps.python.org/pep-0615/

   (3) https://pypi.org/project/tzdata/

   (4) https://pypi.org/project/tzdata/


File: python.info,  Node: Using ZoneInfo,  Next: Data sources,  Up: zoneinfo --- IANA 時區支援

5.8.2.1 Using ‘ZoneInfo’
........................

*note ZoneInfo: 884. is a concrete implementation of the *note
datetime.tzinfo: 582. abstract base class, and is intended to be
attached to ‘tzinfo’, either via the constructor, the *note
datetime.replace: 143a. method or *note datetime.astimezone: 974.:

     >>> from zoneinfo import ZoneInfo
     >>> from datetime import datetime, timedelta

     >>> dt = datetime(2020, 10, 31, 12, tzinfo=ZoneInfo("America/Los_Angeles"))
     >>> print(dt)
     2020-10-31 12:00:00-07:00

     >>> dt.tzname()
     'PDT'

Datetimes constructed in this way are compatible with datetime
arithmetic and handle daylight saving time transitions with no further
intervention:

     >>> dt_add = dt + timedelta(days=1)

     >>> print(dt_add)
     2020-11-01 12:00:00-08:00

     >>> dt_add.tzname()
     'PST'

These time zones also support the *note fold: bfe. attribute introduced
in PEP 495(1).  During offset transitions which induce ambiguous times
(such as a daylight saving time to standard time transition), the offset
from 'before' the transition is used when ‘fold=0’, and the offset
'after' the transition is used when ‘fold=1’, for example:

     >>> dt = datetime(2020, 11, 1, 1, tzinfo=ZoneInfo("America/Los_Angeles"))
     >>> print(dt)
     2020-11-01 01:00:00-07:00

     >>> print(dt.replace(fold=1))
     2020-11-01 01:00:00-08:00

When converting from another time zone, the fold will be set to the
correct value:

     >>> from datetime import timezone
     >>> LOS_ANGELES = ZoneInfo("America/Los_Angeles")
     >>> dt_utc = datetime(2020, 11, 1, 8, tzinfo=timezone.utc)

     >>> # Before the PDT -> PST transition
     >>> print(dt_utc.astimezone(LOS_ANGELES))
     2020-11-01 01:00:00-07:00

     >>> # After the PDT -> PST transition
     >>> print((dt_utc + timedelta(hours=1)).astimezone(LOS_ANGELES))
     2020-11-01 01:00:00-08:00

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0495/


File: python.info,  Node: Data sources,  Next: The ZoneInfo class,  Prev: Using ZoneInfo,  Up: zoneinfo --- IANA 時區支援

5.8.2.2 Data sources
....................

The ‘zoneinfo’ module does not directly provide time zone data, and
instead pulls time zone information from the system time zone database
or the first-party PyPI package tzdata(1), if available.  Some systems,
including notably Windows systems, do not have an IANA database
available, and so for projects targeting cross-platform compatibility
that require time zone data, it is recommended to declare a dependency
on tzdata.  If neither system data nor tzdata are available, all calls
to *note ZoneInfo: 884. will raise *note ZoneInfoNotFoundError: 2368.

* Menu:

* Configuring the data sources::

   ---------- Footnotes ----------

   (1) https://pypi.org/project/tzdata/


File: python.info,  Node: Configuring the data sources,  Up: Data sources

5.8.2.3 Configuring the data sources
....................................

When ‘ZoneInfo(key)’ is called, the constructor first searches the
directories specified in *note TZPATH: 1c72. for a file matching ‘key’,
and on failure looks for a match in the tzdata package.  This behavior
can be configured in three ways:

  1. The default *note TZPATH: 1c72. when not otherwise specified can be
     configured at *note compile time: 1c73.

  2. *note TZPATH: 1c72. can be configured using *note an environment
     variable: 236b.

  3. At *note runtime: 236c, the search path can be manipulated using
     the *note reset_tzpath(): 236d. function.

* Menu:

* Compile-time configuration::
* Environment configuration::
* Runtime configuration::


File: python.info,  Node: Compile-time configuration,  Next: Environment configuration,  Up: Configuring the data sources

5.8.2.4 Compile-time configuration
..................................

The default *note TZPATH: 1c72. includes several common deployment
locations for the time zone database (except on Windows, where there are
no "well-known" locations for time zone data).  On POSIX systems,
downstream distributors and those building Python from source who know
where their system time zone data is deployed may change the default
time zone path by specifying the compile-time option ‘TZPATH’ (or, more
likely, the *note configure flag -with-tzpath: 1c71.), which should be a
string delimited by *note os.pathsep: 1c46.

On all platforms, the configured value is available as the ‘TZPATH’ key
in *note sysconfig.get_config_var(): fce.


File: python.info,  Node: Environment configuration,  Next: Runtime configuration,  Prev: Compile-time configuration,  Up: Configuring the data sources

5.8.2.5 Environment configuration
.................................

When initializing *note TZPATH: 1c72. (either at import time or whenever
*note reset_tzpath(): 236d. is called with no arguments), the ‘zoneinfo’
module will use the environment variable ‘PYTHONTZPATH’, if it exists,
to set the search path.

 -- 環境變數: PYTHONTZPATH

     This is an *note os.pathsep: 1c46.-separated string containing the
     time zone search path to use.  It must consist of only absolute
     rather than relative paths.  Relative components specified in
     ‘PYTHONTZPATH’ will not be used, but otherwise the behavior when a
     relative path is specified is implementation-defined; CPython will
     raise *note InvalidTZPathWarning: 2371, but other implementations
     are free to silently ignore the erroneous component or raise an
     exception.

To set the system to ignore the system data and use the tzdata package
instead, set ‘PYTHONTZPATH=""’.


File: python.info,  Node: Runtime configuration,  Prev: Environment configuration,  Up: Configuring the data sources

5.8.2.6 Runtime configuration
.............................

The TZ search path can also be configured at runtime using the *note
reset_tzpath(): 236d. function.  This is generally not an advisable
operation, though it is reasonable to use it in test functions that
require the use of a specific time zone path (or require disabling
access to the system time zones).


File: python.info,  Node: The ZoneInfo class,  Next: 函式<2>,  Prev: Data sources,  Up: zoneinfo --- IANA 時區支援

5.8.2.7 The ‘ZoneInfo’ class
............................

 -- 類別: zoneinfo.ZoneInfo (key)

     A concrete *note datetime.tzinfo: 582. subclass that represents an
     IANA time zone specified by the string ‘key’.  Calls to the primary
     constructor will always return objects that compare identically;
     put another way, barring cache invalidation via *note
     ZoneInfo.clear_cache(): 2374, for all values of ‘key’, the
     following assertion will always be true:

          a = ZoneInfo(key)
          b = ZoneInfo(key)
          assert a is b

     ‘key’ must be in the form of a relative, normalized POSIX path,
     with no up-level references.  The constructor will raise *note
     ValueError: 1e7. if a non-conforming key is passed.

     If no file matching ‘key’ is found, the constructor will raise
     *note ZoneInfoNotFoundError: 2368.

The ‘ZoneInfo’ class has two alternate constructors:

 -- 方法: classmethod ZoneInfo.from_file (fobj, /, key=None)

     Constructs a ‘ZoneInfo’ object from a file-like object returning
     bytes (e.g.  a file opened in binary mode or an *note io.BytesIO:
     e46. object).  Unlike the primary constructor, this always
     constructs a new object.

     The ‘key’ parameter sets the name of the zone for the purposes of
     *note __str__(): 5c4. and *note __repr__(): 5c2.

     Objects created via this constructor cannot be pickled (see *note
     pickling: 2376.).

 -- 方法: classmethod ZoneInfo.no_cache (key)

     An alternate constructor that bypasses the constructor's cache.  It
     is identical to the primary constructor, but returns a new object
     on each call.  This is most likely to be useful for testing or
     demonstration purposes, but it can also be used to create a system
     with a different cache invalidation strategy.

     Objects created via this constructor will also bypass the cache of
     a deserializing process when unpickled.

          警示: Using this constructor may change the semantics of your
          datetimes in surprising ways, only use it if you know that you
          need to.

The following class methods are also available:

 -- 方法: classmethod ZoneInfo.clear_cache (*, only_keys=None)

     A method for invalidating the cache on the ‘ZoneInfo’ class.  If no
     arguments are passed, all caches are invalidated and the next call
     to the primary constructor for each key will return a new instance.

     If an iterable of key names is passed to the ‘only_keys’ parameter,
     only the specified keys will be removed from the cache.  Keys
     passed to ‘only_keys’ but not found in the cache are ignored.

          警告: Invoking this function may change the semantics of
          datetimes using ‘ZoneInfo’ in surprising ways; this modifies
          module state and thus may have wide-ranging effects.  Only use
          it if you know that you need to.

The class has one attribute:

 -- 屬性: ZoneInfo.key

     This is a read-only *note attribute: 2379. that returns the value
     of ‘key’ passed to the constructor, which should be a lookup key in
     the IANA time zone database (e.g.  ‘America/New_York’,
     ‘Europe/Paris’ or ‘Asia/Tokyo’).

     For zones constructed from file without specifying a ‘key’
     parameter, this will be set to ‘None’.

          備註: Although it is a somewhat common practice to expose
          these to end users, these values are designed to be primary
          keys for representing the relevant zones and not necessarily
          user-facing elements.  Projects like CLDR (the Unicode Common
          Locale Data Repository) can be used to get more user-friendly
          strings from these keys.

* Menu:

* String representations::
* Pickle serialization::


File: python.info,  Node: String representations,  Next: Pickle serialization,  Up: The ZoneInfo class

5.8.2.8 String representations
..............................

The string representation returned when calling *note str: 3f2. on a
*note ZoneInfo: 884. object defaults to using the *note ZoneInfo.key:
2378. attribute (see the note on usage in the attribute documentation):

     >>> zone = ZoneInfo("Pacific/Kwajalein")
     >>> str(zone)
     'Pacific/Kwajalein'

     >>> dt = datetime(2020, 4, 1, 3, 15, tzinfo=zone)
     >>> f"{dt.isoformat()} [{dt.tzinfo}]"
     '2020-04-01T03:15:00+12:00 [Pacific/Kwajalein]'

For objects constructed from a file without specifying a ‘key’
parameter, ‘str’ falls back to calling *note repr(): 7a1.  ‘ZoneInfo’'s
‘repr’ is implementation-defined and not necessarily stable between
versions, but it is guaranteed not to be a valid ‘ZoneInfo’ key.


File: python.info,  Node: Pickle serialization,  Prev: String representations,  Up: The ZoneInfo class

5.8.2.9 Pickle serialization
............................

Rather than serializing all transition data, ‘ZoneInfo’ objects are
serialized by key, and ‘ZoneInfo’ objects constructed from files (even
those with a value for ‘key’ specified) cannot be pickled.

The behavior of a ‘ZoneInfo’ file depends on how it was constructed:

  1. ‘ZoneInfo(key)’: When constructed with the primary constructor, a
     ‘ZoneInfo’ object is serialized by key, and when deserialized, the
     deserializing process uses the primary and thus it is expected that
     these are expected to be the same object as other references to the
     same time zone.  For example, if ‘europe_berlin_pkl’ is a string
     containing a pickle constructed from ‘ZoneInfo("Europe/Berlin")’,
     one would expect the following behavior:

          >>> a = ZoneInfo("Europe/Berlin")
          >>> b = pickle.loads(europe_berlin_pkl)
          >>> a is b
          True

  2. ‘ZoneInfo.no_cache(key)’: When constructed from the cache-bypassing
     constructor, the ‘ZoneInfo’ object is also serialized by key, but
     when deserialized, the deserializing process uses the cache
     bypassing constructor.  If ‘europe_berlin_pkl_nc’ is a string
     containing a pickle constructed from
     ‘ZoneInfo.no_cache("Europe/Berlin")’, one would expect the
     following behavior:

          >>> a = ZoneInfo("Europe/Berlin")
          >>> b = pickle.loads(europe_berlin_pkl_nc)
          >>> a is b
          False

  3. ‘ZoneInfo.from_file(fobj, /, key=None)’: When constructed from a
     file, the ‘ZoneInfo’ object raises an exception on pickling.  If an
     end user wants to pickle a ‘ZoneInfo’ constructed from a file, it
     is recommended that they use a wrapper type or a custom
     serialization function: either serializing by key or storing the
     contents of the file object and serializing that.

This method of serialization requires that the time zone data for the
required key be available on both the serializing and deserializing
side, similar to the way that references to classes and functions are
expected to exist in both the serializing and deserializing
environments.  It also means that no guarantees are made about the
consistency of results when unpickling a ‘ZoneInfo’ pickled in an
environment with a different version of the time zone data.


File: python.info,  Node: 函式<2>,  Next: Globals,  Prev: The ZoneInfo class,  Up: zoneinfo --- IANA 時區支援

5.8.2.10 函式
.............

 -- 函式: zoneinfo.available_timezones ()

     Get a set containing all the valid keys for IANA time zones
     available anywhere on the time zone path.  This is recalculated on
     every call to the function.

     This function only includes canonical zone names and does not
     include "special" zones such as those under the ‘posix/’ and
     ‘right/’ directories, or the ‘posixrules’ zone.

          警示: This function may open a large number of files, as the
          best way to determine if a file on the time zone path is a
          valid time zone is to read the "magic string" at the
          beginning.

          備註: These values are not designed to be exposed to
          end-users; for user facing elements, applications should use
          something like CLDR (the Unicode Common Locale Data
          Repository) to get more user-friendly strings.  See also the
          cautionary note on *note ZoneInfo.key: 2378.

 -- 函式: zoneinfo.reset_tzpath (to=None)

     Sets or resets the time zone search path (*note TZPATH: 1c72.) for
     the module.  When called with no arguments, *note TZPATH: 1c72. is
     set to the default value.

     Calling ‘reset_tzpath’ will not invalidate the *note ZoneInfo: 884.
     cache, and so calls to the primary ‘ZoneInfo’ constructor will only
     use the new ‘TZPATH’ in the case of a cache miss.

     The ‘to’ parameter must be a *note sequence: 499. of strings or
     *note os.PathLike: bf8. and not a string, all of which must be
     absolute paths.  *note ValueError: 1e7. will be raised if something
     other than an absolute path is passed.


File: python.info,  Node: Globals,  Next: Exceptions and warnings,  Prev: 函式<2>,  Up: zoneinfo --- IANA 時區支援

5.8.2.11 Globals
................

 -- 資料: zoneinfo.TZPATH

     A read-only sequence representing the time zone search path - when
     constructing a ‘ZoneInfo’ from a key, the key is joined to each
     entry in the ‘TZPATH’, and the first file found is used.

     ‘TZPATH’ may contain only absolute paths, never relative paths,
     regardless of how it is configured.

     The object that ‘zoneinfo.TZPATH’ points to may change in response
     to a call to *note reset_tzpath(): 236d, so it is recommended to
     use ‘zoneinfo.TZPATH’ rather than importing ‘TZPATH’ from
     ‘zoneinfo’ or assigning a long-lived variable to ‘zoneinfo.TZPATH’.

     For more information on configuring the time zone search path, see
     *note Configuring the data sources: 236a.


File: python.info,  Node: Exceptions and warnings,  Prev: Globals,  Up: zoneinfo --- IANA 時區支援

5.8.2.12 Exceptions and warnings
................................

 -- 例外: zoneinfo.ZoneInfoNotFoundError

     Raised when construction of a *note ZoneInfo: 884. object fails
     because the specified key could not be found on the system.  This
     is a subclass of *note KeyError: 2fb.

 -- 例外: zoneinfo.InvalidTZPathWarning

     Raised when *note PYTHONTZPATH: 2370. contains an invalid component
     that will be filtered out, such as a relative path.


File: python.info,  Node: calendar --- 日曆相關函式,  Next: collections --- 容器資料型態,  Prev: zoneinfo --- IANA 時區支援,  Up: 資料型別

5.8.3 ‘calendar’ -- 日曆相關函式
--------------------------------

'原始碼：'Lib/calendar.py(1)

__________________________________________________________________

這個模組讓你可以像 Unix 的 ‘cal’ 程式一樣輸出日曆，並額外提供有用的日曆
相關函式。這些日曆預設把週一當作一週的第一天，而週日當作最後一天（歐洲的
慣例）。可以使用 *note setfirstweekday(): 2381. 設定一週的第一天為週日
(6) 或一週的其它任一天，其中指定日期的參數是整數。相關功能參考 *note
datetime: 28. 和 *note time: d7. 模組。

這個模組定義的函式和類別使用理想化的日曆，也就是公曆 (Gregorian
calendar) 無限往前後兩個方向延伸。這符合 Dershowitz 和 Reingold 在「
Calendrical Calculations」這本書定義的「逆推公曆」(proleptic Gregorian)，
是做所有計算的基礎日曆。0 及負數年份的解讀跟 ISO 8601 標準裡規定的一樣，
0 年是公元前 1 年，-1 年是公元前 2 年依此類推。

 -- 類別: calendar.Calendar (firstweekday=0)

     建立 *note Calendar: 2382. 物件。'firstweekday' 是一個指定一週第一
     天的整數，*note MONDAY: 2383. 是 ‘0’（預設值），*note SUNDAY: 2384.
     是 ‘6’。

     *note Calendar: 2382. 物件提供一些方法來為日曆資料的格式化做準備。
     這個類別本身不做任何格式化，這是子類別的工作。

     *note Calendar: 2382. 實例有以下方法：

      -- 方法: iterweekdays ()

          回傳一個以數字代表一週的每一天的疊代器 (iterator)。疊代器的第
          一個值和 *note firstweekday: 2386. 屬性的值一樣。

      -- 方法: itermonthdates (year, month)

          回傳一個在 'year' 年 'month' (1-12) 月的疊代器。這個疊代器會回
          傳該月的所有日期（*note datetime.date: 1b1. 物件）以及在該月之
          前及之後用來組成完整一週的日期。

      -- 方法: itermonthdays (year, month)

          類似 *note itermonthdates(): bc0.，回傳一個在 'year' 年
          'month' 月的疊代器，但不受限於 *note datetime.date: 1b1. 的範
          圍。回傳的日期單純是該月當日的數字，對於該月之外的日期數字會是
          ‘0’。

      -- 方法: itermonthdays2 (year, month)

          類似 *note itermonthdates(): bc0.，回傳一個在 'year' 年
          'month' 月的疊代器，但不受限於 *note datetime.date: 1b1. 的範
          圍。回傳的日期是一個由該月當日的數字及代表週幾的數字組成的元組
          。

      -- 方法: itermonthdays3 (year, month)

          類似 *note itermonthdates(): bc0.，回傳一個在 'year' 年
          'month' 月的疊代器，但不受限於 *note datetime.date: 1b1. 的範
          圍。回傳的日期是一個由年、月、日的數字組成的元組。

          在 3.7 版被加入.

      -- 方法: itermonthdays4 (year, month)

          類似 *note itermonthdates(): bc0.，回傳一個在 'year' 年
          'month' 月的疊代器，但不受限於 *note datetime.date: 1b1. 的範
          圍。回傳的日期是一個由年、月、日及代表週幾的數字組成的元組。

          在 3.7 版被加入.

      -- 方法: monthdatescalendar (year, month)

          回傳一個在 'year' 年 'month' 月每一週組成的串列。每一週是一個
          串列，包含七個 *note datetime.date: 1b1. 物件。

      -- 方法: monthdays2calendar (year, month)

          回傳一個在 'year' 年 'month' 月每一週組成的串列。每一週是一個
          串列，包含七個該月當日的數字及代表週幾的數字組成的元組。

      -- 方法: monthdayscalendar (year, month)

          回傳一個在 'year' 年 'month' 月每一週組成的串列。每一週是一個
          串列，包含七個該月當日的數字。

      -- 方法: yeardatescalendar (year, width=3)

          回傳用來格式化的指定年份的資料。回傳值是月份列的串列，每個月份
          列最多由 'width' 個月份組成（預設為 3）。每個月份包含四到六週
          ，每一週包含一到七天，每一天則是一個 *note datetime.date: 1b1.
          物件。

      -- 方法: yeardays2calendar (year, width=3)

          回傳用來格式化的指定年份的資料（類似 *note
          yeardatescalendar(): 238c.）。每一天是一個該月當日的數字及代表
          週幾的數字組成的元組，該月外的日期的該月當日數字為 0。

      -- 方法: yeardayscalendar (year, width=3)

          回傳用來格式化的指定年份的資料（類似 *note
          yeardatescalendar(): 238c.）。每一天是一個該月當日的數字，該月
          外的日期的該月當日數字為 0。

 -- 類別: calendar.TextCalendar (firstweekday=0)

     這個類別用來產生純文字的日曆。

     *note TextCalendar: 238f. 實例有以下方法：

      -- 方法: formatmonth (theyear, themonth, w=0, l=0)

          以多行字串的形式回傳一個月份的日曆。如果給定 'w'，它會指定置中
          的日期欄的寬度。如果給定 'l'，它會指定每一週使用的行數。這個日
          曆會依據在建構函式中指定或者透過 *note setfirstweekday():
          2381. 方法設定的一週的第一天來輸出。

      -- 方法: prmonth (theyear, themonth, w=0, l=0)

          印出一個月份的日曆，內容和 *note formatmonth(): 2390. 回傳的一
          樣。

      -- 方法: formatyear (theyear, w=2, l=1, c=6, m=3)

          以多行字串的形式回傳有 'm' 欄的一整年的日曆。可選的參數 'w'、
          'l' 及 'c' 分別是日期欄寬度、每週行數及月份欄中間的空白數。這
          個日曆會依據在建構函式中指定或者透過 *note setfirstweekday():
          2381. 方法設定的一週的第一天來輸出。最早可以產生日曆的年份會依
          據平台而不同。

      -- 方法: pryear (theyear, w=2, l=1, c=6, m=3)

          印出一整年的日曆，內容和 *note formatyear(): 2392. 回傳的一樣
          。

 -- 類別: calendar.HTMLCalendar (firstweekday=0)

     這個類別用來產生 HTML 日曆。

     ‘HTMLCalendar’ 實例有以下方法：

      -- 方法: formatmonth (theyear, themonth, withyear=True)

          以 HTML 表格的形式回傳一個月份的日曆。如果 'withyear' 是 true
          則標題會包含年份，否則只會有月份名稱。

      -- 方法: formatyear (theyear, width=3)

          以 HTML 表格的形式回傳一整年的日曆。'width'（預設為 3）指定一
          列有幾個月。

      -- 方法: formatyearpage (theyear, width=3, css='calendar.css',
               encoding=None)

          以完整 HTML 頁面的形式回傳一整年的日曆。'width'（預設為 3）指
          定一列有幾個月。'css' 是要使用的 CSS (cascading style sheet) 名
          稱，可以給 *note None: 61b. 表示不使用任何 CSS。'encoding' 指
          定輸出使用的編碼（預設使用系統預設編碼）。

      -- 方法: formatmonthname (theyear, themonth, withyear=True)

          以 HTML 表列的形式回傳一個月份的名稱。如果 'withyear' 是 true
          則該列會包含年份，否則只會有月份名稱。

     ‘HTMLCalendar’ 可以覆寫以下屬性來客製日曆所使用的 CSS 類別：

      -- 屬性: cssclasses

          對應一週每一天 CSS 類別的串列。預設的串列內容為：

               cssclasses = ["mon", "tue", "wed", "thu", "fri", "sat", "sun"]

          可以針對每一天增加更多樣式：

               cssclasses = ["mon text-bold", "tue", "wed", "thu", "fri", "sat", "sun red"]

          注意這個串列的長度必須是七個項目。

      -- 屬性: cssclass_noday

          跟當月為同一週且屬於前一個或下一個月份的日期使用的 CSS 類別。

          在 3.7 版被加入.

      -- 屬性: cssclasses_weekday_head

          在標題列中一週每一天名稱的 CSS 類別的串列。預設內容和 *note
          cssclasses: 2398. 相同。

          在 3.7 版被加入.

      -- 屬性: cssclass_month_head

          月份標題的 CSS 類別（由 *note formatmonthname(): 2397. 所使用
          ），預設值是 ‘"month"’。

          在 3.7 版被加入.

      -- 屬性: cssclass_month

          整個月份表格的 CSS 類別（由 *note formatmonth(): 2394. 所使用
          ），預設值是 ‘"month"’。

          在 3.7 版被加入.

      -- 屬性: cssclass_year

          整年表格的 CSS 類別（由 *note formatyear(): 2395. 所使用），預
          設值是 ‘"year"’。

          在 3.7 版被加入.

      -- 屬性: cssclass_year_head

          整年表格標題的 CSS 類別（由 *note formatyear(): 2395. 所使用）
          ，預設值是 ‘"year"’。

          在 3.7 版被加入.

     注意雖然上面提到的 CSS 屬性名稱是單數（例如 ‘cssclass_month’、
     ‘cssclass_noday’），你可以使用多個以空格隔開的 CSS 類別取代單一 CSS
     類別，例如：

          "text-bold text-red"

     以下是客製化 ‘HTMLCalendar’ 的範例：

          class CustomHTMLCal(calendar.HTMLCalendar):
              cssclasses = [style + " text-nowrap" for style in
                            calendar.HTMLCalendar.cssclasses]
              cssclass_month_head = "text-center month-head"
              cssclass_month = "text-center month"
              cssclass_year = "text-italic lead"

 -- 類別: calendar.LocaleTextCalendar (firstweekday=0, locale=None)

     *note TextCalendar: 238f. 的子類別，可以在建構函式傳入語系名稱，它
     會回傳指定語系的月份及一週每一天的名稱。

 -- 類別: calendar.LocaleHTMLCalendar (firstweekday=0, locale=None)

     *note HTMLCalendar: ac7. 的子類別，可以在建構函式傳入語系名稱，它會
     回傳指定語系的月份及一週每一天的名稱。

     備註: 這兩個類別的建構函式、‘formatweekday()’ 及
     ‘formatmonthname()’ 方法會把 ‘LC_TIME’ 語系暫時改成給定的 'locale'。
     因為目前的語系是屬於整個行程 (process-wide) 的設定，它們不是執行緒
     安全的。

這個模組提供以下函式給單純的文字日曆使用。

 -- 函式: calendar.setfirstweekday (weekday)

     設定一週的第一天（‘0’ 是週一、‘6’ 是週日）。提供 *note MONDAY:
     2383.、*note TUESDAY: 239f.、*note WEDNESDAY: 23a0.、*note
     THURSDAY: 23a1.、*note FRIDAY: 23a2.、*note SATURDAY: 23a3. 及
     *note SUNDAY: 2384. 可以方便設定。例如設定一週的第一天為週日：

          import calendar
          calendar.setfirstweekday(calendar.SUNDAY)

 -- 函式: calendar.firstweekday ()

     回傳目前設定的一週的第一天。

 -- 函式: calendar.isleap (year)

     如果 'year' 是閏年回傳 *note True: bb4.，否則回傳 *note False:
     adb.。

 -- 函式: calendar.leapdays (y1, y2)

     回傳從 'y1' 到 'y2'（不包含）間有幾個閏年，其中 'y1' 和 'y2' 是年份
     。

     這個函式也適用在跨越世紀的時間範圍。

 -- 函式: calendar.weekday (year, month, day)

     回傳 'year' 年 (‘1970’-...)  'month' 月 (‘1’-‘12’) 'day' 日
     (‘1’-‘31’) 是週幾（‘0’ 是星期一）。

 -- 函式: calendar.weekheader (n)

     回傳包含一週每一天的名稱縮寫的標題。'n' 指定每一天的字元寬度。

 -- 函式: calendar.monthrange (year, month)

     回傳指定 'year' 年 'month' 月該月第一天代表週幾的數字及該月有多少天
     。

 -- 函式: calendar.monthcalendar (year, month)

     回傳代表一個月份日曆的矩陣。每一列為一週；該月以外的日期以 0 表示。
     每一週以週一開始，除非有使用 *note setfirstweekday(): 2381. 改變設
     定。

 -- 函式: calendar.prmonth (theyear, themonth, w=0, l=0)

     印出一個月份的日曆，跟 *note month(): 23ab. 回傳的內容一樣。

 -- 函式: calendar.month (theyear, themonth, w=0, l=0)

     以多行字串的形式回傳一個月的日曆，使用 *note TextCalendar: 238f. 類
     別的 *note formatmonth(): 2390.。

 -- 函式: calendar.prcal (year, w=0, l=0, c=6, m=3)

     印出一整年的日曆，跟 *note calendar(): 10. 回傳的內容一樣。

 -- 函式: calendar.calendar (year, w=2, l=1, c=6, m=3)

     以多行字串回傳三欄形式的一整年日曆，使用 *note TextCalendar: 238f.
     類別的 *note formatyear(): 2392.。

 -- 函式: calendar.timegm (tuple)

     一個跟日曆無關但方便的函式，它接受一個像 *note time: d7. 模組裡的
     *note gmtime(): 1158. 函式回傳的元組，並回傳對應的 Unix 時間戳，假
     設從 1970 開始及 POSIX 編碼。事實上，*note time.gmtime(): 1158. 和
     *note timegm(): 23ae. 是彼此相反的。

*note calendar: 10. 模組匯出以下資料屬性：

 -- 資料: calendar.day_name

     以目前語系來表示的一週每一天名稱的陣列。

 -- 資料: calendar.day_abbr

     以目前語系來表示的一週每一天縮寫名稱的陣列。

 -- 資料: calendar.MONDAY
 -- 資料: calendar.TUESDAY
 -- 資料: calendar.WEDNESDAY
 -- 資料: calendar.THURSDAY
 -- 資料: calendar.FRIDAY
 -- 資料: calendar.SATURDAY
 -- 資料: calendar.SUNDAY

     一週每一天的別名，其中 ‘MONDAY’ 是 ‘0’ 而 ‘SUNDAY’ 是 ‘6’。

     在 3.12 版被加入.

 -- 類別: calendar.Day

     將一週中的幾天定義為整數常數的列舉。此列舉的成員將作為 *note
     MONDAY: 2383. 到 *note SUNDAY: 2384. 匯出到模組作用域。

     在 3.12 版被加入.

 -- 資料: calendar.month_name

     以目前語系來表示的一年每個月份名稱的陣列。它按照一般慣例以數字 1 代
     表一月，因此它的長度為 13，而 ‘month_name[0]’ 是空字串。

 -- 資料: calendar.month_abbr

     以目前語系來表示的一年每個月份縮寫名稱的陣列。它按照一般慣例以數字
     1 代表一月，因此它的長度為 13，而 ‘month_abbr[0]’ 是空字串。

 -- 資料: calendar.JANUARY
 -- 資料: calendar.FEBRUARY
 -- 資料: calendar.MARCH
 -- 資料: calendar.APRIL
 -- 資料: calendar.MAY
 -- 資料: calendar.JUNE
 -- 資料: calendar.JULY
 -- 資料: calendar.AUGUST
 -- 資料: calendar.SEPTEMBER
 -- 資料: calendar.OCTOBER
 -- 資料: calendar.NOVEMBER
 -- 資料: calendar.DECEMBER

     一年內每個月的別名，其中 ‘JANUARY’ 是 ‘ㄅ’ 而 ‘DECEMBER’ 是 ‘12’。

     在 3.12 版被加入.

 -- 類別: calendar.Month

     將一年中的月份定義為整數常數的列舉。此列舉的成員將作為 *note
     JANUARY: 2ca. 到 *note DECEMBER: 23bc. 匯出到模組作用域。

     在 3.12 版被加入.

*note calendar: 10. 模組定義了以下例外：

 -- 例外: calendar.IllegalMonthError (month)

     *note ValueError: 1e7. 的子類別，當給定的月份數字超出 1-12 範圍（含
     ）時引發。

      -- 屬性: month

          無效的月份號。

 -- 例外: calendar.IllegalWeekdayError (weekday)

     *note ValueError: 1e7. 的子類別，當給定的週幾的數字超出 0-6（含）範
     圍時引發。

      -- 屬性: weekday

          無效的週幾編號。

也參考
......

*note datetime: 28. 模組

     日期與時間的物件導向介面，和 *note time: d7. 模組有相似的功能。

*note time: d7. 模組

     底層的時間相關函式。

* Menu:

* 命令列用法::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/calendar.py


File: python.info,  Node: 命令列用法,  Up: calendar --- 日曆相關函式

5.8.3.1 命令列用法
..................

在 2.5 版被加入.

*note calendar: 10. 模組可以作為腳本從命令列執行，並以互動方式列印日曆。

     python -m calendar [-h] [-L LOCALE] [-e ENCODING] [-t {text,html}]
                        [-w WIDTH] [-l LINES] [-s SPACING] [-m MONTHS] [-c CSS]
                        [-f FIRST_WEEKDAY] [year] [month]

例如，要列印 2000 年的日曆：

     $ python -m calendar 2000
                                       2000

           January                   February                   March
     Mo Tu We Th Fr Sa Su      Mo Tu We Th Fr Sa Su      Mo Tu We Th Fr Sa Su
                     1  2          1  2  3  4  5  6             1  2  3  4  5
      3  4  5  6  7  8  9       7  8  9 10 11 12 13       6  7  8  9 10 11 12
     10 11 12 13 14 15 16      14 15 16 17 18 19 20      13 14 15 16 17 18 19
     17 18 19 20 21 22 23      21 22 23 24 25 26 27      20 21 22 23 24 25 26
     24 25 26 27 28 29 30      28 29                     27 28 29 30 31
     31

            April                      May                       June
     Mo Tu We Th Fr Sa Su      Mo Tu We Th Fr Sa Su      Mo Tu We Th Fr Sa Su
                     1  2       1  2  3  4  5  6  7                1  2  3  4
      3  4  5  6  7  8  9       8  9 10 11 12 13 14       5  6  7  8  9 10 11
     10 11 12 13 14 15 16      15 16 17 18 19 20 21      12 13 14 15 16 17 18
     17 18 19 20 21 22 23      22 23 24 25 26 27 28      19 20 21 22 23 24 25
     24 25 26 27 28 29 30      29 30 31                  26 27 28 29 30

             July                     August                  September
     Mo Tu We Th Fr Sa Su      Mo Tu We Th Fr Sa Su      Mo Tu We Th Fr Sa Su
                     1  2          1  2  3  4  5  6                   1  2  3
      3  4  5  6  7  8  9       7  8  9 10 11 12 13       4  5  6  7  8  9 10
     10 11 12 13 14 15 16      14 15 16 17 18 19 20      11 12 13 14 15 16 17
     17 18 19 20 21 22 23      21 22 23 24 25 26 27      18 19 20 21 22 23 24
     24 25 26 27 28 29 30      28 29 30 31               25 26 27 28 29 30
     31

           October                   November                  December
     Mo Tu We Th Fr Sa Su      Mo Tu We Th Fr Sa Su      Mo Tu We Th Fr Sa Su
                        1             1  2  3  4  5                   1  2  3
      2  3  4  5  6  7  8       6  7  8  9 10 11 12       4  5  6  7  8  9 10
      9 10 11 12 13 14 15      13 14 15 16 17 18 19      11 12 13 14 15 16 17
     16 17 18 19 20 21 22      20 21 22 23 24 25 26      18 19 20 21 22 23 24
     23 24 25 26 27 28 29      27 28 29 30               25 26 27 28 29 30 31
     30 31

接受以下選項：

 -- Option: --help, -h

     顯示幫助訊息並退出。

 -- Option: --locale LOCALE, -L LOCALE

     用於月份和週幾名稱的語系。預設為英語。

 -- Option: --encoding ENCODING, -e ENCODING

     用於輸出的編碼。如有設定 *note -locale: 23c5. 則必須給定 *note
     -encoding: 23c7.。

 -- Option: --type {text,html}, -t {text,html}

     將日曆以文字或 HTML 文件的形式印出到終端機。

 -- Option: --first-weekday FIRST_WEEKDAY, -f FIRST_WEEKDAY

     The weekday to start each week.  Must be a number between 0
     (Monday) and 6 (Sunday).  Defaults to 0.

     在 3.13 版被加入.

 -- Option: year

     The year to print the calendar for.  Defaults to the current year.

 -- Option: month

     要列印日曆的指定 *note year: 23cd. 的月份。必須是 1 到 12 之間的數
     字，並且只能在文字模式下使用。預設列印全年日曆。

'文字模式選項：'

 -- Option: --width WIDTH, -w WIDTH

     終端機行中日期行的寬度。日期印出在行的中央。任何小於 2 的值都會被忽
     略。預設為 2。

 -- Option: --lines LINES, -l LINES

     終端機列中每週的列數。日期印出時頂部會對齊。任何小於 1 的值都會被忽
     略。預設為 1。

 -- Option: --spacing SPACING, -s SPACING

     行中月份之間的間距。任何小於 2 的值都會被忽略。預設為 6。

 -- Option: --months MONTHS, -m MONTHS

     每列印出的月份數量。預設為 3。

'HTML 模式選項：'

 -- Option: --css CSS, -c CSS

     用於日曆的 CSS 樣式表路徑。這必須是相對於產生之 HTML 的，或者為絕對
     的 HTTP 或 ‘file:///’ URL。


File: python.info,  Node: collections --- 容器資料型態,  Next: collections abc --- 容器的抽象基底類別,  Prev: calendar --- 日曆相關函式,  Up: 資料型別

5.8.4 ‘collections’ -- 容器資料型態
-----------------------------------

'原始碼：'Lib/collections/__init__.py(1)

__________________________________________________________________

這個模組實作了一些特別的容器資料型態，用來替代 Python 一般內建的容器，例
如 *note dict: 23b.（字典）、*note list: 5b6.（串列）、*note set: 57d.（
集合）和 *note tuple: 322.（元組）。

*note namedtuple(): 1ae.  用來建立具名欄位的 tuple 子類別的工廠函式
                          
                          
*note deque: 580.         一個類似 list 的容器，可以快速的在頭尾加入 (append) 元素與移除 (pop) 元
                          素
                          
                          
*note ChainMap: bc3.      一個類似 dict 的類別，用來為多個對映 (mapping) 建立單一的視圖 (view)
                          
                          
*note Counter: 1033.      dict 的子類別，用來計算*note 可雜湊: 5b5.物件的數量
                          
                          
*note OrderedDict: 57f.   dict 的子類別，會記錄物件被加入的順序
                          
                          
*note defaultdict: 1155.  dict 的子類別，當值不存在 dict 中時會呼叫一個提供預設值的工廠函式
                          
                          
*note UserDict: 1898.     dict 物件的包裝器 (wrapper)，簡化了 dict 的子類別化過程
                          
                          
*note UserList: 1452.     list 物件的包裝器，簡化了 list 的子類別化過程
                          
                          
*note UserString: d7b.    字串物件的包裝器，簡化了字串的子類別化過程
                          

* Menu:

* ChainMap 物件::
* Counter 物件::
* deque 物件::
* defaultdict 物件::
* namedtuple() 擁有具名欄位之 tuple 的工廠函式: namedtuple 擁有具名欄位之 tuple 的工廠函式.
* OrderedDict 物件::
* UserDict 物件::
* UserList 物件::
* UserString 物件::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/collections/__init__.py


File: python.info,  Node: ChainMap 物件,  Next: Counter 物件,  Up: collections --- 容器資料型態

5.8.4.1 ‘ChainMap’ 物件
.......................

在 3.3 版被加入.

*note ChainMap: bc3.（對映鏈結）類別的目的是快速將數個對映連結在一起，讓
它們可以被當作一個單元來處理。它通常會比建立一個新的字典並多次呼叫 *note
update(): 13d0. 來得更快。

這個類別可用於模擬巢狀作用域 (nested scopes)，且在模板化 (templating) 時
能派上用場。

 -- 類別: collections.ChainMap (*maps)

     一個 *note ChainMap: bc3. 將多個 dict 或其他對映組合在一起，建立一
     個獨立、可更新的視圖。如果沒有指定 'maps'，預設會提供一個空字典讓每
     個新鏈結都至少有一個對映。

     底層的對映儲存於一個 list 中，這個 list 是公開的且可透過 'maps' 屬
     性存取或更新，沒有其他狀態 (state)。

     檢索 (lookup) 陸續查詢底層對映，直到鍵被找到，然而讀取、更新和刪除
     就只會對第一個對映操作。

     *note ChainMap: bc3. 透過參照將底層對映合併，所以當一個底層對映被更
     新，這些改變也會反映到 *note ChainMap: bc3.。

     所有常見的字典方法都有支援。此外，還有一個 'maps' 屬性 (attribute)、
     一個建立子上下文 (subcontext) 的方法、和一個能夠存取除了第一個以外
     其他所有對映的特性 (property)：

      -- 屬性: maps

          一個可被更新的對映列表，這個列表是按照被搜索的順序來排列，在
          ChainMap 中它是唯一被儲存的狀態，可被修改來變換搜索順序。回傳
          的列表都至少包含一個對映。

      -- 方法: new_child (m=None, **kwargs)

          回傳包含一個新對映的 *note ChainMap: bc3.， 新對映後面接著當前
          實例的所有現存對映。如果有給定 ‘m’，‘m’ 會成為那個最前面的新對
          映；若沒有指定，則會加上一個空 dict，如此一來呼叫
          ‘d.new_child()’ 就等同於 ‘ChainMap({}, *d.maps)’。這個方法用於
          建立子上下文，而保持父對映的不變。

          在 3.4 版的變更: 加入可選參數 ‘m’。

          在 3.10 版的變更: 增加了對關鍵字引數的支援。

      -- 屬性: parents

          回傳一個包含除了第一個以外所有其他對映的新 *note ChainMap:
          bc3. 的特性，可用於需要跳過第一個對映的搜索。使用情境類似於在
          *note 巢狀作用域: 2041.當中使用 *note nonlocal: 123e. 關鍵字，
          也可與內建函式 *note super(): 483. 做類比。引用 ‘d.parents’ 等
          同於 ‘ChainMap(*d.maps[1:])’。

     注意，一個 *note ChainMap: bc3. 的疊代順序是透過由後往前掃描對映而
     定：

          >>> baseline = {'music': 'bach', 'art': 'rembrandt'}
          >>> adjustments = {'art': 'van gogh', 'opera': 'carmen'}
          >>> list(ChainMap(adjustments, baseline))
          ['music', 'art', 'opera']

     這和呼叫 *note dict.update(): 13d0. 結果的順序一樣是從最後一個對映
     開始：

          >>> combined = baseline.copy()
          >>> combined.update(adjustments)
          >>> list(combined)
          ['music', 'art', 'opera']

     在 3.9 版的變更: 支援 ‘|’ 和 ‘|=’ 運算子，詳見 PEP 584(1)。

也參考
......

   * Enthought CodeTools package(2) 中的 MultiContext class(3) 支援在鏈
     中選定任意對映寫入。

   * Django 中用於模板的 Context class(4) 是唯讀的對映鏈，也具有加入
     (push) 和移除 (pop) 上下文的功能，與 *note new_child(): ec7. 方法和
     *note parents: 23dd. 特性類似。

   * Nested Contexts recipe(5) 提供了控制是否只對鏈中第一個或其他對映做
     寫入或其他操作的選項。

   * 一個極度簡化、維讀版本的 Chainmap(6)。

* Menu:

* ChainMap 範例和用法::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0584/

   (2) https://github.com/enthought/codetools

   (3) 
https://github.com/enthought/codetools/blob/4.0.0/codetools/contexts/multi_context.py

   (4) 
https://github.com/django/django/blob/main/django/template/context.py

   (5) 
https://code.activestate.com/recipes/577434-nested-contexts-a-chain-of-mapping-objects/

   (6) https://code.activestate.com/recipes/305268/


File: python.info,  Node: ChainMap 範例和用法,  Up: ChainMap 物件

5.8.4.2 ‘ChainMap’ 範例和用法
.............................

此章節提供了多種操作 ChainMap 的案例。

模擬 Python 內部檢索鏈結的例子：

     import builtins
     pylookup = ChainMap(locals(), globals(), vars(builtins))

讓使用者指定的命令列引數優先於環境變數、再優先於預設值的範例：

     import os, argparse

     defaults = {'color': 'red', 'user': 'guest'}

     parser = argparse.ArgumentParser()
     parser.add_argument('-u', '--user')
     parser.add_argument('-c', '--color')
     namespace = parser.parse_args()
     command_line_args = {k: v for k, v in vars(namespace).items() if v is not None}

     combined = ChainMap(command_line_args, os.environ, defaults)
     print(combined['color'])
     print(combined['user'])

用 *note ChainMap: bc3. 類別模擬巢狀上下文的範例模式：

     c = ChainMap()        # Create root context
     d = c.new_child()     # Create nested child context
     e = c.new_child()     # Child of c, independent from d
     e.maps[0]             # Current context dictionary -- like Python's locals()
     e.maps[-1]            # Root context -- like Python's globals()
     e.parents             # Enclosing context chain -- like Python's nonlocals

     d['x'] = 1            # Set value in current context
     d['x']                # Get first key in the chain of contexts
     del d['x']            # Delete from current context
     list(d)               # All nested values
     k in d                # Check all nested values
     len(d)                # Number of nested values
     d.items()             # All nested items
     dict(d)               # Flatten into a regular dictionary

*note ChainMap: bc3. 類別只對鏈結中第一個對映來做寫入或刪除，但檢索則會
掃過整個鏈結。但如果需要對更深層的鍵寫入或刪除，透過定義一個子類別來實作
也不困難：

     class DeepChainMap(ChainMap):
         'Variant of ChainMap that allows direct updates to inner scopes'

         def __setitem__(self, key, value):
             for mapping in self.maps:
                 if key in mapping:
                     mapping[key] = value
                     return
             self.maps[0][key] = value

         def __delitem__(self, key):
             for mapping in self.maps:
                 if key in mapping:
                     del mapping[key]
                     return
             raise KeyError(key)

     >>> d = DeepChainMap({'zebra': 'black'}, {'elephant': 'blue'}, {'lion': 'yellow'})
     >>> d['lion'] = 'orange'         # update an existing key two levels down
     >>> d['snake'] = 'red'           # new keys get added to the topmost dict
     >>> del d['elephant']            # remove an existing key one level down
     >>> d                            # display result
     DeepChainMap({'zebra': 'black', 'snake': 'red'}, {}, {'lion': 'orange'})


File: python.info,  Node: Counter 物件,  Next: deque 物件,  Prev: ChainMap 物件,  Up: collections --- 容器資料型態

5.8.4.3 ‘Counter’ 物件
......................

提供一個支援方便且快速計數的計數器工具，例如：

     >>> # Tally occurrences of words in a list
     >>> cnt = Counter()
     >>> for word in ['red', 'blue', 'red', 'green', 'blue', 'blue']:
     ...     cnt[word] += 1
     ...
     >>> cnt
     Counter({'blue': 3, 'red': 2, 'green': 1})

     >>> # Find the ten most common words in Hamlet
     >>> import re
     >>> words = re.findall(r'\w+', open('hamlet.txt').read().lower())
     >>> Counter(words).most_common(10)
     [('the', 1143), ('and', 966), ('to', 762), ('of', 669), ('i', 631),
      ('you', 554),  ('a', 546), ('my', 514), ('hamlet', 471), ('in', 451)]

 -- 類別: collections.Counter ([iterable-or-mapping])

     *note Counter: 1033. 是 *note dict: 23b. 的子類別，用來計算*note
     可雜湊: 5b5.物件的數量。它是將物件與其計數作為字典的鍵值對儲存的集
     合容器。計數可以是包含 0 與負數的任何整數值。*note Counter: 1033. 類
     別類似其他程式語言中的 bags 或 multisets。

     被計數的元素來自一個 'iterable' 或是被其他的 'mapping'（或 Counter）
     初始化：

          >>> c = Counter()                           # a new, empty counter
          >>> c = Counter('gallahad')                 # a new counter from an iterable
          >>> c = Counter({'red': 4, 'blue': 2})      # a new counter from a mapping
          >>> c = Counter(cats=4, dogs=8)             # a new counter from keyword args

     Counter 物件擁有一個字典的使用介面，除了遇到 Counter 中沒有的值時會
     回傳計數 0 取代 *note KeyError: 2fb. 這點不同：

          >>> c = Counter(['eggs', 'ham'])
          >>> c['bacon']                              # count of a missing element is zero
          0

     將一個值的計數設為 0 並不會真的從 Counter 中刪除這個元素，要使用
     ‘del’ 來將其刪除：

          >>> c['sausage'] = 0                        # counter entry with a zero count
          >>> del c['sausage']                        # del actually removes the entry

     在 3.1 版被加入.

     在 3.7 版的變更: 作為 *note dict: 23b. 的子類別，*note Counter:
     1033. 繼承了記憶插入順序的功能。對 'Counter' 做數學運算後同樣保留順
     序性，其結果是依照各個元素在運算元左邊出現的時間先後、再按照運算元
     右邊出現的時間先後來排列。

     除了字典原本就有的方法外，Counter 物件額外支援數個新方法：

      -- 方法: elements ()

          回傳每個元素都重複出現計算次數的 iterator（疊代器）物件，其中
          元素的回傳順序是依照各元素首次出現的時間先後。如果元素的出現次
          數小於 1，*note elements(): 1297. 方法會忽略這些元素。

               >>> c = Counter(a=4, b=2, c=0, d=-2)
               >>> sorted(c.elements())
               ['a', 'a', 'a', 'a', 'b', 'b']

      -- 方法: most_common ([n])

          回傳一個 list，包含出現最多次的 'n' 個元素及其出現次數，並按照
          出現次數排序。如果 'n' 被省略或者為 ‘None’，*note
          most_common(): 1296. 會回傳'所有' counter 中的元素。出現次數相
          同的元素會按照首次出現的時間先後來排列：

               >>> Counter('abracadabra').most_common(3)
               [('a', 5), ('b', 2), ('r', 2)]

      -- 方法: subtract ([iterable-or-mapping])

          減去自一個 'iterable' 或另一個'對映'（或 Counter）中的計數元素
          ，行為類似 *note dict.update(): 13d0. 但是是為了減去計數而非取
          代其值。輸入和輸出都可以是 0 或是負數。

               >>> c = Counter(a=4, b=2, c=0, d=-2)
               >>> d = Counter(a=1, b=2, c=3, d=4)
               >>> c.subtract(d)
               >>> c
               Counter({'a': 3, 'b': 0, 'c': -3, 'd': -6})

          在 3.2 版被加入.

      -- 方法: total ()

          計算總計數值。

               >>> c = Counter(a=10, b=5, c=0)
               >>> c.total()
               15

          在 3.10 版被加入.

     通常來說字典方法也可以用於 *note Counter: 1033. 物件，除了以下兩個
     作用方式與計數器不同。

      -- 方法: fromkeys (iterable)

          此類別方法沒有被實作於 *note Counter: 1033. 物件中。

      -- 方法: update ([iterable-or-mapping])

          加上自一個 'iterable' 計算出的計數或加上另一個 'mapping'（或
          Counter）中的計數，行為類似 *note dict.update(): 13d0. 但是是
          為了加上計數而非取代其值。另外，'iterable' 需要是一串將被計算
          個數元素的序列，而非元素為 ‘(key, value)’ 形式的序列。

Counter 支援相等性、子集和超集關係的 rich comparison 運算子：‘==’、
‘!=’、‘<’、‘<=’、‘>’、‘>=’。這些檢測會將不存在的元素之計數值當作零，因此
‘Counter(a=1) == Counter(a=1, b=0)’ 將回傳真值。

在 3.10 版的變更: 增加了 rich comparison 運算。

在 3.10 版的變更: 在相等性運算中，不存在的元素之計數值會被當作零。在此之
前，‘Counter(a=3)’ 和 ‘Counter(a=3, b=0)’ 被視為不同。

使用 *note Counter: 1033. 物件的常見使用模式：

     c.total()                       # total of all counts
     c.clear()                       # reset all counts
     list(c)                         # list unique elements
     set(c)                          # convert to a set
     dict(c)                         # convert to a regular dictionary
     c.items()                       # access the (elem, cnt) pairs
     Counter(dict(list_of_pairs))    # convert from a list of (elem, cnt) pairs
     c.most_common()[:-n-1:-1]       # n least common elements
     +c                              # remove zero and negative counts

為結合多個 *note Counter: 1033. 物件以產生 multiset（多重集合，擁有大於
0 計數元素的計數器），有提供了幾種數學操作。加法和減法是根據各個對應元素
分別將 Counter 加上和減去計數，交集和聯集分別回傳各個元素最小和最大計數
，相等性與包含性運算則會比較對應的計數。每一個操作都可以接受輸入帶有正負
號的計數，但輸出的 Counter 則會將擁有小於或等於 0 計數的元素剔除。

     >>> c = Counter(a=3, b=1)
     >>> d = Counter(a=1, b=2)
     >>> c + d                       # add two counters together:  c[x] + d[x]
     Counter({'a': 4, 'b': 3})
     >>> c - d                       # subtract (keeping only positive counts)
     Counter({'a': 2})
     >>> c & d                       # intersection:  min(c[x], d[x])
     Counter({'a': 1, 'b': 1})
     >>> c | d                       # union:  max(c[x], d[x])
     Counter({'a': 3, 'b': 2})
     >>> c == d                      # equality:  c[x] == d[x]
     False
     >>> c <= d                      # inclusion:  c[x] <= d[x]
     False

加減法的一元運算子分別是加上空的 Counter 和從空 Counter 減去的簡寫。

     >>> c = Counter(a=2, b=-4)
     >>> +c
     Counter({'a': 2})
     >>> -c
     Counter({'b': 4})

在 3.3 版被加入: 開始支援加減一元運算子和 multiset 的原地 (in-place) 操
作。

     備註: Counter 主要是被設計來操作正整數以當作使用中的計數，但為了某
     些會用到計數之值為負數或為其他型別的案例中，Counter 也小心地被設計
     成不會預先排除這些特殊元素。為了輔助使用於上述案例，這一小節記錄了
     最小範圍和型別限制。

        * *note Counter: 1033. 類別本身是字典的子類別，且不限制其鍵與值
          。值被用來表示計數，但實際上你'可以'儲存任何值。

        * 使用 *note most_common(): 1296. 方法的唯一條件是其值要是可被排
          序的。

        * 像是 ‘c[key] += 1’ 的原地操作中，其值之型別只必須支援加減，所
          以分數、浮點數、十進位數與其負值都可以使用。同理，*note
          update(): 23e2. 和 *note subtract(): 1176. 也都允許 0 或負值為
          輸入或輸出。

        * Multiset 相關方法只為了處理正值而設計，其輸入允許是 0 或負值但
          只有正值會被輸出。並無型別限制，但其值的型別須支援加、減及比較
          運算。

        * *note elements(): 1297. 方法需要其計數為正值，如為 0 或負值則
          忽略。

也參考
......

   * Smalltalk 中的 Bag class(1)。

   * 維基百科上的多重集合(2)條目。

   * C++ multisets(3) 教學與範例。

   * Multiset 的數學運算及其使用時機，參考 'Knuth, Donald.  The Art of
     Computer Programming Volume II, Section 4.6.3, Exercise 19'。

   * 若要根據給定的元素集合來列舉出所有不重複且擁有指定元素數量的
     multiset，請見 *note itertools.combinations_with_replacement():
     1219.：

          map(Counter, combinations_with_replacement('ABC', 2)) # --> AA AB AC BB BC CC

   ---------- Footnotes ----------

   (1) 
https://www.gnu.org/software/smalltalk/manual-base/html_node/Bag.html

   (2) https://en.wikipedia.org/wiki/Multiset

   (3) 
http://www.java2s.com/Tutorial/Cpp/0380__set-multiset/Catalog0380__set-multiset.htm


File: python.info,  Node: deque 物件,  Next: defaultdict 物件,  Prev: Counter 物件,  Up: collections --- 容器資料型態

5.8.4.4 ‘deque’ 物件
....................

 -- 類別: collections.deque ([iterable[, maxlen]])

     回傳一個新的 deque（雙端佇列）物件，將 'iterable' 中的資料由左至右
     （使用 *note append(): 23e4.）加入來做初始化。如果 'iterable' 並未
     給定，回傳的則是一個空的 deque。

     Deque（發音為 "deck"，為 "double-ended queue" 的簡稱）為 stack 和
     queue 的一般化。deque 支援執行緒安全 (thread-safe)，且能夠有效率地
     節省記憶體在頭和尾加入和移除元素，兩個方向的表現都大致為 'O'(1) 複
     雜度。

     雖然 *note list: 5b6. 物件也支援類似操作，但 list 優化了長度固定時
     的操作，而會改變底層資料的長度及位置的 ‘pop(0)’ 和 ‘insert(0, v)’ 操
     作，記憶體移動則為 'O'('n') 複雜度。

     如果 'maxlen' 沒有給定或者為 ‘None’，deque 可以增長到任意長度；但若
     有給定的話，deque 的最大長度就會被限制。一個被限制長度的 deque 一但
     滿了，若在一端加入數個新元素，則同時會在另一端移除相同數量的元素。
     限定長度的 deque 提供了和 Unix ‘tail’ filter 類似的功能，可用於追蹤
     使用者在意的那些最新執行事項或數據源。

     Deque 物件支援以下方法：

      -- 方法: append (x)

          將 'x' 自 deque 的右側加入。

      -- 方法: appendleft (x)

          將 'x' 自 deque 的左側加入。

      -- 方法: clear ()

          將所有元素從 deque 中移除，使其長度為 0。

      -- 方法: copy ()

          建立一個 deque 的淺複製 (shallow copy)。

          在 3.5 版被加入.

      -- 方法: count (x)

          計算 deque 內元素為 'x' 的個數。

          在 3.2 版被加入.

      -- 方法: extend (iterable)

          將 iterable 引數加入 deque 的右側。

      -- 方法: extendleft (iterable)

          將 iterable 引數加入 deque 的左側。要注意的是，加入後的元素順
          序和 iterable 參數是相反的。

      -- 方法: index (x[, start[, stop]])

          回傳 deque 中 'x' 的位置（或在索引 'start' 之後、索引 'stop' 之
          前的位置）。回傳第一個匹配的位置，如果沒找到就引發 *note
          ValueError: 1e7.。

          在 3.5 版被加入.

      -- 方法: insert (i, x)

          在 deque 位置 'i' 中插入 'x'。

          如果此插入操作導致 deque 超過其長度上限 'maxlen' 的話，會引發
          *note IndexError: 14a3. 例外。

          在 3.5 版被加入.

      -- 方法: pop ()

          移除並回傳 deque 的最右側元素，若本來就沒有任何元素，則會引發
          *note IndexError: 14a3.。

      -- 方法: popleft ()

          移除並回傳 deque 的最左側元素，若本來就沒有任何元素，則會引發
          *note IndexError: 14a3.。

      -- 方法: remove (value)

          移除第一個出現的 'value'，如果沒找到的話就引發一個 *note
          ValueError: 1e7.。

      -- 方法: reverse ()

          將 deque 中的元素原地 (in-place) 倒序排列並回傳 ‘None’。

          在 3.2 版被加入.

      -- 方法: rotate (n=1)

          將 deque 向右輪轉 'n' 步。若 'n' 為負值則向左輪轉。

          當 deque 不是空的，向右輪轉一步和 ‘d.appendleft(d.pop())’ 有相
          同意義，而向左輪轉亦等價於 ‘d.append(d.popleft())’。

     Deque 物件也提供了一個唯讀屬性：

      -- 屬性: maxlen

          Deque 的最大長度，如果不限制長度的話則為 ‘None’。

          在 3.1 版被加入.

除了以上使用方式，deque 亦支援了疊代、pickle、‘len(d)’、‘reversed(d)’、
‘copy.copy(d)’、‘copy.deepcopy(d)’、用 *note in: 2c5. 運算子來作隸屬資格
檢測以及像是 ‘d[0]’ 的標號引用來取得第一個元素。在兩端做索引存取的複雜度
為 'O'(1) 但越靠近中間則減慢至 'O'('n')。若想要隨機而快速的存取，使用
list 會較為合適。

自從 3.5 版本起，deque 開始支援 ‘__add__()’、‘__mul__()’ 和
‘__imul__()’。

範例：

     >>> from collections import deque
     >>> d = deque('ghi')                 # make a new deque with three items
     >>> for elem in d:                   # iterate over the deque's elements
     ...     print(elem.upper())
     G
     H
     I

     >>> d.append('j')                    # add a new entry to the right side
     >>> d.appendleft('f')                # add a new entry to the left side
     >>> d                                # show the representation of the deque
     deque(['f', 'g', 'h', 'i', 'j'])

     >>> d.pop()                          # return and remove the rightmost item
     'j'
     >>> d.popleft()                      # return and remove the leftmost item
     'f'
     >>> list(d)                          # list the contents of the deque
     ['g', 'h', 'i']
     >>> d[0]                             # peek at leftmost item
     'g'
     >>> d[-1]                            # peek at rightmost item
     'i'

     >>> list(reversed(d))                # list the contents of a deque in reverse
     ['i', 'h', 'g']
     >>> 'h' in d                         # search the deque
     True
     >>> d.extend('jkl')                  # add multiple elements at once
     >>> d
     deque(['g', 'h', 'i', 'j', 'k', 'l'])
     >>> d.rotate(1)                      # right rotation
     >>> d
     deque(['l', 'g', 'h', 'i', 'j', 'k'])
     >>> d.rotate(-1)                     # left rotation
     >>> d
     deque(['g', 'h', 'i', 'j', 'k', 'l'])

     >>> deque(reversed(d))               # make a new deque in reverse order
     deque(['l', 'k', 'j', 'i', 'h', 'g'])
     >>> d.clear()                        # empty the deque
     >>> d.pop()                          # cannot pop from an empty deque
     Traceback (most recent call last):
         File "<pyshell#6>", line 1, in -toplevel-
             d.pop()
     IndexError: pop from an empty deque

     >>> d.extendleft('abc')              # extendleft() reverses the input order
     >>> d
     deque(['c', 'b', 'a'])

* Menu:

* deque 用法::


File: python.info,  Node: deque 用法,  Up: deque 物件

5.8.4.5 ‘deque’ 用法
....................

這一章節提供了多種操作 deque 的案例。

被限制長度的 deque 功能類似 Unix 中的 ‘tail’ filter：

     def tail(filename, n=10):
         'Return the last n lines of a file'
         with open(filename) as f:
             return deque(f, n)

另一用法是透過從右邊加入、從左邊移除來維護最近加入元素的 list：

     def moving_average(iterable, n=3):
         # moving_average([40, 30, 50, 46, 39, 44]) --> 40.0 42.0 45.0 43.0
         # https://en.wikipedia.org/wiki/Moving_average
         it = iter(iterable)
         d = deque(itertools.islice(it, n-1))
         d.appendleft(0)
         s = sum(d)
         for elem in it:
             s += elem - d.popleft()
             d.append(elem)
             yield s / n

一個輪詢調度器(1)可以透過在 *note deque: 580. 中放入 iterator 來實現，值
自當前 iterator 的位置 0 取出，如果 iterator 已經消耗完畢就用 *note
popleft(): 23ea. 將其從佇列中移除，否則利用 *note rotate(): 17d9. 來將其
移至佇列尾端：

     def roundrobin(*iterables):
         "roundrobin('ABC', 'D', 'EF') --> A D E B F C"
         iterators = deque(map(iter, iterables))
         while iterators:
             try:
                 while True:
                     yield next(iterators[0])
                     iterators.rotate(-1)
             except StopIteration:
                 # Remove an exhausted iterator.
                 iterators.popleft()

*note rotate(): 17d9. 提供了可以用來實作 *note deque: 580. 切片和刪除的
方法。舉例來說，用純 Python 實作 ‘del d[n]’ 需要用 ‘rotate()’ 來定位要被
移除的元素：

     def delete_nth(d, n):
         d.rotate(-n)
         d.popleft()
         d.rotate(n)

要實現 *note deque: 580. 切片，可使用近似以下方法：使用 *note rotate():
17d9. 來將目標元素移動到 deque 最左側，用 *note popleft(): 23ea. 移除舊
元素並用 *note extend(): 23e7. 加入新元素，最後再反向 rotate。在這個方法
上做小小的更動就能簡單地實現 Forth 風格的 stack 操作，例如 ‘dup’、
‘drop’、‘swap’、‘over’、‘pick’、‘rot’ 和 ‘roll’。

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Round-robin_scheduling


File: python.info,  Node: defaultdict 物件,  Next: namedtuple 擁有具名欄位之 tuple 的工廠函式,  Prev: deque 物件,  Up: collections --- 容器資料型態

5.8.4.6 ‘defaultdict’ 物件
..........................

 -- 類別: collections.defaultdict (default_factory=None, /[, ...])

     回傳一個新的類似字典的物件。*note defaultdict: 1155. 是內建類別
     *note dict: 23b. 的子類別。它覆蓋掉了一個方法並添加了一個可寫入的實
     例變數。其餘功能與 *note dict: 23b. 相同，此文件不再複述。

     第一個引數為 *note default_factory: 23ed. 屬性提供了初始值，他被預
     設為 ‘None’，所有其他的引數（包括關鍵字引數）都會被傳遞給 *note
     dict: 23b. 的建構函式 (constructor)。

     *note defaultdict: 1155. 物件支援以下 *note dict: 23b. 所沒有的方法
     ：

      -- 方法: __missing__ (key)

          如果 *note default_factory: 23ed. 屬性為 ‘None’，呼叫此方法會
          引發一個附帶引數 'key' 的 *note KeyError: 2fb. 例外。

          如果 *note default_factory: 23ed. 不為 ‘None’，它會不帶引數地
          被呼叫來為給定的 'key' 提供一個預設值，這個值和 'key' 被作為鍵
          值對來插入到字典中，並且被此方法所回傳。

          如果呼叫 *note default_factory: 23ed. 時發生例外，則該例外將會
          保持不變地向外傳遞。

          在無法找到所要求的鍵時，此方法會被 *note dict: 23b. 類別的
          *note __getitem__(): 266. 方法呼叫。無論此方法回傳了值還是引發
          了例外，都會被 *note __getitem__(): 266. 所傳遞。

          注意，*note __missing__(): 23ee. '不會'被 *note __getitem__():
          266. 以外的其他方法呼叫，這意味著 ‘get()’ 會像一般的 dict 那樣
          回傳 ‘None’ 做為預設值，而非使用 *note default_factory: 23ed.。

     *note defaultdict: 1155. 物件支援以下實例變數：

      -- 屬性: default_factory

          此屬性為 *note __missing__(): 23ee. 方法所使用。如果有引數被傳
          入建構函式，則此屬性會被初始化成第一個引數，如未提供引數則被初
          始化為 ‘None’。

     在 3.9 版的變更: 新增合併 (‘|’) 和更新 (‘|=’) 運算子，請見 PEP
     584(1)。

* Menu:

* defaultdict 範例::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0584/


File: python.info,  Node: defaultdict 範例,  Up: defaultdict 物件

5.8.4.7 ‘defaultdict’ 範例
..........................

使用 *note list: 5b6. 作為 *note default_factory: 23ed. 可以很輕鬆地將鍵
值對序列轉換為包含 list 之字典：

     >>> s = [('yellow', 1), ('blue', 2), ('yellow', 3), ('blue', 4), ('red', 1)]
     >>> d = defaultdict(list)
     >>> for k, v in s:
     ...     d[k].append(v)
     ...
     >>> sorted(d.items())
     [('blue', [2, 4]), ('red', [1]), ('yellow', [1, 3])]

當每個鍵第一次被存取時，它還沒有存在於對映中，所以會自動呼叫 *note
default_factory: 23ed. 方法來回傳一個空的 *note list: 5b6. 以建立一個條
目，‘list.append()’ 操作後續會再新增值到這個新的列表裡。當再次存取該鍵時
，就如普通字典般操作（回傳該鍵所對應到的 list），‘list.append()’ 也會新
增另一個值到 list 中。和使用與其等價的 *note dict.setdefault(): 101a. 相
比，這個技巧更加快速和簡單：

     >>> d = {}
     >>> for k, v in s:
     ...     d.setdefault(k, []).append(v)
     ...
     >>> sorted(d.items())
     [('blue', [2, 4]), ('red', [1]), ('yellow', [1, 3])]

設定 *note default_factory: 23ed. 為 *note int: 23c. 使得 *note
defaultdict: 1155. 可被用於計數（類似其他語言中的 bag 或 multiset）：

     >>> s = 'mississippi'
     >>> d = defaultdict(int)
     >>> for k in s:
     ...     d[k] += 1
     ...
     >>> sorted(d.items())
     [('i', 4), ('m', 1), ('p', 2), ('s', 4)]

當一個字母首次被存取時，它並不存在於對映中，則 *note default_factory:
23ed. 函式會呼叫 *note int(): 23c. 來提供一個整數 0 作為預設值。後續的增
加操作繼續對每個字母做計數。

函式 *note int(): 23c. 總是回傳 0，這是常數函式的特殊情況。一個更快、更
有彈性的方法是使用 lambda 函式來提供任何常數值（不用一定要是 0）：

     >>> def constant_factory(value):
     ...     return lambda: value
     ...
     >>> d = defaultdict(constant_factory('<missing>'))
     >>> d.update(name='John', action='ran')
     >>> '%(name)s %(action)s to %(object)s' % d
     'John ran to <missing>'

將 *note default_factory: 23ed. 設為 *note set: 57d. 使 *note
defaultdict: 1155. 可用於構建一個值為 set 的字典：

     >>> s = [('red', 1), ('blue', 2), ('red', 3), ('blue', 4), ('red', 1), ('blue', 4)]
     >>> d = defaultdict(set)
     >>> for k, v in s:
     ...     d[k].add(v)
     ...
     >>> sorted(d.items())
     [('blue', {2, 4}), ('red', {1, 3})]


File: python.info,  Node: namedtuple 擁有具名欄位之 tuple 的工廠函式,  Next: OrderedDict 物件,  Prev: defaultdict 物件,  Up: collections --- 容器資料型態

5.8.4.8 ‘namedtuple()’ 擁有具名欄位之 tuple 的工廠函式
......................................................

Named tuple（具名元組）賦予 tuple 中各個位置意義，使程式碼更有可讀性與自
我文件性。它們可以用於任何普通 tuple 可使用的場合，賦予其透過名稱（而非
位置索引）來存取欄位的能力。

 -- 函式: collections.namedtuple (typename, field_names, *,
          rename=False, defaults=None, module=None)

     回傳一個名為 'typename' 的新 tuple 子類別。這個新的子類別被用於建立
     類似 tuple 的物件，可以透過屬性名稱來存取欄位，它同時也是可索引
     (indexable) 和可疊代的 (iterable)。子類別實例同樣有文件字串
     (docstring)（有類別名 typename 和欄位名 field_names）和一個好用的
     ‘__repr__()’ 方法，可將 tuple 內容以 ‘name=value’ 格式列出。

     'field_names' 是一個像 ‘['x', 'y']’ 一樣的字串序列。'field_names' 也
     可以是一個用空白或逗號分隔各個欄位名稱的字串，比如 ‘'x y'’ 或者
     ‘'x, y'’。

     除了底線開頭以外的其他任何有效 Python 識別字 (identifier) 都可以作
     為欄位名稱，有效識別字由字母、數字、底線所組成，但不能是數字或底線
     開頭，也不能是關鍵詞 *note keyword: 78.，例如 'class'、'for'、
     'return'、'global'、'pass' 或 'raise'。

     如果 'rename' 為真值，無效的欄位名稱會自動被位置名稱取代。比如
     ‘['abc', 'def', 'ghi', 'abc']’ 會被轉換成 ‘['abc', '_1', 'ghi',
     '_3']’，移除了關鍵字 ‘def’ 和重複欄位名 ‘abc’。

     'defaults' 可以為 ‘None’ 或者是一個預設值的 *note iterable: 11bf.。
     因為有預設值的欄位必須出現在那些沒有預設值的欄位之後，'defaults' 是
     被應用在右側的引數。例如 fieldnames 為 ‘['x', 'y', 'z']’ 且
     defaults 為 ‘(1, 2)’，那麼 ‘x’ 就必須被給定一個引數，‘y’ 被預設為
     ‘1’，‘z’ 則被預設為 ‘2’。

     如果 'module' 值有被定義，named tuple 的 ‘__module__’ 屬性就被設定
     為該值。

     Named tuple 實例中沒有字典，所以它們更加輕量，且和一般 tuple 相比佔
     用更少記憶體。

     要支援 pickle，應將 named tuple 類別賦值給一個符合 'typename' 的變
     數。

     在 3.1 版的變更: 新增對於 'rename' 的支援。

     在 3.6 版的變更: 'verbose' 和 'rename' 參數成為*note
     僅限關鍵字引數: 285.。

     在 3.6 版的變更: 新增 'module' 參數。

     在 3.7 版的變更: 移除 'verbose' 參數和 ‘_source’ 屬性。

     在 3.7 版的變更: 新增 'defaults' 參數和 ‘_field_defaults’ 屬性。

     >>> # Basic example
     >>> Point = namedtuple('Point', ['x', 'y'])
     >>> p = Point(11, y=22)     # instantiate with positional or keyword arguments
     >>> p[0] + p[1]             # indexable like the plain tuple (11, 22)
     33
     >>> x, y = p                # unpack like a regular tuple
     >>> x, y
     (11, 22)
     >>> p.x + p.y               # fields also accessible by name
     33
     >>> p                       # readable __repr__ with a name=value style
     Point(x=11, y=22)

Named tuple 在賦予欄位名稱於 *note csv: 21. 或 *note sqlite3: ba. 模組回
傳之 tuple 時相當有用：

     EmployeeRecord = namedtuple('EmployeeRecord', 'name, age, title, department, paygrade')

     import csv
     for emp in map(EmployeeRecord._make, csv.reader(open("employees.csv", "rb"))):
         print(emp.name, emp.title)

     import sqlite3
     conn = sqlite3.connect('/companydata')
     cursor = conn.cursor()
     cursor.execute('SELECT name, age, title, department, paygrade FROM employees')
     for emp in map(EmployeeRecord._make, cursor.fetchall()):
         print(emp.name, emp.title)

除了繼承自 tuple 的方法，named tuple 還支援三個額外的方法和兩個屬性。為
了防止欄位名稱有衝突，方法和屬性的名稱以底線開頭。

 -- 方法: classmethod somenamedtuple._make (iterable)

     從已存在的序列或可疊代物件建立一個新實例的類別方法。

          >>> t = [11, 22]
          >>> Point._make(t)
          Point(x=11, y=22)

 -- 方法: somenamedtuple._asdict ()

     回傳一個將欄位名稱對映至對應值的 *note dict: 23b.：

          >>> p = Point(x=11, y=22)
          >>> p._asdict()
          {'x': 11, 'y': 22}

     在 3.1 版的變更: 回傳一個 *note OrderedDict: 57f. 而非 *note dict:
     23b.。

     在 3.8 版的變更: 回傳一個常規 *note dict: 23b. 而非 *note
     OrderedDict: 57f.，自從 Python 3.7 開始，dict 已經保證有順序性，如
     果需要 *note OrderedDict: 57f. 所專屬的特性，推薦的解法是將結果專換
     成所需的類型：‘OrderedDict(nt._asdict())’。

 -- 方法: somenamedtuple._replace (**kwargs)

     回傳一個新的 named tuple 實例，並將指定欄位替換為新的值：

          >>> p = Point(x=11, y=22)
          >>> p._replace(x=33)
          Point(x=33, y=22)

          >>> for partnum, record in inventory.items():
          ...     inventory[partnum] = record._replace(price=newprices[partnum], timestamp=time.now())

     Named tuples are also supported by generic function *note
     copy.replace(): 136.

     在 3.13 版的變更: Raise *note TypeError: 4dd. instead of *note
     ValueError: 1e7. for invalid keyword arguments.

 -- 屬性: somenamedtuple._fields

     列出 tuple 欄位名稱的字串，用於自我檢查或是從現有 named tuple 建立
     一個新的 named tuple 型別。

          >>> p._fields            # view the field names
          ('x', 'y')

          >>> Color = namedtuple('Color', 'red green blue')
          >>> Pixel = namedtuple('Pixel', Point._fields + Color._fields)
          >>> Pixel(11, 22, 128, 255, 0)
          Pixel(x=11, y=22, red=128, green=255, blue=0)

 -- 屬性: somenamedtuple._field_defaults

     將欄位名稱對映至預設值的字典。

          >>> Account = namedtuple('Account', ['type', 'balance'], defaults=[0])
          >>> Account._field_defaults
          {'balance': 0}
          >>> Account('premium')
          Account(type='premium', balance=0)

要取得這個名稱存於字串的欄位，要使用 *note getattr(): b78. 函式：

     >>> getattr(p, 'x')
     11

（如*note 拆解引數列表（Unpacking Argument Lists）: 1b33.所述）將一個字
典轉換成 named tuple，要使用 ** 雙星號運算子：

     >>> d = {'x': 11, 'y': 22}
     >>> Point(**d)
     Point(x=11, y=22)

因為一個 named tuple 是一個常規的 Python 類別，我們可以很容易的透過子類
別來新增或更改功能，以下是如何新增一個計算得到的欄位和固定寬度的輸出列印
格式：

     >>> class Point(namedtuple('Point', ['x', 'y'])):
     ...     __slots__ = ()
     ...     @property
     ...     def hypot(self):
     ...         return (self.x ** 2 + self.y ** 2) ** 0.5
     ...     def __str__(self):
     ...         return 'Point: x=%6.3f  y=%6.3f  hypot=%6.3f' % (self.x, self.y, self.hypot)

     >>> for p in Point(3, 4), Point(14, 5/7):
     ...     print(p)
     Point: x= 3.000  y= 4.000  hypot= 5.000
     Point: x=14.000  y= 0.714  hypot=14.018

上面的子類別將 ‘__slots__’ 設定為空 tuple，這樣一來就防止了字典實例被建
立，因而保持了較低的記憶體用量。

子類別化無法用於增加新的、已被儲存的欄位，應當透過 *note _fields: 23f3.
屬性以建立一個新的 named tuple 來實現：

     >>> Point3D = namedtuple('Point3D', Point._fields + ('z',))

透過直接賦值給 ‘__doc__’，可以自訂說明文件字串：

     >>> Book = namedtuple('Book', ['id', 'title', 'authors'])
     >>> Book.__doc__ += ': Hardcover book in active collection'
     >>> Book.id.__doc__ = '13-digit ISBN'
     >>> Book.title.__doc__ = 'Title of first printing'
     >>> Book.authors.__doc__ = 'List of authors sorted by last name'

在 3.5 版的變更: 文件字串屬性變成可寫入。

也參考
......

   * 關於為 named tuple 新增型別提示的方法，請參閱 *note
     typing.NamedTuple: 291.，它運用 *note class: 126a. 關鍵字以提供了一
     個簡潔的表示法：

          class Component(NamedTuple):
              part_number: int
              weight: float
              description: Optional[str] = None

   * 關於以 dict 而非 tuple 為底層的可變命名空間，請參考 *note
     types.SimpleNamespace(): 1b5.。

   * *note dataclasses: 27. 模組提供了一個裝飾器和一些函式，用於自動將被
     生成的特殊方法新增到使用者定義的類別中。


File: python.info,  Node: OrderedDict 物件,  Next: UserDict 物件,  Prev: namedtuple 擁有具名欄位之 tuple 的工廠函式,  Up: collections --- 容器資料型態

5.8.4.9 ‘OrderedDict’ 物件
..........................

Ordered dictionary（有序字典）就像常規字典一樣，但有一些與排序操作相關的
額外功能，但由於內建的 *note dict: 23b. 類別現在已經有記憶插入順序的能力
（Python 3.7 中確保了這種新行為），它們變得不那麼重要了。

仍存在一些與 *note dict: 23b. 的不同之處：

   * 常規的 *note dict: 23b. 被設計成非常擅長於對映相關操作，追蹤插入的
     順序為次要目標。

   * *note OrderedDict: 57f. 則被設計成擅長於重新排序相關的操作，空間效
     率、疊代速度和更新操作的效能則為次要設計目標。

   * *note OrderedDict: 57f. 比起 *note dict: 23b. 更適合處理頻繁的重新
     排序操作，如在下方用法中所示，這讓它適合用於多種 LRU cache 的實作中
     。

   * *note OrderedDict: 57f. 之相等性運算會檢查順序是否相同。

     一個一般的 *note dict: 23b. 可以用 ‘p == q and all(k1 == k2 for k1,
     k2 in zip(p, q))’ 來效仿有檢查順序的相等性運算。

   * *note OrderedDict: 57f. 類別的 ‘popitem()’ 方法有不同的函式簽名
     (signature)，它接受傳入一個選擇性引數來指定要移除哪個元素。

     一個一般的 *note dict: 23b. 可以用 ‘d.popitem()’ 來效仿 OrderedDict
     的 ‘od.popitem(last=True)’，這保證會移除最右邊（最後一個）的元素。

     一個一般的 *note dict: 23b. 可以用 ‘(k := next(iter(d)), d.pop(k))’
     來效仿 OrderedDict 的 ‘od.popitem(last=False)’，若最左邊（第一個）
     的元素存在，則將其回傳並移除。

   * *note OrderedDict: 57f. 有個 ‘move_to_end()’ 方法可有效率地將一個元
     素重新排列到任一端。

     一個一般的 *note dict: 23b. 可以用 ‘d[k] = d.pop(k)’ 來效仿
     OrderedDict 的 ‘od.move_to_end(k, last=True)’，這會將該鍵與其對應到
     的值移動至最右（最後面）的位置。

     一個一般的 *note dict: 23b. 沒有和 OrderedDict 的
     ‘od.move_to_end(k, last=False)’ 等價的有效方式，這是將鍵與其對應到
     的值移動至最左（最前面）位置的方法。

   * 在 Python 3.8 之前，*note dict: 23b. 並沒有 ‘__reversed__()’ 方法。

 -- 類別: collections.OrderedDict ([items])

     回傳一個 *note dict: 23b. 子類別的實例，它具有專門用於重新排列字典
     順序的方法。

     在 3.1 版被加入.

      -- 方法: popitem (last=True)

          Ordered dictionary 的 *note popitem(): 1280. 方法移除並回傳一
          個鍵值 (key, value) 對。如果 'last' 為真值，則按 LIFO 後進先出
          的順序回傳鍵值對，否則就按 FIFO (first-in, first-out) 先進先出
          的順序回傳鍵值對。

      -- 方法: move_to_end (key, last=True)

          將現有的 'key' 移動到 ordered dictionary 的任一端。如果 'last'
          為真值（此為預設值）則將元素移至右端；如果 'last' 為假值則將元
          素移至左端。如果 'key' 不存在則會引發 *note KeyError: 2fb.：

               >>> d = OrderedDict.fromkeys('abcde')
               >>> d.move_to_end('b')
               >>> ''.join(d)
               'acdeb'
               >>> d.move_to_end('b', last=False)
               >>> ''.join(d)
               'bacde'

          在 3.2 版被加入.

除了普通的對映方法，ordered dictionary 還支援了透過 *note reversed():
80a. 來做倒序疊代。

*note OrderedDict: 57f. 物件之間的相等性運算是會檢查順序是否相同的，是透
過 ‘list(od1.items())==list(od2.items())’ 來實現。*note OrderedDict:
57f. 物件和其他 *note Mapping: 86f. 物件間的相等性運算則像普通字典一樣不
考慮順序性，這使得 *note OrderedDict: 57f. 可於任何字典可使用的時機中被
替換掉。

在 3.5 版的變更: *note OrderedDict: 57f. 的項 (item)、鍵與值之*note
視圖: 23f6.現在可透過 *note reversed(): 80a. 來倒序疊代。

在 3.6 版的變更: 隨著 PEP 468(1) 被核可，被傳入給 *note OrderedDict:
57f. 建構函式與其 ‘update()’ 方法的關鍵字引數之順序被保留了下來。

在 3.9 版的變更: 新增合併 (‘|’) 和更新 (‘|=’) 運算子，請見 PEP 584(2)。

* Menu:

* OrderedDict 範例與用法::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0468/

   (2) https://peps.python.org/pep-0584/


File: python.info,  Node: OrderedDict 範例與用法,  Up: OrderedDict 物件

5.8.4.10 ‘OrderedDict’ 範例與用法
.................................

建立一個能夠記住鍵'最後'插入順序的 ordered dictionary 變體很簡單。如果新
條目覆蓋了現有條目，則原本插入位置會被更改並移動至末端：

     class LastUpdatedOrderedDict(OrderedDict):
         'Store items in the order the keys were last added'

         def __setitem__(self, key, value):
             super().__setitem__(key, value)
             self.move_to_end(key)

*note OrderedDict: 57f. 在實現一個 *note functools.lru_cache(): 993. 的
變形版本時也非常有用：

     from collections import OrderedDict
     from time import time

     class TimeBoundedLRU:
         "LRU Cache that invalidates and refreshes old entries."

         def __init__(self, func, maxsize=128, maxage=30):
             self.cache = OrderedDict()      # { args : (timestamp, result)}
             self.func = func
             self.maxsize = maxsize
             self.maxage = maxage

         def __call__(self, *args):
             if args in self.cache:
                 self.cache.move_to_end(args)
                 timestamp, result = self.cache[args]
                 if time() - timestamp <= self.maxage:
                     return result
             result = self.func(*args)
             self.cache[args] = time(), result
             if len(self.cache) > self.maxsize:
                 self.cache.popitem(last=False)
             return result

     class MultiHitLRUCache:
         """ LRU cache that defers caching a result until
             it has been requested multiple times.

             To avoid flushing the LRU cache with one-time requests,
             we don't cache until a request has been made more than once.

         """

         def __init__(self, func, maxsize=128, maxrequests=4096, cache_after=1):
             self.requests = OrderedDict()   # { uncached_key : request_count }
             self.cache = OrderedDict()      # { cached_key : function_result }
             self.func = func
             self.maxrequests = maxrequests  # max number of uncached requests
             self.maxsize = maxsize          # max number of stored return values
             self.cache_after = cache_after

         def __call__(self, *args):
             if args in self.cache:
                 self.cache.move_to_end(args)
                 return self.cache[args]
             result = self.func(*args)
             self.requests[args] = self.requests.get(args, 0) + 1
             if self.requests[args] <= self.cache_after:
                 self.requests.move_to_end(args)
                 if len(self.requests) > self.maxrequests:
                     self.requests.popitem(last=False)
             else:
                 self.requests.pop(args, None)
                 self.cache[args] = result
                 if len(self.cache) > self.maxsize:
                     self.cache.popitem(last=False)
             return result


File: python.info,  Node: UserDict 物件,  Next: UserList 物件,  Prev: OrderedDict 物件,  Up: collections --- 容器資料型態

5.8.4.11 ‘UserDict’ 物件
........................

*note UserDict: 1898. 類別是作為 dict 物件的包裝器。因為已經可以直接自
*note dict: 23b. 建立子類別，這個類別的需求已部分被滿足，不過這個類別使
用起來更方便，因為被包裝的字典可以作為其屬性來存取。

 -- 類別: collections.UserDict ([initialdata])

     模擬字典的類別。實例的內容被存於一個字典，可透過 *note UserDict:
     1898. 的 *note data: 23f9. 屬性來做存取。如果有提供 'initialdata'，
     *note data: 23f9. 屬性會被初始化為其值；要注意指到 'initialdata' 的
     參照不會被保留，使其可被用於其他目的。

     除了支援作為對映所需的方法與操作，*note UserDict: 1898. 實例提供了
     以下屬性：

      -- 屬性: data

          一個真實的字典，用於儲存 *note UserDict: 1898. 類別的資料內容
          。


File: python.info,  Node: UserList 物件,  Next: UserString 物件,  Prev: UserDict 物件,  Up: collections --- 容器資料型態

5.8.4.12 ‘UserList’ 物件
........................

此類別是 list 物件的包裝器。它是個方便的基礎類別，可繼承它並覆寫現有方法
或加入新方法來定義你所需的一個類似於 list 的類別。如此一來，我們可以為
list 加入新的特性。

因為已經可以直接自 *note list: 5b6. 建立子類別，這個類別的需求已部分被滿
足，不過這個類別使用起來更方便，因為被包裝的 list 可以作為其屬性來存取。

 -- 類別: collections.UserList ([list])

     模擬 list 的類別。實例的內容被存於一個 list，可透過 *note UserList:
     1452. 的 *note data: 23fb. 屬性來做存取。實例內容被初始化為 'list'
     的複製，預設為一個空的 list ‘[]’。'list' 可以是任何 iterable，例如
     一個真實的 Python list 或是一個 *note UserList: 1452. 物件。

     除了支援可變序列的方法與操作，*note UserList: 1452. 實例提供了以下
     屬性：

      -- 屬性: data

          一個真實的 *note list: 5b6. 物件，用於儲存 *note UserList:
          1452. 類別的資料內容。

'子類別化的條件：'*note UserList: 1452. 的子類別應該要提供一個不需要引數
或一個引數的建構函式。回傳一個新序列的 list 操作會從那些實作出來的類別建
立一個實例，為了達成上述目的，它假設建構函式可傳入單一參數來呼叫，該參數
即是做為數據來源的一個序列物件。

如果希望一個自此獲得的子類別不遵從上述要求，那所有該類別支援的特殊方法則
必須被覆寫；請參考原始碼來理解在這情況下哪些方法是必須提供的。


File: python.info,  Node: UserString 物件,  Prev: UserList 物件,  Up: collections --- 容器資料型態

5.8.4.13 ‘UserString’ 物件
..........................

*note UserString: d7b. 類別是字串物件的包裝器，因為已經可以從 *note str:
3f2. 直接建立子類別，這個類別的需求已經部分被滿足，不過這個類別使用起來
更方便，因為被包裝的字串可以作為其屬性來存取。

 -- 類別: collections.UserString (seq)

     模擬字串物件的類別。實例的內容被存於一個字串物件，可透過 *note
     UserString: d7b. 的 *note data: 23fd. 屬性來做存取。實例內容被初始
     化為 'seq' 的複製，'seq' 引數可以是任何可被內建函式 *note str():
     3f2. 轉換成字串的物件。

     除了支援字串的方法和操作以外，*note UserString: d7b. 實例也提供了以
     下屬性：

      -- 屬性: data

          一個真實的 *note str: 3f2. 物件，用來儲存 *note UserString:
          d7b. 類別的資料內容。

     在 3.5 版的變更: 新增方法 ‘__getnewargs__’、‘__rmod__’、
     ‘casefold’、‘format_map’、‘isprintable’ 以及 ‘maketrans’。


File: python.info,  Node: collections abc --- 容器的抽象基底類別,  Next: heapq --- 堆積佇列 heap queue 演算法,  Prev: collections --- 容器資料型態,  Up: 資料型別

5.8.5 ‘collections.abc’ -- 容器的抽象基底類別
---------------------------------------------

在 3.3 版被加入: Formerly, this module was part of the *note
collections: 16. module.

'原始碼：'Lib/_collections_abc.py(1)

__________________________________________________________________

This module provides *note abstract base classes: 114e. that can be used
to test whether a class provides a particular interface; for example,
whether it is *note hashable: 5b5. or whether it is a *note mapping:
1154.

An *note issubclass(): 765. or *note isinstance(): 3e8. test for an
interface works in one of three ways.

1) A newly written class can inherit directly from one of the abstract
base classes.  The class must supply the required abstract methods.  The
remaining mixin methods come from inheritance and can be overridden if
desired.  Other methods may be added as needed:

     class C(Sequence):                      # Direct inheritance
         def __init__(self): ...             # Extra method not required by the ABC
         def __getitem__(self, index):  ...  # Required abstract method
         def __len__(self):  ...             # Required abstract method
         def count(self, value): ...         # Optionally override a mixin method

     >>> issubclass(C, Sequence)
     True
     >>> isinstance(C(), Sequence)
     True

2) Existing classes and built-in classes can be registered as "virtual
subclasses" of the ABCs.  Those classes should define the full API
including all of the abstract methods and all of the mixin methods.
This lets users rely on *note issubclass(): 765. or *note isinstance():
3e8. tests to determine whether the full interface is supported.  The
exception to this rule is for methods that are automatically inferred
from the rest of the API:

     class D:                                 # No inheritance
         def __init__(self): ...              # Extra method not required by the ABC
         def __getitem__(self, index):  ...   # Abstract method
         def __len__(self):  ...              # Abstract method
         def count(self, value): ...          # Mixin method
         def index(self, value): ...          # Mixin method

     Sequence.register(D)                     # Register instead of inherit

     >>> issubclass(D, Sequence)
     True
     >>> isinstance(D(), Sequence)
     True

In this example, class ‘D’ does not need to define ‘__contains__’,
‘__iter__’, and ‘__reversed__’ because the *note in-operator: 1f4c, the
*note iteration: 11bf. logic, and the *note reversed(): 80a. function
automatically fall back to using ‘__getitem__’ and ‘__len__’.

3) Some simple interfaces are directly recognizable by the presence of
the required methods (unless those methods have been set to *note None:
61b.):

     class E:
         def __iter__(self): ...
         def __next__(self): ...

     >>> issubclass(E, Iterable)
     True
     >>> isinstance(E(), Iterable)
     True

Complex interfaces do not support this last technique because an
interface is more than just the presence of method names.  Interfaces
specify semantics and relationships between methods that cannot be
inferred solely from the presence of specific method names.  For
example, knowing that a class supplies ‘__getitem__’, ‘__len__’, and
‘__iter__’ is insufficient for distinguishing a *note Sequence: 115c.
from a *note Mapping: 86f.

在 3.9 版被加入: These abstract classes now support ‘[]’.  See *note
泛型別名型別: 656. and PEP 585(2).

* Menu:

* Collections Abstract Base Classes::
* Collections Abstract Base Classes: Collections Abstract Base Classes -- Detailed Descriptions. Detailed Descriptions
* Examples and Recipes::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/_collections_abc.py

   (2) https://peps.python.org/pep-0585/


File: python.info,  Node: Collections Abstract Base Classes,  Next: Collections Abstract Base Classes -- Detailed Descriptions,  Up: collections abc --- 容器的抽象基底類別

5.8.5.1 Collections Abstract Base Classes
.........................................

The collections module offers the following *note ABCs: 114e.:

ABC                                Inherits from              Abstract Methods            Mixin Methods
                                                                                          
---------------------------------------------------------------------------------------------------------------------------------------------------
                                                                                          
*note Container: 212c. (1)                                    ‘__contains__’
                                                              
                                                                                          
*note Hashable: 49d. (2)                                      ‘__hash__’
                                                              
                                                                                          
*note Iterable: 212a. (3) (4)                                 ‘__iter__’
                                                              
                                                                                          
*note Iterator: 212b. (5)          *note Iterable: 212a.      ‘__next__’                  ‘__iter__’
                                                                                          
                                                                                          
*note Reversible: c30. (6)         *note Iterable: 212a.      ‘__reversed__’
                                                              
                                                                                          
*note Generator: d81. (7)          *note Iterator: 212b.      ‘send’、‘throw’             ‘close’、‘__iter__’、‘__next__’
                                                                                          
                                                                                          
*note Sized: 49e. (8)                                         ‘__len__’
                                                              
                                                                                          
*note Callable: 78e. (9)                                      ‘__call__’
                                                              
                                                                                          
*note Collection: c2f. (10)        *note Sized: 49e.、        ‘__contains__’、
                                   *note Iterable: 212a.、    ‘__iter__’、‘__len__’
                                   *note Container: 212c.     
                                   
                                                                                          
*note Sequence: 115c.              *note Reversible: c30,     ‘__getitem__’、‘__len__’    ‘__contains__’、‘__iter__’、‘__reversed__’、‘index’ 和
                                   *note Collection: c2f.                                 ‘count’
                                                                                          
                                                                                          
*note MutableSequence: 187.        *note Sequence: 115c.      ‘__getitem__’、             Inherited *note Sequence: 115c. methods and ‘append’,
                                                              ‘__setitem__’、             ‘clear’, ‘reverse’, ‘extend’, ‘pop’, ‘remove’, and
                                                              ‘__delitem__’、             ‘__iadd__’
                                                              ‘__len__’、‘insert’         
                                                              
                                                                                          
*note ByteString: 2a4.             *note Sequence: 115c.      ‘__getitem__’、‘__len__’    Inherited *note Sequence: 115c. methods
                                                                                          
                                                                                          
*note Set: 2122.                   *note Collection: c2f.     ‘__contains__’、            ‘__le__’、‘__lt__’、‘__eq__’、‘__ne__’、‘__gt__’、
                                                              ‘__iter__’、‘__len__’       ‘__ge__’、‘__and__’、‘__or__’、‘__sub__’、‘__xor__’ 與
                                                                                          ‘isdisjoint’
                                                                                          
                                                                                          
*note MutableSet: 212d.            *note Set: 2122.           ‘__contains__’、            Inherited *note Set: 2122. methods and ‘clear’, ‘pop’,
                                                              ‘__iter__’、‘__len__’、     ‘remove’, ‘__ior__’, ‘__iand__’, ‘__ixor__’, and
                                                              ‘add’、‘discard’            ‘__isub__’
                                                                                          
                                                                                          
*note Mapping: 86f.                *note Collection: c2f.     ‘__getitem__’、             ‘__contains__’、‘keys’、‘items’、‘values’、‘get’、
                                                              ‘__iter__’、‘__len__’       ‘__eq__’ 和 ‘__ne__’
                                                                                          
                                                                                          
*note MutableMapping: 1048.        *note Mapping: 86f.        ‘__getitem__’、             Inherited *note Mapping: 86f. methods and ‘pop’,
                                                              ‘__setitem__’、             ‘popitem’, ‘clear’, ‘update’, and ‘setdefault’
                                                              ‘__delitem__’、             
                                                              ‘__iter__’、‘__len__’
                                                              
                                                                                          
*note MappingView: 212e.           *note Sized: 49e.                                      ‘__len__’
                                                                                          
                                                                                          
*note ItemsView: 2130.             *note MappingView: 212e.、                             ‘__contains__’、‘__iter__’
                                   *note Set: 2122.                                       
                                   
                                                                                          
*note KeysView: 212f.              *note MappingView: 212e.、                             ‘__contains__’、‘__iter__’
                                   *note Set: 2122.                                       
                                   
                                                                                          
*note ValuesView: 2131.            *note MappingView: 212e.、                             ‘__contains__’、‘__iter__’
                                   *note Collection: c2f.                                 
                                   
                                                                                          
*note Awaitable: d82. (11)                                    ‘__await__’
                                                              
                                                                                          
*note Coroutine: d83. (12)         *note Awaitable: d82.      ‘send’、‘throw’             ‘close’
                                                                                          
                                                                                          
*note AsyncIterable: d85. (13)                                ‘__aiter__’
                                                              
                                                                                          
*note AsyncIterator: d84. (14)     *note AsyncIterable: d85.  ‘__anext__’                 ‘__aiter__’
                                                                                          
                                                                                          
*note AsyncGenerator: c31. (15)    *note AsyncIterator: d84.  ‘asend’、‘athrow’           ‘aclose’、‘__aiter__’、‘__anext__’
                                                                                          
                                                                                          
*note Buffer: 2a5. (16)                                       ‘__buffer__’
                                                              

註解
....

   ---------- Footnotes ----------

   (1) These ABCs override *note __subclasshook__(): 2401. to support
testing an interface by verifying the required methods are present and
have not been set to *note None: 61b.  This only works for simple
interfaces.  More complex interfaces require registration or direct
subclassing.

   (2) These ABCs override *note __subclasshook__(): 2401. to support
testing an interface by verifying the required methods are present and
have not been set to *note None: 61b.  This only works for simple
interfaces.  More complex interfaces require registration or direct
subclassing.

   (3) These ABCs override *note __subclasshook__(): 2401. to support
testing an interface by verifying the required methods are present and
have not been set to *note None: 61b.  This only works for simple
interfaces.  More complex interfaces require registration or direct
subclassing.

   (4) Checking ‘isinstance(obj, Iterable)’ detects classes that are
registered as *note Iterable: 212a. or that have an *note __iter__():
1bc4. method, but it does not detect classes that iterate with the *note
__getitem__(): 266. method.  The only reliable way to determine whether
an object is *note iterable: 11bf. is to call ‘iter(obj)’.

   (5) These ABCs override *note __subclasshook__(): 2401. to support
testing an interface by verifying the required methods are present and
have not been set to *note None: 61b.  This only works for simple
interfaces.  More complex interfaces require registration or direct
subclassing.

   (6) These ABCs override *note __subclasshook__(): 2401. to support
testing an interface by verifying the required methods are present and
have not been set to *note None: 61b.  This only works for simple
interfaces.  More complex interfaces require registration or direct
subclassing.

   (7) These ABCs override *note __subclasshook__(): 2401. to support
testing an interface by verifying the required methods are present and
have not been set to *note None: 61b.  This only works for simple
interfaces.  More complex interfaces require registration or direct
subclassing.

   (8) These ABCs override *note __subclasshook__(): 2401. to support
testing an interface by verifying the required methods are present and
have not been set to *note None: 61b.  This only works for simple
interfaces.  More complex interfaces require registration or direct
subclassing.

   (9) These ABCs override *note __subclasshook__(): 2401. to support
testing an interface by verifying the required methods are present and
have not been set to *note None: 61b.  This only works for simple
interfaces.  More complex interfaces require registration or direct
subclassing.

   (10) These ABCs override *note __subclasshook__(): 2401. to support
testing an interface by verifying the required methods are present and
have not been set to *note None: 61b.  This only works for simple
interfaces.  More complex interfaces require registration or direct
subclassing.

   (11) These ABCs override *note __subclasshook__(): 2401. to support
testing an interface by verifying the required methods are present and
have not been set to *note None: 61b.  This only works for simple
interfaces.  More complex interfaces require registration or direct
subclassing.

   (12) These ABCs override *note __subclasshook__(): 2401. to support
testing an interface by verifying the required methods are present and
have not been set to *note None: 61b.  This only works for simple
interfaces.  More complex interfaces require registration or direct
subclassing.

   (13) These ABCs override *note __subclasshook__(): 2401. to support
testing an interface by verifying the required methods are present and
have not been set to *note None: 61b.  This only works for simple
interfaces.  More complex interfaces require registration or direct
subclassing.

   (14) These ABCs override *note __subclasshook__(): 2401. to support
testing an interface by verifying the required methods are present and
have not been set to *note None: 61b.  This only works for simple
interfaces.  More complex interfaces require registration or direct
subclassing.

   (15) These ABCs override *note __subclasshook__(): 2401. to support
testing an interface by verifying the required methods are present and
have not been set to *note None: 61b.  This only works for simple
interfaces.  More complex interfaces require registration or direct
subclassing.

   (16) These ABCs override *note __subclasshook__(): 2401. to support
testing an interface by verifying the required methods are present and
have not been set to *note None: 61b.  This only works for simple
interfaces.  More complex interfaces require registration or direct
subclassing.


File: python.info,  Node: Collections Abstract Base Classes -- Detailed Descriptions,  Next: Examples and Recipes,  Prev: Collections Abstract Base Classes,  Up: collections abc --- 容器的抽象基底類別

5.8.5.2 Collections Abstract Base Classes - Detailed Descriptions
.................................................................

 -- 類別: collections.abc.Container

     ABC for classes that provide the *note __contains__(): 1e33.
     method.

 -- 類別: collections.abc.Hashable

     ABC for classes that provide the *note __hash__(): a9e. method.

 -- 類別: collections.abc.Sized

     ABC for classes that provide the *note __len__(): 1e38. method.

 -- 類別: collections.abc.Callable

     ABC for classes that provide the *note __call__(): 4fe. method.

     See *note 註釋 callable 物件: 2403. for details on how to use
     ‘Callable’ in type annotations.

 -- 類別: collections.abc.Iterable

     ABC for classes that provide the *note __iter__(): 1bc4. method.

     Checking ‘isinstance(obj, Iterable)’ detects classes that are
     registered as *note Iterable: 212a. or that have an *note
     __iter__(): 1bc4. method, but it does not detect classes that
     iterate with the *note __getitem__(): 266. method.  The only
     reliable way to determine whether an object is *note iterable:
     11bf. is to call ‘iter(obj)’.

 -- 類別: collections.abc.Collection

     ABC for sized iterable container classes.

     在 3.6 版被加入.

 -- 類別: collections.abc.Iterator

     ABC for classes that provide the *note __iter__(): 1bc7. and *note
     __next__(): 1260. methods.  See also the definition of *note
     iterator: 192.

 -- 類別: collections.abc.Reversible

     ABC for iterable classes that also provide the *note
     __reversed__(): 1e32. method.

     在 3.6 版被加入.

 -- 類別: collections.abc.Generator

     ABC for *note generator: 1004. classes that implement the protocol
     defined in PEP 342(1) that extends *note iterators: 192. with the
     *note send(): 1ea2, *note throw(): 4a0. and *note close(): 15ee.
     methods.

     See *note Annotating generators and coroutines: 2404. for details
     on using ‘Generator’ in type annotations.

     在 3.5 版被加入.

 -- 類別: collections.abc.Sequence
 -- 類別: collections.abc.MutableSequence
 -- 類別: collections.abc.ByteString

     ABCs for read-only and mutable *note sequences: 499.

     Implementation note: Some of the mixin methods, such as *note
     __iter__(): 1bc4, *note __reversed__(): 1e32. and ‘index()’, make
     repeated calls to the underlying *note __getitem__(): 266. method.
     Consequently, if *note __getitem__(): 266. is implemented with
     constant access speed, the mixin methods will have linear
     performance; however, if the underlying method is linear (as it
     would be with a linked list), the mixins will have quadratic
     performance and will likely need to be overridden.

     在 3.5 版的變更: The index() method added support for 'stop' and
     'start' arguments.

     Deprecated since version 3.12, will be removed in version 3.14: The
     *note ByteString: 2a4. ABC has been deprecated.  For use in typing,
     prefer a union, like ‘bytes | bytearray’, or *note
     collections.abc.Buffer: 2a5.  For use as an ABC, prefer *note
     Sequence: 115c. or *note collections.abc.Buffer: 2a5.

 -- 類別: collections.abc.Set
 -- 類別: collections.abc.MutableSet

     ABCs for read-only and mutable *note sets: 204d.

 -- 類別: collections.abc.Mapping
 -- 類別: collections.abc.MutableMapping

     ABCs for read-only and mutable *note mappings: 1154.

 -- 類別: collections.abc.MappingView
 -- 類別: collections.abc.ItemsView
 -- 類別: collections.abc.KeysView
 -- 類別: collections.abc.ValuesView

     ABCs for mapping, items, keys, and values *note views: 23f6.

 -- 類別: collections.abc.Awaitable

     ABC for *note awaitable: 193. objects, which can be used in *note
     await: 19f. expressions.  Custom implementations must provide the
     *note __await__(): 1e9d. method.

     *note Coroutine: 438. objects and instances of the *note Coroutine:
     d83. ABC are all instances of this ABC.

          備註: In CPython, generator-based coroutines (*note
          generators: 1004. decorated with *note @types.coroutine: e2c.)
          are 'awaitables', even though they do not have an *note
          __await__(): 1e9d. method.  Using ‘isinstance(gencoro,
          Awaitable)’ for them will return ‘False’.  Use *note
          inspect.isawaitable(): dbd. to detect them.

     在 3.5 版被加入.

 -- 類別: collections.abc.Coroutine

     ABC for *note coroutine: 438. compatible classes.  These implement
     the following methods, defined in *note Coroutine Objects: 1df8.:
     *note send(): 1ea1, *note throw(): 49f, and *note close(): 1ea3.
     Custom implementations must also implement *note __await__(): 1e9d.
     All *note Coroutine: d83. instances are also instances of *note
     Awaitable: d82.

          備註: In CPython, generator-based coroutines (*note
          generators: 1004. decorated with *note @types.coroutine: e2c.)
          are 'awaitables', even though they do not have an *note
          __await__(): 1e9d. method.  Using ‘isinstance(gencoro,
          Coroutine)’ for them will return ‘False’.  Use *note
          inspect.isawaitable(): dbd. to detect them.

     See *note Annotating generators and coroutines: 2404. for details
     on using ‘Coroutine’ in type annotations.  The variance and order
     of type parameters correspond to those of *note Generator: d81.

     在 3.5 版被加入.

 -- 類別: collections.abc.AsyncIterable

     ABC for classes that provide an ‘__aiter__’ method.  See also the
     definition of *note asynchronous iterable: d1e.

     在 3.5 版被加入.

 -- 類別: collections.abc.AsyncIterator

     ABC for classes that provide ‘__aiter__’ and ‘__anext__’ methods.
     See also the definition of *note asynchronous iterator: 191.

     在 3.5 版被加入.

 -- 類別: collections.abc.AsyncGenerator

     ABC for *note asynchronous generator: 1f14. classes that implement
     the protocol defined in PEP 525(2) and PEP 492(3).

     See *note Annotating generators and coroutines: 2404. for details
     on using ‘AsyncGenerator’ in type annotations.

     在 3.6 版被加入.

 -- 類別: collections.abc.Buffer

     ABC for classes that provide the *note __buffer__(): 405. method,
     implementing the *note buffer protocol: 367.  See PEP 688(4).

     在 3.12 版被加入.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0342/

   (2) https://peps.python.org/pep-0525/

   (3) https://peps.python.org/pep-0492/

   (4) https://peps.python.org/pep-0688/


File: python.info,  Node: Examples and Recipes,  Prev: Collections Abstract Base Classes -- Detailed Descriptions,  Up: collections abc --- 容器的抽象基底類別

5.8.5.3 Examples and Recipes
............................

ABCs allow us to ask classes or instances if they provide particular
functionality, for example:

     size = None
     if isinstance(myvar, collections.abc.Sized):
         size = len(myvar)

Several of the ABCs are also useful as mixins that make it easier to
develop classes supporting container APIs.  For example, to write a
class supporting the full *note Set: 2122. API, it is only necessary to
supply the three underlying abstract methods: *note __contains__():
1e33, *note __iter__(): 1bc4, and *note __len__(): 1e38.  The ABC
supplies the remaining methods such as ‘__and__()’ and *note
isdisjoint(): 210f.:

     class ListBasedSet(collections.abc.Set):
         ''' Alternate set implementation favoring space over speed
             and not requiring the set elements to be hashable. '''
         def __init__(self, iterable):
             self.elements = lst = []
             for value in iterable:
                 if value not in lst:
                     lst.append(value)

         def __iter__(self):
             return iter(self.elements)

         def __contains__(self, value):
             return value in self.elements

         def __len__(self):
             return len(self.elements)

     s1 = ListBasedSet('abcdef')
     s2 = ListBasedSet('defghi')
     overlap = s1 & s2            # The __and__() method is supported automatically

Notes on using *note Set: 2122. and *note MutableSet: 212d. as a mixin:

  1. Since some set operations create new sets, the default mixin
     methods need a way to create new instances from an *note iterable:
     11bf.  The class constructor is assumed to have a signature in the
     form ‘ClassName(iterable)’.  That assumption is factored-out to an
     internal *note classmethod: 14a. called ‘_from_iterable()’ which
     calls ‘cls(iterable)’ to produce a new set.  If the *note Set:
     2122. mixin is being used in a class with a different constructor
     signature, you will need to override ‘_from_iterable()’ with a
     classmethod or regular method that can construct new instances from
     an iterable argument.

  2. To override the comparisons (presumably for speed, as the semantics
     are fixed), redefine *note __le__(): 129f. and *note __ge__():
     12a1, then the other operations will automatically follow suit.

  3. The *note Set: 2122. mixin provides a ‘_hash()’ method to compute a
     hash value for the set; however, *note __hash__(): a9e. is not
     defined because not all sets are *note hashable: 5b5. or immutable.
     To add set hashability using mixins, inherit from both *note Set():
     2122. and *note Hashable(): 49d, then define ‘__hash__ =
     Set._hash’.

也參考
......

   * OrderedSet recipe(1) for an example built on *note MutableSet:
     212d.

   * 關於 ABC 的更多資訊請見 *note abc: 4. module 和 PEP 3119(2)。

   ---------- Footnotes ----------

   (1) https://code.activestate.com/recipes/576694/

   (2) https://peps.python.org/pep-3119/


File: python.info,  Node: heapq --- 堆積佇列 heap queue 演算法,  Next: bisect --- 陣列二分演算法 Array bisection algorithm,  Prev: collections abc --- 容器的抽象基底類別,  Up: 資料型別

5.8.6 ‘heapq’ -- 堆積佇列 (heap queue) 演算法
---------------------------------------------

'原始碼：'Lib/heapq.py(1)

__________________________________________________________________

這個模組實作了堆積佇列 (heap queue) 演算法，亦被稱為優先佇列 (priority
queue) 演算法。

Heap（堆積）是一顆二元樹，樹上所有父節點的值都小於等於他的子節點的值，我
們將這種情況稱為堆積的性質不變。

使用陣列實作，對於所有從0開始的 'k' 都滿足 ‘heap[k] <= heap[2*k+1]’ 和
‘heap[k] <= heap[2*k+2]’ 。為了比較節點的值，不存在的元素被視為無限大。
heap 存在一個有趣的性質：樹上最小的元素永遠會在根節點 ‘heap[0]’ 上。

下方的 API 跟一般教科書的 heap queue 演算法有兩個方面不同：第一，我們的
索引從 0 開始計算，這會父節點與子節點之間的關係產生很微小的差異，但更符
合 Python 從 0 開始索引的設計。第二，我們的 pop 方法會回傳最小的元素而不
是最大的元素 （ 在教科書中被稱作 "min heap"，而 "max heap" 因為他很適合
做原地排序，所以更常出現在教科書中 ）。

這兩個特性使得把 heap 當作一個標準的 Python list 檢視時不會出現意外：
‘heap[0]’ 是最小的物件，‘heap.sort()’ 能保持 heap 的性質不變！

建立一個 heap 可以使用 list 初始化為 ‘[]’，或者使用函式 *note heapify():
2408. 將一個已經有元素的 list轉成一個 heap。

此模組提供下面的函式

 -- 函式: heapq.heappush (heap, item)

     把 'item' 放進 'heap'，並保持 heap 性質不變。

 -- 函式: heapq.heappop (heap)

     從 'heap' 取出並回傳最小的元素，同時保持 heap 性質不變。如果 heap 是
     空的會產生 *note IndexError: 14a3. 錯誤。只存取最小元素但不取出可以
     使用 ‘heap[0]’ 。

 -- 函式: heapq.heappushpop (heap, item)

     將 'item' 放入 heap ，接著從 'heap' 取出並回傳最小的元素。這個組合
     函式比呼叫 *note heappush(): 1427. 之後呼叫 *note heappop(): 1428.
     更有效率。

 -- 函式: heapq.heapify (x)

     在線性時間內將 list 'x' 轉為 heap，且過程不會申請額外記憶體。

 -- 函式: heapq.heapreplace (heap, item)

     從 'heap' 取出並回傳最小的元素，接著將新的 'item' 放進heap。heap 的
     大小不會改變。如果 heap 是空的會產生 *note IndexError: 14a3. 錯誤。

     這個一次完成的操作會比呼叫 *note heappop(): 1428. 之後呼叫 *note
     heappush(): 1427. 更有效率，並在維護 heap 的大小不變時更為適當，取
     出/放入的組合函式一定會從 heap 回傳一個元素並用 'item' 取代他。

     函式的回傳值可能會大於被加入的 'item' 。如果這不是你期望發生的，可
     以考慮使用 *note heappushpop(): 2409. 替代，他會回傳 heap 的最小值
     和 'item' 兩個當中比較小的那個，並將大的留在 heap 內。

這個模組也提供三個利用 heap 實作的一般用途函式

 -- 函式: heapq.merge (*iterables, key=None, reverse=False)

     合併多個已排序的輸入並產生單一且已排序的輸出（舉例：合併來自多個
     log 檔中有時間戳記的項目）。回傳一個 *note iterator: 192. 包含已經
     排序的值。

     和 ‘sorted(itertools.chain(*iterables))’ 類似但回傳值是一個
     iterable ，不會一次把所有資料都放進記憶體中，並且假設每一個輸入都已
     經（由小到大）排序過了。

     有兩個選用參數，指定時必須被當作關鍵字參數指定。

     'key' 參數指定了一個 *note key function: dab. 引數，用來從每一個輸
     入的元素中決定一個比較的依據。預設的值是 ‘None’ （直接比較元素）。

     'reverse' 是一個布林值，如果設定為 ‘True’ ，則輸入的元素將以相反的
     比較順序進行合併。為了達成類似 ‘sorted(itertools.chain(*iterables),
     reverse=True)’ 的行為，所有 iterables 必須由大到小排序。

     在 3.5 版的變更: 加入選用參數 'key' 和 'reverse' 。

 -- 函式: heapq.nlargest (n, iterable, key=None)

     回傳一個包含資料 'iterable' 中前 'n' 大元素的 list 。如果有指定
     'key' 引數，'key' 會是只有一個引數的函式，用來從每一個在 'iterable'
     中的元素提取一個比較的依據（例如 ‘key=str.lower’ ）。效果相當於
     ‘sorted(iterable, key=key, reverse=True)[:n]’ 。

 -- 函式: heapq.nsmallest (n, iterable, key=None)

     回傳一個包含資料 'iterable' 中前 'n' 小元素的 list 。如果有指定
     'key' 引數，'key' 會是只有一個引數的函式，用來從每一個在 'iterable'
     中的元素提取一個比較的依據（例如 ‘key=str.lower’ ）。效果相當於
     ‘sorted(iterable, key=key)[:n]’ 。

後兩個函式在 'n' 值比較小時有最好的表現。對於較大的 'n' 值，只用 *note
sorted(): b75. 函式會更有效率。同樣地，當 ‘n==1’ 時，使用內建函式 *note
min(): eac. 和 *note max(): ead. 會有更好的效率。如果需要重複使用這些函
式，可以考慮將 iterable 轉成真正的 heap 。

* Menu:

* 基礎範例::
* 優先佇列實作細節::
* 原理::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/heapq.py


File: python.info,  Node: 基礎範例,  Next: 優先佇列實作細節,  Up: heapq --- 堆積佇列 heap queue 演算法

5.8.6.1 基礎範例
................

堆積排序 (heapsort)(1) 可以透過將所有的值推入一個 heap，並且從 heap 中一
個接一個彈出最小元素來實作：

     >>> def heapsort(iterable):
     ...     h = []
     ...     for value in iterable:
     ...         heappush(h, value)
     ...     return [heappop(h) for i in range(len(h))]
     ...
     >>> heapsort([1, 3, 5, 7, 9, 2, 4, 6, 8, 0])
     [0, 1, 2, 3, 4, 5, 6, 7, 8, 9]

雖然類似 ‘sorted(iterable)’ ，但跟 *note sorted(): b75. 不同的是，這個實
作不是 stable 的排序。

Heap 中的元素可以是 tuple 。這有利於將要比較的值（例如一個 task 的優先度
）和主要資料放在一起排序：

     >>> h = []
     >>> heappush(h, (5, 'write code'))
     >>> heappush(h, (7, 'release product'))
     >>> heappush(h, (1, 'write spec'))
     >>> heappush(h, (3, 'create tests'))
     >>> heappop(h)
     (1, 'write spec')

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Heapsort


File: python.info,  Node: 優先佇列實作細節,  Next: 原理,  Prev: 基礎範例,  Up: heapq --- 堆積佇列 heap queue 演算法

5.8.6.2 優先佇列實作細節
........................

優先佇列 (priority queue)(1) 是 heap 的常見用途之一，實作優先佇列伴隨著
下列挑戰：

   * 排序的穩定性：如何將兩個擁有相同優先次序 (priority) 的 task 按照他
     們被加入的順序回傳?

   * Tuple的排序在某些情況下會壞掉，例如當 Tuple (priority, task) 的
     priorities 相等且 tasks 沒有一個預設的排序時。

   * 當一個 heap 中 task 的 priority 改變時，如何將它移到 heap 正確的位
     置上?

   * 或者一個還沒被解決的 task 需要被刪除時，要如何從佇列中找到並刪除指
     定的 task?

一個針對前兩個問題的解法是：儲存一個包含 priority 、 entry count 和 task
三個元素的 tuple 。兩個 task 有相同 priority 時， entry count 會讓兩個
task 能根據加入的順序排序。因為沒有任何兩個 task 擁有相同的 entry count
，所以永遠不會直接使用 task 做比較。

task 無法比較的另一個解決方案是建立一個包裝器類別，該類別忽略 task 項目
，只比較優先等級：

     from dataclasses import dataclass, field
     from typing import Any

     @dataclass(order=True)
     class PrioritizedItem:
         priority: int
         item: Any=field(compare=False)

剩下的問題可以藉由找到要刪除的 task 並更改它的 priority 或者直接將它移除
。尋找一個 task 可以使用一個 dictionary 指向佇列當中的 entry 。

移除 entry 或更改它的 priority 更為困難，因為這會破壞 heap 的性質。所以
一個可行的方案是將原本的 entry 做一個標記表示它已經被刪除，並新增一個擁
有新的 priority 的 entry：

     pq = []                         # list of entries arranged in a heap
     entry_finder = {}               # mapping of tasks to entries
     REMOVED = '<removed-task>'      # placeholder for a removed task
     counter = itertools.count()     # unique sequence count

     def add_task(task, priority=0):
         'Add a new task or update the priority of an existing task'
         if task in entry_finder:
             remove_task(task)
         count = next(counter)
         entry = [priority, count, task]
         entry_finder[task] = entry
         heappush(pq, entry)

     def remove_task(task):
         'Mark an existing task as REMOVED.  Raise KeyError if not found.'
         entry = entry_finder.pop(task)
         entry[-1] = REMOVED

     def pop_task():
         'Remove and return the lowest priority task. Raise KeyError if empty.'
         while pq:
             priority, count, task = heappop(pq)
             if task is not REMOVED:
                 del entry_finder[task]
                 return task
         raise KeyError('pop from an empty priority queue')

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Priority_queue


File: python.info,  Node: 原理,  Prev: 優先佇列實作細節,  Up: heapq --- 堆積佇列 heap queue 演算法

5.8.6.3 原理
............

Heap 是一個陣列對於所有從0開始的 index 'k' 都存在性質 ‘a[k] <= a[2*k+1]’
和 ‘a[k] <= a[2*k+2]’ 。為了方便比較，不存在的元素被視為無限大。Heap 的
一個有趣的性質是：‘a[0]’ 永遠是最小的元素。

上述乍看之下有些奇怪的不變式，是為了實作一個對記憶體來說有效率的方法，其
表示方式如同錦標賽一般。下列的數字為 'k'，而不是 ‘a[k]’：

                                    0

                   1                                 2

           3               4                5               6

       7       8       9       10      11      12      13      14

     15 16   17 18   19 20   21 22   23 24   25 26   27 28   29 30

在上面的樹當中，每個單元 'k' 都會位在 ‘2*k+1’ 與 ‘2*k+2’ 上方。如同體育
賽事常見的錦標賽般，每個單元可視為其下方兩個單元當中的贏家，我們可以透過
追溯整棵樹來找到該贏家曾經對戰過的所有對手。然而，在許多電腦應用中，我們
不需要追溯贏家的完整對戰歷史。為了能更有效率地使用記憶體，當一個贏家晉級
勝出時，我們用下方較低層級的另一個項目來取代它，至此規則變為一個單元以及
它下方兩個單元，包含三個不同項目，但是最上方的單元「勝過」下方兩個單元。

如果能確保滿足這個 heap 的不變式，那麼索引 0 顯然是最終的贏家。移除並找
到「下一個」贏家最簡單的演算法為：將一個輸家（例如上圖中的單元 30）移動
到位置 0，然後從新的位置 0 不斷與下方的位置交換值來向下傳遞，直到滿足不
變式為止。這個過程的複雜度顯然是樹的節點數目的對數級別。透過對所有項目疊
代，可以得到一個複雜度為 'O'('n' log 'n') 的排序。

這種排序有個好處，只要插入的項目沒有「贏過」你最後提取、索引為 0 的元素
，你就可以在排序進行的同時有效率地插入新項目。這在模擬情境當中特別有用，
其中樹能夠保存所有輸入事件，而「贏」意味著最小排程時間。當一個事件排程其
它事件的執行時，因這些事件仍在等待進行，所以很容易將它們插入 heap 當中。
因此， heap 是一個實現排程器的優秀資料結構（這就是我用以實作 MIDI 編曲器
的方法 :-）。

多種用於實作排程器的結構現今已被廣泛研究，heap 對此非常有用，因為它們速
度相當快，且速度幾乎不受其他因素影響，最壞情況與平均狀況差異無幾。也有其
它整體說來更有效率的方法，然而它們的最壞情況可能會非常糟糕。

Heap 在為儲存於硬碟上的大量資料進行排序也非常有用。你可能已經知道，大量
資料排序涉及 "runs" 的產生（也就是預先排序的序列，其大小通常與 CPU 記憶
體的大小有關），之後再對這些 run 合併，而這些合併的過程通常相當巧妙 (1)。
很重要的一點是，初始排序產生的 run 越長越好。錦標賽是達成這一點的好方法
，若你用所有可用記憶體來舉行一場錦標賽，並透過替換與向下交換來處理所有適
配當前 run 的值，那麼對於隨機產生的輸入，將可以產生長度兩倍於記憶體大小
的 run。對於已模糊排序過的輸入，效果更好。

此外，若你將索引為 0 的項目輸出至磁碟，並取得一個無法適配當前錦標賽的輸
入（因為該值「勝過」最後的輸出值），則該輸入值就無法插入至 heap 當中，因
此 heap 的大小會減小。釋放出來的記憶體可以巧妙地立即再被運用，逐步建構出
第二個 heap，其大小增加的速度會與第一個 heap 減少的速度一致。當第一個
heap 完全消失時，你可以切換至第二個 heap 開啟一個新 run 。這真是個聰明且
相當有效率的做法！

總結來說，heap 是值得了解的有用記憶體結構。我在一些應用中使用它們，我認
為能有一個 'heap' 模組是很棒的。:-)

註解
....

   ---------- Footnotes ----------

   (1) 現今的磁碟平衡演算法因為硬碟查找能力而更加複雜難解。在沒有查找功
能的裝置如大型磁帶機，狀況又不一樣了，人們必須機智地確保（遠遠提前）每次
於磁帶上移動都盡可能是最有效率的（也就是盡可能更好地「推進」合併的過程）
。有些磁帶甚至能夠向後讀取，這也被用來避免倒轉的時間。相信我，真正優秀的
磁帶排序看起來相當壯觀！排序一直以來都是一門偉大的藝術！:-)


File: python.info,  Node: bisect --- 陣列二分演算法 Array bisection algorithm,  Next: array --- 高效率的數值型陣列,  Prev: heapq --- 堆積佇列 heap queue 演算法,  Up: 資料型別

5.8.7 ‘bisect’ -- 陣列二分演算法 (Array bisection algorithm)
------------------------------------------------------------

'原始碼：'Lib/bisect.py(1)

__________________________________________________________________

這個模組維護一個已經排序過的 list ，當我們每次做完插入後不需要再次排序整
個 list 。一個很長的 list 的比較操作很花費時間，可以透過線性搜索或頻繁地
詢問來改善。

這個模組被稱為 *note bisect: d. 是因為它使用基本二分演算法來完成其工作。
不像其它搜尋特定值的二分法工具，本模組中的函式旨在定位插入點。因此，這些
函式永遠不會呼叫 *note __eq__(): a9d. 方法來確認是否找到一個值。相反地，
這些函式只呼叫 *note __lt__(): 129e. 方法，並在陣列中的值回傳一個插入點
。 此模組提供下面的函式：

 -- 函式: bisect.bisect_left (a, x, lo=0, hi=len(a), *, key=None)

     在 'a' 當中找到一個位置，讓 'x' 插入後 'a' 仍然是排序好的。參數
     'lo' 和 'hi' 用來指定 list 中應該被考慮的子區間，預設是考慮整個
     list 。如果 'a' 裡面已經有 'x' 出現，插入的位置會在所有 'x' 的前面
     （左邊）。回傳值可以被當作 ‘list.insert()’ 的第一個參數，但列表 'a'
     必須先排序過。

     回傳的插入點 'ip' 將陣列 'a' 劃分為左右兩個切片，使得對於左切片而言
     ‘all(elem < x for elem in a[lo : ip])’ 為真，對於右切片而言
     ‘all(elem >= x for elem in a[ip : hi])’ 為真。

     'key' 可指定一個單一參數的 *note key function: dab.。函式將套用此
     function 在陣列所有元素以得到比較值來計算順位。注意此 function 只會
     套用在陣列中的元素，不會套用在 'x'。

     若 'key' 為 ‘None’，元素將直接進行比較，不會呼叫任何鍵函式。

     在 3.10 版的變更: 新增 'key' 參數。

 -- 函式: bisect.bisect_right (a, x, lo=0, hi=len(a), *, key=None)
 -- 函式: bisect.bisect (a, x, lo=0, hi=len(a), *, key=None)

     類似 *note bisect_left(): 2413.，但回傳的插入位置會在所有 'a' 當中
     的 'x' 的後面（右邊）。

     回傳的插入點 'ip' 將陣列 'a' 劃分為左右兩個切片，使得對於左切片而言
     ‘all(elem <= x for elem in a[lo : ip])’ 為真，對於右切片而言
     ‘all(elem > x for elem in a[ip : hi])’ 為真。

     在 3.10 版的變更: 新增 'key' 參數。

 -- 函式: bisect.insort_left (a, x, lo=0, hi=len(a), *, key=None)

     將元素 'x' 插入 list 'a'，並維持順序。

     此函式先使用 *note bisect_left(): 2413. 搜索插入位置，接著用
     ‘insert()’ 於 'a' 以將 'x' 插入，並維持添加元素後的順序。

     此函式只有在搜索時會使用 'key' 函式，插入時不會。

     注意雖然搜索是 'O'(log 'n')，但插入是 'O'('n')，因此此函式整體時間
     複雜度是 'O'('n')。

     在 3.10 版的變更: 新增 'key' 參數。

 -- 函式: bisect.insort_right (a, x, lo=0, hi=len(a), *, key=None)
 -- 函式: bisect.insort (a, x, lo=0, hi=len(a), *, key=None)

     類似 *note insort_left(): 2416.，但插入的位置會在所有 'a' 當中的
     'x' 的後面（右邊）。

     此函式先使用 *note bisect_right(): 2414. 搜索插入位置，接著用
     ‘insert()’ 於 'a' 以將 'x' 插入，並維持添加元素後的順序。

     此函式只有在搜索時會使用 'key' 函式，插入時不會。

     注意雖然搜索是 'O'(log 'n')，但插入是 'O'('n')，因此此函式整體時間
     複雜度是 'O'('n')。

     在 3.10 版的變更: 新增 'key' 參數。

* Menu:

* 效能考量::
* 搜尋一個已排序的 list::
* 範例: 範例<3>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/bisect.py


File: python.info,  Node: 效能考量,  Next: 搜尋一個已排序的 list,  Up: bisect --- 陣列二分演算法 Array bisection algorithm

5.8.7.1 效能考量
................

若在需要關注寫入時間的程式當中使用 'bisect()' 和 'insort()'，請特別注意
幾個事項：

   * 二分法在一段範圍的數值中做搜索的效率較佳，但若是要存取特定數值，使
     用字典的表現還是比較好。

   * 'insort()' 函式的複雜度為 'O'('n')，因為對數搜尋是以線性時間的插入
     步驟所主導 (dominate)。

   * 搜索函式為無狀態的 (stateless)，且鍵函式會在使用過後被丟棄。因此，
     如果搜索函式被使用於迴圈當中，鍵函式會不斷被重複呼叫於相同的 list 元
     素。如果鍵函式執行速度不快，請考慮將其以 *note functools.cache():
     241a. 包裝起來以減少重複的計算。另外，也可以透過搜尋預先計算好的鍵
     列表 (array of precomputed keys) 來定位插入點（如下方範例所示）。

也參考
......

   * 有序容器 (Sorted Collections)(1) 是一個使用 'bisect' 來管理資料之有
     序集合的高效能模組。

   * SortedCollection recipe(2) 使用二分法來建立一個功能完整的集合類別
     (collection class) 並帶有符合直覺的搜索方法 (search methods) 與支援
     鍵函式。鍵會預先被計算好，以減少搜索過程中多餘的鍵函式呼叫。

   ---------- Footnotes ----------

   (1) https://grantjenks.com/docs/sortedcollections/

   (2) https://code.activestate.com/recipes/577197-sortedcollection/


File: python.info,  Node: 搜尋一個已排序的 list,  Next: 範例<3>,  Prev: 效能考量,  Up: bisect --- 陣列二分演算法 Array bisection algorithm

5.8.7.2 搜尋一個已排序的 list
.............................

上面的 *note bisect functions: 2412. 在找到數值插入點上很有用，但一般的
數值搜尋任務上就不是那麼的方便。以下的五個函式展示了如何將其轉換成標準的
有序列表查找函式：

     def index(a, x):
         'Locate the leftmost value exactly equal to x'
         i = bisect_left(a, x)
         if i != len(a) and a[i] == x:
             return i
         raise ValueError

     def find_lt(a, x):
         'Find rightmost value less than x'
         i = bisect_left(a, x)
         if i:
             return a[i-1]
         raise ValueError

     def find_le(a, x):
         'Find rightmost value less than or equal to x'
         i = bisect_right(a, x)
         if i:
             return a[i-1]
         raise ValueError

     def find_gt(a, x):
         'Find leftmost value greater than x'
         i = bisect_right(a, x)
         if i != len(a):
             return a[i]
         raise ValueError

     def find_ge(a, x):
         'Find leftmost item greater than or equal to x'
         i = bisect_left(a, x)
         if i != len(a):
             return a[i]
         raise ValueError


File: python.info,  Node: 範例<3>,  Prev: 搜尋一個已排序的 list,  Up: bisect --- 陣列二分演算法 Array bisection algorithm

5.8.7.3 範例
............

*note bisect(): 2415. 函式可用於數值表中的查找 (numeric table lookup)，
這個範例使用 *note bisect(): 2415. 以基於一組有序的數值分界點來為一個考
試成績找到相對應的字母等級：90 以上是 'A'、80 到 89 為 'B'，依此類推：

     >>> def grade(score, breakpoints=[60, 70, 80, 90], grades='FDCBA'):
     ...     i = bisect(breakpoints, score)
     ...     return grades[i]
     ...
     >>> [grade(score) for score in [33, 99, 77, 70, 89, 90, 100]]
     ['F', 'A', 'C', 'C', 'B', 'A', 'A']

*note bisect(): 2415. 與 *note insort(): 2418. 函式也適用於內容為
tuples（元組）的 lists，'key' 引數可被用以取出在數值表中作為排序依據的欄
位：

     >>> from collections import namedtuple
     >>> from operator import attrgetter
     >>> from bisect import bisect, insort
     >>> from pprint import pprint

     >>> Movie = namedtuple('Movie', ('name', 'released', 'director'))

     >>> movies = [
     ...     Movie('Jaws', 1975, 'Spielberg'),
     ...     Movie('Titanic', 1997, 'Cameron'),
     ...     Movie('The Birds', 1963, 'Hitchcock'),
     ...     Movie('Aliens', 1986, 'Cameron')
     ... ]

     >>> # Find the first movie released after 1960
     >>> by_year = attrgetter('released')
     >>> movies.sort(key=by_year)
     >>> movies[bisect(movies, 1960, key=by_year)]
     Movie(name='The Birds', released=1963, director='Hitchcock')

     >>> # Insert a movie while maintaining sort order
     >>> romance = Movie('Love Story', 1970, 'Hiller')
     >>> insort(movies, romance, key=by_year)
     >>> pprint(movies)
     [Movie(name='The Birds', released=1963, director='Hitchcock'),
      Movie(name='Love Story', released=1970, director='Hiller'),
      Movie(name='Jaws', released=1975, director='Spielberg'),
      Movie(name='Aliens', released=1986, director='Cameron'),
      Movie(name='Titanic', released=1997, director='Cameron')]

如果鍵函式會消耗較多運算資源，那可以在預先計算好的鍵列表中搜索該紀錄的索
引值，以減少重複的函式呼叫：

     >>> data = [('red', 5), ('blue', 1), ('yellow', 8), ('black', 0)]
     >>> data.sort(key=lambda r: r[1])       # Or use operator.itemgetter(1).
     >>> keys = [r[1] for r in data]         # Precompute a list of keys.
     >>> data[bisect_left(keys, 0)]
     ('black', 0)
     >>> data[bisect_left(keys, 1)]
     ('blue', 1)
     >>> data[bisect_left(keys, 5)]
     ('red', 5)
     >>> data[bisect_left(keys, 8)]
     ('yellow', 8)


File: python.info,  Node: array --- 高效率的數值型陣列,  Next: weakref --- 弱參照,  Prev: bisect --- 陣列二分演算法 Array bisection algorithm,  Up: 資料型別

5.8.8 ‘array’ -- 高效率的數值型陣列
-----------------------------------

__________________________________________________________________

這個模組定義了一個物件型別，可以簡潔的表達一個包含基本數值的陣列：字元、
整數、浮點數。陣列是一個非常類似 list（串列）的序列型別，除了陣列會限制
儲存的物件型別。在建立陣列時可以使用一個字元的 'type code' 來指定儲存的
資料型別。以下為有被定義的 type codes：

Type code       C Type                   Python Type             所需的最小位元組 (bytes)    註解
                                                                                             
---------------------------------------------------------------------------------------------------------
                                                                                             
‘'b'’           signed char              int                     1
                                                                 
                                                                                             
‘'B'’           unsigned char            int                     1
                                                                 
                                                                                             
‘'u'’           wchar_t                  Unicode character       2                           (1)
                                                                                             
                                                                                             
‘'w'’           Py_UCS4                  Unicode character       4
                                                                 
                                                                                             
‘'h'’           signed short             int                     2
                                                                 
                                                                                             
‘'H'’           unsigned short           int                     2
                                                                 
                                                                                             
‘'i'’           signed int               int                     2
                                                                 
                                                                                             
‘'I'’           unsigned int             int                     2
                                                                 
                                                                                             
‘'l'’           signed long              int                     4
                                                                 
                                                                                             
‘'L'’           unsigned long            int                     4
                                                                 
                                                                                             
‘'q'’           signed long long         int                     8
                                                                 
                                                                                             
‘'Q'’           unsigned long long       int                     8
                                                                 
                                                                                             
‘'f'’           float                    float                   4
                                                                 
                                                                                             
‘'d'’           double                   float                   8
                                                                 

註解：

  1. 根據平台的不同，它有可能是 16 位元或者 32 位元。

     在 3.9 版的變更: 目前 ‘array('u')’ 使用 ‘wchar_t’ 取代已棄用的
     ‘Py_UNICODE’ 作為 C type。這個異動並沒有影響到它的作用，因爲自從
     Python 3.3 開始 ‘Py_UNICODE’ 即為 ‘wchar_t’ 的別名。

     Deprecated since version 3.3, will be removed in version 3.16:
     Please migrate to ‘'w'’ typecode.

實際上數值的表示方法是被機器的架構所決定（更精準地說，被 C 的實作方法決
定）。實際的大小可以透過 *note array.itemsize: 2420. 屬性存取。

這個模組定義了以下項目：

 -- 資料: array.typecodes

     一個包含所有可用的 type codes 的字串。

這個模組定義了下方的型別：

 -- 類別: array.array (typecode[, initializer])

     一個新的陣列中的元素被 'typecode' 限制，並由選用的 'initializer' 參
     數初始化，'initializer' 必須是一個 *note bytes: 1a5. 或 *note
     bytearray: 4e3. 物件、一個 Unicode 字串或包含適當型別元素的可疊代物
     件 (iterable)。

     如果給定的是一個 *note bytes: 1a5. 或 *note bytearray: 4e3. 物件，
     新的陣列初始化時會傳入 *note frombytes(): 120a. 方法；如為 Unicode
     字串則會傳入 *note fromunicode(): 2422. 方法；其他情況時， 一個
     initializer 的可疊代物件將被傳入 *note extend(): 2423. 方法之中來將
     初始項目新增至陣列。

     陣列支援常見的序列操作，包含索引 (indexing)、切片 (slicing)、串接
     (concatenation)、相乘 (multiplication) 等。當使用切片進行賦值時，賦
     值的陣列必須具備相同的 type code，其他型別的數值將導致 *note
     TypeError: 4dd.。陣列同時也實作了緩衝區介面，可以在任何支援 *note
     bytes-like objects: cd4. 的地方使用。

     引發*note 稽核事件 (auditing event): 17bd. ‘array.__new__’ 並附帶引
     數 ‘typecode’、‘initializer’。

      -- 屬性: typecode

          typecode 字元被用在建立陣列時。

      -- 屬性: itemsize

          陣列當中的一個元素在內部需要的位元組長度。

      -- 方法: append (x)

          新增一個元素 'x' 到陣列的最尾端。

      -- 方法: buffer_info ()

          回傳一個 tuple ‘(address, length)’ 表示當前的記憶體位置和陣列
          儲存元素的緩衝區記憶體長度。緩衝區的長度單位是位元組，並可以用
          ‘array.buffer_info()[1] * array.itemsize’ 計算得到。這偶爾會在
          底層操作需要記憶體位置的輸出輸入時很有用，例如 ‘ioctl()’ 指令
          。只要陣列存在且沒有使用任何更改長度的操作時，回傳的數值就有效
          。

               備註: 當使用來自 C 或 C++ 程式碼（這是唯一使得這個資訊有
               效的途徑）的陣列物件時，更適當的做法是使用陣列物件支援的
               緩衝區介面。這個方法維護了向後兼容性，並應該在新的程式碼
               中避免。關於緩衝區介面的文件在*note 緩衝協定 (Buffer
               Protocol): 367.。

      -- 方法: byteswap ()

          "Byteswap" 所有陣列中的物件。這只有支援物件長度為 1、2、4 或 8
          位元組的陣列，其他型別的值會導致 *note RuntimeError: 179.。這
          在從機器讀取位元順序不同的檔案時很有用。

      -- 方法: count (x)

          回傳 'x' 在陣列中出現了幾次。

      -- 方法: extend (iterable)

          從 'iterable' 中新增元素到陣列的尾端，如果 'iterable' 是另一個
          陣列，它必須有完全相同的 type code，如果不同會導致 *note
          TypeError: 4dd.。如果 'iterable' 不是一個陣列，它必須可以被疊
          代 (iterable) 且其中的元素必須是可以被加入陣列中的正確型別。

      -- 方法: frombytes (buffer)

          從 *note bytes-like object: cd4. 中新增元素。讀取時會將其內容
          當作一個機器數值組成的陣列（就像從檔案中使用 *note fromfile():
          2429. 方法讀出的資料）。

          在 3.2 版被加入: 將 ‘fromstring()’ 更名為 *note frombytes():
          120a.，使其更加清晰易懂。

      -- 方法: fromfile (f, n)

          從 *note file object: 115b. 'f' 讀取 'n' 個元素（作為機器數值
          ），接著將這些元素加入陣列的最尾端。如果只有少於 'n' 個有效的
          元素會導致 *note EOFError: 126c.，但有效的元素仍然會被加入陣列
          中。

      -- 方法: fromlist (list)

          從 list 中新增元素。這等價於 ‘for x in list: a.append(x)’，除
          了有型別錯誤產生時，陣列會保持原狀不會被更改。

      -- 方法: fromunicode (s)

          Extends this array with data from the given Unicode string.
          The array must have type code ‘'u'’ or ‘'w'’; otherwise a
          *note ValueError: 1e7. is raised.  Use
          ‘array.frombytes(unicodestring.encode(enc))’ to append Unicode
          data to an array of some other type.

      -- 方法: index (x[, start[, stop]])

          回傳 'i' 的最小數值，使得 'i' 成為陣列之中第一次出現 'x' 的索
          引。選擇性的引數 'start' 及 'stop' 則可以被用來在指定的陣列空
          間中搜尋 'x'。如果 'x' 不存在將導致 *note ValueError: 1e7.。

          在 3.10 版的變更: 新增選擇性的參數 'start' 及 'stop'。

      -- 方法: insert (i, x)

          在位置 'i' 之前插入一個元素 'x'。負數的索引值會從陣列尾端開始
          數。

      -- 方法: pop ([i])

          移除並回傳陣列索引值 'i' 的元素。選擇性的引數 'i' 預設為 ‘-1’，
          所以預設會刪除並回傳最後一個元素。

      -- 方法: remove (x)

          從陣列中刪除第一個出現的 'x'。

      -- 方法: clear ()

          Remove all elements from the array.

          在 3.13 版被加入.

      -- 方法: reverse ()

          反轉陣列中元素的順序。

      -- 方法: tobytes ()

          將陣列轉為另一個機器數值組成的陣列並回傳它的位元組表示（跟用
          *note tofile(): 242f. 方法寫入檔案時的位元序列相同）。

          在 3.2 版被加入: 為了明確性，過去的 ‘tostring()’ 已更名為
          *note tobytes(): 1209.。

      -- 方法: tofile (f)

          將所有元素（作為機器數值）寫入 *note file object: 115b. 'f'。

      -- 方法: tolist ()

          不更改元素，將陣列轉為一般的 list。

      -- 方法: tounicode ()

          Convert the array to a Unicode string.  The array must have a
          type ‘'u'’ or ‘'w'’; otherwise a *note ValueError: 1e7. is
          raised.  Use ‘array.tobytes().decode(enc)’ to obtain a Unicode
          string from an array of some other type.

The string representation of array objects has the form ‘array(typecode,
initializer)’.  The 'initializer' is omitted if the array is empty,
otherwise it is a Unicode string if the 'typecode' is ‘'u'’ or ‘'w'’,
otherwise it is a list of numbers.  The string representation is
guaranteed to be able to be converted back to an array with the same
type and value using *note eval(): 163, so long as the *note array: 186.
class has been imported using ‘from array import array’.  Variables
‘inf’ and ‘nan’ must also be defined if it contains corresponding
floating-point values.  Examples:

     array('l')
     array('w', 'hello \u2641')
     array('l', [1, 2, 3, 4, 5])
     array('d', [1.0, 2.0, 3.14, -inf, nan])

也參考
......

*note struct: c0. 模組

     將包含不同資料類型的二進位資料包裝與解開包裝。

NumPy(1)

     NumPy 套件定義了另一個陣列型別

   ---------- Footnotes ----------

   (1) https://numpy.org/


File: python.info,  Node: weakref --- 弱參照,  Next: types --- 動態型別建立與內建型別名稱,  Prev: array --- 高效率的數值型陣列,  Up: 資料型別

5.8.9 ‘weakref’ -- 弱參照
-------------------------

'原始碼：'Lib/weakref.py(1)

__________________________________________________________________

*note weakref: fc. 模組允許 Python 程式設計師建立對物件的 '弱參照'。

在以下文章中，術語 '參照目標 (referent)' 表示被弱參照所參考的物件。

對物件的弱參照不足以使物件保持存在：當對參照目標的唯一剩下的參照是弱參照
時，*note garbage collection: 181c. 可以自由地銷毀參照目標並將其記憶體重
新用於其他用途。然而，在物件被確實銷毀之前，即使沒有對該物件的強參照
(strong reference)，弱參照也可能會回傳該物件。

弱參照的主要用途是實作保存大型物件的快取或對映，其不希望大型物件僅僅因為
它出現在快取或對映中而保持存在。

例如，如果你有許多大型的二進位影像物件，你可能會想要為每個物件關聯
(associate) 一個名稱。如果你使用 Python 字典將名稱對映到影像，或將影像對
映到名稱，則影像物件將保持存活，僅因為它們在字典中作為值 (value) 或鍵
(key) 出現。*note weakref: fc. 模組提供的 *note WeakKeyDictionary: 1871.
和 *note WeakValueDictionary: 1870. 類別是另一種選擇，它們使用弱參照來建
構對映，這些對映不會僅因為物件出現在對映物件中而使物件保持存活。例如，如
果一個影像物件是 *note WeakValueDictionary: 1870. 中的一個值，那麼當對該
影像物件最後的參照是弱對映 (weak mapping) 所持有的弱參照時，垃圾回收
(garbage collection) 可以回收該物件，且其對應的條目在弱對映中會被完全地
刪除。

*note WeakKeyDictionary: 1871. 和 *note WeakValueDictionary: 1870. 在其
實作中使用弱參照，在弱參照上設定回呼函式，此弱參照在垃圾回收取回鍵或值時
通知弱字典。*note WeakSet: 581. 實作了 *note set: 57d. 介面，但保留對其
元素的弱參照，就像 *note WeakKeyDictionary: 1871. 一樣。

*note finalize: a1f. 提供了一種直接的方法來註冊在物件被垃圾回收時呼叫的
清理函式。這比在原始弱參照上設定回呼函式更容易使用，因為模組在物件被回收
前會自動確保最終化器 (finalizer) 保持存活。

大多數程式應該發現使用這些弱容器種類之一或 *note finalize: a1f. 就足夠了
—通常不需要直接建立自己的弱參照。低層級的機制由 *note weakref: fc. 模組
公開，以利於進階用途。

並非所有物件都可以被弱參照。支援弱參照的物件包括類別實例、用 Python （但
不是C）編寫的函式、實例方法、集合、凍結集合 (frozenset)、一些*note
檔案物件: 115b.、*note 產生器: 1004.、類型物件、socket、陣列、雙向佇列、
正規表示式模式物件和程式碼物件。

在 3.2 版的變更: 新增了對 thread.lock、threading.Lock 和程式碼物件的支援
。

一些內建型別，例如 *note list: 5b6. 和 *note dict: 23b. 不直接支援弱參照
，但可以透過子類別化來支援：

     class Dict(dict):
         pass

     obj = Dict(red=1, green=2, blue=3)   # 這個物件是可被弱參照的

'CPython 實作細節：' 其他內建型別，例如 *note tuple: 322. 和 *note int:
23c. 即使在子類別化時也不支援弱參照。

擴充型別 (extension type) 可以輕易地支援弱參照；請參閱 *note Weak
Reference Support: 2434.。

當為給定的型別定義 ‘__slots__’ 時，弱參照支援將被停用，除非
‘'__weakref__'’ 字串也存在於 ‘__slots__’ 宣告的字串序列中。詳情請參閱
*note __slots__ 文件: 1e44.。

 -- 類別: weakref.ref (object[, callback])

     回傳對 'object' 的弱參照。如果參照目標仍存活，則可以透過呼叫參照物
     件來取回原始物件；如果參照目標已不存活，呼叫參照物件將導致 *note
     None: 61b. 被回傳。如果 'callback' 被提供而非 *note None: 61b.，且
     回傳的弱參照物件仍存活，那麼當物件即將被最終化 (finalize) 時，回呼
     將被呼叫；弱參照物件將作為唯一的參數傳遞給回呼；參照物件將不再可用
     。

     為同一個物件建構多個弱參照是可行的。為每個弱參照註冊的回呼將按照最
     新到最舊註冊的回呼順序來被呼叫。

     回呼引發的例外將在標準錯誤輸出中被註明，但無法被傳播；它們的處理方
     式與物件的 *note __del__(): 1e36. 方法引發的例外完全相同。

     如果 'object' 是*note 可雜湊的: 5b5.，那麼弱參照就是可雜湊的。即使
     在 'object' 被刪除後，它們仍將保留其雜湊值。如果僅在 'object' 刪除
     後才第一次呼叫 *note hash(): 58f.，則該呼叫將引發 *note TypeError:
     4dd.。

     弱參照支援相等性的測試，但不支援排序。如果參照目標仍存活，則兩個參
     照與其參照目標具有相同的相等關係（無論 'callback' 如何）。如果任一
     參照目標已被刪除，則僅當參照物件是同一物件時，參照才相等。

     這是一個可子類別化的型別，而不是一個工廠函式。

      -- 屬性: __callback__

          此唯讀屬性回傳目前與弱參照關聯的回呼。如果沒有回呼或弱參照的參
          照目標已不存活，那麼該屬性的值為 ‘None’。

     在 3.4 版的變更: 新增 *note __callback__: f92. 屬性。

 -- 函式: weakref.proxy (object[, callback])

     回傳一個使用弱參照的 'object' 的代理 (proxy)。這支援在大多數情境中
     使用代理，而不需要對弱參照物件明確地取消參照。回傳的物件將具有
     ‘ProxyType’ 或 ‘CallableProxyType’ 型別，具體取決於 'object' 是否為
     可呼叫物件。無論參照目標如何，代理物件都不是 *note hashable: 5b5.；
     這避免了與其基本可變物件本質相關的許多問題，並阻止它們作為字典的鍵
     被使用。'callback' 與 *note ref(): f91. 函式的同名參數是相同的。

     在參照目標被垃圾回收後存取代理物件的屬性會引發 *note
     ReferenceError: 147d.。

     在 3.8 版的變更: 提供對代理物件的運算子支援，以包括矩陣乘法運算子
     ‘@’ 和 ‘@=’。

 -- 函式: weakref.getweakrefcount (object)

     回傳參照 'object' 的弱參照和代理的數量。

 -- 函式: weakref.getweakrefs (object)

     回傳參照 'object' 的所有弱參照和代理物件的一個串列。

 -- 類別: weakref.WeakKeyDictionary ([dict])

     弱參照鍵的對映類別。當不再有對鍵的強參照時，字典中的條目將被丟棄。
     這可用於將附加資料與應用程式其他部分擁有的物件相關聯，而無需向這些
     物件新增屬性。這對於覆蓋屬性存取的物件特別有用。

     請注意，當將與現有鍵具有相同值的鍵（但識別性不相等）插入字典時，它
     會替換該值，但不會替換現有鍵。因此，當刪除對原始鍵的參照時，它也會
     刪除字典中的條目：

          >>> class T(str): pass
          ...
          >>> k1, k2 = T(), T()
          >>> d = weakref.WeakKeyDictionary()
          >>> d[k1] = 1   # d = {k1: 1}
          >>> d[k2] = 2   # d = {k1: 2}
          >>> del k1      # d = {}

     一個變通的解法是在重新賦值 (reassignment) 之前刪除鍵：

          >>> class T(str): pass
          ...
          >>> k1, k2 = T(), T()
          >>> d = weakref.WeakKeyDictionary()
          >>> d[k1] = 1   # d = {k1: 1}
          >>> del d[k1]
          >>> d[k2] = 2   # d = {k2: 2}
          >>> del k1      # d = {k2: 2}

     在 3.9 版的變更: 新增對 ‘|’ 和 ‘|=’ 運算子的支持，如 PEP 584(2) 中
     所說明。

*note WeakKeyDictionary: 1871. 物件有一個直接公開內部參照的附加方法。參
照在被使用時不保證是 "存活的"，因此在使用之前需要檢查呼叫參照的結果。這
可以用來防止建立會導致垃圾回收器保留鍵的時間超過其所需時間的參照。

 -- 方法: WeakKeyDictionary.keyrefs ()

     回傳對鍵的弱參照的可疊代物件。

 -- 類別: weakref.WeakValueDictionary ([dict])

     弱參照值的對映類別。當不再存在對值的強參照時，字典中的條目將被丟棄
     。

     在 3.9 版的變更: 新增對 ‘|’ 和 ‘|=’ 運算子的支持，如 PEP 584(3) 中
     所說明。

*note WeakValueDictionary: 1870. 物件有一個附加方法，它與 *note
WeakKeyDictionary.keyrefs(): 2437. 方法有相同的問題。

 -- 方法: WeakValueDictionary.valuerefs ()

     回傳對值的弱參照的可疊代物件。

 -- 類別: weakref.WeakSet ([elements])

     保留對其元素的弱參照的集合類別。當不再存在對某個元素的強參照時，該
     元素將被丟棄。

 -- 類別: weakref.WeakMethod (method[, callback])

     一個特製的 *note ref: f91. 子類別，其模擬對繫結方法 (bound method)
     （即在類別上定義並在實例上查找的方法）的弱參照。由於繫結方法是短暫
     存在的，因此標準弱參照無法保留它。*note WeakMethod: f90. 有特殊的程
     式碼來重新建立繫結方法，直到物件或原始函式死亡：

          >>> class C:
          ...     def method(self):
          ...         print("method called!")
          ...
          >>> c = C()
          >>> r = weakref.ref(c.method)
          >>> r()
          >>> r = weakref.WeakMethod(c.method)
          >>> r()
          <bound method C.method of <__main__.C object at 0x7fc859830220>>
          >>> r()()
          method called!
          >>> del c
          >>> gc.collect()
          0
          >>> r()
          >>>

     'callback' 與 *note ref(): f91. 函式的同名參數是相同的。

     在 3.4 版被加入.

 -- 類別: weakref.finalize (obj, func, /, *args, **kwargs)

     回傳可呼叫的最終化器物件，此物件在 'obj' 被垃圾回收時會被呼叫。與一
     般的弱參照不同，最終化器將始終存在，直到參照物件被回收為止，從而大
     大簡化了生命週期管理。

     最終化器在被呼叫（明確呼叫或在垃圾回收時）之前被視為'存活'，之後它
     就會'死亡'。呼叫存活的最終化器會回傳 ‘func(*arg, **kwargs)’ 的計算
     結果，而呼叫死亡的最終化器會回傳 *note None: 61b.。

     垃圾回收期間最終化器回呼引發的例外會在標準錯誤輸出中顯示，但無法傳
     播。它們的處理方式與從物件的 *note __del__(): 1e36. 方法或弱參照的
     回呼引發的例外相同。

     當程式結束時，除非該最終化器的 *note atexit: 9. 屬性已被設定為
     false，否則每個存活的最終化器會被呼叫。它們以與建立相反的順序被呼叫
     。

     當模組的 globals 可能被 *note None: 61b. 取代時，最終化器永遠不會在
     *note interpreter shutdown: 133. 的後期調用（invoke）其回呼。

      -- 方法: __call__ ()

          如果 'self' 仍存活，則將其標記為死亡並回傳呼叫 ‘func(*args,
          **kwargs)’ 的結果。如果 'self' 已死亡，則回傳 *note None:
          61b.。

      -- 方法: detach ()

          如果 'self' 仍存活，則將其標記為死亡並回傳元組 ‘(obj, func,
          args, kwargs)’。如果 'self' 已死亡，則回傳 *note None: 61b.。

      -- 方法: peek ()

          如果 'self' 仍存活，則回傳元組 ‘(obj, func, args, kwargs)’。如
          果 'self' 已死亡，則回傳 *note None: 61b.。

      -- 屬性: alive

          如果最終化器仍存活，則屬性為 true，否則為 false。

      -- 屬性: atexit

          一個可寫的布林屬性，預設為 true。當程式結束時，它會呼叫 *note
          atexit: 243d. 為 true 的所有剩餘且仍存活的最終化器。它們以與建
          立相反的順序被呼叫。

          備註: 確保 'func'、'args' 和 'kwargs' 不直接或間接擁有對 'obj'
          的任何參照非常重要，否則 'obj' 將永遠不會被垃圾回收。尤其
          'func' 不應該是 'obj' 的繫結方法。

     在 3.4 版被加入.

 -- 資料: weakref.ReferenceType

     弱參照物件的型別物件。

 -- 資料: weakref.ProxyType

     非可呼叫物件的代理的型別物件。

 -- 資料: weakref.CallableProxyType

     可呼叫物件的代理的型別物件。

 -- 資料: weakref.ProxyTypes

     包含代理的所有型別物件的序列。這可以讓測試物件是否為代理變得更簡單
     ，而無需依賴命名兩種代理型別。

也參考
......

PEP 205(4) - 弱參照

     此功能的提案和理由，包括早期實作的連結以及其他語言中類似功能的資訊
     。

* Menu:

* 弱參照物件::
* 範例: 範例<4>.
* 最終化器物件::
* 最終化器與 __del__() 方法的比較: 最終化器與 __del__ 方法的比較.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/weakref.py

   (2) https://peps.python.org/pep-0584/

   (3) https://peps.python.org/pep-0584/

   (4) https://peps.python.org/pep-0205/


File: python.info,  Node: 弱參照物件,  Next: 範例<4>,  Up: weakref --- 弱參照

5.8.9.1 弱參照物件
..................

弱參照物件除了 *note ref.__callback__: f92. 之外沒有任何方法和屬性。弱參
照物件允許透過呼叫來獲取參照目標（如果它仍然存在）：

     >>> import weakref
     >>> class Object:
     ...     pass
     ...
     >>> o = Object()
     >>> r = weakref.ref(o)
     >>> o2 = r()
     >>> o is o2
     True

如果參照目標不再存活，則呼叫參照物件將回傳 *note None: 61b.：

     >>> del o, o2
     >>> print(r())
     None

應該使用運算式 ‘ref() is not None’ 來測試弱參照物件是否仍然存活。需要使
用參照物件的應用程式程式碼通常應遵循以下模式：

     # r is a weak reference object
     o = r()
     if o is None:
         # referent has been garbage collected
         print("Object has been deallocated; can't frobnicate.")
     else:
         print("Object is still live!")
         o.do_something_useful()

使用對「活性 (liveness)」的單獨測試會在執行緒應用程式中建立競爭條件
(race condition)；另一個執行緒可能在弱參照被呼叫之前讓該弱參照失效；上方
顯示的慣用作法在執行緒應用程式和單執行緒應用程式中都是安全的。

可以透過子類別化來建立 *note ref: f91. 物件的特殊版本。這在 *note
WeakValueDictionary: 1870. 的實作中被使用，以減少對映中每個條目的記憶體
開銷。這對於將附加資訊與參照相關聯最有用，但也可用於在呼叫上插入附加處理
以檢索參照目標。

這個範例展示如何使用 *note ref: f91. 的子類別來儲存有關物件的附加資訊並
影響存取參照目標時回傳的值：

     import weakref

     class ExtendedRef(weakref.ref):
         def __init__(self, ob, callback=None, /, **annotations):
             super().__init__(ob, callback)
             self.__counter = 0
             for k, v in annotations.items():
                 setattr(self, k, v)

         def __call__(self):
             """Return a pair containing the referent and the number of
             times the reference has been called.
             """
             ob = super().__call__()
             if ob is not None:
                 self.__counter += 1
                 ob = (ob, self.__counter)
             return ob


File: python.info,  Node: 範例<4>,  Next: 最終化器物件,  Prev: 弱參照物件,  Up: weakref --- 弱參照

5.8.9.2 範例
............

這個簡單的範例展示了應用程式如何使用物件 ID 來檢索它以前見過​​的物件。物件
的 ID 之後可以在其他資料結構中使用，而不必強制物件保持存活，但如果這樣做
，仍然可以透過 ID 檢索物件。

     import weakref

     _id2obj_dict = weakref.WeakValueDictionary()

     def remember(obj):
         oid = id(obj)
         _id2obj_dict[oid] = obj
         return oid

     def id2obj(oid):
         return _id2obj_dict[oid]


File: python.info,  Node: 最終化器物件,  Next: 最終化器與 __del__ 方法的比較,  Prev: 範例<4>,  Up: weakref --- 弱參照

5.8.9.3 最終化器物件
....................

使用 *note finalize: a1f. 的最大優點是可以輕鬆註冊回呼，而無需保留回傳的
最終化器物件。例如

     >>> import weakref
     >>> class Object:
     ...     pass
     ...
     >>> kenny = Object()
     >>> weakref.finalize(kenny, print, "You killed Kenny!")
     <finalize object at ...; for 'Object' at ...>
     >>> del kenny
     You killed Kenny!

最終化器也可以直接被呼叫。然而，最終化器最多會調用回呼一次。

     >>> def callback(x, y, z):
     ...     print("CALLBACK")
     ...     return x + y + z
     ...
     >>> obj = Object()
     >>> f = weakref.finalize(obj, callback, 1, 2, z=3)
     >>> assert f.alive
     >>> assert f() == 6
     CALLBACK
     >>> assert not f.alive
     >>> f()                     # callback not called because finalizer dead
     >>> del obj                 # callback not called because finalizer dead

你可以使用最終化器的 *note detach(): 243a. 方法來取消註冊最終化器。這會
殺死最終化器並回傳建立建構函式時傳遞給建構函式的引數。

     >>> obj = Object()
     >>> f = weakref.finalize(obj, callback, 1, 2, z=3)
     >>> f.detach()
     (<...Object object ...>, <function callback ...>, (1, 2), {'z': 3})
     >>> newobj, func, args, kwargs = _
     >>> assert not f.alive
     >>> assert newobj is obj
     >>> assert func(*args, **kwargs) == 6
     CALLBACK

除非你將 *note atexit: 243d. 屬性設為 *note False: adb.，否則當程式結束
時，最終化器將會被呼叫如果其仍然存在。例如

     >>> obj = Object()
     >>> weakref.finalize(obj, print, "obj dead or exiting")
     <finalize object at ...; for 'Object' at ...>
     >>> exit()
     obj dead or exiting


File: python.info,  Node: 最終化器與 __del__ 方法的比較,  Prev: 最終化器物件,  Up: weakref --- 弱參照

5.8.9.4 最終化器與 ‘__del__()’ 方法的比較
.........................................

假設我們要建立一個類別，其實例代表臨時目錄。當以下任一事件發生時，應刪除
目錄及其內容：

   * 該物件被垃圾回收，

   * 該物件的 ‘remove()’ 方法被呼叫，或者

   * 程式結束。

我們可以用以下的方式來嘗試使用 *note __del__(): 1e36. 方法實作該類別：

     class TempDir:
         def __init__(self):
             self.name = tempfile.mkdtemp()

         def remove(self):
             if self.name is not None:
                 shutil.rmtree(self.name)
                 self.name = None

         @property
         def removed(self):
             return self.name is None

         def __del__(self):
             self.remove()

從 Python 3.4 開始，*note __del__(): 1e36. 方法不再阻止參照循環
(reference cycle) 被垃圾回收，並且在 *note interpreter shutdown: 133. 期
間不再強制將模組的 globals 設為 *note None: 61b.。所以這段程式碼在
CPython 上應該可以正常運作。

然而，眾所周知，對 *note __del__(): 1e36. 方法的處理是特地實作的，因為它
依賴於直譯器的垃圾回收器實作的內部細節。

更耐用的替代方案可以是定義一個最終化器，其僅參照需要的特定函式和物件，而
不是存取物件的完整狀態：

     class TempDir:
         def __init__(self):
             self.name = tempfile.mkdtemp()
             self._finalizer = weakref.finalize(self, shutil.rmtree, self.name)

         def remove(self):
             self._finalizer()

         @property
         def removed(self):
             return not self._finalizer.alive

定義如下，我們的最終化器僅接收對適當清理目錄所需的詳細資訊的參照。如果物
件從未被垃圾回收，則最終化器仍將在結束時被呼叫。

基於 weakref 的最終化器的另一個優點是它們可用於為定義由第三方控制的類別
註冊最終化器，例如在卸載模組時執行程式碼：

     import weakref, sys
     def unloading_module():
         # implicit reference to the module globals from the function body
     weakref.finalize(sys.modules[__name__], unloading_module)

     備註: 如果在程式結束時在常駐的 (daemonic) 執行緒中建立最終化器物件
     ，則最終化器有可能在結束時不會被呼叫。然而，在常駐的執行緒中 *note
     atexit.register(): 821.、‘try: ... finally: ...’ 和 ‘with: ...’ 也
     不保證清理會發生。


File: python.info,  Node: types --- 動態型別建立與內建型別名稱,  Next: copy --- 淺層 shallow 和深層 deep 複製操作,  Prev: weakref --- 弱參照,  Up: 資料型別

5.8.10 ‘types’ -- 動態型別建立與內建型別名稱
--------------------------------------------

'原始碼：'Lib/types.py(1)

__________________________________________________________________

This module defines utility functions to assist in dynamic creation of
new types.

It also defines names for some object types that are used by the
standard Python interpreter, but not exposed as builtins like *note int:
23c. or *note str: 3f2. are.

Finally, it provides some additional type-related utility classes and
functions that are not fundamental enough to be builtins.

* Menu:

* Dynamic Type Creation::
* Standard Interpreter Types::
* Additional Utility Classes and Functions::
* Coroutine Utility Functions::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/types.py


File: python.info,  Node: Dynamic Type Creation,  Next: Standard Interpreter Types,  Up: types --- 動態型別建立與內建型別名稱

5.8.10.1 Dynamic Type Creation
..............................

 -- 函式: types.new_class (name, bases=(), kwds=None, exec_body=None)

     Creates a class object dynamically using the appropriate metaclass.

     The first three arguments are the components that make up a class
     definition header: the class name, the base classes (in order), the
     keyword arguments (such as ‘metaclass’).

     The 'exec_body' argument is a callback that is used to populate the
     freshly created class namespace.  It should accept the class
     namespace as its sole argument and update the namespace directly
     with the class contents.  If no callback is provided, it has the
     same effect as passing in ‘lambda ns: None’.

     在 3.3 版被加入.

 -- 函式: types.prepare_class (name, bases=(), kwds=None)

     Calculates the appropriate metaclass and creates the class
     namespace.

     The arguments are the components that make up a class definition
     header: the class name, the base classes (in order) and the keyword
     arguments (such as ‘metaclass’).

     The return value is a 3-tuple: ‘metaclass, namespace, kwds’

     'metaclass' is the appropriate metaclass, 'namespace' is the
     prepared class namespace and 'kwds' is an updated copy of the
     passed in 'kwds' argument with any ‘'metaclass'’ entry removed.  If
     no 'kwds' argument is passed in, this will be an empty dict.

     在 3.3 版被加入.

     在 3.6 版的變更: The default value for the ‘namespace’ element of
     the returned tuple has changed.  Now an insertion-order-preserving
     mapping is used when the metaclass does not have a ‘__prepare__’
     method.

也參考
......

*note Metaclasses: 1e4a.

     Full details of the class creation process supported by these
     functions

PEP 3115(1) - Metaclasses in Python 3000

     Introduced the ‘__prepare__’ namespace hook

 -- 函式: types.resolve_bases (bases)

     Resolve MRO entries dynamically as specified by PEP 560(2).

     This function looks for items in 'bases' that are not instances of
     *note type: cef, and returns a tuple where each such object that
     has an *note __mro_entries__(): 1e4c. method is replaced with an
     unpacked result of calling this method.  If a 'bases' item is an
     instance of *note type: cef, or it doesn't have an
     ‘__mro_entries__()’ method, then it is included in the return tuple
     unchanged.

     在 3.7 版被加入.

 -- 函式: types.get_original_bases (cls, /)

     Return the tuple of objects originally given as the bases of 'cls'
     before the *note __mro_entries__(): 1e4c. method has been called on
     any bases (following the mechanisms laid out in PEP 560(3)).  This
     is useful for introspecting *note Generics: 476.

     For classes that have an ‘__orig_bases__’ attribute, this function
     returns the value of ‘cls.__orig_bases__’.  For classes without the
     ‘__orig_bases__’ attribute, ‘cls.__bases__’ is returned.

     舉例來說：

          from typing import TypeVar, Generic, NamedTuple, TypedDict

          T = TypeVar("T")
          class Foo(Generic[T]): ...
          class Bar(Foo[int], float): ...
          class Baz(list[str]): ...
          Eggs = NamedTuple("Eggs", [("a", int), ("b", str)])
          Spam = TypedDict("Spam", {"a": int, "b": str})

          assert Bar.__bases__ == (Foo, float)
          assert get_original_bases(Bar) == (Foo[int], float)

          assert Baz.__bases__ == (list,)
          assert get_original_bases(Baz) == (list[str],)

          assert Eggs.__bases__ == (tuple,)
          assert get_original_bases(Eggs) == (NamedTuple,)

          assert Spam.__bases__ == (dict,)
          assert get_original_bases(Spam) == (TypedDict,)

          assert int.__bases__ == (object,)
          assert get_original_bases(int) == (object,)

     在 3.12 版被加入.

也參考
......

PEP 560(4) - Core support for typing module and generic types

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3115/

   (2) https://peps.python.org/pep-0560/

   (3) https://peps.python.org/pep-0560/

   (4) https://peps.python.org/pep-0560/


File: python.info,  Node: Standard Interpreter Types,  Next: Additional Utility Classes and Functions,  Prev: Dynamic Type Creation,  Up: types --- 動態型別建立與內建型別名稱

5.8.10.2 Standard Interpreter Types
...................................

This module provides names for many of the types that are required to
implement a Python interpreter.  It deliberately avoids including some
of the types that arise only incidentally during processing such as the
‘listiterator’ type.

Typical use of these names is for *note isinstance(): 3e8. or *note
issubclass(): 765. checks.

If you instantiate any of these types, note that signatures may vary
between Python versions.

Standard names are defined for the following types:

 -- 資料: types.NoneType

     The type of *note None: 61b.

     在 3.10 版被加入.

 -- 資料: types.FunctionType
 -- 資料: types.LambdaType

     The type of user-defined functions and functions created by *note
     lambda: 1234. expressions.

     引發一個附帶引數 ‘code’ 的*note 稽核事件: 17bd. ‘function.__new__’。

     The audit event only occurs for direct instantiation of function
     objects, and is not raised for normal compilation.

 -- 資料: types.GeneratorType

     The type of *note generator: 1004.-iterator objects, created by
     generator functions.

 -- 資料: types.CoroutineType

     The type of *note coroutine: 438. objects, created by *note async
     def: 575. functions.

     在 3.5 版被加入.

 -- 資料: types.AsyncGeneratorType

     The type of *note asynchronous generator: 1f14.-iterator objects,
     created by asynchronous generator functions.

     在 3.6 版被加入.

 -- 類別: types.CodeType (**kwargs)

     The type of *note code objects: 1b6. such as returned by *note
     compile(): 178.

     引發一個附帶引數 ‘code’、‘filename’、‘name’、‘argcount’、
     ‘posonlyargcount’、‘kwonlyargcount’、‘nlocals’、‘stacksize’、
     ‘flags’ 的*note 稽核事件: 17bd. ‘code.__new__’。

     Note that the audited arguments may not match the names or
     positions required by the initializer.  The audit event only occurs
     for direct instantiation of code objects, and is not raised for
     normal compilation.

 -- 資料: types.CellType

     The type for cell objects: such objects are used as containers for
     a function's free variables.

     在 3.8 版被加入.

 -- 資料: types.MethodType

     The type of methods of user-defined class instances.

 -- 資料: types.BuiltinFunctionType
 -- 資料: types.BuiltinMethodType

     The type of built-in functions like *note len(): 5d4. or *note
     sys.exit(): 12dd, and methods of built-in classes.  (Here, the term
     "built-in" means "written in C".)

 -- 資料: types.WrapperDescriptorType

     The type of methods of some built-in data types and base classes
     such as *note object.__init__(): 655. or *note object.__lt__():
     129e.

     在 3.7 版被加入.

 -- 資料: types.MethodWrapperType

     The type of 'bound' methods of some built-in data types and base
     classes.  For example it is the type of ‘object().__str__’.

     在 3.7 版被加入.

 -- 資料: types.NotImplementedType

     The type of *note NotImplemented: 776.

     在 3.10 版被加入.

 -- 資料: types.MethodDescriptorType

     The type of methods of some built-in data types such as *note
     str.join(): 2088.

     在 3.7 版被加入.

 -- 資料: types.ClassMethodDescriptorType

     The type of 'unbound' class methods of some built-in data types
     such as ‘dict.__dict__['fromkeys']’.

     在 3.7 版被加入.

 -- 類別: types.ModuleType (name, doc=None)

     The type of *note modules: 1555.  The constructor takes the name of
     the module to be created and optionally its *note docstring: 1ffd.

          備註: Use *note importlib.util.module_from_spec(): db8. to
          create a new module if you wish to set the various
          import-controlled attributes.

      -- 屬性: __doc__

          The *note docstring: 1ffd. of the module.  Defaults to ‘None’.

      -- 屬性: __loader__

          The *note loader: 15a8. which loaded the module.  Defaults to
          ‘None’.

          This attribute is to match *note
          importlib.machinery.ModuleSpec.loader: 2451. as stored in the
          *note __spec__: 1ed6. object.

               備註: A future version of Python may stop setting this
               attribute by default.  To guard against this potential
               change, preferably read from the *note __spec__: 1ed6.
               attribute instead or use ‘getattr(module, "__loader__",
               None)’ if you explicitly need to use this attribute.

          在 3.4 版的變更: Defaults to ‘None’.  Previously the attribute
          was optional.

      -- 屬性: __name__

          The name of the module.  Expected to match *note
          importlib.machinery.ModuleSpec.name: 2453.

      -- 屬性: __package__

          Which *note package: 1ec1. a module belongs to.  If the module
          is top-level (i.e.  not a part of any specific package) then
          the attribute should be set to ‘''’, else it should be set to
          the name of the package (which can be *note __name__: 1316. if
          the module is a package itself).  Defaults to ‘None’.

          This attribute is to match *note
          importlib.machinery.ModuleSpec.parent: 1ed7. as stored in the
          *note __spec__: 1ed6. object.

               備註: A future version of Python may stop setting this
               attribute by default.  To guard against this potential
               change, preferably read from the *note __spec__: 1ed6.
               attribute instead or use ‘getattr(module, "__package__",
               None)’ if you explicitly need to use this attribute.

          在 3.4 版的變更: Defaults to ‘None’.  Previously the attribute
          was optional.

      -- 屬性: __spec__

          A record of the module's import-system-related state.
          Expected to be an instance of *note
          importlib.machinery.ModuleSpec: 1d5a.

          在 3.4 版被加入.

 -- 資料: types.EllipsisType

     The type of *note Ellipsis: 2062.

     在 3.10 版被加入.

 -- 類別: types.GenericAlias (t_origin, t_args)

     The type of *note parameterized generics: 656. such as ‘list[int]’.

     ‘t_origin’ should be a non-parameterized generic class, such as
     ‘list’, ‘tuple’ or ‘dict’.  ‘t_args’ should be a *note tuple: 322.
     (possibly of length 1) of types which parameterize ‘t_origin’:

          >>> from types import GenericAlias

          >>> list[int] == GenericAlias(list, (int,))
          True
          >>> dict[str, int] == GenericAlias(dict, (str, int))
          True

     在 3.9 版被加入.

     在 3.9.2 版的變更: This type can now be subclassed.

     也參考
     ......

     *note Generic Alias Types: 656.

          In-depth documentation on instances of ‘types.GenericAlias’

     PEP 585(1) - Type Hinting Generics In Standard Collections

          Introducing the ‘types.GenericAlias’ class

 -- 類別: types.UnionType

     The type of *note union type expressions: 766.

     在 3.10 版被加入.

 -- 類別: types.TracebackType (tb_next, tb_frame, tb_lasti, tb_lineno)

     The type of traceback objects such as found in
     ‘sys.exception().__traceback__’.

     See *note the language reference: a97. for details of the available
     attributes and operations, and guidance on creating tracebacks
     dynamically.

 -- 資料: types.FrameType

     The type of *note frame objects: 27e. such as found in *note
     tb.tb_frame: 1e27. if ‘tb’ is a traceback object.

 -- 資料: types.GetSetDescriptorType

     The type of objects defined in extension modules with
     ‘PyGetSetDef’, such as *note FrameType.f_locals: 165. or
     ‘array.array.typecode’.  This type is used as descriptor for object
     attributes; it has the same purpose as the *note property: 180.
     type, but for classes defined in extension modules.

 -- 資料: types.MemberDescriptorType

     The type of objects defined in extension modules with
     ‘PyMemberDef’, such as ‘datetime.timedelta.days’.  This type is
     used as descriptor for simple C data members which use standard
     conversion functions; it has the same purpose as the *note
     property: 180. type, but for classes defined in extension modules.

     In addition, when a class is defined with a *note __slots__: 1458.
     attribute, then for each slot, an instance of
     ‘MemberDescriptorType’ will be added as an attribute on the class.
     This allows the slot to appear in the class's *note __dict__: c04.

     'CPython 實作細節：' In other implementations of Python, this type
     may be identical to ‘GetSetDescriptorType’.

 -- 類別: types.MappingProxyType (mapping)

     Read-only proxy of a mapping.  It provides a dynamic view on the
     mapping's entries, which means that when the mapping changes, the
     view reflects these changes.

     在 3.3 版被加入.

     在 3.9 版的變更: Updated to support the new union (‘|’) operator
     from PEP 584(2), which simply delegates to the underlying mapping.

      -- Describe: key in proxy

          Return ‘True’ if the underlying mapping has a key 'key', else
          ‘False’.

      -- Describe: proxy[key]

          Return the item of the underlying mapping with key 'key'.
          Raises a *note KeyError: 2fb. if 'key' is not in the
          underlying mapping.

      -- Describe: iter(proxy)

          Return an iterator over the keys of the underlying mapping.
          This is a shortcut for ‘iter(proxy.keys())’.

      -- Describe: len(proxy)

          Return the number of items in the underlying mapping.

      -- 方法: copy ()

          Return a shallow copy of the underlying mapping.

      -- 方法: get (key[, default])

          Return the value for 'key' if 'key' is in the underlying
          mapping, else 'default'.  If 'default' is not given, it
          defaults to ‘None’, so that this method never raises a *note
          KeyError: 2fb.

      -- 方法: items ()

          Return a new view of the underlying mapping's items (‘(key,
          value)’ pairs).

      -- 方法: keys ()

          Return a new view of the underlying mapping's keys.

      -- 方法: values ()

          Return a new view of the underlying mapping's values.

      -- Describe: reversed(proxy)

          Return a reverse iterator over the keys of the underlying
          mapping.

          在 3.9 版被加入.

      -- Describe: hash(proxy)

          Return a hash of the underlying mapping.

          在 3.12 版被加入.

 -- 類別: types.CapsuleType

     The type of *note capsule objects: 245e.

     在 3.13 版被加入.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0585/

   (2) https://peps.python.org/pep-0584/


File: python.info,  Node: Additional Utility Classes and Functions,  Next: Coroutine Utility Functions,  Prev: Standard Interpreter Types,  Up: types --- 動態型別建立與內建型別名稱

5.8.10.3 Additional Utility Classes and Functions
.................................................

 -- 類別: types.SimpleNamespace

     A simple *note object: a2f. subclass that provides attribute access
     to its namespace, as well as a meaningful repr.

     Unlike *note object: a2f, with ‘SimpleNamespace’ you can add and
     remove attributes.

     *note SimpleNamespace: 1b5. objects may be initialized in the same
     way as *note dict: 23b.: either with keyword arguments, with a
     single positional argument, or with both.  When initialized with
     keyword arguments, those are directly added to the underlying
     namespace.  Alternatively, when initialized with a positional
     argument, the underlying namespace will be updated with key-value
     pairs from that argument (either a mapping object or an *note
     iterable: 11bf. object producing key-value pairs).  All such keys
     must be strings.

     The type is roughly equivalent to the following code:

          class SimpleNamespace:
              def __init__(self, mapping_or_iterable=(), /, **kwargs):
                  self.__dict__.update(mapping_or_iterable)
                  self.__dict__.update(kwargs)

              def __repr__(self):
                  items = (f"{k}={v!r}" for k, v in self.__dict__.items())
                  return "{}({})".format(type(self).__name__, ", ".join(items))

              def __eq__(self, other):
                  if isinstance(self, SimpleNamespace) and isinstance(other, SimpleNamespace):
                     return self.__dict__ == other.__dict__
                  return NotImplemented

     ‘SimpleNamespace’ may be useful as a replacement for ‘class NS:
     pass’.  However, for a structured record type use *note
     namedtuple(): 1ae. instead.

     ‘SimpleNamespace’ objects are supported by *note copy.replace():
     136.

     在 3.3 版被加入.

     在 3.9 版的變更: Attribute order in the repr changed from
     alphabetical to insertion (like ‘dict’).

     在 3.13 版的變更: Added support for an optional positional
     argument.

 -- 函式: types.DynamicClassAttribute (fget=None, fset=None, fdel=None,
          doc=None)

     Route attribute access on a class to __getattr__.

     This is a descriptor, used to define attributes that act
     differently when accessed through an instance and through a class.
     Instance access remains normal, but access to an attribute through
     a class will be routed to the class's __getattr__ method; this is
     done by raising AttributeError.

     This allows one to have properties active on an instance, and have
     virtual attributes on the class with the same name (see *note
     enum.Enum: 5d6. for an example).

     在 3.4 版被加入.


File: python.info,  Node: Coroutine Utility Functions,  Prev: Additional Utility Classes and Functions,  Up: types --- 動態型別建立與內建型別名稱

5.8.10.4 Coroutine Utility Functions
....................................

 -- 函式: types.coroutine (gen_func)

     This function transforms a *note generator: 1004. function into a
     *note coroutine function: d1d. which returns a generator-based
     coroutine.  The generator-based coroutine is still a *note
     generator iterator: b85, but is also considered to be a *note
     coroutine: 438. object and is *note awaitable: 193.  However, it
     may not necessarily implement the *note __await__(): 1e9d. method.

     If 'gen_func' is a generator function, it will be modified
     in-place.

     If 'gen_func' is not a generator function, it will be wrapped.  If
     it returns an instance of *note collections.abc.Generator: d81, the
     instance will be wrapped in an 'awaitable' proxy object.  All other
     types of objects will be returned as is.

     在 3.5 版被加入.


File: python.info,  Node: copy --- 淺層 shallow 和深層 deep 複製操作,  Next: pprint --- 資料美化列印器,  Prev: types --- 動態型別建立與內建型別名稱,  Up: 資料型別

5.8.11 ‘copy’ -- 淺層 (shallow) 和深層 (deep) 複製操作
------------------------------------------------------

'原始碼：'Lib/copy.py(1)

__________________________________________________________________

Python 的賦值陳述式不複製物件，而是建立目標和物件的繫結 (binding) 關係。
對於可變 (mutable) 或包含可變項目 (mutable item) 的集合，有時會需要一份
副本來改變特定副本，而不必改變其他副本。本模組提供了通用的淺層複製和深層
複製操作（如下所述）。

介面摘要：

 -- 函式: copy.copy (obj)

     Return a shallow copy of 'obj'.

 -- 函式: copy.deepcopy (obj[, memo])

     Return a deep copy of 'obj'.

 -- 函式: copy.replace (obj, /, **changes)

     Creates a new object of the same type as 'obj', replacing fields
     with values from 'changes'.

     在 3.13 版被加入.

 -- 例外: copy.Error

     引發針對特定模組的錯誤。
淺層與深層複製的區別僅與複合物件（即包含 list 或類別的實例等其他物件的物
件）相關：

   * '淺層複製'建構一個新的複合物件，然後（在儘可能的範圍內）將原始物件
     中找到的物件的'參照'插入其中。

   * '深層複製'建構一個新的複合物件，然後遞迴地將在原始物件裡找到的物件
     的'副本'插入其中。

深層複製操作通常存在兩個問題，而淺層複製操作並不存在這些問題：

   * 遞迴物件（直接或間接包含對自身參照的複合物件）可能會導致遞迴迴圈。

   * 由於深層複製會複製所有內容，因此可能會有過多複製（例如應該在副本之
     間共享的資料）。

*note deepcopy(): b12. 函式用以下方式避免了這些問題：

   * 保留在當前複製過程中已複製的物件的 ‘memo’ 字典；以及

   * 允許使用者定義的類別複寫 (override) 複製操作或複製的元件集合。

該模組不複製模組、方法、堆疊追蹤（stack trace）、堆疊框（stack frame）、
檔案、socket、視窗、陣列以及任何類似的型別。它透過不變更原始物件並將其回
傳來（淺層或深層地）"複製"函式和類別；這與 *note pickle: 95. 模組處理這
類問題的方式是相似的。

字典的淺層複製可以使用 *note dict.copy(): b77.，而 list 的淺層複製可以透
過賦值整個 list 的切片 (slice) 完成，例如，‘copied_list =
original_list[:]’。

類別可以使用與操作 pickle 相同的介面來控制複製操作，關於這些方法的描述資
訊請參考 *note pickle: 95. 模組。實際上，*note copy: 1e. 模組使用的正是
從 *note copyreg: 1f. 模組中註冊的 pickle 函式。

In order for a class to define its own copy implementation, it can
define special methods *note __copy__(): 2464. and *note __deepcopy__():
2465.

 -- 方法: object.__copy__ (self)

     Called to implement the shallow copy operation; no additional
     arguments are passed.

 -- 方法: object.__deepcopy__ (self, memo)

     Called to implement the deep copy operation; it is passed one
     argument, the 'memo' dictionary.  If the ‘__deepcopy__’
     implementation needs to make a deep copy of a component, it should
     call the *note deepcopy(): b12. function with the component as
     first argument and the 'memo' dictionary as second argument.  The
     'memo' dictionary should be treated as an opaque object.

Function ‘copy.replace()’ is more limited than *note copy(): 4d8. and
*note deepcopy(): b12, and only supports named tuples created by *note
namedtuple(): 1ae, *note dataclasses: 27, and other classes which define
method *note __replace__(): 137.

 -- 方法: object.__replace__ (self, /, **changes)

     This method should create a new object of the same type, replacing
     fields with values from 'changes'.

也參考
......

*note pickle: 95. 模組

     支援物件之狀態檢索 (state retrieval) 和恢復 (restoration) 相關特殊
     方法的討論。

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/copy.py


File: python.info,  Node: pprint --- 資料美化列印器,  Next: reprlib --- repr 的替代實作,  Prev: copy --- 淺層 shallow 和深層 deep 複製操作,  Up: 資料型別

5.8.12 ‘pprint’ -- 資料美化列印器
---------------------------------

'原始碼：'Lib/pprint.py(1)

__________________________________________________________________

The *note pprint: 9c. module provides a capability to "pretty-print"
arbitrary Python data structures in a form which can be used as input to
the interpreter.  If the formatted structures include objects which are
not fundamental Python types, the representation may not be loadable.
This may be the case if objects such as files, sockets or classes are
included, as well as many other objects which are not representable as
Python literals.

The formatted representation keeps objects on a single line if it can,
and breaks them onto multiple lines if they don't fit within the allowed
width, adjustable by the 'width' parameter defaulting to 80 characters.

Dictionaries are sorted by key before the display is computed.

在 3.9 版的變更: Added support for pretty-printing *note
types.SimpleNamespace: 1b5.

在 3.10 版的變更: Added support for pretty-printing *note
dataclasses.dataclass: 1af.

* Menu:

* 函式: 函式<3>.
* PrettyPrinter 物件::
* 範例: 範例<5>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/pprint.py


File: python.info,  Node: 函式<3>,  Next: PrettyPrinter 物件,  Up: pprint --- 資料美化列印器

5.8.12.1 函式
.............

 -- 函式: pprint.pp (object, stream=None, indent=1, width=80,
          depth=None, *, compact=False, sort_dicts=False,
          underscore_numbers=False)

     Prints the formatted representation of 'object', followed by a
     newline.  This function may be used in the interactive interpreter
     instead of the *note print(): f18. function for inspecting values.
     Tip: you can reassign ‘print = pprint.pp’ for use within a scope.


     參數:

        * ‘object’ - The object to be printed.

        * ‘stream’ (*note file-like object: 246a. | None) - A file-like
          object to which the output will be written by calling its
          ‘write()’ method.  If ‘None’ (the default), *note sys.stdout:
          a79. is used.

        * ‘indent’ (*note int: 23c.) - The amount of indentation added
          for each nesting level.

        * ‘width’ (*note int: 23c.) - The desired maximum number of
          characters per line in the output.  If a structure cannot be
          formatted within the width constraint, a best effort will be
          made.

        * ‘depth’ (*note int: 23c.‘ | ’‘None’) - The number of nesting
          levels which may be printed.  If the data structure being
          printed is too deep, the next contained level is replaced by
          ‘...’.  If ‘None’ (the default), there is no constraint on the
          depth of the objects being formatted.

        * ‘compact’ (*note bool: 40e.) - Control the way long *note
          sequences: 499. are formatted.  If ‘False’ (the default), each
          item of a sequence will be formatted on a separate line,
          otherwise as many items as will fit within the 'width' will be
          formatted on each output line.

        * ‘sort_dicts’ (*note bool: 40e.) - If ‘True’, dictionaries will
          be formatted with their keys sorted, otherwise they will be
          displayed in insertion order (the default).

        * ‘underscore_numbers’ (*note bool: 40e.) - If ‘True’, integers
          will be formatted with the ‘_’ character for a thousands
          separator, otherwise underscores are not displayed (the
          default).

          >>> import pprint
          >>> stuff = ['spam', 'eggs', 'lumberjack', 'knights', 'ni']
          >>> stuff.insert(0, stuff)
          >>> pprint.pp(stuff)
          [<Recursion on list with id=...>,
           'spam',
           'eggs',
           'lumberjack',
           'knights',
           'ni']

     在 3.8 版被加入.

 -- 函式: pprint.pprint (object, stream=None, indent=1, width=80,
          depth=None, *, compact=False, sort_dicts=True,
          underscore_numbers=False)

     Alias for *note pp(): 9c7. with 'sort_dicts' set to ‘True’ by
     default, which would automatically sort the dictionaries' keys, you
     might want to use *note pp(): 9c7. instead where it is ‘False’ by
     default.

 -- 函式: pprint.pformat (object, indent=1, width=80, depth=None, *,
          compact=False, sort_dicts=True, underscore_numbers=False)

     Return the formatted representation of 'object' as a string.
     'indent', 'width', 'depth', 'compact', 'sort_dicts' and
     'underscore_numbers' are passed to the *note PrettyPrinter: f22.
     constructor as formatting parameters and their meanings are as
     described in the documentation above.

 -- 函式: pprint.isreadable (object)

     Determine if the formatted representation of 'object' is
     "readable", or can be used to reconstruct the value using *note
     eval(): 163.  This always returns ‘False’ for recursive objects.

          >>> pprint.isreadable(stuff)
          False

 -- 函式: pprint.isrecursive (object)

     Determine if 'object' requires a recursive representation.  This
     function is subject to the same limitations as noted in *note
     saferepr(): 246d. below and may raise an *note RecursionError: d12.
     if it fails to detect a recursive object.

 -- 函式: pprint.saferepr (object)

     Return a string representation of 'object', protected against
     recursion in some common data structures, namely instances of *note
     dict: 23b, *note list: 5b6. and *note tuple: 322. or subclasses
     whose ‘__repr__’ has not been overridden.  If the representation of
     object exposes a recursive entry, the recursive reference will be
     represented as ‘<Recursion on typename with id=number>’.  The
     representation is not otherwise formatted.

          >>> pprint.saferepr(stuff)
          "[<Recursion on list with id=...>, 'spam', 'eggs', 'lumberjack', 'knights', 'ni']"


File: python.info,  Node: PrettyPrinter 物件,  Next: 範例<5>,  Prev: 函式<3>,  Up: pprint --- 資料美化列印器

5.8.12.2 PrettyPrinter 物件
...........................

 -- 類別: pprint.PrettyPrinter (indent=1, width=80, depth=None,
          stream=None, *, compact=False, sort_dicts=True,
          underscore_numbers=False)

     Construct a *note PrettyPrinter: f22. instance.

     Arguments have the same meaning as for *note pp(): 9c7.  Note that
     they are in a different order, and that 'sort_dicts' defaults to
     ‘True’.

          >>> import pprint
          >>> stuff = ['spam', 'eggs', 'lumberjack', 'knights', 'ni']
          >>> stuff.insert(0, stuff[:])
          >>> pp = pprint.PrettyPrinter(indent=4)
          >>> pp.pprint(stuff)
          [   ['spam', 'eggs', 'lumberjack', 'knights', 'ni'],
              'spam',
              'eggs',
              'lumberjack',
              'knights',
              'ni']
          >>> pp = pprint.PrettyPrinter(width=41, compact=True)
          >>> pp.pprint(stuff)
          [['spam', 'eggs', 'lumberjack',
            'knights', 'ni'],
           'spam', 'eggs', 'lumberjack', 'knights',
           'ni']
          >>> tup = ('spam', ('eggs', ('lumberjack', ('knights', ('ni', ('dead',
          ... ('parrot', ('fresh fruit',))))))))
          >>> pp = pprint.PrettyPrinter(depth=6)
          >>> pp.pprint(tup)
          ('spam', ('eggs', ('lumberjack', ('knights', ('ni', ('dead', (...)))))))

     在 3.4 版的變更: 新增 'compact' 參數。

     在 3.8 版的變更: 新增 'sort_dicts' 參數。

     在 3.10 版的變更: 新增 'underscore_numbers' 參數。

     在 3.11 版的變更: No longer attempts to write to ‘sys.stdout’ if it
     is ‘None’.

*note PrettyPrinter: f22. instances have the following methods:

 -- 方法: PrettyPrinter.pformat (object)

     Return the formatted representation of 'object'.  This takes into
     account the options passed to the *note PrettyPrinter: f22.
     constructor.

 -- 方法: PrettyPrinter.pprint (object)

     Print the formatted representation of 'object' on the configured
     stream, followed by a newline.

The following methods provide the implementations for the corresponding
functions of the same names.  Using these methods on an instance is
slightly more efficient since new *note PrettyPrinter: f22. objects
don't need to be created.

 -- 方法: PrettyPrinter.isreadable (object)

     Determine if the formatted representation of the object is
     "readable," or can be used to reconstruct the value using *note
     eval(): 163.  Note that this returns ‘False’ for recursive objects.
     If the 'depth' parameter of the *note PrettyPrinter: f22. is set
     and the object is deeper than allowed, this returns ‘False’.

 -- 方法: PrettyPrinter.isrecursive (object)

     Determine if the object requires a recursive representation.

This method is provided as a hook to allow subclasses to modify the way
objects are converted to strings.  The default implementation uses the
internals of the *note saferepr(): 246d. implementation.

 -- 方法: PrettyPrinter.format (object, context, maxlevels, level)

     Returns three values: the formatted version of 'object' as a
     string, a flag indicating whether the result is readable, and a
     flag indicating whether recursion was detected.  The first argument
     is the object to be presented.  The second is a dictionary which
     contains the *note id(): 1390. of objects that are part of the
     current presentation context (direct and indirect containers for
     'object' that are affecting the presentation) as the keys; if an
     object needs to be presented which is already represented in
     'context', the third return value should be ‘True’.  Recursive
     calls to the *note format(): 1821. method should add additional
     entries for containers to this dictionary.  The third argument,
     'maxlevels', gives the requested limit to recursion; this will be
     ‘0’ if there is no requested limit.  This argument should be passed
     unmodified to recursive calls.  The fourth argument, 'level', gives
     the current level; recursive calls should be passed a value less
     than that of the current call.


File: python.info,  Node: 範例<5>,  Prev: PrettyPrinter 物件,  Up: pprint --- 資料美化列印器

5.8.12.3 範例
.............

To demonstrate several uses of the *note pp(): 9c7. function and its
parameters, let's fetch information about a project from PyPI(1):

     >>> import json
     >>> import pprint
     >>> from urllib.request import urlopen
     >>> with urlopen('https://pypi.org/pypi/sampleproject/json') as resp:
     ...     project_info = json.load(resp)['info']

In its basic form, *note pp(): 9c7. shows the whole object:

     >>> pprint.pp(project_info)
     {'author': 'The Python Packaging Authority',
      'author_email': 'pypa-dev@googlegroups.com',
      'bugtrack_url': None,
      'classifiers': ['Development Status :: 3 - Alpha',
                      'Intended Audience :: Developers',
                      'License :: OSI Approved :: MIT License',
                      'Programming Language :: Python :: 2',
                      'Programming Language :: Python :: 2.6',
                      'Programming Language :: Python :: 2.7',
                      'Programming Language :: Python :: 3',
                      'Programming Language :: Python :: 3.2',
                      'Programming Language :: Python :: 3.3',
                      'Programming Language :: Python :: 3.4',
                      'Topic :: Software Development :: Build Tools'],
      'description': 'A sample Python project\n'
                     '=======================\n'
                     '\n'
                     'This is the description file for the project.\n'
                     '\n'
                     'The file should use UTF-8 encoding and be written using '
                     'ReStructured Text. It\n'
                     'will be used to generate the project webpage on PyPI, and '
                     'should be written for\n'
                     'that purpose.\n'
                     '\n'
                     'Typical contents for this file would include an overview of '
                     'the project, basic\n'
                     'usage examples, etc. Generally, including the project '
                     'changelog in here is not\n'
                     'a good idea, although a simple "What\'s New" section for the '
                     'most recent version\n'
                     'may be appropriate.',
      'description_content_type': None,
      'docs_url': None,
      'download_url': 'UNKNOWN',
      'downloads': {'last_day': -1, 'last_month': -1, 'last_week': -1},
      'home_page': 'https://github.com/pypa/sampleproject',
      'keywords': 'sample setuptools development',
      'license': 'MIT',
      'maintainer': None,
      'maintainer_email': None,
      'name': 'sampleproject',
      'package_url': 'https://pypi.org/project/sampleproject/',
      'platform': 'UNKNOWN',
      'project_url': 'https://pypi.org/project/sampleproject/',
      'project_urls': {'Download': 'UNKNOWN',
                       'Homepage': 'https://github.com/pypa/sampleproject'},
      'release_url': 'https://pypi.org/project/sampleproject/1.2.0/',
      'requires_dist': None,
      'requires_python': None,
      'summary': 'A sample Python project',
      'version': '1.2.0'}

The result can be limited to a certain 'depth' (ellipsis is used for
deeper contents):

     >>> pprint.pp(project_info, depth=1)
     {'author': 'The Python Packaging Authority',
      'author_email': 'pypa-dev@googlegroups.com',
      'bugtrack_url': None,
      'classifiers': [...],
      'description': 'A sample Python project\n'
                     '=======================\n'
                     '\n'
                     'This is the description file for the project.\n'
                     '\n'
                     'The file should use UTF-8 encoding and be written using '
                     'ReStructured Text. It\n'
                     'will be used to generate the project webpage on PyPI, and '
                     'should be written for\n'
                     'that purpose.\n'
                     '\n'
                     'Typical contents for this file would include an overview of '
                     'the project, basic\n'
                     'usage examples, etc. Generally, including the project '
                     'changelog in here is not\n'
                     'a good idea, although a simple "What\'s New" section for the '
                     'most recent version\n'
                     'may be appropriate.',
      'description_content_type': None,
      'docs_url': None,
      'download_url': 'UNKNOWN',
      'downloads': {...},
      'home_page': 'https://github.com/pypa/sampleproject',
      'keywords': 'sample setuptools development',
      'license': 'MIT',
      'maintainer': None,
      'maintainer_email': None,
      'name': 'sampleproject',
      'package_url': 'https://pypi.org/project/sampleproject/',
      'platform': 'UNKNOWN',
      'project_url': 'https://pypi.org/project/sampleproject/',
      'project_urls': {...},
      'release_url': 'https://pypi.org/project/sampleproject/1.2.0/',
      'requires_dist': None,
      'requires_python': None,
      'summary': 'A sample Python project',
      'version': '1.2.0'}

Additionally, maximum character 'width' can be suggested.  If a long
object cannot be split, the specified width will be exceeded:

     >>> pprint.pp(project_info, depth=1, width=60)
     {'author': 'The Python Packaging Authority',
      'author_email': 'pypa-dev@googlegroups.com',
      'bugtrack_url': None,
      'classifiers': [...],
      'description': 'A sample Python project\n'
                     '=======================\n'
                     '\n'
                     'This is the description file for the '
                     'project.\n'
                     '\n'
                     'The file should use UTF-8 encoding and be '
                     'written using ReStructured Text. It\n'
                     'will be used to generate the project '
                     'webpage on PyPI, and should be written '
                     'for\n'
                     'that purpose.\n'
                     '\n'
                     'Typical contents for this file would '
                     'include an overview of the project, '
                     'basic\n'
                     'usage examples, etc. Generally, including '
                     'the project changelog in here is not\n'
                     'a good idea, although a simple "What\'s '
                     'New" section for the most recent version\n'
                     'may be appropriate.',
      'description_content_type': None,
      'docs_url': None,
      'download_url': 'UNKNOWN',
      'downloads': {...},
      'home_page': 'https://github.com/pypa/sampleproject',
      'keywords': 'sample setuptools development',
      'license': 'MIT',
      'maintainer': None,
      'maintainer_email': None,
      'name': 'sampleproject',
      'package_url': 'https://pypi.org/project/sampleproject/',
      'platform': 'UNKNOWN',
      'project_url': 'https://pypi.org/project/sampleproject/',
      'project_urls': {...},
      'release_url': 'https://pypi.org/project/sampleproject/1.2.0/',
      'requires_dist': None,
      'requires_python': None,
      'summary': 'A sample Python project',
      'version': '1.2.0'}

   ---------- Footnotes ----------

   (1) https://pypi.org


File: python.info,  Node: reprlib --- repr 的替代實作,  Next: enum --- 對列舉的支援,  Prev: pprint --- 資料美化列印器,  Up: 資料型別

5.8.13 ‘reprlib’ -- ‘repr()’ 的替代實作
---------------------------------------

'原始碼：'Lib/reprlib.py(1)

__________________________________________________________________

The ‘reprlib’ module provides a means for producing object
representations with limits on the size of the resulting strings.  This
is used in the Python debugger and may be useful in other contexts as
well.

This module provides a class, an instance, and a function:

 -- 類別: reprlib.Repr (*, maxlevel=6, maxtuple=6, maxlist=6,
          maxarray=5, maxdict=4, maxset=6, maxfrozenset=6, maxdeque=6,
          maxstring=30, maxlong=40, maxother=30, fillvalue='...',
          indent=None)

     Class which provides formatting services useful in implementing
     functions similar to the built-in *note repr(): 7a1.; size limits
     for different object types are added to avoid the generation of
     representations which are excessively long.

     The keyword arguments of the constructor can be used as a shortcut
     to set the attributes of the *note Repr: 2478. instance.  Which
     means that the following initialization:

          aRepr = reprlib.Repr(maxlevel=3)

     等價於：

          aRepr = reprlib.Repr()
          aRepr.maxlevel = 3

     See section *note Repr Objects: 2479. for more information about
     *note Repr: 2478. attributes.

     在 3.12 版的變更: Allow attributes to be set via keyword arguments.

 -- 資料: reprlib.aRepr

     This is an instance of *note Repr: 2478. which is used to provide
     the *note repr(): 247b. function described below.  Changing the
     attributes of this object will affect the size limits used by *note
     repr(): 247b. and the Python debugger.

 -- 函式: reprlib.repr (obj)

     This is the *note repr(): 247c. method of ‘aRepr’.  It returns a
     string similar to that returned by the built-in function of the
     same name, but with limits on most sizes.

In addition to size-limiting tools, the module also provides a decorator
for detecting recursive calls to *note __repr__(): 5c2. and substituting
a placeholder string instead.

 -- 函式: @reprlib.recursive_repr (fillvalue='...')

     Decorator for *note __repr__(): 5c2. methods to detect recursive
     calls within the same thread.  If a recursive call is made, the
     'fillvalue' is returned, otherwise, the usual ‘__repr__()’ call is
     made.  For example:

          >>> from reprlib import recursive_repr
          >>> class MyList(list):
          ...     @recursive_repr()
          ...     def __repr__(self):
          ...         return '<' + '|'.join(map(repr, self)) + '>'
          ...
          >>> m = MyList('abc')
          >>> m.append(m)
          >>> m.append('x')
          >>> print(m)
          <'a'|'b'|'c'|...|'x'>

     在 3.2 版被加入.

* Menu:

* Repr 物件::
* Subclassing Repr Objects::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/reprlib.py


File: python.info,  Node: Repr 物件,  Next: Subclassing Repr Objects,  Up: reprlib --- repr 的替代實作

5.8.13.1 Repr 物件
..................

*note Repr: 2478. instances provide several attributes which can be used
to provide size limits for the representations of different object
types, and methods which format specific object types.

 -- 屬性: Repr.fillvalue

     This string is displayed for recursive references.  It defaults to
     ‘...’.

     在 3.11 版被加入.

 -- 屬性: Repr.maxlevel

     Depth limit on the creation of recursive representations.  The
     default is ‘6’.

 -- 屬性: Repr.maxdict
 -- 屬性: Repr.maxlist
 -- 屬性: Repr.maxtuple
 -- 屬性: Repr.maxset
 -- 屬性: Repr.maxfrozenset
 -- 屬性: Repr.maxdeque
 -- 屬性: Repr.maxarray

     Limits on the number of entries represented for the named object
     type.  The default is ‘4’ for *note maxdict: 2480, ‘5’ for *note
     maxarray: 2486, and ‘6’ for the others.

 -- 屬性: Repr.maxlong

     Maximum number of characters in the representation for an integer.
     Digits are dropped from the middle.  The default is ‘40’.

 -- 屬性: Repr.maxstring

     Limit on the number of characters in the representation of the
     string.  Note that the "normal" representation of the string is
     used as the character source: if escape sequences are needed in the
     representation, these may be mangled when the representation is
     shortened.  The default is ‘30’.

 -- 屬性: Repr.maxother

     This limit is used to control the size of object types for which no
     specific formatting method is available on the *note Repr: 2478.
     object.  It is applied in a similar manner as *note maxstring:
     2488.  The default is ‘20’.

 -- 屬性: Repr.indent

     If this attribute is set to ‘None’ (the default), the output is
     formatted with no line breaks or indentation, like the standard
     *note repr(): 7a1.  For example:

          >>> example = [
          ...     1, 'spam', {'a': 2, 'b': 'spam eggs', 'c': {3: 4.5, 6: []}}, 'ham']
          >>> import reprlib
          >>> aRepr = reprlib.Repr()
          >>> print(aRepr.repr(example))
          [1, 'spam', {'a': 2, 'b': 'spam eggs', 'c': {3: 4.5, 6: []}}, 'ham']

     If *note indent: 248a. is set to a string, each recursion level is
     placed on its own line, indented by that string:

          >>> aRepr.indent = '-->'
          >>> print(aRepr.repr(example))
          [
          -->1,
          -->'spam',
          -->{
          -->-->'a': 2,
          -->-->'b': 'spam eggs',
          -->-->'c': {
          -->-->-->3: 4.5,
          -->-->-->6: [],
          -->-->},
          -->},
          -->'ham',
          ]

     Setting *note indent: 248a. to a positive integer value behaves as
     if it was set to a string with that number of spaces:

          >>> aRepr.indent = 4
          >>> print(aRepr.repr(example))
          [
              1,
              'spam',
              {
                  'a': 2,
                  'b': 'spam eggs',
                  'c': {
                      3: 4.5,
                      6: [],
                  },
              },
              'ham',
          ]

     在 3.12 版被加入.

 -- 方法: Repr.repr (obj)

     The equivalent to the built-in *note repr(): 7a1. that uses the
     formatting imposed by the instance.

 -- 方法: Repr.repr1 (obj, level)

     Recursive implementation used by *note repr(): 247c.  This uses the
     type of 'obj' to determine which formatting method to call, passing
     it 'obj' and 'level'.  The type-specific methods should call *note
     repr1(): 248b. to perform recursive formatting, with ‘level - 1’
     for the value of 'level' in the recursive call.

 -- 方法: Repr.repr_TYPE (obj, level)

     Formatting methods for specific types are implemented as methods
     with a name based on the type name.  In the method name, 'TYPE' is
     replaced by ‘'_'.join(type(obj).__name__.split())’.  Dispatch to
     these methods is handled by *note repr1(): 248b.  Type-specific
     methods which need to recursively format a value should call
     ‘self.repr1(subobj, level - 1)’.


File: python.info,  Node: Subclassing Repr Objects,  Prev: Repr 物件,  Up: reprlib --- repr 的替代實作

5.8.13.2 Subclassing Repr Objects
.................................

The use of dynamic dispatching by *note Repr.repr1(): 248b. allows
subclasses of *note Repr: 2478. to add support for additional built-in
object types or to modify the handling of types already supported.  This
example shows how special support for file objects could be added:

     import reprlib
     import sys

     class MyRepr(reprlib.Repr):

         def repr_TextIOWrapper(self, obj, level):
             if obj.name in {'<stdin>', '<stdout>', '<stderr>'}:
                 return obj.name
             return repr(obj)

     aRepr = MyRepr()
     print(aRepr.repr(sys.stdin))         # 印出 '<stdin>'

     <stdin>


File: python.info,  Node: enum --- 對列舉的支援,  Next: graphlib —-- 使用類圖 graph-like 結構進行操作的功能,  Prev: reprlib --- repr 的替代實作,  Up: 資料型別

5.8.14 ‘enum’ -- 對列舉的支援
-----------------------------

在 3.4 版被加入.

'原始碼：'Lib/enum.py(1)

Important
.........

本頁包含 API 的參考資訊。關於教學資訊及更多進階主題的討論請參考

   * *note 基本教學: 2490.

   * *note 進階教學: 2491.

   * *note 列舉指南: 2492.

__________________________________________________________________

列舉：

   * 是一組綁定唯一值的代表名稱（成員）

   * 可以用疊代的方式以定義的順序回傳其正式 (canonical)（即非別名）成員

   * 使用 'call' 語法來透過值回傳成員

   * 使用 'index' 語法來透過名稱回傳成員

列舉透過 *note class: 126a. 語法或函式呼叫的語法來建立：

     >>> from enum import Enum

     >>> # class syntax
     >>> class Color(Enum):
     ...     RED = 1
     ...     GREEN = 2
     ...     BLUE = 3

     >>> # functional syntax
     >>> Color = Enum('Color', ['RED', 'GREEN', 'BLUE'])

雖然我們可以用 *note class: 126a. 語法來建立列舉，列舉並不是標準的
Python 類別。參考*note 列舉有何差異: 2493.以取得更多細節。

     備註: 命名方式

        - ‘Color’ 類別是一個'列舉'（或 'enum'）

        - ‘Color.RED’、‘Color.GREEN’ 等屬性是'列舉成員'（或'成員'），並
          且使用上可以看作常數。

        - 列舉成員有'名稱'和'值'（‘Color.RED’ 的名稱是 ‘RED’，
          ‘Color.BLUE’ 的值是 ‘3’ 諸如此類）

__________________________________________________________________

* Menu:

* 模組內容: 模組內容<2>.
* 資料型別: 資料型別<2>.
* 通用項目與裝飾器::
* 備註::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/enum.py


File: python.info,  Node: 模組內容<2>,  Next: 資料型別<2>,  Up: enum --- 對列舉的支援

5.8.14.1 模組內容
.................

     *note EnumType: 5bf.

          Enum 及其子類別的 ‘type’。

     *note Enum: 5d6.

          用來建立列舉常數的基礎類別。

     *note IntEnum: c86.

          用來建立列舉常數的基礎類別，同時也是 *note int: 23c. 的子類別
          。（*note 備註: 2495.）

     *note StrEnum: 5c0.

          用來建立列舉常數的基礎類別，同時也是 *note str: 3f2. 的子類別
          。（*note 備註: 2495.）

     *note Flag: 5c9.

          用來建立列舉常數的基礎類別，可以使用位元操作來結合成員且其結果
          不失去 *note Flag: 5c9. 的成員資格。

     *note IntFlag: 21d7.

          用來建立列舉常數的基礎類別，可以使用位元操作來結合成員且其結果
          不失去 *note IntFlag: 21d7. 的成員資格。*note IntFlag: 21d7. 的
          成員也是 *note int: 23c. 的子類別。（*note 備註: 2495.）

     *note ReprEnum: 5c1.

          由 *note IntEnum: c86.、*note StrEnum: 5c0. 及 *note IntFlag:
          21d7. 所使用來保留這些混合類型的 *note str(): 3f2.。

     *note EnumCheck: 5cc.

          一個有 ‘CONTINUOUS’、‘NAMED_FLAGS’ 及 ‘UNIQUE’ 這些值的列舉，
          和 *note verify(): 5cb. 一起使用來確保給定的列舉符合多種限制。

     *note FlagBoundary: 5ca.

          一個有 ‘STRICT’、‘CONFORM’、‘EJECT’ 及 ‘KEEP’ 這些值的列舉，允
          許列舉對如何處理非法值做更細微的控制。

     *note auto: c43.

          列舉成員的實例會被取代成合適的值。*note StrEnum: 5c0. 預設是小
          寫版本的成員名稱，其它列舉則預設是 1 且往後遞增。

     *note property(): 5cf.

          允許 *note Enum: 5d6. 成員擁有屬性且不會與成員名稱有衝突。
          ‘value’ 及 ‘name’ 屬性是用這個方式來實作。

     *note unique(): 2496.

          Enum 類別的裝飾器，用來確保任何值只有綁定到一個名稱上。

     *note verify(): 5cb.

          Enum 類別的裝飾器，用來檢查列舉上使用者所選的限制。

     *note member(): 5cd.

          讓 ‘obj’ 變成成員。可以當作裝飾器使用。

     *note nonmember(): 5ce.

          不讓 ‘obj’ 變成成員。可以當作裝飾器使用。

     *note global_enum(): 5d1.

          修改列舉上的 *note str(): 3f2. 及 *note repr(): 7a1. ，讓成員
          顯示為屬於模組而不是類別，並將該列舉成員匯出到全域命名空間。

     *note show_flag_values(): 2497.

          回傳旗標 (flag) 裡包含的所有 2 的次方的整數串列。

在 3.6 版被加入: ‘Flag’, ‘IntFlag’, ‘auto’

在 3.11 版被加入: ‘StrEnum’, ‘EnumCheck’, ‘ReprEnum’, ‘FlagBoundary’,
‘property’, ‘member’, ‘nonmember’, ‘global_enum’, ‘show_flag_values’

__________________________________________________________________


File: python.info,  Node: 資料型別<2>,  Next: 通用項目與裝飾器,  Prev: 模組內容<2>,  Up: enum --- 對列舉的支援

5.8.14.2 資料型別
.................

 -- 類別: enum.EnumType

     'EnumType' 是'列舉'的 *note metaclass: 1e5d.。'EnumType' 可以有子類
     別 - 細節請參考 *note 建立 EnumType 的子類別: 2499.。

     ‘EnumType’ is responsible for setting the correct ‘__repr__()’,
     ‘__str__()’, ‘__format__()’, and ‘__reduce__()’ methods on the
     final 'enum', as well as creating the enum members, properly
     handling duplicates, providing iteration over the enum class, etc.

      -- 方法: __call__ (cls, value, names=None, *, module=None,
               qualname=None, type=None, start=1, boundary=None)

          這個方法可以用兩種不同的方式呼叫：

             * 查詢已存在的成員：


                    cls: 所呼叫的列舉類別。


                    value: 要查詢的值。

             * 使用 ‘cls’ 列舉來建立新列舉（只有在現有列舉沒有任何成員時
               ）


                    cls: 所呼叫的列舉類別。


                    value: 要建立的新列舉的名稱。


                    names: 新列舉的成員的名稱/值。


                    module: 新列舉要建立在哪個模組名稱下。


                    qualname: 這個列舉在模組裡實際上的位置。


                    type: 新列舉的混合類型。


                    start: 列舉的第一個整數值（由 *note auto: c43. 所使
                    用）


                    boundary: 在位元操作時怎麼處理範圍外的值（只有 *note
                    Flag: 5c9. 會用到）

      -- 方法: __contains__ (cls, member)

          如果 member 屬於 ‘cls’ 則回傳 ‘True’：

               >>> some_var = Color.RED
               >>> some_var in Color
               True
               >>> Color.RED.value in Color
               True

     在 3.12 版的變更: 在 Python 3.12 之前，如果用非列舉成員做屬於檢查
     (containment check) 會引發 ‘TypeError’。

      -- 方法: __dir__ (cls)

          回傳 ‘['__class__', '__doc__', '__members__', '__module__']’ 及
          'cls' 的成員名稱：

               >>> dir(Color)
               ['BLUE', 'GREEN', 'RED', '__class__', '__contains__', '__doc__', '__getitem__', '__init_subclass__', '__iter__', '__len__', '__members__', '__module__', '__name__', '__qualname__']

      -- 方法: __getitem__ (cls, name)

          回傳 'cls' 中符合 'name' 的列舉成員，或引發 *note KeyError:
          2fb.：

               >>> Color['BLUE']
               <Color.BLUE: 3>

      -- 方法: __iter__ (cls)

          以定義的順序回傳在 'cls' 中的每個成員：

               >>> list(Color)
               [<Color.RED: 1>, <Color.GREEN: 2>, <Color.BLUE: 3>]

      -- 方法: __len__ (cls)

          回傳 'cls' 的成員數量：

               >>> len(Color)
               3

      -- 屬性: __members__

          回傳每個列舉名稱到其成員的對映，包括別名

      -- 方法: __reversed__ (cls)

          以跟定義相反的順序回傳 'cls' 的每個成員：

               >>> list(reversed(Color))
               [<Color.BLUE: 3>, <Color.GREEN: 2>, <Color.RED: 1>]

      -- 方法: _add_alias_ ()

          Adds a new name as an alias to an existing member.  Raises a
          *note NameError: 3e5. if the name is already assigned to a
          different member.

      -- 方法: _add_value_alias_ ()

          Adds a new value as an alias to an existing member.  Raises a
          *note ValueError: 1e7. if the value is already linked with a
          different member.

     在 3.11 版被加入: Before 3.11 ‘EnumType’ was called ‘EnumMeta’,
     which is still available as an alias.

 -- 類別: enum.Enum

     'Enum' 是所有 'enum' 列舉的基礎類別。

      -- 屬性: name

          用來定義 ‘Enum’ 成員的名稱：

               >>> Color.BLUE.name
               'BLUE'

      -- 屬性: value

          ‘Enum’ 成員給定的值：

               >>> Color.RED.value
               1

          成員的值，可以在 *note __new__(): 24a6. 設定。

               備註: 列舉成員的值

               成員的值可以是任何值：*note int: 23c.、*note str: 3f2. 等
               等。如果實際使用什麼值並不重要，你可以使用 *note auto:
               c43. 實例，它會為你選擇合適的值。更多細節請參考 *note
               auto: c43.。

               While mutable/unhashable values, such as *note dict: 23b,
               *note list: 5b6. or a mutable *note dataclass: 1af, can
               be used, they will have a quadratic performance impact
               during creation relative to the total number of
               mutable/unhashable values in the enum.

      -- 屬性: _name_

          成員名稱。

      -- 屬性: _value_

          成員的值，可以在 *note __new__(): 24a6. 設定。

      -- 屬性: _order_

          已不再使用，只為了向後相容而保留（類別屬性，在類別建立時移除）

      -- 屬性: _ignore_

          ‘_ignore_’ 只有在建立的時候用到，在列舉建立完成後會被移除。

          ‘_ignore_’ 是一個不會變成成員的名稱串列，在列舉建立完成後其名
          稱會被移除。範例請參考 *note TimePeriod: 24ab.。

      -- 方法: __dir__ (self)

          回傳 ‘['__class__', '__doc__', '__module__', 'name', 'value']’
          及任何 'self.__class__' 上定義的公開方法：

               >>> from datetime import date
               >>> class Weekday(Enum):
               ...     MONDAY = 1
               ...     TUESDAY = 2
               ...     WEDNESDAY = 3
               ...     THURSDAY = 4
               ...     FRIDAY = 5
               ...     SATURDAY = 6
               ...     SUNDAY = 7
               ...     @classmethod
               ...     def today(cls):
               ...         print('today is %s' % cls(date.today().isoweekday()).name)
               ...
               >>> dir(Weekday.SATURDAY)
               ['__class__', '__doc__', '__eq__', '__hash__', '__module__', 'name', 'today', 'value']

      -- 方法: _generate_next_value_ (name, start, count, last_values)


               name: 定義的成員名稱（例如 'RED'）。


               start: 列舉的開始值，預設為 1。


               count: 已定義的成員數量，不包含目前這一個。


               last_values: 一個之前值的串列。

          一個 'staticmethod'，用來決定 *note auto: c43. 下一個要回傳的
          值的：

               >>> from enum import auto
               >>> class PowersOfThree(Enum):
               ...     @staticmethod
               ...     def _generate_next_value_(name, start, count, last_values):
               ...         return 3 ** (count + 1)
               ...     FIRST = auto()
               ...     SECOND = auto()
               ...
               >>> PowersOfThree.SECOND.value
               9

      -- 方法: __init__ (self, *args, **kwds)

          預設情況下，不執行任何操作。如果在成員賦值中給出多個值，這些值
          將成為與 ‘__init__’ 分別的引數；例如

               >>> from enum import Enum
               >>> class Weekday(Enum):
               ...     MONDAY = 1, 'Mon'

          ‘Weekday.__init__()’ 將被稱為 ‘Weekday.__init__(self, 1,
          'Mon')’

      -- 方法: __init_subclass__ (cls, **kwds)

          一個 'classmethod'，用來進一步設定後續的子類別，預設不做任何事
          。

      -- 方法: _missing_ (cls, value)

          一個 'classmethod'，用來查詢在 'cls' 裡找不到的值。預設不做任
          何事，但可以被覆寫以實作客製化的搜尋行為：

               >>> from enum import StrEnum
               >>> class Build(StrEnum):
               ...     DEBUG = auto()
               ...     OPTIMIZED = auto()
               ...     @classmethod
               ...     def _missing_(cls, value):
               ...         value = value.lower()
               ...         for member in cls:
               ...             if member.value == value:
               ...                 return member
               ...         return None
               ...
               >>> Build.DEBUG.value
               'debug'
               >>> Build('deBUG')
               <Build.DEBUG: 'debug'>

      -- 方法: __new__ (cls, *args, **kwds)

          預設情況下不存在。如果有指定，無論是在列舉類別定義中還是在
          mixin 類別中（例如 ‘int’），都將傳遞成員賦值中給出的所有值；例
          如

               >>> from enum import Enum
               >>> class MyIntEnum(int, Enum):
               ...     TWENTYSIX = '1a', 16

          results in the call ‘int('1a', 16)’ and a value of ‘26’ for
          the member.

               備註: 當寫自訂的 ‘__new__’ 時，不要使用
               ‘super().__new__’，而是要呼叫適當的 ‘__new__’。

      -- 方法: __repr__ (self)

          回傳呼叫 'repr()' 時使用的字串。預設回傳 'Enum' 名稱、成員名稱
          及值，但可以被覆寫：

               >>> class OtherStyle(Enum):
               ...     ALTERNATE = auto()
               ...     OTHER = auto()
               ...     SOMETHING_ELSE = auto()
               ...     def __repr__(self):
               ...         cls_name = self.__class__.__name__
               ...         return f'{cls_name}.{self.name}'
               ...
               >>> OtherStyle.ALTERNATE, str(OtherStyle.ALTERNATE), f"{OtherStyle.ALTERNATE}"
               (OtherStyle.ALTERNATE, 'OtherStyle.ALTERNATE', 'OtherStyle.ALTERNATE')

      -- 方法: __str__ (self)

          回傳呼叫 'str()' 時使用的字串。預設回傳 'Enum' 名稱及成員名稱
          ，但可以被覆寫：

               >>> class OtherStyle(Enum):
               ...     ALTERNATE = auto()
               ...     OTHER = auto()
               ...     SOMETHING_ELSE = auto()
               ...     def __str__(self):
               ...         return f'{self.name}'
               ...
               >>> OtherStyle.ALTERNATE, str(OtherStyle.ALTERNATE), f"{OtherStyle.ALTERNATE}"
               (<OtherStyle.ALTERNATE: 1>, 'ALTERNATE', 'ALTERNATE')

      -- 方法: __format__ (self)

          回傳呼叫 'format()' 及 'f-string' 時使用的字串。預設回傳 *note
          __str__(): 5c8. 的回傳值，但可以被覆寫：

               >>> class OtherStyle(Enum):
               ...     ALTERNATE = auto()
               ...     OTHER = auto()
               ...     SOMETHING_ELSE = auto()
               ...     def __format__(self, spec):
               ...         return f'{self.name}'
               ...
               >>> OtherStyle.ALTERNATE, str(OtherStyle.ALTERNATE), f"{OtherStyle.ALTERNATE}"
               (<OtherStyle.ALTERNATE: 1>, 'OtherStyle.ALTERNATE', 'ALTERNATE')

          備註: *note Enum: 5d6. 使用 *note auto: c43. 會產生從 ‘1’ 開始
          遞增的整數。

     在 3.12 版的變更: 新增 *note Dataclass support: 1687.

 -- 類別: enum.IntEnum

     'IntEnum' is the same as *note Enum: 5d6, but its members are also
     integers and can be used anywhere that an integer can be used.  If
     any integer operation is performed with an 'IntEnum' member, the
     resulting value loses its enumeration status.

          >>> from enum import IntEnum
          >>> class Number(IntEnum):
          ...     ONE = 1
          ...     TWO = 2
          ...     THREE = 3
          ...
          >>> Number.THREE
          <Number.THREE: 3>
          >>> Number.ONE + Number.TWO
          3
          >>> Number.THREE + 5
          8
          >>> Number.THREE == 3
          True

          備註: *note IntEnum: c86. 使用 *note auto: c43. 會產生從 ‘1’ 開
          始遞增的整數。

     在 3.11 版的變更: 為了更好地支援'現存常數取代 (replacement of
     existing constants)' 的使用情境，*note __str__(): 5c4. 現在會是
     ‘int.__str__()’。為了同樣的理由，*note __format__(): 5c5. 已經是
     ‘int.__format__()’。

 -- 類別: enum.StrEnum

     ‘StrEnum’ is the same as *note Enum: 5d6, but its members are also
     strings and can be used in most of the same places that a string
     can be used.  The result of any string operation performed on or
     with a 'StrEnum' member is not part of the enumeration.

          備註: stdlib 裡有些地方會檢查只能是 *note str: 3f2. 而不是
          *note str: 3f2. 的子類別（也就是 ‘type(unknown) == str’ 而不是
          ‘isinstance(unknown, str)’），在這些地方你需要使用
          ‘str(StrEnum.member)’。

          備註: *note StrEnum: 5c0. 使用 *note auto: c43. 會產生小寫的成
          員名稱當作值。

          備註: 為了更好地支援'現存常數取代 (replacement of existing
          constants)' 的使用情境，*note __str__(): 5c4. 現在會是
          ‘str.__str__()’。為了同樣的理由，*note __format__(): 5c5. 也會
          是 ‘str.__format__()’。

     在 3.11 版被加入.

 -- 類別: enum.Flag

     ‘Flag’ 與 *note Enum: 5d6. 相同，但其成員支援位元運算子 ‘&’
     ('AND')、‘|’ ('OR')、‘^’ ('XOR') 和 ‘~’ ('INVERT')；這些操作的結果
     是列舉的成員（的別名）。

      -- 方法: __contains__ (self, value)

          如果 value 在 self 裡則回傳 'True'：

               >>> from enum import Flag, auto
               >>> class Color(Flag):
               ...     RED = auto()
               ...     GREEN = auto()
               ...     BLUE = auto()
               ...
               >>> purple = Color.RED | Color.BLUE
               >>> white = Color.RED | Color.GREEN | Color.BLUE
               >>> Color.GREEN in purple
               False
               >>> Color.GREEN in white
               True
               >>> purple in white
               True
               >>> white in purple
               False

      -- 方法: __iter__(self):

          回傳所有包含的非別名成員：

               >>> list(Color.RED)
               [<Color.RED: 1>]
               >>> list(purple)
               [<Color.RED: 1>, <Color.BLUE: 4>]

          在 3.11 版被加入.

      -- 方法: __len__(self):

          回傳旗標裡的成員數量：

               >>> len(Color.GREEN)
               1
               >>> len(white)
               3

          在 3.11 版被加入.

      -- 方法: __bool__(self):

          如果成員在旗標裡則回傳 'True'，否則回傳 'False'：

               >>> bool(Color.GREEN)
               True
               >>> bool(white)
               True
               >>> black = Color(0)
               >>> bool(black)
               False

      -- 方法: __or__ (self, other)

          回傳和 other 做 OR 過後的二進位旗標：

               >>> Color.RED | Color.GREEN
               <Color.RED|GREEN: 3>

      -- 方法: __and__ (self, other)

          回傳和 other 做 AND 過後的二進位旗標：

               >>> purple & white
               <Color.RED|BLUE: 5>
               >>> purple & Color.GREEN
               <Color: 0>

      -- 方法: __xor__ (self, other)

          回傳和 other 做 XOR 過後的二進位旗標：

               >>> purple ^ white
               <Color.GREEN: 2>
               >>> purple ^ Color.GREEN
               <Color.RED|GREEN|BLUE: 7>

      -- 方法: __invert__(self):

          Returns all the flags in 'type(self)' that are not in 'self':

               >>> ~white
               <Color: 0>
               >>> ~purple
               <Color.GREEN: 2>
               >>> ~Color.RED
               <Color.GREEN|BLUE: 6>

      -- 方法: _numeric_repr_ ()

          用來格式化任何剩下未命名數值的函式。預設是值的 repr，常見選擇
          是 *note hex(): 1262. 和 *note oct(): 1261.。

          備註: *note Flag: 5c9. 使用 *note auto: c43. 會產生從 ‘1’ 開始
          2 的次方的整數。

     在 3.11 版的變更: 值為 0 的旗標的 'repr()' 已改變。現在是：

          >>> Color(0)
          <Color: 0>

 -- 類別: enum.IntFlag

     ‘IntFlag’ is the same as *note Flag: 5c9, but its members are also
     integers and can be used anywhere that an integer can be used.

          >>> from enum import IntFlag, auto
          >>> class Color(IntFlag):
          ...     RED = auto()
          ...     GREEN = auto()
          ...     BLUE = auto()
          ...
          >>> Color.RED & 2
          <Color: 0>
          >>> Color.RED | 2
          <Color.RED|GREEN: 3>

     如果 'IntFlag' 成員經過任何整數運算，其結果不是 'IntFlag'：

          >>> Color.RED + 2
          3

     If a *note Flag: 5c9. operation is performed with an 'IntFlag'
     member and:

        * 結果是合法的 'IntFlag'：回傳 'IntFlag'

        * the result is not a valid 'IntFlag': the result depends on the
          *note FlagBoundary: 5ca. setting

     The *note repr(): 7a1. of unnamed zero-valued flags has changed.
     It is now:

          >>> Color(0)
          <Color: 0>

          備註: *note IntFlag: 21d7. 使用 *note auto: c43. 會產生從 ‘1’
          開始 2 的次方的整數。

     在 3.11 版的變更: 為了更好地支援'現存常數取代 (replacement of
     existing constants)' 的使用情境，*note __str__(): 5c4. 現在會是
     ‘int.__str__()’。為了同樣的理由，*note __format__(): 5c5. 已經是
     ‘int.__format__()’。

     ‘IntFlag’ 的反轉 (inversion) 現在會回傳正值，該值是不在給定旗標的所
     有旗標聯集，而不是一個負值。這符合現有 *note Flag: 5c9. 的行為。

 -- 類別: enum.ReprEnum

     ‘ReprEnum’ 使用 *note Enum: 5d6. 的 *note repr(): 1688.，但使用混合
     資料類型的 *note str(): 3f2.：

        * 對 *note IntEnum: c86. 和 *note IntFlag: 21d7. 是
          ‘int.__str__()’

        * 對 *note StrEnum: 5c0. 是 ‘str.__str__()’

     繼承 ‘ReprEnum’ 來保留混合資料類型的 *note str(): 3f2. / *note
     format(): 5c3.，而不是使用 *note Enum: 5d6. 預設的 *note str():
     5c8.。

     在 3.11 版被加入.

 -- 類別: enum.EnumCheck

     'EnumCheck' 包含 *note verify(): 5cb. 裝飾器使用的選項，以確保多樣
     的限制，不符合限制會產生 *note ValueError: 1e7.。

      -- 屬性: UNIQUE

          確保每個值只有一個名稱：

               >>> from enum import Enum, verify, UNIQUE
               >>> @verify(UNIQUE)
               ... class Color(Enum):
               ...     RED = 1
               ...     GREEN = 2
               ...     BLUE = 3
               ...     CRIMSON = 1
               Traceback (most recent call last):
               ...
               ValueError: aliases found in <enum 'Color'>: CRIMSON -> RED

      -- 屬性: CONTINUOUS

          確保在最小值成員跟最大值成員間沒有缺少值：

               >>> from enum import Enum, verify, CONTINUOUS
               >>> @verify(CONTINUOUS)
               ... class Color(Enum):
               ...     RED = 1
               ...     GREEN = 2
               ...     BLUE = 5
               Traceback (most recent call last):
               ...
               ValueError: invalid enum 'Color': missing values 3, 4

      -- 屬性: NAMED_FLAGS

          確保任何旗標群組 / 遮罩只包含命名旗標 - 當值是用指定而不是透過
          *note auto(): c43. 產生時是很實用的：

               >>> from enum import Flag, verify, NAMED_FLAGS
               >>> @verify(NAMED_FLAGS)
               ... class Color(Flag):
               ...     RED = 1
               ...     GREEN = 2
               ...     BLUE = 4
               ...     WHITE = 15
               ...     NEON = 31
               Traceback (most recent call last):
               ...
               ValueError: invalid Flag 'Color': aliases WHITE and NEON are missing combined values of 0x18 [use enum.show_flag_values(value) for details]

          備註: CONTINUOUS 和 NAMED_FLAGS 是設計用來運作在整數值的成員上
          。

     在 3.11 版被加入.

 -- 類別: enum.FlagBoundary

     ‘FlagBoundary’ controls how out-of-range values are handled in
     *note Flag: 5c9. and its subclasses.

      -- 屬性: STRICT

          範圍外的值會引發 *note ValueError: 1e7.。這是 *note Flag: 5c9.
          的預設行為：

               >>> from enum import Flag, STRICT, auto
               >>> class StrictFlag(Flag, boundary=STRICT):
               ...     RED = auto()
               ...     GREEN = auto()
               ...     BLUE = auto()
               ...
               >>> StrictFlag(2**2 + 2**4)
               Traceback (most recent call last):
               ...
               ValueError: <flag 'StrictFlag'> invalid value 20
                   given 0b0 10100
                 allowed 0b0 00111

      -- 屬性: CONFORM

          Out-of-range values have invalid values removed, leaving a
          valid *note Flag: 5c9. value:

               >>> from enum import Flag, CONFORM, auto
               >>> class ConformFlag(Flag, boundary=CONFORM):
               ...     RED = auto()
               ...     GREEN = auto()
               ...     BLUE = auto()
               ...
               >>> ConformFlag(2**2 + 2**4)
               <ConformFlag.BLUE: 4>

      -- 屬性: EJECT

          Out-of-range values lose their *note Flag: 5c9. membership and
          revert to *note int: 23c.

               >>> from enum import Flag, EJECT, auto
               >>> class EjectFlag(Flag, boundary=EJECT):
               ...     RED = auto()
               ...     GREEN = auto()
               ...     BLUE = auto()
               ...
               >>> EjectFlag(2**2 + 2**4)
               20

      -- 屬性: KEEP

          Out-of-range values are kept, and the *note Flag: 5c9.
          membership is kept.  This is the default for *note IntFlag:
          21d7.:

               >>> from enum import Flag, KEEP, auto
               >>> class KeepFlag(Flag, boundary=KEEP):
               ...     RED = auto()
               ...     GREEN = auto()
               ...     BLUE = auto()
               ...
               >>> KeepFlag(2**2 + 2**4)
               <KeepFlag.BLUE|16: 20>

在 3.11 版被加入.

__________________________________________________________________

* Menu:

* 支援 __dunder__ 名稱::
* 支援 _sunder_ 名稱::


File: python.info,  Node: 支援 __dunder__ 名稱,  Next: 支援 _sunder_ 名稱,  Up: 資料型別<2>

5.8.14.3 支援 ‘__dunder__’ 名稱
...............................

*note __members__: 24a0. 是一個唯讀有序的‘成員名稱’：‘成員’項目的對映。
只有在類別上可用。

*note __new__(): 24a6, if specified, must create and return the enum
members; it is also a very good idea to set the member's ‘_value_’
appropriately.  Once all the members are created it is no longer used.


File: python.info,  Node: 支援 _sunder_ 名稱,  Prev: 支援 __dunder__ 名稱,  Up: 資料型別<2>

5.8.14.4 支援 ‘_sunder_’ 名稱
.............................

   - *note _add_alias_(): 24a2. - adds a new name as an alias to an
     existing member.

   - *note _add_value_alias_(): 24a3. - adds a new value as an alias to
     an existing member.

   - *note _name_: 24a7. - 成員名稱

   - *note _value_: 24a8. - 成員的值；可以在 ‘__new__’ 設定

   - *note _missing_(): 24af. - 當值沒有被找到時會使用的查詢函式；可以被
     覆寫

   - *note _ignore_: 24aa. - 一個名稱的串列，可以是 *note list: 5b6. 或
     *note str: 3f2.，它不會被轉換成成員，且在最後的類別上會被移除

   - *note _order_: 24a9. - 不再被使用，僅為了向後相容而保留（類別屬性，
     在類別建立時移除）

   - *note _generate_next_value_(): 24ac. - 用來為列舉成員取得合適的值；
     可以被覆寫

          備註: For standard *note Enum: 5d6. classes the next value
          chosen is the highest value seen incremented by one.

          For *note Flag: 5c9. classes the next value chosen will be the
          next highest power-of-two.

   - While ‘_sunder_’ names are generally reserved for the further
     development of the *note Enum: 5d6. class and can not be used, some
     are explicitly allowed:

        - ‘_repr_*’ (e.g.  ‘_repr_html_’), as used in IPython's rich
          display(1)

在 3.6 版被加入: ‘_missing_’、‘_order_’、‘_generate_next_value_’

在 3.7 版被加入: ‘_ignore_’

在 3.13 版被加入: ‘_add_alias_’, ‘_add_value_alias_’, ‘_repr_*’

__________________________________________________________________

   ---------- Footnotes ----------

   (1) 
https://ipython.readthedocs.io/en/stable/config/integrating.html#rich-display


File: python.info,  Node: 通用項目與裝飾器,  Next: 備註,  Prev: 資料型別<2>,  Up: enum --- 對列舉的支援

5.8.14.5 通用項目與裝飾器
.........................

 -- 類別: enum.auto

     'auto' can be used in place of a value.  If used, the 'Enum'
     machinery will call an *note Enum: 5d6.'s *note
     _generate_next_value_(): 24ac. to get an appropriate value.  For
     *note Enum: 5d6. and *note IntEnum: c86. that appropriate value
     will be the last value plus one; for *note Flag: 5c9. and *note
     IntFlag: 21d7. it will be the first power-of-two greater than the
     highest value; for *note StrEnum: 5c0. it will be the lower-cased
     version of the member's name.  Care must be taken if mixing
     'auto()' with manually specified values.

     'auto' 實例只有在最上層的賦值時才會被解析：

        * ‘FIRST = auto()’ 可以運作（auto() 會被取代成 ‘1’）

        * ‘SECOND = auto(), -2’ 可以運作（auto 會被取代成 ‘2’, 因此 ‘2,
          -2’ 會被用來建立列舉成員 ‘SECOND’；

        * ‘THREE = [auto(), -3]’ '無法'運作（‘<auto 實例>, -3’ 會被用來
          建立列舉成員 ‘THREE’）

     在 3.11.1 版的變更: 在之前的版本中，‘auto()’ 必須是賦值行裡的唯一內
     容才能運作正確。

     可以覆寫 ‘_generate_next_value_’ 來客製 'auto' 使用的值。

          備註: 在 3.13 預設 ‘_generate_next_value_’ 總是回傳最大的成員
          值加一，如果任何成員是不相容的類型就會失敗。

 -- 函式: @enum.property

     和內建的 'property' 相似的裝飾器，但只專門針對列舉。它允許成員屬性
     和成員本身有相同名稱。

          備註: '屬性'和成員必須定義在分開的類別裡；例如 'value' 和
          'name' 屬性定義在 'Enum' 類別而 'Enum' 子類別可以定義成員名稱
          為 ‘value’ 和 ‘name’。

     在 3.11 版被加入.

 -- 函式: @enum.unique

     專門針對列舉的 *note class: 126a. 裝飾器。它搜尋列舉的 *note
     __members__: 24a0.，蒐集任何它找到的別名；如果有找到任何別名則引發
     *note ValueError: 1e7. 並附上細節：

          >>> from enum import Enum, unique
          >>> @unique
          ... class Mistake(Enum):
          ...     ONE = 1
          ...     TWO = 2
          ...     THREE = 3
          ...     FOUR = 3
          ...
          Traceback (most recent call last):
          ...
          ValueError: duplicate values found in <enum 'Mistake'>: FOUR -> THREE

 -- 函式: @enum.verify

     專門針對列舉的 *note class: 126a. 裝飾器。使用 *note EnumCheck:
     5cc. 裡的成員來指定在裝飾的列舉上應該檢查什麼限制。

     在 3.11 版被加入.

 -- 函式: @enum.member

     列舉所使用的裝飾器：其目標會變成成員。

     在 3.11 版被加入.

 -- 函式: @enum.nonmember

     列舉所使用的裝飾器：其目標不會變成成員。

     在 3.11 版被加入.

 -- 函式: @enum.global_enum

     修改列舉的 *note str(): 3f2. 及 *note repr(): 7a1. 的裝飾器，讓成員
     顯示為屬於模組而不是其類別。應該只有當列舉成員被匯出到模組的全域命
     名空間才使用（範例請參考 *note re.RegexFlag: 5d2.）。

     在 3.11 版被加入.

 -- 函式: enum.show_flag_values (value)

     回傳在旗標'值'中包含的所有 2 的次方的整數串列。

     在 3.11 版被加入.

__________________________________________________________________


File: python.info,  Node: 備註,  Prev: 通用項目與裝飾器,  Up: enum --- 對列舉的支援

5.8.14.6 備註
.............

*note IntEnum: c86.、*note StrEnum: 5c0. 及 *note IntFlag: 21d7.

     這三種列舉類型是設計來直接取代現有以整數及字串為基底的值；因此它們
     有額外的限制：

        - ‘__str__’ 使用值而不是列舉成員的名稱

        - ‘__format__’ 因為使用 ‘__str__’，也會使用值而不是列舉成員的名
          稱

     如果你不需要或不想要這些限制，你可以透過混合 ‘int’ 或 ‘str’ 類型來
     建立自己的基礎類別：

          >>> from enum import Enum
          >>> class MyIntEnum(int, Enum):
          ...     pass

     或者你也可以在你的列舉重新給定合適的 *note str(): 3f2.：

          >>> from enum import Enum, IntEnum
          >>> class MyIntEnum(IntEnum):
          ...     __str__ = Enum.__str__


File: python.info,  Node: graphlib —-- 使用類圖 graph-like 結構進行操作的功能,  Prev: enum --- 對列舉的支援,  Up: 資料型別

5.8.15 ‘graphlib’ —- 使用類圖 (graph-like) 結構進行操作的功能
-------------------------------------------------------------

'原始碼：'Lib/graphlib.py(1)

__________________________________________________________________

 -- 類別: graphlib.TopologicalSorter (graph=None)

     提供對包含*note 可雜湊 (hashable): 5b5. 節點之圖 (graph) 進行拓撲排
     序 (topologically sort) 的功能。

     拓撲排序是圖中頂點 (vertex) 的線性排序，使得對於從頂點 u 到頂點 v 的
     每條有向邊 (directed edge) u -> v，頂點 u 在排序中會位於頂點 v 之前
     。例如，圖的頂點可能代表要執行的任務，而邊可能代表一個任務必須在另
     一個任務之前執行的限制；在此範例中，拓撲排序只是任務的一種有效序列
     。若且唯若 (if and only if) 圖沒有有向環 (directed cycle) 時，即如
     果它是個有向無環圖 (directed acyclic graph)，則完整的拓撲排序才是可
     行的。

     如果提供了可選的 'graph' 引數，它必須是表示有向無環圖的字典，其中鍵
     是節點，值是圖中該節點的包含所有前驅節點 (predecessor) 之可疊代物件
     （這些前驅節點具有指向以鍵表示之節點的邊）。可以使用 *note add():
     24c2. 方法將其他節點新增到圖中。

     在一般情況下，對給定的圖執行排序所需的步驟如下：

        * 以選用的初始圖建立 *note TopologicalSorter: 886. 的實例。

        * 在圖中新增其他節點。

        * 呼叫圖的 *note prepare(): 24c3.。

        * 當 *note is_active(): 24c4. 為 ‘True’ 時，疊代 *note
          get_ready(): 24c5. 回傳的節點並處理它們。在每個節點完成處理時
          呼叫 *note done(): 24c6.。

     如果只需要立即對圖中的節點進行排序且不涉及平行性 (parallelism)，則
     可以直接使用便捷方法 *note TopologicalSorter.static_order(): 24c7.：

          >>> graph = {"D": {"B", "C"}, "C": {"A"}, "B": {"A"}}
          >>> ts = TopologicalSorter(graph)
          >>> tuple(ts.static_order())
          ('A', 'C', 'B', 'D')

     該類別設計為在節點準備就緒時，簡單支援節點的平行處理。例如：

          topological_sorter = TopologicalSorter()

          # Add nodes to 'topological_sorter'...

          topological_sorter.prepare()
          while topological_sorter.is_active():
              for node in topological_sorter.get_ready():
                  # Worker threads or processes take nodes to work on off the
                  # 'task_queue' queue.
                  task_queue.put(node)

              # When the work for a node is done, workers put the node in
              # 'finalized_tasks_queue' so we can get more nodes to work on.
              # The definition of 'is_active()' guarantees that, at this point, at
              # least one node has been placed on 'task_queue' that hasn't yet
              # been passed to 'done()', so this blocking 'get()' must (eventually)
              # succeed.  After calling 'done()', we loop back to call 'get_ready()'
              # again, so put newly freed nodes on 'task_queue' as soon as
              # logically possible.
              node = finalized_tasks_queue.get()
              topological_sorter.done(node)

      -- 方法: add (node, *predecessors)

          向圖中新增新節點及其前驅節點。'node' 和 'predecessors' 中的所
          有元素都必須是*note 可雜湊: 5b5.的。

          如果以相同節點引數多次呼叫，則依賴項的集合將會是傳入的所有依賴
          項的聯集。

          可以新增一個沒有依賴關係的節點（'predecessors' 未提供）或提供
          兩次依賴關係。如果有之前未曾提供的節點被包含在 'predecessors'
          中，它將自動新增到沒有前驅節點的圖中。

          如果在 *note prepare(): 24c3. 之後呼叫，則引發 *note
          ValueError: 1e7.。

      -- 方法: prepare ()

          將圖標記為已完成並檢查圖中的循環。如果檢測到任何循環，將引發
          *note CycleError: 24c8.，但 *note get_ready(): 24c5. 仍可用於
          盡可能獲得更多的節點，直到循環阻塞了進度。呼叫此函式後就無法修
          改圖，因此無法使用 *note add(): 24c2. 來新增更多節點。

      -- 方法: is_active ()

          如果可以有更多進度則回傳 ‘True’，否則回傳 ‘False’。如果循環不
          阻塞解析 (resolution) 並且仍有節點準備就緒但尚未由 *note
          TopologicalSorter.get_ready(): 24c5. 回傳或標記為 *note
          TopologicalSorter.done(): 24c6. 的節點數量較 *note
          TopologicalSorter.get_ready(): 24c5. 所回傳的少，則可以繼續取
          得進度。

          此類別的 *note __bool__(): 1268. 方法遵循此函式，因此以下做法
          ：

               if ts.is_active():
                   ...

          可以簡單地用以下方式替換：

               if ts:
                   ...

          如果呼叫之前沒有先呼叫 *note prepare(): 24c3. 則引發 *note
          ValueError: 1e7.。

      -- 方法: done (*nodes)

          將 *note TopologicalSorter.get_ready(): 24c5. 回傳的一組節點標
          記為已處理，停止阻塞 'nodes' 中每個節點的任何後繼節點
          (successor)，以便將來通過呼叫 *note
          TopologicalSorter.get_ready(): 24c5. 回傳。

          若沒有和該呼叫一起呼叫 *note prepare(): 24c3. 或節點還沒有被
          *note get_ready(): 24c5. 回傳，且如果 'nodes' 中有任何節點已被
          先前對此方法的呼叫標記為已處理、或者未使用 *note
          TopologicalSorter.add(): 24c2. 將節點新增到圖中，則引發 *note
          ValueError: 1e7.。

      -- 方法: get_ready ()

          回傳一個包含所有準備就緒節點的 ‘tuple’。最初它回傳沒有前驅節點
          的所有節點，一旦通過呼叫 *note TopologicalSorter.done(): 24c6.
          來將這些節點標記為已處理後，進一步的呼叫將回傳所有其全部前驅節
          點都已被處理的新節點。若無法取得更多進度，將回傳空 tuple。

          如果呼叫之前沒有先呼叫 *note prepare(): 24c3. 則引發 *note
          ValueError: 1e7.。

      -- 方法: static_order ()

          回傳一個可疊代物件，它將按拓撲排序疊代節點。使用此方法時，不應
          呼叫 *note prepare(): 24c3. 和 *note done(): 24c6.。此方法等效
          於：

               def static_order(self):
                   self.prepare()
                   while self.is_active():
                       node_group = self.get_ready()
                       yield from node_group
                       self.done(*node_group)

          回傳的特定順序可能取決於將項目插入圖中的特定順序。例如：

               >>> ts = TopologicalSorter()
               >>> ts.add(3, 2, 1)
               >>> ts.add(1, 0)
               >>> print([*ts.static_order()])
               [2, 0, 1, 3]

               >>> ts2 = TopologicalSorter()
               >>> ts2.add(1, 0)
               >>> ts2.add(3, 2, 1)
               >>> print([*ts2.static_order()])
               [0, 2, 1, 3]

          這是因為 "0" 和 "2" 在圖中處於同一級別（它們將在對 *note
          get_ready(): 24c5. 的同一呼叫中回傳）並且它們之間的順序取決於
          插入順序。

          如果檢測到任何循環，則引發 *note CycleError: 24c8.。

     在 3.9 版被加入.

* Menu:

* 例外: 例外<2>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/graphlib.py


File: python.info,  Node: 例外<2>,  Up: graphlib —-- 使用類圖 graph-like 結構進行操作的功能

5.8.15.1 例外
.............

*note graphlib: 5b. 模組定義了以下例外類別：

 -- 例外: graphlib.CycleError

     *note ValueError: 1e7. 的子類別，如果作用的圖中存在循環則由 *note
     TopologicalSorter.prepare(): 24c3. 引發。如果存在多個循環，則只會報
     告未定義的其中一個並包含在例外中。

     檢測到的循環可以通過例外實例的 *note args: 512. 屬性中第二個元素來
     存取，其為一個節點列表，每個節點在圖中都是列表中下一個節點的直接前
     驅節點（immediate predecessor，即父節點）。在報告列表中，第一個和最
     後一個節點將會是相同的，用以明確表示它是循環的。


File: python.info,  Node: 數值與數學模組,  Next: 函式編程模組,  Prev: 資料型別,  Up: Python 標準函式庫 Standard Library

5.9 數值與數學模組
==================

The modules described in this chapter provide numeric and math-related
functions and data types.  The *note numbers: 8e. module defines an
abstract hierarchy of numeric types.  The *note math: 81. and *note
cmath: 11. modules contain various mathematical functions for
floating-point and complex numbers.  The *note decimal: 2e. module
supports exact representations of decimal numbers, using arbitrary
precision arithmetic.

The following modules are documented in this chapter:

* Menu:

* numbers: numbers --- 數值的抽象基底類別. 數值的抽象基底類別
* math: math --- 數學函式. 數學函式
* cmath: cmath --- 複數的數學函式. 複數的數學函式
* decimal: decimal --- 十進位固定點和浮點運算. 十進位固定點和浮點運算
* fractions: fractions --- 有理數. 有理數
* random: random --- 生成偽隨機數. 生成偽隨機數
* statistics: statistics --- 數學統計函式. 數學統計函式


File: python.info,  Node: numbers --- 數值的抽象基底類別,  Next: math --- 數學函式,  Up: 數值與數學模組

5.9.1 ‘numbers’ -- 數值的抽象基底類別
-------------------------------------

'原始碼：'Lib/numbers.py(1)

__________________________________________________________________

‘numbers’ 模組 ( PEP 3141(2)) 定義了數值*note 抽象基底類別: 114e. 的階層
結構，其中逐一定義了更多操作。此模組中定義的型別都不可被實例化。

 -- 類別: numbers.Number

     數值階層結構的基礎。如果你只想確認引數 'x' 是不是數值、並不關心其型
     別，請使用 ‘isinstance(x, Number)’。

* Menu:

* 數值的階層::
* 給型別實作者的註記::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/numbers.py

   (2) https://peps.python.org/pep-3141/


File: python.info,  Node: 數值的階層,  Next: 給型別實作者的註記,  Up: numbers --- 數值的抽象基底類別

5.9.1.1 數值的階層
..................

 -- 類別: numbers.Complex

     這個型別的子類別描述了複數並包含適用於內建 *note complex: 2c9. 型別
     的操作。這些操作有：*note complex: 2c9. 和 *note bool: 40e. 的轉換
     、*note real: 24d2.、*note imag: 24d3.、‘+’、‘-’、‘*’、‘/’、‘**’、
     *note abs(): 1ba8.、*note conjugate(): 24d4.、‘==’ 以及 ‘!=’。除
     ‘-’ 和 ‘!=’ 之外所有操作都是抽象的。

      -- 屬性: real

          為抽象的。取得該數值的實數部分。

      -- 屬性: imag

          為抽象的。取得該數值的虛數部分。

      -- 方法: abstractmethod conjugate ()

          為抽象的。回傳共軛複數，例如 ‘(1+3j).conjugate() == (1-3j)’。

 -- 類別: numbers.Real

     相對於 *note Complex: 24d1.，‘Real’ 加入了只有實數才能進行的操作。

     簡單的說，有 *note float: 2c8. 的轉換、*note math.trunc(): 1331.、
     *note round(): 126d.、*note math.floor(): 132f.、*note math.ceil():
     1330.、*note divmod(): 945.、‘//’、‘%’、 ‘<’、‘<=’、‘>’、和 ‘>=’。

     實數同樣提供 *note complex(): 2c9.、*note real: 24d2.、*note imag:
     24d3. 和 *note conjugate(): 24d4. 的預設值。

 -- 類別: numbers.Rational

     *note Real: 2073. 的子型別，並增加了 *note numerator: 24d5. 和
     *note denominator: 24d6. 這兩種特性。它也會提供 *note float(): 2c8.
     的預設值。

     *note numerator: 24d5. 和 *note denominator: 24d6. 的值必須是 *note
     Integral: 1e92. 的實例且 *note denominator: 24d6. 要是正數。

      -- 屬性: numerator

          為抽象的。

      -- 屬性: denominator

          為抽象的。

 -- 類別: numbers.Integral

     *note Rational: 1255. 的子型別，並增加了 *note int: 23c. 的轉換操作
     。為 *note float(): 2c8.、*note numerator: 24d5. 和 *note
     denominator: 24d6. 提供了預設值。為 *note pow(): 976. 方法增加了求
     餘 (modulus) 和位元字串運算 (bit-string operations) 的抽象方法：
     ‘<<’、‘>>’、‘&’、‘^’、‘|’、‘~’。


File: python.info,  Node: 給型別實作者的註記,  Prev: 數值的階層,  Up: numbers --- 數值的抽象基底類別

5.9.1.2 給型別實作者的註記
..........................

實作者需注意，相等的數值除了大小相等外，還必須擁有同樣的雜湊值。當使用兩
個不同的實數擴充時，這可能是很微妙的。例如，*note fractions.Fraction:
1c7. 底下的 *note hash(): 58f. 實作如下：

     def __hash__(self):
         if self.denominator == 1:
             # Get integers right.
             return hash(self.numerator)
         # Expensive check, but definitely correct.
         if self == float(self):
             return hash(float(self))
         else:
             # Use tuple's hash to avoid a high collision rate on
             # simple fractions.
             return hash((self.numerator, self.denominator))

* Menu:

* 加入更多數值 ABC::
* 實作算術操作::


File: python.info,  Node: 加入更多數值 ABC,  Next: 實作算術操作,  Up: 給型別實作者的註記

5.9.1.3 加入更多數值 ABC
........................

當然，還有更多用於數值的 ABC，如果不加入它們就不會有健全的階層。你可以在
*note Complex: 24d1. 和 *note Real: 2073. 中加入 ‘MyFoo’，像是：

     class MyFoo(Complex): ...
     MyFoo.register(Real)


File: python.info,  Node: 實作算術操作,  Prev: 加入更多數值 ABC,  Up: 給型別實作者的註記

5.9.1.4 實作算術操作
....................

我們想要實作算術操作，來使得混合模式操作要麼呼叫一個作者知道兩個引數之型
別的實作，要麼將其轉換成最接近的內建型別並執行這個操作。對於 *note
Integral: 1e92. 的子型別，這意味著 *note __add__(): 1e62. 和 *note
__radd__(): 1e63. 必須用如下方式定義：

     class MyIntegral(Integral):

         def __add__(self, other):
             if isinstance(other, MyIntegral):
                 return do_my_adding_stuff(self, other)
             elif isinstance(other, OtherTypeIKnowAbout):
                 return do_my_other_adding_stuff(self, other)
             else:
                 return NotImplemented

         def __radd__(self, other):
             if isinstance(other, MyIntegral):
                 return do_my_adding_stuff(other, self)
             elif isinstance(other, OtherTypeIKnowAbout):
                 return do_my_other_adding_stuff(other, self)
             elif isinstance(other, Integral):
                 return int(other) + int(self)
             elif isinstance(other, Real):
                 return float(other) + float(self)
             elif isinstance(other, Complex):
                 return complex(other) + complex(self)
             else:
                 return NotImplemented

*note Complex: 24d1. 的子類別有 5 種不同的混合型別操作。我將上面提到所有
不涉及 ‘MyIntegral’ 和 ‘OtherTypeIKnowAbout’ 的程式碼稱作「模板
(boilerplate)」。‘a’ 是 *note Complex: 24d1. 之子型別 ‘A’ 的實例 (‘a : A
<: Complex’)，同時 ‘b : B <: Complex’。我將要計算 ‘a + b’：

  1. 如果 ‘A’ 有定義成一個接受 ‘b’ 的 *note __add__(): 1e62.，不會發生問
     題。

  2. 如果 ‘A’ 回退成模板程式碼，它將回傳一個來自 *note __add__(): 1e62.
     的值，並喪失讓 ‘B’ 定義一個更完善的 *note __radd__(): 1e63. 的機會
     ，因此模板需要回傳一個來自 ‘__add__()’ 的 *note NotImplemented:
     776.。（或者 ‘A’ 可能完全不實作 ‘__add__()’。）

  3. 接著看 ‘B’ 的 *note __radd__(): 1e63.。如果它接受 ‘a’ ，不會發生問
     題。

  4. 如果沒有成功回退到模板，就沒有更多的方法可以去嘗試，因此這裡將使用
     預設的實作。

  5. 如果 ‘B <: A’，Python 會在 ‘A.__add__’ 之前嘗試 ‘B.__radd__’。這是
     可行的，因為它是透過對 ‘A’ 的理解而實作的，所以這可以在交給 *note
     Complex: 24d1. 之前處理好這些實例。

如果 ‘A <: Complex’ 和 ‘B <: Real’ 且沒有共享任何其他型別上的理解，那麼
適當的共享操作會涉及內建的 *note complex: 2c9.，並且分別用到 *note
__radd__(): 1e63.，因此 ‘a+b == b+a’。

由於大部分對任意給定類型的操作都十分相似的，定義一個為任意給定運算子生成
向前 (forward) 與向後 (reverse) 實例的輔助函式可能會非常有用。例如，
*note fractions.Fraction: 1c7. 使用了：

     def _operator_fallbacks(monomorphic_operator, fallback_operator):
         def forward(a, b):
             if isinstance(b, (int, Fraction)):
                 return monomorphic_operator(a, b)
             elif isinstance(b, float):
                 return fallback_operator(float(a), b)
             elif isinstance(b, complex):
                 return fallback_operator(complex(a), b)
             else:
                 return NotImplemented
         forward.__name__ = '__' + fallback_operator.__name__ + '__'
         forward.__doc__ = monomorphic_operator.__doc__

         def reverse(b, a):
             if isinstance(a, Rational):
                 # 包含整數。
                 return monomorphic_operator(a, b)
             elif isinstance(a, Real):
                 return fallback_operator(float(a), float(b))
             elif isinstance(a, Complex):
                 return fallback_operator(complex(a), complex(b))
             else:
                 return NotImplemented
         reverse.__name__ = '__r' + fallback_operator.__name__ + '__'
         reverse.__doc__ = monomorphic_operator.__doc__

         return forward, reverse

     def _add(a, b):
         """a + b"""
         return Fraction(a.numerator * b.denominator +
                         b.numerator * a.denominator,
                         a.denominator * b.denominator)

     __add__, __radd__ = _operator_fallbacks(_add, operator.add)

     # ...


File: python.info,  Node: math --- 數學函式,  Next: cmath --- 複數的數學函式,  Prev: numbers --- 數值的抽象基底類別,  Up: 數值與數學模組

5.9.2 ‘math’ -- 數學函式
------------------------

__________________________________________________________________

此模組提供對 C 標準中定義的數學相關函式的存取。

這些函式不支援複數；若你需要計算複數，請使用 *note cmath: 11. 模組的同名
函式。這是因為大多數的使用者並不想學習那麼多理解複數所需的數學概念，所以
根據支援複數與否分為兩種函式。收到一個例外而非複數回傳值，有助於程式設計
師提早察覺參數中包含非預期的複數，進而從源頭查出導致此情況的原因。

此模組提供下列函式。除非特意註明，否則回傳值皆為浮點數。

* Menu:

* 數論與表現函式::
* Power and logarithmic functions::
* Trigonometric functions::
* Angular conversion::
* Hyperbolic functions::
* Special functions::
* 常數: 常數<2>.


File: python.info,  Node: 數論與表現函式,  Next: Power and logarithmic functions,  Up: math --- 數學函式

5.9.2.1 數論與表現函式
......................

 -- 函式: math.ceil (x)

     回傳 'x' 經上取整的值，即大於或等於 'x' 的最小整數。若 'x' 並非浮點
     數，此函式將委派給 *note x.__ceil__: 1e91.，並回傳 *note Integral:
     1e92. 型別的值。

 -- 函式: math.comb (n, k)

     回傳從 'n' 個物品中不重複且不考慮排序地取出 'k' 個物品的方法數。

     當 ‘k <= n’ 時其值為 ‘n! / (k! * (n - k)!)’，否則其值為 ‘0’。

     因為此值等同於 ‘(1 + x)ⁿ’ 進行多項式展開後第 k 項的係數，所以又稱為
     二項式係數。

     當任一參數非整數型別時會引發 *note TypeError: 4dd.。當任一參數為負
     數時會引發 *note ValueError: 1e7.。

     在 3.8 版被加入.

 -- 函式: math.copysign (x, y)

     回傳與 'x' 相同長度（絕對值）且與 'y' 同號的浮點數。在支援帶符號零
     的平臺上，‘copysign(1.0, -0.0)’ 回傳 '-1.0'。

 -- 函式: math.fabs (x)

     回傳 'x' 的絕對值。

 -- 函式: math.factorial (n)

     以整數回傳 'n' 的階乘。若 'n' 非整數型別或其值為負會引發 *note
     ValueError: 1e7.。

     在 3.10 版的變更: Floats with integral values (like ‘5.0’) are no
     longer accepted.

 -- 函式: math.floor (x)

     回傳 'x' 經下取整的值，即小於或等於 'x' 的最大整數。若 'x' 並非浮點
     數，此函式將委派給 *note x.__floor__: 1e90.，並回傳 *note Integral:
     1e92. 型別的值。

 -- 函式: math.fma (x, y, z)

     Fused multiply-add operation.  Return ‘(x * y) + z’, computed as
     though with infinite precision and range followed by a single round
     to the ‘float’ format.  This operation often provides better
     accuracy than the direct expression ‘(x * y) + z’.

     This function follows the specification of the fusedMultiplyAdd
     operation described in the IEEE 754 standard.  The standard leaves
     one case implementation-defined, namely the result of ‘fma(0, inf,
     nan)’ and ‘fma(inf, 0, nan)’.  In these cases, ‘math.fma’ returns a
     NaN, and does not raise any exception.

     在 3.13 版被加入.

 -- 函式: math.fmod (x, y)

     回傳 C 函式庫所定義的 ‘fmod(x, y)’ 函式值。請注意此函式與 Python 運
     算式 ‘x % y’ 可能會回傳不同結果。C 標準要求 ‘fmod(x, y)’ 的回傳值完
     全等同（數學定義上，即無限精度）於 ‘x - n*y’，'n' 為可使回傳值與
     'x' 同號且長度小於 ‘abs(y)’ 的整數。Python 運算式 ‘x % y’ 的回傳值
     則與 'y' 同號，且可能無法精確地計算浮點數引數。例如：‘fmod(-1e-100,
     1e100)’ 的值為 ‘-1e-100’，但 Python 運算式 ‘-1e-100 % 1e100’ 的結果
     為 ‘1e100-1e-100’，此值無法準確地表示成浮點數，並會四捨五入為出乎意
     料的 ‘1e100’。因此，處理浮點數時通常會選擇函式 *note fmod(): 1f43.，
     而處理整數時會選擇 Python 運算式 ‘x % y’。

 -- 函式: math.frexp (x)

     以 ‘(m, e)’ 對的格式回傳 'x' 的尾數 'm' 及指數 'e'。'm' 是浮點數而
     'e' 是整數，且兩者精確地使 ‘x == m * 2**e’。若 'x' 為零，回傳
     ‘(0.0, 0)’，否則令 ‘0.5 <= abs(m) < 1’。此函式用於以可攜的方式「分
     割」浮點數內部表示法。

 -- 函式: math.fsum (iterable)

     回傳可疊代物件（iterable）中所有值的精確浮點數和。透過追蹤過程中多
     個部分和（partial sum）以避免精確度損失。

     此演算法準確性奠基於保證 IEEE-754 浮點標準及典型奇進偶捨（
     half-even）模式。於有些非 Windows 平台建置時，底層 C 函式庫使用延伸
     精度加法運算，而可能導致對過程中同一部分和重複捨入，並使其最低有效
     位不如預期。

     更深入的討論及兩種替代做法請參閱 ASPN cookbook recipes 精準的浮點數
     總和(1)。

 -- 函式: math.gcd (*integers)

     回傳指定整數引數的最大公因數。若存在任一非零引數，回傳值為所有引數
     共有因數中最大的正整數。若所有引數皆為零，則回傳值為 ‘0’。‘gcd()’ 若
     未傳入任何引數也將回傳 ‘0’。

     在 3.5 版被加入.

     在 3.9 版的變更: 新增支援任意數量的引數。先前僅支援兩個引數。

 -- 函式: math.isclose (a, b, *, rel_tol=1e-09, abs_tol=0.0)

     若 'a' 及 'b' 兩值足夠接近便回傳 ‘True’，否則回傳 ‘False’。

     兩數是否足夠接近取決於給定的絕對及相對容許偏差（tolerance）。

     'rel_tol' 為相對容許偏差 ── 'a' 與 'b' 兩數差的最大容許值，與 'a' 及
     'b' 兩數的絕對值中較大者相關。例如欲設置 5% 的容許偏差，則傳入
     ‘rel_tol=0.05’。其預設值為 ‘1e-09’，該值可確保兩數於大約 9 個十進數
     位內相同。'rel_tol' 須大於 ‘0’。

     'abs_tol' 為最小絕對容許偏差 ── 於接近零的比較時很有用。'abs_tol' 須
     大於等於 ‘0’。

     若未發生任何錯誤，函式結果為 ‘abs(a-b) <= max(rel_tol * max(abs(a),
     abs(b)), abs_tol)’。

     定義於 IEEE 754 浮點標準中的特殊值 ‘NaN’、‘inf’ 和 ‘-inf’ 會根據該
     標準處理。更明確地說，‘NaN’ 不會與包含自身在內的任何數字足夠接近，
     而 ‘inf’ 及 ‘-inf’ 皆只與自身接近。

     在 3.5 版被加入.

     也參考
     ......

     PEP 485(2) ── 用於測試近似相等的函式

 -- 函式: math.isfinite (x)

     若 'x' 不是無限值或 ‘NaN’ 便回傳 ‘True’，否則回傳 ‘False’。（注意
     ‘0.0’ 被視為有限數。）

     在 3.2 版被加入.

 -- 函式: math.isinf (x)

     若 'x' 是正無限值或負無限值便回傳 ‘True’，否則回傳 ‘False’。

 -- 函式: math.isnan (x)

     若 'x' 是 ‘NaN’ ── 即非數字（NaN, not a number）── 便回傳 ‘True’，
     否則回傳 ‘False’。

 -- 函式: math.isqrt (n)

     回傳非負整數 'n' 的整數平方根。此值為 'n' 精確平方根經下取整的值，
     亦等同於滿足 'a'² ≤ 'n' 的最大整數值 'a'。

     於有些應用程式中，取得滿足 'n' ≤ 'a'² 的最小整數值 'a' ── 或者說
     'n' 精確平方根經上取整的值 ── 會更加方便。對正數 'n'，此值可使用 ‘a
     = 1 + isqrt(n - 1)’ 計算。

     在 3.8 版被加入.

 -- 函式: math.lcm (*integers)

     回傳指定整數引數的最小公倍數。若所有引數值皆非零，回傳值為所有引數
     共有倍數中最小的正整數。若存在任一引數值為零，則回傳值為 ‘0’。
     ‘lcm()’ 若未傳入任何引數將回傳 ‘1’。

     在 3.9 版被加入.

 -- 函式: math.ldexp (x, i)

     回傳 ‘x * (2**i)’。此函式本質上為 *note frexp(): 24de. 的反函式。

 -- 函式: math.modf (x)

     Return the fractional and integer parts of 'x'.  Both results carry
     the sign of 'x' and are floats.

 -- 函式: math.nextafter (x, y, steps=1)

     Return the floating-point value 'steps' steps after 'x' towards
     'y'.

     If 'x' is equal to 'y', return 'y', unless 'steps' is zero.

     範例：

        * ‘math.nextafter(x, math.inf)’ goes up: towards positive
          infinity.

        * ‘math.nextafter(x, -math.inf)’ goes down: towards minus
          infinity.

        * ‘math.nextafter(x, 0.0)’ goes towards zero.

        * ‘math.nextafter(x, math.copysign(math.inf, x))’ goes away from
          zero.

     另請參閱 *note math.ulp(): 8b7.。

     在 3.9 版被加入.

     在 3.12 版的變更: 新增 'steps' 引數。

 -- 函式: math.perm (n, k=None)

     Return the number of ways to choose 'k' items from 'n' items
     without repetition and with order.

     Evaluates to ‘n! / (n - k)!’ when ‘k <= n’ and evaluates to zero
     when ‘k > n’.

     If 'k' is not specified or is ‘None’, then 'k' defaults to 'n' and
     the function returns ‘n!’.

     當任一參數非整數型別時會引發 *note TypeError: 4dd.。當任一參數為負
     數時會引發 *note ValueError: 1e7.。

     在 3.8 版被加入.

 -- 函式: math.prod (iterable, *, start=1)

     Calculate the product of all the elements in the input 'iterable'.
     The default 'start' value for the product is ‘1’.

     When the iterable is empty, return the start value.  This function
     is intended specifically for use with numeric values and may reject
     non-numeric types.

     在 3.8 版被加入.

 -- 函式: math.remainder (x, y)

     Return the IEEE 754-style remainder of 'x' with respect to 'y'.
     For finite 'x' and finite nonzero 'y', this is the difference ‘x -
     n*y’, where ‘n’ is the closest integer to the exact value of the
     quotient ‘x / y’.  If ‘x / y’ is exactly halfway between two
     consecutive integers, the nearest 'even' integer is used for ‘n’.
     The remainder ‘r = remainder(x, y)’ thus always satisfies ‘abs(r)
     <= 0.5 * abs(y)’.

     Special cases follow IEEE 754: in particular, ‘remainder(x,
     math.inf)’ is 'x' for any finite 'x', and ‘remainder(x, 0)’ and
     ‘remainder(math.inf, x)’ raise *note ValueError: 1e7. for any
     non-NaN 'x'.  If the result of the remainder operation is zero,
     that zero will have the same sign as 'x'.

     On platforms using IEEE 754 binary floating point, the result of
     this operation is always exactly representable: no rounding error
     is introduced.

     在 3.7 版被加入.

 -- 函式: math.sumprod (p, q)

     Return the sum of products of values from two iterables 'p' and
     'q'.

     Raises *note ValueError: 1e7. if the inputs do not have the same
     length.

     Roughly equivalent to:

          sum(itertools.starmap(operator.mul, zip(p, q, strict=True)))

     For float and mixed int/float inputs, the intermediate products and
     sums are computed with extended precision.

     在 3.12 版被加入.

 -- 函式: math.trunc (x)

     Return 'x' with the fractional part removed, leaving the integer
     part.  This rounds toward 0: ‘trunc()’ is equivalent to *note
     floor(): 132f. for positive 'x', and equivalent to *note ceil():
     1330. for negative 'x'.  If 'x' is not a float, delegates to *note
     x.__trunc__: 6bf, which should return an *note Integral: 1e92.
     value.

 -- 函式: math.ulp (x)

     Return the value of the least significant bit of the float 'x':

        * If 'x' is a NaN (not a number), return 'x'.

        * If 'x' is negative, return ‘ulp(-x)’.

        * If 'x' is a positive infinity, return 'x'.

        * If 'x' is equal to zero, return the smallest positive
          'denormalized' representable float (smaller than the minimum
          positive 'normalized' float, *note sys.float_info.min: 18f0.).

        * If 'x' is equal to the largest positive representable float,
          return the value of the least significant bit of 'x', such
          that the first float smaller than 'x' is ‘x - ulp(x)’.

        * Otherwise ('x' is a positive finite number), return the value
          of the least significant bit of 'x', such that the first float
          bigger than 'x' is ‘x + ulp(x)’.

     ULP stands for "Unit in the Last Place".

     See also *note math.nextafter(): 440. and *note
     sys.float_info.epsilon: 18f0.

     在 3.9 版被加入.

Note that *note frexp(): 24de. and *note modf(): 24e0. have a different
call/return pattern than their C equivalents: they take a single
argument and return a pair of values, rather than returning their second
return value through an 'output parameter' (there is no such thing in
Python).

For the *note ceil(): 1330, *note floor(): 132f, and *note modf(): 24e0.
functions, note that 'all' floating-point numbers of sufficiently large
magnitude are exact integers.  Python floats typically carry no more
than 53 bits of precision (the same as the platform C double type), in
which case any float 'x' with ‘abs(x) >= 2**52’ necessarily has no
fractional bits.

   ---------- Footnotes ----------

   (1) https://code.activestate.com/recipes/393090/

   (2) https://peps.python.org/pep-0485/


File: python.info,  Node: Power and logarithmic functions,  Next: Trigonometric functions,  Prev: 數論與表現函式,  Up: math --- 數學函式

5.9.2.2 Power and logarithmic functions
.......................................

 -- 函式: math.cbrt (x)

     Return the cube root of 'x'.

     在 3.11 版被加入.

 -- 函式: math.exp (x)

     Return 'e' raised to the power 'x', where 'e' = 2.718281...  is the
     base of natural logarithms.  This is usually more accurate than
     ‘math.e ** x’ or ‘pow(math.e, x)’.

 -- 函式: math.exp2 (x)

     Return '2' raised to the power 'x'.

     在 3.11 版被加入.

 -- 函式: math.expm1 (x)

     Return 'e' raised to the power 'x', minus 1.  Here 'e' is the base
     of natural logarithms.  For small floats 'x', the subtraction in
     ‘exp(x) - 1’ can result in a significant loss of precision(1); the
     *note expm1(): 1184. function provides a way to compute this
     quantity to full precision:

          >>> from math import exp, expm1
          >>> exp(1e-5) - 1  # gives result accurate to 11 places
          1.0000050000069649e-05
          >>> expm1(1e-5)    # result accurate to full precision
          1.0000050000166668e-05

     在 3.2 版被加入.

 -- 函式: math.log (x[, base])

     With one argument, return the natural logarithm of 'x' (to base
     'e').

     With two arguments, return the logarithm of 'x' to the given
     'base', calculated as ‘log(x)/log(base)’.

 -- 函式: math.log1p (x)

     Return the natural logarithm of '1+x' (base 'e').  The result is
     calculated in a way which is accurate for 'x' near zero.

 -- 函式: math.log2 (x)

     Return the base-2 logarithm of 'x'.  This is usually more accurate
     than ‘log(x, 2)’.

     在 3.3 版被加入.

     也參考
     ......

     *note int.bit_length(): 2077. returns the number of bits necessary
     to represent an integer in binary, excluding the sign and leading
     zeros.

 -- 函式: math.log10 (x)

     Return the base-10 logarithm of 'x'.  This is usually more accurate
     than ‘log(x, 10)’.

 -- 函式: math.pow (x, y)

     Return ‘x’ raised to the power ‘y’.  Exceptional cases follow the
     IEEE 754 standard as far as possible.  In particular, ‘pow(1.0, x)’
     and ‘pow(x, 0.0)’ always return ‘1.0’, even when ‘x’ is a zero or a
     NaN. If both ‘x’ and ‘y’ are finite, ‘x’ is negative, and ‘y’ is
     not an integer then ‘pow(x, y)’ is undefined, and raises *note
     ValueError: 1e7.

     Unlike the built-in ‘**’ operator, *note math.pow(): 608. converts
     both its arguments to type *note float: 2c8.  Use ‘**’ or the
     built-in *note pow(): 976. function for computing exact integer
     powers.

     在 3.11 版的變更: The special cases ‘pow(0.0, -inf)’ and ‘pow(-0.0,
     -inf)’ were changed to return ‘inf’ instead of raising *note
     ValueError: 1e7, for consistency with IEEE 754.

 -- 函式: math.sqrt (x)

     Return the square root of 'x'.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Loss_of_significance


File: python.info,  Node: Trigonometric functions,  Next: Angular conversion,  Prev: Power and logarithmic functions,  Up: math --- 數學函式

5.9.2.3 Trigonometric functions
...............................

 -- 函式: math.acos (x)

     Return the arc cosine of 'x', in radians.  The result is between
     ‘0’ and ‘pi’.

 -- 函式: math.asin (x)

     Return the arc sine of 'x', in radians.  The result is between
     ‘-pi/2’ and ‘pi/2’.

 -- 函式: math.atan (x)

     Return the arc tangent of 'x', in radians.  The result is between
     ‘-pi/2’ and ‘pi/2’.

 -- 函式: math.atan2 (y, x)

     Return ‘atan(y / x)’, in radians.  The result is between ‘-pi’ and
     ‘pi’.  The vector in the plane from the origin to point ‘(x, y)’
     makes this angle with the positive X axis.  The point of *note
     atan2(): 24e7. is that the signs of both inputs are known to it, so
     it can compute the correct quadrant for the angle.  For example,
     ‘atan(1)’ and ‘atan2(1, 1)’ are both ‘pi/4’, but ‘atan2(-1, -1)’ is
     ‘-3*pi/4’.

 -- 函式: math.cos (x)

     Return the cosine of 'x' radians.

 -- 函式: math.dist (p, q)

     Return the Euclidean distance between two points 'p' and 'q', each
     given as a sequence (or iterable) of coordinates.  The two points
     must have the same dimension.

     Roughly equivalent to:

          sqrt(sum((px - qx) ** 2.0 for px, qx in zip(p, q)))

     在 3.8 版被加入.

 -- 函式: math.hypot (*coordinates)

     Return the Euclidean norm, ‘sqrt(sum(x**2 for x in coordinates))’.
     This is the length of the vector from the origin to the point given
     by the coordinates.

     For a two dimensional point ‘(x, y)’, this is equivalent to
     computing the hypotenuse of a right triangle using the Pythagorean
     theorem, ‘sqrt(x*x + y*y)’.

     在 3.8 版的變更: Added support for n-dimensional points.  Formerly,
     only the two dimensional case was supported.

     在 3.10 版的變更: Improved the algorithm's accuracy so that the
     maximum error is under 1 ulp (unit in the last place).  More
     typically, the result is almost always correctly rounded to within
     1/2 ulp.

 -- 函式: math.sin (x)

     Return the sine of 'x' radians.

 -- 函式: math.tan (x)

     Return the tangent of 'x' radians.


File: python.info,  Node: Angular conversion,  Next: Hyperbolic functions,  Prev: Trigonometric functions,  Up: math --- 數學函式

5.9.2.4 Angular conversion
..........................

 -- 函式: math.degrees (x)

     Convert angle 'x' from radians to degrees.

 -- 函式: math.radians (x)

     Convert angle 'x' from degrees to radians.


File: python.info,  Node: Hyperbolic functions,  Next: Special functions,  Prev: Angular conversion,  Up: math --- 數學函式

5.9.2.5 Hyperbolic functions
............................

Hyperbolic functions(1) are analogs of trigonometric functions that are
based on hyperbolas instead of circles.

 -- 函式: math.acosh (x)

     Return the inverse hyperbolic cosine of 'x'.

 -- 函式: math.asinh (x)

     Return the inverse hyperbolic sine of 'x'.

 -- 函式: math.atanh (x)

     Return the inverse hyperbolic tangent of 'x'.

 -- 函式: math.cosh (x)

     Return the hyperbolic cosine of 'x'.

 -- 函式: math.sinh (x)

     Return the hyperbolic sine of 'x'.

 -- 函式: math.tanh (x)

     Return the hyperbolic tangent of 'x'.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Hyperbolic_functions


File: python.info,  Node: Special functions,  Next: 常數<2>,  Prev: Hyperbolic functions,  Up: math --- 數學函式

5.9.2.6 Special functions
.........................

 -- 函式: math.erf (x)

     Return the error function(1) at 'x'.

     The *note erf(): b7f. function can be used to compute traditional
     statistical functions such as the cumulative standard normal
     distribution(2):

          def phi(x):
              'Cumulative distribution function for the standard normal distribution'
              return (1.0 + erf(x / sqrt(2.0))) / 2.0

     在 3.2 版被加入.

 -- 函式: math.erfc (x)

     Return the complementary error function at 'x'.  The complementary
     error function(3) is defined as ‘1.0 - erf(x)’.  It is used for
     large values of 'x' where a subtraction from one would cause a loss
     of significance(4).

     在 3.2 版被加入.

 -- 函式: math.gamma (x)

     Return the Gamma function(5) at 'x'.

     在 3.2 版被加入.

 -- 函式: math.lgamma (x)

     Return the natural logarithm of the absolute value of the Gamma
     function at 'x'.

     在 3.2 版被加入.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Error_function

   (2) https://en.wikipedia.org/wiki/Cumulative_distribution_function

   (3) https://en.wikipedia.org/wiki/Error_function

   (4) https://en.wikipedia.org/wiki/Loss_of_significance

   (5) https://en.wikipedia.org/wiki/Gamma_function


File: python.info,  Node: 常數<2>,  Prev: Special functions,  Up: math --- 數學函式

5.9.2.7 常數
............

 -- 資料: math.pi

     The mathematical constant 'π' = 3.141592..., to available
     precision.

 -- 資料: math.e

     The mathematical constant 'e' = 2.718281..., to available
     precision.

 -- 資料: math.tau

     The mathematical constant 'τ' = 6.283185..., to available
     precision.  Tau is a circle constant equal to 2'π', the ratio of a
     circle's circumference to its radius.  To learn more about Tau,
     check out Vi Hart's video Pi is (still) Wrong(1), and start
     celebrating Tau day(2) by eating twice as much pie!

     在 3.6 版被加入.

 -- 資料: math.inf

     A floating-point positive infinity.  (For negative infinity, use
     ‘-math.inf’.)  Equivalent to the output of ‘float('inf')’.

     在 3.5 版被加入.

 -- 資料: math.nan

     A floating-point "not a number" (NaN) value.  Equivalent to the
     output of ‘float('nan')’.  Due to the requirements of the IEEE-754
     standard(3), ‘math.nan’ and ‘float('nan')’ are not considered to
     equal to any other numeric value, including themselves.  To check
     whether a number is a NaN, use the *note isnan(): 1340. function to
     test for NaNs instead of ‘is’ or ‘==’.  Example:

          >>> import math
          >>> math.nan == math.nan
          False
          >>> float('nan') == float('nan')
          False
          >>> math.isnan(math.nan)
          True
          >>> math.isnan(float('nan'))
          True

     在 3.5 版被加入.

     在 3.11 版的變更: It is now always available.

'CPython 實作細節：' The *note math: 81. module consists mostly of thin
wrappers around the platform C math library functions.  Behavior in
exceptional cases follows Annex F of the C99 standard where appropriate.
The current implementation will raise *note ValueError: 1e7. for invalid
operations like ‘sqrt(-1.0)’ or ‘log(0.0)’ (where C99 Annex F recommends
signaling invalid operation or divide-by-zero), and *note OverflowError:
825. for results that overflow (for example, ‘exp(1000.0)’).  A NaN will
not be returned from any of the functions above unless one or more of
the input arguments was a NaN; in that case, most functions will return
a NaN, but (again following C99 Annex F) there are some exceptions to
this rule, for example ‘pow(float('nan'), 0.0)’ or ‘hypot(float('nan'),
float('inf'))’.

Note that Python makes no effort to distinguish signaling NaNs from
quiet NaNs, and behavior for signaling NaNs remains unspecified.
Typical behavior is to treat all NaNs as though they were quiet.

也參考
......

*note cmath: 11. 模組

     Complex number versions of many of these functions.

   ---------- Footnotes ----------

   (1) https://www.youtube.com/watch?v=jG7vhMMXagQ

   (2) https://tauday.com/

   (3) https://en.wikipedia.org/wiki/IEEE_754


File: python.info,  Node: cmath --- 複數的數學函式,  Next: decimal --- 十進位固定點和浮點運算,  Prev: math --- 數學函式,  Up: 數值與數學模組

5.9.3 ‘cmath’ -- 複數的數學函式
-------------------------------

__________________________________________________________________

本模組提供一些適用於複數的數學函式。本模組中的函式接受整數、浮點數或複數
作為引數。它們也接受任何具有 *note __complex__(): 58d. 或 *note
__float__(): 970. 方法的 Python 物件：這些方法分別用於將物件轉換為複數或
浮點數，然後再將函式應用於轉換後的結果。

     備註: 對於涉及分枝切割 (branch cut) 的函式，我們面臨的問題是決定如
     何定義在切割本身上的這些函式。遵循 Kahan 的論文 "Branch cuts for
     complex elementary functions"，以及 C99 的附錄 G 和後來的 C 標準，
     我們使用零符號來區分分枝切割的兩側：對於沿著（一部分）實數軸的分枝
     切割，我們查看虛部的符號，而對於沿虛軸的分枝切割，我們則查看實部的
     符號。

     例如 *note cmath.sqrt(): 24f7. 函式具有一條沿負實軸的分枝切割。 引
     數 ‘complex(-2.0, -0.0)’ 被視為位於分枝切割 '下方' 處理，因此給出的
     結果在負虛軸上：

          >>> cmath.sqrt(complex(-2.0, -0.0))
          -1.4142135623730951j

     但是引數 ‘complex(-2.0, 0.0)’ 會被當成位於分枝切割上方處理：

          >>> cmath.sqrt(complex(-2.0, 0.0))
          1.4142135623730951j

* Menu:

* 轉換到極座標和從極座標做轉換::
* 冪函數和對數函數::
* 三角函數::
* 雙曲函數::
* 分類函式::
* 常數: 常數<3>.


File: python.info,  Node: 轉換到極座標和從極座標做轉換,  Next: 冪函數和對數函數,  Up: cmath --- 複數的數學函式

5.9.3.1 轉換到極座標和從極座標做轉換
....................................

Python 複數 ‘z’ 是用 '直角坐標' 或 '笛卡爾坐標' 儲存在內部的。它完全是由
其 '實部' ‘z.real’ 和 '虛部' ‘z.imag’ 所決定。

'極座標' 提供了另一種表示複數的方法。在極座標中，複數 'z' 由絕對值
(modulus) 'r' 和相位角 (phase) 'phi' 定義。絕對值 'r' 是從 'z' 到原點的
距離，而相位角 'phi' 是從正 x 軸到連接原點到 'z' 的線段的逆時針角度（以
弧度為單位）。

以下的函式可用於原始直角座標與極座標之間的相互轉換。

 -- 函式: cmath.phase (x)

     以浮點數的形式回傳 'x' 的相位角（也稱為 'x' 的 '引數' ）。
     ‘phase(x)’ 等價於 ‘math.atan2(x.imag, x.real)’。結果將位於 [-'π',
     'π'] 的範圍內，且此操作的分枝切割將位於負實軸上。結果的符號會與
     ‘x.imag’ 的符號相同，即使 ‘x.imag’ 為零：

          >>> phase(complex(-1.0, 0.0))
          3.141592653589793
          >>> phase(complex(-1.0, -0.0))
          -3.141592653589793

     備註: 複數 'x' 的絕對值可以使用內建的 *note abs(): 1ba8. 函式計算。
     沒有單獨的 *note cmath: 11. 模組函式適用於此操作。

 -- 函式: cmath.polar (x)

     回傳 'x' 在極座標中的表達方式。回傳一組數對 ‘(r, phi)’， 'r' 是 'x'
     的絕對值， 'phi' 是 'x' 的相位角。 ‘polar(x)’ 相當於 ‘(abs(x),
     phase(x))’。

 -- 函式: cmath.rect (r, phi)

     透過極座標 'r' 和 'phi' 回傳複數 'x'。相當於 ‘complex(r *
     math.cos(phi), r * math.sin(phi))’。


File: python.info,  Node: 冪函數和對數函數,  Next: 三角函數,  Prev: 轉換到極座標和從極座標做轉換,  Up: cmath --- 複數的數學函式

5.9.3.2 冪函數和對數函數
........................

 -- 函式: cmath.exp (x)

     回傳 'e' 的 'x' 次方，其中 'e' 是自然對數的底數。

 -- 函式: cmath.log (x[, base])

     回傳 'x' 給定 'base' 的對數。如果未指定 'base'，則傳回 'x' 的自然對
     數。存在一條分枝切割，從 0 沿負實數軸到 -∞。

 -- 函式: cmath.log10 (x)

     回傳 'x' 以 10 為底的對數。它與 *note log(): 24fe. 具有相同的分枝切
     割。

 -- 函式: cmath.sqrt (x)

     回傳 'x' 的平方根。它與 *note log(): 24fe. 具有相同的分枝切割。


File: python.info,  Node: 三角函數,  Next: 雙曲函數,  Prev: 冪函數和對數函數,  Up: cmath --- 複數的數學函式

5.9.3.3 三角函數
................

 -- 函式: cmath.acos (x)

     回傳 'x' 的反餘弦值。存在兩條分枝切割：一條是從 1 沿著實數軸向右延
     伸到 ∞。另一條從 -1 沿實數軸向左延伸到 -∞。

 -- 函式: cmath.asin (x)

     回傳 'x' 的反正弦值。它與 *note acos(): 2501. 具有相同的分枝切割。

 -- 函式: cmath.atan (x)

     回傳 'x' 的反正切值。有兩條分枝切割：一條是從 ‘1j’ 沿著虛軸延伸到
     ‘∞j’。另一條從 ‘-1j’ 沿著虛軸延伸到 ‘-∞j’。

 -- 函式: cmath.cos (x)

     回傳 'x' 的餘弦值。

 -- 函式: cmath.sin (x)

     回傳 'x' 的正弦值。

 -- 函式: cmath.tan (x)

     回傳 'x' 的正切值。


File: python.info,  Node: 雙曲函數,  Next: 分類函式,  Prev: 三角函數,  Up: cmath --- 複數的數學函式

5.9.3.4 雙曲函數
................

 -- 函式: cmath.acosh (x)

     回傳 'x' 的反雙曲餘弦值。存在一條分枝切割，從 1 沿實數軸向左延伸到
     -∞。

 -- 函式: cmath.asinh (x)

     回傳 'x' 的反雙曲正弦值。存在兩條分枝切割：一條是從 ‘1j’ 沿著虛軸延
     伸到 ‘∞j’。另一條從 ‘-1j’ 沿著虛軸延伸到 ‘-∞j’。

 -- 函式: cmath.atanh (x)

     回傳 'x' 的反雙曲正切值。存在兩條分枝切割：一條是從 ‘1’ 沿著實數軸
     延伸到 ‘∞’。另一條從 ‘-1’ 沿著實數軸延伸到 ‘-∞’。

 -- 函式: cmath.cosh (x)

     回傳 'x' 的反雙曲餘弦值。

 -- 函式: cmath.sinh (x)

     回傳 'x' 的反雙曲正弦值。

 -- 函式: cmath.tanh (x)

     回傳 'x' 的反雙曲正切值。


File: python.info,  Node: 分類函式,  Next: 常數<3>,  Prev: 雙曲函數,  Up: cmath --- 複數的數學函式

5.9.3.5 分類函式
................

 -- 函式: cmath.isfinite (x)

     如果 'x' 的實部和虛部都是有限的，則回傳 ‘True’，否則回傳 ‘False’。

     在 3.2 版被加入.

 -- 函式: cmath.isinf (x)

     如果 'x' 的實部或虛部是無窮大，則回傳 ‘True’，否則回傳 ‘False’。

 -- 函式: cmath.isnan (x)

     如果 'x' 的實部或虛部為 NaN，則回傳 ‘True’，否則回傳 ‘False’。

 -- 函式: cmath.isclose (a, b, *, rel_tol=1e-09, abs_tol=0.0)

     如果 'a' 和 'b' 的值相互接近，則回傳 ‘True’，否則回傳 ‘False’。

     兩個值是否被認為相互接近是由給定的絕對和相對容許偏差 (tolerance) 所
     決定的。

     'rel_tol' 是相對容許偏差 - 它是 'a' 和 'b' 之間的最大容許偏差值，相
     對於 'a' 或 'b' 的較大絕對值。例如，要設定 5% 的容許偏差，請傳遞
     ‘rel_tol=0.05’。預設容許偏差是 ‘1e-09’，它確保兩個值在大約 9 位十進
     制數字內相同。 'rel_tol' 必須大於零。

     'abs_tol' 是最小絕對容許偏差 - 對於接近零的比較很有用。 'abs_tol' 必
     須至少為零。

     如果未發生錯誤，結果將為： ‘abs(a-b) <= max(rel_tol * max(abs(a),
     abs(b)), abs_tol)’。

     IEEE 754 特殊值 ‘NaN’ 、 ‘inf’ 和 ‘-inf’ 將會根據 IEEE 規則進行處理
     。具體來說， ‘NaN’ 不被認為接近任何其他值，包括 ‘NaN’。 ‘inf’ 和
     ‘-inf’ 只被認為是接近它們自己的。

     在 3.5 版被加入.

     也參考
     ......

     PEP 485(1) - 一個用來測試近似相等的函式

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0485/


File: python.info,  Node: 常數<3>,  Prev: 分類函式,  Up: cmath --- 複數的數學函式

5.9.3.6 常數
............

 -- 資料: cmath.pi

     數學常數 'π'，作為一個浮點數。

 -- 資料: cmath.e

     數學常數 'e'，作為一個浮點數。

 -- 資料: cmath.tau

     數學常數 'τ'，作為一個浮點數。

     在 3.6 版被加入.

 -- 資料: cmath.inf

     正無窮大的浮點數。相當於 ‘float('inf')’。

     在 3.6 版被加入.

 -- 資料: cmath.infj

     實部為零和虛部為正無窮的複數。相當於 ‘complex(0.0, float('inf'))’。

     在 3.6 版被加入.

 -- 資料: cmath.nan

     浮點「非數字」 (NaN) 值。相當於 ‘float('nan')’。

     在 3.6 版被加入.

 -- 資料: cmath.nanj

     實部為零和虛部為 NaN 的複數。相當於 ‘complex(0.0, float('nan'))’。

     在 3.6 版被加入.

請注意，函式的選擇與模組 *note math: 81. 的類似，但並不完全相同。擁有兩
個模組的原因是有些用戶對複數不感興趣，甚至根本就不知道它們是什麼。他們寧
願讓 ‘math.sqrt(-1)’ 引發異常，也不願它回傳複數。另請注意， *note cmath:
11. 中所定義的函式始終都會回傳複數，即使答案可以表示為實數（在這種情況下
，複數的虛部為零）。

關於分枝切割的註釋：它們是沿著給定的不連續函式的曲線。它們是許多複變函數
的必要特徵。假設你需要使用複變函數進行計算，你將會了解分枝切割的概念。請
參閱幾乎所有關於複變函數的（不是太初級的）書籍以獲得啟發。對於如何正確地
基於數值目的選擇分枝切割的相關訊息，以下內容應該是一個很好的參考：

也參考
......

Kahan, W: Branch cuts for complex elementary functions; or, Much ado
about nothing's sign bit.  In Iserles, A., and Powell, M. (eds.), The
state of the art in numerical analysis.  Clarendon Press (1987)
pp165-211.


File: python.info,  Node: decimal --- 十進位固定點和浮點運算,  Next: fractions --- 有理數,  Prev: cmath --- 複數的數學函式,  Up: 數值與數學模組

5.9.4 ‘decimal’ -- 十進位固定點和浮點運算
-----------------------------------------

'原始碼：'Lib/decimal.py(1)

__________________________________________________________________

The *note decimal: 2e. module provides support for fast correctly
rounded decimal floating-point arithmetic.  It offers several advantages
over the *note float: 2c8. datatype:

   * Decimal "is based on a floating-point model which was designed with
     people in mind, and necessarily has a paramount guiding principle -
     computers must provide an arithmetic that works in the same way as
     the arithmetic that people learn at school."  - excerpt from the
     decimal arithmetic specification.

   * Decimal numbers can be represented exactly.  In contrast, numbers
     like ‘1.1’ and ‘2.2’ do not have exact representations in binary
     floating point.  End users typically would not expect ‘1.1 + 2.2’
     to display as ‘3.3000000000000003’ as it does with binary floating
     point.

   * The exactness carries over into arithmetic.  In decimal floating
     point, ‘0.1 + 0.1 + 0.1 - 0.3’ is exactly equal to zero.  In binary
     floating point, the result is ‘5.5511151231257827e-017’.  While
     near to zero, the differences prevent reliable equality testing and
     differences can accumulate.  For this reason, decimal is preferred
     in accounting applications which have strict equality invariants.

   * The decimal module incorporates a notion of significant places so
     that ‘1.30 + 1.20’ is ‘2.50’.  The trailing zero is kept to
     indicate significance.  This is the customary presentation for
     monetary applications.  For multiplication, the "schoolbook"
     approach uses all the figures in the multiplicands.  For instance,
     ‘1.3 * 1.2’ gives ‘1.56’ while ‘1.30 * 1.20’ gives ‘1.5600’.

   * Unlike hardware based binary floating point, the decimal module has
     a user alterable precision (defaulting to 28 places) which can be
     as large as needed for a given problem:

          >>> from decimal import *
          >>> getcontext().prec = 6
          >>> Decimal(1) / Decimal(7)
          Decimal('0.142857')
          >>> getcontext().prec = 28
          >>> Decimal(1) / Decimal(7)
          Decimal('0.1428571428571428571428571429')

   * Both binary and decimal floating point are implemented in terms of
     published standards.  While the built-in float type exposes only a
     modest portion of its capabilities, the decimal module exposes all
     required parts of the standard.  When needed, the programmer has
     full control over rounding and signal handling.  This includes an
     option to enforce exact arithmetic by using exceptions to block any
     inexact operations.

   * The decimal module was designed to support "without prejudice, both
     exact unrounded decimal arithmetic (sometimes called fixed-point
     arithmetic) and rounded floating-point arithmetic."  - excerpt from
     the decimal arithmetic specification.

The module design is centered around three concepts: the decimal number,
the context for arithmetic, and signals.

A decimal number is immutable.  It has a sign, coefficient digits, and
an exponent.  To preserve significance, the coefficient digits do not
truncate trailing zeros.  Decimals also include special values such as
‘Infinity’, ‘-Infinity’, and ‘NaN’.  The standard also differentiates
‘-0’ from ‘+0’.

The context for arithmetic is an environment specifying precision,
rounding rules, limits on exponents, flags indicating the results of
operations, and trap enablers which determine whether signals are
treated as exceptions.  Rounding options include *note ROUND_CEILING:
2517, *note ROUND_DOWN: 2518, *note ROUND_FLOOR: 2519, *note
ROUND_HALF_DOWN: 251a, *note ROUND_HALF_EVEN: 251b, *note ROUND_HALF_UP:
251c, *note ROUND_UP: 251d, and *note ROUND_05UP: 251e.

Signals are groups of exceptional conditions arising during the course
of computation.  Depending on the needs of the application, signals may
be ignored, considered as informational, or treated as exceptions.  The
signals in the decimal module are: *note Clamped: 251f, *note
InvalidOperation: 1044, *note DivisionByZero: 2520, *note Inexact: 2521,
*note Rounded: 2522, *note Subnormal: 2523, *note Overflow: 2524, *note
Underflow: 2525. and *note FloatOperation: 103e.

For each signal there is a flag and a trap enabler.  When a signal is
encountered, its flag is set to one, then, if the trap enabler is set to
one, an exception is raised.  Flags are sticky, so the user needs to
reset them before monitoring a calculation.

也參考
......

   * IBM's General Decimal Arithmetic Specification, The General Decimal
     Arithmetic Specification(2).

* Menu:

* Quick-start Tutorial::
* Decimal objects::
* Context objects::
* 常數: 常數<4>.
* Rounding modes::
* Signals::
* Floating-Point Notes::
* Working with threads::
* Recipes::
* Decimal FAQ::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/decimal.py

   (2) https://speleotrove.com/decimal/decarith.html


File: python.info,  Node: Quick-start Tutorial,  Next: Decimal objects,  Up: decimal --- 十進位固定點和浮點運算

5.9.4.1 Quick-start Tutorial
............................

The usual start to using decimals is importing the module, viewing the
current context with *note getcontext(): 14c6. and, if necessary,
setting new values for precision, rounding, or enabled traps:

     >>> from decimal import *
     >>> getcontext()
     Context(prec=28, rounding=ROUND_HALF_EVEN, Emin=-999999, Emax=999999,
             capitals=1, clamp=0, flags=[], traps=[Overflow, DivisionByZero,
             InvalidOperation])

     >>> getcontext().prec = 7       # Set a new precision

Decimal instances can be constructed from integers, strings, floats, or
tuples.  Construction from an integer or a float performs an exact
conversion of the value of that integer or float.  Decimal numbers
include special values such as ‘NaN’ which stands for "Not a number",
positive and negative ‘Infinity’, and ‘-0’:

     >>> getcontext().prec = 28
     >>> Decimal(10)
     Decimal('10')
     >>> Decimal('3.14')
     Decimal('3.14')
     >>> Decimal(3.14)
     Decimal('3.140000000000000124344978758017532527446746826171875')
     >>> Decimal((0, (3, 1, 4), -2))
     Decimal('3.14')
     >>> Decimal(str(2.0 ** 0.5))
     Decimal('1.4142135623730951')
     >>> Decimal(2) ** Decimal('0.5')
     Decimal('1.414213562373095048801688724')
     >>> Decimal('NaN')
     Decimal('NaN')
     >>> Decimal('-Infinity')
     Decimal('-Infinity')

If the *note FloatOperation: 103e. signal is trapped, accidental mixing
of decimals and floats in constructors or ordering comparisons raises an
exception:

     >>> c = getcontext()
     >>> c.traps[FloatOperation] = True
     >>> Decimal(3.14)
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     decimal.FloatOperation: [<class 'decimal.FloatOperation'>]
     >>> Decimal('3.5') < 3.7
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     decimal.FloatOperation: [<class 'decimal.FloatOperation'>]
     >>> Decimal('3.5') == 3.5
     True

在 3.3 版被加入.

The significance of a new Decimal is determined solely by the number of
digits input.  Context precision and rounding only come into play during
arithmetic operations.

     >>> getcontext().prec = 6
     >>> Decimal('3.0')
     Decimal('3.0')
     >>> Decimal('3.1415926535')
     Decimal('3.1415926535')
     >>> Decimal('3.1415926535') + Decimal('2.7182818285')
     Decimal('5.85987')
     >>> getcontext().rounding = ROUND_UP
     >>> Decimal('3.1415926535') + Decimal('2.7182818285')
     Decimal('5.85988')

If the internal limits of the C version are exceeded, constructing a
decimal raises *note InvalidOperation: 1044.:

     >>> Decimal("1e9999999999999999999")
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     decimal.InvalidOperation: [<class 'decimal.InvalidOperation'>]

在 3.3 版的變更.

Decimals interact well with much of the rest of Python.  Here is a small
decimal floating-point flying circus:

     >>> data = list(map(Decimal, '1.34 1.87 3.45 2.35 1.00 0.03 9.25'.split()))
     >>> max(data)
     Decimal('9.25')
     >>> min(data)
     Decimal('0.03')
     >>> sorted(data)
     [Decimal('0.03'), Decimal('1.00'), Decimal('1.34'), Decimal('1.87'),
      Decimal('2.35'), Decimal('3.45'), Decimal('9.25')]
     >>> sum(data)
     Decimal('19.29')
     >>> a,b,c = data[:3]
     >>> str(a)
     '1.34'
     >>> float(a)
     1.34
     >>> round(a, 1)
     Decimal('1.3')
     >>> int(a)
     1
     >>> a * 5
     Decimal('6.70')
     >>> a * b
     Decimal('2.5058')
     >>> c % a
     Decimal('0.77')

And some mathematical functions are also available to Decimal:

     >>> getcontext().prec = 28
     >>> Decimal(2).sqrt()
     Decimal('1.414213562373095048801688724')
     >>> Decimal(1).exp()
     Decimal('2.718281828459045235360287471')
     >>> Decimal('10').ln()
     Decimal('2.302585092994045684017991455')
     >>> Decimal('10').log10()
     Decimal('1')

The *note quantize(): 104a. method rounds a number to a fixed exponent.
This method is useful for monetary applications that often round results
to a fixed number of places:

     >>> Decimal('7.325').quantize(Decimal('.01'), rounding=ROUND_DOWN)
     Decimal('7.32')
     >>> Decimal('7.325').quantize(Decimal('1.'), rounding=ROUND_UP)
     Decimal('8')

As shown above, the *note getcontext(): 14c6. function accesses the
current context and allows the settings to be changed.  This approach
meets the needs of most applications.

For more advanced work, it may be useful to create alternate contexts
using the Context() constructor.  To make an alternate active, use the
*note setcontext(): 2528. function.

In accordance with the standard, the *note decimal: 2e. module provides
two ready to use standard contexts, *note BasicContext: 1042. and *note
ExtendedContext: 1043.  The former is especially useful for debugging
because many of the traps are enabled:

     >>> myothercontext = Context(prec=60, rounding=ROUND_HALF_DOWN)
     >>> setcontext(myothercontext)
     >>> Decimal(1) / Decimal(7)
     Decimal('0.142857142857142857142857142857142857142857142857142857142857')

     >>> ExtendedContext
     Context(prec=9, rounding=ROUND_HALF_EVEN, Emin=-999999, Emax=999999,
             capitals=1, clamp=0, flags=[], traps=[])
     >>> setcontext(ExtendedContext)
     >>> Decimal(1) / Decimal(7)
     Decimal('0.142857143')
     >>> Decimal(42) / Decimal(0)
     Decimal('Infinity')

     >>> setcontext(BasicContext)
     >>> Decimal(42) / Decimal(0)
     Traceback (most recent call last):
       File "<pyshell#143>", line 1, in -toplevel-
         Decimal(42) / Decimal(0)
     DivisionByZero: x / 0

Contexts also have signal flags for monitoring exceptional conditions
encountered during computations.  The flags remain set until explicitly
cleared, so it is best to clear the flags before each set of monitored
computations by using the *note clear_flags(): 2529. method.

     >>> setcontext(ExtendedContext)
     >>> getcontext().clear_flags()
     >>> Decimal(355) / Decimal(113)
     Decimal('3.14159292')
     >>> getcontext()
     Context(prec=9, rounding=ROUND_HALF_EVEN, Emin=-999999, Emax=999999,
             capitals=1, clamp=0, flags=[Inexact, Rounded], traps=[])

The 'flags' entry shows that the rational approximation to pi was
rounded (digits beyond the context precision were thrown away) and that
the result is inexact (some of the discarded digits were non-zero).

Individual traps are set using the dictionary in the ‘traps’ attribute
of a context:

     >>> setcontext(ExtendedContext)
     >>> Decimal(1) / Decimal(0)
     Decimal('Infinity')
     >>> getcontext().traps[DivisionByZero] = 1
     >>> Decimal(1) / Decimal(0)
     Traceback (most recent call last):
       File "<pyshell#112>", line 1, in -toplevel-
         Decimal(1) / Decimal(0)
     DivisionByZero: x / 0

Most programs adjust the current context only once, at the beginning of
the program.  And, in many applications, data is converted to *note
Decimal: 27c. with a single cast inside a loop.  With context set and
decimals created, the bulk of the program manipulates the data no
differently than with other Python numeric types.


File: python.info,  Node: Decimal objects,  Next: Context objects,  Prev: Quick-start Tutorial,  Up: decimal --- 十進位固定點和浮點運算

5.9.4.2 Decimal objects
.......................

 -- 類別: decimal.Decimal (value='0', context=None)

     Construct a new *note Decimal: 27c. object based from 'value'.

     'value' can be an integer, string, tuple, *note float: 2c8, or
     another *note Decimal: 27c. object.  If no 'value' is given,
     returns ‘Decimal('0')’.  If 'value' is a string, it should conform
     to the decimal numeric string syntax after leading and trailing
     whitespace characters, as well as underscores throughout, are
     removed:

          sign           ::=  '+' | '-'
          digit          ::=  '0' | '1' | '2' | '3' | '4' | '5' | '6' | '7' | '8' | '9'
          indicator      ::=  'e' | 'E'
          digits         ::=  digit [digit]...
          decimal-part   ::=  digits '.' [digits] | ['.'] digits
          exponent-part  ::=  indicator [sign] digits
          infinity       ::=  'Infinity' | 'Inf'
          nan            ::=  'NaN' [digits] | 'sNaN' [digits]
          numeric-value  ::=  decimal-part [exponent-part] | infinity
          numeric-string ::=  [sign] numeric-value | [sign] nan

     Other Unicode decimal digits are also permitted where ‘digit’
     appears above.  These include decimal digits from various other
     alphabets (for example, Arabic-Indic and Devanāgarī digits) along
     with the fullwidth digits ‘'\uff10'’ through ‘'\uff19'’.

     If 'value' is a *note tuple: 322, it should have three components,
     a sign (‘0’ for positive or ‘1’ for negative), a *note tuple: 322.
     of digits, and an integer exponent.  For example, ‘Decimal((0, (1,
     4, 1, 4), -3))’ returns ‘Decimal('1.414')’.

     If 'value' is a *note float: 2c8, the binary floating-point value
     is losslessly converted to its exact decimal equivalent.  This
     conversion can often require 53 or more digits of precision.  For
     example, ‘Decimal(float('1.1'))’ converts to
     ‘Decimal('1.100000000000000088817841970012523233890533447265625')’.

     The 'context' precision does not affect how many digits are stored.
     That is determined exclusively by the number of digits in 'value'.
     For example, ‘Decimal('3.00000')’ records all five zeros even if
     the context precision is only three.

     The purpose of the 'context' argument is determining what to do if
     'value' is a malformed string.  If the context traps *note
     InvalidOperation: 1044, an exception is raised; otherwise, the
     constructor returns a new Decimal with the value of ‘NaN’.

     Once constructed, *note Decimal: 27c. objects are immutable.

     在 3.2 版的變更: The argument to the constructor is now permitted
     to be a *note float: 2c8. instance.

     在 3.3 版的變更: *note float: 2c8. arguments raise an exception if
     the *note FloatOperation: 103e. trap is set.  By default the trap
     is off.

     在 3.6 版的變更: Underscores are allowed for grouping, as with
     integral and floating-point literals in code.

     Decimal floating-point objects share many properties with the other
     built-in numeric types such as *note float: 2c8. and *note int:
     23c.  All of the usual math operations and special methods apply.
     Likewise, decimal objects can be copied, pickled, printed, used as
     dictionary keys, used as set elements, compared, sorted, and
     coerced to another type (such as *note float: 2c8. or *note int:
     23c.).

     There are some small differences between arithmetic on Decimal
     objects and arithmetic on integers and floats.  When the remainder
     operator ‘%’ is applied to Decimal objects, the sign of the result
     is the sign of the 'dividend' rather than the sign of the divisor:

          >>> (-7) % 4
          1
          >>> Decimal(-7) % Decimal(4)
          Decimal('-3')

     The integer division operator ‘//’ behaves analogously, returning
     the integer part of the true quotient (truncating towards zero)
     rather than its floor, so as to preserve the usual identity ‘x ==
     (x // y) * y + x % y’:

          >>> -7 // 4
          -2
          >>> Decimal(-7) // Decimal(4)
          Decimal('-1')

     The ‘%’ and ‘//’ operators implement the ‘remainder’ and
     ‘divide-integer’ operations (respectively) as described in the
     specification.

     Decimal objects cannot generally be combined with floats or
     instances of *note fractions.Fraction: 1c7. in arithmetic
     operations: an attempt to add a *note Decimal: 27c. to a *note
     float: 2c8, for example, will raise a *note TypeError: 4dd.
     However, it is possible to use Python's comparison operators to
     compare a *note Decimal: 27c. instance ‘x’ with another number ‘y’.
     This avoids confusing results when doing equality comparisons
     between numbers of different types.

     在 3.2 版的變更: Mixed-type comparisons between *note Decimal: 27c.
     instances and other numeric types are now fully supported.

     In addition to the standard numeric properties, decimal
     floating-point objects also have a number of specialized methods:

      -- 方法: adjusted ()

          Return the adjusted exponent after shifting out the
          coefficient's rightmost digits until only the lead digit
          remains: ‘Decimal('321e+5').adjusted()’ returns seven.  Used
          for determining the position of the most significant digit
          with respect to the decimal point.

      -- 方法: as_integer_ratio ()

          Return a pair ‘(n, d)’ of integers that represent the given
          *note Decimal: 27c. instance as a fraction, in lowest terms
          and with a positive denominator:

               >>> Decimal('-3.14').as_integer_ratio()
               (-157, 50)

          The conversion is exact.  Raise OverflowError on infinities
          and ValueError on NaNs.

     在 3.6 版被加入.

      -- 方法: as_tuple ()

          Return a *note named tuple: 5f4. representation of the number:
          ‘DecimalTuple(sign, digits, exponent)’.

      -- 方法: canonical ()

          Return the canonical encoding of the argument.  Currently, the
          encoding of a *note Decimal: 27c. instance is always
          canonical, so this operation returns its argument unchanged.

      -- 方法: compare (other, context=None)

          Compare the values of two Decimal instances.  *note compare():
          252f. returns a Decimal instance, and if either operand is a
          NaN then the result is a NaN:

               a or b is a NaN  ==> Decimal('NaN')
               a < b            ==> Decimal('-1')
               a == b           ==> Decimal('0')
               a > b            ==> Decimal('1')

      -- 方法: compare_signal (other, context=None)

          This operation is identical to the *note compare(): 252f.
          method, except that all NaNs signal.  That is, if neither
          operand is a signaling NaN then any quiet NaN operand is
          treated as though it were a signaling NaN.

      -- 方法: compare_total (other, context=None)

          Compare two operands using their abstract representation
          rather than their numerical value.  Similar to the *note
          compare(): 252f. method, but the result gives a total ordering
          on *note Decimal: 27c. instances.  Two *note Decimal: 27c.
          instances with the same numeric value but different
          representations compare unequal in this ordering:

               >>> Decimal('12.0').compare_total(Decimal('12'))
               Decimal('-1')

          Quiet and signaling NaNs are also included in the total
          ordering.  The result of this function is ‘Decimal('0')’ if
          both operands have the same representation, ‘Decimal('-1')’ if
          the first operand is lower in the total order than the second,
          and ‘Decimal('1')’ if the first operand is higher in the total
          order than the second operand.  See the specification for
          details of the total order.

          This operation is unaffected by context and is quiet: no flags
          are changed and no rounding is performed.  As an exception,
          the C version may raise InvalidOperation if the second operand
          cannot be converted exactly.

      -- 方法: compare_total_mag (other, context=None)

          Compare two operands using their abstract representation
          rather than their value as in *note compare_total(): 2531, but
          ignoring the sign of each operand.  ‘x.compare_total_mag(y)’
          is equivalent to ‘x.copy_abs().compare_total(y.copy_abs())’.

          This operation is unaffected by context and is quiet: no flags
          are changed and no rounding is performed.  As an exception,
          the C version may raise InvalidOperation if the second operand
          cannot be converted exactly.

      -- 方法: conjugate ()

          Just returns self, this method is only to comply with the
          Decimal Specification.

      -- 方法: copy_abs ()

          Return the absolute value of the argument.  This operation is
          unaffected by the context and is quiet: no flags are changed
          and no rounding is performed.

      -- 方法: copy_negate ()

          Return the negation of the argument.  This operation is
          unaffected by the context and is quiet: no flags are changed
          and no rounding is performed.

      -- 方法: copy_sign (other, context=None)

          Return a copy of the first operand with the sign set to be the
          same as the sign of the second operand.  For example:

               >>> Decimal('2.3').copy_sign(Decimal('-1.5'))
               Decimal('-2.3')

          This operation is unaffected by context and is quiet: no flags
          are changed and no rounding is performed.  As an exception,
          the C version may raise InvalidOperation if the second operand
          cannot be converted exactly.

      -- 方法: exp (context=None)

          Return the value of the (natural) exponential function ‘e**x’
          at the given number.  The result is correctly rounded using
          the *note ROUND_HALF_EVEN: 251b. rounding mode.

               >>> Decimal(1).exp()
               Decimal('2.718281828459045235360287471')
               >>> Decimal(321).exp()
               Decimal('2.561702493119680037517373933E+139')

      -- 方法: classmethod from_float (f)

          Alternative constructor that only accepts instances of *note
          float: 2c8. or *note int: 23c.

          Note ‘Decimal.from_float(0.1)’ is not the same as
          ‘Decimal('0.1')’.  Since 0.1 is not exactly representable in
          binary floating point, the value is stored as the nearest
          representable value which is ‘0x1.999999999999ap-4’.  That
          equivalent value in decimal is
          ‘0.1000000000000000055511151231257827021181583404541015625’.

               備註: From Python 3.2 onwards, a *note Decimal: 27c.
               instance can also be constructed directly from a *note
               float: 2c8.

               >>> Decimal.from_float(0.1)
               Decimal('0.1000000000000000055511151231257827021181583404541015625')
               >>> Decimal.from_float(float('nan'))
               Decimal('NaN')
               >>> Decimal.from_float(float('inf'))
               Decimal('Infinity')
               >>> Decimal.from_float(float('-inf'))
               Decimal('-Infinity')

          在 3.1 版被加入.

      -- 方法: fma (other, third, context=None)

          Fused multiply-add.  Return self*other+third with no rounding
          of the intermediate product self*other.

               >>> Decimal(2).fma(3, 5)
               Decimal('11')

      -- 方法: is_canonical ()

          Return *note True: bb4. if the argument is canonical and *note
          False: adb. otherwise.  Currently, a *note Decimal: 27c.
          instance is always canonical, so this operation always returns
          *note True: bb4.

      -- 方法: is_finite ()

          Return *note True: bb4. if the argument is a finite number,
          and *note False: adb. if the argument is an infinity or a NaN.

      -- 方法: is_infinite ()

          Return *note True: bb4. if the argument is either positive or
          negative infinity and *note False: adb. otherwise.

      -- 方法: is_nan ()

          Return *note True: bb4. if the argument is a (quiet or
          signaling) NaN and *note False: adb. otherwise.

      -- 方法: is_normal (context=None)

          Return *note True: bb4. if the argument is a 'normal' finite
          number.  Return *note False: adb. if the argument is zero,
          subnormal, infinite or a NaN.

      -- 方法: is_qnan ()

          Return *note True: bb4. if the argument is a quiet NaN, and
          *note False: adb. otherwise.

      -- 方法: is_signed ()

          Return *note True: bb4. if the argument has a negative sign
          and *note False: adb. otherwise.  Note that zeros and NaNs can
          both carry signs.

      -- 方法: is_snan ()

          Return *note True: bb4. if the argument is a signaling NaN and
          *note False: adb. otherwise.

      -- 方法: is_subnormal (context=None)

          Return *note True: bb4. if the argument is subnormal, and
          *note False: adb. otherwise.

      -- 方法: is_zero ()

          Return *note True: bb4. if the argument is a (positive or
          negative) zero and *note False: adb. otherwise.

      -- 方法: ln (context=None)

          Return the natural (base e) logarithm of the operand.  The
          result is correctly rounded using the *note ROUND_HALF_EVEN:
          251b. rounding mode.

      -- 方法: log10 (context=None)

          Return the base ten logarithm of the operand.  The result is
          correctly rounded using the *note ROUND_HALF_EVEN: 251b.
          rounding mode.

      -- 方法: logb (context=None)

          For a nonzero number, return the adjusted exponent of its
          operand as a *note Decimal: 27c. instance.  If the operand is
          a zero then ‘Decimal('-Infinity')’ is returned and the *note
          DivisionByZero: 2520. flag is raised.  If the operand is an
          infinity then ‘Decimal('Infinity')’ is returned.

      -- 方法: logical_and (other, context=None)

          *note logical_and(): 2544. is a logical operation which takes
          two 'logical operands' (see *note Logical operands: 2545.).
          The result is the digit-wise ‘and’ of the two operands.

      -- 方法: logical_invert (context=None)

          *note logical_invert(): 2546. is a logical operation.  The
          result is the digit-wise inversion of the operand.

      -- 方法: logical_or (other, context=None)

          *note logical_or(): 2547. is a logical operation which takes
          two 'logical operands' (see *note Logical operands: 2545.).
          The result is the digit-wise ‘or’ of the two operands.

      -- 方法: logical_xor (other, context=None)

          *note logical_xor(): 2548. is a logical operation which takes
          two 'logical operands' (see *note Logical operands: 2545.).
          The result is the digit-wise exclusive or of the two operands.

      -- 方法: max (other, context=None)

          Like ‘max(self, other)’ except that the context rounding rule
          is applied before returning and that ‘NaN’ values are either
          signaled or ignored (depending on the context and whether they
          are signaling or quiet).

      -- 方法: max_mag (other, context=None)

          Similar to the *note max(): 2549. method, but the comparison
          is done using the absolute values of the operands.

      -- 方法: min (other, context=None)

          Like ‘min(self, other)’ except that the context rounding rule
          is applied before returning and that ‘NaN’ values are either
          signaled or ignored (depending on the context and whether they
          are signaling or quiet).

      -- 方法: min_mag (other, context=None)

          Similar to the *note min(): 254b. method, but the comparison
          is done using the absolute values of the operands.

      -- 方法: next_minus (context=None)

          Return the largest number representable in the given context
          (or in the current thread's context if no context is given)
          that is smaller than the given operand.

      -- 方法: next_plus (context=None)

          Return the smallest number representable in the given context
          (or in the current thread's context if no context is given)
          that is larger than the given operand.

      -- 方法: next_toward (other, context=None)

          If the two operands are unequal, return the number closest to
          the first operand in the direction of the second operand.  If
          both operands are numerically equal, return a copy of the
          first operand with the sign set to be the same as the sign of
          the second operand.

      -- 方法: normalize (context=None)

          Used for producing canonical values of an equivalence class
          within either the current context or the specified context.

          This has the same semantics as the unary plus operation,
          except that if the final result is finite it is reduced to its
          simplest form, with all trailing zeros removed and its sign
          preserved.  That is, while the coefficient is non-zero and a
          multiple of ten the coefficient is divided by ten and the
          exponent is incremented by 1.  Otherwise (the coefficient is
          zero) the exponent is set to 0.  In all cases the sign is
          unchanged.

          For example, ‘Decimal('32.100')’ and ‘Decimal('0.321000e+2')’
          both normalize to the equivalent value ‘Decimal('32.1')’.

          Note that rounding is applied 'before' reducing to simplest
          form.

          In the latest versions of the specification, this operation is
          also known as ‘reduce’.

      -- 方法: number_class (context=None)

          Return a string describing the 'class' of the operand.  The
          returned value is one of the following ten strings.

             * ‘"-Infinity"’, indicating that the operand is negative
               infinity.

             * ‘"-Normal"’, indicating that the operand is a negative
               normal number.

             * ‘"-Subnormal"’, indicating that the operand is negative
               and subnormal.

             * ‘"-Zero"’, indicating that the operand is a negative
               zero.

             * ‘"+Zero"’, indicating that the operand is a positive
               zero.

             * ‘"+Subnormal"’, indicating that the operand is positive
               and subnormal.

             * ‘"+Normal"’, indicating that the operand is a positive
               normal number.

             * ‘"+Infinity"’, indicating that the operand is positive
               infinity.

             * ‘"NaN"’, indicating that the operand is a quiet NaN (Not
               a Number).

             * ‘"sNaN"’, indicating that the operand is a signaling NaN.

      -- 方法: quantize (exp, rounding=None, context=None)

          Return a value equal to the first operand after rounding and
          having the exponent of the second operand.

               >>> Decimal('1.41421356').quantize(Decimal('1.000'))
               Decimal('1.414')

          Unlike other operations, if the length of the coefficient
          after the quantize operation would be greater than precision,
          then an *note InvalidOperation: 1044. is signaled.  This
          guarantees that, unless there is an error condition, the
          quantized exponent is always equal to that of the right-hand
          operand.

          Also unlike other operations, quantize never signals
          Underflow, even if the result is subnormal and inexact.

          If the exponent of the second operand is larger than that of
          the first then rounding may be necessary.  In this case, the
          rounding mode is determined by the ‘rounding’ argument if
          given, else by the given ‘context’ argument; if neither
          argument is given the rounding mode of the current thread's
          context is used.

          An error is returned whenever the resulting exponent is
          greater than ‘Emax’ or less than *note Etiny(): 2552.

      -- 方法: radix ()

          Return ‘Decimal(10)’, the radix (base) in which the *note
          Decimal: 27c. class does all its arithmetic.  Included for
          compatibility with the specification.

      -- 方法: remainder_near (other, context=None)

          Return the remainder from dividing 'self' by 'other'.  This
          differs from ‘self % other’ in that the sign of the remainder
          is chosen so as to minimize its absolute value.  More
          precisely, the return value is ‘self - n * other’ where ‘n’ is
          the integer nearest to the exact value of ‘self / other’, and
          if two integers are equally near then the even one is chosen.

          If the result is zero then its sign will be the sign of
          'self'.

               >>> Decimal(18).remainder_near(Decimal(10))
               Decimal('-2')
               >>> Decimal(25).remainder_near(Decimal(10))
               Decimal('5')
               >>> Decimal(35).remainder_near(Decimal(10))
               Decimal('-5')

      -- 方法: rotate (other, context=None)

          Return the result of rotating the digits of the first operand
          by an amount specified by the second operand.  The second
          operand must be an integer in the range -precision through
          precision.  The absolute value of the second operand gives the
          number of places to rotate.  If the second operand is positive
          then rotation is to the left; otherwise rotation is to the
          right.  The coefficient of the first operand is padded on the
          left with zeros to length precision if necessary.  The sign
          and exponent of the first operand are unchanged.

      -- 方法: same_quantum (other, context=None)

          Test whether self and other have the same exponent or whether
          both are ‘NaN’.

          This operation is unaffected by context and is quiet: no flags
          are changed and no rounding is performed.  As an exception,
          the C version may raise InvalidOperation if the second operand
          cannot be converted exactly.

      -- 方法: scaleb (other, context=None)

          Return the first operand with exponent adjusted by the second.
          Equivalently, return the first operand multiplied by
          ‘10**other’.  The second operand must be an integer.

      -- 方法: shift (other, context=None)

          Return the result of shifting the digits of the first operand
          by an amount specified by the second operand.  The second
          operand must be an integer in the range -precision through
          precision.  The absolute value of the second operand gives the
          number of places to shift.  If the second operand is positive
          then the shift is to the left; otherwise the shift is to the
          right.  Digits shifted into the coefficient are zeros.  The
          sign and exponent of the first operand are unchanged.

      -- 方法: sqrt (context=None)

          Return the square root of the argument to full precision.

      -- 方法: to_eng_string (context=None)

          Convert to a string, using engineering notation if an exponent
          is needed.

          Engineering notation has an exponent which is a multiple of 3.
          This can leave up to 3 digits to the left of the decimal place
          and may require the addition of either one or two trailing
          zeros.

          For example, this converts ‘Decimal('123E+1')’ to
          ‘Decimal('1.23E+3')’.

      -- 方法: to_integral (rounding=None, context=None)

          Identical to the *note to_integral_value(): 255c. method.  The
          ‘to_integral’ name has been kept for compatibility with older
          versions.

      -- 方法: to_integral_exact (rounding=None, context=None)

          Round to the nearest integer, signaling *note Inexact: 2521.
          or *note Rounded: 2522. as appropriate if rounding occurs.
          The rounding mode is determined by the ‘rounding’ parameter if
          given, else by the given ‘context’.  If neither parameter is
          given then the rounding mode of the current context is used.

      -- 方法: to_integral_value (rounding=None, context=None)

          Round to the nearest integer without signaling *note Inexact:
          2521. or *note Rounded: 2522.  If given, applies 'rounding';
          otherwise, uses the rounding method in either the supplied
          'context' or the current context.

     Decimal numbers can be rounded using the *note round(): 126d.
     function:

      -- Describe: round(number)

      -- Describe: round(number, ndigits)

          If 'ndigits' is not given or ‘None’, returns the nearest *note
          int: 23c. to 'number', rounding ties to even, and ignoring the
          rounding mode of the *note Decimal: 27c. context.  Raises
          *note OverflowError: 825. if 'number' is an infinity or *note
          ValueError: 1e7. if it is a (quiet or signaling) NaN.

          If 'ndigits' is an *note int: 23c, the context's rounding mode
          is respected and a *note Decimal: 27c. representing 'number'
          rounded to the nearest multiple of ‘Decimal('1E-ndigits')’ is
          returned; in this case, ‘round(number, ndigits)’ is equivalent
          to ‘self.quantize(Decimal('1E-ndigits'))’.  Returns
          ‘Decimal('NaN')’ if 'number' is a quiet NaN. Raises *note
          InvalidOperation: 1044. if 'number' is an infinity, a
          signaling NaN, or if the length of the coefficient after the
          quantize operation would be greater than the current context's
          precision.  In other words, for the non-corner cases:

             * if 'ndigits' is positive, return 'number' rounded to
               'ndigits' decimal places;

             * if 'ndigits' is zero, return 'number' rounded to the
               nearest integer;

             * if 'ndigits' is negative, return 'number' rounded to the
               nearest multiple of ‘10**abs(ndigits)’.

          For example:

               >>> from decimal import Decimal, getcontext, ROUND_DOWN
               >>> getcontext().rounding = ROUND_DOWN
               >>> round(Decimal('3.75'))     # context rounding ignored
               4
               >>> round(Decimal('3.5'))      # round-ties-to-even
               4
               >>> round(Decimal('3.75'), 0)  # uses the context rounding
               Decimal('3')
               >>> round(Decimal('3.75'), 1)
               Decimal('3.7')
               >>> round(Decimal('3.75'), -1)
               Decimal('0E+1')

* Menu:

* Logical operands::


File: python.info,  Node: Logical operands,  Up: Decimal objects

5.9.4.3 Logical operands
........................

The *note logical_and(): 2544, *note logical_invert(): 2546, *note
logical_or(): 2547, and *note logical_xor(): 2548. methods expect their
arguments to be 'logical operands'.  A 'logical operand' is a *note
Decimal: 27c. instance whose exponent and sign are both zero, and whose
digits are all either ‘0’ or ‘1’.


File: python.info,  Node: Context objects,  Next: 常數<4>,  Prev: Decimal objects,  Up: decimal --- 十進位固定點和浮點運算

5.9.4.4 Context objects
.......................

Contexts are environments for arithmetic operations.  They govern
precision, set rules for rounding, determine which signals are treated
as exceptions, and limit the range for exponents.

Each thread has its own current context which is accessed or changed
using the *note getcontext(): 14c6. and *note setcontext(): 2528.
functions:

 -- 函式: decimal.getcontext ()

     Return the current context for the active thread.

 -- 函式: decimal.setcontext (c)

     Set the current context for the active thread to 'c'.

You can also use the *note with: 577. statement and the *note
localcontext(): 1709. function to temporarily change the active context.

 -- 函式: decimal.localcontext (ctx=None, **kwargs)

     Return a context manager that will set the current context for the
     active thread to a copy of 'ctx' on entry to the with-statement and
     restore the previous context when exiting the with-statement.  If
     no context is specified, a copy of the current context is used.
     The 'kwargs' argument is used to set the attributes of the new
     context.

     For example, the following code sets the current decimal precision
     to 42 places, performs a calculation, and then automatically
     restores the previous context:

          from decimal import localcontext

          with localcontext() as ctx:
              ctx.prec = 42   # Perform a high precision calculation
              s = calculate_something()
          s = +s  # Round the final result back to the default precision

     Using keyword arguments, the code would be the following:

          from decimal import localcontext

          with localcontext(prec=42) as ctx:
              s = calculate_something()
          s = +s

     Raises *note TypeError: 4dd. if 'kwargs' supplies an attribute that
     *note Context: 1049. doesn't support.  Raises either *note
     TypeError: 4dd. or *note ValueError: 1e7. if 'kwargs' supplies an
     invalid value for an attribute.

     在 3.11 版的變更: *note localcontext(): 1709. now supports setting
     context attributes through the use of keyword arguments.

New contexts can also be created using the *note Context: 1049.
constructor described below.  In addition, the module provides three
pre-made contexts:

 -- 類別: decimal.BasicContext

     This is a standard context defined by the General Decimal
     Arithmetic Specification.  Precision is set to nine.  Rounding is
     set to *note ROUND_HALF_UP: 251c.  All flags are cleared.  All
     traps are enabled (treated as exceptions) except *note Inexact:
     2521, *note Rounded: 2522, and *note Subnormal: 2523.

     Because many of the traps are enabled, this context is useful for
     debugging.

 -- 類別: decimal.ExtendedContext

     This is a standard context defined by the General Decimal
     Arithmetic Specification.  Precision is set to nine.  Rounding is
     set to *note ROUND_HALF_EVEN: 251b.  All flags are cleared.  No
     traps are enabled (so that exceptions are not raised during
     computations).

     Because the traps are disabled, this context is useful for
     applications that prefer to have result value of ‘NaN’ or
     ‘Infinity’ instead of raising exceptions.  This allows an
     application to complete a run in the presence of conditions that
     would otherwise halt the program.

 -- 類別: decimal.DefaultContext

     This context is used by the *note Context: 1049. constructor as a
     prototype for new contexts.  Changing a field (such a precision)
     has the effect of changing the default for new contexts created by
     the *note Context: 1049. constructor.

     This context is most useful in multi-threaded environments.
     Changing one of the fields before threads are started has the
     effect of setting system-wide defaults.  Changing the fields after
     threads have started is not recommended as it would require thread
     synchronization to prevent race conditions.

     In single threaded environments, it is preferable to not use this
     context at all.  Instead, simply create contexts explicitly as
     described below.

     The default values are ‘Context.prec’=‘28’,
     ‘Context.rounding’=*note ROUND_HALF_EVEN: 251b, and enabled traps
     for *note Overflow: 2524, *note InvalidOperation: 1044, and *note
     DivisionByZero: 2520.

In addition to the three supplied contexts, new contexts can be created
with the *note Context: 1049. constructor.

 -- 類別: decimal.Context (prec=None, rounding=None, Emin=None,
          Emax=None, capitals=None, clamp=None, flags=None, traps=None)

     Creates a new context.  If a field is not specified or is *note
     None: 61b, the default values are copied from the *note
     DefaultContext: 1041.  If the 'flags' field is not specified or is
     *note None: 61b, all flags are cleared.

     'prec' is an integer in the range [‘1’, *note MAX_PREC: 2561.] that
     sets the precision for arithmetic operations in the context.

     The 'rounding' option is one of the constants listed in the section
     *note Rounding Modes: 2562.

     The 'traps' and 'flags' fields list any signals to be set.
     Generally, new contexts should only set traps and leave the flags
     clear.

     The 'Emin' and 'Emax' fields are integers specifying the outer
     limits allowable for exponents.  'Emin' must be in the range [*note
     MIN_EMIN: 2563, ‘0’], 'Emax' in the range [‘0’, *note MAX_EMAX:
     2564.].

     The 'capitals' field is either ‘0’ or ‘1’ (the default).  If set to
     ‘1’, exponents are printed with a capital ‘E’; otherwise, a
     lowercase ‘e’ is used: ‘Decimal('6.02e+23')’.

     The 'clamp' field is either ‘0’ (the default) or ‘1’.  If set to
     ‘1’, the exponent ‘e’ of a *note Decimal: 27c. instance
     representable in this context is strictly limited to the range
     ‘Emin - prec + 1 <= e <= Emax - prec + 1’.  If 'clamp' is ‘0’ then
     a weaker condition holds: the adjusted exponent of the *note
     Decimal: 27c. instance is at most ‘Emax’.  When 'clamp' is ‘1’, a
     large normal number will, where possible, have its exponent reduced
     and a corresponding number of zeros added to its coefficient, in
     order to fit the exponent constraints; this preserves the value of
     the number but loses information about significant trailing zeros.
     For example:

          >>> Context(prec=6, Emax=999, clamp=1).create_decimal('1.23e999')
          Decimal('1.23000E+999')

     A 'clamp' value of ‘1’ allows compatibility with the fixed-width
     decimal interchange formats specified in IEEE 754.

     The *note Context: 1049. class defines several general purpose
     methods as well as a large number of methods for doing arithmetic
     directly in a given context.  In addition, for each of the *note
     Decimal: 27c. methods described above (with the exception of the
     *note adjusted(): 252c. and *note as_tuple(): 252d. methods) there
     is a corresponding *note Context: 1049. method.  For example, for a
     *note Context: 1049. instance ‘C’ and *note Decimal: 27c. instance
     ‘x’, ‘C.exp(x)’ is equivalent to ‘x.exp(context=C)’.  Each *note
     Context: 1049. method accepts a Python integer (an instance of
     *note int: 23c.) anywhere that a Decimal instance is accepted.

      -- 方法: clear_flags ()

          Resets all of the flags to ‘0’.

      -- 方法: clear_traps ()

          Resets all of the traps to ‘0’.

          在 3.3 版被加入.

      -- 方法: copy ()

          Return a duplicate of the context.

      -- 方法: copy_decimal (num)

          Return a copy of the Decimal instance num.

      -- 方法: create_decimal (num)

          Creates a new Decimal instance from 'num' but using 'self' as
          context.  Unlike the *note Decimal: 27c. constructor, the
          context precision, rounding method, flags, and traps are
          applied to the conversion.

          This is useful because constants are often given to a greater
          precision than is needed by the application.  Another benefit
          is that rounding immediately eliminates unintended effects
          from digits beyond the current precision.  In the following
          example, using unrounded inputs means that adding zero to a
          sum can change the result:

               >>> getcontext().prec = 3
               >>> Decimal('3.4445') + Decimal('1.0023')
               Decimal('4.45')
               >>> Decimal('3.4445') + Decimal(0) + Decimal('1.0023')
               Decimal('4.44')

          This method implements the to-number operation of the IBM
          specification.  If the argument is a string, no leading or
          trailing whitespace or underscores are permitted.

      -- 方法: create_decimal_from_float (f)

          Creates a new Decimal instance from a float 'f' but rounding
          using 'self' as the context.  Unlike the *note
          Decimal.from_float(): 119c. class method, the context
          precision, rounding method, flags, and traps are applied to
          the conversion.

               >>> context = Context(prec=5, rounding=ROUND_DOWN)
               >>> context.create_decimal_from_float(math.pi)
               Decimal('3.1415')
               >>> context = Context(prec=5, traps=[Inexact])
               >>> context.create_decimal_from_float(math.pi)
               Traceback (most recent call last):
                   ...
               decimal.Inexact: None

          在 3.1 版被加入.

      -- 方法: Etiny ()

          Returns a value equal to ‘Emin - prec + 1’ which is the
          minimum exponent value for subnormal results.  When underflow
          occurs, the exponent is set to *note Etiny: 2552.

      -- 方法: Etop ()

          Returns a value equal to ‘Emax - prec + 1’.

     The usual approach to working with decimals is to create *note
     Decimal: 27c. instances and then apply arithmetic operations which
     take place within the current context for the active thread.  An
     alternative approach is to use context methods for calculating
     within a specific context.  The methods are similar to those for
     the *note Decimal: 27c. class and are only briefly recounted here.

      -- 方法: abs (x)

          Returns the absolute value of 'x'.

      -- 方法: add (x, y)

          Return the sum of 'x' and 'y'.

      -- 方法: canonical (x)

          Returns the same Decimal object 'x'.

      -- 方法: compare (x, y)

          Compares 'x' and 'y' numerically.

      -- 方法: compare_signal (x, y)

          Compares the values of the two operands numerically.

      -- 方法: compare_total (x, y)

          Compares two operands using their abstract representation.

      -- 方法: compare_total_mag (x, y)

          Compares two operands using their abstract representation,
          ignoring sign.

      -- 方法: copy_abs (x)

          Returns a copy of 'x' with the sign set to 0.

      -- 方法: copy_negate (x)

          Returns a copy of 'x' with the sign inverted.

      -- 方法: copy_sign (x, y)

          Copies the sign from 'y' to 'x'.

      -- 方法: divide (x, y)

          Return 'x' divided by 'y'.

      -- 方法: divide_int (x, y)

          Return 'x' divided by 'y', truncated to an integer.

      -- 方法: divmod (x, y)

          Divides two numbers and returns the integer part of the
          result.

      -- 方法: exp (x)

          Returns ‘e ** x’.

      -- 方法: fma (x, y, z)

          Returns 'x' multiplied by 'y', plus 'z'.

      -- 方法: is_canonical (x)

          Returns ‘True’ if 'x' is canonical; otherwise returns ‘False’.

      -- 方法: is_finite (x)

          Returns ‘True’ if 'x' is finite; otherwise returns ‘False’.

      -- 方法: is_infinite (x)

          Returns ‘True’ if 'x' is infinite; otherwise returns ‘False’.

      -- 方法: is_nan (x)

          Returns ‘True’ if 'x' is a qNaN or sNaN; otherwise returns
          ‘False’.

      -- 方法: is_normal (x)

          Returns ‘True’ if 'x' is a normal number; otherwise returns
          ‘False’.

      -- 方法: is_qnan (x)

          Returns ‘True’ if 'x' is a quiet NaN; otherwise returns
          ‘False’.

      -- 方法: is_signed (x)

          Returns ‘True’ if 'x' is negative; otherwise returns ‘False’.

      -- 方法: is_snan (x)

          Returns ‘True’ if 'x' is a signaling NaN; otherwise returns
          ‘False’.

      -- 方法: is_subnormal (x)

          Returns ‘True’ if 'x' is subnormal; otherwise returns ‘False’.

      -- 方法: is_zero (x)

          Returns ‘True’ if 'x' is a zero; otherwise returns ‘False’.

      -- 方法: ln (x)

          Returns the natural (base e) logarithm of 'x'.

      -- 方法: log10 (x)

          Returns the base 10 logarithm of 'x'.

      -- 方法: logb (x)

          Returns the exponent of the magnitude of the operand's MSD.

      -- 方法: logical_and (x, y)

          Applies the logical operation 'and' between each operand's
          digits.

      -- 方法: logical_invert (x)

          Invert all the digits in 'x'.

      -- 方法: logical_or (x, y)

          Applies the logical operation 'or' between each operand's
          digits.

      -- 方法: logical_xor (x, y)

          Applies the logical operation 'xor' between each operand's
          digits.

      -- 方法: max (x, y)

          Compares two values numerically and returns the maximum.

      -- 方法: max_mag (x, y)

          Compares the values numerically with their sign ignored.

      -- 方法: min (x, y)

          Compares two values numerically and returns the minimum.

      -- 方法: min_mag (x, y)

          Compares the values numerically with their sign ignored.

      -- 方法: minus (x)

          Minus corresponds to the unary prefix minus operator in
          Python.

      -- 方法: multiply (x, y)

          Return the product of 'x' and 'y'.

      -- 方法: next_minus (x)

          Returns the largest representable number smaller than 'x'.

      -- 方法: next_plus (x)

          Returns the smallest representable number larger than 'x'.

      -- 方法: next_toward (x, y)

          Returns the number closest to 'x', in direction towards 'y'.

      -- 方法: normalize (x)

          Reduces 'x' to its simplest form.

      -- 方法: number_class (x)

          Returns an indication of the class of 'x'.

      -- 方法: plus (x)

          Plus corresponds to the unary prefix plus operator in Python.
          This operation applies the context precision and rounding, so
          it is 'not' an identity operation.

      -- 方法: power (x, y, modulo=None)

          Return ‘x’ to the power of ‘y’, reduced modulo ‘modulo’ if
          given.

          With two arguments, compute ‘x**y’.  If ‘x’ is negative then
          ‘y’ must be integral.  The result will be inexact unless ‘y’
          is integral and the result is finite and can be expressed
          exactly in 'precision' digits.  The rounding mode of the
          context is used.  Results are always correctly rounded in the
          Python version.

          ‘Decimal(0) ** Decimal(0)’ results in ‘InvalidOperation’, and
          if ‘InvalidOperation’ is not trapped, then results in
          ‘Decimal('NaN')’.

          在 3.3 版的變更: The C module computes *note power(): 2594. in
          terms of the correctly rounded *note exp(): 2576. and *note
          ln(): 2581. functions.  The result is well-defined but only
          "almost always correctly rounded".

          With three arguments, compute ‘(x**y) % modulo’.  For the
          three argument form, the following restrictions on the
          arguments hold:

             - all three arguments must be integral

             - ‘y’ must be nonnegative

             - at least one of ‘x’ or ‘y’ must be nonzero

             - ‘modulo’ must be nonzero and have at most 'precision'
               digits

          The value resulting from ‘Context.power(x, y, modulo)’ is
          equal to the value that would be obtained by computing ‘(x**y)
          % modulo’ with unbounded precision, but is computed more
          efficiently.  The exponent of the result is zero, regardless
          of the exponents of ‘x’, ‘y’ and ‘modulo’.  The result is
          always exact.

      -- 方法: quantize (x, y)

          Returns a value equal to 'x' (rounded), having the exponent of
          'y'.

      -- 方法: radix ()

          Just returns 10, as this is Decimal, :)

      -- 方法: remainder (x, y)

          Returns the remainder from integer division.

          The sign of the result, if non-zero, is the same as that of
          the original dividend.

      -- 方法: remainder_near (x, y)

          Returns ‘x - y * n’, where 'n' is the integer nearest the
          exact value of ‘x / y’ (if the result is 0 then its sign will
          be the sign of 'x').

      -- 方法: rotate (x, y)

          Returns a rotated copy of 'x', 'y' times.

      -- 方法: same_quantum (x, y)

          Returns ‘True’ if the two operands have the same exponent.

      -- 方法: scaleb (x, y)

          Returns the first operand after adding the second value its
          exp.

      -- 方法: shift (x, y)

          Returns a shifted copy of 'x', 'y' times.

      -- 方法: sqrt (x)

          Square root of a non-negative number to context precision.

      -- 方法: subtract (x, y)

          Return the difference between 'x' and 'y'.

      -- 方法: to_eng_string (x)

          Convert to a string, using engineering notation if an exponent
          is needed.

          Engineering notation has an exponent which is a multiple of 3.
          This can leave up to 3 digits to the left of the decimal place
          and may require the addition of either one or two trailing
          zeros.

      -- 方法: to_integral_exact (x)

          Rounds to an integer.

      -- 方法: to_sci_string (x)

          Converts a number to a string using scientific notation.


File: python.info,  Node: 常數<4>,  Next: Rounding modes,  Prev: Context objects,  Up: decimal --- 十進位固定點和浮點運算

5.9.4.5 常數
............

The constants in this section are only relevant for the C module.  They
are also included in the pure Python version for compatibility.

                          32 位元                   64 位元
                                                    
----------------------------------------------------------------------------------------
                                                    
 -- 資料:                 ‘425000000’               ‘999999999999999999’
          decimal.MAX_PREC                          

 -- 資料:                 ‘425000000’               ‘999999999999999999’
          decimal.MAX_EMAX                          

 -- 資料:                 ‘-425000000’              ‘-999999999999999999’
          decimal.MIN_EMIN                          

 -- 資料:                 ‘-849999999’              ‘-1999999999999999997’
          decimal.MIN_ETINY                         

 -- 資料: decimal.HAVE_THREADS

     The value is ‘True’.  Deprecated, because Python now always has
     threads.

     在 3.9 版之後被棄用.

 -- 資料: decimal.HAVE_CONTEXTVAR

     The default value is ‘True’.  If Python is *note configured using
     the -without-decimal-contextvar option: 1c74, the C version uses a
     thread-local rather than a coroutine-local context and the value is
     ‘False’.  This is slightly faster in some nested context scenarios.

     在 3.8.3 版被加入.


File: python.info,  Node: Rounding modes,  Next: Signals,  Prev: 常數<4>,  Up: decimal --- 十進位固定點和浮點運算

5.9.4.6 Rounding modes
......................

 -- 資料: decimal.ROUND_CEILING

     Round towards ‘Infinity’.

 -- 資料: decimal.ROUND_DOWN

     Round towards zero.

 -- 資料: decimal.ROUND_FLOOR

     Round towards ‘-Infinity’.

 -- 資料: decimal.ROUND_HALF_DOWN

     Round to nearest with ties going towards zero.

 -- 資料: decimal.ROUND_HALF_EVEN

     Round to nearest with ties going to nearest even integer.

 -- 資料: decimal.ROUND_HALF_UP

     Round to nearest with ties going away from zero.

 -- 資料: decimal.ROUND_UP

     Round away from zero.

 -- 資料: decimal.ROUND_05UP

     Round away from zero if last digit after rounding towards zero
     would have been 0 or 5; otherwise round towards zero.


File: python.info,  Node: Signals,  Next: Floating-Point Notes,  Prev: Rounding modes,  Up: decimal --- 十進位固定點和浮點運算

5.9.4.7 Signals
...............

Signals represent conditions that arise during computation.  Each
corresponds to one context flag and one context trap enabler.

The context flag is set whenever the condition is encountered.  After
the computation, flags may be checked for informational purposes (for
instance, to determine whether a computation was exact).  After checking
the flags, be sure to clear all flags before starting the next
computation.

If the context's trap enabler is set for the signal, then the condition
causes a Python exception to be raised.  For example, if the *note
DivisionByZero: 2520. trap is set, then a *note DivisionByZero: 2520.
exception is raised upon encountering the condition.

 -- 類別: decimal.Clamped

     Altered an exponent to fit representation constraints.

     Typically, clamping occurs when an exponent falls outside the
     context's ‘Emin’ and ‘Emax’ limits.  If possible, the exponent is
     reduced to fit by adding zeros to the coefficient.

 -- 類別: decimal.DecimalException

     Base class for other signals and a subclass of *note
     ArithmeticError: 2162.

 -- 類別: decimal.DivisionByZero

     Signals the division of a non-infinite number by zero.

     Can occur with division, modulo division, or when raising a number
     to a negative power.  If this signal is not trapped, returns
     ‘Infinity’ or ‘-Infinity’ with the sign determined by the inputs to
     the calculation.

 -- 類別: decimal.Inexact

     Indicates that rounding occurred and the result is not exact.

     Signals when non-zero digits were discarded during rounding.  The
     rounded result is returned.  The signal flag or trap is used to
     detect when results are inexact.

 -- 類別: decimal.InvalidOperation

     An invalid operation was performed.

     Indicates that an operation was requested that does not make sense.
     If not trapped, returns ‘NaN’.  Possible causes include:

          Infinity - Infinity
          0 * Infinity
          Infinity / Infinity
          x % 0
          Infinity % x
          sqrt(-x) and x > 0
          0 ** 0
          x ** (non-integer)
          x ** Infinity

 -- 類別: decimal.Overflow

     Numerical overflow.

     Indicates the exponent is larger than ‘Context.Emax’ after rounding
     has occurred.  If not trapped, the result depends on the rounding
     mode, either pulling inward to the largest representable finite
     number or rounding outward to ‘Infinity’.  In either case, *note
     Inexact: 2521. and *note Rounded: 2522. are also signaled.

 -- 類別: decimal.Rounded

     Rounding occurred though possibly no information was lost.

     Signaled whenever rounding discards digits; even if those digits
     are zero (such as rounding ‘5.00’ to ‘5.0’).  If not trapped,
     returns the result unchanged.  This signal is used to detect loss
     of significant digits.

 -- 類別: decimal.Subnormal

     Exponent was lower than ‘Emin’ prior to rounding.

     Occurs when an operation result is subnormal (the exponent is too
     small).  If not trapped, returns the result unchanged.

 -- 類別: decimal.Underflow

     Numerical underflow with result rounded to zero.

     Occurs when a subnormal result is pushed to zero by rounding.
     *note Inexact: 2521. and *note Subnormal: 2523. are also signaled.

 -- 類別: decimal.FloatOperation

     Enable stricter semantics for mixing floats and Decimals.

     If the signal is not trapped (default), mixing floats and Decimals
     is permitted in the *note Decimal: 27c. constructor, *note
     create_decimal(): 1045. and all comparison operators.  Both
     conversion and comparisons are exact.  Any occurrence of a mixed
     operation is silently recorded by setting *note FloatOperation:
     103e. in the context flags.  Explicit conversions with *note
     from_float(): 119c. or *note create_decimal_from_float(): 2568. do
     not set the flag.

     Otherwise (the signal is trapped), only equality comparisons and
     explicit conversions are silent.  All other mixed operations raise
     *note FloatOperation: 103e.

The following table summarizes the hierarchy of signals:

     exceptions.ArithmeticError(exceptions.Exception)
         DecimalException
             Clamped
             DivisionByZero(DecimalException, exceptions.ZeroDivisionError)
             Inexact
                 Overflow(Inexact, Rounded)
                 Underflow(Inexact, Rounded, Subnormal)
             InvalidOperation
             Rounded
             Subnormal
             FloatOperation(DecimalException, exceptions.TypeError)


File: python.info,  Node: Floating-Point Notes,  Next: Working with threads,  Prev: Signals,  Up: decimal --- 十進位固定點和浮點運算

5.9.4.8 Floating-Point Notes
............................

* Menu:

* Mitigating round-off error with increased precision::
* 特殊值::


File: python.info,  Node: Mitigating round-off error with increased precision,  Next: 特殊值,  Up: Floating-Point Notes

5.9.4.9 Mitigating round-off error with increased precision
...........................................................

The use of decimal floating point eliminates decimal representation
error (making it possible to represent ‘0.1’ exactly); however, some
operations can still incur round-off error when non-zero digits exceed
the fixed precision.

The effects of round-off error can be amplified by the addition or
subtraction of nearly offsetting quantities resulting in loss of
significance.  Knuth provides two instructive examples where rounded
floating-point arithmetic with insufficient precision causes the
breakdown of the associative and distributive properties of addition:

     # Examples from Seminumerical Algorithms, Section 4.2.2.
     >>> from decimal import Decimal, getcontext
     >>> getcontext().prec = 8

     >>> u, v, w = Decimal(11111113), Decimal(-11111111), Decimal('7.51111111')
     >>> (u + v) + w
     Decimal('9.5111111')
     >>> u + (v + w)
     Decimal('10')

     >>> u, v, w = Decimal(20000), Decimal(-6), Decimal('6.0000003')
     >>> (u*v) + (u*w)
     Decimal('0.01')
     >>> u * (v+w)
     Decimal('0.0060000')

The *note decimal: 2e. module makes it possible to restore the
identities by expanding the precision sufficiently to avoid loss of
significance:

     >>> getcontext().prec = 20
     >>> u, v, w = Decimal(11111113), Decimal(-11111111), Decimal('7.51111111')
     >>> (u + v) + w
     Decimal('9.51111111')
     >>> u + (v + w)
     Decimal('9.51111111')
     >>>
     >>> u, v, w = Decimal(20000), Decimal(-6), Decimal('6.0000003')
     >>> (u*v) + (u*w)
     Decimal('0.0060000')
     >>> u * (v+w)
     Decimal('0.0060000')


File: python.info,  Node: 特殊值,  Prev: Mitigating round-off error with increased precision,  Up: Floating-Point Notes

5.9.4.10 特殊值
...............

The number system for the *note decimal: 2e. module provides special
values including ‘NaN’, ‘sNaN’, ‘-Infinity’, ‘Infinity’, and two zeros,
‘+0’ and ‘-0’.

Infinities can be constructed directly with: ‘Decimal('Infinity')’.
Also, they can arise from dividing by zero when the *note
DivisionByZero: 2520. signal is not trapped.  Likewise, when the *note
Overflow: 2524. signal is not trapped, infinity can result from rounding
beyond the limits of the largest representable number.

The infinities are signed (affine) and can be used in arithmetic
operations where they get treated as very large, indeterminate numbers.
For instance, adding a constant to infinity gives another infinite
result.

Some operations are indeterminate and return ‘NaN’, or if the *note
InvalidOperation: 1044. signal is trapped, raise an exception.  For
example, ‘0/0’ returns ‘NaN’ which means "not a number".  This variety
of ‘NaN’ is quiet and, once created, will flow through other
computations always resulting in another ‘NaN’.  This behavior can be
useful for a series of computations that occasionally have missing
inputs -- it allows the calculation to proceed while flagging specific
results as invalid.

A variant is ‘sNaN’ which signals rather than remaining quiet after
every operation.  This is a useful return value when an invalid result
needs to interrupt a calculation for special handling.

The behavior of Python's comparison operators can be a little surprising
where a ‘NaN’ is involved.  A test for equality where one of the
operands is a quiet or signaling ‘NaN’ always returns *note False: adb.
(even when doing ‘Decimal('NaN')==Decimal('NaN')’), while a test for
inequality always returns *note True: bb4.  An attempt to compare two
Decimals using any of the ‘<’, ‘<=’, ‘>’ or ‘>=’ operators will raise
the *note InvalidOperation: 1044. signal if either operand is a ‘NaN’,
and return *note False: adb. if this signal is not trapped.  Note that
the General Decimal Arithmetic specification does not specify the
behavior of direct comparisons; these rules for comparisons involving a
‘NaN’ were taken from the IEEE 854 standard (see Table 3 in section
5.7).  To ensure strict standards-compliance, use the *note compare():
252f. and *note compare_signal(): 2530. methods instead.

The signed zeros can result from calculations that underflow.  They keep
the sign that would have resulted if the calculation had been carried
out to greater precision.  Since their magnitude is zero, both positive
and negative zeros are treated as equal and their sign is informational.

In addition to the two signed zeros which are distinct yet equal, there
are various representations of zero with differing precisions yet
equivalent in value.  This takes a bit of getting used to.  For an eye
accustomed to normalized floating-point representations, it is not
immediately obvious that the following calculation returns a value equal
to zero:

     >>> 1 / Decimal('Infinity')
     Decimal('0E-1000026')


File: python.info,  Node: Working with threads,  Next: Recipes,  Prev: Floating-Point Notes,  Up: decimal --- 十進位固定點和浮點運算

5.9.4.11 Working with threads
.............................

The *note getcontext(): 14c6. function accesses a different *note
Context: 1049. object for each thread.  Having separate thread contexts
means that threads may make changes (such as ‘getcontext().prec=10’)
without interfering with other threads.

Likewise, the *note setcontext(): 2528. function automatically assigns
its target to the current thread.

If *note setcontext(): 2528. has not been called before *note
getcontext(): 14c6, then *note getcontext(): 14c6. will automatically
create a new context for use in the current thread.

The new context is copied from a prototype context called
'DefaultContext'.  To control the defaults so that each thread will use
the same values throughout the application, directly modify the
'DefaultContext' object.  This should be done 'before' any threads are
started so that there won't be a race condition between threads calling
*note getcontext(): 14c6.  For example:

     # Set applicationwide defaults for all threads about to be launched
     DefaultContext.prec = 12
     DefaultContext.rounding = ROUND_DOWN
     DefaultContext.traps = ExtendedContext.traps.copy()
     DefaultContext.traps[InvalidOperation] = 1
     setcontext(DefaultContext)

     # Afterwards, the threads can be started
     t1.start()
     t2.start()
     t3.start()
      . . .


File: python.info,  Node: Recipes,  Next: Decimal FAQ,  Prev: Working with threads,  Up: decimal --- 十進位固定點和浮點運算

5.9.4.12 Recipes
................

Here are a few recipes that serve as utility functions and that
demonstrate ways to work with the *note Decimal: 27c. class:

     def moneyfmt(value, places=2, curr='', sep=',', dp='.',
                  pos='', neg='-', trailneg=''):
         """Convert Decimal to a money formatted string.

         places:  required number of places after the decimal point
         curr:    optional currency symbol before the sign (may be blank)
         sep:     optional grouping separator (comma, period, space, or blank)
         dp:      decimal point indicator (comma or period)
                  only specify as blank when places is zero
         pos:     optional sign for positive numbers: '+', space or blank
         neg:     optional sign for negative numbers: '-', '(', space or blank
         trailneg:optional trailing minus indicator:  '-', ')', space or blank

         >>> d = Decimal('-1234567.8901')
         >>> moneyfmt(d, curr='$')
         '-$1,234,567.89'
         >>> moneyfmt(d, places=0, sep='.', dp='', neg='', trailneg='-')
         '1.234.568-'
         >>> moneyfmt(d, curr='$', neg='(', trailneg=')')
         '($1,234,567.89)'
         >>> moneyfmt(Decimal(123456789), sep=' ')
         '123 456 789.00'
         >>> moneyfmt(Decimal('-0.02'), neg='<', trailneg='>')
         '<0.02>'

         """
         q = Decimal(10) ** -places      # 2 places --> '0.01'
         sign, digits, exp = value.quantize(q).as_tuple()
         result = []
         digits = list(map(str, digits))
         build, next = result.append, digits.pop
         if sign:
             build(trailneg)
         for i in range(places):
             build(next() if digits else '0')
         if places:
             build(dp)
         if not digits:
             build('0')
         i = 0
         while digits:
             build(next())
             i += 1
             if i == 3 and digits:
                 i = 0
                 build(sep)
         build(curr)
         build(neg if sign else pos)
         return ''.join(reversed(result))

     def pi():
         """Compute Pi to the current precision.

         >>> print(pi())
         3.141592653589793238462643383

         """
         getcontext().prec += 2  # extra digits for intermediate steps
         three = Decimal(3)      # substitute "three=3.0" for regular floats
         lasts, t, s, n, na, d, da = 0, three, 3, 1, 0, 0, 24
         while s != lasts:
             lasts = s
             n, na = n+na, na+8
             d, da = d+da, da+32
             t = (t * n) / d
             s += t
         getcontext().prec -= 2
         return +s               # unary plus applies the new precision

     def exp(x):
         """Return e raised to the power of x.  Result type matches input type.

         >>> print(exp(Decimal(1)))
         2.718281828459045235360287471
         >>> print(exp(Decimal(2)))
         7.389056098930650227230427461
         >>> print(exp(2.0))
         7.38905609893
         >>> print(exp(2+0j))
         (7.38905609893+0j)

         """
         getcontext().prec += 2
         i, lasts, s, fact, num = 0, 0, 1, 1, 1
         while s != lasts:
             lasts = s
             i += 1
             fact *= i
             num *= x
             s += num / fact
         getcontext().prec -= 2
         return +s

     def cos(x):
         """Return the cosine of x as measured in radians.

         The Taylor series approximation works best for a small value of x.
         For larger values, first compute x = x % (2 * pi).

         >>> print(cos(Decimal('0.5')))
         0.8775825618903727161162815826
         >>> print(cos(0.5))
         0.87758256189
         >>> print(cos(0.5+0j))
         (0.87758256189+0j)

         """
         getcontext().prec += 2
         i, lasts, s, fact, num, sign = 0, 0, 1, 1, 1, 1
         while s != lasts:
             lasts = s
             i += 2
             fact *= i * (i-1)
             num *= x * x
             sign *= -1
             s += num / fact * sign
         getcontext().prec -= 2
         return +s

     def sin(x):
         """Return the sine of x as measured in radians.

         The Taylor series approximation works best for a small value of x.
         For larger values, first compute x = x % (2 * pi).

         >>> print(sin(Decimal('0.5')))
         0.4794255386042030002732879352
         >>> print(sin(0.5))
         0.479425538604
         >>> print(sin(0.5+0j))
         (0.479425538604+0j)

         """
         getcontext().prec += 2
         i, lasts, s, fact, num, sign = 1, 0, x, 1, x, 1
         while s != lasts:
             lasts = s
             i += 2
             fact *= i * (i-1)
             num *= x * x
             sign *= -1
             s += num / fact * sign
         getcontext().prec -= 2
         return +s


File: python.info,  Node: Decimal FAQ,  Prev: Recipes,  Up: decimal --- 十進位固定點和浮點運算

5.9.4.13 Decimal FAQ
....................

Q. It is cumbersome to type ‘decimal.Decimal('1234.5')’.  Is there a way
to minimize typing when using the interactive interpreter?

A. Some users abbreviate the constructor to just a single letter:

     >>> D = decimal.Decimal
     >>> D('1.23') + D('3.45')
     Decimal('4.68')

Q. In a fixed-point application with two decimal places, some inputs
have many places and need to be rounded.  Others are not supposed to
have excess digits and need to be validated.  What methods should be
used?

A. The *note quantize(): 104a. method rounds to a fixed number of
decimal places.  If the *note Inexact: 2521. trap is set, it is also
useful for validation:

     >>> TWOPLACES = Decimal(10) ** -2       # same as Decimal('0.01')

     >>> # Round to two places
     >>> Decimal('3.214').quantize(TWOPLACES)
     Decimal('3.21')

     >>> # Validate that a number does not exceed two places
     >>> Decimal('3.21').quantize(TWOPLACES, context=Context(traps=[Inexact]))
     Decimal('3.21')

     >>> Decimal('3.214').quantize(TWOPLACES, context=Context(traps=[Inexact]))
     Traceback (most recent call last):
        ...
     Inexact: None

Q. Once I have valid two place inputs, how do I maintain that invariant
throughout an application?

A. Some operations like addition, subtraction, and multiplication by an
integer will automatically preserve fixed point.  Others operations,
like division and non-integer multiplication, will change the number of
decimal places and need to be followed-up with a *note quantize(): 104a.
step:

     >>> a = Decimal('102.72')           # Initial fixed-point values
     >>> b = Decimal('3.17')
     >>> a + b                           # Addition preserves fixed-point
     Decimal('105.89')
     >>> a - b
     Decimal('99.55')
     >>> a * 42                          # So does integer multiplication
     Decimal('4314.24')
     >>> (a * b).quantize(TWOPLACES)     # Must quantize non-integer multiplication
     Decimal('325.62')
     >>> (b / a).quantize(TWOPLACES)     # And quantize division
     Decimal('0.03')

In developing fixed-point applications, it is convenient to define
functions to handle the *note quantize(): 104a. step:

     >>> def mul(x, y, fp=TWOPLACES):
     ...     return (x * y).quantize(fp)
     ...
     >>> def div(x, y, fp=TWOPLACES):
     ...     return (x / y).quantize(fp)

     >>> mul(a, b)                       # Automatically preserve fixed-point
     Decimal('325.62')
     >>> div(b, a)
     Decimal('0.03')

Q. There are many ways to express the same value.  The numbers ‘200’,
‘200.000’, ‘2E2’, and ‘.02E+4’ all have the same value at various
precisions.  Is there a way to transform them to a single recognizable
canonical value?

A. The *note normalize(): 2550. method maps all equivalent values to a
single representative:

     >>> values = map(Decimal, '200 200.000 2E2 .02E+4'.split())
     >>> [v.normalize() for v in values]
     [Decimal('2E+2'), Decimal('2E+2'), Decimal('2E+2'), Decimal('2E+2')]

Q. When does rounding occur in a computation?

A. It occurs 'after' the computation.  The philosophy of the decimal
specification is that numbers are considered exact and are created
independent of the current context.  They can even have greater
precision than current context.  Computations process with those exact
inputs and then rounding (or other context operations) is applied to the
'result' of the computation:

     >>> getcontext().prec = 5
     >>> pi = Decimal('3.1415926535')   # More than 5 digits
     >>> pi                             # All digits are retained
     Decimal('3.1415926535')
     >>> pi + 0                         # Rounded after an addition
     Decimal('3.1416')
     >>> pi - Decimal('0.00005')        # Subtract unrounded numbers, then round
     Decimal('3.1415')
     >>> pi + 0 - Decimal('0.00005').   # Intermediate values are rounded
     Decimal('3.1416')

Q. Some decimal values always print with exponential notation.  Is there
a way to get a non-exponential representation?

A. For some values, exponential notation is the only way to express the
number of significant places in the coefficient.  For example,
expressing ‘5.0E+3’ as ‘5000’ keeps the value constant but cannot show
the original's two-place significance.

If an application does not care about tracking significance, it is easy
to remove the exponent and trailing zeroes, losing significance, but
keeping the value unchanged:

     >>> def remove_exponent(d):
     ...     return d.quantize(Decimal(1)) if d == d.to_integral() else d.normalize()

     >>> remove_exponent(Decimal('5E+3'))
     Decimal('5000')

Q. Is there a way to convert a regular float to a *note Decimal: 27c.?

A. Yes, any binary floating-point number can be exactly expressed as a
Decimal though an exact conversion may take more precision than
intuition would suggest:

     >>> Decimal(math.pi)
     Decimal('3.141592653589793115997963468544185161590576171875')

Q. Within a complex calculation, how can I make sure that I haven't
gotten a spurious result because of insufficient precision or rounding
anomalies.

A. The decimal module makes it easy to test results.  A best practice is
to re-run calculations using greater precision and with various rounding
modes.  Widely differing results indicate insufficient precision,
rounding mode issues, ill-conditioned inputs, or a numerically unstable
algorithm.

Q. I noticed that context precision is applied to the results of
operations but not to the inputs.  Is there anything to watch out for
when mixing values of different precisions?

A. Yes.  The principle is that all values are considered to be exact and
so is the arithmetic on those values.  Only the results are rounded.
The advantage for inputs is that "what you type is what you get".  A
disadvantage is that the results can look odd if you forget that the
inputs haven't been rounded:

     >>> getcontext().prec = 3
     >>> Decimal('3.104') + Decimal('2.104')
     Decimal('5.21')
     >>> Decimal('3.104') + Decimal('0.000') + Decimal('2.104')
     Decimal('5.20')

The solution is either to increase precision or to force rounding of
inputs using the unary plus operation:

     >>> getcontext().prec = 3
     >>> +Decimal('1.23456789')      # unary plus triggers rounding
     Decimal('1.23')

Alternatively, inputs can be rounded upon creation using the *note
Context.create_decimal(): 1045. method:

     >>> Context(prec=5, rounding=ROUND_DOWN).create_decimal('1.2345678')
     Decimal('1.2345')

Q. Is the CPython implementation fast for large numbers?

A. Yes.  In the CPython and PyPy3 implementations, the C/CFFI versions
of the decimal module integrate the high speed libmpdec(1) library for
arbitrary precision correctly rounded decimal floating-point arithmetic
(2).  ‘libmpdec’ uses Karatsuba multiplication(3) for medium-sized
numbers and the Number Theoretic Transform(4) for very large numbers.

The context must be adapted for exact arbitrary precision arithmetic.
‘Emin’ and ‘Emax’ should always be set to the maximum values, ‘clamp’
should always be 0 (the default).  Setting ‘prec’ requires some care.

The easiest approach for trying out bignum arithmetic is to use the
maximum value for ‘prec’ as well (5):

     >>> setcontext(Context(prec=MAX_PREC, Emax=MAX_EMAX, Emin=MIN_EMIN))
     >>> x = Decimal(2) ** 256
     >>> x / 128
     Decimal('904625697166532776746648320380374280103671755200316906558262375061821325312')

For inexact results, *note MAX_PREC: 2561. is far too large on 64-bit
platforms and the available memory will be insufficient:

     >>> Decimal(1) / 3
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     MemoryError

On systems with overallocation (e.g.  Linux), a more sophisticated
approach is to adjust ‘prec’ to the amount of available RAM. Suppose
that you have 8GB of RAM and expect 10 simultaneous operands using a
maximum of 500MB each:

     >>> import sys
     >>>
     >>> # Maximum number of digits for a single operand using 500MB in 8-byte words
     >>> # with 19 digits per word (4-byte and 9 digits for the 32-bit build):
     >>> maxdigits = 19 * ((500 * 1024**2) // 8)
     >>>
     >>> # Check that this works:
     >>> c = Context(prec=maxdigits, Emax=MAX_EMAX, Emin=MIN_EMIN)
     >>> c.traps[Inexact] = True
     >>> setcontext(c)
     >>>
     >>> # Fill the available precision with nines:
     >>> x = Decimal(0).logical_invert() * 9
     >>> sys.getsizeof(x)
     524288112
     >>> x + 2
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
       decimal.Inexact: [<class 'decimal.Inexact'>]

In general (and especially on systems without overallocation), it is
recommended to estimate even tighter bounds and set the *note Inexact:
2521. trap if all calculations are expected to be exact.

   ---------- Footnotes ----------

   (1) https://www.bytereef.org/mpdecimal/doc/libmpdec/index.html

   (2) 
在 3.3 版被加入.

   (3) https://en.wikipedia.org/wiki/Karatsuba_algorithm

   (4) 
https://en.wikipedia.org/wiki/Discrete_Fourier_transform_(general)#Number-theoretic_transform

   (5) 
在 3.9 版的變更: This approach now works for all exact results except
for non-integer powers.


File: python.info,  Node: fractions --- 有理數,  Next: random --- 生成偽隨機數,  Prev: decimal --- 十進位固定點和浮點運算,  Up: 數值與數學模組

5.9.5 ‘fractions’ -- 有理數
---------------------------

'原始碼：'Lib/fractions.py(1)

__________________________________________________________________

The *note fractions: 53. module provides support for rational number
arithmetic.

A Fraction instance can be constructed from a pair of integers, from
another rational number, or from a string.

 -- 類別: fractions.Fraction (numerator=0, denominator=1)

 -- 類別: fractions.Fraction (other_fraction)

 -- 類別: fractions.Fraction (float)

 -- 類別: fractions.Fraction (decimal)

 -- 類別: fractions.Fraction (string)

     The first version requires that 'numerator' and 'denominator' are
     instances of *note numbers.Rational: 1255. and returns a new *note
     Fraction: 1c7. instance with value ‘numerator/denominator’.  If
     'denominator' is ‘0’, it raises a *note ZeroDivisionError: 8e9.
     The second version requires that 'other_fraction' is an instance of
     *note numbers.Rational: 1255. and returns a *note Fraction: 1c7.
     instance with the same value.  The next two versions accept either
     a *note float: 2c8. or a *note decimal.Decimal: 27c. instance, and
     return a *note Fraction: 1c7. instance with exactly the same value.
     Note that due to the usual issues with binary floating point (see
     *note 浮點數運算：問題與限制: 1c13.), the argument to
     ‘Fraction(1.1)’ is not exactly equal to 11/10, and so
     ‘Fraction(1.1)’ does 'not' return ‘Fraction(11, 10)’ as one might
     expect.  (But see the documentation for the *note
     limit_denominator(): 25b4. method below.)  The last version of the
     constructor expects a string or unicode instance.  The usual form
     for this instance is:

          [sign] numerator ['/' denominator]

     where the optional ‘sign’ may be either '+' or '-' and ‘numerator’
     and ‘denominator’ (if present) are strings of decimal digits
     (underscores may be used to delimit digits as with integral
     literals in code).  In addition, any string that represents a
     finite value and is accepted by the *note float: 2c8. constructor
     is also accepted by the *note Fraction: 1c7. constructor.  In
     either form the input string may also have leading and/or trailing
     whitespace.  Here are some examples:

          >>> from fractions import Fraction
          >>> Fraction(16, -10)
          Fraction(-8, 5)
          >>> Fraction(123)
          Fraction(123, 1)
          >>> Fraction()
          Fraction(0, 1)
          >>> Fraction('3/7')
          Fraction(3, 7)
          >>> Fraction(' -3/7 ')
          Fraction(-3, 7)
          >>> Fraction('1.414213 \t\n')
          Fraction(1414213, 1000000)
          >>> Fraction('-.125')
          Fraction(-1, 8)
          >>> Fraction('7e-6')
          Fraction(7, 1000000)
          >>> Fraction(2.25)
          Fraction(9, 4)
          >>> Fraction(1.1)
          Fraction(2476979795053773, 2251799813685248)
          >>> from decimal import Decimal
          >>> Fraction(Decimal('1.1'))
          Fraction(11, 10)

     The *note Fraction: 1c7. class inherits from the abstract base
     class *note numbers.Rational: 1255, and implements all of the
     methods and operations from that class.  *note Fraction: 1c7.
     instances are *note hashable: 5b5, and should be treated as
     immutable.  In addition, *note Fraction: 1c7. has the following
     properties and methods:

     在 3.2 版的變更: The *note Fraction: 1c7. constructor now accepts
     *note float: 2c8. and *note decimal.Decimal: 27c. instances.

     在 3.9 版的變更: The *note math.gcd(): 8b5. function is now used to
     normalize the 'numerator' and 'denominator'.  *note math.gcd():
     8b5. always returns an *note int: 23c. type.  Previously, the GCD
     type depended on 'numerator' and 'denominator'.

     在 3.11 版的變更: Underscores are now permitted when creating a
     *note Fraction: 1c7. instance from a string, following PEP 515(2)
     rules.

     在 3.11 版的變更: *note Fraction: 1c7. implements ‘__int__’ now to
     satisfy ‘typing.SupportsInt’ instance checks.

     在 3.12 版的變更: Space is allowed around the slash for string
     inputs: ‘Fraction('2 / 3')’.

     在 3.12 版的變更: *note Fraction: 1c7. instances now support
     float-style formatting, with presentation types ‘"e"’, ‘"E"’,
     ‘"f"’, ‘"F"’, ‘"g"’, ‘"G"’ and ‘"%""’.

     在 3.13 版的變更: Formatting of *note Fraction: 1c7. instances
     without a presentation type now supports fill, alignment, sign
     handling, minimum width and grouping.

      -- 屬性: numerator

          Numerator of the Fraction in lowest term.

      -- 屬性: denominator

          Denominator of the Fraction in lowest term.

      -- 方法: as_integer_ratio ()

          Return a tuple of two integers, whose ratio is equal to the
          original Fraction.  The ratio is in lowest terms and has a
          positive denominator.

          在 3.8 版被加入.

      -- 方法: is_integer ()

          Return ‘True’ if the Fraction is an integer.

          在 3.12 版被加入.

      -- 方法: classmethod from_float (flt)

          Alternative constructor which only accepts instances of *note
          float: 2c8. or *note numbers.Integral: 1e92.  Beware that
          ‘Fraction.from_float(0.3)’ is not the same value as
          ‘Fraction(3, 10)’.

               備註: From Python 3.2 onwards, you can also construct a
               *note Fraction: 1c7. instance directly from a *note
               float: 2c8.

      -- 方法: classmethod from_decimal (dec)

          Alternative constructor which only accepts instances of *note
          decimal.Decimal: 27c. or *note numbers.Integral: 1e92.

               備註: From Python 3.2 onwards, you can also construct a
               *note Fraction: 1c7. instance directly from a *note
               decimal.Decimal: 27c. instance.

      -- 方法: limit_denominator (max_denominator=1000000)

          Finds and returns the closest *note Fraction: 1c7. to ‘self’
          that has denominator at most max_denominator.  This method is
          useful for finding rational approximations to a given
          floating-point number:

               >>> from fractions import Fraction
               >>> Fraction('3.1415926535897932').limit_denominator(1000)
               Fraction(355, 113)

          or for recovering a rational number that's represented as a
          float:

               >>> from math import pi, cos
               >>> Fraction(cos(pi/3))
               Fraction(4503599627370497, 9007199254740992)
               >>> Fraction(cos(pi/3)).limit_denominator()
               Fraction(1, 2)
               >>> Fraction(1.1).limit_denominator()
               Fraction(11, 10)

      -- 方法: __floor__ ()

          Returns the greatest *note int: 23c. ‘<= self’.  This method
          can also be accessed through the *note math.floor(): 132f.
          function:

               >>> from math import floor
               >>> floor(Fraction(355, 113))
               3

      -- 方法: __ceil__ ()

          Returns the least *note int: 23c. ‘>= self’.  This method can
          also be accessed through the *note math.ceil(): 1330.
          function.

      -- 方法: __round__ ()

      -- 方法: __round__ (ndigits)

          The first version returns the nearest *note int: 23c. to
          ‘self’, rounding half to even.  The second version rounds
          ‘self’ to the nearest multiple of ‘Fraction(1, 10**ndigits)’
          (logically, if ‘ndigits’ is negative), again rounding half
          toward even.  This method can also be accessed through the
          *note round(): 126d. function.

      -- 方法: __format__ (format_spec, /)

          Provides support for formatting of *note Fraction: 1c7.
          instances via the *note str.format(): 5c7. method, the *note
          format(): 5c3. built-in function, or *note Formatted string
          literals: 94d.

          If the ‘format_spec’ format specification string does not end
          with one of the presentation types ‘'e'’, ‘'E'’, ‘'f'’, ‘'F'’,
          ‘'g'’, ‘'G'’ or ‘'%'’ then formatting follows the general
          rules for fill, alignment, sign handling, minimum width, and
          grouping as described in the *note format specification
          mini-language: 1c8.  The "alternate form" flag ‘'#'’ is
          supported: if present, it forces the output string to always
          include an explicit denominator, even when the value being
          formatted is an exact integer.  The zero-fill flag ‘'0'’ is
          not supported.

          If the ‘format_spec’ format specification string ends with one
          of the presentation types ‘'e'’, ‘'E'’, ‘'f'’, ‘'F'’, ‘'g'’,
          ‘'G'’ or ‘'%'’ then formatting follows the rules outlined for
          the *note float: 2c8. type in the *note 格式規格 (Format
          Specification) 迷你語言: 1c8. section.

          Here are some examples:

               >>> from fractions import Fraction
               >>> format(Fraction(103993, 33102), '_')
               '103_993/33_102'
               >>> format(Fraction(1, 7), '.^+10')
               '...+1/7...'
               >>> format(Fraction(3, 1), '')
               '3'
               >>> format(Fraction(3, 1), '#')
               '3/1'
               >>> format(Fraction(1, 7), '.40g')
               '0.1428571428571428571428571428571428571429'
               >>> format(Fraction('1234567.855'), '_.2f')
               '1_234_567.86'
               >>> f"{Fraction(355, 113):*>20.6e}"
               '********3.141593e+00'
               >>> old_price, new_price = 499, 672
               >>> "{:.2%} price increase".format(Fraction(new_price, old_price) - 1)
               '34.67% price increase'

也參考
......

*note numbers: 8e. 模組

     The abstract base classes making up the numeric tower.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/fractions.py

   (2) https://peps.python.org/pep-0515/


File: python.info,  Node: random --- 生成偽隨機數,  Next: statistics --- 數學統計函式,  Prev: fractions --- 有理數,  Up: 數值與數學模組

5.9.6 ‘random’ -- 生成偽隨機數
------------------------------

'原始碼：'Lib/random.py(1)

__________________________________________________________________

本章中所提及的 module（模組）用來實現各種分佈的虛擬隨機數產生器。

對於整數，可以從範圍中進行均勻選擇。對於序列，有一個隨機元素的均勻選擇，
一個用來原地 (in-place) 產生隨機排列清單的函式，以及一個用來隨機採樣不替
換的函式。

在實數線上，有一些函式用於處理均勻分佈、常態分佈（高斯分佈）、對數常態分
佈、負指數分佈、gamma 分佈和 Beta 分佈。對於生成角度分佈，可以使用馮·米
塞斯分佈 (von Mises distribution)。

幾乎所有 module 函式都相依於基本函式 *note random(): 6ec.，此函式在半開
放範圍 ‘0.0 <= X < 1.0’ 內均勻地生成一個隨機 float（浮點數）。Python 使
用 Mersenne Twister（梅森旋轉演算法）作為核心的產生器，它產生 53 位元精
度 float，其週期為 2**19937-1，透過 C 語言進行底層的實作既快速又支援執行
緒安全 (threadsafe)。Mersenne Twister 是現存最廣泛被驗證的隨機數產生器之
一，但是基於完全確定性，它並不適合所有目的，並且完全不適合加密目的。

該 module 提供的函式實際上是 *note random.Random: 17aa. class（類別）中
一個隱藏實例的綁定方法 (bound method)。你可以實例化自己的 *note Random:
17aa. 實例，以得到不共享狀態的產生器。

如果你想使用你自己設計的基本產生器，*note Random: 17aa. 也可以進行子類別
化 (subclass)。有關詳細資訊，請參考該類別的文件。

*note random: a6. module 也提供了 *note SystemRandom: 25bc. class，使用
系統函式 *note os.urandom(): 4c7. 從作業系統提供的來源產生隨機數。

     警告: 本章所提及的虛擬隨機數產生器不應該使用於安全目的。有關安全性
     或加密用途，請參考 *note secrets: ae. module。

也參考
......

M. Matsumoto and T. Nishimura, "Mersenne Twister: A 623-dimensionally
equidistributed uniform pseudorandom number generator", ACM Transactions
on Modeling and Computer Simulation Vol.  8, No.  1, January pp.3-30
1998.

進位互補乘法 (Complementary-Multiply-with-Carry) 用法(2)，可作為隨機數產
生器的一個可相容替代方案，具有較長的週期和相對簡單的更新操作。

     備註: The global random number generator and instances of *note
     Random: 17aa. are thread-safe.  However, in the free-threaded
     build, concurrent calls to the global generator or to the same
     instance of *note Random: 17aa. may encounter contention and poor
     performance.  Consider using separate instances of *note Random:
     17aa. per thread instead.

* Menu:

* 簿記函式 (bookkeeping functions): 簿記函式 bookkeeping functions.
* 回傳位元組的函式::
* 回傳整數的函式::
* 回傳序列的函式::
* 離散分布::
* 實數分布::
* 替代產生器::
* 關於 Reproducibility（復現性）的注意事項::
* 範例: 範例<6>.
* 使用方案::
* Command-line usage::
* Command-line example::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/random.py

   (2) 
https://code.activestate.com/recipes/576707-long-period-random-number-generator/


File: python.info,  Node: 簿記函式 bookkeeping functions,  Next: 回傳位元組的函式,  Up: random --- 生成偽隨機數

5.9.6.1 簿記函式 (bookkeeping functions)
........................................

 -- 函式: random.seed (a=None, version=2)

     初始化隨機數產生器。

     如果 'a' 被省略或為 ‘None’，則使用當前系統時間。如果隨機來源由作業
     系統提供，則使用它們而不是系統時間（有關可用性的詳細資訊，請參考
     *note os.urandom(): 4c7. 函式）。

     如果 'a' 為 int（整數），則直接使用它。

     如使用版本 2（預設值），*note str: 3f2.、*note bytes: 1a5. 或 *note
     bytearray: 4e3. 物件將轉換為 *note int: 23c.，並使用其所有位元。

     若使用版本 1（為復現於舊版本 Python 中產生隨機序列而提供），*note
     str: 3f2. 和 *note bytes: 1a5. 的演算法會生成範圍更窄的種子 (seed)。

     在 3.2 版的變更: 移至版本 2 方案，該方案使用字串種子中的所有位元。

     在 3.11 版的變更: 'seed' 必須是以下型別之一：‘None’、*note int:
     23c.、*note float: 2c8.、*note str: 3f2.、*note bytes: 1a5.、*note
     bytearray: 4e3.。

 -- 函式: random.getstate ()

     回傳一個物件，捕獲產生器的當前內部狀態。此物件可以傳遞給 *note
     setstate(): 25bf. 以恢復狀態。

 -- 函式: random.setstate (state)

     'state' 應該要從之前對 *note getstate(): 25be. 的呼叫中獲得，並且以
     *note setstate(): 25bf. 將產生器的內部狀態恢復到呼叫 *note
     getstate(): 25be. 時的狀態。


File: python.info,  Node: 回傳位元組的函式,  Next: 回傳整數的函式,  Prev: 簿記函式 bookkeeping functions,  Up: random --- 生成偽隨機數

5.9.6.2 回傳位元組的函式
........................

 -- 函式: random.randbytes (n)

     產生 'n' 個隨機位元組。

     此方法不應使用於產生安全性權杖 (Token)。請改用 *note
     secrets.token_bytes(): 25c1.。

     在 3.9 版被加入.


File: python.info,  Node: 回傳整數的函式,  Next: 回傳序列的函式,  Prev: 回傳位元組的函式,  Up: random --- 生成偽隨機數

5.9.6.3 回傳整數的函式
......................

 -- 函式: random.randrange (stop)

 -- 函式: random.randrange (start, stop[, step])

     傳回從 ‘range(start, stop, step)’ 中隨機選擇的元素。

     這大致相當於 ‘choice(range(start, stop, step))’，但支援任意大的範圍
     ，並針對常見情況進行了最佳化。

     位置引數模式與 *note range(): 8e7. 函式相符。

     不應使用關鍵字引數，因為它們可能會以意想不到的方式被直譯。例如
     ‘randrange(start=100)’ 會被直譯為 ‘randrange(0, 100, 1)’。

     在 3.2 版的變更: *note randrange(): 810. 在產生均勻分佈的值方面更為
     複雜。以前，它使用像 ‘int(random()*n)’ 這樣的樣式，這可能會產生稍微
     不均勻的分佈。

     在 3.12 版的變更: 已經不再支援非整數類型到等效整數的自動轉換。像是
     ‘randrange(10.0)’ 和 ‘randrange(Fraction(10, 1))’ 的呼叫將會引發
     *note TypeError: 4dd.。

 -- 函式: random.randint (a, b)

     回傳一個隨機整數 'N'，使得 ‘a <= N <= b’。為 ‘randrange(a, b+1)’ 的
     別名。

 -- 函式: random.getrandbits (k)

     回傳一個具有 'k' 個隨機位元的非負 Python 整數。此方法會隨 Mersenne
     Twister 產生器一起提供，一些其他的產生器也可能將其作為 API 的可選部
     分。如果可用，*note getrandbits(): fae. 使 *note randrange(): 810.
     能夠處理任意大的範圍。

     在 3.9 版的變更: 此方法現在接受 'k' 為零。


File: python.info,  Node: 回傳序列的函式,  Next: 離散分布,  Prev: 回傳整數的函式,  Up: random --- 生成偽隨機數

5.9.6.4 回傳序列的函式
......................

 -- 函式: random.choice (seq)

     從非空序列 'seq' 回傳一個隨機元素。如果 'seq' 為空，則引發 *note
     IndexError: 14a3.。

 -- 函式: random.choices (population, weights=None, *, cum_weights=None,
          k=1)

     回傳從 'population' 中重置取樣出的一個大小為 'k' 的元素 list。如果
     'population' 為空，則引發 *note IndexError: 14a3.。

     如果指定了 'weights' 序列，則根據相對權重進行選擇。另外，如果給定
     'cum_weights' 序列，則根據累積權重進行選擇（可能使用 *note
     itertools.accumulate(): 9a1. 計算）。例如，相對權重 ‘[10, 5, 30,
     5]’ 等同於累積權重 ‘[10, 15, 45, 50]’。在內部，相對權重在進行選擇之
     前會轉換為累積權重，因此提供累積權重可以節省工作。

     如果既未指定 'weights' 也未指定 'cum_weights'，則以相等的機率進行選
     擇。如果提供了加權序列，則該序列的長度必須與 'population' 序列的長
     度相同。它是一個 *note TypeError: 4dd. 來指定 'weights' 和
     'cum_weights'。

     'weights' 或 'cum_weights' 可以使用任何與 *note random(): a6. 所回
     傳的 *note float: 2c8. 值（包括整數、float 和分數，但不包括小數）交
     互操作 (interoperates) 的數值類型。權重假定為非負數和有限的。如果所
     有權重均為零，則引發 *note ValueError: 1e7.。

     對於給定的種子，具有相等權重的 *note choices(): c6d. 函式通常產生與
     重複呼叫 *note choice(): 11c8. 不同的序列。*note choices(): c6d. 使
     用的演算法使用浮點運算來實現內部一致性和速度。*note choice(): 11c8.
     使用的演算法預設為整數運算和重複選擇，以避免捨入誤差產生的小偏差。

     在 3.6 版被加入.

     在 3.9 版的變更: 如果所有權重均為零，則引發 *note ValueError: 1e7.。

 -- 函式: random.shuffle (x)

     將序列 'x' 原地 (in place) 隨機打亂位置。

     要打亂一個不可變的序列並回傳一個新的被打亂的 list（串列），請使用
     ‘sample(x, k=len(x))’。

     請注意，即使對於較小的 ‘len(x)’，'x' 的置換總數也會快速成長到大於大
     多數隨機數產生器的週期。這意味著長序列的大多數置換永遠無法產生。例
     如，長度為 2080 的序列是 Mersenne Twister 隨機數產生器週期內可以容
     納的最大序列。

     在 3.11 版的變更: 移除可選參數 'random'。

 -- 函式: random.sample (population, k, *, counts=None)

     回傳從母體序列中選擇出的一個包含獨特元素、長度為 'k' 的 list。用於
     不重置的隨機取樣。

     回傳包含母體元素的新清單，同時保持原始母體不變。產生的清單按選擇順
     序排列，因此所有子切片也會是有效的隨機樣本。這允許抽獎獲獎者（樣本
     ）分為大獎和第二名獲獎者（子切片）。

     母體成員不必是 *note hashable: 5b5. 或唯一的。如果母體包含重複項，
     則每次出現都是樣本中可能出現的一個選擇。

     可以一次指定一個重複元素，也可以使用可選的僅關鍵字 'counts' 參數指
     定重複元素。例如 ‘sample(['red', 'blue'], counts=[4, 2], k=5)’ 等同
     於 ‘sample(['red', 'red', 'red', 'red', 'blue', 'blue'], k=5)’。

     若要從整數範圍中選擇範例，請使用 *note range(): 8e7. 物件作為引數。
     這對於從大型母體中取樣特別快速且節省空間：‘sample(range(10000000),
     k=60)’。

     如果樣本大小大於母體大小，*note ValueError: 1e7. 會被引發。

     在 3.9 版的變更: 新增 'counts' 參數。

     在 3.11 版的變更: 'population' 必須是一個序列。不再支援將 set 自動
     轉換為 list。


File: python.info,  Node: 離散分布,  Next: 實數分布,  Prev: 回傳序列的函式,  Up: random --- 生成偽隨機數

5.9.6.5 離散分布
................

以下函式產生離散分佈。

 -- 函式: random.binomialvariate (n=1, p=0.5)

     二項分佈 (Binomial distribution)(1)。回傳 'n' 個獨立試驗的成功次數
     ，每個試驗的成功機率為 'p'：

     數學上等價於：

          sum(random() < p for i in range(n))

     試驗次數 'n' 應為非負整數。成功的機率 'p' 應在 ‘0.0 <= p <= 1.0’ 之
     間。結果是 ‘0 <= X <= n’ 範圍內的整數。

     在 3.12 版被加入.

   ---------- Footnotes ----------

   (1) https://mathworld.wolfram.com/BinomialDistribution.html


File: python.info,  Node: 實數分布,  Next: 替代產生器,  Prev: 離散分布,  Up: random --- 生成偽隨機數

5.9.6.6 實數分布
................

以下函式產生特定的實數分佈。函式參數以分佈方程中的對應變數命名，如常見的
數學實踐所示；這些方程式中的大多數都可以在任意統計文本中找到。

 -- 函式: random.random ()

     回傳範圍 ‘0.0 <= X < 1.0’ 中的下一個隨機浮點數

 -- 函式: random.uniform (a, b)

     回傳一個隨機浮點數 'N'，當 ‘a <= b’ 時確保 N 為 ‘a <= N <= b’ 、‘b
     < a’ 時確保 N 為 ‘b <= N <= a’。

     終點值 ‘b’ 可能包含在範圍內，也可能不包含在範圍內，取決於運算式 ‘a
     + (b-a) * random()’ 中的浮點捨入。

 -- 函式: random.triangular (low, high, mode)

     回傳一個隨機浮點數 'N'，使得 ‘low <= N <= high’，並在這些邊界之間具
     有指定的 'mode'。'low' 和 'high' 邊界預設為零和一。'mode' 引數預設
     為邊界之間的中點，從而給出對稱分佈。

 -- 函式: random.betavariate (alpha, beta)

     Beta（貝它）分布。參數的條件為 ‘alpha > 0’ 和 ‘beta > 0’。回傳值的
     範圍介於 0 和 1 之間。

 -- 函式: random.expovariate (lambd=1.0)

     指數分佈。'lambd' 為 1.0 除以所需的平均數。它應該不為零。（該參數將
     被稱為 "lambda"，但這是 Python 中的保留字）如果 'lambd' 為正，則回
     傳值的範圍從 0 到正無窮大；如果 'lambd' 為負，則回傳值的範圍從負無
     窮大到 0。

     在 3.12 版的變更: 新增 ‘lambd’ 的預設值。

 -- 函式: random.gammavariate (alpha, beta)

     Gamma（伽瑪）分佈。（'不是' Gamma 函式！）。形狀 (shape) 和比例
     (scale) 參數 'alpha' 和 'beta' 必須具有正值。（根據呼叫習慣不同，部
     分來源會將 'beta' 定義為比例的倒數）。

     Probability distribution function（機率密度函式）是：

                    x ** (alpha - 1) * math.exp(-x / beta)
          pdf(x) =  --------------------------------------
                      math.gamma(alpha) * beta ** alpha

 -- 函式: random.gauss (mu=0.0, sigma=1.0)

     常態分佈，也稱為高斯分佈。'mu' 是平均數，'sigma' 是標準差。這比下面
     定義的 *note normalvariate(): 1747. 函式快一點。

     多執行緒須注意：當兩個執行緒同時呼叫此函式時，它們可能會收到相同的
     傳回值。這可以透過三種方式避免。1）讓每個執行緒使用隨機數產生器的不
     同實例。2）在所有呼叫周圍加鎖。3）使用較慢但執行緒安全的 *note
     normalvariate(): 1747. 函式代替。

     在 3.11 版的變更: 'mu' 和 'sigma' 現在有預設引數。

 -- 函式: random.lognormvariate (mu, sigma)

     對數常態分佈。如果你取此分佈的自然對數，你將獲得一個具有平均數 'mu'
     和標準差 'sigma' 的常態分佈。'mu' 可以為任何值，並且 'sigma' 必須大
     於零。

 -- 函式: random.normalvariate (mu=0.0, sigma=1.0)

     常態分佈。'mu' 是平均數，'sigma' 是標準差。

     在 3.11 版的變更: 'mu' 和 'sigma' 現在有預設引數。

 -- 函式: random.vonmisesvariate (mu, kappa)

     'mu' 是平均角度，以 0 到 2*'pi' 之間的弧度表示，'kappa' 是濃度參數
     ，必須大於或等於零。如果 'kappa' 等於零，則此分佈在 0 到 2*'pi' 的
     範圍內將減小為均勻的隨機角度。

 -- 函式: random.paretovariate (alpha)

     Pareto distribution（柏拉圖分佈）。'alpha' 是形狀參數。

 -- 函式: random.weibullvariate (alpha, beta)

     Weibull distribution（韋伯分佈）。'alpha' 是比例參數，'beta' 是形狀
     參數。


File: python.info,  Node: 替代產生器,  Next: 關於 Reproducibility（復現性）的注意事項,  Prev: 實數分布,  Up: random --- 生成偽隨機數

5.9.6.7 替代產生器
..................

 -- 類別: random.Random ([seed])

     實現 *note random: a6. 模組使用的預設偽隨機數產生器的 class。

     在 3.11 版的變更: 過去 'seed' 可以是任何可雜湊物件，但現在必須是以
     下類型之一：‘None’、*note int: 23c.、*note float: 2c8.、*note str:
     3f2.、*note bytes: 1a5.、*note bytearray: 4e3.。

     如果 ‘Random’ 的子類別希望使用不同的基礎產生器，則應該覆寫以下方法
     ：

      -- 方法: seed (a=None, version=2)

          在子類別中覆寫此方法以自訂 ‘Random’ 實例的 *note seed(): 120c.
          行為。

      -- 方法: getstate ()

          在子類別中覆寫此方法以自訂 ‘Random’ 實例的 *note getstate():
          25be. 行為。

      -- 方法: setstate (state)

          在子類別中覆寫此方法以自訂 ‘Random’ 實例的 *note setstate():
          25bf. 行為。

      -- 方法: random ()

          在子類別中覆寫此方法以自訂 ‘Random’ 實例的 *note random():
          6ec. 行為。

     或者，自訂產生器子類別還可以提供以下方法：

      -- 方法: getrandbits (k)

          在子類別中覆寫此方法以自訂 ‘Random’ 實例的 *note
          getrandbits(): fae. 行為。

 -- 類別: random.SystemRandom ([seed])

     使用 *note os.urandom(): 4c7. 函式從作業系統提供的來源產生隨機數的
     Class。並非在所有系統上都可用。不依賴於軟體狀態，並且序列不可復現。
     因此 *note seed(): 120c. 方法沒有效果且被忽略。如果呼叫 *note
     getstate(): 25be. 和 *note setstate(): 25bf. 方法會引發 *note
     NotImplementedError: 20d.。


File: python.info,  Node: 關於 Reproducibility（復現性）的注意事項,  Next: 範例<6>,  Prev: 替代產生器,  Up: random --- 生成偽隨機數

5.9.6.8 關於 Reproducibility（復現性）的注意事項
................................................

有時，能夠重現偽隨機數產生器給出的序列很有用。只要多執行緒未運行，透過重
複使用種子值，同一序列就應該可以被復現。

大多數隨機 module 的演算法和 seed 設定函式在 Python 版本中可能會發生變化
，但可以保證兩個方面不會改變：

   * 如果增加了新的 seed 設定函式，則將提供向後相容的播種器 (seeder)。

   * 當相容的播種器被賦予相同的種子時，產生器的 *note random(): 25d2. 方
     法將持續產生相同的序列。


File: python.info,  Node: 範例<6>,  Next: 使用方案,  Prev: 關於 Reproducibility（復現性）的注意事項,  Up: random --- 生成偽隨機數

5.9.6.9 範例
............

基礎範例：

     >>> random()                          # Random float:  0.0 <= x < 1.0
     0.37444887175646646

     >>> uniform(2.5, 10.0)                # Random float:  2.5 <= x <= 10.0
     3.1800146073117523

     >>> expovariate(1 / 5)                # Interval between arrivals averaging 5 seconds
     5.148957571865031

     >>> randrange(10)                     # Integer from 0 to 9 inclusive
     7

     >>> randrange(0, 101, 2)              # Even integer from 0 to 100 inclusive
     26

     >>> choice(['win', 'lose', 'draw'])   # Single random element from a sequence
     'draw'

     >>> deck = 'ace two three four'.split()
     >>> shuffle(deck)                     # Shuffle a list
     >>> deck
     ['four', 'two', 'ace', 'three']

     >>> sample([10, 20, 30, 40, 50], k=4) # Four samples without replacement
     [40, 10, 50, 30]

模擬：

     >>> # Six roulette wheel spins (weighted sampling with replacement)
     >>> choices(['red', 'black', 'green'], [18, 18, 2], k=6)
     ['red', 'green', 'black', 'black', 'red', 'black']

     >>> # Deal 20 cards without replacement from a deck
     >>> # of 52 playing cards, and determine the proportion of cards
     >>> # with a ten-value:  ten, jack, queen, or king.
     >>> deal = sample(['tens', 'low cards'], counts=[16, 36], k=20)
     >>> deal.count('tens') / 20
     0.15

     >>> # Estimate the probability of getting 5 or more heads from 7 spins
     >>> # of a biased coin that settles on heads 60% of the time.
     >>> sum(binomialvariate(n=7, p=0.6) >= 5 for i in range(10_000)) / 10_000
     0.4169

     >>> # Probability of the median of 5 samples being in middle two quartiles
     >>> def trial():
     ...     return 2_500 <= sorted(choices(range(10_000), k=5))[2] < 7_500
     ...
     >>> sum(trial() for i in range(10_000)) / 10_000
     0.7958

統計 bootstrapping（自助法）(1)的範例，使用有重置的重新取樣來估計樣本平
均數的信賴區間：

     # https://www.thoughtco.com/example-of-bootstrapping-3126155
     from statistics import fmean as mean
     from random import choices

     data = [41, 50, 29, 37, 81, 30, 73, 63, 20, 35, 68, 22, 60, 31, 95]
     means = sorted(mean(choices(data, k=len(data))) for i in range(100))
     print(f'The sample mean of {mean(data):.1f} has a 90% confidence '
           f'interval from {means[5]:.1f} to {means[94]:.1f}')

重新取樣排列測試(2)的範例，來確定觀察到的藥物與安慰劑之間差異的統計學意
義或 p 值(3)：

     # Example from "Statistics is Easy" by Dennis Shasha and Manda Wilson
     from statistics import fmean as mean
     from random import shuffle

     drug = [54, 73, 53, 70, 73, 68, 52, 65, 65]
     placebo = [54, 51, 58, 44, 55, 52, 42, 47, 58, 46]
     observed_diff = mean(drug) - mean(placebo)

     n = 10_000
     count = 0
     combined = drug + placebo
     for i in range(n):
         shuffle(combined)
         new_diff = mean(combined[:len(drug)]) - mean(combined[len(drug):])
         count += (new_diff >= observed_diff)

     print(f'{n} label reshufflings produced only {count} instances with a difference')
     print(f'at least as extreme as the observed difference of {observed_diff:.1f}.')
     print(f'The one-sided p-value of {count / n:.4f} leads us to reject the null')
     print(f'hypothesis that there is no difference between the drug and the placebo.')

模擬多伺服器佇列 (queue) 的到達時間與服務交付：

     from heapq import heapify, heapreplace
     from random import expovariate, gauss
     from statistics import mean, quantiles

     average_arrival_interval = 5.6
     average_service_time = 15.0
     stdev_service_time = 3.5
     num_servers = 3

     waits = []
     arrival_time = 0.0
     servers = [0.0] * num_servers  # time when each server becomes available
     heapify(servers)
     for i in range(1_000_000):
         arrival_time += expovariate(1.0 / average_arrival_interval)
         next_server_available = servers[0]
         wait = max(0.0, next_server_available - arrival_time)
         waits.append(wait)
         service_duration = max(0.0, gauss(average_service_time, stdev_service_time))
         service_completed = arrival_time + wait + service_duration
         heapreplace(servers, service_completed)

     print(f'Mean wait: {mean(waits):.1f}   Max wait: {max(waits):.1f}')
     print('Quartiles:', [round(q, 1) for q in quantiles(waits)])

也參考
......

Statistics for Hackers(4) 是由 Jake Vanderplas(5) 製作的教學影片，僅使用
幾個基本概念（包括模擬、取樣、洗牌、交叉驗證）進行統計分析。

Economics Simulation(6)是由 Peter Norvig(7) 對市場進行的模擬，顯示了該模
組提供的許多工具和分佈（高斯、均勻、樣本、 beta 變數、選擇，三角形、隨機
數）的有效使用。

機率的具體介紹（使用Python）(8)為 Peter Norvig(9) 的教學課程，涵蓋了機率
理論的基礎知識與如何模擬以及使用 Python 執行數據分析。

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Bootstrapping_(statistics)

   (2) 
https://en.wikipedia.org/wiki/Resampling_(statistics)#Permutation_tests

   (3) https://en.wikipedia.org/wiki/P-value

   (4) https://www.youtube.com/watch?v=Iq9DzN6mvYA

   (5) https://us.pycon.org/2016/speaker/profile/295/

   (6) https://nbviewer.org/url/norvig.com/ipython/Economics.ipynb

   (7) https://norvig.com/bio.html

   (8) https://nbviewer.org/url/norvig.com/ipython/Probability.ipynb

   (9) https://norvig.com/bio.html


File: python.info,  Node: 使用方案,  Next: Command-line usage,  Prev: 範例<6>,  Up: random --- 生成偽隨機數

5.9.6.10 使用方案
.................

這些使用方案展示了如何有效地從 *note itertools: 75. 模組的組合疊代器
(combinatoric iterators) 中進行隨機選擇：

     def random_product(*args, repeat=1):
         "Random selection from itertools.product(*args, **kwds)"
         pools = [tuple(pool) for pool in args] * repeat
         return tuple(map(random.choice, pools))

     def random_permutation(iterable, r=None):
         "Random selection from itertools.permutations(iterable, r)"
         pool = tuple(iterable)
         r = len(pool) if r is None else r
         return tuple(random.sample(pool, r))

     def random_combination(iterable, r):
         "Random selection from itertools.combinations(iterable, r)"
         pool = tuple(iterable)
         n = len(pool)
         indices = sorted(random.sample(range(n), r))
         return tuple(pool[i] for i in indices)

     def random_combination_with_replacement(iterable, r):
         "Choose r elements with replacement.  Order the result to match the iterable."
         # Result will be in set(itertools.combinations_with_replacement(iterable, r)).
         pool = tuple(iterable)
         n = len(pool)
         indices = sorted(random.choices(range(n), k=r))
         return tuple(pool[i] for i in indices)

預設的 *note random(): 6ec. 回傳 '0.0 ≤ x < 1.0' 範圍內 2⁻⁵³ 的倍數。所
有數字都是均勻分佈的，並且可以完全表示為 Python float。但是，該間隔中的
許多其他可表示的 float 不是可能的選擇。 例如 ‘0.05954861408025609’ 不是
2⁻⁵³ 的整數倍。

以下範例採用不同的方法。間隔中的所有 float 都是可能的選擇。尾數來自 '2⁵²
≤ 尾數 < 2⁵³' 範圍內的整數均勻分佈。指數來自幾何分佈，其中小於 '-53' 的
指數的出現頻率是下一個較大指數的一半。

     from random import Random
     from math import ldexp

     class FullRandom(Random):

         def random(self):
             mantissa = 0x10_0000_0000_0000 | self.getrandbits(52)
             exponent = -53
             x = 0
             while not x:
                 x = self.getrandbits(32)
                 exponent += x.bit_length() - 32
             return ldexp(mantissa, exponent)

Class 中的所有*note 實數分佈: 25c6.都將使用新方法：

     >>> fr = FullRandom()
     >>> fr.random()
     0.05954861408025609
     >>> fr.expovariate(0.25)
     8.87925541791544

該範例在概念上等效於一種演算法，該演算法從 '0.0 ≤ x < 1.0' 範圍內 2⁻¹⁰⁷⁴
的所有倍數中進行選擇。這些數字都是均勻分佈的，但大多數必須向下捨入到最接
近的可表示的 Python float。（2⁻¹⁰⁷⁴ 是最小為正的非正規化 float，等於
‘math.ulp(0.0)’）

也參考
......

產生偽隨機浮點值(1) Allen B. Downey 的一篇論文描述了產生比通常由 *note
random(): 6ec. 產生的 float 更 fine-grained（細粒的）的方法。

   ---------- Footnotes ----------

   (1) https://allendowney.com/research/rand/downey07randfloat.pdf


File: python.info,  Node: Command-line usage,  Next: Command-line example,  Prev: 使用方案,  Up: random --- 生成偽隨機數

5.9.6.11 Command-line usage
...........................

在 3.13 版被加入.

The ‘random’ module can be executed from the command line.

     python -m random [-h] [-c CHOICE [CHOICE ...] | -i N | -f N] [input ...]

The following options are accepted:

 -- Option: -h, --help

     Show the help message and exit.

 -- Option: -c CHOICE [CHOICE ...]
 -- Option: --choice CHOICE [CHOICE ...]

     Print a random choice, using *note choice(): 11c8.

 -- Option: -i <N>
 -- Option: --integer <N>

     Print a random integer between 1 and N inclusive, using *note
     randint(): 11c7.

 -- Option: -f <N>
 -- Option: --float <N>

     Print a random floating-point number between 1 and N inclusive,
     using *note uniform(): 25c7.

If no options are given, the output depends on the input:

   * String or multiple: same as *note -choice: 25db.

   * Integer: same as *note -integer: 25dd.

   * Float: same as *note -float: 25df.


File: python.info,  Node: Command-line example,  Prev: Command-line usage,  Up: random --- 生成偽隨機數

5.9.6.12 Command-line example
.............................

Here are some examples of the ‘random’ command-line interface:

     $ # Choose one at random
     $ python -m random egg bacon sausage spam "Lobster Thermidor aux crevettes with a Mornay sauce"
     Lobster Thermidor aux crevettes with a Mornay sauce

     $ # Random integer
     $ python -m random 6
     6

     $ # Random floating-point number
     $ python -m random 1.8
     1.7080016272295635

     $ # With explicit arguments
     $ python  -m random --choice egg bacon sausage spam "Lobster Thermidor aux crevettes with a Mornay sauce"
     egg

     $ python -m random --integer 6
     3

     $ python -m random --float 1.8
     1.5666339105010318

     $ python -m random --integer 6
     5

     $ python -m random --float 6
     3.1942323316565915


File: python.info,  Node: statistics --- 數學統計函式,  Prev: random --- 生成偽隨機數,  Up: 數值與數學模組

5.9.7 ‘statistics’ -- 數學統計函式
----------------------------------

在 3.4 版被加入.

'原始碼：'Lib/statistics.py(1)

__________________________________________________________________

這個模組提供計算數值 (‘Real’-valued) 資料的數學統計函式。

這個模組並非旨在與 NumPy(2)、SciPy(3) 等第三方函式庫，或者像 Minitab、
SAS 和 Matlab 等專門設計給專業統計學家的高階統計軟體互相競爭。此模組的目
標在於繪圖和科學計算。

除非特別註明，這些函數支援 *note int: 23c.、*note float: 2c8.、*note
Decimal: 27c. 以及 *note Fraction: 1c7.。目前不支援其他型別（無論是否為
數值型別）。含有混合型別的資料的集合亦是尚未定義，且取決於該型別的實作。
若你的輸入資料含有混合型別，你可以考慮使用 *note map(): 808. 來確保結果
是一致的，例如：‘map(float, input_data)’。

有些資料集使用 ‘NaN’ （非數）來表示缺漏的資料。由於 NaN 具有特殊的比較語
義，在排序資料或是統計出現次數的統計函數中，會引發意料之外或是未定義的行
為。受影響的函數包含 ‘median()’、‘median_low()’、 ‘median_high()’、
‘median_grouped()’、 ‘mode()’、 ‘multimode()’ 以及 ‘quantiles()’。在呼叫
這些函數之前，應該先移除 NaN 值：

     >>> from statistics import median
     >>> from math import isnan
     >>> from itertools import filterfalse

     >>> data = [20.7, float('NaN'),19.2, 18.3, float('NaN'), 14.4]
     >>> sorted(data)  # This has surprising behavior
     [20.7, nan, 14.4, 18.3, 19.2, nan]
     >>> median(data)  # This result is unexpected
     16.35

     >>> sum(map(isnan, data))    # Number of missing values
     2
     >>> clean = list(filterfalse(isnan, data))  # Strip NaN values
     >>> clean
     [20.7, 19.2, 18.3, 14.4]
     >>> sorted(clean)  # Sorting now works as expected
     [14.4, 18.3, 19.2, 20.7]
     >>> median(clean)       # This result is now well defined
     18.75

* Menu:

* 平均值與中央位置量數::
* 離度 (spread) 的測量: 離度 spread 的測量.
* 兩個輸入之間的關係統計::
* 函式細節::
* 例外: 例外<3>.
* NormalDist 物件::
* 範例與錦囊妙計::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/statistics.py

   (2) https://numpy.org

   (3) https://scipy.org/


File: python.info,  Node: 平均值與中央位置量數,  Next: 離度 spread 的測量,  Up: statistics --- 數學統計函式

5.9.7.1 平均值與中央位置量數
............................

這些函式計算來自一個母體或樣本的平均值或代表值。

*note mean(): 676.          資料的算術平均數（平均值）。
                            
                            
*note fmean(): 9d8.         快速浮點數算數平均數，可調整權重。
                            
                            
*note geometric_mean(): 9d9.資料的幾何平均數。
                            
                            
*note harmonic_mean(): c88. 資料的調和平均數。
                            
                            
*note kde(): 22f.           Estimate the probability density distribution of the data.
                            
                            
*note kde_random(): 230.    Random sampling from the PDF generated by kde().
                            
                            
*note median(): 25e5.       資料的中位數（中間值）。
                            
                            
*note median_low(): 25e6.   資料中較小的中位數。
                            
                            
*note median_high(): 25e7.  資料中較大的中位數。
                            
                            
*note median_grouped(): 25e8.分組資料的中位數（第 50 百分位數）。
                            
                            
*note mode(): a35.          離散 (discrete) 或名目 (nomial) 資料中的眾數（出現次數最多次的值
                            ），只回傳一個。
                            
                            
*note multimode(): 9da.     離散或名目資料中的眾數（出現次數最多次的值）組成的 list。
                            
                            
*note quantiles(): 9db.     將資料分成數個具有相等機率的區間，即分位數 (quantile)。
                            


File: python.info,  Node: 離度 spread 的測量,  Next: 兩個輸入之間的關係統計,  Prev: 平均值與中央位置量數,  Up: statistics --- 數學統計函式

5.9.7.2 離度 (spread) 的測量
............................

這些函式計算母體或樣本偏離平均值的程度。

*note pstdev(): 25ea.       資料的母體標準差。
                            
                            
*note pvariance(): 25eb.    資料的母體變異數。
                            
                            
*note stdev(): 678.         資料的樣本標準差。
                            
                            
*note variance(): 677.      資料的樣本變異數。
                            


File: python.info,  Node: 兩個輸入之間的關係統計,  Next: 函式細節,  Prev: 離度 spread 的測量,  Up: statistics --- 數學統計函式

5.9.7.3 兩個輸入之間的關係統計
..............................

這些函式計算兩個輸入之間的關係統計數據。

*note covariance(): 7d4.      兩變數的樣本共變異數。
                              
                              
*note correlation(): 463.     Pearson 與 Spearman 相關係數 (correlation coefficient)。
                              
                              
*note linear_regression(): 7d5.簡單線性迴歸的斜率和截距。
                              


File: python.info,  Node: 函式細節,  Next: 例外<3>,  Prev: 兩個輸入之間的關係統計,  Up: statistics --- 數學統計函式

5.9.7.4 函式細節
................

註：這些函數並不要求輸入的資料必須排序過。為了閱讀方便，大部份的範例仍已
排序過。

 -- 函式: statistics.mean (data)

     回傳 'data' 的樣本算數平均數，輸入可為一個 sequence 或者 iterable。

     算數平均數為資料總和除以資料點的數目。他通常被稱為「平均值」，儘管
     它只是眾多不同的數學平均值之一。它是衡量資料集中位置的一種指標。

     若 'data' 為空，則會引發 *note StatisticsError: 25ee.。

     使用範例：

          >>> mean([1, 2, 3, 4, 4])
          2.8
          >>> mean([-1.0, 2.5, 3.25, 5.75])
          2.625

          >>> from fractions import Fraction as F
          >>> mean([F(3, 7), F(1, 21), F(5, 3), F(1, 3)])
          Fraction(13, 21)

          >>> from decimal import Decimal as D
          >>> mean([D("0.5"), D("0.75"), D("0.625"), D("0.375")])
          Decimal('0.5625')

          備註: 平均值強烈受到離群值 (outliers)(1) 的影響，且不一定能當
          作這些資料點的典型範例。若要使用更穩健但效率較低的集中趨勢
          (central tendency)(2) 度量，請參考 *note median(): 25e5.。

          樣本平均數提供了對真實母體平均數的不偏估計 (unbiased
          estimate)，所以從所有可能的樣本中取平均值時，‘mean(sample)’ 會
          收斂至整個母體的真實平均值。若 'data' 為整個母體而非單一樣本，
          則 ‘mean(data)’ 等同於計算真實的母體平均數 μ。

 -- 函式: statistics.fmean (data, weights=None)

     將 'data' 轉換為浮點數並計算其算數平均數。

     這個函式運算比 *note mean(): 676. 更快，並且它總是回傳一個 *note
     float: 2c8.。'data' 可以是一個 sequence 或者 iterable。如果輸入的資
     料為空，則引發 *note StatisticsError: 25ee.。

          >>> fmean([3.5, 4.0, 5.25])
          4.25

     支援選擇性的加權。例如，一位教授以 20% 的比重計算小考分數，20% 的比
     重計算作業分數，30% 的比重計算期中考試分數，以及 30% 的比重計算期末
     考試分數：

          >>> grades = [85, 92, 83, 91]
          >>> weights = [0.20, 0.20, 0.30, 0.30]
          >>> fmean(grades, weights)
          87.6

     如果有提供 'weights'，它必須與 'data' 長度相同，否則將引發 *note
     ValueError: 1e7.。

     在 3.8 版被加入.

     在 3.11 版的變更: 新增 'weights' 的支援。

 -- 函式: statistics.geometric_mean (data)

     將 'data' 轉換成浮點數並計算其幾何平均數。

     幾何平均數使用數值的乘積（與之對照，算數平均數使用的是數值的和）來
     表示 'data' 的集中趨勢或典型值。

     若輸入的資料集為空、包含零、包含負值，則引發 *note StatisticsError:
     25ee.。'data' 可為 sequence 或者 iterable。

     目前沒有特別為了精確結果而特別多下什麼工夫。（然而，未來或許會有。
     ）

          >>> round(geometric_mean([54, 24, 36]), 1)
          36.0

     在 3.8 版被加入.

 -- 函式: statistics.harmonic_mean (data, weights=None)

     回傳 'data' 的調和平均數。'data' 可為實數 (real-valued) sequence 或
     者 iterable。如果省略 'weights' 或者 'weights' 為 ‘None’，則假設各
     權重相等。

     調和平均數是資料的倒數 (reciprocal) 經過 *note mean(): 676. 運算過
     後的倒數。例如，三個數 'a'，'b' 與 'c' 的調和平均數等於 ‘3/(1/a +
     1/b + 1/c)’。若其中一個值為零，結果將為零。

     調和平均數是一種平均數，是衡量資料中心位置的一種方法。它通常用於計
     算比率 (ratio) 或率 (rate) 的平均，例如速率（speed）。

     假設一輛汽車以時速 40 公里的速率行駛 10 公里，然後再以時速 60 公里
     的速率行駛 10 公里，求汽車的平均速率？

          >>> harmonic_mean([40, 60])
          48.0

     假設一輛汽車以時速 40 公里的速率行駛 5 公里，然後在交通順暢時，加速
     到時速 60 公里，以此速度行駛剩下的 30 公里。求汽車的平均速率？

          >>> harmonic_mean([40, 60], weights=[5, 30])
          56.0

     若 'data' 為空、含有任何小於零的元素、或者加權總和不為正數，則引發
     *note StatisticsError: 25ee.。

     目前的演算法設計為，若在輸入當中遇到零，則會提前退出。這意味著後續
     的輸入並未進行有效性檢查。（這種行為在未來可能會改變。）

     在 3.6 版被加入.

     在 3.10 版的變更: 新增 'weights' 的支援。

 -- 函式: statistics.kde (data, h, kernel='normal', *, cumulative=False)

     Kernel Density Estimation (KDE)(3): Create a continuous probability
     density function or cumulative distribution function from discrete
     samples.

     The basic idea is to smooth the data using a kernel function(4).
     to help draw inferences about a population from a sample.

     The degree of smoothing is controlled by the scaling parameter 'h'
     which is called the bandwidth.  Smaller values emphasize local
     features while larger values give smoother results.

     The 'kernel' determines the relative weights of the sample data
     points.  Generally, the choice of kernel shape does not matter as
     much as the more influential bandwidth smoothing parameter.

     Kernels that give some weight to every sample point include
     'normal' ('gauss'), 'logistic', and 'sigmoid'.

     Kernels that only give weight to sample points within the bandwidth
     include 'rectangular' ('uniform'), 'triangular', 'parabolic'
     ('epanechnikov'), 'quartic' ('biweight'), 'triweight', and
     'cosine'.

     If 'cumulative' is true, will return a cumulative distribution
     function.

     A *note StatisticsError: 25ee. will be raised if the 'data'
     sequence is empty.

     Wikipedia has an example(5) where we can use *note kde(): 22f. to
     generate and plot a probability density function estimated from a
     small sample:

          >>> sample = [-2.1, -1.3, -0.4, 1.9, 5.1, 6.2]
          >>> f_hat = kde(sample, h=1.5)
          >>> xarr = [i/100 for i in range(-750, 1100)]
          >>> yarr = [f_hat(x) for x in xarr]

     ‘xarr’ 和 ‘yarr’ 中的點可用於繪製 PDF 圖：

[image src="python-figures/kde_example.png" alt="估計機率密度函式的散點圖 (scatter plot)。"]


     在 3.13 版被加入.

 -- 函式: statistics.kde_random (data, h, kernel='normal', *, seed=None)

     Return a function that makes a random selection from the estimated
     probability density function produced by ‘kde(data, h, kernel)’.

     Providing a 'seed' allows reproducible selections.  In the future,
     the values may change slightly as more accurate kernel inverse CDF
     estimates are implemented.  The seed may be an integer, float, str,
     or bytes.

     A *note StatisticsError: 25ee. will be raised if the 'data'
     sequence is empty.

     Continuing the example for *note kde(): 22f, we can use *note
     kde_random(): 230. to generate new random selections from an
     estimated probability density function:

          >>> data = [-2.1, -1.3, -0.4, 1.9, 5.1, 6.2]
          >>> rand = kde_random(data, h=1.5, seed=8675309)
          >>> new_selections = [rand() for i in range(10)]
          >>> [round(x, 1) for x in new_selections]
          [0.7, 6.2, 1.2, 6.9, 7.0, 1.8, 2.5, -0.5, -1.8, 5.6]

     在 3.13 版被加入.

 -- 函式: statistics.median (data)

     使用常見的「中間兩數取平均」方法回傳數值資料的中位數 （中間值）。若
     'data' 為空，則會引發 *note StatisticsError: 25ee.。'data' 可為一個
     sequence 或者 iterable。

     中位數是一種穩健的衡量資料中心位置的方法，較不易被離群值影響。當資
     料點數量為奇數時，會回傳中間的資料點：

          >>> median([1, 3, 5])
          3

     當資料點數量為偶數時，中位數透過中間兩個值的平均數來插值計算：

          >>> median([1, 3, 5, 7])
          4.0

     若你的資料為離散資料，並且你不介意中位數可能並非真實的資料點，那這
     函式適合你。

     若你的資料為順序 (ordinal) 資料（支援排序操作）但並非數值型（不支援
     加法），可以考慮改用 *note median_low(): 25e6. 或是 *note
     median_high(): 25e7. 代替。

 -- 函式: statistics.median_low (data)

     回傳數值型資料的低中位數 (low median)。若 'data' 為空，則引發 *note
     StatisticsError: 25ee.。'data' 可為 sequence 或者 iterable。

     低中位數一定會在原本的資料集當中。當資料點數量為奇數時，回傳中間值
     。當數量為偶數時，回傳兩個中間值當中較小的值。

          >>> median_low([1, 3, 5])
          3
          >>> median_low([1, 3, 5, 7])
          3

     當你的資料為離散資料，且你希望中位數是實際的資料點而不是插值時，可
     以用低中位數。

 -- 函式: statistics.median_high (data)

     回傳數值型資料的高中位數 (high median)。若 'data' 為空，則引發
     *note StatisticsError: 25ee.。'data' 可為 sequence 或者 iterable。

     高中位數一定會在原本的資料集當中。當資料點數量為奇數時，回傳中間值
     。當數量為偶數時，回傳兩個中間值當中較大的值。

          >>> median_high([1, 3, 5])
          3
          >>> median_high([1, 3, 5, 7])
          5

     當你的資料為離散資料，且你希望中位數是實際的資料點而不是插值時，可
     以用高中位數。

 -- 函式: statistics.median_grouped (data, interval=1.0)

     Estimates the median for numeric data that has been grouped or
     binned(6) around the midpoints of consecutive, fixed-width
     intervals.

     The 'data' can be any iterable of numeric data with each value
     being exactly the midpoint of a bin.  At least one value must be
     present.

     The 'interval' is the width of each bin.

     For example, demographic information may have been summarized into
     consecutive ten-year age groups with each group being represented
     by the 5-year midpoints of the intervals:

          >>> from collections import Counter
          >>> demographics = Counter({
          ...    25: 172,   # 20 to 30 years old
          ...    35: 484,   # 30 to 40 years old
          ...    45: 387,   # 40 to 50 years old
          ...    55:  22,   # 50 to 60 years old
          ...    65:   6,   # 60 to 70 years old
          ... })
          ...

     The 50th percentile (median) is the 536th person out of the 1071
     member cohort.  That person is in the 30 to 40 year old age group.

     The regular *note median(): 25e5. function would assume that
     everyone in the tricenarian age group was exactly 35 years old.  A
     more tenable assumption is that the 484 members of that age group
     are evenly distributed between 30 and 40.  For that, we use *note
     median_grouped(): 25e8.:

          >>> data = list(demographics.elements())
          >>> median(data)
          35
          >>> round(median_grouped(data, interval=10), 1)
          37.5

     The caller is responsible for making sure the data points are
     separated by exact multiples of 'interval'.  This is essential for
     getting a correct result.  The function does not check this
     precondition.

     Inputs may be any numeric type that can be coerced to a float
     during the interpolation step.

 -- 函式: statistics.mode (data)

     回傳離散或名目 'data' 中出現次數最多次的值，只回傳一個。眾數（如果
     存在）是最典型的值，並用來衡量資料的中心位置。

     若有多個出現次數相同的眾數，則回傳在 'data' 中最先出現的眾數。如果
     希望回傳其中最小或最大的眾數，可以使用 ‘min(multimode(data))’ 或
     ‘max(multimode(data))’。如果輸入的 'data' 為空，則會引發 *note
     StatisticsError: 25ee.。

     ‘mode’ 假定為離散資料，並回傳單一的值。這也是一般學校教授的標準眾數
     定義：

          >>> mode([1, 1, 2, 3, 3, 3, 3, 4])
          3

     眾數特別之處在於它是此套件中唯一也適用於名目（非數值型）資料的統計
     量：

          >>> mode(["red", "blue", "blue", "red", "green", "red", "red"])
          'red'

     Only hashable inputs are supported.  To handle type *note set: 57d,
     consider casting to *note frozenset: 57e.  To handle type *note
     list: 5b6, consider casting to *note tuple: 322.  For mixed or
     nested inputs, consider using this slower quadratic algorithm that
     only depends on equality tests: ‘max(data, key=data.count)’.

     在 3.8 版的變更: 現在，遇到資料中有多個眾數時，會回傳第一個遇到的眾
     數。在以前，當找到大於一個眾數時，會引發 *note StatisticsError:
     25ee.。

 -- 函式: statistics.multimode (data)

     回傳一個 list，其組成為 'data' 中出現次數最多次的值，並按照它們在
     'data' 中首次出現的順序排列。如果有多個眾數，將會回傳所有結果。若
     'data' 為空，則回傳空的 list：

          >>> multimode('aabbbbccddddeeffffgg')
          ['b', 'd', 'f']
          >>> multimode('')
          []

     在 3.8 版被加入.

 -- 函式: statistics.pstdev (data, mu=None)

     回傳母體標準差（即母體變異數的平方根）。有關引數以及其他細節，請參
     見 *note pvariance(): 25eb.。

          >>> pstdev([1.5, 2.5, 2.5, 2.75, 3.25, 4.75])
          0.986893273527251

 -- 函式: statistics.pvariance (data, mu=None)

     回傳 'data' 的母體變異數。'data' 可為非空實數 sequence 或者
     iterable。變異數，或者以平均數為中心的二階動差，用於衡量資料的變異
     性（離度或分散程度）。變異數大表示資料分散，變異數小表示資料集中在
     平均數附近。

     若有傳入選擇性的第二個引數 'mu'，該引數應該要是 'data' 的'母體'平均
     值 (population mean)。它也可以用於計算非以平均值為中心的第二動差。
     如果沒有傳入此引數或者引數為 ‘None’ （預設值），則自動計算資料的算
     數平均數。

     使用此函式來計算整個母體的變異數。如果要從樣本估算變異數，*note
     variance(): 677. 通常是較好的選擇。

     若 'data' 為空，則引發 *note StatisticsError: 25ee.。

     範例：

          >>> data = [0.0, 0.25, 0.25, 1.25, 1.5, 1.75, 2.75, 3.25]
          >>> pvariance(data)
          1.25

     如果已經計算出資料的平均值，你可以將其作為選擇性的第二個引數 'mu' 傳
     遞以避免重新計算：

          >>> mu = mean(data)
          >>> pvariance(data, mu)
          1.25

     支援小數 (decimal) 與分數 (fraction)：

          >>> from decimal import Decimal as D
          >>> pvariance([D("27.5"), D("30.25"), D("30.25"), D("34.5"), D("41.75")])
          Decimal('24.815')

          >>> from fractions import Fraction as F
          >>> pvariance([F(1, 4), F(5, 4), F(1, 2)])
          Fraction(13, 72)

          備註: 當在整個母體上呼叫此函式時，會回傳母體變異數 σ²。當在樣
          本上呼叫此函式時，會回傳有偏差的樣本變異數 s²，也就是具有 N 個
          自由度的變異數。

          若你以某種方式知道真正的母體平均數 μ，你可以將一個已知的母體平
          均數作為第二個引數提供給此函式，用以計算樣本的變異數。只要資料
          點是母體的隨機樣本，結果將是母體變異數的不偏估計。

 -- 函式: statistics.stdev (data, xbar=None)

     回傳樣本標準差（即樣本變異數的平方根）。有關引數以及其他細節，請參
     見 *note variance(): 677.。

          >>> stdev([1.5, 2.5, 2.5, 2.75, 3.25, 4.75])
          1.0810874155219827

 -- 函式: statistics.variance (data, xbar=None)

     回傳 'data' 的樣本變異數。'data' 為兩個值以上的實數 iterable。變異
     數，或者以平均數為中心的二階動差，用於衡量資料的變異性（離度或分散
     程度）。變異數大表示資料分散，變異數小表示資料集中在平均數附近。

     若有傳入選擇性的第二個引數 'xbar'，它應該是 'data' 的'樣本'平均值
     (sample mean)。如果沒有傳入或者為 ‘None’ （預設值），則自動計算資料
     的平均值。

     當你的資料是來自母體的樣本時，請使用此函式。若要從整個母體計算變異
     數，請參見 *note pvariance(): 25eb.。

     若 'data' 內少於兩個值，則引發 *note StatisticsError: 25ee.。

     範例：

          >>> data = [2.75, 1.75, 1.25, 0.25, 0.5, 1.25, 3.5]
          >>> variance(data)
          1.3720238095238095

     如果已經計算出資料的樣本平均值，你可以將其作為選擇性的第二個引數
     'mu' 傳遞以避免重新計算：

          >>> m = mean(data)
          >>> variance(data, m)
          1.3720238095238095

     此函式不會驗證你傳入的 'xbar' 是否為實際的平均數。傳入任意的 'xbar'
     會導致無效或不可能的結果。

     支援小數 (decimal) 與分數 (fraction)：

          >>> from decimal import Decimal as D
          >>> variance([D("27.5"), D("30.25"), D("30.25"), D("34.5"), D("41.75")])
          Decimal('31.01875')

          >>> from fractions import Fraction as F
          >>> variance([F(1, 6), F(1, 2), F(5, 3)])
          Fraction(67, 108)

          備註: 這是經過 Bessel 校正 (Bessel's correction) 後的樣本變異
          數 s² ，又稱為自由度為 N-1 的變異數。只要資料點具有代表性（例
          如：獨立且具有相同分布），結果應該會是對真實母體變異數的不偏估
          計。

          若你剛好知道真正的母體平均數 μ，你應該將其作為 'mu' 參數傳入
          *note pvariance(): 25eb. 函式來計算樣本變異數。

 -- 函式: statistics.quantiles (data, *, n=4, method='exclusive')

     將 'data' 分成 'n' 個具有相等機率的連續區間。回傳一個包含 ‘n - 1’ 個
     用於切分各區間的分隔點的 list。

     將 'n' 設為 4 以表示四分位數 (quartile) （預設值）。將 'n' 設置為
     100 表示百分位數 (percentile)，這將給出 99 個分隔點將 'data' 分成
     100 個大小相等的組。如果 'n' 不是至少為 1，則引發 *note
     StatisticsError: 25ee.。

     The 'data' can be any iterable containing sample data.  For
     meaningful results, the number of data points in 'data' should be
     larger than 'n'.  Raises *note StatisticsError: 25ee. if there is
     not at least one data point.

     分隔點是從兩個最近的資料點線性內插值計算出來的。舉例來說，如果分隔
     點落在兩個樣本值 ‘100’ 與 ‘112’ 之間的距離三分之一處，則分隔點的值
     將為 ‘104’。

     計算分位數的 'method' 可以根據 'data' 是否包含或排除來自母體的最小
     與最大可能的值而改變。

     預設的 'method' 是 "exclusive"，用於從可能找到比樣本更極端的值的母
     體中抽樣的樣本資料。對於 'm' 個已排序的資料點，計算出低於 'i-th' 的
     部分為 ‘i / (m + 1)’。給定九個樣本資料，此方法將對資料排序且計算下
     列百分位數：10%、20%、30%、40%、50%、60%、70%、80%、90%。

     若將 'method' 設為 "inclusive"，則用於描述母體或者已知包含母體中最
     極端值的樣本資料。在 'data' 中的最小值被視為第 0 百分位數，最大值為
     第 100 百分位數。對於 'm' 個已排序的資料點，計算出低於 'i-th' 的部
     分為 ‘(i - 1) / (m - 1)’。給定十一個個樣本資料，此方法將對資料排序
     且計算下列百分位數：0%、10%、20%、30%、40%、50%、60%、70%、80%、
     90%、100%。

          # Decile cut points for empirically sampled data
          >>> data = [105, 129, 87, 86, 111, 111, 89, 81, 108, 92, 110,
          ...         100, 75, 105, 103, 109, 76, 119, 99, 91, 103, 129,
          ...         106, 101, 84, 111, 74, 87, 86, 103, 103, 106, 86,
          ...         111, 75, 87, 102, 121, 111, 88, 89, 101, 106, 95,
          ...         103, 107, 101, 81, 109, 104]
          >>> [round(q, 1) for q in quantiles(data, n=10)]
          [81.0, 86.2, 89.0, 99.4, 102.5, 103.6, 106.0, 109.8, 111.0]

     在 3.8 版被加入.

     在 3.13 版的變更: No longer raises an exception for an input with
     only a single data point.  This allows quantile estimates to be
     built up one sample point at a time becoming gradually more refined
     with each new data point.

 -- 函式: statistics.covariance (x, y, /)

     回傳兩輸入 'x' 與 'y' 的樣本共變異數 (sample covariance)。共變異數
     是衡量兩輸入的聯合變異性 (joint variability) 的指標。

     兩輸入必須具有相同長度（至少兩個），否則會引發 *note
     StatisticsError: 25ee.。

     範例：

          >>> x = [1, 2, 3, 4, 5, 6, 7, 8, 9]
          >>> y = [1, 2, 3, 1, 2, 3, 1, 2, 3]
          >>> covariance(x, y)
          0.75
          >>> z = [9, 8, 7, 6, 5, 4, 3, 2, 1]
          >>> covariance(x, z)
          -7.5
          >>> covariance(z, x)
          -7.5

     在 3.10 版被加入.

 -- 函式: statistics.correlation (x, y, /, *, method='linear')

     回傳兩輸入的 Pearson 相關係數 (Pearson’s correlation
     coefficient)(7)。Pearson 相關係數 'r' 的值介於 -1 與 +1 之間。它衡
     量線性關係的強度與方向。

     如果 'method' 為 "ranked"，則計算兩輸入的 Spearman 等級相關係數
     (Spearman’s rank correlation coefficient)(8)。資料將被取代為等級。
     平手的情況則取平均，令相同的值排名也相同。所得係數衡量單調關係
     (monotonic relationship) 的強度。

     Spearman 相關係數適用於順序型資料，或者不符合 Pearson 相關係數要求
     的線性比例關係的連續型 (continuous) 資料。

     兩輸入必須具有相同長度（至少兩個），且不須為常數，否則會引發 *note
     StatisticsError: 25ee.。

     以 Kepler 行星運動定律(9)為例：

          >>> # Mercury, Venus, Earth, Mars, Jupiter, Saturn, Uranus, and  Neptune
          >>> orbital_period = [88, 225, 365, 687, 4331, 10_756, 30_687, 60_190]    # days
          >>> dist_from_sun = [58, 108, 150, 228, 778, 1_400, 2_900, 4_500] # million km

          >>> # Show that a perfect monotonic relationship exists
          >>> correlation(orbital_period, dist_from_sun, method='ranked')
          1.0

          >>> # Observe that a linear relationship is imperfect
          >>> round(correlation(orbital_period, dist_from_sun), 4)
          0.9882

          >>> # Demonstrate Kepler's third law: There is a linear correlation
          >>> # between the square of the orbital period and the cube of the
          >>> # distance from the sun.
          >>> period_squared = [p * p for p in orbital_period]
          >>> dist_cubed = [d * d * d for d in dist_from_sun]
          >>> round(correlation(period_squared, dist_cubed), 4)
          1.0

     在 3.10 版被加入.

     在 3.12 版的變更: 新增了對 Spearman 等級相關係數的支援。

 -- 函式: statistics.linear_regression (x, y, /, *, proportional=False)

     回傳使用普通最小平方法 (ordinary least square) 估計出的簡單線性迴歸
     (simple linear regression)(10) 參數中的斜率 (slope) 與截距
     (intercept)。簡單線性迴歸描述自變數 (independent variable) 'x' 與應
     變數 (dependent variable) 'y' 之間的關係，用以下的線性函式表示：

          'y = slope * x + intercept + noise'

     其中 ‘slope’ 和 ‘intercept’ 是被估計的迴歸參數，而 ‘noise’ 表示由線
     性迴歸未解釋的資料變異性（它等於應變數的預測值與實際值之差）。

     兩輸入必須具有相同長度（至少兩個），且自變數 'x' 不得為常數，否則會
     引發 *note StatisticsError: 25ee.。

     舉例來說，我們可以使用 Monty Python 系列電影的上映日期(11)來預測至
     2019 年為止，假設他們保持固定的製作速度，應該會產生的 Monty Python
     電影的累計數量。

          >>> year = [1971, 1975, 1979, 1982, 1983]
          >>> films_total = [1, 2, 3, 4, 5]
          >>> slope, intercept = linear_regression(year, films_total)
          >>> round(slope * 2019 + intercept)
          16

     若將 'proportional' 設為 True，則假設自變數 'x' 與應變數 'y' 是直接
     成比例的，資料座落在通過原點的一直線上。由於 'intercept' 始終為
     0.0，因此線性函式可簡化如下：

          'y = slope * x + noise'

     繼續 *note correlation(): 463. 中的範例，我們看看基於主要行星的模型
     可以如何很好地預測矮行星的軌道距離：

          >>> model = linear_regression(period_squared, dist_cubed, proportional=True)
          >>> slope = model.slope

          >>> # Dwarf planets:   Pluto,  Eris,    Makemake, Haumea, Ceres
          >>> orbital_periods = [90_560, 204_199, 111_845, 103_410, 1_680]  # days
          >>> predicted_dist = [math.cbrt(slope * (p * p)) for p in orbital_periods]
          >>> list(map(round, predicted_dist))
          [5912, 10166, 6806, 6459, 414]

          >>> [5_906, 10_152, 6_796, 6_450, 414]  # actual distance in million km
          [5906, 10152, 6796, 6450, 414]

     在 3.10 版被加入.

     在 3.11 版的變更: 新增 'proportional' 的支援。

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Outlier

   (2) https://en.wikipedia.org/wiki/Central_tendency

   (3) 
https://www.itm-conferences.org/articles/itmconf/pdf/2018/08/itmconf_sam2018_00037.pdf

   (4) https://en.wikipedia.org/wiki/Kernel_(statistics)

   (5) https://en.wikipedia.org/wiki/Kernel_density_estimation#Example

   (6) https://en.wikipedia.org/wiki/Data_binning

   (7) https://en.wikipedia.org/wiki/Pearson_correlation_coefficient

   (8) 
https://en.wikipedia.org/wiki/Spearman%27s_rank_correlation_coefficient

   (9) https://en.wikipedia.org/wiki/Kepler's_laws_of_planetary_motion

   (10) https://en.wikipedia.org/wiki/Simple_linear_regression

   (11) https://en.wikipedia.org/wiki/Monty_Python#Films


File: python.info,  Node: 例外<3>,  Next: NormalDist 物件,  Prev: 函式細節,  Up: statistics --- 數學統計函式

5.9.7.5 例外
............

定義了一個單一的例外：

 -- 例外: statistics.StatisticsError

     *note ValueError: 1e7. 的子類別，用於和統計相關的例外。


File: python.info,  Node: NormalDist 物件,  Next: 範例與錦囊妙計,  Prev: 例外<3>,  Up: statistics --- 數學統計函式

5.9.7.6 ‘NormalDist’ 物件
.........................

*note NormalDist: 9dc. 是一種用於建立與操作隨機變數 (random variable)(1)
的常態分布的工具。它是一個將量測資料的平均數與標準差視為單一實體的類別。

常態分布源自於中央極限定理 (Central Limit Theorem)(2)，在統計學中有著廣
泛的應用。

 -- 類別: statistics.NormalDist (mu=0.0, sigma=1.0)

     此方法會回傳一個新 'NormalDist' 物件，其中 'mu' 代表算數平均數(3)而
     'sigma' 代表標準差(4)。

     若 'sigma' 為負值，則引發 *note StatisticsError: 25ee.。

      -- 屬性: mean

          常態分布中的算數平均數(5)唯讀屬性。

      -- 屬性: median

          常態分布中的中位數(6)唯讀屬性。

      -- 屬性: mode

          常態分布中的眾數(7)唯讀屬性。

      -- 屬性: stdev

          常態分布中的標準差(8)唯讀屬性。

      -- 屬性: variance

          常態分布中的變異數(9)唯讀屬性。

      -- 方法: classmethod from_samples (data)

          利用 *note fmean(): 9d8. 與 *note stdev(): 678. 函式，估計
          'data' 的 'mu' 與 'sigma' 參數，建立一個常態分布的實例。

          'data' 可以是任何 *note iterable: 11bf.，並應包含可以轉換為
          *note float: 2c8. 的值。若 'data' 沒有包含至少兩個以上的元素在
          內，則引發 *note StatisticsError: 25ee.，因為至少需要一個點來
          估計中央值且至少需要兩個點來估計分散情形。

      -- 方法: samples (n, *, seed=None)

          給定平均值與標準差，產生 'n' 個隨機樣本。回傳一個由 *note
          float: 2c8. 組成的 *note list: 5b6.。

          若有給定 'seed'，則會建立一個以此為基礎的亂數產生器實例。這對
          於建立可重現的結果很有幫助，即使在多執行緒情境下也是如此。

          在 3.13 版的變更.

          Switched to a faster algorithm.  To reproduce samples from
          previous versions, use *note random.seed(): 120c. and *note
          random.gauss(): 1746.

      -- 方法: pdf (x)

          利用機率密度函數 (probability density function, pdf)(10) 計算
          隨機變數 'X' 接近給定值 'x' 的相對概度 (relative likelihood)。
          數學上，它是比率 ‘P(x <= X < x+dx) / dx’ 在 'dx' 趨近於零時的
          極限值。

          相對概度是樣本出現在狹窄範圍的機率，除以該範圍的寬度（故稱為「
          密度」）計算而得。由於概度是相對於其它點，故其值可大於 ‘1.0’。

      -- 方法: cdf (x)

          利用累積分布函式 (cumulative distribution function, cdf)(11) 計
          算隨機變數 'X' 小於或等於 'x' 的機率。數學上，它記為 ‘P(X <=
          x)’。

      -- 方法: inv_cdf (p)

          計算反累計分布函式 (inverse cumulative distribution function)，
          也稱為分位數函式 (quantile function)(12) 或者百分率點
          (percent-point)(13) 函式。數學上記為 ‘x : P(X <= x) = p’。

          找出一個值 'x'，使得隨機變數 'X' 小於或等於該值的機率等於給定
          的機率 'p'。

      -- 方法: overlap (other)

          衡量兩常態分布之間的一致性。回傳一個介於 0.0 與 1.0 之間的值，
          表示兩機率密度函式的重疊區域(14)。

      -- 方法: quantiles (n=4)

          將常態分布分割成 'n' 個具有相等機率的連續區間。回傳一個 list，
          包含 (n-1) 個切割區間的分隔點。

          將 'n' 設定為 4 表示四分位數（預設值）。將 'n' 設定為 10 表示
          十分位數。將 'n' 設定為 100 表示百分位數，這會產生 99 個分隔點
          ，將常態分布切割成大小相等的群組。

      -- 方法: zscore (x)

          計算標準分數 (Standard Score)(15)，用以描述在常態分布中，'x' 高
          出或低於平均數幾個標準差：‘(x - mean) / stdev’。

          在 3.9 版被加入.

     *note NormalDist: 9dc. 的實例支援對常數的加法、減法、乘法與除法。這
     些操作用於平移與縮放。例如：

          >>> temperature_february = NormalDist(5, 2.5)             # Celsius
          >>> temperature_february * (9/5) + 32                     # Fahrenheit
          NormalDist(mu=41.0, sigma=4.5)

     不支援將常數除以 *note NormalDist: 9dc. 的實例，因為結果將不符合常
     態分布。

     由於常態分布源自於自變數的加法效應 (additive effects)，因此可以將兩
     個獨立的常態分布隨機變數相加與相減(16)，並且表示為 *note
     NormalDist: 9dc. 的實例。例如：

          >>> birth_weights = NormalDist.from_samples([2.5, 3.1, 2.1, 2.4, 2.7, 3.5])
          >>> drug_effects = NormalDist(0.4, 0.15)
          >>> combined = birth_weights + drug_effects
          >>> round(combined.mean, 1)
          3.1
          >>> round(combined.stdev, 1)
          0.5

     在 3.8 版被加入.

   ---------- Footnotes ----------

   (1) http://www.stat.yale.edu/Courses/1997-98/101/ranvar.htm

   (2) https://en.wikipedia.org/wiki/Central_limit_theorem

   (3) https://en.wikipedia.org/wiki/Arithmetic_mean

   (4) https://en.wikipedia.org/wiki/Standard_deviation

   (5) https://en.wikipedia.org/wiki/Arithmetic_mean

   (6) https://en.wikipedia.org/wiki/Median

   (7) https://en.wikipedia.org/wiki/Mode_(statistics)

   (8) https://en.wikipedia.org/wiki/Standard_deviation

   (9) https://en.wikipedia.org/wiki/Variance

   (10) https://en.wikipedia.org/wiki/Probability_density_function

   (11) https://en.wikipedia.org/wiki/Cumulative_distribution_function

   (12) https://en.wikipedia.org/wiki/Quantile_function

   (13) 
https://web.archive.org/web/20190203145224/https://www.statisticshowto.datasciencecentral.com/inverse-distribution-function/

   (14) https://www.rasch.org/rmt/rmt101r.htm

   (15) 
https://www.statisticshowto.com/probability-and-statistics/z-score/

   (16) 
https://en.wikipedia.org/wiki/Sum_of_normally_distributed_random_variables


File: python.info,  Node: 範例與錦囊妙計,  Prev: NormalDist 物件,  Up: statistics --- 數學統計函式

5.9.7.7 範例與錦囊妙計
......................

* Menu:

* 經典機率問題::
* 用於模擬的蒙地卡羅 (Monte Carlo) 輸入: 用於模擬的蒙地卡羅 Monte Carlo 輸入.
* 近似二項分布::
* 單純貝氏分類器 (Naive bayesian classifier): 單純貝氏分類器 Naive bayesian classifier.


File: python.info,  Node: 經典機率問題,  Next: 用於模擬的蒙地卡羅 Monte Carlo 輸入,  Up: 範例與錦囊妙計

5.9.7.8 經典機率問題
....................

*note NormalDist: 9dc. 可以輕易地解決經典的機率問題。

例如，給定 SAT 測驗的歷史資料(1)，顯示成績為平均 1060、標準差 195 的常態
分布。我們要求出分數在 1100 與 1200 之間（四捨五入至最接近的整數）的學生
的百分比：

     >>> sat = NormalDist(1060, 195)
     >>> fraction = sat.cdf(1200 + 0.5) - sat.cdf(1100 - 0.5)
     >>> round(fraction * 100.0, 1)
     18.4

找出 SAT 分數的四分位數(2)以及十分位數(3)：

     >>> list(map(round, sat.quantiles()))
     [928, 1060, 1192]
     >>> list(map(round, sat.quantiles(n=10)))
     [810, 896, 958, 1011, 1060, 1109, 1162, 1224, 1310]

   ---------- Footnotes ----------

   (1) https://nces.ed.gov/programs/digest/d17/tables/dt17_226.40.asp

   (2) https://en.wikipedia.org/wiki/Quartile

   (3) https://en.wikipedia.org/wiki/Decile


File: python.info,  Node: 用於模擬的蒙地卡羅 Monte Carlo 輸入,  Next: 近似二項分布,  Prev: 經典機率問題,  Up: 範例與錦囊妙計

5.9.7.9 用於模擬的蒙地卡羅 (Monte Carlo) 輸入
.............................................

欲估計一個不易透過解析方法求解的模型的分布，*note NormalDist: 9dc. 可以
產生輸入樣本以進行蒙地卡羅模擬(1)：

     >>> def model(x, y, z):
     ...     return (3*x + 7*x*y - 5*y) / (11 * z)
     ...
     >>> n = 100_000
     >>> X = NormalDist(10, 2.5).samples(n, seed=3652260728)
     >>> Y = NormalDist(15, 1.75).samples(n, seed=4582495471)
     >>> Z = NormalDist(50, 1.25).samples(n, seed=6582483453)
     >>> quantiles(map(model, X, Y, Z))
     [1.4591308524824727, 1.8035946855390597, 2.175091447274739]

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Monte_Carlo_method


File: python.info,  Node: 近似二項分布,  Next: 單純貝氏分類器 Naive bayesian classifier,  Prev: 用於模擬的蒙地卡羅 Monte Carlo 輸入,  Up: 範例與錦囊妙計

5.9.7.10 近似二項分布
.....................

當樣本數量夠大，且試驗成功的機率接近 50%，可以使用常態分布來近似二項分布
(Binomial distributions)(1)。

例如，一場有 750 位參加者的開源研討會中，有兩間可容納 500 人的會議室。一
場是關於 Python 的講座，另一場則是關於 Ruby 的。在過去的會議中，有 65% 的
參加者傾向參與 Python 講座。假設參與者的偏好沒有改變，那麼 Python 會議室
未超過自身容量限制的機率是？

     >>> n = 750             # Sample size
     >>> p = 0.65            # Preference for Python
     >>> q = 1.0 - p         # Preference for Ruby
     >>> k = 500             # Room capacity

     >>> # Approximation using the cumulative normal distribution
     >>> from math import sqrt
     >>> round(NormalDist(mu=n*p, sigma=sqrt(n*p*q)).cdf(k + 0.5), 4)
     0.8402

     >>> # Exact solution using the cumulative binomial distribution
     >>> from math import comb, fsum
     >>> round(fsum(comb(n, r) * p**r * q**(n-r) for r in range(k+1)), 4)
     0.8402

     >>> # Approximation using a simulation
     >>> from random import seed, binomialvariate
     >>> seed(8675309)
     >>> mean(binomialvariate(n, p) <= k for i in range(10_000))
     0.8406

   ---------- Footnotes ----------

   (1) https://mathworld.wolfram.com/BinomialDistribution.html


File: python.info,  Node: 單純貝氏分類器 Naive bayesian classifier,  Prev: 近似二項分布,  Up: 範例與錦囊妙計

5.9.7.11 單純貝氏分類器 (Naive bayesian classifier)
...................................................

常態分布常在機器學習問題中出現。

維基百科有個 Naive Bayesian Classifier 的優良範例(1)。課題為從身高、體重
與鞋子尺寸等符合常態分布的特徵量測值中判斷一個人的性別。

給定一組包含八個人的量測值的訓練資料集。假設這些量測值服從常態分布，我們
可以利用 *note NormalDist: 9dc. 來總結資料：

     >>> height_male = NormalDist.from_samples([6, 5.92, 5.58, 5.92])
     >>> height_female = NormalDist.from_samples([5, 5.5, 5.42, 5.75])
     >>> weight_male = NormalDist.from_samples([180, 190, 170, 165])
     >>> weight_female = NormalDist.from_samples([100, 150, 130, 150])
     >>> foot_size_male = NormalDist.from_samples([12, 11, 12, 10])
     >>> foot_size_female = NormalDist.from_samples([6, 8, 7, 9])

接著，我們遇到一個新的人，他的特徵量測值已知，但性別未知：

     >>> ht = 6.0        # height
     >>> wt = 130        # weight
     >>> fs = 8          # foot size

從可能為男性或女性的 50% 先驗機率 (prior probability)(2) 為開端，我們將
後驗機率 (posterior probability) 計算為先驗機率乘以給定性別下，各特徵量
測值的概度乘積：

     >>> prior_male = 0.5
     >>> prior_female = 0.5
     >>> posterior_male = (prior_male * height_male.pdf(ht) *
     ...                   weight_male.pdf(wt) * foot_size_male.pdf(fs))

     >>> posterior_female = (prior_female * height_female.pdf(ht) *
     ...                     weight_female.pdf(wt) * foot_size_female.pdf(fs))

最終的預測結果將取決於最大的後驗機率。這被稱為最大後驗機率 (maximum a
posteriori)(3) 或者 MAP：

     >>> 'male' if posterior_male > posterior_female else 'female'
     'female'

   ---------- Footnotes ----------

   (1) 
https://en.wikipedia.org/wiki/Naive_Bayes_classifier#Person_classification

   (2) https://en.wikipedia.org/wiki/Prior_probability

   (3) https://en.wikipedia.org/wiki/Maximum_a_posteriori_estimation


File: python.info,  Node: 函式編程模組,  Next: 檔案與目錄存取,  Prev: 數值與數學模組,  Up: Python 標準函式庫 Standard Library

5.10 函式編程模組
=================

The modules described in this chapter provide functions and classes that
support a functional programming style, and general operations on
callables.

本章包含下列的模組：

* Menu:

* itertools: itertools --- 建立產生高效率迴圈之疊代器的函式. 建立產生高效率迴圈之疊代器的函式
* functools: functools --- 可呼叫物件上的高階函式與操作. 可呼叫物件上的高階函式與操作
* operator: operator --- 標準運算子替代函式. 標準運算子替代函式


File: python.info,  Node: itertools --- 建立產生高效率迴圈之疊代器的函式,  Next: functools --- 可呼叫物件上的高階函式與操作,  Up: 函式編程模組

5.10.1 ‘itertools’ -- 建立產生高效率迴圈之疊代器的函式
------------------------------------------------------

__________________________________________________________________

這個模組實作了許多 *note 疊代器 (iterator): 192. 構建塊 (building
block)，其靈感來自 APL、Haskell 和 SML 的結構。每個構建塊都以適合 Python
的形式來重新設計。

這個模組標準化了快速且高效率利用記憶體的核心工具集，這些工具本身或組合使
用都很有用。它們共同構成了一個「疊代器代數 (iterator algebra)」，使得在
純 Python 中簡潔且高效地建構專用工具成為可能。

例如，SML 提供了一個造表工具：‘tabulate(f)’，它產生一個序列 ‘f(0), f(1),
...’。在 Python 中，可以透過結合 *note map(): 808. 和 *note count():
121b. 組成 ‘map(f, count())’ 以達到同樣的效果。

這些工具及其內建的對等部分 (counterpart) 也可以很好地與 *note operator:
8f. 模組中的高速函式配合使用。例如，乘法運算子可以對映到兩個向量上以組成
高效率的內積：‘sum(starmap(operator.mul, zip(vec1, vec2,
strict=True)))’。

'無限疊代器：'

疊代器                 引數                  結果                                                  範例
                                                                                                   
-------------------------------------------------------------------------------------------------------------------------------------------------
                                                                                                   
*note count(): 121b.   [start[, step]]       start, start+step, start+2*step, ...                  ‘count(10) → 10 11 12 13 14 ...’
                                                                                                   
                                                                                                   
*note cycle(): 2607.   p                     p0, p1, ...  plast, p0, p1, ...                       ‘cycle('ABCD') → A B C D A B C D ...’
                                                                                                   
                                                                                                   
*note repeat(): 2608.  elem [,n]             elem, elem, elem，...  重複無限次或 n 次              ‘repeat(10, 3) → 10 10 10’
                                                                                                   

'在最短輸入序列 (shortest input sequence) 處終止的疊代器：'

疊代器                           引數                             結果                                                  範例
                                                                                                                        
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
                                                                                                                        
*note accumulate(): 9a1.         p [,func]                        p0, p0+p1, p0+p1+p2, ...                              ‘accumulate([1,2,3,4,5]) → 1 3 6 10 15’
                                                                                                                        
                                                                                                                        
*note batched(): 1e6.            p, n                             (p0, p1, ..., p_n-1), ...                             ‘batched('ABCDEFG', n=3) → ABC DEF G’
                                                                                                                        
                                                                                                                        
*note chain(): 205b.             p, q, ...                        p0, p1, ...  plast, q0, q1, ...                       ‘chain('ABC', 'DEF') → A B C D E F’
                                                                                                                        
                                                                                                                        
*note chain.from_iterable(): 2609.可疊代物件                      p0, p1, ...  plast, q0, q1, ...                       ‘chain.from_iterable(['ABC', 'DEF']) → A B C D E F’
                                                                                                                        
                                                                                                                        
*note compress(): 121a.          data, selectors                  (d[0] if s[0]), (d[1] if s[1]), ...                   ‘compress('ABCDEF', [1,0,1,0,1,1]) → A C E F’
                                                                                                                        
                                                                                                                        
*note dropwhile(): 260a.         predicate, seq                   seq[n], seq[n+1]，當 predicate 失敗時開始             ‘dropwhile(lambda x: x<5, [1,4,6,3,8]) → 6 3 8’
                                                                                                                        
                                                                                                                        
*note filterfalse(): 2042.       predicate, seq                   當 predicate(elem) 失敗時 seq 的元素                  ‘filterfalse(lambda x: x<5, [1,4,6,3,8]) → 6 8’
                                                                                                                        
                                                                                                                        
*note groupby(): 260b.           iterable[, key]                  根據 key(v) 的值分組的子疊代器
                                                                  
                                                                                                                        
*note islice(): af0.             seq, [start,] stop [, step]      seq[start:stop:step] 的元素                           ‘islice('ABCDEFG', 2, None) → C D E F G’
                                                                                                                        
                                                                                                                        
*note pairwise(): 7b9.           可疊代物件                       (p[0], p[1]), (p[1], p[2])                            ‘pairwise('ABCDEFG') → AB BC CD DE EF FG’
                                                                                                                        
                                                                                                                        
*note starmap(): 107d.           func, seq                        func(*seq[0]), func(*seq[1]), ...                     ‘starmap(pow, [(2,5), (3,2), (10,3)]) → 32 9 1000’
                                                                                                                        
                                                                                                                        
*note takewhile(): 260c.         predicate, seq                   seq[0], seq[1]，直到 predicate 失敗                   ‘takewhile(lambda x: x<5, [1,4,6,3,8]) → 1 4’
                                                                                                                        
                                                                                                                        
*note tee(): 260d.               it, n                            it1, it2, ...  itn，將一個疊代器分成 n 個
                                                                  
                                                                                                                        
*note zip_longest(): 1235.       p, q, ...                        (p[0], q[0]), (p[1], q[1]), ...                       ‘zip_longest('ABCD', 'xy', fillvalue='-') → Ax By C- D-’
                                                                                                                        

'組合疊代器：'

疊代器                                             引數                     結果
                                                                            
----------------------------------------------------------------------------------------------------------------------------------------------
                                                                            
*note product(): 12a7.                             p, q, ...  [repeat=1]    笛卡爾乘積 (cartesian product)，相當於巢狀的 for 迴圈
                                                                            
                                                                            
*note permutations(): 181d.                        p[, r]                   長度為 r 的元組，所有可能的定序，無重複元素
                                                                            
                                                                            
*note combinations(): 12a6.                        p, r                     長度為 r 的元組，按照排序過後的定序，無重複元素
                                                                            
                                                                            
*note combinations_with_replacement(): 1219.       p, r                     長度為 r 的元組，按照排序過後的定序，有重複元素
                                                                            

範例                                               結果
                                                   
---------------------------------------------------------------------------------------------------------------------
                                                   
‘product('ABCD', repeat=2)’                        ‘AA AB AC AD BA BB BC BD CA CB CC CD DA DB DC DD’
                                                   
                                                   
‘permutations('ABCD', 2)’                          ‘AB AC AD BA BC BD CA CB CD DA DB DC’
                                                   
                                                   
‘combinations('ABCD', 2)’                          ‘AB AC AD BC BD CD’
                                                   
                                                   
‘combinations_with_replacement('ABCD', 2)’         ‘AA AB AC AD BB BC BD CC CD DD’
                                                   

* Menu:

* Itertool 函式::
* Itertools 應用技巧::


File: python.info,  Node: Itertool 函式,  Next: Itertools 應用技巧,  Up: itertools --- 建立產生高效率迴圈之疊代器的函式

5.10.1.1 Itertool 函式
......................

以下的模組函式都會建構並回傳疊代器。一些函式提供無限長度的串流 (stream)，
因此應僅由截斷串流的函式或迴圈來存取它們。

 -- 函式: itertools.accumulate (iterable[, function, *, initial=None])

     建立一個回傳累積和的疊代器，或其他二進位函式的累積結果。

     'function' 預設為加法。'function' 應接受兩個引數，即累積總和和來自
     'iterable' 的值。

     如果提供了 'initial' 值，則累積將從該值開始，並且輸出的元素數將比輸
     入的可疊代物件多一個。

     大致等價於：

          def accumulate(iterable, function=operator.add, *, initial=None):
              'Return running totals'
              # accumulate([1,2,3,4,5]) → 1 3 6 10 15
              # accumulate([1,2,3,4,5], initial=100) → 100 101 103 106 110 115
              # accumulate([1,2,3,4,5], operator.mul) → 1 2 6 24 120

              iterator = iter(iterable)
              total = initial
              if initial is None:
                  try:
                      total = next(iterator)
                  except StopIteration:
                      return

              yield total
              for element in iterator:
                  total = function(total, element)
                  yield total

     'function' 引數可以被設定為 *note min(): eac. 以得到連續的最小值，
     設定為 *note max(): ead. 以得到連續的最大值，或者設定為 *note
     operator.mul(): 2610. 以得到連續的乘積。也可以透過累積利息和付款來
     建立攤銷表 (Amortization tables)(1) ：

          >>> data = [3, 4, 6, 2, 1, 9, 0, 7, 5, 8]
          >>> list(accumulate(data, max))              # running maximum
          [3, 4, 6, 6, 6, 9, 9, 9, 9, 9]
          >>> list(accumulate(data, operator.mul))     # running product
          [3, 12, 72, 144, 144, 1296, 0, 0, 0, 0]

          # Amortize a 5% loan of 1000 with 10 annual payments of 90
          >>> update = lambda balance, payment: round(balance * 1.05) - payment
          >>> list(accumulate(repeat(90, 10), update, initial=1_000))
          [1000, 960, 918, 874, 828, 779, 728, 674, 618, 559, 497]

     可參見 *note functools.reduce(): 126f.，其是個類似的函式，但僅回傳
     最終的累積值。

     在 3.2 版被加入.

     在 3.3 版的變更: 新增可選的 'function' 參數。

     在 3.8 版的變更: 新增可選的 'initial' 參數。

 -- 函式: itertools.batched (iterable, n, *, strict=False)

     將來自 'iterable' 的資料分批為長度為 'n' 的元組。最後一個批次可能比
     'n' 短。

     If 'strict' is true, will raise a *note ValueError: 1e7. if the
     final batch is shorter than 'n'.

     對輸入的可疊代物件進行迴圈，並將資料累積到大小為 'n' 的元組中。輸入
     是惰性地被消耗 (consumed lazily) 的，會剛好足夠填充一批的資料。一旦
     批次填滿或輸入的可疊代物件耗盡，就會 yield 出結果：

          >>> flattened_data = ['roses', 'red', 'violets', 'blue', 'sugar', 'sweet']
          >>> unflattened = list(batched(flattened_data, 2))
          >>> unflattened
          [('roses', 'red'), ('violets', 'blue'), ('sugar', 'sweet')]

     大致等價於：

          def batched(iterable, n, *, strict=False):
              # batched('ABCDEFG', 3) → ABC DEF G
              if n < 1:
                  raise ValueError('n must be at least one')
              iterator = iter(iterable)
              while batch := tuple(islice(iterator, n)):
                  if strict and len(batch) != n:
                      raise ValueError('batched(): incomplete batch')
                  yield batch

     在 3.12 版被加入.

     在 3.13 版的變更: Added the 'strict' option.

 -- 函式: itertools.chain (*iterables)

     建立一個疊代器，從第一個可疊代物件回傳元素直到其耗盡，然後繼續處理
     下一個可疊代物件，直到所有可疊代物件都耗盡。用於將連續的序列做為單
     一序列處理。大致等價於：

          def chain(*iterables):
              # chain('ABC', 'DEF') → A B C D E F
              for iterable in iterables:
                  yield from iterable

 -- 方法: classmethod chain.from_iterable (iterable)

     *note chain(): 205b. 的另一個建構函式。從單個可疊代的引數中得到鏈接
     的輸入，該引數是惰性計算的。大致等價於：

          def from_iterable(iterables):
              # chain.from_iterable(['ABC', 'DEF']) → A B C D E F
              for iterable in iterables:
                  yield from iterable

 -- 函式: itertools.combinations (iterable, r)

     從輸入 'iterable' 中回傳長度為 'r' 的元素的子序列。

     輸出是 *note product(): 12a7. 的子序列，僅保留作為 'iterable' 子序
     列的條目。輸出的長度由 *note math.comb(): 674. 給定，當 ‘0 ≤ r ≤ n’
     時，長度為 ‘n! / r! / (n - r)!’，當 ‘r > n’ 時為零。

     根據輸入值 'iterable' 的順序，組合的元組會按照字典順序輸出。如果輸
     入的 'iterable' 已經排序，則輸出的元組也將按排序的順序產生。

     元素是根據它們的位置（而非值）來決定其唯一性。如果輸入的元素都是獨
     特的，則每個組合內將不會有重複的值。

     大致等價於：

          def combinations(iterable, r):
              # combinations('ABCD', 2) → AB AC AD BC BD CD
              # combinations(range(4), 3) → 012 013 023 123

              pool = tuple(iterable)
              n = len(pool)
              if r > n:
                  return
              indices = list(range(r))

              yield tuple(pool[i] for i in indices)
              while True:
                  for i in reversed(range(r)):
                      if indices[i] != i + n - r:
                          break
                  else:
                      return
                  indices[i] += 1
                  for j in range(i+1, r):
                      indices[j] = indices[j-1] + 1
                  yield tuple(pool[i] for i in indices)

 -- 函式: itertools.combinations_with_replacement (iterable, r)

     回傳來自輸入 'iterable' 的長度為 'r' 的子序列，且允許個別元素重複多
     次。

     其輸出是一個 *note product(): 12a7. 的子序列，僅保留作為 'iterable'
     子序列（可能有重複元素）的條目。當 ‘n > 0’ 時，回傳的子序列數量為
     ‘(n + r - 1)! / r! / (n - 1)!’。

     根據輸入值 'iterable' 的順序，組合的元組會按照字典順序輸出。如果輸
     入的 'iterable' 已經排序，則輸出的元組也將按排序的順序產生。

     元素是根據它們的位置（而非值）來決定其唯一性。如果輸入的元素都是獨
     特的，生成的組合也將是獨特的。

     大致等價於：

          def combinations_with_replacement(iterable, r):
              # combinations_with_replacement('ABC', 2) → AA AB AC BB BC CC

              pool = tuple(iterable)
              n = len(pool)
              if not n and r:
                  return
              indices = [0] * r

              yield tuple(pool[i] for i in indices)
              while True:
                  for i in reversed(range(r)):
                      if indices[i] != n - 1:
                          break
                  else:
                      return
                  indices[i:] = [indices[i] + 1] * (r - i)
                  yield tuple(pool[i] for i in indices)

     在 3.1 版被加入.

 -- 函式: itertools.compress (data, selectors)

     建立一個疊代器，回傳 'data' 中對應 'selectors' 的元素為 true 的元素
     。當 'data' 或 'selectors' 可疊代物件耗盡時停止。大致等價於：

          def compress(data, selectors):
              # compress('ABCDEF', [1,0,1,0,1,1]) → A C E F
              return (datum for datum, selector in zip(data, selectors) if selector)

     在 3.1 版被加入.

 -- 函式: itertools.count (start=0, step=1)

     建立一個疊代器，回傳從 'start' 開始的等差的值。可以與 *note map():
     808. 一起使用來產生連續的資料點，或與 *note zip(): 774. 一起使用來
     增加序列號。大致等價於：

          def count(start=0, step=1):
              # count(10) → 10 11 12 13 14 ...
              # count(2.5, 0.5) → 2.5 3.0 3.5 ...
              n = start
              while True:
                  yield n
                  n += step

     當用浮點數計數時，將上述程式碼替換為乘法有時可以獲得更好的精確度，
     例如：‘(start + step * i for i in count())’。

     在 3.1 版的變更: 新增 'step' 引數並允許非整數引數。

 -- 函式: itertools.cycle (iterable)

     建立一個疊代器，回傳 'iterable' 中的元素並保存每個元素的副本。當可
     疊代物件耗盡時，從保存的副本中回傳元素。會無限次的重複。大致等價於
     ：

          def cycle(iterable):
              # cycle('ABCD') → A B C D A B C D A B C D ...
              saved = []
              for element in iterable:
                  yield element
                  saved.append(element)
              while saved:
                  for element in saved:
                      yield element

     此 itertool 可能需要大量的輔助儲存空間（取決於可疊代物件的長度）。

 -- 函式: itertools.dropwhile (predicate, iterable)

     建立一個疊代器，在 'predicate' 為 true 時丟棄 'iterable' 中的元素，
     之後回傳每個元素。大致等價於：

          def dropwhile(predicate, iterable):
              # dropwhile(lambda x: x<5, [1,4,6,3,8]) → 6 3 8

              iterator = iter(iterable)
              for x in iterator:
                  if not predicate(x):
                      yield x
                      break

              for x in iterator:
                  yield x

     注意，在 predicate 首次變為 False 之前，這不會產生'任何'輸出，所以
     此 itertool 可能會有較長的啟動時間。

 -- 函式: itertools.filterfalse (predicate, iterable)

     建立一個疊代器，過濾 'iterable' 中的元素，僅回傳 'predicate' 為
     False 值的元素。如果 'predicate' 是 ‘None’，則回傳為 False 的項目。
     大致等價於：

          def filterfalse(predicate, iterable):
              # filterfalse(lambda x: x<5, [1,4,6,3,8]) → 6 8
              if predicate is None:
                  predicate = bool
              for x in iterable:
                  if not predicate(x):
                      yield x

 -- 函式: itertools.groupby (iterable, key=None)

     建立一個疊代器，回傳 'iterable' 中連續的鍵和群組。'key' 是一個為每
     個元素計算鍵值的函式。如果其未指定或為 ‘None’，則 'key' 預設為一個
     識別性函式 (identity function)，並回傳未被更改的元素。一般來說，可
     疊代物件需要已經用相同的鍵函式進行排序。

     *note groupby(): 260b. 的操作類似於 Unix 中的 ‘uniq’ 過濾器。每當鍵
     函式的值發生變化時，它會產生一個 break 或新的群組（這就是為什麼通常
     需要使用相同的鍵函式對資料進行排序）。這種行為不同於 SQL 的 GROUP
     BY，其無論輸入順序如何都會聚合相同的元素。

     回傳的群組本身是一個與 *note groupby(): 260b. 共享底層可疊代物件的
     疊代器。由於來源是共享的，當 *note groupby(): 260b. 物件前進時，前
     一個群組將不再可見。因此，如果之後需要該資料，應將其儲存為串列：

          groups = []
          uniquekeys = []
          data = sorted(data, key=keyfunc)
          for k, g in groupby(data, keyfunc):
              groups.append(list(g))      # Store group iterator as a list
              uniquekeys.append(k)

     *note groupby(): 260b. 大致等價於：

          def groupby(iterable, key=None):
              # [k for k, g in groupby('AAAABBBCCDAABBB')] → A B C D A B
              # [list(g) for k, g in groupby('AAAABBBCCD')] → AAAA BBB CC D

              keyfunc = (lambda x: x) if key is None else key
              iterator = iter(iterable)
              exhausted = False

              def _grouper(target_key):
                  nonlocal curr_value, curr_key, exhausted
                  yield curr_value
                  for curr_value in iterator:
                      curr_key = keyfunc(curr_value)
                      if curr_key != target_key:
                          return
                      yield curr_value
                  exhausted = True

              try:
                  curr_value = next(iterator)
              except StopIteration:
                  return
              curr_key = keyfunc(curr_value)

              while not exhausted:
                  target_key = curr_key
                  curr_group = _grouper(target_key)
                  yield curr_key, curr_group
                  if curr_key == target_key:
                      for _ in curr_group:
                          pass

 -- 函式: itertools.islice (iterable, stop)

 -- 函式: itertools.islice (iterable, start, stop[, step])

     建立一個疊代器，回傳從 iterable 中選取的元素。其作用類似於序列切片
     (sequence slicing)，但不支援負數的 'start'、'stop' 或 'step' 的值。

     如果 'start' 為零或 ‘None’，則從零開始疊代。否則在達到 'start' 之前
     ，會跳過 iterable 中的元素。

     如果 'stop' 為 ‘None’，則疊代將繼續前進直到疊代器耗盡。如果指定了
     'stop'，則在達到指定位置時停止。

     如果 'step' 為 ‘None’，則步長 (step) 預設為一。元素會連續回傳，除非
     將 'step' 設定為大於一，這會導致一些項目被跳過。

     大致等價於：

          def islice(iterable, *args):
              # islice('ABCDEFG', 2) → A B
              # islice('ABCDEFG', 2, 4) → C D
              # islice('ABCDEFG', 2, None) → C D E F G
              # islice('ABCDEFG', 0, None, 2) → A C E G

              s = slice(*args)
              start = 0 if s.start is None else s.start
              stop = s.stop
              step = 1 if s.step is None else s.step
              if start < 0 or (stop is not None and stop < 0) or step <= 0:
                  raise ValueError

              indices = count() if stop is None else range(max(start, stop))
              next_i = start
              for i, element in zip(indices, iterable):
                  if i == next_i:
                      yield element
                      next_i += step

 -- 函式: itertools.pairwise (iterable)

     回傳從輸入的 'iterable' 中提取的連續重疊對。

     輸出疊代器中的 2 元組數量將比輸入少一個。如果輸入的可疊代物件中的值
     少於兩個，則輸出將為空值。

     大致等價於：

          def pairwise(iterable):
              # pairwise('ABCDEFG') → AB BC CD DE EF FG
              iterator = iter(iterable)
              a = next(iterator, None)
              for b in iterator:
                  yield a, b
                  a = b

     在 3.10 版被加入.

 -- 函式: itertools.permutations (iterable, r=None)

     回傳 'iterable' 中連續且長度為 'r' 的元素排列(2) 。

     如果未指定 'r' 或其值為 ‘None’，則 'r' 預設為 'iterable' 的長度，並
     產生所有可能的完整長度的排列。

     輸出是 *note product(): 12a7. 的子序列，其中重複元素的條目已被濾除
     。輸出的長度由 *note math.perm(): 675. 給定，當 ‘0 ≤ r ≤ n’ 時，長
     度為 ‘n! / (n - r)!’，當 ‘r > n’ 時為零。

     根據輸入值 'iterable' 的順序，排列的元組會按照字典順序輸出。如果輸
     入的 'iterable' 已排序，則輸出的元組也將按排序的順序產生。

     元素是根據它們的位置（而非值）來決定其唯一性。如果輸入的元素都是獨
     特的，則排列中將不會有重複的值。

     大致等價於：

          def permutations(iterable, r=None):
              # permutations('ABCD', 2) → AB AC AD BA BC BD CA CB CD DA DB DC
              # permutations(range(3)) → 012 021 102 120 201 210

              pool = tuple(iterable)
              n = len(pool)
              r = n if r is None else r
              if r > n:
                  return

              indices = list(range(n))
              cycles = list(range(n, n-r, -1))
              yield tuple(pool[i] for i in indices[:r])

              while n:
                  for i in reversed(range(r)):
                      cycles[i] -= 1
                      if cycles[i] == 0:
                          indices[i:] = indices[i+1:] + indices[i:i+1]
                          cycles[i] = n - i
                      else:
                          j = cycles[i]
                          indices[i], indices[-j] = indices[-j], indices[i]
                          yield tuple(pool[i] for i in indices[:r])
                          break
                  else:
                      return

 -- 函式: itertools.product (*iterables, repeat=1)

     輸入的 iterables 的笛卡爾乘積。

     大致等價於產生器運算式中的巢狀 for 迴圈。例如，‘product(A, B)’ 的回
     傳結果與 ‘((x,y) for x in A for y in B)’ 相同。

     巢狀迴圈的循環類似於里程表，最右邊的元素在每次疊代時前進。這種模式
     會建立字典順序，因此如果輸入的 iterables 已排序，則輸出的乘積元組也
     將按排序的順序產生。

     要計算可疊代物件自身的乘積，可以使用可選的 'repeat' 關鍵字引數來指
     定重複次數。例如，‘product(A, repeat=4)’ 與 ‘product(A, A, A, A)’ 相
     同。

     此函式大致等價於以下的程式碼，不同之處在於真正的實作不會在記憶體中
     建立中間結果：

          def product(*iterables, repeat=1):
              # product('ABCD', 'xy') → Ax Ay Bx By Cx Cy Dx Dy
              # product(range(2), repeat=3) → 000 001 010 011 100 101 110 111

              pools = [tuple(pool) for pool in iterables] * repeat

              result = [[]]
              for pool in pools:
                  result = [x+[y] for x in result for y in pool]

              for prod in result:
                  yield tuple(prod)

     在 *note product(): 12a7. 執行之前，它會完全消耗輸入的 iterables，
     並將值的池 (pools of values) 保存在記憶體中以產生乘積。因此，它僅對
     有限的輸入有用。

 -- 函式: itertools.repeat (object[, times])

     建立一個疊代器，反覆回傳 'object'。除非指定了 'times' 引數，否則會
     執行無限次。

     大致等價於：

          def repeat(object, times=None):
              # repeat(10, 3) → 10 10 10
              if times is None:
                  while True:
                      yield object
              else:
                  for i in range(times):
                      yield object

     'repeat' 的常見用途是為 'map' 或 'zip' 提供定值的串流：

          >>> list(map(pow, range(10), repeat(2)))
          [0, 1, 4, 9, 16, 25, 36, 49, 64, 81]

 -- 函式: itertools.starmap (function, iterable)

     建立一個疊代器，使用從 'iterable' 獲取的引數計算 'function' 。當引
     數參數已經被「預先壓縮 (pre-zipped)」成元組時，使用此方法代替 *note
     map(): 808.。

     *note map(): 808. 和 *note starmap(): 107d. 之間的區別類似於
     ‘function(a,b)’ 和 ‘function(*c)’ 之間的區別。大致等價於：

          def starmap(function, iterable):
              # starmap(pow, [(2,5), (3,2), (10,3)]) → 32 9 1000
              for args in iterable:
                  yield function(*args)

 -- 函式: itertools.takewhile (predicate, iterable)

     建立一個疊代器，只在 'predicate' 為 true 時回傳 'iterable' 中的元素
     。大致等價於：

          def takewhile(predicate, iterable):
              # takewhile(lambda x: x<5, [1,4,6,3,8]) → 1 4
              for x in iterable:
                  if not predicate(x):
                      break
                  yield x

     注意，第一個不符合條件判斷的元素將從輸入疊代器中被消耗，且無法再存
     取它。如果應用程式希望在 'takewhile' 耗盡後進一步消耗輸入疊代器，這
     可能會是個問題。為了解決這個問題，可以考慮使用 more-itertools 中的
     before_and_after()(3) 作為替代。

 -- 函式: itertools.tee (iterable, n=2)

     從一個 iterable 中回傳 'n' 個獨立的疊代器。

     大致等價於：

          def tee(iterable, n=2):
              iterator = iter(iterable)
              shared_link = [None, None]
              return tuple(_tee(iterator, shared_link) for _ in range(n))

          def _tee(iterator, link):
              try:
                  while True:
                      if link[1] is None:
                          link[0] = next(iterator)
                          link[1] = [None, None]
                      value, link = link
                      yield value
              except StopIteration:
                  return

     一旦建立了 *note tee(): 260d.，原始的 'iterable' 不應在其他地方使用
     ；否則，'iterable' 可能會在 tee 物件未被通知的情況下前進。

     ‘tee’ 疊代器不是執行緒安全 (threadsafe) 的。當同時使用由同一個
     *note tee(): 260d. 呼叫所回傳的疊代器時，即使原始的 'iterable' 是執
     行緒安全的，也可能引發 *note RuntimeError: 179.。

     此 itertool 可能需要大量的輔助儲存空間（取決於需要儲存多少臨時資料
     ）。通常如果一個疊代器在另一個疊代器開始之前使用了大部分或全部的資
     料，使用 *note list(): 5b6. 會比 *note tee(): 260d. 更快。

 -- 函式: itertools.zip_longest (*iterables, fillvalue=None)

     建立一個疊代器，聚合來自每個 'iterables' 中的元素。

     如果 iterables 的長度不一，則使用 'fillvalue' 填充缺少的值。如果未
     指定，'fillvalue' 會預設為 ‘None’。

     疊代將持續直到最長的可疊代物件耗盡為止。

     大致等價於：

          def zip_longest(*iterables, fillvalue=None):
              # zip_longest('ABCD', 'xy', fillvalue='-') → Ax By C- D-

              iterators = list(map(iter, iterables))
              num_active = len(iterators)
              if not num_active:
                  return

              while True:
                  values = []
                  for i, iterator in enumerate(iterators):
                      try:
                          value = next(iterator)
                      except StopIteration:
                          num_active -= 1
                          if not num_active:
                              return
                          iterators[i] = repeat(fillvalue)
                          value = fillvalue
                      values.append(value)
                  yield tuple(values)

     如果其中一個 iterables 可能是無限的，那麼應該用別的可以限制呼叫次數
     的方法來包裝 *note zip_longest(): 1235. 函式（例如 *note islice():
     af0. 或 *note takewhile(): 260c.）。

   ---------- Footnotes ----------

   (1) https://www.ramseysolutions.com/real-estate/amortization-schedule

   (2) https://www.britannica.com/science/permutation

   (3) 
https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.before_and_after


File: python.info,  Node: Itertools 應用技巧,  Prev: Itertool 函式,  Up: itertools --- 建立產生高效率迴圈之疊代器的函式

5.10.1.2 Itertools 應用技巧
...........................

此段落展示了使用現有的 itertools 作為構建塊來建立擴展工具集的應用技巧。

itertools 應用技巧的主要目的是教學。這些應用技巧展示了對單個工具進行思考
的各種方式 —— 例如，‘chain.from_iterable’ 與攤平 (flattening) 的概念相關
。這些應用技巧還提供了組合使用工具的想法 —— 例如，‘starmap()’ 和
‘repeat()’ 如何一起工作。另外還展示了將 itertools 與 *note operator: 8f.
和 *note collections: 16. 模組一同使用以及與內建 itertools（如 ‘map()’、
‘filter()’、‘reversed()’ 和 ‘enumerate()’）一同使用的模式。

應用技巧的次要目的是作為 itertools 的孵化器。‘accumulate()’,
‘compress()’ 和 ‘pairwise()’ itertools 最初都是作為應用技巧出現的。目前
，‘sliding_window()’、‘iter_index()’ 和 ‘sieve()’ 的應用技巧正在被測試，
以確定它們是否有價值被收錄到內建的 itertools 中。

幾乎所有這些應用技巧以及許多其他應用技巧都可以從 Python Package Index 上
的 more-itertools(1) 專案中安裝：

     python -m pip install more-itertools

許多應用技巧提供了與底層工具集相同的高性能。透過一次處理一個元素而不是將
整個可疊代物件一次性引入記憶體，能保持優異的記憶體性能。以函式風格
(functional style)(2) 將工具連接在一起，能將程式碼的數量維持在較少的情況
。透過優先使用「向量化 (vectorized)」的構建塊而不是使用會造成直譯器負擔
的 for 迴圈和*note 產生器: 1004.，則能保持高速度。

     import collections
     import contextlib
     import functools
     import math
     import operator
     import random

     def take(n, iterable):
         "Return first n items of the iterable as a list."
         return list(islice(iterable, n))

     def prepend(value, iterable):
         "Prepend a single value in front of an iterable."
         # prepend(1, [2, 3, 4]) → 1 2 3 4
         return chain([value], iterable)

     def tabulate(function, start=0):
         "Return function(0), function(1), ..."
         return map(function, count(start))

     def repeatfunc(func, times=None, *args):
         "Repeat calls to func with specified arguments."
         if times is None:
             return starmap(func, repeat(args))
         return starmap(func, repeat(args, times))

     def flatten(list_of_lists):
         "Flatten one level of nesting."
         return chain.from_iterable(list_of_lists)

     def ncycles(iterable, n):
         "Returns the sequence elements n times."
         return chain.from_iterable(repeat(tuple(iterable), n))

     def tail(n, iterable):
         "Return an iterator over the last n items."
         # tail(3, 'ABCDEFG') → E F G
         return iter(collections.deque(iterable, maxlen=n))

     def consume(iterator, n=None):
         "Advance the iterator n-steps ahead. If n is None, consume entirely."
         # Use functions that consume iterators at C speed.
         if n is None:
             collections.deque(iterator, maxlen=0)
         else:
             next(islice(iterator, n, n), None)

     def nth(iterable, n, default=None):
         "Returns the nth item or a default value."
         return next(islice(iterable, n, None), default)

     def quantify(iterable, predicate=bool):
         "Given a predicate that returns True or False, count the True results."
         return sum(map(predicate, iterable))

     def first_true(iterable, default=False, predicate=None):
         "Returns the first true value or the *default* if there is no true value."
         # first_true([a,b,c], x) → a or b or c or x
         # first_true([a,b], x, f) → a if f(a) else b if f(b) else x
         return next(filter(predicate, iterable), default)

     def all_equal(iterable, key=None):
         "Returns True if all the elements are equal to each other."
         # all_equal('4٤௪౪໔', key=int) → True
         return len(take(2, groupby(iterable, key))) <= 1

     def unique_justseen(iterable, key=None):
         "Yield unique elements, preserving order. Remember only the element just seen."
         # unique_justseen('AAAABBBCCDAABBB') → A B C D A B
         # unique_justseen('ABBcCAD', str.casefold) → A B c A D
         if key is None:
             return map(operator.itemgetter(0), groupby(iterable))
         return map(next, map(operator.itemgetter(1), groupby(iterable, key)))

     def unique_everseen(iterable, key=None):
         "Yield unique elements, preserving order. Remember all elements ever seen."
         # unique_everseen('AAAABBBCCDAABBB') → A B C D
         # unique_everseen('ABBcCAD', str.casefold) → A B c D
         seen = set()
         if key is None:
             for element in filterfalse(seen.__contains__, iterable):
                 seen.add(element)
                 yield element
         else:
             for element in iterable:
                 k = key(element)
                 if k not in seen:
                     seen.add(k)
                     yield element

     def unique(iterable, key=None, reverse=False):
        "Yield unique elements in sorted order. Supports unhashable inputs."
        # unique([[1, 2], [3, 4], [1, 2]]) → [1, 2] [3, 4]
        return unique_justseen(sorted(iterable, key=key, reverse=reverse), key=key)

     def sliding_window(iterable, n):
         "Collect data into overlapping fixed-length chunks or blocks."
         # sliding_window('ABCDEFG', 4) → ABCD BCDE CDEF DEFG
         iterator = iter(iterable)
         window = collections.deque(islice(iterator, n - 1), maxlen=n)
         for x in iterator:
             window.append(x)
             yield tuple(window)

     def grouper(iterable, n, *, incomplete='fill', fillvalue=None):
         "Collect data into non-overlapping fixed-length chunks or blocks."
         # grouper('ABCDEFG', 3, fillvalue='x') → ABC DEF Gxx
         # grouper('ABCDEFG', 3, incomplete='strict') → ABC DEF ValueError
         # grouper('ABCDEFG', 3, incomplete='ignore') → ABC DEF
         iterators = [iter(iterable)] * n
         match incomplete:
             case 'fill':
                 return zip_longest(*iterators, fillvalue=fillvalue)
             case 'strict':
                 return zip(*iterators, strict=True)
             case 'ignore':
                 return zip(*iterators)
             case _:
                 raise ValueError('Expected fill, strict, or ignore')

     def roundrobin(*iterables):
         "Visit input iterables in a cycle until each is exhausted."
         # roundrobin('ABC', 'D', 'EF') → A D E B F C
         # Algorithm credited to George Sakkis
         iterators = map(iter, iterables)
         for num_active in range(len(iterables), 0, -1):
             iterators = cycle(islice(iterators, num_active))
             yield from map(next, iterators)

     def partition(predicate, iterable):
         """Partition entries into false entries and true entries.

         If *predicate* is slow, consider wrapping it with functools.lru_cache().
         """
         # partition(is_odd, range(10)) → 0 2 4 6 8   and  1 3 5 7 9
         t1, t2 = tee(iterable)
         return filterfalse(predicate, t1), filter(predicate, t2)

     def subslices(seq):
         "Return all contiguous non-empty subslices of a sequence."
         # subslices('ABCD') → A AB ABC ABCD B BC BCD C CD D
         slices = starmap(slice, combinations(range(len(seq) + 1), 2))
         return map(operator.getitem, repeat(seq), slices)

     def iter_index(iterable, value, start=0, stop=None):
         "Return indices where a value occurs in a sequence or iterable."
         # iter_index('AABCADEAF', 'A') → 0 1 4 7
         seq_index = getattr(iterable, 'index', None)
         if seq_index is None:
             iterator = islice(iterable, start, stop)
             for i, element in enumerate(iterator, start):
                 if element is value or element == value:
                     yield i
         else:
             stop = len(iterable) if stop is None else stop
             i = start
             with contextlib.suppress(ValueError):
                 while True:
                     yield (i := seq_index(value, i, stop))
                     i += 1

     def iter_except(func, exception, first=None):
         "Convert a call-until-exception interface to an iterator interface."
         # iter_except(d.popitem, KeyError) → non-blocking dictionary iterator
         with contextlib.suppress(exception):
             if first is not None:
                 yield first()
             while True:
                 yield func()

以下的應用技巧具有更多的數學風格：

     def powerset(iterable):
         "powerset([1,2,3]) → () (1,) (2,) (3,) (1,2) (1,3) (2,3) (1,2,3)"
         s = list(iterable)
         return chain.from_iterable(combinations(s, r) for r in range(len(s)+1))

     def sum_of_squares(iterable):
         "Add up the squares of the input values."
         # sum_of_squares([10, 20, 30]) → 1400
         return math.sumprod(*tee(iterable))

     def reshape(matrix, cols):
         "Reshape a 2-D matrix to have a given number of columns."
         # reshape([(0, 1), (2, 3), (4, 5)], 3) →  (0, 1, 2), (3, 4, 5)
         return batched(chain.from_iterable(matrix), cols, strict=True)

     def transpose(matrix):
         "Swap the rows and columns of a 2-D matrix."
         # transpose([(1, 2, 3), (11, 22, 33)]) → (1, 11) (2, 22) (3, 33)
         return zip(*matrix, strict=True)

     def matmul(m1, m2):
         "Multiply two matrices."
         # matmul([(7, 5), (3, 5)], [(2, 5), (7, 9)]) → (49, 80), (41, 60)
         n = len(m2[0])
         return batched(starmap(math.sumprod, product(m1, transpose(m2))), n)

     def convolve(signal, kernel):
         """Discrete linear convolution of two iterables.
         Equivalent to polynomial multiplication.

         Convolutions are mathematically commutative; however, the inputs are
         evaluated differently.  The signal is consumed lazily and can be
         infinite. The kernel is fully consumed before the calculations begin.

         Article:  https://betterexplained.com/articles/intuitive-convolution/
         Video:    https://www.youtube.com/watch?v=KuXjwB4LzSA
         """
         # convolve([1, -1, -20], [1, -3]) → 1 -4 -17 60
         # convolve(data, [0.25, 0.25, 0.25, 0.25]) → Moving average (blur)
         # convolve(data, [1/2, 0, -1/2]) → 1st derivative estimate
         # convolve(data, [1, -2, 1]) → 2nd derivative estimate
         kernel = tuple(kernel)[::-1]
         n = len(kernel)
         padded_signal = chain(repeat(0, n-1), signal, repeat(0, n-1))
         windowed_signal = sliding_window(padded_signal, n)
         return map(math.sumprod, repeat(kernel), windowed_signal)

     def polynomial_from_roots(roots):
         """Compute a polynomial's coefficients from its roots.

            (x - 5) (x + 4) (x - 3)  expands to:   x³ -4x² -17x + 60
         """
         # polynomial_from_roots([5, -4, 3]) → [1, -4, -17, 60]
         factors = zip(repeat(1), map(operator.neg, roots))
         return list(functools.reduce(convolve, factors, [1]))

     def polynomial_eval(coefficients, x):
         """Evaluate a polynomial at a specific value.

         Computes with better numeric stability than Horner's method.
         """
         # Evaluate x³ -4x² -17x + 60 at x = 5
         # polynomial_eval([1, -4, -17, 60], x=5) → 0
         n = len(coefficients)
         if not n:
             return type(x)(0)
         powers = map(pow, repeat(x), reversed(range(n)))
         return math.sumprod(coefficients, powers)

     def polynomial_derivative(coefficients):
         """Compute the first derivative of a polynomial.

            f(x)  =  x³ -4x² -17x + 60
            f'(x) = 3x² -8x  -17
         """
         # polynomial_derivative([1, -4, -17, 60]) → [3, -8, -17]
         n = len(coefficients)
         powers = reversed(range(1, n))
         return list(map(operator.mul, coefficients, powers))

     def sieve(n):
         "Primes less than n."
         # sieve(30) → 2 3 5 7 11 13 17 19 23 29
         if n > 2:
             yield 2
         data = bytearray((0, 1)) * (n // 2)
         for p in iter_index(data, 1, start=3, stop=math.isqrt(n) + 1):
             data[p*p : n : p+p] = bytes(len(range(p*p, n, p+p)))
         yield from iter_index(data, 1, start=3)

     def factor(n):
         "Prime factors of n."
         # factor(99) → 3 3 11
         # factor(1_000_000_000_000_007) → 47 59 360620266859
         # factor(1_000_000_000_000_403) → 1000000000000403
         for prime in sieve(math.isqrt(n) + 1):
             while not n % prime:
                 yield prime
                 n //= prime
                 if n == 1:
                     return
         if n > 1:
             yield n

     def totient(n):
         "Count of natural numbers up to n that are coprime to n."
         # https://mathworld.wolfram.com/TotientFunction.html
         # totient(12) → 4 because len([1, 5, 7, 11]) == 4
         for prime in set(factor(n)):
             n -= n // prime
         return n

   ---------- Footnotes ----------

   (1) https://pypi.org/project/more-itertools/

   (2) https://www.cs.kent.ac.uk/people/staff/dat/miranda/whyfp90.pdf


File: python.info,  Node: functools --- 可呼叫物件上的高階函式與操作,  Next: operator --- 標準運算子替代函式,  Prev: itertools --- 建立產生高效率迴圈之疊代器的函式,  Up: 函式編程模組

5.10.2 ‘functools’ -- 可呼叫物件上的高階函式與操作
--------------------------------------------------

'原始碼：'Lib/functools.py(1)

__________________________________________________________________

*note functools: 55. 模組用於高階函式：作用於或回傳其他函式的函式。一般
來說，任何可呼叫物件都可以被視為用於此模組的函式。

*note functools: 55. 模組定義了以下函式：

 -- 函式: @functools.cache (user_function)

     簡單的輕量級無繫結函式快取 (Simple lightweight unbounded function
     cache)。有時稱之為 "memoize"（記憶化）(2)。

     和 ‘lru_cache(maxsize=None)’ 回傳相同的值，為函式引數建立一個字典查
     找的薄包裝器。因為它永遠不需要丟棄舊值，所以這比有大小限制的 *note
     lru_cache(): 993. 更小、更快。

     舉例來說：

          @cache
          def factorial(n):
              return n * factorial(n-1) if n else 1

          >>> factorial(10)      # no previously cached result, makes 11 recursive calls
          3628800
          >>> factorial(5)       # just looks up cached value result
          120
          >>> factorial(12)      # makes two new recursive calls, the other 10 are cached
          479001600

     該快取是執行緒安全的 (threadsafe)，因此包裝的函式可以在多個執行緒中
     使用。這意味著底層資料結構在並行更新期間將保持連貫 (coherent)。

     如果另一個執行緒在初始呼叫完成並快取之前進行額外的呼叫，則包裝的函
     式可能會被多次呼叫。

     在 3.9 版被加入.

 -- 函式: @functools.cached_property (func)

     將類別的一個方法轉換為屬性 (property)，其值會計算一次，然後在實例的
     生命週期內快取為普通屬性。類似 *note property(): 180.，但增加了快取
     機制。對於除使用該裝飾器的屬性外實質上幾乎是不可變 (immutable) 的實
     例，針對其所需要繁重計算會很有用。

     範例：

          class DataSet:

              def __init__(self, sequence_of_numbers):
                  self._data = tuple(sequence_of_numbers)

              @cached_property
              def stdev(self):
                  return statistics.stdev(self._data)

     *note cached_property(): 4e7. 的機制與 *note property(): 180. 有所
     不同。除非定義了 setter，否則常規屬性會阻止屬性的寫入。相反地，
     'cached_property' 則允許寫入。

     'cached_property' 裝飾器僅在查找時且僅在同名屬性不存在時運行。當它
     運行時，'cached_property' 會寫入同名的屬性。後續屬性讀取和寫入優先
     於 'cached_property' 方法，並且它的工作方式與普通屬性類似。

     可以透過刪除屬性來清除快取的值，這使得 'cached_property' 方法可以再
     次運行。

     'cached_property' 無法防止多執行緒使用中可能出現的競爭條件 (race
     condition)。getter 函式可以在同一個實例上運行多次，最後一次運行會設
     定快取的值。所以快取的屬性最好是冪等的 (idempotent)，或者在一個實例
     上運行多次不會有害，就不會有問題。如果同步是必要的，請在裝飾的
     getter 函式內部或在快取的屬性存取周圍實作必要的鎖。

     請注意，此裝飾器會干擾 PEP 412(3) 金鑰共用字典的操作。這意味著實例
     字典可能比平常佔用更多的空間。

     此外，此裝飾器要求每個實例上的 ‘__dict__’ 屬性是可變對映 (mutable
     mapping)。這意味著它不適用於某些型別，例如元類別 (metaclass)（因為
     型別實例上的 ‘__dict__’ 屬性是類別命名空間的唯讀代理），以及那些指
     定 ‘__slots__’ 而不包含 ‘__dict__’ 的型別作為有定義的插槽之一（因為
     此種類別根本不提供 ‘__dict__’ 屬性）。

     如果可變對映不可用或需要金鑰共享以節省空間，則也可以透過在 *note
     lru_cache(): 993. 之上堆疊 *note property(): 180. 來實作類似於
     *note cached_property(): 4e7. 的效果。請參閱*note
     如何快取方法呼叫？: 2614.以了解有關這與 *note cached_property():
     4e7. 間不同之處的更多詳細資訊。

     在 3.8 版被加入.

     在 3.12 版的變更: 在 Python 3.12 之前，‘cached_property’ 包含一個未
     以文件記錄的鎖，以確保在多執行緒使用中能保證 getter 函式對於每個實
     例只會執行一次。然而，鎖是針對每個屬性，而不是針對每個實例，這可能
     會導致無法被接受的嚴重鎖爭用 (lock contention)。在 Python 3.12+ 中
     ，此鎖已被刪除。

 -- 函式: functools.cmp_to_key (func)

     將舊式比較函式轉換為*note 鍵函式: dab.，能與接受鍵函式的工具一起使
     用（例如 *note sorted(): b75.、*note min(): eac.、*note max():
     ead.、*note heapq.nlargest(): 240b.、*note heapq.nsmallest():
     240c.、*note itertools.groupby(): 260b.）。此函式主要作為轉換工具，
     用於從有支援使用比較函式的 Python 2 轉換成的程式。

     比較函式是任何能接受兩個引數、對它們進行比較，並回傳負數（小於）、
     零（相等）或正數（大於）的可呼叫物件。鍵函式是接受一個引數並回傳另
     一個用作排序鍵之值的可呼叫物件。

     範例：

          sorted(iterable, key=cmp_to_key(locale.strcoll))  # locale-aware sort order

     有關排序範例和簡短的排序教學，請參閱*note 排序技法: 205a.。

     在 3.2 版被加入.

 -- 函式: @functools.lru_cache (user_function)

 -- 函式: @functools.lru_cache (maxsize=128, typed=False)

     以記憶化可呼叫物件來包裝函式的裝飾器，最多可省去 'maxsize' 個最近的
     呼叫。當使用相同引數定期呼叫繁重的或 I/O 密集的函式時，它可以節省時
     間。

     該快取是執行緒安全的 (threadsafe)，因此包裝的函式可以在多個執行緒中
     使用。這意味著底層資料結構在並行更新期間將保持連貫 (coherent)。

     如果另一個執行緒在初始呼叫完成並快取之前進行額外的呼叫，則包裝的函
     式可能會被多次呼叫。

     由於字典用於快取結果，因此函式的位置引數和關鍵字引數必須是*note
     可雜湊的: 5b5.。

     不同的引數模式可以被認為是具有不同快取條目的不同呼叫。例如，‘f(a=1,
     b=2)’ 和 ‘f(b=2, a=1)’ 的關鍵字引數順序不同，並且可能有兩個不同的快
     取條目。

     如果指定了 'user_function'，則它必須是個可呼叫物件。這使得
     'lru_cache' 裝飾器能夠直接應用於使用者函式，將 'maxsize' 保留為其預
     設值 128：

          @lru_cache
          def count_vowels(sentence):
              return sum(sentence.count(vowel) for vowel in 'AEIOUaeiou')

     如果 'maxsize' 設定為 ‘None’，則 LRU 功能將被停用，且快取可以無限制
     地成長。

     如果 'typed' 設定為 true，不同型別的函式引數將會被單獨快取起來。如
     果 'typed' 為 false，則實作通常會將它們視為等效呼叫，並且僅快取單一
     結果。（某些型別，例如 'str' 和 'int' 可能會被單獨快取起來，即使
     'typed' 為 false。）

     請注意，型別特異性 (type specificity) 僅適用於函式的直接引數而不是
     其內容。純量 (scalar) 引數 ‘Decimal(42)’ 和 ‘Fraction(42)’ 被視為具
     有不同結果的不同呼叫。相反地，元組引數 ‘('answer', Decimal(42))’ 和
     ‘('answer', Fraction(42))’ 被視為等效。

     包裝的函式使用一個 ‘cache_parameters()’ 函式來進行偵測，該函式回傳
     一個新的 *note dict: 23b. 以顯示 'maxsize' 和 'typed' 的值。這僅能
     顯示資訊，改變其值不會有任何效果。

     為了輔助測量快取的有效性並調整 'maxsize' 參數，包裝的函式使用了一個
     ‘cache_info()’ 函式來做檢測，該函式會回傳一個*note 附名元組: 5f4.來
     顯示 'hits'、'misses'、'maxsize' 和 'currsize'。

     裝飾器還提供了一個 ‘cache_clear()’ 函式來清除或使快取失效。

     原本的底層函式可以透過 ‘__wrapped__’ 屬性存取。這對於要自我檢查
     (introspection)、繞過快取或使用不同的快取重新包裝函式時非常有用。

     快取會保留對引數和回傳值的參照，直到快取過時 (age out) 或快取被清除
     為止。

     如果方法被快取起來，則 ‘self’ 實例引數將包含在快取中。請參閱*note
     如何快取方法呼叫？: 2614.

     當最近的呼叫是即將發生之呼叫的最佳預測因子時（例如新聞伺服器上最受
     歡迎的文章往往每天都會發生變化），LRU (least recently used) 快取
     (4)能發揮最好的效果。快取的大小限制可確保快取不會在長時間運行的行程
     （例如 Web 伺服器）上無限制地成長。

     一般來說，僅當你想要重複使用先前計算的值時才應使用 LRU 快取。因此，
     快取具有 side-effects 的函式、需要在每次呼叫時建立不同可變物件的函
     式（例如產生器和非同步函式）或不純函式（impure function，例如
     time() 或 random()）是沒有意義的。

     靜態網頁內容的 LRU 快取範例：

          @lru_cache(maxsize=32)
          def get_pep(num):
              'Retrieve text of a Python Enhancement Proposal'
              resource = f'https://peps.python.org/pep-{num:04d}'
              try:
                  with urllib.request.urlopen(resource) as s:
                      return s.read()
              except urllib.error.HTTPError:
                  return 'Not Found'

          >>> for n in 8, 290, 308, 320, 8, 218, 320, 279, 289, 320, 9991:
          ...     pep = get_pep(n)
          ...     print(n, len(pep))

          >>> get_pep.cache_info()
          CacheInfo(hits=3, misses=8, maxsize=32, currsize=8)

     使用快取來實作動態規劃 (dynamic programming)(5) 技法以有效率地計算
     費波那契數 (Fibonacci numbers)(6) 的範例：

          @lru_cache(maxsize=None)
          def fib(n):
              if n < 2:
                  return n
              return fib(n-1) + fib(n-2)

          >>> [fib(n) for n in range(16)]
          [0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89, 144, 233, 377, 610]

          >>> fib.cache_info()
          CacheInfo(hits=28, misses=16, maxsize=None, currsize=16)

     在 3.2 版被加入.

     在 3.3 版的變更: 新增 'typed' 選項。

     在 3.8 版的變更: 新增 'user_function' 選項。

     在 3.9 版的變更: 新增 ‘cache_parameters()’ 函式。

 -- 函式: @functools.total_ordering

     給定一個定義一個或多個 rich comparison 排序方法的類別，該類別裝飾器
     會提供其餘部分。這簡化了指定所有可能的 rich comparison 操作所涉及的
     工作：

     類別必須定義 ‘__lt__()’、‘__le__()’、‘__gt__()’ 或 ‘__ge__()’ 其中
     之一。此外，該類別應該提供 ‘__eq__()’ 方法。

     舉例來說：

          @total_ordering
          class Student:
              def _is_valid_operand(self, other):
                  return (hasattr(other, "lastname") and
                          hasattr(other, "firstname"))
              def __eq__(self, other):
                  if not self._is_valid_operand(other):
                      return NotImplemented
                  return ((self.lastname.lower(), self.firstname.lower()) ==
                          (other.lastname.lower(), other.firstname.lower()))
              def __lt__(self, other):
                  if not self._is_valid_operand(other):
                      return NotImplemented
                  return ((self.lastname.lower(), self.firstname.lower()) <
                          (other.lastname.lower(), other.firstname.lower()))

          備註: 雖然此裝飾器可以輕鬆建立能好好運作的完全有序型別
          (totally ordered types)，但它'的確'以衍生比較方法的執行速度較
          慢和堆疊追蹤 (stack trace) 較複雜做為其代價。如果效能基準測試
          顯示這是給定應用程式的效能瓶頸，那麼實作全部六種 rich
          comparison 方法通常能輕鬆地提升速度。

          備註: 此裝飾器不會嘗試覆寫類別'或其超類別 (superclass)'中宣告
          的方法。這意味著如果超類別定義了比較運算子，'total_ordering' 將
          不會再次實作它，即使原始方法是抽象的。

     在 3.2 版被加入.

     在 3.4 版的變更: 現在支援從底層對於未識別型別的比較函式回傳
     ‘NotImplemented’。

 -- 函式: functools.partial (func, /, *args, **keywords)

     回傳一個新的 *note partial 物件: 2615.，它在被呼叫時的行為類似於使
     用位置引數 'args' 和關鍵字引數 'keywords' 呼叫的 'func'。如果向呼叫
     提供更多引數，它們將被附加到 'args'。如果提供了額外的關鍵字引數，它
     們會擴充並覆寫 'keywords'。大致相當於：

          def partial(func, /, *args, **keywords):
              def newfunc(*fargs, **fkeywords):
                  newkeywords = {**keywords, **fkeywords}
                  return func(*args, *fargs, **newkeywords)
              newfunc.func = func
              newfunc.args = args
              newfunc.keywords = keywords
              return newfunc

     *note partial(): 356. 用於部分函式應用程序，它「凍結」函式引數和/或
     關鍵字的某些部分，從而產生具有簡化簽名的新物件。例如，*note
     partial(): 356. 可用來建立可呼叫函式，其行為類似於 *note int():
     23c. 函式，其中 'base' 引數預設為 2：

          >>> from functools import partial
          >>> basetwo = partial(int, base=2)
          >>> basetwo.__doc__ = 'Convert base 2 string to an int.'
          >>> basetwo('10010')
          18

 -- 類別: functools.partialmethod (func, /, *args, **keywords)

     回傳一個新的 *note partialmethod: a1e. 描述器 (descriptor)，其行為
     類似於 *note partial: 356.，只不過它被設計為用於方法定義而不能直接
     呼叫。

     'func' 必須是一個 *note descriptor: 1e47. 或可呼叫物件（兩者兼具的
     物件，就像普通函式一樣，會被當作描述器處理）。

     當 'func' 是描述器時（例如普通的 Python 函式、*note classmethod():
     14a.、*note staticmethod(): 358.、‘abstractmethod()’ 或 *note
     partialmethod: a1e. 的另一個實例），對 ‘__get__’ 的呼叫將被委託
     (delegated) 給底層描述器，且一個適當的 *note partial 物件: 2615.會
     被作為結果回傳。

     當 'func' 是非描述器可呼叫物件 (non-descriptor callable) 時，會動態
     建立適當的繫結方法 (bound method)。當被作為方法使用時，其行為類似於
     普通的 Python 函式：'self' 引數將作為第一個位置引數插入，甚至會在提
     供給 *note partialmethod: a1e. 建構函式的 'args' 和 'keywords' 的前
     面。

     範例：

          >>> class Cell:
          ...     def __init__(self):
          ...         self._alive = False
          ...     @property
          ...     def alive(self):
          ...         return self._alive
          ...     def set_state(self, state):
          ...         self._alive = bool(state)
          ...     set_alive = partialmethod(set_state, True)
          ...     set_dead = partialmethod(set_state, False)
          ...
          >>> c = Cell()
          >>> c.alive
          False
          >>> c.set_alive()
          >>> c.alive
          True

     在 3.4 版被加入.

 -- 函式: functools.reduce (function, iterable[, initial], /)

     Apply 'function' of two arguments cumulatively to the items of
     'iterable', from left to right, so as to reduce the iterable to a
     single value.  For example, ‘reduce(lambda x, y: x+y, [1, 2, 3, 4,
     5])’ calculates ‘((((1+2)+3)+4)+5)’.  The left argument, 'x', is
     the accumulated value and the right argument, 'y', is the update
     value from the 'iterable'.  If the optional 'initial' is present,
     it is placed before the items of the iterable in the calculation,
     and serves as a default when the iterable is empty.  If 'initial'
     is not given and 'iterable' contains only one item, the first item
     is returned.

     大致相當於：

          initial_missing = object()

          def reduce(function, iterable, initial=initial_missing, /):
              it = iter(iterable)
              if initial is initial_missing:
                  value = next(it)
              else:
                  value = initial
              for element in it:
                  value = function(value, element)
              return value

     請參閱 *note itertools.accumulate(): 9a1. 以了解產生 (yield) 所有中
     間值 (intermediate value) 的疊代器。

 -- 函式: @functools.singledispatch

     將函式轉換為*note 單一調度: 996.*note 泛型函式: 995.。

     若要定義泛型函式，請使用 ‘@singledispatch’ 裝飾器對其裝飾。請注意，
     使用 ‘@singledispatch’ 定義函式時，分派調度 (dispatch) 是發生在第一
     個引數的型別上：

          >>> from functools import singledispatch
          >>> @singledispatch
          ... def fun(arg, verbose=False):
          ...     if verbose:
          ...         print("Let me just say,", end=" ")
          ...     print(arg)

     若要為函式新增過載實作，請使用泛型函式的 ‘register()’ 屬性，該屬性
     可用作裝飾器。對於以型別來註釋的函式，裝飾器將自動推斷第一個引數的
     型別：

          >>> @fun.register
          ... def _(arg: int, verbose=False):
          ...     if verbose:
          ...         print("Strength in numbers, eh?", end=" ")
          ...     print(arg)
          ...
          >>> @fun.register
          ... def _(arg: list, verbose=False):
          ...     if verbose:
          ...         print("Enumerate this:")
          ...     for i, elem in enumerate(arg):
          ...         print(i, elem)

     也可以使用 *note types.UnionType: 5e0. 和 *note typing.Union: 5e1.：

          >>> @fun.register
          ... def _(arg: int | float, verbose=False):
          ...     if verbose:
          ...         print("Strength in numbers, eh?", end=" ")
          ...     print(arg)
          ...
          >>> from typing import Union
          >>> @fun.register
          ... def _(arg: Union[list, set], verbose=False):
          ...     if verbose:
          ...         print("Enumerate this:")
          ...     for i, elem in enumerate(arg):
          ...         print(i, elem)
          ...

     對於不使用型別註釋的程式碼，可以將適當的型別引數明確傳遞給裝飾器本
     身：

          >>> @fun.register(complex)
          ... def _(arg, verbose=False):
          ...     if verbose:
          ...         print("Better than complicated.", end=" ")
          ...     print(arg.real, arg.imag)
          ...

     若要啟用註冊 *note lambdas: 2616. 和預先存在的函式，‘register()’ 屬
     性也能以函式形式使用：

          >>> def nothing(arg, verbose=False):
          ...     print("Nothing.")
          ...
          >>> fun.register(type(None), nothing)

     ‘register()’ 屬性回傳未加裝飾器的函式。這讓使得裝飾器堆疊
     (decorator stacking)、*note pickling: 95. 以及為每個變體獨立建立單
     元測試成為可能：

          >>> @fun.register(float)
          ... @fun.register(Decimal)
          ... def fun_num(arg, verbose=False):
          ...     if verbose:
          ...         print("Half of your number:", end=" ")
          ...     print(arg / 2)
          ...
          >>> fun_num is fun
          False

     呼叫時，泛型函式會分派第一個引數的型別：

          >>> fun("Hello, world.")
          Hello, world.
          >>> fun("test.", verbose=True)
          Let me just say, test.
          >>> fun(42, verbose=True)
          Strength in numbers, eh? 42
          >>> fun(['spam', 'spam', 'eggs', 'spam'], verbose=True)
          Enumerate this:
          0 spam
          1 spam
          2 eggs
          3 spam
          >>> fun(None)
          Nothing.
          >>> fun(1.23)
          0.615

     如果沒有為特定型別註冊實作，則使用其方法解析順序 (method resolution
     order) 來尋找更通用的實作。用 ‘@singledispatch’ 裝飾的原始函式是為
     基底 *note object: a2f. 型別註冊的，這意味著如果沒有找到更好的實作
     就會使用它。

     如果一個實作有被註冊到一個*note 抽象基底類別: 114e.，則基底類別的虛
     擬子類別將被分派到該實作：

          >>> from collections.abc import Mapping
          >>> @fun.register
          ... def _(arg: Mapping, verbose=False):
          ...     if verbose:
          ...         print("Keys & Values")
          ...     for key, value in arg.items():
          ...         print(key, "=>", value)
          ...
          >>> fun({"a": "b"})
          a => b

     若要檢查泛型函式將為給定型別選擇哪種實作，請使用 ‘dispatch()’ 屬性
     ：

          >>> fun.dispatch(float)
          <function fun_num at 0x1035a2840>
          >>> fun.dispatch(dict)    # note: default implementation
          <function fun at 0x103fe0000>

     若要存取所有已註冊的實作，請使用唯讀 ‘registry’ 屬性：

          >>> fun.registry.keys()
          dict_keys([<class 'NoneType'>, <class 'int'>, <class 'object'>,
                    <class 'decimal.Decimal'>, <class 'list'>,
                    <class 'float'>])
          >>> fun.registry[float]
          <function fun_num at 0x1035a2840>
          >>> fun.registry[object]
          <function fun at 0x103fe0000>

     在 3.4 版被加入.

     在 3.7 版的變更: ‘register()’ 屬性現在支援使用型別註釋。

     在 3.11 版的變更: ‘register()’ 屬性現在支援以 *note
     types.UnionType: 5e0. 和 *note typing.Union: 5e1. 作為型別註釋。

 -- 類別: functools.singledispatchmethod (func)

     將方法轉換為*note 單一調度: 996.*note 泛型函式: 995.。

     若要定義泛型方法，請使用 ‘@singledispatchmethod’ 裝飾器對其裝飾。請
     注意，使用 ‘@singledispatchmethod’ 定義函式時，分派調度是發生在第一
     個非 'self' 或非 'cls' 引數的型別上：

          class Negator:
              @singledispatchmethod
              def neg(self, arg):
                  raise NotImplementedError("Cannot negate a")

              @neg.register
              def _(self, arg: int):
                  return -arg

              @neg.register
              def _(self, arg: bool):
                  return not arg

     ‘@singledispatchmethod’ 支援與其他裝飾器巢狀使用 (nesting)，例如
     *note @classmethod: 14a.。請注意，為了使 ‘dispatcher.register’ 可用
     ，‘singledispatchmethod’ 必須是'最外面的'裝飾器。以下範例是
     ‘Negator’ 類別，其 ‘neg’ 方法繫結到該類別，而不是該類別的實例：

          class Negator:
              @singledispatchmethod
              @classmethod
              def neg(cls, arg):
                  raise NotImplementedError("Cannot negate a")

              @neg.register
              @classmethod
              def _(cls, arg: int):
                  return -arg

              @neg.register
              @classmethod
              def _(cls, arg: bool):
                  return not arg

     相同的模式可用於其他類似的裝飾器：*note @staticmethod: 358.、*note
     @abstractmethod: 1027. 等。

     在 3.8 版被加入.

 -- 函式: functools.update_wrapper (wrapper, wrapped,
          assigned=WRAPPER_ASSIGNMENTS, updated=WRAPPER_UPDATES)

     更新 'wrapper' 函式，使其看起來像 'wrapped' 函式。可選引數是元組，
     用於指定原始函式的哪些屬性直接賦值給包裝函式上的匹配屬性，以及包裝
     函式的哪些屬性使用原始函式中的對應屬性進行更新。這些引數的預設值是
     模組層級的常數 ‘WRAPPER_ASSIGNMENTS’（它賦值給包裝函式的
     ‘__module__’、‘__name__’、‘__qualname__’、‘__annotations__’ 和
     ‘__doc__’ 文件字串 (docstring）和 ‘WRAPPER_UPDATES’（更新包裝器函式
     的 ‘__dict__’，即實例字典）。

     為了允許出於內省 (introspection) 和其他目的所對原始函式的存取（例如
     繞過快取裝飾器，如 *note lru_cache(): 993.），此函式會自動向包裝器
     新增 ‘__wrapped__’ 屬性，該包裝器參照被包裝的函式。

     此函式的主要用途是在 *note decorator: 6d5. 函式中，它包裝函式並回傳
     包裝器。如果包裝器函式未更新，則回傳函式的元資料 (metadata) 將反映
     包裝器定義而非原始函式定義，這通常不太會有幫助。

     *note update_wrapper(): fc5. 可以與函式以外的可呼叫物件一起使用。被
     包裝的物件中缺少的 'assigned' 或 'updated' 中指定的任何屬性都將被忽
     略（即此函式不會嘗試在包裝器函式上設定它們）。如果包裝函式本身缺少
     'updated' 中指定的任何屬性，仍然會引發 *note AttributeError: 2f6.。

     在 3.2 版的變更: 現在會自動新增 ‘__wrapped__’ 屬性。現在預設會複製
     ‘__annotations__’ 屬性。缺少的屬性不再觸發 *note AttributeError:
     2f6.。

     在 3.4 版的變更: ‘__wrapped__’ 屬性現在都會參照包裝函式，即便函式有
     定義 ‘__wrapped__’ 屬性。（參見 bpo-17482(7)）

     在 3.12 版的變更: 現在預設會複製 ‘__type_params__’ 屬性。

 -- 函式: @functools.wraps (wrapped, assigned=WRAPPER_ASSIGNMENTS,
          updated=WRAPPER_UPDATES)

     這是一個方便的函式，用於在定義包裝器函式時呼叫 *note
     update_wrapper(): fc5. 作為函式裝飾器。它相當於
     ‘partial(update_wrapper, wrapped=wrapped, assigned=assigned,
     updated=updated)’。例如：

          >>> from functools import wraps
          >>> def my_decorator(f):
          ...     @wraps(f)
          ...     def wrapper(*args, **kwds):
          ...         print('Calling decorated function')
          ...         return f(*args, **kwds)
          ...     return wrapper
          ...
          >>> @my_decorator
          ... def example():
          ...     """Docstring"""
          ...     print('Called example function')
          ...
          >>> example()
          Calling decorated function
          Called example function
          >>> example.__name__
          'example'
          >>> example.__doc__
          'Docstring'

     如果不使用這個裝飾器工廠 (decorator factory)，範例函式的名稱將會是
     ‘'wrapper'’，並且原始 ‘example()’ 的文件字串將會遺失。

* Menu:

* partial 物件::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/functools.py

   (2) https://en.wikipedia.org/wiki/Memoization

   (3) https://peps.python.org/pep-0412/

   (4) 
https://en.wikipedia.org/wiki/Cache_replacement_policies#Least_recently_used_(LRU)

   (5) https://en.wikipedia.org/wiki/Dynamic_programming

   (6) https://en.wikipedia.org/wiki/Fibonacci_number

   (7) https://bugs.python.org/issue?@action=redirect&bpo=17482


File: python.info,  Node: partial 物件,  Up: functools --- 可呼叫物件上的高階函式與操作

5.10.2.1 ‘partial’ 物件
.......................

*note partial: 356. 物件是由 *note partial(): 356. 所建立的可呼叫物件。
它們有三個唯讀屬性：

 -- 屬性: partial.func

     一個可呼叫的物件或函式。對 *note partial: 356. 物件的呼叫將被轉送到
     帶有新引數和關鍵字的 *note func: 2618.。

 -- 屬性: partial.args

     最左邊的位置引數將會被加入到提供給 *note partial: 356. 物件呼叫的位
     置引數的前面。

 -- 屬性: partial.keywords

     呼叫 *note partial: 356. 物件時將提供的關鍵字引數。

*note partial: 356. 物件與 ‘function’ 物件類似，因為它們是可呼叫的、可弱
參照的 (weak referencable) 且可以具有屬性。有一些重要的區別，例如，*note
__name__: 1416. 和 ‘__doc__’ 屬性不會自動建立。此外，類別中定義的 *note
partial: 356. 物件的行為類似於靜態方法，並且在實例屬性查找期間不會轉換為
繫結方法。


File: python.info,  Node: operator --- 標準運算子替代函式,  Prev: functools --- 可呼叫物件上的高階函式與操作,  Up: 函式編程模組

5.10.3 ‘operator’ -- 標準運算子替代函式
---------------------------------------

'原始碼：'Lib/operator.py(1)

__________________________________________________________________

*note operator: 8f. module（模組）提供了一套與 Python 原生運算子對應的高
效率函式。例如，‘operator.add(x, y)’ 與表示式 ‘x+y’ 相同。許多函式名與特
殊方法名相同，只是沒有雙底線。為了向後相容，許多包含雙底線的函式被保留了
下來，但為了易於表達，建議使用沒有雙底線的函式。

函式種類有物件的比較運算、邏輯運算、數學運算以及序列運算。

物件比較函式適用於所有物件，函式根據它們對應的 rich comparison 運算子命
名：

 -- 函式: operator.lt (a, b)
 -- 函式: operator.le (a, b)
 -- 函式: operator.eq (a, b)
 -- 函式: operator.ne (a, b)
 -- 函式: operator.ge (a, b)
 -- 函式: operator.gt (a, b)
 -- 函式: operator.__lt__ (a, b)
 -- 函式: operator.__le__ (a, b)
 -- 函式: operator.__eq__ (a, b)
 -- 函式: operator.__ne__ (a, b)
 -- 函式: operator.__ge__ (a, b)
 -- 函式: operator.__gt__ (a, b)

     在 'a' 和 'b' 之間進行 "rich comparison"。具體來說，‘lt(a, b)’ 與
     ‘a < b’ 相同，‘le(a, b)’ 與 ‘a <= b’ 相同，‘eq(a, b)’ 與 ‘a == b’ 相
     同，‘ne(a, b)’ 與 ‘a != b’ 相同，‘gt(a, b)’ 與 ‘a > b’ 相同，‘ge(a,
     b)’ 與 ‘a >= b’ 相同。注意這些函式可以回傳任何值，無論它是否可當作
     boolean（布林）值。關於 rich comparison 的更多資訊請參考 *note
     Comparisons: 1f4c.。

邏輯運算通常也適用於所有物件，並且支援真值檢測、識別性測試和 boolean 運
算：

 -- 函式: operator.not_ (obj)
 -- 函式: operator.__not__ (obj)

     回傳 *note not: 1f56. 'obj' 的結果。（請注意物件實例並沒有
     ‘__not__()’ method（方法）；只有直譯器核心定義此操作。結果會受
     *note __bool__(): 1268. 和 *note __len__(): 1e38. method 影響。）

 -- 函式: operator.truth (obj)

     如果 'obj' 為真值則回傳 *note True: bb4.，否則回傳 *note False:
     adb.。這等價於使用 *note bool: 40e. 建構器。

 -- 函式: operator.is_ (a, b)

     回傳 ‘a is b’。測試物件識別性。

 -- 函式: operator.is_not (a, b)

     回傳 ‘a is not b’。測試物件識別性。

數學和位元運算的種類是最多的：

 -- 函式: operator.abs (obj)
 -- 函式: operator.__abs__ (obj)

     回傳 'obj' 的絕對值。

 -- 函式: operator.add (a, b)
 -- 函式: operator.__add__ (a, b)

     對於數字 'a' 和 'b'，回傳 ‘a + b’。

 -- 函式: operator.and_ (a, b)
 -- 函式: operator.__and__ (a, b)

     回傳 'x' 和 'y' 位元運算與 (and) 的結果。

 -- 函式: operator.floordiv (a, b)
 -- 函式: operator.__floordiv__ (a, b)

     回傳 ‘a // b’。

 -- 函式: operator.index (a)
 -- 函式: operator.__index__ (a)

     回傳 'a' 轉換為整數的結果。等價於 ‘a.__index__()’。

     在 3.10 版的變更: 結果總是 *note int: 23c. 型別。在過去的版本中，結
     果可能為 ‘int’ 子類別的實例。

 -- 函式: operator.inv (obj)
 -- 函式: operator.invert (obj)
 -- 函式: operator.__inv__ (obj)
 -- 函式: operator.__invert__ (obj)

     回傳數字 'obj' 按位元取反 (inverse) 的結果。這等價於 ‘~obj’。

 -- 函式: operator.lshift (a, b)
 -- 函式: operator.__lshift__ (a, b)

     回傳 'a' 左移 'b' 位的結果。

 -- 函式: operator.mod (a, b)
 -- 函式: operator.__mod__ (a, b)

     回傳 ‘a % b’。

 -- 函式: operator.mul (a, b)
 -- 函式: operator.__mul__ (a, b)

     對於數字 'a' 和 'b'，回傳 ‘a * b’。

 -- 函式: operator.matmul (a, b)
 -- 函式: operator.__matmul__ (a, b)

     回傳 ‘a @ b’。

     在 3.5 版被加入.

 -- 函式: operator.neg (obj)
 -- 函式: operator.__neg__ (obj)

     回傳 'obj' 取負值的結果 (‘-obj’)。

 -- 函式: operator.or_ (a, b)
 -- 函式: operator.__or__ (a, b)

     回傳 'a' 和 'b' 按位元或 (or) 的結果。

 -- 函式: operator.pos (obj)
 -- 函式: operator.__pos__ (obj)

     回傳 'obj' 取正的結果 (‘+obj’)。

 -- 函式: operator.pow (a, b)
 -- 函式: operator.__pow__ (a, b)

     對於數字 'a' 和 'b'，回傳 ‘a ** b’。

 -- 函式: operator.rshift (a, b)
 -- 函式: operator.__rshift__ (a, b)

     回傳 'a' 右移 'b' 位的結果。

 -- 函式: operator.sub (a, b)
 -- 函式: operator.__sub__ (a, b)

     回傳 ‘a - b’。

 -- 函式: operator.truediv (a, b)
 -- 函式: operator.__truediv__ (a, b)

     回傳 ‘a / b’，例如 2/3 將等於 .66 而不是 0。這也被稱為「真」除法。

 -- 函式: operator.xor (a, b)
 -- 函式: operator.__xor__ (a, b)

     回傳 'a' 和 'b' 按位元異或 (exclusive or) 的結果。

適用於序列的操作（其中一些也適用於對映 (mapping)），包括：

 -- 函式: operator.concat (a, b)
 -- 函式: operator.__concat__ (a, b)

     對於序列 'a' 和 'b'，回傳 ‘a + b’。

 -- 函式: operator.contains (a, b)
 -- 函式: operator.__contains__ (a, b)

     回傳 ‘b in a’ 檢測的結果。請注意運算元是反序的。

 -- 函式: operator.countOf (a, b)

     回傳 'b' 在 'a' 中的出現次數。

 -- 函式: operator.delitem (a, b)
 -- 函式: operator.__delitem__ (a, b)

     移除 'a' 中索引為 'b' 的值。

 -- 函式: operator.getitem (a, b)
 -- 函式: operator.__getitem__ (a, b)

     回傳 'a' 中索引為 'b' 的值。

 -- 函式: operator.indexOf (a, b)

     回傳 'b' 在 'a' 中首次出現所在的索引。

 -- 函式: operator.setitem (a, b, c)
 -- 函式: operator.__setitem__ (a, b, c)

     將 'a' 中索引為 'b' 的值設為 'c'。

 -- 函式: operator.length_hint (obj, default=0)

     回傳物件 'obj' 的估計長度。首先嘗試回傳其實際長度，再使用 *note
     object.__length_hint__(): eaf. 得出估計值，最後才是回傳預設值。

     在 3.4 版被加入.

The following operation works with callables:

 -- 函式: operator.call (obj, /, *args, **kwargs)
 -- 函式: operator.__call__ (obj, /, *args, **kwargs)

     Return ‘obj(*args, **kwargs)’.

     在 3.11 版被加入.

*note operator: 8f. module 還定義了一些用於常規屬性和條目查詢的工具。這
些工具適合用來編寫快速欄位提取器以作為 *note map(): 808.、*note
sorted(): b75.、*note itertools.groupby(): 260b. 或其他需要函式引數的函
式之引數。

 -- 函式: operator.attrgetter (attr)

 -- 函式: operator.attrgetter (*attrs)

     回傳一個可從運算元中獲取 'attr' 的可呼叫 (callable) 物件。如果請求
     了一個以上的屬性，則回傳一個包含屬性的 tupple（元組）。屬性名稱還可
     包含點號。例如：

        * 在 ‘f = attrgetter('name')’ 之後，呼叫 ‘f(b)’ 將回傳 ‘b.name’。

        * 在 ‘f = attrgetter('name', 'date')’ 之後，呼叫 ‘f(b)’ 將回傳
          ‘(b.name, b.date)’。

        * 在 ‘f = attrgetter('name.first', 'name.last')’ 之後，呼叫
          ‘f(b)’ 將回傳 ‘(b.name.first, b.name.last)’。

     等價於：

          def attrgetter(*items):
              if any(not isinstance(item, str) for item in items):
                  raise TypeError('attribute name must be a string')
              if len(items) == 1:
                  attr = items[0]
                  def g(obj):
                      return resolve_attr(obj, attr)
              else:
                  def g(obj):
                      return tuple(resolve_attr(obj, attr) for attr in items)
              return g

          def resolve_attr(obj, attr):
              for name in attr.split("."):
                  obj = getattr(obj, name)
              return obj

 -- 函式: operator.itemgetter (item)

 -- 函式: operator.itemgetter (*items)

     回傳一個使用運算元的 *note __getitem__(): 266. 方法從運算元中獲取
     'item' 的可呼叫物件。如果指定了多個條目，則回傳一個查詢值的 tupple。
     例如：

        * 在 ‘f = itemgetter(2)’ 之後，呼叫 ‘f(r)’ 將回傳 ‘r[2]’。

        * 在 ‘g = itemgetter(2, 5, 3)’ 之後，呼叫 ‘g(r)’ 將回傳 ‘(r[2],
          r[5], r[3])’。

     等價於：

          def itemgetter(*items):
              if len(items) == 1:
                  item = items[0]
                  def g(obj):
                      return obj[item]
              else:
                  def g(obj):
                      return tuple(obj[item] for item in items)
              return g

     傳入的條目可以為運算元的 *note __getitem__(): 266. 所接受的任何型別
     。dictionary（字典）接受任意*note 可雜湊: 5b5.的值。list、tupple 和
     字串接受索引或切片：

          >>> itemgetter(1)('ABCDEFG')
          'B'
          >>> itemgetter(1, 3, 5)('ABCDEFG')
          ('B', 'D', 'F')
          >>> itemgetter(slice(2, None))('ABCDEFG')
          'CDEFG'
          >>> soldier = dict(rank='captain', name='dotterbart')
          >>> itemgetter('rank')(soldier)
          'captain'

     使用 *note itemgetter(): a05. 從 tuple 中提取特定欄位的例子：

          >>> inventory = [('apple', 3), ('banana', 2), ('pear', 5), ('orange', 1)]
          >>> getcount = itemgetter(1)
          >>> list(map(getcount, inventory))
          [3, 2, 5, 1]
          >>> sorted(inventory, key=getcount)
          [('orange', 1), ('banana', 2), ('apple', 3), ('pear', 5)]

 -- 函式: operator.methodcaller (name, /, *args, **kwargs)

     回傳一個在運算元上呼叫 'name' method 的可呼叫物件。如果給定額外的引
     數和/或關鍵字引數，它們也將被傳給該 method。例如：

        * 在 ‘f = methodcaller('name')’ 之後，呼叫 ‘f(b)’ 將回傳
          ‘b.name()’。

        * 在 ‘f = methodcaller('name', 'foo', bar=1)’ 之後，呼叫 ‘f(b)’
          將回傳 ‘b.name('foo', bar=1)’。

     等價於：

          def methodcaller(name, /, *args, **kwargs):
              def caller(obj):
                  return getattr(obj, name)(*args, **kwargs)
              return caller

* Menu:

* 運算子與函式間的對映::
* 原地 (in-place) 運算子: 原地 in-place 運算子.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/operator.py


File: python.info,  Node: 運算子與函式間的對映,  Next: 原地 in-place 運算子,  Up: operator --- 標準運算子替代函式

5.10.3.1 運算子與函式間的對映
.............................

以下表格表示了抽象運算是如何對應於 Python 語法中的運算子和 *note
operator: 8f. module中的函式。

運算                        語法                          函式
                                                          
------------------------------------------------------------------------------------------------------
                                                          
加法                        ‘a + b’                       ‘add(a, b)’
                                                          
                                                          
字串串接                    ‘seq1 + seq2’                 ‘concat(seq1, seq2)’
                                                          
                                                          
包含性檢測                  ‘obj in seq’                  ‘contains(seq, obj)’
                                                          
                                                          
除法                        ‘a / b’                       ‘truediv(a, b)’
                                                          
                                                          
除法                        ‘a // b’                      ‘floordiv(a, b)’
                                                          
                                                          
按位元與 (And)              ‘a & b’                       ‘and_(a, b)’
                                                          
                                                          
按位元互斥或 (Exclusive     ‘a ^ b’                       ‘xor(a, b)’
Or)                                                       

按位元取反 (Inversion)      ‘~ a’                         ‘invert(a)’
                                                          
                                                          
按位元或 (Or)               ‘a | b’                       ‘or_(a, b)’
                                                          
                                                          
取冪                        ‘a ** b’                      ‘pow(a, b)’
                                                          
                                                          
識別性                      ‘a is b’                      ‘is_(a, b)’
                                                          
                                                          
識別性                      ‘a is not b’                  ‘is_not(a, b)’
                                                          
                                                          
索引賦值                    ‘obj[k] = v’                  ‘setitem(obj, k, v)’
                                                          
                                                          
索引刪除                    ‘del obj[k]’                  ‘delitem(obj, k)’
                                                          
                                                          
索引取值                    ‘obj[k]’                      ‘getitem(obj, k)’
                                                          
                                                          
左移                        ‘a << b’                      ‘lshift(a, b)’
                                                          
                                                          
模除 (Modulo)               ‘a % b’                       ‘mod(a, b)’
                                                          
                                                          
乘法                        ‘a * b’                       ‘mul(a, b)’
                                                          
                                                          
矩陣乘法                    ‘a @ b’                       ‘matmul(a, b)’
                                                          
                                                          
反相（算術）                ‘- a’                         ‘neg(a)’
                                                          
                                                          
反相（邏輯）                ‘not a’                       ‘not_(a)’
                                                          
                                                          
正數                        ‘+ a’                         ‘pos(a)’
                                                          
                                                          
右移                        ‘a >> b’                      ‘rshift(a, b)’
                                                          
                                                          
切片賦值                    ‘seq[i:j] = values’           ‘setitem(seq, slice(i, j), values)’
                                                          
                                                          
切片刪除                    ‘del seq[i:j]’                ‘delitem(seq, slice(i, j))’
                                                          
                                                          
切片取值                    ‘seq[i:j]’                    ‘getitem(seq, slice(i, j))’
                                                          
                                                          
字串格式化                  ‘s % obj’                     ‘mod(s, obj)’
                                                          
                                                          
減法                        ‘a - b’                       ‘sub(a, b)’
                                                          
                                                          
真值檢測                    ‘obj’                         ‘truth(obj)’
                                                          
                                                          
比較大小                    ‘a < b’                       ‘lt(a, b)’
                                                          
                                                          
比較大小                    ‘a <= b’                      ‘le(a, b)’
                                                          
                                                          
相等性                      ‘a == b’                      ‘eq(a, b)’
                                                          
                                                          
不等性                      ‘a != b’                      ‘ne(a, b)’
                                                          
                                                          
比較大小                    ‘a >= b’                      ‘ge(a, b)’
                                                          
                                                          
比較大小                    ‘a > b’                       ‘gt(a, b)’
                                                          


File: python.info,  Node: 原地 in-place 運算子,  Prev: 運算子與函式間的對映,  Up: operator --- 標準運算子替代函式

5.10.3.2 原地 (in-place) 運算子
...............................

許多運算都有「原地」版本。以下列出的是提供對原地運算子（與一般語法相比）
更底層存取的函式，例如 *note statement: 265e. ‘x += y’ 相當於 ‘x =
operator.iadd(x, y)’。換一種方式來講就是 ‘z = operator.iadd(x, y)’ 等價
於複合陳述式 ‘z = x; z += y’。

在這些例子中，請注意當呼叫一個原地方法時，運算和賦值是分成兩個步驟來執行
的。下面列出的原地函式只執行第一步，即呼叫原地方法，第二步賦值則不加處理
。

對於不可變 (immutable) 的目標例如字串、數字和 tupple，更新的值會被計算，
但不會被再被賦值給輸入變數：

     >>> a = 'hello'
     >>> iadd(a, ' world')
     'hello world'
     >>> a
     'hello'

對於可變 (mutable) 的目標例如 list 和 dictionary，原地方法將執行更新，因
此不需要後續賦值操作：

     >>> s = ['h', 'e', 'l', 'l', 'o']
     >>> iadd(s, [' ', 'w', 'o', 'r', 'l', 'd'])
     ['h', 'e', 'l', 'l', 'o', ' ', 'w', 'o', 'r', 'l', 'd']
     >>> s
     ['h', 'e', 'l', 'l', 'o', ' ', 'w', 'o', 'r', 'l', 'd']

 -- 函式: operator.iadd (a, b)
 -- 函式: operator.__iadd__ (a, b)

     ‘a = iadd(a, b)’ 等價於 ‘a += b’。

 -- 函式: operator.iand (a, b)
 -- 函式: operator.__iand__ (a, b)

     ‘a = iand(a, b)’ 等價於 ‘a &= b’。

 -- 函式: operator.iconcat (a, b)
 -- 函式: operator.__iconcat__ (a, b)

     ‘a = iconcat(a, b)’ 等價於 ‘a += b’，其中 'a' 和 'b' 為序列。

 -- 函式: operator.ifloordiv (a, b)
 -- 函式: operator.__ifloordiv__ (a, b)

     ‘a = ifloordiv(a, b)’ 等價於 ‘a //= b’。

 -- 函式: operator.ilshift (a, b)
 -- 函式: operator.__ilshift__ (a, b)

     ‘a = ilshift(a, b)’ 等價於 ‘a <<= b’。

 -- 函式: operator.imod (a, b)
 -- 函式: operator.__imod__ (a, b)

     ‘a = imod(a, b)’ 等價於 ‘a %= b’。

 -- 函式: operator.imul (a, b)
 -- 函式: operator.__imul__ (a, b)

     ‘a = imul(a, b)’ 等價於 ‘a *= b’。

 -- 函式: operator.imatmul (a, b)
 -- 函式: operator.__imatmul__ (a, b)

     ‘a = imatmul(a, b)’ 等價於 ‘a @= b’。

     在 3.5 版被加入.

 -- 函式: operator.ior (a, b)
 -- 函式: operator.__ior__ (a, b)

     ‘a = ior(a, b)’ 等價於 ‘a |= b’。

 -- 函式: operator.ipow (a, b)
 -- 函式: operator.__ipow__ (a, b)

     ‘a = ipow(a, b)’ 等價於 ‘a **= b’。

 -- 函式: operator.irshift (a, b)
 -- 函式: operator.__irshift__ (a, b)

     ‘a = irshift(a, b)’ 等價於 ‘a >>= b’。

 -- 函式: operator.isub (a, b)
 -- 函式: operator.__isub__ (a, b)

     ‘a = isub(a, b)’ 等價於 ‘a -= b’。

 -- 函式: operator.itruediv (a, b)
 -- 函式: operator.__itruediv__ (a, b)

     ‘a = itruediv(a, b)’ 等價於 ‘a /= b’。

 -- 函式: operator.ixor (a, b)
 -- 函式: operator.__ixor__ (a, b)

     ‘a = ixor(a, b)’ 等價於 ‘a ^= b’。


File: python.info,  Node: 檔案與目錄存取,  Next: 資料持久性 Data Persistence,  Prev: 函式編程模組,  Up: Python 標準函式庫 Standard Library

5.11 檔案與目錄存取
===================

本章中描述的 module（模組）用於處理硬碟檔案和目錄。例如，有一些 module 用
於讀取檔案的屬性、以可攜 (portable) 方式操作路徑以及建立暫存檔。本章中的
完整 module 清單是：

* Menu:

* pathlib: pathlib --- 物件導向檔案系統路徑. 物件導向檔案系統路徑
* os.path: os path --- 常見的路徑名操作. 常見的路徑名操作
* fileinput: fileinput --- 逐列疊代多個輸入串流. 逐列疊代多個輸入串流
* stat: stat --- 直譯 stat 的結果. 直譯 stat() 的結果
* filecmp: filecmp --- 檔案與目錄比較. 檔案與目錄比較
* tempfile: tempfile --- 生成臨時檔案和目錄. 生成臨時檔案和目錄
* glob: glob --- Unix 風格的路徑名稱模式擴展. Unix 風格的路徑名稱模式擴展
* fnmatch: fnmatch --- Unix 檔案名稱模式比對. Unix 檔案名稱模式比對
* linecache: linecache --- 隨機存取文字列. 隨機存取文字列
* shutil — 高階檔案操作::


File: python.info,  Node: pathlib --- 物件導向檔案系統路徑,  Next: os path --- 常見的路徑名操作,  Up: 檔案與目錄存取

5.11.1 ‘pathlib’ -- 物件導向檔案系統路徑
----------------------------------------

在 3.4 版被加入.

'Source code:' Lib/pathlib/(1)

__________________________________________________________________

此模組提供代表檔案系統路徑的類別，能適用不同作業系統的語意。路徑類別分成
兩種，一種是*note 純路徑 (pure paths): 267f.，提供沒有 I/O 的單純計算操
作，另一種是*note 實體路徑 (concrete paths): 2680.，繼承自純路徑但也提供
IO 操作。

[image src="python-figures/pathlib-inheritance.png" alt="Inheritance diagram showing the classes available in pathlib. The most basic class is PurePath, which has three direct subclasses: PurePosixPath, PureWindowsPath, and Path. Further to these four classes, there are two classes that use multiple inheritance: PosixPath subclasses PurePosixPath and Path, and WindowsPath subclasses PureWindowsPath and Path."]


如果你之前從未使用過此模組或不確定哪個類別適合你的任務，那你需要的最有可
能是 *note Path: 20e.。它針對程式執行所在的平台實例化一個*note 實體路徑:
2680.。

純路徑在某些特殊情境下是有用的，例如：

  1. 如果你想在 Unix 機器上處理 Windows 路徑（或反過來），你無法在 Unix
     上實例化 *note WindowsPath: 2681.，但你可以實例化 *note
     PureWindowsPath: 1601.。

  2. 你想確保你的程式在操作路徑的時候不會真的存取到 OS。在這個情況下，實
     例化其中一種純路徑類別可能是有用的，因為它們不會有任何存取 OS 的操
     作。

也參考
......

PEP 428(2)：pathlib 模組 - 物件導向檔案系統路徑。

也參考
......

針對字串上的底層路徑操作，你也可以使用 *note os.path: 92. 模組。

* Menu:

* 基本用法::
* Exceptions: Exceptions<2>.
* 純路徑::
* 實體路徑::
* Pattern language::
* Comparison to the glob module::
* Comparison to the os and os.path modules: Comparison to the os and os path modules.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/pathlib/

   (2) https://peps.python.org/pep-0428/


File: python.info,  Node: 基本用法,  Next: Exceptions<2>,  Up: pathlib --- 物件導向檔案系統路徑

5.11.1.1 基本用法
.................

匯入主要類別：

     >>> from pathlib import Path

列出子目錄：

     >>> p = Path('.')
     >>> [x for x in p.iterdir() if x.is_dir()]
     [PosixPath('.hg'), PosixPath('docs'), PosixPath('dist'),
      PosixPath('__pycache__'), PosixPath('build')]

在當前目錄樹下列出 Python 原始碼檔案：

     >>> list(p.glob('**/*.py'))
     [PosixPath('test_pathlib.py'), PosixPath('setup.py'),
      PosixPath('pathlib.py'), PosixPath('docs/conf.py'),
      PosixPath('build/lib/pathlib.py')]

瀏覽目錄樹內部：

     >>> p = Path('/etc')
     >>> q = p / 'init.d' / 'reboot'
     >>> q
     PosixPath('/etc/init.d/reboot')
     >>> q.resolve()
     PosixPath('/etc/rc.d/init.d/halt')

查詢路徑屬性：

     >>> q.exists()
     True
     >>> q.is_dir()
     False

開啟檔案：

     >>> with q.open() as f: f.readline()
     ...
     '#!/bin/bash\n'


File: python.info,  Node: Exceptions<2>,  Next: 純路徑,  Prev: 基本用法,  Up: pathlib --- 物件導向檔案系統路徑

5.11.1.2 Exceptions
...................

 -- 例外: pathlib.UnsupportedOperation

     An exception inheriting *note NotImplementedError: 20d. that is
     raised when an unsupported operation is called on a path object.

     在 3.13 版被加入.


File: python.info,  Node: 純路徑,  Next: 實體路徑,  Prev: Exceptions<2>,  Up: pathlib --- 物件導向檔案系統路徑

5.11.1.3 純路徑
...............

純路徑物件提供處理路徑的操作，實際上不會存取檔案系統。有三種方式可以存取
這些類別，我們也稱之為'類型 (flavours)'：

 -- 類別: pathlib.PurePath (*pathsegments)

     一個通用的類別，表示系統的路徑類型（實例化時會建立一個 *note
     PurePosixPath: 2685. 或 *note PureWindowsPath: 1601.)：

          >>> PurePath('setup.py')      # Running on a Unix machine
          PurePosixPath('setup.py')

     'pathsegments' 中的每個元素可以是以下的其中一種：一個表示路徑片段的
     字串，或一個物件，它實作了 *note os.PathLike: bf8. 介面且其中的
     *note __fspath__(): bf9. 方法會回傳字串，就像是另一個路徑物件：

          >>> PurePath('foo', 'some/path', 'bar')
          PurePosixPath('foo/some/path/bar')
          >>> PurePath(Path('foo'), Path('bar'))
          PurePosixPath('foo/bar')

     當沒有給 'pathsegments' 的時候，會假設是目前的目錄：

          >>> PurePath()
          PurePosixPath('.')

     如果一個片段是絕對路徑，則所有之前的片段會被忽略（類似 *note
     os.path.join(): 1527.)：

          >>> PurePath('/etc', '/usr', 'lib64')
          PurePosixPath('/usr/lib64')
          >>> PureWindowsPath('c:/Windows', 'd:bar')
          PureWindowsPath('d:bar')

     在 Windows 系統上，當遇到具有根目錄的相對路徑片段（例如 ‘r'\foo'’）
     時，磁碟機 (drive) 部分不會被重置：

          >>> PureWindowsPath('c:/Windows', '/Program Files')
          PureWindowsPath('c:/Program Files')

     不必要的斜線和單點會被合併，但雙點 (‘'..'’) 和前置的雙斜線 (‘'//'’)
     不會被合併，因為這樣會因為各種原因改變路徑的意義（例如符號連結
     (symbolic links)、UNC 路徑）：

          >>> PurePath('foo//bar')
          PurePosixPath('foo/bar')
          >>> PurePath('//foo/bar')
          PurePosixPath('//foo/bar')
          >>> PurePath('foo/./bar')
          PurePosixPath('foo/bar')
          >>> PurePath('foo/../bar')
          PurePosixPath('foo/../bar')

     （一個使得 ‘PurePosixPath('foo/../bar')’ 等同於
     ‘PurePosixPath('bar')’ 的單純方法，但如果 ‘foo’ 是指到另一個目錄的
     符號連結，就會是錯誤的。）

     純路徑物件實作了 *note os.PathLike: bf8. 介面，使得它們可以在任何接
     受該介面的地方使用。

     在 3.6 版的變更: 新增了對於 *note os.PathLike: bf8. 介面的支援。

 -- 類別: pathlib.PurePosixPath (*pathsegments)

     *note PurePath: 44e. 的一個子類別，該路徑類型表示非 Windows 檔案系
     統的路徑：

          >>> PurePosixPath('/etc/hosts')
          PurePosixPath('/etc/hosts')

     'pathsegments' 的指定方式與 *note PurePath: 44e. 類似。

 -- 類別: pathlib.PureWindowsPath (*pathsegments)

     *note PurePath: 44e. 的一個子類別，該路徑類型表示 Windows 檔案系統
     的路徑，包括 UNC paths(1)：

          >>> PureWindowsPath('c:/', 'Users', 'Ximénez')
          PureWindowsPath('c:/Users/Ximénez')
          >>> PureWindowsPath('//server/share/file')
          PureWindowsPath('//server/share/file')

     'pathsegments' 的指定方式與 *note PurePath: 44e. 類似。

不論你使用的是什麼系統，你都可以實例化這些類別，因為它們不提供任何涉及系
統呼叫的操作。

* Menu:

* 通用屬性::
* 運算子::
* 對個別組成的存取::
* 方法與屬性::

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Path_(computing)#UNC


File: python.info,  Node: 通用屬性,  Next: 運算子,  Up: 純路徑

5.11.1.4 通用屬性
.................

路徑物件是不可變 (immutable) 且可雜湊 (*note hashable: 5b5.) 的。相同類
型的路徑物件可以被比較和排序。這些屬性遵守該類型的大小寫語意規則：

     >>> PurePosixPath('foo') == PurePosixPath('FOO')
     False
     >>> PureWindowsPath('foo') == PureWindowsPath('FOO')
     True
     >>> PureWindowsPath('FOO') in { PureWindowsPath('foo') }
     True
     >>> PureWindowsPath('C:') < PureWindowsPath('d:')
     True

不同類型的路徑物件在比較時視為不相等且無法被排序：

     >>> PureWindowsPath('foo') == PurePosixPath('foo')
     False
     >>> PureWindowsPath('foo') < PurePosixPath('foo')
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: '<' not supported between instances of 'PureWindowsPath' and 'PurePosixPath'


File: python.info,  Node: 運算子,  Next: 對個別組成的存取,  Prev: 通用屬性,  Up: 純路徑

5.11.1.5 運算子
...............

斜線運算子 (slash operator) 用於建立子路徑，就像是 *note os.path.join():
1527. 函式一樣。如果引數是絕對路徑，則忽略前一個路徑。在 Windows 系統上
，當引數是具有根目錄的相對路徑（例如，‘r'\foo'’），磁碟機部分不會被重置
：

     >>> p = PurePath('/etc')
     >>> p
     PurePosixPath('/etc')
     >>> p / 'init.d' / 'apache2'
     PurePosixPath('/etc/init.d/apache2')
     >>> q = PurePath('bin')
     >>> '/usr' / q
     PurePosixPath('/usr/bin')
     >>> p / '/an_absolute_path'
     PurePosixPath('/an_absolute_path')
     >>> PureWindowsPath('c:/Windows', '/Program Files')
     PureWindowsPath('c:/Program Files')

路徑物件可以被用在任何可以接受實作 *note os.PathLike: bf8. 的物件的地方
：

     >>> import os
     >>> p = PurePath('/etc')
     >>> os.fspath(p)
     '/etc'

路徑的字串表示是原始的檔案系統路徑本身（以原生的形式，例如在 Windows 下
是反斜線），你可以將其傳入任何將檔案路徑當作字串傳入的函式：

     >>> p = PurePath('/etc')
     >>> str(p)
     '/etc'
     >>> p = PureWindowsPath('c:/Program Files')
     >>> str(p)
     'c:\\Program Files'

類似地，對路徑呼叫 *note bytes: 1a5. 會得到原始檔案系統路徑的 bytes 物件
，就像使用 *note os.fsencode(): bfc. 編碼過的一樣：

     >>> bytes(p)
     b'/etc'

     備註: 只建議在 Unix 下呼叫 *note bytes: 1a5.。在 Windows 裡，
     unicode 形式是檔案系統路徑的權威表示方式。


File: python.info,  Node: 對個別組成的存取,  Next: 方法與屬性,  Prev: 運算子,  Up: 純路徑

5.11.1.6 對個別組成的存取
.........................

可以使用下列屬性來存取路徑的個別「組成」(parts, components)：

 -- 屬性: PurePath.parts

     一個可存取路徑的各組成的元組：

          >>> p = PurePath('/usr/bin/python3')
          >>> p.parts
          ('/', 'usr', 'bin', 'python3')

          >>> p = PureWindowsPath('c:/Program Files/PSF')
          >>> p.parts
          ('c:\\', 'Program Files', 'PSF')

     （特別注意磁碟機跟本地根目錄是如何被重新組合成一個單一組成）


File: python.info,  Node: 方法與屬性,  Prev: 對個別組成的存取,  Up: 純路徑

5.11.1.7 方法與屬性
...................

純路徑提供以下方法與屬性：

 -- 屬性: PurePath.parser

     The implementation of the *note os.path: 92. module used for
     low-level path parsing and joining: either ‘posixpath’ or ‘ntpath’.

     在 3.13 版被加入.

 -- 屬性: PurePath.drive

     若存在則為一個表示磁碟機字母 (drive letter) 或磁碟機名稱 (drive
     name) 的字串：

          >>> PureWindowsPath('c:/Program Files/').drive
          'c:'
          >>> PureWindowsPath('/Program Files/').drive
          ''
          >>> PurePosixPath('/etc').drive
          ''

     UNC shares 也被視為磁碟機：

          >>> PureWindowsPath('//host/share/foo.txt').drive
          '\\\\host\\share'

 -- 屬性: PurePath.root

     若存在則為一個表示（本地或全域）根目錄的字串：

          >>> PureWindowsPath('c:/Program Files/').root
          '\\'
          >>> PureWindowsPath('c:Program Files/').root
          ''
          >>> PurePosixPath('/etc').root
          '/'

     UNC shares 都會有一個根目錄：

          >>> PureWindowsPath('//host/share').root
          '\\'

     如果路徑以超過兩個連續的斜線開頭，*note PurePosixPath: 2685. 會合併
     它們：

          >>> PurePosixPath('//etc').root
          '//'
          >>> PurePosixPath('///etc').root
          '/'
          >>> PurePosixPath('////etc').root
          '/'

          備註: 此行為符合 'The Open Group Base Specifications Issue 6'，
          章節 4.11 路徑名稱解析(1)：

          '「以兩個連續斜線開頭的路徑名稱可以根據實作定義的方式來解讀，
          儘管如此，開頭超過兩個斜線應該視為單一斜線。」'

 -- 屬性: PurePath.anchor

     磁碟機與根目錄的結合：

          >>> PureWindowsPath('c:/Program Files/').anchor
          'c:\\'
          >>> PureWindowsPath('c:Program Files/').anchor
          'c:'
          >>> PurePosixPath('/etc').anchor
          '/'
          >>> PureWindowsPath('//host/share').anchor
          '\\\\host\\share\\'

 -- 屬性: PurePath.parents

     一個不可變的序列，為路徑邏輯上的祖先 (logical ancestors) 提供存取：

          >>> p = PureWindowsPath('c:/foo/bar/setup.py')
          >>> p.parents[0]
          PureWindowsPath('c:/foo/bar')
          >>> p.parents[1]
          PureWindowsPath('c:/foo')
          >>> p.parents[2]
          PureWindowsPath('c:/')

     在 3.10 版的變更: 父序列現在支援 *note slices: 2059. 及負的索引值。

 -- 屬性: PurePath.parent

     邏輯上的父路徑：

          >>> p = PurePosixPath('/a/b/c/d')
          >>> p.parent
          PurePosixPath('/a/b/c')

     你不能越過一個 anchor 或空路徑：

          >>> p = PurePosixPath('/')
          >>> p.parent
          PurePosixPath('/')
          >>> p = PurePosixPath('.')
          >>> p.parent
          PurePosixPath('.')

          備註: 這是一個純粹字句上的 (lexical) 運算，因此會有以下行為：

               >>> p = PurePosixPath('foo/..')
               >>> p.parent
               PurePosixPath('foo')

          如果你想要沿任意的檔案系統路徑往上走，建議要先呼叫 *note
          Path.resolve(): 15f7. 來解析符號連結 (symlink) 及去除其中的
          ‘”..”’。

 -- 屬性: PurePath.name

     最後的路徑組成 (final path component) 的字串表示，不包含任何磁碟機
     或根目錄：

          >>> PurePosixPath('my/library/setup.py').name
          'setup.py'

     UNC 磁碟機名稱並沒有算在內：

          >>> PureWindowsPath('//some/share/setup.py').name
          'setup.py'
          >>> PureWindowsPath('//some/share').name
          ''

 -- 屬性: PurePath.suffix

     The last dot-separated portion of the final component, if any:

          >>> PurePosixPath('my/library/setup.py').suffix
          '.py'
          >>> PurePosixPath('my/library.tar.gz').suffix
          '.gz'
          >>> PurePosixPath('my/library').suffix
          ''

     This is commonly called the file extension.

 -- 屬性: PurePath.suffixes

     A list of the path's suffixes, often called file extensions:

          >>> PurePosixPath('my/library.tar.gar').suffixes
          ['.tar', '.gar']
          >>> PurePosixPath('my/library.tar.gz').suffixes
          ['.tar', '.gz']
          >>> PurePosixPath('my/library').suffixes
          []

 -- 屬性: PurePath.stem

     最後的路徑組成，不包括後綴 (suffix)：

          >>> PurePosixPath('my/library.tar.gz').stem
          'library.tar'
          >>> PurePosixPath('my/library.tar').stem
          'library'
          >>> PurePosixPath('my/library').stem
          'library'

 -- 方法: PurePath.as_posix ()

     回傳一個使用正斜線 (‘/’) 的路徑的字串表示：

          >>> p = PureWindowsPath('c:\\windows')
          >>> str(p)
          'c:\\windows'
          >>> p.as_posix()
          'c:/windows'

 -- 方法: PurePath.is_absolute ()

     回傳一個路徑是否是絕對路徑。一個路徑被視為絕對路徑的條件是它同時有
     根目錄及（如果該系統類型允許的話）磁碟機：

          >>> PurePosixPath('/a/b').is_absolute()
          True
          >>> PurePosixPath('a/b').is_absolute()
          False

          >>> PureWindowsPath('c:/a/b').is_absolute()
          True
          >>> PureWindowsPath('/a/b').is_absolute()
          False
          >>> PureWindowsPath('c:').is_absolute()
          False
          >>> PureWindowsPath('//some/share').is_absolute()
          True

 -- 方法: PurePath.is_relative_to (other)

     回傳此路徑是否為 'other' 路徑的相對路徑。

          >>> p = PurePath('/etc/passwd')
          >>> p.is_relative_to('/etc')
          True
          >>> p.is_relative_to('/usr')
          False

     該方法是基於字串的；它既不存取檔案系統，也不特別處理 "‘..’" 片段。
     以下程式碼是等效的：

          >>> u = PurePath('/usr')
          >>> u == p or u in p.parents
          False

     在 3.9 版被加入.

     Deprecated since version 3.12, will be removed in version 3.14: 額
     外引數的傳入已棄用；如果有的話，它們會與 'other' 連接在一起。

 -- 方法: PurePath.is_reserved ()

     對 *note PureWindowsPath: 1601. 來說，當路徑在 Windows 下被視為保留
     的話會回傳 ‘True’，否則回傳 ‘False’。對 *note PurePosixPath: 2685.
     來說，總是回傳 ‘False’。

     在 3.13 版的變更: Windows path names that contain a colon, or end
     with a dot or a space, are considered reserved.  UNC paths may be
     reserved.

     Deprecated since version 3.13, will be removed in version 3.15:
     This method is deprecated; use *note os.path.isreserved(): 208. to
     detect reserved paths on Windows.

 -- 方法: PurePath.joinpath (*pathsegments)

     呼叫此方法會依序結合每個所給定的 'pathsegments' 到路徑上：

          >>> PurePosixPath('/etc').joinpath('passwd')
          PurePosixPath('/etc/passwd')
          >>> PurePosixPath('/etc').joinpath(PurePosixPath('passwd'))
          PurePosixPath('/etc/passwd')
          >>> PurePosixPath('/etc').joinpath('init.d', 'apache2')
          PurePosixPath('/etc/init.d/apache2')
          >>> PureWindowsPath('c:').joinpath('/Program Files')
          PureWindowsPath('c:/Program Files')

 -- 方法: PurePath.full_match (pattern, *, case_sensitive=None)

     Match this path against the provided glob-style pattern.  Return
     ‘True’ if matching is successful, ‘False’ otherwise.  For example:

          >>> PurePath('a/b.py').full_match('a/*.py')
          True
          >>> PurePath('a/b.py').full_match('*.py')
          False
          >>> PurePath('/a/b/c.py').full_match('/a/**')
          True
          >>> PurePath('/a/b/c.py').full_match('**/*.py')
          True

     也參考
     ......

     *note Pattern language: 2694. documentation.

     像其它方法一樣，是否區分大小寫會遵循平台的預設行為：

          >>> PurePosixPath('b.py').full_match('*.PY')
          False
          >>> PureWindowsPath('b.py').full_match('*.PY')
          True

     將 'case_sensitive' 設定成 ‘True’ 或 ‘False’ 會覆蓋這個行為。

     在 3.13 版被加入.

 -- 方法: PurePath.match (pattern, *, case_sensitive=None)

     Match this path against the provided non-recursive glob-style
     pattern.  Return ‘True’ if matching is successful, ‘False’
     otherwise.

     This method is similar to *note full_match(): 210, but empty
     patterns aren't allowed (*note ValueError: 1e7. is raised), the
     recursive wildcard "‘**’" isn't supported (it acts like
     non-recursive "‘*’"), and if a relative pattern is provided, then
     matching is done from the right:

          >>> PurePath('a/b.py').match('*.py')
          True
          >>> PurePath('/a/b/c.py').match('b/*.py')
          True
          >>> PurePath('/a/b/c.py').match('a/*.py')
          False

     在 3.12 版的變更: The 'pattern' parameter accepts a *note path-like
     object: ac2.

     在 3.12 版的變更: 新增 'case_sensitive' 參數。

 -- 方法: PurePath.relative_to (other, walk_up=False)

     計算這個路徑相對於 'other' 所表示路徑的版本。如果做不到會引發 *note
     ValueError: 1e7.：

          >>> p = PurePosixPath('/etc/passwd')
          >>> p.relative_to('/')
          PurePosixPath('etc/passwd')
          >>> p.relative_to('/etc')
          PurePosixPath('passwd')
          >>> p.relative_to('/usr')
          Traceback (most recent call last):
            File "<stdin>", line 1, in <module>
            File "pathlib.py", line 941, in relative_to
              raise ValueError(error_message.format(str(self), str(formatted)))
          ValueError: '/etc/passwd' is not in the subpath of '/usr' OR one path is relative and the other is absolute.

     當 'walk_up' 是 False（預設值），路徑必須以 'other' 為開始。當此引
     數是 True，可能會加入 ‘..’ 以組成相對路徑。在其他情況下，例如路徑參
     考到不同的磁碟機，則會引發 *note ValueError: 1e7.：

          >>> p.relative_to('/usr', walk_up=True)
          PurePosixPath('../etc/passwd')
          >>> p.relative_to('foo', walk_up=True)
          Traceback (most recent call last):
            File "<stdin>", line 1, in <module>
            File "pathlib.py", line 941, in relative_to
              raise ValueError(error_message.format(str(self), str(formatted)))
          ValueError: '/etc/passwd' is not on the same drive as 'foo' OR one path is relative and the other is absolute.

          警告: 這個函式是 *note PurePath: 44e. 的一部分且可以在字串上運
          作。它不會檢查或存取實際的檔案架構。這會影響到 'walk_up' 選項
          ，因為它假設路徑中沒有符號連結；如果需要解析符號連結的話可以先
          呼叫 *note resolve(): 15f7.。

     在 3.12 版的變更: 加入 'walk_up' 參數（舊的行為和 ‘walk_up=False’ 相
     同）。

     Deprecated since version 3.12, will be removed in version 3.14: 額
     外位置引數的傳入已棄用；如果有的話，它們會與 'other' 連接在一起。

 -- 方法: PurePath.with_name (name)

     回傳一個修改 *note name: 268e. 後的新路徑。如果原始路徑沒有名稱則引
     發 ValueError：

          >>> p = PureWindowsPath('c:/Downloads/pathlib.tar.gz')
          >>> p.with_name('setup.py')
          PureWindowsPath('c:/Downloads/setup.py')
          >>> p = PureWindowsPath('c:/')
          >>> p.with_name('setup.py')
          Traceback (most recent call last):
            File "<stdin>", line 1, in <module>
            File "/home/antoine/cpython/default/Lib/pathlib.py", line 751, in with_name
              raise ValueError("%r has an empty name" % (self,))
          ValueError: PureWindowsPath('c:/') has an empty name

 -- 方法: PurePath.with_stem (stem)

     回傳一個修改 *note stem: 2691. 後的新路徑。如果原始路徑沒有名稱則引
     發 ValueError：

          >>> p = PureWindowsPath('c:/Downloads/draft.txt')
          >>> p.with_stem('final')
          PureWindowsPath('c:/Downloads/final.txt')
          >>> p = PureWindowsPath('c:/Downloads/pathlib.tar.gz')
          >>> p.with_stem('lib')
          PureWindowsPath('c:/Downloads/lib.gz')
          >>> p = PureWindowsPath('c:/')
          >>> p.with_stem('')
          Traceback (most recent call last):
            File "<stdin>", line 1, in <module>
            File "/home/antoine/cpython/default/Lib/pathlib.py", line 861, in with_stem
              return self.with_name(stem + self.suffix)
            File "/home/antoine/cpython/default/Lib/pathlib.py", line 851, in with_name
              raise ValueError("%r has an empty name" % (self,))
          ValueError: PureWindowsPath('c:/') has an empty name

     在 3.9 版被加入.

 -- 方法: PurePath.with_suffix (suffix)

     回傳一個修改 *note suffix: 268f. 後的新路徑。如果原始路徑沒有後綴，
     新的 'suffix' 會附加在後面。如果 'suffix' 是一個空字串，原來的後綴
     會被移除：

          >>> p = PureWindowsPath('c:/Downloads/pathlib.tar.gz')
          >>> p.with_suffix('.bz2')
          PureWindowsPath('c:/Downloads/pathlib.tar.bz2')
          >>> p = PureWindowsPath('README')
          >>> p.with_suffix('.txt')
          PureWindowsPath('README.txt')
          >>> p = PureWindowsPath('README.txt')
          >>> p.with_suffix('')
          PureWindowsPath('README')

 -- 方法: PurePath.with_segments (*pathsegments)

     透過結合給定的 'pathsegments' 建立一個相同類型的新路徑物件，當一個
     衍生路徑被建立的時候會呼叫這個方法，例如從 *note parent: 162b. 和
     *note relative_to(): 2ac. 建立衍生路徑。子類別可以覆寫此方法來傳遞
     資訊給衍生路徑，例如：

          from pathlib import PurePosixPath

          class MyPath(PurePosixPath):
              def __init__(self, *pathsegments, session_id):
                  super().__init__(*pathsegments)
                  self.session_id = session_id

              def with_segments(self, *pathsegments):
                  return type(self)(*pathsegments, session_id=self.session_id)

          etc = MyPath('/etc', session_id=42)
          hosts = etc / 'hosts'
          print(hosts.session_id)  # 42

     在 3.12 版被加入.

   ---------- Footnotes ----------

   (1) 
https://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap04.html#tag_04_11


File: python.info,  Node: 實體路徑,  Next: Pattern language,  Prev: 純路徑,  Up: pathlib --- 物件導向檔案系統路徑

5.11.1.8 實體路徑
.................

實體路徑是純路徑類別的子類別。除了後者本來就有提供的操作，它們也提供方法
可以對路徑物件做系統呼叫。有三種方式可以實例化實體路徑：

 -- 類別: pathlib.Path (*pathsegments)

     *note PurePath: 44e. 的子類別，此類別表示系統的路徑類型的實體路徑（
     實例化時會建立一個 *note PosixPath: 2696. 或 *note WindowsPath:
     2681.）：

          >>> Path('setup.py')
          PosixPath('setup.py')

     'pathsegments' 的指定方式與 *note PurePath: 44e. 類似。

 -- 類別: pathlib.PosixPath (*pathsegments)

     *note Path: 20e. 和 *note PurePosixPath: 2685. 的子類別，此類別表示
     實體非 Windows 檔案系統路徑：

          >>> PosixPath('/etc/hosts')
          PosixPath('/etc/hosts')

     'pathsegments' 的指定方式與 *note PurePath: 44e. 類似。

     在 3.13 版的變更: Raises *note UnsupportedOperation: 20c. on
     Windows.  In previous versions, *note NotImplementedError: 20d. was
     raised instead.

 -- 類別: pathlib.WindowsPath (*pathsegments)

     *note Path: 20e. 和 *note PureWindowsPath: 1601. 的子類別，此類別表
     示實體 Windows 檔案系統路徑：

          >>> WindowsPath('c:/', 'Users', 'Ximénez')
          WindowsPath('c:/Users/Ximénez')

     'pathsegments' 的指定方式與 *note PurePath: 44e. 類似。

     在 3.13 版的變更: Raises *note UnsupportedOperation: 20c. on
     non-Windows platforms.  In previous versions, *note
     NotImplementedError: 20d. was raised instead.

你只能實例化對應你的系統的類別類型（允許在不相容的路徑類型上做系統呼叫可
能在你的應用程式導致漏洞或故障）：

     >>> import os
     >>> os.name
     'posix'
     >>> Path('setup.py')
     PosixPath('setup.py')
     >>> PosixPath('setup.py')
     PosixPath('setup.py')
     >>> WindowsPath('setup.py')
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
       File "pathlib.py", line 798, in __new__
         % (cls.__name__,))
     UnsupportedOperation: cannot instantiate 'WindowsPath' on your system

有些實體路徑方法會在系統呼叫失敗（例如因為路徑不存在）時引發 *note
OSError: 350.

* Menu:

* Parsing and generating URIs::
* Expanding and resolving paths::
* Querying file type and status::
* Reading and writing files::
* 讀取目錄::
* 建立檔案與目錄::
* Renaming and deleting::
* Permissions and ownership::


File: python.info,  Node: Parsing and generating URIs,  Next: Expanding and resolving paths,  Up: 實體路徑

5.11.1.9 Parsing and generating URIs
....................................

Concrete path objects can be created from, and represented as, 'file'
URIs conforming to RFC 8089(1).

     備註: File URIs are not portable across machines with different
     *note filesystem encodings: 2698.

 -- 方法: classmethod Path.from_uri (uri)

     Return a new path object from parsing a 'file' URI. For example:

          >>> p = Path.from_uri('file:///etc/hosts')
          PosixPath('/etc/hosts')

     On Windows, DOS device and UNC paths may be parsed from URIs:

          >>> p = Path.from_uri('file:///c:/windows')
          WindowsPath('c:/windows')
          >>> p = Path.from_uri('file://server/share')
          WindowsPath('//server/share')

     Several variant forms are supported:

          >>> p = Path.from_uri('file:////server/share')
          WindowsPath('//server/share')
          >>> p = Path.from_uri('file://///server/share')
          WindowsPath('//server/share')
          >>> p = Path.from_uri('file:c:/windows')
          WindowsPath('c:/windows')
          >>> p = Path.from_uri('file:/c|/windows')
          WindowsPath('c:/windows')

     *note ValueError: 1e7. is raised if the URI does not start with
     ‘file:’, or the parsed path isn't absolute.

     在 3.13 版被加入.

 -- 方法: Path.as_uri ()

     Represent the path as a 'file' URI. *note ValueError: 1e7. is
     raised if the path isn't absolute.

          >>> p = PosixPath('/etc/passwd')
          >>> p.as_uri()
          'file:///etc/passwd'
          >>> p = WindowsPath('c:/Windows')
          >>> p.as_uri()
          'file:///c:/Windows'

     For historical reasons, this method is also available from *note
     PurePath: 44e. objects.  However, its use of *note os.fsencode():
     bfc. makes it strictly impure.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc8089.html


File: python.info,  Node: Expanding and resolving paths,  Next: Querying file type and status,  Prev: Parsing and generating URIs,  Up: 實體路徑

5.11.1.10 Expanding and resolving paths
.......................................

 -- 方法: classmethod Path.home ()

     回傳一個代表使用者家目錄的新的路徑物件（像以 ‘~’ 構成的 *note
     os.path.expanduser(): 9b8. 的回傳一樣）。如果無法解析家目錄，會引發
     *note RuntimeError: 179.。

          >>> Path.home()
          PosixPath('/home/antoine')

     在 3.5 版被加入.

 -- 方法: Path.expanduser ()

     回傳一個展開 ‘~’ 和 ‘~user’ 構成的新路徑，像 *note
     os.path.expanduser(): 9b8. 回傳的一樣。如果無法解析家目錄，會引發
     *note RuntimeError: 179.。

          >>> p = PosixPath('~/films/Monty Python')
          >>> p.expanduser()
          PosixPath('/home/eric/films/Monty Python')

     在 3.5 版被加入.

 -- 方法: classmethod Path.cwd ()

     回傳一個代表目前目錄的新的路徑物件（像 *note os.getcwd(): 1907. 回
     傳的一樣）：

          >>> Path.cwd()
          PosixPath('/home/antoine/pathlib')

 -- 方法: Path.absolute ()

     將路徑轉換為絕對路徑，不進行標準化或解析符號連結。回傳一個新的路徑
     物件：

          >>> p = Path('tests')
          >>> p
          PosixPath('tests')
          >>> p.absolute()
          PosixPath('/home/antoine/pathlib/tests')

 -- 方法: Path.resolve (strict=False)

     將路徑轉換為絕對路徑，解析所有符號連結。回傳一個新的路徑物件：

          >>> p = Path()
          >>> p
          PosixPath('.')
          >>> p.resolve()
          PosixPath('/home/antoine/pathlib')

     同時也會消除 "‘..’" 的路徑組成（只有此方法這樣做）：

          >>> p = Path('docs/../setup.py')
          >>> p.resolve()
          PosixPath('/home/antoine/pathlib/setup.py')

     If a path doesn't exist or a symlink loop is encountered, and
     'strict' is ‘True’, *note OSError: 350. is raised.  If 'strict' is
     ‘False’, the path is resolved as far as possible and any remainder
     is appended without checking whether it exists.

     在 3.6 版的變更: 新增 'strict' 參數（在 3.6 版本之前的行為是嚴格的
     ）。

     在 3.13 版的變更: Symlink loops are treated like other errors:
     *note OSError: 350. is raised in strict mode, and no exception is
     raised in non-strict mode.  In previous versions, *note
     RuntimeError: 179. is raised no matter the value of 'strict'.

 -- 方法: Path.readlink ()

     回傳符號連結指向的路徑（如 *note os.readlink(): 8c5. 的回傳值）：

          >>> p = Path('mylink')
          >>> p.symlink_to('setup.py')
          >>> p.readlink()
          PosixPath('setup.py')

     在 3.9 版被加入.

     在 3.13 版的變更: Raises *note UnsupportedOperation: 20c. if *note
     os.readlink(): 8c5. is not available.  In previous versions, *note
     NotImplementedError: 20d. was raised.


File: python.info,  Node: Querying file type and status,  Next: Reading and writing files,  Prev: Expanding and resolving paths,  Up: 實體路徑

5.11.1.11 Querying file type and status
.......................................

在 3.8 版的變更: *note exists(): 9ba.、*note is_dir(): 215.、*note
is_file(): 214.、*note is_mount(): 9bb.、*note is_symlink(): 9bc.、*note
is_block_device(): 9bd.、*note is_char_device(): 9be.、*note is_fifo():
9bf.、*note is_socket(): 9c0. 遇到路徑包含 OS 層無法表示的字元時現在會回
傳 ‘False’ 而不是引發例外。

 -- 方法: Path.stat (*, follow_symlinks=True)

     回傳一個包含該路徑資訊的 *note os.stat_result: 142c. 物件，像 *note
     os.stat(): 448. 一樣。每次呼叫此方法都會重新查詢結果。

     此方法通常會跟隨 (follow) 符號連結；想要取得符號連結的資訊，可以加
     上引數 ‘follow_symlinks=False’ 或使用 *note lstat(): 269c.。

          >>> p = Path('setup.py')
          >>> p.stat().st_size
          956
          >>> p.stat().st_mtime
          1327883547.852554

     在 3.10 版的變更: 新增 'follow_symlinks' 參數。

 -- 方法: Path.lstat ()

     類似 *note Path.stat(): 7c7.，但如果該路徑指向一個符號連結，則回傳
     符號連結的資訊而不是其指向的目標。

 -- 方法: Path.exists (*, follow_symlinks=True)

     如果路徑指向存在的檔案或目錄則回傳 ‘True’。

     此方法通常會跟隨符號連結；如果想檢查符號連結是否存在，可以加上引數
     ‘follow_symlinks=False’。

          >>> Path('.').exists()
          True
          >>> Path('setup.py').exists()
          True
          >>> Path('/etc').exists()
          True
          >>> Path('nonexistentfile').exists()
          False

     在 3.12 版的變更: 新增 'follow_symlinks' 參數。

 -- 方法: Path.is_file (*, follow_symlinks=True)

     Return ‘True’ if the path points to a regular file, ‘False’ if it
     points to another kind of file.

     如果路徑不存在或者是一個斷掉的符號連結則也會回傳 ‘False’；其他錯誤
     （例如權限錯誤）則會傳遞出來。

     This method normally follows symlinks; to exclude symlinks, add the
     argument ‘follow_symlinks=False’.

     在 3.13 版的變更: 新增 'follow_symlinks' 參數。

 -- 方法: Path.is_dir (*, follow_symlinks=True)

     Return ‘True’ if the path points to a directory, ‘False’ if it
     points to another kind of file.

     如果路徑不存在或者是一個斷掉的符號連結則也會回傳 ‘False’；其他錯誤
     （例如權限錯誤）則會傳遞出來。

     This method normally follows symlinks; to exclude symlinks to
     directories, add the argument ‘follow_symlinks=False’.

     在 3.13 版的變更: 新增 'follow_symlinks' 參數。

 -- 方法: Path.is_symlink ()

     如果該路徑指向一個符號連結則回傳 ‘True’，否則回傳 ‘False’。

     如果該路徑不存在也會回傳 ‘False’；其他錯誤（例如權限錯誤）則會傳遞
     出來。

 -- 方法: Path.is_junction ()

     如果該路徑指向一個連接點 (junction) 則回傳 ‘True’，對其他類型的檔案
     則回傳 ‘False’。目前只有 Windows 支援連接點。

     在 3.12 版被加入.

 -- 方法: Path.is_mount ()

     如果路徑是一個 'mount point'（一個檔案系統裡掛載不同檔案系統的存取
     點）則回傳 ‘True’。在 POSIX 上，此函式檢查 'path' 的父路徑
     ‘path/..’ 是否和 'path' 在不同的裝置上，或者 ‘path/..’ 和 'path' 是
     否指向相同裝置的相同 i-node ── 這對於所有 Unix 和 POSIX 變體來說應
     該會偵測出掛載點。在 Windows 上，一個掛載點被視為一個根磁碟機字母（
     例如 ‘c:\’）、一個 UNC share（例如 ‘\\server\share’）或是掛載的檔案
     系統目錄。

     在 3.7 版被加入.

     在 3.12 版的變更: 加入對 Windows 的支援。

 -- 方法: Path.is_socket ()

     如果該路徑指向一個 Unix socket（或者是一個指向 Unix socket 的符號連
     結）則會回傳 ‘True’，如果指向其他類型的檔案則回傳 ‘False’。

     如果路徑不存在或者是一個斷掉的符號連結則也會回傳 ‘False’；其他錯誤
     （例如權限錯誤）則會傳遞出來。

 -- 方法: Path.is_fifo ()

     如果該路徑指向一個 FIFO（或者是一個指向 FIFO 的符號連結）則會回傳
     ‘True’，如果指向其他類型的檔案則回傳 ‘False’。

     如果路徑不存在或者是一個斷掉的符號連結則也會回傳 ‘False’；其他錯誤
     （例如權限錯誤）則會傳遞出來。

 -- 方法: Path.is_block_device ()

     如果該路徑指向一個區塊裝置 (block device)（或者是一個指向區塊裝置的
     符號連結）則會回傳 ‘True’，如果指向其他類型的檔案則回傳 ‘False’。

     如果路徑不存在或者是一個斷掉的符號連結則也會回傳 ‘False’；其他錯誤
     （例如權限錯誤）則會傳遞出來。

 -- 方法: Path.is_char_device ()

     如果該路徑指向一個字元裝置 (character device)（或者是一個指向字元裝
     置的符號連結）則會回傳 ‘True’，如果指向其他類型的檔案則回傳
     ‘False’。

     如果路徑不存在或者是一個斷掉的符號連結則也會回傳 ‘False’；其他錯誤
     （例如權限錯誤）則會傳遞出來。

 -- 方法: Path.samefile (other_path)

     回傳此路徑是否指向與 'other_path' 相同的檔案，'other_path' 可以是路
     徑 (Path) 物件或字串。其語義類似於 *note os.path.samefile(): f14. 和
     *note os.path.samestat(): f13.。

     若任何一個檔案因為某些原因無法存取，則引發 *note OSError: 350.。

          >>> p = Path('spam')
          >>> q = Path('eggs')
          >>> p.samefile(q)
          False
          >>> p.samefile('spam')
          True

     在 3.5 版被加入.


File: python.info,  Node: Reading and writing files,  Next: 讀取目錄,  Prev: Querying file type and status,  Up: 實體路徑

5.11.1.12 Reading and writing files
...................................

 -- 方法: Path.open (mode='r', buffering=-1, encoding=None, errors=None,
          newline=None)

     開啟該路徑指向的檔案，像內建的 *note open(): 4c0. 函式做的一樣：

          >>> p = Path('setup.py')
          >>> with p.open() as f:
          ...     f.readline()
          ...
          '#!/usr/bin/env python3\n'

 -- 方法: Path.read_text (encoding=None, errors=None, newline=None)

     將路徑指向的檔案的解碼內容以字串形式回傳：

          >>> p = Path('my_text_file')
          >>> p.write_text('Text file contents')
          18
          >>> p.read_text()
          'Text file contents'

     該檔案被打開並且隨後關閉。可選參數的含義與 *note open(): 4c0. 中的
     相同。

     在 3.5 版被加入.

     在 3.13 版的變更: 新增 'newline' 參數。

 -- 方法: Path.read_bytes ()

     將路徑指向的檔案的二進位內容以一個位元組物件回傳：

          >>> p = Path('my_binary_file')
          >>> p.write_bytes(b'Binary file contents')
          20
          >>> p.read_bytes()
          b'Binary file contents'

     在 3.5 版被加入.

 -- 方法: Path.write_text (data, encoding=None, errors=None,
          newline=None)

     以文字模式開啟指向的檔案，將 'data' 寫到檔案，並關閉檔案:: ：

          >>> p = Path('my_text_file')
          >>> p.write_text('Text file contents')
          18
          >>> p.read_text()
          'Text file contents'

     一個名稱相同的已存在檔案會被覆寫。可選參數和 *note open(): 4c0. 的
     參數有相同意義。

     在 3.5 版被加入.

     在 3.10 版的變更: 新增 'newline' 參數。

 -- 方法: Path.write_bytes (data)

     以位元組模式開啟指向的檔案，將 'data' 寫到檔案，並關閉檔案:: ：

          >>> p = Path('my_binary_file')
          >>> p.write_bytes(b'Binary file contents')
          20
          >>> p.read_bytes()
          b'Binary file contents'

     一個名稱相同的已存在檔案會被覆寫。

     在 3.5 版被加入.


File: python.info,  Node: 讀取目錄,  Next: 建立檔案與目錄,  Prev: Reading and writing files,  Up: 實體路徑

5.11.1.13 讀取目錄
..................

 -- 方法: Path.iterdir ()

     當該路徑指向一個目錄，會 yield 目錄裡面的路徑物件：

          >>> p = Path('docs')
          >>> for child in p.iterdir(): child
          ...
          PosixPath('docs/conf.py')
          PosixPath('docs/_templates')
          PosixPath('docs/make.bat')
          PosixPath('docs/index.rst')
          PosixPath('docs/_build')
          PosixPath('docs/_static')
          PosixPath('docs/Makefile')

     子路徑會以任意順序被 yield，且不會包含特殊項目 ‘'.'’ 和 ‘'..'’。如
     果一個檔案在建立這個疊代器之後加到該目錄或從目錄刪除，這個檔案的路
     徑物件是否會被包含是沒有明定的。

     If the path is not a directory or otherwise inaccessible, *note
     OSError: 350. is raised.

 -- 方法: Path.glob (pattern, *, case_sensitive=None,
          recurse_symlinks=False)

     在該路徑表示的目錄裡，以 glob 方式比對所給定的相對 'pattern'，並
     yield 所有比對到的檔案（任意類型）：

          >>> sorted(Path('.').glob('*.py'))
          [PosixPath('pathlib.py'), PosixPath('setup.py'), PosixPath('test_pathlib.py')]
          >>> sorted(Path('.').glob('*/*.py'))
          [PosixPath('docs/conf.py')]
          >>> sorted(Path('.').glob('**/*.py'))
          [PosixPath('build/lib/pathlib.py'),
           PosixPath('docs/conf.py'),
           PosixPath('pathlib.py'),
           PosixPath('setup.py'),
           PosixPath('test_pathlib.py')]

     也參考
     ......

     *note Pattern language: 2694. documentation.

     預設情況下，或者當 'case_sensitive' 僅限關鍵字引數被設定為 ‘None’ 的
     時候，此方法會使用平台特定的大小寫規則來比對路徑；通常在 POSIX 上會
     區分大小寫，而在 Windows 上不區分大小寫。將 'case_sensitive' 設成
     ‘True’ 或 ‘False’ 會覆寫這個行為。

     By default, or when the 'recurse_symlinks' keyword-only argument is
     set to ‘False’, this method follows symlinks except when expanding
     "‘**’" wildcards.  Set 'recurse_symlinks' to ‘True’ to always
     follow symlinks.

     引發一個附帶引數 ‘self’、‘pattern’ 的*note 稽核事件: 17bd.
     ‘pathlib.Path.glob’。

     在 3.12 版的變更: 新增 'case_sensitive' 參數。

     在 3.13 版的變更: The 'recurse_symlinks' parameter was added.

     在 3.13 版的變更: The 'pattern' parameter accepts a *note path-like
     object: ac2.

     在 3.13 版的變更: Any *note OSError: 350. exceptions raised from
     scanning the filesystem are suppressed.  In previous versions, such
     exceptions are suppressed in many cases, but not all.

 -- 方法: Path.rglob (pattern, *, case_sensitive=None,
          recurse_symlinks=False)

     Glob the given relative 'pattern' recursively.  This is like
     calling *note Path.glob(): 212. with "‘**/’" added in front of the
     'pattern'.

     也參考
     ......

     *note Pattern language: 2694. and *note Path.glob(): 212.
     documentation.

     引發一個附帶引數 ‘self’、‘pattern’ 的*note 稽核事件: 17bd.
     ‘pathlib.Path.rglob’。

     在 3.12 版的變更: 新增 'case_sensitive' 參數。

     在 3.13 版的變更: The 'recurse_symlinks' parameter was added.

     在 3.13 版的變更: The 'pattern' parameter accepts a *note path-like
     object: ac2.

 -- 方法: Path.walk (top_down=True, on_error=None,
          follow_symlinks=False)

     透過由上而下或由下而上地走訪目錄樹產生目錄樹裡的檔案名稱。

     對每個以 'self' 為根且在目錄樹裡的目錄（包含 'self' 但不包含 '.'  和
     '..'  ），此方法會 yield 一個 ‘(dirpath, dirnames, filenames)’ 的三
     元素元組。

     'dirpath' 是一個目前走訪到的目錄的 *note Path: 20e.，'dirnames' 是
     一個 'dirpath' 裡的子目錄名稱的字串串列（不包含 ‘'.'’ 和 ‘'..'’ ）
     ，而 'filenames' 是一個 'dirpath' 裡非目錄檔案名稱的字串串列。要取
     得在 'dirpath' 裡檔案或目錄的完整路徑（以 'self' 開頭），可以使用
     ‘dirpath / name’。會根據檔案系統來決定串列是否有排序。

     如果可選引數 'top_down' 是 true（預設值），一個目錄的三元素元組會在
     其任何子目錄的三元素元組之前產生（目錄是由上而下走訪）。如果
     'top_down' 是 false，一個目錄的三元素元組會在其所有子目錄的三元素元
     組之後產生（目錄是由下而上走訪）。不論 'top_down' 的值是什麼，子目
     錄的串列會在走訪該目錄及其子目錄的三元素元組之前取得。

     當 'top_down' 是 true，呼叫者可以原地 (in-place) 修改 'dirnames' 串
     列（例如使用 *note del: 16a9. 或切片賦值 (slice assignment)），且
     *note Path.walk(): 450. 只會遞迴進名稱依然留在 'dirnames' 裡的子目
     錄。這可以用來修剪搜尋，或者強加特定順序的訪問，或者甚至在繼續
     *note Path.walk(): 450. 之前，用來告訴 *note Path.walk(): 450. 關於
     呼叫者建立或重新命名的目錄。當 'top_down' 是 false 的時候，修改
     'dirnames' 對 *note Path.walk(): 450. 的行為沒有影響，因為
     'dirnames' 裡的目錄已經在 'dirnames' yield 給呼叫者之前被產生。

     預設來自 *note os.scandir(): a02. 的錯誤會被忽略。如果指定了可選引
     數 'on_error'（它應該要是一個可呼叫物件），它會被以一個 *note
     OSError: 350. 實例為引數來呼叫。這個可呼叫物件可以處理錯誤以繼續走
     訪，或者再次引發錯誤來停止走訪。注意，檔案名稱可以從例外物件的
     ‘filename’ 屬性來取得。

     預設 *note Path.walk(): 450. 不會跟隨符號連結，而是會把它們加到
     'filenames' 串列。將 'follow_symlinks' 設定為 true 會解析符號連結，
     並將它們根據其指向的目標放在適當的 'dirnames' 和 'filenames'，而因
     此訪問到符號連結指向的目錄（在有支援符號連結的地方）。

          備註: 需要注意的是如果符號連結指向一個其本身的父目錄，則將
          'follow_symlinks' 設定為 true 會導致無窮的遞迴。*note
          Path.walk(): 450. 不會紀錄其已經訪問過的目錄。

          備註: *note Path.walk(): 450. 假設其走訪的目錄在執行過程中不會
          被修改。舉例來說，如果在 'dirnames' 裡的目錄已經被一個符號連結
          取代，且 'follow_symlinks' 是 false，*note Path.walk(): 450. 依
          然會試著往下進入它。為了防止這樣的行為，可以從 'dirnames' 適當
          地移除目錄。

          備註: 如果 'follow_symlinks' 是 false，和 *note os.walk():
          451. 行為不同的是 *note Path.walk(): 450. 會將指向目錄的符號連
          結放在 'filenames' 串列。

     這個範例會顯示在每個目錄裡所有檔案使用的位元組數量，同時間忽略
     ‘__pycache__’ 目錄：

          from pathlib import Path
          for root, dirs, files in Path("cpython/Lib/concurrent").walk(on_error=print):
            print(
                root,
                "consumes",
                sum((root / file).stat().st_size for file in files),
                "bytes in",
                len(files),
                "non-directory files"
            )
            if '__pycache__' in dirs:
                  dirs.remove('__pycache__')

     下一個範例是 *note shutil.rmtree(): 2d2. 的一個簡單的實作方式。由下
     而上走訪目錄樹是必要的，因為 *note rmdir(): 26a0. 不允許在目錄為空
     之前刪除它：

          # Delete everything reachable from the directory "top".
          # CAUTION:  This is dangerous! For example, if top == Path('/'),
          # it could delete all of your files.
          for root, dirs, files in top.walk(top_down=False):
              for name in files:
                  (root / name).unlink()
              for name in dirs:
                  (root / name).rmdir()

     在 3.12 版被加入.


File: python.info,  Node: 建立檔案與目錄,  Next: Renaming and deleting,  Prev: 讀取目錄,  Up: 實體路徑

5.11.1.14 建立檔案與目錄
........................

 -- 方法: Path.touch (mode=0o666, exist_ok=True)

     根據給定路徑來建立一個檔案。如果 'mode' 有給定，它會與行程的
     ‘umask’ 值結合，以確定檔案模式和存取旗標。當檔案已經存在時，若
     'exist_ok' 為 true 則函式不會失敗（其變更時間會被更新為當下時間），
     否則會引發 *note FileExistsError: fc3.。

     也參考
     ......

     The *note open(): 269e, *note write_text(): dea. and *note
     write_bytes(): dec. methods are often used to create files.

 -- 方法: Path.mkdir (mode=0o777, parents=False, exist_ok=False)

     在給定路徑下建立一個新的目錄。如果有給 'mode' 則會結合行程
     (process) 的 ‘umask’ 值來決定檔案模式與存取旗標 (access flag)。如果
     路徑已經存在，會引發 *note FileExistsError: fc3.。

     如果 'parents' 是 true，則任何缺少的父路徑都會依需要被建立；它們不
     考慮 'mode' 而會以預設的權限來建立（模仿 POSIX 的 ‘mkdir -p’ 指令）
     。

     如果 'parents' 是 false（預設值），缺少的父路徑會引發 *note
     FileNotFoundError: e67.。

     如果 'exist_ok' 是 false（預設值），則當目標目錄已經存在的話會引發
     *note FileExistsError: fc3.。

     如果 'exist_ok' 是 true，只有當最後的路徑組成不是一個已存在的非目錄
     檔案，*note FileExistsError: fc3. 例外會被忽略（與 POSIX 的 ‘mkdir
     -p’ 指令行為相同）。

     在 3.5 版的變更: 新增 'exist_ok' 參數。

 -- 方法: Path.symlink_to (target, target_is_directory=False)

     使這個路徑成為一個指向 'target' 的符號連結。

     在 Windows 上，符號連結代表一個檔案或目錄，且不會隨著目標 (target)
     動態改變。如果目標存在，則符號連結的類型會被建立來符合其目標。否則
     如果 'target_is_directory' 是 true，該符號連結會被建立成目錄，如果
     不是則建立成檔案（預設值）。在非 Windows 平台上，
     'target_is_directory' 會被忽略。

          >>> p = Path('mylink')
          >>> p.symlink_to('setup.py')
          >>> p.resolve()
          PosixPath('/home/antoine/pathlib/setup.py')
          >>> p.stat().st_size
          956
          >>> p.lstat().st_size
          8

          備註: 引數的順序 (link, target) 和 *note os.symlink(): 108d. 相
          反。

     在 3.13 版的變更: Raises *note UnsupportedOperation: 20c. if *note
     os.symlink(): 108d. is not available.  In previous versions, *note
     NotImplementedError: 20d. was raised.

 -- 方法: Path.hardlink_to (target)

     使這個路徑成為與 'target' 相同檔案的一個硬連結 (hard link)。

          備註: 引數的順序 (link, target) 和 *note os.link(): 1088. 相反
          。

     在 3.10 版被加入.

     在 3.13 版的變更: Raises *note UnsupportedOperation: 20c. if *note
     os.link(): 1088. is not available.  In previous versions, *note
     NotImplementedError: 20d. was raised.


File: python.info,  Node: Renaming and deleting,  Next: Permissions and ownership,  Prev: 建立檔案與目錄,  Up: 實體路徑

5.11.1.15 Renaming and deleting
...............................

 -- 方法: Path.rename (target)

     將此檔案或目錄重新命名為給定的 'target' ，並回傳一個新的 ‘Path’ 實
     例指向該 'target'。在 Unix 系統上，若 'target' 存在且為一個檔案，若
     使用者有權限，則會在不顯示訊息的情況下進行取代。在 Windows 系統上，
     若 'target' 存在，則會引發 *note FileExistsError: fc3. 錯誤。
     'target' 可以是字串或另一個路徑物件：

          >>> p = Path('foo')
          >>> p.open('w').write('some text')
          9
          >>> target = Path('bar')
          >>> p.rename(target)
          PosixPath('bar')
          >>> target.open().read()
          'some text'

     目標路徑可以是絕對路徑或相對路徑。相對路徑會相對於當前的工作目錄進
     行解釋，'而不是'相對於 ‘Path’ 物件所在的目錄。

     此功能是使用 *note os.rename(): 108a. 實現的，並提供相同的保證。

     在 3.8 版的變更: 新增了回傳值，回傳新的 ‘Path’ 實例。

 -- 方法: Path.replace (target)

     將此檔案或目錄重新命名為給定的 'target'，並回傳一個指向 'target' 的
     新 ‘Path’ 實例。如果 'target' 指向一個現有的檔案或空目錄，它將被無
     條件地取代。

     目標路徑可以是絕對路徑或相對路徑。相對路徑會相對於當前的工作目錄進
     行解釋，'而不是'相對於 ‘Path’ 物件所在的目錄。

     在 3.8 版的變更: 新增了回傳值，回傳新的 ‘Path’ 實例。

 -- 方法: Path.unlink (missing_ok=False)

     移除這個檔案或符號連結。如果路徑指向目錄，請改用 *note
     Path.rmdir(): 26a0.。

     如果 'missing_ok' 是 false（預設值），*note FileNotFoundError: e67.
     會在路徑不存在時被引發。

     如果 'missing_ok' 是 true，*note FileNotFoundError: e67. 例外會被忽
     略（行為與 POSIX ‘rm -f’ 指令相同）。

     在 3.8 版的變更: 新增 'missing_ok' 參數。

 -- 方法: Path.rmdir ()

     移除此目錄。該目錄必須為空。


File: python.info,  Node: Permissions and ownership,  Prev: Renaming and deleting,  Up: 實體路徑

5.11.1.16 Permissions and ownership
...................................

 -- 方法: Path.owner (*, follow_symlinks=True)

     Return the name of the user owning the file.  *note KeyError: 2fb.
     is raised if the file's user identifier (UID) isn't found in the
     system database.

     This method normally follows symlinks; to get the owner of the
     symlink, add the argument ‘follow_symlinks=False’.

     在 3.13 版的變更: Raises *note UnsupportedOperation: 20c. if the
     *note pwd: a0. module is not available.  In earlier versions, *note
     NotImplementedError: 20d. was raised.

     在 3.13 版的變更: 新增 'follow_symlinks' 參數。

 -- 方法: Path.group (*, follow_symlinks=True)

     Return the name of the group owning the file.  *note KeyError: 2fb.
     is raised if the file's group identifier (GID) isn't found in the
     system database.

     This method normally follows symlinks; to get the group of the
     symlink, add the argument ‘follow_symlinks=False’.

     在 3.13 版的變更: Raises *note UnsupportedOperation: 20c. if the
     *note grp: 5c. module is not available.  In earlier versions, *note
     NotImplementedError: 20d. was raised.

     在 3.13 版的變更: 新增 'follow_symlinks' 參數。

 -- 方法: Path.chmod (mode, *, follow_symlinks=True)

     修改檔案模式 (file mode) 與權限，像 *note os.chmod(): 200. 一樣。

     此方法通常會跟隨符號連結。一些 Unix 類型支援修改符號連結本身的權限
     ；在這些平台上你可以加上引數 ‘follow_symlinks=False’ 或使用 *note
     lchmod(): 26a7.。

          >>> p = Path('setup.py')
          >>> p.stat().st_mode
          33277
          >>> p.chmod(0o444)
          >>> p.stat().st_mode
          33060

     在 3.10 版的變更: 新增 'follow_symlinks' 參數。

 -- 方法: Path.lchmod (mode)

     類似 *note Path.chmod(): 7c8.，但如果該路徑指向一個符號連結，則符號
     連結的模式 (mode) 會被改變而不是其指向的目標。


File: python.info,  Node: Pattern language,  Next: Comparison to the glob module,  Prev: 實體路徑,  Up: pathlib --- 物件導向檔案系統路徑

5.11.1.17 Pattern language
..........................

The following wildcards are supported in patterns for *note
full_match(): 210, *note glob(): 212. and *note rglob(): 213.:

‘**’ (entire segment)

     Matches any number of file or directory segments, including zero.

‘*’ (entire segment)

     Matches one file or directory segment.

‘*’ (part of a segment)

     Matches any number of non-separator characters, including zero.

‘?’

     Matches one non-separator character.

‘[seq]’

     Matches one character in 'seq'.

‘[!seq]’

     Matches one character not in 'seq'.

For a literal match, wrap the meta-characters in brackets.  For example,
‘"[?]"’ matches the character ‘"?"’.

The "‘**’" wildcard enables recursive globbing.  A few examples:

Pattern                       Meaning
                              
--------------------------------------------------------------------------------------------------------
                              
"‘**/*’"                      Any path with at least one segment.
                              
                              
"‘**/*.py’"                   Any path with a final segment ending "‘.py’".
                              
                              
"‘assets/**’"                 Any path starting with "‘assets/’".
                              
                              
"‘assets/**/*’"               Any path starting with "‘assets/’", excluding "‘assets/’" itself.
                              

     備註: Globbing with the "‘**’" wildcard visits every directory in
     the tree.  Large directory trees may take a long time to search.

在 3.13 版的變更: Globbing with a pattern that ends with "‘**’" returns
both files and directories.  In previous versions, only directories were
returned.

In *note Path.glob(): 212. and *note rglob(): 213, a trailing slash may
be added to the pattern to match only directories.

在 3.11 版的變更: Globbing with a pattern that ends with a pathname
components separator (*note sep: 610. or *note altsep: 611.) returns
only directories.


File: python.info,  Node: Comparison to the glob module,  Next: Comparison to the os and os path modules,  Prev: Pattern language,  Up: pathlib --- 物件導向檔案系統路徑

5.11.1.18 Comparison to the ‘glob’ module
.........................................

The patterns accepted and results generated by *note Path.glob(): 212.
and *note Path.rglob(): 213. differ slightly from those by the *note
glob: 5a. module:

  1. Files beginning with a dot are not special in pathlib.  This is
     like passing ‘include_hidden=True’ to *note glob.glob(): 280.

  2. "‘**’" pattern components are always recursive in pathlib.  This is
     like passing ‘recursive=True’ to *note glob.glob(): 280.

  3. "‘**’" pattern components do not follow symlinks by default in
     pathlib.  This behaviour has no equivalent in *note glob.glob():
     280, but you can pass ‘recurse_symlinks=True’ to *note Path.glob():
     212. for compatible behaviour.

  4. Like all *note PurePath: 44e. and *note Path: 20e. objects, the
     values returned from *note Path.glob(): 212. and *note
     Path.rglob(): 213. don't include trailing slashes.

  5. The values returned from pathlib's ‘path.glob()’ and ‘path.rglob()’
     include the 'path' as a prefix, unlike the results of
     ‘glob.glob(root_dir=path)’.

  6. The values returned from pathlib's ‘path.glob()’ and ‘path.rglob()’
     may include 'path' itself, for example when globbing "‘**’",
     whereas the results of ‘glob.glob(root_dir=path)’ never include an
     empty string that would correspond to 'path'.


File: python.info,  Node: Comparison to the os and os path modules,  Prev: Comparison to the glob module,  Up: pathlib --- 物件導向檔案系統路徑

5.11.1.19 Comparison to the ‘os’ and ‘os.path’ modules
......................................................

pathlib implements path operations using *note PurePath: 44e. and *note
Path: 20e. objects, and so it's said to be 'object-oriented'.  On the
other hand, the *note os: 91. and *note os.path: 92. modules supply
functions that work with low-level ‘str’ and ‘bytes’ objects, which is a
more 'procedural' approach.  Some users consider the object-oriented
style to be more readable.

Many functions in *note os: 91. and *note os.path: 92. support ‘bytes’
paths and *note paths relative to directory descriptors: 1083.  These
features aren't available in pathlib.

Python's ‘str’ and ‘bytes’ types, and portions of the *note os: 91. and
*note os.path: 92. modules, are written in C and are very speedy.
pathlib is written in pure Python and is often slower, but rarely slow
enough to matter.

pathlib's path normalization is slightly more opinionated and consistent
than *note os.path: 92.  For example, whereas *note os.path.abspath():
12af. eliminates "‘..’" segments from a path, which may change its
meaning if symlinks are involved, *note Path.absolute(): 15a6. preserves
these segments for greater safety.

pathlib's path normalization may render it unsuitable for some
applications:

  1. pathlib normalizes ‘Path("my_folder/")’ to ‘Path("my_folder")’,
     which changes a path's meaning when supplied to various operating
     system APIs and command-line utilities.  Specifically, the absence
     of a trailing separator may allow the path to be resolved as either
     a file or directory, rather than a directory only.

  2. pathlib normalizes ‘Path("./my_program")’ to ‘Path("my_program")’,
     which changes a path's meaning when used as an executable search
     path, such as in a shell or when spawning a child process.
     Specifically, the absence of a separator in the path may force it
     to be looked up in ‘PATH’ rather than the current directory.

As a consequence of these differences, pathlib is not a drop-in
replacement for *note os.path: 92.

* Menu:

* Corresponding tools::


File: python.info,  Node: Corresponding tools,  Up: Comparison to the os and os path modules

5.11.1.20 Corresponding tools
.............................

以下是一張表格，對應許多 *note os: 91. 函式及其相符於 *note PurePath:
44e./*note Path: 20e. 的項目。

*note os: 91. 和 *note os.path: 92.       *note pathlib: 93.
                                          
---------------------------------------------------------------------------------------------
                                          
*note os.path.dirname(): 26ac.            *note PurePath.parent: 162b.
                                          
                                          
*note os.path.basename(): 26ad.           *note PurePath.name: 268e.
                                          
                                          
*note os.path.splitext(): 26ae.           *note PurePath.stem: 2691. 和
                                          *note PurePath.suffix: 268f.
                                          
                                          
*note os.path.join(): 1527.               *note PurePath.joinpath(): 2693.
                                          
                                          
*note os.path.isabs(): 209.               *note PurePath.is_absolute(): 1629.
                                          
                                          
*note os.path.relpath(): 452.             *note PurePath.relative_to(): 2ac. (1)
                                          
                                          
*note os.path.expanduser(): 9b8.          *note Path.expanduser(): de8. (2)
                                          
                                          
*note os.path.realpath(): 20a.            *note Path.resolve(): 15f7.
                                          
                                          
*note os.path.abspath(): 12af.            *note Path.absolute(): 15a6. (3)
                                          
                                          
*note os.path.exists(): 9b2.              *note Path.exists(): 9ba.
                                          
                                          
*note os.path.isfile(): 9b5.              *note Path.is_file(): 214.
                                          
                                          
*note os.path.isdir(): 9b4.               *note Path.is_dir(): 215.
                                          
                                          
*note os.path.islink(): 9b0.              *note Path.is_symlink(): 9bc.
                                          
                                          
*note os.path.isjunction(): 44b.          *note Path.is_junction(): 453.
                                          
                                          
*note os.path.ismount(): 9b6.             *note Path.is_mount(): 9bb.
                                          
                                          
*note os.path.samefile(): f14.            *note Path.samefile(): de6.
                                          
                                          
*note os.getcwd(): 1907.                  *note Path.cwd(): 1628.
                                          
                                          
*note os.stat(): 448.                     *note Path.stat(): 7c7.
                                          
                                          
*note os.lstat(): 449.                    *note Path.lstat(): 269c.
                                          
                                          
*note os.listdir(): 1092.                 *note Path.iterdir(): 1525.
                                          
                                          
*note os.walk(): 451.                     *note Path.walk(): 450. (4)
                                          
                                          
*note os.mkdir(): 202.、                  *note Path.mkdir(): de7.
*note os.makedirs(): 203.                 

*note os.link(): 1088.                    *note Path.hardlink_to(): 7c5.
                                          
                                          
*note os.symlink(): 108d.                 *note Path.symlink_to(): 7c6.
                                          
                                          
*note os.readlink(): 8c5.                 *note Path.readlink(): 8c4.
                                          
                                          
*note os.rename(): 108a.                  *note Path.rename(): 26a4.
                                          
                                          
*note os.replace(): 108b.                 *note Path.replace(): 26a5.
                                          
                                          
*note os.remove(): 1089.、                *note Path.unlink(): 18f7.
*note os.unlink(): 108e.                  

*note os.rmdir(): 108c.                   *note Path.rmdir(): 26a0.
                                          
                                          
*note os.chmod(): 200.                    *note Path.chmod(): 7c8.
                                          
                                          
*note os.lchmod(): 1ff.                   *note Path.lchmod(): 26a7.
                                          

註解
....

   ---------- Footnotes ----------

   (1) *note os.path.relpath(): 452. calls *note abspath(): 12af. to
make paths absolute and remove "‘..’" parts, whereas *note
PurePath.relative_to(): 2ac. is a lexical operation that raises *note
ValueError: 1e7. when its inputs' anchors differ (e.g.  if one path is
absolute and the other relative.)

   (2) *note os.path.expanduser(): 9b8. returns the path unchanged if
the home directory can't be resolved, whereas *note Path.expanduser():
de8. raises *note RuntimeError: 179.

   (3) *note os.path.abspath(): 12af. removes "‘..’" components without
resolving symlinks, which may change the meaning of the path, whereas
*note Path.absolute(): 15a6. leaves any "‘..’" components in the path.

   (4) *note os.walk(): 451. always follows symlinks when categorizing
paths into 'dirnames' and 'filenames', whereas *note Path.walk(): 450.
categorizes all symlinks into 'filenames' when 'follow_symlinks' is
false (the default.)


File: python.info,  Node: os path --- 常見的路徑名操作,  Next: fileinput --- 逐列疊代多個輸入串流,  Prev: pathlib --- 物件導向檔案系統路徑,  Up: 檔案與目錄存取

5.11.2 ‘os.path’ -- 常見的路徑名操作
------------------------------------

'原始碼：' Lib/genericpath.py(1)、Lib/posixpath.py(2) (用於 POSIX 系統)
和 Lib/ntpath.py(3) (用於 Windows).

__________________________________________________________________

該模組實現了一些有用的路徑名操作函式。若要讀取或寫入檔案，請參閱 *note
open(): 4c0. 函數，要存取檔案系統，請參閱 *note os: 91. 模組。路徑參數可
以以字串、位元組或任何依照 *note os.PathLike: bf8. 協議實作的物件傳遞。

與 Unix shell 不同，Python 不會'自動'進行路徑展開 (path expansions)。當
應用程式需要進行類似 shell 的路徑展開時，可以明確地呼叫 *note
expanduser(): 9b8. 和 *note expandvars(): 1347. 等函式。（另請參閱 *note
glob: 5a. 模組。）

也參考
......

*note pathlib: 93. 模組提供了高階的路徑物件。

     備註: 所有這些函數都只接受位元組或字串物件作為參數。如果回傳的是路
     徑或檔案名稱，結果將是相同型別的物件。

     備註: 由於不同的作業系統具有不同的路徑命名慣例，在標準函式庫中的路
     徑模組有數個版本可供使用，而 *note os.path: 92. 模組都會是運行
     Python 之作業系統所適用本地路徑。然而，如果你想要操作'始終'以某個不
     同於本機格式表示的路徑，你也可以引入並使用對應的模組。它們都具有相
     同的介面：

        * ‘posixpath’ 用於 UNIX 形式的路徑

        * ‘ntpath’ 用於 Windows 的路徑

在 3.8 版的變更: 對於包含有作業系統層級無法表示之字元或位元組的路徑，
*note exists(): 9b2.、*note lexists(): 9b3.、*note isdir(): 9b4.、*note
isfile(): 9b5.、*note islink(): 9b0. 和 *note ismount(): 9b6. 函式現在會
回傳 ‘False’，而不是引發例外。

 -- 函式: os.path.abspath (path)

     回傳經正規化的絕對路徑名 'path' 。在大多數平台上，這等效於按照以下
     方式呼叫 *note normpath(): 12ae. 函式：‘normpath(join(os.getcwd(),
     path))’。

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 函式: os.path.basename (path)

     回傳路徑名 'path' 的基底名稱。這是將 'path' 傳遞給函式 *note
     split(): 26b1. 後回傳結果中的第二個元素。請注意，此函式的結果與
     Unix 的 ‘basename’ 程式不同；對於 ‘'/foo/bar/'’，‘basename’ 回傳
     ‘'bar'’，而 *note basename(): 26ad. 函式回傳空字串（‘''’）。

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 函式: os.path.commonpath (paths)

     Return the longest common sub-path of each pathname in the iterable
     'paths'.  Raise *note ValueError: 1e7. if 'paths' contain both
     absolute and relative pathnames, if 'paths' are on different
     drives, or if 'paths' is empty.  Unlike *note commonprefix(): de4,
     this returns a valid path.

     在 3.5 版被加入.

     在 3.6 版的變更: 接受一個*note 類路徑物件: ac2.的序列。

     在 3.13 版的變更: Any iterable can now be passed, rather than just
     sequences.

 -- 函式: os.path.commonprefix (list)

     回傳 'list' 中所有路徑的最長路徑前綴（逐字元比較）。如果 'list' 為
     空，則回傳空字串（‘''’）。

          備註: 由於此函式是逐字元比較，因此可能會回傳無效的路徑。若要獲
          得有效的路徑，請參考 *note commonpath(): de3. 函式。

               >>> os.path.commonprefix(['/usr/lib', '/usr/local/lib'])
               '/usr/l'

               >>> os.path.commonpath(['/usr/lib', '/usr/local/lib'])
               '/usr'

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 函式: os.path.dirname (path)

     回傳路徑名 'path' 的目錄名稱。這是將 'path' 傳遞給函式 *note
     split(): 26b1. 後回傳之成對結果中的第一個元素。

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 函式: os.path.exists (path)

     如果 'path' 是一個存在的路徑或一個開啟的檔案描述器則回傳 ‘True’。對
     於已損壞的符號連結則回傳 ‘False’。在某些平台上，即使 'path' 實際存
     在，如果未被授予執行 *note os.stat(): 448. 的權限，此函式仍可能回傳
     ‘False’。

     在 3.3 版的變更: 現在 'path' 可以是一個整數：如果它是一個開啟的檔案
     描述器，則回傳 ‘True’；否則回傳 ‘False’。

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 函式: os.path.lexists (path)

     如果 'path' 是一個存在的路徑則回傳 ‘True’，對已損壞的符號連結也是。
     在缺乏 *note os.lstat(): 449. 的平台上，與 *note exists(): 9b2. 函
     式等效。

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 函式: os.path.expanduser (path)

     在 Unix 和 Windows 上，將引數中以 ‘~’ 或 ‘~user’ 開頭的部分替換為該
     'user' 的家目錄。

     在 Unix 上，如果環境變數 ‘HOME’ 有被設置，則將初始的 ‘~’ 替換為該變
     數的值；否則將使用內建模組 *note pwd: a0. 在密碼目錄中查找當前使用
     者的家目錄。對於初始的 ‘~user’，直接在密碼目錄中查找該使用者的家目
     錄。

     在 Windows 上，如果 ‘USERPROFILE’ 有被設置，則使用該變數的值；否則
     將結合 ‘HOMEPATH’ 和 ‘HOMEDRIVE’。對於初始的 ‘~user’，會檢查當前使
     用者的家目錄的最後一個目錄元件是否與 ‘USERNAME’ 相符，如果相符則替
     換它。

     如果展開失敗或路徑不以波浪符號 (tilde) 開頭，則回傳原始路徑，不做任
     何變更。

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

     在 3.8 版的變更: 在 Windows 上不再使用 ‘HOME’ 變數。

 -- 函式: os.path.expandvars (path)

     回傳已展開環境變數的引數。形如 ‘$name’ 或 ‘${name}’ 的子字串會被替
     換為環境變數 'name' 的值。無效的變數名稱和對不存在變數的引用保持不
     變。

     在 Windows 上，除了支援 ‘$name’ 和 ‘${name}’ 形式的展開外，還支援
     ‘%name%’ 形式的展開。

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 函式: os.path.getatime (path)

     回傳 'path' 的最後存取時間。回傳值是一個浮點數，表示自紀元（參見
     *note time: d7. 模組）以來的秒數。如果檔案不存在或無法存取，則引發
     *note OSError: 350.。

 -- 函式: os.path.getmtime (path)

     回傳 'path' 的最後修改時間。回傳值是一個浮點數，表示自紀元（參見
     *note time: d7. 模組）以來的秒數。如果檔案不存在或無法存取，則引發
     *note OSError: 350.。

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 函式: os.path.getctime (path)

     回傳系統的 ctime。在某些系統（如 Unix）上，這是最後一次元數據
     (metadata) 更改的時間，在其他系統（如 Windows）上則是 'path' 的建立
     時間。回傳值是一個浮點數，表示自紀元（參見 *note time: d7. 模組）以
     來的秒數。如果檔案不存在或無法存取），則引發 *note OSError: 350.。

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 函式: os.path.getsize (path)

     回傳 'path' 的大小（以位元組為單位）。如果檔案不存在或無法存取，則
     引發 *note OSError: 350.。

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 函式: os.path.isabs (path)

     Return ‘True’ if 'path' is an absolute pathname.  On Unix, that
     means it begins with a slash, on Windows that it begins with two
     (back)slashes, or a drive letter, colon, and (back)slash together.

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

     在 3.13 版的變更: On Windows, returns ‘False’ if the given path
     starts with exactly one (back)slash.

 -- 函式: os.path.isfile (path)

     如果 'path' 是一個*note 已存在的: 9b2.常規檔案，則回傳 ‘True’。這將
     跟隨符號連結，因此同一個路徑可以同時回傳 *note islink(): 9b0. 和
     *note isfile(): 9b5. 的結果為真。

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 函式: os.path.isdir (path)

     如果 'path' 是一個*note 已存在的: 9b2.目錄，則回傳 ‘True’。這將跟隨
     符號連結，因此同一個路徑可以同時回傳 *note islink(): 9b0. 和 *note
     isfile(): 9b5. 的結果為真。

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 函式: os.path.isjunction (path)

     如果 'path' 是指向*note 已存在的: 9b3.目錄條目且為聯接點
     (junction)，則回傳 ‘True’。如果目前平台不支援聯接點，則始終返回
     ‘False’。

     在 3.12 版被加入.

 -- 函式: os.path.islink (path)

     如果 'path' 是指向*note 已存在的: 9b2.目錄項目且為符號連結，則回傳
     ‘True’。如果 Python 執行時不支援符號連結，則始終回傳 ‘False’。

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 函式: os.path.ismount (path)

     如果路徑名 'path' 是一個掛載點 ('mount point')，則回傳 ‘True’：即在
     檔案系統中掛載了不同的檔案系統。在 POSIX 系統上，該函式檢查 'path'
     的父目錄 ‘`path'/..’ 是否位於不同的設備上，或者 ‘`path'/..’ 和
     'path' 是否指向同一設備上的相同 i-node -- 這應該能夠檢測出所有 Unix
     和 POSIX 變體的掛載點。但無法可靠地檢測出相同檔案系統上的綁定掛載點
     (bind mount)。在 Windows 上，以驅動機字母開頭的根目錄和 UNC 共享路
     徑始終是掛載點，對於任何其他路徑，會呼叫 ‘GetVolumePathName’ 函式來
     檢查它是否與輸入路徑不同。

     在 3.4 版的變更: 新增在 Windows 上檢測非根目錄掛載點的支援。

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 函式: os.path.isdevdrive (path)

     如果路徑名 'path' 位於 Windows Dev 驅動機上，則回傳 ‘True’。Dev 驅
     動機針對開發人員場景進行了優化，提供更快的讀寫檔案性能。建議將其用
     於原始程式碼、臨時建置目錄、封包快取和其他 I/O 密集型操作。

     可能會對無效的路徑引發錯誤，例如，沒有可識別的驅動機的路徑，但在不
     支援 Dev 磁碟機的平台上返回 ‘False’。請參閱 Windows 文件(4)以了解有
     關啟用和建立 Dev 驅動機的資訊。

     在 3.12 版被加入.

     在 3.13 版的變更: The function is now available on all platforms,
     and will always return ‘False’ on those that have no support for
     Dev Drives

 -- 函式: os.path.isreserved (path)

     Return ‘True’ if 'path' is a reserved pathname on the current
     system.

     On Windows, reserved filenames include those that end with a space
     or dot; those that contain colons (i.e.  file streams such as
     "name:stream"), wildcard characters (i.e.  ‘'*?"<>'’), pipe, or
     ASCII control characters; as well as DOS device names such as
     "NUL", "CON", "CONIN$", "CONOUT$", "AUX", "PRN", "COM1", and
     "LPT1".

          備註: This function approximates rules for reserved paths on
          most Windows systems.  These rules change over time in various
          Windows releases.  This function may be updated in future
          Python releases as changes to the rules become broadly
          available.

     *note 適用: 1c56.：Windows。

     在 3.13 版被加入.

 -- 函式: os.path.join (path, *paths)

     聰明地連接一個或多個路徑段。回傳值是 'path' 和 '*paths' 的所有成員
     的串聯，每個非空部分後面都有一個目錄分隔符號，除了最後一個部分。換
     句話說，如果最後一個部分為空或以分隔符號結尾，結果只會以分隔符號結
     尾。如果一個段是絕對路徑（在 Windows 上需要驅動機和根），則忽略所有
     之前的段，並從絕對路徑段繼續連接。

     在 Windows 上，當遇到根路徑段（例如，‘r'\foo'’）時，驅動機不會被重
     置。如果一個段位於不同的驅動機上，或者是絕對路徑，則將忽略所有之前
     的段並重置驅動機。請注意，由於每個驅動機都有當前目錄，
     ‘os.path.join("c:", "foo")’ 表示相對於驅動機 ‘C:’ 的當前目錄的路徑
     （即 ‘c:foo’），而不是 ‘c:\foo’。

     在 3.6 版的變更: 'path' 和 'paths' 接受 *note path-like object:
     ac2. 作為參數。

 -- 函式: os.path.normcase (path)

     將路徑名的大小寫規範化。在 Windows 上，將路徑名中的所有字元轉換為小
     寫，並將正斜線轉換為反斜線。在其他作業系統上，回傳原始路徑。

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 函式: os.path.normpath (path)

     通過合併多餘的分隔符號和上層引用來標準化路徑名，使得 ‘A//B’、
     ‘A/B/’、‘A/./B’ 和 ‘A/foo/../B’ 都變成 ‘A/B’。這種字串操作可能會改
     變包含符號連結的路徑的含義。在 Windows 上，它將正斜線轉換為反斜線。
     要標準化大小寫，請使用 *note normcase(): 26b6.。

          備註: 在 POSIX 系統中，根據 IEEE Std 1003.1 2013 版; 4.13
          Pathname Resolution(5) 標準，如果一個路徑名恰好以兩個斜線開頭
          ，則在前導字元後的第一個部分可能會以由實作品自行定義的方式解釋
          ，雖然多於兩個前導字元應該被視為單個字元。

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 函式: os.path.realpath (path, *, strict=False)

     Return the canonical path of the specified filename, eliminating
     any symbolic links encountered in the path (if they are supported
     by the operating system).  On Windows, this function will also
     resolve MS-DOS (also called 8.3) style names such as ‘C:\\PROGRA~1’
     to ‘C:\\Program Files’.

     If a path doesn't exist or a symlink loop is encountered, and
     'strict' is ‘True’, *note OSError: 350. is raised.  If 'strict' is
     ‘False’ these errors are ignored, and so the result might be
     missing or otherwise inaccessible.

          備註: 此函式模擬作業系統使路徑成為規範的過程，Windows 和 UNIX
          之間在鏈接和後續路徑部份交互方式方面略有不同。

          作業系統的 API 會根據需要自動使路徑正則，因此通常不需要呼叫此
          函式。

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

     在 3.8 版的變更: 在 Windows 上，現在會解析符號連結和連接點。

     在 3.10 版的變更: 新增 'strict' 參數。

 -- 函式: os.path.relpath (path, start=os.curdir)

     從當前目錄或可選的 'start' 目錄回傳到 'path' 的相對檔案路徑。這是一
     個路徑計算：不會訪問檔案系統來確認 'path' 或 'start' 的存在或屬性。
     在 Windows 上，當 'path' 和 'start' 在不同的驅動機上時，會引發
     *note ValueError: 1e7.。

     'start' 的預設值為 *note os.curdir: 26b7.。

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 函式: os.path.samefile (path1, path2)

     如果兩個路徑名引數指向同一個檔案或目錄，則回傳 ‘True’。這是通過設備
     編號和 i-node 編號來確定的，如果對任一路徑名的 *note os.stat():
     448. 呼叫失敗，則會引發異常。

     在 3.2 版的變更: 新增對 Windows 的支援。

     在 3.4 版的變更: 現在在 Windows 上使用與其他所有平台相同的實作方式
     。

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 函式: os.path.sameopenfile (fp1, fp2)

     如果文件描述符 'fp1' 和 'fp2' 指向同一個檔案，則回傳 ‘True’。

     在 3.2 版的變更: 新增對 Windows 的支援。

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 函式: os.path.samestat (stat1, stat2)

     如果 stat 值組 'stat1' 和 'stat2' 指向同一個檔案，則回傳 ‘True’。這
     些結構可能由 *note os.fstat(): d32.、*note os.lstat(): 449. 或
     *note os.stat(): 448. 回傳。此函式使用 *note samefile(): f14. 和
     *note sameopenfile(): 26b8. 實現了底層比較。

     在 3.4 版的變更: 新增對 Windows 的支援。

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 函式: os.path.split (path)

     將路徑名 'path' 拆分為 ‘(head, tail)’ 一對，其中 'tail' 是最後一個
     路徑名部份，'head' 是在它之前的所有部分。'tail' 部分不會包含斜線；
     如果 'path' 以斜線結尾，則 'tail' 將為空。如果 'path' 中沒有斜線，
     則 'head' 將為空。如果 'path' 為空，則 'head' 和 'tail' 都為空。除
     非 'head' 是根目錄（僅有一個或多個斜線），否則從 'head' 中刪除尾部
     的斜線。在所有情況下，‘join(head, tail)’ 回傳指向與 'path' 相同位置
     的路徑（但字串可能不同）。還可以參考函式 *note dirname(): 26ac. 和
     *note basename(): 26ad.。

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 函式: os.path.splitdrive (path)

     將路徑名 'path' 拆分為 ‘(drive, tail)’ 一對，其中 'drive' 是掛載點
     或空字串。在不使用驅動機規範的系統上，'drive' 將始終為空字串。在所
     有情況下，‘drive + tail’ 將與 'path' 相同。

     在 Windows 上，將路徑名拆分為驅動機或 UNC 共享點以及相對路徑。

     如果路徑包含驅動機字母，則 'drive' 將包含從頭到冒號（包括冒號）的所
     有內容：

          >>> splitdrive("c:/dir")
          ("c:", "/dir")

     如果路徑包含 UNC 路徑，則驅動機將包含主機名和共享名：

          >>> splitdrive("//host/computer/dir")
          ("//host/computer", "/dir")

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 函式: os.path.splitroot (path)

     將路徑名 'path' 拆分為一個 3 項值組 ‘(drive, root, tail)’，其中
     'drive' 是設備名稱或掛載點，'root' 是驅動機後的分隔符字串，'tail' 是
     在根後的所有內容。這些項目中的任何一個都可能是空字串。在所有情況下
     ，‘drive + root + tail’ 將與 'path' 相同。

     在 POSIX 系統上，'drive' 始終為空。'root' 可能為空（如果 'path' 是
     相對路徑），一個斜線（如果 'path' 是絕對路徑），或者兩個斜線（根據
     IEEE Std 1003.1-2017; 4.13 Pathname Resolution(6) 的實作定義）。例
     如：

          >>> splitroot('/home/sam')
          ('', '/', 'home/sam')
          >>> splitroot('//home/sam')
          ('', '//', 'home/sam')
          >>> splitroot('///home/sam')
          ('', '/', '//home/sam')

     在 Windows 上，'drive' 可能為空、驅動機名稱、UNC 共享或設備名稱。
     'root' 可能為空，斜線或反斜線。例如：

          >>> splitroot('C:/Users/Sam')
          ('C:', '/', 'Users/Sam')
          >>> splitroot('//Server/Share/Users/Sam')
          ('//Server/Share', '/', 'Users/Sam')

     在 3.12 版被加入.

 -- 函式: os.path.splitext (path)

     將路徑名 'path' 拆分為一對 ‘(root, ext)’，使得 ‘root + ext ==
     path’，且副檔名 'ext' 為空或以點開頭且最多包含一個點 (period)。

     如果路徑不包含副檔名，則 'ext' 將為 ‘''’：

          >>> splitext('bar')
          ('bar', '')

     如果路徑包含副檔名，則 'ext' 將設置為該副檔名，包括前導的點。請注意
     ，前面的點將被忽略：

          >>> splitext('foo.bar.exe')
          ('foo.bar', '.exe')
          >>> splitext('/foo/bar.exe')
          ('/foo/bar', '.exe')

     路徑的最後一個部份的前導點被認為是根的一部分：

          >>> splitext('.cshrc')
          ('.cshrc', '')
          >>> splitext('/foo/....jpg')
          ('/foo/....jpg', '')

     在 3.6 版的變更: 接受一個 *note path-like object: ac2.。

 -- 資料: os.path.supports_unicode_filenames

     如果可以使用任意的 Unicode 字串作為檔案名（在檔案系統所施加的限制範
     圍內），則回傳 ‘True’。

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/genericpath.py

   (2) https://github.com/python/cpython/tree/3.13/Lib/posixpath.py

   (3) https://github.com/python/cpython/tree/3.13/Lib/ntpath.py

   (4) https://learn.microsoft.com/windows/dev-drive/

   (5) 
https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html#tag_04_13

   (6) 
https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap04.html#tag_04_13


File: python.info,  Node: fileinput --- 逐列疊代多個輸入串流,  Next: stat --- 直譯 stat 的結果,  Prev: os path --- 常見的路徑名操作,  Up: 檔案與目錄存取

5.11.3 ‘fileinput’ -- 逐列疊代多個輸入串流
------------------------------------------

'原始碼：'Lib/fileinput.py(1)

__________________________________________________________________

This module implements a helper class and functions to quickly write a
loop over standard input or a list of files.  If you just want to read
or write one file see *note open(): 4c0.

The typical use is:

     import fileinput
     for line in fileinput.input(encoding="utf-8"):
         process(line)

This iterates over the lines of all files listed in ‘sys.argv[1:]’,
defaulting to ‘sys.stdin’ if the list is empty.  If a filename is ‘'-'’,
it is also replaced by ‘sys.stdin’ and the optional arguments 'mode' and
'openhook' are ignored.  To specify an alternative list of filenames,
pass it as the first argument to *note input(): 7a3.  A single file name
is also allowed.

All files are opened in text mode by default, but you can override this
by specifying the 'mode' parameter in the call to *note input(): 7a3. or
*note FileInput: 6db.  If an I/O error occurs during opening or reading
a file, *note OSError: 350. is raised.

在 3.3 版的變更: *note IOError: ff5. used to be raised; it is now an
alias of *note OSError: 350.

If ‘sys.stdin’ is used more than once, the second and further use will
return no lines, except perhaps for interactive use, or if it has been
explicitly reset (e.g.  using ‘sys.stdin.seek(0)’).

Empty files are opened and immediately closed; the only time their
presence in the list of filenames is noticeable at all is when the last
file opened is empty.

Lines are returned with any newlines intact, which means that the last
line in a file may not have one.

You can control how files are opened by providing an opening hook via
the 'openhook' parameter to *note fileinput.input(): 7a3. or *note
FileInput(): 6db.  The hook must be a function that takes two arguments,
'filename' and 'mode', and returns an accordingly opened file-like
object.  If 'encoding' and/or 'errors' are specified, they will be
passed to the hook as additional keyword arguments.  This module
provides a *note hook_compressed(): 7a4. to support compressed files.

The following function is the primary interface of this module:

 -- 函式: fileinput.input (files=None, inplace=False, backup='', *,
          mode='r', openhook=None, encoding=None, errors=None)

     Create an instance of the *note FileInput: 6db. class.  The
     instance will be used as global state for the functions of this
     module, and is also returned to use during iteration.  The
     parameters to this function will be passed along to the constructor
     of the *note FileInput: 6db. class.

     The *note FileInput: 6db. instance can be used as a context manager
     in the *note with: 577. statement.  In this example, 'input' is
     closed after the ‘with’ statement is exited, even if an exception
     occurs:

          with fileinput.input(files=('spam.txt', 'eggs.txt'), encoding="utf-8") as f:
              for line in f:
                  process(line)

     在 3.2 版的變更: Can be used as a context manager.

     在 3.8 版的變更: The keyword parameters 'mode' and 'openhook' are
     now keyword-only.

     在 3.10 版的變更: The keyword-only parameter 'encoding' and
     'errors' are added.

The following functions use the global state created by *note
fileinput.input(): 7a3.; if there is no active state, *note
RuntimeError: 179. is raised.

 -- 函式: fileinput.filename ()

     Return the name of the file currently being read.  Before the first
     line has been read, returns ‘None’.

 -- 函式: fileinput.fileno ()

     Return the integer "file descriptor" for the current file.  When no
     file is opened (before the first line and between files), returns
     ‘-1’.

 -- 函式: fileinput.lineno ()

     Return the cumulative line number of the line that has just been
     read.  Before the first line has been read, returns ‘0’.  After the
     last line of the last file has been read, returns the line number
     of that line.

 -- 函式: fileinput.filelineno ()

     Return the line number in the current file.  Before the first line
     has been read, returns ‘0’.  After the last line of the last file
     has been read, returns the line number of that line within the
     file.

 -- 函式: fileinput.isfirstline ()

     Return ‘True’ if the line just read is the first line of its file,
     otherwise return ‘False’.

 -- 函式: fileinput.isstdin ()

     Return ‘True’ if the last line was read from ‘sys.stdin’, otherwise
     return ‘False’.

 -- 函式: fileinput.nextfile ()

     Close the current file so that the next iteration will read the
     first line from the next file (if any); lines not read from the
     file will not count towards the cumulative line count.  The
     filename is not changed until after the first line of the next file
     has been read.  Before the first line has been read, this function
     has no effect; it cannot be used to skip the first file.  After the
     last line of the last file has been read, this function has no
     effect.

 -- 函式: fileinput.close ()

     Close the sequence.

The class which implements the sequence behavior provided by the module
is available for subclassing as well:

 -- 類別: fileinput.FileInput (files=None, inplace=False, backup='', *,
          mode='r', openhook=None, encoding=None, errors=None)

     Class *note FileInput: 6db. is the implementation; its methods
     *note filename(): 26bb, *note fileno(): 139b, *note lineno(): 26bc,
     *note filelineno(): 26bd, *note isfirstline(): 26be, *note
     isstdin(): 26bf, *note nextfile(): 26c0. and *note close(): 26c1.
     correspond to the functions of the same name in the module.  In
     addition it is *note iterable: 11bf. and has a *note readline():
     1bc0. method which returns the next input line.  The sequence must
     be accessed in strictly sequential order; random access and *note
     readline(): 1bc0. cannot be mixed.

     With 'mode' you can specify which file mode will be passed to *note
     open(): 4c0.  It must be one of ‘'r'’ and ‘'rb'’.

     The 'openhook', when given, must be a function that takes two
     arguments, 'filename' and 'mode', and returns an accordingly opened
     file-like object.  You cannot use 'inplace' and 'openhook'
     together.

     You can specify 'encoding' and 'errors' that is passed to *note
     open(): 4c0. or 'openhook'.

     A *note FileInput: 6db. instance can be used as a context manager
     in the *note with: 577. statement.  In this example, 'input' is
     closed after the ‘with’ statement is exited, even if an exception
     occurs:

          with FileInput(files=('spam.txt', 'eggs.txt')) as input:
              process(input)

     在 3.2 版的變更: Can be used as a context manager.

     在 3.8 版的變更: The keyword parameter 'mode' and 'openhook' are
     now keyword-only.

     在 3.10 版的變更: The keyword-only parameter 'encoding' and
     'errors' are added.

     在 3.11 版的變更: The ‘'rU'’ and ‘'U'’ modes and the
     ‘__getitem__()’ method have been removed.

'Optional in-place filtering:' if the keyword argument ‘inplace=True’ is
passed to *note fileinput.input(): 7a3. or to the *note FileInput: 6db.
constructor, the file is moved to a backup file and standard output is
directed to the input file (if a file of the same name as the backup
file already exists, it will be replaced silently).  This makes it
possible to write a filter that rewrites its input file in place.  If
the 'backup' parameter is given (typically as ‘backup='.<some
extension>'’), it specifies the extension for the backup file, and the
backup file remains around; by default, the extension is ‘'.bak'’ and it
is deleted when the output file is closed.  In-place filtering is
disabled when standard input is read.

The two following opening hooks are provided by this module:

 -- 函式: fileinput.hook_compressed (filename, mode, *, encoding=None,
          errors=None)

     Transparently opens files compressed with gzip and bzip2
     (recognized by the extensions ‘'.gz'’ and ‘'.bz2'’) using the *note
     gzip: 5d. and *note bz2: f. modules.  If the filename extension is
     not ‘'.gz'’ or ‘'.bz2'’, the file is opened normally (ie, using
     *note open(): 4c0. without any decompression).

     The 'encoding' and 'errors' values are passed to *note
     io.TextIOWrapper: 75f. for compressed files and open for normal
     files.

     Usage example: ‘fi =
     fileinput.FileInput(openhook=fileinput.hook_compressed,
     encoding="utf-8")’

     在 3.10 版的變更: The keyword-only parameter 'encoding' and
     'errors' are added.

 -- 函式: fileinput.hook_encoded (encoding, errors=None)

     Returns a hook which opens each file with *note open(): 4c0, using
     the given 'encoding' and 'errors' to read the file.

     Usage example: ‘fi =
     fileinput.FileInput(openhook=fileinput.hook_encoded("utf-8",
     "surrogateescape"))’

     在 3.6 版的變更: 新增可選參數 'errors'。

     在 3.10 版之後被棄用: This function is deprecated since *note
     fileinput.input(): 7a3. and *note FileInput: 6db. now have
     'encoding' and 'errors' parameters.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/fileinput.py


File: python.info,  Node: stat --- 直譯 stat 的結果,  Next: filecmp --- 檔案與目錄比較,  Prev: fileinput --- 逐列疊代多個輸入串流,  Up: 檔案與目錄存取

5.11.4 ‘stat’ -- 直譯 ‘stat()’ 的結果
-------------------------------------

'原始碼：'Lib/stat.py(1)

__________________________________________________________________

The *note stat: bc. module defines constants and functions for
interpreting the results of *note os.stat(): 448, *note os.fstat(): d32.
and *note os.lstat(): 449. (if they exist).  For complete details about
the ‘stat()’, ‘fstat()’ and ‘lstat()’ calls, consult the documentation
for your system.

在 3.4 版的變更: The stat module is backed by a C implementation.

The *note stat: bc. module defines the following functions to test for
specific file types:

 -- 函式: stat.S_ISDIR (mode)

     Return non-zero if the mode is from a directory.

 -- 函式: stat.S_ISCHR (mode)

     Return non-zero if the mode is from a character special device
     file.

 -- 函式: stat.S_ISBLK (mode)

     Return non-zero if the mode is from a block special device file.

 -- 函式: stat.S_ISREG (mode)

     Return non-zero if the mode is from a regular file.

 -- 函式: stat.S_ISFIFO (mode)

     Return non-zero if the mode is from a FIFO (named pipe).

 -- 函式: stat.S_ISLNK (mode)

     Return non-zero if the mode is from a symbolic link.

 -- 函式: stat.S_ISSOCK (mode)

     Return non-zero if the mode is from a socket.

 -- 函式: stat.S_ISDOOR (mode)

     Return non-zero if the mode is from a door.

     在 3.4 版被加入.

 -- 函式: stat.S_ISPORT (mode)

     Return non-zero if the mode is from an event port.

     在 3.4 版被加入.

 -- 函式: stat.S_ISWHT (mode)

     Return non-zero if the mode is from a whiteout.

     在 3.4 版被加入.

Two additional functions are defined for more general manipulation of
the file's mode:

 -- 函式: stat.S_IMODE (mode)

     Return the portion of the file's mode that can be set by *note
     os.chmod(): 200.--that is, the file's permission bits, plus the
     sticky bit, set-group-id, and set-user-id bits (on systems that
     support them).

 -- 函式: stat.S_IFMT (mode)

     Return the portion of the file's mode that describes the file type
     (used by the ‘S_IS*()’ functions above).

Normally, you would use the ‘os.path.is*()’ functions for testing the
type of a file; the functions here are useful when you are doing
multiple tests of the same file and wish to avoid the overhead of the
‘stat()’ system call for each test.  These are also useful when checking
for information about a file that isn't handled by *note os.path: 92,
like the tests for block and character devices.

範例：

     import os, sys
     from stat import *

     def walktree(top, callback):
         '''recursively descend the directory tree rooted at top,
            calling the callback function for each regular file'''

         for f in os.listdir(top):
             pathname = os.path.join(top, f)
             mode = os.lstat(pathname).st_mode
             if S_ISDIR(mode):
                 # It's a directory, recurse into it
                 walktree(pathname, callback)
             elif S_ISREG(mode):
                 # It's a file, call the callback function
                 callback(pathname)
             else:
                 # Unknown file type, print a message
                 print('Skipping %s' % pathname)

     def visitfile(file):
         print('visiting', file)

     if __name__ == '__main__':
         walktree(sys.argv[1], visitfile)

An additional utility function is provided to convert a file's mode in a
human readable string:

 -- 函式: stat.filemode (mode)

     Convert a file's mode to a string of the form '-rwxrwxrwx'.

     在 3.3 版被加入.

     在 3.4 版的變更: The function supports *note S_IFDOOR: f5d, *note
     S_IFPORT: f5e. and *note S_IFWHT: f5f.

All the variables below are simply symbolic indexes into the 10-tuple
returned by *note os.stat(): 448, *note os.fstat(): d32. or *note
os.lstat(): 449.

 -- 資料: stat.ST_MODE

     Inode protection mode.

 -- 資料: stat.ST_INO

     Inode number.

 -- 資料: stat.ST_DEV

     Device inode resides on.

 -- 資料: stat.ST_NLINK

     Number of links to the inode.

 -- 資料: stat.ST_UID

     User id of the owner.

 -- 資料: stat.ST_GID

     Group id of the owner.

 -- 資料: stat.ST_SIZE

     Size in bytes of a plain file; amount of data waiting on some
     special files.

 -- 資料: stat.ST_ATIME

     Time of last access.

 -- 資料: stat.ST_MTIME

     Time of last modification.

 -- 資料: stat.ST_CTIME

     The "ctime" as reported by the operating system.  On some systems
     (like Unix) is the time of the last metadata change, and, on others
     (like Windows), is the creation time (see platform documentation
     for details).

The interpretation of "file size" changes according to the file type.
For plain files this is the size of the file in bytes.  For FIFOs and
sockets under most flavors of Unix (including Linux in particular), the
"size" is the number of bytes waiting to be read at the time of the call
to *note os.stat(): 448, *note os.fstat(): d32, or *note os.lstat():
449.; this can sometimes be useful, especially for polling one of these
special files after a non-blocking open.  The meaning of the size field
for other character and block devices varies more, depending on the
implementation of the underlying system call.

The variables below define the flags used in the *note ST_MODE: f5c.
field.

Use of the functions above is more portable than use of the first set of
flags:

 -- 資料: stat.S_IFSOCK

     Socket.

 -- 資料: stat.S_IFLNK

     Symbolic link.

 -- 資料: stat.S_IFREG

     Regular file.

 -- 資料: stat.S_IFBLK

     Block device.

 -- 資料: stat.S_IFDIR

     Directory.

 -- 資料: stat.S_IFCHR

     Character device.

 -- 資料: stat.S_IFIFO

     FIFO.

 -- 資料: stat.S_IFDOOR

     Door.

     在 3.4 版被加入.

 -- 資料: stat.S_IFPORT

     Event port.

     在 3.4 版被加入.

 -- 資料: stat.S_IFWHT

     Whiteout.

     在 3.4 版被加入.

     備註: *note S_IFDOOR: f5d, *note S_IFPORT: f5e. or *note S_IFWHT:
     f5f. are defined as 0 when the platform does not have support for
     the file types.

The following flags can also be used in the 'mode' argument of *note
os.chmod(): 200.:

 -- 資料: stat.S_ISUID

     Set UID bit.

 -- 資料: stat.S_ISGID

     Set-group-ID bit.  This bit has several special uses.  For a
     directory it indicates that BSD semantics is to be used for that
     directory: files created there inherit their group ID from the
     directory, not from the effective group ID of the creating process,
     and directories created there will also get the *note S_ISGID:
     26de. bit set.  For a file that does not have the group execution
     bit (*note S_IXGRP: 26df.) set, the set-group-ID bit indicates
     mandatory file/record locking (see also *note S_ENFMT: 26e0.).

 -- 資料: stat.S_ISVTX

     Sticky bit.  When this bit is set on a directory it means that a
     file in that directory can be renamed or deleted only by the owner
     of the file, by the owner of the directory, or by a privileged
     process.

 -- 資料: stat.S_IRWXU

     Mask for file owner permissions.

 -- 資料: stat.S_IRUSR

     Owner has read permission.

 -- 資料: stat.S_IWUSR

     Owner has write permission.

 -- 資料: stat.S_IXUSR

     Owner has execute permission.

 -- 資料: stat.S_IRWXG

     Mask for group permissions.

 -- 資料: stat.S_IRGRP

     Group has read permission.

 -- 資料: stat.S_IWGRP

     Group has write permission.

 -- 資料: stat.S_IXGRP

     Group has execute permission.

 -- 資料: stat.S_IRWXO

     Mask for permissions for others (not in group).

 -- 資料: stat.S_IROTH

     Others have read permission.

 -- 資料: stat.S_IWOTH

     Others have write permission.

 -- 資料: stat.S_IXOTH

     Others have execute permission.

 -- 資料: stat.S_ENFMT

     System V file locking enforcement.  This flag is shared with *note
     S_ISGID: 26de.: file/record locking is enforced on files that do
     not have the group execution bit (*note S_IXGRP: 26df.) set.

 -- 資料: stat.S_IREAD

     Unix V7 synonym for *note S_IRUSR: 26e3.

 -- 資料: stat.S_IWRITE

     Unix V7 synonym for *note S_IWUSR: 26e4.

 -- 資料: stat.S_IEXEC

     Unix V7 synonym for *note S_IXUSR: 26e5.

The following flags can be used in the 'flags' argument of *note
os.chflags(): 1086.:

 -- 資料: stat.UF_SETTABLE

     All user settable flags.

     在 3.13 版被加入.

 -- 資料: stat.UF_NODUMP

     Do not dump the file.

 -- 資料: stat.UF_IMMUTABLE

     The file may not be changed.

 -- 資料: stat.UF_APPEND

     The file may only be appended to.

 -- 資料: stat.UF_OPAQUE

     The directory is opaque when viewed through a union stack.

 -- 資料: stat.UF_NOUNLINK

     The file may not be renamed or deleted.

 -- 資料: stat.UF_COMPRESSED

     The file is stored compressed (macOS 10.6+).

 -- 資料: stat.UF_TRACKED

     Used for handling document IDs (macOS)

     在 3.13 版被加入.

 -- 資料: stat.UF_DATAVAULT

     The file needs an entitlement for reading or writing (macOS 10.13+)

     在 3.13 版被加入.

 -- 資料: stat.UF_HIDDEN

     The file should not be displayed in a GUI (macOS 10.5+).

 -- 資料: stat.SF_SETTABLE

     All super-user changeable flags

     在 3.13 版被加入.

 -- 資料: stat.SF_SUPPORTED

     All super-user supported flags

     *note Availability: 1c56.: macOS

     在 3.13 版被加入.

 -- 資料: stat.SF_SYNTHETIC

     All super-user read-only synthetic flags

     *note Availability: 1c56.: macOS

     在 3.13 版被加入.

 -- 資料: stat.SF_ARCHIVED

     The file may be archived.

 -- 資料: stat.SF_IMMUTABLE

     The file may not be changed.

 -- 資料: stat.SF_APPEND

     The file may only be appended to.

 -- 資料: stat.SF_RESTRICTED

     The file needs an entitlement to write to (macOS 10.13+)

     在 3.13 版被加入.

 -- 資料: stat.SF_NOUNLINK

     The file may not be renamed or deleted.

 -- 資料: stat.SF_SNAPSHOT

     The file is a snapshot file.

 -- 資料: stat.SF_FIRMLINK

     The file is a firmlink (macOS 10.15+)

     在 3.13 版被加入.

 -- 資料: stat.SF_DATALESS

     The file is a dataless object (macOS 10.15+)

     在 3.13 版被加入.

See the *BSD or macOS systems man page ‘chflags(2)(2)’ for more
information.

On Windows, the following file attribute constants are available for use
when testing bits in the ‘st_file_attributes’ member returned by *note
os.stat(): 448.  See the Windows API documentation(3) for more detail on
the meaning of these constants.

 -- 資料: stat.FILE_ATTRIBUTE_ARCHIVE
 -- 資料: stat.FILE_ATTRIBUTE_COMPRESSED
 -- 資料: stat.FILE_ATTRIBUTE_DEVICE
 -- 資料: stat.FILE_ATTRIBUTE_DIRECTORY
 -- 資料: stat.FILE_ATTRIBUTE_ENCRYPTED
 -- 資料: stat.FILE_ATTRIBUTE_HIDDEN
 -- 資料: stat.FILE_ATTRIBUTE_INTEGRITY_STREAM
 -- 資料: stat.FILE_ATTRIBUTE_NORMAL
 -- 資料: stat.FILE_ATTRIBUTE_NOT_CONTENT_INDEXED
 -- 資料: stat.FILE_ATTRIBUTE_NO_SCRUB_DATA
 -- 資料: stat.FILE_ATTRIBUTE_OFFLINE
 -- 資料: stat.FILE_ATTRIBUTE_READONLY
 -- 資料: stat.FILE_ATTRIBUTE_REPARSE_POINT
 -- 資料: stat.FILE_ATTRIBUTE_SPARSE_FILE
 -- 資料: stat.FILE_ATTRIBUTE_SYSTEM
 -- 資料: stat.FILE_ATTRIBUTE_TEMPORARY
 -- 資料: stat.FILE_ATTRIBUTE_VIRTUAL

     在 3.5 版被加入.

On Windows, the following constants are available for comparing against
the ‘st_reparse_tag’ member returned by *note os.lstat(): 449.  These
are well-known constants, but are not an exhaustive list.

 -- 資料: stat.IO_REPARSE_TAG_SYMLINK
 -- 資料: stat.IO_REPARSE_TAG_MOUNT_POINT
 -- 資料: stat.IO_REPARSE_TAG_APPEXECLINK

     在 3.8 版被加入.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/stat.py

   (2) https://manpages.debian.org/chflags(2)

   (3) 
https://msdn.microsoft.com/en-us/library/windows/desktop/gg258117.aspx


File: python.info,  Node: filecmp --- 檔案與目錄比較,  Next: tempfile --- 生成臨時檔案和目錄,  Prev: stat --- 直譯 stat 的結果,  Up: 檔案與目錄存取

5.11.5 ‘filecmp’ -- 檔案與目錄比較
----------------------------------

'原始碼：'Lib/filecmp.py(1)

__________________________________________________________________

The *note filecmp: 50. module defines functions to compare files and
directories, with various optional time/correctness trade-offs.  For
comparing files, see also the *note difflib: 2f. module.

The *note filecmp: 50. module defines the following functions:

 -- 函式: filecmp.cmp (f1, f2, shallow=True)

     Compare the files named 'f1' and 'f2', returning ‘True’ if they
     seem equal, ‘False’ otherwise.

     If 'shallow' is true and the *note os.stat(): 448. signatures (file
     type, size, and modification time) of both files are identical, the
     files are taken to be equal.

     Otherwise, the files are treated as different if their sizes or
     contents differ.

     Note that no external programs are called from this function,
     giving it portability and efficiency.

     This function uses a cache for past comparisons and the results,
     with cache entries invalidated if the *note os.stat(): 448.
     information for the file changes.  The entire cache may be cleared
     using *note clear_cache(): ee2.

 -- 函式: filecmp.cmpfiles (dir1, dir2, common, shallow=True)

     Compare the files in the two directories 'dir1' and 'dir2' whose
     names are given by 'common'.

     Returns three lists of file names: 'match', 'mismatch', 'errors'.
     'match' contains the list of files that match, 'mismatch' contains
     the names of those that don't, and 'errors' lists the names of
     files which could not be compared.  Files are listed in 'errors' if
     they don't exist in one of the directories, the user lacks
     permission to read them or if the comparison could not be done for
     some other reason.

     The 'shallow' parameter has the same meaning and default value as
     for *note filecmp.cmp(): 1554.

     For example, ‘cmpfiles('a', 'b', ['c', 'd/e'])’ will compare ‘a/c’
     with ‘b/c’ and ‘a/d/e’ with ‘b/d/e’.  ‘'c'’ and ‘'d/e'’ will each
     be in one of the three returned lists.

 -- 函式: filecmp.clear_cache ()

     Clear the filecmp cache.  This may be useful if a file is compared
     so quickly after it is modified that it is within the mtime
     resolution of the underlying filesystem.

     在 3.4 版被加入.

* Menu:

* The dircmp class::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/filecmp.py


File: python.info,  Node: The dircmp class,  Up: filecmp --- 檔案與目錄比較

5.11.5.1 The ‘dircmp’ class
...........................

 -- 類別: filecmp.dircmp (a, b, ignore=None, hide=None, *, shallow=True)

     Construct a new directory comparison object, to compare the
     directories 'a' and 'b'.  'ignore' is a list of names to ignore,
     and defaults to *note filecmp.DEFAULT_IGNORES: ee3.  'hide' is a
     list of names to hide, and defaults to ‘[os.curdir, os.pardir]’.

     The *note dircmp: ee4. class compares files by doing 'shallow'
     comparisons as described for *note filecmp.cmp(): 1554. by default
     using the 'shallow' parameter.

     在 3.13 版的變更: Added the 'shallow' parameter.

     The *note dircmp: ee4. class provides the following methods:

      -- 方法: report ()

          Print (to *note sys.stdout: a79.) a comparison between 'a' and
          'b'.

      -- 方法: report_partial_closure ()

          Print a comparison between 'a' and 'b' and common immediate
          subdirectories.

      -- 方法: report_full_closure ()

          Print a comparison between 'a' and 'b' and common
          subdirectories (recursively).

     The *note dircmp: ee4. class offers a number of interesting
     attributes that may be used to get various bits of information
     about the directory trees being compared.

     Note that via *note __getattr__(): 47a. hooks, all attributes are
     computed lazily, so there is no speed penalty if only those
     attributes which are lightweight to compute are used.

      -- 屬性: left

          The directory 'a'.

      -- 屬性: right

          The directory 'b'.

      -- 屬性: left_list

          Files and subdirectories in 'a', filtered by 'hide' and
          'ignore'.

      -- 屬性: right_list

          Files and subdirectories in 'b', filtered by 'hide' and
          'ignore'.

      -- 屬性: common

          Files and subdirectories in both 'a' and 'b'.

      -- 屬性: left_only

          Files and subdirectories only in 'a'.

      -- 屬性: right_only

          Files and subdirectories only in 'b'.

      -- 屬性: common_dirs

          Subdirectories in both 'a' and 'b'.

      -- 屬性: common_files

          Files in both 'a' and 'b'.

      -- 屬性: common_funny

          Names in both 'a' and 'b', such that the type differs between
          the directories, or names for which *note os.stat(): 448.
          reports an error.

      -- 屬性: same_files

          Files which are identical in both 'a' and 'b', using the
          class's file comparison operator.

      -- 屬性: diff_files

          Files which are in both 'a' and 'b', whose contents differ
          according to the class's file comparison operator.

      -- 屬性: funny_files

          Files which are in both 'a' and 'b', but could not be
          compared.

      -- 屬性: subdirs

          A dictionary mapping names in *note common_dirs: 2727. to
          *note dircmp: ee4. instances (or MyDirCmp instances if this
          instance is of type MyDirCmp, a subclass of *note dircmp:
          ee4.).

          在 3.10 版的變更: Previously entries were always *note dircmp:
          ee4. instances.  Now entries are the same type as 'self', if
          'self' is a subclass of *note dircmp: ee4.

 -- 屬性: filecmp.DEFAULT_IGNORES

     在 3.4 版被加入.

     List of directories ignored by *note dircmp: ee4. by default.

Here is a simplified example of using the ‘subdirs’ attribute to search
recursively through two directories to show common different files:

     >>> from filecmp import dircmp
     >>> def print_diff_files(dcmp):
     ...     for name in dcmp.diff_files:
     ...         print("diff_file %s found in %s and %s" % (name, dcmp.left,
     ...               dcmp.right))
     ...     for sub_dcmp in dcmp.subdirs.values():
     ...         print_diff_files(sub_dcmp)
     ...
     >>> dcmp = dircmp('dir1', 'dir2')
     >>> print_diff_files(dcmp)


File: python.info,  Node: tempfile --- 生成臨時檔案和目錄,  Next: glob --- Unix 風格的路徑名稱模式擴展,  Prev: filecmp --- 檔案與目錄比較,  Up: 檔案與目錄存取

5.11.6 ‘tempfile’ -- 生成臨時檔案和目錄
---------------------------------------

'原始碼：'Lib/tempfile.py(1)

__________________________________________________________________

該 module（模組）用於建立臨時檔案和目錄，它可以在所有有支援的平臺上使用
。*note TemporaryFile: 272f.、*note NamedTemporaryFile: 46d.、*note
TemporaryDirectory: 11cc. 和 *note SpooledTemporaryFile: 639. 是有自動清
除功能的高階介面，可作為*note 情境管理器 (context manager): 576. 使用。
*note mkstemp(): 2730. 和 *note mkdtemp(): 204. 是低階函式，使用完畢後需
手動清理。

所有可被使用者呼叫的函式和建構函式都帶有可以設定臨時檔案和臨時目錄的路徑
和名稱的引數。此 module 所使用的檔名為一個隨機字元組成的字串，這讓檔案可
以更安全地在共享的臨時目錄中被建立。為了維持向後相容性，引數的順序會稍微
奇怪，所以為了讓程式更容易被理解，建議使用關鍵字引數。

這個 module 定義了以下可供使用者呼叫的項目：

 -- 函式: tempfile.TemporaryFile (mode='w+b', buffering=-1,
          encoding=None, newline=None, suffix=None, prefix=None,
          dir=None, *, errors=None)

     回傳一個可當作臨時儲存區域的*note 類檔案物件: 246a.。建立該檔案使用
     了與 *note mkstemp(): 2730. 相同的安全規則。它將在關閉（包括當物件
     被垃圾回收 (garbage collect) 時的隱式關閉）後立即銷毀。在 Unix 下，
     該檔案所在的目錄可能根本不被建立、或者在建立檔案後立即就被刪除，其
     他平臺不支援此功能；你的程式不應依賴使用此功能建立的臨時檔案名稱，
     因為它在檔案系統中的名稱有可能是不可見的。

     生成的物件可以作為*note 情境管理器: 576.使用（參見 *note 範例:
     2731.）。完成情境或銷毀臨時檔案物件後，臨時檔案將從檔案系統中刪除。

     'mode' 參數預設為 ‘'w+b'’，所以建立的檔案不用關閉就可以讀取或寫入。
     因為用的是二進位制模式，所以無論存的是什麼資料，它在所有平臺上的行
     為都一致。'buffering'、'encoding'、'errors' 和 'newline' 的含義與
     *note open(): 4c0. 中的相同。

     參數 'dir'、'prefix' 和 'suffix' 的含義和預設值都與它們在 *note
     mkstemp(): 2730. 中的相同。

     在 POSIX 平臺上，回傳物件是真實的檔案物件。在其他平臺上，它是一個
     file-like object，它的 ‘file’ 屬性為底層的真實檔案物件。

     如果可用且可運作，則使用 *note os.O_TMPFILE: f16. 旗標（僅限於
     Linux，需要 3.11 版本以上的核心）。

     在不是 Posix 或 Cygwin 的平臺上，TemporaryFile 是
     NamedTemporaryFile 的別名。

     引發一個附帶引數 ‘fullpath’ 的 ‘tempfile.mkstemp’ *note 稽核事件:
     17bd.。

     在 3.5 版的變更: 如果可用，自此開始使用 *note os.O_TMPFILE: f16. 旗
     標。

     在 3.8 版的變更: 新增 'errors' 參數。

 -- 函式: tempfile.NamedTemporaryFile (mode='w+b', buffering=-1,
          encoding=None, newline=None, suffix=None, prefix=None,
          dir=None, delete=True, *, errors=None, delete_on_close=True)

     此函式的操作與 *note TemporaryFile(): 272f. 完全相同，但存在以下差
     異：

        * 此函式回傳一個保證在檔案系統中具有可見名稱的檔案。

        * 為了管理指定檔案，它使用 'delete' 和 'delete_on_close' 參數擴
          充 *note TemporaryFile(): 272f. 來指定是否以及如何自動刪除指定
          檔案。

     回傳的物件始終是一個*note 類檔案物件: 246a.，其 ‘file’ 屬性是底層的
     真實檔案物件。這個類檔案物件可以在 *note with: 577. 陳述式中使用，
     就像普通檔案一樣。臨時檔案的名稱可以從回傳的類檔案物件的
     :attr:!name' 屬性中取得。在 Unix 上則與 *note TemporaryFile():
     272f. 不同，目錄條目不會在檔案建立後立即被取消鏈接 (unlink)。

     如果 'delete' 為 true（預設值）並且 'delete_on_close' 為 true（預設
     值），則檔案在關閉後會立即被刪除。如果 'delete' 為 true 並且
     'delete_on_close' 為 false，則僅在情境管理器退出時刪除檔案，或者在
     *note 類檔案物件: 246a.完結時刪除檔案。在這種情況下，並不總是保證能
     成功刪除（請參閱 *note object.__del__(): 1e36.）。如果 'delete' 為
     false，則會忽略 'delete_on_close' 的值。

     因此，要在關閉檔案後使用臨時檔案的名稱重新打開檔案，請確保在關閉時
     不刪除檔案（將 'delete' 參數設定為 false），或者如果臨時檔案是以
     *note with: 577. 陳述式建立，要將 'delete_on_close' 參數設定為
     false。建議使用後者，因為它有助於在情境管理器退出時自動清理臨時檔案
     。

     在臨時檔案仍處於打開狀態時再次按其名稱打開它，其作用方式如下：

        * 在 POSIX 上，檔案始終可以再次打開。

        * 在 Windows 上，確保至少滿足以下條件之一：

             * 'delete' 為 false

             * 額外的 open 會共享刪除存取權限（例如，通過使用旗標
               ‘O_TEMPORARY’ 來呼叫 *note os.open(): d38.）

             * 'delete' 為 true 但 'delete_on_close' 為 false。請注意，
               在這種情況下不共享刪除存取權限的其他 open（例如透過內建的
               *note open(): 4c0. 建立）必須在退出情境管理器之前關閉，否
               則情境管理器上的 *note os.unlink(): 108e. 呼叫退出將失敗
               並出現 *note PermissionError: ce9.。

     在 Windows 上，如果 'delete_on_close' 為 false，並且檔案是在使用者
     缺乏刪除存取權限的目錄中建立的，則情境管理器退出時的 *note
     os.unlink(): 108e. 呼叫將失敗，並引發 *note PermissionError: ce9.。
     當 'delete_on_close' 為 true 時，不會發生這種情況，因為刪除存取權限
     是由 open 來要求的，如果未授予存取權限則會立即失敗。

     （僅）在 POSIX 上，因使用 SIGKILL 而被終止的行程無法自動刪除它建立
     的任何 NamedTemporaryFiles。

     引發一個附帶引數 ‘fullpath’ 的 ‘tempfile.mkstemp’ *note 稽核事件:
     17bd.。

     在 3.8 版的變更: 新增 'errors' 參數。

     在 3.12 版的變更: 新增 'delete_on_close' 參數。

 -- 類別: tempfile.SpooledTemporaryFile (max_size=0, mode='w+b',
          buffering=-1, encoding=None, newline=None, suffix=None,
          prefix=None, dir=None, *, errors=None)

     此類別執行的操作與 *note TemporaryFile(): 272f. 完全相同，但會將資
     料排存 (spool) 於在記憶體中，直到檔案大小超過 'max_size'，或檔案的
     *note fileno(): 2732. 方法被呼叫為止，此時資料會被寫入磁碟，並且之
     後的操作與 *note TemporaryFile(): 272f. 相同。

      -- 方法: rollover ()

          生成的檔案物件有一個額外的方法 ‘rollover()’，忽略檔案大小並立
          即將其寫入磁碟。

     回傳的物件是 file-like object，它的 ‘_file’ 屬性是 *note
     io.BytesIO: e46. 或 *note io.TextIOWrapper: 75f. 物件（取決於指定的
     是二進位制模式還是文字模式）或真實的檔案物件（取決於是否已呼叫
     *note rollover(): 2733.）。file-like object 可以像普通檔案一樣在
     *note with: 577. 陳述式中使用。

     在 3.3 版的變更: 現在，檔案的截斷方法 (truncate method) 可接受一個
     'size' 引數。

     在 3.8 版的變更: 新增 'errors' 參數。

     在 3.11 版的變更: 完全實作 *note io.BufferedIOBase: 63a. 和 *note
     io.TextIOBase: 63b. 抽象基底類別（取決於指定的是二進位還是文本
     'mode'）。

 -- 類別: tempfile.TemporaryDirectory (suffix=None, prefix=None,
          dir=None, ignore_cleanup_errors=False, *, delete=True)

     此類別會使用與 *note mkdtemp(): 204. 相同安全規則來建立一個臨時目錄
     。回傳物件可當作*note 情境管理器: 576.使用（參見*note 範例: 2731.）
     。在完成情境或銷毀臨時目錄物件時，新建立的臨時目錄及其所有內容會從
     檔案系統中被移除。

      -- 屬性: name

          可以從回傳物件的 ‘name’ 屬性中找到的臨時目錄名稱。當回傳的物件
          用作*note 情境管理器: 576.時，這個 ‘name’ 會作為 *note with:
          577. 陳述句中 ‘as’ 子句的目標（如果有 as 的話）。

      -- 方法: cleanup ()

          此目錄可透過呼叫 ‘cleanup()’ 方法來顯式地清理。如果
          'ignore_cleanup_errors' 為 true，則在顯式或隱式清理期間出現的
          未處理例外（例如在 Windows 上移除開啟的檔案而引發的 *note
          PermissionError: ce9.）將被忽略，並且剩餘的可移除條目會「儘可
          能」地被刪除。在其他情況下，錯誤將在任何情境清理發生時被引發（
          ‘cleanup()’ 呼叫、退出情境管理器、物件被作為垃圾回收或直譯器關
          閉等）。

     'delete' 參數可以停用在退出情境時對目錄樹的清理，雖然停用情境管理器
     在退出情境時所採取的操作似乎不常見，但它在除錯期間或當你需要基於其
     他邏輯的清理行為時會非常有用。

     引發一個附帶引數 ‘fullpath’ 的 ‘tempfile.mkdtemp’ *note 稽核事件:
     17bd.。

     在 3.2 版被加入.

     在 3.10 版的變更: 新增 'ignore_cleanup_errors' 參數。

     在 3.12 版的變更: 新增 'delete' 參數。

 -- 函式: tempfile.mkstemp (suffix=None, prefix=None, dir=None,
          text=False)

     盡可能以最安全的方式建立一個臨時檔案。假設所在平臺正確實作了 *note
     os.open(): d38. 的 *note os.O_EXCL: 2736. 旗標，則建立檔案時不會有
     race condition（競爭條件）的情況。該檔案只能由建立者讀寫，如果所在
     平臺用 permission bit（許可權位元）來表示檔案是否可執行，則沒有人有
     執行權。檔案描述器不會被子行程繼承。

     與 *note TemporaryFile(): 272f. 不同，*note mkstemp(): 2730. 使用者
     用完臨時檔案後需要自行將其刪除。

     如果 'suffix' 不是 ‘None’ 則檔名將以該後綴結尾，若為 ‘None’ 則沒有
     後綴。*note mkstemp(): 2730. 不會在檔名和後綴之間加點 (dot)，如果需
     要加一個點號，請將其放在 'suffix' 的開頭。

     如果 'prefix' 不是 ‘None’ 則檔名將以該字首開頭，若為 ‘None’ 則使用
     預設前綴。預設前綴是 *note gettempprefix(): 2737. 或 *note
     gettempprefixb(): 2738. 函式的回傳值（自動呼叫合適的函式）。

     如果 'dir' 不為 ‘None’ 則在指定的目錄建立檔案，若為 ‘None’ 則使用預
     設目錄。預設目錄是從一個相依於平臺的列表中選擇出來的，但是使用者可
     以設定 'TMPDIR'、'TEMP' 或 'TMP' 環境變數來設定目錄的位置。因此，不
     能保證生成的臨時檔案路徑是使用者友善的，比如透過 ‘os.popen()’ 將路
     徑傳遞給外部命令時仍需要加引號 (quoting)。

     如果 'suffix'、'prefix' 和 'dir' 中的任何一個不是 ‘None’，就要保證
     它們資料型別相同。如果它們是位元組串，則回傳名稱的型別就是位元組串
     而非字串。如果不想遵循預設行為但又想要回傳值是位元組串型別，請傳入
     ‘suffix=b''’。

     如果指定了 'text' 且為真值，檔案會以文字模式開啟。否則，檔案（預設
     ）以二進位制模式開啟。

     *note mkstemp(): 2730. 回傳一個 tuple，tuple 中，第一個元素是一個作
     業系統層級 (OS-level) 控制代碼，指向一個開啟的檔案（如同 *note
     os.open(): d38. 的回傳值），第二元素是該檔案的絕對路徑。

     引發一個附帶引數 ‘fullpath’ 的 ‘tempfile.mkstemp’ *note 稽核事件:
     17bd.。

     在 3.5 版的變更: 現在，'suffix'、'prefix' 和 'dir' 可以以位元組串型
     別按順序提供，以獲得位元組串型別的回傳值。在之前只允許使用字串。
     'suffix' 和 'prefix' 現在可以接受 ‘None’，並且預設為 ‘None’ 以使用
     合適的預設值。

     在 3.6 版的變更: 'dir' 參數現在可接受一個類路徑物件 (*note
     path-like object: ac2.)。

 -- 函式: tempfile.mkdtemp (suffix=None, prefix=None, dir=None)

     盡可能以最安全的方式建立一個臨時目錄，建立該目錄時不會有 race
     condition 的情況，該目錄只能由建立者讀取、寫入和搜尋。

     *note mkdtemp(): 204. 的使用者用完臨時目錄後需要自行將其刪除。

     引數 'prefix'、'suffix' 和 'dir' 的含義與它們在 *note mkstemp():
     2730. 中相同。

     *note mkdtemp(): 204. 回傳新目錄的絕對路徑名稱。

     引發一個附帶引數 ‘fullpath’ 的 ‘tempfile.mkdtemp’ *note 稽核事件:
     17bd.。

     在 3.5 版的變更: 現在，'suffix'、'prefix' 和 'dir' 可以以位元組串型
     別按順序提供，以獲得位元組串型別的回傳值。在之前只允許使用字串。
     'suffix' 和 'prefix' 現在可以接受 ‘None’，並且預設為 ‘None’ 以使用
     合適的預設值。

     在 3.6 版的變更: 'dir' 參數現在可接受一個類路徑物件 (*note
     path-like object: ac2.)。

     在 3.12 版的變更: *note mkdtemp(): 204. 現在都會回傳絕對路徑，即使
     'dir' 是相對路徑。

 -- 函式: tempfile.gettempdir ()

     回傳儲存臨時檔案的目錄名稱。這設定了此 module 所有函式 'dir' 引數的
     預設值。

     Python 搜尋標準目錄列表來找到呼叫者可以在其中建立檔案的目錄。這個列
     表是：

       1. ‘TMPDIR’ 環境變數指向的目錄。

       2. ‘TEMP’ 環境變數指向的目錄。

       3. ‘TMP’ 環境變數指向的目錄。

       4. 與平臺相關的位置：

             * 在 Windows 上，目錄依次為 ‘C:\TEMP’、‘C:\TMP’、‘\TEMP’ 和
               ‘\TMP’。

             * 在所有其他平臺上，目錄依次為 ‘/tmp’、‘/var/tmp’ 和
               ‘/usr/tmp’。

       5. 不得已時，使用當前工作目錄。

     搜尋的結果會被 cache（快取）起來，請見下面 *note tempdir: 17db. 的
     描述。

     在 3.10 版的變更: 回傳一個字串。在之前的版本中它會回傳任意 *note
     tempdir: 17db. 的值而不考慮它的型別，只要它不為 ‘None’。

 -- 函式: tempfile.gettempdirb ()

     與 *note gettempdir(): 17dc. 相同，但回傳值為位元組串型別。

     在 3.5 版被加入.

 -- 函式: tempfile.gettempprefix ()

     回傳用於建立臨時檔案的檔名前綴，它不包含目錄部分。

 -- 函式: tempfile.gettempprefixb ()

     與 *note gettempprefix(): 2737. 相同，但回傳值為位元組串型別。

     在 3.5 版被加入.

此 module 使用一個全域性變數來儲存由 *note gettempdir(): 17dc. 回傳的臨
時檔案使用的目錄路徑。它可被直接設定以覆蓋選擇過程，但不建議這樣做。此
module 中的所有函式都接受一個 'dir' 引數，它可被用於指定目錄。這是個推薦
的做法，它不會透過改變全域性 API 行為而對其他不預期此行為的程式造成影響
。

 -- 資料: tempfile.tempdir

     當被設為 ‘None’ 以外的值時，此變數會為此 module 所定義函式的引數
     'dir' 定義預設值，包括確定其型別為位元組串還是字串。它不可以為
     *note path-like object: ac2.。

     如果在呼叫除 *note gettempprefix(): 2737. 外的上述任何函式時
     ‘tempdir’ 為 ‘None’ (預設值) 則它會按照 *note gettempdir(): 17dc. 中
     所描述的演算法來初始化。

          備註: 請注意如果你將 ‘tempdir’ 設為位元組串值，會有一個麻煩的
          副作用：*note mkstemp(): 2730. 和 *note mkdtemp(): 204. 的全域
          性預設回傳型別會在沒有提供明顯字串型別的 ‘prefix’、‘suffix’ 或
          ‘dir’ 時被改為位元組串。請不要編寫預期此行為或依賴於此行為的程
          式。這個奇怪的行為是為了維持與以往實作版本的相容性。

* Menu:

* 範例: 範例<7>.
* 已棄用的函式和變數::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/tempfile.py


File: python.info,  Node: 範例<7>,  Next: 已棄用的函式和變數,  Up: tempfile --- 生成臨時檔案和目錄

5.11.6.1 範例
.............

以下是 *note tempfile: c9. module 的一些常見用法範例：

     >>> import tempfile

     # create a temporary file and write some data to it
     >>> fp = tempfile.TemporaryFile()
     >>> fp.write(b'Hello world!')
     # read data from file
     >>> fp.seek(0)
     >>> fp.read()
     b'Hello world!'
     # close the file, it will be removed
     >>> fp.close()

     # create a temporary file using a context manager
     >>> with tempfile.TemporaryFile() as fp:
     ...     fp.write(b'Hello world!')
     ...     fp.seek(0)
     ...     fp.read()
     b'Hello world!'
     >>>
     # file is now closed and removed

     # create a temporary file using a context manager
     # close the file, use the name to open the file again
     >>> with tempfile.NamedTemporaryFile(delete_on_close=False) as fp:
     ...     fp.write(b'Hello world!')
     ...     fp.close()
     ... # the file is closed, but not removed
     ... # open the file again by using its name
     ...     with open(fp.name, mode='rb') as f:
     ...         f.read()
     b'Hello world!'
     >>>
     # file is now removed

     # create a temporary directory using the context manager
     >>> with tempfile.TemporaryDirectory() as tmpdirname:
     ...     print('created temporary directory', tmpdirname)
     >>>
     # directory and contents have been removed


File: python.info,  Node: 已棄用的函式和變數,  Prev: 範例<7>,  Up: tempfile --- 生成臨時檔案和目錄

5.11.6.2 已棄用的函式和變數
...........................

在過去，建立臨時檔案首先使用 *note mktemp(): 1790. 函式生成一個檔名，然
後使用該檔名建立檔案。不幸的是這並不安全的，因為在呼叫 *note mktemp():
1790. 與隨後嘗試建立檔案之間的時間裡，其他程式可能會使用該名稱建立檔案。
解決方案是將兩個步驟結合起來，並立即建立檔案。這個方案目前被 *note
mkstemp(): 2730. 和上述其他函式所採用。

 -- 函式: tempfile.mktemp (suffix='', prefix='tmp', dir=None)

     在 2.3 版之後被棄用: 使用 *note mkstemp(): 2730. 代替。

     回傳一個在呼叫本方法時不存在檔案的絕對路徑。引數 'prefix'、'suffix'
     和 'dir' 與 *note mkstemp(): 2730. 中所用的類似，除了在於不支援位元
     組串型別的檔名且不支援 ‘suffix=None’ 和 ‘prefix=None’。

          警告: 使用此功能可能會在程式中引入安全漏洞。當你開始使用本方法
          回傳的檔案執行任何操作時，可能有人已經捷足先登了。*note
          mktemp(): 1790. 的功能可以很輕鬆地用帶有 ‘delete=False’ 參數的
          *note NamedTemporaryFile(): 46d. 代替：

               >>> f = NamedTemporaryFile(delete=False)
               >>> f.name
               '/tmp/tmptjujjt'
               >>> f.write(b"Hello World!\n")
               13
               >>> f.close()
               >>> os.unlink(f.name)
               >>> os.path.exists(f.name)
               False


File: python.info,  Node: glob --- Unix 風格的路徑名稱模式擴展,  Next: fnmatch --- Unix 檔案名稱模式比對,  Prev: tempfile --- 生成臨時檔案和目錄,  Up: 檔案與目錄存取

5.11.7 ‘glob’ -- Unix 風格的路徑名稱模式擴展
--------------------------------------------

'原始碼：'Lib/glob.py(1)

__________________________________________________________________

*note glob: 5a. 模組根據 Unix shell 使用的規則查找與指定模式匹配的所有路
徑名稱，結果以任意順序回傳。沒有波浪號 (tilde) 擴展，但是 ‘*’、‘?’ 和用
‘[]’ 表示的字元範圍將被正確匹配。這是透過同時使用 *note os.scandir():
a02. 和 *note fnmatch.fnmatch(): 17a2. 函式來完成的，而沒有實際調用
subshell。

請注意，以點 (‘.’) 開頭的檔案只能與同樣以點開頭的模式匹配，這與 *note
fnmatch.fnmatch(): 17a2. 或 *note pathlib.Path.glob(): 212. 不同。（對於
波浪號和 shell 變數擴展，請使用 *note os.path.expanduser(): 9b8. 和
*note os.path.expandvars(): 1347.。）

對於文本 (literal) 匹配，將元字元 (meta-character) 括在方括號中。例如，
‘'[?]'’ 會匹配 ‘'?'’ 字元。

The *note glob: 5a. module defines the following functions:

 -- 函式: glob.glob (pathname, *, root_dir=None, dir_fd=None,
          recursive=False, include_hidden=False)

     回傳與 'pathname' 匹配、可能為空的路徑名稱 list，它必須是包含路徑規
     範的字串。 'pathname' 可以是絕對的（如
     ‘/usr/src/Python-1.5/Makefile’）或相對的（如 ‘../../Tools/*/*.gif’）
     ，並且可以包含 shell 樣式的通用字元 (wildcard)。已損壞的符號連接也
     會（如同在 shell）被包含在結果中。結果是否排序取決於檔案系統 (file
     system)。如果在呼叫此函式期間刪除或新增滿足條件的檔案，則結果不一定
     會包含該檔案的路徑名稱。

     如果 'root_dir' 不是 ‘None’，它應該是一個指定搜索根目錄的 *note
     path-like object: ac2.。它在呼叫它之前更改當前目錄的影響與 *note
     glob(): 5a. 相同。如果 'pathname' 是相對的，結果將包含相對於
     'root_dir' 的路徑。

     此函式可以支援以 'dir_fd' 參數使用*note 相對目錄描述器的路徑:
     1083.。

     如果 'recursive' 為真，模式 "‘**’" 將匹配任何檔案、零個或多個目錄、
     子目錄和目錄的符號連結。如果模式後面有 *note os.sep: 610. 或 *note
     os.altsep: 611. 那麼檔案將不會被匹配。

     如果 'include_hidden' 為真，"‘**’" 模式將匹配被隱藏的目錄。

     引發一個附帶引數 ‘pathname’、‘recursive’ 的*note 稽核事件: 17bd.
     ‘glob.glob’。

     引發一個附帶引數 ‘pathname’、‘recursive’、‘root_dir’、‘dir_fd’ 的
     *note 稽核事件: 17bd. ‘glob.glob/2’。

          備註: 在大型目錄樹中使用 "‘**’" 模式可能會消耗過多的時間。

          備註: This function may return duplicate path names if
          'pathname' contains multiple "‘**’" patterns and 'recursive'
          is true.

     在 3.5 版的變更: 支援以 "‘**’" 使用遞迴 glob。

     在 3.10 版的變更: 新增 'root_dir' 與 'dir_fd' 參數。

     在 3.11 版的變更: 新增 'include_hidden' 參數。

 -- 函式: glob.iglob (pathname, *, root_dir=None, dir_fd=None,
          recursive=False, include_hidden=False)

     回傳一個會產生與 *note glob(): 5a. 相同的值的 *note iterator: 192.
     ，而不是同時存儲全部的值。

     引發一個附帶引數 ‘pathname’、‘recursive’ 的*note 稽核事件: 17bd.
     ‘glob.glob’。

     引發一個附帶引數 ‘pathname’、‘recursive’、‘root_dir’、‘dir_fd’ 的
     *note 稽核事件: 17bd. ‘glob.glob/2’。

          備註: This function may return duplicate path names if
          'pathname' contains multiple "‘**’" patterns and 'recursive'
          is true.

     在 3.5 版的變更: 支援以 "‘**’" 使用遞迴 glob。

     在 3.10 版的變更: 新增 'root_dir' 與 'dir_fd' 參數。

     在 3.11 版的變更: 新增 'include_hidden' 參數。

 -- 函式: glob.escape (pathname)

     跳脫 (escape) 所有特殊字元（‘'?'’、‘'*'’ 和 ‘'['’）。如果你想匹配其
     中可能包含特殊字元的任意文本字串，這將會很有用。驅動器 (drive)/UNC
     共享點 (sharepoints) 中的特殊字元不會被跳脫，例如在 Windows 上，
     ‘escape('//?/c:/Quo vadis?.txt')’ 會回傳 ‘'//?/c:/Quo
     vadis[?].txt'’。

     在 3.4 版被加入.

 -- 函式: glob.translate (pathname, *, recursive=False,
          include_hidden=False, seps=None)

     Convert the given path specification to a regular expression for
     use with *note re.match(): 11c5.  The path specification can
     contain shell-style wildcards.

     For example:

          >>> import glob, re
          >>>
          >>> regex = glob.translate('**/*.txt', recursive=True, include_hidden=True)
          >>> regex
          '(?s:(?:.+/)?[^/]*\\.txt)\\Z'
          >>> reobj = re.compile(regex)
          >>> reobj.match('foo/bar/baz.txt')
          <re.Match object; span=(0, 15), match='foo/bar/baz.txt'>

     Path separators and segments are meaningful to this function,
     unlike *note fnmatch.translate(): 194c.  By default wildcards do
     not match path separators, and ‘*’ pattern segments match precisely
     one path segment.

     If 'recursive' is true, the pattern segment "‘**’" will match any
     number of path segments.

     If 'include_hidden' is true, wildcards can match path segments that
     start with a dot (‘.’).

     A sequence of path separators may be supplied to the 'seps'
     argument.  If not given, *note os.sep: 610. and *note altsep: 611.
     (if available) are used.

     也參考
     ......

     *note pathlib.PurePath.full_match(): 210. and *note
     pathlib.Path.glob(): 212. methods, which call this function to
     implement pattern matching and globbing.

     在 3.13 版被加入.

* Menu:

* Examples::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/glob.py


File: python.info,  Node: Examples,  Up: glob --- Unix 風格的路徑名稱模式擴展

5.11.7.1 Examples
.................

Consider a directory containing the following files: ‘1.gif’, ‘2.txt’,
‘card.gif’ and a subdirectory ‘sub’ which contains only the file
‘3.txt’.  *note glob(): 5a. will produce the following results.  Notice
how any leading components of the path are preserved.

     >>> import glob
     >>> glob.glob('./[0-9].*')
     ['./1.gif', './2.txt']
     >>> glob.glob('*.gif')
     ['1.gif', 'card.gif']
     >>> glob.glob('?.gif')
     ['1.gif']
     >>> glob.glob('**/*.txt', recursive=True)
     ['2.txt', 'sub/3.txt']
     >>> glob.glob('./**/', recursive=True)
     ['./', './sub/']

如果目錄包含以 ‘.’ 開頭的檔案，則預設情況下不會去匹配到它們。例如，一個
包含 ‘card.gif’ 和 ‘.card.gif’ 的目錄：

     >>> import glob
     >>> glob.glob('*.gif')
     ['card.gif']
     >>> glob.glob('.c*')
     ['.card.gif']

也參考
......

The *note fnmatch: 52. module offers shell-style filename (not path)
expansion.

也參考
......

*note pathlib: 93. 模組提供高階路徑物件。


File: python.info,  Node: fnmatch --- Unix 檔案名稱模式比對,  Next: linecache --- 隨機存取文字列,  Prev: glob --- Unix 風格的路徑名稱模式擴展,  Up: 檔案與目錄存取

5.11.8 ‘fnmatch’ -- Unix 檔案名稱模式比對
-----------------------------------------

'原始碼：'Lib/fnmatch.py(1)

__________________________________________________________________

This module provides support for Unix shell-style wildcards, which are
'not' the same as regular expressions (which are documented in the *note
re: a7. module).  The special characters used in shell-style wildcards
are:

Pattern          含義
                 
----------------------------------------------------------
                 
‘*’              matches everything
                 
                 
‘?’              matches any single character
                 
                 
‘[seq]’          matches any character in 'seq'
                 
                 
‘[!seq]’         matches any character not in 'seq'
                 

For a literal match, wrap the meta-characters in brackets.  For example,
‘'[?]'’ matches the character ‘'?'’.

Note that the filename separator (‘'/'’ on Unix) is 'not' special to
this module.  See module *note glob: 5a. for pathname expansion (*note
glob: 5a. uses *note filter(): 17a4. to match pathname segments).
Similarly, filenames starting with a period are not special for this
module, and are matched by the ‘*’ and ‘?’ patterns.

Also note that *note functools.lru_cache(): 993. with the 'maxsize' of
32768 is used to cache the compiled regex patterns in the following
functions: *note fnmatch(): 52, *note fnmatchcase(): 17a3, *note
filter(): 17a4.

 -- 函式: fnmatch.fnmatch (name, pat)

     Test whether the filename string 'name' matches the pattern string
     'pat', returning ‘True’ or ‘False’.  Both parameters are
     case-normalized using *note os.path.normcase(): 26b6.  *note
     fnmatchcase(): 17a3. can be used to perform a case-sensitive
     comparison, regardless of whether that's standard for the operating
     system.

     This example will print all file names in the current directory
     with the extension ‘.txt’:

          import fnmatch
          import os

          for file in os.listdir('.'):
              if fnmatch.fnmatch(file, '*.txt'):
                  print(file)

 -- 函式: fnmatch.fnmatchcase (name, pat)

     Test whether the filename string 'name' matches the pattern string
     'pat', returning ‘True’ or ‘False’; the comparison is
     case-sensitive and does not apply *note os.path.normcase(): 26b6.

 -- 函式: fnmatch.filter (names, pat)

     Construct a list from those elements of the *note iterable: 11bf.
     'names' that match pattern 'pat'.  It is the same as ‘[n for n in
     names if fnmatch(n, pat)]’, but implemented more efficiently.

 -- 函式: fnmatch.translate (pat)

     Return the shell-style pattern 'pat' converted to a regular
     expression for using with *note re.match(): 11c5.

     範例：

          >>> import fnmatch, re
          >>>
          >>> regex = fnmatch.translate('*.txt')
          >>> regex
          '(?s:.*\\.txt)\\Z'
          >>> reobj = re.compile(regex)
          >>> reobj.match('foobar.txt')
          <re.Match object; span=(0, 10), match='foobar.txt'>

也參考
......

*note glob: 5a. 模組

     Unix shell-style path expansion.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/fnmatch.py


File: python.info,  Node: linecache --- 隨機存取文字列,  Next: shutil — 高階檔案操作,  Prev: fnmatch --- Unix 檔案名稱模式比對,  Up: 檔案與目錄存取

5.11.9 ‘linecache’ -- 隨機存取文字列
------------------------------------

'原始碼：'Lib/linecache.py(1)

__________________________________________________________________

The *note linecache: 79. module allows one to get any line from a Python
source file, while attempting to optimize internally, using a cache, the
common case where many lines are read from a single file.  This is used
by the *note traceback: e7. module to retrieve source lines for
inclusion in the formatted traceback.

The *note tokenize.open(): 2743. function is used to open files.  This
function uses *note tokenize.detect_encoding(): 2744. to get the
encoding of the file; in the absence of an encoding token, the file
encoding defaults to UTF-8.

The *note linecache: 79. module defines the following functions:

 -- 函式: linecache.getline (filename, lineno, module_globals=None)

     Get line 'lineno' from file named 'filename'.  This function will
     never raise an exception -- it will return ‘''’ on errors (the
     terminating newline character will be included for lines that are
     found).

     If a file named 'filename' is not found, the function first checks
     for a PEP 302(2) ‘__loader__’ in 'module_globals'.  If there is
     such a loader and it defines a ‘get_source’ method, then that
     determines the source lines (if ‘get_source()’ returns ‘None’, then
     ‘''’ is returned).  Finally, if 'filename' is a relative filename,
     it is looked up relative to the entries in the module search path,
     ‘sys.path’.

 -- 函式: linecache.clearcache ()

     Clear the cache.  Use this function if you no longer need lines
     from files previously read using *note getline(): dc9.

 -- 函式: linecache.checkcache (filename=None)

     Check the cache for validity.  Use this function if files in the
     cache may have changed on disk, and you require the updated
     version.  If 'filename' is omitted, it will check all the entries
     in the cache.

 -- 函式: linecache.lazycache (filename, module_globals)

     Capture enough detail about a non-file-based module to permit
     getting its lines later via *note getline(): dc9. even if
     'module_globals' is ‘None’ in the later call.  This avoids doing
     I/O until a line is actually needed, without having to carry the
     module globals around indefinitely.

     在 3.5 版被加入.

範例：

     >>> import linecache
     >>> linecache.getline(linecache.__file__, 8)
     'import sys\n'

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/linecache.py

   (2) https://peps.python.org/pep-0302/


File: python.info,  Node: shutil — 高階檔案操作,  Prev: linecache --- 隨機存取文字列,  Up: 檔案與目錄存取

5.11.10 ‘shutil’ — 高階檔案操作
-------------------------------

'原始碼：'Lib/shutil.py(1)

__________________________________________________________________

The *note shutil: b3. module offers a number of high-level operations on
files and collections of files.  In particular, functions are provided
which support file copying and removal.  For operations on individual
files, see also the *note os: 91. module.

     警告: Even the higher-level file copying functions (*note
     shutil.copy(): 9fd, *note shutil.copy2(): 9fe.) cannot copy all
     file metadata.

     On POSIX platforms, this means that file owner and group are lost
     as well as ACLs.  On Mac OS, the resource fork and other metadata
     are not used.  This means that resources will be lost and file type
     and creator codes will not be correct.  On Windows, file owners,
     ACLs and alternate data streams are not copied.

* Menu:

* Directory and files operations::
* Archiving operations::
* Querying the size of the output terminal::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/shutil.py


File: python.info,  Node: Directory and files operations,  Next: Archiving operations,  Up: shutil — 高階檔案操作

5.11.10.1 Directory and files operations
........................................

 -- 函式: shutil.copyfileobj (fsrc, fdst[, length])

     Copy the contents of the *note file-like object: 115b. 'fsrc' to
     the file-like object 'fdst'.  The integer 'length', if given, is
     the buffer size.  In particular, a negative 'length' value means to
     copy the data without looping over the source data in chunks; by
     default the data is read in chunks to avoid uncontrolled memory
     consumption.  Note that if the current file position of the 'fsrc'
     object is not 0, only the contents from the current file position
     to the end of the file will be copied.

 -- 函式: shutil.copyfile (src, dst, *, follow_symlinks=True)

     Copy the contents (no metadata) of the file named 'src' to a file
     named 'dst' and return 'dst' in the most efficient way possible.
     'src' and 'dst' are *note path-like objects: ac2. or path names
     given as strings.

     'dst' must be the complete target file name; look at *note copy():
     9fd. for a copy that accepts a target directory path.  If 'src' and
     'dst' specify the same file, *note SameFileError: f40. is raised.

     The destination location must be writable; otherwise, an *note
     OSError: 350. exception will be raised.  If 'dst' already exists,
     it will be replaced.  Special files such as character or block
     devices and pipes cannot be copied with this function.

     If 'follow_symlinks' is false and 'src' is a symbolic link, a new
     symbolic link will be created instead of copying the file 'src'
     points to.

     引發一個附帶引數 ‘src’、‘dst’ 的*note 稽核事件: 17bd.
     ‘shutil.copyfile’。

     在 3.3 版的變更: *note IOError: ff5. used to be raised instead of
     *note OSError: 350.  Added 'follow_symlinks' argument.  Now returns
     'dst'.

     在 3.4 版的變更: Raise *note SameFileError: f40. instead of *note
     Error: f3f.  Since the former is a subclass of the latter, this
     change is backward compatible.

     在 3.8 版的變更: Platform-specific fast-copy syscalls may be used
     internally in order to copy the file more efficiently.  See *note
     Platform-dependent efficient copy operations: a01. section.

 -- 例外: shutil.SameFileError

     This exception is raised if source and destination in *note
     copyfile(): 9fc. are the same file.

     在 3.4 版被加入.

 -- 函式: shutil.copymode (src, dst, *, follow_symlinks=True)

     Copy the permission bits from 'src' to 'dst'.  The file contents,
     owner, and group are unaffected.  'src' and 'dst' are *note
     path-like objects: ac2. or path names given as strings.  If
     'follow_symlinks' is false, and both 'src' and 'dst' are symbolic
     links, *note copymode(): 15a3. will attempt to modify the mode of
     'dst' itself (rather than the file it points to).  This
     functionality is not available on every platform; please see *note
     copystat(): 10c7. for more information.  If *note copymode(): 15a3.
     cannot modify symbolic links on the local platform, and it is asked
     to do so, it will do nothing and return.

     引發一個附帶引數 ‘src’、‘dst’ 的*note 稽核事件: 17bd.
     ‘shutil.copymode’。

     在 3.3 版的變更: 新增 'follow_symlinks' 引數。

 -- 函式: shutil.copystat (src, dst, *, follow_symlinks=True)

     Copy the permission bits, last access time, last modification time,
     and flags from 'src' to 'dst'.  On Linux, *note copystat(): 10c7.
     also copies the "extended attributes" where possible.  The file
     contents, owner, and group are unaffected.  'src' and 'dst' are
     *note path-like objects: ac2. or path names given as strings.

     If 'follow_symlinks' is false, and 'src' and 'dst' both refer to
     symbolic links, *note copystat(): 10c7. will operate on the
     symbolic links themselves rather than the files the symbolic links
     refer to—reading the information from the 'src' symbolic link, and
     writing the information to the 'dst' symbolic link.

          備註: Not all platforms provide the ability to examine and
          modify symbolic links.  Python itself can tell you what
          functionality is locally available.

             * If ‘os.chmod in os.supports_follow_symlinks’ is ‘True’,
               *note copystat(): 10c7. can modify the permission bits of
               a symbolic link.

             * If ‘os.utime in os.supports_follow_symlinks’ is ‘True’,
               *note copystat(): 10c7. can modify the last access and
               modification times of a symbolic link.

             * If ‘os.chflags in os.supports_follow_symlinks’ is ‘True’,
               *note copystat(): 10c7. can modify the flags of a
               symbolic link.  (‘os.chflags’ is not available on all
               platforms.)

          On platforms where some or all of this functionality is
          unavailable, when asked to modify a symbolic link, *note
          copystat(): 10c7. will copy everything it can.  *note
          copystat(): 10c7. never returns failure.

          更多資訊請見 *note os.supports_follow_symlinks: 274b.。

     引發一個附帶引數 ‘src’、‘dst’ 的*note 稽核事件: 17bd.
     ‘shutil.copystat’。

     在 3.3 版的變更: Added 'follow_symlinks' argument and support for
     Linux extended attributes.

 -- 函式: shutil.copy (src, dst, *, follow_symlinks=True)

     Copies the file 'src' to the file or directory 'dst'.  'src' and
     'dst' should be *note path-like objects: ac2. or strings.  If 'dst'
     specifies a directory, the file will be copied into 'dst' using the
     base filename from 'src'.  If 'dst' specifies a file that already
     exists, it will be replaced.  Returns the path to the newly created
     file.

     If 'follow_symlinks' is false, and 'src' is a symbolic link, 'dst'
     will be created as a symbolic link.  If 'follow_symlinks' is true
     and 'src' is a symbolic link, 'dst' will be a copy of the file
     'src' refers to.

     *note copy(): 9fd. copies the file data and the file's permission
     mode (see *note os.chmod(): 200.).  Other metadata, like the file's
     creation and modification times, is not preserved.  To preserve all
     file metadata from the original, use *note copy2(): 9fe. instead.

     引發一個附帶引數 ‘src’、‘dst’ 的*note 稽核事件: 17bd.
     ‘shutil.copyfile’。

     引發一個附帶引數 ‘src’、‘dst’ 的*note 稽核事件: 17bd.
     ‘shutil.copymode’。

     在 3.3 版的變更: Added 'follow_symlinks' argument.  Now returns
     path to the newly created file.

     在 3.8 版的變更: Platform-specific fast-copy syscalls may be used
     internally in order to copy the file more efficiently.  See *note
     Platform-dependent efficient copy operations: a01. section.

 -- 函式: shutil.copy2 (src, dst, *, follow_symlinks=True)

     Identical to *note copy(): 9fd. except that *note copy2(): 9fe.
     also attempts to preserve file metadata.

     When 'follow_symlinks' is false, and 'src' is a symbolic link,
     *note copy2(): 9fe. attempts to copy all metadata from the 'src'
     symbolic link to the newly created 'dst' symbolic link.  However,
     this functionality is not available on all platforms.  On platforms
     where some or all of this functionality is unavailable, *note
     copy2(): 9fe. will preserve all the metadata it can; *note copy2():
     9fe. never raises an exception because it cannot preserve file
     metadata.

     *note copy2(): 9fe. uses *note copystat(): 10c7. to copy the file
     metadata.  Please see *note copystat(): 10c7. for more information
     about platform support for modifying symbolic link metadata.

     引發一個附帶引數 ‘src’、‘dst’ 的*note 稽核事件: 17bd.
     ‘shutil.copyfile’。

     引發一個附帶引數 ‘src’、‘dst’ 的*note 稽核事件: 17bd.
     ‘shutil.copystat’。

     在 3.3 版的變更: Added 'follow_symlinks' argument, try to copy
     extended file system attributes too (currently Linux only).  Now
     returns path to the newly created file.

     在 3.8 版的變更: Platform-specific fast-copy syscalls may be used
     internally in order to copy the file more efficiently.  See *note
     Platform-dependent efficient copy operations: a01. section.

 -- 函式: shutil.ignore_patterns (*patterns)

     This factory function creates a function that can be used as a
     callable for *note copytree(): 9cd.'s 'ignore' argument, ignoring
     files and directories that match one of the glob-style 'patterns'
     provided.  See the example below.

 -- 函式: shutil.copytree (src, dst, symlinks=False, ignore=None,
          copy_function=copy2, ignore_dangling_symlinks=False,
          dirs_exist_ok=False)

     Recursively copy an entire directory tree rooted at 'src' to a
     directory named 'dst' and return the destination directory.  All
     intermediate directories needed to contain 'dst' will also be
     created by default.

     Permissions and times of directories are copied with *note
     copystat(): 10c7, individual files are copied using *note copy2():
     9fe.

     If 'symlinks' is true, symbolic links in the source tree are
     represented as symbolic links in the new tree and the metadata of
     the original links will be copied as far as the platform allows; if
     false or omitted, the contents and metadata of the linked files are
     copied to the new tree.

     When 'symlinks' is false, if the file pointed to by the symlink
     doesn't exist, an exception will be added in the list of errors
     raised in an *note Error: f3f. exception at the end of the copy
     process.  You can set the optional 'ignore_dangling_symlinks' flag
     to true if you want to silence this exception.  Notice that this
     option has no effect on platforms that don't support *note
     os.symlink(): 108d.

     If 'ignore' is given, it must be a callable that will receive as
     its arguments the directory being visited by *note copytree(): 9cd,
     and a list of its contents, as returned by *note os.listdir():
     1092.  Since *note copytree(): 9cd. is called recursively, the
     'ignore' callable will be called once for each directory that is
     copied.  The callable must return a sequence of directory and file
     names relative to the current directory (i.e.  a subset of the
     items in its second argument); these names will then be ignored in
     the copy process.  *note ignore_patterns(): 274c. can be used to
     create such a callable that ignores names based on glob-style
     patterns.

     If exception(s) occur, an *note Error: f3f. is raised with a list
     of reasons.

     If 'copy_function' is given, it must be a callable that will be
     used to copy each file.  It will be called with the source path and
     the destination path as arguments.  By default, *note copy2(): 9fe.
     is used, but any function that supports the same signature (like
     *note copy(): 9fd.) can be used.

     If 'dirs_exist_ok' is false (the default) and 'dst' already exists,
     a *note FileExistsError: fc3. is raised.  If 'dirs_exist_ok' is
     true, the copying operation will continue if it encounters existing
     directories, and files within the 'dst' tree will be overwritten by
     corresponding files from the 'src' tree.

     引發一個附帶引數 ‘src’、‘dst’ 的*note 稽核事件: 17bd.
     ‘shutil.copytree’。

     在 3.2 版的變更: Added the 'copy_function' argument to be able to
     provide a custom copy function.  Added the
     'ignore_dangling_symlinks' argument to silence dangling symlinks
     errors when 'symlinks' is false.

     在 3.3 版的變更: Copy metadata when 'symlinks' is false.  Now
     returns 'dst'.

     在 3.8 版的變更: Platform-specific fast-copy syscalls may be used
     internally in order to copy the file more efficiently.  See *note
     Platform-dependent efficient copy operations: a01. section.

     在 3.8 版的變更: 新增 'dirs_exist_ok' 參數。

 -- 函式: shutil.rmtree (path, ignore_errors=False, onerror=None, *,
          onexc=None, dir_fd=None)

     Delete an entire directory tree; 'path' must point to a directory
     (but not a symbolic link to a directory).  If 'ignore_errors' is
     true, errors resulting from failed removals will be ignored; if
     false or omitted, such errors are handled by calling a handler
     specified by 'onexc' or 'onerror' or, if both are omitted,
     exceptions are propagated to the caller.

     This function can support *note paths relative to directory
     descriptors: 1083.

          備註: On platforms that support the necessary fd-based
          functions a symlink attack resistant version of *note
          rmtree(): 2d2. is used by default.  On other platforms, the
          *note rmtree(): 2d2. implementation is susceptible to a
          symlink attack: given proper timing and circumstances,
          attackers can manipulate symlinks on the filesystem to delete
          files they wouldn't be able to access otherwise.  Applications
          can use the *note rmtree.avoids_symlink_attacks: 274d.
          function attribute to determine which case applies.

     If 'onexc' is provided, it must be a callable that accepts three
     parameters: 'function', 'path', and 'excinfo'.

     The first parameter, 'function', is the function which raised the
     exception; it depends on the platform and implementation.  The
     second parameter, 'path', will be the path name passed to
     'function'.  The third parameter, 'excinfo', is the exception that
     was raised.  Exceptions raised by 'onexc' will not be caught.

     The deprecated 'onerror' is similar to 'onexc', except that the
     third parameter it receives is the tuple returned from *note
     sys.exc_info(): 630.

     引發一個附帶引數 ‘path’、‘dir_fd’ 的*note 稽核事件: 17bd.
     ‘shutil.rmtree’。

     在 3.3 版的變更: Added a symlink attack resistant version that is
     used automatically if platform supports fd-based functions.

     在 3.8 版的變更: On Windows, will no longer delete the contents of
     a directory junction before removing the junction.

     在 3.11 版的變更: 新增 'dir_fd' 參數。

     在 3.12 版的變更: 新增 'onexc' 參數並棄用 'onerror'。

     在 3.13 版的變更: ‘rmtree()’ now ignores *note FileNotFoundError:
     e67. exceptions for all but the top-level path.  Exceptions other
     than *note OSError: 350. and subclasses of ‘OSError’ are now always
     propagated to the caller.

      -- 屬性: rmtree.avoids_symlink_attacks

          Indicates whether the current platform and implementation
          provides a symlink attack resistant version of *note rmtree():
          2d2.  Currently this is only true for platforms supporting
          fd-based directory access functions.

          在 3.3 版被加入.

 -- 函式: shutil.move (src, dst, copy_function=copy2)

     Recursively move a file or directory ('src') to another location
     and return the destination.

     If 'dst' is an existing directory or a symlink to a directory, then
     'src' is moved inside that directory.  The destination path in that
     directory must not already exist.

     If 'dst' already exists but is not a directory, it may be
     overwritten depending on *note os.rename(): 108a. semantics.

     If the destination is on the current filesystem, then *note
     os.rename(): 108a. is used.  Otherwise, 'src' is copied to the
     destination using 'copy_function' and then removed.  In case of
     symlinks, a new symlink pointing to the target of 'src' will be
     created as the destination and 'src' will be removed.

     If 'copy_function' is given, it must be a callable that takes two
     arguments, 'src' and the destination, and will be used to copy
     'src' to the destination if *note os.rename(): 108a. cannot be
     used.  If the source is a directory, *note copytree(): 9cd. is
     called, passing it the 'copy_function'.  The default
     'copy_function' is *note copy2(): 9fe.  Using *note copy(): 9fd. as
     the 'copy_function' allows the move to succeed when it is not
     possible to also copy the metadata, at the expense of not copying
     any of the metadata.

     引發一個附帶引數 ‘src’、‘dst’ 的*note 稽核事件: 17bd.
     ‘shutil.move’。

     在 3.3 版的變更: Added explicit symlink handling for foreign
     filesystems, thus adapting it to the behavior of GNU's ‘mv’.  Now
     returns 'dst'.

     在 3.5 版的變更: 新增 'copy_function' 關鍵字引數。

     在 3.8 版的變更: Platform-specific fast-copy syscalls may be used
     internally in order to copy the file more efficiently.  See *note
     Platform-dependent efficient copy operations: a01. section.

     在 3.9 版的變更: Accepts a *note path-like object: ac2. for both
     'src' and 'dst'.

 -- 函式: shutil.disk_usage (path)

     Return disk usage statistics about the given path as a *note named
     tuple: 5f4. with the attributes 'total', 'used' and 'free', which
     are the amount of total, used and free space, in bytes.  'path' may
     be a file or a directory.

          備註: On Unix filesystems, 'path' must point to a path within
          a 'mounted' filesystem partition.  On those platforms, CPython
          doesn't attempt to retrieve disk usage information from
          non-mounted filesystems.

     在 3.3 版被加入.

     在 3.8 版的變更: On Windows, 'path' can now be a file or directory.

     *note 適用: 1c56.：Unix、Windows。

 -- 函式: shutil.chown (path, user=None, group=None, *, dir_fd=None,
          follow_symlinks=True)

     Change owner 'user' and/or 'group' of the given 'path'.

     'user' can be a system user name or a uid; the same applies to
     'group'.  At least one argument is required.

     See also *note os.chown(): 1087, the underlying function.

     引發一個附帶引數 ‘path’、‘user’、‘group’ 的*note 稽核事件: 17bd.
     ‘shutil.chown’。

     *note 適用: 1c56.：Unix。

     在 3.3 版被加入.

     在 3.13 版的變更: Added 'dir_fd' and 'follow_symlinks' parameters.

 -- 函式: shutil.which (cmd, mode=os.F_OK | os.X_OK, path=None)

     Return the path to an executable which would be run if the given
     'cmd' was called.  If no 'cmd' would be called, return ‘None’.

     'mode' is a permission mask passed to *note os.access(): 1085, by
     default determining if the file exists and is executable.

     'path' is a "‘PATH’ string" specifying the lookup directory list.
     When no 'path' is specified, the results of *note os.environ():
     1152. are used, returning either the "PATH" value or a fallback of
     *note os.defpath: 1908.

     On Windows, the current directory is prepended to the 'path' if
     'mode' does not include ‘os.X_OK’.  When the 'mode' does include
     ‘os.X_OK’, the Windows API ‘NeedCurrentDirectoryForExePathW’ will
     be consulted to determine if the current directory should be
     prepended to 'path'.  To avoid consulting the current working
     directory for executables: set the environment variable
     ‘NoDefaultCurrentDirectoryInExePath’.

     Also on Windows, the ‘PATHEXT’ variable is used to resolve commands
     that may not already include an extension.  For example, if you
     call ‘shutil.which("python")’, *note which(): 45b. will search
     ‘PATHEXT’ to know that it should look for ‘python.exe’ within the
     'path' directories.  For example, on Windows:

          >>> shutil.which("python")
          'C:\\Python33\\python.EXE'

     This is also applied when 'cmd' is a path that contains a directory
     component:

          >> shutil.which("C:\\Python33\\python")
          'C:\\Python33\\python.EXE'

     在 3.3 版被加入.

     在 3.8 版的變更: The *note bytes: 1a5. type is now accepted.  If
     'cmd' type is *note bytes: 1a5, the result type is also *note
     bytes: 1a5.

     在 3.12 版的變更: On Windows, the current directory is no longer
     prepended to the search path if 'mode' includes ‘os.X_OK’ and
     WinAPI ‘NeedCurrentDirectoryForExePathW(cmd)’ is false, else the
     current directory is prepended even if it is already in the search
     path; ‘PATHEXT’ is used now even when 'cmd' includes a directory
     component or ends with an extension that is in ‘PATHEXT’; and
     filenames that have no extension can now be found.

     在 3.12.1 版的變更: On Windows, if 'mode' includes ‘os.X_OK’,
     executables with an extension in ‘PATHEXT’ will be preferred over
     executables without a matching extension.  This brings behavior
     closer to that of Python 3.11.

 -- 例外: shutil.Error

     This exception collects exceptions that are raised during a
     multi-file operation.  For *note copytree(): 9cd, the exception
     argument is a list of 3-tuples ('srcname', 'dstname', 'exception').

* Menu:

* Platform-dependent efficient copy operations::
* copytree example::
* rmtree 範例::


File: python.info,  Node: Platform-dependent efficient copy operations,  Next: copytree example,  Up: Directory and files operations

5.11.10.2 Platform-dependent efficient copy operations
......................................................

Starting from Python 3.8, all functions involving a file copy (*note
copyfile(): 9fc, *note copy(): 9fd, *note copy2(): 9fe, *note
copytree(): 9cd, and *note move(): 9ff.) may use platform-specific
"fast-copy" syscalls in order to copy the file more efficiently (see
bpo-33671(1)).  "fast-copy" means that the copying operation occurs
within the kernel, avoiding the use of userspace buffers in Python as in
"‘outfd.write(infd.read())’".

On macOS fcopyfile(2) is used to copy the file content (not metadata).

On Linux *note os.sendfile(): ab2. is used.

On Windows *note shutil.copyfile(): 9fc. uses a bigger default buffer
size (1 MiB instead of 64 KiB) and a *note memoryview(): 40f.-based
variant of *note shutil.copyfileobj(): a00. is used.

If the fast-copy operation fails and no data was written in the
destination file then shutil will silently fallback on using less
efficient *note copyfileobj(): a00. function internally.

在 3.8 版的變更.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33671

   (2) http://www.manpagez.com/man/3/copyfile/


File: python.info,  Node: copytree example,  Next: rmtree 範例,  Prev: Platform-dependent efficient copy operations,  Up: Directory and files operations

5.11.10.3 copytree example
..........................

An example that uses the *note ignore_patterns(): 274c. helper:

     from shutil import copytree, ignore_patterns

     copytree(source, destination, ignore=ignore_patterns('*.pyc', 'tmp*'))

This will copy everything except ‘.pyc’ files and files or directories
whose name starts with ‘tmp’.

Another example that uses the 'ignore' argument to add a logging call:

     from shutil import copytree
     import logging

     def _logpath(path, names):
         logging.info('Working in %s', path)
         return []   # nothing will be ignored

     copytree(source, destination, ignore=_logpath)


File: python.info,  Node: rmtree 範例,  Prev: copytree example,  Up: Directory and files operations

5.11.10.4 rmtree 範例
.....................

This example shows how to remove a directory tree on Windows where some
of the files have their read-only bit set.  It uses the onexc callback
to clear the readonly bit and reattempt the remove.  Any subsequent
failure will propagate.

     import os, stat
     import shutil

     def remove_readonly(func, path, _):
         "Clear the readonly bit and reattempt the removal"
         os.chmod(path, stat.S_IWRITE)
         func(path)

     shutil.rmtree(directory, onexc=remove_readonly)


File: python.info,  Node: Archiving operations,  Next: Querying the size of the output terminal,  Prev: Directory and files operations,  Up: shutil — 高階檔案操作

5.11.10.5 Archiving operations
..............................

在 3.2 版被加入.

在 3.5 版的變更: 新增 'xztar' 格式的支援。

High-level utilities to create and read compressed and archived files
are also provided.  They rely on the *note zipfile: 117. and *note
tarfile: c8. modules.

 -- 函式: shutil.make_archive (base_name, format[, root_dir[, base_dir[,
          verbose[, dry_run[, owner[, group[, logger]]]]]]])

     Create an archive file (such as zip or tar) and return its name.

     'base_name' is the name of the file to create, including the path,
     minus any format-specific extension.

     'format' is the archive format: one of "zip" (if the *note zlib:
     119. module is available), "tar", "gztar" (if the *note zlib: 119.
     module is available), "bztar" (if the *note bz2: f. module is
     available), or "xztar" (if the *note lzma: 7e. module is
     available).

     'root_dir' is a directory that will be the root directory of the
     archive, all paths in the archive will be relative to it; for
     example, we typically chdir into 'root_dir' before creating the
     archive.

     'base_dir' is the directory where we start archiving from; i.e.
     'base_dir' will be the common prefix of all files and directories
     in the archive.  'base_dir' must be given relative to 'root_dir'.
     See *note Archiving example with base_dir: 2754. for how to use
     'base_dir' and 'root_dir' together.

     'root_dir' and 'base_dir' both default to the current directory.

     If 'dry_run' is true, no archive is created, but the operations
     that would be executed are logged to 'logger'.

     'owner' and 'group' are used when creating a tar archive.  By
     default, uses the current owner and group.

     'logger' must be an object compatible with PEP 282(1), usually an
     instance of *note logging.Logger: af3.

     The 'verbose' argument is unused and deprecated.

     引發一個附帶引數 ‘base_name’、‘format’、‘root_dir’、‘base_dir’ 的
     *note 稽核事件: 17bd. ‘shutil.make_archive’。

          備註: This function is not thread-safe when custom archivers
          registered with *note register_archive_format(): 2755. do not
          support the 'root_dir' argument.  In this case it temporarily
          changes the current working directory of the process to
          'root_dir' to perform archiving.

     在 3.8 版的變更: The modern pax (POSIX.1-2001) format is now used
     instead of the legacy GNU format for archives created with
     ‘format="tar"’.

     在 3.10.6 版的變更: This function is now made thread-safe during
     creation of standard ‘.zip’ and tar archives.

 -- 函式: shutil.get_archive_formats ()

     Return a list of supported formats for archiving.  Each element of
     the returned sequence is a tuple ‘(name, description)’.

     By default *note shutil: b3. provides these formats:

        - 'zip': ZIP file (if the *note zlib: 119. module is available).

        - 'tar': Uncompressed tar file.  Uses POSIX.1-2001 pax format
          for new archives.

        - 'gztar': gzip'ed tar-file (if the *note zlib: 119. module is
          available).

        - 'bztar': bzip2'ed tar-file (if the *note bz2: f. module is
          available).

        - 'xztar': xz'ed tar-file (if the *note lzma: 7e. module is
          available).

     You can register new formats or provide your own archiver for any
     existing formats, by using *note register_archive_format(): 2755.

 -- 函式: shutil.register_archive_format (name, function[, extra_args[,
          description]])

     Register an archiver for the format 'name'.

     'function' is the callable that will be used to unpack archives.
     The callable will receive the 'base_name' of the file to create,
     followed by the 'base_dir' (which defaults to *note os.curdir:
     26b7.) to start archiving from.  Further arguments are passed as
     keyword arguments: 'owner', 'group', 'dry_run' and 'logger' (as
     passed in *note make_archive(): 45a.).

     If 'function' has the custom attribute ‘function.supports_root_dir’
     set to ‘True’, the 'root_dir' argument is passed as a keyword
     argument.  Otherwise the current working directory of the process
     is temporarily changed to 'root_dir' before calling 'function'.  In
     this case *note make_archive(): 45a. is not thread-safe.

     If given, 'extra_args' is a sequence of ‘(name, value)’ pairs that
     will be used as extra keywords arguments when the archiver callable
     is used.

     'description' is used by *note get_archive_formats(): 2756. which
     returns the list of archivers.  Defaults to an empty string.

     在 3.12 版的變更: Added support for functions supporting the
     'root_dir' argument.

 -- 函式: shutil.unregister_archive_format (name)

     Remove the archive format 'name' from the list of supported
     formats.

 -- 函式: shutil.unpack_archive (filename[, extract_dir[, format[,
          filter]]])

     Unpack an archive.  'filename' is the full path of the archive.

     'extract_dir' is the name of the target directory where the archive
     is unpacked.  If not provided, the current working directory is
     used.

     'format' is the archive format: one of "zip", "tar", "gztar",
     "bztar", or "xztar".  Or any other format registered with *note
     register_unpack_format(): 2758.  If not provided, *note
     unpack_archive(): 412. will use the archive file name extension and
     see if an unpacker was registered for that extension.  In case none
     is found, a *note ValueError: 1e7. is raised.

     The keyword-only 'filter' argument is passed to the underlying
     unpacking function.  For zip files, 'filter' is not accepted.  For
     tar files, it is recommended to set it to ‘'data'’, unless using
     features specific to tar and UNIX-like filesystems.  (See *note
     Extraction filters: 413. for details.)  The ‘'data'’ filter will
     become the default for tar files in Python 3.14.

     引發一個附帶引數 ‘filename’、‘extract_dir’、‘format’ 的*note
     稽核事件: 17bd. ‘shutil.unpack_archive’。

          警告: Never extract archives from untrusted sources without
          prior inspection.  It is possible that files are created
          outside of the path specified in the 'extract_dir' argument,
          e.g.  members that have absolute filenames starting with "/"
          or filenames with two dots "..".

     在 3.7 版的變更: Accepts a *note path-like object: ac2. for
     'filename' and 'extract_dir'.

     在 3.12 版的變更: 新增 'filter' 引數。

 -- 函式: shutil.register_unpack_format (name, extensions, function[,
          extra_args[, description]])

     Registers an unpack format.  'name' is the name of the format and
     'extensions' is a list of extensions corresponding to the format,
     like ‘.zip’ for Zip files.

     'function' is the callable that will be used to unpack archives.
     The callable will receive:

        - the path of the archive, as a positional argument;

        - the directory the archive must be extracted to, as a
          positional argument;

        - possibly a 'filter' keyword argument, if it was given to *note
          unpack_archive(): 412.;

        - additional keyword arguments, specified by 'extra_args' as a
          sequence of ‘(name, value)’ tuples.

     'description' can be provided to describe the format, and will be
     returned by the *note get_unpack_formats(): 2759. function.

 -- 函式: shutil.unregister_unpack_format (name)

     Unregister an unpack format.  'name' is the name of the format.

 -- 函式: shutil.get_unpack_formats ()

     Return a list of all registered formats for unpacking.  Each
     element of the returned sequence is a tuple ‘(name, extensions,
     description)’.

     By default *note shutil: b3. provides these formats:

        - 'zip': ZIP file (unpacking compressed files works only if the
          corresponding module is available).

        - 'tar': uncompressed tar file.

        - 'gztar': gzip'ed tar-file (if the *note zlib: 119. module is
          available).

        - 'bztar': bzip2'ed tar-file (if the *note bz2: f. module is
          available).

        - 'xztar': xz'ed tar-file (if the *note lzma: 7e. module is
          available).

     You can register new formats or provide your own unpacker for any
     existing formats, by using *note register_unpack_format(): 2758.

* Menu:

* Archiving example::
* Archiving example with base_dir::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0282/


File: python.info,  Node: Archiving example,  Next: Archiving example with base_dir,  Up: Archiving operations

5.11.10.6 Archiving example
...........................

In this example, we create a gzip'ed tar-file archive containing all
files found in the ‘.ssh’ directory of the user:

     >>> from shutil import make_archive
     >>> import os
     >>> archive_name = os.path.expanduser(os.path.join('~', 'myarchive'))
     >>> root_dir = os.path.expanduser(os.path.join('~', '.ssh'))
     >>> make_archive(archive_name, 'gztar', root_dir)
     '/Users/tarek/myarchive.tar.gz'

The resulting archive contains:

     $ tar -tzvf /Users/tarek/myarchive.tar.gz
     drwx------ tarek/staff       0 2010-02-01 16:23:40 ./
     -rw-r--r-- tarek/staff     609 2008-06-09 13:26:54 ./authorized_keys
     -rwxr-xr-x tarek/staff      65 2008-06-09 13:26:54 ./config
     -rwx------ tarek/staff     668 2008-06-09 13:26:54 ./id_dsa
     -rwxr-xr-x tarek/staff     609 2008-06-09 13:26:54 ./id_dsa.pub
     -rw------- tarek/staff    1675 2008-06-09 13:26:54 ./id_rsa
     -rw-r--r-- tarek/staff     397 2008-06-09 13:26:54 ./id_rsa.pub
     -rw-r--r-- tarek/staff   37192 2010-02-06 18:23:10 ./known_hosts


File: python.info,  Node: Archiving example with base_dir,  Prev: Archiving example,  Up: Archiving operations

5.11.10.7 Archiving example with 'base_dir'
...........................................

In this example, similar to the *note one above: 275c, we show how to
use *note make_archive(): 45a, but this time with the usage of
'base_dir'.  We now have the following directory structure:

     $ tree tmp
     tmp
     └── root
         └── structure
             ├── content
                 └── please_add.txt
             └── do_not_add.txt

In the final archive, ‘please_add.txt’ should be included, but
‘do_not_add.txt’ should not.  Therefore we use the following:

     >>> from shutil import make_archive
     >>> import os
     >>> archive_name = os.path.expanduser(os.path.join('~', 'myarchive'))
     >>> make_archive(
     ...     archive_name,
     ...     'tar',
     ...     root_dir='tmp/root',
     ...     base_dir='structure/content',
     ... )
     '/Users/tarek/my_archive.tar'

Listing the files in the resulting archive gives us:

     $ python -m tarfile -l /Users/tarek/myarchive.tar
     structure/content/
     structure/content/please_add.txt


File: python.info,  Node: Querying the size of the output terminal,  Prev: Archiving operations,  Up: shutil — 高階檔案操作

5.11.10.8 Querying the size of the output terminal
..................................................

 -- 函式: shutil.get_terminal_size (fallback=(columns, lines))

     Get the size of the terminal window.

     For each of the two dimensions, the environment variable, ‘COLUMNS’
     and ‘LINES’ respectively, is checked.  If the variable is defined
     and the value is a positive integer, it is used.

     When ‘COLUMNS’ or ‘LINES’ is not defined, which is the common case,
     the terminal connected to *note sys.__stdout__: 275f. is queried by
     invoking *note os.get_terminal_size(): 109a.

     If the terminal size cannot be successfully queried, either because
     the system doesn't support querying, or because we are not
     connected to a terminal, the value given in ‘fallback’ parameter is
     used.  ‘fallback’ defaults to ‘(80, 24)’ which is the default size
     used by many terminal emulators.

     The value returned is a named tuple of type *note os.terminal_size:
     2760.

     See also: The Single UNIX Specification, Version 2, Other
     Environment Variables(1).

     在 3.3 版被加入.

     在 3.11 版的變更: The ‘fallback’ values are also used if *note
     os.get_terminal_size(): 109a. returns zeroes.

也參考
......

Module *note os: 91.

     作業系統介面，包括處理比 Python *note 檔案物件: 115b.更低階檔案的函
     式。

Module *note io: 73.

     Python 的內建 I/O 函式庫，包含抽象類別和一些具體類別 (concrete
     class)，如檔案 I/O。

內建函式 *note open(): 4c0.

     使用 Python 打開檔案以進行讀寫檔案的標準方法。

   ---------- Footnotes ----------

   (1) 
https://pubs.opengroup.org/onlinepubs/7908799/xbd/envvar.html#tag_002_003


File: python.info,  Node: 資料持久性 Data Persistence,  Next: 資料壓縮與保存,  Prev: 檔案與目錄存取,  Up: Python 標準函式庫 Standard Library

5.12 資料持久性 (Data Persistence)
==================================

The modules described in this chapter support storing Python data in a
persistent form on disk.  The *note pickle: 95. and *note marshal: 80.
modules can turn many Python data types into a stream of bytes and then
recreate the objects from the bytes.  The various DBM-related modules
support a family of hash-based file formats that store a mapping of
strings to other strings.

本章節所描述的模組列表為：

* Menu:

* pickle: pickle --- Python 物件序列化. Python 物件序列化
* copyreg: copyreg --- 註冊 pickle 支援函式. 註冊 pickle 支援函式
* shelve: shelve --- Python object persistence. Python object persistence
* marshal: marshal --- 内部 Python 物件序列化. 内部 Python 物件序列化
* dbm: dbm --- Unix "databases" 的介面. Unix "databases" 的介面
* sqlite3: sqlite3 --- SQLite 資料庫的 DB-API 2 0 介面. SQLite 資料庫的 DB-API 2.0 介面


File: python.info,  Node: pickle --- Python 物件序列化,  Next: copyreg --- 註冊 pickle 支援函式,  Up: 資料持久性 Data Persistence

5.12.1 ‘pickle’ -- Python 物件序列化
------------------------------------

'原始碼：'Lib/pickle.py(1)

__________________________________________________________________

The *note pickle: 95. module implements binary protocols for serializing
and de-serializing a Python object structure.  '"Pickling"' is the
process whereby a Python object hierarchy is converted into a byte
stream, and '"unpickling"' is the inverse operation, whereby a byte
stream (from a *note binary file: 1b8b. or *note bytes-like object:
cd4.) is converted back into an object hierarchy.  Pickling (and
unpickling) is alternatively known as "serialization", "marshalling,"
(2) or "flattening"; however, to avoid confusion, the terms used here
are "pickling" and "unpickling".

     警告: The ‘pickle’ module 'is not secure'.  Only unpickle data you
     trust.

     It is possible to construct malicious pickle data which will
     'execute arbitrary code during unpickling'.  Never unpickle data
     that could have come from an untrusted source, or that could have
     been tampered with.

     Consider signing data with *note hmac: 60. if you need to ensure
     that it has not been tampered with.

     Safer serialization formats such as *note json: 76. may be more
     appropriate if you are processing untrusted data.  See *note 和
     json 的比較: 2766.

* Menu:

* 和其他 Python 模組的關係::
* Data stream format::
* 模組介面::
* What can be pickled and unpickled?::
* Pickling Class Instances::
* Custom Reduction for Types, Functions, and Other Objects: Custom Reduction for Types Functions and Other Objects.
* Out-of-band Buffers::
* Restricting Globals::
* Performance: Performance<2>.
* 範例: 範例<9>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/pickle.py

   (2) Don't confuse this with the *note marshal: 80. module


File: python.info,  Node: 和其他 Python 模組的關係,  Next: Data stream format,  Up: pickle --- Python 物件序列化

5.12.1.1 和其他 Python 模組的關係
.................................

* Menu:

* 和 marshal 的比較::
* 和 json 的比較::


File: python.info,  Node: 和 marshal 的比較,  Next: 和 json 的比較,  Up: 和其他 Python 模組的關係

5.12.1.2 和 ‘marshal’ 的比較
............................

Python has a more primitive serialization module called *note marshal:
80, but in general *note pickle: 95. should always be the preferred way
to serialize Python objects.  *note marshal: 80. exists primarily to
support Python's ‘.pyc’ files.

The *note pickle: 95. module differs from *note marshal: 80. in several
significant ways:

   * The *note pickle: 95. module keeps track of the objects it has
     already serialized, so that later references to the same object
     won't be serialized again.  *note marshal: 80. doesn't do this.

     This has implications both for recursive objects and object
     sharing.  Recursive objects are objects that contain references to
     themselves.  These are not handled by marshal, and in fact,
     attempting to marshal recursive objects will crash your Python
     interpreter.  Object sharing happens when there are multiple
     references to the same object in different places in the object
     hierarchy being serialized.  *note pickle: 95. stores such objects
     only once, and ensures that all other references point to the
     master copy.  Shared objects remain shared, which can be very
     important for mutable objects.

   * *note marshal: 80. cannot be used to serialize user-defined classes
     and their instances.  *note pickle: 95. can save and restore class
     instances transparently, however the class definition must be
     importable and live in the same module as when the object was
     stored.

   * The *note marshal: 80. serialization format is not guaranteed to be
     portable across Python versions.  Because its primary job in life
     is to support ‘.pyc’ files, the Python implementers reserve the
     right to change the serialization format in non-backwards
     compatible ways should the need arise.  The *note pickle: 95.
     serialization format is guaranteed to be backwards compatible
     across Python releases provided a compatible pickle protocol is
     chosen and pickling and unpickling code deals with Python 2 to
     Python 3 type differences if your data is crossing that unique
     breaking change language boundary.


File: python.info,  Node: 和 json 的比較,  Prev: 和 marshal 的比較,  Up: 和其他 Python 模組的關係

5.12.1.3 和 ‘json’ 的比較
.........................

There are fundamental differences between the pickle protocols and JSON
(JavaScript Object Notation)(1):

   * JSON is a text serialization format (it outputs unicode text,
     although most of the time it is then encoded to ‘utf-8’), while
     pickle is a binary serialization format;

   * JSON 是人類可讀的，而 pickle 不是；

   * JSON is interoperable and widely used outside of the Python
     ecosystem, while pickle is Python-specific;

   * JSON, by default, can only represent a subset of the Python
     built-in types, and no custom classes; pickle can represent an
     extremely large number of Python types (many of them automatically,
     by clever usage of Python's introspection facilities; complex cases
     can be tackled by implementing *note specific object APIs: 276a.);

   * Unlike pickle, deserializing untrusted JSON does not in itself
     create an arbitrary code execution vulnerability.

也參考
......

The *note json: 76. module: a standard library module allowing JSON
serialization and deserialization.

   ---------- Footnotes ----------

   (1) https://json.org


File: python.info,  Node: Data stream format,  Next: 模組介面,  Prev: 和其他 Python 模組的關係,  Up: pickle --- Python 物件序列化

5.12.1.4 Data stream format
...........................

The data format used by *note pickle: 95. is Python-specific.  This has
the advantage that there are no restrictions imposed by external
standards such as JSON (which can't represent pointer sharing); however
it means that non-Python programs may not be able to reconstruct pickled
Python objects.

By default, the *note pickle: 95. data format uses a relatively compact
binary representation.  If you need optimal size characteristics, you
can efficiently *note compress: 276c. pickled data.

The module *note pickletools: 96. contains tools for analyzing data
streams generated by *note pickle: 95.  *note pickletools: 96. source
code has extensive comments about opcodes used by pickle protocols.

There are currently 6 different protocols which can be used for
pickling.  The higher the protocol used, the more recent the version of
Python needed to read the pickle produced.

   * Protocol version 0 is the original "human-readable" protocol and is
     backwards compatible with earlier versions of Python.

   * Protocol version 1 is an old binary format which is also compatible
     with earlier versions of Python.

   * Protocol version 2 was introduced in Python 2.3.  It provides much
     more efficient pickling of *note new-style classes: 276d.  Refer to
     PEP 307(1) for information about improvements brought by protocol
     2.

   * Protocol version 3 was added in Python 3.0.  It has explicit
     support for *note bytes: 1a5. objects and cannot be unpickled by
     Python 2.x.  This was the default protocol in Python 3.0-3.7.

   * Protocol version 4 was added in Python 3.4.  It adds support for
     very large objects, pickling more kinds of objects, and some data
     format optimizations.  It is the default protocol starting with
     Python 3.8.  Refer to PEP 3154(2) for information about
     improvements brought by protocol 4.

   * Protocol version 5 was added in Python 3.8.  It adds support for
     out-of-band data and speedup for in-band data.  Refer to PEP 574(3)
     for information about improvements brought by protocol 5.

     備註: Serialization is a more primitive notion than persistence;
     although *note pickle: 95. reads and writes file objects, it does
     not handle the issue of naming persistent objects, nor the (even
     more complicated) issue of concurrent access to persistent objects.
     The *note pickle: 95. module can transform a complex object into a
     byte stream and it can transform the byte stream into an object
     with the same internal structure.  Perhaps the most obvious thing
     to do with these byte streams is to write them onto a file, but it
     is also conceivable to send them across a network or store them in
     a database.  The *note shelve: b1. module provides a simple
     interface to pickle and unpickle objects on DBM-style database
     files.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0307/

   (2) https://peps.python.org/pep-3154/

   (3) https://peps.python.org/pep-0574/


File: python.info,  Node: 模組介面,  Next: What can be pickled and unpickled?,  Prev: Data stream format,  Up: pickle --- Python 物件序列化

5.12.1.5 模組介面
.................

To serialize an object hierarchy, you simply call the *note dumps():
140d. function.  Similarly, to de-serialize a data stream, you call the
*note loads(): cb8. function.  However, if you want more control over
serialization and de-serialization, you can create a *note Pickler: 9c2.
or an *note Unpickler: 159f. object, respectively.

*note pickle: 95. 模組提供以下常數：

 -- 資料: pickle.HIGHEST_PROTOCOL

     An integer, the highest *note protocol version: c68. available.
     This value can be passed as a 'protocol' value to functions *note
     dump(): 276f. and *note dumps(): 140d. as well as the *note
     Pickler: 9c2. constructor.

 -- 資料: pickle.DEFAULT_PROTOCOL

     An integer, the default *note protocol version: c68. used for
     pickling.  May be less than *note HIGHEST_PROTOCOL: 140e.
     Currently the default protocol is 4, first introduced in Python 3.4
     and incompatible with previous versions.

     在 3.0 版的變更: 預設協定為 3。

     在 3.8 版的變更: 預設協定為 4。

The *note pickle: 95. module provides the following functions to make
the pickling process more convenient:

 -- 函式: pickle.dump (obj, file, protocol=None, *, fix_imports=True,
          buffer_callback=None)

     Write the pickled representation of the object 'obj' to the open
     *note file object: 115b. 'file'.  This is equivalent to
     ‘Pickler(file, protocol).dump(obj)’.

     Arguments 'file', 'protocol', 'fix_imports' and 'buffer_callback'
     have the same meaning as in the *note Pickler: 9c2. constructor.

     在 3.8 版的變更: 新增 'buffer_callback' 引數。

 -- 函式: pickle.dumps (obj, protocol=None, *, fix_imports=True,
          buffer_callback=None)

     Return the pickled representation of the object 'obj' as a *note
     bytes: 1a5. object, instead of writing it to a file.

     Arguments 'protocol', 'fix_imports' and 'buffer_callback' have the
     same meaning as in the *note Pickler: 9c2. constructor.

     在 3.8 版的變更: 新增 'buffer_callback' 引數。

 -- 函式: pickle.load (file, *, fix_imports=True, encoding='ASCII',
          errors='strict', buffers=None)

     Read the pickled representation of an object from the open *note
     file object: 115b. 'file' and return the reconstituted object
     hierarchy specified therein.  This is equivalent to
     ‘Unpickler(file).load()’.

     The protocol version of the pickle is detected automatically, so no
     protocol argument is needed.  Bytes past the pickled representation
     of the object are ignored.

     Arguments 'file', 'fix_imports', 'encoding', 'errors', 'strict' and
     'buffers' have the same meaning as in the *note Unpickler: 159f.
     constructor.

     在 3.8 版的變更: 新增 'buffer' 引數。

 -- 函式: pickle.loads (data, /, *, fix_imports=True, encoding='ASCII',
          errors='strict', buffers=None)

     Return the reconstituted object hierarchy of the pickled
     representation 'data' of an object.  'data' must be a *note
     bytes-like object: cd4.

     The protocol version of the pickle is detected automatically, so no
     protocol argument is needed.  Bytes past the pickled representation
     of the object are ignored.

     Arguments 'fix_imports', 'encoding', 'errors', 'strict' and
     'buffers' have the same meaning as in the *note Unpickler: 159f.
     constructor.

     在 3.8 版的變更: 新增 'buffer' 引數。

The *note pickle: 95. module defines three exceptions:

 -- 例外: pickle.PickleError

     Common base class for the other pickling exceptions.  It inherits
     from *note Exception: 97d.

 -- 例外: pickle.PicklingError

     Error raised when an unpicklable object is encountered by *note
     Pickler: 9c2.  It inherits from *note PickleError: 2770.

     Refer to *note What can be pickled and unpickled?: 2772. to learn
     what kinds of objects can be pickled.

 -- 例外: pickle.UnpicklingError

     Error raised when there is a problem unpickling an object, such as
     a data corruption or a security violation.  It inherits from *note
     PickleError: 2770.

     Note that other exceptions may also be raised during unpickling,
     including (but not necessarily limited to) AttributeError,
     EOFError, ImportError, and IndexError.

The *note pickle: 95. module exports three classes, *note Pickler: 9c2,
*note Unpickler: 159f. and *note PickleBuffer: 16fd.:

 -- 類別: pickle.Pickler (file, protocol=None, *, fix_imports=True,
          buffer_callback=None)

     This takes a binary file for writing a pickle data stream.

     The optional 'protocol' argument, an integer, tells the pickler to
     use the given protocol; supported protocols are 0 to *note
     HIGHEST_PROTOCOL: 140e.  If not specified, the default is *note
     DEFAULT_PROTOCOL: 7d2.  If a negative number is specified, *note
     HIGHEST_PROTOCOL: 140e. is selected.

     The 'file' argument must have a write() method that accepts a
     single bytes argument.  It can thus be an on-disk file opened for
     binary writing, an *note io.BytesIO: e46. instance, or any other
     custom object that meets this interface.

     If 'fix_imports' is true and 'protocol' is less than 3, pickle will
     try to map the new Python 3 names to the old module names used in
     Python 2, so that the pickle data stream is readable with Python 2.

     If 'buffer_callback' is ‘None’ (the default), buffer views are
     serialized into 'file' as part of the pickle stream.

     If 'buffer_callback' is not ‘None’, then it can be called any
     number of times with a buffer view.  If the callback returns a
     false value (such as ‘None’), the given buffer is *note
     out-of-band: 2774.; otherwise the buffer is serialized in-band,
     i.e.  inside the pickle stream.

     It is an error if 'buffer_callback' is not ‘None’ and 'protocol' is
     ‘None’ or smaller than 5.

     在 3.8 版的變更: 新增 'buffer_callback' 引數。

      -- 方法: dump (obj)

          Write the pickled representation of 'obj' to the open file
          object given in the constructor.

      -- 方法: persistent_id (obj)

          Do nothing by default.  This exists so a subclass can override
          it.

          If *note persistent_id(): 159d. returns ‘None’, 'obj' is
          pickled as usual.  Any other value causes *note Pickler: 9c2.
          to emit the returned value as a persistent ID for 'obj'.  The
          meaning of this persistent ID should be defined by *note
          Unpickler.persistent_load(): 159e.  Note that the value
          returned by *note persistent_id(): 159d. cannot itself have a
          persistent ID.

          關於細節與用法範例請見 *note Persistence of External Objects:
          2775.。

          在 3.13 版的變更: Add the default implementation of this
          method in the C implementation of ‘Pickler’.

      -- 屬性: dispatch_table

          A pickler object's dispatch table is a registry of 'reduction
          functions' of the kind which can be declared using *note
          copyreg.pickle(): 2776.  It is a mapping whose keys are
          classes and whose values are reduction functions.  A reduction
          function takes a single argument of the associated class and
          should conform to the same interface as a *note __reduce__():
          977. method.

          By default, a pickler object will not have a *note
          dispatch_table: 10ba. attribute, and it will instead use the
          global dispatch table managed by the *note copyreg: 1f.
          module.  However, to customize the pickling for a specific
          pickler object one can set the *note dispatch_table: 10ba.
          attribute to a dict-like object.  Alternatively, if a subclass
          of *note Pickler: 9c2. has a *note dispatch_table: 10ba.
          attribute then this will be used as the default dispatch table
          for instances of that class.

          關於用法範例請見 *note Dispatch Tables: 2777.。

          在 3.3 版被加入.

      -- 方法: reducer_override (obj)

          Special reducer that can be defined in *note Pickler: 9c2.
          subclasses.  This method has priority over any reducer in the
          *note dispatch_table: 10ba.  It should conform to the same
          interface as a *note __reduce__(): 977. method, and can
          optionally return *note NotImplemented: 776. to fallback on
          *note dispatch_table: 10ba.-registered reducers to pickle
          ‘obj’.

          For a detailed example, see *note Custom Reduction for Types,
          Functions, and Other Objects: 2778.

          在 3.8 版被加入.

      -- 屬性: fast

          Deprecated.  Enable fast mode if set to a true value.  The
          fast mode disables the usage of memo, therefore speeding the
          pickling process by not generating superfluous PUT opcodes.
          It should not be used with self-referential objects, doing
          otherwise will cause *note Pickler: 9c2. to recurse
          infinitely.

          Use *note pickletools.optimize(): 277a. if you need more
          compact pickles.

 -- 類別: pickle.Unpickler (file, *, fix_imports=True, encoding='ASCII',
          errors='strict', buffers=None)

     This takes a binary file for reading a pickle data stream.

     The protocol version of the pickle is detected automatically, so no
     protocol argument is needed.

     The argument 'file' must have three methods, a read() method that
     takes an integer argument, a readinto() method that takes a buffer
     argument and a readline() method that requires no arguments, as in
     the *note io.BufferedIOBase: 63a. interface.  Thus 'file' can be an
     on-disk file opened for binary reading, an *note io.BytesIO: e46.
     object, or any other custom object that meets this interface.

     The optional arguments 'fix_imports', 'encoding' and 'errors' are
     used to control compatibility support for pickle stream generated
     by Python 2.  If 'fix_imports' is true, pickle will try to map the
     old Python 2 names to the new names used in Python 3.  The
     'encoding' and 'errors' tell pickle how to decode 8-bit string
     instances pickled by Python 2; these default to 'ASCII' and
     'strict', respectively.  The 'encoding' can be 'bytes' to read
     these 8-bit string instances as bytes objects.  Using
     ‘encoding='latin1'’ is required for unpickling NumPy arrays and
     instances of *note datetime: 1b0, *note date: 1b1. and *note time:
     1b2. pickled by Python 2.

     If 'buffers' is ‘None’ (the default), then all data necessary for
     deserialization must be contained in the pickle stream.  This means
     that the 'buffer_callback' argument was ‘None’ when a *note
     Pickler: 9c2. was instantiated (or when *note dump(): 276f. or
     *note dumps(): 140d. was called).

     If 'buffers' is not ‘None’, it should be an iterable of
     buffer-enabled objects that is consumed each time the pickle stream
     references an *note out-of-band: 2774. buffer view.  Such buffers
     have been given in order to the 'buffer_callback' of a Pickler
     object.

     在 3.8 版的變更: 新增 'buffer' 引數。

      -- 方法: load ()

          Read the pickled representation of an object from the open
          file object given in the constructor, and return the
          reconstituted object hierarchy specified therein.  Bytes past
          the pickled representation of the object are ignored.

      -- 方法: persistent_load (pid)

          Raise an *note UnpicklingError: 2773. by default.

          If defined, *note persistent_load(): 159e. should return the
          object specified by the persistent ID 'pid'.  If an invalid
          persistent ID is encountered, an *note UnpicklingError: 2773.
          should be raised.

          關於細節與用法範例請見 *note Persistence of External Objects:
          2775.。

          在 3.13 版的變更: Add the default implementation of this
          method in the C implementation of ‘Unpickler’.

      -- 方法: find_class (module, name)

          Import 'module' if necessary and return the object called
          'name' from it, where the 'module' and 'name' arguments are
          *note str: 3f2. objects.  Note, unlike its name suggests,
          *note find_class(): 277c. is also used for finding functions.

          Subclasses may override this to gain control over what type of
          objects and how they can be loaded, potentially reducing
          security risks.  Refer to *note Restricting Globals: 277d. for
          details.

          引發一個附帶引數 ‘module’、‘name’ 的*note 稽核事件: 17bd.
          ‘pickle.find_class’。

 -- 類別: pickle.PickleBuffer (buffer)

     A wrapper for a buffer representing picklable data.  'buffer' must
     be a *note buffer-providing: 367. object, such as a *note
     bytes-like object: cd4. or a N-dimensional array.

     *note PickleBuffer: 16fd. is itself a buffer provider, therefore it
     is possible to pass it to other APIs expecting a buffer-providing
     object, such as *note memoryview: 40f.

     *note PickleBuffer: 16fd. objects can only be serialized using
     pickle protocol 5 or higher.  They are eligible for *note
     out-of-band serialization: 2774.

     在 3.8 版被加入.

      -- 方法: raw ()

          Return a *note memoryview: 40f. of the memory area underlying
          this buffer.  The returned object is a one-dimensional,
          C-contiguous memoryview with format ‘B’ (unsigned bytes).
          *note BufferError: 1729. is raised if the buffer is neither C-
          nor Fortran-contiguous.

      -- 方法: release ()

          Release the underlying buffer exposed by the PickleBuffer
          object.


File: python.info,  Node: What can be pickled and unpickled?,  Next: Pickling Class Instances,  Prev: 模組介面,  Up: pickle --- Python 物件序列化

5.12.1.6 What can be pickled and unpickled?
...........................................

The following types can be pickled:

   * built-in constants (‘None’, ‘True’, ‘False’, ‘Ellipsis’, and *note
     NotImplemented: 776.);

   * integers, floating-point numbers, complex numbers;

   * strings, bytes, bytearrays;

   * tuples, lists, sets, and dictionaries containing only picklable
     objects;

   * functions (built-in and user-defined) accessible from the top level
     of a module (using *note def: 13c5, not *note lambda: 1234.);

   * classes accessible from the top level of a module;

   * instances of such classes whose the result of calling *note
     __getstate__(): 57c. is picklable (see section *note Pickling Class
     Instances: 276a. for details).

Attempts to pickle unpicklable objects will raise the *note
PicklingError: 2771. exception; when this happens, an unspecified number
of bytes may have already been written to the underlying file.  Trying
to pickle a highly recursive data structure may exceed the maximum
recursion depth, a *note RecursionError: d12. will be raised in this
case.  You can carefully raise this limit with *note
sys.setrecursionlimit(): 46a.

Note that functions (built-in and user-defined) are pickled by fully
*note qualified name: 1843, not by value.  (1)  This means that only the
function name is pickled, along with the name of the containing module
and classes.  Neither the function's code, nor any of its function
attributes are pickled.  Thus the defining module must be importable in
the unpickling environment, and the module must contain the named
object, otherwise an exception will be raised.  (2)

Similarly, classes are pickled by fully qualified name, so the same
restrictions in the unpickling environment apply.  Note that none of the
class's code or data is pickled, so in the following example the class
attribute ‘attr’ is not restored in the unpickling environment:

     class Foo:
         attr = 'A class attribute'

     picklestring = pickle.dumps(Foo)

These restrictions are why picklable functions and classes must be
defined at the top level of a module.

Similarly, when class instances are pickled, their class's code and data
are not pickled along with them.  Only the instance data are pickled.
This is done on purpose, so you can fix bugs in a class or add methods
to the class and still load objects that were created with an earlier
version of the class.  If you plan to have long-lived objects that will
see many versions of a class, it may be worthwhile to put a version
number in the objects so that suitable conversions can be made by the
class's *note __setstate__(): 140f. method.

   ---------- Footnotes ----------

   (1) This is why *note lambda: 1234. functions cannot be pickled: all
‘lambda’ functions share the same name: ‘<lambda>’.

   (2) The exception raised will likely be an *note ImportError: 352. or
an *note AttributeError: 2f6. but it could be something else.


File: python.info,  Node: Pickling Class Instances,  Next: Custom Reduction for Types Functions and Other Objects,  Prev: What can be pickled and unpickled?,  Up: pickle --- Python 物件序列化

5.12.1.7 Pickling Class Instances
.................................

In this section, we describe the general mechanisms available to you to
define, customize, and control how class instances are pickled and
unpickled.

In most cases, no additional code is needed to make instances picklable.
By default, pickle will retrieve the class and the attributes of an
instance via introspection.  When a class instance is unpickled, its
*note __init__(): 655. method is usually 'not' invoked.  The default
behaviour first creates an uninitialized instance and then restores the
saved attributes.  The following code shows an implementation of this
behaviour:

     def save(obj):
         return (obj.__class__, obj.__dict__)

     def restore(cls, attributes):
         obj = cls.__new__(cls)
         obj.__dict__.update(attributes)
         return obj

Classes can alter the default behaviour by providing one or several
special methods:

 -- 方法: object.__getnewargs_ex__ ()

     In protocols 2 and newer, classes that implements the *note
     __getnewargs_ex__(): 2782. method can dictate the values passed to
     the *note __new__(): 526. method upon unpickling.  The method must
     return a pair ‘(args, kwargs)’ where 'args' is a tuple of
     positional arguments and 'kwargs' a dictionary of named arguments
     for constructing the object.  Those will be passed to the *note
     __new__(): 526. method upon unpickling.

     You should implement this method if the *note __new__(): 526.
     method of your class requires keyword-only arguments.  Otherwise,
     it is recommended for compatibility to implement *note
     __getnewargs__(): 1410.

     在 3.6 版的變更: *note __getnewargs_ex__(): 2782. is now used in
     protocols 2 and 3.

 -- 方法: object.__getnewargs__ ()

     This method serves a similar purpose as *note __getnewargs_ex__():
     2782, but supports only positional arguments.  It must return a
     tuple of arguments ‘args’ which will be passed to the *note
     __new__(): 526. method upon unpickling.

     *note __getnewargs__(): 1410. will not be called if *note
     __getnewargs_ex__(): 2782. is defined.

     在 3.6 版的變更: Before Python 3.6, *note __getnewargs__(): 1410.
     was called instead of *note __getnewargs_ex__(): 2782. in protocols
     2 and 3.

 -- 方法: object.__getstate__ ()

     Classes can further influence how their instances are pickled by
     overriding the method *note __getstate__(): 57c.  It is called and
     the returned object is pickled as the contents for the instance,
     instead of a default state.  There are several cases:

        * For a class that has no instance *note __dict__: c04. and no
          *note __slots__: 1458, the default state is ‘None’.

        * For a class that has an instance *note __dict__: c04. and no
          *note __slots__: 1458, the default state is ‘self.__dict__’.

        * For a class that has an instance *note __dict__: c04. and
          *note __slots__: 1458, the default state is a tuple consisting
          of two dictionaries: ‘self.__dict__’, and a dictionary mapping
          slot names to slot values.  Only slots that have a value are
          included in the latter.

        * For a class that has *note __slots__: 1458. and no instance
          *note __dict__: c04, the default state is a tuple whose first
          item is ‘None’ and whose second item is a dictionary mapping
          slot names to slot values described in the previous bullet.

     在 3.11 版的變更: Added the default implementation of the
     ‘__getstate__()’ method in the *note object: a2f. class.

 -- 方法: object.__setstate__ (state)

     Upon unpickling, if the class defines *note __setstate__(): 140f,
     it is called with the unpickled state.  In that case, there is no
     requirement for the state object to be a dictionary.  Otherwise,
     the pickled state must be a dictionary and its items are assigned
     to the new instance's dictionary.

          備註: If *note __reduce__(): 977. returns a state with value
          ‘None’ at pickling, the *note __setstate__(): 140f. method
          will not be called upon unpickling.

Refer to the section *note Handling Stateful Objects: 2783. for more
information about how to use the methods *note __getstate__(): 57c. and
*note __setstate__(): 140f.

     備註: At unpickling time, some methods like *note __getattr__():
     47a, *note __getattribute__(): b79, or *note __setattr__(): 1e05.
     may be called upon the instance.  In case those methods rely on
     some internal invariant being true, the type should implement *note
     __new__(): 526. to establish such an invariant, as *note
     __init__(): 655. is not called when unpickling an instance.

As we shall see, pickle does not use directly the methods described
above.  In fact, these methods are part of the copy protocol which
implements the *note __reduce__(): 977. special method.  The copy
protocol provides a unified interface for retrieving the data necessary
for pickling and copying objects.  (1)

Although powerful, implementing *note __reduce__(): 977. directly in
your classes is error prone.  For this reason, class designers should
use the high-level interface (i.e., *note __getnewargs_ex__(): 2782,
*note __getstate__(): 57c. and *note __setstate__(): 140f.) whenever
possible.  We will show, however, cases where using ‘__reduce__()’ is
the only option or leads to more efficient pickling or both.

 -- 方法: object.__reduce__ ()

     The interface is currently defined as follows.  The *note
     __reduce__(): 977. method takes no argument and shall return either
     a string or preferably a tuple (the returned object is often
     referred to as the "reduce value").

     If a string is returned, the string should be interpreted as the
     name of a global variable.  It should be the object's local name
     relative to its module; the pickle module searches the module
     namespace to determine the object's module.  This behaviour is
     typically useful for singletons.

     When a tuple is returned, it must be between two and six items
     long.  Optional items can either be omitted, or ‘None’ can be
     provided as their value.  The semantics of each item are in order:

        * A callable object that will be called to create the initial
          version of the object.

        * A tuple of arguments for the callable object.  An empty tuple
          must be given if the callable does not accept any argument.

        * Optionally, the object's state, which will be passed to the
          object's *note __setstate__(): 140f. method as previously
          described.  If the object has no such method then, the value
          must be a dictionary and it will be added to the object's
          *note __dict__: c04. attribute.

        * Optionally, an iterator (and not a sequence) yielding
          successive items.  These items will be appended to the object
          either using ‘obj.append(item)’ or, in batch, using
          ‘obj.extend(list_of_items)’.  This is primarily used for list
          subclasses, but may be used by other classes as long as they
          have *note append and extend methods: 2086. with the
          appropriate signature.  (Whether ‘append()’ or ‘extend()’ is
          used depends on which pickle protocol version is used as well
          as the number of items to append, so both must be supported.)

        * Optionally, an iterator (not a sequence) yielding successive
          key-value pairs.  These items will be stored to the object
          using ‘obj[key] = value’.  This is primarily used for
          dictionary subclasses, but may be used by other classes as
          long as they implement *note __setitem__(): 1434.

        * Optionally, a callable with a ‘(obj, state)’ signature.  This
          callable allows the user to programmatically control the
          state-updating behavior of a specific object, instead of using
          ‘obj’'s static *note __setstate__(): 140f. method.  If not
          ‘None’, this callable will have priority over ‘obj’'s *note
          __setstate__(): 140f.

          在 3.8 版被加入: The optional sixth tuple item, ‘(obj,
          state)’, was added.

 -- 方法: object.__reduce_ex__ (protocol)

     Alternatively, a *note __reduce_ex__(): 15ef. method may be
     defined.  The only difference is this method should take a single
     integer argument, the protocol version.  When defined, pickle will
     prefer it over the *note __reduce__(): 977. method.  In addition,
     *note __reduce__(): 977. automatically becomes a synonym for the
     extended version.  The main use for this method is to provide
     backwards-compatible reduce values for older Python releases.

* Menu:

* Persistence of External Objects::
* Dispatch Tables::
* Handling Stateful Objects::

   ---------- Footnotes ----------

   (1) The *note copy: 1e. module uses this protocol for shallow and
deep copying operations.


File: python.info,  Node: Persistence of External Objects,  Next: Dispatch Tables,  Up: Pickling Class Instances

5.12.1.8 Persistence of External Objects
........................................

For the benefit of object persistence, the *note pickle: 95. module
supports the notion of a reference to an object outside the pickled data
stream.  Such objects are referenced by a persistent ID, which should be
either a string of alphanumeric characters (for protocol 0) (1) or just
an arbitrary object (for any newer protocol).

The resolution of such persistent IDs is not defined by the *note
pickle: 95. module; it will delegate this resolution to the user-defined
methods on the pickler and unpickler, *note persistent_id(): 159d. and
*note persistent_load(): 159e. respectively.

To pickle objects that have an external persistent ID, the pickler must
have a custom *note persistent_id(): 159d. method that takes an object
as an argument and returns either ‘None’ or the persistent ID for that
object.  When ‘None’ is returned, the pickler simply pickles the object
as normal.  When a persistent ID string is returned, the pickler will
pickle that object, along with a marker so that the unpickler will
recognize it as a persistent ID.

To unpickle external objects, the unpickler must have a custom *note
persistent_load(): 159e. method that takes a persistent ID object and
returns the referenced object.

Here is a comprehensive example presenting how persistent ID can be used
to pickle external objects by reference.

     # Simple example presenting how persistent ID can be used to pickle
     # external objects by reference.

     import pickle
     import sqlite3
     from collections import namedtuple

     # Simple class representing a record in our database.
     MemoRecord = namedtuple("MemoRecord", "key, task")

     class DBPickler(pickle.Pickler):

         def persistent_id(self, obj):
             # Instead of pickling MemoRecord as a regular class instance, we emit a
             # persistent ID.
             if isinstance(obj, MemoRecord):
                 # Here, our persistent ID is simply a tuple, containing a tag and a
                 # key, which refers to a specific record in the database.
                 return ("MemoRecord", obj.key)
             else:
                 # If obj does not have a persistent ID, return None. This means obj
                 # needs to be pickled as usual.
                 return None


     class DBUnpickler(pickle.Unpickler):

         def __init__(self, file, connection):
             super().__init__(file)
             self.connection = connection

         def persistent_load(self, pid):
             # This method is invoked whenever a persistent ID is encountered.
             # Here, pid is the tuple returned by DBPickler.
             cursor = self.connection.cursor()
             type_tag, key_id = pid
             if type_tag == "MemoRecord":
                 # Fetch the referenced record from the database and return it.
                 cursor.execute("SELECT * FROM memos WHERE key=?", (str(key_id),))
                 key, task = cursor.fetchone()
                 return MemoRecord(key, task)
             else:
                 # Always raises an error if you cannot return the correct object.
                 # Otherwise, the unpickler will think None is the object referenced
                 # by the persistent ID.
                 raise pickle.UnpicklingError("unsupported persistent object")


     def main():
         import io
         import pprint

         # Initialize and populate our database.
         conn = sqlite3.connect(":memory:")
         cursor = conn.cursor()
         cursor.execute("CREATE TABLE memos(key INTEGER PRIMARY KEY, task TEXT)")
         tasks = (
             'give food to fish',
             'prepare group meeting',
             'fight with a zebra',
             )
         for task in tasks:
             cursor.execute("INSERT INTO memos VALUES(NULL, ?)", (task,))

         # Fetch the records to be pickled.
         cursor.execute("SELECT * FROM memos")
         memos = [MemoRecord(key, task) for key, task in cursor]
         # Save the records using our custom DBPickler.
         file = io.BytesIO()
         DBPickler(file).dump(memos)

         print("Pickled records:")
         pprint.pprint(memos)

         # Update a record, just for good measure.
         cursor.execute("UPDATE memos SET task='learn italian' WHERE key=1")

         # Load the records from the pickle data stream.
         file.seek(0)
         memos = DBUnpickler(file, conn).load()

         print("Unpickled records:")
         pprint.pprint(memos)


     if __name__ == '__main__':
         main()

   ---------- Footnotes ----------

   (1) The limitation on alphanumeric characters is due to the fact that
persistent IDs in protocol 0 are delimited by the newline character.
Therefore if any kind of newline characters occurs in persistent IDs,
the resulting pickled data will become unreadable.


File: python.info,  Node: Dispatch Tables,  Next: Handling Stateful Objects,  Prev: Persistence of External Objects,  Up: Pickling Class Instances

5.12.1.9 Dispatch Tables
........................

If one wants to customize pickling of some classes without disturbing
any other code which depends on pickling, then one can create a pickler
with a private dispatch table.

The global dispatch table managed by the *note copyreg: 1f. module is
available as ‘copyreg.dispatch_table’.  Therefore, one may choose to use
a modified copy of ‘copyreg.dispatch_table’ as a private dispatch table.

舉例來說：

     f = io.BytesIO()
     p = pickle.Pickler(f)
     p.dispatch_table = copyreg.dispatch_table.copy()
     p.dispatch_table[SomeClass] = reduce_SomeClass

creates an instance of *note pickle.Pickler: 9c2. with a private
dispatch table which handles the ‘SomeClass’ class specially.
Alternatively, the code

     class MyPickler(pickle.Pickler):
         dispatch_table = copyreg.dispatch_table.copy()
         dispatch_table[SomeClass] = reduce_SomeClass
     f = io.BytesIO()
     p = MyPickler(f)

does the same but all instances of ‘MyPickler’ will by default share the
private dispatch table.  On the other hand, the code

     copyreg.pickle(SomeClass, reduce_SomeClass)
     f = io.BytesIO()
     p = pickle.Pickler(f)

modifies the global dispatch table shared by all users of the *note
copyreg: 1f. module.


File: python.info,  Node: Handling Stateful Objects,  Prev: Dispatch Tables,  Up: Pickling Class Instances

5.12.1.10 Handling Stateful Objects
...................................

Here's an example that shows how to modify pickling behavior for a
class.  The ‘TextReader’ class below opens a text file, and returns the
line number and line contents each time its ‘readline()’ method is
called.  If a ‘TextReader’ instance is pickled, all attributes 'except'
the file object member are saved.  When the instance is unpickled, the
file is reopened, and reading resumes from the last location.  The
‘__setstate__()’ and ‘__getstate__()’ methods are used to implement this
behavior.

     class TextReader:
         """Print and number lines in a text file."""

         def __init__(self, filename):
             self.filename = filename
             self.file = open(filename)
             self.lineno = 0

         def readline(self):
             self.lineno += 1
             line = self.file.readline()
             if not line:
                 return None
             if line.endswith('\n'):
                 line = line[:-1]
             return "%i: %s" % (self.lineno, line)

         def __getstate__(self):
             # Copy the object's state from self.__dict__ which contains
             # all our instance attributes. Always use the dict.copy()
             # method to avoid modifying the original state.
             state = self.__dict__.copy()
             # Remove the unpicklable entries.
             del state['file']
             return state

         def __setstate__(self, state):
             # Restore instance attributes (i.e., filename and lineno).
             self.__dict__.update(state)
             # Restore the previously opened file's state. To do so, we need to
             # reopen it and read from it until the line count is restored.
             file = open(self.filename)
             for _ in range(self.lineno):
                 file.readline()
             # Finally, save the file.
             self.file = file

A sample usage might be something like this:

     >>> reader = TextReader("hello.txt")
     >>> reader.readline()
     '1: Hello world!'
     >>> reader.readline()
     '2: I am line number two.'
     >>> new_reader = pickle.loads(pickle.dumps(reader))
     >>> new_reader.readline()
     '3: Goodbye!'


File: python.info,  Node: Custom Reduction for Types Functions and Other Objects,  Next: Out-of-band Buffers,  Prev: Pickling Class Instances,  Up: pickle --- Python 物件序列化

5.12.1.11 Custom Reduction for Types, Functions, and Other Objects
..................................................................

在 3.8 版被加入.

Sometimes, *note dispatch_table: 10ba. may not be flexible enough.  In
particular we may want to customize pickling based on another criterion
than the object's type, or we may want to customize the pickling of
functions and classes.

For those cases, it is possible to subclass from the *note Pickler: 9c2.
class and implement a *note reducer_override(): 9c3. method.  This
method can return an arbitrary reduction tuple (see *note __reduce__():
977.).  It can alternatively return *note NotImplemented: 776. to
fallback to the traditional behavior.

If both the *note dispatch_table: 10ba. and *note reducer_override():
9c3. are defined, then *note reducer_override(): 9c3. method takes
priority.

     備註: For performance reasons, *note reducer_override(): 9c3. may
     not be called for the following objects: ‘None’, ‘True’, ‘False’,
     and exact instances of *note int: 23c, *note float: 2c8, *note
     bytes: 1a5, *note str: 3f2, *note dict: 23b, *note set: 57d, *note
     frozenset: 57e, *note list: 5b6. and *note tuple: 322.

Here is a simple example where we allow pickling and reconstructing a
given class:

     import io
     import pickle

     class MyClass:
         my_attribute = 1

     class MyPickler(pickle.Pickler):
         def reducer_override(self, obj):
             """Custom reducer for MyClass."""
             if getattr(obj, "__name__", None) == "MyClass":
                 return type, (obj.__name__, obj.__bases__,
                               {'my_attribute': obj.my_attribute})
             else:
                 # For any other object, fallback to usual reduction
                 return NotImplemented

     f = io.BytesIO()
     p = MyPickler(f)
     p.dump(MyClass)

     del MyClass

     unpickled_class = pickle.loads(f.getvalue())

     assert isinstance(unpickled_class, type)
     assert unpickled_class.__name__ == "MyClass"
     assert unpickled_class.my_attribute == 1


File: python.info,  Node: Out-of-band Buffers,  Next: Restricting Globals,  Prev: Custom Reduction for Types Functions and Other Objects,  Up: pickle --- Python 物件序列化

5.12.1.12 Out-of-band Buffers
.............................

在 3.8 版被加入.

In some contexts, the *note pickle: 95. module is used to transfer
massive amounts of data.  Therefore, it can be important to minimize the
number of memory copies, to preserve performance and resource
consumption.  However, normal operation of the *note pickle: 95. module,
as it transforms a graph-like structure of objects into a sequential
stream of bytes, intrinsically involves copying data to and from the
pickle stream.

This constraint can be eschewed if both the 'provider' (the
implementation of the object types to be transferred) and the 'consumer'
(the implementation of the communications system) support the
out-of-band transfer facilities provided by pickle protocol 5 and
higher.

* Menu:

* Provider API::
* Consumer API::
* 範例: 範例<8>.


File: python.info,  Node: Provider API,  Next: Consumer API,  Up: Out-of-band Buffers

5.12.1.13 Provider API
......................

The large data objects to be pickled must implement a *note
__reduce_ex__(): 15ef. method specialized for protocol 5 and higher,
which returns a *note PickleBuffer: 16fd. instance (instead of e.g.  a
*note bytes: 1a5. object) for any large data.

A *note PickleBuffer: 16fd. object 'signals' that the underlying buffer
is eligible for out-of-band data transfer.  Those objects remain
compatible with normal usage of the *note pickle: 95. module.  However,
consumers can also opt-in to tell *note pickle: 95. that they will
handle those buffers by themselves.


File: python.info,  Node: Consumer API,  Next: 範例<8>,  Prev: Provider API,  Up: Out-of-band Buffers

5.12.1.14 Consumer API
......................

A communications system can enable custom handling of the *note
PickleBuffer: 16fd. objects generated when serializing an object graph.

On the sending side, it needs to pass a 'buffer_callback' argument to
*note Pickler: 9c2. (or to the *note dump(): 276f. or *note dumps():
140d. function), which will be called with each *note PickleBuffer:
16fd. generated while pickling the object graph.  Buffers accumulated by
the 'buffer_callback' will not see their data copied into the pickle
stream, only a cheap marker will be inserted.

On the receiving side, it needs to pass a 'buffers' argument to *note
Unpickler: 159f. (or to the *note load(): cb7. or *note loads(): cb8.
function), which is an iterable of the buffers which were passed to
'buffer_callback'.  That iterable should produce buffers in the same
order as they were passed to 'buffer_callback'.  Those buffers will
provide the data expected by the reconstructors of the objects whose
pickling produced the original *note PickleBuffer: 16fd. objects.

Between the sending side and the receiving side, the communications
system is free to implement its own transfer mechanism for out-of-band
buffers.  Potential optimizations include the use of shared memory or
datatype-dependent compression.


File: python.info,  Node: 範例<8>,  Prev: Consumer API,  Up: Out-of-band Buffers

5.12.1.15 範例
..............

Here is a trivial example where we implement a *note bytearray: 4e3.
subclass able to participate in out-of-band buffer pickling:

     class ZeroCopyByteArray(bytearray):

         def __reduce_ex__(self, protocol):
             if protocol >= 5:
                 return type(self)._reconstruct, (PickleBuffer(self),), None
             else:
                 # PickleBuffer is forbidden with pickle protocols <= 4.
                 return type(self)._reconstruct, (bytearray(self),)

         @classmethod
         def _reconstruct(cls, obj):
             with memoryview(obj) as m:
                 # Get a handle over the original buffer object
                 obj = m.obj
                 if type(obj) is cls:
                     # Original buffer object is a ZeroCopyByteArray, return it
                     # as-is.
                     return obj
                 else:
                     return cls(obj)

The reconstructor (the ‘_reconstruct’ class method) returns the buffer's
providing object if it has the right type.  This is an easy way to
simulate zero-copy behaviour on this toy example.

On the consumer side, we can pickle those objects the usual way, which
when unserialized will give us a copy of the original object:

     b = ZeroCopyByteArray(b"abc")
     data = pickle.dumps(b, protocol=5)
     new_b = pickle.loads(data)
     print(b == new_b)  # True
     print(b is new_b)  # False: a copy was made

But if we pass a 'buffer_callback' and then give back the accumulated
buffers when unserializing, we are able to get back the original object:

     b = ZeroCopyByteArray(b"abc")
     buffers = []
     data = pickle.dumps(b, protocol=5, buffer_callback=buffers.append)
     new_b = pickle.loads(data, buffers=buffers)
     print(b == new_b)  # True
     print(b is new_b)  # True: no copy was made

This example is limited by the fact that *note bytearray: 4e3. allocates
its own memory: you cannot create a *note bytearray: 4e3. instance that
is backed by another object's memory.  However, third-party datatypes
such as NumPy arrays do not have this limitation, and allow use of
zero-copy pickling (or making as few copies as possible) when
transferring between distinct processes or systems.

也參考
......

PEP 574(1) - Pickle protocol 5 with out-of-band data

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0574/


File: python.info,  Node: Restricting Globals,  Next: Performance<2>,  Prev: Out-of-band Buffers,  Up: pickle --- Python 物件序列化

5.12.1.16 Restricting Globals
.............................

By default, unpickling will import any class or function that it finds
in the pickle data.  For many applications, this behaviour is
unacceptable as it permits the unpickler to import and invoke arbitrary
code.  Just consider what this hand-crafted pickle data stream does when
loaded:

     >>> import pickle
     >>> pickle.loads(b"cos\nsystem\n(S'echo hello world'\ntR.")
     hello world
     0

In this example, the unpickler imports the *note os.system(): 13c8.
function and then apply the string argument "echo hello world".
Although this example is inoffensive, it is not difficult to imagine one
that could damage your system.

For this reason, you may want to control what gets unpickled by
customizing *note Unpickler.find_class(): 277c.  Unlike its name
suggests, *note Unpickler.find_class(): 277c. is called whenever a
global (i.e., a class or a function) is requested.  Thus it is possible
to either completely forbid globals or restrict them to a safe subset.

Here is an example of an unpickler allowing only few safe classes from
the *note builtins: e. module to be loaded:

     import builtins
     import io
     import pickle

     safe_builtins = {
         'range',
         'complex',
         'set',
         'frozenset',
         'slice',
     }

     class RestrictedUnpickler(pickle.Unpickler):

         def find_class(self, module, name):
             # Only allow safe classes from builtins.
             if module == "builtins" and name in safe_builtins:
                 return getattr(builtins, name)
             # Forbid everything else.
             raise pickle.UnpicklingError("global '%s.%s' is forbidden" %
                                          (module, name))

     def restricted_loads(s):
         """Helper function analogous to pickle.loads()."""
         return RestrictedUnpickler(io.BytesIO(s)).load()

A sample usage of our unpickler working as intended:

     >>> restricted_loads(pickle.dumps([1, 2, range(15)]))
     [1, 2, range(0, 15)]
     >>> restricted_loads(b"cos\nsystem\n(S'echo hello world'\ntR.")
     Traceback (most recent call last):
       ...
     pickle.UnpicklingError: global 'os.system' is forbidden
     >>> restricted_loads(b'cbuiltins\neval\n'
     ...                  b'(S\'getattr(__import__("os"), "system")'
     ...                  b'("echo hello world")\'\ntR.')
     Traceback (most recent call last):
       ...
     pickle.UnpicklingError: global 'builtins.eval' is forbidden

As our examples shows, you have to be careful with what you allow to be
unpickled.  Therefore if security is a concern, you may want to consider
alternatives such as the marshalling API in *note xmlrpc.client: 114. or
third-party solutions.


File: python.info,  Node: Performance<2>,  Next: 範例<9>,  Prev: Restricting Globals,  Up: pickle --- Python 物件序列化

5.12.1.17 Performance
.....................

Recent versions of the pickle protocol (from protocol 2 and upwards)
feature efficient binary encodings for several common features and
built-in types.  Also, the *note pickle: 95. module has a transparent
optimizer written in C.


File: python.info,  Node: 範例<9>,  Prev: Performance<2>,  Up: pickle --- Python 物件序列化

5.12.1.18 範例
..............

For the simplest code, use the *note dump(): 276f. and *note load():
cb7. functions.

     import pickle

     # An arbitrary collection of objects supported by pickle.
     data = {
         'a': [1, 2.0, 3+4j],
         'b': ("character string", b"byte string"),
         'c': {None, True, False}
     }

     with open('data.pickle', 'wb') as f:
         # Pickle the 'data' dictionary using the highest protocol available.
         pickle.dump(data, f, pickle.HIGHEST_PROTOCOL)

The following example reads the resulting pickled data.

     import pickle

     with open('data.pickle', 'rb') as f:
         # The protocol version used is detected automatically, so we do not
         # have to specify it.
         data = pickle.load(f)

也參考
......

*note copyreg: 1f. 模組

     Pickle interface constructor registration for extension types.

*note pickletools: 96. 模組

     Tools for working with and analyzing pickled data.

*note shelve: b1. 模組

     Indexed databases of objects; uses *note pickle: 95.

*note copy: 1e. 模組

     Shallow and deep object copying.

*note marshal: 80. 模組

     High-performance serialization of built-in types.

註解
....


File: python.info,  Node: copyreg --- 註冊 pickle 支援函式,  Next: shelve --- Python object persistence,  Prev: pickle --- Python 物件序列化,  Up: 資料持久性 Data Persistence

5.12.2 ‘copyreg’ -- 註冊 ‘pickle’ 支援函式
------------------------------------------

'原始碼：'Lib/copyreg.py(1)

__________________________________________________________________

*note copyreg: 1f. 模組提供了一種用以定義在 pickle 特定物件時使用之函式
的方式。*note pickle: 95. 和 *note copy: 1e. 模組在 pickle/copy 這些物件
時使用這些函式。此模組提供有關非類別物件之建構函式的配置資訊。此類建構函
式可以是工廠函式 (factory function) 或類別實例。

 -- 函式: copyreg.constructor (object)

     宣告 'object' 是一個有效的建構函式。如果 'object' 不可呼叫（因此不
     可作為有效的建構函式），則會引發 *note TypeError: 4dd.。

 -- 函式: copyreg.pickle (type, function, constructor_ob=None)

     宣告 'function' 應該用作 'type' 型別之物件的「歸約 ("reduction")」
     函式。'function' 必須回傳字串或包含 2 到 6 個元素的元組。有關
     'function' 介面的更多詳細資訊，請參閱 *note dispatch_table: 10ba.。

     'constructor_ob' 參數是一個遺留功能，現在已被忽略，但如果要傳遞它的
     話則必須是個可呼叫物件。

     請注意，pickler 物件或 *note pickle.Pickler: 9c2. 子類別的 *note
     dispatch_table: 10ba. 屬性也可用於宣告歸約函式。

* Menu:

* 範例: 範例<10>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/copyreg.py


File: python.info,  Node: 範例<10>,  Up: copyreg --- 註冊 pickle 支援函式

5.12.2.1 範例
.............

下面範例展示如何註冊一個 pickle 函式以及如何使用它：

     >>> import copyreg, copy, pickle
     >>> class C:
     ...     def __init__(self, a):
     ...         self.a = a
     ...
     >>> def pickle_c(c):
     ...     print("pickling a C instance...")
     ...     return C, (c.a,)
     ...
     >>> copyreg.pickle(C, pickle_c)
     >>> c = C(1)
     >>> d = copy.copy(c)
     pickling a C instance...
     >>> p = pickle.dumps(c)
     pickling a C instance...


File: python.info,  Node: shelve --- Python object persistence,  Next: marshal --- 内部 Python 物件序列化,  Prev: copyreg --- 註冊 pickle 支援函式,  Up: 資料持久性 Data Persistence

5.12.3 ‘shelve’ -- Python object persistence
--------------------------------------------

'原始碼：'Lib/shelve.py(1)

__________________________________________________________________

A "shelf" is a persistent, dictionary-like object.  The difference with
"dbm" databases is that the values (not the keys!)  in a shelf can be
essentially arbitrary Python objects -- anything that the *note pickle:
95. module can handle.  This includes most class instances, recursive
data types, and objects containing lots of shared sub-objects.  The keys
are ordinary strings.

 -- 函式: shelve.open (filename, flag='c', protocol=None,
          writeback=False)

     Open a persistent dictionary.  The filename specified is the base
     filename for the underlying database.  As a side-effect, an
     extension may be added to the filename and more than one file may
     be created.  By default, the underlying database file is opened for
     reading and writing.  The optional 'flag' parameter has the same
     interpretation as the 'flag' parameter of *note dbm.open(): ece.

     By default, pickles created with *note pickle.DEFAULT_PROTOCOL:
     7d2. are used to serialize values.  The version of the pickle
     protocol can be specified with the 'protocol' parameter.

     Because of Python semantics, a shelf cannot know when a mutable
     persistent-dictionary entry is modified.  By default modified
     objects are written 'only' when assigned to the shelf (see *note
     範例: 2796.).  If the optional 'writeback' parameter is set to
     ‘True’, all entries accessed are also cached in memory, and written
     back on *note sync(): 2797. and *note close(): 2798.; this can make
     it handier to mutate mutable entries in the persistent dictionary,
     but, if many entries are accessed, it can consume vast amounts of
     memory for the cache, and it can make the close operation very slow
     since all accessed entries are written back (there is no way to
     determine which accessed entries are mutable, nor which ones were
     actually mutated).

     在 3.10 版的變更: *note pickle.DEFAULT_PROTOCOL: 7d2. is now used
     as the default pickle protocol.

     在 3.11 版的變更: Accepts *note path-like object: ac2. for
     filename.

          備註: Do not rely on the shelf being closed automatically;
          always call *note close(): 2798. explicitly when you don't
          need it any more, or use *note shelve.open(): 15fd. as a
          context manager:

               with shelve.open('spam') as db:
                   db['eggs'] = 'eggs'
     警告: Because the *note shelve: b1. module is backed by *note
     pickle: 95, it is insecure to load a shelf from an untrusted
     source.  Like with pickle, loading a shelf can execute arbitrary
     code.

Shelf objects support most of methods and operations supported by
dictionaries (except copying, constructors and operators ‘|’ and ‘|=’).
This eases the transition from dictionary based scripts to those
requiring persistent storage.

Two additional methods are supported:

 -- 方法: Shelf.sync ()

     Write back all entries in the cache if the shelf was opened with
     'writeback' set to *note True: bb4.  Also empty the cache and
     synchronize the persistent dictionary on disk, if feasible.  This
     is called automatically when the shelf is closed with *note
     close(): 2798.

 -- 方法: Shelf.close ()

     Synchronize and close the persistent 'dict' object.  Operations on
     a closed shelf will fail with a *note ValueError: 1e7.

也參考
......

Persistent dictionary recipe(2) with widely supported storage formats
and having the speed of native dictionaries.

* Menu:

* Restrictions::
* 範例: 範例<11>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/shelve.py

   (2) 
https://code.activestate.com/recipes/576642-persistent-dict-with-multiple-standard-file-format/


File: python.info,  Node: Restrictions,  Next: 範例<11>,  Up: shelve --- Python object persistence

5.12.3.1 Restrictions
.....................

   * The choice of which database package will be used (such as *note
     dbm.ndbm: 2c. or *note dbm.gnu: 2b.) depends on which interface is
     available.  Therefore it is not safe to open the database directly
     using *note dbm: 29.  The database is also (unfortunately) subject
     to the limitations of *note dbm: 29, if it is used -- this means
     that (the pickled representation of) the objects stored in the
     database should be fairly small, and in rare cases key collisions
     may cause the database to refuse updates.

   * The *note shelve: b1. module does not support 'concurrent'
     read/write access to shelved objects.  (Multiple simultaneous read
     accesses are safe.)  When a program has a shelf open for writing,
     no other program should have it open for reading or writing.  Unix
     file locking can be used to solve this, but this differs across
     Unix versions and requires knowledge about the database
     implementation used.

   * On macOS *note dbm.ndbm: 2c. can silently corrupt the database file
     on updates, which can cause hard crashes when trying to read from
     the database.

 -- 類別: shelve.Shelf (dict, protocol=None, writeback=False,
          keyencoding='utf-8')

     A subclass of *note collections.abc.MutableMapping: 1048. which
     stores pickled values in the 'dict' object.

     By default, pickles created with *note pickle.DEFAULT_PROTOCOL:
     7d2. are used to serialize values.  The version of the pickle
     protocol can be specified with the 'protocol' parameter.  See the
     *note pickle: 95. documentation for a discussion of the pickle
     protocols.

     If the 'writeback' parameter is ‘True’, the object will hold a
     cache of all entries accessed and write them back to the 'dict' at
     sync and close times.  This allows natural operations on mutable
     entries, but can consume much more memory and make sync and close
     take a long time.

     The 'keyencoding' parameter is the encoding used to encode keys
     before they are used with the underlying dict.

     A *note Shelf: f3d. object can also be used as a context manager,
     in which case it will be automatically closed when the *note with:
     577. block ends.

     在 3.2 版的變更: Added the 'keyencoding' parameter; previously,
     keys were always encoded in UTF-8.

     在 3.4 版的變更: 新增情境管理器的支援。

     在 3.10 版的變更: *note pickle.DEFAULT_PROTOCOL: 7d2. is now used
     as the default pickle protocol.

 -- 類別: shelve.BsdDbShelf (dict, protocol=None, writeback=False,
          keyencoding='utf-8')

     A subclass of *note Shelf: f3d. which exposes ‘first()’, ‘next()’,
     ‘previous()’, ‘last()’ and ‘set_location()’ methods.  These are
     available in the third-party ‘bsddb’ module from pybsddb(1) but not
     in other database modules.  The 'dict' object passed to the
     constructor must support those methods.  This is generally
     accomplished by calling one of ‘bsddb.hashopen()’, ‘bsddb.btopen()’
     or ‘bsddb.rnopen()’.  The optional 'protocol', 'writeback', and
     'keyencoding' parameters have the same interpretation as for the
     *note Shelf: f3d. class.

 -- 類別: shelve.DbfilenameShelf (filename, flag='c', protocol=None,
          writeback=False)

     A subclass of *note Shelf: f3d. which accepts a 'filename' instead
     of a dict-like object.  The underlying file will be opened using
     *note dbm.open(): ece.  By default, the file will be created and
     opened for both read and write.  The optional 'flag' parameter has
     the same interpretation as for the *note open(): 15fd. function.
     The optional 'protocol' and 'writeback' parameters have the same
     interpretation as for the *note Shelf: f3d. class.

   ---------- Footnotes ----------

   (1) https://www.jcea.es/programacion/pybsddb.htm


File: python.info,  Node: 範例<11>,  Prev: Restrictions,  Up: shelve --- Python object persistence

5.12.3.2 範例
.............

To summarize the interface (‘key’ is a string, ‘data’ is an arbitrary
object):

     import shelve

     d = shelve.open(filename)  # open -- file may get suffix added by low-level
                                # library

     d[key] = data              # store data at key (overwrites old data if
                                # using an existing key)
     data = d[key]              # retrieve a COPY of data at key (raise KeyError
                                # if no such key)
     del d[key]                 # delete data stored at key (raises KeyError
                                # if no such key)

     flag = key in d            # true if the key exists
     klist = list(d.keys())     # a list of all existing keys (slow!)

     # as d was opened WITHOUT writeback=True, beware:
     d['xx'] = [0, 1, 2]        # this works as expected, but...
     d['xx'].append(3)          # *this doesn't!* -- d['xx'] is STILL [0, 1, 2]!

     # having opened d without writeback=True, you need to code carefully:
     temp = d['xx']             # extracts the copy
     temp.append(5)             # mutates the copy
     d['xx'] = temp             # stores the copy right back, to persist it

     # or, d=shelve.open(filename,writeback=True) would let you just code
     # d['xx'].append(5) and have it work as expected, BUT it would also
     # consume more memory and make the d.close() operation slower.

     d.close()                  # close it

也參考
......

*note dbm: 29. 模組

     Generic interface to ‘dbm’-style databases.

*note pickle: 95. 模組

     Object serialization used by *note shelve: b1.


File: python.info,  Node: marshal --- 内部 Python 物件序列化,  Next: dbm --- Unix "databases" 的介面,  Prev: shelve --- Python object persistence,  Up: 資料持久性 Data Persistence

5.12.4 ‘marshal’ -- 内部 Python 物件序列化
------------------------------------------

__________________________________________________________________

此 module（模組）包含一個能以二進位制格式來讀寫 Python 值的函式。這種格
式是 Python 專屬但獨立於機器架構的（例如，你可以在一臺 PC 上寫入某個
Python 值，再將檔案傳到一臺 Mac 上並在那裡讀取它）。這種格式的細節是有意
地不在文件上說明的；它可能在不同 Python 版本中被改變（雖然這種情況極少發
生）。(1)

This is not a general "persistence" module.  For general persistence and
transfer of Python objects through RPC calls, see the modules *note
pickle: 95. and *note shelve: b1.  The *note marshal: 80. module exists
mainly to support reading and writing the "pseudo-compiled" code for
Python modules of ‘.pyc’ files.  Therefore, the Python maintainers
reserve the right to modify the marshal format in backward incompatible
ways should the need arise.  The format of code objects is not
compatible between Python versions, even if the version of the format is
the same.  De-serializing a code object in the incorrect Python version
has undefined behavior.  If you're serializing and de-serializing Python
objects, use the *note pickle: 95. module instead - the performance is
comparable, version independence is guaranteed, and pickle supports a
substantially wider range of objects than marshal.

     警告: *note marshal: 80. module 對於錯誤或惡意構建的資料來說是不安
     全的。永遠不要 unmarshal 來自不受信任的或來源未經驗證的資料。

Not all Python object types are supported; in general, only objects
whose value is independent from a particular invocation of Python can be
written and read by this module.  The following types are supported:
booleans, integers, floating-point numbers, complex numbers, strings,
bytes, bytearrays, tuples, lists, sets, frozensets, dictionaries, and
code objects (if 'allow_code' is true), where it should be understood
that tuples, lists, sets, frozensets and dictionaries are only supported
as long as the values contained therein are themselves supported.  The
singletons *note None: 61b, *note Ellipsis: 2062. and *note
StopIteration: ba1. can also be marshalled and unmarshalled.  For format
'version' lower than 3, recursive lists, sets and dictionaries cannot be
written (see below).

有些函式可以讀/寫檔案，還有些函式可以操作類位元組串物件 (bytes-like
object)。

這個 module 定義了以下函式：

 -- 函式: marshal.dump (value, file, version=version, /, *,
          allow_code=True)

     將值寫入被開啟的檔案。值必須為受支援的型別，檔案必須為可寫入的
     *note binary file: 1b8b.。

     If the value has (or contains an object that has) an unsupported
     type, a *note ValueError: 1e7. exception is raised -- but garbage
     data will also be written to the file.  The object will not be
     properly read back by *note load(): 1919.  *note Code objects: 1b6.
     are only supported if 'allow_code' is true.

     'version' 引數指明 ‘dump’ 應該使用的資料格式（見下文）。

     引發一個附帶引數 ‘value’ 與 ‘version’ 的*note 稽核事件 (auditing
     event): 17bd. ‘marshal.dumps’。

     在 3.13 版的變更: Added the 'allow_code' parameter.

 -- 函式: marshal.load (file, /, *, allow_code=True)

     Read one value from the open file and return it.  If no valid value
     is read (e.g.  because the data has a different Python version's
     incompatible marshal format), raise *note EOFError: 126c, *note
     ValueError: 1e7. or *note TypeError: 4dd.  *note Code objects: 1b6.
     are only supported if 'allow_code' is true.  The file must be a
     readable *note binary file: 1b8b.

     引發一個沒有附帶引數的*note 稽核事件: 17bd. ‘marshal.load’。

          備註: 如果透過 *note dump(): 279e. marshal 了一個包含不支援型
          別的物件，*note load(): 1919. 會將不可 marshal 的型別替換為
          ‘None’。

     在 3.10 版的變更: 使用此呼叫為每個程式碼物件引發一個 ‘code.__new__’
     稽核事件。現在它會為整個載入操作引發單個 ‘marshal.load’ 事件。

     在 3.13 版的變更: Added the 'allow_code' parameter.

 -- 函式: marshal.dumps (value, version=version, /, *, allow_code=True)

     Return the bytes object that would be written to a file by
     ‘dump(value, file)’.  The value must be a supported type.  Raise a
     *note ValueError: 1e7. exception if value has (or contains an
     object that has) an unsupported type.  *note Code objects: 1b6. are
     only supported if 'allow_code' is true.

     'version' 引數指明 ‘dumps’ 應當使用的資料型別（見下文）。

     引發一個附帶引數 ‘value’ 與 ‘version’ 的*note 稽核事件 (auditing
     event): 17bd. ‘marshal.dumps’。

     在 3.13 版的變更: Added the 'allow_code' parameter.

 -- 函式: marshal.loads (bytes, /, *, allow_code=True)

     Convert the *note bytes-like object: cd4. to a value.  If no valid
     value is found, raise *note EOFError: 126c, *note ValueError: 1e7.
     or *note TypeError: 4dd.  *note Code objects: 1b6. are only
     supported if 'allow_code' is true.  Extra bytes in the input are
     ignored.

     引發一個附帶引數 ‘bytes’ 的*note 稽核事件: 17bd. ‘marshal.loads’。

     在 3.10 版的變更: 使用此呼叫為每個程式碼物件引發一個 ‘code.__new__’
     稽核事件。現在它會為整個載入操作引發單個 ‘marshal.loads’ 事件。

     在 3.13 版的變更: Added the 'allow_code' parameter.

此外，還定義了以下常數：

 -- 資料: marshal.version

     表示 module 所使用的格式。第 0 版為歷史格式，第 1 版共享了駐留字串
     (interned string)，第 2 版對浮點數使用二進位制格式。第 3 版添加了對
     於物件實例化和遞迴的支援。目前使用的是第 4 版。

註解
....

   ---------- Footnotes ----------

   (1) 此 module 的名稱來源於 Modula-3 (及其他語言) 的設計者所使用的術語
，他們使用 "marshal" 來表示自包含 (self-contained) 形式資料的傳輸。嚴格
來說，將資料從內部形式轉換為外部形式 (例如用於 RPC 緩衝區) 稱為
"marshal"，而其反向過程則稱為 "unmarshal"。


File: python.info,  Node: dbm --- Unix "databases" 的介面,  Next: sqlite3 --- SQLite 資料庫的 DB-API 2 0 介面,  Prev: marshal --- 内部 Python 物件序列化,  Up: 資料持久性 Data Persistence

5.12.5 ‘dbm’ -- Unix "databases" 的介面
---------------------------------------

'原始碼：'Lib/dbm/__init__.py(1)

__________________________________________________________________

*note dbm: 29. is a generic interface to variants of the DBM database:

   * *note dbm.sqlite3: 2d.

   * *note dbm.gnu: 2b.

   * *note dbm.ndbm: 2c.

If none of these modules are installed, the slow-but-simple
implementation in module *note dbm.dumb: 2a. will be used.  There is a
third party interface(2) to the Oracle Berkeley DB.

*note Availability: 1c56.: not WASI, not iOS.

This module does not work or is not available on WebAssembly platforms,
or on iOS. See *note WebAssembly 平台: 16e6. for more information on
WASM availability; see *note iOS: 1d56. for more information on iOS
availability.

 -- 例外: dbm.error

     A tuple containing the exceptions that can be raised by each of the
     supported modules, with a unique exception also named *note
     dbm.error: 27a3. as the first item -- the latter is used when *note
     dbm.error: 27a3. is raised.

 -- 函式: dbm.whichdb (filename)

     This function attempts to guess which of the several simple
     database modules available -- *note dbm.sqlite3: 2d, *note dbm.gnu:
     2b, *note dbm.ndbm: 2c, or *note dbm.dumb: 2a. -- should be used to
     open a given file.

     回傳以下其中一個值：

        * ‘None’ if the file can't be opened because it's unreadable or
          doesn't exist

        * the empty string (‘''’) if the file's format can't be guessed

        * a string containing the required module name, such as
          ‘'dbm.ndbm'’ or ‘'dbm.gnu'’

     在 3.11 版的變更: 'filename' accepts a *note path-like object: ac2.

 -- 函式: dbm.open (file, flag='r', mode=0o666)

     Open a database and return the corresponding database object.


     參數:

        * ‘file’ (*note path-like object: ac2.) - 要打開的資料庫檔案

          If the database file already exists, the *note whichdb():
          27a4. function is used to determine its type and the
          appropriate module is used; if it does not exist, the first
          submodule listed above that can be imported is used.

        * ‘flag’ (*note str: 3f2.) -

             * ‘'r'’ (default): Open existing database for reading only.

             * ‘'w'’: Open existing database for reading and writing.

             * ‘'c'’: Open database for reading and writing, creating it
               if it doesn't exist.

             * ‘'n'’: Always create a new, empty database, open for
               reading and writing.

        * ‘mode’ (*note int: 23c.) - The Unix file access mode of the
          file (default: octal ‘0o666’), used only when the database has
          to be created.

     在 3.11 版的變更: 'file' 接受一個*note 類路徑物件: ac2.。

The object returned by *note open(): ece. supports the same basic
functionality as a *note dict: 23b.; keys and their corresponding values
can be stored, retrieved, and deleted, and the *note in: 2c5. operator
and the ‘keys()’ method are available, as well as ‘get()’ and
‘setdefault()’ methods.

Key and values are always stored as *note bytes: 1a5.  This means that
when strings are used they are implicitly converted to the default
encoding before being stored.

These objects also support being used in a *note with: 577. statement,
which will automatically close them when done.

在 3.2 版的變更: ‘get()’ and ‘setdefault()’ methods are now available
for all *note dbm: 29. backends.

在 3.4 版的變更: Added native support for the context management
protocol to the objects returned by *note open(): ece.

在 3.8 版的變更: Deleting a key from a read-only database raises a
database module specific exception instead of *note KeyError: 2fb.

The following example records some hostnames and a corresponding title,
and then prints out the contents of the database:

     import dbm

     # Open database, creating it if necessary.
     with dbm.open('cache', 'c') as db:

         # Record some values
         db[b'hello'] = b'there'
         db['www.python.org'] = 'Python Website'
         db['www.cnn.com'] = 'Cable News Network'

         # Note that the keys are considered bytes now.
         assert db[b'www.python.org'] == b'Python Website'
         # Notice how the value is now in bytes.
         assert db['www.cnn.com'] == b'Cable News Network'

         # Often-used methods of the dict interface work too.
         print(db.get('python.org', b'not present'))

         # Storing a non-string key or value will raise an exception (most
         # likely a TypeError).
         db['www.yahoo.com'] = 4

     # db is automatically closed when leaving the with statement.

也參考
......

*note shelve: b1. 模組

     Persistence module which stores non-string data.

The individual submodules are described in the following sections.

* Menu:

* dbm.sqlite3: dbm sqlite3 --- SQLite backend for dbm. SQLite backend for dbm
* dbm.gnu: dbm gnu --- GNU 資料庫管理器. GNU 資料庫管理器
* dbm.ndbm: dbm ndbm --- 新資料庫管理器. 新資料庫管理器
* dbm.dumb: dbm dumb --- 可攜式 DBM 實作. 可攜式 DBM 實作

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/dbm/__init__.py

   (2) https://www.jcea.es/programacion/pybsddb.htm


File: python.info,  Node: dbm sqlite3 --- SQLite backend for dbm,  Next: dbm gnu --- GNU 資料庫管理器,  Up: dbm --- Unix "databases" 的介面

5.12.5.1 ‘dbm.sqlite3’ -- SQLite backend for dbm
................................................

在 3.13 版被加入.

'Source code:' Lib/dbm/sqlite3.py(1)

__________________________________________________________________

This module uses the standard library *note sqlite3: ba. module to
provide an SQLite backend for the *note dbm: 29. module.  The files
created by *note dbm.sqlite3: 2d. can thus be opened by *note sqlite3:
ba, or any other SQLite browser, including the SQLite CLI.

 -- 函式: dbm.sqlite3.open (filename, /, flag='r', mode=0o666)

     Open an SQLite database.  The returned object behaves like a *note
     mapping: 1154, implements a ‘close()’ method, and supports a
     "closing" context manager via the *note with: 577. keyword.


     參數:

        * ‘filename’ (*note path-like object: ac2.) - The path to the
          database to be opened.

        * ‘flag’ (*note str: 3f2.) -

             * ‘'r'’ (default): Open existing database for reading only.

             * ‘'w'’: Open existing database for reading and writing.

             * ‘'c'’: Open database for reading and writing, creating it
               if it doesn't exist.

             * ‘'n'’: Always create a new, empty database, open for
               reading and writing.

        * ‘mode’ - The Unix file access mode of the file (default: octal
          ‘0o666’), used only when the database has to be created.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/dbm/sqlite3.py


File: python.info,  Node: dbm gnu --- GNU 資料庫管理器,  Next: dbm ndbm --- 新資料庫管理器,  Prev: dbm sqlite3 --- SQLite backend for dbm,  Up: dbm --- Unix "databases" 的介面

5.12.5.2 ‘dbm.gnu’ -- GNU 資料庫管理器
......................................

'原始碼：'Lib/dbm/gnu.py(1)

__________________________________________________________________

The *note dbm.gnu: 2b. module provides an interface to the GDBM (GNU
dbm) library, similar to the *note dbm.ndbm: 2c. module, but with
additional functionality like crash tolerance.

     備註: The file formats created by *note dbm.gnu: 2b. and *note
     dbm.ndbm: 2c. are incompatible and can not be used interchangeably.

 -- 例外: dbm.gnu.error

     Raised on *note dbm.gnu: 2b.-specific errors, such as I/O errors.
     *note KeyError: 2fb. is raised for general mapping errors like
     specifying an incorrect key.

 -- 函式: dbm.gnu.open (filename, flag='r', mode=0o666, /)

     Open a GDBM database and return a ‘gdbm’ object.


     參數:

        * ‘filename’ (*note path-like object: ac2.) - 要打開的資料庫檔案

        * ‘flag’ (*note str: 3f2.) -

             * ‘'r'’ (default): Open existing database for reading only.

             * ‘'w'’: Open existing database for reading and writing.

             * ‘'c'’: Open database for reading and writing, creating it
               if it doesn't exist.

             * ‘'n'’: Always create a new, empty database, open for
               reading and writing.

          The following additional characters may be appended to control
          how the database is opened:

             * ‘'f'’: Open the database in fast mode.  Writes to the
               database will not be synchronized.

             * ‘'s'’: Synchronized mode.  Changes to the database will
               be written immediately to the file.

             * ‘'u'’: 不要鎖住資料庫。

          Not all flags are valid for all versions of GDBM. See the
          *note open_flags: 27a8. member for a list of supported flag
          characters.

        * ‘mode’ (*note int: 23c.) - The Unix file access mode of the
          file (default: octal ‘0o666’), used only when the database has
          to be created.


     引發: *note error: a3d. - 如果一個無效的 'flag' 引數被傳入。

     在 3.11 版的變更: 'filename' accepts a *note path-like object: ac2.

      -- 資料: dbm.gnu.open_flags

          A string of characters the 'flag' parameter of *note open():
          1945. supports.

     ‘gdbm’ objects behave similar to *note mappings: 1154, but
     ‘items()’ and ‘values()’ methods are not supported.  The following
     methods are also provided:

      -- 方法: gdbm.firstkey ()

          It's possible to loop over every key in the database using
          this method and the *note nextkey(): 27aa. method.  The
          traversal is ordered by GDBM's internal hash values, and won't
          be sorted by the key values.  This method returns the starting
          key.

      -- 方法: gdbm.nextkey (key)

          Returns the key that follows 'key' in the traversal.  The
          following code prints every key in the database ‘db’, without
          having to create a list in memory that contains them all:

               k = db.firstkey()
               while k is not None:
                   print(k)
                   k = db.nextkey(k)

      -- 方法: gdbm.reorganize ()

          If you have carried out a lot of deletions and would like to
          shrink the space used by the GDBM file, this routine will
          reorganize the database.  ‘gdbm’ objects will not shorten the
          length of a database file except by using this reorganization;
          otherwise, deleted file space will be kept and reused as new
          (key, value) pairs are added.

      -- 方法: gdbm.sync ()

          When the database has been opened in fast mode, this method
          forces any unwritten data to be written to the disk.

      -- 方法: gdbm.close ()

          關閉 GDBM 資料庫。

      -- 方法: gdbm.clear ()

          Remove all items from the GDBM database.

          在 3.13 版被加入.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/dbm/gnu.py


File: python.info,  Node: dbm ndbm --- 新資料庫管理器,  Next: dbm dumb --- 可攜式 DBM 實作,  Prev: dbm gnu --- GNU 資料庫管理器,  Up: dbm --- Unix "databases" 的介面

5.12.5.3 ‘dbm.ndbm’ -- 新資料庫管理器
.....................................

'原始碼：'Lib/dbm/ndbm.py(1)

__________________________________________________________________

The *note dbm.ndbm: 2c. module provides an interface to the NDBM (New
Database Manager) library.  This module can be used with the "classic"
NDBM interface or the GDBM compatibility interface.

     備註: The file formats created by *note dbm.gnu: 2b. and *note
     dbm.ndbm: 2c. are incompatible and can not be used interchangeably.

     警告: The NDBM library shipped as part of macOS has an undocumented
     limitation on the size of values, which can result in corrupted
     database files when storing values larger than this limit.  Reading
     such corrupted files can result in a hard crash (segmentation
     fault).

 -- 例外: dbm.ndbm.error

     Raised on *note dbm.ndbm: 2c.-specific errors, such as I/O errors.
     *note KeyError: 2fb. is raised for general mapping errors like
     specifying an incorrect key.

 -- 資料: dbm.ndbm.library

     Name of the NDBM implementation library used.

 -- 函式: dbm.ndbm.open (filename, flag='r', mode=0o666, /)

     Open an NDBM database and return an ‘ndbm’ object.


     參數:

        * ‘filename’ (*note path-like object: ac2.) - The basename of
          the database file (without the ‘.dir’ or ‘.pag’ extensions).

        * ‘flag’ (*note str: 3f2.) -

             * ‘'r'’ (default): Open existing database for reading only.

             * ‘'w'’: Open existing database for reading and writing.

             * ‘'c'’: Open database for reading and writing, creating it
               if it doesn't exist.

             * ‘'n'’: Always create a new, empty database, open for
               reading and writing.

        * ‘mode’ (*note int: 23c.) - The Unix file access mode of the
          file (default: octal ‘0o666’), used only when the database has
          to be created.

     ‘ndbm’ objects behave similar to *note mappings: 1154, but
     ‘items()’ and ‘values()’ methods are not supported.  The following
     methods are also provided:

     在 3.11 版的變更: Accepts *note path-like object: ac2. for
     filename.

      -- 方法: ndbm.close ()

          關閉 NDBM 資料庫。

      -- 方法: ndbm.clear ()

          Remove all items from the NDBM database.

          在 3.13 版被加入.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/dbm/ndbm.py


File: python.info,  Node: dbm dumb --- 可攜式 DBM 實作,  Prev: dbm ndbm --- 新資料庫管理器,  Up: dbm --- Unix "databases" 的介面

5.12.5.4 ‘dbm.dumb’ -- 可攜式 DBM 實作
......................................

'原始碼：'Lib/dbm/dumb.py(1)

     備註: The *note dbm.dumb: 2a. module is intended as a last resort
     fallback for the *note dbm: 29. module when a more robust module is
     not available.  The *note dbm.dumb: 2a. module is not written for
     speed and is not nearly as heavily used as the other database
     modules.

__________________________________________________________________

The *note dbm.dumb: 2a. module provides a persistent *note dict:
23b.-like interface which is written entirely in Python.  Unlike other
*note dbm: 29. backends, such as *note dbm.gnu: 2b, no external library
is required.

‘dbm.dumb’ 模組定義了以下項目：

 -- 例外: dbm.dumb.error

     Raised on *note dbm.dumb: 2a.-specific errors, such as I/O errors.
     *note KeyError: 2fb. is raised for general mapping errors like
     specifying an incorrect key.

 -- 函式: dbm.dumb.open (filename, flag='c', mode=0o666)

     Open a ‘dbm.dumb’ database.  The returned database object behaves
     similar to a *note mapping: 1154, in addition to providing *note
     sync(): 27b2. and *note close(): 27b3. methods.


     參數:

        * ‘filename’ - The basename of the database file (without
          extensions).  A new database creates the following files:

             - ‘`filename'.dat’

             - ‘`filename'.dir’

        * ‘flag’ (*note str: 3f2.) -

             * ‘'r'’: Open existing database for reading only.

             * ‘'w'’: Open existing database for reading and writing.

             * ‘'c'’ (default): Open database for reading and writing,
               creating it if it doesn't exist.

             * ‘'n'’: Always create a new, empty database, open for
               reading and writing.

        * ‘mode’ (*note int: 23c.) - The Unix file access mode of the
          file (default: octal ‘0o666’), used only when the database has
          to be created.

          警告: It is possible to crash the Python interpreter when
          loading a database with a sufficiently large/complex entry due
          to stack depth limitations in Python's AST compiler.

     在 3.5 版的變更: *note open(): a39. always creates a new database
     when 'flag' is ‘'n'’.

     在 3.8 版的變更: A database opened read-only if 'flag' is ‘'r'’.  A
     database is not created if it does not exist if 'flag' is ‘'r'’ or
     ‘'w'’.

     在 3.11 版的變更: 'filename' accepts a *note path-like object: ac2.

     In addition to the methods provided by the *note
     collections.abc.MutableMapping: 1048. class, the following methods
     are provided:

      -- 方法: dumbdbm.sync ()

          Synchronize the on-disk directory and data files.  This method
          is called by the ‘Shelve.sync()’ method.

      -- 方法: dumbdbm.close ()

          關閉資料庫。

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/dbm/dumb.py


File: python.info,  Node: sqlite3 --- SQLite 資料庫的 DB-API 2 0 介面,  Prev: dbm --- Unix "databases" 的介面,  Up: 資料持久性 Data Persistence

5.12.6 ‘sqlite3’ -- SQLite 資料庫的 DB-API 2.0 介面
---------------------------------------------------

'原始碼：'Lib/sqlite3/(1)

SQLite is a C library that provides a lightweight disk-based database
that doesn't require a separate server process and allows accessing the
database using a nonstandard variant of the SQL query language.  Some
applications can use SQLite for internal data storage.  It's also
possible to prototype an application using SQLite and then port the code
to a larger database such as PostgreSQL or Oracle.

The ‘sqlite3’ module was written by Gerhard Häring.  It provides an SQL
interface compliant with the DB-API 2.0 specification described by PEP
249(2), and requires SQLite 3.15.2 or newer.

此文件包含四個主要章節：

   * *note 教學: 27b7. 教導如何使用 ‘sqlite3’ 模組。

   * *note Reference: 27b8. 描述此模組定義的類別與函式。

   * *note How-to guides: 27b9. 詳細說明如何處理特定工作。

   * *note 解釋: 27ba. 深入提供交易 (transaction) 控制的背景。

也參考
......

‘https://www.sqlite.org’

     The SQLite web page; the documentation describes the syntax and the
     available data types for the supported SQL dialect.

‘https://www.w3schools.com/sql/’

     Tutorial, reference and examples for learning SQL syntax.

PEP 249(3) - 資料庫 API 規格 2.0

     PEP 由 Marc-André Lemburg 撰寫。

* Menu:

* 教學::
* Reference::
* How-to guides::
* 解釋::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/sqlite3/

   (2) https://peps.python.org/pep-0249/

   (3) https://peps.python.org/pep-0249/


File: python.info,  Node: 教學,  Next: Reference,  Up: sqlite3 --- SQLite 資料庫的 DB-API 2 0 介面

5.12.6.1 教學
.............

In this tutorial, you will create a database of Monty Python movies
using basic ‘sqlite3’ functionality.  It assumes a fundamental
understanding of database concepts, including cursors(1) and
transactions(2).

First, we need to create a new database and open a database connection
to allow ‘sqlite3’ to work with it.  Call *note sqlite3.connect(): 288.
to create a connection to the database ‘tutorial.db’ in the current
working directory, implicitly creating it if it does not exist:

     import sqlite3
     con = sqlite3.connect("tutorial.db")

The returned *note Connection: 22a. object ‘con’ represents the
connection to the on-disk database.

In order to execute SQL statements and fetch results from SQL queries,
we will need to use a database cursor.  Call *note con.cursor(): 27bc.
to create the *note Cursor: 27bd.:

     cur = con.cursor()

Now that we've got a database connection and a cursor, we can create a
database table ‘movie’ with columns for title, release year, and review
score.  For simplicity, we can just use column names in the table
declaration - thanks to the flexible typing(3) feature of SQLite,
specifying the data types is optional.  Execute the ‘CREATE TABLE’
statement by calling *note cur.execute(...): 2b3.:

     cur.execute("CREATE TABLE movie(title, year, score)")

We can verify that the new table has been created by querying the
‘sqlite_master’ table built-in to SQLite, which should now contain an
entry for the ‘movie’ table definition (see The Schema Table(4) for
details).  Execute that query by calling *note cur.execute(...): 2b3,
assign the result to ‘res’, and call *note res.fetchone(): 27be. to
fetch the resulting row:

     >>> res = cur.execute("SELECT name FROM sqlite_master")
     >>> res.fetchone()
     ('movie',)

We can see that the table has been created, as the query returns a *note
tuple: 322. containing the table's name.  If we query ‘sqlite_master’
for a non-existent table ‘spam’, ‘res.fetchone()’ will return ‘None’:

     >>> res = cur.execute("SELECT name FROM sqlite_master WHERE name='spam'")
     >>> res.fetchone() is None
     True

Now, add two rows of data supplied as SQL literals by executing an
‘INSERT’ statement, once again by calling *note cur.execute(...): 2b3.:

     cur.execute("""
         INSERT INTO movie VALUES
             ('Monty Python and the Holy Grail', 1975, 8.2),
             ('And Now for Something Completely Different', 1971, 7.5)
     """)

The ‘INSERT’ statement implicitly opens a transaction, which needs to be
committed before changes are saved in the database (see *note
Transaction control: 27bf. for details).  Call *note con.commit(): 27c0.
on the connection object to commit the transaction:

     con.commit()

We can verify that the data was inserted correctly by executing a
‘SELECT’ query.  Use the now-familiar *note cur.execute(...): 2b3. to
assign the result to ‘res’, and call *note res.fetchall(): 27c1. to
return all resulting rows:

     >>> res = cur.execute("SELECT score FROM movie")
     >>> res.fetchall()
     [(8.2,), (7.5,)]

The result is a *note list: 5b6. of two ‘tuple’s, one per row, each
containing that row's ‘score’ value.

Now, insert three more rows by calling *note cur.executemany(...): 2b4.:

     data = [
         ("Monty Python Live at the Hollywood Bowl", 1982, 7.9),
         ("Monty Python's The Meaning of Life", 1983, 7.5),
         ("Monty Python's Life of Brian", 1979, 8.0),
     ]
     cur.executemany("INSERT INTO movie VALUES(?, ?, ?)", data)
     con.commit()  # Remember to commit the transaction after executing INSERT.

Notice that ‘?’ placeholders are used to bind ‘data’ to the query.
Always use placeholders instead of *note string formatting: 1b77. to
bind Python values to SQL statements, to avoid SQL injection attacks(5)
(see *note How to use placeholders to bind values in SQL queries: 2b5.
for more details).

We can verify that the new rows were inserted by executing a ‘SELECT’
query, this time iterating over the results of the query:

     >>> for row in cur.execute("SELECT year, title FROM movie ORDER BY year"):
     ...     print(row)
     (1971, 'And Now for Something Completely Different')
     (1975, 'Monty Python and the Holy Grail')
     (1979, "Monty Python's Life of Brian")
     (1982, 'Monty Python Live at the Hollywood Bowl')
     (1983, "Monty Python's The Meaning of Life")

Each row is a two-item *note tuple: 322. of ‘(year, title)’, matching
the columns selected in the query.

Finally, verify that the database has been written to disk by calling
*note con.close(): 22b. to close the existing connection, opening a new
one, creating a new cursor, then querying the database:

     >>> con.close()
     >>> new_con = sqlite3.connect("tutorial.db")
     >>> new_cur = new_con.cursor()
     >>> res = new_cur.execute("SELECT title, year FROM movie ORDER BY score DESC")
     >>> title, year = res.fetchone()
     >>> print(f'The highest scoring Monty Python movie is {title!r}, released in {year}')
     The highest scoring Monty Python movie is 'Monty Python and the Holy Grail', released in 1975
     >>> new_con.close()

You've now created an SQLite database using the ‘sqlite3’ module,
inserted data and retrieved values from it in multiple ways.

也參考
......

   * 進一步參考 *note How-to guides: 27b9.：

        * *note How to use placeholders to bind values in SQL queries:
          2b5.

        * *note How to adapt custom Python types to SQLite values: 27c2.

        * *note How to convert SQLite values to custom Python types:
          27c3.

        * *note How to use the connection context manager: 16e8.

        * *note How to create and use row factories: 27c4.

   * *note 解釋: 27ba. for in-depth background on transaction control.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Cursor_(databases)

   (2) https://en.wikipedia.org/wiki/Database_transaction

   (3) https://www.sqlite.org/flextypegood.html

   (4) https://www.sqlite.org/schematab.html

   (5) https://en.wikipedia.org/wiki/SQL_injection


File: python.info,  Node: Reference,  Next: How-to guides,  Prev: 教學,  Up: sqlite3 --- SQLite 資料庫的 DB-API 2 0 介面

5.12.6.2 Reference
..................

* Menu:

* Module functions::
* Module constants::
* Connection 物件::
* Cursor 物件::
* Row 物件::
* Blob 物件::
* PrepareProtocol 物件::
* 例外: 例外<4>.
* SQLite and Python types::
* Default adapters and converters (deprecated): Default adapters and converters deprecated.
* 命令列介面::


File: python.info,  Node: Module functions,  Next: Module constants,  Up: Reference

5.12.6.3 Module functions
.........................

 -- 函式: sqlite3.connect (database, timeout=5.0, detect_types=0,
          isolation_level='DEFERRED', check_same_thread=True,
          factory=sqlite3.Connection, cached_statements=128, uri=False,
          *, autocommit=sqlite3.LEGACY_TRANSACTION_CONTROL)

     Open a connection to an SQLite database.


     參數:

        * ‘database’ (*note path-like object: ac2.) - The path to the
          database file to be opened.  You can pass ‘":memory:"’ to
          create an SQLite database existing only in memory(1), and open
          a connection to it.

        * ‘timeout’ (*note float: 2c8.) - How many seconds the
          connection should wait before raising an *note
          OperationalError: 17a0. when a table is locked.  If another
          connection opens a transaction to modify a table, that table
          will be locked until the transaction is committed.  Default
          five seconds.

        * ‘detect_types’ (*note int: 23c.) - Control whether and how
          data types not *note natively supported by SQLite: 27c9. are
          looked up to be converted to Python types, using the
          converters registered with *note register_converter(): 27ca.
          Set it to any combination (using ‘|’, bitwise or) of *note
          PARSE_DECLTYPES: 27cb. and *note PARSE_COLNAMES: 27cc. to
          enable this.  Column names takes precedence over declared
          types if both flags are set.  Types cannot be detected for
          generated fields (for example ‘max(data)’), even when the
          'detect_types' parameter is set; *note str: 3f2. will be
          returned instead.  By default (‘0’), type detection is
          disabled.

        * ‘isolation_level’ (*note str: 3f2.‘ | ’‘None’) - Control
          legacy transaction handling behaviour.  See *note
          Connection.isolation_level: 27cd. and *note Transaction
          control via the isolation_level attribute: 27ce. for more
          information.  Can be ‘"DEFERRED"’ (default), ‘"EXCLUSIVE"’ or
          ‘"IMMEDIATE"’; or ‘None’ to disable opening transactions
          implicitly.  Has no effect unless *note Connection.autocommit:
          45d. is set to *note LEGACY_TRANSACTION_CONTROL: 27cf. (the
          default).

        * ‘check_same_thread’ (*note bool: 40e.) - If ‘True’ (default),
          *note ProgrammingError: 49a. will be raised if the database
          connection is used by a thread other than the one that created
          it.  If ‘False’, the connection may be accessed in multiple
          threads; write operations may need to be serialized by the
          user to avoid data corruption.  See *note threadsafety: 622.
          for more information.

        * ‘factory’ (*note Connection: 22a.) - A custom subclass of
          *note Connection: 22a. to create the connection with, if not
          the default *note Connection: 22a. class.

        * ‘cached_statements’ (*note int: 23c.) - The number of
          statements that ‘sqlite3’ should internally cache for this
          connection, to avoid parsing overhead.  By default, 128
          statements.

        * ‘uri’ (*note bool: 40e.) - If set to ‘True’, 'database' is
          interpreted as a URI (Uniform Resource Identifier) with a file
          path and an optional query string.  The scheme part 'must' be
          ‘"file:"’, and the path can be relative or absolute.  The
          query string allows passing parameters to SQLite, enabling
          various *note How to work with SQLite URIs: 27d0.

        * ‘autocommit’ (*note bool: 40e.) - Control PEP 249(2)
          transaction handling behaviour.  See *note
          Connection.autocommit: 45d. and *note Transaction control via
          the autocommit attribute: 45e. for more information.
          'autocommit' currently defaults to *note
          LEGACY_TRANSACTION_CONTROL: 27cf.  The default will change to
          ‘False’ in a future Python release.


     回傳型別: *note Connection: 22a.

     引發一個附帶引數 ‘database’ 的*note 稽核事件: 17bd.
     ‘sqlite3.connect’。

     引發一個附帶引數 ‘connection_handle’ 的*note 稽核事件: 17bd.
     ‘sqlite3.connect/handle’。

     在 3.4 版的變更: 新增 'uri' 參數。

     在 3.7 版的變更: 'database' can now also be a *note path-like
     object: ac2, not only a string.

     在 3.10 版的變更: 新增 ‘sqlite3.connect/handle’ 稽核事件。

     在 3.12 版的變更: 新增 'autocommit' 參數。

     在 3.13 版的變更: Positional use of the parameters 'timeout',
     'detect_types', 'isolation_level', 'check_same_thread', 'factory',
     'cached_statements', and 'uri' is deprecated.  They will become
     keyword-only parameters in Python 3.15.

 -- 函式: sqlite3.complete_statement (statement)

     Return ‘True’ if the string 'statement' appears to contain one or
     more complete SQL statements.  No syntactic verification or parsing
     of any kind is performed, other than checking that there are no
     unclosed string literals and the statement is terminated by a
     semicolon.

     範例：

          >>> sqlite3.complete_statement("SELECT foo FROM bar;")
          True
          >>> sqlite3.complete_statement("SELECT foo")
          False

     This function may be useful during command-line input to determine
     if the entered text seems to form a complete SQL statement, or if
     additional input is needed before calling *note execute(): 2b3.

     See ‘runsource()’ in Lib/sqlite3/__main__.py(3) for real-world use.

 -- 函式: sqlite3.enable_callback_tracebacks (flag, /)

     Enable or disable callback tracebacks.  By default you will not get
     any tracebacks in user-defined functions, aggregates, converters,
     authorizer callbacks etc.  If you want to debug them, you can call
     this function with 'flag' set to ‘True’.  Afterwards, you will get
     tracebacks from callbacks on *note sys.stderr: 8dd.  Use ‘False’ to
     disable the feature again.

          備註: Errors in user-defined function callbacks are logged as
          unraisable exceptions.  Use an *note unraisable hook handler:
          1dc. for introspection of the failed callback.

 -- 函式: sqlite3.register_adapter (type, adapter, /)

     Register an 'adapter' *note callable: 27d4. to adapt the Python
     type 'type' into an SQLite type.  The adapter is called with a
     Python object of type 'type' as its sole argument, and must return
     a value of a *note type that SQLite natively understands: 27c9.

 -- 函式: sqlite3.register_converter (typename, converter, /)

     Register the 'converter' *note callable: 27d4. to convert SQLite
     objects of type 'typename' into a Python object of a specific type.
     The converter is invoked for all SQLite values of type 'typename';
     it is passed a *note bytes: 1a5. object and should return an object
     of the desired Python type.  Consult the parameter 'detect_types'
     of *note connect(): 288. for information regarding how type
     detection works.

     Note: 'typename' and the name of the type in your query are matched
     case-insensitively.

   ---------- Footnotes ----------

   (1) https://sqlite.org/inmemorydb.html

   (2) https://peps.python.org/pep-0249/

   (3) 
https://github.com/python/cpython/tree/3.13/Lib/sqlite3/__main__.py


File: python.info,  Node: Module constants,  Next: Connection 物件,  Prev: Module functions,  Up: Reference

5.12.6.4 Module constants
.........................

 -- 資料: sqlite3.LEGACY_TRANSACTION_CONTROL

     Set *note autocommit: 45d. to this constant to select old style
     (pre-Python 3.12) transaction control behaviour.  See *note
     Transaction control via the isolation_level attribute: 27ce. for
     more information.

 -- 資料: sqlite3.PARSE_COLNAMES

     Pass this flag value to the 'detect_types' parameter of *note
     connect(): 288. to look up a converter function by using the type
     name, parsed from the query column name, as the converter
     dictionary key.  The type name must be wrapped in square brackets
     (‘[]’).

          SELECT p as "p [point]" FROM test;  ! will look up converter "point"

     This flag may be combined with *note PARSE_DECLTYPES: 27cb. using
     the ‘|’ (bitwise or) operator.

 -- 資料: sqlite3.PARSE_DECLTYPES

     Pass this flag value to the 'detect_types' parameter of *note
     connect(): 288. to look up a converter function using the declared
     types for each column.  The types are declared when the database
     table is created.  ‘sqlite3’ will look up a converter function
     using the first word of the declared type as the converter
     dictionary key.  For example:

          CREATE TABLE test(
             i integer primary key,  ! will look up a converter named "integer"
             p point,                ! will look up a converter named "point"
             n number(10)            ! will look up a converter named "number"
           )

     This flag may be combined with *note PARSE_COLNAMES: 27cc. using
     the ‘|’ (bitwise or) operator.

 -- 資料: sqlite3.SQLITE_OK
 -- 資料: sqlite3.SQLITE_DENY
 -- 資料: sqlite3.SQLITE_IGNORE

     Flags that should be returned by the 'authorizer_callback' *note
     callable: 27d4. passed to *note Connection.set_authorizer(): 28b,
     to indicate whether:

        * Access is allowed (‘SQLITE_OK’),

        * The SQL statement should be aborted with an error
          (‘SQLITE_DENY’)

        * The column should be treated as a ‘NULL’ value
          (‘SQLITE_IGNORE’)

 -- 資料: sqlite3.apilevel

     String constant stating the supported DB-API level.  Required by
     the DB-API. Hard-coded to ‘"2.0"’.

 -- 資料: sqlite3.paramstyle

     String constant stating the type of parameter marker formatting
     expected by the ‘sqlite3’ module.  Required by the DB-API.
     Hard-coded to ‘"qmark"’.

          備註: The ‘named’ DB-API parameter style is also supported.

 -- 資料: sqlite3.sqlite_version

     Version number of the runtime SQLite library as a *note string:
     3f2.

 -- 資料: sqlite3.sqlite_version_info

     Version number of the runtime SQLite library as a *note tuple: 322.
     of *note integers: 23c.

 -- 資料: sqlite3.threadsafety

     Integer constant required by the DB-API 2.0, stating the level of
     thread safety the ‘sqlite3’ module supports.  This attribute is set
     based on the default threading mode(1) the underlying SQLite
     library is compiled with.  The SQLite threading modes are:

       1. 'Single-thread': In this mode, all mutexes are disabled and
          SQLite is unsafe to use in more than a single thread at once.

       2. 'Multi-thread': In this mode, SQLite can be safely used by
          multiple threads provided that no single database connection
          is used simultaneously in two or more threads.

       3. 'Serialized': In serialized mode, SQLite can be safely used by
          multiple threads with no restriction.

     The mappings from SQLite threading modes to DB-API 2.0 threadsafety
     levels are as follows:

     SQLite threading       threadsafety(2)       SQLITE_THREADSAFE(3)       DB-API 2.0 meaning
     mode                                                                    

     ------------------------------------------------------------------------------------------------------------
                                                                             
     single-thread          0                     0                          Threads may not share the module
                                                                             
                                                                             
     multi-thread           1                     2                          Threads may share the module, but
                                                                             not connections
                                                                             
                                                                             
     serialized             3                     1                          Threads may share the module,
                                                                             connections and cursors
                                                                             

     在 3.11 版的變更: Set 'threadsafety' dynamically instead of
     hard-coding it to ‘1’.

 -- 資料: sqlite3.version

     Version number of this module as a *note string: 3f2.  This is not
     the version of the SQLite library.

     Deprecated since version 3.12, will be removed in version 3.14:
     This constant used to reflect the version number of the ‘pysqlite’
     package, a third-party library which used to upstream changes to
     ‘sqlite3’.  Today, it carries no meaning or practical value.

 -- 資料: sqlite3.version_info

     Version number of this module as a *note tuple: 322. of *note
     integers: 23c.  This is not the version of the SQLite library.

     Deprecated since version 3.12, will be removed in version 3.14:
     This constant used to reflect the version number of the ‘pysqlite’
     package, a third-party library which used to upstream changes to
     ‘sqlite3’.  Today, it carries no meaning or practical value.

 -- 資料: sqlite3.SQLITE_DBCONFIG_DEFENSIVE
 -- 資料: sqlite3.SQLITE_DBCONFIG_DQS_DDL
 -- 資料: sqlite3.SQLITE_DBCONFIG_DQS_DML
 -- 資料: sqlite3.SQLITE_DBCONFIG_ENABLE_FKEY
 -- 資料: sqlite3.SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER
 -- 資料: sqlite3.SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION
 -- 資料: sqlite3.SQLITE_DBCONFIG_ENABLE_QPSG
 -- 資料: sqlite3.SQLITE_DBCONFIG_ENABLE_TRIGGER
 -- 資料: sqlite3.SQLITE_DBCONFIG_ENABLE_VIEW
 -- 資料: sqlite3.SQLITE_DBCONFIG_LEGACY_ALTER_TABLE
 -- 資料: sqlite3.SQLITE_DBCONFIG_LEGACY_FILE_FORMAT
 -- 資料: sqlite3.SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE
 -- 資料: sqlite3.SQLITE_DBCONFIG_RESET_DATABASE
 -- 資料: sqlite3.SQLITE_DBCONFIG_TRIGGER_EQP
 -- 資料: sqlite3.SQLITE_DBCONFIG_TRUSTED_SCHEMA
 -- 資料: sqlite3.SQLITE_DBCONFIG_WRITABLE_SCHEMA

     These constants are used for the *note Connection.setconfig(): 461.
     and *note getconfig(): 460. methods.

     The availability of these constants varies depending on the version
     of SQLite Python was compiled with.

     在 3.12 版被加入.

     也參考
     ......

     ‘https://www.sqlite.org/c3ref/c_dbconfig_defensive.html’

          SQLite docs: Database Connection Configuration Options

   ---------- Footnotes ----------

   (1) https://sqlite.org/threadsafe.html

   (2) https://peps.python.org/pep-0249/#threadsafety

   (3) https://sqlite.org/compile.html#threadsafe


File: python.info,  Node: Connection 物件,  Next: Cursor 物件,  Prev: Module constants,  Up: Reference

5.12.6.5 Connection 物件
........................

 -- 類別: sqlite3.Connection

     Each open SQLite database is represented by a ‘Connection’ object,
     which is created using *note sqlite3.connect(): 288.  Their main
     purpose is creating *note Cursor: 27bd. objects, and *note
     Transaction control: 27bf.

     也參考
     ......

        * *note How to use connection shortcut methods: 27f1.

        * *note How to use the connection context manager: 16e8.

     在 3.13 版的變更: A *note ResourceWarning: 229. is emitted if *note
     close(): 22b. is not called before a ‘Connection’ object is
     deleted.

     An SQLite database connection has the following attributes and
     methods:

      -- 方法: cursor (factory=Cursor)

          Create and return a *note Cursor: 27bd. object.  The cursor
          method accepts a single optional parameter 'factory'.  If
          supplied, this must be a *note callable: 27d4. returning an
          instance of *note Cursor: 27bd. or its subclasses.

      -- 方法: blobopen (table, column, row, /, *, readonly=False,
               name='main')

          Open a *note Blob: 628. handle to an existing BLOB (Binary
          Large OBject).


          參數:

             * ‘table’ (*note str: 3f2.) - The name of the table where
               the blob is located.

             * ‘column’ (*note str: 3f2.) - The name of the column where
               the blob is located.

             * ‘row’ (*note str: 3f2.) - The name of the row where the
               blob is located.

             * ‘readonly’ (*note bool: 40e.) - Set to ‘True’ if the blob
               should be opened without write permissions.  Defaults to
               ‘False’.

             * ‘name’ (*note str: 3f2.) - The name of the database where
               the blob is located.  Defaults to ‘"main"’.


          引發: *note OperationalError: 17a0. - When trying to open a
          blob in a ‘WITHOUT ROWID’ table.


          回傳型別: *note Blob: 628.

               備註: The blob size cannot be changed using the *note
               Blob: 628. class.  Use the SQL function ‘zeroblob’ to
               create a blob with a fixed size.

          在 3.11 版被加入.

      -- 方法: commit ()

          Commit any pending transaction to the database.  If *note
          autocommit: 45d. is ‘True’, or there is no open transaction,
          this method does nothing.  If ‘autocommit’ is ‘False’, a new
          transaction is implicitly opened if a pending transaction was
          committed by this method.

      -- 方法: rollback ()

          Roll back to the start of any pending transaction.  If *note
          autocommit: 45d. is ‘True’, or there is no open transaction,
          this method does nothing.  If ‘autocommit’ is ‘False’, a new
          transaction is implicitly opened if a pending transaction was
          rolled back by this method.

      -- 方法: close ()

          Close the database connection.  If *note autocommit: 45d. is
          ‘False’, any pending transaction is implicitly rolled back.
          If ‘autocommit’ is ‘True’ or *note LEGACY_TRANSACTION_CONTROL:
          27cf, no implicit transaction control is executed.  Make sure
          to *note commit(): 27c0. before closing to avoid losing
          pending changes.

      -- 方法: execute (sql, parameters=(), /)

          Create a new *note Cursor: 27bd. object and call *note
          execute(): 2b3. on it with the given 'sql' and 'parameters'.
          Return the new cursor object.

      -- 方法: executemany (sql, parameters, /)

          Create a new *note Cursor: 27bd. object and call *note
          executemany(): 2b4. on it with the given 'sql' and
          'parameters'.  Return the new cursor object.

      -- 方法: executescript (sql_script, /)

          Create a new *note Cursor: 27bd. object and call *note
          executescript(): 27f6. on it with the given 'sql_script'.
          Return the new cursor object.

      -- 方法: create_function (name, narg, func, *,
               deterministic=False)

          Create or remove a user-defined SQL function.


          參數:

             * ‘name’ (*note str: 3f2.) - The name of the SQL function.

             * ‘narg’ (*note int: 23c.) - The number of arguments the
               SQL function can accept.  If ‘-1’, it may take any number
               of arguments.

             * ‘func’ (*note callback: 27f7. | None) - A *note callable:
               27d4. that is called when the SQL function is invoked.
               The callable must return *note a type natively supported
               by SQLite: 27c9.  Set to ‘None’ to remove an existing SQL
               function.

             * ‘deterministic’ (*note bool: 40e.) - If ‘True’, the
               created SQL function is marked as deterministic(1), which
               allows SQLite to perform additional optimizations.

          在 3.8 版的變更: 新增 'deterministic' 參數。

          範例：

               >>> import hashlib
               >>> def md5sum(t):
               ...     return hashlib.md5(t).hexdigest()
               >>> con = sqlite3.connect(":memory:")
               >>> con.create_function("md5", 1, md5sum)
               >>> for row in con.execute("SELECT md5(?)", (b"foo",)):
               ...     print(row)
               ('acbd18db4cc2f85cedef654fccc4a4d8',)
               >>> con.close()

          在 3.13 版的變更: Passing 'name', 'narg', and 'func' as
          keyword arguments is deprecated.  These parameters will become
          positional-only in Python 3.15.

      -- 方法: create_aggregate (name, n_arg, aggregate_class)

          Create or remove a user-defined SQL aggregate function.


          參數:

             * ‘name’ (*note str: 3f2.) - The name of the SQL aggregate
               function.

             * ‘n_arg’ (*note int: 23c.) - The number of arguments the
               SQL aggregate function can accept.  If ‘-1’, it may take
               any number of arguments.

             * ‘aggregate_class’ (*note class: 1834. | None) - A class
               must implement the following methods:

                  * ‘step()’: Add a row to the aggregate.

                  * ‘finalize()’: Return the final result of the
                    aggregate as *note a type natively supported by
                    SQLite: 27c9.

               The number of arguments that the ‘step()’ method must
               accept is controlled by 'n_arg'.

               Set to ‘None’ to remove an existing SQL aggregate
               function.

          範例：

               class MySum:
                   def __init__(self):
                       self.count = 0

                   def step(self, value):
                       self.count += value

                   def finalize(self):
                       return self.count

               con = sqlite3.connect(":memory:")
               con.create_aggregate("mysum", 1, MySum)
               cur = con.execute("CREATE TABLE test(i)")
               cur.execute("INSERT INTO test(i) VALUES(1)")
               cur.execute("INSERT INTO test(i) VALUES(2)")
               cur.execute("SELECT mysum(i) FROM test")
               print(cur.fetchone()[0])

               con.close()

          在 3.13 版的變更: Passing 'name', 'n_arg', and
          'aggregate_class' as keyword arguments is deprecated.  These
          parameters will become positional-only in Python 3.15.

      -- 方法: create_window_function (name, num_params,
               aggregate_class, /)

          Create or remove a user-defined aggregate window function.


          參數:

             * ‘name’ (*note str: 3f2.) - The name of the SQL aggregate
               window function to create or remove.

             * ‘num_params’ (*note int: 23c.) - The number of arguments
               the SQL aggregate window function can accept.  If ‘-1’,
               it may take any number of arguments.

             * ‘aggregate_class’ (*note class: 1834. | None) - A class
               that must implement the following methods:

                  * ‘step()’: Add a row to the current window.

                  * ‘value()’: Return the current value of the
                    aggregate.

                  * ‘inverse()’: Remove a row from the current window.

                  * ‘finalize()’: Return the final result of the
                    aggregate as *note a type natively supported by
                    SQLite: 27c9.

               The number of arguments that the ‘step()’ and ‘value()’
               methods must accept is controlled by 'num_params'.

               Set to ‘None’ to remove an existing SQL aggregate window
               function.


          引發: *note NotSupportedError: 27f8. - If used with a version
          of SQLite older than 3.25.0, which does not support aggregate
          window functions.

          在 3.11 版被加入.

          範例：

               # Example taken from https://www.sqlite.org/windowfunctions.html#udfwinfunc
               class WindowSumInt:
                   def __init__(self):
                       self.count = 0

                   def step(self, value):
                       """Add a row to the current window."""
                       self.count += value

                   def value(self):
                       """Return the current value of the aggregate."""
                       return self.count

                   def inverse(self, value):
                       """Remove a row from the current window."""
                       self.count -= value

                   def finalize(self):
                       """Return the final value of the aggregate.

                       Any clean-up actions should be placed here.
                       """
                       return self.count


               con = sqlite3.connect(":memory:")
               cur = con.execute("CREATE TABLE test(x, y)")
               values = [
                   ("a", 4),
                   ("b", 5),
                   ("c", 3),
                   ("d", 8),
                   ("e", 1),
               ]
               cur.executemany("INSERT INTO test VALUES(?, ?)", values)
               con.create_window_function("sumint", 1, WindowSumInt)
               cur.execute("""
                   SELECT x, sumint(y) OVER (
                       ORDER BY x ROWS BETWEEN 1 PRECEDING AND 1 FOLLOWING
                   ) AS sum_y
                   FROM test ORDER BY x
               """)
               print(cur.fetchall())
               con.close()

      -- 方法: create_collation (name, callable, /)

          Create a collation named 'name' using the collating function
          'callable'.  'callable' is passed two *note string: 3f2.
          arguments, and it should return an *note integer: 23c.:

             * ‘1’ if the first is ordered higher than the second

             * ‘-1’ if the first is ordered lower than the second

             * ‘0’ if they are ordered equal

          The following example shows a reverse sorting collation:

               def collate_reverse(string1, string2):
                   if string1 == string2:
                       return 0
                   elif string1 < string2:
                       return 1
                   else:
                       return -1

               con = sqlite3.connect(":memory:")
               con.create_collation("reverse", collate_reverse)

               cur = con.execute("CREATE TABLE test(x)")
               cur.executemany("INSERT INTO test(x) VALUES(?)", [("a",), ("b",)])
               cur.execute("SELECT x FROM test ORDER BY x COLLATE reverse")
               for row in cur:
                   print(row)
               con.close()

          Remove a collation function by setting 'callable' to ‘None’.

          在 3.11 版的變更: The collation name can contain any Unicode
          character.  Earlier, only ASCII characters were allowed.

      -- 方法: interrupt ()

          Call this method from a different thread to abort any queries
          that might be executing on the connection.  Aborted queries
          will raise an *note OperationalError: 17a0.

      -- 方法: set_authorizer (authorizer_callback)

          Register *note callable: 27d4. 'authorizer_callback' to be
          invoked for each attempt to access a column of a table in the
          database.  The callback should return one of *note SQLITE_OK:
          27d7, *note SQLITE_DENY: 27d8, or *note SQLITE_IGNORE: 27d9.
          to signal how access to the column should be handled by the
          underlying SQLite library.

          The first argument to the callback signifies what kind of
          operation is to be authorized.  The second and third argument
          will be arguments or ‘None’ depending on the first argument.
          The 4th argument is the name of the database ("main", "temp",
          etc.)  if applicable.  The 5th argument is the name of the
          inner-most trigger or view that is responsible for the access
          attempt or ‘None’ if this access attempt is directly from
          input SQL code.

          Please consult the SQLite documentation about the possible
          values for the first argument and the meaning of the second
          and third argument depending on the first one.  All necessary
          constants are available in the ‘sqlite3’ module.

          Passing ‘None’ as 'authorizer_callback' will disable the
          authorizer.

          在 3.11 版的變更: Added support for disabling the authorizer
          using ‘None’.

          在 3.13 版的變更: Passing 'authorizer_callback' as a keyword
          argument is deprecated.  The parameter will become
          positional-only in Python 3.15.

      -- 方法: set_progress_handler (progress_handler, n)

          Register *note callable: 27d4. 'progress_handler' to be
          invoked for every 'n' instructions of the SQLite virtual
          machine.  This is useful if you want to get called from SQLite
          during long-running operations, for example to update a GUI.

          If you want to clear any previously installed progress
          handler, call the method with ‘None’ for 'progress_handler'.

          Returning a non-zero value from the handler function will
          terminate the currently executing query and cause it to raise
          a *note DatabaseError: 27fa. exception.

          在 3.13 版的變更: Passing 'progress_handler' as a keyword
          argument is deprecated.  The parameter will become
          positional-only in Python 3.15.

      -- 方法: set_trace_callback (trace_callback)

          Register *note callable: 27d4. 'trace_callback' to be invoked
          for each SQL statement that is actually executed by the SQLite
          backend.

          The only argument passed to the callback is the statement (as
          *note str: 3f2.) that is being executed.  The return value of
          the callback is ignored.  Note that the backend does not only
          run statements passed to the *note Cursor.execute(): 2b3.
          methods.  Other sources include the *note transaction
          management: 27bf. of the ‘sqlite3’ module and the execution of
          triggers defined in the current database.

          Passing ‘None’ as 'trace_callback' will disable the trace
          callback.

               備註: Exceptions raised in the trace callback are not
               propagated.  As a development and debugging aid, use
               *note enable_callback_tracebacks(): 27d2. to enable
               printing tracebacks from exceptions raised in the trace
               callback.

          在 3.3 版被加入.

          在 3.13 版的變更: Passing 'trace_callback' as a keyword
          argument is deprecated.  The parameter will become
          positional-only in Python 3.15.

      -- 方法: enable_load_extension (enabled, /)

          Enable the SQLite engine to load SQLite extensions from shared
          libraries if 'enabled' is ‘True’; else, disallow loading
          SQLite extensions.  SQLite extensions can define new
          functions, aggregates or whole new virtual table
          implementations.  One well-known extension is the
          fulltext-search extension distributed with SQLite.

               備註: The ‘sqlite3’ module is not built with loadable
               extension support by default, because some platforms
               (notably macOS) have SQLite libraries which are compiled
               without this feature.  To get loadable extension support,
               you must pass the *note
               -enable-loadable-sqlite-extensions: 1c6e. option to
               ‘configure’.

          引發一個附帶引數 ‘connection’、‘enabled’ 的*note 稽核事件:
          17bd. ‘sqlite3.enable_load_extension’。

          在 3.2 版被加入.

          在 3.10 版的變更: 加入 ‘sqlite3.enable_load_extension’ 稽核事
          件。

               con.enable_load_extension(True)

               # Load the fulltext search extension
               con.execute("select load_extension('./fts3.so')")

               # alternatively you can load the extension using an API call:
               # con.load_extension("./fts3.so")

               # disable extension loading again
               con.enable_load_extension(False)

               # example from SQLite wiki
               con.execute("CREATE VIRTUAL TABLE recipe USING fts3(name, ingredients)")
               con.executescript("""
                   INSERT INTO recipe (name, ingredients) VALUES('broccoli stew', 'broccoli peppers cheese tomatoes');
                   INSERT INTO recipe (name, ingredients) VALUES('pumpkin stew', 'pumpkin onions garlic celery');
                   INSERT INTO recipe (name, ingredients) VALUES('broccoli pie', 'broccoli cheese onions flour');
                   INSERT INTO recipe (name, ingredients) VALUES('pumpkin pie', 'pumpkin sugar flour butter');
                   """)
               for row in con.execute("SELECT rowid, name, ingredients FROM recipe WHERE name MATCH 'pie'"):
                   print(row)

      -- 方法: load_extension (path, /, *, entrypoint=None)

          Load an SQLite extension from a shared library.  Enable
          extension loading with *note enable_load_extension(): 7e2.
          before calling this method.


          參數:

             * ‘path’ (*note str: 3f2.) - The path to the SQLite
               extension.

             * ‘entrypoint’ (*note str: 3f2.‘ | ’‘None’) - Entry point
               name.  If ‘None’ (the default), SQLite will come up with
               an entry point name of its own; see the SQLite docs
               Loading an Extension(2) for details.

          引發一個附帶引數 ‘connection’、‘path’ 的*note 稽核事件: 17bd.
          ‘sqlite3.load_extension’。

          在 3.2 版被加入.

          在 3.10 版的變更: 加入 ‘sqlite3.load_extension’ 稽核事件。

          在 3.12 版的變更: 新增 'entrypoint' 參數。

      -- 方法: iterdump (*, filter=None)

          Return an *note iterator: 192. to dump the database as SQL
          source code.  Useful when saving an in-memory database for
          later restoration.  Similar to the ‘.dump’ command in the
          ‘sqlite3’ shell.


          參數: ‘filter’ (*note str: 3f2.‘ | ’‘None’) - An optional
          ‘LIKE’ pattern for database objects to dump, e.g.  ‘prefix_%’.
          If ‘None’ (the default), all database objects will be
          included.

          範例：

               # Convert file example.db to SQL dump file dump.sql
               con = sqlite3.connect('example.db')
               with open('dump.sql', 'w') as f:
                   for line in con.iterdump():
                       f.write('%s\n' % line)
               con.close()

          也參考
          ......

          *note How to handle non-UTF-8 text encodings: 27fb.

          在 3.13 版的變更: Added the 'filter' parameter.

      -- 方法: backup (target, *, pages=-1, progress=None, name='main',
               sleep=0.250)

          Create a backup of an SQLite database.

          Works even if the database is being accessed by other clients
          or concurrently by the same connection.


          參數:

             * ‘target’ (*note Connection: 22a.) - The database
               connection to save the backup to.

             * ‘pages’ (*note int: 23c.) - The number of pages to copy
               at a time.  If equal to or less than ‘0’, the entire
               database is copied in a single step.  Defaults to ‘-1’.

             * ‘progress’ (*note callback: 27f7. | None) - If set to a
               *note callable: 27d4, it is invoked with three integer
               arguments for every backup iteration: the 'status' of the
               last iteration, the 'remaining' number of pages still to
               be copied, and the 'total' number of pages.  Defaults to
               ‘None’.

             * ‘name’ (*note str: 3f2.) - The name of the database to
               back up.  Either ‘"main"’ (the default) for the main
               database, ‘"temp"’ for the temporary database, or the
               name of a custom database as attached using the ‘ATTACH
               DATABASE’ SQL statement.

             * ‘sleep’ (*note float: 2c8.) - The number of seconds to
               sleep between successive attempts to back up remaining
               pages.

          Example 1, copy an existing database into another:

               def progress(status, remaining, total):
                   print(f'Copied {total-remaining} of {total} pages...')

               src = sqlite3.connect('example.db')
               dst = sqlite3.connect('backup.db')
               with dst:
                   src.backup(dst, pages=1, progress=progress)
               dst.close()
               src.close()

          Example 2, copy an existing database into a transient copy:

               src = sqlite3.connect('example.db')
               dst = sqlite3.connect(':memory:')
               src.backup(dst)
               dst.close()
               src.close()

          在 3.7 版被加入.

          也參考
          ......

          *note How to handle non-UTF-8 text encodings: 27fb.

      -- 方法: getlimit (category, /)

          Get a connection runtime limit.


          參數: ‘category’ (*note int: 23c.) - The SQLite limit
          category(3) to be queried.


          回傳型別: *note int: 23c.


          引發: *note ProgrammingError: 49a. - If 'category' is not
          recognised by the underlying SQLite library.

          Example, query the maximum length of an SQL statement for
          *note Connection: 22a. ‘con’ (the default is 1000000000):

               >>> con.getlimit(sqlite3.SQLITE_LIMIT_SQL_LENGTH)
               1000000000

          在 3.11 版被加入.

      -- 方法: setlimit (category, limit, /)

          Set a connection runtime limit.  Attempts to increase a limit
          above its hard upper bound are silently truncated to the hard
          upper bound.  Regardless of whether or not the limit was
          changed, the prior value of the limit is returned.


          參數:

             * ‘category’ (*note int: 23c.) - The SQLite limit
               category(4) to be set.

             * ‘limit’ (*note int: 23c.) - The value of the new limit.
               If negative, the current limit is unchanged.


          回傳型別: *note int: 23c.


          引發: *note ProgrammingError: 49a. - If 'category' is not
          recognised by the underlying SQLite library.

          Example, limit the number of attached databases to 1 for *note
          Connection: 22a. ‘con’ (the default limit is 10):

               >>> con.setlimit(sqlite3.SQLITE_LIMIT_ATTACHED, 1)
               10
               >>> con.getlimit(sqlite3.SQLITE_LIMIT_ATTACHED)
               1

          在 3.11 版被加入.

      -- 方法: getconfig (op, /)

          Query a boolean connection configuration option.


          參數: ‘op’ (*note int: 23c.) - A *note SQLITE_DBCONFIG code:
          27de.


          回傳型別: *note bool: 40e.

          在 3.12 版被加入.

      -- 方法: setconfig (op, enable=True, /)

          Set a boolean connection configuration option.


          參數:

             * ‘op’ (*note int: 23c.) - A *note SQLITE_DBCONFIG code:
               27de.

             * ‘enable’ (*note bool: 40e.) - ‘True’ if the configuration
               option should be enabled (default); ‘False’ if it should
               be disabled.

          在 3.12 版被加入.

      -- 方法: serialize (*, name='main')

          Serialize a database into a *note bytes: 1a5. object.  For an
          ordinary on-disk database file, the serialization is just a
          copy of the disk file.  For an in-memory database or a "temp"
          database, the serialization is the same sequence of bytes
          which would be written to disk if that database were backed up
          to disk.


          參數: ‘name’ (*note str: 3f2.) - The database name to be
          serialized.  Defaults to ‘"main"’.


          回傳型別: *note bytes: 1a5.

               備註: This method is only available if the underlying
               SQLite library has the serialize API.

          在 3.11 版被加入.

      -- 方法: deserialize (data, /, *, name='main')

          Deserialize a *note serialized: 624. database into a *note
          Connection: 22a.  This method causes the database connection
          to disconnect from database 'name', and reopen 'name' as an
          in-memory database based on the serialization contained in
          'data'.


          參數:

             * ‘data’ (*note bytes: 1a5.) - A serialized database.

             * ‘name’ (*note str: 3f2.) - The database name to
               deserialize into.  Defaults to ‘"main"’.


          引發:

             * *note OperationalError: 17a0. - If the database
               connection is currently involved in a read transaction or
               a backup operation.

             * *note DatabaseError: 27fa. - If 'data' does not contain a
               valid SQLite database.

             * *note OverflowError: 825. - If *note len(data): 5d4. is
               larger than ‘2**63 - 1’.

               備註: This method is only available if the underlying
               SQLite library has the deserialize API.

          在 3.11 版被加入.

      -- 屬性: autocommit

          This attribute controls PEP 249(5)-compliant transaction
          behaviour.  ‘autocommit’ has three allowed values:

             * ‘False’: Select PEP 249(6)-compliant transaction
               behaviour, implying that ‘sqlite3’ ensures a transaction
               is always open.  Use *note commit(): 27c0. and *note
               rollback(): 27f2. to close transactions.

               This is the recommended value of ‘autocommit’.

             * ‘True’: Use SQLite's autocommit mode(7).  *note commit():
               27c0. and *note rollback(): 27f2. have no effect in this
               mode.

             * *note LEGACY_TRANSACTION_CONTROL: 27cf.: Pre-Python 3.12
               (non- PEP 249(8)-compliant) transaction control.  See
               *note isolation_level: 27cd. for more details.

               This is currently the default value of ‘autocommit’.

          Changing ‘autocommit’ to ‘False’ will open a new transaction,
          and changing it to ‘True’ will commit any pending transaction.

          更多詳情請見 *note Transaction control via the autocommit
          attribute: 45e.。

               備註: The *note isolation_level: 27cd. attribute has no
               effect unless *note autocommit: 45d. is *note
               LEGACY_TRANSACTION_CONTROL: 27cf.

          在 3.12 版被加入.

      -- 屬性: in_transaction

          This read-only attribute corresponds to the low-level SQLite
          autocommit mode(9).

          ‘True’ if a transaction is active (there are uncommitted
          changes), ‘False’ otherwise.

          在 3.2 版被加入.

      -- 屬性: isolation_level

          Controls the *note legacy transaction handling mode: 27ce. of
          ‘sqlite3’.  If set to ‘None’, transactions are never
          implicitly opened.  If set to one of ‘"DEFERRED"’,
          ‘"IMMEDIATE"’, or ‘"EXCLUSIVE"’, corresponding to the
          underlying SQLite transaction behaviour(10), *note implicit
          transaction management: 27ce. is performed.

          If not overridden by the 'isolation_level' parameter of *note
          connect(): 288, the default is ‘""’, which is an alias for
          ‘"DEFERRED"’.

               備註: Using *note autocommit: 45d. to control transaction
               handling is recommended over using ‘isolation_level’.
               ‘isolation_level’ has no effect unless *note autocommit:
               45d. is set to *note LEGACY_TRANSACTION_CONTROL: 27cf.
               (the default).

      -- 屬性: row_factory

          The initial *note row_factory: 27fd. for *note Cursor: 27bd.
          objects created from this connection.  Assigning to this
          attribute does not affect the ‘row_factory’ of existing
          cursors belonging to this connection, only new ones.  Is
          ‘None’ by default, meaning each row is returned as a *note
          tuple: 322.

          更多詳情請見 *note How to create and use row factories: 27c4.。

      -- 屬性: text_factory

          A *note callable: 27d4. that accepts a *note bytes: 1a5.
          parameter and returns a text representation of it.  The
          callable is invoked for SQLite values with the ‘TEXT’ data
          type.  By default, this attribute is set to *note str: 3f2.

          更多詳情請見 *note How to handle non-UTF-8 text encodings:
          27fb.。

      -- 屬性: total_changes

          Return the total number of database rows that have been
          modified, inserted, or deleted since the database connection
          was opened.

   ---------- Footnotes ----------

   (1) https://sqlite.org/deterministic.html

   (2) https://www.sqlite.org/loadext.html#loading_an_extension

   (3) https://www.sqlite.org/c3ref/c_limit_attached.html

   (4) https://www.sqlite.org/c3ref/c_limit_attached.html

   (5) https://peps.python.org/pep-0249/

   (6) https://peps.python.org/pep-0249/

   (7) 
https://www.sqlite.org/lang_transaction.html#implicit_versus_explicit_transactions

   (8) https://peps.python.org/pep-0249/

   (9) 
https://www.sqlite.org/lang_transaction.html#implicit_versus_explicit_transactions

   (10) 
https://www.sqlite.org/lang_transaction.html#deferred_immediate_and_exclusive_transactions


File: python.info,  Node: Cursor 物件,  Next: Row 物件,  Prev: Connection 物件,  Up: Reference

5.12.6.6 Cursor 物件
....................

     A ‘Cursor’ object represents a database cursor(1) which is used to
     execute SQL statements, and manage the context of a fetch
     operation.  Cursors are created using *note Connection.cursor():
     27bc, or by using any of the *note connection shortcut methods:
     27f1.

     Cursor objects are *note iterators: 192, meaning that if you *note
     execute(): 2b3. a ‘SELECT’ query, you can simply iterate over the
     cursor to fetch the resulting rows:

          for row in cur.execute("SELECT t FROM data"):
              print(row)

 -- 類別: sqlite3.Cursor

     A *note Cursor: 27bd. instance has the following attributes and
     methods.

      -- 方法: execute (sql, parameters=(), /)

          Execute a single SQL statement, optionally binding Python
          values using *note placeholders: 2b5.


          參數:

             * ‘sql’ (*note str: 3f2.) - 單一個 SQL 陳述式。

             * ‘parameters’ (*note dict: 23b. | *note sequence: 499.) -
               Python values to bind to placeholders in 'sql'.  A ‘dict’
               if named placeholders are used.  A sequence if unnamed
               placeholders are used.  See *note How to use placeholders
               to bind values in SQL queries: 2b5.


          引發: *note ProgrammingError: 49a. - If 'sql' contains more
          than one SQL statement.

          If *note autocommit: 45d. is *note LEGACY_TRANSACTION_CONTROL:
          27cf, *note isolation_level: 27cd. is not ‘None’, 'sql' is an
          ‘INSERT’, ‘UPDATE’, ‘DELETE’, or ‘REPLACE’ statement, and
          there is no open transaction, a transaction is implicitly
          opened before executing 'sql'.

          Deprecated since version 3.12, will be removed in version
          3.14: *note DeprecationWarning: 18b. is emitted if *note named
          placeholders: 2b5. are used and 'parameters' is a sequence
          instead of a *note dict: 23b.  Starting with Python 3.14,
          *note ProgrammingError: 49a. will be raised instead.

          Use *note executescript(): 27f6. to execute multiple SQL
          statements.

      -- 方法: executemany (sql, parameters, /)

          For every item in 'parameters', repeatedly execute the *note
          parameterized: 2b5. DML (Data Manipulation Language) SQL
          statement 'sql'.

          Uses the same implicit transaction handling as *note
          execute(): 2b3.


          參數:

             * ‘sql’ (*note str: 3f2.) - A single SQL DML statement.

             * ‘parameters’ (*note iterable: 11bf.) - An iterable of
               parameters to bind with the placeholders in 'sql'.  See
               *note How to use placeholders to bind values in SQL
               queries: 2b5.


          引發: *note ProgrammingError: 49a. - If 'sql' contains more
          than one SQL statement, or is not a DML statement.

          範例：

               rows = [
                   ("row1",),
                   ("row2",),
               ]
               # cur 是一個 sqlite3.Cursor 物件
               cur.executemany("INSERT INTO data VALUES(?)", rows)

               備註: Any resulting rows are discarded, including DML
               statements with RETURNING clauses(2).

          Deprecated since version 3.12, will be removed in version
          3.14: *note DeprecationWarning: 18b. is emitted if *note named
          placeholders: 2b5. are used and the items in 'parameters' are
          sequences instead of *note dict: 23b.s.  Starting with Python
          3.14, *note ProgrammingError: 49a. will be raised instead.

      -- 方法: executescript (sql_script, /)

          Execute the SQL statements in 'sql_script'.  If the *note
          autocommit: 45d. is *note LEGACY_TRANSACTION_CONTROL: 27cf.
          and there is a pending transaction, an implicit ‘COMMIT’
          statement is executed first.  No other implicit transaction
          control is performed; any transaction control must be added to
          'sql_script'.

          'sql_script' must be a *note string: 3f2.

          範例：

               # cur 是一個 sqlite3.Cursor 物件
               cur.executescript("""
                   BEGIN;
                   CREATE TABLE person(firstname, lastname, age);
                   CREATE TABLE book(title, author, published);
                   CREATE TABLE publisher(name, address);
                   COMMIT;
               """)

      -- 方法: fetchone ()

          If *note row_factory: 27fd. is ‘None’, return the next row
          query result set as a *note tuple: 322.  Else, pass it to the
          row factory and return its result.  Return ‘None’ if no more
          data is available.

      -- 方法: fetchmany (size=cursor.arraysize)

          Return the next set of rows of a query result as a *note list:
          5b6.  Return an empty list if no more rows are available.

          The number of rows to fetch per call is specified by the
          'size' parameter.  If 'size' is not given, *note arraysize:
          2803. determines the number of rows to be fetched.  If fewer
          than 'size' rows are available, as many rows as are available
          are returned.

          Note there are performance considerations involved with the
          'size' parameter.  For optimal performance, it is usually best
          to use the arraysize attribute.  If the 'size' parameter is
          used, then it is best for it to retain the same value from one
          *note fetchmany(): 2802. call to the next.

      -- 方法: fetchall ()

          Return all (remaining) rows of a query result as a *note list:
          5b6.  Return an empty list if no rows are available.  Note
          that the *note arraysize: 2803. attribute can affect the
          performance of this operation.

      -- 方法: close ()

          Close the cursor now (rather than whenever ‘__del__’ is
          called).

          The cursor will be unusable from this point forward; a *note
          ProgrammingError: 49a. exception will be raised if any
          operation is attempted with the cursor.

      -- 方法: setinputsizes (sizes, /)

          Required by the DB-API. Does nothing in ‘sqlite3’.

      -- 方法: setoutputsize (size, column=None, /)

          Required by the DB-API. Does nothing in ‘sqlite3’.

      -- 屬性: arraysize

          Read/write attribute that controls the number of rows returned
          by *note fetchmany(): 2802.  The default value is 1 which
          means a single row would be fetched per call.

      -- 屬性: connection

          Read-only attribute that provides the SQLite database *note
          Connection: 22a. belonging to the cursor.  A *note Cursor:
          27bd. object created by calling *note con.cursor(): 27bc. will
          have a *note connection: 2807. attribute that refers to 'con':

               >>> con = sqlite3.connect(":memory:")
               >>> cur = con.cursor()
               >>> cur.connection == con
               True
               >>> con.close()

      -- 屬性: description

          Read-only attribute that provides the column names of the last
          query.  To remain compatible with the Python DB API, it
          returns a 7-tuple for each column where the last six items of
          each tuple are ‘None’.

          It is set for ‘SELECT’ statements without any matching rows as
          well.

      -- 屬性: lastrowid

          Read-only attribute that provides the row id of the last
          inserted row.  It is only updated after successful ‘INSERT’ or
          ‘REPLACE’ statements using the *note execute(): 2b3. method.
          For other statements, after *note executemany(): 2b4. or *note
          executescript(): 27f6, or if the insertion failed, the value
          of ‘lastrowid’ is left unchanged.  The initial value of
          ‘lastrowid’ is ‘None’.

               備註: Inserts into ‘WITHOUT ROWID’ tables are not
               recorded.

          在 3.6 版的變更: 新增 ‘REPLACE’ 陳述式的支援。

      -- 屬性: rowcount

          Read-only attribute that provides the number of modified rows
          for ‘INSERT’, ‘UPDATE’, ‘DELETE’, and ‘REPLACE’ statements; is
          ‘-1’ for other statements, including CTE (Common Table
          Expression) queries.  It is only updated by the *note
          execute(): 2b3. and *note executemany(): 2b4. methods, after
          the statement has run to completion.  This means that any
          resulting rows must be fetched in order for ‘rowcount’ to be
          updated.

      -- 屬性: row_factory

          Control how a row fetched from this ‘Cursor’ is represented.
          If ‘None’, a row is represented as a *note tuple: 322.  Can be
          set to the included *note sqlite3.Row: e13.; or a *note
          callable: 27d4. that accepts two arguments, a *note Cursor:
          27bd. object and the ‘tuple’ of row values, and returns a
          custom object representing an SQLite row.

          Defaults to what *note Connection.row_factory: 1522. was set
          to when the ‘Cursor’ was created.  Assigning to this attribute
          does not affect *note Connection.row_factory: 1522. of the
          parent connection.

          更多詳情請見 *note How to create and use row factories: 27c4.。

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Cursor_(databases)

   (2) https://www.sqlite.org/lang_returning.html


File: python.info,  Node: Row 物件,  Next: Blob 物件,  Prev: Cursor 物件,  Up: Reference

5.12.6.7 Row 物件
.................

 -- 類別: sqlite3.Row

     A ‘Row’ instance serves as a highly optimized *note row_factory:
     1522. for *note Connection: 22a. objects.  It supports iteration,
     equality testing, *note len(): 5d4, and *note mapping: 1154. access
     by column name and index.

     Two ‘Row’ objects compare equal if they have identical column names
     and values.

     更多詳情請見 *note How to create and use row factories: 27c4.。

      -- 方法: keys ()

          Return a *note list: 5b6. of column names as *note strings:
          3f2.  Immediately after a query, it is the first member of
          each tuple in *note Cursor.description: 2808.

     在 3.5 版的變更: 新增對切片的支援。


File: python.info,  Node: Blob 物件,  Next: PrepareProtocol 物件,  Prev: Row 物件,  Up: Reference

5.12.6.8 Blob 物件
..................

 -- 類別: sqlite3.Blob

     在 3.11 版被加入.

     A *note Blob: 628. instance is a *note file-like object: 246a. that
     can read and write data in an SQLite BLOB.  Call *note len(blob):
     5d4. to get the size (number of bytes) of the blob.  Use indices
     and *note slices: 2059. for direct access to the blob data.

     Use the *note Blob: 628. as a *note context manager: 576. to ensure
     that the blob handle is closed after use.

          con = sqlite3.connect(":memory:")
          con.execute("CREATE TABLE test(blob_col blob)")
          con.execute("INSERT INTO test(blob_col) VALUES(zeroblob(13))")

          # Write to our blob, using two write operations:
          with con.blobopen("test", "blob_col", 1) as blob:
              blob.write(b"hello, ")
              blob.write(b"world.")
              # Modify the first and last bytes of our blob
              blob[0] = ord("H")
              blob[-1] = ord("!")

          # Read the contents of our blob
          with con.blobopen("test", "blob_col", 1) as blob:
              greeting = blob.read()

          print(greeting)  # outputs "b'Hello, world!'"
          con.close()

      -- 方法: close ()

          Close the blob.

          The blob will be unusable from this point onward.  An *note
          Error: 1783. (or subclass) exception will be raised if any
          further operation is attempted with the blob.

      -- 方法: read (length=-1, /)

          Read 'length' bytes of data from the blob at the current
          offset position.  If the end of the blob is reached, the data
          up to EOF (End of File) will be returned.  When 'length' is
          not specified, or is negative, *note read(): 2810. will read
          until the end of the blob.

      -- 方法: write (data, /)

          Write 'data' to the blob at the current offset.  This function
          cannot change the blob length.  Writing beyond the end of the
          blob will raise *note ValueError: 1e7.

      -- 方法: tell ()

          Return the current access position of the blob.

      -- 方法: seek (offset, origin=os.SEEK_SET, /)

          Set the current access position of the blob to 'offset'.  The
          'origin' argument defaults to *note os.SEEK_SET: 1225.
          (absolute blob positioning).  Other values for 'origin' are
          *note os.SEEK_CUR: 1226. (seek relative to the current
          position) and *note os.SEEK_END: 1227. (seek relative to the
          blob’s end).


File: python.info,  Node: PrepareProtocol 物件,  Next: 例外<4>,  Prev: Blob 物件,  Up: Reference

5.12.6.9 PrepareProtocol 物件
.............................

 -- 類別: sqlite3.PrepareProtocol

     The PrepareProtocol type's single purpose is to act as a PEP 246(1)
     style adaption protocol for objects that can *note adapt
     themselves: 2815. to *note native SQLite types: 27c9.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0246/


File: python.info,  Node: 例外<4>,  Next: SQLite and Python types,  Prev: PrepareProtocol 物件,  Up: Reference

5.12.6.10 例外
..............

The exception hierarchy is defined by the DB-API 2.0 ( PEP 249(1)).

 -- 例外: sqlite3.Warning

     This exception is not currently raised by the ‘sqlite3’ module, but
     may be raised by applications using ‘sqlite3’, for example if a
     user-defined function truncates data while inserting.  ‘Warning’ is
     a subclass of *note Exception: 97d.

 -- 例外: sqlite3.Error

     The base class of the other exceptions in this module.  Use this to
     catch all errors with one single *note except: 171. statement.
     ‘Error’ is a subclass of *note Exception: 97d.

     If the exception originated from within the SQLite library, the
     following two attributes are added to the exception:

      -- 屬性: sqlite_errorcode

          The numeric error code from the SQLite API(2)

          在 3.11 版被加入.

      -- 屬性: sqlite_errorname

          The symbolic name of the numeric error code from the SQLite
          API(3)

          在 3.11 版被加入.

 -- 例外: sqlite3.InterfaceError

     Exception raised for misuse of the low-level SQLite C API. In other
     words, if this exception is raised, it probably indicates a bug in
     the ‘sqlite3’ module.  ‘InterfaceError’ is a subclass of *note
     Error: 1783.

 -- 例外: sqlite3.DatabaseError

     Exception raised for errors that are related to the database.  This
     serves as the base exception for several types of database errors.
     It is only raised implicitly through the specialised subclasses.
     ‘DatabaseError’ is a subclass of *note Error: 1783.

 -- 例外: sqlite3.DataError

     Exception raised for errors caused by problems with the processed
     data, like numeric values out of range, and strings which are too
     long.  ‘DataError’ is a subclass of *note DatabaseError: 27fa.

 -- 例外: sqlite3.OperationalError

     Exception raised for errors that are related to the database's
     operation, and not necessarily under the control of the programmer.
     For example, the database path is not found, or a transaction could
     not be processed.  ‘OperationalError’ is a subclass of *note
     DatabaseError: 27fa.

 -- 例外: sqlite3.IntegrityError

     Exception raised when the relational integrity of the database is
     affected, e.g.  a foreign key check fails.  It is a subclass of
     *note DatabaseError: 27fa.

 -- 例外: sqlite3.InternalError

     Exception raised when SQLite encounters an internal error.  If this
     is raised, it may indicate that there is a problem with the runtime
     SQLite library.  ‘InternalError’ is a subclass of *note
     DatabaseError: 27fa.

 -- 例外: sqlite3.ProgrammingError

     Exception raised for ‘sqlite3’ API programming errors, for example
     supplying the wrong number of bindings to a query, or trying to
     operate on a closed *note Connection: 22a.  ‘ProgrammingError’ is a
     subclass of *note DatabaseError: 27fa.

 -- 例外: sqlite3.NotSupportedError

     Exception raised in case a method or database API is not supported
     by the underlying SQLite library.  For example, setting
     'deterministic' to ‘True’ in *note create_function(): 289, if the
     underlying SQLite library does not support deterministic functions.
     ‘NotSupportedError’ is a subclass of *note DatabaseError: 27fa.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0249/

   (2) https://sqlite.org/rescode.html

   (3) https://sqlite.org/rescode.html


File: python.info,  Node: SQLite and Python types,  Next: Default adapters and converters deprecated,  Prev: 例外<4>,  Up: Reference

5.12.6.11 SQLite and Python types
.................................

SQLite natively supports the following types: ‘NULL’, ‘INTEGER’, ‘REAL’,
‘TEXT’, ‘BLOB’.

The following Python types can thus be sent to SQLite without any
problem:

Python type                         SQLite type
                                    
------------------------------------------------------
                                    
‘None’                              ‘NULL’
                                    
                                    
*note int: 23c.                     ‘INTEGER’
                                    
                                    
*note float: 2c8.                   ‘REAL’
                                    
                                    
*note str: 3f2.                     ‘TEXT’
                                    
                                    
*note bytes: 1a5.                   ‘BLOB’
                                    

This is how SQLite types are converted to Python types by default:

SQLite type       Python type
                  
---------------------------------------------------------------------
                  
‘NULL’            ‘None’
                  
                  
‘INTEGER’         *note int: 23c.
                  
                  
‘REAL’            *note float: 2c8.
                  
                  
‘TEXT’            depends on *note text_factory: 27fe,
                  *note str: 3f2. by default
                  
                  
‘BLOB’            *note bytes: 1a5.
                  

The type system of the ‘sqlite3’ module is extensible in two ways: you
can store additional Python types in an SQLite database via *note object
adapters: 27c2, and you can let the ‘sqlite3’ module convert SQLite
types to Python types via *note converters: 27c3.


File: python.info,  Node: Default adapters and converters deprecated,  Next: 命令列介面,  Prev: SQLite and Python types,  Up: Reference

5.12.6.12 Default adapters and converters (deprecated)
......................................................

     備註: The default adapters and converters are deprecated as of
     Python 3.12.  Instead, use the *note Adapter and converter recipes:
     498. and tailor them to your needs.

The deprecated default adapters and converters consist of:

   * An adapter for *note datetime.date: 1b1. objects to *note strings:
     3f2. in ISO 8601(1) format.

   * An adapter for *note datetime.datetime: 1b0. objects to strings in
     ISO 8601 format.

   * A converter for *note declared: 27c3. "date" types to *note
     datetime.date: 1b1. objects.

   * A converter for declared "timestamp" types to *note
     datetime.datetime: 1b0. objects.  Fractional parts will be
     truncated to 6 digits (microsecond precision).

     備註: The default "timestamp" converter ignores UTC offsets in the
     database and always returns a naive *note datetime.datetime: 1b0.
     object.  To preserve UTC offsets in timestamps, either leave
     converters disabled, or register an offset-aware converter with
     *note register_converter(): 27ca.

在 3.12 版之後被棄用.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/ISO_8601


File: python.info,  Node: 命令列介面,  Prev: Default adapters and converters deprecated,  Up: Reference

5.12.6.13 命令列介面
....................

The ‘sqlite3’ module can be invoked as a script, using the interpreter's
*note -m: 585. switch, in order to provide a simple SQLite shell.  The
argument signature is as follows:

     python -m sqlite3 [-h] [-v] [filename] [sql]

Type ‘.quit’ or CTRL-D to exit the shell.

 -- Option: -h, --help

     Print CLI help.

 -- Option: -v, --version

     Print underlying SQLite library version.

在 3.12 版被加入.


File: python.info,  Node: How-to guides,  Next: 解釋,  Prev: Reference,  Up: sqlite3 --- SQLite 資料庫的 DB-API 2 0 介面

5.12.6.14 How-to guides
.......................

* Menu:

* How to use placeholders to bind values in SQL queries::
* How to adapt custom Python types to SQLite values::
* How to convert SQLite values to custom Python types::
* Adapter and converter recipes::
* How to use connection shortcut methods::
* How to use the connection context manager::
* How to work with SQLite URIs::
* How to create and use row factories::
* How to handle non-UTF-8 text encodings::


File: python.info,  Node: How to use placeholders to bind values in SQL queries,  Next: How to adapt custom Python types to SQLite values,  Up: How-to guides

5.12.6.15 How to use placeholders to bind values in SQL queries
...............................................................

SQL operations usually need to use values from Python variables.
However, beware of using Python's string operations to assemble queries,
as they are vulnerable to SQL injection attacks(1).  For example, an
attacker can simply close the single quote and inject ‘OR TRUE’ to
select all rows:

     >>> # Never do this -- insecure!
     >>> symbol = input()
     ' OR TRUE; --
     >>> sql = "SELECT * FROM stocks WHERE symbol = '%s'" % symbol
     >>> print(sql)
     SELECT * FROM stocks WHERE symbol = '' OR TRUE; --'
     >>> cur.execute(sql)

Instead, use the DB-API's parameter substitution.  To insert a variable
into a query string, use a placeholder in the string, and substitute the
actual values into the query by providing them as a *note tuple: 322. of
values to the second argument of the cursor's *note execute(): 2b3.
method.

An SQL statement may use one of two kinds of placeholders: question
marks (qmark style) or named placeholders (named style).  For the qmark
style, 'parameters' must be a *note sequence: 499. whose length must
match the number of placeholders, or a *note ProgrammingError: 49a. is
raised.  For the named style, 'parameters' must be an instance of a
*note dict: 23b. (or a subclass), which must contain keys for all named
parameters; any extra items are ignored.  Here's an example of both
styles:

     con = sqlite3.connect(":memory:")
     cur = con.execute("CREATE TABLE lang(name, first_appeared)")

     # This is the named style used with executemany():
     data = (
         {"name": "C", "year": 1972},
         {"name": "Fortran", "year": 1957},
         {"name": "Python", "year": 1991},
         {"name": "Go", "year": 2009},
     )
     cur.executemany("INSERT INTO lang VALUES(:name, :year)", data)

     # This is the qmark style used in a SELECT query:
     params = (1972,)
     cur.execute("SELECT * FROM lang WHERE first_appeared = ?", params)
     print(cur.fetchall())
     con.close()

     備註: PEP 249(2) numeric placeholders are 'not' supported.  If
     used, they will be interpreted as named placeholders.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/SQL_injection

   (2) https://peps.python.org/pep-0249/


File: python.info,  Node: How to adapt custom Python types to SQLite values,  Next: How to convert SQLite values to custom Python types,  Prev: How to use placeholders to bind values in SQL queries,  Up: How-to guides

5.12.6.16 How to adapt custom Python types to SQLite values
...........................................................

SQLite supports only a limited set of data types natively.  To store
custom Python types in SQLite databases, 'adapt' them to one of the
*note Python types SQLite natively understands: 27c9.

There are two ways to adapt Python objects to SQLite types: letting your
object adapt itself, or using an 'adapter callable'.  The latter will
take precedence above the former.  For a library that exports a custom
type, it may make sense to enable that type to adapt itself.  As an
application developer, it may make more sense to take direct control by
registering custom adapter functions.

* Menu:

* How to write adaptable objects::
* How to register adapter callables::


File: python.info,  Node: How to write adaptable objects,  Next: How to register adapter callables,  Up: How to adapt custom Python types to SQLite values

5.12.6.17 How to write adaptable objects
........................................

Suppose we have a ‘Point’ class that represents a pair of coordinates,
‘x’ and ‘y’, in a Cartesian coordinate system.  The coordinate pair will
be stored as a text string in the database, using a semicolon to
separate the coordinates.  This can be implemented by adding a
‘__conform__(self, protocol)’ method which returns the adapted value.
The object passed to 'protocol' will be of type *note PrepareProtocol:
16e7.

     class Point:
         def __init__(self, x, y):
             self.x, self.y = x, y

         def __conform__(self, protocol):
             if protocol is sqlite3.PrepareProtocol:
                 return f"{self.x};{self.y}"

     con = sqlite3.connect(":memory:")
     cur = con.cursor()

     cur.execute("SELECT ?", (Point(4.0, -3.2),))
     print(cur.fetchone()[0])
     con.close()


File: python.info,  Node: How to register adapter callables,  Prev: How to write adaptable objects,  Up: How to adapt custom Python types to SQLite values

5.12.6.18 How to register adapter callables
...........................................

The other possibility is to create a function that converts the Python
object to an SQLite-compatible type.  This function can then be
registered using *note register_adapter(): 27d3.

     class Point:
         def __init__(self, x, y):
             self.x, self.y = x, y

     def adapt_point(point):
         return f"{point.x};{point.y}"

     sqlite3.register_adapter(Point, adapt_point)

     con = sqlite3.connect(":memory:")
     cur = con.cursor()

     cur.execute("SELECT ?", (Point(1.0, 2.5),))
     print(cur.fetchone()[0])
     con.close()


File: python.info,  Node: How to convert SQLite values to custom Python types,  Next: Adapter and converter recipes,  Prev: How to adapt custom Python types to SQLite values,  Up: How-to guides

5.12.6.19 How to convert SQLite values to custom Python types
.............................................................

Writing an adapter lets you convert 'from' custom Python types 'to'
SQLite values.  To be able to convert 'from' SQLite values 'to' custom
Python types, we use 'converters'.

Let's go back to the ‘Point’ class.  We stored the x and y coordinates
separated via semicolons as strings in SQLite.

First, we'll define a converter function that accepts the string as a
parameter and constructs a ‘Point’ object from it.

     備註: Converter functions are 'always' passed a *note bytes: 1a5.
     object, no matter the underlying SQLite data type.

     def convert_point(s):
         x, y = map(float, s.split(b";"))
         return Point(x, y)

We now need to tell ‘sqlite3’ when it should convert a given SQLite
value.  This is done when connecting to a database, using the
'detect_types' parameter of *note connect(): 288.  There are three
options:

   * Implicit: set 'detect_types' to *note PARSE_DECLTYPES: 27cb.

   * Explicit: set 'detect_types' to *note PARSE_COLNAMES: 27cc.

   * Both: set 'detect_types' to ‘sqlite3.PARSE_DECLTYPES |
     sqlite3.PARSE_COLNAMES’.  Column names take precedence over
     declared types.

The following example illustrates the implicit and explicit approaches:

     class Point:
         def __init__(self, x, y):
             self.x, self.y = x, y

         def __repr__(self):
             return f"Point({self.x}, {self.y})"

     def adapt_point(point):
         return f"{point.x};{point.y}"

     def convert_point(s):
         x, y = list(map(float, s.split(b";")))
         return Point(x, y)

     # Register the adapter and converter
     sqlite3.register_adapter(Point, adapt_point)
     sqlite3.register_converter("point", convert_point)

     # 1) Parse using declared types
     p = Point(4.0, -3.2)
     con = sqlite3.connect(":memory:", detect_types=sqlite3.PARSE_DECLTYPES)
     cur = con.execute("CREATE TABLE test(p point)")

     cur.execute("INSERT INTO test(p) VALUES(?)", (p,))
     cur.execute("SELECT p FROM test")
     print("with declared types:", cur.fetchone()[0])
     cur.close()
     con.close()

     # 2) Parse using column names
     con = sqlite3.connect(":memory:", detect_types=sqlite3.PARSE_COLNAMES)
     cur = con.execute("CREATE TABLE test(p)")

     cur.execute("INSERT INTO test(p) VALUES(?)", (p,))
     cur.execute('SELECT p AS "p [point]" FROM test')
     print("with column names:", cur.fetchone()[0])
     cur.close()
     con.close()


File: python.info,  Node: Adapter and converter recipes,  Next: How to use connection shortcut methods,  Prev: How to convert SQLite values to custom Python types,  Up: How-to guides

5.12.6.20 Adapter and converter recipes
.......................................

This section shows recipes for common adapters and converters.

     import datetime
     import sqlite3

     def adapt_date_iso(val):
         """Adapt datetime.date to ISO 8601 date."""
         return val.isoformat()

     def adapt_datetime_iso(val):
         """Adapt datetime.datetime to timezone-naive ISO 8601 date."""
         return val.isoformat()

     def adapt_datetime_epoch(val):
         """Adapt datetime.datetime to Unix timestamp."""
         return int(val.timestamp())

     sqlite3.register_adapter(datetime.date, adapt_date_iso)
     sqlite3.register_adapter(datetime.datetime, adapt_datetime_iso)
     sqlite3.register_adapter(datetime.datetime, adapt_datetime_epoch)

     def convert_date(val):
         """Convert ISO 8601 date to datetime.date object."""
         return datetime.date.fromisoformat(val.decode())

     def convert_datetime(val):
         """Convert ISO 8601 datetime to datetime.datetime object."""
         return datetime.datetime.fromisoformat(val.decode())

     def convert_timestamp(val):
         """Convert Unix epoch timestamp to datetime.datetime object."""
         return datetime.datetime.fromtimestamp(int(val))

     sqlite3.register_converter("date", convert_date)
     sqlite3.register_converter("datetime", convert_datetime)
     sqlite3.register_converter("timestamp", convert_timestamp)


File: python.info,  Node: How to use connection shortcut methods,  Next: How to use the connection context manager,  Prev: Adapter and converter recipes,  Up: How-to guides

5.12.6.21 How to use connection shortcut methods
................................................

Using the *note execute(): 27f3, *note executemany(): 27f4, and *note
executescript(): 27f5. methods of the *note Connection: 22a. class, your
code can be written more concisely because you don't have to create the
(often superfluous) *note Cursor: 27bd. objects explicitly.  Instead,
the *note Cursor: 27bd. objects are created implicitly and these
shortcut methods return the cursor objects.  This way, you can execute a
‘SELECT’ statement and iterate over it directly using only a single call
on the *note Connection: 22a. object.

     # Create and fill the table.
     con = sqlite3.connect(":memory:")
     con.execute("CREATE TABLE lang(name, first_appeared)")
     data = [
         ("C++", 1985),
         ("Objective-C", 1984),
     ]
     con.executemany("INSERT INTO lang(name, first_appeared) VALUES(?, ?)", data)

     # Print the table contents
     for row in con.execute("SELECT name, first_appeared FROM lang"):
         print(row)

     print("I just deleted", con.execute("DELETE FROM lang").rowcount, "rows")

     # close() is not a shortcut method and it's not called automatically;
     # the connection object should be closed manually
     con.close()


File: python.info,  Node: How to use the connection context manager,  Next: How to work with SQLite URIs,  Prev: How to use connection shortcut methods,  Up: How-to guides

5.12.6.22 How to use the connection context manager
...................................................

A *note Connection: 22a. object can be used as a context manager that
automatically commits or rolls back open transactions when leaving the
body of the context manager.  If the body of the *note with: 577.
statement finishes without exceptions, the transaction is committed.  If
this commit fails, or if the body of the ‘with’ statement raises an
uncaught exception, the transaction is rolled back.  If *note
autocommit: 45d. is ‘False’, a new transaction is implicitly opened
after committing or rolling back.

If there is no open transaction upon leaving the body of the ‘with’
statement, or if *note autocommit: 45d. is ‘True’, the context manager
does nothing.

     備註: The context manager neither implicitly opens a new
     transaction nor closes the connection.  If you need a closing
     context manager, consider using *note contextlib.closing(): 282a.

     con = sqlite3.connect(":memory:")
     con.execute("CREATE TABLE lang(id INTEGER PRIMARY KEY, name VARCHAR UNIQUE)")

     # Successful, con.commit() is called automatically afterwards
     with con:
         con.execute("INSERT INTO lang(name) VALUES(?)", ("Python",))

     # con.rollback() is called after the with block finishes with an exception,
     # the exception is still raised and must be caught
     try:
         with con:
             con.execute("INSERT INTO lang(name) VALUES(?)", ("Python",))
     except sqlite3.IntegrityError:
         print("couldn't add Python twice")

     # Connection object used as context manager only commits or rollbacks transactions,
     # so the connection object should be closed manually
     con.close()


File: python.info,  Node: How to work with SQLite URIs,  Next: How to create and use row factories,  Prev: How to use the connection context manager,  Up: How-to guides

5.12.6.23 How to work with SQLite URIs
......................................

Some useful URI tricks include:

   * Open a database in read-only mode:

     >>> con = sqlite3.connect("file:tutorial.db?mode=ro", uri=True)
     >>> con.execute("CREATE TABLE readonly(data)")
     Traceback (most recent call last):
     OperationalError: attempt to write a readonly database

   * Do not implicitly create a new database file if it does not already
     exist; will raise *note OperationalError: 17a0. if unable to create
     a new file:

     >>> con = sqlite3.connect("file:nosuchdb.db?mode=rw", uri=True)
     Traceback (most recent call last):
     OperationalError: unable to open database file

   * Create a shared named in-memory database:

     db = "file:mem1?mode=memory&cache=shared"
     con1 = sqlite3.connect(db, uri=True)
     con2 = sqlite3.connect(db, uri=True)
     with con1:
         con1.execute("CREATE TABLE shared(data)")
         con1.execute("INSERT INTO shared VALUES(28)")
     res = con2.execute("SELECT data FROM shared")
     assert res.fetchone() == (28,)

     con1.close()
     con2.close()

More information about this feature, including a list of parameters, can
be found in the SQLite URI documentation(1).

   ---------- Footnotes ----------

   (1) https://www.sqlite.org/uri.html


File: python.info,  Node: How to create and use row factories,  Next: How to handle non-UTF-8 text encodings,  Prev: How to work with SQLite URIs,  Up: How-to guides

5.12.6.24 How to create and use row factories
.............................................

By default, ‘sqlite3’ represents each row as a *note tuple: 322.  If a
‘tuple’ does not suit your needs, you can use the *note sqlite3.Row:
e13. class or a custom *note row_factory: 27fd.

While ‘row_factory’ exists as an attribute both on the *note Cursor:
27bd. and the *note Connection: 22a, it is recommended to set *note
Connection.row_factory: 1522, so all cursors created from the connection
will use the same row factory.

‘Row’ provides indexed and case-insensitive named access to columns,
with minimal memory overhead and performance impact over a ‘tuple’.  To
use ‘Row’ as a row factory, assign it to the ‘row_factory’ attribute:

     >>> con = sqlite3.connect(":memory:")
     >>> con.row_factory = sqlite3.Row

Queries now return ‘Row’ objects:

     >>> res = con.execute("SELECT 'Earth' AS name, 6378 AS radius")
     >>> row = res.fetchone()
     >>> row.keys()
     ['name', 'radius']
     >>> row[0]         # Access by index.
     'Earth'
     >>> row["name"]    # Access by name.
     'Earth'
     >>> row["RADIUS"]  # Column names are case-insensitive.
     6378
     >>> con.close()

     備註: The ‘FROM’ clause can be omitted in the ‘SELECT’ statement,
     as in the above example.  In such cases, SQLite returns a single
     row with columns defined by expressions, e.g.  literals, with the
     given aliases ‘expr AS alias’.

You can create a custom *note row_factory: 27fd. that returns each row
as a *note dict: 23b, with column names mapped to values:

     def dict_factory(cursor, row):
         fields = [column[0] for column in cursor.description]
         return {key: value for key, value in zip(fields, row)}

Using it, queries now return a ‘dict’ instead of a ‘tuple’:

     >>> con = sqlite3.connect(":memory:")
     >>> con.row_factory = dict_factory
     >>> for row in con.execute("SELECT 1 AS a, 2 AS b"):
     ...     print(row)
     {'a': 1, 'b': 2}
     >>> con.close()

The following row factory returns a *note named tuple: 5f4.:

     from collections import namedtuple

     def namedtuple_factory(cursor, row):
         fields = [column[0] for column in cursor.description]
         cls = namedtuple("Row", fields)
         return cls._make(row)

‘namedtuple_factory()’ can be used as follows:

     >>> con = sqlite3.connect(":memory:")
     >>> con.row_factory = namedtuple_factory
     >>> cur = con.execute("SELECT 1 AS a, 2 AS b")
     >>> row = cur.fetchone()
     >>> row
     Row(a=1, b=2)
     >>> row[0]  # Indexed access.
     1
     >>> row.b   # Attribute access.
     2
     >>> con.close()

With some adjustments, the above recipe can be adapted to use a *note
dataclass: 1af, or any other custom class, instead of a *note
namedtuple: 1ae.


File: python.info,  Node: How to handle non-UTF-8 text encodings,  Prev: How to create and use row factories,  Up: How-to guides

5.12.6.25 How to handle non-UTF-8 text encodings
................................................

By default, ‘sqlite3’ uses *note str: 3f2. to adapt SQLite values with
the ‘TEXT’ data type.  This works well for UTF-8 encoded text, but it
might fail for other encodings and invalid UTF-8.  You can use a custom
*note text_factory: 27fe. to handle such cases.

Because of SQLite's flexible typing(1), it is not uncommon to encounter
table columns with the ‘TEXT’ data type containing non-UTF-8 encodings,
or even arbitrary data.  To demonstrate, let's assume we have a database
with ISO-8859-2 (Latin-2) encoded text, for example a table of
Czech-English dictionary entries.  Assuming we now have a *note
Connection: 22a. instance ‘con’ connected to this database, we can
decode the Latin-2 encoded text using this *note text_factory: 27fe.:

     con.text_factory = lambda data: str(data, encoding="latin2")

For invalid UTF-8 or arbitrary data in stored in ‘TEXT’ table columns,
you can use the following technique, borrowed from the *note Unicode
HOWTO: 123b.:

     con.text_factory = lambda data: str(data, errors="surrogateescape")

     備註: The ‘sqlite3’ module API does not support strings containing
     surrogates.

也參考
......

*note Unicode HOWTO: 123b.

   ---------- Footnotes ----------

   (1) https://www.sqlite.org/flextypegood.html


File: python.info,  Node: 解釋,  Prev: How-to guides,  Up: sqlite3 --- SQLite 資料庫的 DB-API 2 0 介面

5.12.6.26 解釋
..............

* Menu:

* Transaction control::


File: python.info,  Node: Transaction control,  Up: 解釋

5.12.6.27 Transaction control
.............................

‘sqlite3’ offers multiple methods of controlling whether, when and how
database transactions are opened and closed.  *note Transaction control
via the autocommit attribute: 45e. is recommended, while *note
Transaction control via the isolation_level attribute: 27ce. retains the
pre-Python 3.12 behaviour.

* Menu:

* Transaction control via the autocommit attribute::
* Transaction control via the isolation_level attribute::


File: python.info,  Node: Transaction control via the autocommit attribute,  Next: Transaction control via the isolation_level attribute,  Up: Transaction control

5.12.6.28 Transaction control via the ‘autocommit’ attribute
............................................................

The recommended way of controlling transaction behaviour is through the
*note Connection.autocommit: 45d. attribute, which should preferably be
set using the 'autocommit' parameter of *note connect(): 288.

It is suggested to set 'autocommit' to ‘False’, which implies PEP
249(1)-compliant transaction control.  This means:

   * ‘sqlite3’ ensures that a transaction is always open, so *note
     connect(): 288, *note Connection.commit(): 27c0, and *note
     Connection.rollback(): 27f2. will implicitly open a new transaction
     (immediately after closing the pending one, for the latter two).
     ‘sqlite3’ uses ‘BEGIN DEFERRED’ statements when opening
     transactions.

   * Transactions should be committed explicitly using ‘commit()’.

   * Transactions should be rolled back explicitly using ‘rollback()’.

   * An implicit rollback is performed if the database is *note close():
     22b.-ed with pending changes.

Set 'autocommit' to ‘True’ to enable SQLite's autocommit mode(2).  In
this mode, *note Connection.commit(): 27c0. and *note
Connection.rollback(): 27f2. have no effect.  Note that SQLite's
autocommit mode is distinct from the PEP 249(3)-compliant *note
Connection.autocommit: 45d. attribute; use *note
Connection.in_transaction: 27fc. to query the low-level SQLite
autocommit mode.

Set 'autocommit' to *note LEGACY_TRANSACTION_CONTROL: 27cf. to leave
transaction control behaviour to the *note Connection.isolation_level:
27cd. attribute.  See *note Transaction control via the isolation_level
attribute: 27ce. for more information.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0249/

   (2) 
https://www.sqlite.org/lang_transaction.html#implicit_versus_explicit_transactions

   (3) https://peps.python.org/pep-0249/


File: python.info,  Node: Transaction control via the isolation_level attribute,  Prev: Transaction control via the autocommit attribute,  Up: Transaction control

5.12.6.29 Transaction control via the ‘isolation_level’ attribute
.................................................................

     備註: The recommended way of controlling transactions is via the
     *note autocommit: 45d. attribute.  See *note Transaction control
     via the autocommit attribute: 45e.

If *note Connection.autocommit: 45d. is set to *note
LEGACY_TRANSACTION_CONTROL: 27cf. (the default), transaction behaviour
is controlled using the *note Connection.isolation_level: 27cd.
attribute.  Otherwise, ‘isolation_level’ has no effect.

If the connection attribute *note isolation_level: 27cd. is not ‘None’,
new transactions are implicitly opened before *note execute(): 2b3. and
*note executemany(): 2b4. executes ‘INSERT’, ‘UPDATE’, ‘DELETE’, or
‘REPLACE’ statements; for other statements, no implicit transaction
handling is performed.  Use the *note commit(): 27c0. and *note
rollback(): 27f2. methods to respectively commit and roll back pending
transactions.  You can choose the underlying SQLite transaction
behaviour(1) — that is, whether and what type of ‘BEGIN’ statements
‘sqlite3’ implicitly executes – via the *note isolation_level: 27cd.
attribute.

If *note isolation_level: 27cd. is set to ‘None’, no transactions are
implicitly opened at all.  This leaves the underlying SQLite library in
autocommit mode(2), but also allows the user to perform their own
transaction handling using explicit SQL statements.  The underlying
SQLite library autocommit mode can be queried using the *note
in_transaction: 27fc. attribute.

The *note executescript(): 27f6. method implicitly commits any pending
transaction before execution of the given SQL script, regardless of the
value of *note isolation_level: 27cd.

在 3.6 版的變更: ‘sqlite3’ used to implicitly commit an open transaction
before DDL statements.  This is no longer the case.

在 3.12 版的變更: The recommended way of controlling transactions is now
via the *note autocommit: 45d. attribute.

   ---------- Footnotes ----------

   (1) 
https://www.sqlite.org/lang_transaction.html#deferred_immediate_and_exclusive_transactions

   (2) 
https://www.sqlite.org/lang_transaction.html#implicit_versus_explicit_transactions


File: python.info,  Node: 資料壓縮與保存,  Next: 檔案格式,  Prev: 資料持久性 Data Persistence,  Up: Python 標準函式庫 Standard Library

5.13 資料壓縮與保存
===================

本章中描述的模組支援使用 zlib、gzip、bzip2 和 lzma 演算法進行資料壓縮，
以及建立 ZIP 和 tar 格式的存檔。另請參閱 *note shutil: b3. 模組提供的
*note Archiving operations: 11b0.。

* Menu:

* zlib: zlib --- 相容於 gzip 的壓縮. 相容於 gzip 的壓縮
* gzip: gzip --- gzip 檔案的支援. gzip 檔案的支援
* bz2: bz2 --- bzip2 壓縮的支援. bzip2 壓縮的支援
* lzma: lzma --- 使用 LZMA 演算法進行壓縮. 使用 LZMA 演算法進行壓縮
* zipfile: zipfile --- 處理 ZIP 封存檔案. 處理 ZIP 封存檔案
* tarfile: tarfile --- 讀取與寫入 tar 封存檔案. 讀取與寫入 tar 封存檔案


File: python.info,  Node: zlib --- 相容於 gzip 的壓縮,  Next: gzip --- gzip 檔案的支援,  Up: 資料壓縮與保存

5.13.1 ‘zlib’ -- 相容於 ‘gzip’ 的壓縮
-------------------------------------

__________________________________________________________________

對於需要資料壓縮的應用程式，此模組提供了能夠使用 zlib 函式庫進行壓縮和解
壓縮的函式。zlib 函式庫有自己的主頁 ‘https://www.zlib.net’。已知 Python
模組與早於 1.1.3 的 zlib 函式庫版本之間並不相容；1.1.3 存在安全漏洞(1)，
因此我們建議使用 1.1.4 或更新的版本。

zlib 的函式有很多選項，且通常需要按特定順序使用。本文件並不打算解說所有
選項排列組合的效果；相關官方資訊，請參閱
‘http://www.zlib.net/manual.html’ 上的 zlib 手冊。

若要讀寫 ‘.gz’ 文件，請參閱 *note gzip: 5d. 模組。

該模組中可用的例外和函式是：

 -- 例外: zlib.error

     當壓縮和解壓縮發生錯誤時引發的例外。

 -- 函式: zlib.adler32 (data[, value])

     計算 'data' 的 Adler-32 核對和 (checksum)。（Adler-32 核對和幾乎與
     CRC32 一樣可靠，但計算速度更快。）結果是一個 unsigned（無符號的）
     32-bit 整數。如果有提供 'value'，則將其用作核對和的起始值，否則使用
     預設值 1。傳入 'value' 允許了於多個輸入的串聯 (concatenation) 上計
     算核對和。該演算法的加密強度不夠高，不該用於身份驗證
     (authentication) 或數位簽章 (digital signature)。由於該演算法是為核
     對和演算法而設計的，它並不適合作為通用的雜湊演算法。

     在 3.0 版的變更: 結果總是為 unsigned。

 -- 函式: zlib.compress (data, /, level=-1, wbits=MAX_WBITS)

     壓縮 'data' 中的位元組，回傳一個包含壓縮資料的位元組物件。 'level'
     是從 ‘0’ 到 ‘9’ 或 ‘-1’ 的整數，控制了壓縮的級別；‘1’
     (Z_BEST_SPEED) 最快但壓縮程度較小，‘9’ (Z_BEST_COMPRESSION) 最慢但
     壓縮最多。 ‘0’ (Z_NO_COMPRESSION) 代表不壓縮。預設值為 ‘-1’
     (Z_DEFAULT_COMPRESSION)。Z_DEFAULT_COMPRESSION 表示預設的速度和壓縮
     間折衷方案（目前相當於級別 6）。 'wbits' 引數控制了壓縮資料時所使用
     的歷史紀錄緩衝區 (history buffer) 大小（或「視窗大小」），以及輸出
     中是否包含標題和尾末 (trailer)。它可以採用多個值的範圍，預設為 ‘15’
     (MAX_WBITS)：

        * +9 到 +15：視窗大小的以二為底的對數，因此範圍在 512 到 32768 之
          間。較大的值會產生更佳的壓縮，但會佔用更多的記憶體。生成輸出將
          包含特定於 zlib 的標頭和尾末。

        * −9 到 −15：使用 'wbits' 的絕對值作為視窗大小的對數，同時生成沒
          有標頭或尾末核對和的原始輸出串流。

        * +25 到 +31 = 16 +（9 到 15）：使用數值的最低 4 位元作為視窗大
          小的對數，同時在輸出中包含基本的 gzip 標頭和尾末核對和。

     如果發生任何錯誤，則引發 *note error: 2837. 例外。

     在 3.6 版的變更: 'level' 現在可以用作關鍵字參數。

     在 3.11 版的變更: 'wbits' 參數現在可用於設定視窗位元和壓縮型別。

 -- 函式: zlib.compressobj (level=-1, method=DEFLATED, wbits=MAX_WBITS,
          memLevel=DEF_MEM_LEVEL, strategy=Z_DEFAULT_STRATEGY[, zdict])

     回傳一個壓縮物件，用於壓縮不能一次全部放入記憶體中的資料串流。

     'level' 是壓縮級別 - 從 ‘0’ 到 ‘9’ 或 ‘-1’ 的整數。‘1’
     (Z_BEST_SPEED) 最快但壓縮程度較小，而 ‘9’ (Z_BEST_COMPRESSION) 最慢
     但壓縮最多。‘0’ (Z_NO_COMPRESSION) 代表不壓縮。預設值為 ‘-1’
     (Z_DEFAULT_COMPRESSION)。Z_DEFAULT_COMPRESSION 表示預設的速度和壓縮
     間折衷方案（目前相當於級別 6）。

     'method' 代表壓縮演算法。目前唯一支援的值是 ‘DEFLATED’。

     'wbits' 參數控制歷史紀錄緩衝區的大小（或「視窗大小」），以及將使用
     的標頭和尾末格式。它與*note 前面敘述的 compress(): 2838. 具有相同的
     含義。

     'memLevel' 引數控制用於內部壓縮狀態的記憶體大小。有效值範圍為 ‘1’ 到
     ‘9’。較高的值會使用更多的記憶體，但速度更快並產生更小的輸出。

     'strategy' 被用於調整壓縮演算法。可用的值為 ‘Z_DEFAULT_STRATEGY’、
     ‘Z_FILTERED’、‘Z_HUFFMAN_ONLY’、‘Z_RLE’ (zlib 1.2.0.1) 和 ‘Z_FIXED’
     (zlib 1.2.2.2)。

     'zdict' 是事先定義好的的壓縮字典。這是一個位元組序列（例如一個
     *note bytes: 1a5. 物件），其中包含預期在要壓縮的資料中頻繁出現的子
     序列。那些預期會最常見的子序列應該出現在字典的尾末。

     在 3.3 版的變更: 新增 'zdict' 參數與支援關鍵字引數。

 -- 函式: zlib.crc32 (data[, value])

     計算 'data' 的 CRC（Cyclic Redundancy Check，循環冗餘核對）核對和，
     結果會是一個 unsigned 32-bit 整數。如果 'value' 存在，則將其用作核
     對和的起始值，否則使用預設值 0。傳入 'value' 允許在多個輸入的串聯上
     計算核對和。該演算法的加密強度不夠高，不該用於身份驗證或數位簽章。
     由於該演算法是為核對和演算法而設計的，它並不適合作為通用的雜湊演算
     法。

     在 3.0 版的變更: 結果總是為 unsigned。

 -- 函式: zlib.decompress (data, /, wbits=MAX_WBITS,
          bufsize=DEF_BUF_SIZE)

     解壓縮 'data' 中的位元組，回傳包含未壓縮資料的位元組物件。 'wbits'
     參數依賴於 'data' 的格式，下面將進一步討論。如果有給定 'bufsize'，
     它會被用作輸出緩衝區的初始大小。如果發生任何錯誤，則引發 *note
     error: 2837. 例外。 'wbits' 參數控制歷史紀錄緩衝區的大小（或「視窗
     大小」），以及期望的標頭和尾末格式。它類似於 *note compressobj():
     2839. 的參數，但接受更多範圍的值：

        * +8 到 +15：視窗大小的以二為底的對數。輸入必須包括一個 zlib 標
          頭和尾末。

        * 0：根據 zlib 標頭檔自動決定視窗大小。僅有在 zlib 1.2.3.5 或更
          新的版本支援。

        * −8 to −15：使用 'wbits' 的絕對值作為視窗大小的對數，輸入必須是
          沒有標頭或尾末的原始串流。

        * +24 到 +31 = 16 + （8 到 15）：取值的最低4位元作為視窗大小的對
          數，輸入必須包含 gzip 標頭和尾末。

        * +40 到 +47 = 32 + （8 到 15）：使用值的最低 4 位元作為視窗大小
          的對數，並自動接受 zlib 或 gzip 格式。

     當解壓縮一個串流時，視窗大小不得小於最初用於壓縮串流的大小；使用太
     小的值可能會導致 *note error: 2837. 例外。預設的 'wbits' 值對應於最
     大的視窗大小，並且需要包含 zlib 標頭和尾末。

     'bufsize' 是用於保存解壓縮資料的緩衝區的初始大小。如果需要更多空間
     ，緩衝區大小將根據需求來增加，因此你不需要讓該值完全剛好；調整它只
     會節省幾次對 ‘malloc()’ 的呼叫。

     在 3.6 版的變更: 'wbits' 和 'bufsize' 可以用作關鍵字引數。

 -- 函式: zlib.decompressobj (wbits=MAX_WBITS[, zdict])

     回傳一個解壓縮物件，用於解壓縮不能一次全部放入記憶體的資料串流。

     'wbits' 引數控制歷史紀錄緩衝區的大小（或「視窗大小」），以及期望的
     標頭和尾末格式。它與*note 前面敘述的 decompress(): 283a. 具有相同的
     含義。

     'zdict' 參數指定是先定義好的壓縮字典。如果有提供，這必須與生成要解
     壓縮資料的壓縮器所使用的字典相同。

          備註: 如果 'zdict' 是一個可變物件 (mutable object)（例如一個
          *note bytearray: 4e3.），你不能在呼叫 *note decompressobj():
          283b. 和第一次呼叫解壓縮器的 ‘decompress()’ 方法之間修改它的內
          容。

     在 3.3 版的變更: 新增 'zdict' 參數。

壓縮物件支援以下方法：

 -- 方法: Compress.compress (data)

     壓縮 'data'，回傳一個位元組物件，其中至少包含 'data' 中部分資料的壓
     縮資料。此資料應串聯到任何先前呼叫 *note compress(): 5e5. 方法所產
     生的輸出。一些輸入可能會保存在內部緩衝區中以供後續處理。

 -- 方法: Compress.flush ([mode])

     處理所有待處理的輸入，並回傳包含剩餘壓縮輸出的位元組物件。'mode' 可
     以從以下常數中選擇：‘Z_NO_FLUSH’、‘Z_PARTIAL_FLUSH’、
     ‘Z_SYNC_FLUSH’、‘Z_FULL_FLUSH’、‘Z_BLOCK’ (zlib 1.2.3.4) 或
     ‘Z_FINISH’，預設為 ‘Z_FINISH’。除了 ‘Z_FINISH’ 之外，所有常數都允許
     壓縮更多的資料位元組字串，而 ‘Z_FINISH’ 會完成壓縮串流並同時防止壓
     縮更多資料。在 'mode' 設定為 ‘Z_FINISH’ 的情況下呼叫 *note flush():
     283d. 後，無法再次呼叫 *note compress(): 5e5. 方法；唯一可行的作法
     是刪除物件。

 -- 方法: Compress.copy ()

     回傳壓縮物件的副本，這可用於有效壓縮一組共用初始前綴的資料。

在 3.8 版的變更: 於壓縮物件新增對 *note copy.copy(): 4d8. 和 *note
copy.deepcopy(): b12. 的支援。

解壓縮物件支援以下方法和屬性：

 -- 屬性: Decompress.unused_data

     一個位元組物件，它包含壓縮資料結束之後的任何位元組。也就是說，在包
     含壓縮資料的最後一個位元組可用之前，它會一直保持為 ‘b""’。如果整個
     位元組字串 (bytestring) 有包含壓縮資料，這會是 ‘b""’，也就是一個空
     位元組物件。

 -- 屬性: Decompress.unconsumed_tail

     一個位元組物件，包含前一次 *note decompress(): cb4. 的呼叫因超出了
     未壓縮資料緩衝區的限制而沒消耗掉的任何資料。 zlib 機制尚未看到此資
     料，因此你必須將其（和可能有和它串聯的其他資料）反饋給後續的 *note
     decompress(): cb4. 方法呼叫以獲得正確的輸出。

 -- 屬性: Decompress.eof

     一個布林值，代表是否已到達壓縮資料串流的尾末。

     這使其能夠區分有正確建構的壓縮串流和不完整或被截斷的串流。

     在 3.3 版被加入.

 -- 方法: Decompress.decompress (data, max_length=0)

     解壓縮 'data' 並回傳一個位元組物件，其包含與 'string' 中至少與部分
     資料相對應的未壓縮資料。此資料應串聯到任何先前呼叫 *note
     decompress(): cb4. 方法所產生的輸出。一些輸入資料可能會保存在內部緩
     衝區中以供後續處理。

     如果可選參數 'max_length' 不是零，則回傳值長度將不超過
     'max_length'。這代表著並不是所有的已壓縮輸入都可以被處理；未使用的
     資料將被存儲在屬性 *note unconsumed_tail: 2840. 中。如果要繼續解壓
     縮，則必須將此位元組字串傳遞給後續對 *note decompress(): cb4. 的呼
     叫。如果 'max_length' 為零，則整個輸入會被解壓縮，並且 *note
     unconsumed_tail: 2840. 為空。

     在 3.6 版的變更: 'max_length' 可以用作關鍵字引數。

 -- 方法: Decompress.flush ([length])

     處理所有待處理的輸入，並回傳包含剩餘未壓縮輸出的位元組物件。呼叫
     *note flush(): 2842. 後，無法再次呼叫 *note decompress(): cb4. 方法
     ；唯一可行的方法是刪除該物件。

     可選參數 'length' 設定了輸出緩衝區的初始大小。

 -- 方法: Decompress.copy ()

     回傳解壓物件的副本，這可用於在資料串流中途保存解壓縮器的狀態，以便
     在未來某個時間點加速對串流的隨機搜索 (random seek)。

在 3.8 版的變更: 於解壓縮物件新增對 *note copy.copy(): 4d8. 和 *note
copy.deepcopy(): b12. 支援。

有關正在使用的 zlib 函式庫版本資訊可通過以下常數獲得：

 -- 資料: zlib.ZLIB_VERSION

     用於建置模組的 zlib 函式庫版本字串。這可能與實際在執行環境
     (runtime) 使用的 zlib 函式庫不同，後者以 *note
     ZLIB_RUNTIME_VERSION: 1107. 提供。

 -- 資料: zlib.ZLIB_RUNTIME_VERSION

     直譯器實際載入的 zlib 函式庫版本字串。

     在 3.3 版被加入.

也參考
......

*note gzip: 5d. 模組

     讀寫 ‘gzip’ 格式的檔案。

‘http://www.zlib.net’

     zlib 函式庫首頁。

‘http://www.zlib.net/manual.html’

     zlib 手冊解釋了函式庫中許多函式的語義和用法。

   ---------- Footnotes ----------

   (1) https://zlib.net/zlib_faq.html#faq33


File: python.info,  Node: gzip --- gzip 檔案的支援,  Next: bz2 --- bzip2 壓縮的支援,  Prev: zlib --- 相容於 gzip 的壓縮,  Up: 資料壓縮與保存

5.13.2 ‘gzip’ -- ‘gzip’ 檔案的支援
----------------------------------

'原始碼：'Lib/gzip.py(1)

__________________________________________________________________

This module provides a simple interface to compress and decompress files
just like the GNU programs ‘gzip’ and ‘gunzip’ would.

The data compression is provided by the *note zlib: 119. module.

The *note gzip: 5d. module provides the *note GzipFile: 354. class, as
well as the *note open(): 2847, *note compress(): 5e4. and *note
decompress(): 11a5. convenience functions.  The *note GzipFile: 354.
class reads and writes ‘gzip’-format files, automatically compressing or
decompressing the data so that it looks like an ordinary *note file
object: 115b.

Note that additional file formats which can be decompressed by the
‘gzip’ and ‘gunzip’ programs, such as those produced by ‘compress’ and
‘pack’, are not supported by this module.

此模組定義了以下項目：

 -- 函式: gzip.open (filename, mode='rb', compresslevel=9,
          encoding=None, errors=None, newline=None)

     Open a gzip-compressed file in binary or text mode, returning a
     *note file object: 115b.

     The 'filename' argument can be an actual filename (a *note str:
     3f2. or *note bytes: 1a5. object), or an existing file object to
     read from or write to.

     The 'mode' argument can be any of ‘'r'’, ‘'rb'’, ‘'a'’, ‘'ab'’,
     ‘'w'’, ‘'wb'’, ‘'x'’ or ‘'xb'’ for binary mode, or ‘'rt'’, ‘'at'’,
     ‘'wt'’, or ‘'xt'’ for text mode.  The default is ‘'rb'’.

     The 'compresslevel' argument is an integer from 0 to 9, as for the
     *note GzipFile: 354. constructor.

     For binary mode, this function is equivalent to the *note GzipFile:
     354. constructor: ‘GzipFile(filename, mode, compresslevel)’.  In
     this case, the 'encoding', 'errors' and 'newline' arguments must
     not be provided.

     For text mode, a *note GzipFile: 354. object is created, and
     wrapped in an *note io.TextIOWrapper: 75f. instance with the
     specified encoding, error handling behavior, and line ending(s).

     在 3.3 版的變更: Added support for 'filename' being a file object,
     support for text mode, and the 'encoding', 'errors' and 'newline'
     arguments.

     在 3.4 版的變更: 新增 ‘'x'’、‘'xb'’ 和 ‘'xt'’ 模式的支援。

     在 3.6 版的變更: 接受*note 類路徑物件: ac2.。

 -- 例外: gzip.BadGzipFile

     An exception raised for invalid gzip files.  It inherits from *note
     OSError: 350.  *note EOFError: 126c. and *note zlib.error: 2837.
     can also be raised for invalid gzip files.

     在 3.8 版被加入.

 -- 類別: gzip.GzipFile (filename=None, mode=None, compresslevel=9,
          fileobj=None, mtime=None)

     Constructor for the *note GzipFile: 354. class, which simulates
     most of the methods of a *note file object: 115b, with the
     exception of the *note truncate(): 12a5. method.  At least one of
     'fileobj' and 'filename' must be given a non-trivial value.

     The new class instance is based on 'fileobj', which can be a
     regular file, an *note io.BytesIO: e46. object, or any other object
     which simulates a file.  It defaults to ‘None’, in which case
     'filename' is opened to provide a file object.

     When 'fileobj' is not ‘None’, the 'filename' argument is only used
     to be included in the ‘gzip’ file header, which may include the
     original filename of the uncompressed file.  It defaults to the
     filename of 'fileobj', if discernible; otherwise, it defaults to
     the empty string, and in this case the original filename is not
     included in the header.

     The 'mode' argument can be any of ‘'r'’, ‘'rb'’, ‘'a'’, ‘'ab'’,
     ‘'w'’, ‘'wb'’, ‘'x'’, or ‘'xb'’, depending on whether the file will
     be read or written.  The default is the mode of 'fileobj' if
     discernible; otherwise, the default is ‘'rb'’.  In future Python
     releases the mode of 'fileobj' will not be used.  It is better to
     always specify 'mode' for writing.

     Note that the file is always opened in binary mode.  To open a
     compressed file in text mode, use *note open(): 2847. (or wrap your
     *note GzipFile: 354. with an *note io.TextIOWrapper: 75f.).

     The 'compresslevel' argument is an integer from ‘0’ to ‘9’
     controlling the level of compression; ‘1’ is fastest and produces
     the least compression, and ‘9’ is slowest and produces the most
     compression.  ‘0’ is no compression.  The default is ‘9’.

     The optional 'mtime' argument is the timestamp requested by gzip.
     The time is in Unix format, i.e., seconds since 00:00:00 UTC,
     January 1, 1970.  If 'mtime' is omitted or ‘None’, the current time
     is used.  Use 'mtime' = 0 to generate a compressed stream that does
     not depend on creation time.

     See below for the *note mtime: 2848. attribute that is set when
     decompressing.

     Calling a *note GzipFile: 354. object's ‘close()’ method does not
     close 'fileobj', since you might wish to append more material after
     the compressed data.  This also allows you to pass an *note
     io.BytesIO: e46. object opened for writing as 'fileobj', and
     retrieve the resulting memory buffer using the *note io.BytesIO:
     e46. object's *note getvalue(): 2849. method.

     *note GzipFile: 354. supports the *note io.BufferedIOBase: 63a.
     interface, including iteration and the *note with: 577. statement.
     Only the *note truncate(): 12a5. method isn't implemented.

     *note GzipFile: 354. 也提供了以下的方法和屬性：

      -- 方法: peek (n)

          Read 'n' uncompressed bytes without advancing the file
          position.  At most one single read on the compressed stream is
          done to satisfy the call.  The number of bytes returned may be
          more or less than requested.

               備註: While calling *note peek(): 11a4. does not change
               the file position of the *note GzipFile: 354, it may
               change the position of the underlying file object (e.g.
               if the *note GzipFile: 354. was constructed with the
               'fileobj' parameter).

          在 3.2 版被加入.

      -- 屬性: mode

          ‘'rb'’ for reading and ‘'wb'’ for writing.

          在 3.13 版的變更: In previous versions it was an integer ‘1’
          or ‘2’.

      -- 屬性: mtime

          When decompressing, this attribute is set to the last
          timestamp in the most recently read header.  It is an integer,
          holding the number of seconds since the Unix epoch (00:00:00
          UTC, January 1, 1970).  The initial value before reading any
          headers is ‘None’.

      -- 屬性: name

          The path to the gzip file on disk, as a *note str: 3f2. or
          *note bytes: 1a5.  Equivalent to the output of *note
          os.fspath(): bfa. on the original input path, with no other
          normalization, resolution or expansion.

     在 3.1 版的變更: Support for the *note with: 577. statement was
     added, along with the 'mtime' constructor argument and *note mtime:
     2848. attribute.

     在 3.2 版的變更: Support for zero-padded and unseekable files was
     added.

     在 3.3 版的變更: *note io.BufferedIOBase.read1(): 284b. 方法現在已
     有實作。

     在 3.4 版的變更: 新增 ‘'x'’ 和 ‘'xb'’ 模式的支援。

     在 3.5 版的變更: Added support for writing arbitrary *note
     bytes-like objects: cd4.  The *note read(): 12bc. method now
     accepts an argument of ‘None’.

     在 3.6 版的變更: 接受*note 類路徑物件: ac2.。

     在 3.9 版之後被棄用: Opening *note GzipFile: 354. for writing
     without specifying the 'mode' argument is deprecated.

     在 3.12 版的變更: Remove the ‘filename’ attribute, use the *note
     name: 4b2. attribute instead.

 -- 函式: gzip.compress (data, compresslevel=9, *, mtime=None)

     Compress the 'data', returning a *note bytes: 1a5. object
     containing the compressed data.  'compresslevel' and 'mtime' have
     the same meaning as in the *note GzipFile: 354. constructor above.

     在 3.2 版被加入.

     在 3.8 版的變更: Added the 'mtime' parameter for reproducible
     output.

     在 3.11 版的變更: Speed is improved by compressing all data at once
     instead of in a streamed fashion.  Calls with 'mtime' set to ‘0’
     are delegated to *note zlib.compress(): 5e5. for better speed.  In
     this situation the output may contain a gzip header "OS" byte value
     other than 255 "unknown" as supplied by the underlying zlib
     implementation.

     在 3.13 版的變更: The gzip header OS byte is guaranteed to be set
     to 255 when this function is used as was the case in 3.10 and
     earlier.

 -- 函式: gzip.decompress (data)

     Decompress the 'data', returning a *note bytes: 1a5. object
     containing the uncompressed data.  This function is capable of
     decompressing multi-member gzip data (multiple gzip blocks
     concatenated together).  When the data is certain to contain only
     one member the *note zlib.decompress(): cb4. function with 'wbits'
     set to 31 is faster.

     在 3.2 版被加入.

     在 3.11 版的變更: Speed is improved by decompressing members at
     once in memory instead of in a streamed fashion.

* Menu:

* 用法範例::
* 命令列介面: 命令列介面<2>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/gzip.py


File: python.info,  Node: 用法範例,  Next: 命令列介面<2>,  Up: gzip --- gzip 檔案的支援

5.13.2.1 用法範例
.................

如何讀取壓縮檔案的範例：

     import gzip
     with gzip.open('/home/joe/file.txt.gz', 'rb') as f:
         file_content = f.read()

如何建立一個壓縮的 GZIP 檔案的範例：

     import gzip
     content = b"Lots of content here"
     with gzip.open('/home/joe/file.txt.gz', 'wb') as f:
         f.write(content)

如何壓縮一個已存在的檔案的範例：

     import gzip
     import shutil
     with open('/home/joe/file.txt', 'rb') as f_in:
         with gzip.open('/home/joe/file.txt.gz', 'wb') as f_out:
             shutil.copyfileobj(f_in, f_out)

如何壓縮一個二進位字串的範例：

     import gzip
     s_in = b"Lots of content here"
     s_out = gzip.compress(s_in)

也參考
......

*note zlib: 119. 模組

     The basic data compression module needed to support the ‘gzip’ file
     format.


File: python.info,  Node: 命令列介面<2>,  Prev: 用法範例,  Up: gzip --- gzip 檔案的支援

5.13.2.2 命令列介面
...................

The *note gzip: 5d. module provides a simple command line interface to
compress or decompress files.

Once executed the *note gzip: 5d. module keeps the input file(s).

在 3.8 版的變更: Add a new command line interface with a usage.  By
default, when you will execute the CLI, the default compression level is
6.

* Menu:

* 命令列選項::


File: python.info,  Node: 命令列選項,  Up: 命令列介面<2>

5.13.2.3 命令列選項
...................

 -- Option: file

     如果未指定 'file'，則從 *note sys.stdin: 4e2. 讀取。

 -- Option: --fast

     Indicates the fastest compression method (less compression).

 -- Option: --best

     Indicates the slowest compression method (best compression).

 -- Option: -d, --decompress

     解壓縮指定的檔案。

 -- Option: -h, --help

     顯示幫助訊息。


File: python.info,  Node: bz2 --- bzip2 壓縮的支援,  Next: lzma --- 使用 LZMA 演算法進行壓縮,  Prev: gzip --- gzip 檔案的支援,  Up: 資料壓縮與保存

5.13.3 ‘bz2’ -- ‘bzip2’ 壓縮的支援
----------------------------------

'原始碼：'Lib/bz2.py(1)

__________________________________________________________________

This module provides a comprehensive interface for compressing and
decompressing data using the bzip2 compression algorithm.

The *note bz2: f. module contains:

   * The *note open(): 102f. function and *note BZ2File: 80b. class for
     reading and writing compressed files.

   * The *note BZ2Compressor: 165f. and *note BZ2Decompressor: 165d.
     classes for incremental (de)compression.

   * The *note compress(): 22ef. and *note decompress(): 1030. functions
     for one-shot (de)compression.

* Menu:

* (De)compression of files: De compression of files.
* Incremental (de)compression: Incremental de compression.
* One-shot (de)compression: One-shot de compression.
* 用法範例: 用法範例<2>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/bz2.py


File: python.info,  Node: De compression of files,  Next: Incremental de compression,  Up: bz2 --- bzip2 壓縮的支援

5.13.3.1 (De)compression of files
.................................

 -- 函式: bz2.open (filename, mode='rb', compresslevel=9, encoding=None,
          errors=None, newline=None)

     Open a bzip2-compressed file in binary or text mode, returning a
     *note file object: 115b.

     As with the constructor for *note BZ2File: 80b, the 'filename'
     argument can be an actual filename (a *note str: 3f2. or *note
     bytes: 1a5. object), or an existing file object to read from or
     write to.

     The 'mode' argument can be any of ‘'r'’, ‘'rb'’, ‘'w'’, ‘'wb'’,
     ‘'x'’, ‘'xb'’, ‘'a'’ or ‘'ab'’ for binary mode, or ‘'rt'’, ‘'wt'’,
     ‘'xt'’, or ‘'at'’ for text mode.  The default is ‘'rb'’.

     The 'compresslevel' argument is an integer from 1 to 9, as for the
     *note BZ2File: 80b. constructor.

     For binary mode, this function is equivalent to the *note BZ2File:
     80b. constructor: ‘BZ2File(filename, mode,
     compresslevel=compresslevel)’.  In this case, the 'encoding',
     'errors' and 'newline' arguments must not be provided.

     For text mode, a *note BZ2File: 80b. object is created, and wrapped
     in an *note io.TextIOWrapper: 75f. instance with the specified
     encoding, error handling behavior, and line ending(s).

     在 3.3 版被加入.

     在 3.4 版的變更: The ‘'x'’ (exclusive creation) mode was added.

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 類別: bz2.BZ2File (filename, mode='r', *, compresslevel=9)

     Open a bzip2-compressed file in binary mode.

     If 'filename' is a *note str: 3f2. or *note bytes: 1a5. object,
     open the named file directly.  Otherwise, 'filename' should be a
     *note file object: 115b, which will be used to read or write the
     compressed data.

     The 'mode' argument can be either ‘'r'’ for reading (default),
     ‘'w'’ for overwriting, ‘'x'’ for exclusive creation, or ‘'a'’ for
     appending.  These can equivalently be given as ‘'rb'’, ‘'wb'’,
     ‘'xb'’ and ‘'ab'’ respectively.

     If 'filename' is a file object (rather than an actual file name), a
     mode of ‘'w'’ does not truncate the file, and is instead equivalent
     to ‘'a'’.

     If 'mode' is ‘'w'’ or ‘'a'’, 'compresslevel' can be an integer
     between ‘1’ and ‘9’ specifying the level of compression: ‘1’
     produces the least compression, and ‘9’ (default) produces the most
     compression.

     If 'mode' is ‘'r'’, the input file may be the concatenation of
     multiple compressed streams.

     *note BZ2File: 80b. provides all of the members specified by the
     *note io.BufferedIOBase: 63a, except for *note detach(): 285b. and
     *note truncate(): 12a5.  Iteration and the *note with: 577.
     statement are supported.

     *note BZ2File: 80b. also provides the following methods and
     attributes:

      -- 方法: peek ([n])

          Return buffered data without advancing the file position.  At
          least one byte of data will be returned (unless at EOF). The
          exact number of bytes returned is unspecified.

               備註: While calling *note peek(): 285c. does not change
               the file position of the *note BZ2File: 80b, it may
               change the position of the underlying file object (e.g.
               if the *note BZ2File: 80b. was constructed by passing a
               file object for 'filename').

          在 3.3 版被加入.

      -- 方法: fileno ()

          Return the file descriptor for the underlying file.

          在 3.3 版被加入.

      -- 方法: readable ()

          Return whether the file was opened for reading.

          在 3.3 版被加入.

      -- 方法: seekable ()

          Return whether the file supports seeking.

          在 3.3 版被加入.

      -- 方法: writable ()

          Return whether the file was opened for writing.

          在 3.3 版被加入.

      -- 方法: read1 (size=-1)

          Read up to 'size' uncompressed bytes, while trying to avoid
          making multiple reads from the underlying stream.  Reads up to
          a buffer's worth of data if size is negative.

          Returns ‘b''’ if the file is at EOF.

          在 3.3 版被加入.

      -- 方法: readinto (b)

          Read bytes into 'b'.

          Returns the number of bytes read (0 for EOF).

          在 3.3 版被加入.

      -- 屬性: mode

          ‘'rb'’ for reading and ‘'wb'’ for writing.

          在 3.13 版被加入.

      -- 屬性: name

          The bzip2 file name.  Equivalent to the *note name: 2865.
          attribute of the underlying *note file object: 115b.

          在 3.13 版被加入.

     在 3.1 版的變更: Support for the *note with: 577. statement was
     added.

     在 3.3 版的變更: Support was added for 'filename' being a *note
     file object: 115b. instead of an actual filename.

     The ‘'a'’ (append) mode was added, along with support for reading
     multi-stream files.

     在 3.4 版的變更: The ‘'x'’ (exclusive creation) mode was added.

     在 3.5 版的變更: The *note read(): 12bc. method now accepts an
     argument of ‘None’.

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

     在 3.9 版的變更: The 'buffering' parameter has been removed.  It
     was ignored and deprecated since Python 3.0.  Pass an open file
     object to control how the file is opened.

     The 'compresslevel' parameter became keyword-only.

     在 3.10 版的變更: This class is thread unsafe in the face of
     multiple simultaneous readers or writers, just like its equivalent
     classes in *note gzip: 5d. and *note lzma: 7e. have always been.


File: python.info,  Node: Incremental de compression,  Next: One-shot de compression,  Prev: De compression of files,  Up: bz2 --- bzip2 壓縮的支援

5.13.3.2 Incremental (de)compression
....................................

 -- 類別: bz2.BZ2Compressor (compresslevel=9)

     Create a new compressor object.  This object may be used to
     compress data incrementally.  For one-shot compression, use the
     *note compress(): 22ef. function instead.

     'compresslevel', if given, must be an integer between ‘1’ and ‘9’.
     The default is ‘9’.

      -- 方法: compress (data)

          Provide data to the compressor object.  Returns a chunk of
          compressed data if possible, or an empty byte string
          otherwise.

          When you have finished providing data to the compressor, call
          the *note flush(): 2868. method to finish the compression
          process.

      -- 方法: flush ()

          Finish the compression process.  Returns the compressed data
          left in internal buffers.

          The compressor object may not be used after this method has
          been called.

 -- 類別: bz2.BZ2Decompressor

     Create a new decompressor object.  This object may be used to
     decompress data incrementally.  For one-shot compression, use the
     *note decompress(): 1030. function instead.

          備註: This class does not transparently handle inputs
          containing multiple compressed streams, unlike *note
          decompress(): 1030. and *note BZ2File: 80b.  If you need to
          decompress a multi-stream input with *note BZ2Decompressor:
          165d, you must use a new decompressor for each stream.

      -- 方法: decompress (data, max_length=-1)

          Decompress 'data' (a *note bytes-like object: cd4.), returning
          uncompressed data as bytes.  Some of 'data' may be buffered
          internally, for use in later calls to *note decompress():
          1030.  The returned data should be concatenated with the
          output of any previous calls to *note decompress(): 1030.

          If 'max_length' is nonnegative, returns at most 'max_length'
          bytes of decompressed data.  If this limit is reached and
          further output can be produced, the *note needs_input: 2869.
          attribute will be set to ‘False’.  In this case, the next call
          to *note decompress(): d72. may provide 'data' as ‘b''’ to
          obtain more of the output.

          If all of the input data was decompressed and returned (either
          because this was less than 'max_length' bytes, or because
          'max_length' was negative), the *note needs_input: 2869.
          attribute will be set to ‘True’.

          Attempting to decompress data after the end of stream is
          reached raises an *note EOFError: 126c.  Any data found after
          the end of the stream is ignored and saved in the *note
          unused_data: 286a. attribute.

          在 3.5 版的變更: 新增 'max_length' 參數。

      -- 屬性: eof

          ‘True’ if the end-of-stream marker has been reached.

          在 3.3 版被加入.

      -- 屬性: unused_data

          Data found after the end of the compressed stream.

          If this attribute is accessed before the end of the stream has
          been reached, its value will be ‘b''’.

      -- 屬性: needs_input

          ‘False’ if the *note decompress(): d72. method can provide
          more decompressed data before requiring new uncompressed
          input.

          在 3.5 版被加入.


File: python.info,  Node: One-shot de compression,  Next: 用法範例<2>,  Prev: Incremental de compression,  Up: bz2 --- bzip2 壓縮的支援

5.13.3.3 One-shot (de)compression
.................................

 -- 函式: bz2.compress (data, compresslevel=9)

     Compress 'data', a *note bytes-like object: cd4.

     'compresslevel', if given, must be an integer between ‘1’ and ‘9’.
     The default is ‘9’.

     For incremental compression, use a *note BZ2Compressor: 165f.
     instead.

 -- 函式: bz2.decompress (data)

     Decompress 'data', a *note bytes-like object: cd4.

     If 'data' is the concatenation of multiple compressed streams,
     decompress all of the streams.

     For incremental decompression, use a *note BZ2Decompressor: 165d.
     instead.

     在 3.3 版的變更: Support for multi-stream inputs was added.


File: python.info,  Node: 用法範例<2>,  Prev: One-shot de compression,  Up: bz2 --- bzip2 壓縮的支援

5.13.3.4 用法範例
.................

Below are some examples of typical usage of the *note bz2: f. module.

Using *note compress(): 22ef. and *note decompress(): 1030. to
demonstrate round-trip compression:

     >>> import bz2
     >>> data = b"""\
     ... Donec rhoncus quis sapien sit amet molestie. Fusce scelerisque vel augue
     ... nec ullamcorper. Nam rutrum pretium placerat. Aliquam vel tristique lorem,
     ... sit amet cursus ante. In interdum laoreet mi, sit amet ultrices purus
     ... pulvinar a. Nam gravida euismod magna, non varius justo tincidunt feugiat.
     ... Aliquam pharetra lacus non risus vehicula rutrum. Maecenas aliquam leo
     ... felis. Pellentesque semper nunc sit amet nibh ullamcorper, ac elementum
     ... dolor luctus. Curabitur lacinia mi ornare consectetur vestibulum."""
     >>> c = bz2.compress(data)
     >>> len(data) / len(c)  # Data compression ratio
     1.513595166163142
     >>> d = bz2.decompress(c)
     >>> data == d  # Check equality to original object after round-trip
     True

Using *note BZ2Compressor: 165f. for incremental compression:

     >>> import bz2
     >>> def gen_data(chunks=10, chunksize=1000):
     ...     """Yield incremental blocks of chunksize bytes."""
     ...     for _ in range(chunks):
     ...         yield b"z" * chunksize
     ...
     >>> comp = bz2.BZ2Compressor()
     >>> out = b""
     >>> for chunk in gen_data():
     ...     # Provide data to the compressor object
     ...     out = out + comp.compress(chunk)
     ...
     >>> # Finish the compression process.  Call this once you have
     >>> # finished providing data to the compressor.
     >>> out = out + comp.flush()

The example above uses a very "nonrandom" stream of data (a stream of
‘b"z"’ chunks).  Random data tends to compress poorly, while ordered,
repetitive data usually yields a high compression ratio.

Writing and reading a bzip2-compressed file in binary mode:

     >>> import bz2
     >>> data = b"""\
     ... Donec rhoncus quis sapien sit amet molestie. Fusce scelerisque vel augue
     ... nec ullamcorper. Nam rutrum pretium placerat. Aliquam vel tristique lorem,
     ... sit amet cursus ante. In interdum laoreet mi, sit amet ultrices purus
     ... pulvinar a. Nam gravida euismod magna, non varius justo tincidunt feugiat.
     ... Aliquam pharetra lacus non risus vehicula rutrum. Maecenas aliquam leo
     ... felis. Pellentesque semper nunc sit amet nibh ullamcorper, ac elementum
     ... dolor luctus. Curabitur lacinia mi ornare consectetur vestibulum."""
     >>> with bz2.open("myfile.bz2", "wb") as f:
     ...     # Write compressed data to file
     ...     unused = f.write(data)
     ...
     >>> with bz2.open("myfile.bz2", "rb") as f:
     ...     # Decompress data from file
     ...     content = f.read()
     ...
     >>> content == data  # Check equality to original object after round-trip
     True


File: python.info,  Node: lzma --- 使用 LZMA 演算法進行壓縮,  Next: zipfile --- 處理 ZIP 封存檔案,  Prev: bz2 --- bzip2 壓縮的支援,  Up: 資料壓縮與保存

5.13.4 ‘lzma’ -- 使用 LZMA 演算法進行壓縮
-----------------------------------------

在 3.3 版被加入.

'原始碼：'Lib/lzma.py(1)

__________________________________________________________________

This module provides classes and convenience functions for compressing
and decompressing data using the LZMA compression algorithm.  Also
included is a file interface supporting the ‘.xz’ and legacy ‘.lzma’
file formats used by the ‘xz’ utility, as well as raw compressed
streams.

The interface provided by this module is very similar to that of the
*note bz2: f. module.  Note that *note LZMAFile: fad. and *note
bz2.BZ2File: 80b. are 'not' thread-safe, so if you need to use a single
*note LZMAFile: fad. instance from multiple threads, it is necessary to
protect it with a lock.

 -- 例外: lzma.LZMAError

     This exception is raised when an error occurs during compression or
     decompression, or while initializing the compressor/decompressor
     state.

* Menu:

* Reading and writing compressed files::
* Compressing and decompressing data in memory::
* Miscellaneous::
* Specifying custom filter chains::
* 範例: 範例<12>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/lzma.py


File: python.info,  Node: Reading and writing compressed files,  Next: Compressing and decompressing data in memory,  Up: lzma --- 使用 LZMA 演算法進行壓縮

5.13.4.1 Reading and writing compressed files
.............................................

 -- 函式: lzma.open (filename, mode='rb', *, format=None, check=-1,
          preset=None, filters=None, encoding=None, errors=None,
          newline=None)

     Open an LZMA-compressed file in binary or text mode, returning a
     *note file object: 115b.

     The 'filename' argument can be either an actual file name (given as
     a *note str: 3f2, *note bytes: 1a5. or *note path-like: ac2.
     object), in which case the named file is opened, or it can be an
     existing file object to read from or write to.

     The 'mode' argument can be any of ‘"r"’, ‘"rb"’, ‘"w"’, ‘"wb"’,
     ‘"x"’, ‘"xb"’, ‘"a"’ or ‘"ab"’ for binary mode, or ‘"rt"’, ‘"wt"’,
     ‘"xt"’, or ‘"at"’ for text mode.  The default is ‘"rb"’.

     When opening a file for reading, the 'format' and 'filters'
     arguments have the same meanings as for *note LZMADecompressor:
     165c.  In this case, the 'check' and 'preset' arguments should not
     be used.

     When opening a file for writing, the 'format', 'check', 'preset'
     and 'filters' arguments have the same meanings as for *note
     LZMACompressor: 165e.

     For binary mode, this function is equivalent to the *note LZMAFile:
     fad. constructor: ‘LZMAFile(filename, mode, ...)’.  In this case,
     the 'encoding', 'errors' and 'newline' arguments must not be
     provided.

     For text mode, a *note LZMAFile: fad. object is created, and
     wrapped in an *note io.TextIOWrapper: 75f. instance with the
     specified encoding, error handling behavior, and line ending(s).

     在 3.4 版的變更: 新增 ‘"x"’、‘"xb"’ 和 ‘"xt"’ 模式的支援。

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 類別: lzma.LZMAFile (filename=None, mode='r', *, format=None,
          check=-1, preset=None, filters=None)

     Open an LZMA-compressed file in binary mode.

     An *note LZMAFile: fad. can wrap an already-open *note file object:
     115b, or operate directly on a named file.  The 'filename' argument
     specifies either the file object to wrap, or the name of the file
     to open (as a *note str: 3f2, *note bytes: 1a5. or *note path-like:
     ac2. object).  When wrapping an existing file object, the wrapped
     file will not be closed when the *note LZMAFile: fad. is closed.

     The 'mode' argument can be either ‘"r"’ for reading (default),
     ‘"w"’ for overwriting, ‘"x"’ for exclusive creation, or ‘"a"’ for
     appending.  These can equivalently be given as ‘"rb"’, ‘"wb"’,
     ‘"xb"’ and ‘"ab"’ respectively.

     If 'filename' is a file object (rather than an actual file name), a
     mode of ‘"w"’ does not truncate the file, and is instead equivalent
     to ‘"a"’.

     When opening a file for reading, the input file may be the
     concatenation of multiple separate compressed streams.  These are
     transparently decoded as a single logical stream.

     When opening a file for reading, the 'format' and 'filters'
     arguments have the same meanings as for *note LZMADecompressor:
     165c.  In this case, the 'check' and 'preset' arguments should not
     be used.

     When opening a file for writing, the 'format', 'check', 'preset'
     and 'filters' arguments have the same meanings as for *note
     LZMACompressor: 165e.

     *note LZMAFile: fad. supports all the members specified by *note
     io.BufferedIOBase: 63a, except for *note detach(): 285b. and *note
     truncate(): 12a5.  Iteration and the *note with: 577. statement are
     supported.

     The following method and attributes are also provided:

      -- 方法: peek (size=-1)

          Return buffered data without advancing the file position.  At
          least one byte of data will be returned, unless EOF has been
          reached.  The exact number of bytes returned is unspecified
          (the 'size' argument is ignored).

               備註: While calling *note peek(): 2874. does not change
               the file position of the *note LZMAFile: fad, it may
               change the position of the underlying file object (e.g.
               if the *note LZMAFile: fad. was constructed by passing a
               file object for 'filename').

      -- 屬性: mode

          ‘'rb'’ for reading and ‘'wb'’ for writing.

          在 3.13 版被加入.

      -- 屬性: name

          The lzma file name.  Equivalent to the *note name: 2865.
          attribute of the underlying *note file object: 115b.

          在 3.13 版被加入.

     在 3.4 版的變更: 新增 ‘"x"’ 和 ‘"xb"’ 模式的支援。

     在 3.5 版的變更: The *note read(): 12bc. method now accepts an
     argument of ‘None’.

     在 3.6 版的變更: Accepts a *note path-like object: ac2.


File: python.info,  Node: Compressing and decompressing data in memory,  Next: Miscellaneous,  Prev: Reading and writing compressed files,  Up: lzma --- 使用 LZMA 演算法進行壓縮

5.13.4.2 Compressing and decompressing data in memory
.....................................................

 -- 類別: lzma.LZMACompressor (format=FORMAT_XZ, check=-1, preset=None,
          filters=None)

     Create a compressor object, which can be used to compress data
     incrementally.

     For a more convenient way of compressing a single chunk of data,
     see *note compress(): 2878.

     The 'format' argument specifies what container format should be
     used.  Possible values are:

        * 
          ‘FORMAT_XZ’: The ‘.xz’ container format.

               This is the default format.

        * 
          ‘FORMAT_ALONE’: The legacy ‘.lzma’ container format.

               This format is more limited than ‘.xz’ - it does not
               support integrity checks or multiple filters.

        * 
          ‘FORMAT_RAW’: A raw data stream, not using any container format.

               This format specifier does not support integrity checks,
               and requires that you always specify a custom filter
               chain (for both compression and decompression).
               Additionally, data compressed in this manner cannot be
               decompressed using ‘FORMAT_AUTO’ (see *note
               LZMADecompressor: 165c.).

     The 'check' argument specifies the type of integrity check to
     include in the compressed data.  This check is used when
     decompressing, to ensure that the data has not been corrupted.
     Possible values are:

        * ‘CHECK_NONE’: No integrity check.  This is the default (and
          the only acceptable value) for ‘FORMAT_ALONE’ and
          ‘FORMAT_RAW’.

        * ‘CHECK_CRC32’: 32-bit Cyclic Redundancy Check.

        * ‘CHECK_CRC64’: 64-bit Cyclic Redundancy Check.  This is the
          default for ‘FORMAT_XZ’.

        * ‘CHECK_SHA256’: 256-bit Secure Hash Algorithm.

     If the specified check is not supported, an *note LZMAError: 2871.
     is raised.

     The compression settings can be specified either as a preset
     compression level (with the 'preset' argument), or in detail as a
     custom filter chain (with the 'filters' argument).

     The 'preset' argument (if provided) should be an integer between
     ‘0’ and ‘9’ (inclusive), optionally OR-ed with the constant
     ‘PRESET_EXTREME’.  If neither 'preset' nor 'filters' are given, the
     default behavior is to use ‘PRESET_DEFAULT’ (preset level ‘6’).
     Higher presets produce smaller output, but make the compression
     process slower.

          備註: In addition to being more CPU-intensive, compression
          with higher presets also requires much more memory (and
          produces output that needs more memory to decompress).  With
          preset ‘9’ for example, the overhead for an *note
          LZMACompressor: 165e. object can be as high as 800 MiB. For
          this reason, it is generally best to stick with the default
          preset.

     The 'filters' argument (if provided) should be a filter chain
     specifier.  See *note Specifying custom filter chains: 2879. for
     details.

      -- 方法: compress (data)

          Compress 'data' (a *note bytes: 1a5. object), returning a
          *note bytes: 1a5. object containing compressed data for at
          least part of the input.  Some of 'data' may be buffered
          internally, for use in later calls to *note compress(): 2878.
          and *note flush(): 287b.  The returned data should be
          concatenated with the output of any previous calls to *note
          compress(): 2878.

      -- 方法: flush ()

          Finish the compression process, returning a *note bytes: 1a5.
          object containing any data stored in the compressor's internal
          buffers.

          The compressor cannot be used after this method has been
          called.

 -- 類別: lzma.LZMADecompressor (format=FORMAT_AUTO, memlimit=None,
          filters=None)

     Create a decompressor object, which can be used to decompress data
     incrementally.

     For a more convenient way of decompressing an entire compressed
     stream at once, see *note decompress(): 287c.

     The 'format' argument specifies the container format that should be
     used.  The default is ‘FORMAT_AUTO’, which can decompress both
     ‘.xz’ and ‘.lzma’ files.  Other possible values are ‘FORMAT_XZ’,
     ‘FORMAT_ALONE’, and ‘FORMAT_RAW’.

     The 'memlimit' argument specifies a limit (in bytes) on the amount
     of memory that the decompressor can use.  When this argument is
     used, decompression will fail with an *note LZMAError: 2871. if it
     is not possible to decompress the input within the given memory
     limit.

     The 'filters' argument specifies the filter chain that was used to
     create the stream being decompressed.  This argument is required if
     'format' is ‘FORMAT_RAW’, but should not be used for other formats.
     See *note Specifying custom filter chains: 2879. for more
     information about filter chains.

          備註: This class does not transparently handle inputs
          containing multiple compressed streams, unlike *note
          decompress(): 287c. and *note LZMAFile: fad.  To decompress a
          multi-stream input with *note LZMADecompressor: 165c, you must
          create a new decompressor for each stream.

      -- 方法: decompress (data, max_length=-1)

          Decompress 'data' (a *note bytes-like object: cd4.), returning
          uncompressed data as bytes.  Some of 'data' may be buffered
          internally, for use in later calls to *note decompress():
          287c.  The returned data should be concatenated with the
          output of any previous calls to *note decompress(): 287c.

          If 'max_length' is nonnegative, returns at most 'max_length'
          bytes of decompressed data.  If this limit is reached and
          further output can be produced, the *note needs_input: 287d.
          attribute will be set to ‘False’.  In this case, the next call
          to *note decompress(): dd4. may provide 'data' as ‘b''’ to
          obtain more of the output.

          If all of the input data was decompressed and returned (either
          because this was less than 'max_length' bytes, or because
          'max_length' was negative), the *note needs_input: 287d.
          attribute will be set to ‘True’.

          Attempting to decompress data after the end of stream is
          reached raises an *note EOFError: 126c.  Any data found after
          the end of the stream is ignored and saved in the *note
          unused_data: 287e. attribute.

          在 3.5 版的變更: 新增 'max_length' 參數。

      -- 屬性: check

          The ID of the integrity check used by the input stream.  This
          may be ‘CHECK_UNKNOWN’ until enough of the input has been
          decoded to determine what integrity check it uses.

      -- 屬性: eof

          ‘True’ if the end-of-stream marker has been reached.

      -- 屬性: unused_data

          Data found after the end of the compressed stream.

          Before the end of the stream is reached, this will be ‘b""’.

      -- 屬性: needs_input

          ‘False’ if the *note decompress(): dd4. method can provide
          more decompressed data before requiring new uncompressed
          input.

          在 3.5 版被加入.

 -- 函式: lzma.compress (data, format=FORMAT_XZ, check=-1, preset=None,
          filters=None)

     Compress 'data' (a *note bytes: 1a5. object), returning the
     compressed data as a *note bytes: 1a5. object.

     See *note LZMACompressor: 165e. above for a description of the
     'format', 'check', 'preset' and 'filters' arguments.

 -- 函式: lzma.decompress (data, format=FORMAT_AUTO, memlimit=None,
          filters=None)

     Decompress 'data' (a *note bytes: 1a5. object), returning the
     uncompressed data as a *note bytes: 1a5. object.

     If 'data' is the concatenation of multiple distinct compressed
     streams, decompress all of these streams, and return the
     concatenation of the results.

     See *note LZMADecompressor: 165c. above for a description of the
     'format', 'memlimit' and 'filters' arguments.


File: python.info,  Node: Miscellaneous,  Next: Specifying custom filter chains,  Prev: Compressing and decompressing data in memory,  Up: lzma --- 使用 LZMA 演算法進行壓縮

5.13.4.3 Miscellaneous
......................

 -- 函式: lzma.is_check_supported (check)

     Return ‘True’ if the given integrity check is supported on this
     system.

     ‘CHECK_NONE’ and ‘CHECK_CRC32’ are always supported.  ‘CHECK_CRC64’
     and ‘CHECK_SHA256’ may be unavailable if you are using a version of
     ‘liblzma’ that was compiled with a limited feature set.


File: python.info,  Node: Specifying custom filter chains,  Next: 範例<12>,  Prev: Miscellaneous,  Up: lzma --- 使用 LZMA 演算法進行壓縮

5.13.4.4 Specifying custom filter chains
........................................

A filter chain specifier is a sequence of dictionaries, where each
dictionary contains the ID and options for a single filter.  Each
dictionary must contain the key ‘"id"’, and may contain additional keys
to specify filter-dependent options.  Valid filter IDs are as follows:

   * Compression filters:

        * ‘FILTER_LZMA1’ (for use with ‘FORMAT_ALONE’)

        * ‘FILTER_LZMA2’ (for use with ‘FORMAT_XZ’ and ‘FORMAT_RAW’)

   * Delta filter:

        * ‘FILTER_DELTA’

   * Branch-Call-Jump (BCJ) filters:

        * ‘FILTER_X86’

        * ‘FILTER_IA64’

        * ‘FILTER_ARM’

        * ‘FILTER_ARMTHUMB’

        * ‘FILTER_POWERPC’

        * ‘FILTER_SPARC’

A filter chain can consist of up to 4 filters, and cannot be empty.  The
last filter in the chain must be a compression filter, and any other
filters must be delta or BCJ filters.

Compression filters support the following options (specified as
additional entries in the dictionary representing the filter):

   * ‘preset’: A compression preset to use as a source of default values
     for options that are not specified explicitly.

   * ‘dict_size’: Dictionary size in bytes.  This should be between 4
     KiB and 1.5 GiB (inclusive).

   * ‘lc’: Number of literal context bits.

   * ‘lp’: Number of literal position bits.  The sum ‘lc + lp’ must be
     at most 4.

   * ‘pb’: Number of position bits; must be at most 4.

   * ‘mode’: ‘MODE_FAST’ or ‘MODE_NORMAL’.

   * ‘nice_len’: What should be considered a "nice length" for a match.
     This should be 273 or less.

   * ‘mf’: What match finder to use - ‘MF_HC3’, ‘MF_HC4’, ‘MF_BT2’,
     ‘MF_BT3’, or ‘MF_BT4’.

   * ‘depth’: Maximum search depth used by match finder.  0 (default)
     means to select automatically based on other filter options.

The delta filter stores the differences between bytes, producing more
repetitive input for the compressor in certain circumstances.  It
supports one option, ‘dist’.  This indicates the distance between bytes
to be subtracted.  The default is 1, i.e.  take the differences between
adjacent bytes.

The BCJ filters are intended to be applied to machine code.  They
convert relative branches, calls and jumps in the code to use absolute
addressing, with the aim of increasing the redundancy that can be
exploited by the compressor.  These filters support one option,
‘start_offset’.  This specifies the address that should be mapped to the
beginning of the input data.  The default is 0.


File: python.info,  Node: 範例<12>,  Prev: Specifying custom filter chains,  Up: lzma --- 使用 LZMA 演算法進行壓縮

5.13.4.5 範例
.............

Reading in a compressed file:

     import lzma
     with lzma.open("file.xz") as f:
         file_content = f.read()

Creating a compressed file:

     import lzma
     data = b"Insert Data Here"
     with lzma.open("file.xz", "w") as f:
         f.write(data)

Compressing data in memory:

     import lzma
     data_in = b"Insert Data Here"
     data_out = lzma.compress(data_in)

Incremental compression:

     import lzma
     lzc = lzma.LZMACompressor()
     out1 = lzc.compress(b"Some data\n")
     out2 = lzc.compress(b"Another piece of data\n")
     out3 = lzc.compress(b"Even more data\n")
     out4 = lzc.flush()
     # Concatenate all the partial results:
     result = b"".join([out1, out2, out3, out4])

Writing compressed data to an already-open file:

     import lzma
     with open("file.xz", "wb") as f:
         f.write(b"This data will not be compressed\n")
         with lzma.open(f, "w") as lzf:
             lzf.write(b"This *will* be compressed\n")
         f.write(b"Not compressed\n")

Creating a compressed file using a custom filter chain:

     import lzma
     my_filters = [
         {"id": lzma.FILTER_DELTA, "dist": 5},
         {"id": lzma.FILTER_LZMA2, "preset": 7 | lzma.PRESET_EXTREME},
     ]
     with lzma.open("file.xz", "w", filters=my_filters) as f:
         f.write(b"blah blah blah")


File: python.info,  Node: zipfile --- 處理 ZIP 封存檔案,  Next: tarfile --- 讀取與寫入 tar 封存檔案,  Prev: lzma --- 使用 LZMA 演算法進行壓縮,  Up: 資料壓縮與保存

5.13.5 ‘zipfile’ -- 處理 ZIP 封存檔案
-------------------------------------

'原始碼：'Lib/zipfile/(1)

__________________________________________________________________

The ZIP file format is a common archive and compression standard.  This
module provides tools to create, read, write, append, and list a ZIP
file.  Any advanced use of this module will require an understanding of
the format, as defined in PKZIP Application Note(2).

This module does not currently handle multi-disk ZIP files.  It can
handle ZIP files that use the ZIP64 extensions (that is ZIP files that
are more than 4 GiB in size).  It supports decryption of encrypted files
in ZIP archives, but it currently cannot create an encrypted file.
Decryption is extremely slow as it is implemented in native Python
rather than C.

The module defines the following items:

 -- 例外: zipfile.BadZipFile

     The error raised for bad ZIP files.

     在 3.2 版被加入.

 -- 例外: zipfile.BadZipfile

     Alias of *note BadZipFile: 16e3, for compatibility with older
     Python versions.

     在 3.2 版之後被棄用.

 -- 例外: zipfile.LargeZipFile

     The error raised when a ZIP file would require ZIP64 functionality
     but that has not been enabled.

 -- 類別: zipfile.ZipFile

     The class for reading and writing ZIP files.  See section *note
     ZipFile 物件: 2889. for constructor details.

 -- 類別: zipfile.Path

     Class that implements a subset of the interface provided by *note
     pathlib.Path: 20e, including the full *note
     importlib.resources.abc.Traversable: 1d8. interface.

     在 3.8 版被加入.

 -- 類別: zipfile.PyZipFile

     Class for creating ZIP archives containing Python libraries.

 -- 類別: zipfile.ZipInfo (filename='NoName', date_time=(1980, 1, 1, 0,
          0, 0))

     Class used to represent information about a member of an archive.
     Instances of this class are returned by the *note getinfo(): 288a.
     and *note infolist(): 288b. methods of *note ZipFile: 669. objects.
     Most users of the *note zipfile: 117. module will not need to
     create these, but only use those created by this module.
     'filename' should be the full name of the archive member, and
     'date_time' should be a tuple containing six fields which describe
     the time of the last modification to the file; the fields are
     described in section *note ZipInfo 物件: 288c.

     在 3.13 版的變更: A public ‘compress_level’ attribute has been
     added to expose the formerly protected ‘_compresslevel’.  The older
     protected name continues to work as a property for backwards
     compatibility.

 -- 函式: zipfile.is_zipfile (filename)

     Returns ‘True’ if 'filename' is a valid ZIP file based on its magic
     number, otherwise returns ‘False’.  'filename' may be a file or
     file-like object too.

     在 3.1 版的變更: Support for file and file-like objects.

 -- 資料: zipfile.ZIP_STORED

     The numeric constant for an uncompressed archive member.

 -- 資料: zipfile.ZIP_DEFLATED

     The numeric constant for the usual ZIP compression method.  This
     requires the *note zlib: 119. module.

 -- 資料: zipfile.ZIP_BZIP2

     The numeric constant for the BZIP2 compression method.  This
     requires the *note bz2: f. module.

     在 3.3 版被加入.

 -- 資料: zipfile.ZIP_LZMA

     The numeric constant for the LZMA compression method.  This
     requires the *note lzma: 7e. module.

     在 3.3 版被加入.

          備註: The ZIP file format specification has included support
          for bzip2 compression since 2001, and for LZMA compression
          since 2006.  However, some tools (including older Python
          releases) do not support these compression methods, and may
          either refuse to process the ZIP file altogether, or fail to
          extract individual files.

也參考
......

PKZIP Application Note(3)

     Documentation on the ZIP file format by Phil Katz, the creator of
     the format and algorithms used.

Info-ZIP 首頁(4)

     Information about the Info-ZIP project's ZIP archive programs and
     development libraries.

* Menu:

* ZipFile 物件::
* Path Objects::
* PyZipFile 物件::
* ZipInfo 物件::
* Command-Line Interface::
* Decompression pitfalls::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/zipfile/

   (2) https://pkware.cachefly.net/webdocs/casestudies/APPNOTE.TXT

   (3) https://pkware.cachefly.net/webdocs/casestudies/APPNOTE.TXT

   (4) https://infozip.sourceforge.net/


File: python.info,  Node: ZipFile 物件,  Next: Path Objects,  Up: zipfile --- 處理 ZIP 封存檔案

5.13.5.1 ZipFile 物件
.....................

 -- 類別: zipfile.ZipFile (file, mode='r', compression=ZIP_STORED,
          allowZip64=True, compresslevel=None, *,
          strict_timestamps=True, metadata_encoding=None)

     Open a ZIP file, where 'file' can be a path to a file (a string), a
     file-like object or a *note path-like object: ac2.

     The 'mode' parameter should be ‘'r'’ to read an existing file,
     ‘'w'’ to truncate and write a new file, ‘'a'’ to append to an
     existing file, or ‘'x'’ to exclusively create and write a new file.
     If 'mode' is ‘'x'’ and 'file' refers to an existing file, a *note
     FileExistsError: fc3. will be raised.  If 'mode' is ‘'a'’ and
     'file' refers to an existing ZIP file, then additional files are
     added to it.  If 'file' does not refer to a ZIP file, then a new
     ZIP archive is appended to the file.  This is meant for adding a
     ZIP archive to another file (such as ‘python.exe’).  If 'mode' is
     ‘'a'’ and the file does not exist at all, it is created.  If 'mode'
     is ‘'r'’ or ‘'a'’, the file should be seekable.

     'compression' is the ZIP compression method to use when writing the
     archive, and should be *note ZIP_STORED: 288d, *note ZIP_DEFLATED:
     288e, *note ZIP_BZIP2: 288f. or *note ZIP_LZMA: 2890.; unrecognized
     values will cause *note NotImplementedError: 20d. to be raised.  If
     *note ZIP_DEFLATED: 288e, *note ZIP_BZIP2: 288f. or *note ZIP_LZMA:
     2890. is specified but the corresponding module (*note zlib: 119,
     *note bz2: f. or *note lzma: 7e.) is not available, *note
     RuntimeError: 179. is raised.  The default is *note ZIP_STORED:
     288d.

     If 'allowZip64' is ‘True’ (the default) zipfile will create ZIP
     files that use the ZIP64 extensions when the zipfile is larger than
     4 GiB. If it is ‘false’ *note zipfile: 117. will raise an exception
     when the ZIP file would require ZIP64 extensions.

     The 'compresslevel' parameter controls the compression level to use
     when writing files to the archive.  When using *note ZIP_STORED:
     288d. or *note ZIP_LZMA: 2890. it has no effect.  When using *note
     ZIP_DEFLATED: 288e. integers ‘0’ through ‘9’ are accepted (see
     *note zlib: 2839. for more information).  When using *note
     ZIP_BZIP2: 288f. integers ‘1’ through ‘9’ are accepted (see *note
     bz2: 80b. for more information).

     The 'strict_timestamps' argument, when set to ‘False’, allows to
     zip files older than 1980-01-01 at the cost of setting the
     timestamp to 1980-01-01.  Similar behavior occurs with files newer
     than 2107-12-31, the timestamp is also set to the limit.

     When mode is ‘'r'’, 'metadata_encoding' may be set to the name of a
     codec, which will be used to decode metadata such as the names of
     members and ZIP comments.

     If the file is created with mode ‘'w'’, ‘'x'’ or ‘'a'’ and then
     *note closed: 2892. without adding any files to the archive, the
     appropriate ZIP structures for an empty archive will be written to
     the file.

     ZipFile is also a context manager and therefore supports the *note
     with: 577. statement.  In the example, 'myzip' is closed after the
     ‘with’ statement's suite is finished--even if an exception occurs:

          with ZipFile('spam.zip', 'w') as myzip:
              myzip.write('eggs.txt')

          備註: 'metadata_encoding' is an instance-wide setting for the
          ZipFile.  It is not currently possible to set this on a
          per-member basis.

          This attribute is a workaround for legacy implementations
          which produce archives with names in the current locale
          encoding or code page (mostly on Windows).  According to the
          .ZIP standard, the encoding of metadata may be specified to be
          either IBM code page (default) or UTF-8 by a flag in the
          archive header.  That flag takes precedence over
          'metadata_encoding', which is a Python-specific extension.

     在 3.2 版的變更: 新增 *note ZipFile: 669. 作為情境管理器使用的能力
     。

     在 3.3 版的變更: 新增對於 *note bzip2: f. 和 *note lzma: 7e. 壓縮的
     支援。

     在 3.4 版的變更: ZIP64 extensions are enabled by default.

     在 3.5 版的變更: Added support for writing to unseekable streams.
     Added support for the ‘'x'’ mode.

     在 3.6 版的變更: Previously, a plain *note RuntimeError: 179. was
     raised for unrecognized compression values.

     在 3.6.2 版的變更: The 'file' parameter accepts a *note path-like
     object: ac2.

     在 3.7 版的變更: Add the 'compresslevel' parameter.

     在 3.8 版的變更: The 'strict_timestamps' keyword-only parameter.

     在 3.11 版的變更: Added support for specifying member name encoding
     for reading metadata in the zipfile's directory and file headers.

 -- 方法: ZipFile.close ()

     Close the archive file.  You must call *note close(): 2892. before
     exiting your program or essential records will not be written.

 -- 方法: ZipFile.getinfo (name)

     Return a *note ZipInfo: cb1. object with information about the
     archive member 'name'.  Calling *note getinfo(): 288a. for a name
     not currently contained in the archive will raise a *note KeyError:
     2fb.

 -- 方法: ZipFile.infolist ()

     Return a list containing a *note ZipInfo: cb1. object for each
     member of the archive.  The objects are in the same order as their
     entries in the actual ZIP file on disk if an existing archive was
     opened.

 -- 方法: ZipFile.namelist ()

     Return a list of archive members by name.

 -- 方法: ZipFile.open (name, mode='r', pwd=None, *, force_zip64=False)

     Access a member of the archive as a binary file-like object.
     'name' can be either the name of a file within the archive or a
     *note ZipInfo: cb1. object.  The 'mode' parameter, if included,
     must be ‘'r'’ (the default) or ‘'w'’.  'pwd' is the password used
     to decrypt encrypted ZIP files as a *note bytes: 1a5. object.

     *note open(): 355. is also a context manager and therefore supports
     the *note with: 577. statement:

          with ZipFile('spam.zip') as myzip:
              with myzip.open('eggs.txt') as myfile:
                  print(myfile.read())

     With 'mode' ‘'r'’ the file-like object (‘ZipExtFile’) is read-only
     and provides the following methods: *note read(): 12bc, *note
     readline(): 12bd, *note readlines(): 2211, *note seek(): 1224,
     *note tell(): 2894, *note __iter__(): 1bc4, *note __next__(): 1260.
     These objects can operate independently of the ZipFile.

     With ‘mode='w'’, a writable file handle is returned, which supports
     the *note write(): c82. method.  While a writable file handle is
     open, attempting to read or write other files in the ZIP file will
     raise a *note ValueError: 1e7.

     In both cases the file-like object has also attributes ‘name’,
     which is equivalent to the name of a file within the archive, and
     ‘mode’, which is ‘'rb'’ or ‘'wb'’ depending on the input mode.

     When writing a file, if the file size is not known in advance but
     may exceed 2 GiB, pass ‘force_zip64=True’ to ensure that the header
     format is capable of supporting large files.  If the file size is
     known in advance, construct a *note ZipInfo: cb1. object with *note
     file_size: 2895. set, and use that as the 'name' parameter.

          備註: The *note open(): 355, *note read(): 2896. and *note
          extract(): 2897. methods can take a filename or a *note
          ZipInfo: cb1. object.  You will appreciate this when trying to
          read a ZIP file that contains members with duplicate names.

     在 3.6 版的變更: Removed support of ‘mode='U'’.  Use *note
     io.TextIOWrapper: 75f. for reading compressed text files in *note
     universal newlines: ce1. mode.

     在 3.6 版的變更: *note ZipFile.open(): 355. can now be used to
     write files into the archive with the ‘mode='w'’ option.

     在 3.6 版的變更: Calling *note open(): 355. on a closed ZipFile
     will raise a *note ValueError: 1e7.  Previously, a *note
     RuntimeError: 179. was raised.

     在 3.13 版的變更: Added attributes ‘name’ and ‘mode’ for the
     writeable file-like object.  The value of the ‘mode’ attribute for
     the readable file-like object was changed from ‘'r'’ to ‘'rb'’.

 -- 方法: ZipFile.extract (member, path=None, pwd=None)

     Extract a member from the archive to the current working directory;
     'member' must be its full name or a *note ZipInfo: cb1. object.
     Its file information is extracted as accurately as possible.
     'path' specifies a different directory to extract to.  'member' can
     be a filename or a *note ZipInfo: cb1. object.  'pwd' is the
     password used for encrypted files as a *note bytes: 1a5. object.

     Returns the normalized path created (a directory or new file).

          備註: If a member filename is an absolute path, a drive/UNC
          sharepoint and leading (back)slashes will be stripped, e.g.:
          ‘///foo/bar’ becomes ‘foo/bar’ on Unix, and ‘C:\foo\bar’
          becomes ‘foo\bar’ on Windows.  And all ‘".."’ components in a
          member filename will be removed, e.g.: ‘../../foo../../ba..r’
          becomes ‘foo../ba..r’.  On Windows illegal characters (‘:’,
          ‘<’, ‘>’, ‘|’, ‘"’, ‘?’, and ‘*’) replaced by underscore
          (‘_’).

     在 3.6 版的變更: Calling *note extract(): 2897. on a closed ZipFile
     will raise a *note ValueError: 1e7.  Previously, a *note
     RuntimeError: 179. was raised.

     在 3.6.2 版的變更: The 'path' parameter accepts a *note path-like
     object: ac2.

 -- 方法: ZipFile.extractall (path=None, members=None, pwd=None)

     Extract all members from the archive to the current working
     directory.  'path' specifies a different directory to extract to.
     'members' is optional and must be a subset of the list returned by
     *note namelist(): 2893.  'pwd' is the password used for encrypted
     files as a *note bytes: 1a5. object.

          警告: Never extract archives from untrusted sources without
          prior inspection.  It is possible that files are created
          outside of 'path', e.g.  members that have absolute filenames
          starting with ‘"/"’ or filenames with two dots ‘".."’.  This
          module attempts to prevent that.  See *note extract(): 2897.
          note.

     在 3.6 版的變更: Calling *note extractall(): 2898. on a closed
     ZipFile will raise a *note ValueError: 1e7.  Previously, a *note
     RuntimeError: 179. was raised.

     在 3.6.2 版的變更: The 'path' parameter accepts a *note path-like
     object: ac2.

 -- 方法: ZipFile.printdir ()

     Print a table of contents for the archive to ‘sys.stdout’.

 -- 方法: ZipFile.setpassword (pwd)

     Set 'pwd' (a *note bytes: 1a5. object) as default password to
     extract encrypted files.

 -- 方法: ZipFile.read (name, pwd=None)

     Return the bytes of the file 'name' in the archive.  'name' is the
     name of the file in the archive, or a *note ZipInfo: cb1. object.
     The archive must be open for read or append.  'pwd' is the password
     used for encrypted files as a *note bytes: 1a5. object and, if
     specified, overrides the default password set with *note
     setpassword(): 289a.  Calling *note read(): 2896. on a ZipFile that
     uses a compression method other than *note ZIP_STORED: 288d, *note
     ZIP_DEFLATED: 288e, *note ZIP_BZIP2: 288f. or *note ZIP_LZMA: 2890.
     will raise a *note NotImplementedError: 20d.  An error will also be
     raised if the corresponding compression module is not available.

     在 3.6 版的變更: Calling *note read(): 2896. on a closed ZipFile
     will raise a *note ValueError: 1e7.  Previously, a *note
     RuntimeError: 179. was raised.

 -- 方法: ZipFile.testzip ()

     Read all the files in the archive and check their CRC's and file
     headers.  Return the name of the first bad file, or else return
     ‘None’.

     在 3.6 版的變更: Calling *note testzip(): 289b. on a closed ZipFile
     will raise a *note ValueError: 1e7.  Previously, a *note
     RuntimeError: 179. was raised.

 -- 方法: ZipFile.write (filename, arcname=None, compress_type=None,
          compresslevel=None)

     Write the file named 'filename' to the archive, giving it the
     archive name 'arcname' (by default, this will be the same as
     'filename', but without a drive letter and with leading path
     separators removed).  If given, 'compress_type' overrides the value
     given for the 'compression' parameter to the constructor for the
     new entry.  Similarly, 'compresslevel' will override the
     constructor if given.  The archive must be open with mode ‘'w'’,
     ‘'x'’ or ‘'a'’.

          備註: The ZIP file standard historically did not specify a
          metadata encoding, but strongly recommended CP437 (the
          original IBM PC encoding) for interoperability.  Recent
          versions allow use of UTF-8 (only).  In this module, UTF-8
          will automatically be used to write the member names if they
          contain any non-ASCII characters.  It is not possible to write
          member names in any encoding other than ASCII or UTF-8.

          備註: Archive names should be relative to the archive root,
          that is, they should not start with a path separator.

          備註: If ‘arcname’ (or ‘filename’, if ‘arcname’ is not given)
          contains a null byte, the name of the file in the archive will
          be truncated at the null byte.

          備註: A leading slash in the filename may lead to the archive
          being impossible to open in some zip programs on Windows
          systems.

     在 3.6 版的變更: Calling *note write(): cf3. on a ZipFile created
     with mode ‘'r'’ or a closed ZipFile will raise a *note ValueError:
     1e7.  Previously, a *note RuntimeError: 179. was raised.

 -- 方法: ZipFile.writestr (zinfo_or_arcname, data, compress_type=None,
          compresslevel=None)

     Write a file into the archive.  The contents is 'data', which may
     be either a *note str: 3f2. or a *note bytes: 1a5. instance; if it
     is a *note str: 3f2, it is encoded as UTF-8 first.
     'zinfo_or_arcname' is either the file name it will be given in the
     archive, or a *note ZipInfo: cb1. instance.  If it's an instance,
     at least the filename, date, and time must be given.  If it's a
     name, the date and time is set to the current date and time.  The
     archive must be opened with mode ‘'w'’, ‘'x'’ or ‘'a'’.

     If given, 'compress_type' overrides the value given for the
     'compression' parameter to the constructor for the new entry, or in
     the 'zinfo_or_arcname' (if that is a *note ZipInfo: cb1. instance).
     Similarly, 'compresslevel' will override the constructor if given.

          備註: When passing a *note ZipInfo: cb1. instance as the
          'zinfo_or_arcname' parameter, the compression method used will
          be that specified in the 'compress_type' member of the given
          *note ZipInfo: cb1. instance.  By default, the *note ZipInfo:
          cb1. constructor sets this member to *note ZIP_STORED: 288d.

     在 3.2 版的變更: 'compress_type' 引數。

     在 3.6 版的變更: Calling *note writestr(): 12bf. on a ZipFile
     created with mode ‘'r'’ or a closed ZipFile will raise a *note
     ValueError: 1e7.  Previously, a *note RuntimeError: 179. was
     raised.

 -- 方法: ZipFile.mkdir (zinfo_or_directory, mode=511)

     Create a directory inside the archive.  If 'zinfo_or_directory' is
     a string, a directory is created inside the archive with the mode
     that is specified in the 'mode' argument.  If, however,
     'zinfo_or_directory' is a *note ZipInfo: cb1. instance then the
     'mode' argument is ignored.

     The archive must be opened with mode ‘'w'’, ‘'x'’ or ‘'a'’.

     在 3.11 版被加入.

The following data attributes are also available:

 -- 屬性: ZipFile.filename

     Name of the ZIP file.

 -- 屬性: ZipFile.debug

     The level of debug output to use.  This may be set from ‘0’ (the
     default, no output) to ‘3’ (the most output).  Debugging
     information is written to ‘sys.stdout’.

 -- 屬性: ZipFile.comment

     The comment associated with the ZIP file as a *note bytes: 1a5.
     object.  If assigning a comment to a *note ZipFile: 669. instance
     created with mode ‘'w'’, ‘'x'’ or ‘'a'’, it should be no longer
     than 65535 bytes.  Comments longer than this will be truncated.


File: python.info,  Node: Path Objects,  Next: PyZipFile 物件,  Prev: ZipFile 物件,  Up: zipfile --- 處理 ZIP 封存檔案

5.13.5.2 Path Objects
.....................

 -- 類別: zipfile.Path (root, at='')

     Construct a Path object from a ‘root’ zipfile (which may be a *note
     ZipFile: 669. instance or ‘file’ suitable for passing to the *note
     ZipFile: 669. constructor).

     ‘at’ specifies the location of this Path within the zipfile, e.g.
     'dir/file.txt', 'dir/', or ''.  Defaults to the empty string,
     indicating the root.

Path objects expose the following features of *note pathlib.Path: 20e.
objects:

Path objects are traversable using the ‘/’ operator or ‘joinpath’.

 -- 屬性: Path.name

     The final path component.

 -- 方法: Path.open (mode='r', *, pwd, **)

     Invoke *note ZipFile.open(): 355. on the current path.  Allows
     opening for read or write, text or binary through supported modes:
     'r', 'w', 'rb', 'wb'.  Positional and keyword arguments are passed
     through to *note io.TextIOWrapper: 75f. when opened as text and
     ignored otherwise.  ‘pwd’ is the ‘pwd’ parameter to *note
     ZipFile.open(): 355.

     在 3.9 版的變更: Added support for text and binary modes for open.
     Default mode is now text.

     在 3.11.2 版的變更: The ‘encoding’ parameter can be supplied as a
     positional argument without causing a *note TypeError: 4dd.  As it
     could in 3.9.  Code needing to be compatible with unpatched 3.10
     and 3.11 versions must pass all *note io.TextIOWrapper: 75f.
     arguments, ‘encoding’ included, as keywords.

 -- 方法: Path.iterdir ()

     Enumerate the children of the current directory.

 -- 方法: Path.is_dir ()

     Return ‘True’ if the current context references a directory.

 -- 方法: Path.is_file ()

     Return ‘True’ if the current context references a file.

 -- 方法: Path.is_symlink ()

     Return ‘True’ if the current context references a symbolic link.

     在 3.12 版被加入.

     在 3.13 版的變更: Previously, ‘is_symlink’ would unconditionally
     return ‘False’.

 -- 方法: Path.exists ()

     Return ‘True’ if the current context references a file or directory
     in the zip file.

 -- 資料: Path.suffix

     The last dot-separated portion of the final component, if any.
     This is commonly called the file extension.

     在 3.11 版被加入: 新增 *note Path.suffix: 66d. 特性。

 -- 資料: Path.stem

     The final path component, without its suffix.

     在 3.11 版被加入: 新增 *note Path.stem: 66c. 特性。

 -- 資料: Path.suffixes

     A list of the path’s suffixes, commonly called file extensions.

     在 3.11 版被加入: 新增 *note Path.suffixes: 66e. 特性。

 -- 方法: Path.read_text (*, **)

     Read the current file as unicode text.  Positional and keyword
     arguments are passed through to *note io.TextIOWrapper: 75f.
     (except ‘buffer’, which is implied by the context).

     在 3.11.2 版的變更: The ‘encoding’ parameter can be supplied as a
     positional argument without causing a *note TypeError: 4dd.  As it
     could in 3.9.  Code needing to be compatible with unpatched 3.10
     and 3.11 versions must pass all *note io.TextIOWrapper: 75f.
     arguments, ‘encoding’ included, as keywords.

 -- 方法: Path.read_bytes ()

     Read the current file as bytes.

 -- 方法: Path.joinpath (*other)

     Return a new Path object with each of the 'other' arguments joined.
     The following are equivalent:

          >>> Path(...).joinpath('child').joinpath('grandchild')
          >>> Path(...).joinpath('child', 'grandchild')
          >>> Path(...) / 'child' / 'grandchild'

     在 3.10 版的變更: Prior to 3.10, ‘joinpath’ was undocumented and
     accepted exactly one parameter.

The zipp(1) project provides backports of the latest path object
functionality to older Pythons.  Use ‘zipp.Path’ in place of
‘zipfile.Path’ for early access to changes.

   ---------- Footnotes ----------

   (1) https://pypi.org/project/zipp/


File: python.info,  Node: PyZipFile 物件,  Next: ZipInfo 物件,  Prev: Path Objects,  Up: zipfile --- 處理 ZIP 封存檔案

5.13.5.3 PyZipFile 物件
.......................

The *note PyZipFile: f9b. constructor takes the same parameters as the
*note ZipFile: 669. constructor, and one additional parameter,
'optimize'.

 -- 類別: zipfile.PyZipFile (file, mode='r', compression=ZIP_STORED,
          allowZip64=True, optimize=-1)

     在 3.2 版的變更: 新增 'optimize' 參數。

     在 3.4 版的變更: ZIP64 extensions are enabled by default.

     Instances have one method in addition to those of *note ZipFile:
     669. objects:

      -- 方法: writepy (pathname, basename='', filterfunc=None)

          Search for files ‘*.py’ and add the corresponding file to the
          archive.

          If the 'optimize' parameter to *note PyZipFile: f9b. was not
          given or ‘-1’, the corresponding file is a ‘*.pyc’ file,
          compiling if necessary.

          If the 'optimize' parameter to *note PyZipFile: f9b. was ‘0’,
          ‘1’ or ‘2’, only files with that optimization level (see *note
          compile(): 178.) are added to the archive, compiling if
          necessary.

          If 'pathname' is a file, the filename must end with ‘.py’, and
          just the (corresponding ‘*.pyc’) file is added at the top
          level (no path information).  If 'pathname' is a file that
          does not end with ‘.py’, a *note RuntimeError: 179. will be
          raised.  If it is a directory, and the directory is not a
          package directory, then all the files ‘*.pyc’ are added at the
          top level.  If the directory is a package directory, then all
          ‘*.pyc’ are added under the package name as a file path, and
          if any subdirectories are package directories, all of these
          are added recursively in sorted order.

          'basename' is intended for internal use only.

          'filterfunc', if given, must be a function taking a single
          string argument.  It will be passed each path (including each
          individual full file path) before it is added to the archive.
          If 'filterfunc' returns a false value, the path will not be
          added, and if it is a directory its contents will be ignored.
          For example, if our test files are all either in ‘test’
          directories or start with the string ‘test_’, we can use a
          'filterfunc' to exclude them:

               >>> zf = PyZipFile('myprog.zip')
               >>> def notests(s):
               ...     fn = os.path.basename(s)
               ...     return (not (fn == 'test' or fn.startswith('test_')))
               ...
               >>> zf.writepy('myprog', filterfunc=notests)

          The *note writepy(): f9a. method makes archives with file
          names like this:

               string.pyc                   # Top level name
               test/__init__.pyc            # Package directory
               test/testall.pyc             # Module test.testall
               test/bogus/__init__.pyc      # Subpackage directory
               test/bogus/myfile.pyc        # Submodule test.bogus.myfile

          在 3.4 版的變更: 新增 'filterfunc' 參數。

          在 3.6.2 版的變更: The 'pathname' parameter accepts a *note
          path-like object: ac2.

          在 3.7 版的變更: Recursion sorts directory entries.


File: python.info,  Node: ZipInfo 物件,  Next: Command-Line Interface,  Prev: PyZipFile 物件,  Up: zipfile --- 處理 ZIP 封存檔案

5.13.5.4 ZipInfo 物件
.....................

Instances of the *note ZipInfo: cb1. class are returned by the *note
getinfo(): 288a. and *note infolist(): 288b. methods of *note ZipFile:
669. objects.  Each object stores information about a single member of
the ZIP archive.

There is one classmethod to make a *note ZipInfo: cb1. instance for a
filesystem file:

 -- 方法: classmethod ZipInfo.from_file (filename, arcname=None, *,
          strict_timestamps=True)

     Construct a *note ZipInfo: cb1. instance for a file on the
     filesystem, in preparation for adding it to a zip file.

     'filename' should be the path to a file or directory on the
     filesystem.

     If 'arcname' is specified, it is used as the name within the
     archive.  If 'arcname' is not specified, the name will be the same
     as 'filename', but with any drive letter and leading path
     separators removed.

     The 'strict_timestamps' argument, when set to ‘False’, allows to
     zip files older than 1980-01-01 at the cost of setting the
     timestamp to 1980-01-01.  Similar behavior occurs with files newer
     than 2107-12-31, the timestamp is also set to the limit.

     在 3.6 版被加入.

     在 3.6.2 版的變更: The 'filename' parameter accepts a *note
     path-like object: ac2.

     在 3.8 版的變更: 新增 'strict_timestamps' 僅限關鍵字參數。

Instances have the following methods and attributes:

 -- 方法: ZipInfo.is_dir ()

     Return ‘True’ if this archive member is a directory.

     This uses the entry's name: directories should always end with ‘/’.

     在 3.6 版被加入.

 -- 屬性: ZipInfo.filename

     Name of the file in the archive.

 -- 屬性: ZipInfo.date_time

     The time and date of the last modification to the archive member.
     This is a tuple of six values:

     Index       Value
                 
     -------------------------------------------
                 
     ‘0’         Year (>= 1980)
                 
                 
     ‘1’         Month (one-based)
                 
                 
     ‘2’         Day of month (one-based)
                 
                 
     ‘3’         Hours (zero-based)
                 
                 
     ‘4’         Minutes (zero-based)
                 
                 
     ‘5’         Seconds (zero-based)
                 

          備註: The ZIP file format does not support timestamps before
          1980.

 -- 屬性: ZipInfo.compress_type

     Type of compression for the archive member.

 -- 屬性: ZipInfo.comment

     Comment for the individual archive member as a *note bytes: 1a5.
     object.

 -- 屬性: ZipInfo.extra

     Expansion field data.  The PKZIP Application Note(1) contains some
     comments on the internal structure of the data contained in this
     *note bytes: 1a5. object.

 -- 屬性: ZipInfo.create_system

     System which created ZIP archive.

 -- 屬性: ZipInfo.create_version

     PKZIP version which created ZIP archive.

 -- 屬性: ZipInfo.extract_version

     PKZIP version needed to extract archive.

 -- 屬性: ZipInfo.reserved

     Must be zero.

 -- 屬性: ZipInfo.flag_bits

     ZIP flag bits.

 -- 屬性: ZipInfo.volume

     Volume number of file header.

 -- 屬性: ZipInfo.internal_attr

     Internal attributes.

 -- 屬性: ZipInfo.external_attr

     External file attributes.

 -- 屬性: ZipInfo.header_offset

     Byte offset to the file header.

 -- 屬性: ZipInfo.CRC

     CRC-32 of the uncompressed file.

 -- 屬性: ZipInfo.compress_size

     Size of the compressed data.

 -- 屬性: ZipInfo.file_size

     Size of the uncompressed file.

   ---------- Footnotes ----------

   (1) https://pkware.cachefly.net/webdocs/casestudies/APPNOTE.TXT


File: python.info,  Node: Command-Line Interface,  Next: Decompression pitfalls,  Prev: ZipInfo 物件,  Up: zipfile --- 處理 ZIP 封存檔案

5.13.5.5 Command-Line Interface
...............................

The *note zipfile: 117. module provides a simple command-line interface
to interact with ZIP archives.

If you want to create a new ZIP archive, specify its name after the
*note -c: 28be. option and then list the filename(s) that should be
included:

     $ python -m zipfile -c monty.zip spam.txt eggs.txt

Passing a directory is also acceptable:

     $ python -m zipfile -c monty.zip life-of-brian_1979/

If you want to extract a ZIP archive into the specified directory, use
the *note -e: 28bf. option:

     $ python -m zipfile -e monty.zip target-dir/

For a list of the files in a ZIP archive, use the *note -l: 28c0.
option:

     $ python -m zipfile -l monty.zip

* Menu:

* Command-line options::


File: python.info,  Node: Command-line options,  Up: Command-Line Interface

5.13.5.6 Command-line options
.............................

 -- Option: -l <zipfile>
 -- Option: --list <zipfile>

     List files in a zipfile.

 -- Option: -c <zipfile> <source1> ... <sourceN>
 -- Option: --create <zipfile> <source1> ... <sourceN>

     Create zipfile from source files.

 -- Option: -e <zipfile> <output_dir>
 -- Option: --extract <zipfile> <output_dir>

     Extract zipfile into target directory.

 -- Option: -t <zipfile>
 -- Option: --test <zipfile>

     Test whether the zipfile is valid or not.

 -- Option: --metadata-encoding <encoding>

     Specify encoding of member names for *note -l: 28c0, *note -e:
     28bf. and *note -t: 28c5.

     在 3.11 版被加入.


File: python.info,  Node: Decompression pitfalls,  Prev: Command-Line Interface,  Up: zipfile --- 處理 ZIP 封存檔案

5.13.5.7 Decompression pitfalls
...............................

The extraction in zipfile module might fail due to some pitfalls listed
below.

* Menu:

* From file itself::
* File System limitations::
* Resources limitations::
* Interruption::
* Default behaviors of extraction::


File: python.info,  Node: From file itself,  Next: File System limitations,  Up: Decompression pitfalls

5.13.5.8 From file itself
.........................

Decompression may fail due to incorrect password / CRC checksum / ZIP
format or unsupported compression method / decryption.


File: python.info,  Node: File System limitations,  Next: Resources limitations,  Prev: From file itself,  Up: Decompression pitfalls

5.13.5.9 File System limitations
................................

Exceeding limitations on different file systems can cause decompression
failed.  Such as allowable characters in the directory entries, length
of the file name, length of the pathname, size of a single file, and
number of files, etc.


File: python.info,  Node: Resources limitations,  Next: Interruption,  Prev: File System limitations,  Up: Decompression pitfalls

5.13.5.10 Resources limitations
...............................

The lack of memory or disk volume would lead to decompression failed.
For example, decompression bombs (aka ZIP bomb(1)) apply to zipfile
library that can cause disk volume exhaustion.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Zip_bomb


File: python.info,  Node: Interruption,  Next: Default behaviors of extraction,  Prev: Resources limitations,  Up: Decompression pitfalls

5.13.5.11 Interruption
......................

Interruption during the decompression, such as pressing control-C or
killing the decompression process may result in incomplete decompression
of the archive.


File: python.info,  Node: Default behaviors of extraction,  Prev: Interruption,  Up: Decompression pitfalls

5.13.5.12 Default behaviors of extraction
.........................................

Not knowing the default extraction behaviors can cause unexpected
decompression results.  For example, when extracting the same archive
twice, it overwrites files without asking.


File: python.info,  Node: tarfile --- 讀取與寫入 tar 封存檔案,  Prev: zipfile --- 處理 ZIP 封存檔案,  Up: 資料壓縮與保存

5.13.6 ‘tarfile’ -- 讀取與寫入 tar 封存檔案
-------------------------------------------

'原始碼：'Lib/tarfile.py(1)

__________________________________________________________________

The *note tarfile: c8. module makes it possible to read and write tar
archives, including those using gzip, bz2 and lzma compression.  Use the
*note zipfile: 117. module to read or write ‘.zip’ files, or the
higher-level functions in *note shutil: 11b0.

Some facts and figures:

   * reads and writes *note gzip: 5d, *note bz2: f. and *note lzma: 7e.
     compressed archives if the respective modules are available.

   * read/write support for the POSIX.1-1988 (ustar) format.

   * read/write support for the GNU tar format including 'longname' and
     'longlink' extensions, read-only support for all variants of the
     'sparse' extension including restoration of sparse files.

   * read/write support for the POSIX.1-2001 (pax) format.

   * handles directories, regular files, hardlinks, symbolic links,
     fifos, character devices and block devices and is able to acquire
     and restore file information like timestamp, access permissions and
     owner.

在 3.3 版的變更: Added support for *note lzma: 7e. compression.

在 3.12 版的變更: Archives are extracted using a *note filter: 413,
which makes it possible to either limit surprising/dangerous features,
or to acknowledge that they are expected and the archive is fully
trusted.  By default, archives are fully trusted, but this default is
deprecated and slated to change in Python 3.14.

 -- 函式: tarfile.open (name=None, mode='r', fileobj=None,
          bufsize=10240, **kwargs)

     Return a *note TarFile: 290. object for the pathname 'name'.  For
     detailed information on *note TarFile: 290. objects and the keyword
     arguments that are allowed, see *note TarFile 物件: 28d1.

     'mode' has to be a string of the form ‘'filemode[:compression]'’,
     it defaults to ‘'r'’.  Here is a full list of mode combinations:

     mode                   action
                            
     -------------------------------------------------------------------------
                            
     ‘'r' 或 'r:*'’         Open for reading with transparent compression
                            (recommended).
                            
                            
     ‘'r:'’                 Open for reading exclusively without
                            compression.
                            
                            
     ‘'r:gz'’               Open for reading with gzip compression.
                            
                            
     ‘'r:bz2'’              Open for reading with bzip2 compression.
                            
                            
     ‘'r:xz'’               Open for reading with lzma compression.
                            
                            
     ‘'x'’ 或 ‘'x:'’        Create a tarfile exclusively without
                            compression.  Raise a
                            *note FileExistsError: fc3. exception if it
                            already exists.
                            
                            
     ‘'x:gz'’               Create a tarfile with gzip compression.  Raise
                            a *note FileExistsError: fc3. exception if it
                            already exists.
                            
                            
     ‘'x:bz2'’              Create a tarfile with bzip2 compression.  Raise
                            a *note FileExistsError: fc3. exception if it
                            already exists.
                            
                            
     ‘'x:xz'’               Create a tarfile with lzma compression.  Raise
                            a *note FileExistsError: fc3. exception if it
                            already exists.
                            
                            
     ‘'a' 或 'a:'’          Open for appending with no compression.  The
                            file is created if it does not exist.
                            
                            
     ‘'w' 或 'w:'’          Open for uncompressed writing.
                            
                            
     ‘'w:gz'’               Open for gzip compressed writing.
                            
                            
     ‘'w:bz2'’              Open for bzip2 compressed writing.
                            
                            
     ‘'w:xz'’               Open for lzma compressed writing.
                            

     Note that ‘'a:gz'’, ‘'a:bz2'’ or ‘'a:xz'’ is not possible.  If
     'mode' is not suitable to open a certain (compressed) file for
     reading, *note ReadError: 179d. is raised.  Use 'mode' ‘'r'’ to
     avoid this.  If a compression method is not supported, *note
     CompressionError: 28d2. is raised.

     If 'fileobj' is specified, it is used as an alternative to a *note
     file object: 115b. opened in binary mode for 'name'.  It is
     supposed to be at position 0.

     For modes ‘'w:gz'’, ‘'x:gz'’, ‘'w|gz'’, ‘'w:bz2'’, ‘'x:bz2'’,
     ‘'w|bz2'’, *note tarfile.open(): e19. accepts the keyword argument
     'compresslevel' (default ‘9’) to specify the compression level of
     the file.

     For modes ‘'w:xz'’ and ‘'x:xz'’, *note tarfile.open(): e19. accepts
     the keyword argument 'preset' to specify the compression level of
     the file.

     For special purposes, there is a second format for 'mode':
     ‘'filemode|[compression]'’.  *note tarfile.open(): e19. will return
     a *note TarFile: 290. object that processes its data as a stream of
     blocks.  No random seeking will be done on the file.  If given,
     'fileobj' may be any object that has a *note read(): dc2. or *note
     write(): 28d3. method (depending on the 'mode') that works with
     bytes.  'bufsize' specifies the blocksize and defaults to ‘20 *
     512’ bytes.  Use this variant in combination with e.g.
     ‘sys.stdin.buffer’, a socket *note file object: 115b. or a tape
     device.  However, such a *note TarFile: 290. object is limited in
     that it does not allow random access, see *note 範例: 28d4.  The
     currently possible modes:

     Mode              Action
                       
     -------------------------------------------------------------------
                       
     ‘'r|*'’           Open a 'stream' of tar blocks for reading with
                       transparent compression.
                       
                       
     ‘'r|'’            Open a 'stream' of uncompressed tar blocks for
                       reading.
                       
                       
     ‘'r|gz'’          Open a gzip compressed 'stream' for reading.
                       
                       
     ‘'r|bz2'’         Open a bzip2 compressed 'stream' for reading.
                       
                       
     ‘'r|xz'’          Open an lzma compressed 'stream' for reading.
                       
                       
     ‘'w|'’            Open an uncompressed 'stream' for writing.
                       
                       
     ‘'w|gz'’          Open a gzip compressed 'stream' for writing.
                       
                       
     ‘'w|bz2'’         Open a bzip2 compressed 'stream' for writing.
                       
                       
     ‘'w|xz'’          Open an lzma compressed 'stream' for writing.
                       

     在 3.5 版的變更: The ‘'x'’ (exclusive creation) mode was added.

     在 3.6 版的變更: The 'name' parameter accepts a *note path-like
     object: ac2.

     在 3.12 版的變更: The 'compresslevel' keyword argument also works
     for streams.

 -- 類別: tarfile.TarFile

     Class for reading and writing tar archives.  Do not use this class
     directly: use *note tarfile.open(): e19. instead.  See *note
     TarFile 物件: 28d1.

 -- 函式: tarfile.is_tarfile (name)

     Return *note True: bb4. if 'name' is a tar archive file, that the
     *note tarfile: c8. module can read.  'name' may be a *note str:
     3f2, file, or file-like object.

     在 3.9 版的變更: Support for file and file-like objects.

The *note tarfile: c8. module defines the following exceptions:

 -- 例外: tarfile.TarError

     Base class for all *note tarfile: c8. exceptions.

 -- 例外: tarfile.ReadError

     Is raised when a tar archive is opened, that either cannot be
     handled by the *note tarfile: c8. module or is somehow invalid.

 -- 例外: tarfile.CompressionError

     Is raised when a compression method is not supported or when the
     data cannot be decoded properly.

 -- 例外: tarfile.StreamError

     Is raised for the limitations that are typical for stream-like
     *note TarFile: 290. objects.

 -- 例外: tarfile.ExtractError

     Is raised for 'non-fatal' errors when using *note
     TarFile.extract(): e1b, but only if *note TarFile.errorlevel:
     28d8.‘== 2’.

 -- 例外: tarfile.HeaderError

     Is raised by *note TarInfo.frombuf(): 28da. if the buffer it gets
     is invalid.

 -- 例外: tarfile.FilterError

     Base class for members *note refused: 28dc. by filters.

      -- 屬性: tarinfo

          Information about the member that the filter refused to
          extract, as *note TarInfo: 28de.

 -- 例外: tarfile.AbsolutePathError

     Raised to refuse extracting a member with an absolute path.

 -- 例外: tarfile.OutsideDestinationError

     Raised to refuse extracting a member outside the destination
     directory.

 -- 例外: tarfile.SpecialFileError

     Raised to refuse extracting a special file (e.g.  a device or
     pipe).

 -- 例外: tarfile.AbsoluteLinkError

     Raised to refuse extracting a symbolic link with an absolute path.

 -- 例外: tarfile.LinkOutsideDestinationError

     Raised to refuse extracting a symbolic link pointing outside the
     destination directory.

The following constants are available at the module level:

 -- 資料: tarfile.ENCODING

     The default character encoding: ‘'utf-8'’ on Windows, the value
     returned by *note sys.getfilesystemencoding(): c00. otherwise.

 -- 資料: tarfile.REGTYPE
 -- 資料: tarfile.AREGTYPE

     A regular file *note type: 28e7.

 -- 資料: tarfile.LNKTYPE

     A link (inside tarfile) *note type: 28e7.

 -- 資料: tarfile.SYMTYPE

     A symbolic link *note type: 28e7.

 -- 資料: tarfile.CHRTYPE

     A character special device *note type: 28e7.

 -- 資料: tarfile.BLKTYPE

     A block special device *note type: 28e7.

 -- 資料: tarfile.DIRTYPE

     A directory *note type: 28e7.

 -- 資料: tarfile.FIFOTYPE

     A FIFO special device *note type: 28e7.

 -- 資料: tarfile.CONTTYPE

     A contiguous file *note type: 28e7.

 -- 資料: tarfile.GNUTYPE_LONGNAME

     A GNU tar longname *note type: 28e7.

 -- 資料: tarfile.GNUTYPE_LONGLINK

     A GNU tar longlink *note type: 28e7.

 -- 資料: tarfile.GNUTYPE_SPARSE

     A GNU tar sparse file *note type: 28e7.

Each of the following constants defines a tar archive format that the
*note tarfile: c8. module is able to create.  See section *note
Supported tar formats: 28f2. for details.

 -- 資料: tarfile.USTAR_FORMAT

     POSIX.1-1988 (ustar) format.

 -- 資料: tarfile.GNU_FORMAT

     GNU tar format.

 -- 資料: tarfile.PAX_FORMAT

     POSIX.1-2001 (pax) format.

 -- 資料: tarfile.DEFAULT_FORMAT

     The default format for creating archives.  This is currently *note
     PAX_FORMAT: 28f5.

     在 3.8 版的變更: The default format for new archives was changed to
     *note PAX_FORMAT: 28f5. from *note GNU_FORMAT: 28f4.

也參考
......

*note zipfile: 117. 模組

     Documentation of the *note zipfile: 117. standard module.

*note Archiving operations: 11b0.

     Documentation of the higher-level archiving facilities provided by
     the standard *note shutil: b3. module.

GNU tar manual, Basic Tar Format(2)

     Documentation for tar archive files, including GNU tar extensions.

* Menu:

* TarFile 物件::
* TarInfo 物件::
* Extraction filters::
* Command-Line Interface: Command-Line Interface<2>.
* 範例: 範例<13>.
* Supported tar formats::
* Unicode issues::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/tarfile.py

   (2) https://www.gnu.org/software/tar/manual/html_node/Standard.html


File: python.info,  Node: TarFile 物件,  Next: TarInfo 物件,  Up: tarfile --- 讀取與寫入 tar 封存檔案

5.13.6.1 TarFile 物件
.....................

The *note TarFile: 290. object provides an interface to a tar archive.
A tar archive is a sequence of blocks.  An archive member (a stored
file) is made up of a header block followed by data blocks.  It is
possible to store a file in a tar archive several times.  Each archive
member is represented by a *note TarInfo: 11a8. object, see *note
TarInfo 物件: 28de. for details.

A *note TarFile: 290. object can be used as a context manager in a *note
with: 577. statement.  It will automatically be closed when the block is
completed.  Please note that in the event of an exception an archive
opened for writing will not be finalized; only the internally used file
object will be closed.  See the *note 範例: 28d4. section for a use
case.

在 3.2 版被加入: Added support for the context management protocol.

 -- 類別: tarfile.TarFile (name=None, mode='r', fileobj=None,
          format=DEFAULT_FORMAT, tarinfo=TarInfo, dereference=False,
          ignore_zeros=False, encoding=ENCODING,
          errors='surrogateescape', pax_headers=None, debug=0,
          errorlevel=1, stream=False)

     All following arguments are optional and can be accessed as
     instance attributes as well.

     'name' is the pathname of the archive.  'name' may be a *note
     path-like object: ac2.  It can be omitted if 'fileobj' is given.
     In this case, the file object's ‘name’ attribute is used if it
     exists.

     'mode' is either ‘'r'’ to read from an existing archive, ‘'a'’ to
     append data to an existing file, ‘'w'’ to create a new file
     overwriting an existing one, or ‘'x'’ to create a new file only if
     it does not already exist.

     If 'fileobj' is given, it is used for reading or writing data.  If
     it can be determined, 'mode' is overridden by 'fileobj"s mode.
     'fileobj' will be used from position 0.

          備註: 'fileobj' is not closed, when *note TarFile: 290. is
          closed.

     'format' controls the archive format for writing.  It must be one
     of the constants *note USTAR_FORMAT: 28f3, *note GNU_FORMAT: 28f4.
     or *note PAX_FORMAT: 28f5. that are defined at module level.  When
     reading, format will be automatically detected, even if different
     formats are present in a single archive.

     The 'tarinfo' argument can be used to replace the default *note
     TarInfo: 11a8. class with a different one.

     If 'dereference' is *note False: adb, add symbolic and hard links
     to the archive.  If it is *note True: bb4, add the content of the
     target files to the archive.  This has no effect on systems that do
     not support symbolic links.

     If 'ignore_zeros' is *note False: adb, treat an empty block as the
     end of the archive.  If it is *note True: bb4, skip empty (and
     invalid) blocks and try to get as many members as possible.  This
     is only useful for reading concatenated or damaged archives.

     'debug' can be set from ‘0’ (no debug messages) up to ‘3’ (all
     debug messages).  The messages are written to ‘sys.stderr’.

     'errorlevel' controls how extraction errors are handled, see *note
     the corresponding attribute: 28d8.

     The 'encoding' and 'errors' arguments define the character encoding
     to be used for reading or writing the archive and how conversion
     errors are going to be handled.  The default settings will work for
     most users.  See section *note Unicode issues: 28f8. for in-depth
     information.

     The 'pax_headers' argument is an optional dictionary of strings
     which will be added as a pax global header if 'format' is *note
     PAX_FORMAT: 28f5.

     If 'stream' is set to *note True: bb4. then while reading the
     archive info about files in the archive are not cached, saving
     memory.

     在 3.2 版的變更: Use ‘'surrogateescape'’ as the default for the
     'errors' argument.

     在 3.5 版的變更: The ‘'x'’ (exclusive creation) mode was added.

     在 3.6 版的變更: The 'name' parameter accepts a *note path-like
     object: ac2.

     在 3.13 版的變更: Add the 'stream' parameter.

 -- 方法: classmethod TarFile.open (...)

     Alternative constructor.  The *note tarfile.open(): e19. function
     is actually a shortcut to this classmethod.

 -- 方法: TarFile.getmember (name)

     Return a *note TarInfo: 11a8. object for member 'name'.  If 'name'
     can not be found in the archive, *note KeyError: 2fb. is raised.

          備註: If a member occurs more than once in the archive, its
          last occurrence is assumed to be the most up-to-date version.

 -- 方法: TarFile.getmembers ()

     Return the members of the archive as a list of *note TarInfo: 11a8.
     objects.  The list has the same order as the members in the
     archive.

 -- 方法: TarFile.getnames ()

     Return the members as a list of their names.  It has the same order
     as the list returned by *note getmembers(): e1d.

 -- 方法: TarFile.list (verbose=True, *, members=None)

     Print a table of contents to ‘sys.stdout’.  If 'verbose' is *note
     False: adb, only the names of the members are printed.  If it is
     *note True: bb4, output similar to that of ‘ls -l’ is produced.  If
     optional 'members' is given, it must be a subset of the list
     returned by *note getmembers(): e1d.

     在 3.5 版的變更: 新增 'members' 參數。

 -- 方法: TarFile.next ()

     Return the next member of the archive as a *note TarInfo: 11a8.
     object, when *note TarFile: 290. is opened for reading.  Return
     *note None: 61b. if there is no more available.

 -- 方法: TarFile.extractall (path='.', members=None, *,
          numeric_owner=False, filter=None)

     Extract all members from the archive to the current working
     directory or directory 'path'.  If optional 'members' is given, it
     must be a subset of the list returned by *note getmembers(): e1d.
     Directory information like owner, modification time and permissions
     are set after all members have been extracted.  This is done to
     work around two problems: A directory's modification time is reset
     each time a file is created in it.  And, if a directory's
     permissions do not allow writing, extracting files to it will fail.

     If 'numeric_owner' is *note True: bb4, the uid and gid numbers from
     the tarfile are used to set the owner/group for the extracted
     files.  Otherwise, the named values from the tarfile are used.

     The 'filter' argument specifies how ‘members’ are modified or
     rejected before extraction.  See *note Extraction filters: 413. for
     details.  It is recommended to set this explicitly depending on
     which 'tar' features you need to support.

          警告: Never extract archives from untrusted sources without
          prior inspection.  It is possible that files are created
          outside of 'path', e.g.  members that have absolute filenames
          starting with ‘"/"’ or filenames with two dots ‘".."’.

          Set ‘filter='data'’ to prevent the most dangerous security
          issues, and read the *note Extraction filters: 413. section
          for details.

     在 3.5 版的變更: 新增 'numeric_owner' 參數。

     在 3.6 版的變更: The 'path' parameter accepts a *note path-like
     object: ac2.

     在 3.12 版的變更: 新增 'filter' 參數。

 -- 方法: TarFile.extract (member, path='', set_attrs=True, *,
          numeric_owner=False, filter=None)

     Extract a member from the archive to the current working directory,
     using its full name.  Its file information is extracted as
     accurately as possible.  'member' may be a filename or a *note
     TarInfo: 11a8. object.  You can specify a different directory using
     'path'.  'path' may be a *note path-like object: ac2.  File
     attributes (owner, mtime, mode) are set unless 'set_attrs' is
     false.

     The 'numeric_owner' and 'filter' arguments are the same as for
     *note extractall(): e1a.

          備註: The *note extract(): e1b. method does not take care of
          several extraction issues.  In most cases you should consider
          using the *note extractall(): e1a. method.

          警告: 參閱 *note extractall(): e1a. 的警告。

          Set ‘filter='data'’ to prevent the most dangerous security
          issues, and read the *note Extraction filters: 413. section
          for details.

     在 3.2 版的變更: 增加 'set_attrs' 參數。

     在 3.5 版的變更: 新增 'numeric_owner' 參數。

     在 3.6 版的變更: The 'path' parameter accepts a *note path-like
     object: ac2.

     在 3.12 版的變更: 新增 'filter' 參數。

 -- 方法: TarFile.extractfile (member)

     Extract a member from the archive as a file object.  'member' may
     be a filename or a *note TarInfo: 11a8. object.  If 'member' is a
     regular file or a link, an *note io.BufferedReader: 11a6. object is
     returned.  For all other existing members, *note None: 61b. is
     returned.  If 'member' does not appear in the archive, *note
     KeyError: 2fb. is raised.

     在 3.3 版的變更: Return an *note io.BufferedReader: 11a6. object.

     在 3.13 版的變更: The returned *note io.BufferedReader: 11a6.
     object has the ‘mode’ attribute which is always equal to ‘'rb'’.

 -- 屬性: TarFile.errorlevel: *note int: 23c.

     If 'errorlevel' is ‘0’, errors are ignored when using *note
     TarFile.extract(): e1b. and *note TarFile.extractall(): e1a.
     Nevertheless, they appear as error messages in the debug output
     when 'debug' is greater than 0.  If ‘1’ (the default), all 'fatal'
     errors are raised as *note OSError: 350. or *note FilterError:
     28db. exceptions.  If ‘2’, all 'non-fatal' errors are raised as
     *note TarError: 28d5. exceptions as well.

     Some exceptions, e.g.  ones caused by wrong argument types or data
     corruption, are always raised.

     Custom *note extraction filters: 413. should raise *note
     FilterError: 28db. for 'fatal' errors and *note ExtractError: 28d7.
     for 'non-fatal' ones.

     Note that when an exception is raised, the archive may be partially
     extracted.  It is the user’s responsibility to clean up.

 -- 屬性: TarFile.extraction_filter

     在 3.12 版被加入.

     The *note extraction filter: 413. used as a default for the
     'filter' argument of *note extract(): e1b. and *note extractall():
     e1a.

     The attribute may be ‘None’ or a callable.  String names are not
     allowed for this attribute, unlike the 'filter' argument to *note
     extract(): e1b.

     If ‘extraction_filter’ is ‘None’ (the default), calling an
     extraction method without a 'filter' argument will raise a
     ‘DeprecationWarning’, and fall back to the *note fully_trusted:
     28fd. filter, whose dangerous behavior matches previous versions of
     Python.

     In Python 3.14+, leaving ‘extraction_filter=None’ will cause
     extraction methods to use the *note data: 15f9. filter by default.

     The attribute may be set on instances or overridden in subclasses.
     It also is possible to set it on the ‘TarFile’ class itself to set
     a global default, although, since it affects all uses of 'tarfile',
     it is best practice to only do so in top-level applications or
     *note site configuration: b5.  To set a global default this way, a
     filter function needs to be wrapped in *note staticmethod(): 358.
     to prevent injection of a ‘self’ argument.

 -- 方法: TarFile.add (name, arcname=None, recursive=True, *,
          filter=None)

     Add the file 'name' to the archive.  'name' may be any type of file
     (directory, fifo, symbolic link, etc.).  If given, 'arcname'
     specifies an alternative name for the file in the archive.
     Directories are added recursively by default.  This can be avoided
     by setting 'recursive' to *note False: adb.  Recursion adds entries
     in sorted order.  If 'filter' is given, it should be a function
     that takes a *note TarInfo: 11a8. object argument and returns the
     changed *note TarInfo: 11a8. object.  If it instead returns *note
     None: 61b. the *note TarInfo: 11a8. object will be excluded from
     the archive.  See *note 範例: 28d4. for an example.

     在 3.2 版的變更: 新增 'filter' 參數。

     在 3.7 版的變更: Recursion adds entries in sorted order.

 -- 方法: TarFile.addfile (tarinfo, fileobj=None)

     Add the *note TarInfo: 11a8. object 'tarinfo' to the archive.  If
     'tarinfo' represents a non zero-size regular file, the 'fileobj'
     argument should be a *note binary file: 1b8b, and ‘tarinfo.size’
     bytes are read from it and added to the archive.  You can create
     *note TarInfo: 11a8. objects directly, or by using *note
     gettarinfo(): 28fe.

     在 3.13 版的變更: 'fileobj' must be given for non-zero-sized
     regular files.

 -- 方法: TarFile.gettarinfo (name=None, arcname=None, fileobj=None)

     Create a *note TarInfo: 11a8. object from the result of *note
     os.stat(): 448. or equivalent on an existing file.  The file is
     either named by 'name', or specified as a *note file object: 115b.
     'fileobj' with a file descriptor.  'name' may be a *note path-like
     object: ac2.  If given, 'arcname' specifies an alternative name for
     the file in the archive, otherwise, the name is taken from
     'fileobj'’s *note name: 2865. attribute, or the 'name' argument.
     The name should be a text string.

     You can modify some of the *note TarInfo: 11a8.’s attributes before
     you add it using *note addfile(): 1524.  If the file object is not
     an ordinary file object positioned at the beginning of the file,
     attributes such as *note size: 28ff. may need modifying.  This is
     the case for objects such as *note GzipFile: 354.  The *note name:
     2900. may also be modified, in which case 'arcname' could be a
     dummy string.

     在 3.6 版的變更: The 'name' parameter accepts a *note path-like
     object: ac2.

 -- 方法: TarFile.close ()

     Close the *note TarFile: 290.  In write mode, two finishing zero
     blocks are appended to the archive.

 -- 屬性: TarFile.pax_headers: *note dict: 23b.

     A dictionary containing key-value pairs of pax global headers.


File: python.info,  Node: TarInfo 物件,  Next: Extraction filters,  Prev: TarFile 物件,  Up: tarfile --- 讀取與寫入 tar 封存檔案

5.13.6.2 TarInfo 物件
.....................

A *note TarInfo: 11a8. object represents one member in a *note TarFile:
290.  Aside from storing all required attributes of a file (like file
type, size, time, permissions, owner etc.), it provides some useful
methods to determine its type.  It does 'not' contain the file's data
itself.

*note TarInfo: 11a8. objects are returned by *note TarFile: 290.'s
methods *note getmember(): 1757, *note getmembers(): e1d. and *note
gettarinfo(): 28fe.

Modifying the objects returned by *note getmember(): 1757. or *note
getmembers(): e1d. will affect all subsequent operations on the archive.
For cases where this is unwanted, you can use *note copy.copy(): 1e. or
call the *note replace(): 2904. method to create a modified copy in one
step.

Several attributes can be set to ‘None’ to indicate that a piece of
metadata is unused or unknown.  Different *note TarInfo: 11a8. methods
handle ‘None’ differently:

   - The *note extract(): e1b. or *note extractall(): e1a. methods will
     ignore the corresponding metadata, leaving it set to a default.

   - *note addfile(): 1524. will fail.

   - *note list(): e1c. will print a placeholder string.

 -- 類別: tarfile.TarInfo (name='')

     Create a *note TarInfo: 11a8. object.

 -- 方法: classmethod TarInfo.frombuf (buf, encoding, errors)

     Create and return a *note TarInfo: 11a8. object from string buffer
     'buf'.

     Raises *note HeaderError: 28d9. if the buffer is invalid.

 -- 方法: classmethod TarInfo.fromtarfile (tarfile)

     Read the next member from the *note TarFile: 290. object 'tarfile'
     and return it as a *note TarInfo: 11a8. object.

 -- 方法: TarInfo.tobuf (format=DEFAULT_FORMAT, encoding=ENCODING,
          errors='surrogateescape')

     Create a string buffer from a *note TarInfo: 11a8. object.  For
     information on the arguments see the constructor of the *note
     TarFile: 290. class.

     在 3.2 版的變更: Use ‘'surrogateescape'’ as the default for the
     'errors' argument.

A ‘TarInfo’ object has the following public data attributes:

 -- 屬性: TarInfo.name: *note str: 3f2.

     Name of the archive member.

 -- 屬性: TarInfo.size: *note int: 23c.

     Size in bytes.

 -- 屬性: TarInfo.mtime: *note int: 23c. | *note float: 2c8.

     Time of last modification in seconds since the *note epoch: 2908,
     as in *note os.stat_result.st_mtime: 2909.

     在 3.12 版的變更: Can be set to ‘None’ for *note extract(): e1b.
     and *note extractall(): e1a, causing extraction to skip applying
     this attribute.

 -- 屬性: TarInfo.mode: *note int: 23c.

     Permission bits, as for *note os.chmod(): 200.

     在 3.12 版的變更: Can be set to ‘None’ for *note extract(): e1b.
     and *note extractall(): e1a, causing extraction to skip applying
     this attribute.

 -- 屬性: TarInfo.type

     File type.  'type' is usually one of these constants: *note
     REGTYPE: 28e5, *note AREGTYPE: 28e6, *note LNKTYPE: 28e8, *note
     SYMTYPE: 28e9, *note DIRTYPE: 28ec, *note FIFOTYPE: 28ed, *note
     CONTTYPE: 28ee, *note CHRTYPE: 28ea, *note BLKTYPE: 28eb, *note
     GNUTYPE_SPARSE: 28f1.  To determine the type of a *note TarInfo:
     11a8. object more conveniently, use the ‘is*()’ methods below.

 -- 屬性: TarInfo.linkname: *note str: 3f2.

     Name of the target file name, which is only present in *note
     TarInfo: 11a8. objects of type *note LNKTYPE: 28e8. and *note
     SYMTYPE: 28e9.

     For symbolic links (‘SYMTYPE’), the 'linkname' is relative to the
     directory that contains the link.  For hard links (‘LNKTYPE’), the
     'linkname' is relative to the root of the archive.

 -- 屬性: TarInfo.uid: *note int: 23c.

     User ID of the user who originally stored this member.

     在 3.12 版的變更: Can be set to ‘None’ for *note extract(): e1b.
     and *note extractall(): e1a, causing extraction to skip applying
     this attribute.

 -- 屬性: TarInfo.gid: *note int: 23c.

     Group ID of the user who originally stored this member.

     在 3.12 版的變更: Can be set to ‘None’ for *note extract(): e1b.
     and *note extractall(): e1a, causing extraction to skip applying
     this attribute.

 -- 屬性: TarInfo.uname: *note str: 3f2.

     User name.

     在 3.12 版的變更: Can be set to ‘None’ for *note extract(): e1b.
     and *note extractall(): e1a, causing extraction to skip applying
     this attribute.

 -- 屬性: TarInfo.gname: *note str: 3f2.

     Group name.

     在 3.12 版的變更: Can be set to ‘None’ for *note extract(): e1b.
     and *note extractall(): e1a, causing extraction to skip applying
     this attribute.

 -- 屬性: TarInfo.chksum: *note int: 23c.

     Header checksum.

 -- 屬性: TarInfo.devmajor: *note int: 23c.

     Device major number.

 -- 屬性: TarInfo.devminor: *note int: 23c.

     Device minor number.

 -- 屬性: TarInfo.offset: *note int: 23c.

     The tar header starts here.

 -- 屬性: TarInfo.offset_data: *note int: 23c.

     The file's data starts here.

 -- 屬性: TarInfo.sparse

     Sparse member information.

 -- 屬性: TarInfo.pax_headers: *note dict: 23b.

     A dictionary containing key-value pairs of an associated pax
     extended header.

 -- 方法: TarInfo.replace (name=..., mtime=..., mode=..., linkname=...,
          uid=..., gid=..., uname=..., gname=..., deep=True)

     在 3.12 版被加入.

     Return a 'new' copy of the ‘TarInfo’ object with the given
     attributes changed.  For example, to return a ‘TarInfo’ with the
     group name set to ‘'staff'’, use:

          new_tarinfo = old_tarinfo.replace(gname='staff')

     By default, a deep copy is made.  If 'deep' is false, the copy is
     shallow, i.e.  ‘pax_headers’ and any custom attributes are shared
     with the original ‘TarInfo’ object.

A *note TarInfo: 11a8. object also provides some convenient query
methods:

 -- 方法: TarInfo.isfile ()

     Return *note True: bb4. if the *note TarInfo: 11a8. object is a
     regular file.

 -- 方法: TarInfo.isreg ()

     Same as *note isfile(): 2917.

 -- 方法: TarInfo.isdir ()

     Return *note True: bb4. if it is a directory.

 -- 方法: TarInfo.issym ()

     Return *note True: bb4. if it is a symbolic link.

 -- 方法: TarInfo.islnk ()

     Return *note True: bb4. if it is a hard link.

 -- 方法: TarInfo.ischr ()

     Return *note True: bb4. if it is a character device.

 -- 方法: TarInfo.isblk ()

     Return *note True: bb4. if it is a block device.

 -- 方法: TarInfo.isfifo ()

     Return *note True: bb4. if it is a FIFO.

 -- 方法: TarInfo.isdev ()

     Return *note True: bb4. if it is one of character device, block
     device or FIFO.


File: python.info,  Node: Extraction filters,  Next: Command-Line Interface<2>,  Prev: TarInfo 物件,  Up: tarfile --- 讀取與寫入 tar 封存檔案

5.13.6.3 Extraction filters
...........................

在 3.12 版被加入.

The 'tar' format is designed to capture all details of a UNIX-like
filesystem, which makes it very powerful.  Unfortunately, the features
make it easy to create tar files that have unintended - and possibly
malicious - effects when extracted.  For example, extracting a tar file
can overwrite arbitrary files in various ways (e.g.  by using absolute
paths, ‘..’ path components, or symlinks that affect later members).

In most cases, the full functionality is not needed.  Therefore,
'tarfile' supports extraction filters: a mechanism to limit
functionality, and thus mitigate some of the security issues.

也參考
......

PEP 706(1)

     Contains further motivation and rationale behind the design.

The 'filter' argument to *note TarFile.extract(): e1b. or *note
extractall(): e1a. can be:

   * the string ‘'fully_trusted'’: Honor all metadata as specified in
     the archive.  Should be used if the user trusts the archive
     completely, or implements their own complex verification.

   * the string ‘'tar'’: Honor most 'tar'-specific features (i.e.
     features of UNIX-like filesystems), but block features that are
     very likely to be surprising or malicious.  See *note tar_filter():
     2921. for details.

   * the string ‘'data'’: Ignore or block most features specific to
     UNIX-like filesystems.  Intended for extracting cross-platform data
     archives.  See *note data_filter(): 15f9. for details.

   * ‘None’ (default): Use *note TarFile.extraction_filter: 28fc.

     If that is also ‘None’ (the default), raise a ‘DeprecationWarning’,
     and fall back to the ‘'fully_trusted'’ filter, whose dangerous
     behavior matches previous versions of Python.

     In Python 3.14, the ‘'data'’ filter will become the default
     instead.  It's possible to switch earlier; see *note
     TarFile.extraction_filter: 28fc.

   * A callable which will be called for each extracted member with a
     *note TarInfo: 28de. describing the member and the destination path
     to where the archive is extracted (i.e.  the same path is used for
     all members):

          filter(member: TarInfo, path: str, /) -> TarInfo | None

     The callable is called just before each member is extracted, so it
     can take the current state of the disk into account.  It can:

        - return a *note TarInfo: 11a8. object which will be used
          instead of the metadata in the archive, or

        - return ‘None’, in which case the member will be skipped, or

        - raise an exception to abort the operation or skip the member,
          depending on *note errorlevel: 28d8.  Note that when
          extraction is aborted, *note extractall(): e1a. may leave the
          archive partially extracted.  It does not attempt to clean up.

* Menu:

* Default named filters::
* Filter errors::
* Hints for further verification::
* Supporting older Python versions::
* Stateful extraction filter example::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0706/


File: python.info,  Node: Default named filters,  Next: Filter errors,  Up: Extraction filters

5.13.6.4 Default named filters
..............................

The pre-defined, named filters are available as functions, so they can
be reused in custom filters:

 -- 函式: tarfile.fully_trusted_filter (member, path)

     Return 'member' unchanged.

     This implements the ‘'fully_trusted'’ filter.

 -- 函式: tarfile.tar_filter (member, path)

     Implements the ‘'tar'’ filter.

        - Strip leading slashes (‘/’ and *note os.sep: 610.) from
          filenames.

        - *note Refuse: 28dc. to extract files with absolute paths (in
          case the name is absolute even after stripping slashes, e.g.
          ‘C:/foo’ on Windows).  This raises *note AbsolutePathError:
          28df.

        - *note Refuse: 28dc. to extract files whose absolute path
          (after following symlinks) would end up outside the
          destination.  This raises *note OutsideDestinationError: 28e0.

        - Clear high mode bits (setuid, setgid, sticky) and group/other
          write bits (*note S_IWGRP: 26e8. | *note S_IWOTH: 26eb.).

     Return the modified ‘TarInfo’ member.

 -- 函式: tarfile.data_filter (member, path)

     Implements the ‘'data'’ filter.  In addition to what ‘tar_filter’
     does:

        - *note Refuse: 28dc. to extract links (hard or soft) that link
          to absolute paths, or ones that link outside the destination.

          This raises *note AbsoluteLinkError: 28e2. or *note
          LinkOutsideDestinationError: 28e3.

          Note that such files are refused even on platforms that do not
          support symbolic links.

        - *note Refuse: 28dc. to extract device files (including pipes).
          This raises *note SpecialFileError: 28e1.

        - For regular files, including hard links:

             - Set the owner read and write permissions (*note S_IRUSR:
               26e3. | *note S_IWUSR: 26e4.).

             - Remove the group & other executable permission (*note
               S_IXGRP: 26df. | *note S_IXOTH: 26ec.) if the owner
               doesn’t have it (*note S_IXUSR: 26e5.).

        - For other files (directories), set ‘mode’ to ‘None’, so that
          extraction methods skip applying permission bits.

        - Set user and group info (‘uid’, ‘gid’, ‘uname’, ‘gname’) to
          ‘None’, so that extraction methods skip setting it.

     Return the modified ‘TarInfo’ member.


File: python.info,  Node: Filter errors,  Next: Hints for further verification,  Prev: Default named filters,  Up: Extraction filters

5.13.6.5 Filter errors
......................

When a filter refuses to extract a file, it will raise an appropriate
exception, a subclass of *note FilterError: 28db.  This will abort the
extraction if *note TarFile.errorlevel: 28d8. is 1 or more.  With
‘errorlevel=0’ the error will be logged and the member will be skipped,
but extraction will continue.


File: python.info,  Node: Hints for further verification,  Next: Supporting older Python versions,  Prev: Filter errors,  Up: Extraction filters

5.13.6.6 Hints for further verification
.......................................

Even with ‘filter='data'’, 'tarfile' is not suited for extracting
untrusted files without prior inspection.  Among other issues, the
pre-defined filters do not prevent denial-of-service attacks.  Users
should do additional checks.

Here is an incomplete list of things to consider:

   * Extract to a *note new temporary directory: 204. to prevent e.g.
     exploiting pre-existing links, and to make it easier to clean up
     after a failed extraction.

   * When working with untrusted data, use external (e.g.  OS-level)
     limits on disk, memory and CPU usage.

   * Check filenames against an allow-list of characters (to filter out
     control characters, confusables, foreign path separators, etc.).

   * Check that filenames have expected extensions (discouraging files
     that execute when you “click on them”, or extension-less files like
     Windows special device names).

   * Limit the number of extracted files, total size of extracted data,
     filename length (including symlink length), and size of individual
     files.

   * Check for files that would be shadowed on case-insensitive
     filesystems.

Also note that:

   * Tar files may contain multiple versions of the same file.  Later
     ones are expected to overwrite any earlier ones.  This feature is
     crucial to allow updating tape archives, but can be abused
     maliciously.

   * 'tarfile' does not protect against issues with “live” data, e.g.
     an attacker tinkering with the destination (or source) directory
     while extraction (or archiving) is in progress.


File: python.info,  Node: Supporting older Python versions,  Next: Stateful extraction filter example,  Prev: Hints for further verification,  Up: Extraction filters

5.13.6.7 Supporting older Python versions
.........................................

Extraction filters were added to Python 3.12, but may be backported to
older versions as security updates.  To check whether the feature is
available, use e.g.  ‘hasattr(tarfile, 'data_filter')’ rather than
checking the Python version.

The following examples show how to support Python versions with and
without the feature.  Note that setting ‘extraction_filter’ will affect
any subsequent operations.

   * Fully trusted archive:

          my_tarfile.extraction_filter = (lambda member, path: member)
          my_tarfile.extractall()

   * Use the ‘'data'’ filter if available, but revert to Python 3.11
     behavior (‘'fully_trusted'’) if this feature is not available:

          my_tarfile.extraction_filter = getattr(tarfile, 'data_filter',
                                                 (lambda member, path: member))
          my_tarfile.extractall()

   * Use the ‘'data'’ filter; 'fail' if it is not available:

          my_tarfile.extractall(filter=tarfile.data_filter)

     或：

          my_tarfile.extraction_filter = tarfile.data_filter
          my_tarfile.extractall()

   * Use the ‘'data'’ filter; 'warn' if it is not available:

          if hasattr(tarfile, 'data_filter'):
              my_tarfile.extractall(filter='data')
          else:
              # remove this when no longer needed
              warn_the_user('Extracting may be unsafe; consider updating Python')
              my_tarfile.extractall()


File: python.info,  Node: Stateful extraction filter example,  Prev: Supporting older Python versions,  Up: Extraction filters

5.13.6.8 Stateful extraction filter example
...........................................

While 'tarfile"s extraction methods take a simple 'filter' callable,
custom filters may be more complex objects with an internal state.  It
may be useful to write these as context managers, to be used like this:

     with StatefulFilter() as filter_func:
         tar.extractall(path, filter=filter_func)

Such a filter can be written as, for example:

     class StatefulFilter:
         def __init__(self):
             self.file_count = 0

         def __enter__(self):
             return self

         def __call__(self, member, path):
             self.file_count += 1
             return member

         def __exit__(self, *exc_info):
             print(f'{self.file_count} files extracted')


File: python.info,  Node: Command-Line Interface<2>,  Next: 範例<13>,  Prev: Extraction filters,  Up: tarfile --- 讀取與寫入 tar 封存檔案

5.13.6.9 Command-Line Interface
...............................

在 3.4 版被加入.

The *note tarfile: c8. module provides a simple command-line interface
to interact with tar archives.

If you want to create a new tar archive, specify its name after the
*note -c: 2928. option and then list the filename(s) that should be
included:

     $ python -m tarfile -c monty.tar  spam.txt eggs.txt

Passing a directory is also acceptable:

     $ python -m tarfile -c monty.tar life-of-brian_1979/

If you want to extract a tar archive into the current directory, use the
*note -e: 2929. option:

     $ python -m tarfile -e monty.tar

You can also extract a tar archive into a different directory by passing
the directory's name:

     $ python -m tarfile -e monty.tar  other-dir/

For a list of the files in a tar archive, use the *note -l: 292a.
option:

     $ python -m tarfile -l monty.tar

* Menu:

* 命令列選項: 命令列選項<2>.


File: python.info,  Node: 命令列選項<2>,  Up: Command-Line Interface<2>

5.13.6.10 命令列選項
....................

 -- Option: -l <tarfile>
 -- Option: --list <tarfile>

     List files in a tarfile.

 -- Option: -c <tarfile> <source1> ... <sourceN>
 -- Option: --create <tarfile> <source1> ... <sourceN>

     Create tarfile from source files.

 -- Option: -e <tarfile> [<output_dir>]
 -- Option: --extract <tarfile> [<output_dir>]

     Extract tarfile into the current directory if 'output_dir' is not
     specified.

 -- Option: -t <tarfile>
 -- Option: --test <tarfile>

     Test whether the tarfile is valid or not.

 -- Option: -v, --verbose

     Verbose output.

 -- Option: --filter <filtername>

     Specifies the 'filter' for ‘--extract’.  See *note Extraction
     filters: 413. for details.  Only string names are accepted (that
     is, ‘fully_trusted’, ‘tar’, and ‘data’).


File: python.info,  Node: 範例<13>,  Next: Supported tar formats,  Prev: Command-Line Interface<2>,  Up: tarfile --- 讀取與寫入 tar 封存檔案

5.13.6.11 範例
..............

How to extract an entire tar archive to the current working directory:

     import tarfile
     tar = tarfile.open("sample.tar.gz")
     tar.extractall(filter='data')
     tar.close()

How to extract a subset of a tar archive with *note
TarFile.extractall(): e1a. using a generator function instead of a list:

     import os
     import tarfile

     def py_files(members):
         for tarinfo in members:
             if os.path.splitext(tarinfo.name)[1] == ".py":
                 yield tarinfo

     tar = tarfile.open("sample.tar.gz")
     tar.extractall(members=py_files(tar))
     tar.close()

How to create an uncompressed tar archive from a list of filenames:

     import tarfile
     tar = tarfile.open("sample.tar", "w")
     for name in ["foo", "bar", "quux"]:
         tar.add(name)
     tar.close()

The same example using the *note with: 577. statement:

     import tarfile
     with tarfile.open("sample.tar", "w") as tar:
         for name in ["foo", "bar", "quux"]:
             tar.add(name)

How to read a gzip compressed tar archive and display some member
information:

     import tarfile
     tar = tarfile.open("sample.tar.gz", "r:gz")
     for tarinfo in tar:
         print(tarinfo.name, "is", tarinfo.size, "bytes in size and is ", end="")
         if tarinfo.isreg():
             print("a regular file.")
         elif tarinfo.isdir():
             print("a directory.")
         else:
             print("something else.")
     tar.close()

How to create an archive and reset the user information using the
'filter' parameter in *note TarFile.add(): b9a.:

     import tarfile
     def reset(tarinfo):
         tarinfo.uid = tarinfo.gid = 0
         tarinfo.uname = tarinfo.gname = "root"
         return tarinfo
     tar = tarfile.open("sample.tar.gz", "w:gz")
     tar.add("foo", filter=reset)
     tar.close()


File: python.info,  Node: Supported tar formats,  Next: Unicode issues,  Prev: 範例<13>,  Up: tarfile --- 讀取與寫入 tar 封存檔案

5.13.6.12 Supported tar formats
...............................

There are three tar formats that can be created with the *note tarfile:
c8. module:

   * The POSIX.1-1988 ustar format (*note USTAR_FORMAT: 28f3.).  It
     supports filenames up to a length of at best 256 characters and
     linknames up to 100 characters.  The maximum file size is 8 GiB.
     This is an old and limited but widely supported format.

   * The GNU tar format (*note GNU_FORMAT: 28f4.).  It supports long
     filenames and linknames, files bigger than 8 GiB and sparse files.
     It is the de facto standard on GNU/Linux systems.  *note tarfile:
     c8. fully supports the GNU tar extensions for long names, sparse
     file support is read-only.

   * The POSIX.1-2001 pax format (*note PAX_FORMAT: 28f5.).  It is the
     most flexible format with virtually no limits.  It supports long
     filenames and linknames, large files and stores pathnames in a
     portable way.  Modern tar implementations, including GNU tar,
     bsdtar/libarchive and star, fully support extended 'pax' features;
     some old or unmaintained libraries may not, but should treat 'pax'
     archives as if they were in the universally supported 'ustar'
     format.  It is the current default format for new archives.

     It extends the existing 'ustar' format with extra headers for
     information that cannot be stored otherwise.  There are two
     flavours of pax headers: Extended headers only affect the
     subsequent file header, global headers are valid for the complete
     archive and affect all following files.  All the data in a pax
     header is encoded in 'UTF-8' for portability reasons.

There are some more variants of the tar format which can be read, but
not created:

   * The ancient V7 format.  This is the first tar format from Unix
     Seventh Edition, storing only regular files and directories.  Names
     must not be longer than 100 characters, there is no user/group name
     information.  Some archives have miscalculated header checksums in
     case of fields with non-ASCII characters.

   * The SunOS tar extended format.  This format is a variant of the
     POSIX.1-2001 pax format, but is not compatible.


File: python.info,  Node: Unicode issues,  Prev: Supported tar formats,  Up: tarfile --- 讀取與寫入 tar 封存檔案

5.13.6.13 Unicode issues
........................

The tar format was originally conceived to make backups on tape drives
with the main focus on preserving file system information.  Nowadays tar
archives are commonly used for file distribution and exchanging archives
over networks.  One problem of the original format (which is the basis
of all other formats) is that there is no concept of supporting
different character encodings.  For example, an ordinary tar archive
created on a 'UTF-8' system cannot be read correctly on a 'Latin-1'
system if it contains non-'ASCII' characters.  Textual metadata (like
filenames, linknames, user/group names) will appear damaged.
Unfortunately, there is no way to autodetect the encoding of an archive.
The pax format was designed to solve this problem.  It stores non-ASCII
metadata using the universal character encoding 'UTF-8'.

The details of character conversion in *note tarfile: c8. are controlled
by the 'encoding' and 'errors' keyword arguments of the *note TarFile:
290. class.

'encoding' defines the character encoding to use for the metadata in the
archive.  The default value is *note sys.getfilesystemencoding(): c00.
or ‘'ascii'’ as a fallback.  Depending on whether the archive is read or
written, the metadata must be either decoded or encoded.  If 'encoding'
is not set appropriately, this conversion may fail.

The 'errors' argument defines how characters are treated that cannot be
converted.  Possible values are listed in section *note Error Handlers:
16eb.  The default scheme is ‘'surrogateescape'’ which Python also uses
for its file system calls, see *note File Names, Command Line Arguments,
and Environment Variables: 2937.

For *note PAX_FORMAT: 28f5. archives (the default), 'encoding' is
generally not needed because all the metadata is stored using 'UTF-8'.
'encoding' is only used in the rare cases when binary pax headers are
decoded or when strings with surrogate characters are stored.


File: python.info,  Node: 檔案格式,  Next: 加密服務,  Prev: 資料壓縮與保存,  Up: Python 標準函式庫 Standard Library

5.14 檔案格式
=============

The modules described in this chapter parse various miscellaneous file
formats that aren't markup languages and are not related to e-mail.

* Menu:

* csv: csv --- CSV 檔案讀取及寫入. CSV 檔案讀取及寫入
* configparser: configparser --- 設定檔剖析器. 設定檔剖析器
* tomllib: tomllib --- 剖析 TOML 檔案. 剖析 TOML 檔案
* netrc: netrc --- netrc 檔案處理. netrc 檔案處理
* plistlib: plistlib --- 產生和剖析 Apple plist 檔案. 產生和剖析 Apple .plist 檔案


File: python.info,  Node: csv --- CSV 檔案讀取及寫入,  Next: configparser --- 設定檔剖析器,  Up: 檔案格式

5.14.1 ‘csv’ -- CSV 檔案讀取及寫入
----------------------------------

'原始碼：'Lib/csv.py(1)

__________________________________________________________________

所謂的 CSV (Comma Separated Values) 檔案格式是試算表及資料庫中最常見的匯
入、匯出檔案格式。在嘗試以 RFC 4180(2) 中的標準化方式來描述格式之前，CSV
格式已經使用了許多年。由於缺少一個完善定義的標準，意味著各個不同的應用程
式會在資料產生及銷毀時有微妙的差別。這些不同之處使得從不同資料來源處理
CSV 檔案時會非常擾人。儘管如此，雖然分隔符號和引號字元有所不同，整體的格
式非常相似，可以寫個單一模組來高效率的操作這樣的資料，讓程式設計師可以隱
藏讀取及寫入資料的細節。

*note csv: 21. 模組實作透過 class 去讀取、寫入 CSV 格式的表格資料。它讓
程式設計師可以說出：「以 Excel 為首選並寫入該種格式的資料」或是「從
Excel 產生的檔案來讀取資料」，且無需知道這是 Excel 所使用的 CSV 格式等精
確的細節。程式設計師也可以描述其他應用程式所理解的 CSV 格式或他們自行定
義具有特殊意義的 CSV 格式。

*note csv: 21. 模組的 *note reader: 42d. 及 *note writer: 42e. 物件可以
讀取及寫入序列。程式設計師也可以透過 *note DictReader: 989. 及 *note
DictWriter: 1196. class（類別）使用 dictionary （字典）讀取及寫入資料。

也參考
......

PEP 305(3) - CSV 檔案 API

     Python Enhancement Proposal (PEP) 所提出的 Python 附加功能。

* Menu:

* 模組內容: 模組內容<3>.
* Dialect 與格式參數::
* 讀取器物件::
* 寫入器物件::
* 範例: 範例<14>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/csv.py

   (2) https://datatracker.ietf.org/doc/html/rfc4180.html

   (3) https://peps.python.org/pep-0305/


File: python.info,  Node: 模組內容<3>,  Next: Dialect 與格式參數,  Up: csv --- CSV 檔案讀取及寫入

5.14.1.1 模組內容
.................

*note csv: 21. 模組定義了以下函式：

 -- 函式: csv.reader (csvfile, dialect='excel', **fmtparams)

     回傳一個*note 讀取器物件 (reader object): 293f. 並處理在指定的
     'csvfile' 中的每一行，csvfile 必須是字串的可疊代物件 (iterable of
     strings)，其中每個字串都要是讀取器所定義的 csv 格式，csvfile 通常是
     個類檔案物件或者 list。如果 'csvfile' 是個檔案物件，則需開啟時使用
     ‘newline=''’。 (1) 'dialect' 為一個可選填的參數，可以用為特定的 CSV
     dialect（方言） 定義一組參數。它可能為 *note Dialect: 1571. 的一個
     子類別 (subclass) 的實例或是由 *note list_dialects(): 170e. 函式回
     傳的多個字串中的其中之一。另一個可選填的關鍵字引數 'fmtparams' 可以
     在這個 dialect 中覆寫 (override) 個別的格式化參數 (formatting
     parameter)。關於 dialect 及格式化參數的完整說明，請見段落 *note
     Dialect 與格式參數: 2940.。

     從 CSV 檔案讀取的每一列會回傳為一個字串列表。除非格式選項
     ‘QUOTE_NONNUMERIC’ 有被指定（在這個情況之下，沒有引號的欄位都會被轉
     換成浮點數），否則不會進行自動資料型別轉換。

     一個簡短的用法範例：

          >>> import csv
          >>> with open('eggs.csv', newline='') as csvfile:
          ...     spamreader = csv.reader(csvfile, delimiter=' ', quotechar='|')
          ...     for row in spamreader:
          ...         print(', '.join(row))
          Spam, Spam, Spam, Spam, Spam, Baked Beans
          Spam, Lovely Spam, Wonderful Spam

 -- 函式: csv.writer (csvfile, dialect='excel', **fmtparams)

     回傳一個寫入器物件 (writer object)，其負責在給定的類檔案物件
     (file-like object) 上將使用者的資料轉換為分隔字串 (delimited
     string)。'csvfile' 可以為具有 *note write(): 1b78. method 的任何物
     件。若 'csvfile' 為一個檔案物件，它應該使用 ‘newline=''’ 開啟 (2) 。
     'dialect' 為一個可選填的參數，可以用為特定的 CSV dialect 定義一組參
     數。它可能為 *note Dialect: 1571. 的一個子類別的實例或是由 *note
     list_dialects(): 170e. 函式回傳的多個字串中的其中之一。另一個可選填
     的關鍵字引數 'fmtparams' 可以在這個 dialect 中覆寫個別的格式化參數
     。關於 dialect 及格式化參數的完整說明，請見段落 *note Dialect
     與格式參數: 2940.。為了更容易與有實作 DB API 的模組互相接合，*note
     None: 61b. 值會被寫成空字串。雖然這不是一個可逆的變換，這使得dump （
     傾印） SQL NULL 資料值到 CSV 檔案上就無需讓 ‘cursor.fetch*’ 呼叫回
     傳的資料進行預處理 (preprocessing)。其餘非字串的資料則會在寫入之前
     用 *note str(): 3f2. 函式進行字串化 (stringify)。

     一個簡短的用法範例：

          import csv
          with open('eggs.csv', 'w', newline='') as csvfile:
              spamwriter = csv.writer(csvfile, delimiter=' ',
                                      quotechar='|', quoting=csv.QUOTE_MINIMAL)
              spamwriter.writerow(['Spam'] * 5 + ['Baked Beans'])
              spamwriter.writerow(['Spam', 'Lovely Spam', 'Wonderful Spam'])

 -- 函式: csv.register_dialect (name[, dialect[, **fmtparams]])

     將 'dialect' 與 'name' 進行關聯 (associate)。'name' 必須為字串。這
     個 dialect 可以透過傳遞 *note Dialect: 1571. 的子類別進行指定；或是
     關鍵字引數 'fmtparams'；或是以上兩者皆是，並透過關鍵字引數來覆寫
     dialect 的參數。關於 dialect 及格式化參數的完整說明，請見段落 *note
     Dialect 與格式參數: 2940.。

 -- 函式: csv.unregister_dialect (name)

     從 dialect 註冊表 (registry) 中，刪除與 'name' 關聯的 dialect。若
     'name' 如果不是註冊的 dialect 名稱，則會產生一個 *note Error:
     2942.。

 -- 函式: csv.get_dialect (name)

     回傳一個與 'name' 關聯的 dialect。若 'name' 如果不是註冊的 dialect
     名稱，則會產生一個 *note Error: 2942.。這個函式會回傳一個 immutable
     （不可變物件） *note Dialect: 1571.。

 -- 函式: csv.list_dialects ()

     回傳所有已註冊的 dialect 名稱。

 -- 函式: csv.field_size_limit ([new_limit])

     回傳當前的剖析器 (parser) 允許的最大字串大小。如果 'new_limit' 被給
     定，則會變成新的最大字串大小。

*note csv: 21. 模組定義了下列的類別：

 -- 類別: csv.DictReader (f, fieldnames=None, restkey=None,
          restval=None, dialect='excel', *args, **kwds)

     建立一個物件，其運作上就像一般的讀取器，但可以將每一列資訊 map （對
     映） 到 *note dict: 23b. 中，可以透過選填的參數 'fieldnames' 設定
     key。

     參數 'fieldnames' 是一個 *note sequence: 499.。如果 'fieldnames' 被
     省略了，檔案 'f' 中第一列的值會被當作欄位標題，且於結果中會被省略。
     如果 'fieldname' 有提供，它們就會被使用，且第一列會被包含在結果中。
     不管欄位標題是如何決定的，dictionary 都會保留原始的排序。

     如果一列資料中的欄位比欄位標題還多，其餘的資料及以 'restkey' （預設
     為 ‘None’）特指的欄位標題會放入列表當中並儲存。如果一個非空的
     (non-blank) 列中的欄位比欄位標題還少，缺少的值則會填入 'restval' （
     預設為 ‘None’）的值。

     所有其他選填的引數或關鍵字引數皆會傳遞至下層的 *note reader: 42d. 實
     例。

     如果傳遞至 'fieldnames' 的引數是個疊代器，則會被迫成為一個 *note
     list: 5b6.。

     在 3.6 版的變更: 回傳的列已成為型別 ‘OrderedDict’。

     在 3.8 版的變更: 回傳的列已成為型別 *note dict: 23b.。

     一個簡短的用法範例：

          >>> import csv
          >>> with open('names.csv', newline='') as csvfile:
          ...     reader = csv.DictReader(csvfile)
          ...     for row in reader:
          ...         print(row['first_name'], row['last_name'])
          ...
          Eric Idle
          John Cleese

          >>> print(row)
          {'first_name': 'John', 'last_name': 'Cleese'}

 -- 類別: csv.DictWriter (f, fieldnames, restval='',
          extrasaction='raise', dialect='excel', *args, **kwds)

     建立一個物件，其運作上就像一般的寫入器，但可以將 dictionary map 到
     輸出的列上。參數 'fieldnames' 是一個鍵值的 *note sequence: 17. 且可
     以辨識 dictionary 中傳遞至 *note writerow(): d90. method 寫入至檔案
     'f' 中的值。如果 dictionary 中缺少了 'fieldnames' 的鍵值，則會寫入
     選填的參數 'restval' 的值。如果傳遞至 *note writerow(): d90. method
     的 dictionary 包含了一個 'fieldnames' 中不存在的鍵值，選填的參數
     'extrasaction' 可以指出該執行的動作。如果它被設定為 ‘'raise'’，預設
     會觸發 *note ValueError: 1e7.。如果它被設定為 ‘'ignore'’，
     dictionary 中額外的值會被忽略。其他選填的引數或關鍵字引數皆會傳遞至
     下層的 *note writer: 42e. 實例。

     請記得這不像類別 *note DictReader: 989.，在類別 *note DictWriter:
     1196. 中，參數 'fieldnames' 並不是選填的。

     如果傳遞至 'fieldnames' 的引數是個疊代器，則會被迫成為一個 *note
     list: 5b6.。

     一個簡短的用法範例：

          import csv

          with open('names.csv', 'w', newline='') as csvfile:
              fieldnames = ['first_name', 'last_name']
              writer = csv.DictWriter(csvfile, fieldnames=fieldnames)

              writer.writeheader()
              writer.writerow({'first_name': 'Baked', 'last_name': 'Beans'})
              writer.writerow({'first_name': 'Lovely', 'last_name': 'Spam'})
              writer.writerow({'first_name': 'Wonderful', 'last_name': 'Spam'})

 -- 類別: csv.Dialect

     類別 *note Dialect: 1571. 是一個容器類別，其屬性 (attribute) 包含如
     何處理雙引號、空白、分隔符號等資訊。由於缺少一個嚴謹的 CSV 技術規範
     ，不同的應用程式會產出有巧妙不同的 CSV 資料。*note Dialect: 1571. 實
     例定義了 *note reader: 42d. 以及 *note writer: 42e. 的實例該如何表
     示。

     所有可用的 *note Dialect: 1571. 名稱會透過 *note list_dialects():
     170e. 回傳，且它們可以透過特定 *note reader: 42d. 及 *note writer:
     42e. 類別的初始器 (initializer, ‘__init__’) 函式進行註冊，就像這樣
     ：

          import csv

          with open('students.csv', 'w', newline='') as csvfile:
              writer = csv.writer(csvfile, dialect='unix')

 -- 類別: csv.excel

     類別 *note excel: 2943. 定義了透過 Excel 產生的 CSV 檔案的慣用屬性
     。它被註冊的 dialect 名稱為 ‘'excel'’。

 -- 類別: csv.excel_tab

     類別 *note excel_tab: 2944. 定義了透過 Excel 產生並以 Tab 作為分隔
     的 CSV 檔案的慣用屬性。它被註冊的 dialect 名稱為 ‘'excel-tab'’。

 -- 類別: csv.unix_dialect

     類別 *note unix_dialect: 1195. 定義了透過 UNIX 系統產生的 CSV 檔案
     的慣用屬性，換句話說，使用 ‘'\n'’ 作為換行符號且所有欄位都被引號包
     覆起來。它被註冊的 dialect 名稱為 ‘'unix'’。

     在 3.2 版被加入.

 -- 類別: csv.Sniffer

     類別 *note Sniffer: 2945. 被用來推斷 CSV 檔案的格式。

     類別 *note Sniffer: 2945. 提供了兩個 method：

      -- 方法: sniff (sample, delimiters=None)

          分析給定的 'sample' 且回傳一個 *note Dialect: 1571. 子類別，反
          應出找到的格式參數。如果給定選填的參數 'delimiters'，它會被解
          釋為一個字串且含有可能、有效的分隔字元。

      -- 方法: has_header (sample)

          如果第一列的文字顯示將作為一系列的欄位標題，會分析 sample 文字
          （假定他是 CSV 格式）並回傳 *note True: bb4.。檢查每一欄時，會
          考慮是否滿足兩個關鍵標準其中之一，判斷 sample 是否包含標題：

             - 第二列至第 n 列包含數字

             - 第二列到第 n 列包含的字串中至少有一個值的長度與該行的假定
               標題的長度不同。

          對第一列之後的二十個列進行採樣；如果超過一半的行及列滿足條件，
          則返回 *note True: bb4.。

          備註: 此方法是一個粗略的啟發，可能會產生偽陽性及偽陰性 (false
          positives and negatives)。

一個 *note Sniffer: 2945. 的使用範例：

     with open('example.csv', newline='') as csvfile:
         dialect = csv.Sniffer().sniff(csvfile.read(1024))
         csvfile.seek(0)
         reader = csv.reader(csvfile, dialect)
         # ... 在這邊處理 CSV 檔案 ...
*note csv: 21. 模組定義了以下常數：

 -- 資料: csv.QUOTE_ALL

     引導 *note writer: 42e. 物件引用所有欄位。

 -- 資料: csv.QUOTE_MINIMAL

     引導 *note writer: 42e. 物件只引用包含特殊字元的欄位，例如：'分隔符
     號'、'引號'、或是 '分行符號' 的其他字元。

 -- 資料: csv.QUOTE_NONNUMERIC

     引導 *note writer: 42e. 物件引用所有非數字的欄位。

     引導 *note reader: 42d. 物件轉換所有非引用的欄位為 'float'。

 -- 資料: csv.QUOTE_NONE

     引導 *note writer: 42e. 物件不得引用欄位。當前的 '分隔符號' 出現在
     輸出資料時，在他之前的字元是當前的*逸出字元 (escape character)*。如
     果沒有設定*逸出字元*，若遇到任何字元需要逸出，寫入器則會引發 *note
     Error: 2942. 。

     引導 *note reader: 42d. 物件不對引號進行特別處理。

 -- 資料: csv.QUOTE_NOTNULL

     引導 *note writer: 42e. 物件引用所有非 ‘None’ 的欄位。這與 *note
     QUOTE_ALL: 2948. 相似，除非如果欄位值為 ‘None’，該欄位則被寫成空（
     沒有引號）字串。

     引導 *note reader: 42d. 物件將空（沒有引號）欄位直譯 (interpret) 為
     ‘None’，否則會和 *note QUOTE_ALL: 2948. 有相同的表現方式。

     在 3.12 版被加入.

 -- 資料: csv.QUOTE_STRINGS

     引導 *note writer: 42e. 物件永遠在字串的欄位前後放置引號。這與
     *note QUOTE_NONNUMERIC: 14df. 相似，除非如果欄位值為 ‘None’，該欄位
     則被寫成空（沒有引號）字串。

     引導 *note reader: 42d. 物件將空（沒有引號）字串直譯為 ‘None’，否則
     會和 *note QUOTE_ALL: 2948. 有相同的表現方式。

     在 3.12 版被加入.

*note csv: 21. 模組定義下列例外：

 -- 例外: csv.Error

     當偵測到錯誤時，任何函式都可以引發。

   ---------- Footnotes ----------

   (1) 如果 ‘newline=''’ 沒有被指定，則嵌入引號中的換行符號不會被正確直
譯，使用 ‘\r\n’ 行尾 (linending) 的平台會寫入額外的 ‘\r’。自從 csv 模組
有自己 (*note 統一的: ce1.) 換行處理方式，因此指定 ‘newline=''’ 會永遠是
安全的。

   (2) 如果 ‘newline=''’ 沒有被指定，則嵌入引號中的換行符號不會被正確直
譯，使用 ‘\r\n’ 行尾 (linending) 的平台會寫入額外的 ‘\r’。自從 csv 模組
有自己 (*note 統一的: ce1.) 換行處理方式，因此指定 ‘newline=''’ 會永遠是
安全的。


File: python.info,  Node: Dialect 與格式參數,  Next: 讀取器物件,  Prev: 模組內容<3>,  Up: csv --- CSV 檔案讀取及寫入

5.14.1.2 Dialect 與格式參數
...........................

為了讓指定輸入及輸出紀錄的格式更方便，特定的格式化參數會被組成 dialect。
一個 dialect 是 *note Dialect: 1571. class 的子類別，其包含多個描述 CSV
檔案格式的多個屬性。當建立 *note reader: 42d. 或 *note writer: 42e. 物件
時，程式設計師可以指定一個字串或是一個 *note Dialect: 1571. 的子類別作為
dialect 參數。此外，或是作為替代，在'dialect'參數中，程式設計師可以指定
個別的格式化參數，其與 *note Dialect: 1571. 類別定義的屬性具有相同的名字
。

Dialect 支援下列屬性：

 -- 屬性: Dialect.delimiter

     一個單一字元 (one-character) 的字串可已用來分割欄位。預設為 ‘','’。

 -- 屬性: Dialect.doublequote

     控制 'quotechar' 的實例何時出現在欄位之中，並讓它們自己被放在引號之
     內。當屬性為 *note True: bb4.，字元會是雙引號。若為 *note False:
     adb.，在 'quotechar' 之前會先使用 'escapechar' 作為前綴字。預設為
     *note True: bb4.。

     在輸出時，若 'doublequote' 是 *note False: adb. 且'逸出字元'沒有被
     設定，當一個'引號'在欄位中被發現時，*note Error: 2942. 會被引發。

 -- 屬性: Dialect.escapechar

     一個會被寫入器使用的單一字元的字串，當 'quoting' 設定為 *note
     QUOTE_NONE: 294a. 時逸出'分隔符號'；當 'doublequote' 設定為 *note
     False: adb. 時逸出'引號'。在讀取時，'逸出字元'會移除後面的字元以及
     任何特殊意義。預設為 *note None: 61b.，表示禁止逸出。

     在 3.11 版的變更: 'escapechar' 為空是不被接受的。

 -- 屬性: Dialect.lineterminator

     由 *note writer: 42e. 產生被用來分行的字串。預設為 ‘'\r\n'’。

          備註: *note reader: 42d. 是 hard-coded 辨別 ‘'\r'’ or ‘'\n'’ 作
          為行尾 (end-of-line)，並忽略'分行符號'。未來可能會改變這個行為
          。

 -- 屬性: Dialect.quotechar

     一個單一字元的字串被用於引用包含特殊字元的欄位，像是 'delimiter'、
     'quotechar' 或是換行字元。預設為 ‘'"'’。

     在 3.11 版的變更: 'quotechar' 為空是不被允許的。

 -- 屬性: Dialect.quoting

     控制 writer 何時產生引號，以及 reader 如何辨識引號。他可以使用任何
     *note QUOTE_* 常數: 2947.且預設為 *note QUOTE_MINIMAL: 2949.。

 -- 屬性: Dialect.skipinitialspace

     若為 *note True: bb4.，在緊接著'分隔符號'後的空格會被忽略。預設為
     *note False: adb.。

 -- 屬性: Dialect.strict

     若為 ‘True’，若有錯誤的 CSV 輸入則會引發 *note Error: 2942.。預設為
     ‘False’。


File: python.info,  Node: 讀取器物件,  Next: 寫入器物件,  Prev: Dialect 與格式參數,  Up: csv --- CSV 檔案讀取及寫入

5.14.1.3 讀取器物件
...................

讀取器物件（*note reader(): 42d. 函式回傳的 *note DictReader: 989. 實例
與物件）有下列公用方法 (public method)：

 -- 方法: csvreader.__next__ ()

     回傳一個列表為讀入器的可疊代物件的下一列內容（若該物件是由 *note
     reader(): 42d. 回傳）或是一個 dict（若為 *note DictReader: 989. 實
     例），會依據當前的 *note Dialect: 1571. 進行剖析。通常會用
     ‘next(reader)’ 來進行呼叫。

讀取器物件有下列公用屬性 (public attributes)：

 -- 屬性: csvreader.dialect

     dialect 的唯讀敘述，會被剖析器使用。

 -- 屬性: csvreader.line_num

     來源疊代器所讀取的行數。這與回傳的紀錄數不同，因為可以進行跨行紀錄
     。

DictReader 物件有下列公用屬性：

 -- 屬性: DictReader.fieldnames

     若在建立物件時沒有作為參數傳遞，這個屬性會在第一次存取之前或是第一
     筆資料被讀取之前進行初始化 (initialize)。


File: python.info,  Node: 寫入器物件,  Next: 範例<14>,  Prev: 讀取器物件,  Up: csv --- CSV 檔案讀取及寫入

5.14.1.4 寫入器物件
...................

*note writer: 42e. 物件（*note writer(): 42e. 函式回傳的 *note
DictWriter: 1196. 實例與物件）有下列公用方法。對於 *note writer: 42e. 物
件而言，一個'列'中必須為一個可疊代的字串或是數字；對於 *note DictWriter:
1196. 物件而言，則必須為一個 dictionary ，且可以對應欄位標題至字串或數字
（會先透過 *note str(): 3f2. 進行傳遞）。請注意，在寫入複數 (complex
number) 時會用小括號 (parens) 包起來。這可能在其他程式讀取 CSV 檔案時導
致某些問題（假設他們完全支援複雜數字）。

 -- 方法: csvwriter.writerow (row)

     將參數 'row' 寫入至寫入器的檔案物件中，並依照當前的 *note Dialect:
     1571. 進行格式化。回傳下層檔案物件 'write' 方法的回傳值。

     在 3.5 版的變更: 新增對任意可疊代物件 (arbitrary iterables) 的支援
     。

 -- 方法: csvwriter.writerows (rows)

     將 'rows' 中所有元素（為上述的一個可疊代的 'row' 物件）寫入至寫入器
     的檔案物件中，並依照當前的 dialect 進行格式化。

寫入器物件有下列公用屬性：

 -- 屬性: csvwriter.dialect

     dialect 的唯讀敘述，會被寫入器使用。

DictWriter 物件有下列公用方法：

 -- 方法: DictWriter.writeheader ()

     將具欄位標題的一列（於建構函式 (constructor) 中指定的）寫入至寫入器
     的檔案物件中，並依照當前的 dialect 進行格式化。回傳內部呼叫 *note
     csvwriter.writerow(): d90. 的回傳值。

     在 3.2 版被加入.

     在 3.8 版的變更: *note writeheader(): 1197. 現在也會回傳內部呼叫
     *note csvwriter.writerow(): d90. 的回傳值。


File: python.info,  Node: 範例<14>,  Prev: 寫入器物件,  Up: csv --- CSV 檔案讀取及寫入

5.14.1.5 範例
.............

最簡單的讀取 CSV 檔案範例：

     import csv
     with open('some.csv', newline='') as f:
         reader = csv.reader(f)
         for row in reader:
             print(row)

讀取一個其他格式的檔案：

     import csv
     with open('passwd', newline='') as f:
         reader = csv.reader(f, delimiter=':', quoting=csv.QUOTE_NONE)
         for row in reader:
             print(row)

相對最簡單、可行的寫入範例為：

     import csv
     with open('some.csv', 'w', newline='') as f:
         writer = csv.writer(f)
         writer.writerows(someiterable)

當 *note open(): 4c0. 被使用於開啟並讀取一個 CSV 檔案，該檔案會預設使用
系統預設的編碼格式（請見 *note locale.getencoding(): 2bc.），並解碼為
unicode。若要使用不同編碼格式進行檔案解碼，請使用 open 函式的 ‘encoding’
引數：

     import csv
     with open('some.csv', newline='', encoding='utf-8') as f:
         reader = csv.reader(f)
         for row in reader:
             print(row)

同理可以應用到使用不同編碼格式進行寫入：當開啟輸出檔案時，指定
‘encoding’ 引數。

註冊一個新的 dialect ：

     import csv
     csv.register_dialect('unixpwd', delimiter=':', quoting=csv.QUOTE_NONE)
     with open('passwd', newline='') as f:
         reader = csv.reader(f, 'unixpwd')

稍微進階的讀取器用法 - 擷取及回報錯誤：

     import csv, sys
     filename = 'some.csv'
     with open(filename, newline='') as f:
         reader = csv.reader(f)
         try:
             for row in reader:
                 print(row)
         except csv.Error as e:
             sys.exit('file {}, line {}: {}'.format(filename, reader.line_num, e))

而當模組無法直接支援剖析字串時，仍可以輕鬆的解決：

     import csv
     for row in csv.reader(['one,two,three']):
         print(row)

註解
....


File: python.info,  Node: configparser --- 設定檔剖析器,  Next: tomllib --- 剖析 TOML 檔案,  Prev: csv --- CSV 檔案讀取及寫入,  Up: 檔案格式

5.14.2 ‘configparser’ -- 設定檔剖析器
-------------------------------------

'原始碼：'Lib/configparser.py(1)

__________________________________________________________________

This module provides the *note ConfigParser: 1aa. class which implements
a basic configuration language which provides a structure similar to
what's found in Microsoft Windows INI files.  You can use this to write
Python programs which can be customized by end users easily.

     備註: This library does 'not' interpret or write the value-type
     prefixes used in the Windows Registry extended version of INI
     syntax.

也參考
......

*note tomllib: e5. 模組

     TOML is a well-specified format for application configuration
     files.  It is specifically designed to be an improved version of
     INI.

*note shlex: b2. 模組

     Support for creating Unix shell-like mini-languages which can also
     be used for application configuration files.

*note json: 76. 模組

     The ‘json’ module implements a subset of JavaScript syntax which is
     sometimes used for configuration, but does not support comments.

* Menu:

* Quick Start::
* Supported Datatypes::
* Fallback Values::
* Supported INI File Structure::
* Unnamed Sections::
* Interpolation of values::
* Mapping Protocol Access::
* Customizing Parser Behaviour::
* Legacy API Examples::
* ConfigParser 物件::
* RawConfigParser 物件::
* 例外: 例外<5>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/configparser.py


File: python.info,  Node: Quick Start,  Next: Supported Datatypes,  Up: configparser --- 設定檔剖析器

5.14.2.1 Quick Start
....................

Let's take a very basic configuration file that looks like this:

     [DEFAULT]
     ServerAliveInterval = 45
     Compression = yes
     CompressionLevel = 9
     ForwardX11 = yes

     [forge.example]
     User = hg

     [topsecret.server.example]
     Port = 50022
     ForwardX11 = no

The structure of INI files is described *note in the following section:
2961.  Essentially, the file consists of sections, each of which
contains keys with values.  *note configparser: 1b. classes can read and
write such files.  Let's start by creating the above configuration file
programmatically.

     >>> import configparser
     >>> config = configparser.ConfigParser()
     >>> config['DEFAULT'] = {'ServerAliveInterval': '45',
     ...                      'Compression': 'yes',
     ...                      'CompressionLevel': '9'}
     >>> config['forge.example'] = {}
     >>> config['forge.example']['User'] = 'hg'
     >>> config['topsecret.server.example'] = {}
     >>> topsecret = config['topsecret.server.example']
     >>> topsecret['Port'] = '50022'     # mutates the parser
     >>> topsecret['ForwardX11'] = 'no'  # same here
     >>> config['DEFAULT']['ForwardX11'] = 'yes'
     >>> with open('example.ini', 'w') as configfile:
     ...   config.write(configfile)
     ...

As you can see, we can treat a config parser much like a dictionary.
There are differences, *note outlined later: 2962, but the behavior is
very close to what you would expect from a dictionary.

Now that we have created and saved a configuration file, let's read it
back and explore the data it holds.

     >>> config = configparser.ConfigParser()
     >>> config.sections()
     []
     >>> config.read('example.ini')
     ['example.ini']
     >>> config.sections()
     ['forge.example', 'topsecret.server.example']
     >>> 'forge.example' in config
     True
     >>> 'python.org' in config
     False
     >>> config['forge.example']['User']
     'hg'
     >>> config['DEFAULT']['Compression']
     'yes'
     >>> topsecret = config['topsecret.server.example']
     >>> topsecret['ForwardX11']
     'no'
     >>> topsecret['Port']
     '50022'
     >>> for key in config['forge.example']:
     ...     print(key)
     user
     compressionlevel
     serveraliveinterval
     compression
     forwardx11
     >>> config['forge.example']['ForwardX11']
     'yes'

As we can see above, the API is pretty straightforward.  The only bit of
magic involves the ‘DEFAULT’ section which provides default values for
all other sections (1).  Note also that keys in sections are
case-insensitive and stored in lowercase (2).

It is possible to read several configurations into a single *note
ConfigParser: 1aa, where the most recently added configuration has the
highest priority.  Any conflicting keys are taken from the more recent
configuration while the previously existing keys are retained.  The
example below reads in an ‘override.ini’ file, which will override any
conflicting keys from the ‘example.ini’ file.

     [DEFAULT]
     ServerAliveInterval = -1

     >>> config_override = configparser.ConfigParser()
     >>> config_override['DEFAULT'] = {'ServerAliveInterval': '-1'}
     >>> with open('override.ini', 'w') as configfile:
     ...     config_override.write(configfile)
     ...
     >>> config_override = configparser.ConfigParser()
     >>> config_override.read(['example.ini', 'override.ini'])
     ['example.ini', 'override.ini']
     >>> print(config_override.get('DEFAULT', 'ServerAliveInterval'))
     -1

This behaviour is equivalent to a *note ConfigParser.read(): 13d3. call
with several files passed to the 'filenames' parameter.

   ---------- Footnotes ----------

   (1) Config parsers allow for heavy customization.  If you are
interested in changing the behaviour outlined by the footnote reference,
consult the *note Customizing Parser Behaviour: 2963. section.

   (2) Config parsers allow for heavy customization.  If you are
interested in changing the behaviour outlined by the footnote reference,
consult the *note Customizing Parser Behaviour: 2963. section.


File: python.info,  Node: Supported Datatypes,  Next: Fallback Values,  Prev: Quick Start,  Up: configparser --- 設定檔剖析器

5.14.2.2 Supported Datatypes
............................

Config parsers do not guess datatypes of values in configuration files,
always storing them internally as strings.  This means that if you need
other datatypes, you should convert on your own:

     >>> int(topsecret['Port'])
     50022
     >>> float(topsecret['CompressionLevel'])
     9.0

Since this task is so common, config parsers provide a range of handy
getter methods to handle integers, floats and booleans.  The last one is
the most interesting because simply passing the value to ‘bool()’ would
do no good since ‘bool('False')’ is still ‘True’.  This is why config
parsers also provide *note getboolean(): 2965.  This method is
case-insensitive and recognizes Boolean values from ‘'yes'’/‘'no'’,
‘'on'’/‘'off'’, ‘'true'’/‘'false'’ and ‘'1'’/‘'0'’ (1).  For example:

     >>> topsecret.getboolean('ForwardX11')
     False
     >>> config['forge.example'].getboolean('ForwardX11')
     True
     >>> config.getboolean('forge.example', 'Compression')
     True

Apart from *note getboolean(): 2965, config parsers also provide
equivalent *note getint(): 2966. and *note getfloat(): 2967. methods.
You can register your own converters and customize the provided ones.
(2)

   ---------- Footnotes ----------

   (1) Config parsers allow for heavy customization.  If you are
interested in changing the behaviour outlined by the footnote reference,
consult the *note Customizing Parser Behaviour: 2963. section.

   (2) Config parsers allow for heavy customization.  If you are
interested in changing the behaviour outlined by the footnote reference,
consult the *note Customizing Parser Behaviour: 2963. section.


File: python.info,  Node: Fallback Values,  Next: Supported INI File Structure,  Prev: Supported Datatypes,  Up: configparser --- 設定檔剖析器

5.14.2.3 Fallback Values
........................

As with a dictionary, you can use a section's *note get(): 1204. method
to provide fallback values:

     >>> topsecret.get('Port')
     '50022'
     >>> topsecret.get('CompressionLevel')
     '9'
     >>> topsecret.get('Cipher')
     >>> topsecret.get('Cipher', '3des-cbc')
     '3des-cbc'

Please note that default values have precedence over fallback values.
For instance, in our example the ‘'CompressionLevel'’ key was specified
only in the ‘'DEFAULT'’ section.  If we try to get it from the section
‘'topsecret.server.example'’, we will always get the default, even if we
specify a fallback:

     >>> topsecret.get('CompressionLevel', '3')
     '9'

One more thing to be aware of is that the parser-level *note get():
1204. method provides a custom, more complex interface, maintained for
backwards compatibility.  When using this method, a fallback value can
be provided via the ‘fallback’ keyword-only argument:

     >>> config.get('forge.example', 'monster',
     ...            fallback='No such things as monsters')
     'No such things as monsters'

The same ‘fallback’ argument can be used with the *note getint(): 2966,
*note getfloat(): 2967. and *note getboolean(): 2965. methods, for
example:

     >>> 'BatchMode' in topsecret
     False
     >>> topsecret.getboolean('BatchMode', fallback=True)
     True
     >>> config['DEFAULT']['BatchMode'] = 'no'
     >>> topsecret.getboolean('BatchMode', fallback=True)
     False


File: python.info,  Node: Supported INI File Structure,  Next: Unnamed Sections,  Prev: Fallback Values,  Up: configparser --- 設定檔剖析器

5.14.2.4 Supported INI File Structure
.....................................

A configuration file consists of sections, each led by a ‘[section]’
header, followed by key/value entries separated by a specific string
(‘=’ or ‘:’ by default (1)).  By default, section names are case
sensitive but keys are not (2).  Leading and trailing whitespace is
removed from keys and values.  Values can be omitted if the parser is
configured to allow it (3), in which case the key/value delimiter may
also be left out.  Values can also span multiple lines, as long as they
are indented deeper than the first line of the value.  Depending on the
parser's mode, blank lines may be treated as parts of multiline values
or ignored.

By default, a valid section name can be any string that does not contain
'\n'.  To change this, see *note ConfigParser.SECTCRE: 2969.

The first section name may be omitted if the parser is configured to
allow an unnamed top level section with ‘allow_unnamed_section=True’.
In this case, the keys/values may be retrieved by *note UNNAMED_SECTION:
296a. as in ‘config[UNNAMED_SECTION]’.

Configuration files may include comments, prefixed by specific
characters (‘#’ and ‘;’ by default (4)).  Comments may appear on their
own on an otherwise empty line, possibly indented.  (5)

舉例來說：

     [Simple Values]
     key=value
     spaces in keys=allowed
     spaces in values=allowed as well
     spaces around the delimiter = obviously
     you can also use : to delimit keys from values

     [All Values Are Strings]
     values like this: 1000000
     or this: 3.14159265359
     are they treated as numbers? : no
     integers, floats and booleans are held as: strings
     can use the API to get converted values directly: true

     [Multiline Values]
     chorus: I'm a lumberjack, and I'm okay
         I sleep all night and I work all day

     [No Values]
     key_without_value
     empty string value here =

     [You can use comments]
     # like this
     ; or this

     # By default only in an empty line.
     # Inline comments can be harmful because they prevent users
     # from using the delimiting characters as parts of values.
     # That being said, this can be customized.

         [Sections Can Be Indented]
             can_values_be_as_well = True
             does_that_mean_anything_special = False
             purpose = formatting for readability
             multiline_values = are
                 handled just fine as
                 long as they are indented
                 deeper than the first line
                 of a value
             # Did I mention we can indent comments, too?

   ---------- Footnotes ----------

   (1) Config parsers allow for heavy customization.  If you are
interested in changing the behaviour outlined by the footnote reference,
consult the *note Customizing Parser Behaviour: 2963. section.

   (2) Config parsers allow for heavy customization.  If you are
interested in changing the behaviour outlined by the footnote reference,
consult the *note Customizing Parser Behaviour: 2963. section.

   (3) Config parsers allow for heavy customization.  If you are
interested in changing the behaviour outlined by the footnote reference,
consult the *note Customizing Parser Behaviour: 2963. section.

   (4) Config parsers allow for heavy customization.  If you are
interested in changing the behaviour outlined by the footnote reference,
consult the *note Customizing Parser Behaviour: 2963. section.

   (5) Config parsers allow for heavy customization.  If you are
interested in changing the behaviour outlined by the footnote reference,
consult the *note Customizing Parser Behaviour: 2963. section.


File: python.info,  Node: Unnamed Sections,  Next: Interpolation of values,  Prev: Supported INI File Structure,  Up: configparser --- 設定檔剖析器

5.14.2.5 Unnamed Sections
.........................

The name of the first section (or unique) may be omitted and values
retrieved by the *note UNNAMED_SECTION: 296a. attribute.

     >>> config = """
     ... option = value
     ...
     ... [  Section 2  ]
     ... another = val
     ... """
     >>> unnamed = configparser.ConfigParser(allow_unnamed_section=True)
     >>> unnamed.read_string(config)
     >>> unnamed.get(configparser.UNNAMED_SECTION, 'option')
     'value'


File: python.info,  Node: Interpolation of values,  Next: Mapping Protocol Access,  Prev: Unnamed Sections,  Up: configparser --- 設定檔剖析器

5.14.2.6 Interpolation of values
................................

On top of the core functionality, *note ConfigParser: 1aa. supports
interpolation.  This means values can be preprocessed before returning
them from ‘get()’ calls.

 -- 類別: configparser.BasicInterpolation

     The default implementation used by *note ConfigParser: 1aa.  It
     enables values to contain format strings which refer to other
     values in the same section, or values in the special default
     section (1).  Additional default values can be provided on
     initialization.

     舉例來說：

          [Paths]
          home_dir: /Users
          my_dir: %(home_dir)s/lumberjack
          my_pictures: %(my_dir)s/Pictures

          [Escape]
          # use a %% to escape the % sign (% is the only character that needs to be escaped):
          gain: 80%%

     In the example above, *note ConfigParser: 1aa. with 'interpolation'
     set to ‘BasicInterpolation()’ would resolve ‘%(home_dir)s’ to the
     value of ‘home_dir’ (‘/Users’ in this case).  ‘%(my_dir)s’ in
     effect would resolve to ‘/Users/lumberjack’.  All interpolations
     are done on demand so keys used in the chain of references do not
     have to be specified in any specific order in the configuration
     file.

     With ‘interpolation’ set to ‘None’, the parser would simply return
     ‘%(my_dir)s/Pictures’ as the value of ‘my_pictures’ and
     ‘%(home_dir)s/lumberjack’ as the value of ‘my_dir’.

 -- 類別: configparser.ExtendedInterpolation

     An alternative handler for interpolation which implements a more
     advanced syntax, used for instance in ‘zc.buildout’.  Extended
     interpolation is using ‘${section:option}’ to denote a value from a
     foreign section.  Interpolation can span multiple levels.  For
     convenience, if the ‘section:’ part is omitted, interpolation
     defaults to the current section (and possibly the default values
     from the special section).

     For example, the configuration specified above with basic
     interpolation, would look like this with extended interpolation:

          [Paths]
          home_dir: /Users
          my_dir: ${home_dir}/lumberjack
          my_pictures: ${my_dir}/Pictures

          [Escape]
          # use a $$ to escape the $ sign ($ is the only character that needs to be escaped):
          cost: $$80

     Values from other sections can be fetched as well:

          [Common]
          home_dir: /Users
          library_dir: /Library
          system_dir: /System
          macports_dir: /opt/local

          [Frameworks]
          Python: 3.2
          path: ${Common:system_dir}/Library/Frameworks/

          [Arthur]
          nickname: Two Sheds
          last_name: Jackson
          my_dir: ${Common:home_dir}/twosheds
          my_pictures: ${my_dir}/Pictures
          python_dir: ${Frameworks:path}/Python/Versions/${Frameworks:Python}

   ---------- Footnotes ----------

   (1) Config parsers allow for heavy customization.  If you are
interested in changing the behaviour outlined by the footnote reference,
consult the *note Customizing Parser Behaviour: 2963. section.


File: python.info,  Node: Mapping Protocol Access,  Next: Customizing Parser Behaviour,  Prev: Interpolation of values,  Up: configparser --- 設定檔剖析器

5.14.2.7 Mapping Protocol Access
................................

在 3.2 版被加入.

Mapping protocol access is a generic name for functionality that enables
using custom objects as if they were dictionaries.  In case of *note
configparser: 1b, the mapping interface implementation is using the
‘parser['section']['option']’ notation.

‘parser['section']’ in particular returns a proxy for the section's data
in the parser.  This means that the values are not copied but they are
taken from the original parser on demand.  What's even more important is
that when values are changed on a section proxy, they are actually
mutated in the original parser.

*note configparser: 1b. objects behave as close to actual dictionaries
as possible.  The mapping interface is complete and adheres to the *note
MutableMapping: 1048. ABC. However, there are a few differences that
should be taken into account:

   * By default, all keys in sections are accessible in a
     case-insensitive manner (1).  E.g.  ‘for option in
     parser["section"]’ yields only ‘optionxform’'ed option key names.
     This means lowercased keys by default.  At the same time, for a
     section that holds the key ‘'a'’, both expressions return ‘True’:

          "a" in parser["section"]
          "A" in parser["section"]

   * All sections include ‘DEFAULTSECT’ values as well which means that
     ‘.clear()’ on a section may not leave the section visibly empty.
     This is because default values cannot be deleted from the section
     (because technically they are not there).  If they are overridden
     in the section, deleting causes the default value to be visible
     again.  Trying to delete a default value causes a *note KeyError:
     2fb.

   * ‘DEFAULTSECT’ cannot be removed from the parser:

        * trying to delete it raises *note ValueError: 1e7,

        * ‘parser.clear()’ leaves it intact,

        * ‘parser.popitem()’ never returns it.

   * ‘parser.get(section, option, **kwargs)’ - the second argument is
     'not' a fallback value.  Note however that the section-level
     ‘get()’ methods are compatible both with the mapping protocol and
     the classic configparser API.

   * ‘parser.items()’ is compatible with the mapping protocol (returns a
     list of 'section_name', 'section_proxy' pairs including the
     DEFAULTSECT). However, this method can also be invoked with
     arguments: ‘parser.items(section, raw, vars)’.  The latter call
     returns a list of 'option', 'value' pairs for a specified
     ‘section’, with all interpolations expanded (unless ‘raw=True’ is
     provided).

The mapping protocol is implemented on top of the existing legacy API so
that subclasses overriding the original interface still should have
mappings working as expected.

   ---------- Footnotes ----------

   (1) Config parsers allow for heavy customization.  If you are
interested in changing the behaviour outlined by the footnote reference,
consult the *note Customizing Parser Behaviour: 2963. section.


File: python.info,  Node: Customizing Parser Behaviour,  Next: Legacy API Examples,  Prev: Mapping Protocol Access,  Up: configparser --- 設定檔剖析器

5.14.2.8 Customizing Parser Behaviour
.....................................

There are nearly as many INI format variants as there are applications
using it.  *note configparser: 1b. goes a long way to provide support
for the largest sensible set of INI styles available.  The default
functionality is mainly dictated by historical background and it's very
likely that you will want to customize some of the features.

The most common way to change the way a specific config parser works is
to use the ‘__init__()’ options:

   * 'defaults', default value: ‘None’

     This option accepts a dictionary of key-value pairs which will be
     initially put in the ‘DEFAULT’ section.  This makes for an elegant
     way to support concise configuration files that don't specify
     values which are the same as the documented default.

     Hint: if you want to specify default values for a specific section,
     use *note read_dict(): 296e. before you read the actual file.

   * 'dict_type', default value: *note dict: 23b.

     This option has a major impact on how the mapping protocol will
     behave and how the written configuration files look.  With the
     standard dictionary, every section is stored in the order they were
     added to the parser.  Same goes for options within sections.

     An alternative dictionary type can be used for example to sort
     sections and options on write-back.

     Please note: there are ways to add a set of key-value pairs in a
     single operation.  When you use a regular dictionary in those
     operations, the order of the keys will be ordered.  For example:

          >>> parser = configparser.ConfigParser()
          >>> parser.read_dict({'section1': {'key1': 'value1',
          ...                                'key2': 'value2',
          ...                                'key3': 'value3'},
          ...                   'section2': {'keyA': 'valueA',
          ...                                'keyB': 'valueB',
          ...                                'keyC': 'valueC'},
          ...                   'section3': {'foo': 'x',
          ...                                'bar': 'y',
          ...                                'baz': 'z'}
          ... })
          >>> parser.sections()
          ['section1', 'section2', 'section3']
          >>> [option for option in parser['section3']]
          ['foo', 'bar', 'baz']

   * 'allow_no_value', default value: ‘False’

     Some configuration files are known to include settings without
     values, but which otherwise conform to the syntax supported by
     *note configparser: 1b.  The 'allow_no_value' parameter to the
     constructor can be used to indicate that such values should be
     accepted:

          >>> import configparser

          >>> sample_config = """
          ... [mysqld]
          ...   user = mysql
          ...   pid-file = /var/run/mysqld/mysqld.pid
          ...   skip-external-locking
          ...   old_passwords = 1
          ...   skip-bdb
          ...   # we don't need ACID today
          ...   skip-innodb
          ... """
          >>> config = configparser.ConfigParser(allow_no_value=True)
          >>> config.read_string(sample_config)

          >>> # Settings with values are treated as before:
          >>> config["mysqld"]["user"]
          'mysql'

          >>> # Settings without values provide None:
          >>> config["mysqld"]["skip-bdb"]

          >>> # Settings which aren't specified still raise an error:
          >>> config["mysqld"]["does-not-exist"]
          Traceback (most recent call last):
            ...
          KeyError: 'does-not-exist'

   * 'delimiters', default value: ‘('=', ':')’

     Delimiters are substrings that delimit keys from values within a
     section.  The first occurrence of a delimiting substring on a line
     is considered a delimiter.  This means values (but not keys) can
     contain the delimiters.

     See also the 'space_around_delimiters' argument to *note
     ConfigParser.write(): 296f.

   * 'comment_prefixes', default value: ‘('#', ';')’

   * 'inline_comment_prefixes', default value: ‘None’

     Comment prefixes are strings that indicate the start of a valid
     comment within a config file.  'comment_prefixes' are used only on
     otherwise empty lines (optionally indented) whereas
     'inline_comment_prefixes' can be used after every valid value (e.g.
     section names, options and empty lines as well).  By default inline
     comments are disabled and ‘'#'’ and ‘';'’ are used as prefixes for
     whole line comments.

     在 3.2 版的變更: In previous versions of *note configparser: 1b.
     behaviour matched ‘comment_prefixes=('#',';')’ and
     ‘inline_comment_prefixes=(';',)’.

     Please note that config parsers don't support escaping of comment
     prefixes so using 'inline_comment_prefixes' may prevent users from
     specifying option values with characters used as comment prefixes.
     When in doubt, avoid setting 'inline_comment_prefixes'.  In any
     circumstances, the only way of storing comment prefix characters at
     the beginning of a line in multiline values is to interpolate the
     prefix, for example:

          >>> from configparser import ConfigParser, ExtendedInterpolation
          >>> parser = ConfigParser(interpolation=ExtendedInterpolation())
          >>> # the default BasicInterpolation could be used as well
          >>> parser.read_string("""
          ... [DEFAULT]
          ... hash = #
          ...
          ... [hashes]
          ... shebang =
          ...   ${hash}!/usr/bin/env python
          ...   ${hash} -*- coding: utf-8 -*-
          ...
          ... extensions =
          ...   enabled_extension
          ...   another_extension
          ...   #disabled_by_comment
          ...   yet_another_extension
          ...
          ... interpolation not necessary = if # is not at line start
          ... even in multiline values = line #1
          ...   line #2
          ...   line #3
          ... """)
          >>> print(parser['hashes']['shebang'])

          #!/usr/bin/env python
          # -*- coding: utf-8 -*-
          >>> print(parser['hashes']['extensions'])

          enabled_extension
          another_extension
          yet_another_extension
          >>> print(parser['hashes']['interpolation not necessary'])
          if # is not at line start
          >>> print(parser['hashes']['even in multiline values'])
          line #1
          line #2
          line #3

   * 'strict', default value: ‘True’

     When set to ‘True’, the parser will not allow for any section or
     option duplicates while reading from a single source (using *note
     read_file(): 4ac, *note read_string(): 2970. or *note read_dict():
     296e.).  It is recommended to use strict parsers in new
     applications.

     在 3.2 版的變更: In previous versions of *note configparser: 1b.
     behaviour matched ‘strict=False’.

   * 'empty_lines_in_values', default value: ‘True’

     In config parsers, values can span multiple lines as long as they
     are indented more than the key that holds them.  By default parsers
     also let empty lines to be parts of values.  At the same time, keys
     can be arbitrarily indented themselves to improve readability.  In
     consequence, when configuration files get big and complex, it is
     easy for the user to lose track of the file structure.  Take for
     instance:

          [Section]
          key = multiline
            value with a gotcha

           this = is still a part of the multiline value of 'key'

     This can be especially problematic for the user to see if she's
     using a proportional font to edit the file.  That is why when your
     application does not need values with empty lines, you should
     consider disallowing them.  This will make empty lines split keys
     every time.  In the example above, it would produce two keys, ‘key’
     and ‘this’.

   * 'default_section', default value: ‘configparser.DEFAULTSECT’ (that
     is: ‘"DEFAULT"’)

     The convention of allowing a special section of default values for
     other sections or interpolation purposes is a powerful concept of
     this library, letting users create complex declarative
     configurations.  This section is normally called ‘"DEFAULT"’ but
     this can be customized to point to any other valid section name.
     Some typical values include: ‘"general"’ or ‘"common"’.  The name
     provided is used for recognizing default sections when reading from
     any source and is used when writing configuration back to a file.
     Its current value can be retrieved using the
     ‘parser_instance.default_section’ attribute and may be modified at
     runtime (i.e.  to convert files from one format to another).

   * 'interpolation', default value: ‘configparser.BasicInterpolation’

     Interpolation behaviour may be customized by providing a custom
     handler through the 'interpolation' argument.  ‘None’ can be used
     to turn off interpolation completely, ‘ExtendedInterpolation()’
     provides a more advanced variant inspired by ‘zc.buildout’.  More
     on the subject in the *note dedicated documentation section: 296d.
     *note RawConfigParser: f07. has a default value of ‘None’.

   * 'converters', default value: not set

     Config parsers provide option value getters that perform type
     conversion.  By default *note getint(): 2966, *note getfloat():
     2967, and *note getboolean(): 2965. are implemented.  Should other
     getters be desirable, users may define them in a subclass or pass a
     dictionary where each key is a name of the converter and each value
     is a callable implementing said conversion.  For instance, passing
     ‘{'decimal': decimal.Decimal}’ would add ‘getdecimal()’ on both the
     parser object and all section proxies.  In other words, it will be
     possible to write both ‘parser_instance.getdecimal('section',
     'key', fallback=0)’ and
     ‘parser_instance['section'].getdecimal('key', 0)’.

     If the converter needs to access the state of the parser, it can be
     implemented as a method on a config parser subclass.  If the name
     of this method starts with ‘get’, it will be available on all
     section proxies, in the dict-compatible form (see the
     ‘getdecimal()’ example above).

More advanced customization may be achieved by overriding default values
of these parser attributes.  The defaults are defined on the classes, so
they may be overridden by subclasses or by attribute assignment.

 -- 屬性: ConfigParser.BOOLEAN_STATES

     By default when using *note getboolean(): 2965, config parsers
     consider the following values ‘True’: ‘'1'’, ‘'yes'’, ‘'true'’,
     ‘'on'’ and the following values ‘False’: ‘'0'’, ‘'no'’, ‘'false'’,
     ‘'off'’.  You can override this by specifying a custom dictionary
     of strings and their Boolean outcomes.  For example:

          >>> custom = configparser.ConfigParser()
          >>> custom['section1'] = {'funky': 'nope'}
          >>> custom['section1'].getboolean('funky')
          Traceback (most recent call last):
          ...
          ValueError: Not a boolean: nope
          >>> custom.BOOLEAN_STATES = {'sure': True, 'nope': False}
          >>> custom['section1'].getboolean('funky')
          False

     Other typical Boolean pairs include ‘accept’/‘reject’ or
     ‘enabled’/‘disabled’.

 -- 方法: ConfigParser.optionxform (option)

     This method transforms option names on every read, get, or set
     operation.  The default converts the name to lowercase.  This also
     means that when a configuration file gets written, all keys will be
     lowercase.  Override this method if that's unsuitable.  For
     example:

          >>> config = """
          ... [Section1]
          ... Key = Value
          ...
          ... [Section2]
          ... AnotherKey = Value
          ... """
          >>> typical = configparser.ConfigParser()
          >>> typical.read_string(config)
          >>> list(typical['Section1'].keys())
          ['key']
          >>> list(typical['Section2'].keys())
          ['anotherkey']
          >>> custom = configparser.RawConfigParser()
          >>> custom.optionxform = lambda option: option
          >>> custom.read_string(config)
          >>> list(custom['Section1'].keys())
          ['Key']
          >>> list(custom['Section2'].keys())
          ['AnotherKey']

          備註: The optionxform function transforms option names to a
          canonical form.  This should be an idempotent function: if the
          name is already in canonical form, it should be returned
          unchanged.

 -- 屬性: ConfigParser.SECTCRE

     A compiled regular expression used to parse section headers.  The
     default matches ‘[section]’ to the name ‘"section"’.  Whitespace is
     considered part of the section name, thus ‘[ larch ]’ will be read
     as a section of name ‘" larch "’.  Override this attribute if
     that's unsuitable.  For example:

          >>> import re
          >>> config = """
          ... [Section 1]
          ... option = value
          ...
          ... [  Section 2  ]
          ... another = val
          ... """
          >>> typical = configparser.ConfigParser()
          >>> typical.read_string(config)
          >>> typical.sections()
          ['Section 1', '  Section 2  ']
          >>> custom = configparser.ConfigParser()
          >>> custom.SECTCRE = re.compile(r"\[ *(?P<header>[^]]+?) *\]")
          >>> custom.read_string(config)
          >>> custom.sections()
          ['Section 1', 'Section 2']

          備註: While ConfigParser objects also use an ‘OPTCRE’
          attribute for recognizing option lines, it's not recommended
          to override it because that would interfere with constructor
          options 'allow_no_value' and 'delimiters'.


File: python.info,  Node: Legacy API Examples,  Next: ConfigParser 物件,  Prev: Customizing Parser Behaviour,  Up: configparser --- 設定檔剖析器

5.14.2.9 Legacy API Examples
............................

Mainly because of backwards compatibility concerns, *note configparser:
1b. provides also a legacy API with explicit ‘get’/‘set’ methods.  While
there are valid use cases for the methods outlined below, mapping
protocol access is preferred for new projects.  The legacy API is at
times more advanced, low-level and downright counterintuitive.

An example of writing to a configuration file:

     import configparser

     config = configparser.RawConfigParser()

     # Please note that using RawConfigParser's set functions, you can assign
     # non-string values to keys internally, but will receive an error when
     # attempting to write to a file or when you get it in non-raw mode. Setting
     # values using the mapping protocol or ConfigParser's set() does not allow
     # such assignments to take place.
     config.add_section('Section1')
     config.set('Section1', 'an_int', '15')
     config.set('Section1', 'a_bool', 'true')
     config.set('Section1', 'a_float', '3.1415')
     config.set('Section1', 'baz', 'fun')
     config.set('Section1', 'bar', 'Python')
     config.set('Section1', 'foo', '%(bar)s is %(baz)s!')

     # Writing our configuration file to 'example.cfg'
     with open('example.cfg', 'w') as configfile:
         config.write(configfile)

An example of reading the configuration file again:

     import configparser

     config = configparser.RawConfigParser()
     config.read('example.cfg')

     # getfloat() raises an exception if the value is not a float
     # getint() and getboolean() also do this for their respective types
     a_float = config.getfloat('Section1', 'a_float')
     an_int = config.getint('Section1', 'an_int')
     print(a_float + an_int)

     # Notice that the next output does not interpolate '%(bar)s' or '%(baz)s'.
     # This is because we are using a RawConfigParser().
     if config.getboolean('Section1', 'a_bool'):
         print(config.get('Section1', 'foo'))

To get interpolation, use *note ConfigParser: 1aa.:

     import configparser

     cfg = configparser.ConfigParser()
     cfg.read('example.cfg')

     # Set the optional *raw* argument of get() to True if you wish to disable
     # interpolation in a single get operation.
     print(cfg.get('Section1', 'foo', raw=False))  # -> "Python is fun!"
     print(cfg.get('Section1', 'foo', raw=True))   # -> "%(bar)s is %(baz)s!"

     # The optional *vars* argument is a dict with members that will take
     # precedence in interpolation.
     print(cfg.get('Section1', 'foo', vars={'bar': 'Documentation',
                                            'baz': 'evil'}))

     # The optional *fallback* argument can be used to provide a fallback value
     print(cfg.get('Section1', 'foo'))
           # -> "Python is fun!"

     print(cfg.get('Section1', 'foo', fallback='Monty is not.'))
           # -> "Python is fun!"

     print(cfg.get('Section1', 'monster', fallback='No such things as monsters.'))
           # -> "No such things as monsters."

     # A bare print(cfg.get('Section1', 'monster')) would raise NoOptionError
     # but we can also use:

     print(cfg.get('Section1', 'monster', fallback=None))
           # -> None

Default values are available in both types of ConfigParsers.  They are
used in interpolation if an option used is not defined elsewhere.

     import configparser

     # New instance with 'bar' and 'baz' defaulting to 'Life' and 'hard' each
     config = configparser.ConfigParser({'bar': 'Life', 'baz': 'hard'})
     config.read('example.cfg')

     print(config.get('Section1', 'foo'))     # -> "Python is fun!"
     config.remove_option('Section1', 'bar')
     config.remove_option('Section1', 'baz')
     print(config.get('Section1', 'foo'))     # -> "Life is hard!"


File: python.info,  Node: ConfigParser 物件,  Next: RawConfigParser 物件,  Prev: Legacy API Examples,  Up: configparser --- 設定檔剖析器

5.14.2.10 ConfigParser 物件
...........................

 -- 類別: configparser.ConfigParser (defaults=None, dict_type=dict,
          allow_no_value=False, delimiters=('=', ':'),
          comment_prefixes=('#', ';'), inline_comment_prefixes=None,
          strict=True, empty_lines_in_values=True,
          default_section=configparser.DEFAULTSECT,
          interpolation=BasicInterpolation(), converters={})

     The main configuration parser.  When 'defaults' is given, it is
     initialized into the dictionary of intrinsic defaults.  When
     'dict_type' is given, it will be used to create the dictionary
     objects for the list of sections, for the options within a section,
     and for the default values.

     When 'delimiters' is given, it is used as the set of substrings
     that divide keys from values.  When 'comment_prefixes' is given, it
     will be used as the set of substrings that prefix comments in
     otherwise empty lines.  Comments can be indented.  When
     'inline_comment_prefixes' is given, it will be used as the set of
     substrings that prefix comments in non-empty lines.

     When 'strict' is ‘True’ (the default), the parser won't allow for
     any section or option duplicates while reading from a single source
     (file, string or dictionary), raising *note DuplicateSectionError:
     1207. or *note DuplicateOptionError: 1208.  When
     'empty_lines_in_values' is ‘False’ (default: ‘True’), each empty
     line marks the end of an option.  Otherwise, internal empty lines
     of a multiline option are kept as part of the value.  When
     'allow_no_value' is ‘True’ (default: ‘False’), options without
     values are accepted; the value held for these is ‘None’ and they
     are serialized without the trailing delimiter.

     When 'default_section' is given, it specifies the name for the
     special section holding default values for other sections and
     interpolation purposes (normally named ‘"DEFAULT"’).  This value
     can be retrieved and changed at runtime using the ‘default_section’
     instance attribute.  This won't re-evaluate an already parsed
     config file, but will be used when writing parsed settings to a new
     config file.

     Interpolation behaviour may be customized by providing a custom
     handler through the 'interpolation' argument.  ‘None’ can be used
     to turn off interpolation completely, ‘ExtendedInterpolation()’
     provides a more advanced variant inspired by ‘zc.buildout’.  More
     on the subject in the *note dedicated documentation section: 296d.

     All option names used in interpolation will be passed through the
     *note optionxform(): 2975. method just like any other option name
     reference.  For example, using the default implementation of *note
     optionxform(): 2975. (which converts option names to lower case),
     the values ‘foo %(bar)s’ and ‘foo %(BAR)s’ are equivalent.

     When 'converters' is given, it should be a dictionary where each
     key represents the name of a type converter and each value is a
     callable implementing the conversion from string to the desired
     datatype.  Every converter gets its own corresponding ‘get*()’
     method on the parser object and section proxies.

     It is possible to read several configurations into a single *note
     ConfigParser: 1aa, where the most recently added configuration has
     the highest priority.  Any conflicting keys are taken from the more
     recent configuration while the previously existing keys are
     retained.  The example below reads in an ‘override.ini’ file, which
     will override any conflicting keys from the ‘example.ini’ file.

          [DEFAULT]
          ServerAliveInterval = -1

          >>> config_override = configparser.ConfigParser()
          >>> config_override['DEFAULT'] = {'ServerAliveInterval': '-1'}
          >>> with open('override.ini', 'w') as configfile:
          ...     config_override.write(configfile)
          ...
          >>> config_override = configparser.ConfigParser()
          >>> config_override.read(['example.ini', 'override.ini'])
          ['example.ini', 'override.ini']
          >>> print(config_override.get('DEFAULT', 'ServerAliveInterval'))
          -1

     在 3.1 版的變更: The default 'dict_type' is *note
     collections.OrderedDict: 57f.

     在 3.2 版的變更: 'allow_no_value', 'delimiters',
     'comment_prefixes', 'strict', 'empty_lines_in_values',
     'default_section' and 'interpolation' were added.

     在 3.5 版的變更: 新增 'converters' 引數。

     在 3.7 版的變更: The 'defaults' argument is read with *note
     read_dict(): 296e, providing consistent behavior across the parser:
     non-string keys and values are implicitly converted to strings.

     在 3.8 版的變更: The default 'dict_type' is *note dict: 23b, since
     it now preserves insertion order.

     在 3.13 版的變更: Raise a *note MultilineContinuationError: 2976.
     when 'allow_no_value' is ‘True’, and a key without a value is
     continued with an indented line.

      -- 方法: defaults ()

          Return a dictionary containing the instance-wide defaults.

      -- 方法: sections ()

          Return a list of the sections available; the 'default section'
          is not included in the list.

      -- 方法: add_section (section)

          Add a section named 'section' to the instance.  If a section
          by the given name already exists, *note DuplicateSectionError:
          1207. is raised.  If the 'default section' name is passed,
          *note ValueError: 1e7. is raised.  The name of the section
          must be a string; if not, *note TypeError: 4dd. is raised.

          在 3.2 版的變更: Non-string section names raise *note
          TypeError: 4dd.

      -- 方法: has_section (section)

          Indicates whether the named 'section' is present in the
          configuration.  The 'default section' is not acknowledged.

      -- 方法: options (section)

          Return a list of options available in the specified 'section'.

      -- 方法: has_option (section, option)

          If the given 'section' exists, and contains the given
          'option', return *note True: bb4.; otherwise return *note
          False: adb.  If the specified 'section' is *note None: 61b. or
          an empty string, DEFAULT is assumed.

      -- 方法: read (filenames, encoding=None)

          Attempt to read and parse an iterable of filenames, returning
          a list of filenames which were successfully parsed.

          If 'filenames' is a string, a *note bytes: 1a5. object or a
          *note path-like object: ac2, it is treated as a single
          filename.  If a file named in 'filenames' cannot be opened,
          that file will be ignored.  This is designed so that you can
          specify an iterable of potential configuration file locations
          (for example, the current directory, the user's home
          directory, and some system-wide directory), and all existing
          configuration files in the iterable will be read.

          If none of the named files exist, the *note ConfigParser: 1aa.
          instance will contain an empty dataset.  An application which
          requires initial values to be loaded from a file should load
          the required file or files using *note read_file(): 4ac.
          before calling *note read(): 13d3. for any optional files:

               import configparser, os

               config = configparser.ConfigParser()
               config.read_file(open('defaults.cfg'))
               config.read(['site.cfg', os.path.expanduser('~/.myapp.cfg')],
                           encoding='cp1250')

          在 3.2 版的變更: Added the 'encoding' parameter.  Previously,
          all files were read using the default encoding for *note
          open(): 4c0.

          在 3.6.1 版的變更: The 'filenames' parameter accepts a *note
          path-like object: ac2.

          在 3.7 版的變更: The 'filenames' parameter accepts a *note
          bytes: 1a5. object.

      -- 方法: read_file (f, source=None)

          Read and parse configuration data from 'f' which must be an
          iterable yielding Unicode strings (for example files opened in
          text mode).

          Optional argument 'source' specifies the name of the file
          being read.  If not given and 'f' has a ‘name’ attribute, that
          is used for 'source'; the default is ‘'<???>'’.

          在 3.2 版被加入: 取代 ‘readfp()’。

      -- 方法: read_string (string, source='<string>')

          Parse configuration data from a string.

          Optional argument 'source' specifies a context-specific name
          of the string passed.  If not given, ‘'<string>'’ is used.
          This should commonly be a filesystem path or a URL.

          在 3.2 版被加入.

      -- 方法: read_dict (dictionary, source='<dict>')

          Load configuration from any object that provides a dict-like
          ‘items()’ method.  Keys are section names, values are
          dictionaries with keys and values that should be present in
          the section.  If the used dictionary type preserves order,
          sections and their keys will be added in order.  Values are
          automatically converted to strings.

          Optional argument 'source' specifies a context-specific name
          of the dictionary passed.  If not given, ‘<dict>’ is used.

          This method can be used to copy state between parsers.

          在 3.2 版被加入.

      -- 方法: get (section, option, *, raw=False, vars=None[,
               fallback])

          Get an 'option' value for the named 'section'.  If 'vars' is
          provided, it must be a dictionary.  The 'option' is looked up
          in 'vars' (if provided), 'section', and in 'DEFAULTSECT' in
          that order.  If the key is not found and 'fallback' is
          provided, it is used as a fallback value.  ‘None’ can be
          provided as a 'fallback' value.

          All the ‘'%'’ interpolations are expanded in the return
          values, unless the 'raw' argument is true.  Values for
          interpolation keys are looked up in the same manner as the
          option.

          在 3.2 版的變更: Arguments 'raw', 'vars' and 'fallback' are
          keyword only to protect users from trying to use the third
          argument as the 'fallback' fallback (especially when using the
          mapping protocol).

      -- 方法: getint (section, option, *, raw=False, vars=None[,
               fallback])

          A convenience method which coerces the 'option' in the
          specified 'section' to an integer.  See *note get(): 1204. for
          explanation of 'raw', 'vars' and 'fallback'.

      -- 方法: getfloat (section, option, *, raw=False, vars=None[,
               fallback])

          A convenience method which coerces the 'option' in the
          specified 'section' to a floating-point number.  See *note
          get(): 1204. for explanation of 'raw', 'vars' and 'fallback'.

      -- 方法: getboolean (section, option, *, raw=False, vars=None[,
               fallback])

          A convenience method which coerces the 'option' in the
          specified 'section' to a Boolean value.  Note that the
          accepted values for the option are ‘'1'’, ‘'yes'’, ‘'true'’,
          and ‘'on'’, which cause this method to return ‘True’, and
          ‘'0'’, ‘'no'’, ‘'false'’, and ‘'off'’, which cause it to
          return ‘False’.  These string values are checked in a
          case-insensitive manner.  Any other value will cause it to
          raise *note ValueError: 1e7.  See *note get(): 1204. for
          explanation of 'raw', 'vars' and 'fallback'.

      -- 方法: items (raw=False, vars=None)

      -- 方法: items (section, raw=False, vars=None)

          When 'section' is not given, return a list of 'section_name',
          'section_proxy' pairs, including DEFAULTSECT.

          Otherwise, return a list of 'name', 'value' pairs for the
          options in the given 'section'.  Optional arguments have the
          same meaning as for the *note get(): 1204. method.

          在 3.8 版的變更: Items present in 'vars' no longer appear in
          the result.  The previous behaviour mixed actual parser
          options with variables provided for interpolation.

      -- 方法: set (section, option, value)

          If the given section exists, set the given option to the
          specified value; otherwise raise *note NoSectionError: 297d.
          'option' and 'value' must be strings; if not, *note TypeError:
          4dd. is raised.

      -- 方法: write (fileobject, space_around_delimiters=True)

          Write a representation of the configuration to the specified
          *note file object: 115b, which must be opened in text mode
          (accepting strings).  This representation can be parsed by a
          future *note read(): 13d3. call.  If 'space_around_delimiters'
          is true, delimiters between keys and values are surrounded by
          spaces.

          備註: Comments in the original configuration file are not
          preserved when writing the configuration back.  What is
          considered a comment, depends on the given values for
          'comment_prefix' and 'inline_comment_prefix'.

      -- 方法: remove_option (section, option)

          Remove the specified 'option' from the specified 'section'.
          If the section does not exist, raise *note NoSectionError:
          297d.  If the option existed to be removed, return *note True:
          bb4.; otherwise return *note False: adb.

      -- 方法: remove_section (section)

          Remove the specified 'section' from the configuration.  If the
          section in fact existed, return ‘True’.  Otherwise return
          ‘False’.

      -- 方法: optionxform (option)

          Transforms the option name 'option' as found in an input file
          or as passed in by client code to the form that should be used
          in the internal structures.  The default implementation
          returns a lower-case version of 'option'; subclasses may
          override this or client code can set an attribute of this name
          on instances to affect this behavior.

          You don't need to subclass the parser to use this method, you
          can also set it on an instance, to a function that takes a
          string argument and returns a string.  Setting it to ‘str’,
          for example, would make option names case sensitive:

               cfgparser = ConfigParser()
               cfgparser.optionxform = str

          Note that when reading configuration files, whitespace around
          the option names is stripped before *note optionxform(): 2975.
          is called.

 -- 資料: configparser.UNNAMED_SECTION

     A special object representing a section name used to reference the
     unnamed section (see *note Unnamed Sections: 296c.).

 -- 資料: configparser.MAX_INTERPOLATION_DEPTH

     The maximum depth for recursive interpolation for *note get():
     1204. when the 'raw' parameter is false.  This is relevant only
     when the default 'interpolation' is used.


File: python.info,  Node: RawConfigParser 物件,  Next: 例外<5>,  Prev: ConfigParser 物件,  Up: configparser --- 設定檔剖析器

5.14.2.11 RawConfigParser 物件
..............................

 -- 類別: configparser.RawConfigParser (defaults=None, dict_type=dict,
          allow_no_value=False, *, delimiters=('=', ':'),
          comment_prefixes=('#', ';'), inline_comment_prefixes=None,
          strict=True, empty_lines_in_values=True,
          default_section=configparser.DEFAULTSECT[, interpolation])

     Legacy variant of the *note ConfigParser: 1aa.  It has
     interpolation disabled by default and allows for non-string section
     names, option names, and values via its unsafe ‘add_section’ and
     ‘set’ methods, as well as the legacy ‘defaults=’ keyword argument
     handling.

     在 3.8 版的變更: The default 'dict_type' is *note dict: 23b, since
     it now preserves insertion order.

          備註: Consider using *note ConfigParser: 1aa. instead which
          checks types of the values to be stored internally.  If you
          don't want interpolation, you can use
          ‘ConfigParser(interpolation=None)’.

      -- 方法: add_section (section)

          Add a section named 'section' to the instance.  If a section
          by the given name already exists, *note DuplicateSectionError:
          1207. is raised.  If the 'default section' name is passed,
          *note ValueError: 1e7. is raised.

          Type of 'section' is not checked which lets users create
          non-string named sections.  This behaviour is unsupported and
          may cause internal errors.

      -- 方法: set (section, option, value)

          If the given section exists, set the given option to the
          specified value; otherwise raise *note NoSectionError: 297d.
          While it is possible to use *note RawConfigParser: f07. (or
          *note ConfigParser: 1aa. with 'raw' parameters set to true)
          for 'internal' storage of non-string values, full
          functionality (including interpolation and output to files)
          can only be achieved using string values.

          This method lets users assign non-string values to keys
          internally.  This behaviour is unsupported and will cause
          errors when attempting to write to a file or get it in non-raw
          mode.  'Use the mapping protocol API' which does not allow
          such assignments to take place.


File: python.info,  Node: 例外<5>,  Prev: RawConfigParser 物件,  Up: configparser --- 設定檔剖析器

5.14.2.12 例外
..............

 -- 例外: configparser.Error

     Base class for all other *note configparser: 1b. exceptions.

 -- 例外: configparser.NoSectionError

     Exception raised when a specified section is not found.

 -- 例外: configparser.DuplicateSectionError

     Exception raised if *note add_section(): 1206. is called with the
     name of a section that is already present or in strict parsers when
     a section if found more than once in a single input file, string or
     dictionary.

     在 3.2 版的變更: Added the optional 'source' and 'lineno'
     attributes and parameters to ‘__init__()’.

 -- 例外: configparser.DuplicateOptionError

     Exception raised by strict parsers if a single option appears twice
     during reading from a single file, string or dictionary.  This
     catches misspellings and case sensitivity-related errors, e.g.  a
     dictionary may have two keys representing the same case-insensitive
     configuration key.

 -- 例外: configparser.NoOptionError

     Exception raised when a specified option is not found in the
     specified section.

 -- 例外: configparser.InterpolationError

     Base class for exceptions raised when problems occur performing
     string interpolation.

 -- 例外: configparser.InterpolationDepthError

     Exception raised when string interpolation cannot be completed
     because the number of iterations exceeds *note
     MAX_INTERPOLATION_DEPTH: 2980.  Subclass of *note
     InterpolationError: 2988.

 -- 例外: configparser.InterpolationMissingOptionError

     Exception raised when an option referenced from a value does not
     exist.  Subclass of *note InterpolationError: 2988.

 -- 例外: configparser.InterpolationSyntaxError

     Exception raised when the source text into which substitutions are
     made does not conform to the required syntax.  Subclass of *note
     InterpolationError: 2988.

 -- 例外: configparser.MissingSectionHeaderError

     Exception raised when attempting to parse a file which has no
     section headers.

 -- 例外: configparser.ParsingError

     Exception raised when errors occur attempting to parse a file.

     在 3.12 版的變更: The ‘filename’ attribute and ‘__init__()’
     constructor argument were removed.  They have been available using
     the name ‘source’ since 3.2.

 -- 例外: configparser.MultilineContinuationError

     Exception raised when a key without a corresponding value is
     continued with an indented line.

     在 3.13 版被加入.

註解
....


File: python.info,  Node: tomllib --- 剖析 TOML 檔案,  Next: netrc --- netrc 檔案處理,  Prev: configparser --- 設定檔剖析器,  Up: 檔案格式

5.14.3 ‘tomllib’ -- 剖析 TOML 檔案
----------------------------------

在 3.11 版被加入.

'原始碼：'Lib/tomllib(1)

__________________________________________________________________

This module provides an interface for parsing TOML (Tom's Obvious
Minimal Language, https://toml.io(2)).  This module does not support
writing TOML.

也參考
......

Tomli-W 套件(3)是一個 TOML 編寫器，可以與此模組結合使用，以提供標準函式
庫中 *note marshal: 80. 和 *note pickle: 95. 模組之使用者所熟悉的寫入
API。

也參考
......

TOML 工具套件(4)是一個保留風格且具有讀寫能力的 TOML 函式庫。若要編輯已存
在的 TOML 文件，建議用它來替換此模組。

此模組定義了以下函式：

 -- 函式: tomllib.load (fp, /, *, parse_float=float)

     讀取一個 TOML 檔案。第一個引數應為一個可讀取的二進位檔案物件。回傳
     一個 *note dict: 23b.。用這個*note 轉換表: 2990.將 TOML 型別轉換成
     Python 的。

     'parse_float' 會被呼叫於要解碼的每個 TOML 浮點數字串。預設情況下，
     這相當於 ‘float(num_str)’。若有使用另一種資料型別或剖析器的 TOML 浮
     點數（例如 *note decimal.Decimal: 27c.），這就派得上用場。可呼叫物
     件不得回傳 *note dict: 23b. 或 *note list: 5b6.，否則會引發 *note
     ValueError: 1e7.。

     不合格的 TOML 文件會使得 *note TOMLDecodeError: 2991. 被引發。

 -- 函式: tomllib.loads (s, /, *, parse_float=float)

     自一個 *note str: 3f2. 物件載入成 TOML。回傳一個 *note dict: 23b.。
     用這個*note 轉換表: 2990.轉換 TOML 型別成 Python 的。'parse_float'
     引數和 *note load(): 298f. 中的相同。

     不合格的 TOML 文件會使得 *note TOMLDecodeError: 2991. 被引發。

以下為可用的例外：

 -- 例外: tomllib.TOMLDecodeError

     *note ValueError: 1e7. 的子類別。

* Menu:

* 範例: 範例<15>.
* 轉換表::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/tomllib

   (2) https://toml.io/en/

   (3) https://pypi.org/project/tomli-w/

   (4) https://pypi.org/project/tomlkit/


File: python.info,  Node: 範例<15>,  Next: 轉換表,  Up: tomllib --- 剖析 TOML 檔案

5.14.3.1 範例
.............

剖析一個 TOML 檔案：

     import tomllib

     with open("pyproject.toml", "rb") as f:
         data = tomllib.load(f)

剖析一個 TOML 字串：

     import tomllib

     toml_str = """
     python-version = "3.11.0"
     python-implementation = "CPython"
     """

     data = tomllib.loads(toml_str)


File: python.info,  Node: 轉換表,  Prev: 範例<15>,  Up: tomllib --- 剖析 TOML 檔案

5.14.3.2 轉換表
...............

TOML                   Python
                       
------------------------------------------------------------------------------------------------------------------
                       
TOML 文件              dict
                       
                       
string                 str
                       
                       
integer                int
                       
                       
float                  float（可透過 'parse_float' 調整）
                       
                       
boolean                bool
                       
                       
偏移日期時間 (offset   datetime.datetime（設定 ‘tzinfo’ 屬性為 ‘datetime.timezone’ 的實例）
date-time)             

本地日期時間 (local    datetime.datetime（設定 ‘tzinfo’ 為 ‘None’）
date-time)             

本地日期 (local        datetime.date
date)                  

本地時間 (local        datetime.time
time)                  

array                  list
                       
                       
table                  dict
                       
                       
行內表格 (inline       dict
table)                 

表格陣列 (array of     dict 串列 (list of dicts)
tables)                


File: python.info,  Node: netrc --- netrc 檔案處理,  Next: plistlib --- 產生和剖析 Apple plist 檔案,  Prev: tomllib --- 剖析 TOML 檔案,  Up: 檔案格式

5.14.4 ‘netrc’ -- netrc 檔案處理
--------------------------------

'原始碼：'Lib/netrc.py(1)

__________________________________________________________________

*note netrc: 17c4. 類別能夠剖析 (parse) 並封裝 (encapsulate) netrc 檔案
格式，以供 Unix ‘ftp’ 程式和其他 FTP 用戶端使用。

 -- 類別: netrc.netrc ([file])

     *note netrc: 17c4. 實例或其子類別實例能夠封裝來自 netrc 檔案的資料
     。可用初始化引數（如有給定）指定要剖析的檔案，如果未給定引數，則將
     讀取（由 *note os.path.expanduser(): 9b8. 指定的）使用者主目錄中的
     ‘.netrc’ 檔案，否則將引發 *note FileNotFoundError: e67. 例外。剖析
     錯誤會引發 *note NetrcParseError: 2997.，其帶有包括檔案名稱、列號和
     終止 token 的診斷資訊。如果在 POSIX 系統上未指定引數，且若檔案所有
     權或權限不安全（擁有者與運行該行程的使用者不同，或者可供任何其他使
     用者讀取或寫入），存有密碼的 ‘.netrc’ 檔案將會引發 *note
     NetrcParseError: 2997.。這實作了與 ftp 和其他使用 ‘.netrc’ 程式等效
     的安全行為。

     在 3.4 版的變更: 新增了 POSIX 權限檢查。

     在 3.7 版的變更: 當未傳遞 'file' 引數時，*note
     os.path.expanduser(): 9b8. 可用於查找 ‘.netrc’ 檔案的位置。

     在 3.10 版的變更: *note netrc: 8d. 在使用特定語言環境編碼前會先嘗試
     UTF-8 編碼。netrc 檔案中的條目就不再需要包含所有 token，缺少的
     token 值被預設為空字串。現在所有 token 及其值都可以包含任意字元，例
     如空格和非 ASCII 字元。如果登入名稱為匿名，就不會觸發安全檢查。

 -- 例外: netrc.NetrcParseError

     當原始文本中遇到語法錯誤時，*note netrc: 17c4. 類別會引發例外。此例
     外的實例提供了三個有趣的屬性：

      -- 屬性: msg

          錯誤的文字解釋。

      -- 屬性: filename

          原始檔案的名稱。

      -- 屬性: lineno

          發現錯誤的列號。

* Menu:

* netrc 物件::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/netrc.py


File: python.info,  Node: netrc 物件,  Up: netrc --- netrc 檔案處理

5.14.4.1 netrc 物件
...................

*note netrc: 17c4. 實例具有以下方法：

 -- 方法: netrc.authenticators (host)

     回傳 'host' 身份驗證器的三元素 tuple ‘(login, account, password)’。
     如果 netrc 檔案不包含給定主機的條目，則回傳與 'default' 條目關聯的
     tuple。如果並無匹配主機且預設條目也不可用則回傳 ‘None’。

 -- 方法: netrc.__repr__ ()

     將類別資料傾印 (dump) 為 netrc 檔案格式的字串。（這會將註解移除，並
     可能會對條目重新排序。）

*note netrc: 17c4. 的實例具有公開實例變數：

 -- 屬性: netrc.hosts

     將主機名稱對映到 ‘(login, account, password)’ tuple 的字典。
     'default' 條目（如存在）表示為該名稱對應到的偽主機 (pseudo-host)。

 -- 屬性: netrc.macros

     巨集 (macro) 名稱與字串 list（串列）的對映字典。


File: python.info,  Node: plistlib --- 產生和剖析 Apple plist 檔案,  Prev: netrc --- netrc 檔案處理,  Up: 檔案格式

5.14.5 ‘plistlib’ -- 產生和剖析 Apple ‘.plist’ 檔案
---------------------------------------------------

'原始碼：'Lib/plistlib.py(1)

__________________________________________________________________

This module provides an interface for reading and writing the "property
list" files used by Apple, primarily on macOS and iOS. This module
supports both binary and XML plist files.

The property list (‘.plist’) file format is a simple serialization
supporting basic object types, like dictionaries, lists, numbers and
strings.  Usually the top level object is a dictionary.

To write out and to parse a plist file, use the *note dump(): 8f5. and
*note load(): 8f3. functions.

To work with plist data in bytes or string objects, use *note dumps():
8f6. and *note loads(): 8f4.

Values can be strings, integers, floats, booleans, tuples, lists,
dictionaries (but only with string keys), *note bytes: 1a5, *note
bytearray: 4e3. or *note datetime.datetime: 1b0. objects.

在 3.4 版的變更: New API, old API deprecated.  Support for binary format
plists added.

在 3.8 版的變更: Support added for reading and writing *note UID: 9c5.
tokens in binary plists as used by NSKeyedArchiver and
NSKeyedUnarchiver.

在 3.9 版的變更: Old API removed.

也參考
......

PList manual page(2)

     Apple's documentation of the file format.

This module defines the following functions:

 -- 函式: plistlib.load (fp, *, fmt=None, dict_type=dict,
          aware_datetime=False)

     Read a plist file.  'fp' should be a readable and binary file
     object.  Return the unpacked root object (which usually is a
     dictionary).

     The 'fmt' is the format of the file and the following values are
     valid:

        * *note None: 61b.: Autodetect the file format

        * *note FMT_XML: f1c.: XML file format

        * *note FMT_BINARY: f1d.: Binary plist format

     The 'dict_type' is the type used for dictionaries that are read
     from the plist file.

     When 'aware_datetime' is true, fields with type ‘datetime.datetime’
     will be created as *note aware object: 2302, with ‘tzinfo’ as *note
     datetime.UTC: 496.

     XML data for the *note FMT_XML: f1c. format is parsed using the
     Expat parser from *note xml.parsers.expat: 10d. - see its
     documentation for possible exceptions on ill-formed XML. Unknown
     elements will simply be ignored by the plist parser.

     The parser for the binary format raises ‘InvalidFileException’ when
     the file cannot be parsed.

     在 3.4 版被加入.

     在 3.13 版的變更: The keyword-only parameter 'aware_datetime' has
     been added.

 -- 函式: plistlib.loads (data, *, fmt=None, dict_type=dict,
          aware_datetime=False)

     Load a plist from a bytes or string object.  See *note load(): 8f3.
     for an explanation of the keyword arguments.

     在 3.4 版被加入.

     在 3.13 版的變更: 'data' can be a string when 'fmt' equals *note
     FMT_XML: f1c.

 -- 函式: plistlib.dump (value, fp, *, fmt=FMT_XML, sort_keys=True,
          skipkeys=False, aware_datetime=False)

     Write 'value' to a plist file.  'Fp' should be a writable, binary
     file object.

     The 'fmt' argument specifies the format of the plist file and can
     be one of the following values:

        * *note FMT_XML: f1c.: XML formatted plist file

        * *note FMT_BINARY: f1d.: Binary formatted plist file

     When 'sort_keys' is true (the default) the keys for dictionaries
     will be written to the plist in sorted order, otherwise they will
     be written in the iteration order of the dictionary.

     When 'skipkeys' is false (the default) the function raises *note
     TypeError: 4dd. when a key of a dictionary is not a string,
     otherwise such keys are skipped.

     When 'aware_datetime' is true and any field with type
     ‘datetime.datetime’ is set as an *note aware object: 2302, it will
     convert to UTC timezone before writing it.

     A *note TypeError: 4dd. will be raised if the object is of an
     unsupported type or a container that contains objects of
     unsupported types.

     An *note OverflowError: 825. will be raised for integer values that
     cannot be represented in (binary) plist files.

     在 3.4 版被加入.

     在 3.13 版的變更: The keyword-only parameter 'aware_datetime' has
     been added.

 -- 函式: plistlib.dumps (value, *, fmt=FMT_XML, sort_keys=True,
          skipkeys=False, aware_datetime=False)

     Return 'value' as a plist-formatted bytes object.  See the
     documentation for *note dump(): 8f5. for an explanation of the
     keyword arguments of this function.

     在 3.4 版被加入.

The following classes are available:

 -- 類別: plistlib.UID (data)

     Wraps an *note int: 23c.  This is used when reading or writing
     NSKeyedArchiver encoded data, which contains UID (see PList
     manual).

     It has one attribute, ‘data’, which can be used to retrieve the int
     value of the UID. ‘data’ must be in the range ‘0 <= data < 2**64’.

     在 3.8 版被加入.

The following constants are available:

 -- 資料: plistlib.FMT_XML

     The XML format for plist files.

     在 3.4 版被加入.

 -- 資料: plistlib.FMT_BINARY

     The binary format for plist files

     在 3.4 版被加入.

* Menu:

* 範例: 範例<16>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/plistlib.py

   (2) 
https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/PropertyLists/


File: python.info,  Node: 範例<16>,  Up: plistlib --- 產生和剖析 Apple plist 檔案

5.14.5.1 範例
.............

Generating a plist:

     import datetime
     import plistlib

     pl = dict(
         aString = "Doodah",
         aList = ["A", "B", 12, 32.1, [1, 2, 3]],
         aFloat = 0.1,
         anInt = 728,
         aDict = dict(
             anotherString = "<hello & hi there!>",
             aThirdString = "M\xe4ssig, Ma\xdf",
             aTrueValue = True,
             aFalseValue = False,
         ),
         someData = b"<binary gunk>",
         someMoreData = b"<lots of binary gunk>" * 10,
         aDate = datetime.datetime.now()
     )
     print(plistlib.dumps(pl).decode())

Parsing a plist:

     import plistlib

     plist = b"""<plist version="1.0">
     <dict>
         <key>foo</key>
         <string>bar</string>
     </dict>
     </plist>"""
     pl = plistlib.loads(plist)
     print(pl["foo"])


File: python.info,  Node: 加密服務,  Next: 通用作業系統服務,  Prev: 檔案格式,  Up: Python 標準函式庫 Standard Library

5.15 加密服務
=============

The modules described in this chapter implement various algorithms of a
cryptographic nature.  They are available at the discretion of the
installation.  Here's an overview:

* Menu:

* hashlib: hashlib --- 安全雜湊與訊息摘要. 安全雜湊與訊息摘要
* hmac: hmac --- 基於金鑰雜湊的訊息驗證. 基於金鑰雜湊的訊息驗證
* secrets: secrets --- 產生用於管理機密的安全亂數. 產生用於管理機密的安全亂數


File: python.info,  Node: hashlib --- 安全雜湊與訊息摘要,  Next: hmac --- 基於金鑰雜湊的訊息驗證,  Up: 加密服務

5.15.1 ‘hashlib’ -- 安全雜湊與訊息摘要
--------------------------------------

'原始碼：'Lib/hashlib.py(1)

__________________________________________________________________

該模組實作了許多不同安全雜湊和訊息摘要演算法的通用介面，其中包括 FIPS 安
全雜湊演算法 SHA1、SHA224、SHA256、SHA384、SHA512（定義於 FIPS 180-4 標
準(2)）、SHA-3 系列（定義於 FIPS 202 標準(3)）以及 RSA 的 MD5 演算法（定
義於網際網路 RFC 1321(4)）。「安全雜湊 (secure hash)」和「訊息摘要
(message digest)」這兩個術語是可以互換的。較舊的演算法稱為訊息摘要、現代
則較常稱之安全雜湊。

     備註: 如果你需要 adler32 或 crc32 雜湊函式，可以在 *note zlib: 119.
     模組中找到它們。

* Menu:

* 雜湊演算法::
* 用法::
* 建構函式::
* 屬性::
* 雜湊物件::
* SHAKE 可變長度摘要::
* 檔案雜湊::
* 密鑰的生成::
* BLAKE2::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/hashlib.py

   (2) https://csrc.nist.gov/publications/detail/fips/180/4/final

   (3) https://csrc.nist.gov/publications/detail/fips/202/final

   (4) https://datatracker.ietf.org/doc/html/rfc1321.html


File: python.info,  Node: 雜湊演算法,  Next: 用法,  Up: hashlib --- 安全雜湊與訊息摘要

5.15.1.1 雜湊演算法
...................

每種種類的 'hash' 都有一個以其命名的建構函式方法。全部都會回傳具有相同簡
單介面的雜湊物件。例如：可使用 *note sha256(): 29ab. 來建立 SHA-256 雜湊
物件。現在你可以使用 *note update: 29ac. 方法向此物件提供*note
類位元組物件 (bytes-like objects): cd4.（通常是 *note bytes: 1a5.）。在
任何時候，你都可以使用 *note digest(): 29ad. 或 *note hexdigest(): 29ae.
方法來要求它提供迄今為止傳遞給它的資料串聯的'摘要 (digest)'。

為了允許多執行緒 (multithreading)，Python *note GIL: 13e. 被釋放，同時在
其建構函式或 *note .update: 29ac. 方法中計算一次提供超過 2047 位元組資料
的雜湊值。

此模組中始終存在的雜湊演算法之建構函式有 *note sha1(): 29af.、*note
sha224(): 29b0.、*note sha256(): 29ab.、*note sha384(): 29b1.、*note
sha512(): 29b2.、*note sha3_224(): c49.、*note sha3_256(): c4a.、*note
sha3_384(): c4b.、*note sha3_512(): c4c.、*note shake_128(): c4d.、*note
shake_256(): c4e.、*note blake2b(): 5e8. 和 *note blake2s(): 5e9.。*note
md5(): 29b3. 通常也可用，但如果你使用罕見的「符合 FIPS (FIPS compliant)」
的 Python 建置版本，它可能不存在或者不被允許使用。以上會對應到 *note
algorithms_guaranteed: 1300.。

如果你的 Python 發行版的 *note hashlib: 5e. 與提供其他演算法的 OpenSSL 版
本鏈結，也可能有其他演算法可用。其他則'不保證可用'於在所有安裝上，並且只
能以名稱來透過 *note new(): 1849. 存取。請參閱 *note
algorithms_available: 1301.。

     警告: 某些演算法具有已知的雜湊碰撞 (hash collision) 弱點（包括 MD5
     和 SHA1）。請參閱 Attacks on cryptographic hash algorithms(1) 和本
     文件後面的*note 也參考: 29b4.部分。

在 3.6 版被加入: 新增了 SHA3 (Keccak) 和 SHAKE 建構函式 *note
sha3_224(): c49.、*note sha3_256(): c4a.、*note sha3_384(): c4b.、*note
sha3_512(): c4c.、*note shake_128(): c4d.、*note shake_256(): c4e.。也新
增了 *note blake2b(): 5e8. 和 *note blake2s(): 5e9.。

在 3.9 版的變更: 所有 hashlib 建構函式都採用一個僅限關鍵字引數
(keyword-only argument) 'usedforsecurity'，其預設值為 ‘True’。False 值則
會允許在受限環境中使用不安全 (insecure) 和阻塞的 (blocked) 雜湊演算法。
‘False’ 表示雜湊演算法未在安全情境中使用，例如作為一種非加密用途的單向壓
縮函式。

在 3.9 版的變更: Hashlib 現在使用 OpenSSL 中的 SHA3 和 SHAKE（如果有提供
的話）。

在 3.12 版的變更: 對於鏈結之 OpenSSL 未提供的任何 MD5、SHA1、SHA2 或
SHA3 演算法，我們會回退使用 HACL* 專案(2)中經過驗證的實作。

   ---------- Footnotes ----------

   (1) 
https://en.wikipedia.org/wiki/Cryptographic_hash_function#Attacks_on_cryptographic_hash_algorithms

   (2) https://github.com/hacl-star/hacl-star


File: python.info,  Node: 用法,  Next: 建構函式,  Prev: 雜湊演算法,  Up: hashlib --- 安全雜湊與訊息摘要

5.15.1.2 用法
.............

獲取位元組字串 ‘b"Nobody inspects the spammish repetition"’ 的摘要：

     >>> import hashlib
     >>> m = hashlib.sha256()
     >>> m.update(b"Nobody inspects")
     >>> m.update(b" the spammish repetition")
     >>> m.digest()
     b'\x03\x1e\xdd}Ae\x15\x93\xc5\xfe\\\x00o\xa5u+7\xfd\xdf\xf7\xbcN\x84:\xa6\xaf\x0c\x95\x0fK\x94\x06'
     >>> m.hexdigest()
     '031edd7d41651593c5fe5c006fa5752b37fddff7bc4e843aa6af0c950f4b9406'

更濃縮：

     >>> hashlib.sha256(b"Nobody inspects the spammish repetition").hexdigest()
     '031edd7d41651593c5fe5c006fa5752b37fddff7bc4e843aa6af0c950f4b9406'


File: python.info,  Node: 建構函式,  Next: 屬性,  Prev: 用法,  Up: hashlib --- 安全雜湊與訊息摘要

5.15.1.3 建構函式
.................

 -- 函式: hashlib.new (name[, data], *, usedforsecurity=True)

     是一個通用建構函式，它將目標演算法的字串 'name' 作為其第一個參數。
     它還允許使用者取得上面列出的雜湊值以及 OpenSSL 函式庫可能提供的任何
     其他演算法。

使用 *note new(): 1849. 和演算法名稱：

     >>> h = hashlib.new('sha256')
     >>> h.update(b"Nobody inspects the spammish repetition")
     >>> h.hexdigest()
     '031edd7d41651593c5fe5c006fa5752b37fddff7bc4e843aa6af0c950f4b9406'

 -- 函式: hashlib.md5 ([data], *, usedforsecurity=True)

 -- 函式: hashlib.sha1 ([data], *, usedforsecurity=True)

 -- 函式: hashlib.sha224 ([data], *, usedforsecurity=True)

 -- 函式: hashlib.sha256 ([data], *, usedforsecurity=True)

 -- 函式: hashlib.sha384 ([data], *, usedforsecurity=True)

 -- 函式: hashlib.sha512 ([data], *, usedforsecurity=True)

 -- 函式: hashlib.sha3_224 ([data], *, usedforsecurity=True)

 -- 函式: hashlib.sha3_256 ([data], *, usedforsecurity=True)

 -- 函式: hashlib.sha3_384 ([data], *, usedforsecurity=True)

 -- 函式: hashlib.sha3_512 ([data], *, usedforsecurity=True)

諸如此類的附名建構函式比將演算法名稱傳遞給 *note new(): 1849. 更快。


File: python.info,  Node: 屬性,  Next: 雜湊物件,  Prev: 建構函式,  Up: hashlib --- 安全雜湊與訊息摘要

5.15.1.4 屬性
.............

Hashlib 提供以下常數模組屬性：

 -- 資料: hashlib.algorithms_guaranteed

     包含所有平台上該模組保證支援的雜湊演算法名稱的集合。請注意，'md5' 有
     出現在此列表中，儘管有一些上游供應商提供了奇怪的「符合 FIPS (FIPS
     compliant)」的 Python 建置，並將其排除在外。

     在 3.2 版被加入.

 -- 資料: hashlib.algorithms_available

     包含正在運行的 Python 直譯器中可用的雜湊演算法名稱的集合。這些名稱
     在傳遞給 *note new(): 1849. 時將被識別。*note
     algorithms_guaranteed: 1300. 都會是它的一個子集。相同的演算法可能會
     以不同的名稱多次出現在該集合中（多虧了 OpenSSL）。

     在 3.2 版被加入.


File: python.info,  Node: 雜湊物件,  Next: SHAKE 可變長度摘要,  Prev: 屬性,  Up: hashlib --- 安全雜湊與訊息摘要

5.15.1.5 雜湊物件
.................

以下的值皆為建構函式回傳之雜湊物件的常數屬性：

 -- 資料: hash.digest_size

     生成雜湊的大小（以位元組為單位）。

 -- 資料: hash.block_size

     雜湊演算法的內部區塊大小（以位元組為單位）。

雜湊物件具有以下屬性：

 -- 屬性: hash.name

     該雜湊的規範名稱，都會是小寫，且都會適合作為 *note new(): 1849. 的
     參數以建立此型別的另一個雜湊。

     在 3.4 版的變更: name 屬性自 CPython 誕生以來就存在於其中，但直到
     Python 3.4 才正式確立，因此在某些平台上可能不存在。

雜湊物件具有以下方法：

 -- 方法: hash.update (data)

     使用*note 類位元組物件: cd4.來更新雜湊物件。重複呼叫相當於連接所有
     引數的單一呼叫：‘m.update(a); m.update(b)’ 等價於 ‘m.update(a+b)’。

 -- 方法: hash.digest ()

     回傳目前有傳遞給 *note update(): 29ac. 方法的資料之摘要。這是一個大
     小為 *note digest_size: 29ba. 的位元組物件，它可能包含從 0 到 255 的
     整個範圍內的位元組。

 -- 方法: hash.hexdigest ()

     與 *note digest(): 29ad. 類似，只不過摘要會是作為雙倍長度的字串物件
     回傳，僅包含十六進位數字。這可用於在電子郵件或其他非二進位環境中安
     全地交換值。

 -- 方法: hash.copy ()

     回傳雜湊物件的副本（「複製 (clone)」），這可用於高效率地計算出共享
     同一初始子字串的資料之摘要。


File: python.info,  Node: SHAKE 可變長度摘要,  Next: 檔案雜湊,  Prev: 雜湊物件,  Up: hashlib --- 安全雜湊與訊息摘要

5.15.1.6 SHAKE 可變長度摘要
...........................

 -- 函式: hashlib.shake_128 ([data], *, usedforsecurity=True)

 -- 函式: hashlib.shake_256 ([data], *, usedforsecurity=True)

*note shake_128(): c4d. 和 *note shake_256(): c4e. 演算法提供了可變長度
摘要，其 length_in_bits//2 最高為 128 或 256 位元安全性。因此，他們的摘
要方法會需要長度。最大長度不受 SHAKE 演算法限制。

 -- 方法: shake.digest (length)

     回傳目前有傳遞給 *note update(): 29ac. 方法的資料之摘要。這是一個大
     小為 'length' 的位元組物件，可能包含從 0 到 255 的整個範圍內的位元
     組。

 -- 方法: shake.hexdigest (length)

     與 *note digest(): 193f. 類似，只不過摘要作為雙倍長度的字串物件回傳
     ，僅包含十六進位數字。這可用於交換電子郵件或其他非二進位環境中的值
     。

範例：

     >>> h = hashlib.shake_256(b'Nobody inspects the spammish repetition')
     >>> h.hexdigest(20)
     '44709d6fcb83d92a76dcb0b668c98e1b1d3dafe7'


File: python.info,  Node: 檔案雜湊,  Next: 密鑰的生成,  Prev: SHAKE 可變長度摘要,  Up: hashlib --- 安全雜湊與訊息摘要

5.15.1.7 檔案雜湊
.................

hashlib 模組提供了一個輔助函式，用於對檔案或類檔案物件 (file-like
object) 進行有效率的雜湊。

 -- 函式: hashlib.file_digest (fileobj, digest, /)

     回傳已用檔案物件內容更新的摘要物件。

     'fileobj' 必須是以二進位模式讀取的類檔案物件。它接受來自內建 *note
     open(): 4c0. 的檔案物件、*note BytesIO: e46. 實例、來自 *note
     socket.socket.makefile(): 1137. 的 SocketIO 物件等。該函式可以繞過
     Python 的 I/O 並直接使用 *note fileno(): 2732. 中的檔案描述器 (file
     descriptor)。在此函式回傳或引發後，必須假定 'fileobj' 處於未知狀態
     (unknown state)。由呼叫者決定是否關閉 'fileobj'。

     'digest' 必須是名稱作為 'str' 的雜湊演算法、雜湊建構函式或會回傳雜
     湊物件的可呼叫函式。

     範例：

          >>> import io, hashlib, hmac
          >>> with open(hashlib.__file__, "rb") as f:
          ...     digest = hashlib.file_digest(f, "sha256")
          ...
          >>> digest.hexdigest()
          '...'

          >>> buf = io.BytesIO(b"somedata")
          >>> mac1 = hmac.HMAC(b"key", digestmod=hashlib.sha512)
          >>> digest = hashlib.file_digest(buf, lambda: mac1)

          >>> digest is mac1
          True
          >>> mac2 = hmac.HMAC(b"key", b"somedata", digestmod=hashlib.sha512)
          >>> mac1.digest() == mac2.digest()
          True

     在 3.11 版被加入.


File: python.info,  Node: 密鑰的生成,  Next: BLAKE2,  Prev: 檔案雜湊,  Up: hashlib --- 安全雜湊與訊息摘要

5.15.1.8 密鑰的生成
...................

密鑰生成 (key derivation) 和密鑰延伸 (key stretching) 演算法專為安全密碼
雜湊而設計。像是 ‘sha1(password)’ 這樣過於單純的演算法無法抵抗暴力攻擊。
一個好的密碼雜湊函式必須是可調校的 (tunable)、緩慢的，並且有包含 salt（
鹽）(1)。

 -- 函式: hashlib.pbkdf2_hmac (hash_name, password, salt, iterations,
          dklen=None)

     該函式提供基於密碼的 PKCS#5 密鑰生成函式 2。它使用 HMAC 作為偽隨機
     函式 (pseudorandom function)。

     字串 'hash_name' 是 HMAC 的雜湊摘要演算法所需的名稱，例如 ‘sha1’ 或
     ‘sha256’。'password' 和 'salt' 被直譯為位元組緩衝區。應用程式和函式
     庫應為 'password' 設下合理的長度限制（例如 1024）。'salt' 應該是來
     自適當來源（例如 *note os.urandom(): 4c7.）且大約 16 或更多位元組。

     應根據雜湊演算法和計算能力選擇 'iterations' 次數。截至 2022 年，建
     議進行數十萬次 SHA-256 疊代。有關為什麼以及如何選擇最適合你的應用程
     式的基本原理，請閱讀 NIST-SP-800-132(2) 的 'Appendix A.2.2'。
     stackexchange pbkdf2 疊代問題(3)上的答案有詳細解釋。

     'dklen' 是生成的密鑰長度。如果 'dklen' 為 ‘None’，則會使用雜湊演算
     法 'hash_name' 的摘要大小，例如 SHA-512 為 64。

          >>> from hashlib import pbkdf2_hmac
          >>> our_app_iters = 500_000  # Application specific, read above.
          >>> dk = pbkdf2_hmac('sha256', b'password', b'bad salt' * 2, our_app_iters)
          >>> dk.hex()
          '15530bba69924174860db778f2c6f8104d3aaf9d26241840c8c4a641c8d000a9'

     僅當有使用 OpenSSL 編譯 Python 時該函式才可用。

     在 3.4 版被加入.

     在 3.12 版的變更: 該函式現在僅在有使用 OpenSSL 建置 Python 時可用。
     緩慢的純 Python 實作已被刪除。

 -- 函式: hashlib.scrypt (password, *, salt, n, r, p, maxmem=0,
          dklen=64)

     該函式提供（如 RFC 7914(4) 中所定義的）scrypt 基於密碼的密鑰衍生函
     式。

     'password' 和 'salt' 必須是*note 類位元組物件: cd4.。應用程式和函式
     庫應為 'password' 設下合理的長度限制（例如 1024）。'salt' 應該是來
     自適當來源（例如 *note os.urandom(): 4c7.）且大約 16 或更多位元組。

     'n' 是 CPU/記憶體開銷係數、'r' 是區塊大小、'p' 為平行化係數、
     'maxmem' 為記憶體限制（OpenSSL 1.1.0 預設為 32 MiB）。'dklen' 是生
     成密鑰的長度。

     在 3.6 版被加入.

   ---------- Footnotes ----------

   (1) 
https://zh.wikipedia.org/zh-tw/%E7%9B%90_(%E5%AF%86%E7%A0%81%E5%AD%A6)

   (2) 
https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-132.pdf

   (3) 
https://security.stackexchange.com/questions/3959/recommended-of-iterations-when-using-pbkdf2-sha256/

   (4) https://datatracker.ietf.org/doc/html/rfc7914.html


File: python.info,  Node: BLAKE2,  Prev: 密鑰的生成,  Up: hashlib --- 安全雜湊與訊息摘要

5.15.1.9 BLAKE2
...............

BLAKE2(1) 是在 RFC 7693(2) 中定義的加密雜湊函式，有兩種類型：

   * 'BLAKE2b'，針對 64 位元平台進行了最佳化，可生成 1 到 64 位元組之間
     任意大小的摘要，

   * 'BLAKE2s'，針對 8 至 32 位元平台進行了最佳化，可生成 1 至 32 位元組
     之間任意大小的摘要。

BLAKE2 支援'密鑰模式 (keyed mode)' （更快、更簡單的 HMAC(3) 替代品）、
'加鹽雜湊 (salted hashing)'、'個人化'和'樹狀雜湊'。

該模組中的雜湊物件遵循標準函式庫的 *note hashlib: 5e. 物件 API。

* Menu:

* 建立雜湊物件::
* 常數: 常數<5>.
* 範例: 範例<17>.
* 製作人員::

   ---------- Footnotes ----------

   (1) https://www.blake2.net

   (2) https://datatracker.ietf.org/doc/html/rfc7693.html

   (3) 
https://en.wikipedia.org/wiki/Hash-based_message_authentication_code


File: python.info,  Node: 建立雜湊物件,  Next: 常數<5>,  Up: BLAKE2

5.15.1.10 建立雜湊物件
......................

新的雜湊物件是透過呼叫建構函式建立的：

 -- 函式: hashlib.blake2b (data=b'', *, digest_size=64, key=b'',
          salt=b'', person=b'', fanout=1, depth=1, leaf_size=0,
          node_offset=0, node_depth=0, inner_size=0, last_node=False,
          usedforsecurity=True)

 -- 函式: hashlib.blake2s (data=b'', *, digest_size=32, key=b'',
          salt=b'', person=b'', fanout=1, depth=1, leaf_size=0,
          node_offset=0, node_depth=0, inner_size=0, last_node=False,
          usedforsecurity=True)

這些函式回傳相應的雜湊物件以計算 BLAKE2b 或 BLAKE2s。他們可以選擇採用這
些通用參數：

   * 'data'：要雜湊的初始資料塊 (data chunk)，它必須是*note
     類位元組物件: cd4.。它只能作為位置引數傳遞。

   * 'digest_size'：輸出摘要的大小（以位元組為單位）。

   * 'key'：用於密鑰雜湊的密鑰（BLAKE2b 最多 64 位元組、BLAKE2s 最多 32
     位元組）。

   * 'salt'：用於隨機雜湊的鹽（BLAKE2b 最多 16 個位元組、BLAKE2s 最多 8
     個位元組）。

   * 'person'：個人化字串（BLAKE2b 最多 16 個位元組、BLAKE2s 最多 8 個位
     元組）。

下表顯示了一般參數的限制（以位元組為單位）：

雜湊        digest_size     len(key)     len(salt)     len(person)
                                                       
-----------------------------------------------------------------------
                                                       
BLAKE2b     64              64           16            16
                                                       
                                                       
BLAKE2s     32              32           8             8
                                                       

     備註: BLAKE2 規範定義了鹽和個人化參數的恆定長度，但為了方便起見，此
     實作接受任意大小的位元組字串，最多可達指定長度。如果參數的長度小於
     指定的長度，則用零補滿，所以像是 ‘b'salt’ 和 ‘b'salt\x00’ 是相同的
     值。（但 'key' 的情況並非如此。）

這些大小可作為模組*note 常數: 29c2.使用，如下所述。

建構函式還接受以下樹狀雜湊參數：

   * 'fanout'：扇出（0 到 255，如果無限制則為 0、順序模式為 1）。

   * 'depth'：樹的最大深度（1 到 255，如果無限制則為 255、順序模式為 1）
     。

   * 'leaf_size'：葉的最大位元組長度（0 到 ‘2**32-1’，如果無限制或處於順
     序模式則為 0）。

   * 'node_offset'：節點偏移量（BLAKE2b 為 0 到 ‘2**64-1’，BLAKE2s 為 0
     到 ‘2**48-1’，0 表示第一個、最左邊、葉子或在順序模式下）。

   * 'node_depth'：節點深度（0 到 255，葉為 0，或在順序模式下）。

   * 'inner_size'：內部摘要大小（BLAKE2b 為 0 到 64，BLAKE2s 為 0 到 32，
     順序模式為 0）。

   * 'last_node'：布林值，代表處理的節點是否為最後一個（‘False’ 代表順序
     模式）。

[image src="python-figures/hashlib-blake2-tree.png" alt="樹狀模式參數說明。"]


Figure
關於樹狀雜湊的綜合回顧，請參閱 BLAKE2 規範(1)中的第 2.10 節。

   ---------- Footnotes ----------

   (1) https://www.blake2.net/blake2_20130129.pdf


File: python.info,  Node: 常數<5>,  Next: 範例<17>,  Prev: 建立雜湊物件,  Up: BLAKE2

5.15.1.11 常數
..............

 -- 資料: blake2b.SALT_SIZE

 -- 資料: blake2s.SALT_SIZE

鹽長度（建構函式接受的最大長度）。

 -- 資料: blake2b.PERSON_SIZE

 -- 資料: blake2s.PERSON_SIZE

個人化字串長度（建構函式接受的最大長度）。

 -- 資料: blake2b.MAX_KEY_SIZE

 -- 資料: blake2s.MAX_KEY_SIZE

最大密鑰大小。

 -- 資料: blake2b.MAX_DIGEST_SIZE

 -- 資料: blake2s.MAX_DIGEST_SIZE

雜湊函式可以輸出的最大摘要大小。


File: python.info,  Node: 範例<17>,  Next: 製作人員,  Prev: 常數<5>,  Up: BLAKE2

5.15.1.12 範例
..............

* Menu:

* 簡單雜湊::
* 使用不同的摘要大小::
* 密鑰雜湊 (Keyed hashing): 密鑰雜湊 Keyed hashing.
* 隨機雜湊 (Randomized hashing): 隨機雜湊 Randomized hashing.
* 個人化::
* 樹狀模式::


File: python.info,  Node: 簡單雜湊,  Next: 使用不同的摘要大小,  Up: 範例<17>

5.15.1.13 簡單雜湊
..................

要計算某些資料的雜湊值，你應該首先透過呼叫適當的建構函式（*note
blake2b(): 5e8. 或 *note blake2s(): 5e9.）以建構一個雜湊物件，然後透過於
物件呼叫 *note update(): 29ac. 來以資料對它更新，最後透過呼叫 *note
digest(): 29ad.（或對於十六進位編碼字串則為 *note hexdigest(): 29ae.）從
物件中獲得摘要。

     >>> from hashlib import blake2b
     >>> h = blake2b()
     >>> h.update(b'Hello world')
     >>> h.hexdigest()
     '6ff843ba685842aa82031d3f53c48b66326df7639a63d128974c5c14f31a0f33343a8c65551134ed1ae0f2b0dd2bb495dc81039e3eeb0aa1bb0388bbeac29183'

作為一個快捷方式，你可以將要更新的第一個資料塊作為位置引數直接傳遞給建構
函式：

     >>> from hashlib import blake2b
     >>> blake2b(b'Hello world').hexdigest()
     '6ff843ba685842aa82031d3f53c48b66326df7639a63d128974c5c14f31a0f33343a8c65551134ed1ae0f2b0dd2bb495dc81039e3eeb0aa1bb0388bbeac29183'

你可以根據需求來多次呼叫 *note hash.update(): 29ac. 以疊代更新雜湊：

     >>> from hashlib import blake2b
     >>> items = [b'Hello', b' ', b'world']
     >>> h = blake2b()
     >>> for item in items:
     ...     h.update(item)
     ...
     >>> h.hexdigest()
     '6ff843ba685842aa82031d3f53c48b66326df7639a63d128974c5c14f31a0f33343a8c65551134ed1ae0f2b0dd2bb495dc81039e3eeb0aa1bb0388bbeac29183'


File: python.info,  Node: 使用不同的摘要大小,  Next: 密鑰雜湊 Keyed hashing,  Prev: 簡單雜湊,  Up: 範例<17>

5.15.1.14 使用不同的摘要大小
............................

BLAKE2 有可調整的摘要大小，BLAKE2b 最多為 64 位元組，BLAKE2s 最多為 32 位
元組。例如，要在不改變輸出大小的情況下用 BLAKE2b 替換 SHA-1，我們可以指
定 BLAKE2b 生成 20 位元組的摘要：

     >>> from hashlib import blake2b
     >>> h = blake2b(digest_size=20)
     >>> h.update(b'Replacing SHA1 with the more secure function')
     >>> h.hexdigest()
     'd24f26cf8de66472d58d4e1b1774b4c9158b1f4c'
     >>> h.digest_size
     20
     >>> len(h.digest())
     20

具有不同摘要大小的雜湊物件具有完全不同的輸出（較短的雜湊值'不是'較長雜湊
值的前綴）；即使輸出長度相同，BLAKE2b 和 BLAKE2s 也會產生不同的輸出：

     >>> from hashlib import blake2b, blake2s
     >>> blake2b(digest_size=10).hexdigest()
     '6fa1d8fcfd719046d762'
     >>> blake2b(digest_size=11).hexdigest()
     'eb6ec15daf9546254f0809'
     >>> blake2s(digest_size=10).hexdigest()
     '1bf21a98c78a1c376ae9'
     >>> blake2s(digest_size=11).hexdigest()
     '567004bf96e4a25773ebf4'


File: python.info,  Node: 密鑰雜湊 Keyed hashing,  Next: 隨機雜湊 Randomized hashing,  Prev: 使用不同的摘要大小,  Up: 範例<17>

5.15.1.15 密鑰雜湊 (Keyed hashing)
..................................

密鑰雜湊可用於身份驗證，作為基於雜湊的訊息驗證碼 (Hash-based message
authentication code)(1) (HMAC) 的更快、更簡單的替代方案。由於繼承自
BLAKE 的不可微特性 (indifferentiability property)，BLAKE2 可以安全地用於
prefix-MAC 模式。

此範例示範了如何使用密鑰 ‘b'pseudorandom key'’ 獲取訊息 ‘b'message
data'’ 的（十六進位編碼）128 位元驗證碼：

     >>> from hashlib import blake2b
     >>> h = blake2b(key=b'pseudorandom key', digest_size=16)
     >>> h.update(b'message data')
     >>> h.hexdigest()
     '3d363ff7401e02026f4a4687d4863ced'

舉一個實際的例子，網頁應用程式可以對發送給使用者的 cookie 進行對稱簽名
(symmetrically sign)，然後驗證它們以確保它們沒有被篡改：

     >>> from hashlib import blake2b
     >>> from hmac import compare_digest
     >>>
     >>> SECRET_KEY = b'pseudorandomly generated server secret key'
     >>> AUTH_SIZE = 16
     >>>
     >>> def sign(cookie):
     ...     h = blake2b(digest_size=AUTH_SIZE, key=SECRET_KEY)
     ...     h.update(cookie)
     ...     return h.hexdigest().encode('utf-8')
     >>>
     >>> def verify(cookie, sig):
     ...     good_sig = sign(cookie)
     ...     return compare_digest(good_sig, sig)
     >>>
     >>> cookie = b'user-alice'
     >>> sig = sign(cookie)
     >>> print("{0},{1}".format(cookie.decode('utf-8'), sig))
     user-alice,b'43b3c982cf697e0c5ab22172d1ca7421'
     >>> verify(cookie, sig)
     True
     >>> verify(b'user-bob', sig)
     False
     >>> verify(cookie, b'0102030405060708090a0b0c0d0e0f00')
     False

儘管有原生密鑰雜湊模式，BLAKE2 還是可以透過 *note hmac: 60. 模組用於建構
HMAC：

     >>> import hmac, hashlib
     >>> m = hmac.new(b'secret key', digestmod=hashlib.blake2s)
     >>> m.update(b'message')
     >>> m.hexdigest()
     'e3c8102868d28b5ff85fc35dda07329970d1a01e273c37481326fe0c861c8142'

   ---------- Footnotes ----------

   (1) https://zh.wikipedia.org/zh-tw/HMAC


File: python.info,  Node: 隨機雜湊 Randomized hashing,  Next: 個人化,  Prev: 密鑰雜湊 Keyed hashing,  Up: 範例<17>

5.15.1.16 隨機雜湊 (Randomized hashing)
.......................................

透過設定 'salt' 參數，使用者可以向雜湊函式引入隨機化。隨機雜湊在防止針對
數位簽章中雜湊函式的碰撞攻擊 (collision attacks) 非常有用。

     隨機雜湊是為這樣的情況而設計的：一方（訊息準備者）生成全部或部分訊
     息並由另一方（訊息簽名者）簽名。如果訊息準備者能夠發現加密雜湊函式
     發生碰撞（collision，即兩條訊息產生相同的雜湊值），那麼他們可能會準
     備有意義的訊息版本，該版本將產生相同的雜湊值和數位簽章，但結果不同
     （例如，將 $1,000,000 轉入賬戶，而不是 $10）。加密雜湊函式的設計以
     抗碰撞性為主要目標，但當前對加密雜湊函式攻擊的關注可能會導致給定的
     加密雜湊函式所提供的抗碰撞性低於預期。隨機雜湊透過降低準備者在數位
     簽章生成過程中生成最終產生相同雜湊值的兩個或多個訊息的可能性，為簽
     名者提供額外的保護 —— 即便嘗試去找到雜湊函式碰撞的發生是實際可行的
     。然而，若訊息的所有部分都是由簽名者所準備好的，使用隨機雜湊可能會
     降低數位簽章提供的安全性。

     （NIST SP-800-106 「數位簽章的隨機雜湊 (Randomized Hashing for
     Digital Signatures)」(1)）

在 BLAKE2 中，鹽在初始化期間作為雜湊函式的一次性輸入被處理，而不是作為每
個壓縮函式的輸入。

     警告: 使用 BLAKE2 或任何其他通用加密雜湊函式（例如 SHA-256）的'加鹽
     雜湊' （或單純雜湊）不適合對密碼進行雜湊處理。有關更多資訊，請參閱
     BLAKE2 FAQ(2) 。

     >>> import os
     >>> from hashlib import blake2b
     >>> msg = b'some message'
     >>> # Calculate the first hash with a random salt.
     >>> salt1 = os.urandom(blake2b.SALT_SIZE)
     >>> h1 = blake2b(salt=salt1)
     >>> h1.update(msg)
     >>> # Calculate the second hash with a different random salt.
     >>> salt2 = os.urandom(blake2b.SALT_SIZE)
     >>> h2 = blake2b(salt=salt2)
     >>> h2.update(msg)
     >>> # The digests are different.
     >>> h1.digest() != h2.digest()
     True

   ---------- Footnotes ----------

   (1) 
https://csrc.nist.gov/publications/detail/sp/800-106/archive/2009-02-25

   (2) https://www.blake2.net/#qa


File: python.info,  Node: 個人化,  Next: 樹狀模式,  Prev: 隨機雜湊 Randomized hashing,  Up: 範例<17>

5.15.1.17 個人化
................

有時候強制雜湊函式為不同目的的相同輸入生成不同的摘要是很有用的。引用
Skein 雜湊函式的作者的話：

     我們建議所有應用程式設計者認真考慮這樣做；我們已經看到許多協議，其
     中在協議的一個部分中計算的雜湊可以在完全不同的部分中使用，因為兩次
     雜湊計算是在相似或相關的資料上完成的，並且攻擊者可以強制應用程式將
     雜湊輸入設為相同的。對協議中使用的每個雜湊函式進行個人化可以立即阻
     止此類攻擊。

     （Skein 雜湊函式系列(1)，第 21 頁）

BLAKE2 可以透過將位元組傳遞給 'person' 引數來做個人化：

     >>> from hashlib import blake2b
     >>> FILES_HASH_PERSON = b'MyApp Files Hash'
     >>> BLOCK_HASH_PERSON = b'MyApp Block Hash'
     >>> h = blake2b(digest_size=32, person=FILES_HASH_PERSON)
     >>> h.update(b'the same content')
     >>> h.hexdigest()
     '20d9cd024d4fb086aae819a1432dd2466de12947831b75c5a30cf2676095d3b4'
     >>> h = blake2b(digest_size=32, person=BLOCK_HASH_PERSON)
     >>> h.update(b'the same content')
     >>> h.hexdigest()
     'cf68fb5761b9c44e7878bfb2c4c9aea52264a80b75005e65619778de59f383a3'

個人化與密鑰模式還可以一起用於從單個密鑰得出不同的密鑰。

     >>> from hashlib import blake2s
     >>> from base64 import b64decode, b64encode
     >>> orig_key = b64decode(b'Rm5EPJai72qcK3RGBpW3vPNfZy5OZothY+kHY6h21KM=')
     >>> enc_key = blake2s(key=orig_key, person=b'kEncrypt').digest()
     >>> mac_key = blake2s(key=orig_key, person=b'kMAC').digest()
     >>> print(b64encode(enc_key).decode('utf-8'))
     rbPb15S/Z9t+agffno5wuhB77VbRi6F9Iv2qIxU7WHw=
     >>> print(b64encode(mac_key).decode('utf-8'))
     G9GtHFE1YluXY1zWPlYk1e/nWfu0WSEb0KRcjhDeP/o=

   ---------- Footnotes ----------

   (1) https://www.schneier.com/wp-content/uploads/2016/02/skein.pdf


File: python.info,  Node: 樹狀模式,  Prev: 個人化,  Up: 範例<17>

5.15.1.18 樹狀模式
..................

下面是對具有兩個葉節點的最小樹進行雜湊處理的範例：

       10
      /  \
     00  01

此範例使用 64-byte 內部摘要，並回傳 32-byte 最終摘要：

     >>> from hashlib import blake2b
     >>>
     >>> FANOUT = 2
     >>> DEPTH = 2
     >>> LEAF_SIZE = 4096
     >>> INNER_SIZE = 64
     >>>
     >>> buf = bytearray(6000)
     >>>
     >>> # Left leaf
     ... h00 = blake2b(buf[0:LEAF_SIZE], fanout=FANOUT, depth=DEPTH,
     ...               leaf_size=LEAF_SIZE, inner_size=INNER_SIZE,
     ...               node_offset=0, node_depth=0, last_node=False)
     >>> # Right leaf
     ... h01 = blake2b(buf[LEAF_SIZE:], fanout=FANOUT, depth=DEPTH,
     ...               leaf_size=LEAF_SIZE, inner_size=INNER_SIZE,
     ...               node_offset=1, node_depth=0, last_node=True)
     >>> # Root node
     ... h10 = blake2b(digest_size=32, fanout=FANOUT, depth=DEPTH,
     ...               leaf_size=LEAF_SIZE, inner_size=INNER_SIZE,
     ...               node_offset=0, node_depth=1, last_node=True)
     >>> h10.update(h00.digest())
     >>> h10.update(h01.digest())
     >>> h10.hexdigest()
     '3ad2a9b37c6070e374c7a8c508fe20ca86b6ed54e286e93a0318e95e881db5aa'


File: python.info,  Node: 製作人員,  Prev: 範例<17>,  Up: BLAKE2

5.15.1.19 製作人員
..................

BLAKE2(1) 由 'Jean-Philippe Aumasson'、'Samuel Neves'、'Zooko
Wilcox-O'Hearn' 和 'Christian Winnerlein' 設計，基於由 'Jean-Philippe
Aumasson'、'Luca Henzen'、'Willi Meier' 和 'Raphael C.-W. Phan' 所建立的
SHA-3(2) 最終版本 BLAKE(3)。

它使用 'Daniel J. Bernstein' 設計的 ChaCha(4) 密碼的核心演算法。

標準函式庫實作是基於 pyblake2(5) 模組。它是由 'Dmitry Chestnykh' 在
'Samuel Neves' 的 C 版本實作為基礎所編寫的。該文件是由 'Dmitry
Chestnykh' 編寫並從 pyblake2(6) 複製過來的。

'Christian Heimes' 為 Python 重寫了部分 C 程式碼。

以下公開領域貢獻適用於 C 雜湊函式實作、擴充程式碼和此文件：

     在法律允許的範圍內，作者已將該軟體的所有版權以及相關和鄰接權利奉獻
     給全球的公開領域。該軟體的發布沒有任何授權 (warranty)。

     你應會隨本軟體一起收到一份 CC0 公眾領域貢獻宣告 (CC0 Public Domain
     Dedication) 的副本。如果沒有，請參閱
     ‘https://creativecommons.org/publicdomain/zero/1.0/’ 。

以下人員根據創用 CC 通用公眾領域貢獻宣告 1.0 (Creative Commons Public
Domain Dedication 1.0 Universal) 於專案和公開領域做出了開發或貢獻：

   * 'Alexandr Sokolovskiy'

也參考
......

*note hmac: 60. 模組

     使用雜湊生成訊息驗證程式碼的模組。

*note base64: a. 模組

     另一種在非二進位環境中編碼二進位雜湊的方法。

‘https://nvlpubs.nist.gov/nistpubs/fips/nist.fips.180-4.pdf’

     有關安全雜湊演算法的 FIPS 180-4 出版物。

‘https://csrc.nist.gov/publications/detail/fips/202/final’

     有關 SHA-3 標準的 FIPS 202 出版物。

‘https://www.blake2.net/’

     BLAKE2 官方網站。

‘https://en.wikipedia.org/wiki/Cryptographic_hash_function’

     包含有關哪些演算法存在已知問題以及這些問題對其使用意味著什麼資訊的
     維基百科文章。

‘https://www.ietf.org/rfc/rfc8018.txt’

     PKCS #5：基於密碼的加密規範版本 2.1

‘https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-132.pdf’

     NIST（美國國家標準技術研究院）針對基於密碼的密鑰衍生的建議。

   ---------- Footnotes ----------

   (1) https://www.blake2.net

   (2) https://en.wikipedia.org/wiki/Secure_Hash_Algorithms

   (3) 
https://web.archive.org/web/20200918190133/https://131002.net/blake/

   (4) https://cr.yp.to/chacha.html

   (5) https://pythonhosted.org/pyblake2/

   (6) https://pythonhosted.org/pyblake2/


File: python.info,  Node: hmac --- 基於金鑰雜湊的訊息驗證,  Next: secrets --- 產生用於管理機密的安全亂數,  Prev: hashlib --- 安全雜湊與訊息摘要,  Up: 加密服務

5.15.2 ‘hmac’ -- 基於金鑰雜湊的訊息驗證
---------------------------------------

'原始碼：'Lib/hmac.py(1)

__________________________________________________________________

此模組 (module) 實現了 RFC 2014(2) 所描述的 HMAC 演算法。

 -- 函式: hmac.new (key, msg=None, digestmod)

     回傳一個新的 hmac 物件。'key' 是一個指定密鑰的 bytes（位元組）或
     bytearray 物件。如果提供了 'msg'，將會呼叫 ‘update(msg)’ 方法。
     'digestmod' 為 HMAC 物件所用的摘要名稱、摘要建構函式 (constructor)
     或模組。它可以是適用於 *note hashlib.new(): 1849. 的任何名稱。儘管
     該引數的位置在後，但它卻是必須的。

     在 3.4 版的變更: 參數 'key' 可以為 bytes 或 bytearray 物件。參數
     'msg' 可以為 *note hashlib: 5e. 所支援的任意型別。參數 'digestmod'
     可以為雜湊演算法的名稱。

     在 3.8 版的變更: 'digestmod' 引數現在是必須的。請將其作為關鍵字引數
     傳入以避免當你沒有初始 'msg' 時導致的麻煩。

 -- 函式: hmac.digest (key, msg, digest)

     基於給定密鑰 'key' 和 'digest' 回傳 'msg' 的摘要。此函式等價於
     ‘HMAC(key, msg, digest).digest()’，但使用了優化的 C 或 行內實作（
     inline implementation），對放入記憶體的訊息能處理得更快。參數
     'key'、'msg' 和 'digest' 在 *note new(): a42. 中具有相同含義。

     作為 CPython 的實現細節，C 的優化實作只有當 'digest' 為字串並且是一
     個 OpenSSL 所支持的摘要演算法的名稱時才會被使用。

     在 3.7 版被加入.

HMAC 物件具有下列方法 (method)：

 -- 方法: HMAC.update (msg)

     用 'msg' 來更新 hmac 物件。重複呼叫相當於單次呼叫並傳入所有引數的拼
     接結果：‘m.update(a); m.update(b)’ 等價於 ‘m.update(a + b)’。

     在 3.4 版的變更: 參數 'msg' 可以是 *note hashlib: 5e. 所支援的任何
     型別。

 -- 方法: HMAC.digest ()

     回傳當前已傳給 *note update(): eed. 方法的 bytes 摘要。這個 bytes 物
     件的長度會與傳給建構函式的摘要 'digest_size' 的長度相同。它可以包含
     NUL bytes 以及 non-ASCII bytes。

          警告: 在一個例行的驗證事務運行期間，將 *note digest(): ae2. 的
          輸出與外部提供的摘要進行比較時，建議使用 *note
          compare_digest(): 1063. 函式而不是 ‘==’ 運算子以減少被定時攻擊
          時的漏洞。

 -- 方法: HMAC.hexdigest ()

     像是 *note digest(): ae2. 但摘要的回傳形式為兩倍長度的字串，且此字
     串只包含十六進位數位。這可以被用於在電子郵件或其他非二進位制環境中
     安全地交換數據。

          警告: 在一個例行的驗證事務運行期間，將 *note hexdigest():
          29d6. 的輸出與外部提供的摘要進行比較時，建議使用 *note
          compare_digest(): 1063. 函式而不是 ‘==’ 運算子以減少被定時攻擊
          時的漏洞。

 -- 方法: HMAC.copy ()

     回傳 hmac 物件的拷貝 ("clone")。這可以被用來有效率地計算那些共享相
     同初始子字串的字串的摘要。

一個 hash 物件具有以下屬性：

 -- 屬性: HMAC.digest_size

     以 bytes 表示最終 HMAC 摘要的大小。

 -- 屬性: HMAC.block_size

     以 bytes 表示雜湊演算法的內部區塊大小。

     在 3.4 版被加入.

 -- 屬性: HMAC.name

     HMAC 的正準名稱總是為小寫形式，例如 ‘hmac-md5’。

     在 3.4 版被加入.

在 3.10 版的變更: 未寫入文件的屬性 ‘HMAC.digest_cons’，‘HMAC.inner’ 和
‘HMAC.outer’ 已被移除。

這個模組還提供了下列輔助函式：

 -- 函式: hmac.compare_digest (a, b)

     回傳 ‘a == b’。此函式使用一種經專門設計的方式通過避免基於內容的短路
     行為來防止定時分析，使得它適合處理密碼學。'a' 和 'b' 必須為相同的型
     別：可以是 *note str: 3f2.（僅限 ASCII，如 *note HMAC.hexdigest():
     29d6. 的回傳值），或者是 *note bytes-like object: cd4.。

          備註: 如果 'a' 和 'b' 具有不同的長度，或者如果發生了錯誤，定時
          攻擊在理論上可以獲取有關 'a' 和 'b' 的型別和長度的訊息 — 但不
          能獲取他們的值。

     在 3.3 版被加入.

     在 3.10 版的變更: 此函式在可能的情況下會在內部使用 OpenSSL 的
     ‘CRYPTO_memcmp()’。

也參考
......

*note hashlib: 5e. 模組

     Python 模組提供安全的雜湊函式。

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/hmac.py

   (2) https://datatracker.ietf.org/doc/html/rfc2014.html


File: python.info,  Node: secrets --- 產生用於管理機密的安全亂數,  Prev: hmac --- 基於金鑰雜湊的訊息驗證,  Up: 加密服務

5.15.3 ‘secrets’ -- 產生用於管理機密的安全亂數
----------------------------------------------

在 3.6 版被加入.

'原始碼：'Lib/secrets.py(1)

__________________________________________________________________

*note secrets: ae. 模組可用於產生高加密強度的亂數，適合用來管理諸如密碼
、帳號認證、安全性權杖（security tokens）這類資料，以及管理其他相關的機
密資料。

尤其應優先使用 *note secrets: ae. 作為預設來替代 *note random: a6. 模組
中的預設偽亂數產生器（pseudo-random number generator），該模組被設計用於
建模和模擬，而非用於安全性和加密。

也參考
......

PEP 506(2)

* Menu:

* 亂數::
* 產生權杖（token）::
* 其他函式::
* 應用技巧和典範實務（best practices）::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/secrets.py

   (2) https://peps.python.org/pep-0506/


File: python.info,  Node: 亂數,  Next: 產生權杖（token）,  Up: secrets --- 產生用於管理機密的安全亂數

5.15.3.1 亂數
.............

*note secrets: ae. 模組使你得以存取作業系統所提供安全性最高的亂數產生器
。

 -- 類別: secrets.SystemRandom

     一個用來產生亂數的類別，用的是作業系統提供的最高品質來源。 請參閱
     *note random.SystemRandom: 25bc. 以獲取更多細節。

 -- 函式: secrets.choice (seq)

     從一非空序列中，回傳一個隨機選取的元素。

 -- 函式: secrets.randbelow (exclusive_upper_bound)

     回傳一個 [0, 'exclusive_upper_bound') 範圍之內的隨機整數。

 -- 函式: secrets.randbits (k)

     Return an int with 'k' random bits.


File: python.info,  Node: 產生權杖（token）,  Next: 其他函式,  Prev: 亂數,  Up: secrets --- 產生用於管理機密的安全亂數

5.15.3.2 產生權杖（token）
..........................

*note secrets: ae. 模組提供了一些產生安全性權杖的函式，適合用於諸如重設
密碼、難以猜測的 URL，或類似的應用。

 -- 函式: secrets.token_bytes ([nbytes=None])

     回傳一個隨機位元組字串，其中含有 'nbytes' 位元組的數字。 如果
     'nbytes' 為 ‘None’ 或未提供，則會使用一合理預設值。

          >>> token_bytes(16)
          b'\xebr\x17D*t\xae\xd4\xe3S\xb6\xe2\xebP1\x8b'

 -- 函式: secrets.token_hex ([nbytes=None])

     回傳一以十六進位表示的隨機字串。 字串具有 'nbytes' 個隨機位元組，每
     個位元組會轉成兩個十六進位的數字。 如果 'nbytes' 為 ‘None’ 或未提供
     ，則會使用一個合理的預設值。

          >>> token_hex(16)
          'f9bf78b9a18ce6d46a0cd2b0b86df9da'

 -- 函式: secrets.token_urlsafe ([nbytes=None])

     回傳一個 URL 安全的隨機文本字串，包含 'nbytes' 個隨機位元組。 文本
     將使用 Base64 編碼，因此平均來說每個位元組會對應到約 1.3 個字元。 如
     果 'nbytes' 為 ‘None’ 或未提供，則會使用一個合理的預設值。

          >>> token_urlsafe(16)
          'Drmhze6EPcv0fN_81Bj-nA'

* Menu:

* 權杖應當使用多少個位元組？::


File: python.info,  Node: 權杖應當使用多少個位元組？,  Up: 產生權杖（token）

5.15.3.3 權杖應當使用多少個位元組？
...................................

為了在面對暴力攻擊(1)時能保證安全，權杖必須具有足夠的隨機性。 不幸的是，
對隨機性是否足夠的標準，會隨著電腦越來越強大並能夠在更短時間內進行更多猜
測而不斷提高。 在 2015 年時，人們認為 32 位元組（256 位元）的隨機性對於
*note secrets: ae. 模組所預期的一般使用場景來說是足夠的。

對於想自行管理權杖長度的使用者，你可以對各種 ‘token_*’ 函式明白地指定
*note int: 23c. 引數（argument）來指定權杖要使用的隨機性程度。 該引數以
位元組數來表示要使用的隨機性程度。

否則，如未提供引數，或者如果引數為 ‘None’，則 ‘token_*’ 函式則會使用一個
合理的預設值。

     備註: 該預設值可能在任何時候被改變，包括在維護版本更新的時候。

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Brute-force_attack


File: python.info,  Node: 其他函式,  Next: 應用技巧和典範實務（best practices）,  Prev: 產生權杖（token）,  Up: secrets --- 產生用於管理機密的安全亂數

5.15.3.4 其他函式
.................

 -- 函式: secrets.compare_digest (a, b)

     如果字串或*note 類位元組串物件: cd4. 'a' 與 'b' 相等則回傳 ‘True’，
     否則回傳 ‘False’，以"恆定時間比較 (constant-time compare) "的處理方
     式可降低時序攻擊(1)的風險。 請參閱 *note hmac.compare_digest():
     1063. 以了解更多細節。

   ---------- Footnotes ----------

   (1) https://codahale.com/a-lesson-in-timing-attacks/


File: python.info,  Node: 應用技巧和典範實務（best practices）,  Prev: 其他函式,  Up: secrets --- 產生用於管理機密的安全亂數

5.15.3.5 應用技巧和典範實務（best practices）
.............................................

本節展示了一些使用 *note secrets: ae. 來管理基本安全等級的應用技巧和典範
實務。

產生八個字元長的字母數字密碼：

     import string
     import secrets
     alphabet = string.ascii_letters + string.digits
     password = ''.join(secrets.choice(alphabet) for i in range(8))

     備註: 應用程式不能以可復原的格式存儲密碼(1)，無論是用純文本還是經過
     加密。 它們應當先加鹽（salt），再使用高加密強度的單向（不可逆）雜湊
     函式來產生雜湊值。

產生十個字元長的字母數字密碼，其中包含至少一個小寫字母，至少一個大寫字母
以及至少三個數字:

     import string
     import secrets
     alphabet = string.ascii_letters + string.digits
     while True:
         password = ''.join(secrets.choice(alphabet) for i in range(10))
         if (any(c.islower() for c in password)
                 and any(c.isupper() for c in password)
                 and sum(c.isdigit() for c in password) >= 3):
             break

產生 XKCD 風格的 passphrase(2):

     import secrets
     # On standard Linux systems, use a convenient dictionary file.
     # Other platforms may need to provide their own word-list.
     with open('/usr/share/dict/words') as f:
         words = [word.strip() for word in f]
         password = ' '.join(secrets.choice(words) for i in range(4))

產生難以猜測的暫時性 URL，內含回復密碼時所用的一個安全性權杖：

     import secrets
     url = 'https://example.com/reset=' + secrets.token_urlsafe()

   ---------- Footnotes ----------

   (1) https://cwe.mitre.org/data/definitions/257.html

   (2) https://xkcd.com/936/


File: python.info,  Node: 通用作業系統服務,  Next: 並行執行 Concurrent Execution,  Prev: 加密服務,  Up: Python 標準函式庫 Standard Library

5.16 通用作業系統服務
=====================

此章節所描述的模組 (module) 提供了作業系統特性的使用介面，例如檔案與時鐘
，（幾乎）在所有作業系統上皆能使用。這些介面通常是參考 Unix 或 C 的介面
來實作，不過在其他大多數系統上也能使用。以下為概述：

* Menu:

* os: os --- 各種作業系統介面. 各種作業系統介面
* io — 處理資料串流的核心工具::
* time: time --- 時間存取與轉換. 時間存取與轉換
* argparse: argparse --- Parser for command-line options arguments and sub-commands. Parser for command-line options, arguments and sub-
                        commands
* logging: logging --- Python 的日誌記錄工具. Python 的日誌記錄工具
* logging.config: logging config --- 日誌記錄配置. 日誌記錄配置
* logging.handlers: logging handlers --- 日誌紀錄處理器. 日誌紀錄處理器
* getpass: getpass --- 可攜式密碼輸入工具. 可攜式密碼輸入工具
* curses: curses --- 字元儲存格顯示的終端處理. 字元儲存格顯示的終端處理
* curses.textpad: curses textpad --- Text input widget for curses programs. Text input widget for curses programs
* curses.ascii: curses ascii --- ASCII 字元的工具程式. ASCII 字元的工具程式
* curses.panel: curses panel --- curses 的面板堆疊擴充. curses 的面板堆疊擴充
* platform: platform --- 對底層平臺識別資料的存取. 對底層平臺識別資料的存取
* errno: errno --- 標準 errno 系統符號. 標準 errno 系統符號
* ctypes: ctypes --- 用於 Python 的外部函式庫. 用於 Python 的外部函式庫


File: python.info,  Node: os --- 各種作業系統介面,  Next: io — 處理資料串流的核心工具,  Up: 通用作業系統服務

5.16.1 ‘os’ -- 各種作業系統介面
-------------------------------

'原始碼：'Lib/os.py(1)

__________________________________________________________________

該模組提供了一種便利的方式來操作與作業系統相關的功能。如果你想讀取或寫入
檔案，請參閱 *note open(): 4c0. ，如果你想操作檔案路徑，請參閱 *note
os.path: 92. 模組，如果你想透過命令列查看所有檔案中的所有內容，請查看
*note fileinput: 51. 模組。要建立臨時檔案和目錄，請參閱 *note tempfile:
c9. 模組，要操作高級檔案和目錄，請參閱 *note shutil: b3. 模組。

關於這些功能的可用性說明：

   * Python 所有內建作業系統相關的模組設計是這樣：只要有相同的函式可使用
     ，就會使用相同的介面 （interface）。舉例來說，‘os.stat(path)’ 函式
     會以相同格式回傳關於 'path' 的統計資訊（這剛好來自於 POSIX 的介面。
     ）。

   * 對於特定的作業系統獨有的擴充功能也可以透過 *note os: 91. 取得，但使
     用它們的時候對於可移植性無疑會是個問題。

   * 所有接受檔案路徑和檔案名稱的函式皆接受位元組 (bytes) 和字串物件
     (string objects)，且如果回傳檔案路徑或檔案名稱，則會產出相同型別的
     物件。

   * 在 VxWorks, 不支援 os.popen、os.fork、os.execv 和 os.spawn*p*。

   * On WebAssembly platforms, and on iOS, large parts of the *note os:
     91. module are not available or behave differently.  API related to
     processes (e.g.  *note fork(): 17b, *note execve(): 1091.) and
     resources (e.g.  *note nice(): 1099.) are not available.  Others
     like *note getuid(): 29ea. and *note getpid(): 29eb. are emulated
     or stubs.  WebAssembly platforms also lack support for signals
     (e.g.  *note kill(): 12f4, *note wait(): d3e.).

     備註: 在檔案名稱和路徑找不到或無效的時候，或引數型別正確但作業系統
     不接受的時候，在此模組中的所有的函式都會引發 *note OSError: 350.（
     或其子類別）。

 -- 例外: os.error

     內建例外 *note OSError: 350. 的別名。

 -- 資料: os.name

     The name of the operating system dependent module imported.  The
     following names have currently been registered: ‘'posix'’, ‘'nt'’,
     ‘'java'’.

     也參考
     ......

     *note sys.platform: a30. has a finer granularity.  *note
     os.uname(): 10ae. gives system-dependent version information.

     The *note platform: 98. module provides detailed checks for the
     system's identity.

* Menu:

* File Names, Command Line Arguments, and Environment Variables: File Names Command Line Arguments and Environment Variables.
* Python UTF-8 模式::
* 行程參數::
* File Object Creation::
* File Descriptor Operations::
* Files and Directories::
* 行程管理::
* Interface to the scheduler::
* Miscellaneous System Information::
* Random numbers::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/os.py


File: python.info,  Node: File Names Command Line Arguments and Environment Variables,  Next: Python UTF-8 模式,  Up: os --- 各種作業系統介面

5.16.1.1 File Names, Command Line Arguments, and Environment Variables
......................................................................

In Python, file names, command line arguments, and environment variables
are represented using the string type.  On some systems, decoding these
strings to and from bytes is necessary before passing them to the
operating system.  Python uses the *note filesystem encoding and error
handler: 4e0. to perform this conversion (see *note
sys.getfilesystemencoding(): c00.).

The *note filesystem encoding and error handler: 4e0. are configured at
Python startup by the *note PyConfig_Read(): 734. function: see *note
filesystem_encoding: 3b3. and *note filesystem_errors: 3b4. members of
*note PyConfig: 371.

在 3.1 版的變更: On some systems, conversion using the file system
encoding may fail.  In this case, Python uses the *note surrogateescape
encoding error handler: 22c2, which means that undecodable bytes are
replaced by a Unicode character U+DC'xx' on decoding, and these are
again translated to the original byte on encoding.

The *note file system encoding: 4e0. must guarantee to successfully
decode all bytes below 128.  If the file system encoding fails to
provide this guarantee, API functions can raise *note UnicodeError:
123a.

另請參閱 *note locale encoding: 227.。


File: python.info,  Node: Python UTF-8 模式,  Next: 行程參數,  Prev: File Names Command Line Arguments and Environment Variables,  Up: os --- 各種作業系統介面

5.16.1.2 Python UTF-8 模式
..........................

在 3.7 版被加入: 更多資訊請見 PEP 540(1)。

Python 在 UTF-8 模式下會忽略 *note locale encoding: 227. 並且強制使用
UTF-8 去編碼：

   * Use UTF-8 as the *note filesystem encoding: 4e0.

   * *note sys.getfilesystemencoding(): c00. 回傳 ‘'utf-8'’。

   * *note locale.getpreferredencoding(): 4df. returns ‘'utf-8'’ (the
     'do_setlocale' argument has no effect).

   * *note sys.stdin: 4e2, *note sys.stdout: a79, and *note sys.stderr:
     8dd. all use UTF-8 as their text encoding, with the
     ‘surrogateescape’ *note error handler: 16eb. being enabled for
     *note sys.stdin: 4e2. and *note sys.stdout: a79. (*note sys.stderr:
     8dd. continues to use ‘backslashreplace’ as it does in the default
     locale-aware mode)

   * On Unix, *note os.device_encoding(): 1794. returns ‘'utf-8'’ rather
     than the device encoding.

Note that the standard stream settings in UTF-8 mode can be overridden
by *note PYTHONIOENCODING: fab. (just as they can be in the default
locale-aware mode).

As a consequence of the changes in those lower level APIs, other higher
level APIs also exhibit different default behaviours:

   * Command line arguments, environment variables and filenames are
     decoded to text using the UTF-8 encoding.

   * *note os.fsdecode(): bfb. and *note os.fsencode(): bfc. use the
     UTF-8 encoding.

   * *note open(): 4c0, *note io.open(): 4c1, and *note codecs.open():
     6e4. use the UTF-8 encoding by default.  However, they still use
     the strict error handler by default so that attempting to open a
     binary file in text mode is likely to raise an exception rather
     than producing nonsense data.

The *note Python UTF-8 Mode: 5fc. is enabled if the LC_CTYPE locale is
‘C’ or ‘POSIX’ at Python startup (see the *note PyConfig_Read(): 734.
function).

It can be enabled or disabled using the *note -X utf8: 15a. command line
option and the *note PYTHONUTF8: a7b. environment variable.

If the *note PYTHONUTF8: a7b. environment variable is not set at all,
then the interpreter defaults to using the current locale settings,
'unless' the current locale is identified as a legacy ASCII-based locale
(as described for *note PYTHONCOERCECLOCALE: a78.), and locale coercion
is either disabled or fails.  In such legacy locales, the interpreter
will default to enabling UTF-8 mode unless explicitly instructed not to
do so.

The Python UTF-8 Mode can only be enabled at the Python startup.  Its
value can be read from *note sys.flags.utf8_mode: 632.

See also the *note UTF-8 mode on Windows: 1d20. and the *note filesystem
encoding and error handler: 4e0.

也參考
......

PEP 686(2)

     Python 3.15 預設使用 *note Python UTF-8 模式: 5fc.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0540/

   (2) https://peps.python.org/pep-0686/


File: python.info,  Node: 行程參數,  Next: File Object Creation,  Prev: Python UTF-8 模式,  Up: os --- 各種作業系統介面

5.16.1.3 行程參數
.................

These functions and data items provide information and operate on the
current process and user.

 -- 函式: os.ctermid ()

     Return the filename corresponding to the controlling terminal of
     the process.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 資料: os.environ

     A *note mapping: 1154. object where keys and values are strings
     that represent the process environment.  For example,
     ‘environ['HOME']’ is the pathname of your home directory (on some
     platforms), and is equivalent to ‘getenv("HOME")’ in C.

     This mapping is captured the first time the *note os: 91. module is
     imported, typically during Python startup as part of processing
     ‘site.py’.  Changes to the environment made after this time are not
     reflected in *note os.environ: 1152, except for changes made by
     modifying *note os.environ: 1152. directly.

     This mapping may be used to modify the environment as well as query
     the environment.  *note putenv(): 8c1. will be called automatically
     when the mapping is modified.

     On Unix, keys and values use *note sys.getfilesystemencoding():
     c00. and ‘'surrogateescape'’ error handler.  Use *note environb:
     11ae. if you would like to use a different encoding.

     On Windows, the keys are converted to uppercase.  This also applies
     when getting, setting, or deleting an item.  For example,
     ‘environ['monty'] = 'python'’ maps the key ‘'MONTY'’ to the value
     ‘'python'’.

          備註: Calling *note putenv(): 8c1. directly does not change
          *note os.environ: 1152, so it's better to modify *note
          os.environ: 1152.

          備註: On some platforms, including FreeBSD and macOS, setting
          ‘environ’ may cause memory leaks.  Refer to the system
          documentation for ‘putenv()’.

     You can delete items in this mapping to unset environment
     variables.  *note unsetenv(): 8c0. will be called automatically
     when an item is deleted from *note os.environ: 1152, and when one
     of the ‘pop()’ or ‘clear()’ methods is called.

     在 3.9 版的變更: Updated to support PEP 584(1)'s merge (‘|’) and
     update (‘|=’) operators.

 -- 資料: os.environb

     Bytes version of *note environ: 1152.: a *note mapping: 1154.
     object where both keys and values are *note bytes: 1a5. objects
     representing the process environment.  *note environ: 1152. and
     *note environb: 11ae. are synchronized (modifying *note environb:
     11ae. updates *note environ: 1152, and vice versa).

     *note environb: 11ae. is only available if *note
     supports_bytes_environ: 11ac. is ‘True’.

     在 3.2 版被加入.

     在 3.9 版的變更: Updated to support PEP 584(2)'s merge (‘|’) and
     update (‘|=’) operators.

 -- 函式: os.chdir (path)

 -- 函式: os.fchdir (fd)

 -- 函式: os.getcwd ()

     These functions are described in *note Files and Directories: 29f3.

 -- 函式: os.fsencode (filename)

     Encode *note path-like: ac2. 'filename' to the *note filesystem
     encoding and error handler: 4e0.; return *note bytes: 1a5.
     unchanged.

     *note fsdecode(): bfb. is the reverse function.

     在 3.2 版被加入.

     在 3.6 版的變更: Support added to accept objects implementing the
     *note os.PathLike: bf8. interface.

 -- 函式: os.fsdecode (filename)

     Decode the *note path-like: ac2. 'filename' from the *note
     filesystem encoding and error handler: 4e0.; return *note str: 3f2.
     unchanged.

     *note fsencode(): bfc. is the reverse function.

     在 3.2 版被加入.

     在 3.6 版的變更: Support added to accept objects implementing the
     *note os.PathLike: bf8. interface.

 -- 函式: os.fspath (path)

     Return the file system representation of the path.

     If *note str: 3f2. or *note bytes: 1a5. is passed in, it is
     returned unchanged.  Otherwise *note __fspath__(): bf9. is called
     and its value is returned as long as it is a *note str: 3f2. or
     *note bytes: 1a5. object.  In all other cases, *note TypeError:
     4dd. is raised.

     在 3.6 版被加入.

 -- 類別: os.PathLike

     An *note abstract base class: 114e. for objects representing a file
     system path, e.g.  *note pathlib.PurePath: 44e.

     在 3.6 版被加入.

      -- 方法: abstractmethod __fspath__ ()

          Return the file system path representation of the object.

          The method should only return a *note str: 3f2. or *note
          bytes: 1a5. object, with the preference being for *note str:
          3f2.

 -- 函式: os.getenv (key, default=None)

     Return the value of the environment variable 'key' as a string if
     it exists, or 'default' if it doesn't.  'key' is a string.  Note
     that since *note getenv(): 29f4. uses *note os.environ: 1152, the
     mapping of *note getenv(): 29f4. is similarly also captured on
     import, and the function may not reflect future environment
     changes.

     On Unix, keys and values are decoded with *note
     sys.getfilesystemencoding(): c00. and ‘'surrogateescape'’ error
     handler.  Use *note os.getenvb(): 11ad. if you would like to use a
     different encoding.

     *note 適用: 1c56.：Unix、Windows。

 -- 函式: os.getenvb (key, default=None)

     Return the value of the environment variable 'key' as bytes if it
     exists, or 'default' if it doesn't.  'key' must be bytes.  Note
     that since *note getenvb(): 11ad. uses *note os.environb: 11ae, the
     mapping of *note getenvb(): 11ad. is similarly also captured on
     import, and the function may not reflect future environment
     changes.

     *note getenvb(): 11ad. is only available if *note
     supports_bytes_environ: 11ac. is ‘True’.

     *note 適用: 1c56.：Unix。

     在 3.2 版被加入.

 -- 函式: os.get_exec_path (env=None)

     Returns the list of directories that will be searched for a named
     executable, similar to a shell, when launching a process.  'env',
     when specified, should be an environment variable dictionary to
     lookup the PATH in.  By default, when 'env' is ‘None’, *note
     environ: 1152. is used.

     在 3.2 版被加入.

 -- 函式: os.getegid ()

     Return the effective group id of the current process.  This
     corresponds to the "set id" bit on the file being executed in the
     current process.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 函式: os.geteuid ()

     Return the current process's effective user id.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 函式: os.getgid ()

     Return the real group id of the current process.

     *note 適用: 1c56.：Unix。

     The function is a stub on WASI, see *note WebAssembly 平台: 16e6.
     for more information.

 -- 函式: os.getgrouplist (user, group, /)

     Return list of group ids that 'user' belongs to.  If 'group' is not
     in the list, it is included; typically, 'group' is specified as the
     group ID field from the password record for 'user', because that
     group ID will otherwise be potentially omitted.

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.3 版被加入.

 -- 函式: os.getgroups ()

     Return list of supplemental group ids associated with the current
     process.

     *note 適用: 1c56.：Unix、非 WASI。

          備註: On macOS, *note getgroups(): 29f8. behavior differs
          somewhat from other Unix platforms.  If the Python interpreter
          was built with a deployment target of ‘10.5’ or earlier, *note
          getgroups(): 29f8. returns the list of effective group ids
          associated with the current user process; this list is limited
          to a system-defined number of entries, typically 16, and may
          be modified by calls to *note setgroups(): 29f9. if suitably
          privileged.  If built with a deployment target greater than
          ‘10.5’, *note getgroups(): 29f8. returns the current group
          access list for the user associated with the effective user id
          of the process; the group access list may change over the
          lifetime of the process, it is not affected by calls to *note
          setgroups(): 29f9, and its length is not limited to 16.  The
          deployment target value, ‘MACOSX_DEPLOYMENT_TARGET’, can be
          obtained with *note sysconfig.get_config_var(): fce.

 -- 函式: os.getlogin ()

     Return the name of the user logged in on the controlling terminal
     of the process.  For most purposes, it is more useful to use *note
     getpass.getuser(): 351. since the latter checks the environment
     variables ‘LOGNAME’ or ‘USERNAME’ to find out who the user is, and
     falls back to ‘pwd.getpwuid(os.getuid())[0]’ to get the login name
     of the current real user id.

     *note Availability: 1c56.: Unix, Windows, not WASI.

 -- 函式: os.getpgid (pid)

     Return the process group id of the process with process id 'pid'.
     If 'pid' is 0, the process group id of the current process is
     returned.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 函式: os.getpgrp ()

     Return the id of the current process group.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 函式: os.getpid ()

     Return the current process id.

     The function is a stub on WASI, see *note WebAssembly 平台: 16e6.
     for more information.

 -- 函式: os.getppid ()

     Return the parent's process id.  When the parent process has
     exited, on Unix the id returned is the one of the init process (1),
     on Windows it is still the same id, which may be already reused by
     another process.

     *note Availability: 1c56.: Unix, Windows, not WASI.

     在 3.2 版的變更: 新增對 Windows 的支援。

 -- 函式: os.getpriority (which, who)

     Get program scheduling priority.  The value 'which' is one of *note
     PRIO_PROCESS: 29fd, *note PRIO_PGRP: 29fe, or *note PRIO_USER:
     29ff, and 'who' is interpreted relative to 'which' (a process
     identifier for *note PRIO_PROCESS: 29fd, process group identifier
     for *note PRIO_PGRP: 29fe, and a user ID for *note PRIO_USER:
     29ff.).  A zero value for 'who' denotes (respectively) the calling
     process, the process group of the calling process, or the real user
     ID of the calling process.

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.3 版被加入.

 -- 資料: os.PRIO_PROCESS
 -- 資料: os.PRIO_PGRP
 -- 資料: os.PRIO_USER

     Parameters for the *note getpriority(): 1097. and *note
     setpriority(): 1098. functions.

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.3 版被加入.

 -- 資料: os.PRIO_DARWIN_THREAD
 -- 資料: os.PRIO_DARWIN_PROCESS
 -- 資料: os.PRIO_DARWIN_BG
 -- 資料: os.PRIO_DARWIN_NONUI

     Parameters for the *note getpriority(): 1097. and *note
     setpriority(): 1098. functions.

     *note 適用: 1c56.：macOS

     在 3.12 版被加入.

 -- 函式: os.getresuid ()

     Return a tuple (ruid, euid, suid) denoting the current process's
     real, effective, and saved user ids.

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.2 版被加入.

 -- 函式: os.getresgid ()

     Return a tuple (rgid, egid, sgid) denoting the current process's
     real, effective, and saved group ids.

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.2 版被加入.

 -- 函式: os.getuid ()

     Return the current process's real user id.

     *note 適用: 1c56.：Unix。

     The function is a stub on WASI, see *note WebAssembly 平台: 16e6.
     for more information.

 -- 函式: os.initgroups (username, gid, /)

     Call the system initgroups() to initialize the group access list
     with all of the groups of which the specified username is a member,
     plus the specified group id.

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.2 版被加入.

 -- 函式: os.putenv (key, value, /)

     Set the environment variable named 'key' to the string 'value'.
     Such changes to the environment affect subprocesses started with
     *note os.system(): 13c8, *note popen(): a2a. or *note fork(): 17b.
     and *note execv(): 2a04.

     Assignments to items in *note os.environ: 1152. are automatically
     translated into corresponding calls to *note putenv(): 8c1.;
     however, calls to *note putenv(): 8c1. don't update *note
     os.environ: 1152, so it is actually preferable to assign to items
     of *note os.environ: 1152.  This also applies to *note getenv():
     29f4. and *note getenvb(): 11ad, which respectively use *note
     os.environ: 1152. and *note os.environb: 11ae. in their
     implementations.

          備註: On some platforms, including FreeBSD and macOS, setting
          ‘environ’ may cause memory leaks.  Refer to the system
          documentation for ‘putenv()’.

     引發一個附帶引數 ‘key’、‘value’ 的*note 稽核事件: 17bd.
     ‘os.putenv’。

     在 3.9 版的變更: The function is now always available.

 -- 函式: os.setegid (egid, /)

     Set the current process's effective group id.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 函式: os.seteuid (euid, /)

     Set the current process's effective user id.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 函式: os.setgid (gid, /)

     Set the current process' group id.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 函式: os.setgroups (groups, /)

     Set the list of supplemental group ids associated with the current
     process to 'groups'.  'groups' must be a sequence, and each element
     must be an integer identifying a group.  This operation is
     typically available only to the superuser.

     *note 適用: 1c56.：Unix、非 WASI。

          備註: On macOS, the length of 'groups' may not exceed the
          system-defined maximum number of effective group ids,
          typically 16.  See the documentation for *note getgroups():
          29f8. for cases where it may not return the same group list
          set by calling setgroups().

 -- 函式: os.setns (fd, nstype=0)

     Reassociate the current thread with a Linux namespace.  See the
     ‘setns(2)(3)’ and ‘namespaces(7)(4)’ man pages for more details.

     If 'fd' refers to a ‘/proc/`pid'/ns/’ link, ‘setns()’ reassociates
     the calling thread with the namespace associated with that link,
     and 'nstype' may be set to one of the *note CLONE_NEW* constants:
     2a08. to impose constraints on the operation (‘0’ means no
     constraints).

     Since Linux 5.8, 'fd' may refer to a PID file descriptor obtained
     from *note pidfd_open(): 421.  In this case, ‘setns()’ reassociates
     the calling thread into one or more of the same namespaces as the
     thread referred to by 'fd'.  This is subject to any constraints
     imposed by 'nstype', which is a bit mask combining one or more of
     the *note CLONE_NEW* constants: 2a08, e.g.  ‘setns(fd,
     os.CLONE_NEWUTS | os.CLONE_NEWPID)’.  The caller's memberships in
     unspecified namespaces are left unchanged.

     'fd' can be any object with a *note fileno(): 2732. method, or a
     raw file descriptor.

     This example reassociates the thread with the ‘init’ process's
     network namespace:

          fd = os.open("/proc/1/ns/net", os.O_RDONLY)
          os.setns(fd, os.CLONE_NEWNET)
          os.close(fd)

     *note 適用: 1c56.：Linux 3.0 以上且具有 glibc 2.14 以上。

     在 3.12 版被加入.

     也參考
     ......

     *note unshare(): 16c5. 函式。

 -- 函式: os.setpgrp ()

     Call the system call ‘setpgrp()’ or ‘setpgrp(0, 0)’ depending on
     which version is implemented (if any).  See the Unix manual for the
     semantics.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 函式: os.setpgid (pid, pgrp, /)

     Call the system call ‘setpgid()’ to set the process group id of the
     process with id 'pid' to the process group with id 'pgrp'.  See the
     Unix manual for the semantics.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 函式: os.setpriority (which, who, priority)

     Set program scheduling priority.  The value 'which' is one of *note
     PRIO_PROCESS: 29fd, *note PRIO_PGRP: 29fe, or *note PRIO_USER:
     29ff, and 'who' is interpreted relative to 'which' (a process
     identifier for *note PRIO_PROCESS: 29fd, process group identifier
     for *note PRIO_PGRP: 29fe, and a user ID for *note PRIO_USER:
     29ff.).  A zero value for 'who' denotes (respectively) the calling
     process, the process group of the calling process, or the real user
     ID of the calling process.  'priority' is a value in the range -20
     to 19.  The default priority is 0; lower priorities cause more
     favorable scheduling.

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.3 版被加入.

 -- 函式: os.setregid (rgid, egid, /)

     Set the current process's real and effective group ids.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 函式: os.setresgid (rgid, egid, sgid, /)

     Set the current process's real, effective, and saved group ids.

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.2 版被加入.

 -- 函式: os.setresuid (ruid, euid, suid, /)

     Set the current process's real, effective, and saved user ids.

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.2 版被加入.

 -- 函式: os.setreuid (ruid, euid, /)

     Set the current process's real and effective user ids.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 函式: os.getsid (pid, /)

     Call the system call ‘getsid()’.  See the Unix manual for the
     semantics.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 函式: os.setsid ()

     Call the system call ‘setsid()’.  See the Unix manual for the
     semantics.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 函式: os.setuid (uid, /)

     Set the current process's user id.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 函式: os.strerror (code, /)

     Return the error message corresponding to the error code in 'code'.
     On platforms where ‘strerror()’ returns ‘NULL’ when given an
     unknown error number, *note ValueError: 1e7. is raised.

 -- 資料: os.supports_bytes_environ

     ‘True’ if the native OS type of the environment is bytes (eg.
     ‘False’ on Windows).

     在 3.2 版被加入.

 -- 函式: os.umask (mask, /)

     Set the current numeric umask and return the previous umask.

     The function is a stub on WASI, see *note WebAssembly 平台: 16e6.
     for more information.

 -- 函式: os.uname ()

     Returns information identifying the current operating system.  The
     return value is an object with five attributes:

        * ‘sysname’ - 作業系統名稱

        * ‘nodename’ - name of machine on network
          (implementation-defined)

        * ‘release’ - operating system release

        * ‘version’ - 作業系統版本

        * ‘machine’ - hardware identifier

     For backwards compatibility, this object is also iterable, behaving
     like a five-tuple containing ‘sysname’, ‘nodename’, ‘release’,
     ‘version’, and ‘machine’ in that order.

     Some systems truncate ‘nodename’ to 8 characters or to the leading
     component; a better way to get the hostname is *note
     socket.gethostname(): 2a11. or even
     ‘socket.gethostbyaddr(socket.gethostname())’.

     On macOS, iOS and Android, this returns the 'kernel' name and
     version (i.e., ‘'Darwin'’ on macOS and iOS; ‘'Linux'’ on Android).
     *note platform.uname(): 1938. can be used to get the user-facing
     operating system name and version on iOS and Android.

     *note 適用: 1c56.：Unix。

     在 3.3 版的變更: Return type changed from a tuple to a tuple-like
     object with named attributes.

 -- 函式: os.unsetenv (key, /)

     Unset (delete) the environment variable named 'key'.  Such changes
     to the environment affect subprocesses started with *note
     os.system(): 13c8, *note popen(): a2a. or *note fork(): 17b. and
     *note execv(): 2a04.

     Deletion of items in *note os.environ: 1152. is automatically
     translated into a corresponding call to *note unsetenv(): 8c0.;
     however, calls to *note unsetenv(): 8c0. don't update *note
     os.environ: 1152, so it is actually preferable to delete items of
     *note os.environ: 1152.

     引發一個附帶引數 ‘key’ 的*note 稽核事件: 17bd. ‘os.unsetenv’。

     在 3.9 版的變更: The function is now always available and is also
     available on Windows.

 -- 函式: os.unshare (flags)

     Disassociate parts of the process execution context, and move them
     into a newly created namespace.  See the ‘unshare(2)(5)’ man page
     for more details.  The 'flags' argument is a bit mask, combining
     zero or more of the *note CLONE_* constants: 2a08, that specifies
     which parts of the execution context should be unshared from their
     existing associations and moved to a new namespace.  If the 'flags'
     argument is ‘0’, no changes are made to the calling process's
     execution context.

     *note 適用: 1c56.：Linux 2.6.16 以上。

     在 3.12 版被加入.

     也參考
     ......

     *note setns(): 16c4. 函式。

Flags to the *note unshare(): 16c5. function, if the implementation
supports them.  See ‘unshare(2)(6)’ in the Linux manual for their exact
effect and availability.

 -- 資料: os.CLONE_FILES
 -- 資料: os.CLONE_FS
 -- 資料: os.CLONE_NEWCGROUP
 -- 資料: os.CLONE_NEWIPC
 -- 資料: os.CLONE_NEWNET
 -- 資料: os.CLONE_NEWNS
 -- 資料: os.CLONE_NEWPID
 -- 資料: os.CLONE_NEWTIME
 -- 資料: os.CLONE_NEWUSER
 -- 資料: os.CLONE_NEWUTS
 -- 資料: os.CLONE_SIGHAND
 -- 資料: os.CLONE_SYSVSEM
 -- 資料: os.CLONE_THREAD
 -- 資料: os.CLONE_VM

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0584/

   (2) https://peps.python.org/pep-0584/

   (3) https://manpages.debian.org/setns(2)

   (4) https://manpages.debian.org/namespaces(7)

   (5) https://manpages.debian.org/unshare(2)

   (6) https://manpages.debian.org/unshare(2)


File: python.info,  Node: File Object Creation,  Next: File Descriptor Operations,  Prev: 行程參數,  Up: os --- 各種作業系統介面

5.16.1.4 File Object Creation
.............................

These functions create new *note file objects: 115b.  (See also *note
open(): d38. for opening file descriptors.)

 -- 函式: os.fdopen (fd, *args, **kwargs)

     Return an open file object connected to the file descriptor 'fd'.
     This is an alias of the *note open(): 4c0. built-in function and
     accepts the same arguments.  The only difference is that the first
     argument of *note fdopen(): 1e08. must always be an integer.


File: python.info,  Node: File Descriptor Operations,  Next: Files and Directories,  Prev: File Object Creation,  Up: os --- 各種作業系統介面

5.16.1.5 File Descriptor Operations
...................................

These functions operate on I/O streams referenced using file
descriptors.

File descriptors are small integers corresponding to a file that has
been opened by the current process.  For example, standard input is
usually file descriptor 0, standard output is 1, and standard error is
2.  Further files opened by a process will then be assigned 3, 4, 5, and
so forth.  The name "file descriptor" is slightly deceptive; on Unix
platforms, sockets and pipes are also referenced by file descriptors.

The *note fileno(): 2732. method can be used to obtain the file
descriptor associated with a *note file object: 115b. when required.
Note that using the file descriptor directly will bypass the file object
methods, ignoring aspects such as internal buffering of data.

 -- 函式: os.close (fd)

     Close file descriptor 'fd'.

          備註: This function is intended for low-level I/O and must be
          applied to a file descriptor as returned by *note os.open():
          d38. or *note pipe(): 16df.  To close a "file object" returned
          by the built-in function *note open(): 4c0. or by *note
          popen(): a2a. or *note fdopen(): 1e08, use its *note close():
          1db. method.

 -- 函式: os.closerange (fd_low, fd_high, /)

     Close all file descriptors from 'fd_low' (inclusive) to 'fd_high'
     (exclusive), ignoring errors.  Equivalent to (but much faster
     than):

          for fd in range(fd_low, fd_high):
              try:
                  os.close(fd)
              except OSError:
                  pass

 -- 函式: os.copy_file_range (src, dst, count, offset_src=None,
          offset_dst=None)

     Copy 'count' bytes from file descriptor 'src', starting from offset
     'offset_src', to file descriptor 'dst', starting from offset
     'offset_dst'.  If 'offset_src' is ‘None’, then 'src' is read from
     the current position; respectively for 'offset_dst'.

     In Linux kernel older than 5.3, the files pointed to by 'src' and
     'dst' must reside in the same filesystem, otherwise an *note
     OSError: 350. is raised with *note errno: 2169. set to *note
     errno.EXDEV: 2a26.

     This copy is done without the additional cost of transferring data
     from the kernel to user space and then back into the kernel.
     Additionally, some filesystems could implement extra optimizations,
     such as the use of reflinks (i.e., two or more inodes that share
     pointers to the same copy-on-write disk blocks; supported file
     systems include btrfs and XFS) and server-side copy (in the case of
     NFS).

     The function copies bytes between two file descriptors.  Text
     options, like the encoding and the line ending, are ignored.

     The return value is the amount of bytes copied.  This could be less
     than the amount requested.

          備註: On Linux, *note os.copy_file_range(): 2a25. should not
          be used for copying a range of a pseudo file from a special
          filesystem like procfs and sysfs.  It will always copy no
          bytes and return 0 as if the file was empty because of a known
          Linux kernel issue.

     *note 適用: 1c56.：Linux 4.5 以上且具有 glibc 2.27 以上。

     在 3.8 版被加入.

 -- 函式: os.device_encoding (fd)

     Return a string describing the encoding of the device associated
     with 'fd' if it is connected to a terminal; else return *note None:
     61b.

     On Unix, if the *note Python UTF-8 Mode: 5fc. is enabled, return
     ‘'UTF-8'’ rather than the device encoding.

     在 3.10 版的變更: On Unix, the function now implements the Python
     UTF-8 Mode.

 -- 函式: os.dup (fd, /)

     Return a duplicate of file descriptor 'fd'.  The new file
     descriptor is *note non-inheritable: e9d.

     On Windows, when duplicating a standard stream (0: stdin, 1:
     stdout, 2: stderr), the new file descriptor is *note inheritable:
     e9d.

     *note 適用: 1c56.：非 WASI。

     在 3.4 版的變更: The new file descriptor is now non-inheritable.

 -- 函式: os.dup2 (fd, fd2, inheritable=True)

     Duplicate file descriptor 'fd' to 'fd2', closing the latter first
     if necessary.  Return 'fd2'.  The new file descriptor is *note
     inheritable: e9d. by default or non-inheritable if 'inheritable' is
     ‘False’.

     *note 適用: 1c56.：非 WASI。

     在 3.4 版的變更: Add the optional 'inheritable' parameter.

     在 3.7 版的變更: Return 'fd2' on success.  Previously, ‘None’ was
     always returned.

 -- 函式: os.fchmod (fd, mode)

     Change the mode of the file given by 'fd' to the numeric 'mode'.
     See the docs for *note chmod(): 200. for possible values of 'mode'.
     As of Python 3.3, this is equivalent to ‘os.chmod(fd, mode)’.

     引發一個附帶引數 ‘path’、‘mode’、‘dir_fd’ 的*note 稽核事件: 17bd.
     ‘os.chmod’。

     *note 適用: 1c56.：Unix、Windows。

     The function is limited on WASI, see *note WebAssembly 平台: 16e6.
     for more information.

     在 3.13 版的變更: Added support on Windows.

 -- 函式: os.fchown (fd, uid, gid)

     Change the owner and group id of the file given by 'fd' to the
     numeric 'uid' and 'gid'.  To leave one of the ids unchanged, set it
     to -1.  See *note chown(): 1087.  As of Python 3.3, this is
     equivalent to ‘os.chown(fd, uid, gid)’.

     引發一個附帶引數 ‘path’、‘uid’、‘gid’、‘dir_fd’ 的*note 稽核事件:
     17bd. ‘os.chown’。

     *note 適用: 1c56.：Unix。

     The function is limited on WASI, see *note WebAssembly 平台: 16e6.
     for more information.

 -- 函式: os.fdatasync (fd)

     Force write of file with filedescriptor 'fd' to disk.  Does not
     force update of metadata.

     *note 適用: 1c56.：Unix。

          備註: This function is not available on MacOS.

 -- 函式: os.fpathconf (fd, name, /)

     Return system configuration information relevant to an open file.
     'name' specifies the configuration value to retrieve; it may be a
     string which is the name of a defined system value; these names are
     specified in a number of standards (POSIX.1, Unix 95, Unix 98, and
     others).  Some platforms define additional names as well.  The
     names known to the host operating system are given in the
     ‘pathconf_names’ dictionary.  For configuration variables not
     included in that mapping, passing an integer for 'name' is also
     accepted.

     If 'name' is a string and is not known, *note ValueError: 1e7. is
     raised.  If a specific value for 'name' is not supported by the
     host system, even if it is included in ‘pathconf_names’, an *note
     OSError: 350. is raised with *note errno.EINVAL: 18f4. for the
     error number.

     As of Python 3.3, this is equivalent to ‘os.pathconf(fd, name)’.

     *note 適用: 1c56.：Unix。

 -- 函式: os.fstat (fd)

     Get the status of the file descriptor 'fd'.  Return a *note
     stat_result: 142c. object.

     As of Python 3.3, this is equivalent to ‘os.stat(fd)’.

     也參考
     ......

     The *note stat(): 448. function.

 -- 函式: os.fstatvfs (fd, /)

     Return information about the filesystem containing the file
     associated with file descriptor 'fd', like *note statvfs(): 1094.
     As of Python 3.3, this is equivalent to ‘os.statvfs(fd)’.

     *note 適用: 1c56.：Unix。

 -- 函式: os.fsync (fd)

     Force write of file with filedescriptor 'fd' to disk.  On Unix,
     this calls the native ‘fsync()’ function; on Windows, the MS
     ‘_commit()’ function.

     If you're starting with a buffered Python *note file object: 115b.
     'f', first do ‘f.flush()’, and then do ‘os.fsync(f.fileno())’, to
     ensure that all internal buffers associated with 'f' are written to
     disk.

     *note 適用: 1c56.：Unix、Windows。

 -- 函式: os.ftruncate (fd, length, /)

     Truncate the file corresponding to file descriptor 'fd', so that it
     is at most 'length' bytes in size.  As of Python 3.3, this is
     equivalent to ‘os.truncate(fd, length)’.

     引發一個附帶引數 ‘fd’、‘length’ 的*note 稽核事件: 17bd.
     ‘os.truncate’。

     *note 適用: 1c56.：Unix、Windows。

     在 3.5 版的變更: 新增對 Windows 的支援

 -- 函式: os.get_blocking (fd, /)

     Get the blocking mode of the file descriptor: ‘False’ if the *note
     O_NONBLOCK: de1. flag is set, ‘True’ if the flag is cleared.

     另請參閱 *note set_blocking(): de0. 與 *note
     socket.socket.setblocking(): 2a28.。

     *note 適用: 1c56.：Unix、Windows。

     The function is limited on WASI, see *note WebAssembly 平台: 16e6.
     for more information.

     On Windows, this function is limited to pipes.

     在 3.5 版被加入.

     在 3.12 版的變更: 新增對 Windows 上的 pipe 支援。

 -- 函式: os.grantpt (fd, /)

     Grant access to the slave pseudo-terminal device associated with
     the master pseudo-terminal device to which the file descriptor 'fd'
     refers.  The file descriptor 'fd' is not closed upon failure.

     Calls the C standard library function ‘grantpt()’.

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.13 版被加入.

 -- 函式: os.isatty (fd, /)

     Return ‘True’ if the file descriptor 'fd' is open and connected to
     a tty(-like) device, else ‘False’.

 -- 函式: os.lockf (fd, cmd, len, /)

     Apply, test or remove a POSIX lock on an open file descriptor.
     'fd' is an open file descriptor.  'cmd' specifies the command to
     use - one of *note F_LOCK: 2a29, *note F_TLOCK: 2a2a, *note
     F_ULOCK: 2a2b. or *note F_TEST: 2a2c.  'len' specifies the section
     of the file to lock.

     引發一個附帶引數 ‘fd’、‘cmd’、‘len’ 的*note 稽核事件: 17bd.
     ‘os.lockf’。

     *note 適用: 1c56.：Unix。

     在 3.3 版被加入.

 -- 資料: os.F_LOCK
 -- 資料: os.F_TLOCK
 -- 資料: os.F_ULOCK
 -- 資料: os.F_TEST

     Flags that specify what action *note lockf(): 10ab. will take.

     *note 適用: 1c56.：Unix。

     在 3.3 版被加入.

 -- 函式: os.login_tty (fd, /)

     Prepare the tty of which fd is a file descriptor for a new login
     session.  Make the calling process a session leader; make the tty
     the controlling tty, the stdin, the stdout, and the stderr of the
     calling process; close fd.

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.11 版被加入.

 -- 函式: os.lseek (fd, pos, whence, /)

     Set the current position of file descriptor 'fd' to position 'pos',
     modified by 'whence', and return the new position in bytes relative
     to the start of the file.  Valid values for 'whence' are:

        * *note SEEK_SET: 1225. or ‘0’ - set 'pos' relative to the
          beginning of the file

        * *note SEEK_CUR: 1226. or ‘1’ - set 'pos' relative to the
          current file position

        * *note SEEK_END: 1227. or ‘2’ - set 'pos' relative to the end
          of the file

        * *note SEEK_HOLE: 2a2d. - set 'pos' to the next data location,
          relative to 'pos'

        * *note SEEK_DATA: 2a2e. - set 'pos' to the next data hole,
          relative to 'pos'

     在 3.3 版的變更: Add support for ‘SEEK_HOLE’ and ‘SEEK_DATA’.

 -- 資料: os.SEEK_SET
 -- 資料: os.SEEK_CUR
 -- 資料: os.SEEK_END

     Parameters to the *note lseek(): 10af. function and the *note
     seek(): 1224. method on *note file-like objects: 115b, for whence
     to adjust the file position indicator.

     *note SEEK_SET: 1225.

          Adjust the file position relative to the beginning of the
          file.

     *note SEEK_CUR: 1226.

          Adjust the file position relative to the current file
          position.

     *note SEEK_END: 1227.

          Adjust the file position relative to the end of the file.

     Their values are 0, 1, and 2, respectively.

 -- 資料: os.SEEK_HOLE
 -- 資料: os.SEEK_DATA

     Parameters to the *note lseek(): 10af. function and the *note
     seek(): 1224. method on *note file-like objects: 115b, for seeking
     file data and holes on sparsely allocated files.

     ‘SEEK_DATA’

          Adjust the file offset to the next location containing data,
          relative to the seek position.

     ‘SEEK_HOLE’

          Adjust the file offset to the next location containing a hole,
          relative to the seek position.  A hole is defined as a
          sequence of zeros.

          備註: These operations only make sense for filesystems that
          support them.

     *note 適用: 1c56.：Linux 3.1 以上、macOS、Unix。

     在 3.3 版被加入.

 -- 函式: os.open (path, flags, mode=0o777, *, dir_fd=None)

     Open the file 'path' and set various flags according to 'flags' and
     possibly its mode according to 'mode'.  When computing 'mode', the
     current umask value is first masked out.  Return the file
     descriptor for the newly opened file.  The new file descriptor is
     *note non-inheritable: e9d.

     For a description of the flag and mode values, see the C run-time
     documentation; flag constants (like *note O_RDONLY: 2a2f. and *note
     O_WRONLY: 2a30.) are defined in the *note os: 91. module.  In
     particular, on Windows adding *note O_BINARY: 2a31. is needed to
     open files in binary mode.

     This function can support *note paths relative to directory
     descriptors: 1083. with the 'dir_fd' parameter.

     引發一個附帶引數 ‘path’、‘mode’、‘flags’ 的*note 稽核事件: 17bd.
     ‘open’。

     在 3.4 版的變更: The new file descriptor is now non-inheritable.

          備註: This function is intended for low-level I/O. For normal
          usage, use the built-in function *note open(): 4c0, which
          returns a *note file object: 115b. with ‘read()’ and ‘write()’
          methods (and many more).  To wrap a file descriptor in a file
          object, use *note fdopen(): 1e08.

     在 3.3 版的變更: 新增 'dir_fd' 參數。

     在 3.5 版的變更: If the system call is interrupted and the signal
     handler does not raise an exception, the function now retries the
     system call instead of raising an *note InterruptedError: d2e.
     exception (see PEP 475(1) for the rationale).

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

The following constants are options for the 'flags' parameter to the
*note open(): d38. function.  They can be combined using the bitwise OR
operator ‘|’.  Some of them are not available on all platforms.  For
descriptions of their availability and use, consult the ‘open(2)(2)’
manual page on Unix or the MSDN(3) on Windows.

 -- 資料: os.O_RDONLY
 -- 資料: os.O_WRONLY
 -- 資料: os.O_RDWR
 -- 資料: os.O_APPEND
 -- 資料: os.O_CREAT
 -- 資料: os.O_EXCL
 -- 資料: os.O_TRUNC

     The above constants are available on Unix and Windows.

 -- 資料: os.O_DSYNC
 -- 資料: os.O_RSYNC
 -- 資料: os.O_SYNC
 -- 資料: os.O_NDELAY
 -- 資料: os.O_NONBLOCK
 -- 資料: os.O_NOCTTY
 -- 資料: os.O_CLOEXEC

     The above constants are only available on Unix.

     在 3.3 版的變更: Add *note O_CLOEXEC: 101d. constant.

 -- 資料: os.O_BINARY
 -- 資料: os.O_NOINHERIT
 -- 資料: os.O_SHORT_LIVED
 -- 資料: os.O_TEMPORARY
 -- 資料: os.O_RANDOM
 -- 資料: os.O_SEQUENTIAL
 -- 資料: os.O_TEXT

     The above constants are only available on Windows.

 -- 資料: os.O_EVTONLY
 -- 資料: os.O_FSYNC
 -- 資料: os.O_SYMLINK
 -- 資料: os.O_NOFOLLOW_ANY

     The above constants are only available on macOS.

     在 3.10 版的變更: Add *note O_EVTONLY: 7be, *note O_FSYNC: 7bf,
     *note O_SYMLINK: 7c0. and *note O_NOFOLLOW_ANY: 7c1. constants.

 -- 資料: os.O_ASYNC
 -- 資料: os.O_DIRECT
 -- 資料: os.O_DIRECTORY
 -- 資料: os.O_NOFOLLOW
 -- 資料: os.O_NOATIME
 -- 資料: os.O_PATH
 -- 資料: os.O_TMPFILE
 -- 資料: os.O_SHLOCK
 -- 資料: os.O_EXLOCK

     The above constants are extensions and not present if they are not
     defined by the C library.

     在 3.4 版的變更: Add *note O_PATH: f15. on systems that support it.
     Add *note O_TMPFILE: f16, only available on Linux Kernel 3.11 or
     newer.

 -- 函式: os.openpty ()

     Open a new pseudo-terminal pair.  Return a pair of file descriptors
     ‘(master, slave)’ for the pty and the tty, respectively.  The new
     file descriptors are *note non-inheritable: e9d.  For a (slightly)
     more portable approach, use the *note pty: 9f. module.

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.4 版的變更: The new file descriptors are now non-inheritable.

 -- 函式: os.pipe ()

     Create a pipe.  Return a pair of file descriptors ‘(r, w)’ usable
     for reading and writing, respectively.  The new file descriptor is
     *note non-inheritable: e9d.

     *note 適用: 1c56.：Unix、Windows。

     在 3.4 版的變更: The new file descriptors are now non-inheritable.

 -- 函式: os.pipe2 (flags, /)

     Create a pipe with 'flags' set atomically.  'flags' can be
     constructed by ORing together one or more of these values: *note
     O_NONBLOCK: de1, *note O_CLOEXEC: 101d.  Return a pair of file
     descriptors ‘(r, w)’ usable for reading and writing, respectively.

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.3 版被加入.

 -- 函式: os.posix_fallocate (fd, offset, len, /)

     Ensures that enough disk space is allocated for the file specified
     by 'fd' starting from 'offset' and continuing for 'len' bytes.

     *note 適用: 1c56.：Unix。

     在 3.3 版被加入.

 -- 函式: os.posix_fadvise (fd, offset, len, advice, /)

     Announces an intention to access data in a specific pattern thus
     allowing the kernel to make optimizations.  The advice applies to
     the region of the file specified by 'fd' starting at 'offset' and
     continuing for 'len' bytes.  'advice' is one of *note
     POSIX_FADV_NORMAL: 2a47, *note POSIX_FADV_SEQUENTIAL: 2a48, *note
     POSIX_FADV_RANDOM: 2a49, *note POSIX_FADV_NOREUSE: 2a4a, *note
     POSIX_FADV_WILLNEED: 2a4b. or *note POSIX_FADV_DONTNEED: 2a4c.

     *note 適用: 1c56.：Unix。

     在 3.3 版被加入.

 -- 資料: os.POSIX_FADV_NORMAL
 -- 資料: os.POSIX_FADV_SEQUENTIAL
 -- 資料: os.POSIX_FADV_RANDOM
 -- 資料: os.POSIX_FADV_NOREUSE
 -- 資料: os.POSIX_FADV_WILLNEED
 -- 資料: os.POSIX_FADV_DONTNEED

     Flags that can be used in 'advice' in *note posix_fadvise(): d39.
     that specify the access pattern that is likely to be used.

     *note 適用: 1c56.：Unix。

     在 3.3 版被加入.

 -- 函式: os.pread (fd, n, offset, /)

     Read at most 'n' bytes from file descriptor 'fd' at a position of
     'offset', leaving the file offset unchanged.

     Return a bytestring containing the bytes read.  If the end of the
     file referred to by 'fd' has been reached, an empty bytes object is
     returned.

     *note 適用: 1c56.：Unix。

     在 3.3 版被加入.

 -- 函式: os.posix_openpt (oflag, /)

     Open and return a file descriptor for a master pseudo-terminal
     device.

     Calls the C standard library function ‘posix_openpt()’.  The
     'oflag' argument is used to set file status flags and file access
     modes as specified in the manual page of ‘posix_openpt()’ of your
     system.

     The returned file descriptor is *note non-inheritable: e9d.  If the
     value *note O_CLOEXEC: 101d. is available on the system, it is
     added to 'oflag'.

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.13 版被加入.

 -- 函式: os.preadv (fd, buffers, offset, flags=0, /)

     Read from a file descriptor 'fd' at a position of 'offset' into
     mutable *note bytes-like objects: cd4. 'buffers', leaving the file
     offset unchanged.  Transfer data into each buffer until it is full
     and then move on to the next buffer in the sequence to hold the
     rest of the data.

     The flags argument contains a bitwise OR of zero or more of the
     following flags:

        - *note RWF_HIPRI: 2a4d.

        - *note RWF_NOWAIT: 2a4e.

     Return the total number of bytes actually read which can be less
     than the total capacity of all the objects.

     The operating system may set a limit (*note sysconf(): 2a4f. value
     ‘'SC_IOV_MAX'’) on the number of buffers that can be used.

     Combine the functionality of *note os.readv(): b02. and *note
     os.pread(): b03.

     *note 適用: 1c56.：Linux 2.6.30 以上、FreeBSD 6.0 以上、OpenBSD 2.7
     以上、AIX 7.1 以上。

     Using flags requires Linux >= 4.6.

     在 3.7 版被加入.

 -- 資料: os.RWF_NOWAIT

     Do not wait for data which is not immediately available.  If this
     flag is specified, the system call will return instantly if it
     would have to read data from the backing storage or wait for a
     lock.

     If some data was successfully read, it will return the number of
     bytes read.  If no bytes were read, it will return ‘-1’ and set
     errno to *note errno.EAGAIN: 217c.

     *note 適用: 1c56.：Linux 4.14 以上。

     在 3.7 版被加入.

 -- 資料: os.RWF_HIPRI

     High priority read/write.  Allows block-based filesystems to use
     polling of the device, which provides lower latency, but may use
     additional resources.

     Currently, on Linux, this feature is usable only on a file
     descriptor opened using the *note O_DIRECT: 2a42. flag.

     *note 適用: 1c56.：Linux 4.6 以上。

     在 3.7 版被加入.

 -- 函式: os.ptsname (fd, /)

     Return the name of the slave pseudo-terminal device associated with
     the master pseudo-terminal device to which the file descriptor 'fd'
     refers.  The file descriptor 'fd' is not closed upon failure.

     Calls the reentrant C standard library function ‘ptsname_r()’ if it
     is available; otherwise, the C standard library function
     ‘ptsname()’, which is not guaranteed to be thread-safe, is called.

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.13 版被加入.

 -- 函式: os.pwrite (fd, str, offset, /)

     Write the bytestring in 'str' to file descriptor 'fd' at position
     of 'offset', leaving the file offset unchanged.

     Return the number of bytes actually written.

     *note 適用: 1c56.：Unix。

     在 3.3 版被加入.

 -- 函式: os.pwritev (fd, buffers, offset, flags=0, /)

     Write the 'buffers' contents to file descriptor 'fd' at an offset
     'offset', leaving the file offset unchanged.  'buffers' must be a
     sequence of *note bytes-like objects: cd4.  Buffers are processed
     in array order.  Entire contents of the first buffer is written
     before proceeding to the second, and so on.

     The flags argument contains a bitwise OR of zero or more of the
     following flags:

        - *note RWF_DSYNC: 2a50.

        - *note RWF_SYNC: 2a51.

        - *note RWF_APPEND: 1848.

     Return the total number of bytes actually written.

     The operating system may set a limit (*note sysconf(): 2a4f. value
     ‘'SC_IOV_MAX'’) on the number of buffers that can be used.

     Combine the functionality of *note os.writev(): b05. and *note
     os.pwrite(): b06.

     *note 適用: 1c56.：Linux 2.6.30 以上、FreeBSD 6.0 以上、OpenBSD 2.7
     以上、AIX 7.1 以上。

     Using flags requires Linux >= 4.6.

     在 3.7 版被加入.

 -- 資料: os.RWF_DSYNC

     Provide a per-write equivalent of the *note O_DSYNC: 2a36. *note
     os.open(): d38. flag.  This flag effect applies only to the data
     range written by the system call.

     *note 適用: 1c56.：Linux 4.7 以上。

     在 3.7 版被加入.

 -- 資料: os.RWF_SYNC

     Provide a per-write equivalent of the *note O_SYNC: 2a38. *note
     os.open(): d38. flag.  This flag effect applies only to the data
     range written by the system call.

     *note 適用: 1c56.：Linux 4.7 以上。

     在 3.7 版被加入.

 -- 資料: os.RWF_APPEND

     Provide a per-write equivalent of the *note O_APPEND: 2a33. *note
     os.open(): d38. flag.  This flag is meaningful only for *note
     os.pwritev(): b04, and its effect applies only to the data range
     written by the system call.  The 'offset' argument does not affect
     the write operation; the data is always appended to the end of the
     file.  However, if the 'offset' argument is ‘-1’, the current file
     'offset' is updated.

     *note 適用: 1c56.：Linux 4.16 以上。

     在 3.10 版被加入.

 -- 函式: os.read (fd, n, /)

     Read at most 'n' bytes from file descriptor 'fd'.

     Return a bytestring containing the bytes read.  If the end of the
     file referred to by 'fd' has been reached, an empty bytes object is
     returned.

          備註: This function is intended for low-level I/O and must be
          applied to a file descriptor as returned by *note os.open():
          d38. or *note pipe(): 16df.  To read a "file object" returned
          by the built-in function *note open(): 4c0. or by *note
          popen(): a2a. or *note fdopen(): 1e08, or *note sys.stdin:
          4e2, use its ‘read()’ or ‘readline()’ methods.

     在 3.5 版的變更: If the system call is interrupted and the signal
     handler does not raise an exception, the function now retries the
     system call instead of raising an *note InterruptedError: d2e.
     exception (see PEP 475(4) for the rationale).

 -- 函式: os.sendfile (out_fd, in_fd, offset, count)

 -- 函式: os.sendfile (out_fd, in_fd, offset, count, headers=(),
          trailers=(), flags=0)

     Copy 'count' bytes from file descriptor 'in_fd' to file descriptor
     'out_fd' starting at 'offset'.  Return the number of bytes sent.
     When EOF is reached return ‘0’.

     The first function notation is supported by all platforms that
     define *note sendfile(): ab2.

     On Linux, if 'offset' is given as ‘None’, the bytes are read from
     the current position of 'in_fd' and the position of 'in_fd' is
     updated.

     The second case may be used on macOS and FreeBSD where 'headers'
     and 'trailers' are arbitrary sequences of buffers that are written
     before and after the data from 'in_fd' is written.  It returns the
     same as the first case.

     On macOS and FreeBSD, a value of ‘0’ for 'count' specifies to send
     until the end of 'in_fd' is reached.

     All platforms support sockets as 'out_fd' file descriptor, and some
     platforms allow other types (e.g.  regular file, pipe) as well.

     Cross-platform applications should not use 'headers', 'trailers'
     and 'flags' arguments.

     *note 適用: 1c56.：Unix、非 WASI。

          備註: For a higher-level wrapper of *note sendfile(): ab2, see
          *note socket.socket.sendfile(): dff.

     在 3.3 版被加入.

     在 3.9 版的變更: Parameters 'out' and 'in' was renamed to 'out_fd'
     and 'in_fd'.

 -- 資料: os.SF_NODISKIO
 -- 資料: os.SF_MNOWAIT
 -- 資料: os.SF_SYNC

     Parameters to the *note sendfile(): ab2. function, if the
     implementation supports them.

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.3 版被加入.

 -- 資料: os.SF_NOCACHE

     Parameter to the *note sendfile(): ab2. function, if the
     implementation supports it.  The data won't be cached in the
     virtual memory and will be freed afterwards.

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.11 版被加入.

 -- 函式: os.set_blocking (fd, blocking, /)

     Set the blocking mode of the specified file descriptor.  Set the
     *note O_NONBLOCK: de1. flag if blocking is ‘False’, clear the flag
     otherwise.

     另請參閱 *note get_blocking(): ddf. 與 *note
     socket.socket.setblocking(): 2a28.。

     *note 適用: 1c56.：Unix、Windows。

     The function is limited on WASI, see *note WebAssembly 平台: 16e6.
     for more information.

     On Windows, this function is limited to pipes.

     在 3.5 版被加入.

     在 3.12 版的變更: 新增對 Windows 上的 pipe 支援。

 -- 函式: os.splice (src, dst, count, offset_src=None, offset_dst=None)

     Transfer 'count' bytes from file descriptor 'src', starting from
     offset 'offset_src', to file descriptor 'dst', starting from offset
     'offset_dst'.  At least one of the file descriptors must refer to a
     pipe.  If 'offset_src' is ‘None’, then 'src' is read from the
     current position; respectively for 'offset_dst'.  The offset
     associated to the file descriptor that refers to a pipe must be
     ‘None’.  The files pointed to by 'src' and 'dst' must reside in the
     same filesystem, otherwise an *note OSError: 350. is raised with
     *note errno: 2169. set to *note errno.EXDEV: 2a26.

     This copy is done without the additional cost of transferring data
     from the kernel to user space and then back into the kernel.
     Additionally, some filesystems could implement extra optimizations.
     The copy is done as if both files are opened as binary.

     Upon successful completion, returns the number of bytes spliced to
     or from the pipe.  A return value of 0 means end of input.  If
     'src' refers to a pipe, then this means that there was no data to
     transfer, and it would not make sense to block because there are no
     writers connected to the write end of the pipe.

     *note 適用: 1c56.：Linux 2.6.17 以上且具有 glibc 2.5 以上

     在 3.10 版被加入.

 -- 資料: os.SPLICE_F_MOVE
 -- 資料: os.SPLICE_F_NONBLOCK
 -- 資料: os.SPLICE_F_MORE

     在 3.10 版被加入.

 -- 函式: os.readv (fd, buffers, /)

     Read from a file descriptor 'fd' into a number of mutable *note
     bytes-like objects: cd4. 'buffers'.  Transfer data into each buffer
     until it is full and then move on to the next buffer in the
     sequence to hold the rest of the data.

     Return the total number of bytes actually read which can be less
     than the total capacity of all the objects.

     The operating system may set a limit (*note sysconf(): 2a4f. value
     ‘'SC_IOV_MAX'’) on the number of buffers that can be used.

     *note 適用: 1c56.：Unix。

     在 3.3 版被加入.

 -- 函式: os.tcgetpgrp (fd, /)

     Return the process group associated with the terminal given by 'fd'
     (an open file descriptor as returned by *note os.open(): d38.).

     *note 適用: 1c56.：Unix、非 WASI。

 -- 函式: os.tcsetpgrp (fd, pg, /)

     Set the process group associated with the terminal given by 'fd'
     (an open file descriptor as returned by *note os.open(): d38.) to
     'pg'.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 函式: os.ttyname (fd, /)

     Return a string which specifies the terminal device associated with
     file descriptor 'fd'.  If 'fd' is not associated with a terminal
     device, an exception is raised.

     *note 適用: 1c56.：Unix。

 -- 函式: os.unlockpt (fd, /)

     Unlock the slave pseudo-terminal device associated with the master
     pseudo-terminal device to which the file descriptor 'fd' refers.
     The file descriptor 'fd' is not closed upon failure.

     Calls the C standard library function ‘unlockpt()’.

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.13 版被加入.

 -- 函式: os.write (fd, str, /)

     Write the bytestring in 'str' to file descriptor 'fd'.

     Return the number of bytes actually written.

          備註: This function is intended for low-level I/O and must be
          applied to a file descriptor as returned by *note os.open():
          d38. or *note pipe(): 16df.  To write a "file object" returned
          by the built-in function *note open(): 4c0. or by *note
          popen(): a2a. or *note fdopen(): 1e08, or *note sys.stdout:
          a79. or *note sys.stderr: 8dd, use its ‘write()’ method.

     在 3.5 版的變更: If the system call is interrupted and the signal
     handler does not raise an exception, the function now retries the
     system call instead of raising an *note InterruptedError: d2e.
     exception (see PEP 475(5) for the rationale).

 -- 函式: os.writev (fd, buffers, /)

     Write the contents of 'buffers' to file descriptor 'fd'.  'buffers'
     must be a sequence of *note bytes-like objects: cd4.  Buffers are
     processed in array order.  Entire contents of the first buffer is
     written before proceeding to the second, and so on.

     Returns the total number of bytes actually written.

     The operating system may set a limit (*note sysconf(): 2a4f. value
     ‘'SC_IOV_MAX'’) on the number of buffers that can be used.

     *note 適用: 1c56.：Unix。

     在 3.3 版被加入.

* Menu:

* Querying the size of a terminal::
* Inheritance of File Descriptors::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0475/

   (2) https://manpages.debian.org/open(2)

   (3) https://msdn.microsoft.com/en-us/library/z0kc8e3z.aspx

   (4) https://peps.python.org/pep-0475/

   (5) https://peps.python.org/pep-0475/


File: python.info,  Node: Querying the size of a terminal,  Next: Inheritance of File Descriptors,  Up: File Descriptor Operations

5.16.1.6 Querying the size of a terminal
........................................

在 3.3 版被加入.

 -- 函式: os.get_terminal_size (fd=STDOUT_FILENO, /)

     Return the size of the terminal window as ‘(columns, lines)’, tuple
     of type *note terminal_size: 2760.

     The optional argument ‘fd’ (default ‘STDOUT_FILENO’, or standard
     output) specifies which file descriptor should be queried.

     If the file descriptor is not connected to a terminal, an *note
     OSError: 350. is raised.

     *note shutil.get_terminal_size(): 109b. is the high-level function
     which should normally be used, ‘os.get_terminal_size’ is the
     low-level implementation.

     *note 適用: 1c56.：Unix、Windows。

 -- 類別: os.terminal_size

     A subclass of tuple, holding ‘(columns, lines)’ of the terminal
     window size.

      -- 屬性: columns

          Width of the terminal window in characters.

      -- 屬性: lines

          Height of the terminal window in characters.


File: python.info,  Node: Inheritance of File Descriptors,  Prev: Querying the size of a terminal,  Up: File Descriptor Operations

5.16.1.7 Inheritance of File Descriptors
........................................

在 3.4 版被加入.

A file descriptor has an "inheritable" flag which indicates if the file
descriptor can be inherited by child processes.  Since Python 3.4, file
descriptors created by Python are non-inheritable by default.

On UNIX, non-inheritable file descriptors are closed in child processes
at the execution of a new program, other file descriptors are inherited.

On Windows, non-inheritable handles and file descriptors are closed in
child processes, except for standard streams (file descriptors 0, 1 and
2: stdin, stdout and stderr), which are always inherited.  Using *note
spawn*: 1630. functions, all inheritable handles and all inheritable
file descriptors are inherited.  Using the *note subprocess: c1. module,
all file descriptors except standard streams are closed, and inheritable
handles are only inherited if the 'close_fds' parameter is ‘False’.

On WebAssembly platforms, the file descriptor cannot be modified.

 -- 函式: os.get_inheritable (fd, /)

     Get the "inheritable" flag of the specified file descriptor (a
     boolean).

 -- 函式: os.set_inheritable (fd, inheritable, /)

     Set the "inheritable" flag of the specified file descriptor.

 -- 函式: os.get_handle_inheritable (handle, /)

     Get the "inheritable" flag of the specified handle (a boolean).

     *note 適用: 1c56.：Windows。

 -- 函式: os.set_handle_inheritable (handle, inheritable, /)

     Set the "inheritable" flag of the specified handle.

     *note 適用: 1c56.：Windows。


File: python.info,  Node: Files and Directories,  Next: 行程管理,  Prev: File Descriptor Operations,  Up: os --- 各種作業系統介面

5.16.1.8 Files and Directories
..............................

On some Unix platforms, many of these functions support one or more of
these features:

   * 'specifying a file descriptor:' Normally the 'path' argument
     provided to functions in the *note os: 91. module must be a string
     specifying a file path.  However, some functions now alternatively
     accept an open file descriptor for their 'path' argument.  The
     function will then operate on the file referred to by the
     descriptor.  (For POSIX systems, Python will call the variant of
     the function prefixed with ‘f’ (e.g.  call ‘fchdir’ instead of
     ‘chdir’).)

     You can check whether or not 'path' can be specified as a file
     descriptor for a particular function on your platform using *note
     os.supports_fd: 1095.  If this functionality is unavailable, using
     it will raise a *note NotImplementedError: 20d.

     If the function also supports 'dir_fd' or 'follow_symlinks'
     arguments, it's an error to specify one of those when supplying
     'path' as a file descriptor.

   * 'paths relative to directory descriptors:' If 'dir_fd' is not
     ‘None’, it should be a file descriptor referring to a directory,
     and the path to operate on should be relative; path will then be
     relative to that directory.  If the path is absolute, 'dir_fd' is
     ignored.  (For POSIX systems, Python will call the variant of the
     function with an ‘at’ suffix and possibly prefixed with ‘f’ (e.g.
     call ‘faccessat’ instead of ‘access’).

     You can check whether or not 'dir_fd' is supported for a particular
     function on your platform using *note os.supports_dir_fd: 1090.  If
     it's unavailable, using it will raise a *note NotImplementedError:
     20d.

   * 'not following symlinks:' If 'follow_symlinks' is ‘False’, and the
     last element of the path to operate on is a symbolic link, the
     function will operate on the symbolic link itself rather than the
     file pointed to by the link.  (For POSIX systems, Python will call
     the ‘l...’ variant of the function.)

     You can check whether or not 'follow_symlinks' is supported for a
     particular function on your platform using *note
     os.supports_follow_symlinks: 274b.  If it's unavailable, using it
     will raise a *note NotImplementedError: 20d.

 -- 函式: os.access (path, mode, *, dir_fd=None, effective_ids=False,
          follow_symlinks=True)

     Use the real uid/gid to test for access to 'path'.  Note that most
     operations will use the effective uid/gid, therefore this routine
     can be used in a suid/sgid environment to test if the invoking user
     has the specified access to 'path'.  'mode' should be *note F_OK:
     2a62. to test the existence of 'path', or it can be the inclusive
     OR of one or more of *note R_OK: 2a63, *note W_OK: 2a64, and *note
     X_OK: 2a65. to test permissions.  Return *note True: bb4. if access
     is allowed, *note False: adb. if not.  See the Unix man page
     ‘access(2)(1)’ for more information.

     This function can support specifying *note paths relative to
     directory descriptors: 1083. and *note not following symlinks:
     1084.

     If 'effective_ids' is ‘True’, *note access(): 1085. will perform
     its access checks using the effective uid/gid instead of the real
     uid/gid.  'effective_ids' may not be supported on your platform;
     you can check whether or not it is available using *note
     os.supports_effective_ids: 1096.  If it is unavailable, using it
     will raise a *note NotImplementedError: 20d.

          備註: Using *note access(): 1085. to check if a user is
          authorized to e.g.  open a file before actually doing so using
          *note open(): 4c0. creates a security hole, because the user
          might exploit the short time interval between checking and
          opening the file to manipulate it.  It's preferable to use
          *note EAFP: 2a66. techniques.  For example:

               if os.access("myfile", os.R_OK):
                   with open("myfile") as fp:
                       return fp.read()
               return "some default data"

          is better written as:

               try:
                   fp = open("myfile")
               except PermissionError:
                   return "some default data"
               else:
                   with fp:
                       return fp.read()

          備註: I/O operations may fail even when *note access(): 1085.
          indicates that they would succeed, particularly for operations
          on network filesystems which may have permissions semantics
          beyond the usual POSIX permission-bit model.

     在 3.3 版的變更: 新增 'dir_fd'、'effective_ids' 與
     'follow_symlinks' 參數。

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 資料: os.F_OK
 -- 資料: os.R_OK
 -- 資料: os.W_OK
 -- 資料: os.X_OK

     Values to pass as the 'mode' parameter of *note access(): 1085. to
     test the existence, readability, writability and executability of
     'path', respectively.

 -- 函式: os.chdir (path)

     Change the current working directory to 'path'.

     This function can support *note specifying a file descriptor: b00.
     The descriptor must refer to an opened directory, not an open file.

     This function can raise *note OSError: 350. and subclasses such as
     *note FileNotFoundError: e67, *note PermissionError: ce9, and *note
     NotADirectoryError: ffd.

     引發一個附帶引數 ‘path’ 的*note 稽核事件: 17bd. ‘os.chdir’。

     在 3.3 版的變更: Added support for specifying 'path' as a file
     descriptor on some platforms.

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 函式: os.chflags (path, flags, *, follow_symlinks=True)

     Set the flags of 'path' to the numeric 'flags'.  'flags' may take a
     combination (bitwise OR) of the following values (as defined in the
     *note stat: bc. module):

        * *note stat.UF_NODUMP: 26f1.

        * *note stat.UF_IMMUTABLE: 26f2.

        * *note stat.UF_APPEND: 26f3.

        * *note stat.UF_OPAQUE: 26f4.

        * *note stat.UF_NOUNLINK: 26f5.

        * *note stat.UF_COMPRESSED: 26f6.

        * *note stat.UF_HIDDEN: 26f9.

        * *note stat.SF_ARCHIVED: 26fd.

        * *note stat.SF_IMMUTABLE: 26fe.

        * *note stat.SF_APPEND: 26ff.

        * *note stat.SF_NOUNLINK: 2701.

        * *note stat.SF_SNAPSHOT: 2702.

     This function can support *note not following symlinks: 1084.

     引發一個附帶引數 ‘path’、‘flags’ 的*note 稽核事件: 17bd.
     ‘os.chflags’。

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.3 版的變更: 新增 'follow_symlinks' 參數。

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 函式: os.chmod (path, mode, *, dir_fd=None, follow_symlinks=True)

     Change the mode of 'path' to the numeric 'mode'.  'mode' may take
     one of the following values (as defined in the *note stat: bc.
     module) or bitwise ORed combinations of them:

        * *note stat.S_ISUID: 26dd.

        * *note stat.S_ISGID: 26de.

        * *note stat.S_ENFMT: 26e0.

        * *note stat.S_ISVTX: 26e1.

        * *note stat.S_IREAD: 26ed.

        * *note stat.S_IWRITE: 26ee.

        * *note stat.S_IEXEC: 26ef.

        * *note stat.S_IRWXU: 26e2.

        * *note stat.S_IRUSR: 26e3.

        * *note stat.S_IWUSR: 26e4.

        * *note stat.S_IXUSR: 26e5.

        * *note stat.S_IRWXG: 26e6.

        * *note stat.S_IRGRP: 26e7.

        * *note stat.S_IWGRP: 26e8.

        * *note stat.S_IXGRP: 26df.

        * *note stat.S_IRWXO: 26e9.

        * *note stat.S_IROTH: 26ea.

        * *note stat.S_IWOTH: 26eb.

        * *note stat.S_IXOTH: 26ec.

     This function can support *note specifying a file descriptor: b00,
     *note paths relative to directory descriptors: 1083. and *note not
     following symlinks: 1084.

          備註: Although Windows supports *note chmod(): 200, you can
          only set the file's read-only flag with it (via the
          ‘stat.S_IWRITE’ and ‘stat.S_IREAD’ constants or a
          corresponding integer value).  All other bits are ignored.
          The default value of 'follow_symlinks' is ‘False’ on Windows.

          The function is limited on WASI, see *note WebAssembly 平台:
          16e6. for more information.

     引發一個附帶引數 ‘path’、‘mode’、‘dir_fd’ 的*note 稽核事件: 17bd.
     ‘os.chmod’。

     在 3.3 版的變更: Added support for specifying 'path' as an open
     file descriptor, and the 'dir_fd' and 'follow_symlinks' arguments.

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

     在 3.13 版的變更: Added support for a file descriptor and the
     'follow_symlinks' argument on Windows.

 -- 函式: os.chown (path, uid, gid, *, dir_fd=None,
          follow_symlinks=True)

     Change the owner and group id of 'path' to the numeric 'uid' and
     'gid'.  To leave one of the ids unchanged, set it to -1.

     This function can support *note specifying a file descriptor: b00,
     *note paths relative to directory descriptors: 1083. and *note not
     following symlinks: 1084.

     See *note shutil.chown(): 225. for a higher-level function that
     accepts names in addition to numeric ids.

     引發一個附帶引數 ‘path’、‘uid’、‘gid’、‘dir_fd’ 的*note 稽核事件:
     17bd. ‘os.chown’。

     *note 適用: 1c56.：Unix。

     The function is limited on WASI, see *note WebAssembly 平台: 16e6.
     for more information.

     在 3.3 版的變更: Added support for specifying 'path' as an open
     file descriptor, and the 'dir_fd' and 'follow_symlinks' arguments.

     在 3.6 版的變更: Supports a *note path-like object: ac2.

 -- 函式: os.chroot (path)

     Change the root directory of the current process to 'path'.

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 函式: os.fchdir (fd)

     Change the current working directory to the directory represented
     by the file descriptor 'fd'.  The descriptor must refer to an
     opened directory, not an open file.  As of Python 3.3, this is
     equivalent to ‘os.chdir(fd)’.

     引發一個附帶引數 ‘path’ 的*note 稽核事件: 17bd. ‘os.chdir’。

     *note 適用: 1c56.：Unix。

 -- 函式: os.getcwd ()

     Return a string representing the current working directory.

 -- 函式: os.getcwdb ()

     Return a bytestring representing the current working directory.

     在 3.8 版的變更: The function now uses the UTF-8 encoding on
     Windows, rather than the ANSI code page: see PEP 529(2) for the
     rationale.  The function is no longer deprecated on Windows.

 -- 函式: os.lchflags (path, flags)

     Set the flags of 'path' to the numeric 'flags', like *note
     chflags(): 1086, but do not follow symbolic links.  As of Python
     3.3, this is equivalent to ‘os.chflags(path, flags,
     follow_symlinks=False)’.

     引發一個附帶引數 ‘path’、‘flags’ 的*note 稽核事件: 17bd.
     ‘os.chflags’。

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 函式: os.lchmod (path, mode)

     Change the mode of 'path' to the numeric 'mode'.  If path is a
     symlink, this affects the symlink rather than the target.  See the
     docs for *note chmod(): 200. for possible values of 'mode'.  As of
     Python 3.3, this is equivalent to ‘os.chmod(path, mode,
     follow_symlinks=False)’.

     ‘lchmod()’ is not part of POSIX, but Unix implementations may have
     it if changing the mode of symbolic links is supported.

     引發一個附帶引數 ‘path’、‘mode’、‘dir_fd’ 的*note 稽核事件: 17bd.
     ‘os.chmod’。

     *note Availability: 1c56.: Unix, Windows, not Linux, FreeBSD >=
     1.3, NetBSD >= 1.3, not OpenBSD

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

     在 3.13 版的變更: Added support on Windows.

 -- 函式: os.lchown (path, uid, gid)

     Change the owner and group id of 'path' to the numeric 'uid' and
     'gid'.  This function will not follow symbolic links.  As of Python
     3.3, this is equivalent to ‘os.chown(path, uid, gid,
     follow_symlinks=False)’.

     引發一個附帶引數 ‘path’、‘uid’、‘gid’、‘dir_fd’ 的*note 稽核事件:
     17bd. ‘os.chown’。

     *note 適用: 1c56.：Unix。

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 函式: os.link (src, dst, *, src_dir_fd=None, dst_dir_fd=None,
          follow_symlinks=True)

     Create a hard link pointing to 'src' named 'dst'.

     This function can support specifying 'src_dir_fd' and/or
     'dst_dir_fd' to supply *note paths relative to directory
     descriptors: 1083, and *note not following symlinks: 1084.

     引發一個附帶引數 ‘src’、‘dst’、‘src_dir_fd’、‘dst_dir_fd’ 的*note
     稽核事件: 17bd. ‘os.link’。

     *note 適用: 1c56.：Unix、Windows。

     在 3.2 版的變更: 新支援 Windows。

     在 3.3 版的變更: 新增 'src_dir_fd'、'dst_dir_fd' 與
     'follow_symlinks' 參數。

     在 3.6 版的變更: Accepts a *note path-like object: ac2. for 'src'
     and 'dst'.

 -- 函式: os.listdir (path='.')

     Return a list containing the names of the entries in the directory
     given by 'path'.  The list is in arbitrary order, and does not
     include the special entries ‘'.'’ and ‘'..'’ even if they are
     present in the directory.  If a file is removed from or added to
     the directory during the call of this function, whether a name for
     that file be included is unspecified.

     'path' may be a *note path-like object: ac2.  If 'path' is of type
     ‘bytes’ (directly or indirectly through the *note PathLike: bf8.
     interface), the filenames returned will also be of type ‘bytes’; in
     all other circumstances, they will be of type ‘str’.

     This function can also support *note specifying a file descriptor:
     b00.; the file descriptor must refer to a directory.

     引發一個附帶引數 ‘path’ 的*note 稽核事件: 17bd. ‘os.listdir’。

          備註: To encode ‘str’ filenames to ‘bytes’, use *note
          fsencode(): bfc.

     也參考
     ......

     The *note scandir(): a02. function returns directory entries along
     with file attribute information, giving better performance for many
     common use cases.

     在 3.2 版的變更: The 'path' parameter became optional.

     在 3.3 版的變更: Added support for specifying 'path' as an open
     file descriptor.

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 函式: os.listdrives ()

     Return a list containing the names of drives on a Windows system.

     A drive name typically looks like ‘'C:\\'’.  Not every drive name
     will be associated with a volume, and some may be inaccessible for
     a variety of reasons, including permissions, network connectivity
     or missing media.  This function does not test for access.

     May raise *note OSError: 350. if an error occurs collecting the
     drive names.

     引發一個不附帶引數的*note 稽核事件: 17bd. ‘os.listdrives’。

     *note 適用: 1c56.：Windows。

     在 3.12 版被加入.

 -- 函式: os.listmounts (volume)

     Return a list containing the mount points for a volume on a Windows
     system.

     'volume' must be represented as a GUID path, like those returned by
     *note os.listvolumes(): 446.  Volumes may be mounted in multiple
     locations or not at all.  In the latter case, the list will be
     empty.  Mount points that are not associated with a volume will not
     be returned by this function.

     The mount points return by this function will be absolute paths,
     and may be longer than the drive name.

     Raises *note OSError: 350. if the volume is not recognized or if an
     error occurs collecting the paths.

     引發一個附帶引數 ‘volume’ 的*note 稽核事件: 17bd. ‘os.listmounts’。

     *note 適用: 1c56.：Windows。

     在 3.12 版被加入.

 -- 函式: os.listvolumes ()

     Return a list containing the volumes in the system.

     Volumes are typically represented as a GUID path that looks like
     ‘\\?\Volume{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}\’.  Files can
     usually be accessed through a GUID path, permissions allowing.
     However, users are generally not familiar with them, and so the
     recommended use of this function is to retrieve mount points using
     *note os.listmounts(): 447.

     May raise *note OSError: 350. if an error occurs collecting the
     volumes.

     引發一個不附帶引數的*note 稽核事件: 17bd. ‘os.listvolumes’。

     *note 適用: 1c56.：Windows。

     在 3.12 版被加入.

 -- 函式: os.lstat (path, *, dir_fd=None)

     Perform the equivalent of an ‘lstat()’ system call on the given
     path.  Similar to *note stat(): 448, but does not follow symbolic
     links.  Return a *note stat_result: 142c. object.

     On platforms that do not support symbolic links, this is an alias
     for *note stat(): 448.

     As of Python 3.3, this is equivalent to ‘os.stat(path,
     dir_fd=dir_fd, follow_symlinks=False)’.

     This function can also support *note paths relative to directory
     descriptors: 1083.

     也參考
     ......

     The *note stat(): 448. function.

     在 3.2 版的變更: Added support for Windows 6.0 (Vista) symbolic
     links.

     在 3.3 版的變更: 新增 'dir_fd' 參數。

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

     在 3.8 版的變更: On Windows, now opens reparse points that
     represent another path (name surrogates), including symbolic links
     and directory junctions.  Other kinds of reparse points are
     resolved by the operating system as for *note stat(): 448.

 -- 函式: os.mkdir (path, mode=0o777, *, dir_fd=None)

     Create a directory named 'path' with numeric mode 'mode'.

     If the directory already exists, *note FileExistsError: fc3. is
     raised.  If a parent directory in the path does not exist, *note
     FileNotFoundError: e67. is raised.  On some systems, 'mode' is
     ignored.  Where it is used, the current umask value is first masked
     out.  If bits other than the last 9 (i.e.  the last 3 digits of the
     octal representation of the 'mode') are set, their meaning is
     platform-dependent.  On some platforms, they are ignored and you
     should call *note chmod(): 200. explicitly to set them.

     On Windows, a 'mode' of ‘0o700’ is specifically handled to apply
     access control to the new directory such that only the current user
     and administrators have access.  Other values of 'mode' are
     ignored.

     This function can also support *note paths relative to directory
     descriptors: 1083.

     It is also possible to create temporary directories; see the *note
     tempfile: c9. module's *note tempfile.mkdtemp(): 204. function.

     引發一個附帶引數 ‘path’、‘mode’、‘dir_fd’ 的*note 稽核事件: 17bd.
     ‘os.mkdir’。

     在 3.3 版的變更: 新增 'dir_fd' 參數。

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

     在 3.13 版的變更: Windows now handles a 'mode' of ‘0o700’.

 -- 函式: os.makedirs (name, mode=0o777, exist_ok=False)

     Recursive directory creation function.  Like *note mkdir(): 202,
     but makes all intermediate-level directories needed to contain the
     leaf directory.

     The 'mode' parameter is passed to *note mkdir(): 202. for creating
     the leaf directory; see *note the mkdir() description: 2a69. for
     how it is interpreted.  To set the file permission bits of any
     newly created parent directories you can set the umask before
     invoking *note makedirs(): 203.  The file permission bits of
     existing parent directories are not changed.

     If 'exist_ok' is ‘False’ (the default), a *note FileExistsError:
     fc3. is raised if the target directory already exists.

          備註: *note makedirs(): 203. will become confused if the path
          elements to create include *note pardir: 2a6a. (eg.  ".."  on
          UNIX systems).

     This function handles UNC paths correctly.

     引發一個附帶引數 ‘path’、‘mode’、‘dir_fd’ 的*note 稽核事件: 17bd.
     ‘os.mkdir’。

     在 3.2 版的變更: 新增 'exist_ok' 參數。

     在 3.4.1 版的變更: Before Python 3.4.1, if 'exist_ok' was ‘True’
     and the directory existed, *note makedirs(): 203. would still raise
     an error if 'mode' did not match the mode of the existing
     directory.  Since this behavior was impossible to implement safely,
     it was removed in Python 3.4.1.  See bpo-21082(3).

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

     在 3.7 版的變更: The 'mode' argument no longer affects the file
     permission bits of newly created intermediate-level directories.

 -- 函式: os.mkfifo (path, mode=0o666, *, dir_fd=None)

     Create a FIFO (a named pipe) named 'path' with numeric mode 'mode'.
     The current umask value is first masked out from the mode.

     This function can also support *note paths relative to directory
     descriptors: 1083.

     FIFOs are pipes that can be accessed like regular files.  FIFOs
     exist until they are deleted (for example with *note os.unlink():
     108e.).  Generally, FIFOs are used as rendezvous between "client"
     and "server" type processes: the server opens the FIFO for reading,
     and the client opens it for writing.  Note that *note mkfifo():
     d36. doesn't open the FIFO -- it just creates the rendezvous point.

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.3 版的變更: 新增 'dir_fd' 參數。

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 函式: os.mknod (path, mode=0o600, device=0, *, dir_fd=None)

     Create a filesystem node (file, device special file or named pipe)
     named 'path'.  'mode' specifies both the permissions to use and the
     type of node to be created, being combined (bitwise OR) with one of
     ‘stat.S_IFREG’, ‘stat.S_IFCHR’, ‘stat.S_IFBLK’, and ‘stat.S_IFIFO’
     (those constants are available in *note stat: bc.).  For
     ‘stat.S_IFCHR’ and ‘stat.S_IFBLK’, 'device' defines the newly
     created device special file (probably using *note os.makedev():
     1510.), otherwise it is ignored.

     This function can also support *note paths relative to directory
     descriptors: 1083.

     *note 適用: 1c56.：Unix、非 WASI。

     在 3.3 版的變更: 新增 'dir_fd' 參數。

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 函式: os.major (device, /)

     Extract the device major number from a raw device number (usually
     the ‘st_dev’ or ‘st_rdev’ field from ‘stat’).

 -- 函式: os.minor (device, /)

     Extract the device minor number from a raw device number (usually
     the ‘st_dev’ or ‘st_rdev’ field from ‘stat’).

 -- 函式: os.makedev (major, minor, /)

     Compose a raw device number from the major and minor device
     numbers.

 -- 函式: os.pathconf (path, name)

     Return system configuration information relevant to a named file.
     'name' specifies the configuration value to retrieve; it may be a
     string which is the name of a defined system value; these names are
     specified in a number of standards (POSIX.1, Unix 95, Unix 98, and
     others).  Some platforms define additional names as well.  The
     names known to the host operating system are given in the
     ‘pathconf_names’ dictionary.  For configuration variables not
     included in that mapping, passing an integer for 'name' is also
     accepted.

     If 'name' is a string and is not known, *note ValueError: 1e7. is
     raised.  If a specific value for 'name' is not supported by the
     host system, even if it is included in ‘pathconf_names’, an *note
     OSError: 350. is raised with *note errno.EINVAL: 18f4. for the
     error number.

     This function can support *note specifying a file descriptor: b00.

     *note 適用: 1c56.：Unix。

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 資料: os.pathconf_names

     Dictionary mapping names accepted by *note pathconf(): 1093. and
     *note fpathconf(): 2a27. to the integer values defined for those
     names by the host operating system.  This can be used to determine
     the set of names known to the system.

     *note 適用: 1c56.：Unix。

 -- 函式: os.readlink (path, *, dir_fd=None)

     Return a string representing the path to which the symbolic link
     points.  The result may be either an absolute or relative pathname;
     if it is relative, it may be converted to an absolute pathname
     using ‘os.path.join(os.path.dirname(path), result)’.

     If the 'path' is a string object (directly or indirectly through a
     *note PathLike: bf8. interface), the result will also be a string
     object, and the call may raise a UnicodeDecodeError.  If the 'path'
     is a bytes object (direct or indirectly), the result will be a
     bytes object.

     This function can also support *note paths relative to directory
     descriptors: 1083.

     When trying to resolve a path that may contain links, use *note
     realpath(): 20a. to properly handle recursion and platform
     differences.

     *note 適用: 1c56.：Unix、Windows。

     在 3.2 版的變更: Added support for Windows 6.0 (Vista) symbolic
     links.

     在 3.3 版的變更: 新增 'dir_fd' 參數。

     在 3.6 版的變更: Accepts a *note path-like object: ac2. on Unix.

     在 3.8 版的變更: Accepts a *note path-like object: ac2. and a bytes
     object on Windows.

     Added support for directory junctions, and changed to return the
     substitution path (which typically includes ‘\\?\’ prefix) rather
     than the optional "print name" field that was previously returned.

 -- 函式: os.remove (path, *, dir_fd=None)

     Remove (delete) the file 'path'.  If 'path' is a directory, an
     *note OSError: 350. is raised.  Use *note rmdir(): 108c. to remove
     directories.  If the file does not exist, a *note
     FileNotFoundError: e67. is raised.

     This function can support *note paths relative to directory
     descriptors: 1083.

     On Windows, attempting to remove a file that is in use causes an
     exception to be raised; on Unix, the directory entry is removed but
     the storage allocated to the file is not made available until the
     original file is no longer in use.

     This function is semantically identical to *note unlink(): 108e.

     引發一個附帶引數 ‘path’、‘dir_fd’ 的*note 稽核事件: 17bd.
     ‘os.remove’。

     在 3.3 版的變更: 新增 'dir_fd' 參數。

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 函式: os.removedirs (name)

     Remove directories recursively.  Works like *note rmdir(): 108c.
     except that, if the leaf directory is successfully removed, *note
     removedirs(): 2a6c. tries to successively remove every parent
     directory mentioned in 'path' until an error is raised (which is
     ignored, because it generally means that a parent directory is not
     empty).  For example, ‘os.removedirs('foo/bar/baz')’ will first
     remove the directory ‘'foo/bar/baz'’, and then remove ‘'foo/bar'’
     and ‘'foo'’ if they are empty.  Raises *note OSError: 350. if the
     leaf directory could not be successfully removed.

     引發一個附帶引數 ‘path’、‘dir_fd’ 的*note 稽核事件: 17bd.
     ‘os.remove’。

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 函式: os.rename (src, dst, *, src_dir_fd=None, dst_dir_fd=None)

     Rename the file or directory 'src' to 'dst'.  If 'dst' exists, the
     operation will fail with an *note OSError: 350. subclass in a
     number of cases:

     On Windows, if 'dst' exists a *note FileExistsError: fc3. is always
     raised.  The operation may fail if 'src' and 'dst' are on different
     filesystems.  Use *note shutil.move(): 9ff. to support moves to a
     different filesystem.

     On Unix, if 'src' is a file and 'dst' is a directory or vice-versa,
     an *note IsADirectoryError: ffc. or a *note NotADirectoryError:
     ffd. will be raised respectively.  If both are directories and
     'dst' is empty, 'dst' will be silently replaced.  If 'dst' is a
     non-empty directory, an *note OSError: 350. is raised.  If both are
     files, 'dst' will be replaced silently if the user has permission.
     The operation may fail on some Unix flavors if 'src' and 'dst' are
     on different filesystems.  If successful, the renaming will be an
     atomic operation (this is a POSIX requirement).

     This function can support specifying 'src_dir_fd' and/or
     'dst_dir_fd' to supply *note paths relative to directory
     descriptors: 1083.

     If you want cross-platform overwriting of the destination, use
     *note replace(): 108b.

     引發一個附帶引數 ‘src’、‘dst’、‘src_dir_fd’、‘dst_dir_fd’ 的*note
     稽核事件: 17bd. ‘os.rename’。

     在 3.3 版的變更: 新增 'src_dir_fd' 與 'dst_dir_fd' 參數。

     在 3.6 版的變更: Accepts a *note path-like object: ac2. for 'src'
     and 'dst'.

 -- 函式: os.renames (old, new)

     Recursive directory or file renaming function.  Works like *note
     rename(): 108a, except creation of any intermediate directories
     needed to make the new pathname good is attempted first.  After the
     rename, directories corresponding to rightmost path segments of the
     old name will be pruned away using *note removedirs(): 2a6c.

          備註: This function can fail with the new directory structure
          made if you lack permissions needed to remove the leaf
          directory or file.

     引發一個附帶引數 ‘src’、‘dst’、‘src_dir_fd’、‘dst_dir_fd’ 的*note
     稽核事件: 17bd. ‘os.rename’。

     在 3.6 版的變更: Accepts a *note path-like object: ac2. for 'old'
     and 'new'.

 -- 函式: os.replace (src, dst, *, src_dir_fd=None, dst_dir_fd=None)

     Rename the file or directory 'src' to 'dst'.  If 'dst' is a
     non-empty directory, *note OSError: 350. will be raised.  If 'dst'
     exists and is a file, it will be replaced silently if the user has
     permission.  The operation may fail if 'src' and 'dst' are on
     different filesystems.  If successful, the renaming will be an
     atomic operation (this is a POSIX requirement).

     This function can support specifying 'src_dir_fd' and/or
     'dst_dir_fd' to supply *note paths relative to directory
     descriptors: 1083.

     引發一個附帶引數 ‘src’、‘dst’、‘src_dir_fd’、‘dst_dir_fd’ 的*note
     稽核事件: 17bd. ‘os.rename’。

     在 3.3 版被加入.

     在 3.6 版的變更: Accepts a *note path-like object: ac2. for 'src'
     and 'dst'.

 -- 函式: os.rmdir (path, *, dir_fd=None)

     Remove (delete) the directory 'path'.  If the directory does not
     exist or is not empty, a *note FileNotFoundError: e67. or an *note
     OSError: 350. is raised respectively.  In order to remove whole
     directory trees, *note shutil.rmtree(): 2d2. can be used.

     This function can support *note paths relative to directory
     descriptors: 1083.

     引發一個附帶引數 ‘path’、‘dir_fd’ 的*note 稽核事件: 17bd.
     ‘os.rmdir’。

     在 3.3 版的變更: 新增 'dir_fd' 參數。

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 函式: os.scandir (path='.')

     Return an iterator of *note os.DirEntry: 443. objects corresponding
     to the entries in the directory given by 'path'.  The entries are
     yielded in arbitrary order, and the special entries ‘'.'’ and
     ‘'..'’ are not included.  If a file is removed from or added to the
     directory after creating the iterator, whether an entry for that
     file be included is unspecified.

     Using *note scandir(): a02. instead of *note listdir(): 1092. can
     significantly increase the performance of code that also needs file
     type or file attribute information, because *note os.DirEntry: 443.
     objects expose this information if the operating system provides it
     when scanning a directory.  All *note os.DirEntry: 443. methods may
     perform a system call, but *note is_dir(): 2a6e. and *note
     is_file(): d2a. usually only require a system call for symbolic
     links; *note os.DirEntry.stat(): 15f5. always requires a system
     call on Unix but only requires one for symbolic links on Windows.

     'path' may be a *note path-like object: ac2.  If 'path' is of type
     ‘bytes’ (directly or indirectly through the *note PathLike: bf8.
     interface), the type of the *note name: 2a6f. and *note path: 1572.
     attributes of each *note os.DirEntry: 443. will be ‘bytes’; in all
     other circumstances, they will be of type ‘str’.

     This function can also support *note specifying a file descriptor:
     b00.; the file descriptor must refer to a directory.

     引發一個附帶引數 ‘path’ 的*note 稽核事件: 17bd. ‘os.scandir’。

     The *note scandir(): a02. iterator supports the *note context
     manager: 576. protocol and has the following method:

      -- 方法: scandir.close ()

          Close the iterator and free acquired resources.

          This is called automatically when the iterator is exhausted or
          garbage collected, or when an error happens during iterating.
          However it is advisable to call it explicitly or use the *note
          with: 577. statement.

          在 3.6 版被加入.

     The following example shows a simple use of *note scandir(): a02.
     to display all the files (excluding directories) in the given
     'path' that don't start with ‘'.'’.  The ‘entry.is_file()’ call
     will generally not make an additional system call:

          with os.scandir(path) as it:
              for entry in it:
                  if not entry.name.startswith('.') and entry.is_file():
                      print(entry.name)

          備註: On Unix-based systems, *note scandir(): a02. uses the
          system's opendir()(4) and readdir()(5) functions.  On Windows,
          it uses the Win32 FindFirstFileW(6) and FindNextFileW(7)
          functions.

     在 3.5 版被加入.

     在 3.6 版的變更: Added support for the *note context manager: 576.
     protocol and the *note close(): c63. method.  If a *note scandir():
     a02. iterator is neither exhausted nor explicitly closed a *note
     ResourceWarning: 229. will be emitted in its destructor.

     The function accepts a *note path-like object: ac2.

     在 3.7 版的變更: Added support for *note file descriptors: b00. on
     Unix.

 -- 類別: os.DirEntry

     Object yielded by *note scandir(): a02. to expose the file path and
     other file attributes of a directory entry.

     *note scandir(): a02. will provide as much of this information as
     possible without making additional system calls.  When a ‘stat()’
     or ‘lstat()’ system call is made, the ‘os.DirEntry’ object will
     cache the result.

     ‘os.DirEntry’ instances are not intended to be stored in long-lived
     data structures; if you know the file metadata has changed or if a
     long time has elapsed since calling *note scandir(): a02, call
     ‘os.stat(entry.path)’ to fetch up-to-date information.

     Because the ‘os.DirEntry’ methods can make operating system calls,
     they may also raise *note OSError: 350.  If you need very
     fine-grained control over errors, you can catch *note OSError: 350.
     when calling one of the ‘os.DirEntry’ methods and handle as
     appropriate.

     To be directly usable as a *note path-like object: ac2,
     ‘os.DirEntry’ implements the *note PathLike: bf8. interface.

     Attributes and methods on a ‘os.DirEntry’ instance are as follows:

      -- 屬性: name

          The entry's base filename, relative to the *note scandir():
          a02. 'path' argument.

          The *note name: 29ed. attribute will be ‘bytes’ if the *note
          scandir(): a02. 'path' argument is of type ‘bytes’ and ‘str’
          otherwise.  Use *note fsdecode(): bfb. to decode byte
          filenames.

      -- 屬性: path

          The entry's full path name: equivalent to
          ‘os.path.join(scandir_path, entry.name)’ where 'scandir_path'
          is the *note scandir(): a02. 'path' argument.  The path is
          only absolute if the *note scandir(): a02. 'path' argument was
          absolute.  If the *note scandir(): a02. 'path' argument was a
          *note file descriptor: b00, the *note path: 92. attribute is
          the same as the *note name: 29ed. attribute.

          The *note path: 92. attribute will be ‘bytes’ if the *note
          scandir(): a02. 'path' argument is of type ‘bytes’ and ‘str’
          otherwise.  Use *note fsdecode(): bfb. to decode byte
          filenames.

      -- 方法: inode ()

          Return the inode number of the entry.

          The result is cached on the ‘os.DirEntry’ object.  Use
          ‘os.stat(entry.path, follow_symlinks=False).st_ino’ to fetch
          up-to-date information.

          On the first, uncached call, a system call is required on
          Windows but not on Unix.

      -- 方法: is_dir (*, follow_symlinks=True)

          Return ‘True’ if this entry is a directory or a symbolic link
          pointing to a directory; return ‘False’ if the entry is or
          points to any other kind of file, or if it doesn't exist
          anymore.

          If 'follow_symlinks' is ‘False’, return ‘True’ only if this
          entry is a directory (without following symlinks); return
          ‘False’ if the entry is any other kind of file or if it
          doesn't exist anymore.

          The result is cached on the ‘os.DirEntry’ object, with a
          separate cache for 'follow_symlinks' ‘True’ and ‘False’.  Call
          *note os.stat(): 448. along with *note stat.S_ISDIR(): 26c4.
          to fetch up-to-date information.

          On the first, uncached call, no system call is required in
          most cases.  Specifically, for non-symlinks, neither Windows
          or Unix require a system call, except on certain Unix file
          systems, such as network file systems, that return
          ‘dirent.d_type == DT_UNKNOWN’.  If the entry is a symlink, a
          system call will be required to follow the symlink unless
          'follow_symlinks' is ‘False’.

          This method can raise *note OSError: 350, such as *note
          PermissionError: ce9, but *note FileNotFoundError: e67. is
          caught and not raised.

      -- 方法: is_file (*, follow_symlinks=True)

          Return ‘True’ if this entry is a file or a symbolic link
          pointing to a file; return ‘False’ if the entry is or points
          to a directory or other non-file entry, or if it doesn't exist
          anymore.

          If 'follow_symlinks' is ‘False’, return ‘True’ only if this
          entry is a file (without following symlinks); return ‘False’
          if the entry is a directory or other non-file entry, or if it
          doesn't exist anymore.

          The result is cached on the ‘os.DirEntry’ object.  Caching,
          system calls made, and exceptions raised are as per *note
          is_dir(): 2a6e.

      -- 方法: is_symlink ()

          Return ‘True’ if this entry is a symbolic link (even if
          broken); return ‘False’ if the entry points to a directory or
          any kind of file, or if it doesn't exist anymore.

          The result is cached on the ‘os.DirEntry’ object.  Call *note
          os.path.islink(): 9b0. to fetch up-to-date information.

          On the first, uncached call, no system call is required in
          most cases.  Specifically, neither Windows or Unix require a
          system call, except on certain Unix file systems, such as
          network file systems, that return ‘dirent.d_type ==
          DT_UNKNOWN’.

          This method can raise *note OSError: 350, such as *note
          PermissionError: ce9, but *note FileNotFoundError: e67. is
          caught and not raised.

      -- 方法: is_junction ()

          Return ‘True’ if this entry is a junction (even if broken);
          return ‘False’ if the entry points to a regular directory, any
          kind of file, a symlink, or if it doesn't exist anymore.

          The result is cached on the ‘os.DirEntry’ object.  Call *note
          os.path.isjunction(): 44b. to fetch up-to-date information.

          在 3.12 版被加入.

      -- 方法: stat (*, follow_symlinks=True)

          Return a *note stat_result: 142c. object for this entry.  This
          method follows symbolic links by default; to stat a symbolic
          link add the ‘follow_symlinks=False’ argument.

          On Unix, this method always requires a system call.  On
          Windows, it only requires a system call if 'follow_symlinks'
          is ‘True’ and the entry is a reparse point (for example, a
          symbolic link or directory junction).

          On Windows, the ‘st_ino’, ‘st_dev’ and ‘st_nlink’ attributes
          of the *note stat_result: 142c. are always set to zero.  Call
          *note os.stat(): 448. to get these attributes.

          The result is cached on the ‘os.DirEntry’ object, with a
          separate cache for 'follow_symlinks' ‘True’ and ‘False’.  Call
          *note os.stat(): 448. to fetch up-to-date information.

     Note that there is a nice correspondence between several attributes
     and methods of ‘os.DirEntry’ and of *note pathlib.Path: 20e.  In
     particular, the ‘name’ attribute has the same meaning, as do the
     ‘is_dir()’, ‘is_file()’, ‘is_symlink()’, ‘is_junction()’, and
     ‘stat()’ methods.

     在 3.5 版被加入.

     在 3.6 版的變更: Added support for the *note PathLike: bf8.
     interface.  Added support for *note bytes: 1a5. paths on Windows.

     在 3.12 版的變更: The ‘st_ctime’ attribute of a stat result is
     deprecated on Windows.  The file creation time is properly
     available as ‘st_birthtime’, and in the future ‘st_ctime’ may be
     changed to return zero or the metadata change time, if available.

 -- 函式: os.stat (path, *, dir_fd=None, follow_symlinks=True)

     Get the status of a file or a file descriptor.  Perform the
     equivalent of a ‘stat()’ system call on the given path.  'path' may
     be specified as either a string or bytes - directly or indirectly
     through the *note PathLike: bf8. interface - or as an open file
     descriptor.  Return a *note stat_result: 142c. object.

     This function normally follows symlinks; to stat a symlink add the
     argument ‘follow_symlinks=False’, or use *note lstat(): 449.

     This function can support *note specifying a file descriptor: b00.
     and *note not following symlinks: 1084.

     On Windows, passing ‘follow_symlinks=False’ will disable following
     all name-surrogate reparse points, which includes symlinks and
     directory junctions.  Other types of reparse points that do not
     resemble links or that the operating system is unable to follow
     will be opened directly.  When following a chain of multiple links,
     this may result in the original link being returned instead of the
     non-link that prevented full traversal.  To obtain stat results for
     the final path in this case, use the *note os.path.realpath(): 20a.
     function to resolve the path name as far as possible and call *note
     lstat(): 449. on the result.  This does not apply to dangling
     symlinks or junction points, which will raise the usual exceptions.

     範例：

          >>> import os
          >>> statinfo = os.stat('somefile.txt')
          >>> statinfo
          os.stat_result(st_mode=33188, st_ino=7876932, st_dev=234881026,
          st_nlink=1, st_uid=501, st_gid=501, st_size=264, st_atime=1297230295,
          st_mtime=1297230027, st_ctime=1297230027)
          >>> statinfo.st_size
          264

     也參考
     ......

     *note fstat(): d32. 和 *note lstat(): 449. 函式。

     在 3.3 版的變更: 新增 'dir_fd' 與 'follow_symlinks' 參數，指定一個
     檔案描述器而非路徑。

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

     在 3.8 版的變更: On Windows, all reparse points that can be
     resolved by the operating system are now followed, and passing
     ‘follow_symlinks=False’ disables following all name surrogate
     reparse points.  If the operating system reaches a reparse point
     that it is not able to follow, 'stat' now returns the information
     for the original path as if ‘follow_symlinks=False’ had been
     specified instead of raising an error.

 -- 類別: os.stat_result

     Object whose attributes correspond roughly to the members of the
     ‘stat’ structure.  It is used for the result of *note os.stat():
     448, *note os.fstat(): d32. and *note os.lstat(): 449.

     屬性：

      -- 屬性: st_mode

          File mode: file type and file mode bits (permissions).

      -- 屬性: st_ino

          Platform dependent, but if non-zero, uniquely identifies the
          file for a given value of ‘st_dev’.  Typically:

             * the inode number on Unix,

             * the file index(8) on Windows

      -- 屬性: st_dev

          Identifier of the device on which this file resides.

      -- 屬性: st_nlink

          Number of hard links.

      -- 屬性: st_uid

          User identifier of the file owner.

      -- 屬性: st_gid

          Group identifier of the file owner.

      -- 屬性: st_size

          Size of the file in bytes, if it is a regular file or a
          symbolic link.  The size of a symbolic link is the length of
          the pathname it contains, without a terminating null byte.

     Timestamps:

      -- 屬性: st_atime

          Time of most recent access expressed in seconds.

      -- 屬性: st_mtime

          Time of most recent content modification expressed in seconds.

      -- 屬性: st_ctime

          Time of most recent metadata change expressed in seconds.

          在 3.12 版的變更: ‘st_ctime’ is deprecated on Windows.  Use
          ‘st_birthtime’ for the file creation time.  In the future,
          ‘st_ctime’ will contain the time of the most recent metadata
          change, as for other platforms.

      -- 屬性: st_atime_ns

          Time of most recent access expressed in nanoseconds as an
          integer.

          在 3.3 版被加入.

      -- 屬性: st_mtime_ns

          Time of most recent content modification expressed in
          nanoseconds as an integer.

          在 3.3 版被加入.

      -- 屬性: st_ctime_ns

          Time of most recent metadata change expressed in nanoseconds
          as an integer.

          在 3.3 版被加入.

          在 3.12 版的變更: ‘st_ctime_ns’ is deprecated on Windows.  Use
          ‘st_birthtime_ns’ for the file creation time.  In the future,
          ‘st_ctime’ will contain the time of the most recent metadata
          change, as for other platforms.

      -- 屬性: st_birthtime

          Time of file creation expressed in seconds.  This attribute is
          not always available, and may raise *note AttributeError: 2f6.

          在 3.12 版的變更: ‘st_birthtime’ is now available on Windows.

      -- 屬性: st_birthtime_ns

          Time of file creation expressed in nanoseconds as an integer.
          This attribute is not always available, and may raise *note
          AttributeError: 2f6.

          在 3.12 版被加入.

          備註: The exact meaning and resolution of the *note st_atime:
          2a78, *note st_mtime: 2909, *note st_ctime: 2a79. and *note
          st_birthtime: 2a7d. attributes depend on the operating system
          and the file system.  For example, on Windows systems using
          the FAT32 file systems, *note st_mtime: 2909. has 2-second
          resolution, and *note st_atime: 2a78. has only 1-day
          resolution.  See your operating system documentation for
          details.

          Similarly, although *note st_atime_ns: 2a7a, *note
          st_mtime_ns: 2a7b, *note st_ctime_ns: 2a7c. and *note
          st_birthtime_ns: 2a7e. are always expressed in nanoseconds,
          many systems do not provide nanosecond precision.  On systems
          that do provide nanosecond precision, the floating-point
          object used to store *note st_atime: 2a78, *note st_mtime:
          2909, *note st_ctime: 2a79. and *note st_birthtime: 2a7d.
          cannot preserve all of it, and as such will be slightly
          inexact.  If you need the exact timestamps you should always
          use *note st_atime_ns: 2a7a, *note st_mtime_ns: 2a7b, *note
          st_ctime_ns: 2a7c. and *note st_birthtime_ns: 2a7e.

     On some Unix systems (such as Linux), the following attributes may
     also be available:

      -- 屬性: st_blocks

          Number of 512-byte blocks allocated for file.  This may be
          smaller than *note st_size: 2a77./512 when the file has holes.

      -- 屬性: st_blksize

          "Preferred" blocksize for efficient file system I/O. Writing
          to a file in smaller chunks may cause an inefficient
          read-modify-rewrite.

      -- 屬性: st_rdev

          Type of device if an inode device.

      -- 屬性: st_flags

          User defined flags for file.

     On other Unix systems (such as FreeBSD), the following attributes
     may be available (but may be only filled out if root tries to use
     them):

      -- 屬性: st_gen

          File generation number.

     On Solaris and derivatives, the following attributes may also be
     available:

      -- 屬性: st_fstype

          String that uniquely identifies the type of the filesystem
          that contains the file.

     On macOS systems, the following attributes may also be available:

      -- 屬性: st_rsize

          Real size of the file.

      -- 屬性: st_creator

          Creator of the file.

      -- 屬性: st_type

          File type.

     On Windows systems, the following attributes are also available:

      -- 屬性: st_file_attributes

          Windows file attributes: ‘dwFileAttributes’ member of the
          ‘BY_HANDLE_FILE_INFORMATION’ structure returned by
          ‘GetFileInformationByHandle()’.  See the ‘FILE_ATTRIBUTE_*
          <stat.FILE_ATTRIBUTE_ARCHIVE>’ constants in the *note stat:
          bc. module.

          在 3.5 版被加入.

      -- 屬性: st_reparse_tag

          When *note st_file_attributes: dde. has the *note
          FILE_ATTRIBUTE_REPARSE_POINT: 2711. set, this field contains
          the tag identifying the type of reparse point.  See the *note
          IO_REPARSE_TAG_*: 2716. constants in the *note stat: bc.
          module.

     The standard module *note stat: bc. defines functions and constants
     that are useful for extracting information from a ‘stat’ structure.
     (On Windows, some items are filled with dummy values.)

     For backward compatibility, a *note stat_result: 142c. instance is
     also accessible as a tuple of at least 10 integers giving the most
     important (and portable) members of the ‘stat’ structure, in the
     order *note st_mode: 2a71, *note st_ino: 2a72, *note st_dev: 2a73,
     *note st_nlink: 2a74, *note st_uid: 2a75, *note st_gid: 2a76, *note
     st_size: 2a77, *note st_atime: 2a78, *note st_mtime: 2909, *note
     st_ctime: 2a79.  More items may be added at the end by some
     implementations.  For compatibility with older Python versions,
     accessing *note stat_result: 142c. as a tuple always returns
     integers.

     在 3.5 版的變更: Windows now returns the file index as *note
     st_ino: 2a72. when available.

     在 3.7 版的變更: Added the *note st_fstype: b08. member to
     Solaris/derivatives.

     在 3.8 版的變更: 在 Windows 上新增 *note st_reparse_tag: 2a87. 成員
     。

     在 3.8 版的變更: On Windows, the *note st_mode: 2a71. member now
     identifies special files as ‘S_IFCHR’, ‘S_IFIFO’ or ‘S_IFBLK’ as
     appropriate.

     在 3.12 版的變更: On Windows, *note st_ctime: 2a79. is deprecated.
     Eventually, it will contain the last metadata change time, for
     consistency with other platforms, but for now still contains
     creation time.  Use *note st_birthtime: 2a7d. for the creation
     time.

     On Windows, *note st_ino: 2a72. may now be up to 128 bits,
     depending on the file system.  Previously it would not be above 64
     bits, and larger file identifiers would be arbitrarily packed.

     On Windows, *note st_rdev: 2a81. no longer returns a value.
     Previously it would contain the same as *note st_dev: 2a73, which
     was incorrect.

     在 Windows 上新增 *note st_birthtime: 2a7d. 成員。

 -- 函式: os.statvfs (path)

     Perform a ‘statvfs()’ system call on the given path.  The return
     value is an object whose attributes describe the filesystem on the
     given path, and correspond to the members of the ‘statvfs’
     structure, namely: ‘f_bsize’, ‘f_frsize’, ‘f_blocks’, ‘f_bfree’,
     ‘f_bavail’, ‘f_files’, ‘f_ffree’, ‘f_favail’, ‘f_flag’,
     ‘f_namemax’, ‘f_fsid’.

     Two module-level constants are defined for the ‘f_flag’ attribute's
     bit-flags: if ‘ST_RDONLY’ is set, the filesystem is mounted
     read-only, and if ‘ST_NOSUID’ is set, the semantics of
     setuid/setgid bits are disabled or not supported.

     Additional module-level constants are defined for GNU/glibc based
     systems.  These are ‘ST_NODEV’ (disallow access to device special
     files), ‘ST_NOEXEC’ (disallow program execution), ‘ST_SYNCHRONOUS’
     (writes are synced at once), ‘ST_MANDLOCK’ (allow mandatory locks
     on an FS), ‘ST_WRITE’ (write on file/directory/symlink),
     ‘ST_APPEND’ (append-only file), ‘ST_IMMUTABLE’ (immutable file),
     ‘ST_NOATIME’ (do not update access times), ‘ST_NODIRATIME’ (do not
     update directory access times), ‘ST_RELATIME’ (update atime
     relative to mtime/ctime).

     This function can support *note specifying a file descriptor: b00.

     *note 適用: 1c56.：Unix。

     在 3.2 版的變更: 新增 ‘ST_RDONLY’ 與 ‘ST_NOSUID’ 常數。

     在 3.3 版的變更: Added support for specifying 'path' as an open
     file descriptor.

     在 3.4 版的變更: The ‘ST_NODEV’, ‘ST_NOEXEC’, ‘ST_SYNCHRONOUS’,
     ‘ST_MANDLOCK’, ‘ST_WRITE’, ‘ST_APPEND’, ‘ST_IMMUTABLE’,
     ‘ST_NOATIME’, ‘ST_NODIRATIME’, and ‘ST_RELATIME’ constants were
     added.

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

     在 3.7 版的變更: 新增 ‘f_fsid’ 屬性。

 -- 資料: os.supports_dir_fd

     A *note set: 57d. object indicating which functions in the *note
     os: 91. module accept an open file descriptor for their 'dir_fd'
     parameter.  Different platforms provide different features, and the
     underlying functionality Python uses to implement the 'dir_fd'
     parameter is not available on all platforms Python supports.  For
     consistency's sake, functions that may support 'dir_fd' always
     allow specifying the parameter, but will throw an exception if the
     functionality is used when it's not locally available.  (Specifying
     ‘None’ for 'dir_fd' is always supported on all platforms.)

     To check whether a particular function accepts an open file
     descriptor for its 'dir_fd' parameter, use the ‘in’ operator on
     ‘supports_dir_fd’.  As an example, this expression evaluates to
     ‘True’ if *note os.stat(): 448. accepts open file descriptors for
     'dir_fd' on the local platform:

          os.stat in os.supports_dir_fd

     Currently 'dir_fd' parameters only work on Unix platforms; none of
     them work on Windows.

     在 3.3 版被加入.

 -- 資料: os.supports_effective_ids

     A *note set: 57d. object indicating whether *note os.access():
     1085. permits specifying ‘True’ for its 'effective_ids' parameter
     on the local platform.  (Specifying ‘False’ for 'effective_ids' is
     always supported on all platforms.)  If the local platform supports
     it, the collection will contain *note os.access(): 1085.; otherwise
     it will be empty.

     This expression evaluates to ‘True’ if *note os.access(): 1085.
     supports ‘effective_ids=True’ on the local platform:

          os.access in os.supports_effective_ids

     Currently 'effective_ids' is only supported on Unix platforms; it
     does not work on Windows.

     在 3.3 版被加入.

 -- 資料: os.supports_fd

     A *note set: 57d. object indicating which functions in the *note
     os: 91. module permit specifying their 'path' parameter as an open
     file descriptor on the local platform.  Different platforms provide
     different features, and the underlying functionality Python uses to
     accept open file descriptors as 'path' arguments is not available
     on all platforms Python supports.

     To determine whether a particular function permits specifying an
     open file descriptor for its 'path' parameter, use the ‘in’
     operator on ‘supports_fd’.  As an example, this expression
     evaluates to ‘True’ if *note os.chdir(): 5b2. accepts open file
     descriptors for 'path' on your local platform:

          os.chdir in os.supports_fd

     在 3.3 版被加入.

 -- 資料: os.supports_follow_symlinks

     A *note set: 57d. object indicating which functions in the *note
     os: 91. module accept ‘False’ for their 'follow_symlinks' parameter
     on the local platform.  Different platforms provide different
     features, and the underlying functionality Python uses to implement
     'follow_symlinks' is not available on all platforms Python
     supports.  For consistency's sake, functions that may support
     'follow_symlinks' always allow specifying the parameter, but will
     throw an exception if the functionality is used when it's not
     locally available.  (Specifying ‘True’ for 'follow_symlinks' is
     always supported on all platforms.)

     To check whether a particular function accepts ‘False’ for its
     'follow_symlinks' parameter, use the ‘in’ operator on
     ‘supports_follow_symlinks’.  As an example, this expression
     evaluates to ‘True’ if you may specify ‘follow_symlinks=False’ when
     calling *note os.stat(): 448. on the local platform:

          os.stat in os.supports_follow_symlinks

     在 3.3 版被加入.

 -- 函式: os.symlink (src, dst, target_is_directory=False, *,
          dir_fd=None)

     Create a symbolic link pointing to 'src' named 'dst'.

     On Windows, a symlink represents either a file or a directory, and
     does not morph to the target dynamically.  If the target is
     present, the type of the symlink will be created to match.
     Otherwise, the symlink will be created as a directory if
     'target_is_directory' is ‘True’ or a file symlink (the default)
     otherwise.  On non-Windows platforms, 'target_is_directory' is
     ignored.

     This function can support *note paths relative to directory
     descriptors: 1083.

          備註: On newer versions of Windows 10, unprivileged accounts
          can create symlinks if Developer Mode is enabled.  When
          Developer Mode is not available/enabled, the
          'SeCreateSymbolicLinkPrivilege' privilege is required, or the
          process must be run as an administrator.

          *note OSError: 350. is raised when the function is called by
          an unprivileged user.

     引發一個附帶引數 ‘src’、‘dst’、‘dir_fd’ 的*note 稽核事件: 17bd.
     ‘os.symlink’。

     *note 適用: 1c56.：Unix、Windows。

     The function is limited on WASI, see *note WebAssembly 平台: 16e6.
     for more information.

     在 3.2 版的變更: Added support for Windows 6.0 (Vista) symbolic
     links.

     在 3.3 版的變更: Added the 'dir_fd' parameter, and now allow
     'target_is_directory' on non-Windows platforms.

     在 3.6 版的變更: Accepts a *note path-like object: ac2. for 'src'
     and 'dst'.

     在 3.8 版的變更: Added support for unelevated symlinks on Windows
     with Developer Mode.

 -- 函式: os.sync ()

     Force write of everything to disk.

     *note 適用: 1c56.：Unix。

     在 3.3 版被加入.

 -- 函式: os.truncate (path, length)

     Truncate the file corresponding to 'path', so that it is at most
     'length' bytes in size.

     This function can support *note specifying a file descriptor: b00.

     引發一個附帶引數 ‘path’、‘length’ 的*note 稽核事件: 17bd.
     ‘os.truncate’。

     *note 適用: 1c56.：Unix、Windows。

     在 3.3 版被加入.

     在 3.5 版的變更: 新增對 Windows 的支援

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 函式: os.unlink (path, *, dir_fd=None)

     Remove (delete) the file 'path'.  This function is semantically
     identical to *note remove(): 1089.; the ‘unlink’ name is its
     traditional Unix name.  Please see the documentation for *note
     remove(): 1089. for further information.

     引發一個附帶引數 ‘path’、‘dir_fd’ 的*note 稽核事件: 17bd.
     ‘os.remove’。

     在 3.3 版的變更: 新增 'dir_fd' 參數。

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 函式: os.utime (path, times=None, *[, ns], dir_fd=None,
          follow_symlinks=True)

     Set the access and modified times of the file specified by 'path'.

     *note utime(): 108f. takes two optional parameters, 'times' and
     'ns'.  These specify the times set on 'path' and are used as
     follows:

        - If 'ns' is specified, it must be a 2-tuple of the form
          ‘(atime_ns, mtime_ns)’ where each member is an int expressing
          nanoseconds.

        - If 'times' is not ‘None’, it must be a 2-tuple of the form
          ‘(atime, mtime)’ where each member is an int or float
          expressing seconds.

        - If 'times' is ‘None’ and 'ns' is unspecified, this is
          equivalent to specifying ‘ns=(atime_ns, mtime_ns)’ where both
          times are the current time.

     It is an error to specify tuples for both 'times' and 'ns'.

     Note that the exact times you set here may not be returned by a
     subsequent *note stat(): 448. call, depending on the resolution
     with which your operating system records access and modification
     times; see *note stat(): 448.  The best way to preserve exact times
     is to use the 'st_atime_ns' and 'st_mtime_ns' fields from the *note
     os.stat(): 448. result object with the 'ns' parameter to *note
     utime(): 108f.

     This function can support *note specifying a file descriptor: b00,
     *note paths relative to directory descriptors: 1083. and *note not
     following symlinks: 1084.

     引發一個附帶引數 ‘path’、‘times’、‘ns’、‘dir_fd’ 的*note 稽核事件:
     17bd. ‘os.utime’。

     在 3.3 版的變更: Added support for specifying 'path' as an open
     file descriptor, and the 'dir_fd', 'follow_symlinks', and 'ns'
     parameters.

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 函式: os.walk (top, topdown=True, onerror=None, followlinks=False)

     Generate the file names in a directory tree by walking the tree
     either top-down or bottom-up.  For each directory in the tree
     rooted at directory 'top' (including 'top' itself), it yields a
     3-tuple ‘(dirpath, dirnames, filenames)’.

     'dirpath' is a string, the path to the directory.  'dirnames' is a
     list of the names of the subdirectories in 'dirpath' (including
     symlinks to directories, and excluding ‘'.'’ and ‘'..'’).
     'filenames' is a list of the names of the non-directory files in
     'dirpath'.  Note that the names in the lists contain no path
     components.  To get a full path (which begins with 'top') to a file
     or directory in 'dirpath', do ‘os.path.join(dirpath, name)’.
     Whether or not the lists are sorted depends on the file system.  If
     a file is removed from or added to the 'dirpath' directory during
     generating the lists, whether a name for that file be included is
     unspecified.

     If optional argument 'topdown' is ‘True’ or not specified, the
     triple for a directory is generated before the triples for any of
     its subdirectories (directories are generated top-down).  If
     'topdown' is ‘False’, the triple for a directory is generated after
     the triples for all of its subdirectories (directories are
     generated bottom-up).  No matter the value of 'topdown', the list
     of subdirectories is retrieved before the tuples for the directory
     and its subdirectories are generated.

     When 'topdown' is ‘True’, the caller can modify the 'dirnames' list
     in-place (perhaps using *note del: 16a9. or slice assignment), and
     *note walk(): 451. will only recurse into the subdirectories whose
     names remain in 'dirnames'; this can be used to prune the search,
     impose a specific order of visiting, or even to inform *note
     walk(): 451. about directories the caller creates or renames before
     it resumes *note walk(): 451. again.  Modifying 'dirnames' when
     'topdown' is ‘False’ has no effect on the behavior of the walk,
     because in bottom-up mode the directories in 'dirnames' are
     generated before 'dirpath' itself is generated.

     By default, errors from the *note scandir(): a02. call are ignored.
     If optional argument 'onerror' is specified, it should be a
     function; it will be called with one argument, an *note OSError:
     350. instance.  It can report the error to continue with the walk,
     or raise the exception to abort the walk.  Note that the filename
     is available as the ‘filename’ attribute of the exception object.

     By default, *note walk(): 451. will not walk down into symbolic
     links that resolve to directories.  Set 'followlinks' to ‘True’ to
     visit directories pointed to by symlinks, on systems that support
     them.

          備註: Be aware that setting 'followlinks' to ‘True’ can lead
          to infinite recursion if a link points to a parent directory
          of itself.  *note walk(): 451. does not keep track of the
          directories it visited already.

          備註: If you pass a relative pathname, don't change the
          current working directory between resumptions of *note walk():
          451.  *note walk(): 451. never changes the current directory,
          and assumes that its caller doesn't either.

     This example displays the number of bytes taken by non-directory
     files in each directory under the starting directory, except that
     it doesn't look under any CVS subdirectory:

          import os
          from os.path import join, getsize
          for root, dirs, files in os.walk('python/Lib/email'):
              print(root, "consumes", end=" ")
              print(sum(getsize(join(root, name)) for name in files), end=" ")
              print("bytes in", len(files), "non-directory files")
              if 'CVS' in dirs:
                  dirs.remove('CVS')  # don't visit CVS directories

     In the next example (simple implementation of *note
     shutil.rmtree(): 2d2.), walking the tree bottom-up is essential,
     *note rmdir(): 108c. doesn't allow deleting a directory before the
     directory is empty:

          # Delete everything reachable from the directory named in "top",
          # assuming there are no symbolic links.
          # CAUTION:  This is dangerous!  For example, if top == '/', it
          # could delete all your disk files.
          import os
          for root, dirs, files in os.walk(top, topdown=False):
              for name in files:
                  os.remove(os.path.join(root, name))
              for name in dirs:
                  os.rmdir(os.path.join(root, name))

     引發一個附帶引數 ‘top’、‘topdown’、‘onerror’、‘followlinks’ 的*note
     稽核事件: 17bd. ‘os.walk’。

     在 3.5 版的變更: This function now calls *note os.scandir(): a02.
     instead of *note os.listdir(): 1092, making it faster by reducing
     the number of calls to *note os.stat(): 448.

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 函式: os.fwalk (top='.', topdown=True, onerror=None, *,
          follow_symlinks=False, dir_fd=None)

     This behaves exactly like *note walk(): 451, except that it yields
     a 4-tuple ‘(dirpath, dirnames, filenames, dirfd)’, and it supports
     ‘dir_fd’.

     'dirpath', 'dirnames' and 'filenames' are identical to *note
     walk(): 451. output, and 'dirfd' is a file descriptor referring to
     the directory 'dirpath'.

     This function always supports *note paths relative to directory
     descriptors: 1083. and *note not following symlinks: 1084.  Note
     however that, unlike other functions, the *note fwalk(): aff.
     default value for 'follow_symlinks' is ‘False’.

          備註: Since *note fwalk(): aff. yields file descriptors, those
          are only valid until the next iteration step, so you should
          duplicate them (e.g.  with *note dup(): 18e2.) if you want to
          keep them longer.

     This example displays the number of bytes taken by non-directory
     files in each directory under the starting directory, except that
     it doesn't look under any CVS subdirectory:

          import os
          for root, dirs, files, rootfd in os.fwalk('python/Lib/email'):
              print(root, "consumes", end="")
              print(sum([os.stat(name, dir_fd=rootfd).st_size for name in files]),
                    end="")
              print("bytes in", len(files), "non-directory files")
              if 'CVS' in dirs:
                  dirs.remove('CVS')  # don't visit CVS directories

     In the next example, walking the tree bottom-up is essential: *note
     rmdir(): 108c. doesn't allow deleting a directory before the
     directory is empty:

          # Delete everything reachable from the directory named in "top",
          # assuming there are no symbolic links.
          # CAUTION:  This is dangerous!  For example, if top == '/', it
          # could delete all your disk files.
          import os
          for root, dirs, files, rootfd in os.fwalk(top, topdown=False):
              for name in files:
                  os.unlink(name, dir_fd=rootfd)
              for name in dirs:
                  os.rmdir(name, dir_fd=rootfd)

     引發一個附帶引數 ‘top’、‘topdown’、‘onerror’、‘follow_symlinks’、
     ‘dir_fd’ 的*note 稽核事件: 17bd. ‘os.fwalk’。

     *note 適用: 1c56.：Unix。

     在 3.3 版被加入.

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

     在 3.7 版的變更: 新增對 *note bytes: 1a5. 路徑的支援。

 -- 函式: os.memfd_create (name[, flags=os.MFD_CLOEXEC])

     Create an anonymous file and return a file descriptor that refers
     to it.  'flags' must be one of the ‘os.MFD_*’ constants available
     on the system (or a bitwise ORed combination of them).  By default,
     the new file descriptor is *note non-inheritable: e9d.

     The name supplied in 'name' is used as a filename and will be
     displayed as the target of the corresponding symbolic link in the
     directory ‘/proc/self/fd/’.  The displayed name is always prefixed
     with ‘memfd:’ and serves only for debugging purposes.  Names do not
     affect the behavior of the file descriptor, and as such multiple
     files can have the same name without any side effects.

     *note 適用: 1c56.：Linux 3.17 以上且具有 glibc 2.27 以上。

     在 3.8 版被加入.

 -- 資料: os.MFD_CLOEXEC
 -- 資料: os.MFD_ALLOW_SEALING
 -- 資料: os.MFD_HUGETLB
 -- 資料: os.MFD_HUGE_SHIFT
 -- 資料: os.MFD_HUGE_MASK
 -- 資料: os.MFD_HUGE_64KB
 -- 資料: os.MFD_HUGE_512KB
 -- 資料: os.MFD_HUGE_1MB
 -- 資料: os.MFD_HUGE_2MB
 -- 資料: os.MFD_HUGE_8MB
 -- 資料: os.MFD_HUGE_16MB
 -- 資料: os.MFD_HUGE_32MB
 -- 資料: os.MFD_HUGE_256MB
 -- 資料: os.MFD_HUGE_512MB
 -- 資料: os.MFD_HUGE_1GB
 -- 資料: os.MFD_HUGE_2GB
 -- 資料: os.MFD_HUGE_16GB

     這些旗標可以傳給 *note memfd_create(): 9af.。

     *note 適用: 1c56.：Linux 3.17 以上且具有 glibc 2.27 以上

     ‘MFD_HUGE*’ 旗標僅在 Linux 4.14 以上可用。

     在 3.8 版被加入.

 -- 函式: os.eventfd (initval[, flags=os.EFD_CLOEXEC])

     Create and return an event file descriptor.  The file descriptors
     supports raw *note read(): d3b. and *note write(): d41. with a
     buffer size of 8, *note select(): d46, *note poll(): 2a99. and
     similar.  See man page ‘eventfd(2)(9)’ for more information.  By
     default, the new file descriptor is *note non-inheritable: e9d.

     'initval' is the initial value of the event counter.  The initial
     value must be a 32 bit unsigned integer.  Please note that the
     initial value is limited to a 32 bit unsigned int although the
     event counter is an unsigned 64 bit integer with a maximum value of
     2^64-2.

     'flags' can be constructed from *note EFD_CLOEXEC: 16d3, *note
     EFD_NONBLOCK: 16d4, and *note EFD_SEMAPHORE: 16d5.

     If *note EFD_SEMAPHORE: 16d5. is specified and the event counter is
     non-zero, *note eventfd_read(): 2a9a. returns 1 and decrements the
     counter by one.

     If *note EFD_SEMAPHORE: 16d5. is not specified and the event
     counter is non-zero, *note eventfd_read(): 2a9a. returns the
     current event counter value and resets the counter to zero.

     If the event counter is zero and *note EFD_NONBLOCK: 16d4. is not
     specified, *note eventfd_read(): 2a9a. blocks.

     *note eventfd_write(): 2a9b. increments the event counter.  Write
     blocks if the write operation would increment the counter to a
     value larger than 2^64-2.

     範例：

          import os

          # semaphore with start value '1'
          fd = os.eventfd(1, os.EFD_SEMAPHORE | os.EFC_CLOEXEC)
          try:
              # acquire semaphore
              v = os.eventfd_read(fd)
              try:
                  do_work()
              finally:
                  # release semaphore
                  os.eventfd_write(fd, v)
          finally:
              os.close(fd)

     *note 適用: 1c56.：Linux 2.6.27 以上且具有 glibc 2.8 以上

     在 3.10 版被加入.

 -- 函式: os.eventfd_read (fd)

     Read value from an *note eventfd(): 7bc. file descriptor and return
     a 64 bit unsigned int.  The function does not verify that 'fd' is
     an *note eventfd(): 7bc.

     *note 適用: 1c56.：Linux 2.6.27 以上

     在 3.10 版被加入.

 -- 函式: os.eventfd_write (fd, value)

     Add value to an *note eventfd(): 7bc. file descriptor.  'value'
     must be a 64 bit unsigned int.  The function does not verify that
     'fd' is an *note eventfd(): 7bc.

     *note 適用: 1c56.：Linux 2.6.27 以上

     在 3.10 版被加入.

 -- 資料: os.EFD_CLOEXEC

     Set close-on-exec flag for new *note eventfd(): 7bc. file
     descriptor.

     *note 適用: 1c56.：Linux 2.6.27 以上

     在 3.10 版被加入.

 -- 資料: os.EFD_NONBLOCK

     設定新的 *note eventfd(): 7bc. 檔案描述器的 *note O_NONBLOCK: de1.
     狀態旗標。

     *note 適用: 1c56.：Linux 2.6.27 以上

     在 3.10 版被加入.

 -- 資料: os.EFD_SEMAPHORE

     Provide semaphore-like semantics for reads from an *note eventfd():
     7bc. file descriptor.  On read the internal counter is decremented
     by one.

     *note 適用: 1c56.：Linux 2.6.30 以上

     在 3.10 版被加入.

* Menu:

* Timer File Descriptors::
* Linux extended attributes::

   ---------- Footnotes ----------

   (1) https://manpages.debian.org/access(2)

   (2) https://peps.python.org/pep-0529/

   (3) https://bugs.python.org/issue?@action=redirect&bpo=21082

   (4) 
https://pubs.opengroup.org/onlinepubs/009695399/functions/opendir.html

   (5) 
https://pubs.opengroup.org/onlinepubs/009695399/functions/readdir_r.html

   (6) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa364418(v=vs.85).aspx

   (7) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa364428(v=vs.85).aspx

   (8) https://msdn.microsoft.com/en-us/library/aa363788

   (9) https://manpages.debian.org/eventfd(2)


File: python.info,  Node: Timer File Descriptors,  Next: Linux extended attributes,  Up: Files and Directories

5.16.1.9 Timer File Descriptors
...............................

在 3.13 版被加入.

These functions provide support for Linux's 'timer file descriptor' API.
Naturally, they are all only available on Linux.

 -- 函式: os.timerfd_create (clockid, /, *, flags=0)

     Create and return a timer file descriptor ('timerfd').

     The file descriptor returned by *note timerfd_create(): 1f6.
     supports:

        - *note read(): d3b.

        - *note select(): d46.

        - *note poll(): 2a99.

     The file descriptor's *note read(): d3b. method can be called with
     a buffer size of 8.  If the timer has already expired one or more
     times, *note read(): d3b. returns the number of expirations with
     the host's endianness, which may be converted to an *note int: 23c.
     by ‘int.from_bytes(x, byteorder=sys.byteorder)’.

     *note select(): d46. and *note poll(): 2a99. can be used to wait
     until timer expires and the file descriptor is readable.

     'clockid' must be a valid *note clock ID: 2a9d, as defined in the
     *note time: d7. module:

        - *note time.CLOCK_REALTIME: 63f.

        - *note time.CLOCK_MONOTONIC: b35.

        - *note time.CLOCK_BOOTTIME: b34. (Since Linux 3.15 for
          timerfd_create)

     If 'clockid' is *note time.CLOCK_REALTIME: 63f, a settable
     system-wide real-time clock is used.  If system clock is changed,
     timer setting need to be updated.  To cancel timer when system
     clock is changed, see *note TFD_TIMER_CANCEL_ON_SET: 1fe.

     If 'clockid' is *note time.CLOCK_MONOTONIC: b35, a non-settable
     monotonically increasing clock is used.  Even if the system clock
     is changed, the timer setting will not be affected.

     If 'clockid' is *note time.CLOCK_BOOTTIME: b34, same as *note
     time.CLOCK_MONOTONIC: b35. except it includes any time that the
     system is suspended.

     The file descriptor's behaviour can be modified by specifying a
     'flags' value.  Any of the following variables may used, combined
     using bitwise OR (the ‘|’ operator):

        - *note TFD_NONBLOCK: 1fb.

        - *note TFD_CLOEXEC: 1fc.

     If *note TFD_NONBLOCK: 1fb. is not set as a flag, *note read():
     d3b. blocks until the timer expires.  If it is set as a flag, *note
     read(): d3b. doesn't block, but If there hasn't been an expiration
     since the last call to read, *note read(): d3b. raises *note
     OSError: 350. with ‘errno’ is set to *note errno.EAGAIN: 217c.

     *note TFD_CLOEXEC: 1fc. is always set by Python automatically.

     The file descriptor must be closed with *note os.close(): b18. when
     it is no longer needed, or else the file descriptor will be leaked.

     也參考
     ......

     The ‘timerfd_create(2)(1)’ man page.

     *note 適用: 1c56.：Linux 2.6.27 以上且具有 glibc 2.8 以上

     在 3.13 版被加入.

 -- 函式: os.timerfd_settime (fd, /, *, flags=flags, initial=0.0,
          interval=0.0)

     Alter a timer file descriptor's internal timer.  This function
     operates the same interval timer as *note timerfd_settime_ns():
     1f8.

     'fd' must be a valid timer file descriptor.

     The timer's behaviour can be modified by specifying a 'flags'
     value.  Any of the following variables may used, combined using
     bitwise OR (the ‘|’ operator):

        - *note TFD_TIMER_ABSTIME: 1fd.

        - *note TFD_TIMER_CANCEL_ON_SET: 1fe.

     The timer is disabled by setting 'initial' to zero (‘0’).  If
     'initial' is equal to or greater than zero, the timer is enabled.
     If 'initial' is less than zero, it raises an *note OSError: 350.
     exception with ‘errno’ set to *note errno.EINVAL: 18f4.

     By default the timer will fire when 'initial' seconds have elapsed.
     (If 'initial' is zero, timer will fire immediately.)

     However, if the *note TFD_TIMER_ABSTIME: 1fd. flag is set, the
     timer will fire when the timer's clock (set by 'clockid' in *note
     timerfd_create(): 1f6.) reaches 'initial' seconds.

     The timer's interval is set by the 'interval' *note float: 2c8.  If
     'interval' is zero, the timer only fires once, on the initial
     expiration.  If 'interval' is greater than zero, the timer fires
     every time 'interval' seconds have elapsed since the previous
     expiration.  If 'interval' is less than zero, it raises *note
     OSError: 350. with ‘errno’ set to *note errno.EINVAL: 18f4.

     If the *note TFD_TIMER_CANCEL_ON_SET: 1fe. flag is set along with
     *note TFD_TIMER_ABSTIME: 1fd. and the clock for this timer is *note
     time.CLOCK_REALTIME: 63f, the timer is marked as cancelable if the
     real-time clock is changed discontinuously.  Reading the descriptor
     is aborted with the error ECANCELED.

     Linux manages system clock as UTC. A daylight-savings time
     transition is done by changing time offset only and doesn't cause
     discontinuous system clock change.

     Discontinuous system clock change will be caused by the following
     events:

        - ‘settimeofday’

        - ‘clock_settime’

        - set the system date and time by ‘date’ command

     Return a two-item tuple of (‘next_expiration’, ‘interval’) from the
     previous timer state, before this function executed.

     也參考
     ......

     ‘timerfd_create(2)(2)’, ‘timerfd_settime(2)(3)’,
     ‘settimeofday(2)(4)’, ‘clock_settime(2)(5)’, and ‘date(1)(6)’.

     *note 適用: 1c56.：Linux 2.6.27 以上且具有 glibc 2.8 以上

     在 3.13 版被加入.

 -- 函式: os.timerfd_settime_ns (fd, /, *, flags=0, initial=0,
          interval=0)

     Similar to *note timerfd_settime(): 1f7, but use time as
     nanoseconds.  This function operates the same interval timer as
     *note timerfd_settime(): 1f7.

     *note 適用: 1c56.：Linux 2.6.27 以上且具有 glibc 2.8 以上

     在 3.13 版被加入.

 -- 函式: os.timerfd_gettime (fd, /)

     Return a two-item tuple of floats (‘next_expiration’, ‘interval’).

     ‘next_expiration’ denotes the relative time until next the timer
     next fires, regardless of if the *note TFD_TIMER_ABSTIME: 1fd. flag
     is set.

     ‘interval’ denotes the timer's interval.  If zero, the timer will
     only fire once, after ‘next_expiration’ seconds have elapsed.

     也參考
     ......

     ‘timerfd_gettime(2)(7)’

     *note 適用: 1c56.：Linux 2.6.27 以上且具有 glibc 2.8 以上

     在 3.13 版被加入.

 -- 函式: os.timerfd_gettime_ns (fd, /)

     Similar to *note timerfd_gettime(): 1f9, but return time as
     nanoseconds.

     *note 適用: 1c56.：Linux 2.6.27 以上且具有 glibc 2.8 以上

     在 3.13 版被加入.

 -- 資料: os.TFD_NONBLOCK

     A flag for the *note timerfd_create(): 1f6. function, which sets
     the *note O_NONBLOCK: de1. status flag for the new timer file
     descriptor.  If *note TFD_NONBLOCK: 1fb. is not set as a flag,
     *note read(): d3b. blocks.

     *note 適用: 1c56.：Linux 2.6.27 以上且具有 glibc 2.8 以上

     在 3.13 版被加入.

 -- 資料: os.TFD_CLOEXEC

     A flag for the *note timerfd_create(): 1f6. function, If *note
     TFD_CLOEXEC: 1fc. is set as a flag, set close-on-exec flag for new
     file descriptor.

     *note 適用: 1c56.：Linux 2.6.27 以上且具有 glibc 2.8 以上

     在 3.13 版被加入.

 -- 資料: os.TFD_TIMER_ABSTIME

     A flag for the *note timerfd_settime(): 1f7. and *note
     timerfd_settime_ns(): 1f8. functions.  If this flag is set,
     'initial' is interpreted as an absolute value on the timer's clock
     (in UTC seconds or nanoseconds since the Unix Epoch).

     *note 適用: 1c56.：Linux 2.6.27 以上且具有 glibc 2.8 以上

     在 3.13 版被加入.

 -- 資料: os.TFD_TIMER_CANCEL_ON_SET

     A flag for the *note timerfd_settime(): 1f7. and *note
     timerfd_settime_ns(): 1f8. functions along with *note
     TFD_TIMER_ABSTIME: 1fd.  The timer is cancelled when the time of
     the underlying clock changes discontinuously.

     *note 適用: 1c56.：Linux 2.6.27 以上且具有 glibc 2.8 以上

     在 3.13 版被加入.

   ---------- Footnotes ----------

   (1) https://manpages.debian.org/timerfd_create(2)

   (2) https://manpages.debian.org/timerfd_create(2)

   (3) https://manpages.debian.org/timerfd_settime(2)

   (4) https://manpages.debian.org/settimeofday(2)

   (5) https://manpages.debian.org/clock_settime(2)

   (6) https://manpages.debian.org/date(1)

   (7) https://manpages.debian.org/timerfd_gettime(2)


File: python.info,  Node: Linux extended attributes,  Prev: Timer File Descriptors,  Up: Files and Directories

5.16.1.10 Linux extended attributes
...................................

在 3.3 版被加入.

These functions are all available on Linux only.

 -- 函式: os.getxattr (path, attribute, *, follow_symlinks=True)

     Return the value of the extended filesystem attribute 'attribute'
     for 'path'.  'attribute' can be bytes or str (directly or
     indirectly through the *note PathLike: bf8. interface).  If it is
     str, it is encoded with the filesystem encoding.

     This function can support *note specifying a file descriptor: b00.
     and *note not following symlinks: 1084.

     引發一個附帶引數 ‘path’、‘attribute’ 的*note 稽核事件: 17bd.
     ‘os.getxattr’。

     在 3.6 版的變更: Accepts a *note path-like object: ac2. for 'path'
     and 'attribute'.

 -- 函式: os.listxattr (path=None, *, follow_symlinks=True)

     Return a list of the extended filesystem attributes on 'path'.  The
     attributes in the list are represented as strings decoded with the
     filesystem encoding.  If 'path' is ‘None’, *note listxattr(): 109d.
     will examine the current directory.

     This function can support *note specifying a file descriptor: b00.
     and *note not following symlinks: 1084.

     引發一個附帶引數 ‘path’ 的*note 稽核事件: 17bd. ‘os.listxattr’。

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 函式: os.removexattr (path, attribute, *, follow_symlinks=True)

     Removes the extended filesystem attribute 'attribute' from 'path'.
     'attribute' should be bytes or str (directly or indirectly through
     the *note PathLike: bf8. interface).  If it is a string, it is
     encoded with the *note filesystem encoding and error handler: 4e0.

     This function can support *note specifying a file descriptor: b00.
     and *note not following symlinks: 1084.

     引發一個附帶引數 ‘path’、‘attribute’ 的*note 稽核事件: 17bd.
     ‘os.removexattr’。

     在 3.6 版的變更: Accepts a *note path-like object: ac2. for 'path'
     and 'attribute'.

 -- 函式: os.setxattr (path, attribute, value, flags=0, *,
          follow_symlinks=True)

     Set the extended filesystem attribute 'attribute' on 'path' to
     'value'.  'attribute' must be a bytes or str with no embedded NULs
     (directly or indirectly through the *note PathLike: bf8.
     interface).  If it is a str, it is encoded with the *note
     filesystem encoding and error handler: 4e0.  'flags' may be *note
     XATTR_REPLACE: 2a9f. or *note XATTR_CREATE: 2aa0.  If *note
     XATTR_REPLACE: 2a9f. is given and the attribute does not exist,
     ‘ENODATA’ will be raised.  If *note XATTR_CREATE: 2aa0. is given
     and the attribute already exists, the attribute will not be created
     and ‘EEXISTS’ will be raised.

     This function can support *note specifying a file descriptor: b00.
     and *note not following symlinks: 1084.

          備註: A bug in Linux kernel versions less than 2.6.39 caused
          the flags argument to be ignored on some filesystems.

     引發一個附帶引數 ‘path’、‘attribute’、‘value’、‘flags’ 的*note
     稽核事件: 17bd. ‘os.setxattr’。

     在 3.6 版的變更: Accepts a *note path-like object: ac2. for 'path'
     and 'attribute'.

 -- 資料: os.XATTR_SIZE_MAX

     The maximum size the value of an extended attribute can be.
     Currently, this is 64 KiB on Linux.

 -- 資料: os.XATTR_CREATE

     This is a possible value for the flags argument in *note
     setxattr(): 109f.  It indicates the operation must create an
     attribute.

 -- 資料: os.XATTR_REPLACE

     This is a possible value for the flags argument in *note
     setxattr(): 109f.  It indicates the operation must replace an
     existing attribute.


File: python.info,  Node: 行程管理,  Next: Interface to the scheduler,  Prev: Files and Directories,  Up: os --- 各種作業系統介面

5.16.1.11 行程管理
..................

These functions may be used to create and manage processes.

The various *note exec*: 2aa4. functions take a list of arguments for
the new program loaded into the process.  In each case, the first of
these arguments is passed to the new program as its own name rather than
as an argument a user may have typed on a command line.  For the C
programmer, this is the ‘argv[0]’ passed to a program's ‘main()’.  For
example, ‘os.execv('/bin/echo', ['foo', 'bar'])’ will only print ‘bar’
on standard output; ‘foo’ will seem to be ignored.

 -- 函式: os.abort ()

     Generate a ‘SIGABRT’ signal to the current process.  On Unix, the
     default behavior is to produce a core dump; on Windows, the process
     immediately returns an exit code of ‘3’.  Be aware that calling
     this function will not call the Python signal handler registered
     for ‘SIGABRT’ with *note signal.signal(): 10cd.

 -- 函式: os.add_dll_directory (path)

     Add a path to the DLL search path.

     This search path is used when resolving dependencies for imported
     extension modules (the module itself is resolved through *note
     sys.path: 37f.), and also by *note ctypes: 22.

     Remove the directory by calling 'close()' on the returned object or
     using it in a *note with: 577. statement.

     See the Microsoft documentation(1) for more information about how
     DLLs are loaded.

     引發一個附帶引數 ‘path’ 的*note 稽核事件: 17bd.
     ‘os.add_dll_directory’。

     *note 適用: 1c56.：Windows。

     在 3.8 版被加入: Previous versions of CPython would resolve DLLs
     using the default behavior for the current process.  This led to
     inconsistencies, such as only sometimes searching ‘PATH’ or the
     current working directory, and OS functions such as
     ‘AddDllDirectory’ having no effect.

     In 3.8, the two primary ways DLLs are loaded now explicitly
     override the process-wide behavior to ensure consistency.  See the
     *note porting notes: a41. for information on updating libraries.

 -- 函式: os.execl (path, arg0, arg1, ...)
 -- 函式: os.execle (path, arg0, arg1, ..., env)
 -- 函式: os.execlp (file, arg0, arg1, ...)
 -- 函式: os.execlpe (file, arg0, arg1, ..., env)
 -- 函式: os.execv (path, args)
 -- 函式: os.execve (path, args, env)
 -- 函式: os.execvp (file, args)
 -- 函式: os.execvpe (file, args, env)

     These functions all execute a new program, replacing the current
     process; they do not return.  On Unix, the new executable is loaded
     into the current process, and will have the same process id as the
     caller.  Errors will be reported as *note OSError: 350. exceptions.

     The current process is replaced immediately.  Open file objects and
     descriptors are not flushed, so if there may be data buffered on
     these open files, you should flush them using ‘sys.stdout.flush()’
     or *note os.fsync(): d34. before calling an *note exec*: 2aa4.
     function.

     The "l" and "v" variants of the *note exec*: 2aa4. functions differ
     in how command-line arguments are passed.  The "l" variants are
     perhaps the easiest to work with if the number of parameters is
     fixed when the code is written; the individual parameters simply
     become additional parameters to the ‘execl*()’ functions.  The "v"
     variants are good when the number of parameters is variable, with
     the arguments being passed in a list or tuple as the 'args'
     parameter.  In either case, the arguments to the child process
     should start with the name of the command being run, but this is
     not enforced.

     The variants which include a "p" near the end (*note execlp():
     2aa7, *note execlpe(): 2aa8, *note execvp(): 2aa9, and *note
     execvpe(): 2aaa.) will use the ‘PATH’ environment variable to
     locate the program 'file'.  When the environment is being replaced
     (using one of the *note exec*e: 2aa4. variants, discussed in the
     next paragraph), the new environment is used as the source of the
     ‘PATH’ variable.  The other variants, *note execl(): 2aa4, *note
     execle(): 2aa6, *note execv(): 2a04, and *note execve(): 1091, will
     not use the ‘PATH’ variable to locate the executable; 'path' must
     contain an appropriate absolute or relative path.  Relative paths
     must include at least one slash, even on Windows, as plain names
     will not be resolved.

     For *note execle(): 2aa6, *note execlpe(): 2aa8, *note execve():
     1091, and *note execvpe(): 2aaa. (note that these all end in "e"),
     the 'env' parameter must be a mapping which is used to define the
     environment variables for the new process (these are used instead
     of the current process' environment); the functions *note execl():
     2aa4, *note execlp(): 2aa7, *note execv(): 2a04, and *note
     execvp(): 2aa9. all cause the new process to inherit the
     environment of the current process.

     For *note execve(): 1091. on some platforms, 'path' may also be
     specified as an open file descriptor.  This functionality may not
     be supported on your platform; you can check whether or not it is
     available using *note os.supports_fd: 1095.  If it is unavailable,
     using it will raise a *note NotImplementedError: 20d.

     引發一個附帶引數 ‘path’、‘args’、‘env’ 的*note 稽核事件: 17bd.
     ‘os.exec’。

     *note Availability: 1c56.: Unix, Windows, not WASI, not iOS.

     在 3.3 版的變更: Added support for specifying 'path' as an open
     file descriptor for *note execve(): 1091.

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 函式: os._exit (n)

     Exit the process with status 'n', without calling cleanup handlers,
     flushing stdio buffers, etc.

          備註: The standard way to exit is *note sys.exit(n): 12dd.
          ‘_exit()’ should normally only be used in the child process
          after a *note fork(): 17b.

The following exit codes are defined and can be used with *note _exit():
2174, although they are not required.  These are typically used for
system programs written in Python, such as a mail server's external
command delivery program.

     備註: Some of these may not be available on all Unix platforms,
     since there is some variation.  These constants are defined where
     they are defined by the underlying platform.

 -- 資料: os.EX_OK

     Exit code that means no error occurred.  May be taken from the
     defined value of ‘EXIT_SUCCESS’ on some platforms.  Generally has a
     value of zero.

     *note 適用: 1c56.：Unix、Windows。

 -- 資料: os.EX_USAGE

     Exit code that means the command was used incorrectly, such as when
     the wrong number of arguments are given.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 資料: os.EX_DATAERR

     Exit code that means the input data was incorrect.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 資料: os.EX_NOINPUT

     Exit code that means an input file did not exist or was not
     readable.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 資料: os.EX_NOUSER

     Exit code that means a specified user did not exist.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 資料: os.EX_NOHOST

     Exit code that means a specified host did not exist.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 資料: os.EX_UNAVAILABLE

     Exit code that means that a required service is unavailable.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 資料: os.EX_SOFTWARE

     Exit code that means an internal software error was detected.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 資料: os.EX_OSERR

     Exit code that means an operating system error was detected, such
     as the inability to fork or create a pipe.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 資料: os.EX_OSFILE

     Exit code that means some system file did not exist, could not be
     opened, or had some other kind of error.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 資料: os.EX_CANTCREAT

     Exit code that means a user specified output file could not be
     created.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 資料: os.EX_IOERR

     Exit code that means that an error occurred while doing I/O on some
     file.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 資料: os.EX_TEMPFAIL

     Exit code that means a temporary failure occurred.  This indicates
     something that may not really be an error, such as a network
     connection that couldn't be made during a retryable operation.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 資料: os.EX_PROTOCOL

     Exit code that means that a protocol exchange was illegal, invalid,
     or not understood.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 資料: os.EX_NOPERM

     Exit code that means that there were insufficient permissions to
     perform the operation (but not intended for file system problems).

     *note 適用: 1c56.：Unix、非 WASI。

 -- 資料: os.EX_CONFIG

     Exit code that means that some kind of configuration error
     occurred.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 資料: os.EX_NOTFOUND

     Exit code that means something like "an entry was not found".

     *note 適用: 1c56.：Unix、非 WASI。

 -- 函式: os.fork ()

     Fork a child process.  Return ‘0’ in the child and the child's
     process id in the parent.  If an error occurs *note OSError: 350.
     is raised.

     Note that some platforms including FreeBSD <= 6.3 and Cygwin have
     known issues when using ‘fork()’ from a thread.

     引發一個不附帶引數的*note 稽核事件: 17bd. ‘os.fork’。

          警告: If you use TLS sockets in an application calling
          ‘fork()’, see the warning in the *note ssl: bb. documentation.

          警告: On macOS the use of this function is unsafe when mixed
          with using higher-level system APIs, and that includes using
          *note urllib.request: f4.

     在 3.8 版的變更: Calling ‘fork()’ in a subinterpreter is no longer
     supported (*note RuntimeError: 179. is raised).

     在 3.12 版的變更: If Python is able to detect that your process has
     multiple threads, *note os.fork(): 17b. now raises a *note
     DeprecationWarning: 18b.

     We chose to surface this as a warning, when detectable, to better
     inform developers of a design problem that the POSIX platform
     specifically notes as not supported.  Even in code that 'appears'
     to work, it has never been safe to mix threading with *note
     os.fork(): 17b. on POSIX platforms.  The CPython runtime itself has
     always made API calls that are not safe for use in the child
     process when threads existed in the parent (such as ‘malloc’ and
     ‘free’).

     Users of macOS or users of libc or malloc implementations other
     than those typically found in glibc to date are among those already
     more likely to experience deadlocks running such code.

     See this discussion on fork being incompatible with threads(2) for
     technical details of why we're surfacing this longstanding platform
     compatibility problem to developers.

     *note Availability: 1c56.: POSIX, not WASI, not iOS.

 -- 函式: os.forkpty ()

     Fork a child process, using a new pseudo-terminal as the child's
     controlling terminal.  Return a pair of ‘(pid, fd)’, where 'pid' is
     ‘0’ in the child, the new child's process id in the parent, and
     'fd' is the file descriptor of the master end of the
     pseudo-terminal.  For a more portable approach, use the *note pty:
     9f. module.  If an error occurs *note OSError: 350. is raised.

     引發一個不附帶引數的*note 稽核事件: 17bd. ‘os.forkpty’。

          警告: On macOS the use of this function is unsafe when mixed
          with using higher-level system APIs, and that includes using
          *note urllib.request: f4.

     在 3.8 版的變更: Calling ‘forkpty()’ in a subinterpreter is no
     longer supported (*note RuntimeError: 179. is raised).

     在 3.12 版的變更: If Python is able to detect that your process has
     multiple threads, this now raises a *note DeprecationWarning: 18b.
     See the longer explanation on *note os.fork(): 17b.

     *note Availability: 1c56.: Unix, not WASI, not iOS.

 -- 函式: os.kill (pid, sig, /)

     Send signal 'sig' to the process 'pid'.  Constants for the specific
     signals available on the host platform are defined in the *note
     signal: b4. module.

     Windows: The *note signal.CTRL_C_EVENT: 12f5. and *note
     signal.CTRL_BREAK_EVENT: 12f6. signals are special signals which
     can only be sent to console processes which share a common console
     window, e.g., some subprocesses.  Any other value for 'sig' will
     cause the process to be unconditionally killed by the
     TerminateProcess API, and the exit code will be set to 'sig'.  The
     Windows version of *note kill(): 12f4. additionally takes process
     handles to be killed.

     另請參閱 *note signal.pthread_kill(): 10ca.。

     引發一個附帶引數 ‘pid’、‘sig’ 的*note 稽核事件: 17bd. ‘os.kill’。

     *note Availability: 1c56.: Unix, Windows, not WASI, not iOS.

     在 3.2 版的變更: 新支援 Windows。

 -- 函式: os.killpg (pgid, sig, /)

     Send the signal 'sig' to the process group 'pgid'.

     引發一個附帶引數 ‘pgid’、‘sig’ 的*note 稽核事件: 17bd. ‘os.killpg’。

     *note Availability: 1c56.: Unix, not WASI, not iOS.

 -- 函式: os.nice (increment, /)

     Add 'increment' to the process's "niceness".  Return the new
     niceness.

     *note 適用: 1c56.：Unix、非 WASI。

 -- 函式: os.pidfd_open (pid, flags=0)

     Return a file descriptor referring to the process 'pid' with
     'flags' set.  This descriptor can be used to perform process
     management without races and signals.

     更多細節請見 ‘pidfd_open(2)(3)’ 手冊頁。

     *note 適用: 1c56.：Linux 5.3 以上

     在 3.9 版被加入.

      -- 資料: os.PIDFD_NONBLOCK

          This flag indicates that the file descriptor will be
          non-blocking.  If the process referred to by the file
          descriptor has not yet terminated, then an attempt to wait on
          the file descriptor using ‘waitid(2)(4)’ will immediately
          return the error *note EAGAIN: 217c. rather than blocking.

     *note 適用: 1c56.：Linux 5.10 以上

     在 3.12 版被加入.

 -- 函式: os.plock (op, /)

     Lock program segments into memory.  The value of 'op' (defined in
     ‘<sys/lock.h>’) determines which segments are locked.

     *note Availability: 1c56.: Unix, not WASI, not iOS.

 -- 函式: os.popen (cmd, mode='r', buffering=-1)

     Open a pipe to or from command 'cmd'.  The return value is an open
     file object connected to the pipe, which can be read or written
     depending on whether 'mode' is ‘'r'’ (default) or ‘'w'’.  The
     'buffering' argument have the same meaning as the corresponding
     argument to the built-in *note open(): 4c0. function.  The returned
     file object reads or writes text strings rather than bytes.

     The ‘close’ method returns *note None: 61b. if the subprocess
     exited successfully, or the subprocess's return code if there was
     an error.  On POSIX systems, if the return code is positive it
     represents the return value of the process left-shifted by one
     byte.  If the return code is negative, the process was terminated
     by the signal given by the negated value of the return code.  (For
     example, the return value might be ‘- signal.SIGKILL’ if the
     subprocess was killed.)  On Windows systems, the return value
     contains the signed integer return code from the child process.

     On Unix, *note waitstatus_to_exitcode(): 8c2. can be used to
     convert the ‘close’ method result (exit status) into an exit code
     if it is not ‘None’.  On Windows, the ‘close’ method result is
     directly the exit code (or ‘None’).

     This is implemented using *note subprocess.Popen: 17d.; see that
     class's documentation for more powerful ways to manage and
     communicate with subprocesses.

     *note Availability: 1c56.: not WASI, not iOS.

          備註: The *note Python UTF-8 Mode: 5fc. affects encodings used
          for 'cmd' and pipe contents.

          *note popen(): a2a. is a simple wrapper around *note
          subprocess.Popen: 17d.  Use *note subprocess.Popen: 17d. or
          *note subprocess.run(): b2c. to control options like
          encodings.

 -- 函式: os.posix_spawn (path, argv, env, *, file_actions=None,
          setpgroup=None, resetids=False, setsid=False, setsigmask=(),
          setsigdef=(), scheduler=None)

     Wraps the ‘posix_spawn()’ C library API for use from Python.

     Most users should use *note subprocess.run(): b2c. instead of *note
     posix_spawn(): 205.

     The positional-only arguments 'path', 'args', and 'env' are similar
     to *note execve(): 1091.  'env' is allowed to be ‘None’, in which
     case current process' environment is used.

     The 'path' parameter is the path to the executable file.  The
     'path' should contain a directory.  Use *note posix_spawnp(): 1935.
     to pass an executable file without directory.

     The 'file_actions' argument may be a sequence of tuples describing
     actions to take on specific file descriptors in the child process
     between the C library implementation's ‘fork()’ and ‘exec()’ steps.
     The first item in each tuple must be one of the three type
     indicator listed below describing the remaining tuple elements:

      -- 資料: os.POSIX_SPAWN_OPEN

          (‘os.POSIX_SPAWN_OPEN’, 'fd', 'path', 'flags', 'mode')

          Performs ‘os.dup2(os.open(path, flags, mode), fd)’.

      -- 資料: os.POSIX_SPAWN_CLOSE

          (‘os.POSIX_SPAWN_CLOSE’, 'fd')

          Performs ‘os.close(fd)’.

      -- 資料: os.POSIX_SPAWN_DUP2

          (‘os.POSIX_SPAWN_DUP2’, 'fd', 'new_fd')

          Performs ‘os.dup2(fd, new_fd)’.

      -- 資料: os.POSIX_SPAWN_CLOSEFROM

          (‘os.POSIX_SPAWN_CLOSEFROM’, 'fd')

          Performs ‘os.closerange(fd, INF)’.

     These tuples correspond to the C library
     ‘posix_spawn_file_actions_addopen()’,
     ‘posix_spawn_file_actions_addclose()’,
     ‘posix_spawn_file_actions_adddup2()’, and
     ‘posix_spawn_file_actions_addclosefrom_np()’ API calls used to
     prepare for the ‘posix_spawn()’ call itself.

     The 'setpgroup' argument will set the process group of the child to
     the value specified.  If the value specified is 0, the child's
     process group ID will be made the same as its process ID. If the
     value of 'setpgroup' is not set, the child will inherit the
     parent's process group ID. This argument corresponds to the C
     library ‘POSIX_SPAWN_SETPGROUP’ flag.

     If the 'resetids' argument is ‘True’ it will reset the effective
     UID and GID of the child to the real UID and GID of the parent
     process.  If the argument is ‘False’, then the child retains the
     effective UID and GID of the parent.  In either case, if the
     set-user-ID and set-group-ID permission bits are enabled on the
     executable file, their effect will override the setting of the
     effective UID and GID. This argument corresponds to the C library
     ‘POSIX_SPAWN_RESETIDS’ flag.

     If the 'setsid' argument is ‘True’, it will create a new session ID
     for ‘posix_spawn’.  'setsid' requires ‘POSIX_SPAWN_SETSID’ or
     ‘POSIX_SPAWN_SETSID_NP’ flag.  Otherwise, *note
     NotImplementedError: 20d. is raised.

     The 'setsigmask' argument will set the signal mask to the signal
     set specified.  If the parameter is not used, then the child
     inherits the parent's signal mask.  This argument corresponds to
     the C library ‘POSIX_SPAWN_SETSIGMASK’ flag.

     The 'sigdef' argument will reset the disposition of all signals in
     the set specified.  This argument corresponds to the C library
     ‘POSIX_SPAWN_SETSIGDEF’ flag.

     The 'scheduler' argument must be a tuple containing the (optional)
     scheduler policy and an instance of *note sched_param: 2ac0. with
     the scheduler parameters.  A value of ‘None’ in the place of the
     scheduler policy indicates that is not being provided.  This
     argument is a combination of the C library
     ‘POSIX_SPAWN_SETSCHEDPARAM’ and ‘POSIX_SPAWN_SETSCHEDULER’ flags.

     引發一個附帶引數 ‘path’、‘argv’、‘env’ 的*note 稽核事件: 17bd.
     ‘os.posix_spawn’。

     在 3.8 版被加入.

     在 3.13 版的變更: 'env' parameter accepts ‘None’.
     ‘os.POSIX_SPAWN_CLOSEFROM’ is available on platforms where
     ‘posix_spawn_file_actions_addclosefrom_np()’ exists.

     *note Availability: 1c56.: Unix, not WASI, not iOS.

 -- 函式: os.posix_spawnp (path, argv, env, *, file_actions=None,
          setpgroup=None, resetids=False, setsid=False, setsigmask=(),
          setsigdef=(), scheduler=None)

     Wraps the ‘posix_spawnp()’ C library API for use from Python.

     Similar to *note posix_spawn(): 205. except that the system
     searches for the 'executable' file in the list of directories
     specified by the ‘PATH’ environment variable (in the same way as
     for ‘execvp(3)’).

     引發一個附帶引數 ‘path’、‘argv’、‘env’ 的*note 稽核事件: 17bd.
     ‘os.posix_spawn’。

     在 3.8 版被加入.

     *note Availability: 1c56.: POSIX, not WASI, not iOS.

     見 *note posix_spawn(): 205. 文件。

 -- 函式: os.register_at_fork (*, before=None, after_in_parent=None,
          after_in_child=None)

     Register callables to be executed when a new child process is
     forked using *note os.fork(): 17b. or similar process cloning APIs.
     The parameters are optional and keyword-only.  Each specifies a
     different call point.

        * 'before' is a function called before forking a child process.

        * 'after_in_parent' is a function called from the parent process
          after forking a child process.

        * 'after_in_child' is a function called from the child process.

     These calls are only made if control is expected to return to the
     Python interpreter.  A typical *note subprocess: c1. launch will
     not trigger them as the child is not going to re-enter the
     interpreter.

     Functions registered for execution before forking are called in
     reverse registration order.  Functions registered for execution
     after forking (either in the parent or in the child) are called in
     registration order.

     Note that ‘fork()’ calls made by third-party C code may not call
     those functions, unless it explicitly calls *note
     PyOS_BeforeFork(): b66, *note PyOS_AfterFork_Parent(): b67. and
     *note PyOS_AfterFork_Child(): 3c3.

     There is no way to unregister a function.

     *note Availability: 1c56.: Unix, not WASI, not iOS.

     在 3.7 版被加入.

 -- 函式: os.spawnl (mode, path, ...)
 -- 函式: os.spawnle (mode, path, ..., env)
 -- 函式: os.spawnlp (mode, file, ...)
 -- 函式: os.spawnlpe (mode, file, ..., env)
 -- 函式: os.spawnv (mode, path, args)
 -- 函式: os.spawnve (mode, path, args, env)
 -- 函式: os.spawnvp (mode, file, args)
 -- 函式: os.spawnvpe (mode, file, args, env)

     Execute the program 'path' in a new process.

     (Note that the *note subprocess: c1. module provides more powerful
     facilities for spawning new processes and retrieving their results;
     using that module is preferable to using these functions.  Check
     especially the *note Replacing Older Functions with the subprocess
     Module: 1122. section.)

     If 'mode' is *note P_NOWAIT: 2ac8, this function returns the
     process id of the new process; if 'mode' is *note P_WAIT: 2ac9,
     returns the process's exit code if it exits normally, or ‘-signal’,
     where 'signal' is the signal that killed the process.  On Windows,
     the process id will actually be the process handle, so can be used
     with the *note waitpid(): d40. function.

     Note on VxWorks, this function doesn't return ‘-signal’ when the
     new process is killed.  Instead it raises OSError exception.

     The "l" and "v" variants of the *note spawn*: 1630. functions
     differ in how command-line arguments are passed.  The "l" variants
     are perhaps the easiest to work with if the number of parameters is
     fixed when the code is written; the individual parameters simply
     become additional parameters to the ‘spawnl*()’ functions.  The "v"
     variants are good when the number of parameters is variable, with
     the arguments being passed in a list or tuple as the 'args'
     parameter.  In either case, the arguments to the child process must
     start with the name of the command being run.

     The variants which include a second "p" near the end (*note
     spawnlp(): 2ac2, *note spawnlpe(): 2ac3, *note spawnvp(): 2ac6, and
     *note spawnvpe(): 2ac7.) will use the ‘PATH’ environment variable
     to locate the program 'file'.  When the environment is being
     replaced (using one of the *note spawn*e: 1630. variants, discussed
     in the next paragraph), the new environment is used as the source
     of the ‘PATH’ variable.  The other variants, *note spawnl(): 1630,
     *note spawnle(): 2ac1, *note spawnv(): 2ac4, and *note spawnve():
     2ac5, will not use the ‘PATH’ variable to locate the executable;
     'path' must contain an appropriate absolute or relative path.

     For *note spawnle(): 2ac1, *note spawnlpe(): 2ac3, *note spawnve():
     2ac5, and *note spawnvpe(): 2ac7. (note that these all end in "e"),
     the 'env' parameter must be a mapping which is used to define the
     environment variables for the new process (they are used instead of
     the current process' environment); the functions *note spawnl():
     1630, *note spawnlp(): 2ac2, *note spawnv(): 2ac4, and *note
     spawnvp(): 2ac6. all cause the new process to inherit the
     environment of the current process.  Note that keys and values in
     the 'env' dictionary must be strings; invalid keys or values will
     cause the function to fail, with a return value of ‘127’.

     As an example, the following calls to *note spawnlp(): 2ac2. and
     *note spawnvpe(): 2ac7. are equivalent:

          import os
          os.spawnlp(os.P_WAIT, 'cp', 'cp', 'index.html', '/dev/null')

          L = ['cp', 'index.html', '/dev/null']
          os.spawnvpe(os.P_WAIT, 'cp', L, os.environ)

     引發一個附帶引數 ‘mode’、‘path’、‘args’、‘env’ 的*note 稽核事件:
     17bd. ‘os.spawn’。

     *note Availability: 1c56.: Unix, Windows, not WASI, not iOS.

     *note spawnlp(): 2ac2, *note spawnlpe(): 2ac3, *note spawnvp():
     2ac6. and *note spawnvpe(): 2ac7. are not available on Windows.
     *note spawnle(): 2ac1. and *note spawnve(): 2ac5. are not
     thread-safe on Windows; we advise you to use the *note subprocess:
     c1. module instead.

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 資料: os.P_NOWAIT
 -- 資料: os.P_NOWAITO

     Possible values for the 'mode' parameter to the *note spawn*: 1630.
     family of functions.  If either of these values is given, the *note
     spawn*: 1630. functions will return as soon as the new process has
     been created, with the process id as the return value.

     *note 適用: 1c56.：Unix、Windows。

 -- 資料: os.P_WAIT

     Possible value for the 'mode' parameter to the *note spawn*: 1630.
     family of functions.  If this is given as 'mode', the *note spawn*:
     1630. functions will not return until the new process has run to
     completion and will return the exit code of the process the run is
     successful, or ‘-signal’ if a signal kills the process.

     *note 適用: 1c56.：Unix、Windows。

 -- 資料: os.P_DETACH
 -- 資料: os.P_OVERLAY

     Possible values for the 'mode' parameter to the *note spawn*: 1630.
     family of functions.  These are less portable than those listed
     above.  *note P_DETACH: 2acb. is similar to *note P_NOWAIT: 2ac8,
     but the new process is detached from the console of the calling
     process.  If *note P_OVERLAY: 2acc. is used, the current process
     will be replaced; the *note spawn*: 1630. function will not return.

     *note 適用: 1c56.：Windows。

 -- 函式: os.startfile (path[, operation][, arguments][, cwd][,
          show_cmd])

     Start a file with its associated application.

     When 'operation' is not specified, this acts like double-clicking
     the file in Windows Explorer, or giving the file name as an
     argument to the ‘start’ command from the interactive command shell:
     the file is opened with whatever application (if any) its extension
     is associated.

     When another 'operation' is given, it must be a "command verb" that
     specifies what should be done with the file.  Common verbs
     documented by Microsoft are ‘'open'’, ‘'print'’ and ‘'edit'’ (to be
     used on files) as well as ‘'explore'’ and ‘'find'’ (to be used on
     directories).

     When launching an application, specify 'arguments' to be passed as
     a single string.  This argument may have no effect when using this
     function to launch a document.

     The default working directory is inherited, but may be overridden
     by the 'cwd' argument.  This should be an absolute path.  A
     relative 'path' will be resolved against this argument.

     Use 'show_cmd' to override the default window style.  Whether this
     has any effect will depend on the application being launched.
     Values are integers as supported by the Win32 ‘ShellExecute()’
     function.

     *note startfile(): 17ce. returns as soon as the associated
     application is launched.  There is no option to wait for the
     application to close, and no way to retrieve the application's exit
     status.  The 'path' parameter is relative to the current directory
     or 'cwd'.  If you want to use an absolute path, make sure the first
     character is not a slash (‘'/'’) Use *note pathlib: 93. or the
     *note os.path.normpath(): 12ae. function to ensure that paths are
     properly encoded for Win32.

     To reduce interpreter startup overhead, the Win32 ‘ShellExecute()’
     function is not resolved until this function is first called.  If
     the function cannot be resolved, *note NotImplementedError: 20d.
     will be raised.

     引發一個附帶引數 ‘path’、‘operation’ 的*note 稽核事件: 17bd.
     ‘os.startfile’。

     引發一個附帶引數 ‘path’、‘operation’、‘arguments’、‘cwd’、
     ‘show_cmd’ 的*note 稽核事件: 17bd. ‘os.startfile/2’。

     *note 適用: 1c56.：Windows。

     在 3.10 版的變更: Added the 'arguments', 'cwd' and 'show_cmd'
     arguments, and the ‘os.startfile/2’ audit event.

 -- 函式: os.system (command)

     Execute the command (a string) in a subshell.  This is implemented
     by calling the Standard C function ‘system()’, and has the same
     limitations.  Changes to *note sys.stdin: 4e2, etc.  are not
     reflected in the environment of the executed command.  If 'command'
     generates any output, it will be sent to the interpreter standard
     output stream.  The C standard does not specify the meaning of the
     return value of the C function, so the return value of the Python
     function is system-dependent.

     On Unix, the return value is the exit status of the process encoded
     in the format specified for *note wait(): d3e.

     On Windows, the return value is that returned by the system shell
     after running 'command'.  The shell is given by the Windows
     environment variable ‘COMSPEC’: it is usually ‘cmd.exe’, which
     returns the exit status of the command run; on systems using a
     non-native shell, consult your shell documentation.

     The *note subprocess: c1. module provides more powerful facilities
     for spawning new processes and retrieving their results; using that
     module is preferable to using this function.  See the *note
     Replacing Older Functions with the subprocess Module: 1122. section
     in the *note subprocess: c1. documentation for some helpful
     recipes.

     On Unix, *note waitstatus_to_exitcode(): 8c2. can be used to
     convert the result (exit status) into an exit code.  On Windows,
     the result is directly the exit code.

     引發一個附帶引數 ‘command’ 的*note 稽核事件: 17bd. ‘os.system’。

     *note Availability: 1c56.: Unix, Windows, not WASI, not iOS.

 -- 函式: os.times ()

     Returns the current global process times.  The return value is an
     object with five attributes:

        * ‘user’ - 使用者時間

        * ‘system’ - 系統時間

        * ‘children_user’ - 所有子行程的使用者時間

        * ‘children_system’ - 所有子行程的系統時間

        * ‘elapsed’ - elapsed real time since a fixed point in the past

     For backwards compatibility, this object also behaves like a
     five-tuple containing ‘user’, ‘system’, ‘children_user’,
     ‘children_system’, and ‘elapsed’ in that order.

     See the Unix manual page ‘times(2)(5)’ and times(3)(6) manual page
     on Unix or the GetProcessTimes MSDN(7) on Windows.  On Windows,
     only ‘user’ and ‘system’ are known; the other attributes are zero.

     *note 適用: 1c56.：Unix、Windows。

     在 3.3 版的變更: Return type changed from a tuple to a tuple-like
     object with named attributes.

 -- 函式: os.wait ()

     Wait for completion of a child process, and return a tuple
     containing its pid and exit status indication: a 16-bit number,
     whose low byte is the signal number that killed the process, and
     whose high byte is the exit status (if the signal number is zero);
     the high bit of the low byte is set if a core file was produced.

     If there are no children that could be waited for, *note
     ChildProcessError: ffb. is raised.

     *note waitstatus_to_exitcode(): 8c2. can be used to convert the
     exit status into an exit code.

     *note Availability: 1c56.: Unix, not WASI, not iOS.

     也參考
     ......

     The other ‘wait*()’ functions documented below can be used to wait
     for the completion of a specific child process and have more
     options.  *note waitpid(): d40. is the only one also available on
     Windows.

 -- 函式: os.waitid (idtype, id, options, /)

     Wait for the completion of a child process.

     'idtype' can be *note P_PID: 2acd, *note P_PGID: 2ace, *note P_ALL:
     2acf, or (on Linux) *note P_PIDFD: 8bf.  The interpretation of 'id'
     depends on it; see their individual descriptions.

     'options' is an OR combination of flags.  At least one of *note
     WEXITED: 2ad0, *note WSTOPPED: 2ad1. or *note WCONTINUED: 2ad2. is
     required; *note WNOHANG: 2ad3. and *note WNOWAIT: 2ad4. are
     additional optional flags.

     The return value is an object representing the data contained in
     the ‘siginfo_t’ structure with the following attributes:

        * ‘si_pid’ (process ID)

        * ‘si_uid’ (real user ID of the child)

        * ‘si_signo’ (always *note SIGCHLD: 2ad5.)

        * ‘si_status’ (the exit status or signal number, depending on
          ‘si_code’)

        * ‘si_code’ (see *note CLD_EXITED: 2ad6. for possible values)

     If *note WNOHANG: 2ad3. is specified and there are no matching
     children in the requested state, ‘None’ is returned.  Otherwise, if
     there are no matching children that could be waited for, *note
     ChildProcessError: ffb. is raised.

     *note Availability: 1c56.: Unix, not WASI, not iOS.

     在 3.3 版被加入.

     在 3.13 版的變更: This function is now available on macOS as well.

 -- 函式: os.waitpid (pid, options, /)

     The details of this function differ on Unix and Windows.

     On Unix: Wait for completion of a child process given by process id
     'pid', and return a tuple containing its process id and exit status
     indication (encoded as for *note wait(): d3e.).  The semantics of
     the call are affected by the value of the integer 'options', which
     should be ‘0’ for normal operation.

     If 'pid' is greater than ‘0’, *note waitpid(): d40. requests status
     information for that specific process.  If 'pid' is ‘0’, the
     request is for the status of any child in the process group of the
     current process.  If 'pid' is ‘-1’, the request pertains to any
     child of the current process.  If 'pid' is less than ‘-1’, status
     is requested for any process in the process group ‘-pid’ (the
     absolute value of 'pid').

     'options' is an OR combination of flags.  If it contains *note
     WNOHANG: 2ad3. and there are no matching children in the requested
     state, ‘(0, 0)’ is returned.  Otherwise, if there are no matching
     children that could be waited for, *note ChildProcessError: ffb. is
     raised.  Other options that can be used are *note WUNTRACED: 2ad7.
     and *note WCONTINUED: 2ad2.

     On Windows: Wait for completion of a process given by process
     handle 'pid', and return a tuple containing 'pid', and its exit
     status shifted left by 8 bits (shifting makes cross-platform use of
     the function easier).  A 'pid' less than or equal to ‘0’ has no
     special meaning on Windows, and raises an exception.  The value of
     integer 'options' has no effect.  'pid' can refer to any process
     whose id is known, not necessarily a child process.  The *note
     spawn*: 1630. functions called with *note P_NOWAIT: 2ac8. return
     suitable process handles.

     *note waitstatus_to_exitcode(): 8c2. can be used to convert the
     exit status into an exit code.

     *note Availability: 1c56.: Unix, Windows, not WASI, not iOS.

     在 3.5 版的變更: If the system call is interrupted and the signal
     handler does not raise an exception, the function now retries the
     system call instead of raising an *note InterruptedError: d2e.
     exception (see PEP 475(8) for the rationale).

 -- 函式: os.wait3 (options)

     Similar to *note waitpid(): d40, except no process id argument is
     given and a 3-element tuple containing the child's process id, exit
     status indication, and resource usage information is returned.
     Refer to *note resource.getrusage(): 139e. for details on resource
     usage information.  The 'options' argument is the same as that
     provided to *note waitpid(): d40. and *note wait4(): d3d.

     *note waitstatus_to_exitcode(): 8c2. can be used to convert the
     exit status into an exitcode.

     *note Availability: 1c56.: Unix, not WASI, not iOS.

 -- 函式: os.wait4 (pid, options)

     Similar to *note waitpid(): d40, except a 3-element tuple,
     containing the child's process id, exit status indication, and
     resource usage information is returned.  Refer to *note
     resource.getrusage(): 139e. for details on resource usage
     information.  The arguments to *note wait4(): d3d. are the same as
     those provided to *note waitpid(): d40.

     *note waitstatus_to_exitcode(): 8c2. can be used to convert the
     exit status into an exitcode.

     *note Availability: 1c56.: Unix, not WASI, not iOS.

 -- 資料: os.P_PID
 -- 資料: os.P_PGID
 -- 資料: os.P_ALL
 -- 資料: os.P_PIDFD

     These are the possible values for 'idtype' in *note waitid(): d3f.
     They affect how 'id' is interpreted:

        * ‘P_PID’ - wait for the child whose PID is 'id'.

        * ‘P_PGID’ - wait for any child whose progress group ID is 'id'.

        * ‘P_ALL’ - wait for any child; 'id' is ignored.

        * ‘P_PIDFD’ - wait for the child identified by the file
          descriptor 'id' (a process file descriptor created with *note
          pidfd_open(): 421.).

     *note Availability: 1c56.: Unix, not WASI, not iOS.

          備註: ‘P_PIDFD’ is only available on Linux >= 5.4.

     在 3.3 版被加入.

     在 3.9 版被加入: The ‘P_PIDFD’ constant.

 -- 資料: os.WCONTINUED

     This 'options' flag for *note waitpid(): d40, *note wait3(): d3c,
     *note wait4(): d3d, and *note waitid(): d3f. causes child processes
     to be reported if they have been continued from a job control stop
     since they were last reported.

     *note Availability: 1c56.: Unix, not WASI, not iOS.

 -- 資料: os.WEXITED

     This 'options' flag for *note waitid(): d3f. causes child processes
     that have terminated to be reported.

     The other ‘wait*’ functions always report children that have
     terminated, so this option is not available for them.

     *note Availability: 1c56.: Unix, not WASI, not iOS.

     在 3.3 版被加入.

 -- 資料: os.WSTOPPED

     This 'options' flag for *note waitid(): d3f. causes child processes
     that have been stopped by the delivery of a signal to be reported.

     This option is not available for the other ‘wait*’ functions.

     *note Availability: 1c56.: Unix, not WASI, not iOS.

     在 3.3 版被加入.

 -- 資料: os.WUNTRACED

     This 'options' flag for *note waitpid(): d40, *note wait3(): d3c,
     and *note wait4(): d3d. causes child processes to also be reported
     if they have been stopped but their current state has not been
     reported since they were stopped.

     This option is not available for *note waitid(): d3f.

     *note Availability: 1c56.: Unix, not WASI, not iOS.

 -- 資料: os.WNOHANG

     This 'options' flag causes *note waitpid(): d40, *note wait3():
     d3c, *note wait4(): d3d, and *note waitid(): d3f. to return right
     away if no child process status is available immediately.

     *note Availability: 1c56.: Unix, not WASI, not iOS.

 -- 資料: os.WNOWAIT

     This 'options' flag causes *note waitid(): d3f. to leave the child
     in a waitable state, so that a later ‘wait*()’ call can be used to
     retrieve the child status information again.

     This option is not available for the other ‘wait*’ functions.

     *note Availability: 1c56.: Unix, not WASI, not iOS.

 -- 資料: os.CLD_EXITED
 -- 資料: os.CLD_KILLED
 -- 資料: os.CLD_DUMPED
 -- 資料: os.CLD_TRAPPED
 -- 資料: os.CLD_STOPPED
 -- 資料: os.CLD_CONTINUED

     These are the possible values for ‘si_code’ in the result returned
     by *note waitid(): d3f.

     *note Availability: 1c56.: Unix, not WASI, not iOS.

     在 3.3 版被加入.

     在 3.9 版的變更: Added *note CLD_KILLED: 8bd. and *note
     CLD_STOPPED: 8be. values.

 -- 函式: os.waitstatus_to_exitcode (status)

     Convert a wait status to an exit code.

     On Unix:

        * If the process exited normally (if ‘WIFEXITED(status)’ is
          true), return the process exit status (return
          ‘WEXITSTATUS(status)’): result greater than or equal to 0.

        * If the process was terminated by a signal (if
          ‘WIFSIGNALED(status)’ is true), return ‘-signum’ where
          'signum' is the number of the signal that caused the process
          to terminate (return ‘-WTERMSIG(status)’): result less than 0.

        * Otherwise, raise a *note ValueError: 1e7.

     On Windows, return 'status' shifted right by 8 bits.

     On Unix, if the process is being traced or if *note waitpid(): d40.
     was called with *note WUNTRACED: 2ad7. option, the caller must
     first check if ‘WIFSTOPPED(status)’ is true.  This function must
     not be called if ‘WIFSTOPPED(status)’ is true.

     也參考
     ......

     *note WIFEXITED(): 2adb, *note WEXITSTATUS(): 2adc, *note
     WIFSIGNALED(): 2add, *note WTERMSIG(): 2ade, *note WIFSTOPPED():
     2adf, *note WSTOPSIG(): 2ae0. functions.

     *note Availability: 1c56.: Unix, Windows, not WASI, not iOS.

     在 3.9 版被加入.

The following functions take a process status code as returned by *note
system(): 13c8, *note wait(): d3e, or *note waitpid(): d40. as a
parameter.  They may be used to determine the disposition of a process.

 -- 函式: os.WCOREDUMP (status, /)

     Return ‘True’ if a core dump was generated for the process,
     otherwise return ‘False’.

     This function should be employed only if *note WIFSIGNALED(): 2add.
     is true.

     *note Availability: 1c56.: Unix, not WASI, not iOS.

 -- 函式: os.WIFCONTINUED (status)

     Return ‘True’ if a stopped child has been resumed by delivery of
     *note SIGCONT: 2ae3. (if the process has been continued from a job
     control stop), otherwise return ‘False’.

     參閱 *note WCONTINUED: 2ad2. 選項。

     *note Availability: 1c56.: Unix, not WASI, not iOS.

 -- 函式: os.WIFSTOPPED (status)

     Return ‘True’ if the process was stopped by delivery of a signal,
     otherwise return ‘False’.

     *note WIFSTOPPED(): 2adf. only returns ‘True’ if the *note
     waitpid(): d40. call was done using *note WUNTRACED: 2ad7. option
     or when the process is being traced (see ‘ptrace(2)(9)’).

     *note Availability: 1c56.: Unix, not WASI, not iOS.

 -- 函式: os.WIFSIGNALED (status)

     Return ‘True’ if the process was terminated by a signal, otherwise
     return ‘False’.

     *note Availability: 1c56.: Unix, not WASI, not iOS.

 -- 函式: os.WIFEXITED (status)

     Return ‘True’ if the process exited terminated normally, that is,
     by calling ‘exit()’ or ‘_exit()’, or by returning from ‘main()’;
     otherwise return ‘False’.

     *note Availability: 1c56.: Unix, not WASI, not iOS.

 -- 函式: os.WEXITSTATUS (status)

     Return the process exit status.

     This function should be employed only if *note WIFEXITED(): 2adb.
     is true.

     *note Availability: 1c56.: Unix, not WASI, not iOS.

 -- 函式: os.WSTOPSIG (status)

     Return the signal which caused the process to stop.

     This function should be employed only if *note WIFSTOPPED(): 2adf.
     is true.

     *note Availability: 1c56.: Unix, not WASI, not iOS.

 -- 函式: os.WTERMSIG (status)

     Return the number of the signal that caused the process to
     terminate.

     This function should be employed only if *note WIFSIGNALED(): 2add.
     is true.

     *note Availability: 1c56.: Unix, not WASI, not iOS.

   ---------- Footnotes ----------

   (1) https://msdn.microsoft.com/44228cf2-6306-466c-8f16-f513cd3ba8b5

   (2) https://discuss.python.org/t/33555

   (3) https://manpages.debian.org/pidfd_open(2)

   (4) https://manpages.debian.org/waitid(2)

   (5) https://manpages.debian.org/times(2)

   (6) https://man.freebsd.org/cgi/man.cgi?time(3)

   (7) 
https://docs.microsoft.com/windows/win32/api/processthreadsapi/nf-processthreadsapi-getprocesstimes

   (8) https://peps.python.org/pep-0475/

   (9) https://manpages.debian.org/ptrace(2)


File: python.info,  Node: Interface to the scheduler,  Next: Miscellaneous System Information,  Prev: 行程管理,  Up: os --- 各種作業系統介面

5.16.1.12 Interface to the scheduler
....................................

These functions control how a process is allocated CPU time by the
operating system.  They are only available on some Unix platforms.  For
more detailed information, consult your Unix manpages.

在 3.3 版被加入.

The following scheduling policies are exposed if they are supported by
the operating system.

 -- 資料: os.SCHED_OTHER

     The default scheduling policy.

 -- 資料: os.SCHED_BATCH

     Scheduling policy for CPU-intensive processes that tries to
     preserve interactivity on the rest of the computer.

 -- 資料: os.SCHED_IDLE

     Scheduling policy for extremely low priority background tasks.

 -- 資料: os.SCHED_SPORADIC

     Scheduling policy for sporadic server programs.

 -- 資料: os.SCHED_FIFO

     A First In First Out scheduling policy.

 -- 資料: os.SCHED_RR

     A round-robin scheduling policy.

 -- 資料: os.SCHED_RESET_ON_FORK

     This flag can be OR'ed with any other scheduling policy.  When a
     process with this flag set forks, its child's scheduling policy and
     priority are reset to the default.

 -- 類別: os.sched_param (sched_priority)

     This class represents tunable scheduling parameters used in *note
     sched_setparam(): 10a7, *note sched_setscheduler(): 10a8, and *note
     sched_getparam(): 10a3.  It is immutable.

     At the moment, there is only one possible parameter:

      -- 屬性: sched_priority

          The scheduling priority for a scheduling policy.

 -- 函式: os.sched_get_priority_min (policy)

     Get the minimum priority value for 'policy'.  'policy' is one of
     the scheduling policy constants above.

 -- 函式: os.sched_get_priority_max (policy)

     Get the maximum priority value for 'policy'.  'policy' is one of
     the scheduling policy constants above.

 -- 函式: os.sched_setscheduler (pid, policy, param, /)

     Set the scheduling policy for the process with PID 'pid'.  A 'pid'
     of 0 means the calling process.  'policy' is one of the scheduling
     policy constants above.  'param' is a *note sched_param: 2ac0.
     instance.

 -- 函式: os.sched_getscheduler (pid, /)

     Return the scheduling policy for the process with PID 'pid'.  A
     'pid' of 0 means the calling process.  The result is one of the
     scheduling policy constants above.

 -- 函式: os.sched_setparam (pid, param, /)

     Set the scheduling parameters for the process with PID 'pid'.  A
     'pid' of 0 means the calling process.  'param' is a *note
     sched_param: 2ac0. instance.

 -- 函式: os.sched_getparam (pid, /)

     Return the scheduling parameters as a *note sched_param: 2ac0.
     instance for the process with PID 'pid'.  A 'pid' of 0 means the
     calling process.

 -- 函式: os.sched_rr_get_interval (pid, /)

     Return the round-robin quantum in seconds for the process with PID
     'pid'.  A 'pid' of 0 means the calling process.

 -- 函式: os.sched_yield ()

     Voluntarily relinquish the CPU.

 -- 函式: os.sched_setaffinity (pid, mask, /)

     Restrict the process with PID 'pid' (or the current process if
     zero) to a set of CPUs.  'mask' is an iterable of integers
     representing the set of CPUs to which the process should be
     restricted.

 -- 函式: os.sched_getaffinity (pid, /)

     Return the set of CPUs the process with PID 'pid' is restricted to.

     If 'pid' is zero, return the set of CPUs the calling thread of the
     current process is restricted to.

     See also the *note process_cpu_count(): 1a7. function.


File: python.info,  Node: Miscellaneous System Information,  Next: Random numbers,  Prev: Interface to the scheduler,  Up: os --- 各種作業系統介面

5.16.1.13 Miscellaneous System Information
..........................................

 -- 函式: os.confstr (name, /)

     Return string-valued system configuration values.  'name' specifies
     the configuration value to retrieve; it may be a string which is
     the name of a defined system value; these names are specified in a
     number of standards (POSIX, Unix 95, Unix 98, and others).  Some
     platforms define additional names as well.  The names known to the
     host operating system are given as the keys of the ‘confstr_names’
     dictionary.  For configuration variables not included in that
     mapping, passing an integer for 'name' is also accepted.

     If the configuration value specified by 'name' isn't defined,
     ‘None’ is returned.

     If 'name' is a string and is not known, *note ValueError: 1e7. is
     raised.  If a specific value for 'name' is not supported by the
     host system, even if it is included in ‘confstr_names’, an *note
     OSError: 350. is raised with *note errno.EINVAL: 18f4. for the
     error number.

     *note 適用: 1c56.：Unix。

 -- 資料: os.confstr_names

     Dictionary mapping names accepted by *note confstr(): 2aef. to the
     integer values defined for those names by the host operating
     system.  This can be used to determine the set of names known to
     the system.

     *note 適用: 1c56.：Unix。

 -- 函式: os.cpu_count ()

     Return the number of logical CPUs in the 'system'.  Returns ‘None’
     if undetermined.

     The *note process_cpu_count(): 1a7. function can be used to get the
     number of logical CPUs usable by the calling thread of the 'current
     process'.

     在 3.4 版被加入.

     在 3.13 版的變更: If *note -X cpu_count: 15a. is given or *note
     PYTHON_CPU_COUNT: 1f5. is set, *note cpu_count(): 1a8. returns the
     overridden value 'n'.

 -- 函式: os.getloadavg ()

     Return the number of processes in the system run queue averaged
     over the last 1, 5, and 15 minutes or raises *note OSError: 350. if
     the load average was unobtainable.

     *note 適用: 1c56.：Unix。

 -- 函式: os.process_cpu_count ()

     Get the number of logical CPUs usable by the calling thread of the
     'current process'.  Returns ‘None’ if undetermined.  It can be less
     than *note cpu_count(): 1a8. depending on the CPU affinity.

     The *note cpu_count(): 1a8. function can be used to get the number
     of logical CPUs in the 'system'.

     If *note -X cpu_count: 15a. is given or *note PYTHON_CPU_COUNT:
     1f5. is set, *note process_cpu_count(): 1a7. returns the overridden
     value 'n'.

     See also the *note sched_getaffinity(): 10a2. functions.

     在 3.13 版被加入.

 -- 函式: os.sysconf (name, /)

     Return integer-valued system configuration values.  If the
     configuration value specified by 'name' isn't defined, ‘-1’ is
     returned.  The comments regarding the 'name' parameter for *note
     confstr(): 2aef. apply here as well; the dictionary that provides
     information on the known names is given by ‘sysconf_names’.

     *note 適用: 1c56.：Unix。

 -- 資料: os.sysconf_names

     Dictionary mapping names accepted by *note sysconf(): 2a4f. to the
     integer values defined for those names by the host operating
     system.  This can be used to determine the set of names known to
     the system.

     *note 適用: 1c56.：Unix。

     在 3.11 版的變更: Add ‘'SC_MINSIGSTKSZ'’ name.

The following data values are used to support path manipulation
operations.  These are defined for all platforms.

Higher-level operations on pathnames are defined in the *note os.path:
92. module.

 -- 資料: os.curdir

     The constant string used by the operating system to refer to the
     current directory.  This is ‘'.'’ for Windows and POSIX. Also
     available via *note os.path: 92.

 -- 資料: os.pardir

     The constant string used by the operating system to refer to the
     parent directory.  This is ‘'..'’ for Windows and POSIX. Also
     available via *note os.path: 92.

 -- 資料: os.sep

     The character used by the operating system to separate pathname
     components.  This is ‘'/'’ for POSIX and ‘'\\'’ for Windows.  Note
     that knowing this is not sufficient to be able to parse or
     concatenate pathnames -- use *note os.path.split(): 26b1. and *note
     os.path.join(): 1527. -- but it is occasionally useful.  Also
     available via *note os.path: 92.

 -- 資料: os.altsep

     An alternative character used by the operating system to separate
     pathname components, or ‘None’ if only one separator character
     exists.  This is set to ‘'/'’ on Windows systems where ‘sep’ is a
     backslash.  Also available via *note os.path: 92.

 -- 資料: os.extsep

     The character which separates the base filename from the extension;
     for example, the ‘'.'’ in ‘os.py’.  Also available via *note
     os.path: 92.

 -- 資料: os.pathsep

     The character conventionally used by the operating system to
     separate search path components (as in ‘PATH’), such as ‘':'’ for
     POSIX or ‘';'’ for Windows.  Also available via *note os.path: 92.

 -- 資料: os.defpath

     The default search path used by *note exec*p*: 2aa4. and *note
     spawn*p*: 1630. if the environment doesn't have a ‘'PATH'’ key.
     Also available via *note os.path: 92.

 -- 資料: os.linesep

     The string used to separate (or, rather, terminate) lines on the
     current platform.  This may be a single character, such as ‘'\n'’
     for POSIX, or multiple characters, for example, ‘'\r\n'’ for
     Windows.  Do not use 'os.linesep' as a line terminator when writing
     files opened in text mode (the default); use a single ‘'\n'’
     instead, on all platforms.

 -- 資料: os.devnull

     The file path of the null device.  For example: ‘'/dev/null'’ for
     POSIX, ‘'nul'’ for Windows.  Also available via *note os.path: 92.

 -- 資料: os.RTLD_LAZY
 -- 資料: os.RTLD_NOW
 -- 資料: os.RTLD_GLOBAL
 -- 資料: os.RTLD_LOCAL
 -- 資料: os.RTLD_NODELETE
 -- 資料: os.RTLD_NOLOAD
 -- 資料: os.RTLD_DEEPBIND

     Flags for use with the *note setdlopenflags(): 10b7. and *note
     getdlopenflags(): 147e. functions.  See the Unix manual page
     ‘dlopen(3)(1)’ for what the different flags mean.

     在 3.3 版被加入.

   ---------- Footnotes ----------

   (1) https://manpages.debian.org/dlopen(3)


File: python.info,  Node: Random numbers,  Prev: Miscellaneous System Information,  Up: os --- 各種作業系統介面

5.16.1.14 Random numbers
........................

 -- 函式: os.getrandom (size, flags=0)

     Get up to 'size' random bytes.  The function can return less bytes
     than requested.

     These bytes can be used to seed user-space random number generators
     or for cryptographic purposes.

     ‘getrandom()’ relies on entropy gathered from device drivers and
     other sources of environmental noise.  Unnecessarily reading large
     quantities of data will have a negative impact on other users of
     the ‘/dev/random’ and ‘/dev/urandom’ devices.

     The flags argument is a bit mask that can contain zero or more of
     the following values ORed together: *note os.GRND_RANDOM: 2af4. and
     *note GRND_NONBLOCK: 2af5.

     See also the Linux getrandom() manual page(1).

     *note 適用: 1c56.：Linux 3.17 以上。

     在 3.6 版被加入.

 -- 函式: os.urandom (size, /)

     Return a bytestring of 'size' random bytes suitable for
     cryptographic use.

     This function returns random bytes from an OS-specific randomness
     source.  The returned data should be unpredictable enough for
     cryptographic applications, though its exact quality depends on the
     OS implementation.

     On Linux, if the ‘getrandom()’ syscall is available, it is used in
     blocking mode: block until the system urandom entropy pool is
     initialized (128 bits of entropy are collected by the kernel).  See
     the PEP 524(2) for the rationale.  On Linux, the *note getrandom():
     c64. function can be used to get random bytes in non-blocking mode
     (using the *note GRND_NONBLOCK: 2af5. flag) or to poll until the
     system urandom entropy pool is initialized.

     On a Unix-like system, random bytes are read from the
     ‘/dev/urandom’ device.  If the ‘/dev/urandom’ device is not
     available or not readable, the *note NotImplementedError: 20d.
     exception is raised.

     On Windows, it will use ‘BCryptGenRandom()’.

     也參考
     ......

     The *note secrets: ae. module provides higher level functions.  For
     an easy-to-use interface to the random number generator provided by
     your platform, please see *note random.SystemRandom: 25bc.

     在 3.5 版的變更: On Linux 3.17 and newer, the ‘getrandom()’ syscall
     is now used when available.  On OpenBSD 5.6 and newer, the C
     ‘getentropy()’ function is now used.  These functions avoid the
     usage of an internal file descriptor.

     在 3.5.2 版的變更: On Linux, if the ‘getrandom()’ syscall blocks
     (the urandom entropy pool is not initialized yet), fall back on
     reading ‘/dev/urandom’.

     在 3.6 版的變更: On Linux, ‘getrandom()’ is now used in blocking
     mode to increase the security.

     在 3.11 版的變更: On Windows, ‘BCryptGenRandom()’ is used instead
     of ‘CryptGenRandom()’ which is deprecated.

 -- 資料: os.GRND_NONBLOCK

     By default, when reading from ‘/dev/random’, *note getrandom():
     c64. blocks if no random bytes are available, and when reading from
     ‘/dev/urandom’, it blocks if the entropy pool has not yet been
     initialized.

     If the *note GRND_NONBLOCK: 2af5. flag is set, then *note
     getrandom(): c64. does not block in these cases, but instead
     immediately raises *note BlockingIOError: ffa.

     在 3.6 版被加入.

 -- 資料: os.GRND_RANDOM

     If this bit is set, then random bytes are drawn from the
     ‘/dev/random’ pool instead of the ‘/dev/urandom’ pool.

     在 3.6 版被加入.

   ---------- Footnotes ----------

   (1) https://man7.org/linux/man-pages/man2/getrandom.2.html

   (2) https://peps.python.org/pep-0524/


File: python.info,  Node: io — 處理資料串流的核心工具,  Next: time --- 時間存取與轉換,  Prev: os --- 各種作業系統介面,  Up: 通用作業系統服務

5.16.2 ‘io’ — 處理資料串流的核心工具
------------------------------------

'原始碼：'Lib/io.py(1)

__________________________________________________________________

* Menu:

* 總覽::
* 文字編碼::
* 高階模組介面::
* 類別階層::
* Performance: Performance<3>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/io.py


File: python.info,  Node: 總覽,  Next: 文字編碼,  Up: io — 處理資料串流的核心工具

5.16.2.1 總覽
.............

*note io: 73. 模組替 Python 提供處理各種類型 IO 的主要工具。有三種主要的
IO 類型： '文字 I/O (text I/O)'、'二進位 I/O (binary I/O)' 以及'原始 I/O
(raw I/O)'。這些均為泛用 (generic) 類型，且每種類型都可以使用各式後端儲
存 (backing store)。任一種屬於這些類型的具體物件稱為 *note file object:
115b.。其它常見的名詞還有'資料串流 (stream)' 以及'類檔案物件 (file-like
objects)'。

無論其類型為何，每個具體的資料串流物件也將具有各種能力：唯讀的、只接受寫
入的、或者讀寫兼具的。它還允許任意的隨機存取（向前或向後尋找至任意位置）
，或者只能依順序存取（例如 socket 或 pipe 的情形下）。

所有的資料串流都會謹慎處理你所提供的資料的型別。舉例來說，提供一個 *note
str: 3f2. 物件給二進位資料串流的 ‘write()’ 方法將會引發 *note TypeError:
4dd.。同樣地，若提供一個 *note bytes: 1a5. 物件給文字資料串流的
‘write()’ 方法，也會引發同樣的錯誤。

在 3.3 版的變更: 原本會引發 *note IOError: ff5. 的操作，現在將改成引發
*note OSError: 350.。因為 *note IOError: ff5. 現在是 *note OSError: 350.
的別名。

* Menu:

* 文字 I/O::
* 二進位 (Binary) I/O: 二進位 Binary I/O.
* 原始 (Raw) I/O: 原始 Raw I/O.


File: python.info,  Node: 文字 I/O,  Next: 二進位 Binary I/O,  Up: 總覽

5.16.2.2 文字 I/O
.................

文字 I/O 要求和產出 *note str: 3f2. 物件。這意味著每當後端儲存為原生
bytes 時（例如在檔案的情形下），資料的編碼與解碼會以清楚易懂的方式進行，
也可選擇同時轉換特定於平台的換行字元。

建立文字資料串流最簡單的方法是使用 *note open(): 4c0.，可選擇性地指定編
碼：

     f = open("myfile.txt", "r", encoding="utf-8")

記憶體內的文字資料串流也可以使用 *note StringIO: ecb. 物件建立：

     f = io.StringIO("some initial text data")

文字資料串流 API 的詳細說明在 *note TextIOBase: 63b. 文件當中。


File: python.info,  Node: 二進位 Binary I/O,  Next: 原始 Raw I/O,  Prev: 文字 I/O,  Up: 總覽

5.16.2.3 二進位 (Binary) I/O
............................

二進位 I/O（也稱為'緩衝 I/O (buffered I/O)'）要求的是*note 類位元組物件
(bytes-like objects): cd4. 且產生 *note bytes: 1a5. 物件。不進行編碼、解
碼或者換行字元轉換。這種類型的資料串流可用於各種非文字資料，以及需要手動
控制對文字資料的處理時。

建立二進位資料串流最簡單的方法是使用 *note open(): 4c0.，並在 mode 字串
中加入 ‘'b'’：

     f = open("myfile.jpg", "rb")

記憶體內的二進位資料串流也可以透過 *note BytesIO: e46. 物件來建立：

     f = io.BytesIO(b"some initial binary data: \x00\x01")

二進位資料串流 API 的詳細說明在 *note BufferedIOBase: 63a. 文件當中。

其它函式庫模組可能提供額外的方法來建立文字或二進位資料串流。例如 *note
socket.socket.makefile(): 1137.。


File: python.info,  Node: 原始 Raw I/O,  Prev: 二進位 Binary I/O,  Up: 總覽

5.16.2.4 原始 (Raw) I/O
.......................

原始 I/O（也稱為'無緩衝 I/O (unbuffered I/O)'）通常作為二進位以及文字資
料串流的低階 building-block 使用；在使用者程式碼中直接操作原始資料串流很
少有用。然而，你可以透過以無緩衝的二進位模式開啟一個檔案來建立一個原始資
料串流：

     f = open("myfile.jpg", "rb", buffering=0)

原始串流 API 在 *note RawIOBase: 106a. 文件中有詳細描述。


File: python.info,  Node: 文字編碼,  Next: 高階模組介面,  Prev: 總覽,  Up: io — 處理資料串流的核心工具

5.16.2.5 文字編碼
.................

*note TextIOWrapper: 75f. 和 *note open(): 4c0. 預設編碼是根據區域設定的
(locale-specific) (*note locale.getencoding(): 2bc.)。

然而，許多開發人員在開啟以 UTF-8 編碼的文字檔案（例如：JSON、TOML、
Markdown等）時忘記指定編碼，因為多數 Unix 平台預設使用 UTF-8 區域設定。
這會導致錯誤，因為對於大多數 Windows 使用者來說，預設地區編碼並非 UTF-8。
舉例來說：

     # May not work on Windows when non-ASCII characters in the file.
     with open("README.md") as f:
         long_description = f.read()

因此，強烈建議在開啟文字檔案時，明確指定編碼。若你想使用 UTF-8 編碼，請
傳入 ‘encoding="utf-8"’。若想使用目前的地區編碼，Python 3.10 以後的版本
支援使用 ‘encoding="locale"’。

也參考
......

*note Python UTF-8 模式: 5fc.

     在 Python UTF-8 模式下，可以將預設編碼從特定地區編碼改為 UTF-8。

PEP 686(1)

     Python 3.15 將預設使用 *note Python UTF-8 模式: 5fc.。

* Menu:

* 選擇性加入的編碼警告::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0686/


File: python.info,  Node: 選擇性加入的編碼警告,  Up: 文字編碼

5.16.2.6 選擇性加入的編碼警告
.............................

在 3.10 版被加入: 更多資訊請見 PEP 597(1)。

要找出哪些地方使用到預設的地區編碼，你可以啟用 *note -X
warn_default_encoding: 15a. 命令列選項，或者設定環境變數 *note
PYTHONWARNDEFAULTENCODING: 760.。當使用到預設編碼時，會引發 *note
EncodingWarning: 1c3f.。

如果你正在提供一個使用 *note open(): 4c0. 或 *note TextIOWrapper: 75f. 且
傳遞 ‘encoding=None’ 作為參數的 API，你可以使用 *note text_encoding():
15c1.。如此一來如果 API 的呼叫方沒有傳遞 ‘encoding’，呼叫方就會發出一個
*note EncodingWarning: 1c3f.。然而，對於新的 API，請考慮預設使用 UTF-8（
即 ‘encoding="utf-8"’）。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0597/


File: python.info,  Node: 高階模組介面,  Next: 類別階層,  Prev: 文字編碼,  Up: io — 處理資料串流的核心工具

5.16.2.7 高階模組介面
.....................

 -- 資料: io.DEFAULT_BUFFER_SIZE

     一個包含模組中緩衝 I/O 類別所使用的預設緩衝區大小的整數。若可能的話
     ，*note open(): 4c0. 會使用檔案的 blksize （透過 *note os.stat():
     448. 取得）。

 -- 函式: io.open (file, mode='r', buffering=-1, encoding=None,
          errors=None, newline=None, closefd=True, opener=None)

     這是內建函式 *note open(): 4c0. 的別名。

     此函式會引發一個帶有引數 'path'、'mode' 以及 'flags' 的*note
     稽核事件 (auditing event): 17bd. ‘open’。'mode' 與 'flags' 引數可能
     已經被修改或者從原始呼叫中被推斷出來。

 -- 函式: io.open_code (path)

     以 ‘'rb'’ 模式開啟提供的檔案。此函式應用於意圖將內容視為可執行的程
     式碼的情況下。

     'path' 應該要屬於 *note str: 3f2. 類別，且是個絕對路徑。

     這個函式的行為可能會被之前對 *note PyFile_SetOpenCodeHook(): 1627.
     的呼叫覆寫。然而，假設 'path' 是個 *note str: 3f2. 且為絕對路徑，則
     ‘open_code(path)’ 總是與 ‘open(path, 'rb')’ 有相同行為。覆寫這個行
     為是為了對檔案進行額外驗證或預處理。

     在 3.8 版被加入.

 -- 函式: io.text_encoding (encoding, stacklevel=2, /)

     這是個輔助函數，適用於使用 *note open(): 4c0. 或 *note
     TextIOWrapper: 75f. 且具有 ‘encoding=None’ 參數的可呼叫物件。

     若 'encoding' 不為 ‘None’，此函式將回傳 'encoding'。否則，將根據
     *note UTF-8 Mode: 5fc. 回傳 ‘"locale"’ 或 ‘"utf-8"’。

     若 *note sys.flags.warn_default_encoding: 632. 為真，且 'encoding'
     為 ‘None’，此函式會發出一個 *note EncodingWarning: 1c3f.。
     'stacklevel' 指定警告在哪層發出。範例：

          def read_text(path, encoding=None):
              encoding = io.text_encoding(encoding)  # stacklevel=2
              with open(path, encoding) as f:
                  return f.read()

     在此範例中，對於 ‘read_text()’ 的呼叫方會引發一個 *note
     EncodingWarning: 1c3f.。

     更多資訊請見 *note 文字編碼: 761.。

     在 3.10 版被加入.

     在 3.11 版的變更: 當 UTF-8 模式啟用且 'encoding' 為 ‘None’ 時，
     *note text_encoding(): 15c1. 會回傳 "utf-8"。

 -- 例外: io.BlockingIOError

     這是內建的 *note BlockingIOError: ffa. 例外的相容性別名。

 -- 例外: io.UnsupportedOperation

     當在資料串流上呼叫不支援的操作時，會引發繼承自 *note OSError: 350.
     與 *note ValueError: 1e7. 的例外。

也參考
......

*note sys: c3.

     包含標準的 IO 資料串流：*note sys.stdin: 4e2.、*note sys.stdout:
     a79. 以及 *note sys.stderr: 8dd.。


File: python.info,  Node: 類別階層,  Next: Performance<3>,  Prev: 高階模組介面,  Up: io — 處理資料串流的核心工具

5.16.2.8 類別階層
.................

I/O 串流的實作是由多個類別組合成的階層結構所構成。首先是 *note abstract
base classes: 114e. （抽象基底類別，ABCs），它們被用來規範各種不同類型的
串流，接著具體類別會提供標準串流的實作。

     備註: 為了協助具體串流類別的實作，抽象基底類別提供了某些方法的預設
     實作。舉例來說，*note BufferedIOBase: 63a. 提供未經最佳化的
     ‘readinto()’ 與 ‘readline()’ 實作。

I/O 階層結構的最上層是抽象基底類別 *note IOBase: 1da.。它定義了串流的基
礎的介面。然而，請注意，讀取串流與寫入串流之間並沒有分離；若不支援給定的
操作，實作是允許引發 *note UnsupportedOperation: 189a. 例外的。

抽象基底類別 *note RawIOBase: 106a. 繼承 *note IOBase: 1da.。此類別處理
對串流的位元組讀寫。*note FileIO: 12a4. 則繼承 *note RawIOBase: 106a. 來
提供一個介面以存取機器檔案系統內的檔案。

抽象基底類別 *note BufferedIOBase: 63a. 繼承 *note IOBase: 1da.。此類別
緩衝原始二進位串流 (*note RawIOBase: 106a.)。它的子類別 *note
BufferedWriter: 2056.、*note BufferedReader: 11a6. 與 *note
BufferedRWPair: 2b01. 分別緩衝可寫、可讀、可讀也可寫的的原始二進位串流。
類別 *note BufferedRandom: 2057. 則提供一個對可搜尋串流 (seekable
stream) 的緩衝介面。另一個類別 *note BufferedIOBase: 63a. 的子類別 *note
BytesIO: e46.，是一個記憶體內位元組串流。

抽象基底類別 *note TextIOBase: 63b. 繼承 *note IOBase: 1da.。此類別處理
文本位元組串流，並處理字串的編碼和解碼。類別 *note TextIOWrapper: 75f. 繼
承自 *note TextIOBase: 63b.，這是個對緩衝原始串流 (*note BufferedIOBase:
63a.) 的緩衝文本介面。最後，*note StringIO: ecb. 是個文字記憶體內串流。

引數名稱不是規範的一部份，只有 *note open(): 4c0. 的引數將作為關鍵字引數
。

以下表格總結了 *note io: 73. 模組提供的抽象基底類別 (ABC)：

抽象基底類別 (ABC)            繼承                   Stub 方法                    Mixin 方法與屬性
                                                                                  
-----------------------------------------------------------------------------------------------------------------------------------------
                                                                                  
*note IOBase: 1da.                                   ‘fileno’、‘seek’ 和          ‘close’、‘closed’、‘__enter__’、‘__exit__’、
                                                     ‘truncate’                   ‘flush’、‘isatty’、‘__iter__’、‘__next__’、
                                                                                  ‘readable’、‘readline’、‘readlines’、‘seekable’、
                                                                                  ‘tell’、‘writable’ 與 ‘writelines’
                                                                                  
                                                                                  
*note RawIOBase: 106a.        *note IOBase: 1da.     ‘readinto’ 和 ‘write’        繼承自 *note IOBase: 1da. 的方法，‘read’ 與
                                                                                  ‘readall’
                                                                                  
                                                                                  
*note BufferedIOBase: 63a.    *note IOBase: 1da.     ‘detach’、‘read’、‘read1’    繼承自 *note IOBase: 1da. 的方法，‘readinto’ 與
                                                     和 ‘write’                   ‘readinto1’
                                                                                  
                                                                                  
*note TextIOBase: 63b.        *note IOBase: 1da.     ‘detach’、‘read’、           繼承自 *note IOBase: 1da. 的方法，‘encoding’、
                                                     ‘readline’ 和 ‘write’        ‘errors’ 與 ‘newlines’
                                                                                  

* Menu:

* I/O 基礎類別::
* 原始檔案 I/O::
* Buffered Streams::
* 文字 I/O: 文字 I/O<2>.


File: python.info,  Node: I/O 基礎類別,  Next: 原始檔案 I/O,  Up: 類別階層

5.16.2.9 I/O 基礎類別
.....................

 -- 類別: io.IOBase

     所有 I/O 類別的抽象基礎類別。

     為許多方法提供了空的抽象實作，衍生類別可以選擇性地覆寫這些方法；預
     設的實作代表一個無法讀取、寫入或搜尋的檔案。

     即使 *note IOBase: 1da. 因為實作的簽名差異巨大而沒有宣告 ‘read()’ 或
     ‘write()’ 方法，實作與用戶端應把這些方法視為介面的一部份。此外，當
     呼叫不被它們支援的操作時，可能會引發 *note ValueError: 1e7. （或
     *note UnsupportedOperation: 189a.）例外。

     The basic type used for binary data read from or written to a file
     is *note bytes: 1a5.  Other *note bytes-like objects: cd4. are
     accepted as method arguments too.  Text I/O classes work with *note
     str: 3f2. data.

     請注意，在一個已經關閉的串流上呼叫任何方法（即使只是查詢）都是未定
     義的。在這種情況下，實作可能會引發 *note ValueError: 1e7. 例外。

     *note IOBase: 1da. (and its subclasses) supports the iterator
     protocol, meaning that an *note IOBase: 1da. object can be iterated
     over yielding the lines in a stream.  Lines are defined slightly
     differently depending on whether the stream is a binary stream
     (yielding bytes), or a text stream (yielding character strings).
     See *note readline(): 12bd. below.

     *note IOBase: 1da. 也是個情境管理器，因此支援 *note with: 577. 陳述
     式。在這個例子中，'file' 會在 ‘with’ 陳述式執行完畢後關閉——即使發生
     了異常。

          with open('spam.txt', 'w') as file:
              file.write('Spam and eggs!')

     *note IOBase: 1da. 提供這些資料屬性與方法：

      -- 方法: close ()

          清除並關閉這個串流。若檔案已經關閉，則此方法沒有作用。一旦檔案
          被關閉，任何對檔案的操作（例如讀取或寫入）將引發 *note
          ValueError: 1e7. 異常。

          為了方便起見，允許多次呼叫這個方法；然而，只有第一次呼叫會有效
          果。

      -- 屬性: closed

          如果串流已關閉，則為 ‘True’。

      -- 方法: fileno ()

          如果串流存在，則回傳其底層的檔案描述器（一個整數）。如果 IO 物
          件不使用檔案描述器，則會引發一個 *note OSError: 350. 例外。

      -- 方法: flush ()

          如果適用，清空串流的寫入緩衝區。對於唯讀和非阻塞串流，此操作不
          會執行任何操作。

      -- 方法: isatty ()

          如果串流是互動式的（即連接到終端機/tty 設備），則回傳 ‘True’。

      -- 方法: readable ()

          如果串流可以被讀取，則回傳 ‘True’。如果是 ‘False’，‘read()’ 將
          會引發 *note OSError: 350. 例外。

      -- 方法: readline (size=-1, /)

          從串流讀取並回傳一行。如果指定了 'size'，則最多讀取 'size' 個
          位元組。

          對於二進位檔案，行結束符總是 ‘b'\n'’；對於文字檔案，可以使用
          *note open(): 4c0. 函式的 'newline' 引數來選擇識別的行結束符號
          。

      -- 方法: readlines (hint=-1, /)

          從串流讀取並回傳一個含有一或多行的 list。可以指定 'hint' 來控
          制讀取的行數：如果到目前為止所有行的總大小（以位元組/字元計）
          超過 'hint'，則不會再讀取更多行。

          'hint' 值為 ‘0’ 或更小，以及 ‘None’，都被視為沒有提供 hint。

          請注意，已經可以使用 ‘for line in file: ...’ 在檔案物件上進行
          疊代，而不一定需要呼叫 ‘file.readlines()’。

      -- 方法: seek (offset, whence=os.SEEK_SET, /)

          將串流位置改變到給定的位元組 'offset'，此位置是相對於由
          'whence' 指示的位置解釋的，並回傳新的絕對位置。'whence' 的值可
          為：

             * *note os.SEEK_SET: 1225. 或 ‘0’ - 串流的起點（預設值）；
               'offset' 應為零或正數

             * *note os.SEEK_CUR: 1226. 或 ‘1’ - 目前串流位置；'offset'
               可以是負數

             * *note os.SEEK_END: 1227. 或 ‘2’ - 串流的結尾；'offset' 通
               常是負數

          在 3.1 版被加入: ‘SEEK_*’ 常數。

          在 3.3 版被加入: 某些作業系統可以支援額外的值，例如 *note
          os.SEEK_HOLE: 2a2d. 或 *note os.SEEK_DATA: 2a2e.。檔案的合法值
          取決於它是以文字模式還是二進位模式開啟。

      -- 方法: seekable ()

          如果串流支援隨機存取，則回傳 ‘True’。如果是 ‘False’，則 *note
          seek(): 1224.、*note tell(): 2894. 和 *note truncate(): 12a5.
          會引發 *note OSError: 350.。

      -- 方法: tell ()

          回傳目前串流的位置。

      -- 方法: truncate (size=None, /)

          將串流的大小調整為指定的 'size' 位元組（如果沒有指定 'size'，
          則調整為目前位置）。目前串流位置不會改變。這種調整可以擴展或縮
          減當前檔案大小。在擴展的情況下，新檔案區域的內容取決於平台（在
          大多數系統上，額外的位元組會被填充為零）。回傳新的檔案大小。

          在 3.5 版的變更: Windows 現在在擴展時會對檔案進行零填充
          (zero-fill)。

      -- 方法: writable ()

          如果串流支援寫入，則回傳 ‘True’。如果是 ‘False’，‘write()’ 和
          *note truncate(): 12a5. 將會引發 *note OSError: 350.。

      -- 方法: writelines (lines, /)

          將一個包含每一行的 list 寫入串流。這不會新增行分隔符號，因此通
          常提供的每一行末尾都有一個行分隔符號。

      -- 方法: __del__ ()

          為物件銷毀做準備。*note IOBase: 1da. 提供了這個方法的預設實作
          ，該實作會呼叫實例的 *note close(): 1db. 方法。

 -- 類別: io.RawIOBase

     原始二進位串流的基底類別。它繼承自 *note IOBase: 1da.。

     原始二進位串流通常提供對底層作業系統設備或 API 的低階存取，並不嘗試
     將其封裝在高階基元 (primitive) 中（這項功能在緩衝二進位串流和文字串
     流中的更高階層級完成，後面的頁面會有描述）。

     *note RawIOBase: 106a. 除了 *note IOBase: 1da. 的方法外，還提供以下
     這些方法：

      -- 方法: read (size=-1, /)

          從物件中讀取最多 'size' 個位元組並回傳。方便起見，如果 'size'
          未指定或為 -1，則回傳直到檔案結尾 (EOF) 的所有位元組。否則，只
          會進行一次系統呼叫。如果作業系統呼叫回傳的位元組少於 'size'，
          則可能回傳少於 'size' 的位元組。

          如果回傳了 0 位元組，且 'size' 不是 0，這表示檔案結尾 (end of
          file)。如果物件處於非阻塞模式且沒有可用的位元組，則回傳
          ‘None’。

          預設的實作會遵守 *note readall(): 2b08. 和 *note readinto():
          dc3. 的實作。

      -- 方法: readall ()

          讀取並回傳串流中直到檔案結尾的所有位元組，必要時使用多次對串流
          的呼叫。

      -- 方法: readinto (b, /)

          將位元組讀入一個預先分配的、可寫的 *note bytes-like object:
          cd4. （類位元組物件） 'b' 中，並回傳讀取的位元組數量。例如，
          'b' 可能是一個 *note bytearray: 4e3.。如果物件處於非阻塞模式且
          沒有可用的位元組，則回傳 ‘None’。

      -- 方法: write (b, /)

          將給定的 *note bytes-like object: cd4. （類位元組物件），'b'，
          寫入底層的原始串流，並回傳寫入的位元組大小。根據底層原始串流的
          具體情況，這可能少於 'b' 的位元組長度，尤其是當它處於非阻塞模
          式時。如果原始串流設置為非阻塞且無法立即寫入任何單一位元組，則
          回傳 ‘None’。呼叫者在此方法回傳後可以釋放或變更 'b'，因此實作
          應該只在方法呼叫期間存取 'b'。

 -- 類別: io.BufferedIOBase

     支援某種緩衝的二進位串流的基底類別。它繼承自 *note IOBase: 1da.。

     與 *note RawIOBase: 106a. 的主要差異在於，*note read(): 12bc.、
     *note readinto(): 2b09. 及 *note write(): c82. 方法將分別嘗試讀取所
     請求的盡可能多的輸入，或消耗所有給定的輸出，即使可能需要進行多於一
     次的系統呼叫。

     此外，如果底層的原始串流處於非阻塞模式且無法提供或接收足夠的資料，
     這些方法可能會引發 *note BlockingIOError: ffa. 例外；與 *note
     RawIOBase: 106a. 不同之處在於，它們永遠不會回傳 ‘None’。

     此外，*note read(): 12bc. 方法不存在一個遵從 *note readinto():
     2b09. 的預設實作。

     一個典型的 *note BufferedIOBase: 63a. 實作不應該繼承自一個 *note
     RawIOBase: 106a. 的實作，而是應該改用包裝的方式，像 *note
     BufferedWriter: 2056. 和 *note BufferedReader: 11a6. 那樣的作法。

     *note BufferedIOBase: 63a. 除了提供或覆寫來自 *note IOBase: 1da. 的
     資料屬性和方法以外，還包含了這些：

      -- 屬性: raw

          底層的原始串流（一個 *note RawIOBase: 106a. 實例），*note
          BufferedIOBase: 63a. 處理的對象。這不是 *note BufferedIOBase:
          63a. API 的一部分，且在某些實作可能不存在。

      -- 方法: detach ()

          將底層的原始串流從緩衝區中分離出來，並回傳它。

          在原始串流被分離後，緩衝區處於一個不可用的狀態。

          某些緩衝區，如 *note BytesIO: e46.，沒有單一原始串流的概念可從
          此方法回傳。它們會引發 *note UnsupportedOperation: 189a.。

          在 3.1 版被加入.

      -- 方法: read (size=-1, /)

          讀取並回傳最多 'size' 個位元組。如果引數被省略、為 ‘None’ 或為
          負值，將讀取並回傳資料直到達到 EOF 為止。如果串流已經處於 EOF，
          則回傳一個空的 *note bytes: 1a5. 物件。

          如果引數為正數，且底層原始串流不是互動式的，可能會發出多次原始
          讀取來滿足位元組數量（除非首先達到 EOF）。但對於互動式原始串流
          ，最多只會發出一次原始讀取，且短少的資料不表示 EOF 即將到來。

          如果底層原始串流處於非阻塞模式，且當前沒有可用資料，則會引發
          *note BlockingIOError: ffa.。

      -- 方法: read1 (size=-1, /)

          讀取並回傳最多 'size' 個位元組，最多呼叫一次底層原始串流的
          *note read(): dc2. (或 *note readinto(): dc3.) 方法。如果你正
          在 *note BufferedIOBase: 63a. 物件之上實作自己的緩衝區，這可能
          會很有用。

          如果 'size' 為 ‘-1’ （預設值），則會回傳任意數量的位元組（除非
          達到 EOF，否則會超過零）。

      -- 方法: readinto (b, /)

          讀取位元組到一個預先分配的、可寫的 *note bytes-like object:
          cd4. 'b' 當中，並回傳讀取的位元組數量。例如，'b' 可能是一個
          *note bytearray: 4e3.。

          類似於 *note read(): 12bc.，除非後者是互動式的，否則可能會對底
          層原始串流發出多次讀取。

          如果底層原始串流處於非阻塞模式，且當前沒有可用資料，則會引發
          *note BlockingIOError: ffa.。

      -- 方法: readinto1 (b, /)

          讀取位元組到一個預先分配的、可寫的 *note bytes-like object:
          cd4. 'b' 中，最多呼叫一次底層原始串流的 *note read(): dc2. （
          或 *note readinto(): dc3.）方法。此方法回傳讀取的位元組數量。

          如果底層原始串流處於非阻塞模式，且當前沒有可用資料，則會引發
          *note BlockingIOError: ffa.。

          在 3.5 版被加入.

      -- 方法: write (b, /)

          寫入給定的 *note bytes-like object: cd4.，'b'，並回傳寫入的位
          元組數量（總是等於 'b' 的長度，以位元組計，因為如果寫入失敗將
          會引發 *note OSError: 350.）。根據實際的實作，這些位元組可能會
          立即寫入底層串流，或出於性能和延遲的緣故而被留在緩衝區當中。

          當處於非阻塞模式時，如果需要將資料寫入原始串流，但它無法接受所
          有資料而不阻塞，則會引發 *note BlockingIOError: ffa.。

          呼叫者可以在此方法回傳後釋放或變更 'b'，因此實作應該僅在方法呼
          叫期間存取 'b'。


File: python.info,  Node: 原始檔案 I/O,  Next: Buffered Streams,  Prev: I/O 基礎類別,  Up: 類別階層

5.16.2.10 原始檔案 I/O
......................

 -- 類別: io.FileIO (name, mode='r', closefd=True, opener=None)

     一個代表包含位元組資料的 OS 層級檔案的原始二進制串流。它繼承自
     *note RawIOBase: 106a.。

     'name' 可以是兩種事物之一：

        * 代表將要打開的檔案路徑的一個字元串或 *note bytes: 1a5. 物件。
          在這種情況下，closefd 必須是 ‘True’ （預設值），否則將引發錯誤
          。

        * an integer representing the number of an existing OS-level
          file descriptor to which the resulting *note FileIO: 12a4.
          object will give access.  When the FileIO object is closed
          this fd will be closed as well, unless 'closefd' is set to
          ‘False’.

     The 'mode' can be ‘'r'’, ‘'w'’, ‘'x'’ or ‘'a'’ for reading
     (default), writing, exclusive creation or appending.  The file will
     be created if it doesn't exist when opened for writing or
     appending; it will be truncated when opened for writing.  *note
     FileExistsError: fc3. will be raised if it already exists when
     opened for creating.  Opening a file for creating implies writing,
     so this mode behaves in a similar way to ‘'w'’.  Add a ‘'+'’ to the
     mode to allow simultaneous reading and writing.

     The *note read(): dc2. (when called with a positive argument),
     *note readinto(): dc3. and *note write(): 28d3. methods on this
     class will only make one system call.

     A custom opener can be used by passing a callable as 'opener'.  The
     underlying file descriptor for the file object is then obtained by
     calling 'opener' with ('name', 'flags').  'opener' must return an
     open file descriptor (passing *note os.open: d38. as 'opener'
     results in functionality similar to passing ‘None’).

     The newly created file is *note non-inheritable: e9d.

     See the *note open(): 4c0. built-in function for examples on using
     the 'opener' parameter.

     在 3.3 版的變更: The 'opener' parameter was added.  The ‘'x'’ mode
     was added.

     在 3.4 版的變更: The file is now non-inheritable.

     *note FileIO: 12a4. provides these data attributes in addition to
     those from *note RawIOBase: 106a. and *note IOBase: 1da.:

      -- 屬性: mode

          The mode as given in the constructor.

      -- 屬性: name

          The file name.  This is the file descriptor of the file when
          no name is given in the constructor.


File: python.info,  Node: Buffered Streams,  Next: 文字 I/O<2>,  Prev: 原始檔案 I/O,  Up: 類別階層

5.16.2.11 Buffered Streams
..........................

Buffered I/O streams provide a higher-level interface to an I/O device
than raw I/O does.

 -- 類別: io.BytesIO (initial_bytes=b'')

     A binary stream using an in-memory bytes buffer.  It inherits from
     *note BufferedIOBase: 63a.  The buffer is discarded when the *note
     close(): 1db. method is called.

     The optional argument 'initial_bytes' is a *note bytes-like object:
     cd4. that contains initial data.

     *note BytesIO: e46. provides or overrides these methods in addition
     to those from *note BufferedIOBase: 63a. and *note IOBase: 1da.:

      -- 方法: getbuffer ()

          Return a readable and writable view over the contents of the
          buffer without copying them.  Also, mutating the view will
          transparently update the contents of the buffer:

               >>> b = io.BytesIO(b"abcdef")
               >>> view = b.getbuffer()
               >>> view[2:4] = b"56"
               >>> b.getvalue()
               b'ab56ef'

               備註: As long as the view exists, the *note BytesIO: e46.
               object cannot be resized or closed.

          在 3.2 版被加入.

      -- 方法: getvalue ()

          Return *note bytes: 1a5. containing the entire contents of the
          buffer.

      -- 方法: read1 (size=-1, /)

          In *note BytesIO: e46, this is the same as *note read(): 12bc.

          在 3.7 版的變更: The 'size' argument is now optional.

      -- 方法: readinto1 (b, /)

          In *note BytesIO: e46, this is the same as *note readinto():
          2b09.

          在 3.5 版被加入.

 -- 類別: io.BufferedReader (raw, buffer_size=DEFAULT_BUFFER_SIZE)

     A buffered binary stream providing higher-level access to a
     readable, non seekable *note RawIOBase: 106a. raw binary stream.
     It inherits from *note BufferedIOBase: 63a.

     When reading data from this object, a larger amount of data may be
     requested from the underlying raw stream, and kept in an internal
     buffer.  The buffered data can then be returned directly on
     subsequent reads.

     The constructor creates a *note BufferedReader: 11a6. for the given
     readable 'raw' stream and 'buffer_size'.  If 'buffer_size' is
     omitted, *note DEFAULT_BUFFER_SIZE: 15c2. is used.

     *note BufferedReader: 11a6. provides or overrides these methods in
     addition to those from *note BufferedIOBase: 63a. and *note IOBase:
     1da.:

      -- 方法: peek (size=0, /)

          Return bytes from the stream without advancing the position.
          At most one single read on the raw stream is done to satisfy
          the call.  The number of bytes returned may be less or more
          than requested.

      -- 方法: read (size=-1, /)

          Read and return 'size' bytes, or if 'size' is not given or
          negative, until EOF or if the read call would block in
          non-blocking mode.

      -- 方法: read1 (size=-1, /)

          Read and return up to 'size' bytes with only one call on the
          raw stream.  If at least one byte is buffered, only buffered
          bytes are returned.  Otherwise, one raw stream read call is
          made.

          在 3.7 版的變更: The 'size' argument is now optional.

 -- 類別: io.BufferedWriter (raw, buffer_size=DEFAULT_BUFFER_SIZE)

     A buffered binary stream providing higher-level access to a
     writeable, non seekable *note RawIOBase: 106a. raw binary stream.
     It inherits from *note BufferedIOBase: 63a.

     When writing to this object, data is normally placed into an
     internal buffer.  The buffer will be written out to the underlying
     *note RawIOBase: 106a. object under various conditions, including:

        * when the buffer gets too small for all pending data;

        * when *note flush(): 2b13. is called;

        * when a *note seek(): 1224. is requested (for *note
          BufferedRandom: 2057. objects);

        * when the *note BufferedWriter: 2056. object is closed or
          destroyed.

     The constructor creates a *note BufferedWriter: 2056. for the given
     writeable 'raw' stream.  If the 'buffer_size' is not given, it
     defaults to *note DEFAULT_BUFFER_SIZE: 15c2.

     *note BufferedWriter: 2056. provides or overrides these methods in
     addition to those from *note BufferedIOBase: 63a. and *note IOBase:
     1da.:

      -- 方法: flush ()

          Force bytes held in the buffer into the raw stream.  A *note
          BlockingIOError: ffa. should be raised if the raw stream
          blocks.

      -- 方法: write (b, /)

          Write the *note bytes-like object: cd4, 'b', and return the
          number of bytes written.  When in non-blocking mode, a *note
          BlockingIOError: ffa. is raised if the buffer needs to be
          written out but the raw stream blocks.

 -- 類別: io.BufferedRandom (raw, buffer_size=DEFAULT_BUFFER_SIZE)

     A buffered binary stream providing higher-level access to a
     seekable *note RawIOBase: 106a. raw binary stream.  It inherits
     from *note BufferedReader: 11a6. and *note BufferedWriter: 2056.

     The constructor creates a reader and writer for a seekable raw
     stream, given in the first argument.  If the 'buffer_size' is
     omitted it defaults to *note DEFAULT_BUFFER_SIZE: 15c2.

     *note BufferedRandom: 2057. is capable of anything *note
     BufferedReader: 11a6. or *note BufferedWriter: 2056. can do.  In
     addition, *note seek(): 1224. and *note tell(): 2894. are
     guaranteed to be implemented.

 -- 類別: io.BufferedRWPair (reader, writer,
          buffer_size=DEFAULT_BUFFER_SIZE, /)

     A buffered binary stream providing higher-level access to two non
     seekable *note RawIOBase: 106a. raw binary streams--one readable,
     the other writeable.  It inherits from *note BufferedIOBase: 63a.

     'reader' and 'writer' are *note RawIOBase: 106a. objects that are
     readable and writeable respectively.  If the 'buffer_size' is
     omitted it defaults to *note DEFAULT_BUFFER_SIZE: 15c2.

     *note BufferedRWPair: 2b01. implements all of *note BufferedIOBase:
     63a.'s methods except for *note detach(): 285b, which raises *note
     UnsupportedOperation: 189a.

          警告: *note BufferedRWPair: 2b01. does not attempt to
          synchronize accesses to its underlying raw streams.  You
          should not pass it the same object as reader and writer; use
          *note BufferedRandom: 2057. instead.


File: python.info,  Node: 文字 I/O<2>,  Prev: Buffered Streams,  Up: 類別階層

5.16.2.12 文字 I/O
..................

 -- 類別: io.TextIOBase

     Base class for text streams.  This class provides a character and
     line based interface to stream I/O. It inherits from *note IOBase:
     1da.

     *note TextIOBase: 63b. provides or overrides these data attributes
     and methods in addition to those from *note IOBase: 1da.:

      -- 屬性: encoding

          The name of the encoding used to decode the stream's bytes
          into strings, and to encode strings into bytes.

      -- 屬性: errors

          The error setting of the decoder or encoder.

      -- 屬性: newlines

          A string, a tuple of strings, or ‘None’, indicating the
          newlines translated so far.  Depending on the implementation
          and the initial constructor flags, this may not be available.

      -- 屬性: buffer

          The underlying binary buffer (a *note BufferedIOBase: 63a.
          instance) that *note TextIOBase: 63b. deals with.  This is not
          part of the *note TextIOBase: 63b. API and may not exist in
          some implementations.

      -- 方法: detach ()

          Separate the underlying binary buffer from the *note
          TextIOBase: 63b. and return it.

          After the underlying buffer has been detached, the *note
          TextIOBase: 63b. is in an unusable state.

          Some *note TextIOBase: 63b. implementations, like *note
          StringIO: ecb, may not have the concept of an underlying
          buffer and calling this method will raise *note
          UnsupportedOperation: 189a.

          在 3.1 版被加入.

      -- 方法: read (size=-1, /)

          Read and return at most 'size' characters from the stream as a
          single *note str: 3f2.  If 'size' is negative or ‘None’, reads
          until EOF.

      -- 方法: readline (size=-1, /)

          Read until newline or EOF and return a single *note str: 3f2.
          If the stream is already at EOF, an empty string is returned.

          If 'size' is specified, at most 'size' characters will be
          read.

      -- 方法: seek (offset, whence=SEEK_SET, /)

          Change the stream position to the given 'offset'.  Behaviour
          depends on the 'whence' parameter.  The default value for
          'whence' is ‘SEEK_SET’.

             * ‘SEEK_SET’ or ‘0’: seek from the start of the stream (the
               default); 'offset' must either be a number returned by
               *note TextIOBase.tell(): 2b1a, or zero.  Any other
               'offset' value produces undefined behaviour.

             * ‘SEEK_CUR’ or ‘1’: "seek" to the current position;
               'offset' must be zero, which is a no-operation (all other
               values are unsupported).

             * ‘SEEK_END’ or ‘2’: seek to the end of the stream;
               'offset' must be zero (all other values are unsupported).

          Return the new absolute position as an opaque number.

          在 3.1 版被加入: ‘SEEK_*’ 常數。

      -- 方法: tell ()

          Return the current stream position as an opaque number.  The
          number does not usually represent a number of bytes in the
          underlying binary storage.

      -- 方法: write (s, /)

          Write the string 's' to the stream and return the number of
          characters written.

 -- 類別: io.TextIOWrapper (buffer, encoding=None, errors=None,
          newline=None, line_buffering=False, write_through=False)

     A buffered text stream providing higher-level access to a *note
     BufferedIOBase: 63a. buffered binary stream.  It inherits from
     *note TextIOBase: 63b.

     'encoding' gives the name of the encoding that the stream will be
     decoded or encoded with.  It defaults to *note
     locale.getencoding(): 2bc.  ‘encoding="locale"’ can be used to
     specify the current locale's encoding explicitly.  See *note
     文字編碼: 761. for more information.

     'errors' is an optional string that specifies how encoding and
     decoding errors are to be handled.  Pass ‘'strict'’ to raise a
     *note ValueError: 1e7. exception if there is an encoding error (the
     default of ‘None’ has the same effect), or pass ‘'ignore'’ to
     ignore errors.  (Note that ignoring encoding errors can lead to
     data loss.)  ‘'replace'’ causes a replacement marker (such as
     ‘'?'’) to be inserted where there is malformed data.
     ‘'backslashreplace'’ causes malformed data to be replaced by a
     backslashed escape sequence.  When writing, ‘'xmlcharrefreplace'’
     (replace with the appropriate XML character reference) or
     ‘'namereplace'’ (replace with ‘\N{...}’ escape sequences) can be
     used.  Any other error handling name that has been registered with
     *note codecs.register_error(): 1404. is also valid.

     'newline' controls how line endings are handled.  It can be ‘None’,
     ‘''’, ‘'\n'’, ‘'\r'’, and ‘'\r\n'’.  It works as follows:

        * When reading input from the stream, if 'newline' is ‘None’,
          *note universal newlines: ce1. mode is enabled.  Lines in the
          input can end in ‘'\n'’, ‘'\r'’, or ‘'\r\n'’, and these are
          translated into ‘'\n'’ before being returned to the caller.
          If 'newline' is ‘''’, universal newlines mode is enabled, but
          line endings are returned to the caller untranslated.  If
          'newline' has any of the other legal values, input lines are
          only terminated by the given string, and the line ending is
          returned to the caller untranslated.

        * When writing output to the stream, if 'newline' is ‘None’, any
          ‘'\n'’ characters written are translated to the system default
          line separator, *note os.linesep: 2055.  If 'newline' is ‘''’
          or ‘'\n'’, no translation takes place.  If 'newline' is any of
          the other legal values, any ‘'\n'’ characters written are
          translated to the given string.

     If 'line_buffering' is ‘True’, *note flush(): 2b03. is implied when
     a call to write contains a newline character or a carriage return.

     If 'write_through' is ‘True’, calls to *note write(): c82. are
     guaranteed not to be buffered: any data written on the *note
     TextIOWrapper: 75f. object is immediately handled to its underlying
     binary 'buffer'.

     在 3.3 版的變更: The 'write_through' argument has been added.

     在 3.3 版的變更: The default 'encoding' is now
     ‘locale.getpreferredencoding(False)’ instead of
     ‘locale.getpreferredencoding()’.  Don't change temporary the locale
     encoding using *note locale.setlocale(): 2bb, use the current
     locale encoding instead of the user preferred encoding.

     在 3.10 版的變更: The 'encoding' argument now supports the
     ‘"locale"’ dummy encoding name.

     *note TextIOWrapper: 75f. provides these data attributes and
     methods in addition to those from *note TextIOBase: 63b. and *note
     IOBase: 1da.:

      -- 屬性: line_buffering

          Whether line buffering is enabled.

      -- 屬性: write_through

          Whether writes are passed immediately to the underlying binary
          buffer.

          在 3.7 版被加入.

      -- 方法: reconfigure (*, encoding=None, errors=None, newline=None,
               line_buffering=None, write_through=None)

          Reconfigure this text stream using new settings for
          'encoding', 'errors', 'newline', 'line_buffering' and
          'write_through'.

          Parameters not specified keep current settings, except
          ‘errors='strict'’ is used when 'encoding' is specified but
          'errors' is not specified.

          It is not possible to change the encoding or newline if some
          data has already been read from the stream.  On the other
          hand, changing encoding after write is possible.

          This method does an implicit stream flush before setting the
          new parameters.

          在 3.7 版被加入.

          在 3.11 版的變更: The method supports ‘encoding="locale"’
          option.

      -- 方法: seek (cookie, whence=os.SEEK_SET, /)

          Set the stream position.  Return the new stream position as an
          *note int: 23c.

          Four operations are supported, given by the following argument
          combinations:

             * ‘seek(0, SEEK_SET)’: Rewind to the start of the stream.

             * ‘seek(cookie, SEEK_SET)’: Restore a previous position;
               'cookie' 'must be' a number returned by *note tell():
               2b1e.

             * ‘seek(0, SEEK_END)’: Fast-forward to the end of the
               stream.

             * ‘seek(0, SEEK_CUR)’: Leave the current stream position
               unchanged.

          Any other argument combinations are invalid, and may raise
          exceptions.

          也參考
          ......

          *note os.SEEK_SET: 1225, *note os.SEEK_CUR: 1226, and *note
          os.SEEK_END: 1227.

      -- 方法: tell ()

          Return the stream position as an opaque number.  The return
          value of ‘tell()’ can be given as input to *note seek(): 2b1d,
          to restore a previous stream position.

 -- 類別: io.StringIO (initial_value='', newline='\n')

     A text stream using an in-memory text buffer.  It inherits from
     *note TextIOBase: 63b.

     The text buffer is discarded when the *note close(): 1db. method is
     called.

     The initial value of the buffer can be set by providing
     'initial_value'.  If newline translation is enabled, newlines will
     be encoded as if by *note write(): 1b78.  The stream is positioned
     at the start of the buffer which emulates opening an existing file
     in a ‘w+’ mode, making it ready for an immediate write from the
     beginning or for a write that would overwrite the initial value.
     To emulate opening a file in an ‘a+’ mode ready for appending, use
     ‘f.seek(0, io.SEEK_END)’ to reposition the stream at the end of the
     buffer.

     The 'newline' argument works like that of *note TextIOWrapper: 75f,
     except that when writing output to the stream, if 'newline' is
     ‘None’, newlines are written as ‘\n’ on all platforms.

     *note StringIO: ecb. provides this method in addition to those from
     *note TextIOBase: 63b. and *note IOBase: 1da.:

      -- 方法: getvalue ()

          Return a *note str: 3f2. containing the entire contents of the
          buffer.  Newlines are decoded as if by *note read(): 1b89,
          although the stream position is not changed.

     使用範例：

          import io

          output = io.StringIO()
          output.write('First line.\n')
          print('Second line.', file=output)

          # Retrieve file contents -- this will be
          # 'First line.\nSecond line.\n'
          contents = output.getvalue()

          # Close object and discard memory buffer --
          # .getvalue() will now raise an exception.
          output.close()

 -- 類別: io.IncrementalNewlineDecoder

     A helper codec that decodes newlines for *note universal newlines:
     ce1. mode.  It inherits from *note codecs.IncrementalDecoder: 22a7.


File: python.info,  Node: Performance<3>,  Prev: 類別階層,  Up: io — 處理資料串流的核心工具

5.16.2.13 Performance
.....................

This section discusses the performance of the provided concrete I/O
implementations.

* Menu:

* 二進位 (Binary) I/O: 二進位 Binary I/O<2>.
* 文字 I/O: 文字 I/O<3>.
* Multi-threading: Multi-threading<2>.
* Reentrancy::


File: python.info,  Node: 二進位 Binary I/O<2>,  Next: 文字 I/O<3>,  Up: Performance<3>

5.16.2.14 二進位 (Binary) I/O
.............................

By reading and writing only large chunks of data even when the user asks
for a single byte, buffered I/O hides any inefficiency in calling and
executing the operating system's unbuffered I/O routines.  The gain
depends on the OS and the kind of I/O which is performed.  For example,
on some modern OSes such as Linux, unbuffered disk I/O can be as fast as
buffered I/O. The bottom line, however, is that buffered I/O offers
predictable performance regardless of the platform and the backing
device.  Therefore, it is almost always preferable to use buffered I/O
rather than unbuffered I/O for binary data.


File: python.info,  Node: 文字 I/O<3>,  Next: Multi-threading<2>,  Prev: 二進位 Binary I/O<2>,  Up: Performance<3>

5.16.2.15 文字 I/O
..................

Text I/O over a binary storage (such as a file) is significantly slower
than binary I/O over the same storage, because it requires conversions
between unicode and binary data using a character codec.  This can
become noticeable handling huge amounts of text data like large log
files.  Also, *note tell(): 2b1a. and *note seek(): 2b19. are both quite
slow due to the reconstruction algorithm used.

*note StringIO: ecb, however, is a native in-memory unicode container
and will exhibit similar speed to *note BytesIO: e46.


File: python.info,  Node: Multi-threading<2>,  Next: Reentrancy,  Prev: 文字 I/O<3>,  Up: Performance<3>

5.16.2.16 Multi-threading
.........................

*note FileIO: 12a4. objects are thread-safe to the extent that the
operating system calls (such as ‘read(2)(1)’ under Unix) they wrap are
thread-safe too.

Binary buffered objects (instances of *note BufferedReader: 11a6, *note
BufferedWriter: 2056, *note BufferedRandom: 2057. and *note
BufferedRWPair: 2b01.) protect their internal structures using a lock;
it is therefore safe to call them from multiple threads at once.

*note TextIOWrapper: 75f. objects are not thread-safe.

   ---------- Footnotes ----------

   (1) https://manpages.debian.org/read(2)


File: python.info,  Node: Reentrancy,  Prev: Multi-threading<2>,  Up: Performance<3>

5.16.2.17 Reentrancy
....................

Binary buffered objects (instances of *note BufferedReader: 11a6, *note
BufferedWriter: 2056, *note BufferedRandom: 2057. and *note
BufferedRWPair: 2b01.) are not reentrant.  While reentrant calls will
not happen in normal situations, they can arise from doing I/O in a
*note signal: b4. handler.  If a thread tries to re-enter a buffered
object which it is already accessing, a *note RuntimeError: 179. is
raised.  Note this doesn't prohibit a different thread from entering the
buffered object.

The above implicitly extends to text files, since the *note open(): 4c0.
function will wrap a buffered object inside a *note TextIOWrapper: 75f.
This includes standard streams and therefore affects the built-in *note
print(): f18. function as well.


File: python.info,  Node: time --- 時間存取與轉換,  Next: argparse --- Parser for command-line options arguments and sub-commands,  Prev: io — 處理資料串流的核心工具,  Up: 通用作業系統服務

5.16.3 ‘time’ -- 時間存取與轉換
-------------------------------

__________________________________________________________________

這個模組提供了各種與時間相關的函式。若要查看相關功能，請參閱 *note
datetime: 28. 和 *note calendar: 10. 模組。

雖然這個模組隨時可用，但並非所有函式在所有平台上都可用。這個模組中定義的
大多數函式都會呼叫 C 語言平台的函式庫中具有相同名稱的函式。由於這些函式
的語義因平台而異，所以偶爾查閱平台文件可能會有所幫助。

以下是對一些術語和慣例的說明。

   * 'epoch' 是起始的時間點，即 ‘time.gmtime(0)’ 的回傳值。在所有平台上
     ，它是 1970 年 1 月 1 日，00:00:00（UTC）。

   * 術語 'seconds since the epoch（紀元秒數）' 是指從 epoch（紀元）開始
     經過的總秒數，通常不包括 leap seconds(1)。在所有符合 POSIX 標準的平
     台上，leap seconds （閏秒）都不計入這個總數。

   * 這個模組中的函式可能無法處理 *note epoch: 2908. 之前或遙遠未來的日
     期和時間。未來的臨界點由 C 函式庫決定；對於 32 位元系統來說通常是在
     2038 年。

   * 函式 *note strptime(): 139a. 在給定 ‘%y’ 格式碼時可以剖析 (parse) 兩
     位數的年份。當剖析兩位數的年份時，它們會根據 POSIX 和 ISO C 標準進
     行轉換：69-99 的值對映到 1969-1999，0-68 的值對映到 2000-2068。

   * UTC 是 Coordinated Universal Time -- 世界協調時間（原稱為格林威治標
     準時間，或 GMT）。縮寫 UTC 並不是寫錯，而是英文和法文之間折衷的結果
     。

   * DST 是 Daylight Saving Time（日光節約時間），一年中的某些時段（通常
     ）將會時區調整一小時。DST 的規則是根據當地法律決定的，且可能每年不
     同。C 函式庫有一個包含當地規則的表（通常會為了靈活性而從系統文件中
     讀取），在這方面是唯一的真正依據。

   * 各種即時 (real-time) 函式的精確度可能低於其值或引數所表示的單位所建
     議的精確度。例如，在大多數 Unix 系統上，時鐘每秒只「跳」50 次或 100
     次。

   * 另一方面，*note time(): 239. 和 *note sleep(): 642. 的精確度比它們
     的在 Unix 的等效函式更高：時間以浮點數表示，*note time(): 239. 回傳
     最精確的可用時間（如果可以會使用 Unix 的 ‘gettimeofday()’），而
     *note sleep(): 642. 可以接受帶有非零分數的時間（如果可以會使用 Unix
     的 ‘select()’ 來實作）。

   * 由 *note gmtime(): 1158.、*note localtime(): 1467. 和 *note
     strptime(): 139a. 回傳，並由 *note asctime(): 117f.、*note
     mktime(): 1180. 和 *note strftime(): 1181. 接受的時間值，是一個 9 個
     整數的序列。*note gmtime(): 1158.、*note localtime(): 1467. 和
     *note strptime(): 139a. 的回傳值也為各個欄位提供屬性名稱。

     關於這些物件的敘述請見 *note struct_time: c91.。

     在 3.3 版的變更: 當平台支援對應的 ‘struct tm’ 成員時，*note
     struct_time: c91. 型別被擴展以提供 *note tm_gmtoff: 2b27. 和 *note
     tm_zone: 2b28. 屬性。

     在 3.6 版的變更: *note struct_time: c91. 的屬性 *note tm_gmtoff:
     2b27. 和 *note tm_zone: 2b28. 現在在所有平台上都可用。

   * 使用以下函式在時間表示之間進行轉換：

     轉換來源                      轉換目標                      使用
                                                                 
     ------------------------------------------------------------------------------------------
                                                                 
     紀元秒數                      世界協調時間的                *note gmtime(): 1158.
                                   *note struct_time: c91.       
                                   
                                                                 
     紀元秒數                      本地時間的                    *note localtime(): 1467.
                                   *note struct_time: c91.       
                                   
                                                                 
     世界協調時間的                紀元秒數                      *note calendar.timegm(): 23ae.
     *note struct_time: c91.                                     

     本地時間的                    紀元秒數                      *note mktime(): 1180.
     *note struct_time: c91.                                     

* Menu:

* 函式: 函式<4>.
* Clock ID Constants::
* Timezone Constants::

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Leap_second


File: python.info,  Node: 函式<4>,  Next: Clock ID Constants,  Up: time --- 時間存取與轉換

5.16.3.1 函式
.............

 -- 函式: time.asctime ([t])

     將由 *note gmtime(): 1158. 或 *note localtime(): 1467. 回傳的元組或
     *note struct_time: c91. 表示的時間轉換為以下格式的字串：‘'Sun Jun
     20 23:21:05 1993'’。日期欄位為兩個字元長，如果日期是個位數，則用空
     格填充，例如：‘'Wed Jun 9 04:26:40 1993'’。

     如果沒有提供 't'，則使用由 *note localtime(): 1467. 回傳的當前時間
     。*note asctime(): 117f. 不使用區域資訊。

          備註: 與同名的 C 函式不同，*note asctime(): 117f. 不會添加結尾
          的換行字元。

 -- 函式: time.pthread_getcpuclockid (thread_id)

     為指定的 'thread_id' 回傳執行緒專用 CPU-time 時鐘的 'clk_id'。

     使用 *note threading.get_ident(): 10f3. 或 *note threading.Thread:
     8f0. 物件的 *note ident: 2b2b. 屬性來獲取適用於 'thread_id' 的值。

          警告: 傳遞無效或過期的 'thread_id' 可能會導致未定義的行為，例
          如分段錯誤 (segmentation fault)。

     *note 適用: 1c56.：Unix

     若需更多資訊，請參閱 ‘pthread_getcpuclockid(3)(1)’ 的說明文件。

     在 3.7 版被加入.

 -- 函式: time.clock_getres (clk_id)

     回傳指定時鐘 'clk_id' 的解析度（精確度）。有關 'clk_id' 可接受的值
     的串列，請參閱 *note Clock ID Constants: 2a9d.。

     *note 適用: 1c56.：Unix。

     在 3.3 版被加入.

 -- 函式: time.clock_gettime (clk_id) -> float

     回傳指定時鐘 'clk_id' 的時間。有關 'clk_id' 可接受的值的串列，請參
     閱 *note Clock ID Constants: 2a9d.。

     使用 *note clock_gettime_ns(): a85. 以避免 *note float: 2c8. 型別造
     成的精確度損失。

     *note 適用: 1c56.：Unix。

     在 3.3 版被加入.

 -- 函式: time.clock_gettime_ns (clk_id) -> int

     類似於 *note clock_gettime(): 10f7.，但回傳以奈秒 (nanoseconds) 為
     單位的時間。

     *note 適用: 1c56.：Unix。

     在 3.7 版被加入.

 -- 函式: time.clock_settime (clk_id, time: float)

     設定指定時鐘 'clk_id' 的時間。目前，*note CLOCK_REALTIME: 63f. 是
     'clk_id' 唯一可以接受的值。

     使用 *note clock_settime_ns(): a86. 以避免 *note float: 2c8. 型別造
     成的精確度損失。

     *note 適用: 1c56.：Unix。

     在 3.3 版被加入.

 -- 函式: time.clock_settime_ns (clk_id, time: int)

     類似於 *note clock_settime(): 10f8.，但設定以奈秒為單位的時間。

     *note 適用: 1c56.：Unix。

     在 3.7 版被加入.

 -- 函式: time.ctime ([secs])

     將自 *note epoch: 2908. 起以秒表示的時間轉換為表示當地時間且符合以
     下格式的字串：‘'Sun Jun 20 23:21:05 1993'’。日期欄位為兩個字元長，
     如果日期是個位數，則用空格填充，例如：‘'Wed Jun 9 04:26:40 1993'’。

     如果未提供 'secs' 或其為 *note None: 61b.，則使用由 *note time():
     239. 回傳的當前時間。‘ctime(secs)’ 等同於
     ‘asctime(localtime(secs))’。*note ctime(): 232f. 不使用區域資訊。

 -- 函式: time.get_clock_info (name)

     獲取指定時鐘的資訊作為命名空間物件。支援的時鐘名稱及讀取他們的值的
     對應函式如下：

        * ‘'monotonic'’：*note time.monotonic(): 238.

        * ‘'perf_counter'’：*note time.perf_counter(): a2b.

        * ‘'process_time'’：*note time.process_time(): a2c.

        * ‘'thread_time'’：*note time.thread_time(): 8da.

        * ‘'time'’：*note time.time(): 239.

     其結果具有以下屬性：

        - 'adjustable': 如果時鐘可以自動（例如，透過 NTP 常駐程式）或由
          系統管理員手動更改，則為 ‘True’，否則為 ‘False’

        - 'implementation': 用於獲取時鐘的值的底層 C 函式名稱。有關可能
          的值，請參閱 *note Clock ID Constants: 2a9d.。

        - 'monotonic': 如果時鐘不能倒轉，則為 ‘True’，否則為 ‘False’

        - 'resolution': 以秒 (*note float: 2c8.) 為單位的時鐘的解析度

     在 3.3 版被加入.

 -- 函式: time.gmtime ([secs])

     將自 *note epoch: 2908. 起以秒表示的時間轉換為 UTC 中的 *note
     struct_time: c91.，其中 dst 旗標始終為零。如果未提供 'secs' 或其為
     *note None: 61b.，則使用由 *note time(): 239. 回傳的當前時間。忽略
     秒的分數部分。關於 *note struct_time: c91. 物件的描述，請參閱上文。
     此函式的反運算請參閱 *note calendar.timegm(): 23ae.。

 -- 函式: time.localtime ([secs])

     類似於 *note gmtime(): 1158.，但轉換為當地時間。如果未提供 'secs' 或
     其為 *note None: 61b.，則使用由 *note time(): 239. 回傳的當前時間。
     當 DST 適用於給定時間時，dst 旗標會被設定為 ‘1’。

     如果時間戳超出 C 平台的 ‘localtime()’ 或 ‘gmtime()’ 函式支援的範圍
     ，*note localtime(): 1467. 可能會引發 *note OverflowError: 825.；在
     ‘localtime()’ 或 ‘gmtime()’ 失敗時，會引發 *note OSError: 350.。通
     常會把年份限制在 1970 年到 2038 年之間。

 -- 函式: time.mktime (t)

     這是 *note localtime(): 1467. 的反函式。其引數是表示'當地'時間（不
     是 UTC）的 *note struct_time: c91. 或完整的 9 元組（因為需要 dst 旗
     標；如果 dst 為未知，則使用 ‘-1’ 作為 dst 旗標）。它回傳一個浮點數
     ，以與 *note time(): 239. 相容。如果輸入值不能表示為有效時間，將引
     發 *note OverflowError: 825. 或 *note ValueError: 1e7.（取決於無效
     值是被 Python 還是底層 C 函式庫捕獲）。它能生成時間的最早日期根據平
     台而有所不同。

 -- 函式: time.monotonic () -> float

     回傳單調時鐘（monotonic clock，即不能倒轉的時鐘）的值（以帶有小數的
     秒數表示）。該時鐘不受系統時鐘更新的影響。回傳值的參考點沒有定義，
     因此只有兩次呼叫結果之間的差異才是有效的。

     Clock:

        * On Windows, call ‘QueryPerformanceCounter()’ and
          ‘QueryPerformanceFrequency()’.

        * On macOS, call ‘mach_absolute_time()’ and
          ‘mach_timebase_info()’.

        * On HP-UX, call ‘gethrtime()’.

        * Call ‘clock_gettime(CLOCK_HIGHRES)’ if available.

        * Otherwise, call ‘clock_gettime(CLOCK_MONOTONIC)’.

     使用 *note monotonic_ns(): a87. 以避免 *note float: 2c8. 型別造成的
     精確度損失。

     在 3.3 版被加入.

     在 3.5 版的變更: 此函式現在始終可用且涵蓋整個系統。

     在 3.10 版的變更: 在 macOS 上，此函式現在涵蓋整個系統。

 -- 函式: time.monotonic_ns () -> int

     類似於 *note monotonic(): 238.，但回傳以奈秒為單位的時間。

     在 3.7 版被加入.

 -- 函式: time.perf_counter () -> float

     回傳性能計數器的值（以帶有小數的秒數表示），即具有最高可用解析度來
     測量短時間間隔的時鐘。它包括睡眠時經過的時間，並且涵蓋整個系統。回
     傳值的參考點沒有定義，因此只有兩次呼叫結果之間的差異才是有效的。

     'CPython 實作細節：' On CPython, use the same clock than *note
     time.monotonic(): 238. and is a monotonic clock, i.e.  a clock that
     cannot go backwards.

     使用 *note perf_counter_ns(): a88. 以避免 *note float: 2c8. 型別造
     成的精確度損失。

     在 3.3 版被加入.

     在 3.10 版的變更: 在 Windows 上，此函式現在涵蓋整個系統。

     在 3.13 版的變更: Use the same clock than *note time.monotonic():
     238.

 -- 函式: time.perf_counter_ns () -> int

     類似於 *note perf_counter(): a2b.，但回傳以奈秒為單位的時間。

     在 3.7 版被加入.

 -- 函式: time.process_time () -> float

     回傳當前行程的系統和用戶 CPU 時間之和（以帶有小數的秒數表示）。它不
     包括睡眠時經過的時間。根據定義，它涵蓋整個行程。回傳值的參考點沒有
     定義，因此只有兩次呼叫結果之間的差異才是有效的。

     使用 *note process_time_ns(): a89. 以避免 *note float: 2c8. 型別造
     成的精確度損失。

     在 3.3 版被加入.

 -- 函式: time.process_time_ns () -> int

     類似於 *note process_time(): a2c.，但回傳以奈秒為單位的時間。

     在 3.7 版被加入.

 -- 函式: time.sleep (secs)

     在一個給定的秒數內暫停呼叫執行緒 (calling thread) 的執行。引數可以
     是浮點數，以表示更精確的睡眠時間。

     如果睡眠被訊號中斷且訊號處理器未引發例外，則睡眠將以重新計算過的逾
     時 (timeout) 重新開始。

     由於系統中其他活動的調度，暫停時間可能會比請求的時間長任意的量。

     在 Windows 上，如果 'secs' 為零，則執行緒將其剩餘的時間片段讓給任何
     準備運行的其他執行緒。如果沒有其他執行緒準備運行，該函式將立即回傳
     ，而執行緒會繼續執行。在 Windows 8.1 及更新的版本中，此實作使用高解
     析度計時器(2)，其解析度為 100 奈秒。如果 'secs' 為零，則使用
     ‘Sleep(0)’。

     Unix 實作：

        * 如果可以，使用 ‘clock_nanosleep()’（解析度：1 奈秒）；

        * 或者使用 ‘nanosleep()’（解析度：1 奈秒）；

        * 或使用 ‘select()’（解析度：1 微秒）。

     Raises an *note auditing event: 17bd. ‘time.sleep’ with argument
     ‘secs’.

     在 3.5 版的變更: 即使睡眠被訊號中斷，此函式現在至少還是會睡眠
     'secs'，除非訊號處理器引發例外（理由請參閱 PEP 475(3)）。

     在 3.11 版的變更: 在 Unix 上，如果可以的話現在會使用
     ‘clock_nanosleep()’ 和 ‘nanosleep()’ 函式。在 Windows 上，現在使用
     可等待的計時器。

     在 3.13 版的變更: Raises an auditing event.

 -- 函式: time.strftime (format[, t])

     將由 *note gmtime(): 1158. 或 *note localtime(): 1467. 回傳代表時間
     的一個元組或 *note struct_time: c91. 轉換為由 'format' 引數指定的字
     串。如果未提供 't'，則使用由 *note localtime(): 1467. 回傳的當前時
     間。'format' 必須是一個字串。如果 't' 中的任何欄位超出允許範圍，將
     會引發 *note ValueError: 1e7.。

     0 在時間元組中的任何位置都是合法引數；如果元組中出現常見的錯誤，該
     值將被強制更改為正確的值。

     以下指令可以嵌入在 'format' 字串中。它們顯示時不帶可選的欄位寬度和
     精度規範，並在 *note strftime(): 1181. 的結果中被標示的字元替換：

     指令            意義                                                 註解
                                                                          
     ---------------------------------------------------------------------------------
                                                                          
     ‘%a’            區域設定的週間日 (weekday) 縮寫名稱。
                     
                                                                          
     ‘%A’            區域設定的完整週間日名稱。
                     
                                                                          
     ‘%b’            區域設定的縮寫月份名稱。
                     
                                                                          
     ‘%B’            區域設定的完整月份名稱。
                     
                                                                          
     ‘%c’            區域設定的合適的日期和時間的表示法。
                     
                                                                          
     ‘%d’            月份中的日期，表示為十進位數 [01,31]。
                     
                                                                          
     ‘%f’            微秒，表示為十進位數                                 (1)
                                                                          
                          [000000,999999]。
                     
                                                                          
     ‘%H’            小時（24 小時制），表示為十進位數 [00,23]。
                     
                                                                          
     ‘%I’            小時（12 小時制），表示為十進位數 [01,12]。
                     
                                                                          
     ‘%j’            一年中的第幾天，表示為十進位數 [001,366]。
                     
                                                                          
     ‘%m’            月份，表示為十進位數 [01,12]。
                     
                                                                          
     ‘%M’            分鐘，表示為十進位數 [00,59]。
                     
                                                                          
     ‘%p’            區域設定中相當於 AM 或 PM 的表示。                   (2)
                                                                          
                                                                          
     ‘%S’            秒，表示為十進位數 [00,61]。                         (3)
                                                                          
                                                                          
     ‘%U’            一年中的週數（星期天作為一週的第一天），表示為十進   (4)
                     位數 [00,53]。新的一年中，在第一個星期天之前的所有   
                     日子都被認定為第 0 週。
                     
                                                                          
     ‘%w’            週間日，表示為十進位數 [0（星期天）,6]。
                     
                                                                          
     ‘%W’            一年中的週數（星期一作為一週的第一天），表示為十進   (4)
                     位數 [00,53]。新的一年中，在第一個星期一之前的所有   
                     日子都被認定為第 0 週。
                     
                                                                          
     ‘%x’            區域設定的合適的日期表示法。
                     
                                                                          
     ‘%X’            區域設定的合適的時間表示法。
                     
                                                                          
     ‘%y’            去掉世紀的年份，表示為十進位數 [00,99]。
                     
                                                                          
     ‘%Y’            帶世紀的年份，表示為十進位數。
                     
                                                                          
     ‘%z’            時區偏移量，表示與 UTC/GMT 的正或負時間差，形式為
                     +HHMM 或 -HHMM，其中 H 代表十進位的小時數碼
                     (digits)，M 代表十進位的分鐘數碼 [-23:59, +23:59]。
                     (4)
                     
                                                                          
     ‘%Z’            時區名稱（如果不存在時區，則無字元）。已被棄用。
                     (5)
                     
                                                                          
     ‘%%’            字面意義上的 ‘'%'’ 字元。
                     

     註解：

       1. ‘%f’ 格式的指令僅適用於 *note strptime(): 139a.，不適用於
          *note strftime(): 1181.。然而，在 *note
          datetime.datetime.strptime(): 14fe. 和 *note
          datetime.datetime.strftime(): c37. 其中的 ‘%f’ 格式的指令*note
          適用於微秒: 2300.。

       2. 當與 *note strptime(): 139a. 函式一起使用時，‘%p’ 指令僅在使用
          ‘%I’ 指令剖析小時時影響輸出小時的欄位。

       3. 範圍確實是從 ‘0’ 到 ‘61’；數值 ‘60’ 在表示 leap seconds(6) 的
          時間戳中是有效的，而數值 ‘61’ 是出於歷史因素而被支援。

       4. 當與 *note strptime(): 139a. 函式一起使用時，‘%U’ 和 ‘%W’ 僅在
          指定週間的某天和年份時用於計算中。

     以下是一個範例，其為一種與 RFC 2822(7) 網際網路電子郵件標準中指定的
     日期格式兼容的格式。 (8)：

          >>> from time import gmtime, strftime
          >>> strftime("%a, %d %b %Y %H:%M:%S +0000", gmtime())
          'Thu, 28 Jun 2001 14:17:15 +0000'

     某些平台可能支援額外的指令，但只有這裡列出的指令具有 ANSI C 標準化
     的意義。要查看你的平台上支援的完整格式碼集，請參閱 ‘strftime(3)(9)’
     文件。

     在某些平台上，可選的欄位寬度和精度規範可以以此順序緊跟在指令初始的
     ‘'%'’ 之後；這也是不可攜 (portable) 的。欄位寬度通常為 2，除了 ‘%j’
     為 3。

 -- 函式: time.strptime (string[, format])

     根據格式剖析表示時間的字串。回傳值是 *note struct_time: c91.，如同
     由 *note gmtime(): 1158. 或 *note localtime(): 1467. 回傳的一樣。

     'format' 參數使用與 *note strftime(): 1181. 相同的指令；預設為 ‘"%a
     %b %d %H:%M:%S %Y"’，與 *note ctime(): 232f. 回傳的格式匹配。如果
     'string' 無法根據 'format' 解析，或剖析後有多餘的資料，將引發 *note
     ValueError: 1e7.。當無法推斷更精確的值時，用來填充任何缺失資料的預
     設值為 ‘(1900, 1, 1, 0, 0, 0, 0, 1, -1)’。'string' 和 'format' 都必
     須是字串。

     例如：

          >>> import time
          >>> time.strptime("30 Nov 00", "%d %b %y")
          time.struct_time(tm_year=2000, tm_mon=11, tm_mday=30, tm_hour=0, tm_min=0,
                           tm_sec=0, tm_wday=3, tm_yday=335, tm_isdst=-1)

     對 ‘%Z’ 指令的支援基於 ‘tzname’ 中包含的值以及 ‘daylight’ 是否為
     true。因此，除了識別始終已知的 UTC 和 GMT（且被考慮為非日光節約時區
     ）外，這是特定於平台的。

     僅支援文檔中指定的指令。由於 ‘strftime()’ 是根據每個平台實作的，有
     時它可以提供比列出的還要更多的指令。但是 ‘strptime()’ 與任何平台無
     關，因此不一定支援所有未記載為支援的指令。

 -- 類別: time.struct_time

     由 *note gmtime(): 1158.、*note localtime(): 1467. 和 *note
     strptime(): 139a. 回傳的時間值序列的型別。它是一個具有 *note named
     tuple: 5f4. 介面的物件：值可以通過索引和屬性名稱存取。包含以下值：

     索引                                  屬性                                  值
                                                                                 
                                                                                 
     0                                      -- 屬性: tm_year                     （例如 1993）
                                                                                 
                                                                                 
     1                                      -- 屬性: tm_mon                      範圍 [1, 12]
                                                                                 
                                                                                 
     2                                      -- 屬性: tm_mday                     範圍 [1, 31]
                                                                                 
                                                                                 
     3                                      -- 屬性: tm_hour                     範圍 [0, 23]
                                                                                 
                                                                                 
     4                                      -- 屬性: tm_min                      範圍 [0, 59]
                                                                                 
                                                                                 
     5                                      -- 屬性: tm_sec                      範圍 [0, 61]；參見
                                                                                 *note strftime(): 1181. 中的
                                                                                 *note 註釋 (2): 2b2c.
                                                                                 
                                                                                 
     6                                      -- 屬性: tm_wday                     範圍 [0, 6]；星期一是 0
                                                                                 
                                                                                 
     7                                      -- 屬性: tm_yday                     範圍 [1, 366]
                                                                                 
                                                                                 
     8                                      -- 屬性: tm_isdst                    0、1 或 -1；見下文
                                                                                 
                                                                                 
     N/A                                    -- 屬性: tm_zone                     時區名稱的縮寫
                                                                                 
                                                                                 
     N/A                                    -- 屬性: tm_gmtoff                   UTC 向東的偏移量（以秒為單位）
                                                                                 

     請注意，與 C 結構不同，月份值的範圍是 [1, 12]，而不是 [0, 11]。

     在呼叫 *note mktime(): 1180. 時，當日光節約時間生效的時候，*note
     tm_isdst: 2340. 可以設定為 1，不生效時設定為 0。值 -1 表示未知是否
     生效，通常結果會填入正確的狀態。

     當一個長度不正確的元組被傳遞給預期得到 *note struct_time: c91. 的函
     式時，或者其中有元素型別錯誤時，將引發 *note TypeError: 4dd.。

 -- 函式: time.time () -> float

     回傳自 *note epoch: 2908. 起的時間（秒）至今的浮點數。對 leap
     seconds(10) 的處理是與平台有關的。在 Windows 和大多數 Unix 系統上，
     閏秒不計入自 *note epoch: 2908. 起的秒數中。這通常被稱為 Unix 時間
     (11)。

     請注意，即使時間始終作為浮點數回傳，但並非所有系統都提供比 1 秒還更
     精確的時間。雖然此函式通常回傳非遞減的值，但如果在兩次呼叫之間系統
     時鐘被回調，則它可能回傳比之前呼叫更小的值。

     由 *note time(): 239. 回傳的數字可以通過傳遞給 *note gmtime():
     1158. 函式轉換為 UTC 內更常見的時間格式（即年、月、日、小時等）或通
     過傳遞給 *note localtime(): 1467. 函式轉換為當地時間。在這兩種情況
     下都會回傳一個 *note struct_time: c91. 物件，從中可以作為屬性存取日
     曆日期的組成部分。

     Clock:

        * On Windows, call ‘GetSystemTimeAsFileTime()’.

        * Call ‘clock_gettime(CLOCK_REALTIME)’ if available.

        * Otherwise, call ‘gettimeofday()’.

     使用 *note time_ns(): a8a. 以避免 *note float: 2c8. 型別造成的精確
     度損失。

 -- 函式: time.time_ns () -> int

     類似於 *note time(): 239.，但回傳自 *note epoch: 2908. 起的以奈秒為
     單位的整數。

     在 3.7 版被加入.

 -- 函式: time.thread_time () -> float

     Return the value (in fractional seconds) of the sum of the system
     and user CPU time of the current thread.  It does not include time
     elapsed during sleep.  It is thread-specific by definition.  The
     reference point of the returned value is undefined, so that only
     the difference between the results of two calls in the same thread
     is valid.

     Use *note thread_time_ns(): b38. to avoid the precision loss caused
     by the *note float: 2c8. type.

     *note 適用: 1c56.：Linux、Unix、Windows。

     Unix systems supporting ‘CLOCK_THREAD_CPUTIME_ID’.

     在 3.7 版被加入.

 -- 函式: time.thread_time_ns () -> int

     Similar to *note thread_time(): 8da. but return time as
     nanoseconds.

     在 3.7 版被加入.

 -- 函式: time.tzset ()

     Reset the time conversion rules used by the library routines.  The
     environment variable ‘TZ’ specifies how this is done.  It will also
     set the variables ‘tzname’ (from the ‘TZ’ environment variable),
     ‘timezone’ (non-DST seconds West of UTC), ‘altzone’ (DST seconds
     west of UTC) and ‘daylight’ (to 0 if this timezone does not have
     any daylight saving time rules, or to nonzero if there is a time,
     past, present or future when daylight saving time applies).

     *note 適用: 1c56.：Unix。

          備註: Although in many cases, changing the ‘TZ’ environment
          variable may affect the output of functions like *note
          localtime(): 1467. without calling *note tzset(): 2b34, this
          behavior should not be relied on.

          The ‘TZ’ environment variable should contain no whitespace.

     The standard format of the ‘TZ’ environment variable is (whitespace
     added for clarity):

          std offset [dst [offset [,start[/time], end[/time]]]]

     Where the components are:

     ‘std’ 和 ‘dst’

          Three or more alphanumerics giving the timezone abbreviations.
          These will be propagated into time.tzname

     ‘offset’

          The offset has the form: ‘± hh[:mm[:ss]]’.  This indicates the
          value added the local time to arrive at UTC. If preceded by a
          '-', the timezone is east of the Prime Meridian; otherwise, it
          is west.  If no offset follows dst, summer time is assumed to
          be one hour ahead of standard time.

     ‘start[/time], end[/time]’

          Indicates when to change to and back from DST. The format of
          the start and end dates are one of the following:

          ‘JN’

               The Julian day 'n' (1 <= 'n' <= 365).  Leap days are not
               counted, so in all years February 28 is day 59 and March
               1 is day 60.

          ‘N’

               The zero-based Julian day (0 <= 'n' <= 365).  Leap days
               are counted, and it is possible to refer to February 29.

          ‘MM.N.D’

               The 'd"th day (0 <= 'd' <= 6) of week 'n' of month 'm' of
               the year (1 <= 'n' <= 5, 1 <= 'm' <= 12, where week 5
               means "the last 'd' day in month 'm'" which may occur in
               either the fourth or the fifth week).  Week 1 is the
               first week in which the 'd"th day occurs.  Day zero is a
               Sunday.

          ‘time’ has the same format as ‘offset’ except that no leading
          sign ('-' or '+') is allowed.  The default, if time is not
          given, is 02:00:00.

          >>> os.environ['TZ'] = 'EST+05EDT,M4.1.0,M10.5.0'
          >>> time.tzset()
          >>> time.strftime('%X %x %Z')
          '02:07:36 05/08/03 EDT'
          >>> os.environ['TZ'] = 'AEST-10AEDT-11,M10.5.0,M3.5.0'
          >>> time.tzset()
          >>> time.strftime('%X %x %Z')
          '16:08:12 05/08/03 AEST'

     On many Unix systems (including *BSD, Linux, Solaris, and Darwin),
     it is more convenient to use the system's zoneinfo
     (‘tzfile(5)(12)’) database to specify the timezone rules.  To do
     this, set the ‘TZ’ environment variable to the path of the required
     timezone datafile, relative to the root of the systems 'zoneinfo'
     timezone database, usually located at ‘/usr/share/zoneinfo’.  For
     example, ‘'US/Eastern'’, ‘'Australia/Melbourne'’, ‘'Egypt'’ or
     ‘'Europe/Amsterdam'’.

          >>> os.environ['TZ'] = 'US/Eastern'
          >>> time.tzset()
          >>> time.tzname
          ('EST', 'EDT')
          >>> os.environ['TZ'] = 'Egypt'
          >>> time.tzset()
          >>> time.tzname
          ('EET', 'EEST')

   ---------- Footnotes ----------

   (1) https://manpages.debian.org/pthread_getcpuclockid(3)

   (2) 
https://docs.microsoft.com/en-us/windows-hardware/drivers/kernel/high-resolution-timers

   (3) https://peps.python.org/pep-0475/

   (4) The use of ‘%Z’ is now deprecated, but the ‘%z’ escape that
expands to the preferred hour/minute offset is not supported by all ANSI
C libraries.  Also, a strict reading of the original 1982 RFC 822
(https://datatracker.ietf.org/doc/html/rfc822.html) standard calls for a
two-digit year (‘%y’ rather than ‘%Y’), but practice moved to 4-digit
years long before the year 2000.  After that, RFC 822
(https://datatracker.ietf.org/doc/html/rfc822.html) became obsolete and
the 4-digit year has been first recommended by RFC 1123
(https://datatracker.ietf.org/doc/html/rfc1123.html) and then mandated
by RFC 2822 (https://datatracker.ietf.org/doc/html/rfc2822.html).

   (5) The use of ‘%Z’ is now deprecated, but the ‘%z’ escape that
expands to the preferred hour/minute offset is not supported by all ANSI
C libraries.  Also, a strict reading of the original 1982 RFC 822
(https://datatracker.ietf.org/doc/html/rfc822.html) standard calls for a
two-digit year (‘%y’ rather than ‘%Y’), but practice moved to 4-digit
years long before the year 2000.  After that, RFC 822
(https://datatracker.ietf.org/doc/html/rfc822.html) became obsolete and
the 4-digit year has been first recommended by RFC 1123
(https://datatracker.ietf.org/doc/html/rfc1123.html) and then mandated
by RFC 2822 (https://datatracker.ietf.org/doc/html/rfc2822.html).

   (6) https://en.wikipedia.org/wiki/Leap_second

   (7) https://datatracker.ietf.org/doc/html/rfc2822.html

   (8) The use of ‘%Z’ is now deprecated, but the ‘%z’ escape that
expands to the preferred hour/minute offset is not supported by all ANSI
C libraries.  Also, a strict reading of the original 1982 RFC 822
(https://datatracker.ietf.org/doc/html/rfc822.html) standard calls for a
two-digit year (‘%y’ rather than ‘%Y’), but practice moved to 4-digit
years long before the year 2000.  After that, RFC 822
(https://datatracker.ietf.org/doc/html/rfc822.html) became obsolete and
the 4-digit year has been first recommended by RFC 1123
(https://datatracker.ietf.org/doc/html/rfc1123.html) and then mandated
by RFC 2822 (https://datatracker.ietf.org/doc/html/rfc2822.html).

   (9) https://manpages.debian.org/strftime(3)

   (10) https://en.wikipedia.org/wiki/Leap_second

   (11) https://en.wikipedia.org/wiki/Unix_time

   (12) https://manpages.debian.org/tzfile(5)


File: python.info,  Node: Clock ID Constants,  Next: Timezone Constants,  Prev: 函式<4>,  Up: time --- 時間存取與轉換

5.16.3.2 Clock ID Constants
...........................

These constants are used as parameters for *note clock_getres(): 10f6.
and *note clock_gettime(): 10f7.

 -- 資料: time.CLOCK_BOOTTIME

     Identical to *note CLOCK_MONOTONIC: b35, except it also includes
     any time that the system is suspended.

     This allows applications to get a suspend-aware monotonic clock
     without having to deal with the complications of *note
     CLOCK_REALTIME: 63f, which may have discontinuities if the time is
     changed using ‘settimeofday()’ or similar.

     *note 適用: 1c56.：Linux 2.6.39 以上。

     在 3.7 版被加入.

 -- 資料: time.CLOCK_HIGHRES

     The Solaris OS has a ‘CLOCK_HIGHRES’ timer that attempts to use an
     optimal hardware source, and may give close to nanosecond
     resolution.  ‘CLOCK_HIGHRES’ is the nonadjustable, high-resolution
     clock.

     *note 適用: 1c56.：Solaris。

     在 3.3 版被加入.

 -- 資料: time.CLOCK_MONOTONIC

     Clock that cannot be set and represents monotonic time since some
     unspecified starting point.

     *note 適用: 1c56.：Unix。

     在 3.3 版被加入.

 -- 資料: time.CLOCK_MONOTONIC_RAW

     Similar to *note CLOCK_MONOTONIC: b35, but provides access to a raw
     hardware-based time that is not subject to NTP adjustments.

     *note 適用: 1c56.：Linux 2.6.28 以上、macOS 10.12 以上。

     在 3.3 版被加入.

 -- 資料: time.CLOCK_MONOTONIC_RAW_APPROX

     Similar to *note CLOCK_MONOTONIC_RAW: 2b37, but reads a value
     cached by the system at context switch and hence has less accuracy.

     *note 適用: 1c56.：macOS 10.12 以上。

     在 3.13 版被加入.

 -- 資料: time.CLOCK_PROCESS_CPUTIME_ID

     High-resolution per-process timer from the CPU.

     *note 適用: 1c56.：Unix。

     在 3.3 版被加入.

 -- 資料: time.CLOCK_PROF

     High-resolution per-process timer from the CPU.

     *note 適用: 1c56.：FreeBSD、NetBSD 7 以上、OpenBSD。

     在 3.7 版被加入.

 -- 資料: time.CLOCK_TAI

     International Atomic Time(1)

     The system must have a current leap second table in order for this
     to give the correct answer.  PTP or NTP software can maintain a
     leap second table.

     *note 適用: 1c56.：Linux。

     在 3.9 版被加入.

 -- 資料: time.CLOCK_THREAD_CPUTIME_ID

     Thread-specific CPU-time clock.

     *note 適用: 1c56.：Unix。

     在 3.3 版被加入.

 -- 資料: time.CLOCK_UPTIME

     Time whose absolute value is the time the system has been running
     and not suspended, providing accurate uptime measurement, both
     absolute and interval.

     *note 適用: 1c56.：FreeBSD、OpenBSD 5.5 以上。

     在 3.7 版被加入.

 -- 資料: time.CLOCK_UPTIME_RAW

     Clock that increments monotonically, tracking the time since an
     arbitrary point, unaffected by frequency or time adjustments and
     not incremented while the system is asleep.

     *note 適用: 1c56.：macOS 10.12 以上。

     在 3.8 版被加入.

 -- 資料: time.CLOCK_UPTIME_RAW_APPROX

     Like *note CLOCK_UPTIME_RAW: 9e6, but the value is cached by the
     system at context switches and therefore has less accuracy.

     *note 適用: 1c56.：macOS 10.12 以上。

     在 3.13 版被加入.

The following constant is the only parameter that can be sent to *note
clock_settime(): 10f8.

 -- 資料: time.CLOCK_REALTIME

     System-wide real-time clock.  Setting this clock requires
     appropriate privileges.

     *note 適用: 1c56.：Unix。

     在 3.3 版被加入.

   ---------- Footnotes ----------

   (1) 
https://www.nist.gov/pml/time-and-frequency-division/nist-time-frequently-asked-questions-faq#tai


File: python.info,  Node: Timezone Constants,  Prev: Clock ID Constants,  Up: time --- 時間存取與轉換

5.16.3.3 Timezone Constants
...........................

 -- 資料: time.altzone

     The offset of the local DST timezone, in seconds west of UTC, if
     one is defined.  This is negative if the local DST timezone is east
     of UTC (as in Western Europe, including the UK). Only use this if
     ‘daylight’ is nonzero.  See note below.

 -- 資料: time.daylight

     Nonzero if a DST timezone is defined.  See note below.

 -- 資料: time.timezone

     The offset of the local (non-DST) timezone, in seconds west of UTC
     (negative in most of Western Europe, positive in the US, zero in
     the UK). See note below.

 -- 資料: time.tzname

     A tuple of two strings: the first is the name of the local non-DST
     timezone, the second is the name of the local DST timezone.  If no
     DST timezone is defined, the second string should not be used.  See
     note below.

     備註: For the above Timezone constants (*note altzone: 2b3e, *note
     daylight: 2b3f, *note timezone: 2b40, and *note tzname: 2b41.), the
     value is determined by the timezone rules in effect at module load
     time or the last time *note tzset(): 2b34. is called and may be
     incorrect for times in the past.  It is recommended to use the
     *note tm_gmtoff: 2b27. and *note tm_zone: 2b28. results from *note
     localtime(): 1467. to obtain timezone information.

也參考
......

*note datetime: 28. 模組

     More object-oriented interface to dates and times.

*note locale: 7a. 模組

     Internationalization services.  The locale setting affects the
     interpretation of many format specifiers in *note strftime(): 1181.
     and *note strptime(): 139a.

*note calendar: 10. 模組

     General calendar-related functions.  *note timegm(): 23ae. is the
     inverse of *note gmtime(): 1158. from this module.

註解
....


File: python.info,  Node: argparse --- Parser for command-line options arguments and sub-commands,  Next: logging --- Python 的日誌記錄工具,  Prev: time --- 時間存取與轉換,  Up: 通用作業系統服務

5.16.4 ‘argparse’ -- Parser for command-line options, arguments and sub-commands
--------------------------------------------------------------------------------

在 3.2 版被加入.

'原始碼：'Lib/argparse.py(1)

__________________________________________________________________

教學
....

This page contains the API reference information.  For a more gentle
introduction to Python command-line parsing, have a look at the *note
argparse tutorial: 2b44.

The *note argparse: 5. module makes it easy to write user-friendly
command-line interfaces.  The program defines what arguments it
requires, and *note argparse: 5. will figure out how to parse those out
of *note sys.argv: 11fd.  The *note argparse: 5. module also
automatically generates help and usage messages.  The module will also
issue errors when users give the program invalid arguments.

* Menu:

* Core Functionality::
* Quick Links for add_argument(): Quick Links for add_argument.
* 範例: 範例<18>.
* ArgumentParser 物件::
* The add_argument() method: The add_argument method.
* The parse_args() method: The parse_args method.
* Other utilities::
* Upgrading optparse code::
* Exceptions: Exceptions<3>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/argparse.py


File: python.info,  Node: Core Functionality,  Next: Quick Links for add_argument,  Up: argparse --- Parser for command-line options arguments and sub-commands

5.16.4.1 Core Functionality
...........................

The *note argparse: 5. module's support for command-line interfaces is
built around an instance of *note argparse.ArgumentParser: 4de.  It is a
container for argument specifications and has options that apply to the
parser as whole:

     parser = argparse.ArgumentParser(
                         prog='ProgramName',
                         description='What the program does',
                         epilog='Text at the bottom of help')

The *note ArgumentParser.add_argument(): 184. method attaches individual
argument specifications to the parser.  It supports positional
arguments, options that accept values, and on/off flags:

     parser.add_argument('filename')           # positional argument
     parser.add_argument('-c', '--count')      # option that takes a value
     parser.add_argument('-v', '--verbose',
                         action='store_true')  # on/off flag

The *note ArgumentParser.parse_args(): 2b46. method runs the parser and
places the extracted data in a *note argparse.Namespace: 2b47. object:

     args = parser.parse_args()
     print(args.filename, args.count, args.verbose)


File: python.info,  Node: Quick Links for add_argument,  Next: 範例<18>,  Prev: Core Functionality,  Up: argparse --- Parser for command-line options arguments and sub-commands

5.16.4.2 Quick Links for add_argument()
.......................................

名稱                             描述                                                            數值
                                                                                                 
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
                                                                                                 
*note action: 2b49.              Specify how an argument should be handled                       ‘'store'’, ‘'store_const'’, ‘'store_true'’, ‘'append'’, ‘'append_const'’, ‘'count'’, ‘'help'’, ‘'version'’
                                                                                                 
                                                                                                 
*note choices: 2b4a.             Limit values to a specific set of choices                       ‘['foo', 'bar']’, ‘range(1, 10)’, or *note Container: 212c. instance
                                                                                                 
                                                                                                 
*note const: 2b4b.               Store a constant value
                                 
                                                                                                 
*note default: 2b4c.             Default value used when an argument is not provided             Defaults to ‘None’
                                                                                                 
                                                                                                 
*note dest: 2b4d.                Specify the attribute name used in the result namespace
                                 
                                                                                                 
*note help: 2b4e.                Help message for an argument
                                 
                                                                                                 
*note metavar: 2b4f.             Alternate display name for the argument as shown in help
                                 
                                                                                                 
*note nargs: 2b50.               Number of times the argument can be used                        *note int: 23c, ‘'?'’, ‘'*'’, or ‘'+'’
                                                                                                 
                                                                                                 
*note required: 2b51.            Indicate whether an argument is required or optional            ‘True’ 或 ‘False’
                                                                                                 
                                                                                                 
*note type: 2b52.                Automatically convert an argument to the given type             *note int: 23c.、*note float: 2c8.、‘argparse.FileType('w')’ 或可呼叫的函式
                                                                                                 


File: python.info,  Node: 範例<18>,  Next: ArgumentParser 物件,  Prev: Quick Links for add_argument,  Up: argparse --- Parser for command-line options arguments and sub-commands

5.16.4.3 範例
.............

The following code is a Python program that takes a list of integers and
produces either the sum or the max:

     import argparse

     parser = argparse.ArgumentParser(description='Process some integers.')
     parser.add_argument('integers', metavar='N', type=int, nargs='+',
                         help='an integer for the accumulator')
     parser.add_argument('--sum', dest='accumulate', action='store_const',
                         const=sum, default=max,
                         help='sum the integers (default: find the max)')

     args = parser.parse_args()
     print(args.accumulate(args.integers))

Assuming the above Python code is saved into a file called ‘prog.py’, it
can be run at the command line and it provides useful help messages:

     $ python prog.py -h
     usage: prog.py [-h] [--sum] N [N ...]

     Process some integers.

     positional arguments:
      N           an integer for the accumulator

     options:
      -h, --help  show this help message and exit
      --sum       sum the integers (default: find the max)

When run with the appropriate arguments, it prints either the sum or the
max of the command-line integers:

     $ python prog.py 1 2 3 4
     4

     $ python prog.py 1 2 3 4 --sum
     10

If invalid arguments are passed in, an error will be displayed:

     $ python prog.py a b c
     usage: prog.py [-h] [--sum] N [N ...]
     prog.py: error: argument N: invalid int value: 'a'

The following sections walk you through this example.

* Menu:

* 建立一個剖析器::
* 增加引數::
* 剖析引數::


File: python.info,  Node: 建立一個剖析器,  Next: 增加引數,  Up: 範例<18>

5.16.4.4 建立一個剖析器
.......................

The first step in using the *note argparse: 5. is creating an *note
ArgumentParser: 4de. object:

     >>> parser = argparse.ArgumentParser(description='Process some integers.')

The *note ArgumentParser: 4de. object will hold all the information
necessary to parse the command line into Python data types.


File: python.info,  Node: 增加引數,  Next: 剖析引數,  Prev: 建立一個剖析器,  Up: 範例<18>

5.16.4.5 增加引數
.................

Filling an *note ArgumentParser: 4de. with information about program
arguments is done by making calls to the *note add_argument(): 184.
method.  Generally, these calls tell the *note ArgumentParser: 4de. how
to take the strings on the command line and turn them into objects.
This information is stored and used when *note parse_args(): 2b46. is
called.  For example:

     >>> parser.add_argument('integers', metavar='N', type=int, nargs='+',
     ...                     help='an integer for the accumulator')
     >>> parser.add_argument('--sum', dest='accumulate', action='store_const',
     ...                     const=sum, default=max,
     ...                     help='sum the integers (default: find the max)')

Later, calling *note parse_args(): 2b46. will return an object with two
attributes, ‘integers’ and ‘accumulate’.  The ‘integers’ attribute will
be a list of one or more integers, and the ‘accumulate’ attribute will
be either the *note sum(): 411. function, if ‘--sum’ was specified at
the command line, or the *note max(): ead. function if it was not.


File: python.info,  Node: 剖析引數,  Prev: 增加引數,  Up: 範例<18>

5.16.4.6 剖析引數
.................

*note ArgumentParser: 4de. parses arguments through the *note
parse_args(): 2b46. method.  This will inspect the command line, convert
each argument to the appropriate type and then invoke the appropriate
action.  In most cases, this means a simple *note Namespace: 2b47.
object will be built up from attributes parsed out of the command line:

     >>> parser.parse_args(['--sum', '7', '-1', '42'])
     Namespace(accumulate=<built-in function sum>, integers=[7, -1, 42])

In a script, *note parse_args(): 2b46. will typically be called with no
arguments, and the *note ArgumentParser: 4de. will automatically
determine the command-line arguments from *note sys.argv: 11fd.


File: python.info,  Node: ArgumentParser 物件,  Next: The add_argument method,  Prev: 範例<18>,  Up: argparse --- Parser for command-line options arguments and sub-commands

5.16.4.7 ArgumentParser 物件
............................

 -- 類別: argparse.ArgumentParser (prog=None, usage=None,
          description=None, epilog=None, parents=[],
          formatter_class=argparse.HelpFormatter, prefix_chars='-',
          fromfile_prefix_chars=None, argument_default=None,
          conflict_handler='error', add_help=True, allow_abbrev=True,
          exit_on_error=True)

     Create a new *note ArgumentParser: 4de. object.  All parameters
     should be passed as keyword arguments.  Each parameter has its own
     more detailed description below, but in short they are:

        * *note prog: 2b58. - The name of the program (default:
          ‘os.path.basename(sys.argv[0])’)

        * *note usage: 2b59. - The string describing the program usage
          (default: generated from arguments added to parser)

        * *note description: 2b5a. - Text to display before the argument
          help (by default, no text)

        * *note epilog: 2b5b. - Text to display after the argument help
          (by default, no text)

        * *note parents: 2b5c. - A list of *note ArgumentParser: 4de.
          objects whose arguments should also be included

        * *note formatter_class: 2b5d. - A class for customizing the
          help output

        * *note prefix_chars: 2b5e. - The set of characters that prefix
          optional arguments (default: '-')

        * *note fromfile_prefix_chars: 2b5f. - The set of characters
          that prefix files from which additional arguments should be
          read (default: ‘None’)

        * *note argument_default: 2b60. - The global default value for
          arguments (default: ‘None’)

        * *note conflict_handler: 2b61. - The strategy for resolving
          conflicting optionals (usually unnecessary)

        * *note add_help: 2b62. - Add a ‘-h/--help’ option to the parser
          (default: ‘True’)

        * *note allow_abbrev: d66. - Allows long options to be
          abbreviated if the abbreviation is unambiguous.  (default:
          ‘True’)

        * *note exit_on_error: 2b63. - Determines whether or not
          ArgumentParser exits with error info when an error occurs.
          (default: ‘True’)

     在 3.5 版的變更: 新增 'allow_abbrev' 參數。

     在 3.8 版的變更: In previous versions, 'allow_abbrev' also disabled
     grouping of short flags such as ‘-vv’ to mean ‘-v -v’.

     在 3.9 版的變更: 新增 'exit_on_error' 參數。

The following sections describe how each of these are used.

* Menu:

* prog::
* usage::
* 描述::
* epilog::
* parents::
* formatter_class::
* prefix_chars::
* fromfile_prefix_chars::
* argument_default::
* allow_abbrev::
* conflict_handler::
* add_help::
* exit_on_error::


File: python.info,  Node: prog,  Next: usage,  Up: ArgumentParser 物件

5.16.4.8 prog
.............

By default, *note ArgumentParser: 4de. objects use ‘sys.argv[0]’ to
determine how to display the name of the program in help messages.  This
default is almost always desirable because it will make the help
messages match how the program was invoked on the command line.  For
example, consider a file named ‘myprogram.py’ with the following code:

     import argparse
     parser = argparse.ArgumentParser()
     parser.add_argument('--foo', help='foo help')
     args = parser.parse_args()

The help for this program will display ‘myprogram.py’ as the program
name (regardless of where the program was invoked from):

     $ python myprogram.py --help
     usage: myprogram.py [-h] [--foo FOO]

     options:
      -h, --help  show this help message and exit
      --foo FOO   foo help
     $ cd ..
     $ python subdir/myprogram.py --help
     usage: myprogram.py [-h] [--foo FOO]

     options:
      -h, --help  show this help message and exit
      --foo FOO   foo help

To change this default behavior, another value can be supplied using the
‘prog=’ argument to *note ArgumentParser: 4de.:

     >>> parser = argparse.ArgumentParser(prog='myprogram')
     >>> parser.print_help()
     usage: myprogram [-h]

     options:
      -h, --help  show this help message and exit

Note that the program name, whether determined from ‘sys.argv[0]’ or
from the ‘prog=’ argument, is available to help messages using the
‘%(prog)s’ format specifier.

     >>> parser = argparse.ArgumentParser(prog='myprogram')
     >>> parser.add_argument('--foo', help='foo of the %(prog)s program')
     >>> parser.print_help()
     usage: myprogram [-h] [--foo FOO]

     options:
      -h, --help  show this help message and exit
      --foo FOO   foo of the myprogram program


File: python.info,  Node: usage,  Next: 描述,  Prev: prog,  Up: ArgumentParser 物件

5.16.4.9 usage
..............

By default, *note ArgumentParser: 4de. calculates the usage message from
the arguments it contains:

     >>> parser = argparse.ArgumentParser(prog='PROG')
     >>> parser.add_argument('--foo', nargs='?', help='foo help')
     >>> parser.add_argument('bar', nargs='+', help='bar help')
     >>> parser.print_help()
     usage: PROG [-h] [--foo [FOO]] bar [bar ...]

     positional arguments:
      bar          bar help

     options:
      -h, --help   show this help message and exit
      --foo [FOO]  foo help

The default message can be overridden with the ‘usage=’ keyword
argument:

     >>> parser = argparse.ArgumentParser(prog='PROG', usage='%(prog)s [options]')
     >>> parser.add_argument('--foo', nargs='?', help='foo help')
     >>> parser.add_argument('bar', nargs='+', help='bar help')
     >>> parser.print_help()
     usage: PROG [options]

     positional arguments:
      bar          bar help

     options:
      -h, --help   show this help message and exit
      --foo [FOO]  foo help

The ‘%(prog)s’ format specifier is available to fill in the program name
in your usage messages.


File: python.info,  Node: 描述,  Next: epilog,  Prev: usage,  Up: ArgumentParser 物件

5.16.4.10 描述
..............

Most calls to the *note ArgumentParser: 4de. constructor will use the
‘description=’ keyword argument.  This argument gives a brief
description of what the program does and how it works.  In help
messages, the description is displayed between the command-line usage
string and the help messages for the various arguments:

     >>> parser = argparse.ArgumentParser(description='A foo that bars')
     >>> parser.print_help()
     usage: argparse.py [-h]

     A foo that bars

     options:
      -h, --help  show this help message and exit

By default, the description will be line-wrapped so that it fits within
the given space.  To change this behavior, see the *note
formatter_class: 2b5d. argument.


File: python.info,  Node: epilog,  Next: parents,  Prev: 描述,  Up: ArgumentParser 物件

5.16.4.11 epilog
................

Some programs like to display additional description of the program
after the description of the arguments.  Such text can be specified
using the ‘epilog=’ argument to *note ArgumentParser: 4de.:

     >>> parser = argparse.ArgumentParser(
     ...     description='A foo that bars',
     ...     epilog="And that's how you'd foo a bar")
     >>> parser.print_help()
     usage: argparse.py [-h]

     A foo that bars

     options:
      -h, --help  show this help message and exit

     And that's how you'd foo a bar

As with the *note description: 2b5a. argument, the ‘epilog=’ text is by
default line-wrapped, but this behavior can be adjusted with the *note
formatter_class: 2b5d. argument to *note ArgumentParser: 4de.


File: python.info,  Node: parents,  Next: formatter_class,  Prev: epilog,  Up: ArgumentParser 物件

5.16.4.12 parents
.................

Sometimes, several parsers share a common set of arguments.  Rather than
repeating the definitions of these arguments, a single parser with all
the shared arguments and passed to ‘parents=’ argument to *note
ArgumentParser: 4de. can be used.  The ‘parents=’ argument takes a list
of *note ArgumentParser: 4de. objects, collects all the positional and
optional actions from them, and adds these actions to the *note
ArgumentParser: 4de. object being constructed:

     >>> parent_parser = argparse.ArgumentParser(add_help=False)
     >>> parent_parser.add_argument('--parent', type=int)

     >>> foo_parser = argparse.ArgumentParser(parents=[parent_parser])
     >>> foo_parser.add_argument('foo')
     >>> foo_parser.parse_args(['--parent', '2', 'XXX'])
     Namespace(foo='XXX', parent=2)

     >>> bar_parser = argparse.ArgumentParser(parents=[parent_parser])
     >>> bar_parser.add_argument('--bar')
     >>> bar_parser.parse_args(['--bar', 'YYY'])
     Namespace(bar='YYY', parent=None)

Note that most parent parsers will specify ‘add_help=False’.  Otherwise,
the *note ArgumentParser: 4de. will see two ‘-h/--help’ options (one in
the parent and one in the child) and raise an error.

     備註: You must fully initialize the parsers before passing them via
     ‘parents=’.  If you change the parent parsers after the child
     parser, those changes will not be reflected in the child.


File: python.info,  Node: formatter_class,  Next: prefix_chars,  Prev: parents,  Up: ArgumentParser 物件

5.16.4.13 formatter_class
.........................

*note ArgumentParser: 4de. objects allow the help formatting to be
customized by specifying an alternate formatting class.  Currently,
there are four such classes:

 -- 類別: argparse.RawDescriptionHelpFormatter
 -- 類別: argparse.RawTextHelpFormatter
 -- 類別: argparse.ArgumentDefaultsHelpFormatter
 -- 類別: argparse.MetavarTypeHelpFormatter

*note RawDescriptionHelpFormatter: 2b67. and *note RawTextHelpFormatter:
2b68. give more control over how textual descriptions are displayed.  By
default, *note ArgumentParser: 4de. objects line-wrap the *note
description: 2b5a. and *note epilog: 2b5b. texts in command-line help
messages:

     >>> parser = argparse.ArgumentParser(
     ...     prog='PROG',
     ...     description='''this description
     ...         was indented weird
     ...             but that is okay''',
     ...     epilog='''
     ...             likewise for this epilog whose whitespace will
     ...         be cleaned up and whose words will be wrapped
     ...         across a couple lines''')
     >>> parser.print_help()
     usage: PROG [-h]

     this description was indented weird but that is okay

     options:
      -h, --help  show this help message and exit

     likewise for this epilog whose whitespace will be cleaned up and whose words
     will be wrapped across a couple lines

Passing *note RawDescriptionHelpFormatter: 2b67. as ‘formatter_class=’
indicates that *note description: 2b5a. and *note epilog: 2b5b. are
already correctly formatted and should not be line-wrapped:

     >>> parser = argparse.ArgumentParser(
     ...     prog='PROG',
     ...     formatter_class=argparse.RawDescriptionHelpFormatter,
     ...     description=textwrap.dedent('''\
     ...         Please do not mess up this text!
     ...         --------------------------------
     ...             I have indented it
     ...             exactly the way
     ...             I want it
     ...         '''))
     >>> parser.print_help()
     usage: PROG [-h]

     Please do not mess up this text!
     --------------------------------
        I have indented it
        exactly the way
        I want it

     options:
      -h, --help  show this help message and exit

*note RawTextHelpFormatter: 2b68. maintains whitespace for all sorts of
help text, including argument descriptions.  However, multiple new lines
are replaced with one.  If you wish to preserve multiple blank lines,
add spaces between the newlines.

*note ArgumentDefaultsHelpFormatter: 179e. automatically adds
information about default values to each of the argument help messages:

     >>> parser = argparse.ArgumentParser(
     ...     prog='PROG',
     ...     formatter_class=argparse.ArgumentDefaultsHelpFormatter)
     >>> parser.add_argument('--foo', type=int, default=42, help='FOO!')
     >>> parser.add_argument('bar', nargs='*', default=[1, 2, 3], help='BAR!')
     >>> parser.print_help()
     usage: PROG [-h] [--foo FOO] [bar ...]

     positional arguments:
      bar         BAR! (default: [1, 2, 3])

     options:
      -h, --help  show this help message and exit
      --foo FOO   FOO! (default: 42)

*note MetavarTypeHelpFormatter: 2b69. uses the name of the *note type:
2b6a. argument for each argument as the display name for its values
(rather than using the *note dest: 2b4d. as the regular formatter does):

     >>> parser = argparse.ArgumentParser(
     ...     prog='PROG',
     ...     formatter_class=argparse.MetavarTypeHelpFormatter)
     >>> parser.add_argument('--foo', type=int)
     >>> parser.add_argument('bar', type=float)
     >>> parser.print_help()
     usage: PROG [-h] [--foo int] float

     positional arguments:
       float

     options:
       -h, --help  show this help message and exit
       --foo int


File: python.info,  Node: prefix_chars,  Next: fromfile_prefix_chars,  Prev: formatter_class,  Up: ArgumentParser 物件

5.16.4.14 prefix_chars
......................

Most command-line options will use ‘-’ as the prefix, e.g.  ‘-f/--foo’.
Parsers that need to support different or additional prefix characters,
e.g.  for options like ‘+f’ or ‘/foo’, may specify them using the
‘prefix_chars=’ argument to the ArgumentParser constructor:

     >>> parser = argparse.ArgumentParser(prog='PROG', prefix_chars='-+')
     >>> parser.add_argument('+f')
     >>> parser.add_argument('++bar')
     >>> parser.parse_args('+f X ++bar Y'.split())
     Namespace(bar='Y', f='X')

The ‘prefix_chars=’ argument defaults to ‘'-'’.  Supplying a set of
characters that does not include ‘-’ will cause ‘-f/--foo’ options to be
disallowed.


File: python.info,  Node: fromfile_prefix_chars,  Next: argument_default,  Prev: prefix_chars,  Up: ArgumentParser 物件

5.16.4.15 fromfile_prefix_chars
...............................

Sometimes, when dealing with a particularly long argument list, it may
make sense to keep the list of arguments in a file rather than typing it
out at the command line.  If the ‘fromfile_prefix_chars=’ argument is
given to the *note ArgumentParser: 4de. constructor, then arguments that
start with any of the specified characters will be treated as files, and
will be replaced by the arguments they contain.  For example:

     >>> with open('args.txt', 'w', encoding=sys.getfilesystemencoding()) as fp:
     ...     fp.write('-f\nbar')
     ...
     >>> parser = argparse.ArgumentParser(fromfile_prefix_chars='@')
     >>> parser.add_argument('-f')
     >>> parser.parse_args(['-f', 'foo', '@args.txt'])
     Namespace(f='bar')

Arguments read from a file must by default be one per line (but see also
*note convert_arg_line_to_args(): 2b6b.) and are treated as if they were
in the same place as the original file referencing argument on the
command line.  So in the example above, the expression ‘['-f', 'foo',
'@args.txt']’ is considered equivalent to the expression ‘['-f', 'foo',
'-f', 'bar']’.

*note ArgumentParser: 4de. uses *note filesystem encoding and error
handler: 4e0. to read the file containing arguments.

The ‘fromfile_prefix_chars=’ argument defaults to ‘None’, meaning that
arguments will never be treated as file references.

在 3.12 版的變更: *note ArgumentParser: 4de. changed encoding and errors
to read arguments files from default (e.g.  *note
locale.getpreferredencoding(False): 4df. and ‘"strict"’) to *note
filesystem encoding and error handler: 4e0.  Arguments file should be
encoded in UTF-8 instead of ANSI Codepage on Windows.


File: python.info,  Node: argument_default,  Next: allow_abbrev,  Prev: fromfile_prefix_chars,  Up: ArgumentParser 物件

5.16.4.16 argument_default
..........................

Generally, argument defaults are specified either by passing a default
to *note add_argument(): 184. or by calling the *note set_defaults():
2b6c. methods with a specific set of name-value pairs.  Sometimes
however, it may be useful to specify a single parser-wide default for
arguments.  This can be accomplished by passing the ‘argument_default=’
keyword argument to *note ArgumentParser: 4de.  For example, to globally
suppress attribute creation on *note parse_args(): 2b46. calls, we
supply ‘argument_default=SUPPRESS’:

     >>> parser = argparse.ArgumentParser(argument_default=argparse.SUPPRESS)
     >>> parser.add_argument('--foo')
     >>> parser.add_argument('bar', nargs='?')
     >>> parser.parse_args(['--foo', '1', 'BAR'])
     Namespace(bar='BAR', foo='1')
     >>> parser.parse_args([])
     Namespace()


File: python.info,  Node: allow_abbrev,  Next: conflict_handler,  Prev: argument_default,  Up: ArgumentParser 物件

5.16.4.17 allow_abbrev
......................

Normally, when you pass an argument list to the *note parse_args():
2b46. method of an *note ArgumentParser: 4de, it *note recognizes
abbreviations: d65. of long options.

This feature can be disabled by setting ‘allow_abbrev’ to ‘False’:

     >>> parser = argparse.ArgumentParser(prog='PROG', allow_abbrev=False)
     >>> parser.add_argument('--foobar', action='store_true')
     >>> parser.add_argument('--foonley', action='store_false')
     >>> parser.parse_args(['--foon'])
     usage: PROG [-h] [--foobar] [--foonley]
     PROG: error: unrecognized arguments: --foon

在 3.5 版被加入.


File: python.info,  Node: conflict_handler,  Next: add_help,  Prev: allow_abbrev,  Up: ArgumentParser 物件

5.16.4.18 conflict_handler
..........................

*note ArgumentParser: 4de. objects do not allow two actions with the
same option string.  By default, *note ArgumentParser: 4de. objects
raise an exception if an attempt is made to create an argument with an
option string that is already in use:

     >>> parser = argparse.ArgumentParser(prog='PROG')
     >>> parser.add_argument('-f', '--foo', help='old foo help')
     >>> parser.add_argument('--foo', help='new foo help')
     Traceback (most recent call last):
      ..
     ArgumentError: argument --foo: conflicting option string(s): --foo

Sometimes (e.g.  when using *note parents: 2b5c.) it may be useful to
simply override any older arguments with the same option string.  To get
this behavior, the value ‘'resolve'’ can be supplied to the
‘conflict_handler=’ argument of *note ArgumentParser: 4de.:

     >>> parser = argparse.ArgumentParser(prog='PROG', conflict_handler='resolve')
     >>> parser.add_argument('-f', '--foo', help='old foo help')
     >>> parser.add_argument('--foo', help='new foo help')
     >>> parser.print_help()
     usage: PROG [-h] [-f FOO] [--foo FOO]

     options:
      -h, --help  show this help message and exit
      -f FOO      old foo help
      --foo FOO   new foo help

Note that *note ArgumentParser: 4de. objects only remove an action if
all of its option strings are overridden.  So, in the example above, the
old ‘-f/--foo’ action is retained as the ‘-f’ action, because only the
‘--foo’ option string was overridden.


File: python.info,  Node: add_help,  Next: exit_on_error,  Prev: conflict_handler,  Up: ArgumentParser 物件

5.16.4.19 add_help
..................

By default, ArgumentParser objects add an option which simply displays
the parser's help message.  For example, consider a file named
‘myprogram.py’ containing the following code:

     import argparse
     parser = argparse.ArgumentParser()
     parser.add_argument('--foo', help='foo help')
     args = parser.parse_args()

If ‘-h’ or ‘--help’ is supplied at the command line, the ArgumentParser
help will be printed:

     $ python myprogram.py --help
     usage: myprogram.py [-h] [--foo FOO]

     options:
      -h, --help  show this help message and exit
      --foo FOO   foo help

Occasionally, it may be useful to disable the addition of this help
option.  This can be achieved by passing ‘False’ as the ‘add_help=’
argument to *note ArgumentParser: 4de.:

     >>> parser = argparse.ArgumentParser(prog='PROG', add_help=False)
     >>> parser.add_argument('--foo', help='foo help')
     >>> parser.print_help()
     usage: PROG [--foo FOO]

     options:
      --foo FOO  foo help

The help option is typically ‘-h/--help’.  The exception to this is if
the ‘prefix_chars=’ is specified and does not include ‘-’, in which case
‘-h’ and ‘--help’ are not valid options.  In this case, the first
character in ‘prefix_chars’ is used to prefix the help options:

     >>> parser = argparse.ArgumentParser(prog='PROG', prefix_chars='+/')
     >>> parser.print_help()
     usage: PROG [+h]

     options:
       +h, ++help  show this help message and exit


File: python.info,  Node: exit_on_error,  Prev: add_help,  Up: ArgumentParser 物件

5.16.4.20 exit_on_error
.......................

Normally, when you pass an invalid argument list to the *note
parse_args(): 2b46. method of an *note ArgumentParser: 4de, it will exit
with error info.

If the user would like to catch errors manually, the feature can be
enabled by setting ‘exit_on_error’ to ‘False’:

     >>> parser = argparse.ArgumentParser(exit_on_error=False)
     >>> parser.add_argument('--integers', type=int)
     _StoreAction(option_strings=['--integers'], dest='integers', nargs=None, const=None, default=None, type=<class 'int'>, choices=None, help=None, metavar=None)
     >>> try:
     ...     parser.parse_args('--integers a'.split())
     ... except argparse.ArgumentError:
     ...     print('Catching an argumentError')
     ...
     Catching an argumentError

在 3.9 版被加入.


File: python.info,  Node: The add_argument method,  Next: The parse_args method,  Prev: ArgumentParser 物件,  Up: argparse --- Parser for command-line options arguments and sub-commands

5.16.4.21 The add_argument() method
...................................

 -- 方法: ArgumentParser.add_argument (name or flags...[, action][,
          nargs][, const][, default][, type][, choices][, required][,
          help][, metavar][, dest][, deprecated])

     Define how a single command-line argument should be parsed.  Each
     parameter has its own more detailed description below, but in short
     they are:

        * *note name or flags: 2b6f. - Either a name or a list of option
          strings, e.g.  ‘foo’ or ‘-f, --foo’.

        * *note action: 2b49. - The basic type of action to be taken
          when this argument is encountered at the command line.

        * *note nargs: 2b50. - The number of command-line arguments that
          should be consumed.

        * *note const: 2b4b. - A constant value required by some *note
          action: 2b49. and *note nargs: 2b50. selections.

        * *note default: 2b4c. - The value produced if the argument is
          absent from the command line and if it is absent from the
          namespace object.

        * *note type: 2b6a. - The type to which the command-line
          argument should be converted.

        * *note choices: 2b4a. - A sequence of the allowable values for
          the argument.

        * *note required: 2b51. - Whether or not the command-line option
          may be omitted (optionals only).

        * *note help: 2b4e. - A brief description of what the argument
          does.

        * *note metavar: 2b4f. - A name for the argument in usage
          messages.

        * *note dest: 2b4d. - The name of the attribute to be added to
          the object returned by *note parse_args(): 2b46.

        * *note deprecated: 2b70. - Whether or not use of the argument
          is deprecated.

The following sections describe how each of these are used.

* Menu:

* name or flags::
* action::
* nargs::
* const::
* default::
* type::
* choices::
* required::
* 幫助::
* metavar::
* dest::
* deprecated::
* Action classes::


File: python.info,  Node: name or flags,  Next: action,  Up: The add_argument method

5.16.4.22 name or flags
.......................

The *note add_argument(): 184. method must know whether an optional
argument, like ‘-f’ or ‘--foo’, or a positional argument, like a list of
filenames, is expected.  The first arguments passed to *note
add_argument(): 184. must therefore be either a series of flags, or a
simple argument name.

For example, an optional argument could be created like:

     >>> parser.add_argument('-f', '--foo')

while a positional argument could be created like:

     >>> parser.add_argument('bar')

When *note parse_args(): 2b46. is called, optional arguments will be
identified by the ‘-’ prefix, and the remaining arguments will be
assumed to be positional:

     >>> parser = argparse.ArgumentParser(prog='PROG')
     >>> parser.add_argument('-f', '--foo')
     >>> parser.add_argument('bar')
     >>> parser.parse_args(['BAR'])
     Namespace(bar='BAR', foo=None)
     >>> parser.parse_args(['BAR', '--foo', 'FOO'])
     Namespace(bar='BAR', foo='FOO')
     >>> parser.parse_args(['--foo', 'FOO'])
     usage: PROG [-h] [-f FOO] bar
     PROG: error: the following arguments are required: bar


File: python.info,  Node: action,  Next: nargs,  Prev: name or flags,  Up: The add_argument method

5.16.4.23 action
................

*note ArgumentParser: 4de. objects associate command-line arguments with
actions.  These actions can do just about anything with the command-line
arguments associated with them, though most actions simply add an
attribute to the object returned by *note parse_args(): 2b46.  The
‘action’ keyword argument specifies how the command-line arguments
should be handled.  The supplied actions are:

   * ‘'store'’ - This just stores the argument's value.  This is the
     default action.  For example:

          >>> parser = argparse.ArgumentParser()
          >>> parser.add_argument('--foo')
          >>> parser.parse_args('--foo 1'.split())
          Namespace(foo='1')

   * ‘'store_const'’ - This stores the value specified by the *note
     const: 2b4b. keyword argument; note that the *note const: 2b4b.
     keyword argument defaults to ‘None’.  The ‘'store_const'’ action is
     most commonly used with optional arguments that specify some sort
     of flag.  For example:

          >>> parser = argparse.ArgumentParser()
          >>> parser.add_argument('--foo', action='store_const', const=42)
          >>> parser.parse_args(['--foo'])
          Namespace(foo=42)

   * ‘'store_true'’ and ‘'store_false'’ - These are special cases of
     ‘'store_const'’ used for storing the values ‘True’ and ‘False’
     respectively.  In addition, they create default values of ‘False’
     and ‘True’ respectively.  For example:

          >>> parser = argparse.ArgumentParser()
          >>> parser.add_argument('--foo', action='store_true')
          >>> parser.add_argument('--bar', action='store_false')
          >>> parser.add_argument('--baz', action='store_false')
          >>> parser.parse_args('--foo --bar'.split())
          Namespace(foo=True, bar=False, baz=True)

   * ‘'append'’ - This stores a list, and appends each argument value to
     the list.  It is useful to allow an option to be specified multiple
     times.  If the default value is non-empty, the default elements
     will be present in the parsed value for the option, with any values
     from the command line appended after those default values.  Example
     usage:

          >>> parser = argparse.ArgumentParser()
          >>> parser.add_argument('--foo', action='append')
          >>> parser.parse_args('--foo 1 --foo 2'.split())
          Namespace(foo=['1', '2'])

   * ‘'append_const'’ - This stores a list, and appends the value
     specified by the *note const: 2b4b. keyword argument to the list;
     note that the *note const: 2b4b. keyword argument defaults to
     ‘None’.  The ‘'append_const'’ action is typically useful when
     multiple arguments need to store constants to the same list.  For
     example:

          >>> parser = argparse.ArgumentParser()
          >>> parser.add_argument('--str', dest='types', action='append_const', const=str)
          >>> parser.add_argument('--int', dest='types', action='append_const', const=int)
          >>> parser.parse_args('--str --int'.split())
          Namespace(types=[<class 'str'>, <class 'int'>])

   * ‘'count'’ - This counts the number of times a keyword argument
     occurs.  For example, this is useful for increasing verbosity
     levels:

          >>> parser = argparse.ArgumentParser()
          >>> parser.add_argument('--verbose', '-v', action='count', default=0)
          >>> parser.parse_args(['-vvv'])
          Namespace(verbose=3)

     Note, the 'default' will be ‘None’ unless explicitly set to '0'.

   * ‘'help'’ - This prints a complete help message for all the options
     in the current parser and then exits.  By default a help action is
     automatically added to the parser.  See *note ArgumentParser: 4de.
     for details of how the output is created.

   * ‘'version'’ - This expects a ‘version=’ keyword argument in the
     *note add_argument(): 184. call, and prints version information and
     exits when invoked:

          >>> import argparse
          >>> parser = argparse.ArgumentParser(prog='PROG')
          >>> parser.add_argument('--version', action='version', version='%(prog)s 2.0')
          >>> parser.parse_args(['--version'])
          PROG 2.0

   * ‘'extend'’ - This stores a list, and extends each argument value to
     the list.  Example usage:

          >>> parser = argparse.ArgumentParser()
          >>> parser.add_argument("--foo", action="extend", nargs="+", type=str)
          >>> parser.parse_args(["--foo", "f1", "--foo", "f2", "f3", "f4"])
          Namespace(foo=['f1', 'f2', 'f3', 'f4'])

     在 3.8 版被加入.

You may also specify an arbitrary action by passing an Action subclass
or other object that implements the same interface.  The
‘BooleanOptionalAction’ is available in ‘argparse’ and adds support for
boolean actions such as ‘--foo’ and ‘--no-foo’:

     >>> import argparse
     >>> parser = argparse.ArgumentParser()
     >>> parser.add_argument('--foo', action=argparse.BooleanOptionalAction)
     >>> parser.parse_args(['--no-foo'])
     Namespace(foo=False)

在 3.9 版被加入.

The recommended way to create a custom action is to extend *note Action:
1704, overriding the ‘__call__’ method and optionally the ‘__init__’ and
‘format_usage’ methods.

An example of a custom action:

     >>> class FooAction(argparse.Action):
     ...     def __init__(self, option_strings, dest, nargs=None, **kwargs):
     ...         if nargs is not None:
     ...             raise ValueError("nargs not allowed")
     ...         super().__init__(option_strings, dest, **kwargs)
     ...     def __call__(self, parser, namespace, values, option_string=None):
     ...         print('%r %r %r' % (namespace, values, option_string))
     ...         setattr(namespace, self.dest, values)
     ...
     >>> parser = argparse.ArgumentParser()
     >>> parser.add_argument('--foo', action=FooAction)
     >>> parser.add_argument('bar', action=FooAction)
     >>> args = parser.parse_args('1 --foo 2'.split())
     Namespace(bar=None, foo=None) '1' None
     Namespace(bar='1', foo=None) '2' '--foo'
     >>> args
     Namespace(bar='1', foo='2')

For more details, see *note Action: 1704.


File: python.info,  Node: nargs,  Next: const,  Prev: action,  Up: The add_argument method

5.16.4.24 nargs
...............

ArgumentParser objects usually associate a single command-line argument
with a single action to be taken.  The ‘nargs’ keyword argument
associates a different number of command-line arguments with a single
action.  See also *note 指定不明確的引數: 2b74.  The supported values
are:

   * ‘N’ (an integer).  ‘N’ arguments from the command line will be
     gathered together into a list.  For example:

          >>> parser = argparse.ArgumentParser()
          >>> parser.add_argument('--foo', nargs=2)
          >>> parser.add_argument('bar', nargs=1)
          >>> parser.parse_args('c --foo a b'.split())
          Namespace(bar=['c'], foo=['a', 'b'])

     Note that ‘nargs=1’ produces a list of one item.  This is different
     from the default, in which the item is produced by itself.

   * ‘'?'’.  One argument will be consumed from the command line if
     possible, and produced as a single item.  If no command-line
     argument is present, the value from *note default: 2b4c. will be
     produced.  Note that for optional arguments, there is an additional
     case - the option string is present but not followed by a
     command-line argument.  In this case the value from *note const:
     2b4b. will be produced.  Some examples to illustrate this:

          >>> parser = argparse.ArgumentParser()
          >>> parser.add_argument('--foo', nargs='?', const='c', default='d')
          >>> parser.add_argument('bar', nargs='?', default='d')
          >>> parser.parse_args(['XX', '--foo', 'YY'])
          Namespace(bar='XX', foo='YY')
          >>> parser.parse_args(['XX', '--foo'])
          Namespace(bar='XX', foo='c')
          >>> parser.parse_args([])
          Namespace(bar='d', foo='d')

     One of the more common uses of ‘nargs='?'’ is to allow optional
     input and output files:

          >>> parser = argparse.ArgumentParser()
          >>> parser.add_argument('infile', nargs='?', type=argparse.FileType('r'),
          ...                     default=sys.stdin)
          >>> parser.add_argument('outfile', nargs='?', type=argparse.FileType('w'),
          ...                     default=sys.stdout)
          >>> parser.parse_args(['input.txt', 'output.txt'])
          Namespace(infile=<_io.TextIOWrapper name='input.txt' encoding='UTF-8'>,
                    outfile=<_io.TextIOWrapper name='output.txt' encoding='UTF-8'>)
          >>> parser.parse_args([])
          Namespace(infile=<_io.TextIOWrapper name='<stdin>' encoding='UTF-8'>,
                    outfile=<_io.TextIOWrapper name='<stdout>' encoding='UTF-8'>)

   * ‘'*'’.  All command-line arguments present are gathered into a
     list.  Note that it generally doesn't make much sense to have more
     than one positional argument with ‘nargs='*'’, but multiple
     optional arguments with ‘nargs='*'’ is possible.  For example:

          >>> parser = argparse.ArgumentParser()
          >>> parser.add_argument('--foo', nargs='*')
          >>> parser.add_argument('--bar', nargs='*')
          >>> parser.add_argument('baz', nargs='*')
          >>> parser.parse_args('a b --foo x y --bar 1 2'.split())
          Namespace(bar=['1', '2'], baz=['a', 'b'], foo=['x', 'y'])

   * ‘'+'’.  Just like ‘'*'’, all command-line args present are gathered
     into a list.  Additionally, an error message will be generated if
     there wasn't at least one command-line argument present.  For
     example:

          >>> parser = argparse.ArgumentParser(prog='PROG')
          >>> parser.add_argument('foo', nargs='+')
          >>> parser.parse_args(['a', 'b'])
          Namespace(foo=['a', 'b'])
          >>> parser.parse_args([])
          usage: PROG [-h] foo [foo ...]
          PROG: error: the following arguments are required: foo

If the ‘nargs’ keyword argument is not provided, the number of arguments
consumed is determined by the *note action: 2b49.  Generally this means
a single command-line argument will be consumed and a single item (not a
list) will be produced.


File: python.info,  Node: const,  Next: default,  Prev: nargs,  Up: The add_argument method

5.16.4.25 const
...............

The ‘const’ argument of *note add_argument(): 184. is used to hold
constant values that are not read from the command line but are required
for the various *note ArgumentParser: 4de. actions.  The two most common
uses of it are:

   * When *note add_argument(): 184. is called with
     ‘action='store_const'’ or ‘action='append_const'’.  These actions
     add the ‘const’ value to one of the attributes of the object
     returned by *note parse_args(): 2b46.  See the *note action: 2b49.
     description for examples.  If ‘const’ is not provided to *note
     add_argument(): 184, it will receive a default value of ‘None’.

   * When *note add_argument(): 184. is called with option strings (like
     ‘-f’ or ‘--foo’) and ‘nargs='?'’.  This creates an optional
     argument that can be followed by zero or one command-line
     arguments.  When parsing the command line, if the option string is
     encountered with no command-line argument following it, the value
     of ‘const’ will be assumed to be ‘None’ instead.  See the *note
     nargs: 2b50. description for examples.

在 3.11 版的變更: ‘const=None’ by default, including when
‘action='append_const'’ or ‘action='store_const'’.


File: python.info,  Node: default,  Next: type,  Prev: const,  Up: The add_argument method

5.16.4.26 default
.................

All optional arguments and some positional arguments may be omitted at
the command line.  The ‘default’ keyword argument of *note
add_argument(): 184, whose value defaults to ‘None’, specifies what
value should be used if the command-line argument is not present.  For
optional arguments, the ‘default’ value is used when the option string
was not present at the command line:

     >>> parser = argparse.ArgumentParser()
     >>> parser.add_argument('--foo', default=42)
     >>> parser.parse_args(['--foo', '2'])
     Namespace(foo='2')
     >>> parser.parse_args([])
     Namespace(foo=42)

If the target namespace already has an attribute set, the action
'default' will not over write it:

     >>> parser = argparse.ArgumentParser()
     >>> parser.add_argument('--foo', default=42)
     >>> parser.parse_args([], namespace=argparse.Namespace(foo=101))
     Namespace(foo=101)

If the ‘default’ value is a string, the parser parses the value as if it
were a command-line argument.  In particular, the parser applies any
*note type: 2b6a. conversion argument, if provided, before setting the
attribute on the *note Namespace: 2b47. return value.  Otherwise, the
parser uses the value as is:

     >>> parser = argparse.ArgumentParser()
     >>> parser.add_argument('--length', default='10', type=int)
     >>> parser.add_argument('--width', default=10.5, type=int)
     >>> parser.parse_args()
     Namespace(length=10, width=10.5)

For positional arguments with *note nargs: 2b50. equal to ‘?’ or ‘*’,
the ‘default’ value is used when no command-line argument was present:

     >>> parser = argparse.ArgumentParser()
     >>> parser.add_argument('foo', nargs='?', default=42)
     >>> parser.parse_args(['a'])
     Namespace(foo='a')
     >>> parser.parse_args([])
     Namespace(foo=42)

Providing ‘default=argparse.SUPPRESS’ causes no attribute to be added if
the command-line argument was not present:

     >>> parser = argparse.ArgumentParser()
     >>> parser.add_argument('--foo', default=argparse.SUPPRESS)
     >>> parser.parse_args([])
     Namespace()
     >>> parser.parse_args(['--foo', '1'])
     Namespace(foo='1')


File: python.info,  Node: type,  Next: choices,  Prev: default,  Up: The add_argument method

5.16.4.27 type
..............

By default, the parser reads command-line arguments in as simple
strings.  However, quite often the command-line string should instead be
interpreted as another type, such as a *note float: 2c8. or *note int:
23c.  The ‘type’ keyword for *note add_argument(): 184. allows any
necessary type-checking and type conversions to be performed.

If the *note type: 2b6a. keyword is used with the *note default: 2b4c.
keyword, the type converter is only applied if the default is a string.

The argument to ‘type’ can be any callable that accepts a single string.
If the function raises *note ArgumentTypeError: 2b77, *note TypeError:
4dd, or *note ValueError: 1e7, the exception is caught and a nicely
formatted error message is displayed.  No other exception types are
handled.

Common built-in types and functions can be used as type converters:

     import argparse
     import pathlib

     parser = argparse.ArgumentParser()
     parser.add_argument('count', type=int)
     parser.add_argument('distance', type=float)
     parser.add_argument('street', type=ascii)
     parser.add_argument('code_point', type=ord)
     parser.add_argument('source_file', type=open)
     parser.add_argument('dest_file', type=argparse.FileType('w', encoding='latin-1'))
     parser.add_argument('datapath', type=pathlib.Path)

User defined functions can be used as well:

     >>> def hyphenated(string):
     ...     return '-'.join([word[:4] for word in string.casefold().split()])
     ...
     >>> parser = argparse.ArgumentParser()
     >>> _ = parser.add_argument('short_title', type=hyphenated)
     >>> parser.parse_args(['"The Tale of Two Cities"'])
     Namespace(short_title='"the-tale-of-two-citi')

The *note bool(): 40e. function is not recommended as a type converter.
All it does is convert empty strings to ‘False’ and non-empty strings to
‘True’.  This is usually not what is desired.

In general, the ‘type’ keyword is a convenience that should only be used
for simple conversions that can only raise one of the three supported
exceptions.  Anything with more interesting error-handling or resource
management should be done downstream after the arguments are parsed.

For example, JSON or YAML conversions have complex error cases that
require better reporting than can be given by the ‘type’ keyword.  A
*note JSONDecodeError: dc6. would not be well formatted and a *note
FileNotFoundError: e67. exception would not be handled at all.

Even *note FileType: ebf. has its limitations for use with the ‘type’
keyword.  If one argument uses 'FileType' and then a subsequent argument
fails, an error is reported but the file is not automatically closed.
In this case, it would be better to wait until after the parser has run
and then use the *note with: 577.-statement to manage the files.

For type checkers that simply check against a fixed set of values,
consider using the *note choices: 2b4a. keyword instead.


File: python.info,  Node: choices,  Next: required,  Prev: type,  Up: The add_argument method

5.16.4.28 choices
.................

Some command-line arguments should be selected from a restricted set of
values.  These can be handled by passing a sequence object as the
'choices' keyword argument to *note add_argument(): 184.  When the
command line is parsed, argument values will be checked, and an error
message will be displayed if the argument was not one of the acceptable
values:

     >>> parser = argparse.ArgumentParser(prog='game.py')
     >>> parser.add_argument('move', choices=['rock', 'paper', 'scissors'])
     >>> parser.parse_args(['rock'])
     Namespace(move='rock')
     >>> parser.parse_args(['fire'])
     usage: game.py [-h] {rock,paper,scissors}
     game.py: error: argument move: invalid choice: 'fire' (choose from 'rock',
     'paper', 'scissors')

Note that inclusion in the 'choices' sequence is checked after any *note
type: 2b6a. conversions have been performed, so the type of the objects
in the 'choices' sequence should match the *note type: 2b6a. specified:

     >>> parser = argparse.ArgumentParser(prog='doors.py')
     >>> parser.add_argument('door', type=int, choices=range(1, 4))
     >>> print(parser.parse_args(['3']))
     Namespace(door=3)
     >>> parser.parse_args(['4'])
     usage: doors.py [-h] {1,2,3}
     doors.py: error: argument door: invalid choice: 4 (choose from 1, 2, 3)

Any sequence can be passed as the 'choices' value, so *note list: 5b6.
objects, *note tuple: 322. objects, and custom sequences are all
supported.

Use of *note enum.Enum: 5d6. is not recommended because it is difficult
to control its appearance in usage, help, and error messages.

Formatted choices override the default 'metavar' which is normally
derived from 'dest'.  This is usually what you want because the user
never sees the 'dest' parameter.  If this display isn't desirable
(perhaps because there are many choices), just specify an explicit *note
metavar: 2b4f.


File: python.info,  Node: required,  Next: 幫助,  Prev: choices,  Up: The add_argument method

5.16.4.29 required
..................

In general, the *note argparse: 5. module assumes that flags like ‘-f’
and ‘--bar’ indicate 'optional' arguments, which can always be omitted
at the command line.  To make an option 'required', ‘True’ can be
specified for the ‘required=’ keyword argument to *note add_argument():
184.:

     >>> parser = argparse.ArgumentParser()
     >>> parser.add_argument('--foo', required=True)
     >>> parser.parse_args(['--foo', 'BAR'])
     Namespace(foo='BAR')
     >>> parser.parse_args([])
     usage: [-h] --foo FOO
     : error: the following arguments are required: --foo

As the example shows, if an option is marked as ‘required’, *note
parse_args(): 2b46. will report an error if that option is not present
at the command line.

     備註: Required options are generally considered bad form because
     users expect 'options' to be 'optional', and thus they should be
     avoided when possible.


File: python.info,  Node: 幫助,  Next: metavar,  Prev: required,  Up: The add_argument method

5.16.4.30 幫助
..............

The ‘help’ value is a string containing a brief description of the
argument.  When a user requests help (usually by using ‘-h’ or ‘--help’
at the command line), these ‘help’ descriptions will be displayed with
each argument:

     >>> parser = argparse.ArgumentParser(prog='frobble')
     >>> parser.add_argument('--foo', action='store_true',
     ...                     help='foo the bars before frobbling')
     >>> parser.add_argument('bar', nargs='+',
     ...                     help='one of the bars to be frobbled')
     >>> parser.parse_args(['-h'])
     usage: frobble [-h] [--foo] bar [bar ...]

     positional arguments:
      bar     one of the bars to be frobbled

     options:
      -h, --help  show this help message and exit
      --foo   foo the bars before frobbling

The ‘help’ strings can include various format specifiers to avoid
repetition of things like the program name or the argument *note
default: 2b4c.  The available specifiers include the program name,
‘%(prog)s’ and most keyword arguments to *note add_argument(): 184, e.g.
‘%(default)s’, ‘%(type)s’, etc.:

     >>> parser = argparse.ArgumentParser(prog='frobble')
     >>> parser.add_argument('bar', nargs='?', type=int, default=42,
     ...                     help='the bar to %(prog)s (default: %(default)s)')
     >>> parser.print_help()
     usage: frobble [-h] [bar]

     positional arguments:
      bar     the bar to frobble (default: 42)

     options:
      -h, --help  show this help message and exit

As the help string supports %-formatting, if you want a literal ‘%’ to
appear in the help string, you must escape it as ‘%%’.

*note argparse: 5. supports silencing the help entry for certain
options, by setting the ‘help’ value to ‘argparse.SUPPRESS’:

     >>> parser = argparse.ArgumentParser(prog='frobble')
     >>> parser.add_argument('--foo', help=argparse.SUPPRESS)
     >>> parser.print_help()
     usage: frobble [-h]

     options:
       -h, --help  show this help message and exit


File: python.info,  Node: metavar,  Next: dest,  Prev: 幫助,  Up: The add_argument method

5.16.4.31 metavar
.................

When *note ArgumentParser: 4de. generates help messages, it needs some
way to refer to each expected argument.  By default, ArgumentParser
objects use the *note dest: 2b4d. value as the "name" of each object.
By default, for positional argument actions, the *note dest: 2b4d. value
is used directly, and for optional argument actions, the *note dest:
2b4d. value is uppercased.  So, a single positional argument with
‘dest='bar'’ will be referred to as ‘bar’.  A single optional argument
‘--foo’ that should be followed by a single command-line argument will
be referred to as ‘FOO’.  An example:

     >>> parser = argparse.ArgumentParser()
     >>> parser.add_argument('--foo')
     >>> parser.add_argument('bar')
     >>> parser.parse_args('X --foo Y'.split())
     Namespace(bar='X', foo='Y')
     >>> parser.print_help()
     usage:  [-h] [--foo FOO] bar

     positional arguments:
      bar

     options:
      -h, --help  show this help message and exit
      --foo FOO

An alternative name can be specified with ‘metavar’:

     >>> parser = argparse.ArgumentParser()
     >>> parser.add_argument('--foo', metavar='YYY')
     >>> parser.add_argument('bar', metavar='XXX')
     >>> parser.parse_args('X --foo Y'.split())
     Namespace(bar='X', foo='Y')
     >>> parser.print_help()
     usage:  [-h] [--foo YYY] XXX

     positional arguments:
      XXX

     options:
      -h, --help  show this help message and exit
      --foo YYY

Note that ‘metavar’ only changes the 'displayed' name - the name of the
attribute on the *note parse_args(): 2b46. object is still determined by
the *note dest: 2b4d. value.

Different values of ‘nargs’ may cause the metavar to be used multiple
times.  Providing a tuple to ‘metavar’ specifies a different display for
each of the arguments:

     >>> parser = argparse.ArgumentParser(prog='PROG')
     >>> parser.add_argument('-x', nargs=2)
     >>> parser.add_argument('--foo', nargs=2, metavar=('bar', 'baz'))
     >>> parser.print_help()
     usage: PROG [-h] [-x X X] [--foo bar baz]

     options:
      -h, --help     show this help message and exit
      -x X X
      --foo bar baz


File: python.info,  Node: dest,  Next: deprecated,  Prev: metavar,  Up: The add_argument method

5.16.4.32 dest
..............

Most *note ArgumentParser: 4de. actions add some value as an attribute
of the object returned by *note parse_args(): 2b46.  The name of this
attribute is determined by the ‘dest’ keyword argument of *note
add_argument(): 184.  For positional argument actions, ‘dest’ is
normally supplied as the first argument to *note add_argument(): 184.:

     >>> parser = argparse.ArgumentParser()
     >>> parser.add_argument('bar')
     >>> parser.parse_args(['XXX'])
     Namespace(bar='XXX')

For optional argument actions, the value of ‘dest’ is normally inferred
from the option strings.  *note ArgumentParser: 4de. generates the value
of ‘dest’ by taking the first long option string and stripping away the
initial ‘--’ string.  If no long option strings were supplied, ‘dest’
will be derived from the first short option string by stripping the
initial ‘-’ character.  Any internal ‘-’ characters will be converted to
‘_’ characters to make sure the string is a valid attribute name.  The
examples below illustrate this behavior:

     >>> parser = argparse.ArgumentParser()
     >>> parser.add_argument('-f', '--foo-bar', '--foo')
     >>> parser.add_argument('-x', '-y')
     >>> parser.parse_args('-f 1 -x 2'.split())
     Namespace(foo_bar='1', x='2')
     >>> parser.parse_args('--foo 1 -y 2'.split())
     Namespace(foo_bar='1', x='2')

‘dest’ allows a custom attribute name to be provided:

     >>> parser = argparse.ArgumentParser()
     >>> parser.add_argument('--foo', dest='bar')
     >>> parser.parse_args('--foo XXX'.split())
     Namespace(bar='XXX')


File: python.info,  Node: deprecated,  Next: Action classes,  Prev: dest,  Up: The add_argument method

5.16.4.33 deprecated
....................

During a project's lifetime, some arguments may need to be removed from
the command line.  Before removing them, you should inform your users
that the arguments are deprecated and will be removed.  The ‘deprecated’
keyword argument of *note add_argument(): 184, which defaults to
‘False’, specifies if the argument is deprecated and will be removed in
the future.  For arguments, if ‘deprecated’ is ‘True’, then a warning
will be printed to standard error when the argument is used:

     >>> import argparse
     >>> parser = argparse.ArgumentParser(prog='snake.py')
     >>> parser.add_argument('--legs', default=0, type=int, deprecated=True)
     >>> parser.parse_args([])
     Namespace(legs=0)
     >>> parser.parse_args(['--legs', '4'])
     snake.py: warning: option '--legs' is deprecated
     Namespace(legs=4)

在 3.13 版被加入.


File: python.info,  Node: Action classes,  Prev: deprecated,  Up: The add_argument method

5.16.4.34 Action classes
........................

Action classes implement the Action API, a callable which returns a
callable which processes arguments from the command-line.  Any object
which follows this API may be passed as the ‘action’ parameter to *note
add_argument(): 184.

 -- 類別: argparse.Action (option_strings, dest, nargs=None, const=None,
          default=None, type=None, choices=None, required=False,
          help=None, metavar=None)

Action objects are used by an ArgumentParser to represent the
information needed to parse a single argument from one or more strings
from the command line.  The Action class must accept the two positional
arguments plus any keyword arguments passed to *note
ArgumentParser.add_argument(): 184. except for the ‘action’ itself.

Instances of Action (or return value of any callable to the ‘action’
parameter) should have attributes "dest", "option_strings", "default",
"type", "required", "help", etc.  defined.  The easiest way to ensure
these attributes are defined is to call ‘Action.__init__’.

Action instances should be callable, so subclasses must override the
‘__call__’ method, which should accept four parameters:

   * ‘parser’ - The ArgumentParser object which contains this action.

   * ‘namespace’ - The *note Namespace: 2b47. object that will be
     returned by *note parse_args(): 2b46.  Most actions add an
     attribute to this object using *note setattr(): 2032.

   * ‘values’ - The associated command-line arguments, with any type
     conversions applied.  Type conversions are specified with the *note
     type: 2b6a. keyword argument to *note add_argument(): 184.

   * ‘option_string’ - The option string that was used to invoke this
     action.  The ‘option_string’ argument is optional, and will be
     absent if the action is associated with a positional argument.

The ‘__call__’ method may perform arbitrary actions, but will typically
set attributes on the ‘namespace’ based on ‘dest’ and ‘values’.

Action subclasses can define a ‘format_usage’ method that takes no
argument and return a string which will be used when printing the usage
of the program.  If such method is not provided, a sensible default will
be used.


File: python.info,  Node: The parse_args method,  Next: Other utilities,  Prev: The add_argument method,  Up: argparse --- Parser for command-line options arguments and sub-commands

5.16.4.35 The parse_args() method
.................................

 -- 方法: ArgumentParser.parse_args (args=None, namespace=None)

     Convert argument strings to objects and assign them as attributes
     of the namespace.  Return the populated namespace.

     Previous calls to *note add_argument(): 184. determine exactly what
     objects are created and how they are assigned.  See the
     documentation for *note add_argument(): 184. for details.

        * *note args: 2b80. - List of strings to parse.  The default is
          taken from *note sys.argv: 11fd.

        * *note namespace: 2b81. - An object to take the attributes.
          The default is a new empty *note Namespace: 2b47. object.

* Menu:

* Option value syntax::
* Invalid arguments::
* Arguments containing -::
* Argument abbreviations (prefix matching): Argument abbreviations prefix matching.
* Beyond sys.argv: Beyond sys argv.
* The Namespace object::


File: python.info,  Node: Option value syntax,  Next: Invalid arguments,  Up: The parse_args method

5.16.4.36 Option value syntax
.............................

The *note parse_args(): 2b46. method supports several ways of specifying
the value of an option (if it takes one).  In the simplest case, the
option and its value are passed as two separate arguments:

     >>> parser = argparse.ArgumentParser(prog='PROG')
     >>> parser.add_argument('-x')
     >>> parser.add_argument('--foo')
     >>> parser.parse_args(['-x', 'X'])
     Namespace(foo=None, x='X')
     >>> parser.parse_args(['--foo', 'FOO'])
     Namespace(foo='FOO', x=None)

For long options (options with names longer than a single character),
the option and value can also be passed as a single command-line
argument, using ‘=’ to separate them:

     >>> parser.parse_args(['--foo=FOO'])
     Namespace(foo='FOO', x=None)

For short options (options only one character long), the option and its
value can be concatenated:

     >>> parser.parse_args(['-xX'])
     Namespace(foo=None, x='X')

Several short options can be joined together, using only a single ‘-’
prefix, as long as only the last option (or none of them) requires a
value:

     >>> parser = argparse.ArgumentParser(prog='PROG')
     >>> parser.add_argument('-x', action='store_true')
     >>> parser.add_argument('-y', action='store_true')
     >>> parser.add_argument('-z')
     >>> parser.parse_args(['-xyzZ'])
     Namespace(x=True, y=True, z='Z')


File: python.info,  Node: Invalid arguments,  Next: Arguments containing -,  Prev: Option value syntax,  Up: The parse_args method

5.16.4.37 Invalid arguments
...........................

While parsing the command line, *note parse_args(): 2b46. checks for a
variety of errors, including ambiguous options, invalid types, invalid
options, wrong number of positional arguments, etc.  When it encounters
such an error, it exits and prints the error along with a usage message:

     >>> parser = argparse.ArgumentParser(prog='PROG')
     >>> parser.add_argument('--foo', type=int)
     >>> parser.add_argument('bar', nargs='?')

     >>> # invalid type
     >>> parser.parse_args(['--foo', 'spam'])
     usage: PROG [-h] [--foo FOO] [bar]
     PROG: error: argument --foo: invalid int value: 'spam'

     >>> # invalid option
     >>> parser.parse_args(['--bar'])
     usage: PROG [-h] [--foo FOO] [bar]
     PROG: error: no such option: --bar

     >>> # wrong number of arguments
     >>> parser.parse_args(['spam', 'badger'])
     usage: PROG [-h] [--foo FOO] [bar]
     PROG: error: extra arguments found: badger


File: python.info,  Node: Arguments containing -,  Next: Argument abbreviations prefix matching,  Prev: Invalid arguments,  Up: The parse_args method

5.16.4.38 Arguments containing ‘-’
..................................

The *note parse_args(): 2b46. method attempts to give errors whenever
the user has clearly made a mistake, but some situations are inherently
ambiguous.  For example, the command-line argument ‘-1’ could either be
an attempt to specify an option or an attempt to provide a positional
argument.  The *note parse_args(): 2b46. method is cautious here:
positional arguments may only begin with ‘-’ if they look like negative
numbers and there are no options in the parser that look like negative
numbers:

     >>> parser = argparse.ArgumentParser(prog='PROG')
     >>> parser.add_argument('-x')
     >>> parser.add_argument('foo', nargs='?')

     >>> # no negative number options, so -1 is a positional argument
     >>> parser.parse_args(['-x', '-1'])
     Namespace(foo=None, x='-1')

     >>> # no negative number options, so -1 and -5 are positional arguments
     >>> parser.parse_args(['-x', '-1', '-5'])
     Namespace(foo='-5', x='-1')

     >>> parser = argparse.ArgumentParser(prog='PROG')
     >>> parser.add_argument('-1', dest='one')
     >>> parser.add_argument('foo', nargs='?')

     >>> # negative number options present, so -1 is an option
     >>> parser.parse_args(['-1', 'X'])
     Namespace(foo=None, one='X')

     >>> # negative number options present, so -2 is an option
     >>> parser.parse_args(['-2'])
     usage: PROG [-h] [-1 ONE] [foo]
     PROG: error: no such option: -2

     >>> # negative number options present, so both -1s are options
     >>> parser.parse_args(['-1', '-1'])
     usage: PROG [-h] [-1 ONE] [foo]
     PROG: error: argument -1: expected one argument

If you have positional arguments that must begin with ‘-’ and don't look
like negative numbers, you can insert the pseudo-argument ‘'--'’ which
tells *note parse_args(): 2b46. that everything after that is a
positional argument:

     >>> parser.parse_args(['--', '-f'])
     Namespace(foo='-f', one=None)

See also *note the argparse howto on ambiguous arguments: 2b74. for more
details.


File: python.info,  Node: Argument abbreviations prefix matching,  Next: Beyond sys argv,  Prev: Arguments containing -,  Up: The parse_args method

5.16.4.39 Argument abbreviations (prefix matching)
..................................................

The *note parse_args(): 2b46. method *note by default: d66. allows long
options to be abbreviated to a prefix, if the abbreviation is
unambiguous (the prefix matches a unique option):

     >>> parser = argparse.ArgumentParser(prog='PROG')
     >>> parser.add_argument('-bacon')
     >>> parser.add_argument('-badger')
     >>> parser.parse_args('-bac MMM'.split())
     Namespace(bacon='MMM', badger=None)
     >>> parser.parse_args('-bad WOOD'.split())
     Namespace(bacon=None, badger='WOOD')
     >>> parser.parse_args('-ba BA'.split())
     usage: PROG [-h] [-bacon BACON] [-badger BADGER]
     PROG: error: ambiguous option: -ba could match -badger, -bacon

An error is produced for arguments that could produce more than one
options.  This feature can be disabled by setting *note allow_abbrev:
d66. to ‘False’.


File: python.info,  Node: Beyond sys argv,  Next: The Namespace object,  Prev: Argument abbreviations prefix matching,  Up: The parse_args method

5.16.4.40 Beyond ‘sys.argv’
...........................

Sometimes it may be useful to have an ArgumentParser parse arguments
other than those of *note sys.argv: 11fd.  This can be accomplished by
passing a list of strings to *note parse_args(): 2b46.  This is useful
for testing at the interactive prompt:

     >>> parser = argparse.ArgumentParser()
     >>> parser.add_argument(
     ...     'integers', metavar='int', type=int, choices=range(10),
     ...     nargs='+', help='an integer in the range 0..9')
     >>> parser.add_argument(
     ...     '--sum', dest='accumulate', action='store_const', const=sum,
     ...     default=max, help='sum the integers (default: find the max)')
     >>> parser.parse_args(['1', '2', '3', '4'])
     Namespace(accumulate=<built-in function max>, integers=[1, 2, 3, 4])
     >>> parser.parse_args(['1', '2', '3', '4', '--sum'])
     Namespace(accumulate=<built-in function sum>, integers=[1, 2, 3, 4])


File: python.info,  Node: The Namespace object,  Prev: Beyond sys argv,  Up: The parse_args method

5.16.4.41 The Namespace object
..............................

 -- 類別: argparse.Namespace

     Simple class used by default by *note parse_args(): 2b46. to create
     an object holding attributes and return it.

This class is deliberately simple, just an *note object: a2f. subclass
with a readable string representation.  If you prefer to have dict-like
view of the attributes, you can use the standard Python idiom, *note
vars(): 1948.:

     >>> parser = argparse.ArgumentParser()
     >>> parser.add_argument('--foo')
     >>> args = parser.parse_args(['--foo', 'BAR'])
     >>> vars(args)
     {'foo': 'BAR'}

It may also be useful to have an *note ArgumentParser: 4de. assign
attributes to an already existing object, rather than a new *note
Namespace: 2b47. object.  This can be achieved by specifying the
‘namespace=’ keyword argument:

     >>> class C:
     ...     pass
     ...
     >>> c = C()
     >>> parser = argparse.ArgumentParser()
     >>> parser.add_argument('--foo')
     >>> parser.parse_args(args=['--foo', 'BAR'], namespace=c)
     >>> c.foo
     'BAR'


File: python.info,  Node: Other utilities,  Next: Upgrading optparse code,  Prev: The parse_args method,  Up: argparse --- Parser for command-line options arguments and sub-commands

5.16.4.42 Other utilities
.........................

* Menu:

* Sub-commands::
* FileType 物件::
* Argument groups::
* Mutual exclusion::
* Parser defaults::
* Printing help::
* Partial parsing::
* Customizing file parsing::
* Exiting methods::
* Intermixed parsing::


File: python.info,  Node: Sub-commands,  Next: FileType 物件,  Up: Other utilities

5.16.4.43 Sub-commands
......................

 -- 方法: ArgumentParser.add_subparsers ([title][, description][,
          prog][, parser_class][, action][, option_strings][, dest][,
          required][, help][, metavar])

     Many programs split up their functionality into a number of
     sub-commands, for example, the ‘svn’ program can invoke
     sub-commands like ‘svn checkout’, ‘svn update’, and ‘svn commit’.
     Splitting up functionality this way can be a particularly good idea
     when a program performs several different functions which require
     different kinds of command-line arguments.  *note ArgumentParser:
     4de. supports the creation of such sub-commands with the *note
     add_subparsers(): bbe. method.  The *note add_subparsers(): bbe.
     method is normally called with no arguments and returns a special
     action object.  This object has a single method, ‘add_parser()’,
     which takes a command name and any *note ArgumentParser: 4de.
     constructor arguments, and returns an *note ArgumentParser: 4de.
     object that can be modified as usual.

     Description of parameters:

        * title - title for the sub-parser group in help output; by
          default "subcommands" if description is provided, otherwise
          uses title for positional arguments

        * description - description for the sub-parser group in help
          output, by default ‘None’

        * prog - usage information that will be displayed with
          sub-command help, by default the name of the program and any
          positional arguments before the subparser argument

        * parser_class - class which will be used to create sub-parser
          instances, by default the class of the current parser (e.g.
          ArgumentParser)

        * *note action: 2b49. - the basic type of action to be taken
          when this argument is encountered at the command line

        * *note dest: 2b4d. - name of the attribute under which
          sub-command name will be stored; by default ‘None’ and no
          value is stored

        * *note required: 2b51. - Whether or not a subcommand must be
          provided, by default ‘False’ (added in 3.7)

        * *note help: 2b4e. - help for sub-parser group in help output,
          by default ‘None’

        * *note metavar: 2b4f. - string presenting available
          sub-commands in help; by default it is ‘None’ and presents
          sub-commands in form {cmd1, cmd2, ..}

     一些使用範例：

          >>> # create the top-level parser
          >>> parser = argparse.ArgumentParser(prog='PROG')
          >>> parser.add_argument('--foo', action='store_true', help='foo help')
          >>> subparsers = parser.add_subparsers(help='sub-command help')
          >>>
          >>> # create the parser for the "a" command
          >>> parser_a = subparsers.add_parser('a', help='a help')
          >>> parser_a.add_argument('bar', type=int, help='bar help')
          >>>
          >>> # create the parser for the "b" command
          >>> parser_b = subparsers.add_parser('b', help='b help')
          >>> parser_b.add_argument('--baz', choices='XYZ', help='baz help')
          >>>
          >>> # parse some argument lists
          >>> parser.parse_args(['a', '12'])
          Namespace(bar=12, foo=False)
          >>> parser.parse_args(['--foo', 'b', '--baz', 'Z'])
          Namespace(baz='Z', foo=True)

     Note that the object returned by *note parse_args(): 2b46. will
     only contain attributes for the main parser and the subparser that
     was selected by the command line (and not any other subparsers).
     So in the example above, when the ‘a’ command is specified, only
     the ‘foo’ and ‘bar’ attributes are present, and when the ‘b’
     command is specified, only the ‘foo’ and ‘baz’ attributes are
     present.

     Similarly, when a help message is requested from a subparser, only
     the help for that particular parser will be printed.  The help
     message will not include parent parser or sibling parser messages.
     (A help message for each subparser command, however, can be given
     by supplying the ‘help=’ argument to ‘add_parser()’ as above.)

          >>> parser.parse_args(['--help'])
          usage: PROG [-h] [--foo] {a,b} ...

          positional arguments:
            {a,b}   sub-command help
              a     a help
              b     b help

          options:
            -h, --help  show this help message and exit
            --foo   foo help

          >>> parser.parse_args(['a', '--help'])
          usage: PROG a [-h] bar

          positional arguments:
            bar     bar help

          options:
            -h, --help  show this help message and exit

          >>> parser.parse_args(['b', '--help'])
          usage: PROG b [-h] [--baz {X,Y,Z}]

          options:
            -h, --help     show this help message and exit
            --baz {X,Y,Z}  baz help

     The *note add_subparsers(): bbe. method also supports ‘title’ and
     ‘description’ keyword arguments.  When either is present, the
     subparser's commands will appear in their own group in the help
     output.  For example:

          >>> parser = argparse.ArgumentParser()
          >>> subparsers = parser.add_subparsers(title='subcommands',
          ...                                    description='valid subcommands',
          ...                                    help='additional help')
          >>> subparsers.add_parser('foo')
          >>> subparsers.add_parser('bar')
          >>> parser.parse_args(['-h'])
          usage:  [-h] {foo,bar} ...

          options:
            -h, --help  show this help message and exit

          subcommands:
            valid subcommands

            {foo,bar}   additional help

     Furthermore, ‘add_parser()’ supports an additional 'aliases'
     argument, which allows multiple strings to refer to the same
     subparser.  This example, like ‘svn’, aliases ‘co’ as a shorthand
     for ‘checkout’:

          >>> parser = argparse.ArgumentParser()
          >>> subparsers = parser.add_subparsers()
          >>> checkout = subparsers.add_parser('checkout', aliases=['co'])
          >>> checkout.add_argument('foo')
          >>> parser.parse_args(['co', 'bar'])
          Namespace(foo='bar')

     ‘add_parser()’ supports also an additional 'deprecated' argument,
     which allows to deprecate the subparser.

          >>> import argparse
          >>> parser = argparse.ArgumentParser(prog='chicken.py')
          >>> subparsers = parser.add_subparsers()
          >>> run = subparsers.add_parser('run')
          >>> fly = subparsers.add_parser('fly', deprecated=True)
          >>> parser.parse_args(['fly'])
          chicken.py: warning: command 'fly' is deprecated
          Namespace()

     在 3.13 版被加入.

     One particularly effective way of handling sub-commands is to
     combine the use of the *note add_subparsers(): bbe. method with
     calls to *note set_defaults(): 2b6c. so that each subparser knows
     which Python function it should execute.  For example:

          >>> # sub-command functions
          >>> def foo(args):
          ...     print(args.x * args.y)
          ...
          >>> def bar(args):
          ...     print('((%s))' % args.z)
          ...
          >>> # create the top-level parser
          >>> parser = argparse.ArgumentParser()
          >>> subparsers = parser.add_subparsers(required=True)
          >>>
          >>> # create the parser for the "foo" command
          >>> parser_foo = subparsers.add_parser('foo')
          >>> parser_foo.add_argument('-x', type=int, default=1)
          >>> parser_foo.add_argument('y', type=float)
          >>> parser_foo.set_defaults(func=foo)
          >>>
          >>> # create the parser for the "bar" command
          >>> parser_bar = subparsers.add_parser('bar')
          >>> parser_bar.add_argument('z')
          >>> parser_bar.set_defaults(func=bar)
          >>>
          >>> # parse the args and call whatever function was selected
          >>> args = parser.parse_args('foo 1 -x 2'.split())
          >>> args.func(args)
          2.0
          >>>
          >>> # parse the args and call whatever function was selected
          >>> args = parser.parse_args('bar XYZYX'.split())
          >>> args.func(args)
          ((XYZYX))

     This way, you can let *note parse_args(): 2b46. do the job of
     calling the appropriate function after argument parsing is
     complete.  Associating functions with actions like this is
     typically the easiest way to handle the different actions for each
     of your subparsers.  However, if it is necessary to check the name
     of the subparser that was invoked, the ‘dest’ keyword argument to
     the *note add_subparsers(): bbe. call will work:

          >>> parser = argparse.ArgumentParser()
          >>> subparsers = parser.add_subparsers(dest='subparser_name')
          >>> subparser1 = subparsers.add_parser('1')
          >>> subparser1.add_argument('-x')
          >>> subparser2 = subparsers.add_parser('2')
          >>> subparser2.add_argument('y')
          >>> parser.parse_args(['2', 'frobble'])
          Namespace(subparser_name='2', y='frobble')

     在 3.7 版的變更: New 'required' keyword argument.


File: python.info,  Node: FileType 物件,  Next: Argument groups,  Prev: Sub-commands,  Up: Other utilities

5.16.4.44 FileType 物件
.......................

 -- 類別: argparse.FileType (mode='r', bufsize=-1, encoding=None,
          errors=None)

     The *note FileType: ebf. factory creates objects that can be passed
     to the type argument of *note ArgumentParser.add_argument(): 184.
     Arguments that have *note FileType: ebf. objects as their type will
     open command-line arguments as files with the requested modes,
     buffer sizes, encodings and error handling (see the *note open():
     4c0. function for more details):

          >>> parser = argparse.ArgumentParser()
          >>> parser.add_argument('--raw', type=argparse.FileType('wb', 0))
          >>> parser.add_argument('out', type=argparse.FileType('w', encoding='UTF-8'))
          >>> parser.parse_args(['--raw', 'raw.dat', 'file.txt'])
          Namespace(out=<_io.TextIOWrapper name='file.txt' mode='w' encoding='UTF-8'>, raw=<_io.FileIO name='raw.dat' mode='wb'>)

     FileType objects understand the pseudo-argument ‘'-'’ and
     automatically convert this into *note sys.stdin: 4e2. for readable
     *note FileType: ebf. objects and *note sys.stdout: a79. for
     writable *note FileType: ebf. objects:

          >>> parser = argparse.ArgumentParser()
          >>> parser.add_argument('infile', type=argparse.FileType('r'))
          >>> parser.parse_args(['-'])
          Namespace(infile=<_io.TextIOWrapper name='<stdin>' encoding='UTF-8'>)

     在 3.4 版的變更: Added the 'encodings' and 'errors' parameters.


File: python.info,  Node: Argument groups,  Next: Mutual exclusion,  Prev: FileType 物件,  Up: Other utilities

5.16.4.45 Argument groups
.........................

 -- 方法: ArgumentParser.add_argument_group (title=None,
          description=None)

     By default, *note ArgumentParser: 4de. groups command-line
     arguments into "positional arguments" and "options" when displaying
     help messages.  When there is a better conceptual grouping of
     arguments than this default one, appropriate groups can be created
     using the *note add_argument_group(): 2b8c. method:

          >>> parser = argparse.ArgumentParser(prog='PROG', add_help=False)
          >>> group = parser.add_argument_group('group')
          >>> group.add_argument('--foo', help='foo help')
          >>> group.add_argument('bar', help='bar help')
          >>> parser.print_help()
          usage: PROG [--foo FOO] bar

          group:
            bar    bar help
            --foo FOO  foo help

     The *note add_argument_group(): 2b8c. method returns an argument
     group object which has an *note add_argument(): 184. method just
     like a regular *note ArgumentParser: 4de.  When an argument is
     added to the group, the parser treats it just like a normal
     argument, but displays the argument in a separate group for help
     messages.  The *note add_argument_group(): 2b8c. method accepts
     'title' and 'description' arguments which can be used to customize
     this display:

          >>> parser = argparse.ArgumentParser(prog='PROG', add_help=False)
          >>> group1 = parser.add_argument_group('group1', 'group1 description')
          >>> group1.add_argument('foo', help='foo help')
          >>> group2 = parser.add_argument_group('group2', 'group2 description')
          >>> group2.add_argument('--bar', help='bar help')
          >>> parser.print_help()
          usage: PROG [--bar BAR] foo

          group1:
            group1 description

            foo    foo help

          group2:
            group2 description

            --bar BAR  bar help

     Note that any arguments not in your user-defined groups will end up
     back in the usual "positional arguments" and "optional arguments"
     sections.

     在 3.11 版的變更: Calling *note add_argument_group(): 2b8c. on an
     argument group is deprecated.  This feature was never supported and
     does not always work correctly.  The function exists on the API by
     accident through inheritance and will be removed in the future.


File: python.info,  Node: Mutual exclusion,  Next: Parser defaults,  Prev: Argument groups,  Up: Other utilities

5.16.4.46 Mutual exclusion
..........................

 -- 方法: ArgumentParser.add_mutually_exclusive_group (required=False)

     Create a mutually exclusive group.  *note argparse: 5. will make
     sure that only one of the arguments in the mutually exclusive group
     was present on the command line:

          >>> parser = argparse.ArgumentParser(prog='PROG')
          >>> group = parser.add_mutually_exclusive_group()
          >>> group.add_argument('--foo', action='store_true')
          >>> group.add_argument('--bar', action='store_false')
          >>> parser.parse_args(['--foo'])
          Namespace(bar=True, foo=True)
          >>> parser.parse_args(['--bar'])
          Namespace(bar=False, foo=False)
          >>> parser.parse_args(['--foo', '--bar'])
          usage: PROG [-h] [--foo | --bar]
          PROG: error: argument --bar: not allowed with argument --foo

     The *note add_mutually_exclusive_group(): 2b8e. method also accepts
     a 'required' argument, to indicate that at least one of the
     mutually exclusive arguments is required:

          >>> parser = argparse.ArgumentParser(prog='PROG')
          >>> group = parser.add_mutually_exclusive_group(required=True)
          >>> group.add_argument('--foo', action='store_true')
          >>> group.add_argument('--bar', action='store_false')
          >>> parser.parse_args([])
          usage: PROG [-h] (--foo | --bar)
          PROG: error: one of the arguments --foo --bar is required

     Note that currently mutually exclusive argument groups do not
     support the 'title' and 'description' arguments of *note
     add_argument_group(): 2b8c.  However, a mutually exclusive group
     can be added to an argument group that has a title and description.
     For example:

          >>> parser = argparse.ArgumentParser(prog='PROG')
          >>> group = parser.add_argument_group('Group title', 'Group description')
          >>> exclusive_group = group.add_mutually_exclusive_group(required=True)
          >>> exclusive_group.add_argument('--foo', help='foo help')
          >>> exclusive_group.add_argument('--bar', help='bar help')
          >>> parser.print_help()
          usage: PROG [-h] (--foo FOO | --bar BAR)

          options:
            -h, --help  show this help message and exit

          Group title:
            Group description

            --foo FOO   foo help
            --bar BAR   bar help

     在 3.11 版的變更: Calling *note add_argument_group(): 2b8c. or
     *note add_mutually_exclusive_group(): 2b8e. on a mutually exclusive
     group is deprecated.  These features were never supported and do
     not always work correctly.  The functions exist on the API by
     accident through inheritance and will be removed in the future.


File: python.info,  Node: Parser defaults,  Next: Printing help,  Prev: Mutual exclusion,  Up: Other utilities

5.16.4.47 Parser defaults
.........................

 -- 方法: ArgumentParser.set_defaults (**kwargs)

     Most of the time, the attributes of the object returned by *note
     parse_args(): 2b46. will be fully determined by inspecting the
     command-line arguments and the argument actions.  *note
     set_defaults(): 2b6c. allows some additional attributes that are
     determined without any inspection of the command line to be added:

          >>> parser = argparse.ArgumentParser()
          >>> parser.add_argument('foo', type=int)
          >>> parser.set_defaults(bar=42, baz='badger')
          >>> parser.parse_args(['736'])
          Namespace(bar=42, baz='badger', foo=736)

     Note that parser-level defaults always override argument-level
     defaults:

          >>> parser = argparse.ArgumentParser()
          >>> parser.add_argument('--foo', default='bar')
          >>> parser.set_defaults(foo='spam')
          >>> parser.parse_args([])
          Namespace(foo='spam')

     Parser-level defaults can be particularly useful when working with
     multiple parsers.  See the *note add_subparsers(): bbe. method for
     an example of this type.

 -- 方法: ArgumentParser.get_default (dest)

     Get the default value for a namespace attribute, as set by either
     *note add_argument(): 184. or by *note set_defaults(): 2b6c.:

          >>> parser = argparse.ArgumentParser()
          >>> parser.add_argument('--foo', default='badger')
          >>> parser.get_default('foo')
          'badger'


File: python.info,  Node: Printing help,  Next: Partial parsing,  Prev: Parser defaults,  Up: Other utilities

5.16.4.48 Printing help
.......................

In most typical applications, *note parse_args(): 2b46. will take care
of formatting and printing any usage or error messages.  However,
several formatting methods are available:

 -- 方法: ArgumentParser.print_usage (file=None)

     Print a brief description of how the *note ArgumentParser: 4de.
     should be invoked on the command line.  If 'file' is ‘None’, *note
     sys.stdout: a79. is assumed.

 -- 方法: ArgumentParser.print_help (file=None)

     Print a help message, including the program usage and information
     about the arguments registered with the *note ArgumentParser: 4de.
     If 'file' is ‘None’, *note sys.stdout: a79. is assumed.

There are also variants of these methods that simply return a string
instead of printing it:

 -- 方法: ArgumentParser.format_usage ()

     Return a string containing a brief description of how the *note
     ArgumentParser: 4de. should be invoked on the command line.

 -- 方法: ArgumentParser.format_help ()

     Return a string containing a help message, including the program
     usage and information about the arguments registered with the *note
     ArgumentParser: 4de.


File: python.info,  Node: Partial parsing,  Next: Customizing file parsing,  Prev: Printing help,  Up: Other utilities

5.16.4.49 Partial parsing
.........................

 -- 方法: ArgumentParser.parse_known_args (args=None, namespace=None)

Sometimes a script may only parse a few of the command-line arguments,
passing the remaining arguments on to another script or program.  In
these cases, the *note parse_known_args(): 2b96. method can be useful.
It works much like *note parse_args(): 2b46. except that it does not
produce an error when extra arguments are present.  Instead, it returns
a two item tuple containing the populated namespace and the list of
remaining argument strings.

     >>> parser = argparse.ArgumentParser()
     >>> parser.add_argument('--foo', action='store_true')
     >>> parser.add_argument('bar')
     >>> parser.parse_known_args(['--foo', '--badger', 'BAR', 'spam'])
     (Namespace(bar='BAR', foo=True), ['--badger', 'spam'])

     警告: *note Prefix matching: d65. rules apply to *note
     parse_known_args(): 2b96.  The parser may consume an option even if
     it's just a prefix of one of its known options, instead of leaving
     it in the remaining arguments list.


File: python.info,  Node: Customizing file parsing,  Next: Exiting methods,  Prev: Partial parsing,  Up: Other utilities

5.16.4.50 Customizing file parsing
..................................

 -- 方法: ArgumentParser.convert_arg_line_to_args (arg_line)

     Arguments that are read from a file (see the
     'fromfile_prefix_chars' keyword argument to the *note
     ArgumentParser: 4de. constructor) are read one argument per line.
     *note convert_arg_line_to_args(): 2b6b. can be overridden for
     fancier reading.

     This method takes a single argument 'arg_line' which is a string
     read from the argument file.  It returns a list of arguments parsed
     from this string.  The method is called once per line read from the
     argument file, in order.

     A useful override of this method is one that treats each
     space-separated word as an argument.  The following example
     demonstrates how to do this:

          class MyArgumentParser(argparse.ArgumentParser):
              def convert_arg_line_to_args(self, arg_line):
                  return arg_line.split()


File: python.info,  Node: Exiting methods,  Next: Intermixed parsing,  Prev: Customizing file parsing,  Up: Other utilities

5.16.4.51 Exiting methods
.........................

 -- 方法: ArgumentParser.exit (status=0, message=None)

     This method terminates the program, exiting with the specified
     'status' and, if given, it prints a 'message' before that.  The
     user can override this method to handle these steps differently:

          class ErrorCatchingArgumentParser(argparse.ArgumentParser):
              def exit(self, status=0, message=None):
                  if status:
                      raise Exception(f'Exiting because of an error: {message}')
                  exit(status)

 -- 方法: ArgumentParser.error (message)

     This method prints a usage message including the 'message' to the
     standard error and terminates the program with a status code of 2.


File: python.info,  Node: Intermixed parsing,  Prev: Exiting methods,  Up: Other utilities

5.16.4.52 Intermixed parsing
............................

 -- 方法: ArgumentParser.parse_intermixed_args (args=None,
          namespace=None)

 -- 方法: ArgumentParser.parse_known_intermixed_args (args=None,
          namespace=None)

A number of Unix commands allow the user to intermix optional arguments
with positional arguments.  The *note parse_intermixed_args(): aa3. and
*note parse_known_intermixed_args(): 2b9c. methods support this parsing
style.

These parsers do not support all the argparse features, and will raise
exceptions if unsupported features are used.  In particular, subparsers,
and mutually exclusive groups that include both optionals and
positionals are not supported.

The following example shows the difference between *note
parse_known_args(): 2b96. and *note parse_intermixed_args(): aa3.: the
former returns ‘['2', '3']’ as unparsed arguments, while the latter
collects all the positionals into ‘rest’.

     >>> parser = argparse.ArgumentParser()
     >>> parser.add_argument('--foo')
     >>> parser.add_argument('cmd')
     >>> parser.add_argument('rest', nargs='*', type=int)
     >>> parser.parse_known_args('doit 1 --foo bar 2 3'.split())
     (Namespace(cmd='doit', foo='bar', rest=[1]), ['2', '3'])
     >>> parser.parse_intermixed_args('doit 1 --foo bar 2 3'.split())
     Namespace(cmd='doit', foo='bar', rest=[1, 2, 3])

*note parse_known_intermixed_args(): 2b9c. returns a two item tuple
containing the populated namespace and the list of remaining argument
strings.  *note parse_intermixed_args(): aa3. raises an error if there
are any remaining unparsed argument strings.

在 3.7 版被加入.


File: python.info,  Node: Upgrading optparse code,  Next: Exceptions<3>,  Prev: Other utilities,  Up: argparse --- Parser for command-line options arguments and sub-commands

5.16.4.53 Upgrading optparse code
.................................

Originally, the *note argparse: 5. module had attempted to maintain
compatibility with *note optparse: 90.  However, *note optparse: 90. was
difficult to extend transparently, particularly with the changes
required to support the new ‘nargs=’ specifiers and better usage
messages.  When most everything in *note optparse: 90. had either been
copy-pasted over or monkey-patched, it no longer seemed practical to try
to maintain the backwards compatibility.

The *note argparse: 5. module improves on the standard library *note
optparse: 90. module in a number of ways including:

   * Handling positional arguments.

   * Supporting sub-commands.

   * Allowing alternative option prefixes like ‘+’ and ‘/’.

   * Handling zero-or-more and one-or-more style arguments.

   * Producing more informative usage messages.

   * Providing a much simpler interface for custom ‘type’ and ‘action’.

A partial upgrade path from *note optparse: 90. to *note argparse: 5.:

   * Replace all *note optparse.OptionParser.add_option(): 2b9e. calls
     with *note ArgumentParser.add_argument(): 184. calls.

   * Replace ‘(options, args) = parser.parse_args()’ with ‘args =
     parser.parse_args()’ and add additional *note
     ArgumentParser.add_argument(): 184. calls for the positional
     arguments.  Keep in mind that what was previously called ‘options’,
     now in the *note argparse: 5. context is called ‘args’.

   * Replace *note optparse.OptionParser.disable_interspersed_args():
     2b9f. by using *note parse_intermixed_args(): aa3. instead of *note
     parse_args(): 2b46.

   * Replace callback actions and the ‘callback_*’ keyword arguments
     with ‘type’ or ‘action’ arguments.

   * Replace string names for ‘type’ keyword arguments with the
     corresponding type objects (e.g.  int, float, complex, etc).

   * Replace *note optparse.Values: 2ba0. with *note Namespace: 2b47.
     and *note optparse.OptionError: 2ba1. and *note
     optparse.OptionValueError: 2ba2. with *note ArgumentError: 2ba3.

   * Replace strings with implicit arguments such as ‘%default’ or
     ‘%prog’ with the standard Python syntax to use dictionaries to
     format strings, that is, ‘%(default)s’ and ‘%(prog)s’.

   * Replace the OptionParser constructor ‘version’ argument with a call
     to ‘parser.add_argument('--version', action='version',
     version='<the version>')’.


File: python.info,  Node: Exceptions<3>,  Prev: Upgrading optparse code,  Up: argparse --- Parser for command-line options arguments and sub-commands

5.16.4.54 Exceptions
....................

 -- 例外: argparse.ArgumentError

     An error from creating or using an argument (optional or
     positional).

     The string value of this exception is the message, augmented with
     information about the argument that caused it.

 -- 例外: argparse.ArgumentTypeError

     Raised when something goes wrong converting a command line string
     to a type.


File: python.info,  Node: logging --- Python 的日誌記錄工具,  Next: logging config --- 日誌記錄配置,  Prev: argparse --- Parser for command-line options arguments and sub-commands,  Up: 通用作業系統服務

5.16.5 ‘logging’ -- Python 的日誌記錄工具
-----------------------------------------

'原始碼：'Lib/logging/__init__.py(1)

Important
.........

此頁面包含 API 參考訊息。有關教學流程和更進階的主題討論，請參閱

   * *note 基礎教學: 118d.

   * *note 進階教學: 118e.

   * *note 日誌記錄手冊: 118f.

__________________________________________________________________

這個模組定義了函式與類別 (class)，為應用程式和函式庫實作彈性的日誌管理系
統。

由標準函式庫模組提供的日誌記錄 API 的主要好處是，所有的 Python 模組都能
參與日誌記錄，因此你的應用程式日誌可以包含你自己的訊息，並與來自第三方模
組的訊息整合在一起。

Here's a simple example of idiomatic usage:

     # myapp.py
     import logging
     import mylib
     logger = logging.getLogger(__name__)

     def main():
         logging.basicConfig(filename='myapp.log', level=logging.INFO)
         logger.info('Started')
         mylib.do_something()
         logger.info('Finished')

     if __name__ == '__main__':
         main()

     # mylib.py
     import logging
     logger = logging.getLogger(__name__)

     def do_something():
         logger.info('Doing something')

If you run 'myapp.py', you should see this in 'myapp.log':

     INFO:__main__:Started
     INFO:mylib:Doing something
     INFO:__main__:Finished

The key feature of this idiomatic usage is that the majority of code is
simply creating a module level logger with ‘getLogger(__name__)’, and
using that logger to do any needed logging.  This is concise, while
allowing downstream code fine-grained control if needed.  Logged
messages to the module-level logger get forwarded to handlers of loggers
in higher-level modules, all the way up to the highest-level logger
known as the root logger; this approach is known as hierarchical
logging.

For logging to be useful, it needs to be configured: setting the levels
and destinations for each logger, potentially changing how specific
modules log, often based on command-line arguments or application
configuration.  In most cases, like the one above, only the root logger
needs to be so configured, since all the lower level loggers at module
level eventually forward their messages to its handlers.  *note
basicConfig(): 9a4. provides a quick way to configure the root logger
that handles many use cases.

這個模組提供了很多的功能性以及彈性。如果你對於 logging 不熟悉，熟悉它最
好的方法就是去看教學（'請看右上方的連結'）。

The basic classes defined by the module, together with their attributes
and methods, are listed in the sections below.

   * Loggers expose the interface that application code directly uses.

   * Handlers send the log records (created by loggers) to the
     appropriate destination.

   * Filters provide a finer grained facility for determining which log
     records to output.

   * 格式器指定日誌記錄在最終輸出中的佈局。

* Menu:

* Logger 物件::
* Logging Levels::
* Handler Objects::
* Formatter Objects::
* Filter Objects::
* LogRecord 物件::
* LogRecord attributes::
* LoggerAdapter 物件::
* Thread Safety::
* Module-Level Functions::
* Module-Level Attributes::
* Integration with the warnings module::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/logging/__init__.py


File: python.info,  Node: Logger 物件,  Next: Logging Levels,  Up: logging --- Python 的日誌記錄工具

5.16.5.1 Logger 物件
....................

Loggers have the following attributes and methods.  Note that Loggers
should 'NEVER' be instantiated directly, but always through the
module-level function ‘logging.getLogger(name)’.  Multiple calls to
*note getLogger(): 904. with the same name will always return a
reference to the same Logger object.

The ‘name’ is potentially a period-separated hierarchical value, like
‘foo.bar.baz’ (though it could also be just plain ‘foo’, for example).
Loggers that are further down in the hierarchical list are children of
loggers higher up in the list.  For example, given a logger with a name
of ‘foo’, loggers with names of ‘foo.bar’, ‘foo.bar.baz’, and ‘foo.bam’
are all descendants of ‘foo’.  In addition, all loggers are descendants
of the root logger.  The logger name hierarchy is analogous to the
Python package hierarchy, and identical to it if you organise your
loggers on a per-module basis using the recommended construction
‘logging.getLogger(__name__)’.  That's because in a module, ‘__name__’
is the module's name in the Python package namespace.

 -- 類別: logging.Logger

      -- 屬性: name

          This is the logger's name, and is the value that was passed to
          *note getLogger(): 904. to obtain the logger.

               備註: This attribute should be treated as read-only.

      -- 屬性: level

          The threshold of this logger, as set by the *note setLevel():
          13fc. method.

               備註: Do not set this attribute directly - always use
               *note setLevel(): 13fc, which has checks for the level
               passed to it.

      -- 屬性: parent

          The parent logger of this logger.  It may change based on
          later instantiation of loggers which are higher up in the
          namespace hierarchy.

               備註: This value should be treated as read-only.

      -- 屬性: propagate

          如果此屬性評估為 true，則在此日誌紀錄器被記錄的事件會被傳到更
          高階（上代）日誌記錄器 的處理函式和所有附加在此日誌記錄器的任
          何處理器。訊息會直接傳到上代 loggers 的處理器 - 在問題中上代日
          誌記錄器的層級或是篩選器都不會被考慮。

          If this evaluates to false, logging messages are not passed to
          the handlers of ancestor loggers.

          Spelling it out with an example: If the propagate attribute of
          the logger named ‘A.B.C’ evaluates to true, any event logged
          to ‘A.B.C’ via a method call such as
          ‘logging.getLogger('A.B.C').error(...)’ will [subject to
          passing that logger's level and filter settings] be passed in
          turn to any handlers attached to loggers named ‘A.B’, ‘A’ and
          the root logger, after first being passed to any handlers
          attached to ‘A.B.C’.  If any logger in the chain ‘A.B.C’,
          ‘A.B’, ‘A’ has its ‘propagate’ attribute set to false, then
          that is the last logger whose handlers are offered the event
          to handle, and propagation stops at that point.

          此建構函式將該屬性設為 ‘True’。

               備註: If you attach a handler to a logger 'and' one or
               more of its ancestors, it may emit the same record
               multiple times.  In general, you should not need to
               attach a handler to more than one logger - if you just
               attach it to the appropriate logger which is highest in
               the logger hierarchy, then it will see all events logged
               by all descendant loggers, provided that their propagate
               setting is left set to ‘True’.  A common scenario is to
               attach handlers only to the root logger, and to let
               propagation take care of the rest.

      -- 屬性: handlers

          The list of handlers directly attached to this logger
          instance.

               備註: This attribute should be treated as read-only; it
               is normally changed via the *note addHandler(): 2bad. and
               *note removeHandler(): 2bae. methods, which use locks to
               ensure thread-safe operation.

      -- 屬性: disabled

          This attribute disables handling of any events.  It is set to
          ‘False’ in the initializer, and only changed by logging
          configuration code.

               備註: This attribute should be treated as read-only.

      -- 方法: setLevel (level)

          Sets the threshold for this logger to 'level'.  Logging
          messages which are less severe than 'level' will be ignored;
          logging messages which have severity 'level' or higher will be
          emitted by whichever handler or handlers service this logger,
          unless a handler's level has been set to a higher severity
          level than 'level'.

          當一個日誌記錄器被建立時，記錄層級會被設定成 *note NOTSET:
          2bb0. （當此日誌記錄器是根日誌記錄器，或是代表父日誌記錄器的非
          根日誌記錄器時，會使所有訊息被處理）。請注意根日誌記錄器會以記
          錄等級 *note WARNING: 1bf7. 被建立。

          The term 'delegation to the parent' means that if a logger has
          a level of NOTSET, its chain of ancestor loggers is traversed
          until either an ancestor with a level other than NOTSET is
          found, or the root is reached.

          If an ancestor is found with a level other than NOTSET, then
          that ancestor's level is treated as the effective level of the
          logger where the ancestor search began, and is used to
          determine how a logging event is handled.

          If the root is reached, and it has a level of NOTSET, then all
          messages will be processed.  Otherwise, the root's level will
          be used as the effective level.

          層級清單請見 *note Logging Levels: 600.。

          在 3.2 版的變更: The 'level' parameter now accepts a string
          representation of the level such as 'INFO' as an alternative
          to the integer constants such as *note INFO: 1bf6.  Note,
          however, that levels are internally stored as integers, and
          methods such as e.g.  *note getEffectiveLevel(): 2bb1. and
          *note isEnabledFor(): 1289. will return/expect to be passed
          integers.

      -- 方法: isEnabledFor (level)

          Indicates if a message of severity 'level' would be processed
          by this logger.  This method checks first the module-level
          level set by ‘logging.disable(level)’ and then the logger's
          effective level as determined by *note getEffectiveLevel():
          2bb1.

      -- 方法: getEffectiveLevel ()

          Indicates the effective level for this logger.  If a value
          other than *note NOTSET: 2bb0. has been set using *note
          setLevel(): 13fc, it is returned.  Otherwise, the hierarchy is
          traversed towards the root until a value other than *note
          NOTSET: 2bb0. is found, and that value is returned.  The value
          returned is an integer, typically one of *note logging.DEBUG:
          1bf5, *note logging.INFO: 1bf6. etc.

      -- 方法: getChild (suffix)

          Returns a logger which is a descendant to this logger, as
          determined by the suffix.  Thus,
          ‘logging.getLogger('abc').getChild('def.ghi')’ would return
          the same logger as would be returned by
          ‘logging.getLogger('abc.def.ghi')’.  This is a convenience
          method, useful when the parent logger is named using e.g.
          ‘__name__’ rather than a literal string.

          在 3.2 版被加入.

      -- 方法: getChildren ()

          Returns a set of loggers which are immediate children of this
          logger.  So for example ‘logging.getLogger().getChildren()’
          might return a set containing loggers named ‘foo’ and ‘bar’,
          but a logger named ‘foo.bar’ wouldn't be included in the set.
          Likewise, ‘logging.getLogger('foo').getChildren()’ might
          return a set including a logger named ‘foo.bar’, but it
          wouldn't include one named ‘foo.bar.baz’.

          在 3.12 版被加入.

      -- 方法: debug (msg, *args, **kwargs)

          Logs a message with level *note DEBUG: 1bf5. on this logger.
          The 'msg' is the message format string, and the 'args' are the
          arguments which are merged into 'msg' using the string
          formatting operator.  (Note that this means that you can use
          keywords in the format string, together with a single
          dictionary argument.)  No % formatting operation is performed
          on 'msg' when no 'args' are supplied.

          There are four keyword arguments in 'kwargs' which are
          inspected: 'exc_info', 'stack_info', 'stacklevel' and 'extra'.

          If 'exc_info' does not evaluate as false, it causes exception
          information to be added to the logging message.  If an
          exception tuple (in the format returned by *note
          sys.exc_info(): 630.) or an exception instance is provided, it
          is used; otherwise, *note sys.exc_info(): 630. is called to
          get the exception information.

          The second optional keyword argument is 'stack_info', which
          defaults to ‘False’.  If true, stack information is added to
          the logging message, including the actual logging call.  Note
          that this is not the same stack information as that displayed
          through specifying 'exc_info': The former is stack frames from
          the bottom of the stack up to the logging call in the current
          thread, whereas the latter is information about stack frames
          which have been unwound, following an exception, while
          searching for exception handlers.

          You can specify 'stack_info' independently of 'exc_info', e.g.
          to just show how you got to a certain point in your code, even
          when no exceptions were raised.  The stack frames are printed
          following a header line which says:

               Stack (most recent call last):

          This mimics the ‘Traceback (most recent call last):’ which is
          used when displaying exception frames.

          The third optional keyword argument is 'stacklevel', which
          defaults to ‘1’.  If greater than 1, the corresponding number
          of stack frames are skipped when computing the line number and
          function name set in the *note LogRecord: f89. created for the
          logging event.  This can be used in logging helpers so that
          the function name, filename and line number recorded are not
          the information for the helper function/method, but rather its
          caller.  The name of this parameter mirrors the equivalent one
          in the *note warnings: fa. module.

          The fourth keyword argument is 'extra' which can be used to
          pass a dictionary which is used to populate the __dict__ of
          the *note LogRecord: f89. created for the logging event with
          user-defined attributes.  These custom attributes can then be
          used as you like.  For example, they could be incorporated
          into logged messages.  For example:

               FORMAT = '%(asctime)s %(clientip)-15s %(user)-8s %(message)s'
               logging.basicConfig(format=FORMAT)
               d = {'clientip': '192.168.0.1', 'user': 'fbloggs'}
               logger = logging.getLogger('tcpserver')
               logger.warning('Protocol problem: %s', 'connection reset', extra=d)

          would print something like

               2006-02-08 22:20:02,165 192.168.0.1 fbloggs  Protocol problem: connection reset

          The keys in the dictionary passed in 'extra' should not clash
          with the keys used by the logging system.  (See the section on
          *note LogRecord attributes: 2bb2. for more information on
          which keys are used by the logging system.)

          If you choose to use these attributes in logged messages, you
          need to exercise some care.  In the above example, for
          instance, the *note Formatter: 1400. has been set up with a
          format string which expects 'clientip' and 'user' in the
          attribute dictionary of the *note LogRecord: f89.  If these
          are missing, the message will not be logged because a string
          formatting exception will occur.  So in this case, you always
          need to pass the 'extra' dictionary with these keys.

          While this might be annoying, this feature is intended for use
          in specialized circumstances, such as multi-threaded servers
          where the same code executes in many contexts, and interesting
          conditions which arise are dependent on this context (such as
          remote client IP address and authenticated user name, in the
          above example).  In such circumstances, it is likely that
          specialized *note Formatter: 1400.s would be used with
          particular *note Handler: 13ff.s.

          If no handler is attached to this logger (or any of its
          ancestors, taking into account the relevant *note
          Logger.propagate: 13fe. attributes), the message will be sent
          to the handler set on *note lastResort: 1192.

          在 3.2 版的變更: 新增 'stack_info' 參數。

          在 3.5 版的變更: The 'exc_info' parameter can now accept
          exception instances.

          在 3.8 版的變更: 新增 'stacklevel' 參數。

      -- 方法: info (msg, *args, **kwargs)

          Logs a message with level *note INFO: 1bf6. on this logger.
          The arguments are interpreted as for *note debug(): 2bb4.

      -- 方法: warning (msg, *args, **kwargs)

          在此記錄器上記錄一條層級為 *note WARNING: 1bf7. 的訊息。這些引
          數被直譯的方式與 *note debug(): 2bb4. 相同。

               備註: There is an obsolete method ‘warn’ which is
               functionally identical to ‘warning’.  As ‘warn’ is
               deprecated, please do not use it - use ‘warning’ instead.

      -- 方法: error (msg, *args, **kwargs)

          Logs a message with level *note ERROR: 1bf8. on this logger.
          The arguments are interpreted as for *note debug(): 2bb4.

      -- 方法: critical (msg, *args, **kwargs)

          Logs a message with level *note CRITICAL: 1bf9. on this
          logger.  The arguments are interpreted as for *note debug():
          2bb4.

      -- 方法: log (level, msg, *args, **kwargs)

          Logs a message with integer level 'level' on this logger.  The
          other arguments are interpreted as for *note debug(): 2bb4.

      -- 方法: exception (msg, *args, **kwargs)

          Logs a message with level *note ERROR: 1bf8. on this logger.
          The arguments are interpreted as for *note debug(): 2bb4.
          Exception info is added to the logging message.  This method
          should only be called from an exception handler.

      -- 方法: addFilter (filter)

          在該 logger 內增加指定的 filter 'filter'。

      -- 方法: removeFilter (filter)

          在該 logger 內移除指定的 filter 'filter'。

      -- 方法: filter (record)

          Apply this logger's filters to the record and return ‘True’ if
          the record is to be processed.  The filters are consulted in
          turn, until one of them returns a false value.  If none of
          them return a false value, the record will be processed
          (passed to handlers).  If one returns a false value, no
          further processing of the record occurs.

      -- 方法: addHandler (hdlr)

          Adds the specified handler 'hdlr' to this logger.

      -- 方法: removeHandler (hdlr)

          Removes the specified handler 'hdlr' from this logger.

      -- 方法: findCaller (stack_info=False, stacklevel=1)

          Finds the caller's source filename and line number.  Returns
          the filename, line number, function name and stack information
          as a 4-element tuple.  The stack information is returned as
          ‘None’ unless 'stack_info' is ‘True’.

          The 'stacklevel' parameter is passed from code calling the
          *note debug(): 2bb4. and other APIs.  If greater than 1, the
          excess is used to skip stack frames before determining the
          values to be returned.  This will generally be useful when
          calling logging APIs from helper/wrapper code, so that the
          information in the event log refers not to the helper/wrapper
          code, but to the code that calls it.

      -- 方法: handle (record)

          Handles a record by passing it to all handlers associated with
          this logger and its ancestors (until a false value of
          'propagate' is found).  This method is used for unpickled
          records received from a socket, as well as those created
          locally.  Logger-level filtering is applied using *note
          filter(): 2bb8.

      -- 方法: makeRecord (name, level, fn, lno, msg, args, exc_info,
               func=None, extra=None, sinfo=None)

          This is a factory method which can be overridden in subclasses
          to create specialized *note LogRecord: f89. instances.

      -- 方法: hasHandlers ()

          Checks to see if this logger has any handlers configured.
          This is done by looking for handlers in this logger and its
          parents in the logger hierarchy.  Returns ‘True’ if a handler
          was found, else ‘False’.  The method stops searching up the
          hierarchy whenever a logger with the 'propagate' attribute set
          to false is found - that will be the last logger which is
          checked for the existence of handlers.

          在 3.2 版被加入.

     在 3.7 版的變更: Loggers can now be pickled and unpickled.


File: python.info,  Node: Logging Levels,  Next: Handler Objects,  Prev: Logger 物件,  Up: logging --- Python 的日誌記錄工具

5.16.5.2 Logging Levels
.......................

The numeric values of logging levels are given in the following table.
These are primarily of interest if you want to define your own levels,
and need them to have specific values relative to the predefined levels.
If you define a level with the same numeric value, it overwrites the
predefined value; the predefined name is lost.

Level                       Numeric value       What it means / When to use it
                                                
------------------------------------------------------------------------------------------
                                                
 -- 資料: logging.NOTSET    0                   When set on a logger, indicates that
                                                ancestor loggers are to be consulted to
                                                determine the effective level.  If that
                                                still resolves to ‘NOTSET’, then all
                                                events are logged.  When set on a
                                                handler, all events are handled.
                                                
                                                
 -- 資料: logging.DEBUG     10                  Detailed information, typically only of
                                                interest to a developer trying to
                                                diagnose a problem.
                                                
                                                
 -- 資料: logging.INFO      20                  Confirmation that things are working as
                                                expected.
                                                
                                                
 -- 資料: logging.WARNING   30                  An indication that something unexpected
                                                happened, or that a problem might occur
                                                in the near future (e.g.  'disk space
                                                low').  The software is still working
                                                as expected.
                                                
                                                
 -- 資料: logging.ERROR     40                  Due to a more serious problem, the
                                                software has not been able to perform
                                                some function.
                                                
                                                
 -- 資料:                   50                  A serious error, indicating that the
          logging.CRITICAL                      program itself may be unable to
                                                continue running.
                                                


File: python.info,  Node: Handler Objects,  Next: Formatter Objects,  Prev: Logging Levels,  Up: logging --- Python 的日誌記錄工具

5.16.5.3 Handler Objects
........................

Handlers have the following attributes and methods.  Note that *note
Handler: 13ff. is never instantiated directly; this class acts as a base
for more useful subclasses.  However, the ‘__init__()’ method in
subclasses needs to call *note Handler.__init__(): 2bc0.

 -- 類別: logging.Handler

      -- 方法: __init__ (level=NOTSET)

          Initializes the *note Handler: 13ff. instance by setting its
          level, setting the list of filters to the empty list and
          creating a lock (using *note createLock(): 2bc1.) for
          serializing access to an I/O mechanism.

      -- 方法: createLock ()

          Initializes a thread lock which can be used to serialize
          access to underlying I/O functionality which may not be
          threadsafe.

      -- 方法: acquire ()

          Acquires the thread lock created with *note createLock():
          2bc1.

      -- 方法: release ()

          Releases the thread lock acquired with *note acquire(): 2bc2.

      -- 方法: setLevel (level)

          Sets the threshold for this handler to 'level'.  Logging
          messages which are less severe than 'level' will be ignored.
          When a handler is created, the level is set to *note NOTSET:
          2bb0. (which causes all messages to be processed).

          層級清單請見 *note Logging Levels: 600.。

          在 3.2 版的變更: The 'level' parameter now accepts a string
          representation of the level such as 'INFO' as an alternative
          to the integer constants such as *note INFO: 1bf6.

      -- 方法: setFormatter (fmt)

          Sets the *note Formatter: 1400. for this handler to 'fmt'.

      -- 方法: addFilter (filter)

          Adds the specified filter 'filter' to this handler.

      -- 方法: removeFilter (filter)

          Removes the specified filter 'filter' from this handler.

      -- 方法: filter (record)

          Apply this handler's filters to the record and return ‘True’
          if the record is to be processed.  The filters are consulted
          in turn, until one of them returns a false value.  If none of
          them return a false value, the record will be emitted.  If one
          returns a false value, the handler will not emit the record.

      -- 方法: flush ()

          Ensure all logging output has been flushed.  This version does
          nothing and is intended to be implemented by subclasses.

      -- 方法: close ()

          Tidy up any resources used by the handler.  This version does
          no output but removes the handler from an internal list of
          handlers which is closed when *note shutdown(): 2bcb. is
          called.  Subclasses should ensure that this gets called from
          overridden *note close(): 2bca. methods.

      -- 方法: handle (record)

          Conditionally emits the specified logging record, depending on
          filters which may have been added to the handler.  Wraps the
          actual emission of the record with acquisition/release of the
          I/O thread lock.

      -- 方法: handleError (record)

          This method should be called from handlers when an exception
          is encountered during an *note emit(): 2bce. call.  If the
          module-level attribute *note raiseExceptions: 1191. is
          ‘False’, exceptions get silently ignored.  This is what is
          mostly wanted for a logging system - most users will not care
          about errors in the logging system, they are more interested
          in application errors.  You could, however, replace this with
          a custom handler if you wish.  The specified record is the one
          which was being processed when the exception occurred.  (The
          default value of *note raiseExceptions: 1191. is ‘True’, as
          that is more useful during development).

      -- 方法: format (record)

          Do formatting for a record - if a formatter is set, use it.
          Otherwise, use the default formatter for the module.

      -- 方法: emit (record)

          Do whatever it takes to actually log the specified logging
          record.  This version is intended to be implemented by
          subclasses and so raises a *note NotImplementedError: 20d.

               警告: This method is called after a handler-level lock is
               acquired, which is released after this method returns.
               When you override this method, note that you should be
               careful when calling anything that invokes other parts of
               the logging API which might do locking, because that
               might result in a deadlock.  Specifically:

                  * Logging configuration APIs acquire the module-level
                    lock, and then individual handler-level locks as
                    those handlers are configured.

                  * Many logging APIs lock the module-level lock.  If
                    such an API is called from this method, it could
                    cause a deadlock if a configuration call is made on
                    another thread, because that thread will try to
                    acquire the module-level lock 'before' the
                    handler-level lock, whereas this thread tries to
                    acquire the module-level lock 'after' the
                    handler-level lock (because in this method, the
                    handler-level lock has already been acquired).

For a list of handlers included as standard, see *note logging.handlers:
7d.


File: python.info,  Node: Formatter Objects,  Next: Filter Objects,  Prev: Handler Objects,  Up: logging --- Python 的日誌記錄工具

5.16.5.4 Formatter Objects
..........................

 -- 類別: logging.Formatter (fmt=None, datefmt=None, style='%',
          validate=True, *, defaults=None)

     Responsible for converting a *note LogRecord: f89. to an output
     string to be interpreted by a human or external system.


     參數:

        * ‘fmt’ (*note str: 3f2.) - A format string in the given 'style'
          for the logged output as a whole.  The possible mapping keys
          are drawn from the *note LogRecord: f89. object's *note
          LogRecord attributes: 2bb2.  If not specified, ‘'%(message)s'’
          is used, which is just the logged message.

        * ‘datefmt’ (*note str: 3f2.) - A format string in the given
          'style' for the date/time portion of the logged output.  If
          not specified, the default described in *note formatTime():
          2bd2. is used.

        * ‘style’ (*note str: 3f2.) - Can be one of ‘'%'’, ‘'{'’ or
          ‘'$'’ and determines how the format string will be merged with
          its data: using one of *note printf-style String Formatting:
          671. (‘%’), *note str.format(): 5c7. (‘{’) or *note
          string.Template: 62d. (‘$’).  This only applies to 'fmt' and
          'datefmt' (e.g.  ‘'%(message)s'’ versus ‘'{message}'’), not to
          the actual log messages passed to the logging methods.
          However, there are *note other ways: 2bd3. to use ‘{’- and
          ‘$’-formatting for log messages.

        * ‘validate’ (*note bool: 40e.) - If ‘True’ (the default),
          incorrect or mismatched 'fmt' and 'style' will raise a *note
          ValueError: 1e7.; for example, ‘logging.Formatter('%(asctime)s
          - %(message)s', style='{')’.

        * ‘defaults’ (*note dict: 23b.‘[’*note str: 3f2.‘, ’‘Any’‘]’) -
          A dictionary with default values to use in custom fields.  For
          example, ‘logging.Formatter('%(ip)s %(message)s',
          defaults={"ip": None})’

     在 3.2 版的變更: 新增 'style' 參數。

     在 3.8 版的變更: 新增 'validate' 參數。

     在 3.10 版的變更: 新增 'defaults' 參數。

      -- 方法: format (record)

          The record's attribute dictionary is used as the operand to a
          string formatting operation.  Returns the resulting string.
          Before formatting the dictionary, a couple of preparatory
          steps are carried out.  The 'message' attribute of the record
          is computed using 'msg' % 'args'.  If the formatting string
          contains ‘'(asctime)'’, *note formatTime(): 2bd2. is called to
          format the event time.  If there is exception information, it
          is formatted using *note formatException(): 2bd5. and appended
          to the message.  Note that the formatted exception information
          is cached in attribute 'exc_text'.  This is useful because the
          exception information can be pickled and sent across the wire,
          but you should be careful if you have more than one *note
          Formatter: 1400. subclass which customizes the formatting of
          exception information.  In this case, you will have to clear
          the cached value (by setting the 'exc_text' attribute to
          ‘None’) after a formatter has done its formatting, so that the
          next formatter to handle the event doesn't use the cached
          value, but recalculates it afresh.

          If stack information is available, it's appended after the
          exception information, using *note formatStack(): 2bd6. to
          transform it if necessary.

      -- 方法: formatTime (record, datefmt=None)

          This method should be called from *note format(): 5c3. by a
          formatter which wants to make use of a formatted time.  This
          method can be overridden in formatters to provide for any
          specific requirement, but the basic behavior is as follows: if
          'datefmt' (a string) is specified, it is used with *note
          time.strftime(): 1181. to format the creation time of the
          record.  Otherwise, the format '%Y-%m-%d %H:%M:%S,uuu' is
          used, where the uuu part is a millisecond value and the other
          letters are as per the *note time.strftime(): 1181.
          documentation.  An example time in this format is ‘2003-01-23
          00:29:50,411’.  The resulting string is returned.

          This function uses a user-configurable function to convert the
          creation time to a tuple.  By default, *note time.localtime():
          1467. is used; to change this for a particular formatter
          instance, set the ‘converter’ attribute to a function with the
          same signature as *note time.localtime(): 1467. or *note
          time.gmtime(): 1158.  To change it for all formatters, for
          example if you want all logging times to be shown in GMT, set
          the ‘converter’ attribute in the ‘Formatter’ class.

          在 3.3 版的變更: Previously, the default format was hard-coded
          as in this example: ‘2010-09-06 22:38:15,292’ where the part
          before the comma is handled by a strptime format string
          (‘'%Y-%m-%d %H:%M:%S'’), and the part after the comma is a
          millisecond value.  Because strptime does not have a format
          placeholder for milliseconds, the millisecond value is
          appended using another format string, ‘'%s,%03d'’ -- and both
          of these format strings have been hardcoded into this method.
          With the change, these strings are defined as class-level
          attributes which can be overridden at the instance level when
          desired.  The names of the attributes are
          ‘default_time_format’ (for the strptime format string) and
          ‘default_msec_format’ (for appending the millisecond value).

          在 3.9 版的變更: The ‘default_msec_format’ can be ‘None’.

      -- 方法: formatException (exc_info)

          Formats the specified exception information (a standard
          exception tuple as returned by *note sys.exc_info(): 630.) as
          a string.  This default implementation just uses *note
          traceback.print_exception(): 7f3.  The resulting string is
          returned.

      -- 方法: formatStack (stack_info)

          Formats the specified stack information (a string as returned
          by *note traceback.print_stack(): e2a, but with the last
          newline removed) as a string.  This default implementation
          just returns the input value.

 -- 類別: logging.BufferingFormatter (linefmt=None)

     A base formatter class suitable for subclassing when you want to
     format a number of records.  You can pass a *note Formatter: 1400.
     instance which you want to use to format each line (that
     corresponds to a single record).  If not specified, the default
     formatter (which just outputs the event message) is used as the
     line formatter.

      -- 方法: formatHeader (records)

          Return a header for a list of 'records'.  The base
          implementation just returns the empty string.  You will need
          to override this method if you want specific behaviour, e.g.
          to show the count of records, a title or a separator line.

      -- 方法: formatFooter (records)

          Return a footer for a list of 'records'.  The base
          implementation just returns the empty string.  You will need
          to override this method if you want specific behaviour, e.g.
          to show the count of records or a separator line.

      -- 方法: format (records)

          Return formatted text for a list of 'records'.  The base
          implementation just returns the empty string if there are no
          records; otherwise, it returns the concatenation of the
          header, each record formatted with the line formatter, and the
          footer.


File: python.info,  Node: Filter Objects,  Next: LogRecord 物件,  Prev: Formatter Objects,  Up: logging --- Python 的日誌記錄工具

5.16.5.5 Filter Objects
.......................

‘Filters’ can be used by ‘Handlers’ and ‘Loggers’ for more sophisticated
filtering than is provided by levels.  The base filter class only allows
events which are below a certain point in the logger hierarchy.  For
example, a filter initialized with 'A.B' will allow events logged by
loggers 'A.B', 'A.B.C', 'A.B.C.D', 'A.B.D' etc.  but not 'A.BB', 'B.A.B'
etc.  If initialized with the empty string, all events are passed.

 -- 類別: logging.Filter (name='')

     Returns an instance of the *note Filter: 1193. class.  If 'name' is
     specified, it names a logger which, together with its children,
     will have its events allowed through the filter.  If 'name' is the
     empty string, allows every event.

      -- 方法: filter (record)

          Is the specified record to be logged?  Returns false for no,
          true for yes.  Filters can either modify log records in-place
          or return a completely different record instance which will
          replace the original log record in any future processing of
          the event.

Note that filters attached to handlers are consulted before an event is
emitted by the handler, whereas filters attached to loggers are
consulted whenever an event is logged (using *note debug(): 2bb4, *note
info(): 2bde, etc.), before sending an event to handlers.  This means
that events which have been generated by descendant loggers will not be
filtered by a logger's filter setting, unless the filter has also been
applied to those descendant loggers.

You don't actually need to subclass ‘Filter’: you can pass any instance
which has a ‘filter’ method with the same semantics.

在 3.2 版的變更: You don't need to create specialized ‘Filter’ classes,
or use other classes with a ‘filter’ method: you can use a function (or
other callable) as a filter.  The filtering logic will check to see if
the filter object has a ‘filter’ attribute: if it does, it's assumed to
be a ‘Filter’ and its *note filter(): 2bdd. method is called.
Otherwise, it's assumed to be a callable and called with the record as
the single parameter.  The returned value should conform to that
returned by *note filter(): 2bdd.

在 3.12 版的變更: You can now return a *note LogRecord: f89. instance
from filters to replace the log record rather than modifying it in
place.  This allows filters attached to a *note Handler: 13ff. to modify
the log record before it is emitted, without having side effects on
other handlers.

Although filters are used primarily to filter records based on more
sophisticated criteria than levels, they get to see every record which
is processed by the handler or logger they're attached to: this can be
useful if you want to do things like counting how many records were
processed by a particular logger or handler, or adding, changing or
removing attributes in the *note LogRecord: f89. being processed.
Obviously changing the LogRecord needs to be done with some care, but it
does allow the injection of contextual information into logs (see *note
Using Filters to impart contextual information: 2bdf.).


File: python.info,  Node: LogRecord 物件,  Next: LogRecord attributes,  Prev: Filter Objects,  Up: logging --- Python 的日誌記錄工具

5.16.5.6 LogRecord 物件
.......................

*note LogRecord: f89. instances are created automatically by the *note
Logger: af3. every time something is logged, and can be created manually
via *note makeLogRecord(): 2be2. (for example, from a pickled event
received over the wire).

 -- 類別: logging.LogRecord (name, level, pathname, lineno, msg, args,
          exc_info, func=None, sinfo=None)

     Contains all the information pertinent to the event being logged.

     The primary information is passed in 'msg' and 'args', which are
     combined using ‘msg % args’ to create the ‘message’ attribute of
     the record.


     參數:

        * ‘name’ (*note str: 3f2.) - The name of the logger used to log
          the event represented by this ‘LogRecord’.  Note that the
          logger name in the ‘LogRecord’ will always have this value,
          even though it may be emitted by a handler attached to a
          different (ancestor) logger.

        * ‘level’ (*note int: 23c.) - The *note numeric level: 600. of
          the logging event (such as ‘10’ for ‘DEBUG’, ‘20’ for ‘INFO’,
          etc).  Note that this is converted to 'two' attributes of the
          LogRecord: ‘levelno’ for the numeric value and ‘levelname’ for
          the corresponding level name.

        * ‘pathname’ (*note str: 3f2.) - The full string path of the
          source file where the logging call was made.

        * ‘lineno’ (*note int: 23c.) - The line number in the source
          file where the logging call was made.

        * ‘msg’ (*note Any: 651.) - The event description message, which
          can be a %-format string with placeholders for variable data,
          or an arbitrary object (see *note Using arbitrary objects as
          messages: 2be3.).

        * ‘args’ (*note tuple: 322.‘ | ’*note dict: 23b.‘[’*note str:
          3f2.‘, ’*note Any: 651.‘]’) - Variable data to merge into the
          'msg' argument to obtain the event description.

        * ‘exc_info’ (*note tuple: 322.‘[’*note type: cef.‘[’*note
          BaseException: 55f.‘]’‘, ’*note BaseException: 55f.‘, ’*note
          types.TracebackType: a95.‘] ’‘| ’‘None’) - An exception tuple
          with the current exception information, as returned by *note
          sys.exc_info(): 630, or ‘None’ if no exception information is
          available.

        * ‘func’ (*note str: 3f2.‘ | ’‘None’) - The name of the function
          or method from which the logging call was invoked.

        * ‘sinfo’ (*note str: 3f2.‘ | ’‘None’) - A text string
          representing stack information from the base of the stack in
          the current thread, up to the logging call.

      -- 方法: getMessage ()

          Returns the message for this *note LogRecord: f89. instance
          after merging any user-supplied arguments with the message.
          If the user-supplied message argument to the logging call is
          not a string, *note str(): 3f2. is called on it to convert it
          to a string.  This allows use of user-defined classes as
          messages, whose ‘__str__’ method can return the actual format
          string to be used.

     在 3.2 版的變更: The creation of a *note LogRecord: f89. has been
     made more configurable by providing a factory which is used to
     create the record.  The factory can be set using *note
     getLogRecordFactory(): 2be5. and *note setLogRecordFactory(): 2be6.
     (see this for the factory's signature).

     This functionality can be used to inject your own values into a
     *note LogRecord: f89. at creation time.  You can use the following
     pattern:

          old_factory = logging.getLogRecordFactory()

          def record_factory(*args, **kwargs):
              record = old_factory(*args, **kwargs)
              record.custom_attribute = 0xdecafbad
              return record

          logging.setLogRecordFactory(record_factory)

     With this pattern, multiple factories could be chained, and as long
     as they don't overwrite each other's attributes or unintentionally
     overwrite the standard attributes listed above, there should be no
     surprises.


File: python.info,  Node: LogRecord attributes,  Next: LoggerAdapter 物件,  Prev: LogRecord 物件,  Up: logging --- Python 的日誌記錄工具

5.16.5.7 LogRecord attributes
.............................

The LogRecord has a number of attributes, most of which are derived from
the parameters to the constructor.  (Note that the names do not always
correspond exactly between the LogRecord constructor parameters and the
LogRecord attributes.)  These attributes can be used to merge data from
the record into the format string.  The following table lists (in
alphabetical order) the attribute names, their meanings and the
corresponding placeholder in a %-style format string.

If you are using {}-formatting (*note str.format(): 5c7.), you can use
‘{attrname}’ as the placeholder in the format string.  If you are using
$-formatting (*note string.Template: 62d.), use the form ‘${attrname}’.
In both cases, of course, replace ‘attrname’ with the actual attribute
name you want to use.

In the case of {}-formatting, you can specify formatting flags by
placing them after the attribute name, separated from it with a colon.
For example: a placeholder of ‘{msecs:03.0f}’ would format a millisecond
value of ‘4’ as ‘004’.  Refer to the *note str.format(): 5c7.
documentation for full details on the options available to you.

Attribute name       格式                          描述
                                                   
-------------------------------------------------------------------------------------------------------
                                                   
args                 你不應該需要自己格式化它。    The tuple of arguments merged into ‘msg’ to
                                                   produce ‘message’, or a dict whose values are
                                                   used for the merge (when there is only one
                                                   argument, and it is a dictionary).
                                                   
                                                   
asctime              ‘%(asctime)s’                 Human-readable time when the
                                                   *note LogRecord: f89. was created.  By default
                                                   this is of the form '2003-07-08 16:49:45,896'
                                                   (the numbers after the comma are millisecond
                                                   portion of the time).
                                                   
                                                   
created              ‘%(created)f’                 Time when the *note LogRecord: f89. was created
                                                   (as returned by *note time.time_ns(): a8a. /
                                                   1e9).
                                                   
                                                   
exc_info             你不應該需要自己格式化它。    Exception tuple (à la ‘sys.exc_info’) or, if no
                                                   exception has occurred, ‘None’.
                                                   
                                                   
filename             ‘%(filename)s’                Filename portion of ‘pathname’.
                                                   
                                                   
funcName             ‘%(funcName)s’                Name of function containing the logging call.
                                                   
                                                   
levelname            ‘%(levelname)s’               Text logging level for the message (‘'DEBUG'’,
                                                   ‘'INFO'’, ‘'WARNING'’, ‘'ERROR'’, ‘'CRITICAL'’).
                                                   
                                                   
levelno              ‘%(levelno)s’                 Numeric logging level for the message
                                                   (*note DEBUG: 1bf5, *note INFO: 1bf6,
                                                   *note WARNING: 1bf7, *note ERROR: 1bf8,
                                                   *note CRITICAL: 1bf9.).
                                                   
                                                   
lineno               ‘%(lineno)d’                  Source line number where the logging call was
                                                   issued (if available).
                                                   
                                                   
message              ‘%(message)s’                 The logged message, computed as ‘msg % args’.
                                                   This is set when *note Formatter.format(): 2bd4.
                                                   is invoked.
                                                   
                                                   
模組                 ‘%(module)s’                  Module (name portion of ‘filename’).
                                                   
                                                   
msecs                ‘%(msecs)d’                   Millisecond portion of the time when the
                                                   *note LogRecord: f89. was created.
                                                   
                                                   
msg                  你不應該需要自己格式化它。    The format string passed in the original logging
                                                   call.  Merged with ‘args’ to produce ‘message’,
                                                   or an arbitrary object (see
                                                   *note Using arbitrary objects as messages: 2be3.).
                                                   
                                                   
name                 ‘%(name)s’                    Name of the logger used to log the call.
                                                   
                                                   
pathname             ‘%(pathname)s’                Full pathname of the source file where the
                                                   logging call was issued (if available).
                                                   
                                                   
process              ‘%(process)d’                 Process ID (if available).
                                                   
                                                   
processName          ‘%(processName)s’             Process name (if available).
                                                   
                                                   
relativeCreated      ‘%(relativeCreated)d’         Time in milliseconds when the LogRecord was
                                                   created, relative to the time the logging module
                                                   was loaded.
                                                   
                                                   
stack_info           你不應該需要自己格式化它。    Stack frame information (where available) from
                                                   the bottom of the stack in the current thread, up
                                                   to and including the stack frame of the logging
                                                   call which resulted in the creation of this
                                                   record.
                                                   
                                                   
thread               ‘%(thread)d’                  Thread ID (if available).
                                                   
                                                   
threadName           ‘%(threadName)s’              Thread name (if available).
                                                   
                                                   
taskName             ‘%(taskName)s’                *note asyncio.Task: 480. name (if available).
                                                   

在 3.1 版的變更: 新增 'processName'。

在 3.12 版的變更: 新增 'taskName'。


File: python.info,  Node: LoggerAdapter 物件,  Next: Thread Safety,  Prev: LogRecord attributes,  Up: logging --- Python 的日誌記錄工具

5.16.5.8 LoggerAdapter 物件
...........................

*note LoggerAdapter: 1288. instances are used to conveniently pass
contextual information into logging calls.  For a usage example, see the
section on *note adding contextual information to your logging output:
2bea.

 -- 類別: logging.LoggerAdapter (logger, extra, merge_extra=False)

     Returns an instance of *note LoggerAdapter: 1288. initialized with
     an underlying *note Logger: af3. instance, a dict-like object
     ('extra'), and a boolean ('merge_extra') indicating whether or not
     the 'extra' argument of individual log calls should be merged with
     the *note LoggerAdapter: 1288. extra.  The default behavior is to
     ignore the 'extra' argument of individual log calls and only use
     the one of the *note LoggerAdapter: 1288. instance

      -- 方法: process (msg, kwargs)

          Modifies the message and/or keyword arguments passed to a
          logging call in order to insert contextual information.  This
          implementation takes the object passed as 'extra' to the
          constructor and adds it to 'kwargs' using key 'extra'.  The
          return value is a ('msg', 'kwargs') tuple which has the
          (possibly modified) versions of the arguments passed in.

      -- 屬性: manager

          Delegates to the underlying ‘manager`’ on 'logger'.

      -- 屬性: _log

          Delegates to the underlying ‘_log`()’ method on 'logger'.

     In addition to the above, *note LoggerAdapter: 1288. supports the
     following methods of *note Logger: af3.: *note debug(): dd0, *note
     info(): 2bb3, *note warning(): 1600, *note error(): 2bb5, *note
     exception(): dce, *note critical(): dcf, *note log(): dcd, *note
     isEnabledFor(): 1289, *note getEffectiveLevel(): 2bb1, *note
     setLevel(): 13fc. and *note hasHandlers(): 2bbc.  These methods
     have the same signatures as their counterparts in *note Logger:
     af3, so you can use the two types of instances interchangeably.

     在 3.2 版的變更: The *note isEnabledFor(): 1289, *note
     getEffectiveLevel(): 2bb1, *note setLevel(): 13fc. and *note
     hasHandlers(): 2bbc. methods were added to *note LoggerAdapter:
     1288.  These methods delegate to the underlying logger.

     在 3.6 版的變更: Attribute ‘manager’ and method ‘_log()’ were
     added, which delegate to the underlying logger and allow adapters
     to be nested.

     在 3.13 版的變更: The 'merge_extra' argument was added.


File: python.info,  Node: Thread Safety,  Next: Module-Level Functions,  Prev: LoggerAdapter 物件,  Up: logging --- Python 的日誌記錄工具

5.16.5.9 Thread Safety
......................

The logging module is intended to be thread-safe without any special
work needing to be done by its clients.  It achieves this though using
threading locks; there is one lock to serialize access to the module's
shared data, and each handler also creates a lock to serialize access to
its underlying I/O.

If you are implementing asynchronous signal handlers using the *note
signal: b4. module, you may not be able to use logging from within such
handlers.  This is because lock implementations in the *note threading:
d6. module are not always re-entrant, and so cannot be invoked from such
signal handlers.


File: python.info,  Node: Module-Level Functions,  Next: Module-Level Attributes,  Prev: Thread Safety,  Up: logging --- Python 的日誌記錄工具

5.16.5.10 Module-Level Functions
................................

In addition to the classes described above, there are a number of
module-level functions.

 -- 函式: logging.getLogger (name=None)

     Return a logger with the specified name or, if name is ‘None’,
     return the root logger of the hierarchy.  If specified, the name is
     typically a dot-separated hierarchical name like ''a", ''a.b" or
     ''a.b.c.d".  Choice of these names is entirely up to the developer
     who is using logging, though it is recommended that ‘__name__’ be
     used unless you have a specific reason for not doing that, as
     mentioned in *note Logger 物件: 2ba7.

     All calls to this function with a given name return the same logger
     instance.  This means that logger instances never need to be passed
     between different parts of an application.

 -- 函式: logging.getLoggerClass ()

     Return either the standard *note Logger: af3. class, or the last
     class passed to *note setLoggerClass(): 2bf1.  This function may be
     called from within a new class definition, to ensure that
     installing a customized *note Logger: af3. class will not undo
     customizations already applied by other code.  For example:

          class MyLogger(logging.getLoggerClass()):
              # ... override behaviour here

 -- 函式: logging.getLogRecordFactory ()

     Return a callable which is used to create a *note LogRecord: f89.

     在 3.2 版被加入: This function has been provided, along with *note
     setLogRecordFactory(): 2be6, to allow developers more control over
     how the *note LogRecord: f89. representing a logging event is
     constructed.

     See *note setLogRecordFactory(): 2be6. for more information about
     the how the factory is called.

 -- 函式: logging.debug (msg, *args, **kwargs)

     This is a convenience function that calls *note Logger.debug():
     dd0, on the root logger.  The handling of the arguments is in every
     way identical to what is described in that method.

     The only difference is that if the root logger has no handlers,
     then *note basicConfig(): 9a4. is called, prior to calling ‘debug’
     on the root logger.

     For very short scripts or quick demonstrations of ‘logging’
     facilities, ‘debug’ and the other module-level functions may be
     convenient.  However, most programs will want to carefully and
     explicitly control the logging configuration, and should therefore
     prefer creating a module-level logger and calling *note
     Logger.debug(): dd0. (or other level-specific methods) on it, as
     described at the beginnning of this documentation.

 -- 函式: logging.info (msg, *args, **kwargs)

     Logs a message with level *note INFO: 1bf6. on the root logger.
     The arguments and behavior are otherwise the same as for *note
     debug(): 2bb4.

 -- 函式: logging.warning (msg, *args, **kwargs)

     Logs a message with level *note WARNING: 1bf7. on the root logger.
     The arguments and behavior are otherwise the same as for *note
     debug(): 2bb4.

          備註: There is an obsolete function ‘warn’ which is
          functionally identical to ‘warning’.  As ‘warn’ is deprecated,
          please do not use it - use ‘warning’ instead.

 -- 函式: logging.error (msg, *args, **kwargs)

     Logs a message with level *note ERROR: 1bf8. on the root logger.
     The arguments and behavior are otherwise the same as for *note
     debug(): 2bb4.

 -- 函式: logging.critical (msg, *args, **kwargs)

     Logs a message with level *note CRITICAL: 1bf9. on the root logger.
     The arguments and behavior are otherwise the same as for *note
     debug(): 2bb4.

 -- 函式: logging.exception (msg, *args, **kwargs)

     Logs a message with level *note ERROR: 1bf8. on the root logger.
     The arguments and behavior are otherwise the same as for *note
     debug(): 2bb4.  Exception info is added to the logging message.
     This function should only be called from an exception handler.

 -- 函式: logging.log (level, msg, *args, **kwargs)

     Logs a message with level 'level' on the root logger.  The
     arguments and behavior are otherwise the same as for *note debug():
     2bb4.

 -- 函式: logging.disable (level=CRITICAL)

     Provides an overriding level 'level' for all loggers which takes
     precedence over the logger's own level.  When the need arises to
     temporarily throttle logging output down across the whole
     application, this function can be useful.  Its effect is to disable
     all logging calls of severity 'level' and below, so that if you
     call it with a value of INFO, then all INFO and DEBUG events would
     be discarded, whereas those of severity WARNING and above would be
     processed according to the logger's effective level.  If
     ‘logging.disable(logging.NOTSET)’ is called, it effectively removes
     this overriding level, so that logging output again depends on the
     effective levels of individual loggers.

     Note that if you have defined any custom logging level higher than
     ‘CRITICAL’ (this is not recommended), you won't be able to rely on
     the default value for the 'level' parameter, but will have to
     explicitly supply a suitable value.

     在 3.7 版的變更: The 'level' parameter was defaulted to level
     ‘CRITICAL’.  See bpo-28524(1) for more information about this
     change.

 -- 函式: logging.addLevelName (level, levelName)

     Associates level 'level' with text 'levelName' in an internal
     dictionary, which is used to map numeric levels to a textual
     representation, for example when a *note Formatter: 1400. formats a
     message.  This function can also be used to define your own levels.
     The only constraints are that all levels used must be registered
     using this function, levels should be positive integers and they
     should increase in increasing order of severity.

          備註: If you are thinking of defining your own levels, please
          see the section on *note Custom Levels: 2bf7.

 -- 函式: logging.getLevelNamesMapping ()

     Returns a mapping from level names to their corresponding logging
     levels.  For example, the string "CRITICAL" maps to *note CRITICAL:
     1bf9.  The returned mapping is copied from an internal mapping on
     each call to this function.

     在 3.11 版被加入.

 -- 函式: logging.getLevelName (level)

     Returns the textual or numeric representation of logging level
     'level'.

     If 'level' is one of the predefined levels *note CRITICAL: 1bf9,
     *note ERROR: 1bf8, *note WARNING: 1bf7, *note INFO: 1bf6. or *note
     DEBUG: 1bf5. then you get the corresponding string.  If you have
     associated levels with names using *note addLevelName(): 2bf6. then
     the name you have associated with 'level' is returned.  If a
     numeric value corresponding to one of the defined levels is passed
     in, the corresponding string representation is returned.

     The 'level' parameter also accepts a string representation of the
     level such as 'INFO'. In such cases, this functions returns the
     corresponding numeric value of the level.

     If no matching numeric or string value is passed in, the string
     'Level %s' % level is returned.

          備註: Levels are internally integers (as they need to be
          compared in the logging logic).  This function is used to
          convert between an integer level and the level name displayed
          in the formatted log output by means of the ‘%(levelname)s’
          format specifier (see *note LogRecord attributes: 2bb2.), and
          vice versa.

     在 3.4 版的變更: In Python versions earlier than 3.4, this function
     could also be passed a text level, and would return the
     corresponding numeric value of the level.  This undocumented
     behaviour was considered a mistake, and was removed in Python 3.4,
     but reinstated in 3.4.2 due to retain backward compatibility.

 -- 函式: logging.getHandlerByName (name)

     Returns a handler with the specified 'name', or ‘None’ if there is
     no handler with that name.

     在 3.12 版被加入.

 -- 函式: logging.getHandlerNames ()

     Returns an immutable set of all known handler names.

     在 3.12 版被加入.

 -- 函式: logging.makeLogRecord (attrdict)

     Creates and returns a new *note LogRecord: f89. instance whose
     attributes are defined by 'attrdict'.  This function is useful for
     taking a pickled *note LogRecord: f89. attribute dictionary, sent
     over a socket, and reconstituting it as a *note LogRecord: f89.
     instance at the receiving end.

 -- 函式: logging.basicConfig (**kwargs)

     Does basic configuration for the logging system by creating a *note
     StreamHandler: 1190. with a default *note Formatter: 1400. and
     adding it to the root logger.  The functions *note debug(): 2bb4,
     *note info(): 2bde, *note warning(): 2d0, *note error(): 2bf2. and
     *note critical(): 2bf3. will call *note basicConfig(): 9a4.
     automatically if no handlers are defined for the root logger.

     This function does nothing if the root logger already has handlers
     configured, unless the keyword argument 'force' is set to ‘True’.

          備註: This function should be called from the main thread
          before other threads are started.  In versions of Python prior
          to 2.7.1 and 3.2, if this function is called from multiple
          threads, it is possible (in rare circumstances) that a handler
          will be added to the root logger more than once, leading to
          unexpected results such as messages being duplicated in the
          log.

     The following keyword arguments are supported.

     格式               描述
                        
     ---------------------------------------------------------------------
                        
     'filename'         Specifies that a *note FileHandler: 17a1. be
                        created, using the specified filename, rather
                        than a *note StreamHandler: 1190.
                        
                        
     'filemode'         If 'filename' is specified, open the file in
                        this *note mode: 2052.  Defaults to ‘'a'’.
                        
                        
     'format'           Use the specified format string for the
                        handler.  Defaults to attributes ‘levelname’,
                        ‘name’ and ‘message’ separated by colons.
                        
                        
     'datefmt'          Use the specified date/time format, as accepted
                        by *note time.strftime(): 1181.
                        
                        
     'style'            If 'format' is specified, use this style for
                        the format string.  One of ‘'%'’, ‘'{'’ or
                        ‘'$'’ for *note printf-style: 671,
                        *note str.format(): 5c7. or
                        *note string.Template: 62d. respectively.
                        Defaults to ‘'%'’.
                        
                        
     'level'            Set the root logger level to the specified
                        *note level: 600.
                        
                        
     'stream'           Use the specified stream to initialize the
                        *note StreamHandler: 1190.  Note that this
                        argument is incompatible with 'filename' - if
                        both are present, a ‘ValueError’ is raised.
                        
                        
     'handlers'         If specified, this should be an iterable of
                        already created handlers to add to the root
                        logger.  Any handlers which don't already have
                        a formatter set will be assigned the default
                        formatter created in this function.  Note that
                        this argument is incompatible with 'filename'
                        or 'stream' - if both are present, a
                        ‘ValueError’ is raised.
                        
                        
     'force'            If this keyword argument is specified as true,
                        any existing handlers attached to the root
                        logger are removed and closed, before carrying
                        out the configuration as specified by the other
                        arguments.
                        
                        
     'encoding'         If this keyword argument is specified along
                        with 'filename', its value is used when the
                        *note FileHandler: 17a1. is created, and thus
                        used when opening the output file.
                        
                        
     'errors'           If this keyword argument is specified along
                        with 'filename', its value is used when the
                        *note FileHandler: 17a1. is created, and thus
                        used when opening the output file.  If not
                        specified, the value 'backslashreplace' is
                        used.  Note that if ‘None’ is specified, it
                        will be passed as such to *note open(): 4c0,
                        which means that it will be treated the same as
                        passing 'errors'.
                        

     在 3.2 版的變更: 新增 'style' 引數。

     在 3.3 版的變更: The 'handlers' argument was added.  Additional
     checks were added to catch situations where incompatible arguments
     are specified (e.g.  'handlers' together with 'stream' or
     'filename', or 'stream' together with 'filename').

     在 3.8 版的變更: 新增 'force' 引數。

     在 3.9 版的變更: 新增 'encoding' 與 'errors' 引數。

 -- 函式: logging.shutdown ()

     Informs the logging system to perform an orderly shutdown by
     flushing and closing all handlers.  This should be called at
     application exit and no further use of the logging system should be
     made after this call.

     When the logging module is imported, it registers this function as
     an exit handler (see *note atexit: 9.), so normally there's no need
     to do that manually.

 -- 函式: logging.setLoggerClass (klass)

     Tells the logging system to use the class 'klass' when
     instantiating a logger.  The class should define ‘__init__()’ such
     that only a name argument is required, and the ‘__init__()’ should
     call ‘Logger.__init__()’.  This function is typically called before
     any loggers are instantiated by applications which need to use
     custom logger behavior.  After this call, as at any other time, do
     not instantiate loggers directly using the subclass: continue to
     use the *note logging.getLogger(): 904. API to get your loggers.

 -- 函式: logging.setLogRecordFactory (factory)

     Set a callable which is used to create a *note LogRecord: f89.


     參數: ‘factory’ - The factory callable to be used to instantiate a
     log record.

     在 3.2 版被加入: This function has been provided, along with *note
     getLogRecordFactory(): 2be5, to allow developers more control over
     how the *note LogRecord: f89. representing a logging event is
     constructed.

     The factory has the following signature:

     ‘factory(name, level, fn, lno, msg, args, exc_info, func=None,
     sinfo=None, **kwargs)’


          name: The logger name.


          level: The logging level (numeric).


          fn: The full pathname of the file where the logging call was
          made.


          lno: The line number in the file where the logging call was
          made.


          msg: The logging message.


          args: The arguments for the logging message.


          exc_info: An exception tuple, or ‘None’.


          func: The name of the function or method which invoked the
          logging call.


          sinfo: A stack traceback such as is provided by *note
          traceback.print_stack(): e2a, showing the call hierarchy.


          kwargs: 額外的關鍵字引數。

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=28524


File: python.info,  Node: Module-Level Attributes,  Next: Integration with the warnings module,  Prev: Module-Level Functions,  Up: logging --- Python 的日誌記錄工具

5.16.5.11 Module-Level Attributes
.................................

 -- 屬性: logging.lastResort

     A "handler of last resort" is available through this attribute.
     This is a *note StreamHandler: 1190. writing to ‘sys.stderr’ with a
     level of ‘WARNING’, and is used to handle logging events in the
     absence of any logging configuration.  The end result is to just
     print the message to ‘sys.stderr’.  This replaces the earlier error
     message saying that "no handlers could be found for logger XYZ". If
     you need the earlier behaviour for some reason, ‘lastResort’ can be
     set to ‘None’.

     在 3.2 版被加入.

 -- 屬性: logging.raiseExceptions

     Used to see if exceptions during handling should be propagated.

     Default: ‘True’.

     If *note raiseExceptions: 1191. is ‘False’, exceptions get silently
     ignored.  This is what is mostly wanted for a logging system - most
     users will not care about errors in the logging system, they are
     more interested in application errors.


File: python.info,  Node: Integration with the warnings module,  Prev: Module-Level Attributes,  Up: logging --- Python 的日誌記錄工具

5.16.5.12 Integration with the warnings module
..............................................

The *note captureWarnings(): 2bfb. function can be used to integrate
*note logging: 7b. with the *note warnings: fa. module.

 -- 函式: logging.captureWarnings (capture)

     This function is used to turn the capture of warnings by logging on
     and off.

     If 'capture' is ‘True’, warnings issued by the *note warnings: fa.
     module will be redirected to the logging system.  Specifically, a
     warning will be formatted using *note warnings.formatwarning():
     191b. and the resulting string logged to a logger named
     ‘'py.warnings'’ with a severity of *note WARNING: 1bf7.

     If 'capture' is ‘False’, the redirection of warnings to the logging
     system will stop, and warnings will be redirected to their original
     destinations (i.e.  those in effect before ‘captureWarnings(True)’
     was called).

也參考
......

Module *note logging.config: 7c.

     Configuration API for the logging module.

Module *note logging.handlers: 7d.

     Useful handlers included with the logging module.

PEP 282(1) - A Logging System

     The proposal which described this feature for inclusion in the
     Python standard library.

Original Python logging package(2)

     This is the original source for the *note logging: 7b. package.
     The version of the package available from this site is suitable for
     use with Python 1.5.2, 2.1.x and 2.2.x, which do not include the
     *note logging: 7b. package in the standard library.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0282/

   (2) https://old.red-dove.com/python_logging.html


File: python.info,  Node: logging config --- 日誌記錄配置,  Next: logging handlers --- 日誌紀錄處理器,  Prev: logging --- Python 的日誌記錄工具,  Up: 通用作業系統服務

5.16.6 ‘logging.config’ -- 日誌記錄配置
---------------------------------------

'原始碼：'Lib/logging/config.py(1)

Important
.........

This page contains only reference information.  For tutorials, please
see

   * *note 基礎教學: 118d.

   * *note 進階教學: 118e.

   * *note Logging Cookbook: 118f.

__________________________________________________________________

This section describes the API for configuring the logging module.

* Menu:

* Configuration functions::
* Security considerations::
* Configuration dictionary schema::
* Configuration file format::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/logging/config.py


File: python.info,  Node: Configuration functions,  Next: Security considerations,  Up: logging config --- 日誌記錄配置

5.16.6.1 Configuration functions
................................

The following functions configure the logging module.  They are located
in the *note logging.config: 7c. module.  Their use is optional -- you
can configure the logging module using these functions or by making
calls to the main API (defined in *note logging: 7b. itself) and
defining handlers which are declared either in *note logging: 7b. or
*note logging.handlers: 7d.

 -- 函式: logging.config.dictConfig (config)

     Takes the logging configuration from a dictionary.  The contents of
     this dictionary are described in *note Configuration dictionary
     schema: 2bff. below.

     If an error is encountered during configuration, this function will
     raise a *note ValueError: 1e7, *note TypeError: 4dd, *note
     AttributeError: 2f6. or *note ImportError: 352. with a suitably
     descriptive message.  The following is a (possibly incomplete) list
     of conditions which will raise an error:

        * A ‘level’ which is not a string or which is a string not
          corresponding to an actual logging level.

        * A ‘propagate’ value which is not a boolean.

        * An id which does not have a corresponding destination.

        * A non-existent handler id found during an incremental call.

        * An invalid logger name.

        * Inability to resolve to an internal or external object.

     Parsing is performed by the ‘DictConfigurator’ class, whose
     constructor is passed the dictionary used for configuration, and
     has a ‘configure()’ method.  The *note logging.config: 7c. module
     has a callable attribute ‘dictConfigClass’ which is initially set
     to ‘DictConfigurator’.  You can replace the value of
     ‘dictConfigClass’ with a suitable implementation of your own.

     *note dictConfig(): 1147. calls ‘dictConfigClass’ passing the
     specified dictionary, and then calls the ‘configure()’ method on
     the returned object to put the configuration into effect:

          def dictConfig(config):
              dictConfigClass(config).configure()

     For example, a subclass of ‘DictConfigurator’ could call
     ‘DictConfigurator.__init__()’ in its own ‘__init__()’, then set up
     custom prefixes which would be usable in the subsequent
     ‘configure()’ call.  ‘dictConfigClass’ would be bound to this new
     subclass, and then *note dictConfig(): 1147. could be called
     exactly as in the default, uncustomized state.

     在 3.2 版被加入.

 -- 函式: logging.config.fileConfig (fname, defaults=None,
          disable_existing_loggers=True, encoding=None)

     Reads the logging configuration from a *note configparser:
     1b.-format file.  The format of the file should be as described in
     *note Configuration file format: 2c00.  This function can be called
     several times from an application, allowing an end user to select
     from various pre-canned configurations (if the developer provides a
     mechanism to present the choices and load the chosen
     configuration).

     It will raise *note FileNotFoundError: e67. if the file doesn't
     exist and *note RuntimeError: 179. if the file is invalid or empty.


     參數:

        * ‘fname’ - A filename, or a file-like object, or an instance
          derived from *note RawConfigParser: f07.  If a
          ‘RawConfigParser’-derived instance is passed, it is used as
          is.  Otherwise, a *note ConfigParser: 1aa. is instantiated,
          and the configuration read by it from the object passed in
          ‘fname’.  If that has a *note readline(): a8. method, it is
          assumed to be a file-like object and read using *note
          read_file(): 4ac.; otherwise, it is assumed to be a filename
          and passed to *note read(): 13d3.

        * ‘defaults’ - Defaults to be passed to the ‘ConfigParser’ can
          be specified in this argument.

        * ‘disable_existing_loggers’ - If specified as ‘False’, loggers
          which exist when this call is made are left enabled.  The
          default is ‘True’ because this enables old behaviour in a
          backward-compatible way.  This behaviour is to disable any
          existing non-root loggers unless they or their ancestors are
          explicitly named in the logging configuration.

        * ‘encoding’ - The encoding used to open file when 'fname' is
          filename.

     在 3.4 版的變更: An instance of a subclass of *note
     RawConfigParser: f07. is now accepted as a value for ‘fname’.  This
     facilitates:

             * Use of a configuration file where logging configuration
               is just part of the overall application configuration.

             * Use of a configuration read from a file, and then
               modified by the using application (e.g.  based on
               command-line parameters or other aspects of the runtime
               environment) before being passed to ‘fileConfig’.

     在 3.10 版的變更: Added the 'encoding' parameter.

     在 3.12 版的變更: An exception will be thrown if the provided file
     doesn't exist or is invalid or empty.

 -- 函式: logging.config.listen (port=DEFAULT_LOGGING_CONFIG_PORT,
          verify=None)

     Starts up a socket server on the specified port, and listens for
     new configurations.  If no port is specified, the module's default
     ‘DEFAULT_LOGGING_CONFIG_PORT’ is used.  Logging configurations will
     be sent as a file suitable for processing by *note dictConfig():
     1147. or *note fileConfig(): af5.  Returns a *note Thread: 8f0.
     instance on which you can call *note start(): 2c01. to start the
     server, and which you can *note join(): 117c. when appropriate.  To
     stop the server, call *note stopListening(): 2c02.

     The ‘verify’ argument, if specified, should be a callable which
     should verify whether bytes received across the socket are valid
     and should be processed.  This could be done by encrypting and/or
     signing what is sent across the socket, such that the ‘verify’
     callable can perform signature verification and/or decryption.  The
     ‘verify’ callable is called with a single argument - the bytes
     received across the socket - and should return the bytes to be
     processed, or ‘None’ to indicate that the bytes should be
     discarded.  The returned bytes could be the same as the passed in
     bytes (e.g.  when only verification is done), or they could be
     completely different (perhaps if decryption were performed).

     To send a configuration to the socket, read in the configuration
     file and send it to the socket as a sequence of bytes preceded by a
     four-byte length string packed in binary using ‘struct.pack('>L',
     n)’.
          備註: Because portions of the configuration are passed through
          *note eval(): 163, use of this function may open its users to
          a security risk.  While the function only binds to a socket on
          ‘localhost’, and so does not accept connections from remote
          machines, there are scenarios where untrusted code could be
          run under the account of the process which calls *note
          listen(): f08.  Specifically, if the process calling *note
          listen(): f08. runs on a multi-user machine where users cannot
          trust each other, then a malicious user could arrange to run
          essentially arbitrary code in a victim user's process, simply
          by connecting to the victim's *note listen(): f08. socket and
          sending a configuration which runs whatever code the attacker
          wants to have executed in the victim's process.  This is
          especially easy to do if the default port is used, but not
          hard even if a different port is used.  To avoid the risk of
          this happening, use the ‘verify’ argument to *note listen():
          f08. to prevent unrecognised configurations from being
          applied.

     在 3.4 版的變更: 新增 ‘verify’ 引數。

          備註: If you want to send configurations to the listener which
          don't disable existing loggers, you will need to use a JSON
          format for the configuration, which will use *note
          dictConfig(): 1147. for configuration.  This method allows you
          to specify ‘disable_existing_loggers’ as ‘False’ in the
          configuration you send.

 -- 函式: logging.config.stopListening ()

     Stops the listening server which was created with a call to *note
     listen(): f08.  This is typically called before calling ‘join()’ on
     the return value from *note listen(): f08.


File: python.info,  Node: Security considerations,  Next: Configuration dictionary schema,  Prev: Configuration functions,  Up: logging config --- 日誌記錄配置

5.16.6.2 Security considerations
................................

The logging configuration functionality tries to offer convenience, and
in part this is done by offering the ability to convert text in
configuration files into Python objects used in logging configuration -
for example, as described in *note User-defined objects: 2c05.  However,
these same mechanisms (importing callables from user-defined modules and
calling them with parameters from the configuration) could be used to
invoke any code you like, and for this reason you should treat
configuration files from untrusted sources with 'extreme caution' and
satisfy yourself that nothing bad can happen if you load them, before
actually loading them.


File: python.info,  Node: Configuration dictionary schema,  Next: Configuration file format,  Prev: Security considerations,  Up: logging config --- 日誌記錄配置

5.16.6.3 Configuration dictionary schema
........................................

Describing a logging configuration requires listing the various objects
to create and the connections between them; for example, you may create
a handler named 'console' and then say that the logger named 'startup'
will send its messages to the 'console' handler.  These objects aren't
limited to those provided by the *note logging: 7b. module because you
might write your own formatter or handler class.  The parameters to
these classes may also need to include external objects such as
‘sys.stderr’.  The syntax for describing these objects and connections
is defined in *note Object connections: 2c07. below.

* Menu:

* Dictionary Schema Details::
* Incremental Configuration::
* Object connections::
* User-defined objects::
* Handler configuration order::
* Access to external objects::
* Access to internal objects::
* Import resolution and custom importers::
* Configuring QueueHandler and QueueListener::


File: python.info,  Node: Dictionary Schema Details,  Next: Incremental Configuration,  Up: Configuration dictionary schema

5.16.6.4 Dictionary Schema Details
..................................

The dictionary passed to *note dictConfig(): 1147. must contain the
following keys:

   * 'version' - to be set to an integer value representing the schema
     version.  The only valid value at present is 1, but having this key
     allows the schema to evolve while still preserving backwards
     compatibility.

All other keys are optional, but if present they will be interpreted as
described below.  In all cases below where a 'configuring dict' is
mentioned, it will be checked for the special ‘'()'’ key to see if a
custom instantiation is required.  If so, the mechanism described in
*note User-defined objects: 2c05. below is used to create an instance;
otherwise, the context is used to determine what to instantiate.

   * 'formatters' - the corresponding value will be a dict in which each
     key is a formatter id and each value is a dict describing how to
     configure the corresponding *note Formatter: 1400. instance.

     The configuring dict is searched for the following optional keys
     which correspond to the arguments passed to create a *note
     Formatter: 1400. object:

        * ‘format’

        * ‘datefmt’

        * ‘style’

        * ‘validate’ (since version >=3.8)

        * ‘defaults’ (since version >=3.12)

     An optional ‘class’ key indicates the name of the formatter's class
     (as a dotted module and class name).  The instantiation arguments
     are as for *note Formatter: 1400, thus this key is most useful for
     instantiating a customised subclass of *note Formatter: 1400.  For
     example, the alternative class might present exception tracebacks
     in an expanded or condensed format.  If your formatter requires
     different or extra configuration keys, you should use *note
     User-defined objects: 2c05.

   * 'filters' - the corresponding value will be a dict in which each
     key is a filter id and each value is a dict describing how to
     configure the corresponding Filter instance.

     The configuring dict is searched for the key ‘name’ (defaulting to
     the empty string) and this is used to construct a *note
     logging.Filter: 1193. instance.

   * 'handlers' - the corresponding value will be a dict in which each
     key is a handler id and each value is a dict describing how to
     configure the corresponding Handler instance.

     The configuring dict is searched for the following keys:

        * ‘class’ (mandatory).  This is the fully qualified name of the
          handler class.

        * ‘level’ (optional).  The level of the handler.

        * ‘formatter’ (optional).  The id of the formatter for this
          handler.

        * ‘filters’ (optional).  A list of ids of the filters for this
          handler.

          在 3.11 版的變更: ‘filters’ can take filter instances in
          addition to ids.

     All 'other' keys are passed through as keyword arguments to the
     handler's constructor.  For example, given the snippet:

          handlers:
            console:
              class : logging.StreamHandler
              formatter: brief
              level   : INFO
              filters: [allow_foo]
              stream  : ext://sys.stdout
            file:
              class : logging.handlers.RotatingFileHandler
              formatter: precise
              filename: logconfig.log
              maxBytes: 1024
              backupCount: 3

     the handler with id ‘console’ is instantiated as a *note
     logging.StreamHandler: 1190, using ‘sys.stdout’ as the underlying
     stream.  The handler with id ‘file’ is instantiated as a *note
     logging.handlers.RotatingFileHandler: 14cb. with the keyword
     arguments ‘filename='logconfig.log', maxBytes=1024, backupCount=3’.

   * 'loggers' - the corresponding value will be a dict in which each
     key is a logger name and each value is a dict describing how to
     configure the corresponding Logger instance.

     The configuring dict is searched for the following keys:

        * ‘level’ (optional).  The level of the logger.

        * ‘propagate’ (optional).  The propagation setting of the
          logger.

        * ‘filters’ (optional).  A list of ids of the filters for this
          logger.

          在 3.11 版的變更: ‘filters’ can take filter instances in
          addition to ids.

        * ‘handlers’ (optional).  A list of ids of the handlers for this
          logger.

     The specified loggers will be configured according to the level,
     propagation, filters and handlers specified.

   * 'root' - this will be the configuration for the root logger.
     Processing of the configuration will be as for any logger, except
     that the ‘propagate’ setting will not be applicable.

   * 'incremental' - whether the configuration is to be interpreted as
     incremental to the existing configuration.  This value defaults to
     ‘False’, which means that the specified configuration replaces the
     existing configuration with the same semantics as used by the
     existing *note fileConfig(): af5. API.

     If the specified value is ‘True’, the configuration is processed as
     described in the section on *note Incremental Configuration: 2c0a.

   * 'disable_existing_loggers' - whether any existing non-root loggers
     are to be disabled.  This setting mirrors the parameter of the same
     name in *note fileConfig(): af5.  If absent, this parameter
     defaults to ‘True’.  This value is ignored if 'incremental' is
     ‘True’.


File: python.info,  Node: Incremental Configuration,  Next: Object connections,  Prev: Dictionary Schema Details,  Up: Configuration dictionary schema

5.16.6.5 Incremental Configuration
..................................

It is difficult to provide complete flexibility for incremental
configuration.  For example, because objects such as filters and
formatters are anonymous, once a configuration is set up, it is not
possible to refer to such anonymous objects when augmenting a
configuration.

Furthermore, there is not a compelling case for arbitrarily altering the
object graph of loggers, handlers, filters, formatters at run-time, once
a configuration is set up; the verbosity of loggers and handlers can be
controlled just by setting levels (and, in the case of loggers,
propagation flags).  Changing the object graph arbitrarily in a safe way
is problematic in a multi-threaded environment; while not impossible,
the benefits are not worth the complexity it adds to the implementation.

Thus, when the ‘incremental’ key of a configuration dict is present and
is ‘True’, the system will completely ignore any ‘formatters’ and
‘filters’ entries, and process only the ‘level’ settings in the
‘handlers’ entries, and the ‘level’ and ‘propagate’ settings in the
‘loggers’ and ‘root’ entries.

Using a value in the configuration dict lets configurations to be sent
over the wire as pickled dicts to a socket listener.  Thus, the logging
verbosity of a long-running application can be altered over time with no
need to stop and restart the application.


File: python.info,  Node: Object connections,  Next: User-defined objects,  Prev: Incremental Configuration,  Up: Configuration dictionary schema

5.16.6.6 Object connections
...........................

The schema describes a set of logging objects - loggers, handlers,
formatters, filters - which are connected to each other in an object
graph.  Thus, the schema needs to represent connections between the
objects.  For example, say that, once configured, a particular logger
has attached to it a particular handler.  For the purposes of this
discussion, we can say that the logger represents the source, and the
handler the destination, of a connection between the two.  Of course in
the configured objects this is represented by the logger holding a
reference to the handler.  In the configuration dict, this is done by
giving each destination object an id which identifies it unambiguously,
and then using the id in the source object's configuration to indicate
that a connection exists between the source and the destination object
with that id.

So, for example, consider the following YAML snippet:

     formatters:
       brief:
         # configuration for formatter with id 'brief' goes here
       precise:
         # configuration for formatter with id 'precise' goes here
     handlers:
       h1: #This is an id
        # configuration of handler with id 'h1' goes here
        formatter: brief
       h2: #This is another id
        # configuration of handler with id 'h2' goes here
        formatter: precise
     loggers:
       foo.bar.baz:
         # other configuration for logger 'foo.bar.baz'
         handlers: [h1, h2]

(Note: YAML used here because it's a little more readable than the
equivalent Python source form for the dictionary.)

The ids for loggers are the logger names which would be used
programmatically to obtain a reference to those loggers, e.g.
‘foo.bar.baz’.  The ids for Formatters and Filters can be any string
value (such as ‘brief’, ‘precise’ above) and they are transient, in that
they are only meaningful for processing the configuration dictionary and
used to determine connections between objects, and are not persisted
anywhere when the configuration call is complete.

The above snippet indicates that logger named ‘foo.bar.baz’ should have
two handlers attached to it, which are described by the handler ids ‘h1’
and ‘h2’.  The formatter for ‘h1’ is that described by id ‘brief’, and
the formatter for ‘h2’ is that described by id ‘precise’.


File: python.info,  Node: User-defined objects,  Next: Handler configuration order,  Prev: Object connections,  Up: Configuration dictionary schema

5.16.6.7 User-defined objects
.............................

The schema supports user-defined objects for handlers, filters and
formatters.  (Loggers do not need to have different types for different
instances, so there is no support in this configuration schema for
user-defined logger classes.)

Objects to be configured are described by dictionaries which detail
their configuration.  In some places, the logging system will be able to
infer from the context how an object is to be instantiated, but when a
user-defined object is to be instantiated, the system will not know how
to do this.  In order to provide complete flexibility for user-defined
object instantiation, the user needs to provide a 'factory' - a callable
which is called with a configuration dictionary and which returns the
instantiated object.  This is signalled by an absolute import path to
the factory being made available under the special key ‘'()'’.  Here's a
concrete example:

     formatters:
       brief:
         format: '%(message)s'
       default:
         format: '%(asctime)s %(levelname)-8s %(name)-15s %(message)s'
         datefmt: '%Y-%m-%d %H:%M:%S'
       custom:
           (): my.package.customFormatterFactory
           bar: baz
           spam: 99.9
           answer: 42

The above YAML snippet defines three formatters.  The first, with id
‘brief’, is a standard *note logging.Formatter: 1400. instance with the
specified format string.  The second, with id ‘default’, has a longer
format and also defines the time format explicitly, and will result in a
*note logging.Formatter: 1400. initialized with those two format
strings.  Shown in Python source form, the ‘brief’ and ‘default’
formatters have configuration sub-dictionaries:

     {
       'format' : '%(message)s'
     }

和：

     {
       'format' : '%(asctime)s %(levelname)-8s %(name)-15s %(message)s',
       'datefmt' : '%Y-%m-%d %H:%M:%S'
     }

respectively, and as these dictionaries do not contain the special key
‘'()'’, the instantiation is inferred from the context: as a result,
standard *note logging.Formatter: 1400. instances are created.  The
configuration sub-dictionary for the third formatter, with id ‘custom’,
is:

     {
       '()' : 'my.package.customFormatterFactory',
       'bar' : 'baz',
       'spam' : 99.9,
       'answer' : 42
     }

and this contains the special key ‘'()'’, which means that user-defined
instantiation is wanted.  In this case, the specified factory callable
will be used.  If it is an actual callable it will be used directly -
otherwise, if you specify a string (as in the example) the actual
callable will be located using normal import mechanisms.  The callable
will be called with the 'remaining' items in the configuration
sub-dictionary as keyword arguments.  In the above example, the
formatter with id ‘custom’ will be assumed to be returned by the call:

     my.package.customFormatterFactory(bar='baz', spam=99.9, answer=42)

     警告: The values for keys such as ‘bar’, ‘spam’ and ‘answer’ in the
     above example should not be configuration dictionaries or
     references such as ‘cfg://foo’ or ‘ext://bar’, because they will
     not be processed by the configuration machinery, but passed to the
     callable as-is.

The key ‘'()'’ has been used as the special key because it is not a
valid keyword parameter name, and so will not clash with the names of
the keyword arguments used in the call.  The ‘'()'’ also serves as a
mnemonic that the corresponding value is a callable.

在 3.11 版的變更: The ‘filters’ member of ‘handlers’ and ‘loggers’ can
take filter instances in addition to ids.

You can also specify a special key ‘'.'’ whose value is a dictionary is
a mapping of attribute names to values.  If found, the specified
attributes will be set on the user-defined object before it is returned.
Thus, with the following configuration:

     {
       '()' : 'my.package.customFormatterFactory',
       'bar' : 'baz',
       'spam' : 99.9,
       'answer' : 42,
       '.' {
         'foo': 'bar',
         'baz': 'bozz'
       }
     }

the returned formatter will have attribute ‘foo’ set to ‘'bar'’ and
attribute ‘baz’ set to ‘'bozz'’.

     警告: The values for attributes such as ‘foo’ and ‘baz’ in the
     above example should not be configuration dictionaries or
     references such as ‘cfg://foo’ or ‘ext://bar’, because they will
     not be processed by the configuration machinery, but set as
     attribute values as-is.


File: python.info,  Node: Handler configuration order,  Next: Access to external objects,  Prev: User-defined objects,  Up: Configuration dictionary schema

5.16.6.8 Handler configuration order
....................................

Handlers are configured in alphabetical order of their keys, and a
configured handler replaces the configuration dictionary in (a working
copy of) the ‘handlers’ dictionary in the schema.  If you use a
construct such as ‘cfg://handlers.foo’, then initially ‘handlers['foo']’
points to the configuration dictionary for the handler named ‘foo’, and
later (once that handler has been configured) it points to the
configured handler instance.  Thus, ‘cfg://handlers.foo’ could resolve
to either a dictionary or a handler instance.  In general, it is wise to
name handlers in a way such that dependent handlers are configured
_after_ any handlers they depend on; that allows something like
‘cfg://handlers.foo’ to be used in configuring a handler that depends on
handler ‘foo’.  If that dependent handler were named ‘bar’, problems
would result, because the configuration of ‘bar’ would be attempted
before that of ‘foo’, and ‘foo’ would not yet have been configured.
However, if the dependent handler were named ‘foobar’, it would be
configured after ‘foo’, with the result that ‘cfg://handlers.foo’ would
resolve to configured handler ‘foo’, and not its configuration
dictionary.


File: python.info,  Node: Access to external objects,  Next: Access to internal objects,  Prev: Handler configuration order,  Up: Configuration dictionary schema

5.16.6.9 Access to external objects
...................................

There are times where a configuration needs to refer to objects external
to the configuration, for example ‘sys.stderr’.  If the configuration
dict is constructed using Python code, this is straightforward, but a
problem arises when the configuration is provided via a text file (e.g.
JSON, YAML). In a text file, there is no standard way to distinguish
‘sys.stderr’ from the literal string ‘'sys.stderr'’.  To facilitate this
distinction, the configuration system looks for certain special prefixes
in string values and treat them specially.  For example, if the literal
string ‘'ext://sys.stderr'’ is provided as a value in the configuration,
then the ‘ext://’ will be stripped off and the remainder of the value
processed using normal import mechanisms.

The handling of such prefixes is done in a way analogous to protocol
handling: there is a generic mechanism to look for prefixes which match
the regular expression ‘^(?P<prefix>[a-z]+)://(?P<suffix>.*)$’ whereby,
if the ‘prefix’ is recognised, the ‘suffix’ is processed in a
prefix-dependent manner and the result of the processing replaces the
string value.  If the prefix is not recognised, then the string value
will be left as-is.


File: python.info,  Node: Access to internal objects,  Next: Import resolution and custom importers,  Prev: Access to external objects,  Up: Configuration dictionary schema

5.16.6.10 Access to internal objects
....................................

As well as external objects, there is sometimes also a need to refer to
objects in the configuration.  This will be done implicitly by the
configuration system for things that it knows about.  For example, the
string value ‘'DEBUG'’ for a ‘level’ in a logger or handler will
automatically be converted to the value ‘logging.DEBUG’, and the
‘handlers’, ‘filters’ and ‘formatter’ entries will take an object id and
resolve to the appropriate destination object.

However, a more generic mechanism is needed for user-defined objects
which are not known to the *note logging: 7b. module.  For example,
consider *note logging.handlers.MemoryHandler: 2c14, which takes a
‘target’ argument which is another handler to delegate to.  Since the
system already knows about this class, then in the configuration, the
given ‘target’ just needs to be the object id of the relevant target
handler, and the system will resolve to the handler from the id.  If,
however, a user defines a ‘my.package.MyHandler’ which has an
‘alternate’ handler, the configuration system would not know that the
‘alternate’ referred to a handler.  To cater for this, a generic
resolution system allows the user to specify:

     handlers:
       file:
         # configuration of file handler goes here

       custom:
         (): my.package.MyHandler
         alternate: cfg://handlers.file

The literal string ‘'cfg://handlers.file'’ will be resolved in an
analogous way to strings with the ‘ext://’ prefix, but looking in the
configuration itself rather than the import namespace.  The mechanism
allows access by dot or by index, in a similar way to that provided by
‘str.format’.  Thus, given the following snippet:

     handlers:
       email:
         class: logging.handlers.SMTPHandler
         mailhost: localhost
         fromaddr: my_app@domain.tld
         toaddrs:
           - support_team@domain.tld
           - dev_team@domain.tld
         subject: Houston, we have a problem.

in the configuration, the string ‘'cfg://handlers'’ would resolve to the
dict with key ‘handlers’, the string ‘'cfg://handlers.email’ would
resolve to the dict with key ‘email’ in the ‘handlers’ dict, and so on.
The string ‘'cfg://handlers.email.toaddrs[1]’ would resolve to
‘'dev_team@domain.tld'’ and the string
‘'cfg://handlers.email.toaddrs[0]'’ would resolve to the value
‘'support_team@domain.tld'’.  The ‘subject’ value could be accessed
using either ‘'cfg://handlers.email.subject'’ or, equivalently,
‘'cfg://handlers.email[subject]'’.  The latter form only needs to be
used if the key contains spaces or non-alphanumeric characters.  Please
note that the characters ‘[’ and ‘]’ are not allowed in the keys.  If an
index value consists only of decimal digits, access will be attempted
using the corresponding integer value, falling back to the string value
if needed.

Given a string ‘cfg://handlers.myhandler.mykey.123’, this will resolve
to ‘config_dict['handlers']['myhandler']['mykey']['123']’.  If the
string is specified as ‘cfg://handlers.myhandler.mykey[123]’, the system
will attempt to retrieve the value from
‘config_dict['handlers']['myhandler']['mykey'][123]’, and fall back to
‘config_dict['handlers']['myhandler']['mykey']['123']’ if that fails.


File: python.info,  Node: Import resolution and custom importers,  Next: Configuring QueueHandler and QueueListener,  Prev: Access to internal objects,  Up: Configuration dictionary schema

5.16.6.11 Import resolution and custom importers
................................................

Import resolution, by default, uses the builtin *note __import__(): 879.
function to do its importing.  You may want to replace this with your
own importing mechanism: if so, you can replace the ‘importer’ attribute
of the ‘DictConfigurator’ or its superclass, the ‘BaseConfigurator’
class.  However, you need to be careful because of the way functions are
accessed from classes via descriptors.  If you are using a Python
callable to do your imports, and you want to define it at class level
rather than instance level, you need to wrap it with *note
staticmethod(): 358.  For example:

     from importlib import import_module
     from logging.config import BaseConfigurator

     BaseConfigurator.importer = staticmethod(import_module)

You don't need to wrap with *note staticmethod(): 358. if you're setting
the import callable on a configurator 'instance'.


File: python.info,  Node: Configuring QueueHandler and QueueListener,  Prev: Import resolution and custom importers,  Up: Configuration dictionary schema

5.16.6.12 Configuring QueueHandler and QueueListener
....................................................

If you want to configure a *note QueueHandler: 16dc, noting that this is
normally used in conjunction with a *note QueueListener: dd2, you can
configure both together.  After the configuration, the ‘QueueListener’
instance will be available as the *note listener: 2c18. attribute of the
created handler, and that in turn will be available to you using *note
getHandlerByName(): 16dd. and passing the name you have used for the
‘QueueHandler’ in your configuration.  The dictionary schema for
configuring the pair is shown in the example YAML snippet below.

     handlers:
       qhand:
         class: logging.handlers.QueueHandler
         queue: my.module.queue_factory
         listener: my.package.CustomListener
         handlers:
           - hand_name_1
           - hand_name_2
           ...

The ‘queue’ and ‘listener’ keys are optional.

If the ‘queue’ key is present, the corresponding value can be one of the
following:

   * An object implementing the *note queue.Queue: 131c. public API. For
     instance, this may be an actual instance of *note queue.Queue:
     131c. or a subclass thereof, or a proxy obtained by *note
     multiprocessing.managers.SyncManager.Queue(): 2c19.

     This is of course only possible if you are constructing or
     modifying the configuration dictionary in code.

   * A string that resolves to a callable which, when called with no
     arguments, returns the *note queue.Queue: 131c. instance to use.
     That callable could be a *note queue.Queue: 131c. subclass or a
     function which returns a suitable queue instance, such as
     ‘my.module.queue_factory()’.

   * A dict with a ‘'()'’ key which is constructed in the usual way as
     discussed in *note User-defined objects: 2c05.  The result of this
     construction should be a *note queue.Queue: 131c. instance.

If the ‘queue’ key is absent, a standard unbounded *note queue.Queue:
131c. instance is created and used.

If the ‘listener’ key is present, the corresponding value can be one of
the following:

   * A subclass of *note logging.handlers.QueueListener: dd2.  This is
     of course only possible if you are constructing or modifying the
     configuration dictionary in code.

   * A string which resolves to a class which is a subclass of
     ‘QueueListener’, such as ‘'my.package.CustomListener'’.

   * A dict with a ‘'()'’ key which is constructed in the usual way as
     discussed in *note User-defined objects: 2c05.  The result of this
     construction should be a callable with the same signature as the
     ‘QueueListener’ initializer.

If the ‘listener’ key is absent, *note logging.handlers.QueueListener:
dd2. is used.

The values under the ‘handlers’ key are the names of other handlers in
the configuration (not shown in the above snippet) which will be passed
to the queue listener.

Any custom queue handler and listener classes will need to be defined
with the same initialization signatures as *note QueueHandler: 16dc. and
*note QueueListener: dd2.

在 3.12 版被加入.


File: python.info,  Node: Configuration file format,  Prev: Configuration dictionary schema,  Up: logging config --- 日誌記錄配置

5.16.6.13 Configuration file format
...................................

The configuration file format understood by *note fileConfig(): af5. is
based on *note configparser: 1b. functionality.  The file must contain
sections called ‘[loggers]’, ‘[handlers]’ and ‘[formatters]’ which
identify by name the entities of each type which are defined in the
file.  For each such entity, there is a separate section which
identifies how that entity is configured.  Thus, for a logger named
‘log01’ in the ‘[loggers]’ section, the relevant configuration details
are held in a section ‘[logger_log01]’.  Similarly, a handler called
‘hand01’ in the ‘[handlers]’ section will have its configuration held in
a section called ‘[handler_hand01]’, while a formatter called ‘form01’
in the ‘[formatters]’ section will have its configuration specified in a
section called ‘[formatter_form01]’.  The root logger configuration must
be specified in a section called ‘[logger_root]’.

     備註: The *note fileConfig(): af5. API is older than the *note
     dictConfig(): 1147. API and does not provide functionality to cover
     certain aspects of logging.  For example, you cannot configure
     *note Filter: 1193. objects, which provide for filtering of
     messages beyond simple integer levels, using *note fileConfig():
     af5.  If you need to have instances of *note Filter: 1193. in your
     logging configuration, you will need to use *note dictConfig():
     1147.  Note that future enhancements to configuration functionality
     will be added to *note dictConfig(): 1147, so it's worth
     considering transitioning to this newer API when it's convenient to
     do so.

Examples of these sections in the file are given below.

     [loggers]
     keys=root,log02,log03,log04,log05,log06,log07

     [handlers]
     keys=hand01,hand02,hand03,hand04,hand05,hand06,hand07,hand08,hand09

     [formatters]
     keys=form01,form02,form03,form04,form05,form06,form07,form08,form09

The root logger must specify a level and a list of handlers.  An example
of a root logger section is given below.

     [logger_root]
     level=NOTSET
     handlers=hand01

The ‘level’ entry can be one of ‘DEBUG, INFO, WARNING, ERROR, CRITICAL’
or ‘NOTSET’.  For the root logger only, ‘NOTSET’ means that all messages
will be logged.  Level values are *note evaluated: 2040. in the context
of the ‘logging’ package's namespace.

The ‘handlers’ entry is a comma-separated list of handler names, which
must appear in the ‘[handlers]’ section.  These names must appear in the
‘[handlers]’ section and have corresponding sections in the
configuration file.

For loggers other than the root logger, some additional information is
required.  This is illustrated by the following example.

     [logger_parser]
     level=DEBUG
     handlers=hand01
     propagate=1
     qualname=compiler.parser

The ‘level’ and ‘handlers’ entries are interpreted as for the root
logger, except that if a non-root logger's level is specified as
‘NOTSET’, the system consults loggers higher up the hierarchy to
determine the effective level of the logger.  The ‘propagate’ entry is
set to 1 to indicate that messages must propagate to handlers higher up
the logger hierarchy from this logger, or 0 to indicate that messages
are 'not' propagated to handlers up the hierarchy.  The ‘qualname’ entry
is the hierarchical channel name of the logger, that is to say the name
used by the application to get the logger.

Sections which specify handler configuration are exemplified by the
following.

     [handler_hand01]
     class=StreamHandler
     level=NOTSET
     formatter=form01
     args=(sys.stdout,)

The ‘class’ entry indicates the handler's class (as determined by *note
eval(): 163. in the ‘logging’ package's namespace).  The ‘level’ is
interpreted as for loggers, and ‘NOTSET’ is taken to mean 'log
everything'.

The ‘formatter’ entry indicates the key name of the formatter for this
handler.  If blank, a default formatter (‘logging._defaultFormatter’) is
used.  If a name is specified, it must appear in the ‘[formatters]’
section and have a corresponding section in the configuration file.

The ‘args’ entry, when *note evaluated: 2040. in the context of the
‘logging’ package's namespace, is the list of arguments to the
constructor for the handler class.  Refer to the constructors for the
relevant handlers, or to the examples below, to see how typical entries
are constructed.  If not provided, it defaults to ‘()’.

The optional ‘kwargs’ entry, when *note evaluated: 2040. in the context
of the ‘logging’ package's namespace, is the keyword argument dict to
the constructor for the handler class.  If not provided, it defaults to
‘{}’.

     [handler_hand02]
     class=FileHandler
     level=DEBUG
     formatter=form02
     args=('python.log', 'w')

     [handler_hand03]
     class=handlers.SocketHandler
     level=INFO
     formatter=form03
     args=('localhost', handlers.DEFAULT_TCP_LOGGING_PORT)

     [handler_hand04]
     class=handlers.DatagramHandler
     level=WARN
     formatter=form04
     args=('localhost', handlers.DEFAULT_UDP_LOGGING_PORT)

     [handler_hand05]
     class=handlers.SysLogHandler
     level=ERROR
     formatter=form05
     args=(('localhost', handlers.SYSLOG_UDP_PORT), handlers.SysLogHandler.LOG_USER)

     [handler_hand06]
     class=handlers.NTEventLogHandler
     level=CRITICAL
     formatter=form06
     args=('Python Application', '', 'Application')

     [handler_hand07]
     class=handlers.SMTPHandler
     level=WARN
     formatter=form07
     args=('localhost', 'from@abc', ['user1@abc', 'user2@xyz'], 'Logger Subject')
     kwargs={'timeout': 10.0}

     [handler_hand08]
     class=handlers.MemoryHandler
     level=NOTSET
     formatter=form08
     target=
     args=(10, ERROR)

     [handler_hand09]
     class=handlers.HTTPHandler
     level=NOTSET
     formatter=form09
     args=('localhost:9022', '/log', 'GET')
     kwargs={'secure': True}

Sections which specify formatter configuration are typified by the
following.

     [formatter_form01]
     format=F1 %(asctime)s %(levelname)s %(message)s %(customfield)s
     datefmt=
     style=%
     validate=True
     defaults={'customfield': 'defaultvalue'}
     class=logging.Formatter

The arguments for the formatter configuration are the same as the keys
in the dictionary schema *note formatters section: 2c09.

The ‘defaults’ entry, when *note evaluated: 2040. in the context of the
‘logging’ package's namespace, is a dictionary of default values for
custom formatting fields.  If not provided, it defaults to ‘None’.

     備註: Due to the use of *note eval(): 163. as described above,
     there are potential security risks which result from using the
     *note listen(): f08. to send and receive configurations via
     sockets.  The risks are limited to where multiple users with no
     mutual trust run code on the same machine; see the *note listen():
     f08. documentation for more information.

也參考
......

*note logging: 7b. 模組

     API reference for the logging module.

*note logging.handlers: 7d. 模組

     Useful handlers included with the logging module.


File: python.info,  Node: logging handlers --- 日誌紀錄處理器,  Next: getpass --- 可攜式密碼輸入工具,  Prev: logging config --- 日誌記錄配置,  Up: 通用作業系統服務

5.16.7 ‘logging.handlers’ -- 日誌紀錄處理器
-------------------------------------------

'原始碼：'Lib/logging/handlers.py(1)

Important
.........

This page contains only reference information.  For tutorials, please
see

   * *note 基礎教學: 118d.

   * *note 進階教學: 118e.

   * *note Logging Cookbook: 118f.

__________________________________________________________________

The following useful handlers are provided in the package.  Note that
three of the handlers (*note StreamHandler: 1190, *note FileHandler:
17a1. and *note NullHandler: 121c.) are actually defined in the *note
logging: 7b. module itself, but have been documented here along with the
other handlers.

* Menu:

* StreamHandler::
* FileHandler::
* NullHandler::
* WatchedFileHandler::
* BaseRotatingHandler::
* RotatingFileHandler::
* TimedRotatingFileHandler::
* SocketHandler::
* DatagramHandler::
* SysLogHandler::
* NTEventLogHandler::
* SMTPHandler::
* MemoryHandler::
* HTTPHandler::
* QueueHandler::
* QueueListener::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/logging/handlers.py


File: python.info,  Node: StreamHandler,  Next: FileHandler,  Up: logging handlers --- 日誌紀錄處理器

5.16.7.1 StreamHandler
......................

The *note StreamHandler: 1190. class, located in the core *note logging:
7b. package, sends logging output to streams such as 'sys.stdout',
'sys.stderr' or any file-like object (or, more precisely, any object
which supports ‘write()’ and ‘flush()’ methods).

 -- 類別: logging.StreamHandler (stream=None)

     Returns a new instance of the *note StreamHandler: 1190. class.  If
     'stream' is specified, the instance will use it for logging output;
     otherwise, 'sys.stderr' will be used.

      -- 方法: emit (record)

          If a formatter is specified, it is used to format the record.
          The record is then written to the stream followed by *note
          terminator: 2c20.  If exception information is present, it is
          formatted using *note traceback.print_exception(): 7f3. and
          appended to the stream.

      -- 方法: flush ()

          Flushes the stream by calling its *note flush(): 2c21. method.
          Note that the ‘close()’ method is inherited from *note
          Handler: 13ff. and so does no output, so an explicit *note
          flush(): 2c21. call may be needed at times.

      -- 方法: setStream (stream)

          Sets the instance's stream to the specified value, if it is
          different.  The old stream is flushed before the new stream is
          set.


          參數: ‘stream’ - The stream that the handler should use.


          回傳: the old stream, if the stream was changed, or ‘None’ if
          it wasn't.

          在 3.7 版被加入.

      -- 屬性: terminator

          String used as the terminator when writing a formatted record
          to a stream.  Default value is ‘'\n'’.

          If you don't want a newline termination, you can set the
          handler instance's ‘terminator’ attribute to the empty string.

          In earlier versions, the terminator was hardcoded as ‘'\n'’.

          在 3.2 版被加入.


File: python.info,  Node: FileHandler,  Next: NullHandler,  Prev: StreamHandler,  Up: logging handlers --- 日誌紀錄處理器

5.16.7.2 FileHandler
....................

The *note FileHandler: 17a1. class, located in the core *note logging:
7b. package, sends logging output to a disk file.  It inherits the
output functionality from *note StreamHandler: 1190.

 -- 類別: logging.FileHandler (filename, mode='a', encoding=None,
          delay=False, errors=None)

     Returns a new instance of the *note FileHandler: 17a1. class.  The
     specified file is opened and used as the stream for logging.  If
     'mode' is not specified, ‘'a'’ is used.  If 'encoding' is not
     ‘None’, it is used to open the file with that encoding.  If 'delay'
     is true, then file opening is deferred until the first call to
     *note emit(): 2c24.  By default, the file grows indefinitely.  If
     'errors' is specified, it's used to determine how encoding errors
     are handled.

     在 3.6 版的變更: As well as string values, *note Path: 20e. objects
     are also accepted for the 'filename' argument.

     在 3.9 版的變更: 新增 'errors' 參數。

      -- 方法: close ()

          Closes the file.

      -- 方法: emit (record)

          Outputs the record to the file.

          Note that if the file was closed due to logging shutdown at
          exit and the file mode is 'w', the record will not be emitted
          (see bpo-42378(1)).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=42378


File: python.info,  Node: NullHandler,  Next: WatchedFileHandler,  Prev: FileHandler,  Up: logging handlers --- 日誌紀錄處理器

5.16.7.3 NullHandler
....................

在 3.1 版被加入.

The *note NullHandler: 121c. class, located in the core *note logging:
7b. package, does not do any formatting or output.  It is essentially a
'no-op' handler for use by library developers.

 -- 類別: logging.NullHandler

     Returns a new instance of the *note NullHandler: 121c. class.

      -- 方法: emit (record)

          This method does nothing.

      -- 方法: handle (record)

          This method does nothing.

      -- 方法: createLock ()

          This method returns ‘None’ for the lock, since there is no
          underlying I/O to which access needs to be serialized.

See *note Configuring Logging for a Library: 2c2b. for more information
on how to use *note NullHandler: 121c.


File: python.info,  Node: WatchedFileHandler,  Next: BaseRotatingHandler,  Prev: NullHandler,  Up: logging handlers --- 日誌紀錄處理器

5.16.7.4 WatchedFileHandler
...........................

The *note WatchedFileHandler: 2c2e. class, located in the *note
logging.handlers: 7d. module, is a ‘FileHandler’ which watches the file
it is logging to.  If the file changes, it is closed and reopened using
the file name.

A file change can happen because of usage of programs such as
'newsyslog' and 'logrotate' which perform log file rotation.  This
handler, intended for use under Unix/Linux, watches the file to see if
it has changed since the last emit.  (A file is deemed to have changed
if its device or inode have changed.)  If the file has changed, the old
file stream is closed, and the file opened to get a new stream.

This handler is not appropriate for use under Windows, because under
Windows open log files cannot be moved or renamed - logging opens the
files with exclusive locks - and so there is no need for such a handler.
Furthermore, 'ST_INO' is not supported under Windows; *note stat(): 448.
always returns zero for this value.

 -- 類別: logging.handlers.WatchedFileHandler (filename, mode='a',
          encoding=None, delay=False, errors=None)

     Returns a new instance of the *note WatchedFileHandler: 2c2e.
     class.  The specified file is opened and used as the stream for
     logging.  If 'mode' is not specified, ‘'a'’ is used.  If 'encoding'
     is not ‘None’, it is used to open the file with that encoding.  If
     'delay' is true, then file opening is deferred until the first call
     to *note emit(): 2c2f.  By default, the file grows indefinitely.
     If 'errors' is provided, it determines how encoding errors are
     handled.

     在 3.6 版的變更: As well as string values, *note Path: 20e. objects
     are also accepted for the 'filename' argument.

     在 3.9 版的變更: 新增 'errors' 參數。

      -- 方法: reopenIfNeeded ()

          Checks to see if the file has changed.  If it has, the
          existing stream is flushed and closed and the file opened
          again, typically as a precursor to outputting the record to
          the file.

          在 3.6 版被加入.

      -- 方法: emit (record)

          Outputs the record to the file, but first calls *note
          reopenIfNeeded(): c5d. to reopen the file if it has changed.


File: python.info,  Node: BaseRotatingHandler,  Next: RotatingFileHandler,  Prev: WatchedFileHandler,  Up: logging handlers --- 日誌紀錄處理器

5.16.7.5 BaseRotatingHandler
............................

The *note BaseRotatingHandler: 2c32. class, located in the *note
logging.handlers: 7d. module, is the base class for the rotating file
handlers, *note RotatingFileHandler: 14cb. and *note
TimedRotatingFileHandler: f04.  You should not need to instantiate this
class, but it has attributes and methods you may need to override.

 -- 類別: logging.handlers.BaseRotatingHandler (filename, mode,
          encoding=None, delay=False, errors=None)

     The parameters are as for ‘FileHandler’.  The attributes are:

      -- 屬性: namer

          If this attribute is set to a callable, the *note
          rotation_filename(): 2c34. method delegates to this callable.
          The parameters passed to the callable are those passed to
          *note rotation_filename(): 2c34.

               備註: The namer function is called quite a few times
               during rollover, so it should be as simple and as fast as
               possible.  It should also return the same output every
               time for a given input, otherwise the rollover behaviour
               may not work as expected.

               It's also worth noting that care should be taken when
               using a namer to preserve certain attributes in the
               filename which are used during rotation.  For example,
               *note RotatingFileHandler: 14cb. expects to have a set of
               log files whose names contain successive integers, so
               that rotation works as expected, and *note
               TimedRotatingFileHandler: f04. deletes old log files
               (based on the ‘backupCount’ parameter passed to the
               handler's initializer) by determining the oldest files to
               delete.  For this to happen, the filenames should be
               sortable using the date/time portion of the filename, and
               a namer needs to respect this.  (If a namer is wanted
               that doesn't respect this scheme, it will need to be used
               in a subclass of *note TimedRotatingFileHandler: f04.
               which overrides the *note getFilesToDelete(): 2c35.
               method to fit in with the custom naming scheme.)

          在 3.3 版被加入.

      -- 屬性: rotator

          If this attribute is set to a callable, the *note rotate():
          2c37. method delegates to this callable.  The parameters
          passed to the callable are those passed to *note rotate():
          2c37.

          在 3.3 版被加入.

      -- 方法: rotation_filename (default_name)

          Modify the filename of a log file when rotating.

          This is provided so that a custom filename can be provided.

          The default implementation calls the 'namer' attribute of the
          handler, if it's callable, passing the default name to it.  If
          the attribute isn't callable (the default is ‘None’), the name
          is returned unchanged.


          參數: ‘default_name’ - The default name for the log file.

          在 3.3 版被加入.

      -- 方法: rotate (source, dest)

          When rotating, rotate the current log.

          The default implementation calls the 'rotator' attribute of
          the handler, if it's callable, passing the source and dest
          arguments to it.  If the attribute isn't callable (the default
          is ‘None’), the source is simply renamed to the destination.


          參數:

             * ‘source’ - The source filename.  This is normally the
               base filename, e.g.  'test.log'.

             * ‘dest’ - The destination filename.  This is normally what
               the source is rotated to, e.g.  'test.log.1'.

          在 3.3 版被加入.

The reason the attributes exist is to save you having to subclass - you
can use the same callables for instances of *note RotatingFileHandler:
14cb. and *note TimedRotatingFileHandler: f04.  If either the namer or
rotator callable raises an exception, this will be handled in the same
way as any other exception during an ‘emit()’ call, i.e.  via the
‘handleError()’ method of the handler.

If you need to make more significant changes to rotation processing, you
can override the methods.

For an example, see *note Using a rotator and namer to customize log
rotation processing: 2c38.


File: python.info,  Node: RotatingFileHandler,  Next: TimedRotatingFileHandler,  Prev: BaseRotatingHandler,  Up: logging handlers --- 日誌紀錄處理器

5.16.7.6 RotatingFileHandler
............................

The *note RotatingFileHandler: 14cb. class, located in the *note
logging.handlers: 7d. module, supports rotation of disk log files.

 -- 類別: logging.handlers.RotatingFileHandler (filename, mode='a',
          maxBytes=0, backupCount=0, encoding=None, delay=False,
          errors=None)

     Returns a new instance of the *note RotatingFileHandler: 14cb.
     class.  The specified file is opened and used as the stream for
     logging.  If 'mode' is not specified, ‘'a'’ is used.  If 'encoding'
     is not ‘None’, it is used to open the file with that encoding.  If
     'delay' is true, then file opening is deferred until the first call
     to *note emit(): 2c3b.  By default, the file grows indefinitely.
     If 'errors' is provided, it determines how encoding errors are
     handled.

     You can use the 'maxBytes' and 'backupCount' values to allow the
     file to 'rollover' at a predetermined size.  When the size is about
     to be exceeded, the file is closed and a new file is silently
     opened for output.  Rollover occurs whenever the current log file
     is nearly 'maxBytes' in length; but if either of 'maxBytes' or
     'backupCount' is zero, rollover never occurs, so you generally want
     to set 'backupCount' to at least 1, and have a non-zero 'maxBytes'.
     When 'backupCount' is non-zero, the system will save old log files
     by appending the extensions '.1', '.2' etc., to the filename.  For
     example, with a 'backupCount' of 5 and a base file name of
     ‘app.log’, you would get ‘app.log’, ‘app.log.1’, ‘app.log.2’, up to
     ‘app.log.5’.  The file being written to is always ‘app.log’.  When
     this file is filled, it is closed and renamed to ‘app.log.1’, and
     if files ‘app.log.1’, ‘app.log.2’, etc.  exist, then they are
     renamed to ‘app.log.2’, ‘app.log.3’ etc.  respectively.

     在 3.6 版的變更: As well as string values, *note Path: 20e. objects
     are also accepted for the 'filename' argument.

     在 3.9 版的變更: 新增 'errors' 參數。

      -- 方法: doRollover ()

          Does a rollover, as described above.

      -- 方法: emit (record)

          Outputs the record to the file, catering for rollover as
          described previously.


File: python.info,  Node: TimedRotatingFileHandler,  Next: SocketHandler,  Prev: RotatingFileHandler,  Up: logging handlers --- 日誌紀錄處理器

5.16.7.7 TimedRotatingFileHandler
.................................

The *note TimedRotatingFileHandler: f04. class, located in the *note
logging.handlers: 7d. module, supports rotation of disk log files at
certain timed intervals.

 -- 類別: logging.handlers.TimedRotatingFileHandler (filename, when='h',
          interval=1, backupCount=0, encoding=None, delay=False,
          utc=False, atTime=None, errors=None)

     Returns a new instance of the *note TimedRotatingFileHandler: f04.
     class.  The specified file is opened and used as the stream for
     logging.  On rotating it also sets the filename suffix.  Rotating
     happens based on the product of 'when' and 'interval'.

     You can use the 'when' to specify the type of 'interval'.  The list
     of possible values is below.  Note that they are not case
     sensitive.

     Value                Type of interval                 If/how 'atTime' is used
                                                           
     ------------------------------------------------------------------------------------
                                                           
     ‘'S'’                Seconds                          Ignored
                                                           
                                                           
     ‘'M'’                Minutes                          Ignored
                                                           
                                                           
     ‘'H'’                Hours                            Ignored
                                                           
                                                           
     ‘'D'’                Days                             Ignored
                                                           
                                                           
     ‘'W0'-'W6'’          Weekday (0=Monday)               Used to compute initial
                                                           rollover time
                                                           
                                                           
     ‘'midnight'’         Roll over at midnight, if        Used to compute initial
                          'atTime' not specified, else     rollover time
                          at time 'atTime'                 
                          

     When using weekday-based rotation, specify 'W0' for Monday, 'W1'
     for Tuesday, and so on up to 'W6' for Sunday.  In this case, the
     value passed for 'interval' isn't used.

     The system will save old log files by appending extensions to the
     filename.  The extensions are date-and-time based, using the
     strftime format ‘%Y-%m-%d_%H-%M-%S’ or a leading portion thereof,
     depending on the rollover interval.

     When computing the next rollover time for the first time (when the
     handler is created), the last modification time of an existing log
     file, or else the current time, is used to compute when the next
     rotation will occur.

     If the 'utc' argument is true, times in UTC will be used; otherwise
     local time is used.

     If 'backupCount' is nonzero, at most 'backupCount' files will be
     kept, and if more would be created when rollover occurs, the oldest
     one is deleted.  The deletion logic uses the interval to determine
     which files to delete, so changing the interval may leave old files
     lying around.

     If 'delay' is true, then file opening is deferred until the first
     call to *note emit(): 2c3f.

     If 'atTime' is not ‘None’, it must be a ‘datetime.time’ instance
     which specifies the time of day when rollover occurs, for the cases
     where rollover is set to happen "at midnight" or "on a particular
     weekday".  Note that in these cases, the 'atTime' value is
     effectively used to compute the 'initial' rollover, and subsequent
     rollovers would be calculated via the normal interval calculation.

     If 'errors' is specified, it's used to determine how encoding
     errors are handled.

          備註: Calculation of the initial rollover time is done when
          the handler is initialised.  Calculation of subsequent
          rollover times is done only when rollover occurs, and rollover
          occurs only when emitting output.  If this is not kept in
          mind, it might lead to some confusion.  For example, if an
          interval of "every minute" is set, that does not mean you will
          always see log files with times (in the filename) separated by
          a minute; if, during application execution, logging output is
          generated more frequently than once a minute, 'then' you can
          expect to see log files with times separated by a minute.  If,
          on the other hand, logging messages are only output once every
          five minutes (say), then there will be gaps in the file times
          corresponding to the minutes where no output (and hence no
          rollover) occurred.

     在 3.4 版的變更: 新增 'atTime' 參數。

     在 3.6 版的變更: As well as string values, *note Path: 20e. objects
     are also accepted for the 'filename' argument.

     在 3.9 版的變更: 新增 'errors' 參數。

      -- 方法: doRollover ()

          Does a rollover, as described above.

      -- 方法: emit (record)

          Outputs the record to the file, catering for rollover as
          described above.

      -- 方法: getFilesToDelete ()

          Returns a list of filenames which should be deleted as part of
          rollover.  These are the absolute paths of the oldest backup
          log files written by the handler.


File: python.info,  Node: SocketHandler,  Next: DatagramHandler,  Prev: TimedRotatingFileHandler,  Up: logging handlers --- 日誌紀錄處理器

5.16.7.8 SocketHandler
......................

The *note SocketHandler: f05. class, located in the *note
logging.handlers: 7d. module, sends logging output to a network socket.
The base class uses a TCP socket.

 -- 類別: logging.handlers.SocketHandler (host, port)

     Returns a new instance of the *note SocketHandler: f05. class
     intended to communicate with a remote machine whose address is
     given by 'host' and 'port'.

     在 3.4 版的變更: If ‘port’ is specified as ‘None’, a Unix domain
     socket is created using the value in ‘host’ - otherwise, a TCP
     socket is created.

      -- 方法: close ()

          Closes the socket.

      -- 方法: emit ()

          Pickles the record's attribute dictionary and writes it to the
          socket in binary format.  If there is an error with the
          socket, silently drops the packet.  If the connection was
          previously lost, re-establishes the connection.  To unpickle
          the record at the receiving end into a *note LogRecord: f89,
          use the *note makeLogRecord(): 2be2. function.

      -- 方法: handleError ()

          Handles an error which has occurred during *note emit(): 2c44.
          The most likely cause is a lost connection.  Closes the socket
          so that we can retry on the next event.

      -- 方法: makeSocket ()

          This is a factory method which allows subclasses to define the
          precise type of socket they want.  The default implementation
          creates a TCP socket (*note socket.SOCK_STREAM: 1286.).

      -- 方法: makePickle (record)

          Pickles the record's attribute dictionary in binary format
          with a length prefix, and returns it ready for transmission
          across the socket.  The details of this operation are
          equivalent to:

               data = pickle.dumps(record_attr_dict, 1)
               datalen = struct.pack('>L', len(data))
               return datalen + data

          Note that pickles aren't completely secure.  If you are
          concerned about security, you may want to override this method
          to implement a more secure mechanism.  For example, you can
          sign pickles using HMAC and then verify them on the receiving
          end, or alternatively you can disable unpickling of global
          objects on the receiving end.

      -- 方法: send (packet)

          Send a pickled byte-string 'packet' to the socket.  The format
          of the sent byte-string is as described in the documentation
          for *note makePickle(): 2c47.

          This function allows for partial sends, which can happen when
          the network is busy.

      -- 方法: createSocket ()

          Tries to create a socket; on failure, uses an exponential
          back-off algorithm.  On initial failure, the handler will drop
          the message it was trying to send.  When subsequent messages
          are handled by the same instance, it will not try connecting
          until some time has passed.  The default parameters are such
          that the initial delay is one second, and if after that delay
          the connection still can't be made, the handler will double
          the delay each time up to a maximum of 30 seconds.

          This behaviour is controlled by the following handler
          attributes:

             * ‘retryStart’ (initial delay, defaulting to 1.0 seconds).

             * ‘retryFactor’ (multiplier, defaulting to 2.0).

             * ‘retryMax’ (maximum delay, defaulting to 30.0 seconds).

          This means that if the remote listener starts up 'after' the
          handler has been used, you could lose messages (since the
          handler won't even attempt a connection until the delay has
          elapsed, but just silently drop messages during the delay
          period).


File: python.info,  Node: DatagramHandler,  Next: SysLogHandler,  Prev: SocketHandler,  Up: logging handlers --- 日誌紀錄處理器

5.16.7.9 DatagramHandler
........................

The *note DatagramHandler: f06. class, located in the *note
logging.handlers: 7d. module, inherits from *note SocketHandler: f05. to
support sending logging messages over UDP sockets.

 -- 類別: logging.handlers.DatagramHandler (host, port)

     Returns a new instance of the *note DatagramHandler: f06. class
     intended to communicate with a remote machine whose address is
     given by 'host' and 'port'.

          備註: As UDP is not a streaming protocol, there is no
          persistent connection between an instance of this handler and
          'host'.  For this reason, when using a network socket, a DNS
          lookup might have to be made each time an event is logged,
          which can introduce some latency into the system.  If this
          affects you, you can do a lookup yourself and initialize this
          handler using the looked-up IP address rather than the
          hostname.

     在 3.4 版的變更: If ‘port’ is specified as ‘None’, a Unix domain
     socket is created using the value in ‘host’ - otherwise, a UDP
     socket is created.

      -- 方法: emit ()

          Pickles the record's attribute dictionary and writes it to the
          socket in binary format.  If there is an error with the
          socket, silently drops the packet.  To unpickle the record at
          the receiving end into a *note LogRecord: f89, use the *note
          makeLogRecord(): 2be2. function.

      -- 方法: makeSocket ()

          The factory method of *note SocketHandler: f05. is here
          overridden to create a UDP socket (*note socket.SOCK_DGRAM:
          1285.).

      -- 方法: send (s)

          Send a pickled byte-string to a socket.  The format of the
          sent byte-string is as described in the documentation for
          *note SocketHandler.makePickle(): 2c47.


File: python.info,  Node: SysLogHandler,  Next: NTEventLogHandler,  Prev: DatagramHandler,  Up: logging handlers --- 日誌紀錄處理器

5.16.7.10 SysLogHandler
.......................

The *note SysLogHandler: 602. class, located in the *note
logging.handlers: 7d. module, supports sending logging messages to a
remote or local Unix syslog.

 -- 類別: logging.handlers.SysLogHandler (address=('localhost',
          SYSLOG_UDP_PORT), facility=LOG_USER,
          socktype=socket.SOCK_DGRAM)

     Returns a new instance of the *note SysLogHandler: 602. class
     intended to communicate with a remote Unix machine whose address is
     given by 'address' in the form of a ‘(host, port)’ tuple.  If
     'address' is not specified, ‘('localhost', 514)’ is used.  The
     address is used to open a socket.  An alternative to providing a
     ‘(host, port)’ tuple is providing an address as a string, for
     example '/dev/log'.  In this case, a Unix domain socket is used to
     send the message to the syslog.  If 'facility' is not specified,
     ‘LOG_USER’ is used.  The type of socket opened depends on the
     'socktype' argument, which defaults to *note socket.SOCK_DGRAM:
     1285. and thus opens a UDP socket.  To open a TCP socket (for use
     with the newer syslog daemons such as rsyslog), specify a value of
     *note socket.SOCK_STREAM: 1286.

     Note that if your server is not listening on UDP port 514, *note
     SysLogHandler: 602. may appear not to work.  In that case, check
     what address you should be using for a domain socket - it's system
     dependent.  For example, on Linux it's usually '/dev/log' but on
     OS/X it's '/var/run/syslog'.  You'll need to check your platform
     and use the appropriate address (you may need to do this check at
     runtime if your application needs to run on several platforms).  On
     Windows, you pretty much have to use the UDP option.

          備註: On macOS 12.x (Monterey), Apple has changed the
          behaviour of their syslog daemon - it no longer listens on a
          domain socket.  Therefore, you cannot expect *note
          SysLogHandler: 602. to work on this system.

          See gh-91070(1) for more information.

     在 3.2 版的變更: 新增 'socktype'。

      -- 方法: close ()

          Closes the socket to the remote host.

      -- 方法: createSocket ()

          Tries to create a socket and, if it's not a datagram socket,
          connect it to the other end.  This method is called during
          handler initialization, but it's not regarded as an error if
          the other end isn't listening at this point - the method will
          be called again when emitting an event, if there is no socket
          at that point.

          在 3.11 版被加入.

      -- 方法: emit (record)

          The record is formatted, and then sent to the syslog server.
          If exception information is present, it is 'not' sent to the
          server.

          在 3.2.1 版的變更: (See: bpo-12168(2).)  In earlier versions,
          the message sent to the syslog daemons was always terminated
          with a NUL byte, because early versions of these daemons
          expected a NUL terminated message - even though it's not in
          the relevant specification ( RFC 5424(3)).  More recent
          versions of these daemons don't expect the NUL byte but strip
          it off if it's there, and even more recent daemons (which
          adhere more closely to RFC 5424) pass the NUL byte on as part
          of the message.

          To enable easier handling of syslog messages in the face of
          all these differing daemon behaviours, the appending of the
          NUL byte has been made configurable, through the use of a
          class-level attribute, ‘append_nul’.  This defaults to ‘True’
          (preserving the existing behaviour) but can be set to ‘False’
          on a ‘SysLogHandler’ instance in order for that instance to
          'not' append the NUL terminator.

          在 3.3 版的變更: (See: bpo-12419(4).)  In earlier versions,
          there was no facility for an "ident" or "tag" prefix to
          identify the source of the message.  This can now be specified
          using a class-level attribute, defaulting to ‘""’ to preserve
          existing behaviour, but which can be overridden on a
          ‘SysLogHandler’ instance in order for that instance to prepend
          the ident to every message handled.  Note that the provided
          ident must be text, not bytes, and is prepended to the message
          exactly as is.

      -- 方法: encodePriority (facility, priority)

          Encodes the facility and priority into an integer.  You can
          pass in strings or integers - if strings are passed, internal
          mapping dictionaries are used to convert them to integers.

          The symbolic ‘LOG_’ values are defined in *note SysLogHandler:
          602. and mirror the values defined in the ‘sys/syslog.h’
          header file.

          'Priorities'

          Name (string)                  Symbolic value
                                         
          ---------------------------------------------------
                                         
          ‘alert’                        LOG_ALERT
                                         
                                         
          ‘crit’ 或 ‘critical’           LOG_CRIT
                                         
                                         
          ‘debug’                        LOG_DEBUG
                                         
                                         
          ‘emerg’ 或 ‘panic’             LOG_EMERG
                                         
                                         
          ‘err’ 或 ‘error’               LOG_ERR
                                         
                                         
          ‘info’                         LOG_INFO
                                         
                                         
          ‘notice’                       LOG_NOTICE
                                         
                                         
          ‘warn’ 或 ‘warning’            LOG_WARNING
                                         

          'Facilities'

          Name (string)       Symbolic value
                              
          ----------------------------------------
                              
          ‘auth’              LOG_AUTH
                              
                              
          ‘authpriv’          LOG_AUTHPRIV
                              
                              
          ‘cron’              LOG_CRON
                              
                              
          ‘daemon’            LOG_DAEMON
                              
                              
          ‘ftp’               LOG_FTP
                              
                              
          ‘kern’              LOG_KERN
                              
                              
          ‘lpr’               LOG_LPR
                              
                              
          ‘mail’              LOG_MAIL
                              
                              
          ‘news’              LOG_NEWS
                              
                              
          ‘syslog’            LOG_SYSLOG
                              
                              
          ‘user’              LOG_USER
                              
                              
          ‘uucp’              LOG_UUCP
                              
                              
          ‘local0’            LOG_LOCAL0
                              
                              
          ‘local1’            LOG_LOCAL1
                              
                              
          ‘local2’            LOG_LOCAL2
                              
                              
          ‘local3’            LOG_LOCAL3
                              
                              
          ‘local4’            LOG_LOCAL4
                              
                              
          ‘local5’            LOG_LOCAL5
                              
                              
          ‘local6’            LOG_LOCAL6
                              
                              
          ‘local7’            LOG_LOCAL7
                              

      -- 方法: mapPriority (levelname)

          Maps a logging level name to a syslog priority name.  You may
          need to override this if you are using custom levels, or if
          the default algorithm is not suitable for your needs.  The
          default algorithm maps ‘DEBUG’, ‘INFO’, ‘WARNING’, ‘ERROR’ and
          ‘CRITICAL’ to the equivalent syslog names, and all other level
          names to 'warning'.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/91070

   (2) https://bugs.python.org/issue?@action=redirect&bpo=12168

   (3) https://datatracker.ietf.org/doc/html/rfc5424.html

   (4) https://bugs.python.org/issue?@action=redirect&bpo=12419


File: python.info,  Node: NTEventLogHandler,  Next: SMTPHandler,  Prev: SysLogHandler,  Up: logging handlers --- 日誌紀錄處理器

5.16.7.11 NTEventLogHandler
...........................

The *note NTEventLogHandler: 2c56. class, located in the *note
logging.handlers: 7d. module, supports sending logging messages to a
local Windows NT, Windows 2000 or Windows XP event log.  Before you can
use it, you need Mark Hammond's Win32 extensions for Python installed.

 -- 類別: logging.handlers.NTEventLogHandler (appname, dllname=None,
          logtype='Application')

     Returns a new instance of the *note NTEventLogHandler: 2c56. class.
     The 'appname' is used to define the application name as it appears
     in the event log.  An appropriate registry entry is created using
     this name.  The 'dllname' should give the fully qualified pathname
     of a .dll or .exe which contains message definitions to hold in the
     log (if not specified, ‘'win32service.pyd'’ is used - this is
     installed with the Win32 extensions and contains some basic
     placeholder message definitions.  Note that use of these
     placeholders will make your event logs big, as the entire message
     source is held in the log.  If you want slimmer logs, you have to
     pass in the name of your own .dll or .exe which contains the
     message definitions you want to use in the event log).  The
     'logtype' is one of ‘'Application'’, ‘'System'’ or ‘'Security'’,
     and defaults to ‘'Application'’.

      -- 方法: close ()

          At this point, you can remove the application name from the
          registry as a source of event log entries.  However, if you do
          this, you will not be able to see the events as you intended
          in the Event Log Viewer - it needs to be able to access the
          registry to get the .dll name.  The current version does not
          do this.

      -- 方法: emit (record)

          Determines the message ID, event category and event type, and
          then logs the message in the NT event log.

      -- 方法: getEventCategory (record)

          Returns the event category for the record.  Override this if
          you want to specify your own categories.  This version returns
          0.

      -- 方法: getEventType (record)

          Returns the event type for the record.  Override this if you
          want to specify your own types.  This version does a mapping
          using the handler's typemap attribute, which is set up in
          ‘__init__()’ to a dictionary which contains mappings for
          ‘DEBUG’, ‘INFO’, ‘WARNING’, ‘ERROR’ and ‘CRITICAL’.  If you
          are using your own levels, you will either need to override
          this method or place a suitable dictionary in the handler's
          'typemap' attribute.

      -- 方法: getMessageID (record)

          Returns the message ID for the record.  If you are using your
          own messages, you could do this by having the 'msg' passed to
          the logger being an ID rather than a format string.  Then, in
          here, you could use a dictionary lookup to get the message ID.
          This version returns 1, which is the base message ID in
          ‘win32service.pyd’.


File: python.info,  Node: SMTPHandler,  Next: MemoryHandler,  Prev: NTEventLogHandler,  Up: logging handlers --- 日誌紀錄處理器

5.16.7.12 SMTPHandler
.....................

The *note SMTPHandler: 2c5e. class, located in the *note
logging.handlers: 7d. module, supports sending logging messages to an
email address via SMTP.

 -- 類別: logging.handlers.SMTPHandler (mailhost, fromaddr, toaddrs,
          subject, credentials=None, secure=None, timeout=1.0)

     Returns a new instance of the *note SMTPHandler: 2c5e. class.  The
     instance is initialized with the from and to addresses and subject
     line of the email.  The 'toaddrs' should be a list of strings.  To
     specify a non-standard SMTP port, use the (host, port) tuple format
     for the 'mailhost' argument.  If you use a string, the standard
     SMTP port is used.  If your SMTP server requires authentication,
     you can specify a (username, password) tuple for the 'credentials'
     argument.

     To specify the use of a secure protocol (TLS), pass in a tuple to
     the 'secure' argument.  This will only be used when authentication
     credentials are supplied.  The tuple should be either an empty
     tuple, or a single-value tuple with the name of a keyfile, or a
     2-value tuple with the names of the keyfile and certificate file.
     (This tuple is passed to the *note smtplib.SMTP.starttls(): 10d1.
     method.)

     A timeout can be specified for communication with the SMTP server
     using the 'timeout' argument.

     在 3.3 版的變更: 新增 'timeout' 參數。

      -- 方法: emit (record)

          Formats the record and sends it to the specified addressees.

      -- 方法: getSubject (record)

          If you want to specify a subject line which is
          record-dependent, override this method.


File: python.info,  Node: MemoryHandler,  Next: HTTPHandler,  Prev: SMTPHandler,  Up: logging handlers --- 日誌紀錄處理器

5.16.7.13 MemoryHandler
.......................

The *note MemoryHandler: 2c14. class, located in the *note
logging.handlers: 7d. module, supports buffering of logging records in
memory, periodically flushing them to a 'target' handler.  Flushing
occurs whenever the buffer is full, or when an event of a certain
severity or greater is seen.

*note MemoryHandler: 2c14. is a subclass of the more general *note
BufferingHandler: 2c63, which is an abstract class.  This buffers
logging records in memory.  Whenever each record is added to the buffer,
a check is made by calling ‘shouldFlush()’ to see if the buffer should
be flushed.  If it should, then ‘flush()’ is expected to do the
flushing.

 -- 類別: logging.handlers.BufferingHandler (capacity)

     Initializes the handler with a buffer of the specified capacity.
     Here, 'capacity' means the number of logging records buffered.

      -- 方法: emit (record)

          Append the record to the buffer.  If *note shouldFlush():
          2c65. returns true, call *note flush(): 2c66. to process the
          buffer.

      -- 方法: flush ()

          For a *note BufferingHandler: 2c63. instance, flushing means
          that it sets the buffer to an empty list.  This method can be
          overwritten to implement more useful flushing behavior.

      -- 方法: shouldFlush (record)

          Return ‘True’ if the buffer is up to capacity.  This method
          can be overridden to implement custom flushing strategies.

 -- 類別: logging.handlers.MemoryHandler (capacity, flushLevel=ERROR,
          target=None, flushOnClose=True)

     Returns a new instance of the *note MemoryHandler: 2c14. class.
     The instance is initialized with a buffer size of 'capacity'
     (number of records buffered).  If 'flushLevel' is not specified,
     ‘ERROR’ is used.  If no 'target' is specified, the target will need
     to be set using *note setTarget(): 2c67. before this handler does
     anything useful.  If 'flushOnClose' is specified as ‘False’, then
     the buffer is 'not' flushed when the handler is closed.  If not
     specified or specified as ‘True’, the previous behaviour of
     flushing the buffer will occur when the handler is closed.

     在 3.6 版的變更: 新增 'flushOnClose' 參數。

      -- 方法: close ()

          Calls *note flush(): 2c69, sets the target to ‘None’ and
          clears the buffer.

      -- 方法: flush ()

          For a *note MemoryHandler: 2c14. instance, flushing means just
          sending the buffered records to the target, if there is one.
          The buffer is also cleared when buffered records are sent to
          the target.  Override if you want different behavior.

      -- 方法: setTarget (target)

          Sets the target handler for this handler.

      -- 方法: shouldFlush (record)

          Checks for buffer full or a record at the 'flushLevel' or
          higher.


File: python.info,  Node: HTTPHandler,  Next: QueueHandler,  Prev: MemoryHandler,  Up: logging handlers --- 日誌紀錄處理器

5.16.7.14 HTTPHandler
.....................

The *note HTTPHandler: dd1. class, located in the *note
logging.handlers: 7d. module, supports sending logging messages to a web
server, using either ‘GET’ or ‘POST’ semantics.

 -- 類別: logging.handlers.HTTPHandler (host, url, method='GET',
          secure=False, credentials=None, context=None)

     Returns a new instance of the *note HTTPHandler: dd1. class.  The
     'host' can be of the form ‘host:port’, should you need to use a
     specific port number.  If no 'method' is specified, ‘GET’ is used.
     If 'secure' is true, a HTTPS connection will be used.  The
     'context' parameter may be set to a *note ssl.SSLContext: 276.
     instance to configure the SSL settings used for the HTTPS
     connection.  If 'credentials' is specified, it should be a 2-tuple
     consisting of userid and password, which will be placed in a HTTP
     'Authorization' header using Basic authentication.  If you specify
     credentials, you should also specify secure=True so that your
     userid and password are not passed in cleartext across the wire.

     在 3.5 版的變更: 新增 'context' 參數。

      -- 方法: mapLogRecord (record)

          Provides a dictionary, based on ‘record’, which is to be
          URL-encoded and sent to the web server.  The default
          implementation just returns ‘record.__dict__’.  This method
          can be overridden if e.g.  only a subset of *note LogRecord:
          f89. is to be sent to the web server, or if more specific
          customization of what's sent to the server is required.

      -- 方法: emit (record)

          Sends the record to the web server as a URL-encoded
          dictionary.  The *note mapLogRecord(): 2c6d. method is used to
          convert the record to the dictionary to be sent.

          備註: Since preparing a record for sending it to a web server
          is not the same as a generic formatting operation, using *note
          setFormatter(): 2bc5. to specify a *note Formatter: 1400. for
          a *note HTTPHandler: dd1. has no effect.  Instead of calling
          *note format(): 2bcf, this handler calls *note mapLogRecord():
          2c6d. and then *note urllib.parse.urlencode(): e37. to encode
          the dictionary in a form suitable for sending to a web server.


File: python.info,  Node: QueueHandler,  Next: QueueListener,  Prev: HTTPHandler,  Up: logging handlers --- 日誌紀錄處理器

5.16.7.15 QueueHandler
......................

在 3.2 版被加入.

The *note QueueHandler: 16dc. class, located in the *note
logging.handlers: 7d. module, supports sending logging messages to a
queue, such as those implemented in the *note queue: a4. or *note
multiprocessing: 86. modules.

Along with the *note QueueListener: dd2. class, *note QueueHandler:
16dc. can be used to let handlers do their work on a separate thread
from the one which does the logging.  This is important in web
applications and also other service applications where threads servicing
clients need to respond as quickly as possible, while any potentially
slow operations (such as sending an email via *note SMTPHandler: 2c5e.)
are done on a separate thread.

 -- 類別: logging.handlers.QueueHandler (queue)

     Returns a new instance of the *note QueueHandler: 16dc. class.  The
     instance is initialized with the queue to send messages to.  The
     'queue' can be any queue-like object; it's used as-is by the *note
     enqueue(): 2c71. method, which needs to know how to send messages
     to it.  The queue is not 'required' to have the task tracking API,
     which means that you can use *note SimpleQueue: b0e. instances for
     'queue'.

          備註: If you are using *note multiprocessing: 86, you should
          avoid using *note SimpleQueue: b0e. and instead use *note
          multiprocessing.Queue: 1701.

      -- 方法: emit (record)

          Enqueues the result of preparing the LogRecord.  Should an
          exception occur (e.g.  because a bounded queue has filled up),
          the *note handleError(): 2bcd. method is called to handle the
          error.  This can result in the record silently being dropped
          (if *note logging.raiseExceptions: 1191. is ‘False’) or a
          message printed to ‘sys.stderr’ (if *note
          logging.raiseExceptions: 1191. is ‘True’).

      -- 方法: prepare (record)

          Prepares a record for queuing.  The object returned by this
          method is enqueued.

          The base implementation formats the record to merge the
          message, arguments, exception and stack information, if
          present.  It also removes unpickleable items from the record
          in-place.  Specifically, it overwrites the record's ‘msg’ and
          ‘message’ attributes with the merged message (obtained by
          calling the handler's *note format(): 5c3. method), and sets
          the ‘args’, ‘exc_info’ and ‘exc_text’ attributes to ‘None’.

          You might want to override this method if you want to convert
          the record to a dict or JSON string, or send a modified copy
          of the record while leaving the original intact.

               備註: The base implementation formats the message with
               arguments, sets the ‘message’ and ‘msg’ attributes to the
               formatted message and sets the ‘args’ and ‘exc_text’
               attributes to ‘None’ to allow pickling and to prevent
               further attempts at formatting.  This means that a
               handler on the *note QueueListener: dd2. side won't have
               the information to do custom formatting, e.g.  of
               exceptions.  You may wish to subclass ‘QueueHandler’ and
               override this method to e.g.  avoid setting ‘exc_text’ to
               ‘None’.  Note that the ‘message’ / ‘msg’ / ‘args’ changes
               are related to ensuring the record is pickleable, and you
               might or might not be able to avoid doing that depending
               on whether your ‘args’ are pickleable.  (Note that you
               may have to consider not only your own code but also code
               in any libraries that you use.)

      -- 方法: enqueue (record)

          Enqueues the record on the queue using ‘put_nowait()’; you may
          want to override this if you want to use blocking behaviour,
          or a timeout, or a customized queue implementation.

      -- 屬性: listener

          When created via configuration using *note dictConfig(): 1147,
          this attribute will contain a *note QueueListener: dd2.
          instance for use with this handler.  Otherwise, it will be
          ‘None’.

          在 3.12 版被加入.


File: python.info,  Node: QueueListener,  Prev: QueueHandler,  Up: logging handlers --- 日誌紀錄處理器

5.16.7.16 QueueListener
.......................

在 3.2 版被加入.

The *note QueueListener: dd2. class, located in the *note
logging.handlers: 7d. module, supports receiving logging messages from a
queue, such as those implemented in the *note queue: a4. or *note
multiprocessing: 86. modules.  The messages are received from a queue in
an internal thread and passed, on the same thread, to one or more
handlers for processing.  While *note QueueListener: dd2. is not itself
a handler, it is documented here because it works hand-in-hand with
*note QueueHandler: 16dc.

Along with the *note QueueHandler: 16dc. class, *note QueueListener:
dd2. can be used to let handlers do their work on a separate thread from
the one which does the logging.  This is important in web applications
and also other service applications where threads servicing clients need
to respond as quickly as possible, while any potentially slow operations
(such as sending an email via *note SMTPHandler: 2c5e.) are done on a
separate thread.

 -- 類別: logging.handlers.QueueListener (queue, *handlers,
          respect_handler_level=False)

     Returns a new instance of the *note QueueListener: dd2. class.  The
     instance is initialized with the queue to send messages to and a
     list of handlers which will handle entries placed on the queue.
     The queue can be any queue-like object; it's passed as-is to the
     *note dequeue(): 2c76. method, which needs to know how to get
     messages from it.  The queue is not 'required' to have the task
     tracking API (though it's used if available), which means that you
     can use *note SimpleQueue: b0e. instances for 'queue'.

          備註: If you are using *note multiprocessing: 86, you should
          avoid using *note SimpleQueue: b0e. and instead use *note
          multiprocessing.Queue: 1701.

     If ‘respect_handler_level’ is ‘True’, a handler's level is
     respected (compared with the level for the message) when deciding
     whether to pass messages to that handler; otherwise, the behaviour
     is as in previous Python versions - to always pass each message to
     each handler.

     在 3.5 版的變更: 新增 ‘respect_handler_level’ 引數。

      -- 方法: dequeue (block)

          Dequeues a record and return it, optionally blocking.

          The base implementation uses ‘get()’.  You may want to
          override this method if you want to use timeouts or work with
          custom queue implementations.

      -- 方法: prepare (record)

          Prepare a record for handling.

          This implementation just returns the passed-in record.  You
          may want to override this method if you need to do any custom
          marshalling or manipulation of the record before passing it to
          the handlers.

      -- 方法: handle (record)

          Handle a record.

          This just loops through the handlers offering them the record
          to handle.  The actual object passed to the handlers is that
          which is returned from *note prepare(): 2c77.

      -- 方法: start ()

          Starts the listener.

          This starts up a background thread to monitor the queue for
          LogRecords to process.

      -- 方法: stop ()

          Stops the listener.

          This asks the thread to terminate, and then waits for it to do
          so.  Note that if you don't call this before your application
          exits, there may be some records still left on the queue,
          which won't be processed.

      -- 方法: enqueue_sentinel ()

          Writes a sentinel to the queue to tell the listener to quit.
          This implementation uses ‘put_nowait()’.  You may want to
          override this method if you want to use timeouts or work with
          custom queue implementations.

          在 3.3 版被加入.

也參考
......

*note logging: 7b. 模組

     API reference for the logging module.

*note logging.config: 7c. 模組

     Configuration API for the logging module.


File: python.info,  Node: getpass --- 可攜式密碼輸入工具,  Next: curses --- 字元儲存格顯示的終端處理,  Prev: logging handlers --- 日誌紀錄處理器,  Up: 通用作業系統服務

5.16.8 ‘getpass’ -- 可攜式密碼輸入工具
--------------------------------------

'原始碼：'Lib/getpass.py(1)

__________________________________________________________________

*note Availability: 1c56.: not WASI.

This module does not work or is not available on WebAssembly.  See *note
WebAssembly 平台: 16e6. for more information.

*note getpass: 58. 模組 (module) 提供了兩個函式：

 -- 函式: getpass.getpass (prompt='Password: ', stream=None)

     提示使用者輸入一個密碼且不會有回音 (echo)。使用者會看到字串
     'prompt' 作為提示，其預設值為 ‘'Password: '’。在 Unix 上，如有必要
     的話會使用替換錯誤處理函式 (replace error handler) 寫入到類檔案物件
     (file-like object) 'stream'中。'stream' 預設為主控終端機
     (controlling terminal) (‘/dev/tty’)，如果不可用則為 ‘sys.stderr’ (此
     引數在 Windows 上會被忽略)。

     如果無回音輸入 (echo-free input) 無法使用則 getpass() 將回退為印出
     一條警告訊息到 'stream'，並從 ‘sys.stdin’ 讀取且同時發出 *note
     GetPassWarning: 2c7f.。

          備註: 如果你從 IDLE 內部呼叫 getpass，輸入可能會在你啟動 IDLE
          的終端機中完成，而非在 IDLE 視窗中。

 -- 例外: getpass.GetPassWarning

     當密碼輸入可能被回音時會發出的 *note UserWarning: 2192. 子類別。

 -- 函式: getpass.getuser ()

     回傳使用者的"登入名稱"。

     This function checks the environment variables ‘LOGNAME’, ‘USER’,
     ‘LNAME’ and ‘USERNAME’, in order, and returns the value of the
     first one which is set to a non-empty string.  If none are set, the
     login name from the password database is returned on systems which
     support the *note pwd: a0. module, otherwise, an *note OSError:
     350. is raised.

     大部分情況下，此函式應該要比 *note os.getlogin(): 29fa. 優先使用。

     在 3.13 版的變更: Previously, various exceptions beyond just *note
     OSError: 350. were raised.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/getpass.py


File: python.info,  Node: curses --- 字元儲存格顯示的終端處理,  Next: curses textpad --- Text input widget for curses programs,  Prev: getpass --- 可攜式密碼輸入工具,  Up: 通用作業系統服務

5.16.9 ‘curses’ -- 字元儲存格顯示的終端處理
-------------------------------------------

'原始碼：'Lib/curses(1)

__________________________________________________________________

The *note curses: 23. module provides an interface to the curses
library, the de-facto standard for portable advanced terminal handling.

While curses is most widely used in the Unix environment, versions are
available for Windows, DOS, and possibly other systems as well.  This
extension module is designed to match the API of ncurses, an open-source
curses library hosted on Linux and the BSD variants of Unix.

*note Availability: 1c56.: not WASI, not iOS.

This module does not work or is not available on WebAssembly platforms,
or on iOS. See *note WebAssembly 平台: 16e6. for more information on
WASM availability; see *note iOS: 1d56. for more information on iOS
availability.

     備註: Whenever the documentation mentions a 'character' it can be
     specified as an integer, a one-character Unicode string or a
     one-byte byte string.

     Whenever the documentation mentions a 'character string' it can be
     specified as a Unicode string or a byte string.

也參考
......

*note curses.ascii: 24. 模組

     Utilities for working with ASCII characters, regardless of your
     locale settings.

*note curses.panel: 25. 模組

     A panel stack extension that adds depth to curses windows.

*note curses.textpad: 26. 模組

     Editable text widget for curses supporting ‘Emacs’-like bindings.

*note Curses Programming with Python: 2c82.

     Tutorial material on using curses with Python, by Andrew Kuchling
     and Eric Raymond.

* Menu:

* 函式: 函式<5>.
* Window Objects::
* Constants::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/curses


File: python.info,  Node: 函式<5>,  Next: Window Objects,  Up: curses --- 字元儲存格顯示的終端處理

5.16.9.1 函式
.............

The module *note curses: 23. defines the following exception:

 -- 例外: curses.error

     Exception raised when a curses library function returns an error.

     備註: Whenever 'x' or 'y' arguments to a function or a method are
     optional, they default to the current cursor location.  Whenever
     'attr' is optional, it defaults to *note A_NORMAL: 2c86.

The module *note curses: 23. defines the following functions:

 -- 函式: curses.baudrate ()

     Return the output speed of the terminal in bits per second.  On
     software terminal emulators it will have a fixed high value.
     Included for historical reasons; in former times, it was used to
     write output loops for time delays and occasionally to change
     interfaces depending on the line speed.

 -- 函式: curses.beep ()

     Emit a short attention sound.

 -- 函式: curses.can_change_color ()

     Return ‘True’ or ‘False’, depending on whether the programmer can
     change the colors displayed by the terminal.

 -- 函式: curses.cbreak ()

     Enter cbreak mode.  In cbreak mode (sometimes called "rare" mode)
     normal tty line buffering is turned off and characters are
     available to be read one by one.  However, unlike raw mode, special
     characters (interrupt, quit, suspend, and flow control) retain
     their effects on the tty driver and calling program.  Calling first
     *note raw(): 2c8b. then *note cbreak(): 2c8a. leaves the terminal
     in cbreak mode.

 -- 函式: curses.color_content (color_number)

     Return the intensity of the red, green, and blue (RGB) components
     in the color 'color_number', which must be between ‘0’ and ‘COLORS
     - 1’.  Return a 3-tuple, containing the R,G,B values for the given
     color, which will be between ‘0’ (no component) and ‘1000’ (maximum
     amount of component).

 -- 函式: curses.color_pair (pair_number)

     Return the attribute value for displaying text in the specified
     color pair.  Only the first 256 color pairs are supported.  This
     attribute value can be combined with *note A_STANDOUT: 2c8d, *note
     A_REVERSE: 2c8e, and the other ‘A_*’ attributes.  *note
     pair_number(): 2c8f. is the counterpart to this function.

 -- 函式: curses.curs_set (visibility)

     Set the cursor state.  'visibility' can be set to ‘0’, ‘1’, or ‘2’,
     for invisible, normal, or very visible.  If the terminal supports
     the visibility requested, return the previous cursor state;
     otherwise raise an exception.  On many terminals, the "visible"
     mode is an underline cursor and the "very visible" mode is a block
     cursor.

 -- 函式: curses.def_prog_mode ()

     Save the current terminal mode as the "program" mode, the mode when
     the running program is using curses.  (Its counterpart is the
     "shell" mode, for when the program is not in curses.)  Subsequent
     calls to *note reset_prog_mode(): 2c92. will restore this mode.

 -- 函式: curses.def_shell_mode ()

     Save the current terminal mode as the "shell" mode, the mode when
     the running program is not using curses.  (Its counterpart is the
     "program" mode, when the program is using curses capabilities.)
     Subsequent calls to *note reset_shell_mode(): 2c94. will restore
     this mode.

 -- 函式: curses.delay_output (ms)

     Insert an 'ms' millisecond pause in output.

 -- 函式: curses.doupdate ()

     Update the physical screen.  The curses library keeps two data
     structures, one representing the current physical screen contents
     and a virtual screen representing the desired next state.  The
     *note doupdate(): 2c96. ground updates the physical screen to match
     the virtual screen.

     The virtual screen may be updated by a *note noutrefresh(): 2c97.
     call after write operations such as *note addstr(): 2c98. have been
     performed on a window.  The normal *note refresh(): 2c99. call is
     simply ‘noutrefresh()’ followed by ‘doupdate()’; if you have to
     update multiple windows, you can speed performance and perhaps
     reduce screen flicker by issuing ‘noutrefresh()’ calls on all
     windows, followed by a single ‘doupdate()’.

 -- 函式: curses.echo ()

     Enter echo mode.  In echo mode, each character input is echoed to
     the screen as it is entered.

 -- 函式: curses.endwin ()

     De-initialize the library, and return terminal to normal status.

 -- 函式: curses.erasechar ()

     Return the user's current erase character as a one-byte bytes
     object.  Under Unix operating systems this is a property of the
     controlling tty of the curses program, and is not set by the curses
     library itself.

 -- 函式: curses.filter ()

     The *note filter(): 2c9d. routine, if used, must be called before
     *note initscr(): 2c9e. is called.  The effect is that, during those
     calls, ‘LINES’ is set to ‘1’; the capabilities ‘clear’, ‘cup’,
     ‘cud’, ‘cud1’, ‘cuu1’, ‘cuu’, ‘vpa’ are disabled; and the ‘home’
     string is set to the value of ‘cr’.  The effect is that the cursor
     is confined to the current line, and so are screen updates.  This
     may be used for enabling character-at-a-time line editing without
     touching the rest of the screen.

 -- 函式: curses.flash ()

     Flash the screen.  That is, change it to reverse-video and then
     change it back in a short interval.  Some people prefer such as
     'visible bell' to the audible attention signal produced by *note
     beep(): 2c88.

 -- 函式: curses.flushinp ()

     Flush all input buffers.  This throws away any typeahead that has
     been typed by the user and has not yet been processed by the
     program.

 -- 函式: curses.getmouse ()

     After *note getch(): 2ca2. returns *note KEY_MOUSE: 2ca3. to signal
     a mouse event, this method should be called to retrieve the queued
     mouse event, represented as a 5-tuple ‘(id, x, y, z, bstate)’.
     'id' is an ID value used to distinguish multiple devices, and 'x',
     'y', 'z' are the event's coordinates.  ('z' is currently unused.)
     'bstate' is an integer value whose bits will be set to indicate the
     type of event, and will be the bitwise OR of one or more of the
     following constants, where 'n' is the button number from 1 to 5:
     *note BUTTONn_PRESSED: 2ca4, *note BUTTONn_RELEASED: 2ca5, *note
     BUTTONn_CLICKED: 2ca6, *note BUTTONn_DOUBLE_CLICKED: 2ca7, *note
     BUTTONn_TRIPLE_CLICKED: 2ca8, *note BUTTON_SHIFT: 2ca9, *note
     BUTTON_CTRL: 2caa, *note BUTTON_ALT: 2cab.

     在 3.10 版的變更: The ‘BUTTON5_*’ constants are now exposed if they
     are provided by the underlying curses library.

 -- 函式: curses.getsyx ()

     Return the current coordinates of the virtual screen cursor as a
     tuple ‘(y, x)’.  If *note leaveok: 2cad. is currently ‘True’, then
     return ‘(-1, -1)’.

 -- 函式: curses.getwin (file)

     Read window related data stored in the file by an earlier *note
     window.putwin(): 2caf. call.  The routine then creates and
     initializes a new window using that data, returning the new window
     object.

 -- 函式: curses.has_colors ()

     Return ‘True’ if the terminal can display colors; otherwise, return
     ‘False’.

 -- 函式: curses.has_extended_color_support ()

     Return ‘True’ if the module supports extended colors; otherwise,
     return ‘False’.  Extended color support allows more than 256 color
     pairs for terminals that support more than 16 colors (e.g.
     xterm-256color).

     Extended color support requires ncurses version 6.1 or later.

     在 3.10 版被加入.

 -- 函式: curses.has_ic ()

     Return ‘True’ if the terminal has insert- and delete-character
     capabilities.  This function is included for historical reasons
     only, as all modern software terminal emulators have such
     capabilities.

 -- 函式: curses.has_il ()

     Return ‘True’ if the terminal has insert- and delete-line
     capabilities, or can simulate them using scrolling regions.  This
     function is included for historical reasons only, as all modern
     software terminal emulators have such capabilities.

 -- 函式: curses.has_key (ch)

     Take a key value 'ch', and return ‘True’ if the current terminal
     type recognizes a key with that value.

 -- 函式: curses.halfdelay (tenths)

     Used for half-delay mode, which is similar to cbreak mode in that
     characters typed by the user are immediately available to the
     program.  However, after blocking for 'tenths' tenths of seconds,
     raise an exception if nothing has been typed.  The value of
     'tenths' must be a number between ‘1’ and ‘255’.  Use *note
     nocbreak(): 2cb5. to leave half-delay mode.

 -- 函式: curses.init_color (color_number, r, g, b)

     Change the definition of a color, taking the number of the color to
     be changed followed by three RGB values (for the amounts of red,
     green, and blue components).  The value of 'color_number' must be
     between ‘0’ and ‘COLORS - 1’.  Each of 'r', 'g', 'b', must be a
     value between ‘0’ and ‘1000’.  When *note init_color(): 796. is
     used, all occurrences of that color on the screen immediately
     change to the new definition.  This function is a no-op on most
     terminals; it is active only if *note can_change_color(): 2c89.
     returns ‘True’.

 -- 函式: curses.init_pair (pair_number, fg, bg)

     Change the definition of a color-pair.  It takes three arguments:
     the number of the color-pair to be changed, the foreground color
     number, and the background color number.  The value of
     'pair_number' must be between ‘1’ and ‘COLOR_PAIRS - 1’ (the ‘0’
     color pair is wired to white on black and cannot be changed).  The
     value of 'fg' and 'bg' arguments must be between ‘0’ and ‘COLORS -
     1’, or, after calling *note use_default_colors(): 2cb6, ‘-1’.  If
     the color-pair was previously initialized, the screen is refreshed
     and all occurrences of that color-pair are changed to the new
     definition.

 -- 函式: curses.initscr ()

     Initialize the library.  Return a *note window: 2cb7. object which
     represents the whole screen.

          備註: If there is an error opening the terminal, the
          underlying curses library may cause the interpreter to exit.

 -- 函式: curses.is_term_resized (nlines, ncols)

     Return ‘True’ if *note resize_term(): 2cb9. would modify the window
     structure, ‘False’ otherwise.

 -- 函式: curses.isendwin ()

     Return ‘True’ if *note endwin(): 2c9b. has been called (that is,
     the curses library has been deinitialized).

 -- 函式: curses.keyname (k)

     Return the name of the key numbered 'k' as a bytes object.  The
     name of a key generating printable ASCII character is the key's
     character.  The name of a control-key combination is a two-byte
     bytes object consisting of a caret (‘b'^'’) followed by the
     corresponding printable ASCII character.  The name of an alt-key
     combination (128-255) is a bytes object consisting of the prefix
     ‘b'M-'’ followed by the name of the corresponding ASCII character.

 -- 函式: curses.killchar ()

     Return the user's current line kill character as a one-byte bytes
     object.  Under Unix operating systems this is a property of the
     controlling tty of the curses program, and is not set by the curses
     library itself.

 -- 函式: curses.longname ()

     Return a bytes object containing the terminfo long name field
     describing the current terminal.  The maximum length of a verbose
     description is 128 characters.  It is defined only after the call
     to *note initscr(): 2c9e.

 -- 函式: curses.meta (flag)

     If 'flag' is ‘True’, allow 8-bit characters to be input.  If 'flag'
     is ‘False’, allow only 7-bit chars.

 -- 函式: curses.mouseinterval (interval)

     Set the maximum time in milliseconds that can elapse between press
     and release events in order for them to be recognized as a click,
     and return the previous interval value.  The default value is 200
     milliseconds, or one fifth of a second.

 -- 函式: curses.mousemask (mousemask)

     Set the mouse events to be reported, and return a tuple
     ‘(availmask, oldmask)’.  'availmask' indicates which of the
     specified mouse events can be reported; on complete failure it
     returns ‘0’.  'oldmask' is the previous value of the given window's
     mouse event mask.  If this function is never called, no mouse
     events are ever reported.

 -- 函式: curses.napms (ms)

     Sleep for 'ms' milliseconds.

 -- 函式: curses.newpad (nlines, ncols)

     Create and return a pointer to a new pad data structure with the
     given number of lines and columns.  Return a pad as a window
     object.

     A pad is like a window, except that it is not restricted by the
     screen size, and is not necessarily associated with a particular
     part of the screen.  Pads can be used when a large window is
     needed, and only a part of the window will be on the screen at one
     time.  Automatic refreshes of pads (such as from scrolling or
     echoing of input) do not occur.  The *note refresh(): 2c99. and
     *note noutrefresh(): 2c97. methods of a pad require 6 arguments to
     specify the part of the pad to be displayed and the location on the
     screen to be used for the display.  The arguments are 'pminrow',
     'pmincol', 'sminrow', 'smincol', 'smaxrow', 'smaxcol'; the 'p'
     arguments refer to the upper left corner of the pad region to be
     displayed and the 's' arguments define a clipping box on the screen
     within which the pad region is to be displayed.

 -- 函式: curses.newwin (nlines, ncols)

 -- 函式: curses.newwin (nlines, ncols, begin_y, begin_x)

     Return a new *note window: 2cb7, whose left-upper corner is at
     ‘(begin_y, begin_x)’, and whose height/width is 'nlines'/'ncols'.

     By default, the window will extend from the specified position to
     the lower right corner of the screen.

 -- 函式: curses.nl ()

     Enter newline mode.  This mode translates the return key into
     newline on input, and translates newline into return and line-feed
     on output.  Newline mode is initially on.

 -- 函式: curses.nocbreak ()

     Leave cbreak mode.  Return to normal "cooked" mode with line
     buffering.

 -- 函式: curses.noecho ()

     Leave echo mode.  Echoing of input characters is turned off.

 -- 函式: curses.nonl ()

     Leave newline mode.  Disable translation of return into newline on
     input, and disable low-level translation of newline into
     newline/return on output (but this does not change the behavior of
     ‘addch('\n')’, which always does the equivalent of return and line
     feed on the virtual screen).  With translation off, curses can
     sometimes speed up vertical motion a little; also, it will be able
     to detect the return key on input.

 -- 函式: curses.noqiflush ()

     When the ‘noqiflush()’ routine is used, normal flush of input and
     output queues associated with the ‘INTR’, ‘QUIT’ and ‘SUSP’
     characters will not be done.  You may want to call ‘noqiflush()’ in
     a signal handler if you want output to continue as though the
     interrupt had not occurred, after the handler exits.

 -- 函式: curses.noraw ()

     Leave raw mode.  Return to normal "cooked" mode with line
     buffering.

 -- 函式: curses.pair_content (pair_number)

     Return a tuple ‘(fg, bg)’ containing the colors for the requested
     color pair.  The value of 'pair_number' must be between ‘0’ and
     ‘COLOR_PAIRS - 1’.

 -- 函式: curses.pair_number (attr)

     Return the number of the color-pair set by the attribute value
     'attr'.  *note color_pair(): 2c8c. is the counterpart to this
     function.

 -- 函式: curses.putp (str)

     Equivalent to ‘tputs(str, 1, putchar)’; emit the value of a
     specified terminfo capability for the current terminal.  Note that
     the output of *note putp(): 2cc9. always goes to standard output.

 -- 函式: curses.qiflush ([flag])

     If 'flag' is ‘False’, the effect is the same as calling *note
     noqiflush(): 2cc7.  If 'flag' is ‘True’, or no argument is
     provided, the queues will be flushed when these control characters
     are read.

 -- 函式: curses.raw ()

     Enter raw mode.  In raw mode, normal line buffering and processing
     of interrupt, quit, suspend, and flow control keys are turned off;
     characters are presented to curses input functions one by one.

 -- 函式: curses.reset_prog_mode ()

     Restore the terminal to "program" mode, as previously saved by
     *note def_prog_mode(): 2c91.

 -- 函式: curses.reset_shell_mode ()

     Restore the terminal to "shell" mode, as previously saved by *note
     def_shell_mode(): 2c93.

 -- 函式: curses.resetty ()

     Restore the state of the terminal modes to what it was at the last
     call to *note savetty(): 2ccc.

 -- 函式: curses.resize_term (nlines, ncols)

     Backend function used by *note resizeterm(): 2ccd, performing most
     of the work; when resizing the windows, *note resize_term(): 2cb9.
     blank-fills the areas that are extended.  The calling application
     should fill in these areas with appropriate data.  The
     ‘resize_term()’ function attempts to resize all windows.  However,
     due to the calling convention of pads, it is not possible to resize
     these without additional interaction with the application.

 -- 函式: curses.resizeterm (nlines, ncols)

     Resize the standard and current windows to the specified
     dimensions, and adjusts other bookkeeping data used by the curses
     library that record the window dimensions (in particular the
     SIGWINCH handler).

 -- 函式: curses.savetty ()

     Save the current state of the terminal modes in a buffer, usable by
     *note resetty(): 2ccb.

 -- 函式: curses.get_escdelay ()

     Retrieves the value set by *note set_escdelay(): 896.

     在 3.9 版被加入.

 -- 函式: curses.set_escdelay (ms)

     Sets the number of milliseconds to wait after reading an escape
     character, to distinguish between an individual escape character
     entered on the keyboard from escape sequences sent by cursor and
     function keys.

     在 3.9 版被加入.

 -- 函式: curses.get_tabsize ()

     Retrieves the value set by *note set_tabsize(): 898.

     在 3.9 版被加入.

 -- 函式: curses.set_tabsize (size)

     Sets the number of columns used by the curses library when
     converting a tab character to spaces as it adds the tab to a
     window.

     在 3.9 版被加入.

 -- 函式: curses.setsyx (y, x)

     Set the virtual screen cursor to 'y', 'x'.  If 'y' and 'x' are both
     ‘-1’, then *note leaveok: 2cad. is set ‘True’.

 -- 函式: curses.setupterm (term=None, fd=-1)

     Initialize the terminal.  'term' is a string giving the terminal
     name, or ‘None’; if omitted or ‘None’, the value of the ‘TERM’
     environment variable will be used.  'fd' is the file descriptor to
     which any initialization sequences will be sent; if not supplied or
     ‘-1’, the file descriptor for ‘sys.stdout’ will be used.

 -- 函式: curses.start_color ()

     Must be called if the programmer wants to use colors, and before
     any other color manipulation routine is called.  It is good
     practice to call this routine right after *note initscr(): 2c9e.

     *note start_color(): 2cd0. initializes eight basic colors (black,
     red, green, yellow, blue, magenta, cyan, and white), and two global
     variables in the *note curses: 23. module, *note COLORS: 2cd1. and
     *note COLOR_PAIRS: 2cd2, containing the maximum number of colors
     and color-pairs the terminal can support.  It also restores the
     colors on the terminal to the values they had when the terminal was
     just turned on.

 -- 函式: curses.termattrs ()

     Return a logical OR of all video attributes supported by the
     terminal.  This information is useful when a curses program needs
     complete control over the appearance of the screen.

 -- 函式: curses.termname ()

     Return the value of the environment variable ‘TERM’, as a bytes
     object, truncated to 14 characters.

 -- 函式: curses.tigetflag (capname)

     Return the value of the Boolean capability corresponding to the
     terminfo capability name 'capname' as an integer.  Return the value
     ‘-1’ if 'capname' is not a Boolean capability, or ‘0’ if it is
     canceled or absent from the terminal description.

 -- 函式: curses.tigetnum (capname)

     Return the value of the numeric capability corresponding to the
     terminfo capability name 'capname' as an integer.  Return the value
     ‘-2’ if 'capname' is not a numeric capability, or ‘-1’ if it is
     canceled or absent from the terminal description.

 -- 函式: curses.tigetstr (capname)

     Return the value of the string capability corresponding to the
     terminfo capability name 'capname' as a bytes object.  Return
     ‘None’ if 'capname' is not a terminfo "string capability", or is
     canceled or absent from the terminal description.

 -- 函式: curses.tparm (str[, ...])

     Instantiate the bytes object 'str' with the supplied parameters,
     where 'str' should be a parameterized string obtained from the
     terminfo database.  E.g.  ‘tparm(tigetstr("cup"), 5, 3)’ could
     result in ‘b'\033[6;4H'’, the exact result depending on terminal
     type.

 -- 函式: curses.typeahead (fd)

     Specify that the file descriptor 'fd' be used for typeahead
     checking.  If 'fd' is ‘-1’, then no typeahead checking is done.

     The curses library does "line-breakout optimization" by looking for
     typeahead periodically while updating the screen.  If input is
     found, and it is coming from a tty, the current update is postponed
     until refresh or doupdate is called again, allowing faster response
     to commands typed in advance.  This function allows specifying a
     different file descriptor for typeahead checking.

 -- 函式: curses.unctrl (ch)

     Return a bytes object which is a printable representation of the
     character 'ch'.  Control characters are represented as a caret
     followed by the character, for example as ‘b'^C'’.  Printing
     characters are left as they are.

 -- 函式: curses.ungetch (ch)

     Push 'ch' so the next *note getch(): 2ca2. will return it.

          備註: Only one 'ch' can be pushed before ‘getch()’ is called.

 -- 函式: curses.update_lines_cols ()

     Update the *note LINES: 1608. and *note COLS: 1609. module
     variables.  Useful for detecting manual screen resize.

     在 3.5 版被加入.

 -- 函式: curses.unget_wch (ch)

     Push 'ch' so the next *note get_wch(): 1038. will return it.

          備註: Only one 'ch' can be pushed before ‘get_wch()’ is
          called.

     在 3.3 版被加入.

 -- 函式: curses.ungetmouse (id, x, y, z, bstate)

     Push a *note KEY_MOUSE: 2ca3. event onto the input queue,
     associating the given state data with it.

 -- 函式: curses.use_env (flag)

     If used, this function should be called before *note initscr():
     2c9e. or newterm are called.  When 'flag' is ‘False’, the values of
     lines and columns specified in the terminfo database will be used,
     even if environment variables ‘LINES’ and ‘COLUMNS’ (used by
     default) are set, or if curses is running in a window (in which
     case default behavior would be to use the window size if ‘LINES’
     and ‘COLUMNS’ are not set).

 -- 函式: curses.use_default_colors ()

     Allow use of default values for colors on terminals supporting this
     feature.  Use this to support transparency in your application.
     The default color is assigned to the color number ‘-1’.  After
     calling this function, ‘init_pair(x, curses.COLOR_RED, -1)’
     initializes, for instance, color pair 'x' to a red foreground color
     on the default background.

 -- 函式: curses.wrapper (func, /, *args, **kwargs)

     Initialize curses and call another callable object, 'func', which
     should be the rest of your curses-using application.  If the
     application raises an exception, this function will restore the
     terminal to a sane state before re-raising the exception and
     generating a traceback.  The callable object 'func' is then passed
     the main window 'stdscr' as its first argument, followed by any
     other arguments passed to ‘wrapper()’.  Before calling 'func',
     ‘wrapper()’ turns on cbreak mode, turns off echo, enables the
     terminal keypad, and initializes colors if the terminal has color
     support.  On exit (whether normally or by exception) it restores
     cooked mode, turns on echo, and disables the terminal keypad.


File: python.info,  Node: Window Objects,  Next: Constants,  Prev: 函式<5>,  Up: curses --- 字元儲存格顯示的終端處理

5.16.9.2 Window Objects
.......................

Window objects, as returned by *note initscr(): 2c9e. and *note
newwin(): 2cc3. above, have the following methods and attributes:

 -- 方法: window.addch (ch[, attr])

 -- 方法: window.addch (y, x, ch[, attr])

     Paint character 'ch' at ‘(y, x)’ with attributes 'attr',
     overwriting any character previously painted at that location.  By
     default, the character position and attributes are the current
     settings for the window object.

          備註: Writing outside the window, subwindow, or pad raises a
          *note curses.error: 2c85.  Attempting to write to the lower
          right corner of a window, subwindow, or pad will cause an
          exception to be raised after the character is printed.

 -- 方法: window.addnstr (str, n[, attr])

 -- 方法: window.addnstr (y, x, str, n[, attr])

     Paint at most 'n' characters of the character string 'str' at ‘(y,
     x)’ with attributes 'attr', overwriting anything previously on the
     display.

 -- 方法: window.addstr (str[, attr])

 -- 方法: window.addstr (y, x, str[, attr])

     Paint the character string 'str' at ‘(y, x)’ with attributes
     'attr', overwriting anything previously on the display.

          備註: 
             * Writing outside the window, subwindow, or pad raises
               *note curses.error: 2c85.  Attempting to write to the
               lower right corner of a window, subwindow, or pad will
               cause an exception to be raised after the string is
               printed.

             * A bug in ncurses(1), the backend for this Python module,
               can cause SegFaults when resizing windows.  This is fixed
               in ncurses-6.1-20190511.  If you are stuck with an
               earlier ncurses, you can avoid triggering this if you do
               not call *note addstr(): 2c98. with a 'str' that has
               embedded newlines.  Instead, call *note addstr(): 2c98.
               separately for each line.

 -- 方法: window.attroff (attr)

     Remove attribute 'attr' from the "background" set applied to all
     writes to the current window.

 -- 方法: window.attron (attr)

     Add attribute 'attr' from the "background" set applied to all
     writes to the current window.

 -- 方法: window.attrset (attr)

     Set the "background" set of attributes to 'attr'.  This set is
     initially ‘0’ (no attributes).

 -- 方法: window.bkgd (ch[, attr])

     Set the background property of the window to the character 'ch',
     with attributes 'attr'.  The change is then applied to every
     character position in that window:

        * The attribute of every character in the window is changed to
          the new background attribute.

        * Wherever the former background character appears, it is
          changed to the new background character.

 -- 方法: window.bkgdset (ch[, attr])

     Set the window's background.  A window's background consists of a
     character and any combination of attributes.  The attribute part of
     the background is combined (OR'ed) with all non-blank characters
     that are written into the window.  Both the character and attribute
     parts of the background are combined with the blank characters.
     The background becomes a property of the character and moves with
     the character through any scrolling and insert/delete
     line/character operations.

 -- 方法: window.border ([ls[, rs[, ts[, bs[, tl[, tr[, bl[, br]]]]]]]])

     Draw a border around the edges of the window.  Each parameter
     specifies the character to use for a specific part of the border;
     see the table below for more details.

          備註: A ‘0’ value for any parameter will cause the default
          character to be used for that parameter.  Keyword parameters
          can 'not' be used.  The defaults are listed in this table:

     參數            描述                      Default value
                                               
     ----------------------------------------------------------------------
                                               
     'ls'            Left side                 *note ACS_VLINE: 2ce7.
                                               
                                               
     'rs'            Right side                *note ACS_VLINE: 2ce7.
                                               
                                               
     'ts'            Top                       *note ACS_HLINE: 2ce8.
                                               
                                               
     'bs'            Bottom                    *note ACS_HLINE: 2ce8.
                                               
                                               
     'tl'            Upper-left corner         *note ACS_ULCORNER: 2ce9.
                                               
                                               
     'tr'            Upper-right corner        *note ACS_URCORNER: 2cea.
                                               
                                               
     'bl'            Bottom-left corner        *note ACS_LLCORNER: 2ceb.
                                               
                                               
     'br'            Bottom-right corner       *note ACS_LRCORNER: 2cec.
                                               

 -- 方法: window.box ([vertch, horch])

     Similar to *note border(): 2ce6, but both 'ls' and 'rs' are
     'vertch' and both 'ts' and 'bs' are 'horch'.  The default corner
     characters are always used by this function.

 -- 方法: window.chgat (attr)

 -- 方法: window.chgat (num, attr)

 -- 方法: window.chgat (y, x, attr)

 -- 方法: window.chgat (y, x, num, attr)

     Set the attributes of 'num' characters at the current cursor
     position, or at position ‘(y, x)’ if supplied.  If 'num' is not
     given or is ‘-1’, the attribute will be set on all the characters
     to the end of the line.  This function moves cursor to position
     ‘(y, x)’ if supplied.  The changed line will be touched using the
     *note touchline(): 2cef. method so that the contents will be
     redisplayed by the next window refresh.

 -- 方法: window.clear ()

     Like *note erase(): 2cf1, but also cause the whole window to be
     repainted upon next call to *note refresh(): 2c99.

 -- 方法: window.clearok (flag)

     If 'flag' is ‘True’, the next call to *note refresh(): 2c99. will
     clear the window completely.

 -- 方法: window.clrtobot ()

     Erase from cursor to the end of the window: all lines below the
     cursor are deleted, and then the equivalent of *note clrtoeol():
     2cf4. is performed.

 -- 方法: window.clrtoeol ()

     Erase from cursor to the end of the line.

 -- 方法: window.cursyncup ()

     Update the current cursor position of all the ancestors of the
     window to reflect the current cursor position of the window.

 -- 方法: window.delch ([y, x])

     Delete any character at ‘(y, x)’.

 -- 方法: window.deleteln ()

     Delete the line under the cursor.  All following lines are moved up
     by one line.

 -- 方法: window.derwin (begin_y, begin_x)

 -- 方法: window.derwin (nlines, ncols, begin_y, begin_x)

     An abbreviation for "derive window", *note derwin(): 2cf8. is the
     same as calling *note subwin(): 2cf9, except that 'begin_y' and
     'begin_x' are relative to the origin of the window, rather than
     relative to the entire screen.  Return a window object for the
     derived window.

 -- 方法: window.echochar (ch[, attr])

     Add character 'ch' with attribute 'attr', and immediately call
     *note refresh(): 2c99. on the window.

 -- 方法: window.enclose (y, x)

     Test whether the given pair of screen-relative character-cell
     coordinates are enclosed by the given window, returning ‘True’ or
     ‘False’.  It is useful for determining what subset of the screen
     windows enclose the location of a mouse event.

     在 3.10 版的變更: Previously it returned ‘1’ or ‘0’ instead of
     ‘True’ or ‘False’.

 -- 屬性: window.encoding

     Encoding used to encode method arguments (Unicode strings and
     characters).  The encoding attribute is inherited from the parent
     window when a subwindow is created, for example with *note
     window.subwin(): 2cf9.  By default, current locale encoding is used
     (see *note locale.getencoding(): 2bc.).

     在 3.3 版被加入.

 -- 方法: window.erase ()

     Clear the window.

 -- 方法: window.getbegyx ()

     Return a tuple ‘(y, x)’ of coordinates of upper-left corner.

 -- 方法: window.getbkgd ()

     Return the given window's current background character/attribute
     pair.

 -- 方法: window.getch ([y, x])

     Get a character.  Note that the integer returned does 'not' have to
     be in ASCII range: function keys, keypad keys and so on are
     represented by numbers higher than 255.  In no-delay mode, return
     ‘-1’ if there is no input, otherwise wait until a key is pressed.

 -- 方法: window.get_wch ([y, x])

     Get a wide character.  Return a character for most keys, or an
     integer for function keys, keypad keys, and other special keys.  In
     no-delay mode, raise an exception if there is no input.

     在 3.3 版被加入.

 -- 方法: window.getkey ([y, x])

     Get a character, returning a string instead of an integer, as *note
     getch(): 2ca2. does.  Function keys, keypad keys and other special
     keys return a multibyte string containing the key name.  In
     no-delay mode, raise an exception if there is no input.

 -- 方法: window.getmaxyx ()

     Return a tuple ‘(y, x)’ of the height and width of the window.

 -- 方法: window.getparyx ()

     Return the beginning coordinates of this window relative to its
     parent window as a tuple ‘(y, x)’.  Return ‘(-1, -1)’ if this
     window has no parent.

 -- 方法: window.getstr ()

 -- 方法: window.getstr (n)

 -- 方法: window.getstr (y, x)

 -- 方法: window.getstr (y, x, n)

     Read a bytes object from the user, with primitive line editing
     capacity.

 -- 方法: window.getyx ()

     Return a tuple ‘(y, x)’ of current cursor position relative to the
     window's upper-left corner.

 -- 方法: window.hline (ch, n)

 -- 方法: window.hline (y, x, ch, n)

     Display a horizontal line starting at ‘(y, x)’ with length 'n'
     consisting of the character 'ch'.

 -- 方法: window.idcok (flag)

     If 'flag' is ‘False’, curses no longer considers using the hardware
     insert/delete character feature of the terminal; if 'flag' is
     ‘True’, use of character insertion and deletion is enabled.  When
     curses is first initialized, use of character insert/delete is
     enabled by default.

 -- 方法: window.idlok (flag)

     If 'flag' is ‘True’, *note curses: 23. will try and use hardware
     line editing facilities.  Otherwise, line insertion/deletion are
     disabled.

 -- 方法: window.immedok (flag)

     If 'flag' is ‘True’, any change in the window image automatically
     causes the window to be refreshed; you no longer have to call *note
     refresh(): 2c99. yourself.  However, it may degrade performance
     considerably, due to repeated calls to wrefresh.  This option is
     disabled by default.

 -- 方法: window.inch ([y, x])

     Return the character at the given position in the window.  The
     bottom 8 bits are the character proper, and upper bits are the
     attributes.

 -- 方法: window.insch (ch[, attr])

 -- 方法: window.insch (y, x, ch[, attr])

     Paint character 'ch' at ‘(y, x)’ with attributes 'attr', moving the
     line from position 'x' right by one character.

 -- 方法: window.insdelln (nlines)

     Insert 'nlines' lines into the specified window above the current
     line.  The 'nlines' bottom lines are lost.  For negative 'nlines',
     delete 'nlines' lines starting with the one under the cursor, and
     move the remaining lines up.  The bottom 'nlines' lines are
     cleared.  The current cursor position remains the same.

 -- 方法: window.insertln ()

     Insert a blank line under the cursor.  All following lines are
     moved down by one line.

 -- 方法: window.insnstr (str, n[, attr])

 -- 方法: window.insnstr (y, x, str, n[, attr])

     Insert a character string (as many characters as will fit on the
     line) before the character under the cursor, up to 'n' characters.
     If 'n' is zero or negative, the entire string is inserted.  All
     characters to the right of the cursor are shifted right, with the
     rightmost characters on the line being lost.  The cursor position
     does not change (after moving to 'y', 'x', if specified).

 -- 方法: window.insstr (str[, attr])

 -- 方法: window.insstr (y, x, str[, attr])

     Insert a character string (as many characters as will fit on the
     line) before the character under the cursor.  All characters to the
     right of the cursor are shifted right, with the rightmost
     characters on the line being lost.  The cursor position does not
     change (after moving to 'y', 'x', if specified).

 -- 方法: window.instr ([n])

 -- 方法: window.instr (y, x[, n])

     Return a bytes object of characters, extracted from the window
     starting at the current cursor position, or at 'y', 'x' if
     specified.  Attributes are stripped from the characters.  If 'n' is
     specified, *note instr(): 2d0c. returns a string at most 'n'
     characters long (exclusive of the trailing NUL).

 -- 方法: window.is_linetouched (line)

     Return ‘True’ if the specified line was modified since the last
     call to *note refresh(): 2c99.; otherwise return ‘False’.  Raise a
     *note curses.error: 2c85. exception if 'line' is not valid for the
     given window.

 -- 方法: window.is_wintouched ()

     Return ‘True’ if the specified window was modified since the last
     call to *note refresh(): 2c99.; otherwise return ‘False’.

 -- 方法: window.keypad (flag)

     If 'flag' is ‘True’, escape sequences generated by some keys
     (keypad, function keys) will be interpreted by *note curses: 23.
     If 'flag' is ‘False’, escape sequences will be left as is in the
     input stream.

 -- 方法: window.leaveok (flag)

     If 'flag' is ‘True’, cursor is left where it is on update, instead
     of being at "cursor position."  This reduces cursor movement where
     possible.  If possible the cursor will be made invisible.

     If 'flag' is ‘False’, cursor will always be at "cursor position"
     after an update.

 -- 方法: window.move (new_y, new_x)

     Move cursor to ‘(new_y, new_x)’.

 -- 方法: window.mvderwin (y, x)

     Move the window inside its parent window.  The screen-relative
     parameters of the window are not changed.  This routine is used to
     display different parts of the parent window at the same physical
     position on the screen.

 -- 方法: window.mvwin (new_y, new_x)

     Move the window so its upper-left corner is at ‘(new_y, new_x)’.

 -- 方法: window.nodelay (flag)

     If 'flag' is ‘True’, *note getch(): 2ca2. will be non-blocking.

 -- 方法: window.notimeout (flag)

     If 'flag' is ‘True’, escape sequences will not be timed out.

     If 'flag' is ‘False’, after a few milliseconds, an escape sequence
     will not be interpreted, and will be left in the input stream as
     is.

 -- 方法: window.noutrefresh ()

     Mark for refresh but wait.  This function updates the data
     structure representing the desired state of the window, but does
     not force an update of the physical screen.  To accomplish that,
     call *note doupdate(): 2c96.

 -- 方法: window.overlay (destwin[, sminrow, smincol, dminrow, dmincol,
          dmaxrow, dmaxcol])

     Overlay the window on top of 'destwin'.  The windows need not be
     the same size, only the overlapping region is copied.  This copy is
     non-destructive, which means that the current background character
     does not overwrite the old contents of 'destwin'.

     To get fine-grained control over the copied region, the second form
     of *note overlay(): 2d15. can be used.  'sminrow' and 'smincol' are
     the upper-left coordinates of the source window, and the other
     variables mark a rectangle in the destination window.

 -- 方法: window.overwrite (destwin[, sminrow, smincol, dminrow,
          dmincol, dmaxrow, dmaxcol])

     Overwrite the window on top of 'destwin'.  The windows need not be
     the same size, in which case only the overlapping region is copied.
     This copy is destructive, which means that the current background
     character overwrites the old contents of 'destwin'.

     To get fine-grained control over the copied region, the second form
     of *note overwrite(): 2d16. can be used.  'sminrow' and 'smincol'
     are the upper-left coordinates of the source window, the other
     variables mark a rectangle in the destination window.

 -- 方法: window.putwin (file)

     Write all data associated with the window into the provided file
     object.  This information can be later retrieved using the *note
     getwin(): 2cae. function.

 -- 方法: window.redrawln (beg, num)

     Indicate that the 'num' screen lines, starting at line 'beg', are
     corrupted and should be completely redrawn on the next *note
     refresh(): 2c99. call.

 -- 方法: window.redrawwin ()

     Touch the entire window, causing it to be completely redrawn on the
     next *note refresh(): 2c99. call.

 -- 方法: window.refresh ([pminrow, pmincol, sminrow, smincol, smaxrow,
          smaxcol])

     Update the display immediately (sync actual screen with previous
     drawing/deleting methods).

     The 6 optional arguments can only be specified when the window is a
     pad created with *note newpad(): 2cc2.  The additional parameters
     are needed to indicate what part of the pad and screen are
     involved.  'pminrow' and 'pmincol' specify the upper left-hand
     corner of the rectangle to be displayed in the pad.  'sminrow',
     'smincol', 'smaxrow', and 'smaxcol' specify the edges of the
     rectangle to be displayed on the screen.  The lower right-hand
     corner of the rectangle to be displayed in the pad is calculated
     from the screen coordinates, since the rectangles must be the same
     size.  Both rectangles must be entirely contained within their
     respective structures.  Negative values of 'pminrow', 'pmincol',
     'sminrow', or 'smincol' are treated as if they were zero.

 -- 方法: window.resize (nlines, ncols)

     Reallocate storage for a curses window to adjust its dimensions to
     the specified values.  If either dimension is larger than the
     current values, the window's data is filled with blanks that have
     the current background rendition (as set by *note bkgdset(): 2ce5.)
     merged into them.

 -- 方法: window.scroll ([lines=1])

     Scroll the screen or scrolling region upward by 'lines' lines.

 -- 方法: window.scrollok (flag)

     Control what happens when the cursor of a window is moved off the
     edge of the window or scrolling region, either as a result of a
     newline action on the bottom line, or typing the last character of
     the last line.  If 'flag' is ‘False’, the cursor is left on the
     bottom line.  If 'flag' is ‘True’, the window is scrolled up one
     line.  Note that in order to get the physical scrolling effect on
     the terminal, it is also necessary to call *note idlok(): 2d04.

 -- 方法: window.setscrreg (top, bottom)

     Set the scrolling region from line 'top' to line 'bottom'.  All
     scrolling actions will take place in this region.

 -- 方法: window.standend ()

     Turn off the standout attribute.  On some terminals this has the
     side effect of turning off all attributes.

 -- 方法: window.standout ()

     Turn on attribute 'A_STANDOUT'.

 -- 方法: window.subpad (begin_y, begin_x)

 -- 方法: window.subpad (nlines, ncols, begin_y, begin_x)

     Return a sub-window, whose upper-left corner is at ‘(begin_y,
     begin_x)’, and whose width/height is 'ncols'/'nlines'.

 -- 方法: window.subwin (begin_y, begin_x)

 -- 方法: window.subwin (nlines, ncols, begin_y, begin_x)

     Return a sub-window, whose upper-left corner is at ‘(begin_y,
     begin_x)’, and whose width/height is 'ncols'/'nlines'.

     By default, the sub-window will extend from the specified position
     to the lower right corner of the window.

 -- 方法: window.syncdown ()

     Touch each location in the window that has been touched in any of
     its ancestor windows.  This routine is called by *note refresh():
     2c99, so it should almost never be necessary to call it manually.

 -- 方法: window.syncok (flag)

     If 'flag' is ‘True’, then *note syncup(): 2d22. is called
     automatically whenever there is a change in the window.

 -- 方法: window.syncup ()

     Touch all locations in ancestors of the window that have been
     changed in the window.

 -- 方法: window.timeout (delay)

     Set blocking or non-blocking read behavior for the window.  If
     'delay' is negative, blocking read is used (which will wait
     indefinitely for input).  If 'delay' is zero, then non-blocking
     read is used, and *note getch(): 2ca2. will return ‘-1’ if no input
     is waiting.  If 'delay' is positive, then *note getch(): 2ca2. will
     block for 'delay' milliseconds, and return ‘-1’ if there is still
     no input at the end of that time.

 -- 方法: window.touchline (start, count[, changed])

     Pretend 'count' lines have been changed, starting with line
     'start'.  If 'changed' is supplied, it specifies whether the
     affected lines are marked as having been changed ('changed'‘=True’)
     or unchanged ('changed'‘=False’).

 -- 方法: window.touchwin ()

     Pretend the whole window has been changed, for purposes of drawing
     optimizations.

 -- 方法: window.untouchwin ()

     Mark all lines in the window as unchanged since the last call to
     *note refresh(): 2c99.

 -- 方法: window.vline (ch, n[, attr])

 -- 方法: window.vline (y, x, ch, n[, attr])

     Display a vertical line starting at ‘(y, x)’ with length 'n'
     consisting of the character 'ch' with attributes 'attr'.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue35924


File: python.info,  Node: Constants,  Prev: Window Objects,  Up: curses --- 字元儲存格顯示的終端處理

5.16.9.3 Constants
..................

The *note curses: 23. module defines the following data members:

 -- 資料: curses.ERR

     Some curses routines that return an integer, such as *note getch():
     2ca2, return *note ERR: 2d27. upon failure.

 -- 資料: curses.OK

     Some curses routines that return an integer, such as *note napms():
     2cc1, return *note OK: 2d28. upon success.

 -- 資料: curses.version

 -- 資料: curses.__version__

     A bytes object representing the current version of the module.

 -- 資料: curses.ncurses_version

     A named tuple containing the three components of the ncurses
     library version: 'major', 'minor', and 'patch'.  All values are
     integers.  The components can also be accessed by name, so
     ‘curses.ncurses_version[0]’ is equivalent to
     ‘curses.ncurses_version.major’ and so on.

     Availability: if the ncurses library is used.

     在 3.8 版被加入.

 -- 資料: curses.COLORS

     The maximum number of colors the terminal can support.  It is
     defined only after the call to *note start_color(): 2cd0.

 -- 資料: curses.COLOR_PAIRS

     The maximum number of color pairs the terminal can support.  It is
     defined only after the call to *note start_color(): 2cd0.

 -- 資料: curses.COLS

     The width of the screen, i.e., the number of columns.  It is
     defined only after the call to *note initscr(): 2c9e.  Updated by
     *note update_lines_cols(): d92, *note resizeterm(): 2ccd. and *note
     resize_term(): 2cb9.

 -- 資料: curses.LINES

     The height of the screen, i.e., the number of lines.  It is defined
     only after the call to *note initscr(): 2c9e.  Updated by *note
     update_lines_cols(): d92, *note resizeterm(): 2ccd. and *note
     resize_term(): 2cb9.

Some constants are available to specify character cell attributes.  The
exact constants available are system dependent.

Attribute                    含義
                             
-----------------------------------------------------------------
                             
 -- 資料:                    Alternate character set mode
          curses.A_ALTCHARSET

 -- 資料: curses.A_BLINK     Blink mode
                             
                             
 -- 資料: curses.A_BOLD      Bold mode
                             
                             
 -- 資料: curses.A_DIM       Dim mode
                             
                             
 -- 資料: curses.A_INVIS     Invisible or blank mode
                             
                             
 -- 資料: curses.A_ITALIC    Italic mode
                             
                             
 -- 資料: curses.A_NORMAL    Normal attribute
                             
                             
 -- 資料: curses.A_PROTECT   Protected mode
                             
                             
 -- 資料: curses.A_REVERSE   Reverse background and foreground
                             colors
                             
                             
 -- 資料:                    Standout mode
          curses.A_STANDOUT  

 -- 資料:                    Underline mode
          curses.A_UNDERLINE 

 -- 資料:                    Horizontal highlight
          curses.A_HORIZONTAL

 -- 資料: curses.A_LEFT      Left highlight
                             
                             
 -- 資料: curses.A_LOW       Low highlight
                             
                             
 -- 資料: curses.A_RIGHT     Right highlight
                             
                             
 -- 資料: curses.A_TOP       Top highlight
                             
                             
 -- 資料:                    Vertical highlight
          curses.A_VERTICAL  

在 3.7 版被加入: ‘A_ITALIC’ was added.

Several constants are available to extract corresponding attributes
returned by some methods.

Bit-mask                      含義
                              
------------------------------------------------------------------
                              
 -- 資料:                     Bit-mask to extract attributes
          curses.A_ATTRIBUTES 

 -- 資料: curses.A_CHARTEXT   Bit-mask to extract a character
                              
                              
 -- 資料: curses.A_COLOR      Bit-mask to extract color-pair
                              field information
                              

Keys are referred to by integer constants with names starting with
‘KEY_’.  The exact keycaps available are system dependent.

Key constant                  Key
                              
-------------------------------------------------------------------------------
                              
 -- 資料: curses.KEY_MIN      Minimum key value
                              
                              
 -- 資料: curses.KEY_BREAK    Break key (unreliable)
                              
                              
 -- 資料: curses.KEY_DOWN     Down-arrow
                              
                              
 -- 資料: curses.KEY_UP       Up-arrow
                              
                              
 -- 資料: curses.KEY_LEFT     Left-arrow
                              
                              
 -- 資料: curses.KEY_RIGHT    Right-arrow
                              
                              
 -- 資料: curses.KEY_HOME     Home key (upward+left arrow)
                              
                              
 -- 資料:                     Backspace (unreliable)
          curses.KEY_BACKSPACE

 -- 資料: curses.KEY_F0       Function keys.  Up to 64 function keys are
                              supported.
                              
                              
 -- 資料: curses.KEY_Fn       Value of function key 'n'
                              
                              
 -- 資料: curses.KEY_DL       Delete line
                              
                              
 -- 資料: curses.KEY_IL       Insert line
                              
                              
 -- 資料: curses.KEY_DC       Delete character
                              
                              
 -- 資料: curses.KEY_IC       Insert char or enter insert mode
                              
                              
 -- 資料: curses.KEY_EIC      Exit insert char mode
                              
                              
 -- 資料: curses.KEY_CLEAR    Clear screen
                              
                              
 -- 資料: curses.KEY_EOS      Clear to end of screen
                              
                              
 -- 資料: curses.KEY_EOL      Clear to end of line
                              
                              
 -- 資料: curses.KEY_SF       Scroll 1 line forward
                              
                              
 -- 資料: curses.KEY_SR       Scroll 1 line backward (reverse)
                              
                              
 -- 資料: curses.KEY_NPAGE    Next page
                              
                              
 -- 資料: curses.KEY_PPAGE    Previous page
                              
                              
 -- 資料: curses.KEY_STAB     Set tab
                              
                              
 -- 資料: curses.KEY_CTAB     Clear tab
                              
                              
 -- 資料: curses.KEY_CATAB    Clear all tabs
                              
                              
 -- 資料: curses.KEY_ENTER    Enter or send (unreliable)
                              
                              
 -- 資料: curses.KEY_SRESET   Soft (partial) reset (unreliable)
                              
                              
 -- 資料: curses.KEY_RESET    Reset or hard reset (unreliable)
                              
                              
 -- 資料: curses.KEY_PRINT    Print
                              
                              
 -- 資料: curses.KEY_LL       Home down or bottom (lower left)
                              
                              
 -- 資料: curses.KEY_A1       Upper left of keypad
                              
                              
 -- 資料: curses.KEY_A3       Upper right of keypad
                              
                              
 -- 資料: curses.KEY_B2       Center of keypad
                              
                              
 -- 資料: curses.KEY_C1       Lower left of keypad
                              
                              
 -- 資料: curses.KEY_C3       Lower right of keypad
                              
                              
 -- 資料: curses.KEY_BTAB     Back tab
                              
                              
 -- 資料: curses.KEY_BEG      Beg (beginning)
                              
                              
 -- 資料: curses.KEY_CANCEL   Cancel
                              
                              
 -- 資料: curses.KEY_CLOSE    Close
                              
                              
 -- 資料:                     Cmd (command)
          curses.KEY_COMMAND  

 -- 資料: curses.KEY_COPY     Copy
                              
                              
 -- 資料: curses.KEY_CREATE   Create
                              
                              
 -- 資料: curses.KEY_END      End
                              
                              
 -- 資料: curses.KEY_EXIT     Exit
                              
                              
 -- 資料: curses.KEY_FIND     Find
                              
                              
 -- 資料: curses.KEY_HELP     Help
                              
                              
 -- 資料: curses.KEY_MARK     Mark
                              
                              
 -- 資料:                     Message
          curses.KEY_MESSAGE  

 -- 資料: curses.KEY_MOVE     Move
                              
                              
 -- 資料: curses.KEY_NEXT     Next
                              
                              
 -- 資料: curses.KEY_OPEN     Open
                              
                              
 -- 資料:                     Options
          curses.KEY_OPTIONS  

 -- 資料:                     Prev (previous)
          curses.KEY_PREVIOUS 

 -- 資料: curses.KEY_REDO     Redo
                              
                              
 -- 資料:                     Ref (reference)
          curses.KEY_REFERENCE

 -- 資料:                     Refresh
          curses.KEY_REFRESH  

 -- 資料:                     Replace
          curses.KEY_REPLACE  

 -- 資料:                     Restart
          curses.KEY_RESTART  

 -- 資料: curses.KEY_RESUME   Resume
                              
                              
 -- 資料: curses.KEY_SAVE     Save
                              
                              
 -- 資料: curses.KEY_SBEG     Shifted Beg (beginning)
                              
                              
 -- 資料:                     Shifted Cancel
          curses.KEY_SCANCEL  

 -- 資料:                     Shifted Command
          curses.KEY_SCOMMAND 

 -- 資料: curses.KEY_SCOPY    Shifted Copy
                              
                              
 -- 資料:                     Shifted Create
          curses.KEY_SCREATE  

 -- 資料: curses.KEY_SDC      Shifted Delete char
                              
                              
 -- 資料: curses.KEY_SDL      Shifted Delete line
                              
                              
 -- 資料: curses.KEY_SELECT   Select
                              
                              
 -- 資料: curses.KEY_SEND     Shifted End
                              
                              
 -- 資料: curses.KEY_SEOL     Shifted Clear line
                              
                              
 -- 資料: curses.KEY_SEXIT    Shifted Exit
                              
                              
 -- 資料: curses.KEY_SFIND    Shifted Find
                              
                              
 -- 資料: curses.KEY_SHELP    Shifted Help
                              
                              
 -- 資料: curses.KEY_SHOME    Shifted Home
                              
                              
 -- 資料: curses.KEY_SIC      Shifted Input
                              
                              
 -- 資料: curses.KEY_SLEFT    Shifted Left arrow
                              
                              
 -- 資料:                     Shifted Message
          curses.KEY_SMESSAGE 

 -- 資料: curses.KEY_SMOVE    Shifted Move
                              
                              
 -- 資料: curses.KEY_SNEXT    Shifted Next
                              
                              
 -- 資料:                     Shifted Options
          curses.KEY_SOPTIONS 

 -- 資料:                     Shifted Prev
          curses.KEY_SPREVIOUS

 -- 資料: curses.KEY_SPRINT   Shifted Print
                              
                              
 -- 資料: curses.KEY_SREDO    Shifted Redo
                              
                              
 -- 資料:                     Shifted Replace
          curses.KEY_SREPLACE 

 -- 資料: curses.KEY_SRIGHT   Shifted Right arrow
                              
                              
 -- 資料: curses.KEY_SRSUME   Shifted Resume
                              
                              
 -- 資料: curses.KEY_SSAVE    Shifted Save
                              
                              
 -- 資料:                     Shifted Suspend
          curses.KEY_SSUSPEND 

 -- 資料: curses.KEY_SUNDO    Shifted Undo
                              
                              
 -- 資料:                     Suspend
          curses.KEY_SUSPEND  

 -- 資料: curses.KEY_UNDO     Undo
                              
                              
 -- 資料: curses.KEY_MOUSE    Mouse event has occurred
                              
                              
 -- 資料: curses.KEY_RESIZE   Terminal resize event
                              
                              
 -- 資料: curses.KEY_MAX      Maximum key value
                              

On VT100s and their software emulations, such as X terminal emulators,
there are normally at least four function keys (*note KEY_F1: 2d45,
*note KEY_F2: 2d45, *note KEY_F3: 2d45, *note KEY_F4: 2d45.) available,
and the arrow keys mapped to *note KEY_UP: 2d3f, *note KEY_DOWN: 2d3e,
*note KEY_LEFT: 2d40. and *note KEY_RIGHT: 2d41. in the obvious way.  If
your machine has a PC keyboard, it is safe to expect arrow keys and
twelve function keys (older PC keyboards may have only ten function
keys); also, the following keypad mappings are standard:

Keycap                 Constant
                       
---------------------------------------
                       
‘Insert’               KEY_IC
                       
                       
‘Delete’               KEY_DC
                       
                       
‘Home’                 KEY_HOME
                       
                       
‘End’                  KEY_END
                       
                       
‘Page Up’              KEY_PPAGE
                       
                       
‘Page Down’            KEY_NPAGE
                       

The following table lists characters from the alternate character set.
These are inherited from the VT100 terminal, and will generally be
available on software emulations such as X terminals.  When there is no
graphic available, curses falls back on a crude printable ASCII
approximation.

     備註: These are available only after *note initscr(): 2c9e. has
     been called.

ACS code                     含義
                             
----------------------------------------------------------------------------
                             
 -- 資料: curses.ACS_BBSS    alternate name for upper right corner
                             
                             
 -- 資料: curses.ACS_BLOCK   solid square block
                             
                             
 -- 資料: curses.ACS_BOARD   board of squares
                             
                             
 -- 資料: curses.ACS_BSBS    alternate name for horizontal line
                             
                             
 -- 資料: curses.ACS_BSSB    alternate name for upper left corner
                             
                             
 -- 資料: curses.ACS_BSSS    alternate name for top tee
                             
                             
 -- 資料: curses.ACS_BTEE    bottom tee
                             
                             
 -- 資料:                    bullet
          curses.ACS_BULLET  

 -- 資料:                    checker board (stipple)
          curses.ACS_CKBOARD 

 -- 資料:                    arrow pointing down
          curses.ACS_DARROW  

 -- 資料:                    degree symbol
          curses.ACS_DEGREE  

 -- 資料:                    diamond
          curses.ACS_DIAMOND 

 -- 資料:                    greater-than-or-equal-to
          curses.ACS_GEQUAL  

 -- 資料: curses.ACS_HLINE   horizontal line
                             
                             
 -- 資料:                    lantern symbol
          curses.ACS_LANTERN 

 -- 資料:                    left arrow
          curses.ACS_LARROW  

 -- 資料:                    less-than-or-equal-to
          curses.ACS_LEQUAL  

 -- 資料:                    lower left-hand corner
          curses.ACS_LLCORNER

 -- 資料:                    lower right-hand corner
          curses.ACS_LRCORNER

 -- 資料: curses.ACS_LTEE    left tee
                             
                             
 -- 資料:                    not-equal sign
          curses.ACS_NEQUAL  

 -- 資料: curses.ACS_PI      letter pi
                             
                             
 -- 資料:                    plus-or-minus sign
          curses.ACS_PLMINUS 

 -- 資料: curses.ACS_PLUS    big plus sign
                             
                             
 -- 資料:                    right arrow
          curses.ACS_RARROW  

 -- 資料: curses.ACS_RTEE    right tee
                             
                             
 -- 資料: curses.ACS_S1      scan line 1
                             
                             
 -- 資料: curses.ACS_S3      scan line 3
                             
                             
 -- 資料: curses.ACS_S7      scan line 7
                             
                             
 -- 資料: curses.ACS_S9      scan line 9
                             
                             
 -- 資料: curses.ACS_SBBS    alternate name for lower right corner
                             
                             
 -- 資料: curses.ACS_SBSB    alternate name for vertical line
                             
                             
 -- 資料: curses.ACS_SBSS    alternate name for right tee
                             
                             
 -- 資料: curses.ACS_SSBB    alternate name for lower left corner
                             
                             
 -- 資料: curses.ACS_SSBS    alternate name for bottom tee
                             
                             
 -- 資料: curses.ACS_SSSB    alternate name for left tee
                             
                             
 -- 資料: curses.ACS_SSSS    alternate name for crossover or big plus
                             
                             
 -- 資料:                    pound sterling
          curses.ACS_STERLING

 -- 資料: curses.ACS_TTEE    top tee
                             
                             
 -- 資料:                    up arrow
          curses.ACS_UARROW  

 -- 資料:                    upper left corner
          curses.ACS_ULCORNER

 -- 資料:                    upper right corner
          curses.ACS_URCORNER

 -- 資料: curses.ACS_VLINE   vertical line
                             

The following table lists mouse button constants used by *note
getmouse(): 2ca1.:

Mouse button constant                  含義
                                       
-----------------------------------------------------------------------------------------
                                       
 -- 資料: curses.BUTTONn_PRESSED       Mouse button 'n' pressed
                                       
                                       
 -- 資料: curses.BUTTONn_RELEASED      Mouse button 'n' released
                                       
                                       
 -- 資料: curses.BUTTONn_CLICKED       Mouse button 'n' clicked
                                       
                                       
 -- 資料:                              Mouse button 'n' double clicked
          curses.BUTTONn_DOUBLE_CLICKED

 -- 資料:                              Mouse button 'n' triple clicked
          curses.BUTTONn_TRIPLE_CLICKED

 -- 資料: curses.BUTTON_SHIFT          Shift was down during button state change
                                       
                                       
 -- 資料: curses.BUTTON_CTRL           Control was down during button state change
                                       
                                       
 -- 資料: curses.BUTTON_ALT            Control was down during button state change
                                       

在 3.10 版的變更: The ‘BUTTON5_*’ constants are now exposed if they are
provided by the underlying curses library.

The following table lists the predefined colors:

Constant                      顏色
                              
---------------------------------------------------------------
                              
 -- 資料:                     黑
          curses.COLOR_BLACK  

 -- 資料: curses.COLOR_BLUE   藍
                              
                              
 -- 資料: curses.COLOR_CYAN   Cyan (light greenish blue)
                              
                              
 -- 資料:                     綠
          curses.COLOR_GREEN  

 -- 資料:                     Magenta (purplish red)
          curses.COLOR_MAGENTA

 -- 資料: curses.COLOR_RED    紅
                              
                              
 -- 資料:                     白
          curses.COLOR_WHITE  

 -- 資料:                     Yellow
          curses.COLOR_YELLOW 


File: python.info,  Node: curses textpad --- Text input widget for curses programs,  Next: curses ascii --- ASCII 字元的工具程式,  Prev: curses --- 字元儲存格顯示的終端處理,  Up: 通用作業系統服務

5.16.10 ‘curses.textpad’ -- Text input widget for curses programs
-----------------------------------------------------------------

The *note curses.textpad: 26. module provides a *note Textbox: 2dc8.
class that handles elementary text editing in a curses window,
supporting a set of keybindings resembling those of Emacs (thus, also of
Netscape Navigator, BBedit 6.x, FrameMaker, and many other programs).
The module also provides a rectangle-drawing function useful for framing
text boxes or for other purposes.

The module *note curses.textpad: 26. defines the following function:

 -- 函式: curses.textpad.rectangle (win, uly, ulx, lry, lrx)

     Draw a rectangle.  The first argument must be a window object; the
     remaining arguments are coordinates relative to that window.  The
     second and third arguments are the y and x coordinates of the upper
     left hand corner of the rectangle to be drawn; the fourth and fifth
     arguments are the y and x coordinates of the lower right hand
     corner.  The rectangle will be drawn using VT100/IBM PC forms
     characters on terminals that make this possible (including xterm
     and most other software terminal emulators).  Otherwise it will be
     drawn with ASCII dashes, vertical bars, and plus signs.

* Menu:

* Textbox objects::


File: python.info,  Node: Textbox objects,  Up: curses textpad --- Text input widget for curses programs

5.16.10.1 Textbox objects
.........................

You can instantiate a *note Textbox: 2dc8. object as follows:

 -- 類別: curses.textpad.Textbox (win)

     Return a textbox widget object.  The 'win' argument should be a
     curses *note window: 2cb7. object in which the textbox is to be
     contained.  The edit cursor of the textbox is initially located at
     the upper left hand corner of the containing window, with
     coordinates ‘(0, 0)’.  The instance's *note stripspaces: 2dcc. flag
     is initially on.

     *note Textbox: 2dc8. objects have the following methods:

      -- 方法: edit ([validator])

          This is the entry point you will normally use.  It accepts
          editing keystrokes until one of the termination keystrokes is
          entered.  If 'validator' is supplied, it must be a function.
          It will be called for each keystroke entered with the
          keystroke as a parameter; command dispatch is done on the
          result.  This method returns the window contents as a string;
          whether blanks in the window are included is affected by the
          *note stripspaces: 2dcc. attribute.

      -- 方法: do_command (ch)

          Process a single command keystroke.  Here are the supported
          special keystrokes:

          Keystroke              Action
                                 
          -----------------------------------------------------------------------
                                 
          ‘Control-A’            Go to left edge of window.
                                 
                                 
          ‘Control-B’            Cursor left, wrapping to previous line if
                                 appropriate.
                                 
                                 
          ‘Control-D’            Delete character under cursor.
                                 
                                 
          ‘Control-E’            Go to right edge (stripspaces off) or end of
                                 line (stripspaces on).
                                 
                                 
          ‘Control-F’            Cursor right, wrapping to next line when
                                 appropriate.
                                 
                                 
          ‘Control-G’            Terminate, returning the window contents.
                                 
                                 
          ‘Control-H’            Delete character backward.
                                 
                                 
          ‘Control-J’            Terminate if the window is 1 line, otherwise
                                 insert newline.
                                 
                                 
          ‘Control-K’            If line is blank, delete it, otherwise clear
                                 to end of line.
                                 
                                 
          ‘Control-L’            Refresh screen.
                                 
                                 
          ‘Control-N’            Cursor down; move down one line.
                                 
                                 
          ‘Control-O’            Insert a blank line at cursor location.
                                 
                                 
          ‘Control-P’            Cursor up; move up one line.
                                 

          Move operations do nothing if the cursor is at an edge where
          the movement is not possible.  The following synonyms are
          supported where possible:

          Constant                             Keystroke
                                               
          ------------------------------------------------------------
                                               
          *note KEY_LEFT: 2d40.                ‘Control-B’
                                               
                                               
          *note KEY_RIGHT: 2d41.               ‘Control-F’
                                               
                                               
          *note KEY_UP: 2d3f.                  ‘Control-P’
                                               
                                               
          *note KEY_DOWN: 2d3e.                ‘Control-N’
                                               
                                               
          *note KEY_BACKSPACE: 2d43.           ‘Control-h’
                                               

          All other keystrokes are treated as a command to insert the
          given character and move right (with line wrapping).

      -- 方法: gather ()

          Return the window contents as a string; whether blanks in the
          window are included is affected by the *note stripspaces:
          2dcc. member.

      -- 屬性: stripspaces

          This attribute is a flag which controls the interpretation of
          blanks in the window.  When it is on, trailing blanks on each
          line are ignored; any cursor motion that would land the cursor
          on a trailing blank goes to the end of that line instead, and
          trailing blanks are stripped when the window contents are
          gathered.


File: python.info,  Node: curses ascii --- ASCII 字元的工具程式,  Next: curses panel --- curses 的面板堆疊擴充,  Prev: curses textpad --- Text input widget for curses programs,  Up: 通用作業系統服務

5.16.11 ‘curses.ascii’ -- ASCII 字元的工具程式
----------------------------------------------

'原始碼：'Lib/curses/ascii.py(1)

__________________________________________________________________

The *note curses.ascii: 24. module supplies name constants for ASCII
characters and functions to test membership in various ASCII character
classes.  The constants supplied are names for control characters as
follows:

名稱                含義
                    
-----------------------------------------------------------------------
                    
 -- 資料:
          curses.ascii.NUL

 -- 資料:           Start of heading, console interrupt
          curses.ascii.SOH

 -- 資料:           Start of text
          curses.ascii.STX

 -- 資料:           End of text
          curses.ascii.ETX

 -- 資料:           End of transmission
          curses.ascii.EOT

 -- 資料:           Enquiry, goes with *note ACK: 2dd8. flow control
          curses.ascii.ENQ

 -- 資料:           Acknowledgement
          curses.ascii.ACK

 -- 資料:           Bell
          curses.ascii.BEL

 -- 資料:           Backspace
          curses.ascii.BS

 -- 資料:           Tab
          curses.ascii.TAB

 -- 資料:           Alias for *note TAB: 2ddb.: "Horizontal tab"
          curses.ascii.HT

 -- 資料:           Line feed
          curses.ascii.LF

 -- 資料:           Alias for *note LF: 2ddd.: "New line"
          curses.ascii.NL

 -- 資料:           Vertical tab
          curses.ascii.VT

 -- 資料:           Form feed
          curses.ascii.FF

 -- 資料:           Carriage return
          curses.ascii.CR

 -- 資料:           Shift-out, begin alternate character set
          curses.ascii.SO

 -- 資料:           Shift-in, resume default character set
          curses.ascii.SI

 -- 資料:           Data-link escape
          curses.ascii.DLE

 -- 資料:           XON, for flow control
          curses.ascii.DC1

 -- 資料:           Device control 2, block-mode flow control
          curses.ascii.DC2

 -- 資料:           XOFF, for flow control
          curses.ascii.DC3

 -- 資料:           Device control 4
          curses.ascii.DC4

 -- 資料:           Negative acknowledgement
          curses.ascii.NAK

 -- 資料:           Synchronous idle
          curses.ascii.SYN

 -- 資料:           End transmission block
          curses.ascii.ETB

 -- 資料:           Cancel
          curses.ascii.CAN

 -- 資料:           End of medium
          curses.ascii.EM

 -- 資料:           Substitute
          curses.ascii.SUB

 -- 資料:           Escape
          curses.ascii.ESC

 -- 資料:           File separator
          curses.ascii.FS

 -- 資料:           Group separator
          curses.ascii.GS

 -- 資料:           Record separator, block-mode terminator
          curses.ascii.RS

 -- 資料:           Unit separator
          curses.ascii.US

 -- 資料:           Space
          curses.ascii.SP

 -- 資料:           Delete
          curses.ascii.DEL

Note that many of these have little practical significance in modern
usage.  The mnemonics derive from teleprinter conventions that predate
digital computers.

The module supplies the following functions, patterned on those in the
standard C library:

 -- 函式: curses.ascii.isalnum (c)

     Checks for an ASCII alphanumeric character; it is equivalent to
     ‘isalpha(c) or isdigit(c)’.

 -- 函式: curses.ascii.isalpha (c)

     Checks for an ASCII alphabetic character; it is equivalent to
     ‘isupper(c) or islower(c)’.

 -- 函式: curses.ascii.isascii (c)

     Checks for a character value that fits in the 7-bit ASCII set.

 -- 函式: curses.ascii.isblank (c)

     Checks for an ASCII whitespace character; space or horizontal tab.

 -- 函式: curses.ascii.iscntrl (c)

     Checks for an ASCII control character (in the range 0x00 to 0x1f or
     0x7f).

 -- 函式: curses.ascii.isdigit (c)

     Checks for an ASCII decimal digit, ‘'0'’ through ‘'9'’.  This is
     equivalent to ‘c in string.digits’.

 -- 函式: curses.ascii.isgraph (c)

     Checks for ASCII any printable character except space.

 -- 函式: curses.ascii.islower (c)

     Checks for an ASCII lower-case character.

 -- 函式: curses.ascii.isprint (c)

     Checks for any ASCII printable character including space.

 -- 函式: curses.ascii.ispunct (c)

     Checks for any printable ASCII character which is not a space or an
     alphanumeric character.

 -- 函式: curses.ascii.isspace (c)

     Checks for ASCII white-space characters; space, line feed, carriage
     return, form feed, horizontal tab, vertical tab.

 -- 函式: curses.ascii.isupper (c)

     Checks for an ASCII uppercase letter.

 -- 函式: curses.ascii.isxdigit (c)

     Checks for an ASCII hexadecimal digit.  This is equivalent to ‘c in
     string.hexdigits’.

 -- 函式: curses.ascii.isctrl (c)

     Checks for an ASCII control character (ordinal values 0 to 31).

 -- 函式: curses.ascii.ismeta (c)

     Checks for a non-ASCII character (ordinal values 0x80 and above).

These functions accept either integers or single-character strings; when
the argument is a string, it is first converted using the built-in
function *note ord(): 1de1.

Note that all these functions check ordinal bit values derived from the
character of the string you pass in; they do not actually know anything
about the host machine's character encoding.

The following two functions take either a single-character string or
integer byte value; they return a value of the same type.

 -- 函式: curses.ascii.ascii (c)

     Return the ASCII value corresponding to the low 7 bits of 'c'.

 -- 函式: curses.ascii.ctrl (c)

     Return the control character corresponding to the given character
     (the character bit value is bitwise-anded with 0x1f).

 -- 函式: curses.ascii.alt (c)

     Return the 8-bit character corresponding to the given ASCII
     character (the character bit value is bitwise-ored with 0x80).

The following function takes either a single-character string or integer
value; it returns a string.

 -- 函式: curses.ascii.unctrl (c)

     Return a string representation of the ASCII character 'c'.  If 'c'
     is printable, this string is the character itself.  If the
     character is a control character (0x00-0x1f) the string consists of
     a caret (‘'^'’) followed by the corresponding uppercase letter.  If
     the character is an ASCII delete (0x7f) the string is ‘'^?'’.  If
     the character has its meta bit (0x80) set, the meta bit is
     stripped, the preceding rules applied, and ‘'!'’ prepended to the
     result.

 -- 資料: curses.ascii.controlnames

     A 33-element string array that contains the ASCII mnemonics for the
     thirty-two ASCII control characters from 0 (NUL) to 0x1f (US), in
     order, plus the mnemonic ‘SP’ for the space character.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/curses/ascii.py


File: python.info,  Node: curses panel --- curses 的面板堆疊擴充,  Next: platform --- 對底層平臺識別資料的存取,  Prev: curses ascii --- ASCII 字元的工具程式,  Up: 通用作業系統服務

5.16.12 ‘curses.panel’ -- curses 的面板堆疊擴充
-----------------------------------------------

__________________________________________________________________

Panels are windows with the added feature of depth, so they can be
stacked on top of each other, and only the visible portions of each
window will be displayed.  Panels can be added, moved up or down in the
stack, and removed.

* Menu:

* 函式: 函式<6>.
* Panel Objects::


File: python.info,  Node: 函式<6>,  Next: Panel Objects,  Up: curses panel --- curses 的面板堆疊擴充

5.16.12.1 函式
..............

The module *note curses.panel: 25. defines the following functions:

 -- 函式: curses.panel.bottom_panel ()

     Returns the bottom panel in the panel stack.

 -- 函式: curses.panel.new_panel (win)

     Returns a panel object, associating it with the given window 'win'.
     Be aware that you need to keep the returned panel object referenced
     explicitly.  If you don't, the panel object is garbage collected
     and removed from the panel stack.

 -- 函式: curses.panel.top_panel ()

     Returns the top panel in the panel stack.

 -- 函式: curses.panel.update_panels ()

     Updates the virtual screen after changes in the panel stack.  This
     does not call *note curses.doupdate(): 2c96, so you'll have to do
     this yourself.


File: python.info,  Node: Panel Objects,  Prev: 函式<6>,  Up: curses panel --- curses 的面板堆疊擴充

5.16.12.2 Panel Objects
.......................

Panel objects, as returned by *note new_panel(): 2e0f. above, are
windows with a stacking order.  There's always a window associated with
a panel which determines the content, while the panel methods are
responsible for the window's depth in the panel stack.

Panel objects have the following methods:

 -- 方法: Panel.above ()

     Returns the panel above the current panel.

 -- 方法: Panel.below ()

     Returns the panel below the current panel.

 -- 方法: Panel.bottom ()

     Push the panel to the bottom of the stack.

 -- 方法: Panel.hidden ()

     Returns ‘True’ if the panel is hidden (not visible), ‘False’
     otherwise.

 -- 方法: Panel.hide ()

     Hide the panel.  This does not delete the object, it just makes the
     window on screen invisible.

 -- 方法: Panel.move (y, x)

     Move the panel to the screen coordinates ‘(y, x)’.

 -- 方法: Panel.replace (win)

     Change the window associated with the panel to the window 'win'.

 -- 方法: Panel.set_userptr (obj)

     Set the panel's user pointer to 'obj'.  This is used to associate
     an arbitrary piece of data with the panel, and can be any Python
     object.

 -- 方法: Panel.show ()

     Display the panel (which might have been hidden).

 -- 方法: Panel.top ()

     Push panel to the top of the stack.

 -- 方法: Panel.userptr ()

     Returns the user pointer for the panel.  This might be any Python
     object.

 -- 方法: Panel.window ()

     Returns the window object associated with the panel.


File: python.info,  Node: platform --- 對底層平臺識別資料的存取,  Next: errno --- 標準 errno 系統符號,  Prev: curses panel --- curses 的面板堆疊擴充,  Up: 通用作業系統服務

5.16.13 ‘platform’ -- 對底層平臺識別資料的存取
----------------------------------------------

'原始碼：'Lib/platform.py(1)

__________________________________________________________________

     備註: 特定平臺清單為按字母順序排列，Linux 包括在 Unix 小節之中。

* Menu:

* 跨平台::
* Java 平台::
* Windows 平台::
* macOS 平台::
* iOS Platform::
* Unix 平台::
* Linux 平台::
* Android Platform::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/platform.py


File: python.info,  Node: 跨平台,  Next: Java 平台,  Up: platform --- 對底層平臺識別資料的存取

5.16.13.1 跨平台
................

 -- 函式: platform.architecture (executable=sys.executable, bits='',
          linkage='')

     查詢給定的可執行檔案（預設為 Python 直譯器二進位制檔案）來獲取各種
     架構資訊。

     回傳一個 tuple（元組） ‘(bits, linkage)’，其中包含可執行檔案所使用
     的位元架構和連結格式資訊。這兩個值均以字串形式回傳。

     無法確定的值將回傳參數所給定之預先設置值。如果給定的位元為 ‘''’，則
     會使用 ‘sizeof(pointer)’（或者當 Python 版本 < 1.5.2 時為
     ‘sizeof(long)’）作為所支援指標大小的指示器 (indicator)。

     此函式依賴於系統的 ‘file’ 命令來執行實際的操作。這在幾乎所有 Unix 平
     臺和某些非 Unix 平臺上，只有當可執行檔案指向 Python 直譯器時才可使
     用。當以上要求不滿足時將會使用合理的預設值。

          備註: 在 macOS（也許還有其他平臺）上，可執行檔案可能是包含多種
          架構的通用檔案。

          要獲取當前直譯器的 "64 位元性 (64-bitness)"，更可靠的做法是查
          詢 *note sys.maxsize: 115d. 屬性：

               is_64bits = sys.maxsize > 2**32

 -- 函式: platform.machine ()

     回傳機器種類，例如 ‘'AMD64'’。如果該值無法確定則會回傳一個空字串。

 -- 函式: platform.node ()

     回傳電腦的網路名稱（可能不是完整名稱！）。如果該值無法確定則會回傳
     一個空字串。

 -- 函式: platform.platform (aliased=False, terse=False)

     會儘可能附帶有用資訊地回傳一個標識底層平臺的字串。

     輸出應為'人類易讀的 (human readable)'，而非機器易剖析的 (machine
     parseable)。它在不同平臺上看起來可能不一致，這是有意為之的。

     如果 'aliased' 為真值，此函式將使用各種不同於平臺通用名稱的別名來回
     報系統名稱，例如 SunOS 將被回報為 Solaris。*note system_alias():
     2e25. 函式被用於實作此功能。

     將 'terse' 設為真值將導致此函式只回傳標識平臺所需的最小量資訊。

     在 3.8 版的變更: 在 macOS 上，如果 *note mac_ver(): 193a. 回傳的釋
     出版字串非空字串，此函式現在會使用它以獲取 macOS 版本而非 darwin 版
     本。

 -- 函式: platform.processor ()

     回傳（真實的）處理器名稱，例如 ‘'amdk6'’。

     如果該值無法確定則將回傳空字串。請注意，許多平臺都不提供此資訊或是
     簡單地回傳與 *note machine(): 2e23. 相同的值。NetBSD 則會提供此資訊
     。

 -- 函式: platform.python_build ()

     回傳一個 tuple ‘(buildno, builddate)’，表示字串形式的 Python 建置編
     號和日期。

 -- 函式: platform.python_compiler ()

     回傳一個標識用於編譯 Python 的編譯器的字串。

 -- 函式: platform.python_branch ()

     回傳一個標識 Python 實作 SCM 分支的字串。

 -- 函式: platform.python_implementation ()

     回傳一個標識 Python 實作的字串。可能的回傳值有：'CPython'、
     'IronPython'、'Jython'、'PyPy'。

 -- 函式: platform.python_revision ()

     回傳一個標識 Python 實作 SCM 修訂版的字串。

 -- 函式: platform.python_version ()

     將 Python 版本以字串 ‘'major.minor.patchlevel'’ 形式回傳。

     請注意此回傳值不同於 Python ‘sys.version’，它總是會包括 patchlevel（
     預設為 ‘'0'’）。

 -- 函式: platform.python_version_tuple ()

     將 Python 版本以字串 tuple ‘(major, minor, patchlevel)’ 形式回傳。

     請注意此回傳值不同於 Python ‘sys.version’，它總是會包括 patchlevel（
     預設為 ‘'0'’）。

 -- 函式: platform.release ()

     回傳系統的釋出版本，例如 ‘'2.2.0'’ 或 ‘'NT'’，如果該值無法確定則將
     回傳一個空字串。

 -- 函式: platform.system ()

     回傳系統/OS 的名稱，例如 ‘'Linux'’、‘'Darwin'’、‘'Java'’、
     ‘'Windows'’。如果該值無法確定則回傳一個空字串。

     On iOS and Android, this returns the user-facing OS name (i.e,
     ‘'iOS’, ‘'iPadOS'’ or ‘'Android'’).  To obtain the kernel name
     (‘'Darwin'’ or ‘'Linux'’), use *note os.uname(): 10ae.

 -- 函式: platform.system_alias (system, release, version)

     回傳做為某些系統所使用的常見行銷名稱之別名的 ‘(system, release,
     version)’。它還會在可能導致混淆的情況下對資訊進行一些重新排序。

 -- 函式: platform.version ()

     回傳系統的釋出版本資訊，例如 ‘'#3 on degas'’。如果該值無法確定則將
     回傳一個空字串。

     On iOS and Android, this is the user-facing OS version.  To obtain
     the Darwin or Linux kernel version, use *note os.uname(): 10ae.

 -- 函式: platform.uname ()

     具有高可攜性 (portable) 的 uname 介面。回傳包含六個屬性的 *note
     namedtuple(): 1ae.：*note system: 1d54.、*note node: 2e24.、*note
     release: 2e2e.、*note version: 2e2f.、*note machine: 2e23. 和 *note
     processor: 2e26.。

     *note processor: 2e26. 會延遲解析，有需求時才會解析

     注意：前兩個屬性名稱與 *note os.uname(): 10ae. 提供的名稱不同，它們
     分別命名為 ‘sysname’ 和 ‘nodename’。

     無法確定的條目會被設為 ‘''’。

     在 3.3 版的變更: 將結果從 tuple 改為 *note namedtuple(): 1ae.。

     在 3.9 版的變更: *note processor: 2e26. 會延遲解析，並非立即解析。


File: python.info,  Node: Java 平台,  Next: Windows 平台,  Prev: 跨平台,  Up: platform --- 對底層平臺識別資料的存取

5.16.13.2 Java 平台
...................

 -- 函式: platform.java_ver (release='', vendor='', vminfo=('', '', ''),
          osinfo=('', '', ''))

     Jython 的版本介面。

     回傳一個 tuple ‘(release, vendor, vminfo, osinfo)’，其中 'vminfo' 為
     tuple ‘(vm_name, vm_release, vm_vendor)’ 而 'osinfo' 為 tuple
     ‘(os_name, os_version, os_arch)’。無法確定的值將被設為由參數所給定
     的預設值（預設均為 ‘''’）。

     Deprecated since version 3.13, will be removed in version 3.15: It
     was largely untested, had a confusing API, and was only useful for
     Jython support.


File: python.info,  Node: Windows 平台,  Next: macOS 平台,  Prev: Java 平台,  Up: platform --- 對底層平臺識別資料的存取

5.16.13.3 Windows 平台
......................

 -- 函式: platform.win32_ver (release='', version='', csd='', ptype='')

     從 Windows 登錄檔 (Window Registry) 獲取額外的版本資訊並回傳一個
     tuple ‘(release, version, csd, ptype)’，它代表 OS 發行版、版本號、
     CSD 級別 (service pack) 和 OS 類型（多個/單個處理器）。

     一點提示：'ptype' 在單個處理器的 NT 機器上為 ‘'Uniprocessor Free'’，
     而在多個處理器的機器上為 ‘'Multiprocessor Free'’。‘'Free'’ 是指該
     OS 版本沒有除錯程式。它也可能以 ‘'Checked'’ 表示，代表該 OS 版本使
     用了除錯程式，即檢查引數、範圍等的程式。

 -- 函式: platform.win32_edition ()

     回傳一個代表當前 Windows 版本的字串。可能的值包括但不限於
     ‘'Enterprise'’、‘'IoTUAP'’、‘'ServerStandard'’ 和 ‘'nanoserver'’。

     在 3.8 版被加入.

 -- 函式: platform.win32_is_iot ()

     如果 *note win32_edition(): 2e32. 回傳的 Windows 版本被識別為 IoT 版
     則回傳 ‘True’。

     在 3.8 版被加入.


File: python.info,  Node: macOS 平台,  Next: iOS Platform,  Prev: Windows 平台,  Up: platform --- 對底層平臺識別資料的存取

5.16.13.4 macOS 平台
....................

 -- 函式: platform.mac_ver (release='', versioninfo=('', '', ''),
          machine='')

     獲取 Mac OS 版本資訊並將其回傳為 tuple ‘(release, versioninfo,
     machine)’，其中 'versioninfo' 是一個 tuple ‘(version, dev_stage,
     non_release_version)’。

     無法確定的條目會被設為 ‘''’。所有 tuple 條目均為字串。


File: python.info,  Node: iOS Platform,  Next: Unix 平台,  Prev: macOS 平台,  Up: platform --- 對底層平臺識別資料的存取

5.16.13.5 iOS Platform
......................

 -- 函式: platform.ios_ver (system='', release='', model='',
          is_simulator=False)

     Get iOS version information and return it as a *note namedtuple():
     1ae. with the following attributes:

        * ‘system’ is the OS name; either ‘'iOS'’ or ‘'iPadOS'’.

        * ‘release’ is the iOS version number as a string (e.g.,
          ‘'17.2'’).

        * ‘model’ is the device model identifier; this will be a string
          like ‘'iPhone13,2'’ for a physical device, or ‘'iPhone'’ on a
          simulator.

        * ‘is_simulator’ is a boolean describing if the app is running
          on a simulator or a physical device.

     Entries which cannot be determined are set to the defaults given as
     parameters.


File: python.info,  Node: Unix 平台,  Next: Linux 平台,  Prev: iOS Platform,  Up: platform --- 對底層平臺識別資料的存取

5.16.13.6 Unix 平台
...................

 -- 函式: platform.libc_ver (executable=sys.executable, lib='',
          version='', chunksize=16384)

     嘗試確認可執行檔案（預設為 Python 直譯器）所連結到的 libc 版本。回
     傳一個字串 tuple ‘(lib, version)’，當查詢失敗時其預設值將被設為給定
     的參數值。

     請注意，此函式對於不同 libc 版本如何為可執行檔案新增符號的方式有深
     層的關聯，可能僅適用於以 ‘gcc’ 編譯出來的可執行檔案。

     檔案會以 'chunksize' 位元組大小的分塊 (chunk) 來讀取和掃描。


File: python.info,  Node: Linux 平台,  Next: Android Platform,  Prev: Unix 平台,  Up: platform --- 對底層平臺識別資料的存取

5.16.13.7 Linux 平台
....................

 -- 函式: platform.freedesktop_os_release ()

     從 ‘os-release’ 檔案獲取作業系統標識，並將其作為一個字典回傳。
     ‘os-release’ 檔案為 freedesktop.org 標準(1)、並在大多數 Linux 發行
     版上可用。一個重要的例外是 Android 和基於 Android 的發行版。

     當 ‘/etc/os-release’ 與 ‘/usr/lib/os-release’ 均無法被讀取時將引發
     *note OSError: 350. 或其子類別。

     成功時，該函式將回傳一個字典，其中鍵和值均為字串。值當中的特殊字元
     例如 ‘"’ 和 ‘$’ 會被移除引號 (unquoted)。欄位 ‘NAME’、‘ID’ 和
     ‘PRETTY_NAME’ 總會按照標準來定義。所有其他欄位都是可選的。根據不同
     廠商可能會包括額外的欄位。

     請注意 ‘NAME’、‘VERSION’ 和 ‘VARIANT’ 等欄位是適用於向使用者展示的
     字串。程式應當使用 ‘ID’、‘ID_LIKE’、‘VERSION_ID’ 或 ‘VARIANT_ID’ 等
     欄位來標識 Linux 發行版。

     範例：

          def get_like_distro():
              info = platform.freedesktop_os_release()
              ids = [info["ID"]]
              if "ID_LIKE" in info:
                  # ids are space separated and ordered by precedence
                  ids.extend(info["ID_LIKE"].split())
              return ids

     在 3.10 版被加入.

   ---------- Footnotes ----------

   (1) https://www.freedesktop.org/software/systemd/man/os-release.html


File: python.info,  Node: Android Platform,  Prev: Linux 平台,  Up: platform --- 對底層平臺識別資料的存取

5.16.13.8 Android Platform
..........................

 -- 函式: platform.android_ver (release='', api_level=0,
          manufacturer='', model='', device='', is_emulator=False)

     Get Android device information.  Returns a *note namedtuple(): 1ae.
     with the following attributes.  Values which cannot be determined
     are set to the defaults given as parameters.

        * ‘release’ - Android version, as a string (e.g.  ‘"14"’).

        * ‘api_level’ - API level of the running device, as an integer
          (e.g.  ‘34’ for Android 14).  To get the API level which
          Python was built against, see *note sys.getandroidapilevel():
          b30.

        * ‘manufacturer’ - Manufacturer name(1).

        * ‘model’ - Model name(2) – typically the marketing name or
          model number.

        * ‘device’ - Device name(3) – typically the model number or a
          codename.

        * ‘is_emulator’ - ‘True’ if the device is an emulator; ‘False’
          if it's a physical device.

     Google maintains a list of known model and device names(4).

     在 3.13 版被加入.

   ---------- Footnotes ----------

   (1) 
https://developer.android.com/reference/android/os/Build#MANUFACTURER

   (2) https://developer.android.com/reference/android/os/Build#MODEL

   (3) https://developer.android.com/reference/android/os/Build#DEVICE

   (4) https://storage.googleapis.com/play_public/supported_devices.html


File: python.info,  Node: errno --- 標準 errno 系統符號,  Next: ctypes --- 用於 Python 的外部函式庫,  Prev: platform --- 對底層平臺識別資料的存取,  Up: 通用作業系統服務

5.16.14 ‘errno’ -- 標準 errno 系統符號
--------------------------------------

__________________________________________________________________

This module makes available standard ‘errno’ system symbols.  The value
of each symbol is the corresponding integer value.  The names and
descriptions are borrowed from ‘linux/include/errno.h’, which should be
all-inclusive.

 -- 資料: errno.errorcode

     Dictionary providing a mapping from the errno value to the string
     name in the underlying system.  For instance,
     ‘errno.errorcode[errno.EPERM]’ maps to ‘'EPERM'’.

To translate a numeric error code to an error message, use *note
os.strerror(): 2a0f.

Of the following list, symbols that are not used on the current platform
are not defined by the module.  The specific list of defined symbols is
available as ‘errno.errorcode.keys()’.  Symbols available can include:

 -- 資料: errno.EPERM

     Operation not permitted.  This error is mapped to the exception
     *note PermissionError: ce9.

 -- 資料: errno.ENOENT

     No such file or directory.  This error is mapped to the exception
     *note FileNotFoundError: e67.

 -- 資料: errno.ESRCH

     No such process.  This error is mapped to the exception *note
     ProcessLookupError: ffe.

 -- 資料: errno.EINTR

     Interrupted system call.  This error is mapped to the exception
     *note InterruptedError: d2e.

 -- 資料: errno.EIO

     I/O error

 -- 資料: errno.ENXIO

     No such device or address

 -- 資料: errno.E2BIG

     Arg list too long

 -- 資料: errno.ENOEXEC

     Exec format error

 -- 資料: errno.EBADF

     Bad file number

 -- 資料: errno.ECHILD

     No child processes.  This error is mapped to the exception *note
     ChildProcessError: ffb.

 -- 資料: errno.EAGAIN

     Try again.  This error is mapped to the exception *note
     BlockingIOError: ffa.

 -- 資料: errno.ENOMEM

     Out of memory

 -- 資料: errno.EACCES

     Permission denied.  This error is mapped to the exception *note
     PermissionError: ce9.

 -- 資料: errno.EFAULT

     Bad address

 -- 資料: errno.ENOTBLK

     Block device required

 -- 資料: errno.EBUSY

     Device or resource busy

 -- 資料: errno.EEXIST

     File exists.  This error is mapped to the exception *note
     FileExistsError: fc3.

 -- 資料: errno.EXDEV

     Cross-device link

 -- 資料: errno.ENODEV

     No such device

 -- 資料: errno.ENOTDIR

     Not a directory.  This error is mapped to the exception *note
     NotADirectoryError: ffd.

 -- 資料: errno.EISDIR

     Is a directory.  This error is mapped to the exception *note
     IsADirectoryError: ffc.

 -- 資料: errno.EINVAL

     Invalid argument

 -- 資料: errno.ENFILE

     File table overflow

 -- 資料: errno.EMFILE

     Too many open files

 -- 資料: errno.ENOTTY

     Not a typewriter

 -- 資料: errno.ETXTBSY

     Text file busy

 -- 資料: errno.EFBIG

     File too large

 -- 資料: errno.ENOSPC

     No space left on device

 -- 資料: errno.ESPIPE

     Illegal seek

 -- 資料: errno.EROFS

     Read-only file system

 -- 資料: errno.EMLINK

     Too many links

 -- 資料: errno.EPIPE

     Broken pipe.  This error is mapped to the exception *note
     BrokenPipeError: fff.

 -- 資料: errno.EDOM

     Math argument out of domain of func

 -- 資料: errno.ERANGE

     Math result not representable

 -- 資料: errno.EDEADLK

     Resource deadlock would occur

 -- 資料: errno.ENAMETOOLONG

     File name too long

 -- 資料: errno.ENOLCK

     No record locks available

 -- 資料: errno.ENOSYS

     Function not implemented

 -- 資料: errno.ENOTEMPTY

     Directory not empty

 -- 資料: errno.ELOOP

     Too many symbolic links encountered

 -- 資料: errno.EWOULDBLOCK

     Operation would block.  This error is mapped to the exception *note
     BlockingIOError: ffa.

 -- 資料: errno.ENOMSG

     No message of desired type

 -- 資料: errno.EIDRM

     Identifier removed

 -- 資料: errno.ECHRNG

     Channel number out of range

 -- 資料: errno.EL2NSYNC

     Level 2 not synchronized

 -- 資料: errno.EL3HLT

     Level 3 halted

 -- 資料: errno.EL3RST

     Level 3 reset

 -- 資料: errno.ELNRNG

     Link number out of range

 -- 資料: errno.EUNATCH

     Protocol driver not attached

 -- 資料: errno.ENOCSI

     No CSI structure available

 -- 資料: errno.EL2HLT

     Level 2 halted

 -- 資料: errno.EBADE

     Invalid exchange

 -- 資料: errno.EBADR

     Invalid request descriptor

 -- 資料: errno.EXFULL

     Exchange full

 -- 資料: errno.ENOANO

     No anode

 -- 資料: errno.EBADRQC

     Invalid request code

 -- 資料: errno.EBADSLT

     Invalid slot

 -- 資料: errno.EDEADLOCK

     File locking deadlock error

 -- 資料: errno.EBFONT

     Bad font file format

 -- 資料: errno.ENOSTR

     Device not a stream

 -- 資料: errno.ENODATA

     No data available

 -- 資料: errno.ETIME

     Timer expired

 -- 資料: errno.ENOSR

     Out of streams resources

 -- 資料: errno.ENONET

     Machine is not on the network

 -- 資料: errno.ENOPKG

     Package not installed

 -- 資料: errno.EREMOTE

     Object is remote

 -- 資料: errno.ENOLINK

     Link has been severed

 -- 資料: errno.EADV

     Advertise error

 -- 資料: errno.ESRMNT

     Srmount error

 -- 資料: errno.ECOMM

     Communication error on send

 -- 資料: errno.EPROTO

     Protocol error

 -- 資料: errno.EMULTIHOP

     Multihop attempted

 -- 資料: errno.EDOTDOT

     RFS specific error

 -- 資料: errno.EBADMSG

     Not a data message

 -- 資料: errno.EOVERFLOW

     Value too large for defined data type

 -- 資料: errno.ENOTUNIQ

     Name not unique on network

 -- 資料: errno.EBADFD

     File descriptor in bad state

 -- 資料: errno.EREMCHG

     Remote address changed

 -- 資料: errno.ELIBACC

     Can not access a needed shared library

 -- 資料: errno.ELIBBAD

     Accessing a corrupted shared library

 -- 資料: errno.ELIBSCN

     .lib section in a.out corrupted

 -- 資料: errno.ELIBMAX

     Attempting to link in too many shared libraries

 -- 資料: errno.ELIBEXEC

     Cannot exec a shared library directly

 -- 資料: errno.EILSEQ

     Illegal byte sequence

 -- 資料: errno.ERESTART

     Interrupted system call should be restarted

 -- 資料: errno.ESTRPIPE

     Streams pipe error

 -- 資料: errno.EUSERS

     Too many users

 -- 資料: errno.ENOTSOCK

     Socket operation on non-socket

 -- 資料: errno.EDESTADDRREQ

     Destination address required

 -- 資料: errno.EMSGSIZE

     Message too long

 -- 資料: errno.EPROTOTYPE

     Protocol wrong type for socket

 -- 資料: errno.ENOPROTOOPT

     Protocol not available

 -- 資料: errno.EPROTONOSUPPORT

     Protocol not supported

 -- 資料: errno.ESOCKTNOSUPPORT

     Socket type not supported

 -- 資料: errno.EOPNOTSUPP

     Operation not supported on transport endpoint

 -- 資料: errno.ENOTSUP

     Operation not supported

     在 3.2 版被加入.

 -- 資料: errno.EPFNOSUPPORT

     Protocol family not supported

 -- 資料: errno.EAFNOSUPPORT

     Address family not supported by protocol

 -- 資料: errno.EADDRINUSE

     Address already in use

 -- 資料: errno.EADDRNOTAVAIL

     Cannot assign requested address

 -- 資料: errno.ENETDOWN

     Network is down

 -- 資料: errno.ENETUNREACH

     Network is unreachable

 -- 資料: errno.ENETRESET

     Network dropped connection because of reset

 -- 資料: errno.ECONNABORTED

     Software caused connection abort.  This error is mapped to the
     exception *note ConnectionAbortedError: 1000.

 -- 資料: errno.ECONNRESET

     Connection reset by peer.  This error is mapped to the exception
     *note ConnectionResetError: 1002.

 -- 資料: errno.ENOBUFS

     No buffer space available

 -- 資料: errno.EISCONN

     Transport endpoint is already connected

 -- 資料: errno.ENOTCONN

     Transport endpoint is not connected

 -- 資料: errno.ESHUTDOWN

     Cannot send after transport endpoint shutdown.  This error is
     mapped to the exception *note BrokenPipeError: fff.

 -- 資料: errno.ETOOMANYREFS

     Too many references: cannot splice

 -- 資料: errno.ETIMEDOUT

     Connection timed out.  This error is mapped to the exception *note
     TimeoutError: 7d9.

 -- 資料: errno.ECONNREFUSED

     Connection refused.  This error is mapped to the exception *note
     ConnectionRefusedError: 1001.

 -- 資料: errno.EHOSTDOWN

     Host is down

 -- 資料: errno.EHOSTUNREACH

     No route to host

 -- 資料: errno.EALREADY

     Operation already in progress.  This error is mapped to the
     exception *note BlockingIOError: ffa.

 -- 資料: errno.EINPROGRESS

     Operation now in progress.  This error is mapped to the exception
     *note BlockingIOError: ffa.

 -- 資料: errno.ESTALE

     Stale NFS file handle

 -- 資料: errno.EUCLEAN

     Structure needs cleaning

 -- 資料: errno.ENOTNAM

     Not a XENIX named type file

 -- 資料: errno.ENAVAIL

     No XENIX semaphores available

 -- 資料: errno.EISNAM

     Is a named type file

 -- 資料: errno.EREMOTEIO

     Remote I/O error

 -- 資料: errno.EDQUOT

     Quota exceeded

 -- 資料: errno.EQFULL

     Interface output queue is full

     在 3.11 版被加入.

 -- 資料: errno.ENOTCAPABLE

     Capabilities insufficient.  This error is mapped to the exception
     *note PermissionError: ce9.

     *note 適用: 1c56.：WASI, FreeBSD

     在 3.11.1 版被加入.

 -- 資料: errno.ECANCELED

     Operation canceled

     在 3.2 版被加入.

 -- 資料: errno.EOWNERDEAD

     Owner died

     在 3.2 版被加入.

 -- 資料: errno.ENOTRECOVERABLE

     State not recoverable

     在 3.2 版被加入.


File: python.info,  Node: ctypes --- 用於 Python 的外部函式庫,  Prev: errno --- 標準 errno 系統符號,  Up: 通用作業系統服務

5.16.15 ‘ctypes’ -- 用於 Python 的外部函式庫
--------------------------------------------

'原始碼：'Lib/ctypes(1)

__________________________________________________________________

*note ctypes: 22. is a foreign function library for Python.  It provides
C compatible data types, and allows calling functions in DLLs or shared
libraries.  It can be used to wrap these libraries in pure Python.

* Menu:

* ctypes 教學::
* ctypes reference::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/ctypes


File: python.info,  Node: ctypes 教學,  Next: ctypes reference,  Up: ctypes --- 用於 Python 的外部函式庫

5.16.15.1 ctypes 教學
.....................

Note: The code samples in this tutorial use *note doctest: 31. to make
sure that they actually work.  Since some code samples behave
differently under Linux, Windows, or macOS, they contain doctest
directives in comments.

Note: Some code samples reference the ctypes *note c_int: 2ea6. type.
On platforms where ‘sizeof(long) == sizeof(int)’ it is an alias to *note
c_long: 2ea7.  So, you should not be confused if *note c_long: 2ea7. is
printed if you would expect *note c_int: 2ea6. -- they are actually the
same type.

* Menu:

* Loading dynamic link libraries::
* Accessing functions from loaded dlls::
* 呼叫函式::
* Fundamental data types::
* Calling functions, continued: Calling functions continued.
* Calling variadic functions::
* Calling functions with your own custom data types::
* Specifying the required argument types (function prototypes): Specifying the required argument types function prototypes.
* Return types::
* Passing pointers (or; passing parameters by reference): Passing pointers or passing parameters by reference.
* Structures and unions::
* Structure/union alignment and byte order::
* Bit fields in structures and unions::
* Arrays::
* Pointers::
* Type conversions::
* Incomplete Types::
* 回呼函式::
* Accessing values exported from dlls::
* Surprises::
* Variable-sized data types::


File: python.info,  Node: Loading dynamic link libraries,  Next: Accessing functions from loaded dlls,  Up: ctypes 教學

5.16.15.2 Loading dynamic link libraries
........................................

*note ctypes: 22. exports the 'cdll', and on Windows 'windll' and
'oledll' objects, for loading dynamic link libraries.

You load libraries by accessing them as attributes of these objects.
'cdll' loads libraries which export functions using the standard ‘cdecl’
calling convention, while 'windll' libraries call functions using the
‘stdcall’ calling convention.  'oledll' also uses the ‘stdcall’ calling
convention, and assumes the functions return a Windows ‘HRESULT’ error
code.  The error code is used to automatically raise an *note OSError:
350. exception when the function call fails.

在 3.3 版的變更: Windows errors used to raise *note WindowsError: ff7,
which is now an alias of *note OSError: 350.

Here are some examples for Windows.  Note that ‘msvcrt’ is the MS
standard C library containing most standard C functions, and uses the
cdecl calling convention:

     >>> from ctypes import *
     >>> print(windll.kernel32)
     <WinDLL 'kernel32', handle ... at ...>
     >>> print(cdll.msvcrt)
     <CDLL 'msvcrt', handle ... at ...>
     >>> libc = cdll.msvcrt
     >>>

Windows appends the usual ‘.dll’ file suffix automatically.

     備註: Accessing the standard C library through ‘cdll.msvcrt’ will
     use an outdated version of the library that may be incompatible
     with the one being used by Python.  Where possible, use native
     Python functionality, or else import and use the ‘msvcrt’ module.

On Linux, it is required to specify the filename 'including' the
extension to load a library, so attribute access can not be used to load
libraries.  Either the *note LoadLibrary(): 2eaa. method of the dll
loaders should be used, or you should load the library by creating an
instance of CDLL by calling the constructor:

     >>> cdll.LoadLibrary("libc.so.6")
     <CDLL 'libc.so.6', handle ... at ...>
     >>> libc = CDLL("libc.so.6")
     >>> libc
     <CDLL 'libc.so.6', handle ... at ...>
     >>>


File: python.info,  Node: Accessing functions from loaded dlls,  Next: 呼叫函式,  Prev: Loading dynamic link libraries,  Up: ctypes 教學

5.16.15.3 Accessing functions from loaded dlls
..............................................

Functions are accessed as attributes of dll objects:

     >>> libc.printf
     <_FuncPtr object at 0x...>
     >>> print(windll.kernel32.GetModuleHandleA)
     <_FuncPtr object at 0x...>
     >>> print(windll.kernel32.MyOwnFunction)
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
       File "ctypes.py", line 239, in __getattr__
         func = _StdcallFuncPtr(name, self)
     AttributeError: function 'MyOwnFunction' not found
     >>>

Note that win32 system dlls like ‘kernel32’ and ‘user32’ often export
ANSI as well as UNICODE versions of a function.  The UNICODE version is
exported with a ‘W’ appended to the name, while the ANSI version is
exported with an ‘A’ appended to the name.  The win32 ‘GetModuleHandle’
function, which returns a 'module handle' for a given module name, has
the following C prototype, and a macro is used to expose one of them as
‘GetModuleHandle’ depending on whether UNICODE is defined or not:

     /* ANSI 版本 */
     HMODULE GetModuleHandleA(LPCSTR lpModuleName);
     /* UNICODE 版本 */
     HMODULE GetModuleHandleW(LPCWSTR lpModuleName);

'windll' does not try to select one of them by magic, you must access
the version you need by specifying ‘GetModuleHandleA’ or
‘GetModuleHandleW’ explicitly, and then call it with bytes or string
objects respectively.

Sometimes, dlls export functions with names which aren't valid Python
identifiers, like ‘"??2@YAPAXI@Z"’.  In this case you have to use *note
getattr(): b78. to retrieve the function:

     >>> getattr(cdll.msvcrt, "??2@YAPAXI@Z")
     <_FuncPtr object at 0x...>
     >>>

On Windows, some dlls export functions not by name but by ordinal.
These functions can be accessed by indexing the dll object with the
ordinal number:

     >>> cdll.kernel32[1]
     <_FuncPtr object at 0x...>
     >>> cdll.kernel32[0]
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
       File "ctypes.py", line 310, in __getitem__
         func = _StdcallFuncPtr(name, self)
     AttributeError: function ordinal 0 not found
     >>>


File: python.info,  Node: 呼叫函式,  Next: Fundamental data types,  Prev: Accessing functions from loaded dlls,  Up: ctypes 教學

5.16.15.4 呼叫函式
..................

You can call these functions like any other Python callable.  This
example uses the ‘rand()’ function, which takes no arguments and returns
a pseudo-random integer:

     >>> print(libc.rand())
     1804289383

On Windows, you can call the ‘GetModuleHandleA()’ function, which
returns a win32 module handle (passing ‘None’ as single argument to call
it with a ‘NULL’ pointer):

     >>> print(hex(windll.kernel32.GetModuleHandleA(None)))
     0x1d000000
     >>>

*note ValueError: 1e7. is raised when you call an ‘stdcall’ function
with the ‘cdecl’ calling convention, or vice versa:

     >>> cdll.kernel32.GetModuleHandleA(None)
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     ValueError: Procedure probably called with not enough arguments (4 bytes missing)
     >>>

     >>> windll.msvcrt.printf(b"spam")
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     ValueError: Procedure probably called with too many arguments (4 bytes in excess)
     >>>

To find out the correct calling convention you have to look into the C
header file or the documentation for the function you want to call.

On Windows, *note ctypes: 22. uses win32 structured exception handling
to prevent crashes from general protection faults when functions are
called with invalid argument values:

     >>> windll.kernel32.GetModuleHandleA(32)
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     OSError: exception: access violation reading 0x00000020
     >>>

There are, however, enough ways to crash Python with *note ctypes: 22,
so you should be careful anyway.  The *note faulthandler: 4e. module can
be helpful in debugging crashes (e.g.  from segmentation faults produced
by erroneous C library calls).

‘None’, integers, bytes objects and (unicode) strings are the only
native Python objects that can directly be used as parameters in these
function calls.  ‘None’ is passed as a C ‘NULL’ pointer, bytes objects
and strings are passed as pointer to the memory block that contains
their data (char* or wchar_t*).  Python integers are passed as the
platform's default C int type, their value is masked to fit into the C
type.

Before we move on calling functions with other parameter types, we have
to learn more about *note ctypes: 22. data types.


File: python.info,  Node: Fundamental data types,  Next: Calling functions continued,  Prev: 呼叫函式,  Up: ctypes 教學

5.16.15.5 Fundamental data types
................................

*note ctypes: 22. defines a number of primitive C compatible data types:

ctypes 型別                C 型別                                         Python 型別
                                                                          
-----------------------------------------------------------------------------------------------------------
                                                                          
*note c_bool: 2eb1.        _Bool                                          bool (1)
                                                                          
                                                                          
*note c_char: 2eb2.        char                                           1-character bytes object
                                                                          
                                                                          
*note c_wchar: 2eb3.       ‘wchar_t’                                      1-character string
                                                                          
                                                                          
*note c_byte: 1673.        char                                           int
                                                                          
                                                                          
*note c_ubyte: 1674.       unsigned char                                  int
                                                                          
                                                                          
*note c_short: 2eb4.       short                                          int
                                                                          
                                                                          
*note c_ushort: 2eb5.      unsigned short                                 int
                                                                          
                                                                          
*note c_int: 2ea6.         int                                            int
                                                                          
                                                                          
*note c_uint: 2eb6.        unsigned int                                   int
                                                                          
                                                                          
*note c_long: 2ea7.        long                                           int
                                                                          
                                                                          
*note c_ulong: 2eb7.       unsigned long                                  int
                                                                          
                                                                          
*note c_longlong: 2eb8.    __int64 或 long long                           int
                                                                          
                                                                          
*note c_ulonglong: 2eb9.   unsigned __int64 或 unsigned long long         int
                                                                          
                                                                          
*note c_size_t: 2eba.      ‘size_t’                                       int
                                                                          
                                                                          
*note c_ssize_t: 11d4.     ‘ssize_t’ 或 *note Py_ssize_t: a03.            int
                                                                          
                                                                          
*note c_time_t: 16de.      ‘time_t’                                       int
                                                                          
                                                                          
*note c_float: 2ebb.       float                                          float
                                                                          
                                                                          
*note c_double: 17fd.      double                                         float
                                                                          
                                                                          
*note c_longdouble: 17fe.  long double                                    float
                                                                          
                                                                          
*note c_char_p: 15e1.      char* (NUL terminated)                         bytes object or ‘None’
                                                                          
                                                                          
*note c_wchar_p: 15e2.     wchar_t* (NUL terminated)                      字串或 ‘None’
                                                                          
                                                                          
*note c_void_p: 15e3.      void*                                          int or ‘None’
                                                                          

  1. The constructor accepts any object with a truth value.

All these types can be created by calling them with an optional
initializer of the correct type and value:

     >>> c_int()
     c_long(0)
     >>> c_wchar_p("Hello, World")
     c_wchar_p(140018365411392)
     >>> c_ushort(-3)
     c_ushort(65533)
     >>>

Since these types are mutable, their value can also be changed
afterwards:

     >>> i = c_int(42)
     >>> print(i)
     c_long(42)
     >>> print(i.value)
     42
     >>> i.value = -99
     >>> print(i.value)
     -99
     >>>

Assigning a new value to instances of the pointer types *note c_char_p:
15e1, *note c_wchar_p: 15e2, and *note c_void_p: 15e3. changes the
'memory location' they point to, 'not the contents' of the memory block
(of course not, because Python bytes objects are immutable):

     >>> s = "Hello, World"
     >>> c_s = c_wchar_p(s)
     >>> print(c_s)
     c_wchar_p(139966785747344)
     >>> print(c_s.value)
     Hello World
     >>> c_s.value = "Hi, there"
     >>> print(c_s)              # the memory location has changed
     c_wchar_p(139966783348904)
     >>> print(c_s.value)
     Hi, there
     >>> print(s)                # first object is unchanged
     Hello, World
     >>>

You should be careful, however, not to pass them to functions expecting
pointers to mutable memory.  If you need mutable memory blocks, ctypes
has a *note create_string_buffer(): 2ebc. function which creates these
in various ways.  The current memory block contents can be accessed (or
changed) with the ‘raw’ property; if you want to access it as NUL
terminated string, use the ‘value’ property:

     >>> from ctypes import *
     >>> p = create_string_buffer(3)            # create a 3 byte buffer, initialized to NUL bytes
     >>> print(sizeof(p), repr(p.raw))
     3 b'\x00\x00\x00'
     >>> p = create_string_buffer(b"Hello")     # create a buffer containing a NUL terminated string
     >>> print(sizeof(p), repr(p.raw))
     6 b'Hello\x00'
     >>> print(repr(p.value))
     b'Hello'
     >>> p = create_string_buffer(b"Hello", 10) # create a 10 byte buffer
     >>> print(sizeof(p), repr(p.raw))
     10 b'Hello\x00\x00\x00\x00\x00'
     >>> p.value = b"Hi"
     >>> print(sizeof(p), repr(p.raw))
     10 b'Hi\x00lo\x00\x00\x00\x00\x00'
     >>>

The *note create_string_buffer(): 2ebc. function replaces the old
‘c_buffer()’ function (which is still available as an alias).  To create
a mutable memory block containing unicode characters of the C type
‘wchar_t’, use the *note create_unicode_buffer(): 18d4. function.


File: python.info,  Node: Calling functions continued,  Next: Calling variadic functions,  Prev: Fundamental data types,  Up: ctypes 教學

5.16.15.6 Calling functions, continued
......................................

Note that printf prints to the real standard output channel, 'not' to
*note sys.stdout: a79, so these examples will only work at the console
prompt, not from within 'IDLE' or 'PythonWin':

     >>> printf = libc.printf
     >>> printf(b"Hello, %s\n", b"World!")
     Hello, World!
     14
     >>> printf(b"Hello, %S\n", "World!")
     Hello, World!
     14
     >>> printf(b"%d bottles of beer\n", 42)
     42 bottles of beer
     19
     >>> printf(b"%f bottles of beer\n", 42.5)
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     ctypes.ArgumentError: argument 2: TypeError: Don't know how to convert parameter 2
     >>>

As has been mentioned before, all Python types except integers, strings,
and bytes objects have to be wrapped in their corresponding *note
ctypes: 22. type, so that they can be converted to the required C data
type:

     >>> printf(b"An int %d, a double %f\n", 1234, c_double(3.14))
     An int 1234, a double 3.140000
     31
     >>>


File: python.info,  Node: Calling variadic functions,  Next: Calling functions with your own custom data types,  Prev: Calling functions continued,  Up: ctypes 教學

5.16.15.7 Calling variadic functions
....................................

On a lot of platforms calling variadic functions through ctypes is
exactly the same as calling functions with a fixed number of parameters.
On some platforms, and in particular ARM64 for Apple Platforms, the
calling convention for variadic functions is different than that for
regular functions.

On those platforms it is required to specify the *note argtypes: 2ec1.
attribute for the regular, non-variadic, function arguments:

     libc.printf.argtypes = [ctypes.c_char_p]

Because specifying the attribute does not inhibit portability it is
advised to always specify *note argtypes: 2ec1. for all variadic
functions.


File: python.info,  Node: Calling functions with your own custom data types,  Next: Specifying the required argument types function prototypes,  Prev: Calling variadic functions,  Up: ctypes 教學

5.16.15.8 Calling functions with your own custom data types
...........................................................

You can also customize *note ctypes: 22. argument conversion to allow
instances of your own classes be used as function arguments.  *note
ctypes: 22. looks for an ‘_as_parameter_’ attribute and uses this as the
function argument.  The attribute must be an integer, string, bytes, a
*note ctypes: 22. instance, or an object with an ‘_as_parameter_’
attribute:

     >>> class Bottles:
     ...     def __init__(self, number):
     ...         self._as_parameter_ = number
     ...
     >>> bottles = Bottles(42)
     >>> printf(b"%d bottles of beer\n", bottles)
     42 bottles of beer
     19
     >>>

If you don't want to store the instance's data in the ‘_as_parameter_’
instance variable, you could define a *note property: 180. which makes
the attribute available on request.


File: python.info,  Node: Specifying the required argument types function prototypes,  Next: Return types,  Prev: Calling functions with your own custom data types,  Up: ctypes 教學

5.16.15.9 Specifying the required argument types (function prototypes)
......................................................................

It is possible to specify the required argument types of functions
exported from DLLs by setting the *note argtypes: 2ec1. attribute.

*note argtypes: 2ec1. must be a sequence of C data types (the ‘printf()’
function is probably not a good example here, because it takes a
variable number and different types of parameters depending on the
format string, on the other hand this is quite handy to experiment with
this feature):

     >>> printf.argtypes = [c_char_p, c_char_p, c_int, c_double]
     >>> printf(b"String '%s', Int %d, Double %f\n", b"Hi", 10, 2.2)
     String 'Hi', Int 10, Double 2.200000
     37
     >>>

Specifying a format protects against incompatible argument types (just
as a prototype for a C function), and tries to convert the arguments to
valid types:

     >>> printf(b"%d %d %d", 1, 2, 3)
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     ctypes.ArgumentError: argument 2: TypeError: 'int' object cannot be interpreted as ctypes.c_char_p
     >>> printf(b"%s %d %f\n", b"X", 2, 3)
     X 2 3.000000
     13
     >>>

If you have defined your own classes which you pass to function calls,
you have to implement a *note from_param(): 2ec6. class method for them
to be able to use them in the *note argtypes: 2ec1. sequence.  The *note
from_param(): 2ec6. class method receives the Python object passed to
the function call, it should do a typecheck or whatever is needed to
make sure this object is acceptable, and then return the object itself,
its ‘_as_parameter_’ attribute, or whatever you want to pass as the C
function argument in this case.  Again, the result should be an integer,
string, bytes, a *note ctypes: 22. instance, or an object with an
‘_as_parameter_’ attribute.


File: python.info,  Node: Return types,  Next: Passing pointers or passing parameters by reference,  Prev: Specifying the required argument types function prototypes,  Up: ctypes 教學

5.16.15.10 Return types
.......................

By default functions are assumed to return the C int type.  Other return
types can be specified by setting the *note restype: 2ec9. attribute of
the function object.

The C prototype of ‘time()’ is ‘time_t time(time_t *)’.  Because
‘time_t’ might be of a different type than the default return type int,
you should specify the ‘restype’ attribute:

     >>> libc.time.restype = c_time_t

The argument types can be specified using *note argtypes: 2ec1.:

     >>> libc.time.argtypes = (POINTER(c_time_t),)

To call the function with a ‘NULL’ pointer as first argument, use
‘None’:

     >>> print(libc.time(None))
     1150640792

Here is a more advanced example, it uses the ‘strchr()’ function, which
expects a string pointer and a char, and returns a pointer to a string:

     >>> strchr = libc.strchr
     >>> strchr(b"abcdef", ord("d"))
     8059983
     >>> strchr.restype = c_char_p    # c_char_p is a pointer to a string
     >>> strchr(b"abcdef", ord("d"))
     b'def'
     >>> print(strchr(b"abcdef", ord("x")))
     None
     >>>

If you want to avoid the *note ord("x"): 1de1. calls above, you can set
the *note argtypes: 2ec1. attribute, and the second argument will be
converted from a single character Python bytes object into a C char:

     >>> strchr.restype = c_char_p
     >>> strchr.argtypes = [c_char_p, c_char]
     >>> strchr(b"abcdef", b"d")
     b'def'
     >>> strchr(b"abcdef", b"def")
     Traceback (most recent call last):
     ctypes.ArgumentError: argument 2: TypeError: one character bytes, bytearray or integer expected
     >>> print(strchr(b"abcdef", b"x"))
     None
     >>> strchr(b"abcdef", b"d")
     b'def'
     >>>

You can also use a callable Python object (a function or a class for
example) as the *note restype: 2ec9. attribute, if the foreign function
returns an integer.  The callable will be called with the 'integer' the
C function returns, and the result of this call will be used as the
result of your function call.  This is useful to check for error return
values and automatically raise an exception:

     >>> GetModuleHandle = windll.kernel32.GetModuleHandleA
     >>> def ValidHandle(value):
     ...     if value == 0:
     ...         raise WinError()
     ...     return value
     ...
     >>>
     >>> GetModuleHandle.restype = ValidHandle
     >>> GetModuleHandle(None)
     486539264
     >>> GetModuleHandle("something silly")
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
       File "<stdin>", line 3, in ValidHandle
     OSError: [Errno 126] The specified module could not be found.
     >>>

‘WinError’ is a function which will call Windows ‘FormatMessage()’ api
to get the string representation of an error code, and 'returns' an
exception.  ‘WinError’ takes an optional error code parameter, if no one
is used, it calls *note GetLastError(): 2eca. to retrieve it.

Please note that a much more powerful error checking mechanism is
available through the *note errcheck: 2ecb. attribute; see the reference
manual for details.


File: python.info,  Node: Passing pointers or passing parameters by reference,  Next: Structures and unions,  Prev: Return types,  Up: ctypes 教學

5.16.15.11 Passing pointers (or: passing parameters by reference)
.................................................................

Sometimes a C api function expects a 'pointer' to a data type as
parameter, probably to write into the corresponding location, or if the
data is too large to be passed by value.  This is also known as 'passing
parameters by reference'.

*note ctypes: 22. exports the *note byref(): 2ece. function which is
used to pass parameters by reference.  The same effect can be achieved
with the *note pointer(): 15df. function, although *note pointer():
15df. does a lot more work since it constructs a real pointer object, so
it is faster to use *note byref(): 2ece. if you don't need the pointer
object in Python itself:

     >>> i = c_int()
     >>> f = c_float()
     >>> s = create_string_buffer(b'\000' * 32)
     >>> print(i.value, f.value, repr(s.value))
     0 0.0 b''
     >>> libc.sscanf(b"1 3.14 Hello", b"%d %f %s",
     ...             byref(i), byref(f), s)
     3
     >>> print(i.value, f.value, repr(s.value))
     1 3.1400001049 b'Hello'
     >>>


File: python.info,  Node: Structures and unions,  Next: Structure/union alignment and byte order,  Prev: Passing pointers or passing parameters by reference,  Up: ctypes 教學

5.16.15.12 Structures and unions
................................

Structures and unions must derive from the *note Structure: 154d. and
*note Union: 1577. base classes which are defined in the *note ctypes:
22. module.  Each subclass must define a *note _fields_: 2ed1.
attribute.  ‘_fields_’ must be a list of '2-tuples', containing a 'field
name' and a 'field type'.

The field type must be a *note ctypes: 22. type like *note c_int: 2ea6,
or any other derived *note ctypes: 22. type: structure, union, array,
pointer.

Here is a simple example of a POINT structure, which contains two
integers named 'x' and 'y', and also shows how to initialize a structure
in the constructor:

     >>> from ctypes import *
     >>> class POINT(Structure):
     ...     _fields_ = [("x", c_int),
     ...                 ("y", c_int)]
     ...
     >>> point = POINT(10, 20)
     >>> print(point.x, point.y)
     10 20
     >>> point = POINT(y=5)
     >>> print(point.x, point.y)
     0 5
     >>> POINT(1, 2, 3)
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: too many initializers
     >>>

You can, however, build much more complicated structures.  A structure
can itself contain other structures by using a structure as a field
type.

Here is a RECT structure which contains two POINTs named 'upperleft' and
'lowerright':

     >>> class RECT(Structure):
     ...     _fields_ = [("upperleft", POINT),
     ...                 ("lowerright", POINT)]
     ...
     >>> rc = RECT(point)
     >>> print(rc.upperleft.x, rc.upperleft.y)
     0 5
     >>> print(rc.lowerright.x, rc.lowerright.y)
     0 0
     >>>

Nested structures can also be initialized in the constructor in several
ways:

     >>> r = RECT(POINT(1, 2), POINT(3, 4))
     >>> r = RECT((1, 2), (3, 4))

Field *note descriptor: 1e47.s can be retrieved from the 'class', they
are useful for debugging because they can provide useful information:

     >>> print(POINT.x)
     <Field type=c_long, ofs=0, size=4>
     >>> print(POINT.y)
     <Field type=c_long, ofs=4, size=4>
     >>>
     警告: *note ctypes: 22. does not support passing unions or
     structures with bit-fields to functions by value.  While this may
     work on 32-bit x86, it's not guaranteed by the library to work in
     the general case.  Unions and structures with bit-fields should
     always be passed to functions by pointer.


File: python.info,  Node: Structure/union alignment and byte order,  Next: Bit fields in structures and unions,  Prev: Structures and unions,  Up: ctypes 教學

5.16.15.13 Structure/union alignment and byte order
...................................................

By default, Structure and Union fields are aligned in the same way the C
compiler does it.  It is possible to override this behavior by
specifying a *note _pack_: 2ed4. class attribute in the subclass
definition.  This must be set to a positive integer and specifies the
maximum alignment for the fields.  This is what ‘#pragma pack(n)’ also
does in MSVC. It is also possible to set a minimum alignment for how the
subclass itself is packed in the same way ‘#pragma align(n)’ works in
MSVC. This can be achieved by specifying a :*note _align_: 2ed5. class
attribute in the subclass definition.

*note ctypes: 22. uses the native byte order for Structures and Unions.
To build structures with non-native byte order, you can use one of the
*note BigEndianStructure: 2ed6, *note LittleEndianStructure: 2ed7, *note
BigEndianUnion: 172b, and *note LittleEndianUnion: 172c. base classes.
These classes cannot contain pointer fields.


File: python.info,  Node: Bit fields in structures and unions,  Next: Arrays,  Prev: Structure/union alignment and byte order,  Up: ctypes 教學

5.16.15.14 Bit fields in structures and unions
..............................................

It is possible to create structures and unions containing bit fields.
Bit fields are only possible for integer fields, the bit width is
specified as the third item in the *note _fields_: 2ed1. tuples:

     >>> class Int(Structure):
     ...     _fields_ = [("first_16", c_int, 16),
     ...                 ("second_16", c_int, 16)]
     ...
     >>> print(Int.first_16)
     <Field type=c_long, ofs=0:0, bits=16>
     >>> print(Int.second_16)
     <Field type=c_long, ofs=0:16, bits=16>
     >>>


File: python.info,  Node: Arrays,  Next: Pointers,  Prev: Bit fields in structures and unions,  Up: ctypes 教學

5.16.15.15 Arrays
.................

Arrays are sequences, containing a fixed number of instances of the same
type.

The recommended way to create array types is by multiplying a data type
with a positive integer:

     TenPointsArrayType = POINT * 10

Here is an example of a somewhat artificial data type, a structure
containing 4 POINTs among other stuff:

     >>> from ctypes import *
     >>> class POINT(Structure):
     ...     _fields_ = ("x", c_int), ("y", c_int)
     ...
     >>> class MyStruct(Structure):
     ...     _fields_ = [("a", c_int),
     ...                 ("b", c_float),
     ...                 ("point_array", POINT * 4)]
     >>>
     >>> print(len(MyStruct().point_array))
     4
     >>>

Instances are created in the usual way, by calling the class:

     arr = TenPointsArrayType()
     for pt in arr:
         print(pt.x, pt.y)

The above code print a series of ‘0 0’ lines, because the array contents
is initialized to zeros.

Initializers of the correct type can also be specified:

     >>> from ctypes import *
     >>> TenIntegers = c_int * 10
     >>> ii = TenIntegers(1, 2, 3, 4, 5, 6, 7, 8, 9, 10)
     >>> print(ii)
     <c_long_Array_10 object at 0x...>
     >>> for i in ii: print(i, end=" ")
     ...
     1 2 3 4 5 6 7 8 9 10
     >>>


File: python.info,  Node: Pointers,  Next: Type conversions,  Prev: Arrays,  Up: ctypes 教學

5.16.15.16 Pointers
...................

Pointer instances are created by calling the *note pointer(): 15df.
function on a *note ctypes: 22. type:

     >>> from ctypes import *
     >>> i = c_int(42)
     >>> pi = pointer(i)
     >>>

Pointer instances have a *note contents: 2ede. attribute which returns
the object to which the pointer points, the ‘i’ object above:

     >>> pi.contents
     c_long(42)
     >>>

Note that *note ctypes: 22. does not have OOR (original object return),
it constructs a new, equivalent object each time you retrieve an
attribute:

     >>> pi.contents is i
     False
     >>> pi.contents is pi.contents
     False
     >>>

Assigning another *note c_int: 2ea6. instance to the pointer's contents
attribute would cause the pointer to point to the memory location where
this is stored:

     >>> i = c_int(99)
     >>> pi.contents = i
     >>> pi.contents
     c_long(99)
     >>>

Pointer instances can also be indexed with integers:

     >>> pi[0]
     99
     >>>

Assigning to an integer index changes the pointed to value:

     >>> print(i)
     c_long(99)
     >>> pi[0] = 22
     >>> print(i)
     c_long(22)
     >>>

It is also possible to use indexes different from 0, but you must know
what you're doing, just as in C: You can access or change arbitrary
memory locations.  Generally you only use this feature if you receive a
pointer from a C function, and you 'know' that the pointer actually
points to an array instead of a single item.

Behind the scenes, the *note pointer(): 15df. function does more than
simply create pointer instances, it has to create pointer 'types' first.
This is done with the *note POINTER(): 15e0. function, which accepts any
*note ctypes: 22. type, and returns a new type:

     >>> PI = POINTER(c_int)
     >>> PI
     <class 'ctypes.LP_c_long'>
     >>> PI(42)
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: expected c_long instead of int
     >>> PI(c_int(42))
     <ctypes.LP_c_long object at 0x...>
     >>>

Calling the pointer type without an argument creates a ‘NULL’ pointer.
‘NULL’ pointers have a ‘False’ boolean value:

     >>> null_ptr = POINTER(c_int)()
     >>> print(bool(null_ptr))
     False
     >>>

*note ctypes: 22. checks for ‘NULL’ when dereferencing pointers (but
dereferencing invalid non-‘NULL’ pointers would crash Python):

     >>> null_ptr[0]
     Traceback (most recent call last):
         ....
     ValueError: NULL pointer access
     >>>

     >>> null_ptr[0] = 1234
     Traceback (most recent call last):
         ....
     ValueError: NULL pointer access
     >>>


File: python.info,  Node: Type conversions,  Next: Incomplete Types,  Prev: Pointers,  Up: ctypes 教學

5.16.15.17 Type conversions
...........................

Usually, ctypes does strict type checking.  This means, if you have
‘POINTER(c_int)’ in the *note argtypes: 2ec1. list of a function or as
the type of a member field in a structure definition, only instances of
exactly the same type are accepted.  There are some exceptions to this
rule, where ctypes accepts other objects.  For example, you can pass
compatible array instances instead of pointer types.  So, for
‘POINTER(c_int)’, ctypes accepts an array of c_int:

     >>> class Bar(Structure):
     ...     _fields_ = [("count", c_int), ("values", POINTER(c_int))]
     ...
     >>> bar = Bar()
     >>> bar.values = (c_int * 3)(1, 2, 3)
     >>> bar.count = 3
     >>> for i in range(bar.count):
     ...     print(bar.values[i])
     ...
     1
     2
     3
     >>>

In addition, if a function argument is explicitly declared to be a
pointer type (such as ‘POINTER(c_int)’) in *note argtypes: 2ec1, an
object of the pointed type (‘c_int’ in this case) can be passed to the
function.  ctypes will apply the required *note byref(): 2ece.
conversion in this case automatically.

To set a POINTER type field to ‘NULL’, you can assign ‘None’:

     >>> bar.values = None
     >>>

Sometimes you have instances of incompatible types.  In C, you can cast
one type into another type.  *note ctypes: 22. provides a *note cast():
2ee1. function which can be used in the same way.  The ‘Bar’ structure
defined above accepts ‘POINTER(c_int)’ pointers or *note c_int: 2ea6.
arrays for its ‘values’ field, but not instances of other types:

     >>> bar.values = (c_byte * 4)()
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: incompatible types, c_byte_Array_4 instance instead of LP_c_long instance
     >>>

For these cases, the *note cast(): 2ee1. function is handy.

The *note cast(): 2ee1. function can be used to cast a ctypes instance
into a pointer to a different ctypes data type.  *note cast(): 2ee1.
takes two parameters, a ctypes object that is or can be converted to a
pointer of some kind, and a ctypes pointer type.  It returns an instance
of the second argument, which references the same memory block as the
first argument:

     >>> a = (c_byte * 4)()
     >>> cast(a, POINTER(c_int))
     <ctypes.LP_c_long object at ...>
     >>>

So, *note cast(): 2ee1. can be used to assign to the ‘values’ field of
‘Bar’ the structure:

     >>> bar = Bar()
     >>> bar.values = cast((c_byte * 4)(), POINTER(c_int))
     >>> print(bar.values[0])
     0
     >>>


File: python.info,  Node: Incomplete Types,  Next: 回呼函式,  Prev: Type conversions,  Up: ctypes 教學

5.16.15.18 Incomplete Types
...........................

'Incomplete Types' are structures, unions or arrays whose members are
not yet specified.  In C, they are specified by forward declarations,
which are defined later:

     struct cell; /* forward declaration */

     struct cell {
         char *name;
         struct cell *next;
     };

The straightforward translation into ctypes code would be this, but it
does not work:

     >>> class cell(Structure):
     ...     _fields_ = [("name", c_char_p),
     ...                 ("next", POINTER(cell))]
     ...
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
       File "<stdin>", line 2, in cell
     NameError: name 'cell' is not defined
     >>>

because the new ‘class cell’ is not available in the class statement
itself.  In *note ctypes: 22, we can define the ‘cell’ class and set the
*note _fields_: 2ed1. attribute later, after the class statement:

     >>> from ctypes import *
     >>> class cell(Structure):
     ...     pass
     ...
     >>> cell._fields_ = [("name", c_char_p),
     ...                  ("next", POINTER(cell))]
     >>>

Let's try it.  We create two instances of ‘cell’, and let them point to
each other, and finally follow the pointer chain a few times:

     >>> c1 = cell()
     >>> c1.name = b"foo"
     >>> c2 = cell()
     >>> c2.name = b"bar"
     >>> c1.next = pointer(c2)
     >>> c2.next = pointer(c1)
     >>> p = c1
     >>> for i in range(8):
     ...     print(p.name, end=" ")
     ...     p = p.next[0]
     ...
     foo bar foo bar foo bar foo bar
     >>>


File: python.info,  Node: 回呼函式,  Next: Accessing values exported from dlls,  Prev: Incomplete Types,  Up: ctypes 教學

5.16.15.19 回呼函式
...................

*note ctypes: 22. allows creating C callable function pointers from
Python callables.  These are sometimes called 'callback functions'.

First, you must create a class for the callback function.  The class
knows the calling convention, the return type, and the number and types
of arguments this function will receive.

The *note CFUNCTYPE(): 2ee6. factory function creates types for callback
functions using the ‘cdecl’ calling convention.  On Windows, the *note
WINFUNCTYPE(): 2ee7. factory function creates types for callback
functions using the ‘stdcall’ calling convention.

Both of these factory functions are called with the result type as first
argument, and the callback functions expected argument types as the
remaining arguments.

I will present an example here which uses the standard C library's
‘qsort()’ function, that is used to sort items with the help of a
callback function.  ‘qsort()’ will be used to sort an array of integers:

     >>> IntArray5 = c_int * 5
     >>> ia = IntArray5(5, 1, 7, 33, 99)
     >>> qsort = libc.qsort
     >>> qsort.restype = None
     >>>

‘qsort()’ must be called with a pointer to the data to sort, the number
of items in the data array, the size of one item, and a pointer to the
comparison function, the callback.  The callback will then be called
with two pointers to items, and it must return a negative integer if the
first item is smaller than the second, a zero if they are equal, and a
positive integer otherwise.

So our callback function receives pointers to integers, and must return
an integer.  First we create the ‘type’ for the callback function:

     >>> CMPFUNC = CFUNCTYPE(c_int, POINTER(c_int), POINTER(c_int))
     >>>

To get started, here is a simple callback that shows the values it gets
passed:

     >>> def py_cmp_func(a, b):
     ...     print("py_cmp_func", a[0], b[0])
     ...     return 0
     ...
     >>> cmp_func = CMPFUNC(py_cmp_func)
     >>>

結果為：

     >>> qsort(ia, len(ia), sizeof(c_int), cmp_func)
     py_cmp_func 5 1
     py_cmp_func 33 99
     py_cmp_func 7 33
     py_cmp_func 5 7
     py_cmp_func 1 7
     >>>

Now we can actually compare the two items and return a useful result:

     >>> def py_cmp_func(a, b):
     ...     print("py_cmp_func", a[0], b[0])
     ...     return a[0] - b[0]
     ...
     >>>
     >>> qsort(ia, len(ia), sizeof(c_int), CMPFUNC(py_cmp_func))
     py_cmp_func 5 1
     py_cmp_func 33 99
     py_cmp_func 7 33
     py_cmp_func 1 7
     py_cmp_func 5 7
     >>>

As we can easily check, our array is sorted now:

     >>> for i in ia: print(i, end=" ")
     ...
     1 5 7 33 99
     >>>

The function factories can be used as decorator factories, so we may as
well write:

     >>> @CFUNCTYPE(c_int, POINTER(c_int), POINTER(c_int))
     ... def py_cmp_func(a, b):
     ...     print("py_cmp_func", a[0], b[0])
     ...     return a[0] - b[0]
     ...
     >>> qsort(ia, len(ia), sizeof(c_int), py_cmp_func)
     py_cmp_func 5 1
     py_cmp_func 33 99
     py_cmp_func 7 33
     py_cmp_func 1 7
     py_cmp_func 5 7
     >>>

     備註: Make sure you keep references to *note CFUNCTYPE(): 2ee6.
     objects as long as they are used from C code.  *note ctypes: 22.
     doesn't, and if you don't, they may be garbage collected, crashing
     your program when a callback is made.

     Also, note that if the callback function is called in a thread
     created outside of Python's control (e.g.  by the foreign code that
     calls the callback), ctypes creates a new dummy Python thread on
     every invocation.  This behavior is correct for most purposes, but
     it means that values stored with *note threading.local: 166d. will
     'not' survive across different callbacks, even when those calls are
     made from the same C thread.


File: python.info,  Node: Accessing values exported from dlls,  Next: Surprises,  Prev: 回呼函式,  Up: ctypes 教學

5.16.15.20 Accessing values exported from dlls
..............................................

Some shared libraries not only export functions, they also export
variables.  An example in the Python library itself is the *note
Py_Version: 6fa, Python runtime version number encoded in a single
constant integer.

*note ctypes: 22. can access values like this with the *note in_dll():
2eea. class methods of the type.  'pythonapi' is a predefined symbol
giving access to the Python C api:

     >>> version = ctypes.c_int.in_dll(ctypes.pythonapi, "Py_Version")
     >>> print(hex(version.value))
     0x30c00a0

An extended example which also demonstrates the use of pointers accesses
the *note PyImport_FrozenModules: 2eeb. pointer exported by Python.

Quoting the docs for that value:

     This pointer is initialized to point to an array of *note _frozen:
     719. records, terminated by one whose members are all ‘NULL’ or
     zero.  When a frozen module is imported, it is searched in this
     table.  Third-party code could play tricks with this to provide a
     dynamically created collection of frozen modules.

So manipulating this pointer could even prove useful.  To restrict the
example size, we show only how this table can be read with *note ctypes:
22.:

     >>> from ctypes import *
     >>>
     >>> class struct_frozen(Structure):
     ...     _fields_ = [("name", c_char_p),
     ...                 ("code", POINTER(c_ubyte)),
     ...                 ("size", c_int),
     ...                 ("get_code", POINTER(c_ubyte)),  # 函式指標
     ...                ]
     ...
     >>>

We have defined the *note _frozen: 719. data type, so we can get the
pointer to the table:

     >>> FrozenTable = POINTER(struct_frozen)
     >>> table = FrozenTable.in_dll(pythonapi, "_PyImport_FrozenBootstrap")
     >>>

Since ‘table’ is a ‘pointer’ to the array of ‘struct_frozen’ records, we
can iterate over it, but we just have to make sure that our loop
terminates, because pointers have no size.  Sooner or later it would
probably crash with an access violation or whatever, so it's better to
break out of the loop when we hit the ‘NULL’ entry:

     >>> for item in table:
     ...     if item.name is None:
     ...         break
     ...     print(item.name.decode("ascii"), item.size)
     ...
     _frozen_importlib 31764
     _frozen_importlib_external 41499
     zipimport 12345
     >>>

The fact that standard Python has a frozen module and a frozen package
(indicated by the negative ‘size’ member) is not well known, it is only
used for testing.  Try it out with ‘import __hello__’ for example.


File: python.info,  Node: Surprises,  Next: Variable-sized data types,  Prev: Accessing values exported from dlls,  Up: ctypes 教學

5.16.15.21 Surprises
....................

There are some edges in *note ctypes: 22. where you might expect
something other than what actually happens.

Consider the following example:

     >>> from ctypes import *
     >>> class POINT(Structure):
     ...     _fields_ = ("x", c_int), ("y", c_int)
     ...
     >>> class RECT(Structure):
     ...     _fields_ = ("a", POINT), ("b", POINT)
     ...
     >>> p1 = POINT(1, 2)
     >>> p2 = POINT(3, 4)
     >>> rc = RECT(p1, p2)
     >>> print(rc.a.x, rc.a.y, rc.b.x, rc.b.y)
     1 2 3 4
     >>> # now swap the two points
     >>> rc.a, rc.b = rc.b, rc.a
     >>> print(rc.a.x, rc.a.y, rc.b.x, rc.b.y)
     3 4 3 4
     >>>

Hm.  We certainly expected the last statement to print ‘3 4 1 2’.  What
happened?  Here are the steps of the ‘rc.a, rc.b = rc.b, rc.a’ line
above:

     >>> temp0, temp1 = rc.b, rc.a
     >>> rc.a = temp0
     >>> rc.b = temp1
     >>>

Note that ‘temp0’ and ‘temp1’ are objects still using the internal
buffer of the ‘rc’ object above.  So executing ‘rc.a = temp0’ copies the
buffer contents of ‘temp0’ into ‘rc’ 's buffer.  This, in turn, changes
the contents of ‘temp1’.  So, the last assignment ‘rc.b = temp1’,
doesn't have the expected effect.

Keep in mind that retrieving sub-objects from Structure, Unions, and
Arrays doesn't 'copy' the sub-object, instead it retrieves a wrapper
object accessing the root-object's underlying buffer.

Another example that may behave differently from what one would expect
is this:

     >>> s = c_char_p()
     >>> s.value = b"abc def ghi"
     >>> s.value
     b'abc def ghi'
     >>> s.value is s.value
     False
     >>>

     備註: Objects instantiated from *note c_char_p: 15e1. can only have
     their value set to bytes or integers.

Why is it printing ‘False’?  ctypes instances are objects containing a
memory block plus some *note descriptor: 1e47.s accessing the contents
of the memory.  Storing a Python object in the memory block does not
store the object itself, instead the ‘contents’ of the object is stored.
Accessing the contents again constructs a new Python object each time!


File: python.info,  Node: Variable-sized data types,  Prev: Surprises,  Up: ctypes 教學

5.16.15.22 Variable-sized data types
....................................

*note ctypes: 22. provides some support for variable-sized arrays and
structures.

The *note resize(): 2ef0. function can be used to resize the memory
buffer of an existing ctypes object.  The function takes the object as
first argument, and the requested size in bytes as the second argument.
The memory block cannot be made smaller than the natural memory block
specified by the objects type, a *note ValueError: 1e7. is raised if
this is tried:

     >>> short_array = (c_short * 4)()
     >>> print(sizeof(short_array))
     8
     >>> resize(short_array, 4)
     Traceback (most recent call last):
         ...
     ValueError: minimum size is 8
     >>> resize(short_array, 32)
     >>> sizeof(short_array)
     32
     >>> sizeof(type(short_array))
     8
     >>>

This is nice and fine, but how would one access the additional elements
contained in this array?  Since the type still only knows about 4
elements, we get errors accessing other elements:

     >>> short_array[:]
     [0, 0, 0, 0]
     >>> short_array[7]
     Traceback (most recent call last):
         ...
     IndexError: invalid index
     >>>

Another way to use variable-sized data types with *note ctypes: 22. is
to use the dynamic nature of Python, and (re-)define the data type after
the required size is already known, on a case by case basis.


File: python.info,  Node: ctypes reference,  Prev: ctypes 教學,  Up: ctypes --- 用於 Python 的外部函式庫

5.16.15.23 ctypes reference
...........................

* Menu:

* Finding shared libraries::
* Loading shared libraries::
* Foreign functions::
* Function prototypes::
* Utility functions::
* Data types::
* Fundamental data types: Fundamental data types<2>.
* Structured data types::
* Arrays and pointers::


File: python.info,  Node: Finding shared libraries,  Next: Loading shared libraries,  Up: ctypes reference

5.16.15.24 Finding shared libraries
...................................

When programming in a compiled language, shared libraries are accessed
when compiling/linking a program, and when the program is run.

The purpose of the *note find_library(): cf0. function is to locate a
library in a way similar to what the compiler or runtime loader does (on
platforms with several versions of a shared library the most recent
should be loaded), while the ctypes library loaders act like when a
program is run, and call the runtime loader directly.

The ‘ctypes.util’ module provides a function which can help to determine
the library to load.

 -- 資料: ctypes.util.find_library (name)

     Try to find a library and return a pathname.  'name' is the library
     name without any prefix like 'lib', suffix like ‘.so’, ‘.dylib’ or
     version number (this is the form used for the posix linker option
     ‘-l’).  If no library can be found, returns ‘None’.

The exact functionality is system dependent.

On Linux, *note find_library(): cf0. tries to run external programs
(‘/sbin/ldconfig’, ‘gcc’, ‘objdump’ and ‘ld’) to find the library file.
It returns the filename of the library file.

在 3.6 版的變更: On Linux, the value of the environment variable
‘LD_LIBRARY_PATH’ is used when searching for libraries, if a library
cannot be found by any other means.

以下是一些範例：

     >>> from ctypes.util import find_library
     >>> find_library("m")
     'libm.so.6'
     >>> find_library("c")
     'libc.so.6'
     >>> find_library("bz2")
     'libbz2.so.1.0'
     >>>

On macOS and Android, *note find_library(): cf0. uses the system's
standard naming schemes and paths to locate the library, and returns a
full pathname if successful:

     >>> from ctypes.util import find_library
     >>> find_library("c")
     '/usr/lib/libc.dylib'
     >>> find_library("m")
     '/usr/lib/libm.dylib'
     >>> find_library("bz2")
     '/usr/lib/libbz2.dylib'
     >>> find_library("AGL")
     '/System/Library/Frameworks/AGL.framework/AGL'
     >>>

On Windows, *note find_library(): cf0. searches along the system search
path, and returns the full pathname, but since there is no predefined
naming scheme a call like ‘find_library("c")’ will fail and return
‘None’.

If wrapping a shared library with *note ctypes: 22, it 'may' be better
to determine the shared library name at development time, and hardcode
that into the wrapper module instead of using *note find_library(): cf0.
to locate the library at runtime.


File: python.info,  Node: Loading shared libraries,  Next: Foreign functions,  Prev: Finding shared libraries,  Up: ctypes reference

5.16.15.25 Loading shared libraries
...................................

There are several ways to load shared libraries into the Python process.
One way is to instantiate one of the following classes:

 -- 類別: ctypes.CDLL (name, mode=DEFAULT_MODE, handle=None,
          use_errno=False, use_last_error=False, winmode=None)

     Instances of this class represent loaded shared libraries.
     Functions in these libraries use the standard C calling convention,
     and are assumed to return int.

     On Windows creating a *note CDLL: 98d. instance may fail even if
     the DLL name exists.  When a dependent DLL of the loaded DLL is not
     found, a *note OSError: 350. error is raised with the message
     '"[WinError 126] The specified module could not be found".'  This
     error message does not contain the name of the missing DLL because
     the Windows API does not return this information making this error
     hard to diagnose.  To resolve this error and determine which DLL is
     not found, you need to find the list of dependent DLLs and
     determine which one is not found using Windows debugging and
     tracing tools.

     在 3.12 版的變更: The 'name' parameter can now be a *note path-like
     object: ac2.

也參考
......

Microsoft DUMPBIN tool(1) - A tool to find DLL dependents.

 -- 類別: ctypes.OleDLL (name, mode=DEFAULT_MODE, handle=None,
          use_errno=False, use_last_error=False, winmode=None)

     Windows only: Instances of this class represent loaded shared
     libraries, functions in these libraries use the ‘stdcall’ calling
     convention, and are assumed to return the windows specific *note
     HRESULT: 2ef7. code.  *note HRESULT: 2ef7. values contain
     information specifying whether the function call failed or
     succeeded, together with additional error code.  If the return
     value signals a failure, an *note OSError: 350. is automatically
     raised.

     在 3.3 版的變更: *note WindowsError: ff7. used to be raised, which
     is now an alias of *note OSError: 350.

     在 3.12 版的變更: The 'name' parameter can now be a *note path-like
     object: ac2.

 -- 類別: ctypes.WinDLL (name, mode=DEFAULT_MODE, handle=None,
          use_errno=False, use_last_error=False, winmode=None)

     Windows only: Instances of this class represent loaded shared
     libraries, functions in these libraries use the ‘stdcall’ calling
     convention, and are assumed to return int by default.

     在 3.12 版的變更: The 'name' parameter can now be a *note path-like
     object: ac2.

The Python *note global interpreter lock: 12e. is released before
calling any function exported by these libraries, and reacquired
afterwards.

 -- 類別: ctypes.PyDLL (name, mode=DEFAULT_MODE, handle=None)

     Instances of this class behave like *note CDLL: 98d. instances,
     except that the Python GIL is 'not' released during the function
     call, and after the function execution the Python error flag is
     checked.  If the error flag is set, a Python exception is raised.

     Thus, this is only useful to call Python C api functions directly.

     在 3.12 版的變更: The 'name' parameter can now be a *note path-like
     object: ac2.

All these classes can be instantiated by calling them with at least one
argument, the pathname of the shared library.  If you have an existing
handle to an already loaded shared library, it can be passed as the
‘handle’ named parameter, otherwise the underlying platform's ‘dlopen()’
or ‘LoadLibrary()’ function is used to load the library into the
process, and to get a handle to it.

The 'mode' parameter can be used to specify how the library is loaded.
For details, consult the ‘dlopen(3)(2)’ manpage.  On Windows, 'mode' is
ignored.  On posix systems, RTLD_NOW is always added, and is not
configurable.

The 'use_errno' parameter, when set to true, enables a ctypes mechanism
that allows accessing the system *note errno: 4d. error number in a safe
way.  *note ctypes: 22. maintains a thread-local copy of the system's
*note errno: 4d. variable; if you call foreign functions created with
‘use_errno=True’ then the *note errno: 4d. value before the function
call is swapped with the ctypes private copy, the same happens
immediately after the function call.

The function *note ctypes.get_errno(): 2ef8. returns the value of the
ctypes private copy, and the function *note ctypes.set_errno(): 2ef9.
changes the ctypes private copy to a new value and returns the former
value.

The 'use_last_error' parameter, when set to true, enables the same
mechanism for the Windows error code which is managed by the *note
GetLastError(): 2eca. and ‘SetLastError()’ Windows API functions; *note
ctypes.get_last_error(): 2efa. and *note ctypes.set_last_error(): 2efb.
are used to request and change the ctypes private copy of the windows
error code.

The 'winmode' parameter is used on Windows to specify how the library is
loaded (since 'mode' is ignored).  It takes any value that is valid for
the Win32 API ‘LoadLibraryEx’ flags parameter.  When omitted, the
default is to use the flags that result in the most secure DLL load,
which avoids issues such as DLL hijacking.  Passing the full path to the
DLL is the safest way to ensure the correct library and dependencies are
loaded.

在 3.8 版的變更: 新增 'winmode' 參數。

 -- 資料: ctypes.RTLD_GLOBAL

     Flag to use as 'mode' parameter.  On platforms where this flag is
     not available, it is defined as the integer zero.

 -- 資料: ctypes.RTLD_LOCAL

     Flag to use as 'mode' parameter.  On platforms where this is not
     available, it is the same as 'RTLD_GLOBAL'.

 -- 資料: ctypes.DEFAULT_MODE

     The default mode which is used to load shared libraries.  On OSX
     10.3, this is 'RTLD_GLOBAL', otherwise it is the same as
     'RTLD_LOCAL'.

Instances of these classes have no public methods.  Functions exported
by the shared library can be accessed as attributes or by index.  Please
note that accessing the function through an attribute caches the result
and therefore accessing it repeatedly returns the same object each time.
On the other hand, accessing it through an index returns a new object
each time:

     >>> from ctypes import CDLL
     >>> libc = CDLL("libc.so.6")  # 於 Linux
     >>> libc.time == libc.time
     True
     >>> libc['time'] == libc['time']
     False

The following public attributes are available, their name starts with an
underscore to not clash with exported function names:

 -- 屬性: PyDLL._handle

     The system handle used to access the library.

 -- 屬性: PyDLL._name

     The name of the library passed in the constructor.

Shared libraries can also be loaded by using one of the prefabricated
objects, which are instances of the *note LibraryLoader: 2efe. class,
either by calling the *note LoadLibrary(): 2eaa. method, or by
retrieving the library as attribute of the loader instance.

 -- 類別: ctypes.LibraryLoader (dlltype)

     Class which loads shared libraries.  'dlltype' should be one of the
     *note CDLL: 98d, *note PyDLL: 1677, *note WinDLL: 1676, or *note
     OleDLL: 1675. types.

     ‘__getattr__()’ has special behavior: It allows loading a shared
     library by accessing it as attribute of a library loader instance.
     The result is cached, so repeated attribute accesses return the
     same library each time.

      -- 方法: LoadLibrary (name)

          Load a shared library into the process and return it.  This
          method always returns a new instance of the library.

These prefabricated library loaders are available:

 -- 資料: ctypes.cdll

     Creates *note CDLL: 98d. instances.

 -- 資料: ctypes.windll

     Windows only: Creates *note WinDLL: 1676. instances.

 -- 資料: ctypes.oledll

     Windows only: Creates *note OleDLL: 1675. instances.

 -- 資料: ctypes.pydll

     Creates *note PyDLL: 1677. instances.

For accessing the C Python api directly, a ready-to-use Python shared
library object is available:

 -- 資料: ctypes.pythonapi

     An instance of *note PyDLL: 1677. that exposes Python C API
     functions as attributes.  Note that all these functions are assumed
     to return C int, which is of course not always the truth, so you
     have to assign the correct ‘restype’ attribute to use these
     functions.

Loading a library through any of these objects raises an *note auditing
event: 17bd. ‘ctypes.dlopen’ with string argument ‘name’, the name used
to load the library.

Accessing a function on a loaded library raises an auditing event
‘ctypes.dlsym’ with arguments ‘library’ (the library object) and ‘name’
(the symbol's name as a string or integer).

In cases when only the library handle is available rather than the
object, accessing a function raises an auditing event
‘ctypes.dlsym/handle’ with arguments ‘handle’ (the raw library handle)
and ‘name’.

   ---------- Footnotes ----------

   (1) https://docs.microsoft.com/cpp/build/reference/dependents

   (2) https://manpages.debian.org/dlopen(3)


File: python.info,  Node: Foreign functions,  Next: Function prototypes,  Prev: Loading shared libraries,  Up: ctypes reference

5.16.15.26 Foreign functions
............................

As explained in the previous section, foreign functions can be accessed
as attributes of loaded shared libraries.  The function objects created
in this way by default accept any number of arguments, accept any ctypes
data instances as arguments, and return the default result type
specified by the library loader.  They are instances of a private class:

 -- 類別: ctypes._FuncPtr

     Base class for C callable foreign functions.

     Instances of foreign functions are also C compatible data types;
     they represent C function pointers.

     This behavior can be customized by assigning to special attributes
     of the foreign function object.

      -- 屬性: restype

          Assign a ctypes type to specify the result type of the foreign
          function.  Use ‘None’ for void, a function not returning
          anything.

          It is possible to assign a callable Python object that is not
          a ctypes type, in this case the function is assumed to return
          a C int, and the callable will be called with this integer,
          allowing further processing or error checking.  Using this is
          deprecated, for more flexible post processing or error
          checking use a ctypes data type as ‘restype’ and assign a
          callable to the *note errcheck: 2ecb. attribute.

      -- 屬性: argtypes

          Assign a tuple of ctypes types to specify the argument types
          that the function accepts.  Functions using the ‘stdcall’
          calling convention can only be called with the same number of
          arguments as the length of this tuple; functions using the C
          calling convention accept additional, unspecified arguments as
          well.

          When a foreign function is called, each actual argument is
          passed to the *note from_param(): 2ec6. class method of the
          items in the *note argtypes: 2ec1. tuple, this method allows
          adapting the actual argument to an object that the foreign
          function accepts.  For example, a *note c_char_p: 15e1. item
          in the *note argtypes: 2ec1. tuple will convert a string
          passed as argument into a bytes object using ctypes conversion
          rules.

          New: It is now possible to put items in argtypes which are not
          ctypes types, but each item must have a *note from_param():
          2ec6. method which returns a value usable as argument
          (integer, string, ctypes instance).  This allows defining
          adapters that can adapt custom objects as function parameters.

      -- 屬性: errcheck

          Assign a Python function or another callable to this
          attribute.  The callable will be called with three or more
          arguments:

           -- 函式: callable (result, func, arguments)

               'result' is what the foreign function returns, as
               specified by the ‘restype’ attribute.

               'func' is the foreign function object itself, this allows
               reusing the same callable object to check or post process
               the results of several functions.

               'arguments' is a tuple containing the parameters
               originally passed to the function call, this allows
               specializing the behavior on the arguments used.

          The object that this function returns will be returned from
          the foreign function call, but it can also check the result
          value and raise an exception if the foreign function call
          failed.

 -- 例外: ctypes.ArgumentError

     This exception is raised when a foreign function call cannot
     convert one of the passed arguments.

On Windows, when a foreign function call raises a system exception (for
example, due to an access violation), it will be captured and replaced
with a suitable Python exception.  Further, an auditing event
‘ctypes.set_exception’ with argument ‘code’ will be raised, allowing an
audit hook to replace the exception with its own.

Some ways to invoke foreign function calls may raise an auditing event
‘ctypes.call_function’ with arguments ‘function pointer’ and
‘arguments’.


File: python.info,  Node: Function prototypes,  Next: Utility functions,  Prev: Foreign functions,  Up: ctypes reference

5.16.15.27 Function prototypes
..............................

Foreign functions can also be created by instantiating function
prototypes.  Function prototypes are similar to function prototypes in
C; they describe a function (return type, argument types, calling
convention) without defining an implementation.  The factory functions
must be called with the desired result type and the argument types of
the function, and can be used as decorator factories, and as such, be
applied to functions through the ‘@wrapper’ syntax.  See *note 回呼函式:
2ee5. for examples.

 -- 函式: ctypes.CFUNCTYPE (restype, *argtypes, use_errno=False,
          use_last_error=False)

     The returned function prototype creates functions that use the
     standard C calling convention.  The function will release the GIL
     during the call.  If 'use_errno' is set to true, the ctypes private
     copy of the system *note errno: 4d. variable is exchanged with the
     real *note errno: 4d. value before and after the call;
     'use_last_error' does the same for the Windows error code.

 -- 函式: ctypes.WINFUNCTYPE (restype, *argtypes, use_errno=False,
          use_last_error=False)

     Windows only: The returned function prototype creates functions
     that use the ‘stdcall’ calling convention.  The function will
     release the GIL during the call.  'use_errno' and 'use_last_error'
     have the same meaning as above.

 -- 函式: ctypes.PYFUNCTYPE (restype, *argtypes)

     The returned function prototype creates functions that use the
     Python calling convention.  The function will 'not' release the GIL
     during the call.

Function prototypes created by these factory functions can be
instantiated in different ways, depending on the type and number of the
parameters in the call:

 -- 函式: prototype (address)

     Returns a foreign function at the specified address which must be
     an integer.

 -- 函式: prototype (callable)

     Create a C callable function (a callback function) from a Python
     'callable'.

 -- 函式: prototype (func_spec[, paramflags])

     Returns a foreign function exported by a shared library.
     'func_spec' must be a 2-tuple ‘(name_or_ordinal, library)’.  The
     first item is the name of the exported function as string, or the
     ordinal of the exported function as small integer.  The second item
     is the shared library instance.

 -- 函式: prototype (vtbl_index, name[, paramflags[, iid]])

     Returns a foreign function that will call a COM method.
     'vtbl_index' is the index into the virtual function table, a small
     non-negative integer.  'name' is name of the COM method.  'iid' is
     an optional pointer to the interface identifier which is used in
     extended error reporting.

     COM methods use a special calling convention: They require a
     pointer to the COM interface as first argument, in addition to
     those parameters that are specified in the ‘argtypes’ tuple.

The optional 'paramflags' parameter creates foreign function wrappers
with much more functionality than the features described above.

'paramflags' must be a tuple of the same length as *note argtypes: 2ec1.

Each item in this tuple contains further information about a parameter,
it must be a tuple containing one, two, or three items.

The first item is an integer containing a combination of direction flags
for the parameter:

     1

          Specifies an input parameter to the function.

     2

          Output parameter.  The foreign function fills in a value.

     4

          Input parameter which defaults to the integer zero.

The optional second item is the parameter name as string.  If this is
specified, the foreign function can be called with named parameters.

The optional third item is the default value for this parameter.

The following example demonstrates how to wrap the Windows ‘MessageBoxW’
function so that it supports default parameters and named arguments.
The C declaration from the windows header file is this:

     WINUSERAPI int WINAPI
     MessageBoxW(
         HWND hWnd,
         LPCWSTR lpText,
         LPCWSTR lpCaption,
         UINT uType);

Here is the wrapping with *note ctypes: 22.:

     >>> from ctypes import c_int, WINFUNCTYPE, windll
     >>> from ctypes.wintypes import HWND, LPCWSTR, UINT
     >>> prototype = WINFUNCTYPE(c_int, HWND, LPCWSTR, LPCWSTR, UINT)
     >>> paramflags = (1, "hwnd", 0), (1, "text", "Hi"), (1, "caption", "Hello from ctypes"), (1, "flags", 0)
     >>> MessageBox = prototype(("MessageBoxW", windll.user32), paramflags)

The ‘MessageBox’ foreign function can now be called in these ways:

     >>> MessageBox()
     >>> MessageBox(text="Spam, spam, spam")
     >>> MessageBox(flags=2, text="foo bar")

A second example demonstrates output parameters.  The win32
‘GetWindowRect’ function retrieves the dimensions of a specified window
by copying them into ‘RECT’ structure that the caller has to supply.
Here is the C declaration:

     WINUSERAPI BOOL WINAPI
     GetWindowRect(
          HWND hWnd,
          LPRECT lpRect);

Here is the wrapping with *note ctypes: 22.:

     >>> from ctypes import POINTER, WINFUNCTYPE, windll, WinError
     >>> from ctypes.wintypes import BOOL, HWND, RECT
     >>> prototype = WINFUNCTYPE(BOOL, HWND, POINTER(RECT))
     >>> paramflags = (1, "hwnd"), (2, "lprect")
     >>> GetWindowRect = prototype(("GetWindowRect", windll.user32), paramflags)
     >>>

Functions with output parameters will automatically return the output
parameter value if there is a single one, or a tuple containing the
output parameter values when there are more than one, so the
GetWindowRect function now returns a RECT instance, when called.

Output parameters can be combined with the *note errcheck: 2ecb.
protocol to do further output processing and error checking.  The win32
‘GetWindowRect’ api function returns a ‘BOOL’ to signal success or
failure, so this function could do the error checking, and raises an
exception when the api call failed:

     >>> def errcheck(result, func, args):
     ...     if not result:
     ...         raise WinError()
     ...     return args
     ...
     >>> GetWindowRect.errcheck = errcheck
     >>>

If the *note errcheck: 2ecb. function returns the argument tuple it
receives unchanged, *note ctypes: 22. continues the normal processing it
does on the output parameters.  If you want to return a tuple of window
coordinates instead of a ‘RECT’ instance, you can retrieve the fields in
the function and return them instead, the normal processing will no
longer take place:

     >>> def errcheck(result, func, args):
     ...     if not result:
     ...         raise WinError()
     ...     rc = args[1]
     ...     return rc.left, rc.top, rc.bottom, rc.right
     ...
     >>> GetWindowRect.errcheck = errcheck
     >>>


File: python.info,  Node: Utility functions,  Next: Data types,  Prev: Function prototypes,  Up: ctypes reference

5.16.15.28 Utility functions
............................

 -- 函式: ctypes.addressof (obj)

     Returns the address of the memory buffer as integer.  'obj' must be
     an instance of a ctypes type.

     引發一個附帶引數 ‘obj’ 的*note 稽核事件: 17bd. ‘ctypes.addressof’。

 -- 函式: ctypes.alignment (obj_or_type)

     Returns the alignment requirements of a ctypes type.  'obj_or_type'
     must be a ctypes type or instance.

 -- 函式: ctypes.byref (obj[, offset])

     Returns a light-weight pointer to 'obj', which must be an instance
     of a ctypes type.  'offset' defaults to zero, and must be an
     integer that will be added to the internal pointer value.

     ‘byref(obj, offset)’ corresponds to this C code:

          (((char *)&obj) + offset)

     The returned object can only be used as a foreign function call
     parameter.  It behaves similar to ‘pointer(obj)’, but the
     construction is a lot faster.

 -- 函式: ctypes.cast (obj, type)

     This function is similar to the cast operator in C. It returns a
     new instance of 'type' which points to the same memory block as
     'obj'.  'type' must be a pointer type, and 'obj' must be an object
     that can be interpreted as a pointer.

 -- 函式: ctypes.create_string_buffer (init_or_size, size=None)

     This function creates a mutable character buffer.  The returned
     object is a ctypes array of *note c_char: 2eb2.

     'init_or_size' must be an integer which specifies the size of the
     array, or a bytes object which will be used to initialize the array
     items.

     If a bytes object is specified as first argument, the buffer is
     made one item larger than its length so that the last element in
     the array is a NUL termination character.  An integer can be passed
     as second argument which allows specifying the size of the array if
     the length of the bytes should not be used.

     引發一個附帶引數 ‘init’ 與 ‘size’ 的*note 稽核事件: 17bd.
     ‘ctypes.create_string_buffer’。

 -- 函式: ctypes.create_unicode_buffer (init_or_size, size=None)

     This function creates a mutable unicode character buffer.  The
     returned object is a ctypes array of *note c_wchar: 2eb3.

     'init_or_size' must be an integer which specifies the size of the
     array, or a string which will be used to initialize the array
     items.

     If a string is specified as first argument, the buffer is made one
     item larger than the length of the string so that the last element
     in the array is a NUL termination character.  An integer can be
     passed as second argument which allows specifying the size of the
     array if the length of the string should not be used.

     引發一個附帶引數 ‘init’ 與 ‘size’ 的*note 稽核事件: 17bd.
     ‘ctypes.create_unicode_buffer’。

 -- 函式: ctypes.DllCanUnloadNow ()

     Windows only: This function is a hook which allows implementing
     in-process COM servers with ctypes.  It is called from the
     DllCanUnloadNow function that the _ctypes extension dll exports.

 -- 函式: ctypes.DllGetClassObject ()

     Windows only: This function is a hook which allows implementing
     in-process COM servers with ctypes.  It is called from the
     DllGetClassObject function that the ‘_ctypes’ extension dll
     exports.

 -- 函式: ctypes.util.find_library (name)

     Try to find a library and return a pathname.  'name' is the library
     name without any prefix like ‘lib’, suffix like ‘.so’, ‘.dylib’ or
     version number (this is the form used for the posix linker option
     ‘-l’).  If no library can be found, returns ‘None’.

     The exact functionality is system dependent.

 -- 函式: ctypes.util.find_msvcrt ()

     Windows only: return the filename of the VC runtime library used by
     Python, and by the extension modules.  If the name of the library
     cannot be determined, ‘None’ is returned.

     If you need to free memory, for example, allocated by an extension
     module with a call to the ‘free(void *)’, it is important that you
     use the function in the same library that allocated the memory.

 -- 函式: ctypes.FormatError ([code])

     Windows only: Returns a textual description of the error code
     'code'.  If no error code is specified, the last error code is used
     by calling the Windows api function GetLastError.

 -- 函式: ctypes.GetLastError ()

     Windows only: Returns the last error code set by Windows in the
     calling thread.  This function calls the Windows ‘GetLastError()’
     function directly, it does not return the ctypes-private copy of
     the error code.

 -- 函式: ctypes.get_errno ()

     Returns the current value of the ctypes-private copy of the system
     *note errno: 4d. variable in the calling thread.

     引發一個不附帶引數的*note 稽核事件: 17bd. ‘ctypes.get_errno’。

 -- 函式: ctypes.get_last_error ()

     Windows only: returns the current value of the ctypes-private copy
     of the system ‘LastError’ variable in the calling thread.

     引發一個不附帶引數的*note 稽核事件: 17bd. ‘ctypes.get_last_error’。

 -- 函式: ctypes.memmove (dst, src, count)

     Same as the standard C memmove library function: copies 'count'
     bytes from 'src' to 'dst'.  'dst' and 'src' must be integers or
     ctypes instances that can be converted to pointers.

 -- 函式: ctypes.memset (dst, c, count)

     Same as the standard C memset library function: fills the memory
     block at address 'dst' with 'count' bytes of value 'c'.  'dst' must
     be an integer specifying an address, or a ctypes instance.

 -- 函式: ctypes.POINTER (type, /)

     Create and return a new ctypes pointer type.  Pointer types are
     cached and reused internally, so calling this function repeatedly
     is cheap.  'type' must be a ctypes type.

 -- 函式: ctypes.pointer (obj, /)

     Create a new pointer instance, pointing to 'obj'.  The returned
     object is of the type ‘POINTER(type(obj))’.

     Note: If you just want to pass a pointer to an object to a foreign
     function call, you should use ‘byref(obj)’ which is much faster.

 -- 函式: ctypes.resize (obj, size)

     This function resizes the internal memory buffer of 'obj', which
     must be an instance of a ctypes type.  It is not possible to make
     the buffer smaller than the native size of the objects type, as
     given by ‘sizeof(type(obj))’, but it is possible to enlarge the
     buffer.

 -- 函式: ctypes.set_errno (value)

     Set the current value of the ctypes-private copy of the system
     *note errno: 4d. variable in the calling thread to 'value' and
     return the previous value.

     引發一個附帶引數 ‘errno’ 的*note 稽核事件: 17bd.
     ‘ctypes.set_errno’。

 -- 函式: ctypes.set_last_error (value)

     Windows only: set the current value of the ctypes-private copy of
     the system ‘LastError’ variable in the calling thread to 'value'
     and return the previous value.

     引發一個附帶引數 ‘error’ 的*note 稽核事件: 17bd.
     ‘ctypes.set_last_error’。

 -- 函式: ctypes.sizeof (obj_or_type)

     Returns the size in bytes of a ctypes type or instance memory
     buffer.  Does the same as the C ‘sizeof’ operator.

 -- 函式: ctypes.string_at (ptr, size=-1)

     Return the byte string at 'void *ptr'.  If 'size' is specified, it
     is used as size, otherwise the string is assumed to be
     zero-terminated.

     引發一個附帶引數 ‘ptr’、‘size’ 的*note 稽核事件: 17bd.
     ‘ctypes.string_at’。

 -- 函式: ctypes.WinError (code=None, descr=None)

     Windows only: this function is probably the worst-named thing in
     ctypes.  It creates an instance of *note OSError: 350.  If 'code'
     is not specified, ‘GetLastError’ is called to determine the error
     code.  If 'descr' is not specified, *note FormatError(): 2f0d. is
     called to get a textual description of the error.

     在 3.3 版的變更: An instance of *note WindowsError: ff7. used to be
     created, which is now an alias of *note OSError: 350.

 -- 函式: ctypes.wstring_at (ptr, size=-1)

     Return the wide-character string at 'void *ptr'.  If 'size' is
     specified, it is used as the number of characters of the string,
     otherwise the string is assumed to be zero-terminated.

     引發一個附帶引數 ‘ptr’、‘size’ 的*note 稽核事件: 17bd.
     ‘ctypes.wstring_at’。


File: python.info,  Node: Data types,  Next: Fundamental data types<2>,  Prev: Utility functions,  Up: ctypes reference

5.16.15.29 Data types
.....................

 -- 類別: ctypes._CData

     This non-public class is the common base class of all ctypes data
     types.  Among other things, all ctypes type instances contain a
     memory block that hold C compatible data; the address of the memory
     block is returned by the *note addressof(): 2f08. helper function.
     Another instance variable is exposed as *note _objects: 2f17.; this
     contains other Python objects that need to be kept alive in case
     the memory block contains pointers.

     Common methods of ctypes data types, these are all class methods
     (to be exact, they are methods of the *note metaclass: 1e5d.):

      -- 方法: from_buffer (source[, offset])

          This method returns a ctypes instance that shares the buffer
          of the 'source' object.  The 'source' object must support the
          writeable buffer interface.  The optional 'offset' parameter
          specifies an offset into the source buffer in bytes; the
          default is zero.  If the source buffer is not large enough a
          *note ValueError: 1e7. is raised.

          引發一個附帶引數 ‘pointer’、‘size’、‘offset’ 的*note 稽核事件:
          17bd. ‘ctypes.cdata/buffer’。

      -- 方法: from_buffer_copy (source[, offset])

          This method creates a ctypes instance, copying the buffer from
          the 'source' object buffer which must be readable.  The
          optional 'offset' parameter specifies an offset into the
          source buffer in bytes; the default is zero.  If the source
          buffer is not large enough a *note ValueError: 1e7. is raised.

          引發一個附帶引數 ‘pointer’、‘size’、‘offset’ 的*note 稽核事件:
          17bd. ‘ctypes.cdata/buffer’。

      -- 方法: from_address (address)

          This method returns a ctypes type instance using the memory
          specified by 'address' which must be an integer.

          This method, and others that indirectly call this method,
          raises an *note auditing event: 17bd. ‘ctypes.cdata’ with
          argument ‘address’.

      -- 方法: from_param (obj)

          This method adapts 'obj' to a ctypes type.  It is called with
          the actual object used in a foreign function call when the
          type is present in the foreign function's *note argtypes:
          2ec1. tuple; it must return an object that can be used as a
          function call parameter.

          All ctypes data types have a default implementation of this
          classmethod that normally returns 'obj' if that is an instance
          of the type.  Some types accept other objects as well.

      -- 方法: in_dll (library, name)

          This method returns a ctypes type instance exported by a
          shared library.  'name' is the name of the symbol that exports
          the data, 'library' is the loaded shared library.

     Common instance variables of ctypes data types:

      -- 屬性: _b_base_

          Sometimes ctypes data instances do not own the memory block
          they contain, instead they share part of the memory block of a
          base object.  The *note _b_base_: 2f1b. read-only member is
          the root ctypes object that owns the memory block.

      -- 屬性: _b_needsfree_

          This read-only variable is true when the ctypes data instance
          has allocated the memory block itself, false otherwise.

      -- 屬性: _objects

          This member is either ‘None’ or a dictionary containing Python
          objects that need to be kept alive so that the memory block
          contents is kept valid.  This object is only exposed for
          debugging; never modify the contents of this dictionary.


File: python.info,  Node: Fundamental data types<2>,  Next: Structured data types,  Prev: Data types,  Up: ctypes reference

5.16.15.30 Fundamental data types
.................................

 -- 類別: ctypes._SimpleCData

     This non-public class is the base class of all fundamental ctypes
     data types.  It is mentioned here because it contains the common
     attributes of the fundamental ctypes data types.  *note
     _SimpleCData: 2f1f. is a subclass of *note _CData: 2f16, so it
     inherits their methods and attributes.  ctypes data types that are
     not and do not contain pointers can now be pickled.

     Instances have a single attribute:

      -- 屬性: value

          This attribute contains the actual value of the instance.  For
          integer and pointer types, it is an integer, for character
          types, it is a single character bytes object or string, for
          character pointer types it is a Python bytes object or string.

          When the ‘value’ attribute is retrieved from a ctypes
          instance, usually a new object is returned each time.  *note
          ctypes: 22. does 'not' implement original object return,
          always a new object is constructed.  The same is true for all
          other ctypes object instances.

Fundamental data types, when returned as foreign function call results,
or, for example, by retrieving structure field members or array items,
are transparently converted to native Python types.  In other words, if
a foreign function has a *note restype: 2ec9. of *note c_char_p: 15e1,
you will always receive a Python bytes object, 'not' a *note c_char_p:
15e1. instance.

Subclasses of fundamental data types do 'not' inherit this behavior.
So, if a foreign functions ‘restype’ is a subclass of *note c_void_p:
15e3, you will receive an instance of this subclass from the function
call.  Of course, you can get the value of the pointer by accessing the
‘value’ attribute.

These are the fundamental ctypes data types:

 -- 類別: ctypes.c_byte

     Represents the C signed char datatype, and interprets the value as
     small integer.  The constructor accepts an optional integer
     initializer; no overflow checking is done.

 -- 類別: ctypes.c_char

     Represents the C char datatype, and interprets the value as a
     single character.  The constructor accepts an optional string
     initializer, the length of the string must be exactly one
     character.

 -- 類別: ctypes.c_char_p

     Represents the C char* datatype when it points to a zero-terminated
     string.  For a general character pointer that may also point to
     binary data, ‘POINTER(c_char)’ must be used.  The constructor
     accepts an integer address, or a bytes object.

 -- 類別: ctypes.c_double

     Represents the C double datatype.  The constructor accepts an
     optional float initializer.

 -- 類別: ctypes.c_longdouble

     Represents the C long double datatype.  The constructor accepts an
     optional float initializer.  On platforms where ‘sizeof(long
     double) == sizeof(double)’ it is an alias to *note c_double: 17fd.

 -- 類別: ctypes.c_float

     Represents the C float datatype.  The constructor accepts an
     optional float initializer.

 -- 類別: ctypes.c_int

     Represents the C signed int datatype.  The constructor accepts an
     optional integer initializer; no overflow checking is done.  On
     platforms where ‘sizeof(int) == sizeof(long)’ it is an alias to
     *note c_long: 2ea7.

 -- 類別: ctypes.c_int8

     Represents the C 8-bit signed int datatype.  Usually an alias for
     *note c_byte: 1673.

 -- 類別: ctypes.c_int16

     Represents the C 16-bit signed int datatype.  Usually an alias for
     *note c_short: 2eb4.

 -- 類別: ctypes.c_int32

     Represents the C 32-bit signed int datatype.  Usually an alias for
     *note c_int: 2ea6.

 -- 類別: ctypes.c_int64

     Represents the C 64-bit signed int datatype.  Usually an alias for
     *note c_longlong: 2eb8.

 -- 類別: ctypes.c_long

     Represents the C signed long datatype.  The constructor accepts an
     optional integer initializer; no overflow checking is done.

 -- 類別: ctypes.c_longlong

     Represents the C signed long long datatype.  The constructor
     accepts an optional integer initializer; no overflow checking is
     done.

 -- 類別: ctypes.c_short

     Represents the C signed short datatype.  The constructor accepts an
     optional integer initializer; no overflow checking is done.

 -- 類別: ctypes.c_size_t

     Represents the C ‘size_t’ datatype.

 -- 類別: ctypes.c_ssize_t

     Represents the C ‘ssize_t’ datatype.

     在 3.2 版被加入.

 -- 類別: ctypes.c_time_t

     Represents the C ‘time_t’ datatype.

     在 3.12 版被加入.

 -- 類別: ctypes.c_ubyte

     Represents the C unsigned char datatype, it interprets the value as
     small integer.  The constructor accepts an optional integer
     initializer; no overflow checking is done.

 -- 類別: ctypes.c_uint

     Represents the C unsigned int datatype.  The constructor accepts an
     optional integer initializer; no overflow checking is done.  On
     platforms where ‘sizeof(int) == sizeof(long)’ it is an alias for
     *note c_ulong: 2eb7.

 -- 類別: ctypes.c_uint8

     Represents the C 8-bit unsigned int datatype.  Usually an alias for
     *note c_ubyte: 1674.

 -- 類別: ctypes.c_uint16

     Represents the C 16-bit unsigned int datatype.  Usually an alias
     for *note c_ushort: 2eb5.

 -- 類別: ctypes.c_uint32

     Represents the C 32-bit unsigned int datatype.  Usually an alias
     for *note c_uint: 2eb6.

 -- 類別: ctypes.c_uint64

     Represents the C 64-bit unsigned int datatype.  Usually an alias
     for *note c_ulonglong: 2eb9.

 -- 類別: ctypes.c_ulong

     Represents the C unsigned long datatype.  The constructor accepts
     an optional integer initializer; no overflow checking is done.

 -- 類別: ctypes.c_ulonglong

     Represents the C unsigned long long datatype.  The constructor
     accepts an optional integer initializer; no overflow checking is
     done.

 -- 類別: ctypes.c_ushort

     Represents the C unsigned short datatype.  The constructor accepts
     an optional integer initializer; no overflow checking is done.

 -- 類別: ctypes.c_void_p

     Represents the C void* type.  The value is represented as integer.
     The constructor accepts an optional integer initializer.

 -- 類別: ctypes.c_wchar

     Represents the C ‘wchar_t’ datatype, and interprets the value as a
     single character unicode string.  The constructor accepts an
     optional string initializer, the length of the string must be
     exactly one character.

 -- 類別: ctypes.c_wchar_p

     Represents the C wchar_t* datatype, which must be a pointer to a
     zero-terminated wide character string.  The constructor accepts an
     integer address, or a string.

 -- 類別: ctypes.c_bool

     Represent the C bool datatype (more accurately, _Bool from C99).
     Its value can be ‘True’ or ‘False’, and the constructor accepts any
     object that has a truth value.

 -- 類別: ctypes.HRESULT

     Windows only: Represents a ‘HRESULT’ value, which contains success
     or error information for a function or method call.

 -- 類別: ctypes.py_object

     Represents the C *note PyObject: 311.* datatype.  Calling this
     without an argument creates a ‘NULL’ *note PyObject: 311.* pointer.

The ‘ctypes.wintypes’ module provides quite some other Windows specific
data types, for example ‘HWND’, ‘WPARAM’, or ‘DWORD’.  Some useful
structures like ‘MSG’ or ‘RECT’ are also defined.


File: python.info,  Node: Structured data types,  Next: Arrays and pointers,  Prev: Fundamental data types<2>,  Up: ctypes reference

5.16.15.31 Structured data types
................................

 -- 類別: ctypes.Union (*args, **kw)

     Abstract base class for unions in native byte order.

 -- 類別: ctypes.BigEndianUnion (*args, **kw)

     Abstract base class for unions in 'big endian' byte order.

     在 3.11 版被加入.

 -- 類別: ctypes.LittleEndianUnion (*args, **kw)

     Abstract base class for unions in 'little endian' byte order.

     在 3.11 版被加入.

 -- 類別: ctypes.BigEndianStructure (*args, **kw)

     Abstract base class for structures in 'big endian' byte order.

 -- 類別: ctypes.LittleEndianStructure (*args, **kw)

     Abstract base class for structures in 'little endian' byte order.

Structures and unions with non-native byte order cannot contain pointer
type fields, or any other data types containing pointer type fields.

 -- 類別: ctypes.Structure (*args, **kw)

     Abstract base class for structures in 'native' byte order.

     Concrete structure and union types must be created by subclassing
     one of these types, and at least define a *note _fields_: 2ed1.
     class variable.  *note ctypes: 22. will create *note descriptor:
     1e47.s which allow reading and writing the fields by direct
     attribute accesses.  These are the

      -- 屬性: _fields_

          A sequence defining the structure fields.  The items must be
          2-tuples or 3-tuples.  The first item is the name of the
          field, the second item specifies the type of the field; it can
          be any ctypes data type.

          For integer type fields like *note c_int: 2ea6, a third
          optional item can be given.  It must be a small positive
          integer defining the bit width of the field.

          Field names must be unique within one structure or union.
          This is not checked, only one field can be accessed when names
          are repeated.

          It is possible to define the *note _fields_: 2ed1. class
          variable 'after' the class statement that defines the
          Structure subclass, this allows creating data types that
          directly or indirectly reference themselves:

               class List(Structure):
                   pass
               List._fields_ = [("pnext", POINTER(List)),
                                ...
                               ]

          The *note _fields_: 2ed1. class variable must, however, be
          defined before the type is first used (an instance is created,
          *note sizeof(): 2f10. is called on it, and so on).  Later
          assignments to the *note _fields_: 2ed1. class variable will
          raise an AttributeError.

          It is possible to define sub-subclasses of structure types,
          they inherit the fields of the base class plus the *note
          _fields_: 2ed1. defined in the sub-subclass, if any.

      -- 屬性: _pack_

          An optional small integer that allows overriding the alignment
          of structure fields in the instance.  *note _pack_: 2ed4. must
          already be defined when *note _fields_: 2ed1. is assigned,
          otherwise it will have no effect.  Setting this attribute to 0
          is the same as not setting it at all.

      -- 屬性: _align_

          An optional small integer that allows overriding the alignment
          of the structure when being packed or unpacked to/from memory.
          Setting this attribute to 0 is the same as not setting it at
          all.

      -- 屬性: _anonymous_

          An optional sequence that lists the names of unnamed
          (anonymous) fields.  *note _anonymous_: 2f2b. must be already
          defined when *note _fields_: 2ed1. is assigned, otherwise it
          will have no effect.

          The fields listed in this variable must be structure or union
          type fields.  *note ctypes: 22. will create descriptors in the
          structure type that allows accessing the nested fields
          directly, without the need to create the structure or union
          field.

          Here is an example type (Windows):

               class _U(Union):
                   _fields_ = [("lptdesc", POINTER(TYPEDESC)),
                               ("lpadesc", POINTER(ARRAYDESC)),
                               ("hreftype", HREFTYPE)]

               class TYPEDESC(Structure):
                   _anonymous_ = ("u",)
                   _fields_ = [("u", _U),
                               ("vt", VARTYPE)]

          The ‘TYPEDESC’ structure describes a COM data type, the ‘vt’
          field specifies which one of the union fields is valid.  Since
          the ‘u’ field is defined as anonymous field, it is now
          possible to access the members directly off the TYPEDESC
          instance.  ‘td.lptdesc’ and ‘td.u.lptdesc’ are equivalent, but
          the former is faster since it does not need to create a
          temporary union instance:

               td = TYPEDESC()
               td.vt = VT_PTR
               td.lptdesc = POINTER(some_type)
               td.u.lptdesc = POINTER(some_type)

     It is possible to define sub-subclasses of structures, they inherit
     the fields of the base class.  If the subclass definition has a
     separate *note _fields_: 2ed1. variable, the fields specified in
     this are appended to the fields of the base class.

     Structure and union constructors accept both positional and keyword
     arguments.  Positional arguments are used to initialize member
     fields in the same order as they are appear in *note _fields_:
     2ed1.  Keyword arguments in the constructor are interpreted as
     attribute assignments, so they will initialize *note _fields_:
     2ed1. with the same name, or create new attributes for names not
     present in *note _fields_: 2ed1.


File: python.info,  Node: Arrays and pointers,  Prev: Structured data types,  Up: ctypes reference

5.16.15.32 Arrays and pointers
..............................

 -- 類別: ctypes.Array (*args)

     Abstract base class for arrays.

     The recommended way to create concrete array types is by
     multiplying any *note ctypes: 22. data type with a non-negative
     integer.  Alternatively, you can subclass this type and define
     *note _length_: 2f2e. and *note _type_: 2f2f. class variables.
     Array elements can be read and written using standard subscript and
     slice accesses; for slice reads, the resulting object is 'not'
     itself an *note Array: 1930.

      -- 屬性: _length_

          A positive integer specifying the number of elements in the
          array.  Out-of-range subscripts result in an *note IndexError:
          14a3.  Will be returned by *note len(): 5d4.

      -- 屬性: _type_

          Specifies the type of each element in the array.

     Array subclass constructors accept positional arguments, used to
     initialize the elements in order.

 -- 函式: ctypes.ARRAY (type, length)

     Create an array.  Equivalent to ‘type * length’, where 'type' is a
     *note ctypes: 22. data type and 'length' an integer.

     This function is *note soft deprecated: 1ee. in favor of
     multiplication.  There are no plans to remove it.

 -- 類別: ctypes._Pointer

     Private, abstract base class for pointers.

     Concrete pointer types are created by calling *note POINTER():
     15e0. with the type that will be pointed to; this is done
     automatically by *note pointer(): 15df.

     If a pointer points to an array, its elements can be read and
     written using standard subscript and slice accesses.  Pointer
     objects have no size, so *note len(): 5d4. will raise *note
     TypeError: 4dd.  Negative subscripts will read from the memory
     'before' the pointer (as in C), and out-of-range subscripts will
     probably crash with an access violation (if you're lucky).

      -- 屬性: _type_

          Specifies the type pointed to.

      -- 屬性: contents

          Returns the object to which to pointer points.  Assigning to
          this attribute changes the pointer to point to the assigned
          object.


File: python.info,  Node: 並行執行 Concurrent Execution,  Next: Networking and Interprocess Communication,  Prev: 通用作業系統服務,  Up: Python 標準函式庫 Standard Library

5.17 並行執行 (Concurrent Execution)
====================================

本章節描述的模組在程式的並行執行上提供支援。選擇要使用哪一個工具則取決於
是執行什麼樣的任務（CPU 密集或 IO 密集）與偏好的開發風格（事件驅動協作式
多工處理或搶占式多工處理）。以下為此章節總覽：

* Menu:

* threading: threading --- 基於執行緒的平行性. 基於執行緒的平行性
* multiprocessing: multiprocessing --- 以行程為基礎的平行性. 以行程為基礎的平行性
* multiprocessing.shared_memory: multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取. 對於共享記憶體的跨行程直接存取
* concurrent 套件::
* concurrent.futures: concurrent futures --- 啟動平行任務. 啟動平行任務
* subprocess: subprocess --- 子行程管理. 子行程管理
* sched: sched --- 事件排程器. 事件排程器
* queue: queue --- 同步佇列 synchronized queue 類別. 同步佇列 (synchronized queue) 類別
* contextvars: contextvars --- 情境變數. 情境變數
* _thread: _thread --- 低階執行緒 API. 低階執行緒 API


File: python.info,  Node: threading --- 基於執行緒的平行性,  Next: multiprocessing --- 以行程為基礎的平行性,  Up: 並行執行 Concurrent Execution

5.17.1 ‘threading’ -- 基於執行緒的平行性
----------------------------------------

'原始碼：'Lib/threading.py(1)

__________________________________________________________________

This module constructs higher-level threading interfaces on top of the
lower level *note _thread: 2. module.

在 3.7 版的變更: This module used to be optional, it is now always
available.

也參考
......

*note concurrent.futures.ThreadPoolExecutor: 6e6. offers a higher level
interface to push tasks to a background thread without blocking
execution of the calling thread, while still being able to retrieve
their results when needed.

*note queue: a4. provides a thread-safe interface for exchanging data
between running threads.

*note asyncio: 8. offers an alternative approach to achieving task level
concurrency without requiring the use of multiple operating system
threads.

     備註: In the Python 2.x series, this module contained ‘camelCase’
     names for some methods and functions.  These are deprecated as of
     Python 3.10, but they are still supported for compatibility with
     Python 2.5 and lower.

'CPython 實作細節：' In CPython, due to the *note Global Interpreter
Lock: 12e, only one thread can execute Python code at once (even though
certain performance-oriented libraries might overcome this limitation).
If you want your application to make better use of the computational
resources of multi-core machines, you are advised to use *note
multiprocessing: 86. or *note concurrent.futures.ProcessPoolExecutor:
893.  However, threading is still an appropriate model if you want to
run multiple I/O-bound tasks simultaneously.

*note Availability: 1c56.: not WASI.

This module does not work or is not available on WebAssembly.  See *note
WebAssembly 平台: 16e6. for more information.

This module defines the following functions:

 -- 函式: threading.active_count ()

     Return the number of *note Thread: 8f0. objects currently alive.
     The returned count is equal to the length of the list returned by
     *note enumerate(): 17a8.

     The function ‘activeCount’ is a deprecated alias for this function.

 -- 函式: threading.current_thread ()

     Return the current *note Thread: 8f0. object, corresponding to the
     caller's thread of control.  If the caller's thread of control was
     not created through the *note threading: d6. module, a dummy thread
     object with limited functionality is returned.

     The function ‘currentThread’ is a deprecated alias for this
     function.

 -- 函式: threading.excepthook (args, /)

     Handle uncaught exception raised by *note Thread.run(): 9e0.

     The 'args' argument has the following attributes:

        * 'exc_type': Exception type.

        * 'exc_value': Exception value, can be ‘None’.

        * 'exc_traceback': Exception traceback, can be ‘None’.

        * 'thread': Thread which raised the exception, can be ‘None’.

     If 'exc_type' is *note SystemExit: ce7, the exception is silently
     ignored.  Otherwise, the exception is printed out on *note
     sys.stderr: 8dd.

     If this function raises an exception, *note sys.excepthook(): 7af.
     is called to handle it.

     *note threading.excepthook(): 7ef. can be overridden to control how
     uncaught exceptions raised by *note Thread.run(): 9e0. are handled.

     Storing 'exc_value' using a custom hook can create a reference
     cycle.  It should be cleared explicitly to break the reference
     cycle when the exception is no longer needed.

     Storing 'thread' using a custom hook can resurrect it if it is set
     to an object which is being finalized.  Avoid storing 'thread'
     after the custom hook completes to avoid resurrecting objects.

     也參考
     ......

     *note sys.excepthook(): 7af. handles uncaught exceptions.

     在 3.8 版被加入.

 -- 資料: threading.__excepthook__

     Holds the original value of *note threading.excepthook(): 7ef.  It
     is saved so that the original value can be restored in case they
     happen to get replaced with broken or alternative objects.

     在 3.10 版被加入.

 -- 函式: threading.get_ident ()

     Return the 'thread identifier' of the current thread.  This is a
     nonzero integer.  Its value has no direct meaning; it is intended
     as a magic cookie to be used e.g.  to index a dictionary of
     thread-specific data.  Thread identifiers may be recycled when a
     thread exits and another thread is created.

     在 3.3 版被加入.

 -- 函式: threading.get_native_id ()

     Return the native integral Thread ID of the current thread assigned
     by the kernel.  This is a non-negative integer.  Its value may be
     used to uniquely identify this particular thread system-wide (until
     the thread terminates, after which the value may be recycled by the
     OS).

     *note Availability: 1c56.: Windows, FreeBSD, Linux, macOS, OpenBSD,
     NetBSD, AIX, DragonFlyBSD, GNU/kFreeBSD.

     在 3.8 版被加入.

     在 3.13 版的變更: Added support for GNU/kFreeBSD.

 -- 函式: threading.enumerate ()

     Return a list of all *note Thread: 8f0. objects currently active.
     The list includes daemonic threads and dummy thread objects created
     by *note current_thread(): 2db.  It excludes terminated threads and
     threads that have not yet been started.  However, the main thread
     is always part of the result, even when terminated.

 -- 函式: threading.main_thread ()

     Return the main *note Thread: 8f0. object.  In normal conditions,
     the main thread is the thread from which the Python interpreter was
     started.

     在 3.4 版被加入.

 -- 函式: threading.settrace (func)

     Set a trace function for all threads started from the *note
     threading: d6. module.  The 'func' will be passed to *note
     sys.settrace(): 146e. for each thread, before its *note run(): 9e0.
     method is called.

 -- 函式: threading.settrace_all_threads (func)

     Set a trace function for all threads started from the *note
     threading: d6. module and all Python threads that are currently
     executing.

     The 'func' will be passed to *note sys.settrace(): 146e. for each
     thread, before its *note run(): 9e0. method is called.

     在 3.12 版被加入.

 -- 函式: threading.gettrace ()

     Get the trace function as set by *note settrace(): 7ec.

     在 3.10 版被加入.

 -- 函式: threading.setprofile (func)

     Set a profile function for all threads started from the *note
     threading: d6. module.  The 'func' will be passed to *note
     sys.setprofile(): 146d. for each thread, before its *note run():
     9e0. method is called.

 -- 函式: threading.setprofile_all_threads (func)

     Set a profile function for all threads started from the *note
     threading: d6. module and all Python threads that are currently
     executing.

     The 'func' will be passed to *note sys.setprofile(): 146d. for each
     thread, before its *note run(): 9e0. method is called.

     在 3.12 版被加入.

 -- 函式: threading.getprofile ()

     Get the profiler function as set by *note setprofile(): 7ed.

     在 3.10 版被加入.

 -- 函式: threading.stack_size ([size])

     Return the thread stack size used when creating new threads.  The
     optional 'size' argument specifies the stack size to be used for
     subsequently created threads, and must be 0 (use platform or
     configured default) or a positive integer value of at least 32,768
     (32 KiB). If 'size' is not specified, 0 is used.  If changing the
     thread stack size is unsupported, a *note RuntimeError: 179. is
     raised.  If the specified stack size is invalid, a *note
     ValueError: 1e7. is raised and the stack size is unmodified.  32
     KiB is currently the minimum supported stack size value to
     guarantee sufficient stack space for the interpreter itself.  Note
     that some platforms may have particular restrictions on values for
     the stack size, such as requiring a minimum stack size > 32 KiB or
     requiring allocation in multiples of the system memory page size -
     platform documentation should be referred to for more information
     (4 KiB pages are common; using multiples of 4096 for the stack size
     is the suggested approach in the absence of more specific
     information).

     *note 適用: 1c56.：Windows, pthreads。

     Unix platforms with POSIX threads support.

This module also defines the following constant:

 -- 資料: threading.TIMEOUT_MAX

     The maximum value allowed for the 'timeout' parameter of blocking
     functions (*note Lock.acquire(): 63e, *note RLock.acquire(): e1f,
     *note Condition.wait(): 17b4, etc.).  Specifying a timeout greater
     than this value will raise an *note OverflowError: 825.

     在 3.2 版被加入.

This module defines a number of classes, which are detailed in the
sections below.

The design of this module is loosely based on Java's threading model.
However, where Java makes locks and condition variables basic behavior
of every object, they are separate objects in Python.  Python's *note
Thread: 8f0. class supports a subset of the behavior of Java's Thread
class; currently, there are no priorities, no thread groups, and threads
cannot be destroyed, stopped, suspended, resumed, or interrupted.  The
static methods of Java's Thread class, when implemented, are mapped to
module-level functions.

All of the methods described below are executed atomically.

* Menu:

* Thread-Local Data::
* Thread Objects::
* Lock Objects::
* RLock 物件::
* Condition Objects::
* Semaphore Objects::
* Event Objects::
* Timer Objects::
* Barrier Objects::
* Using locks, conditions, and semaphores in the with statement: Using locks conditions and semaphores in the with statement.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/threading.py


File: python.info,  Node: Thread-Local Data,  Next: Thread Objects,  Up: threading --- 基於執行緒的平行性

5.17.1.1 Thread-Local Data
..........................

Thread-local data is data whose values are thread specific.  To manage
thread-local data, just create an instance of *note local: 166d. (or a
subclass) and store attributes on it:

     mydata = threading.local()
     mydata.x = 1

The instance's values will be different for separate threads.

 -- 類別: threading.local

     A class that represents thread-local data.

     For more details and extensive examples, see the documentation
     string of the ‘_threading_local’ module:
     Lib/_threading_local.py(1).

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/_threading_local.py


File: python.info,  Node: Thread Objects,  Next: Lock Objects,  Prev: Thread-Local Data,  Up: threading --- 基於執行緒的平行性

5.17.1.2 Thread Objects
.......................

The *note Thread: 8f0. class represents an activity that is run in a
separate thread of control.  There are two ways to specify the activity:
by passing a callable object to the constructor, or by overriding the
*note run(): 9e0. method in a subclass.  No other methods (except for
the constructor) should be overridden in a subclass.  In other words,
'only' override the ‘__init__()’ and *note run(): 9e0. methods of this
class.

Once a thread object is created, its activity must be started by calling
the thread's *note start(): 2c01. method.  This invokes the *note run():
9e0. method in a separate thread of control.

Once the thread's activity is started, the thread is considered 'alive'.
It stops being alive when its *note run(): 9e0. method terminates -
either normally, or by raising an unhandled exception.  The *note
is_alive(): 8f1. method tests whether the thread is alive.

Other threads can call a thread's *note join(): 117c. method.  This
blocks the calling thread until the thread whose *note join(): 117c.
method is called is terminated.

A thread has a name.  The name can be passed to the constructor, and
read or changed through the *note name: 2da. attribute.

If the *note run(): 9e0. method raises an exception, *note
threading.excepthook(): 7ef. is called to handle it.  By default, *note
threading.excepthook(): 7ef. ignores silently *note SystemExit: ce7.

A thread can be flagged as a "daemon thread".  The significance of this
flag is that the entire Python program exits when only daemon threads
are left.  The initial value is inherited from the creating thread.  The
flag can be set through the *note daemon: 2d8. property or the 'daemon'
constructor argument.

     備註: Daemon threads are abruptly stopped at shutdown.  Their
     resources (such as open files, database transactions, etc.)  may
     not be released properly.  If you want your threads to stop
     gracefully, make them non-daemonic and use a suitable signalling
     mechanism such as an *note Event: 10f1.

There is a "main thread" object; this corresponds to the initial thread
of control in the Python program.  It is not a daemon thread.

There is the possibility that "dummy thread objects" are created.  These
are thread objects corresponding to "alien threads", which are threads
of control started outside the threading module, such as directly from C
code.  Dummy thread objects have limited functionality; they are always
considered alive and daemonic, and cannot be *note joined: 2f3c.  They
are never deleted, since it is impossible to detect the termination of
alien threads.

 -- 類別: threading.Thread (group=None, target=None, name=None, args=(),
          kwargs={}, *, daemon=None)

     This constructor should always be called with keyword arguments.
     Arguments are:

     'group' should be ‘None’; reserved for future extension when a
     ‘ThreadGroup’ class is implemented.

     'target' is the callable object to be invoked by the *note run():
     9e0. method.  Defaults to ‘None’, meaning nothing is called.

     'name' is the thread name.  By default, a unique name is
     constructed of the form "Thread-'N'" where 'N' is a small decimal
     number, or "Thread-'N' (target)" where "target" is
     ‘target.__name__’ if the 'target' argument is specified.

     'args' is a list or tuple of arguments for the target invocation.
     Defaults to ‘()’.

     'kwargs' is a dictionary of keyword arguments for the target
     invocation.  Defaults to ‘{}’.

     If not ‘None’, 'daemon' explicitly sets whether the thread is
     daemonic.  If ‘None’ (the default), the daemonic property is
     inherited from the current thread.

     If the subclass overrides the constructor, it must make sure to
     invoke the base class constructor (‘Thread.__init__()’) before
     doing anything else to the thread.

     在 3.3 版的變更: 新增 'daemon' 參數。

     在 3.10 版的變更: Use the 'target' name if 'name' argument is
     omitted.

      -- 方法: start ()

          Start the thread's activity.

          It must be called at most once per thread object.  It arranges
          for the object's *note run(): 9e0. method to be invoked in a
          separate thread of control.

          This method will raise a *note RuntimeError: 179. if called
          more than once on the same thread object.

      -- 方法: run ()

          Method representing the thread's activity.

          You may override this method in a subclass.  The standard
          *note run(): 9e0. method invokes the callable object passed to
          the object's constructor as the 'target' argument, if any,
          with positional and keyword arguments taken from the 'args'
          and 'kwargs' arguments, respectively.

          Using list or tuple as the 'args' argument which passed to the
          *note Thread: 8f0. could achieve the same effect.

          舉例來說：

               >>> from threading import Thread
               >>> t = Thread(target=print, args=[1])
               >>> t.run()
               1
               >>> t = Thread(target=print, args=(1,))
               >>> t.run()
               1

      -- 方法: join (timeout=None)

          Wait until the thread terminates.  This blocks the calling
          thread until the thread whose *note join(): 117c. method is
          called terminates - either normally or through an unhandled
          exception - or until the optional timeout occurs.

          When the 'timeout' argument is present and not ‘None’, it
          should be a floating-point number specifying a timeout for the
          operation in seconds (or fractions thereof).  As *note join():
          117c. always returns ‘None’, you must call *note is_alive():
          8f1. after *note join(): 117c. to decide whether a timeout
          happened - if the thread is still alive, the *note join():
          117c. call timed out.

          When the 'timeout' argument is not present or ‘None’, the
          operation will block until the thread terminates.

          A thread can be joined many times.

          *note join(): 117c. raises a *note RuntimeError: 179. if an
          attempt is made to join the current thread as that would cause
          a deadlock.  It is also an error to *note join(): 117c. a
          thread before it has been started and attempts to do so raise
          the same exception.

      -- 屬性: name

          A string used for identification purposes only.  It has no
          semantics.  Multiple threads may be given the same name.  The
          initial name is set by the constructor.

      -- 方法: getName ()
      -- 方法: setName ()

          Deprecated getter/setter API for *note name: 2da.; use it
          directly as a property instead.

          在 3.10 版之後被棄用.

      -- 屬性: ident

          The 'thread identifier' of this thread or ‘None’ if the thread
          has not been started.  This is a nonzero integer.  See the
          *note get_ident(): 10f3. function.  Thread identifiers may be
          recycled when a thread exits and another thread is created.
          The identifier is available even after the thread has exited.

      -- 屬性: native_id

          The Thread ID (‘TID’) of this thread, as assigned by the OS
          (kernel).  This is a non-negative integer, or ‘None’ if the
          thread has not been started.  See the *note get_native_id():
          9e1. function.  This value may be used to uniquely identify
          this particular thread system-wide (until the thread
          terminates, after which the value may be recycled by the OS).

               備註: Similar to Process IDs, Thread IDs are only valid
               (guaranteed unique system-wide) from the time the thread
               is created until the thread has been terminated.

          *note Availability: 1c56.: Windows, FreeBSD, Linux, macOS,
          OpenBSD, NetBSD, AIX, DragonFlyBSD.

          在 3.8 版被加入.

      -- 方法: is_alive ()

          Return whether the thread is alive.

          This method returns ‘True’ just before the *note run(): 9e0.
          method starts until just after the *note run(): 9e0. method
          terminates.  The module function *note enumerate(): 17a8.
          returns a list of all alive threads.

      -- 屬性: daemon

          A boolean value indicating whether this thread is a daemon
          thread (‘True’) or not (‘False’).  This must be set before
          *note start(): 2c01. is called, otherwise *note RuntimeError:
          179. is raised.  Its initial value is inherited from the
          creating thread; the main thread is not a daemon thread and
          therefore all threads created in the main thread default to
          *note daemon: 2d8. = ‘False’.

          The entire Python program exits when no alive non-daemon
          threads are left.

      -- 方法: isDaemon ()
      -- 方法: setDaemon ()

          Deprecated getter/setter API for *note daemon: 2d8.; use it
          directly as a property instead.

          在 3.10 版之後被棄用.


File: python.info,  Node: Lock Objects,  Next: RLock 物件,  Prev: Thread Objects,  Up: threading --- 基於執行緒的平行性

5.17.1.3 Lock Objects
.....................

A primitive lock is a synchronization primitive that is not owned by a
particular thread when locked.  In Python, it is currently the lowest
level synchronization primitive available, implemented directly by the
*note _thread: 2. extension module.

A primitive lock is in one of two states, "locked" or "unlocked".  It is
created in the unlocked state.  It has two basic methods, *note
acquire(): 63e. and *note release(): 1257.  When the state is unlocked,
*note acquire(): 63e. changes the state to locked and returns
immediately.  When the state is locked, *note acquire(): 63e. blocks
until a call to *note release(): 1257. in another thread changes it to
unlocked, then the *note acquire(): 63e. call resets it to locked and
returns.  The *note release(): 1257. method should only be called in the
locked state; it changes the state to unlocked and returns immediately.
If an attempt is made to release an unlocked lock, a *note RuntimeError:
179. will be raised.

Locks also support the *note context management protocol: 2f41.

When more than one thread is blocked in *note acquire(): 63e. waiting
for the state to turn to unlocked, only one thread proceeds when a *note
release(): 1257. call resets the state to unlocked; which one of the
waiting threads proceeds is not defined, and may vary across
implementations.

All methods are executed atomically.

 -- 類別: threading.Lock

     The class implementing primitive lock objects.  Once a thread has
     acquired a lock, subsequent attempts to acquire it block, until it
     is released; any thread may release it.

     在 3.13 版的變更: ‘Lock’ is now a class.  In earlier Pythons,
     ‘Lock’ was a factory function which returned an instance of the
     underlying private lock type.

      -- 方法: acquire (blocking=True, timeout=-1)

          Acquire a lock, blocking or non-blocking.

          When invoked with the 'blocking' argument set to ‘True’ (the
          default), block until the lock is unlocked, then set it to
          locked and return ‘True’.

          When invoked with the 'blocking' argument set to ‘False’, do
          not block.  If a call with 'blocking' set to ‘True’ would
          block, return ‘False’ immediately; otherwise, set the lock to
          locked and return ‘True’.

          When invoked with the floating-point 'timeout' argument set to
          a positive value, block for at most the number of seconds
          specified by 'timeout' and as long as the lock cannot be
          acquired.  A 'timeout' argument of ‘-1’ specifies an unbounded
          wait.  It is forbidden to specify a 'timeout' when 'blocking'
          is ‘False’.

          The return value is ‘True’ if the lock is acquired
          successfully, ‘False’ if not (for example if the 'timeout'
          expired).

          在 3.2 版的變更: The 'timeout' parameter is new.

          在 3.2 版的變更: Lock acquisition can now be interrupted by
          signals on POSIX if the underlying threading implementation
          supports it.

      -- 方法: release ()

          Release a lock.  This can be called from any thread, not only
          the thread which has acquired the lock.

          When the lock is locked, reset it to unlocked, and return.  If
          any other threads are blocked waiting for the lock to become
          unlocked, allow exactly one of them to proceed.

          When invoked on an unlocked lock, a *note RuntimeError: 179.
          is raised.

          There is no return value.

      -- 方法: locked ()

          Return ‘True’ if the lock is acquired.


File: python.info,  Node: RLock 物件,  Next: Condition Objects,  Prev: Lock Objects,  Up: threading --- 基於執行緒的平行性

5.17.1.4 RLock 物件
...................

A reentrant lock is a synchronization primitive that may be acquired
multiple times by the same thread.  Internally, it uses the concepts of
"owning thread" and "recursion level" in addition to the locked/unlocked
state used by primitive locks.  In the locked state, some thread owns
the lock; in the unlocked state, no thread owns it.

Threads call a lock's *note acquire(): e1f. method to lock it, and its
*note release(): 1257. method to unlock it.

     備註: Reentrant locks support the *note context management
     protocol: 2f41, so it is recommended to use *note with: 577.
     instead of manually calling *note acquire(): e1f. and *note
     release(): 2f45. to handle acquiring and releasing the lock for a
     block of code.

RLock's *note acquire(): e1f./*note release(): 2f45. call pairs may be
nested, unlike Lock's *note acquire(): 63e./*note release(): 1257.  Only
the final *note release(): 2f45. (the *note release(): 1257. of the
outermost pair) resets the lock to an unlocked state and allows another
thread blocked in *note acquire(): e1f. to proceed.

*note acquire(): e1f./*note release(): 2f45. must be used in pairs: each
acquire must have a release in the thread that has acquired the lock.
Failing to call release as many times the lock has been acquired can
lead to deadlock.

 -- 類別: threading.RLock

     This class implements reentrant lock objects.  A reentrant lock
     must be released by the thread that acquired it.  Once a thread has
     acquired a reentrant lock, the same thread may acquire it again
     without blocking; the thread must release it once for each time it
     has acquired it.

     Note that ‘RLock’ is actually a factory function which returns an
     instance of the most efficient version of the concrete RLock class
     that is supported by the platform.

      -- 方法: acquire (blocking=True, timeout=-1)

          Acquire a lock, blocking or non-blocking.

          也參考
          ......

          *note Using RLock as a context manager: 2f41.

               Recommended over manual ‘acquire()’ and *note release():
               2f45. calls whenever practical.

          When invoked with the 'blocking' argument set to ‘True’ (the
          default):

                  * If no thread owns the lock, acquire the lock and
                    return immediately.

                  * If another thread owns the lock, block until we are
                    able to acquire lock, or 'timeout', if set to a
                    positive float value.

                  * If the same thread owns the lock, acquire the lock
                    again, and return immediately.  This is the
                    difference between *note Lock: 156d. and ‘RLock’;
                    *note Lock: 156d. handles this case the same as the
                    previous, blocking until the lock can be acquired.

          When invoked with the 'blocking' argument set to ‘False’:

                  * If no thread owns the lock, acquire the lock and
                    return immediately.

                  * If another thread owns the lock, return immediately.

                  * If the same thread owns the lock, acquire the lock
                    again and return immediately.

          In all cases, if the thread was able to acquire the lock,
          return ‘True’.  If the thread was unable to acquire the lock
          (i.e.  if not blocking or the timeout was reached) return
          ‘False’.

          If called multiple times, failing to call *note release():
          2f45. as many times may lead to deadlock.  Consider using
          ‘RLock’ as a context manager rather than calling
          acquire/release directly.

          在 3.2 版的變更: The 'timeout' parameter is new.

      -- 方法: release ()

          Release a lock, decrementing the recursion level.  If after
          the decrement it is zero, reset the lock to unlocked (not
          owned by any thread), and if any other threads are blocked
          waiting for the lock to become unlocked, allow exactly one of
          them to proceed.  If after the decrement the recursion level
          is still nonzero, the lock remains locked and owned by the
          calling thread.

          Only call this method when the calling thread owns the lock.
          A *note RuntimeError: 179. is raised if this method is called
          when the lock is not acquired.

          There is no return value.


File: python.info,  Node: Condition Objects,  Next: Semaphore Objects,  Prev: RLock 物件,  Up: threading --- 基於執行緒的平行性

5.17.1.5 Condition Objects
..........................

A condition variable is always associated with some kind of lock; this
can be passed in or one will be created by default.  Passing one in is
useful when several condition variables must share the same lock.  The
lock is part of the condition object: you don't have to track it
separately.

A condition variable obeys the *note context management protocol: 2f41.:
using the ‘with’ statement acquires the associated lock for the duration
of the enclosed block.  The *note acquire(): 2f48. and *note release():
2f49. methods also call the corresponding methods of the associated
lock.

Other methods must be called with the associated lock held.  The *note
wait(): 17b4. method releases the lock, and then blocks until another
thread awakens it by calling *note notify(): 16e1. or *note
notify_all(): 2d5.  Once awakened, *note wait(): 17b4. re-acquires the
lock and returns.  It is also possible to specify a timeout.

The *note notify(): 16e1. method wakes up one of the threads waiting for
the condition variable, if any are waiting.  The *note notify_all():
2d5. method wakes up all threads waiting for the condition variable.

Note: the *note notify(): 16e1. and *note notify_all(): 2d5. methods
don't release the lock; this means that the thread or threads awakened
will not return from their *note wait(): 17b4. call immediately, but
only when the thread that called *note notify(): 16e1. or *note
notify_all(): 2d5. finally relinquishes ownership of the lock.

The typical programming style using condition variables uses the lock to
synchronize access to some shared state; threads that are interested in
a particular change of state call *note wait(): 17b4. repeatedly until
they see the desired state, while threads that modify the state call
*note notify(): 16e1. or *note notify_all(): 2d5. when they change the
state in such a way that it could possibly be a desired state for one of
the waiters.  For example, the following code is a generic
producer-consumer situation with unlimited buffer capacity:

     # Consume one item
     with cv:
         while not an_item_is_available():
             cv.wait()
         get_an_available_item()

     # Produce one item
     with cv:
         make_an_item_available()
         cv.notify()

The ‘while’ loop checking for the application's condition is necessary
because *note wait(): 17b4. can return after an arbitrary long time, and
the condition which prompted the *note notify(): 16e1. call may no
longer hold true.  This is inherent to multi-threaded programming.  The
*note wait_for(): 2f4a. method can be used to automate the condition
checking, and eases the computation of timeouts:

     # Consume an item
     with cv:
         cv.wait_for(an_item_is_available)
         get_an_available_item()

To choose between *note notify(): 16e1. and *note notify_all(): 2d5,
consider whether one state change can be interesting for only one or
several waiting threads.  E.g.  in a typical producer-consumer
situation, adding one item to the buffer only needs to wake up one
consumer thread.

 -- 類別: threading.Condition (lock=None)

     This class implements condition variable objects.  A condition
     variable allows one or more threads to wait until they are notified
     by another thread.

     If the 'lock' argument is given and not ‘None’, it must be a *note
     Lock: 156d. or *note RLock: 2be. object, and it is used as the
     underlying lock.  Otherwise, a new *note RLock: 2be. object is
     created and used as the underlying lock.

     在 3.3 版的變更: changed from a factory function to a class.

      -- 方法: acquire (*args)

          Acquire the underlying lock.  This method calls the
          corresponding method on the underlying lock; the return value
          is whatever that method returns.

      -- 方法: release ()

          Release the underlying lock.  This method calls the
          corresponding method on the underlying lock; there is no
          return value.

      -- 方法: wait (timeout=None)

          Wait until notified or until a timeout occurs.  If the calling
          thread has not acquired the lock when this method is called, a
          *note RuntimeError: 179. is raised.

          This method releases the underlying lock, and then blocks
          until it is awakened by a *note notify(): 16e1. or *note
          notify_all(): 2d5. call for the same condition variable in
          another thread, or until the optional timeout occurs.  Once
          awakened or timed out, it re-acquires the lock and returns.

          When the 'timeout' argument is present and not ‘None’, it
          should be a floating-point number specifying a timeout for the
          operation in seconds (or fractions thereof).

          When the underlying lock is an *note RLock: 2be, it is not
          released using its *note release(): 2f49. method, since this
          may not actually unlock the lock when it was acquired multiple
          times recursively.  Instead, an internal interface of the
          *note RLock: 2be. class is used, which really unlocks it even
          when it has been recursively acquired several times.  Another
          internal interface is then used to restore the recursion level
          when the lock is reacquired.

          The return value is ‘True’ unless a given 'timeout' expired,
          in which case it is ‘False’.

          在 3.2 版的變更: Previously, the method always returned
          ‘None’.

      -- 方法: wait_for (predicate, timeout=None)

          Wait until a condition evaluates to true.  'predicate' should
          be a callable which result will be interpreted as a boolean
          value.  A 'timeout' may be provided giving the maximum time to
          wait.

          This utility method may call *note wait(): 17b4. repeatedly
          until the predicate is satisfied, or until a timeout occurs.
          The return value is the last return value of the predicate and
          will evaluate to ‘False’ if the method timed out.

          Ignoring the timeout feature, calling this method is roughly
          equivalent to writing:

               while not predicate():
                   cv.wait()

          Therefore, the same rules apply as with *note wait(): 17b4.:
          The lock must be held when called and is re-acquired on
          return.  The predicate is evaluated with the lock held.

          在 3.2 版被加入.

      -- 方法: notify (n=1)

          By default, wake up one thread waiting on this condition, if
          any.  If the calling thread has not acquired the lock when
          this method is called, a *note RuntimeError: 179. is raised.

          This method wakes up at most 'n' of the threads waiting for
          the condition variable; it is a no-op if no threads are
          waiting.

          The current implementation wakes up exactly 'n' threads, if at
          least 'n' threads are waiting.  However, it's not safe to rely
          on this behavior.  A future, optimized implementation may
          occasionally wake up more than 'n' threads.

          Note: an awakened thread does not actually return from its
          *note wait(): 17b4. call until it can reacquire the lock.
          Since *note notify(): 16e1. does not release the lock, its
          caller should.

      -- 方法: notify_all ()

          Wake up all threads waiting on this condition.  This method
          acts like *note notify(): 16e1, but wakes up all waiting
          threads instead of one.  If the calling thread has not
          acquired the lock when this method is called, a *note
          RuntimeError: 179. is raised.

          The method ‘notifyAll’ is a deprecated alias for this method.


File: python.info,  Node: Semaphore Objects,  Next: Event Objects,  Prev: Condition Objects,  Up: threading --- 基於執行緒的平行性

5.17.1.6 Semaphore Objects
..........................

This is one of the oldest synchronization primitives in the history of
computer science, invented by the early Dutch computer scientist Edsger
W. Dijkstra (he used the names ‘P()’ and ‘V()’ instead of *note
acquire(): 11ec. and *note release(): 2f4d.).

A semaphore manages an internal counter which is decremented by each
*note acquire(): 11ec. call and incremented by each *note release():
2f4d. call.  The counter can never go below zero; when *note acquire():
11ec. finds that it is zero, it blocks, waiting until some other thread
calls *note release(): 2f4d.

Semaphores also support the *note context management protocol: 2f41.

 -- 類別: threading.Semaphore (value=1)

     This class implements semaphore objects.  A semaphore manages an
     atomic counter representing the number of *note release(): 2f4d.
     calls minus the number of *note acquire(): 11ec. calls, plus an
     initial value.  The *note acquire(): 11ec. method blocks if
     necessary until it can return without making the counter negative.
     If not given, 'value' defaults to 1.

     The optional argument gives the initial 'value' for the internal
     counter; it defaults to ‘1’.  If the 'value' given is less than 0,
     *note ValueError: 1e7. is raised.

     在 3.3 版的變更: changed from a factory function to a class.

      -- 方法: acquire (blocking=True, timeout=None)

          Acquire a semaphore.

          When invoked without arguments:

             * If the internal counter is larger than zero on entry,
               decrement it by one and return ‘True’ immediately.

             * If the internal counter is zero on entry, block until
               awoken by a call to *note release(): 2f4d.  Once awoken
               (and the counter is greater than 0), decrement the
               counter by 1 and return ‘True’.  Exactly one thread will
               be awoken by each call to *note release(): 2f4d.  The
               order in which threads are awoken should not be relied
               on.

          When invoked with 'blocking' set to ‘False’, do not block.  If
          a call without an argument would block, return ‘False’
          immediately; otherwise, do the same thing as when called
          without arguments, and return ‘True’.

          When invoked with a 'timeout' other than ‘None’, it will block
          for at most 'timeout' seconds.  If acquire does not complete
          successfully in that interval, return ‘False’.  Return ‘True’
          otherwise.

          在 3.2 版的變更: The 'timeout' parameter is new.

      -- 方法: release (n=1)

          Release a semaphore, incrementing the internal counter by 'n'.
          When it was zero on entry and other threads are waiting for it
          to become larger than zero again, wake up 'n' of those
          threads.

          在 3.9 版的變更: Added the 'n' parameter to release multiple
          waiting threads at once.

 -- 類別: threading.BoundedSemaphore (value=1)

     Class implementing bounded semaphore objects.  A bounded semaphore
     checks to make sure its current value doesn't exceed its initial
     value.  If it does, *note ValueError: 1e7. is raised.  In most
     situations semaphores are used to guard resources with limited
     capacity.  If the semaphore is released too many times it's a sign
     of a bug.  If not given, 'value' defaults to 1.

     在 3.3 版的變更: changed from a factory function to a class.

* Menu:

* Semaphore 範例::


File: python.info,  Node: Semaphore 範例,  Up: Semaphore Objects

5.17.1.7 ‘Semaphore’ 範例
.........................

Semaphores are often used to guard resources with limited capacity, for
example, a database server.  In any situation where the size of the
resource is fixed, you should use a bounded semaphore.  Before spawning
any worker threads, your main thread would initialize the semaphore:

     maxconnections = 5
     # ...
     pool_sema = BoundedSemaphore(value=maxconnections)

Once spawned, worker threads call the semaphore's acquire and release
methods when they need to connect to the server:

     with pool_sema:
         conn = connectdb()
         try:
             # ... 使用該連線 ...
         finally:
             conn.close()

The use of a bounded semaphore reduces the chance that a programming
error which causes the semaphore to be released more than it's acquired
will go undetected.


File: python.info,  Node: Event Objects,  Next: Timer Objects,  Prev: Semaphore Objects,  Up: threading --- 基於執行緒的平行性

5.17.1.8 Event Objects
......................

This is one of the simplest mechanisms for communication between
threads: one thread signals an event and other threads wait for it.

An event object manages an internal flag that can be set to true with
the *note set(): 2f52. method and reset to false with the *note clear():
2f53. method.  The *note wait(): 12ba. method blocks until the flag is
true.

 -- 類別: threading.Event

     Class implementing event objects.  An event manages a flag that can
     be set to true with the *note set(): 2f52. method and reset to
     false with the *note clear(): 2f53. method.  The *note wait():
     12ba. method blocks until the flag is true.  The flag is initially
     false.

     在 3.3 版的變更: changed from a factory function to a class.

      -- 方法: is_set ()

          Return ‘True’ if and only if the internal flag is true.

          The method ‘isSet’ is a deprecated alias for this method.

      -- 方法: set ()

          Set the internal flag to true.  All threads waiting for it to
          become true are awakened.  Threads that call *note wait():
          12ba. once the flag is true will not block at all.

      -- 方法: clear ()

          Reset the internal flag to false.  Subsequently, threads
          calling *note wait(): 12ba. will block until *note set():
          2f52. is called to set the internal flag to true again.

      -- 方法: wait (timeout=None)

          Block as long as the internal flag is false and the timeout,
          if given, has not expired.  The return value represents the
          reason that this blocking method returned; ‘True’ if returning
          because the internal flag is set to true, or ‘False’ if a
          timeout is given and the internal flag did not become true
          within the given wait time.

          When the timeout argument is present and not ‘None’, it should
          be a floating-point number specifying a timeout for the
          operation in seconds, or fractions thereof.

          在 3.1 版的變更: Previously, the method always returned
          ‘None’.


File: python.info,  Node: Timer Objects,  Next: Barrier Objects,  Prev: Event Objects,  Up: threading --- 基於執行緒的平行性

5.17.1.9 Timer Objects
......................

This class represents an action that should be run only after a certain
amount of time has passed -- a timer.  *note Timer: 10f2. is a subclass
of *note Thread: 8f0. and as such also functions as an example of
creating custom threads.

Timers are started, as with threads, by calling their *note Timer.start:
2c01. method.  The timer can be stopped (before its action has begun) by
calling the *note cancel(): 2f56. method.  The interval the timer will
wait before executing its action may not be exactly the same as the
interval specified by the user.

舉例來說：

     def hello():
         print("hello, world")

     t = Timer(30.0, hello)
     t.start()  # 30 秒後會印出 "hello, world"

 -- 類別: threading.Timer (interval, function, args=None, kwargs=None)

     Create a timer that will run 'function' with arguments 'args' and
     keyword arguments 'kwargs', after 'interval' seconds have passed.
     If 'args' is ‘None’ (the default) then an empty list will be used.
     If 'kwargs' is ‘None’ (the default) then an empty dict will be
     used.

     在 3.3 版的變更: changed from a factory function to a class.

      -- 方法: cancel ()

          Stop the timer, and cancel the execution of the timer's
          action.  This will only work if the timer is still in its
          waiting stage.


File: python.info,  Node: Barrier Objects,  Next: Using locks conditions and semaphores in the with statement,  Prev: Timer Objects,  Up: threading --- 基於執行緒的平行性

5.17.1.10 Barrier Objects
.........................

在 3.2 版被加入.

This class provides a simple synchronization primitive for use by a
fixed number of threads that need to wait for each other.  Each of the
threads tries to pass the barrier by calling the *note wait(): 2f58.
method and will block until all of the threads have made their *note
wait(): 2f58. calls.  At this point, the threads are released
simultaneously.

The barrier can be reused any number of times for the same number of
threads.

As an example, here is a simple way to synchronize a client and server
thread:

     b = Barrier(2, timeout=5)

     def server():
         start_server()
         b.wait()
         while True:
             connection = accept_connection()
             process_server_connection(connection)

     def client():
         b.wait()
         while True:
             connection = make_connection()
             process_client_connection(connection)

 -- 類別: threading.Barrier (parties, action=None, timeout=None)

     Create a barrier object for 'parties' number of threads.  An
     'action', when provided, is a callable to be called by one of the
     threads when they are released.  'timeout' is the default timeout
     value if none is specified for the *note wait(): 2f58. method.

      -- 方法: wait (timeout=None)

          Pass the barrier.  When all the threads party to the barrier
          have called this function, they are all released
          simultaneously.  If a 'timeout' is provided, it is used in
          preference to any that was supplied to the class constructor.

          The return value is an integer in the range 0 to 'parties' -
          1, different for each thread.  This can be used to select a
          thread to do some special housekeeping, e.g.:

               i = barrier.wait()
               if i == 0:
                   # 只會有一個執行緒會印出這個
                   print("passed the barrier")

          If an 'action' was provided to the constructor, one of the
          threads will have called it prior to being released.  Should
          this call raise an error, the barrier is put into the broken
          state.

          If the call times out, the barrier is put into the broken
          state.

          This method may raise a *note BrokenBarrierError: 117d.
          exception if the barrier is broken or reset while a thread is
          waiting.

      -- 方法: reset ()

          Return the barrier to the default, empty state.  Any threads
          waiting on it will receive the *note BrokenBarrierError: 117d.
          exception.

          Note that using this function may require some external
          synchronization if there are other threads whose state is
          unknown.  If a barrier is broken it may be better to just
          leave it and create a new one.

      -- 方法: abort ()

          Put the barrier into a broken state.  This causes any active
          or future calls to *note wait(): 2f58. to fail with the *note
          BrokenBarrierError: 117d.  Use this for example if one of the
          threads needs to abort, to avoid deadlocking the application.

          It may be preferable to simply create the barrier with a
          sensible 'timeout' value to automatically guard against one of
          the threads going awry.

      -- 屬性: parties

          The number of threads required to pass the barrier.

      -- 屬性: n_waiting

          The number of threads currently waiting in the barrier.

      -- 屬性: broken

          A boolean that is ‘True’ if the barrier is in the broken
          state.

 -- 例外: threading.BrokenBarrierError

     This exception, a subclass of *note RuntimeError: 179, is raised
     when the *note Barrier: 117b. object is reset or broken.


File: python.info,  Node: Using locks conditions and semaphores in the with statement,  Prev: Barrier Objects,  Up: threading --- 基於執行緒的平行性

5.17.1.11 Using locks, conditions, and semaphores in the ‘with’ statement
.........................................................................

All of the objects provided by this module that have ‘acquire’ and
‘release’ methods can be used as context managers for a *note with: 577.
statement.  The ‘acquire’ method will be called when the block is
entered, and ‘release’ will be called when the block is exited.  Hence,
the following snippet:

     with some_lock:
         # 做某些事情...

is equivalent to:

     some_lock.acquire()
     try:
         # 做某些事情...
     finally:
         some_lock.release()

Currently, *note Lock: 156d, *note RLock: 2be, *note Condition: 10ee,
*note Semaphore: 10ef, and *note BoundedSemaphore: 10f0. objects may be
used as *note with: 577. statement context managers.


File: python.info,  Node: multiprocessing --- 以行程為基礎的平行性,  Next: multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取,  Prev: threading --- 基於執行緒的平行性,  Up: 並行執行 Concurrent Execution

5.17.2 ‘multiprocessing’ -- 以行程為基礎的平行性
------------------------------------------------

'原始碼：'Lib/multiprocessing/(1)

__________________________________________________________________

*note Availability: 1c56.: not WASI, not iOS.

This module does not work or is not available on WebAssembly platforms,
or on iOS. See *note WebAssembly 平台: 16e6. for more information on
WASM availability; see *note iOS: 1d56. for more information on iOS
availability.

* Menu:

* 簡介: 簡介<7>.
* Reference: Reference<2>.
* Programming guidelines::
* 範例: 範例<19>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/multiprocessing/


File: python.info,  Node: 簡介<7>,  Next: Reference<2>,  Up: multiprocessing --- 以行程為基礎的平行性

5.17.2.1 簡介
.............

*note multiprocessing: 86. is a package that supports spawning processes
using an API similar to the *note threading: d6. module.  The *note
multiprocessing: 86. package offers both local and remote concurrency,
effectively side-stepping the *note Global Interpreter Lock: 12e. by
using subprocesses instead of threads.  Due to this, the *note
multiprocessing: 86. module allows the programmer to fully leverage
multiple processors on a given machine.  It runs on both POSIX and
Windows.

The *note multiprocessing: 86. module also introduces APIs which do not
have analogs in the *note threading: d6. module.  A prime example of
this is the *note Pool: f0e. object which offers a convenient means of
parallelizing the execution of a function across multiple input values,
distributing the input data across processes (data parallelism).  The
following example demonstrates the common practice of defining such
functions in a module so that child processes can successfully import
that module.  This basic example of data parallelism using *note Pool:
f0e,

     from multiprocessing import Pool

     def f(x):
         return x*x

     if __name__ == '__main__':
         with Pool(5) as p:
             print(p.map(f, [1, 2, 3]))

will print to standard output

     [1, 4, 9]

也參考
......

*note concurrent.futures.ProcessPoolExecutor: 893. offers a higher level
interface to push tasks to a background process without blocking
execution of the calling process.  Compared to using the *note Pool:
f0e. interface directly, the *note concurrent.futures: 1a. API more
readily allows the submission of work to the underlying process pool to
be separated from waiting for the results.

* Menu:

* Process 類別::
* Contexts and start methods::
* Exchanging objects between processes::
* Synchronization between processes::
* Sharing state between processes::
* Using a pool of workers::


File: python.info,  Node: Process 類別,  Next: Contexts and start methods,  Up: 簡介<7>

5.17.2.2 ‘Process’ 類別
.......................

In *note multiprocessing: 86, processes are spawned by creating a *note
Process: afd. object and then calling its *note start(): 2f63. method.
*note Process: afd. follows the API of *note threading.Thread: 8f0.  A
trivial example of a multiprocess program is

     from multiprocessing import Process

     def f(name):
         print('hello', name)

     if __name__ == '__main__':
         p = Process(target=f, args=('bob',))
         p.start()
         p.join()

To show the individual process IDs involved, here is an expanded
example:

     from multiprocessing import Process
     import os

     def info(title):
         print(title)
         print('module name:', __name__)
         print('parent process:', os.getppid())
         print('process id:', os.getpid())

     def f(name):
         info('function f')
         print('hello', name)

     if __name__ == '__main__':
         info('main line')
         p = Process(target=f, args=('bob',))
         p.start()
         p.join()

For an explanation of why the ‘if __name__ == '__main__'’ part is
necessary, see *note Programming guidelines: 2f64.


File: python.info,  Node: Contexts and start methods,  Next: Exchanging objects between processes,  Prev: Process 類別,  Up: 簡介<7>

5.17.2.3 Contexts and start methods
...................................

Depending on the platform, *note multiprocessing: 86. supports three
ways to start a process.  These 'start methods' are

     'spawn'

          The parent process starts a fresh Python interpreter process.
          The child process will only inherit those resources necessary
          to run the process object's *note run(): 2f66. method.  In
          particular, unnecessary file descriptors and handles from the
          parent process will not be inherited.  Starting a process
          using this method is rather slow compared to using 'fork' or
          'forkserver'.

          Available on POSIX and Windows platforms.  The default on
          Windows and macOS.

     'fork'

          The parent process uses *note os.fork(): 17b. to fork the
          Python interpreter.  The child process, when it begins, is
          effectively identical to the parent process.  All resources of
          the parent are inherited by the child process.  Note that
          safely forking a multithreaded process is problematic.

          Available on POSIX systems.  Currently the default on POSIX
          except macOS.

               備註: The default start method will change away from
               'fork' in Python 3.14.  Code that requires 'fork' should
               explicitly specify that via *note get_context(): 2a8. or
               *note set_start_method(): 2a9.

          在 3.12 版的變更: If Python is able to detect that your
          process has multiple threads, the *note os.fork(): 17b.
          function that this start method calls internally will raise a
          *note DeprecationWarning: 18b.  Use a different start method.
          See the *note os.fork(): 17b. documentation for further
          explanation.

     'forkserver'

          When the program starts and selects the 'forkserver' start
          method, a server process is spawned.  From then on, whenever a
          new process is needed, the parent process connects to the
          server and requests that it fork a new process.  The fork
          server process is single threaded unless system libraries or
          preloaded imports spawn threads as a side-effect so it is
          generally safe for it to use *note os.fork(): 17b.  No
          unnecessary resources are inherited.

          Available on POSIX platforms which support passing file
          descriptors over Unix pipes such as Linux.

在 3.4 版的變更: 'spawn' added on all POSIX platforms, and 'forkserver'
added for some POSIX platforms.  Child processes no longer inherit all
of the parents inheritable handles on Windows.

在 3.8 版的變更: On macOS, the 'spawn' start method is now the default.
The 'fork' start method should be considered unsafe as it can lead to
crashes of the subprocess as macOS system libraries may start threads.
See bpo-33725(1).

On POSIX using the 'spawn' or 'forkserver' start methods will also start
a 'resource tracker' process which tracks the unlinked named system
resources (such as named semaphores or *note SharedMemory: 154f.
objects) created by processes of the program.  When all processes have
exited the resource tracker unlinks any remaining tracked object.
Usually there should be none, but if a process was killed by a signal
there may be some "leaked" resources.  (Neither leaked semaphores nor
shared memory segments will be automatically unlinked until the next
reboot.  This is problematic for both objects because the system allows
only a limited number of named semaphores, and shared memory segments
occupy some space in the main memory.)

To select a start method you use the *note set_start_method(): 2a9. in
the ‘if __name__ == '__main__'’ clause of the main module.  For example:

     import multiprocessing as mp

     def foo(q):
         q.put('hello')

     if __name__ == '__main__':
         mp.set_start_method('spawn')
         q = mp.Queue()
         p = mp.Process(target=foo, args=(q,))
         p.start()
         print(q.get())
         p.join()

*note set_start_method(): 2a9. should not be used more than once in the
program.

Alternatively, you can use *note get_context(): 2a8. to obtain a context
object.  Context objects have the same API as the multiprocessing
module, and allow one to use multiple start methods in the same program.

     import multiprocessing as mp

     def foo(q):
         q.put('hello')

     if __name__ == '__main__':
         ctx = mp.get_context('spawn')
         q = ctx.Queue()
         p = ctx.Process(target=foo, args=(q,))
         p.start()
         print(q.get())
         p.join()

Note that objects related to one context may not be compatible with
processes for a different context.  In particular, locks created using
the 'fork' context cannot be passed to processes started using the
'spawn' or 'forkserver' start methods.

A library which wants to use a particular start method should probably
use *note get_context(): 2a8. to avoid interfering with the choice of
the library user.

     警告: The ‘'spawn'’ and ‘'forkserver'’ start methods generally
     cannot be used with "frozen" executables (i.e., binaries produced
     by packages like 'PyInstaller' and 'cx_Freeze') on POSIX systems.
     The ‘'fork'’ start method may work if code does not use threads.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33725


File: python.info,  Node: Exchanging objects between processes,  Next: Synchronization between processes,  Prev: Contexts and start methods,  Up: 簡介<7>

5.17.2.4 Exchanging objects between processes
.............................................

*note multiprocessing: 86. supports two types of communication channel
between processes:

'Queues'

     The *note Queue: 1701. class is a near clone of *note queue.Queue:
     131c.  For example:

          from multiprocessing import Process, Queue

          def f(q):
              q.put([42, None, 'hello'])

          if __name__ == '__main__':
              q = Queue()
              p = Process(target=f, args=(q,))
              p.start()
              print(q.get())    # 印出 "[42, None, 'hello']"
              p.join()

     Queues are thread and process safe.  Any object put into a *note
     multiprocessing: 86. queue will be serialized.

'Pipes'

     The *note Pipe(): 2f68. function returns a pair of connection
     objects connected by a pipe which by default is duplex (two-way).
     For example:

          from multiprocessing import Process, Pipe

          def f(conn):
              conn.send([42, None, 'hello'])
              conn.close()

          if __name__ == '__main__':
              parent_conn, child_conn = Pipe()
              p = Process(target=f, args=(child_conn,))
              p.start()
              print(parent_conn.recv())   # 印出 "[42, None, 'hello']"
              p.join()

     The two connection objects returned by *note Pipe(): 2f68.
     represent the two ends of the pipe.  Each connection object has
     ‘send()’ and ‘recv()’ methods (among others).  Note that data in a
     pipe may become corrupted if two processes (or threads) try to read
     from or write to the 'same' end of the pipe at the same time.  Of
     course there is no risk of corruption from processes using
     different ends of the pipe at the same time.

     The ‘send()’ method serializes the the object and ‘recv()’
     re-creates the object.


File: python.info,  Node: Synchronization between processes,  Next: Sharing state between processes,  Prev: Exchanging objects between processes,  Up: 簡介<7>

5.17.2.5 Synchronization between processes
..........................................

*note multiprocessing: 86. contains equivalents of all the
synchronization primitives from *note threading: d6.  For instance one
can use a lock to ensure that only one process prints to standard output
at a time:

     from multiprocessing import Process, Lock

     def f(l, i):
         l.acquire()
         try:
             print('hello world', i)
         finally:
             l.release()

     if __name__ == '__main__':
         lock = Lock()

         for num in range(10):
             Process(target=f, args=(lock, num)).start()

Without using the lock output from the different processes is liable to
get all mixed up.


File: python.info,  Node: Sharing state between processes,  Next: Using a pool of workers,  Prev: Synchronization between processes,  Up: 簡介<7>

5.17.2.6 Sharing state between processes
........................................

As mentioned above, when doing concurrent programming it is usually best
to avoid using shared state as far as possible.  This is particularly
true when using multiple processes.

However, if you really do need to use some shared data then *note
multiprocessing: 86. provides a couple of ways of doing so.

'Shared memory'

     Data can be stored in a shared memory map using *note Value: 2f6b.
     or *note Array: 2f6c.  For example, the following code

          from multiprocessing import Process, Value, Array

          def f(n, a):
              n.value = 3.1415927
              for i in range(len(a)):
                  a[i] = -a[i]

          if __name__ == '__main__':
              num = Value('d', 0.0)
              arr = Array('i', range(10))

              p = Process(target=f, args=(num, arr))
              p.start()
              p.join()

              print(num.value)
              print(arr[:])

     will print

          3.1415927
          [0, -1, -2, -3, -4, -5, -6, -7, -8, -9]

     The ‘'d'’ and ‘'i'’ arguments used when creating ‘num’ and ‘arr’
     are typecodes of the kind used by the *note array: 6. module: ‘'d'’
     indicates a double precision float and ‘'i'’ indicates a signed
     integer.  These shared objects will be process and thread-safe.

     For more flexibility in using shared memory one can use the *note
     multiprocessing.sharedctypes: 8c. module which supports the
     creation of arbitrary ctypes objects allocated from shared memory.

'Server process'

     A manager object returned by *note Manager(): c61. controls a
     server process which holds Python objects and allows other
     processes to manipulate them using proxies.

     A manager returned by *note Manager(): c61. will support types
     *note list: 5b6, *note dict: 23b, *note Namespace: 2f6d, *note
     Lock: 2f6e, *note RLock: 2f6f, *note Semaphore: 2f70, *note
     BoundedSemaphore: 2f71, *note Condition: 2f72, *note Event: 1766,
     *note Barrier: 2f73, *note Queue: 1701, *note Value: 2f6b. and
     *note Array: 2f6c.  For example,

          from multiprocessing import Process, Manager

          def f(d, l):
              d[1] = '1'
              d['2'] = 2
              d[0.25] = None
              l.reverse()

          if __name__ == '__main__':
              with Manager() as manager:
                  d = manager.dict()
                  l = manager.list(range(10))

                  p = Process(target=f, args=(d, l))
                  p.start()
                  p.join()

                  print(d)
                  print(l)

     will print

          {0.25: None, 1: '1', '2': 2}
          [9, 8, 7, 6, 5, 4, 3, 2, 1, 0]

     Server process managers are more flexible than using shared memory
     objects because they can be made to support arbitrary object types.
     Also, a single manager can be shared by processes on different
     computers over a network.  They are, however, slower than using
     shared memory.


File: python.info,  Node: Using a pool of workers,  Prev: Sharing state between processes,  Up: 簡介<7>

5.17.2.7 Using a pool of workers
................................

The *note Pool: f0e. class represents a pool of worker processes.  It
has methods which allows tasks to be offloaded to the worker processes
in a few different ways.

舉例來說：

     from multiprocessing import Pool, TimeoutError
     import time
     import os

     def f(x):
         return x*x

     if __name__ == '__main__':
         # start 4 worker processes
         with Pool(processes=4) as pool:

             # print "[0, 1, 4,..., 81]"
             print(pool.map(f, range(10)))

             # print same numbers in arbitrary order
             for i in pool.imap_unordered(f, range(10)):
                 print(i)

             # evaluate "f(20)" asynchronously
             res = pool.apply_async(f, (20,))      # runs in *only* one process
             print(res.get(timeout=1))             # prints "400"

             # evaluate "os.getpid()" asynchronously
             res = pool.apply_async(os.getpid, ()) # runs in *only* one process
             print(res.get(timeout=1))             # prints the PID of that process

             # launching multiple evaluations asynchronously *may* use more processes
             multiple_results = [pool.apply_async(os.getpid, ()) for i in range(4)]
             print([res.get(timeout=1) for res in multiple_results])

             # make a single worker sleep for 10 seconds
             res = pool.apply_async(time.sleep, (10,))
             try:
                 print(res.get(timeout=1))
             except TimeoutError:
                 print("We lacked patience and got a multiprocessing.TimeoutError")

             print("For the moment, the pool remains available for more work")

         # exiting the 'with'-block has stopped the pool
         print("Now the pool is closed and no longer available")

Note that the methods of a pool should only ever be used by the process
which created it.

     備註: Functionality within this package requires that the
     ‘__main__’ module be importable by the children.  This is covered
     in *note Programming guidelines: 2f64. however it is worth pointing
     out here.  This means that some examples, such as the *note
     multiprocessing.pool.Pool: f0e. examples will not work in the
     interactive interpreter.  For example:

          >>> from multiprocessing import Pool
          >>> p = Pool(5)
          >>> def f(x):
          ...     return x*x
          ...
          >>> with p:
          ...     p.map(f, [1,2,3])
          Process PoolWorker-1:
          Process PoolWorker-2:
          Process PoolWorker-3:
          Traceback (most recent call last):
          Traceback (most recent call last):
          Traceback (most recent call last):
          AttributeError: Can't get attribute 'f' on <module '__main__' (<class '_frozen_importlib.BuiltinImporter'>)>
          AttributeError: Can't get attribute 'f' on <module '__main__' (<class '_frozen_importlib.BuiltinImporter'>)>
          AttributeError: Can't get attribute 'f' on <module '__main__' (<class '_frozen_importlib.BuiltinImporter'>)>

     (If you try this it will actually output three full tracebacks
     interleaved in a semi-random fashion, and then you may have to stop
     the parent process somehow.)


File: python.info,  Node: Reference<2>,  Next: Programming guidelines,  Prev: 簡介<7>,  Up: multiprocessing --- 以行程為基礎的平行性

5.17.2.8 Reference
..................

The *note multiprocessing: 86. package mostly replicates the API of the
*note threading: d6. module.

* Menu:

* Process 與例外::
* Pipes and Queues::
* Miscellaneous: Miscellaneous<2>.
* Connection Objects::
* Synchronization primitives::
* 共享的 ctypes 物件::
* Managers::
* Proxy Objects::
* Process Pools::
* Listeners and Clients::
* Authentication keys::
* Logging::
* multiprocessing.dummy 模組: multiprocessing dummy 模組.


File: python.info,  Node: Process 與例外,  Next: Pipes and Queues,  Up: Reference<2>

5.17.2.9 ‘Process’ 與例外
.........................

 -- 類別: multiprocessing.Process (group=None, target=None, name=None,
          args=(), kwargs={}, *, daemon=None)

     Process objects represent activity that is run in a separate
     process.  The *note Process: afd. class has equivalents of all the
     methods of *note threading.Thread: 8f0.

     The constructor should always be called with keyword arguments.
     'group' should always be ‘None’; it exists solely for compatibility
     with *note threading.Thread: 8f0.  'target' is the callable object
     to be invoked by the *note run(): 2f66. method.  It defaults to
     ‘None’, meaning nothing is called.  'name' is the process name (see
     *note name: 2f77. for more details).  'args' is the argument tuple
     for the target invocation.  'kwargs' is a dictionary of keyword
     arguments for the target invocation.  If provided, the keyword-only
     'daemon' argument sets the process *note daemon: 2f78. flag to
     ‘True’ or ‘False’.  If ‘None’ (the default), this flag will be
     inherited from the creating process.

     By default, no arguments are passed to 'target'.  The 'args'
     argument, which defaults to ‘()’, can be used to specify a list or
     tuple of the arguments to pass to 'target'.

     If a subclass overrides the constructor, it must make sure it
     invokes the base class constructor (‘Process.__init__()’) before
     doing anything else to the process.

     在 3.3 版的變更: 新增 'daemon' 參數。

      -- 方法: run ()

          Method representing the process's activity.

          You may override this method in a subclass.  The standard
          *note run(): 2f66. method invokes the callable object passed
          to the object's constructor as the target argument, if any,
          with sequential and keyword arguments taken from the 'args'
          and 'kwargs' arguments, respectively.

          Using a list or tuple as the 'args' argument passed to *note
          Process: afd. achieves the same effect.

          範例：

               >>> from multiprocessing import Process
               >>> p = Process(target=print, args=[1])
               >>> p.run()
               1
               >>> p = Process(target=print, args=(1,))
               >>> p.run()
               1

      -- 方法: start ()

          Start the process's activity.

          This must be called at most once per process object.  It
          arranges for the object's *note run(): 2f66. method to be
          invoked in a separate process.

      -- 方法: join ([timeout])

          If the optional argument 'timeout' is ‘None’ (the default),
          the method blocks until the process whose *note join(): 2f79.
          method is called terminates.  If 'timeout' is a positive
          number, it blocks at most 'timeout' seconds.  Note that the
          method returns ‘None’ if its process terminates or if the
          method times out.  Check the process's *note exitcode: 2f7a.
          to determine if it terminated.

          A process can be joined many times.

          A process cannot join itself because this would cause a
          deadlock.  It is an error to attempt to join a process before
          it has been started.

      -- 屬性: name

          The process's name.  The name is a string used for
          identification purposes only.  It has no semantics.  Multiple
          processes may be given the same name.

          The initial name is set by the constructor.  If no explicit
          name is provided to the constructor, a name of the form
          'Process-N[1]:N[2]:...:N[k]' is constructed, where each N[k]
          is the N-th child of its parent.

      -- 方法: is_alive ()

          Return whether the process is alive.

          Roughly, a process object is alive from the moment the *note
          start(): 2f63. method returns until the child process
          terminates.

      -- 屬性: daemon

          The process's daemon flag, a Boolean value.  This must be set
          before *note start(): 2f63. is called.

          The initial value is inherited from the creating process.

          When a process exits, it attempts to terminate all of its
          daemonic child processes.

          Note that a daemonic process is not allowed to create child
          processes.  Otherwise a daemonic process would leave its
          children orphaned if it gets terminated when its parent
          process exits.  Additionally, these are 'not' Unix daemons or
          services, they are normal processes that will be terminated
          (and not joined) if non-daemonic processes have exited.

     In addition to the *note threading.Thread: 8f0. API, *note Process:
     afd. objects also support the following attributes and methods:

      -- 屬性: pid

          Return the process ID. Before the process is spawned, this
          will be ‘None’.

      -- 屬性: exitcode

          The child's exit code.  This will be ‘None’ if the process has
          not yet terminated.

          If the child's *note run(): 2f66. method returned normally,
          the exit code will be 0.  If it terminated via *note
          sys.exit(): 12dd. with an integer argument 'N', the exit code
          will be 'N'.

          If the child terminated due to an exception not caught within
          *note run(): 2f66, the exit code will be 1.  If it was
          terminated by signal 'N', the exit code will be the negative
          value '-N'.

      -- 屬性: authkey

          The process's authentication key (a byte string).

          When *note multiprocessing: 86. is initialized the main
          process is assigned a random string using *note os.urandom():
          4c7.

          When a *note Process: afd. object is created, it will inherit
          the authentication key of its parent process, although this
          may be changed by setting *note authkey: 2f7d. to another byte
          string.

          參閱 *note Authentication keys: 2f7e.。

      -- 屬性: sentinel

          A numeric handle of a system object which will become "ready"
          when the process ends.

          You can use this value if you want to wait on several events
          at once using *note multiprocessing.connection.wait(): 1079.
          Otherwise calling *note join(): 2f79. is simpler.

          On Windows, this is an OS handle usable with the
          ‘WaitForSingleObject’ and ‘WaitForMultipleObjects’ family of
          API calls.  On POSIX, this is a file descriptor usable with
          primitives from the *note select: af. module.

          在 3.3 版被加入.

      -- 方法: terminate ()

          Terminate the process.  On POSIX this is done using the *note
          SIGTERM: 134d. signal; on Windows ‘TerminateProcess()’ is
          used.  Note that exit handlers and finally clauses, etc., will
          not be executed.

          Note that descendant processes of the process will 'not' be
          terminated - they will simply become orphaned.

               警告: If this method is used when the associated process
               is using a pipe or queue then the pipe or queue is liable
               to become corrupted and may become unusable by other
               process.  Similarly, if the process has acquired a lock
               or semaphore etc.  then terminating it is liable to cause
               other processes to deadlock.

      -- 方法: kill ()

          Same as *note terminate(): 2f7f. but using the ‘SIGKILL’
          signal on POSIX.

          在 3.7 版被加入.

      -- 方法: close ()

          Close the *note Process: afd. object, releasing all resources
          associated with it.  *note ValueError: 1e7. is raised if the
          underlying process is still running.  Once *note close(): afb.
          returns successfully, most other methods and attributes of the
          *note Process: afd. object will raise *note ValueError: 1e7.

          在 3.7 版被加入.

     Note that the *note start(): 2f63, *note join(): 2f79, *note
     is_alive(): 2f7b, *note terminate(): 2f7f. and *note exitcode:
     2f7a. methods should only be called by the process that created the
     process object.

     Example usage of some of the methods of *note Process: afd.:

          >>> import multiprocessing, time, signal
          >>> mp_context = multiprocessing.get_context('spawn')
          >>> p = mp_context.Process(target=time.sleep, args=(1000,))
          >>> print(p, p.is_alive())
          <...Process ... initial> False
          >>> p.start()
          >>> print(p, p.is_alive())
          <...Process ... started> True
          >>> p.terminate()
          >>> time.sleep(0.1)
          >>> print(p, p.is_alive())
          <...Process ... stopped exitcode=-SIGTERM> False
          >>> p.exitcode == -signal.SIGTERM
          True

 -- 例外: multiprocessing.ProcessError

     The base class of all *note multiprocessing: 86. exceptions.

 -- 例外: multiprocessing.BufferTooShort

     Exception raised by ‘Connection.recv_bytes_into()’ when the
     supplied buffer object is too small for the message read.

     If ‘e’ is an instance of *note BufferTooShort: 2f81. then
     ‘e.args[0]’ will give the message as a byte string.

 -- 例外: multiprocessing.AuthenticationError

     Raised when there is an authentication error.

 -- 例外: multiprocessing.TimeoutError

     Raised by methods with a timeout when the timeout expires.


File: python.info,  Node: Pipes and Queues,  Next: Miscellaneous<2>,  Prev: Process 與例外,  Up: Reference<2>

5.17.2.10 Pipes and Queues
..........................

When using multiple processes, one generally uses message passing for
communication between processes and avoids having to use any
synchronization primitives like locks.

For passing messages one can use *note Pipe(): 2f68. (for a connection
between two processes) or a queue (which allows multiple producers and
consumers).

The *note Queue: 1701, *note SimpleQueue: 8b9. and *note JoinableQueue:
2f85. types are multi-producer, multi-consumer FIFO queues modelled on
the *note queue.Queue: 131c. class in the standard library.  They differ
in that *note Queue: 1701. lacks the *note task_done(): 2f86. and *note
join(): 2f87. methods introduced into Python 2.5's *note queue.Queue:
131c. class.

If you use *note JoinableQueue: 2f85. then you 'must' call *note
JoinableQueue.task_done(): 2f88. for each task removed from the queue or
else the semaphore used to count the number of unfinished tasks may
eventually overflow, raising an exception.

One difference from other Python queue implementations, is that *note
multiprocessing: 86. queues serializes all objects that are put into
them using *note pickle: 95.  The object return by the get method is a
re-created object that does not share memory with the original object.

Note that one can also create a shared queue by using a manager object -
see *note Managers: 2f89.

     備註: *note multiprocessing: 86. uses the usual *note queue.Empty:
     2f8a. and *note queue.Full: 2f8b. exceptions to signal a timeout.
     They are not available in the *note multiprocessing: 86. namespace
     so you need to import them from *note queue: a4.

     備註: When an object is put on a queue, the object is pickled and a
     background thread later flushes the pickled data to an underlying
     pipe.  This has some consequences which are a little surprising,
     but should not cause any practical difficulties - if they really
     bother you then you can instead use a queue created with a *note
     manager: 2f89.

       1. After putting an object on an empty queue there may be an
          infinitesimal delay before the queue's *note empty(): 14ee.
          method returns *note False: adb. and *note get_nowait(): 2f8c.
          can return without raising *note queue.Empty: 2f8a.

       2. If multiple processes are enqueuing objects, it is possible
          for the objects to be received at the other end out-of-order.
          However, objects enqueued by the same process will always be
          in the expected order with respect to each other.

     警告: If a process is killed using *note Process.terminate(): 2f7f.
     or *note os.kill(): 12f4. while it is trying to use a *note Queue:
     1701, then the data in the queue is likely to become corrupted.
     This may cause any other process to get an exception when it tries
     to use the queue later on.

     警告: As mentioned above, if a child process has put items on a
     queue (and it has not used *note JoinableQueue.cancel_join_thread:
     2f8d.), then that process will not terminate until all buffered
     items have been flushed to the pipe.

     This means that if you try joining that process you may get a
     deadlock unless you are sure that all items which have been put on
     the queue have been consumed.  Similarly, if the child process is
     non-daemonic then the parent process may hang on exit when it tries
     to join all its non-daemonic children.

     Note that a queue created using a manager does not have this issue.
     See *note Programming guidelines: 2f64.

For an example of the usage of queues for interprocess communication see
*note 範例: 2f8e.

 -- 函式: multiprocessing.Pipe ([duplex])

     Returns a pair ‘(conn1, conn2)’ of *note Connection: 15a2. objects
     representing the ends of a pipe.

     If 'duplex' is ‘True’ (the default) then the pipe is bidirectional.
     If 'duplex' is ‘False’ then the pipe is unidirectional: ‘conn1’ can
     only be used for receiving messages and ‘conn2’ can only be used
     for sending messages.

     The ‘send()’ method serializes the the object using *note pickle:
     95. and the ‘recv()’ re-creates the object.

 -- 類別: multiprocessing.Queue ([maxsize])

     Returns a process shared queue implemented using a pipe and a few
     locks/semaphores.  When a process first puts an item on the queue a
     feeder thread is started which transfers objects from a buffer into
     the pipe.

     The usual *note queue.Empty: 2f8a. and *note queue.Full: 2f8b.
     exceptions from the standard library's *note queue: a4. module are
     raised to signal timeouts.

     *note Queue: 1701. implements all the methods of *note queue.Queue:
     131c. except for *note task_done(): 2f86. and *note join(): 2f87.

      -- 方法: qsize ()

          Return the approximate size of the queue.  Because of
          multithreading/multiprocessing semantics, this number is not
          reliable.

          Note that this may raise *note NotImplementedError: 20d. on
          platforms like macOS where ‘sem_getvalue()’ is not
          implemented.

      -- 方法: empty ()

          Return ‘True’ if the queue is empty, ‘False’ otherwise.
          Because of multithreading/multiprocessing semantics, this is
          not reliable.

          May raise an *note OSError: 350. on closed queues.  (not
          guaranteed)

      -- 方法: full ()

          Return ‘True’ if the queue is full, ‘False’ otherwise.
          Because of multithreading/multiprocessing semantics, this is
          not reliable.

      -- 方法: put (obj[, block[, timeout]])

          Put obj into the queue.  If the optional argument 'block' is
          ‘True’ (the default) and 'timeout' is ‘None’ (the default),
          block if necessary until a free slot is available.  If
          'timeout' is a positive number, it blocks at most 'timeout'
          seconds and raises the *note queue.Full: 2f8b. exception if no
          free slot was available within that time.  Otherwise ('block'
          is ‘False’), put an item on the queue if a free slot is
          immediately available, else raise the *note queue.Full: 2f8b.
          exception ('timeout' is ignored in that case).

          在 3.8 版的變更: If the queue is closed, *note ValueError:
          1e7. is raised instead of *note AssertionError: 64e.

      -- 方法: put_nowait (obj)

          Equivalent to ‘put(obj, False)’.

      -- 方法: get ([block[, timeout]])

          Remove and return an item from the queue.  If optional args
          'block' is ‘True’ (the default) and 'timeout' is ‘None’ (the
          default), block if necessary until an item is available.  If
          'timeout' is a positive number, it blocks at most 'timeout'
          seconds and raises the *note queue.Empty: 2f8a. exception if
          no item was available within that time.  Otherwise (block is
          ‘False’), return an item if one is immediately available, else
          raise the *note queue.Empty: 2f8a. exception ('timeout' is
          ignored in that case).

          在 3.8 版的變更: If the queue is closed, *note ValueError:
          1e7. is raised instead of *note OSError: 350.

      -- 方法: get_nowait ()

          Equivalent to ‘get(False)’.

     *note multiprocessing.Queue: 1701. has a few additional methods not
     found in *note queue.Queue: 131c.  These methods are usually
     unnecessary for most code:

      -- 方法: close ()

          Indicate that no more data will be put on this queue by the
          current process.  The background thread will quit once it has
          flushed all buffered data to the pipe.  This is called
          automatically when the queue is garbage collected.

      -- 方法: join_thread ()

          Join the background thread.  This can only be used after *note
          close(): 1702. has been called.  It blocks until the
          background thread exits, ensuring that all data in the buffer
          has been flushed to the pipe.

          By default if a process is not the creator of the queue then
          on exit it will attempt to join the queue's background thread.
          The process can call *note cancel_join_thread(): 2f8d. to make
          *note join_thread(): 2f92. do nothing.

      -- 方法: cancel_join_thread ()

          Prevent *note join_thread(): 2f92. from blocking.  In
          particular, this prevents the background thread from being
          joined automatically when the process exits - see *note
          join_thread(): 2f92.

          A better name for this method might be
          ‘allow_exit_without_flush()’.  It is likely to cause enqueued
          data to be lost, and you almost certainly will not need to use
          it.  It is really only there if you need the current process
          to exit immediately without waiting to flush enqueued data to
          the underlying pipe, and you don't care about lost data.

          備註: This class's functionality requires a functioning shared
          semaphore implementation on the host operating system.
          Without one, the functionality in this class will be disabled,
          and attempts to instantiate a *note Queue: 1701. will result
          in an *note ImportError: 352.  See bpo-3770(1) for additional
          information.  The same holds true for any of the specialized
          queue types listed below.

 -- 類別: multiprocessing.SimpleQueue

     It is a simplified *note Queue: 1701. type, very close to a locked
     *note Pipe: 2f68.

      -- 方法: close ()

          Close the queue: release internal resources.

          A queue must not be used anymore after it is closed.  For
          example, *note get(): 2f93, *note put(): 2f94. and *note
          empty(): 14ef. methods must no longer be called.

          在 3.9 版被加入.

      -- 方法: empty ()

          Return ‘True’ if the queue is empty, ‘False’ otherwise.

          Always raises an *note OSError: 350. if the SimpleQueue is
          closed.

      -- 方法: get ()

          Remove and return an item from the queue.

      -- 方法: put (item)

          Put 'item' into the queue.

 -- 類別: multiprocessing.JoinableQueue ([maxsize])

     *note JoinableQueue: 2f85, a *note Queue: 1701. subclass, is a
     queue which additionally has *note task_done(): 2f88. and *note
     join(): 2f95. methods.

      -- 方法: task_done ()

          Indicate that a formerly enqueued task is complete.  Used by
          queue consumers.  For each *note get(): 1943. used to fetch a
          task, a subsequent call to *note task_done(): 2f88. tells the
          queue that the processing on the task is complete.

          If a *note join(): 2f87. is currently blocking, it will resume
          when all items have been processed (meaning that a *note
          task_done(): 2f88. call was received for every item that had
          been *note put(): 1942. into the queue).

          Raises a *note ValueError: 1e7. if called more times than
          there were items placed in the queue.

      -- 方法: join ()

          Block until all items in the queue have been gotten and
          processed.

          The count of unfinished tasks goes up whenever an item is
          added to the queue.  The count goes down whenever a consumer
          calls *note task_done(): 2f88. to indicate that the item was
          retrieved and all work on it is complete.  When the count of
          unfinished tasks drops to zero, *note join(): 2f87. unblocks.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=3770


File: python.info,  Node: Miscellaneous<2>,  Next: Connection Objects,  Prev: Pipes and Queues,  Up: Reference<2>

5.17.2.11 Miscellaneous
.......................

 -- 函式: multiprocessing.active_children ()

     Return list of all live children of the current process.

     Calling this has the side effect of "joining" any processes which
     have already finished.

 -- 函式: multiprocessing.cpu_count ()

     Return the number of CPUs in the system.

     This number is not equivalent to the number of CPUs the current
     process can use.  The number of usable CPUs can be obtained with
     *note os.process_cpu_count(): 1a7. (or
     ‘len(os.sched_getaffinity(0))’).

     When the number of CPUs cannot be determined a *note
     NotImplementedError: 20d. is raised.

     也參考
     ......

     *note os.cpu_count(): 1a8. *note os.process_cpu_count(): 1a7.

     在 3.13 版的變更: The return value can also be overridden using the
     *note -X cpu_count: 15a. flag or *note PYTHON_CPU_COUNT: 1f5. as
     this is merely a wrapper around the *note os: 91. cpu count APIs.

 -- 函式: multiprocessing.current_process ()

     Return the *note Process: afd. object corresponding to the current
     process.

     An analogue of *note threading.current_thread(): 2db.

 -- 函式: multiprocessing.parent_process ()

     Return the *note Process: afd. object corresponding to the parent
     process of the *note current_process(): 2f98.  For the main
     process, ‘parent_process’ will be ‘None’.

     在 3.8 版被加入.

 -- 函式: multiprocessing.freeze_support ()

     Add support for when a program which uses *note multiprocessing:
     86. has been frozen to produce a Windows executable.  (Has been
     tested with 'py2exe', 'PyInstaller' and 'cx_Freeze'.)

     One needs to call this function straight after the ‘if __name__ ==
     '__main__'’ line of the main module.  For example:

          from multiprocessing import Process, freeze_support

          def f():
              print('hello world!')

          if __name__ == '__main__':
              freeze_support()
              Process(target=f).start()

     If the ‘freeze_support()’ line is omitted then trying to run the
     frozen executable will raise *note RuntimeError: 179.

     Calling ‘freeze_support()’ has no effect when invoked on any
     operating system other than Windows.  In addition, if the module is
     being run normally by the Python interpreter on Windows (the
     program has not been frozen), then ‘freeze_support()’ has no
     effect.

 -- 函式: multiprocessing.get_all_start_methods ()

     Returns a list of the supported start methods, the first of which
     is the default.  The possible start methods are ‘'fork'’, ‘'spawn'’
     and ‘'forkserver'’.  Not all platforms support all methods.  See
     *note Contexts and start methods: 2aa.

     在 3.4 版被加入.

 -- 函式: multiprocessing.get_context (method=None)

     Return a context object which has the same attributes as the *note
     multiprocessing: 86. module.

     If 'method' is ‘None’ then the default context is returned.
     Otherwise 'method' should be ‘'fork'’, ‘'spawn'’, ‘'forkserver'’.
     *note ValueError: 1e7. is raised if the specified start method is
     not available.  See *note Contexts and start methods: 2aa.

     在 3.4 版被加入.

 -- 函式: multiprocessing.get_start_method (allow_none=False)

     Return the name of start method used for starting processes.

     If the start method has not been fixed and 'allow_none' is false,
     then the start method is fixed to the default and the name is
     returned.  If the start method has not been fixed and 'allow_none'
     is true then ‘None’ is returned.

     The return value can be ‘'fork'’, ‘'spawn'’, ‘'forkserver'’ or
     ‘None’.  See *note Contexts and start methods: 2aa.

     在 3.4 版被加入.

     在 3.8 版的變更: On macOS, the 'spawn' start method is now the
     default.  The 'fork' start method should be considered unsafe as it
     can lead to crashes of the subprocess.  See bpo-33725(1).

 -- 函式: multiprocessing.set_executable (executable)

     Set the path of the Python interpreter to use when starting a child
     process.  (By default *note sys.executable: 383. is used).
     Embedders will probably need to do some thing like

          set_executable(os.path.join(sys.exec_prefix, 'pythonw.exe'))

     before they can create child processes.

     在 3.4 版的變更: Now supported on POSIX when the ‘'spawn'’ start
     method is used.

     在 3.11 版的變更: 接受一個*note 類路徑物件: ac2.。

 -- 函式: multiprocessing.set_forkserver_preload (module_names)

     Set a list of module names for the forkserver main process to
     attempt to import so that their already imported state is inherited
     by forked processes.  Any *note ImportError: 352. when doing so is
     silently ignored.  This can be used as a performance enhancement to
     avoid repeated work in every process.

     For this to work, it must be called before the forkserver process
     has been launched (before creating a ‘Pool’ or starting a *note
     Process: afd.).

     Only meaningful when using the ‘'forkserver'’ start method.  See
     *note Contexts and start methods: 2aa.

     在 3.4 版被加入.

 -- 函式: multiprocessing.set_start_method (method, force=False)

     Set the method which should be used to start child processes.  The
     'method' argument can be ‘'fork'’, ‘'spawn'’ or ‘'forkserver'’.
     Raises *note RuntimeError: 179. if the start method has already
     been set and 'force' is not ‘True’.  If 'method' is ‘None’ and
     'force' is ‘True’ then the start method is set to ‘None’.  If
     'method' is ‘None’ and 'force' is ‘False’ then the context is set
     to the default context.

     Note that this should be called at most once, and it should be
     protected inside the ‘if __name__ == '__main__'’ clause of the main
     module.

     參閱 *note Contexts and start methods: 2aa.。

     在 3.4 版被加入.

     備註: *note multiprocessing: 86. contains no analogues of *note
     threading.active_count(): 2dc, *note threading.enumerate(): 17a8,
     *note threading.settrace(): 7ec, *note threading.setprofile(): 7ed,
     *note threading.Timer: 10f2, or *note threading.local: 166d.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33725


File: python.info,  Node: Connection Objects,  Next: Synchronization primitives,  Prev: Miscellaneous<2>,  Up: Reference<2>

5.17.2.12 Connection Objects
............................

Connection objects allow the sending and receiving of picklable objects
or strings.  They can be thought of as message oriented connected
sockets.

Connection objects are usually created using *note Pipe: 2f68. - see
also *note Listeners and Clients: 2f9c.

 -- 類別: multiprocessing.connection.Connection

      -- 方法: send (obj)

          Send an object to the other end of the connection which should
          be read using *note recv(): 2f9e.

          The object must be picklable.  Very large pickles
          (approximately 32 MiB+, though it depends on the OS) may raise
          a *note ValueError: 1e7. exception.

      -- 方法: recv ()

          Return an object sent from the other end of the connection
          using *note send(): 2f9d.  Blocks until there is something to
          receive.  Raises *note EOFError: 126c. if there is nothing
          left to receive and the other end was closed.

      -- 方法: fileno ()

          Return the file descriptor or handle used by the connection.

      -- 方法: close ()

          Close the connection.

          This is called automatically when the connection is garbage
          collected.

      -- 方法: poll ([timeout])

          Return whether there is any data available to be read.

          If 'timeout' is not specified then it will return immediately.
          If 'timeout' is a number then this specifies the maximum time
          in seconds to block.  If 'timeout' is ‘None’ then an infinite
          timeout is used.

          Note that multiple connection objects may be polled at once by
          using *note multiprocessing.connection.wait(): 1079.

      -- 方法: send_bytes (buffer[, offset[, size]])

          Send byte data from a *note bytes-like object: cd4. as a
          complete message.

          If 'offset' is given then data is read from that position in
          'buffer'.  If 'size' is given then that many bytes will be
          read from buffer.  Very large buffers (approximately 32 MiB+,
          though it depends on the OS) may raise a *note ValueError:
          1e7. exception

      -- 方法: recv_bytes ([maxlength])

          Return a complete message of byte data sent from the other end
          of the connection as a string.  Blocks until there is
          something to receive.  Raises *note EOFError: 126c. if there
          is nothing left to receive and the other end has closed.

          If 'maxlength' is specified and the message is longer than
          'maxlength' then *note OSError: 350. is raised and the
          connection will no longer be readable.

          在 3.3 版的變更: This function used to raise *note IOError:
          ff5, which is now an alias of *note OSError: 350.

      -- 方法: recv_bytes_into (buffer[, offset])

          Read into 'buffer' a complete message of byte data sent from
          the other end of the connection and return the number of bytes
          in the message.  Blocks until there is something to receive.
          Raises *note EOFError: 126c. if there is nothing left to
          receive and the other end was closed.

          'buffer' must be a writable *note bytes-like object: cd4.  If
          'offset' is given then the message will be written into the
          buffer from that position.  Offset must be a non-negative
          integer less than the length of 'buffer' (in bytes).

          If the buffer is too short then a ‘BufferTooShort’ exception
          is raised and the complete message is available as ‘e.args[0]’
          where ‘e’ is the exception instance.

     在 3.3 版的變更: Connection objects themselves can now be
     transferred between processes using *note Connection.send(): 2f9d.
     and *note Connection.recv(): 2f9e.

     Connection objects also now support the context management protocol
     - see *note 情境管理器型別: 1e95.  *note __enter__(): 2124. returns
     the connection object, and *note __exit__(): 2125. calls *note
     close(): 2fa0.

舉例來說：

     >>> from multiprocessing import Pipe
     >>> a, b = Pipe()
     >>> a.send([1, 'hello', None])
     >>> b.recv()
     [1, 'hello', None]
     >>> b.send_bytes(b'thank you')
     >>> a.recv_bytes()
     b'thank you'
     >>> import array
     >>> arr1 = array.array('i', range(5))
     >>> arr2 = array.array('i', [0] * 10)
     >>> a.send_bytes(arr1)
     >>> count = b.recv_bytes_into(arr2)
     >>> assert count == len(arr1) * arr1.itemsize
     >>> arr2
     array('i', [0, 1, 2, 3, 4, 0, 0, 0, 0, 0])
     警告: The *note Connection.recv(): 2f9e. method automatically
     unpickles the data it receives, which can be a security risk unless
     you can trust the process which sent the message.

     Therefore, unless the connection object was produced using ‘Pipe()’
     you should only use the *note recv(): 2f9e. and *note send(): 2f9d.
     methods after performing some sort of authentication.  See *note
     Authentication keys: 2f7e.

     警告: If a process is killed while it is trying to read or write to
     a pipe then the data in the pipe is likely to become corrupted,
     because it may become impossible to be sure where the message
     boundaries lie.


File: python.info,  Node: Synchronization primitives,  Next: 共享的 ctypes 物件,  Prev: Connection Objects,  Up: Reference<2>

5.17.2.13 Synchronization primitives
....................................

Generally synchronization primitives are not as necessary in a
multiprocess program as they are in a multithreaded program.  See the
documentation for *note threading: d6. module.

Note that one can also create synchronization primitives by using a
manager object - see *note Managers: 2f89.

 -- 類別: multiprocessing.Barrier (parties[, action[, timeout]])

     A barrier object: a clone of *note threading.Barrier: 117b.

     在 3.3 版被加入.

 -- 類別: multiprocessing.BoundedSemaphore ([value])

     A bounded semaphore object: a close analog of *note
     threading.BoundedSemaphore: 10f0.

     A solitary difference from its close analog exists: its ‘acquire’
     method's first argument is named 'block', as is consistent with
     *note Lock.acquire(): 2fa7.

          備註: On macOS, this is indistinguishable from *note
          Semaphore: 2f70. because ‘sem_getvalue()’ is not implemented
          on that platform.

 -- 類別: multiprocessing.Condition ([lock])

     A condition variable: an alias for *note threading.Condition: 10ee.

     If 'lock' is specified then it should be a *note Lock: 2f6e. or
     *note RLock: 2f6f. object from *note multiprocessing: 86.

     在 3.3 版的變更: The *note wait_for(): 2f4a. method was added.

 -- 類別: multiprocessing.Event

     A clone of *note threading.Event: 10f1.

 -- 類別: multiprocessing.Lock

     A non-recursive lock object: a close analog of *note
     threading.Lock: 156d.  Once a process or thread has acquired a
     lock, subsequent attempts to acquire it from any process or thread
     will block until it is released; any process or thread may release
     it.  The concepts and behaviors of *note threading.Lock: 156d. as
     it applies to threads are replicated here in *note
     multiprocessing.Lock: 2f6e. as it applies to either processes or
     threads, except as noted.

     Note that *note Lock: 2f6e. is actually a factory function which
     returns an instance of ‘multiprocessing.synchronize.Lock’
     initialized with a default context.

     *note Lock: 2f6e. supports the *note context manager: 576. protocol
     and thus may be used in *note with: 577. statements.

      -- 方法: acquire (block=True, timeout=None)

          Acquire a lock, blocking or non-blocking.

          With the 'block' argument set to ‘True’ (the default), the
          method call will block until the lock is in an unlocked state,
          then set it to locked and return ‘True’.  Note that the name
          of this first argument differs from that in *note
          threading.Lock.acquire(): 63e.

          With the 'block' argument set to ‘False’, the method call does
          not block.  If the lock is currently in a locked state, return
          ‘False’; otherwise set the lock to a locked state and return
          ‘True’.

          When invoked with a positive, floating-point value for
          'timeout', block for at most the number of seconds specified
          by 'timeout' as long as the lock can not be acquired.
          Invocations with a negative value for 'timeout' are equivalent
          to a 'timeout' of zero.  Invocations with a 'timeout' value of
          ‘None’ (the default) set the timeout period to infinite.  Note
          that the treatment of negative or ‘None’ values for 'timeout'
          differs from the implemented behavior in *note
          threading.Lock.acquire(): 63e.  The 'timeout' argument has no
          practical implications if the 'block' argument is set to
          ‘False’ and is thus ignored.  Returns ‘True’ if the lock has
          been acquired or ‘False’ if the timeout period has elapsed.

      -- 方法: release ()

          Release a lock.  This can be called from any process or
          thread, not only the process or thread which originally
          acquired the lock.

          Behavior is the same as in *note threading.Lock.release():
          1257. except that when invoked on an unlocked lock, a *note
          ValueError: 1e7. is raised.

 -- 類別: multiprocessing.RLock

     A recursive lock object: a close analog of *note threading.RLock:
     2be.  A recursive lock must be released by the process or thread
     that acquired it.  Once a process or thread has acquired a
     recursive lock, the same process or thread may acquire it again
     without blocking; that process or thread must release it once for
     each time it has been acquired.

     Note that *note RLock: 2f6f. is actually a factory function which
     returns an instance of ‘multiprocessing.synchronize.RLock’
     initialized with a default context.

     *note RLock: 2f6f. supports the *note context manager: 576.
     protocol and thus may be used in *note with: 577. statements.

      -- 方法: acquire (block=True, timeout=None)

          Acquire a lock, blocking or non-blocking.

          When invoked with the 'block' argument set to ‘True’, block
          until the lock is in an unlocked state (not owned by any
          process or thread) unless the lock is already owned by the
          current process or thread.  The current process or thread then
          takes ownership of the lock (if it does not already have
          ownership) and the recursion level inside the lock increments
          by one, resulting in a return value of ‘True’.  Note that
          there are several differences in this first argument's
          behavior compared to the implementation of *note
          threading.RLock.acquire(): e1f, starting with the name of the
          argument itself.

          When invoked with the 'block' argument set to ‘False’, do not
          block.  If the lock has already been acquired (and thus is
          owned) by another process or thread, the current process or
          thread does not take ownership and the recursion level within
          the lock is not changed, resulting in a return value of
          ‘False’.  If the lock is in an unlocked state, the current
          process or thread takes ownership and the recursion level is
          incremented, resulting in a return value of ‘True’.

          Use and behaviors of the 'timeout' argument are the same as in
          *note Lock.acquire(): 2fa7.  Note that some of these behaviors
          of 'timeout' differ from the implemented behaviors in *note
          threading.RLock.acquire(): e1f.

      -- 方法: release ()

          Release a lock, decrementing the recursion level.  If after
          the decrement the recursion level is zero, reset the lock to
          unlocked (not owned by any process or thread) and if any other
          processes or threads are blocked waiting for the lock to
          become unlocked, allow exactly one of them to proceed.  If
          after the decrement the recursion level is still nonzero, the
          lock remains locked and owned by the calling process or
          thread.

          Only call this method when the calling process or thread owns
          the lock.  An *note AssertionError: 64e. is raised if this
          method is called by a process or thread other than the owner
          or if the lock is in an unlocked (unowned) state.  Note that
          the type of exception raised in this situation differs from
          the implemented behavior in *note threading.RLock.release():
          2f45.

 -- 類別: multiprocessing.Semaphore ([value])

     A semaphore object: a close analog of *note threading.Semaphore:
     10ef.

     A solitary difference from its close analog exists: its ‘acquire’
     method's first argument is named 'block', as is consistent with
     *note Lock.acquire(): 2fa7.

     備註: On macOS, ‘sem_timedwait’ is unsupported, so calling
     ‘acquire()’ with a timeout will emulate that function's behavior
     using a sleeping loop.

     備註: Some of this package's functionality requires a functioning
     shared semaphore implementation on the host operating system.
     Without one, the ‘multiprocessing.synchronize’ module will be
     disabled, and attempts to import it will result in an *note
     ImportError: 352.  See bpo-3770(1) for additional information.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=3770


File: python.info,  Node: 共享的 ctypes 物件,  Next: Managers,  Prev: Synchronization primitives,  Up: Reference<2>

5.17.2.14 共享的 ‘ctypes’ 物件
..............................

It is possible to create shared objects using shared memory which can be
inherited by child processes.

 -- 函式: multiprocessing.Value (typecode_or_type, *args, lock=True)

     Return a *note ctypes: 22. object allocated from shared memory.  By
     default the return value is actually a synchronized wrapper for the
     object.  The object itself can be accessed via the 'value'
     attribute of a *note Value: 2f6b.

     'typecode_or_type' determines the type of the returned object: it
     is either a ctypes type or a one character typecode of the kind
     used by the *note array: 6. module.  '*args' is passed on to the
     constructor for the type.

     If 'lock' is ‘True’ (the default) then a new recursive lock object
     is created to synchronize access to the value.  If 'lock' is a
     *note Lock: 2f6e. or *note RLock: 2f6f. object then that will be
     used to synchronize access to the value.  If 'lock' is ‘False’ then
     access to the returned object will not be automatically protected
     by a lock, so it will not necessarily be "process-safe".

     Operations like ‘+=’ which involve a read and write are not atomic.
     So if, for instance, you want to atomically increment a shared
     value it is insufficient to just do

          counter.value += 1

     Assuming the associated lock is recursive (which it is by default)
     you can instead do

          with counter.get_lock():
              counter.value += 1

     Note that 'lock' is a keyword-only argument.

 -- 函式: multiprocessing.Array (typecode_or_type, size_or_initializer,
          *, lock=True)

     Return a ctypes array allocated from shared memory.  By default the
     return value is actually a synchronized wrapper for the array.

     'typecode_or_type' determines the type of the elements of the
     returned array: it is either a ctypes type or a one character
     typecode of the kind used by the *note array: 6. module.  If
     'size_or_initializer' is an integer, then it determines the length
     of the array, and the array will be initially zeroed.  Otherwise,
     'size_or_initializer' is a sequence which is used to initialize the
     array and whose length determines the length of the array.

     If 'lock' is ‘True’ (the default) then a new lock object is created
     to synchronize access to the value.  If 'lock' is a *note Lock:
     2f6e. or *note RLock: 2f6f. object then that will be used to
     synchronize access to the value.  If 'lock' is ‘False’ then access
     to the returned object will not be automatically protected by a
     lock, so it will not necessarily be "process-safe".

     Note that 'lock' is a keyword only argument.

     Note that an array of *note ctypes.c_char: 2eb2. has 'value' and
     'raw' attributes which allow one to use it to store and retrieve
     strings.

* Menu:

* multiprocessing.sharedctypes 模組: multiprocessing sharedctypes 模組.


File: python.info,  Node: multiprocessing sharedctypes 模組,  Up: 共享的 ctypes 物件

5.17.2.15 ‘multiprocessing.sharedctypes’ 模組
.............................................

The *note multiprocessing.sharedctypes: 8c. module provides functions
for allocating *note ctypes: 22. objects from shared memory which can be
inherited by child processes.

     備註: Although it is possible to store a pointer in shared memory
     remember that this will refer to a location in the address space of
     a specific process.  However, the pointer is quite likely to be
     invalid in the context of a second process and trying to
     dereference the pointer from the second process may cause a crash.

 -- 函式: multiprocessing.sharedctypes.RawArray (typecode_or_type,
          size_or_initializer)

     Return a ctypes array allocated from shared memory.

     'typecode_or_type' determines the type of the elements of the
     returned array: it is either a ctypes type or a one character
     typecode of the kind used by the *note array: 6. module.  If
     'size_or_initializer' is an integer then it determines the length
     of the array, and the array will be initially zeroed.  Otherwise
     'size_or_initializer' is a sequence which is used to initialize the
     array and whose length determines the length of the array.

     Note that setting and getting an element is potentially non-atomic
     - use *note Array(): 2fae. instead to make sure that access is
     automatically synchronized using a lock.

 -- 函式: multiprocessing.sharedctypes.RawValue (typecode_or_type,
          *args)

     Return a ctypes object allocated from shared memory.

     'typecode_or_type' determines the type of the returned object: it
     is either a ctypes type or a one character typecode of the kind
     used by the *note array: 6. module.  '*args' is passed on to the
     constructor for the type.

     Note that setting and getting the value is potentially non-atomic -
     use *note Value(): 2fb0. instead to make sure that access is
     automatically synchronized using a lock.

     Note that an array of *note ctypes.c_char: 2eb2. has ‘value’ and
     ‘raw’ attributes which allow one to use it to store and retrieve
     strings - see documentation for *note ctypes: 22.

 -- 函式: multiprocessing.sharedctypes.Array (typecode_or_type,
          size_or_initializer, *, lock=True)

     The same as *note RawArray(): 2fad. except that depending on the
     value of 'lock' a process-safe synchronization wrapper may be
     returned instead of a raw ctypes array.

     If 'lock' is ‘True’ (the default) then a new lock object is created
     to synchronize access to the value.  If 'lock' is a *note Lock:
     2f6e. or *note RLock: 2f6f. object then that will be used to
     synchronize access to the value.  If 'lock' is ‘False’ then access
     to the returned object will not be automatically protected by a
     lock, so it will not necessarily be "process-safe".

     Note that 'lock' is a keyword-only argument.

 -- 函式: multiprocessing.sharedctypes.Value (typecode_or_type, *args,
          lock=True)

     The same as *note RawValue(): 2faf. except that depending on the
     value of 'lock' a process-safe synchronization wrapper may be
     returned instead of a raw ctypes object.

     If 'lock' is ‘True’ (the default) then a new lock object is created
     to synchronize access to the value.  If 'lock' is a *note Lock:
     2f6e. or *note RLock: 2f6f. object then that will be used to
     synchronize access to the value.  If 'lock' is ‘False’ then access
     to the returned object will not be automatically protected by a
     lock, so it will not necessarily be "process-safe".

     Note that 'lock' is a keyword-only argument.

 -- 函式: multiprocessing.sharedctypes.copy (obj)

     Return a ctypes object allocated from shared memory which is a copy
     of the ctypes object 'obj'.

 -- 函式: multiprocessing.sharedctypes.synchronized (obj[, lock])

     Return a process-safe wrapper object for a ctypes object which uses
     'lock' to synchronize access.  If 'lock' is ‘None’ (the default)
     then a *note multiprocessing.RLock: 2f6f. object is created
     automatically.

     A synchronized wrapper will have two methods in addition to those
     of the object it wraps: ‘get_obj()’ returns the wrapped object and
     ‘get_lock()’ returns the lock object used for synchronization.

     Note that accessing the ctypes object through the wrapper can be a
     lot slower than accessing the raw ctypes object.

     在 3.5 版的變更: Synchronized objects support the *note context
     manager: 576. protocol.

The table below compares the syntax for creating shared ctypes objects
from shared memory with the normal ctypes syntax.  (In the table
‘MyStruct’ is some subclass of *note ctypes.Structure: 154d.)

ctypes                   sharedctypes using type        sharedctypes using typecode
                                                        
----------------------------------------------------------------------------------------
                                                        
c_double(2.4)            RawValue(c_double, 2.4)        RawValue('d', 2.4)
                                                        
                                                        
MyStruct(4, 6)           RawValue(MyStruct, 4, 6)
                         
                                                        
(c_short * 7)()          RawArray(c_short, 7)           RawArray('h', 7)
                                                        
                                                        
(c_int * 3)(9, 2, 8)     RawArray(c_int, (9, 2, 8))     RawArray('i', (9, 2, 8))
                                                        

Below is an example where a number of ctypes objects are modified by a
child process:

     from multiprocessing import Process, Lock
     from multiprocessing.sharedctypes import Value, Array
     from ctypes import Structure, c_double

     class Point(Structure):
         _fields_ = [('x', c_double), ('y', c_double)]

     def modify(n, x, s, A):
         n.value **= 2
         x.value **= 2
         s.value = s.value.upper()
         for a in A:
             a.x **= 2
             a.y **= 2

     if __name__ == '__main__':
         lock = Lock()

         n = Value('i', 7)
         x = Value(c_double, 1.0/3.0, lock=False)
         s = Array('c', b'hello world', lock=lock)
         A = Array(Point, [(1.875,-6.25), (-5.75,2.0), (2.375,9.5)], lock=lock)

         p = Process(target=modify, args=(n, x, s, A))
         p.start()
         p.join()

         print(n.value)
         print(x.value)
         print(s.value)
         print([(a.x, a.y) for a in A])

The results printed are

     49
     0.1111111111111111
     HELLO WORLD
     [(3.515625, 39.0625), (33.0625, 4.0), (5.640625, 90.25)]


File: python.info,  Node: Managers,  Next: Proxy Objects,  Prev: 共享的 ctypes 物件,  Up: Reference<2>

5.17.2.16 Managers
..................

Managers provide a way to create data which can be shared between
different processes, including sharing over a network between processes
running on different machines.  A manager object controls a server
process which manages 'shared objects'.  Other processes can access the
shared objects by using proxies.

 -- 函式: multiprocessing.Manager ()

     Returns a started *note SyncManager: 2fb3. object which can be used
     for sharing objects between processes.  The returned manager object
     corresponds to a spawned child process and has methods which will
     create shared objects and return corresponding proxies.

Manager processes will be shutdown as soon as they are garbage collected
or their parent process exits.  The manager classes are defined in the
*note multiprocessing.managers: 89. module:

 -- 類別: multiprocessing.managers.BaseManager (address=None,
          authkey=None, serializer='pickle', ctx=None, *,
          shutdown_timeout=1.0)

     建立一個 BaseManager 物件。

     Once created one should call *note start(): 2fb5. or
     ‘get_server().serve_forever()’ to ensure that the manager object
     refers to a started manager process.

     'address' is the address on which the manager process listens for
     new connections.  If 'address' is ‘None’ then an arbitrary one is
     chosen.

     'authkey' is the authentication key which will be used to check the
     validity of incoming connections to the server process.  If
     'authkey' is ‘None’ then ‘current_process().authkey’ is used.
     Otherwise 'authkey' is used and it must be a byte string.

     'serializer' must be ‘'pickle'’ (use *note pickle: 95.
     serialization) or ‘'xmlrpclib'’ (use *note xmlrpc.client: 114.
     serialization).

     'ctx' is a context object, or ‘None’ (use the current context).
     See the ‘get_context()’ function.

     'shutdown_timeout' is a timeout in seconds used to wait until the
     process used by the manager completes in the *note shutdown():
     2fb6. method.  If the shutdown times out, the process is
     terminated.  If terminating the process also times out, the process
     is killed.

     在 3.11 版的變更: 新增 'shutdown_timeout' 參數。

      -- 方法: start ([initializer[, initargs]])

          Start a subprocess to start the manager.  If 'initializer' is
          not ‘None’ then the subprocess will call
          ‘initializer(*initargs)’ when it starts.

      -- 方法: get_server ()

          Returns a ‘Server’ object which represents the actual server
          under the control of the Manager.  The ‘Server’ object
          supports the ‘serve_forever()’ method:

               >>> from multiprocessing.managers import BaseManager
               >>> manager = BaseManager(address=('', 50000), authkey=b'abc')
               >>> server = manager.get_server()
               >>> server.serve_forever()

          ‘Server’ additionally has an *note address: 2fb8. attribute.

      -- 方法: connect ()

          Connect a local manager object to a remote manager process:

               >>> from multiprocessing.managers import BaseManager
               >>> m = BaseManager(address=('127.0.0.1', 50000), authkey=b'abc')
               >>> m.connect()

      -- 方法: shutdown ()

          Stop the process used by the manager.  This is only available
          if *note start(): 2fb5. has been used to start the server
          process.

          This can be called multiple times.

      -- 方法: register (typeid[, callable[, proxytype[, exposed[,
               method_to_typeid[, create_method]]]]])

          A classmethod which can be used for registering a type or
          callable with the manager class.

          'typeid' is a "type identifier" which is used to identify a
          particular type of shared object.  This must be a string.

          'callable' is a callable used for creating objects for this
          type identifier.  If a manager instance will be connected to
          the server using the *note connect(): 2fb9. method, or if the
          'create_method' argument is ‘False’ then this can be left as
          ‘None’.

          'proxytype' is a subclass of *note BaseProxy: 2fbb. which is
          used to create proxies for shared objects with this 'typeid'.
          If ‘None’ then a proxy class is created automatically.

          'exposed' is used to specify a sequence of method names which
          proxies for this typeid should be allowed to access using
          *note BaseProxy._callmethod(): 2fbc.  (If 'exposed' is ‘None’
          then ‘proxytype._exposed_’ is used instead if it exists.)  In
          the case where no exposed list is specified, all "public
          methods" of the shared object will be accessible.  (Here a
          "public method" means any attribute which has a *note
          __call__(): 4fe. method and whose name does not begin with
          ‘'_'’.)

          'method_to_typeid' is a mapping used to specify the return
          type of those exposed methods which should return a proxy.  It
          maps method names to typeid strings.  (If 'method_to_typeid'
          is ‘None’ then ‘proxytype._method_to_typeid_’ is used instead
          if it exists.)  If a method's name is not a key of this
          mapping or if the mapping is ‘None’ then the object returned
          by the method will be copied by value.

          'create_method' determines whether a method should be created
          with name 'typeid' which can be used to tell the server
          process to create a new shared object and return a proxy for
          it.  By default it is ‘True’.

     *note BaseManager: 2fb4. instances also have one read-only
     property:

      -- 屬性: address

          The address used by the manager.

     在 3.3 版的變更: Manager objects support the context management
     protocol - see *note 情境管理器型別: 1e95.  *note __enter__():
     2124. starts the server process (if it has not already started) and
     then returns the manager object.  *note __exit__(): 2125. calls
     *note shutdown(): 2fb6.

     In previous versions *note __enter__(): 2124. did not start the
     manager's server process if it was not already started.

 -- 類別: multiprocessing.managers.SyncManager

     A subclass of *note BaseManager: 2fb4. which can be used for the
     synchronization of processes.  Objects of this type are returned by
     *note multiprocessing.Manager(): c61.

     Its methods create and return *note Proxy Objects: c60. for a
     number of commonly used data types to be synchronized across
     processes.  This notably includes shared lists and dictionaries.

      -- 方法: Barrier (parties[, action[, timeout]])

          Create a shared *note threading.Barrier: 117b. object and
          return a proxy for it.

          在 3.3 版被加入.

      -- 方法: BoundedSemaphore ([value])

          Create a shared *note threading.BoundedSemaphore: 10f0. object
          and return a proxy for it.

      -- 方法: Condition ([lock])

          Create a shared *note threading.Condition: 10ee. object and
          return a proxy for it.

          If 'lock' is supplied then it should be a proxy for a *note
          threading.Lock: 156d. or *note threading.RLock: 2be. object.

          在 3.3 版的變更: The *note wait_for(): 2f4a. method was added.

      -- 方法: Event ()

          Create a shared *note threading.Event: 10f1. object and return
          a proxy for it.

      -- 方法: Lock ()

          Create a shared *note threading.Lock: 156d. object and return
          a proxy for it.

      -- 方法: Namespace ()

          Create a shared *note Namespace: 2f6d. object and return a
          proxy for it.

      -- 方法: Queue ([maxsize])

          Create a shared *note queue.Queue: 131c. object and return a
          proxy for it.

      -- 方法: RLock ()

          Create a shared *note threading.RLock: 2be. object and return
          a proxy for it.

      -- 方法: Semaphore ([value])

          Create a shared *note threading.Semaphore: 10ef. object and
          return a proxy for it.

      -- 方法: Array (typecode, sequence)

          Create an array and return a proxy for it.

      -- 方法: Value (typecode, value)

          Create an object with a writable ‘value’ attribute and return
          a proxy for it.

      -- 方法: dict ()

      -- 方法: dict (mapping)

      -- 方法: dict (sequence)

          Create a shared *note dict: 23b. object and return a proxy for
          it.

      -- 方法: list ()

      -- 方法: list (sequence)

          Create a shared *note list: 5b6. object and return a proxy for
          it.

     在 3.6 版的變更: Shared objects are capable of being nested.  For
     example, a shared container object such as a shared list can
     contain other shared objects which will all be managed and
     synchronized by the *note SyncManager: 2fb3.

 -- 類別: multiprocessing.managers.Namespace

     A type that can register with *note SyncManager: 2fb3.

     A namespace object has no public methods, but does have writable
     attributes.  Its representation shows the values of its attributes.

     However, when using a proxy for a namespace object, an attribute
     beginning with ‘'_'’ will be an attribute of the proxy and not an
     attribute of the referent:

          >>> mp_context = multiprocessing.get_context('spawn')
          >>> manager = mp_context.Manager()
          >>> Global = manager.Namespace()
          >>> Global.x = 10
          >>> Global.y = 'hello'
          >>> Global._z = 12.3    # this is an attribute of the proxy
          >>> print(Global)
          Namespace(x=10, y='hello')

* Menu:

* Customized managers::
* Using a remote manager::


File: python.info,  Node: Customized managers,  Next: Using a remote manager,  Up: Managers

5.17.2.17 Customized managers
.............................

To create one's own manager, one creates a subclass of *note
BaseManager: 2fb4. and uses the *note register(): 2fba. classmethod to
register new types or callables with the manager class.  For example:

     from multiprocessing.managers import BaseManager

     class MathsClass:
         def add(self, x, y):
             return x + y
         def mul(self, x, y):
             return x * y

     class MyManager(BaseManager):
         pass

     MyManager.register('Maths', MathsClass)

     if __name__ == '__main__':
         with MyManager() as manager:
             maths = manager.Maths()
             print(maths.add(4, 3))         # 印出 7
             print(maths.mul(7, 8))         # 印出 56


File: python.info,  Node: Using a remote manager,  Prev: Customized managers,  Up: Managers

5.17.2.18 Using a remote manager
................................

It is possible to run a manager server on one machine and have clients
use it from other machines (assuming that the firewalls involved allow
it).

Running the following commands creates a server for a single shared
queue which remote clients can access:

     >>> from multiprocessing.managers import BaseManager
     >>> from queue import Queue
     >>> queue = Queue()
     >>> class QueueManager(BaseManager): pass
     >>> QueueManager.register('get_queue', callable=lambda:queue)
     >>> m = QueueManager(address=('', 50000), authkey=b'abracadabra')
     >>> s = m.get_server()
     >>> s.serve_forever()

One client can access the server as follows:

     >>> from multiprocessing.managers import BaseManager
     >>> class QueueManager(BaseManager): pass
     >>> QueueManager.register('get_queue')
     >>> m = QueueManager(address=('foo.bar.org', 50000), authkey=b'abracadabra')
     >>> m.connect()
     >>> queue = m.get_queue()
     >>> queue.put('hello')

Another client can also use it:

     >>> from multiprocessing.managers import BaseManager
     >>> class QueueManager(BaseManager): pass
     >>> QueueManager.register('get_queue')
     >>> m = QueueManager(address=('foo.bar.org', 50000), authkey=b'abracadabra')
     >>> m.connect()
     >>> queue = m.get_queue()
     >>> queue.get()
     'hello'

Local processes can also access that queue, using the code from above on
the client to access it remotely:

     >>> from multiprocessing import Process, Queue
     >>> from multiprocessing.managers import BaseManager
     >>> class Worker(Process):
     ...     def __init__(self, q):
     ...         self.q = q
     ...         super().__init__()
     ...     def run(self):
     ...         self.q.put('local hello')
     ...
     >>> queue = Queue()
     >>> w = Worker(queue)
     >>> w.start()
     >>> class QueueManager(BaseManager): pass
     ...
     >>> QueueManager.register('get_queue', callable=lambda: queue)
     >>> m = QueueManager(address=('', 50000), authkey=b'abracadabra')
     >>> s = m.get_server()
     >>> s.serve_forever()


File: python.info,  Node: Proxy Objects,  Next: Process Pools,  Prev: Managers,  Up: Reference<2>

5.17.2.19 Proxy Objects
.......................

A proxy is an object which 'refers' to a shared object which lives
(presumably) in a different process.  The shared object is said to be
the 'referent' of the proxy.  Multiple proxy objects may have the same
referent.

A proxy object has methods which invoke corresponding methods of its
referent (although not every method of the referent will necessarily be
available through the proxy).  In this way, a proxy can be used just
like its referent can:

     >>> mp_context = multiprocessing.get_context('spawn')
     >>> manager = mp_context.Manager()
     >>> l = manager.list([i*i for i in range(10)])
     >>> print(l)
     [0, 1, 4, 9, 16, 25, 36, 49, 64, 81]
     >>> print(repr(l))
     <ListProxy object, typeid 'list' at 0x...>
     >>> l[4]
     16
     >>> l[2:5]
     [4, 9, 16]

Notice that applying *note str(): 3f2. to a proxy will return the
representation of the referent, whereas applying *note repr(): 7a1. will
return the representation of the proxy.

An important feature of proxy objects is that they are picklable so they
can be passed between processes.  As such, a referent can contain *note
Proxy Objects: c60.  This permits nesting of these managed lists, dicts,
and other *note Proxy Objects: c60.:

     >>> a = manager.list()
     >>> b = manager.list()
     >>> a.append(b)         # referent of a now contains referent of b
     >>> print(a, b)
     [<ListProxy object, typeid 'list' at ...>] []
     >>> b.append('hello')
     >>> print(a[0], b)
     ['hello'] ['hello']

Similarly, dict and list proxies may be nested inside one another:

     >>> l_outer = manager.list([ manager.dict() for i in range(2) ])
     >>> d_first_inner = l_outer[0]
     >>> d_first_inner['a'] = 1
     >>> d_first_inner['b'] = 2
     >>> l_outer[1]['c'] = 3
     >>> l_outer[1]['z'] = 26
     >>> print(l_outer[0])
     {'a': 1, 'b': 2}
     >>> print(l_outer[1])
     {'c': 3, 'z': 26}

If standard (non-proxy) *note list: 5b6. or *note dict: 23b. objects are
contained in a referent, modifications to those mutable values will not
be propagated through the manager because the proxy has no way of
knowing when the values contained within are modified.  However, storing
a value in a container proxy (which triggers a ‘__setitem__’ on the
proxy object) does propagate through the manager and so to effectively
modify such an item, one could re-assign the modified value to the
container proxy:

     # create a list proxy and append a mutable object (a dictionary)
     lproxy = manager.list()
     lproxy.append({})
     # now mutate the dictionary
     d = lproxy[0]
     d['a'] = 1
     d['b'] = 2
     # at this point, the changes to d are not yet synced, but by
     # updating the dictionary, the proxy is notified of the change
     lproxy[0] = d

This approach is perhaps less convenient than employing nested *note
Proxy Objects: c60. for most use cases but also demonstrates a level of
control over the synchronization.

     備註: The proxy types in *note multiprocessing: 86. do nothing to
     support comparisons by value.  So, for instance, we have:

          >>> manager.list([1,2,3]) == [1,2,3]
          False

     One should just use a copy of the referent instead when making
     comparisons.

 -- 類別: multiprocessing.managers.BaseProxy

     Proxy objects are instances of subclasses of *note BaseProxy: 2fbb.

      -- 方法: _callmethod (methodname[, args[, kwds]])

          Call and return the result of a method of the proxy's
          referent.

          If ‘proxy’ is a proxy whose referent is ‘obj’ then the
          expression

               proxy._callmethod(methodname, args, kwds)

          will evaluate the expression

               getattr(obj, methodname)(*args, **kwds)

          in the manager's process.

          The returned value will be a copy of the result of the call or
          a proxy to a new shared object - see documentation for the
          'method_to_typeid' argument of *note BaseManager.register():
          2fba.

          If an exception is raised by the call, then is re-raised by
          *note _callmethod(): 2fbc.  If some other exception is raised
          in the manager's process then this is converted into a
          ‘RemoteError’ exception and is raised by *note _callmethod():
          2fbc.

          Note in particular that an exception will be raised if
          'methodname' has not been 'exposed'.

          An example of the usage of *note _callmethod(): 2fbc.:

               >>> l = manager.list(range(10))
               >>> l._callmethod('__len__')
               10
               >>> l._callmethod('__getitem__', (slice(2, 7),)) # 等價於 l[2:7]
               [2, 3, 4, 5, 6]
               >>> l._callmethod('__getitem__', (20,))          # 等價於 l[20]
               Traceback (most recent call last):
               ...
               IndexError: list index out of range

      -- 方法: _getvalue ()

          Return a copy of the referent.

          If the referent is unpicklable then this will raise an
          exception.

      -- 方法: __repr__ ()

          Return a representation of the proxy object.

      -- 方法: __str__ ()

          Return the representation of the referent.

* Menu:

* Cleanup::


File: python.info,  Node: Cleanup,  Up: Proxy Objects

5.17.2.20 Cleanup
.................

A proxy object uses a weakref callback so that when it gets garbage
collected it deregisters itself from the manager which owns its
referent.

A shared object gets deleted from the manager process when there are no
longer any proxies referring to it.


File: python.info,  Node: Process Pools,  Next: Listeners and Clients,  Prev: Proxy Objects,  Up: Reference<2>

5.17.2.21 Process Pools
.......................

One can create a pool of processes which will carry out tasks submitted
to it with the *note Pool: f0e. class.

 -- 類別: multiprocessing.pool.Pool ([processes[, initializer[,
          initargs[, maxtasksperchild[, context]]]]])

     A process pool object which controls a pool of worker processes to
     which jobs can be submitted.  It supports asynchronous results with
     timeouts and callbacks and has a parallel map implementation.

     'processes' is the number of worker processes to use.  If
     'processes' is ‘None’ then the number returned by *note
     os.process_cpu_count(): 1a7. is used.

     If 'initializer' is not ‘None’ then each worker process will call
     ‘initializer(*initargs)’ when it starts.

     'maxtasksperchild' is the number of tasks a worker process can
     complete before it will exit and be replaced with a fresh worker
     process, to enable unused resources to be freed.  The default
     'maxtasksperchild' is ‘None’, which means worker processes will
     live as long as the pool.

     'context' can be used to specify the context used for starting the
     worker processes.  Usually a pool is created using the function
     ‘multiprocessing.Pool()’ or the *note Pool(): f0e. method of a
     context object.  In both cases 'context' is set appropriately.

     Note that the methods of the pool object should only be called by
     the process which created the pool.

          警告: *note multiprocessing.pool: 8a. objects have internal
          resources that need to be properly managed (like any other
          resource) by using the pool as a context manager or by calling
          *note close(): 2fd1. and *note terminate(): 2fd2. manually.
          Failure to do this can lead to the process hanging on
          finalization.

          Note that it is 'not correct' to rely on the garbage collector
          to destroy the pool as CPython does not assure that the
          finalizer of the pool will be called (see *note
          object.__del__(): 1e36. for more information).

     在 3.2 版的變更: 新增 'maxtasksperchild' 參數。

     在 3.4 版的變更: 新增 'context' 參數。

     在 3.13 版的變更: 'processes' uses *note os.process_cpu_count():
     1a7. by default, instead of *note os.cpu_count(): 1a8.

          備註: Worker processes within a *note Pool: f0e. typically
          live for the complete duration of the Pool's work queue.  A
          frequent pattern found in other systems (such as Apache,
          mod_wsgi, etc) to free resources held by workers is to allow a
          worker within a pool to complete only a set amount of work
          before being exiting, being cleaned up and a new process
          spawned to replace the old one.  The 'maxtasksperchild'
          argument to the *note Pool: f0e. exposes this ability to the
          end user.

      -- 方法: apply (func[, args[, kwds]])

          Call 'func' with arguments 'args' and keyword arguments
          'kwds'.  It blocks until the result is ready.  Given this
          blocks, *note apply_async(): 2fd4. is better suited for
          performing work in parallel.  Additionally, 'func' is only
          executed in one of the workers of the pool.

      -- 方法: apply_async (func[, args[, kwds[, callback[,
               error_callback]]]])

          A variant of the *note apply(): 2fd3. method which returns a
          *note AsyncResult: 2fd5. object.

          If 'callback' is specified then it should be a callable which
          accepts a single argument.  When the result becomes ready
          'callback' is applied to it, that is unless the call failed,
          in which case the 'error_callback' is applied instead.

          If 'error_callback' is specified then it should be a callable
          which accepts a single argument.  If the target function
          fails, then the 'error_callback' is called with the exception
          instance.

          Callbacks should complete immediately since otherwise the
          thread which handles the results will get blocked.

      -- 方法: map (func, iterable[, chunksize])

          A parallel equivalent of the *note map(): 808. built-in
          function (it supports only one 'iterable' argument though, for
          multiple iterables see *note starmap(): 107b.).  It blocks
          until the result is ready.

          This method chops the iterable into a number of chunks which
          it submits to the process pool as separate tasks.  The
          (approximate) size of these chunks can be specified by setting
          'chunksize' to a positive integer.

          Note that it may cause high memory usage for very long
          iterables.  Consider using *note imap(): 2fd6. or *note
          imap_unordered(): 2fd7. with explicit 'chunksize' option for
          better efficiency.

      -- 方法: map_async (func, iterable[, chunksize[, callback[,
               error_callback]]])

          A variant of the *note map(): 107e. method which returns a
          *note AsyncResult: 2fd5. object.

          If 'callback' is specified then it should be a callable which
          accepts a single argument.  When the result becomes ready
          'callback' is applied to it, that is unless the call failed,
          in which case the 'error_callback' is applied instead.

          If 'error_callback' is specified then it should be a callable
          which accepts a single argument.  If the target function
          fails, then the 'error_callback' is called with the exception
          instance.

          Callbacks should complete immediately since otherwise the
          thread which handles the results will get blocked.

      -- 方法: imap (func, iterable[, chunksize])

          A lazier version of *note map(): 107e.

          The 'chunksize' argument is the same as the one used by the
          *note map(): 107e. method.  For very long iterables using a
          large value for 'chunksize' can make the job complete 'much'
          faster than using the default value of ‘1’.

          Also if 'chunksize' is ‘1’ then the ‘next()’ method of the
          iterator returned by the *note imap(): 2fd6. method has an
          optional 'timeout' parameter: ‘next(timeout)’ will raise *note
          multiprocessing.TimeoutError: 2f83. if the result cannot be
          returned within 'timeout' seconds.

      -- 方法: imap_unordered (func, iterable[, chunksize])

          The same as *note imap(): 2fd6. except that the ordering of
          the results from the returned iterator should be considered
          arbitrary.  (Only when there is only one worker process is the
          order guaranteed to be "correct".)

      -- 方法: starmap (func, iterable[, chunksize])

          Like *note map(): 107e. except that the elements of the
          'iterable' are expected to be iterables that are unpacked as
          arguments.

          Hence an 'iterable' of ‘[(1,2), (3, 4)]’ results in
          ‘[func(1,2), func(3,4)]’.

          在 3.3 版被加入.

      -- 方法: starmap_async (func, iterable[, chunksize[, callback[,
               error_callback]]])

          A combination of *note starmap(): 107b. and *note map_async():
          107f. that iterates over 'iterable' of iterables and calls
          'func' with the iterables unpacked.  Returns a result object.

          在 3.3 版被加入.

      -- 方法: close ()

          Prevents any more tasks from being submitted to the pool.
          Once all the tasks have been completed the worker processes
          will exit.

      -- 方法: terminate ()

          Stops the worker processes immediately without completing
          outstanding work.  When the pool object is garbage collected
          *note terminate(): 2fd2. will be called immediately.

      -- 方法: join ()

          Wait for the worker processes to exit.  One must call *note
          close(): 2fd1. or *note terminate(): 2fd2. before using *note
          join(): 2fd8.

     在 3.3 版的變更: Pool objects now support the context management
     protocol - see *note 情境管理器型別: 1e95.  *note __enter__():
     2124. returns the pool object, and *note __exit__(): 2125. calls
     *note terminate(): 2fd2.

 -- 類別: multiprocessing.pool.AsyncResult

     The class of the result returned by *note Pool.apply_async(): 2fd4.
     and *note Pool.map_async(): 107f.

      -- 方法: get ([timeout])

          Return the result when it arrives.  If 'timeout' is not ‘None’
          and the result does not arrive within 'timeout' seconds then
          *note multiprocessing.TimeoutError: 2f83. is raised.  If the
          remote call raised an exception then that exception will be
          reraised by *note get(): 2fd9.

      -- 方法: wait ([timeout])

          Wait until the result is available or until 'timeout' seconds
          pass.

      -- 方法: ready ()

          Return whether the call has completed.

      -- 方法: successful ()

          Return whether the call completed without raising an
          exception.  Will raise *note ValueError: 1e7. if the result is
          not ready.

          在 3.7 版的變更: If the result is not ready, *note ValueError:
          1e7. is raised instead of *note AssertionError: 64e.

The following example demonstrates the use of a pool:

     from multiprocessing import Pool
     import time

     def f(x):
         return x*x

     if __name__ == '__main__':
         with Pool(processes=4) as pool:         # start 4 worker processes
             result = pool.apply_async(f, (10,)) # evaluate "f(10)" asynchronously in a single process
             print(result.get(timeout=1))        # prints "100" unless your computer is *very* slow

             print(pool.map(f, range(10)))       # prints "[0, 1, 4,..., 81]"

             it = pool.imap(f, range(10))
             print(next(it))                     # prints "0"
             print(next(it))                     # prints "1"
             print(it.next(timeout=1))           # prints "4" unless your computer is *very* slow

             result = pool.apply_async(time.sleep, (10,))
             print(result.get(timeout=1))        # raises multiprocessing.TimeoutError


File: python.info,  Node: Listeners and Clients,  Next: Authentication keys,  Prev: Process Pools,  Up: Reference<2>

5.17.2.22 Listeners and Clients
...............................

Usually message passing between processes is done using queues or by
using *note Connection: 15a2. objects returned by *note Pipe(): 2f68.

However, the *note multiprocessing.connection: 87. module allows some
extra flexibility.  It basically gives a high level message oriented API
for dealing with sockets or Windows named pipes.  It also has support
for 'digest authentication' using the *note hmac: 60. module, and for
polling multiple connections at the same time.

 -- 函式: multiprocessing.connection.deliver_challenge (connection,
          authkey)

     Send a randomly generated message to the other end of the
     connection and wait for a reply.

     If the reply matches the digest of the message using 'authkey' as
     the key then a welcome message is sent to the other end of the
     connection.  Otherwise *note AuthenticationError: 2f82. is raised.

 -- 函式: multiprocessing.connection.answer_challenge (connection,
          authkey)

     Receive a message, calculate the digest of the message using
     'authkey' as the key, and then send the digest back.

     If a welcome message is not received, then *note
     AuthenticationError: 2f82. is raised.

 -- 函式: multiprocessing.connection.Client (address[, family[,
          authkey]])

     Attempt to set up a connection to the listener which is using
     address 'address', returning a *note Connection: 15a2.

     The type of the connection is determined by 'family' argument, but
     this can generally be omitted since it can usually be inferred from
     the format of 'address'.  (See *note Address Formats: 2fe1.)

     If 'authkey' is given and not ‘None’, it should be a byte string
     and will be used as the secret key for an HMAC-based authentication
     challenge.  No authentication is done if 'authkey' is ‘None’.
     *note AuthenticationError: 2f82. is raised if authentication fails.
     See *note Authentication keys: 2f7e.

 -- 類別: multiprocessing.connection.Listener ([address[, family[,
          backlog[, authkey]]]])

     A wrapper for a bound socket or Windows named pipe which is
     'listening' for connections.

     'address' is the address to be used by the bound socket or named
     pipe of the listener object.

          備註: If an address of '0.0.0.0' is used, the address will not
          be a connectable end point on Windows.  If you require a
          connectable end-point, you should use '127.0.0.1'.

     'family' is the type of socket (or named pipe) to use.  This can be
     one of the strings ‘'AF_INET'’ (for a TCP socket), ‘'AF_UNIX'’ (for
     a Unix domain socket) or ‘'AF_PIPE'’ (for a Windows named pipe).
     Of these only the first is guaranteed to be available.  If 'family'
     is ‘None’ then the family is inferred from the format of 'address'.
     If 'address' is also ‘None’ then a default is chosen.  This default
     is the family which is assumed to be the fastest available.  See
     *note Address Formats: 2fe1.  Note that if 'family' is ‘'AF_UNIX'’
     and address is ‘None’ then the socket will be created in a private
     temporary directory created using *note tempfile.mkstemp(): 2730.

     If the listener object uses a socket then 'backlog' (1 by default)
     is passed to the *note listen(): e00. method of the socket once it
     has been bound.

     If 'authkey' is given and not ‘None’, it should be a byte string
     and will be used as the secret key for an HMAC-based authentication
     challenge.  No authentication is done if 'authkey' is ‘None’.
     *note AuthenticationError: 2f82. is raised if authentication fails.
     See *note Authentication keys: 2f7e.

      -- 方法: accept ()

          Accept a connection on the bound socket or named pipe of the
          listener object and return a *note Connection: 15a2. object.
          If authentication is attempted and fails, then *note
          AuthenticationError: 2f82. is raised.

      -- 方法: close ()

          Close the bound socket or named pipe of the listener object.
          This is called automatically when the listener is garbage
          collected.  However it is advisable to call it explicitly.

     Listener objects have the following read-only properties:

      -- 屬性: address

          The address which is being used by the Listener object.

      -- 屬性: last_accepted

          The address from which the last accepted connection came.  If
          this is unavailable then it is ‘None’.

     在 3.3 版的變更: Listener objects now support the context
     management protocol - see *note 情境管理器型別: 1e95.  *note
     __enter__(): 2124. returns the listener object, and *note
     __exit__(): 2125. calls *note close(): 2fe2.

 -- 函式: multiprocessing.connection.wait (object_list, timeout=None)

     Wait till an object in 'object_list' is ready.  Returns the list of
     those objects in 'object_list' which are ready.  If 'timeout' is a
     float then the call blocks for at most that many seconds.  If
     'timeout' is ‘None’ then it will block for an unlimited period.  A
     negative timeout is equivalent to a zero timeout.

     For both POSIX and Windows, an object can appear in 'object_list'
     if it is

        * a readable *note Connection: 15a2. object;

        * a connected and readable *note socket.socket: d47. object; or

        * the *note sentinel: 107a. attribute of a *note Process: afd.
          object.

     A connection or socket object is ready when there is data available
     to be read from it, or the other end has been closed.

     'POSIX': ‘wait(object_list, timeout)’ almost equivalent
     ‘select.select(object_list, [], [], timeout)’.  The difference is
     that, if *note select.select(): d46. is interrupted by a signal, it
     can raise *note OSError: 350. with an error number of ‘EINTR’,
     whereas *note wait(): 1079. will not.

     'Windows': An item in 'object_list' must either be an integer
     handle which is waitable (according to the definition used by the
     documentation of the Win32 function ‘WaitForMultipleObjects()’) or
     it can be an object with a *note fileno(): 2732. method which
     returns a socket handle or pipe handle.  (Note that pipe handles
     and socket handles are 'not' waitable handles.)

     在 3.3 版被加入.

'Examples'

The following server code creates a listener which uses ‘'secret
password'’ as an authentication key.  It then waits for a connection and
sends some data to the client:

     from multiprocessing.connection import Listener
     from array import array

     address = ('localhost', 6000)     # family is deduced to be 'AF_INET'

     with Listener(address, authkey=b'secret password') as listener:
         with listener.accept() as conn:
             print('connection accepted from', listener.last_accepted)

             conn.send([2.25, None, 'junk', float])

             conn.send_bytes(b'hello')

             conn.send_bytes(array('i', [42, 1729]))

The following code connects to the server and receives some data from
the server:

     from multiprocessing.connection import Client
     from array import array

     address = ('localhost', 6000)

     with Client(address, authkey=b'secret password') as conn:
         print(conn.recv())                  # => [2.25, None, 'junk', float]

         print(conn.recv_bytes())            # => 'hello'

         arr = array('i', [0, 0, 0, 0, 0])
         print(conn.recv_bytes_into(arr))    # => 8
         print(arr)                          # => array('i', [42, 1729, 0, 0, 0])

The following code uses *note wait(): 1079. to wait for messages from
multiple processes at once:

     from multiprocessing import Process, Pipe, current_process
     from multiprocessing.connection import wait

     def foo(w):
         for i in range(10):
             w.send((i, current_process().name))
         w.close()

     if __name__ == '__main__':
         readers = []

         for i in range(4):
             r, w = Pipe(duplex=False)
             readers.append(r)
             p = Process(target=foo, args=(w,))
             p.start()
             # We close the writable end of the pipe now to be sure that
             # p is the only process which owns a handle for it.  This
             # ensures that when p closes its handle for the writable end,
             # wait() will promptly report the readable end as being ready.
             w.close()

         while readers:
             for r in wait(readers):
                 try:
                     msg = r.recv()
                 except EOFError:
                     readers.remove(r)
                 else:
                     print(msg)

* Menu:

* Address Formats::


File: python.info,  Node: Address Formats,  Up: Listeners and Clients

5.17.2.23 Address Formats
.........................

   * An ‘'AF_INET'’ address is a tuple of the form ‘(hostname, port)’
     where 'hostname' is a string and 'port' is an integer.

   * An ‘'AF_UNIX'’ address is a string representing a filename on the
     filesystem.

   * An ‘'AF_PIPE'’ address is a string of the form
     ‘r'\\.\pipe\PIPENAME'’.  To use *note Client(): 2fe0. to connect to
     a named pipe on a remote computer called 'ServerName' one should
     use an address of the form ‘r'\\SERVERNAME\pipe\PIPENAME'’ instead.

Note that any string beginning with two backslashes is assumed by
default to be an ‘'AF_PIPE'’ address rather than an ‘'AF_UNIX'’ address.


File: python.info,  Node: Authentication keys,  Next: Logging,  Prev: Listeners and Clients,  Up: Reference<2>

5.17.2.24 Authentication keys
.............................

When one uses *note Connection.recv: 2f9e, the data received is
automatically unpickled.  Unfortunately unpickling data from an
untrusted source is a security risk.  Therefore *note Listener: 15a1.
and *note Client(): 2fe0. use the *note hmac: 60. module to provide
digest authentication.

An authentication key is a byte string which can be thought of as a
password: once a connection is established both ends will demand proof
that the other knows the authentication key.  (Demonstrating that both
ends are using the same key does 'not' involve sending the key over the
connection.)

If authentication is requested but no authentication key is specified
then the return value of ‘current_process().authkey’ is used (see *note
Process: afd.).  This value will be automatically inherited by any *note
Process: afd. object that the current process creates.  This means that
(by default) all processes of a multi-process program will share a
single authentication key which can be used when setting up connections
between themselves.

Suitable authentication keys can also be generated by using *note
os.urandom(): 4c7.


File: python.info,  Node: Logging,  Next: multiprocessing dummy 模組,  Prev: Authentication keys,  Up: Reference<2>

5.17.2.25 Logging
.................

Some support for logging is available.  Note, however, that the *note
logging: 7b. package does not use process shared locks so it is possible
(depending on the handler type) for messages from different processes to
get mixed up.

 -- 函式: multiprocessing.get_logger ()

     Returns the logger used by *note multiprocessing: 86.  If
     necessary, a new one will be created.

     When first created the logger has level *note logging.NOTSET: 2bb0.
     and no default handler.  Messages sent to this logger will not by
     default propagate to the root logger.

     Note that on Windows child processes will only inherit the level of
     the parent process's logger - any other customization of the logger
     will not be inherited.

 -- 函式: multiprocessing.log_to_stderr (level=None)

     This function performs a call to *note get_logger(): 2fe8. but in
     addition to returning the logger created by get_logger, it adds a
     handler which sends output to *note sys.stderr: 8dd. using format
     ‘'[%(levelname)s/%(processName)s] %(message)s'’.  You can modify
     ‘levelname’ of the logger by passing a ‘level’ argument.

Below is an example session with logging turned on:

     >>> import multiprocessing, logging
     >>> logger = multiprocessing.log_to_stderr()
     >>> logger.setLevel(logging.INFO)
     >>> logger.warning('doomed')
     [WARNING/MainProcess] doomed
     >>> m = multiprocessing.Manager()
     [INFO/SyncManager-...] child process calling self.run()
     [INFO/SyncManager-...] created temp directory /.../pymp-...
     [INFO/SyncManager-...] manager serving at '/.../listener-...'
     >>> del m
     [INFO/MainProcess] sending shutdown message to manager
     [INFO/SyncManager-...] manager exiting with exitcode 0

For a full table of logging levels, see the *note logging: 7b. module.


File: python.info,  Node: multiprocessing dummy 模組,  Prev: Logging,  Up: Reference<2>

5.17.2.26 ‘multiprocessing.dummy’ 模組
......................................

*note multiprocessing.dummy: 88. replicates the API of *note
multiprocessing: 86. but is no more than a wrapper around the *note
threading: d6. module.

In particular, the ‘Pool’ function provided by *note
multiprocessing.dummy: 88. returns an instance of *note ThreadPool:
1813, which is a subclass of *note Pool: f0e. that supports all the same
method calls but uses a pool of worker threads rather than worker
processes.

 -- 類別: multiprocessing.pool.ThreadPool ([processes[, initializer[,
          initargs]]])

     A thread pool object which controls a pool of worker threads to
     which jobs can be submitted.  *note ThreadPool: 1813. instances are
     fully interface compatible with *note Pool: f0e. instances, and
     their resources must also be properly managed, either by using the
     pool as a context manager or by calling *note close(): 2fd1. and
     *note terminate(): 2fd2. manually.

     'processes' is the number of worker threads to use.  If 'processes'
     is ‘None’ then the number returned by *note os.process_cpu_count():
     1a7. is used.

     If 'initializer' is not ‘None’ then each worker process will call
     ‘initializer(*initargs)’ when it starts.

     Unlike *note Pool: f0e, 'maxtasksperchild' and 'context' cannot be
     provided.

          備註: A *note ThreadPool: 1813. shares the same interface as
          *note Pool: f0e, which is designed around a pool of processes
          and predates the introduction of the *note concurrent.futures:
          1a. module.  As such, it inherits some operations that don't
          make sense for a pool backed by threads, and it has its own
          type for representing the status of asynchronous jobs, *note
          AsyncResult: 2fd5, that is not understood by any other
          libraries.

          Users should generally prefer to use *note
          concurrent.futures.ThreadPoolExecutor: 6e6, which has a
          simpler interface that was designed around threads from the
          start, and which returns *note concurrent.futures.Future:
          1149. instances that are compatible with many other libraries,
          including *note asyncio: 8.


File: python.info,  Node: Programming guidelines,  Next: 範例<19>,  Prev: Reference<2>,  Up: multiprocessing --- 以行程為基礎的平行性

5.17.2.27 Programming guidelines
................................

There are certain guidelines and idioms which should be adhered to when
using *note multiprocessing: 86.

* Menu:

* All start methods::
* The spawn and forkserver start methods::


File: python.info,  Node: All start methods,  Next: The spawn and forkserver start methods,  Up: Programming guidelines

5.17.2.28 All start methods
...........................

The following applies to all start methods.

Avoid shared state

     As far as possible one should try to avoid shifting large amounts
     of data between processes.

     It is probably best to stick to using queues or pipes for
     communication between processes rather than using the lower level
     synchronization primitives.

Picklability

     Ensure that the arguments to the methods of proxies are picklable.

Thread safety of proxies

     Do not use a proxy object from more than one thread unless you
     protect it with a lock.

     (There is never a problem with different processes using the 'same'
     proxy.)

Joining zombie processes

     On POSIX when a process finishes but has not been joined it becomes
     a zombie.  There should never be very many because each time a new
     process starts (or *note active_children(): 2f97. is called) all
     completed processes which have not yet been joined will be joined.
     Also calling a finished process's *note Process.is_alive: 2f7b.
     will join the process.  Even so it is probably good practice to
     explicitly join all the processes that you start.

Better to inherit than pickle/unpickle

     When using the 'spawn' or 'forkserver' start methods many types
     from *note multiprocessing: 86. need to be picklable so that child
     processes can use them.  However, one should generally avoid
     sending shared objects to other processes using pipes or queues.
     Instead you should arrange the program so that a process which
     needs access to a shared resource created elsewhere can inherit it
     from an ancestor process.

Avoid terminating processes

     Using the *note Process.terminate: 2f7f. method to stop a process
     is liable to cause any shared resources (such as locks, semaphores,
     pipes and queues) currently being used by the process to become
     broken or unavailable to other processes.

     Therefore it is probably best to only consider using *note
     Process.terminate: 2f7f. on processes which never use any shared
     resources.

Joining processes that use queues

     Bear in mind that a process that has put items in a queue will wait
     before terminating until all the buffered items are fed by the
     "feeder" thread to the underlying pipe.  (The child process can
     call the *note Queue.cancel_join_thread: 2f8d. method of the queue
     to avoid this behaviour.)

     This means that whenever you use a queue you need to make sure that
     all items which have been put on the queue will eventually be
     removed before the process is joined.  Otherwise you cannot be sure
     that processes which have put items on the queue will terminate.
     Remember also that non-daemonic processes will be joined
     automatically.

     An example which will deadlock is the following:

          from multiprocessing import Process, Queue

          def f(q):
              q.put('X' * 1000000)

          if __name__ == '__main__':
              queue = Queue()
              p = Process(target=f, args=(queue,))
              p.start()
              p.join()                    # this deadlocks
              obj = queue.get()

     A fix here would be to swap the last two lines (or simply remove
     the ‘p.join()’ line).

Explicitly pass resources to child processes

     On POSIX using the 'fork' start method, a child process can make
     use of a shared resource created in a parent process using a global
     resource.  However, it is better to pass the object as an argument
     to the constructor for the child process.

     Apart from making the code (potentially) compatible with Windows
     and the other start methods this also ensures that as long as the
     child process is still alive the object will not be garbage
     collected in the parent process.  This might be important if some
     resource is freed when the object is garbage collected in the
     parent process.

     So for instance

          from multiprocessing import Process, Lock

          def f():
              ... do something using "lock" ...

          if __name__ == '__main__':
              lock = Lock()
              for i in range(10):
                  Process(target=f).start()

     should be rewritten as

          from multiprocessing import Process, Lock

          def f(l):
              ... do something using "l" ...

          if __name__ == '__main__':
              lock = Lock()
              for i in range(10):
                  Process(target=f, args=(lock,)).start()

Beware of replacing *note sys.stdin: 4e2. with a "file like object"

     *note multiprocessing: 86. originally unconditionally called:

          os.close(sys.stdin.fileno())

     in the ‘multiprocessing.Process._bootstrap()’ method -- this
     resulted in issues with processes-in-processes.  This has been
     changed to:

          sys.stdin.close()
          sys.stdin = open(os.open(os.devnull, os.O_RDONLY), closefd=False)

     Which solves the fundamental issue of processes colliding with each
     other resulting in a bad file descriptor error, but introduces a
     potential danger to applications which replace *note sys.stdin():
     4e2. with a "file-like object" with output buffering.  This danger
     is that if multiple processes call *note close(): 1db. on this
     file-like object, it could result in the same data being flushed to
     the object multiple times, resulting in corruption.

     If you write a file-like object and implement your own caching, you
     can make it fork-safe by storing the pid whenever you append to the
     cache, and discarding the cache when the pid changes.  For example:

          @property
          def cache(self):
              pid = os.getpid()
              if pid != self._pid:
                  self._pid = pid
                  self._cache = []
              return self._cache

     For more information, see bpo-5155(1), bpo-5313(2) and bpo-5331(3)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=5155

   (2) https://bugs.python.org/issue?@action=redirect&bpo=5313

   (3) https://bugs.python.org/issue?@action=redirect&bpo=5331


File: python.info,  Node: The spawn and forkserver start methods,  Prev: All start methods,  Up: Programming guidelines

5.17.2.29 The 'spawn' and 'forkserver' start methods
....................................................

There are a few extra restrictions which don't apply to the 'fork' start
method.

More picklability

     Ensure that all arguments to ‘Process.__init__()’ are picklable.
     Also, if you subclass *note Process: afd. then make sure that
     instances will be picklable when the *note Process.start: 2f63.
     method is called.

Global variables

     Bear in mind that if code run in a child process tries to access a
     global variable, then the value it sees (if any) may not be the
     same as the value in the parent process at the time that *note
     Process.start: 2f63. was called.

     However, global variables which are just module level constants
     cause no problems.
Safe importing of main module

     Make sure that the main module can be safely imported by a new
     Python interpreter without causing unintended side effects (such as
     starting a new process).

     For example, using the 'spawn' or 'forkserver' start method running
     the following module would fail with a *note RuntimeError: 179.:

          from multiprocessing import Process

          def foo():
              print('hello')

          p = Process(target=foo)
          p.start()

     Instead one should protect the "entry point" of the program by
     using ‘if __name__ == '__main__':’ as follows:

          from multiprocessing import Process, freeze_support, set_start_method

          def foo():
              print('hello')

          if __name__ == '__main__':
              freeze_support()
              set_start_method('spawn')
              p = Process(target=foo)
              p.start()

     (The ‘freeze_support()’ line can be omitted if the program will be
     run normally instead of frozen.)

     This allows the newly spawned Python interpreter to safely import
     the module and then run the module's ‘foo()’ function.

     Similar restrictions apply if a pool or manager is created in the
     main module.


File: python.info,  Node: 範例<19>,  Prev: Programming guidelines,  Up: multiprocessing --- 以行程為基礎的平行性

5.17.2.30 範例
..............

Demonstration of how to create and use customized managers and proxies:

     from multiprocessing import freeze_support
     from multiprocessing.managers import BaseManager, BaseProxy
     import operator

     ##

     class Foo:
         def f(self):
             print('you called Foo.f()')
         def g(self):
             print('you called Foo.g()')
         def _h(self):
             print('you called Foo._h()')

     # A simple generator function
     def baz():
         for i in range(10):
             yield i*i

     # Proxy type for generator objects
     class GeneratorProxy(BaseProxy):
         _exposed_ = ['__next__']
         def __iter__(self):
             return self
         def __next__(self):
             return self._callmethod('__next__')

     # Function to return the operator module
     def get_operator_module():
         return operator

     ##

     class MyManager(BaseManager):
         pass

     # register the Foo class; make `f()` and `g()` accessible via proxy
     MyManager.register('Foo1', Foo)

     # register the Foo class; make `g()` and `_h()` accessible via proxy
     MyManager.register('Foo2', Foo, exposed=('g', '_h'))

     # register the generator function baz; use `GeneratorProxy` to make proxies
     MyManager.register('baz', baz, proxytype=GeneratorProxy)

     # register get_operator_module(); make public functions accessible via proxy
     MyManager.register('operator', get_operator_module)

     ##

     def test():
         manager = MyManager()
         manager.start()

         print('-' * 20)

         f1 = manager.Foo1()
         f1.f()
         f1.g()
         assert not hasattr(f1, '_h')
         assert sorted(f1._exposed_) == sorted(['f', 'g'])

         print('-' * 20)

         f2 = manager.Foo2()
         f2.g()
         f2._h()
         assert not hasattr(f2, 'f')
         assert sorted(f2._exposed_) == sorted(['g', '_h'])

         print('-' * 20)

         it = manager.baz()
         for i in it:
             print('<%d>' % i, end=' ')
         print()

         print('-' * 20)

         op = manager.operator()
         print('op.add(23, 45) =', op.add(23, 45))
         print('op.pow(2, 94) =', op.pow(2, 94))
         print('op._exposed_ =', op._exposed_)

     ##

     if __name__ == '__main__':
         freeze_support()
         test()

使用 *note Pool: f0e.：

     import multiprocessing
     import time
     import random
     import sys

     #
     # Functions used by test code
     #

     def calculate(func, args):
         result = func(*args)
         return '%s says that %s%s = %s' % (
             multiprocessing.current_process().name,
             func.__name__, args, result
             )

     def calculatestar(args):
         return calculate(*args)

     def mul(a, b):
         time.sleep(0.5 * random.random())
         return a * b

     def plus(a, b):
         time.sleep(0.5 * random.random())
         return a + b

     def f(x):
         return 1.0 / (x - 5.0)

     def pow3(x):
         return x ** 3

     def noop(x):
         pass

     #
     # Test code
     #

     def test():
         PROCESSES = 4
         print('Creating pool with %d processes\n' % PROCESSES)

         with multiprocessing.Pool(PROCESSES) as pool:
             #
             # Tests
             #

             TASKS = [(mul, (i, 7)) for i in range(10)] + \
                     [(plus, (i, 8)) for i in range(10)]

             results = [pool.apply_async(calculate, t) for t in TASKS]
             imap_it = pool.imap(calculatestar, TASKS)
             imap_unordered_it = pool.imap_unordered(calculatestar, TASKS)

             print('Ordered results using pool.apply_async():')
             for r in results:
                 print('\t', r.get())
             print()

             print('Ordered results using pool.imap():')
             for x in imap_it:
                 print('\t', x)
             print()

             print('Unordered results using pool.imap_unordered():')
             for x in imap_unordered_it:
                 print('\t', x)
             print()

             print('Ordered results using pool.map() --- will block till complete:')
             for x in pool.map(calculatestar, TASKS):
                 print('\t', x)
             print()

             #
             # Test error handling
             #

             print('Testing error handling:')

             try:
                 print(pool.apply(f, (5,)))
             except ZeroDivisionError:
                 print('\tGot ZeroDivisionError as expected from pool.apply()')
             else:
                 raise AssertionError('expected ZeroDivisionError')

             try:
                 print(pool.map(f, list(range(10))))
             except ZeroDivisionError:
                 print('\tGot ZeroDivisionError as expected from pool.map()')
             else:
                 raise AssertionError('expected ZeroDivisionError')

             try:
                 print(list(pool.imap(f, list(range(10)))))
             except ZeroDivisionError:
                 print('\tGot ZeroDivisionError as expected from list(pool.imap())')
             else:
                 raise AssertionError('expected ZeroDivisionError')

             it = pool.imap(f, list(range(10)))
             for i in range(10):
                 try:
                     x = next(it)
                 except ZeroDivisionError:
                     if i == 5:
                         pass
                 except StopIteration:
                     break
                 else:
                     if i == 5:
                         raise AssertionError('expected ZeroDivisionError')

             assert i == 9
             print('\tGot ZeroDivisionError as expected from IMapIterator.next()')
             print()

             #
             # Testing timeouts
             #

             print('Testing ApplyResult.get() with timeout:', end=' ')
             res = pool.apply_async(calculate, TASKS[0])
             while 1:
                 sys.stdout.flush()
                 try:
                     sys.stdout.write('\n\t%s' % res.get(0.02))
                     break
                 except multiprocessing.TimeoutError:
                     sys.stdout.write('.')
             print()
             print()

             print('Testing IMapIterator.next() with timeout:', end=' ')
             it = pool.imap(calculatestar, TASKS)
             while 1:
                 sys.stdout.flush()
                 try:
                     sys.stdout.write('\n\t%s' % it.next(0.02))
                 except StopIteration:
                     break
                 except multiprocessing.TimeoutError:
                     sys.stdout.write('.')
             print()
             print()


     if __name__ == '__main__':
         multiprocessing.freeze_support()
         test()

An example showing how to use queues to feed tasks to a collection of
worker processes and collect the results:

     import time
     import random

     from multiprocessing import Process, Queue, current_process, freeze_support

     #
     # Function run by worker processes
     #

     def worker(input, output):
         for func, args in iter(input.get, 'STOP'):
             result = calculate(func, args)
             output.put(result)

     #
     # Function used to calculate result
     #

     def calculate(func, args):
         result = func(*args)
         return '%s says that %s%s = %s' % \
             (current_process().name, func.__name__, args, result)

     #
     # Functions referenced by tasks
     #

     def mul(a, b):
         time.sleep(0.5*random.random())
         return a * b

     def plus(a, b):
         time.sleep(0.5*random.random())
         return a + b

     #
     #
     #

     def test():
         NUMBER_OF_PROCESSES = 4
         TASKS1 = [(mul, (i, 7)) for i in range(20)]
         TASKS2 = [(plus, (i, 8)) for i in range(10)]

         # Create queues
         task_queue = Queue()
         done_queue = Queue()

         # Submit tasks
         for task in TASKS1:
             task_queue.put(task)

         # Start worker processes
         for i in range(NUMBER_OF_PROCESSES):
             Process(target=worker, args=(task_queue, done_queue)).start()

         # Get and print results
         print('Unordered results:')
         for i in range(len(TASKS1)):
             print('\t', done_queue.get())

         # Add more tasks using `put()`
         for task in TASKS2:
             task_queue.put(task)

         # Get and print some more results
         for i in range(len(TASKS2)):
             print('\t', done_queue.get())

         # Tell child processes to stop
         for i in range(NUMBER_OF_PROCESSES):
             task_queue.put('STOP')


     if __name__ == '__main__':
         freeze_support()
         test()


File: python.info,  Node: multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取,  Next: concurrent 套件,  Prev: multiprocessing --- 以行程為基礎的平行性,  Up: 並行執行 Concurrent Execution

5.17.3 ‘multiprocessing.shared_memory’ -- 對於共享記憶體的跨行程直接存取
------------------------------------------------------------------------

'原始碼：'Lib/multiprocessing/shared_memory.py(1)

在 3.8 版被加入.

__________________________________________________________________

該模組提供了一個 *note SharedMemory: 154f. 類別，用於分配和管理被多核心
或對稱多處理器 (symmetric multiprocessor, SMP) 機器上的一個或多個行程存
取的共享記憶體。為了協助共享記憶體的生命週期管理，特別是跨不同行程的管理
，*note multiprocessing.managers: 89. 模組中還提供了一個 *note
BaseManager: 2fb4. 子類別 *note SharedMemoryManager: 2ff2.。

在此模組中，共享記憶體是指「POSIX 風格」的共享記憶體區塊（儘管不一定如此
明確實作），而不是指「分散式共享記憶體 (distributed shared memory)」。這
種型別的共享記憶體允許不同的行程潛在地讀取和寫入揮發性記憶體 (volatile
memory) 的公開（或共享）區域。通常行程只能存取自己的行程記憶體空間，但共
享記憶體允許在行程之間共享資料，從而避免需要跨行程傳遞資料的情境。與透過
硬碟或 socket 或其他需要序列化/還原序列化
(serialization/deserialization) 和複製資料的通訊方式以共享資料相比，直接
透過記憶體共享資料可以提供顯著的性能優勢。

 -- 類別: multiprocessing.shared_memory.SharedMemory (name=None,
          create=False, size=0, *, track=True)

     建立 ‘SharedMemory’ 類別的實例，用於建立新的共享記憶體區塊或附加到
     現有的共享記憶體區塊。每個共享記憶體區塊都被分配了一個唯一的名稱。
     透過這種方式，一個行程可以建立具有特定名稱的共享記憶體區塊，而不同
     的行程可以使用該相同名稱附加到同一共享記憶體塊。

     作為跨行程共享資料的資源，共享記憶體區塊的壽命可能比建立它們的原始
     行程還要長。當一個行程不再需要存取但其他行程可能仍需要的共享記憶體
     區塊時，應該呼叫 *note close(): 2ff3. 方法。當任何行程不再需要共享
     記憶體區塊時，應呼叫 *note unlink(): 2ff4. 方法以確保正確清理。


     參數:

        * ‘name’ (*note str: 3f2.‘ | ’‘None’) - 所請求的共享記憶體的唯一
          名稱，指定為字串。建立新的共享記憶體區塊時，如果名稱提供為
          ‘None’（預設值），則會生成一個新的名稱。

        * ‘create’ (*note bool: 40e.) - 控制是否建立新的共享記憶體區塊
          (‘True’) 或附加現有的共享記憶體區塊 (‘False’)。

        * ‘size’ (*note int: 23c.) - 指定建立新共享記憶體區塊時請求的位
          元組數。由於某些平台會根據該平台的記憶體頁 (memory page) 大小
          來選擇分配記憶體區塊，因此共享記憶體區塊的確切大小可能大於或等
          於請求的大小。當附加到現有共享記憶體區塊時，‘size’ 參數將被忽
          略。

        * ‘track’ (*note bool: 40e.) - When ‘True’, register the shared
          memory block with a resource tracker process on platforms
          where the OS does not do this automatically.  The resource
          tracker ensures proper cleanup of the shared memory even if
          all other processes with access to the memory exit without
          doing so.  Python processes created from a common ancestor
          using *note multiprocessing: 86. facilities share a single
          resource tracker process, and the lifetime of shared memory
          segments is handled automatically among these processes.
          Python processes created in any other way will receive their
          own resource tracker when accessing shared memory with 'track'
          enabled.  This will cause the shared memory to be deleted by
          the resource tracker of the first process that terminates.  To
          avoid this issue, users of *note subprocess: c1. or standalone
          Python processes should set 'track' to ‘False’ when there is
          already another process in place that does the bookkeeping.
          'track' is ignored on Windows, which has its own tracking and
          automatically deletes shared memory when all handles to it
          have been closed.

     在 3.13 版的變更: Added the 'track' parameter.

      -- 方法: close ()

          Close the file descriptor/handle to the shared memory from
          this instance.  *note close(): 2ff3. should be called once
          access to the shared memory block from this instance is no
          longer needed.  Depending on operating system, the underlying
          memory may or may not be freed even if all handles to it have
          been closed.  To ensure proper cleanup, use the *note
          unlink(): 2ff4. method.

      -- 方法: unlink ()

          Delete the underlying shared memory block.  This should be
          called only once per shared memory block regardless of the
          number of handles to it, even in other processes.  *note
          unlink(): 2ff4. and *note close(): 2ff3. can be called in any
          order, but trying to access data inside a shared memory block
          after *note unlink(): 2ff4. may result in memory access
          errors, depending on platform.

          This method has no effect on Windows, where the only way to
          delete a shared memory block is to close all handles.

      -- 屬性: buf

          共享記憶體區塊內容的記憶體視圖 (memoryview)。

      -- 屬性: name

          對共享記憶體區塊之唯一名稱的唯讀存取。

      -- 屬性: size

          對共享記憶體區塊大小（以位元組為單位）的唯讀存取。

以下範例示範了 *note SharedMemory: 154f. 實例的低階使用方式：

     >>> from multiprocessing import shared_memory
     >>> shm_a = shared_memory.SharedMemory(create=True, size=10)
     >>> type(shm_a.buf)
     <class 'memoryview'>
     >>> buffer = shm_a.buf
     >>> len(buffer)
     10
     >>> buffer[:4] = bytearray([22, 33, 44, 55])  # Modify multiple at once
     >>> buffer[4] = 100                           # Modify single byte at a time
     >>> # Attach to an existing shared memory block
     >>> shm_b = shared_memory.SharedMemory(shm_a.name)
     >>> import array
     >>> array.array('b', shm_b.buf[:5])  # Copy the data into a new array.array
     array('b', [22, 33, 44, 55, 100])
     >>> shm_b.buf[:5] = b'howdy'  # Modify via shm_b using bytes
     >>> bytes(shm_a.buf[:5])      # Access via shm_a
     b'howdy'
     >>> shm_b.close()   # Close each SharedMemory instance
     >>> shm_a.close()
     >>> shm_a.unlink()  # Call unlink only once to release the shared memory

以下範例示範了 *note SharedMemory: 154f. 類別與 NumPy 陣列(2)的實際用法
：從兩個不同的 Python shell 存取相同的 ‘numpy.ndarray’：

     >>> # In the first Python interactive shell
     >>> import numpy as np
     >>> a = np.array([1, 1, 2, 3, 5, 8])  # Start with an existing NumPy array
     >>> from multiprocessing import shared_memory
     >>> shm = shared_memory.SharedMemory(create=True, size=a.nbytes)
     >>> # Now create a NumPy array backed by shared memory
     >>> b = np.ndarray(a.shape, dtype=a.dtype, buffer=shm.buf)
     >>> b[:] = a[:]  # Copy the original data into shared memory
     >>> b
     array([1, 1, 2, 3, 5, 8])
     >>> type(b)
     <class 'numpy.ndarray'>
     >>> type(a)
     <class 'numpy.ndarray'>
     >>> shm.name  # We did not specify a name so one was chosen for us
     'psm_21467_46075'

     >>> # In either the same shell or a new Python shell on the same machine
     >>> import numpy as np
     >>> from multiprocessing import shared_memory
     >>> # Attach to the existing shared memory block
     >>> existing_shm = shared_memory.SharedMemory(name='psm_21467_46075')
     >>> # Note that a.shape is (6,) and a.dtype is np.int64 in this example
     >>> c = np.ndarray((6,), dtype=np.int64, buffer=existing_shm.buf)
     >>> c
     array([1, 1, 2, 3, 5, 8])
     >>> c[-1] = 888
     >>> c
     array([  1,   1,   2,   3,   5, 888])

     >>> # Back in the first Python interactive shell, b reflects this change
     >>> b
     array([  1,   1,   2,   3,   5, 888])

     >>> # Clean up from within the second Python shell
     >>> del c  # Unnecessary; merely emphasizing the array is no longer used
     >>> existing_shm.close()

     >>> # Clean up from within the first Python shell
     >>> del b  # Unnecessary; merely emphasizing the array is no longer used
     >>> shm.close()
     >>> shm.unlink()  # Free and release the shared memory block at the very end

 -- 類別: multiprocessing.managers.SharedMemoryManager ([address[,
          authkey]])

     *note multiprocessing.managers.BaseManager: 2fb4. 的子類別，可用於
     跨行程管理共享記憶體區塊。

     在 ‘SharedMemoryManager’ 實例上呼叫 *note start(): 2fb5. 會啟動一個
     新行程。這個新行程的唯一目的是管理那些透過它建立出的所有共享記憶體
     區塊的生命週期。要觸發釋放該行程管理的所有共享記憶體區塊，請在實例
     上呼叫 *note shutdown(): 2fb6.，這會觸發對該行程管理的所有 *note
     SharedMemory: 2ff8. 物件的 *note unlink(): 2ff4. 呼叫，然後再停止這
     個行程。透過 ‘SharedMemoryManager’ 建立 ‘SharedMemory’ 實例，我們無
     需手動追蹤和觸發共享記憶體資源的釋放。

     此類別提供了用於建立和回傳 *note SharedMemory: 2ff8. 實例以及建立由
     共享記憶體支援的類串列物件 (*note ShareableList: 2ff9.) 的方法。

     請參閱 *note BaseManager: 2fb4. 了解繼承的 'address' 和 'authkey' 可
     選輸入引數的描述以及如何使用它們從其他行程連接到現有的
     ‘SharedMemoryManager’ 服務。

      -- 方法: SharedMemory (size)

          建立並回傳一個新的 *note SharedMemory: 2ff8. 物件，該物件具有
          指定的 'size'（以位元組為單位）。

      -- 方法: ShareableList (sequence)

          建立並回傳一個新的 *note ShareableList: 2ff9. 物件，該物件由輸
          入 'sequence' 中的值初始化。

以下範例示範了 *note SharedMemoryManager: 2ff2. 的基本作用機制：

     >>> from multiprocessing.managers import SharedMemoryManager
     >>> smm = SharedMemoryManager()
     >>> smm.start()  # Start the process that manages the shared memory blocks
     >>> sl = smm.ShareableList(range(4))
     >>> sl
     ShareableList([0, 1, 2, 3], name='psm_6572_7512')
     >>> raw_shm = smm.SharedMemory(size=128)
     >>> another_sl = smm.ShareableList('alpha')
     >>> another_sl
     ShareableList(['a', 'l', 'p', 'h', 'a'], name='psm_6572_12221')
     >>> smm.shutdown()  # Calls unlink() on sl, raw_shm, and another_sl

以下範例描述了一種可能更方便的模式，即透過 *note with: 577. 陳述式使用
*note SharedMemoryManager: 2ff2. 物件，以確保所有共享記憶體區塊不再被需
要後都被釋放：

     >>> with SharedMemoryManager() as smm:
     ...     sl = smm.ShareableList(range(2000))
     ...     # Divide the work among two processes, storing partial results in sl
     ...     p1 = Process(target=do_work, args=(sl, 0, 1000))
     ...     p2 = Process(target=do_work, args=(sl, 1000, 2000))
     ...     p1.start()
     ...     p2.start()  # A multiprocessing.Pool might be more efficient
     ...     p1.join()
     ...     p2.join()   # Wait for all work to complete in both processes
     ...     total_result = sum(sl)  # Consolidate the partial results now in sl

在 *note with: 577. 陳述式中使用 *note SharedMemoryManager: 2ff2. 時，當
‘with’ 陳述式的程式碼區塊執行完畢時，使用該管理器建立的共享記憶體區塊都
會被釋放。

 -- 類別: multiprocessing.shared_memory.ShareableList (sequence=None, *,
          name=None)

     提供一個類似 list 的可變物件，其中儲存的所有值都儲存在共享記憶體區
     塊中。這將可儲存值限制為以下內建資料型別：

        * *note int: 23c. （有符號 64 位元）

        * *note float: 2c8.

        * *note bool: 40e.

        * *note str: 3f2. （編碼為 UTF-8 時每個小於 10M 位元組）

        * *note bytes: 1a5. （每個小於 10M 位元組）

        * ‘None’

     它也與內建 *note list: 5b6. 型別明顯不同，因為這些 list 不能更改其
     總長度（即沒有 ‘append()’、‘insert()’ 等）並且不支援通過切片動態建
     立新的 ‘ShareableList’ 實例。

     'sequence' 用於填充 (populate) 一個充滿值的新 ‘ShareableList’。設定
     為 ‘None’ 以透過其唯一的共享記憶體名稱來附加到已經存在的
     ‘ShareableList’。

     如 *note SharedMemory: 154f. 的定義中所述，'name' 是被請求之共享記
     憶體的唯一名稱。當附加到現有的 ‘ShareableList’ 時，指定其共享記憶體
     區塊的唯一名稱，同時將 'sequence' 設定為 ‘None’。

          備註: *note bytes: 1a5. 和 *note str: 3f2. 值存在一個已知問題
          。如果它們以 ‘\x00’ nul 位元組或字元結尾，那麼當透過索引從
          ‘ShareableList’ 中獲取它們時，這些位元組或字元可能會被'默默地
          剝離 (silently stripped)'。這種 ‘.rstrip(b'\x00')’ 行為被認為
          是一個錯誤，將來可能會消失。請參閱 gh-106939(3)。

     對於去除尾隨空值 (rstripping of trailing nulls) 會出問題的應用程式
     ，變通解法 (workaround) 是始終無條件地在儲存時於此類值的末尾追加一
     個額外非 0 位元組，並在獲取時也無條件地刪除它：

          >>> from multiprocessing import shared_memory
          >>> nul_bug_demo = shared_memory.ShareableList(['?\x00', b'\x03\x02\x01\x00\x00\x00'])
          >>> nul_bug_demo[0]
          '?'
          >>> nul_bug_demo[1]
          b'\x03\x02\x01'
          >>> nul_bug_demo.shm.unlink()
          >>> padded = shared_memory.ShareableList(['?\x00\x07', b'\x03\x02\x01\x00\x00\x00\x07'])
          >>> padded[0][:-1]
          '?\x00'
          >>> padded[1][:-1]
          b'\x03\x02\x01\x00\x00\x00'
          >>> padded.shm.unlink()

      -- 方法: count (value)

          回傳 'value' 出現的次數。

      -- 方法: index (value)

          回傳 'value' 的第一個索引位置。如果 'value' 不存在，則引發
          *note ValueError: 1e7.。

      -- 屬性: format

          唯讀屬性，包含所有目前有儲存的值所使用的 *note struct: c0. 打
          包格式。

      -- 屬性: shm

          儲存值的 *note SharedMemory: 154f. 實例。

以下範例示範了 *note ShareableList: 1872. 實例的基本用法：

     >>> from multiprocessing import shared_memory
     >>> a = shared_memory.ShareableList(['howdy', b'HoWdY', -273.154, 100, None, True, 42])
     >>> [ type(entry) for entry in a ]
     [<class 'str'>, <class 'bytes'>, <class 'float'>, <class 'int'>, <class 'NoneType'>, <class 'bool'>, <class 'int'>]
     >>> a[2]
     -273.154
     >>> a[2] = -78.5
     >>> a[2]
     -78.5
     >>> a[2] = 'dry ice'  # Changing data types is supported as well
     >>> a[2]
     'dry ice'
     >>> a[2] = 'larger than previously allocated storage space'
     Traceback (most recent call last):
       ...
     ValueError: exceeds available storage for existing str
     >>> a[2]
     'dry ice'
     >>> len(a)
     7
     >>> a.index(42)
     6
     >>> a.count(b'howdy')
     0
     >>> a.count(b'HoWdY')
     1
     >>> a.shm.close()
     >>> a.shm.unlink()
     >>> del a  # Use of a ShareableList after call to unlink() is unsupported

以下範例描述了一個、兩個或多個行程如何透過提供後面的共享記憶體區塊名稱來
存取同一個 *note ShareableList: 1872.：

     >>> b = shared_memory.ShareableList(range(5))         # In a first process
     >>> c = shared_memory.ShareableList(name=b.shm.name)  # In a second process
     >>> c
     ShareableList([0, 1, 2, 3, 4], name='...')
     >>> c[-1] = -999
     >>> b[-1]
     -999
     >>> b.shm.close()
     >>> c.shm.close()
     >>> c.shm.unlink()

以下範例示範了如果需要，可以對 *note ShareableList: 1872.（和底層 *note
SharedMemory: 154f.）物件進行 pickle 和 unpickle。請注意，它仍然是相同的
共享物件。發生這種情況是因為反序列化的物件具有相同的唯一名稱，並且只是附
加到具有相同名稱的現有物件（如果該物件仍然存在）：

     >>> import pickle
     >>> from multiprocessing import shared_memory
     >>> sl = shared_memory.ShareableList(range(10))
     >>> list(sl)
     [0, 1, 2, 3, 4, 5, 6, 7, 8, 9]

     >>> deserialized_sl = pickle.loads(pickle.dumps(sl))
     >>> list(deserialized_sl)
     [0, 1, 2, 3, 4, 5, 6, 7, 8, 9]

     >>> sl[0] = -1
     >>> deserialized_sl[1] = -2
     >>> list(sl)
     [-1, -2, 2, 3, 4, 5, 6, 7, 8, 9]
     >>> list(deserialized_sl)
     [-1, -2, 2, 3, 4, 5, 6, 7, 8, 9]

     >>> sl.shm.close()
     >>> sl.shm.unlink()

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/multiprocessing/shared_memory.py

   (2) https://numpy.org/

   (3) https://github.com/python/cpython/issues/106939


File: python.info,  Node: concurrent 套件,  Next: concurrent futures --- 啟動平行任務,  Prev: multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取,  Up: 並行執行 Concurrent Execution

5.17.4 ‘concurrent’ 套件
------------------------

目前此套件只有一個模組：

   * *note concurrent.futures: 1a. - 啟動平行任務


File: python.info,  Node: concurrent futures --- 啟動平行任務,  Next: subprocess --- 子行程管理,  Prev: concurrent 套件,  Up: 並行執行 Concurrent Execution

5.17.5 ‘concurrent.futures’ -- 啟動平行任務
-------------------------------------------

在 3.2 版被加入.

'原始碼：'Lib/concurrent/futures/thread.py(1) 與
Lib/concurrent/futures/process.py(2)

__________________________________________________________________

*note concurrent.futures: 1a. 模組提供了一個高階介面來非同步地
(asynchronously) 執行可呼叫物件 (callable) 。

非同步執行可以透過 *note ThreadPoolExecutor: 6e6. 來使用執行緒 (thread)
執行，或透過 *note ProcessPoolExecutor: 893. 來使用單獨行程 (process) 執
行。兩者都實作了相同的介面，該介面由抽象的 *note Executor: 3002. 類別定
義。

*note Availability: 1c56.: not WASI.

This module does not work or is not available on WebAssembly.  See *note
WebAssembly 平台: 16e6. for more information.

* Menu:

* Executor 物件::
* ThreadPoolExecutor::
* ProcessPoolExecutor::
* Future 物件::
* 模組函式::
* 例外類別::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/concurrent/futures/thread.py

   (2) 
https://github.com/python/cpython/tree/3.13/Lib/concurrent/futures/process.py


File: python.info,  Node: Executor 物件,  Next: ThreadPoolExecutor,  Up: concurrent futures --- 啟動平行任務

5.17.5.1 Executor 物件
......................

 -- 類別: concurrent.futures.Executor

     提供非同步執行呼叫方法的抽象類別。不應直接使用它，而應透過其具體子
     類別來使用。

      -- 方法: submit (fn, /, *args, **kwargs)

          為可呼叫物件 'fn' 排程來以 ‘fn(*args, **kwargs)’ 的形式執行並
          回傳一個表示可呼叫的執行的 *note Future: 1149. 物件。

               with ThreadPoolExecutor(max_workers=1) as executor:
                   future = executor.submit(pow, 323, 1235)
                   print(future.result())

      -- 方法: map (fn, *iterables, timeout=None, chunksize=1)

          類似於 *note map(fn, *iterables): 808.，除了：

             * 'iterables' 立即被收集而不是延遲 (lazily) 收集；

             * 'fn' 是非同步執行的，並且對 'fn' 的多次呼叫可以並行處理。

          如果 *note __next__(): 1260. 被呼叫，且在原先呼叫 *note
          Executor.map(): d8a. 的 'timeout' 秒後結果仍不可用，回傳的疊代
          器就會引發 *note TimeoutError: 7d9.。'timeout' 可以是整數或浮
          點數。如果未指定 'timeout' 或為 ‘None’，則等待時間就不會有限制
          。

          如果 'fn' 呼叫引發例外，則當從疊代器中檢索到它的值時將引發該例
          外。

          使用 *note ProcessPoolExecutor: 893. 時，此方法將 'iterables'
          分成許多分塊 (chunks)，並將其作為獨立的任務來提交給池 (pool)。
          可以透過將 'chunksize' 設定為正整數來指定這些分塊的（約略）大
          小。對於非常長的可疊代物件，'chunksize' 使用較大的值（與預設大
          小 1 相比）可以顯著提高性能。對於 *note ThreadPoolExecutor:
          6e6.，'chunksize' 無效。

          在 3.5 版的變更: 新增 'chunksize' 引數。

      -- 方法: shutdown (wait=True, *, cancel_futures=False)

          向 executor 發出訊號 (signal)，表明它應該在當前未定 (pending)
          的 future 完成執行時釋放它正在使用的任何資源。在關閉後呼叫
          *note Executor.submit(): a25. 和 *note Executor.map(): d8a. 將
          引發 *note RuntimeError: 179.。

          如果 'wait' 為 ‘True’ 則此方法將不會回傳，直到所有未定的
          futures 完成執行並且與 executor 關聯的資源都被釋放。如果
          'wait' 為 ‘False’ 則此方法將立即回傳，並且當所有未定的 future
          執行完畢時，與 executor 關聯的資源將被釋放。不管 'wait' 的值如
          何，整個 Python 程式都不會退出，直到所有未定的 futures 執行完
          畢。

          如果 'cancel_futures' 為 ‘True’，此方法將取消 executor 尚未開
          始運行的所有未定 future。無論 'cancel_futures' 的值如何，任何
          已完成或正在運行的 future 都不會被取消。

          如果 'cancel_futures' 和 'wait' 都為 ‘True’，則 executor 已開
          始運行的所有 future 將在此方法回傳之前完成。剩餘的 future 被取
          消。

          如果使用 *note with: 577. 陳述句，你就可以不用明確地呼叫此方法
          ，這將會自己關閉 *note Executor: 3002.（如同呼叫 *note
          Executor.shutdown(): 892. 時 'wait' 被設定為 ‘True’ 般等待）：

               import shutil
               with ThreadPoolExecutor(max_workers=4) as e:
                   e.submit(shutil.copy, 'src1.txt', 'dest1.txt')
                   e.submit(shutil.copy, 'src2.txt', 'dest2.txt')
                   e.submit(shutil.copy, 'src3.txt', 'dest3.txt')
                   e.submit(shutil.copy, 'src4.txt', 'dest4.txt')

          在 3.9 版的變更: 新增 'cancel_futures'。


File: python.info,  Node: ThreadPoolExecutor,  Next: ProcessPoolExecutor,  Prev: Executor 物件,  Up: concurrent futures --- 啟動平行任務

5.17.5.2 ThreadPoolExecutor
...........................

*note ThreadPoolExecutor: 6e6. 是一個 *note Executor: 3002. 子類別，它使
用執行緒池來非同步地執行呼叫。

當與 *note Future: 1149. 關聯的可呼叫物件等待另一個 *note Future: 1149.
的結果時，可能會發生死鎖 (deadlock)。例如：

     import time
     def wait_on_b():
         time.sleep(5)
         print(b.result())  # b will never complete because it is waiting on a.
         return 5

     def wait_on_a():
         time.sleep(5)
         print(a.result())  # a will never complete because it is waiting on b.
         return 6


     executor = ThreadPoolExecutor(max_workers=2)
     a = executor.submit(wait_on_b)
     b = executor.submit(wait_on_a)

和：

     def wait_on_future():
         f = executor.submit(pow, 5, 2)
         # This will never complete because there is only one worker thread and
         # it is executing this function.
         print(f.result())

     executor = ThreadPoolExecutor(max_workers=1)
     executor.submit(wait_on_future)

 -- 類別: concurrent.futures.ThreadPoolExecutor (max_workers=None,
          thread_name_prefix='', initializer=None, initargs=())

     一個 *note Executor: 3002. 子類別，它使用最多有 'max_workers' 個執
     行緒的池來非同步地執行呼叫。

     所有排隊到 ‘ThreadPoolExecutor’ 的執行緒都將在直譯器退出之前加入。
     請注意，執行此操作的退出處理程式會在任何使用 ‘atexit’ 新增的退出處
     理程式'之前'執行。這意味著必須捕獲並處理主執行緒中的例外，以便向執
     行緒發出訊號來正常退出 (gracefully exit)。因此，建議不要將
     ‘ThreadPoolExecutor’ 用於長時間運行的任務。

     'initializer' 是一個可選的可呼叫物件，在每個工作執行緒開始時呼叫；
     'initargs' 是傳遞給 initializer 的引數元組 (tuple)。如果
     'initializer' 引發例外，所有當前未定的作業以及任何向池中提交
     (submit) 更多作業的嘗試都將引發 *note BrokenThreadPool: 3005.。

     在 3.5 版的變更: 如果 'max_workers' 為 ‘None’ 或未給定，它將預設為
     機器上的處理器數量乘以 ‘5’，這假定了 *note ThreadPoolExecutor: 6e6.
     通常用於 I/O 重疊而非 CPU 密集的作業，並且 worker 的數量應該高於
     *note ProcessPoolExecutor: 893. 的 worker 數量。

     在 3.6 版的變更: 新增 'thread_name_prefix' 參數以允許使用者控制由池
     所建立的工作執行緒 (worker thread) 的 *note threading.Thread: 8f0.
     名稱，以便於除錯。

     在 3.7 版的變更: 新增 'initializer' 與 'initargs' 引數。

     在 3.8 版的變更: 'max_workers' 的預設值改為 ‘min(32, os.cpu_count()
     + 4)’。此預設值為 I/O 密集任務至少保留了 5 個 worker。它最多使用 32
     個 CPU 核心來執行CPU 密集任務，以釋放 GIL。並且它避免了在多核機器上
     隱晦地使用非常大量的資源。

     ThreadPoolExecutor 現在在啟動 'max_workers' 工作執行緒之前會重用
     (reuse) 空閒的工作執行緒。

     在 3.13 版的變更: Default value of 'max_workers' is changed to
     ‘min(32, (os.process_cpu_count() or 1) + 4)’.

* Menu:

* ThreadPoolExecutor 範例::


File: python.info,  Node: ThreadPoolExecutor 範例,  Up: ThreadPoolExecutor

5.17.5.3 ThreadPoolExecutor 範例
................................

     import concurrent.futures
     import urllib.request

     URLS = ['http://www.foxnews.com/',
             'http://www.cnn.com/',
             'http://europe.wsj.com/',
             'http://www.bbc.co.uk/',
             'http://nonexistant-subdomain.python.org/']

     # Retrieve a single page and report the URL and contents
     def load_url(url, timeout):
         with urllib.request.urlopen(url, timeout=timeout) as conn:
             return conn.read()

     # We can use a with statement to ensure threads are cleaned up promptly
     with concurrent.futures.ThreadPoolExecutor(max_workers=5) as executor:
         # Start the load operations and mark each future with its URL
         future_to_url = {executor.submit(load_url, url, 60): url for url in URLS}
         for future in concurrent.futures.as_completed(future_to_url):
             url = future_to_url[future]
             try:
                 data = future.result()
             except Exception as exc:
                 print('%r generated an exception: %s' % (url, exc))
             else:
                 print('%r page is %d bytes' % (url, len(data)))


File: python.info,  Node: ProcessPoolExecutor,  Next: Future 物件,  Prev: ThreadPoolExecutor,  Up: concurrent futures --- 啟動平行任務

5.17.5.4 ProcessPoolExecutor
............................

*note ProcessPoolExecutor: 893. 類別是一個 *note Executor: 3002. 的子類
別，它使用行程池來非同步地執行呼叫。*note ProcessPoolExecutor: 893. 使用
了 *note multiprocessing: 86. 模組，這允許它避開*note 全域直譯器鎖
(Global Interpreter Lock): 12e.，但也意味著只能執行和回傳可被 pickle 的
(picklable) 物件。

‘__main__’ 模組必須可以被工作子行程 (worker subprocess) 引入。這意味著
*note ProcessPoolExecutor: 893. 將無法在交互式直譯器 (interactive
interpreter) 中工作。

從提交給 *note ProcessPoolExecutor: 893. 的可呼叫物件中呼叫 *note
Executor: 3002. 或 *note Future: 1149. 方法將導致死鎖。

 -- 類別: concurrent.futures.ProcessPoolExecutor (max_workers=None,
          mp_context=None, initializer=None, initargs=(),
          max_tasks_per_child=None)

     An *note Executor: 3002. subclass that executes calls
     asynchronously using a pool of at most 'max_workers' processes.  If
     'max_workers' is ‘None’ or not given, it will default to *note
     os.process_cpu_count(): 1a7.  If 'max_workers' is less than or
     equal to ‘0’, then a *note ValueError: 1e7. will be raised.  On
     Windows, 'max_workers' must be less than or equal to ‘61’.  If it
     is not then *note ValueError: 1e7. will be raised.  If
     'max_workers' is ‘None’, then the default chosen will be at most
     ‘61’, even if more processors are available.  'mp_context' can be a
     *note multiprocessing: 86. context or ‘None’.  It will be used to
     launch the workers.  If 'mp_context' is ‘None’ or not given, the
     default *note multiprocessing: 86. context is used.  See *note
     Contexts and start methods: 2aa.

     'initializer' 是一個可選的可呼叫物件，在每個工作行程 (worker
     process) 開始時呼叫；'initargs' 是傳遞給 initializer 的引數元組。如
     果 'initializer' 引發例外，所有當前未定的作業以及任何向池中提交更多
     作業的嘗試都將引發 *note BrokenProcessPool: 3008.。

     'max_tasks_per_child' 是一個可選引數，它指定單個行程在退出並被新的
     工作行程替換之前可以執行的最大任務數。預設情況下
     'max_tasks_per_child' 是 ‘None’，這意味著工作行程的生命週期將與池一
     樣長。當指定最大值時，在沒有 'mp_context' 參數的情況下，將預設使用
     "spawn" 做為 multiprocessing 啟動方法。此功能與 "fork" 啟動方法不相
     容。

     在 3.3 版的變更: 當其中一個工作行程突然終止時，現在會引發 *note
     BrokenProcessPool: 3008. 錯誤。在過去，此行為是未定義的
     (undefined)，但對 executor 或其 future 的操作經常會發生凍結或死鎖。

     在 3.7 版的變更: 新增了 'mp_context' 引數以允許使用者控制由池所建立
     的工作行程的 start_method。

     新增 'initializer' 與 'initargs' 引數。

          備註: 預設的 *note multiprocessing: 86. 啟動方法（請參閱 *note
          Contexts and start methods: 2aa.）將不再是 Python 3.14 中的
          'fork'。需要 'fork' 用於其 *note ProcessPoolExecutor: 893. 的
          程式碼應透過傳遞
          ‘mp_context=multiprocessing.get_context("fork")’ 參數來明確指
          定。

     在 3.11 版的變更: 新增了 'max_tasks_per_child' 引數以允許使用者控制
     池中 worker 的生命週期。

     在 3.12 版的變更: 在 POSIX 系統上，如果你的應用程式有多個執行緒並且
     *note multiprocessing: 86. 情境使用了 ‘"fork"’ 啟動方法：內部呼叫以
     產生 worker 的 *note os.fork(): 17b. 函式可能會引發 *note
     DeprecationWarning: 18b.。傳遞一個 'mp_context' 以配置為使用不同的
     啟動方法。更多說明請參閱 *note os.fork(): 17b. 文件。

     在 3.13 版的變更: 'max_workers' uses *note os.process_cpu_count():
     1a7. by default, instead of *note os.cpu_count(): 1a8.

* Menu:

* ProcessPoolExecutor 範例::


File: python.info,  Node: ProcessPoolExecutor 範例,  Up: ProcessPoolExecutor

5.17.5.5 ProcessPoolExecutor 範例
.................................

     import concurrent.futures
     import math

     PRIMES = [
         112272535095293,
         112582705942171,
         112272535095293,
         115280095190773,
         115797848077099,
         1099726899285419]

     def is_prime(n):
         if n < 2:
             return False
         if n == 2:
             return True
         if n % 2 == 0:
             return False

         sqrt_n = int(math.floor(math.sqrt(n)))
         for i in range(3, sqrt_n + 1, 2):
             if n % i == 0:
                 return False
         return True

     def main():
         with concurrent.futures.ProcessPoolExecutor() as executor:
             for number, prime in zip(PRIMES, executor.map(is_prime, PRIMES)):
                 print('%d is prime: %s' % (number, prime))

     if __name__ == '__main__':
         main()


File: python.info,  Node: Future 物件,  Next: 模組函式,  Prev: ProcessPoolExecutor,  Up: concurrent futures --- 啟動平行任務

5.17.5.6 Future 物件
....................

*note Future: 1149. 類別封裝了可呼叫物件的非同步執行。*note Future:
1149. 實例由 *note Executor.submit(): a25. 建立。

 -- 類別: concurrent.futures.Future

     封裝可呼叫物件的非同步執行。*note Future: 1149. 實例由 *note
     Executor.submit(): a25. 建立，且除測試外不應直接建立。

      -- 方法: cancel ()

          嘗試取消呼叫。如果呼叫當前正在執行或已完成運行且無法取消，則該
          方法將回傳 ‘False’，否則呼叫將被取消並且該方法將回傳 ‘True’。

      -- 方法: cancelled ()

          如果該呼叫成功被取消，則回傳 ‘True’。

      -- 方法: running ()

          如果呼叫正在執行且無法取消，則回傳 ‘True’。

      -- 方法: done ()

          如果呼叫成功被取消或結束運行，則回傳 ‘True’。

      -- 方法: result (timeout=None)

          回傳該呼叫回傳的值。如果呼叫尚未完成，則此方法將等待至多
          'timeout' 秒。如果呼叫在 'timeout' 秒內未完成，則會引發 *note
          TimeoutError: 7d9.。'timeout' 可以是整數或浮點數。如果未指定
          'timeout' 或為 ‘None’，則等待時間就不會有限制。

          如果 future 在完成之前被取消，那麼 *note CancelledError: 97e.
          將被引發。

          如果該呼叫引發了例外，此方法將引發相同的例外。

      -- 方法: exception (timeout=None)

          回傳該呼叫引發的例外。如果呼叫尚未完成，則此方法將等待至多
          'timeout' 秒。如果呼叫在 'timeout' 秒內未完成，則會引發 *note
          TimeoutError: 7d9.。 'timeout' 可以是整數或浮點數。如果未指定
          'timeout' 或為 ‘None’，則等待時間就不會有限制。

          如果 future 在完成之前被取消，那麼 *note CancelledError: 97e.
          將被引發。

          如果呼叫在沒有引發的情況下完成，則回傳 ‘None’。

      -- 方法: add_done_callback (fn)

          將可呼叫的 'fn' 附加到 future 上。當 future 被取消或完成運行時
          ，'fn' 將被以 future 作為其唯一引數來呼叫。

          新增的可呼叫物件按新增順序呼叫，並且始終在屬於新增它們的行程的
          執行緒中呼叫。如果可呼叫物件引發 *note Exception: 97d. 子類別
          ，它將被記錄 (log) 並忽略。如果可呼叫物件引發 *note
          BaseException: 55f. 子類別，該行為未定義。

          如果 future 已經完成或被取消，'fn' 將立即被呼叫。

     以下 *note Future: 1149. 方法旨在用於單元測試和 *note Executor:
     3002. 實作。

      -- 方法: set_running_or_notify_cancel ()

          此方法只能在與 *note Future: 1149. 關聯的工作被執行之前於
          *note Executor: 3002. 實作中呼叫，或者在單元測試中呼叫。

          如果該方法回傳 ‘False’ 則 *note Future: 1149. 已被取消，即
          *note Future.cancel(): 300b. 被呼叫並回傳 ‘True’。任何等待
          *note Future: 1149. 完成的執行緒（即透過 *note as_completed():
          1541. 或 *note wait(): 1765.）將被喚醒。

          如果該方法回傳 ‘True’ 則代表 *note Future: 1149. 未被取消並已
          進入運行狀態，意即呼叫 *note Future.running(): 300d. 將回傳
          ‘True’。

          此方法只能呼叫一次，且不能在呼叫 *note Future.set_result():
          3013. 或 *note Future.set_exception(): 3014. 之後呼叫。

      -- 方法: set_result (result)

          將與 *note Future: 1149. 關聯的工作結果設定為 'result'。

          此方法只能在 *note Executor: 3002. 實作中和單元測試中使用。

          在 3.8 版的變更: 如果 *note Future: 1149. 已經完成，此方法會引
          發 *note concurrent.futures.InvalidStateError: 14ff.。

      -- 方法: set_exception (exception)

          將與 *note Future: 1149. 關聯的工作結果設定為 *note Exception:
          97d. 'exception'。

          此方法只能在 *note Executor: 3002. 實作中和單元測試中使用。

          在 3.8 版的變更: 如果 *note Future: 1149. 已經完成，此方法會引
          發 *note concurrent.futures.InvalidStateError: 14ff.。


File: python.info,  Node: 模組函式,  Next: 例外類別,  Prev: Future 物件,  Up: concurrent futures --- 啟動平行任務

5.17.5.7 模組函式
.................

 -- 函式: concurrent.futures.wait (fs, timeout=None,
          return_when=ALL_COMPLETED)

     等待 'fs' 給定的 *note Future: 1149. 實例（可能由不同的 *note
     Executor: 3002. 實例建立）完成。提供給 'fs' 的重複 future 將被刪除
     ，並且只會回傳一次。回傳一個集合的附名二元組 (named 2-tuple of
     sets)。第一組名為 ‘done’，包含在等待完成之前完成的 future（已完成或
     被取消的 future）。第二組名為 ‘not_done’，包含未完成的 future（未定
     或運行中的 future）。

     'timeout' 可用於控制回傳前等待的最大秒數。'timeout' 可以是整數或浮
     點數。如果未指定 'timeout' 或為 ‘None’，則等待時間就沒有限制。

     'return_when' 表示此函式應回傳的時間。它必須是以下常數之一：

     常數                                                   描述
                                                            
     --------------------------------------------------------------------------------------------------------------
                                                            
      -- 資料: concurrent.futures.FIRST_COMPLETED           當任何 future 完成或被取消時，該函式就會回傳。
                                                            
                                                            
      -- 資料: concurrent.futures.FIRST_EXCEPTION           該函式會在任何 future 透過引發例外而完結時回傳。如果
                                                            future 沒有引發例外，那麼它等同於
                                                            *note ALL_COMPLETED: 3018.。
                                                            
                                                            
      -- 資料: concurrent.futures.ALL_COMPLETED             當所有 future 都完成或被取消時，該函式才會回傳。
                                                            

 -- 函式: concurrent.futures.as_completed (fs, timeout=None)

     回傳由 'fs' 給定的 *note Future: 1149. 實例（可能由不同的 *note
     Executor: 3002. 實例建立）的疊代器，它在完成時產生 future（已完成或
     被取消的 future）。'fs' 給定的任何重複的 future 將只被回傳一次。呼
     叫 *note as_completed(): 1541. 之前完成的任何 future 將首先產生。如
     果 *note __next__(): 1260. 被呼叫，並且在原先呼叫 *note
     as_completed(): 1541. 的 'timeout' 秒後結果仍不可用，則回傳的疊代器
     會引發 *note TimeoutError: 7d9.。'timeout' 可以是整數或浮點數。如果
     未指定 'timeout' 或為 ‘None’，則等待時間就沒有限制。

也參考
......

PEP 3148(1) - futures - 非同步地執行運算

     描述此功能並提出被包含於 Python 標準函式庫中的提案。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3148/


File: python.info,  Node: 例外類別,  Prev: 模組函式,  Up: concurrent futures --- 啟動平行任務

5.17.5.8 例外類別
.................

 -- 例外: concurrent.futures.CancelledError

     當 future 被取消時引發。

 -- 例外: concurrent.futures.TimeoutError

     *note TimeoutError: 7d9. 的棄用別名，在 future 操作超過給定超時
     (timeout) 時引發。

     在 3.11 版的變更: 這個類別是 *note TimeoutError: 7d9. 的別名。

 -- 例外: concurrent.futures.BrokenExecutor

     衍生自 *note RuntimeError: 179.，當執行器因某種原因損壞時會引發此例
     外類別，並且不能用於提交或執行新任務。

     在 3.7 版被加入.

 -- 例外: concurrent.futures.InvalidStateError

     當前狀態下不允許的 future 操作被執行時而引發。

     在 3.8 版被加入.

 -- 例外: concurrent.futures.thread.BrokenThreadPool

     衍生自 *note BrokenExecutor: 301b.，當 *note ThreadPoolExecutor:
     6e6. 的其中一個 worker 初始化失敗時會引發此例外類別。

     在 3.7 版被加入.

 -- 例外: concurrent.futures.process.BrokenProcessPool

     衍生自 *note BrokenExecutor: 301b.（以前為 *note RuntimeError:
     179.），當 *note ProcessPoolExecutor: 893. 的其中一個 worker 以不乾
     淨的方式終止時將引發此例外類別（例如它是從外面被 kill 掉的）。

     在 3.3 版被加入.


File: python.info,  Node: subprocess --- 子行程管理,  Next: sched --- 事件排程器,  Prev: concurrent futures --- 啟動平行任務,  Up: 並行執行 Concurrent Execution

5.17.6 ‘subprocess’ -- 子行程管理
---------------------------------

'原始碼：'Lib/subprocess.py(1)

__________________________________________________________________

The *note subprocess: c1. module allows you to spawn new processes,
connect to their input/output/error pipes, and obtain their return
codes.  This module intends to replace several older modules and
functions:

     os.system
     os.spawn*

Information about how the *note subprocess: c1. module can be used to
replace these modules and functions can be found in the following
sections.

也參考
......

PEP 324(2) - 提議 subprocess 模組的 PEP

*note Availability: 1c56.: not WASI, not iOS.

This module does not work or is not available on WebAssembly platforms,
or on iOS. See *note WebAssembly 平台: 16e6. for more information on
WASM availability; see *note iOS: 1d56. for more information on iOS
availability.

* Menu:

* Using the subprocess Module::
* 安全性注意事項::
* Popen Objects::
* Windows Popen Helpers::
* Older high-level API::
* Replacing Older Functions with the subprocess Module::
* Legacy Shell Invocation Functions::
* 註解::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/subprocess.py

   (2) https://peps.python.org/pep-0324/


File: python.info,  Node: Using the subprocess Module,  Next: 安全性注意事項,  Up: subprocess --- 子行程管理

5.17.6.1 Using the ‘subprocess’ Module
......................................

The recommended approach to invoking subprocesses is to use the *note
run(): b2c. function for all use cases it can handle.  For more advanced
use cases, the underlying *note Popen: 17d. interface can be used
directly.

 -- 函式: subprocess.run (args, *, stdin=None, input=None, stdout=None,
          stderr=None, capture_output=False, shell=False, cwd=None,
          timeout=None, check=False, encoding=None, errors=None,
          text=None, env=None, universal_newlines=None,
          **other_popen_kwargs)

     Run the command described by 'args'.  Wait for command to complete,
     then return a *note CompletedProcess: e15. instance.

     The arguments shown above are merely the most common ones,
     described below in *note Frequently Used Arguments: 301f. (hence
     the use of keyword-only notation in the abbreviated signature).
     The full function signature is largely the same as that of the
     *note Popen: 17d. constructor - most of the arguments to this
     function are passed through to that interface.  ('timeout',
     'input', 'check', and 'capture_output' are not.)

     If 'capture_output' is true, stdout and stderr will be captured.
     When used, the internal *note Popen: 17d. object is automatically
     created with 'stdout' and 'stderr' both set to *note PIPE: b2d.
     The 'stdout' and 'stderr' arguments may not be supplied at the same
     time as 'capture_output'.  If you wish to capture and combine both
     streams into one, set 'stdout' to *note PIPE: b2d. and 'stderr' to
     *note STDOUT: 3020, instead of using 'capture_output'.

     A 'timeout' may be specified in seconds, it is internally passed on
     to *note Popen.communicate(): 3021.  If the timeout expires, the
     child process will be killed and waited for.  The *note
     TimeoutExpired: 3022. exception will be re-raised after the child
     process has terminated.  The initial process creation itself cannot
     be interrupted on many platform APIs so you are not guaranteed to
     see a timeout exception until at least after however long process
     creation takes.

     The 'input' argument is passed to *note Popen.communicate(): 3021.
     and thus to the subprocess's stdin.  If used it must be a byte
     sequence, or a string if 'encoding' or 'errors' is specified or
     'text' is true.  When used, the internal *note Popen: 17d. object
     is automatically created with 'stdin' set to *note PIPE: b2d, and
     the 'stdin' argument may not be used as well.

     If 'check' is true, and the process exits with a non-zero exit
     code, a *note CalledProcessError: 12b8. exception will be raised.
     Attributes of that exception hold the arguments, the exit code, and
     stdout and stderr if they were captured.

     If 'encoding' or 'errors' are specified, or 'text' is true, file
     objects for stdin, stdout and stderr are opened in text mode using
     the specified 'encoding' and 'errors' or the *note
     io.TextIOWrapper: 75f. default.  The 'universal_newlines' argument
     is equivalent to 'text' and is provided for backwards
     compatibility.  By default, file objects are opened in binary mode.

     If 'env' is not ‘None’, it must be a mapping that defines the
     environment variables for the new process; these are used instead
     of the default behavior of inheriting the current process'
     environment.  It is passed directly to *note Popen: 17d.  This
     mapping can be str to str on any platform or bytes to bytes on
     POSIX platforms much like *note os.environ: 1152. or *note
     os.environb: 11ae.

     範例：

          >>> subprocess.run(["ls", "-l"])  # 不捕捉輸出
          CompletedProcess(args=['ls', '-l'], returncode=0)

          >>> subprocess.run("exit 1", shell=True, check=True)
          Traceback (most recent call last):
            ...
          subprocess.CalledProcessError: Command 'exit 1' returned non-zero exit status 1

          >>> subprocess.run(["ls", "-l", "/dev/null"], capture_output=True)
          CompletedProcess(args=['ls', '-l', '/dev/null'], returncode=0,
          stdout=b'crw-rw-rw- 1 root root 1, 3 Jan 23 16:23 /dev/null\n', stderr=b'')

     在 3.5 版被加入.

     在 3.6 版的變更: 新增 'encoding' 與 'errors' 參數。

     在 3.7 版的變更: Added the 'text' parameter, as a more
     understandable alias of 'universal_newlines'.  Added the
     'capture_output' parameter.

     在 3.12 版的變更: Changed Windows shell search order for
     ‘shell=True’.  The current directory and ‘%PATH%’ are replaced with
     ‘%COMSPEC%’ and ‘%SystemRoot%\System32\cmd.exe’.  As a result,
     dropping a malicious program named ‘cmd.exe’ into a current
     directory no longer works.

 -- 類別: subprocess.CompletedProcess

     The return value from *note run(): b2c, representing a process that
     has finished.

      -- 屬性: args

          The arguments used to launch the process.  This may be a list
          or a string.

      -- 屬性: returncode

          Exit status of the child process.  Typically, an exit status
          of 0 indicates that it ran successfully.

          A negative value ‘-N’ indicates that the child was terminated
          by signal ‘N’ (POSIX only).

      -- 屬性: stdout

          Captured stdout from the child process.  A bytes sequence, or
          a string if *note run(): b2c. was called with an encoding,
          errors, or text=True.  ‘None’ if stdout was not captured.

          If you ran the process with ‘stderr=subprocess.STDOUT’, stdout
          and stderr will be combined in this attribute, and *note
          stderr: 3026. will be ‘None’.

      -- 屬性: stderr

          Captured stderr from the child process.  A bytes sequence, or
          a string if *note run(): b2c. was called with an encoding,
          errors, or text=True.  ‘None’ if stderr was not captured.

      -- 方法: check_returncode ()

          If *note returncode: 3024. is non-zero, raise a *note
          CalledProcessError: 12b8.

     在 3.5 版被加入.

 -- 資料: subprocess.DEVNULL

     Special value that can be used as the 'stdin', 'stdout' or 'stderr'
     argument to *note Popen: 17d. and indicates that the special file
     *note os.devnull: 1939. will be used.

     在 3.3 版被加入.

 -- 資料: subprocess.PIPE

     Special value that can be used as the 'stdin', 'stdout' or 'stderr'
     argument to *note Popen: 17d. and indicates that a pipe to the
     standard stream should be opened.  Most useful with *note
     Popen.communicate(): 3021.

 -- 資料: subprocess.STDOUT

     Special value that can be used as the 'stderr' argument to *note
     Popen: 17d. and indicates that standard error should go into the
     same handle as standard output.

 -- 例外: subprocess.SubprocessError

     Base class for all other exceptions from this module.

     在 3.3 版被加入.

 -- 例外: subprocess.TimeoutExpired

     Subclass of *note SubprocessError: 3028, raised when a timeout
     expires while waiting for a child process.

      -- 屬性: cmd

          Command that was used to spawn the child process.

      -- 屬性: timeout

          Timeout in seconds.

      -- 屬性: output

          Output of the child process if it was captured by *note run():
          b2c. or *note check_output(): f64.  Otherwise, ‘None’.  This
          is always *note bytes: 1a5. when any output was captured
          regardless of the ‘text=True’ setting.  It may remain ‘None’
          instead of ‘b''’ when no output was observed.

      -- 屬性: stdout

          Alias for output, for symmetry with *note stderr: 302d.

      -- 屬性: stderr

          Stderr output of the child process if it was captured by *note
          run(): b2c.  Otherwise, ‘None’.  This is always *note bytes:
          1a5. when stderr output was captured regardless of the
          ‘text=True’ setting.  It may remain ‘None’ instead of ‘b''’
          when no stderr output was observed.

     在 3.3 版被加入.

     在 3.5 版的變更: 'stdout' and 'stderr' attributes added

 -- 例外: subprocess.CalledProcessError

     Subclass of *note SubprocessError: 3028, raised when a process run
     by *note check_call(): 302e, *note check_output(): f64, or *note
     run(): b2c. (with ‘check=True’) returns a non-zero exit status.

      -- 屬性: returncode

          Exit status of the child process.  If the process exited due
          to a signal, this will be the negative signal number.

      -- 屬性: cmd

          Command that was used to spawn the child process.

      -- 屬性: output

          Output of the child process if it was captured by *note run():
          b2c. or *note check_output(): f64.  Otherwise, ‘None’.

      -- 屬性: stdout

          Alias for output, for symmetry with *note stderr: 3033.

      -- 屬性: stderr

          Stderr output of the child process if it was captured by *note
          run(): b2c.  Otherwise, ‘None’.

     在 3.5 版的變更: 'stdout' and 'stderr' attributes added

* Menu:

* Frequently Used Arguments::
* Popen Constructor::
* 例外: 例外<6>.


File: python.info,  Node: Frequently Used Arguments,  Next: Popen Constructor,  Up: Using the subprocess Module

5.17.6.2 Frequently Used Arguments
..................................

To support a wide variety of use cases, the *note Popen: 17d.
constructor (and the convenience functions) accept a large number of
optional arguments.  For most typical use cases, many of these arguments
can be safely left at their default values.  The arguments that are most
commonly needed are:

     'args' is required for all calls and should be a string, or a
     sequence of program arguments.  Providing a sequence of arguments
     is generally preferred, as it allows the module to take care of any
     required escaping and quoting of arguments (e.g.  to permit spaces
     in file names).  If passing a single string, either 'shell' must be
     *note True: bb4. (see below) or else the string must simply name
     the program to be executed without specifying any arguments.

     'stdin', 'stdout' and 'stderr' specify the executed program's
     standard input, standard output and standard error file handles,
     respectively.  Valid values are ‘None’, *note PIPE: b2d, *note
     DEVNULL: 10e7, an existing file descriptor (a positive integer),
     and an existing *note file object: 115b. with a valid file
     descriptor.  With the default settings of ‘None’, no redirection
     will occur.  *note PIPE: b2d. indicates that a new pipe to the
     child should be created.  *note DEVNULL: 10e7. indicates that the
     special file *note os.devnull: 1939. will be used.  Additionally,
     'stderr' can be *note STDOUT: 3020, which indicates that the stderr
     data from the child process should be captured into the same file
     handle as for 'stdout'.

     If 'encoding' or 'errors' are specified, or 'text' (also known as
     'universal_newlines') is true, the file objects 'stdin', 'stdout'
     and 'stderr' will be opened in text mode using the 'encoding' and
     'errors' specified in the call or the defaults for *note
     io.TextIOWrapper: 75f.

     For 'stdin', line ending characters ‘'\n'’ in the input will be
     converted to the default line separator *note os.linesep: 2055.
     For 'stdout' and 'stderr', all line endings in the output will be
     converted to ‘'\n'’.  For more information see the documentation of
     the *note io.TextIOWrapper: 75f. class when the 'newline' argument
     to its constructor is ‘None’.

     If text mode is not used, 'stdin', 'stdout' and 'stderr' will be
     opened as binary streams.  No encoding or line ending conversion is
     performed.

     在 3.6 版的變更: 新增 'encoding' 與 'errors' 參數。

     在 3.7 版的變更: Added the 'text' parameter as an alias for
     'universal_newlines'.

          備註: The newlines attribute of the file objects *note
          Popen.stdin: 3035, *note Popen.stdout: 3036. and *note
          Popen.stderr: 3037. are not updated by the *note
          Popen.communicate(): 3021. method.

     If 'shell' is ‘True’, the specified command will be executed
     through the shell.  This can be useful if you are using Python
     primarily for the enhanced control flow it offers over most system
     shells and still want convenient access to other shell features
     such as shell pipes, filename wildcards, environment variable
     expansion, and expansion of ‘~’ to a user's home directory.
     However, note that Python itself offers implementations of many
     shell-like features (in particular, *note glob: 5a, *note fnmatch:
     52, *note os.walk(): 451, *note os.path.expandvars(): 1347, *note
     os.path.expanduser(): 9b8, and *note shutil: b3.).

     在 3.3 版的變更: When 'universal_newlines' is ‘True’, the class
     uses the encoding *note locale.getpreferredencoding(False): 4df.
     instead of ‘locale.getpreferredencoding()’.  See the *note
     io.TextIOWrapper: 75f. class for more information on this change.

          備註: Read the *note Security Considerations: 3038. section
          before using ‘shell=True’.

These options, along with all of the other options, are described in
more detail in the *note Popen: 17d. constructor documentation.


File: python.info,  Node: Popen Constructor,  Next: 例外<6>,  Prev: Frequently Used Arguments,  Up: Using the subprocess Module

5.17.6.3 Popen Constructor
..........................

The underlying process creation and management in this module is handled
by the *note Popen: 17d. class.  It offers a lot of flexibility so that
developers are able to handle the less common cases not covered by the
convenience functions.

 -- 類別: subprocess.Popen (args, bufsize=-1, executable=None,
          stdin=None, stdout=None, stderr=None, preexec_fn=None,
          close_fds=True, shell=False, cwd=None, env=None,
          universal_newlines=None, startupinfo=None, creationflags=0,
          restore_signals=True, start_new_session=False, pass_fds=(), *,
          group=None, extra_groups=None, user=None, umask=-1,
          encoding=None, errors=None, text=None, pipesize=-1,
          process_group=None)

     Execute a child program in a new process.  On POSIX, the class uses
     *note os.execvpe(): 2aaa.-like behavior to execute the child
     program.  On Windows, the class uses the Windows ‘CreateProcess()’
     function.  The arguments to *note Popen: 17d. are as follows.

     'args' should be a sequence of program arguments or else a single
     string or *note path-like object: ac2.  By default, the program to
     execute is the first item in 'args' if 'args' is a sequence.  If
     'args' is a string, the interpretation is platform-dependent and
     described below.  See the 'shell' and 'executable' arguments for
     additional differences from the default behavior.  Unless otherwise
     stated, it is recommended to pass 'args' as a sequence.

          警告: For maximum reliability, use a fully qualified path for
          the executable.  To search for an unqualified name on ‘PATH’,
          use *note shutil.which(): 45b.  On all platforms, passing
          *note sys.executable: 383. is the recommended way to launch
          the current Python interpreter again, and use the ‘-m’
          command-line format to launch an installed module.

          Resolving the path of 'executable' (or the first item of
          'args') is platform dependent.  For POSIX, see *note
          os.execvpe(): 2aaa, and note that when resolving or searching
          for the executable path, 'cwd' overrides the current working
          directory and 'env' can override the ‘PATH’ environment
          variable.  For Windows, see the documentation of the
          ‘lpApplicationName’ and ‘lpCommandLine’ parameters of WinAPI
          ‘CreateProcess’, and note that when resolving or searching for
          the executable path with ‘shell=False’, 'cwd' does not
          override the current working directory and 'env' cannot
          override the ‘PATH’ environment variable.  Using a full path
          avoids all of these variations.

     An example of passing some arguments to an external program as a
     sequence is:

          Popen(["/usr/bin/git", "commit", "-m", "Fixes a bug."])

     On POSIX, if 'args' is a string, the string is interpreted as the
     name or path of the program to execute.  However, this can only be
     done if not passing arguments to the program.

          備註: It may not be obvious how to break a shell command into
          a sequence of arguments, especially in complex cases.  *note
          shlex.split(): 4e1. can illustrate how to determine the
          correct tokenization for 'args':

               >>> import shlex, subprocess
               >>> command_line = input()
               /bin/vikings -input eggs.txt -output "spam spam.txt" -cmd "echo '$MONEY'"
               >>> args = shlex.split(command_line)
               >>> print(args)
               ['/bin/vikings', '-input', 'eggs.txt', '-output', 'spam spam.txt', '-cmd', "echo '$MONEY'"]
               >>> p = subprocess.Popen(args) # 成功！

          Note in particular that options (such as '-input') and
          arguments (such as 'eggs.txt') that are separated by
          whitespace in the shell go in separate list elements, while
          arguments that need quoting or backslash escaping when used in
          the shell (such as filenames containing spaces or the 'echo'
          command shown above) are single list elements.

     On Windows, if 'args' is a sequence, it will be converted to a
     string in a manner described in *note Converting an argument
     sequence to a string on Windows: 303a.  This is because the
     underlying ‘CreateProcess()’ operates on strings.

     在 3.6 版的變更: 'args' parameter accepts a *note path-like object:
     ac2. if 'shell' is ‘False’ and a sequence containing path-like
     objects on POSIX.

     在 3.8 版的變更: 'args' parameter accepts a *note path-like object:
     ac2. if 'shell' is ‘False’ and a sequence containing bytes and
     path-like objects on Windows.

     The 'shell' argument (which defaults to ‘False’) specifies whether
     to use the shell as the program to execute.  If 'shell' is ‘True’,
     it is recommended to pass 'args' as a string rather than as a
     sequence.

     On POSIX with ‘shell=True’, the shell defaults to ‘/bin/sh’.  If
     'args' is a string, the string specifies the command to execute
     through the shell.  This means that the string must be formatted
     exactly as it would be when typed at the shell prompt.  This
     includes, for example, quoting or backslash escaping filenames with
     spaces in them.  If 'args' is a sequence, the first item specifies
     the command string, and any additional items will be treated as
     additional arguments to the shell itself.  That is to say, *note
     Popen: 17d. does the equivalent of:

          Popen(['/bin/sh', '-c', args[0], args[1], ...])

     On Windows with ‘shell=True’, the ‘COMSPEC’ environment variable
     specifies the default shell.  The only time you need to specify
     ‘shell=True’ on Windows is when the command you wish to execute is
     built into the shell (e.g.  ‘dir’ or ‘copy’).  You do not need
     ‘shell=True’ to run a batch file or console-based executable.

          備註: Read the *note Security Considerations: 3038. section
          before using ‘shell=True’.

     'bufsize' will be supplied as the corresponding argument to the
     *note open(): 4c0. function when creating the stdin/stdout/stderr
     pipe file objects:

        - ‘0’ means unbuffered (read and write are one system call and
          can return short)

        - ‘1’ means line buffered (only usable if ‘text=True’ or
          ‘universal_newlines=True’)

        - any other positive value means use a buffer of approximately
          that size

        - negative bufsize (the default) means the system default of
          io.DEFAULT_BUFFER_SIZE will be used.

     在 3.3.1 版的變更: 'bufsize' now defaults to -1 to enable buffering
     by default to match the behavior that most code expects.  In
     versions prior to Python 3.2.4 and 3.3.1 it incorrectly defaulted
     to ‘0’ which was unbuffered and allowed short reads.  This was
     unintentional and did not match the behavior of Python 2 as most
     code expected.

     The 'executable' argument specifies a replacement program to
     execute.  It is very seldom needed.  When ‘shell=False’,
     'executable' replaces the program to execute specified by 'args'.
     However, the original 'args' is still passed to the program.  Most
     programs treat the program specified by 'args' as the command name,
     which can then be different from the program actually executed.  On
     POSIX, the 'args' name becomes the display name for the executable
     in utilities such as ‘ps’.  If ‘shell=True’, on POSIX the
     'executable' argument specifies a replacement shell for the default
     ‘/bin/sh’.

     在 3.6 版的變更: 'executable' parameter accepts a *note path-like
     object: ac2. on POSIX.

     在 3.8 版的變更: 'executable' parameter accepts a bytes and *note
     path-like object: ac2. on Windows.

     在 3.12 版的變更: Changed Windows shell search order for
     ‘shell=True’.  The current directory and ‘%PATH%’ are replaced with
     ‘%COMSPEC%’ and ‘%SystemRoot%\System32\cmd.exe’.  As a result,
     dropping a malicious program named ‘cmd.exe’ into a current
     directory no longer works.

     'stdin', 'stdout' and 'stderr' specify the executed program's
     standard input, standard output and standard error file handles,
     respectively.  Valid values are ‘None’, *note PIPE: b2d, *note
     DEVNULL: 10e7, an existing file descriptor (a positive integer),
     and an existing *note file object: 115b. with a valid file
     descriptor.  With the default settings of ‘None’, no redirection
     will occur.  *note PIPE: b2d. indicates that a new pipe to the
     child should be created.  *note DEVNULL: 10e7. indicates that the
     special file *note os.devnull: 1939. will be used.  Additionally,
     'stderr' can be *note STDOUT: 3020, which indicates that the stderr
     data from the applications should be captured into the same file
     handle as for 'stdout'.

     If 'preexec_fn' is set to a callable object, this object will be
     called in the child process just before the child is executed.
     (POSIX only)

          警告: The 'preexec_fn' parameter is NOT SAFE to use in the
          presence of threads in your application.  The child process
          could deadlock before exec is called.

          備註: If you need to modify the environment for the child use
          the 'env' parameter rather than doing it in a 'preexec_fn'.
          The 'start_new_session' and 'process_group' parameters should
          take the place of code using 'preexec_fn' to call *note
          os.setsid(): 18da. or *note os.setpgid(): 2a0a. in the child.

     在 3.8 版的變更: The 'preexec_fn' parameter is no longer supported
     in subinterpreters.  The use of the parameter in a subinterpreter
     raises *note RuntimeError: 179.  The new restriction may affect
     applications that are deployed in mod_wsgi, uWSGI, and other
     embedded environments.

     If 'close_fds' is true, all file descriptors except ‘0’, ‘1’ and
     ‘2’ will be closed before the child process is executed.  Otherwise
     when 'close_fds' is false, file descriptors obey their inheritable
     flag as described in *note Inheritance of File Descriptors: e9d.

     On Windows, if 'close_fds' is true then no handles will be
     inherited by the child process unless explicitly passed in the
     ‘handle_list’ element of *note STARTUPINFO.lpAttributeList: bb5, or
     by standard handle redirection.

     在 3.2 版的變更: The default for 'close_fds' was changed from *note
     False: adb. to what is described above.

     在 3.7 版的變更: On Windows the default for 'close_fds' was changed
     from *note False: adb. to *note True: bb4. when redirecting the
     standard handles.  It's now possible to set 'close_fds' to *note
     True: bb4. when redirecting the standard handles.

     'pass_fds' is an optional sequence of file descriptors to keep open
     between the parent and child.  Providing any 'pass_fds' forces
     'close_fds' to be *note True: bb4.  (POSIX only)

     在 3.2 版的變更: 新增 'pass_fds' 參數。

     If 'cwd' is not ‘None’, the function changes the working directory
     to 'cwd' before executing the child.  'cwd' can be a string, bytes
     or *note path-like: ac2. object.  On POSIX, the function looks for
     'executable' (or for the first item in 'args') relative to 'cwd' if
     the executable path is a relative path.

     在 3.6 版的變更: 'cwd' parameter accepts a *note path-like object:
     ac2. on POSIX.

     在 3.7 版的變更: 'cwd' parameter accepts a *note path-like object:
     ac2. on Windows.

     在 3.8 版的變更: 'cwd' parameter accepts a bytes object on Windows.

     If 'restore_signals' is true (the default) all signals that Python
     has set to SIG_IGN are restored to SIG_DFL in the child process
     before the exec.  Currently this includes the SIGPIPE, SIGXFZ and
     SIGXFSZ signals.  (POSIX only)

     在 3.2 版的變更: 新增 'restore_signals'。

     If 'start_new_session' is true the ‘setsid()’ system call will be
     made in the child process prior to the execution of the subprocess.

     *note 適用: 1c56.：POSIX

     在 3.2 版的變更: 新增 'start_new_session'。

     If 'process_group' is a non-negative integer, the ‘setpgid(0,
     value)’ system call will be made in the child process prior to the
     execution of the subprocess.

     *note 適用: 1c56.：POSIX

     在 3.11 版的變更: 新增 'process_group'。

     If 'group' is not ‘None’, the setregid() system call will be made
     in the child process prior to the execution of the subprocess.  If
     the provided value is a string, it will be looked up via *note
     grp.getgrnam(): 303b. and the value in ‘gr_gid’ will be used.  If
     the value is an integer, it will be passed verbatim.  (POSIX only)

     *note 適用: 1c56.：POSIX

     在 3.9 版被加入.

     If 'extra_groups' is not ‘None’, the setgroups() system call will
     be made in the child process prior to the execution of the
     subprocess.  Strings provided in 'extra_groups' will be looked up
     via *note grp.getgrnam(): 303b. and the values in ‘gr_gid’ will be
     used.  Integer values will be passed verbatim.  (POSIX only)

     *note 適用: 1c56.：POSIX

     在 3.9 版被加入.

     If 'user' is not ‘None’, the setreuid() system call will be made in
     the child process prior to the execution of the subprocess.  If the
     provided value is a string, it will be looked up via *note
     pwd.getpwnam(): 303c. and the value in ‘pw_uid’ will be used.  If
     the value is an integer, it will be passed verbatim.  (POSIX only)

     *note 適用: 1c56.：POSIX

     在 3.9 版被加入.

     If 'umask' is not negative, the umask() system call will be made in
     the child process prior to the execution of the subprocess.

     *note 適用: 1c56.：POSIX

     在 3.9 版被加入.

     If 'env' is not ‘None’, it must be a mapping that defines the
     environment variables for the new process; these are used instead
     of the default behavior of inheriting the current process'
     environment.  This mapping can be str to str on any platform or
     bytes to bytes on POSIX platforms much like *note os.environ: 1152.
     or *note os.environb: 11ae.

          備註: If specified, 'env' must provide any variables required
          for the program to execute.  On Windows, in order to run a
          side-by-side assembly(1) the specified 'env' 'must' include a
          valid ‘SystemRoot’.

     If 'encoding' or 'errors' are specified, or 'text' is true, the
     file objects 'stdin', 'stdout' and 'stderr' are opened in text mode
     with the specified 'encoding' and 'errors', as described above in
     *note Frequently Used Arguments: 301f.  The 'universal_newlines'
     argument is equivalent to 'text' and is provided for backwards
     compatibility.  By default, file objects are opened in binary mode.

     在 3.6 版被加入: 新增 'encoding' 與 'errors'。

     在 3.7 版被加入: 'text' was added as a more readable alias for
     'universal_newlines'.

     If given, 'startupinfo' will be a *note STARTUPINFO: 303d. object,
     which is passed to the underlying ‘CreateProcess’ function.

     If given, 'creationflags', can be one or more of the following
     flags:

        * *note CREATE_NEW_CONSOLE: 303e.

        * *note CREATE_NEW_PROCESS_GROUP: 303f.

        * *note ABOVE_NORMAL_PRIORITY_CLASS: 3040.

        * *note BELOW_NORMAL_PRIORITY_CLASS: 3041.

        * *note HIGH_PRIORITY_CLASS: 3042.

        * *note IDLE_PRIORITY_CLASS: 3043.

        * *note NORMAL_PRIORITY_CLASS: 3044.

        * *note REALTIME_PRIORITY_CLASS: 3045.

        * *note CREATE_NO_WINDOW: 3046.

        * *note DETACHED_PROCESS: 3047.

        * *note CREATE_DEFAULT_ERROR_MODE: 3048.

        * *note CREATE_BREAKAWAY_FROM_JOB: 3049.

     'pipesize' can be used to change the size of the pipe when *note
     PIPE: b2d. is used for 'stdin', 'stdout' or 'stderr'.  The size of
     the pipe is only changed on platforms that support this (only Linux
     at this time of writing).  Other platforms will ignore this
     parameter.

     在 3.10 版的變更: 新增 ‘pipesize’ 參數。

     Popen objects are supported as context managers via the *note with:
     577. statement: on exit, standard file descriptors are closed, and
     the process is waited for.

          with Popen(["ifconfig"], stdout=PIPE) as proc:
              log.write(proc.stdout.read())

     Popen and the other functions in this module that use it raise an
     *note auditing event: 17bd. ‘subprocess.Popen’ with arguments
     ‘executable’, ‘args’, ‘cwd’, and ‘env’.  The value for ‘args’ may
     be a single string or a list of strings, depending on platform.

     在 3.2 版的變更: 新增情境管理器的支援。

     在 3.6 版的變更: Popen destructor now emits a *note
     ResourceWarning: 229. warning if the child process is still
     running.

     在 3.8 版的變更: Popen can use *note os.posix_spawn(): 205. in some
     cases for better performance.  On Windows Subsystem for Linux and
     QEMU User Emulation, Popen constructor using *note
     os.posix_spawn(): 205. no longer raise an exception on errors like
     missing program, but the child process fails with a non-zero *note
     returncode: 18ac.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Side-by-Side_Assembly


File: python.info,  Node: 例外<6>,  Prev: Popen Constructor,  Up: Using the subprocess Module

5.17.6.4 例外
.............

Exceptions raised in the child process, before the new program has
started to execute, will be re-raised in the parent.

The most common exception raised is *note OSError: 350.  This occurs,
for example, when trying to execute a non-existent file.  Applications
should prepare for *note OSError: 350. exceptions.  Note that, when
‘shell=True’, *note OSError: 350. will be raised by the child only if
the selected shell itself was not found.  To determine if the shell
failed to find the requested application, it is necessary to check the
return code or output from the subprocess.

A *note ValueError: 1e7. will be raised if *note Popen: 17d. is called
with invalid arguments.

*note check_call(): 302e. and *note check_output(): f64. will raise
*note CalledProcessError: 12b8. if the called process returns a non-zero
return code.

All of the functions and methods that accept a 'timeout' parameter, such
as *note run(): b2c. and *note Popen.communicate(): 3021. will raise
*note TimeoutExpired: 3022. if the timeout expires before the process
exits.

Exceptions defined in this module all inherit from *note
SubprocessError: 3028.

在 3.3 版被加入: The *note SubprocessError: 3028. base class was added.


File: python.info,  Node: 安全性注意事項,  Next: Popen Objects,  Prev: Using the subprocess Module,  Up: subprocess --- 子行程管理

5.17.6.5 安全性注意事項
.......................

Unlike some other popen functions, this library will not implicitly
choose to call a system shell.  This means that all characters,
including shell metacharacters, can safely be passed to child processes.
If the shell is invoked explicitly, via ‘shell=True’, it is the
application's responsibility to ensure that all whitespace and
metacharacters are quoted appropriately to avoid shell injection(1)
vulnerabilities.  On *note some platforms: 304c, it is possible to use
*note shlex.quote(): 10c4. for this escaping.

On Windows, batch files (‘*.bat’ or ‘*.cmd’) may be launched by the
operating system in a system shell regardless of the arguments passed to
this library.  This could result in arguments being parsed according to
shell rules, but without any escaping added by Python.  If you are
intentionally launching a batch file with arguments from untrusted
sources, consider passing ‘shell=True’ to allow Python to escape special
characters.  See gh-114539(2) for additional discussion.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Shell_injection#Shell_injection

   (2) https://github.com/python/cpython/issues/114539


File: python.info,  Node: Popen Objects,  Next: Windows Popen Helpers,  Prev: 安全性注意事項,  Up: subprocess --- 子行程管理

5.17.6.6 Popen Objects
......................

Instances of the *note Popen: 17d. class have the following methods:

 -- 方法: Popen.poll ()

     Check if child process has terminated.  Set and return *note
     returncode: 18ac. attribute.  Otherwise, returns ‘None’.

 -- 方法: Popen.wait (timeout=None)

     Wait for child process to terminate.  Set and return *note
     returncode: 18ac. attribute.

     If the process does not terminate after 'timeout' seconds, raise a
     *note TimeoutExpired: 3022. exception.  It is safe to catch this
     exception and retry the wait.

          備註: This will deadlock when using ‘stdout=PIPE’ or
          ‘stderr=PIPE’ and the child process generates enough output to
          a pipe such that it blocks waiting for the OS pipe buffer to
          accept more data.  Use *note Popen.communicate(): 3021. when
          using pipes to avoid that.

          備註: When the ‘timeout’ parameter is not ‘None’, then (on
          POSIX) the function is implemented using a busy loop
          (non-blocking call and short sleeps).  Use the *note asyncio:
          8. module for an asynchronous wait: see *note
          asyncio.create_subprocess_exec: a1a.

     在 3.3 版的變更: 新增 'timeout'。

 -- 方法: Popen.communicate (input=None, timeout=None)

     Interact with process: Send data to stdin.  Read data from stdout
     and stderr, until end-of-file is reached.  Wait for process to
     terminate and set the *note returncode: 18ac. attribute.  The
     optional 'input' argument should be data to be sent to the child
     process, or ‘None’, if no data should be sent to the child.  If
     streams were opened in text mode, 'input' must be a string.
     Otherwise, it must be bytes.

     *note communicate(): 3021. returns a tuple ‘(stdout_data,
     stderr_data)’.  The data will be strings if streams were opened in
     text mode; otherwise, bytes.

     Note that if you want to send data to the process's stdin, you need
     to create the Popen object with ‘stdin=PIPE’.  Similarly, to get
     anything other than ‘None’ in the result tuple, you need to give
     ‘stdout=PIPE’ and/or ‘stderr=PIPE’ too.

     If the process does not terminate after 'timeout' seconds, a *note
     TimeoutExpired: 3022. exception will be raised.  Catching this
     exception and retrying communication will not lose any output.

     The child process is not killed if the timeout expires, so in order
     to cleanup properly a well-behaved application should kill the
     child process and finish communication:

          proc = subprocess.Popen(...)
          try:
              outs, errs = proc.communicate(timeout=15)
          except TimeoutExpired:
              proc.kill()
              outs, errs = proc.communicate()

          備註: The data read is buffered in memory, so do not use this
          method if the data size is large or unlimited.

     在 3.3 版的變更: 新增 'timeout'。

 -- 方法: Popen.send_signal (signal)

     Sends the signal 'signal' to the child.

     Do nothing if the process completed.

          備註: On Windows, SIGTERM is an alias for *note terminate():
          134a.  CTRL_C_EVENT and CTRL_BREAK_EVENT can be sent to
          processes started with a 'creationflags' parameter which
          includes ‘CREATE_NEW_PROCESS_GROUP’.

 -- 方法: Popen.terminate ()

     Stop the child.  On POSIX OSs the method sends *note SIGTERM: 134d.
     to the child.  On Windows the Win32 API function
     ‘TerminateProcess()’ is called to stop the child.

 -- 方法: Popen.kill ()

     Kills the child.  On POSIX OSs the function sends SIGKILL to the
     child.  On Windows *note kill(): 134b. is an alias for *note
     terminate(): 134a.

The following attributes are also set by the class for you to access.
Reassigning them to new values is unsupported:

 -- 屬性: Popen.args

     The 'args' argument as it was passed to *note Popen: 17d. - a
     sequence of program arguments or else a single string.

     在 3.3 版被加入.

 -- 屬性: Popen.stdin

     If the 'stdin' argument was *note PIPE: b2d, this attribute is a
     writeable stream object as returned by *note open(): 4c0.  If the
     'encoding' or 'errors' arguments were specified or the 'text' or
     'universal_newlines' argument was ‘True’, the stream is a text
     stream, otherwise it is a byte stream.  If the 'stdin' argument was
     not *note PIPE: b2d, this attribute is ‘None’.

 -- 屬性: Popen.stdout

     If the 'stdout' argument was *note PIPE: b2d, this attribute is a
     readable stream object as returned by *note open(): 4c0.  Reading
     from the stream provides output from the child process.  If the
     'encoding' or 'errors' arguments were specified or the 'text' or
     'universal_newlines' argument was ‘True’, the stream is a text
     stream, otherwise it is a byte stream.  If the 'stdout' argument
     was not *note PIPE: b2d, this attribute is ‘None’.

 -- 屬性: Popen.stderr

     If the 'stderr' argument was *note PIPE: b2d, this attribute is a
     readable stream object as returned by *note open(): 4c0.  Reading
     from the stream provides error output from the child process.  If
     the 'encoding' or 'errors' arguments were specified or the 'text'
     or 'universal_newlines' argument was ‘True’, the stream is a text
     stream, otherwise it is a byte stream.  If the 'stderr' argument
     was not *note PIPE: b2d, this attribute is ‘None’.

     警告: Use *note communicate(): 3021. rather than *note
     .stdin.write: 3035, *note .stdout.read: 3036. or *note
     .stderr.read: 3037. to avoid deadlocks due to any of the other OS
     pipe buffers filling up and blocking the child process.

 -- 屬性: Popen.pid

     The process ID of the child process.

     Note that if you set the 'shell' argument to ‘True’, this is the
     process ID of the spawned shell.

 -- 屬性: Popen.returncode

     The child return code.  Initially ‘None’, *note returncode: 18ac.
     is set by a call to the *note poll(): 304e, *note wait(): c8b, or
     *note communicate(): 3021. methods if they detect that the process
     has terminated.

     A ‘None’ value indicates that the process hadn't yet terminated at
     the time of the last method call.

     A negative value ‘-N’ indicates that the child was terminated by
     signal ‘N’ (POSIX only).


File: python.info,  Node: Windows Popen Helpers,  Next: Older high-level API,  Prev: Popen Objects,  Up: subprocess --- 子行程管理

5.17.6.7 Windows Popen Helpers
..............................

The *note STARTUPINFO: 303d. class and following constants are only
available on Windows.

 -- 類別: subprocess.STARTUPINFO (*, dwFlags=0, hStdInput=None,
          hStdOutput=None, hStdError=None, wShowWindow=0,
          lpAttributeList=None)

     Partial support of the Windows STARTUPINFO(1) structure is used for
     *note Popen: 17d. creation.  The following attributes can be set by
     passing them as keyword-only arguments.

     在 3.7 版的變更: Keyword-only argument support was added.

      -- 屬性: dwFlags

          A bit field that determines whether certain *note STARTUPINFO:
          303d. attributes are used when the process creates a window.

               si = subprocess.STARTUPINFO()
               si.dwFlags = subprocess.STARTF_USESTDHANDLES | subprocess.STARTF_USESHOWWINDOW

      -- 屬性: hStdInput

          If *note dwFlags: 3052. specifies *note STARTF_USESTDHANDLES:
          3054, this attribute is the standard input handle for the
          process.  If *note STARTF_USESTDHANDLES: 3054. is not
          specified, the default for standard input is the keyboard
          buffer.

      -- 屬性: hStdOutput

          If *note dwFlags: 3052. specifies *note STARTF_USESTDHANDLES:
          3054, this attribute is the standard output handle for the
          process.  Otherwise, this attribute is ignored and the default
          for standard output is the console window's buffer.

      -- 屬性: hStdError

          If *note dwFlags: 3052. specifies *note STARTF_USESTDHANDLES:
          3054, this attribute is the standard error handle for the
          process.  Otherwise, this attribute is ignored and the default
          for standard error is the console window's buffer.

      -- 屬性: wShowWindow

          If *note dwFlags: 3052. specifies *note STARTF_USESHOWWINDOW:
          3058, this attribute can be any of the values that can be
          specified in the ‘nCmdShow’ parameter for the ShowWindow(2)
          function, except for ‘SW_SHOWDEFAULT’.  Otherwise, this
          attribute is ignored.

          *note SW_HIDE: 3059. is provided for this attribute.  It is
          used when *note Popen: 17d. is called with ‘shell=True’.

      -- 屬性: lpAttributeList

          A dictionary of additional attributes for process creation as
          given in ‘STARTUPINFOEX’, see UpdateProcThreadAttribute(3).

          Supported attributes:

          'handle_list'

               Sequence of handles that will be inherited.  'close_fds'
               must be true if non-empty.

               The handles must be temporarily made inheritable by *note
               os.set_handle_inheritable(): ea1. when passed to the
               *note Popen: 17d. constructor, else *note OSError: 350.
               will be raised with Windows error
               ‘ERROR_INVALID_PARAMETER’ (87).

                    警告: In a multithreaded process, use caution to
                    avoid leaking handles that are marked inheritable
                    when combining this feature with concurrent calls to
                    other process creation functions that inherit all
                    handles such as *note os.system(): 13c8.  This also
                    applies to standard handle redirection, which
                    temporarily creates inheritable handles.

          在 3.7 版被加入.

* Menu:

* Windows Constants::

   ---------- Footnotes ----------

   (1) https://msdn.microsoft.com/en-us/library/ms686331(v=vs.85).aspx

   (2) https://msdn.microsoft.com/en-us/library/ms633548(v=vs.85).aspx

   (3) 
https://msdn.microsoft.com/en-us/library/windows/desktop/ms686880(v=vs.85).aspx


File: python.info,  Node: Windows Constants,  Up: Windows Popen Helpers

5.17.6.8 Windows Constants
..........................

The *note subprocess: c1. module exposes the following constants.

 -- 資料: subprocess.STD_INPUT_HANDLE

     The standard input device.  Initially, this is the console input
     buffer, ‘CONIN$’.

 -- 資料: subprocess.STD_OUTPUT_HANDLE

     The standard output device.  Initially, this is the active console
     screen buffer, ‘CONOUT$’.

 -- 資料: subprocess.STD_ERROR_HANDLE

     The standard error device.  Initially, this is the active console
     screen buffer, ‘CONOUT$’.

 -- 資料: subprocess.SW_HIDE

     Hides the window.  Another window will be activated.

 -- 資料: subprocess.STARTF_USESTDHANDLES

     Specifies that the *note STARTUPINFO.hStdInput: 3053, *note
     STARTUPINFO.hStdOutput: 3055, and *note STARTUPINFO.hStdError:
     3056. attributes contain additional information.

 -- 資料: subprocess.STARTF_USESHOWWINDOW

     Specifies that the *note STARTUPINFO.wShowWindow: 3057. attribute
     contains additional information.

 -- 資料: subprocess.STARTF_FORCEONFEEDBACK

     A *note STARTUPINFO.dwFlags: 3052. parameter to specify that the
     'Working in Background' mouse cursor will be displayed while a
     process is launching.  This is the default behavior for GUI
     processes.

     在 3.13 版被加入.

 -- 資料: subprocess.STARTF_FORCEOFFFEEDBACK

     A *note STARTUPINFO.dwFlags: 3052. parameter to specify that the
     mouse cursor will not be changed when launching a process.

     在 3.13 版被加入.

 -- 資料: subprocess.CREATE_NEW_CONSOLE

     The new process has a new console, instead of inheriting its
     parent's console (the default).

 -- 資料: subprocess.CREATE_NEW_PROCESS_GROUP

     A *note Popen: 17d. ‘creationflags’ parameter to specify that a new
     process group will be created.  This flag is necessary for using
     *note os.kill(): 12f4. on the subprocess.

     This flag is ignored if *note CREATE_NEW_CONSOLE: 303e. is
     specified.

 -- 資料: subprocess.ABOVE_NORMAL_PRIORITY_CLASS

     A *note Popen: 17d. ‘creationflags’ parameter to specify that a new
     process will have an above average priority.

     在 3.7 版被加入.

 -- 資料: subprocess.BELOW_NORMAL_PRIORITY_CLASS

     A *note Popen: 17d. ‘creationflags’ parameter to specify that a new
     process will have a below average priority.

     在 3.7 版被加入.

 -- 資料: subprocess.HIGH_PRIORITY_CLASS

     A *note Popen: 17d. ‘creationflags’ parameter to specify that a new
     process will have a high priority.

     在 3.7 版被加入.

 -- 資料: subprocess.IDLE_PRIORITY_CLASS

     A *note Popen: 17d. ‘creationflags’ parameter to specify that a new
     process will have an idle (lowest) priority.

     在 3.7 版被加入.

 -- 資料: subprocess.NORMAL_PRIORITY_CLASS

     A *note Popen: 17d. ‘creationflags’ parameter to specify that a new
     process will have a normal priority.  (default)

     在 3.7 版被加入.

 -- 資料: subprocess.REALTIME_PRIORITY_CLASS

     A *note Popen: 17d. ‘creationflags’ parameter to specify that a new
     process will have realtime priority.  You should almost never use
     REALTIME_PRIORITY_CLASS, because this interrupts system threads
     that manage mouse input, keyboard input, and background disk
     flushing.  This class can be appropriate for applications that
     "talk" directly to hardware or that perform brief tasks that should
     have limited interruptions.

     在 3.7 版被加入.

 -- 資料: subprocess.CREATE_NO_WINDOW

     A *note Popen: 17d. ‘creationflags’ parameter to specify that a new
     process will not create a window.

     在 3.7 版被加入.

 -- 資料: subprocess.DETACHED_PROCESS

     A *note Popen: 17d. ‘creationflags’ parameter to specify that a new
     process will not inherit its parent's console.  This value cannot
     be used with CREATE_NEW_CONSOLE.

     在 3.7 版被加入.

 -- 資料: subprocess.CREATE_DEFAULT_ERROR_MODE

     A *note Popen: 17d. ‘creationflags’ parameter to specify that a new
     process does not inherit the error mode of the calling process.
     Instead, the new process gets the default error mode.  This feature
     is particularly useful for multithreaded shell applications that
     run with hard errors disabled.

     在 3.7 版被加入.

 -- 資料: subprocess.CREATE_BREAKAWAY_FROM_JOB

     A *note Popen: 17d. ‘creationflags’ parameter to specify that a new
     process is not associated with the job.

     在 3.7 版被加入.


File: python.info,  Node: Older high-level API,  Next: Replacing Older Functions with the subprocess Module,  Prev: Windows Popen Helpers,  Up: subprocess --- 子行程管理

5.17.6.9 Older high-level API
.............................

Prior to Python 3.5, these three functions comprised the high level API
to subprocess.  You can now use *note run(): b2c. in many cases, but
lots of existing code calls these functions.

 -- 函式: subprocess.call (args, *, stdin=None, stdout=None,
          stderr=None, shell=False, cwd=None, timeout=None,
          **other_popen_kwargs)

     Run the command described by 'args'.  Wait for command to complete,
     then return the *note returncode: 18ac. attribute.

     Code needing to capture stdout or stderr should use *note run():
     b2c. instead:

          run(...).returncode

     To suppress stdout or stderr, supply a value of *note DEVNULL:
     10e7.

     The arguments shown above are merely some common ones.  The full
     function signature is the same as that of the *note Popen: 17d.
     constructor - this function passes all supplied arguments other
     than 'timeout' directly through to that interface.

          備註: Do not use ‘stdout=PIPE’ or ‘stderr=PIPE’ with this
          function.  The child process will block if it generates enough
          output to a pipe to fill up the OS pipe buffer as the pipes
          are not being read from.

     在 3.3 版的變更: 新增 'timeout'。

     在 3.12 版的變更: Changed Windows shell search order for
     ‘shell=True’.  The current directory and ‘%PATH%’ are replaced with
     ‘%COMSPEC%’ and ‘%SystemRoot%\System32\cmd.exe’.  As a result,
     dropping a malicious program named ‘cmd.exe’ into a current
     directory no longer works.

 -- 函式: subprocess.check_call (args, *, stdin=None, stdout=None,
          stderr=None, shell=False, cwd=None, timeout=None,
          **other_popen_kwargs)

     Run command with arguments.  Wait for command to complete.  If the
     return code was zero then return, otherwise raise *note
     CalledProcessError: 12b8.  The *note CalledProcessError: 12b8.
     object will have the return code in the *note returncode: 302f.
     attribute.  If *note check_call(): 302e. was unable to start the
     process it will propagate the exception that was raised.

     Code needing to capture stdout or stderr should use *note run():
     b2c. instead:

          run(..., check=True)

     To suppress stdout or stderr, supply a value of *note DEVNULL:
     10e7.

     The arguments shown above are merely some common ones.  The full
     function signature is the same as that of the *note Popen: 17d.
     constructor - this function passes all supplied arguments other
     than 'timeout' directly through to that interface.

          備註: Do not use ‘stdout=PIPE’ or ‘stderr=PIPE’ with this
          function.  The child process will block if it generates enough
          output to a pipe to fill up the OS pipe buffer as the pipes
          are not being read from.

     在 3.3 版的變更: 新增 'timeout'。

     在 3.12 版的變更: Changed Windows shell search order for
     ‘shell=True’.  The current directory and ‘%PATH%’ are replaced with
     ‘%COMSPEC%’ and ‘%SystemRoot%\System32\cmd.exe’.  As a result,
     dropping a malicious program named ‘cmd.exe’ into a current
     directory no longer works.

 -- 函式: subprocess.check_output (args, *, stdin=None, stderr=None,
          shell=False, cwd=None, encoding=None, errors=None,
          universal_newlines=None, timeout=None, text=None,
          **other_popen_kwargs)

     Run command with arguments and return its output.

     If the return code was non-zero it raises a *note
     CalledProcessError: 12b8.  The *note CalledProcessError: 12b8.
     object will have the return code in the *note returncode: 302f.
     attribute and any output in the *note output: 3031. attribute.

     這等同於：

          run(..., check=True, stdout=PIPE).stdout

     The arguments shown above are merely some common ones.  The full
     function signature is largely the same as that of *note run(): b2c.
     - most arguments are passed directly through to that interface.
     One API deviation from *note run(): b2c. behavior exists: passing
     ‘input=None’ will behave the same as ‘input=b''’ (or ‘input=''’,
     depending on other arguments) rather than using the parent's
     standard input file handle.

     By default, this function will return the data as encoded bytes.
     The actual encoding of the output data may depend on the command
     being invoked, so the decoding to text will often need to be
     handled at the application level.

     This behaviour may be overridden by setting 'text', 'encoding',
     'errors', or 'universal_newlines' to ‘True’ as described in *note
     Frequently Used Arguments: 301f. and *note run(): b2c.

     To also capture standard error in the result, use
     ‘stderr=subprocess.STDOUT’:

          >>> subprocess.check_output(
          ...     "ls non_existent_file; exit 0",
          ...     stderr=subprocess.STDOUT,
          ...     shell=True)
          'ls: non_existent_file: No such file or directory\n'

     在 3.1 版被加入.

     在 3.3 版的變更: 新增 'timeout'。

     在 3.4 版的變更: 新增 'input' 關鍵字引數的支援。

     在 3.6 版的變更: 新增 'encoding' 與 'errors'。細節請見 *note run():
     b2c.。

     在 3.7 版被加入: 'text' was added as a more readable alias for
     'universal_newlines'.

     在 3.12 版的變更: Changed Windows shell search order for
     ‘shell=True’.  The current directory and ‘%PATH%’ are replaced with
     ‘%COMSPEC%’ and ‘%SystemRoot%\System32\cmd.exe’.  As a result,
     dropping a malicious program named ‘cmd.exe’ into a current
     directory no longer works.


File: python.info,  Node: Replacing Older Functions with the subprocess Module,  Next: Legacy Shell Invocation Functions,  Prev: Older high-level API,  Up: subprocess --- 子行程管理

5.17.6.10 Replacing Older Functions with the ‘subprocess’ Module
................................................................

In this section, "a becomes b" means that b can be used as a replacement
for a.

     備註: All "a" functions in this section fail (more or less)
     silently if the executed program cannot be found; the "b"
     replacements raise *note OSError: 350. instead.

     In addition, the replacements using *note check_output(): f64. will
     fail with a *note CalledProcessError: 12b8. if the requested
     operation produces a non-zero return code.  The output is still
     available as the *note output: 3031. attribute of the raised
     exception.

In the following examples, we assume that the relevant functions have
already been imported from the *note subprocess: c1. module.

* Menu:

* Replacing /bin/sh shell command substitution::
* Replacing shell pipeline::
* Replacing os.system(): Replacing os system.
* Replacing the os.spawn family: Replacing the os spawn family.
* Replacing os.popen(), os.popen2(), os.popen3(): Replacing os popen os popen2 os popen3.
* Replacing functions from the popen2 module::


File: python.info,  Node: Replacing /bin/sh shell command substitution,  Next: Replacing shell pipeline,  Up: Replacing Older Functions with the subprocess Module

5.17.6.11 Replacing ‘/bin/sh’ shell command substitution
........................................................

     output=$(mycmd myarg)

變成：

     output = check_output(["mycmd", "myarg"])


File: python.info,  Node: Replacing shell pipeline,  Next: Replacing os system,  Prev: Replacing /bin/sh shell command substitution,  Up: Replacing Older Functions with the subprocess Module

5.17.6.12 Replacing shell pipeline
..................................

     output=$(dmesg | grep hda)

變成：

     p1 = Popen(["dmesg"], stdout=PIPE)
     p2 = Popen(["grep", "hda"], stdin=p1.stdout, stdout=PIPE)
     p1.stdout.close()  # Allow p1 to receive a SIGPIPE if p2 exits.
     output = p2.communicate()[0]

The ‘p1.stdout.close()’ call after starting the p2 is important in order
for p1 to receive a SIGPIPE if p2 exits before p1.

Alternatively, for trusted input, the shell's own pipeline support may
still be used directly:

     output=$(dmesg | grep hda)

變成：

     output = check_output("dmesg | grep hda", shell=True)


File: python.info,  Node: Replacing os system,  Next: Replacing the os spawn family,  Prev: Replacing shell pipeline,  Up: Replacing Older Functions with the subprocess Module

5.17.6.13 Replacing ‘os.system()’
.................................

     sts = os.system("mycmd" + " myarg")
     # 變成
     retcode = call("mycmd" + " myarg", shell=True)

註解：

   * Calling the program through the shell is usually not required.

   * The *note call(): b2e. return value is encoded differently to that
     of *note os.system(): 13c8.

   * The *note os.system(): 13c8. function ignores SIGINT and SIGQUIT
     signals while the command is running, but the caller must do this
     separately when using the *note subprocess: c1. module.

A more realistic example would look like this:

     try:
         retcode = call("mycmd" + " myarg", shell=True)
         if retcode < 0:
             print("Child was terminated by signal", -retcode, file=sys.stderr)
         else:
             print("Child returned", retcode, file=sys.stderr)
     except OSError as e:
         print("Execution failed:", e, file=sys.stderr)


File: python.info,  Node: Replacing the os spawn family,  Next: Replacing os popen os popen2 os popen3,  Prev: Replacing os system,  Up: Replacing Older Functions with the subprocess Module

5.17.6.14 Replacing the ‘os.spawn’ family
.........................................

P_NOWAIT 範例：

     pid = os.spawnlp(os.P_NOWAIT, "/bin/mycmd", "mycmd", "myarg")
     ==>
     pid = Popen(["/bin/mycmd", "myarg"]).pid

P_WAIT 範例：

     retcode = os.spawnlp(os.P_WAIT, "/bin/mycmd", "mycmd", "myarg")
     ==>
     retcode = call(["/bin/mycmd", "myarg"])

Vector example:

     os.spawnvp(os.P_NOWAIT, path, args)
     ==>
     Popen([path] + args[1:])

Environment example:

     os.spawnlpe(os.P_NOWAIT, "/bin/mycmd", "mycmd", "myarg", env)
     ==>
     Popen(["/bin/mycmd", "myarg"], env={"PATH": "/usr/bin"})


File: python.info,  Node: Replacing os popen os popen2 os popen3,  Next: Replacing functions from the popen2 module,  Prev: Replacing the os spawn family,  Up: Replacing Older Functions with the subprocess Module

5.17.6.15 Replacing ‘os.popen()’, ‘os.popen2()’, ‘os.popen3()’
..............................................................

     (child_stdin, child_stdout) = os.popen2(cmd, mode, bufsize)
     ==>
     p = Popen(cmd, shell=True, bufsize=bufsize,
               stdin=PIPE, stdout=PIPE, close_fds=True)
     (child_stdin, child_stdout) = (p.stdin, p.stdout)

     (child_stdin,
      child_stdout,
      child_stderr) = os.popen3(cmd, mode, bufsize)
     ==>
     p = Popen(cmd, shell=True, bufsize=bufsize,
               stdin=PIPE, stdout=PIPE, stderr=PIPE, close_fds=True)
     (child_stdin,
      child_stdout,
      child_stderr) = (p.stdin, p.stdout, p.stderr)

     (child_stdin, child_stdout_and_stderr) = os.popen4(cmd, mode, bufsize)
     ==>
     p = Popen(cmd, shell=True, bufsize=bufsize,
               stdin=PIPE, stdout=PIPE, stderr=STDOUT, close_fds=True)
     (child_stdin, child_stdout_and_stderr) = (p.stdin, p.stdout)

Return code handling translates as follows:

     pipe = os.popen(cmd, 'w')
     ...
     rc = pipe.close()
     if rc is not None and rc >> 8:
         print("There were some errors")
     ==>
     process = Popen(cmd, stdin=PIPE)
     ...
     process.stdin.close()
     if process.wait() != 0:
         print("There were some errors")


File: python.info,  Node: Replacing functions from the popen2 module,  Prev: Replacing os popen os popen2 os popen3,  Up: Replacing Older Functions with the subprocess Module

5.17.6.16 Replacing functions from the ‘popen2’ module
......................................................

     備註: If the cmd argument to popen2 functions is a string, the
     command is executed through /bin/sh.  If it is a list, the command
     is directly executed.

     (child_stdout, child_stdin) = popen2.popen2("somestring", bufsize, mode)
     ==>
     p = Popen("somestring", shell=True, bufsize=bufsize,
               stdin=PIPE, stdout=PIPE, close_fds=True)
     (child_stdout, child_stdin) = (p.stdout, p.stdin)

     (child_stdout, child_stdin) = popen2.popen2(["mycmd", "myarg"], bufsize, mode)
     ==>
     p = Popen(["mycmd", "myarg"], bufsize=bufsize,
               stdin=PIPE, stdout=PIPE, close_fds=True)
     (child_stdout, child_stdin) = (p.stdout, p.stdin)

‘popen2.Popen3’ and ‘popen2.Popen4’ basically work as *note
subprocess.Popen: 17d, except that:

   * *note Popen: 17d. raises an exception if the execution fails.

   * The 'capturestderr' argument is replaced with the 'stderr'
     argument.

   * ‘stdin=PIPE’ and ‘stdout=PIPE’ must be specified.

   * popen2 closes all file descriptors by default, but you have to
     specify ‘close_fds=True’ with *note Popen: 17d. to guarantee this
     behavior on all platforms or past Python versions.


File: python.info,  Node: Legacy Shell Invocation Functions,  Next: 註解,  Prev: Replacing Older Functions with the subprocess Module,  Up: subprocess --- 子行程管理

5.17.6.17 Legacy Shell Invocation Functions
...........................................

This module also provides the following legacy functions from the 2.x
‘commands’ module.  These operations implicitly invoke the system shell
and none of the guarantees described above regarding security and
exception handling consistency are valid for these functions.

 -- 函式: subprocess.getstatusoutput (cmd, *, encoding=None,
          errors=None)

     Return ‘(exitcode, output)’ of executing 'cmd' in a shell.

     Execute the string 'cmd' in a shell with ‘Popen.check_output()’ and
     return a 2-tuple ‘(exitcode, output)’.  'encoding' and 'errors' are
     used to decode output; see the notes on *note Frequently Used
     Arguments: 301f. for more details.

     A trailing newline is stripped from the output.  The exit code for
     the command can be interpreted as the return code of subprocess.
     Example:

          >>> subprocess.getstatusoutput('ls /bin/ls')
          (0, '/bin/ls')
          >>> subprocess.getstatusoutput('cat /bin/junk')
          (1, 'cat: /bin/junk: No such file or directory')
          >>> subprocess.getstatusoutput('/bin/junk')
          (127, 'sh: /bin/junk: not found')
          >>> subprocess.getstatusoutput('/bin/kill $$')
          (-15, '')

     *note 適用: 1c56.：Unix 和 Windows。

     在 3.3.4 版的變更: 新增對 Windows 的支援。

     The function now returns (exitcode, output) instead of (status,
     output) as it did in Python 3.3.3 and earlier.  exitcode has the
     same value as *note returncode: 18ac.

     在 3.11 版的變更: 新增 'encoding' 與 'errors' 參數。

 -- 函式: subprocess.getoutput (cmd, *, encoding=None, errors=None)

     Return output (stdout and stderr) of executing 'cmd' in a shell.

     Like *note getstatusoutput(): f65, except the exit code is ignored
     and the return value is a string containing the command's output.
     Example:

          >>> subprocess.getoutput('ls /bin/ls')
          '/bin/ls'

     *note 適用: 1c56.：Unix 和 Windows。

     在 3.3.4 版的變更: 新增對 Windows 的支援

     在 3.11 版的變更: 新增 'encoding' 與 'errors' 參數。


File: python.info,  Node: 註解,  Prev: Legacy Shell Invocation Functions,  Up: subprocess --- 子行程管理

5.17.6.18 註解
..............

* Menu:

* Converting an argument sequence to a string on Windows::
* 停用 vfork() 或 posix_spawn(): 停用 vfork 或 posix_spawn.


File: python.info,  Node: Converting an argument sequence to a string on Windows,  Next: 停用 vfork 或 posix_spawn,  Up: 註解

5.17.6.19 Converting an argument sequence to a string on Windows
................................................................

On Windows, an 'args' sequence is converted to a string that can be
parsed using the following rules (which correspond to the rules used by
the MS C runtime):

  1. Arguments are delimited by white space, which is either a space or
     a tab.

  2. A string surrounded by double quotation marks is interpreted as a
     single argument, regardless of white space contained within.  A
     quoted string can be embedded in an argument.

  3. A double quotation mark preceded by a backslash is interpreted as a
     literal double quotation mark.

  4. Backslashes are interpreted literally, unless they immediately
     precede a double quotation mark.

  5. If backslashes immediately precede a double quotation mark, every
     pair of backslashes is interpreted as a literal backslash.  If the
     number of backslashes is odd, the last backslash escapes the next
     double quotation mark as described in rule 3.

也參考
......

*note shlex: b2.

     Module which provides function to parse and escape command lines.


File: python.info,  Node: 停用 vfork 或 posix_spawn,  Prev: Converting an argument sequence to a string on Windows,  Up: 註解

5.17.6.20 停用 ‘vfork()’ 或 ‘posix_spawn()’
...........................................

在 Linux 上，*note subprocess: c1. 在安全的情況下預設會在內部使用
‘vfork()’ 系統呼叫，而不是 ‘fork()’，這顯著地提高了性能。

如果你遇到了一個推定為極異常的情況，需要防止 Python 使用 ‘vfork()’，你可
以將 ‘subprocess._USE_VFORK’ 屬性設為 false 值。

     subprocess._USE_VFORK = False  # 見 CPython 問題 gh-NNNNNN.

設定它並不會影響 ‘posix_spawn()’ 的使用，它可以在其 libc 實作內部使用
‘vfork()’。如果你需要封鎖該屬性的使用，則有一個類似的
‘subprocess._USE_POSIX_SPAWN’ 屬性。

     subprocess._USE_POSIX_SPAWN = False  # 見 CPython 問題 gh-NNNNNN.

在任何 Python 版本上將這些設定為 false 都是安全的。當不受支援時，它們對
舊版本沒有影響。不要假設屬性可供讀取。儘管有它們的名稱，真實值並不表示將
使用相應的函式，而只是表示可能會使用。

每當你需要使用這些私有開關以重現你所看到的問題時，請隨時提出問題 (file
issues)。從程式碼中的註解連結到該問題。

在 3.8 版被加入: ‘_USE_POSIX_SPAWN’

在 3.11 版被加入: ‘_USE_VFORK’


File: python.info,  Node: sched --- 事件排程器,  Next: queue --- 同步佇列 synchronized queue 類別,  Prev: subprocess --- 子行程管理,  Up: 並行執行 Concurrent Execution

5.17.7 ‘sched’ -- 事件排程器
----------------------------

'原始碼：'Lib/sched.py(1)

__________________________________________________________________

*note sched: ad. 模組定義了一個有實作通用事件排程器的類別：

 -- 類別: sched.scheduler (timefunc=time.monotonic,
          delayfunc=time.sleep)

     *note scheduler: 10bf. 類別定義了事件排程的泛用介面。它需要兩個函式
     來和「外部世界」作用 —— 'timefunc' 應不帶引數地被呼叫，並回傳一個數
     字（為「時間」，可為任何單位）。'delayfunc' 函式應以一個引數呼叫，
     並與 'timefunc' 的輸出相容，且應延遲其指定的時間單位。每個事件運行
     後，也會以引數 ‘0’ 呼叫 'delayfunc'，來使得其他執行緒有機會在多執行
     緒應用程式中運行。

     在 3.3 版的變更: 'timefunc' 和 'delayfunc' 參數是可選的。

     在 3.3 版的變更: *note scheduler: 10bf. 類別可以安全地在多執行緒環
     境中使用。

範例：

     >>> import sched, time
     >>> s = sched.scheduler(time.time, time.sleep)
     >>> def print_time(a='default'):
     ...     print("From print_time", time.time(), a)
     ...
     >>> def print_some_times():
     ...     print(time.time())
     ...     s.enter(10, 1, print_time)
     ...     s.enter(5, 2, print_time, argument=('positional',))
     ...     # despite having higher priority, 'keyword' runs after 'positional' as enter() is relative
     ...     s.enter(5, 1, print_time, kwargs={'a': 'keyword'})
     ...     s.enterabs(1_650_000_000, 10, print_time, argument=("first enterabs",))
     ...     s.enterabs(1_650_000_000, 5, print_time, argument=("second enterabs",))
     ...     s.run()
     ...     print(time.time())
     ...
     >>> print_some_times()
     1652342830.3640375
     From print_time 1652342830.3642538 second enterabs
     From print_time 1652342830.3643398 first enterabs
     From print_time 1652342835.3694863 positional
     From print_time 1652342835.3696074 keyword
     From print_time 1652342840.369612 default
     1652342840.3697174

* Menu:

* 排程器物件::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/sched.py


File: python.info,  Node: 排程器物件,  Up: sched --- 事件排程器

5.17.7.1 排程器物件
...................

*note scheduler: 10bf. 實例具有以下方法和屬性：

 -- 方法: scheduler.enterabs (time, priority, action, argument=(),
          kwargs={})

     為一個新事件排程。'time' 引數應該是與傳遞給建構函式的 'timefunc' 函
     式回傳值相容的數字型別。安排在相同 'time' 的事件將按照其 'priority'
     的順序執行。數字越小代表優先順序越高。

     執行事件意味著執行 ‘action(*argument, **kwargs)’。'argument' 是一個
     包含 'action' 之位置引數的序列。'kwargs' 是一個字典，帶有 'action'
     的關鍵字引數。

     回傳值是一個事件，可用於後續取消該事件（請見 *note cancel(): 1832.）
     。

     在 3.3 版的變更: 'argument' 參數是可選的。

     在 3.3 版的變更: 新增 'kwargs' 參數。

 -- 方法: scheduler.enter (delay, priority, action, argument=(),
          kwargs={})

     為一個排程事件延期 'delay' 個時間單位。除了相對時間之外，其他引數、
     效果和回傳值皆與 *note enterabs(): 10c1. 的相同。

     在 3.3 版的變更: 'argument' 參數是可選的。

     在 3.3 版的變更: 新增 'kwargs' 參數。

 -- 方法: scheduler.cancel (event)

     從佇列中刪除該事件。如果 'event' 不是目前佇列中的事件，此方法將引發
     *note ValueError: 1e7.。

 -- 方法: scheduler.empty ()

     如果事件佇列為空，則回傳 ‘True’。

 -- 方法: scheduler.run (blocking=True)

     運行所有已排程的事件。此方法將會等待（使用傳遞給建構函式的
     'delayfunc' 函式）下一個事件，然後執行它，並依此類推，直到不再有排
     程好的事件。

     如果 'blocking' 為 false，則執行最快到期的已排程事件（如存在），然
     後回傳排程器中下一個排程呼叫（如存在）的截止時間。

     'action' 或 'delayfunc' 都可能引發例外。無論哪種情況，排程器都將保
     持一致的狀態並傳遞例外。如果是由 'action' 引發例外，則後續呼叫
     *note run(): 10be. 時將不會嘗試運行該事件。

     如果一系列事件的運行時長比執行下一個事件前的可用時長 (available
     time) 更長，那麼排程器就單純會落後。不會有事件被丟棄；呼叫程式碼也
     要負責取消不再相關的事件。

     在 3.3 版的變更: 新增 'blocking' 參數。

 -- 屬性: scheduler.queue

     會按事件運行順序回傳即將發生的事件串列的唯讀屬性。每個事件都以*note
     附名元組 (named tuple): 5f4. 表示，並包含以下欄位：時間、優先順序、
     動作 (action)、引數、kwargs。


File: python.info,  Node: queue --- 同步佇列 synchronized queue 類別,  Next: contextvars --- 情境變數,  Prev: sched --- 事件排程器,  Up: 並行執行 Concurrent Execution

5.17.8 ‘queue’ -- 同步佇列 (synchronized queue) 類別
----------------------------------------------------

'原始碼：'Lib/queue.py(1)

__________________________________________________________________

*note queue: a4. module（模組）實作多生產者、多消費者佇列。在執行緒程式
設計中，必須在多執行緒之間安全地交換資訊時，特別有用。此 module 中的
*note Queue: 131c. class 實作所有必需的鎖定語義 (locking semantics)。

此 module 實作三種型別的佇列，它們僅在取出條目的順序上有所不同。在 FIFO
佇列中，先加入的任務是第一個被取出的。在 LIFO 佇列中，最近被加入的條目是
第一個被取出的（像堆疊 (stack) 一樣操作）。使用優先佇列 (priority queue)
時，條目將保持排序狀態（使用 *note heapq: 5f. module），並先取出最低值條
目。

在內部，這三種型別的佇列使用鎖 (lock) 來暫時阻塞競爭執行緒；但是，它們並
不是被設計來處理執行緒內的 reentrancy（可重入）。

此外，此 module 實作一個「簡單」的 FIFO 佇列型別 *note SimpleQueue:
b0e.，其特定的實作是以較少的功能為代價，來提供額外的保證。

*note queue: a4. module 定義了以下的 class 和例外：

 -- 類別: queue.Queue (maxsize=0)

     FIFO 佇列的建構子 (constructor)。'maxsize' 是一個整數，用於設置佇列
     中可放置的項目數的上限。一旦達到此大小，插入將會阻塞，直到佇列中的
     項目被消耗。如果 'maxsize' 小於或等於零，則佇列大小為無限。

 -- 類別: queue.LifoQueue (maxsize=0)

     LIFO 佇列的建構子。'maxsize' 是一個整數，用於設置佇列中可放置的項目
     數的上限。一旦達到此大小，插入將被鎖定，到佇列中的項目被消耗。如果
     'maxsize' 小於或等於零，則佇列大小為無限。

 -- 類別: queue.PriorityQueue (maxsize=0)

     優先佇列的建構子。'maxsize' 是一個整數，用於設置佇列中可放置的項目
     數的上限。一旦達到此大小，插入將被阻塞，直到佇列中的項目被消耗。如
     果 'maxsize' 小於或等於零，則佇列大小為無限。

     最低值的條目會最先被取出（最低值的條目是被會 ‘min(entries)’ 回傳的
     那一個）。條目的典型模式是格式為 ‘(priority_number, data)’ 的
     tuple（元組）。

     如果 'data' 元素為不可比較的，則可以將資料包裝在一個 class 中，該
     class 忽略資料項目並僅比較優先數：

          from dataclasses import dataclass, field
          from typing import Any

          @dataclass(order=True)
          class PrioritizedItem:
              priority: int
              item: Any=field(compare=False)

 -- 類別: queue.SimpleQueue

     無界的 FIFO 佇列的建構子。簡單佇列缺少任務追蹤等進階功能。

     在 3.7 版被加入.

 -- 例外: queue.Empty

     當對一個空的 *note Queue: 131c. 物件呼叫非阻塞的 (non-blocking)
     *note get(): 3077.（或 *note get_nowait(): 3078.）將引發此例外。

 -- 例外: queue.Full

     當對一個已滿的 *note Queue: 131c. 物件呼叫非阻塞的 *note put():
     3079.（或 *note put_nowait(): 307a.）將引發此例外。

 -- 例外: queue.ShutDown

     Exception raised when *note put(): 3079. or *note get(): 3077. is
     called on a *note Queue: 131c. object which has been shut down.

     在 3.13 版被加入.

* Menu:

* 佇列物件::
* SimpleQueue 物件::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/queue.py


File: python.info,  Node: 佇列物件,  Next: SimpleQueue 物件,  Up: queue --- 同步佇列 synchronized queue 類別

5.17.8.1 佇列物件
.................

佇列物件（*note Queue: 131c.、*note LifoQueue: 2133.、*note
PriorityQueue: 2134.）提供下面描述的公用 method。

 -- 方法: Queue.qsize ()

     回傳佇列的近似大小。注意，qsize() > 0 並不能保證後續的 get() 不會阻
     塞，qsize() < maxsize 也不會保證 put() 不會阻塞。

 -- 方法: Queue.empty ()

     如果佇列為空，則回傳 ‘True’，否則回傳 ‘False’。如果 empty() 回傳
     ‘True’，則不保證後續呼叫 put() 不會阻塞。同樣，如果 empty() 回傳
     ‘False’，則不保證後續呼叫 get() 不會阻塞。

 -- 方法: Queue.full ()

     如果佇列已滿，則回傳 ‘True’ ，否則回傳 ‘False’。如果 full() 回傳
     ‘True’，則不保證後續呼叫 get() 不會阻塞。同樣，如果 full() 回傳
     ‘False’，則不保證後續呼叫 put() 不會阻塞。

 -- 方法: Queue.put (item, block=True, timeout=None)

     將 'item' 放入佇列中。如果可選的 args 'block' 為 true、'timeout' 為
     ‘None’（預設值），則在必要時阻塞，直到自由槽 (free slot) 可用。如果
     'timeout' 為正數，則最多阻塞 'timeout' 秒，如果該時間內沒有可用的自
     由槽，則會引發 *note Full: 2f8b. 例外。否則（'block' 為 false），如
     果自由槽立即可用，則將項目放在佇列中，否則引發 *note Full: 2f8b. 例
     外（在這種情況下，'timeout' 將被忽略）。

     Raises *note ShutDown: 220. if the queue has been shut down.

 -- 方法: Queue.put_nowait (item)

     等效於 ‘put(item, block=False)’。

 -- 方法: Queue.get (block=True, timeout=None)

     從佇列中移除並回傳一個項目。如果可選的 args 'block' 為 true，且
     'timeout' 為 ‘None’（預設值），則在必要時阻塞，直到有可用的項目。如
     果 'timeout' 是正數，則最多會阻塞 'timeout' 秒，如果該時間內沒有可
     用的項目，則會引發 *note Empty: 2f8a. 例外。否則（'block' 為 false）
     ，如果立即可用，則回傳一個項目，否則引發 *note Empty: 2f8a. 例外（
     在這種情況下，'timeout' 將被忽略）。

     在 POSIX 系統的 3.0 版之前，以及 Windows 的所有版本，如果 'block' 為
     true 且 'timeout' 為 ‘None’，則此操作將在底層鎖上進入不間斷等待。這
     意味著不會發生例外，特別是 SIGINT（中斷訊號）不會觸發 *note
     KeyboardInterrupt: 975.。

     Raises *note ShutDown: 220. if the queue has been shut down and is
     empty, or if the queue has been shut down immediately.

 -- 方法: Queue.get_nowait ()

     等效於 ‘get(False)’。

有兩個 method 可以支援追蹤放入佇列的任務是否已由常駐消費者執行緒 (daemon
consumer threads) 完全處理。

 -- 方法: Queue.task_done ()

     表示先前放入佇列的任務已完成。由佇列消費者執行緒使用。對於用來提取
     任務的每個 *note get(): 3077.，隨後呼叫 *note task_done(): 2f86. 告
     訴佇列任務的處理已完成。

     如果目前 *note join(): 2f87. 阻塞，它將會在所有項目都已處理完畢後恢
     復（代表對於以 *note put(): 3079. 放進佇列的每個項目，都要收到
     *note task_done(): 2f86. 的呼叫）。

     ‘shutdown(immediate=True)’ calls *note task_done(): 2f86. for each
     remaining item in the queue.

     如果呼叫次數超過佇列中放置的項目數量，則引發 *note ValueError:
     1e7.。

 -- 方法: Queue.join ()

     持續阻塞直到佇列中的所有項目都已被獲取並處理完畢。

     每當項目被加到佇列中時，未完成任務的計數都會增加。每當消費者執行緒
     呼叫 *note task_done(): 2f86. 以指示該項目已被取出並且對其的所有工
     作都已完成時，計數就會下降。當未完成任務的計數降至零時，*note
     join(): 2f87. 將停止阻塞。

如何等待放入佇列的任務完成的範例：

     import threading
     import queue

     q = queue.Queue()

     def worker():
         while True:
             item = q.get()
             print(f'Working on {item}')
             print(f'Finished {item}')
             q.task_done()

     # Turn-on the worker thread.
     threading.Thread(target=worker, daemon=True).start()

     # Send thirty task requests to the worker.
     for item in range(30):
         q.put(item)

     # Block until all tasks are done.
     q.join()
     print('All work completed')

* Menu:

* Terminating queues::


File: python.info,  Node: Terminating queues,  Up: 佇列物件

5.17.8.2 Terminating queues
...........................

*note Queue: 131c. objects can be made to prevent further interaction by
shutting them down.

 -- 方法: Queue.shutdown (immediate=False)

     Shut down the queue, making *note get(): 3077. and *note put():
     3079. raise *note ShutDown: 220.

     By default, *note get(): 3077. on a shut down queue will only raise
     once the queue is empty.  Set 'immediate' to true to make *note
     get(): 3077. raise immediately instead.

     All blocked callers of *note put(): 3079. and *note get(): 3077.
     will be unblocked.  If 'immediate' is true, a task will be marked
     as done for each remaining item in the queue, which may unblock
     callers of *note join(): 2f87.

     在 3.13 版被加入.


File: python.info,  Node: SimpleQueue 物件,  Prev: 佇列物件,  Up: queue --- 同步佇列 synchronized queue 類別

5.17.8.3 SimpleQueue 物件
.........................

*note SimpleQueue: b0e. 物件提供下面描述的公用 method。

 -- 方法: SimpleQueue.qsize ()

     傳回佇列的近似大小。注意，qsize() > 0 並不能保證後續的 get() 不會阻
     塞。

 -- 方法: SimpleQueue.empty ()

     如果佇列為空，則回傳 ‘True’，否則回傳 ‘False’。如果 empty() 回傳
     ‘False’，則不保證後續呼叫 get() 不會阻塞。

 -- 方法: SimpleQueue.put (item, block=True, timeout=None)

     將 'item' 放入佇列中。此 method 從不阻塞，並且都會成功（除了潛在的
     低階錯誤，像是分配記憶體失敗）。可選的 args 'block' 和 'timeout' 會
     被忽略，它們僅是為了與 *note Queue.put(): 3079. 相容才存在。

     'CPython 實作細節：' 此 method 有一個可重入 (reentrant) 的 C 實作。
     意思就是，一個 ‘put()’ 或 ‘get()’ 呼叫，可以被同一執行緒中的另一個
     ‘put()’ 呼叫中斷，而不會造成死鎖 (deadlock) 或損壞佇列中的內部狀態
     。這使得它適合在解構子 (destructor) 中使用，像是 ‘__del__’ method 或
     *note weakref: fc. 回呼函式 (callback)。

 -- 方法: SimpleQueue.put_nowait (item)

     等效於 ‘put(item, block=False)’，用於與 *note Queue.put_nowait():
     307a. 相容。

 -- 方法: SimpleQueue.get (block=True, timeout=None)

     從佇列中移除並回傳一個項目。如果可選的 args 'block' 為 true，且
     'timeout' 為 ‘None’（預設值），則在必要時阻塞，直到有可用的項目。如
     果 'timeout' 是正數，則最多會阻塞 'timeout' 秒，如果該時間內沒有可
     用的項目，則會引發 *note Empty: 2f8a. 例外。否則（'block' 為 false）
     ，如果立即可用，則回傳一個項目，否則引發 *note Empty: 2f8a. 例外（
     在這種情況下，'timeout' 將被忽略）。

 -- 方法: SimpleQueue.get_nowait ()

     等效於 ‘get(False)’。

也參考
......

Class *note multiprocessing.Queue: 1701.

     用於多行程處理 (multi-processing)（而非多執行緒）情境 (context) 的
     佇列 class。

*note collections.deque: 580. 是無界佇列的替代實作，有快速且具原子性
(atomic) 的 *note append(): 23e4. 和 *note popleft(): 23ea. 操作，這些操
作不需要鎖定，並且還支持索引。


File: python.info,  Node: contextvars --- 情境變數,  Next: _thread --- 低階執行緒 API,  Prev: queue --- 同步佇列 synchronized queue 類別,  Up: 並行執行 Concurrent Execution

5.17.9 ‘contextvars’ -- 情境變數
--------------------------------

__________________________________________________________________

This module provides APIs to manage, store, and access context-local
state.  The *note ContextVar: 308a. class is used to declare and work
with 'Context Variables'.  The *note copy_context(): 308b. function and
the *note Context: 308c. class should be used to manage the current
context in asynchronous frameworks.

Context managers that have state should use Context Variables instead of
*note threading.local(): 166d. to prevent their state from bleeding to
other code unexpectedly, when used in concurrent code.

額外資訊請見 PEP 567(1)。

在 3.7 版被加入.

* Menu:

* Context Variables::
* Manual Context Management::
* asyncio support::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0567/


File: python.info,  Node: Context Variables,  Next: Manual Context Management,  Up: contextvars --- 情境變數

5.17.9.1 Context Variables
..........................

 -- 類別: contextvars.ContextVar (name[, *, default])

     This class is used to declare a new Context Variable, e.g.:

          var: ContextVar[int] = ContextVar('var', default=42)

     The required 'name' parameter is used for introspection and debug
     purposes.

     The optional keyword-only 'default' parameter is returned by *note
     ContextVar.get(): 308e. when no value for the variable is found in
     the current context.

     'Important:' Context Variables should be created at the top module
     level and never in closures.  *note Context: 308c. objects hold
     strong references to context variables which prevents context
     variables from being properly garbage collected.

      -- 屬性: name

          The name of the variable.  This is a read-only property.

          在 3.7.1 版被加入.

      -- 方法: get ([default])

          Return a value for the context variable for the current
          context.

          If there is no value for the variable in the current context,
          the method will:

             * return the value of the 'default' argument of the method,
               if provided; or

             * return the default value for the context variable, if it
               was created with one; or

             * raise a *note LookupError: 20a9.

      -- 方法: set (value)

          Call to set a new value for the context variable in the
          current context.

          The required 'value' argument is the new value for the context
          variable.

          Returns a *note Token: 3091. object that can be used to
          restore the variable to its previous value via the *note
          ContextVar.reset(): 3092. method.

      -- 方法: reset (token)

          Reset the context variable to the value it had before the
          *note ContextVar.set(): 3090. that created the 'token' was
          used.

          舉例來說：

               var = ContextVar('var')

               token = var.set('new value')
               # code that uses 'var'; var.get() returns 'new value'.
               var.reset(token)

               # After the reset call the var has no value again, so
               # var.get() would raise a LookupError.

 -- 類別: contextvars.Token

     'Token' objects are returned by the *note ContextVar.set(): 3090.
     method.  They can be passed to the *note ContextVar.reset(): 3092.
     method to revert the value of the variable to what it was before
     the corresponding 'set'.

      -- 屬性: var

          A read-only property.  Points to the *note ContextVar: 308a.
          object that created the token.

      -- 屬性: old_value

          A read-only property.  Set to the value the variable had
          before the *note ContextVar.set(): 3090. method call that
          created the token.  It points to *note Token.MISSING: 3095. if
          the variable was not set before the call.

      -- 屬性: MISSING

          A marker object used by *note Token.old_value: 3094.


File: python.info,  Node: Manual Context Management,  Next: asyncio support,  Prev: Context Variables,  Up: contextvars --- 情境變數

5.17.9.2 Manual Context Management
..................................

 -- 函式: contextvars.copy_context ()

     Returns a copy of the current *note Context: 308c. object.

     The following snippet gets a copy of the current context and prints
     all variables and their values that are set in it:

          ctx: Context = copy_context()
          print(list(ctx.items()))

     The function has an 'O'(1) complexity, i.e.  works equally fast for
     contexts with a few context variables and for contexts that have a
     lot of them.

 -- 類別: contextvars.Context

     A mapping of *note ContextVars: 308a. to their values.

     ‘Context()’ creates an empty context with no values in it.  To get
     a copy of the current context use the *note copy_context(): 308b.
     function.

     Every thread will have a different top-level *note Context: 308c.
     object.  This means that a *note ContextVar: 308a. object behaves
     in a similar fashion to *note threading.local(): 166d. when values
     are assigned in different threads.

     Context implements the *note collections.abc.Mapping: 86f.
     interface.

      -- 方法: run (callable, *args, **kwargs)

          Execute ‘callable(*args, **kwargs)’ code in the context object
          the 'run' method is called on.  Return the result of the
          execution or propagate an exception if one occurred.

          Any changes to any context variables that 'callable' makes
          will be contained in the context object:

               var = ContextVar('var')
               var.set('spam')

               def main():
                   # 'var' was set to 'spam' before
                   # calling 'copy_context()' and 'ctx.run(main)', so:
                   # var.get() == ctx[var] == 'spam'

                   var.set('ham')

                   # Now, after setting 'var' to 'ham':
                   # var.get() == ctx[var] == 'ham'

               ctx = copy_context()

               # Any changes that the 'main' function makes to 'var'
               # will be contained in 'ctx'.
               ctx.run(main)

               # The 'main()' function was run in the 'ctx' context,
               # so changes to 'var' are contained in it:
               # ctx[var] == 'ham'

               # However, outside of 'ctx', 'var' is still set to 'spam':
               # var.get() == 'spam'

          The method raises a *note RuntimeError: 179. when called on
          the same context object from more than one OS thread, or when
          called recursively.

      -- 方法: copy ()

          Return a shallow copy of the context object.

      -- Describe: var in context

          Return ‘True’ if the 'context' has a value for 'var' set;
          return ‘False’ otherwise.

      -- Describe: context[var]

          Return the value of the 'var' *note ContextVar: 308a.
          variable.  If the variable is not set in the context object, a
          *note KeyError: 2fb. is raised.

      -- 方法: get (var[, default])

          Return the value for 'var' if 'var' has the value in the
          context object.  Return 'default' otherwise.  If 'default' is
          not given, return ‘None’.

      -- Describe: iter(context)

          Return an iterator over the variables stored in the context
          object.

      -- Describe: len(proxy)

          Return the number of variables set in the context object.

      -- 方法: keys ()

          Return a list of all variables in the context object.

      -- 方法: values ()

          Return a list of all variables' values in the context object.

      -- 方法: items ()

          Return a list of 2-tuples containing all variables and their
          values in the context object.


File: python.info,  Node: asyncio support,  Prev: Manual Context Management,  Up: contextvars --- 情境變數

5.17.9.3 asyncio support
........................

Context variables are natively supported in *note asyncio: 8. and are
ready to be used without any extra configuration.  For example, here is
a simple echo server, that uses a context variable to make the address
of a remote client available in the Task that handles that client:

     import asyncio
     import contextvars

     client_addr_var = contextvars.ContextVar('client_addr')

     def render_goodbye():
         # The address of the currently handled client can be accessed
         # without passing it explicitly to this function.

         client_addr = client_addr_var.get()
         return f'Good bye, client @ {client_addr}\n'.encode()

     async def handle_request(reader, writer):
         addr = writer.transport.get_extra_info('socket').getpeername()
         client_addr_var.set(addr)

         # In any code that we call is now possible to get
         # client's address by calling 'client_addr_var.get()'.

         while True:
             line = await reader.readline()
             print(line)
             if not line.strip():
                 break
             writer.write(line)

         writer.write(render_goodbye())
         writer.close()

     async def main():
         srv = await asyncio.start_server(
             handle_request, '127.0.0.1', 8081)

         async with srv:
             await srv.serve_forever()

     asyncio.run(main())

     # To test it you can use telnet:
     #     telnet 127.0.0.1 8081

以下是支援部份上述服務的模組：


File: python.info,  Node: _thread --- 低階執行緒 API,  Prev: contextvars --- 情境變數,  Up: 並行執行 Concurrent Execution

5.17.10 ‘_thread’ -- 低階執行緒 API
-----------------------------------

__________________________________________________________________

這個模組提供了與多個執行緒（也稱為:dfn:‘輕量級行程’ 或 :dfn: ‘任務’）一
起工作的低階原始物件 -- 多個控制執行緒分享其全域資料空間。為了處理同步問
題，也提供了簡單的鎖 (lock) 機制（也稱為:dfn:‘互斥鎖’ 或 '二進位號誌'）
。 *note threading: d6. 模組提供了一個建立在這個模組之上的更易於使用和高
階的執行緒 API。

在 3.7 版的變更: 這個模組之前是可選擇性的，但現在已經是可用的。

這個模組定義了以下的常數和函式：

 -- 例外: _thread.error

     在執行緒相關的錯誤發生時引發。

     在 3.3 版的變更: 現在是內建例外 *note RuntimeError: 179. 的別名。

 -- 資料: _thread.LockType

     這是鎖物件的型別。

 -- 函式: _thread.start_new_thread (function, args[, kwargs])

     開始一個新的執行緒並回傳其識別字 (identifier) 。該執行緒執行帶有引
     數列表 'args*（必須是一個 tuple（元組））的函式 *function'。可選的
     'kwargs' 引數指定一個關鍵字引數的字典。

     當函式回傳時，執行緒會靜默退出。

     當函式因未處理的例外終止時，將呼叫 *note sys.unraisablehook(): 1dc.
     來處理該例外。鉤子引數的 'object' 屬性是 'function'。預設情況下，會
     列印堆疊跟蹤，然後執行緒退出（但其他執行緒會繼續運行）。

     當函式引發 *note SystemExit: ce7. 例外時，它會被靜默忽略。

     引發一個 *note 稽核事件: 17bd. ‘_thread.start_new_thread’，帶有引數
     ‘function’、‘args’ 和 ‘kwargs’。

     在 3.8 版的變更: 現在使用 *note sys.unraisablehook(): 1dc. 來處理未
     處理的例外。

 -- 函式: _thread.interrupt_main (signum=signal.SIGINT, /)

     模擬一個訊號到達主執行緒的效果。執行緒可以使用此函式來中斷主執行緒
     ，但無法保證中斷會立即發生。

     如果提供了 'signum'，則模擬指定的訊號編號。如果未提供 'signum'，則
     模擬 *note signal.SIGINT: 7e8. 訊號。

     如果給定的訊號在 Python 中未被處理（即設置為 *note signal.SIG_DFL:
     1726. 或 *note signal.SIG_IGN: 1725.），此函式不做任何操作。

     在 3.10 版的變更: 新增了 'signum' 引數以自定義訊號編號。

          備註: 這並不會發出對應的訊號，而是安排呼叫相應的處理器（如果存
          在的話）。如果你想真正發出訊號，請使用 *note
          signal.raise_signal(): 1707.。

 -- 函式: _thread.exit ()

     引發 *note SystemExit: ce7. 例外。當未捕獲時，將導致執行緒靜默退出
     。

 -- 函式: _thread.allocate_lock ()

     回傳一個新的鎖物件。鎖物件的方法如下所述。初始狀況下鎖是解鎖狀態。

 -- 函式: _thread.get_ident ()

     回傳當前執行緒的「執行緒識別字」。這是一個非零的整數。它的值沒有直
     接的含義；它被用作一個 magic cookie，例如用於索引特定於執行緒的資料
     的字典。當執行緒退出並建立另一個執行緒時，執行緒識別字可能會被重複
     使用。

 -- 函式: _thread.get_native_id ()

     回傳由核心 (kernel) 分配的當前執行緒的原生整數執行緒 ID。這是一個非
     負整數。它的值可用於在整個系統中唯一標識此特定執行緒（直到執行緒終
     止後，該值可能被操作系統重新使用）。

     *note Availability: 1c56.: Windows, FreeBSD, Linux, macOS, OpenBSD,
     NetBSD, AIX, DragonFlyBSD, GNU/kFreeBSD.

     在 3.8 版被加入.

     在 3.13 版的變更: Added support for GNU/kFreeBSD.

 -- 函式: _thread.stack_size ([size])

     回傳在建立新執行緒時使用的執行緒堆疊大小。可選的 'size' 引數指定了
     隨後建立的執行緒要使用的堆疊大小，必須是 0（使用平台或配置的預設值
     ）或至少 32,768（32 KiB）的正整數值。如果未指定 'size'，則使用 0。
     如果不支持更改執行緒堆疊大小，則會引發 *note RuntimeError: 179. 錯
     誤。如果指定的堆疊大小無效，則會引發 *note ValueError: 1e7. 錯誤，
     並且堆疊大小不會被修改。目前，32 KiB 是保證解譯器本身具有足夠堆疊空
     間所支持的最小堆疊大小值。請注意，某些平台對於堆疊大小的值可能有特
     定的限制，例如要求最小堆疊大小 > 32 KiB，或要求按系統記憶體頁面大小
     的倍數進行分配。應參考平台文檔以獲取更多訊息（4 KiB 頁面是比較普遍
     的；在缺乏更具體訊息的情況下，建議使用 4096 的倍數作為堆疊大小）。

     *note 適用: 1c56.：Windows, pthreads。

     Unix 平台上支援 POSIX 執行緒。

 -- 資料: _thread.TIMEOUT_MAX

     *note Lock.acquire: 63e. 的 'timeout' 參數所允許的最大值。指定超過
     此值的 timeout 將引發 *note OverflowError: 825. 錯誤。

     在 3.2 版被加入.

鎖物件具有以下方法：

 -- 方法: lock.acquire (blocking=True, timeout=-1)

     沒有任何可選引數時，此方法無條件地獲取鎖，必要時會等待直到被另一個
     執行緒釋放（一次只能有一個執行緒獲取鎖 -- 這正是鎖存在的原因）。

     如果存在 'blocking' 引數，則根據其值執行操作：如果為 False，只有在
     可以立即獲取鎖而無需等待的情況下才獲取鎖，而如果為 True，則像上面一
     樣無條件地獲取鎖。

     如果存在浮點數的 'timeout' 引數且為正值，則它指定了在回傳之前的最大
     等待時間（以秒為單位）。如果 'timeout' 引數為負值，則表示等待時間會
     無限期地等待。如果 'blocking' 為 False，則你無法指定 'timeout'。

     如果成功獲取鎖，回傳值為 ‘True’，否則為 ‘False’。

     在 3.2 版的變更: 新增的 'timeout' 參數。

     在 3.2 版的變更: 現在獲取鎖的操作可以被 POSIX 訊號中斷。

 -- 方法: lock.release ()

     釋放鎖。鎖必須先前被獲取，但不一定是由同一個執行緒獲取的。

 -- 方法: lock.locked ()

     回傳鎖的狀態：如果鎖已被某個執行緒獲取，則回傳 ‘True’，否則回傳
     ‘False’。

除了這些方法之外，鎖物件還可以透過 *note with: 577. 語句來使用，例如：

     import _thread

     a_lock = _thread.allocate_lock()

     with a_lock:
         print("a_lock is locked while this executes")

'注意事項：'

   * 執行緒與中斷的互動可能會有奇怪的情況：任何一個執行緒都有可能收到
     *note KeyboardInterrupt: 975. 例外。（當 *note signal: b4. 模組可用
     時，中斷總是會進入主執行緒。）

   * 呼叫 *note sys.exit(): 12dd. 函數或引發 *note SystemExit: ce7. 例外
     等同於呼叫 *note _thread.exit(): 30a1. 函式。

   * 無法在鎖的 *note acquire(): 63e. 方法上中斷執行， *note
     KeyboardInterrupt: 975. 例外會在鎖被獲取後發生。

   * 當主執行緒退出時，其他執行緒是否保留是由系統決定的。在大多數系統上
     ，它們將被終止，而不會執行 *note try: 68c. ...  *note finally: 96e.
     子句或執行物件的解構函式。

   * 當主執行緒退出時，它不會執行任何通常的清理操作（除非有 *note try:
     68c. ...  *note finally: 96e. 子句），並且標準 I/O 檔案不會被刷新。


File: python.info,  Node: Networking and Interprocess Communication,  Next: 網際網路資料處理,  Prev: 並行執行 Concurrent Execution,  Up: Python 標準函式庫 Standard Library

5.18 Networking and Interprocess Communication
==============================================

The modules described in this chapter provide mechanisms for networking
and inter-processes communication.

Some modules only work for two processes that are on the same machine,
e.g.  *note signal: b4. and *note mmap: 83.  Other modules support
networking protocols that two or more processes can use to communicate
across machines.

The list of modules described in this chapter is:

* Menu:

* asyncio: asyncio --- 非同步 I/O. 非同步 I/O
* socket: socket --- 低階網路介面. 低階網路介面
* ssl: ssl --- socket 物件的 TLS/SSL 包裝器. socket 物件的 TLS/SSL 包裝器
* select: select --- 等待 I/O 完成. 等待 I/O 完成
* selectors: selectors --- 高階 I/O 多工. 高階 I/O 多工
* signal: signal --- 設定非同步事件的處理函式. 設定非同步事件的處理函式
* mmap: mmap --- 記憶體映射檔案的支援. 記憶體映射檔案的支援


File: python.info,  Node: asyncio --- 非同步 I/O,  Next: socket --- 低階網路介面,  Up: Networking and Interprocess Communication

5.18.1 ‘asyncio’ -- 非同步 I/O
------------------------------

__________________________________________________________________

Hello World!
............

     import asyncio

     async def main():
         print('Hello ...')
         await asyncio.sleep(1)
         print('... World!')

     asyncio.run(main())

asyncio 是讓使用者以 'async/await' 語法來編寫'並行 (concurrent)' 程式碼
的函式庫 (library)。

asyncio 作為多個 Python 非同步框架的基礎，在高效能網路與網頁伺服器、資料
庫連線函式庫、分散式任務佇列等服務都可以看得到它。

asyncio 往往是個建構 IO 密集型與高階層'結構化'網路程式碼的完美選擇。

asyncio 提供了一系列'高階' API：

   * 並行地*note 運行 Python 協程 (coroutine): 30af. 並擁有完整控制權；

   * 執行*note 網路 IO 與 IPC: 30b0.；

   * 控制*note 子行程 (subprocess): 30b1.；

   * 透過*note 佇列 (queue): 30b2. 分配任務；

   * *note 同步: 30b3.並行程式碼；

此外，還有一些給'函式庫與框架 (framework) 開發者'的'低階' API：

   * 建立與管理 *note event loops（事件迴圈）: d1f.，它提供了能被用於
     *note 網路: 30b4.、執行*note 子行程: 30b5.、處理*note 作業系統訊號:
     30b6.等任務的非同步 API；

   * 使用 *note transports（asyncio 底層傳輸相關類別）: 30b7.來實作高效
     能協定；

   * 透過 async/await 語法來*note 橋接: 30b8.基於回呼 (callback-based) 的
     函式庫與程式碼。

*note Availability: 1c56.: not WASI.

This module does not work or is not available on WebAssembly.  See *note
WebAssembly 平台: 16e6. for more information.

asyncio REPL
............

You can experiment with an ‘asyncio’ concurrent context in the *note
REPL: 14e.:

     $ python -m asyncio
     asyncio REPL ...
     Use "await" directly instead of "asyncio.run()".
     Type "help", "copyright", "credits" or "license" for more information.
     >>> import asyncio
     >>> await asyncio.sleep(10, result='hello')
     'hello'

Raises an *note auditing event: 17bd. ‘cpython.run_stdin’ with no
arguments.

在 3.12.5 版的變更: (also 3.11.10, 3.10.15, 3.9.20, and 3.8.20) Emits
audit events.

在 3.13 版的變更: Uses PyREPL if possible, in which case *note
PYTHONSTARTUP: f6b. is also executed.  Emits audit events.

參閱
....

* Menu:

* Runners (執行器): Runners 執行器.
* 協程與任務::
* 串流::
* 同步化原始物件 (Synchronization Primitives): 同步化原始物件 Synchronization Primitives.
* 子行程::
* 佇列 (Queues): 佇列 Queues.
* 例外: 例外<8>.
* 事件迴圈::
* Futures::
* 傳輸與協定::
* Policies::
* 平臺支援::
* 擴充::
* 高階 API 索引::
* 低階 API 索引::
* 使用 asyncio 開發::


File: python.info,  Node: Runners 執行器,  Next: 協程與任務,  Up: asyncio --- 非同步 I/O

5.18.1.1 Runners (執行器)
.........................

'原始碼：'Lib/asyncio/runners.py(1)

這個章節概述用於執行 asyncio 程式碼的高階 asyncio 原始物件。

他們是基於一個*note 事件迴圈: d1f.，目的是為了簡化常見且廣泛運用場景的非
同步程式碼。

* Menu:

* 運行一個 asyncio 程式::
* Runner context manager::
* Handling Keyboard Interruption::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/asyncio/runners.py


File: python.info,  Node: 運行一個 asyncio 程式,  Next: Runner context manager,  Up: Runners 執行器

5.18.1.2 運行一個 asyncio 程式
..............................

 -- 函式: asyncio.run (coro, *, debug=None, loop_factory=None)

     執行*note 協程 (coroutine): 438. 'coro' 並回傳結果。

     這個函式負責運行被傳入的協程、管理 asyncio 的事件迴圈、'終結非同步
     產生器'，以及關閉執行器。

     當另一個非同步事件迴圈在同一執行緒中執行時，無法呼叫此函式。

     如果 'debug' 為 ‘True’，事件迴圈會以除錯模式執行。‘False’ 則會關閉
     除錯模式。‘None’ 則會優先使用*note 除錯模式: 1c51.的全域設定。

     If 'loop_factory' is not ‘None’, it is used to create a new event
     loop; otherwise *note asyncio.new_event_loop(): 30bd. is used.  The
     loop is closed at the end.  This function should be used as a main
     entry point for asyncio programs, and should ideally only be called
     once.  It is recommended to use 'loop_factory' to configure the
     event loop instead of policies.  Passing *note asyncio.EventLoop:
     15f1. allows running asyncio without the policy system.

     The executor is given a timeout duration of 5 minutes to shutdown.
     If the executor hasn't finished within that duration, a warning is
     emitted and the executor is closed.

     範例：

          async def main():
              await asyncio.sleep(1)
              print('hello')

          asyncio.run(main())

     在 3.7 版被加入.

     在 3.9 版的變更: Updated to use *note
     loop.shutdown_default_executor(): 88c.

     在 3.10 版的變更: 'debug' is ‘None’ by default to respect the
     global debug mode settings.

     在 3.12 版的變更: 新增 'loop_factory' 參數。


File: python.info,  Node: Runner context manager,  Next: Handling Keyboard Interruption,  Prev: 運行一個 asyncio 程式,  Up: Runners 執行器

5.18.1.3 Runner context manager
...............................

 -- 類別: asyncio.Runner (*, debug=None, loop_factory=None)

     A context manager that simplifies 'multiple' async function calls
     in the same context.

     Sometimes several top-level async functions should be called in the
     same *note event loop: d1f. and *note contextvars.Context: 308c.

     如果 'debug' 為 ‘True’，事件迴圈會以除錯模式執行。‘False’ 則會關閉
     除錯模式。‘None’ 則會優先使用*note 除錯模式: 1c51.的全域設定。

     'loop_factory' could be used for overriding the loop creation.  It
     is the responsibility of the 'loop_factory' to set the created loop
     as the current one.  By default *note asyncio.new_event_loop():
     30bd. is used and set as current event loop with *note
     asyncio.set_event_loop(): 16cf. if 'loop_factory' is ‘None’.

     Basically, *note asyncio.run(): 423. example can be rewritten with
     the runner usage:

          async def main():
              await asyncio.sleep(1)
              print('hello')

          with asyncio.Runner() as runner:
              runner.run(main())

     在 3.11 版被加入.

      -- 方法: run (coro, *, context=None)

          Run a *note coroutine: 438. 'coro' in the embedded loop.

          Return the coroutine's result or raise its exception.

          An optional keyword-only 'context' argument allows specifying
          a custom *note contextvars.Context: 308c. for the 'coro' to
          run in.  The runner's default context is used if ‘None’.

          當另一個非同步事件迴圈在同一執行緒中執行時，無法呼叫此函式。

      -- 方法: close ()

          Close the runner.

          Finalize asynchronous generators, shutdown default executor,
          close the event loop and release embedded *note
          contextvars.Context: 308c.

      -- 方法: get_loop ()

          Return the event loop associated with the runner instance.

          備註: *note Runner: 5a5. uses the lazy initialization
          strategy, its constructor doesn't initialize underlying
          low-level structures.

          Embedded 'loop' and 'context' are created at the *note with:
          577. body entering or the first call of *note run(): 423. or
          *note get_loop(): 30c0.


File: python.info,  Node: Handling Keyboard Interruption,  Prev: Runner context manager,  Up: Runners 執行器

5.18.1.4 Handling Keyboard Interruption
.......................................

在 3.11 版被加入.

When *note signal.SIGINT: 7e8. is raised by ‘Ctrl-C’, *note
KeyboardInterrupt: 975. exception is raised in the main thread by
default.  However this doesn't work with *note asyncio: 8. because it
can interrupt asyncio internals and can hang the program from exiting.

To mitigate this issue, *note asyncio: 8. handles *note signal.SIGINT:
7e8. as follows:

  1. *note asyncio.Runner.run(): 15a5. installs a custom *note
     signal.SIGINT: 7e8. handler before any user code is executed and
     removes it when exiting from the function.

  2. The *note Runner: 5a5. creates the main task for the passed
     coroutine for its execution.

  3. When *note signal.SIGINT: 7e8. is raised by ‘Ctrl-C’, the custom
     signal handler cancels the main task by calling *note
     asyncio.Task.cancel(): 19d. which raises *note
     asyncio.CancelledError: 19e. inside the main task.  This causes the
     Python stack to unwind, ‘try/except’ and ‘try/finally’ blocks can
     be used for resource cleanup.  After the main task is cancelled,
     *note asyncio.Runner.run(): 15a5. raises *note KeyboardInterrupt:
     975.

  4. A user could write a tight loop which cannot be interrupted by
     *note asyncio.Task.cancel(): 19d, in which case the second
     following ‘Ctrl-C’ immediately raises the *note KeyboardInterrupt:
     975. without cancelling the main task.


File: python.info,  Node: 協程與任務,  Next: 串流,  Prev: Runners 執行器,  Up: asyncio --- 非同步 I/O

5.18.1.5 協程與任務
...................

This section outlines high-level asyncio APIs to work with coroutines
and Tasks.

* Menu:

* 協程: 協程<3>.
* Awaitables::
* Creating Tasks::
* Task Cancellation::
* Task Groups::
* Sleeping::
* Running Tasks Concurrently::
* Eager Task Factory::
* Shielding From Cancellation::
* Timeouts::
* Waiting Primitives::
* Running in Threads::
* Scheduling From Other Threads::
* Introspection::
* Task Object::


File: python.info,  Node: 協程<3>,  Next: Awaitables,  Up: 協程與任務

5.18.1.6 協程
.............

'原始碼：'Lib/asyncio/coroutines.py(1)

__________________________________________________________________

*note Coroutines: 438. declared with the async/await syntax is the
preferred way of writing asyncio applications.  For example, the
following snippet of code prints "hello", waits 1 second, and then
prints "world":

     >>> import asyncio

     >>> async def main():
     ...     print('hello')
     ...     await asyncio.sleep(1)
     ...     print('world')

     >>> asyncio.run(main())
     hello
     world

Note that simply calling a coroutine will not schedule it to be
executed:

     >>> main()
     <coroutine object main at 0x1053bb7c8>

To actually run a coroutine, asyncio provides the following mechanisms:

   * The *note asyncio.run(): 423. function to run the top-level entry
     point "main()" function (see the above example.)

   * Awaiting on a coroutine.  The following snippet of code will print
     "hello" after waiting for 1 second, and then print "world" after
     waiting for 'another' 2 seconds:

          import asyncio
          import time

          async def say_after(delay, what):
              await asyncio.sleep(delay)
              print(what)

          async def main():
              print(f"started at {time.strftime('%X')}")

              await say_after(1, 'hello')
              await say_after(2, 'world')

              print(f"finished at {time.strftime('%X')}")

          asyncio.run(main())

     預期的輸出：

          started at 17:13:52
          hello
          world
          finished at 17:13:55

   * The *note asyncio.create_task(): 5a1. function to run coroutines
     concurrently as asyncio *note Tasks: 480.

     Let's modify the above example and run two ‘say_after’ coroutines
     'concurrently':

          async def main():
              task1 = asyncio.create_task(
                  say_after(1, 'hello'))

              task2 = asyncio.create_task(
                  say_after(2, 'world'))

              print(f"started at {time.strftime('%X')}")

              # Wait until both tasks are completed (should take
              # around 2 seconds.)
              await task1
              await task2

              print(f"finished at {time.strftime('%X')}")

     Note that expected output now shows that the snippet runs 1 second
     faster than before:

          started at 17:14:32
          hello
          world
          finished at 17:14:34

   * The *note asyncio.TaskGroup: 19b. class provides a more modern
     alternative to *note create_task(): 5a1.  Using this API, the last
     example becomes:

          async def main():
              async with asyncio.TaskGroup() as tg:
                  task1 = tg.create_task(
                      say_after(1, 'hello'))

                  task2 = tg.create_task(
                      say_after(2, 'world'))

                  print(f"started at {time.strftime('%X')}")

              # The await is implicit when the context manager exits.

              print(f"finished at {time.strftime('%X')}")

     The timing and output should be the same as for the previous
     version.

     在 3.11 版被加入: *note asyncio.TaskGroup: 19b.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/asyncio/coroutines.py


File: python.info,  Node: Awaitables,  Next: Creating Tasks,  Prev: 協程<3>,  Up: 協程與任務

5.18.1.7 Awaitables
...................

We say that an object is an 'awaitable' object if it can be used in an
*note await: 19f. expression.  Many asyncio APIs are designed to accept
awaitables.

There are three main types of 'awaitable' objects: 'coroutines',
'Tasks', and 'Futures'.

協程
....

Python coroutines are 'awaitables' and therefore can be awaited from
other coroutines:

     import asyncio

     async def nested():
         return 42

     async def main():
         # Nothing happens if we just call "nested()".
         # A coroutine object is created but not awaited,
         # so it *won't run at all*.
         nested()

         # Let's do it differently now and await it:
         print(await nested())  # will print "42".

     asyncio.run(main())

     重要: In this documentation the term "coroutine" can be used for
     two closely related concepts:

        * a 'coroutine function': an *note async def: 575. function;

        * a 'coroutine object': an object returned by calling a
          'coroutine function'.

Tasks
.....

'Tasks' are used to schedule coroutines 'concurrently'.

When a coroutine is wrapped into a 'Task' with functions like *note
asyncio.create_task(): 5a1. the coroutine is automatically scheduled to
run soon:

     import asyncio

     async def nested():
         return 42

     async def main():
         # Schedule nested() to run soon concurrently
         # with "main()".
         task = asyncio.create_task(nested())

         # "task" can now be used to cancel "nested()", or
         # can simply be awaited to wait until it is complete:
         await task

     asyncio.run(main())

Futures
.......

A *note Future: b74. is a special 'low-level' awaitable object that
represents an 'eventual result' of an asynchronous operation.

When a Future object is 'awaited' it means that the coroutine will wait
until the Future is resolved in some other place.

Future objects in asyncio are needed to allow callback-based code to be
used with async/await.

Normally 'there is no need' to create Future objects at the application
level code.

Future objects, sometimes exposed by libraries and some asyncio APIs,
can be awaited:

     async def main():
         await function_that_returns_a_future_object()

         # this is also valid:
         await asyncio.gather(
             function_that_returns_a_future_object(),
             some_python_coroutine()
         )

A good example of a low-level function that returns a Future object is
*note loop.run_in_executor(): 88e.


File: python.info,  Node: Creating Tasks,  Next: Task Cancellation,  Prev: Awaitables,  Up: 協程與任務

5.18.1.8 Creating Tasks
.......................

'原始碼：'Lib/asyncio/tasks.py(1)

__________________________________________________________________

 -- 函式: asyncio.create_task (coro, *, name=None, context=None)

     Wrap the 'coro' *note coroutine: 30af. into a *note Task: 480. and
     schedule its execution.  Return the Task object.

     If 'name' is not ‘None’, it is set as the name of the task using
     *note Task.set_name(): 981.

     An optional keyword-only 'context' argument allows specifying a
     custom *note contextvars.Context: 308c. for the 'coro' to run in.
     The current context copy is created when no 'context' is provided.

     The task is executed in the loop returned by *note
     get_running_loop(): aae, *note RuntimeError: 179. is raised if
     there is no running loop in current thread.

          備註: *note asyncio.TaskGroup.create_task(): 1a2. is a new
          alternative leveraging structural concurrency; it allows for
          waiting for a group of related tasks with strong safety
          guarantees.

          重要: Save a reference to the result of this function, to
          avoid a task disappearing mid-execution.  The event loop only
          keeps weak references to tasks.  A task that isn't referenced
          elsewhere may get garbage collected at any time, even before
          it's done.  For reliable "fire-and-forget" background tasks,
          gather them in a collection:

               background_tasks = set()

               for i in range(10):
                   task = asyncio.create_task(some_coro(param=i))

                   # Add task to the set. This creates a strong reference.
                   background_tasks.add(task)

                   # To prevent keeping references to finished tasks forever,
                   # make each task remove its own reference from the set after
                   # completion:
                   task.add_done_callback(background_tasks.discard)

     在 3.7 版被加入.

     在 3.8 版的變更: 新增 'name' 參數。

     在 3.11 版的變更: 新增 'context' 參數。

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/asyncio/tasks.py


File: python.info,  Node: Task Cancellation,  Next: Task Groups,  Prev: Creating Tasks,  Up: 協程與任務

5.18.1.9 Task Cancellation
..........................

Tasks can easily and safely be cancelled.  When a task is cancelled,
*note asyncio.CancelledError: 19e. will be raised in the task at the
next opportunity.

It is recommended that coroutines use ‘try/finally’ blocks to robustly
perform clean-up logic.  In case *note asyncio.CancelledError: 19e. is
explicitly caught, it should generally be propagated when clean-up is
complete.  *note asyncio.CancelledError: 19e. directly subclasses *note
BaseException: 55f. so most code will not need to be aware of it.

The asyncio components that enable structured concurrency, like *note
asyncio.TaskGroup: 19b. and *note asyncio.timeout(): 5a3, are
implemented using cancellation internally and might misbehave if a
coroutine swallows *note asyncio.CancelledError: 19e.  Similarly, user
code should not generally call *note uncancel: 1a1.  However, in cases
when suppressing *note asyncio.CancelledError: 19e. is truly desired, it
is necessary to also call ‘uncancel()’ to completely remove the
cancellation state.


File: python.info,  Node: Task Groups,  Next: Sleeping,  Prev: Task Cancellation,  Up: 協程與任務

5.18.1.10 Task Groups
.....................

Task groups combine a task creation API with a convenient and reliable
way to wait for all tasks in the group to finish.

 -- 類別: asyncio.TaskGroup

     An *note asynchronous context manager: 5a0. holding a group of
     tasks.  Tasks can be added to the group using *note create_task():
     5a1.  All tasks are awaited when the context manager exits.

     在 3.11 版被加入.

      -- 方法: create_task (coro, *, name=None, context=None)

          Create a task in this task group.  The signature matches that
          of *note asyncio.create_task(): 5a1.  If the task group is
          inactive (e.g.  not yet entered, already finished, or in the
          process of shutting down), we will close the given ‘coro’.

          在 3.13 版的變更: Close the given coroutine if the task group
          is not active.

範例：

     async def main():
         async with asyncio.TaskGroup() as tg:
             task1 = tg.create_task(some_coro(...))
             task2 = tg.create_task(another_coro(...))
         print(f"Both tasks have completed now: {task1.result()}, {task2.result()}")

The ‘async with’ statement will wait for all tasks in the group to
finish.  While waiting, new tasks may still be added to the group (for
example, by passing ‘tg’ into one of the coroutines and calling
‘tg.create_task()’ in that coroutine).  Once the last task has finished
and the ‘async with’ block is exited, no new tasks may be added to the
group.

The first time any of the tasks belonging to the group fails with an
exception other than *note asyncio.CancelledError: 19e, the remaining
tasks in the group are cancelled.  No further tasks can then be added to
the group.  At this point, if the body of the ‘async with’ statement is
still active (i.e., *note __aexit__(): 151e. hasn't been called yet),
the task directly containing the ‘async with’ statement is also
cancelled.  The resulting *note asyncio.CancelledError: 19e. will
interrupt an ‘await’, but it will not bubble out of the containing
‘async with’ statement.

Once all tasks have finished, if any tasks have failed with an exception
other than *note asyncio.CancelledError: 19e, those exceptions are
combined in an *note ExceptionGroup: 19c. or *note BaseExceptionGroup:
244. (as appropriate; see their documentation) which is then raised.

Two base exceptions are treated specially: If any task fails with *note
KeyboardInterrupt: 975. or *note SystemExit: ce7, the task group still
cancels the remaining tasks and waits for them, but then the initial
*note KeyboardInterrupt: 975. or *note SystemExit: ce7. is re-raised
instead of *note ExceptionGroup: 19c. or *note BaseExceptionGroup: 244.

If the body of the ‘async with’ statement exits with an exception (so
*note __aexit__(): 151e. is called with an exception set), this is
treated the same as if one of the tasks failed: the remaining tasks are
cancelled and then waited for, and non-cancellation exceptions are
grouped into an exception group and raised.  The exception passed into
*note __aexit__(): 151e, unless it is *note asyncio.CancelledError: 19e,
is also included in the exception group.  The same special case is made
for *note KeyboardInterrupt: 975. and *note SystemExit: ce7. as in the
previous paragraph.

Task groups are careful not to mix up the internal cancellation used to
"wake up" their *note __aexit__(): 151e. with cancellation requests for
the task in which they are running made by other parties.  In
particular, when one task group is syntactically nested in another, and
both experience an exception in one of their child tasks simultaneously,
the inner task group will process its exceptions, and then the outer
task group will receive another cancellation and process its own
exceptions.

In the case where a task group is cancelled externally and also must
raise an *note ExceptionGroup: 19c, it will call the parent task's *note
cancel(): 19d. method.  This ensures that a *note
asyncio.CancelledError: 19e. will be raised at the next *note await:
19f, so the cancellation is not lost.

Task groups preserve the cancellation count reported by *note
asyncio.Task.cancelling(): 1a0.

在 3.13 版的變更: Improved handling of simultaneous internal and
external cancellations and correct preservation of cancellation counts.


File: python.info,  Node: Sleeping,  Next: Running Tasks Concurrently,  Prev: Task Groups,  Up: 協程與任務

5.18.1.11 Sleeping
..................

 -- 函式: coroutine asyncio.sleep (delay, result=None)

     Block for 'delay' seconds.

     If 'result' is provided, it is returned to the caller when the
     coroutine completes.

     ‘sleep()’ always suspends the current task, allowing other tasks to
     run.

     Setting the delay to 0 provides an optimized path to allow other
     tasks to run.  This can be used by long-running functions to avoid
     blocking the event loop for the full duration of the function call.
     Example of coroutine displaying the current date every second for 5
     seconds:

          import asyncio
          import datetime

          async def display_date():
              loop = asyncio.get_running_loop()
              end_time = loop.time() + 5.0
              while True:
                  print(datetime.datetime.now())
                  if (loop.time() + 1.0) >= end_time:
                      break
                  await asyncio.sleep(1)

          asyncio.run(display_date())

     在 3.10 版的變更: 移除 'loop' 參數。

     在 3.13 版的變更: Raises *note ValueError: 1e7. if 'delay' is *note
     nan: 609.


File: python.info,  Node: Running Tasks Concurrently,  Next: Eager Task Factory,  Prev: Sleeping,  Up: 協程與任務

5.18.1.12 Running Tasks Concurrently
....................................

 -- 函式: awaitable asyncio.gather (*aws, return_exceptions=False)

     Run *note awaitable objects: 30c5. in the 'aws' sequence
     'concurrently'.

     If any awaitable in 'aws' is a coroutine, it is automatically
     scheduled as a Task.

     If all awaitables are completed successfully, the result is an
     aggregate list of returned values.  The order of result values
     corresponds to the order of awaitables in 'aws'.

     If 'return_exceptions' is ‘False’ (default), the first raised
     exception is immediately propagated to the task that awaits on
     ‘gather()’.  Other awaitables in the 'aws' sequence 'won't be
     cancelled' and will continue to run.

     If 'return_exceptions' is ‘True’, exceptions are treated the same
     as successful results, and aggregated in the result list.

     If ‘gather()’ is 'cancelled', all submitted awaitables (that have
     not completed yet) are also 'cancelled'.

     If any Task or Future from the 'aws' sequence is 'cancelled', it is
     treated as if it raised *note CancelledError: 19e. - the ‘gather()’
     call is 'not' cancelled in this case.  This is to prevent the
     cancellation of one submitted Task/Future to cause other
     Tasks/Futures to be cancelled.

          備註: A new alternative to create and run tasks concurrently
          and wait for their completion is *note asyncio.TaskGroup: 19b.
          'TaskGroup' provides stronger safety guarantees than 'gather'
          for scheduling a nesting of subtasks: if a task (or a subtask,
          a task scheduled by a task) raises an exception, 'TaskGroup'
          will, while 'gather' will not, cancel the remaining scheduled
          tasks).
     範例：

          import asyncio

          async def factorial(name, number):
              f = 1
              for i in range(2, number + 1):
                  print(f"Task {name}: Compute factorial({number}), currently i={i}...")
                  await asyncio.sleep(1)
                  f *= i
              print(f"Task {name}: factorial({number}) = {f}")
              return f

          async def main():
              # Schedule three calls *concurrently*:
              L = await asyncio.gather(
                  factorial("A", 2),
                  factorial("B", 3),
                  factorial("C", 4),
              )
              print(L)

          asyncio.run(main())

          # Expected output:
          #
          #     Task A: Compute factorial(2), currently i=2...
          #     Task B: Compute factorial(3), currently i=2...
          #     Task C: Compute factorial(4), currently i=2...
          #     Task A: factorial(2) = 2
          #     Task B: Compute factorial(3), currently i=3...
          #     Task C: Compute factorial(4), currently i=3...
          #     Task B: factorial(3) = 6
          #     Task C: Compute factorial(4), currently i=4...
          #     Task C: factorial(4) = 24
          #     [2, 6, 24]

          備註: If 'return_exceptions' is false, cancelling gather()
          after it has been marked done won't cancel any submitted
          awaitables.  For instance, gather can be marked done after
          propagating an exception to the caller, therefore, calling
          ‘gather.cancel()’ after catching an exception (raised by one
          of the awaitables) from gather won't cancel any other
          awaitables.

     在 3.7 版的變更: If the 'gather' itself is cancelled, the
     cancellation is propagated regardless of 'return_exceptions'.

     在 3.10 版的變更: 移除 'loop' 參數。

     在 3.10 版之後被棄用: Deprecation warning is emitted if no
     positional arguments are provided or not all positional arguments
     are Future-like objects and there is no running event loop.


File: python.info,  Node: Eager Task Factory,  Next: Shielding From Cancellation,  Prev: Running Tasks Concurrently,  Up: 協程與任務

5.18.1.13 Eager Task Factory
............................

 -- 函式: asyncio.eager_task_factory (loop, coro, *, name=None,
          context=None)

     A task factory for eager task execution.

     When using this factory (via *note
     loop.set_task_factory(asyncio.eager_task_factory): d6c.),
     coroutines begin execution synchronously during *note Task: 480.
     construction.  Tasks are only scheduled on the event loop if they
     block.  This can be a performance improvement as the overhead of
     loop scheduling is avoided for coroutines that complete
     synchronously.

     A common example where this is beneficial is coroutines which
     employ caching or memoization to avoid actual I/O when possible.

          備註: Immediate execution of the coroutine is a semantic
          change.  If the coroutine returns or raises, the task is never
          scheduled to the event loop.  If the coroutine execution
          blocks, the task is scheduled to the event loop.  This change
          may introduce behavior changes to existing applications.  For
          example, the application's task execution order is likely to
          change.

     在 3.12 版被加入.

 -- 函式: asyncio.create_eager_task_factory (custom_task_constructor)

     Create an eager task factory, similar to *note
     eager_task_factory(): 41e, using the provided
     'custom_task_constructor' when creating a new task instead of the
     default *note Task: 480.

     'custom_task_constructor' must be a 'callable' with the signature
     matching the signature of *note Task.__init__: 480.  The callable
     must return a *note asyncio.Task: 480.-compatible object.

     This function returns a 'callable' intended to be used as a task
     factory of an event loop via *note loop.set_task_factory(factory):
     d6c.).

     在 3.12 版被加入.


File: python.info,  Node: Shielding From Cancellation,  Next: Timeouts,  Prev: Eager Task Factory,  Up: 協程與任務

5.18.1.14 Shielding From Cancellation
.....................................

 -- 函式: awaitable asyncio.shield (aw)

     Protect an *note awaitable object: 30c5. from being *note
     cancelled: 19d.

     If 'aw' is a coroutine it is automatically scheduled as a Task.

     The statement:

          task = asyncio.create_task(something())
          res = await shield(task)

     is equivalent to:

          res = await something()

     'except' that if the coroutine containing it is cancelled, the Task
     running in ‘something()’ is not cancelled.  From the point of view
     of ‘something()’, the cancellation did not happen.  Although its
     caller is still cancelled, so the "await" expression still raises a
     *note CancelledError: 19e.

     If ‘something()’ is cancelled by other means (i.e.  from within
     itself) that would also cancel ‘shield()’.

     If it is desired to completely ignore cancellation (not
     recommended) the ‘shield()’ function should be combined with a
     try/except clause, as follows:

          task = asyncio.create_task(something())
          try:
              res = await shield(task)
          except CancelledError:
              res = None

          重要: Save a reference to tasks passed to this function, to
          avoid a task disappearing mid-execution.  The event loop only
          keeps weak references to tasks.  A task that isn't referenced
          elsewhere may get garbage collected at any time, even before
          it's done.

     在 3.10 版的變更: 移除 'loop' 參數。

     在 3.10 版之後被棄用: Deprecation warning is emitted if 'aw' is not
     Future-like object and there is no running event loop.


File: python.info,  Node: Timeouts,  Next: Waiting Primitives,  Prev: Shielding From Cancellation,  Up: 協程與任務

5.18.1.15 Timeouts
..................

 -- 函式: asyncio.timeout (delay)

     Return an *note asynchronous context manager: 5a0. that can be used
     to limit the amount of time spent waiting on something.

     'delay' can either be ‘None’, or a float/int number of seconds to
     wait.  If 'delay' is ‘None’, no time limit will be applied; this
     can be useful if the delay is unknown when the context manager is
     created.

     In either case, the context manager can be rescheduled after
     creation using *note Timeout.reschedule(): 30d3.

     範例：

          async def main():
              async with asyncio.timeout(10):
                  await long_running_task()

     If ‘long_running_task’ takes more than 10 seconds to complete, the
     context manager will cancel the current task and handle the
     resulting *note asyncio.CancelledError: 19e. internally,
     transforming it into a *note TimeoutError: 7d9. which can be caught
     and handled.

          備註: The *note asyncio.timeout(): 5a3. context manager is
          what transforms the *note asyncio.CancelledError: 19e. into a
          *note TimeoutError: 7d9, which means the *note TimeoutError:
          7d9. can only be caught 'outside' of the context manager.

     Example of catching *note TimeoutError: 7d9.:

          async def main():
              try:
                  async with asyncio.timeout(10):
                      await long_running_task()
              except TimeoutError:
                  print("The long operation timed out, but we've handled it.")

              print("This statement will run regardless.")

     The context manager produced by *note asyncio.timeout(): 5a3. can
     be rescheduled to a different deadline and inspected.

      -- 類別: asyncio.Timeout (when)

          An *note asynchronous context manager: 5a0. for cancelling
          overdue coroutines.

          ‘when’ should be an absolute time at which the context should
          time out, as measured by the event loop's clock:

             - If ‘when’ is ‘None’, the timeout will never trigger.

             - If ‘when < loop.time()’, the timeout will trigger on the
               next iteration of the event loop.

                -- 方法: when () -> float | None

                    Return the current deadline, or ‘None’ if the
                    current deadline is not set.

                -- 方法: reschedule (when: float | None)

                    Reschedule the timeout.

                -- 方法: expired () -> bool

                    Return whether the context manager has exceeded its
                    deadline (expired).

     範例：

          async def main():
              try:
                  # We do not know the timeout when starting, so we pass ``None``.
                  async with asyncio.timeout(None) as cm:
                      # We know the timeout now, so we reschedule it.
                      new_deadline = get_running_loop().time() + 10
                      cm.reschedule(new_deadline)

                      await long_running_task()
              except TimeoutError:
                  pass

              if cm.expired():
                  print("Looks like we haven't finished on time.")

     Timeout context managers can be safely nested.

     在 3.11 版被加入.

 -- 函式: asyncio.timeout_at (when)

     Similar to *note asyncio.timeout(): 5a3, except 'when' is the
     absolute time to stop waiting, or ‘None’.

     範例：

          async def main():
              loop = get_running_loop()
              deadline = loop.time() + 20
              try:
                  async with asyncio.timeout_at(deadline):
                      await long_running_task()
              except TimeoutError:
                  print("The long operation timed out, but we've handled it.")

              print("This statement will run regardless.")

     在 3.11 版被加入.

 -- 函式: coroutine asyncio.wait_for (aw, timeout)

     Wait for the 'aw' *note awaitable: 30c5. to complete with a
     timeout.

     If 'aw' is a coroutine it is automatically scheduled as a Task.

     'timeout' can either be ‘None’ or a float or int number of seconds
     to wait for.  If 'timeout' is ‘None’, block until the future
     completes.

     If a timeout occurs, it cancels the task and raises *note
     TimeoutError: 7d9.

     To avoid the task *note cancellation: 19d, wrap it in *note
     shield(): a13.

     The function will wait until the future is actually cancelled, so
     the total wait time may exceed the 'timeout'.  If an exception
     happens during cancellation, it is propagated.

     If the wait is cancelled, the future 'aw' is also cancelled.  範例
     ：

          async def eternity():
              # Sleep for one hour
              await asyncio.sleep(3600)
              print('yay!')

          async def main():
              # Wait for at most 1 second
              try:
                  await asyncio.wait_for(eternity(), timeout=1.0)
              except TimeoutError:
                  print('timeout!')

          asyncio.run(main())

          # Expected output:
          #
          #     timeout!

     在 3.7 版的變更: When 'aw' is cancelled due to a timeout,
     ‘wait_for’ waits for 'aw' to be cancelled.  Previously, it raised
     *note TimeoutError: 7d9. immediately.

     在 3.10 版的變更: 移除 'loop' 參數。

     在 3.11 版的變更: 引發 *note TimeoutError: 7d9. 而不是 *note
     asyncio.TimeoutError: 1642.。


File: python.info,  Node: Waiting Primitives,  Next: Running in Threads,  Prev: Timeouts,  Up: 協程與任務

5.18.1.16 Waiting Primitives
............................

 -- 函式: coroutine asyncio.wait (aws, *, timeout=None,
          return_when=ALL_COMPLETED)

     Run *note Future: b74. and *note Task: 480. instances in the 'aws'
     iterable concurrently and block until the condition specified by
     'return_when'.

     The 'aws' iterable must not be empty.

     Returns two sets of Tasks/Futures: ‘(done, pending)’.

     用法：

          done, pending = await asyncio.wait(aws)

     'timeout' (a float or int), if specified, can be used to control
     the maximum number of seconds to wait before returning.

     Note that this function does not raise *note TimeoutError: 7d9.
     Futures or Tasks that aren't done when the timeout occurs are
     simply returned in the second set.

     'return_when' indicates when this function should return.  It must
     be one of the following constants:

     常數                                                   描述
                                                            
     --------------------------------------------------------------------------------------------------------------
                                                            
      -- 資料: asyncio.FIRST_COMPLETED                      The function will return when any future finishes or
                                                            is cancelled.
                                                            
                                                            
      -- 資料: asyncio.FIRST_EXCEPTION                      The function will return when any future finishes by
                                                            raising an exception.  If no future raises an
                                                            exception then it is equivalent to
                                                            *note ALL_COMPLETED: 30da.
                                                            
                                                            
      -- 資料: asyncio.ALL_COMPLETED                        The function will return when all futures finish or
                                                            are cancelled.
                                                            

     Unlike *note wait_for(): 5a4, ‘wait()’ does not cancel the futures
     when a timeout occurs.

     在 3.10 版的變更: 移除 'loop' 參數。

     在 3.11 版的變更: Passing coroutine objects to ‘wait()’ directly is
     forbidden.

     在 3.12 版的變更: Added support for generators yielding tasks.

 -- 函式: asyncio.as_completed (aws, *, timeout=None)

     Run *note awaitable objects: 30c5. in the 'aws' iterable
     concurrently.  The returned object can be iterated to obtain the
     results of the awaitables as they finish.

     The object returned by ‘as_completed()’ can be iterated as an *note
     asynchronous iterator: 191. or a plain *note iterator: 192.  When
     asynchronous iteration is used, the originally-supplied awaitables
     are yielded if they are tasks or futures.  This makes it easy to
     correlate previously-scheduled tasks with their results.  Example:

          ipv4_connect = create_task(open_connection("127.0.0.1", 80))
          ipv6_connect = create_task(open_connection("::1", 80))
          tasks = [ipv4_connect, ipv6_connect]

          async for earliest_connect in as_completed(tasks):
              # earliest_connect is done. The result can be obtained by
              # awaiting it or calling earliest_connect.result()
              reader, writer = await earliest_connect

              if earliest_connect is ipv6_connect:
                  print("IPv6 connection established.")
              else:
                  print("IPv4 connection established.")

     During asynchronous iteration, implicitly-created tasks will be
     yielded for supplied awaitables that aren't tasks or futures.

     When used as a plain iterator, each iteration yields a new
     coroutine that returns the result or raises the exception of the
     next completed awaitable.  This pattern is compatible with Python
     versions older than 3.13:

          ipv4_connect = create_task(open_connection("127.0.0.1", 80))
          ipv6_connect = create_task(open_connection("::1", 80))
          tasks = [ipv4_connect, ipv6_connect]

          for next_connect in as_completed(tasks):
              # next_connect is not one of the original task objects. It must be
              # awaited to obtain the result value or raise the exception of the
              # awaitable that finishes next.
              reader, writer = await next_connect

     A *note TimeoutError: 7d9. is raised if the timeout occurs before
     all awaitables are done.  This is raised by the ‘async for’ loop
     during asynchronous iteration or by the coroutines yielded during
     plain iteration.

     在 3.10 版的變更: 移除 'loop' 參數。

     在 3.10 版之後被棄用: Deprecation warning is emitted if not all
     awaitable objects in the 'aws' iterable are Future-like objects and
     there is no running event loop.

     在 3.12 版的變更: Added support for generators yielding tasks.

     在 3.13 版的變更: The result can now be used as either an *note
     asynchronous iterator: 191. or as a plain *note iterator: 192.
     (previously it was only a plain iterator).


File: python.info,  Node: Running in Threads,  Next: Scheduling From Other Threads,  Prev: Waiting Primitives,  Up: 協程與任務

5.18.1.17 Running in Threads
............................

 -- 函式: coroutine asyncio.to_thread (func, /, *args, **kwargs)

     Asynchronously run function 'func' in a separate thread.

     Any *args and **kwargs supplied for this function are directly
     passed to 'func'.  Also, the current *note contextvars.Context:
     308c. is propagated, allowing context variables from the event loop
     thread to be accessed in the separate thread.

     Return a coroutine that can be awaited to get the eventual result
     of 'func'.

     This coroutine function is primarily intended to be used for
     executing IO-bound functions/methods that would otherwise block the
     event loop if they were run in the main thread.  For example:

          def blocking_io():
              print(f"start blocking_io at {time.strftime('%X')}")
              # Note that time.sleep() can be replaced with any blocking
              # IO-bound operation, such as file operations.
              time.sleep(1)
              print(f"blocking_io complete at {time.strftime('%X')}")

          async def main():
              print(f"started main at {time.strftime('%X')}")

              await asyncio.gather(
                  asyncio.to_thread(blocking_io),
                  asyncio.sleep(1))

              print(f"finished main at {time.strftime('%X')}")


          asyncio.run(main())

          # Expected output:
          #
          # started main at 19:50:53
          # start blocking_io at 19:50:53
          # blocking_io complete at 19:50:54
          # finished main at 19:50:54

     Directly calling ‘blocking_io()’ in any coroutine would block the
     event loop for its duration, resulting in an additional 1 second of
     run time.  Instead, by using ‘asyncio.to_thread()’, we can run it
     in a separate thread without blocking the event loop.

          備註: Due to the *note GIL: 13e, ‘asyncio.to_thread()’ can
          typically only be used to make IO-bound functions
          non-blocking.  However, for extension modules that release the
          GIL or alternative Python implementations that don't have one,
          ‘asyncio.to_thread()’ can also be used for CPU-bound
          functions.

     在 3.9 版被加入.


File: python.info,  Node: Scheduling From Other Threads,  Next: Introspection,  Prev: Running in Threads,  Up: 協程與任務

5.18.1.18 Scheduling From Other Threads
.......................................

 -- 函式: asyncio.run_coroutine_threadsafe (coro, loop)

     Submit a coroutine to the given event loop.  Thread-safe.

     Return a *note concurrent.futures.Future: 1149. to wait for the
     result from another OS thread.

     This function is meant to be called from a different OS thread than
     the one where the event loop is running.  Example:

          # Create a coroutine
          coro = asyncio.sleep(1, result=3)

          # Submit the coroutine to a given loop
          future = asyncio.run_coroutine_threadsafe(coro, loop)

          # Wait for the result with an optional timeout argument
          assert future.result(timeout) == 3

     If an exception is raised in the coroutine, the returned Future
     will be notified.  It can also be used to cancel the task in the
     event loop:

          try:
              result = future.result(timeout)
          except TimeoutError:
              print('The coroutine took too long, cancelling the task...')
              future.cancel()
          except Exception as exc:
              print(f'The coroutine raised an exception: {exc!r}')
          else:
              print(f'The coroutine returned: {result!r}')

     See the *note concurrency and multithreading: 30dd. section of the
     documentation.

     Unlike other asyncio functions this function requires the 'loop'
     argument to be passed explicitly.

     在 3.5.1 版被加入.


File: python.info,  Node: Introspection,  Next: Task Object,  Prev: Scheduling From Other Threads,  Up: 協程與任務

5.18.1.19 Introspection
.......................

 -- 函式: asyncio.current_task (loop=None)

     Return the currently running *note Task: 480. instance, or ‘None’
     if no task is running.

     If 'loop' is ‘None’ *note get_running_loop(): aae. is used to get
     the current loop.

     在 3.7 版被加入.

 -- 函式: asyncio.all_tasks (loop=None)

     Return a set of not yet finished *note Task: 480. objects run by
     the loop.

     If 'loop' is ‘None’, *note get_running_loop(): aae. is used for
     getting current loop.

     在 3.7 版被加入.

 -- 函式: asyncio.iscoroutine (obj)

     Return ‘True’ if 'obj' is a coroutine object.

     在 3.4 版被加入.


File: python.info,  Node: Task Object,  Prev: Introspection,  Up: 協程與任務

5.18.1.20 Task Object
.....................

 -- 類別: asyncio.Task (coro, *, loop=None, name=None, context=None,
          eager_start=False)

     A *note Future-like: b74. object that runs a Python *note
     coroutine: 30af.  Not thread-safe.

     Tasks are used to run coroutines in event loops.  If a coroutine
     awaits on a Future, the Task suspends the execution of the
     coroutine and waits for the completion of the Future.  When the
     Future is 'done', the execution of the wrapped coroutine resumes.

     Event loops use cooperative scheduling: an event loop runs one Task
     at a time.  While a Task awaits for the completion of a Future, the
     event loop runs other Tasks, callbacks, or performs IO operations.

     Use the high-level *note asyncio.create_task(): 5a1. function to
     create Tasks, or the low-level *note loop.create_task(): 980. or
     *note ensure_future(): c1d. functions.  Manual instantiation of
     Tasks is discouraged.

     To cancel a running Task use the *note cancel(): 19d. method.
     Calling it will cause the Task to throw a *note CancelledError:
     19e. exception into the wrapped coroutine.  If a coroutine is
     awaiting on a Future object during cancellation, the Future object
     will be cancelled.

     *note cancelled(): 30e0. can be used to check if the Task was
     cancelled.  The method returns ‘True’ if the wrapped coroutine did
     not suppress the *note CancelledError: 19e. exception and was
     actually cancelled.

     *note asyncio.Task: 480. inherits from *note Future: b74. all of
     its APIs except *note Future.set_result(): 30e1. and *note
     Future.set_exception(): 30e2.

     An optional keyword-only 'context' argument allows specifying a
     custom *note contextvars.Context: 308c. for the 'coro' to run in.
     If no 'context' is provided, the Task copies the current context
     and later runs its coroutine in the copied context.

     An optional keyword-only 'eager_start' argument allows eagerly
     starting the execution of the *note asyncio.Task: 480. at task
     creation time.  If set to ‘True’ and the event loop is running, the
     task will start executing the coroutine immediately, until the
     first time the coroutine blocks.  If the coroutine returns or
     raises without blocking, the task will be finished eagerly and will
     skip scheduling to the event loop.

     在 3.7 版的變更: Added support for the *note contextvars: 1d.
     module.

     在 3.8 版的變更: 新增 'name' 參數。

     在 3.10 版之後被棄用: Deprecation warning is emitted if 'loop' is
     not specified and there is no running event loop.

     在 3.11 版的變更: 新增 'context' 參數。

     在 3.12 版的變更: 新增 'eager_start' 參數。

      -- 方法: done ()

          Return ‘True’ if the Task is 'done'.

          A Task is 'done' when the wrapped coroutine either returned a
          value, raised an exception, or the Task was cancelled.

      -- 方法: result ()

          Return the result of the Task.

          If the Task is 'done', the result of the wrapped coroutine is
          returned (or if the coroutine raised an exception, that
          exception is re-raised.)

          If the Task has been 'cancelled', this method raises a *note
          CancelledError: 19e. exception.

          If the Task's result isn't yet available, this method raises
          an *note InvalidStateError: 30e5. exception.

      -- 方法: exception ()

          Return the exception of the Task.

          If the wrapped coroutine raised an exception that exception is
          returned.  If the wrapped coroutine returned normally this
          method returns ‘None’.

          If the Task has been 'cancelled', this method raises a *note
          CancelledError: 19e. exception.

          If the Task isn't 'done' yet, this method raises an *note
          InvalidStateError: 30e5. exception.

      -- 方法: add_done_callback (callback, *, context=None)

          Add a callback to be run when the Task is 'done'.

          This method should only be used in low-level callback-based
          code.

          See the documentation of *note Future.add_done_callback():
          aab. for more details.

      -- 方法: remove_done_callback (callback)

          Remove 'callback' from the callbacks list.

          This method should only be used in low-level callback-based
          code.

          See the documentation of *note Future.remove_done_callback():
          16c7. for more details.

      -- 方法: get_stack (*, limit=None)

          Return the list of stack frames for this Task.

          If the wrapped coroutine is not done, this returns the stack
          where it is suspended.  If the coroutine has completed
          successfully or was cancelled, this returns an empty list.  If
          the coroutine was terminated by an exception, this returns the
          list of traceback frames.

          The frames are always ordered from oldest to newest.

          Only one stack frame is returned for a suspended coroutine.

          The optional 'limit' argument sets the maximum number of
          frames to return; by default all available frames are
          returned.  The ordering of the returned list differs depending
          on whether a stack or a traceback is returned: the newest
          frames of a stack are returned, but the oldest frames of a
          traceback are returned.  (This matches the behavior of the
          traceback module.)

      -- 方法: print_stack (*, limit=None, file=None)

          Print the stack or traceback for this Task.

          This produces output similar to that of the traceback module
          for the frames retrieved by *note get_stack(): 30e9.

          The 'limit' argument is passed to *note get_stack(): 30e9.
          directly.

          The 'file' argument is an I/O stream to which the output is
          written; by default output is written to *note sys.stdout:
          a79.

      -- 方法: get_coro ()

          Return the coroutine object wrapped by the *note Task: 480.

               備註: This will return ‘None’ for Tasks which have
               already completed eagerly.  See the *note Eager Task
               Factory: 30cf.

          在 3.8 版被加入.

          在 3.12 版的變更: Newly added eager task execution means
          result may be ‘None’.

      -- 方法: get_context ()

          Return the *note contextvars.Context: 308c. object associated
          with the task.

          在 3.12 版被加入.

      -- 方法: get_name ()

          Return the name of the Task.

          If no name has been explicitly assigned to the Task, the
          default asyncio Task implementation generates a default name
          during instantiation.

          在 3.8 版被加入.

      -- 方法: set_name (value)

          Set the name of the Task.

          The 'value' argument can be any object, which is then
          converted to a string.

          In the default Task implementation, the name will be visible
          in the *note repr(): 7a1. output of a task object.

          在 3.8 版被加入.

      -- 方法: cancel (msg=None)

          Request the Task to be cancelled.

          This arranges for a *note CancelledError: 19e. exception to be
          thrown into the wrapped coroutine on the next cycle of the
          event loop.

          The coroutine then has a chance to clean up or even deny the
          request by suppressing the exception with a *note try: 68c.
          ...  ...  ‘except CancelledError’ ...  *note finally: 96e.
          block.  Therefore, unlike *note Future.cancel(): 171f, *note
          Task.cancel(): 19d. does not guarantee that the Task will be
          cancelled, although suppressing cancellation completely is not
          common and is actively discouraged.  Should the coroutine
          nevertheless decide to suppress the cancellation, it needs to
          call *note Task.uncancel(): 1a1. in addition to catching the
          exception.

          在 3.9 版的變更: 新增 'msg' 參數。

          在 3.11 版的變更: The ‘msg’ parameter is propagated from
          cancelled task to its awaiter.

          The following example illustrates how coroutines can intercept
          the cancellation request:

               async def cancel_me():
                   print('cancel_me(): before sleep')

                   try:
                       # Wait for 1 hour
                       await asyncio.sleep(3600)
                   except asyncio.CancelledError:
                       print('cancel_me(): cancel sleep')
                       raise
                   finally:
                       print('cancel_me(): after sleep')

               async def main():
                   # Create a "cancel_me" Task
                   task = asyncio.create_task(cancel_me())

                   # Wait for 1 second
                   await asyncio.sleep(1)

                   task.cancel()
                   try:
                       await task
                   except asyncio.CancelledError:
                       print("main(): cancel_me is cancelled now")

               asyncio.run(main())

               # Expected output:
               #
               #     cancel_me(): before sleep
               #     cancel_me(): cancel sleep
               #     cancel_me(): after sleep
               #     main(): cancel_me is cancelled now

      -- 方法: cancelled ()

          Return ‘True’ if the Task is 'cancelled'.

          The Task is 'cancelled' when the cancellation was requested
          with *note cancel(): 19d. and the wrapped coroutine propagated
          the *note CancelledError: 19e. exception thrown into it.

      -- 方法: uncancel ()

          Decrement the count of cancellation requests to this Task.

          Returns the remaining number of cancellation requests.

          Note that once execution of a cancelled task completed,
          further calls to *note uncancel(): 1a1. are ineffective.

          在 3.11 版被加入.

          This method is used by asyncio's internals and isn't expected
          to be used by end-user code.  In particular, if a Task gets
          successfully uncancelled, this allows for elements of
          structured concurrency like *note Task Groups: 30ca. and *note
          asyncio.timeout(): 5a3. to continue running, isolating
          cancellation to the respective structured block.  For example:

               async def make_request_with_timeout():
                   try:
                       async with asyncio.timeout(1):
                           # Structured block affected by the timeout:
                           await make_request()
                           await make_another_request()
                   except TimeoutError:
                       log("There was a timeout")
                   # Outer code not affected by the timeout:
                   await unrelated_code()

          While the block with ‘make_request()’ and
          ‘make_another_request()’ might get cancelled due to the
          timeout, ‘unrelated_code()’ should continue running even in
          case of the timeout.  This is implemented with *note
          uncancel(): 1a1.  *note TaskGroup: 19b. context managers use
          *note uncancel(): 1a1. in a similar fashion.

          If end-user code is, for some reason, suppressing cancellation
          by catching *note CancelledError: 19e, it needs to call this
          method to remove the cancellation state.

          When this method decrements the cancellation count to zero,
          the method checks if a previous *note cancel(): 19d. call had
          arranged for *note CancelledError: 19e. to be thrown into the
          task.  If it hasn't been thrown yet, that arrangement will be
          rescinded (by resetting the internal ‘_must_cancel’ flag).

     在 3.13 版的變更: Changed to rescind pending cancellation requests
     upon reaching zero.

      -- 方法: cancelling ()

          Return the number of pending cancellation requests to this
          Task, i.e., the number of calls to *note cancel(): 19d. less
          the number of *note uncancel(): 1a1. calls.

          Note that if this number is greater than zero but the Task is
          still executing, *note cancelled(): 30e0. will still return
          ‘False’.  This is because this number can be lowered by
          calling *note uncancel(): 1a1, which can lead to the task not
          being cancelled after all if the cancellation requests go down
          to zero.

          This method is used by asyncio's internals and isn't expected
          to be used by end-user code.  See *note uncancel(): 1a1. for
          more details.

          在 3.11 版被加入.


File: python.info,  Node: 串流,  Next: 同步化原始物件 Synchronization Primitives,  Prev: 協程與任務,  Up: asyncio --- 非同步 I/O

5.18.1.21 串流
..............

'原始碼：'Lib/asyncio/streams.py(1)

__________________________________________________________________

串流是支援 async/await (async/await-ready) 的高階原始物件 (high-level
primitive)，用於處理網路連線。串流不需要使用回呼 (callback) 或低階協定和
傳輸 (transport) 就能夠傳送和接收資料。 這是一個使用 asyncio 串流編寫的
TCP echo 客戶端範例：

     import asyncio

     async def tcp_echo_client(message):
         reader, writer = await asyncio.open_connection(
             '127.0.0.1', 8888)

         print(f'Send: {message!r}')
         writer.write(message.encode())
         await writer.drain()

         data = await reader.read(100)
         print(f'Received: {data.decode()!r}')

         print('Close the connection')
         writer.close()
         await writer.wait_closed()

     asyncio.run(tcp_echo_client('Hello World!'))

另請參閱下方 *note Examples: 30ef. 段落。

串流函式
........

下面的高階 asyncio 函式可以用來建立和處理串流：

 -- 函式: coroutine asyncio.open_connection (host=None, port=None, *,
          limit=None, ssl=None, family=0, proto=0, flags=0, sock=None,
          local_addr=None, server_hostname=None,
          ssl_handshake_timeout=None, ssl_shutdown_timeout=None,
          happy_eyeballs_delay=None, interleave=None)

     建立網路連線並回傳一對 ‘(reader, writer)’ 物件。

     回傳的 'reader' 和 'writer' 物件是 *note StreamReader: 17c8. 和
     *note StreamWriter: 15fc. 類別的實例。

     'limit' 指定了回傳的 *note StreamReader: 17c8. 實例所使用的緩衝區
     (buffer) 大小限制。'limit' 預設為 64 KiB。

     其餘的引數會直接傳遞到 *note loop.create_connection(): 5a8.。

          備註: The 'sock' argument transfers ownership of the socket to
          the *note StreamWriter: 15fc. created.  To close the socket,
          call its *note close(): 30f0. method.

     在 3.7 版的變更: 新增 'ssl_handshake_timeout' 參數。

     在 3.8 版的變更: 新增 'happy_eyeballs_delay' 和 'interleave' 參數。

     在 3.10 版的變更: 移除 'loop' 參數。

     在 3.11 版的變更: 新增 'ssl_shutdown_timeout' 參數。

 -- 函式: coroutine asyncio.start_server (client_connected_cb,
          host=None, port=None, *, limit=None, family=socket.AF_UNSPEC,
          flags=socket.AI_PASSIVE, sock=None, backlog=100, ssl=None,
          reuse_address=None, reuse_port=None,
          ssl_handshake_timeout=None, ssl_shutdown_timeout=None,
          start_serving=True)

     啟動 socket 伺服器。

     當一個新的客戶端連線被建立時，回呼函式 'client_connected_cb' 就會被
     呼叫。該函式會接收到一對引數 ‘(reader, writer)’，分別為 *note
     StreamReader: 17c8. 和 *note StreamWriter: 15fc. 的實例。

     'client_connected_cb' 既可以是普通的可呼叫物件 (callable)，也可以是
     一個*note 協程函式: 30af.；如果它是一個協程函式，它將自動作為 *note
     Task: 480. 來被排程。

     'limit' 指定了回傳的 *note StreamReader: 17c8. 實例所使用的緩衝區
     (buffer) 大小限制。'limit' 預設為 64 KiB。

     剩下的引數將會直接傳遞給 *note loop.create_server(): ab6.。

          備註: The 'sock' argument transfers ownership of the socket to
          the server created.  To close the socket, call the server's
          *note close(): 30f1. method.

     在 3.7 版的變更: 新增 'ssl_handshake_timeout' 與 'start_serving' 參
     數。

     在 3.10 版的變更: 移除 'loop' 參數。

     在 3.11 版的變更: 新增 'ssl_shutdown_timeout' 參數。

Unix Sockets
............

 -- 函式: coroutine asyncio.open_unix_connection (path=None, *,
          limit=None, ssl=None, sock=None, server_hostname=None,
          ssl_handshake_timeout=None, ssl_shutdown_timeout=None)

     建立一個 Unix socket 連線並回傳一對 ‘(reader, writer)’。

     與 *note open_connection(): abb. 相似，但是是操作 Unix sockets。

     另請參閱 *note loop.create_unix_connection(): 30f3. 文件。

          備註: The 'sock' argument transfers ownership of the socket to
          the *note StreamWriter: 15fc. created.  To close the socket,
          call its *note close(): 30f0. method.

     *note 適用: 1c56.：Unix。

     在 3.7 版的變更: 新增 'ssl_handshake_timeout' 參數。'path' 參數現在
     可以是個 *note path-like object: ac2.

     在 3.10 版的變更: 移除 'loop' 參數。

     在 3.11 版的變更: 新增 'ssl_shutdown_timeout' 參數。

 -- 函式: coroutine asyncio.start_unix_server (client_connected_cb,
          path=None, *, limit=None, sock=None, backlog=100, ssl=None,
          ssl_handshake_timeout=None, ssl_shutdown_timeout=None,
          start_serving=True)

     啟動一個 Unix socket 伺服器。

     與 *note start_server(): abc. 相似，但會是操作 Unix sockets。

     另請參閱 *note loop.create_unix_server(): 194. 文件。

          備註: The 'sock' argument transfers ownership of the socket to
          the server created.  To close the socket, call the server's
          *note close(): 30f1. method.

     *note 適用: 1c56.：Unix。

     在 3.7 版的變更: 新增 'ssl_handshake_timeout' 與 'start_serving' 參
     數。'path' 參數現在可以是個 *note path-like object: ac2.。

     在 3.10 版的變更: 移除 'loop' 參數。

     在 3.11 版的變更: 新增 'ssl_shutdown_timeout' 參數。

* Menu:

* StreamReader::
* StreamWriter::
* 範例: 範例<20>.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/asyncio/streams.py


File: python.info,  Node: StreamReader,  Next: StreamWriter,  Up: 串流

5.18.1.22 StreamReader
......................

 -- 類別: asyncio.StreamReader

     表示一個有提供 API 來從 IO 串流中讀取資料的 reader 物件。作為一個
     *note asynchronous iterable: d1e.，此物件支援 *note async for: a4e.
     陳述式。

     不建議直接實例化 'StreamReader' 物件；使用 *note open_connection():
     abb. 和 *note start_server(): abc. 會是較好的做法。

      -- 方法: feed_eof ()

          Acknowledge the EOF.

      -- 方法: coroutine read (n=-1)

          從串流中讀取至多 'n' 個位元組的資料。

          如果沒有設定 'n' 或是被設為 ‘-1’，則會持續讀取直到 EOF，然後回
          傳所有讀取到的 *note bytes: 1a5.。讀取到 EOF 且內部緩衝區是空
          的，則回傳一個空的 ‘bytes’ 物件。

          如果 'n' 為 ‘0’，則立即回傳一個空的 ‘bytes’ 物件。

          If 'n' is positive, return at most 'n' available ‘bytes’ as
          soon as at least 1 byte is available in the internal buffer.
          If EOF is received before any byte is read, return an empty
          ‘bytes’ object.

      -- 方法: coroutine readline ()

          讀取一行，其中"行"指的是以 ‘\n’ 結尾的位元組序列。

          如果讀取到 EOF 而沒有找到 ‘\n’，該方法會回傳部分的已讀取資料。

          如果讀取到 EOF 且內部緩衝區是空的，則回傳一個空的 ‘bytes’ 物件
          。

      -- 方法: coroutine readexactly (n)

          讀取剛好 'n' 個位元組。

          如果在讀取完 'n' 個位元組之前讀取到 EOF，則會引發 *note
          IncompleteReadError: 1822.。使用 *note
          IncompleteReadError.partial: 30f9. 屬性來獲取串流結束前已讀取
          的部分資料。

      -- 方法: coroutine readuntil (separator=b'\n')

          從串流中持續讀取資料直到出現 'separator'。

          成功後，資料和 separator（分隔符號）會從內部緩衝區中刪除（或者
          說是被消費掉 (consumed)）。回傳的資料在末尾會有一個 separator。

          如果讀取的資料量超過了設定的串流限制，將會引發 *note
          LimitOverrunError: 30fa. 例外，資料將被留在內部緩衝區中，並可
          以再次被讀取。

          如果在完整的 separator 被找到之前就讀取到 EOF，則會引發 *note
          IncompleteReadError: 1822. 例外，且內部緩衝區會被重置。*note
          IncompleteReadError.partial: 30f9. 屬性可能包含一部分的
          separator。

          The 'separator' may also be a tuple of separators.  In this
          case the return value will be the shortest possible that has
          any separator as the suffix.  For the purposes of *note
          LimitOverrunError: 30fa, the shortest possible separator is
          considered to be the one that matched.

          在 3.5.2 版被加入.

          在 3.13 版的變更: The 'separator' parameter may now be a *note
          tuple: 322. of separators.

      -- 方法: at_eof ()

          如果緩衝區是空的且 *note feed_eof(): 30f6. 曾被呼叫則回傳
          ‘True’。


File: python.info,  Node: StreamWriter,  Next: 範例<20>,  Prev: StreamReader,  Up: 串流

5.18.1.23 StreamWriter
......................

 -- 類別: asyncio.StreamWriter

     表示一個有提供 API 來將資料寫入 IO 串流的 writer 物件。

     不建議直接實例化 'StreamWriter' 物件；使用 *note open_connection():
     abb. 和 *note start_server(): abc. 會是較好的做法。

      -- 方法: write (data)

          此方法會嘗試立即將 'data' 寫入到底層的 socket。如果失敗，資料
          會被放到內部寫入緩衝中排隊等待 (queue)，直到它可被發送。

          此方法應當與 ‘drain()’ 方法一起使用：

               stream.write(data)
               await stream.drain()

      -- 方法: writelines (data)

          此方法會立即嘗試將一個位元組 list（或任何可疊代物件
          (iterable)）寫入到底層的 socket。如果失敗，資料會被放到內部寫
          入緩衝中排隊等待，直到它可被發送。

          此方法應當與 ‘drain()’ 方法一起使用：

               stream.writelines(lines)
               await stream.drain()

      -- 方法: close ()

          此方法會關閉串流以及底層的 socket。

          此方法應與 ‘wait_closed()’ 方法一起使用，但並非強制：

               stream.close()
               await stream.wait_closed()

      -- 方法: can_write_eof ()

          如果底層的傳輸支援 *note write_eof(): 3100. 方法就回傳 ‘True’，
          否則回傳 ‘False’。

      -- 方法: write_eof ()

          在已緩衝的寫入資料被清理 (flush) 後關閉串流的寫入端。

      -- 屬性: transport

          回傳底層的 asyncio 傳輸。

      -- 方法: get_extra_info (name, default=None)

          存取可選的傳輸資訊；詳情請見 *note
          BaseTransport.get_extra_info(): a3f.。

      -- 方法: coroutine drain ()

          等待直到可以繼續寫入到串流。範例：

               writer.write(data)
               await writer.drain()

          這是一個與底層 IO 寫入緩衝區互動的流程控制方法。當緩衝區大小達
          到最高標記位 (high watermark) 時，'drain()' 會阻塞直到緩衝區大
          小減少至最低標記位 (low watermark) 以便繼續寫入。當沒有要等待
          的資料時，*note drain(): 16b1. 會立即回傳。

      -- 方法: coroutine start_tls (sslcontext, *, server_hostname=None,
               ssl_handshake_timeout=None, ssl_shutdown_timeout=None)

          Upgrade an existing stream-based connection to TLS.

          參數：

             * 'sslcontext': a configured instance of *note SSLContext:
               276.

             * 'server_hostname': sets or overrides the host name that
               the target server's certificate will be matched against.

             * 'ssl_handshake_timeout' is the time in seconds to wait
               for the TLS handshake to complete before aborting the
               connection.  ‘60.0’ seconds if ‘None’ (default).

             * 'ssl_shutdown_timeout' is the time in seconds to wait for
               the SSL shutdown to complete before aborting the
               connection.  ‘30.0’ seconds if ‘None’ (default).

          在 3.11 版被加入.

          在 3.12 版的變更: 新增 'ssl_shutdown_timeout' 參數。

      -- 方法: is_closing ()

          如果串流已被關閉或正在被關閉則回傳 ‘True’。

          在 3.7 版被加入.

      -- 方法: coroutine wait_closed ()

          等待直到串流被關閉。

          應當在 *note close(): 30f0. 之後才被呼叫，這會持續等待直到底層
          的連線被關閉，以確保在這之前（例如在程式退出前）所有資料都已經
          被清空

          在 3.7 版被加入.


File: python.info,  Node: 範例<20>,  Prev: StreamWriter,  Up: 串流

5.18.1.24 範例
..............

* Menu:

* 使用串流的 TCP echo 客戶端::
* 使用串流的 TCP echo 伺服器::
* 獲取 HTTP 標頭::
* 註冊一個使用串流來等待資料的開放 socket::


File: python.info,  Node: 使用串流的 TCP echo 客戶端,  Next: 使用串流的 TCP echo 伺服器,  Up: 範例<20>

5.18.1.25 使用串流的 TCP echo 客戶端
....................................

使用 *note asyncio.open_connection(): abb. 函式的 TCP echo 客戶端：

     import asyncio

     async def tcp_echo_client(message):
         reader, writer = await asyncio.open_connection(
             '127.0.0.1', 8888)

         print(f'Send: {message!r}')
         writer.write(message.encode())
         await writer.drain()

         data = await reader.read(100)
         print(f'Received: {data.decode()!r}')

         print('Close the connection')
         writer.close()
         await writer.wait_closed()

     asyncio.run(tcp_echo_client('Hello World!'))

也參考
......

使用低階 *note loop.create_connection(): 5a8. 方法的 *note TCP echo
客戶端協定: 3105.範例。


File: python.info,  Node: 使用串流的 TCP echo 伺服器,  Next: 獲取 HTTP 標頭,  Prev: 使用串流的 TCP echo 客戶端,  Up: 範例<20>

5.18.1.26 使用串流的 TCP echo 伺服器
....................................

TCP echo 伺服器使用 *note asyncio.start_server(): abc. 函式：

     import asyncio

     async def handle_echo(reader, writer):
         data = await reader.read(100)
         message = data.decode()
         addr = writer.get_extra_info('peername')

         print(f"Received {message!r} from {addr!r}")

         print(f"Send: {message!r}")
         writer.write(data)
         await writer.drain()

         print("Close the connection")
         writer.close()
         await writer.wait_closed()

     async def main():
         server = await asyncio.start_server(
             handle_echo, '127.0.0.1', 8888)

         addrs = ', '.join(str(sock.getsockname()) for sock in server.sockets)
         print(f'Serving on {addrs}')

         async with server:
             await server.serve_forever()

     asyncio.run(main())

也參考
......

使用 *note loop.create_server(): ab6. 方法的 *note TCP echo 伺服器協定:
3108. 範例。


File: python.info,  Node: 獲取 HTTP 標頭,  Next: 註冊一個使用串流來等待資料的開放 socket,  Prev: 使用串流的 TCP echo 伺服器,  Up: 範例<20>

5.18.1.27 獲取 HTTP 標頭
........................

查詢自命令列傳入之 URL 所帶有 HTTP 標頭的簡單範例：

     import asyncio
     import urllib.parse
     import sys

     async def print_http_headers(url):
         url = urllib.parse.urlsplit(url)
         if url.scheme == 'https':
             reader, writer = await asyncio.open_connection(
                 url.hostname, 443, ssl=True)
         else:
             reader, writer = await asyncio.open_connection(
                 url.hostname, 80)

         query = (
             f"HEAD {url.path or '/'} HTTP/1.0\r\n"
             f"Host: {url.hostname}\r\n"
             f"\r\n"
         )

         writer.write(query.encode('latin-1'))
         while True:
             line = await reader.readline()
             if not line:
                 break

             line = line.decode('latin1').rstrip()
             if line:
                 print(f'HTTP header> {line}')

         # Ignore the body, close the socket
         writer.close()
         await writer.wait_closed()

     url = sys.argv[1]
     asyncio.run(print_http_headers(url))

用法：

     python example.py http://example.com/path/page.html

或使用 HTTPS：

     python example.py https://example.com/path/page.html


File: python.info,  Node: 註冊一個使用串流來等待資料的開放 socket,  Prev: 獲取 HTTP 標頭,  Up: 範例<20>

5.18.1.28 註冊一個使用串流來等待資料的開放 socket
.................................................

等待直到 socket 透過使用 *note open_connection(): abb. 函式接收到資料的
協程：

     import asyncio
     import socket

     async def wait_for_data():
         # Get a reference to the current event loop because
         # we want to access low-level APIs.
         loop = asyncio.get_running_loop()

         # Create a pair of connected sockets.
         rsock, wsock = socket.socketpair()

         # Register the open socket to wait for data.
         reader, writer = await asyncio.open_connection(sock=rsock)

         # Simulate the reception of data from the network
         loop.call_soon(wsock.send, 'abc'.encode())

         # Wait for data
         data = await reader.read(100)

         # Got data, we are done: close the socket
         print("Received:", data.decode())
         writer.close()
         await writer.wait_closed()

         # Close the second socket
         wsock.close()

     asyncio.run(wait_for_data())

也參考
......

在*note 註冊一個開啟的 socket 以等待有使用協定的資料: 310c.範例中，有使
用了低階協定以及 *note loop.create_connection(): 5a8. 方法。

在*note 監視檔案描述器以讀取事件: 310d.範例中，有使用低階的 *note
loop.add_reader(): 310e. 方法來監視檔案描述器。


File: python.info,  Node: 同步化原始物件 Synchronization Primitives,  Next: 子行程,  Prev: 串流,  Up: asyncio --- 非同步 I/O

5.18.1.29 同步化原始物件 (Synchronization Primitives)
.....................................................

'原始碼：'Lib/asyncio/locks.py(1)

__________________________________________________________________

asyncio 的同步化原始物件被設計成和那些 *note threading: d6. 模組
(module) 中的同名物件相似，但有兩個重要的限制條件：

   * asyncio 原始物件並不支援執行緒安全 (thread-safe)，因此他們不可被用
     於 OS 執行緒同步化（請改用 *note threading: d6.）；

   * 這些同步化原始物件的方法 (method) 並不接受 'timeout' 引數；要達成有
     超時 (timeout) 設定的操作請改用 *note asyncio.wait_for(): 5a4. 函式
     。

asyncio 有以下基礎同步化原始物件：

   * *note Lock: a14.

   * *note Event: a15.

   * *note Condition: a16.

   * *note Semaphore: a17.

   * *note BoundedSemaphore: a18.

   * *note Barrier: 5a6.

__________________________________________________________________

* Menu:

* Lock::
* Event::
* Condition::
* Semaphore::
* BoundedSemaphore::
* Barrier::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/asyncio/locks.py


File: python.info,  Node: Lock,  Next: Event,  Up: 同步化原始物件 Synchronization Primitives

5.18.1.30 Lock
..............

 -- 類別: asyncio.Lock

     實作了一個給 asyncio 任務 (task) 用的互斥鎖 (mutex lock)。不支援執
     行緒安全。

     一個 asyncio 的鎖可以用來確保一個共享資源的存取權被獨佔。

     使用 Lock 的推薦方式是透過 *note async with: 57a. 陳述式：

          lock = asyncio.Lock()

          # ... later
          async with lock:
              # access shared state

     這等價於：

          lock = asyncio.Lock()

          # ... later
          await lock.acquire()
          try:
              # access shared state
          finally:
              lock.release()

     在 3.10 版的變更: 移除 ‘loop’ 參數。

      -- 方法: coroutine acquire ()

          獲得鎖。

          此方法會持續等待直到鎖的狀態成為 'unlocked'，並將其設置為
          'locked' 和回傳 ‘True’。

          當多於一個的協程 (coroutine) 在 *note acquire(): 3112. 中等待
          解鎖而被阻塞，最終只會有其中的一個被處理。

          鎖的獲取方式是'公平'的：被處理的協程會是最早開始等待解鎖的那一
          個。

      -- 方法: release ()

          釋放鎖。

          如果鎖的狀態為 'locked' 則將其重置為 'unlocked' 並回傳。

          如果鎖的狀態為 'unlocked' 則 *note RuntimeError: 179. 會被引發
          。

      -- 方法: locked ()

          如果鎖的狀態為 'locked' 則回傳 ‘True’。


File: python.info,  Node: Event,  Next: Condition,  Prev: Lock,  Up: 同步化原始物件 Synchronization Primitives

5.18.1.31 Event
...............

 -- 類別: asyncio.Event

     一個事件 (event) 物件。不支援執行緒安全。

     一個 asyncio 事件可以被用於通知多個有發生某些事件於其中的 asyncio 任
     務。

     一個 Event 物件會管理一個內部旗標 (flag)，它可以透過 *note set():
     3116. 方法來被設為 'true' 並透過 *note clear(): 3117. 方法來重置為
     'false'。*note wait(): 3118. 方法會被阻塞 (block) 直到該旗標被設為
     'true'。該旗標初始設置為 'false'。

     在 3.10 版的變更: 移除 ‘loop’ 參數。

     範例：

          async def waiter(event):
              print('waiting for it ...')
              await event.wait()
              print('... got it!')

          async def main():
              # Create an Event object.
              event = asyncio.Event()

              # Spawn a Task to wait until 'event' is set.
              waiter_task = asyncio.create_task(waiter(event))

              # Sleep for 1 second and set the event.
              await asyncio.sleep(1)
              event.set()

              # Wait until the waiter task is finished.
              await waiter_task

          asyncio.run(main())

      -- 方法: coroutine wait ()

          持續等待直到事件被設置。

          如果事件有被設置則立刻回傳 ‘True’。否則持續阻塞直到另一個任務
          呼叫 *note set(): 3116.。

      -- 方法: set ()

          設置事件。

          所有正在等待事件被設置的任務會立即被喚醒。

      -- 方法: clear ()

          清除（還原）事件。

          正透過 *note wait(): 3118. 等待的 Tasks 現在會持續阻塞直到
          *note set(): 3116. 方法再次被呼叫。

      -- 方法: is_set ()

          如果事件有被設置則回傳 ‘True’。


File: python.info,  Node: Condition,  Next: Semaphore,  Prev: Event,  Up: 同步化原始物件 Synchronization Primitives

5.18.1.32 Condition
...................

 -- 類別: asyncio.Condition (lock=None)

     一個條件 (codition) 物件。不支援執行緒安全。

     一個 asyncio 條件原始物件可以被任務用來等待某事件發生，並獲得一個共
     享資源的獨佔存取權。

     本質上，一個 Condition 物件會結合 *note Event: a15. 和 *note Lock:
     a14. 的功能。多個 Condition 物件共享一個 Lock 是有可能發生的，這能
     夠協調關注同一共享資源的不同狀態以獲取其獨佔存取權的多個任務。

     可選的 'lock' 引數必須是一個 *note Lock: a14. 物件或者為 ‘None’。如
     為後者則一個新的 Lock 物件會被自動建立。

     在 3.10 版的變更: 移除 ‘loop’ 參數。

     使用 Condition 的推薦方式是透過 *note async with: 57a. 陳述式：

          cond = asyncio.Condition()

          # ... later
          async with cond:
              await cond.wait()

     這等價於：

          cond = asyncio.Condition()

          # ... later
          await cond.acquire()
          try:
              await cond.wait()
          finally:
              cond.release()

      -- 方法: coroutine acquire ()

          獲取底層的鎖。

          此方法會持續等待直到底層的鎖為 'unlocked'，並將其設為 'locked'
          並回傳 ‘True’。

      -- 方法: notify (n=1)

          Wake up 'n' tasks (1 by default) waiting on this condition.
          If fewer than 'n' tasks are waiting they are all awakened.

          在此方法被呼叫前必須先獲得鎖，並在之後立刻將其釋放。如果呼叫於
          一個 'unlocked' 的鎖則 *note RuntimeError: 179. 錯誤會被引發。

      -- 方法: locked ()

          如果已獲取底層的鎖則回傳 ‘True’。

      -- 方法: notify_all ()

          喚醒所有正在等待此條件的任務。

          這個方法的行為就像 *note notify(): 1570.，但會喚醒所有正在等待
          的任務。

          在此方法被呼叫前必須先獲得鎖，並在之後立刻將其釋放。如果呼叫於
          一個 'unlocked' 的鎖則 *note RuntimeError: 179. 錯誤會被引發。

      -- 方法: release ()

          釋放底層的鎖。

          當調用於一個未被解開的鎖之上時，會引發一個 *note RuntimeError:
          179.。

      -- 方法: coroutine wait ()

          持續等待直到被通知 (notify)。

          當此方法被呼叫時，如果呼叫它的任務還沒有獲取鎖的話，*note
          RuntimeError: 179. 會被引發。

          此方法會釋放底層的鎖，然後持續阻塞直到被 *note notify(): 1570.
          或 *note notify_all(): 311e. 的呼叫所喚醒。一但被喚醒，
          Condition 會重新獲取該鎖且此方法會回傳 ‘True’。

          Note that a task 'may' return from this call spuriously, which
          is why the caller should always re-check the state and be
          prepared to *note wait(): 426. again.  For this reason, you
          may prefer to use *note wait_for(): 5a4. instead.

      -- 方法: coroutine wait_for (predicate)

          持續等待直到謂語 (predicate) 成為 'true'。

          The predicate must be a callable which result will be
          interpreted as a boolean value.  The method will repeatedly
          *note wait(): 426. until the predicate evaluates to 'true'.
          The final value is the return value.


File: python.info,  Node: Semaphore,  Next: BoundedSemaphore,  Prev: Condition,  Up: 同步化原始物件 Synchronization Primitives

5.18.1.33 Semaphore
...................

 -- 類別: asyncio.Semaphore (value=1)

     一個旗號 (semaphore) 物件。不支援執行緒安全。

     一個旗號物件會管理一個內部計數器，會在每次呼叫 *note acquire():
     159c. 時減少一、每次呼叫 *note release(): 3122. 時增加一。此計數器
     永遠不會少於零；當 *note acquire(): 159c. 發現它是零時，它會持續阻
     塞並等待某任務呼叫 *note release(): 3122.。

     可選的 'value' 引數給定了內部計數器的初始值（預設為 ‘1’）。如給定的
     值少於 ‘0’ 則 *note ValueError: 1e7. 會被引發。

     在 3.10 版的變更: 移除 ‘loop’ 參數。

     使用 Semaphore 的推薦方式是透過 *note async with: 57a. 陳述式：

          sem = asyncio.Semaphore(10)

          # ... later
          async with sem:
              # work with shared resource

     這等價於：

          sem = asyncio.Semaphore(10)

          # ... later
          await sem.acquire()
          try:
              # work with shared resource
          finally:
              sem.release()

      -- 方法: coroutine acquire ()

          獲取一個旗號。

          如果內部計數器大於零，將其減一並立刻回傳 ‘True’。如果為零，則
          持續等待直到 *note release(): 3122. 被呼叫，並回傳 ‘True’。

      -- 方法: locked ()

          如果旗號無法立即被取得則回傳 ‘True’。

      -- 方法: release ()

          釋放一個旗號，並為其內部的計數器數值增加一。可以把一個正在等待
          獲取旗號的任務叫醒。

          和 *note BoundedSemaphore: a18. 不同，*note Semaphore: a17. 允
          許 ‘release()’ 的呼叫次數多於 ‘acquire()’。


File: python.info,  Node: BoundedSemaphore,  Next: Barrier,  Prev: Semaphore,  Up: 同步化原始物件 Synchronization Primitives

5.18.1.34 BoundedSemaphore
..........................

 -- 類別: asyncio.BoundedSemaphore (value=1)

     一個有界的旗號物件。不支援執行緒安全。

     Bounded Semaphore 是 *note Semaphore: a17. 的另一版本，如果其內部的
     計數器數值增加至大於初始 'value' 值的話，*note ValueError: 1e7. 會
     在 *note release(): 3122. 時被引發。

     在 3.10 版的變更: 移除 ‘loop’ 參數。


File: python.info,  Node: Barrier,  Prev: BoundedSemaphore,  Up: 同步化原始物件 Synchronization Primitives

5.18.1.35 Barrier
.................

 -- 類別: asyncio.Barrier (parties)

     一個屏障 (barrier) 物件。不支援執行緒安全。

     A barrier is a simple synchronization primitive that allows to
     block until 'parties' number of tasks are waiting on it.  Tasks can
     wait on the *note wait(): 3126. method and would be blocked until
     the specified number of tasks end up waiting on *note wait(): 3126.
     At that point all of the waiting tasks would unblock
     simultaneously.

     *note async with: 57a. can be used as an alternative to awaiting on
     *note wait(): 3126.

     The barrier can be reused any number of times.  範例：

          async def example_barrier():
             # barrier with 3 parties
             b = asyncio.Barrier(3)

             # create 2 new waiting tasks
             asyncio.create_task(b.wait())
             asyncio.create_task(b.wait())

             await asyncio.sleep(0)
             print(b)

             # The third .wait() call passes the barrier
             await b.wait()
             print(b)
             print("barrier passed")

             await asyncio.sleep(0)
             print(b)

          asyncio.run(example_barrier())

     Result of this example is:

          <asyncio.locks.Barrier object at 0x... [filling, waiters:2/3]>
          <asyncio.locks.Barrier object at 0x... [draining, waiters:0/3]>
          barrier passed
          <asyncio.locks.Barrier object at 0x... [filling, waiters:0/3]>

     在 3.11 版被加入.

      -- 方法: coroutine wait ()

          Pass the barrier.  When all the tasks party to the barrier
          have called this function, they are all unblocked
          simultaneously.

          When a waiting or blocked task in the barrier is cancelled,
          this task exits the barrier which stays in the same state.  If
          the state of the barrier is "filling", the number of waiting
          task decreases by 1.

          The return value is an integer in the range of 0 to
          ‘parties-1’, different for each task.  This can be used to
          select a task to do some special housekeeping, e.g.:

               ...
               async with barrier as position:
                  if position == 0:
                     # Only one task prints this
                     print('End of *draining phase*')

          This method may raise a *note BrokenBarrierError: 5a7.
          exception if the barrier is broken or reset while a task is
          waiting.  It could raise a *note CancelledError: 19e. if a
          task is cancelled.

      -- 方法: coroutine reset ()

          Return the barrier to the default, empty state.  Any tasks
          waiting on it will receive the *note BrokenBarrierError: 5a7.
          exception.

          If a barrier is broken it may be better to just leave it and
          create a new one.

      -- 方法: coroutine abort ()

          Put the barrier into a broken state.  This causes any active
          or future calls to *note wait(): 426. to fail with the *note
          BrokenBarrierError: 5a7.  Use this for example if one of the
          tasks needs to abort, to avoid infinite waiting tasks.

      -- 屬性: parties

          The number of tasks required to pass the barrier.

      -- 屬性: n_waiting

          The number of tasks currently waiting in the barrier while
          filling.

      -- 屬性: broken

          A boolean that is ‘True’ if the barrier is in the broken
          state.

 -- 例外: asyncio.BrokenBarrierError

     This exception, a subclass of *note RuntimeError: 179, is raised
     when the *note Barrier: 5a6. object is reset or broken.

__________________________________________________________________

在 3.9 版的變更: 透過 ‘await lock’ 或 ‘yield from lock’ 和/或 *note
with: 577. 陳述式 (‘with await lock’, ‘with (yield from lock)’) 來獲取鎖
的方式已被移除。請改用 ‘async with lock’。


File: python.info,  Node: 子行程,  Next: 佇列 Queues,  Prev: 同步化原始物件 Synchronization Primitives,  Up: asyncio --- 非同步 I/O

5.18.1.36 子行程
................

'原始碼：'Lib/asyncio/subprocess.py(1)、
Lib/asyncio/base_subprocess.py(2)

__________________________________________________________________

This section describes high-level async/await asyncio APIs to create and
manage subprocesses.  Here's an example of how asyncio can run a shell
command and obtain its result:

     import asyncio

     async def run(cmd):
         proc = await asyncio.create_subprocess_shell(
             cmd,
             stdout=asyncio.subprocess.PIPE,
             stderr=asyncio.subprocess.PIPE)

         stdout, stderr = await proc.communicate()

         print(f'[{cmd!r} exited with {proc.returncode}]')
         if stdout:
             print(f'[stdout]\n{stdout.decode()}')
         if stderr:
             print(f'[stderr]\n{stderr.decode()}')

     asyncio.run(run('ls /zzz'))

will print:

     ['ls /zzz' exited with 1]
     [stderr]
     ls: /zzz: No such file or directory

Because all asyncio subprocess functions are asynchronous and asyncio
provides many tools to work with such functions, it is easy to execute
and monitor multiple subprocesses in parallel.  It is indeed trivial to
modify the above example to run several commands simultaneously:

     async def main():
         await asyncio.gather(
             run('ls /zzz'),
             run('sleep 1; echo "hello"'))

     asyncio.run(main())

另請參閱*note Examples: 3130.。

* Menu:

* 建立子行程::
* 常數: 常數<6>.
* Interacting with Subprocesses::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/asyncio/subprocess.py

   (2) 
https://github.com/python/cpython/tree/3.13/Lib/asyncio/base_subprocess.py


File: python.info,  Node: 建立子行程,  Next: 常數<6>,  Up: 子行程

5.18.1.37 建立子行程
....................

 -- 函式: coroutine asyncio.create_subprocess_exec (program, *args,
          stdin=None, stdout=None, stderr=None, limit=None, **kwds)

     Create a subprocess.

     The 'limit' argument sets the buffer limit for *note StreamReader:
     17c8. wrappers for ‘Process.stdout’ and ‘Process.stderr’ (if *note
     subprocess.PIPE: b2d. is passed to 'stdout' and 'stderr'
     arguments).

     Return a *note Process: 3132. instance.

     See the documentation of *note loop.subprocess_exec(): 3133. for
     other parameters.

     在 3.10 版的變更: Removed the 'loop' parameter.

 -- 函式: coroutine asyncio.create_subprocess_shell (cmd, stdin=None,
          stdout=None, stderr=None, limit=None, **kwds)

     Run the 'cmd' shell command.

     The 'limit' argument sets the buffer limit for *note StreamReader:
     17c8. wrappers for ‘Process.stdout’ and ‘Process.stderr’ (if *note
     subprocess.PIPE: b2d. is passed to 'stdout' and 'stderr'
     arguments).

     Return a *note Process: 3132. instance.

     See the documentation of *note loop.subprocess_shell(): 3134. for
     other parameters.

          重要: It is the application's responsibility to ensure that
          all whitespace and special characters are quoted appropriately
          to avoid shell injection(1) vulnerabilities.  The *note
          shlex.quote(): 10c4. function can be used to properly escape
          whitespace and special shell characters in strings that are
          going to be used to construct shell commands.

     在 3.10 版的變更: Removed the 'loop' parameter.

     備註: Subprocesses are available for Windows if a *note
     ProactorEventLoop: 5ae. is used.  See *note Subprocess Support on
     Windows: 3135. for details.

也參考
......

asyncio also has the following 'low-level' APIs to work with
subprocesses: *note loop.subprocess_exec(): 3133, *note
loop.subprocess_shell(): 3134, *note loop.connect_read_pipe(): 3136,
*note loop.connect_write_pipe(): 3137, as well as the *note Subprocess
Transports: 3138. and *note Subprocess Protocols: 3139.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Shell_injection#Shell_injection


File: python.info,  Node: 常數<6>,  Next: Interacting with Subprocesses,  Prev: 建立子行程,  Up: 子行程

5.18.1.38 常數
..............

 -- 資料: asyncio.subprocess.PIPE

     Can be passed to the 'stdin', 'stdout' or 'stderr' parameters.

     If 'PIPE' is passed to 'stdin' argument, the *note Process.stdin:
     313c. attribute will point to a ‘StreamWriter’ instance.

     If 'PIPE' is passed to 'stdout' or 'stderr' arguments, the *note
     Process.stdout: 313d. and *note Process.stderr: 313e. attributes
     will point to ‘StreamReader’ instances.

 -- 資料: asyncio.subprocess.STDOUT

     Special value that can be used as the 'stderr' argument and
     indicates that standard error should be redirected into standard
     output.

 -- 資料: asyncio.subprocess.DEVNULL

     Special value that can be used as the 'stdin', 'stdout' or 'stderr'
     argument to process creation functions.  It indicates that the
     special file *note os.devnull: 1939. will be used for the
     corresponding subprocess stream.


File: python.info,  Node: Interacting with Subprocesses,  Prev: 常數<6>,  Up: 子行程

5.18.1.39 Interacting with Subprocesses
.......................................

Both *note create_subprocess_exec(): a1a. and *note
create_subprocess_shell(): a1b. functions return instances of the
'Process' class.  'Process' is a high-level wrapper that allows
communicating with subprocesses and watching for their completion.

 -- 類別: asyncio.subprocess.Process

     An object that wraps OS processes created by the
     ‘create_subprocess_exec()’ and ‘create_subprocess_shell()’
     functions.

     This class is designed to have a similar API to the *note
     subprocess.Popen: 17d. class, but there are some notable
     differences:

        * unlike Popen, Process instances do not have an equivalent to
          the *note poll(): 304e. method;

        * the *note communicate(): 162d. and *note wait(): 3142. methods
          don't have a 'timeout' parameter: use the *note wait_for():
          5a4. function;

        * the *note Process.wait(): 3142. method is asynchronous,
          whereas *note subprocess.Popen.wait(): c8b. method is
          implemented as a blocking busy loop;

        * the 'universal_newlines' parameter is not supported.

     This class is *note not thread safe: 30dd.

     See also the *note Subprocess and Threads: 3143. section.

      -- 方法: coroutine wait ()

          Wait for the child process to terminate.

          Set and return the *note returncode: 3144. attribute.

               備註: This method can deadlock when using ‘stdout=PIPE’
               or ‘stderr=PIPE’ and the child process generates so much
               output that it blocks waiting for the OS pipe buffer to
               accept more data.  Use the *note communicate(): 162d.
               method when using pipes to avoid this condition.

      -- 方法: coroutine communicate (input=None)

          Interact with process:

            1. send data to 'stdin' (if 'input' is not ‘None’);

            2. closes 'stdin';

            3. read data from 'stdout' and 'stderr', until EOF is
               reached;

            4. wait for process to terminate.

          The optional 'input' argument is the data (*note bytes: 1a5.
          object) that will be sent to the child process.

          Return a tuple ‘(stdout_data, stderr_data)’.

          If either *note BrokenPipeError: fff. or *note
          ConnectionResetError: 1002. exception is raised when writing
          'input' into 'stdin', the exception is ignored.  This
          condition occurs when the process exits before all data are
          written into 'stdin'.

          If it is desired to send data to the process' 'stdin', the
          process needs to be created with ‘stdin=PIPE’.  Similarly, to
          get anything other than ‘None’ in the result tuple, the
          process has to be created with ‘stdout=PIPE’ and/or
          ‘stderr=PIPE’ arguments.

          Note, that the data read is buffered in memory, so do not use
          this method if the data size is large or unlimited.

          在 3.12 版的變更: 'stdin' gets closed when ‘input=None’ too.

      -- 方法: send_signal (signal)

          Sends the signal 'signal' to the child process.

               備註: On Windows, *note SIGTERM: 134d. is an alias for
               *note terminate(): 3145.  ‘CTRL_C_EVENT’ and
               ‘CTRL_BREAK_EVENT’ can be sent to processes started with
               a 'creationflags' parameter which includes
               ‘CREATE_NEW_PROCESS_GROUP’.

      -- 方法: terminate ()

          Stop the child process.

          On POSIX systems this method sends *note SIGTERM: 134d. to the
          child process.

          On Windows the Win32 API function ‘TerminateProcess()’ is
          called to stop the child process.

      -- 方法: kill ()

          Kill the child process.

          On POSIX systems this method sends ‘SIGKILL’ to the child
          process.

          On Windows this method is an alias for *note terminate():
          3145.

      -- 屬性: stdin

          Standard input stream (‘StreamWriter’) or ‘None’ if the
          process was created with ‘stdin=None’.

      -- 屬性: stdout

          Standard output stream (‘StreamReader’) or ‘None’ if the
          process was created with ‘stdout=None’.

      -- 屬性: stderr

          Standard error stream (‘StreamReader’) or ‘None’ if the
          process was created with ‘stderr=None’.

          警告: Use the *note communicate(): 162d. method rather than
          *note process.stdin.write(): 313c, *note await
          process.stdout.read(): 313d. or *note await
          process.stderr.read(): 313e.  This avoids deadlocks due to
          streams pausing reading or writing and blocking the child
          process.

      -- 屬性: pid

          Process identification number (PID).

          Note that for processes created by the
          ‘create_subprocess_shell()’ function, this attribute is the
          PID of the spawned shell.

      -- 屬性: returncode

          Return code of the process when it exits.

          A ‘None’ value indicates that the process has not terminated
          yet.

          A negative value ‘-N’ indicates that the child was terminated
          by signal ‘N’ (POSIX only).

* Menu:

* 子行程與線程::
* 範例: 範例<21>.


File: python.info,  Node: 子行程與線程,  Next: 範例<21>,  Up: Interacting with Subprocesses

5.18.1.40 子行程與線程
......................

Standard asyncio event loop supports running subprocesses from different
threads by default.

On Windows subprocesses are provided by *note ProactorEventLoop: 5ae.
only (default), *note SelectorEventLoop: 5ad. has no subprocess support.

On UNIX 'child watchers' are used for subprocess finish waiting, see
*note Process Watchers: 3149. for more info.

在 3.8 版的變更: UNIX switched to use *note ThreadedChildWatcher: 422.
for spawning subprocesses from different threads without any limitation.

Spawning a subprocess with 'inactive' current child watcher raises *note
RuntimeError: 179.

Note that alternative event loop implementations might have own
limitations; please refer to their documentation.

也參考
......

The *note Concurrency and multithreading in asyncio: 30dd. section.


File: python.info,  Node: 範例<21>,  Prev: 子行程與線程,  Up: Interacting with Subprocesses

5.18.1.41 範例
..............

An example using the *note Process: 3132. class to control a subprocess
and the *note StreamReader: 17c8. class to read from its standard
output.  The subprocess is created by the *note
create_subprocess_exec(): a1a. function:

     import asyncio
     import sys

     async def get_date():
         code = 'import datetime; print(datetime.datetime.now())'

         # Create the subprocess; redirect the standard output
         # into a pipe.
         proc = await asyncio.create_subprocess_exec(
             sys.executable, '-c', code,
             stdout=asyncio.subprocess.PIPE)

         # Read one line of output.
         data = await proc.stdout.readline()
         line = data.decode('ascii').rstrip()

         # Wait for the subprocess exit.
         await proc.wait()
         return line

     date = asyncio.run(get_date())
     print(f"Current date: {date}")

See also the *note same example: 314b. written using low-level APIs.


File: python.info,  Node: 佇列 Queues,  Next: 例外<8>,  Prev: 子行程,  Up: asyncio --- 非同步 I/O

5.18.1.42 佇列 (Queues)
.......................

'原始碼：'Lib/asyncio/queues.py(1)

__________________________________________________________________

asyncio 佇列被設計成與 *note queue: a4. 模組類似。儘管 asyncio 佇列不支
援執行緒安全 (thread-safe)，但他們是被設計來專用於 async/await 程式。

注意 asyncio 的佇列沒有 'timeout' 參數；請使用 *note asyncio.wait_for():
5a4. 函式來為佇列新增具有超時 (timeout) 設定的操作。

另請參閱下方 *note Examples: 314e.。

* Menu:

* Queue::
* Priority Queue（優先佇列）::
* LIFO Queue::
* 例外: 例外<7>.
* 範例: 範例<22>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/asyncio/queues.py


File: python.info,  Node: Queue,  Next: Priority Queue（優先佇列）,  Up: 佇列 Queues

5.18.1.43 Queue
...............

 -- 類別: asyncio.Queue (maxsize=0)

     先進先出 (FIFO) 佇列。

     如果 'maxsize' 小於或等於零，則佇列尺寸是無限制的。如果是大於 ‘0’ 的
     整數，則當佇列達到 'maxsize' 時，‘await put()’ 將會阻塞 (block)，直
     到某個元素被 *note get(): 3150. 取出。

     不像標準函式庫中執行緒類型的 *note queue: a4.，佇列的尺寸一直是已知
     的，可以透過呼叫 *note qsize(): 3151. 方法回傳。

     在 3.10 版的變更: 移除 'loop' 參數。

     這個類別是*note 不支援執行緒安全的: 30dd.。

      -- 屬性: maxsize

          佇列中可存放的元素數量。

      -- 方法: empty ()

          如果佇列為空則回傳 ‘True’，否則回傳 ‘False’。

      -- 方法: full ()

          如果有 *note maxsize: 3152. 個條目在佇列中，則回傳 ‘True’。

          如果佇列用 ‘maxsize=0’ （預設）初始化，則 *note full(): 3154.
          永遠不會回傳 ‘True’。

      -- 方法: coroutine get ()

          從佇列中刪除並回傳一個元素。如果佇列為空，則持續等待直到佇列中
          有元素。

          Raises *note QueueShutDown: 197. if the queue has been shut
          down and is empty, or if the queue has been shut down
          immediately.

      -- 方法: get_nowait ()

          如果佇列內有值則立即回傳佇列中的元素，否則引發 *note
          QueueEmpty: 3156.。

      -- 方法: coroutine join ()

          持續阻塞直到佇列中所有的元素都被接收和處理完畢。

          當條目新增到佇列的時候，未完成任務的計數就會增加。每當一個消耗
          者 (consumer) 協程呼叫 *note task_done(): d6f.，表示這個條目已
          經被取回且被它包含的所有工作都已完成，未完成任務計數就會減少。
          當未完成計數降到零的時候，*note join(): d6e. 阻塞會被解除
          (unblock)。

      -- 方法: coroutine put (item)

          將一個元素放進佇列。如果佇列滿了，在新增元素之前，會持續等待直
          到有空閒插槽 (free slot) 能被使用。

          Raises *note QueueShutDown: 197. if the queue has been shut
          down.

      -- 方法: put_nowait (item)

          不阻塞地將一個元素放入佇列。

          如果沒有立即可用的空閒插槽，引發 *note QueueFull: 3159.。

      -- 方法: qsize ()

          回傳佇列中的元素數量。

      -- 方法: shutdown (immediate=False)

          Shut down the queue, making *note get(): 3150. and *note
          put(): 3157. raise *note QueueShutDown: 197.

          By default, *note get(): 3150. on a shut down queue will only
          raise once the queue is empty.  Set 'immediate' to true to
          make *note get(): 3150. raise immediately instead.

          All blocked callers of *note put(): 3157. and *note get():
          3150. will be unblocked.  If 'immediate' is true, a task will
          be marked as done for each remaining item in the queue, which
          may unblock callers of *note join(): d6e.

          在 3.13 版被加入.

      -- 方法: task_done ()

          表示前面一個排隊的任務已經完成。

          由佇列消耗者使用。對於每個用於獲取一個任務的 *note get():
          3150.，接續的 *note task_done(): d6f. 呼叫會告訴佇列這個任務的
          處理已經完成。

          如果 *note join(): d6e. 當前正在阻塞，在所有項目都被處理後會解
          除阻塞（意味著每個以 *note put(): 3157. 放進佇列的條目都會收到
          一個 *note task_done(): d6f.）。

          ‘shutdown(immediate=True)’ calls *note task_done(): d6f. for
          each remaining item in the queue.

          如果被呼叫的次數多於放入佇列中的項目數量，將引發 *note
          ValueError: 1e7.。


File: python.info,  Node: Priority Queue（優先佇列）,  Next: LIFO Queue,  Prev: Queue,  Up: 佇列 Queues

5.18.1.44 Priority Queue（優先佇列）
....................................

 -- 類別: asyncio.PriorityQueue

     *note Queue: a19. 的變形；按優先順序取出條目 (最小的先取出)。

     條目通常是 ‘(priority_number, data)’ 形式的 tuple（元組）。


File: python.info,  Node: LIFO Queue,  Next: 例外<7>,  Prev: Priority Queue（優先佇列）,  Up: 佇列 Queues

5.18.1.45 LIFO Queue
....................

 -- 類別: asyncio.LifoQueue

     *note Queue: a19. 的變形，先取出最近新增的條目（後進先出）。


File: python.info,  Node: 例外<7>,  Next: 範例<22>,  Prev: LIFO Queue,  Up: 佇列 Queues

5.18.1.46 例外
..............

 -- 例外: asyncio.QueueEmpty

     當佇列為空的時候，呼叫 *note get_nowait(): 3155. 方法會引發這個例外
     。

 -- 例外: asyncio.QueueFull

     當佇列中條目數量已經達到它的 'maxsize' 時，呼叫 *note put_nowait():
     3158. 方法會引發這個例外。

 -- 例外: asyncio.QueueShutDown

     Exception raised when *note put(): 3157. or *note get(): 3150. is
     called on a queue which has been shut down.

     在 3.13 版被加入.


File: python.info,  Node: 範例<22>,  Prev: 例外<7>,  Up: 佇列 Queues

5.18.1.47 範例
..............

佇列能被用於多個並行任務的工作分配：

     import asyncio
     import random
     import time


     async def worker(name, queue):
         while True:
             # Get a "work item" out of the queue.
             sleep_for = await queue.get()

             # Sleep for the "sleep_for" seconds.
             await asyncio.sleep(sleep_for)

             # Notify the queue that the "work item" has been processed.
             queue.task_done()

             print(f'{name} has slept for {sleep_for:.2f} seconds')


     async def main():
         # Create a queue that we will use to store our "workload".
         queue = asyncio.Queue()

         # Generate random timings and put them into the queue.
         total_sleep_time = 0
         for _ in range(20):
             sleep_for = random.uniform(0.05, 1.0)
             total_sleep_time += sleep_for
             queue.put_nowait(sleep_for)

         # Create three worker tasks to process the queue concurrently.
         tasks = []
         for i in range(3):
             task = asyncio.create_task(worker(f'worker-{i}', queue))
             tasks.append(task)

         # Wait until the queue is fully processed.
         started_at = time.monotonic()
         await queue.join()
         total_slept_for = time.monotonic() - started_at

         # Cancel our worker tasks.
         for task in tasks:
             task.cancel()
         # Wait until all worker tasks are cancelled.
         await asyncio.gather(*tasks, return_exceptions=True)

         print('====')
         print(f'3 workers slept in parallel for {total_slept_for:.2f} seconds')
         print(f'total expected sleep time: {total_sleep_time:.2f} seconds')


     asyncio.run(main())


File: python.info,  Node: 例外<8>,  Next: 事件迴圈,  Prev: 佇列 Queues,  Up: asyncio --- 非同步 I/O

5.18.1.48 例外
..............

'原始碼：'Lib/asyncio/exceptions.py(1)

__________________________________________________________________

 -- 例外: asyncio.TimeoutError

     *note TimeoutError: 7d9. 的一個已被棄用的別名，當操作已超過規定的截
     止時間時被引發。

     在 3.11 版的變更: 此 class 是 *note TimeoutError: 7d9. 的一個別名。

 -- 例外: asyncio.CancelledError

     該操作已被取消。

     當 asyncio Task 被取消時，可以捕獲此例外以執行客製化操作。在幾乎所
     有情況下，該例外必須重新被引發。

     在 3.8 版的變更: *note CancelledError: 19e. 現在是 *note
     BaseException: 55f. 而非 *note Exception: 97d. 的子類別。

 -- 例外: asyncio.InvalidStateError

     *note Task: 480. 或 *note Future: b74. 的無效內部狀態。

     可以在像是為已設定結果值的 'Future' 物件設定結果值的情況下引發。

 -- 例外: asyncio.SendfileNotAvailableError

     "sendfile" 系統呼叫不適用於給定的 socket 或檔案型別。

     一個 *note RuntimeError: 179. 的子類別。

 -- 例外: asyncio.IncompleteReadError

     請求的讀取操作未全部完成。

     由 *note asyncio 串流 APIs: 30b0. 引發。

     此例外是 *note EOFError: 126c. 的子類別。

      -- 屬性: expected

          預期的位元組總數 (*note int: 23c.)。

      -- 屬性: partial

          串流結束之前讀取的 *note bytes: 1a5. 字串。

 -- 例外: asyncio.LimitOverrunError

     在查詢分隔符號 (separator) 時達到緩衝區 (buffer) 大小限制。

     由 *note asyncio 串流 APIs: 30b0. 引發。

      -- 屬性: consumed

          要消耗的位元組總數。

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/asyncio/exceptions.py


File: python.info,  Node: 事件迴圈,  Next: Futures,  Prev: 例外<8>,  Up: asyncio --- 非同步 I/O

5.18.1.49 事件迴圈
..................

'原始碼：' Lib/asyncio/events.py(1)、Lib/asyncio/base_events.py(2)

__________________________________________________________________

前言
....

事件迴圈是每個 asyncio 應用程式的核心。事件迴圈執行非同步任務和回呼、執
行網路 IO 操作並啟動子行程。

應用程式開發人員通常應使用高階的 asyncio 函式，例如 *note asyncio.run():
423.，並且很少需要參照事件迴圈物件或呼叫其方法。本節主要針對那些需要更細
粒度控制事件迴圈行為的低階程式碼、函式庫和框架的作者。

取得事件迴圈
............

以下的低階函式可用於取得、設置或建立事件迴圈：

 -- 函式: asyncio.get_running_loop ()

     在當前作業系統執行緒中回傳正在運行的事件迴圈。

     如果沒有運行的事件迴圈，則引發 *note RuntimeError: 179.。

     此函式只能從協程或回呼函式中呼叫。

     在 3.7 版被加入.

 -- 函式: asyncio.get_event_loop ()

     取得目前的事件迴圈。

     當從協程或回呼函式呼叫此函式（例如，使用 call_soon 或類似的 API 於
     排程呼叫），此函式將永遠回傳正在運行的事件迴圈。

     如果沒有設定正在運行的事件迴圈，該函式將回傳
     ‘get_event_loop_policy().get_event_loop()’ 呼叫的結果。

     由於此函式具有相當複雜的行為（尤其是在使用自訂事件迴圈策略時），在
     協程和回呼函式中，建議使用 *note get_running_loop(): aae. 函式，而
     不是 *note get_event_loop(): 2a3.。

     如上所述，可以考慮使用高階的 *note asyncio.run(): 423. 函式，而不是
     使用這些較低階的函式手動建立和關閉事件迴圈。

     在 3.12 版之後被棄用: 如果沒有當前事件迴圈，則會發出棄用警告。在未
     來的某個 Python 發行版中，這將變成錯誤。

 -- 函式: asyncio.set_event_loop (loop)

     將 'loop' 設置為當前 OS 執行緒的當前事件迴圈。

 -- 函式: asyncio.new_event_loop ()

     建立並回傳新的事件迴圈物件。

請注意 *note get_event_loop(): 2a3.、*note set_event_loop(): 16cf. 和
*note new_event_loop(): 30bd. 函式的行為可以透過*note
設定自訂事件迴圈策略: 3168.進行調整。

目錄
....

本頁文件包含以下章節：

   * *note 事件迴圈方法: 3169.章節是事件迴圈 API 們的參照文件；

   * *note 回呼處理: 316a.章節記錄了從排程方法（如 *note
     loop.call_soon(): aa7. 和 *note loop.call_later(): aa9.）回傳的
     *note Handle: 19a9. 和 *note TimerHandle: 166f. 實例；

   * *note Server 物件: 316b.章節記錄了從事件迴圈方法（如 *note
     loop.create_server(): ab6.）回傳的資料型別；

   * *note 事件迴圈實作: 316c.章節記錄了 *note SelectorEventLoop: 5ad. 和
     *note ProactorEventLoop: 5ae. 類別；

   * *note 範例: 316d.章節展示了如何使用一些事件迴圈 API。

* Menu:

* 事件迴圈方法::
* 回呼處理::
* Server 物件::
* 事件迴圈實作::
* 範例: 範例<23>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/asyncio/events.py

   (2) 
https://github.com/python/cpython/tree/3.13/Lib/asyncio/base_events.py


File: python.info,  Node: 事件迴圈方法,  Next: 回呼處理,  Up: 事件迴圈

5.18.1.50 事件迴圈方法
......................

事件迴圈提供以下'低階' API：

* Menu:

* 啟動和停止迴圈::
* 排程回呼函式::
* 排程延遲的回呼函式::
* 建立 Futures 和 Tasks::
* 打開網路連線::
* 建立網路伺服器::
* 傳輸檔案::
* TLS 升級::
* 監視檔案描述器::
* 直接使用 socket 物件::
* DNS::
* 使用管道::
* Unix 訊號::
* 在執行緒池或行程池中執行程式碼::
* 錯誤處理 API::
* 啟用除錯模式::
* 運行子行程::


File: python.info,  Node: 啟動和停止迴圈,  Next: 排程回呼函式,  Up: 事件迴圈方法

5.18.1.51 啟動和停止迴圈
........................

 -- 方法: loop.run_until_complete (future)

     運行直到 'future' （一個 *note Future: b74. 實例）完成。

     如果引數是*note 協程物件: 30af.，則它將被隱式排程為 *note
     asyncio.Task: 480. 運行。

     回傳 Future 的結果或引發其例外。

 -- 方法: loop.run_forever ()

     運行事件迴圈直到 *note stop(): c23. 被呼叫。

     如果在呼叫 *note run_forever(): 3170. 之前呼叫 *note stop(): c23.，
     則迴圈將使用超時為零的方式輪詢 I/O 選擇器，運行所有回應 I/O 事件（
     以及已經排程的事件）的回呼函數，然後退出。

     如果在 *note run_forever(): 3170. 運行時呼叫 *note stop(): c23.，則
     迴圈將運行當前批次的回呼函式，然後退出。請注意，由回呼函式排程的新
     回呼在此情況下不會運行；而是在下次呼叫 *note run_forever(): 3170. 或
     *note run_until_complete(): c1e. 時運行。

 -- 方法: loop.stop ()

     停止事件迴圈。

 -- 方法: loop.is_running ()

     如果事件迴圈當前正在運行，則回傳 ‘True’。

 -- 方法: loop.is_closed ()

     如果事件迴圈已關閉，則回傳 ‘True’。

 -- 方法: loop.close ()

     關閉事件迴圈。

     不得於迴圈運行中呼叫此函式。將丟棄任何待處理的回呼。

     此方法清除所有佇列並關閉執行器，但不等待執行器完成。

     此方法是冪等且不可逆的。在事件迴圈關閉後不應呼叫其他方法。

 -- 方法: coroutine loop.shutdown_asyncgens ()

     排程所有當前打開的*note 非同步產生器: 1f14.物件使用 *note aclose():
     87d. 呼叫來關閉。呼叫此方法後，如果疊代新的非同步產生器，事件迴圈將
     發出警告。應該使用此方法可靠地完成所有已排程的非同步產生器。

     請注意，使用 *note asyncio.run(): 423. 時不需要呼叫此函式。

     範例：

          try:
              loop.run_forever()
          finally:
              loop.run_until_complete(loop.shutdown_asyncgens())
              loop.close()

     在 3.6 版被加入.

 -- 方法: coroutine loop.shutdown_default_executor (timeout=None)

     排程預設執行器的關閉，並等待它加入 *note ThreadPoolExecutor: 6e6. 中
     的所有執行緒。一旦呼叫了此方法，使用預設執行器與 *note
     loop.run_in_executor(): 88e. 將引發 *note RuntimeError: 179.。

     'timeout' 參數指定執行器完成加入所需的時間（以 *note float: 2c8. 秒
     為單位）。預設情況下為 ‘None’，不會限制執行器所花費的時間。

     如果達到 'timeout'，將發出 *note RuntimeWarning: 1a3. 警告，預設執
     行器將立即終止，不等待其執行緒完成加入。

          備註: 使用 *note asyncio.run(): 423. 時請勿呼叫此方法，因為後
          者會自動處理預設執行器的關閉。

     在 3.9 版被加入.

     在 3.12 版的變更: 加入 'timeout' 參數。


File: python.info,  Node: 排程回呼函式,  Next: 排程延遲的回呼函式,  Prev: 啟動和停止迴圈,  Up: 事件迴圈方法

5.18.1.52 排程回呼函式
......................

 -- 方法: loop.call_soon (callback, *args, context=None)

     在事件迴圈的下一次疊代中排程以 'args' 引數呼叫 'callback' *note
     callback: 27f7.。

     回傳 *note asyncio.Handle: 19a9. 的實例，稍後可以用於取消回呼函式。

     回呼函式按照其註冊的順序呼叫。每個回呼函式將被呼叫恰好一次。

     選用的僅限關鍵字引數 'context' 指定了要給 'callback' 執行的自定義
     *note contextvars.Context: 308c.。當未提供 'context' 時，回呼函式使
     用當前情境。

     與 *note call_soon_threadsafe(): aa8. 不同，此方法不是執行緒安全的
     。

 -- 方法: loop.call_soon_threadsafe (callback, *args, context=None)

     這是 *note call_soon(): aa7. 的執行緒安全變體。當從另一個執行緒排程
     回呼函式時，'必須'使用此函式，因為 *note call_soon(): aa7. 不是執行
     緒安全的。

     如果在已關閉的迴圈上呼叫，則引發 *note RuntimeError: 179.。在主應用
     程式關閉時，這可能發生在次要執行緒上。

     請參閱文件的*note 並行和多執行緒: 30dd.部分。

     在 3.7 版的變更: 新增了 'context' 僅限關鍵字參數。詳細資訊請參閱
     PEP 567(1)。

     備註: 大多數 *note asyncio: 8. 排程函式不允許傳遞關鍵字引數。要傳遞
     關鍵字引數，請使用 *note functools.partial(): 356.：

          # will schedule "print("Hello", flush=True)"
          loop.call_soon(
              functools.partial(print, "Hello", flush=True))

     通常使用 partial 物件比使用 lambda 更方便，因為 asyncio 可以在除錯
     和錯誤訊息中更好地呈現 partial 物件。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0567/


File: python.info,  Node: 排程延遲的回呼函式,  Next: 建立 Futures 和 Tasks,  Prev: 排程回呼函式,  Up: 事件迴圈方法

5.18.1.53 排程延遲的回呼函式
............................

事件迴圈提供為回呼函式排程在將來某個時間點才呼叫的機制。事件迴圈使用了單
調時鐘來追蹤時間。

 -- 方法: loop.call_later (delay, callback, *args, context=None)

     排程 'callback' 在給定的 'delay' 秒數後呼叫（可以是整數或浮點數）。

     回傳 *note asyncio.TimerHandle: 166f. 的實例，可用於取消回呼函式。

     'callback' 將只被呼叫恰好一次。如果有兩個回呼函式被排程在完全相同的
     時間，則其呼叫順序是不定的。

     可選的位置引數 'args' 將在呼叫回呼函式時傳遞。如果要使用關鍵字引數
     呼叫回呼函數，請使用 *note functools.partial(): 356.。

     可選的僅限關鍵字 'context' 引數允許為 'callback' 指定自定義的 *note
     contextvars.Context: 308c. 以提供運行。當未提供 'context' 時，將使
     用當前情境。

     在 3.7 版的變更: 新增了 'context' 僅限關鍵字參數。詳細資訊請參閱
     PEP 567(1)。

     在 3.8 版的變更: 在 Python 3.7 及更早版本中，使用預設事件迴圈實作時
     ，'delay' 不能超過一天。這在 Python 3.8 中已經修復。

 -- 方法: loop.call_at (when, callback, *args, context=None)

     排程 'callback' 在給定的絕對時間戳 'when' （整數或浮點數）處呼叫，
     使用與 *note loop.time(): 3177. 相同的時間參照。

     此方法的行為與 *note call_later(): aa9. 相同。

     回傳 *note asyncio.TimerHandle: 166f. 的實例，可用於取消回呼函式。

     在 3.7 版的變更: 新增了 'context' 僅限關鍵字參數。詳細資訊請參閱
     PEP 567(2)。

     在 3.8 版的變更: 在 Python 3.7 及更早版本中，使用預設事件迴圈實作時
     ，'when' 和當前時間之間的差值不能超過一天。這在 Python 3.8 中已經修
     復。

 -- 方法: loop.time ()

     根據事件迴圈的內部單調時鐘，回傳當前時間，以 *note float: 2c8. 值表
     示。

     備註: 
     在 3.8 版的變更: 在 Python 3.7 及更早版本中，超時（相對 'delay' 或
     絕對 'when'）不應超過一天。這在 Python 3.8 中已經修復。

也參考
......

函式 *note asyncio.sleep(): a12.。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0567/

   (2) https://peps.python.org/pep-0567/


File: python.info,  Node: 建立 Futures 和 Tasks,  Next: 打開網路連線,  Prev: 排程延遲的回呼函式,  Up: 事件迴圈方法

5.18.1.54 建立 Futures 和 Tasks
...............................

 -- 方法: loop.create_future ()

     建立附加到事件迴圈的 *note asyncio.Future: b74. 物件。

     這是在 asyncio 中建立 Futures 的首選方式。這允許第三方事件迴圈提供
     Future 物件的替代實作（具有更好的性能或儀器計測表現）。

     在 3.5.2 版被加入.

 -- 方法: loop.create_task (coro, *, name=None, context=None)

     排程執行*note 協程: 30af. 'coro'。回傳 *note Task: 480. 物件。

     第三方事件迴圈可以使用其自己的 *note Task: 480. 子類別以實現互操作
     性（interoperability）。在這種情況下，結果類型是 *note Task: 480. 的
     子類別。

     如果提供了 'name' 引數且不為 ‘None’，則將其設置為任務的名稱，使用
     *note Task.set_name(): 981.。

     可選的僅限關鍵字 'context' 引數允許為 'coro' 指定自定義的 *note
     contextvars.Context: 308c. 以提供運行。當未提供 'context' 時，將建
     立當前情境的副本。

     在 3.8 版的變更: 加入 'name' 參數。

     在 3.11 版的變更: 加入 'context' 參數。

 -- 方法: loop.set_task_factory (factory)

     設置將由 *note loop.create_task(): 980. 使用的任務工廠。

     如果 'factory' 為 ‘None’，將設置預設的任務工廠。否則，'factory' 必
     須是一個具有匹配簽名 ‘(loop, coro, context=None)’ 的 'callable'，其
     中 'loop' 是有效事件迴圈的參照，'coro' 是一個協程物件。該可呼叫物件
     必須回傳一個與 *note asyncio.Future: b74. 相容的物件。

 -- 方法: loop.get_task_factory ()

     回傳任務工廠，如果使用預設任務工廠則回傳 ‘None’。


File: python.info,  Node: 打開網路連線,  Next: 建立網路伺服器,  Prev: 建立 Futures 和 Tasks,  Up: 事件迴圈方法

5.18.1.55 打開網路連線
......................

 -- 方法: coroutine loop.create_connection (protocol_factory, host=None,
          port=None, *, ssl=None, family=0, proto=0, flags=0, sock=None,
          local_addr=None, server_hostname=None,
          ssl_handshake_timeout=None, ssl_shutdown_timeout=None,
          happy_eyeballs_delay=None, interleave=None, all_errors=False)

     打開以 'host' 和 'port' 指定之給定地址的串流傳輸連線。

     根據 'host*（或提供的 *family' 引數）的情況，socket 家族可以是
     *note AF_INET: 1722. 或 *note AF_INET6: 1723.。

     Socket 類型將為 *note SOCK_STREAM: 1286.。

     'protocol_factory' 必須是一個回傳 *note asyncio protocol: 317a. 實
     作的可呼叫函式。

     此方法將嘗試在背景建立連線。成功時，它將回傳一對 ‘(transport,
     protocol)’。

     底層操作的時間軸簡介如下：

       1. 建立連線並為其建立*note 傳輸: 317b.。

       2. 'protocol_factory' 在無引數的情況下被呼叫，並且預計回傳一個
          *note 協定: 317a. 實例。

       3. 通過呼叫其 *note connection_made(): 317c. 方法，將協議實例與傳
          輸連線在一起。

       4. 成功時回傳一個 ‘(transport, protocol)’ 元組。

     建立的傳輸是一個依賴實作的雙向串流。

     其他引數：

        * 若有給定 'ssl' 且非 false，將建立 SSL/TLS 傳輸（預設建立普通
          TCP 傳輸）。如果 'ssl' 為 *note ssl.SSLContext: 276. 物件，則
          使用該情境來建立傳輸；如果 'ssl' 為 *note True: bb4.，則使用
          *note ssl.create_default_context(): 13a. 回傳的預設情境。

          也參考
          ......

          *note SSL/TLS 安全考量: 317d.

        * 'server_hostname' 設置或覆蓋目標伺服器憑證將匹配的主機名稱。僅
          在 'ssl' 不為 ‘None’ 時傳遞。預設情況下，將使用 'host' 引數的
          值。如果 'host' 為空，則沒有預設值，必須傳遞 'server_hostname'
          的值。若 'server_hostname' 為空字串，將停用主機名稱匹配（這是
          一個嚴重的安全風險，可能導致中間人攻擊）。

        * 'family'、'proto'、'flags' 是可選的位址家族、協議和旗標，用於
          傳遞至 getaddrinfo() 進行 'host' 解析。若有給定這些應該都是相
          應 *note socket: b8. 模組常數的整數。

        * 若有給定，'happy_eyeballs_delay' 會啟用此連線的 Happy
          Eyeballs。它應該是一個浮點數，表示等待連線嘗試完成的秒數，然後
          在並行啟動下一次嘗試。這是 RFC 8305(1) 中定義的「連線嘗試延遲
          」。RFC 建議的合理預設值為 ‘0.25’ 秒（250 毫秒）。

        * 'interleave' 控制主機名稱解析為多個 IP 位址時的地址重新排序。
          若為 ‘0’ 或未指定，將不執行重排序，並按 *note getaddrinfo():
          bbb. 回傳的順序嘗試位址。如果指定正整數，則按地址家族交錯排列
          ，給定的整數直譯為 RFC 8305(2) 中定義的「首個地址家族計數」。
          如果未指定 'happy_eyeballs_delay'，則預設值為 ‘0’，如果指定則
          為 ‘1’。

        * 若有給定 'sock' 則其應為已存在且已連線的 *note socket.socket:
          d47. 物件，可供傳輸使用。如果提供了 'sock'，則不應指定 'host'、
          'port'、'family'、'proto'、'flags'、'happy_eyeballs_delay'、
          'interleave' 和 'local_addr' 中的任何一項。

               備註: 引數 'sock' 將 socket 所有權轉移給所建立的傳輸
               socket，請呼叫傳輸的 *note close(): 317e. 方法。

        * 若有給定 'local_addr' 則其為一個 ‘(local_host, local_port)’ 元
          組，用於在本地綁定 socket。將使用 ‘getaddrinfo()’ 查找
          'local_host' 和 'local_port'，方式類似於 'host' 和 'port'。

        * 'ssl_handshake_timeout' （對於 TLS 連線）是等待 TLS 交握的時間
          ，以秒為單位，在那之前若未完成則會中斷連線。如果為 ‘None’ （預
          設值），則會等待 ‘60.0’ 秒。

        * 'ssl_shutdown_timeout' 是等待 SSL 關閉完成以前中斷連線的時間，
          以秒為單位。如果為 ‘None’ （預設值），則會等待 ‘30.0’ 秒。

        * 'all_errors' 決定在無法建立連線時會引發哪些例外。預設情況下，
          只會引發單一 ‘Exception’：如果只有一個例外或所有錯誤訊息相同，
          則引發第一個例外，否則引發包含所有錯誤訊息的單一 ‘OSError’。當
          ‘all_errors’ 為 ‘True’ 時，將引發包含所有例外的
          ‘ExceptionGroup’ （即使只有一個例外）。

     在 3.5 版的變更: 新增 *note ProactorEventLoop: 5ae. 中的 SSL/TLS 支
     援。

     在 3.6 版的變更: 所有 TCP 連線都預設有 *note socket.TCP_NODELAY:
     317f. socket 選項。

     在 3.7 版的變更: 增加 'ssl_handshake_timeout' 參數。

     在 3.8 版的變更: 加入 'happy_eyeballs_delay' 和 'interleave' 參數。

     Happy Eyeballs 演算法：雙協定堆疊主機 (Dual-Stack Hosts) 的成功。當
     伺服器的 IPv4 路徑和協議運作正常，但伺服器的 IPv6 路徑和協議不運作
     時，雙棧用戶端應用程式會比僅具 IPv4 的用戶端體驗到顯著的連線延遲。
     這是不希望的，因為這會導致雙棧用戶端的使用者體驗變差。本文件具體說
     明了減少此用戶可見延遲的演算法要求並提供了一種演算法。

     更多資訊請見： ‘https://datatracker.ietf.org/doc/html/rfc6555’

     在 3.11 版的變更: 增加 'ssl_shutdown_timeout' 參數。

     在 3.12 版的變更: 已新增 'all_errors'。

     也參考
     ......

     函式 *note open_connection(): abb. 是高階的替代 API。它回傳一對
     (*note StreamReader: 17c8, *note StreamWriter: 15fc.) 可直接在
     async/await 程式碼中使用。

 -- 方法: coroutine loop.create_datagram_endpoint (protocol_factory,
          local_addr=None, remote_addr=None, *, family=0, proto=0,
          flags=0, reuse_port=None, allow_broadcast=None, sock=None)

     建立一個資料報連線。

     Socket 家族可以是 *note AF_INET: 1722.、*note AF_INET6: 1723. 或
     *note AF_UNIX: 1724.，視乎 'host'（或提供的 'family' 引數）而定。

     Socket 類型將為 *note SOCK_DGRAM: 1285.。

     'protocol_factory' 必須是可呼叫的函式，回傳 *note protocol: 317a. 實
     作。

     成功時回傳 ‘(transport, protocol)’ 元組。

     其他引數：

        * 'local_addr'，如果提供，是一個 ‘(local_host, local_port)’ 元組
          ，用於在本地綁定 socket。'local_host' 和 'local_port' 使用
          *note getaddrinfo(): bbb. 來查找。

        * 'remote_addr'，如果提供，是一個 ‘(remote_host, remote_port)’ 元
          組，用於將 socket 連線到遠端位址。 'remote_host' 和
          'remote_port' 使用 *note getaddrinfo(): bbb. 來查找。

        * 'family'、'proto' 和 'flags' 是用於傳遞給 *note getaddrinfo():
          bbb. 以解析 'host' 的可選地址家族、協定和旗標。如果提供，這些
          應該都是來自相應的 *note socket: b8. 模組常數的整數。

        * 'reuse_port' 告訴核心允許將此端點綁定到與其他現有端點相同的埠
          ，只要它們在建立時都設定了此旗標。此選項不受 Windows 和某些
          Unix 系統支援。如果未定義 ‘SO_REUSEPORT’ 常數，則不支援此功能
          。

        * 'allow_broadcast' 告訴核心允許此端點向廣播位址發送訊息。

        * 'sock' 可以選擇性地指定，以使用預先存在且已連線的 *note
          socket.socket: d47. 物件供傳輸使用。如果指定，'local_addr' 和
          'remote_addr' 應省略（必須是 *note None: 61b.）。

               備註: 引數 'sock' 將 socket 所有權轉移給所建立的傳輸
               socket，請呼叫傳輸的 *note close(): 317e. 方法。

     請參閱 *note UDP 回應用戶端協議: 3180. 和 *note UDP 回應伺服器協議:
     3181. 範例。

     在 3.4.4 版的變更: 新增 'family'、'proto'、'flags'、
     'reuse_address'、'reuse_port'、'allow_broadcast' 和 'sock' 參數。

     在 3.8 版的變更: 新增對於 Windows 的支援。

     在 3.8.1 版的變更: 不再支援 'reuse_address' 參數，因為使用
     ‘SO_REUSEADDR’ 對於 UDP 存有重大的安全疑慮。明確傳遞
     ‘reuse_address=True’ 將引發例外。

     當具有不同 UID 的多個行程使用 ‘SO_REUSEADDR’ 將 socket 分配給相同的
     UDP socket 地址時，傳入的封包可能會在 socket 之間隨機分佈。

     對於有支援的平台，'reuse_port' 可以用作類似功能的替代方案。使用
     'reuse_port'，將改為使用 ‘SO_REUSEPORT’，該選項明確禁止具有不同 UID
     的行程將 socket 分配給相同的 socket 地址。

     在 3.11 版的變更: 自 Python 3.9.0、3.8.1、3.7.6 和 3.6.10 起，已完
     全移除 'reuse_address' 參數。

 -- 方法: coroutine loop.create_unix_connection (protocol_factory,
          path=None, *, ssl=None, sock=None, server_hostname=None,
          ssl_handshake_timeout=None, ssl_shutdown_timeout=None)

     建立一個 Unix 連線。

     Socket 家族將為 *note AF_UNIX: 1724.；socket 類型將為 *note
     SOCK_STREAM: 1286.。

     成功時回傳 ‘(transport, protocol)’ 元組。

     'path' 是 Unix 域 socket 的名稱，除非指定 'sock' 參數，否則為必填。
     支援抽象 Unix sockets、*note str: 3f2.、*note bytes: 1a5. 和 *note
     Path: 20e. 路徑。

     有關此方法的引數資訊，請參閱 *note loop.create_connection(): 5a8. 方
     法的文件。

     *note 適用: 1c56.：Unix。

     在 3.7 版的變更: 新增 'ssl_handshake_timeout' 參數。'path' 參數現在
     可以是 *note path-like object: ac2.。

     在 3.11 版的變更: 增加 'ssl_shutdown_timeout' 參數。

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc8305.html

   (2) https://datatracker.ietf.org/doc/html/rfc8305.html


File: python.info,  Node: 建立網路伺服器,  Next: 傳輸檔案,  Prev: 打開網路連線,  Up: 事件迴圈方法

5.18.1.56 建立網路伺服器
........................

 -- 方法: coroutine loop.create_server (protocol_factory, host=None,
          port=None, *, family=socket.AF_UNSPEC,
          flags=socket.AI_PASSIVE, sock=None, backlog=100, ssl=None,
          reuse_address=None, reuse_port=None, keep_alive=None,
          ssl_handshake_timeout=None, ssl_shutdown_timeout=None,
          start_serving=True)

     建立一個 TCP 伺服器（socket 類型 *note SOCK_STREAM: 1286.），監聽
     'host' 位址的 'port'。

     回傳一個 *note Server: ab5. 物件。

     引數：

        * 'protocol_factory' 必須是可呼叫的函式，回傳 *note protocol:
          317a. 實作。

        * 可以將 'host' 參數設為幾種類型，以確定伺服器將監聽的位置：

             - 如果 'host' 是字串，則 TCP 伺服器綁定到由 'host' 指定的單
               個網路介面。

             - 如果 'host' 是字串序列，則 TCP 伺服器綁定到序列指定的所有
               網路介面。

             - 若 'host' 是空字串或 ‘None’，則所有介面都被假定並回傳多個
               socket 的清單（可能一個用於 IPv4，另一個用於 IPv6）。

        * 可以設定 'port' 參數以指定伺服器應該監聽的埠。如果是 ‘0’ 或
          ‘None’（預設值），將隨機選擇一個未使用的埠（請注意，如果
          'host' 解析為多個網路介面，將為每個介面隨機選擇不同的隨機埠）
          。

        * 'family' 可以設定為 *note socket.AF_INET: 1722. 或 *note
          AF_INET6: 1723. 以強制使用 IPv4 或 IPv6。如果未設定，'family'
          將從主機名稱決定（預設為 *note AF_UNSPEC: 3183.）。

        * 'flags' 是 *note getaddrinfo(): bbb. 的位元遮罩。

        * 可以可選地指定 'sock' 以使用現有的 socket 物件。如果指定了，
          'host' 和 'port' 不能指定。

               備註: 'sock' 引數將 socket 的所有權轉移給建立的伺服器。要
               關閉 socket，請呼叫伺服器的 *note close(): 30f1. 方法。

        * 'backlog' 是傳遞給 *note listen(): e00. 的最大佇列連線數（預設
          為 100）。

        * 'ssl' 可以設定為 *note SSLContext: 276. 實例以在接受的連線上啟
          用 TLS。

        * 'reuse_address' 告訴內核重用 ‘TIME_WAIT’ 狀態下的本地 socket，
          而不等待其自然超時過期。如果未指定，在 Unix 上將自動設置為
          ‘True’。

        * 'reuse_port' 告訴內核允許此端點繫結到與其他現有端點繫結的相同
          埠，只要它們在建立時都設置了此旗標。此選項在旗標 Windows 上不
          受支援。

        * 'keep_alive' set to ‘True’ keeps connections active by
          enabling the periodic transmission of messages.

     在 3.13 版的變更: Added the 'keep_alive' parameter.

        * （對於 TLS 伺服器）'ssl_handshake_timeout' 是在中斷連線之前等
          待 TLS 握手完成的時間（以秒為單位）。如果為 ‘None’（預設），則
          為 ‘60.0’ 秒。

        * 'ssl_shutdown_timeout' 是等待 SSL 關閉完成以前中斷連線的時間，
          以秒為單位。如果為 ‘None’ （預設值），則會等待 ‘30.0’ 秒。

        * 將 'start_serving' 設置為 ‘True’（預設）將使建立的伺服器立即開
          始接受連接。當設置為 ‘False’ 時，用戶應該等待 *note
          Server.start_serving(): ab7. 或 *note Server.serve_forever():
          ab8. 來使伺服器開始接受連線。

     在 3.5 版的變更: 新增 *note ProactorEventLoop: 5ae. 中的 SSL/TLS 支
     援。

     在 3.5.1 版的變更: 'host' 參數可以是字串序列。

     在 3.6 版的變更: 新增 'ssl_handshake_timeout' 與 'start_serving' 參
     數。所有 TCP 連線都預設有 *note socket.TCP_NODELAY: 317f. socket 選
     項。

     在 3.11 版的變更: 增加 'ssl_shutdown_timeout' 參數。

     也參考
     ......

     *note start_server(): abc. 函式是一個更高階的替代 API，它回傳一對
     *note StreamReader: 17c8. 和 *note StreamWriter: 15fc.，可以在
     async/await 程式碼中使用。

 -- 方法: coroutine loop.create_unix_server (protocol_factory,
          path=None, *, sock=None, backlog=100, ssl=None,
          ssl_handshake_timeout=None, ssl_shutdown_timeout=None,
          start_serving=True, cleanup_socket=True)

     類似 *note loop.create_server(): ab6.，但適用於 *note AF_UNIX:
     1724. socket 家族。

     'path' 是 Unix 域 socket 的名稱，除非提供了 'sock' 引數，否則必須給
     定。支援抽象 Unix sockets、*note str: 3f2.、*note bytes: 1a5. 和
     *note Path: 20e. 路徑。

     If 'cleanup_socket' is true then the Unix socket will automatically
     be removed from the filesystem when the server is closed, unless
     the socket has been replaced after the server has been created.

     有關此方法的引數資訊，請參閱 *note loop.create_server(): ab6. 方法
     的文件。

     *note 適用: 1c56.：Unix。

     在 3.7 版的變更: 新增 'ssl_handshake_timeout' 與 'start_serving' 參
     數。'path' 參數現在可為一個 *note Path: 20e. 物件。

     在 3.11 版的變更: 增加 'ssl_shutdown_timeout' 參數。

     在 3.13 版的變更: Added the 'cleanup_socket' parameter.

 -- 方法: coroutine loop.connect_accepted_socket (protocol_factory,
          sock, *, ssl=None, ssl_handshake_timeout=None,
          ssl_shutdown_timeout=None)

     將已接受的連線包裝成傳輸層/協議對。

     此方法可以由在 asyncio 外接受連線但使用 asyncio 處理連線的伺服器使
     用。

     參數：

        * 'protocol_factory' 必須是可呼叫的函式，回傳 *note protocol:
          317a. 實作。

        * 'sock' 是從 *note socket.accept: d48. 回傳的預先存在的 socket
          物件。

               備註: 引數 'sock' 將 socket 所有權轉移給所建立的傳輸
               socket，請呼叫傳輸的 *note close(): 317e. 方法。

        * 'ssl' 可以設置為 *note SSLContext: 276. 以在已接受的連線上啟用
          SSL。

        * （對於 SSL 連線）'ssl_handshake_timeout' 是在中斷連線之前等待
          SSL 握手完成的時間（以秒為單位）。如果為 ‘None’（預設），則為
          ‘60.0’ 秒。

        * 'ssl_shutdown_timeout' 是等待 SSL 關閉完成以前中斷連線的時間，
          以秒為單位。如果為 ‘None’ （預設值），則會等待 ‘30.0’ 秒。

     回傳 ‘(transport, protocol)’ 對。

     在 3.5.3 版被加入.

     在 3.7 版的變更: 增加 'ssl_handshake_timeout' 參數。

     在 3.11 版的變更: 增加 'ssl_shutdown_timeout' 參數。


File: python.info,  Node: 傳輸檔案,  Next: TLS 升級,  Prev: 建立網路伺服器,  Up: 事件迴圈方法

5.18.1.57 傳輸檔案
..................

 -- 方法: coroutine loop.sendfile (transport, file, offset=0,
          count=None, *, fallback=True)

     通過 'transport' 發送 'file'。回傳發送的總位元組數。

     如果可用，該方法使用高性能 *note os.sendfile(): ab2.。

     'file' 必須是以二進位模式打開的常規檔案物件。

     'offset' 告訴從哪裡開始讀取檔案。如果指定了，'count' 是要傳輸的總位
     元組數，而不是發送檔案直到達到 EOF。即使此方法引發錯誤時，檔案位置
     也始終更新，可以使用 *note file.tell(): 2894. 取得實際發送的位元組
     數。

     將 'fallback' 設置為 ‘True’ 會使 asyncio 在平台不支援 sendfile 系統
     呼叫時（例如 Windows 或 Unix 上的 SSL socket）手動讀取和發送檔案。

     如果系統不支援 'sendfile' 系統呼叫且 'fallback' 為 ‘False’，則引發
     *note SendfileNotAvailableError: 3163.。

     在 3.7 版被加入.


File: python.info,  Node: TLS 升級,  Next: 監視檔案描述器,  Prev: 傳輸檔案,  Up: 事件迴圈方法

5.18.1.58 TLS 升級
..................

 -- 方法: coroutine loop.start_tls (transport, protocol, sslcontext, *,
          server_side=False, server_hostname=None,
          ssl_handshake_timeout=None, ssl_shutdown_timeout=None)

     將基於傳輸的現有連線升級到 TLS。

     建立 TLS 編解碼器實例並在 'transport' 和 'protocol' 之間插入它。編
     解碼器既實作了對於 'transport' 的協議，也實作了對於 'protocol' 的傳
     輸。

     回傳建立的雙介面實例。在 'await' 後，'protocol' 必須停止使用原始的
     'transport'，僅與回傳的物件通信，因為編碼器快取了 'protocol' 端的資
     料，並且與 'transport' 間歇性地交換額外的 TLS session 封包。

     在某些情況下（例如傳入的傳輸已經關閉），此函式可能回傳 ‘None’。

     參數：

        * 'transport' 和 'protocol' 實例，由像 *note create_server():
          ab6. 和 *note create_connection(): 5a8. 等方法回傳。

        * 'sslcontext'：配置好的 *note SSLContext: 276. 實例。

        * 當升級伺服器端連線時（像由 *note create_server(): ab6. 建立的
          那樣）傳遞 ‘True’。

        * 'server_hostname'：設置或覆蓋將用於匹配目標伺服器憑證的主機名
          。

        * 'ssl_handshake_timeout' （對於 TLS 連線）是等待 TLS 交握的時間
          ，以秒為單位，在那之前若未完成則會中斷連線。如果為 ‘None’ （預
          設值），則會等待 ‘60.0’ 秒。

        * 'ssl_shutdown_timeout' 是等待 SSL 關閉完成以前中斷連線的時間，
          以秒為單位。如果為 ‘None’ （預設值），則會等待 ‘30.0’ 秒。

     在 3.7 版被加入.

     在 3.11 版的變更: 增加 'ssl_shutdown_timeout' 參數。


File: python.info,  Node: 監視檔案描述器,  Next: 直接使用 socket 物件,  Prev: TLS 升級,  Up: 事件迴圈方法

5.18.1.59 監視檔案描述器
........................

 -- 方法: loop.add_reader (fd, callback, *args)

     開始監視 'fd' 檔案描述器的讀取可用性，一但 'fd' 可讀取，使用指定引
     數呼叫 'callback'。

 -- 方法: loop.remove_reader (fd)

     停止監視 'fd' 檔案描述器的讀取可用性。如果 'fd' 之前正在監視讀取，
     則回傳 ‘True’。

 -- 方法: loop.add_writer (fd, callback, *args)

     開始監視 'fd' 檔案描述器的寫入可用性，一旦 'fd' 可寫入，使用指定引
     數呼叫 'callback'。

     使用 *note functools.partial(): 356. 向 'callback' *note
     傳送關鍵字引數: 3174.。

 -- 方法: loop.remove_writer (fd)

     停止監視 'fd' 檔案描述器的寫入可用性。如果 'fd' 之前正在監視寫入，
     則回傳 ‘True’。

另請參閱*note 平台支援: 318b.部分以了解這些方法的一些限制。


File: python.info,  Node: 直接使用 socket 物件,  Next: DNS,  Prev: 監視檔案描述器,  Up: 事件迴圈方法

5.18.1.60 直接使用 socket 物件
..............................

一般情況下，使用基於傳輸的 API（如 *note loop.create_connection(): 5a8.
和 *note loop.create_server(): ab6.）的協議實作比直接使用 socket 的實作
更快。然而在某些情況下性能不是關鍵，直接使用 *note socket: d47. 物件更方
便。

 -- 方法: coroutine loop.sock_recv (sock, nbytes)

     從 'sock' 接收最多 'nbytes'。*note socket.recv(): d4a. 的非同步版本
     。

     將接收到的資料作為 bytes 物件回傳。

     'sock' 必須是非阻塞 socket。

     在 3.7 版的變更: 儘管此方法一直記錄為協程方法，但 Python 3.7 之前的
     版本回傳 *note Future: b74.。自 Python 3.7 起，這是 ‘async def’ 方
     法。

 -- 方法: coroutine loop.sock_recv_into (sock, buf)

     從 'sock' 接收資料到 'buf' 緩衝區。仿照阻塞 *note
     socket.recv_into(): 12b1. 方法。

     回傳寫入緩衝區位元組的數目。

     'sock' 必須是非阻塞 socket。

     在 3.7 版被加入.

 -- 方法: coroutine loop.sock_recvfrom (sock, bufsize)

     從 'sock' 接收最多 'bufsize' 大小的資料單元。*note
     socket.recvfrom(): d4b. 的非同步版本。

     回傳一個元組 (received data, remote address)。

     'sock' 必須是非阻塞 socket。

     在 3.11 版被加入.

 -- 方法: coroutine loop.sock_recvfrom_into (sock, buf, nbytes=0)

     從 'sock' 接收最多 'nbytes' 大小的資料單元到 'buf'。*note
     socket.recvfrom_into(): 12b2. 的非同步版本。

     回傳一個元組 (number of bytes received, remote address)。

     'sock' 必須是非阻塞 socket。

     在 3.11 版被加入.

 -- 方法: coroutine loop.sock_sendall (sock, data)

     將 'data' 發送到 'sock' socket。*note socket.sendall(): d4e. 的非同
     步版本。

     此方法將繼續發送到 socket，直到 'data' 中的所有資料都已發送或發生錯
     誤。成功時回傳 ‘None’。錯誤時引發例外。此外，沒有辦法確定接收端成功
     處理了多少資料（如果有的話）。

     'sock' 必須是非阻塞 socket。

     在 3.7 版的變更: 儘管該方法一直被記錄為協程方法，但在 Python 3.7 之
     前它回傳 *note Future: b74.。從 Python 3.7 開始，這是一個 ‘async
     def’ 方法。

 -- 方法: coroutine loop.sock_sendto (sock, data, address)

     從 'sock' 向 'address' 發送一個資料單元。*note socket.sendto():
     d4f. 的非同步版本。

     回傳發送的位元組數。

     'sock' 必須是非阻塞 socket。

     在 3.11 版被加入.

 -- 方法: coroutine loop.sock_connect (sock, address)

     將 'sock' 連線到位於 'address' 的遠端 socket。

     *note socket.connect(): d49. 的非同步版本。

     'sock' 必須是非阻塞 socket。

     在 3.5.2 版的變更: 不再需要解析 ‘address’。‘sock_connect’ 將嘗試透
     過呼叫 *note socket.inet_pton(): 906. 檢查 'address' 是否已解析。如
     果沒有，將使用 *note loop.getaddrinfo(): bbb. 解析 'address'。

     也參考
     ......

     *note loop.create_connection(): 5a8. 和 *note
     asyncio.open_connection(): abb.。

 -- 方法: coroutine loop.sock_accept (sock)

     接受一個連線。模擬阻塞的 *note socket.accept(): d48. 方法。

     Socket 必須繫結到一個地址並偵聽連線。回傳值是一個 ‘(conn, address)’
     對，其中 'conn' 是一個 '新' socket 物件，可在連線上發送和接收資料，
     'address' 是連接另一端對應的 socket 地址。

     'sock' 必須是非阻塞 socket。

     在 3.7 版的變更: 儘管該方法一直被記錄為協程方法，但在 Python 3.7 之
     前它回傳 *note Future: b74.。從 Python 3.7 開始，這是一個 ‘async
     def’ 方法。

     也參考
     ......

     *note loop.create_server(): ab6. 和 *note start_server(): abc.。

 -- 方法: coroutine loop.sock_sendfile (sock, file, offset=0,
          count=None, *, fallback=True)

     如果可行，使用高性能 *note os.sendfile: ab2. 發送檔案。回傳發送的總
     位元組數。

     *note socket.sendfile(): dff. 的非同步版本。

     'sock' 必須是非阻塞的 *note socket.SOCK_STREAM: 1286. *note socket:
     d47.。

     'file' 必須是以二進位模式打開的常規檔案物件。

     'offset' 告訴從哪裡開始讀取檔案。如果指定了，'count' 是要傳輸的總位
     元組數，而不是發送檔案直到達到 EOF。即使此方法引發錯誤時，檔案位置
     也始終更新，可以使用 *note file.tell(): 2894. 取得實際發送的位元組
     數。

     當設置為 ‘True’ 時，'fallback' 使 asyncio 在平台不支援 sendfile 系
     統呼叫時（例如 Windows 或 Unix 上的 SSL socket）手動讀取和發送檔案
     。

     如果系統不支援 'sendfile' 系統呼叫且 'fallback' 為 ‘False’，引發
     *note SendfileNotAvailableError: 3163.。

     'sock' 必須是非阻塞 socket。

     在 3.7 版被加入.


File: python.info,  Node: DNS,  Next: 使用管道,  Prev: 直接使用 socket 物件,  Up: 事件迴圈方法

5.18.1.61 DNS
.............

 -- 方法: coroutine loop.getaddrinfo (host, port, *, family=0, type=0,
          proto=0, flags=0)

     *note socket.getaddrinfo(): 1654. 的非同步版本。

 -- 方法: coroutine loop.getnameinfo (sockaddr, flags=0)

     *note socket.getnameinfo(): 15be. 的非同步版本。

     備註: Both 'getaddrinfo' and 'getnameinfo' internally utilize their
     synchronous versions through the loop's default thread pool
     executor.  When this executor is saturated, these methods may
     experience delays, which higher-level networking libraries may
     report as increased timeouts.  To mitigate this, consider using a
     custom executor for other user tasks, or setting a default executor
     with a larger number of workers.

在 3.7 版的變更: 'getaddrinfo' 和 'getnameinfo' 方法一直被記錄為回傳協程
，但在 Python 3.7 之前它們實際上回傳 *note asyncio.Future: b74. 物件。從
Python 3.7 開始，兩個方法都是協程。


File: python.info,  Node: 使用管道,  Next: Unix 訊號,  Prev: DNS,  Up: 事件迴圈方法

5.18.1.62 使用管道
..................

 -- 方法: coroutine loop.connect_read_pipe (protocol_factory, pipe)

     在事件迴圈中註冊 'pipe' 的讀取端。

     'protocol_factory' 必須是一個回傳 *note asyncio protocol: 317a. 實
     作的可呼叫函式。

     'pipe' 是 *note 類檔案物件: 115b.。

     回傳 ‘(transport, protocol)’ 對，其中 'transport' 支援 *note
     ReadTransport: 318f. 介面，'protocol' 是由 'protocol_factory' 實例
     化的物件。

     使用 *note SelectorEventLoop: 5ad. 事件迴圈時，'pipe' 設置為非阻塞
     模式。

 -- 方法: coroutine loop.connect_write_pipe (protocol_factory, pipe)

     在事件迴圈中註冊 'pipe' 的寫入端。

     'protocol_factory' 必須是一個回傳 *note asyncio protocol: 317a. 實
     作的可呼叫函式。

     'pipe' 是 *note file-like object: 115b.。

     回傳 ‘(transport, protocol)’ 對，其中 'transport' 支援 *note
     WriteTransport: 3190. 介面，'protocol' 是由 'protocol_factory' 實例
     化的物件。

     使用 *note SelectorEventLoop: 5ad. 事件迴圈時，'pipe' 設置為非阻塞
     模式。

     備註: *note SelectorEventLoop: 5ad. 在 Windows 上不支援上述方法。對
     於 Windows 請使用 *note ProactorEventLoop: 5ae.。

也參考
......

*note loop.subprocess_exec(): 3133. 和 *note loop.subprocess_shell():
3134. 方法。


File: python.info,  Node: Unix 訊號,  Next: 在執行緒池或行程池中執行程式碼,  Prev: 使用管道,  Up: 事件迴圈方法

5.18.1.63 Unix 訊號
...................

 -- 方法: loop.add_signal_handler (signum, callback, *args)

     將 'callback' 設置為 'signum' 訊號的處理程式。

     該回呼將由 'loop' 呼叫，與該事件迴圈的其他排隊回呼和可運行的協程一
     起。與使用 *note signal.signal(): 10cd. 註冊的訊號處理程式不同，使
     用此函式註冊的回呼允許與事件迴圈進行互動。

     如果訊號號無效或不可捕獲，引發 *note ValueError: 1e7.。如果設定處理
     程序有問題，拋出 *note RuntimeError: 179.。

     使用 *note functools.partial(): 356. 向 'callback' *note
     傳送關鍵字引數: 3174.。

     像 *note signal.signal(): 10cd. 一樣，此函式必須在主執行緒中呼叫。

 -- 方法: loop.remove_signal_handler (sig)

     移除 'sig' 訊號的處理程式。

     如果訊號處理程式被移除，回傳 ‘True’；如果給定訊號沒有設置處理程式，
     回傳 ‘False’。

     *note 適用: 1c56.：Unix。

也參考
......

*note signal: b4. 模組。


File: python.info,  Node: 在執行緒池或行程池中執行程式碼,  Next: 錯誤處理 API,  Prev: Unix 訊號,  Up: 事件迴圈方法

5.18.1.64 在執行緒池或行程池中執行程式碼
........................................

 -- 方法: awaitable loop.run_in_executor (executor, func, *args)

     安排在指定的執行器中呼叫 'func'。

     The 'executor' argument should be an *note
     concurrent.futures.Executor: 3002. instance.  The default executor
     is used if 'executor' is ‘None’.  The default executor can be set
     by *note loop.set_default_executor(): 6e7, otherwise, a *note
     concurrent.futures.ThreadPoolExecutor: 6e6. will be
     lazy-initialized and used by *note run_in_executor(): 88e. if
     needed.

     範例：

          import asyncio
          import concurrent.futures

          def blocking_io():
              # File operations (such as logging) can block the
              # event loop: run them in a thread pool.
              with open('/dev/urandom', 'rb') as f:
                  return f.read(100)

          def cpu_bound():
              # CPU-bound operations will block the event loop:
              # in general it is preferable to run them in a
              # process pool.
              return sum(i * i for i in range(10 ** 7))

          async def main():
              loop = asyncio.get_running_loop()

              ## Options:

              # 1. Run in the default loop's executor:
              result = await loop.run_in_executor(
                  None, blocking_io)
              print('default thread pool', result)

              # 2. Run in a custom thread pool:
              with concurrent.futures.ThreadPoolExecutor() as pool:
                  result = await loop.run_in_executor(
                      pool, blocking_io)
                  print('custom thread pool', result)

              # 3. Run in a custom process pool:
              with concurrent.futures.ProcessPoolExecutor() as pool:
                  result = await loop.run_in_executor(
                      pool, cpu_bound)
                  print('custom process pool', result)

          if __name__ == '__main__':
              asyncio.run(main())

     請注意，由於 *note multiprocessing: 86.（由 *note
     ProcessPoolExecutor: 893. 使用）的特殊性，選項 3 需要進入點保護（
     ‘if __name__ == '__main__'’）。請參閱*note 主模組的安全引入: 2fee.。

     此方法回傳 *note asyncio.Future: b74. 物件。

     使用 *note functools.partial(): 356. 將來*note 關鍵字引數傳遞:
     3174.給 'func'。

     在 3.5.3 版的變更: *note loop.run_in_executor(): 88e. 不再配置它建
     立的執行緒池執行器的 ‘max_workers’，而是讓執行緒池執行器（*note
     ThreadPoolExecutor: 6e6.）設定預設值。

 -- 方法: loop.set_default_executor (executor)

     將 'executor' 設置為 *note run_in_executor(): 88e. 使用的預設執行器
     。'executor' 必須是 *note ThreadPoolExecutor: 6e6. 的實例。

     在 3.11 版的變更: 'executor' 必須是 *note ThreadPoolExecutor: 6e6.
     的實例。


File: python.info,  Node: 錯誤處理 API,  Next: 啟用除錯模式,  Prev: 在執行緒池或行程池中執行程式碼,  Up: 事件迴圈方法

5.18.1.65 錯誤處理 API
......................

允許自定義事件迴圈中的例外處理方式。

 -- 方法: loop.set_exception_handler (handler)

     將 'handler' 設定為新的事件迴圈例外處理程式。

     如果 'handler' 是 ‘None’，則將設置預設例外處理程式。否則，'handler'
     必須是一個可呼叫物件，簽名匹配 ‘(loop, context)’，其中 ‘loop’ 是參
     照活躍事件迴圈的，‘context’ 是包含例外詳細資訊的 ‘dict’ 物件（有關
     情境的詳細資訊，請參閱 *note call_exception_handler(): 3197. 文件）
     。

     如果代表 *note Task: 480. 或 *note Handle: 19a9. 呼叫處理程式，它將
     在該任務或回呼處理程式的 *note contextvars.Context: 308c. 中運行。

     在 3.12 版的變更: 處理程式可能在引發例外的任務或處理程式的 *note
     Context: 308c. 中被呼叫。

 -- 方法: loop.get_exception_handler ()

     回傳當前的例外處理程式，如果未設置自定義例外處理程式，則回傳
     ‘None’。

     在 3.5.2 版被加入.

 -- 方法: loop.default_exception_handler (context)

     預設例外處理程式。

     當發生例外且未設置例外處理程式時呼叫此函式。自定義例外處理程式可以
     呼叫此函式以轉由預設處理程式處理。

     'context' 參數與 *note call_exception_handler(): 3197. 中的意思相同
     。

 -- 方法: loop.call_exception_handler (context)

     呼叫當前事件迴圈例外處理程式。

     'context' 是一個包含以下鍵的 ‘dict’ 物件（未來的 Python 版本中可能
     會引入新的鍵）:

        * 'message'：錯誤訊息；

        * 'exception'（可選）：例外物件；

        * 'future'（可選）： *note asyncio.Future: b74. 實例；

        * 'task'（可選）： *note asyncio.Task: 480. 實例；

        * 'handle'（可選）： *note asyncio.Handle: 19a9. 實例；

        * 'protocol'（可選）： *note Protocol: 317a. 實例；

        * 'transport'（可選）： *note Transport: 317b. 實例；

        * 'socket'（可選）： *note socket.socket: d47. 實例；

        * 
          'asyncgen'(可選)： 非同步產生器引發

               例外。

          備註: 此方法不應在子類別事件迴圈中被覆寫。為了自定義例外處理，
          請使用 *note set_exception_handler(): 3196. 方法。


File: python.info,  Node: 啟用除錯模式,  Next: 運行子行程,  Prev: 錯誤處理 API,  Up: 事件迴圈方法

5.18.1.66 啟用除錯模式
......................

 -- 方法: loop.get_debug ()

     取得事件迴圈的除錯模式（*note bool: 40e.）。

     如果環境變數 *note PYTHONASYNCIODEBUG: 1c50. 被設定為非空字串，則預
     設值為 ‘True’，否則為 ‘False’。

 -- 方法: loop.set_debug (enabled: bool)

     設定事件迴圈的除錯模式。

     在 3.7 版的變更: 現在也可以使用新的 *note Python 開發模式: 1dd. 啟
     用除錯模式。

 -- 屬性: loop.slow_callback_duration

     此屬性可用於設定被視為"慢"的最短執行時間（以秒為單位）。啟用偵錯模
     式後，"慢"回呼將被記錄。

     預設值為 100 毫秒

也參考
......

*note asyncio 的除錯模式: 1c51.。


File: python.info,  Node: 運行子行程,  Prev: 啟用除錯模式,  Up: 事件迴圈方法

5.18.1.67 運行子行程
....................

本小節描述的方法是低階的。在常規的 async/await 程式碼中，請考慮使用高階
*note asyncio.create_subprocess_shell(): a1b. 和 *note
asyncio.create_subprocess_exec(): a1a. 輔助功能而不是。

     備註: 在 Windows 上，預設事件迴圈 *note ProactorEventLoop: 5ae. 支
     援子行程，而 *note SelectorEventLoop: 5ad. 不支援。詳細資訊請參見
     *note Windows 上對於子行程的支援: 3135.。

 -- 方法: coroutine loop.subprocess_exec (protocol_factory, *args,
          stdin=subprocess.PIPE, stdout=subprocess.PIPE,
          stderr=subprocess.PIPE, **kwargs)

     從 'args' 指定的一個或多個字串引數建立子行程。

     'args' 必須是由以下項表示的字串串列：

        * *note str: 3f2.；

        * 或 *note bytes: 1a5.，編碼為 *note 檔案系統編碼: 2698.。

     第一個字串指定程序可執行檔案，其餘字串指定引數。字串引數一起組成程
     序的 ‘argv’。

     這與標準函式庫 *note subprocess.Popen: 17d. 類似，使用
     ‘shell=False’ 呼叫並將字串串列作為第一個引數傳遞；然而，*note
     Popen: 17d. 接受單個字串串列引數，'subprocess_exec' 接受多個字串引
     數。

     'protocol_factory' 必須是回傳 *note asyncio.SubprocessProtocol:
     319c. 子類別的可呼叫物件。

     其他參數：

        * 'stdin' 可以是以下任意一個：

             * 類檔案物件

             * 現有的檔案描述器（正整數），例如用 *note os.pipe(): 16df.
               建立的

             * *note subprocess.PIPE: b2d. 常數（預設），它將建立一個新
               的管道並連線，

             * 值 ‘None’ 將使子行程從此行程繼承檔案描述器

             * *note subprocess.DEVNULL: 10e7. 常數，表示將使用特殊的
               *note os.devnull: 1939. 檔案

        * 'stdout' 可以是以下任意一個：

             * 類檔案物件

             * *note subprocess.PIPE: b2d. 常數（預設），它將建立一個新
               的管道並連線，

             * 值 ‘None’ 將使子行程從此行程繼承檔案描述器

             * *note subprocess.DEVNULL: 10e7. 常數，表示將使用特殊的
               *note os.devnull: 1939. 檔案

        * 'stderr' 可以是以下任意一個：

             * 類檔案物件

             * *note subprocess.PIPE: b2d. 常數（預設），它將建立一個新
               的管道並連線，

             * 值 ‘None’ 將使子行程從此行程繼承檔案描述器

             * *note subprocess.DEVNULL: 10e7. 常數，表示將使用特殊的
               *note os.devnull: 1939. 檔案

             * *note subprocess.STDOUT: 3020. 常數，它將標準錯誤串流連線
               到行程的標準輸出串流

        * 所有其他關鍵字引數都會傳遞給 *note subprocess.Popen: 17d. 而不
          進行直譯，但 'bufsize'、'universal_newlines'、'shell'、
          'text'、'encoding' 和 'errors' 除外，這些不應該指定。

          ‘asyncio’ 子行程 API 不支援將串流解碼為文本。可以使用 *note
          bytes.decode(): 87b. 將從串流回傳的位元組轉換為文本。

     如果傳遞給 'stdin'、'stdout' 或 'stderr' 的類檔案物件表示管道，則該
     管道的另一端應該使用 *note connect_write_pipe(): 3137. 或 *note
     connect_read_pipe(): 3136. 註冊到事件迴圈中。

     有關其他引數的文件，請參閱 *note subprocess.Popen: 17d. 類別的建構
     函式。

     回傳 ‘(transport, protocol)’ 對，其中 'transport' 符合 *note
     asyncio.SubprocessTransport: 319d. 基底類別，'protocol' 是由
     'protocol_factory' 實例化的物件。

 -- 方法: coroutine loop.subprocess_shell (protocol_factory, cmd, *,
          stdin=subprocess.PIPE, stdout=subprocess.PIPE,
          stderr=subprocess.PIPE, **kwargs)

     使用平台的 “shell” 語法從 'cmd' 建立子行程，'cmd' 可以是 *note str:
     3f2. 或編碼為 *note 檔案系統編碼: 2698. 的 *note bytes: 1a5. 字串。

     這類似於標準函式庫中的 *note subprocess.Popen: 17d. 類別，使用
     ‘shell=True’ 呼叫。

     'protocol_factory' 必須是回傳 *note SubprocessProtocol: 319c. 子類
     別的可呼叫物件。

     有關其餘引數的更多詳細資訊，請參閱 *note subprocess_exec(): 3133.。

     回傳一對 ‘(transport, protocol)’，其中 'transport' 符合 *note
     SubprocessTransport: 319d. 基底類別，而 'protocol' 是由
     'protocol_factory' 實例化的物件。

     備註: 由應用程式負責確保適當引用所有空白和特殊字元，以避免 shell 注
     入(1)風險。可以使用 *note shlex.quote(): 10c4. 函式來正確跳脫用於構
     建 shell 命令的字串中的空白和特殊字元。

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Shell_injection#Shell_injection


File: python.info,  Node: 回呼處理,  Next: Server 物件,  Prev: 事件迴圈方法,  Up: 事件迴圈

5.18.1.68 回呼處理
..................

 -- 類別: asyncio.Handle

     由 *note loop.call_soon(): aa7. 和 *note
     loop.call_soon_threadsafe(): aa8. 回傳的回呼包裝器。

      -- 方法: get_context ()

          回傳與處理相關聯的 *note contextvars.Context: 308c. 物件。

          在 3.12 版被加入.

      -- 方法: cancel ()

          取消回呼。如果回呼已被取消或執行，此方法將不起作用。

      -- 方法: cancelled ()

          如果回呼已被取消，回傳 ‘True’。

          在 3.7 版被加入.

 -- 類別: asyncio.TimerHandle

     由 *note loop.call_later(): aa9. 和 *note loop.call_at(): aaa. 回傳
     的回呼包裝器。

     這個類別是 *note Handle: 19a9. 的子類別。

      -- 方法: when ()

          回傳預定的回呼時間，以 *note float: 2c8. 秒為單位。

          時間是一個絕對的時間戳，使用與 *note loop.time(): 3177. 相同的
          時間參照。

          在 3.7 版被加入.


File: python.info,  Node: Server 物件,  Next: 事件迴圈實作,  Prev: 回呼處理,  Up: 事件迴圈

5.18.1.69 Server 物件
.....................

Server 物件是由 *note loop.create_server(): ab6.、*note
loop.create_unix_server(): 194.、*note start_server(): abc. 和 *note
start_unix_server(): 30f4. 函式所建立。

請勿直接實例化 *note Server: ab5. 類別。

 -- 類別: asyncio.Server

     'Server' 物件是非同步情境管理器。當在 ‘async with’ 陳述中使用時，可
     以保證在完成 ‘async with’ 陳述時，Server 物件將會關閉並停止接受新的
     連線：

          srv = await loop.create_server(...)

          async with srv:
              # some code

          # At this point, srv is closed and no longer accepts new connections.

     在 3.7 版的變更: 自 Python 3.7 起，Server 物件是非同步情境管理器。

     在 3.11 版的變更: 此類別在 Python 3.9.11、3.10.3 和 3.11 中以
     ‘asyncio.Server’ 的形式被公開。

      -- 方法: close ()

          停止服務：關閉監聽的 sockets 並將 *note sockets: bbd. 屬性設為
          ‘None’。

          代表現有傳入用戶端連線的 sockets 仍然保持開啟。

          伺服器以非同步方式關閉；使用 ‘wait_close()’ 協程等待伺服器關閉
          （不再有活躍連線）。

      -- 方法: close_clients ()

          Close all existing incoming client connections.

          Calls *note close(): 317e. on all associated transports.

          *note close(): 30f1. should be called before *note
          close_clients(): 198. when closing the server to avoid races
          with new clients connecting.

          在 3.13 版被加入.

      -- 方法: abort_clients ()

          Close all existing incoming client connections immediately,
          without waiting for pending operations to complete.

          Calls *note abort(): 31a0. on all associated transports.

          *note close(): 30f1. should be called before *note
          abort_clients(): 199. when closing the server to avoid races
          with new clients connecting.

          在 3.13 版被加入.

      -- 方法: get_loop ()

          回傳與伺服器物件關聯的事件迴圈。

          在 3.7 版被加入.

      -- 方法: coroutine start_serving ()

          開始接受連線。

          此方法是幂等的，因此可以在伺服器已經運行時呼叫。

          'start_serving' 僅限關鍵字參數只能在 *note
          loop.create_server(): ab6. 和 *note asyncio.start_server():
          abc. 中使用，允許建立一個最初不接受連線的 Server 物件。在這種
          情況下，可以使用 ‘Server.start_serving()’ 或 *note
          Server.serve_forever(): ab8. 來使 Server 開始接受連線。

          在 3.7 版被加入.

      -- 方法: coroutine serve_forever ()

          開始接受連線，直到協程被取消。取消 ‘serve_forever’ 任務會導致
          伺服器關閉。

          如果伺服器已經接受連線，則可以呼叫此方法。每個 'Server' 物件只
          能存在一個 ‘serve_forever’ 任務。

          範例：

               async def client_connected(reader, writer):
                   # Communicate with the client with
                   # reader/writer streams.  For example:
                   await reader.readline()

               async def main(host, port):
                   srv = await asyncio.start_server(
                       client_connected, host, port)
                   await srv.serve_forever()

               asyncio.run(main('127.0.0.1', 0))

          在 3.7 版被加入.

      -- 方法: is_serving ()

          如果伺服器正在接受新連線，則回傳 ‘True’。

          在 3.7 版被加入.

      -- 方法: coroutine wait_closed ()

          等待 *note close(): 30f1. 方法完成且所有活動連線都已結束。

      -- 屬性: sockets

          伺服器正在監聽的類似 socket 的物件串列，
          ‘asyncio.trsock.TransportSocket’。

          在 3.7 版的變更: 在 Python 3.7 之前，‘Server.sockets’ 曾經直接
          回傳內部伺服器 sockets 的串列。在 3.7 中回傳了該串列的副本。


File: python.info,  Node: 事件迴圈實作,  Next: 範例<23>,  Prev: Server 物件,  Up: 事件迴圈

5.18.1.70 事件迴圈實作
......................

asyncio 內附兩個不同的事件迴圈實作：*note SelectorEventLoop: 5ad. 和
*note ProactorEventLoop: 5ae.。

By default asyncio is configured to use *note EventLoop: 15f1.

 -- 類別: asyncio.SelectorEventLoop

     A subclass of *note AbstractEventLoop: 903. based on the *note
     selectors: b0. module.

     使用特定平台上最有效的 'selector'。也可以手動配置要使用的確切
     selector 實作：

          import asyncio
          import selectors

          class MyPolicy(asyncio.DefaultEventLoopPolicy):
             def new_event_loop(self):
                selector = selectors.SelectSelector()
                return asyncio.SelectorEventLoop(selector)

          asyncio.set_event_loop_policy(MyPolicy())

     *note 適用: 1c56.：Unix、Windows。

 -- 類別: asyncio.ProactorEventLoop

     A subclass of *note AbstractEventLoop: 903. for Windows that uses
     "I/O Completion Ports" (IOCP).

     *note 適用: 1c56.：Windows。

     也參考
     ......

     I/O 完成埠（I/O Completion Ports）的 MSDN 文件(1)。

 -- 類別: asyncio.EventLoop

          An alias to the most efficient available subclass of *note
          AbstractEventLoop: 903. for the given platform.

          It is an alias to *note SelectorEventLoop: 5ad. on Unix and
          *note ProactorEventLoop: 5ae. on Windows.

     在 3.13 版被加入.

 -- 類別: asyncio.AbstractEventLoop

     為符合 asyncio 標準的事件迴圈的抽象基礎類別。

     *note 事件迴圈方法: 316e. 部分列出了替代 ‘AbstractEventLoop’ 實作應
     該定義的所有方法。

   ---------- Footnotes ----------

   (1) 
https://docs.microsoft.com/zh-tw/windows/desktop/FileIO/i-o-completion-ports


File: python.info,  Node: 範例<23>,  Prev: 事件迴圈實作,  Up: 事件迴圈

5.18.1.71 範例
..............

請注意，本節中的所有範例都 '故意' 展示如何使用低階事件迴圈 API，如 *note
loop.run_forever(): 3170. 和 *note loop.call_soon(): aa7.。現代 asyncio
應用程式很少需要這種方式撰寫；請考慮使用高階的函式，如 *note
asyncio.run(): 423.。

* Menu:

* 使用 call_soon() 的 Hello World 範例: 使用 call_soon 的 Hello World 範例.
* 使用 call_later() 顯示目前日期: 使用 call_later 顯示目前日期.
* 監聽檔案描述器以進行讀取事件::
* 設定 SIGINT 和 SIGTERM 的訊號處理程式::


File: python.info,  Node: 使用 call_soon 的 Hello World 範例,  Next: 使用 call_later 顯示目前日期,  Up: 範例<23>

5.18.1.72 使用 call_soon() 的 Hello World 範例
..............................................

使用 *note loop.call_soon(): aa7. 方法排程回呼的範例。回呼會顯示 ‘"Hello
World"’，然後停止事件迴圈：

     import asyncio

     def hello_world(loop):
         """A callback to print 'Hello World' and stop the event loop"""
         print('Hello World')
         loop.stop()

     loop = asyncio.new_event_loop()

     # Schedule a call to hello_world()
     loop.call_soon(hello_world, loop)

     # Blocking call interrupted by loop.stop()
     try:
         loop.run_forever()
     finally:
         loop.close()

也參考
......

使用協程和 *note run(): 423. 函式建立的類似 *note Hello World: 30af. 範
例。


File: python.info,  Node: 使用 call_later 顯示目前日期,  Next: 監聽檔案描述器以進行讀取事件,  Prev: 使用 call_soon 的 Hello World 範例,  Up: 範例<23>

5.18.1.73 使用 call_later() 顯示目前日期
........................................

一個回呼的範例，每秒顯示目前日期。回呼使用 *note loop.call_later(): aa9.
方法在 5 秒後重新排程自己，然後停止事件迴圈：

     import asyncio
     import datetime

     def display_date(end_time, loop):
         print(datetime.datetime.now())
         if (loop.time() + 1.0) < end_time:
             loop.call_later(1, display_date, end_time, loop)
         else:
             loop.stop()

     loop = asyncio.new_event_loop()

     # Schedule the first call to display_date()
     end_time = loop.time() + 5.0
     loop.call_soon(display_date, end_time, loop)

     # Blocking call interrupted by loop.stop()
     try:
         loop.run_forever()
     finally:
         loop.close()

也參考
......

使用協程和 *note run(): 423. 函式建立的類似 *note current date: 30cc. 範
例。


File: python.info,  Node: 監聽檔案描述器以進行讀取事件,  Next: 設定 SIGINT 和 SIGTERM 的訊號處理程式,  Prev: 使用 call_later 顯示目前日期,  Up: 範例<23>

5.18.1.74 監聽檔案描述器以進行讀取事件
......................................

使用 *note loop.add_reader(): 310e. 方法等待檔案描述器接收到某些資料，然
後關閉事件迴圈：

     import asyncio
     from socket import socketpair

     # Create a pair of connected file descriptors
     rsock, wsock = socketpair()

     loop = asyncio.new_event_loop()

     def reader():
         data = rsock.recv(100)
         print("Received:", data.decode())

         # We are done: unregister the file descriptor
         loop.remove_reader(rsock)

         # Stop the event loop
         loop.stop()

     # Register the file descriptor for read event
     loop.add_reader(rsock, reader)

     # Simulate the reception of data from the network
     loop.call_soon(wsock.send, 'abc'.encode())

     try:
         # Run the event loop
         loop.run_forever()
     finally:
         # We are done. Close sockets and the event loop.
         rsock.close()
         wsock.close()
         loop.close()

也參考
......

   * 使用傳輸、協定和 *note loop.create_connection(): 5a8. 方法的類似
     *note 範例: 310c.。

   * 另一個使用高階 *note asyncio.open_connection(): abb. 函式和串流的類
     似 *note 範例: 310a.。


File: python.info,  Node: 設定 SIGINT 和 SIGTERM 的訊號處理程式,  Prev: 監聽檔案描述器以進行讀取事件,  Up: 範例<23>

5.18.1.75 設定 SIGINT 和 SIGTERM 的訊號處理程式
...............................................

（此 ‘signals’ 範例僅在 Unix 上運作。）

使用 *note loop.add_signal_handler(): 3192. 方法註冊訊號 ‘SIGINT’ 和
‘SIGTERM’ 的處理程式：

     import asyncio
     import functools
     import os
     import signal

     def ask_exit(signame, loop):
         print("got signal %s: exit" % signame)
         loop.stop()

     async def main():
         loop = asyncio.get_running_loop()

         for signame in {'SIGINT', 'SIGTERM'}:
             loop.add_signal_handler(
                 getattr(signal, signame),
                 functools.partial(ask_exit, signame, loop))

         await asyncio.sleep(3600)

     print("Event loop running for 1 hour, press Ctrl+C to interrupt.")
     print(f"pid {os.getpid()}: send SIGINT or SIGTERM to exit.")

     asyncio.run(main())


File: python.info,  Node: Futures,  Next: 傳輸與協定,  Prev: 事件迴圈,  Up: asyncio --- 非同步 I/O

5.18.1.76 Futures
.................

'原始碼：'Lib/asyncio/futures.py、source:'Lib/asyncio/base_futures.py(1)

__________________________________________________________________

'Future' 物件被用來連結'低階回呼式程式'和高階 async/await 程式。

* Menu:

* Future 函式::
* Future 物件: Future 物件<2>.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/asyncio/futures.py、
source:'Lib/asyncio/base_futures.py


File: python.info,  Node: Future 函式,  Next: Future 物件<2>,  Up: Futures

5.18.1.77 Future 函式
.....................

 -- 函式: asyncio.isfuture (obj)

     如果 'obj' 為下面任意物件，回傳 ‘True’：

        * 一個 *note asyncio.Future: b74. 的實例、

        * 一個 *note asyncio.Task: 480. 的實例、

        * 帶有 ‘_asyncio_future_blocking’ 屬性的類 Future 物件
          (Future-like object)。

     在 3.5 版被加入.

 -- 函式: asyncio.ensure_future (obj, *, loop=None)

     回傳：

        * 'obj' 引數會保持原樣，'obj' 須為 *note Future: b74.、*note
          Task: 480. 或類 Future 物件（可以用 *note isfuture(): 31ad. 來
          進行檢查。）

        * 包裝 (wrap) 了 'obj' 的 *note Task: 480. 物件，如果 'obj' 是一
          個協程 (coroutine) (可以用 *note iscoroutine(): 425. 來進行檢
          查)；在此情況下該協程將透過 ‘ensure_future()’ 來排程。

        * 一個會等待 'obj' 的 *note Task: 480. 物件，'obj' 須為一個可等
          待物件（*note inspect.isawaitable(): dbd. 用於測試。)

     如果 'obj' 不是上述物件的話會引發一個 *note TypeError: 4dd. 例外。

          重要: 請見 *note create_task(): 5a1. 函式，它是建立新 Task 的
          推薦方法。

          將參照 (reference) 儲存至此函式的結果，用以防止任務在執行中消
          失。

     在 3.5.1 版的變更: 這個函式接受任意 *note awaitable: 193. 物件。

     在 3.10 版之後被棄用: 如果 'obj' 不是類 Future 物件且 'loop' 並未被
     指定，同時沒有正在執行的事件迴圈 (event loop)，則會發出棄用警告。

 -- 函式: asyncio.wrap_future (future, *, loop=None)

     將一個 *note concurrent.futures.Future: 1149. 物件包裝到 *note
     asyncio.Future: b74. 物件中。

     在 3.10 版之後被棄用: 如果 'future' 不是類 Future 物件且 'loop' 未
     被指定，同時沒有正在執行的事件迴圈，則會發出棄用警告。


File: python.info,  Node: Future 物件<2>,  Prev: Future 函式,  Up: Futures

5.18.1.78 Future 物件
.....................

 -- 類別: asyncio.Future (*, loop=None)

     一個 Future 代表一個非同步運算的最終結果。並不支援執行緒安全
     (thread-safe)。

     Future 是一個 *note awaitable: 193. 物件。協程可以等待 Future 物件
     直到它們有結果或例外被設置、或者被取消。一個 Future 可被多次等待而
     結果都會是相同的。

     Future 通常用於讓低階基於回呼的程式（例如在協定實作中使用 asyncio
     *note transports: 30b7.）能夠與高階 async/await 程式互動。

     經驗法則為永遠不要在提供給使用者的 API 中公開 Future 物件，同時建議
     使用 *note loop.create_future(): c20. 來建立 Future 物件。如此一來
     ，不同實作的事件迴圈可以注入自己最佳化實作的 Future 物件。

     在 3.7 版的變更: 加入對 *note contextvars: 1d. 模組的支援。

     在 3.10 版之後被棄用: 如果未指定 'loop' 並且沒有正在執行的事件迴圈
     則會發出棄用警告。

      -- 方法: result ()

          回傳 Future 的結果。

          如果 Future 狀態為 'done'（完成），並擁有 *note set_result():
          30e1. 方法設定的一個結果，則回傳該結果之值。

          如果 Future 狀態為 'done'，並擁有 *note set_exception(): 30e2.
          方法設定的一個例外，那麼這個方法會引發該例外。

          如果 Future 已被 'cancelled'（取消），此方法會引發一個 *note
          CancelledError: 19e. 例外。

          如果 Future 的結果還不可用，此方法會引發一個 *note
          InvalidStateError: 30e5. 例外。

      -- 方法: set_result (result)

          將 Future 標記為 'done' 並設定其結果。

          如果 Future 已經 'done' 則引發一個 *note InvalidStateError:
          30e5. 錯誤。

      -- 方法: set_exception (exception)

          將 Future 標記為 'done' 並設定一個例外。

          如果 Future 已經 'done' 則引發一個 *note InvalidStateError:
          30e5. 錯誤。

      -- 方法: done ()

          如果 Future 已為 'done' 則回傳 ‘True’。

          如果 Future 有被 'cancelled'、*note set_result(): 30e1. 有被呼
          叫來為其設定結果、或 *note set_exception(): 30e2. 有被呼叫為其
          設定例外，那麼它就是 'done'。

      -- 方法: cancelled ()

          如果 Future 已經被 'cancelled' 則回傳 ‘True’。

          這個方法通常在為 Future 設定結果或例外前用來確認它還沒被
          'cancelled'：

               if not fut.cancelled():
                   fut.set_result(42)

      -- 方法: add_done_callback (callback, *, context=None)

          新增一個在 Future 為 'done' 時執行的回呼函式。

          呼叫 'callback' 並附帶做為唯一引數的 Future 物件。

          如果呼叫這個方法時 Future 已經為 'done'，回呼函式會被 *note
          loop.call_soon(): aa7. 排程。

          可選僅限關鍵字引數 'context' 用來指定一個讓 'callback' 執行於
          其中的客製化 *note contextvars.Context: 308c. 物件。如果沒有提
          供 'context'，則使用當前情境。

          可以用 *note functools.partial(): 356. 傳遞引數給回呼函式，例
          如：

               # Call 'print("Future:", fut)' when "fut" is done.
               fut.add_done_callback(
                   functools.partial(print, "Future:"))

          在 3.7 版的變更: 加入僅限關鍵字參數 'context'。更多細節請參閱
          PEP 567(1)。

      -- 方法: remove_done_callback (callback)

          從回呼列表中移除 'callback'。

          回傳被移除的回呼函式數量，通常為 1，除非一個回呼函式被多次加入
          。

      -- 方法: cancel (msg=None)

          取消 Future 並為回呼函式排程。

          如果 Future 已經是 'done' 或 'cancelled'，回傳 ‘False’。否則將
          Future 狀態改為 'cancelled' 並在為回呼函式排程後回傳 ‘True’。

          在 3.9 版的變更: 新增 'msg' 參數。

      -- 方法: exception ()

          回傳被設定於此 Future 的例外。

          只有 Future 在 'done' 時才回傳例外（如果沒有設定例外則回傳
          ‘None’）。

          如果 Future 已被 'cancelled'（取消），此方法會引發一個 *note
          CancelledError: 19e. 例外。

          如果 Future 還不為 'done'，此方法會引發一個 *note
          InvalidStateError: 30e5. 例外。

      -- 方法: get_loop ()

          回傳已被 Future 物件繫結 (bind) 的事件迴圈。

          在 3.7 版被加入.

這個例子建立一個 Future 物件，建立一個非同步 Task 並為其排程以設定
Future 結果，然後等待 Future 結果出現：

     async def set_after(fut, delay, value):
         # Sleep for *delay* seconds.
         await asyncio.sleep(delay)

         # Set *value* as a result of *fut* Future.
         fut.set_result(value)

     async def main():
         # Get the current event loop.
         loop = asyncio.get_running_loop()

         # Create a new Future object.
         fut = loop.create_future()

         # Run "set_after()" coroutine in a parallel Task.
         # We are using the low-level "loop.create_task()" API here because
         # we already have a reference to the event loop at hand.
         # Otherwise we could have just used "asyncio.create_task()".
         loop.create_task(
             set_after(fut, 1, '... world'))

         print('hello ...')

         # Wait until *fut* has a result (1 second) and print it.
         print(await fut)

     asyncio.run(main())

     重要: 該 Future 物件是為了模仿 *note concurrent.futures.Future:
     1149. 而設計。主要差異包含：

        - 與 asyncio 的 Future 不同，*note concurrent.futures.Future:
          1149. 實例不可被等待。

        - *note asyncio.Future.result(): 31af. 和 *note
          asyncio.Future.exception(): 31b2. 不接受 'timeout' 引數。

        - Future 不為 'done' 時 *note asyncio.Future.result(): 31af. 和
          *note asyncio.Future.exception(): 31b2. 會引發一個 *note
          InvalidStateError: 30e5. 例外。

        - 使用 *note asyncio.Future.add_done_callback(): aab. 註冊的回呼
          函式不會立即呼叫，而是被 *note loop.call_soon(): aa7. 排程。

        - asyncio Future 不能與 *note concurrent.futures.wait(): 1765. 和
          *note concurrent.futures.as_completed(): 1541. 函式相容。

        - *note asyncio.Future.cancel(): 171f. 接受一個可選的 ‘msg’ 引數
          ，但 *note concurrent.futures.Future.cancel(): 300b. 無此引數
          。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0567/


File: python.info,  Node: 傳輸與協定,  Next: Policies,  Prev: Futures,  Up: asyncio --- 非同步 I/O

5.18.1.79 傳輸與協定
....................

前言
....

Transports and Protocols are used by the 'low-level' event loop APIs
such as *note loop.create_connection(): 5a8.  They use callback-based
programming style and enable high-performance implementations of network
or IPC protocols (e.g.  HTTP).

Essentially, transports and protocols should only be used in libraries
and frameworks and never in high-level asyncio applications.

This documentation page covers both *note Transports: 31b6. and *note
Protocols: 31b7.

Introduction
............

At the highest level, the transport is concerned with 'how' bytes are
transmitted, while the protocol determines 'which' bytes to transmit
(and to some extent when).

A different way of saying the same thing: a transport is an abstraction
for a socket (or similar I/O endpoint) while a protocol is an
abstraction for an application, from the transport's point of view.

Yet another view is the transport and protocol interfaces together
define an abstract interface for using network I/O and interprocess I/O.

There is always a 1:1 relationship between transport and protocol
objects: the protocol calls transport methods to send data, while the
transport calls protocol methods to pass it data that has been received.

Most of connection oriented event loop methods (such as *note
loop.create_connection(): 5a8.) usually accept a 'protocol_factory'
argument used to create a 'Protocol' object for an accepted connection,
represented by a 'Transport' object.  Such methods usually return a
tuple of ‘(transport, protocol)’.

目錄
....

This documentation page contains the following sections:

   * The *note Transports: 31b6. section documents asyncio *note
     BaseTransport: 31b8, *note ReadTransport: 318f, *note
     WriteTransport: 3190, *note Transport: 31b9, *note
     DatagramTransport: 16af, and *note SubprocessTransport: 319d.
     classes.

   * The *note Protocols: 31b7. section documents asyncio *note
     BaseProtocol: 31ba, *note Protocol: 31bb, *note BufferedProtocol:
     a40, *note DatagramProtocol: 673, and *note SubprocessProtocol:
     319c. classes.

   * The *note Examples: 31bc. section showcases how to work with
     transports, protocols, and low-level event loop APIs.

* Menu:

* Transports::
* Protocols::
* 範例: 範例<24>.


File: python.info,  Node: Transports,  Next: Protocols,  Up: 傳輸與協定

5.18.1.80 Transports
....................

'原始碼：'Lib/asyncio/transports.py(1)

__________________________________________________________________

Transports are classes provided by *note asyncio: 8. in order to
abstract various kinds of communication channels.

Transport objects are always instantiated by an *note asyncio event
loop: d1f.

asyncio implements transports for TCP, UDP, SSL, and subprocess pipes.
The methods available on a transport depend on the transport's kind.

The transport classes are *note not thread safe: 30dd.

* Menu:

* Transports Hierarchy::
* Base Transport::
* Read-only Transports::
* Write-only Transports::
* Datagram Transports::
* Subprocess Transports::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/asyncio/transports.py


File: python.info,  Node: Transports Hierarchy,  Next: Base Transport,  Up: Transports

5.18.1.81 Transports Hierarchy
..............................

 -- 類別: asyncio.BaseTransport

     Base class for all transports.  Contains methods that all asyncio
     transports share.

 -- 類別: asyncio.WriteTransport (BaseTransport)

     A base transport for write-only connections.

     Instances of the 'WriteTransport' class are returned from the *note
     loop.connect_write_pipe(): 3137. event loop method and are also
     used by subprocess-related methods like *note
     loop.subprocess_exec(): 3133.

 -- 類別: asyncio.ReadTransport (BaseTransport)

     A base transport for read-only connections.

     Instances of the 'ReadTransport' class are returned from the *note
     loop.connect_read_pipe(): 3136. event loop method and are also used
     by subprocess-related methods like *note loop.subprocess_exec():
     3133.

 -- 類別: asyncio.Transport (WriteTransport, ReadTransport)

     Interface representing a bidirectional transport, such as a TCP
     connection.

     The user does not instantiate a transport directly; they call a
     utility function, passing it a protocol factory and other
     information necessary to create the transport and protocol.

     Instances of the 'Transport' class are returned from or used by
     event loop methods like *note loop.create_connection(): 5a8, *note
     loop.create_unix_connection(): 30f3, *note loop.create_server():
     ab6, *note loop.sendfile(): 3185, etc.

 -- 類別: asyncio.DatagramTransport (BaseTransport)

     A transport for datagram (UDP) connections.

     Instances of the 'DatagramTransport' class are returned from the
     *note loop.create_datagram_endpoint(): 6d7. event loop method.

 -- 類別: asyncio.SubprocessTransport (BaseTransport)

     An abstraction to represent a connection between a parent and its
     child OS process.

     Instances of the 'SubprocessTransport' class are returned from
     event loop methods *note loop.subprocess_shell(): 3134. and *note
     loop.subprocess_exec(): 3133.


File: python.info,  Node: Base Transport,  Next: Read-only Transports,  Prev: Transports Hierarchy,  Up: Transports

5.18.1.82 Base Transport
........................

 -- 方法: BaseTransport.close ()

     Close the transport.

     If the transport has a buffer for outgoing data, buffered data will
     be flushed asynchronously.  No more data will be received.  After
     all buffered data is flushed, the protocol's *note
     protocol.connection_lost(): 31bf. method will be called with *note
     None: 61b. as its argument.  The transport should not be used once
     it is closed.

 -- 方法: BaseTransport.is_closing ()

     Return ‘True’ if the transport is closing or is closed.

 -- 方法: BaseTransport.get_extra_info (name, default=None)

     Return information about the transport or underlying resources it
     uses.

     'name' is a string representing the piece of transport-specific
     information to get.

     'default' is the value to return if the information is not
     available, or if the transport does not support querying it with
     the given third-party event loop implementation or on the current
     platform.

     For example, the following code attempts to get the underlying
     socket object of the transport:

          sock = transport.get_extra_info('socket')
          if sock is not None:
              print(sock.getsockopt(...))

     Categories of information that can be queried on some transports:

        * socket:

             - ‘'peername'’: the remote address to which the socket is
               connected, result of *note socket.socket.getpeername():
               31c0. (‘None’ on error)

             - ‘'socket'’: *note socket.socket: d47. instance

             - ‘'sockname'’: the socket's own address, result of *note
               socket.socket.getsockname(): 31c1.

        * SSL socket:

             - ‘'compression'’: the compression algorithm being used as
               a string, or ‘None’ if the connection isn't compressed;
               result of *note ssl.SSLSocket.compression(): 10de.

             - ‘'cipher'’: a three-value tuple containing the name of
               the cipher being used, the version of the SSL protocol
               that defines its use, and the number of secret bits being
               used; result of *note ssl.SSLSocket.cipher(): 31c2.

             - ‘'peercert'’: peer certificate; result of *note
               ssl.SSLSocket.getpeercert(): f5a.

             - ‘'sslcontext'’: *note ssl.SSLContext: 276. instance

             - ‘'ssl_object'’: *note ssl.SSLObject: b25. or *note
               ssl.SSLSocket: 88f. instance

        * pipe:

             - ‘'pipe'’: pipe object

        * subprocess:

             - ‘'subprocess'’: *note subprocess.Popen: 17d. instance

 -- 方法: BaseTransport.set_protocol (protocol)

     Set a new protocol.

     Switching protocol should only be done when both protocols are
     documented to support the switch.

 -- 方法: BaseTransport.get_protocol ()

     Return the current protocol.


File: python.info,  Node: Read-only Transports,  Next: Write-only Transports,  Prev: Base Transport,  Up: Transports

5.18.1.83 Read-only Transports
..............................

 -- 方法: ReadTransport.is_reading ()

     Return ‘True’ if the transport is receiving new data.

     在 3.7 版被加入.

 -- 方法: ReadTransport.pause_reading ()

     Pause the receiving end of the transport.  No data will be passed
     to the protocol's *note protocol.data_received(): 1690. method
     until *note resume_reading(): ac0. is called.

     在 3.7 版的變更: The method is idempotent, i.e.  it can be called
     when the transport is already paused or closed.

 -- 方法: ReadTransport.resume_reading ()

     Resume the receiving end.  The protocol's *note
     protocol.data_received(): 1690. method will be called once again if
     some data is available for reading.

     在 3.7 版的變更: The method is idempotent, i.e.  it can be called
     when the transport is already reading.


File: python.info,  Node: Write-only Transports,  Next: Datagram Transports,  Prev: Read-only Transports,  Up: Transports

5.18.1.84 Write-only Transports
...............................

 -- 方法: WriteTransport.abort ()

     Close the transport immediately, without waiting for pending
     operations to complete.  Buffered data will be lost.  No more data
     will be received.  The protocol's *note protocol.connection_lost():
     31bf. method will eventually be called with *note None: 61b. as its
     argument.

 -- 方法: WriteTransport.can_write_eof ()

     Return *note True: bb4. if the transport supports *note
     write_eof(): 31c8, *note False: adb. if not.

 -- 方法: WriteTransport.get_write_buffer_size ()

     Return the current size of the output buffer used by the transport.

 -- 方法: WriteTransport.get_write_buffer_limits ()

     Get the 'high' and 'low' watermarks for write flow control.  Return
     a tuple ‘(low, high)’ where 'low' and 'high' are positive number of
     bytes.

     Use *note set_write_buffer_limits(): 31ca. to set the limits.

     在 3.4.2 版被加入.

 -- 方法: WriteTransport.set_write_buffer_limits (high=None, low=None)

     Set the 'high' and 'low' watermarks for write flow control.

     These two values (measured in number of bytes) control when the
     protocol's *note protocol.pause_writing(): 31cb. and *note
     protocol.resume_writing(): 31cc. methods are called.  If specified,
     the low watermark must be less than or equal to the high watermark.
     Neither 'high' nor 'low' can be negative.

     *note pause_writing(): 31cb. is called when the buffer size becomes
     greater than or equal to the 'high' value.  If writing has been
     paused, *note resume_writing(): 31cc. is called when the buffer
     size becomes less than or equal to the 'low' value.

     The defaults are implementation-specific.  If only the high
     watermark is given, the low watermark defaults to an
     implementation-specific value less than or equal to the high
     watermark.  Setting 'high' to zero forces 'low' to zero as well,
     and causes *note pause_writing(): 31cb. to be called whenever the
     buffer becomes non-empty.  Setting 'low' to zero causes *note
     resume_writing(): 31cc. to be called only once the buffer is empty.
     Use of zero for either limit is generally sub-optimal as it reduces
     opportunities for doing I/O and computation concurrently.

     Use *note get_write_buffer_limits(): d6b. to get the limits.

 -- 方法: WriteTransport.write (data)

     Write some 'data' bytes to the transport.

     This method does not block; it buffers the data and arranges for it
     to be sent out asynchronously.

 -- 方法: WriteTransport.writelines (list_of_data)

     Write a list (or any iterable) of data bytes to the transport.
     This is functionally equivalent to calling *note write(): 31cd. on
     each element yielded by the iterable, but may be implemented more
     efficiently.

 -- 方法: WriteTransport.write_eof ()

     Close the write end of the transport after flushing all buffered
     data.  Data may still be received.

     This method can raise *note NotImplementedError: 20d. if the
     transport (e.g.  SSL) doesn't support half-closed connections.


File: python.info,  Node: Datagram Transports,  Next: Subprocess Transports,  Prev: Write-only Transports,  Up: Transports

5.18.1.85 Datagram Transports
.............................

 -- 方法: DatagramTransport.sendto (data, addr=None)

     Send the 'data' bytes to the remote peer given by 'addr' (a
     transport-dependent target address).  If 'addr' is *note None: 61b,
     the data is sent to the target address given on transport creation.

     This method does not block; it buffers the data and arranges for it
     to be sent out asynchronously.

     在 3.13 版的變更: This method can be called with an empty bytes
     object to send a zero-length datagram.  The buffer size calculation
     used for flow control is also updated to account for the datagram
     header.

 -- 方法: DatagramTransport.abort ()

     Close the transport immediately, without waiting for pending
     operations to complete.  Buffered data will be lost.  No more data
     will be received.  The protocol's *note protocol.connection_lost():
     31bf. method will eventually be called with *note None: 61b. as its
     argument.


File: python.info,  Node: Subprocess Transports,  Prev: Datagram Transports,  Up: Transports

5.18.1.86 Subprocess Transports
...............................

 -- 方法: SubprocessTransport.get_pid ()

     Return the subprocess process id as an integer.

 -- 方法: SubprocessTransport.get_pipe_transport (fd)

     Return the transport for the communication pipe corresponding to
     the integer file descriptor 'fd':

        * ‘0’: readable streaming transport of the standard input
          ('stdin'), or *note None: 61b. if the subprocess was not
          created with ‘stdin=PIPE’

        * ‘1’: writable streaming transport of the standard output
          ('stdout'), or *note None: 61b. if the subprocess was not
          created with ‘stdout=PIPE’

        * ‘2’: writable streaming transport of the standard error
          ('stderr'), or *note None: 61b. if the subprocess was not
          created with ‘stderr=PIPE’

        * other 'fd': *note None: 61b.

 -- 方法: SubprocessTransport.get_returncode ()

     Return the subprocess return code as an integer or *note None: 61b.
     if it hasn't returned, which is similar to the *note
     subprocess.Popen.returncode: 18ac. attribute.

 -- 方法: SubprocessTransport.kill ()

     Kill the subprocess.

     On POSIX systems, the function sends SIGKILL to the subprocess.  On
     Windows, this method is an alias for *note terminate(): 31d5.

     另請參閱 *note subprocess.Popen.kill(): 134b.。

 -- 方法: SubprocessTransport.send_signal (signal)

     Send the 'signal' number to the subprocess, as in *note
     subprocess.Popen.send_signal(): 134c.

 -- 方法: SubprocessTransport.terminate ()

     Stop the subprocess.

     On POSIX systems, this method sends *note SIGTERM: 134d. to the
     subprocess.  On Windows, the Windows API function
     ‘TerminateProcess()’ is called to stop the subprocess.

     另請參閱 *note subprocess.Popen.terminate(): 134a.。

 -- 方法: SubprocessTransport.close ()

     Kill the subprocess by calling the *note kill(): 31d4. method.

     If the subprocess hasn't returned yet, and close transports of
     'stdin', 'stdout', and 'stderr' pipes.


File: python.info,  Node: Protocols,  Next: 範例<24>,  Prev: Transports,  Up: 傳輸與協定

5.18.1.87 Protocols
...................

'原始碼：'Lib/asyncio/protocols.py(1)

__________________________________________________________________

asyncio provides a set of abstract base classes that should be used to
implement network protocols.  Those classes are meant to be used
together with *note transports: 317b.

Subclasses of abstract base protocol classes may implement some or all
methods.  All these methods are callbacks: they are called by transports
on certain events, for example when some data is received.  A base
protocol method should be called by the corresponding transport.

* Menu:

* Base Protocols::
* Base Protocol::
* Streaming Protocols::
* Buffered Streaming Protocols::
* Datagram Protocols::
* Subprocess Protocols::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/asyncio/protocols.py


File: python.info,  Node: Base Protocols,  Next: Base Protocol,  Up: Protocols

5.18.1.88 Base Protocols
........................

 -- 類別: asyncio.BaseProtocol

     Base protocol with methods that all protocols share.

 -- 類別: asyncio.Protocol (BaseProtocol)

     The base class for implementing streaming protocols (TCP, Unix
     sockets, etc).

 -- 類別: asyncio.BufferedProtocol (BaseProtocol)

     A base class for implementing streaming protocols with manual
     control of the receive buffer.

 -- 類別: asyncio.DatagramProtocol (BaseProtocol)

     The base class for implementing datagram (UDP) protocols.

 -- 類別: asyncio.SubprocessProtocol (BaseProtocol)

     The base class for implementing protocols communicating with child
     processes (unidirectional pipes).


File: python.info,  Node: Base Protocol,  Next: Streaming Protocols,  Prev: Base Protocols,  Up: Protocols

5.18.1.89 Base Protocol
.......................

All asyncio protocols can implement Base Protocol callbacks.

Connection Callbacks
....................

Connection callbacks are called on all protocols, exactly once per a
successful connection.  All other protocol callbacks can only be called
between those two methods.

 -- 方法: BaseProtocol.connection_made (transport)

     Called when a connection is made.

     The 'transport' argument is the transport representing the
     connection.  The protocol is responsible for storing the reference
     to its transport.

 -- 方法: BaseProtocol.connection_lost (exc)

     Called when the connection is lost or closed.

     The argument is either an exception object or *note None: 61b.  The
     latter means a regular EOF is received, or the connection was
     aborted or closed by this side of the connection.

Flow Control Callbacks
......................

Flow control callbacks can be called by transports to pause or resume
writing performed by the protocol.

See the documentation of the *note set_write_buffer_limits(): 31ca.
method for more details.

 -- 方法: BaseProtocol.pause_writing ()

     Called when the transport's buffer goes over the high watermark.

 -- 方法: BaseProtocol.resume_writing ()

     Called when the transport's buffer drains below the low watermark.

If the buffer size equals the high watermark, *note pause_writing():
31cb. is not called: the buffer size must go strictly over.

Conversely, *note resume_writing(): 31cc. is called when the buffer size
is equal or lower than the low watermark.  These end conditions are
important to ensure that things go as expected when either mark is zero.


File: python.info,  Node: Streaming Protocols,  Next: Buffered Streaming Protocols,  Prev: Base Protocol,  Up: Protocols

5.18.1.90 Streaming Protocols
.............................

Event methods, such as *note loop.create_server(): ab6, *note
loop.create_unix_server(): 194, *note loop.create_connection(): 5a8,
*note loop.create_unix_connection(): 30f3, *note
loop.connect_accepted_socket(): abd, *note loop.connect_read_pipe():
3136, and *note loop.connect_write_pipe(): 3137. accept factories that
return streaming protocols.

 -- 方法: Protocol.data_received (data)

     Called when some data is received.  'data' is a non-empty bytes
     object containing the incoming data.

     Whether the data is buffered, chunked or reassembled depends on the
     transport.  In general, you shouldn't rely on specific semantics
     and instead make your parsing generic and flexible.  However, data
     is always received in the correct order.

     The method can be called an arbitrary number of times while a
     connection is open.

     However, *note protocol.eof_received(): 31db. is called at most
     once.  Once ‘eof_received()’ is called, ‘data_received()’ is not
     called anymore.

 -- 方法: Protocol.eof_received ()

     Called when the other end signals it won't send any more data (for
     example by calling *note transport.write_eof(): 31c8, if the other
     end also uses asyncio).

     This method may return a false value (including ‘None’), in which
     case the transport will close itself.  Conversely, if this method
     returns a true value, the protocol used determines whether to close
     the transport.  Since the default implementation returns ‘None’, it
     implicitly closes the connection.

     Some transports, including SSL, don't support half-closed
     connections, in which case returning true from this method will
     result in the connection being closed.

State machine:

     start -> connection_made
         [-> data_received]*
         [-> eof_received]?
     -> connection_lost -> end


File: python.info,  Node: Buffered Streaming Protocols,  Next: Datagram Protocols,  Prev: Streaming Protocols,  Up: Protocols

5.18.1.91 Buffered Streaming Protocols
......................................

在 3.7 版被加入.

Buffered Protocols can be used with any event loop method that supports
*note Streaming Protocols: 31da.

‘BufferedProtocol’ implementations allow explicit manual allocation and
control of the receive buffer.  Event loops can then use the buffer
provided by the protocol to avoid unnecessary data copies.  This can
result in noticeable performance improvement for protocols that receive
big amounts of data.  Sophisticated protocol implementations can
significantly reduce the number of buffer allocations.

The following callbacks are called on *note BufferedProtocol: a40.
instances:

 -- 方法: BufferedProtocol.get_buffer (sizehint)

     Called to allocate a new receive buffer.

     'sizehint' is the recommended minimum size for the returned buffer.
     It is acceptable to return smaller or larger buffers than what
     'sizehint' suggests.  When set to -1, the buffer size can be
     arbitrary.  It is an error to return a buffer with a zero size.

     ‘get_buffer()’ must return an object implementing the *note buffer
     protocol: 367.

 -- 方法: BufferedProtocol.buffer_updated (nbytes)

     Called when the buffer was updated with the received data.

     'nbytes' is the total number of bytes that were written to the
     buffer.

 -- 方法: BufferedProtocol.eof_received ()

     See the documentation of the *note protocol.eof_received(): 31db.
     method.

*note get_buffer(): 31dd. can be called an arbitrary number of times
during a connection.  However, *note protocol.eof_received(): 31db. is
called at most once and, if called, *note get_buffer(): 31dd. and *note
buffer_updated(): 31de. won't be called after it.

State machine:

     start -> connection_made
         [-> get_buffer
             [-> buffer_updated]?
         ]*
         [-> eof_received]?
     -> connection_lost -> end


File: python.info,  Node: Datagram Protocols,  Next: Subprocess Protocols,  Prev: Buffered Streaming Protocols,  Up: Protocols

5.18.1.92 Datagram Protocols
............................

Datagram Protocol instances should be constructed by protocol factories
passed to the *note loop.create_datagram_endpoint(): 6d7. method.

 -- 方法: DatagramProtocol.datagram_received (data, addr)

     Called when a datagram is received.  'data' is a bytes object
     containing the incoming data.  'addr' is the address of the peer
     sending the data; the exact format depends on the transport.

 -- 方法: DatagramProtocol.error_received (exc)

     Called when a previous send or receive operation raises an *note
     OSError: 350.  'exc' is the *note OSError: 350. instance.

     This method is called in rare conditions, when the transport (e.g.
     UDP) detects that a datagram could not be delivered to its
     recipient.  In many conditions though, undeliverable datagrams will
     be silently dropped.

     備註: On BSD systems (macOS, FreeBSD, etc.)  flow control is not
     supported for datagram protocols, because there is no reliable way
     to detect send failures caused by writing too many packets.

     The socket always appears 'ready' and excess packets are dropped.
     An *note OSError: 350. with ‘errno’ set to *note errno.ENOBUFS:
     16ed. may or may not be raised; if it is raised, it will be
     reported to *note DatagramProtocol.error_received(): 31e2. but
     otherwise ignored.


File: python.info,  Node: Subprocess Protocols,  Prev: Datagram Protocols,  Up: Protocols

5.18.1.93 Subprocess Protocols
..............................

Subprocess Protocol instances should be constructed by protocol
factories passed to the *note loop.subprocess_exec(): 3133. and *note
loop.subprocess_shell(): 3134. methods.

 -- 方法: SubprocessProtocol.pipe_data_received (fd, data)

     Called when the child process writes data into its stdout or stderr
     pipe.

     'fd' is the integer file descriptor of the pipe.

     'data' is a non-empty bytes object containing the received data.

 -- 方法: SubprocessProtocol.pipe_connection_lost (fd, exc)

     Called when one of the pipes communicating with the child process
     is closed.

     'fd' is the integer file descriptor that was closed.

 -- 方法: SubprocessProtocol.process_exited ()

     Called when the child process has exited.

     It can be called before *note pipe_data_received(): 16c9. and *note
     pipe_connection_lost(): 31e4. methods.


File: python.info,  Node: 範例<24>,  Prev: Protocols,  Up: 傳輸與協定

5.18.1.94 範例
..............

* Menu:

* TCP Echo Server::
* TCP Echo Client::
* UDP Echo Server::
* UDP Echo Client::
* Connecting Existing Sockets::
* loop.subprocess_exec() and SubprocessProtocol: loop subprocess_exec and SubprocessProtocol.


File: python.info,  Node: TCP Echo Server,  Next: TCP Echo Client,  Up: 範例<24>

5.18.1.95 TCP Echo Server
.........................

Create a TCP echo server using the *note loop.create_server(): ab6.
method, send back received data, and close the connection:

     import asyncio


     class EchoServerProtocol(asyncio.Protocol):
         def connection_made(self, transport):
             peername = transport.get_extra_info('peername')
             print('Connection from {}'.format(peername))
             self.transport = transport

         def data_received(self, data):
             message = data.decode()
             print('Data received: {!r}'.format(message))

             print('Send: {!r}'.format(message))
             self.transport.write(data)

             print('Close the client socket')
             self.transport.close()


     async def main():
         # Get a reference to the event loop as we plan to use
         # low-level APIs.
         loop = asyncio.get_running_loop()

         server = await loop.create_server(
             EchoServerProtocol,
             '127.0.0.1', 8888)

         async with server:
             await server.serve_forever()


     asyncio.run(main())

也參考
......

The *note TCP echo server using streams: 3106. example uses the
high-level *note asyncio.start_server(): abc. function.


File: python.info,  Node: TCP Echo Client,  Next: UDP Echo Server,  Prev: TCP Echo Server,  Up: 範例<24>

5.18.1.96 TCP Echo Client
.........................

A TCP echo client using the *note loop.create_connection(): 5a8. method,
sends data, and waits until the connection is closed:

     import asyncio


     class EchoClientProtocol(asyncio.Protocol):
         def __init__(self, message, on_con_lost):
             self.message = message
             self.on_con_lost = on_con_lost

         def connection_made(self, transport):
             transport.write(self.message.encode())
             print('Data sent: {!r}'.format(self.message))

         def data_received(self, data):
             print('Data received: {!r}'.format(data.decode()))

         def connection_lost(self, exc):
             print('The server closed the connection')
             self.on_con_lost.set_result(True)


     async def main():
         # Get a reference to the event loop as we plan to use
         # low-level APIs.
         loop = asyncio.get_running_loop()

         on_con_lost = loop.create_future()
         message = 'Hello World!'

         transport, protocol = await loop.create_connection(
             lambda: EchoClientProtocol(message, on_con_lost),
             '127.0.0.1', 8888)

         # Wait until the protocol signals that the connection
         # is lost and close the transport.
         try:
             await on_con_lost
         finally:
             transport.close()


     asyncio.run(main())

也參考
......

The *note TCP echo client using streams: 3103. example uses the
high-level *note asyncio.open_connection(): abb. function.


File: python.info,  Node: UDP Echo Server,  Next: UDP Echo Client,  Prev: TCP Echo Client,  Up: 範例<24>

5.18.1.97 UDP Echo Server
.........................

A UDP echo server, using the *note loop.create_datagram_endpoint(): 6d7.
method, sends back received data:

     import asyncio


     class EchoServerProtocol:
         def connection_made(self, transport):
             self.transport = transport

         def datagram_received(self, data, addr):
             message = data.decode()
             print('Received %r from %s' % (message, addr))
             print('Send %r to %s' % (message, addr))
             self.transport.sendto(data, addr)


     async def main():
         print("Starting UDP server")

         # Get a reference to the event loop as we plan to use
         # low-level APIs.
         loop = asyncio.get_running_loop()

         # One protocol instance will be created to serve all
         # client requests.
         transport, protocol = await loop.create_datagram_endpoint(
             EchoServerProtocol,
             local_addr=('127.0.0.1', 9999))

         try:
             await asyncio.sleep(3600)  # Serve for 1 hour.
         finally:
             transport.close()


     asyncio.run(main())


File: python.info,  Node: UDP Echo Client,  Next: Connecting Existing Sockets,  Prev: UDP Echo Server,  Up: 範例<24>

5.18.1.98 UDP Echo Client
.........................

A UDP echo client, using the *note loop.create_datagram_endpoint(): 6d7.
method, sends data and closes the transport when it receives the answer:

     import asyncio


     class EchoClientProtocol:
         def __init__(self, message, on_con_lost):
             self.message = message
             self.on_con_lost = on_con_lost
             self.transport = None

         def connection_made(self, transport):
             self.transport = transport
             print('Send:', self.message)
             self.transport.sendto(self.message.encode())

         def datagram_received(self, data, addr):
             print("Received:", data.decode())

             print("Close the socket")
             self.transport.close()

         def error_received(self, exc):
             print('Error received:', exc)

         def connection_lost(self, exc):
             print("Connection closed")
             self.on_con_lost.set_result(True)


     async def main():
         # Get a reference to the event loop as we plan to use
         # low-level APIs.
         loop = asyncio.get_running_loop()

         on_con_lost = loop.create_future()
         message = "Hello World!"

         transport, protocol = await loop.create_datagram_endpoint(
             lambda: EchoClientProtocol(message, on_con_lost),
             remote_addr=('127.0.0.1', 9999))

         try:
             await on_con_lost
         finally:
             transport.close()


     asyncio.run(main())


File: python.info,  Node: Connecting Existing Sockets,  Next: loop subprocess_exec and SubprocessProtocol,  Prev: UDP Echo Client,  Up: 範例<24>

5.18.1.99 Connecting Existing Sockets
.....................................

Wait until a socket receives data using the *note
loop.create_connection(): 5a8. method with a protocol:

     import asyncio
     import socket


     class MyProtocol(asyncio.Protocol):

         def __init__(self, on_con_lost):
             self.transport = None
             self.on_con_lost = on_con_lost

         def connection_made(self, transport):
             self.transport = transport

         def data_received(self, data):
             print("Received:", data.decode())

             # We are done: close the transport;
             # connection_lost() will be called automatically.
             self.transport.close()

         def connection_lost(self, exc):
             # The socket has been closed
             self.on_con_lost.set_result(True)


     async def main():
         # Get a reference to the event loop as we plan to use
         # low-level APIs.
         loop = asyncio.get_running_loop()
         on_con_lost = loop.create_future()

         # Create a pair of connected sockets
         rsock, wsock = socket.socketpair()

         # Register the socket to wait for data.
         transport, protocol = await loop.create_connection(
             lambda: MyProtocol(on_con_lost), sock=rsock)

         # Simulate the reception of data from the network.
         loop.call_soon(wsock.send, 'abc'.encode())

         try:
             await protocol.on_con_lost
         finally:
             transport.close()
             wsock.close()

     asyncio.run(main())

也參考
......

The *note watch a file descriptor for read events: 310d. example uses
the low-level *note loop.add_reader(): 310e. method to register an FD.

The *note register an open socket to wait for data using streams: 310a.
example uses high-level streams created by the *note open_connection():
abb. function in a coroutine.


File: python.info,  Node: loop subprocess_exec and SubprocessProtocol,  Prev: Connecting Existing Sockets,  Up: 範例<24>

5.18.1.100 loop.subprocess_exec() and SubprocessProtocol
........................................................

An example of a subprocess protocol used to get the output of a
subprocess and to wait for the subprocess exit.

The subprocess is created by the *note loop.subprocess_exec(): 3133.
method:

     import asyncio
     import sys

     class DateProtocol(asyncio.SubprocessProtocol):
         def __init__(self, exit_future):
             self.exit_future = exit_future
             self.output = bytearray()
             self.pipe_closed = False
             self.exited = False

         def pipe_connection_lost(self, fd, exc):
             self.pipe_closed = True
             self.check_for_exit()

         def pipe_data_received(self, fd, data):
             self.output.extend(data)

         def process_exited(self):
             self.exited = True
             # process_exited() method can be called before
             # pipe_connection_lost() method: wait until both methods are
             # called.
             self.check_for_exit()

         def check_for_exit(self):
             if self.pipe_closed and self.exited:
                 self.exit_future.set_result(True)

     async def get_date():
         # Get a reference to the event loop as we plan to use
         # low-level APIs.
         loop = asyncio.get_running_loop()

         code = 'import datetime; print(datetime.datetime.now())'
         exit_future = asyncio.Future(loop=loop)

         # Create the subprocess controlled by DateProtocol;
         # redirect the standard output into a pipe.
         transport, protocol = await loop.subprocess_exec(
             lambda: DateProtocol(exit_future),
             sys.executable, '-c', code,
             stdin=None, stderr=None)

         # Wait for the subprocess exit using the process_exited()
         # method of the protocol.
         await exit_future

         # Close the stdout pipe.
         transport.close()

         # Read the output which was collected by the
         # pipe_data_received() method of the protocol.
         data = bytes(protocol.output)
         return data.decode('ascii').rstrip()

     date = asyncio.run(get_date())
     print(f"Current date: {date}")

See also the *note same example: 314a. written using high-level APIs.


File: python.info,  Node: Policies,  Next: 平臺支援,  Prev: 傳輸與協定,  Up: asyncio --- 非同步 I/O

5.18.1.101 Policies
...................

An event loop policy is a global object used to get and set the current
*note event loop: d1f, as well as create new event loops.  The default
policy can be *note replaced: 31ed. with *note built-in alternatives:
31ee. to use different event loop implementations, or substituted by a
*note custom policy: 31ef. that can override these behaviors.

The *note policy object: 31f0. gets and sets a separate event loop per
'context'.  This is per-thread by default, though custom policies could
define 'context' differently.

Custom event loop policies can control the behavior of *note
get_event_loop(): 2a3, *note set_event_loop(): 16cf, and *note
new_event_loop(): 30bd.

Policy objects should implement the APIs defined in the *note
AbstractEventLoopPolicy: 31f1. abstract base class.

* Menu:

* Getting and Setting the Policy::
* Policy Objects::
* Process Watchers::
* Custom Policies::


File: python.info,  Node: Getting and Setting the Policy,  Next: Policy Objects,  Up: Policies

5.18.1.102 Getting and Setting the Policy
.........................................

The following functions can be used to get and set the policy for the
current process:

 -- 函式: asyncio.get_event_loop_policy ()

     Return the current process-wide policy.

 -- 函式: asyncio.set_event_loop_policy (policy)

     Set the current process-wide policy to 'policy'.

     If 'policy' is set to ‘None’, the default policy is restored.


File: python.info,  Node: Policy Objects,  Next: Process Watchers,  Prev: Getting and Setting the Policy,  Up: Policies

5.18.1.103 Policy Objects
.........................

The abstract event loop policy base class is defined as follows:

 -- 類別: asyncio.AbstractEventLoopPolicy

     An abstract base class for asyncio policies.

      -- 方法: get_event_loop ()

          Get the event loop for the current context.

          Return an event loop object implementing the *note
          AbstractEventLoop: 903. interface.

          This method should never return ‘None’.

          在 3.6 版的變更.

      -- 方法: set_event_loop (loop)

          Set the event loop for the current context to 'loop'.

      -- 方法: new_event_loop ()

          Create and return a new event loop object.

          This method should never return ‘None’.

      -- 方法: get_child_watcher ()

          Get a child process watcher object.

          Return a watcher object implementing the *note
          AbstractChildWatcher: 29d. interface.

          This function is Unix specific.

          在 3.12 版之後被棄用.

      -- 方法: set_child_watcher (watcher)

          Set the current child process watcher to 'watcher'.

          This function is Unix specific.

          在 3.12 版之後被棄用.

asyncio ships with the following built-in policies:

 -- 類別: asyncio.DefaultEventLoopPolicy

     The default asyncio policy.  Uses *note SelectorEventLoop: 5ad. on
     Unix and *note ProactorEventLoop: 5ae. on Windows.

     There is no need to install the default policy manually.  asyncio
     is configured to use the default policy automatically.

     在 3.8 版的變更: On Windows, *note ProactorEventLoop: 5ae. is now
     used by default.

     在 3.12 版之後被棄用: The *note get_event_loop(): 2a3. method of
     the default asyncio policy now emits a *note DeprecationWarning:
     18b. if there is no current event loop set and it decides to create
     one.  In some future Python release this will become an error.

 -- 類別: asyncio.WindowsSelectorEventLoopPolicy

     An alternative event loop policy that uses the *note
     SelectorEventLoop: 5ad. event loop implementation.

     *note 適用: 1c56.：Windows。

 -- 類別: asyncio.WindowsProactorEventLoopPolicy

     An alternative event loop policy that uses the *note
     ProactorEventLoop: 5ae. event loop implementation.

     *note 適用: 1c56.：Windows。


File: python.info,  Node: Process Watchers,  Next: Custom Policies,  Prev: Policy Objects,  Up: Policies

5.18.1.104 Process Watchers
...........................

A process watcher allows customization of how an event loop monitors
child processes on Unix.  Specifically, the event loop needs to know
when a child process has exited.

In asyncio, child processes are created with *note
create_subprocess_exec(): a1a. and *note loop.subprocess_exec(): 3133.
functions.

asyncio defines the *note AbstractChildWatcher: 29d. abstract base
class, which child watchers should implement, and has four different
implementations: *note ThreadedChildWatcher: 422. (configured to be used
by default), *note MultiLoopChildWatcher: 29b, *note SafeChildWatcher:
29e, and *note FastChildWatcher: 29c.

See also the *note Subprocess and Threads: 3143. section.

The following two functions can be used to customize the child process
watcher implementation used by the asyncio event loop:

 -- 函式: asyncio.get_child_watcher ()

     Return the current child watcher for the current policy.

     在 3.12 版之後被棄用.

 -- 函式: asyncio.set_child_watcher (watcher)

     Set the current child watcher to 'watcher' for the current policy.
     'watcher' must implement methods defined in the *note
     AbstractChildWatcher: 29d. base class.

     在 3.12 版之後被棄用.

     備註: Third-party event loops implementations might not support
     custom child watchers.  For such event loops, using *note
     set_child_watcher(): 29f. might be prohibited or have no effect.

 -- 類別: asyncio.AbstractChildWatcher

      -- 方法: add_child_handler (pid, callback, *args)

          Register a new child handler.

          Arrange for ‘callback(pid, returncode, *args)’ to be called
          when a process with PID equal to 'pid' terminates.  Specifying
          another callback for the same process replaces the previous
          handler.

          The 'callback' callable must be thread-safe.

      -- 方法: remove_child_handler (pid)

          Removes the handler for process with PID equal to 'pid'.

          The function returns ‘True’ if the handler was successfully
          removed, ‘False’ if there was nothing to remove.

      -- 方法: attach_loop (loop)

          Attach the watcher to an event loop.

          If the watcher was previously attached to an event loop, then
          it is first detached before attaching to the new loop.

          Note: loop may be ‘None’.

      -- 方法: is_active ()

          Return ‘True’ if the watcher is ready to use.

          Spawning a subprocess with 'inactive' current child watcher
          raises *note RuntimeError: 179.

          在 3.8 版被加入.

      -- 方法: close ()

          Close the watcher.

          This method has to be called to ensure that underlying
          resources are cleaned-up.

     在 3.12 版之後被棄用.

 -- 類別: asyncio.ThreadedChildWatcher

     This implementation starts a new waiting thread for every
     subprocess spawn.

     It works reliably even when the asyncio event loop is run in a
     non-main OS thread.

     There is no noticeable overhead when handling a big number of
     children ('O'(1) each time a child terminates), but starting a
     thread per process requires extra memory.

     This watcher is used by default.

     在 3.8 版被加入.

 -- 類別: asyncio.MultiLoopChildWatcher

     This implementation registers a ‘SIGCHLD’ signal handler on
     instantiation.  That can break third-party code that installs a
     custom handler for ‘SIGCHLD’ signal.

     The watcher avoids disrupting other code spawning processes by
     polling every process explicitly on a ‘SIGCHLD’ signal.

     There is no limitation for running subprocesses from different
     threads once the watcher is installed.

     The solution is safe but it has a significant overhead when
     handling a big number of processes ('O'('n') each time a ‘SIGCHLD’
     is received).

     在 3.8 版被加入.

     在 3.12 版之後被棄用.

 -- 類別: asyncio.SafeChildWatcher

     This implementation uses active event loop from the main thread to
     handle ‘SIGCHLD’ signal.  If the main thread has no running event
     loop another thread cannot spawn a subprocess (*note RuntimeError:
     179. is raised).

     The watcher avoids disrupting other code spawning processes by
     polling every process explicitly on a ‘SIGCHLD’ signal.

     This solution is as safe as *note MultiLoopChildWatcher: 29b. and
     has the same 'O'('n') complexity but requires a running event loop
     in the main thread to work.

     在 3.12 版之後被棄用.

 -- 類別: asyncio.FastChildWatcher

     This implementation reaps every terminated processes by calling
     ‘os.waitpid(-1)’ directly, possibly breaking other code spawning
     processes and waiting for their termination.

     There is no noticeable overhead when handling a big number of
     children ('O'(1) each time a child terminates).

     This solution requires a running event loop in the main thread to
     work, as *note SafeChildWatcher: 29e.

     在 3.12 版之後被棄用.

 -- 類別: asyncio.PidfdChildWatcher

     This implementation polls process file descriptors (pidfds) to
     await child process termination.  In some respects, *note
     PidfdChildWatcher: 420. is a "Goldilocks" child watcher
     implementation.  It doesn't require signals or threads, doesn't
     interfere with any processes launched outside the event loop, and
     scales linearly with the number of subprocesses launched by the
     event loop.  The main disadvantage is that pidfds are specific to
     Linux, and only work on recent (5.3+) kernels.

     在 3.9 版被加入.


File: python.info,  Node: Custom Policies,  Prev: Process Watchers,  Up: Policies

5.18.1.105 Custom Policies
..........................

To implement a new event loop policy, it is recommended to subclass
*note DefaultEventLoopPolicy: 31f9. and override the methods for which
custom behavior is wanted, e.g.:

     class MyEventLoopPolicy(asyncio.DefaultEventLoopPolicy):

         def get_event_loop(self):
             """Get the event loop.

             This may be None or an instance of EventLoop.
             """
             loop = super().get_event_loop()
             # Do something with loop ...
             return loop

     asyncio.set_event_loop_policy(MyEventLoopPolicy())


File: python.info,  Node: 平臺支援,  Next: 擴充,  Prev: Policies,  Up: asyncio --- 非同步 I/O

5.18.1.106 平臺支援
...................

*note asyncio: 8. module（模組）被設計為可攜的 (portable)，但由於平臺的
底層架構和功能不同，在一些平臺上存在細微的差異和限制。

* Menu:

* 所有平台::
* Windows: Windows<72>.
* macOS: macOS<45>.


File: python.info,  Node: 所有平台,  Next: Windows<72>,  Up: 平臺支援

5.18.1.107 所有平台
...................

   * *note loop.add_reader(): 310e. 和 *note loop.add_writer(): 3189. 不
     能用來監視檔案 I/O。


File: python.info,  Node: Windows<72>,  Next: macOS<45>,  Prev: 所有平台,  Up: 平臺支援

5.18.1.108 Windows
..................

'原始碼：'Lib/asyncio/proactor_events.py、
source:'Lib/asyncio/windows_events.py、
source:'Lib/asyncio/windows_utils.py(1)

__________________________________________________________________

在 3.8 版的變更: 在 Windows 上，現在 *note ProactorEventLoop: 5ae. 是預
設的事件迴圈。

Windows 上的所有事件迴圈都不支援以下 method（方法）：

   * 不支援 *note loop.create_unix_connection(): 30f3. 和 *note
     loop.create_unix_server(): 194.。*note socket.AF_UNIX: 1724. socket
     系列常數僅限於 Unix 上使用。

   * 不支援 *note loop.add_signal_handler(): 3192. 和 *note
     loop.remove_signal_handler(): 3193.。

*note SelectorEventLoop: 5ad. 有以下限制：

   * *note SelectSelector: 3206. 只被用於等待 socket 事件：它支援 socket
     且最多支援 512 個 socket。

   * *note loop.add_reader(): 310e. 和 *note loop.add_writer(): 3189. 只
     接受 socket 處理函式（例如不支援 pipe 檔案描述器 (pipe file
     descriptor)）。

   * 因為不支援 pipe，所以 *note loop.connect_read_pipe(): 3136. 和
     *note loop.connect_write_pipe(): 3137. method 沒有被實作出來。

   * 不支援*note 子行程 (subprocess): 30b1.，也就是說 *note
     loop.subprocess_exec(): 3133. 和 *note loop.subprocess_shell():
     3134. method 沒有被實作出來。

*note ProactorEventLoop: 5ae. 有以下限制：

   * 不支援 *note loop.add_reader(): 310e. 和 *note loop.add_writer():
     3189. method。

Windows 上單調時鐘 (monotonic clock) 的解析度大約為 15.6 毫秒。最佳的解
析度是 0.5 毫秒。解析度和硬體（HPET(2) 是否可用）與 Windows 的設定有關。

* Menu:

* Windows 的子行程支援::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/asyncio/proactor_events.py、
source:'Lib/asyncio/windows_events.py、
source:'Lib/asyncio/windows_utils.py

   (2) https://zh.wikipedia.org/wiki/高精度事件計時器


File: python.info,  Node: Windows 的子行程支援,  Up: Windows<72>

5.18.1.109 Windows 的子行程支援
...............................

在 Windows 上，預設的事件迴圈 *note ProactorEventLoop: 5ae. 支援子行程，
而 *note SelectorEventLoop: 5ad. 則不支援。

也不支援 *note policy.set_child_watcher(): 2a1. 函式，*note
ProactorEventLoop: 5ae. 在監視子行程上有不同的機制。


File: python.info,  Node: macOS<45>,  Prev: Windows<72>,  Up: 平臺支援

5.18.1.110 macOS
................

完整支援現在普遍流行的 macOS 版本。

macOS <= 10.8
.............

在 macOS 10.6、10.7 和 10.8 上，預設的事件迴圈是使用 *note
selectors.KqueueSelector: 3209.，在這些版本上它並不支援字元裝置
(character device)。可以手工設置 *note SelectorEventLoop: 5ad. 來使用
*note SelectSelector: 3206. 或 *note PollSelector: b7d. 以在這些舊版
macOS 上支援字元裝置。例如：

     import asyncio
     import selectors

     selector = selectors.SelectSelector()
     loop = asyncio.SelectorEventLoop(selector)
     asyncio.set_event_loop(loop)


File: python.info,  Node: 擴充,  Next: 高階 API 索引,  Prev: 平臺支援,  Up: asyncio --- 非同步 I/O

5.18.1.111 擴充
...............

The main direction for *note asyncio: 8. extending is writing custom
'event loop' classes.  Asyncio has helpers that could be used to
simplify this task.

     備註: Third-parties should reuse existing asyncio code with
     caution, a new Python version is free to break backward
     compatibility in 'internal' part of API.

* Menu:

* Writing a Custom Event Loop::
* Future and Task private constructors::
* Task lifetime support::


File: python.info,  Node: Writing a Custom Event Loop,  Next: Future and Task private constructors,  Up: 擴充

5.18.1.112 Writing a Custom Event Loop
......................................

*note asyncio.AbstractEventLoop: 903. declares very many methods.
Implementing all them from scratch is a tedious job.

A loop can get many common methods implementation for free by inheriting
from ‘asyncio.BaseEventLoop’.

In turn, the successor should implement a bunch of 'private' methods
declared but not implemented in ‘asyncio.BaseEventLoop’.

For example, ‘loop.create_connection()’ checks arguments, resolves DNS
addresses, and calls ‘loop._make_socket_transport()’ that should be
implemented by inherited class.  The ‘_make_socket_transport()’ method
is not documented and is considered as an 'internal' API.


File: python.info,  Node: Future and Task private constructors,  Next: Task lifetime support,  Prev: Writing a Custom Event Loop,  Up: 擴充

5.18.1.113 Future and Task private constructors
...............................................

*note asyncio.Future: b74. and *note asyncio.Task: 480. should be never
created directly, please use corresponding *note loop.create_future():
c20. and *note loop.create_task(): 980, or *note asyncio.create_task():
5a1. factories instead.

However, third-party 'event loops' may 'reuse' built-in future and task
implementations for the sake of getting a complex and highly optimized
code for free.

For this purpose the following, 'private' constructors are listed:

 -- 方法: Future.__init__ (*, loop=None)

     Create a built-in future instance.

     'loop' is an optional event loop instance.

 -- 方法: Task.__init__ (coro, *, loop=None, name=None, context=None)

     Create a built-in task instance.

     'loop' is an optional event loop instance.  The rest of arguments
     are described in *note loop.create_task(): 980. description.

     在 3.11 版的變更: 'context' argument is added.


File: python.info,  Node: Task lifetime support,  Prev: Future and Task private constructors,  Up: 擴充

5.18.1.114 Task lifetime support
................................

A third party task implementation should call the following functions to
keep a task visible by *note asyncio.all_tasks(): 8fa. and *note
asyncio.current_task(): 424.:

 -- 函式: asyncio._register_task (task)

     Register a new 'task' as managed by 'asyncio'.

     Call the function from a task constructor.

 -- 函式: asyncio._unregister_task (task)

     Unregister a 'task' from 'asyncio' internal structures.

     The function should be called when a task is about to finish.

 -- 函式: asyncio._enter_task (loop, task)

     Switch the current task to the 'task' argument.

     Call the function just before executing a portion of embedded
     'coroutine' (*note coroutine.send(): 1ea1. or *note
     coroutine.throw(): 49f.).

 -- 函式: asyncio._leave_task (loop, task)

     Switch the current task back from 'task' to ‘None’.

     Call the function just after *note coroutine.send(): 1ea1. or *note
     coroutine.throw(): 49f. execution.


File: python.info,  Node: 高階 API 索引,  Next: 低階 API 索引,  Prev: 擴充,  Up: asyncio --- 非同步 I/O

5.18.1.115 高階 API 索引
........................

這個頁面列出了所有能使用 async/wait 的高階 asyncio API。

* Menu:

* 任務 (Tasks): 任務 Tasks.
* 佇列 (Queues): 佇列 Queues<2>.
* 子行程 (Subprocesses): 子行程 Subprocesses.
* 串流 (Streams): 串流 Streams.
* 同步化 (Synchronization): 同步化 Synchronization.
* 例外: 例外<9>.


File: python.info,  Node: 任務 Tasks,  Next: 佇列 Queues<2>,  Up: 高階 API 索引

5.18.1.116 任務 (Tasks)
.......................

用於執行非同步程式、建立 Task 物件、帶有超時 (timeout) 設定地等待多個事
件的工具程式。

*note run(): 423.                                      建立事件迴圈 (event loop)、執行一個協程 (coroutine)、
                                                       關閉事件迴圈。
                                                       
                                                       
*note Runner: 5a5.                                     A context manager that simplifies multiple async
                                                       function calls.
                                                       
                                                       
*note Task: 480.                                       Task 物件。
                                                       
                                                       
*note TaskGroup: 19b.                                  A context manager that holds a group of tasks.
                                                       Provides a convenient and reliable way to wait for
                                                       all tasks in the group to finish.
                                                       
                                                       
*note create_task(): 5a1.                              啟動一個 asyncio 的 Task 物件，然後回傳它。
                                                       
                                                       
*note current_task(): 424.                             回傳當前 Task 物件。
                                                       
                                                       
*note all_tasks(): 8fa.                                回傳事件迴圈中所有未完成的 task 物件。
                                                       
                                                       
‘await’ *note sleep(): a12.                            休眠數秒鐘。
                                                       
                                                       
‘await’ *note gather(): 5a2.                           並行 (concurrent) 地執行事件的排程與等待。
                                                       
                                                       
‘await’ *note wait_for(): 5a4.                         有超時設置的執行。
                                                       
                                                       
‘await’ *note shield(): a13.                           屏蔽取消操作。
                                                       
                                                       
‘await’ *note wait(): 426.                             監控完成情況。
                                                       
                                                       
*note timeout(): 5a3.                                  Run with a timeout.  Useful in cases when ‘wait_for’
                                                       is not suitable.
                                                       
                                                       
*note to_thread(): 88d.                                在不同的 OS 執行緒 (thread) 中非同步地執行一個函式。
                                                       
                                                       
*note run_coroutine_threadsafe(): 826.                 從其他 OS 執行緒中為一個協程排程。
                                                       
                                                       
‘for in’ *note as_completed(): 190.                    用 ‘for’ 迴圈來監控完成情況。
                                                       

範例
....

   * *note 使用 asyncio.gather() 平行 (parallel) 執行: 30ce.。

   * *note 使用 asyncio.wait_for() 強制設置超時: 30d6.。

   * *note 取消任務: 30eb.。

   * *note 使用 asyncio.sleep(): 30cc.。

   * 請參閱 *note Tasks 文件頁面: 30af.。


File: python.info,  Node: 佇列 Queues<2>,  Next: 子行程 Subprocesses,  Prev: 任務 Tasks,  Up: 高階 API 索引

5.18.1.117 佇列 (Queues)
........................

佇列應被用於為多個 asyncio Task 物件分配工作、實作 connection pools（連
線池）以及 pub/sub（發行/訂閱）模式。

*note Queue: a19.                                      一個先進先出 (FIFO) 佇列。
                                                       
                                                       
*note PriorityQueue: 315b.                             一個優先佇列 (priority queue)。
                                                       
                                                       
*note LifoQueue: 315d.                                 一個後進先出 (LIFO) 佇列。
                                                       

範例
....

   * *note 使用 asyncio.Queue 為多個 Task 分配工作: 315f.。

   * 請參閱*note 佇列文件頁面: 30b2.。


File: python.info,  Node: 子行程 Subprocesses,  Next: 串流 Streams,  Prev: 佇列 Queues<2>,  Up: 高階 API 索引

5.18.1.118 子行程 (Subprocesses)
................................

用於衍生（spawn）子行程和執行 shell 指令的工具程式。

‘await’ *note create_subprocess_exec(): a1a.           建立一個子行程。
                                                       
                                                       
‘await’ *note create_subprocess_shell(): a1b.          執行一個 shell 命令。
                                                       

範例
....

   * *note 執行一個 shell 指令: 312f.。

   * 請參閱*note 子行程 APIs: 30b1. 相關文件。


File: python.info,  Node: 串流 Streams,  Next: 同步化 Synchronization,  Prev: 子行程 Subprocesses,  Up: 高階 API 索引

5.18.1.119 串流 (Streams)
.........................

用於網路 IO 處理的高階 API。

‘await’ *note open_connection(): abb.                  建立一個 TCP 連線。
                                                       
                                                       
‘await’ *note open_unix_connection(): 30f2.            建立一個 Unix socket 連線。
                                                       
                                                       
‘await’ *note start_server(): abc.                     啟動一個 TCP 伺服器。
                                                       
                                                       
‘await’ *note start_unix_server(): 30f4.               啟動一個 Unix socket 伺服器。
                                                       
                                                       
*note StreamReader: 17c8.                              接收網路資料的高階 async/await 物件。
                                                       
                                                       
*note StreamWriter: 15fc.                              傳送網路資料的高階 async/await 物件。
                                                       

範例
....

   * *note TCP 客戶端範例: 30ee.。

   * 請參閱*note 串流 APIs: 30b0. 文件。


File: python.info,  Node: 同步化 Synchronization,  Next: 例外<9>,  Prev: 串流 Streams,  Up: 高階 API 索引

5.18.1.120 同步化 (Synchronization)
...................................

類似執行緒且能被用於 Task 中的同步化原始物件 (primitive)。

*note Lock: a14.                                       一個互斥鎖 (mutex lock)。
                                                       
                                                       
*note Event: a15.                                      一個事件物件。
                                                       
                                                       
*note Condition: a16.                                  一個條件物件。
                                                       
                                                       
*note Semaphore: a17.                                  一個旗號 (semaphore) 物件。
                                                       
                                                       
*note BoundedSemaphore: a18.                           一個有界的旗號物件。
                                                       
                                                       
*note Barrier: 5a6.                                    一個屏障物件。
                                                       

範例
....

   * *note 使用 asyncio.Event: 3119.。

   * *note 使用 asyncio.Barrier: 3127.。

   * 請參閱 asyncio 關於*note 同步化原始物件: 30b3.的文件。


File: python.info,  Node: 例外<9>,  Prev: 同步化 Synchronization,  Up: 高階 API 索引

5.18.1.121 例外
...............

*note asyncio.CancelledError: 19e.                     當一 Task 物件被取消時被引發。請參閱
                                                       *note Task.cancel(): 19d.。
                                                       
                                                       
*note asyncio.BrokenBarrierError: 5a7.                 當一 Barrier 物件損壞時被引發。請參閱
                                                       *note Barrier.wait(): 3126.。
                                                       

範例
....

   * *note 在取消請求發生的程式中處理 CancelledError 例外: 30eb.。

   * 請參閱 *note asyncio 專用例外: 3161.完整列表。


File: python.info,  Node: 低階 API 索引,  Next: 使用 asyncio 開發,  Prev: 高階 API 索引,  Up: asyncio --- 非同步 I/O

5.18.1.122 低階 API 索引
........................

本頁列出所有低階 asyncio APIs。

* Menu:

* 獲取事件迴圈::
* 事件迴圈方法: 事件迴圈方法<2>.
* 傳輸::
* 協定::
* 事件迴圈 Policies::


File: python.info,  Node: 獲取事件迴圈,  Next: 事件迴圈方法<2>,  Up: 低階 API 索引

5.18.1.123 獲取事件迴圈
.......................

*note asyncio.get_running_loop(): aae.                 '推薦使用'於獲取當前運行事件迴圈 (event loop) 的函式
                                                       。
                                                       
                                                       
*note asyncio.get_event_loop(): 2a3.                   獲得一個（正在運行的或透過當前 policy 建立的）事件迴
                                                       圈實例。
                                                       
                                                       
*note asyncio.set_event_loop(): 16cf.                  透過當前 policy 來設定當前事件迴圈。
                                                       
                                                       
*note asyncio.new_event_loop(): 30bd.                  建立一個新的事件迴圈。
                                                       

範例
....

   * *note 使用 asyncio.get_running_loop(): 31b3.。


File: python.info,  Node: 事件迴圈方法<2>,  Next: 傳輸,  Prev: 獲取事件迴圈,  Up: 低階 API 索引

5.18.1.124 事件迴圈方法
.......................

也請查閱文件中關於*note 事件迴圈方法: 316e.的主要段落。

生命週期
........

*note loop.run_until_complete(): c1e.                  執行一個 Future/Task/awaitable（可等待物件）直到完成
                                                       。
                                                       
                                                       
*note loop.run_forever(): 3170.                        持續運行事件迴圈。
                                                       
                                                       
*note loop.stop(): c23.                                停止事件迴圈。
                                                       
                                                       
*note loop.close(): 3172.                              關閉事件迴圈。
                                                       
                                                       
*note loop.is_running(): 3171.                         如果事件迴圈正在執行則回傳 ‘True’。
                                                       
                                                       
*note loop.is_closed(): d6a.                           如果事件迴圈已經被關閉則回傳 ‘True’。
                                                       
                                                       
‘await’ *note loop.shutdown_asyncgens(): c24.          關閉非同步產生器 (asynchronous generators)。
                                                       

除錯
....

*note loop.set_debug(): d68.                           開啟或禁用除錯模式。
                                                       
                                                       
*note loop.get_debug(): d69.                           獲取當前除錯模式。
                                                       

為回呼函式排程
..............

*note loop.call_soon(): aa7.                           儘快調用回呼函式 (callback)。
                                                       
                                                       
*note loop.call_soon_threadsafe(): aa8.                *note loop.call_soon(): aa7. 方法之有支援執行緒安全
                                                       (thread-safe) 變體。
                                                       
                                                       
*note loop.call_later(): aa9.                          在給定時間'之後'調用回呼函式。
                                                       
                                                       
*note loop.call_at(): aaa.                             在給定時間'當下'調用回呼函式。
                                                       

執行緒 (Thread)/行程池 (Process Pool)
.....................................

‘await’ *note loop.run_in_executor(): 88e.             在 *note concurrent.futures: 1a. 執行器 (excutor) 中
                                                       執行一個 CPU 密集型 (CPU-bound) 或其它阻塞型式的函式
                                                       。
                                                       
                                                       
*note loop.set_default_executor(): 6e7.                為 *note loop.run_in_executor(): 88e. 設定預設執行器
                                                       。
                                                       

Tasks 與 Futures
................

*note loop.create_future(): c20.                       建立一個 *note Future: b74. 物件。
                                                       
                                                       
*note loop.create_task(): 980.                         像是 *note Task: 480. 一樣，為協程 (coroutine) 排程
                                                       。
                                                       
                                                       
*note loop.set_task_factory(): d6c.                    設定被 *note loop.create_task(): 980. 用來建立
                                                       *note Tasks: 480. 的工廠函式 (factory)。
                                                       
                                                       
*note loop.get_task_factory(): d6d.                    獲取被 *note loop.create_task(): 980. 用來建立
                                                       *note Tasks: 480. 的工廠函式。
                                                       

DNS
...

‘await’ *note loop.getaddrinfo(): bbb.                 非同步版本的 *note socket.getaddrinfo(): 1654.。
                                                       
                                                       
‘await’ *note loop.getnameinfo(): bbc.                 非同步版本的 *note socket.getnameinfo(): 15be.。
                                                       

網路和 IPC
..........

‘await’ *note loop.create_connection(): 5a8.           開啟一個 TCP 連線。
                                                       
                                                       
‘await’ *note loop.create_server(): ab6.               建立一個 TCP 伺服器。
                                                       
                                                       
‘await’ *note loop.create_unix_connection(): 30f3.     開啟一個 Unix socket 連線。
                                                       
                                                       
‘await’ *note loop.create_unix_server(): 194.          建立一個 Unix socket 伺服器。
                                                       
                                                       
‘await’ *note loop.connect_accepted_socket(): abd.     將 *note socket: d47. 包裝成 ‘(transport,
                                                       protocol)’。
                                                       
                                                       
‘await’ *note loop.create_datagram_endpoint(): 6d7.    開啟一個資料單元 (datagram) (UDP) 連線。
                                                       
                                                       
‘await’ *note loop.sendfile(): 3185.                   透過傳輸通道傳送一個檔案。
                                                       
                                                       
‘await’ *note loop.start_tls(): aac.                   將一個已存在的連線升級到 TLS。
                                                       
                                                       
‘await’ *note loop.connect_read_pipe(): 3136.          將 pipe（管道）讀取端包裝成 ‘(transport, protocol)’。
                                                       
                                                       
‘await’ *note loop.connect_write_pipe(): 3137.         將 pipe 寫入端包裝成 ‘(transport, protocol)’。
                                                       

Sockets
.......

‘await’ *note loop.sock_recv(): bb8.                   從 *note socket: d47. 接收資料。
                                                       
                                                       
‘await’ *note loop.sock_recv_into(): aad.              將從 *note socket: d47. 接收到的資料存放於一個緩衝區
                                                       (buffer) 中。
                                                       
                                                       
‘await’ *note loop.sock_recvfrom(): 5ab.               從 *note socket: d47. 接收一個資料單元。
                                                       
                                                       
‘await’ *note loop.sock_recvfrom_into(): 5ac.          將從 *note socket: d47. 接收到的資料單元存放於一個緩
                                                       衝區中。
                                                       
                                                       
‘await’ *note loop.sock_sendall(): bb9.                傳送資料到 *note socket: d47.。
                                                       
                                                       
‘await’ *note loop.sock_sendto(): 5aa.                 透過 *note socket: d47. 將資料單元傳送至給定的地址。
                                                       
                                                       
‘await’ *note loop.sock_connect(): d70.                連接 *note socket: d47.。
                                                       
                                                       
‘await’ *note loop.sock_accept(): bba.                 接受一個 *note socket: d47. 連線。
                                                       
                                                       
‘await’ *note loop.sock_sendfile(): ab1.               透過 *note socket: d47. 傳送一個檔案。
                                                       
                                                       
*note loop.add_reader(): 310e.                         開始監控一個檔案描述器 (file descriptor) 的可讀取性
                                                       。
                                                       
                                                       
*note loop.remove_reader(): 3188.                      停止監控一個檔案描述器的可讀取性。
                                                       
                                                       
*note loop.add_writer(): 3189.                         開始監控一個檔案描述器的可寫入性。
                                                       
                                                       
*note loop.remove_writer(): 318a.                      停止監控一個檔案描述器的可寫入性。
                                                       

Unix 信號
.........

*note loop.add_signal_handler(): 3192.                 為 *note signal: b4. 新增一個處理函式 (handler)。
                                                       
                                                       
*note loop.remove_signal_handler(): 3193.              刪除 *note signal: b4. 的處理函式。
                                                       

子行程
......

*note loop.subprocess_exec(): 3133.                    衍生 (spawn) 一個子行程 (subprocess)。
                                                       
                                                       
*note loop.subprocess_shell(): 3134.                   從 shell 指令衍生一個子行程。
                                                       

錯誤處理
........

*note loop.call_exception_handler(): 3197.             呼叫例外處理函式。
                                                       
                                                       
*note loop.set_exception_handler(): 3196.              設定一個新的例外處理函式。
                                                       
                                                       
*note loop.get_exception_handler(): c21.               獲取當前例外處理函式。
                                                       
                                                       
*note loop.default_exception_handler(): 3198.          預設例外處理函式實作。
                                                       

範例
....

   * *note 使用 asyncio.new_event_loop() 和 loop.run_forever(): 31a3.。

   * *note 使用 loop.call_later(): 31a5.。

   * 使用 ‘loop.create_connection()’ 以實作*note 一個 echo 客戶端:
     3105.。

   * 使用 ‘loop.create_connection()’ 來*note 連接 socket: 310c.。

   * *note 使用 add_reader() 監控 FD 的讀取事件: 310d.。

   * *note 使用 loop.add_signal_handler(): 31a8.。

   * *note 使用 loop.add_signal_handler(): 314b.。


File: python.info,  Node: 傳輸,  Next: 協定,  Prev: 事件迴圈方法<2>,  Up: 低階 API 索引

5.18.1.125 傳輸
...............

所有傳輸方式都有實作以下方法：

*note transport.close(): 317e.                         關閉傳輸。
                                                       
                                                       
*note transport.is_closing(): c1f.                     如果傳輸正在關閉或已經關閉則回傳 ‘True’。
                                                       
                                                       
*note transport.get_extra_info(): a3f.                 請求傳輸的相關資訊。
                                                       
                                                       
*note transport.set_protocol(): 31c3.                  設定一個新協定。
                                                       
                                                       
*note transport.get_protocol(): 31c4.                  回傳當前協定。
                                                       

可以接收資料（TCP 和 Unix 連線、pipe 等）的傳輸。它由 *note
loop.create_connection(): 5a8.、*note loop.create_unix_connection():
30f3.、*note loop.connect_read_pipe(): 3136. 等方法回傳：

讀取傳輸
........

*note transport.is_reading(): abf.                     如果傳輸正在接收則回傳 ‘True’。
                                                       
                                                       
*note transport.pause_reading(): ac1.                  暫停接收。
                                                       
                                                       
*note transport.resume_reading(): ac0.                 繼續接收。
                                                       

可以傳送資料（TCP 和 Unix 連線、pipe 等）的傳輸。它由 *note
loop.create_connection(): 5a8.、*note loop.create_unix_connection():
30f3.、*note loop.connect_write_pipe(): 3137. 等方法回傳：

寫入傳輸
........

*note transport.write(): 31cd.                         將資料寫入傳輸。
                                                       
                                                       
*note transport.writelines(): 162a.                    將緩衝區資料寫入傳輸。
                                                       
                                                       
*note transport.can_write_eof(): 31c7.                 如果傳輸支援傳送 EOF 則回傳 *note True: bb4.。
                                                       
                                                       
*note transport.write_eof(): 31c8.                     在清除 (flush) 已緩衝的資料後關閉傳輸並傳送 EOF。
                                                       
                                                       
*note transport.abort(): 31a0.                         立即關閉傳輸。
                                                       
                                                       
*note transport.get_write_buffer_size(): 31c9.         回傳當前輸出緩衝區的大小。
                                                       
                                                       
*note transport.get_write_buffer_limits(): d6b.        回傳用於寫入流量控制 (write flow control) 的高低標記
                                                       位 (high and low water marks)。
                                                       
                                                       
*note transport.set_write_buffer_limits(): 31ca.       為寫入流量控制設定高低標記位。
                                                       

由 *note loop.create_datagram_endpoint(): 6d7. 回傳的傳輸：

資料單元傳輸
............

*note transport.sendto(): 195.                         傳送資料到連線遠端。
                                                       
                                                       
*note transport.abort(): 31cf.                         立即關閉傳輸。
                                                       

基於子行程的低階傳輸抽象，它會由 *note loop.subprocess_exec(): 3133. 和
*note loop.subprocess_shell(): 3134. 所回傳：

子行程傳輸
..........

*note transport.get_pid(): 31d1.                       回傳子行程的行程 id。
                                                       
                                                       
*note transport.get_pipe_transport(): 31d2.            回傳被請求用於通訊 pipe （'stdin'、'stdout' 或
                                                       'stderr'）的傳輸。
                                                       
                                                       
*note transport.get_returncode(): 31d3.                回傳子行程的回傳代號 (return code)。
                                                       
                                                       
*note transport.kill(): 31d4.                          殺死子行程。
                                                       
                                                       
*note transport.send_signal(): 31d6.                   傳送一個訊號到子行程。
                                                       
                                                       
*note transport.terminate(): 31d5.                     停止子行程。
                                                       
                                                       
*note transport.close(): 31d7.                         殺死子行程並關閉所有 pipes。
                                                       


File: python.info,  Node: 協定,  Next: 事件迴圈 Policies,  Prev: 傳輸,  Up: 低階 API 索引

5.18.1.126 協定
...............

協定類別可以實作以下'回呼方法'：

‘callback’ *note connection_made(): 317c.              在連線建立時被呼叫。
                                                       
                                                       
‘callback’ *note connection_lost(): 31bf.              在失去連線或連線關閉時被呼叫。
                                                       
                                                       
‘callback’ *note pause_writing(): 31cb.                在傳輸緩衝區超過高標記位時被呼叫。
                                                       
                                                       
‘callback’ *note resume_writing(): 31cc.               在傳輸緩衝區低於低標記位時被呼叫。
                                                       

串流協定 (TCP, Unix socket, Pipes)
..................................

‘callback’ *note data_received(): 1690.                在接收到資料時被呼叫。
                                                       
                                                       
‘callback’ *note eof_received(): 31db.                 在接收到 EOF 時被呼叫。
                                                       

緩衝串流協定
............

‘callback’ *note get_buffer(): 31dd.                   呼叫後會分配新的接收緩衝區。
                                                       
                                                       
‘callback’ *note buffer_updated(): 31de.               在以接收到的資料更新緩衝區時被呼叫。
                                                       
                                                       
‘callback’ *note eof_received(): 31df.                 在接收到 EOF 時被呼叫。
                                                       

資料單元協定
............

‘callback’ *note datagram_received(): 31e1.            在接收到資料單元時被呼叫。
                                                       
                                                       
‘callback’ *note error_received(): 31e2.               在前一個傳送或接收操作引發 *note OSError: 350. 時被
                                                       呼叫。
                                                       

子行程協定
..........

‘callback’ *note pipe_data_received(): 16c9.           在子行程向 'stdout' 或 'stderr' pipe 寫入資料時被呼
                                                       叫。
                                                       
                                                       
‘callback’ *note pipe_connection_lost(): 31e4.         在與子行程通訊的其中一個 pipes 關閉時被呼叫。
                                                       
                                                       
‘callback’ *note process_exited(): 16c8.               在子行程退出時呼叫。它可以在
                                                       *note pipe_data_received(): 16c9. 和
                                                       *note pipe_connection_lost(): 31e4. 方法之前呼叫。
                                                       


File: python.info,  Node: 事件迴圈 Policies,  Prev: 協定,  Up: 低階 API 索引

5.18.1.127 事件迴圈 Policies
............................

Policy 是改變 *note asyncio.get_event_loop(): 2a3. 這類函式行為的一個低
階機制。更多細節請見 *note Policy 相關段落: 3168.。

存取 Policy
...........

*note asyncio.get_event_loop_policy(): 31f3.           回傳當前整個行程中的 Policy。
                                                       
                                                       
*note asyncio.set_event_loop_policy(): 31f4.           設定整個行程中的一個新 Policy。
                                                       
                                                       
*note AbstractEventLoopPolicy: 31f1.                   Policy 物件的基礎類別。
                                                       


File: python.info,  Node: 使用 asyncio 開發,  Prev: 低階 API 索引,  Up: asyncio --- 非同步 I/O

5.18.1.128 使用 asyncio 開發
............................

非同步程式設計 (asynchronous programming) 與傳統的"順序"程式設計
(sequential programming) 不同。

本頁列出常見的錯誤和陷阱，並解釋如何避免它們。

* Menu:

* 除錯模式::
* 並行性和多執行緒 (Concurrency and Multithreading): 並行性和多執行緒 Concurrency and Multithreading.
* 執行阻塞的程式::
* 日誌記錄::
* 偵測從未被等待的 (never-awaited) 協程: 偵測從未被等待的 never-awaited 協程.
* 偵測從未被獲取的 (never-retrieved) 例外: 偵測從未被獲取的 never-retrieved 例外.


File: python.info,  Node: 除錯模式,  Next: 並行性和多執行緒 Concurrency and Multithreading,  Up: 使用 asyncio 開發

5.18.1.129 除錯模式
...................

在預設情況下 asyncio 以正式生產模式 (production mode) 執行。為了讓開發更
輕鬆，asyncio 還有一種'除錯模式 (debug mode)'。

有幾種方法可以啟用 asyncio 除錯模式：

   * 將 *note PYTHONASYNCIODEBUG: 1c50. 環境變數設定為 ‘1’。

   * 使用 *note Python 開發模式 (Development Mode): 1dd.。

   * 將 ‘debug=True’ 傳遞給 *note asyncio.run(): 423.。

   * 呼叫 *note loop.set_debug(): d68.。

除了啟用除錯模式外，還要考慮：

   * 將 *note asyncio logger（日誌記錄器）: 3227.的日誌級别設置為 *note
     logging.DEBUG: 1bf5.，例如下面的程式片段可以在應用程式啟動時運行：

          logging.basicConfig(level=logging.DEBUG)

   * 配置 *note warnings: fa. 模組以顯示 *note ResourceWarning: 229. 警
     告。一種方法是使用 *note -W: 86c. ‘default’ 命令列選項。

啟用除錯模式時：

   * asyncio 會檢查*note 未被等待的協程: 3228.並記錄他們；這會減輕"被遺
     忘的等待 (forgotten await)" 問題。

   * 許多非執行緒安全 (non-threadsafe) 的 asyncio APIs（例如 *note
     loop.call_soon(): aa7. 和 *note loop.call_at(): aaa. 方法），如果從
     錯誤的執行緒呼叫就會引發例外。

   * 如果執行一個 I/O 操作花費的時間太長，則將 I/O 選擇器 (selector) 的
     執行時間記錄到日誌中。

   * 執行時間超過 100 毫秒的回呼 (callback) 將會被記錄於日誌。屬性 *note
     loop.slow_callback_duration: 319a. 可用於設定以秒為單位的最小執行持
     續時間，超過這個值執行時間就會被視為"緩慢"。


File: python.info,  Node: 並行性和多執行緒 Concurrency and Multithreading,  Next: 執行阻塞的程式,  Prev: 除錯模式,  Up: 使用 asyncio 開發

5.18.1.130 並行性和多執行緒 (Concurrency and Multithreading)
............................................................

事件迴圈在執行緒中運行（通常是主執行緒），並在其執行緒中執行所有回呼和
Tasks（任務）。當一個 Task 在事件迴圈中運行時，沒有其他 Task 可以在同一
個執行緒中運行。當一個 Task 執行一個 ‘await’ 運算式時，正在執行的 Task 會
被暫停，而事件迴圈會執行下一個 Task。

要從不同的 OS 執行緒為一個 *note callback: 27f7. 排程，應該使用 *note
loop.call_soon_threadsafe(): aa8. 方法。例如：

     loop.call_soon_threadsafe(callback, *args)

幾乎所有 asyncio 物件都不支援執行緒安全 (thread safe)，這通常不是問題，
除非在 Task 或回呼函式之外有程式需要和它們一起運作。如果需要這樣的程式來
呼叫低階 asyncio API，應該使用 *note loop.call_soon_threadsafe(): aa8. 方
法，例如：

     loop.call_soon_threadsafe(fut.cancel)

要從不同的 OS 執行緒為一個協程物件排程，應該使用 *note
run_coroutine_threadsafe(): 826. 函式。它會回傳一個 *note
concurrent.futures.Future: 1149. 以存取結果：

     async def coro_func():
          return await asyncio.sleep(1, 42)

     # Later in another OS thread:

     future = asyncio.run_coroutine_threadsafe(coro_func(), loop)
     # Wait for the result:
     result = future.result()

為了能夠處理訊號，事件迴圈必須於主執行緒中運行。

*note loop.run_in_executor(): 88e. 方法可以和 *note
concurrent.futures.ThreadPoolExecutor: 6e6. 一起使用，這能夠在作業系統上
另一個不同的執行緒中執行阻塞程式，且避免阻塞執行事件迴圈的執行緒。

目前沒有什麼辦法能直接從另一個行程（例如透過 *note multiprocessing: 86.
啟動的程序）來為協程或回呼排程。*note 事件迴圈方法: 316e.小節列出了可以
從 pipes（管道）讀取並監視 file descriptor（檔案描述器）而不會阻塞事件迴
圈的 API。此外，asyncio 的*note 子行程: 30b1. API 提供了一種啟動行程並從
事件迴圈與其通訊的辦法。最後，之前提到的 *note loop.run_in_executor():
88e. 方法也可和 *note concurrent.futures.ProcessPoolExecutor: 893. 搭配
使用，以在另一個行程中執行程式。


File: python.info,  Node: 執行阻塞的程式,  Next: 日誌記錄,  Prev: 並行性和多執行緒 Concurrency and Multithreading,  Up: 使用 asyncio 開發

5.18.1.131 執行阻塞的程式
.........................

不應該直接呼叫阻塞（CPU 密集型）程式。例如一個執行 1 秒 CPU 密集型計算的
函式，那麼所有並行非同步 Tasks 和 IO 操作都會被延遲 1 秒。

一個 executor（執行器）可以被用來在不同的執行緒、或甚至不同的行程中執行
任務，以避免使用事件迴圈阻塞 OS 執行緒。詳情請見 *note
loop.run_in_executor(): 88e. 方法。


File: python.info,  Node: 日誌記錄,  Next: 偵測從未被等待的 never-awaited 協程,  Prev: 執行阻塞的程式,  Up: 使用 asyncio 開發

5.18.1.132 日誌記錄
...................

asyncio 使用 *note logging: 7b. 模組，所有日誌記錄都是透過 ‘"asyncio"’
logger 執行的。

日誌級別被預設為 *note logging.INFO: 1bf6.，它可以很容易地被調整：

     logging.getLogger("asyncio").setLevel(logging.WARNING)

網路日誌記錄可能會阻塞事件迴圈。建議使用獨立的執行緒來處理日誌或使用非阻
塞 IO，範例請參見 *note Dealing with handlers that block: 322d.。


File: python.info,  Node: 偵測從未被等待的 never-awaited 協程,  Next: 偵測從未被獲取的 never-retrieved 例外,  Prev: 日誌記錄,  Up: 使用 asyncio 開發

5.18.1.133 偵測從未被等待的 (never-awaited) 協程
................................................

當協程函式被呼叫而不是被等待時（即執行 ‘coro()’ 而不是 ‘await coro()’）
或者協程沒有透過 *note asyncio.create_task(): 5a1. 被排程，asyncio 將會
發出 *note RuntimeWarning: 1a3.：

     import asyncio

     async def test():
         print("never scheduled")

     async def main():
         test()

     asyncio.run(main())

輸出：

     test.py:7: RuntimeWarning: coroutine 'test' was never awaited
       test()

除錯模式中的輸出：

     test.py:7: RuntimeWarning: coroutine 'test' was never awaited
     Coroutine created at (most recent call last)
       File "../t.py", line 9, in <module>
         asyncio.run(main(), debug=True)

       < .. >

       File "../t.py", line 7, in main
         test()
       test()

常用的修復方法是去等待協程或者呼叫 *note asyncio.create_task(): 5a1. 函
式：

     async def main():
         await test()


File: python.info,  Node: 偵測從未被獲取的 never-retrieved 例外,  Prev: 偵測從未被等待的 never-awaited 協程,  Up: 使用 asyncio 開發

5.18.1.134 偵測從未被獲取的 (never-retrieved) 例外
..................................................

如果呼叫 *note Future.set_exception(): 30e2.，但 Future 物件從未被等待，
例外將無法被傳播 (propagate) 到使用者程式。在這種情況下，當 Future 物件
被垃圾回收 (garbage collected) 時，asyncio 將發出一則日誌訊息。

未處理例外的例子：

     import asyncio

     async def bug():
         raise Exception("not consumed")

     async def main():
         asyncio.create_task(bug())

     asyncio.run(main())

輸出：

     Task exception was never retrieved
     future: <Task finished coro=<bug() done, defined at test.py:3>
       exception=Exception('not consumed')>

     Traceback (most recent call last):
       File "test.py", line 4, in bug
         raise Exception("not consumed")
     Exception: not consumed

*note 啟用除錯模式: 1c51.以取得任務建立處的追蹤資訊 (traceback)：

     asyncio.run(main(), debug=True)

除錯模式中的輸出：

     Task exception was never retrieved
     future: <Task finished coro=<bug() done, defined at test.py:3>
         exception=Exception('not consumed') created at asyncio/tasks.py:321>

     source_traceback: Object created at (most recent call last):
       File "../t.py", line 9, in <module>
         asyncio.run(main(), debug=True)

     < .. >

     Traceback (most recent call last):
       File "../t.py", line 4, in bug
         raise Exception("not consumed")
     Exception: not consumed

     備註: asyncio 的原始碼可以在 Lib/asyncio/(1) 中找到。

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/asyncio/


File: python.info,  Node: socket --- 低階網路介面,  Next: ssl --- socket 物件的 TLS/SSL 包裝器,  Prev: asyncio --- 非同步 I/O,  Up: Networking and Interprocess Communication

5.18.2 ‘socket’ -- 低階網路介面
-------------------------------

'原始碼：'Lib/socket.py(1)

__________________________________________________________________

This module provides access to the BSD 'socket' interface.  It is
available on all modern Unix systems, Windows, MacOS, and probably
additional platforms.

     備註: Some behavior may be platform dependent, since calls are made
     to the operating system socket APIs.

*note 適用: 1c56.：非 WASI。

This module does not work or is not available on WebAssembly.  See *note
WebAssembly 平台: 16e6. for more information.

The Python interface is a straightforward transliteration of the Unix
system call and library interface for sockets to Python's
object-oriented style: the *note socket(): d47. function returns a
'socket object' whose methods implement the various socket system calls.
Parameter types are somewhat higher-level than in the C interface: as
with ‘read()’ and ‘write()’ operations on Python files, buffer
allocation on receive operations is automatic, and buffer length is
implicit on send operations.

也參考
......

*note socketserver: b9. 模組

     Classes that simplify writing network servers.

*note ssl: bb. 模組

     A TLS/SSL wrapper for socket objects.

* Menu:

* Socket 系列家族::
* 模組內容: 模組內容<4>.
* Socket 物件::
* Notes on socket timeouts::
* 範例: 範例<25>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/socket.py


File: python.info,  Node: Socket 系列家族,  Next: 模組內容<4>,  Up: socket --- 低階網路介面

5.18.2.1 Socket 系列家族
........................

Depending on the system and the build options, various socket families
are supported by this module.

The address format required by a particular socket object is
automatically selected based on the address family specified when the
socket object was created.  Socket addresses are represented as follows:

   - The address of an *note AF_UNIX: 1724. socket bound to a file
     system node is represented as a string, using the file system
     encoding and the ‘'surrogateescape'’ error handler (see PEP
     383(1)).  An address in Linux's abstract namespace is returned as a
     *note bytes-like object: cd4. with an initial null byte; note that
     sockets in this namespace can communicate with normal file system
     sockets, so programs intended to run on Linux may need to deal with
     both types of address.  A string or bytes-like object can be used
     for either type of address when passing it as an argument.

     在 3.3 版的變更: Previously, *note AF_UNIX: 1724. socket paths were
     assumed to use UTF-8 encoding.

     在 3.5 版的變更: Writable *note bytes-like object: cd4. is now
     accepted.

   - A pair ‘(host, port)’ is used for the *note AF_INET: 1722. address
     family, where 'host' is a string representing either a hostname in
     internet domain notation like ‘'daring.cwi.nl'’ or an IPv4 address
     like ‘'100.50.200.5'’, and 'port' is an integer.

        - For IPv4 addresses, two special forms are accepted instead of
          a host address: ‘''’ represents ‘INADDR_ANY’, which is used to
          bind to all interfaces, and the string ‘'<broadcast>'’
          represents ‘INADDR_BROADCAST’.  This behavior is not
          compatible with IPv6, therefore, you may want to avoid these
          if you intend to support IPv6 with your Python programs.

   - For *note AF_INET6: 1723. address family, a four-tuple ‘(host,
     port, flowinfo, scope_id)’ is used, where 'flowinfo' and 'scope_id'
     represent the ‘sin6_flowinfo’ and ‘sin6_scope_id’ members in
     ‘struct sockaddr_in6’ in C. For *note socket: b8. module methods,
     'flowinfo' and 'scope_id' can be omitted just for backward
     compatibility.  Note, however, omission of 'scope_id' can cause
     problems in manipulating scoped IPv6 addresses.

     在 3.7 版的變更: For multicast addresses (with 'scope_id'
     meaningful) 'address' may not contain ‘%scope_id’ (or ‘zone id’)
     part.  This information is superfluous and may be safely omitted
     (recommended).

   - ‘AF_NETLINK’ sockets are represented as pairs ‘(pid, groups)’.

   - Linux-only support for TIPC is available using the ‘AF_TIPC’
     address family.  TIPC is an open, non-IP based networked protocol
     designed for use in clustered computer environments.  Addresses are
     represented by a tuple, and the fields depend on the address type.
     The general tuple form is ‘(addr_type, v1, v2, v3 [, scope])’,
     where:

        - 'addr_type' is one of ‘TIPC_ADDR_NAMESEQ’, ‘TIPC_ADDR_NAME’,
          or ‘TIPC_ADDR_ID’.

        - 'scope' is one of ‘TIPC_ZONE_SCOPE’, ‘TIPC_CLUSTER_SCOPE’, and
          ‘TIPC_NODE_SCOPE’.

        - If 'addr_type' is ‘TIPC_ADDR_NAME’, then 'v1' is the server
          type, 'v2' is the port identifier, and 'v3' should be 0.

          If 'addr_type' is ‘TIPC_ADDR_NAMESEQ’, then 'v1' is the server
          type, 'v2' is the lower port number, and 'v3' is the upper
          port number.

          If 'addr_type' is ‘TIPC_ADDR_ID’, then 'v1' is the node, 'v2'
          is the reference, and 'v3' should be set to 0.

   - A tuple ‘(interface, )’ is used for the *note AF_CAN: 3234. address
     family, where 'interface' is a string representing a network
     interface name like ‘'can0'’.  The network interface name ‘''’ can
     be used to receive packets from all network interfaces of this
     family.

        - *note CAN_ISOTP: 3235. protocol require a tuple ‘(interface,
          rx_addr, tx_addr)’ where both additional parameters are
          unsigned long integer that represent a CAN identifier
          (standard or extended).

        - *note CAN_J1939: 8d6. protocol require a tuple ‘(interface,
          name, pgn, addr)’ where additional parameters are 64-bit
          unsigned integer representing the ECU name, a 32-bit unsigned
          integer representing the Parameter Group Number (PGN), and an
          8-bit integer representing the address.

   - A string or a tuple ‘(id, unit)’ is used for the ‘SYSPROTO_CONTROL’
     protocol of the ‘PF_SYSTEM’ family.  The string is the name of a
     kernel control using a dynamically assigned ID. The tuple can be
     used if ID and unit number of the kernel control are known or if a
     registered ID is used.

     在 3.3 版被加入.

   - ‘AF_BLUETOOTH’ supports the following protocols and address
     formats:

        - ‘BTPROTO_L2CAP’ accepts ‘(bdaddr, psm)’ where ‘bdaddr’ is the
          Bluetooth address as a string and ‘psm’ is an integer.

        - ‘BTPROTO_RFCOMM’ accepts ‘(bdaddr, channel)’ where ‘bdaddr’ is
          the Bluetooth address as a string and ‘channel’ is an integer.

        - ‘BTPROTO_HCI’ accepts ‘(device_id,)’ where ‘device_id’ is
          either an integer or a string with the Bluetooth address of
          the interface.  (This depends on your OS; NetBSD and
          DragonFlyBSD expect a Bluetooth address while everything else
          expects an integer.)

          在 3.2 版的變更: 加入對 NetBSD 和 DragonFlyBSD 的支援。

        - ‘BTPROTO_SCO’ accepts ‘bdaddr’ where ‘bdaddr’ is a *note
          bytes: 1a5. object containing the Bluetooth address in a
          string format.  (ex.  ‘b'12:23:34:45:56:67'’) This protocol is
          not supported under FreeBSD.

   - *note AF_ALG: c7e. is a Linux-only socket based interface to Kernel
     cryptography.  An algorithm socket is configured with a tuple of
     two to four elements ‘(type, name [, feat [, mask]])’, where:

        - 'type' is the algorithm type as string, e.g.  ‘aead’, ‘hash’,
          ‘skcipher’ or ‘rng’.

        - 'name' is the algorithm name and operation mode as string,
          e.g.  ‘sha256’, ‘hmac(sha256)’, ‘cbc(aes)’ or
          ‘drbg_nopr_ctr_aes256’.

        - 'feat' and 'mask' are unsigned 32bit integers.

     *note 適用: 1c56.：Linux >= 2.6.38。

     Some algorithm types require more recent Kernels.

     在 3.6 版被加入.

   - *note AF_VSOCK: b19. allows communication between virtual machines
     and their hosts.  The sockets are represented as a ‘(CID, port)’
     tuple where the context ID or CID and port are integers.

     *note 適用: 1c56.：Linux 3.9 以上。

     請見 ‘vsock(7)(2)’

     在 3.7 版被加入.

   - *note AF_PACKET: 3236. is a low-level interface directly to network
     devices.  The addresses are represented by the tuple ‘(ifname,
     proto[, pkttype[, hatype[, addr]]])’ where:

        - 'ifname' - String specifying the device name.

        - 'proto' - The Ethernet protocol number.  May be *note
          ETH_P_ALL: 16ab. to capture all protocols, one of the *note
          ETHERTYPE_* constants: 16ac. or any other Ethernet protocol
          number.

        - 'pkttype' - Optional integer specifying the packet type:

             - ‘PACKET_HOST’ (the default) - Packet addressed to the
               local host.

             - ‘PACKET_BROADCAST’ - Physical-layer broadcast packet.

             - ‘PACKET_MULTICAST’ - Packet sent to a physical-layer
               multicast address.

             - ‘PACKET_OTHERHOST’ - Packet to some other host that has
               been caught by a device driver in promiscuous mode.

             - ‘PACKET_OUTGOING’ - Packet originating from the local
               host that is looped back to a packet socket.

        - 'hatype' - Optional integer specifying the ARP hardware
          address type.

        - 'addr' - Optional bytes-like object specifying the hardware
          physical address, whose interpretation depends on the device.

     *note 適用: 1c56.：Linux >= 2.2。

   - *note AF_QIPCRTR: 3237. is a Linux-only socket based interface for
     communicating with services running on co-processors in Qualcomm
     platforms.  The address family is represented as a ‘(node, port)’
     tuple where the 'node' and 'port' are non-negative integers.

     *note 適用: 1c56.：Linux >= 4.7。

     在 3.8 版被加入.

   - ‘IPPROTO_UDPLITE’ is a variant of UDP which allows you to specify
     what portion of a packet is covered with the checksum.  It adds two
     socket options that you can change.
     ‘self.setsockopt(IPPROTO_UDPLITE, UDPLITE_SEND_CSCOV, length)’ will
     change what portion of outgoing packets are covered by the checksum
     and ‘self.setsockopt(IPPROTO_UDPLITE, UDPLITE_RECV_CSCOV, length)’
     will filter out packets which cover too little of their data.  In
     both cases ‘length’ should be in ‘range(8, 2**16, 8)’.

     Such a socket should be constructed with ‘socket(AF_INET,
     SOCK_DGRAM, IPPROTO_UDPLITE)’ for IPv4 or ‘socket(AF_INET6,
     SOCK_DGRAM, IPPROTO_UDPLITE)’ for IPv6.

     *note 適用: 1c56.：Linux 2.6.20 以上、FreeBSD 10.1 以上。

     在 3.9 版被加入.

   - *note AF_HYPERV: 3238. is a Windows-only socket based interface for
     communicating with Hyper-V hosts and guests.  The address family is
     represented as a ‘(vm_id, service_id)’ tuple where the ‘vm_id’ and
     ‘service_id’ are UUID strings.

     The ‘vm_id’ is the virtual machine identifier or a set of known
     VMID values if the target is not a specific virtual machine.  Known
     VMID constants defined on ‘socket’ are:

        - ‘HV_GUID_ZERO’

        - ‘HV_GUID_BROADCAST’

        - ‘HV_GUID_WILDCARD’ - Used to bind on itself and accept
          connections from all partitions.

        - ‘HV_GUID_CHILDREN’ - Used to bind on itself and accept
          connection from child partitions.

        - ‘HV_GUID_LOOPBACK’ - Used as a target to itself.

        - ‘HV_GUID_PARENT’ - When used as a bind accepts connection from
          the parent partition.  When used as an address target it will
          connect to the parent partition.

     The ‘service_id’ is the service identifier of the registered
     service.

     在 3.12 版被加入.

If you use a hostname in the 'host' portion of IPv4/v6 socket address,
the program may show a nondeterministic behavior, as Python uses the
first address returned from the DNS resolution.  The socket address will
be resolved differently into an actual IPv4/v6 address, depending on the
results from DNS resolution and/or the host configuration.  For
deterministic behavior use a numeric address in 'host' portion.

All errors raise exceptions.  The normal exceptions for invalid argument
types and out-of-memory conditions can be raised.  Errors related to
socket or address semantics raise *note OSError: 350. or one of its
subclasses.

Non-blocking mode is supported through *note setblocking(): 2a28.  A
generalization of this based on timeouts is supported through *note
settimeout(): 3239.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0383/

   (2) https://manpages.debian.org/vsock(7)


File: python.info,  Node: 模組內容<4>,  Next: Socket 物件,  Prev: Socket 系列家族,  Up: socket --- 低階網路介面

5.18.2.2 模組內容
.................

The module *note socket: b8. exports the following elements.

* Menu:

* 例外: 例外<10>.
* 常數: 常數<7>.
* 函式: 函式<7>.


File: python.info,  Node: 例外<10>,  Next: 常數<7>,  Up: 模組內容<4>

5.18.2.3 例外
.............

 -- 例外: socket.error

     一個已棄用的 *note OSError: 350. 的別名。

     在 3.3 版的變更: Following PEP 3151(1), this class was made an
     alias of *note OSError: 350.

 -- 例外: socket.herror

     A subclass of *note OSError: 350, this exception is raised for
     address-related errors, i.e.  for functions that use 'h_errno' in
     the POSIX C API, including *note gethostbyname_ex(): 17d0. and
     *note gethostbyaddr(): 17cf.  The accompanying value is a pair
     ‘(h_errno, string)’ representing an error returned by a library
     call.  'h_errno' is a numeric value, while 'string' represents the
     description of 'h_errno', as returned by the ‘hstrerror()’ C
     function.

     在 3.3 版的變更: This class was made a subclass of *note OSError:
     350.

 -- 例外: socket.gaierror

     A subclass of *note OSError: 350, this exception is raised for
     address-related errors by *note getaddrinfo(): 1654. and *note
     getnameinfo(): 15be.  The accompanying value is a pair ‘(error,
     string)’ representing an error returned by a library call.
     'string' represents the description of 'error', as returned by the
     ‘gai_strerror()’ C function.  The numeric 'error' value will match
     one of the ‘EAI_*’ constants defined in this module.

     在 3.3 版的變更: This class was made a subclass of *note OSError:
     350.

 -- 例外: socket.timeout

     A deprecated alias of *note TimeoutError: 7d9.

     A subclass of *note OSError: 350, this exception is raised when a
     timeout occurs on a socket which has had timeouts enabled via a
     prior call to *note settimeout(): 3239. (or implicitly through
     *note setdefaulttimeout(): 323d.).  The accompanying value is a
     string whose value is currently always "timed out".

     在 3.3 版的變更: This class was made a subclass of *note OSError:
     350.

     在 3.10 版的變更: This class was made an alias of *note
     TimeoutError: 7d9.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3151/


File: python.info,  Node: 常數<7>,  Next: 函式<7>,  Prev: 例外<10>,  Up: 模組內容<4>

5.18.2.4 常數
.............

     The AF_* and SOCK_* constants are now ‘AddressFamily’ and
     ‘SocketKind’ *note IntEnum: c86. collections.

     在 3.4 版被加入.

 -- 資料: socket.AF_UNIX
 -- 資料: socket.AF_INET
 -- 資料: socket.AF_INET6

     These constants represent the address (and protocol) families, used
     for the first argument to *note socket(): d47.  If the *note
     AF_UNIX: 1724. constant is not defined then this protocol is
     unsupported.  More constants may be available depending on the
     system.

 -- 資料: socket.AF_UNSPEC

     *note AF_UNSPEC: 3183. means that *note getaddrinfo(): 1654. should
     return socket addresses for any address family (either IPv4, IPv6,
     or any other) that can be used.

 -- 資料: socket.SOCK_STREAM
 -- 資料: socket.SOCK_DGRAM
 -- 資料: socket.SOCK_RAW
 -- 資料: socket.SOCK_RDM
 -- 資料: socket.SOCK_SEQPACKET

     These constants represent the socket types, used for the second
     argument to *note socket(): d47.  More constants may be available
     depending on the system.  (Only *note SOCK_STREAM: 1286. and *note
     SOCK_DGRAM: 1285. appear to be generally useful.)

 -- 資料: socket.SOCK_CLOEXEC
 -- 資料: socket.SOCK_NONBLOCK

     These two constants, if defined, can be combined with the socket
     types and allow you to set some flags atomically (thus avoiding
     possible race conditions and the need for separate calls).

     也參考
     ......

     Secure File Descriptor Handling(1) for a more thorough explanation.

     *note 適用: 1c56.：Linux >= 2.6.27。

     在 3.2 版被加入.

 -- 資料: SO_*
 -- 資料: socket.SOMAXCONN

 -- 資料: MSG_*

 -- 資料: SOL_*

 -- 資料: SCM_*

 -- 資料: IPPROTO_*

 -- 資料: IPPORT_*

 -- 資料: INADDR_*

 -- 資料: IP_*

 -- 資料: IPV6_*

 -- 資料: EAI_*

 -- 資料: AI_*

 -- 資料: NI_*

 -- 資料: TCP_*

     Many constants of these forms, documented in the Unix documentation
     on sockets and/or the IP protocol, are also defined in the socket
     module.  They are generally used in arguments to the *note
     setsockopt(): c7d. and *note getsockopt(): c7c. methods of socket
     objects.  In most cases, only those symbols that are defined in the
     Unix header files are defined; for a few symbols, default values
     are provided.

     在 3.6 版的變更: ‘SO_DOMAIN’, ‘SO_PROTOCOL’, ‘SO_PEERSEC’,
     ‘SO_PASSSEC’, ‘TCP_USER_TIMEOUT’, ‘TCP_CONGESTION’ were added.

     在 3.6.5 版的變更: On Windows, ‘TCP_FASTOPEN’, ‘TCP_KEEPCNT’ appear
     if run-time Windows supports.

     在 3.7 版的變更: 新增 ‘TCP_NOTSENT_LOWAT’。

     On Windows, ‘TCP_KEEPIDLE’, ‘TCP_KEEPINTVL’ appear if run-time
     Windows supports.

     在 3.10 版的變更: ‘IP_RECVTOS’ was added.  Added ‘TCP_KEEPALIVE’.
     On MacOS this constant can be used in the same way that
     ‘TCP_KEEPIDLE’ is used on Linux.

     在 3.11 版的變更: Added ‘TCP_CONNECTION_INFO’.  On MacOS this
     constant can be used in the same way that ‘TCP_INFO’ is used on
     Linux and BSD.

     在 3.12 版的變更: Added ‘SO_RTABLE’ and ‘SO_USER_COOKIE’.  On
     OpenBSD and FreeBSD respectively those constants can be used in the
     same way that ‘SO_MARK’ is used on Linux.  Also added missing TCP
     socket options from Linux: ‘TCP_MD5SIG’,
     ‘TCP_THIN_LINEAR_TIMEOUTS’, ‘TCP_THIN_DUPACK’, ‘TCP_REPAIR’,
     ‘TCP_REPAIR_QUEUE’, ‘TCP_QUEUE_SEQ’, ‘TCP_REPAIR_OPTIONS’,
     ‘TCP_TIMESTAMP’, ‘TCP_CC_INFO’, ‘TCP_SAVE_SYN’, ‘TCP_SAVED_SYN’,
     ‘TCP_REPAIR_WINDOW’, ‘TCP_FASTOPEN_CONNECT’, ‘TCP_ULP’,
     ‘TCP_MD5SIG_EXT’, ‘TCP_FASTOPEN_KEY’, ‘TCP_FASTOPEN_NO_COOKIE’,
     ‘TCP_ZEROCOPY_RECEIVE’, ‘TCP_INQ’, ‘TCP_TX_DELAY’.  Added
     ‘IP_PKTINFO’, ‘IP_UNBLOCK_SOURCE’, ‘IP_BLOCK_SOURCE’,
     ‘IP_ADD_SOURCE_MEMBERSHIP’, ‘IP_DROP_SOURCE_MEMBERSHIP’.

     在 3.13 版的變更: Added ‘SO_BINDTOIFINDEX’.  On Linux this constant
     can be used in the same way that ‘SO_BINDTODEVICE’ is used, but
     with the index of a network interface instead of its name.

 -- 資料: socket.AF_CAN
 -- 資料: socket.PF_CAN

 -- 資料: SOL_CAN_*

 -- 資料: CAN_*

     Many constants of these forms, documented in the Linux
     documentation, are also defined in the socket module.

     *note 適用: 1c56.：Linux 2.6.25 以上、NetBSD 8 以上。

     在 3.3 版被加入.

     在 3.11 版的變更: NetBSD support was added.

 -- 資料: socket.CAN_BCM

 -- 資料: CAN_BCM_*

     CAN_BCM, in the CAN protocol family, is the broadcast manager (BCM)
     protocol.  Broadcast manager constants, documented in the Linux
     documentation, are also defined in the socket module.

     *note 適用: 1c56.：Linux >= 2.6.25。

          備註: The ‘CAN_BCM_CAN_FD_FRAME’ flag is only available on
          Linux >= 4.8.

     在 3.4 版被加入.

 -- 資料: socket.CAN_RAW_FD_FRAMES

     Enables CAN FD support in a CAN_RAW socket.  This is disabled by
     default.  This allows your application to send both CAN and CAN FD
     frames; however, you must accept both CAN and CAN FD frames when
     reading from the socket.

     This constant is documented in the Linux documentation.

     *note 適用: 1c56.：Linux >= 3.6。

     在 3.5 版被加入.

 -- 資料: socket.CAN_RAW_JOIN_FILTERS

     Joins the applied CAN filters such that only CAN frames that match
     all given CAN filters are passed to user space.

     This constant is documented in the Linux documentation.

     *note 適用: 1c56.：Linux >= 4.1。

     在 3.9 版被加入.

 -- 資料: socket.CAN_ISOTP

     CAN_ISOTP, in the CAN protocol family, is the ISO-TP (ISO 15765-2)
     protocol.  ISO-TP constants, documented in the Linux documentation.

     *note 適用: 1c56.：Linux >= 2.6.25。

     在 3.7 版被加入.

 -- 資料: socket.CAN_J1939

     CAN_J1939, in the CAN protocol family, is the SAE J1939 protocol.
     J1939 constants, documented in the Linux documentation.

     *note 適用: 1c56.：Linux >= 5.4。

     在 3.9 版被加入.

 -- 資料: socket.AF_DIVERT
 -- 資料: socket.PF_DIVERT

     These two constants, documented in the FreeBSD divert(4) manual
     page, are also defined in the socket module.

     *note 適用: 1c56.：FreeBSD >= 14.0。

     在 3.12 版被加入.

 -- 資料: socket.AF_PACKET
 -- 資料: socket.PF_PACKET

 -- 資料: PACKET_*

     Many constants of these forms, documented in the Linux
     documentation, are also defined in the socket module.

     *note 適用: 1c56.：Linux >= 2.2。

 -- 資料: socket.ETH_P_ALL

     ‘ETH_P_ALL’ can be used in the *note socket: d47. constructor as
     'proto' for the *note AF_PACKET: 3236. family in order to capture
     every packet, regardless of protocol.

     For more information, see the ‘packet(7)(2)’ manpage.

     *note 適用: 1c56.：Linux。

     在 3.12 版被加入.

 -- 資料: socket.AF_RDS
 -- 資料: socket.PF_RDS
 -- 資料: socket.SOL_RDS

 -- 資料: RDS_*

     Many constants of these forms, documented in the Linux
     documentation, are also defined in the socket module.

     *note 適用: 1c56.：Linux >= 2.6.30。

     在 3.3 版被加入.

 -- 資料: socket.SIO_RCVALL
 -- 資料: socket.SIO_KEEPALIVE_VALS
 -- 資料: socket.SIO_LOOPBACK_FAST_PATH

 -- 資料: RCVALL_*

     Constants for Windows' WSAIoctl().  The constants are used as
     arguments to the *note ioctl(): c7a. method of socket objects.

     在 3.6 版的變更: 加入 ‘SIO_LOOPBACK_FAST_PATH’。

 -- 資料: TIPC_*

     TIPC related constants, matching the ones exported by the C socket
     API. See the TIPC documentation for more information.

 -- 資料: socket.AF_ALG
 -- 資料: socket.SOL_ALG

 -- 資料: ALG_*

     Constants for Linux Kernel cryptography.

     *note 適用: 1c56.：Linux >= 2.6.38。

     在 3.6 版被加入.

 -- 資料: socket.AF_VSOCK
 -- 資料: socket.IOCTL_VM_SOCKETS_GET_LOCAL_CID

 -- 資料: VMADDR*

 -- 資料: SO_VM*

     Constants for Linux host/guest communication.

     *note 適用: 1c56.：Linux >= 4.8。

     在 3.7 版被加入.

 -- 資料: socket.AF_LINK

     *note 適用: 1c56.：BSD、macOS。

     在 3.4 版被加入.

 -- 資料: socket.has_ipv6

     This constant contains a boolean value which indicates if IPv6 is
     supported on this platform.

 -- 資料: socket.BDADDR_ANY
 -- 資料: socket.BDADDR_LOCAL

     These are string constants containing Bluetooth addresses with
     special meanings.  For example, *note BDADDR_ANY: 324e. can be used
     to indicate any address when specifying the binding socket with
     ‘BTPROTO_RFCOMM’.

 -- 資料: socket.HCI_FILTER
 -- 資料: socket.HCI_TIME_STAMP
 -- 資料: socket.HCI_DATA_DIR

     For use with ‘BTPROTO_HCI’.  *note HCI_FILTER: 3250. is not
     available for NetBSD or DragonFlyBSD. *note HCI_TIME_STAMP: 3251.
     and *note HCI_DATA_DIR: 3252. are not available for FreeBSD,
     NetBSD, or DragonFlyBSD.

 -- 資料: socket.AF_QIPCRTR

     Constant for Qualcomm's IPC router protocol, used to communicate
     with service providing remote processors.

     *note 適用: 1c56.：Linux >= 4.7。

 -- 資料: socket.SCM_CREDS2
 -- 資料: socket.LOCAL_CREDS
 -- 資料: socket.LOCAL_CREDS_PERSISTENT

     LOCAL_CREDS and LOCAL_CREDS_PERSISTENT can be used with SOCK_DGRAM,
     SOCK_STREAM sockets, equivalent to Linux/DragonFlyBSD SO_PASSCRED,
     while LOCAL_CREDS sends the credentials at first read,
     LOCAL_CREDS_PERSISTENT sends for each read, SCM_CREDS2 must be then
     used for the latter for the message type.

     在 3.11 版被加入.

     *note 適用: 1c56.：FreeBSD。

 -- 資料: socket.SO_INCOMING_CPU

          Constant to optimize CPU locality, to be used in conjunction
          with ‘SO_REUSEPORT’.

     在 3.11 版被加入.

     *note 適用: 1c56.：Linux 3.9 以上。

 -- 資料: socket.AF_HYPERV
 -- 資料: socket.HV_PROTOCOL_RAW
 -- 資料: socket.HVSOCKET_CONNECT_TIMEOUT
 -- 資料: socket.HVSOCKET_CONNECT_TIMEOUT_MAX
 -- 資料: socket.HVSOCKET_CONNECTED_SUSPEND
 -- 資料: socket.HVSOCKET_ADDRESS_FLAG_PASSTHRU
 -- 資料: socket.HV_GUID_ZERO
 -- 資料: socket.HV_GUID_WILDCARD
 -- 資料: socket.HV_GUID_BROADCAST
 -- 資料: socket.HV_GUID_CHILDREN
 -- 資料: socket.HV_GUID_LOOPBACK
 -- 資料: socket.HV_GUID_PARENT

     Constants for Windows Hyper-V sockets for host/guest
     communications.

     *note 適用: 1c56.：Windows。

     在 3.12 版被加入.

 -- 資料: socket.ETHERTYPE_ARP
 -- 資料: socket.ETHERTYPE_IP
 -- 資料: socket.ETHERTYPE_IPV6
 -- 資料: socket.ETHERTYPE_VLAN

     IEEE 802.3 protocol number(3).  constants.

     *note 適用: 1c56.：Linux、FreeBSD、macOS。

     在 3.12 版被加入.

 -- 資料: socket.SHUT_RD
 -- 資料: socket.SHUT_WR
 -- 資料: socket.SHUT_RDWR

     These constants are used by the *note shutdown(): 3269. method of
     socket objects.

     *note 適用: 1c56.：非 WASI。

   ---------- Footnotes ----------

   (1) https://udrepper.livejournal.com/20407.html

   (2) https://manpages.debian.org/packet(7)

   (3) 
https://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers.txt


File: python.info,  Node: 函式<7>,  Prev: 常數<7>,  Up: 模組內容<4>

5.18.2.5 函式
.............

* Menu:

* 建立 sockets::
* 其他函式: 其他函式<2>.


File: python.info,  Node: 建立 sockets,  Next: 其他函式<2>,  Up: 函式<7>

5.18.2.6 建立 sockets
.....................

The following functions all create *note socket objects: 326c.

 -- 類別: socket.socket (family=AF_INET, type=SOCK_STREAM, proto=0,
          fileno=None)

     Create a new socket using the given address family, socket type and
     protocol number.  The address family should be *note AF_INET: 1722.
     (the default), *note AF_INET6: 1723, *note AF_UNIX: 1724, *note
     AF_CAN: 3234, *note AF_PACKET: 3236, or *note AF_RDS: 3246.  The
     socket type should be *note SOCK_STREAM: 1286. (the default), *note
     SOCK_DGRAM: 1285, *note SOCK_RAW: 323f. or perhaps one of the other
     ‘SOCK_’ constants.  The protocol number is usually zero and may be
     omitted or in the case where the address family is *note AF_CAN:
     3234. the protocol should be one of ‘CAN_RAW’, *note CAN_BCM: f45,
     *note CAN_ISOTP: 3235. or *note CAN_J1939: 8d6.

     If 'fileno' is specified, the values for 'family', 'type', and
     'proto' are auto-detected from the specified file descriptor.
     Auto-detection can be overruled by calling the function with
     explicit 'family', 'type', or 'proto' arguments.  This only affects
     how Python represents e.g.  the return value of *note
     socket.getpeername(): 31c0. but not the actual OS resource.  Unlike
     *note socket.fromfd(): 326d, 'fileno' will return the same socket
     and not a duplicate.  This may help close a detached socket using
     *note socket.close(): b17.

     The newly created socket is *note non-inheritable: e9d.

     引發一個附帶引數 ‘self’、‘family’、‘type’、‘protocol’ 的*note
     稽核事件: 17bd. ‘socket.__new__’。

     在 3.3 版的變更: The AF_CAN family was added.  The AF_RDS family
     was added.

     在 3.4 版的變更: 新增 CAN_BCM 協定。

     在 3.4 版的變更: The returned socket is now non-inheritable.

     在 3.7 版的變更: 新增 CAN_ISOTP 協定。

     在 3.7 版的變更: When *note SOCK_NONBLOCK: bb1. or *note
     SOCK_CLOEXEC: bb2. bit flags are applied to 'type' they are
     cleared, and *note socket.type: bb3. will not reflect them.  They
     are still passed to the underlying system ‘socket()’ call.
     Therefore,

          sock = socket.socket(
              socket.AF_INET,
              socket.SOCK_STREAM | socket.SOCK_NONBLOCK)

     will still create a non-blocking socket on OSes that support
     ‘SOCK_NONBLOCK’, but ‘sock.type’ will be set to
     ‘socket.SOCK_STREAM’.

     在 3.9 版的變更: 新增 CAN_J1939 協定。

     在 3.10 版的變更: 新增 IPPROTO_MPTCP 協定。

 -- 函式: socket.socketpair ([family[, type[, proto]]])

     Build a pair of connected socket objects using the given address
     family, socket type, and protocol number.  Address family, socket
     type, and protocol number are as for the *note socket(): d47.
     function above.  The default family is *note AF_UNIX: 1724. if
     defined on the platform; otherwise, the default is *note AF_INET:
     1722.

     The newly created sockets are *note non-inheritable: e9d.

     在 3.2 版的變更: The returned socket objects now support the whole
     socket API, rather than a subset.

     在 3.4 版的變更: The returned sockets are now non-inheritable.

     在 3.5 版的變更: 新增對 Windows 的支援。

 -- 函式: socket.create_connection (address, timeout=GLOBAL_DEFAULT,
          source_address=None, *, all_errors=False)

     Connect to a TCP service listening on the internet 'address' (a
     2-tuple ‘(host, port)’), and return the socket object.  This is a
     higher-level function than *note socket.connect(): d49.: if 'host'
     is a non-numeric hostname, it will try to resolve it for both *note
     AF_INET: 1722. and *note AF_INET6: 1723, and then try to connect to
     all possible addresses in turn until a connection succeeds.  This
     makes it easy to write clients that are compatible to both IPv4 and
     IPv6.

     Passing the optional 'timeout' parameter will set the timeout on
     the socket instance before attempting to connect.  If no 'timeout'
     is supplied, the global default timeout setting returned by *note
     getdefaulttimeout(): 326e. is used.

     If supplied, 'source_address' must be a 2-tuple ‘(host, port)’ for
     the socket to bind to as its source address before connecting.  If
     host or port are '' or 0 respectively the OS default behavior will
     be used.

     When a connection cannot be created, an exception is raised.  By
     default, it is the exception from the last address in the list.  If
     'all_errors' is ‘True’, it is an *note ExceptionGroup: 19c.
     containing the errors of all attempts.

     在 3.2 版的變更: 新增 'source_address'。

     在 3.11 版的變更: 新增 'all_errors'。

 -- 函式: socket.create_server (address, *, family=AF_INET,
          backlog=None, reuse_port=False, dualstack_ipv6=False)

     Convenience function which creates a TCP socket bound to 'address'
     (a 2-tuple ‘(host, port)’) and returns the socket object.

     'family' should be either *note AF_INET: 1722. or *note AF_INET6:
     1723.  'backlog' is the queue size passed to *note socket.listen():
     e00.; if not specified , a default reasonable value is chosen.
     'reuse_port' dictates whether to set the ‘SO_REUSEPORT’ socket
     option.

     If 'dualstack_ipv6' is true and the platform supports it the socket
     will be able to accept both IPv4 and IPv6 connections, else it will
     raise *note ValueError: 1e7.  Most POSIX platforms and Windows are
     supposed to support this functionality.  When this functionality is
     enabled the address returned by *note socket.getpeername(): 31c0.
     when an IPv4 connection occurs will be an IPv6 address represented
     as an IPv4-mapped IPv6 address.  If 'dualstack_ipv6' is false it
     will explicitly disable this functionality on platforms that enable
     it by default (e.g.  Linux).  This parameter can be used in
     conjunction with *note has_dualstack_ipv6(): 9d0.:

          import socket

          addr = ("", 8080)  # all interfaces, port 8080
          if socket.has_dualstack_ipv6():
              s = socket.create_server(addr, family=socket.AF_INET6, dualstack_ipv6=True)
          else:
              s = socket.create_server(addr)

          備註: On POSIX platforms the ‘SO_REUSEADDR’ socket option is
          set in order to immediately reuse previous sockets which were
          bound on the same 'address' and remained in TIME_WAIT state.

     在 3.8 版被加入.

 -- 函式: socket.has_dualstack_ipv6 ()

     Return ‘True’ if the platform supports creating a TCP socket which
     can handle both IPv4 and IPv6 connections.

     在 3.8 版被加入.

 -- 函式: socket.fromfd (fd, family, type, proto=0)

     Duplicate the file descriptor 'fd' (an integer as returned by a
     file object's *note fileno(): 2732. method) and build a socket
     object from the result.  Address family, socket type and protocol
     number are as for the *note socket(): d47. function above.  The
     file descriptor should refer to a socket, but this is not checked
     -- subsequent operations on the object may fail if the file
     descriptor is invalid.  This function is rarely needed, but can be
     used to get or set socket options on a socket passed to a program
     as standard input or output (such as a server started by the Unix
     inet daemon).  The socket is assumed to be in blocking mode.

     The newly created socket is *note non-inheritable: e9d.

     在 3.4 版的變更: The returned socket is now non-inheritable.

 -- 函式: socket.fromshare (data)

     Instantiate a socket from data obtained from the *note
     socket.share(): baf. method.  The socket is assumed to be in
     blocking mode.

     *note 適用: 1c56.：Windows。

     在 3.3 版被加入.

 -- 資料: socket.SocketType

     This is a Python type object that represents the socket object
     type.  It is the same as ‘type(socket(...))’.


File: python.info,  Node: 其他函式<2>,  Prev: 建立 sockets,  Up: 函式<7>

5.18.2.7 其他函式
.................

The *note socket: b8. module also offers various network-related
services:

 -- 函式: socket.close (fd)

     Close a socket file descriptor.  This is like *note os.close():
     b18, but for sockets.  On some platforms (most noticeable Windows)
     *note os.close(): b18. does not work for socket file descriptors.

     在 3.7 版被加入.

 -- 函式: socket.getaddrinfo (host, port, family=0, type=0, proto=0,
          flags=0)

     Translate the 'host'/'port' argument into a sequence of 5-tuples
     that contain all the necessary arguments for creating a socket
     connected to that service.  'host' is a domain name, a string
     representation of an IPv4/v6 address or ‘None’.  'port' is a string
     service name such as ‘'http'’, a numeric port number or ‘None’.  By
     passing ‘None’ as the value of 'host' and 'port', you can pass
     ‘NULL’ to the underlying C API.

     The 'family', 'type' and 'proto' arguments can be optionally
     specified in order to narrow the list of addresses returned.
     Passing zero as a value for each of these arguments selects the
     full range of results.  The 'flags' argument can be one or several
     of the ‘AI_*’ constants, and will influence how results are
     computed and returned.  For example, ‘AI_NUMERICHOST’ will disable
     domain name resolution and will raise an error if 'host' is a
     domain name.

     The function returns a list of 5-tuples with the following
     structure:

     ‘(family, type, proto, canonname, sockaddr)’

     In these tuples, 'family', 'type', 'proto' are all integers and are
     meant to be passed to the *note socket(): d47. function.
     'canonname' will be a string representing the canonical name of the
     'host' if ‘AI_CANONNAME’ is part of the 'flags' argument; else
     'canonname' will be empty.  'sockaddr' is a tuple describing a
     socket address, whose format depends on the returned 'family' (a
     ‘(address, port)’ 2-tuple for *note AF_INET: 1722, a ‘(address,
     port, flowinfo, scope_id)’ 4-tuple for *note AF_INET6: 1723.), and
     is meant to be passed to the *note socket.connect(): d49. method.

     引發一個附帶引數 ‘host’、‘port’、‘family’、‘type’、‘protocol’ 的
     *note 稽核事件: 17bd. ‘socket.getaddrinfo’。

     The following example fetches address information for a
     hypothetical TCP connection to ‘example.org’ on port 80 (results
     may differ on your system if IPv6 isn't enabled):

          >>> socket.getaddrinfo("example.org", 80, proto=socket.IPPROTO_TCP)
          [(socket.AF_INET6, socket.SOCK_STREAM,
           6, '', ('2606:2800:220:1:248:1893:25c8:1946', 80, 0, 0)),
           (socket.AF_INET, socket.SOCK_STREAM,
           6, '', ('93.184.216.34', 80))]

     在 3.2 版的變更: parameters can now be passed using keyword
     arguments.

     在 3.7 版的變更: for IPv6 multicast addresses, string representing
     an address will not contain ‘%scope_id’ part.

 -- 函式: socket.getfqdn ([name])

     Return a fully qualified domain name for 'name'.  If 'name' is
     omitted or empty, it is interpreted as the local host.  To find the
     fully qualified name, the hostname returned by *note
     gethostbyaddr(): 17cf. is checked, followed by aliases for the
     host, if available.  The first name which includes a period is
     selected.  In case no fully qualified domain name is available and
     'name' was provided, it is returned unchanged.  If 'name' was empty
     or equal to ‘'0.0.0.0'’, the hostname from *note gethostname():
     2a11. is returned.

 -- 函式: socket.gethostbyname (hostname)

     Translate a host name to IPv4 address format.  The IPv4 address is
     returned as a string, such as ‘'100.50.200.5'’.  If the host name
     is an IPv4 address itself it is returned unchanged.  See *note
     gethostbyname_ex(): 17d0. for a more complete interface.  *note
     gethostbyname(): 3271. does not support IPv6 name resolution, and
     *note getaddrinfo(): 1654. should be used instead for IPv4/v6 dual
     stack support.

     引發一個附帶引數 ‘hostname’ 的*note 稽核事件: 17bd.
     ‘socket.gethostbyname’。

     *note 適用: 1c56.：非 WASI。

 -- 函式: socket.gethostbyname_ex (hostname)

     Translate a host name to IPv4 address format, extended interface.
     Return a 3-tuple ‘(hostname, aliaslist, ipaddrlist)’ where
     'hostname' is the host's primary host name, 'aliaslist' is a
     (possibly empty) list of alternative host names for the same
     address, and 'ipaddrlist' is a list of IPv4 addresses for the same
     interface on the same host (often but not always a single address).
     *note gethostbyname_ex(): 17d0. does not support IPv6 name
     resolution, and *note getaddrinfo(): 1654. should be used instead
     for IPv4/v6 dual stack support.

     引發一個附帶引數 ‘hostname’ 的*note 稽核事件: 17bd.
     ‘socket.gethostbyname’。

     *note 適用: 1c56.：非 WASI。

 -- 函式: socket.gethostname ()

     Return a string containing the hostname of the machine where the
     Python interpreter is currently executing.

     引發一個不附帶引數的*note 稽核事件: 17bd. ‘socket.gethostname’。

     Note: *note gethostname(): 2a11. doesn't always return the fully
     qualified domain name; use *note getfqdn(): 167f. for that.

     *note 適用: 1c56.：非 WASI。

 -- 函式: socket.gethostbyaddr (ip_address)

     Return a 3-tuple ‘(hostname, aliaslist, ipaddrlist)’ where
     'hostname' is the primary host name responding to the given
     'ip_address', 'aliaslist' is a (possibly empty) list of alternative
     host names for the same address, and 'ipaddrlist' is a list of
     IPv4/v6 addresses for the same interface on the same host (most
     likely containing only a single address).  To find the fully
     qualified domain name, use the function *note getfqdn(): 167f.
     *note gethostbyaddr(): 17cf. supports both IPv4 and IPv6.

     引發一個附帶引數 ‘ip_address’ 的*note 稽核事件: 17bd.
     ‘socket.gethostbyaddr’。

     *note 適用: 1c56.：非 WASI。

 -- 函式: socket.getnameinfo (sockaddr, flags)

     Translate a socket address 'sockaddr' into a 2-tuple ‘(host,
     port)’.  Depending on the settings of 'flags', the result can
     contain a fully qualified domain name or numeric address
     representation in 'host'.  Similarly, 'port' can contain a string
     port name or a numeric port number.

     For IPv6 addresses, ‘%scope_id’ is appended to the host part if
     'sockaddr' contains meaningful 'scope_id'.  Usually this happens
     for multicast addresses.

     For more information about 'flags' you can consult
     ‘getnameinfo(3)(1)’.

     引發一個附帶引數 ‘sockaddr’ 的*note 稽核事件: 17bd.
     ‘socket.getnameinfo’。

     *note 適用: 1c56.：非 WASI。

 -- 函式: socket.getprotobyname (protocolname)

     Translate an internet protocol name (for example, ‘'icmp'’) to a
     constant suitable for passing as the (optional) third argument to
     the *note socket(): d47. function.  This is usually only needed for
     sockets opened in "raw" mode (*note SOCK_RAW: 323f.); for the
     normal socket modes, the correct protocol is chosen automatically
     if the protocol is omitted or zero.

     *note 適用: 1c56.：非 WASI。

 -- 函式: socket.getservbyname (servicename[, protocolname])

     Translate an internet service name and protocol name to a port
     number for that service.  The optional protocol name, if given,
     should be ‘'tcp'’ or ‘'udp'’, otherwise any protocol will match.

     引發一個附帶引數 ‘sockaddr’、‘protocolname’ 的*note 稽核事件: 17bd.
     ‘socket.getservbyname’。

     *note 適用: 1c56.：非 WASI。

 -- 函式: socket.getservbyport (port[, protocolname])

     Translate an internet port number and protocol name to a service
     name for that service.  The optional protocol name, if given,
     should be ‘'tcp'’ or ‘'udp'’, otherwise any protocol will match.

     引發一個附帶引數 ‘port’、‘protocolname’ 的*note 稽核事件: 17bd.
     ‘socket.getservbyport’。

     *note 適用: 1c56.：非 WASI。

 -- 函式: socket.ntohl (x)

     Convert 32-bit positive integers from network to host byte order.
     On machines where the host byte order is the same as network byte
     order, this is a no-op; otherwise, it performs a 4-byte swap
     operation.

 -- 函式: socket.ntohs (x)

     Convert 16-bit positive integers from network to host byte order.
     On machines where the host byte order is the same as network byte
     order, this is a no-op; otherwise, it performs a 2-byte swap
     operation.

     在 3.10 版的變更: Raises *note OverflowError: 825. if 'x' does not
     fit in a 16-bit unsigned integer.

 -- 函式: socket.htonl (x)

     Convert 32-bit positive integers from host to network byte order.
     On machines where the host byte order is the same as network byte
     order, this is a no-op; otherwise, it performs a 4-byte swap
     operation.

 -- 函式: socket.htons (x)

     Convert 16-bit positive integers from host to network byte order.
     On machines where the host byte order is the same as network byte
     order, this is a no-op; otherwise, it performs a 2-byte swap
     operation.

     在 3.10 版的變更: Raises *note OverflowError: 825. if 'x' does not
     fit in a 16-bit unsigned integer.

 -- 函式: socket.inet_aton (ip_string)

     Convert an IPv4 address from dotted-quad string format (for
     example, '123.45.67.89') to 32-bit packed binary format, as a bytes
     object four characters in length.  This is useful when conversing
     with a program that uses the standard C library and needs objects
     of type ‘in_addr’, which is the C type for the 32-bit packed binary
     this function returns.

     *note inet_aton(): 905. also accepts strings with less than three
     dots; see the Unix manual page ‘inet(3)(2)’ for details.

     If the IPv4 address string passed to this function is invalid,
     *note OSError: 350. will be raised.  Note that exactly what is
     valid depends on the underlying C implementation of ‘inet_aton()’.

     *note inet_aton(): 905. does not support IPv6, and *note
     inet_pton(): 906. should be used instead for IPv4/v6 dual stack
     support.

 -- 函式: socket.inet_ntoa (packed_ip)

     Convert a 32-bit packed IPv4 address (a *note bytes-like object:
     cd4. four bytes in length) to its standard dotted-quad string
     representation (for example, '123.45.67.89').  This is useful when
     conversing with a program that uses the standard C library and
     needs objects of type ‘in_addr’, which is the C type for the 32-bit
     packed binary data this function takes as an argument.

     If the byte sequence passed to this function is not exactly 4 bytes
     in length, *note OSError: 350. will be raised.  *note inet_ntoa():
     3277. does not support IPv6, and *note inet_ntop(): f47. should be
     used instead for IPv4/v6 dual stack support.

     在 3.5 版的變更: Writable *note bytes-like object: cd4. is now
     accepted.

 -- 函式: socket.inet_pton (address_family, ip_string)

     Convert an IP address from its family-specific string format to a
     packed, binary format.  *note inet_pton(): 906. is useful when a
     library or network protocol calls for an object of type ‘in_addr’
     (similar to *note inet_aton(): 905.) or ‘in6_addr’.

     Supported values for 'address_family' are currently *note AF_INET:
     1722. and *note AF_INET6: 1723.  If the IP address string
     'ip_string' is invalid, *note OSError: 350. will be raised.  Note
     that exactly what is valid depends on both the value of
     'address_family' and the underlying implementation of
     ‘inet_pton()’.

     *note 適用: 1c56.：Unix、Windows。

     在 3.4 版的變更: Windows support added

 -- 函式: socket.inet_ntop (address_family, packed_ip)

     Convert a packed IP address (a *note bytes-like object: cd4. of
     some number of bytes) to its standard, family-specific string
     representation (for example, ‘'7.10.0.5'’ or ‘'5aef:2b::8'’).
     *note inet_ntop(): f47. is useful when a library or network
     protocol returns an object of type ‘in_addr’ (similar to *note
     inet_ntoa(): 3277.) or ‘in6_addr’.

     Supported values for 'address_family' are currently *note AF_INET:
     1722. and *note AF_INET6: 1723.  If the bytes object 'packed_ip' is
     not the correct length for the specified address family, *note
     ValueError: 1e7. will be raised.  *note OSError: 350. is raised for
     errors from the call to *note inet_ntop(): f47.

     *note 適用: 1c56.：Unix、Windows。

     在 3.4 版的變更: Windows support added

     在 3.5 版的變更: Writable *note bytes-like object: cd4. is now
     accepted.

 -- 函式: socket.CMSG_LEN (length)

     Return the total length, without trailing padding, of an ancillary
     data item with associated data of the given 'length'.  This value
     can often be used as the buffer size for *note recvmsg(): d4c. to
     receive a single item of ancillary data, but RFC 3542(3) requires
     portable applications to use *note CMSG_SPACE(): 193c. and thus
     include space for padding, even when the item will be the last in
     the buffer.  Raises *note OverflowError: 825. if 'length' is
     outside the permissible range of values.

     *note 適用: 1c56.：Unix、非 WASI。

     Most Unix platforms.

     在 3.3 版被加入.

 -- 函式: socket.CMSG_SPACE (length)

     Return the buffer size needed for *note recvmsg(): d4c. to receive
     an ancillary data item with associated data of the given 'length',
     along with any trailing padding.  The buffer space needed to
     receive multiple items is the sum of the *note CMSG_SPACE(): 193c.
     values for their associated data lengths.  Raises *note
     OverflowError: 825. if 'length' is outside the permissible range of
     values.

     Note that some systems might support ancillary data without
     providing this function.  Also note that setting the buffer size
     using the results of this function may not precisely limit the
     amount of ancillary data that can be received, since additional
     data may be able to fit into the padding area.

     *note 適用: 1c56.：Unix、非 WASI。

     most Unix platforms.

     在 3.3 版被加入.

 -- 函式: socket.getdefaulttimeout ()

     Return the default timeout in seconds (float) for new socket
     objects.  A value of ‘None’ indicates that new socket objects have
     no timeout.  When the socket module is first imported, the default
     is ‘None’.

 -- 函式: socket.setdefaulttimeout (timeout)

     Set the default timeout in seconds (float) for new socket objects.
     When the socket module is first imported, the default is ‘None’.
     See *note settimeout(): 3239. for possible values and their
     respective meanings.

 -- 函式: socket.sethostname (name)

     Set the machine's hostname to 'name'.  This will raise an *note
     OSError: 350. if you don't have enough rights.

     引發一個附帶引數 ‘name’ 的*note 稽核事件: 17bd.
     ‘socket.sethostname’。

     *note 適用: 1c56.：Unix。

     在 3.3 版被加入.

 -- 函式: socket.if_nameindex ()

     Return a list of network interface information (index int, name
     string) tuples.  *note OSError: 350. if the system call fails.

     *note Availability: 1c56.: Unix, Windows, not WASI.

     在 3.3 版被加入.

     在 3.8 版的變更: 增加對 Windows 的支援。

          備註: On Windows network interfaces have different names in
          different contexts (all names are examples):

             * UUID: ‘{FB605B73-AAC2-49A6-9A2F-25416AEA0573}’

             * name: ‘ethernet_32770’

             * friendly name: ‘vEthernet (nat)’

             * description: ‘Hyper-V Virtual Ethernet Adapter’

          This function returns names of the second form from the list,
          ‘ethernet_32770’ in this example case.

 -- 函式: socket.if_nametoindex (if_name)

     Return a network interface index number corresponding to an
     interface name.  *note OSError: 350. if no interface with the given
     name exists.

     *note Availability: 1c56.: Unix, Windows, not WASI.

     在 3.3 版被加入.

     在 3.8 版的變更: 增加對 Windows 的支援。

     也參考
     ......

     "Interface name" is a name as documented in *note if_nameindex():
     9d1.

 -- 函式: socket.if_indextoname (if_index)

     Return a network interface name corresponding to an interface index
     number.  *note OSError: 350. if no interface with the given index
     exists.

     *note Availability: 1c56.: Unix, Windows, not WASI.

     在 3.3 版被加入.

     在 3.8 版的變更: 增加對 Windows 的支援。

     也參考
     ......

     "Interface name" is a name as documented in *note if_nameindex():
     9d1.

 -- 函式: socket.send_fds (sock, buffers, fds[, flags[, address]])

     Send the list of file descriptors 'fds' over an *note AF_UNIX:
     1724. socket 'sock'.  The 'fds' parameter is a sequence of file
     descriptors.  Consult *note sendmsg(): 41d. for the documentation
     of these parameters.

     *note Availability: 1c56.: Unix, Windows, not WASI.

     Unix platforms supporting *note sendmsg(): 41d. and ‘SCM_RIGHTS’
     mechanism.

     在 3.9 版被加入.

 -- 函式: socket.recv_fds (sock, bufsize, maxfds[, flags])

     Receive up to 'maxfds' file descriptors from an *note AF_UNIX:
     1724. socket 'sock'.  Return ‘(msg, list(fds), flags, addr)’.
     Consult *note recvmsg(): d4c. for the documentation of these
     parameters.

     *note Availability: 1c56.: Unix, Windows, not WASI.

     Unix platforms supporting *note sendmsg(): 41d. and ‘SCM_RIGHTS’
     mechanism.

     在 3.9 版被加入.

          備註: Any truncated integers at the end of the list of file
          descriptors.

   ---------- Footnotes ----------

   (1) https://manpages.debian.org/getnameinfo(3)

   (2) https://manpages.debian.org/inet(3)

   (3) https://datatracker.ietf.org/doc/html/rfc3542.html


File: python.info,  Node: Socket 物件,  Next: Notes on socket timeouts,  Prev: 模組內容<4>,  Up: socket --- 低階網路介面

5.18.2.8 Socket 物件
....................

Socket objects have the following methods.  Except for *note makefile():
1137, these correspond to Unix system calls applicable to sockets.

在 3.2 版的變更: Support for the *note context manager: 576. protocol
was added.  Exiting the context manager is equivalent to calling *note
close(): b17.

 -- 方法: socket.accept ()

     Accept a connection.  The socket must be bound to an address and
     listening for connections.  The return value is a pair ‘(conn,
     address)’ where 'conn' is a 'new' socket object usable to send and
     receive data on the connection, and 'address' is the address bound
     to the socket on the other end of the connection.

     The newly created socket is *note non-inheritable: e9d.

     在 3.4 版的變更: The socket is now non-inheritable.

     在 3.5 版的變更: If the system call is interrupted and the signal
     handler does not raise an exception, the method now retries the
     system call instead of raising an *note InterruptedError: d2e.
     exception (see PEP 475(1) for the rationale).

 -- 方法: socket.bind (address)

     Bind the socket to 'address'.  The socket must not already be
     bound.  (The format of 'address' depends on the address family --
     see above.)

     引發一個附帶引數 ‘self’、‘address’ 的*note 稽核事件: 17bd.
     ‘socket.bind’。

     *note 適用: 1c56.：非 WASI。

 -- 方法: socket.close ()

     Mark the socket closed.  The underlying system resource (e.g.  a
     file descriptor) is also closed when all file objects from *note
     makefile(): 1137. are closed.  Once that happens, all future
     operations on the socket object will fail.  The remote end will
     receive no more data (after queued data is flushed).

     Sockets are automatically closed when they are garbage-collected,
     but it is recommended to *note close(): b17. them explicitly, or to
     use a *note with: 577. statement around them.

     在 3.6 版的變更: *note OSError: 350. is now raised if an error
     occurs when the underlying ‘close()’ call is made.

          備註: *note close(): b17. releases the resource associated
          with a connection but does not necessarily close the
          connection immediately.  If you want to close the connection
          in a timely fashion, call *note shutdown(): 3269. before *note
          close(): b17.

 -- 方法: socket.connect (address)

     Connect to a remote socket at 'address'.  (The format of 'address'
     depends on the address family -- see above.)

     If the connection is interrupted by a signal, the method waits
     until the connection completes, or raise a *note TimeoutError: 7d9.
     on timeout, if the signal handler doesn't raise an exception and
     the socket is blocking or has a timeout.  For non-blocking sockets,
     the method raises an *note InterruptedError: d2e. exception if the
     connection is interrupted by a signal (or the exception raised by
     the signal handler).

     引發一個附帶引數 ‘self’、‘address’ 的*note 稽核事件: 17bd.
     ‘socket.connect’。

     在 3.5 版的變更: The method now waits until the connection
     completes instead of raising an *note InterruptedError: d2e.
     exception if the connection is interrupted by a signal, the signal
     handler doesn't raise an exception and the socket is blocking or
     has a timeout (see the PEP 475(2) for the rationale).

     *note 適用: 1c56.：非 WASI。

 -- 方法: socket.connect_ex (address)

     Like ‘connect(address)’, but return an error indicator instead of
     raising an exception for errors returned by the C-level ‘connect()’
     call (other problems, such as "host not found," can still raise
     exceptions).  The error indicator is ‘0’ if the operation
     succeeded, otherwise the value of the ‘errno’ variable.  This is
     useful to support, for example, asynchronous connects.

     引發一個附帶引數 ‘self’、‘address’ 的*note 稽核事件: 17bd.
     ‘socket.connect’。

     *note 適用: 1c56.：非 WASI。

 -- 方法: socket.detach ()

     Put the socket object into closed state without actually closing
     the underlying file descriptor.  The file descriptor is returned,
     and can be reused for other purposes.

     在 3.2 版被加入.

 -- 方法: socket.dup ()

     Duplicate the socket.

     The newly created socket is *note non-inheritable: e9d.

     在 3.4 版的變更: The socket is now non-inheritable.

     *note 適用: 1c56.：非 WASI。

 -- 方法: socket.fileno ()

     Return the socket's file descriptor (a small integer), or -1 on
     failure.  This is useful with *note select.select(): d46.

     Under Windows the small integer returned by this method cannot be
     used where a file descriptor can be used (such as *note
     os.fdopen(): 1e08.).  Unix does not have this limitation.

 -- 方法: socket.get_inheritable ()

     Get the *note inheritable flag: e9d. of the socket's file
     descriptor or socket's handle: ‘True’ if the socket can be
     inherited in child processes, ‘False’ if it cannot.

     在 3.4 版被加入.

 -- 方法: socket.getpeername ()

     Return the remote address to which the socket is connected.  This
     is useful to find out the port number of a remote IPv4/v6 socket,
     for instance.  (The format of the address returned depends on the
     address family -- see above.)  On some systems this function is not
     supported.

 -- 方法: socket.getsockname ()

     Return the socket's own address.  This is useful to find out the
     port number of an IPv4/v6 socket, for instance.  (The format of the
     address returned depends on the address family -- see above.)

 -- 方法: socket.getsockopt (level, optname[, buflen])

     Return the value of the given socket option (see the Unix man page
     ‘getsockopt(2)(3)’).  The needed symbolic constants (*note SO_*
     etc.: 317f.) are defined in this module.  If 'buflen' is absent, an
     integer option is assumed and its integer value is returned by the
     function.  If 'buflen' is present, it specifies the maximum length
     of the buffer used to receive the option in, and this buffer is
     returned as a bytes object.  It is up to the caller to decode the
     contents of the buffer (see the optional built-in module *note
     struct: c0. for a way to decode C structures encoded as byte
     strings).

     *note 適用: 1c56.：非 WASI。

 -- 方法: socket.getblocking ()

     Return ‘True’ if socket is in blocking mode, ‘False’ if in
     non-blocking.

     這等同於檢查 ‘socket.gettimeout() != 0’。

     在 3.7 版被加入.

 -- 方法: socket.gettimeout ()

     Return the timeout in seconds (float) associated with socket
     operations, or ‘None’ if no timeout is set.  This reflects the last
     call to *note setblocking(): 2a28. or *note settimeout(): 3239.

 -- 方法: socket.ioctl (control, option)


     平台: Windows

     The *note ioctl(): c7a. method is a limited interface to the
     WSAIoctl system interface.  Please refer to the Win32
     documentation(4) for more information.

     On other platforms, the generic *note fcntl.fcntl(): 327c. and
     *note fcntl.ioctl(): 13e5. functions may be used; they accept a
     socket object as their first argument.

     Currently only the following control codes are supported:
     ‘SIO_RCVALL’, ‘SIO_KEEPALIVE_VALS’, and ‘SIO_LOOPBACK_FAST_PATH’.

     在 3.6 版的變更: 加入 ‘SIO_LOOPBACK_FAST_PATH’。

 -- 方法: socket.listen ([backlog])

     Enable a server to accept connections.  If 'backlog' is specified,
     it must be at least 0 (if it is lower, it is set to 0); it
     specifies the number of unaccepted connections that the system will
     allow before refusing new connections.  If not specified, a default
     reasonable value is chosen.

     *note 適用: 1c56.：非 WASI。

     在 3.5 版的變更: The 'backlog' parameter is now optional.

 -- 方法: socket.makefile (mode='r', buffering=None, *, encoding=None,
          errors=None, newline=None)

     Return a *note file object: 115b. associated with the socket.  The
     exact returned type depends on the arguments given to *note
     makefile(): 1137.  These arguments are interpreted the same way as
     by the built-in *note open(): 4c0. function, except the only
     supported 'mode' values are ‘'r'’ (default), ‘'w'’, ‘'b'’, or a
     combination of those.

     The socket must be in blocking mode; it can have a timeout, but the
     file object's internal buffer may end up in an inconsistent state
     if a timeout occurs.

     Closing the file object returned by *note makefile(): 1137. won't
     close the original socket unless all other file objects have been
     closed and *note socket.close(): b17. has been called on the socket
     object.

          備註: On Windows, the file-like object created by *note
          makefile(): 1137. cannot be used where a file object with a
          file descriptor is expected, such as the stream arguments of
          *note subprocess.Popen(): 17d.

 -- 方法: socket.recv (bufsize[, flags])

     Receive data from the socket.  The return value is a bytes object
     representing the data received.  The maximum amount of data to be
     received at once is specified by 'bufsize'.  A returned empty bytes
     object indicates that the client has disconnected.  See the Unix
     manual page ‘recv(2)(5)’ for the meaning of the optional argument
     'flags'; it defaults to zero.

          備註: For best match with hardware and network realities, the
          value of 'bufsize' should be a relatively small power of 2,
          for example, 4096.

     在 3.5 版的變更: If the system call is interrupted and the signal
     handler does not raise an exception, the method now retries the
     system call instead of raising an *note InterruptedError: d2e.
     exception (see PEP 475(6) for the rationale).

 -- 方法: socket.recvfrom (bufsize[, flags])

     Receive data from the socket.  The return value is a pair ‘(bytes,
     address)’ where 'bytes' is a bytes object representing the data
     received and 'address' is the address of the socket sending the
     data.  See the Unix manual page ‘recv(2)(7)’ for the meaning of the
     optional argument 'flags'; it defaults to zero.  (The format of
     'address' depends on the address family -- see above.)

     在 3.5 版的變更: If the system call is interrupted and the signal
     handler does not raise an exception, the method now retries the
     system call instead of raising an *note InterruptedError: d2e.
     exception (see PEP 475(8) for the rationale).

     在 3.7 版的變更: For multicast IPv6 address, first item of
     'address' does not contain ‘%scope_id’ part anymore.  In order to
     get full IPv6 address use *note getnameinfo(): 15be.

 -- 方法: socket.recvmsg (bufsize[, ancbufsize[, flags]])

     Receive normal data (up to 'bufsize' bytes) and ancillary data from
     the socket.  The 'ancbufsize' argument sets the size in bytes of
     the internal buffer used to receive the ancillary data; it defaults
     to 0, meaning that no ancillary data will be received.  Appropriate
     buffer sizes for ancillary data can be calculated using *note
     CMSG_SPACE(): 193c. or *note CMSG_LEN(): 193d, and items which do
     not fit into the buffer might be truncated or discarded.  The
     'flags' argument defaults to 0 and has the same meaning as for
     *note recv(): d4a.

     The return value is a 4-tuple: ‘(data, ancdata, msg_flags,
     address)’.  The 'data' item is a *note bytes: 1a5. object holding
     the non-ancillary data received.  The 'ancdata' item is a list of
     zero or more tuples ‘(cmsg_level, cmsg_type, cmsg_data)’
     representing the ancillary data (control messages) received:
     'cmsg_level' and 'cmsg_type' are integers specifying the protocol
     level and protocol-specific type respectively, and 'cmsg_data' is a
     *note bytes: 1a5. object holding the associated data.  The
     'msg_flags' item is the bitwise OR of various flags indicating
     conditions on the received message; see your system documentation
     for details.  If the receiving socket is unconnected, 'address' is
     the address of the sending socket, if available; otherwise, its
     value is unspecified.

     On some systems, *note sendmsg(): 41d. and *note recvmsg(): d4c.
     can be used to pass file descriptors between processes over an
     *note AF_UNIX: 1724. socket.  When this facility is used (it is
     often restricted to *note SOCK_STREAM: 1286. sockets), *note
     recvmsg(): d4c. will return, in its ancillary data, items of the
     form ‘(socket.SOL_SOCKET, socket.SCM_RIGHTS, fds)’, where 'fds' is
     a *note bytes: 1a5. object representing the new file descriptors as
     a binary array of the native C int type.  If *note recvmsg(): d4c.
     raises an exception after the system call returns, it will first
     attempt to close any file descriptors received via this mechanism.

     Some systems do not indicate the truncated length of ancillary data
     items which have been only partially received.  If an item appears
     to extend beyond the end of the buffer, *note recvmsg(): d4c. will
     issue a *note RuntimeWarning: 1a3, and will return the part of it
     which is inside the buffer provided it has not been truncated
     before the start of its associated data.

     On systems which support the ‘SCM_RIGHTS’ mechanism, the following
     function will receive up to 'maxfds' file descriptors, returning
     the message data and a list containing the descriptors (while
     ignoring unexpected conditions such as unrelated control messages
     being received).  See also *note sendmsg(): 41d.

          import socket, array

          def recv_fds(sock, msglen, maxfds):
              fds = array.array("i")   # Array of ints
              msg, ancdata, flags, addr = sock.recvmsg(msglen, socket.CMSG_LEN(maxfds * fds.itemsize))
              for cmsg_level, cmsg_type, cmsg_data in ancdata:
                  if cmsg_level == socket.SOL_SOCKET and cmsg_type == socket.SCM_RIGHTS:
                      # Append data, ignoring any truncated integers at the end.
                      fds.frombytes(cmsg_data[:len(cmsg_data) - (len(cmsg_data) % fds.itemsize)])
              return msg, list(fds)

     *note 適用: 1c56.：Unix。

     Most Unix platforms.

     在 3.3 版被加入.

     在 3.5 版的變更: If the system call is interrupted and the signal
     handler does not raise an exception, the method now retries the
     system call instead of raising an *note InterruptedError: d2e.
     exception (see PEP 475(9) for the rationale).

 -- 方法: socket.recvmsg_into (buffers[, ancbufsize[, flags]])

     Receive normal data and ancillary data from the socket, behaving as
     *note recvmsg(): d4c. would, but scatter the non-ancillary data
     into a series of buffers instead of returning a new bytes object.
     The 'buffers' argument must be an iterable of objects that export
     writable buffers (e.g.  *note bytearray: 4e3. objects); these will
     be filled with successive chunks of the non-ancillary data until it
     has all been written or there are no more buffers.  The operating
     system may set a limit (*note sysconf(): 2a4f. value ‘SC_IOV_MAX’)
     on the number of buffers that can be used.  The 'ancbufsize' and
     'flags' arguments have the same meaning as for *note recvmsg():
     d4c.

     The return value is a 4-tuple: ‘(nbytes, ancdata, msg_flags,
     address)’, where 'nbytes' is the total number of bytes of
     non-ancillary data written into the buffers, and 'ancdata',
     'msg_flags' and 'address' are the same as for *note recvmsg(): d4c.

     範例：

          >>> import socket
          >>> s1, s2 = socket.socketpair()
          >>> b1 = bytearray(b'----')
          >>> b2 = bytearray(b'0123456789')
          >>> b3 = bytearray(b'--------------')
          >>> s1.send(b'Mary had a little lamb')
          22
          >>> s2.recvmsg_into([b1, memoryview(b2)[2:9], b3])
          (22, [], 0, None)
          >>> [b1, b2, b3]
          [bytearray(b'Mary'), bytearray(b'01 had a 9'), bytearray(b'little lamb---')]

     *note 適用: 1c56.：Unix。

     Most Unix platforms.

     在 3.3 版被加入.

 -- 方法: socket.recvfrom_into (buffer[, nbytes[, flags]])

     Receive data from the socket, writing it into 'buffer' instead of
     creating a new bytestring.  The return value is a pair ‘(nbytes,
     address)’ where 'nbytes' is the number of bytes received and
     'address' is the address of the socket sending the data.  See the
     Unix manual page ‘recv(2)(10)’ for the meaning of the optional
     argument 'flags'; it defaults to zero.  (The format of 'address'
     depends on the address family -- see above.)

 -- 方法: socket.recv_into (buffer[, nbytes[, flags]])

     Receive up to 'nbytes' bytes from the socket, storing the data into
     a buffer rather than creating a new bytestring.  If 'nbytes' is not
     specified (or 0), receive up to the size available in the given
     buffer.  Returns the number of bytes received.  See the Unix manual
     page ‘recv(2)(11)’ for the meaning of the optional argument
     'flags'; it defaults to zero.

 -- 方法: socket.send (bytes[, flags])

     Send data to the socket.  The socket must be connected to a remote
     socket.  The optional 'flags' argument has the same meaning as for
     *note recv(): d4a. above.  Returns the number of bytes sent.
     Applications are responsible for checking that all data has been
     sent; if only some of the data was transmitted, the application
     needs to attempt delivery of the remaining data.  For further
     information on this topic, consult the *note Socket 程式設計指南:
     327d.

     在 3.5 版的變更: If the system call is interrupted and the signal
     handler does not raise an exception, the method now retries the
     system call instead of raising an *note InterruptedError: d2e.
     exception (see PEP 475(12) for the rationale).

 -- 方法: socket.sendall (bytes[, flags])

     Send data to the socket.  The socket must be connected to a remote
     socket.  The optional 'flags' argument has the same meaning as for
     *note recv(): d4a. above.  Unlike *note send(): d4d, this method
     continues to send data from 'bytes' until either all data has been
     sent or an error occurs.  ‘None’ is returned on success.  On error,
     an exception is raised, and there is no way to determine how much
     data, if any, was successfully sent.

     在 3.5 版的變更: The socket timeout is no longer reset each time
     data is sent successfully.  The socket timeout is now the maximum
     total duration to send all data.

     在 3.5 版的變更: If the system call is interrupted and the signal
     handler does not raise an exception, the method now retries the
     system call instead of raising an *note InterruptedError: d2e.
     exception (see PEP 475(13) for the rationale).

 -- 方法: socket.sendto (bytes, address)

 -- 方法: socket.sendto (bytes, flags, address)

     Send data to the socket.  The socket should not be connected to a
     remote socket, since the destination socket is specified by
     'address'.  The optional 'flags' argument has the same meaning as
     for *note recv(): d4a. above.  Return the number of bytes sent.
     (The format of 'address' depends on the address family -- see
     above.)

     引發一個附帶引數 ‘self’、‘address’ 的*note 稽核事件: 17bd.
     ‘socket.sendto’。

     在 3.5 版的變更: If the system call is interrupted and the signal
     handler does not raise an exception, the method now retries the
     system call instead of raising an *note InterruptedError: d2e.
     exception (see PEP 475(14) for the rationale).

 -- 方法: socket.sendmsg (buffers[, ancdata[, flags[, address]]])

     Send normal and ancillary data to the socket, gathering the
     non-ancillary data from a series of buffers and concatenating it
     into a single message.  The 'buffers' argument specifies the
     non-ancillary data as an iterable of *note bytes-like objects: cd4.
     (e.g.  *note bytes: 1a5. objects); the operating system may set a
     limit (*note sysconf(): 2a4f. value ‘SC_IOV_MAX’) on the number of
     buffers that can be used.  The 'ancdata' argument specifies the
     ancillary data (control messages) as an iterable of zero or more
     tuples ‘(cmsg_level, cmsg_type, cmsg_data)’, where 'cmsg_level' and
     'cmsg_type' are integers specifying the protocol level and
     protocol-specific type respectively, and 'cmsg_data' is a
     bytes-like object holding the associated data.  Note that some
     systems (in particular, systems without *note CMSG_SPACE(): 193c.)
     might support sending only one control message per call.  The
     'flags' argument defaults to 0 and has the same meaning as for
     *note send(): d4d.  If 'address' is supplied and not ‘None’, it
     sets a destination address for the message.  The return value is
     the number of bytes of non-ancillary data sent.

     The following function sends the list of file descriptors 'fds'
     over an *note AF_UNIX: 1724. socket, on systems which support the
     ‘SCM_RIGHTS’ mechanism.  See also *note recvmsg(): d4c.

          import socket, array

          def send_fds(sock, msg, fds):
              return sock.sendmsg([msg], [(socket.SOL_SOCKET, socket.SCM_RIGHTS, array.array("i", fds))])

     *note 適用: 1c56.：Unix、非 WASI。

     Most Unix platforms.

     引發一個附帶引數 ‘self’、‘address’ 的*note 稽核事件: 17bd.
     ‘socket.sendmsg’。

     在 3.3 版被加入.

     在 3.5 版的變更: If the system call is interrupted and the signal
     handler does not raise an exception, the method now retries the
     system call instead of raising an *note InterruptedError: d2e.
     exception (see PEP 475(15) for the rationale).

 -- 方法: socket.sendmsg_afalg ([msg], *, op[, iv[, assoclen[, flags]]])

     Specialized version of *note sendmsg(): 41d. for *note AF_ALG: c7e.
     socket.  Set mode, IV, AEAD associated data length and flags for
     *note AF_ALG: c7e. socket.

     *note 適用: 1c56.：Linux >= 2.6.38。

     在 3.6 版被加入.

 -- 方法: socket.sendfile (file, offset=0, count=None)

     Send a file until EOF is reached by using high-performance *note
     os.sendfile: ab2. and return the total number of bytes which were
     sent.  'file' must be a regular file object opened in binary mode.
     If *note os.sendfile: ab2. is not available (e.g.  Windows) or
     'file' is not a regular file *note send(): d4d. will be used
     instead.  'offset' tells from where to start reading the file.  If
     specified, 'count' is the total number of bytes to transmit as
     opposed to sending the file until EOF is reached.  File position is
     updated on return or also in case of error in which case *note
     file.tell(): 2894. can be used to figure out the number of bytes
     which were sent.  The socket must be of *note SOCK_STREAM: 1286.
     type.  Non-blocking sockets are not supported.

     在 3.5 版被加入.

 -- 方法: socket.set_inheritable (inheritable)

     Set the *note inheritable flag: e9d. of the socket's file
     descriptor or socket's handle.

     在 3.4 版被加入.

 -- 方法: socket.setblocking (flag)

     Set blocking or non-blocking mode of the socket: if 'flag' is
     false, the socket is set to non-blocking, else to blocking mode.

     This method is a shorthand for certain *note settimeout(): 3239.
     calls:

        * ‘sock.setblocking(True)’ 等價於 ‘sock.settimeout(None)’

        * ‘sock.setblocking(False)’ 等價於 ‘sock.settimeout(0.0)’

     在 3.7 版的變更: The method no longer applies *note SOCK_NONBLOCK:
     bb1. flag on *note socket.type: bb3.

 -- 方法: socket.settimeout (value)

     Set a timeout on blocking socket operations.  The 'value' argument
     can be a nonnegative floating-point number expressing seconds, or
     ‘None’.  If a non-zero value is given, subsequent socket operations
     will raise a *note timeout: 7d8. exception if the timeout period
     'value' has elapsed before the operation has completed.  If zero is
     given, the socket is put in non-blocking mode.  If ‘None’ is given,
     the socket is put in blocking mode.

     For further information, please consult the *note notes on socket
     timeouts: 327e.

     在 3.7 版的變更: The method no longer toggles *note SOCK_NONBLOCK:
     bb1. flag on *note socket.type: bb3.

 -- 方法: socket.setsockopt (level, optname, value: int)

 -- 方法: socket.setsockopt (level, optname, value: buffer)

 -- 方法: socket.setsockopt (level, optname, None, optlen: int)

     Set the value of the given socket option (see the Unix manual page
     ‘setsockopt(2)(16)’).  The needed symbolic constants are defined in
     this module (SO_* etc.  <socket-unix-constants>).  The value can be
     an integer, ‘None’ or a *note bytes-like object: cd4. representing
     a buffer.  In the later case it is up to the caller to ensure that
     the bytestring contains the proper bits (see the optional built-in
     module *note struct: c0. for a way to encode C structures as
     bytestrings).  When 'value' is set to ‘None’, 'optlen' argument is
     required.  It's equivalent to call ‘setsockopt()’ C function with
     ‘optval=NULL’ and ‘optlen=optlen’.

     在 3.5 版的變更: Writable *note bytes-like object: cd4. is now
     accepted.

     在 3.6 版的變更: setsockopt(level, optname, None, optlen: int) form
     added.

     *note 適用: 1c56.：非 WASI。

 -- 方法: socket.shutdown (how)

     Shut down one or both halves of the connection.  If 'how' is *note
     SHUT_RD: 3266, further receives are disallowed.  If 'how' is *note
     SHUT_WR: 3267, further sends are disallowed.  If 'how' is *note
     SHUT_RDWR: 3268, further sends and receives are disallowed.

     *note 適用: 1c56.：非 WASI。

 -- 方法: socket.share (process_id)

     Duplicate a socket and prepare it for sharing with a target
     process.  The target process must be provided with 'process_id'.
     The resulting bytes object can then be passed to the target process
     using some form of interprocess communication and the socket can be
     recreated there using *note fromshare(): bae.  Once this method has
     been called, it is safe to close the socket since the operating
     system has already duplicated it for the target process.

     *note 適用: 1c56.：Windows。

     在 3.3 版被加入.

Note that there are no methods ‘read()’ or ‘write()’; use *note recv():
d4a. and *note send(): d4d. without 'flags' argument instead.

Socket objects also have these (read-only) attributes that correspond to
the values given to the *note socket: d47. constructor.

 -- 屬性: socket.family

     The socket family.

 -- 屬性: socket.type

     The socket type.

 -- 屬性: socket.proto

     The socket protocol.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0475/

   (2) https://peps.python.org/pep-0475/

   (3) https://manpages.debian.org/getsockopt(2)

   (4) https://msdn.microsoft.com/en-us/library/ms741621%28VS.85%29.aspx

   (5) https://manpages.debian.org/recv(2)

   (6) https://peps.python.org/pep-0475/

   (7) https://manpages.debian.org/recv(2)

   (8) https://peps.python.org/pep-0475/

   (9) https://peps.python.org/pep-0475/

   (10) https://manpages.debian.org/recv(2)

   (11) https://manpages.debian.org/recv(2)

   (12) https://peps.python.org/pep-0475/

   (13) https://peps.python.org/pep-0475/

   (14) https://peps.python.org/pep-0475/

   (15) https://peps.python.org/pep-0475/

   (16) https://manpages.debian.org/setsockopt(2)


File: python.info,  Node: Notes on socket timeouts,  Next: 範例<25>,  Prev: Socket 物件,  Up: socket --- 低階網路介面

5.18.2.9 Notes on socket timeouts
.................................

A socket object can be in one of three modes: blocking, non-blocking, or
timeout.  Sockets are by default always created in blocking mode, but
this can be changed by calling *note setdefaulttimeout(): 323d.

   * In 'blocking mode', operations block until complete or the system
     returns an error (such as connection timed out).

   * In 'non-blocking mode', operations fail (with an error that is
     unfortunately system-dependent) if they cannot be completed
     immediately: functions from the *note select: af. module can be
     used to know when and whether a socket is available for reading or
     writing.

   * In 'timeout mode', operations fail if they cannot be completed
     within the timeout specified for the socket (they raise a *note
     timeout: 7d8. exception) or if the system returns an error.

     備註: At the operating system level, sockets in 'timeout mode' are
     internally set in non-blocking mode.  Also, the blocking and
     timeout modes are shared between file descriptors and socket
     objects that refer to the same network endpoint.  This
     implementation detail can have visible consequences if e.g.  you
     decide to use the *note fileno(): 327a. of a socket.

* Menu:

* Timeouts and the connect method::
* Timeouts and the accept method::


File: python.info,  Node: Timeouts and the connect method,  Next: Timeouts and the accept method,  Up: Notes on socket timeouts

5.18.2.10 Timeouts and the ‘connect’ method
...........................................

The *note connect(): d49. operation is also subject to the timeout
setting, and in general it is recommended to call *note settimeout():
3239. before calling *note connect(): d49. or pass a timeout parameter
to *note create_connection(): 618.  However, the system network stack
may also return a connection timeout error of its own regardless of any
Python socket timeout setting.


File: python.info,  Node: Timeouts and the accept method,  Prev: Timeouts and the connect method,  Up: Notes on socket timeouts

5.18.2.11 Timeouts and the ‘accept’ method
..........................................

If *note getdefaulttimeout(): 326e. is not *note None: 61b, sockets
returned by the *note accept(): d48. method inherit that timeout.
Otherwise, the behaviour depends on settings of the listening socket:

   * if the listening socket is in 'blocking mode' or in 'timeout mode',
     the socket returned by *note accept(): d48. is in 'blocking mode';

   * if the listening socket is in 'non-blocking mode', whether the
     socket returned by *note accept(): d48. is in blocking or
     non-blocking mode is operating system-dependent.  If you want to
     ensure cross-platform behaviour, it is recommended you manually
     override this setting.


File: python.info,  Node: 範例<25>,  Prev: Notes on socket timeouts,  Up: socket --- 低階網路介面

5.18.2.12 範例
..............

Here are four minimal example programs using the TCP/IP protocol: a
server that echoes all data that it receives back (servicing only one
client), and a client using it.  Note that a server must perform the
sequence *note socket(): d47, *note bind(): 14a8, *note listen(): e00,
*note accept(): d48. (possibly repeating the *note accept(): d48. to
service more than one client), while a client only needs the sequence
*note socket(): d47, *note connect(): d49.  Also note that the server
does not *note sendall(): d4e./*note recv(): d4a. on the socket it is
listening on but on the new socket returned by *note accept(): d48.

前兩個範例只支援 IPv4：

     # Echo server program
     import socket

     HOST = ''                 # Symbolic name meaning all available interfaces
     PORT = 50007              # Arbitrary non-privileged port
     with socket.socket(socket.AF_INET, socket.SOCK_STREAM) as s:
         s.bind((HOST, PORT))
         s.listen(1)
         conn, addr = s.accept()
         with conn:
             print('Connected by', addr)
             while True:
                 data = conn.recv(1024)
                 if not data: break
                 conn.sendall(data)

     # Echo client program
     import socket

     HOST = 'daring.cwi.nl'    # The remote host
     PORT = 50007              # The same port as used by the server
     with socket.socket(socket.AF_INET, socket.SOCK_STREAM) as s:
         s.connect((HOST, PORT))
         s.sendall(b'Hello, world')
         data = s.recv(1024)
     print('Received', repr(data))

The next two examples are identical to the above two, but support both
IPv4 and IPv6.  The server side will listen to the first address family
available (it should listen to both instead).  On most of IPv6-ready
systems, IPv6 will take precedence and the server may not accept IPv4
traffic.  The client side will try to connect to all the addresses
returned as a result of the name resolution, and sends traffic to the
first one connected successfully.

     # Echo server program
     import socket
     import sys

     HOST = None               # Symbolic name meaning all available interfaces
     PORT = 50007              # Arbitrary non-privileged port
     s = None
     for res in socket.getaddrinfo(HOST, PORT, socket.AF_UNSPEC,
                                   socket.SOCK_STREAM, 0, socket.AI_PASSIVE):
         af, socktype, proto, canonname, sa = res
         try:
             s = socket.socket(af, socktype, proto)
         except OSError as msg:
             s = None
             continue
         try:
             s.bind(sa)
             s.listen(1)
         except OSError as msg:
             s.close()
             s = None
             continue
         break
     if s is None:
         print('could not open socket')
         sys.exit(1)
     conn, addr = s.accept()
     with conn:
         print('Connected by', addr)
         while True:
             data = conn.recv(1024)
             if not data: break
             conn.send(data)

     # Echo client program
     import socket
     import sys

     HOST = 'daring.cwi.nl'    # The remote host
     PORT = 50007              # The same port as used by the server
     s = None
     for res in socket.getaddrinfo(HOST, PORT, socket.AF_UNSPEC, socket.SOCK_STREAM):
         af, socktype, proto, canonname, sa = res
         try:
             s = socket.socket(af, socktype, proto)
         except OSError as msg:
             s = None
             continue
         try:
             s.connect(sa)
         except OSError as msg:
             s.close()
             s = None
             continue
         break
     if s is None:
         print('could not open socket')
         sys.exit(1)
     with s:
         s.sendall(b'Hello, world')
         data = s.recv(1024)
     print('Received', repr(data))

The next example shows how to write a very simple network sniffer with
raw sockets on Windows.  The example requires administrator privileges
to modify the interface:

     import socket

     # the public network interface
     HOST = socket.gethostbyname(socket.gethostname())

     # create a raw socket and bind it to the public interface
     s = socket.socket(socket.AF_INET, socket.SOCK_RAW, socket.IPPROTO_IP)
     s.bind((HOST, 0))

     # Include IP headers
     s.setsockopt(socket.IPPROTO_IP, socket.IP_HDRINCL, 1)

     # receive all packets
     s.ioctl(socket.SIO_RCVALL, socket.RCVALL_ON)

     # receive a packet
     print(s.recvfrom(65565))

     # disabled promiscuous mode
     s.ioctl(socket.SIO_RCVALL, socket.RCVALL_OFF)

The next example shows how to use the socket interface to communicate to
a CAN network using the raw socket protocol.  To use CAN with the
broadcast manager protocol instead, open a socket with:

     socket.socket(socket.AF_CAN, socket.SOCK_DGRAM, socket.CAN_BCM)

After binding (‘CAN_RAW’) or connecting (*note CAN_BCM: f45.) the
socket, you can use the *note socket.send(): d4d. and *note
socket.recv(): d4a. operations (and their counterparts) on the socket
object as usual.

This last example might require special privileges:

     import socket
     import struct


     # CAN frame packing/unpacking (see 'struct can_frame' in <linux/can.h>)

     can_frame_fmt = "=IB3x8s"
     can_frame_size = struct.calcsize(can_frame_fmt)

     def build_can_frame(can_id, data):
         can_dlc = len(data)
         data = data.ljust(8, b'\x00')
         return struct.pack(can_frame_fmt, can_id, can_dlc, data)

     def dissect_can_frame(frame):
         can_id, can_dlc, data = struct.unpack(can_frame_fmt, frame)
         return (can_id, can_dlc, data[:can_dlc])


     # create a raw socket and bind it to the 'vcan0' interface
     s = socket.socket(socket.AF_CAN, socket.SOCK_RAW, socket.CAN_RAW)
     s.bind(('vcan0',))

     while True:
         cf, addr = s.recvfrom(can_frame_size)

         print('Received: can_id=%x, can_dlc=%x, data=%s' % dissect_can_frame(cf))

         try:
             s.send(cf)
         except OSError:
             print('Error sending CAN frame')

         try:
             s.send(build_can_frame(0x01, b'\x01\x02\x03'))
         except OSError:
             print('Error sending CAN frame')

Running an example several times with too small delay between
executions, could lead to this error:

     OSError: [Errno 98] Address already in use

This is because the previous execution has left the socket in a
‘TIME_WAIT’ state, and can't be immediately reused.

There is a *note socket: b8. flag to set, in order to prevent this,
‘socket.SO_REUSEADDR’:

     s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
     s.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
     s.bind((HOST, PORT))

the ‘SO_REUSEADDR’ flag tells the kernel to reuse a local socket in
‘TIME_WAIT’ state, without waiting for its natural timeout to expire.

也參考
......

For an introduction to socket programming (in C), see the following
papers:

   - 'An Introductory 4.3BSD Interprocess Communication Tutorial', by
     Stuart Sechrest

   - 'An Advanced 4.3BSD Interprocess Communication Tutorial', by Samuel
     J. Leffler et al,

both in the UNIX Programmer's Manual, Supplementary Documents 1
(sections PS1:7 and PS1:8).  The platform-specific reference material
for the various socket-related system calls are also a valuable source
of information on the details of socket semantics.  For Unix, refer to
the manual pages; for Windows, see the WinSock (or Winsock 2)
specification.  For IPv6-ready APIs, readers may want to refer to RFC
3493(1) titled Basic Socket Interface Extensions for IPv6.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc3493.html


File: python.info,  Node: ssl --- socket 物件的 TLS/SSL 包裝器,  Next: select --- 等待 I/O 完成,  Prev: socket --- 低階網路介面,  Up: Networking and Interprocess Communication

5.18.3 ‘ssl’ -- socket 物件的 TLS/SSL 包裝器
--------------------------------------------

'原始碼：'Lib/ssl.py(1)

__________________________________________________________________

這個模組向客戶端及伺服器端提供了對於網路 socket 的傳輸層安全性協定（或稱
為「安全通訊協定 (Secure Sockets Layer)」）加密及身分驗證功能。這個模組
使用 OpenSSL 套件，它可以在所有的 Unix 系統、Windows、macOS、以及其他任
何可能的平台上使用，只要事先在該平台上安裝 OpenSSL。

     備註: 由於呼叫了作業系統的 socket APIs，有些行為會根據平台而有所不
     同。OpenSSL 的安裝版本也會對模組的運作產生影響。例如，OpenSSL 版本
     1.1.1 附帶 TLSv1.3。

     警告: 在使用此模組之前，請閱讀 *note Security considerations:
     317d.。如果不這樣做，可能會產生錯誤的安全性認知，因為 ssl 模組的預
     設設定未必適合你的應用程式。

*note Availability: 1c56.: not WASI.

This module does not work or is not available on WebAssembly.  See *note
WebAssembly 平台: 16e6. for more information.

這個章節記錄了 ‘ssl’ 模組的物件及函式；關於 TSL、SSL、以及憑證的更多資訊
，可以去參考此章節底部的「詳情」部分。

This module provides a class, *note ssl.SSLSocket: 88f, which is derived
from the *note socket.socket: d47. type, and provides a socket-like
wrapper that also encrypts and decrypts the data going over the socket
with SSL. It supports additional methods such as ‘getpeercert()’, which
retrieves the certificate of the other side of the connection,
‘cipher()’, which retrieves the cipher being used for the secure
connection or ‘get_verified_chain()’, ‘get_unverified_chain()’ which
retrieves certificate chain.

對於更複雜的應用程式，*note ssl.SSLContext: 276. 類別有助於管理設定及認
證，然後可以透過 *note SSLContext.wrap_socket(): 4c9. 方法建立的 SSL
socket 繼承這些設定和認證。

在 3.5.3 版的變更: 更新以支援與 OpenSSL 1.1.0 進行連結

在 3.6 版的變更: OpenSSL 0.9.8, 1.0.0 及 1.0.1 版本已被棄用且不再支援。
在未來 ssl 模組將需要至少 OpenSSL 1.0.2 版本或 1.1.0 版本。

在 3.10 版的變更: PEP 644(2) 已經被實作。ssl 模組需要 OpenSSL 1.1.1 以上
的版本才能使用。

使用已經被棄用的常數或函式將會導致棄用警示。

* Menu:

* 函式、常數與例外::
* SSL Sockets::
* SSL Contexts::
* Certificates::
* 範例: 範例<26>.
* Notes on non-blocking sockets::
* Memory BIO Support: Memory BIO Support<2>.
* SSL session::
* Security considerations: Security considerations<2>.
* TLS 1.3: TLS 1 3.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/ssl.py

   (2) https://peps.python.org/pep-0644/


File: python.info,  Node: 函式、常數與例外,  Next: SSL Sockets,  Up: ssl --- socket 物件的 TLS/SSL 包裝器

5.18.3.1 函式、常數與例外
.........................

* Menu:

* Socket 建立::
* 語境建立::
* 例外: 例外<11>.
* 隨機產生::
* 認證處理::
* 常數: 常數<8>.


File: python.info,  Node: Socket 建立,  Next: 語境建立,  Up: 函式、常數與例外

5.18.3.2 Socket 建立
....................

*note SSLSocket: 88f. 實例必須使用 *note SSLContext.wrap_socket(): 4c9.
方法來建立。輔助函式 *note create_default_context(): 13a. 會回傳有安全預
設設定的新語境 (context)。

使用預設語境及 IPv4/IPv6 雙協定堆疊的客戶端 socket 範例：

     import socket
     import ssl

     hostname = 'www.python.org'
     context = ssl.create_default_context()

     with socket.create_connection((hostname, 443)) as sock:
         with context.wrap_socket(sock, server_hostname=hostname) as ssock:
             print(ssock.version())

使用自訂語境及 IPv4 的客戶端 socket範例：

     hostname = 'www.python.org'
     # PROTOCOL_TLS_CLIENT requires valid cert chain and hostname
     context = ssl.SSLContext(ssl.PROTOCOL_TLS_CLIENT)
     context.load_verify_locations('path/to/cabundle.pem')

     with socket.socket(socket.AF_INET, socket.SOCK_STREAM, 0) as sock:
         with context.wrap_socket(sock, server_hostname=hostname) as ssock:
             print(ssock.version())

在本地 IPv4 上監聽伺服器 socket 的範例：

     context = ssl.SSLContext(ssl.PROTOCOL_TLS_SERVER)
     context.load_cert_chain('/path/to/certchain.pem', '/path/to/private.key')

     with socket.socket(socket.AF_INET, socket.SOCK_STREAM, 0) as sock:
         sock.bind(('127.0.0.1', 8443))
         sock.listen(5)
         with context.wrap_socket(sock, server_side=True) as ssock:
             conn, addr = ssock.accept()
             ...


File: python.info,  Node: 語境建立,  Next: 例外<11>,  Prev: Socket 建立,  Up: 函式、常數與例外

5.18.3.3 語境建立
.................

一個可以幫忙建立出 *note SSLContext: 276. 物件以用於一般目的的方便函式。

 -- 函式: ssl.create_default_context (purpose=Purpose.SERVER_AUTH,
          cafile=None, capath=None, cadata=None)

     回傳一個新的 *note SSLContext: 276. 物件，使用給定 'purpose' 的預設
     值。這些設定是由 *note ssl: bb. 選擇，通常比直接呼叫 *note
     SSLContext: 276. 有更高的安全性。

     'cafile', 'capath', 'cadata' 是用來選擇用於憑證認證的 CA 憑證，就像
     *note SSLContext.load_verify_locations(): e8f. 一樣。如果三個值都是
     *note None: 61b.，此函式會自動選擇系統預設的 CA 憑證。

     這些設定包含：*note PROTOCOL_TLS_CLIENT: 815. 或 *note
     PROTOCOL_TLS_SERVER: 816.、*note OP_NO_SSLv2: 7dd.、以及 *note
     OP_NO_SSLv3: 7de.，使用高等加密套件但不包含 RC4 和未經身份驗證的加
     密套件。如果將 'purpose' 設定為 *note SERVER_AUTH: f55.，則會把
     *note verify_mode: 328b. 設為 *note CERT_REQUIRED: 328c. 並使用設定
     的 CA 憑證(當 'cafile'、'capath' 或 'cadata' 其中一個值有被設定時)
     或使用預設的 CA 憑證 *note SSLContext.load_default_certs(): f54. 。

     當系統有支援 *note keylog_filename: 328d. 並且有設定環境變數
     ‘SSLKEYLOGFILE’ 時 *note create_default_context(): 13a. 會啟用密鑰
     日誌記錄 (logging)。

     The default settings for this context include *note
     VERIFY_X509_PARTIAL_CHAIN: 13b. and *note VERIFY_X509_STRICT: 13c.
     These make the underlying OpenSSL implementation behave more like a
     conforming implementation of RFC 5280(1), in exchange for a small
     amount of incompatibility with older X.509 certificates.

          備註: 協定、選項、加密方式和其它設定可以在不捨棄舊值的情況下直
          接更改成新的值，這些值代表了在相容性和安全性之間取得的合理平衡
          。

          如果你的應用程式需要特殊的設定，你應該要自行建立一個 *note
          SSLContext: 276. 並自行調整設定。

          備註: 如果你發現某些舊的客戶端或伺服器常適用此函式建立的 *note
          SSLContext: 276. 連線時，收到 "Protocol or cipher suite
          mismatch" 錯誤，這可能是因為他們的系統僅支援 SSL3.0，然而
          SSL3.0 已被此函數用 *note OP_NO_SSLv3: 7de. 排除。目前廣泛認為
          SSL3.0 已經被完全破解(2)。如果你仍然希望在允許 SSL3.0 連線的情
          況下使用此函數，可以使用下面的方法：

               ctx = ssl.create_default_context(Purpose.CLIENT_AUTH)
               ctx.options &= ~ssl.OP_NO_SSLv3

          備註: This context enables *note VERIFY_X509_STRICT: 13c. by
          default, which may reject pre- RFC 5280(3) or malformed
          certificates that the underlying OpenSSL implementation
          otherwise would accept.  While disabling this is not
          recommended, you can do so using:

               ctx = ssl.create_default_context()
               ctx.verify_flags &= ~ssl.VERIFY_X509_STRICT

     在 3.4 版被加入.

     在 3.4.4 版的變更: 把 RC4 從預設加密方法字串中捨棄。

     在 3.6 版的變更: 把 ChaCha20/Poly1305 加入預設加密方法字串。

     把 3DES 從預設加密方法字串中捨棄。

     在 3.8 版的變更: 增加了 ‘SSLKEYLOGFILE’ 對密鑰日誌記錄 (logging) 的
     支援。

     在 3.10 版的變更: 當前語境使用 *note PROTOCOL_TLS_CLIENT: 815. 協定
     或 *note PROTOCOL_TLS_SERVER: 816. 協定而非通用的 *note
     PROTOCOL_TLS: 328e.。

     在 3.13 版的變更: The context now uses *note
     VERIFY_X509_PARTIAL_CHAIN: 13b. and *note VERIFY_X509_STRICT: 13c.
     in its default verify flags.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc5280.html

   (2) https://en.wikipedia.org/wiki/POODLE

   (3) https://datatracker.ietf.org/doc/html/rfc5280.html


File: python.info,  Node: 例外<11>,  Next: 隨機產生,  Prev: 語境建立,  Up: 函式、常數與例外

5.18.3.4 例外
.............

 -- 例外: ssl.SSLError

     引發由底層 SSL 實作（目前由 OpenSSL 函式庫提供）所引發的錯誤訊息。
     這表示在覆蓋底層網路連線的高階加密和身份驗證層中存在一些問題。這項
     錯誤是 *note OSError: 350. 的一個子型別。*note SSLError: 1212. 實例
     的錯誤程式代碼和訊息是由 OpenSSL 函式庫提供。

     在 3.3 版的變更: *note SSLError: 1212. 曾經是 *note socket.error:
     ff8. 的一個子型別。

      -- 屬性: library

          一個字串符號 (string mnemonic)，用來指定發生錯誤的 OpenSSL 子
          模組，如：‘SSL’、‘PEM’ 或 ‘X509’。可能值的範圍取決於 OpenSSL 的
          版本。

          在 3.3 版被加入.

      -- 屬性: reason

          一個字串符號，用來指定發生錯誤的原因，如：
          ‘CERTIFICATE_VERIFY_FAILED’。可能值的範圍取決於 OpenSSL 的版本
          。

          在 3.3 版被加入.

 -- 例外: ssl.SSLZeroReturnError

     一個 *note SSLError: 1212. 的子類別，當嘗試去讀寫已經被完全關閉的
     SSL 連線時會被引發。請注意，這並不表示底層傳輸（例如 TCP）已經被關
     閉。

     在 3.3 版被加入.

 -- 例外: ssl.SSLWantReadError

     一個 *note SSLError: 1212. 的子類別，當嘗試去讀寫資料前，底層 TCP 傳
     輸需要先接收更多資料時會由*note 非阻塞的 SSL socket: 3291. 引發該錯
     誤。

     在 3.3 版被加入.

 -- 例外: ssl.SSLWantWriteError

     一個 *note SSLError: 1212. 的子類別，當嘗試去讀寫資料前，底層 TCP 傳
     輸需要先發送更多資料時會由*note 非阻塞的 SSL socket: 3291. 引發該錯
     誤。

     在 3.3 版被加入.

 -- 例外: ssl.SSLSyscallError

     一個 *note SSLError: 1212. 的子類別，當嘗試去操作 SSL socket 時有系
     統錯誤產生會引發此錯誤。不幸的是，目前沒有任何簡單的方法可以去檢查
     原本的的 errno 編號。

     在 3.3 版被加入.

 -- 例外: ssl.SSLEOFError

     一個 *note SSLError: 1212. 的子類別，當 SSL 連線被突然終止時會引發
     此錯誤。通常，當此錯誤發生時，你不該再去重新使用底層傳輸。

     在 3.3 版被加入.

 -- 例外: ssl.SSLCertVerificationError

     當憑證驗證失敗時會引發的一個 *note SSLError: 1212. 子類別。

     在 3.7 版被加入.

      -- 屬性: verify_code

          一個表示驗證錯誤的錯誤數值編號。

      -- 屬性: verify_message

          一個人類可讀的驗證錯誤字串。

 -- 例外: ssl.CertificateError

     *note SSLCertVerificationError: b20. 的別名。

     在 3.7 版的變更: 此例外現在是 *note SSLCertVerificationError: b20.
     的別名。


File: python.info,  Node: 隨機產生,  Next: 認證處理,  Prev: 例外<11>,  Up: 函式、常數與例外

5.18.3.5 隨機產生
.................

 -- 函式: ssl.RAND_bytes (num)

     回傳 'num' 個加密性強的偽隨機位元組。如果 PRNG 未使用足夠的資料做為
     隨機種子 (seed) 或是目前的 RAND 方法不支持該操作則會導致 *note
     SSLError: 1212. 錯誤。*note RAND_status(): 17c9. 函式可以用來檢查
     PRNG 函式，而 *note RAND_add(): 3297. 則可以用來為 PRNG 設定隨機種
     子。

     在幾乎所有的應用程式中，*note os.urandom(): 4c7. 會是較好的選擇。

     請閱讀維基百科的密碼學安全偽隨機數產生器 (CSPRNG)(1)文章來了解密碼
     學安全偽隨機數產生器的需求。

     在 3.3 版被加入.

 -- 函式: ssl.RAND_status ()

     如果 SSL 偽隨機數產生器已經使用「足夠的」隨機性進行隨機種子生成，則
     回傳 ‘True’ ，否則回傳 ‘False’。你可以使用 ‘ssl.RAND_egd()’ 函式和
     *note ssl.RAND_add(): 3297. 函式來增加偽隨機數產生器的隨機性。

 -- 函式: ssl.RAND_add (bytes, entropy)

     將給定的 'bytes' 混進 SSL 隨機偽隨機數產生器中。 'entropy' 參數（
     float 值）是指字串中包含熵值的下限（因此你可以將其設為 ‘0.0’）。請
     參閱 RFC 1750(2) 了解有關熵源的更多資訊。

     在 3.5 版的變更: 可寫入的*note 類位元組物件: cd4.現在可被接受。

   ---------- Footnotes ----------

   (1) 
https://en.wikipedia.org/wiki/Cryptographically_secure_pseudorandom_number_generator

   (2) https://datatracker.ietf.org/doc/html/rfc1750.html


File: python.info,  Node: 認證處理,  Next: 常數<8>,  Prev: 隨機產生,  Up: 函式、常數與例外

5.18.3.6 認證處理
.................

 -- 函式: ssl.cert_time_to_seconds (cert_time)

     回傳自紀元以來的秒數，給定的 ‘cert_time’ 字串表示憑證的 "notBefore"
     或 "notAfter" 日期，字串採用 ‘"%b %d %H:%M:%S %Y %Z"’ 格式（C 語言
     區域設定）。

     以下是一個範例：

          >>> import ssl
          >>> timestamp = ssl.cert_time_to_seconds("Jan  5 09:34:43 2018 GMT")
          >>> timestamp
          1515144883
          >>> from datetime import datetime
          >>> print(datetime.utcfromtimestamp(timestamp))
          2018-01-05 09:34:43

     "notBefore" 或 "notAfter" 日期必須使用 GMT ( RFC 5280(1))。

     在 3.5 版的變更: 將輸入的時間直譯為 UTC 時間，如輸入字串中指定的
     'GMT' 時區。在之前是使用本地的時區。回傳一個整數（在輸入格式中不包
     括秒的小數部分）。

 -- 函式: ssl.get_server_certificate (addr,
          ssl_version=PROTOCOL_TLS_CLIENT, ca_certs=None[, timeout])

     輸入使用 SSL 保護的伺服器的地址 ‘addr’，輸入形式為一個 pair
     ('hostname', 'port-number')，獲取該伺服器的憑證，並以 PEM 編碼字串
     的形式回傳。如果指定了 ‘ssl_version’，則使用指定的 SSL 協議來嘗試與
     伺服器連線。如果指定 'ca_certs'，則它應該是一個包含根憑證列表的檔案
     ，並與 *note SSLContext.load_verify_locations(): e8f. 中的參數
     'cafile' 所使用的格式相同。此呼叫將嘗試使用該組根憑證對伺服器憑證進
     行驗證，如果驗證失敗，呼叫將失敗。可以使用 ‘timeout’ 參數指定超時時
     間。

     在 3.3 版的變更: 此函式現在是與 IPv6 相容的。

     在 3.5 版的變更: 預設的 'ssl_version' 已經從 *note PROTOCOL_SSLv3:
     3299. 改為 *note PROTOCOL_TLS: 328e.，已確保與現今的伺服器有最大的
     相容性。

     在 3.10 版的變更: 新增 'timeout' 參數。

 -- 函式: ssl.DER_cert_to_PEM_cert (DER_cert_bytes)

     給定一個以 DER 編碼的位元組 blob 作為憑證，回傳以 PEM 編碼字串版本
     的相同憑證。

 -- 函式: ssl.PEM_cert_to_DER_cert (PEM_cert_string)

     給定一個以 ASCII PEM 的字串作為憑證，回傳以 DER 編碼的位元組序列的
     相同憑證。

 -- 函式: ssl.get_default_verify_paths ()

     回傳一個具有 OpenSSL 的預設 cafile 和 capath 路徑的附名元組。這些路
     徑與 *note SSLContext.set_default_verify_paths(): f4d. 使用的相同。
     回傳值是一個 *note named tuple: 5f4. ‘DefaultVerifyPaths’：

        * ‘cafile’ - 解析後的 cafile 路徑，如果檔案不存在則為 ‘None’，

        * ‘capath’ - 解析後的 capath 路徑，如果目錄不存在則為 ‘None’，

        * ‘openssl_cafile_env’ - 指向 cafile 的 OpenSSL 環境密鑰，

        * ‘openssl_cafile’ - hard coded 的 cafile 路徑，

        * ‘openssl_capath_env’ - 指向 capath 的 OpenSSL 環境密鑰，

        * ‘openssl_capath’ - hard coded 的 capath 目錄路徑

     在 3.4 版被加入.

 -- 函式: ssl.enum_certificates (store_name)

     從 Windows 的系統憑證儲存庫中搜尋憑證。'store_name' 可以是 ‘CA’、
     ‘ROOT’ 或 ‘MY’ 的其中一個。Windows 也可能會提供額外的憑證儲存庫。

     此函式會回傳一個元組 (cert_bytes, encoding_type, trust) 串列。
     encoding_type 指定了 cert_bytes 的編碼格式。它可以是用來表示 X.509
     ASN.1 資料的 ‘x509_asn’ 或是用來表示 PKCS#7 ASN.1 資料的
     ‘pkcs_7_asn’。Trust 通過一組 OIDS 來指定憑證的用途，或是如果憑證對
     所有用途都可以使用則回傳 ‘True’。

     範例：

          >>> ssl.enum_certificates("CA")
          [(b'data...', 'x509_asn', {'1.3.6.1.5.5.7.3.1', '1.3.6.1.5.5.7.3.2'}),
           (b'data...', 'x509_asn', True)]

     *note 適用: 1c56.：只有 Windows。

     在 3.4 版被加入.

 -- 函式: ssl.enum_crls (store_name)

     從 Windows 的系統憑證儲存庫中搜尋 CRLs。'store_name' 可以是 ‘CA’、
     ‘ROOT’ 或 ‘MY’ 的其中一個。Windows 也可能會提供額外的憑證儲存庫。

     此函式會回傳一個元組 (cert_bytes, encoding_type, trust) 串列。
     encoding_type 指定了 cert_bytes 的編碼格式。它可以是用來表示 X.509
     ASN.1 資料的 ‘x509_asn’ 或是用來表示 PKCS#7 ASN.1 資料的
     ‘pkcs_7_asn’。

     *note 適用: 1c56.：只有 Windows。

     在 3.4 版被加入.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc5280.html


File: python.info,  Node: 常數<8>,  Prev: 認證處理,  Up: 函式、常數與例外

5.18.3.7 常數
.............

     所有的常數現在都是 *note enum.IntEnum: c86. 或 *note enum.IntFlag:
     21d7. 的集合。

     在 3.6 版被加入.

 -- 資料: ssl.CERT_NONE

     *note SSLContext.verify_mode: 328b. 可能的值。除了 *note
     SSLContext.verify_mode: 328b. 外，這是預設的模式。對於客戶端的
     sockets，幾乎任何憑證都能被允許。驗證錯誤，像是不被信任或是過期的憑
     證，會被忽略並不會中止 TLS/SSL 握手。

     在伺服器模式下，不會從客戶端請求任何憑證，所以客戶端不用發送任何用
     於客戶端憑證身分驗證的憑證。

     參閱下方 *note Security considerations: 317d. 的討論。

 -- 資料: ssl.CERT_OPTIONAL

     *note SSLContext.verify_mode: 328b. 可能的值。在客戶端模式下，*note
     CERT_OPTIONAL: 329e. 具有與 *note CERT_REQUIRED: 328c. 相同的含意。
     對於客戶端 sockets 推薦改用 *note CERT_REQUIRED: 328c.。

     在伺服器模式下，客戶憑證請求會被發送給客戶端。客戶端可以選擇忽略請
     求或是選擇發送憑證來執行 TLS 客戶端憑證身分驗證。如果客戶端選擇發送
     憑證，則會對其進行驗證。任何驗證錯誤都會立刻終止 TLS 握手。

     使用此設定需要將一組有效的 CA 憑證傳送給 *note
     SSLContext.load_verify_locations(): e8f.。

 -- 資料: ssl.CERT_REQUIRED

     *note SSLContext.verify_mode: 328b. 可能的值。在這個模式下，需要從
     socket 連線的另一端獲取憑證；如果未提供憑證或是驗證失敗，則將會導致
     *note SSLError: 1212.。此模式 '不能' 在客戶端模式下對憑證進行驗證，
     因為它無法去配對主機名稱。*note check_hostname: 329f. 也必須被開起
     來來驗證憑證的真實性。*note PROTOCOL_TLS_CLIENT: 815. 會使用 *note
     CERT_REQUIRED: 328c. 並預設開啟 *note check_hostname: 329f.。

     對於 socket 伺服器，此模式會提供強制的 TLS 客戶端憑證驗證。客戶端憑
     證請求會被發送給客戶端並且客戶端必須提供有效且被信任的憑證。

     使用此設定需要將一組有效的 CA 憑證傳送給 *note
     SSLContext.load_verify_locations(): e8f.。

 -- 類別: ssl.VerifyMode

     *note enum.IntEnum: c86. 為 CERT_* 常數的一個集合。

     在 3.6 版被加入.

 -- 資料: ssl.VERIFY_DEFAULT

     *note SSLContext.verify_flags: f50. 可能的值。在此模式下，不會檢查
     憑證吊銷列表 (CRLs)。預設的 OpenSSL 並不會請求及驗證 CRLs。

     在 3.4 版被加入.

 -- 資料: ssl.VERIFY_CRL_CHECK_LEAF

     *note SSLContext.verify_flags: f50. 可能的值。在此模式下，只會檢查
     同等的憑證而不會去檢查中間的 CA 憑證。此模式需要提供由對等憑證發行
     者 (它的直接上級 CA) 的有效的 CRL 簽名。如果沒有用 *note
     SSLContext.load_verify_locations: e8f. 載入適當的 CRL，則會驗證失敗
     。

     在 3.4 版被加入.

 -- 資料: ssl.VERIFY_CRL_CHECK_CHAIN

     *note SSLContext.verify_flags: f50. 可能的值。在此模式下，會檢查對
     等憑證鍊中所有憑證的 CRLs。

     在 3.4 版被加入.

 -- 資料: ssl.VERIFY_X509_STRICT

     *note SSLContext.verify_flags: f50. 可能的值，用來禁用已損壞的
     X.509 憑證的解決方法。

     在 3.4 版被加入.

 -- 資料: ssl.VERIFY_ALLOW_PROXY_CERTS

     *note SSLContext.verify_flags: f50. 可能的值，用來啟用憑證代理驗證
     。

     在 3.10 版被加入.

 -- 資料: ssl.VERIFY_X509_TRUSTED_FIRST

     *note SSLContext.verify_flags: f50. 可能的值。它指示 OpenSSL 在構建
     信任鍊來驗證憑證時會優先使用被信任的憑證。此旗標預設開啟。

     在 3.4.4 版被加入.

 -- 資料: ssl.VERIFY_X509_PARTIAL_CHAIN

     *note SSLContext.verify_flags: f50. 可能的值。它指示 OpenSSL 接受信
     任存儲中的中間 CAs 作為信任錨，就像自簽名的根 CA 憑證。這樣就能去信
     任中間 CA 所頒發的憑證，而不一定非要去信任其祖先的根 CA。

     在 3.10 版被加入.

 -- 類別: ssl.VerifyFlags

     *note enum.IntFlag: 21d7. 為 VERIFY_* 常數的其中一個集合。

     在 3.6 版被加入.

 -- 資料: ssl.PROTOCOL_TLS

     選擇客戶端及伺服器均可以支援最高協定版本。儘管名稱只有 「TLS」，但
     實際上「SSL」和「TLS」均可以選擇。

     在 3.6 版被加入.

     在 3.10 版之後被棄用: TLS 的客戶端及伺服器端需要不同的預設值來實現
     安全通訊。通用的 TLS 協定常數已被廢除，並改用 *note
     PROTOCOL_TLS_CLIENT: 815. 和 *note PROTOCOL_TLS_SERVER: 816.。

 -- 資料: ssl.PROTOCOL_TLS_CLIENT

     自動協商客戶端和服務器都支援的最高協議版本，並配置客戶端語境連線。
     該協定預設啟用 *note CERT_REQUIRED: 328c. 和 *note check_hostname:
     329f.。

     在 3.6 版被加入.

 -- 資料: ssl.PROTOCOL_TLS_SERVER

     自動協商客戶端和服務器都支援的最高協議版本，並配置客戶端語境連線。

     在 3.6 版被加入.

 -- 資料: ssl.PROTOCOL_SSLv23

     *note PROTOCOL_TLS: 328e. 的別名。

     在 3.6 版之後被棄用: 請改用 *note PROTOCOL_TLS: 328e.。

 -- 資料: ssl.PROTOCOL_SSLv3

     選擇第三版的 SSL 做為通道加密協定。

     如果 OpenSSL 是用 ‘no-ssl3’ 編譯的，則此項協議無法使用。

          警告: 第三版的 SSL 是不安全的，強烈建議不要使用。

     在 3.6 版之後被棄用: OpenSSL 已經終止了所有特定版本的協定。請改用預
     設的 *note PROTOCOL_TLS_SERVER: 816. 協定或帶有 *note
     SSLContext.minimum_version: b27. 和 *note
     SSLContext.maximum_version: b28. 的 *note PROTOCOL_TLS_CLIENT:
     815.。

 -- 資料: ssl.PROTOCOL_TLSv1

     選擇 1.0 版的 TLS 做為通道加密協定。

     在 3.6 版之後被棄用: OpenSSL 已經將所有版本特定的協定棄用。

 -- 資料: ssl.PROTOCOL_TLSv1_1

     選擇 1.1 版的 TLS 做為通道加密協定。只有在 1.0.1 版本以上的 OpenSSL
     才可以選用。

     在 3.4 版被加入.

     在 3.6 版之後被棄用: OpenSSL 已經將所有版本特定的協定棄用。

 -- 資料: ssl.PROTOCOL_TLSv1_2

     選擇 1.2 版的 TLS 做為通道加密協定。只有在 1.0.1 版本以上的 OpenSSL
     才可以選用。

     在 3.4 版被加入.

     在 3.6 版之後被棄用: OpenSSL 已經將所有版本特定的協定棄用。

 -- 資料: ssl.OP_ALL

     啟用對 SSL 實作時所產生的各種錯誤的緩解措施。此選項預設被設定。它不
     一定設定與 OpenSSL 的 ‘SSL_OP_ALL’ 常數相同的旗標。

     在 3.2 版被加入.

 -- 資料: ssl.OP_NO_SSLv2

     防止 SSLv2 連線。此選項只可以跟 *note PROTOCOL_TLS: 328e. 一起使用
     。它會防止同級 (peer)選用 SSLv2 做為協定版本。

     在 3.2 版被加入.

     在 3.6 版之後被棄用: SSLv2 已被棄用

 -- 資料: ssl.OP_NO_SSLv3

     防止 SSLv3 連線。此選項只可以跟 *note PROTOCOL_TLS: 328e. 一起使用
     。它會防止同級選用 SSLv3 做為協定版本。

     在 3.2 版被加入.

     在 3.6 版之後被棄用: SSLv3 已被棄用

 -- 資料: ssl.OP_NO_TLSv1

     防止 TLSv1 連線。此選項只可以跟 *note PROTOCOL_TLS: 328e. 一起使用
     。它會防止同級選用 TLSv1 做為協定版本。

     在 3.2 版被加入.

     在 3.7 版之後被棄用: 該選項自從 OpenSSL 1.1.0 以後已被棄用，請改用
     新的 *note SSLContext.minimum_version: b27. 及 *note
     SSLContext.maximum_version: b28. 代替。

 -- 資料: ssl.OP_NO_TLSv1_1

     防止 TLSv1.1 連線。此選項只可以跟 *note PROTOCOL_TLS: 328e. 一起使
     用。它會防止同級選用 TLSv1.1 做為協定版本。只有 1.0.1 版後的
     OpenSSL 版本才能使用。

     在 3.4 版被加入.

     在 3.7 版之後被棄用: 此選項自 OpenSSL 1.1.0 版已被棄用。

 -- 資料: ssl.OP_NO_TLSv1_2

     防止 TLSv1.2 連線。此選項只可以跟 *note PROTOCOL_TLS: 328e. 一起使
     用。它會防止同級選用 TLSv1.2 做為協定版本。只有 1.0.1 版後的
     OpenSSL 版本才能使用。

     在 3.4 版被加入.

     在 3.7 版之後被棄用: 此選項自 OpenSSL 1.1.0 版已被棄用。

 -- 資料: ssl.OP_NO_TLSv1_3

     防止 TLSv1.3 連線。此選項只可以跟 *note PROTOCOL_TLS: 328e. 一起使
     用。它會防止同級選用 TLSv1.3 做為協定版本。TSL1.3 只適用於 1.1.1 版
     以後的 OpenSSL。當使用 Python 編譯舊版的 OpenSSL 時，該標志預設為
     '0'。

     在 3.6.3 版被加入.

     在 3.7 版之後被棄用: 此選項自 OpenSSL 1.1.0 以後已被棄用。它被添加
     到 2.7.15 和 3.6.3 中，以向後相容 OpenSSL 1.0.2。

 -- 資料: ssl.OP_NO_RENEGOTIATION

     停用所有在 TLSv1.2 及更早版本的重協商 (renegotiation)。不發送
     HelloRequest 訊息，並忽略通過 ClientHello 的重協商請求。

     此選項僅適用於 OpenSSL 1.1.0h 及更新版本。

     在 3.7 版被加入.

 -- 資料: ssl.OP_CIPHER_SERVER_PREFERENCE

     使用伺服器的加密方法名稱字串排序優先順序，而不是客戶端的。此選項並
     不會影響到客戶端及 SSLv2 伺服器的 sockets。

     在 3.3 版被加入.

 -- 資料: ssl.OP_SINGLE_DH_USE

     防止對不同的 SSL 會談重複使用相同的 DH 密鑰。這會加強向前保密但需要
     更多的運算資源。此選項只適用於伺服器 sockets。

     在 3.3 版被加入.

 -- 資料: ssl.OP_SINGLE_ECDH_USE

     防止對不同的 SSL 會談重複使用相同的 ECDH 密鑰。這會加強向前保密但需
     要更多的運算資源。此選項只適用於伺服器 sockets。

     在 3.3 版被加入.

 -- 資料: ssl.OP_ENABLE_MIDDLEBOX_COMPAT

     在 TLS 1.3 握手中發送虛擬的變更加密方法規範 (CCS) 消息，以使 TLS
     1.3 連接看起來更像 TLS 1.2 連線。

     此選項僅適用於 OpenSSL 1.1.1 及更新版本。

     在 3.8 版被加入.

 -- 資料: ssl.OP_NO_COMPRESSION

     在 SSL 通道上禁用壓縮。如果應用程序協定支援自己的壓縮方案，這會很有
     用。

     在 3.3 版被加入.

 -- 類別: ssl.Options

     *note enum.IntFlag: 21d7. 為 OP_* 常數中的一個集合。

 -- 資料: ssl.OP_NO_TICKET

     防止客戶端請求會談票據。

     在 3.6 版被加入.

 -- 資料: ssl.OP_IGNORE_UNEXPECTED_EOF

     忽略意外關閉的 TLS 連線。

     此選項僅適用於 OpenSSL 3.0.0 及更新版本。

     在 3.10 版被加入.

 -- 資料: ssl.OP_ENABLE_KTLS

     允許使用 TLS 核心。要想受益於該功能，OpenSSL 必須編譯為支援該功能，
     並且想使用的加密套件及擴充套件也必須被該功能支援 (該功能所支援的列
     表可能會因平台及核心而有所差異)。

     請注意當允許使用 TLS 核心時，一些加密操作將直接由核心執行而不是經由
     任何由可用的 OpenSSL 所提供的程序，而這可能並非你所想使用的，例如：
     當應用程式要求所有的加密操作由 FIPS 提供執行。

     此選項僅適用於 OpenSSL 3.0.0 及更新版本。

     在 3.12 版被加入.

 -- 資料: ssl.OP_LEGACY_SERVER_CONNECT

     只允許 OpenSSL 與未修補的伺服器進行遺留 (legacy) 不安全重協商。

     在 3.12 版被加入.

 -- 資料: ssl.HAS_ALPN

     OpenSSL 函式庫是否內建支援 '應用層協定協商' TLS 擴充套件，該擴充套
     件描述在 RFC 7301(1) 中。

     在 3.5 版被加入.

 -- 資料: ssl.HAS_NEVER_CHECK_COMMON_NAME

     OpenSSL 函式庫是否內建支援不檢查主題通用名稱及 *note
     SSLContext.hostname_checks_common_name: b21. 是否可寫。

     在 3.7 版被加入.

 -- 資料: ssl.HAS_ECDH

     OpenSSL 函式庫是否內建支援基於橢圓曲線的 (Elliptic Curve-based)
     Diffie-Hellman 金鑰交換。此回傳值應該要為 true 除非發布者明確禁用此
     功能。

     在 3.3 版被加入.

 -- 資料: ssl.HAS_SNI

     OpenSSL 函式庫是否內建支援 '伺服器名稱提示' 擴充套件 (在 RFC
     6066(2) 中定義)。

     在 3.2 版被加入.

 -- 資料: ssl.HAS_NPN

     OpenSSL 函式庫是否內建支援 '下一代協定協商' 該功能在應用層協定協商
     (3) 中有描述。當此值為 true 時，你可以使用 *note
     SSLContext.set_npn_protocols(): 2d3. 方法來公告你想支援的協定。

     在 3.3 版被加入.

 -- 資料: ssl.HAS_SSLv2

     此 OpenSSL 函式庫是否內建支援 SSL 2.0 協定。

     在 3.7 版被加入.

 -- 資料: ssl.HAS_SSLv3

     此 OpenSSL 函式庫是否內建支援 SSL 3.0 協定。

     在 3.7 版被加入.

 -- 資料: ssl.HAS_TLSv1

     此 OpenSSL 函式庫是否內建支援 TLS 1.0 協定。

     在 3.7 版被加入.

 -- 資料: ssl.HAS_TLSv1_1

     此 OpenSSL 函式庫是否內建支援 TLS 1.1 協定。

     在 3.7 版被加入.

 -- 資料: ssl.HAS_TLSv1_2

     此 OpenSSL 函式庫是否內建支援 TLS 1.2 協定。

     在 3.7 版被加入.

 -- 資料: ssl.HAS_TLSv1_3

     此 OpenSSL 函式庫是否內建支援 TLS 1.3 協定。

     在 3.7 版被加入.

 -- 資料: ssl.HAS_PSK

     Whether the OpenSSL library has built-in support for TLS-PSK.

     在 3.13 版被加入.

 -- 資料: ssl.CHANNEL_BINDING_TYPES

     支援的 TLS 通道綁定類型列表。列表中的字串可以作為 *note
     SSLSocket.get_channel_binding(): 10dd. 的參數。

     在 3.3 版被加入.

 -- 資料: ssl.OPENSSL_VERSION

     直譯器所加載的 OpenSSL 函式庫的版本字串:

          >>> ssl.OPENSSL_VERSION
          'OpenSSL 1.0.2k  26 Jan 2017'

     在 3.2 版被加入.

 -- 資料: ssl.OPENSSL_VERSION_INFO

     代表 OpenSSL 函式庫版本資訊的五個整數的元組：

          >>> ssl.OPENSSL_VERSION_INFO
          (1, 0, 2, 11, 15)

     在 3.2 版被加入.

 -- 資料: ssl.OPENSSL_VERSION_NUMBER

     OpenSSL 函式庫的初始版本，以單一整數表示:

          >>> ssl.OPENSSL_VERSION_NUMBER
          268443839
          >>> hex(ssl.OPENSSL_VERSION_NUMBER)
          '0x100020bf'

     在 3.2 版被加入.

 -- 資料: ssl.ALERT_DESCRIPTION_HANDSHAKE_FAILURE
 -- 資料: ssl.ALERT_DESCRIPTION_INTERNAL_ERROR

 -- 資料: ALERT_DESCRIPTION_*

     來自 RFC 5246(4) 和其他文檔的警報描述。IANA TLS Alert Registry(5) 包
     含了此列表以及其含義定義所在的 RFC 的引用。

     被用來做為 *note SSLContext.set_servername_callback(): f59. 中回呼
     函式的回傳值。

     在 3.4 版被加入.

 -- 類別: ssl.AlertDescription

     *note enum.IntEnum: c86. 為 ALERT_DESCRIPTION_* 常數中的一個集合。

     在 3.6 版被加入.

 -- 資料: Purpose.SERVER_AUTH

     *note create_default_context(): 13a. 和 *note
     SSLContext.load_default_certs(): f54. 的選項。此值表示該語境可能會
     用於驗證網頁伺服器 (因此它將用於建立用戶端 socket）。

     在 3.4 版被加入.

 -- 資料: Purpose.CLIENT_AUTH

     *note create_default_context(): 13a. 和 *note
     SSLContext.load_default_certs(): f54. 的選項。此值表示該語境可能會
     用於驗證網頁用戶端 (因此，它將用於建立伺服器端的 socket）。

     在 3.4 版被加入.

 -- 類別: ssl.SSLErrorNumber

     *note enum.IntEnum: c86. 為 SSL_ERROR_* 常數中的一個集合。

     在 3.6 版被加入.

 -- 類別: ssl.TLSVersion

     用於 *note SSLContext.maximum_version: b28. 和 *note
     SSLContext.minimum_version: b27. 的 SSL 和 TLS 版本 *note
     enum.IntEnum: c86. 集合。

     在 3.7 版被加入.

 -- 屬性: TLSVersion.MINIMUM_SUPPORTED

 -- 屬性: TLSVersion.MAXIMUM_SUPPORTED

     最低或最高支援的 SSL 或 TLS 版本。這些是特殊常數。它們的值並不反映
     可用的最低和最高 TLS/SSL 版本。

 -- 屬性: TLSVersion.SSLv3

 -- 屬性: TLSVersion.TLSv1

 -- 屬性: TLSVersion.TLSv1_1

 -- 屬性: TLSVersion.TLSv1_2

 -- 屬性: TLSVersion.TLSv1_3

     SSL 3.0 到 TLS 1.3。

     在 3.10 版之後被棄用: 除了 *note TLSVersion.TLSv1_2: 32c4. 和 *note
     TLSVersion.TLSv1_3: 32c5. 之外，所有的 *note TLSVersion: 32be. 成員
     都已被棄用。

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc7301.html

   (2) https://datatracker.ietf.org/doc/html/rfc6066.html

   (3) 
https://en.wikipedia.org/wiki/Application-Layer_Protocol_Negotiation

   (4) https://datatracker.ietf.org/doc/html/rfc5246.html

   (5) 
https://www.iana.org/assignments/tls-parameters/tls-parameters.xml#tls-parameters-6


File: python.info,  Node: SSL Sockets,  Next: SSL Contexts,  Prev: 函式、常數與例外,  Up: ssl --- socket 物件的 TLS/SSL 包裝器

5.18.3.8 SSL Sockets
....................

 -- 類別: ssl.SSLSocket (socket.socket)

     SSL sockets 提供以下 *note Socket 物件: 326c. 方法：

        - *note accept(): d48.

        - *note bind(): 14a8.

        - *note close(): cea.

        - *note connect(): d49.

        - *note detach(): 11b4.

        - *note fileno(): 327a.

        - *note getpeername(): 31c0.、*note getsockname(): 31c1.

        - *note getsockopt(): c7c.、*note setsockopt(): c7d.

        - *note gettimeout(): 327b.、*note settimeout(): 3239.、*note
          setblocking(): 2a28.

        - *note listen(): e00.

        - *note makefile(): 1137.

        - *note recv(): d4a.、*note recv_into(): 12b1. （但不允許傳遞非
          零的 ‘flags’ 引數）

        - *note send(): d4d.、*note sendall(): d4e. （同樣不允許傳遞非零
          的 ‘flags’ 引數）

        - *note sendfile(): dff. （但 *note os.sendfile: ab2. 只能用於純
          文本 sockets，其餘則會使用 *note send(): d4d.）

        - *note shutdown(): 3269.

     然而，由於 SSL（和 TLS）協定在 TCP 之上有自己的框架，因此在某些方面
     ，SSL sockets 的抽象可能會與普通操作系統級別的 sockets 規範有所不同
     。特別是請參閱*note 關於 non-blocking sockets 的說明: 3291.。

     *note SSLSocket: 88f. 的實例必須使用 *note
     SSLContext.wrap_socket(): 4c9. 方法建立。

     在 3.5 版的變更: 新增 ‘sendfile()’ 方法。

     在 3.5 版的變更: ‘shutdown()’ 不會在每次接收或發送位元組時重置
     socket 超時時間。現在，socket 超時時間是關閉操作的最大總持續時間。

     在 3.6 版之後被棄用: 直接建立 *note SSLSocket: 88f. 實例的方式已被
     棄用，請使用 *note SSLContext.wrap_socket(): 4c9. 來包裝 socket。

     在 3.7 版的變更: *note SSLSocket: 88f. 實例必須使用 *note
     wrap_socket(): 4c9. 建立。在較早的版本中可以直接建立實例，但這從未
     被記錄或正式支援。

     在 3.10 版的變更: Python 現在內部使用了 ‘SSL_read_ex’ 和
     ‘SSL_write_ex’ 函式。這些函式支援讀取和寫入大於 2 GB 的資料。寫入零
     長度的資料不再會導致協定違規錯誤。

SSL sockets 還具有以下附加方法和屬性：

 -- 方法: SSLSocket.read (len=1024, buffer=None)

     從 SSL socket 讀取 'len' 位元組的資料，並將結果以 ‘bytes’ 實例的形
     式回傳。如果指定了 'buffer'，則將資料讀入緩衝區，並回傳讀取的位元組
     。

     如果 socket 是*note 非阻塞的: 3291.則會引發 *note SSLWantReadError:
     e0b. 或 *note SSLWantWriteError: e0c. 並且讀取操作將會被阻塞。

     由於在任何時刻都可能發生重新協商，呼叫 *note read(): e10. 也可能觸
     發寫入操作。

     在 3.5 版的變更: 當接收或發送位元組時，socket 的超時時間將不再重置
     。現在，socket 超時時間是讀取最多 'len' 位元組的總最大持續時間。

     在 3.6 版之後被棄用: 請改用 ‘recv()’ 來替換掉 *note read(): e10.。

 -- 方法: SSLSocket.write (buf)

     將 'buf' 寫入 SSL socket 並回傳寫入的位元組數量。'buf' 引數必須是支
     援緩衝區介面的物件。

     如果 socket 是*note 非阻塞的: 3291.則會引發 *note SSLWantReadError:
     e0b. 或 *note SSLWantWriteError: e0c. 並且寫入操作將會被阻塞。

     由於在任何時刻都可能發生重新協商，呼叫 *note write(): e11. 也可能觸
     發讀取操作。

     在 3.5 版的變更: 當接收或發送位元組時，socket 的超時時間將不再重置
     。現在，socket 超時時間是寫入 'buf' 的總最大持續時間。

     在 3.6 版之後被棄用: 請改用 ‘send()’ 來替換掉 *note write(): e11.。

     備註: The *note read(): e10. and *note write(): e11. methods are
     the low-level methods that read and write unencrypted,
     application-level data and decrypt/encrypt it to encrypted,
     wire-level data.  These methods require an active SSL connection,
     i.e.  the handshake was completed and *note SSLSocket.unwrap():
     32c7. was not called.

     Normally you should use the socket API methods like *note recv():
     d4a. and *note send(): d4d. instead of these methods.

 -- 方法: SSLSocket.do_handshake ()

     Perform the SSL setup handshake.

     在 3.4 版的變更: The handshake method also performs
     ‘match_hostname()’ when the *note check_hostname: 329f. attribute
     of the socket's *note context: 32c8. is true.

     在 3.5 版的變更: The socket timeout is no longer reset each time
     bytes are received or sent.  The socket timeout is now the maximum
     total duration of the handshake.

     在 3.7 版的變更: Hostname or IP address is matched by OpenSSL
     during handshake.  The function ‘match_hostname()’ is no longer
     used.  In case OpenSSL refuses a hostname or IP address, the
     handshake is aborted early and a TLS alert message is sent to the
     peer.

 -- 方法: SSLSocket.getpeercert (binary_form=False)

     If there is no certificate for the peer on the other end of the
     connection, return ‘None’.  If the SSL handshake hasn't been done
     yet, raise *note ValueError: 1e7.

     If the ‘binary_form’ parameter is *note False: adb, and a
     certificate was received from the peer, this method returns a *note
     dict: 23b. instance.  If the certificate was not validated, the
     dict is empty.  If the certificate was validated, it returns a dict
     with several keys, amongst them ‘subject’ (the principal for which
     the certificate was issued) and ‘issuer’ (the principal issuing the
     certificate).  If a certificate contains an instance of the
     'Subject Alternative Name' extension (see RFC 3280(1)), there will
     also be a ‘subjectAltName’ key in the dictionary.

     The ‘subject’ and ‘issuer’ fields are tuples containing the
     sequence of relative distinguished names (RDNs) given in the
     certificate's data structure for the respective fields, and each
     RDN is a sequence of name-value pairs.  Here is a real-world
     example:

          {'issuer': ((('countryName', 'IL'),),
                      (('organizationName', 'StartCom Ltd.'),),
                      (('organizationalUnitName',
                        'Secure Digital Certificate Signing'),),
                      (('commonName',
                        'StartCom Class 2 Primary Intermediate Server CA'),)),
           'notAfter': 'Nov 22 08:15:19 2013 GMT',
           'notBefore': 'Nov 21 03:09:52 2011 GMT',
           'serialNumber': '95F0',
           'subject': ((('description', '571208-SLe257oHY9fVQ07Z'),),
                       (('countryName', 'US'),),
                       (('stateOrProvinceName', 'California'),),
                       (('localityName', 'San Francisco'),),
                       (('organizationName', 'Electronic Frontier Foundation, Inc.'),),
                       (('commonName', '*.eff.org'),),
                       (('emailAddress', 'hostmaster@eff.org'),)),
           'subjectAltName': (('DNS', '*.eff.org'), ('DNS', 'eff.org')),
           'version': 3}

     If the ‘binary_form’ parameter is *note True: bb4, and a
     certificate was provided, this method returns the DER-encoded form
     of the entire certificate as a sequence of bytes, or *note None:
     61b. if the peer did not provide a certificate.  Whether the peer
     provides a certificate depends on the SSL socket's role:

        * for a client SSL socket, the server will always provide a
          certificate, regardless of whether validation was required;

        * for a server SSL socket, the client will only provide a
          certificate when requested by the server; therefore *note
          getpeercert(): f5a. will return *note None: 61b. if you used
          *note CERT_NONE: 329d. (rather than *note CERT_OPTIONAL: 329e.
          or *note CERT_REQUIRED: 328c.).

     請見 *note SSLContext.check_hostname: 329f.。

     在 3.2 版的變更: The returned dictionary includes additional items
     such as ‘issuer’ and ‘notBefore’.

     在 3.4 版的變更: *note ValueError: 1e7. is raised when the
     handshake isn't done.  The returned dictionary includes additional
     X509v3 extension items such as ‘crlDistributionPoints’, ‘caIssuers’
     and ‘OCSP’ URIs.

     在 3.9 版的變更: IPv6 address strings no longer have a trailing new
     line.

 -- 方法: SSLSocket.get_verified_chain ()

     Returns verified certificate chain provided by the other end of the
     SSL channel as a list of DER-encoded bytes.  If certificate
     verification was disabled method acts the same as *note
     get_unverified_chain(): 14d0.

     在 3.13 版被加入.

 -- 方法: SSLSocket.get_unverified_chain ()

     Returns raw certificate chain provided by the other end of the SSL
     channel as a list of DER-encoded bytes.

     在 3.13 版被加入.

 -- 方法: SSLSocket.cipher ()

     Returns a three-value tuple containing the name of the cipher being
     used, the version of the SSL protocol that defines its use, and the
     number of secret bits being used.  If no connection has been
     established, returns ‘None’.

 -- 方法: SSLSocket.shared_ciphers ()

     Return the list of ciphers available in both the client and server.
     Each entry of the returned list is a three-value tuple containing
     the name of the cipher, the version of the SSL protocol that
     defines its use, and the number of secret bits the cipher uses.
     *note shared_ciphers(): e0e. returns ‘None’ if no connection has
     been established or the socket is a client socket.

     在 3.5 版被加入.

 -- 方法: SSLSocket.compression ()

     Return the compression algorithm being used as a string, or ‘None’
     if the connection isn't compressed.

     If the higher-level protocol supports its own compression
     mechanism, you can use *note OP_NO_COMPRESSION: 10df. to disable
     SSL-level compression.

     在 3.3 版被加入.

 -- 方法: SSLSocket.get_channel_binding (cb_type='tls-unique')

     Get channel binding data for current connection, as a bytes object.
     Returns ‘None’ if not connected or the handshake has not been
     completed.

     The 'cb_type' parameter allow selection of the desired channel
     binding type.  Valid channel binding types are listed in the *note
     CHANNEL_BINDING_TYPES: 32b9. list.  Currently only the 'tls-unique'
     channel binding, defined by RFC 5929(2), is supported.  *note
     ValueError: 1e7. will be raised if an unsupported channel binding
     type is requested.

     在 3.3 版被加入.

 -- 方法: SSLSocket.selected_alpn_protocol ()

     Return the protocol that was selected during the TLS handshake.  If
     *note SSLContext.set_alpn_protocols(): e06. was not called, if the
     other party does not support ALPN, if this socket does not support
     any of the client's proposed protocols, or if the handshake has not
     happened yet, ‘None’ is returned.

     在 3.5 版被加入.

 -- 方法: SSLSocket.selected_npn_protocol ()

     Return the higher-level protocol that was selected during the
     TLS/SSL handshake.  If *note SSLContext.set_npn_protocols(): 2d3.
     was not called, or if the other party does not support NPN, or if
     the handshake has not yet happened, this will return ‘None’.

     在 3.3 版被加入.

     在 3.10 版之後被棄用: NPN has been superseded by ALPN

 -- 方法: SSLSocket.unwrap ()

     Performs the SSL shutdown handshake, which removes the TLS layer
     from the underlying socket, and returns the underlying socket
     object.  This can be used to go from encrypted operation over a
     connection to unencrypted.  The returned socket should always be
     used for further communication with the other side of the
     connection, rather than the original socket.

 -- 方法: SSLSocket.verify_client_post_handshake ()

     Requests post-handshake authentication (PHA) from a TLS 1.3 client.
     PHA can only be initiated for a TLS 1.3 connection from a
     server-side socket, after the initial TLS handshake and with PHA
     enabled on both sides, see *note SSLContext.post_handshake_auth:
     9d5.

     The method does not perform a cert exchange immediately.  The
     server-side sends a CertificateRequest during the next write event
     and expects the client to respond with a certificate on the next
     read event.

     If any precondition isn't met (e.g.  not TLS 1.3, PHA not enabled),
     an *note SSLError: 1212. is raised.

          備註: Only available with OpenSSL 1.1.1 and TLS 1.3 enabled.
          Without TLS 1.3 support, the method raises *note
          NotImplementedError: 20d.

     在 3.8 版被加入.

 -- 方法: SSLSocket.version ()

     Return the actual SSL protocol version negotiated by the connection
     as a string, or ‘None’ if no secure connection is established.  As
     of this writing, possible return values include ‘"SSLv2"’,
     ‘"SSLv3"’, ‘"TLSv1"’, ‘"TLSv1.1"’ and ‘"TLSv1.2"’.  Recent OpenSSL
     versions may define more return values.

     在 3.5 版被加入.

 -- 方法: SSLSocket.pending ()

     Returns the number of already decrypted bytes available for read,
     pending on the connection.

 -- 屬性: SSLSocket.context

     The *note SSLContext: 276. object this SSL socket is tied to.

     在 3.2 版被加入.

 -- 屬性: SSLSocket.server_side

     A boolean which is ‘True’ for server-side sockets and ‘False’ for
     client-side sockets.

     在 3.2 版被加入.

 -- 屬性: SSLSocket.server_hostname

     Hostname of the server: *note str: 3f2. type, or ‘None’ for
     server-side socket or if the hostname was not specified in the
     constructor.

     在 3.2 版被加入.

     在 3.7 版的變更: The attribute is now always ASCII text.  When
     ‘server_hostname’ is an internationalized domain name (IDN), this
     attribute now stores the A-label form (‘"xn--pythn-mua.org"’),
     rather than the U-label form (‘"pythön.org"’).

 -- 屬性: SSLSocket.session

     The *note SSLSession: c84. for this SSL connection.  The session is
     available for client and server side sockets after the TLS
     handshake has been performed.  For client sockets the session can
     be set before *note do_handshake(): e0f. has been called to reuse a
     session.

     在 3.6 版被加入.

 -- 屬性: SSLSocket.session_reused

     在 3.6 版被加入.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc3280.html

   (2) https://datatracker.ietf.org/doc/html/rfc5929.html


File: python.info,  Node: SSL Contexts,  Next: Certificates,  Prev: SSL Sockets,  Up: ssl --- socket 物件的 TLS/SSL 包裝器

5.18.3.9 SSL Contexts
.....................

在 3.2 版被加入.

An SSL context holds various data longer-lived than single SSL
connections, such as SSL configuration options, certificate(s) and
private key(s).  It also manages a cache of SSL sessions for server-side
sockets, in order to speed up repeated connections from the same
clients.

 -- 類別: ssl.SSLContext (protocol=None)

     Create a new SSL context.  You may pass 'protocol' which must be
     one of the ‘PROTOCOL_*’ constants defined in this module.  The
     parameter specifies which version of the SSL protocol to use.
     Typically, the server chooses a particular protocol version, and
     the client must adapt to the server's choice.  Most of the versions
     are not interoperable with the other versions.  If not specified,
     the default is *note PROTOCOL_TLS: 328e.; it provides the most
     compatibility with other versions.

     Here's a table showing which versions in a client (down the side)
     can connect to which versions in a server (along the top):

     'client' / 'server'          'SSLv2'          'SSLv3'          'TLS' (1)         'TLSv1'       'TLSv1.1'       'TLSv1.2'
                                                                                                                    
                                                                                                                    
     'SSLv2'                      yes              no               no (2)            no            no              no
                                                                                                                    
                                                                                                                    
     'SSLv3'                      no               yes              no (3)            no            no              no
                                                                                                                    
                                                                                                                    
     'TLS' ('SSLv23') (4)         no (5)           no (6)           yes               yes           yes             yes
                                                                                                                    
                                                                                                                    
     'TLSv1'                      no               no               yes               yes           no              no
                                                                                                                    
                                                                                                                    
     'TLSv1.1'                    no               no               yes               no            yes             no
                                                                                                                    
                                                                                                                    
     'TLSv1.2'                    no               no               yes               no            no              yes
                                                                                                                    

     註解
     ....

     也參考
     ......

     *note create_default_context(): 13a. lets the *note ssl: bb. module
     choose security settings for a given purpose.

     在 3.6 版的變更: The context is created with secure default values.
     The options *note OP_NO_COMPRESSION: 10df, *note
     OP_CIPHER_SERVER_PREFERENCE: 10e2, *note OP_SINGLE_DH_USE: 32aa,
     *note OP_SINGLE_ECDH_USE: 32ab, *note OP_NO_SSLv2: 7dd, and *note
     OP_NO_SSLv3: 7de. (except for *note PROTOCOL_SSLv3: 3299.) are set
     by default.  The initial cipher suite list contains only ‘HIGH’
     ciphers, no ‘NULL’ ciphers and no ‘MD5’ ciphers.

     在 3.10 版之後被棄用: *note SSLContext: 276. without protocol
     argument is deprecated.  The context class will either require
     *note PROTOCOL_TLS_CLIENT: 815. or *note PROTOCOL_TLS_SERVER: 816.
     protocol in the future.

     在 3.10 版的變更: The default cipher suites now include only secure
     AES and ChaCha20 ciphers with forward secrecy and security level 2.
     RSA and DH keys with less than 2048 bits and ECC keys with less
     than 224 bits are prohibited.  *note PROTOCOL_TLS: 328e, *note
     PROTOCOL_TLS_CLIENT: 815, and *note PROTOCOL_TLS_SERVER: 816. use
     TLS 1.2 as minimum TLS version.

          備註: *note SSLContext: 276. only supports limited mutation
          once it has been used by a connection.  Adding new
          certificates to the internal trust store is allowed, but
          changing ciphers, verification settings, or mTLS certificates
          may result in surprising behavior.

          備註: *note SSLContext: 276. is designed to be shared and used
          by multiple connections.  Thus, it is thread-safe as long as
          it is not reconfigured after being used by a connection.

*note SSLContext: 276. objects have the following methods and
attributes:

 -- 方法: SSLContext.cert_store_stats ()

     Get statistics about quantities of loaded X.509 certificates, count
     of X.509 certificates flagged as CA certificates and certificate
     revocation lists as dictionary.

     Example for a context with one CA cert and one other cert:

          >>> context.cert_store_stats()
          {'crl': 0, 'x509_ca': 1, 'x509': 2}

     在 3.4 版被加入.

 -- 方法: SSLContext.load_cert_chain (certfile, keyfile=None,
          password=None)

     Load a private key and the corresponding certificate.  The
     'certfile' string must be the path to a single file in PEM format
     containing the certificate as well as any number of CA certificates
     needed to establish the certificate's authenticity.  The 'keyfile'
     string, if present, must point to a file containing the private
     key.  Otherwise the private key will be taken from 'certfile' as
     well.  See the discussion of *note Certificates: 32ce. for more
     information on how the certificate is stored in the 'certfile'.

     The 'password' argument may be a function to call to get the
     password for decrypting the private key.  It will only be called if
     the private key is encrypted and a password is necessary.  It will
     be called with no arguments, and it should return a string, bytes,
     or bytearray.  If the return value is a string it will be encoded
     as UTF-8 before using it to decrypt the key.  Alternatively a
     string, bytes, or bytearray value may be supplied directly as the
     'password' argument.  It will be ignored if the private key is not
     encrypted and no password is needed.

     If the 'password' argument is not specified and a password is
     required, OpenSSL's built-in password prompting mechanism will be
     used to interactively prompt the user for a password.

     An *note SSLError: 1212. is raised if the private key doesn't match
     with the certificate.

     在 3.3 版的變更: New optional argument 'password'.

 -- 方法: SSLContext.load_default_certs (purpose=Purpose.SERVER_AUTH)

     Load a set of default "certification authority" (CA) certificates
     from default locations.  On Windows it loads CA certs from the ‘CA’
     and ‘ROOT’ system stores.  On all systems it calls *note
     SSLContext.set_default_verify_paths(): f4d.  In the future the
     method may load CA certificates from other locations, too.

     The 'purpose' flag specifies what kind of CA certificates are
     loaded.  The default settings *note Purpose.SERVER_AUTH: f55. loads
     certificates, that are flagged and trusted for TLS web server
     authentication (client side sockets).  *note Purpose.CLIENT_AUTH:
     f56. loads CA certificates for client certificate verification on
     the server side.

     在 3.4 版被加入.

 -- 方法: SSLContext.load_verify_locations (cafile=None, capath=None,
          cadata=None)

     Load a set of "certification authority" (CA) certificates used to
     validate other peers' certificates when *note verify_mode: 328b. is
     other than *note CERT_NONE: 329d.  At least one of 'cafile' or
     'capath' must be specified.

     This method can also load certification revocation lists (CRLs) in
     PEM or DER format.  In order to make use of CRLs, *note
     SSLContext.verify_flags: f50. must be configured properly.

     The 'cafile' string, if present, is the path to a file of
     concatenated CA certificates in PEM format.  See the discussion of
     *note Certificates: 32ce. for more information about how to arrange
     the certificates in this file.

     The 'capath' string, if present, is the path to a directory
     containing several CA certificates in PEM format, following an
     OpenSSL specific layout(7).

     The 'cadata' object, if present, is either an ASCII string of one
     or more PEM-encoded certificates or a *note bytes-like object: cd4.
     of DER-encoded certificates.  Like with 'capath' extra lines around
     PEM-encoded certificates are ignored but at least one certificate
     must be present.

     在 3.4 版的變更: New optional argument 'cadata'

 -- 方法: SSLContext.get_ca_certs (binary_form=False)

     Get a list of loaded "certification authority" (CA) certificates.
     If the ‘binary_form’ parameter is *note False: adb. each list entry
     is a dict like the output of *note SSLSocket.getpeercert(): f5a.
     Otherwise the method returns a list of DER-encoded certificates.
     The returned list does not contain certificates from 'capath'
     unless a certificate was requested and loaded by a SSL connection.

          備註: Certificates in a capath directory aren't loaded unless
          they have been used at least once.

     在 3.4 版被加入.

 -- 方法: SSLContext.get_ciphers ()

     Get a list of enabled ciphers.  The list is in order of cipher
     priority.  See *note SSLContext.set_ciphers(): 32cf.

     範例：

          >>> ctx = ssl.SSLContext(ssl.PROTOCOL_SSLv23)
          >>> ctx.set_ciphers('ECDHE+AESGCM:!ECDSA')
          >>> ctx.get_ciphers()
          [{'aead': True,
            'alg_bits': 256,
            'auth': 'auth-rsa',
            'description': 'ECDHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH     Au=RSA  '
                           'Enc=AESGCM(256) Mac=AEAD',
            'digest': None,
            'id': 50380848,
            'kea': 'kx-ecdhe',
            'name': 'ECDHE-RSA-AES256-GCM-SHA384',
            'protocol': 'TLSv1.2',
            'strength_bits': 256,
            'symmetric': 'aes-256-gcm'},
           {'aead': True,
            'alg_bits': 128,
            'auth': 'auth-rsa',
            'description': 'ECDHE-RSA-AES128-GCM-SHA256 TLSv1.2 Kx=ECDH     Au=RSA  '
                           'Enc=AESGCM(128) Mac=AEAD',
            'digest': None,
            'id': 50380847,
            'kea': 'kx-ecdhe',
            'name': 'ECDHE-RSA-AES128-GCM-SHA256',
            'protocol': 'TLSv1.2',
            'strength_bits': 128,
            'symmetric': 'aes-128-gcm'}]

     在 3.6 版被加入.

 -- 方法: SSLContext.set_default_verify_paths ()

     Load a set of default "certification authority" (CA) certificates
     from a filesystem path defined when building the OpenSSL library.
     Unfortunately, there's no easy way to know whether this method
     succeeds: no error is returned if no certificates are to be found.
     When the OpenSSL library is provided as part of the operating
     system, though, it is likely to be configured properly.

 -- 方法: SSLContext.set_ciphers (ciphers)

     Set the available ciphers for sockets created with this context.
     It should be a string in the OpenSSL cipher list format(8).  If no
     cipher can be selected (because compile-time options or other
     configuration forbids use of all the specified ciphers), an *note
     SSLError: 1212. will be raised.

          備註: when connected, the *note SSLSocket.cipher(): 31c2.
          method of SSL sockets will give the currently selected cipher.

          TLS 1.3 cipher suites cannot be disabled with *note
          set_ciphers(): 32cf.

 -- 方法: SSLContext.set_alpn_protocols (protocols)

     Specify which protocols the socket should advertise during the
     SSL/TLS handshake.  It should be a list of ASCII strings, like
     ‘['http/1.1', 'spdy/2']’, ordered by preference.  The selection of
     a protocol will happen during the handshake, and will play out
     according to RFC 7301(9).  After a successful handshake, the *note
     SSLSocket.selected_alpn_protocol(): e07. method will return the
     agreed-upon protocol.

     This method will raise *note NotImplementedError: 20d. if *note
     HAS_ALPN: e08. is ‘False’.

     在 3.5 版被加入.

 -- 方法: SSLContext.set_npn_protocols (protocols)

     Specify which protocols the socket should advertise during the
     SSL/TLS handshake.  It should be a list of strings, like
     ‘['http/1.1', 'spdy/2']’, ordered by preference.  The selection of
     a protocol will happen during the handshake, and will play out
     according to the Application Layer Protocol Negotiation(10).  After
     a successful handshake, the *note
     SSLSocket.selected_npn_protocol(): 817. method will return the
     agreed-upon protocol.

     This method will raise *note NotImplementedError: 20d. if *note
     HAS_NPN: 32b2. is ‘False’.

     在 3.3 版被加入.

     在 3.10 版之後被棄用: NPN has been superseded by ALPN

 -- 屬性: SSLContext.sni_callback

     Register a callback function that will be called after the TLS
     Client Hello handshake message has been received by the SSL/TLS
     server when the TLS client specifies a server name indication.  The
     server name indication mechanism is specified in RFC 6066(11)
     section 3 - Server Name Indication.

     Only one callback can be set per ‘SSLContext’.  If 'sni_callback'
     is set to ‘None’ then the callback is disabled.  Calling this
     function a subsequent time will disable the previously registered
     callback.

     The callback function will be called with three arguments; the
     first being the *note ssl.SSLSocket: 88f, the second is a string
     that represents the server name that the client is intending to
     communicate (or *note None: 61b. if the TLS Client Hello does not
     contain a server name) and the third argument is the original *note
     SSLContext: 276.  The server name argument is text.  For
     internationalized domain name, the server name is an IDN A-label
     (‘"xn--pythn-mua.org"’).

     A typical use of this callback is to change the *note
     ssl.SSLSocket: 88f.'s *note SSLSocket.context: 32c8. attribute to a
     new object of type *note SSLContext: 276. representing a
     certificate chain that matches the server name.

     Due to the early negotiation phase of the TLS connection, only
     limited methods and attributes are usable like *note
     SSLSocket.selected_alpn_protocol(): e07. and *note
     SSLSocket.context: 32c8.  The *note SSLSocket.getpeercert(): f5a,
     *note SSLSocket.get_verified_chain(): 14cf, *note
     SSLSocket.get_unverified_chain(): 14d0. *note SSLSocket.cipher():
     31c2. and *note SSLSocket.compression(): 10de. methods require that
     the TLS connection has progressed beyond the TLS Client Hello and
     therefore will not return meaningful values nor can they be called
     safely.

     The 'sni_callback' function must return ‘None’ to allow the TLS
     negotiation to continue.  If a TLS failure is required, a constant
     *note ALERT_DESCRIPTION_*: 32bb. can be returned.  Other return
     values will result in a TLS fatal error with *note
     ALERT_DESCRIPTION_INTERNAL_ERROR: 32bb.

     If an exception is raised from the 'sni_callback' function the TLS
     connection will terminate with a fatal TLS alert message *note
     ALERT_DESCRIPTION_HANDSHAKE_FAILURE: 32ba.

     This method will raise *note NotImplementedError: 20d. if the
     OpenSSL library had OPENSSL_NO_TLSEXT defined when it was built.

     在 3.7 版被加入.

 -- 屬性: SSLContext.set_servername_callback (server_name_callback)

     This is a legacy API retained for backwards compatibility.  When
     possible, you should use *note sni_callback: 17d8. instead.  The
     given 'server_name_callback' is similar to 'sni_callback', except
     that when the server hostname is an IDN-encoded internationalized
     domain name, the 'server_name_callback' receives a decoded U-label
     (‘"pythön.org"’).

     If there is a decoding error on the server name, the TLS connection
     will terminate with an *note ALERT_DESCRIPTION_INTERNAL_ERROR:
     32bb. fatal TLS alert message to the client.

     在 3.4 版被加入.

 -- 方法: SSLContext.load_dh_params (dhfile)

     Load the key generation parameters for Diffie-Hellman (DH) key
     exchange.  Using DH key exchange improves forward secrecy at the
     expense of computational resources (both on the server and on the
     client).  The 'dhfile' parameter should be the path to a file
     containing DH parameters in PEM format.

     This setting doesn't apply to client sockets.  You can also use the
     *note OP_SINGLE_DH_USE: 32aa. option to further improve security.

     在 3.3 版被加入.

 -- 方法: SSLContext.set_ecdh_curve (curve_name)

     Set the curve name for Elliptic Curve-based Diffie-Hellman (ECDH)
     key exchange.  ECDH is significantly faster than regular DH while
     arguably as secure.  The 'curve_name' parameter should be a string
     describing a well-known elliptic curve, for example ‘prime256v1’
     for a widely supported curve.

     This setting doesn't apply to client sockets.  You can also use the
     *note OP_SINGLE_ECDH_USE: 32ab. option to further improve security.

     This method is not available if *note HAS_ECDH: 32b0. is ‘False’.

     在 3.3 版被加入.

     也參考
     ......

     SSL/TLS & Perfect Forward Secrecy(12)

          Vincent Bernat.

 -- 方法: SSLContext.wrap_socket (sock, server_side=False,
          do_handshake_on_connect=True, suppress_ragged_eofs=True,
          server_hostname=None, session=None)

     Wrap an existing Python socket 'sock' and return an instance of
     *note SSLContext.sslsocket_class: 32d0. (default *note SSLSocket:
     88f.).  The returned SSL socket is tied to the context, its
     settings and certificates.  'sock' must be a *note SOCK_STREAM:
     1286. socket; other socket types are unsupported.

     The parameter ‘server_side’ is a boolean which identifies whether
     server-side or client-side behavior is desired from this socket.

     For client-side sockets, the context construction is lazy; if the
     underlying socket isn't connected yet, the context construction
     will be performed after ‘connect()’ is called on the socket.  For
     server-side sockets, if the socket has no remote peer, it is
     assumed to be a listening socket, and the server-side SSL wrapping
     is automatically performed on client connections accepted via the
     ‘accept()’ method.  The method may raise *note SSLError: 1212.

     On client connections, the optional parameter 'server_hostname'
     specifies the hostname of the service which we are connecting to.
     This allows a single server to host multiple SSL-based services
     with distinct certificates, quite similarly to HTTP virtual hosts.
     Specifying 'server_hostname' will raise a *note ValueError: 1e7. if
     'server_side' is true.

     The parameter ‘do_handshake_on_connect’ specifies whether to do the
     SSL handshake automatically after doing a ‘socket.connect()’, or
     whether the application program will call it explicitly, by
     invoking the *note SSLSocket.do_handshake(): e0f. method.  Calling
     *note SSLSocket.do_handshake(): e0f. explicitly gives the program
     control over the blocking behavior of the socket I/O involved in
     the handshake.

     The parameter ‘suppress_ragged_eofs’ specifies how the
     ‘SSLSocket.recv()’ method should signal unexpected EOF from the
     other end of the connection.  If specified as *note True: bb4. (the
     default), it returns a normal EOF (an empty bytes object) in
     response to unexpected EOF errors raised from the underlying
     socket; if *note False: adb, it will raise the exceptions back to
     the caller.

     'session', see *note session: 32cb.

     To wrap an *note SSLSocket: 88f. in another *note SSLSocket: 88f,
     use *note SSLContext.wrap_bio(): b26.

     在 3.5 版的變更: Always allow a server_hostname to be passed, even
     if OpenSSL does not have SNI.

     在 3.6 版的變更: 新增 'session' 引數。

     在 3.7 版的變更: The method returns an instance of *note
     SSLContext.sslsocket_class: 32d0. instead of hard-coded *note
     SSLSocket: 88f.

 -- 屬性: SSLContext.sslsocket_class

     The return type of *note SSLContext.wrap_socket(): 4c9, defaults to
     *note SSLSocket: 88f.  The attribute can be overridden on instance
     of class in order to return a custom subclass of *note SSLSocket:
     88f.

     在 3.7 版被加入.

 -- 方法: SSLContext.wrap_bio (incoming, outgoing, server_side=False,
          server_hostname=None, session=None)

     Wrap the BIO objects 'incoming' and 'outgoing' and return an
     instance of *note SSLContext.sslobject_class: 32d1. (default *note
     SSLObject: b25.).  The SSL routines will read input data from the
     incoming BIO and write data to the outgoing BIO.

     The 'server_side', 'server_hostname' and 'session' parameters have
     the same meaning as in *note SSLContext.wrap_socket(): 4c9.

     在 3.6 版的變更: 新增 'session' 引數。

     在 3.7 版的變更: The method returns an instance of *note
     SSLContext.sslobject_class: 32d1. instead of hard-coded *note
     SSLObject: b25.

 -- 屬性: SSLContext.sslobject_class

     The return type of *note SSLContext.wrap_bio(): b26, defaults to
     *note SSLObject: b25.  The attribute can be overridden on instance
     of class in order to return a custom subclass of *note SSLObject:
     b25.

     在 3.7 版被加入.

 -- 方法: SSLContext.session_stats ()

     Get statistics about the SSL sessions created or managed by this
     context.  A dictionary is returned which maps the names of each
     piece of information(13) to their numeric values.  For example,
     here is the total number of hits and misses in the session cache
     since the context was created:

          >>> stats = context.session_stats()
          >>> stats['hits'], stats['misses']
          (0, 0)

 -- 屬性: SSLContext.check_hostname

     Whether to match the peer cert's hostname in *note
     SSLSocket.do_handshake(): e0f.  The context's *note verify_mode:
     328b. must be set to *note CERT_OPTIONAL: 329e. or *note
     CERT_REQUIRED: 328c, and you must pass 'server_hostname' to *note
     wrap_socket(): 4c9. in order to match the hostname.  Enabling
     hostname checking automatically sets *note verify_mode: 328b. from
     *note CERT_NONE: 329d. to *note CERT_REQUIRED: 328c.  It cannot be
     set back to *note CERT_NONE: 329d. as long as hostname checking is
     enabled.  The *note PROTOCOL_TLS_CLIENT: 815. protocol enables
     hostname checking by default.  With other protocols, hostname
     checking must be enabled explicitly.

     範例：

          import socket, ssl

          context = ssl.SSLContext(ssl.PROTOCOL_TLSv1_2)
          context.verify_mode = ssl.CERT_REQUIRED
          context.check_hostname = True
          context.load_default_certs()

          s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
          ssl_sock = context.wrap_socket(s, server_hostname='www.verisign.com')
          ssl_sock.connect(('www.verisign.com', 443))

     在 3.4 版被加入.

     在 3.7 版的變更: *note verify_mode: 328b. is now automatically
     changed to *note CERT_REQUIRED: 328c. when hostname checking is
     enabled and *note verify_mode: 328b. is *note CERT_NONE: 329d.
     Previously the same operation would have failed with a *note
     ValueError: 1e7.

 -- 屬性: SSLContext.keylog_filename

     Write TLS keys to a keylog file, whenever key material is generated
     or received.  The keylog file is designed for debugging purposes
     only.  The file format is specified by NSS and used by many traffic
     analyzers such as Wireshark.  The log file is opened in append-only
     mode.  Writes are synchronized between threads, but not between
     processes.

     在 3.8 版被加入.

 -- 屬性: SSLContext.maximum_version

     A *note TLSVersion: 32be. enum member representing the highest
     supported TLS version.  The value defaults to *note
     TLSVersion.MAXIMUM_SUPPORTED: 32c0.  The attribute is read-only for
     protocols other than *note PROTOCOL_TLS: 328e, *note
     PROTOCOL_TLS_CLIENT: 815, and *note PROTOCOL_TLS_SERVER: 816.

     The attributes *note maximum_version: b28, *note minimum_version:
     b27. and *note SSLContext.options: 7dc. all affect the supported
     SSL and TLS versions of the context.  The implementation does not
     prevent invalid combination.  For example a context with *note
     OP_NO_TLSv1_2: 32a8. in *note options: 7dc. and *note
     maximum_version: b28. set to *note TLSVersion.TLSv1_2: 32c4. will
     not be able to establish a TLS 1.2 connection.

     在 3.7 版被加入.

 -- 屬性: SSLContext.minimum_version

     Like *note SSLContext.maximum_version: b28. except it is the lowest
     supported version or *note TLSVersion.MINIMUM_SUPPORTED: 32bf.

     在 3.7 版被加入.

 -- 屬性: SSLContext.num_tickets

     Control the number of TLS 1.3 session tickets of a *note
     PROTOCOL_TLS_SERVER: 816. context.  The setting has no impact on
     TLS 1.0 to 1.2 connections.

     在 3.8 版被加入.

 -- 屬性: SSLContext.options

     An integer representing the set of SSL options enabled on this
     context.  The default value is *note OP_ALL: 32a5, but you can
     specify other options such as *note OP_NO_SSLv2: 7dd. by ORing them
     together.

     在 3.6 版的變更: *note SSLContext.options: 7dc. returns *note
     Options: 32ad. flags:

          >>> ssl.create_default_context().options
          <Options.OP_ALL|OP_NO_SSLv3|OP_NO_SSLv2|OP_NO_COMPRESSION: 2197947391>

     在 3.7 版之後被棄用: All ‘OP_NO_SSL*’ and ‘OP_NO_TLS*’ options have
     been deprecated since Python 3.7.  Use *note
     SSLContext.minimum_version: b27. and *note
     SSLContext.maximum_version: b28. instead.

 -- 屬性: SSLContext.post_handshake_auth

     Enable TLS 1.3 post-handshake client authentication.
     Post-handshake auth is disabled by default and a server can only
     request a TLS client certificate during the initial handshake.
     When enabled, a server may request a TLS client certificate at any
     time after the handshake.

     When enabled on client-side sockets, the client signals the server
     that it supports post-handshake authentication.

     When enabled on server-side sockets, *note SSLContext.verify_mode:
     328b. must be set to *note CERT_OPTIONAL: 329e. or *note
     CERT_REQUIRED: 328c, too.  The actual client cert exchange is
     delayed until *note SSLSocket.verify_client_post_handshake(): 9d6.
     is called and some I/O is performed.

     在 3.8 版被加入.

 -- 屬性: SSLContext.protocol

     The protocol version chosen when constructing the context.  This
     attribute is read-only.

 -- 屬性: SSLContext.hostname_checks_common_name

     Whether *note check_hostname: 329f. falls back to verify the cert's
     subject common name in the absence of a subject alternative name
     extension (default: true).

     在 3.7 版被加入.

     在 3.10 版的變更: The flag had no effect with OpenSSL before
     version 1.1.1l.  Python 3.8.9, 3.9.3, and 3.10 include workarounds
     for previous versions.

 -- 屬性: SSLContext.security_level

     An integer representing the security level(14) for the context.
     This attribute is read-only.

     在 3.10 版被加入.

 -- 屬性: SSLContext.verify_flags

     The flags for certificate verification operations.  You can set
     flags like *note VERIFY_CRL_CHECK_LEAF: f52. by ORing them
     together.  By default OpenSSL does neither require nor verify
     certificate revocation lists (CRLs).

     在 3.4 版被加入.

     在 3.6 版的變更: *note SSLContext.verify_flags: f50. returns *note
     VerifyFlags: 32a2. flags:

          >>> ssl.create_default_context().verify_flags
          <VerifyFlags.VERIFY_X509_TRUSTED_FIRST: 32768>

 -- 屬性: SSLContext.verify_mode

     Whether to try to verify other peers' certificates and how to
     behave if verification fails.  This attribute must be one of *note
     CERT_NONE: 329d, *note CERT_OPTIONAL: 329e. or *note CERT_REQUIRED:
     328c.

     在 3.6 版的變更: *note SSLContext.verify_mode: 328b. returns *note
     VerifyMode: 32a0. enum:

          >>> ssl.create_default_context().verify_mode
          <VerifyMode.CERT_REQUIRED: 2>

 -- 方法: SSLContext.set_psk_client_callback (callback)

     Enables TLS-PSK (pre-shared key) authentication on a client-side
     connection.

     In general, certificate based authentication should be preferred
     over this method.

     The parameter ‘callback’ is a callable object with the signature:
     ‘def callback(hint: str | None) -> tuple[str | None, bytes]’.  The
     ‘hint’ parameter is an optional identity hint sent by the server.
     The return value is a tuple in the form (client-identity, psk).
     Client-identity is an optional string which may be used by the
     server to select a corresponding PSK for the client.  The string
     must be less than or equal to ‘256’ octets when UTF-8 encoded.  PSK
     is a *note bytes-like object: cd4. representing the pre-shared key.
     Return a zero length PSK to reject the connection.

     Setting ‘callback’ to *note None: 61b. removes any existing
     callback.

          備註: When using TLS 1.3:

             - the ‘hint’ parameter is always *note None: 61b.

             - client-identity must be a non-empty string.

     Example usage:

          context = ssl.SSLContext(ssl.PROTOCOL_TLS_CLIENT)
          context.check_hostname = False
          context.verify_mode = ssl.CERT_NONE
          context.maximum_version = ssl.TLSVersion.TLSv1_2
          context.set_ciphers('PSK')

          # A simple lambda:
          psk = bytes.fromhex('c0ffee')
          context.set_psk_client_callback(lambda hint: (None, psk))

          # A table using the hint from the server:
          psk_table = { 'ServerId_1': bytes.fromhex('c0ffee'),
                        'ServerId_2': bytes.fromhex('facade')
          }
          def callback(hint):
              return 'ClientId_1', psk_table.get(hint, b'')
          context.set_psk_client_callback(callback)

     This method will raise *note NotImplementedError: 20d. if *note
     HAS_PSK: 32b8. is ‘False’.

     在 3.13 版被加入.

 -- 方法: SSLContext.set_psk_server_callback (callback,
          identity_hint=None)

     Enables TLS-PSK (pre-shared key) authentication on a server-side
     connection.

     In general, certificate based authentication should be preferred
     over this method.

     The parameter ‘callback’ is a callable object with the signature:
     ‘def callback(identity: str | None) -> bytes’.  The ‘identity’
     parameter is an optional identity sent by the client which can be
     used to select a corresponding PSK. The return value is a *note
     bytes-like object: cd4. representing the pre-shared key.  Return a
     zero length PSK to reject the connection.

     Setting ‘callback’ to *note None: 61b. removes any existing
     callback.

     The parameter ‘identity_hint’ is an optional identity hint string
     sent to the client.  The string must be less than or equal to ‘256’
     octets when UTF-8 encoded.

          備註: When using TLS 1.3 the ‘identity_hint’ parameter is not
          sent to the client.

     Example usage:

          context = ssl.SSLContext(ssl.PROTOCOL_TLS_SERVER)
          context.maximum_version = ssl.TLSVersion.TLSv1_2
          context.set_ciphers('PSK')

          # A simple lambda:
          psk = bytes.fromhex('c0ffee')
          context.set_psk_server_callback(lambda identity: psk)

          # A table using the identity of the client:
          psk_table = { 'ClientId_1': bytes.fromhex('c0ffee'),
                        'ClientId_2': bytes.fromhex('facade')
          }
          def callback(identity):
              return psk_table.get(identity, b'')
          context.set_psk_server_callback(callback, 'ServerId_1')

     This method will raise *note NotImplementedError: 20d. if *note
     HAS_PSK: 32b8. is ‘False’.

     在 3.13 版被加入.

   ---------- Footnotes ----------

   (1) TLS 1.3 protocol will be available with *note PROTOCOL_TLS: 328e.
in OpenSSL >= 1.1.1.  There is no dedicated PROTOCOL constant for just
TLS 1.3.

   (2) *note SSLContext: 276. 預設會關閉 SSLv2 的 *note OP_NO_SSLv2:
7dd.。

   (3) *note SSLContext: 276. 預設會關閉 SSLv3 的 *note OP_NO_SSLv3:
7de.。

   (4) TLS 1.3 protocol will be available with *note PROTOCOL_TLS: 328e.
in OpenSSL >= 1.1.1.  There is no dedicated PROTOCOL constant for just
TLS 1.3.

   (5) *note SSLContext: 276. 預設會關閉 SSLv2 的 *note OP_NO_SSLv2:
7dd.。

   (6) *note SSLContext: 276. 預設會關閉 SSLv3 的 *note OP_NO_SSLv3:
7de.。

   (7) 
https://www.openssl.org/docs/manmaster/man3/SSL_CTX_load_verify_locations.html

   (8) https://www.openssl.org/docs/manmaster/man1/ciphers.html

   (9) https://datatracker.ietf.org/doc/html/rfc7301.html

   (10) 
https://en.wikipedia.org/wiki/Application-Layer_Protocol_Negotiation

   (11) https://datatracker.ietf.org/doc/html/rfc6066.html

   (12) 
https://vincent.bernat.ch/en/blog/2011-ssl-perfect-forward-secrecy

   (13) 
https://www.openssl.org/docs/man1.1.1/man3/SSL_CTX_sess_number.html

   (14) 
https://www.openssl.org/docs/manmaster/man3/SSL_CTX_get_security_level.html


File: python.info,  Node: Certificates,  Next: 範例<26>,  Prev: SSL Contexts,  Up: ssl --- socket 物件的 TLS/SSL 包裝器

5.18.3.10 Certificates
......................

Certificates in general are part of a public-key / private-key system.
In this system, each 'principal', (which may be a machine, or a person,
or an organization) is assigned a unique two-part encryption key.  One
part of the key is public, and is called the 'public key'; the other
part is kept secret, and is called the 'private key'.  The two parts are
related, in that if you encrypt a message with one of the parts, you can
decrypt it with the other part, and 'only' with the other part.

A certificate contains information about two principals.  It contains
the name of a 'subject', and the subject's public key.  It also contains
a statement by a second principal, the 'issuer', that the subject is who
they claim to be, and that this is indeed the subject's public key.  The
issuer's statement is signed with the issuer's private key, which only
the issuer knows.  However, anyone can verify the issuer's statement by
finding the issuer's public key, decrypting the statement with it, and
comparing it to the other information in the certificate.  The
certificate also contains information about the time period over which
it is valid.  This is expressed as two fields, called "notBefore" and
"notAfter".

In the Python use of certificates, a client or server can use a
certificate to prove who they are.  The other side of a network
connection can also be required to produce a certificate, and that
certificate can be validated to the satisfaction of the client or server
that requires such validation.  The connection attempt can be set to
raise an exception if the validation fails.  Validation is done
automatically, by the underlying OpenSSL framework; the application need
not concern itself with its mechanics.  But the application does usually
need to provide sets of certificates to allow this process to take
place.

Python uses files to contain certificates.  They should be formatted as
"PEM" (see RFC 1422(1)), which is a base-64 encoded form wrapped with a
header line and a footer line:

     -----BEGIN CERTIFICATE-----
     ... (certificate in base64 PEM encoding) ...
     -----END CERTIFICATE-----

* Menu:

* Certificate chains::
* CA certificates::
* Combined key and certificate::
* Self-signed certificates::

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc1422.html


File: python.info,  Node: Certificate chains,  Next: CA certificates,  Up: Certificates

5.18.3.11 Certificate chains
............................

The Python files which contain certificates can contain a sequence of
certificates, sometimes called a 'certificate chain'.  This chain should
start with the specific certificate for the principal who "is" the
client or server, and then the certificate for the issuer of that
certificate, and then the certificate for the issuer of 'that'
certificate, and so on up the chain till you get to a certificate which
is 'self-signed', that is, a certificate which has the same subject and
issuer, sometimes called a 'root certificate'.  The certificates should
just be concatenated together in the certificate file.  For example,
suppose we had a three certificate chain, from our server certificate to
the certificate of the certification authority that signed our server
certificate, to the root certificate of the agency which issued the
certification authority's certificate:

     -----BEGIN CERTIFICATE-----
     ... (certificate for your server)...
     -----END CERTIFICATE-----
     -----BEGIN CERTIFICATE-----
     ... (the certificate for the CA)...
     -----END CERTIFICATE-----
     -----BEGIN CERTIFICATE-----
     ... (the root certificate for the CA's issuer)...
     -----END CERTIFICATE-----


File: python.info,  Node: CA certificates,  Next: Combined key and certificate,  Prev: Certificate chains,  Up: Certificates

5.18.3.12 CA certificates
.........................

If you are going to require validation of the other side of the
connection's certificate, you need to provide a "CA certs" file, filled
with the certificate chains for each issuer you are willing to trust.
Again, this file just contains these chains concatenated together.  For
validation, Python will use the first chain it finds in the file which
matches.  The platform's certificates file can be used by calling *note
SSLContext.load_default_certs(): f54, this is done automatically with
*note create_default_context(): 13a.


File: python.info,  Node: Combined key and certificate,  Next: Self-signed certificates,  Prev: CA certificates,  Up: Certificates

5.18.3.13 Combined key and certificate
......................................

Often the private key is stored in the same file as the certificate; in
this case, only the ‘certfile’ parameter to *note
SSLContext.load_cert_chain(): 277. needs to be passed.  If the private
key is stored with the certificate, it should come before the first
certificate in the certificate chain:

     -----BEGIN RSA PRIVATE KEY-----
     ... (private key in base64 encoding) ...
     -----END RSA PRIVATE KEY-----
     -----BEGIN CERTIFICATE-----
     ... (certificate in base64 PEM encoding) ...
     -----END CERTIFICATE-----


File: python.info,  Node: Self-signed certificates,  Prev: Combined key and certificate,  Up: Certificates

5.18.3.14 Self-signed certificates
..................................

If you are going to create a server that provides SSL-encrypted
connection services, you will need to acquire a certificate for that
service.  There are many ways of acquiring appropriate certificates,
such as buying one from a certification authority.  Another common
practice is to generate a self-signed certificate.  The simplest way to
do this is with the OpenSSL package, using something like the following:

     % openssl req -new -x509 -days 365 -nodes -out cert.pem -keyout cert.pem
     Generating a 1024 bit RSA private key
     .......++++++
     .............................++++++
     writing new private key to 'cert.pem'
     -----
     You are about to be asked to enter information that will be incorporated
     into your certificate request.
     What you are about to enter is what is called a Distinguished Name or a DN.
     There are quite a few fields but you can leave some blank
     For some fields there will be a default value,
     If you enter '.', the field will be left blank.
     -----
     Country Name (2 letter code) [AU]:US
     State or Province Name (full name) [Some-State]:MyState
     Locality Name (eg, city) []:Some City
     Organization Name (eg, company) [Internet Widgits Pty Ltd]:My Organization, Inc.
     Organizational Unit Name (eg, section) []:My Group
     Common Name (eg, YOUR name) []:myserver.mygroup.myorganization.com
     Email Address []:ops@myserver.mygroup.myorganization.com
     %

The disadvantage of a self-signed certificate is that it is its own root
certificate, and no one else will have it in their cache of known (and
trusted) root certificates.


File: python.info,  Node: 範例<26>,  Next: Notes on non-blocking sockets,  Prev: Certificates,  Up: ssl --- socket 物件的 TLS/SSL 包裝器

5.18.3.15 範例
..............

* Menu:

* Testing for SSL support::
* Client-side operation::
* Server-side operation::


File: python.info,  Node: Testing for SSL support,  Next: Client-side operation,  Up: 範例<26>

5.18.3.16 Testing for SSL support
.................................

To test for the presence of SSL support in a Python installation, user
code should use the following idiom:

     try:
         import ssl
     except ImportError:
         pass
     else:
         ...  # do something that requires SSL support


File: python.info,  Node: Client-side operation,  Next: Server-side operation,  Prev: Testing for SSL support,  Up: 範例<26>

5.18.3.17 Client-side operation
...............................

This example creates a SSL context with the recommended security
settings for client sockets, including automatic certificate
verification:

     >>> context = ssl.create_default_context()

If you prefer to tune security settings yourself, you might create a
context from scratch (but beware that you might not get the settings
right):

     >>> context = ssl.SSLContext(ssl.PROTOCOL_TLS_CLIENT)
     >>> context.load_verify_locations("/etc/ssl/certs/ca-bundle.crt")

(this snippet assumes your operating system places a bundle of all CA
certificates in ‘/etc/ssl/certs/ca-bundle.crt’; if not, you'll get an
error and have to adjust the location)

The *note PROTOCOL_TLS_CLIENT: 815. protocol configures the context for
cert validation and hostname verification.  *note verify_mode: 328b. is
set to *note CERT_REQUIRED: 328c. and *note check_hostname: 329f. is set
to ‘True’.  All other protocols create SSL contexts with insecure
defaults.

When you use the context to connect to a server, *note CERT_REQUIRED:
328c. and *note check_hostname: 329f. validate the server certificate:
it ensures that the server certificate was signed with one of the CA
certificates, checks the signature for correctness, and verifies other
properties like validity and identity of the hostname:

     >>> conn = context.wrap_socket(socket.socket(socket.AF_INET),
     ...                            server_hostname="www.python.org")
     >>> conn.connect(("www.python.org", 443))

You may then fetch the certificate:

     >>> cert = conn.getpeercert()

Visual inspection shows that the certificate does identify the desired
service (that is, the HTTPS host ‘www.python.org’):

     >>> pprint.pprint(cert)
     {'OCSP': ('http://ocsp.digicert.com',),
      'caIssuers': ('http://cacerts.digicert.com/DigiCertSHA2ExtendedValidationServerCA.crt',),
      'crlDistributionPoints': ('http://crl3.digicert.com/sha2-ev-server-g1.crl',
                                'http://crl4.digicert.com/sha2-ev-server-g1.crl'),
      'issuer': ((('countryName', 'US'),),
                 (('organizationName', 'DigiCert Inc'),),
                 (('organizationalUnitName', 'www.digicert.com'),),
                 (('commonName', 'DigiCert SHA2 Extended Validation Server CA'),)),
      'notAfter': 'Sep  9 12:00:00 2016 GMT',
      'notBefore': 'Sep  5 00:00:00 2014 GMT',
      'serialNumber': '01BB6F00122B177F36CAB49CEA8B6B26',
      'subject': ((('businessCategory', 'Private Organization'),),
                  (('1.3.6.1.4.1.311.60.2.1.3', 'US'),),
                  (('1.3.6.1.4.1.311.60.2.1.2', 'Delaware'),),
                  (('serialNumber', '3359300'),),
                  (('streetAddress', '16 Allen Rd'),),
                  (('postalCode', '03894-4801'),),
                  (('countryName', 'US'),),
                  (('stateOrProvinceName', 'NH'),),
                  (('localityName', 'Wolfeboro'),),
                  (('organizationName', 'Python Software Foundation'),),
                  (('commonName', 'www.python.org'),)),
      'subjectAltName': (('DNS', 'www.python.org'),
                         ('DNS', 'python.org'),
                         ('DNS', 'pypi.org'),
                         ('DNS', 'docs.python.org'),
                         ('DNS', 'testpypi.org'),
                         ('DNS', 'bugs.python.org'),
                         ('DNS', 'wiki.python.org'),
                         ('DNS', 'hg.python.org'),
                         ('DNS', 'mail.python.org'),
                         ('DNS', 'packaging.python.org'),
                         ('DNS', 'pythonhosted.org'),
                         ('DNS', 'www.pythonhosted.org'),
                         ('DNS', 'test.pythonhosted.org'),
                         ('DNS', 'us.pycon.org'),
                         ('DNS', 'id.python.org')),
      'version': 3}

Now the SSL channel is established and the certificate verified, you can
proceed to talk with the server:

     >>> conn.sendall(b"HEAD / HTTP/1.0\r\nHost: linuxfr.org\r\n\r\n")
     >>> pprint.pprint(conn.recv(1024).split(b"\r\n"))
     [b'HTTP/1.1 200 OK',
      b'Date: Sat, 18 Oct 2014 18:27:20 GMT',
      b'Server: nginx',
      b'Content-Type: text/html; charset=utf-8',
      b'X-Frame-Options: SAMEORIGIN',
      b'Content-Length: 45679',
      b'Accept-Ranges: bytes',
      b'Via: 1.1 varnish',
      b'Age: 2188',
      b'X-Served-By: cache-lcy1134-LCY',
      b'X-Cache: HIT',
      b'X-Cache-Hits: 11',
      b'Vary: Cookie',
      b'Strict-Transport-Security: max-age=63072000; includeSubDomains',
      b'Connection: close',
      b'',
      b'']

參閱下方 *note Security considerations: 317d. 的討論。


File: python.info,  Node: Server-side operation,  Prev: Client-side operation,  Up: 範例<26>

5.18.3.18 Server-side operation
...............................

For server operation, typically you'll need to have a server
certificate, and private key, each in a file.  You'll first create a
context holding the key and the certificate, so that clients can check
your authenticity.  Then you'll open a socket, bind it to a port, call
‘listen()’ on it, and start waiting for clients to connect:

     import socket, ssl

     context = ssl.create_default_context(ssl.Purpose.CLIENT_AUTH)
     context.load_cert_chain(certfile="mycertfile", keyfile="mykeyfile")

     bindsocket = socket.socket()
     bindsocket.bind(('myaddr.example.com', 10023))
     bindsocket.listen(5)

When a client connects, you'll call ‘accept()’ on the socket to get the
new socket from the other end, and use the context's *note
SSLContext.wrap_socket(): 4c9. method to create a server-side SSL socket
for the connection:

     while True:
         newsocket, fromaddr = bindsocket.accept()
         connstream = context.wrap_socket(newsocket, server_side=True)
         try:
             deal_with_client(connstream)
         finally:
             connstream.shutdown(socket.SHUT_RDWR)
             connstream.close()

Then you'll read data from the ‘connstream’ and do something with it
till you are finished with the client (or the client is finished with
you):

     def deal_with_client(connstream):
         data = connstream.recv(1024)
         # empty data means the client is finished with us
         while data:
             if not do_something(connstream, data):
                 # we'll assume do_something returns False
                 # when we're finished with client
                 break
             data = connstream.recv(1024)
         # finished with client

And go back to listening for new client connections (of course, a real
server would probably handle each client connection in a separate
thread, or put the sockets in *note non-blocking mode: 3291. and use an
event loop).


File: python.info,  Node: Notes on non-blocking sockets,  Next: Memory BIO Support<2>,  Prev: 範例<26>,  Up: ssl --- socket 物件的 TLS/SSL 包裝器

5.18.3.19 Notes on non-blocking sockets
.......................................

SSL sockets behave slightly different than regular sockets in
non-blocking mode.  When working with non-blocking sockets, there are
thus several things you need to be aware of:

   - Most *note SSLSocket: 88f. methods will raise either *note
     SSLWantWriteError: e0c. or *note SSLWantReadError: e0b. instead of
     *note BlockingIOError: ffa. if an I/O operation would block.  *note
     SSLWantReadError: e0b. will be raised if a read operation on the
     underlying socket is necessary, and *note SSLWantWriteError: e0c.
     for a write operation on the underlying socket.  Note that attempts
     to 'write' to an SSL socket may require 'reading' from the
     underlying socket first, and attempts to 'read' from the SSL socket
     may require a prior 'write' to the underlying socket.

     在 3.5 版的變更: In earlier Python versions, the ‘SSLSocket.send()’
     method returned zero instead of raising *note SSLWantWriteError:
     e0c. or *note SSLWantReadError: e0b.

   - Calling *note select(): d46. tells you that the OS-level socket can
     be read from (or written to), but it does not imply that there is
     sufficient data at the upper SSL layer.  For example, only part of
     an SSL frame might have arrived.  Therefore, you must be ready to
     handle ‘SSLSocket.recv()’ and ‘SSLSocket.send()’ failures, and
     retry after another call to *note select(): d46.

   - Conversely, since the SSL layer has its own framing, a SSL socket
     may still have data available for reading without *note select():
     d46. being aware of it.  Therefore, you should first call
     ‘SSLSocket.recv()’ to drain any potentially available data, and
     then only block on a *note select(): d46. call if still necessary.

     (of course, similar provisions apply when using other primitives
     such as *note poll(): 2a99, or those in the *note selectors: b0.
     module)

   - The SSL handshake itself will be non-blocking: the *note
     SSLSocket.do_handshake(): e0f. method has to be retried until it
     returns successfully.  Here is a synopsis using *note select():
     d46. to wait for the socket's readiness:

          while True:
              try:
                  sock.do_handshake()
                  break
              except ssl.SSLWantReadError:
                  select.select([sock], [], [])
              except ssl.SSLWantWriteError:
                  select.select([], [sock], [])

也參考
......

The *note asyncio: 8. module supports *note non-blocking SSL sockets:
3291. and provides a higher level API. It polls for events using the
*note selectors: b0. module and handles *note SSLWantWriteError: e0c,
*note SSLWantReadError: e0b. and *note BlockingIOError: ffa. exceptions.
It runs the SSL handshake asynchronously as well.


File: python.info,  Node: Memory BIO Support<2>,  Next: SSL session,  Prev: Notes on non-blocking sockets,  Up: ssl --- socket 物件的 TLS/SSL 包裝器

5.18.3.20 Memory BIO Support
............................

在 3.5 版被加入.

Ever since the SSL module was introduced in Python 2.6, the *note
SSLSocket: 88f. class has provided two related but distinct areas of
functionality:

   - SSL protocol handling

   - Network IO

The network IO API is identical to that provided by *note socket.socket:
d47, from which *note SSLSocket: 88f. also inherits.  This allows an SSL
socket to be used as a drop-in replacement for a regular socket, making
it very easy to add SSL support to an existing application.

Combining SSL protocol handling and network IO usually works well, but
there are some cases where it doesn't.  An example is async IO
frameworks that want to use a different IO multiplexing model than the
"select/poll on a file descriptor" (readiness based) model that is
assumed by *note socket.socket: d47. and by the internal OpenSSL socket
IO routines.  This is mostly relevant for platforms like Windows where
this model is not efficient.  For this purpose, a reduced scope variant
of *note SSLSocket: 88f. called *note SSLObject: b25. is provided.

 -- 類別: ssl.SSLObject

     A reduced-scope variant of *note SSLSocket: 88f. representing an
     SSL protocol instance that does not contain any network IO methods.
     This class is typically used by framework authors that want to
     implement asynchronous IO for SSL through memory buffers.

     This class implements an interface on top of a low-level SSL object
     as implemented by OpenSSL. This object captures the state of an SSL
     connection but does not provide any network IO itself.  IO needs to
     be performed through separate "BIO" objects which are OpenSSL's IO
     abstraction layer.

     This class has no public constructor.  An *note SSLObject: b25.
     instance must be created using the *note wrap_bio(): b26. method.
     This method will create the *note SSLObject: b25. instance and bind
     it to a pair of BIOs.  The 'incoming' BIO is used to pass data from
     Python to the SSL protocol instance, while the 'outgoing' BIO is
     used to pass data the other way around.

     The following methods are available:

        - *note context: 32c8.

        - *note server_side: 32ca.

        - *note server_hostname: b23.

        - *note session: 32cb.

        - *note session_reused: 32cc.

        - *note read(): e10.

        - *note write(): e11.

        - *note getpeercert(): f5a.

        - *note get_verified_chain(): 14cf.

        - *note get_unverified_chain(): 14d0.

        - *note selected_alpn_protocol(): e07.

        - *note selected_npn_protocol(): 817.

        - *note cipher(): 31c2.

        - *note shared_ciphers(): e0e.

        - *note compression(): 10de.

        - *note pending(): 32c9.

        - *note do_handshake(): e0f.

        - *note verify_client_post_handshake(): 9d6.

        - *note unwrap(): 32c7.

        - *note get_channel_binding(): 10dd.

        - *note version(): e0a.

     When compared to *note SSLSocket: 88f, this object lacks the
     following features:

        - Any form of network IO; ‘recv()’ and ‘send()’ read and write
          only to the underlying *note MemoryBIO: e04. buffers.

        - There is no 'do_handshake_on_connect' machinery.  You must
          always manually call *note do_handshake(): e0f. to start the
          handshake.

        - There is no handling of 'suppress_ragged_eofs'.  All
          end-of-file conditions that are in violation of the protocol
          are reported via the *note SSLEOFError: 1646. exception.

        - The method *note unwrap(): 32c7. call does not return
          anything, unlike for an SSL socket where it returns the
          underlying socket.

        - The 'server_name_callback' callback passed to *note
          SSLContext.set_servername_callback(): f59. will get an *note
          SSLObject: b25. instance instead of a *note SSLSocket: 88f.
          instance as its first parameter.

     Some notes related to the use of *note SSLObject: b25.:

        - All IO on an *note SSLObject: b25. is *note non-blocking:
          3291.  This means that for example *note read(): e10. will
          raise an *note SSLWantReadError: e0b. if it needs more data
          than the incoming BIO has available.

     在 3.7 版的變更: *note SSLObject: b25. instances must be created
     with *note wrap_bio(): b26.  In earlier versions, it was possible
     to create instances directly.  This was never documented or
     officially supported.

An SSLObject communicates with the outside world using memory buffers.
The class *note MemoryBIO: e04. provides a memory buffer that can be
used for this purpose.  It wraps an OpenSSL memory BIO (Basic IO)
object:

 -- 類別: ssl.MemoryBIO

     A memory buffer that can be used to pass data between Python and an
     SSL protocol instance.

      -- 屬性: pending

          Return the number of bytes currently in the memory buffer.

      -- 屬性: eof

          A boolean indicating whether the memory BIO is current at the
          end-of-file position.

      -- 方法: read (n=-1)

          Read up to 'n' bytes from the memory buffer.  If 'n' is not
          specified or negative, all bytes are returned.

      -- 方法: write (buf)

          Write the bytes from 'buf' to the memory BIO. The 'buf'
          argument must be an object supporting the buffer protocol.

          The return value is the number of bytes written, which is
          always equal to the length of 'buf'.

      -- 方法: write_eof ()

          Write an EOF marker to the memory BIO. After this method has
          been called, it is illegal to call *note write(): 32e6.  The
          attribute *note eof: 32e4. will become true after all data
          currently in the buffer has been read.


File: python.info,  Node: SSL session,  Next: Security considerations<2>,  Prev: Memory BIO Support<2>,  Up: ssl --- socket 物件的 TLS/SSL 包裝器

5.18.3.21 SSL session
.....................

在 3.6 版被加入.

 -- 類別: ssl.SSLSession

     Session object used by *note session: 32cb.

      -- 屬性: id

      -- 屬性: time

      -- 屬性: timeout

      -- 屬性: ticket_lifetime_hint

      -- 屬性: has_ticket


File: python.info,  Node: Security considerations<2>,  Next: TLS 1 3,  Prev: SSL session,  Up: ssl --- socket 物件的 TLS/SSL 包裝器

5.18.3.22 Security considerations
.................................

* Menu:

* Best defaults::
* 手動設定::
* Multi-processing::


File: python.info,  Node: Best defaults,  Next: 手動設定,  Up: Security considerations<2>

5.18.3.23 Best defaults
.......................

For 'client use', if you don't have any special requirements for your
security policy, it is highly recommended that you use the *note
create_default_context(): 13a. function to create your SSL context.  It
will load the system's trusted CA certificates, enable certificate
validation and hostname checking, and try to choose reasonably secure
protocol and cipher settings.

For example, here is how you would use the *note smtplib.SMTP: 8d1.
class to create a trusted, secure connection to a SMTP server:

     >>> import ssl, smtplib
     >>> smtp = smtplib.SMTP("mail.python.org", port=587)
     >>> context = ssl.create_default_context()
     >>> smtp.starttls(context=context)
     (220, b'2.0.0 Ready to start TLS')

If a client certificate is needed for the connection, it can be added
with *note SSLContext.load_cert_chain(): 277.

By contrast, if you create the SSL context by calling the *note
SSLContext: 276. constructor yourself, it will not have certificate
validation nor hostname checking enabled by default.  If you do so,
please read the paragraphs below to achieve a good security level.


File: python.info,  Node: 手動設定,  Next: Multi-processing,  Prev: Best defaults,  Up: Security considerations<2>

5.18.3.24 手動設定
..................

* Menu:

* 驗證憑證::
* 協定版本::
* Cipher selection::


File: python.info,  Node: 驗證憑證,  Next: 協定版本,  Up: 手動設定

5.18.3.25 驗證憑證
..................

When calling the *note SSLContext: 276. constructor directly, *note
CERT_NONE: 329d. is the default.  Since it does not authenticate the
other peer, it can be insecure, especially in client mode where most of
the time you would like to ensure the authenticity of the server you're
talking to.  Therefore, when in client mode, it is highly recommended to
use *note CERT_REQUIRED: 328c.  However, it is in itself not sufficient;
you also have to check that the server certificate, which can be
obtained by calling *note SSLSocket.getpeercert(): f5a, matches the
desired service.  For many protocols and applications, the service can
be identified by the hostname.  This common check is automatically
performed when *note SSLContext.check_hostname: 329f. is enabled.

在 3.7 版的變更: Hostname matchings is now performed by OpenSSL. Python
no longer uses ‘match_hostname()’.

In server mode, if you want to authenticate your clients using the SSL
layer (rather than using a higher-level authentication mechanism),
you'll also have to specify *note CERT_REQUIRED: 328c. and similarly
check the client certificate.


File: python.info,  Node: 協定版本,  Next: Cipher selection,  Prev: 驗證憑證,  Up: 手動設定

5.18.3.26 協定版本
..................

SSL versions 2 and 3 are considered insecure and are therefore dangerous
to use.  If you want maximum compatibility between clients and servers,
it is recommended to use *note PROTOCOL_TLS_CLIENT: 815. or *note
PROTOCOL_TLS_SERVER: 816. as the protocol version.  SSLv2 and SSLv3 are
disabled by default.

     >>> client_context = ssl.SSLContext(ssl.PROTOCOL_TLS_CLIENT)
     >>> client_context.minimum_version = ssl.TLSVersion.TLSv1_3
     >>> client_context.maximum_version = ssl.TLSVersion.TLSv1_3

The SSL context created above will only allow TLSv1.3 and later (if
supported by your system) connections to a server.  *note
PROTOCOL_TLS_CLIENT: 815. implies certificate validation and hostname
checks by default.  You have to load certificates into the context.


File: python.info,  Node: Cipher selection,  Prev: 協定版本,  Up: 手動設定

5.18.3.27 Cipher selection
..........................

If you have advanced security requirements, fine-tuning of the ciphers
enabled when negotiating a SSL session is possible through the *note
SSLContext.set_ciphers(): 32cf. method.  Starting from Python 3.2.3, the
ssl module disables certain weak ciphers by default, but you may want to
further restrict the cipher choice.  Be sure to read OpenSSL's
documentation about the cipher list format(1).  If you want to check
which ciphers are enabled by a given cipher list, use *note
SSLContext.get_ciphers(): c85. or the ‘openssl ciphers’ command on your
system.

   ---------- Footnotes ----------

   (1) 
https://www.openssl.org/docs/man1.1.1/man1/ciphers.html#CIPHER-LIST-FORMAT


File: python.info,  Node: Multi-processing,  Prev: 手動設定,  Up: Security considerations<2>

5.18.3.28 Multi-processing
..........................

If using this module as part of a multi-processed application (using,
for example the *note multiprocessing: 86. or *note concurrent.futures:
1a. modules), be aware that OpenSSL's internal random number generator
does not properly handle forked processes.  Applications must change the
PRNG state of the parent process if they use any SSL feature with *note
os.fork(): 17b.  Any successful call of *note RAND_add(): 3297. or *note
RAND_bytes(): 4c8. is sufficient.


File: python.info,  Node: TLS 1 3,  Prev: Security considerations<2>,  Up: ssl --- socket 物件的 TLS/SSL 包裝器

5.18.3.29 TLS 1.3
.................

在 3.7 版被加入.

The TLS 1.3 protocol behaves slightly differently than previous version
of TLS/SSL. Some new TLS 1.3 features are not yet available.

   - TLS 1.3 uses a disjunct set of cipher suites.  All AES-GCM and
     ChaCha20 cipher suites are enabled by default.  The method *note
     SSLContext.set_ciphers(): 32cf. cannot enable or disable any TLS
     1.3 ciphers yet, but *note SSLContext.get_ciphers(): c85. returns
     them.

   - Session tickets are no longer sent as part of the initial handshake
     and are handled differently.  *note SSLSocket.session: 32cb. and
     *note SSLSession: c84. are not compatible with TLS 1.3.

   - Client-side certificates are also no longer verified during the
     initial handshake.  A server can request a certificate at any time.
     Clients process certificate requests while they send or receive
     application data from the server.

   - TLS 1.3 features like early data, deferred TLS client cert request,
     signature algorithm configuration, and rekeying are not supported
     yet.

也參考
......

*note socket.socket: d47. 類別

     底層 *note socket: b8. 類別的文件

SSL/TLS Strong Encryption: An Introduction(1)

     Apache HTTP Server 文件的介紹

RFC 1422: Privacy Enhancement for Internet Electronic Mail: Part II: Certificate-Based Key Management(2)

     Steve Kent

RFC 4086: Randomness Requirements for Security(3)

     Donald E., Jeffrey I. Schiller

RFC 5280: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile(4)

     D. Cooper

RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2(5)

     T. Dierks et.  al.

RFC 6066: Transport Layer Security (TLS) Extensions(6)

     D. Eastlake

IANA TLS: Transport Layer Security (TLS) Parameters(7)

     IANA

RFC 7525: Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)(8)

     IETF

Mozilla's Server Side TLS recommendations(9)

     Mozilla

   ---------- Footnotes ----------

   (1) https://httpd.apache.org/docs/trunk/en/ssl/ssl_intro.html

   (2) https://datatracker.ietf.org/doc/html/rfc1422.html

   (3) https://datatracker.ietf.org/doc/html/rfc4086.html

   (4) https://datatracker.ietf.org/doc/html/rfc5280.html

   (5) https://datatracker.ietf.org/doc/html/rfc5246.html

   (6) https://datatracker.ietf.org/doc/html/rfc6066.html

   (7) 
https://www.iana.org/assignments/tls-parameters/tls-parameters.xml

   (8) https://datatracker.ietf.org/doc/html/rfc7525.html

   (9) https://wiki.mozilla.org/Security/Server_Side_TLS


File: python.info,  Node: select --- 等待 I/O 完成,  Next: selectors --- 高階 I/O 多工,  Prev: ssl --- socket 物件的 TLS/SSL 包裝器,  Up: Networking and Interprocess Communication

5.18.4 ‘select’ -- 等待 I/O 完成
--------------------------------

__________________________________________________________________

This module provides access to the ‘select()’ and ‘poll()’ functions
available in most operating systems, ‘devpoll()’ available on Solaris
and derivatives, ‘epoll()’ available on Linux 2.5+ and ‘kqueue()’
available on most BSD. Note that on Windows, it only works for sockets;
on other operating systems, it also works for other file types (in
particular, on Unix, it works on pipes).  It cannot be used on regular
files to determine whether a file has grown since it was last read.

     備註: The *note selectors: b0. module allows high-level and
     efficient I/O multiplexing, built upon the *note select: af. module
     primitives.  Users are encouraged to use the *note selectors: b0.
     module instead, unless they want precise control over the OS-level
     primitives used.

*note Availability: 1c56.: not WASI.

This module does not work or is not available on WebAssembly.  See *note
WebAssembly 平台: 16e6. for more information.

The module defines the following:

 -- 例外: select.error

     A deprecated alias of *note OSError: 350.

     在 3.3 版的變更: Following PEP 3151(1), this class was made an
     alias of *note OSError: 350.

 -- 函式: select.devpoll ()

     (Only supported on Solaris and derivatives.)  Returns a ‘/dev/poll’
     polling object; see section *note /dev/poll Polling Objects: 32f8.
     below for the methods supported by devpoll objects.

     ‘devpoll()’ objects are linked to the number of file descriptors
     allowed at the time of instantiation.  If your program reduces this
     value, ‘devpoll()’ will fail.  If your program increases this
     value, ‘devpoll()’ may return an incomplete list of active file
     descriptors.

     The new file descriptor is *note non-inheritable: e9d.

     在 3.3 版被加入.

     在 3.4 版的變更: The new file descriptor is now non-inheritable.

 -- 函式: select.epoll (sizehint=-1, flags=0)

     (Only supported on Linux 2.5.44 and newer.)  Return an edge polling
     object, which can be used as Edge or Level Triggered interface for
     I/O events.

     'sizehint' informs epoll about the expected number of events to be
     registered.  It must be positive, or ‘-1’ to use the default.  It
     is only used on older systems where ‘epoll_create1()’ is not
     available; otherwise it has no effect (though its value is still
     checked).

     'flags' is deprecated and completely ignored.  However, when
     supplied, its value must be ‘0’ or ‘select.EPOLL_CLOEXEC’,
     otherwise ‘OSError’ is raised.

     See the *note Edge and Level Trigger Polling (epoll) Objects: 32f9.
     section below for the methods supported by epolling objects.

     ‘epoll’ objects support the context management protocol: when used
     in a *note with: 577. statement, the new file descriptor is
     automatically closed at the end of the block.

     The new file descriptor is *note non-inheritable: e9d.

     在 3.3 版的變更: 新增 'flags' 參數。

     在 3.4 版的變更: Support for the *note with: 577. statement was
     added.  The new file descriptor is now non-inheritable.

     在 3.4 版之後被棄用: The 'flags' parameter.  ‘select.EPOLL_CLOEXEC’
     is used by default now.  Use *note os.set_inheritable(): e9f. to
     make the file descriptor inheritable.

 -- 函式: select.poll ()

     (Not supported by all operating systems.)  Returns a polling
     object, which supports registering and unregistering file
     descriptors, and then polling them for I/O events; see section
     *note Polling Objects: 32fa. below for the methods supported by
     polling objects.

 -- 函式: select.kqueue ()

     (Only supported on BSD.) Returns a kernel queue object; see section
     *note Kqueue Objects: 32fb. below for the methods supported by
     kqueue objects.

     The new file descriptor is *note non-inheritable: e9d.

     在 3.4 版的變更: The new file descriptor is now non-inheritable.

 -- 函式: select.kevent (ident, filter=KQ_FILTER_READ, flags=KQ_EV_ADD,
          fflags=0, data=0, udata=0)

     (Only supported on BSD.) Returns a kernel event object; see section
     *note Kevent Objects: 32fd. below for the methods supported by
     kevent objects.

 -- 函式: select.select (rlist, wlist, xlist[, timeout])

     This is a straightforward interface to the Unix ‘select()’ system
     call.  The first three arguments are iterables of 'waitable
     objects': either integers representing file descriptors or objects
     with a parameterless method named *note fileno(): 2732. returning
     such an integer:

        * 'rlist': wait until ready for reading

        * 'wlist': wait until ready for writing

        * 'xlist': wait for an "exceptional condition" (see the manual
          page for what your system considers such a condition)

     Empty iterables are allowed, but acceptance of three empty
     iterables is platform-dependent.  (It is known to work on Unix but
     not on Windows.)  The optional 'timeout' argument specifies a
     time-out as a floating-point number in seconds.  When the 'timeout'
     argument is omitted the function blocks until at least one file
     descriptor is ready.  A time-out value of zero specifies a poll and
     never blocks.

     The return value is a triple of lists of objects that are ready:
     subsets of the first three arguments.  When the time-out is reached
     without a file descriptor becoming ready, three empty lists are
     returned.

     Among the acceptable object types in the iterables are Python *note
     file objects: 115b. (e.g.  ‘sys.stdin’, or objects returned by
     *note open(): 4c0. or *note os.popen(): a2a.), socket objects
     returned by *note socket.socket(): d47.  You may also define a
     'wrapper' class yourself, as long as it has an appropriate *note
     fileno(): 2732. method (that really returns a file descriptor, not
     just a random integer).

          備註: 
          File objects on Windows are not acceptable, but sockets are.
          On Windows, the underlying ‘select()’ function is provided by
          the WinSock library, and does not handle file descriptors that
          don't originate from WinSock.

     在 3.5 版的變更: The function is now retried with a recomputed
     timeout when interrupted by a signal, except if the signal handler
     raises an exception (see PEP 475(2) for the rationale), instead of
     raising *note InterruptedError: d2e.

 -- 屬性: select.PIPE_BUF

     The minimum number of bytes which can be written without blocking
     to a pipe when the pipe has been reported as ready for writing by
     *note select(): d46, ‘poll()’ or another interface in this module.
     This doesn't apply to other kind of file-like objects such as
     sockets.

     This value is guaranteed by POSIX to be at least 512.

     *note 適用: 1c56.：Unix。

     在 3.2 版被加入.

* Menu:

* /dev/poll Polling Objects::
* Edge and Level Trigger Polling (epoll) Objects: Edge and Level Trigger Polling epoll Objects.
* Polling Objects::
* Kqueue Objects::
* Kevent Objects::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3151/

   (2) https://peps.python.org/pep-0475/


File: python.info,  Node: /dev/poll Polling Objects,  Next: Edge and Level Trigger Polling epoll Objects,  Up: select --- 等待 I/O 完成

5.18.4.1 ‘/dev/poll’ Polling Objects
....................................

Solaris and derivatives have ‘/dev/poll’.  While ‘select()’ is
'O'('highest file descriptor') and ‘poll()’ is 'O'('number of file
descriptors'), ‘/dev/poll’ is 'O'('active file descriptors').

‘/dev/poll’ behaviour is very close to the standard ‘poll()’ object.

 -- 方法: devpoll.close ()

     Close the file descriptor of the polling object.

     在 3.4 版被加入.

 -- 屬性: devpoll.closed

     ‘True’ if the polling object is closed.

     在 3.4 版被加入.

 -- 方法: devpoll.fileno ()

     Return the file descriptor number of the polling object.

     在 3.4 版被加入.

 -- 方法: devpoll.register (fd[, eventmask])

     Register a file descriptor with the polling object.  Future calls
     to the *note poll(): 2a99. method will then check whether the file
     descriptor has any pending I/O events.  'fd' can be either an
     integer, or an object with a *note fileno(): 2732. method that
     returns an integer.  File objects implement ‘fileno()’, so they can
     also be used as the argument.

     'eventmask' is an optional bitmask describing the type of events
     you want to check for.  The constants are the same that with
     ‘poll()’ object.  The default value is a combination of the
     constants ‘POLLIN’, ‘POLLPRI’, and ‘POLLOUT’.

          警告: Registering a file descriptor that's already registered
          is not an error, but the result is undefined.  The appropriate
          action is to unregister or modify it first.  This is an
          important difference compared with ‘poll()’.

 -- 方法: devpoll.modify (fd[, eventmask])

     This method does an *note unregister(): 3301. followed by a *note
     register(): 32ff.  It is (a bit) more efficient that doing the same
     explicitly.

 -- 方法: devpoll.unregister (fd)

     Remove a file descriptor being tracked by a polling object.  Just
     like the *note register(): 32ff. method, 'fd' can be an integer or
     an object with a *note fileno(): 2732. method that returns an
     integer.

     Attempting to remove a file descriptor that was never registered is
     safely ignored.

 -- 方法: devpoll.poll ([timeout])

     Polls the set of registered file descriptors, and returns a
     possibly empty list containing ‘(fd, event)’ 2-tuples for the
     descriptors that have events or errors to report.  'fd' is the file
     descriptor, and 'event' is a bitmask with bits set for the reported
     events for that descriptor -- ‘POLLIN’ for waiting input, ‘POLLOUT’
     to indicate that the descriptor can be written to, and so forth.
     An empty list indicates that the call timed out and no file
     descriptors had any events to report.  If 'timeout' is given, it
     specifies the length of time in milliseconds which the system will
     wait for events before returning.  If 'timeout' is omitted, -1, or
     *note None: 61b, the call will block until there is an event for
     this poll object.

     在 3.5 版的變更: The function is now retried with a recomputed
     timeout when interrupted by a signal, except if the signal handler
     raises an exception (see PEP 475(1) for the rationale), instead of
     raising *note InterruptedError: d2e.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0475/


File: python.info,  Node: Edge and Level Trigger Polling epoll Objects,  Next: Polling Objects,  Prev: /dev/poll Polling Objects,  Up: select --- 等待 I/O 完成

5.18.4.2 Edge and Level Trigger Polling (epoll) Objects
.......................................................

     ‘https://linux.die.net/man/4/epoll’

     'eventmask'

     常數                          含義
                                   
     ----------------------------------------------------------------------------------
                                   
     ‘EPOLLIN’                     Available for read
                                   
                                   
     ‘EPOLLOUT’                    Available for write
                                   
                                   
     ‘EPOLLPRI’                    Urgent data for read
                                   
                                   
     ‘EPOLLERR’                    Error condition happened on the assoc.  fd
                                   
                                   
     ‘EPOLLHUP’                    Hang up happened on the assoc.  fd
                                   
                                   
     ‘EPOLLET’                     Set Edge Trigger behavior, the default is Level
                                   Trigger behavior
                                   
                                   
     ‘EPOLLONESHOT’                Set one-shot behavior.  After one event is pulled
                                   out, the fd is internally disabled
                                   
                                   
     ‘EPOLLEXCLUSIVE’              Wake only one epoll object when the associated fd
                                   has an event.  The default (if this flag is not
                                   set) is to wake all epoll objects polling on a
                                   fd.
                                   
                                   
     ‘EPOLLRDHUP’                  Stream socket peer closed connection or shut down
                                   writing half of connection.
                                   
                                   
     ‘EPOLLRDNORM’                 等價於 ‘EPOLLIN’
                                   
                                   
     ‘EPOLLRDBAND’                 Priority data band can be read.
                                   
                                   
     ‘EPOLLWRNORM’                 等價於 ‘EPOLLOUT’
                                   
                                   
     ‘EPOLLWRBAND’                 Priority data may be written.
                                   
                                   
     ‘EPOLLMSG’                    Ignored.
                                   

     在 3.6 版被加入: ‘EPOLLEXCLUSIVE’ was added.  It's only supported
     by Linux Kernel 4.5 or later.

 -- 方法: epoll.close ()

     Close the control file descriptor of the epoll object.

 -- 屬性: epoll.closed

     ‘True’ if the epoll object is closed.

 -- 方法: epoll.fileno ()

     Return the file descriptor number of the control fd.

 -- 方法: epoll.fromfd (fd)

     Create an epoll object from a given file descriptor.

 -- 方法: epoll.register (fd[, eventmask])

     Register a fd descriptor with the epoll object.

 -- 方法: epoll.modify (fd, eventmask)

     Modify a registered file descriptor.

 -- 方法: epoll.unregister (fd)

     Remove a registered file descriptor from the epoll object.

     在 3.9 版的變更: The method no longer ignores the *note EBADF: 8ff.
     error.

 -- 方法: epoll.poll (timeout=None, maxevents=-1)

     Wait for events.  timeout in seconds (float)

     在 3.5 版的變更: The function is now retried with a recomputed
     timeout when interrupted by a signal, except if the signal handler
     raises an exception (see PEP 475(1) for the rationale), instead of
     raising *note InterruptedError: d2e.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0475/


File: python.info,  Node: Polling Objects,  Next: Kqueue Objects,  Prev: Edge and Level Trigger Polling epoll Objects,  Up: select --- 等待 I/O 完成

5.18.4.3 Polling Objects
........................

The ‘poll()’ system call, supported on most Unix systems, provides
better scalability for network servers that service many, many clients
at the same time.  ‘poll()’ scales better because the system call only
requires listing the file descriptors of interest, while ‘select()’
builds a bitmap, turns on bits for the fds of interest, and then
afterward the whole bitmap has to be linearly scanned again.  ‘select()’
is 'O'('highest file descriptor'), while ‘poll()’ is 'O'('number of file
descriptors').

 -- 方法: poll.register (fd[, eventmask])

     Register a file descriptor with the polling object.  Future calls
     to the *note poll(): 2a99. method will then check whether the file
     descriptor has any pending I/O events.  'fd' can be either an
     integer, or an object with a *note fileno(): 2732. method that
     returns an integer.  File objects implement ‘fileno()’, so they can
     also be used as the argument.

     'eventmask' is an optional bitmask describing the type of events
     you want to check for, and can be a combination of the constants
     ‘POLLIN’, ‘POLLPRI’, and ‘POLLOUT’, described in the table below.
     If not specified, the default value used will check for all 3 types
     of events.

     常數                    含義
                             
     -----------------------------------------------------------------------
                             
     ‘POLLIN’                There is data to read
                             
                             
     ‘POLLPRI’               There is urgent data to read
                             
                             
     ‘POLLOUT’               Ready for output: writing will not block
                             
                             
     ‘POLLERR’               Error condition of some sort
                             
                             
     ‘POLLHUP’               Hung up
                             
                             
     ‘POLLRDHUP’             Stream socket peer closed connection, or
                             shut down writing half of connection
                             
                             
     ‘POLLNVAL’              Invalid request: descriptor not open
                             

     Registering a file descriptor that's already registered is not an
     error, and has the same effect as registering the descriptor
     exactly once.

 -- 方法: poll.modify (fd, eventmask)

     Modifies an already registered fd.  This has the same effect as
     ‘register(fd, eventmask)’.  Attempting to modify a file descriptor
     that was never registered causes an *note OSError: 350. exception
     with errno ‘ENOENT’ to be raised.

 -- 方法: poll.unregister (fd)

     Remove a file descriptor being tracked by a polling object.  Just
     like the *note register(): 3309. method, 'fd' can be an integer or
     an object with a *note fileno(): 2732. method that returns an
     integer.

     Attempting to remove a file descriptor that was never registered
     causes a *note KeyError: 2fb. exception to be raised.

 -- 方法: poll.poll ([timeout])

     Polls the set of registered file descriptors, and returns a
     possibly empty list containing ‘(fd, event)’ 2-tuples for the
     descriptors that have events or errors to report.  'fd' is the file
     descriptor, and 'event' is a bitmask with bits set for the reported
     events for that descriptor -- ‘POLLIN’ for waiting input, ‘POLLOUT’
     to indicate that the descriptor can be written to, and so forth.
     An empty list indicates that the call timed out and no file
     descriptors had any events to report.  If 'timeout' is given, it
     specifies the length of time in milliseconds which the system will
     wait for events before returning.  If 'timeout' is omitted,
     negative, or *note None: 61b, the call will block until there is an
     event for this poll object.

     在 3.5 版的變更: The function is now retried with a recomputed
     timeout when interrupted by a signal, except if the signal handler
     raises an exception (see PEP 475(1) for the rationale), instead of
     raising *note InterruptedError: d2e.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0475/


File: python.info,  Node: Kqueue Objects,  Next: Kevent Objects,  Prev: Polling Objects,  Up: select --- 等待 I/O 完成

5.18.4.4 Kqueue Objects
.......................

 -- 方法: kqueue.close ()

     Close the control file descriptor of the kqueue object.

 -- 屬性: kqueue.closed

     ‘True’ if the kqueue object is closed.

 -- 方法: kqueue.fileno ()

     Return the file descriptor number of the control fd.

 -- 方法: kqueue.fromfd (fd)

     Create a kqueue object from a given file descriptor.

 -- 方法: kqueue.control (changelist, max_events[, timeout]) ->
          eventlist

     Low level interface to kevent

        - changelist must be an iterable of kevent objects or ‘None’

        - max_events must be 0 or a positive integer

        - timeout in seconds (floats possible); the default is ‘None’,
          to wait forever

     在 3.5 版的變更: The function is now retried with a recomputed
     timeout when interrupted by a signal, except if the signal handler
     raises an exception (see PEP 475(1) for the rationale), instead of
     raising *note InterruptedError: d2e.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0475/


File: python.info,  Node: Kevent Objects,  Prev: Kqueue Objects,  Up: select --- 等待 I/O 完成

5.18.4.5 Kevent Objects
.......................

‘https://man.freebsd.org/cgi/man.cgi?query=kqueue&sektion=2’

 -- 屬性: kevent.ident

     Value used to identify the event.  The interpretation depends on
     the filter but it's usually the file descriptor.  In the
     constructor ident can either be an int or an object with a *note
     fileno(): 2732. method.  kevent stores the integer internally.

 -- 屬性: kevent.filter

     Name of the kernel filter.

     常數                            含義
                                     
     ----------------------------------------------------------------------------------
                                     
     ‘KQ_FILTER_READ’                Takes a descriptor and returns whenever there
                                     is data available to read
                                     
                                     
     ‘KQ_FILTER_WRITE’               Takes a descriptor and returns whenever there
                                     is data available to write
                                     
                                     
     ‘KQ_FILTER_AIO’                 AIO requests
                                     
                                     
     ‘KQ_FILTER_VNODE’               Returns when one or more of the requested
                                     events watched in 'fflag' occurs
                                     
                                     
     ‘KQ_FILTER_PROC’                Watch for events on a process id
                                     
                                     
     ‘KQ_FILTER_NETDEV’              Watch for events on a network device [not
                                     available on macOS]
                                     
                                     
     ‘KQ_FILTER_SIGNAL’              Returns whenever the watched signal is
                                     delivered to the process
                                     
                                     
     ‘KQ_FILTER_TIMER’               Establishes an arbitrary timer
                                     

 -- 屬性: kevent.flags

     Filter action.

     常數                            含義
                                     
     ----------------------------------------------------------------------------------
                                     
     ‘KQ_EV_ADD’                     Adds or modifies an event
                                     
                                     
     ‘KQ_EV_DELETE’                  Removes an event from the queue
                                     
                                     
     ‘KQ_EV_ENABLE’                  Permitscontrol() to returns the event
                                     
                                     
     ‘KQ_EV_DISABLE’                 Disablesevent
                                     
                                     
     ‘KQ_EV_ONESHOT’                 Removes event after first occurrence
                                     
                                     
     ‘KQ_EV_CLEAR’                   Reset the state after an event is retrieved
                                     
                                     
     ‘KQ_EV_SYSFLAGS’                internal event
                                     
                                     
     ‘KQ_EV_FLAG1’                   internal event
                                     
                                     
     ‘KQ_EV_EOF’                     Filter specific EOF condition
                                     
                                     
     ‘KQ_EV_ERROR’                   See return values
                                     

 -- 屬性: kevent.fflags

     Filter specific flags.

     ‘KQ_FILTER_READ’ and ‘KQ_FILTER_WRITE’ filter flags:

     常數                             含義
                                      
     ----------------------------------------------------------------------------------
                                      
     ‘KQ_NOTE_LOWAT’                  low water mark of a socket buffer
                                      

     ‘KQ_FILTER_VNODE’ filter flags:

     常數                             含義
                                      
     ----------------------------------------------------------------------------------
                                      
     ‘KQ_NOTE_DELETE’                 'unlink()' was called
                                      
                                      
     ‘KQ_NOTE_WRITE’                  a write occurred
                                      
                                      
     ‘KQ_NOTE_EXTEND’                 the file was extended
                                      
                                      
     ‘KQ_NOTE_ATTRIB’                 an attribute was changed
                                      
                                      
     ‘KQ_NOTE_LINK’                   the link count has changed
                                      
                                      
     ‘KQ_NOTE_RENAME’                 the file was renamed
                                      
                                      
     ‘KQ_NOTE_REVOKE’                 access to the file was revoked
                                      

     ‘KQ_FILTER_PROC’ filter flags:

     常數                             含義
                                      
     ----------------------------------------------------------------------------------
                                      
     ‘KQ_NOTE_EXIT’                   the process has exited
                                      
                                      
     ‘KQ_NOTE_FORK’                   the process has called 'fork()'
                                      
                                      
     ‘KQ_NOTE_EXEC’                   the process has executed a new process
                                      
                                      
     ‘KQ_NOTE_PCTRLMASK’              internal filter flag
                                      
                                      
     ‘KQ_NOTE_PDATAMASK’              internal filter flag
                                      
                                      
     ‘KQ_NOTE_TRACK’                  follow a process across 'fork()'
                                      
                                      
     ‘KQ_NOTE_CHILD’                  returned on the child process for 'NOTE_TRACK'
                                      
                                      
     ‘KQ_NOTE_TRACKERR’               unable to attach to a child
                                      

     ‘KQ_FILTER_NETDEV’ filter flags (not available on macOS):

     常數                             含義
                                      
     ----------------------------------------------------------------------------------
                                      
     ‘KQ_NOTE_LINKUP’                 link is up
                                      
                                      
     ‘KQ_NOTE_LINKDOWN’               link is down
                                      
                                      
     ‘KQ_NOTE_LINKINV’                link state is invalid
                                      

 -- 屬性: kevent.data

     Filter specific data.

 -- 屬性: kevent.udata

     User defined value.


File: python.info,  Node: selectors --- 高階 I/O 多工,  Next: signal --- 設定非同步事件的處理函式,  Prev: select --- 等待 I/O 完成,  Up: Networking and Interprocess Communication

5.18.5 ‘selectors’ -- 高階 I/O 多工
-----------------------------------

在 3.4 版被加入.

'原始碼：'Lib/selectors.py(1)

__________________________________________________________________

* Menu:

* 簡介: 簡介<8>.
* Classes: Classes<3>.
* 範例: 範例<27>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/selectors.py


File: python.info,  Node: 簡介<8>,  Next: Classes<3>,  Up: selectors --- 高階 I/O 多工

5.18.5.1 簡介
.............

This module allows high-level and efficient I/O multiplexing, built upon
the *note select: af. module primitives.  Users are encouraged to use
this module instead, unless they want precise control over the OS-level
primitives used.

It defines a *note BaseSelector: 331b. abstract base class, along with
several concrete implementations (*note KqueueSelector: 3209, *note
EpollSelector: b7c...), that can be used to wait for I/O readiness
notification on multiple file objects.  In the following, "file object"
refers to any object with a *note fileno(): 2732. method, or a raw file
descriptor.  See *note file object: 115b.

*note DefaultSelector: 331c. is an alias to the most efficient
implementation available on the current platform: this should be the
default choice for most users.

     備註: The type of file objects supported depends on the platform:
     on Windows, sockets are supported, but not pipes, whereas on Unix,
     both are supported (some other types may be supported as well, such
     as fifos or special file devices).

也參考
......

*note select: af.

     Low-level I/O multiplexing module.

*note Availability: 1c56.: not WASI.

This module does not work or is not available on WebAssembly.  See *note
WebAssembly 平台: 16e6. for more information.


File: python.info,  Node: Classes<3>,  Next: 範例<27>,  Prev: 簡介<8>,  Up: selectors --- 高階 I/O 多工

5.18.5.2 Classes
................

Classes hierarchy:

     BaseSelector
     +-- SelectSelector
     +-- PollSelector
     +-- EpollSelector
     +-- DevpollSelector
     +-- KqueueSelector

In the following, 'events' is a bitwise mask indicating which I/O events
should be waited for on a given file object.  It can be a combination of
the modules constants below:

     Constant                    含義
                                 
     --------------------------------------------------------------------------------
                                 
      -- 資料:                   Available for read
               selectors.EVENT_READ

      -- 資料:                   Available for write
               selectors.EVENT_WRITE

 -- 類別: selectors.SelectorKey

     A *note SelectorKey: 3320. is a *note namedtuple: 1ae. used to
     associate a file object to its underlying file descriptor, selected
     event mask and attached data.  It is returned by several *note
     BaseSelector: 331b. methods.

      -- 屬性: fileobj

          File object registered.

      -- 屬性: fd

          Underlying file descriptor.

      -- 屬性: events

          Events that must be waited for on this file object.

      -- 屬性: data

          Optional opaque data associated to this file object: for
          example, this could be used to store a per-client session ID.

 -- 類別: selectors.BaseSelector

     A *note BaseSelector: 331b. is used to wait for I/O event readiness
     on multiple file objects.  It supports file stream registration,
     unregistration, and a method to wait for I/O events on those
     streams, with an optional timeout.  It's an abstract base class, so
     cannot be instantiated.  Use *note DefaultSelector: 331c. instead,
     or one of *note SelectSelector: 3206, *note KqueueSelector: 3209.
     etc.  if you want to specifically use an implementation, and your
     platform supports it.  *note BaseSelector: 331b. and its concrete
     implementations support the *note context manager: 576. protocol.

      -- 方法: abstractmethod register (fileobj, events, data=None)

          Register a file object for selection, monitoring it for I/O
          events.

          'fileobj' is the file object to monitor.  It may either be an
          integer file descriptor or an object with a ‘fileno()’ method.
          'events' is a bitwise mask of events to monitor.  'data' is an
          opaque object.

          This returns a new *note SelectorKey: 3320. instance, or
          raises a *note ValueError: 1e7. in case of invalid event mask
          or file descriptor, or *note KeyError: 2fb. if the file object
          is already registered.

      -- 方法: abstractmethod unregister (fileobj)

          Unregister a file object from selection, removing it from
          monitoring.  A file object shall be unregistered prior to
          being closed.

          'fileobj' must be a file object previously registered.

          This returns the associated *note SelectorKey: 3320. instance,
          or raises a *note KeyError: 2fb. if 'fileobj' is not
          registered.  It will raise *note ValueError: 1e7. if 'fileobj'
          is invalid (e.g.  it has no ‘fileno()’ method or its
          ‘fileno()’ method has an invalid return value).

      -- 方法: modify (fileobj, events, data=None)

          Change a registered file object's monitored events or attached
          data.

          This is equivalent to ‘BaseSelector.unregister(fileobj)’
          followed by ‘BaseSelector.register(fileobj, events, data)’,
          except that it can be implemented more efficiently.

          This returns a new *note SelectorKey: 3320. instance, or
          raises a *note ValueError: 1e7. in case of invalid event mask
          or file descriptor, or *note KeyError: 2fb. if the file object
          is not registered.

      -- 方法: abstractmethod select (timeout=None)

          Wait until some registered file objects become ready, or the
          timeout expires.

          If ‘timeout > 0’, this specifies the maximum wait time, in
          seconds.  If ‘timeout <= 0’, the call won't block, and will
          report the currently ready file objects.  If 'timeout' is
          ‘None’, the call will block until a monitored file object
          becomes ready.

          This returns a list of ‘(key, events)’ tuples, one for each
          ready file object.

          'key' is the *note SelectorKey: 3320. instance corresponding
          to a ready file object.  'events' is a bitmask of events ready
          on this file object.

               備註: This method can return before any file object
               becomes ready or the timeout has elapsed if the current
               process receives a signal: in this case, an empty list
               will be returned.

          在 3.5 版的變更: The selector is now retried with a recomputed
          timeout when interrupted by a signal if the signal handler did
          not raise an exception (see PEP 475(1) for the rationale),
          instead of returning an empty list of events before the
          timeout.

      -- 方法: close ()

          Close the selector.

          This must be called to make sure that any underlying resource
          is freed.  The selector shall not be used once it has been
          closed.

      -- 方法: get_key (fileobj)

          Return the key associated with a registered file object.

          This returns the *note SelectorKey: 3320. instance associated
          to this file object, or raises *note KeyError: 2fb. if the
          file object is not registered.

      -- 方法: abstractmethod get_map ()

          Return a mapping of file objects to selector keys.

          This returns a *note Mapping: 86f. instance mapping registered
          file objects to their associated *note SelectorKey: 3320.
          instance.

 -- 類別: selectors.DefaultSelector

     The default selector class, using the most efficient implementation
     available on the current platform.  This should be the default
     choice for most users.

 -- 類別: selectors.SelectSelector

     *note select.select(): d46.-based selector.

 -- 類別: selectors.PollSelector

     *note select.poll(): 2a99.-based selector.

 -- 類別: selectors.EpollSelector

     *note select.epoll(): f36.-based selector.

      -- 方法: fileno ()

          This returns the file descriptor used by the underlying *note
          select.epoll(): f36. object.

 -- 類別: selectors.DevpollSelector

     *note select.devpoll(): f38.-based selector.

      -- 方法: fileno ()

          This returns the file descriptor used by the underlying *note
          select.devpoll(): f38. object.

     在 3.5 版被加入.

 -- 類別: selectors.KqueueSelector

     *note select.kqueue(): 15c8.-based selector.

      -- 方法: fileno ()

          This returns the file descriptor used by the underlying *note
          select.kqueue(): 15c8. object.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0475/


File: python.info,  Node: 範例<27>,  Prev: Classes<3>,  Up: selectors --- 高階 I/O 多工

5.18.5.3 範例
.............

Here is a simple echo server implementation:

     import selectors
     import socket

     sel = selectors.DefaultSelector()

     def accept(sock, mask):
         conn, addr = sock.accept()  # Should be ready
         print('accepted', conn, 'from', addr)
         conn.setblocking(False)
         sel.register(conn, selectors.EVENT_READ, read)

     def read(conn, mask):
         data = conn.recv(1000)  # Should be ready
         if data:
             print('echoing', repr(data), 'to', conn)
             conn.send(data)  # Hope it won't block
         else:
             print('closing', conn)
             sel.unregister(conn)
             conn.close()

     sock = socket.socket()
     sock.bind(('localhost', 1234))
     sock.listen(100)
     sock.setblocking(False)
     sel.register(sock, selectors.EVENT_READ, accept)

     while True:
         events = sel.select()
         for key, mask in events:
             callback = key.data
             callback(key.fileobj, mask)


File: python.info,  Node: signal --- 設定非同步事件的處理函式,  Next: mmap --- 記憶體映射檔案的支援,  Prev: selectors --- 高階 I/O 多工,  Up: Networking and Interprocess Communication

5.18.6 ‘signal’ -- 設定非同步事件的處理函式
-------------------------------------------

'原始碼：'Lib/signal.py(1)

__________________________________________________________________

This module provides mechanisms to use signal handlers in Python.

* Menu:

* General rules::
* 模組內容: 模組內容<5>.
* 範例: 範例<28>.
* Note on SIGPIPE::
* Note on Signal Handlers and Exceptions::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/signal.py


File: python.info,  Node: General rules,  Next: 模組內容<5>,  Up: signal --- 設定非同步事件的處理函式

5.18.6.1 General rules
......................

The *note signal.signal(): 10cd. function allows defining custom
handlers to be executed when a signal is received.  A small number of
default handlers are installed: *note SIGPIPE: 3332. is ignored (so
write errors on pipes and sockets can be reported as ordinary Python
exceptions) and *note SIGINT: 7e8. is translated into a *note
KeyboardInterrupt: 975. exception if the parent process has not changed
it.

A handler for a particular signal, once set, remains installed until it
is explicitly reset (Python emulates the BSD style interface regardless
of the underlying implementation), with the exception of the handler for
*note SIGCHLD: 2ad5, which follows the underlying implementation.

On WebAssembly platforms, signals are emulated and therefore behave
differently.  Several functions and signals are not available on these
platforms.

* Menu:

* Execution of Python signal handlers::
* Signals and threads::


File: python.info,  Node: Execution of Python signal handlers,  Next: Signals and threads,  Up: General rules

5.18.6.2 Execution of Python signal handlers
............................................

A Python signal handler does not get executed inside the low-level (C)
signal handler.  Instead, the low-level signal handler sets a flag which
tells the *note virtual machine: 3334. to execute the corresponding
Python signal handler at a later point(for example at the next *note
bytecode: 16d. instruction).  This has consequences:

   * It makes little sense to catch synchronous errors like *note
     SIGFPE: 1c4c. or *note SIGSEGV: 1c4b. that are caused by an invalid
     operation in C code.  Python will return from the signal handler to
     the C code, which is likely to raise the same signal again, causing
     Python to apparently hang.  From Python 3.3 onwards, you can use
     the *note faulthandler: 4e. module to report on synchronous errors.

   * A long-running calculation implemented purely in C (such as regular
     expression matching on a large body of text) may run uninterrupted
     for an arbitrary amount of time, regardless of any signals
     received.  The Python signal handlers will be called when the
     calculation finishes.

   * If the handler raises an exception, it will be raised "out of thin
     air" in the main thread.  See the *note note below: 2167. for a
     discussion.


File: python.info,  Node: Signals and threads,  Prev: Execution of Python signal handlers,  Up: General rules

5.18.6.3 Signals and threads
............................

Python signal handlers are always executed in the main Python thread of
the main interpreter, even if the signal was received in another thread.
This means that signals can't be used as a means of inter-thread
communication.  You can use the synchronization primitives from the
*note threading: d6. module instead.

Besides, only the main thread of the main interpreter is allowed to set
a new signal handler.


File: python.info,  Node: 模組內容<5>,  Next: 範例<28>,  Prev: General rules,  Up: signal --- 設定非同步事件的處理函式

5.18.6.4 模組內容
.................

在 3.5 版的變更: signal (SIG*), handler (*note SIG_DFL: 1726, *note
SIG_IGN: 1725.) and sigmask (*note SIG_BLOCK: 3338, *note SIG_UNBLOCK:
3339, *note SIG_SETMASK: 333a.) related constants listed below were
turned into *note enums: c86. (*note Signals: 333b, *note Handlers:
333c. and *note Sigmasks: 333d. respectively).  *note getsignal(): 15a4,
*note pthread_sigmask(): 10c9, *note sigpending(): 10cb. and *note
sigwait(): 10cc. functions return human-readable *note enums: c86. as
*note Signals: 333b. objects.

The signal module defines three enums:

 -- 類別: signal.Signals

     *note enum.IntEnum: c86. collection of SIG* constants and the
     CTRL_* constants.

     在 3.5 版被加入.

 -- 類別: signal.Handlers

     *note enum.IntEnum: c86. collection the constants *note SIG_DFL:
     1726. and *note SIG_IGN: 1725.

     在 3.5 版被加入.

 -- 類別: signal.Sigmasks

     *note enum.IntEnum: c86. collection the constants *note SIG_BLOCK:
     3338, *note SIG_UNBLOCK: 3339. and *note SIG_SETMASK: 333a.

     *note 適用: 1c56.：Unix。

     更多資訊請見 ‘sigprocmask(2)(1)’ 與 ‘pthread_sigmask(3)(2)’ 手冊頁
     。

     在 3.5 版被加入.

The variables defined in the *note signal: b4. module are:

 -- 資料: signal.SIG_DFL

     This is one of two standard signal handling options; it will simply
     perform the default function for the signal.  For example, on most
     systems the default action for ‘SIGQUIT’ is to dump core and exit,
     while the default action for *note SIGCHLD: 2ad5. is to simply
     ignore it.

 -- 資料: signal.SIG_IGN

     This is another standard signal handler, which will simply ignore
     the given signal.

 -- 資料: signal.SIGABRT

     Abort signal from ‘abort(3)(3)’.

 -- 資料: signal.SIGALRM

     Timer signal from ‘alarm(2)(4)’.

     *note 適用: 1c56.：Unix。

 -- 資料: signal.SIGBREAK

     Interrupt from keyboard (CTRL + BREAK).

     *note 適用: 1c56.：Windows。

 -- 資料: signal.SIGBUS

     Bus error (bad memory access).

     *note 適用: 1c56.：Unix。

 -- 資料: signal.SIGCHLD

     Child process stopped or terminated.

     *note 適用: 1c56.：Unix。

 -- 資料: signal.SIGCLD

     *note SIGCHLD: 2ad5. 的別名。

     *note 適用: 1c56.：非 macOS。

 -- 資料: signal.SIGCONT

     Continue the process if it is currently stopped

     *note 適用: 1c56.：Unix。

 -- 資料: signal.SIGFPE

     Floating-point exception.  For example, division by zero.

     也參考
     ......

     *note ZeroDivisionError: 8e9. is raised when the second argument of
     a division or modulo operation is zero.

 -- 資料: signal.SIGHUP

     Hangup detected on controlling terminal or death of controlling
     process.

     *note 適用: 1c56.：Unix。

 -- 資料: signal.SIGILL

     Illegal instruction.

 -- 資料: signal.SIGINT

     Interrupt from keyboard (CTRL + C).

     Default action is to raise *note KeyboardInterrupt: 975.

 -- 資料: signal.SIGKILL

     Kill signal.

     It cannot be caught, blocked, or ignored.

     *note 適用: 1c56.：Unix。

 -- 資料: signal.SIGPIPE

     Broken pipe: write to pipe with no readers.

     Default action is to ignore the signal.

     *note 適用: 1c56.：Unix。

 -- 資料: signal.SIGSEGV

     Segmentation fault: invalid memory reference.

 -- 資料: signal.SIGSTKFLT

          Stack fault on coprocessor.  The Linux kernel does not raise
          this signal: it can only be raised in user space.

     *note 適用: 1c56.：Linux。

     On architectures where the signal is available.  See the man page
     ‘signal(7)(5)’ for further information.

     在 3.11 版被加入.

 -- 資料: signal.SIGTERM

     Termination signal.

 -- 資料: signal.SIGUSR1

     User-defined signal 1.

     *note 適用: 1c56.：Unix。

 -- 資料: signal.SIGUSR2

     User-defined signal 2.

     *note 適用: 1c56.：Unix。

 -- 資料: signal.SIGWINCH

     Window resize signal.

     *note 適用: 1c56.：Unix。

 -- 資料: SIG*

     All the signal numbers are defined symbolically.  For example, the
     hangup signal is defined as *note signal.SIGHUP: 3341.; the
     variable names are identical to the names used in C programs, as
     found in ‘<signal.h>’.  The Unix man page for '‘signal()’' lists
     the existing signals (on some systems this is ‘signal(2)(6)’, on
     others the list is in ‘signal(7)(7)’).  Note that not all systems
     define the same set of signal names; only those names defined by
     the system are defined by this module.

 -- 資料: signal.CTRL_C_EVENT

     The signal corresponding to the ‘Ctrl+C’ keystroke event.  This
     signal can only be used with *note os.kill(): 12f4.

     *note 適用: 1c56.：Windows。

     在 3.2 版被加入.

 -- 資料: signal.CTRL_BREAK_EVENT

     The signal corresponding to the ‘Ctrl+Break’ keystroke event.  This
     signal can only be used with *note os.kill(): 12f4.

     *note 適用: 1c56.：Windows。

     在 3.2 版被加入.

 -- 資料: signal.NSIG

     One more than the number of the highest signal number.  Use *note
     valid_signals(): 3346. to get valid signal numbers.

 -- 資料: signal.ITIMER_REAL

     Decrements interval timer in real time, and delivers *note SIGALRM:
     333e. upon expiration.

 -- 資料: signal.ITIMER_VIRTUAL

     Decrements interval timer only when the process is executing, and
     delivers SIGVTALRM upon expiration.

 -- 資料: signal.ITIMER_PROF

     Decrements interval timer both when the process executes and when
     the system is executing on behalf of the process.  Coupled with
     ITIMER_VIRTUAL, this timer is usually used to profile the time
     spent by the application in user and kernel space.  SIGPROF is
     delivered upon expiration.

 -- 資料: signal.SIG_BLOCK

     A possible value for the 'how' parameter to *note
     pthread_sigmask(): 10c9. indicating that signals are to be blocked.

     在 3.3 版被加入.

 -- 資料: signal.SIG_UNBLOCK

     A possible value for the 'how' parameter to *note
     pthread_sigmask(): 10c9. indicating that signals are to be
     unblocked.

     在 3.3 版被加入.

 -- 資料: signal.SIG_SETMASK

     A possible value for the 'how' parameter to *note
     pthread_sigmask(): 10c9. indicating that the signal mask is to be
     replaced.

     在 3.3 版被加入.

The *note signal: b4. module defines one exception:

 -- 例外: signal.ItimerError

     Raised to signal an error from the underlying *note setitimer():
     334b. or *note getitimer(): 334c. implementation.  Expect this
     error if an invalid interval timer or a negative time is passed to
     *note setitimer(): 334b.  This error is a subtype of *note OSError:
     350.

     在 3.3 版被加入: This error used to be a subtype of *note IOError:
     ff5, which is now an alias of *note OSError: 350.

The *note signal: b4. module defines the following functions:

 -- 函式: signal.alarm (time)

     If 'time' is non-zero, this function requests that a *note SIGALRM:
     333e. signal be sent to the process in 'time' seconds.  Any
     previously scheduled alarm is canceled (only one alarm can be
     scheduled at any time).  The returned value is then the number of
     seconds before any previously set alarm was to have been delivered.
     If 'time' is zero, no alarm is scheduled, and any scheduled alarm
     is canceled.  If the return value is zero, no alarm is currently
     scheduled.

     *note 適用: 1c56.：Unix。

     更多資訊請見 ‘alarm(2)(8)’ 手冊頁。

 -- 函式: signal.getsignal (signalnum)

     Return the current signal handler for the signal 'signalnum'.  The
     returned value may be a callable Python object, or one of the
     special values *note signal.SIG_IGN: 1725, *note signal.SIG_DFL:
     1726. or *note None: 61b.  Here, *note signal.SIG_IGN: 1725. means
     that the signal was previously ignored, *note signal.SIG_DFL: 1726.
     means that the default way of handling the signal was previously in
     use, and ‘None’ means that the previous signal handler was not
     installed from Python.

 -- 函式: signal.strsignal (signalnum)

     Returns the description of signal 'signalnum', such as "Interrupt"
     for *note SIGINT: 7e8.  Returns *note None: 61b. if 'signalnum' has
     no description.  Raises *note ValueError: 1e7. if 'signalnum' is
     invalid.

     在 3.8 版被加入.

 -- 函式: signal.valid_signals ()

     Return the set of valid signal numbers on this platform.  This can
     be less than ‘range(1, NSIG)’ if some signals are reserved by the
     system for internal use.

     在 3.8 版被加入.

 -- 函式: signal.pause ()

     Cause the process to sleep until a signal is received; the
     appropriate handler will then be called.  Returns nothing.

     *note 適用: 1c56.：Unix。

     更多資訊請見 ‘signal(2)(9)’ 手冊頁。

     See also *note sigwait(): 10cc, *note sigwaitinfo(): d51, *note
     sigtimedwait(): d50. and *note sigpending(): 10cb.

 -- 函式: signal.raise_signal (signum)

     Sends a signal to the calling process.  Returns nothing.

     在 3.8 版被加入.

 -- 函式: signal.pidfd_send_signal (pidfd, sig, siginfo=None, flags=0)

     Send signal 'sig' to the process referred to by file descriptor
     'pidfd'.  Python does not currently support the 'siginfo'
     parameter; it must be ‘None’.  The 'flags' argument is provided for
     future extensions; no flag values are currently defined.

     更多資訊請見 ‘pidfd_send_signal(2)(10)’ 手冊頁。

     *note 適用: 1c56.：Linux 5.1 以上

     在 3.9 版被加入.

 -- 函式: signal.pthread_kill (thread_id, signalnum)

     Send the signal 'signalnum' to the thread 'thread_id', another
     thread in the same process as the caller.  The target thread can be
     executing any code (Python or not).  However, if the target thread
     is executing the Python interpreter, the Python signal handlers
     will be *note executed by the main thread of the main interpreter:
     3336.  Therefore, the only point of sending a signal to a
     particular Python thread would be to force a running system call to
     fail with *note InterruptedError: d2e.

     Use *note threading.get_ident(): 10f3. or the *note ident: 2b2b.
     attribute of *note threading.Thread: 8f0. objects to get a suitable
     value for 'thread_id'.

     If 'signalnum' is 0, then no signal is sent, but error checking is
     still performed; this can be used to check if the target thread is
     still running.

     引發一個附帶引數 ‘thread_id’、‘signalnum’ 的*note 稽核事件: 17bd.
     ‘signal.pthread_kill’。

     *note 適用: 1c56.：Unix。

     更多資訊請見 ‘pthread_kill(3)(11)’ 手冊頁。

     另請參閱 *note os.kill(): 12f4.。

     在 3.3 版被加入.

 -- 函式: signal.pthread_sigmask (how, mask)

     Fetch and/or change the signal mask of the calling thread.  The
     signal mask is the set of signals whose delivery is currently
     blocked for the caller.  Return the old signal mask as a set of
     signals.

     The behavior of the call is dependent on the value of 'how', as
     follows.

        * *note SIG_BLOCK: 3338.: The set of blocked signals is the
          union of the current set and the 'mask' argument.

        * *note SIG_UNBLOCK: 3339.: The signals in 'mask' are removed
          from the current set of blocked signals.  It is permissible to
          attempt to unblock a signal which is not blocked.

        * *note SIG_SETMASK: 333a.: The set of blocked signals is set to
          the 'mask' argument.

     'mask' is a set of signal numbers (e.g.  {*note signal.SIGINT: 7e8,
     *note signal.SIGTERM: 134d.}).  Use *note valid_signals(): 3346.
     for a full mask including all signals.

     For example, ‘signal.pthread_sigmask(signal.SIG_BLOCK, [])’ reads
     the signal mask of the calling thread.

     *note SIGKILL: 3342. and ‘SIGSTOP’ cannot be blocked.

     *note 適用: 1c56.：Unix。

     更多資訊請見 ‘sigprocmask(2)(12)’ 與 ‘pthread_sigmask(3)(13)’ 手冊
     頁。

     另請參閱 *note pause(): 334e.、*note sigpending(): 10cb. 與 *note
     sigwait(): 10cc.。

     在 3.3 版被加入.

 -- 函式: signal.setitimer (which, seconds, interval=0.0)

     Sets given interval timer (one of *note signal.ITIMER_REAL: 3347,
     *note signal.ITIMER_VIRTUAL: 3348. or *note signal.ITIMER_PROF:
     3349.) specified by 'which' to fire after 'seconds' (float is
     accepted, different from *note alarm(): 334d.) and after that every
     'interval' seconds (if 'interval' is non-zero).  The interval timer
     specified by 'which' can be cleared by setting 'seconds' to zero.

     When an interval timer fires, a signal is sent to the process.  The
     signal sent is dependent on the timer being used; *note
     signal.ITIMER_REAL: 3347. will deliver *note SIGALRM: 333e, *note
     signal.ITIMER_VIRTUAL: 3348. sends ‘SIGVTALRM’, and *note
     signal.ITIMER_PROF: 3349. will deliver ‘SIGPROF’.

     The old values are returned as a tuple: (delay, interval).

     Attempting to pass an invalid interval timer will cause an *note
     ItimerError: 334a.

     *note 適用: 1c56.：Unix。

 -- 函式: signal.getitimer (which)

     Returns current value of a given interval timer specified by
     'which'.

     *note 適用: 1c56.：Unix。

 -- 函式: signal.set_wakeup_fd (fd, *, warn_on_full_buffer=True)

     Set the wakeup file descriptor to 'fd'.  When a signal is received,
     the signal number is written as a single byte into the fd.  This
     can be used by a library to wakeup a poll or select call, allowing
     the signal to be fully processed.

     The old wakeup fd is returned (or -1 if file descriptor wakeup was
     not enabled).  If 'fd' is -1, file descriptor wakeup is disabled.
     If not -1, 'fd' must be non-blocking.  It is up to the library to
     remove any bytes from 'fd' before calling poll or select again.

     When threads are enabled, this function can only be called from
     *note the main thread of the main interpreter: 3336.; attempting to
     call it from other threads will cause a *note ValueError: 1e7.
     exception to be raised.

     There are two common ways to use this function.  In both
     approaches, you use the fd to wake up when a signal arrives, but
     then they differ in how they determine 'which' signal or signals
     have arrived.

     In the first approach, we read the data out of the fd's buffer, and
     the byte values give you the signal numbers.  This is simple, but
     in rare cases it can run into a problem: generally the fd will have
     a limited amount of buffer space, and if too many signals arrive
     too quickly, then the buffer may become full, and some signals may
     be lost.  If you use this approach, then you should set
     ‘warn_on_full_buffer=True’, which will at least cause a warning to
     be printed to stderr when signals are lost.

     In the second approach, we use the wakeup fd 'only' for wakeups,
     and ignore the actual byte values.  In this case, all we care about
     is whether the fd's buffer is empty or non-empty; a full buffer
     doesn't indicate a problem at all.  If you use this approach, then
     you should set ‘warn_on_full_buffer=False’, so that your users are
     not confused by spurious warning messages.

     在 3.5 版的變更: On Windows, the function now also supports socket
     handles.

     在 3.7 版的變更: 新增 ‘warn_on_full_buffer’ 參數。

 -- 函式: signal.siginterrupt (signalnum, flag)

     Change system call restart behaviour: if 'flag' is *note False:
     adb, system calls will be restarted when interrupted by signal
     'signalnum', otherwise system calls will be interrupted.  Returns
     nothing.

     *note 適用: 1c56.：Unix。

     更多資訊請見 ‘siginterrupt(3)(14)’ 手冊頁。

     Note that installing a signal handler with *note signal(): b4. will
     reset the restart behaviour to interruptible by implicitly calling
     ‘siginterrupt()’ with a true 'flag' value for the given signal.

 -- 函式: signal.signal (signalnum, handler)

     Set the handler for signal 'signalnum' to the function 'handler'.
     'handler' can be a callable Python object taking two arguments (see
     below), or one of the special values *note signal.SIG_IGN: 1725. or
     *note signal.SIG_DFL: 1726.  The previous signal handler will be
     returned (see the description of *note getsignal(): 15a4. above).
     (See the Unix man page ‘signal(2)(15)’ for further information.)

     When threads are enabled, this function can only be called from
     *note the main thread of the main interpreter: 3336.; attempting to
     call it from other threads will cause a *note ValueError: 1e7.
     exception to be raised.

     The 'handler' is called with two arguments: the signal number and
     the current stack frame (‘None’ or a frame object; for a
     description of frame objects, see the *note description in the type
     hierarchy: 27e. or see the attribute descriptions in the *note
     inspect: 72. module).

     On Windows, *note signal(): b4. can only be called with *note
     SIGABRT: 1c4d, *note SIGFPE: 1c4c, *note SIGILL: 1c4f, *note
     SIGINT: 7e8, *note SIGSEGV: 1c4b, *note SIGTERM: 134d, or *note
     SIGBREAK: 333f.  A *note ValueError: 1e7. will be raised in any
     other case.  Note that not all systems define the same set of
     signal names; an *note AttributeError: 2f6. will be raised if a
     signal name is not defined as ‘SIG*’ module level constant.

 -- 函式: signal.sigpending ()

     Examine the set of signals that are pending for delivery to the
     calling thread (i.e., the signals which have been raised while
     blocked).  Return the set of the pending signals.

     *note 適用: 1c56.：Unix。

     更多資訊請見 ‘sigpending(2)(16)’ 手冊頁。

     另請參閱 *note pause(): 334e.、*note pthread_sigmask(): 10c9. 與
     *note sigwait(): 10cc.。

     在 3.3 版被加入.

 -- 函式: signal.sigwait (sigset)

     Suspend execution of the calling thread until the delivery of one
     of the signals specified in the signal set 'sigset'.  The function
     accepts the signal (removes it from the pending list of signals),
     and returns the signal number.

     *note 適用: 1c56.：Unix。

     更多資訊請見 ‘sigwait(3)(17)’ 手冊頁。

     See also *note pause(): 334e, *note pthread_sigmask(): 10c9, *note
     sigpending(): 10cb, *note sigwaitinfo(): d51. and *note
     sigtimedwait(): d50.

     在 3.3 版被加入.

 -- 函式: signal.sigwaitinfo (sigset)

     Suspend execution of the calling thread until the delivery of one
     of the signals specified in the signal set 'sigset'.  The function
     accepts the signal and removes it from the pending list of signals.
     If one of the signals in 'sigset' is already pending for the
     calling thread, the function will return immediately with
     information about that signal.  The signal handler is not called
     for the delivered signal.  The function raises an *note
     InterruptedError: d2e. if it is interrupted by a signal that is not
     in 'sigset'.

     The return value is an object representing the data contained in
     the ‘siginfo_t’ structure, namely: ‘si_signo’, ‘si_code’,
     ‘si_errno’, ‘si_pid’, ‘si_uid’, ‘si_status’, ‘si_band’.

     *note 適用: 1c56.：Unix。

     更多資訊請見 ‘sigwaitinfo(2)(18)’ 手冊頁。

     另請參閱 *note pause(): 334e.、*note sigwait(): 10cc. 與 *note
     sigtimedwait(): d50.。

     在 3.3 版被加入.

     在 3.5 版的變更: The function is now retried if interrupted by a
     signal not in 'sigset' and the signal handler does not raise an
     exception (see PEP 475(19) for the rationale).

 -- 函式: signal.sigtimedwait (sigset, timeout)

     Like *note sigwaitinfo(): d51, but takes an additional 'timeout'
     argument specifying a timeout.  If 'timeout' is specified as ‘0’, a
     poll is performed.  Returns *note None: 61b. if a timeout occurs.

     *note 適用: 1c56.：Unix。

     更多資訊請見 ‘sigtimedwait(2)(20)’ 手冊頁。

     另請參閱 *note pause(): 334e.、*note sigwait(): 10cc. 與 *note
     sigwaitinfo(): d51.。

     在 3.3 版被加入.

     在 3.5 版的變更: The function is now retried with the recomputed
     'timeout' if interrupted by a signal not in 'sigset' and the signal
     handler does not raise an exception (see PEP 475(21) for the
     rationale).

   ---------- Footnotes ----------

   (1) https://manpages.debian.org/sigprocmask(2)

   (2) https://manpages.debian.org/pthread_sigmask(3)

   (3) https://manpages.debian.org/abort(3)

   (4) https://manpages.debian.org/alarm(2)

   (5) https://manpages.debian.org/signal(7)

   (6) https://manpages.debian.org/signal(2)

   (7) https://manpages.debian.org/signal(7)

   (8) https://manpages.debian.org/alarm(2)

   (9) https://manpages.debian.org/signal(2)

   (10) https://manpages.debian.org/pidfd_send_signal(2)

   (11) https://manpages.debian.org/pthread_kill(3)

   (12) https://manpages.debian.org/sigprocmask(2)

   (13) https://manpages.debian.org/pthread_sigmask(3)

   (14) https://manpages.debian.org/siginterrupt(3)

   (15) https://manpages.debian.org/signal(2)

   (16) https://manpages.debian.org/sigpending(2)

   (17) https://manpages.debian.org/sigwait(3)

   (18) https://manpages.debian.org/sigwaitinfo(2)

   (19) https://peps.python.org/pep-0475/

   (20) https://manpages.debian.org/sigtimedwait(2)

   (21) https://peps.python.org/pep-0475/


File: python.info,  Node: 範例<28>,  Next: Note on SIGPIPE,  Prev: 模組內容<5>,  Up: signal --- 設定非同步事件的處理函式

5.18.6.5 範例
.............

Here is a minimal example program.  It uses the *note alarm(): 334d.
function to limit the time spent waiting to open a file; this is useful
if the file is for a serial device that may not be turned on, which
would normally cause the *note os.open(): d38. to hang indefinitely.
The solution is to set a 5-second alarm before opening the file; if the
operation takes too long, the alarm signal will be sent, and the handler
raises an exception.

     import signal, os

     def handler(signum, frame):
         signame = signal.Signals(signum).name
         print(f'Signal handler called with signal {signame} ({signum})')
         raise OSError("Couldn't open device!")

     # Set the signal handler and a 5-second alarm
     signal.signal(signal.SIGALRM, handler)
     signal.alarm(5)

     # This open() may hang indefinitely
     fd = os.open('/dev/ttyS0', os.O_RDWR)

     signal.alarm(0)          # Disable the alarm


File: python.info,  Node: Note on SIGPIPE,  Next: Note on Signal Handlers and Exceptions,  Prev: 範例<28>,  Up: signal --- 設定非同步事件的處理函式

5.18.6.6 Note on SIGPIPE
........................

Piping output of your program to tools like ‘head(1)(1)’ will cause a
*note SIGPIPE: 3332. signal to be sent to your process when the receiver
of its standard output closes early.  This results in an exception like
‘BrokenPipeError: [Errno 32] Broken pipe’.  To handle this case, wrap
your entry point to catch this exception as follows:

     import os
     import sys

     def main():
         try:
             # simulate large output (your code replaces this loop)
             for x in range(10000):
                 print("y")
             # flush output here to force SIGPIPE to be triggered
             # while inside this try block.
             sys.stdout.flush()
         except BrokenPipeError:
             # Python flushes standard streams on exit; redirect remaining output
             # to devnull to avoid another BrokenPipeError at shutdown
             devnull = os.open(os.devnull, os.O_WRONLY)
             os.dup2(devnull, sys.stdout.fileno())
             sys.exit(1)  # Python exits with error code 1 on EPIPE

     if __name__ == '__main__':
         main()

Do not set *note SIGPIPE: 3332.'s disposition to *note SIG_DFL: 1726. in
order to avoid *note BrokenPipeError: fff.  Doing that would cause your
program to exit unexpectedly whenever any socket connection is
interrupted while your program is still writing to it.

   ---------- Footnotes ----------

   (1) https://manpages.debian.org/head(1)


File: python.info,  Node: Note on Signal Handlers and Exceptions,  Prev: Note on SIGPIPE,  Up: signal --- 設定非同步事件的處理函式

5.18.6.7 Note on Signal Handlers and Exceptions
...............................................

If a signal handler raises an exception, the exception will be
propagated to the main thread and may be raised after any *note
bytecode: 16d. instruction.  Most notably, a *note KeyboardInterrupt:
975. may appear at any point during execution.  Most Python code,
including the standard library, cannot be made robust against this, and
so a *note KeyboardInterrupt: 975. (or any other exception resulting
from a signal handler) may on rare occasions put the program in an
unexpected state.

To illustrate this issue, consider the following code:

     class SpamContext:
         def __init__(self):
             self.lock = threading.Lock()

         def __enter__(self):
             # If KeyboardInterrupt occurs here, everything is fine
             self.lock.acquire()
             # If KeyboardInterrupt occurs here, __exit__ will not be called
             ...
             # KeyboardInterrupt could occur just before the function returns

         def __exit__(self, exc_type, exc_val, exc_tb):
             ...
             self.lock.release()

For many programs, especially those that merely want to exit on *note
KeyboardInterrupt: 975, this is not a problem, but applications that are
complex or require high reliability should avoid raising exceptions from
signal handlers.  They should also avoid catching *note
KeyboardInterrupt: 975. as a means of gracefully shutting down.
Instead, they should install their own *note SIGINT: 7e8. handler.
Below is an example of an HTTP server that avoids *note
KeyboardInterrupt: 975.:

     import signal
     import socket
     from selectors import DefaultSelector, EVENT_READ
     from http.server import HTTPServer, SimpleHTTPRequestHandler

     interrupt_read, interrupt_write = socket.socketpair()

     def handler(signum, frame):
         print('Signal handler called with signal', signum)
         interrupt_write.send(b'\0')
     signal.signal(signal.SIGINT, handler)

     def serve_forever(httpd):
         sel = DefaultSelector()
         sel.register(interrupt_read, EVENT_READ)
         sel.register(httpd, EVENT_READ)

         while True:
             for key, _ in sel.select():
                 if key.fileobj == interrupt_read:
                     interrupt_read.recv(1)
                     return
                 if key.fileobj == httpd:
                     httpd.handle_request()

     print("Serving on port 8000")
     httpd = HTTPServer(('', 8000), SimpleHTTPRequestHandler)
     serve_forever(httpd)
     print("Shutdown...")


File: python.info,  Node: mmap --- 記憶體映射檔案的支援,  Prev: signal --- 設定非同步事件的處理函式,  Up: Networking and Interprocess Communication

5.18.7 ‘mmap’ -- 記憶體映射檔案的支援
-------------------------------------

__________________________________________________________________

*note Availability: 1c56.: not WASI.

This module does not work or is not available on WebAssembly.  See *note
WebAssembly 平台: 16e6. for more information.

Memory-mapped file objects behave like both *note bytearray: 4e3. and
like *note file objects: 115b.  You can use mmap objects in most places
where *note bytearray: 4e3. are expected; for example, you can use the
*note re: a7. module to search through a memory-mapped file.  You can
also change a single byte by doing ‘obj[index] = 97’, or change a
subsequence by assigning to a slice: ‘obj[i1:i2] = b'...'’.  You can
also read and write data starting at the current file position, and
‘seek()’ through the file to different positions.

A memory-mapped file is created by the *note mmap: 1f0. constructor,
which is different on Unix and on Windows.  In either case you must
provide a file descriptor for a file opened for update.  If you wish to
map an existing Python file object, use its *note fileno(): 2732. method
to obtain the correct value for the 'fileno' parameter.  Otherwise, you
can open the file using the *note os.open(): d38. function, which
returns a file descriptor directly (the file still needs to be closed
when done).

     備註: If you want to create a memory-mapping for a writable,
     buffered file, you should *note flush(): 2b03. the file first.
     This is necessary to ensure that local modifications to the buffers
     are actually available to the mapping.

For both the Unix and Windows versions of the constructor, 'access' may
be specified as an optional keyword parameter.  'access' accepts one of
four values: ‘ACCESS_READ’, ‘ACCESS_WRITE’, or ‘ACCESS_COPY’ to specify
read-only, write-through or copy-on-write memory respectively, or
‘ACCESS_DEFAULT’ to defer to 'prot'.  'access' can be used on both Unix
and Windows.  If 'access' is not specified, Windows mmap returns a
write-through mapping.  The initial memory values for all three access
types are taken from the specified file.  Assignment to an ‘ACCESS_READ’
memory map raises a *note TypeError: 4dd. exception.  Assignment to an
‘ACCESS_WRITE’ memory map affects both memory and the underlying file.
Assignment to an ‘ACCESS_COPY’ memory map affects memory but does not
update the underlying file.

在 3.7 版的變更: 新增 ‘ACCESS_DEFAULT’ 常數。

To map anonymous memory, -1 should be passed as the fileno along with
the length.

 -- 類別: mmap.mmap (fileno, length, tagname=None,
          access=ACCESS_DEFAULT, offset=0)

     '(Windows version)' Maps 'length' bytes from the file specified by
     the file handle 'fileno', and creates a mmap object.  If 'length'
     is larger than the current size of the file, the file is extended
     to contain 'length' bytes.  If 'length' is ‘0’, the maximum length
     of the map is the current size of the file, except that if the file
     is empty Windows raises an exception (you cannot create an empty
     mapping on Windows).

     'tagname', if specified and not ‘None’, is a string giving a tag
     name for the mapping.  Windows allows you to have many different
     mappings against the same file.  If you specify the name of an
     existing tag, that tag is opened, otherwise a new tag of this name
     is created.  If this parameter is omitted or ‘None’, the mapping is
     created without a name.  Avoiding the use of the 'tagname'
     parameter will assist in keeping your code portable between Unix
     and Windows.

     'offset' may be specified as a non-negative integer offset.  mmap
     references will be relative to the offset from the beginning of the
     file.  'offset' defaults to 0.  'offset' must be a multiple of the
     ‘ALLOCATIONGRANULARITY’.

     引發一個附帶引數 ‘fileno’、‘length’、‘access’、‘offset’ 的*note
     稽核事件: 17bd. ‘mmap.__new__’。

 -- 類別: mmap.mmap (fileno, length, flags=MAP_SHARED, prot=PROT_WRITE |
          PROT_READ, access=ACCESS_DEFAULT, offset=0, *, trackfd=True)

     '(Unix version)' Maps 'length' bytes from the file specified by the
     file descriptor 'fileno', and returns a mmap object.  If 'length'
     is ‘0’, the maximum length of the map will be the current size of
     the file when *note mmap: 1f0. is called.

     'flags' specifies the nature of the mapping.  *note MAP_PRIVATE:
     3355. creates a private copy-on-write mapping, so changes to the
     contents of the mmap object will be private to this process, and
     *note MAP_SHARED: 3356. creates a mapping that's shared with all
     other processes mapping the same areas of the file.  The default
     value is *note MAP_SHARED: 3356.  Some systems have additional
     possible flags with the full list specified in *note MAP_*
     constants: 3357.

     'prot', if specified, gives the desired memory protection; the two
     most useful values are ‘PROT_READ’ and ‘PROT_WRITE’, to specify
     that the pages may be read or written.  'prot' defaults to
     ‘PROT_READ | PROT_WRITE’.

     'access' may be specified in lieu of 'flags' and 'prot' as an
     optional keyword parameter.  It is an error to specify both
     'flags', 'prot' and 'access'.  See the description of 'access'
     above for information on how to use this parameter.

     'offset' may be specified as a non-negative integer offset.  mmap
     references will be relative to the offset from the beginning of the
     file.  'offset' defaults to 0.  'offset' must be a multiple of
     ‘ALLOCATIONGRANULARITY’ which is equal to ‘PAGESIZE’ on Unix
     systems.

     If 'trackfd' is ‘False’, the file descriptor specified by 'fileno'
     will not be duplicated, and the resulting ‘mmap’ object will not be
     associated with the map's underlying file.  This means that the
     *note size(): 3358. and *note resize(): 3359. methods will fail.
     This mode is useful to limit the number of open file descriptors.

     To ensure validity of the created memory mapping the file specified
     by the descriptor 'fileno' is internally automatically synchronized
     with the physical backing store on macOS.

     在 3.13 版的變更: The 'trackfd' parameter was added.

     This example shows a simple way of using *note mmap: 1f0.:

          import mmap

          # write a simple example file
          with open("hello.txt", "wb") as f:
              f.write(b"Hello Python!\n")

          with open("hello.txt", "r+b") as f:
              # memory-map the file, size 0 means whole file
              mm = mmap.mmap(f.fileno(), 0)
              # read content via standard file methods
              print(mm.readline())  # prints b"Hello Python!\n"
              # read content via slice notation
              print(mm[:5])  # prints b"Hello"
              # update content using slice notation;
              # note that new content must have same size
              mm[6:] = b" world!\n"
              # ... and read again using standard file methods
              mm.seek(0)
              print(mm.readline())  # prints b"Hello  world!\n"
              # close the map
              mm.close()

     *note mmap: 1f0. can also be used as a context manager in a *note
     with: 577. statement:

          import mmap

          with mmap.mmap(-1, 13) as mm:
              mm.write(b"Hello world!")

     在 3.2 版被加入: Context manager support.

     The next example demonstrates how to create an anonymous map and
     exchange data between the parent and child processes:

          import mmap
          import os

          mm = mmap.mmap(-1, 13)
          mm.write(b"Hello world!")

          pid = os.fork()

          if pid == 0:  # 在子行程中
              mm.seek(0)
              print(mm.readline())

              mm.close()

     引發一個附帶引數 ‘fileno’、‘length’、‘access’、‘offset’ 的*note
     稽核事件: 17bd. ‘mmap.__new__’。

     Memory-mapped file objects support the following methods:

      -- 方法: close ()

          Closes the mmap.  Subsequent calls to other methods of the
          object will result in a ValueError exception being raised.
          This will not close the open file.

      -- 屬性: closed

          ‘True’ if the file is closed.

          在 3.2 版被加入.

      -- 方法: find (sub[, start[, end]])

          Returns the lowest index in the object where the subsequence
          'sub' is found, such that 'sub' is contained in the range
          ['start', 'end'].  Optional arguments 'start' and 'end' are
          interpreted as in slice notation.  Returns ‘-1’ on failure.

          在 3.5 版的變更: Writable *note bytes-like object: cd4. is now
          accepted.

      -- 方法: flush ([offset[, size]])

          Flushes changes made to the in-memory copy of a file back to
          disk.  Without use of this call there is no guarantee that
          changes are written back before the object is destroyed.  If
          'offset' and 'size' are specified, only changes to the given
          range of bytes will be flushed to disk; otherwise, the whole
          extent of the mapping is flushed.  'offset' must be a multiple
          of the ‘PAGESIZE’ or ‘ALLOCATIONGRANULARITY’.

          ‘None’ is returned to indicate success.  An exception is
          raised when the call failed.

          在 3.8 版的變更: Previously, a nonzero value was returned on
          success; zero was returned on error under Windows.  A zero
          value was returned on success; an exception was raised on
          error under Unix.

      -- 方法: madvise (option[, start[, length]])

          Send advice 'option' to the kernel about the memory region
          beginning at 'start' and extending 'length' bytes.  'option'
          must be one of the *note MADV_* constants: 335d. available on
          the system.  If 'start' and 'length' are omitted, the entire
          mapping is spanned.  On some systems (including Linux),
          'start' must be a multiple of the ‘PAGESIZE’.

          Availability: Systems with the ‘madvise()’ system call.

          在 3.8 版被加入.

      -- 方法: move (dest, src, count)

          Copy the 'count' bytes starting at offset 'src' to the
          destination index 'dest'.  If the mmap was created with
          ‘ACCESS_READ’, then calls to move will raise a *note
          TypeError: 4dd. exception.

      -- 方法: read ([n])

          Return a *note bytes: 1a5. containing up to 'n' bytes starting
          from the current file position.  If the argument is omitted,
          ‘None’ or negative, return all bytes from the current file
          position to the end of the mapping.  The file position is
          updated to point after the bytes that were returned.

          在 3.3 版的變更: Argument can be omitted or ‘None’.

      -- 方法: read_byte ()

          Returns a byte at the current file position as an integer, and
          advances the file position by 1.

      -- 方法: readline ()

          Returns a single line, starting at the current file position
          and up to the next newline.  The file position is updated to
          point after the bytes that were returned.

      -- 方法: resize (newsize)

          Resizes the map and the underlying file, if any.

          Resizing a map created with 'access' of ‘ACCESS_READ’ or
          ‘ACCESS_COPY’, will raise a *note TypeError: 4dd. exception.
          Resizing a map created with with 'trackfd' set to ‘False’,
          will raise a *note ValueError: 1e7. exception.

          'On Windows': Resizing the map will raise an *note OSError:
          350. if there are other maps against the same named file.
          Resizing an anonymous map (ie against the pagefile) will
          silently create a new map with the original data copied over
          up to the length of the new size.

          在 3.11 版的變更: Correctly fails if attempting to resize when
          another map is held Allows resize against an anonymous map on
          Windows

      -- 方法: rfind (sub[, start[, end]])

          Returns the highest index in the object where the subsequence
          'sub' is found, such that 'sub' is contained in the range
          ['start', 'end'].  Optional arguments 'start' and 'end' are
          interpreted as in slice notation.  Returns ‘-1’ on failure.

          在 3.5 版的變更: Writable *note bytes-like object: cd4. is now
          accepted.

      -- 方法: seek (pos[, whence])

          Set the file's current position.  'whence' argument is
          optional and defaults to ‘os.SEEK_SET’ or ‘0’ (absolute file
          positioning); other values are ‘os.SEEK_CUR’ or ‘1’ (seek
          relative to the current position) and ‘os.SEEK_END’ or ‘2’
          (seek relative to the file's end).

          在 3.13 版的變更: Return the new absolute position instead of
          ‘None’.

      -- 方法: seekable ()

          Return whether the file supports seeking, and the return value
          is always ‘True’.

          在 3.13 版被加入.

      -- 方法: size ()

          Return the length of the file, which can be larger than the
          size of the memory-mapped area.

      -- 方法: tell ()

          Returns the current position of the file pointer.

      -- 方法: write (bytes)

          Write the bytes in 'bytes' into memory at the current position
          of the file pointer and return the number of bytes written
          (never less than ‘len(bytes)’, since if the write fails, a
          *note ValueError: 1e7. will be raised).  The file position is
          updated to point after the bytes that were written.  If the
          mmap was created with ‘ACCESS_READ’, then writing to it will
          raise a *note TypeError: 4dd. exception.

          在 3.5 版的變更: Writable *note bytes-like object: cd4. is now
          accepted.

          在 3.6 版的變更: The number of bytes written is now returned.

      -- 方法: write_byte (byte)

          Write the integer 'byte' into memory at the current position
          of the file pointer; the file position is advanced by ‘1’.  If
          the mmap was created with ‘ACCESS_READ’, then writing to it
          will raise a *note TypeError: 4dd. exception.

* Menu:

* MADV_* Constants::
* MAP_* 常數::


File: python.info,  Node: MADV_* Constants,  Next: MAP_* 常數,  Up: mmap --- 記憶體映射檔案的支援

5.18.7.1 MADV_* Constants
.........................

 -- 資料: mmap.MADV_NORMAL
 -- 資料: mmap.MADV_RANDOM
 -- 資料: mmap.MADV_SEQUENTIAL
 -- 資料: mmap.MADV_WILLNEED
 -- 資料: mmap.MADV_DONTNEED
 -- 資料: mmap.MADV_REMOVE
 -- 資料: mmap.MADV_DONTFORK
 -- 資料: mmap.MADV_DOFORK
 -- 資料: mmap.MADV_HWPOISON
 -- 資料: mmap.MADV_MERGEABLE
 -- 資料: mmap.MADV_UNMERGEABLE
 -- 資料: mmap.MADV_SOFT_OFFLINE
 -- 資料: mmap.MADV_HUGEPAGE
 -- 資料: mmap.MADV_NOHUGEPAGE
 -- 資料: mmap.MADV_DONTDUMP
 -- 資料: mmap.MADV_DODUMP
 -- 資料: mmap.MADV_FREE
 -- 資料: mmap.MADV_NOSYNC
 -- 資料: mmap.MADV_AUTOSYNC
 -- 資料: mmap.MADV_NOCORE
 -- 資料: mmap.MADV_CORE
 -- 資料: mmap.MADV_PROTECT
 -- 資料: mmap.MADV_FREE_REUSABLE
 -- 資料: mmap.MADV_FREE_REUSE

     These options can be passed to *note mmap.madvise(): 9ac.  Not
     every option will be present on every system.

     Availability: Systems with the madvise() system call.

     在 3.8 版被加入.


File: python.info,  Node: MAP_* 常數,  Prev: MADV_* Constants,  Up: mmap --- 記憶體映射檔案的支援

5.18.7.2 MAP_* 常數
...................

 -- 資料: mmap.MAP_SHARED
 -- 資料: mmap.MAP_PRIVATE
 -- 資料: mmap.MAP_32BIT
 -- 資料: mmap.MAP_ALIGNED_SUPER
 -- 資料: mmap.MAP_ANON
 -- 資料: mmap.MAP_ANONYMOUS
 -- 資料: mmap.MAP_CONCEAL
 -- 資料: mmap.MAP_DENYWRITE
 -- 資料: mmap.MAP_EXECUTABLE
 -- 資料: mmap.MAP_HASSEMAPHORE
 -- 資料: mmap.MAP_JIT
 -- 資料: mmap.MAP_NOCACHE
 -- 資料: mmap.MAP_NOEXTEND
 -- 資料: mmap.MAP_NORESERVE
 -- 資料: mmap.MAP_POPULATE
 -- 資料: mmap.MAP_RESILIENT_CODESIGN
 -- 資料: mmap.MAP_RESILIENT_MEDIA
 -- 資料: mmap.MAP_STACK
 -- 資料: mmap.MAP_TPRO
 -- 資料: mmap.MAP_TRANSLATED_ALLOW_EXECUTE
 -- 資料: mmap.MAP_UNIX03

     These are the various flags that can be passed to *note
     mmap.mmap(): 1f0.  *note MAP_ALIGNED_SUPER: 1658. is only available
     at FreeBSD and *note MAP_CONCEAL: 1659. is only available at
     OpenBSD. Note that some options might not be present on some
     systems.

     在 3.10 版的變更: 新增 *note MAP_POPULATE: 184a. 常數。

     在 3.11 版被加入: 新增 *note MAP_STACK: 3383. 常數。

     在 3.12 版被加入: Added *note MAP_ALIGNED_SUPER: 1658. and *note
     MAP_CONCEAL: 1659. constants.

     在 3.13 版被加入: Added *note MAP_32BIT: 1597, *note
     MAP_HASSEMAPHORE: 1592, *note MAP_JIT: 1594, *note MAP_NOCACHE:
     1593, *note MAP_NOEXTEND: 1591, *note MAP_NORESERVE: 1590, *note
     MAP_RESILIENT_CODESIGN: 1595, *note MAP_RESILIENT_MEDIA: 1596,
     *note MAP_TPRO: 159a, *note MAP_TRANSLATED_ALLOW_EXECUTE: 1598, and
     *note MAP_UNIX03: 1599. constants.


File: python.info,  Node: 網際網路資料處理,  Next: Structured Markup Processing Tools,  Prev: Networking and Interprocess Communication,  Up: Python 標準函式庫 Standard Library

5.19 網際網路資料處理
=====================

本章描述了支援網際網路上處理常用資料格式的模組。

* Menu:

* email: email --- 郵件和 MIME 處理套件. 郵件和 MIME 處理套件
* json: json --- JSON 編碼器與解碼器. JSON 編碼器與解碼器
* mailbox: mailbox --- 以各種格式操作郵件信箱. 以各種格式操作郵件信箱
* mimetypes: mimetypes --- 將檔案名稱對映到 MIME 類型. 將檔案名稱對映到 MIME 類型
* base64: base64 --- Base16、Base32、Base64、Base85 資料編碼. Base16、Base32、Base64、Base85 資料編碼
* binascii: binascii --- 在二進位制和 ASCII 之間轉換. 在二進位制和 ASCII 之間轉換
* quopri: quopri --- 編碼和解碼 MIME 可列印字元資料. 編碼和解碼 MIME 可列印字元資料


File: python.info,  Node: email --- 郵件和 MIME 處理套件,  Next: json --- JSON 編碼器與解碼器,  Up: 網際網路資料處理

5.19.1 ‘email’ -- 郵件和 MIME 處理套件
--------------------------------------

'原始碼：'Lib/email/__init__.py(1)

__________________________________________________________________

The *note email: 32. package is a library for managing email messages.
It is specifically 'not' designed to do any sending of email messages to
SMTP ( RFC 2821(2)), NNTP, or other servers; those are functions of
modules such as *note smtplib: b7.  The *note email: 32. package
attempts to be as RFC-compliant as possible, supporting RFC 5322(3) and
RFC 6532(4), as well as such MIME-related RFCs as RFC 2045(5), RFC
2046(6), RFC 2047(7), RFC 2183(8), and RFC 2231(9).

The overall structure of the email package can be divided into three
major components, plus a fourth component that controls the behavior of
the other components.

The central component of the package is an "object model" that
represents email messages.  An application interacts with the package
primarily through the object model interface defined in the *note
message: 3b. sub-module.  The application can use this API to ask
questions about an existing email, to construct a new email, or to add
or remove email subcomponents that themselves use the same object model
interface.  That is, following the nature of email messages and their
MIME subcomponents, the email object model is a tree structure of
objects that all provide the *note EmailMessage: 260. API.

The other two major components of the package are the *note parser: 45.
and the *note generator: 37.  The parser takes the serialized version of
an email message (a stream of bytes) and converts it into a tree of
*note EmailMessage: 260. objects.  The generator takes an *note
EmailMessage: 260. and turns it back into a serialized byte stream.
(The parser and generator also handle streams of text characters, but
this usage is discouraged as it is too easy to end up with messages that
are not valid in one way or another.)

The control component is the *note policy: 46. module.  Every *note
EmailMessage: 260, every *note generator: 37, and every *note parser:
45. has an associated *note policy: 46. object that controls its
behavior.  Usually an application only needs to specify the policy when
an *note EmailMessage: 260. is created, either by directly instantiating
an *note EmailMessage: 260. to create a new email, or by parsing an
input stream using a *note parser: 45.  But the policy can be changed
when the message is serialized using a *note generator: 37.  This
allows, for example, a generic email message to be parsed from disk, but
to serialize it using standard SMTP settings when sending it to an email
server.

The email package does its best to hide the details of the various
governing RFCs from the application.  Conceptually the application
should be able to treat the email message as a structured tree of
unicode text and binary attachments, without having to worry about how
these are represented when serialized.  In practice, however, it is
often necessary to be aware of at least some of the rules governing MIME
messages and their structure, specifically the names and nature of the
MIME "content types" and how they identify multipart documents.  For the
most part this knowledge should only be required for more complex
applications, and even then it should only be the high level structure
in question, and not the details of how those structures are
represented.  Since MIME content types are used widely in modern
internet software (not just email), this will be a familiar concept to
many programmers.

The following sections describe the functionality of the *note email:
32. package.  We start with the *note message: 3b. object model, which
is the primary interface an application will use, and follow that with
the *note parser: 45. and *note generator: 37. components.  Then we
cover the *note policy: 46. controls, which completes the treatment of
the main components of the library.

The next three sections cover the exceptions the package may raise and
the defects (non-compliance with the RFCs) that the *note parser: 45.
may detect.  Then we cover the *note headerregistry: 39. and the *note
contentmanager: 34. sub-components, which provide tools for doing more
detailed manipulation of headers and payloads, respectively.  Both of
these components contain features relevant to consuming and producing
non-trivial messages, but also document their extensibility APIs, which
will be of interest to advanced applications.

Following those is a set of examples of using the fundamental parts of
the APIs covered in the preceding sections.

The foregoing represent the modern (unicode friendly) API of the email
package.  The remaining sections, starting with the *note Message: 261.
class, cover the legacy *note compat32: c40. API that deals much more
directly with the details of how email messages are represented.  The
*note compat32: c40. API does 'not' hide the details of the RFCs from
the application, but for applications that need to operate at that
level, they can be useful tools.  This documentation is also relevant
for applications that are still using the *note compat32: c40. API for
backward compatibility reasons.

在 3.6 版的變更: Docs reorganized and rewritten to promote the new *note
EmailMessage: 260./*note EmailPolicy: 1051. API.

Contents of the *note email: 32. package documentation:

* Menu:

* email.message：表示電子郵件訊息: email message：表示電子郵件訊息.
* email.parser：剖析電子郵件訊息: email parser：剖析電子郵件訊息.
* email.generator：產生 MIME 文件: email generator：產生 MIME 文件.
* email.policy; Policy Objects: email policy Policy Objects.
* email.errors：例外和缺陷類別: email errors：例外和缺陷類別.
* email.headerregistry：自訂標頭物件: email headerregistry：自訂標頭物件.
* email.contentmanager：管理 MIME 內容: email contentmanager：管理 MIME 內容.
* email：範例::
* email.message.Message; Representing an email message using the compat32 API: email message Message Representing an email message using the compat32 API.
* email.mime：從頭開始建立電子郵件和 MIME 物件: email mime：從頭開始建立電子郵件和 MIME 物件.
* email.header：國際化標頭: email header：國際化標頭.
* email.charset：表示字元集合: email charset：表示字元集合.
* email.encoders：編碼器: email encoders：編碼器.
* email.utils：雜項工具: email utils：雜項工具.
* email.iterators：疊代器: email iterators：疊代器.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/email/__init__.py

   (2) https://datatracker.ietf.org/doc/html/rfc2821.html

   (3) https://datatracker.ietf.org/doc/html/rfc5322.html

   (4) https://datatracker.ietf.org/doc/html/rfc6532.html

   (5) https://datatracker.ietf.org/doc/html/rfc2045.html

   (6) https://datatracker.ietf.org/doc/html/rfc2046.html

   (7) https://datatracker.ietf.org/doc/html/rfc2047.html

   (8) https://datatracker.ietf.org/doc/html/rfc2183.html

   (9) https://datatracker.ietf.org/doc/html/rfc2231.html


File: python.info,  Node: email message：表示電子郵件訊息,  Next: email parser：剖析電子郵件訊息,  Up: email --- 郵件和 MIME 處理套件

5.19.1.1 ‘email.message’：表示電子郵件訊息
..........................................

'原始碼：'Lib/email/message.py(1)

__________________________________________________________________

在 3.6 版被加入: (2)

The central class in the *note email: 32. package is the *note
EmailMessage: 260. class, imported from the *note email.message: 3b.
module.  It is the base class for the *note email: 32. object model.
*note EmailMessage: 260. provides the core functionality for setting and
querying header fields, for accessing message bodies, and for creating
or modifying structured messages.

An email message consists of 'headers' and a 'payload' (which is also
referred to as the 'content').  Headers are RFC 5322(3) or RFC 6532(4)
style field names and values, where the field name and value are
separated by a colon.  The colon is not part of either the field name or
the field value.  The payload may be a simple text message, or a binary
object, or a structured sequence of sub-messages each with their own set
of headers and their own payload.  The latter type of payload is
indicated by the message having a MIME type such as ‘multipart/*’ or
‘message/rfc822’.

The conceptual model provided by an *note EmailMessage: 260. object is
that of an ordered dictionary of headers coupled with a 'payload' that
represents the RFC 5322(5) body of the message, which might be a list of
sub-‘EmailMessage’ objects.  In addition to the normal dictionary
methods for accessing the header names and values, there are methods for
accessing specialized information from the headers (for example the MIME
content type), for operating on the payload, for generating a serialized
version of the message, and for recursively walking over the object
tree.

The *note EmailMessage: 260. dictionary-like interface is indexed by the
header names, which must be ASCII values.  The values of the dictionary
are strings with some extra methods.  Headers are stored and returned in
case-preserving form, but field names are matched case-insensitively.
The keys are ordered, but unlike a real dict, there can be duplicates.
Additional methods are provided for working with headers that have
duplicate keys.

The 'payload' is either a string or bytes object, in the case of simple
message objects, or a list of *note EmailMessage: 260. objects, for MIME
container documents such as ‘multipart/*’ and ‘message/rfc822’ message
objects.

 -- 類別: email.message.EmailMessage (policy=default)

     If 'policy' is specified use the rules it specifies to update and
     serialize the representation of the message.  If 'policy' is not
     set, use the *note default: 338c. policy, which follows the rules
     of the email RFCs except for line endings (instead of the RFC
     mandated ‘\r\n’, it uses the Python standard ‘\n’ line endings).
     For more information see the *note policy: 46. documentation.

      -- 方法: as_string (unixfrom=False, maxheaderlen=None,
               policy=None)

          Return the entire message flattened as a string.  When
          optional 'unixfrom' is true, the envelope header is included
          in the returned string.  'unixfrom' defaults to ‘False’.  For
          backward compatibility with the base *note Message: 261. class
          'maxheaderlen' is accepted, but defaults to ‘None’, which
          means that by default the line length is controlled by the
          *note max_line_length: 338e. of the policy.  The 'policy'
          argument may be used to override the default policy obtained
          from the message instance.  This can be used to control some
          of the formatting produced by the method, since the specified
          'policy' will be passed to the *note Generator: 1166.

          Flattening the message may trigger changes to the *note
          EmailMessage: 260. if defaults need to be filled in to
          complete the transformation to a string (for example, MIME
          boundaries may be generated or modified).

          Note that this method is provided as a convenience and may not
          be the most useful way to serialize messages in your
          application, especially if you are dealing with multiple
          messages.  See *note email.generator.Generator: 1166. for a
          more flexible API for serializing messages.  Note also that
          this method is restricted to producing messages serialized as
          "7 bit clean" when *note utf8: d9e. is ‘False’, which is the
          default.

          在 3.6 版的變更: the default behavior when 'maxheaderlen' is
          not specified was changed from defaulting to 0 to defaulting
          to the value of 'max_line_length' from the policy.

      -- 方法: __str__ ()

          Equivalent to
          ‘as_string(policy=self.policy.clone(utf8=True))’.  Allows
          ‘str(msg)’ to produce a string containing the serialized
          message in a readable format.

          在 3.4 版的變更: the method was changed to use ‘utf8=True’,
          thus producing an RFC 6531(6)-like message representation,
          instead of being a direct alias for *note as_string(): 338d.

      -- 方法: as_bytes (unixfrom=False, policy=None)

          Return the entire message flattened as a bytes object.  When
          optional 'unixfrom' is true, the envelope header is included
          in the returned string.  'unixfrom' defaults to ‘False’.  The
          'policy' argument may be used to override the default policy
          obtained from the message instance.  This can be used to
          control some of the formatting produced by the method, since
          the specified 'policy' will be passed to the *note
          BytesGenerator: 1167.

          Flattening the message may trigger changes to the *note
          EmailMessage: 260. if defaults need to be filled in to
          complete the transformation to a string (for example, MIME
          boundaries may be generated or modified).

          Note that this method is provided as a convenience and may not
          be the most useful way to serialize messages in your
          application, especially if you are dealing with multiple
          messages.  See *note email.generator.BytesGenerator: 1167. for
          a more flexible API for serializing messages.

      -- 方法: __bytes__ ()

          Equivalent to *note as_bytes(): 3390.  Allows ‘bytes(msg)’ to
          produce a bytes object containing the serialized message.

      -- 方法: is_multipart ()

          Return ‘True’ if the message's payload is a list of sub-*note
          EmailMessage: 260. objects, otherwise return ‘False’.  When
          *note is_multipart(): 3392. returns ‘False’, the payload
          should be a string object (which might be a CTE encoded binary
          payload).  Note that *note is_multipart(): 3392. returning
          ‘True’ does not necessarily mean that
          "msg.get_content_maintype() == 'multipart'" will return the
          ‘True’.  For example, ‘is_multipart’ will return ‘True’ when
          the *note EmailMessage: 260. is of type ‘message/rfc822’.

      -- 方法: set_unixfrom (unixfrom)

          Set the message's envelope header to 'unixfrom', which should
          be a string.  (See *note mboxMessage: 3394. for a brief
          description of this header.)

      -- 方法: get_unixfrom ()

          Return the message's envelope header.  Defaults to ‘None’ if
          the envelope header was never set.

     The following methods implement the mapping-like interface for
     accessing the message's headers.  Note that there are some semantic
     differences between these methods and a normal mapping (i.e.
     dictionary) interface.  For example, in a dictionary there are no
     duplicate keys, but here there may be duplicate message headers.
     Also, in dictionaries there is no guaranteed order to the keys
     returned by *note keys(): 3396, but in an *note EmailMessage: 260.
     object, headers are always returned in the order they appeared in
     the original message, or in which they were added to the message
     later.  Any header deleted and then re-added is always appended to
     the end of the header list.

     These semantic differences are intentional and are biased toward
     convenience in the most common use cases.

     Note that in all cases, any envelope header present in the message
     is not included in the mapping interface.

      -- 方法: __len__ ()

          Return the total number of headers, including duplicates.

      -- 方法: __contains__ (name)

          Return ‘True’ if the message object has a field named 'name'.
          Matching is done without regard to case and 'name' does not
          include the trailing colon.  Used for the ‘in’ operator.  For
          example:

               if 'message-id' in myMessage:
                  print('Message-ID:', myMessage['message-id'])

      -- 方法: __getitem__ (name)

          Return the value of the named header field.  'name' does not
          include the colon field separator.  If the header is missing,
          ‘None’ is returned; a *note KeyError: 2fb. is never raised.

          Note that if the named field appears more than once in the
          message's headers, exactly which of those field values will be
          returned is undefined.  Use the *note get_all(): 339a. method
          to get the values of all the extant headers named 'name'.

          Using the standard (non-‘compat32’) policies, the returned
          value is an instance of a subclass of *note
          email.headerregistry.BaseHeader: 339b.

      -- 方法: __setitem__ (name, val)

          Add a header to the message with field name 'name' and value
          'val'.  The field is appended to the end of the message's
          existing headers.

          Note that this does 'not' overwrite or delete any existing
          header with the same name.  If you want to ensure that the new
          header is the only one present in the message with field name
          'name', delete the field first, e.g.:

               del msg['subject']
               msg['subject'] = 'Python roolz!'

          If the *note policy: 46. defines certain headers to be unique
          (as the standard policies do), this method may raise a *note
          ValueError: 1e7. when an attempt is made to assign a value to
          such a header when one already exists.  This behavior is
          intentional for consistency's sake, but do not depend on it as
          we may choose to make such assignments do an automatic
          deletion of the existing header in the future.

      -- 方法: __delitem__ (name)

          Delete all occurrences of the field with name 'name' from the
          message's headers.  No exception is raised if the named field
          isn't present in the headers.

      -- 方法: keys ()

          Return a list of all the message's header field names.

      -- 方法: values ()

          Return a list of all the message's field values.

      -- 方法: items ()

          Return a list of 2-tuples containing all the message's field
          headers and values.

      -- 方法: get (name, failobj=None)

          Return the value of the named header field.  This is identical
          to *note __getitem__(): 266. except that optional 'failobj' is
          returned if the named header is missing ('failobj' defaults to
          ‘None’).

     Here are some additional useful header related methods:

      -- 方法: get_all (name, failobj=None)

          Return a list of all the values for the field named 'name'.
          If there are no such named headers in the message, 'failobj'
          is returned (defaults to ‘None’).

      -- 方法: add_header (_name, _value, **_params)

          Extended header setting.  This method is similar to *note
          __setitem__(): 339c. except that additional header parameters
          can be provided as keyword arguments.  '_name' is the header
          field to add and '_value' is the 'primary' value for the
          header.

          For each item in the keyword argument dictionary '_params',
          the key is taken as the parameter name, with underscores
          converted to dashes (since dashes are illegal in Python
          identifiers).  Normally, the parameter will be added as
          ‘key="value"’ unless the value is ‘None’, in which case only
          the key will be added.

          If the value contains non-ASCII characters, the charset and
          language may be explicitly controlled by specifying the value
          as a three tuple in the format ‘(CHARSET, LANGUAGE, VALUE)’,
          where ‘CHARSET’ is a string naming the charset to be used to
          encode the value, ‘LANGUAGE’ can usually be set to ‘None’ or
          the empty string (see RFC 2231(7) for other possibilities),
          and ‘VALUE’ is the string value containing non-ASCII code
          points.  If a three tuple is not passed and the value contains
          non-ASCII characters, it is automatically encoded in RFC
          2231(8) format using a ‘CHARSET’ of ‘utf-8’ and a ‘LANGUAGE’
          of ‘None’.

          以下是個範例：

               msg.add_header('Content-Disposition', 'attachment', filename='bud.gif')

          This will add a header that looks like

               Content-Disposition: attachment; filename="bud.gif"

          An example of the extended interface with non-ASCII
          characters:

               msg.add_header('Content-Disposition', 'attachment',
                              filename=('iso-8859-1', '', 'Fußballer.ppt'))

      -- 方法: replace_header (_name, _value)

          Replace a header.  Replace the first header found in the
          message that matches '_name', retaining header order and field
          name case of the original header.  If no matching header is
          found, raise a *note KeyError: 2fb.

      -- 方法: get_content_type ()

          Return the message's content type, coerced to lower case of
          the form ‘maintype/subtype’.  If there is no ‘Content-Type’
          header in the message return the value returned by *note
          get_default_type(): 33a4.  If the ‘Content-Type’ header is
          invalid, return ‘text/plain’.

          (According to RFC 2045(9), messages always have a default
          type, *note get_content_type(): 33a3. will always return a
          value.  RFC 2045(10) defines a message's default type to be
          ‘text/plain’ unless it appears inside a ‘multipart/digest’
          container, in which case it would be ‘message/rfc822’.  If the
          ‘Content-Type’ header has an invalid type specification, RFC
          2045(11) mandates that the default type be ‘text/plain’.)

      -- 方法: get_content_maintype ()

          Return the message's main content type.  This is the
          ‘maintype’ part of the string returned by *note
          get_content_type(): 33a3.

      -- 方法: get_content_subtype ()

          Return the message's sub-content type.  This is the ‘subtype’
          part of the string returned by *note get_content_type(): 33a3.

      -- 方法: get_default_type ()

          Return the default content type.  Most messages have a default
          content type of ‘text/plain’, except for messages that are
          subparts of ‘multipart/digest’ containers.  Such subparts have
          a default content type of ‘message/rfc822’.

      -- 方法: set_default_type (ctype)

          Set the default content type.  'ctype' should either be
          ‘text/plain’ or ‘message/rfc822’, although this is not
          enforced.  The default content type is not stored in the
          ‘Content-Type’ header, so it only affects the return value of
          the ‘get_content_type’ methods when no ‘Content-Type’ header
          is present in the message.

      -- 方法: set_param (param, value, header='Content-Type',
               requote=True, charset=None, language='', replace=False)

          Set a parameter in the ‘Content-Type’ header.  If the
          parameter already exists in the header, replace its value with
          'value'.  When 'header' is ‘Content-Type’ (the default) and
          the header does not yet exist in the message, add it, set its
          value to ‘text/plain’, and append the new parameter value.
          Optional 'header' specifies an alternative header to
          ‘Content-Type’.

          If the value contains non-ASCII characters, the charset and
          language may be explicitly specified using the optional
          'charset' and 'language' parameters.  Optional 'language'
          specifies the RFC 2231(12) language, defaulting to the empty
          string.  Both 'charset' and 'language' should be strings.  The
          default is to use the ‘utf8’ 'charset' and ‘None’ for the
          'language'.

          If 'replace' is ‘False’ (the default) the header is moved to
          the end of the list of headers.  If 'replace' is ‘True’, the
          header will be updated in place.

          Use of the 'requote' parameter with *note EmailMessage: 260.
          objects is deprecated.

          Note that existing parameter values of headers may be accessed
          through the *note params: 33a9. attribute of the header value
          (for example, ‘msg['Content-Type'].params['charset']’).

          在 3.4 版的變更: ‘replace’ keyword was added.

      -- 方法: del_param (param, header='content-type', requote=True)

          Remove the given parameter completely from the ‘Content-Type’
          header.  The header will be re-written in place without the
          parameter or its value.  Optional 'header' specifies an
          alternative to ‘Content-Type’.

          Use of the 'requote' parameter with *note EmailMessage: 260.
          objects is deprecated.

      -- 方法: get_filename (failobj=None)

          Return the value of the ‘filename’ parameter of the
          ‘Content-Disposition’ header of the message.  If the header
          does not have a ‘filename’ parameter, this method falls back
          to looking for the ‘name’ parameter on the ‘Content-Type’
          header.  If neither is found, or the header is missing, then
          'failobj' is returned.  The returned string will always be
          unquoted as per *note email.utils.unquote(): 33ac.

      -- 方法: get_boundary (failobj=None)

          Return the value of the ‘boundary’ parameter of the
          ‘Content-Type’ header of the message, or 'failobj' if either
          the header is missing, or has no ‘boundary’ parameter.  The
          returned string will always be unquoted as per *note
          email.utils.unquote(): 33ac.

      -- 方法: set_boundary (boundary)

          Set the ‘boundary’ parameter of the ‘Content-Type’ header to
          'boundary'.  *note set_boundary(): 33ae. will always quote
          'boundary' if necessary.  A *note HeaderParseError: 33af. is
          raised if the message object has no ‘Content-Type’ header.

          Note that using this method is subtly different from deleting
          the old ‘Content-Type’ header and adding a new one with the
          new boundary via *note add_header(): 33a1, because *note
          set_boundary(): 33ae. preserves the order of the
          ‘Content-Type’ header in the list of headers.

      -- 方法: get_content_charset (failobj=None)

          Return the ‘charset’ parameter of the ‘Content-Type’ header,
          coerced to lower case.  If there is no ‘Content-Type’ header,
          or if that header has no ‘charset’ parameter, 'failobj' is
          returned.

      -- 方法: get_charsets (failobj=None)

          Return a list containing the character set names in the
          message.  If the message is a ‘multipart’, then the list will
          contain one element for each subpart in the payload,
          otherwise, it will be a list of length 1.

          Each item in the list will be a string which is the value of
          the ‘charset’ parameter in the ‘Content-Type’ header for the
          represented subpart.  If the subpart has no ‘Content-Type’
          header, no ‘charset’ parameter, or is not of the ‘text’ main
          MIME type, then that item in the returned list will be
          'failobj'.

      -- 方法: is_attachment ()

          Return ‘True’ if there is a ‘Content-Disposition’ header and
          its (case insensitive) value is ‘attachment’, ‘False’
          otherwise.

          在 3.4.2 版的變更: is_attachment is now a method instead of a
          property, for consistency with *note is_multipart(): 33b3.

      -- 方法: get_content_disposition ()

          Return the lowercased value (without parameters) of the
          message's ‘Content-Disposition’ header if it has one, or
          ‘None’.  The possible values for this method are 'inline',
          'attachment' or ‘None’ if the message follows RFC 2183(13).

          在 3.5 版被加入.

     The following methods relate to interrogating and manipulating the
     content (payload) of the message.

      -- 方法: walk ()

          The *note walk(): 33b5. method is an all-purpose generator
          which can be used to iterate over all the parts and subparts
          of a message object tree, in depth-first traversal order.  You
          will typically use *note walk(): 33b5. as the iterator in a
          ‘for’ loop; each iteration returns the next subpart.

          Here's an example that prints the MIME type of every part of a
          multipart message structure:

               >>> for part in msg.walk():
               ...     print(part.get_content_type())
               multipart/report
               text/plain
               message/delivery-status
               text/plain
               text/plain
               message/rfc822
               text/plain

          ‘walk’ iterates over the subparts of any part where *note
          is_multipart(): 3392. returns ‘True’, even though
          ‘msg.get_content_maintype() == 'multipart'’ may return
          ‘False’.  We can see this in our example by making use of the
          ‘_structure’ debug helper function:

               >>> from email.iterators import _structure
               >>> for part in msg.walk():
               ...     print(part.get_content_maintype() == 'multipart',
               ...           part.is_multipart())
               True True
               False False
               False True
               False False
               False False
               False True
               False False
               >>> _structure(msg)
               multipart/report
                   text/plain
                   message/delivery-status
                       text/plain
                       text/plain
                   message/rfc822
                       text/plain

          Here the ‘message’ parts are not ‘multiparts’, but they do
          contain subparts.  ‘is_multipart()’ returns ‘True’ and ‘walk’
          descends into the subparts.

      -- 方法: get_body (preferencelist=('related', 'html', 'plain'))

          Return the MIME part that is the best candidate to be the
          "body" of the message.

          'preferencelist' must be a sequence of strings from the set
          ‘related’, ‘html’, and ‘plain’, and indicates the order of
          preference for the content type of the part returned.

          Start looking for candidate matches with the object on which
          the ‘get_body’ method is called.

          If ‘related’ is not included in 'preferencelist', consider the
          root part (or subpart of the root part) of any related
          encountered as a candidate if the (sub-)part matches a
          preference.

          When encountering a ‘multipart/related’, check the ‘start’
          parameter and if a part with a matching ‘Content-ID’ is found,
          consider only it when looking for candidate matches.
          Otherwise consider only the first (default root) part of the
          ‘multipart/related’.

          If a part has a ‘Content-Disposition’ header, only consider
          the part a candidate match if the value of the header is
          ‘inline’.

          If none of the candidates matches any of the preferences in
          'preferencelist', return ‘None’.

          Notes: (1) For most applications the only 'preferencelist'
          combinations that really make sense are ‘('plain',)’,
          ‘('html', 'plain')’, and the default ‘('related', 'html',
          'plain')’.  (2) Because matching starts with the object on
          which ‘get_body’ is called, calling ‘get_body’ on a
          ‘multipart/related’ will return the object itself unless
          'preferencelist' has a non-default value.  (3) Messages (or
          message parts) that do not specify a ‘Content-Type’ or whose
          ‘Content-Type’ header is invalid will be treated as if they
          are of type ‘text/plain’, which may occasionally cause
          ‘get_body’ to return unexpected results.

      -- 方法: iter_attachments ()

          Return an iterator over all of the immediate sub-parts of the
          message that are not candidate "body" parts.  That is, skip
          the first occurrence of each of ‘text/plain’, ‘text/html’,
          ‘multipart/related’, or ‘multipart/alternative’ (unless they
          are explicitly marked as attachments via ‘Content-Disposition:
          attachment’), and return all remaining parts.  When applied
          directly to a ‘multipart/related’, return an iterator over the
          all the related parts except the root part (ie: the part
          pointed to by the ‘start’ parameter, or the first part if
          there is no ‘start’ parameter or the ‘start’ parameter doesn't
          match the ‘Content-ID’ of any of the parts).  When applied
          directly to a ‘multipart/alternative’ or a non-‘multipart’,
          return an empty iterator.

      -- 方法: iter_parts ()

          Return an iterator over all of the immediate sub-parts of the
          message, which will be empty for a non-‘multipart’.  (See also
          *note walk(): 33b5.)

      -- 方法: get_content (*args, content_manager=None, **kw)

          Call the *note get_content(): 33ba. method of the
          'content_manager', passing self as the message object, and
          passing along any other arguments or keywords as additional
          arguments.  If 'content_manager' is not specified, use the
          ‘content_manager’ specified by the current *note policy: 46.

      -- 方法: set_content (*args, content_manager=None, **kw)

          Call the *note set_content(): 33bb. method of the
          'content_manager', passing self as the message object, and
          passing along any other arguments or keywords as additional
          arguments.  If 'content_manager' is not specified, use the
          ‘content_manager’ specified by the current *note policy: 46.

      -- 方法: make_related (boundary=None)

          Convert a non-‘multipart’ message into a ‘multipart/related’
          message, moving any existing ‘Content-’ headers and payload
          into a (new) first part of the ‘multipart’.  If 'boundary' is
          specified, use it as the boundary string in the multipart,
          otherwise leave the boundary to be automatically created when
          it is needed (for example, when the message is serialized).

      -- 方法: make_alternative (boundary=None)

          Convert a non-‘multipart’ or a ‘multipart/related’ into a
          ‘multipart/alternative’, moving any existing ‘Content-’
          headers and payload into a (new) first part of the
          ‘multipart’.  If 'boundary' is specified, use it as the
          boundary string in the multipart, otherwise leave the boundary
          to be automatically created when it is needed (for example,
          when the message is serialized).

      -- 方法: make_mixed (boundary=None)

          Convert a non-‘multipart’, a ‘multipart/related’, or a
          ‘multipart-alternative’ into a ‘multipart/mixed’, moving any
          existing ‘Content-’ headers and payload into a (new) first
          part of the ‘multipart’.  If 'boundary' is specified, use it
          as the boundary string in the multipart, otherwise leave the
          boundary to be automatically created when it is needed (for
          example, when the message is serialized).

      -- 方法: add_related (*args, content_manager=None, **kw)

          If the message is a ‘multipart/related’, create a new message
          object, pass all of the arguments to its *note set_content():
          17ab. method, and *note attach(): 33c0. it to the ‘multipart’.
          If the message is a non-‘multipart’, call *note
          make_related(): 33bc. and then proceed as above.  If the
          message is any other type of ‘multipart’, raise a *note
          TypeError: 4dd.  If 'content_manager' is not specified, use
          the ‘content_manager’ specified by the current *note policy:
          46.  If the added part has no ‘Content-Disposition’ header,
          add one with the value ‘inline’.

      -- 方法: add_alternative (*args, content_manager=None, **kw)

          If the message is a ‘multipart/alternative’, create a new
          message object, pass all of the arguments to its *note
          set_content(): 17ab. method, and *note attach(): 33c0. it to
          the ‘multipart’.  If the message is a non-‘multipart’ or
          ‘multipart/related’, call *note make_alternative(): 33bd. and
          then proceed as above.  If the message is any other type of
          ‘multipart’, raise a *note TypeError: 4dd.  If
          'content_manager' is not specified, use the ‘content_manager’
          specified by the current *note policy: 46.

      -- 方法: add_attachment (*args, content_manager=None, **kw)

          If the message is a ‘multipart/mixed’, create a new message
          object, pass all of the arguments to its *note set_content():
          17ab. method, and *note attach(): 33c0. it to the ‘multipart’.
          If the message is a non-‘multipart’, ‘multipart/related’, or
          ‘multipart/alternative’, call *note make_mixed(): 33be. and
          then proceed as above.  If 'content_manager' is not specified,
          use the ‘content_manager’ specified by the current *note
          policy: 46.  If the added part has no ‘Content-Disposition’
          header, add one with the value ‘attachment’.  This method can
          be used both for explicit attachments (‘Content-Disposition:
          attachment’) and ‘inline’ attachments (‘Content-Disposition:
          inline’), by passing appropriate options to the
          ‘content_manager’.

      -- 方法: clear ()

          Remove the payload and all of the headers.

      -- 方法: clear_content ()

          Remove the payload and all of the ‘!Content-’ headers, leaving
          all other headers intact and in their original order.

     *note EmailMessage: 260. objects have the following instance
     attributes:

      -- 屬性: preamble

          The format of a MIME document allows for some text between the
          blank line following the headers, and the first multipart
          boundary string.  Normally, this text is never visible in a
          MIME-aware mail reader because it falls outside the standard
          MIME armor.  However, when viewing the raw text of the
          message, or when viewing the message in a non-MIME aware
          reader, this text can become visible.

          The 'preamble' attribute contains this leading extra-armor
          text for MIME documents.  When the *note Parser: 1136.
          discovers some text after the headers but before the first
          boundary string, it assigns this text to the message's
          'preamble' attribute.  When the *note Generator: 1166. is
          writing out the plain text representation of a MIME message,
          and it finds the message has a 'preamble' attribute, it will
          write this text in the area between the headers and the first
          boundary.  See *note email.parser: 45. and *note
          email.generator: 37. for details.

          Note that if the message object has no preamble, the
          'preamble' attribute will be ‘None’.

      -- 屬性: epilogue

          The 'epilogue' attribute acts the same way as the 'preamble'
          attribute, except that it contains text that appears between
          the last boundary and the end of the message.  As with the
          *note preamble: 33c5, if there is no epilog text this
          attribute will be ‘None’.

      -- 屬性: defects

          The 'defects' attribute contains a list of all the problems
          found when parsing this message.  See *note email.errors: 36.
          for a detailed description of the possible parsing defects.

 -- 類別: email.message.MIMEPart (policy=default)

     This class represents a subpart of a MIME message.  It is identical
     to *note EmailMessage: 260, except that no ‘MIME-Version’ headers
     are added when *note set_content(): 17ab. is called, since
     sub-parts do not need their own ‘MIME-Version’ headers.

註解
....

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/email/message.py

   (2) Originally added in 3.4 as a *note provisional module: fe4.  Docs
for legacy message class moved to *note email.message.Message;
Representing an email message using the compat32 API: 338b.

   (3) https://datatracker.ietf.org/doc/html/rfc5322.html

   (4) https://datatracker.ietf.org/doc/html/rfc6532.html

   (5) https://datatracker.ietf.org/doc/html/rfc5322.html

   (6) https://datatracker.ietf.org/doc/html/rfc6531.html

   (7) https://datatracker.ietf.org/doc/html/rfc2231.html

   (8) https://datatracker.ietf.org/doc/html/rfc2231.html

   (9) https://datatracker.ietf.org/doc/html/rfc2045.html

   (10) https://datatracker.ietf.org/doc/html/rfc2045.html

   (11) https://datatracker.ietf.org/doc/html/rfc2045.html

   (12) https://datatracker.ietf.org/doc/html/rfc2231.html

   (13) https://datatracker.ietf.org/doc/html/rfc2183.html


File: python.info,  Node: email parser：剖析電子郵件訊息,  Next: email generator：產生 MIME 文件,  Prev: email message：表示電子郵件訊息,  Up: email --- 郵件和 MIME 處理套件

5.19.1.2 ‘email.parser’：剖析電子郵件訊息
.........................................

'原始碼：'Lib/email/parser.py(1)

__________________________________________________________________

Message object structures can be created in one of two ways: they can be
created from whole cloth by creating an *note EmailMessage: 260. object,
adding headers using the dictionary interface, and adding payload(s)
using *note set_content(): 17ab. and related methods, or they can be
created by parsing a serialized representation of the email message.

The *note email: 32. package provides a standard parser that understands
most email document structures, including MIME documents.  You can pass
the parser a bytes, string or file object, and the parser will return to
you the root *note EmailMessage: 260. instance of the object structure.
For simple, non-MIME messages the payload of this root object will
likely be a string containing the text of the message.  For MIME
messages, the root object will return ‘True’ from its *note
is_multipart(): 3392. method, and the subparts can be accessed via the
payload manipulation methods, such as *note get_body(): 33b6, *note
iter_parts(): 33b8, and *note walk(): 33b5.

There are actually two parser interfaces available for use, the *note
Parser: 1136. API and the incremental *note FeedParser: 33ca. API. The
*note Parser: 1136. API is most useful if you have the entire text of
the message in memory, or if the entire message lives in a file on the
file system.  *note FeedParser: 33ca. is more appropriate when you are
reading the message from a stream which might block waiting for more
input (such as reading an email message from a socket).  The *note
FeedParser: 33ca. can consume and parse the message incrementally, and
only returns the root object when you close the parser.

Note that the parser can be extended in limited ways, and of course you
can implement your own parser completely from scratch.  All of the logic
that connects the *note email: 32. package's bundled parser and the
*note EmailMessage: 260. class is embodied in the *note Policy: 104d.
class, so a custom parser can create message object trees any way it
finds necessary by implementing custom versions of the appropriate
‘Policy’ methods.

* Menu:

* FeedParser API::
* Parser API::
* Additional notes::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/email/parser.py


File: python.info,  Node: FeedParser API,  Next: Parser API,  Up: email parser：剖析電子郵件訊息

5.19.1.3 FeedParser API
.......................

The *note BytesFeedParser: 1163, imported from the ‘email.feedparser’
module, provides an API that is conducive to incremental parsing of
email messages, such as would be necessary when reading the text of an
email message from a source that can block (such as a socket).  The
*note BytesFeedParser: 1163. can of course be used to parse an email
message fully contained in a *note bytes-like object: cd4, string, or
file, but the *note BytesParser: 1164. API may be more convenient for
such use cases.  The semantics and results of the two parser APIs are
identical.

The *note BytesFeedParser: 1163.'s API is simple; you create an
instance, feed it a bunch of bytes until there's no more to feed it,
then close the parser to retrieve the root message object.  The *note
BytesFeedParser: 1163. is extremely accurate when parsing
standards-compliant messages, and it does a very good job of parsing
non-compliant messages, providing information about how a message was
deemed broken.  It will populate a message object's *note defects: 33c7.
attribute with a list of any problems it found in a message.  See the
*note email.errors: 36. module for the list of defects that it can find.

Here is the API for the *note BytesFeedParser: 1163.:

 -- 類別: email.parser.BytesFeedParser (_factory=None, *,
          policy=policy.compat32)

     Create a *note BytesFeedParser: 1163. instance.  Optional
     '_factory' is a no-argument callable; if not specified use the
     *note message_factory: c3f. from the 'policy'.  Call '_factory'
     whenever a new message object is needed.

     If 'policy' is specified use the rules it specifies to update the
     representation of the message.  If 'policy' is not set, use the
     *note compat32: 104e. policy, which maintains backward
     compatibility with the Python 3.2 version of the email package and
     provides *note Message: 261. as the default factory.  All other
     policies provide *note EmailMessage: 260. as the default
     '_factory'.  For more information on what else 'policy' controls,
     see the *note policy: 46. documentation.

     Note: 'The policy keyword should always be specified'; The default
     will change to *note email.policy.default: 338c. in a future
     version of Python.

     在 3.2 版被加入.

     在 3.3 版的變更: 新增 'policy' 關鍵字。

     在 3.6 版的變更: '_factory' defaults to the policy
     ‘message_factory’.

      -- 方法: feed (data)

          Feed the parser some more data.  'data' should be a *note
          bytes-like object: cd4. containing one or more lines.  The
          lines can be partial and the parser will stitch such partial
          lines together properly.  The lines can have any of the three
          common line endings: carriage return, newline, or carriage
          return and newline (they can even be mixed).

      -- 方法: close ()

          Complete the parsing of all previously fed data and return the
          root message object.  It is undefined what happens if *note
          feed(): 33cc. is called after this method has been called.

 -- 類別: email.parser.FeedParser (_factory=None, *,
          policy=policy.compat32)

     Works like *note BytesFeedParser: 1163. except that the input to
     the *note feed(): 33cc. method must be a string.  This is of
     limited utility, since the only way for such a message to be valid
     is for it to contain only ASCII text or, if ‘utf8’ is ‘True’, no
     binary attachments.

     在 3.3 版的變更: 新增 'policy' 關鍵字。


File: python.info,  Node: Parser API,  Next: Additional notes,  Prev: FeedParser API,  Up: email parser：剖析電子郵件訊息

5.19.1.4 Parser API
...................

The *note BytesParser: 1164. class, imported from the *note
email.parser: 45. module, provides an API that can be used to parse a
message when the complete contents of the message are available in a
*note bytes-like object: cd4. or file.  The *note email.parser: 45.
module also provides *note Parser: 1136. for parsing strings, and
header-only parsers, *note BytesHeaderParser: 1055. and *note
HeaderParser: 1056, which can be used if you're only interested in the
headers of the message.  *note BytesHeaderParser: 1055. and *note
HeaderParser: 1056. can be much faster in these situations, since they
do not attempt to parse the message body, instead setting the payload to
the raw body.

 -- 類別: email.parser.BytesParser (_class=None, *,
          policy=policy.compat32)

     Create a *note BytesParser: 1164. instance.  The '_class' and
     'policy' arguments have the same meaning and semantics as the
     '_factory' and 'policy' arguments of *note BytesFeedParser: 1163.

     Note: 'The policy keyword should always be specified'; The default
     will change to *note email.policy.default: 338c. in a future
     version of Python.

     在 3.3 版的變更: Removed the 'strict' argument that was deprecated
     in 2.4.  Added the 'policy' keyword.

     在 3.6 版的變更: '_class' defaults to the policy ‘message_factory’.

      -- 方法: parse (fp, headersonly=False)

          Read all the data from the binary file-like object 'fp', parse
          the resulting bytes, and return the message object.  'fp' must
          support both the *note readline(): 12bd. and the ‘read()’
          methods.

          The bytes contained in 'fp' must be formatted as a block of
          RFC 5322(1) (or, if ‘utf8’ is ‘True’, RFC 6532(2)) style
          headers and header continuation lines, optionally preceded by
          an envelope header.  The header block is terminated either by
          the end of the data or by a blank line.  Following the header
          block is the body of the message (which may contain
          MIME-encoded subparts, including subparts with a
          ‘Content-Transfer-Encoding’ of ‘8bit’).

          Optional 'headersonly' is a flag specifying whether to stop
          parsing after reading the headers or not.  The default is
          ‘False’, meaning it parses the entire contents of the file.

      -- 方法: parsebytes (bytes, headersonly=False)

          Similar to the *note parse(): 33cf. method, except it takes a
          *note bytes-like object: cd4. instead of a file-like object.
          Calling this method on a *note bytes-like object: cd4. is
          equivalent to wrapping 'bytes' in a *note BytesIO: e46.
          instance first and calling *note parse(): 33cf.

          Optional 'headersonly' is as with the *note parse(): 33cf.
          method.

     在 3.2 版被加入.

 -- 類別: email.parser.BytesHeaderParser (_class=None, *,
          policy=policy.compat32)

     Exactly like *note BytesParser: 1164, except that 'headersonly'
     defaults to ‘True’.

     在 3.3 版被加入.

 -- 類別: email.parser.Parser (_class=None, *, policy=policy.compat32)

     This class is parallel to *note BytesParser: 1164, but handles
     string input.

     在 3.3 版的變更: Removed the 'strict' argument.  Added the 'policy'
     keyword.

     在 3.6 版的變更: '_class' defaults to the policy ‘message_factory’.

      -- 方法: parse (fp, headersonly=False)

          Read all the data from the text-mode file-like object 'fp',
          parse the resulting text, and return the root message object.
          'fp' must support both the *note readline(): 1bc0. and the
          *note read(): 1b89. methods on file-like objects.

          Other than the text mode requirement, this method operates
          like *note BytesParser.parse(): 33cf.

      -- 方法: parsestr (text, headersonly=False)

          Similar to the *note parse(): 33d1. method, except it takes a
          string object instead of a file-like object.  Calling this
          method on a string is equivalent to wrapping 'text' in a *note
          StringIO: ecb. instance first and calling *note parse(): 33d1.

          Optional 'headersonly' is as with the *note parse(): 33d1.
          method.

 -- 類別: email.parser.HeaderParser (_class=None, *,
          policy=policy.compat32)

     Exactly like *note Parser: 1136, except that 'headersonly' defaults
     to ‘True’.

Since creating a message object structure from a string or a file object
is such a common task, four functions are provided as a convenience.
They are available in the top-level *note email: 32. package namespace.

 -- 函式: email.message_from_bytes (s, _class=None, *,
          policy=policy.compat32)

     Return a message object structure from a *note bytes-like object:
     cd4.  This is equivalent to ‘BytesParser().parsebytes(s)’.
     Optional '_class' and 'policy' are interpreted as with the *note
     BytesParser: 1164. class constructor.

     在 3.2 版被加入.

     在 3.3 版的變更: Removed the 'strict' argument.  Added the 'policy'
     keyword.

 -- 函式: email.message_from_binary_file (fp, _class=None, *,
          policy=policy.compat32)

     Return a message object structure tree from an open binary *note
     file object: 115b.  This is equivalent to
     ‘BytesParser().parse(fp)’.  '_class' and 'policy' are interpreted
     as with the *note BytesParser: 1164. class constructor.

     在 3.2 版被加入.

     在 3.3 版的變更: Removed the 'strict' argument.  Added the 'policy'
     keyword.

 -- 函式: email.message_from_string (s, _class=None, *,
          policy=policy.compat32)

     Return a message object structure from a string.  This is
     equivalent to ‘Parser().parsestr(s)’.  '_class' and 'policy' are
     interpreted as with the *note Parser: 1136. class constructor.

     在 3.3 版的變更: Removed the 'strict' argument.  Added the 'policy'
     keyword.

 -- 函式: email.message_from_file (fp, _class=None, *,
          policy=policy.compat32)

     Return a message object structure tree from an open *note file
     object: 115b.  This is equivalent to ‘Parser().parse(fp)’.
     '_class' and 'policy' are interpreted as with the *note Parser:
     1136. class constructor.

     在 3.3 版的變更: Removed the 'strict' argument.  Added the 'policy'
     keyword.

     在 3.6 版的變更: '_class' defaults to the policy ‘message_factory’.

Here's an example of how you might use *note message_from_bytes(): 1161.
at an interactive Python prompt:

     >>> import email
     >>> msg = email.message_from_bytes(myBytes)

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc5322.html

   (2) https://datatracker.ietf.org/doc/html/rfc6532.html


File: python.info,  Node: Additional notes,  Prev: Parser API,  Up: email parser：剖析電子郵件訊息

5.19.1.5 Additional notes
.........................

Here are some notes on the parsing semantics:

   * Most non-‘multipart’ type messages are parsed as a single message
     object with a string payload.  These objects will return ‘False’
     for *note is_multipart(): 3392, and *note iter_parts(): 33b8. will
     yield an empty list.

   * All ‘multipart’ type messages will be parsed as a container message
     object with a list of sub-message objects for their payload.  The
     outer container message will return ‘True’ for *note
     is_multipart(): 3392, and *note iter_parts(): 33b8. will yield a
     list of subparts.

   * Most messages with a content type of ‘message/*’ (such as
     ‘message/delivery-status’ and ‘message/rfc822’) will also be parsed
     as container object containing a list payload of length 1.  Their
     *note is_multipart(): 3392. method will return ‘True’.  The single
     element yielded by *note iter_parts(): 33b8. will be a sub-message
     object.

   * Some non-standards-compliant messages may not be internally
     consistent about their ‘multipart’-edness.  Such messages may have
     a ‘Content-Type’ header of type ‘multipart’, but their *note
     is_multipart(): 3392. method may return ‘False’.  If such messages
     were parsed with the *note FeedParser: 33ca, they will have an
     instance of the ‘MultipartInvariantViolationDefect’ class in their
     'defects' attribute list.  See *note email.errors: 36. for details.


File: python.info,  Node: email generator：產生 MIME 文件,  Next: email policy Policy Objects,  Prev: email parser：剖析電子郵件訊息,  Up: email --- 郵件和 MIME 處理套件

5.19.1.6 ‘email.generator’：產生 MIME 文件
..........................................

'原始碼：'Lib/email/generator.py(1)

__________________________________________________________________

One of the most common tasks is to generate the flat (serialized)
version of the email message represented by a message object structure.
You will need to do this if you want to send your message via *note
smtplib.SMTP.sendmail(): dfb, or print the message on the console.
Taking a message object structure and producing a serialized
representation is the job of the generator classes.

As with the *note email.parser: 45. module, you aren't limited to the
functionality of the bundled generator; you could write one from scratch
yourself.  However the bundled generator knows how to generate most
email in a standards-compliant way, should handle MIME and non-MIME
email messages just fine, and is designed so that the bytes-oriented
parsing and generation operations are inverses, assuming the same
non-transforming *note policy: 46. is used for both.  That is, parsing
the serialized byte stream via the *note BytesParser: 1164. class and
then regenerating the serialized byte stream using *note BytesGenerator:
1167. should produce output identical to the input (2).  (On the other
hand, using the generator on an *note EmailMessage: 260. constructed by
program may result in changes to the *note EmailMessage: 260. object as
defaults are filled in.)

The *note Generator: 1166. class can be used to flatten a message into a
text (as opposed to binary) serialized representation, but since Unicode
cannot represent binary data directly, the message is of necessity
transformed into something that contains only ASCII characters, using
the standard email RFC Content Transfer Encoding techniques for encoding
email messages for transport over channels that are not "8 bit clean".

To accommodate reproducible processing of SMIME-signed messages *note
Generator: 1166. disables header folding for message parts of type
‘multipart/signed’ and all subparts.

 -- 類別: email.generator.BytesGenerator (outfp, mangle_from_=None,
          maxheaderlen=None, *, policy=None)

     Return a *note BytesGenerator: 1167. object that will write any
     message provided to the *note flatten(): 33d9. method, or any
     surrogateescape encoded text provided to the *note write(): 33da.
     method, to the *note file-like object: 246a. 'outfp'.  'outfp' must
     support a ‘write’ method that accepts binary data.

     If optional 'mangle_from_' is ‘True’, put a ‘>’ character in front
     of any line in the body that starts with the exact string ‘"From
     "’, that is ‘From’ followed by a space at the beginning of a line.
     'mangle_from_' defaults to the value of the *note mangle_from_:
     d9c. setting of the 'policy' (which is ‘True’ for the *note
     compat32: c40. policy and ‘False’ for all others).  'mangle_from_'
     is intended for use when messages are stored in Unix mbox format
     (see *note mailbox: 7f. and WHY THE CONTENT-LENGTH FORMAT IS
     BAD(3)).

     If 'maxheaderlen' is not ‘None’, refold any header lines that are
     longer than 'maxheaderlen', or if ‘0’, do not rewrap any headers.
     If 'manheaderlen' is ‘None’ (the default), wrap headers and other
     message lines according to the 'policy' settings.

     If 'policy' is specified, use that policy to control message
     generation.  If 'policy' is ‘None’ (the default), use the policy
     associated with the *note Message: 261. or *note EmailMessage: 260.
     object passed to ‘flatten’ to control the message generation.  See
     *note email.policy: 46. for details on what 'policy' controls.

     在 3.2 版被加入.

     在 3.3 版的變更: 新增關鍵字 'policy'。

     在 3.6 版的變更: The default behavior of the 'mangle_from_' and
     'maxheaderlen' parameters is to follow the policy.

      -- 方法: flatten (msg, unixfrom=False, linesep=None)

          Print the textual representation of the message object
          structure rooted at 'msg' to the output file specified when
          the *note BytesGenerator: 1167. instance was created.

          If the *note policy: 46. option *note cte_type: 33db. is
          ‘8bit’ (the default), copy any headers in the original parsed
          message that have not been modified to the output with any
          bytes with the high bit set reproduced as in the original, and
          preserve the non-ASCII ‘Content-Transfer-Encoding’ of any body
          parts that have them.  If ‘cte_type’ is ‘7bit’, convert the
          bytes with the high bit set as needed using an
          ASCII-compatible ‘Content-Transfer-Encoding’.  That is,
          transform parts with non-ASCII ‘Content-Transfer-Encoding’
          (‘Content-Transfer-Encoding: 8bit’) to an ASCII compatible
          ‘Content-Transfer-Encoding’, and encode RFC-invalid non-ASCII
          bytes in headers using the MIME ‘unknown-8bit’ character set,
          thus rendering them RFC-compliant.

          If 'unixfrom' is ‘True’, print the envelope header delimiter
          used by the Unix mailbox format (see *note mailbox: 7f.)
          before the first of the RFC 5322(4) headers of the root
          message object.  If the root object has no envelope header,
          craft a standard one.  The default is ‘False’.  Note that for
          subparts, no envelope header is ever printed.

          If 'linesep' is not ‘None’, use it as the separator character
          between all the lines of the flattened message.  If 'linesep'
          is ‘None’ (the default), use the value specified in the
          'policy'.

      -- 方法: clone (fp)

          Return an independent clone of this *note BytesGenerator:
          1167. instance with the exact same option settings, and 'fp'
          as the new 'outfp'.

      -- 方法: write (s)

          Encode 's' using the ‘ASCII’ codec and the ‘surrogateescape’
          error handler, and pass it to the 'write' method of the
          'outfp' passed to the *note BytesGenerator: 1167.'s
          constructor.

As a convenience, *note EmailMessage: 260. provides the methods *note
as_bytes(): 3390. and ‘bytes(aMessage)’ (a.k.a.  *note __bytes__():
3391.), which simplify the generation of a serialized binary
representation of a message object.  For more detail, see *note
email.message: 3b.

Because strings cannot represent binary data, the *note Generator: 1166.
class must convert any binary data in any message it flattens to an
ASCII compatible format, by converting them to an ASCII compatible
‘Content-Transfer_Encoding’.  Using the terminology of the email RFCs,
you can think of this as *note Generator: 1166. serializing to an I/O
stream that is not "8 bit clean".  In other words, most applications
will want to be using *note BytesGenerator: 1167, and not *note
Generator: 1166.

 -- 類別: email.generator.Generator (outfp, mangle_from_=None,
          maxheaderlen=None, *, policy=None)

     Return a *note Generator: 1166. object that will write any message
     provided to the *note flatten(): 33dd. method, or any text provided
     to the *note write(): 33de. method, to the *note file-like object:
     246a. 'outfp'.  'outfp' must support a ‘write’ method that accepts
     string data.

     If optional 'mangle_from_' is ‘True’, put a ‘>’ character in front
     of any line in the body that starts with the exact string ‘"From
     "’, that is ‘From’ followed by a space at the beginning of a line.
     'mangle_from_' defaults to the value of the *note mangle_from_:
     d9c. setting of the 'policy' (which is ‘True’ for the *note
     compat32: c40. policy and ‘False’ for all others).  'mangle_from_'
     is intended for use when messages are stored in Unix mbox format
     (see *note mailbox: 7f. and WHY THE CONTENT-LENGTH FORMAT IS
     BAD(5)).

     If 'maxheaderlen' is not ‘None’, refold any header lines that are
     longer than 'maxheaderlen', or if ‘0’, do not rewrap any headers.
     If 'manheaderlen' is ‘None’ (the default), wrap headers and other
     message lines according to the 'policy' settings.

     If 'policy' is specified, use that policy to control message
     generation.  If 'policy' is ‘None’ (the default), use the policy
     associated with the *note Message: 261. or *note EmailMessage: 260.
     object passed to ‘flatten’ to control the message generation.  See
     *note email.policy: 46. for details on what 'policy' controls.

     在 3.3 版的變更: 新增關鍵字 'policy'。

     在 3.6 版的變更: The default behavior of the 'mangle_from_' and
     'maxheaderlen' parameters is to follow the policy.

      -- 方法: flatten (msg, unixfrom=False, linesep=None)

          Print the textual representation of the message object
          structure rooted at 'msg' to the output file specified when
          the *note Generator: 1166. instance was created.

          If the *note policy: 46. option *note cte_type: 33db. is
          ‘8bit’, generate the message as if the option were set to
          ‘7bit’.  (This is required because strings cannot represent
          non-ASCII bytes.)  Convert any bytes with the high bit set as
          needed using an ASCII-compatible ‘Content-Transfer-Encoding’.
          That is, transform parts with non-ASCII
          ‘Content-Transfer-Encoding’ (‘Content-Transfer-Encoding:
          8bit’) to an ASCII compatible ‘Content-Transfer-Encoding’, and
          encode RFC-invalid non-ASCII bytes in headers using the MIME
          ‘unknown-8bit’ character set, thus rendering them
          RFC-compliant.

          If 'unixfrom' is ‘True’, print the envelope header delimiter
          used by the Unix mailbox format (see *note mailbox: 7f.)
          before the first of the RFC 5322(6) headers of the root
          message object.  If the root object has no envelope header,
          craft a standard one.  The default is ‘False’.  Note that for
          subparts, no envelope header is ever printed.

          If 'linesep' is not ‘None’, use it as the separator character
          between all the lines of the flattened message.  If 'linesep'
          is ‘None’ (the default), use the value specified in the
          'policy'.

          在 3.2 版的變更: Added support for re-encoding ‘8bit’ message
          bodies, and the 'linesep' argument.

      -- 方法: clone (fp)

          Return an independent clone of this *note Generator: 1166.
          instance with the exact same options, and 'fp' as the new
          'outfp'.

      -- 方法: write (s)

          Write 's' to the 'write' method of the 'outfp' passed to the
          *note Generator: 1166.'s constructor.  This provides just
          enough file-like API for *note Generator: 1166. instances to
          be used in the *note print(): f18. function.

As a convenience, *note EmailMessage: 260. provides the methods *note
as_string(): 338d. and ‘str(aMessage)’ (a.k.a.  *note __str__(): 338f.),
which simplify the generation of a formatted string representation of a
message object.  For more detail, see *note email.message: 3b.

The *note email.generator: 37. module also provides a derived class,
*note DecodedGenerator: c3e, which is like the *note Generator: 1166.
base class, except that non-‘text’ parts are not serialized, but are
instead represented in the output stream by a string derived from a
template filled in with information about the part.

 -- 類別: email.generator.DecodedGenerator (outfp, mangle_from_=None,
          maxheaderlen=None, fmt=None, *, policy=None)

     Act like *note Generator: 1166, except that for any subpart of the
     message passed to *note Generator.flatten(): 33dd, if the subpart
     is of main type ‘text’, print the decoded payload of the subpart,
     and if the main type is not ‘text’, instead of printing it fill in
     the string 'fmt' using information from the part and print the
     resulting filled-in string.

     To fill in 'fmt', execute ‘fmt % part_info’, where ‘part_info’ is a
     dictionary composed of the following keys and values:

        * ‘type’ - Full MIME type of the non-‘text’ part

        * ‘maintype’ - Main MIME type of the non-‘text’ part

        * ‘subtype’ - Sub-MIME type of the non-‘text’ part

        * ‘filename’ - Filename of the non-‘text’ part

        * ‘description’ - Description associated with the non-‘text’
          part

        * ‘encoding’ - Content transfer encoding of the non-‘text’ part

     If 'fmt' is ‘None’, use the following default 'fmt':

          "[Non-text (%(type)s) part of message omitted, filename
          %(filename)s]"

     Optional '_mangle_from_' and 'maxheaderlen' are as with the *note
     Generator: 1166. base class.

註解
....

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/email/generator.py

   (2) This statement assumes that you use the appropriate setting for
‘unixfrom’, and that there are no *note email.policy: 46. settings
calling for automatic adjustments (for example, *note refold_source:
33d8. must be ‘none’, which is 'not' the default).  It is also not 100%
true, since if the message does not conform to the RFC standards
occasionally information about the exact original text is lost during
parsing error recovery.  It is a goal to fix these latter edge cases
when possible.

   (3) https://www.jwz.org/doc/content-length.html

   (4) https://datatracker.ietf.org/doc/html/rfc5322.html

   (5) https://www.jwz.org/doc/content-length.html

   (6) https://datatracker.ietf.org/doc/html/rfc5322.html


File: python.info,  Node: email policy Policy Objects,  Next: email errors：例外和缺陷類別,  Prev: email generator：產生 MIME 文件,  Up: email --- 郵件和 MIME 處理套件

5.19.1.7 ‘email.policy’: Policy Objects
.......................................

在 3.3 版被加入.

'原始碼：'Lib/email/policy.py(1)

__________________________________________________________________

The *note email: 32. package's prime focus is the handling of email
messages as described by the various email and MIME RFCs.  However, the
general format of email messages (a block of header fields each
consisting of a name followed by a colon followed by a value, the whole
block followed by a blank line and an arbitrary 'body'), is a format
that has found utility outside of the realm of email.  Some of these
uses conform fairly closely to the main email RFCs, some do not.  Even
when working with email, there are times when it is desirable to break
strict compliance with the RFCs, such as generating emails that
interoperate with email servers that do not themselves follow the
standards, or that implement extensions you want to use in ways that
violate the standards.

Policy objects give the email package the flexibility to handle all
these disparate use cases.

A *note Policy: 104d. object encapsulates a set of attributes and
methods that control the behavior of various components of the email
package during use.  *note Policy: 104d. instances can be passed to
various classes and methods in the email package to alter the default
behavior.  The settable values and their defaults are described below.

There is a default policy used by all classes in the email package.  For
all of the *note parser: 45. classes and the related convenience
functions, and for the *note Message: 261. class, this is the *note
Compat32: 104e. policy, via its corresponding pre-defined instance *note
compat32: c40.  This policy provides for complete backward compatibility
(in some cases, including bug compatibility) with the pre-Python3.3
version of the email package.

This default value for the 'policy' keyword to *note EmailMessage: 260.
is the *note EmailPolicy: 1051. policy, via its pre-defined instance
*note default: 338c.

When a *note Message: 261. or *note EmailMessage: 260. object is
created, it acquires a policy.  If the message is created by a *note
parser: 45, a policy passed to the parser will be the policy used by the
message it creates.  If the message is created by the program, then the
policy can be specified when it is created.  When a message is passed to
a *note generator: 37, the generator uses the policy from the message by
default, but you can also pass a specific policy to the generator that
will override the one stored on the message object.

The default value for the 'policy' keyword for the *note email.parser:
45. classes and the parser convenience functions 'will be changing' in a
future version of Python.  Therefore you should 'always specify
explicitly which policy you want to use' when calling any of the classes
and functions described in the *note parser: 45. module.

The first part of this documentation covers the features of *note
Policy: 104d, an *note abstract base class: 114e. that defines the
features that are common to all policy objects, including *note
compat32: c40.  This includes certain hook methods that are called
internally by the email package, which a custom policy could override to
obtain different behavior.  The second part describes the concrete
classes *note EmailPolicy: 1051. and *note Compat32: 104e, which
implement the hooks that provide the standard behavior and the backward
compatible behavior and features, respectively.

*note Policy: 104d. instances are immutable, but they can be cloned,
accepting the same keyword arguments as the class constructor and
returning a new *note Policy: 104d. instance that is a copy of the
original but with the specified attributes values changed.

As an example, the following code could be used to read an email message
from a file on disk and pass it to the system ‘sendmail’ program on a
Unix system:

     >>> from email import message_from_binary_file
     >>> from email.generator import BytesGenerator
     >>> from email import policy
     >>> from subprocess import Popen, PIPE
     >>> with open('mymsg.txt', 'rb') as f:
     ...     msg = message_from_binary_file(f, policy=policy.default)
     ...
     >>> p = Popen(['sendmail', msg['To'].addresses[0]], stdin=PIPE)
     >>> g = BytesGenerator(p.stdin, policy=msg.policy.clone(linesep='\r\n'))
     >>> g.flatten(msg)
     >>> p.stdin.close()
     >>> rc = p.wait()

Here we are telling *note BytesGenerator: 1167. to use the RFC correct
line separator characters when creating the binary string to feed into
‘sendmail's’ ‘stdin’, where the default policy would use ‘\n’ line
separators.

Some email package methods accept a 'policy' keyword argument, allowing
the policy to be overridden for that method.  For example, the following
code uses the *note as_bytes(): edb. method of the 'msg' object from the
previous example and writes the message to a file using the native line
separators for the platform on which it is running:

     >>> import os
     >>> with open('converted.txt', 'wb') as f:
     ...     f.write(msg.as_bytes(policy=msg.policy.clone(linesep=os.linesep)))
     17

Policy objects can also be combined using the addition operator,
producing a policy object whose settings are a combination of the
non-default values of the summed objects:

     >>> compat_SMTP = policy.compat32.clone(linesep='\r\n')
     >>> compat_strict = policy.compat32.clone(raise_on_defect=True)
     >>> compat_strict_SMTP = compat_SMTP + compat_strict

This operation is not commutative; that is, the order in which the
objects are added matters.  To illustrate:

     >>> policy100 = policy.compat32.clone(max_line_length=100)
     >>> policy80 = policy.compat32.clone(max_line_length=80)
     >>> apolicy = policy100 + policy80
     >>> apolicy.max_line_length
     80
     >>> apolicy = policy80 + policy100
     >>> apolicy.max_line_length
     100

 -- 類別: email.policy.Policy (**kw)

     This is the *note abstract base class: 114e. for all policy
     classes.  It provides default implementations for a couple of
     trivial methods, as well as the implementation of the immutability
     property, the *note clone(): 104f. method, and the constructor
     semantics.

     The constructor of a policy class can be passed various keyword
     arguments.  The arguments that may be specified are any non-method
     properties on this class, plus any additional non-method properties
     on the concrete class.  A value specified in the constructor will
     override the default value for the corresponding attribute.

     This class defines the following properties, and thus values for
     the following may be passed in the constructor of any policy class:

      -- 屬性: max_line_length

          The maximum length of any line in the serialized output, not
          counting the end of line character(s).  Default is 78, per RFC
          5322(2).  A value of ‘0’ or *note None: 61b. indicates that no
          line wrapping should be done at all.

      -- 屬性: linesep

          The string to be used to terminate lines in serialized output.
          The default is ‘\n’ because that's the internal end-of-line
          discipline used by Python, though ‘\r\n’ is required by the
          RFCs.

      -- 屬性: cte_type

          Controls the type of Content Transfer Encodings that may be or
          are required to be used.  The possible values are:

          ‘7bit’       all data must be "7 bit clean" (ASCII-only).  This means that
                       where necessary data will be encoded using either
                       quoted-printable or base64 encoding.
                       
                       
          ‘8bit’       data is not constrained to be 7 bit clean.  Data in headers is
                       still required to be ASCII-only and so will be encoded (see
                       *note fold_binary(): 33e3. and *note utf8: d9e. below for
                       exceptions), but body parts may use the ‘8bit’ CTE.
                       

          A ‘cte_type’ value of ‘8bit’ only works with ‘BytesGenerator’,
          not ‘Generator’, because strings cannot contain binary data.
          If a ‘Generator’ is operating under a policy that specifies
          ‘cte_type=8bit’, it will act as if ‘cte_type’ is ‘7bit’.

      -- 屬性: raise_on_defect

          If *note True: bb4, any defects encountered will be raised as
          errors.  If *note False: adb. (the default), defects will be
          passed to the *note register_defect(): 33e5. method.

      -- 屬性: mangle_from_

          If *note True: bb4, lines starting with '"From "' in the body
          are escaped by putting a ‘>’ in front of them.  This parameter
          is used when the message is being serialized by a generator.
          Default: *note False: adb.

          在 3.5 版被加入.

      -- 屬性: message_factory

          A factory function for constructing a new empty message
          object.  Used by the parser when building messages.  Defaults
          to ‘None’, in which case *note Message: 261. is used.

          在 3.6 版被加入.

      -- 屬性: verify_generated_headers

          If ‘True’ (the default), the generator will raise *note
          HeaderWriteError: 33e6. instead of writing a header that is
          improperly folded or delimited, such that it would be parsed
          as multiple headers or joined with adjacent data.  Such
          headers can be generated by custom header classes or bugs in
          the ‘email’ module.

          As it's a security feature, this defaults to ‘True’ even in
          the *note Compat32: 104e. policy.  For backwards compatible,
          but unsafe, behavior, it must be set to ‘False’ explicitly.

          在 3.13 版被加入.

     The following *note Policy: 104d. method is intended to be called
     by code using the email library to create policy instances with
     custom settings:

      -- 方法: clone (**kw)

          Return a new *note Policy: 104d. instance whose attributes
          have the same values as the current instance, except where
          those attributes are given new values by the keyword
          arguments.

     The remaining *note Policy: 104d. methods are called by the email
     package code, and are not intended to be called by an application
     using the email package.  A custom policy must implement all of
     these methods.

      -- 方法: handle_defect (obj, defect)

          Handle a 'defect' found on 'obj'.  When the email package
          calls this method, 'defect' will always be a subclass of
          ‘Defect’.

          The default implementation checks the *note raise_on_defect:
          33e4. flag.  If it is ‘True’, 'defect' is raised as an
          exception.  If it is ‘False’ (the default), 'obj' and 'defect'
          are passed to *note register_defect(): 33e5.

      -- 方法: register_defect (obj, defect)

          Register a 'defect' on 'obj'.  In the email package, 'defect'
          will always be a subclass of ‘Defect’.

          The default implementation calls the ‘append’ method of the
          ‘defects’ attribute of 'obj'.  When the email package calls
          *note handle_defect: 33e7, 'obj' will normally have a
          ‘defects’ attribute that has an ‘append’ method.  Custom
          object types used with the email package (for example, custom
          ‘Message’ objects) should also provide such an attribute,
          otherwise defects in parsed messages will raise unexpected
          errors.

      -- 方法: header_max_count (name)

          Return the maximum allowed number of headers named 'name'.

          Called when a header is added to an *note EmailMessage: 260.
          or *note Message: 261. object.  If the returned value is not
          ‘0’ or ‘None’, and there are already a number of headers with
          the name 'name' greater than or equal to the value returned, a
          *note ValueError: 1e7. is raised.

          Because the default behavior of ‘Message.__setitem__’ is to
          append the value to the list of headers, it is easy to create
          duplicate headers without realizing it.  This method allows
          certain headers to be limited in the number of instances of
          that header that may be added to a ‘Message’ programmatically.
          (The limit is not observed by the parser, which will
          faithfully produce as many headers as exist in the message
          being parsed.)

          The default implementation returns ‘None’ for all header
          names.

      -- 方法: header_source_parse (sourcelines)

          The email package calls this method with a list of strings,
          each string ending with the line separation characters found
          in the source being parsed.  The first line includes the field
          header name and separator.  All whitespace in the source is
          preserved.  The method should return the ‘(name, value)’ tuple
          that is to be stored in the ‘Message’ to represent the parsed
          header.

          If an implementation wishes to retain compatibility with the
          existing email package policies, 'name' should be the case
          preserved name (all characters up to the '‘:’' separator),
          while 'value' should be the unfolded value (all line separator
          characters removed, but whitespace kept intact), stripped of
          leading whitespace.

          'sourcelines' may contain surrogateescaped binary data.

          There is no default implementation

      -- 方法: header_store_parse (name, value)

          The email package calls this method with the name and value
          provided by the application program when the application
          program is modifying a ‘Message’ programmatically (as opposed
          to a ‘Message’ created by a parser).  The method should return
          the ‘(name, value)’ tuple that is to be stored in the
          ‘Message’ to represent the header.

          If an implementation wishes to retain compatibility with the
          existing email package policies, the 'name' and 'value' should
          be strings or string subclasses that do not change the content
          of the passed in arguments.

          There is no default implementation

      -- 方法: header_fetch_parse (name, value)

          The email package calls this method with the 'name' and
          'value' currently stored in the ‘Message’ when that header is
          requested by the application program, and whatever the method
          returns is what is passed back to the application as the value
          of the header being retrieved.  Note that there may be more
          than one header with the same name stored in the ‘Message’;
          the method is passed the specific name and value of the header
          destined to be returned to the application.

          'value' may contain surrogateescaped binary data.  There
          should be no surrogateescaped binary data in the value
          returned by the method.

          There is no default implementation

      -- 方法: fold (name, value)

          The email package calls this method with the 'name' and
          'value' currently stored in the ‘Message’ for a given header.
          The method should return a string that represents that header
          "folded" correctly (according to the policy settings) by
          composing the 'name' with the 'value' and inserting *note
          linesep: 33e2. characters at the appropriate places.  See RFC
          5322(3) for a discussion of the rules for folding email
          headers.

          'value' may contain surrogateescaped binary data.  There
          should be no surrogateescaped binary data in the string
          returned by the method.

      -- 方法: fold_binary (name, value)

          The same as *note fold(): 33ec, except that the returned value
          should be a bytes object rather than a string.

          'value' may contain surrogateescaped binary data.  These could
          be converted back into binary data in the returned bytes
          object.

 -- 類別: email.policy.EmailPolicy (**kw)

     This concrete *note Policy: 104d. provides behavior that is
     intended to be fully compliant with the current email RFCs.  These
     include (but are not limited to) RFC 5322(4), RFC 2047(5), and the
     current MIME RFCs.

     This policy adds new header parsing and folding algorithms.
     Instead of simple strings, headers are ‘str’ subclasses with
     attributes that depend on the type of the field.  The parsing and
     folding algorithm fully implement RFC 2047(6) and RFC 5322(7).

     The default value for the *note message_factory: c3f. attribute is
     *note EmailMessage: 260.

     In addition to the settable attributes listed above that apply to
     all policies, this policy adds the following additional attributes:

     在 3.6 版被加入: (8)

      -- 屬性: utf8

          If ‘False’, follow RFC 5322(9), supporting non-ASCII
          characters in headers by encoding them as "encoded words".  If
          ‘True’, follow RFC 6532(10) and use ‘utf-8’ encoding for
          headers.  Messages formatted in this way may be passed to SMTP
          servers that support the ‘SMTPUTF8’ extension ( RFC 6531(11)).

      -- 屬性: refold_source

          If the value for a header in the ‘Message’ object originated
          from a *note parser: 45. (as opposed to being set by a
          program), this attribute indicates whether or not a generator
          should refold that value when transforming the message back
          into serialized form.  The possible values are:

          ‘none’       all source values use original folding
                       
                       
          ‘long’       source values that have any line that is longer than
                       ‘max_line_length’ will be refolded
                       
                       
          ‘all’        all values are refolded.
                       

          預設為 ‘long’。

      -- 屬性: header_factory

          A callable that takes two arguments, ‘name’ and ‘value’, where
          ‘name’ is a header field name and ‘value’ is an unfolded
          header field value, and returns a string subclass that
          represents that header.  A default ‘header_factory’ (see *note
          headerregistry: 39.) is provided that supports custom parsing
          for the various address and date RFC 5322(12) header field
          types, and the major MIME header field stypes.  Support for
          additional custom parsing will be added in the future.

      -- 屬性: content_manager

          An object with at least two methods: get_content and
          set_content.  When the *note get_content(): 33b9. or *note
          set_content(): 17ab. method of an *note EmailMessage: 260.
          object is called, it calls the corresponding method of this
          object, passing it the message object as its first argument,
          and any arguments or keywords that were passed to it as
          additional arguments.  By default ‘content_manager’ is set to
          *note raw_data_manager: 33ee.

          在 3.4 版被加入.

     The class provides the following concrete implementations of the
     abstract methods of *note Policy: 104d.:

      -- 方法: header_max_count (name)

          Returns the value of the *note max_count: 33f0. attribute of
          the specialized class used to represent the header with the
          given name.

      -- 方法: header_source_parse (sourcelines)

          The name is parsed as everything up to the '‘:’' and returned
          unmodified.  The value is determined by stripping leading
          whitespace off the remainder of the first line, joining all
          subsequent lines together, and stripping any trailing carriage
          return or linefeed characters.

      -- 方法: header_store_parse (name, value)

          The name is returned unchanged.  If the input value has a
          ‘name’ attribute and it matches 'name' ignoring case, the
          value is returned unchanged.  Otherwise the 'name' and 'value'
          are passed to ‘header_factory’, and the resulting header
          object is returned as the value.  In this case a ‘ValueError’
          is raised if the input value contains CR or LF characters.

      -- 方法: header_fetch_parse (name, value)

          If the value has a ‘name’ attribute, it is returned to
          unmodified.  Otherwise the 'name', and the 'value' with any CR
          or LF characters removed, are passed to the ‘header_factory’,
          and the resulting header object is returned.  Any
          surrogateescaped bytes get turned into the unicode
          unknown-character glyph.

      -- 方法: fold (name, value)

          Header folding is controlled by the *note refold_source: 33d8.
          policy setting.  A value is considered to be a 'source value'
          if and only if it does not have a ‘name’ attribute (having a
          ‘name’ attribute means it is a header object of some sort).
          If a source value needs to be refolded according to the
          policy, it is converted into a header object by passing the
          'name' and the 'value' with any CR and LF characters removed
          to the ‘header_factory’.  Folding of a header object is done
          by calling its ‘fold’ method with the current policy.

          Source values are split into lines using *note splitlines():
          11ef.  If the value is not to be refolded, the lines are
          rejoined using the ‘linesep’ from the policy and returned.
          The exception is lines containing non-ascii binary data.  In
          that case the value is refolded regardless of the
          ‘refold_source’ setting, which causes the binary data to be
          CTE encoded using the ‘unknown-8bit’ charset.

      -- 方法: fold_binary (name, value)

          The same as *note fold(): 156b. if *note cte_type: 33db. is
          ‘7bit’, except that the returned value is bytes.

          If *note cte_type: 33db. is ‘8bit’, non-ASCII binary data is
          converted back into bytes.  Headers with binary data are not
          refolded, regardless of the ‘refold_header’ setting, since
          there is no way to know whether the binary data consists of
          single byte characters or multibyte characters.

The following instances of *note EmailPolicy: 1051. provide defaults
suitable for specific application domains.  Note that in the future the
behavior of these instances (in particular the ‘HTTP’ instance) may be
adjusted to conform even more closely to the RFCs relevant to their
domains.

 -- 資料: email.policy.default

     An instance of ‘EmailPolicy’ with all defaults unchanged.  This
     policy uses the standard Python ‘\n’ line endings rather than the
     RFC-correct ‘\r\n’.

 -- 資料: email.policy.SMTP

     Suitable for serializing messages in conformance with the email
     RFCs.  Like ‘default’, but with ‘linesep’ set to ‘\r\n’, which is
     RFC compliant.

 -- 資料: email.policy.SMTPUTF8

     The same as ‘SMTP’ except that *note utf8: d9e. is ‘True’.  Useful
     for serializing messages to a message store without using encoded
     words in the headers.  Should only be used for SMTP transmission if
     the sender or recipient addresses have non-ASCII characters (the
     *note smtplib.SMTP.send_message(): dfc. method handles this
     automatically).

 -- 資料: email.policy.HTTP

     Suitable for serializing headers with for use in HTTP traffic.
     Like ‘SMTP’ except that ‘max_line_length’ is set to ‘None’
     (unlimited).

 -- 資料: email.policy.strict

     Convenience instance.  The same as ‘default’ except that
     ‘raise_on_defect’ is set to ‘True’.  This allows any policy to be
     made strict by writing:

          somepolicy + policy.strict

With all of these *note EmailPolicies: 1051, the effective API of the
email package is changed from the Python 3.2 API in the following ways:

   * Setting a header on a *note Message: 261. results in that header
     being parsed and a header object created.

   * Fetching a header value from a *note Message: 261. results in that
     header being parsed and a header object created and returned.

   * Any header object, or any header that is refolded due to the policy
     settings, is folded using an algorithm that fully implements the
     RFC folding algorithms, including knowing where encoded words are
     required and allowed.

From the application view, this means that any header obtained through
the *note EmailMessage: 260. is a header object with extra attributes,
whose string value is the fully decoded unicode value of the header.
Likewise, a header may be assigned a new value, or a new header created,
using a unicode string, and the policy will take care of converting the
unicode string into the correct RFC encoded form.

The header objects and their attributes are described in *note
headerregistry: 39.

 -- 類別: email.policy.Compat32 (**kw)

     This concrete *note Policy: 104d. is the backward compatibility
     policy.  It replicates the behavior of the email package in Python
     3.2.  The *note policy: 46. module also defines an instance of this
     class, *note compat32: c40, that is used as the default policy.
     Thus the default behavior of the email package is to maintain
     compatibility with Python 3.2.

     The following attributes have values that are different from the
     *note Policy: 104d. default:

      -- 屬性: mangle_from_

          The default is ‘True’.

     The class provides the following concrete implementations of the
     abstract methods of *note Policy: 104d.:

      -- 方法: header_source_parse (sourcelines)

          The name is parsed as everything up to the '‘:’' and returned
          unmodified.  The value is determined by stripping leading
          whitespace off the remainder of the first line, joining all
          subsequent lines together, and stripping any trailing carriage
          return or linefeed characters.

      -- 方法: header_store_parse (name, value)

          The name and value are returned unmodified.

      -- 方法: header_fetch_parse (name, value)

          If the value contains binary data, it is converted into a
          *note Header: 17ac. object using the ‘unknown-8bit’ charset.
          Otherwise it is returned unmodified.

      -- 方法: fold (name, value)

          Headers are folded using the *note Header: 17ac. folding
          algorithm, which preserves existing line breaks in the value,
          and wraps each resulting line to the ‘max_line_length’.
          Non-ASCII binary data are CTE encoded using the ‘unknown-8bit’
          charset.

      -- 方法: fold_binary (name, value)

          Headers are folded using the *note Header: 17ac. folding
          algorithm, which preserves existing line breaks in the value,
          and wraps each resulting line to the ‘max_line_length’.  If
          ‘cte_type’ is ‘7bit’, non-ascii binary data is CTE encoded
          using the ‘unknown-8bit’ charset.  Otherwise the original
          source header is used, with its existing line breaks and any
          (RFC invalid) binary data it may contain.

 -- 資料: email.policy.compat32

     An instance of *note Compat32: 104e, providing backward
     compatibility with the behavior of the email package in Python 3.2.

註解
....

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/email/policy.py

   (2) https://datatracker.ietf.org/doc/html/rfc5322.html

   (3) https://datatracker.ietf.org/doc/html/rfc5322.html

   (4) https://datatracker.ietf.org/doc/html/rfc5322.html

   (5) https://datatracker.ietf.org/doc/html/rfc2047.html

   (6) https://datatracker.ietf.org/doc/html/rfc2047.html

   (7) https://datatracker.ietf.org/doc/html/rfc5322.html

   (8) Originally added in 3.3 as a *note provisional feature: fe4.

   (9) https://datatracker.ietf.org/doc/html/rfc5322.html

   (10) https://datatracker.ietf.org/doc/html/rfc6532.html

   (11) https://datatracker.ietf.org/doc/html/rfc6531.html

   (12) https://datatracker.ietf.org/doc/html/rfc5322.html


File: python.info,  Node: email errors：例外和缺陷類別,  Next: email headerregistry：自訂標頭物件,  Prev: email policy Policy Objects,  Up: email --- 郵件和 MIME 處理套件

5.19.1.8 ‘email.errors’：例外和缺陷類別
.......................................

'原始碼：'Lib/email/errors.py(1)

__________________________________________________________________

The following exception classes are defined in the *note email.errors:
36. module:

 -- 例外: email.errors.MessageError

     This is the base class for all exceptions that the *note email: 32.
     package can raise.  It is derived from the standard *note
     Exception: 97d. class and defines no additional methods.

 -- 例外: email.errors.MessageParseError

     This is the base class for exceptions raised by the *note Parser:
     1136. class.  It is derived from *note MessageError: 3401.  This
     class is also used internally by the parser used by *note
     headerregistry: 39.

 -- 例外: email.errors.HeaderParseError

     Raised under some error conditions when parsing the RFC 5322(2)
     headers of a message, this class is derived from *note
     MessageParseError: 3402.  The *note set_boundary(): 33ae. method
     will raise this error if the content type is unknown when the
     method is called.  *note Header: 17ac. may raise this error for
     certain base64 decoding errors, and when an attempt is made to
     create a header that appears to contain an embedded header (that
     is, there is what is supposed to be a continuation line that has no
     leading whitespace and looks like a header).

 -- 例外: email.errors.BoundaryError

     Deprecated and no longer used.

 -- 例外: email.errors.MultipartConversionError

     Raised when a payload is added to a *note Message: 261. object
     using ‘add_payload()’, but the payload is already a scalar and the
     message's ‘Content-Type’ main type is not either ‘multipart’ or
     missing.  *note MultipartConversionError: 3404. multiply inherits
     from *note MessageError: 3401. and the built-in *note TypeError:
     4dd.

     Since ‘Message.add_payload()’ is deprecated, this exception is
     rarely raised in practice.  However the exception may also be
     raised if the *note attach(): 33c0. method is called on an instance
     of a class derived from *note MIMENonMultipart: 3405. (e.g.  *note
     MIMEImage: 3406.).

 -- 例外: email.errors.HeaderWriteError

     Raised when an error occurs when the *note generator: 37. outputs
     headers.

 -- 例外: email.errors.MessageDefect

     This is the base class for all defects found when parsing email
     messages.  It is derived from *note ValueError: 1e7.

 -- 例外: email.errors.HeaderDefect

     This is the base class for all defects found when parsing email
     headers.  It is derived from *note MessageDefect: 3407.

Here is the list of the defects that the *note FeedParser: 33ca. can
find while parsing messages.  Note that the defects are added to the
message where the problem was found, so for example, if a message nested
inside a ‘multipart/alternative’ had a malformed header, that nested
message object would have a defect, but the containing messages would
not.

All defect classes are subclassed from *note email.errors.MessageDefect:
3407.

   * ‘NoBoundaryInMultipartDefect’ - A message claimed to be a
     multipart, but had no ‘boundary’ parameter.

   * ‘StartBoundaryNotFoundDefect’ - The start boundary claimed in the
     ‘Content-Type’ header was never found.

   * ‘CloseBoundaryNotFoundDefect’ - A start boundary was found, but no
     corresponding close boundary was ever found.

     在 3.3 版被加入.

   * ‘FirstHeaderLineIsContinuationDefect’ - The message had a
     continuation line as its first header line.

   * ‘MisplacedEnvelopeHeaderDefect’ - A "Unix From" header was found in
     the middle of a header block.

   * ‘MissingHeaderBodySeparatorDefect’ - A line was found while parsing
     headers that had no leading white space but contained no ':'.
     Parsing continues assuming that the line represents the first line
     of the body.

     在 3.3 版被加入.

   * ‘MalformedHeaderDefect’ - A header was found that was missing a
     colon, or was otherwise malformed.

     在 3.3 版之後被棄用: This defect has not been used for several
     Python versions.

   * ‘MultipartInvariantViolationDefect’ - A message claimed to be a
     ‘multipart’, but no subparts were found.  Note that when a message
     has this defect, its *note is_multipart(): 33b3. method may return
     ‘False’ even though its content type claims to be ‘multipart’.

   * ‘InvalidBase64PaddingDefect’ - When decoding a block of base64
     encoded bytes, the padding was not correct.  Enough padding is
     added to perform the decode, but the resulting decoded bytes may be
     invalid.

   * ‘InvalidBase64CharactersDefect’ - When decoding a block of base64
     encoded bytes, characters outside the base64 alphabet were
     encountered.  The characters are ignored, but the resulting decoded
     bytes may be invalid.

   * ‘InvalidBase64LengthDefect’ - When decoding a block of base64
     encoded bytes, the number of non-padding base64 characters was
     invalid (1 more than a multiple of 4).  The encoded block was kept
     as-is.

   * ‘InvalidDateDefect’ - When decoding an invalid or unparsable date
     field.  The original value is kept as-is.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/email/errors.py

   (2) https://datatracker.ietf.org/doc/html/rfc5322.html


File: python.info,  Node: email headerregistry：自訂標頭物件,  Next: email contentmanager：管理 MIME 內容,  Prev: email errors：例外和缺陷類別,  Up: email --- 郵件和 MIME 處理套件

5.19.1.9 ‘email.headerregistry’：自訂標頭物件
.............................................

'原始碼：'Lib/email/headerregistry.py(1)

__________________________________________________________________

在 3.6 版被加入: (2)

Headers are represented by customized subclasses of *note str: 3f2.  The
particular class used to represent a given header is determined by the
*note header_factory: 33ed. of the *note policy: 46. in effect when the
headers are created.  This section documents the particular
‘header_factory’ implemented by the email package for handling RFC
5322(3) compliant email messages, which not only provides customized
header objects for various header types, but also provides an extension
mechanism for applications to add their own custom header types.

When using any of the policy objects derived from *note EmailPolicy:
1051, all headers are produced by *note HeaderRegistry: 340b. and have
*note BaseHeader: 339b. as their last base class.  Each header class has
an additional base class that is determined by the type of the header.
For example, many headers have the class *note UnstructuredHeader: 340c.
as their other base class.  The specialized second class for a header is
determined by the name of the header, using a lookup table stored in the
*note HeaderRegistry: 340b.  All of this is managed transparently for
the typical application program, but interfaces are provided for
modifying the default behavior for use by more complex applications.

The sections below first document the header base classes and their
attributes, followed by the API for modifying the behavior of *note
HeaderRegistry: 340b, and finally the support classes used to represent
the data parsed from structured headers.

 -- 類別: email.headerregistry.BaseHeader (name, value)

     'name' and 'value' are passed to ‘BaseHeader’ from the *note
     header_factory: 33ed. call.  The string value of any header object
     is the 'value' fully decoded to unicode.

     This base class defines the following read-only properties:

      -- 屬性: name

          The name of the header (the portion of the field before the
          ':').  This is exactly the value passed in the *note
          header_factory: 33ed. call for 'name'; that is, case is
          preserved.

      -- 屬性: defects

          A tuple of *note HeaderDefect: 3408. instances reporting any
          RFC compliance problems found during parsing.  The email
          package tries to be complete about detecting compliance
          issues.  See the *note errors: 36. module for a discussion of
          the types of defects that may be reported.

      -- 屬性: max_count

          The maximum number of headers of this type that can have the
          same ‘name’.  A value of ‘None’ means unlimited.  The
          ‘BaseHeader’ value for this attribute is ‘None’; it is
          expected that specialized header classes will override this
          value as needed.

     ‘BaseHeader’ also provides the following method, which is called by
     the email library code and should not in general be called by
     application programs:

      -- 方法: fold (*, policy)

          Return a string containing *note linesep: 33e2. characters as
          required to correctly fold the header according to 'policy'.
          A *note cte_type: 33db. of ‘8bit’ will be treated as if it
          were ‘7bit’, since headers may not contain arbitrary binary
          data.  If *note utf8: d9e. is ‘False’, non-ASCII data will be
          RFC 2047(4) encoded.

     ‘BaseHeader’ by itself cannot be used to create a header object.
     It defines a protocol that each specialized header cooperates with
     in order to produce the header object.  Specifically, ‘BaseHeader’
     requires that the specialized class provide a *note classmethod():
     14a. named ‘parse’.  This method is called as follows:

          parse(string, kwds)

     ‘kwds’ is a dictionary containing one pre-initialized key,
     ‘defects’.  ‘defects’ is an empty list.  The parse method should
     append any detected defects to this list.  On return, the ‘kwds’
     dictionary 'must' contain values for at least the keys ‘decoded’
     and ‘defects’.  ‘decoded’ should be the string value for the header
     (that is, the header value fully decoded to unicode).  The parse
     method should assume that 'string' may contain
     content-transfer-encoded parts, but should correctly handle all
     valid unicode characters as well so that it can parse un-encoded
     header values.

     ‘BaseHeader’'s ‘__new__’ then creates the header instance, and
     calls its ‘init’ method.  The specialized class only needs to
     provide an ‘init’ method if it wishes to set additional attributes
     beyond those provided by ‘BaseHeader’ itself.  Such an ‘init’
     method should look like this:

          def init(self, /, *args, **kw):
              self._myattr = kw.pop('myattr')
              super().init(*args, **kw)

     That is, anything extra that the specialized class puts in to the
     ‘kwds’ dictionary should be removed and handled, and the remaining
     contents of ‘kw’ (and ‘args’) passed to the ‘BaseHeader’ ‘init’
     method.

 -- 類別: email.headerregistry.UnstructuredHeader

     An "unstructured" header is the default type of header in RFC
     5322(5).  Any header that does not have a specified syntax is
     treated as unstructured.  The classic example of an unstructured
     header is the ‘Subject’ header.

     In RFC 5322(6), an unstructured header is a run of arbitrary text
     in the ASCII character set.  RFC 2047(7), however, has an RFC
     5322(8) compatible mechanism for encoding non-ASCII text as ASCII
     characters within a header value.  When a 'value' containing
     encoded words is passed to the constructor, the
     ‘UnstructuredHeader’ parser converts such encoded words into
     unicode, following the RFC 2047(9) rules for unstructured text.
     The parser uses heuristics to attempt to decode certain
     non-compliant encoded words.  Defects are registered in such cases,
     as well as defects for issues such as invalid characters within the
     encoded words or the non-encoded text.

     This header type provides no additional attributes.

 -- 類別: email.headerregistry.DateHeader

     RFC 5322(10) specifies a very specific format for dates within
     email headers.  The ‘DateHeader’ parser recognizes that date
     format, as well as recognizing a number of variant forms that are
     sometimes found "in the wild".

     This header type provides the following additional attributes:

      -- 屬性: datetime

          If the header value can be recognized as a valid date of one
          form or another, this attribute will contain a *note datetime:
          1b0. instance representing that date.  If the timezone of the
          input date is specified as ‘-0000’ (indicating it is in UTC
          but contains no information about the source timezone), then
          *note datetime: 3411. will be a naive *note datetime: 1b0.  If
          a specific timezone offset is found (including ‘+0000’), then
          *note datetime: 3411. will contain an aware ‘datetime’ that
          uses *note datetime.timezone: 1059. to record the timezone
          offset.

     The ‘decoded’ value of the header is determined by formatting the
     ‘datetime’ according to the RFC 5322(11) rules; that is, it is set
     to:

          email.utils.format_datetime(self.datetime)

     When creating a ‘DateHeader’, 'value' may be *note datetime: 1b0.
     instance.  This means, for example, that the following code is
     valid and does what one would expect:

          msg['Date'] = datetime(2011, 7, 15, 21)

     Because this is a naive ‘datetime’ it will be interpreted as a UTC
     timestamp, and the resulting value will have a timezone of ‘-0000’.
     Much more useful is to use the *note localtime(): 2a6. function
     from the *note utils: 47. module:

          msg['Date'] = utils.localtime()

     This example sets the date header to the current time and date
     using the current timezone offset.

 -- 類別: email.headerregistry.AddressHeader

     Address headers are one of the most complex structured header
     types.  The ‘AddressHeader’ class provides a generic interface to
     any address header.

     This header type provides the following additional attributes:

      -- 屬性: groups

          A tuple of *note Group: 3414. objects encoding the addresses
          and groups found in the header value.  Addresses that are not
          part of a group are represented in this list as single-address
          ‘Groups’ whose *note display_name: 3415. is ‘None’.

      -- 屬性: addresses

          A tuple of *note Address: 3417. objects encoding all of the
          individual addresses from the header value.  If the header
          value contains any groups, the individual addresses from the
          group are included in the list at the point where the group
          occurs in the value (that is, the list of addresses is
          "flattened" into a one dimensional list).

     The ‘decoded’ value of the header will have all encoded words
     decoded to unicode.  *note idna: 48. encoded domain names are also
     decoded to unicode.  The ‘decoded’ value is set by *note joining:
     20a4. the *note str: 3f2. value of the elements of the ‘groups’
     attribute with ‘', '’.

     A list of *note Address: 3417. and *note Group: 3414. objects in
     any combination may be used to set the value of an address header.
     ‘Group’ objects whose ‘display_name’ is ‘None’ will be interpreted
     as single addresses, which allows an address list to be copied with
     groups intact by using the list obtained from the ‘groups’
     attribute of the source header.

 -- 類別: email.headerregistry.SingleAddressHeader

     A subclass of *note AddressHeader: 3412. that adds one additional
     attribute:

      -- 屬性: address

          The single address encoded by the header value.  If the header
          value actually contains more than one address (which would be
          a violation of the RFC under the default *note policy: 46.),
          accessing this attribute will result in a *note ValueError:
          1e7.

Many of the above classes also have a ‘Unique’ variant (for example,
‘UniqueUnstructuredHeader’).  The only difference is that in the
‘Unique’ variant, *note max_count: 33f0. is set to 1.

 -- 類別: email.headerregistry.MIMEVersionHeader

     There is really only one valid value for the ‘MIME-Version’ header,
     and that is ‘1.0’.  For future proofing, this header class supports
     other valid version numbers.  If a version number has a valid value
     per RFC 2045(12), then the header object will have non-‘None’
     values for the following attributes:

      -- 屬性: version

          The version number as a string, with any whitespace and/or
          comments removed.

      -- 屬性: major

          The major version number as an integer

      -- 屬性: minor

          The minor version number as an integer

 -- 類別: email.headerregistry.ParameterizedMIMEHeader

     MIME headers all start with the prefix 'Content-'.  Each specific
     header has a certain value, described under the class for that
     header.  Some can also take a list of supplemental parameters,
     which have a common format.  This class serves as a base for all
     the MIME headers that take parameters.

      -- 屬性: params

          A dictionary mapping parameter names to parameter values.

 -- 類別: email.headerregistry.ContentTypeHeader

     A *note ParameterizedMIMEHeader: 341e. class that handles the
     ‘Content-Type’ header.

      -- 屬性: content_type

          The content type string, in the form ‘maintype/subtype’.

      -- 屬性: maintype

      -- 屬性: subtype

 -- 類別: email.headerregistry.ContentDispositionHeader

     A *note ParameterizedMIMEHeader: 341e. class that handles the
     ‘Content-Disposition’ header.

      -- 屬性: content_disposition

          ‘inline’ and ‘attachment’ are the only valid values in common
          use.

 -- 類別: email.headerregistry.ContentTransferEncoding

     Handles the ‘Content-Transfer-Encoding’ header.

      -- 屬性: cte

          Valid values are ‘7bit’, ‘8bit’, ‘base64’, and
          ‘quoted-printable’.  See RFC 2045(13) for more information.

 -- 類別: email.headerregistry.HeaderRegistry (base_class=BaseHeader,
          default_class=UnstructuredHeader, use_default_map=True)

     This is the factory used by *note EmailPolicy: 1051. by default.
     ‘HeaderRegistry’ builds the class used to create a header instance
     dynamically, using 'base_class' and a specialized class retrieved
     from a registry that it holds.  When a given header name does not
     appear in the registry, the class specified by 'default_class' is
     used as the specialized class.  When 'use_default_map' is ‘True’
     (the default), the standard mapping of header names to classes is
     copied in to the registry during initialization.  'base_class' is
     always the last class in the generated class's ‘__bases__’ list.

     The default mappings are:


          subject: UniqueUnstructuredHeader


          date: UniqueDateHeader


          resent-date: DateHeader


          orig-date: UniqueDateHeader


          sender: UniqueSingleAddressHeader


          resent-sender: SingleAddressHeader


          to: UniqueAddressHeader


          resent-to: AddressHeader


          cc: UniqueAddressHeader


          resent-cc: AddressHeader


          bcc: UniqueAddressHeader


          resent-bcc: AddressHeader


          from: UniqueAddressHeader


          resent-from: AddressHeader


          reply-to: UniqueAddressHeader


          mime-version: MIMEVersionHeader


          content-type: ContentTypeHeader


          content-disposition: ContentDispositionHeader


          content-transfer-encoding: ContentTransferEncodingHeader


          message-id: MessageIDHeader

     ‘HeaderRegistry’ has the following methods:

      -- 方法: map_to_type (self, name, cls)

          'name' is the name of the header to be mapped.  It will be
          converted to lower case in the registry.  'cls' is the
          specialized class to be used, along with 'base_class', to
          create the class used to instantiate headers that match
          'name'.

      -- 方法: __getitem__ (name)

          Construct and return a class to handle creating a 'name'
          header.

      -- 方法: __call__ (name, value)

          Retrieves the specialized header associated with 'name' from
          the registry (using 'default_class' if 'name' does not appear
          in the registry) and composes it with 'base_class' to produce
          a class, calls the constructed class's constructor, passing it
          the same argument list, and finally returns the class instance
          created thereby.

The following classes are the classes used to represent data parsed from
structured headers and can, in general, be used by an application
program to construct structured values to assign to specific headers.

 -- 類別: email.headerregistry.Address (display_name='', username='',
          domain='', addr_spec=None)

     The class used to represent an email address.  The general form of
     an address is:

          [display_name] <username@domain>

     或是：

          username@domain

     where each part must conform to specific syntax rules spelled out
     in RFC 5322(14).

     As a convenience 'addr_spec' can be specified instead of 'username'
     and 'domain', in which case 'username' and 'domain' will be parsed
     from the 'addr_spec'.  An 'addr_spec' must be a properly RFC quoted
     string; if it is not ‘Address’ will raise an error.  Unicode
     characters are allowed and will be property encoded when
     serialized.  However, per the RFCs, unicode is 'not' allowed in the
     username portion of the address.

      -- 屬性: display_name

          The display name portion of the address, if any, with all
          quoting removed.  If the address does not have a display name,
          this attribute will be an empty string.

      -- 屬性: username

          The ‘username’ portion of the address, with all quoting
          removed.

      -- 屬性: domain

          The ‘domain’ portion of the address.

      -- 屬性: addr_spec

          The ‘username@domain’ portion of the address, correctly quoted
          for use as a bare address (the second form shown above).  This
          attribute is not mutable.

      -- 方法: __str__ ()

          The ‘str’ value of the object is the address quoted according
          to RFC 5322(15) rules, but with no Content Transfer Encoding
          of any non-ASCII characters.

     To support SMTP ( RFC 5321(16)), ‘Address’ handles one special
     case: if ‘username’ and ‘domain’ are both the empty string (or
     ‘None’), then the string value of the ‘Address’ is ‘<>’.

 -- 類別: email.headerregistry.Group (display_name=None, addresses=None)

     The class used to represent an address group.  The general form of
     an address group is:

          display_name: [address-list];

     As a convenience for processing lists of addresses that consist of
     a mixture of groups and single addresses, a ‘Group’ may also be
     used to represent single addresses that are not part of a group by
     setting 'display_name' to ‘None’ and providing a list of the single
     address as 'addresses'.

      -- 屬性: display_name

          The ‘display_name’ of the group.  If it is ‘None’ and there is
          exactly one ‘Address’ in ‘addresses’, then the ‘Group’
          represents a single address that is not in a group.

      -- 屬性: addresses

          A possibly empty tuple of *note Address: 3417. objects
          representing the addresses in the group.

      -- 方法: __str__ ()

          The ‘str’ value of a ‘Group’ is formatted according to RFC
          5322(17), but with no Content Transfer Encoding of any
          non-ASCII characters.  If ‘display_name’ is none and there is
          a single ‘Address’ in the ‘addresses’ list, the ‘str’ value
          will be the same as the ‘str’ of that single ‘Address’.

註解
....

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/email/headerregistry.py

   (2) Originally added in 3.3 as a *note provisional module: fe4.

   (3) https://datatracker.ietf.org/doc/html/rfc5322.html

   (4) https://datatracker.ietf.org/doc/html/rfc2047.html

   (5) https://datatracker.ietf.org/doc/html/rfc5322.html

   (6) https://datatracker.ietf.org/doc/html/rfc5322.html

   (7) https://datatracker.ietf.org/doc/html/rfc2047.html

   (8) https://datatracker.ietf.org/doc/html/rfc5322.html

   (9) https://datatracker.ietf.org/doc/html/rfc2047.html

   (10) https://datatracker.ietf.org/doc/html/rfc5322.html

   (11) https://datatracker.ietf.org/doc/html/rfc5322.html

   (12) https://datatracker.ietf.org/doc/html/rfc2045.html

   (13) https://datatracker.ietf.org/doc/html/rfc2045.html

   (14) https://datatracker.ietf.org/doc/html/rfc5322.html

   (15) https://datatracker.ietf.org/doc/html/rfc5322.html

   (16) https://datatracker.ietf.org/doc/html/rfc5321.html

   (17) https://datatracker.ietf.org/doc/html/rfc5322.html


File: python.info,  Node: email contentmanager：管理 MIME 內容,  Next: email：範例,  Prev: email headerregistry：自訂標頭物件,  Up: email --- 郵件和 MIME 處理套件

5.19.1.10 ‘email.contentmanager’：管理 MIME 內容
................................................

'原始碼：'Lib/email/contentmanager.py(1)

__________________________________________________________________

在 3.6 版被加入: (2)

 -- 類別: email.contentmanager.ContentManager

     Base class for content managers.  Provides the standard registry
     mechanisms to register converters between MIME content and other
     representations, as well as the ‘get_content’ and ‘set_content’
     dispatch methods.

      -- 方法: get_content (msg, *args, **kw)

          Look up a handler function based on the ‘mimetype’ of 'msg'
          (see next paragraph), call it, passing through all arguments,
          and return the result of the call.  The expectation is that
          the handler will extract the payload from 'msg' and return an
          object that encodes information about the extracted data.

          To find the handler, look for the following keys in the
          registry, stopping with the first one found:

             * the string representing the full MIME type
               (‘maintype/subtype’)

             * the string representing the ‘maintype’

             * the empty string

          If none of these keys produce a handler, raise a *note
          KeyError: 2fb. for the full MIME type.

      -- 方法: set_content (msg, obj, *args, **kw)

          If the ‘maintype’ is ‘multipart’, raise a *note TypeError:
          4dd.; otherwise look up a handler function based on the type
          of 'obj' (see next paragraph), call *note clear_content():
          33c4. on the 'msg', and call the handler function, passing
          through all arguments.  The expectation is that the handler
          will transform and store 'obj' into 'msg', possibly making
          other changes to 'msg' as well, such as adding various MIME
          headers to encode information needed to interpret the stored
          data.

          To find the handler, obtain the type of 'obj' (‘typ =
          type(obj)’), and look for the following keys in the registry,
          stopping with the first one found:

             * the type itself (‘typ’)

             * the type's fully qualified name (‘typ.__module__ + '.' +
               typ.__qualname__’).

             * the type's qualname (‘typ.__qualname__’)

             * the type's name (‘typ.__name__’).

          If none of the above match, repeat all of the checks above for
          each of the types in the *note MRO: 3434. (‘typ.__mro__’).
          Finally, if no other key yields a handler, check for a handler
          for the key ‘None’.  If there is no handler for ‘None’, raise
          a *note KeyError: 2fb. for the fully qualified name of the
          type.

          Also add a ‘MIME-Version’ header if one is not present (see
          also *note MIMEPart: ede.).

      -- 方法: add_get_handler (key, handler)

          Record the function 'handler' as the handler for 'key'.  For
          the possible values of 'key', see *note get_content(): 3436.

      -- 方法: add_set_handler (typekey, handler)

          Record 'handler' as the function to call when an object of a
          type matching 'typekey' is passed to *note set_content():
          3438.  For the possible values of 'typekey', see *note
          set_content(): 3438.

* Menu:

* Content Manager Instances::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/email/contentmanager.py

   (2) Originally added in 3.4 as a *note provisional module: fe4.


File: python.info,  Node: Content Manager Instances,  Up: email contentmanager：管理 MIME 內容

5.19.1.11 Content Manager Instances
...................................

Currently the email package provides only one concrete content manager,
*note raw_data_manager: 33ee, although more may be added in the future.
*note raw_data_manager: 33ee. is the *note content_manager: edf.
provided by *note EmailPolicy: 1051. and its derivatives.

 -- 資料: email.contentmanager.raw_data_manager

     This content manager provides only a minimum interface beyond that
     provided by *note Message: 261. itself: it deals only with text,
     raw byte strings, and *note Message: 261. objects.  Nevertheless,
     it provides significant advantages compared to the base API:
     ‘get_content’ on a text part will return a unicode string without
     the application needing to manually decode it, ‘set_content’
     provides a rich set of options for controlling the headers added to
     a part and controlling the content transfer encoding, and it
     enables the use of the various ‘add_’ methods, thereby simplifying
     the creation of multipart messages.

      -- 方法: email.contentmanager.get_content (msg, errors='replace')

          Return the payload of the part as either a string (for ‘text’
          parts), an *note EmailMessage: 260. object (for
          ‘message/rfc822’ parts), or a ‘bytes’ object (for all other
          non-multipart types).  Raise a *note KeyError: 2fb. if called
          on a ‘multipart’.  If the part is a ‘text’ part and 'errors'
          is specified, use it as the error handler when decoding the
          payload to unicode.  The default error handler is ‘replace’.

      -- 方法: email.contentmanager.set_content (msg, <'str'>,
               subtype="plain", charset='utf-8', cte=None,
               disposition=None, filename=None, cid=None, params=None,
               headers=None)

      -- 方法: email.contentmanager.set_content (msg, <'bytes'>,
               maintype, subtype, cte="base64", disposition=None,
               filename=None, cid=None, params=None, headers=None)

      -- 方法: email.contentmanager.set_content (msg, <'EmailMessage'>,
               cte=None, disposition=None, filename=None, cid=None,
               params=None, headers=None)

          Add headers and payload to 'msg':

          Add a ‘Content-Type’ header with a ‘maintype/subtype’ value.

             * For ‘str’, set the MIME ‘maintype’ to ‘text’, and set the
               subtype to 'subtype' if it is specified, or ‘plain’ if it
               is not.

             * For ‘bytes’, use the specified 'maintype' and 'subtype',
               or raise a *note TypeError: 4dd. if they are not
               specified.

             * For *note EmailMessage: 260. objects, set the maintype to
               ‘message’, and set the subtype to 'subtype' if it is
               specified or ‘rfc822’ if it is not.  If 'subtype' is
               ‘partial’, raise an error (‘bytes’ objects must be used
               to construct ‘message/partial’ parts).

          If 'charset' is provided (which is valid only for ‘str’),
          encode the string to bytes using the specified character set.
          The default is ‘utf-8’.  If the specified 'charset' is a known
          alias for a standard MIME charset name, use the standard
          charset instead.

          If 'cte' is set, encode the payload using the specified
          content transfer encoding, and set the
          ‘Content-Transfer-Encoding’ header to that value.  Possible
          values for 'cte' are ‘quoted-printable’, ‘base64’, ‘7bit’,
          ‘8bit’, and ‘binary’.  If the input cannot be encoded in the
          specified encoding (for example, specifying a 'cte' of ‘7bit’
          for an input that contains non-ASCII values), raise a *note
          ValueError: 1e7.

             * For ‘str’ objects, if 'cte' is not set use heuristics to
               determine the most compact encoding.

             * For *note EmailMessage: 260, per RFC 2046(1), raise an
               error if a 'cte' of ‘quoted-printable’ or ‘base64’ is
               requested for 'subtype' ‘rfc822’, and for any 'cte' other
               than ‘7bit’ for 'subtype' ‘external-body’.  For
               ‘message/rfc822’, use ‘8bit’ if 'cte' is not specified.
               For all other values of 'subtype', use ‘7bit’.

               備註: A 'cte' of ‘binary’ does not actually work
               correctly yet.  The ‘EmailMessage’ object as modified by
               ‘set_content’ is correct, but *note BytesGenerator: 1167.
               does not serialize it correctly.

          If 'disposition' is set, use it as the value of the
          ‘Content-Disposition’ header.  If not specified, and
          'filename' is specified, add the header with the value
          ‘attachment’.  If 'disposition' is not specified and
          'filename' is also not specified, do not add the header.  The
          only valid values for 'disposition' are ‘attachment’ and
          ‘inline’.

          If 'filename' is specified, use it as the value of the
          ‘filename’ parameter of the ‘Content-Disposition’ header.

          If 'cid' is specified, add a ‘Content-ID’ header with 'cid' as
          its value.

          If 'params' is specified, iterate its ‘items’ method and use
          the resulting ‘(key, value)’ pairs to set additional
          parameters on the ‘Content-Type’ header.

          If 'headers' is specified and is a list of strings of the form
          ‘headername: headervalue’ or a list of ‘header’ objects
          (distinguished from strings by having a ‘name’ attribute), add
          the headers to 'msg'.

註解
....

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2046.html


File: python.info,  Node: email：範例,  Next: email message Message Representing an email message using the compat32 API,  Prev: email contentmanager：管理 MIME 內容,  Up: email --- 郵件和 MIME 處理套件

5.19.1.12 ‘email’：範例
.......................

Here are a few examples of how to use the *note email: 32. package to
read, write, and send simple email messages, as well as more complex
MIME messages.

First, let's see how to create and send a simple text message (both the
text content and the addresses may contain unicode characters):

     # Import smtplib for the actual sending function
     import smtplib

     # Import the email modules we'll need
     from email.message import EmailMessage

     # Open the plain text file whose name is in textfile for reading.
     with open(textfile) as fp:
         # Create a text/plain message
         msg = EmailMessage()
         msg.set_content(fp.read())

     # me == the sender's email address
     # you == the recipient's email address
     msg['Subject'] = f'The contents of {textfile}'
     msg['From'] = me
     msg['To'] = you

     # Send the message via our own SMTP server.
     s = smtplib.SMTP('localhost')
     s.send_message(msg)
     s.quit()

Parsing RFC 822(1) headers can easily be done by the using the classes
from the *note parser: 45. module:

     # Import the email modules we'll need
     #from email.parser import BytesParser
     from email.parser import Parser
     from email.policy import default

     # If the e-mail headers are in a file, uncomment these two lines:
     # with open(messagefile, 'rb') as fp:
     #     headers = BytesParser(policy=default).parse(fp)

     #  Or for parsing headers in a string (this is an uncommon operation), use:
     headers = Parser(policy=default).parsestr(
             'From: Foo Bar <user@example.com>\n'
             'To: <someone_else@example.com>\n'
             'Subject: Test message\n'
             '\n'
             'Body would go here\n')

     #  Now the header items can be accessed as a dictionary:
     print('To: {}'.format(headers['to']))
     print('From: {}'.format(headers['from']))
     print('Subject: {}'.format(headers['subject']))

     # You can also access the parts of the addresses:
     print('Recipient username: {}'.format(headers['to'].addresses[0].username))
     print('Sender name: {}'.format(headers['from'].addresses[0].display_name))

Here's an example of how to send a MIME message containing a bunch of
family pictures that may be residing in a directory:

     # Import smtplib for the actual sending function.
     import smtplib

     # Here are the email package modules we'll need.
     from email.message import EmailMessage

     # Create the container email message.
     msg = EmailMessage()
     msg['Subject'] = 'Our family reunion'
     # me == the sender's email address
     # family = the list of all recipients' email addresses
     msg['From'] = me
     msg['To'] = ', '.join(family)
     msg.preamble = 'You will not see this in a MIME-aware mail reader.\n'

     # Open the files in binary mode.  You can also omit the subtype
     # if you want MIMEImage to guess it.
     for file in pngfiles:
         with open(file, 'rb') as fp:
             img_data = fp.read()
         msg.add_attachment(img_data, maintype='image',
                                      subtype='png')

     # Send the email via our own SMTP server.
     with smtplib.SMTP('localhost') as s:
         s.send_message(msg)

Here's an example of how to send the entire contents of a directory as
an email message: (2)

     #!/usr/bin/env python3

     """Send the contents of a directory as a MIME message."""

     import os
     import smtplib
     # For guessing MIME type based on file name extension
     import mimetypes

     from argparse import ArgumentParser

     from email.message import EmailMessage
     from email.policy import SMTP


     def main():
         parser = ArgumentParser(description="""\
     Send the contents of a directory as a MIME message.
     Unless the -o option is given, the email is sent by forwarding to your local
     SMTP server, which then does the normal delivery process.  Your local machine
     must be running an SMTP server.
     """)
         parser.add_argument('-d', '--directory',
                             help="""Mail the contents of the specified directory,
                             otherwise use the current directory.  Only the regular
                             files in the directory are sent, and we don't recurse to
                             subdirectories.""")
         parser.add_argument('-o', '--output',
                             metavar='FILE',
                             help="""Print the composed message to FILE instead of
                             sending the message to the SMTP server.""")
         parser.add_argument('-s', '--sender', required=True,
                             help='The value of the From: header (required)')
         parser.add_argument('-r', '--recipient', required=True,
                             action='append', metavar='RECIPIENT',
                             default=[], dest='recipients',
                             help='A To: header value (at least one required)')
         args = parser.parse_args()
         directory = args.directory
         if not directory:
             directory = '.'
         # Create the message
         msg = EmailMessage()
         msg['Subject'] = f'Contents of directory {os.path.abspath(directory)}'
         msg['To'] = ', '.join(args.recipients)
         msg['From'] = args.sender
         msg.preamble = 'You will not see this in a MIME-aware mail reader.\n'

         for filename in os.listdir(directory):
             path = os.path.join(directory, filename)
             if not os.path.isfile(path):
                 continue
             # Guess the content type based on the file's extension.  Encoding
             # will be ignored, although we should check for simple things like
             # gzip'd or compressed files.
             ctype, encoding = mimetypes.guess_file_type(path)
             if ctype is None or encoding is not None:
                 # No guess could be made, or the file is encoded (compressed), so
                 # use a generic bag-of-bits type.
                 ctype = 'application/octet-stream'
             maintype, subtype = ctype.split('/', 1)
             with open(path, 'rb') as fp:
                 msg.add_attachment(fp.read(),
                                    maintype=maintype,
                                    subtype=subtype,
                                    filename=filename)
         # Now send or store the message
         if args.output:
             with open(args.output, 'wb') as fp:
                 fp.write(msg.as_bytes(policy=SMTP))
         else:
             with smtplib.SMTP('localhost') as s:
                 s.send_message(msg)


     if __name__ == '__main__':
         main()

Here's an example of how to unpack a MIME message like the one above,
into a directory of files:

     #!/usr/bin/env python3

     """Unpack a MIME message into a directory of files."""

     import os
     import email
     import mimetypes

     from email.policy import default

     from argparse import ArgumentParser


     def main():
         parser = ArgumentParser(description="""\
     Unpack a MIME message into a directory of files.
     """)
         parser.add_argument('-d', '--directory', required=True,
                             help="""Unpack the MIME message into the named
                             directory, which will be created if it doesn't already
                             exist.""")
         parser.add_argument('msgfile')
         args = parser.parse_args()

         with open(args.msgfile, 'rb') as fp:
             msg = email.message_from_binary_file(fp, policy=default)

         try:
             os.mkdir(args.directory)
         except FileExistsError:
             pass

         counter = 1
         for part in msg.walk():
             # multipart/* are just containers
             if part.get_content_maintype() == 'multipart':
                 continue
             # Applications should really sanitize the given filename so that an
             # email message can't be used to overwrite important files
             filename = part.get_filename()
             if not filename:
                 ext = mimetypes.guess_extension(part.get_content_type())
                 if not ext:
                     # Use a generic bag-of-bits extension
                     ext = '.bin'
                 filename = f'part-{counter:03d}{ext}'
             counter += 1
             with open(os.path.join(args.directory, filename), 'wb') as fp:
                 fp.write(part.get_payload(decode=True))


     if __name__ == '__main__':
         main()

Here's an example of how to create an HTML message with an alternative
plain text version.  To make things a bit more interesting, we include a
related image in the html part, and we save a copy of what we are going
to send to disk, as well as sending it.

     #!/usr/bin/env python3

     import smtplib

     from email.message import EmailMessage
     from email.headerregistry import Address
     from email.utils import make_msgid

     # Create the base text message.
     msg = EmailMessage()
     msg['Subject'] = "Pourquoi pas des asperges pour ce midi ?"
     msg['From'] = Address("Pepé Le Pew", "pepe", "example.com")
     msg['To'] = (Address("Penelope Pussycat", "penelope", "example.com"),
                  Address("Fabrette Pussycat", "fabrette", "example.com"))
     msg.set_content("""\
     Salut!

     Cette recette [1] sera sûrement un très bon repas.

     [1] http://www.yummly.com/recipe/Roasted-Asparagus-Epicurious-203718

     --Pepé
     """)

     # Add the html version.  This converts the message into a multipart/alternative
     # container, with the original text message as the first part and the new html
     # message as the second part.
     asparagus_cid = make_msgid()
     msg.add_alternative("""\
     <html>
       <head></head>
       <body>
         <p>Salut!</p>
         <p>Cette
             <a href="http://www.yummly.com/recipe/Roasted-Asparagus-Epicurious-203718">
                 recette
             </a> sera sûrement un très bon repas.
         </p>
         <img src="cid:{asparagus_cid}" />
       </body>
     </html>
     """.format(asparagus_cid=asparagus_cid[1:-1]), subtype='html')
     # note that we needed to peel the <> off the msgid for use in the html.

     # Now add the related image to the html part.
     with open("roasted-asparagus.jpg", 'rb') as img:
         msg.get_payload()[1].add_related(img.read(), 'image', 'jpeg',
                                          cid=asparagus_cid)

     # Make a local copy of what we are going to send.
     with open('outgoing.msg', 'wb') as f:
         f.write(bytes(msg))

     # Send the message via local SMTP server.
     with smtplib.SMTP('localhost') as s:
         s.send_message(msg)

If we were sent the message from the last example, here is one way we
could process it:

     import os
     import sys
     import tempfile
     import mimetypes
     import webbrowser

     # Import the email modules we'll need
     from email import policy
     from email.parser import BytesParser


     def magic_html_parser(html_text, partfiles):
         """Return safety-sanitized html linked to partfiles.

         Rewrite the href="cid:...." attributes to point to the filenames in partfiles.
         Though not trivial, this should be possible using html.parser.
         """
         raise NotImplementedError("Add the magic needed")


     # In a real program you'd get the filename from the arguments.
     with open('outgoing.msg', 'rb') as fp:
         msg = BytesParser(policy=policy.default).parse(fp)

     # Now the header items can be accessed as a dictionary, and any non-ASCII will
     # be converted to unicode:
     print('To:', msg['to'])
     print('From:', msg['from'])
     print('Subject:', msg['subject'])

     # If we want to print a preview of the message content, we can extract whatever
     # the least formatted payload is and print the first three lines.  Of course,
     # if the message has no plain text part printing the first three lines of html
     # is probably useless, but this is just a conceptual example.
     simplest = msg.get_body(preferencelist=('plain', 'html'))
     print()
     print(''.join(simplest.get_content().splitlines(keepends=True)[:3]))

     ans = input("View full message?")
     if ans.lower()[0] == 'n':
         sys.exit()

     # We can extract the richest alternative in order to display it:
     richest = msg.get_body()
     partfiles = {}
     if richest['content-type'].maintype == 'text':
         if richest['content-type'].subtype == 'plain':
             for line in richest.get_content().splitlines():
                 print(line)
             sys.exit()
         elif richest['content-type'].subtype == 'html':
             body = richest
         else:
             print("Don't know how to display {}".format(richest.get_content_type()))
             sys.exit()
     elif richest['content-type'].content_type == 'multipart/related':
         body = richest.get_body(preferencelist=('html'))
         for part in richest.iter_attachments():
             fn = part.get_filename()
             if fn:
                 extension = os.path.splitext(part.get_filename())[1]
             else:
                 extension = mimetypes.guess_extension(part.get_content_type())
             with tempfile.NamedTemporaryFile(suffix=extension, delete=False) as f:
                 f.write(part.get_content())
                 # again strip the <> to go from email form of cid to html form.
                 partfiles[part['content-id'][1:-1]] = f.name
     else:
         print("Don't know how to display {}".format(richest.get_content_type()))
         sys.exit()
     with tempfile.NamedTemporaryFile(mode='w', delete=False) as f:
         f.write(magic_html_parser(body.get_content(), partfiles))
     webbrowser.open(f.name)
     os.remove(f.name)
     for fn in partfiles.values():
         os.remove(fn)

     # Of course, there are lots of email messages that could break this simple
     # minded program, but it will handle the most common ones.

Up to the prompt, the output from the above is:

     To: Penelope Pussycat <penelope@example.com>, Fabrette Pussycat <fabrette@example.com>
     From: Pepé Le Pew <pepe@example.com>
     Subject: Pourquoi pas des asperges pour ce midi ?

     Salut!

     Cette recette [1] sera sûrement un très bon repas.

註解
....

Legacy API:

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc822.html

   (2) Thanks to Matthew Dixon Cowles for the original inspiration and
examples.


File: python.info,  Node: email message Message Representing an email message using the compat32 API,  Next: email mime：從頭開始建立電子郵件和 MIME 物件,  Prev: email：範例,  Up: email --- 郵件和 MIME 處理套件

5.19.1.13 ‘email.message.Message’: Representing an email message using the ‘compat32’ API
.........................................................................................

The *note Message: 261. class is very similar to the *note EmailMessage:
260. class, without the methods added by that class, and with the
default behavior of certain other methods being slightly different.  We
also document here some methods that, while supported by the *note
EmailMessage: 260. class, are not recommended unless you are dealing
with legacy code.

The philosophy and structure of the two classes is otherwise the same.

This document describes the behavior under the default (for *note
Message: 261.) policy *note Compat32: 104e.  If you are going to use
another policy, you should be using the *note EmailMessage: 260. class
instead.

An email message consists of 'headers' and a 'payload'.  Headers must be
RFC 5322(1) style names and values, where the field name and value are
separated by a colon.  The colon is not part of either the field name or
the field value.  The payload may be a simple text message, or a binary
object, or a structured sequence of sub-messages each with their own set
of headers and their own payload.  The latter type of payload is
indicated by the message having a MIME type such as ‘multipart/*’ or
‘message/rfc822’.

The conceptual model provided by a *note Message: 261. object is that of
an ordered dictionary of headers with additional methods for accessing
both specialized information from the headers, for accessing the
payload, for generating a serialized version of the message, and for
recursively walking over the object tree.  Note that duplicate headers
are supported but special methods must be used to access them.

The *note Message: 261. pseudo-dictionary is indexed by the header
names, which must be ASCII values.  The values of the dictionary are
strings that are supposed to contain only ASCII characters; there is
some special handling for non-ASCII input, but it doesn't always produce
the correct results.  Headers are stored and returned in case-preserving
form, but field names are matched case-insensitively.  There may also be
a single envelope header, also known as the 'Unix-From' header or the
‘From_’ header.  The 'payload' is either a string or bytes, in the case
of simple message objects, or a list of *note Message: 261. objects, for
MIME container documents (e.g.  ‘multipart/*’ and ‘message/rfc822’).

Here are the methods of the *note Message: 261. class:

 -- 類別: email.message.Message (policy=compat32)

     If 'policy' is specified (it must be an instance of a *note policy:
     46. class) use the rules it specifies to update and serialize the
     representation of the message.  If 'policy' is not set, use the
     *note compat32: 104e. policy, which maintains backward
     compatibility with the Python 3.2 version of the email package.
     For more information see the *note policy: 46. documentation.

     在 3.3 版的變更: 新增 'policy' 關鍵字引數。

      -- 方法: as_string (unixfrom=False, maxheaderlen=0, policy=None)

          Return the entire message flattened as a string.  When
          optional 'unixfrom' is true, the envelope header is included
          in the returned string.  'unixfrom' defaults to ‘False’.  For
          backward compatibility reasons, 'maxheaderlen' defaults to
          ‘0’, so if you want a different value you must override it
          explicitly (the value specified for 'max_line_length' in the
          policy will be ignored by this method).  The 'policy' argument
          may be used to override the default policy obtained from the
          message instance.  This can be used to control some of the
          formatting produced by the method, since the specified
          'policy' will be passed to the ‘Generator’.

          Flattening the message may trigger changes to the *note
          Message: 261. if defaults need to be filled in to complete the
          transformation to a string (for example, MIME boundaries may
          be generated or modified).

          Note that this method is provided as a convenience and may not
          always format the message the way you want.  For example, by
          default it does not do the mangling of lines that begin with
          ‘From’ that is required by the Unix mbox format.  For more
          flexibility, instantiate a *note Generator: 1166. instance and
          use its *note flatten(): 33dd. method directly.  For example:

               from io import StringIO
               from email.generator import Generator
               fp = StringIO()
               g = Generator(fp, mangle_from_=True, maxheaderlen=60)
               g.flatten(msg)
               text = fp.getvalue()

          If the message object contains binary data that is not encoded
          according to RFC standards, the non-compliant data will be
          replaced by unicode "unknown character" code points.  (See
          also *note as_bytes(): edb. and *note BytesGenerator: 1167.)

          在 3.4 版的變更: 新增 'policy' 關鍵字引數。

      -- 方法: __str__ ()

          Equivalent to *note as_string(): eda.  Allows ‘str(msg)’ to
          produce a string containing the formatted message.

      -- 方法: as_bytes (unixfrom=False, policy=None)

          Return the entire message flattened as a bytes object.  When
          optional 'unixfrom' is true, the envelope header is included
          in the returned string.  'unixfrom' defaults to ‘False’.  The
          'policy' argument may be used to override the default policy
          obtained from the message instance.  This can be used to
          control some of the formatting produced by the method, since
          the specified 'policy' will be passed to the ‘BytesGenerator’.

          Flattening the message may trigger changes to the *note
          Message: 261. if defaults need to be filled in to complete the
          transformation to a string (for example, MIME boundaries may
          be generated or modified).

          Note that this method is provided as a convenience and may not
          always format the message the way you want.  For example, by
          default it does not do the mangling of lines that begin with
          ‘From’ that is required by the Unix mbox format.  For more
          flexibility, instantiate a *note BytesGenerator: 1167.
          instance and use its *note flatten(): 33d9. method directly.
          For example:

               from io import BytesIO
               from email.generator import BytesGenerator
               fp = BytesIO()
               g = BytesGenerator(fp, mangle_from_=True, maxheaderlen=60)
               g.flatten(msg)
               text = fp.getvalue()

          在 3.4 版被加入.

      -- 方法: __bytes__ ()

          Equivalent to *note as_bytes(): edb.  Allows ‘bytes(msg)’ to
          produce a bytes object containing the formatted message.

          在 3.4 版被加入.

      -- 方法: is_multipart ()

          Return ‘True’ if the message's payload is a list of sub-*note
          Message: 261. objects, otherwise return ‘False’.  When *note
          is_multipart(): 33b3. returns ‘False’, the payload should be a
          string object (which might be a CTE encoded binary payload).
          (Note that *note is_multipart(): 33b3. returning ‘True’ does
          not necessarily mean that "msg.get_content_maintype() ==
          'multipart'" will return the ‘True’.  For example,
          ‘is_multipart’ will return ‘True’ when the *note Message: 261.
          is of type ‘message/rfc822’.)

      -- 方法: set_unixfrom (unixfrom)

          Set the message's envelope header to 'unixfrom', which should
          be a string.

      -- 方法: get_unixfrom ()

          Return the message's envelope header.  Defaults to ‘None’ if
          the envelope header was never set.

      -- 方法: attach (payload)

          Add the given 'payload' to the current payload, which must be
          ‘None’ or a list of *note Message: 261. objects before the
          call.  After the call, the payload will always be a list of
          *note Message: 261. objects.  If you want to set the payload
          to a scalar object (e.g.  a string), use *note set_payload():
          3441. instead.

          This is a legacy method.  On the ‘EmailMessage’ class its
          functionality is replaced by *note set_content(): 17ab. and
          the related ‘make’ and ‘add’ methods.

      -- 方法: get_payload (i=None, decode=False)

          Return the current payload, which will be a list of *note
          Message: 261. objects when *note is_multipart(): 33b3. is
          ‘True’, or a string when *note is_multipart(): 33b3. is
          ‘False’.  If the payload is a list and you mutate the list
          object, you modify the message's payload in place.

          With optional argument 'i', *note get_payload(): 1165. will
          return the 'i'-th element of the payload, counting from zero,
          if *note is_multipart(): 33b3. is ‘True’.  An *note
          IndexError: 14a3. will be raised if 'i' is less than 0 or
          greater than or equal to the number of items in the payload.
          If the payload is a string (i.e.  *note is_multipart(): 33b3.
          is ‘False’) and 'i' is given, a *note TypeError: 4dd. is
          raised.

          Optional 'decode' is a flag indicating whether the payload
          should be decoded or not, according to the
          ‘Content-Transfer-Encoding’ header.  When ‘True’ and the
          message is not a multipart, the payload will be decoded if
          this header's value is ‘quoted-printable’ or ‘base64’.  If
          some other encoding is used, or ‘Content-Transfer-Encoding’
          header is missing, the payload is returned as-is (undecoded).
          In all cases the returned value is binary data.  If the
          message is a multipart and the 'decode' flag is ‘True’, then
          ‘None’ is returned.  If the payload is base64 and it was not
          perfectly formed (missing padding, characters outside the
          base64 alphabet), then an appropriate defect will be added to
          the message's defect property (‘InvalidBase64PaddingDefect’ or
          ‘InvalidBase64CharactersDefect’, respectively).

          When 'decode' is ‘False’ (the default) the body is returned as
          a string without decoding the ‘Content-Transfer-Encoding’.
          However, for a ‘Content-Transfer-Encoding’ of 8bit, an attempt
          is made to decode the original bytes using the ‘charset’
          specified by the ‘Content-Type’ header, using the ‘replace’
          error handler.  If no ‘charset’ is specified, or if the
          ‘charset’ given is not recognized by the email package, the
          body is decoded using the default ASCII charset.

          This is a legacy method.  On the ‘EmailMessage’ class its
          functionality is replaced by *note get_content(): 33b9. and
          *note iter_parts(): 33b8.

      -- 方法: set_payload (payload, charset=None)

          Set the entire message object's payload to 'payload'.  It is
          the client's responsibility to ensure the payload invariants.
          Optional 'charset' sets the message's default character set;
          see *note set_charset(): 3442. for details.

          This is a legacy method.  On the ‘EmailMessage’ class its
          functionality is replaced by *note set_content(): 17ab.

      -- 方法: set_charset (charset)

          Set the character set of the payload to 'charset', which can
          either be a *note Charset: da0. instance (see *note
          email.charset: 33.), a string naming a character set, or
          ‘None’.  If it is a string, it will be converted to a *note
          Charset: da0. instance.  If 'charset' is ‘None’, the ‘charset’
          parameter will be removed from the ‘Content-Type’ header (the
          message will not be otherwise modified).  Anything else will
          generate a *note TypeError: 4dd.

          If there is no existing ‘MIME-Version’ header one will be
          added.  If there is no existing ‘Content-Type’ header, one
          will be added with a value of ‘text/plain’.  Whether the
          ‘Content-Type’ header already exists or not, its ‘charset’
          parameter will be set to 'charset.output_charset'.  If
          'charset.input_charset' and 'charset.output_charset' differ,
          the payload will be re-encoded to the 'output_charset'.  If
          there is no existing ‘Content-Transfer-Encoding’ header, then
          the payload will be transfer-encoded, if needed, using the
          specified *note Charset: da0, and a header with the
          appropriate value will be added.  If a
          ‘Content-Transfer-Encoding’ header already exists, the payload
          is assumed to already be correctly encoded using that
          ‘Content-Transfer-Encoding’ and is not modified.

          This is a legacy method.  On the ‘EmailMessage’ class its
          functionality is replaced by the 'charset' parameter of the
          ‘email.emailmessage.EmailMessage.set_content()’ method.

      -- 方法: get_charset ()

          Return the *note Charset: da0. instance associated with the
          message's payload.

          This is a legacy method.  On the ‘EmailMessage’ class it
          always returns ‘None’.

     The following methods implement a mapping-like interface for
     accessing the message's RFC 2822(2) headers.  Note that there are
     some semantic differences between these methods and a normal
     mapping (i.e.  dictionary) interface.  For example, in a dictionary
     there are no duplicate keys, but here there may be duplicate
     message headers.  Also, in dictionaries there is no guaranteed
     order to the keys returned by *note keys(): 3444, but in a *note
     Message: 261. object, headers are always returned in the order they
     appeared in the original message, or were added to the message
     later.  Any header deleted and then re-added are always appended to
     the end of the header list.

     These semantic differences are intentional and are biased toward
     maximal convenience.

     Note that in all cases, any envelope header present in the message
     is not included in the mapping interface.

     In a model generated from bytes, any header values that (in
     contravention of the RFCs) contain non-ASCII bytes will, when
     retrieved through this interface, be represented as *note Header:
     17ac. objects with a charset of ‘unknown-8bit’.

      -- 方法: __len__ ()

          Return the total number of headers, including duplicates.

      -- 方法: __contains__ (name)

          Return ‘True’ if the message object has a field named 'name'.
          Matching is done case-insensitively and 'name' should not
          include the trailing colon.  Used for the ‘in’ operator, e.g.:

               if 'message-id' in myMessage:
                  print('Message-ID:', myMessage['message-id'])

      -- 方法: __getitem__ (name)

          Return the value of the named header field.  'name' should not
          include the colon field separator.  If the header is missing,
          ‘None’ is returned; a *note KeyError: 2fb. is never raised.

          Note that if the named field appears more than once in the
          message's headers, exactly which of those field values will be
          returned is undefined.  Use the *note get_all(): 3447. method
          to get the values of all the extant named headers.

      -- 方法: __setitem__ (name, val)

          Add a header to the message with field name 'name' and value
          'val'.  The field is appended to the end of the message's
          existing fields.

          Note that this does 'not' overwrite or delete any existing
          header with the same name.  If you want to ensure that the new
          header is the only one present in the message with field name
          'name', delete the field first, e.g.:

               del msg['subject']
               msg['subject'] = 'Python roolz!'

      -- 方法: __delitem__ (name)

          Delete all occurrences of the field with name 'name' from the
          message's headers.  No exception is raised if the named field
          isn't present in the headers.

      -- 方法: keys ()

          Return a list of all the message's header field names.

      -- 方法: values ()

          Return a list of all the message's field values.

      -- 方法: items ()

          Return a list of 2-tuples containing all the message's field
          headers and values.

      -- 方法: get (name, failobj=None)

          Return the value of the named header field.  This is identical
          to *note __getitem__(): 266. except that optional 'failobj' is
          returned if the named header is missing (defaults to ‘None’).

     Here are some additional useful methods:

      -- 方法: get_all (name, failobj=None)

          Return a list of all the values for the field named 'name'.
          If there are no such named headers in the message, 'failobj'
          is returned (defaults to ‘None’).

      -- 方法: add_header (_name, _value, **_params)

          Extended header setting.  This method is similar to *note
          __setitem__(): 3448. except that additional header parameters
          can be provided as keyword arguments.  '_name' is the header
          field to add and '_value' is the 'primary' value for the
          header.

          For each item in the keyword argument dictionary '_params',
          the key is taken as the parameter name, with underscores
          converted to dashes (since dashes are illegal in Python
          identifiers).  Normally, the parameter will be added as
          ‘key="value"’ unless the value is ‘None’, in which case only
          the key will be added.  If the value contains non-ASCII
          characters, it can be specified as a three tuple in the format
          ‘(CHARSET, LANGUAGE, VALUE)’, where ‘CHARSET’ is a string
          naming the charset to be used to encode the value, ‘LANGUAGE’
          can usually be set to ‘None’ or the empty string (see RFC
          2231(3) for other possibilities), and ‘VALUE’ is the string
          value containing non-ASCII code points.  If a three tuple is
          not passed and the value contains non-ASCII characters, it is
          automatically encoded in RFC 2231(4) format using a ‘CHARSET’
          of ‘utf-8’ and a ‘LANGUAGE’ of ‘None’.

          以下是個範例：

               msg.add_header('Content-Disposition', 'attachment', filename='bud.gif')

          This will add a header that looks like

               Content-Disposition: attachment; filename="bud.gif"

          An example with non-ASCII characters:

               msg.add_header('Content-Disposition', 'attachment',
                              filename=('iso-8859-1', '', 'Fußballer.ppt'))

          Which produces

               Content-Disposition: attachment; filename*="iso-8859-1''Fu%DFballer.ppt"

      -- 方法: replace_header (_name, _value)

          Replace a header.  Replace the first header found in the
          message that matches '_name', retaining header order and field
          name case.  If no matching header was found, a *note KeyError:
          2fb. is raised.

      -- 方法: get_content_type ()

          Return the message's content type.  The returned string is
          coerced to lower case of the form ‘maintype/subtype’.  If
          there was no ‘Content-Type’ header in the message the default
          type as given by *note get_default_type(): 3450. will be
          returned.  Since according to RFC 2045(5), messages always
          have a default type, *note get_content_type(): 344f. will
          always return a value.

          RFC 2045(6) defines a message's default type to be
          ‘text/plain’ unless it appears inside a ‘multipart/digest’
          container, in which case it would be ‘message/rfc822’.  If the
          ‘Content-Type’ header has an invalid type specification, RFC
          2045(7) mandates that the default type be ‘text/plain’.

      -- 方法: get_content_maintype ()

          Return the message's main content type.  This is the
          ‘maintype’ part of the string returned by *note
          get_content_type(): 344f.

      -- 方法: get_content_subtype ()

          Return the message's sub-content type.  This is the ‘subtype’
          part of the string returned by *note get_content_type(): 344f.

      -- 方法: get_default_type ()

          Return the default content type.  Most messages have a default
          content type of ‘text/plain’, except for messages that are
          subparts of ‘multipart/digest’ containers.  Such subparts have
          a default content type of ‘message/rfc822’.

      -- 方法: set_default_type (ctype)

          Set the default content type.  'ctype' should either be
          ‘text/plain’ or ‘message/rfc822’, although this is not
          enforced.  The default content type is not stored in the
          ‘Content-Type’ header.

      -- 方法: get_params (failobj=None, header='content-type',
               unquote=True)

          Return the message's ‘Content-Type’ parameters, as a list.
          The elements of the returned list are 2-tuples of key/value
          pairs, as split on the ‘'='’ sign.  The left hand side of the
          ‘'='’ is the key, while the right hand side is the value.  If
          there is no ‘'='’ sign in the parameter the value is the empty
          string, otherwise the value is as described in *note
          get_param(): 3455. and is unquoted if optional 'unquote' is
          ‘True’ (the default).

          Optional 'failobj' is the object to return if there is no
          ‘Content-Type’ header.  Optional 'header' is the header to
          search instead of ‘Content-Type’.

          This is a legacy method.  On the ‘EmailMessage’ class its
          functionality is replaced by the 'params' property of the
          individual header objects returned by the header access
          methods.

      -- 方法: get_param (param, failobj=None, header='content-type',
               unquote=True)

          Return the value of the ‘Content-Type’ header's parameter
          'param' as a string.  If the message has no ‘Content-Type’
          header or if there is no such parameter, then 'failobj' is
          returned (defaults to ‘None’).

          Optional 'header' if given, specifies the message header to
          use instead of ‘Content-Type’.

          Parameter keys are always compared case insensitively.  The
          return value can either be a string, or a 3-tuple if the
          parameter was RFC 2231(8) encoded.  When it's a 3-tuple, the
          elements of the value are of the form ‘(CHARSET, LANGUAGE,
          VALUE)’.  Note that both ‘CHARSET’ and ‘LANGUAGE’ can be
          ‘None’, in which case you should consider ‘VALUE’ to be
          encoded in the ‘us-ascii’ charset.  You can usually ignore
          ‘LANGUAGE’.

          If your application doesn't care whether the parameter was
          encoded as in RFC 2231(9), you can collapse the parameter
          value by calling *note email.utils.collapse_rfc2231_value():
          3456, passing in the return value from *note get_param():
          3455.  This will return a suitably decoded Unicode string when
          the value is a tuple, or the original string unquoted if it
          isn't.  For example:

               rawparam = msg.get_param('foo')
               param = email.utils.collapse_rfc2231_value(rawparam)

          In any case, the parameter value (either the returned string,
          or the ‘VALUE’ item in the 3-tuple) is always unquoted, unless
          'unquote' is set to ‘False’.

          This is a legacy method.  On the ‘EmailMessage’ class its
          functionality is replaced by the 'params' property of the
          individual header objects returned by the header access
          methods.

      -- 方法: set_param (param, value, header='Content-Type',
               requote=True, charset=None, language='', replace=False)

          Set a parameter in the ‘Content-Type’ header.  If the
          parameter already exists in the header, its value will be
          replaced with 'value'.  If the ‘Content-Type’ header as not
          yet been defined for this message, it will be set to
          ‘text/plain’ and the new parameter value will be appended as
          per RFC 2045(10).

          Optional 'header' specifies an alternative header to
          ‘Content-Type’, and all parameters will be quoted as necessary
          unless optional 'requote' is ‘False’ (the default is ‘True’).

          If optional 'charset' is specified, the parameter will be
          encoded according to RFC 2231(11).  Optional 'language'
          specifies the RFC 2231 language, defaulting to the empty
          string.  Both 'charset' and 'language' should be strings.

          If 'replace' is ‘False’ (the default) the header is moved to
          the end of the list of headers.  If 'replace' is ‘True’, the
          header will be updated in place.

          在 3.4 版的變更: ‘replace’ keyword was added.

      -- 方法: del_param (param, header='content-type', requote=True)

          Remove the given parameter completely from the ‘Content-Type’
          header.  The header will be re-written in place without the
          parameter or its value.  All values will be quoted as
          necessary unless 'requote' is ‘False’ (the default is ‘True’).
          Optional 'header' specifies an alternative to ‘Content-Type’.

      -- 方法: set_type (type, header='Content-Type', requote=True)

          Set the main type and subtype for the ‘Content-Type’ header.
          'type' must be a string in the form ‘maintype/subtype’,
          otherwise a *note ValueError: 1e7. is raised.

          This method replaces the ‘Content-Type’ header, keeping all
          the parameters in place.  If 'requote' is ‘False’, this leaves
          the existing header's quoting as is, otherwise the parameters
          will be quoted (the default).

          An alternative header can be specified in the 'header'
          argument.  When the ‘Content-Type’ header is set a
          ‘MIME-Version’ header is also added.

          This is a legacy method.  On the ‘EmailMessage’ class its
          functionality is replaced by the ‘make_’ and ‘add_’ methods.

      -- 方法: get_filename (failobj=None)

          Return the value of the ‘filename’ parameter of the
          ‘Content-Disposition’ header of the message.  If the header
          does not have a ‘filename’ parameter, this method falls back
          to looking for the ‘name’ parameter on the ‘Content-Type’
          header.  If neither is found, or the header is missing, then
          'failobj' is returned.  The returned string will always be
          unquoted as per *note email.utils.unquote(): 33ac.

      -- 方法: get_boundary (failobj=None)

          Return the value of the ‘boundary’ parameter of the
          ‘Content-Type’ header of the message, or 'failobj' if either
          the header is missing, or has no ‘boundary’ parameter.  The
          returned string will always be unquoted as per *note
          email.utils.unquote(): 33ac.

      -- 方法: set_boundary (boundary)

          Set the ‘boundary’ parameter of the ‘Content-Type’ header to
          'boundary'.  *note set_boundary(): 345b. will always quote
          'boundary' if necessary.  A *note HeaderParseError: 33af. is
          raised if the message object has no ‘Content-Type’ header.

          Note that using this method is subtly different than deleting
          the old ‘Content-Type’ header and adding a new one with the
          new boundary via *note add_header(): 344d, because *note
          set_boundary(): 345b. preserves the order of the
          ‘Content-Type’ header in the list of headers.  However, it
          does 'not' preserve any continuation lines which may have been
          present in the original ‘Content-Type’ header.

      -- 方法: get_content_charset (failobj=None)

          Return the ‘charset’ parameter of the ‘Content-Type’ header,
          coerced to lower case.  If there is no ‘Content-Type’ header,
          or if that header has no ‘charset’ parameter, 'failobj' is
          returned.

          Note that this method differs from *note get_charset(): 3443.
          which returns the *note Charset: da0. instance for the default
          encoding of the message body.

      -- 方法: get_charsets (failobj=None)

          Return a list containing the character set names in the
          message.  If the message is a ‘multipart’, then the list will
          contain one element for each subpart in the payload,
          otherwise, it will be a list of length 1.

          Each item in the list will be a string which is the value of
          the ‘charset’ parameter in the ‘Content-Type’ header for the
          represented subpart.  However, if the subpart has no
          ‘Content-Type’ header, no ‘charset’ parameter, or is not of
          the ‘text’ main MIME type, then that item in the returned list
          will be 'failobj'.

      -- 方法: get_content_disposition ()

          Return the lowercased value (without parameters) of the
          message's ‘Content-Disposition’ header if it has one, or
          ‘None’.  The possible values for this method are 'inline',
          'attachment' or ‘None’ if the message follows RFC 2183(12).

          在 3.5 版被加入.

      -- 方法: walk ()

          The *note walk(): 345e. method is an all-purpose generator
          which can be used to iterate over all the parts and subparts
          of a message object tree, in depth-first traversal order.  You
          will typically use *note walk(): 345e. as the iterator in a
          ‘for’ loop; each iteration returns the next subpart.

          Here's an example that prints the MIME type of every part of a
          multipart message structure:

               >>> for part in msg.walk():
               ...     print(part.get_content_type())
               multipart/report
               text/plain
               message/delivery-status
               text/plain
               text/plain
               message/rfc822
               text/plain

          ‘walk’ iterates over the subparts of any part where *note
          is_multipart(): 33b3. returns ‘True’, even though
          ‘msg.get_content_maintype() == 'multipart'’ may return
          ‘False’.  We can see this in our example by making use of the
          ‘_structure’ debug helper function:

               >>> for part in msg.walk():
               ...     print(part.get_content_maintype() == 'multipart',
               ...           part.is_multipart())
               True True
               False False
               False True
               False False
               False False
               False True
               False False
               >>> _structure(msg)
               multipart/report
                   text/plain
                   message/delivery-status
                       text/plain
                       text/plain
                   message/rfc822
                       text/plain

          Here the ‘message’ parts are not ‘multiparts’, but they do
          contain subparts.  ‘is_multipart()’ returns ‘True’ and ‘walk’
          descends into the subparts.

     *note Message: 261. objects can also optionally contain two
     instance attributes, which can be used when generating the plain
     text of a MIME message.

      -- 屬性: preamble

          The format of a MIME document allows for some text between the
          blank line following the headers, and the first multipart
          boundary string.  Normally, this text is never visible in a
          MIME-aware mail reader because it falls outside the standard
          MIME armor.  However, when viewing the raw text of the
          message, or when viewing the message in a non-MIME aware
          reader, this text can become visible.

          The 'preamble' attribute contains this leading extra-armor
          text for MIME documents.  When the *note Parser: 1136.
          discovers some text after the headers but before the first
          boundary string, it assigns this text to the message's
          'preamble' attribute.  When the *note Generator: 1166. is
          writing out the plain text representation of a MIME message,
          and it finds the message has a 'preamble' attribute, it will
          write this text in the area between the headers and the first
          boundary.  See *note email.parser: 45. and *note
          email.generator: 37. for details.

          Note that if the message object has no preamble, the
          'preamble' attribute will be ‘None’.

      -- 屬性: epilogue

          The 'epilogue' attribute acts the same way as the 'preamble'
          attribute, except that it contains text that appears between
          the last boundary and the end of the message.

          You do not need to set the epilogue to the empty string in
          order for the *note Generator: 1166. to print a newline at the
          end of the file.

      -- 屬性: defects

          The 'defects' attribute contains a list of all the problems
          found when parsing this message.  See *note email.errors: 36.
          for a detailed description of the possible parsing defects.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc5322.html

   (2) https://datatracker.ietf.org/doc/html/rfc2822.html

   (3) https://datatracker.ietf.org/doc/html/rfc2231.html

   (4) https://datatracker.ietf.org/doc/html/rfc2231.html

   (5) https://datatracker.ietf.org/doc/html/rfc2045.html

   (6) https://datatracker.ietf.org/doc/html/rfc2045.html

   (7) https://datatracker.ietf.org/doc/html/rfc2045.html

   (8) https://datatracker.ietf.org/doc/html/rfc2231.html

   (9) https://datatracker.ietf.org/doc/html/rfc2231.html

   (10) https://datatracker.ietf.org/doc/html/rfc2045.html

   (11) https://datatracker.ietf.org/doc/html/rfc2231.html

   (12) https://datatracker.ietf.org/doc/html/rfc2183.html


File: python.info,  Node: email mime：從頭開始建立電子郵件和 MIME 物件,  Next: email header：國際化標頭,  Prev: email message Message Representing an email message using the compat32 API,  Up: email --- 郵件和 MIME 處理套件

5.19.1.14 ‘email.mime’：從頭開始建立電子郵件和 MIME 物件
........................................................

'原始碼：'Lib/email/mime/(1)

__________________________________________________________________

This module is part of the legacy (‘Compat32’) email API. Its
functionality is partially replaced by the *note contentmanager: 34. in
the new API, but in certain applications these classes may still be
useful, even in non-legacy code.

Ordinarily, you get a message object structure by passing a file or some
text to a parser, which parses the text and returns the root message
object.  However you can also build a complete message structure from
scratch, or even individual *note Message: 261. objects by hand.  In
fact, you can also take an existing structure and add new *note Message:
261. objects, move them around, etc.  This makes a very convenient
interface for slicing-and-dicing MIME messages.

You can create a new object structure by creating *note Message: 261.
instances, adding attachments and all the appropriate headers manually.
For MIME messages though, the *note email: 32. package provides some
convenient subclasses to make things easier.

Here are the classes:

 -- 類別: email.mime.base.MIMEBase (_maintype, _subtype, *,
          policy=compat32, **_params)

     模組：*note email.mime.base: 3f.

     This is the base class for all the MIME-specific subclasses of
     *note Message: 261.  Ordinarily you won't create instances
     specifically of *note MIMEBase: 3464, although you could.  *note
     MIMEBase: 3464. is provided primarily as a convenient base class
     for more specific MIME-aware subclasses.

     '_maintype' is the ‘Content-Type’ major type (e.g.  ‘text’ or
     ‘image’), and '_subtype' is the ‘Content-Type’ minor type (e.g.
     ‘plain’ or ‘gif’).  '_params' is a parameter key/value dictionary
     and is passed directly to *note Message.add_header: 344d.

     If 'policy' is specified, (defaults to the *note compat32: 104e.
     policy) it will be passed to *note Message: 261.

     The *note MIMEBase: 3464. class always adds a ‘Content-Type’ header
     (based on '_maintype', '_subtype', and '_params'), and a
     ‘MIME-Version’ header (always set to ‘1.0’).

     在 3.6 版的變更: 新增僅限關鍵字參數 'policy'。

 -- 類別: email.mime.nonmultipart.MIMENonMultipart

     模組：*note email.mime.nonmultipart: 43.

     A subclass of *note MIMEBase: 3464, this is an intermediate base
     class for MIME messages that are not ‘multipart’.  The primary
     purpose of this class is to prevent the use of the *note attach():
     33c0. method, which only makes sense for ‘multipart’ messages.  If
     *note attach(): 33c0. is called, a *note MultipartConversionError:
     3404. exception is raised.

 -- 類別: email.mime.multipart.MIMEMultipart (_subtype='mixed',
          boundary=None, _subparts=None, *, policy=compat32, **_params)

     模組：*note email.mime.multipart: 42.

     A subclass of *note MIMEBase: 3464, this is an intermediate base
     class for MIME messages that are ‘multipart’.  Optional '_subtype'
     defaults to ‘mixed’, but can be used to specify the subtype of the
     message.  A ‘Content-Type’ header of ‘multipart/_subtype’ will be
     added to the message object.  A ‘MIME-Version’ header will also be
     added.

     Optional 'boundary' is the multipart boundary string.  When ‘None’
     (the default), the boundary is calculated when needed (for example,
     when the message is serialized).

     '_subparts' is a sequence of initial subparts for the payload.  It
     must be possible to convert this sequence to a list.  You can
     always attach new subparts to the message by using the *note
     Message.attach: 33c0. method.

     Optional 'policy' argument defaults to *note compat32: 104e.

     Additional parameters for the ‘Content-Type’ header are taken from
     the keyword arguments, or passed into the '_params' argument, which
     is a keyword dictionary.

     在 3.6 版的變更: 新增僅限關鍵字參數 'policy'。

 -- 類別: email.mime.application.MIMEApplication (_data,
          _subtype='octet-stream',
          _encoder=email.encoders.encode_base64, *, policy=compat32,
          **_params)

     模組：*note email.mime.application: 3d.

     A subclass of *note MIMENonMultipart: 3405, the *note
     MIMEApplication: 3466. class is used to represent MIME message
     objects of major type ‘application’.  '_data' contains the bytes
     for the raw application data.  Optional '_subtype' specifies the
     MIME subtype and defaults to ‘octet-stream’.

     Optional '_encoder' is a callable (i.e.  function) which will
     perform the actual encoding of the data for transport.  This
     callable takes one argument, which is the *note MIMEApplication:
     3466. instance.  It should use *note get_payload(): 1165. and *note
     set_payload(): 3441. to change the payload to encoded form.  It
     should also add any ‘Content-Transfer-Encoding’ or other headers to
     the message object as necessary.  The default encoding is base64.
     See the *note email.encoders: 35. module for a list of the built-in
     encoders.

     Optional 'policy' argument defaults to *note compat32: 104e.

     '_params' are passed straight through to the base class
     constructor.

     在 3.6 版的變更: 新增僅限關鍵字參數 'policy'。

 -- 類別: email.mime.audio.MIMEAudio (_audiodata, _subtype=None,
          _encoder=email.encoders.encode_base64, *, policy=compat32,
          **_params)

     模組：*note email.mime.audio: 3e.

     A subclass of *note MIMENonMultipart: 3405, the *note MIMEAudio:
     3467. class is used to create MIME message objects of major type
     ‘audio’.  '_audiodata' contains the bytes for the raw audio data.
     If this data can be decoded as au, wav, aiff, or aifc, then the
     subtype will be automatically included in the ‘Content-Type’
     header.  Otherwise you can explicitly specify the audio subtype via
     the '_subtype' argument.  If the minor type could not be guessed
     and '_subtype' was not given, then *note TypeError: 4dd. is raised.

     Optional '_encoder' is a callable (i.e.  function) which will
     perform the actual encoding of the audio data for transport.  This
     callable takes one argument, which is the *note MIMEAudio: 3467.
     instance.  It should use *note get_payload(): 1165. and *note
     set_payload(): 3441. to change the payload to encoded form.  It
     should also add any ‘Content-Transfer-Encoding’ or other headers to
     the message object as necessary.  The default encoding is base64.
     See the *note email.encoders: 35. module for a list of the built-in
     encoders.

     Optional 'policy' argument defaults to *note compat32: 104e.

     '_params' are passed straight through to the base class
     constructor.

     在 3.6 版的變更: 新增僅限關鍵字參數 'policy'。

 -- 類別: email.mime.image.MIMEImage (_imagedata, _subtype=None,
          _encoder=email.encoders.encode_base64, *, policy=compat32,
          **_params)

     模組：*note email.mime.image: 40.

     A subclass of *note MIMENonMultipart: 3405, the *note MIMEImage:
     3406. class is used to create MIME message objects of major type
     ‘image’.  '_imagedata' contains the bytes for the raw image data.
     If this data type can be detected (jpeg, png, gif, tiff, rgb, pbm,
     pgm, ppm, rast, xbm, bmp, webp, and exr attempted), then the
     subtype will be automatically included in the ‘Content-Type’
     header.  Otherwise you can explicitly specify the image subtype via
     the '_subtype' argument.  If the minor type could not be guessed
     and '_subtype' was not given, then *note TypeError: 4dd. is raised.

     Optional '_encoder' is a callable (i.e.  function) which will
     perform the actual encoding of the image data for transport.  This
     callable takes one argument, which is the *note MIMEImage: 3406.
     instance.  It should use *note get_payload(): 1165. and *note
     set_payload(): 3441. to change the payload to encoded form.  It
     should also add any ‘Content-Transfer-Encoding’ or other headers to
     the message object as necessary.  The default encoding is base64.
     See the *note email.encoders: 35. module for a list of the built-in
     encoders.

     Optional 'policy' argument defaults to *note compat32: 104e.

     '_params' are passed straight through to the *note MIMEBase: 3464.
     constructor.

     在 3.6 版的變更: 新增僅限關鍵字參數 'policy'。

 -- 類別: email.mime.message.MIMEMessage (_msg, _subtype='rfc822', *,
          policy=compat32)

     模組：*note email.mime.message: 41.

     A subclass of *note MIMENonMultipart: 3405, the *note MIMEMessage:
     3468. class is used to create MIME objects of main type ‘message’.
     '_msg' is used as the payload, and must be an instance of class
     *note Message: 261. (or a subclass thereof), otherwise a *note
     TypeError: 4dd. is raised.

     Optional '_subtype' sets the subtype of the message; it defaults to
     ‘rfc822’.

     Optional 'policy' argument defaults to *note compat32: 104e.

     在 3.6 版的變更: 新增僅限關鍵字參數 'policy'。

 -- 類別: email.mime.text.MIMEText (_text, _subtype='plain',
          _charset=None, *, policy=compat32)

     模組：*note email.mime.text: 44.

     A subclass of *note MIMENonMultipart: 3405, the *note MIMEText:
     d9f. class is used to create MIME objects of major type ‘text’.
     '_text' is the string for the payload.  '_subtype' is the minor
     type and defaults to ‘plain’.  '_charset' is the character set of
     the text and is passed as an argument to the *note
     MIMENonMultipart: 3405. constructor; it defaults to ‘us-ascii’ if
     the string contains only ‘ascii’ code points, and ‘utf-8’
     otherwise.  The '_charset' parameter accepts either a string or a
     *note Charset: da0. instance.

     Unless the '_charset' argument is explicitly set to ‘None’, the
     MIMEText object created will have both a ‘Content-Type’ header with
     a ‘charset’ parameter, and a ‘Content-Transfer-Encoding’ header.
     This means that a subsequent ‘set_payload’ call will not result in
     an encoded payload, even if a charset is passed in the
     ‘set_payload’ command.  You can "reset" this behavior by deleting
     the ‘Content-Transfer-Encoding’ header, after which a ‘set_payload’
     call will automatically encode the new payload (and add a new
     ‘Content-Transfer-Encoding’ header).

     Optional 'policy' argument defaults to *note compat32: 104e.

     在 3.5 版的變更: '_charset' also accepts *note Charset: da0.
     instances.

     在 3.6 版的變更: 新增僅限關鍵字參數 'policy'。

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/email/mime/


File: python.info,  Node: email header：國際化標頭,  Next: email charset：表示字元集合,  Prev: email mime：從頭開始建立電子郵件和 MIME 物件,  Up: email --- 郵件和 MIME 處理套件

5.19.1.15 ‘email.header’：國際化標頭
....................................

'原始碼：'Lib/email/header.py(1)

__________________________________________________________________

This module is part of the legacy (‘Compat32’) email API. In the current
API encoding and decoding of headers is handled transparently by the
dictionary-like API of the *note EmailMessage: 260. class.  In addition
to uses in legacy code, this module can be useful in applications that
need to completely control the character sets used when encoding
headers.

The remaining text in this section is the original documentation of the
module.

RFC 2822(2) is the base standard that describes the format of email
messages.  It derives from the older RFC 822(3) standard which came into
widespread use at a time when most email was composed of ASCII
characters only.  RFC 2822(4) is a specification written assuming email
contains only 7-bit ASCII characters.

Of course, as email has been deployed worldwide, it has become
internationalized, such that language specific character sets can now be
used in email messages.  The base standard still requires email messages
to be transferred using only 7-bit ASCII characters, so a slew of RFCs
have been written describing how to encode email containing non-ASCII
characters into RFC 2822(5)-compliant format.  These RFCs include RFC
2045(6), RFC 2046(7), RFC 2047(8), and RFC 2231(9).  The *note email:
32. package supports these standards in its *note email.header: 38. and
*note email.charset: 33. modules.

If you want to include non-ASCII characters in your email headers, say
in the ‘Subject’ or ‘To’ fields, you should use the *note Header: 17ac.
class and assign the field in the *note Message: 261. object to an
instance of *note Header: 17ac. instead of using a string for the header
value.  Import the *note Header: 17ac. class from the *note
email.header: 38. module.  For example:

     >>> from email.message import Message
     >>> from email.header import Header
     >>> msg = Message()
     >>> h = Header('p\xf6stal', 'iso-8859-1')
     >>> msg['Subject'] = h
     >>> msg.as_string()
     'Subject: =?iso-8859-1?q?p=F6stal?=\n\n'

Notice here how we wanted the ‘Subject’ field to contain a non-ASCII
character?  We did this by creating a *note Header: 17ac. instance and
passing in the character set that the byte string was encoded in.  When
the subsequent *note Message: 261. instance was flattened, the ‘Subject’
field was properly RFC 2047(10) encoded.  MIME-aware mail readers would
show this header using the embedded ISO-8859-1 character.

Here is the *note Header: 17ac. class description:

 -- 類別: email.header.Header (s=None, charset=None, maxlinelen=None,
          header_name=None, continuation_ws=' ', errors='strict')

     Create a MIME-compliant header that can contain strings in
     different character sets.

     Optional 's' is the initial header value.  If ‘None’ (the default),
     the initial header value is not set.  You can later append to the
     header with *note append(): 346b. method calls.  's' may be an
     instance of *note bytes: 1a5. or *note str: 3f2, but see the *note
     append(): 346b. documentation for semantics.

     Optional 'charset' serves two purposes: it has the same meaning as
     the 'charset' argument to the *note append(): 346b. method.  It
     also sets the default character set for all subsequent *note
     append(): 346b. calls that omit the 'charset' argument.  If
     'charset' is not provided in the constructor (the default), the
     ‘us-ascii’ character set is used both as 's"s initial charset and
     as the default for subsequent *note append(): 346b. calls.

     The maximum line length can be specified explicitly via
     'maxlinelen'.  For splitting the first line to a shorter value (to
     account for the field header which isn't included in 's', e.g.
     ‘Subject’) pass in the name of the field in 'header_name'.  The
     default 'maxlinelen' is 78, and the default value for 'header_name'
     is ‘None’, meaning it is not taken into account for the first line
     of a long, split header.

     Optional 'continuation_ws' must be RFC 2822(11)-compliant folding
     whitespace, and is usually either a space or a hard tab character.
     This character will be prepended to continuation lines.
     'continuation_ws' defaults to a single space character.

     Optional 'errors' is passed straight through to the *note append():
     346b. method.

      -- 方法: append (s, charset=None, errors='strict')

          Append the string 's' to the MIME header.

          Optional 'charset', if given, should be a *note Charset: da0.
          instance (see *note email.charset: 33.) or the name of a
          character set, which will be converted to a *note Charset:
          da0. instance.  A value of ‘None’ (the default) means that the
          'charset' given in the constructor is used.

          's' may be an instance of *note bytes: 1a5. or *note str: 3f2.
          If it is an instance of *note bytes: 1a5, then 'charset' is
          the encoding of that byte string, and a *note UnicodeError:
          123a. will be raised if the string cannot be decoded with that
          character set.

          If 's' is an instance of *note str: 3f2, then 'charset' is a
          hint specifying the character set of the characters in the
          string.

          In either case, when producing an RFC 2822(12)-compliant
          header using RFC 2047(13) rules, the string will be encoded
          using the output codec of the charset.  If the string cannot
          be encoded using the output codec, a UnicodeError will be
          raised.

          Optional 'errors' is passed as the errors argument to the
          decode call if 's' is a byte string.

      -- 方法: encode (splitchars=';, \t', maxlinelen=None,
               linesep='\n')

          Encode a message header into an RFC-compliant format, possibly
          wrapping long lines and encapsulating non-ASCII parts in
          base64 or quoted-printable encodings.

          Optional 'splitchars' is a string containing characters which
          should be given extra weight by the splitting algorithm during
          normal header wrapping.  This is in very rough support of RFC
          2822(14)'s 'higher level syntactic breaks': split points
          preceded by a splitchar are preferred during line splitting,
          with the characters preferred in the order in which they
          appear in the string.  Space and tab may be included in the
          string to indicate whether preference should be given to one
          over the other as a split point when other split chars do not
          appear in the line being split.  Splitchars does not affect
          RFC 2047(15) encoded lines.

          'maxlinelen', if given, overrides the instance's value for the
          maximum line length.

          'linesep' specifies the characters used to separate the lines
          of the folded header.  It defaults to the most useful value
          for Python application code (‘\n’), but ‘\r\n’ can be
          specified in order to produce headers with RFC-compliant line
          separators.

          在 3.2 版的變更: 新增引數 'linesep'。

     The *note Header: 17ac. class also provides a number of methods to
     support standard operators and built-in functions.

      -- 方法: __str__ ()

          Returns an approximation of the *note Header: 17ac. as a
          string, using an unlimited line length.  All pieces are
          converted to unicode using the specified encoding and joined
          together appropriately.  Any pieces with a charset of
          ‘'unknown-8bit'’ are decoded as ASCII using the ‘'replace'’
          error handler.

          在 3.2 版的變更: Added handling for the ‘'unknown-8bit'’
          charset.

      -- 方法: __eq__ (other)

          This method allows you to compare two *note Header: 17ac.
          instances for equality.

      -- 方法: __ne__ (other)

          This method allows you to compare two *note Header: 17ac.
          instances for inequality.

The *note email.header: 38. module also provides the following
convenient functions.

 -- 函式: email.header.decode_header (header)

     Decode a message header value without converting the character set.
     The header value is in 'header'.

     This function returns a list of ‘(decoded_string, charset)’ pairs
     containing each of the decoded parts of the header.  'charset' is
     ‘None’ for non-encoded parts of the header, otherwise a lower case
     string containing the name of the character set specified in the
     encoded string.

     以下是個範例：

          >>> from email.header import decode_header
          >>> decode_header('=?iso-8859-1?q?p=F6stal?=')
          [(b'p\xf6stal', 'iso-8859-1')]

 -- 函式: email.header.make_header (decoded_seq, maxlinelen=None,
          header_name=None, continuation_ws=' ')

     Create a *note Header: 17ac. instance from a sequence of pairs as
     returned by *note decode_header(): 1052.

     *note decode_header(): 1052. takes a header value string and
     returns a sequence of pairs of the format ‘(decoded_string,
     charset)’ where 'charset' is the name of the character set.

     This function takes one of those sequence of pairs and returns a
     *note Header: 17ac. instance.  Optional 'maxlinelen',
     'header_name', and 'continuation_ws' are as in the *note Header:
     17ac. constructor.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/email/header.py

   (2) https://datatracker.ietf.org/doc/html/rfc2822.html

   (3) https://datatracker.ietf.org/doc/html/rfc822.html

   (4) https://datatracker.ietf.org/doc/html/rfc2822.html

   (5) https://datatracker.ietf.org/doc/html/rfc2822.html

   (6) https://datatracker.ietf.org/doc/html/rfc2045.html

   (7) https://datatracker.ietf.org/doc/html/rfc2046.html

   (8) https://datatracker.ietf.org/doc/html/rfc2047.html

   (9) https://datatracker.ietf.org/doc/html/rfc2231.html

   (10) https://datatracker.ietf.org/doc/html/rfc2047.html

   (11) https://datatracker.ietf.org/doc/html/rfc2822.html

   (12) https://datatracker.ietf.org/doc/html/rfc2822.html

   (13) https://datatracker.ietf.org/doc/html/rfc2047.html

   (14) https://datatracker.ietf.org/doc/html/rfc2822.html

   (15) https://datatracker.ietf.org/doc/html/rfc2047.html


File: python.info,  Node: email charset：表示字元集合,  Next: email encoders：編碼器,  Prev: email header：國際化標頭,  Up: email --- 郵件和 MIME 處理套件

5.19.1.16 ‘email.charset’：表示字元集合
.......................................

'原始碼：'Lib/email/charset.py(1)

__________________________________________________________________

此模組是舊版 (‘Compat32’) email API的其中一部份，在新版的 API 只有使用別
名表。

此章節的其餘文字是原始模組的說明文件

此模組提供一個 class（類別） *note Charset: da0. 來表示電子郵件中的字元
集合和字元集合轉換，以及字元集合登錄檔 (registry) 和其他許多便捷的方法以
運用此登錄檔。在 *note email: 32. 套件中有許多其他模組使用 *note
Charset: da0. 的實例。

從 *note email.charset: 33. 模組中 import 此類別

 -- 類別: email.charset.Charset (input_charset=DEFAULT_CHARSET)

     Map character sets to their email properties.

     This class provides information about the requirements imposed on
     email for a specific character set.  It also provides convenience
     routines for converting between character sets, given the
     availability of the applicable codecs.  Given a character set, it
     will do its best to provide information on how to use that
     character set in an email message in an RFC-compliant way.

     Certain character sets must be encoded with quoted-printable or
     base64 when used in email headers or bodies.  Certain character
     sets must be converted outright, and are not allowed in email.

     Optional 'input_charset' is as described below; it is always
     coerced to lower case.  After being alias normalized it is also
     used as a lookup into the registry of character sets to find out
     the header encoding, body encoding, and output conversion codec to
     be used for the character set.  For example, if 'input_charset' is
     ‘iso-8859-1’, then headers and bodies will be encoded using
     quoted-printable and no output conversion codec is necessary.  If
     'input_charset' is ‘euc-jp’, then headers will be encoded with
     base64, bodies will not be encoded, but output text will be
     converted from the ‘euc-jp’ character set to the ‘iso-2022-jp’
     character set.

     *note Charset: da0. instances have the following data attributes:

      -- 屬性: input_charset

          The initial character set specified.  Common aliases are
          converted to their 'official' email names (e.g.  ‘latin_1’ is
          converted to ‘iso-8859-1’).  Defaults to 7-bit ‘us-ascii’.

      -- 屬性: header_encoding

          If the character set must be encoded before it can be used in
          an email header, this attribute will be set to ‘charset.QP’
          (for quoted-printable), ‘charset.BASE64’ (for base64
          encoding), or ‘charset.SHORTEST’ for the shortest of QP or
          BASE64 encoding.  Otherwise, it will be ‘None’.

      -- 屬性: body_encoding

          Same as 'header_encoding', but describes the encoding for the
          mail message's body, which indeed may be different than the
          header encoding.  ‘charset.SHORTEST’ is not allowed for
          'body_encoding'.

      -- 屬性: output_charset

          Some character sets must be converted before they can be used
          in email headers or bodies.  If the 'input_charset' is one of
          them, this attribute will contain the name of the character
          set output will be converted to.  Otherwise, it will be
          ‘None’.

      -- 屬性: input_codec

          The name of the Python codec used to convert the
          'input_charset' to Unicode.  If no conversion codec is
          necessary, this attribute will be ‘None’.

      -- 屬性: output_codec

          The name of the Python codec used to convert Unicode to the
          'output_charset'.  If no conversion codec is necessary, this
          attribute will have the same value as the 'input_codec'.

     *note Charset: da0. instances also have the following methods:

      -- 方法: get_body_encoding ()

          Return the content transfer encoding used for body encoding.

          This is either the string ‘quoted-printable’ or ‘base64’
          depending on the encoding used, or it is a function, in which
          case you should call the function with a single argument, the
          Message object being encoded.  The function should then set
          the ‘Content-Transfer-Encoding’ header itself to whatever is
          appropriate.

          Returns the string ‘quoted-printable’ if 'body_encoding' is
          ‘QP’, returns the string ‘base64’ if 'body_encoding' is
          ‘BASE64’, and returns the string ‘7bit’ otherwise.

      -- 方法: get_output_charset ()

          Return the output character set.

          This is the 'output_charset' attribute if that is not ‘None’,
          otherwise it is 'input_charset'.

      -- 方法: header_encode (string)

          Header-encode the string 'string'.

          The type of encoding (base64 or quoted-printable) will be
          based on the 'header_encoding' attribute.

      -- 方法: header_encode_lines (string, maxlengths)

          Header-encode a 'string' by converting it first to bytes.

          This is similar to *note header_encode(): 347a. except that
          the string is fit into maximum line lengths as given by the
          argument 'maxlengths', which must be an iterator: each element
          returned from this iterator will provide the next maximum line
          length.

      -- 方法: body_encode (string)

          Body-encode the string 'string'.

          The type of encoding (base64 or quoted-printable) will be
          based on the 'body_encoding' attribute.

     The *note Charset: da0. class also provides a number of methods to
     support standard operations and built-in functions.

      -- 方法: __str__ ()

          Returns 'input_charset' as a string coerced to lower case.
          ‘__repr__()’ is an alias for ‘__str__()’.

      -- 方法: __eq__ (other)

          This method allows you to compare two *note Charset: da0.
          instances for equality.

      -- 方法: __ne__ (other)

          This method allows you to compare two *note Charset: da0.
          instances for inequality.

The *note email.charset: 33. module also provides the following
functions for adding new entries to the global character set, alias, and
codec registries:

 -- 函式: email.charset.add_charset (charset, header_enc=None,
          body_enc=None, output_charset=None)

     Add character properties to the global registry.

     'charset' is the input character set, and must be the canonical
     name of a character set.

     Optional 'header_enc' and 'body_enc' is either ‘charset.QP’ for
     quoted-printable, ‘charset.BASE64’ for base64 encoding,
     ‘charset.SHORTEST’ for the shortest of quoted-printable or base64
     encoding, or ‘None’ for no encoding.  ‘SHORTEST’ is only valid for
     'header_enc'.  The default is ‘None’ for no encoding.

     Optional 'output_charset' is the character set that the output
     should be in.  Conversions will proceed from input charset, to
     Unicode, to the output charset when the method ‘Charset.convert()’
     is called.  The default is to output in the same character set as
     the input.

     Both 'input_charset' and 'output_charset' must have Unicode codec
     entries in the module's character set-to-codec mapping; use *note
     add_codec(): 3481. to add codecs the module does not know about.
     See the *note codecs: 14. module's documentation for more
     information.

     The global character set registry is kept in the module global
     dictionary ‘CHARSETS’.

 -- 函式: email.charset.add_alias (alias, canonical)

     Add a character set alias.  'alias' is the alias name, e.g.
     ‘latin-1’.  'canonical' is the character set's canonical name, e.g.
     ‘iso-8859-1’.

     The global charset alias registry is kept in the module global
     dictionary ‘ALIASES’.

 -- 函式: email.charset.add_codec (charset, codecname)

     Add a codec that map characters in the given character set to and
     from Unicode.

     'charset' is the canonical name of a character set.  'codecname' is
     the name of a Python codec, as appropriate for the second argument
     to the *note str: 3f2.'s *note encode(): 87a. method.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/email/charset.py


File: python.info,  Node: email encoders：編碼器,  Next: email utils：雜項工具,  Prev: email charset：表示字元集合,  Up: email --- 郵件和 MIME 處理套件

5.19.1.17 ‘email.encoders’：編碼器
..................................

'原始碼：'Lib/email/encoders.py(1)

__________________________________________________________________

此模組是舊版 (‘Compat32’) 電子郵件 API 的一部分。在新 API 中，此功能由
*note set_content(): 17ab. 方法的 'cte' 參數提供。

此模組在 Python 3 中已棄用。不應明確呼叫此處提供的函式，因為 *note
MIMEText: d9f. 類別使用在該類別的實例化過程中傳遞的 '_subtype' 和
'_charset' 值來設定內容類型 (content type) 和 CTE 標頭。

本節中的其餘文字是該模組的原始文件。

從零開始建立 *note Message: 261. 物件時，你通常需要對負載 (payload) 進行
編碼，以便透過相容的郵件伺服器進行傳輸。對於包含二進位資料的 ‘image/*’ 和
‘text/*’ 類型的訊息尤其如此。

*note email: 32. 套件在其 *note encoders: 35. 模組中提供了一些方便的編碼
器。這些編碼器實際上由 *note MIMEAudio: 3467. 和 *note MIMEImage: 3406.
類別建構函式使用來提供預設編碼。所有編碼器函式都只接受一個引數，也就是要
編碼的訊息物件。他們通常會提取負載、對其進行編碼，然後將負載重設為新編碼
的值。他們也應適當地設定 ‘Content-Transfer-Encoding’ 標頭。

請注意，這些函式對於多部分訊息 (multipart message) 沒有意義。它們必須應
用於各個子部分，如果傳遞類型為多部分訊息，則會引發 *note TypeError:
4dd.。

以下是提供的編碼函式：

 -- 函式: email.encoders.encode_quopri (msg)

     將負載編碼為可列印字元 (quoted-printable) 形式，並將
     ‘Content-Transfer-Encoding’ 標頭設定為 ‘quoted-printable’ (2)。當大
     部分負載是正常的可列印資料，但包含一些不可列印的字元時，這是一種很
     好的編碼。

 -- 函式: email.encoders.encode_base64 (msg)

     將負載編碼為 base64 形式，並將 ‘Content-Transfer-Encoding’ 標頭設定
     為 ‘base64’。當大部分負載是不可列印資料時，這是一種很好的編碼，因為
     它是比可列印字元更緊湊的形式。Base64 編碼的缺點是它使文字無法讓人類
     可讀。

 -- 函式: email.encoders.encode_7or8bit (msg)

     這實際上並沒有修改訊息的負載，但它確實根據負載資料將
     ‘Content-Transfer-Encoding’ 標頭設定為適當的 ‘7bit’ 或 ‘8bit’。

 -- 函式: email.encoders.encode_noop (msg)

     這沒有任何作用；它甚至沒有設定 ‘Content-Transfer-Encoding’ 標頭。

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/email/encoders.py

   (2) 請注意，使用 *note encode_quopri(): 3485. 進行編碼也會對資料中的
所有定位字元 (tab) 和空格字元進行編碼。


File: python.info,  Node: email utils：雜項工具,  Next: email iterators：疊代器,  Prev: email encoders：編碼器,  Up: email --- 郵件和 MIME 處理套件

5.19.1.18 ‘email.utils’：雜項工具
.................................

'原始碼：'Lib/email/utils.py(1)

__________________________________________________________________

There are a couple of useful utilities provided in the *note
email.utils: 47. module:

 -- 函式: email.utils.localtime (dt=None)

     Return local time as an aware datetime object.  If called without
     arguments, return current time.  Otherwise 'dt' argument should be
     a *note datetime: 1b0. instance, and it is converted to the local
     time zone according to the system time zone database.  If 'dt' is
     naive (that is, ‘dt.tzinfo’ is ‘None’), it is assumed to be in
     local time.  The 'isdst' parameter is ignored.

     在 3.3 版被加入.

     Deprecated since version 3.12, will be removed in version 3.14: The
     'isdst' parameter.

 -- 函式: email.utils.make_msgid (idstring=None, domain=None)

     Returns a string suitable for an RFC 2822(2)-compliant ‘Message-ID’
     header.  Optional 'idstring' if given, is a string used to
     strengthen the uniqueness of the message id.  Optional 'domain' if
     given provides the portion of the msgid after the '@'.  The default
     is the local hostname.  It is not normally necessary to override
     this default, but may be useful certain cases, such as a
     constructing distributed system that uses a consistent domain name
     across multiple hosts.

     在 3.2 版的變更: 新增 'domain' 關鍵字。

The remaining functions are part of the legacy (‘Compat32’) email API.
There is no need to directly use these with the new API, since the
parsing and formatting they provide is done automatically by the header
parsing machinery of the new API.

 -- 函式: email.utils.quote (str)

     Return a new string with backslashes in 'str' replaced by two
     backslashes, and double quotes replaced by backslash-double quote.

 -- 函式: email.utils.unquote (str)

     Return a new string which is an 'unquoted' version of 'str'.  If
     'str' ends and begins with double quotes, they are stripped off.
     Likewise if 'str' ends and begins with angle brackets, they are
     stripped off.

 -- 函式: email.utils.parseaddr (address, *, strict=True)

     Parse address - which should be the value of some
     address-containing field such as ‘To’ or ‘Cc’ - into its
     constituent 'realname' and 'email address' parts.  Returns a tuple
     of that information, unless the parse fails, in which case a
     2-tuple of ‘('', '')’ is returned.

     If 'strict' is true, use a strict parser which rejects malformed
     inputs.

     在 3.13 版的變更: Add 'strict' optional parameter and reject
     malformed inputs by default.

 -- 函式: email.utils.formataddr (pair, charset='utf-8')

     The inverse of *note parseaddr(): 1c5, this takes a 2-tuple of the
     form ‘(realname, email_address)’ and returns the string value
     suitable for a ‘To’ or ‘Cc’ header.  If the first element of 'pair'
     is false, then the second element is returned unmodified.

     Optional 'charset' is the character set that will be used in the
     RFC 2047(3) encoding of the ‘realname’ if the ‘realname’ contains
     non-ASCII characters.  Can be an instance of *note str: 3f2. or a
     *note Charset: da0.  Defaults to ‘utf-8’.

     在 3.3 版的變更: 新增 'charset' 選項。

 -- 函式: email.utils.getaddresses (fieldvalues, *, strict=True)

     This method returns a list of 2-tuples of the form returned by
     ‘parseaddr()’.  'fieldvalues' is a sequence of header field values
     as might be returned by *note Message.get_all: 3447.

     If 'strict' is true, use a strict parser which rejects malformed
     inputs.

     Here's a simple example that gets all the recipients of a message:

          from email.utils import getaddresses

          tos = msg.get_all('to', [])
          ccs = msg.get_all('cc', [])
          resent_tos = msg.get_all('resent-to', [])
          resent_ccs = msg.get_all('resent-cc', [])
          all_recipients = getaddresses(tos + ccs + resent_tos + resent_ccs)

     在 3.13 版的變更: Add 'strict' optional parameter and reject
     malformed inputs by default.

 -- 函式: email.utils.parsedate (date)

     Attempts to parse a date according to the rules in RFC 2822(4).
     however, some mailers don't follow that format as specified, so
     *note parsedate(): 348d. tries to guess correctly in such cases.
     'date' is a string containing an RFC 2822(5) date, such as ‘"Mon,
     20 Nov 1995 19:12:08 -0500"’.  If it succeeds in parsing the date,
     *note parsedate(): 348d. returns a 9-tuple that can be passed
     directly to *note time.mktime(): 1180.; otherwise ‘None’ will be
     returned.  Note that indexes 6, 7, and 8 of the result tuple are
     not usable.

 -- 函式: email.utils.parsedate_tz (date)

     Performs the same function as *note parsedate(): 348d, but returns
     either ‘None’ or a 10-tuple; the first 9 elements make up a tuple
     that can be passed directly to *note time.mktime(): 1180, and the
     tenth is the offset of the date's timezone from UTC (which is the
     official term for Greenwich Mean Time) (6).  If the input string
     has no timezone, the last element of the tuple returned is ‘0’,
     which represents UTC. Note that indexes 6, 7, and 8 of the result
     tuple are not usable.

 -- 函式: email.utils.parsedate_to_datetime (date)

     The inverse of *note format_datetime(): 1057.  Performs the same
     function as *note parsedate(): 348d, but on success returns a *note
     datetime: 1b0.; otherwise ‘ValueError’ is raised if 'date' contains
     an invalid value such as an hour greater than 23 or a timezone
     offset not between -24 and 24 hours.  If the input date has a
     timezone of ‘-0000’, the ‘datetime’ will be a naive ‘datetime’, and
     if the date is conforming to the RFCs it will represent a time in
     UTC but with no indication of the actual source timezone of the
     message the date comes from.  If the input date has any other valid
     timezone offset, the ‘datetime’ will be an aware ‘datetime’ with
     the corresponding a *note timezone: 1059. *note tzinfo: 582.

     在 3.3 版被加入.

 -- 函式: email.utils.mktime_tz (tuple)

     Turn a 10-tuple as returned by *note parsedate_tz(): 1781. into a
     UTC timestamp (seconds since the Epoch).  If the timezone item in
     the tuple is ‘None’, assume local time.

 -- 函式: email.utils.formatdate (timeval=None, localtime=False,
          usegmt=False)

     Returns a date string as per RFC 2822(7), e.g.:

          Fri, 09 Nov 2001 01:08:47 -0000

     Optional 'timeval' if given is a floating-point time value as
     accepted by *note time.gmtime(): 1158. and *note time.localtime():
     1467, otherwise the current time is used.

     Optional 'localtime' is a flag that when ‘True’, interprets
     'timeval', and returns a date relative to the local timezone
     instead of UTC, properly taking daylight savings time into account.
     The default is ‘False’ meaning UTC is used.

     Optional 'usegmt' is a flag that when ‘True’, outputs a date string
     with the timezone as an ascii string ‘GMT’, rather than a numeric
     ‘-0000’.  This is needed for some protocols (such as HTTP). This
     only applies when 'localtime' is ‘False’.  The default is ‘False’.

 -- 函式: email.utils.format_datetime (dt, usegmt=False)

     Like ‘formatdate’, but the input is a *note datetime: 28. instance.
     If it is a naive datetime, it is assumed to be "UTC with no
     information about the source timezone", and the conventional
     ‘-0000’ is used for the timezone.  If it is an aware ‘datetime’,
     then the numeric timezone offset is used.  If it is an aware
     timezone with offset zero, then 'usegmt' may be set to ‘True’, in
     which case the string ‘GMT’ is used instead of the numeric timezone
     offset.  This provides a way to generate standards conformant HTTP
     date headers.

     在 3.3 版被加入.

 -- 函式: email.utils.decode_rfc2231 (s)

     Decode the string 's' according to RFC 2231(8).

 -- 函式: email.utils.encode_rfc2231 (s, charset=None, language=None)

     Encode the string 's' according to RFC 2231(9).  Optional 'charset'
     and 'language', if given is the character set name and language
     name to use.  If neither is given, 's' is returned as-is.  If
     'charset' is given but 'language' is not, the string is encoded
     using the empty string for 'language'.

 -- 函式: email.utils.collapse_rfc2231_value (value, errors='replace',
          fallback_charset='us-ascii')

     When a header parameter is encoded in RFC 2231(10) format, *note
     Message.get_param: 3455. may return a 3-tuple containing the
     character set, language, and value.  *note
     collapse_rfc2231_value(): 3456. turns this into a unicode string.
     Optional 'errors' is passed to the 'errors' argument of *note str:
     3f2.'s *note encode(): 87a. method; it defaults to ‘'replace'’.
     Optional 'fallback_charset' specifies the character set to use if
     the one in the RFC 2231(11) header is not known by Python; it
     defaults to ‘'us-ascii'’.

     For convenience, if the 'value' passed to *note
     collapse_rfc2231_value(): 3456. is not a tuple, it should be a
     string and it is returned unquoted.

 -- 函式: email.utils.decode_params (params)

     Decode parameters list according to RFC 2231(12).  'params' is a
     sequence of 2-tuples containing elements of the form
     ‘(content-type, string-value)’.

註解
....

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/email/utils.py

   (2) https://datatracker.ietf.org/doc/html/rfc2822.html

   (3) https://datatracker.ietf.org/doc/html/rfc2047.html

   (4) https://datatracker.ietf.org/doc/html/rfc2822.html

   (5) https://datatracker.ietf.org/doc/html/rfc2822.html

   (6) Note that the sign of the timezone offset is the opposite of the
sign of the ‘time.timezone’ variable for the same timezone; the latter
variable follows the POSIX standard while this module follows RFC 2822
(https://datatracker.ietf.org/doc/html/rfc2822.html).

   (7) https://datatracker.ietf.org/doc/html/rfc2822.html

   (8) https://datatracker.ietf.org/doc/html/rfc2231.html

   (9) https://datatracker.ietf.org/doc/html/rfc2231.html

   (10) https://datatracker.ietf.org/doc/html/rfc2231.html

   (11) https://datatracker.ietf.org/doc/html/rfc2231.html

   (12) https://datatracker.ietf.org/doc/html/rfc2231.html


File: python.info,  Node: email iterators：疊代器,  Prev: email utils：雜項工具,  Up: email --- 郵件和 MIME 處理套件

5.19.1.19 ‘email.iterators’：疊代器
...................................

'原始碼：'Lib/email/iterators.py(1)

__________________________________________________________________

Iterating over a message object tree is fairly easy with the *note
Message.walk: 345e. method.  The *note email.iterators: 3a. module
provides some useful higher level iterations over message object trees.

 -- 函式: email.iterators.body_line_iterator (msg, decode=False)

     This iterates over all the payloads in all the subparts of 'msg',
     returning the string payloads line-by-line.  It skips over all the
     subpart headers, and it skips over any subpart with a payload that
     isn't a Python string.  This is somewhat equivalent to reading the
     flat text representation of the message from a file using *note
     readline(): 1bc0, skipping over all the intervening headers.

     Optional 'decode' is passed through to *note Message.get_payload:
     1165.

 -- 函式: email.iterators.typed_subpart_iterator (msg, maintype='text',
          subtype=None)

     This iterates over all the subparts of 'msg', returning only those
     subparts that match the MIME type specified by 'maintype' and
     'subtype'.

     Note that 'subtype' is optional; if omitted, then subpart MIME type
     matching is done only with the main type.  'maintype' is optional
     too; it defaults to ‘text’.

     Thus, by default *note typed_subpart_iterator(): 3495. returns each
     subpart that has a MIME type of ‘text/*’.

The following function has been added as a useful debugging tool.  It
should 'not' be considered part of the supported public interface for
the package.

 -- 函式: email.iterators._structure (msg, fp=None, level=0,
          include_default=False)

     Prints an indented representation of the content types of the
     message object structure.  For example:

          >>> msg = email.message_from_file(somefile)
          >>> _structure(msg)
          multipart/mixed
              text/plain
              text/plain
              multipart/digest
                  message/rfc822
                      text/plain
                  message/rfc822
                      text/plain
                  message/rfc822
                      text/plain
                  message/rfc822
                      text/plain
                  message/rfc822
                      text/plain
              text/plain

     Optional 'fp' is a file-like object to print the output to.  It
     must be suitable for Python's *note print(): f18. function.
     'level' is used internally.  'include_default', if true, prints the
     default type as well.

也參考
......

*note smtplib: b7. 模組

     SMTP (Simple Mail Transport Protocol) client

*note poplib: 9a. 模組

     POP (Post Office Protocol) client

*note imaplib: 6a. 模組

     IMAP (Internet Message Access Protocol) client

*note mailbox: 7f. 模組

     Tools for creating, reading, and managing collections of messages
     on disk using a variety standard formats.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/email/iterators.py


File: python.info,  Node: json --- JSON 編碼器與解碼器,  Next: mailbox --- 以各種格式操作郵件信箱,  Prev: email --- 郵件和 MIME 處理套件,  Up: 網際網路資料處理

5.19.2 ‘json’ -- JSON 編碼器與解碼器
------------------------------------

'原始碼：'Lib/json/__init__.py(1)

__________________________________________________________________

JSON (JavaScript Object Notation)(2) 是一個輕量化的資料交換格式，在 RFC
7159(3)（其廢棄了 RFC 4627(4)）及 ECMA-404(5) 裡面有詳細說明，它啟發自
JavaScript(6) 的物件字面語法 (object literal syntax)（雖然它並不是
JavaScript 的嚴格子集 (7)）。

     警告: 當剖析無法信任來源的 JSON 資料時要小心。一段惡意的 JSON 字串
     可能會導致解碼器耗費大量 CPU 與記憶體資源。建議限制剖析資料的大小。

*note json: 76. 為習慣標準函式庫 *note marshal: 80. 與 *note pickle: 95.
模組的使用者提供熟悉的 API。

對基本 Python 物件階層進行編碼：

     >>> import json
     >>> json.dumps(['foo', {'bar': ('baz', None, 1.0, 2)}])
     '["foo", {"bar": ["baz", null, 1.0, 2]}]'
     >>> print(json.dumps("\"foo\bar"))
     "\"foo\bar"
     >>> print(json.dumps('\u1234'))
     "\u1234"
     >>> print(json.dumps('\\'))
     "\\"
     >>> print(json.dumps({"c": 0, "b": 0, "a": 0}, sort_keys=True))
     {"a": 0, "b": 0, "c": 0}
     >>> from io import StringIO
     >>> io = StringIO()
     >>> json.dump(['streaming API'], io)
     >>> io.getvalue()
     '["streaming API"]'

改用緊湊型編碼方式：

     >>> import json
     >>> json.dumps([1, 2, 3, {'4': 5, '6': 7}], separators=(',', ':'))
     '[1,2,3,{"4":5,"6":7}]'

美化輸出：

     >>> import json
     >>> print(json.dumps({'6': 7, '4': 5}, sort_keys=True, indent=4))
     {
         "4": 5,
         "6": 7
     }

Specializing JSON object encoding:

     >>> import json
     >>> def custom_json(obj):
     ...     if isinstance(obj, complex):
     ...         return {'__complex__': True, 'real': obj.real, 'imag': obj.imag}
     ...     raise TypeError(f'Cannot serialize object of {type(obj)}')
     ...
     >>> json.dumps(1 + 2j, default=custom_json)
     '{"__complex__": true, "real": 1.0, "imag": 2.0}'

JSON 解碼：

     >>> import json
     >>> json.loads('["foo", {"bar":["baz", null, 1.0, 2]}]')
     ['foo', {'bar': ['baz', None, 1.0, 2]}]
     >>> json.loads('"\\"foo\\bar"')
     '"foo\x08ar'
     >>> from io import StringIO
     >>> io = StringIO('["streaming API"]')
     >>> json.load(io)
     ['streaming API']

自訂特殊的 JSON 解碼方式：

     >>> import json
     >>> def as_complex(dct):
     ...     if '__complex__' in dct:
     ...         return complex(dct['real'], dct['imag'])
     ...     return dct
     ...
     >>> json.loads('{"__complex__": true, "real": 1, "imag": 2}',
     ...     object_hook=as_complex)
     (1+2j)
     >>> import decimal
     >>> json.loads('1.1', parse_float=decimal.Decimal)
     Decimal('1.1')

繼承 *note JSONEncoder: ced. 類別並自行擴充額外的編碼方法：

     >>> import json
     >>> class ComplexEncoder(json.JSONEncoder):
     ...     def default(self, obj):
     ...         if isinstance(obj, complex):
     ...             return [obj.real, obj.imag]
     ...         # Let the base class default method raise the TypeError
     ...         return super().default(obj)
     ...
     >>> json.dumps(2 + 1j, cls=ComplexEncoder)
     '[2.0, 1.0]'
     >>> ComplexEncoder().encode(2 + 1j)
     '[2.0, 1.0]'
     >>> list(ComplexEncoder().iterencode(2 + 1j))
     ['[2.0', ', 1.0', ']']

在命令列介面裡使用 *note json.tool: 77. 來驗證 JSON 語法和美化呈現方式：

     $ echo '{"json":"obj"}' | python -m json.tool
     {
         "json": "obj"
     }
     $ echo '{1.2:3.4}' | python -m json.tool
     Expecting property name enclosed in double quotes: line 1 column 2 (char 1)

更詳盡的文件請見 *note 命令列介面: 3499.。

     備註: JSON 語法是 YAML(8) 1.2 語法的一種子集合。所以如果使用預設的
     設定的話（準確來說，使用預設的 'separators' 分隔符設定的話），這個
     模組的輸出也符合 YAML 1.0 和 1.1 的子集合規範。因此你也可以利用這個
     模組來當作 YAML 的序列化工具（serializer）。

     備註: 這個模組的編、解碼器預設會保存輸入與輸出資料的順序關係，除非
     一開始的輸入本身就是無序的。

* Menu:

* 基本用法: 基本用法<2>.
* 編碼器與解碼器::
* 例外: 例外<12>.
* 合規性與互通性（Interoperability）::
* 命令列介面: 命令列介面<3>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/json/__init__.py

   (2) https://json.org

   (3) https://datatracker.ietf.org/doc/html/rfc7159.html

   (4) https://datatracker.ietf.org/doc/html/rfc4627.html

   (5) 
https://www.ecma-international.org/publications-and-standards/standards/ecma-404/

   (6) https://en.wikipedia.org/wiki/JavaScript

   (7) 如 RFC 7159 更正
(https://www.rfc-editor.org/errata_search.php?rfc=7159) 所述，JSON 允許
字串中出現 U+2028（列分隔符）和 U+2029（段落分隔符）字元，而 JavaScript（
截至 ECMAScript 5.1 版）則不允許。

   (8) https://yaml.org/


File: python.info,  Node: 基本用法<2>,  Next: 編碼器與解碼器,  Up: json --- JSON 編碼器與解碼器

5.19.2.1 基本用法
.................

 -- 函式: json.dump (obj, fp, *, skipkeys=False, ensure_ascii=True,
          check_circular=True, allow_nan=True, cls=None, indent=None,
          separators=None, default=None, sort_keys=False, **kw)

     參考這個*note 轉換表: 349b.將 'obj' 序列化為符合 JSON 格式的串流，
     並寫入到 'fp' （一個支援 ‘.write()’ 方法的 *note file-like object:
     246a.）

     如果 'skipkeys' 被設為 true（預設值：‘False’），那麼非基本型別（
     *note str: 3f2.、*note int: 23c.、*note float: 2c8.、*note bool:
     40e.、‘None’）的 dictionary（字典）鍵值將被略過而不會引發 *note
     TypeError: 4dd.。

     *note json: 76. 模組總是產生 *note str: 3f2. 物件，而非 *note
     bytes: 1a5. 物件。因此，‘fp.write()’ 必須支援 *note str: 3f2. 輸入
     。

     如果 'ensure_ascii' 被設為 true（預設值），則輸出時將確保所有輸入的
     非 ASCII 字元都會被轉義。若 'ensure_ascii' 為 false，則這些字元將照
     原樣輸出。

     如果 'check_circular' 設為 false（預設是 ‘True’），則針對不同容器型
     別的循環參照 (circular reference) 檢查將會被跳過，若有循環參照則最
     後將引發 *note RecursionError: d12. （或其他更糟的錯誤）。

     如果 'allow_nan' 為 false（預設值：‘True’），則序列化不符合嚴格
     JSON 規範的 *note float: 2c8. 值 (‘nan’, ‘inf’, ‘-inf’) 會引發
     *note ValueError: 1e7.。如果 'allow_nan' 為 true，則將使用它們的
     JavaScript 等效表示 (‘NaN’, ‘Infinity’, ‘-Infinity’)。

     如果 'indent' 是非負整數或字串，則 JSON 陣列元素和物件成員將使用該
     縮排等級進行格式美化。縮排等級 0、負數或 ‘""’ 只會插入換行符號。
     ‘None’（預設值）等於是選擇最緊湊的表示法。使用正整數縮排可以在每層
     縮排數量相同的空格。如果 'indent' 是一個字串（例如 ‘"\t"’），則該字
     串用於縮排每個層級。

     在 3.2 版的變更: 除了整數之外，'indent' 還允許使用字串作為輸入。

     如果有指定本引數內容，'separators' 應該是一個 ‘(item_separator,
     key_separator)’ 二元組。如果 'indent' 為 ‘None’ 則預設為 ‘(', ', ':
     ')’，否則預設為 ‘(',', ': ')’。想要獲得最緊湊的 JSON 表示形式，你可
     以改成指定 ‘(',', ':')’ 來消除空格。

     在 3.4 版的變更: 如果 'indent' 不是 ‘None’，則使用 ‘(',', ': ')’ 作
     為預設值

     如果有指定本參數，'default' 會是一個遭遇無法序列化的物件時會被呼叫
     的函式。它應該回傳該物件的 JSON 可編碼版本或引發 *note TypeError:
     4dd.。如果未指定，則會直接引發 *note TypeError: 4dd.。

     如果 'sort_keys' 為 true（預設值：‘False’），則字典的輸出將按鍵值排
     序。

     若要使用繼承自 *note JSONEncoder: ced. 的自訂子類別（例如覆寫 *note
     default(): 349c. 方法來序列化其他型別的一個子類別物件），請使用關鍵
     字引數 'cls' 指定該類別物件；否則預設使用 *note JSONEncoder: ced.。

     在 3.6 版的變更: 所有可選參數現在都是*note 僅限關鍵字: 285.參數了。

          備註: 與 *note pickle: 95. 和 *note marshal: 80. 不同，JSON 不
          具有二進位分框（binary framed）的協定，因此嘗試重複呼叫 *note
          dump(): ceb. 來序列化多個物件到同一個 'fp' 裡將導致無效的 JSON
          檔案。

 -- 函式: json.dumps (obj, *, skipkeys=False, ensure_ascii=True,
          check_circular=True, allow_nan=True, cls=None, indent=None,
          separators=None, default=None, sort_keys=False, **kw)

     使用此*note 轉換表: 349d.來將 'obj' 序列化為 JSON 格式 *note str:
     3f2.。這個引數的作用與 *note dump(): ceb. 中的同名引數意義相同。

          備註: JSON 鍵/值對中的鍵始終為 *note str: 3f2. 型別。當字典被
          轉換為 JSON 時，字典的所有鍵值資料型別都會被強制轉換為字串。因
          此，如果將字典先轉換為 JSON 格式然後再轉換回字典，則該字典可能
          不等於原始字典。也就是說，如果字典 x 含有非字串鍵值，則
          ‘loads(dumps(x)) != x’。

 -- 函式: json.load (fp, *, cls=None, object_hook=None,
          parse_float=None, parse_int=None, parse_constant=None,
          object_pairs_hook=None, **kw)

     使用此*note 轉換表: 349d.來將 'fp'（一個支援 ‘.read()’、包含 JSON 文
     件的*note 文字檔案: 1b8a.或*note 二進位檔案: 1b8b.）去序列化為
     Python 物件。

     'object_hook' 是一個可選引數，其接受一個函式作為輸入。原始的字串解
     碼結果（一個 *note dict: 23b.）將被傳入這個函式、並使用
     'object_hook' 的回傳值來取代原先的 *note dict: 23b. 輸出。此功能可
     用於實作自訂解碼器（例如 JSON-RPC(1) 類別提示）。

     'object_pairs_hook' 是一個可選引數，其接受一個函式作為輸入。原始的
     有序對串列（ordered list of pairs）解碼結果將被傳入這個函式、並使用
     'object_pairs_hook' 的回傳值來取代原先的 *note dict: 23b. 輸出。此
     功能可用於實作自訂解碼器。如果也同時給定了 'object_hook'，則
     'object_pairs_hook' 優先。

     在 3.1 版的變更: 新增對於 'object_pairs_hook' 的支援。

     'parse_float' 為可選函式，每個要被解碼的 JSON 浮點數字串都會改用這
     個參數給定的函式來進行解碼。預設情況這等效於 ‘float(num_str)’。這個
     參數可用於將 JSON 中的浮點數解碼或剖析為另一種資料型別（例如 *note
     decimal.Decimal: 27c.）。

     'parse_int' 為可選函式，當解碼 JSON 整數字串時會被呼叫。預設情況等
     效於 ‘int(num_str)’。這個參數可用於將 JSON 中的整數解碼或剖析為另一
     種資料型別（例如 *note float: 2c8.）。

     在 3.11 版的變更: 預設 'parse_int' 使用的 *note int(): 23c. 函式現
     在有限制整數字串的長度上限了，限制由直譯器的*note
     整數字串轉換長度限制: 599.機制來達成，這能防止阻斷服務攻擊 (Denial
     of Service attacks)。

     'parse_constant' 為可選函式，在解碼時若遭遇字串 ‘'-Infinity'’、
     ‘'Infinity'’ 或 ‘'NaN'’ 其中之一則會改用這個參數給定的函式來進行解
     碼。這也可用於使解碼過程中遇到無效的 JSON 數字時引發一個例外。

     在 3.1 版的變更: 遭遇 'null'、'true' 或 'false' 時不再以
     'parse_constant' 給定的函式來處理了。

     若想要使用自訂的 *note JSONDecoder: cee. 子類別物件，請以 ‘cls’ 關
     鍵字引數指定之，否則將使用預設的 *note JSONDecoder: cee.。其他未使
     用到的關鍵字引數將繼續傳入給 JSONDecoder 的建構函式使用。

     如果被去序列化（deserialized）的資料不符合 JSON 格式，將會引發
     *note JSONDecodeError: dc6. 例外。

     在 3.6 版的變更: 所有可選參數現在都是*note 僅限關鍵字: 285.參數了。

     在 3.6 版的變更: 現在，'fp' 可以是一個*note 二進位檔案: 1b8b.，前提
     是其編碼格式為 UTF-8、UTF-16 或 UTF-32。

 -- 函式: json.loads (s, *, cls=None, object_hook=None,
          parse_float=None, parse_int=None, parse_constant=None,
          object_pairs_hook=None, **kw)

     使用*note 轉換表: 349d.將 's' （一個含有 JSON 文件的 *note str:
     3f2.、*note bytes: 1a5. 或 *note bytearray: 4e3. 的實例（instance）
     ）去序列化（deserialize）為一個 Python 物件

     其餘引數的使用方式與意義和 *note load(): c5b. 的相同。

     如果被去序列化（deserialized）的資料不符合 JSON 格式，將會引發
     *note JSONDecodeError: dc6. 例外。

     在 3.6 版的變更: 現在，'s' 可以是一個二進位檔案如 *note bytes: 1a5.
     或 *note bytearray: 4e3.，前提是其編碼格式為 UTF-8、UTF-16 或
     UTF-32。

     在 3.9 版的變更: 刪除關鍵字引數 'encoding'。

   ---------- Footnotes ----------

   (1) https://www.jsonrpc.org


File: python.info,  Node: 編碼器與解碼器,  Next: 例外<12>,  Prev: 基本用法<2>,  Up: json --- JSON 編碼器與解碼器

5.19.2.2 編碼器與解碼器
.......................

 -- 類別: json.JSONDecoder (*, object_hook=None, parse_float=None,
          parse_int=None, parse_constant=None, strict=True,
          object_pairs_hook=None)

     簡易 JSON 解碼器

     預設將執行下列資料型別轉換：

     JSON                Python
                         
     --------------------------------------------
                         
     object              dict
                         
                         
     array               list
                         
                         
     string              str
                         
                         
     number (整數)       int
                         
                         
     number (實數)       float
                         
                         
     true                True
                         
                         
     false               False
                         
                         
     null                None
                         

     雖然 ‘NaN’、‘Infinity’ 和 ‘-Infinity’ 並不符合 JSON 規範，但解碼器
     依然能正確地將其轉換到相應的 Python ‘float’ 值。

     'object_hook' 是一個可選函式，其接受一個解碼後的 JSON 物件作為輸入
     ，並使用其回傳值來取代原先的 *note dict: 23b.。這個功能可用於提供自
     訂的去序列化（例如支援 JSON-RPC(1) 類別提示）。

     'object_pairs_hook' is an optional function that will be called
     with the result of every JSON object decoded with an ordered list
     of pairs.  The return value of 'object_pairs_hook' will be used
     instead of the *note dict: 23b.  This feature can be used to
     implement custom decoders.  If 'object_hook' is also defined, the
     'object_pairs_hook' takes priority.

     在 3.1 版的變更: 新增對於 'object_pairs_hook' 的支援。

     'parse_float' 為可選函式，每個要被解碼的 JSON 浮點數字串都會改用這
     個參數給定的函式來進行解碼。預設情況這等效於 ‘float(num_str)’。這個
     參數可用於將 JSON 中的浮點數解碼或剖析為另一種資料型別（例如 *note
     decimal.Decimal: 27c.）。

     'parse_int' 為可選函式，當解碼 JSON 整數字串時會被呼叫。預設情況等
     效於 ‘int(num_str)’。這個參數可用於將 JSON 中的整數解碼或剖析為另一
     種資料型別（例如 *note float: 2c8.）。

     'parse_constant' 為可選函式，在解碼時若遭遇字串 ‘'-Infinity'’、
     ‘'Infinity'’ 或 ‘'NaN'’ 其中之一則會改用這個參數給定的函式來進行解
     碼。這也可用於使解碼過程中遇到無效的 JSON 數字時引發一個例外。

     如果 'strict' 被設為 false（預設值為 ‘True’），那麼字串中將允許控制
     字元。此語境中的控制字元指的是 ASCII 字元編碼在 0～31 範圍內的字元
     ，包括 ‘'\t'``（tab）、’'n'‘、’'r''' 和 ‘'\0'’。

     如果被去序列化（deserialized）的資料不符合 JSON 格式，將會引發
     *note JSONDecodeError: dc6. 例外。

     在 3.6 版的變更: 所有參數現在都是*note 僅限關鍵字參數: 285.了。

      -- 方法: decode (s)

          回傳用 Python 型式表達的 's' （一個含有 JSON 文件的 *note str:
          3f2. 實例）。

          若給定的輸入不符合 JSON 格式會引發 *note JSONDecodeError: dc6.
          例外。

      -- 方法: raw_decode (s)

          將 's' （一個開頭部分含有合格 JSON 文件的 *note str: 3f2.） 解
          碼，並將 JSON 文件結束點的索引值（index）和解碼結果合併為一個
          二元組（2-tuple）後回傳。

          這個方法可以用來解碼尾段可能帶有 JSON 以外資料的文字。

 -- 類別: json.JSONEncoder (*, skipkeys=False, ensure_ascii=True,
          check_circular=True, allow_nan=True, sort_keys=False,
          indent=None, separators=None, default=None)

     可擴充的 Python 資料結構 JSON 編碼器。

     預設可支援下列物件及型別：

     Python                                       JSON
                                                  
     -----------------------------------------------------------------
                                                  
     dict                                         object
                                                  
                                                  
     list, tuple                                  array
                                                  
                                                  
     str                                          string
                                                  
                                                  
     int、float 或可作為整數或浮點數運算的衍生    number
     列舉（int- or float-derived Enums）          

     True                                         true
                                                  
                                                  
     False                                        false
                                                  
                                                  
     None                                         null
                                                  

     在 3.4 版的變更: 增加對整數（int）、浮點數（float）或可作為整數或浮
     點數運算的衍生列舉（int- or float-derived Enums）類別的支援性。

     若要擴充此功能來識別其他物件，請繼承並實作一個 *note default():
     349c. 方法。此方法應回傳一個可序列化的 ‘o’ 物件，否則此方法應呼叫父
     類別的 JSONEncoder.default 方法（以引發 *note TypeError: 4dd. 例外
     ）。

     若 'skipkeys' 為 false（預設值），則當在編碼不是 *note str: 3f2.、
     *note int: 23c.、*note float: 2c8. 或 ‘None’ 的鍵值時，將引發 *note
     TypeError: 4dd.。如果 'skipkeys' 為 true，這些項目將直接被跳過。

     如果 'ensure_ascii' 被設為 true（預設值），則輸出時將確保所有輸入的
     非 ASCII 字元都會被轉義。若 'ensure_ascii' 為 false，則這些字元將照
     原樣輸出。

     如果 'check_circular' 為 true（預設值），則會在編碼期間檢查串列（
     list）、字典（dict）和自訂編碼物件的循環參照，以防止無限遞迴（一個
     會導致 *note RecursionError: d12. 例外的問題）。否則不會進行此類檢
     查。

     如果 'allow_nan' 為 true（預設值），則 ‘NaN’、‘Infinity’ 和
     ‘-Infinity’ 將按照原樣進行編碼。請記得此行為不符合標準 JSON 規範，
     但的確與大多數基於 JavaScript 的編碼器和解碼器一致。否則若設為
     false，嘗試對這些浮點數進行編碼將引發 *note ValueError: 1e7. 例外。

     如果 'sort_keys' 為 true（預設值：‘False’），則 dictionary（字典）
     的輸出將按鍵值排序。這項功能可確保 JSON 序列化的結果能被互相比較，
     能讓日常的回歸測試檢查變得方便一些。

     如果 'indent' 是非負整數或字串，則 JSON 陣列元素和物件成員將使用該
     縮排等級進行格式美化。縮排等級 0、負數或 ‘""’ 只會插入換行符號。
     ‘None’（預設值）等於是選擇最緊湊的表示法。使用正整數縮排可以在每層
     縮排數量相同的空格。如果 'indent' 是一個字串（例如 ‘"\t"’），則該字
     串用於縮排每個層級。

     在 3.2 版的變更: 除了整數之外，'indent' 還允許使用字串作為輸入。

     如果有指定本引數內容，'separators' 應該是一個 ‘(item_separator,
     key_separator)’ 二元組。如果 'indent' 為 ‘None’ 則預設為 ‘(', ', ':
     ')’，否則預設為 ‘(',', ': ')’。想要獲得最緊湊的 JSON 表示形式，你可
     以改成指定 ‘(',', ':')’ 來消除空格。

     在 3.4 版的變更: 如果 'indent' 不是 ‘None’，則使用 ‘(',', ': ')’ 作
     為預設值

     如果有指定本參數，'default' 會是一個遭遇無法序列化的物件時會被呼叫
     的函式。它應該回傳該物件的 JSON 可編碼版本或引發 *note TypeError:
     4dd.。如果未指定，則會直接引發 *note TypeError: 4dd.。

     在 3.6 版的變更: 所有參數現在都是*note 僅限關鍵字參數: 285.了。

      -- 方法: default (o)

          在任意一個子類別裡實作這個方法時須讓其回傳一個可序列化的物件
          'o' ，或呼叫原始的實作以引發 *note TypeError: 4dd. 例外。

          舉例來說，想要讓編碼器支援任意疊代器（iterator），你可以實作這
          樣子的 *note default(): 349c.：

               def default(self, o):
                  try:
                      iterable = iter(o)
                  except TypeError:
                      pass
                  else:
                      return list(iterable)
                  # Let the base class default method raise the TypeError
                  return super().default(o)

      -- 方法: encode (o)

          回傳一個 Python 資料結構物件 'o' 的 JSON 的字串表示。例如：

               >>> json.JSONEncoder().encode({"foo": ["bar", "baz"]})
               '{"foo": ["bar", "baz"]}'

      -- 方法: iterencode (o)

          將物件 'o' 編碼，並將結果統整為一個能依序產生（yield）各結果字
          串的物件。如下例：

               for chunk in json.JSONEncoder().iterencode(bigobject):
                   mysocket.write(chunk)

   ---------- Footnotes ----------

   (1) https://www.jsonrpc.org


File: python.info,  Node: 例外<12>,  Next: 合規性與互通性（Interoperability）,  Prev: 編碼器與解碼器,  Up: json --- JSON 編碼器與解碼器

5.19.2.3 例外
.............

 -- 例外: json.JSONDecodeError (msg, doc, pos)

     *note ValueError: 1e7. 的子類別具有下列額外屬性：

      -- 屬性: msg

          未受格式化的錯誤訊息。

      -- 屬性: doc

          正在被剖析的 JSON 文件。

      -- 屬性: pos

          'doc' 剖析失敗處的起始點的索引值。

      -- 屬性: lineno

          'pos' 所在的列（line）數。

      -- 屬性: colno

          'pos' 所在的行（column）數。

     在 3.5 版被加入.


File: python.info,  Node: 合規性與互通性（Interoperability）,  Next: 命令列介面<3>,  Prev: 例外<12>,  Up: json --- JSON 編碼器與解碼器

5.19.2.4 合規性與互通性（Interoperability）
...........................................

JSON 格式是由 RFC 7159(1) 和 ECMA-404(2) 規範的。本節詳細說明了本模組對
RFC 的遵循程度。簡單起見，*note JSONEncoder: ced. 和 *note JSONDecoder:
cee. 子類別以及未明確提及的參數將不予討論。

這個模組的部份實作並未非常嚴格地遵循 RFC 規範。準確來說，下列實際實作符
合 JavaScript 語法格式，但並不符合 JSON 格式：

   - 無限（Infinite）和非數字（NaN）值會被接受。

   - 同一個物件內可以有重複的名稱，但只有最後一個同名物件是有效的。

不過 RFC 准許遵循 RFC 的剖析器接受不合規的文字輸入，所以技術上來說若以預
設設定運作，本模組的去序列化器（deserializer）是符合 RFC 規範的。

* Menu:

* 字元編碼格式::
* 正負無限與非數值::
* 物件內重複的名稱::
* 位於頂層的非物件及非列表值::
* 實作限制::

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc7159.html

   (2) 
https://www.ecma-international.org/publications-and-standards/standards/ecma-404/


File: python.info,  Node: 字元編碼格式,  Next: 正負無限與非數值,  Up: 合規性與互通性（Interoperability）

5.19.2.5 字元編碼格式
.....................

RFC 要求 JSON 必須以 UTF-8、UTF-16 或 UTF-32 格式編碼。並推薦以 UTF-8 編
碼以達成最佳的互通性。

RFC 准許但並不強制編碼器的 'ensure_ascii=True' 行為是預設值，但本模組依
然實作了此一選項作為預設，因此本模組預設會轉義所有非 ASCII 字元。

除了 'ensure_ascii' 選項參數之外，本模組嚴格遵循 Python 物件與 *note
Unicode strings: 3f2. 之間的轉換規範，因此並不另外處理字元編碼的問題。

RFC 禁止在文件的開頭加上端序記號（Byte Order Mark），因此本模組的序列化
器（serializer）也不會在輸出中加入端序記號。RFC 允許但不強制 JSON 去序列
化器（deserializer）忽略文件初始的端序記號，因此本模組的去序列化器將在遭
遇位於文件開頭的端序記號時引發 *note ValueError: 1e7. 例外。

RFC 並未明確禁止 JSON 文件包含無法對應有效 Unicode 字元的位元組序列（例
如未配對的 UTF-16 代理對（surrogate pairs）），但這個特性的確可能會引起
相容性問題。預設情況下，當原始輸入的 *note str: 3f2. 中存在此類序列時，
該模組將接受並輸出這些序列的編碼位置（code points）。


File: python.info,  Node: 正負無限與非數值,  Next: 物件內重複的名稱,  Prev: 字元編碼格式,  Up: 合規性與互通性（Interoperability）

5.19.2.6 正負無限與非數值
.........................

RFC 不允許表現無限大或非數值（NaN）。但預設情況下，這個模組仍接受並輸出
‘Infinity’、‘-Infinity’ 和 ‘NaN’，如同它們是有效的 JSON 數值字面值：

     >>> # Neither of these calls raises an exception, but the results are not valid JSON
     >>> json.dumps(float('-inf'))
     '-Infinity'
     >>> json.dumps(float('nan'))
     'NaN'
     >>> # Same when deserializing
     >>> json.loads('-Infinity')
     -inf
     >>> json.loads('NaN')
     nan

在序列化器中，'allow_nan' 參數可以改變這個行為。在去序列化器中，
'parse_constant' 參數可以改變這個行為。


File: python.info,  Node: 物件內重複的名稱,  Next: 位於頂層的非物件及非列表值,  Prev: 正負無限與非數值,  Up: 合規性與互通性（Interoperability）

5.19.2.7 物件內重複的名稱
.........................

RFC 規範僅表明 JSON 物件中的名字應該是唯一的，但沒有強制要求如何處理重複
的名字。預設情況下，本模組不會因此引發例外；相反的，它會忽略該名字的所有
重複鍵值對，並只保留最後一個：

     >>> weird_json = '{"x": 1, "x": 2, "x": 3}'
     >>> json.loads(weird_json)
     {'x': 3}

'object_parts_hook' 參數可以改變這個行為。


File: python.info,  Node: 位於頂層的非物件及非列表值,  Next: 實作限制,  Prev: 物件內重複的名稱,  Up: 合規性與互通性（Interoperability）

5.19.2.8 位於頂層的非物件及非列表值
...................................

由已廢棄的 RFC 4627(1) 所規範的舊版 JSON 要求 JSON 文字的頂層值必須是
JSON 物件或陣列（Python *note dict: 23b. 或 *note list: 5b6.），而且不能
是 JSON 的 null、boolean、數字或字串值。 RFC 7159(2) 移除了這個限制，而
本模組的序列化器或去串列化器中未曾實施過該限制。

如果想要最大限度地保留互通性，你可能還是會想要自行施加這個限制。

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc4627.html

   (2) https://datatracker.ietf.org/doc/html/rfc7159.html


File: python.info,  Node: 實作限制,  Prev: 位於頂層的非物件及非列表值,  Up: 合規性與互通性（Interoperability）

5.19.2.9 實作限制
.................

某些 JSON 去序列化器的實作可能會造成下列限制：

   * JSON 文件長度上限

   * JSON 物件或陣列的最大巢狀層數（level of nesting）限制

   * 數字的精準度或範圍

   * JSON 字串長度上限

本模組除了 Python 資料型態本身或 Python 直譯器本身的限制以外，不會設定任
何此類限制。

將資料序列化為 JSON 時，要注意可能會使用該 JSON 輸出的應用程式中的相關限
制。特別要注意的是，JSON 數字常會被去序列化為 IEEE 754 雙精度浮點數（
double），並因而受到其表示範圍和精度限制的影響。這在序列化極大的 Python
*note int: 23c. 數值、或是序列化特殊數字型別的實例時（例如 *note
decimal.Decimal: 27c.）尤其重要。


File: python.info,  Node: 命令列介面<3>,  Prev: 合規性與互通性（Interoperability）,  Up: json --- JSON 編碼器與解碼器

5.19.2.10 命令列介面
....................

'原始碼：'Lib/json/tool.py(1)

__________________________________________________________________

*note json.tool: 77. 模組提供了一個簡易的命令列界面以供校驗與美化呈現
JSON 物件。

如果沒有指定可選引數 ‘infile’ 和 ‘outfile’ ，則 *note sys.stdin: 4e2. 和
*note sys.stdout: a79. 將各自做為輸入和輸出的預設值。

     $ echo '{"json": "obj"}' | python -m json.tool
     {
         "json": "obj"
     }
     $ echo '{1.2:3.4}' | python -m json.tool
     Expecting property name enclosed in double quotes: line 1 column 2 (char 1)

在 3.5 版的變更: 現在開始輸出和輸入的資料順序會是相同的。傳入 *note
-sort-keys: 34b0. 引數以按照鍵值的字母順序對輸出進行排序。

* Menu:

* 命令列選項: 命令列選項<3>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/json/tool.py


File: python.info,  Node: 命令列選項<3>,  Up: 命令列介面<3>

5.19.2.11 命令列選項
....................

 -- Option: infile

     將被用於校驗或美化呈現的 JSON 文件：

          $ python -m json.tool mp_films.json
          [
              {
                  "title": "And Now for Something Completely Different",
                  "year": 1971
              },
              {
                  "title": "Monty Python and the Holy Grail",
                  "year": 1975
              }
          ]

     如果沒有指定 'infile' 則會從 *note sys.stdin: 4e2. 讀取輸入。

 -- Option: outfile

     將 'infile' 的結果寫入到給定的 'outfile'。若未提供則寫入到 *note
     sys.stdout: a79.。

 -- Option: --sort-keys

     按照鍵值的字母順序對輸出字典進行排序。

     在 3.5 版被加入.

 -- Option: --no-ensure-ascii

     關閉非 ASCII 字元的自動轉義功能。詳情請參照 *note json.dumps():
     cec.。

     在 3.9 版被加入.

 -- Option: --json-lines

     將每一行輸入都單獨輸出為一個 JSON 物件。

     在 3.8 版被加入.

 -- Option: --indent, --tab, --no-indent, --compact

     互斥的空白字元控制選項。

     在 3.9 版被加入.

 -- Option: -h, --help

     顯示說明訊息。

註解
....


File: python.info,  Node: mailbox --- 以各種格式操作郵件信箱,  Next: mimetypes --- 將檔案名稱對映到 MIME 類型,  Prev: json --- JSON 編碼器與解碼器,  Up: 網際網路資料處理

5.19.3 ‘mailbox’ -- 以各種格式操作郵件信箱
------------------------------------------

'原始碼：'Lib/mailbox.py(1)

__________________________________________________________________

This module defines two classes, *note Mailbox: 11e5. and *note Message:
11e9, for accessing and manipulating on-disk mailboxes and the messages
they contain.  ‘Mailbox’ offers a dictionary-like mapping from keys to
messages.  ‘Message’ extends the *note email.message: 3b. module's *note
Message: 261. class with format-specific state and behavior.  Supported
mailbox formats are Maildir, mbox, MH, Babyl, and MMDF.

也參考
......

*note email: 32. 模組

     Represent and manipulate messages.

* Menu:

* Mailbox 物件::
* Message 物件::
* 例外: 例外<13>.
* 範例: 範例<29>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/mailbox.py


File: python.info,  Node: Mailbox 物件,  Next: Message 物件,  Up: mailbox --- 以各種格式操作郵件信箱

5.19.3.1 ‘Mailbox’ 物件
.......................

 -- 類別: mailbox.Mailbox

     A mailbox, which may be inspected and modified.

     The ‘Mailbox’ class defines an interface and is not intended to be
     instantiated.  Instead, format-specific subclasses should inherit
     from ‘Mailbox’ and your code should instantiate a particular
     subclass.

     The ‘Mailbox’ interface is dictionary-like, with small keys
     corresponding to messages.  Keys are issued by the ‘Mailbox’
     instance with which they will be used and are only meaningful to
     that ‘Mailbox’ instance.  A key continues to identify a message
     even if the corresponding message is modified, such as by replacing
     it with another message.

     Messages may be added to a ‘Mailbox’ instance using the set-like
     method *note add(): 11e4. and removed using a ‘del’ statement or
     the set-like methods *note remove(): 34c0. and *note discard():
     34c1.

     ‘Mailbox’ interface semantics differ from dictionary semantics in
     some noteworthy ways.  Each time a message is requested, a new
     representation (typically a *note Message: 11e9. instance) is
     generated based upon the current state of the mailbox.  Similarly,
     when a message is added to a ‘Mailbox’ instance, the provided
     message representation's contents are copied.  In neither case is a
     reference to the message representation kept by the ‘Mailbox’
     instance.

     The default ‘Mailbox’ *note iterator: 192. iterates over message
     representations, not keys as the default *note dictionary: 23b.
     iterator does.  Moreover, modification of a mailbox during
     iteration is safe and well-defined.  Messages added to the mailbox
     after an iterator is created will not be seen by the iterator.
     Messages removed from the mailbox before the iterator yields them
     will be silently skipped, though using a key from an iterator may
     result in a *note KeyError: 2fb. exception if the corresponding
     message is subsequently removed.

          警告: Be very cautious when modifying mailboxes that might be
          simultaneously changed by some other process.  The safest
          mailbox format to use for such tasks is *note Maildir: 353.;
          try to avoid using single-file formats such as *note mbox:
          1575. for concurrent writing.  If you're modifying a mailbox,
          you 'must' lock it by calling the *note lock(): 34c2. and
          *note unlock(): 34c3. methods 'before' reading any messages in
          the file or making any changes by adding or deleting a
          message.  Failing to lock the mailbox runs the risk of losing
          messages or corrupting the entire mailbox.

     ‘Mailbox’ instances have the following methods:

      -- 方法: add (message)

          Add 'message' to the mailbox and return the key that has been
          assigned to it.

          Parameter 'message' may be a *note Message: 11e9. instance, an
          *note email.message.Message: 261. instance, a string, a byte
          string, or a file-like object (which should be open in binary
          mode).  If 'message' is an instance of the appropriate
          format-specific *note Message: 11e9. subclass (e.g., if it's
          an *note mboxMessage: 3394. instance and this is an *note
          mbox: 1575. instance), its format-specific information is
          used.  Otherwise, reasonable defaults for format-specific
          information are used.

          在 3.2 版的變更: Support for binary input was added.

      -- 方法: remove (key)
      -- 方法: __delitem__ (key)
      -- 方法: discard (key)

          Delete the message corresponding to 'key' from the mailbox.

          If no such message exists, a *note KeyError: 2fb. exception is
          raised if the method was called as *note remove(): 34c0. or
          *note __delitem__(): 34c4. but no exception is raised if the
          method was called as *note discard(): 34c1.  The behavior of
          *note discard(): 34c1. may be preferred if the underlying
          mailbox format supports concurrent modification by other
          processes.

      -- 方法: __setitem__ (key, message)

          Replace the message corresponding to 'key' with 'message'.
          Raise a *note KeyError: 2fb. exception if no message already
          corresponds to 'key'.

          As with *note add(): 11e4, parameter 'message' may be a *note
          Message: 11e9. instance, an *note email.message.Message: 261.
          instance, a string, a byte string, or a file-like object
          (which should be open in binary mode).  If 'message' is an
          instance of the appropriate format-specific *note Message:
          11e9. subclass (e.g., if it's an *note mboxMessage: 3394.
          instance and this is an *note mbox: 1575. instance), its
          format-specific information is used.  Otherwise, the
          format-specific information of the message that currently
          corresponds to 'key' is left unchanged.

      -- 方法: iterkeys ()

          Return an *note iterator: 192. over all keys

      -- 方法: keys ()

          The same as *note iterkeys(): 34c6, except that a *note list:
          5b6. is returned rather than an *note iterator: 192.

      -- 方法: itervalues ()
      -- 方法: __iter__ ()

          Return an *note iterator: 192. over representations of all
          messages.  The messages are represented as instances of the
          appropriate format-specific *note Message: 11e9. subclass
          unless a custom message factory was specified when the
          ‘Mailbox’ instance was initialized.

               備註: The behavior of *note __iter__(): 34c9. is unlike
               that of dictionaries, which iterate over keys.

      -- 方法: values ()

          The same as *note itervalues(): 34c8, except that a *note
          list: 5b6. is returned rather than an *note iterator: 192.

      -- 方法: iteritems ()

          Return an *note iterator: 192. over ('key', 'message') pairs,
          where 'key' is a key and 'message' is a message
          representation.  The messages are represented as instances of
          the appropriate format-specific *note Message: 11e9. subclass
          unless a custom message factory was specified when the
          ‘Mailbox’ instance was initialized.

      -- 方法: items ()

          The same as *note iteritems(): 34cb, except that a *note list:
          5b6. of pairs is returned rather than an *note iterator: 192.
          of pairs.

      -- 方法: get (key, default=None)
      -- 方法: __getitem__ (key)

          Return a representation of the message corresponding to 'key'.
          If no such message exists, 'default' is returned if the method
          was called as *note get(): 34cd. and a *note KeyError: 2fb.
          exception is raised if the method was called as
          ‘__getitem__()’.  The message is represented as an instance of
          the appropriate format-specific *note Message: 11e9. subclass
          unless a custom message factory was specified when the
          ‘Mailbox’ instance was initialized.

      -- 方法: get_message (key)

          Return a representation of the message corresponding to 'key'
          as an instance of the appropriate format-specific *note
          Message: 11e9. subclass, or raise a *note KeyError: 2fb.
          exception if no such message exists.

      -- 方法: get_bytes (key)

          Return a byte representation of the message corresponding to
          'key', or raise a *note KeyError: 2fb. exception if no such
          message exists.

          在 3.2 版被加入.

      -- 方法: get_string (key)

          Return a string representation of the message corresponding to
          'key', or raise a *note KeyError: 2fb. exception if no such
          message exists.  The message is processed through *note
          email.message.Message: 261. to convert it to a 7bit clean
          representation.

      -- 方法: get_file (key)

          Return a *note file-like: 246a. representation of the message
          corresponding to 'key', or raise a *note KeyError: 2fb.
          exception if no such message exists.  The file-like object
          behaves as if open in binary mode.  This file should be closed
          once it is no longer needed.

          在 3.2 版的變更: The file object really is a *note binary
          file: 1b8b.; previously it was incorrectly returned in text
          mode.  Also, the *note file-like object: 246a. now supports
          the *note context manager: 576. protocol: you can use a *note
          with: 577. statement to automatically close it.

               備註: Unlike other representations of messages, *note
               file-like: 246a. representations are not necessarily
               independent of the ‘Mailbox’ instance that created them
               or of the underlying mailbox.  More specific
               documentation is provided by each subclass.

      -- 方法: __contains__ (key)

          Return ‘True’ if 'key' corresponds to a message, ‘False’
          otherwise.

      -- 方法: __len__ ()

          Return a count of messages in the mailbox.

      -- 方法: clear ()

          Delete all messages from the mailbox.

      -- 方法: pop (key, default=None)

          Return a representation of the message corresponding to 'key'
          and delete the message.  If no such message exists, return
          'default'.  The message is represented as an instance of the
          appropriate format-specific *note Message: 11e9. subclass
          unless a custom message factory was specified when the
          ‘Mailbox’ instance was initialized.

      -- 方法: popitem ()

          Return an arbitrary ('key', 'message') pair, where 'key' is a
          key and 'message' is a message representation, and delete the
          corresponding message.  If the mailbox is empty, raise a *note
          KeyError: 2fb. exception.  The message is represented as an
          instance of the appropriate format-specific *note Message:
          11e9. subclass unless a custom message factory was specified
          when the ‘Mailbox’ instance was initialized.

      -- 方法: update (arg)

          Parameter 'arg' should be a 'key'-to-'message' mapping or an
          iterable of ('key', 'message') pairs.  Updates the mailbox so
          that, for each given 'key' and 'message', the message
          corresponding to 'key' is set to 'message' as if by using
          *note __setitem__(): 34c5.  As with *note __setitem__(): 34c5,
          each 'key' must already correspond to a message in the mailbox
          or else a *note KeyError: 2fb. exception will be raised, so in
          general it is incorrect for 'arg' to be a ‘Mailbox’ instance.

               備註: Unlike with dictionaries, keyword arguments are not
               supported.

      -- 方法: flush ()

          Write any pending changes to the filesystem.  For some *note
          Mailbox: 11e5. subclasses, changes are always written
          immediately and ‘flush()’ does nothing, but you should still
          make a habit of calling this method.

      -- 方法: lock ()

          Acquire an exclusive advisory lock on the mailbox so that
          other processes know not to modify it.  An *note
          ExternalClashError: 34d7. is raised if the lock is not
          available.  The particular locking mechanisms used depend upon
          the mailbox format.  You should 'always' lock the mailbox
          before making any modifications to its contents.

      -- 方法: unlock ()

          Release the lock on the mailbox, if any.

      -- 方法: close ()

          Flush the mailbox, unlock it if necessary, and close any open
          files.  For some ‘Mailbox’ subclasses, this method does
          nothing.

* Menu:

* Mailbox 物件: Mailbox 物件<2>.
* mbox 物件::
* MH 物件::
* Babyl 物件::
* MMDF 物件::


File: python.info,  Node: Mailbox 物件<2>,  Next: mbox 物件,  Up: Mailbox 物件

5.19.3.2 ‘Mailbox’ 物件
.......................

 -- 類別: mailbox.Maildir (dirname, factory=None, create=True)

     A subclass of *note Mailbox: 11e5. for mailboxes in Maildir format.
     Parameter 'factory' is a callable object that accepts a file-like
     message representation (which behaves as if opened in binary mode)
     and returns a custom representation.  If 'factory' is ‘None’, *note
     MaildirMessage: 34db. is used as the default message
     representation.  If 'create' is ‘True’, the mailbox is created if
     it does not exist.

     If 'create' is ‘True’ and the 'dirname' path exists, it will be
     treated as an existing maildir without attempting to verify its
     directory layout.

     It is for historical reasons that 'dirname' is named as such rather
     than 'path'.

     Maildir is a directory-based mailbox format invented for the qmail
     mail transfer agent and now widely supported by other programs.
     Messages in a Maildir mailbox are stored in separate files within a
     common directory structure.  This design allows Maildir mailboxes
     to be accessed and modified by multiple unrelated programs without
     data corruption, so file locking is unnecessary.

     Maildir mailboxes contain three subdirectories, namely: ‘tmp’,
     ‘new’, and ‘cur’.  Messages are created momentarily in the ‘tmp’
     subdirectory and then moved to the ‘new’ subdirectory to finalize
     delivery.  A mail user agent may subsequently move the message to
     the ‘cur’ subdirectory and store information about the state of the
     message in a special "info" section appended to its file name.

     Folders of the style introduced by the Courier mail transfer agent
     are also supported.  Any subdirectory of the main mailbox is
     considered a folder if ‘'.'’ is the first character in its name.
     Folder names are represented by ‘Maildir’ without the leading
     ‘'.'’.  Each folder is itself a Maildir mailbox but should not
     contain other folders.  Instead, a logical nesting is indicated
     using ‘'.'’ to delimit levels, e.g., "Archived.2005.07".

      -- 屬性: colon

          The Maildir specification requires the use of a colon (‘':'’)
          in certain message file names.  However, some operating
          systems do not permit this character in file names, If you
          wish to use a Maildir-like format on such an operating system,
          you should specify another character to use instead.  The
          exclamation point (‘'!'’) is a popular choice.  For example:

               import mailbox
               mailbox.Maildir.colon = '!'

          The ‘colon’ attribute may also be set on a per-instance basis.

     在 3.13 版的變更: *note Maildir: 353. now ignores files with a
     leading dot.

     ‘Maildir’ instances have all of the methods of *note Mailbox: 11e5.
     in addition to the following:

      -- 方法: list_folders ()

          Return a list of the names of all folders.

      -- 方法: get_folder (folder)

          Return a ‘Maildir’ instance representing the folder whose name
          is 'folder'.  A *note NoSuchMailboxError: 34df. exception is
          raised if the folder does not exist.

      -- 方法: add_folder (folder)

          Create a folder whose name is 'folder' and return a ‘Maildir’
          instance representing it.

      -- 方法: remove_folder (folder)

          Delete the folder whose name is 'folder'.  If the folder
          contains any messages, a *note NotEmptyError: 34e2. exception
          will be raised and the folder will not be deleted.

      -- 方法: clean ()

          Delete temporary files from the mailbox that have not been
          accessed in the last 36 hours.  The Maildir specification says
          that mail-reading programs should do this occasionally.

      -- 方法: get_flags (key)

          Return as a string the flags that are set on the message
          corresponding to 'key'.  This is the same as
          ‘get_message(key).get_flags()’ but much faster, because it
          does not open the message file.  Use this method when
          iterating over the keys to determine which messages are
          interesting to get.

          If you do have a *note MaildirMessage: 34db. object, use its
          *note get_flags(): 34e4. method instead, because changes made
          by the message's *note set_flags(): 34e5, *note add_flag():
          34e6. and *note remove_flag(): 34e7. methods are not reflected
          here until the mailbox's *note __setitem__(): 34e8. method is
          called.

          在 3.13 版被加入.

      -- 方法: set_flags (key, flags)

          On the message corresponding to 'key', set the flags specified
          by 'flags' and unset all others.  Calling
          ‘some_mailbox.set_flags(key, flags)’ is similar to

               one_message = some_mailbox.get_message(key)
               one_message.set_flags(flags)
               some_mailbox[key] = one_message

          but faster, because it does not open the message file.

          If you do have a *note MaildirMessage: 34db. object, use its
          *note set_flags(): 34e5. method instead, because changes made
          with this mailbox method will not be visible to the message
          object's method, *note get_flags(): 34e4.

          在 3.13 版被加入.

      -- 方法: add_flag (key, flag)

          On the message corresponding to 'key', set the flags specified
          by 'flag' without changing other flags.  To add more than one
          flag at a time, 'flag' may be a string of more than one
          character.

          Considerations for using this method versus the message
          object's *note add_flag(): 34e6. method are similar to those
          for *note set_flags(): 15cd.; see the discussion there.

          在 3.13 版被加入.

      -- 方法: remove_flag (key, flag)

          On the message corresponding to 'key', unset the flags
          specified by 'flag' without changing other flags.  To remove
          more than one flag at a time, 'flag' may be a string of more
          than one character.

          Considerations for using this method versus the message
          object's *note remove_flag(): 34e7. method are similar to
          those for *note set_flags(): 15cd.; see the discussion there.

          在 3.13 版被加入.

      -- 方法: get_info (key)

          Return a string containing the info for the message
          corresponding to 'key'.  This is the same as
          ‘get_message(key).get_info()’ but much faster, because it does
          not open the message file.  Use this method when iterating
          over the keys to determine which messages are interesting to
          get.

          If you do have a *note MaildirMessage: 34db. object, use its
          *note get_info(): 34e9. method instead, because changes made
          by the message's *note set_info(): 34ea. method are not
          reflected here until the mailbox's *note __setitem__(): 34e8.
          method is called.

          在 3.13 版被加入.

      -- 方法: set_info (key, info)

          Set the info of the message corresponding to 'key' to 'info'.
          Calling ‘some_mailbox.set_info(key, flags)’ is similar to

               one_message = some_mailbox.get_message(key)
               one_message.set_info(info)
               some_mailbox[key] = one_message

          but faster, because it does not open the message file.

          If you do have a *note MaildirMessage: 34db. object, use its
          *note set_info(): 34ea. method instead, because changes made
          with this mailbox method will not be visible to the message
          object's method, *note get_info(): 34e9.

          在 3.13 版被加入.

     Some *note Mailbox: 11e5. methods implemented by ‘Maildir’ deserve
     special remarks:

      -- 方法: add (message)
      -- 方法: __setitem__ (key, message)
      -- 方法: update (arg)

               警告: These methods generate unique file names based upon
               the current process ID. When using multiple threads,
               undetected name clashes may occur and cause corruption of
               the mailbox unless threads are coordinated to avoid using
               these methods to manipulate the same mailbox
               simultaneously.

      -- 方法: flush ()

          All changes to Maildir mailboxes are immediately applied, so
          this method does nothing.

      -- 方法: lock ()
      -- 方法: unlock ()

          Maildir mailboxes do not support (or require) locking, so
          these methods do nothing.

      -- 方法: close ()

          ‘Maildir’ instances do not keep any open files and the
          underlying mailboxes do not support locking, so this method
          does nothing.

      -- 方法: get_file (key)

          Depending upon the host platform, it may not be possible to
          modify or remove the underlying message while the returned
          file remains open.

也參考
......

maildir man page from Courier(1)

     A specification of the format.  Describes a common extension for
     supporting folders.

Using maildir format(2)

     Notes on Maildir by its inventor.  Includes an updated
     name-creation scheme and details on "info" semantics.

   ---------- Footnotes ----------

   (1) https://www.courier-mta.org/maildir.html

   (2) https://cr.yp.to/proto/maildir.html


File: python.info,  Node: mbox 物件,  Next: MH 物件,  Prev: Mailbox 物件<2>,  Up: Mailbox 物件

5.19.3.3 ‘mbox’ 物件
....................

 -- 類別: mailbox.mbox (path, factory=None, create=True)

     A subclass of *note Mailbox: 11e5. for mailboxes in mbox format.
     Parameter 'factory' is a callable object that accepts a file-like
     message representation (which behaves as if opened in binary mode)
     and returns a custom representation.  If 'factory' is ‘None’, *note
     mboxMessage: 3394. is used as the default message representation.
     If 'create' is ‘True’, the mailbox is created if it does not exist.

     The mbox format is the classic format for storing mail on Unix
     systems.  All messages in an mbox mailbox are stored in a single
     file with the beginning of each message indicated by a line whose
     first five characters are "From ".

     Several variations of the mbox format exist to address perceived
     shortcomings in the original.  In the interest of compatibility,
     ‘mbox’ implements the original format, which is sometimes referred
     to as 'mboxo'.  This means that the ‘Content-Length’ header, if
     present, is ignored and that any occurrences of "From " at the
     beginning of a line in a message body are transformed to ">From "
     when storing the message, although occurrences of ">From " are not
     transformed to "From " when reading the message.

     Some *note Mailbox: 11e5. methods implemented by ‘mbox’ deserve
     special remarks:

      -- 方法: get_file (key)

          Using the file after calling *note flush(): 34d6. or *note
          close(): 34d8. on the ‘mbox’ instance may yield unpredictable
          results or raise an exception.

      -- 方法: lock ()
      -- 方法: unlock ()

          Three locking mechanisms are used--dot locking and, if
          available, the ‘flock()’ and ‘lockf()’ system calls.

也參考
......

mbox man page from tin(1)

     A specification of the format, with details on locking.

Configuring Netscape Mail on Unix: Why The Content-Length Format is Bad(2)

     An argument for using the original mbox format rather than a
     variation.

"mbox" is a family of several mutually incompatible mailbox formats(3)

     A history of mbox variations.

   ---------- Footnotes ----------

   (1) http://www.tin.org/bin/man.cgi?section=5&topic=mbox

   (2) https://www.jwz.org/doc/content-length.html

   (3) 
https://www.loc.gov/preservation/digital/formats/fdd/fdd000383.shtml


File: python.info,  Node: MH 物件,  Next: Babyl 物件,  Prev: mbox 物件,  Up: Mailbox 物件

5.19.3.4 ‘MH’ 物件
..................

 -- 類別: mailbox.MH (path, factory=None, create=True)

     A subclass of *note Mailbox: 11e5. for mailboxes in MH format.
     Parameter 'factory' is a callable object that accepts a file-like
     message representation (which behaves as if opened in binary mode)
     and returns a custom representation.  If 'factory' is ‘None’, *note
     MHMessage: 34f9. is used as the default message representation.  If
     'create' is ‘True’, the mailbox is created if it does not exist.

     MH is a directory-based mailbox format invented for the MH Message
     Handling System, a mail user agent.  Each message in an MH mailbox
     resides in its own file.  An MH mailbox may contain other MH
     mailboxes (called 'folders') in addition to messages.  Folders may
     be nested indefinitely.  MH mailboxes also support 'sequences',
     which are named lists used to logically group messages without
     moving them to sub-folders.  Sequences are defined in a file called
     ‘.mh_sequences’ in each folder.

     The ‘MH’ class manipulates MH mailboxes, but it does not attempt to
     emulate all of ‘mh’'s behaviors.  In particular, it does not modify
     and is not affected by the ‘context’ or ‘.mh_profile’ files that
     are used by ‘mh’ to store its state and configuration.

     ‘MH’ instances have all of the methods of *note Mailbox: 11e5. in
     addition to the following:

     在 3.13 版的變更: Supported folders that don't contain a
     ‘.mh_sequences’ file.

      -- 方法: list_folders ()

          Return a list of the names of all folders.

      -- 方法: get_folder (folder)

          Return an ‘MH’ instance representing the folder whose name is
          'folder'.  A *note NoSuchMailboxError: 34df. exception is
          raised if the folder does not exist.

      -- 方法: add_folder (folder)

          Create a folder whose name is 'folder' and return an ‘MH’
          instance representing it.

      -- 方法: remove_folder (folder)

          Delete the folder whose name is 'folder'.  If the folder
          contains any messages, a *note NotEmptyError: 34e2. exception
          will be raised and the folder will not be deleted.

      -- 方法: get_sequences ()

          Return a dictionary of sequence names mapped to key lists.  If
          there are no sequences, the empty dictionary is returned.

      -- 方法: set_sequences (sequences)

          Re-define the sequences that exist in the mailbox based upon
          'sequences', a dictionary of names mapped to key lists, like
          returned by *note get_sequences(): 34fe.

      -- 方法: pack ()

          Rename messages in the mailbox as necessary to eliminate gaps
          in numbering.  Entries in the sequences list are updated
          correspondingly.

               備註: Already-issued keys are invalidated by this
               operation and should not be subsequently used.

     Some *note Mailbox: 11e5. methods implemented by ‘MH’ deserve
     special remarks:

      -- 方法: remove (key)
      -- 方法: __delitem__ (key)
      -- 方法: discard (key)

          These methods immediately delete the message.  The MH
          convention of marking a message for deletion by prepending a
          comma to its name is not used.

      -- 方法: lock ()
      -- 方法: unlock ()

          Three locking mechanisms are used--dot locking and, if
          available, the ‘flock()’ and ‘lockf()’ system calls.  For MH
          mailboxes, locking the mailbox means locking the
          ‘.mh_sequences’ file and, only for the duration of any
          operations that affect them, locking individual message files.

      -- 方法: get_file (key)

          Depending upon the host platform, it may not be possible to
          remove the underlying message while the returned file remains
          open.

      -- 方法: flush ()

          All changes to MH mailboxes are immediately applied, so this
          method does nothing.

      -- 方法: close ()

          ‘MH’ instances do not keep any open files, so this method is
          equivalent to *note unlock(): 3505.

也參考
......

nmh - Message Handling System(1)

     Home page of ‘nmh’, an updated version of the original ‘mh’.

MH & nmh: Email for Users & Programmers(2)

     A GPL-licensed book on ‘mh’ and ‘nmh’, with some information on the
     mailbox format.

   ---------- Footnotes ----------

   (1) https://www.nongnu.org/nmh/

   (2) https://rand-mh.sourceforge.io/book/


File: python.info,  Node: Babyl 物件,  Next: MMDF 物件,  Prev: MH 物件,  Up: Mailbox 物件

5.19.3.5 ‘Babyl’ 物件
.....................

 -- 類別: mailbox.Babyl (path, factory=None, create=True)

     A subclass of *note Mailbox: 11e5. for mailboxes in Babyl format.
     Parameter 'factory' is a callable object that accepts a file-like
     message representation (which behaves as if opened in binary mode)
     and returns a custom representation.  If 'factory' is ‘None’, *note
     BabylMessage: 350c. is used as the default message representation.
     If 'create' is ‘True’, the mailbox is created if it does not exist.

     Babyl is a single-file mailbox format used by the Rmail mail user
     agent included with Emacs.  The beginning of a message is indicated
     by a line containing the two characters Control-Underscore
     (‘'\037'’) and Control-L (‘'\014'’).  The end of a message is
     indicated by the start of the next message or, in the case of the
     last message, a line containing a Control-Underscore (‘'\037'’)
     character.

     Messages in a Babyl mailbox have two sets of headers, original
     headers and so-called visible headers.  Visible headers are
     typically a subset of the original headers that have been
     reformatted or abridged to be more attractive.  Each message in a
     Babyl mailbox also has an accompanying list of 'labels', or short
     strings that record extra information about the message, and a list
     of all user-defined labels found in the mailbox is kept in the
     Babyl options section.

     ‘Babyl’ instances have all of the methods of *note Mailbox: 11e5.
     in addition to the following:

      -- 方法: get_labels ()

          Return a list of the names of all user-defined labels used in
          the mailbox.

               備註: The actual messages are inspected to determine
               which labels exist in the mailbox rather than consulting
               the list of labels in the Babyl options section, but the
               Babyl section is updated whenever the mailbox is
               modified.

     Some *note Mailbox: 11e5. methods implemented by ‘Babyl’ deserve
     special remarks:

      -- 方法: get_file (key)

          In Babyl mailboxes, the headers of a message are not stored
          contiguously with the body of the message.  To generate a
          file-like representation, the headers and body are copied
          together into an *note io.BytesIO: e46. instance, which has an
          API identical to that of a file.  As a result, the file-like
          object is truly independent of the underlying mailbox but does
          not save memory compared to a string representation.

      -- 方法: lock ()
      -- 方法: unlock ()

          Three locking mechanisms are used--dot locking and, if
          available, the ‘flock()’ and ‘lockf()’ system calls.

也參考
......

Format of Version 5 Babyl Files(1)

     A specification of the Babyl format.

Reading Mail with Rmail(2)

     The Rmail manual, with some information on Babyl semantics.

   ---------- Footnotes ----------

   (1) https://quimby.gnus.org/notes/BABYL

   (2) 
https://www.gnu.org/software/emacs/manual/html_node/emacs/Rmail.html


File: python.info,  Node: MMDF 物件,  Prev: Babyl 物件,  Up: Mailbox 物件

5.19.3.6 ‘MMDF’ 物件
....................

 -- 類別: mailbox.MMDF (path, factory=None, create=True)

     A subclass of *note Mailbox: 11e5. for mailboxes in MMDF format.
     Parameter 'factory' is a callable object that accepts a file-like
     message representation (which behaves as if opened in binary mode)
     and returns a custom representation.  If 'factory' is ‘None’, *note
     MMDFMessage: 3513. is used as the default message representation.
     If 'create' is ‘True’, the mailbox is created if it does not exist.

     MMDF is a single-file mailbox format invented for the Multichannel
     Memorandum Distribution Facility, a mail transfer agent.  Each
     message is in the same form as an mbox message but is bracketed
     before and after by lines containing four Control-A (‘'\001'’)
     characters.  As with the mbox format, the beginning of each message
     is indicated by a line whose first five characters are "From ", but
     additional occurrences of "From " are not transformed to ">From "
     when storing messages because the extra message separator lines
     prevent mistaking such occurrences for the starts of subsequent
     messages.

     Some *note Mailbox: 11e5. methods implemented by ‘MMDF’ deserve
     special remarks:

      -- 方法: get_file (key)

          Using the file after calling *note flush(): 34d6. or *note
          close(): 34d8. on the ‘MMDF’ instance may yield unpredictable
          results or raise an exception.

      -- 方法: lock ()
      -- 方法: unlock ()

          Three locking mechanisms are used--dot locking and, if
          available, the ‘flock()’ and ‘lockf()’ system calls.

也參考
......

mmdf man page from tin(1)

     A specification of MMDF format from the documentation of tin, a
     newsreader.

MMDF(2)

     A Wikipedia article describing the Multichannel Memorandum
     Distribution Facility.

   ---------- Footnotes ----------

   (1) http://www.tin.org/bin/man.cgi?section=5&topic=mmdf

   (2) https://en.wikipedia.org/wiki/MMDF


File: python.info,  Node: Message 物件,  Next: 例外<13>,  Prev: Mailbox 物件,  Up: mailbox --- 以各種格式操作郵件信箱

5.19.3.7 ‘Message’ 物件
.......................

 -- 類別: mailbox.Message (message=None)

     A subclass of the *note email.message: 3b. module's *note Message:
     261.  Subclasses of ‘mailbox.Message’ add mailbox-format-specific
     state and behavior.

     If 'message' is omitted, the new instance is created in a default,
     empty state.  If 'message' is an *note email.message.Message: 261.
     instance, its contents are copied; furthermore, any format-specific
     information is converted insofar as possible if 'message' is a
     ‘Message’ instance.  If 'message' is a string, a byte string, or a
     file, it should contain an RFC 2822(1)-compliant message, which is
     read and parsed.  Files should be open in binary mode, but text
     mode files are accepted for backward compatibility.

     The format-specific state and behaviors offered by subclasses vary,
     but in general it is only the properties that are not specific to a
     particular mailbox that are supported (although presumably the
     properties are specific to a particular mailbox format).  For
     example, file offsets for single-file mailbox formats and file
     names for directory-based mailbox formats are not retained, because
     they are only applicable to the original mailbox.  But state such
     as whether a message has been read by the user or marked as
     important is retained, because it applies to the message itself.

     There is no requirement that ‘Message’ instances be used to
     represent messages retrieved using *note Mailbox: 11e5. instances.
     In some situations, the time and memory required to generate
     ‘Message’ representations might not be acceptable.  For such
     situations, ‘Mailbox’ instances also offer string and file-like
     representations, and a custom message factory may be specified when
     a ‘Mailbox’ instance is initialized.

* Menu:

* MaildirMessage 物件::
* mboxMessage 物件::
* MHMessage 物件::
* BabylMessage 物件::
* MMDFMessage 物件::

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2822.html


File: python.info,  Node: MaildirMessage 物件,  Next: mboxMessage 物件,  Up: Message 物件

5.19.3.8 ‘MaildirMessage’ 物件
..............................

 -- 類別: mailbox.MaildirMessage (message=None)

     A message with Maildir-specific behaviors.  Parameter 'message' has
     the same meaning as with the *note Message: 11e9. constructor.

     Typically, a mail user agent application moves all of the messages
     in the ‘new’ subdirectory to the ‘cur’ subdirectory after the first
     time the user opens and closes the mailbox, recording that the
     messages are old whether or not they've actually been read.  Each
     message in ‘cur’ has an "info" section added to its file name to
     store information about its state.  (Some mail readers may also add
     an "info" section to messages in ‘new’.)  The "info" section may
     take one of two forms: it may contain "2," followed by a list of
     standardized flags (e.g., "2,FR") or it may contain "1," followed
     by so-called experimental information.  Standard flags for Maildir
     messages are as follows:

     Flag       含義          Explanation
                              
     --------------------------------------------------------------
                              
     D          Draft         Under composition
                              
                              
     F          Flagged       Marked as important
                              
                              
     P          Passed        Forwarded, resent, or bounced
                              
                              
     R          Replied       Replied to
                              
                              
     S          Seen          Read
                              
                              
     T          Trashed       Marked for subsequent deletion
                              

     ‘MaildirMessage’ instances offer the following methods:

      -- 方法: get_subdir ()

          Return either "new" (if the message should be stored in the
          ‘new’ subdirectory) or "cur" (if the message should be stored
          in the ‘cur’ subdirectory).

               備註: A message is typically moved from ‘new’ to ‘cur’
               after its mailbox has been accessed, whether or not the
               message has been read.  A message ‘msg’ has been read if
               ‘"S" in msg.get_flags()’ is ‘True’.

      -- 方法: set_subdir (subdir)

          Set the subdirectory the message should be stored in.
          Parameter 'subdir' must be either "new" or "cur".

      -- 方法: get_flags ()

          Return a string specifying the flags that are currently set.
          If the message complies with the standard Maildir format, the
          result is the concatenation in alphabetical order of zero or
          one occurrence of each of ‘'D'’, ‘'F'’, ‘'P'’, ‘'R'’, ‘'S'’,
          and ‘'T'’.  The empty string is returned if no flags are set
          or if "info" contains experimental semantics.

      -- 方法: set_flags (flags)

          Set the flags specified by 'flags' and unset all others.

      -- 方法: add_flag (flag)

          Set the flag(s) specified by 'flag' without changing other
          flags.  To add more than one flag at a time, 'flag' may be a
          string of more than one character.  The current "info" is
          overwritten whether or not it contains experimental
          information rather than flags.

      -- 方法: remove_flag (flag)

          Unset the flag(s) specified by 'flag' without changing other
          flags.  To remove more than one flag at a time, 'flag' maybe a
          string of more than one character.  If "info" contains
          experimental information rather than flags, the current "info"
          is not modified.

      -- 方法: get_date ()

          Return the delivery date of the message as a floating-point
          number representing seconds since the epoch.

      -- 方法: set_date (date)

          Set the delivery date of the message to 'date', a
          floating-point number representing seconds since the epoch.

      -- 方法: get_info ()

          Return a string containing the "info" for a message.  This is
          useful for accessing and modifying "info" that is experimental
          (i.e., not a list of flags).

      -- 方法: set_info (info)

          Set "info" to 'info', which should be a string.

When a ‘MaildirMessage’ instance is created based upon an *note
mboxMessage: 3394. or *note MMDFMessage: 3513. instance, the ‘Status’
and ‘X-Status’ headers are omitted and the following conversions take
place:

Resulting state          *note mboxMessage: 3394. or
                         *note MMDFMessage: 3513. state
                         
----------------------------------------------------------------------------
                         
"cur" subdirectory       O flag
                         
                         
F flag                   F flag
                         
                         
R flag                   A flag
                         
                         
S flag                   R flag
                         
                         
T flag                   D flag
                         

When a ‘MaildirMessage’ instance is created based upon an *note
MHMessage: 34f9. instance, the following conversions take place:

Resulting state                     *note MHMessage: 34f9. state
                                    
-------------------------------------------------------------------
                                    
"cur" subdirectory                  "unseen" sequence
                                    
                                    
"cur" subdirectory and S flag       no "unseen" sequence
                                    
                                    
F flag                              "flagged" sequence
                                    
                                    
R flag                              "replied" sequence
                                    

When a ‘MaildirMessage’ instance is created based upon a *note
BabylMessage: 350c. instance, the following conversions take place:

Resulting state                     *note BabylMessage: 350c. state
                                    
------------------------------------------------------------------------
                                    
"cur" subdirectory                  "unseen" label
                                    
                                    
"cur" subdirectory and S flag       no "unseen" label
                                    
                                    
P flag                              "forwarded" or "resent" label
                                    
                                    
R flag                              "answered" label
                                    
                                    
T flag                              "deleted" label
                                    


File: python.info,  Node: mboxMessage 物件,  Next: MHMessage 物件,  Prev: MaildirMessage 物件,  Up: Message 物件

5.19.3.9 ‘mboxMessage’ 物件
...........................

 -- 類別: mailbox.mboxMessage (message=None)

     A message with mbox-specific behaviors.  Parameter 'message' has
     the same meaning as with the *note Message: 11e9. constructor.

     Messages in an mbox mailbox are stored together in a single file.
     The sender's envelope address and the time of delivery are
     typically stored in a line beginning with "From " that is used to
     indicate the start of a message, though there is considerable
     variation in the exact format of this data among mbox
     implementations.  Flags that indicate the state of the message,
     such as whether it has been read or marked as important, are
     typically stored in ‘Status’ and ‘X-Status’ headers.

     Conventional flags for mbox messages are as follows:

     Flag       含義           Explanation
                               
     ---------------------------------------------------------------
                               
     R          Read           Read
                               
                               
     O          Old            Previously detected by MUA
                               
                               
     D          Deleted        Marked for subsequent deletion
                               
                               
     F          Flagged        Marked as important
                               
                               
     A          Answered       Replied to
                               

     The "R" and "O" flags are stored in the ‘Status’ header, and the
     "D", "F", and "A" flags are stored in the ‘X-Status’ header.  The
     flags and headers typically appear in the order mentioned.

     ‘mboxMessage’ instances offer the following methods:

      -- 方法: get_from ()

          Return a string representing the "From " line that marks the
          start of the message in an mbox mailbox.  The leading "From "
          and the trailing newline are excluded.

      -- 方法: set_from (from_, time_=None)

          Set the "From " line to 'from_', which should be specified
          without a leading "From " or trailing newline.  For
          convenience, 'time_' may be specified and will be formatted
          appropriately and appended to 'from_'.  If 'time_' is
          specified, it should be a *note time.struct_time: c91.
          instance, a tuple suitable for passing to *note
          time.strftime(): 1181, or ‘True’ (to use *note time.gmtime():
          1158.).

      -- 方法: get_flags ()

          Return a string specifying the flags that are currently set.
          If the message complies with the conventional format, the
          result is the concatenation in the following order of zero or
          one occurrence of each of ‘'R'’, ‘'O'’, ‘'D'’, ‘'F'’, and
          ‘'A'’.

      -- 方法: set_flags (flags)

          Set the flags specified by 'flags' and unset all others.
          Parameter 'flags' should be the concatenation in any order of
          zero or more occurrences of each of ‘'R'’, ‘'O'’, ‘'D'’,
          ‘'F'’, and ‘'A'’.

      -- 方法: add_flag (flag)

          Set the flag(s) specified by 'flag' without changing other
          flags.  To add more than one flag at a time, 'flag' may be a
          string of more than one character.

      -- 方法: remove_flag (flag)

          Unset the flag(s) specified by 'flag' without changing other
          flags.  To remove more than one flag at a time, 'flag' maybe a
          string of more than one character.

When an ‘mboxMessage’ instance is created based upon a *note
MaildirMessage: 34db. instance, a "From " line is generated based upon
the *note MaildirMessage: 34db. instance's delivery date, and the
following conversions take place:

Resulting state       *note MaildirMessage: 34db. state
                      
----------------------------------------------------------
                      
R flag                S flag
                      
                      
O flag                "cur" subdirectory
                      
                      
D flag                T flag
                      
                      
F flag                F flag
                      
                      
A flag                R flag
                      

When an ‘mboxMessage’ instance is created based upon an *note MHMessage:
34f9. instance, the following conversions take place:

Resulting state         *note MHMessage: 34f9. state
                        
-------------------------------------------------------
                        
R flag and O flag       no "unseen" sequence
                        
                        
O flag                  "unseen" sequence
                        
                        
F flag                  "flagged" sequence
                        
                        
A flag                  "replied" sequence
                        

When an ‘mboxMessage’ instance is created based upon a *note
BabylMessage: 350c. instance, the following conversions take place:

Resulting state         *note BabylMessage: 350c. state
                        
----------------------------------------------------------
                        
R flag and O flag       no "unseen" label
                        
                        
O flag                  "unseen" label
                        
                        
D flag                  "deleted" label
                        
                        
A flag                  "answered" label
                        

When a ‘mboxMessage’ instance is created based upon an *note
MMDFMessage: 3513. instance, the "From " line is copied and all flags
directly correspond:

Resulting state       *note MMDFMessage: 3513. state
                      
-------------------------------------------------------
                      
R flag                R flag
                      
                      
O flag                O flag
                      
                      
D flag                D flag
                      
                      
F flag                F flag
                      
                      
A flag                A flag
                      


File: python.info,  Node: MHMessage 物件,  Next: BabylMessage 物件,  Prev: mboxMessage 物件,  Up: Message 物件

5.19.3.10 ‘MHMessage’ 物件
..........................

 -- 類別: mailbox.MHMessage (message=None)

     A message with MH-specific behaviors.  Parameter 'message' has the
     same meaning as with the *note Message: 11e9. constructor.

     MH messages do not support marks or flags in the traditional sense,
     but they do support sequences, which are logical groupings of
     arbitrary messages.  Some mail reading programs (although not the
     standard ‘mh’ and ‘nmh’) use sequences in much the same way flags
     are used with other formats, as follows:

     Sequence       Explanation
                    
     --------------------------------------------------------------
                    
     unseen         Not read, but previously detected by MUA
                    
                    
     replied        Replied to
                    
                    
     flagged        Marked as important
                    

     ‘MHMessage’ instances offer the following methods:

      -- 方法: get_sequences ()

          Return a list of the names of sequences that include this
          message.

      -- 方法: set_sequences (sequences)

          Set the list of sequences that include this message.

      -- 方法: add_sequence (sequence)

          Add 'sequence' to the list of sequences that include this
          message.

      -- 方法: remove_sequence (sequence)

          Remove 'sequence' from the list of sequences that include this
          message.

When an ‘MHMessage’ instance is created based upon a *note
MaildirMessage: 34db. instance, the following conversions take place:

Resulting state          *note MaildirMessage: 34db. state
                         
-------------------------------------------------------------
                         
"unseen" sequence        no S flag
                         
                         
"replied" sequence       R flag
                         
                         
"flagged" sequence       F flag
                         

When an ‘MHMessage’ instance is created based upon an *note mboxMessage:
3394. or *note MMDFMessage: 3513. instance, the ‘Status’ and ‘X-Status’
headers are omitted and the following conversions take place:

Resulting state          *note mboxMessage: 3394. or
                         *note MMDFMessage: 3513. state
                         
----------------------------------------------------------------------------
                         
"unseen" sequence        no R flag
                         
                         
"replied" sequence       A flag
                         
                         
"flagged" sequence       F flag
                         

When an ‘MHMessage’ instance is created based upon a *note BabylMessage:
350c. instance, the following conversions take place:

Resulting state          *note BabylMessage: 350c. state
                         
-----------------------------------------------------------
                         
"unseen" sequence        "unseen" label
                         
                         
"replied" sequence       "answered" label
                         


File: python.info,  Node: BabylMessage 物件,  Next: MMDFMessage 物件,  Prev: MHMessage 物件,  Up: Message 物件

5.19.3.11 ‘BabylMessage’ 物件
.............................

 -- 類別: mailbox.BabylMessage (message=None)

     A message with Babyl-specific behaviors.  Parameter 'message' has
     the same meaning as with the *note Message: 11e9. constructor.

     Certain message labels, called 'attributes', are defined by
     convention to have special meanings.  The attributes are as
     follows:

     Label           Explanation
                     
     ---------------------------------------------------------------
                     
     unseen          Not read, but previously detected by MUA
                     
                     
     deleted         Marked for subsequent deletion
                     
                     
     filed           Copied to another file or mailbox
                     
                     
     answered        Replied to
                     
                     
     forwarded       Forwarded
                     
                     
     edited          Modified by the user
                     
                     
     resent          Resent
                     

     By default, Rmail displays only visible headers.  The
     ‘BabylMessage’ class, though, uses the original headers because
     they are more complete.  Visible headers may be accessed explicitly
     if desired.

     ‘BabylMessage’ instances offer the following methods:

      -- 方法: get_labels ()

          Return a list of labels on the message.

      -- 方法: set_labels (labels)

          Set the list of labels on the message to 'labels'.

      -- 方法: add_label (label)

          Add 'label' to the list of labels on the message.

      -- 方法: remove_label (label)

          Remove 'label' from the list of labels on the message.

      -- 方法: get_visible ()

          Return a *note Message: 11e9. instance whose headers are the
          message's visible headers and whose body is empty.

      -- 方法: set_visible (visible)

          Set the message's visible headers to be the same as the
          headers in 'message'.  Parameter 'visible' should be a *note
          Message: 11e9. instance, an *note email.message.Message: 261.
          instance, a string, or a file-like object (which should be
          open in text mode).

      -- 方法: update_visible ()

          When a ‘BabylMessage’ instance's original headers are
          modified, the visible headers are not automatically modified
          to correspond.  This method updates the visible headers as
          follows: each visible header with a corresponding original
          header is set to the value of the original header, each
          visible header without a corresponding original header is
          removed, and any of ‘Date’, ‘From’, ‘Reply-To’, ‘To’, ‘CC’,
          and ‘Subject’ that are present in the original headers but not
          the visible headers are added to the visible headers.

When a ‘BabylMessage’ instance is created based upon a *note
MaildirMessage: 34db. instance, the following conversions take place:

Resulting state         *note MaildirMessage: 34db. state
                        
------------------------------------------------------------
                        
"unseen" label          no S flag
                        
                        
"deleted" label         T flag
                        
                        
"answered" label        R flag
                        
                        
"forwarded" label       P flag
                        

When a ‘BabylMessage’ instance is created based upon an *note
mboxMessage: 3394. or *note MMDFMessage: 3513. instance, the ‘Status’
and ‘X-Status’ headers are omitted and the following conversions take
place:

Resulting state        *note mboxMessage: 3394. or
                       *note MMDFMessage: 3513. state
                       
--------------------------------------------------------------------------
                       
"unseen" label         no R flag
                       
                       
"deleted" label        D flag
                       
                       
"answered" label       A flag
                       

When a ‘BabylMessage’ instance is created based upon an *note MHMessage:
34f9. instance, the following conversions take place:

Resulting state        *note MHMessage: 34f9. state
                       
------------------------------------------------------
                       
"unseen" label         "unseen" sequence
                       
                       
"answered" label       "replied" sequence
                       


File: python.info,  Node: MMDFMessage 物件,  Prev: BabylMessage 物件,  Up: Message 物件

5.19.3.12 ‘MMDFMessage’ 物件
............................

 -- 類別: mailbox.MMDFMessage (message=None)

     A message with MMDF-specific behaviors.  Parameter 'message' has
     the same meaning as with the *note Message: 11e9. constructor.

     As with message in an mbox mailbox, MMDF messages are stored with
     the sender's address and the delivery date in an initial line
     beginning with "From ".  Likewise, flags that indicate the state of
     the message are typically stored in ‘Status’ and ‘X-Status’
     headers.

     Conventional flags for MMDF messages are identical to those of mbox
     message and are as follows:

     Flag       含義           Explanation
                               
     ---------------------------------------------------------------
                               
     R          Read           Read
                               
                               
     O          Old            Previously detected by MUA
                               
                               
     D          Deleted        Marked for subsequent deletion
                               
                               
     F          Flagged        Marked as important
                               
                               
     A          Answered       Replied to
                               

     The "R" and "O" flags are stored in the ‘Status’ header, and the
     "D", "F", and "A" flags are stored in the ‘X-Status’ header.  The
     flags and headers typically appear in the order mentioned.

     ‘MMDFMessage’ instances offer the following methods, which are
     identical to those offered by *note mboxMessage: 3394.:

      -- 方法: get_from ()

          Return a string representing the "From " line that marks the
          start of the message in an mbox mailbox.  The leading "From "
          and the trailing newline are excluded.

      -- 方法: set_from (from_, time_=None)

          Set the "From " line to 'from_', which should be specified
          without a leading "From " or trailing newline.  For
          convenience, 'time_' may be specified and will be formatted
          appropriately and appended to 'from_'.  If 'time_' is
          specified, it should be a *note time.struct_time: c91.
          instance, a tuple suitable for passing to *note
          time.strftime(): 1181, or ‘True’ (to use *note time.gmtime():
          1158.).

      -- 方法: get_flags ()

          Return a string specifying the flags that are currently set.
          If the message complies with the conventional format, the
          result is the concatenation in the following order of zero or
          one occurrence of each of ‘'R'’, ‘'O'’, ‘'D'’, ‘'F'’, and
          ‘'A'’.

      -- 方法: set_flags (flags)

          Set the flags specified by 'flags' and unset all others.
          Parameter 'flags' should be the concatenation in any order of
          zero or more occurrences of each of ‘'R'’, ‘'O'’, ‘'D'’,
          ‘'F'’, and ‘'A'’.

      -- 方法: add_flag (flag)

          Set the flag(s) specified by 'flag' without changing other
          flags.  To add more than one flag at a time, 'flag' may be a
          string of more than one character.

      -- 方法: remove_flag (flag)

          Unset the flag(s) specified by 'flag' without changing other
          flags.  To remove more than one flag at a time, 'flag' maybe a
          string of more than one character.

When an ‘MMDFMessage’ instance is created based upon a *note
MaildirMessage: 34db. instance, a "From " line is generated based upon
the *note MaildirMessage: 34db. instance's delivery date, and the
following conversions take place:

Resulting state       *note MaildirMessage: 34db. state
                      
----------------------------------------------------------
                      
R flag                S flag
                      
                      
O flag                "cur" subdirectory
                      
                      
D flag                T flag
                      
                      
F flag                F flag
                      
                      
A flag                R flag
                      

When an ‘MMDFMessage’ instance is created based upon an *note MHMessage:
34f9. instance, the following conversions take place:

Resulting state         *note MHMessage: 34f9. state
                        
-------------------------------------------------------
                        
R flag and O flag       no "unseen" sequence
                        
                        
O flag                  "unseen" sequence
                        
                        
F flag                  "flagged" sequence
                        
                        
A flag                  "replied" sequence
                        

When an ‘MMDFMessage’ instance is created based upon a *note
BabylMessage: 350c. instance, the following conversions take place:

Resulting state         *note BabylMessage: 350c. state
                        
----------------------------------------------------------
                        
R flag and O flag       no "unseen" label
                        
                        
O flag                  "unseen" label
                        
                        
D flag                  "deleted" label
                        
                        
A flag                  "answered" label
                        

When an ‘MMDFMessage’ instance is created based upon an *note
mboxMessage: 3394. instance, the "From " line is copied and all flags
directly correspond:

Resulting state       *note mboxMessage: 3394. state
                      
-------------------------------------------------------
                      
R flag                R flag
                      
                      
O flag                O flag
                      
                      
D flag                D flag
                      
                      
F flag                F flag
                      
                      
A flag                A flag
                      


File: python.info,  Node: 例外<13>,  Next: 範例<29>,  Prev: Message 物件,  Up: mailbox --- 以各種格式操作郵件信箱

5.19.3.13 例外
..............

The following exception classes are defined in the ‘mailbox’ module:

 -- 例外: mailbox.Error

     The based class for all other module-specific exceptions.

 -- 例外: mailbox.NoSuchMailboxError

     Raised when a mailbox is expected but is not found, such as when
     instantiating a *note Mailbox: 11e5. subclass with a path that does
     not exist (and with the 'create' parameter set to ‘False’), or when
     opening a folder that does not exist.

 -- 例外: mailbox.NotEmptyError

     Raised when a mailbox is not empty but is expected to be, such as
     when deleting a folder that contains messages.

 -- 例外: mailbox.ExternalClashError

     Raised when some mailbox-related condition beyond the control of
     the program causes it to be unable to proceed, such as when failing
     to acquire a lock that another program already holds a lock, or
     when a uniquely generated file name already exists.

 -- 例外: mailbox.FormatError

     Raised when the data in a file cannot be parsed, such as when an
     *note MH: 15ae. instance attempts to read a corrupted
     ‘.mh_sequences’ file.


File: python.info,  Node: 範例<29>,  Prev: 例外<13>,  Up: mailbox --- 以各種格式操作郵件信箱

5.19.3.14 範例
..............

A simple example of printing the subjects of all messages in a mailbox
that seem interesting:

     import mailbox
     for message in mailbox.mbox('~/mbox'):
         subject = message['subject']       # 可能為 None.
         if subject and 'python' in subject.lower():
             print(subject)

To copy all mail from a Babyl mailbox to an MH mailbox, converting all
of the format-specific information that can be converted:

     import mailbox
     destination = mailbox.MH('~/Mail')
     destination.lock()
     for message in mailbox.Babyl('~/RMAIL'):
         destination.add(mailbox.MHMessage(message))
     destination.flush()
     destination.unlock()

This example sorts mail from several mailing lists into different
mailboxes, being careful to avoid mail corruption due to concurrent
modification by other programs, mail loss due to interruption of the
program, or premature termination due to malformed messages in the
mailbox:

     import mailbox
     import email.errors

     list_names = ('python-list', 'python-dev', 'python-bugs')

     boxes = {name: mailbox.mbox('~/email/%s' % name) for name in list_names}
     inbox = mailbox.Maildir('~/Maildir', factory=None)

     for key in inbox.iterkeys():
         try:
             message = inbox[key]
         except email.errors.MessageParseError:
             continue                # The message is malformed. Just leave it.

         for name in list_names:
             list_id = message['list-id']
             if list_id and name in list_id:
                 # Get mailbox to use
                 box = boxes[name]

                 # Write copy to disk before removing original.
                 # If there's a crash, you might duplicate a message, but
                 # that's better than losing a message completely.
                 box.lock()
                 box.add(message)
                 box.flush()
                 box.unlock()

                 # Remove original message
                 inbox.lock()
                 inbox.discard(key)
                 inbox.flush()
                 inbox.unlock()
                 break               # Found destination, so stop looking.

     for box in boxes.itervalues():
         box.close()


File: python.info,  Node: mimetypes --- 將檔案名稱對映到 MIME 類型,  Next: base64 --- Base16、Base32、Base64、Base85 資料編碼,  Prev: mailbox --- 以各種格式操作郵件信箱,  Up: 網際網路資料處理

5.19.4 ‘mimetypes’ -- 將檔案名稱對映到 MIME 類型
------------------------------------------------

'原始碼：'Lib/mimetypes.py(1)

__________________________________________________________________

The *note mimetypes: 82. module converts between a filename or URL and
the MIME type associated with the filename extension.  Conversions are
provided from filename to MIME type and from MIME type to filename
extension; encodings are not supported for the latter conversion.

The module provides one class and a number of convenience functions.
The functions are the normal interface to this module, but some
applications may be interested in the class as well.

The functions described below provide the primary interface for this
module.  If the module has not been initialized, they will call *note
init(): 3545. if they rely on the information *note init(): 3545. sets
up.

 -- 函式: mimetypes.guess_type (url, strict=True)

     Guess the type of a file based on its filename, path or URL, given
     by 'url'.  URL can be a string or a *note path-like object: ac2.

     The return value is a tuple ‘(type, encoding)’ where 'type' is
     ‘None’ if the type can't be guessed (missing or unknown suffix) or
     a string of the form ‘'type/subtype'’, usable for a MIME
     ‘content-type’ header.

     'encoding' is ‘None’ for no encoding or the name of the program
     used to encode (e.g.  ‘compress’ or ‘gzip’).  The encoding is
     suitable for use as a ‘Content-Encoding’ header, 'not' as a
     ‘Content-Transfer-Encoding’ header.  The mappings are table driven.
     Encoding suffixes are case sensitive; type suffixes are first tried
     case sensitively, then case insensitively.

     The optional 'strict' argument is a flag specifying whether the
     list of known MIME types is limited to only the official types
     registered with IANA(2). When 'strict' is ‘True’ (the default),
     only the IANA types are supported; when 'strict' is ‘False’, some
     additional non-standard but commonly used MIME types are also
     recognized.

     在 3.8 版的變更: Added support for 'url' being a *note path-like
     object: ac2.

     在 3.13 版之後被棄用: Passing a file path instead of URL is *note
     soft deprecated: 1ee.  Use *note guess_file_type(): 1ec. for this.

 -- 函式: mimetypes.guess_file_type (path, *, strict=True)

     Guess the type of a file based on its path, given by 'path'.
     Similar to the *note guess_type(): 1ed. function, but accepts a
     path instead of URL. Path can be a string, a bytes object or a
     *note path-like object: ac2.

     在 3.13 版被加入.

 -- 函式: mimetypes.guess_all_extensions (type, strict=True)

     Guess the extensions for a file based on its MIME type, given by
     'type'.  The return value is a list of strings giving all possible
     filename extensions, including the leading dot (‘'.'’).  The
     extensions are not guaranteed to have been associated with any
     particular data stream, but would be mapped to the MIME type 'type'
     by *note guess_type(): 1ed. and *note guess_file_type(): 1ec.

     The optional 'strict' argument has the same meaning as with the
     *note guess_type(): 1ed. function.

 -- 函式: mimetypes.guess_extension (type, strict=True)

     Guess the extension for a file based on its MIME type, given by
     'type'.  The return value is a string giving a filename extension,
     including the leading dot (‘'.'’).  The extension is not guaranteed
     to have been associated with any particular data stream, but would
     be mapped to the MIME type 'type' by *note guess_type(): 1ed. and
     *note guess_file_type(): 1ec.  If no extension can be guessed for
     'type', ‘None’ is returned.

     The optional 'strict' argument has the same meaning as with the
     *note guess_type(): 1ed. function.

Some additional functions and data items are available for controlling
the behavior of the module.

 -- 函式: mimetypes.init (files=None)

     Initialize the internal data structures.  If given, 'files' must be
     a sequence of file names which should be used to augment the
     default type map.  If omitted, the file names to use are taken from
     *note knownfiles: 3547.; on Windows, the current registry settings
     are loaded.  Each file named in 'files' or *note knownfiles: 3547.
     takes precedence over those named before it.  Calling *note init():
     3545. repeatedly is allowed.

     Specifying an empty list for 'files' will prevent the system
     defaults from being applied: only the well-known values will be
     present from a built-in list.

     If 'files' is ‘None’ the internal data structure is completely
     rebuilt to its initial default value.  This is a stable operation
     and will produce the same results when called multiple times.

     在 3.2 版的變更: Previously, Windows registry settings were
     ignored.

 -- 函式: mimetypes.read_mime_types (filename)

     Load the type map given in the file 'filename', if it exists.  The
     type map is returned as a dictionary mapping filename extensions,
     including the leading dot (‘'.'’), to strings of the form
     ‘'type/subtype'’.  If the file 'filename' does not exist or cannot
     be read, ‘None’ is returned.

 -- 函式: mimetypes.add_type (type, ext, strict=True)

     Add a mapping from the MIME type 'type' to the extension 'ext'.
     When the extension is already known, the new type will replace the
     old one.  When the type is already known the extension will be
     added to the list of known extensions.

     When 'strict' is ‘True’ (the default), the mapping will be added to
     the official MIME types, otherwise to the non-standard ones.

 -- 資料: mimetypes.inited

     Flag indicating whether or not the global data structures have been
     initialized.  This is set to ‘True’ by *note init(): 3545.

 -- 資料: mimetypes.knownfiles

     List of type map file names commonly installed.  These files are
     typically named ‘mime.types’ and are installed in different
     locations by different packages.

 -- 資料: mimetypes.suffix_map

     Dictionary mapping suffixes to suffixes.  This is used to allow
     recognition of encoded files for which the encoding and the type
     are indicated by the same extension.  For example, the ‘.tgz’
     extension is mapped to ‘.tar.gz’ to allow the encoding and type to
     be recognized separately.

 -- 資料: mimetypes.encodings_map

     Dictionary mapping filename extensions to encoding types.

 -- 資料: mimetypes.types_map

     Dictionary mapping filename extensions to MIME types.

 -- 資料: mimetypes.common_types

     Dictionary mapping filename extensions to non-standard, but
     commonly found MIME types.

模組的使用範例：

     >>> import mimetypes
     >>> mimetypes.init()
     >>> mimetypes.knownfiles
     ['/etc/mime.types', '/etc/httpd/mime.types', ... ]
     >>> mimetypes.suffix_map['.tgz']
     '.tar.gz'
     >>> mimetypes.encodings_map['.gz']
     'gzip'
     >>> mimetypes.types_map['.tgz']
     'application/x-tar-gz'

* Menu:

* MimeTypes 物件::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/mimetypes.py

   (2) https://www.iana.org/assignments/media-types/media-types.xhtml


File: python.info,  Node: MimeTypes 物件,  Up: mimetypes --- 將檔案名稱對映到 MIME 類型

5.19.4.1 MimeTypes 物件
.......................

The *note MimeTypes: 1469. class may be useful for applications which
may want more than one MIME-type database; it provides an interface
similar to the one of the *note mimetypes: 82. module.

 -- 類別: mimetypes.MimeTypes (filenames=(), strict=True)

     This class represents a MIME-types database.  By default, it
     provides access to the same database as the rest of this module.
     The initial database is a copy of that provided by the module, and
     may be extended by loading additional ‘mime.types’-style files into
     the database using the *note read(): 3550. or *note readfp(): 3551.
     methods.  The mapping dictionaries may also be cleared before
     loading additional data if the default data is not desired.

     The optional 'filenames' parameter can be used to cause additional
     files to be loaded "on top" of the default database.

      -- 屬性: suffix_map

          Dictionary mapping suffixes to suffixes.  This is used to
          allow recognition of encoded files for which the encoding and
          the type are indicated by the same extension.  For example,
          the ‘.tgz’ extension is mapped to ‘.tar.gz’ to allow the
          encoding and type to be recognized separately.  This is
          initially a copy of the global *note suffix_map: 354a. defined
          in the module.

      -- 屬性: encodings_map

          Dictionary mapping filename extensions to encoding types.
          This is initially a copy of the global *note encodings_map:
          354b. defined in the module.

      -- 屬性: types_map

          Tuple containing two dictionaries, mapping filename extensions
          to MIME types: the first dictionary is for the non-standards
          types and the second one is for the standard types.  They are
          initialized by *note common_types: 354d. and *note types_map:
          354c.

      -- 屬性: types_map_inv

          Tuple containing two dictionaries, mapping MIME types to a
          list of filename extensions: the first dictionary is for the
          non-standards types and the second one is for the standard
          types.  They are initialized by *note common_types: 354d. and
          *note types_map: 354c.

      -- 方法: guess_extension (type, strict=True)

          Similar to the *note guess_extension(): 3546. function, using
          the tables stored as part of the object.

      -- 方法: guess_type (url, strict=True)

          Similar to the *note guess_type(): 1ed. function, using the
          tables stored as part of the object.

      -- 方法: guess_file_type (path, *, strict=True)

          Similar to the *note guess_file_type(): 1ec. function, using
          the tables stored as part of the object.

          在 3.13 版被加入.

      -- 方法: guess_all_extensions (type, strict=True)

          Similar to the *note guess_all_extensions(): 1798. function,
          using the tables stored as part of the object.

      -- 方法: read (filename, strict=True)

          Load MIME information from a file named 'filename'.  This uses
          *note readfp(): 3551. to parse the file.

          If 'strict' is ‘True’, information will be added to list of
          standard types, else to the list of non-standard types.

      -- 方法: readfp (fp, strict=True)

          Load MIME type information from an open file 'fp'.  The file
          must have the format of the standard ‘mime.types’ files.

          If 'strict' is ‘True’, information will be added to the list
          of standard types, else to the list of non-standard types.

      -- 方法: read_windows_registry (strict=True)

          Load MIME type information from the Windows registry.

          *note 適用: 1c56.：Windows。

          If 'strict' is ‘True’, information will be added to the list
          of standard types, else to the list of non-standard types.

          在 3.2 版被加入.

      -- 方法: add_type (type, ext, strict=True)

          Add a mapping from the MIME type 'type' to the extension
          'ext'.  When the extension is already known, the new type will
          replace the old one.  When the type is already known the
          extension will be added to the list of known extensions.

          When 'strict' is ‘True’ (the default), the mapping will be
          added to the official MIME types, otherwise to the
          non-standard ones.


File: python.info,  Node: base64 --- Base16、Base32、Base64、Base85 資料編碼,  Next: binascii --- 在二進位制和 ASCII 之間轉換,  Prev: mimetypes --- 將檔案名稱對映到 MIME 類型,  Up: 網際網路資料處理

5.19.5 ‘base64’ -- Base16、Base32、Base64、Base85 資料編碼
----------------------------------------------------------

'原始碼：' Lib/base64.py(1)

__________________________________________________________________

這個模組提供將二進位資料編碼成可顯示 ASCII 字元以及解碼回原始資料的功能
，包括了 RFC 4648(2) 中的 Base16、Base32、Base64 等編碼方式，以及標準
Ascii85、Base85 編碼等。

RFC 4648(3) 編碼適合對二進位資料進行編碼來使得電子郵件、URL 或是 HTTP
POST 內容等傳輸管道安全地傳遞資料。這些編碼演算法與 ‘uuencode’ 並不相同
。

該模組提供了兩個介面。新介面支援將*note 類位元組物件: cd4. 編碼成 ASCII
*note bytes: 1a5.，並將包含 ASCII 的*note 類位元組物件: cd4.或字串解碼為
*note bytes: 1a5.。支援 RFC 4648(4) 中定義的兩種 base-64 字母表（常見和
URL 安全 (URL-safe) 及檔案系統安全 (filesystem-safe) 字母表）。

舊版介面不支援從字串解碼，但它提供對*note 檔案物件: 115b.進行編碼和解碼
的函式。它僅支援 Base64 標準字母表，並且按照 RFC 2045(5) 每 76 個字元添
加換行字元。請注意，如果你需要 RFC 2045(6) 的支援，你可能會需要 *note
email: 32. 函式庫。

在 3.3 版的變更: 新介面的解碼功能現在接受 ASCII-only 的 Unicode 字串。

在 3.4 版的變更: 任何*note 類位元組物件: cd4.現在被該模組中的所有編碼和
解碼函式接受。新增了對 Ascii85/Base85 的支援。

新介面提供：

 -- 函式: base64.b64encode (s, altchars=None)

     使用 Base64 對*note 類位元組物件: cd4. 's' 進行編碼並回傳編碼過的
     *note bytes: 1a5.。

     可選的 'altchars' 必須是一個長度為 2 的*note 類位元組物件: cd4.，用
     來指定替代的字母表，以替換 ‘+’ 和 ‘/’ 字元。這使得應用程式可以生成
     對 URL 或檔案系統安全的 Base64 字串。預設值為 ‘None’，即使用標準的
     Base64 字母表。

     如果 'altchars' 的長度不是 2，可以斷言或引發 *note ValueError:
     1e7.。如果 'altchars' 不是*note 類位元組物件: cd4.，則會引發 *note
     TypeError: 4dd.。

 -- 函式: base64.b64decode (s, altchars=None, validate=False)

     將經過 Base64 編碼的*note 類位元組物件: cd4.或 ASCII 字串 's' 解碼
     ，並回傳解碼後的 *note bytes: 1a5.。

     可選的 'altchars' 必須是長度為 2 的*note 類位元組物件: cd4.或 ASCII
     字串，用於指定替代字母表，取代 ‘+’ 和 ‘/’ 字元。

     如果 's' 填充 (pad) 不正確，將引發 *note binascii.Error: fc9. 例外
     。

     如果 'validate' 為 ‘False’（預設值），在 padding check（填充檢查）
     之前，不屬於標準 base-64 字母表和替代字母表的字元將被丟棄。如果
     'validate' 為 ‘True’，輸入中的這些非字母表字元將導致引發 *note
     binascii.Error: fc9.。

     有關嚴格的 base64 檢查的更多資訊，請參閱 *note
     binascii.a2b_base64(): 1521.。

     如果 'altchars' 的長度不是 2，可能會斷言或引發 *note ValueError:
     1e7.。

 -- 函式: base64.standard_b64encode (s)

     使用標準 Base64 字母表對*note 類位元組物件: cd4. 's' 進行編碼，並回
     傳編碼後的 *note bytes: 1a5.。

 -- 函式: base64.standard_b64decode (s)

     使用標準 Base64 字母表對*note 類位元組物件: cd4.或 ASCII 字串 's' 進
     行解碼，並回傳解碼後的 *note bytes: 1a5.。

 -- 函式: base64.urlsafe_b64encode (s)

     使用 URL 安全和檔案系統安全的字母表對*note 類位元組物件: cd4. 's' 進
     行編碼，該字母表將標準 Base64 字母表中的 ‘+’ 替換為 ‘-’，‘/’ 替換為
     ‘_’，並回傳編碼後的 *note bytes: 1a5.。結果仍可能包含 ‘=’。

 -- 函式: base64.urlsafe_b64decode (s)

     使用 URL 安全和檔案系統安全字母表對*note 類位元組物件: cd4.或 ASCII
     字串 's' 進行解碼，該字母表將標準 Base64 字母表中的 ‘+’ 替換為 ‘-’，
     ‘/’ 替換為 ‘_’，並回傳解碼後的 *note bytes: 1a5.。

 -- 函式: base64.b32encode (s)

     使用 Base32 對*note 類位元組物件: cd4. 's' 進行編碼，並回傳編碼後的
     *note bytes: 1a5.。

 -- 函式: base64.b32decode (s, casefold=False, map01=None)

     解碼經過 Base32 編碼的*note 類位元組物件: cd4.或 ASCII 字串 's'，並
     回傳解碼後的 *note bytes: 1a5.。

     可選的 'casefold' 是一個是否接受小寫字母表作為輸入的旗標。出於安全
     性考量，預設值為 ‘False’。

     RFC 4648(7) 允許將數字 0 選擇性地對應對映為字母 O，並且允許將數字 1
     選擇性地對映為字母 I 或字母 L。當可選的引數 'map01' 不為 ‘None’ 時
     ，指定數字 1 應該對映為哪個字母（當 'map01' 不為 ‘None’ 時，數字 0
     總是對映為字母 O）。出於安全性考量，預設值為 ‘None’，因此不允許在輸
     入中使用數字 0 和 1。

     如果 's' 的填充不正確或輸入中存在非字母表字元，將引發 *note
     binascii.Error: fc9.。

 -- 函式: base64.b32hexencode (s)

     類似於 *note b32encode(): 3562.，但使用在 RFC 4648(8) 中定義的擴展
     十六進位字母表 (Extended Hex Alphabet)。

     在 3.10 版被加入.

 -- 函式: base64.b32hexdecode (s, casefold=False)

     類似於 *note b32encode(): 3562.，但使用在 RFC 4648(9) 中定義的擴展
     十六進位字母表。

     這個版本不允許將數字 0 對映為字母 O ，以及將數字 1 對映為字母 I 或
     字母 L，所有這些字元都包含在擴展十六進位字母表中，並且不能互換使用
     。

     在 3.10 版被加入.

 -- 函式: base64.b16encode (s)

     使用 Base16 對*note 類位元組物件: cd4. 's' 進行編碼，並回傳編碼後的
     *note bytes: 1a5.。

 -- 函式: base64.b16decode (s, casefold=False)

     解碼經過 Base16 編碼的*note 類位元組物件: cd4.或 ASCII 字串 's'，並
     回傳解碼後的 *note bytes: 1a5.。

     可選的 'casefold' 是一個是否接受小寫字母表作為輸入的旗標。出於安全
     性考量，預設值為 ‘False’。

     如果 's' 的填充不正確或輸入中存在非字母表字元，將引發 *note
     binascii.Error: fc9.。

 -- 函式: base64.a85encode (b, *, foldspaces=False, wrapcol=0,
          pad=False, adobe=False)

     使用 Ascii85 對*note 類位元組物件: cd4. 'b' 進行編碼，並回傳編碼後
     的 *note bytes: 1a5.。

     'foldspaces' 是一個可選的旗標，它使用特殊的短序列 'y' 來替代連續的
     4 個空格 (ASCII 0x20)，這是由 'btoa' 支援的功能。這個特性不被「標準
     」的 Ascii85 編碼所支援。

     'wrapcol' 控制輸出是否應該包含換行字元 (‘b'\n'’) 。如果這個值不為零
     ，每行輸出的長度將不超過這個字元長度（不包含後面的換行符號）。

     'pad' 控制是否在編碼之前將輸入填充為 4 的倍數。請注意，‘btoa’ 實作
     始終會填充。

     'adobe' 控制編碼的位元組序列前後是否加上 ‘<~’ 和 ‘~>’，這是 Adobe 實
     作中使用的。

     在 3.4 版被加入.

 -- 函式: base64.a85decode (b, *, foldspaces=False, adobe=False,
          ignorechars=b' \t\n\r\x0b')

     解碼經過 Ascii85 編碼的*note 類位元組物件: cd4.或 ASCII 字串 'b'，
     並回傳解碼後的 *note bytes: 1a5.。

     'foldspaces' 是一個旗標，指定是否應該將短序列 'y' 視為 4 個連續的空
     格 (ASCII 0x20) 的簡寫。這個功能不受「標準」Ascii85 編碼的支援。

     'adobe' 控制輸入序列是否符合 Adobe Ascii85 格式（即前後加上 ‘<~’ 和
     ‘~>’）。

     'ignorechars' 是一個包含要從輸入中忽略的字元的*note 類位元組物件:
     cd4.或 ASCII 字串。這只包含空格字元，預設情況下包含 ASCII 中的所有
     空格字元。

     在 3.4 版被加入.

 -- 函式: base64.b85encode (b, pad=False)

     使用 Base85（例如，git 風格的二進位差異 (binary diff)）對*note
     類位元組物件: cd4. 'b' 進行編碼，並回傳編碼後的 *note bytes: 1a5.。

     如果 'pad' 為 true，則在編碼之前，輸入將使用 ‘b'\0'’ 進行填充，以使
     其長度為 4 的倍數。

     在 3.4 版被加入.

 -- 函式: base64.b85decode (b)

     解碼經過 base85 編碼的*note 類位元組物件: cd4.或 ASCII 字串 'b'，並
     回傳解碼後的 *note bytes: 1a5.。必要時會隱式移除填充。

     在 3.4 版被加入.

 -- 函式: base64.z85encode (s)

     Encode the *note bytes-like object: cd4. 's' using Z85 (as used in
     ZeroMQ) and return the encoded *note bytes: 1a5.  See Z85
     specification(10) for more information.

     在 3.13 版被加入.

 -- 函式: base64.z85decode (s)

     Decode the Z85-encoded *note bytes-like object: cd4. or ASCII
     string 's' and return the decoded *note bytes: 1a5.  See Z85
     specification(11) for more information.

     在 3.13 版被加入.

舊版介面：

 -- 函式: base64.decode (input, output)

     解碼二進位檔案 'input' 的內容，並將結果的二進位資料寫入 'output' 檔
     案。 'input' 和 'output' 必須是*note 檔案物件: 115b.。'input' 將被
     讀取，直到 ‘input.readline()’ 回傳一個空的 bytes 物件為止。

 -- 函式: base64.decodebytes (s)

     解碼必須包含一行或多行的 base64 編碼資料*note 類位元組物件: cd4.
     's'，並回傳解碼後的 *note bytes: 1a5.。

     在 3.1 版被加入.

 -- 函式: base64.encode (input, output)

     編碼二進位檔案 'input' 的內容，並將結果的 base64 編碼資料寫入
     'output' 檔案。'input' 和 'output' 必須是*note 檔案物件: 115b.。
     'input' 將被讀取，直到 ‘input.read()’ 回傳一個空的 bytes 物件為止。
     *note encode(): 3566. 會在輸出的每 76 個位元組之後插入一個換行字元
     (‘b'\n'’)，並確保輸出始終以換行字元結尾，符合 RFC 2045(12) (MIME) 的
     規定。

 -- 函式: base64.encodebytes (s)

     對包含任意二進位資料的*note 類位元組物件: cd4. 's' 進行編碼，並回傳
     包含 base64 編碼資料 *note bytes: 1a5.，在每 76 個輸出位元組後插入
     換行字元 (‘b'\n'’) ，並確保有尾隨換行字元，符合 RFC 2045(13) (MIME)
     的規定。

     在 3.1 版被加入.

模組的一個範例用法：

     >>> import base64
     >>> encoded = base64.b64encode(b'data to be encoded')
     >>> encoded
     b'ZGF0YSB0byBiZSBlbmNvZGVk'
     >>> data = base64.b64decode(encoded)
     >>> data
     b'data to be encoded'

* Menu:

* 安全性注意事項: 安全性注意事項<2>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/base64.py

   (2) https://datatracker.ietf.org/doc/html/rfc4648.html

   (3) https://datatracker.ietf.org/doc/html/rfc4648.html

   (4) https://datatracker.ietf.org/doc/html/rfc4648.html

   (5) https://datatracker.ietf.org/doc/html/rfc2045.html

   (6) https://datatracker.ietf.org/doc/html/rfc2045.html

   (7) https://datatracker.ietf.org/doc/html/rfc4648.html

   (8) https://datatracker.ietf.org/doc/html/rfc4648.html

   (9) https://datatracker.ietf.org/doc/html/rfc4648.html

   (10) https://rfc.zeromq.org/spec/32/

   (11) https://rfc.zeromq.org/spec/32/

   (12) https://datatracker.ietf.org/doc/html/rfc2045.html

   (13) https://datatracker.ietf.org/doc/html/rfc2045.html


File: python.info,  Node: 安全性注意事項<2>,  Up: base64 --- Base16、Base32、Base64、Base85 資料編碼

5.19.5.1 安全性注意事項
.......................

RFC 4648(1)（第 12 節）中添加了一個新的安全性考量部分；建議對部署到正式
環境的任何程式碼進行安全性部分的審查。

也參考
......

*note binascii: c. 模組

     支援模組中包含 ASCII 到二進位 (ASCII-to-binary) 和二進位到 ASCII
     (binary-to-ASCII) 的轉換功能。

RFC 1521(2) - MIME（多用途網際網路郵件擴展）第一部分：指定和描述網際網路主體格式的機制。

     第 5.2 節，"Base64 Content-Transfer-Encoding"，提供了 base64 編碼的
     定義。

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc4648.html

   (2) https://datatracker.ietf.org/doc/html/rfc1521.html


File: python.info,  Node: binascii --- 在二進位制和 ASCII 之間轉換,  Next: quopri --- 編碼和解碼 MIME 可列印字元資料,  Prev: base64 --- Base16、Base32、Base64、Base85 資料編碼,  Up: 網際網路資料處理

5.19.6 ‘binascii’ -- 在二進位制和 ASCII 之間轉換
------------------------------------------------

__________________________________________________________________

The *note binascii: c. module contains a number of methods to convert
between binary and various ASCII-encoded binary representations.
Normally, you will not use these functions directly but use wrapper
modules like *note base64: a. instead.  The *note binascii: c. module
contains low-level functions written in C for greater speed that are
used by the higher-level modules.

     備註: ‘a2b_*’ functions accept Unicode strings containing only
     ASCII characters.  Other functions only accept *note bytes-like
     objects: cd4. (such as *note bytes: 1a5, *note bytearray: 4e3. and
     other objects that support the buffer protocol).

     在 3.3 版的變更: ASCII-only unicode strings are now accepted by the
     ‘a2b_*’ functions.

The *note binascii: c. module defines the following functions:

 -- 函式: binascii.a2b_uu (string)

     Convert a single line of uuencoded data back to binary and return
     the binary data.  Lines normally contain 45 (binary) bytes, except
     for the last line.  Line data may be followed by whitespace.

 -- 函式: binascii.b2a_uu (data, *, backtick=False)

     Convert binary data to a line of ASCII characters, the return value
     is the converted line, including a newline char.  The length of
     'data' should be at most 45.  If 'backtick' is true, zeros are
     represented by ‘'`'’ instead of spaces.

     在 3.7 版的變更: 新增 'backtick' 參數。

 -- 函式: binascii.a2b_base64 (string, /, *, strict_mode=False)

     Convert a block of base64 data back to binary and return the binary
     data.  More than one line may be passed at a time.

     If 'strict_mode' is true, only valid base64 data will be converted.
     Invalid base64 data will raise *note binascii.Error: fc9.

     Valid base64:

        * Conforms to RFC 3548(1).

        * Contains only characters from the base64 alphabet.

        * Contains no excess data after padding (including excess
          padding, newlines, etc.).

        * Does not start with a padding.

     在 3.11 版的變更: 新增 'strict_mode' 參數。

 -- 函式: binascii.b2a_base64 (data, *, newline=True)

     Convert binary data to a line of ASCII characters in base64 coding.
     The return value is the converted line, including a newline char if
     'newline' is true.  The output of this function conforms to RFC
     3548(2).

     在 3.6 版的變更: 新增 'newline' 參數。

 -- 函式: binascii.a2b_qp (data, header=False)

     Convert a block of quoted-printable data back to binary and return
     the binary data.  More than one line may be passed at a time.  If
     the optional argument 'header' is present and true, underscores
     will be decoded as spaces.

 -- 函式: binascii.b2a_qp (data, quotetabs=False, istext=True,
          header=False)

     Convert binary data to a line(s) of ASCII characters in
     quoted-printable encoding.  The return value is the converted
     line(s).  If the optional argument 'quotetabs' is present and true,
     all tabs and spaces will be encoded.  If the optional argument
     'istext' is present and true, newlines are not encoded but trailing
     whitespace will be encoded.  If the optional argument 'header' is
     present and true, spaces will be encoded as underscores per RFC
     1522(3).  If the optional argument 'header' is present and false,
     newline characters will be encoded as well; otherwise linefeed
     conversion might corrupt the binary data stream.

 -- 函式: binascii.crc_hqx (data, value)

     Compute a 16-bit CRC value of 'data', starting with 'value' as the
     initial CRC, and return the result.  This uses the CRC-CCITT
     polynomial 'x'^16 + 'x'^12 + 'x'^5 + 1, often represented as
     0x1021.  This CRC is used in the binhex4 format.

 -- 函式: binascii.crc32 (data[, value])

     Compute CRC-32, the unsigned 32-bit checksum of 'data', starting
     with an initial CRC of 'value'.  The default initial CRC is zero.
     The algorithm is consistent with the ZIP file checksum.  Since the
     algorithm is designed for use as a checksum algorithm, it is not
     suitable for use as a general hash algorithm.  Use as follows:

          print(binascii.crc32(b"hello world"))
          # Or, in two pieces:
          crc = binascii.crc32(b"hello")
          crc = binascii.crc32(b" world", crc)
          print('crc32 = {:#010x}'.format(crc))

     在 3.0 版的變更: The result is always unsigned.

 -- 函式: binascii.b2a_hex (data[, sep[, bytes_per_sep=1]])
 -- 函式: binascii.hexlify (data[, sep[, bytes_per_sep=1]])

     Return the hexadecimal representation of the binary 'data'.  Every
     byte of 'data' is converted into the corresponding 2-digit hex
     representation.  The returned bytes object is therefore twice as
     long as the length of 'data'.

     Similar functionality (but returning a text string) is also
     conveniently accessible using the *note bytes.hex(): d0f. method.

     If 'sep' is specified, it must be a single character str or bytes
     object.  It will be inserted in the output after every
     'bytes_per_sep' input bytes.  Separator placement is counted from
     the right end of the output by default, if you wish to count from
     the left, supply a negative 'bytes_per_sep' value.

          >>> import binascii
          >>> binascii.b2a_hex(b'\xb9\x01\xef')
          b'b901ef'
          >>> binascii.hexlify(b'\xb9\x01\xef', '-')
          b'b9-01-ef'
          >>> binascii.b2a_hex(b'\xb9\x01\xef', b'_', 2)
          b'b9_01ef'
          >>> binascii.b2a_hex(b'\xb9\x01\xef', b' ', -2)
          b'b901 ef'

     在 3.8 版的變更: 新增 'sep' 與 'bytes_per_sep' 參數。

 -- 函式: binascii.a2b_hex (hexstr)
 -- 函式: binascii.unhexlify (hexstr)

     Return the binary data represented by the hexadecimal string
     'hexstr'.  This function is the inverse of *note b2a_hex(): 22f0.
     'hexstr' must contain an even number of hexadecimal digits (which
     can be upper or lower case), otherwise an *note Error: fc9.
     exception is raised.

     Similar functionality (accepting only text string arguments, but
     more liberal towards whitespace) is also accessible using the *note
     bytes.fromhex(): a92. class method.

 -- 例外: binascii.Error

     Exception raised on errors.  These are usually programming errors.

 -- 例外: binascii.Incomplete

     Exception raised on incomplete data.  These are usually not
     programming errors, but may be handled by reading a little more
     data and trying again.

也參考
......

*note base64: a. 模組

     Support for RFC compliant base64-style encoding in base 16, 32, 64,
     and 85.

*note quopri: a5. 模組

     Support for quoted-printable encoding used in MIME email messages.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc3548.html

   (2) https://datatracker.ietf.org/doc/html/rfc3548.html

   (3) https://datatracker.ietf.org/doc/html/rfc1522.html


File: python.info,  Node: quopri --- 編碼和解碼 MIME 可列印字元資料,  Prev: binascii --- 在二進位制和 ASCII 之間轉換,  Up: 網際網路資料處理

5.19.7 ‘quopri’ -- 編碼和解碼 MIME 可列印字元資料
-------------------------------------------------

'原始碼：'Lib/quopri.py(1)

__________________________________________________________________

該模組根據 RFC 1521(2)：「MIME（多功能網際網路郵件擴充）第一部分：指定和
描述網際網路訊息正文格式的機制」中的定義來執行可列印字元
(quoted-printable) 傳輸編碼和解碼。可列印字元編碼是為不可列印字元相對較
少的資料而設計的；如果存在許多此類字元（例如發送圖形檔案時），則透過
*note base64: a. 模組提供的 Base64 編碼方案會更加簡潔。

 -- 函式: quopri.decode (input, output, header=False)

     解碼 'input' 檔案的內容並將解碼後的二進位資料寫入 'output' 檔案。
     'input' 和 'output' 必須是*note 二進位檔案物件: 115b.。如果可選參數
     'header' 存在且為 true，則底線將被解碼為空格。這用於解碼如 RFC
     1522(3)：「MIME（多功能網際網路郵件擴充）第二部分：非 ASCII 文字的
     訊息標頭擴充」中所述的 "Q" 編碼標頭。

 -- 函式: quopri.encode (input, output, quotetabs, header=False)

     對 'input' 檔案的內容進行編碼，並將生成的可列印字元資料寫入
     'output' 檔案。 'input' 和 'output' 必須是*note 二進位檔案物件:
     115b.。 'quotetabs'，一個非可選旗標，控制是否對嵌入的空格和製表符號
     (tab) 進行編碼；當為 true 時，它將對此類嵌入的空白進行編碼，當為
     false 時，它將不對它們進行編碼。請注意，出現在列尾的空格和製表符號
     都會按照 RFC 1521(4) 進行編碼。 'header' 是一個旗標，用於控制空格是
     否按照 RFC 1522(5) 編碼為底線。

 -- 函式: quopri.decodestring (s, header=False)

     與 *note decode(): 22f3. 類似，不同之處在於它接受來源的 *note
     bytes: 1a5. 並回傳相應的已解碼 *note bytes: 1a5.。

 -- 函式: quopri.encodestring (s, quotetabs=False, header=False)

     與 *note encode(): 22f2. 類似，不同之處在於它接受來源的 *note
     bytes: 1a5. 並回傳相應的已編碼 *note bytes: 1a5.。預設情況下，它向
     *note encode(): 22f2. 函式的 'quotetabs' 參數發送一個 ‘False’ 值。

也參考
......

*note base64: a. 模組

     對 MIME Base64 資料進行編碼和解碼

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/quopri.py

   (2) https://datatracker.ietf.org/doc/html/rfc1521.html

   (3) https://datatracker.ietf.org/doc/html/rfc1522.html

   (4) https://datatracker.ietf.org/doc/html/rfc1521.html

   (5) https://datatracker.ietf.org/doc/html/rfc1522.html


File: python.info,  Node: Structured Markup Processing Tools,  Next: 網路協定 Internet protocols 及支援,  Prev: 網際網路資料處理,  Up: Python 標準函式庫 Standard Library

5.20 Structured Markup Processing Tools
=======================================

Python supports a variety of modules to work with various forms of
structured data markup.  This includes modules to work with the Standard
Generalized Markup Language (SGML) and the Hypertext Markup Language
(HTML), and several interfaces for working with the Extensible Markup
Language (XML).

* Menu:

* html: html --- 超連結標記語言 HTML 支援. 超連結標記語言 (HTML) 支援
* html.parser: html parser --- 簡單的 HTML 和 XHTML 剖析器. 簡單的 HTML 和 XHTML 剖析器
* html.entities: html entities --- HTML 一般實體的定義. HTML 一般實體的定義
* XML 處理模組::
* xml.etree.cElementTree: xml etree cElementTree --- ElementTree XML API. ElementTree XML API
* xml.dom: xml dom --- Document 物件模型 API. Document 物件模型 API
* xml.dom.minidom: xml dom minidom --- 最小的 DOM 實作. 最小的 DOM 實作
* xml.dom.pulldom: xml dom pulldom --- 支援建置部分 DOM 樹. 支援建置部分 DOM 樹
* xml.sax: xml sax --- SAX2 剖析器支援. SAX2 剖析器支援
* xml.sax.handler: xml sax handler --- SAX 處理函式的基本類別. SAX 處理函式的基本類別
* xml.sax.saxutils: xml sax saxutils --- SAX 工具程式. SAX 工具程式
* xml.sax.xmlreader: xml sax xmlreader --- XML 剖析器的介面. XML 剖析器的介面
* xml.parsers.expat: xml parsers expat --- 使用 Expat 進行快速 XML 剖析. 使用 Expat 進行快速 XML 剖析


File: python.info,  Node: html --- 超連結標記語言 HTML 支援,  Next: html parser --- 簡單的 HTML 和 XHTML 剖析器,  Up: Structured Markup Processing Tools

5.20.1 ‘html’ -- 超連結標記語言 (HTML) 支援
-------------------------------------------

'原始碼：'Lib/html/__init__.py(1)

__________________________________________________________________

此模組定義了操作 HTML 的工具。

 -- 函式: html.escape (s, quote=True)

     將字串 's' 中的 ‘&’、‘<’ 和 ‘>’ 字元轉換為在 HTML 中安全的序列
     (sequence)。如果你需要在 HTML 中顯示可能包含這些字元的文字，可以使
     用這個函式。如果選擇性的旗標 'quote' 為 true，則 (‘"’) 與 (‘'’) 字
     元也會被轉換；這樣能包含在 HTML 中，被引號分隔的屬性值，如 ‘<a
     href="...">’ 。

     在 3.2 版被加入.

 -- 函式: html.unescape (s)

     將字串 's' 中所有附名 (named) 且為數值的 (numeric) 字元參照（如：
     ‘&gt;’、 ‘&#62;’、‘&#x3e;’ ）轉換為對應的 Unicode 字元。此函式針對
     有效及無效的字元參照，皆使用 HTML 5 標準所定義的規則，以及 *note
     HTML 5 附名字元參照清單: 106c. 。

     在 3.4 版被加入.

__________________________________________________________________

‘html’ 套件中的子模組為：

   * *note html.parser: 63. - 帶有寬鬆剖析模式的 HTML/XHTML 剖析器

   * *note html.entities: 62. - HTML 實體的定義

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/html/__init__.py


File: python.info,  Node: html parser --- 簡單的 HTML 和 XHTML 剖析器,  Next: html entities --- HTML 一般實體的定義,  Prev: html --- 超連結標記語言 HTML 支援,  Up: Structured Markup Processing Tools

5.20.2 ‘html.parser’ -- 簡單的 HTML 和 XHTML 剖析器
---------------------------------------------------

'原始碼：'Lib/html/parser.py(1)

__________________________________________________________________

該模組定義了一個類別 *note HTMLParser: 81a.，是剖析 (parse) HTML（
HyperText Mark-up Language、超文本標記語言）和 XHTML 格式文本檔案的基礎
。

 -- 類別: html.parser.HTMLParser (*, convert_charrefs=True)

     建立一個能夠剖析無效標記的剖析器實例。

     如果 'convert_charrefs' 為 ‘True’ （預設值），所有字元參照
     (reference)（ ‘script’/‘style’ 元素中的參照除外）將自動轉換為相應的
     Unicode 字元。

     *note HTMLParser: 81a. 實例被提供 HTML 資料，並在遇到開始標籤、結束
     標籤、文本、註解和其他標記元素時呼叫處理程式 (handler) 方法。使用者
     應該繼承 *note HTMLParser: 81a. 並覆蓋其方法以實作所需的行為。

     此剖析器不檢查結束標籤是否與開始標籤匹配，也不會為透過結束外部元素
     來隱晦地被結束的元素呼叫結束標籤處理程式。

     在 3.4 版的變更: 新增關鍵字引數 'convert_charrefs'。

     在 3.5 版的變更: 引數 'convert_charrefs' 的預設值現在是 ‘True’。

* Menu:

* HTML 剖析器應用程式範例::
* HTMLParser 方法::
* 範例: 範例<30>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/html/parser.py


File: python.info,  Node: HTML 剖析器應用程式範例,  Next: HTMLParser 方法,  Up: html parser --- 簡單的 HTML 和 XHTML 剖析器

5.20.2.1 HTML 剖析器應用程式範例
................................

以下的基礎範例是一個簡單的 HTML 剖析器，它使用 *note HTMLParser: 81a. 類
別，當遇到開始標籤、結束標籤和資料時將它們印出：

     from html.parser import HTMLParser

     class MyHTMLParser(HTMLParser):
         def handle_starttag(self, tag, attrs):
             print("Encountered a start tag:", tag)

         def handle_endtag(self, tag):
             print("Encountered an end tag :", tag)

         def handle_data(self, data):
             print("Encountered some data  :", data)

     parser = MyHTMLParser()
     parser.feed('<html><head><title>Test</title></head>'
                 '<body><h1>Parse me!</h1></body></html>')

輸出將是：

     Encountered a start tag: html
     Encountered a start tag: head
     Encountered a start tag: title
     Encountered some data  : Test
     Encountered an end tag : title
     Encountered an end tag : head
     Encountered a start tag: body
     Encountered a start tag: h1
     Encountered some data  : Parse me!
     Encountered an end tag : h1
     Encountered an end tag : body
     Encountered an end tag : html


File: python.info,  Node: HTMLParser 方法,  Next: 範例<30>,  Prev: HTML 剖析器應用程式範例,  Up: html parser --- 簡單的 HTML 和 XHTML 剖析器

5.20.2.2 ‘HTMLParser’ 方法
..........................

*note HTMLParser: 81a. 實例具有以下方法：

 -- 方法: HTMLParser.feed (data)

     向剖析器提供一些文本。只要它由完整的元素組成，它就會被處理；不完整
     的資料會被緩衝，直到輸入更多資料或呼叫 *note close(): 357e.。
     'data' 必須是 *note str: 3f2.。

 -- 方法: HTMLParser.close ()

     強制處理所有緩衝資料，如同它後面跟有文件結束標籤一樣。此方法可能有
     被衍生類別重新定義，以在輸入末尾定義額外的處理，但重新定義的版本仍
     應要呼叫 *note HTMLParser: 81a. 基底類別方法 *note close(): 357e.。

 -- 方法: HTMLParser.reset ()

     重置實例。丟棄所有未處理的資料。這在實例化時被會隱晦地呼叫。

 -- 方法: HTMLParser.getpos ()

     回傳當前列號 (line number) 和偏移量 (offset)。

 -- 方法: HTMLParser.get_starttag_text ()

     回傳最近開啟 (open) 的開始標籤的文本。這對於結構化處理通常不必要，
     但在處理「已部署」的 HTML 或以最少的更改重新生成輸入（可以保留屬性
     之間的空白等）時可能很有用。

當遇到資料或標記元素時將呼叫以下方法，並且它們應在子類別中被覆蓋。基底類
別實作什麼都不做（除了 *note handle_startendtag(): 3582.）：

 -- 方法: HTMLParser.handle_starttag (tag, attrs)

     呼叫此方法來處理元素的開始標籤（例如 ‘<div id="main">’）。

     'tag' 引數是轉換為小寫的標籤名稱。 'attrs' 引數是一個 ‘(name,
     value)’ 對的列表，包含在標籤的 ‘<>’ 括號內找到的屬性。 'name' 將被
     轉成小寫，'value' 中的引號會被刪除，字元和實體參照也會被替換。

     例如，對於標籤 ‘<A HREF="https://www.cwi.nl/">’，這個方法會以
     ‘handle_starttag('a', [('href', 'https://www.cwi.nl/')])’ 的形式被
     呼叫。

     在屬性值中來自 *note html.entities: 62. 的所有實體參照都會被替換。

 -- 方法: HTMLParser.handle_endtag (tag)

     呼叫此方法來處理元素的結束標籤（例如 ‘</div>’）。

     'tag' 引數是轉換為小寫的標籤名稱。

 -- 方法: HTMLParser.handle_startendtag (tag, attrs)

     與 *note handle_starttag(): 3583. 類似，但在剖析器遇到 XHTML 樣式的
     空標籤 (‘<img ... />’) 時呼叫。這個方法可能被需要這個特定詞彙資訊
     (lexical information) 的子類別覆蓋；預設實作只是呼叫 *note
     handle_starttag(): 3583. 和 *note handle_endtag(): 3584.。

 -- 方法: HTMLParser.handle_data (data)

     呼叫此方法來處理任意資料（例如文本節點與 ‘<script>...</script>’ 和
     ‘<style>...</style>’ 的內容）。

 -- 方法: HTMLParser.handle_entityref (name)

     呼叫此方法來處理形式為 ‘&name;’ （例如 ‘&gt;’）的附名字元參照，其中
     'name' 是一般實體參照（例如 ‘'gt'’）。如果 'convert_charrefs' 為
     ‘True’，則永遠不會呼叫此方法。

 -- 方法: HTMLParser.handle_charref (name)

     呼叫此方法來處理 ‘&#NNN;’ 和 ‘&#xNNN;’ 形式的十進位和十六進位數字字
     元參照。例如，‘&gt;’ 的十進位等效為 ‘&#62;’，而十六進位為 ‘&#x3E;’；
     在這種情況下，該方法將收到 ‘'62'’ 或 ‘'x3E'’。如果
     'convert_charrefs' 為 ‘True’，則永遠不會呼叫此方法。

 -- 方法: HTMLParser.handle_comment (data)

     當遇到註解時呼叫此方法（例如 ‘<!--comment-->’）。

     舉例來說，註解 ‘<!-- comment -->’ 會使得此方法被以引數 ‘' comment
     '’ 來呼叫。

     Internet Explorer 條件式註解（conditional comments, condcoms）的內
     容也會被發送到這個方法，故以 ‘<!--[if IE 9]>IE9-specific
     content<![endif]-->’ 為例，這個方法將會收到 ‘'[if IE
     9]>IE9-specific content<![endif]'’。

 -- 方法: HTMLParser.handle_decl (decl)

     呼叫此方法來處理 HTML 文件類型聲明 (doctype declaration)（例如
     ‘<!DOCTYPE html>’）。

     'decl' 參數將是 ‘<!...>’ 標記內聲明部分的全部內容（例如 ‘'DOCTYPE
     html'’）。

 -- 方法: HTMLParser.handle_pi (data)

     遇到處理指示 (processing instruction) 時會呼叫的方法。 'data' 參數
     將包含整個處理指示。例如，對於處理指示 ‘<?proc color='red'>’，這個
     方法將以 ‘handle_pi("proc color='red'")’ 形式被呼叫。它旨在被衍生類
     別覆蓋；基底類別實作中什麼都不做。

          備註: *note HTMLParser: 81a. 類別使用 SGML 語法規則來處理指示
          。使用有 ‘?’ 跟隨在後面的 XHTML 處理指示將導致 ‘?’ 被包含在
          'data' 中。

 -- 方法: HTMLParser.unknown_decl (data)

     當剖析器讀取無法識別的聲明時會呼叫此方法。

     'data' 參數將是 ‘<![...]>’ 標記內聲明的全部內容。有時被衍生類別被覆
     蓋會是好用的。在基底類別實作中什麼都不做。


File: python.info,  Node: 範例<30>,  Prev: HTMLParser 方法,  Up: html parser --- 簡單的 HTML 和 XHTML 剖析器

5.20.2.3 範例
.............

以下類別實作了一個剖析器，將用於解說更多範例：

     from html.parser import HTMLParser
     from html.entities import name2codepoint

     class MyHTMLParser(HTMLParser):
         def handle_starttag(self, tag, attrs):
             print("Start tag:", tag)
             for attr in attrs:
                 print("     attr:", attr)

         def handle_endtag(self, tag):
             print("End tag  :", tag)

         def handle_data(self, data):
             print("Data     :", data)

         def handle_comment(self, data):
             print("Comment  :", data)

         def handle_entityref(self, name):
             c = chr(name2codepoint[name])
             print("Named ent:", c)

         def handle_charref(self, name):
             if name.startswith('x'):
                 c = chr(int(name[1:], 16))
             else:
                 c = chr(int(name))
             print("Num ent  :", c)

         def handle_decl(self, data):
             print("Decl     :", data)

     parser = MyHTMLParser()

剖析文件類型：

     >>> parser.feed('<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" '
     ...             '"http://www.w3.org/TR/html4/strict.dtd">')
     Decl     : DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"

剖析一個具有一些屬性和標題的元素：

     >>> parser.feed('<img src="python-logo.png" alt="The Python logo">')
     Start tag: img
          attr: ('src', 'python-logo.png')
          attr: ('alt', 'The Python logo')
     >>>
     >>> parser.feed('<h1>Python</h1>')
     Start tag: h1
     Data     : Python
     End tag  : h1

‘script’ 和 ‘style’ 元素的內容按原樣回傳，無需進一步剖析：

     >>> parser.feed('<style type="text/css">#python { color: green }</style>')
     Start tag: style
          attr: ('type', 'text/css')
     Data     : #python { color: green }
     End tag  : style

     >>> parser.feed('<script type="text/javascript">'
     ...             'alert("<strong>hello!</strong>");</script>')
     Start tag: script
          attr: ('type', 'text/javascript')
     Data     : alert("<strong>hello!</strong>");
     End tag  : script

剖析註解：

     >>> parser.feed('<!-- a comment -->'
     ...             '<!--[if IE 9]>IE-specific content<![endif]-->')
     Comment  :  a comment
     Comment  : [if IE 9]>IE-specific content<![endif]

剖析附名 (named) 且為數值的 (numeric) 字元參照，並將它們轉換為正確的字元
（注意：這 3 個參照都等同於 ‘'>'’）：

     >>> parser.feed('&gt;&#62;&#x3E;')
     Named ent: >
     Num ent  : >
     Num ent  : >

將不完整的區塊提供給 *note feed(): 357d. 是可行的，但是 *note
handle_data(): 3585. 可能會被多次呼叫（除非 'convert_charrefs' 設定為
‘True’）：

     >>> for chunk in ['<sp', 'an>buff', 'ered ', 'text</s', 'pan>']:
     ...     parser.feed(chunk)
     ...
     Start tag: span
     Data     : buff
     Data     : ered
     Data     : text
     End tag  : span

也能夠剖析無效的 HTML（例如未加引號的屬性）：

     >>> parser.feed('<p><a class=link href=#main>tag soup</p ></a>')
     Start tag: p
     Start tag: a
          attr: ('class', 'link')
          attr: ('href', '#main')
     Data     : tag soup
     End tag  : p
     End tag  : a


File: python.info,  Node: html entities --- HTML 一般實體的定義,  Next: XML 處理模組,  Prev: html parser --- 簡單的 HTML 和 XHTML 剖析器,  Up: Structured Markup Processing Tools

5.20.3 ‘html.entities’ -- HTML 一般實體的定義
---------------------------------------------

'原始碼：'Lib/html/entities.py(1)

__________________________________________________________________

該 module（模組）定義了四個字典：*note html5: 106c.、*note
name2codepoint: 3590.、*note codepoint2name: 3591. 以及 *note
entitydefs: 3592.。

 -- 資料: html.entities.html5

     將 HTML5 命名字元引用 (2) 對映到同等 Unicode 字元的字典，例如
     ‘html5['gt;'] == '>'’。請注意，後面的的分號包含在名稱中（例如
     ‘'gt;'’），但有些名稱即使沒有分號也會被此標準接受：在這種情況下，名
     稱可帶有或不帶有 ‘';'’。請見 *note html.unescape(): 8fb.。

     在 3.3 版被加入.

 -- 資料: html.entities.entitydefs

     將 XHTML 1.0 實體定義對映到 ISO Latin-1 中的替換文字的字典。

 -- 資料: html.entities.name2codepoint

     將 HTML4 實體名稱對映到 Unicode 程式點的字典。

 -- 資料: html.entities.codepoint2name

     將 Unicode 程式點對映到 HTML4 實體名稱的字典。

註解
....

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/html/entities.py

   (2) 請見
‘https://html.spec.whatwg.org/multipage/named-characters.html#named-character-references’


File: python.info,  Node: XML 處理模組,  Next: xml etree cElementTree --- ElementTree XML API,  Prev: html entities --- HTML 一般實體的定義,  Up: Structured Markup Processing Tools

5.20.4 XML 處理模組
-------------------

'原始碼：'Lib/xml/(1)

__________________________________________________________________

Python 處理 XML 的介面被歸類於 ‘xml’ 套件中。

     警告: XML 模組無法抵禦錯誤或惡意建構的資料。如果你需要剖析不受信任
     或未經身份驗證的資料，請參閱 *note XML 漏洞: 3596. 和 *note
     defusedxml 套件: 3597. 段落。

請務必注意 *note xml: 107. 套件中的模組要求至少有一個可用的 SAX 相容 XML
剖析器。Expat 剖析器包含在 Python 中，所以總是可以使用 *note
xml.parsers.expat: 10d. 模組。

*note xml.dom: 108. 和 *note xml.sax: 110. 套件的文件為 DOM 和 SAX 介面
的 Python 繫結的定義。

以下是 XML 處理子模組：

   * *note xml.etree.ElementTree: 10c.：ElementTree API，一個簡單且輕量
     級的 XML 處理器

   * *note xml.dom: 108.：DOM API 定義

   * *note xml.dom.minidom: 109.：最小的 DOM 實作

   * *note xml.dom.pulldom: 10a.：支援建置部分 DOM 樹

   * *note xml.sax: 110.：SAX2 基底類別和便利函式

   * *note xml.parsers.expat: 10d.：Expat 剖析器繫結

* Menu:

* XML 漏洞::
* defusedxml 套件::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/xml/


File: python.info,  Node: XML 漏洞,  Next: defusedxml 套件,  Up: XML 處理模組

5.20.4.1 XML 漏洞
.................

XML 處理模組無法抵禦惡意建構的資料。攻擊者可以濫用 XML 功能來執行阻斷服
務攻擊 (denial of service attack)、存取本地檔案、生成與其他機器的網路連
接或繞過防火牆。

下表概述了已知的攻擊以及各個模組是否易有漏洞。

種類                          sax                    etree                  minidom                pulldom                xmlrpc
                                                                                                                          
-------------------------------------------------------------------------------------------------------------------------------------------------
                                                                                                                          
十億笑聲 (billion laughs)     '脆弱' (1)             '脆弱' (1)             '脆弱' (1)             '脆弱' (1)             '脆弱' (1)
                                                                                                                          
                                                                                                                          
二次爆炸 (quadratic blowup)   '脆弱' (1)             '脆弱' (1)             '脆弱' (1)             '脆弱' (1)             '脆弱' (1)
                                                                                                                          
                                                                                                                          
外部實體擴展 (external        安全 (5)               安全 (2)               安全 (3)               安全 (5)               安全 (4)
entity expansion)                                                                                                         

DTD(1) 檢索                   安全 (5)               安全                   安全                   安全 (5)               安全
                                                                                                                          
                                                                                                                          
解壓縮炸彈 (decompression     安全                   安全                   安全                   安全                   '脆弱'
bomb)                                                                                                                     

大型 token                    '脆弱' (6)             '脆弱' (6)             '脆弱' (6)             '脆弱' (6)             '脆弱' (6)
                                                                                                                          

  1. Expat 2.4.1 及更新的版本不易受到「十億笑聲」和「二次爆炸」漏洞的影
     響。但仍可能由於依賴系統提供的函式庫而被列為易受攻擊的項目。請檢查
     ‘pyexpat.EXPAT_VERSION’。

  2. *note xml.etree.ElementTree: 10c. 不會擴展外部實體，並在實體出現時
     引發 *note ParseError: 1210.。

  3. *note xml.dom.minidom: 109. 不會擴展外部實體，只會逐字回傳未擴展的
     實體。

  4. *note xmlrpc.client: 114. 不會擴展外部實體且會忽略它們。

  5. 從 Python 3.7.1 開始，預設情況下不再處理外部通用實體。

  6. Expat 2.6.0 及更新版本不易受到剖析大型 token 所導致的二次 runtime 阻
     斷服務的影響。由於可能依賴系統提供的函式庫，因此仍被列為易受攻擊的
     項目。請參考 ‘pyexpat.EXPAT_VERSION’。

十億笑聲 / 指數實體擴展

     十億笑聲(2)攻擊（也稱為指數實體擴展 (exponential entity expansion)）
     使用多層巢狀實體。每個實體多次引用另一個實體，最終的實體定義包含一
     個小字串。指數擴展會產生數 GB 的文本，並消耗大量記憶體和 CPU 時間。

二次爆炸實體擴展

     二次爆炸攻擊類似於十億笑聲(3)攻擊；它也濫用實體擴展。它不是巢狀實體
     ，而是一遍又一遍地重複一個具有幾千個字元的大型實體。該攻擊不如指數
     擴展那麼有效率，但它不會觸發那些用來防止深度巢狀實體的剖析器對策。

外部實體擴展 (external entity expansion)

     實體聲明不僅僅可以包含用於替換的文本，它們還可以指向外部資源或本地
     檔案。XML 剖析器會存取資源並將內容嵌入到 XML 文件中。

DTD(4) 檢索

     一些 XML 函式庫（例如 Python 的 *note xml.dom.pulldom: 10a.）從遠端
     或本地位置檢索文件類型定義。該功能與外部實體擴展問題具有類似的含義
     。

解壓縮炸彈 (decompression bomb)

     解壓縮炸彈（又名 ZIP bomb(5)）適用於所有可以剖析壓縮 XML 串流（例如
     gzip 壓縮的 HTTP 串流或 LZMA 壓縮檔案）的 XML 函式庫。對於攻擊者來
     說，它可以將傳輸的資料量減少三個或更多數量級。

大型 token

     Expat 需要重新剖析未完成的 token；如果沒有 Expat 2.6.0 中引入的保護
     ，這可能會導致二次 runtime 而導致剖析 XML 的應用程式出現阻斷服務。
     此問題記錄於 CVE-2023-52425(6)。

PyPI 上的 defusedxml(7) 文件包含有關所有已知攻擊媒介 (attack vector) 的
更多資訊以及範例和參考資料。

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Document_type_definition

   (2) https://en.wikipedia.org/wiki/Billion_laughs

   (3) https://en.wikipedia.org/wiki/Billion_laughs

   (4) https://en.wikipedia.org/wiki/Document_type_definition

   (5) https://en.wikipedia.org/wiki/Zip_bomb

   (6) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-52425

   (7) https://pypi.org/project/defusedxml/


File: python.info,  Node: defusedxml 套件,  Prev: XML 漏洞,  Up: XML 處理模組

5.20.4.2 ‘defusedxml’ 套件
..........................

defusedxml(1) 是一個純 Python 套件，其中包含所有標準函式庫中 XML 剖析器
的修正版本子類別，可防止任何潛在的惡意操作。當伺服器程式會剖析任何不受信
任的 XML 資料時建議使用此套件。該套件還附帶了更多有關 XML 漏洞（例如
XPath 注入）的範例和延伸文件。

   ---------- Footnotes ----------

   (1) https://pypi.org/project/defusedxml/


File: python.info,  Node: xml etree cElementTree --- ElementTree XML API,  Next: xml dom --- Document 物件模型 API,  Prev: XML 處理模組,  Up: Structured Markup Processing Tools

5.20.5 ‘xml.etree.cElementTree’ -- ElementTree XML API
------------------------------------------------------

'原始碼：'Lib/xml/etree/ElementTree.py(1)

__________________________________________________________________

The *note xml.etree.ElementTree: 10c. module implements a simple and
efficient API for parsing and creating XML data.

在 3.3 版的變更: This module will use a fast implementation whenever
available.

在 3.3 版之後被棄用: ‘xml.etree.cElementTree’ 模組已被棄用。

     警告: The *note xml.etree.ElementTree: 10c. module is not secure
     against maliciously constructed data.  If you need to parse
     untrusted or unauthenticated data see *note XML 漏洞: 3596.

* Menu:

* 教學: 教學<2>.
* XPath 支援::
* Reference: Reference<3>.
* XInclude support::
* Reference: Reference<4>.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/xml/etree/ElementTree.py


File: python.info,  Node: 教學<2>,  Next: XPath 支援,  Up: xml etree cElementTree --- ElementTree XML API

5.20.5.1 教學
.............

This is a short tutorial for using *note xml.etree.ElementTree: 10c.
(‘ET’ in short).  The goal is to demonstrate some of the building blocks
and basic concepts of the module.

* Menu:

* XML tree and elements::
* 剖析 XML::
* Pull API for non-blocking parsing::
* Finding interesting elements::
* 改動 XML 檔案::
* Building XML documents::
* Parsing XML with Namespaces::


File: python.info,  Node: XML tree and elements,  Next: 剖析 XML,  Up: 教學<2>

5.20.5.2 XML tree and elements
..............................

XML is an inherently hierarchical data format, and the most natural way
to represent it is with a tree.  ‘ET’ has two classes for this purpose -
*note ElementTree: 8f2. represents the whole XML document as a tree, and
*note Element: 2e2. represents a single node in this tree.  Interactions
with the whole document (reading and writing to/from files) are usually
done on the *note ElementTree: 8f2. level.  Interactions with a single
XML element and its sub-elements are done on the *note Element: 2e2.
level.


File: python.info,  Node: 剖析 XML,  Next: Pull API for non-blocking parsing,  Prev: XML tree and elements,  Up: 教學<2>

5.20.5.3 剖析 XML
.................

We'll be using the fictive ‘country_data.xml’ XML document as the sample
data for this section:

     <?xml version="1.0"?>
     <data>
         <country name="Liechtenstein">
             <rank>1</rank>
             <year>2008</year>
             <gdppc>141100</gdppc>
             <neighbor name="Austria" direction="E"/>
             <neighbor name="Switzerland" direction="W"/>
         </country>
         <country name="Singapore">
             <rank>4</rank>
             <year>2011</year>
             <gdppc>59900</gdppc>
             <neighbor name="Malaysia" direction="N"/>
         </country>
         <country name="Panama">
             <rank>68</rank>
             <year>2011</year>
             <gdppc>13600</gdppc>
             <neighbor name="Costa Rica" direction="W"/>
             <neighbor name="Colombia" direction="E"/>
         </country>
     </data>

We can import this data by reading from a file:

     import xml.etree.ElementTree as ET
     tree = ET.parse('country_data.xml')
     root = tree.getroot()

Or directly from a string:

     root = ET.fromstring(country_data_as_string)

*note fromstring(): 35a0. parses XML from a string directly into an
*note Element: 2e2, which is the root element of the parsed tree.  Other
parsing functions may create an *note ElementTree: 8f2.  Check the
documentation to be sure.

As an *note Element: 2e2, ‘root’ has a tag and a dictionary of
attributes:

     >>> root.tag
     'data'
     >>> root.attrib
     {}

It also has children nodes over which we can iterate:

     >>> for child in root:
     ...     print(child.tag, child.attrib)
     ...
     country {'name': 'Liechtenstein'}
     country {'name': 'Singapore'}
     country {'name': 'Panama'}

Children are nested, and we can access specific child nodes by index:

     >>> root[0][1].text
     '2008'

     備註: Not all elements of the XML input will end up as elements of
     the parsed tree.  Currently, this module skips over any XML
     comments, processing instructions, and document type declarations
     in the input.  Nevertheless, trees built using this module's API
     rather than parsing from XML text can have comments and processing
     instructions in them; they will be included when generating XML
     output.  A document type declaration may be accessed by passing a
     custom *note TreeBuilder: 9f8. instance to the *note XMLParser:
     9f7. constructor.


File: python.info,  Node: Pull API for non-blocking parsing,  Next: Finding interesting elements,  Prev: 剖析 XML,  Up: 教學<2>

5.20.5.4 Pull API for non-blocking parsing
..........................................

Most parsing functions provided by this module require the whole
document to be read at once before returning any result.  It is possible
to use an *note XMLParser: 9f7. and feed data into it incrementally, but
it is a push API that calls methods on a callback target, which is too
low-level and inconvenient for most needs.  Sometimes what the user
really wants is to be able to parse XML incrementally, without blocking
operations, while enjoying the convenience of fully constructed *note
Element: 2e2. objects.

The most powerful tool for doing this is *note XMLPullParser: f94.  It
does not require a blocking read to obtain the XML data, and is instead
fed with data incrementally with *note XMLPullParser.feed(): 35a2.
calls.  To get the parsed XML elements, call *note
XMLPullParser.read_events(): 35a3.  Here is an example:

     >>> parser = ET.XMLPullParser(['start', 'end'])
     >>> parser.feed('<mytag>sometext')
     >>> list(parser.read_events())
     [('start', <Element 'mytag' at 0x7fa66db2be58>)]
     >>> parser.feed(' more text</mytag>')
     >>> for event, elem in parser.read_events():
     ...     print(event)
     ...     print(elem.tag, 'text=', elem.text)
     ...
     end
     mytag text= sometext more text

The obvious use case is applications that operate in a non-blocking
fashion where the XML data is being received from a socket or read
incrementally from some storage device.  In such cases, blocking reads
are unacceptable.

Because it's so flexible, *note XMLPullParser: f94. can be inconvenient
to use for simpler use-cases.  If you don't mind your application
blocking on reading XML data but would still like to have incremental
parsing capabilities, take a look at *note iterparse(): 258.  It can be
useful when you're reading a large XML document and don't want to hold
it wholly in memory.

Where 'immediate' feedback through events is wanted, calling method
*note XMLPullParser.flush(): 255. can help reduce delay; please make
sure to study the related security notes.


File: python.info,  Node: Finding interesting elements,  Next: 改動 XML 檔案,  Prev: Pull API for non-blocking parsing,  Up: 教學<2>

5.20.5.5 Finding interesting elements
.....................................

*note Element: 2e2. has some useful methods that help iterate
recursively over all the sub-tree below it (its children, their
children, and so on).  For example, *note Element.iter(): 12e3.:

     >>> for neighbor in root.iter('neighbor'):
     ...     print(neighbor.attrib)
     ...
     {'name': 'Austria', 'direction': 'E'}
     {'name': 'Switzerland', 'direction': 'W'}
     {'name': 'Malaysia', 'direction': 'N'}
     {'name': 'Costa Rica', 'direction': 'W'}
     {'name': 'Colombia', 'direction': 'E'}

*note Element.findall(): 35a5. finds only elements with a tag which are
direct children of the current element.  *note Element.find(): 35a6.
finds the 'first' child with a particular tag, and *note Element.text:
35a7. accesses the element's text content.  *note Element.get(): 35a8.
accesses the element's attributes:

     >>> for country in root.findall('country'):
     ...     rank = country.find('rank').text
     ...     name = country.get('name')
     ...     print(name, rank)
     ...
     Liechtenstein 1
     Singapore 4
     Panama 68

More sophisticated specification of which elements to look for is
possible by using *note XPath: b54.


File: python.info,  Node: 改動 XML 檔案,  Next: Building XML documents,  Prev: Finding interesting elements,  Up: 教學<2>

5.20.5.6 改動 XML 檔案
......................

*note ElementTree: 8f2. provides a simple way to build XML documents and
write them to files.  The *note ElementTree.write(): f98. method serves
this purpose.

Once created, an *note Element: 2e2. object may be manipulated by
directly changing its fields (such as *note Element.text: 35a7.), adding
and modifying attributes (*note Element.set(): 35aa. method), as well as
adding new children (for example with *note Element.append(): 35ab.).

Let's say we want to add one to each country's rank, and add an
‘updated’ attribute to the rank element:

     >>> for rank in root.iter('rank'):
     ...     new_rank = int(rank.text) + 1
     ...     rank.text = str(new_rank)
     ...     rank.set('updated', 'yes')
     ...
     >>> tree.write('output.xml')

XML 現在看起來像這樣：

     <?xml version="1.0"?>
     <data>
         <country name="Liechtenstein">
             <rank updated="yes">2</rank>
             <year>2008</year>
             <gdppc>141100</gdppc>
             <neighbor name="Austria" direction="E"/>
             <neighbor name="Switzerland" direction="W"/>
         </country>
         <country name="Singapore">
             <rank updated="yes">5</rank>
             <year>2011</year>
             <gdppc>59900</gdppc>
             <neighbor name="Malaysia" direction="N"/>
         </country>
         <country name="Panama">
             <rank updated="yes">69</rank>
             <year>2011</year>
             <gdppc>13600</gdppc>
             <neighbor name="Costa Rica" direction="W"/>
             <neighbor name="Colombia" direction="E"/>
         </country>
     </data>

We can remove elements using *note Element.remove(): 35ac.  Let's say we
want to remove all countries with a rank higher than 50:

     >>> for country in root.findall('country'):
     ...     # using root.findall() to avoid removal during traversal
     ...     rank = int(country.find('rank').text)
     ...     if rank > 50:
     ...         root.remove(country)
     ...
     >>> tree.write('output.xml')

Note that concurrent modification while iterating can lead to problems,
just like when iterating and modifying Python lists or dicts.
Therefore, the example first collects all matching elements with
‘root.findall()’, and only then iterates over the list of matches.

XML 現在看起來像這樣：

     <?xml version="1.0"?>
     <data>
         <country name="Liechtenstein">
             <rank updated="yes">2</rank>
             <year>2008</year>
             <gdppc>141100</gdppc>
             <neighbor name="Austria" direction="E"/>
             <neighbor name="Switzerland" direction="W"/>
         </country>
         <country name="Singapore">
             <rank updated="yes">5</rank>
             <year>2011</year>
             <gdppc>59900</gdppc>
             <neighbor name="Malaysia" direction="N"/>
         </country>
     </data>


File: python.info,  Node: Building XML documents,  Next: Parsing XML with Namespaces,  Prev: 改動 XML 檔案,  Up: 教學<2>

5.20.5.7 Building XML documents
...............................

The *note SubElement(): 35ae. function also provides a convenient way to
create new sub-elements for a given element:

     >>> a = ET.Element('a')
     >>> b = ET.SubElement(a, 'b')
     >>> c = ET.SubElement(a, 'c')
     >>> d = ET.SubElement(c, 'd')
     >>> ET.dump(a)
     <a><b /><c><d /></c></a>


File: python.info,  Node: Parsing XML with Namespaces,  Prev: Building XML documents,  Up: 教學<2>

5.20.5.8 Parsing XML with Namespaces
....................................

If the XML input has namespaces(1), tags and attributes with prefixes in
the form ‘prefix:sometag’ get expanded to ‘{uri}sometag’ where the
'prefix' is replaced by the full 'URI'. Also, if there is a default
namespace(2), that full URI gets prepended to all of the non-prefixed
tags.

Here is an XML example that incorporates two namespaces, one with the
prefix "fictional" and the other serving as the default namespace:

     <?xml version="1.0"?>
     <actors xmlns:fictional="http://characters.example.com"
             xmlns="http://people.example.com">
         <actor>
             <name>John Cleese</name>
             <fictional:character>Lancelot</fictional:character>
             <fictional:character>Archie Leach</fictional:character>
         </actor>
         <actor>
             <name>Eric Idle</name>
             <fictional:character>Sir Robin</fictional:character>
             <fictional:character>Gunther</fictional:character>
             <fictional:character>Commander Clement</fictional:character>
         </actor>
     </actors>

One way to search and explore this XML example is to manually add the
URI to every tag or attribute in the xpath of a *note find(): 35a6. or
*note findall(): 35a5.:

     root = fromstring(xml_text)
     for actor in root.findall('{http://people.example.com}actor'):
         name = actor.find('{http://people.example.com}name')
         print(name.text)
         for char in actor.findall('{http://characters.example.com}character'):
             print(' |-->', char.text)

A better way to search the namespaced XML example is to create a
dictionary with your own prefixes and use those in the search functions:

     ns = {'real_person': 'http://people.example.com',
           'role': 'http://characters.example.com'}

     for actor in root.findall('real_person:actor', ns):
         name = actor.find('real_person:name', ns)
         print(name.text)
         for char in actor.findall('role:character', ns):
             print(' |-->', char.text)

These two approaches both output:

     John Cleese
      |--> Lancelot
      |--> Archie Leach
     Eric Idle
      |--> Sir Robin
      |--> Gunther
      |--> Commander Clement

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/XML_namespace

   (2) https://www.w3.org/TR/xml-names/#defaulting


File: python.info,  Node: XPath 支援,  Next: Reference<3>,  Prev: 教學<2>,  Up: xml etree cElementTree --- ElementTree XML API

5.20.5.9 XPath 支援
...................

This module provides limited support for XPath expressions(1) for
locating elements in a tree.  The goal is to support a small subset of
the abbreviated syntax; a full XPath engine is outside the scope of the
module.

* Menu:

* 範例: 範例<31>.
* Supported XPath syntax::

   ---------- Footnotes ----------

   (1) https://www.w3.org/TR/xpath


File: python.info,  Node: 範例<31>,  Next: Supported XPath syntax,  Up: XPath 支援

5.20.5.10 範例
..............

Here's an example that demonstrates some of the XPath capabilities of
the module.  We'll be using the ‘countrydata’ XML document from the
*note Parsing XML: 359e. section:

     import xml.etree.ElementTree as ET

     root = ET.fromstring(countrydata)

     # Top-level elements
     root.findall(".")

     # All 'neighbor' grand-children of 'country' children of the top-level
     # elements
     root.findall("./country/neighbor")

     # Nodes with name='Singapore' that have a 'year' child
     root.findall(".//year/..[@name='Singapore']")

     # 'year' nodes that are children of nodes with name='Singapore'
     root.findall(".//*[@name='Singapore']/year")

     # All 'neighbor' nodes that are the second child of their parent
     root.findall(".//neighbor[2]")

For XML with namespaces, use the usual qualified ‘{namespace}tag’
notation:

     # All dublin-core "title" tags in the document
     root.findall(".//{http://purl.org/dc/elements/1.1/}title")


File: python.info,  Node: Supported XPath syntax,  Prev: 範例<31>,  Up: XPath 支援

5.20.5.11 Supported XPath syntax
................................

語法                        意義
                            
---------------------------------------------------------------------------------------
                            
‘tag’                       Selects all child elements with the given tag.  For
                            example, ‘spam’ selects all child elements named ‘spam’,
                            and ‘spam/egg’ selects all grandchildren named ‘egg’ in
                            all children named ‘spam’.  ‘{namespace}*’ selects all
                            tags in the given namespace, ‘{*}spam’ selects tags
                            named ‘spam’ in any (or no) namespace, and ‘{}*’ only
                            selects tags that are not in a namespace.
                            
                            在 3.8 版的變更: 新增對星號萬用字元的支援。
                            
                            
‘*’                         Selects all child elements, including comments and
                            processing instructions.  For example, ‘*/egg’ selects
                            all grandchildren named ‘egg’.
                            
                            
‘.’                         Selects the current node.  This is mostly useful at the
                            beginning of the path, to indicate that it's a relative
                            path.
                            
                            
‘//’                        Selects all subelements, on all levels beneath the
                            current element.  For example, ‘.//egg’ selects all
                            ‘egg’ elements in the entire tree.
                            
                            
‘..’                        Selects the parent element.  Returns ‘None’ if the path
                            attempts to reach the ancestors of the start element
                            (the element ‘find’ was called on).
                            
                            
‘[@attrib]’                 選擇所有具有給定屬性的元素。
                            
                            
‘[@attrib='value']’         Selects all elements for which the given attribute has
                            the given value.  The value cannot contain quotes.
                            
                            
‘[@attrib!='value']’        Selects all elements for which the given attribute does
                            not have the given value.  The value cannot contain
                            quotes.
                            
                            在 3.10 版被加入.
                            
                            
‘[tag]’                     Selects all elements that have a child named ‘tag’.
                            Only immediate children are supported.
                            
                            
‘[.='text']’                Selects all elements whose complete text content,
                            including descendants, equals the given ‘text’.
                            
                            在 3.7 版被加入.
                            
                            
‘[.!='text']’               Selects all elements whose complete text content,
                            including descendants, does not equal the given ‘text’.
                            
                            在 3.10 版被加入.
                            
                            
‘[tag='text']’              Selects all elements that have a child named ‘tag’ whose
                            complete text content, including descendants, equals the
                            given ‘text’.
                            
                            
‘[tag!='text']’             Selects all elements that have a child named ‘tag’ whose
                            complete text content, including descendants, does not
                            equal the given ‘text’.
                            
                            在 3.10 版被加入.
                            
                            
‘[position]’                Selects all elements that are located at the given
                            position.  The position can be either an integer (1 is
                            the first position), the expression ‘last()’ (for the
                            last position), or a position relative to the last
                            position (e.g.  ‘last()-1’).
                            

Predicates (expressions within square brackets) must be preceded by a
tag name, an asterisk, or another predicate.  ‘position’ predicates must
be preceded by a tag name.


File: python.info,  Node: Reference<3>,  Next: XInclude support,  Prev: XPath 支援,  Up: xml etree cElementTree --- ElementTree XML API

5.20.5.12 Reference
...................

* Menu:

* 函式: 函式<8>.


File: python.info,  Node: 函式<8>,  Up: Reference<3>

5.20.5.13 函式
..............

 -- 函式: xml.etree.ElementTree.canonicalize (xml_data=None, *,
          out=None, from_file=None, **options)

     C14N 2.0(1) transformation function.

     Canonicalization is a way to normalise XML output in a way that
     allows byte-by-byte comparisons and digital signatures.  It reduces
     the freedom that XML serializers have and instead generates a more
     constrained XML representation.  The main restrictions regard the
     placement of namespace declarations, the ordering of attributes,
     and ignorable whitespace.

     This function takes an XML data string ('xml_data') or a file path
     or file-like object ('from_file') as input, converts it to the
     canonical form, and writes it out using the 'out' file(-like)
     object, if provided, or returns it as a text string if not.  The
     output file receives text, not bytes.  It should therefore be
     opened in text mode with ‘utf-8’ encoding.

     Typical uses:

          xml_data = "<root>...</root>"
          print(canonicalize(xml_data))

          with open("c14n_output.xml", mode='w', encoding='utf-8') as out_file:
              canonicalize(xml_data, out=out_file)

          with open("c14n_output.xml", mode='w', encoding='utf-8') as out_file:
              canonicalize(from_file="inputfile.xml", out=out_file)

     The configuration 'options' are as follows:

        - 'with_comments': set to true to include comments (default:
          false)

        - 
          'strip_text': set to true to strip whitespace before and after text content

               (default: false)

        - 
          'rewrite_prefixes': set to true to replace namespace prefixes by "n{number}"

               (default: false)

        - 
          'qname_aware_tags': a set of qname aware tag names in which prefixes

               should be replaced in text content (default: empty)

        - 
          'qname_aware_attrs': a set of qname aware attribute names in which prefixes

               should be replaced in text content (default: empty)

        - 'exclude_attrs': a set of attribute names that should not be
          serialised

        - 'exclude_tags': a set of tag names that should not be
          serialised

     In the option list above, "a set" refers to any collection or
     iterable of strings, no ordering is expected.

     在 3.8 版被加入.

 -- 函式: xml.etree.ElementTree.Comment (text=None)

     Comment element factory.  This factory function creates a special
     element that will be serialized as an XML comment by the standard
     serializer.  The comment string can be either a bytestring or a
     Unicode string.  'text' is a string containing the comment string.
     Returns an element instance representing a comment.

     Note that *note XMLParser: 9f7. skips over comments in the input
     instead of creating comment objects for them.  An *note
     ElementTree: 8f2. will only contain comment nodes if they have been
     inserted into to the tree using one of the *note Element: 2e2.
     methods.

 -- 函式: xml.etree.ElementTree.dump (elem)

     Writes an element tree or element structure to sys.stdout.  This
     function should be used for debugging only.

     The exact output format is implementation dependent.  In this
     version, it's written as an ordinary XML file.

     'elem' is an element tree or an individual element.

     在 3.8 版的變更: The *note dump(): 35b8. function now preserves the
     attribute order specified by the user.

 -- 函式: xml.etree.ElementTree.fromstring (text, parser=None)

     Parses an XML section from a string constant.  Same as *note XML():
     35b9.  'text' is a string containing XML data.  'parser' is an
     optional parser instance.  If not given, the standard *note
     XMLParser: 9f7. parser is used.  Returns an *note Element: 2e2.
     instance.

 -- 函式: xml.etree.ElementTree.fromstringlist (sequence, parser=None)

     Parses an XML document from a sequence of string fragments.
     'sequence' is a list or other sequence containing XML data
     fragments.  'parser' is an optional parser instance.  If not given,
     the standard *note XMLParser: 9f7. parser is used.  Returns an
     *note Element: 2e2. instance.

     在 3.2 版被加入.

 -- 函式: xml.etree.ElementTree.indent (tree, space=' ', level=0)

     Appends whitespace to the subtree to indent the tree visually.
     This can be used to generate pretty-printed XML output.  'tree' can
     be an Element or ElementTree.  'space' is the whitespace string
     that will be inserted for each indentation level, two space
     characters by default.  For indenting partial subtrees inside of an
     already indented tree, pass the initial indentation level as
     'level'.

     在 3.9 版被加入.

 -- 函式: xml.etree.ElementTree.iselement (element)

     Check if an object appears to be a valid element object.  'element'
     is an element instance.  Return ‘True’ if this is an element
     object.

 -- 函式: xml.etree.ElementTree.iterparse (source, events=None,
          parser=None)

     Parses an XML section into an element tree incrementally, and
     reports what's going on to the user.  'source' is a filename or
     *note file object: 115b. containing XML data.  'events' is a
     sequence of events to report back.  The supported events are the
     strings ‘"start"’, ‘"end"’, ‘"comment"’, ‘"pi"’, ‘"start-ns"’ and
     ‘"end-ns"’ (the "ns" events are used to get detailed namespace
     information).  If 'events' is omitted, only ‘"end"’ events are
     reported.  'parser' is an optional parser instance.  If not given,
     the standard *note XMLParser: 9f7. parser is used.  'parser' must
     be a subclass of *note XMLParser: 9f7. and can only use the default
     *note TreeBuilder: 9f8. as a target.  Returns an *note iterator:
     192. providing ‘(event, elem)’ pairs; it has a ‘root’ attribute
     that references the root element of the resulting XML tree once
     'source' is fully read.  The iterator has the ‘close()’ method that
     closes the internal file object if 'source' is a filename.

     Note that while *note iterparse(): 258. builds the tree
     incrementally, it issues blocking reads on 'source' (or the file it
     names).  As such, it's unsuitable for applications where blocking
     reads can't be made.  For fully non-blocking parsing, see *note
     XMLPullParser: f94.

          備註: *note iterparse(): 258. only guarantees that it has seen
          the ">" character of a starting tag when it emits a "start"
          event, so the attributes are defined, but the contents of the
          text and tail attributes are undefined at that point.  The
          same applies to the element children; they may or may not be
          present.

          If you need a fully populated element, look for "end" events
          instead.

     在 3.4 版之後被棄用: 'parser' 引數。

     在 3.8 版的變更: 新增 'context' 與 'check_hostname' 事件。

     在 3.13 版的變更: Added the ‘close()’ method.

 -- 函式: xml.etree.ElementTree.parse (source, parser=None)

     Parses an XML section into an element tree.  'source' is a filename
     or file object containing XML data.  'parser' is an optional parser
     instance.  If not given, the standard *note XMLParser: 9f7. parser
     is used.  Returns an *note ElementTree: 8f2. instance.

 -- 函式: xml.etree.ElementTree.ProcessingInstruction (target,
          text=None)

     PI element factory.  This factory function creates a special
     element that will be serialized as an XML processing instruction.
     'target' is a string containing the PI target.  'text' is a string
     containing the PI contents, if given.  Returns an element instance,
     representing a processing instruction.

     Note that *note XMLParser: 9f7. skips over processing instructions
     in the input instead of creating PI objects for them.  An *note
     ElementTree: 8f2. will only contain processing instruction nodes if
     they have been inserted into to the tree using one of the *note
     Element: 2e2. methods.

 -- 函式: xml.etree.ElementTree.register_namespace (prefix, uri)

     Registers a namespace prefix.  The registry is global, and any
     existing mapping for either the given prefix or the namespace URI
     will be removed.  'prefix' is a namespace prefix.  'uri' is a
     namespace uri.  Tags and attributes in this namespace will be
     serialized with the given prefix, if at all possible.

     在 3.2 版被加入.

 -- 函式: xml.etree.ElementTree.SubElement (parent, tag, attrib={},
          **extra)

     Subelement factory.  This function creates an element instance, and
     appends it to an existing element.

     The element name, attribute names, and attribute values can be
     either bytestrings or Unicode strings.  'parent' is the parent
     element.  'tag' is the subelement name.  'attrib' is an optional
     dictionary, containing element attributes.  'extra' contains
     additional attributes, given as keyword arguments.  Returns an
     element instance.

 -- 函式: xml.etree.ElementTree.tostring (element, encoding='us-ascii',
          method='xml', *, xml_declaration=None, default_namespace=None,
          short_empty_elements=True)

     Generates a string representation of an XML element, including all
     subelements.  'element' is an *note Element: 2e2. instance.
     'encoding' (2) is the output encoding (default is US-ASCII). Use
     ‘encoding="unicode"’ to generate a Unicode string (otherwise, a
     bytestring is generated).  'method' is either ‘"xml"’, ‘"html"’ or
     ‘"text"’ (default is ‘"xml"’).  'xml_declaration',
     'default_namespace' and 'short_empty_elements' has the same meaning
     as in *note ElementTree.write(): f98.  Returns an (optionally)
     encoded string containing the XML data.

     在 3.4 版的變更: 新增 'short_empty_elements' 參數。

     在 3.8 版的變更: 新增 'xml_declaration' 與 'default_namespace' 參數
     。

     在 3.8 版的變更: The *note tostring(): f96. function now preserves
     the attribute order specified by the user.

 -- 函式: xml.etree.ElementTree.tostringlist (element,
          encoding='us-ascii', method='xml', *, xml_declaration=None,
          default_namespace=None, short_empty_elements=True)

     Generates a string representation of an XML element, including all
     subelements.  'element' is an *note Element: 2e2. instance.
     'encoding' (3) is the output encoding (default is US-ASCII). Use
     ‘encoding="unicode"’ to generate a Unicode string (otherwise, a
     bytestring is generated).  'method' is either ‘"xml"’, ‘"html"’ or
     ‘"text"’ (default is ‘"xml"’).  'xml_declaration',
     'default_namespace' and 'short_empty_elements' has the same meaning
     as in *note ElementTree.write(): f98.  Returns a list of
     (optionally) encoded strings containing the XML data.  It does not
     guarantee any specific sequence, except that
     ‘b"".join(tostringlist(element)) == tostring(element)’.

     在 3.2 版被加入.

     在 3.4 版的變更: 新增 'short_empty_elements' 參數。

     在 3.8 版的變更: 新增 'xml_declaration' 與 'default_namespace' 參數
     。

     在 3.8 版的變更: The *note tostringlist(): f97. function now
     preserves the attribute order specified by the user.

 -- 函式: xml.etree.ElementTree.XML (text, parser=None)

     Parses an XML section from a string constant.  This function can be
     used to embed "XML literals" in Python code.  'text' is a string
     containing XML data.  'parser' is an optional parser instance.  If
     not given, the standard *note XMLParser: 9f7. parser is used.
     Returns an *note Element: 2e2. instance.

 -- 函式: xml.etree.ElementTree.XMLID (text, parser=None)

     Parses an XML section from a string constant, and also returns a
     dictionary which maps from element id:s to elements.  'text' is a
     string containing XML data.  'parser' is an optional parser
     instance.  If not given, the standard *note XMLParser: 9f7. parser
     is used.  Returns a tuple containing an *note Element: 2e2.
     instance and a dictionary.

   ---------- Footnotes ----------

   (1) https://www.w3.org/TR/xml-c14n2/

   (2) The encoding string included in XML output should conform to the
appropriate standards.  For example, "UTF-8" is valid, but "UTF8" is
not.  See
‘https://www.w3.org/TR/2006/REC-xml11-20060816/#NT-EncodingDecl’ and
‘https://www.iana.org/assignments/character-sets/character-sets.xhtml’.

   (3) The encoding string included in XML output should conform to the
appropriate standards.  For example, "UTF-8" is valid, but "UTF8" is
not.  See
‘https://www.w3.org/TR/2006/REC-xml11-20060816/#NT-EncodingDecl’ and
‘https://www.iana.org/assignments/character-sets/character-sets.xhtml’.


File: python.info,  Node: XInclude support,  Next: Reference<4>,  Prev: Reference<3>,  Up: xml etree cElementTree --- ElementTree XML API

5.20.5.14 XInclude support
..........................

This module provides limited support for XInclude directives(1), via the
*note xml.etree.ElementInclude: 10b. helper module.  This module can be
used to insert subtrees and text strings into element trees, based on
information in the tree.

* Menu:

* 範例: 範例<32>.

   ---------- Footnotes ----------

   (1) https://www.w3.org/TR/xinclude/


File: python.info,  Node: 範例<32>,  Up: XInclude support

5.20.5.15 範例
..............

Here's an example that demonstrates use of the XInclude module.  To
include an XML document in the current document, use the
‘{http://www.w3.org/2001/XInclude}include’ element and set the 'parse'
attribute to ‘"xml"’, and use the 'href' attribute to specify the
document to include.

     <?xml version="1.0"?>
     <document xmlns:xi="http://www.w3.org/2001/XInclude">
       <xi:include href="source.xml" parse="xml" />
     </document>

By default, the 'href' attribute is treated as a file name.  You can use
custom loaders to override this behaviour.  Also note that the standard
helper does not support XPointer syntax.

To process this file, load it as usual, and pass the root element to the
*note xml.etree.ElementTree: 10c. module:

     from xml.etree import ElementTree, ElementInclude

     tree = ElementTree.parse("document.xml")
     root = tree.getroot()

     ElementInclude.include(root)

The ElementInclude module replaces the
‘{http://www.w3.org/2001/XInclude}include’ element with the root element
from the 'source.xml' document.  The result might look something like
this:

     <document xmlns:xi="http://www.w3.org/2001/XInclude">
       <para>This is a paragraph.</para>
     </document>

If the 'parse' attribute is omitted, it defaults to "xml".  The href
attribute is required.

To include a text document, use the
‘{http://www.w3.org/2001/XInclude}include’ element, and set the 'parse'
attribute to "text":

     <?xml version="1.0"?>
     <document xmlns:xi="http://www.w3.org/2001/XInclude">
       Copyright (c) <xi:include href="year.txt" parse="text" />.
     </document>

The result might look something like:

     <document xmlns:xi="http://www.w3.org/2001/XInclude">
       Copyright (c) 2003.
     </document>


File: python.info,  Node: Reference<4>,  Prev: XInclude support,  Up: xml etree cElementTree --- ElementTree XML API

5.20.5.16 Reference
...................

* Menu:

* 函式: 函式<9>.
* Element 物件::
* ElementTree 物件::
* QName 物件::
* TreeBuilder 物件::
* XMLParser 物件::
* XMLPullParser 物件::
* 例外: 例外<14>.


File: python.info,  Node: 函式<9>,  Next: Element 物件,  Up: Reference<4>

5.20.5.17 函式
..............

 -- 函式: xml.etree.ElementInclude.default_loader (href, parse,
          encoding=None)

     Default loader.  This default loader reads an included resource
     from disk.  'href' is a URL. 'parse' is for parse mode either "xml"
     or "text".  'encoding' is an optional text encoding.  If not given,
     encoding is ‘utf-8’.  Returns the expanded resource.  If the parse
     mode is ‘"xml"’, this is an *note Element: 2e2. instance.  If the
     parse mode is ‘"text"’, this is a string.  If the loader fails, it
     can return ‘None’ or raise an exception.

 -- 函式: xml.etree.ElementInclude.include (elem, loader=None,
          base_url=None, max_depth=6)

     This function expands XInclude directives in-place in tree pointed
     by 'elem'.  'elem' is either the root *note Element: 2e2. or an
     *note ElementTree: 8f2. instance to find such element.  'loader' is
     an optional resource loader.  If omitted, it defaults to *note
     default_loader(): 35c5.  If given, it should be a callable that
     implements the same interface as *note default_loader(): 35c5.
     'base_url' is base URL of the original file, to resolve relative
     include file references.  'max_depth' is the maximum number of
     recursive inclusions.  Limited to reduce the risk of malicious
     content explosion.  Pass ‘None’ to disable the limitation.

     在 3.9 版的變更: 新增 'base_url' 與 'max_depth' 參數。


File: python.info,  Node: Element 物件,  Next: ElementTree 物件,  Prev: 函式<9>,  Up: Reference<4>

5.20.5.18 Element 物件
......................

 -- 類別: xml.etree.ElementTree.Element (tag, attrib={}, **extra)

     Element class.  This class defines the Element interface, and
     provides a reference implementation of this interface.

     The element name, attribute names, and attribute values can be
     either bytestrings or Unicode strings.  'tag' is the element name.
     'attrib' is an optional dictionary, containing element attributes.
     'extra' contains additional attributes, given as keyword arguments.

      -- 屬性: tag

          A string identifying what kind of data this element represents
          (the element type, in other words).

      -- 屬性: text
      -- 屬性: tail

          These attributes can be used to hold additional data
          associated with the element.  Their values are usually strings
          but may be any application-specific object.  If the element is
          created from an XML file, the 'text' attribute holds either
          the text between the element's start tag and its first child
          or end tag, or ‘None’, and the 'tail' attribute holds either
          the text between the element's end tag and the next tag, or
          ‘None’.  For the XML data

               <a><b>1<c>2<d/>3</c></b>4</a>

          the 'a' element has ‘None’ for both 'text' and 'tail'
          attributes, the 'b' element has 'text' ‘"1"’ and 'tail' ‘"4"’,
          the 'c' element has 'text' ‘"2"’ and 'tail' ‘None’, and the
          'd' element has 'text' ‘None’ and 'tail' ‘"3"’.

          To collect the inner text of an element, see *note itertext():
          116d, for example ‘"".join(element.itertext())’.

          Applications may store arbitrary objects in these attributes.

      -- 屬性: attrib

          A dictionary containing the element's attributes.  Note that
          while the 'attrib' value is always a real mutable Python
          dictionary, an ElementTree implementation may choose to use
          another internal representation, and create the dictionary
          only if someone asks for it.  To take advantage of such
          implementations, use the dictionary methods below whenever
          possible.

     The following dictionary-like methods work on the element
     attributes.

      -- 方法: clear ()

          Resets an element.  This function removes all subelements,
          clears all attributes, and sets the text and tail attributes
          to ‘None’.

      -- 方法: get (key, default=None)

          Gets the element attribute named 'key'.

          Returns the attribute value, or 'default' if the attribute was
          not found.

      -- 方法: items ()

          Returns the element attributes as a sequence of (name, value)
          pairs.  The attributes are returned in an arbitrary order.

      -- 方法: keys ()

          Returns the elements attribute names as a list.  The names are
          returned in an arbitrary order.

      -- 方法: set (key, value)

          Set the attribute 'key' on the element to 'value'.

     The following methods work on the element's children (subelements).

      -- 方法: append (subelement)

          Adds the element 'subelement' to the end of this element's
          internal list of subelements.  Raises *note TypeError: 4dd. if
          'subelement' is not an *note Element: 2e2.

      -- 方法: extend (subelements)

          Appends 'subelements' from an iterable of elements.  Raises
          *note TypeError: 4dd. if a subelement is not an *note Element:
          2e2.

          在 3.2 版被加入.

      -- 方法: find (match, namespaces=None)

          Finds the first subelement matching 'match'.  'match' may be a
          tag name or a *note path: b54.  Returns an element instance or
          ‘None’.  'namespaces' is an optional mapping from namespace
          prefix to full name.  Pass ‘''’ as prefix to move all
          unprefixed tag names in the expression into the given
          namespace.

      -- 方法: findall (match, namespaces=None)

          Finds all matching subelements, by tag name or *note path:
          b54.  Returns a list containing all matching elements in
          document order.  'namespaces' is an optional mapping from
          namespace prefix to full name.  Pass ‘''’ as prefix to move
          all unprefixed tag names in the expression into the given
          namespace.

      -- 方法: findtext (match, default=None, namespaces=None)

          Finds text for the first subelement matching 'match'.  'match'
          may be a tag name or a *note path: b54.  Returns the text
          content of the first matching element, or 'default' if no
          element was found.  Note that if the matching element has no
          text content an empty string is returned.  'namespaces' is an
          optional mapping from namespace prefix to full name.  Pass
          ‘''’ as prefix to move all unprefixed tag names in the
          expression into the given namespace.

      -- 方法: insert (index, subelement)

          Inserts 'subelement' at the given position in this element.
          Raises *note TypeError: 4dd. if 'subelement' is not an *note
          Element: 2e2.

      -- 方法: iter (tag=None)

          Creates a tree *note iterator: 192. with the current element
          as the root.  The iterator iterates over this element and all
          elements below it, in document (depth first) order.  If 'tag'
          is not ‘None’ or ‘'*'’, only elements whose tag equals 'tag'
          are returned from the iterator.  If the tree structure is
          modified during iteration, the result is undefined.

          在 3.2 版被加入.

      -- 方法: iterfind (match, namespaces=None)

          Finds all matching subelements, by tag name or *note path:
          b54.  Returns an iterable yielding all matching elements in
          document order.  'namespaces' is an optional mapping from
          namespace prefix to full name.

          在 3.2 版被加入.

      -- 方法: itertext ()

          Creates a text iterator.  The iterator loops over this element
          and all subelements, in document order, and returns all inner
          text.

          在 3.2 版被加入.

      -- 方法: makeelement (tag, attrib)

          Creates a new element object of the same type as this element.
          Do not call this method, use the *note SubElement(): 35ae.
          factory function instead.

      -- 方法: remove (subelement)

          Removes 'subelement' from the element.  Unlike the find*
          methods this method compares elements based on the instance
          identity, not on tag value or contents.

     *note Element: 2e2. objects also support the following sequence
     type methods for working with subelements: *note __delitem__():
     1435, *note __getitem__(): 266, *note __setitem__(): 1434, *note
     __len__(): 1e38.

     Caution: Elements with no subelements will test as ‘False’.  In a
     future release of Python, all elements will test as ‘True’
     regardless of whether subelements exist.  Instead, prefer explicit
     ‘len(elem)’ or ‘elem is not None’ tests.:

          element = root.find('foo')

          if not element:  # careful!
              print("element not found, or element has no subelements")

          if element is None:
              print("element not found")

     在 3.12 版的變更: Testing the truth value of an Element emits *note
     DeprecationWarning: 18b.

     Prior to Python 3.8, the serialisation order of the XML attributes
     of elements was artificially made predictable by sorting the
     attributes by their name.  Based on the now guaranteed ordering of
     dicts, this arbitrary reordering was removed in Python 3.8 to
     preserve the order in which attributes were originally parsed or
     created by user code.

     In general, user code should try not to depend on a specific
     ordering of attributes, given that the XML Information Set(1)
     explicitly excludes the attribute order from conveying information.
     Code should be prepared to deal with any ordering on input.  In
     cases where deterministic XML output is required, e.g.  for
     cryptographic signing or test data sets, canonical serialisation is
     available with the *note canonicalize(): 35b6. function.

     In cases where canonical output is not applicable but a specific
     attribute order is still desirable on output, code should aim for
     creating the attributes directly in the desired order, to avoid
     perceptual mismatches for readers of the code.  In cases where this
     is difficult to achieve, a recipe like the following can be applied
     prior to serialisation to enforce an order independently from the
     Element creation:

          def reorder_attributes(root):
              for el in root.iter():
                  attrib = el.attrib
                  if len(attrib) > 1:
                      # adjust attribute order, e.g. by sorting
                      attribs = sorted(attrib.items())
                      attrib.clear()
                      attrib.update(attribs)

   ---------- Footnotes ----------

   (1) https://www.w3.org/TR/xml-infoset/


File: python.info,  Node: ElementTree 物件,  Next: QName 物件,  Prev: Element 物件,  Up: Reference<4>

5.20.5.19 ElementTree 物件
..........................

 -- 類別: xml.etree.ElementTree.ElementTree (element=None, file=None)

     ElementTree wrapper class.  This class represents an entire element
     hierarchy, and adds some extra support for serialization to and
     from standard XML.

     'element' is the root element.  The tree is initialized with the
     contents of the XML 'file' if given.

      -- 方法: _setroot (element)

          Replaces the root element for this tree.  This discards the
          current contents of the tree, and replaces it with the given
          element.  Use with care.  'element' is an element instance.

      -- 方法: find (match, namespaces=None)

          Same as *note Element.find(): 35a6, starting at the root of
          the tree.

      -- 方法: findall (match, namespaces=None)

          Same as *note Element.findall(): 35a5, starting at the root of
          the tree.

      -- 方法: findtext (match, default=None, namespaces=None)

          Same as *note Element.findtext(): 35ce, starting at the root
          of the tree.

      -- 方法: getroot ()

          Returns the root element for this tree.

      -- 方法: iter (tag=None)

          Creates and returns a tree iterator for the root element.  The
          iterator loops over all elements in this tree, in section
          order.  'tag' is the tag to look for (default is to return all
          elements).

      -- 方法: iterfind (match, namespaces=None)

          Same as *note Element.iterfind(): 116c, starting at the root
          of the tree.

          在 3.2 版被加入.

      -- 方法: parse (source, parser=None)

          Loads an external XML section into this element tree.
          'source' is a file name or *note file object: 115b.  'parser'
          is an optional parser instance.  If not given, the standard
          *note XMLParser: 9f7. parser is used.  Returns the section
          root element.

      -- 方法: write (file, encoding='us-ascii', xml_declaration=None,
               default_namespace=None, method='xml', *,
               short_empty_elements=True)

          Writes the element tree to a file, as XML. 'file' is a file
          name, or a *note file object: 115b. opened for writing.
          'encoding' (1) is the output encoding (default is US-ASCII).
          'xml_declaration' controls if an XML declaration should be
          added to the file.  Use ‘False’ for never, ‘True’ for always,
          ‘None’ for only if not US-ASCII or UTF-8 or Unicode (default
          is ‘None’).  'default_namespace' sets the default XML
          namespace (for "xmlns").  'method' is either ‘"xml"’, ‘"html"’
          or ‘"text"’ (default is ‘"xml"’).  The keyword-only
          'short_empty_elements' parameter controls the formatting of
          elements that contain no content.  If ‘True’ (the default),
          they are emitted as a single self-closed tag, otherwise they
          are emitted as a pair of start/end tags.

          The output is either a string (*note str: 3f2.) or binary
          (*note bytes: 1a5.).  This is controlled by the 'encoding'
          argument.  If 'encoding' is ‘"unicode"’, the output is a
          string; otherwise, it's binary.  Note that this may conflict
          with the type of 'file' if it's an open *note file object:
          115b.; make sure you do not try to write a string to a binary
          stream and vice versa.

          在 3.4 版的變更: 新增 'short_empty_elements' 參數。

          在 3.8 版的變更: The *note write(): f98. method now preserves
          the attribute order specified by the user.

This is the XML file that is going to be manipulated:

     <html>
         <head>
             <title>Example page</title>
         </head>
         <body>
             <p>Moved to <a href="http://example.org/">example.org</a>
             or <a href="http://example.com/">example.com</a>.</p>
         </body>
     </html>

Example of changing the attribute "target" of every link in first
paragraph:

     >>> from xml.etree.ElementTree import ElementTree
     >>> tree = ElementTree()
     >>> tree.parse("index.xhtml")
     <Element 'html' at 0xb77e6fac>
     >>> p = tree.find("body/p")     # Finds first occurrence of tag p in body
     >>> p
     <Element 'p' at 0xb77ec26c>
     >>> links = list(p.iter("a"))   # Returns list of all links
     >>> links
     [<Element 'a' at 0xb77ec2ac>, <Element 'a' at 0xb77ec1cc>]
     >>> for i in links:             # Iterates through all found links
     ...     i.attrib["target"] = "blank"
     ...
     >>> tree.write("output.xhtml")

   ---------- Footnotes ----------

   (1) The encoding string included in XML output should conform to the
appropriate standards.  For example, "UTF-8" is valid, but "UTF8" is
not.  See
‘https://www.w3.org/TR/2006/REC-xml11-20060816/#NT-EncodingDecl’ and
‘https://www.iana.org/assignments/character-sets/character-sets.xhtml’.


File: python.info,  Node: QName 物件,  Next: TreeBuilder 物件,  Prev: ElementTree 物件,  Up: Reference<4>

5.20.5.20 QName 物件
....................

 -- 類別: xml.etree.ElementTree.QName (text_or_uri, tag=None)

     QName wrapper.  This can be used to wrap a QName attribute value,
     in order to get proper namespace handling on output.  'text_or_uri'
     is a string containing the QName value, in the form {uri}local, or,
     if the tag argument is given, the URI part of a QName.  If 'tag' is
     given, the first argument is interpreted as a URI, and this
     argument is interpreted as a local name.  *note QName: 35dd.
     instances are opaque.


File: python.info,  Node: TreeBuilder 物件,  Next: XMLParser 物件,  Prev: QName 物件,  Up: Reference<4>

5.20.5.21 TreeBuilder 物件
..........................

 -- 類別: xml.etree.ElementTree.TreeBuilder (element_factory=None, *,
          comment_factory=None, pi_factory=None, insert_comments=False,
          insert_pis=False)

     Generic element structure builder.  This builder converts a
     sequence of start, data, end, comment and pi method calls to a
     well-formed element structure.  You can use this class to build an
     element structure using a custom XML parser, or a parser for some
     other XML-like format.

     'element_factory', when given, must be a callable accepting two
     positional arguments: a tag and a dict of attributes.  It is
     expected to return a new element instance.

     The 'comment_factory' and 'pi_factory' functions, when given,
     should behave like the *note Comment(): 35b7. and *note
     ProcessingInstruction(): 35bd. functions to create comments and
     processing instructions.  When not given, the default factories
     will be used.  When 'insert_comments' and/or 'insert_pis' is true,
     comments/pis will be inserted into the tree if they appear within
     the root element (but not outside of it).

      -- 方法: close ()

          Flushes the builder buffers, and returns the toplevel document
          element.  Returns an *note Element: 2e2. instance.

      -- 方法: data (data)

          Adds text to the current element.  'data' is a string.  This
          should be either a bytestring, or a Unicode string.

      -- 方法: end (tag)

          Closes the current element.  'tag' is the element name.
          Returns the closed element.

      -- 方法: start (tag, attrs)

          Opens a new element.  'tag' is the element name.  'attrs' is a
          dictionary containing element attributes.  Returns the opened
          element.

      -- 方法: comment (text)

          Creates a comment with the given 'text'.  If ‘insert_comments’
          is true, this will also add it to the tree.

          在 3.8 版被加入.

      -- 方法: pi (target, text)

          Creates a process instruction with the given 'target' name and
          'text'.  If ‘insert_pis’ is true, this will also add it to the
          tree.

          在 3.8 版被加入.

     In addition, a custom *note TreeBuilder: 9f8. object can provide
     the following methods:

      -- 方法: doctype (name, pubid, system)

          Handles a doctype declaration.  'name' is the doctype name.
          'pubid' is the public identifier.  'system' is the system
          identifier.  This method does not exist on the default *note
          TreeBuilder: 9f8. class.

          在 3.2 版被加入.

      -- 方法: start_ns (prefix, uri)

          Is called whenever the parser encounters a new namespace
          declaration, before the ‘start()’ callback for the opening
          element that defines it.  'prefix' is ‘''’ for the default
          namespace and the declared namespace prefix name otherwise.
          'uri' is the namespace URI.

          在 3.8 版被加入.

      -- 方法: end_ns (prefix)

          Is called after the ‘end()’ callback of an element that
          declared a namespace prefix mapping, with the name of the
          'prefix' that went out of scope.

          在 3.8 版被加入.

 -- 類別: xml.etree.ElementTree.C14NWriterTarget (write, *,
          with_comments=False, strip_text=False, rewrite_prefixes=False,
          qname_aware_tags=None, qname_aware_attrs=None,
          exclude_attrs=None, exclude_tags=None)

     A C14N 2.0(1) writer.  Arguments are the same as for the *note
     canonicalize(): 35b6. function.  This class does not build a tree
     but translates the callback events directly into a serialised form
     using the 'write' function.

     在 3.8 版被加入.

   ---------- Footnotes ----------

   (1) https://www.w3.org/TR/xml-c14n2/


File: python.info,  Node: XMLParser 物件,  Next: XMLPullParser 物件,  Prev: TreeBuilder 物件,  Up: Reference<4>

5.20.5.22 XMLParser 物件
........................

 -- 類別: xml.etree.ElementTree.XMLParser (*, target=None,
          encoding=None)

     This class is the low-level building block of the module.  It uses
     *note xml.parsers.expat: 10d. for efficient, event-based parsing of
     XML. It can be fed XML data incrementally with the *note feed():
     35e9. method, and parsing events are translated to a push API - by
     invoking callbacks on the 'target' object.  If 'target' is omitted,
     the standard *note TreeBuilder: 9f8. is used.  If 'encoding' (1) is
     given, the value overrides the encoding specified in the XML file.

     在 3.8 版的變更: Parameters are now *note keyword-only: 285.  The
     'html' argument no longer supported.

      -- 方法: close ()

          Finishes feeding data to the parser.  Returns the result of
          calling the ‘close()’ method of the 'target' passed during
          construction; by default, this is the toplevel document
          element.

      -- 方法: feed (data)

          Feeds data to the parser.  'data' is encoded data.

      -- 方法: flush ()

          Triggers parsing of any previously fed unparsed data, which
          can be used to ensure more immediate feedback, in particular
          with Expat >=2.6.0.  The implementation of *note flush(): 254.
          temporarily disables reparse deferral with Expat (if currently
          enabled) and triggers a reparse.  Disabling reparse deferral
          has security consequences; please see *note
          xml.parsers.expat.xmlparser.SetReparseDeferralEnabled(): 257.
          for details.

          Note that *note flush(): 254. has been backported to some
          prior releases of CPython as a security fix.  Check for
          availability of *note flush(): 254. using *note hasattr():
          479. if used in code running across a variety of Python
          versions.

          在 3.13 版被加入.

     *note XMLParser.feed(): 35e9. calls 'target"s ‘start(tag,
     attrs_dict)’ method for each opening tag, its ‘end(tag)’ method for
     each closing tag, and data is processed by method ‘data(data)’.
     For further supported callback methods, see the *note TreeBuilder:
     9f8. class.  *note XMLParser.close(): 35ea. calls 'target"s method
     ‘close()’.  *note XMLParser: 9f7. can be used not only for building
     a tree structure.  This is an example of counting the maximum depth
     of an XML file:

          >>> from xml.etree.ElementTree import XMLParser
          >>> class MaxDepth:                     # The target object of the parser
          ...     maxDepth = 0
          ...     depth = 0
          ...     def start(self, tag, attrib):   # Called for each opening tag.
          ...         self.depth += 1
          ...         if self.depth > self.maxDepth:
          ...             self.maxDepth = self.depth
          ...     def end(self, tag):             # Called for each closing tag.
          ...         self.depth -= 1
          ...     def data(self, data):
          ...         pass            # We do not need to do anything with data.
          ...     def close(self):    # Called when all data has been parsed.
          ...         return self.maxDepth
          ...
          >>> target = MaxDepth()
          >>> parser = XMLParser(target=target)
          >>> exampleXml = """
          ... <a>
          ...   <b>
          ...   </b>
          ...   <b>
          ...     <c>
          ...       <d>
          ...       </d>
          ...     </c>
          ...   </b>
          ... </a>"""
          >>> parser.feed(exampleXml)
          >>> parser.close()
          4

   ---------- Footnotes ----------

   (1) The encoding string included in XML output should conform to the
appropriate standards.  For example, "UTF-8" is valid, but "UTF8" is
not.  See
‘https://www.w3.org/TR/2006/REC-xml11-20060816/#NT-EncodingDecl’ and
‘https://www.iana.org/assignments/character-sets/character-sets.xhtml’.


File: python.info,  Node: XMLPullParser 物件,  Next: 例外<14>,  Prev: XMLParser 物件,  Up: Reference<4>

5.20.5.23 XMLPullParser 物件
............................

 -- 類別: xml.etree.ElementTree.XMLPullParser (events=None)

     A pull parser suitable for non-blocking applications.  Its
     input-side API is similar to that of *note XMLParser: 9f7, but
     instead of pushing calls to a callback target, *note XMLPullParser:
     f94. collects an internal list of parsing events and lets the user
     read from it.  'events' is a sequence of events to report back.
     The supported events are the strings ‘"start"’, ‘"end"’,
     ‘"comment"’, ‘"pi"’, ‘"start-ns"’ and ‘"end-ns"’ (the "ns" events
     are used to get detailed namespace information).  If 'events' is
     omitted, only ‘"end"’ events are reported.

      -- 方法: feed (data)

          Feed the given bytes data to the parser.

      -- 方法: flush ()

          Triggers parsing of any previously fed unparsed data, which
          can be used to ensure more immediate feedback, in particular
          with Expat >=2.6.0.  The implementation of *note flush(): 255.
          temporarily disables reparse deferral with Expat (if currently
          enabled) and triggers a reparse.  Disabling reparse deferral
          has security consequences; please see *note
          xml.parsers.expat.xmlparser.SetReparseDeferralEnabled(): 257.
          for details.

          Note that *note flush(): 255. has been backported to some
          prior releases of CPython as a security fix.  Check for
          availability of *note flush(): 255. using *note hasattr():
          479. if used in code running across a variety of Python
          versions.

          在 3.13 版被加入.

      -- 方法: close ()

          Signal the parser that the data stream is terminated.  Unlike
          *note XMLParser.close(): 35ea, this method always returns
          *note None: 61b.  Any events not yet retrieved when the parser
          is closed can still be read with *note read_events(): 35a3.

      -- 方法: read_events ()

          Return an iterator over the events which have been encountered
          in the data fed to the parser.  The iterator yields ‘(event,
          elem)’ pairs, where 'event' is a string representing the type
          of event (e.g.  ‘"end"’) and 'elem' is the encountered *note
          Element: 2e2. object, or other context value as follows.

             * ‘start’、‘end’：目前的 Element。

             * ‘comment’, ‘pi’: the current comment / processing
               instruction

             * ‘start-ns’: a tuple ‘(prefix, uri)’ naming the declared
               namespace mapping.

             * ‘end-ns’: *note None: 61b. (this may change in a future
               version)

          Events provided in a previous call to *note read_events():
          35a3. will not be yielded again.  Events are consumed from the
          internal queue only when they are retrieved from the iterator,
          so multiple readers iterating in parallel over iterators
          obtained from *note read_events(): 35a3. will have
          unpredictable results.

          備註: *note XMLPullParser: f94. only guarantees that it has
          seen the ">" character of a starting tag when it emits a
          "start" event, so the attributes are defined, but the contents
          of the text and tail attributes are undefined at that point.
          The same applies to the element children; they may or may not
          be present.

          If you need a fully populated element, look for "end" events
          instead.

     在 3.4 版被加入.

     在 3.8 版的變更: 新增 'context' 與 'check_hostname' 事件。


File: python.info,  Node: 例外<14>,  Prev: XMLPullParser 物件,  Up: Reference<4>

5.20.5.24 例外
..............

 -- 類別: xml.etree.ElementTree.ParseError

     XML parse error, raised by the various parsing methods in this
     module when parsing fails.  The string representation of an
     instance of this exception will contain a user-friendly error
     message.  In addition, it will have the following attributes
     available:

      -- 屬性: code

          A numeric error code from the expat parser.  See the
          documentation of *note xml.parsers.expat: 10d. for the list of
          error codes and their meanings.

      -- 屬性: position

          A tuple of 'line', 'column' numbers, specifying where the
          error occurred.

註解
....


File: python.info,  Node: xml dom --- Document 物件模型 API,  Next: xml dom minidom --- 最小的 DOM 實作,  Prev: xml etree cElementTree --- ElementTree XML API,  Up: Structured Markup Processing Tools

5.20.6 ‘xml.dom’ -- Document 物件模型 API
-----------------------------------------

'原始碼：'Lib/xml/dom/__init__.py(1)

__________________________________________________________________

The Document Object Model, or "DOM," is a cross-language API from the
World Wide Web Consortium (W3C) for accessing and modifying XML
documents.  A DOM implementation presents an XML document as a tree
structure, or allows client code to build such a structure from scratch.
It then gives access to the structure through a set of objects which
provided well-known interfaces.

The DOM is extremely useful for random-access applications.  SAX only
allows you a view of one bit of the document at a time.  If you are
looking at one SAX element, you have no access to another.  If you are
looking at a text node, you have no access to a containing element.
When you write a SAX application, you need to keep track of your
program's position in the document somewhere in your own code.  SAX does
not do it for you.  Also, if you need to look ahead in the XML document,
you are just out of luck.

Some applications are simply impossible in an event driven model with no
access to a tree.  Of course you could build some sort of tree yourself
in SAX events, but the DOM allows you to avoid writing that code.  The
DOM is a standard tree representation for XML data.

The Document Object Model is being defined by the W3C in stages, or
"levels" in their terminology.  The Python mapping of the API is
substantially based on the DOM Level 2 recommendation.

DOM applications typically start by parsing some XML into a DOM. How
this is accomplished is not covered at all by DOM Level 1, and Level 2
provides only limited improvements: There is a ‘DOMImplementation’
object class which provides access to ‘Document’ creation methods, but
no way to access an XML reader/parser/Document builder in an
implementation-independent way.  There is also no well-defined way to
access these methods without an existing ‘Document’ object.  In Python,
each DOM implementation will provide a function *note
getDOMImplementation(): 35f3.  DOM Level 3 adds a Load/Store
specification, which defines an interface to the reader, but this is not
yet available in the Python standard library.

Once you have a DOM document object, you can access the parts of your
XML document through its properties and methods.  These properties are
defined in the DOM specification; this portion of the reference manual
describes the interpretation of the specification in Python.

The specification provided by the W3C defines the DOM API for Java,
ECMAScript, and OMG IDL. The Python mapping defined here is based in
large part on the IDL version of the specification, but strict
compliance is not required (though implementations are free to support
the strict mapping from IDL). See section *note Conformance: 35f4. for a
detailed discussion of mapping requirements.

也參考
......

Document Object Model (DOM) Level 2 Specification(2)

     The W3C recommendation upon which the Python DOM API is based.

Document Object Model (DOM) Level 1 Specification(3)

     The W3C recommendation for the DOM supported by *note
     xml.dom.minidom: 109.

Python Language Mapping Specification(4)

     This specifies the mapping from OMG IDL to Python.

* Menu:

* 模組內容: 模組內容<6>.
* Objects in the DOM::
* Conformance::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/xml/dom/__init__.py

   (2) https://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/

   (3) https://www.w3.org/TR/REC-DOM-Level-1/

   (4) https://www.omg.org/spec/PYTH/1.2/PDF


File: python.info,  Node: 模組內容<6>,  Next: Objects in the DOM,  Up: xml dom --- Document 物件模型 API

5.20.6.1 模組內容
.................

The *note xml.dom: 108. contains the following functions:

 -- 函式: xml.dom.registerDOMImplementation (name, factory)

     Register the 'factory' function with the name 'name'.  The factory
     function should return an object which implements the
     ‘DOMImplementation’ interface.  The factory function can return the
     same object every time, or a new one for each call, as appropriate
     for the specific implementation (e.g.  if that implementation
     supports some customization).

 -- 函式: xml.dom.getDOMImplementation (name=None, features=())

     Return a suitable DOM implementation.  The 'name' is either
     well-known, the module name of a DOM implementation, or ‘None’.  If
     it is not ‘None’, imports the corresponding module and returns a
     ‘DOMImplementation’ object if the import succeeds.  If no name is
     given, and if the environment variable ‘PYTHON_DOM’ is set, this
     variable is used to find the implementation.

     If name is not given, this examines the available implementations
     to find one with the required feature set.  If no implementation
     can be found, raise an *note ImportError: 352.  The features list
     must be a sequence of ‘(feature, version)’ pairs which are passed
     to the ‘hasFeature()’ method on available ‘DOMImplementation’
     objects.

Some convenience constants are also provided:

 -- 資料: xml.dom.EMPTY_NAMESPACE

     The value used to indicate that no namespace is associated with a
     node in the DOM. This is typically found as the ‘namespaceURI’ of a
     node, or used as the 'namespaceURI' parameter to a
     namespaces-specific method.

 -- 資料: xml.dom.XML_NAMESPACE

     The namespace URI associated with the reserved prefix ‘xml’, as
     defined by Namespaces in XML(1) (section 4).

 -- 資料: xml.dom.XMLNS_NAMESPACE

     The namespace URI for namespace declarations, as defined by
     Document Object Model (DOM) Level 2 Core Specification(2) (section
     1.1.8).

 -- 資料: xml.dom.XHTML_NAMESPACE

     The URI of the XHTML namespace as defined by XHTML 1.0: The
     Extensible HyperText Markup Language(3) (section 3.1.1).

In addition, *note xml.dom: 108. contains a base ‘Node’ class and the
DOM exception classes.  The ‘Node’ class provided by this module does
not implement any of the methods or attributes defined by the DOM
specification; concrete DOM implementations must provide those.  The
‘Node’ class provided as part of this module does provide the constants
used for the ‘nodeType’ attribute on concrete ‘Node’ objects; they are
located within the class rather than at the module level to conform with
the DOM specifications.

   ---------- Footnotes ----------

   (1) https://www.w3.org/TR/REC-xml-names/

   (2) https://www.w3.org/TR/DOM-Level-2-Core/core.html

   (3) https://www.w3.org/TR/xhtml1/


File: python.info,  Node: Objects in the DOM,  Next: Conformance,  Prev: 模組內容<6>,  Up: xml dom --- Document 物件模型 API

5.20.6.2 Objects in the DOM
...........................

The definitive documentation for the DOM is the DOM specification from
the W3C.

Note that DOM attributes may also be manipulated as nodes instead of as
simple strings.  It is fairly rare that you must do this, however, so
this usage is not yet documented.

Interface                            Section                                 Purpose
                                                                             
-------------------------------------------------------------------------------------------------------------------
                                                                             
‘DOMImplementation’                  *note DOMImplementation 物件: 35fd.     Interface to the underlying
                                                                             implementation.
                                                                             
                                                                             
‘Node’                               *note Node Objects: 35fe.               Base interface for most objects in
                                                                             a document.
                                                                             
                                                                             
‘NodeList’                           *note NodeList 物件: 35ff.              Interface for a sequence of nodes.
                                                                             
                                                                             
‘DocumentType’                       *note DocumentType 物件: 3600.          Information about the declarations
                                                                             needed to process a document.
                                                                             
                                                                             
‘Document’                           *note Document Objects: 3601.           Object which represents an entire
                                                                             document.
                                                                             
                                                                             
‘Element’                            *note Element Objects: 3602.            Element nodes in the document
                                                                             hierarchy.
                                                                             
                                                                             
‘Attr’                               *note Attr Objects: 3603.               Attribute value nodes on element
                                                                             nodes.
                                                                             
                                                                             
‘Comment’                            *note Comment Objects: 3604.            Representation of comments in the
                                                                             source document.
                                                                             
                                                                             
‘Text’                               *note Text and CDATASection Objects: 3605.Nodes containing textual content
                                                                             from the document.
                                                                             
                                                                             
‘ProcessingInstruction’              *note ProcessingInstruction 物件: 3606. Processing instruction
                                                                             representation.
                                                                             

An additional section describes the exceptions defined for working with
the DOM in Python.

* Menu:

* DOMImplementation 物件::
* Node Objects::
* NodeList 物件::
* DocumentType 物件::
* Document Objects::
* Element Objects::
* Attr Objects::
* NamedNodeMap 物件::
* Comment Objects::
* Text and CDATASection Objects::
* ProcessingInstruction 物件::
* 例外: 例外<15>.


File: python.info,  Node: DOMImplementation 物件,  Next: Node Objects,  Up: Objects in the DOM

5.20.6.3 DOMImplementation 物件
...............................

The ‘DOMImplementation’ interface provides a way for applications to
determine the availability of particular features in the DOM they are
using.  DOM Level 2 added the ability to create new ‘Document’ and
‘DocumentType’ objects using the ‘DOMImplementation’ as well.

 -- 方法: DOMImplementation.hasFeature (feature, version)

     Return ‘True’ if the feature identified by the pair of strings
     'feature' and 'version' is implemented.

 -- 方法: DOMImplementation.createDocument (namespaceUri, qualifiedName,
          doctype)

     Return a new ‘Document’ object (the root of the DOM), with a child
     ‘Element’ object having the given 'namespaceUri' and
     'qualifiedName'.  The 'doctype' must be a ‘DocumentType’ object
     created by *note createDocumentType(): 360a, or ‘None’.  In the
     Python DOM API, the first two arguments can also be ‘None’ in order
     to indicate that no ‘Element’ child is to be created.

 -- 方法: DOMImplementation.createDocumentType (qualifiedName, publicId,
          systemId)

     Return a new ‘DocumentType’ object that encapsulates the given
     'qualifiedName', 'publicId', and 'systemId' strings, representing
     the information contained in an XML document type declaration.


File: python.info,  Node: Node Objects,  Next: NodeList 物件,  Prev: DOMImplementation 物件,  Up: Objects in the DOM

5.20.6.4 Node Objects
.....................

All of the components of an XML document are subclasses of ‘Node’.

 -- 屬性: Node.nodeType

     An integer representing the node type.  Symbolic constants for the
     types are on the ‘Node’ object: ‘ELEMENT_NODE’, ‘ATTRIBUTE_NODE’,
     ‘TEXT_NODE’, ‘CDATA_SECTION_NODE’, ‘ENTITY_NODE’,
     ‘PROCESSING_INSTRUCTION_NODE’, ‘COMMENT_NODE’, ‘DOCUMENT_NODE’,
     ‘DOCUMENT_TYPE_NODE’, ‘NOTATION_NODE’.  This is a read-only
     attribute.

 -- 屬性: Node.parentNode

     The parent of the current node, or ‘None’ for the document node.
     The value is always a ‘Node’ object or ‘None’.  For ‘Element’
     nodes, this will be the parent element, except for the root
     element, in which case it will be the ‘Document’ object.  For
     ‘Attr’ nodes, this is always ‘None’.  This is a read-only
     attribute.

 -- 屬性: Node.attributes

     A ‘NamedNodeMap’ of attribute objects.  Only elements have actual
     values for this; others provide ‘None’ for this attribute.  This is
     a read-only attribute.

 -- 屬性: Node.previousSibling

     The node that immediately precedes this one with the same parent.
     For instance the element with an end-tag that comes just before the
     'self' element's start-tag.  Of course, XML documents are made up
     of more than just elements so the previous sibling could be text, a
     comment, or something else.  If this node is the first child of the
     parent, this attribute will be ‘None’.  This is a read-only
     attribute.

 -- 屬性: Node.nextSibling

     The node that immediately follows this one with the same parent.
     See also *note previousSibling: 360f.  If this is the last child of
     the parent, this attribute will be ‘None’.  This is a read-only
     attribute.

 -- 屬性: Node.childNodes

     A list of nodes contained within this node.  This is a read-only
     attribute.

 -- 屬性: Node.firstChild

     The first child of the node, if there are any, or ‘None’.  This is
     a read-only attribute.

 -- 屬性: Node.lastChild

     The last child of the node, if there are any, or ‘None’.  This is a
     read-only attribute.

 -- 屬性: Node.localName

     The part of the ‘tagName’ following the colon if there is one, else
     the entire ‘tagName’.  The value is a string.

 -- 屬性: Node.prefix

     The part of the ‘tagName’ preceding the colon if there is one, else
     the empty string.  The value is a string, or ‘None’.

 -- 屬性: Node.namespaceURI

     The namespace associated with the element name.  This will be a
     string or ‘None’.  This is a read-only attribute.

 -- 屬性: Node.nodeName

     This has a different meaning for each node type; see the DOM
     specification for details.  You can always get the information you
     would get here from another property such as the ‘tagName’ property
     for elements or the ‘name’ property for attributes.  For all node
     types, the value of this attribute will be either a string or
     ‘None’.  This is a read-only attribute.

 -- 屬性: Node.nodeValue

     This has a different meaning for each node type; see the DOM
     specification for details.  The situation is similar to that with
     *note nodeName: 3617.  The value is a string or ‘None’.

 -- 方法: Node.hasAttributes ()

     Return ‘True’ if the node has any attributes.

 -- 方法: Node.hasChildNodes ()

     Return ‘True’ if the node has any child nodes.

 -- 方法: Node.isSameNode (other)

     Return ‘True’ if 'other' refers to the same node as this node.
     This is especially useful for DOM implementations which use any
     sort of proxy architecture (because more than one object can refer
     to the same node).

          備註: This is based on a proposed DOM Level 3 API which is
          still in the "working draft" stage, but this particular
          interface appears uncontroversial.  Changes from the W3C will
          not necessarily affect this method in the Python DOM interface
          (though any new W3C API for this would also be supported).

 -- 方法: Node.appendChild (newChild)

     Add a new child node to this node at the end of the list of
     children, returning 'newChild'.  If the node was already in the
     tree, it is removed first.

 -- 方法: Node.insertBefore (newChild, refChild)

     Insert a new child node before an existing child.  It must be the
     case that 'refChild' is a child of this node; if not, *note
     ValueError: 1e7. is raised.  'newChild' is returned.  If 'refChild'
     is ‘None’, it inserts 'newChild' at the end of the children's list.

 -- 方法: Node.removeChild (oldChild)

     Remove a child node.  'oldChild' must be a child of this node; if
     not, *note ValueError: 1e7. is raised.  'oldChild' is returned on
     success.  If 'oldChild' will not be used further, its ‘unlink()’
     method should be called.

 -- 方法: Node.replaceChild (newChild, oldChild)

     Replace an existing node with a new node.  It must be the case that
     'oldChild' is a child of this node; if not, *note ValueError: 1e7.
     is raised.

 -- 方法: Node.normalize ()

     Join adjacent text nodes so that all stretches of text are stored
     as single ‘Text’ instances.  This simplifies processing text from a
     DOM tree for many applications.

 -- 方法: Node.cloneNode (deep)

     Clone this node.  Setting 'deep' means to clone all child nodes as
     well.  This returns the clone.


File: python.info,  Node: NodeList 物件,  Next: DocumentType 物件,  Prev: Node Objects,  Up: Objects in the DOM

5.20.6.5 NodeList 物件
......................

A ‘NodeList’ represents a sequence of nodes.  These objects are used in
two ways in the DOM Core recommendation: an ‘Element’ object provides
one as its list of child nodes, and the ‘getElementsByTagName()’ and
‘getElementsByTagNameNS()’ methods of ‘Node’ return objects with this
interface to represent query results.

The DOM Level 2 recommendation defines one method and one attribute for
these objects:

 -- 方法: NodeList.item (i)

     Return the 'i"th item from the sequence, if there is one, or
     ‘None’.  The index 'i' is not allowed to be less than zero or
     greater than or equal to the length of the sequence.

 -- 屬性: NodeList.length

     The number of nodes in the sequence.

In addition, the Python DOM interface requires that some additional
support is provided to allow ‘NodeList’ objects to be used as Python
sequences.  All ‘NodeList’ implementations must include support for
*note __len__(): 1e38. and *note __getitem__(): 266.; this allows
iteration over the ‘NodeList’ in *note for: 2c3. statements and proper
support for the *note len(): 5d4. built-in function.

If a DOM implementation supports modification of the document, the
‘NodeList’ implementation must also support the *note __setitem__():
1434. and *note __delitem__(): 1435. methods.


File: python.info,  Node: DocumentType 物件,  Next: Document Objects,  Prev: NodeList 物件,  Up: Objects in the DOM

5.20.6.6 DocumentType 物件
..........................

Information about the notations and entities declared by a document
(including the external subset if the parser uses it and can provide the
information) is available from a ‘DocumentType’ object.  The
‘DocumentType’ for a document is available from the ‘Document’ object's
‘doctype’ attribute; if there is no ‘DOCTYPE’ declaration for the
document, the document's ‘doctype’ attribute will be set to ‘None’
instead of an instance of this interface.

‘DocumentType’ is a specialization of ‘Node’, and adds the following
attributes:

 -- 屬性: DocumentType.publicId

     The public identifier for the external subset of the document type
     definition.  This will be a string or ‘None’.

 -- 屬性: DocumentType.systemId

     The system identifier for the external subset of the document type
     definition.  This will be a URI as a string, or ‘None’.

 -- 屬性: DocumentType.internalSubset

     A string giving the complete internal subset from the document.
     This does not include the brackets which enclose the subset.  If
     the document has no internal subset, this should be ‘None’.

 -- 屬性: DocumentType.name

     The name of the root element as given in the ‘DOCTYPE’ declaration,
     if present.

 -- 屬性: DocumentType.entities

     This is a ‘NamedNodeMap’ giving the definitions of external
     entities.  For entity names defined more than once, only the first
     definition is provided (others are ignored as required by the XML
     recommendation).  This may be ‘None’ if the information is not
     provided by the parser, or if no entities are defined.

 -- 屬性: DocumentType.notations

     This is a ‘NamedNodeMap’ giving the definitions of notations.  For
     notation names defined more than once, only the first definition is
     provided (others are ignored as required by the XML
     recommendation).  This may be ‘None’ if the information is not
     provided by the parser, or if no notations are defined.


File: python.info,  Node: Document Objects,  Next: Element Objects,  Prev: DocumentType 物件,  Up: Objects in the DOM

5.20.6.7 Document Objects
.........................

A ‘Document’ represents an entire XML document, including its
constituent elements, attributes, processing instructions, comments etc.
Remember that it inherits properties from ‘Node’.

 -- 屬性: Document.documentElement

     The one and only root element of the document.

 -- 方法: Document.createElement (tagName)

     Create and return a new element node.  The element is not inserted
     into the document when it is created.  You need to explicitly
     insert it with one of the other methods such as ‘insertBefore()’ or
     ‘appendChild()’.

 -- 方法: Document.createElementNS (namespaceURI, tagName)

     Create and return a new element with a namespace.  The 'tagName'
     may have a prefix.  The element is not inserted into the document
     when it is created.  You need to explicitly insert it with one of
     the other methods such as ‘insertBefore()’ or ‘appendChild()’.

 -- 方法: Document.createTextNode (data)

     Create and return a text node containing the data passed as a
     parameter.  As with the other creation methods, this one does not
     insert the node into the tree.

 -- 方法: Document.createComment (data)

     Create and return a comment node containing the data passed as a
     parameter.  As with the other creation methods, this one does not
     insert the node into the tree.

 -- 方法: Document.createProcessingInstruction (target, data)

     Create and return a processing instruction node containing the
     'target' and 'data' passed as parameters.  As with the other
     creation methods, this one does not insert the node into the tree.

 -- 方法: Document.createAttribute (name)

     Create and return an attribute node.  This method does not
     associate the attribute node with any particular element.  You must
     use ‘setAttributeNode()’ on the appropriate ‘Element’ object to use
     the newly created attribute instance.

 -- 方法: Document.createAttributeNS (namespaceURI, qualifiedName)

     Create and return an attribute node with a namespace.  The
     'tagName' may have a prefix.  This method does not associate the
     attribute node with any particular element.  You must use
     ‘setAttributeNode()’ on the appropriate ‘Element’ object to use the
     newly created attribute instance.

 -- 方法: Document.getElementsByTagName (tagName)

     Search for all descendants (direct children, children's children,
     etc.)  with a particular element type name.

 -- 方法: Document.getElementsByTagNameNS (namespaceURI, localName)

     Search for all descendants (direct children, children's children,
     etc.)  with a particular namespace URI and localname.  The
     localname is the part of the namespace after the prefix.


File: python.info,  Node: Element Objects,  Next: Attr Objects,  Prev: Document Objects,  Up: Objects in the DOM

5.20.6.8 Element Objects
........................

‘Element’ is a subclass of ‘Node’, so inherits all the attributes of
that class.

 -- 屬性: Element.tagName

     The element type name.  In a namespace-using document it may have
     colons in it.  The value is a string.

 -- 方法: Element.getElementsByTagName (tagName)

     Same as equivalent method in the ‘Document’ class.

 -- 方法: Element.getElementsByTagNameNS (namespaceURI, localName)

     Same as equivalent method in the ‘Document’ class.

 -- 方法: Element.hasAttribute (name)

     Return ‘True’ if the element has an attribute named by 'name'.

 -- 方法: Element.hasAttributeNS (namespaceURI, localName)

     Return ‘True’ if the element has an attribute named by
     'namespaceURI' and 'localName'.

 -- 方法: Element.getAttribute (name)

     Return the value of the attribute named by 'name' as a string.  If
     no such attribute exists, an empty string is returned, as if the
     attribute had no value.

 -- 方法: Element.getAttributeNode (attrname)

     Return the ‘Attr’ node for the attribute named by 'attrname'.

 -- 方法: Element.getAttributeNS (namespaceURI, localName)

     Return the value of the attribute named by 'namespaceURI' and
     'localName' as a string.  If no such attribute exists, an empty
     string is returned, as if the attribute had no value.

 -- 方法: Element.getAttributeNodeNS (namespaceURI, localName)

     Return an attribute value as a node, given a 'namespaceURI' and
     'localName'.

 -- 方法: Element.removeAttribute (name)

     Remove an attribute by name.  If there is no matching attribute, a
     *note NotFoundErr: 3642. is raised.

 -- 方法: Element.removeAttributeNode (oldAttr)

     Remove and return 'oldAttr' from the attribute list, if present.
     If 'oldAttr' is not present, *note NotFoundErr: 3642. is raised.

 -- 方法: Element.removeAttributeNS (namespaceURI, localName)

     Remove an attribute by name.  Note that it uses a localName, not a
     qname.  No exception is raised if there is no matching attribute.

 -- 方法: Element.setAttribute (name, value)

     Set an attribute value from a string.

 -- 方法: Element.setAttributeNode (newAttr)

     Add a new attribute node to the element, replacing an existing
     attribute if necessary if the ‘name’ attribute matches.  If a
     replacement occurs, the old attribute node will be returned.  If
     'newAttr' is already in use, *note InuseAttributeErr: 3647. will be
     raised.

 -- 方法: Element.setAttributeNodeNS (newAttr)

     Add a new attribute node to the element, replacing an existing
     attribute if necessary if the ‘namespaceURI’ and ‘localName’
     attributes match.  If a replacement occurs, the old attribute node
     will be returned.  If 'newAttr' is already in use, *note
     InuseAttributeErr: 3647. will be raised.

 -- 方法: Element.setAttributeNS (namespaceURI, qname, value)

     Set an attribute value from a string, given a 'namespaceURI' and a
     'qname'.  Note that a qname is the whole attribute name.  This is
     different than above.


File: python.info,  Node: Attr Objects,  Next: NamedNodeMap 物件,  Prev: Element Objects,  Up: Objects in the DOM

5.20.6.9 Attr Objects
.....................

‘Attr’ inherits from ‘Node’, so inherits all its attributes.

 -- 屬性: Attr.name

     The attribute name.  In a namespace-using document it may include a
     colon.

 -- 屬性: Attr.localName

     The part of the name following the colon if there is one, else the
     entire name.  This is a read-only attribute.

 -- 屬性: Attr.prefix

     The part of the name preceding the colon if there is one, else the
     empty string.

 -- 屬性: Attr.value

     The text value of the attribute.  This is a synonym for the
     ‘nodeValue’ attribute.


File: python.info,  Node: NamedNodeMap 物件,  Next: Comment Objects,  Prev: Attr Objects,  Up: Objects in the DOM

5.20.6.10 NamedNodeMap 物件
...........................

‘NamedNodeMap’ does 'not' inherit from ‘Node’.

 -- 屬性: NamedNodeMap.length

     The length of the attribute list.

 -- 方法: NamedNodeMap.item (index)

     Return an attribute with a particular index.  The order you get the
     attributes in is arbitrary but will be consistent for the life of a
     DOM. Each item is an attribute node.  Get its value with the
     ‘value’ attribute.

There are also experimental methods that give this class more mapping
behavior.  You can use them or you can use the standardized
‘getAttribute*()’ family of methods on the ‘Element’ objects.


File: python.info,  Node: Comment Objects,  Next: Text and CDATASection Objects,  Prev: NamedNodeMap 物件,  Up: Objects in the DOM

5.20.6.11 Comment Objects
.........................

‘Comment’ represents a comment in the XML document.  It is a subclass of
‘Node’, but cannot have child nodes.

 -- 屬性: Comment.data

     The content of the comment as a string.  The attribute contains all
     characters between the leading ‘<!-’‘-’ and trailing ‘-’‘->’, but
     does not include them.


File: python.info,  Node: Text and CDATASection Objects,  Next: ProcessingInstruction 物件,  Prev: Comment Objects,  Up: Objects in the DOM

5.20.6.12 Text and CDATASection Objects
.......................................

The ‘Text’ interface represents text in the XML document.  If the parser
and DOM implementation support the DOM's XML extension, portions of the
text enclosed in CDATA marked sections are stored in ‘CDATASection’
objects.  These two interfaces are identical, but provide different
values for the ‘nodeType’ attribute.

These interfaces extend the ‘Node’ interface.  They cannot have child
nodes.

 -- 屬性: Text.data

     The content of the text node as a string.

     備註: The use of a ‘CDATASection’ node does not indicate that the
     node represents a complete CDATA marked section, only that the
     content of the node was part of a CDATA section.  A single CDATA
     section may be represented by more than one node in the document
     tree.  There is no way to determine whether two adjacent
     ‘CDATASection’ nodes represent different CDATA marked sections.


File: python.info,  Node: ProcessingInstruction 物件,  Next: 例外<15>,  Prev: Text and CDATASection Objects,  Up: Objects in the DOM

5.20.6.13 ProcessingInstruction 物件
....................................

Represents a processing instruction in the XML document; this inherits
from the ‘Node’ interface and cannot have child nodes.

 -- 屬性: ProcessingInstruction.target

     The content of the processing instruction up to the first
     whitespace character.  This is a read-only attribute.

 -- 屬性: ProcessingInstruction.data

     The content of the processing instruction following the first
     whitespace character.


File: python.info,  Node: 例外<15>,  Prev: ProcessingInstruction 物件,  Up: Objects in the DOM

5.20.6.14 例外
..............

The DOM Level 2 recommendation defines a single exception, *note
DOMException: 365c, and a number of constants that allow applications to
determine what sort of error occurred.  *note DOMException: 365c.
instances carry a *note code: 13. attribute that provides the
appropriate value for the specific exception.

The Python DOM interface provides the constants, but also expands the
set of exceptions so that a specific exception exists for each of the
exception codes defined by the DOM. The implementations must raise the
appropriate specific exception, each of which carries the appropriate
value for the *note code: 13. attribute.

 -- 例外: xml.dom.DOMException

     Base exception class used for all specific DOM exceptions.  This
     exception class cannot be directly instantiated.

 -- 例外: xml.dom.DomstringSizeErr

     Raised when a specified range of text does not fit into a string.
     This is not known to be used in the Python DOM implementations, but
     may be received from DOM implementations not written in Python.

 -- 例外: xml.dom.HierarchyRequestErr

     Raised when an attempt is made to insert a node where the node type
     is not allowed.

 -- 例外: xml.dom.IndexSizeErr

     Raised when an index or size parameter to a method is negative or
     exceeds the allowed values.

 -- 例外: xml.dom.InuseAttributeErr

     Raised when an attempt is made to insert an ‘Attr’ node that is
     already present elsewhere in the document.

 -- 例外: xml.dom.InvalidAccessErr

     Raised if a parameter or an operation is not supported on the
     underlying object.

 -- 例外: xml.dom.InvalidCharacterErr

     This exception is raised when a string parameter contains a
     character that is not permitted in the context it's being used in
     by the XML 1.0 recommendation.  For example, attempting to create
     an ‘Element’ node with a space in the element type name will cause
     this error to be raised.

 -- 例外: xml.dom.InvalidModificationErr

     Raised when an attempt is made to modify the type of a node.

 -- 例外: xml.dom.InvalidStateErr

     Raised when an attempt is made to use an object that is not defined
     or is no longer usable.

 -- 例外: xml.dom.NamespaceErr

     If an attempt is made to change any object in a way that is not
     permitted with regard to the Namespaces in XML(1) recommendation,
     this exception is raised.

 -- 例外: xml.dom.NotFoundErr

     Exception when a node does not exist in the referenced context.
     For example, ‘NamedNodeMap.removeNamedItem()’ will raise this if
     the node passed in does not exist in the map.

 -- 例外: xml.dom.NotSupportedErr

     Raised when the implementation does not support the requested type
     of object or operation.

 -- 例外: xml.dom.NoDataAllowedErr

     This is raised if data is specified for a node which does not
     support data.

 -- 例外: xml.dom.NoModificationAllowedErr

     Raised on attempts to modify an object where modifications are not
     allowed (such as for read-only nodes).

 -- 例外: xml.dom.SyntaxErr

     Raised when an invalid or illegal string is specified.

 -- 例外: xml.dom.WrongDocumentErr

     Raised when a node is inserted in a different document than it
     currently belongs to, and the implementation does not support
     migrating the node from one document to the other.

The exception codes defined in the DOM recommendation map to the
exceptions described above according to this table:

常數                                       例外
                                           
---------------------------------------------------------------------------------
                                           
‘DOMSTRING_SIZE_ERR’                       *note DomstringSizeErr: 365d.
                                           
                                           
‘HIERARCHY_REQUEST_ERR’                    *note HierarchyRequestErr: 365e.
                                           
                                           
‘INDEX_SIZE_ERR’                           *note IndexSizeErr: 365f.
                                           
                                           
‘INUSE_ATTRIBUTE_ERR’                      *note InuseAttributeErr: 3647.
                                           
                                           
‘INVALID_ACCESS_ERR’                       *note InvalidAccessErr: 3660.
                                           
                                           
‘INVALID_CHARACTER_ERR’                    *note InvalidCharacterErr: 3661.
                                           
                                           
‘INVALID_MODIFICATION_ERR’                 *note InvalidModificationErr: 3662.
                                           
                                           
‘INVALID_STATE_ERR’                        *note InvalidStateErr: 3663.
                                           
                                           
‘NAMESPACE_ERR’                            *note NamespaceErr: 3664.
                                           
                                           
‘NOT_FOUND_ERR’                            *note NotFoundErr: 3642.
                                           
                                           
‘NOT_SUPPORTED_ERR’                        *note NotSupportedErr: 3665.
                                           
                                           
‘NO_DATA_ALLOWED_ERR’                      *note NoDataAllowedErr: 3666.
                                           
                                           
‘NO_MODIFICATION_ALLOWED_ERR’              *note NoModificationAllowedErr: 3667.
                                           
                                           
‘SYNTAX_ERR’                               *note SyntaxErr: 3668.
                                           
                                           
‘WRONG_DOCUMENT_ERR’                       *note WrongDocumentErr: 3669.
                                           

   ---------- Footnotes ----------

   (1) https://www.w3.org/TR/REC-xml-names/


File: python.info,  Node: Conformance,  Prev: Objects in the DOM,  Up: xml dom --- Document 物件模型 API

5.20.6.15 Conformance
.....................

This section describes the conformance requirements and relationships
between the Python DOM API, the W3C DOM recommendations, and the OMG IDL
mapping for Python.

* Menu:

* Type Mapping::
* Accessor Methods::


File: python.info,  Node: Type Mapping,  Next: Accessor Methods,  Up: Conformance

5.20.6.16 Type Mapping
......................

The IDL types used in the DOM specification are mapped to Python types
according to the following table.

IDL Type               Python Type
                       
-----------------------------------------------------------------------
                       
‘boolean’              ‘bool’ 或 ‘int’
                       
                       
‘int’                  ‘int’
                       
                       
‘long int’             ‘int’
                       
                       
‘unsigned int’         ‘int’
                       
                       
‘DOMString’            ‘str’ 或 ‘bytes’
                       
                       
‘null’                 ‘None’
                       


File: python.info,  Node: Accessor Methods,  Prev: Type Mapping,  Up: Conformance

5.20.6.17 Accessor Methods
..........................

The mapping from OMG IDL to Python defines accessor functions for IDL
‘attribute’ declarations in much the way the Java mapping does.  Mapping
the IDL declarations

     readonly attribute string someValue;
              attribute string anotherValue;

yields three accessor functions: a "get" method for ‘someValue’
(‘_get_someValue()’), and "get" and "set" methods for ‘anotherValue’
(‘_get_anotherValue()’ and ‘_set_anotherValue()’).  The mapping, in
particular, does not require that the IDL attributes are accessible as
normal Python attributes: ‘object.someValue’ is 'not' required to work,
and may raise an *note AttributeError: 2f6.

The Python DOM API, however, 'does' require that normal attribute access
work.  This means that the typical surrogates generated by Python IDL
compilers are not likely to work, and wrapper objects may be needed on
the client if the DOM objects are accessed via CORBA. While this does
require some additional consideration for CORBA DOM clients, the
implementers with experience using DOM over CORBA from Python do not
consider this a problem.  Attributes that are declared ‘readonly’ may
not restrict write access in all DOM implementations.

In the Python DOM API, accessor functions are not required.  If
provided, they should take the form defined by the Python IDL mapping,
but these methods are considered unnecessary since the attributes are
accessible directly from Python.  "Set" accessors should never be
provided for ‘readonly’ attributes.

The IDL definitions do not fully embody the requirements of the W3C DOM
API, such as the notion of certain objects, such as the return value of
‘getElementsByTagName()’, being "live".  The Python DOM API does not
require implementations to enforce such requirements.


File: python.info,  Node: xml dom minidom --- 最小的 DOM 實作,  Next: xml dom pulldom --- 支援建置部分 DOM 樹,  Prev: xml dom --- Document 物件模型 API,  Up: Structured Markup Processing Tools

5.20.7 ‘xml.dom.minidom’ -- 最小的 DOM 實作
-------------------------------------------

'原始碼：'Lib/xml/dom/minidom.py(1)

__________________________________________________________________

*note xml.dom.minidom: 109. is a minimal implementation of the Document
Object Model interface, with an API similar to that in other languages.
It is intended to be simpler than the full DOM and also significantly
smaller.  Users who are not already proficient with the DOM should
consider using the *note xml.etree.ElementTree: 10c. module for their
XML processing instead.

     警告: The *note xml.dom.minidom: 109. module is not secure against
     maliciously constructed data.  If you need to parse untrusted or
     unauthenticated data see *note XML 漏洞: 3596.

DOM applications typically start by parsing some XML into a DOM. With
*note xml.dom.minidom: 109, this is done through the parse functions:

     from xml.dom.minidom import parse, parseString

     dom1 = parse('c:\\temp\\mydata.xml')  # parse an XML file by name

     datasource = open('c:\\temp\\mydata.xml')
     dom2 = parse(datasource)  # parse an open file

     dom3 = parseString('<myxml>Some data<empty/> some more data</myxml>')

The *note parse(): 3671. function can take either a filename or an open
file object.

 -- 函式: xml.dom.minidom.parse (filename_or_file, parser=None,
          bufsize=None)

     Return a ‘Document’ from the given input.  'filename_or_file' may
     be either a file name, or a file-like object.  'parser', if given,
     must be a SAX2 parser object.  This function will change the
     document handler of the parser and activate namespace support;
     other parser configuration (like setting an entity resolver) must
     have been done in advance.

If you have XML in a string, you can use the *note parseString(): 3672.
function instead:

 -- 函式: xml.dom.minidom.parseString (string, parser=None)

     Return a ‘Document’ that represents the 'string'.  This method
     creates an *note io.StringIO: ecb. object for the string and passes
     that on to *note parse(): 3671.

Both functions return a ‘Document’ object representing the content of
the document.

What the *note parse(): 3671. and *note parseString(): 3672. functions
do is connect an XML parser with a "DOM builder" that can accept parse
events from any SAX parser and convert them into a DOM tree.  The name
of the functions are perhaps misleading, but are easy to grasp when
learning the interfaces.  The parsing of the document will be completed
before these functions return; it's simply that these functions do not
provide a parser implementation themselves.

You can also create a ‘Document’ by calling a method on a "DOM
Implementation" object.  You can get this object either by calling the
‘getDOMImplementation()’ function in the *note xml.dom: 108. package or
the *note xml.dom.minidom: 109. module.  Once you have a ‘Document’, you
can add child nodes to it to populate the DOM:

     from xml.dom.minidom import getDOMImplementation

     impl = getDOMImplementation()

     newdoc = impl.createDocument(None, "some_tag", None)
     top_element = newdoc.documentElement
     text = newdoc.createTextNode('Some textual content.')
     top_element.appendChild(text)

Once you have a DOM document object, you can access the parts of your
XML document through its properties and methods.  These properties are
defined in the DOM specification.  The main property of the document
object is the ‘documentElement’ property.  It gives you the main element
in the XML document: the one that holds all others.  Here is an example
program:

     dom3 = parseString("<myxml>Some data</myxml>")
     assert dom3.documentElement.tagName == "myxml"

When you are finished with a DOM tree, you may optionally call the
‘unlink()’ method to encourage early cleanup of the now-unneeded
objects.  ‘unlink()’ is an *note xml.dom.minidom: 109.-specific
extension to the DOM API that renders the node and its descendants
essentially useless.  Otherwise, Python's garbage collector will
eventually take care of the objects in the tree.

也參考
......

Document Object Model (DOM) Level 1 Specification(2)

     The W3C recommendation for the DOM supported by *note
     xml.dom.minidom: 109.

* Menu:

* DOM 物件::
* DOM 範例::
* minidom and the DOM standard::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/xml/dom/minidom.py

   (2) https://www.w3.org/TR/REC-DOM-Level-1/


File: python.info,  Node: DOM 物件,  Next: DOM 範例,  Up: xml dom minidom --- 最小的 DOM 實作

5.20.7.1 DOM 物件
.................

The definition of the DOM API for Python is given as part of the *note
xml.dom: 108. module documentation.  This section lists the differences
between the API and *note xml.dom.minidom: 109.

 -- 方法: Node.unlink ()

     Break internal references within the DOM so that it will be garbage
     collected on versions of Python without cyclic GC. Even when cyclic
     GC is available, using this can make large amounts of memory
     available sooner, so calling this on DOM objects as soon as they
     are no longer needed is good practice.  This only needs to be
     called on the ‘Document’ object, but may be called on child nodes
     to discard children of that node.

     You can avoid calling this method explicitly by using the *note
     with: 577. statement.  The following code will automatically unlink
     'dom' when the ‘with’ block is exited:

          with xml.dom.minidom.parse(datasource) as dom:
              ... # Work with dom.

 -- 方法: Node.writexml (writer, indent='', addindent='', newl='',
          encoding=None, standalone=None)

     Write XML to the writer object.  The writer receives texts but not
     bytes as input, it should have a ‘write()’ method which matches
     that of the file object interface.  The 'indent' parameter is the
     indentation of the current node.  The 'addindent' parameter is the
     incremental indentation to use for subnodes of the current one.
     The 'newl' parameter specifies the string to use to terminate
     newlines.

     For the ‘Document’ node, an additional keyword argument 'encoding'
     can be used to specify the encoding field of the XML header.

     Similarly, explicitly stating the 'standalone' argument causes the
     standalone document declarations to be added to the prologue of the
     XML document.  If the value is set to ‘True’, ‘standalone="yes"’ is
     added, otherwise it is set to ‘"no"’.  Not stating the argument
     will omit the declaration from the document.

     在 3.8 版的變更: The *note writexml(): 3676. method now preserves
     the attribute order specified by the user.

     在 3.9 版的變更: 新增 'standalone' 參數。

 -- 方法: Node.toxml (encoding=None, standalone=None)

     Return a string or byte string containing the XML represented by
     the DOM node.

     With an explicit 'encoding' (1) argument, the result is a byte
     string in the specified encoding.  With no 'encoding' argument, the
     result is a Unicode string, and the XML declaration in the
     resulting string does not specify an encoding.  Encoding this
     string in an encoding other than UTF-8 is likely incorrect, since
     UTF-8 is the default encoding of XML.

     The 'standalone' argument behaves exactly as in *note writexml():
     3676.

     在 3.8 版的變更: The *note toxml(): 1436. method now preserves the
     attribute order specified by the user.

     在 3.9 版的變更: 新增 'standalone' 參數。

 -- 方法: Node.toprettyxml (indent='\t', newl='\n', encoding=None,
          standalone=None)

     Return a pretty-printed version of the document.  'indent'
     specifies the indentation string and defaults to a tabulator;
     'newl' specifies the string emitted at the end of each line and
     defaults to ‘\n’.

     The 'encoding' argument behaves like the corresponding argument of
     *note toxml(): 1436.

     The 'standalone' argument behaves exactly as in *note writexml():
     3676.

     在 3.8 版的變更: The *note toprettyxml(): 1437. method now
     preserves the attribute order specified by the user.

     在 3.9 版的變更: 新增 'standalone' 參數。

   ---------- Footnotes ----------

   (1) The encoding name included in the XML output should conform to
the appropriate standards.  For example, "UTF-8" is valid, but "UTF8" is
not valid in an XML document's declaration, even though Python accepts
it as an encoding name.  See
‘https://www.w3.org/TR/2006/REC-xml11-20060816/#NT-EncodingDecl’ and
‘https://www.iana.org/assignments/character-sets/character-sets.xhtml’.


File: python.info,  Node: DOM 範例,  Next: minidom and the DOM standard,  Prev: DOM 物件,  Up: xml dom minidom --- 最小的 DOM 實作

5.20.7.2 DOM 範例
.................

This example program is a fairly realistic example of a simple program.
In this particular case, we do not take much advantage of the
flexibility of the DOM.

     import xml.dom.minidom

     document = """\
     <slideshow>
     <title>Demo slideshow</title>
     <slide><title>Slide title</title>
     <point>This is a demo</point>
     <point>Of a program for processing slides</point>
     </slide>

     <slide><title>Another demo slide</title>
     <point>It is important</point>
     <point>To have more than</point>
     <point>one slide</point>
     </slide>
     </slideshow>
     """

     dom = xml.dom.minidom.parseString(document)

     def getText(nodelist):
         rc = []
         for node in nodelist:
             if node.nodeType == node.TEXT_NODE:
                 rc.append(node.data)
         return ''.join(rc)

     def handleSlideshow(slideshow):
         print("<html>")
         handleSlideshowTitle(slideshow.getElementsByTagName("title")[0])
         slides = slideshow.getElementsByTagName("slide")
         handleToc(slides)
         handleSlides(slides)
         print("</html>")

     def handleSlides(slides):
         for slide in slides:
             handleSlide(slide)

     def handleSlide(slide):
         handleSlideTitle(slide.getElementsByTagName("title")[0])
         handlePoints(slide.getElementsByTagName("point"))

     def handleSlideshowTitle(title):
         print(f"<title>{getText(title.childNodes)}</title>")

     def handleSlideTitle(title):
         print(f"<h2>{getText(title.childNodes)}</h2>")

     def handlePoints(points):
         print("<ul>")
         for point in points:
             handlePoint(point)
         print("</ul>")

     def handlePoint(point):
         print(f"<li>{getText(point.childNodes)}</li>")

     def handleToc(slides):
         for slide in slides:
             title = slide.getElementsByTagName("title")[0]
             print(f"<p>{getText(title.childNodes)}</p>")

     handleSlideshow(dom)


File: python.info,  Node: minidom and the DOM standard,  Prev: DOM 範例,  Up: xml dom minidom --- 最小的 DOM 實作

5.20.7.3 minidom and the DOM standard
.....................................

The *note xml.dom.minidom: 109. module is essentially a DOM
1.0-compatible DOM with some DOM 2 features (primarily namespace
features).

Usage of the DOM interface in Python is straight-forward.  The following
mapping rules apply:

   * Interfaces are accessed through instance objects.  Applications
     should not instantiate the classes themselves; they should use the
     creator functions available on the ‘Document’ object.  Derived
     interfaces support all operations (and attributes) from the base
     interfaces, plus any new operations.

   * Operations are used as methods.  Since the DOM uses only *note in:
     2c5. parameters, the arguments are passed in normal order (from
     left to right).  There are no optional arguments.  ‘void’
     operations return ‘None’.

   * IDL attributes map to instance attributes.  For compatibility with
     the OMG IDL language mapping for Python, an attribute ‘foo’ can
     also be accessed through accessor methods ‘_get_foo()’ and
     ‘_set_foo()’.  ‘readonly’ attributes must not be changed; this is
     not enforced at runtime.

   * The types ‘short int’, ‘unsigned int’, ‘unsigned long long’, and
     ‘boolean’ all map to Python integer objects.

   * The type ‘DOMString’ maps to Python strings.  *note
     xml.dom.minidom: 109. supports either bytes or strings, but will
     normally produce strings.  Values of type ‘DOMString’ may also be
     ‘None’ where allowed to have the IDL ‘null’ value by the DOM
     specification from the W3C.

   * ‘const’ declarations map to variables in their respective scope
     (e.g.  ‘xml.dom.minidom.Node.PROCESSING_INSTRUCTION_NODE’); they
     must not be changed.

   * ‘DOMException’ is currently not supported in *note xml.dom.minidom:
     109.  Instead, *note xml.dom.minidom: 109. uses standard Python
     exceptions such as *note TypeError: 4dd. and *note AttributeError:
     2f6.

   * ‘NodeList’ objects are implemented using Python's built-in list
     type.  These objects provide the interface defined in the DOM
     specification, but with earlier versions of Python they do not
     support the official API. They are, however, much more "Pythonic"
     than the interface defined in the W3C recommendations.

The following interfaces have no implementation in *note
xml.dom.minidom: 109.:

   * ‘DOMTimeStamp’

   * ‘EntityReference’

Most of these reflect information in the XML document that is not of
general utility to most DOM users.

註解
....


File: python.info,  Node: xml dom pulldom --- 支援建置部分 DOM 樹,  Next: xml sax --- SAX2 剖析器支援,  Prev: xml dom minidom --- 最小的 DOM 實作,  Up: Structured Markup Processing Tools

5.20.8 ‘xml.dom.pulldom’ -- 支援建置部分 DOM 樹
-----------------------------------------------

'原始碼：'Lib/xml/dom/pulldom.py(1)

__________________________________________________________________

The *note xml.dom.pulldom: 10a. module provides a "pull parser" which
can also be asked to produce DOM-accessible fragments of the document
where necessary.  The basic concept involves pulling "events" from a
stream of incoming XML and processing them.  In contrast to SAX which
also employs an event-driven processing model together with callbacks,
the user of a pull parser is responsible for explicitly pulling events
from the stream, looping over those events until either processing is
finished or an error condition occurs.

     警告: The *note xml.dom.pulldom: 10a. module is not secure against
     maliciously constructed data.  If you need to parse untrusted or
     unauthenticated data see *note XML 漏洞: 3596.

在 3.7.1 版的變更: The SAX parser no longer processes general external
entities by default to increase security by default.  To enable
processing of external entities, pass a custom parser instance in:

     from xml.dom.pulldom import parse
     from xml.sax import make_parser
     from xml.sax.handler import feature_external_ges

     parser = make_parser()
     parser.setFeature(feature_external_ges, True)
     parse(filename, parser=parser)

範例：

     from xml.dom import pulldom

     doc = pulldom.parse('sales_items.xml')
     for event, node in doc:
         if event == pulldom.START_ELEMENT and node.tagName == 'item':
             if int(node.getAttribute('price')) > 50:
                 doc.expandNode(node)
                 print(node.toxml())

‘event’ is a constant and can be one of:

   * ‘START_ELEMENT’

   * ‘END_ELEMENT’

   * ‘COMMENT’

   * ‘START_DOCUMENT’

   * ‘END_DOCUMENT’

   * ‘CHARACTERS’

   * ‘PROCESSING_INSTRUCTION’

   * ‘IGNORABLE_WHITESPACE’

‘node’ is an object of type ‘xml.dom.minidom.Document’,
‘xml.dom.minidom.Element’ or ‘xml.dom.minidom.Text’.

Since the document is treated as a "flat" stream of events, the document
"tree" is implicitly traversed and the desired elements are found
regardless of their depth in the tree.  In other words, one does not
need to consider hierarchical issues such as recursive searching of the
document nodes, although if the context of elements were important, one
would either need to maintain some context-related state (i.e.
remembering where one is in the document at any given point) or to make
use of the *note DOMEventStream.expandNode(): 367d. method and switch to
DOM-related processing.

 -- 類別: xml.dom.pulldom.PullDom (documentFactory=None)

     Subclass of *note xml.sax.handler.ContentHandler: 367f.

 -- 類別: xml.dom.pulldom.SAX2DOM (documentFactory=None)

     Subclass of *note xml.sax.handler.ContentHandler: 367f.

 -- 函式: xml.dom.pulldom.parse (stream_or_string, parser=None,
          bufsize=None)

     Return a *note DOMEventStream: 6d9. from the given input.
     'stream_or_string' may be either a file name, or a file-like
     object.  'parser', if given, must be an *note XMLReader: 3682.
     object.  This function will change the document handler of the
     parser and activate namespace support; other parser configuration
     (like setting an entity resolver) must have been done in advance.

If you have XML in a string, you can use the *note parseString(): 3683.
function instead:

 -- 函式: xml.dom.pulldom.parseString (string, parser=None)

     Return a *note DOMEventStream: 6d9. that represents the (Unicode)
     'string'.

 -- 資料: xml.dom.pulldom.default_bufsize

     Default value for the 'bufsize' parameter to *note parse(): 3681.

     The value of this variable can be changed before calling *note
     parse(): 3681. and the new value will take effect.

* Menu:

* DOMEventStream 物件::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/xml/dom/pulldom.py


File: python.info,  Node: DOMEventStream 物件,  Up: xml dom pulldom --- 支援建置部分 DOM 樹

5.20.8.1 DOMEventStream 物件
............................

 -- 類別: xml.dom.pulldom.DOMEventStream (stream, parser, bufsize)

     在 3.11 版的變更: Support for *note __getitem__(): 266. method has
     been removed.

      -- 方法: getEvent ()

          Return a tuple containing 'event' and the current 'node' as
          ‘xml.dom.minidom.Document’ if event equals ‘START_DOCUMENT’,
          ‘xml.dom.minidom.Element’ if event equals ‘START_ELEMENT’ or
          ‘END_ELEMENT’ or ‘xml.dom.minidom.Text’ if event equals
          ‘CHARACTERS’.  The current node does not contain information
          about its children, unless *note expandNode(): 367d. is
          called.

      -- 方法: expandNode (node)

          Expands all children of 'node' into 'node'.  Example:

               from xml.dom import pulldom

               xml = '<html><title>Foo</title> <p>Some text <div>and more</div></p> </html>'
               doc = pulldom.parseString(xml)
               for event, node in doc:
                   if event == pulldom.START_ELEMENT and node.tagName == 'p':
                       # Following statement only prints '<p/>'
                       print(node.toxml())
                       doc.expandNode(node)
                       # Following statement prints node with all its children '<p>Some text <div>and more</div></p>'
                       print(node.toxml())

      -- 方法: reset ()


File: python.info,  Node: xml sax --- SAX2 剖析器支援,  Next: xml sax handler --- SAX 處理函式的基本類別,  Prev: xml dom pulldom --- 支援建置部分 DOM 樹,  Up: Structured Markup Processing Tools

5.20.9 ‘xml.sax’ -- SAX2 剖析器支援
-----------------------------------

'原始碼：'Lib/xml/sax/__init__.py(1)

__________________________________________________________________

The *note xml.sax: 110. package provides a number of modules which
implement the Simple API for XML (SAX) interface for Python.  The
package itself provides the SAX exceptions and the convenience functions
which will be most used by users of the SAX API.

     警告: The *note xml.sax: 110. module is not secure against
     maliciously constructed data.  If you need to parse untrusted or
     unauthenticated data see *note XML 漏洞: 3596.

在 3.7.1 版的變更: The SAX parser no longer processes general external
entities by default to increase security.  Before, the parser created
network connections to fetch remote files or loaded local files from the
file system for DTD and entities.  The feature can be enabled again with
method *note setFeature(): 368b. on the parser object and argument *note
feature_external_ges: 368c.

The convenience functions are:

 -- 函式: xml.sax.make_parser (parser_list=[])

     Create and return a SAX *note XMLReader: 3682. object.  The first
     parser found will be used.  If 'parser_list' is provided, it must
     be an iterable of strings which name modules that have a function
     named ‘create_parser()’.  Modules listed in 'parser_list' will be
     used before modules in the default list of parsers.

     在 3.8 版的變更: The 'parser_list' argument can be any iterable,
     not just a list.

 -- 函式: xml.sax.parse (filename_or_stream, handler,
          error_handler=handler.ErrorHandler())

     Create a SAX parser and use it to parse a document.  The document,
     passed in as 'filename_or_stream', can be a filename or a file
     object.  The 'handler' parameter needs to be a SAX *note
     ContentHandler: 367f. instance.  If 'error_handler' is given, it
     must be a SAX *note ErrorHandler: 368d. instance; if omitted, *note
     SAXParseException: 368e. will be raised on all errors.  There is no
     return value; all work must be done by the 'handler' passed in.

 -- 函式: xml.sax.parseString (string, handler,
          error_handler=handler.ErrorHandler())

     Similar to *note parse(): 190a, but parses from a buffer 'string'
     received as a parameter.  'string' must be a *note str: 3f2.
     instance or a *note bytes-like object: cd4.

     在 3.5 版的變更: 新增 *note str: 3f2. 實例的支援。

A typical SAX application uses three kinds of objects: readers, handlers
and input sources.  "Reader" in this context is another term for parser,
i.e.  some piece of code that reads the bytes or characters from the
input source, and produces a sequence of events.  The events then get
distributed to the handler objects, i.e.  the reader invokes a method on
the handler.  A SAX application must therefore obtain a reader object,
create or open the input sources, create the handlers, and connect these
objects all together.  As the final step of preparation, the reader is
called to parse the input.  During parsing, methods on the handler
objects are called based on structural and syntactic events from the
input data.

For these objects, only the interfaces are relevant; they are normally
not instantiated by the application itself.  Since Python does not have
an explicit notion of interface, they are formally introduced as
classes, but applications may use implementations which do not inherit
from the provided classes.  The *note InputSource: e3d, *note Locator:
368f, ‘Attributes’, ‘AttributesNS’, and *note XMLReader: 3682.
interfaces are defined in the module *note xml.sax.xmlreader: 113.  The
handler interfaces are defined in *note xml.sax.handler: 111.  For
convenience, *note InputSource: e3d. (which is often instantiated
directly) and the handler classes are also available from *note xml.sax:
110.  These interfaces are described below.

In addition to these classes, *note xml.sax: 110. provides the following
exception classes.

 -- 例外: xml.sax.SAXException (msg, exception=None)

     Encapsulate an XML error or warning.  This class can contain basic
     error or warning information from either the XML parser or the
     application: it can be subclassed to provide additional
     functionality or to add localization.  Note that although the
     handlers defined in the *note ErrorHandler: 368d. interface receive
     instances of this exception, it is not required to actually raise
     the exception -- it is also useful as a container for information.

     When instantiated, 'msg' should be a human-readable description of
     the error.  The optional 'exception' parameter, if given, should be
     ‘None’ or an exception that was caught by the parsing code and is
     being passed along as information.

     This is the base class for the other SAX exception classes.

 -- 例外: xml.sax.SAXParseException (msg, exception, locator)

     Subclass of *note SAXException: 3690. raised on parse errors.
     Instances of this class are passed to the methods of the SAX *note
     ErrorHandler: 368d. interface to provide information about the
     parse error.  This class supports the SAX *note Locator: 368f.
     interface as well as the *note SAXException: 3690. interface.

 -- 例外: xml.sax.SAXNotRecognizedException (msg, exception=None)

     Subclass of *note SAXException: 3690. raised when a SAX *note
     XMLReader: 3682. is confronted with an unrecognized feature or
     property.  SAX applications and extensions may use this class for
     similar purposes.

 -- 例外: xml.sax.SAXNotSupportedException (msg, exception=None)

     Subclass of *note SAXException: 3690. raised when a SAX *note
     XMLReader: 3682. is asked to enable a feature that is not
     supported, or to set a property to a value that the implementation
     does not support.  SAX applications and extensions may use this
     class for similar purposes.

也參考
......

SAX: The Simple API for XML(2)

     This site is the focal point for the definition of the SAX API. It
     provides a Java implementation and online documentation.  Links to
     implementations and historical information are also available.

*note xml.sax.handler: 111. 模組

     Definitions of the interfaces for application-provided objects.

*note xml.sax.saxutils: 112. 模組

     Convenience functions for use in SAX applications.

*note xml.sax.xmlreader: 113. 模組

     Definitions of the interfaces for parser-provided objects.

* Menu:

* SAXException 物件::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/xml/sax/__init__.py

   (2) http://www.saxproject.org/


File: python.info,  Node: SAXException 物件,  Up: xml sax --- SAX2 剖析器支援

5.20.9.1 SAXException 物件
..........................

The *note SAXException: 3690. exception class supports the following
methods:

 -- 方法: SAXException.getMessage ()

     Return a human-readable message describing the error condition.

 -- 方法: SAXException.getException ()

     Return an encapsulated exception object, or ‘None’.


File: python.info,  Node: xml sax handler --- SAX 處理函式的基本類別,  Next: xml sax saxutils --- SAX 工具程式,  Prev: xml sax --- SAX2 剖析器支援,  Up: Structured Markup Processing Tools

5.20.10 ‘xml.sax.handler’ -- SAX 處理函式的基本類別
---------------------------------------------------

'原始碼：'Lib/xml/sax/handler.py(1)

__________________________________________________________________

The SAX API defines five kinds of handlers: content handlers, DTD
handlers, error handlers, entity resolvers and lexical handlers.
Applications normally only need to implement those interfaces whose
events they are interested in; they can implement the interfaces in a
single object or in multiple objects.  Handler implementations should
inherit from the base classes provided in the module *note
xml.sax.handler: 111, so that all methods get default implementations.

 -- 類別: xml.sax.handler.ContentHandler

     This is the main callback interface in SAX, and the one most
     important to applications.  The order of events in this interface
     mirrors the order of the information in the document.

 -- 類別: xml.sax.handler.DTDHandler

     Handle DTD events.

     This interface specifies only those DTD events required for basic
     parsing (unparsed entities and attributes).

 -- 類別: xml.sax.handler.EntityResolver

     Basic interface for resolving entities.  If you create an object
     implementing this interface, then register the object with your
     Parser, the parser will call the method in your object to resolve
     all external entities.

 -- 類別: xml.sax.handler.ErrorHandler

     Interface used by the parser to present error and warning messages
     to the application.  The methods of this object control whether
     errors are immediately converted to exceptions or are handled in
     some other way.

 -- 類別: xml.sax.handler.LexicalHandler

     Interface used by the parser to represent low frequency events
     which may not be of interest to many applications.

In addition to these classes, *note xml.sax.handler: 111. provides
symbolic constants for the feature and property names.

 -- 資料: xml.sax.handler.feature_namespaces

          value: ‘"http://xml.org/sax/features/namespaces"’
          true: Perform Namespace processing.
          false: Optionally do not perform Namespace processing (implies namespace-prefixes; default).
          access: (parsing) read-only; (not parsing) read/write

 -- 資料: xml.sax.handler.feature_namespace_prefixes

          value: ‘"http://xml.org/sax/features/namespace-prefixes"’
          true: Report the original prefixed names and attributes used for Namespace declarations.
          false: Do not report attributes used for Namespace declarations, and optionally do not report original prefixed names (default).
          access: (parsing) read-only; (not parsing) read/write

 -- 資料: xml.sax.handler.feature_string_interning

          value: ‘"http://xml.org/sax/features/string-interning"’
          true: All element names, prefixes, attribute names, Namespace URIs, and local names are interned using the built-in intern function.
          false: Names are not necessarily interned, although they may be (default).
          access: (parsing) read-only; (not parsing) read/write

 -- 資料: xml.sax.handler.feature_validation

          value: ‘"http://xml.org/sax/features/validation"’
          true: Report all validation errors (implies external-general-entities and external-parameter-entities).
          false: Do not report validation errors.
          access: (parsing) read-only; (not parsing) read/write

 -- 資料: xml.sax.handler.feature_external_ges

          value: ‘"http://xml.org/sax/features/external-general-entities"’
          true: Include all external general (text) entities.
          false: Do not include external general entities.
          access: (parsing) read-only; (not parsing) read/write

 -- 資料: xml.sax.handler.feature_external_pes

          value: ‘"http://xml.org/sax/features/external-parameter-entities"’
          true: Include all external parameter entities, including the external DTD subset.
          false: Do not include any external parameter entities, even the external DTD subset.
          access: (parsing) read-only; (not parsing) read/write

 -- 資料: xml.sax.handler.all_features

     List of all features.

 -- 資料: xml.sax.handler.property_lexical_handler

          value: ‘"http://xml.org/sax/properties/lexical-handler"’
          data type: xml.sax.handler.LexicalHandler (not supported in Python 2)
          description: An optional extension handler for lexical events like comments.
          access: read/write

 -- 資料: xml.sax.handler.property_declaration_handler

          value: ‘"http://xml.org/sax/properties/declaration-handler"’
          data type: xml.sax.sax2lib.DeclHandler (not supported in Python 2)
          description: An optional extension handler for DTD-related events other than notations and unparsed entities.
          access: read/write

 -- 資料: xml.sax.handler.property_dom_node

          value: ‘"http://xml.org/sax/properties/dom-node"’
          data type: org.w3c.dom.Node (not supported in Python 2)
          description: When parsing, the current DOM node being visited if this is a DOM iterator; when not parsing, the root DOM node for iteration.
          access: (parsing) read-only; (not parsing) read/write

 -- 資料: xml.sax.handler.property_xml_string

          value: ‘"http://xml.org/sax/properties/xml-string"’
          data type: Bytes
          description: The literal string of characters that was the source for the current event.
          access: read-only

 -- 資料: xml.sax.handler.all_properties

     List of all known property names.

* Menu:

* ContentHandler 物件::
* DTDHandler 物件::
* EntityResolver 物件::
* ErrorHandler 物件::
* LexicalHandler 物件::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/xml/sax/handler.py


File: python.info,  Node: ContentHandler 物件,  Next: DTDHandler 物件,  Up: xml sax handler --- SAX 處理函式的基本類別

5.20.10.1 ContentHandler 物件
.............................

Users are expected to subclass *note ContentHandler: 367f. to support
their application.  The following methods are called by the parser on
the appropriate events in the input document:

 -- 方法: ContentHandler.setDocumentLocator (locator)

     Called by the parser to give the application a locator for locating
     the origin of document events.

     SAX parsers are strongly encouraged (though not absolutely
     required) to supply a locator: if it does so, it must supply the
     locator to the application by invoking this method before invoking
     any of the other methods in the DocumentHandler interface.

     The locator allows the application to determine the end position of
     any document-related event, even if the parser is not reporting an
     error.  Typically, the application will use this information for
     reporting its own errors (such as character content that does not
     match an application's business rules).  The information returned
     by the locator is probably not sufficient for use with a search
     engine.

     Note that the locator will return correct information only during
     the invocation of the events in this interface.  The application
     should not attempt to use it at any other time.

 -- 方法: ContentHandler.startDocument ()

     Receive notification of the beginning of a document.

     The SAX parser will invoke this method only once, before any other
     methods in this interface or in DTDHandler (except for *note
     setDocumentLocator(): 36a8.).

 -- 方法: ContentHandler.endDocument ()

     Receive notification of the end of a document.

     The SAX parser will invoke this method only once, and it will be
     the last method invoked during the parse.  The parser shall not
     invoke this method until it has either abandoned parsing (because
     of an unrecoverable error) or reached the end of input.

 -- 方法: ContentHandler.startPrefixMapping (prefix, uri)

     Begin the scope of a prefix-URI Namespace mapping.

     The information from this event is not necessary for normal
     Namespace processing: the SAX XML reader will automatically replace
     prefixes for element and attribute names when the
     ‘feature_namespaces’ feature is enabled (the default).

     There are cases, however, when applications need to use prefixes in
     character data or in attribute values, where they cannot safely be
     expanded automatically; the *note startPrefixMapping(): 36ab. and
     *note endPrefixMapping(): 36ac. events supply the information to
     the application to expand prefixes in those contexts itself, if
     necessary.

     Note that *note startPrefixMapping(): 36ab. and *note
     endPrefixMapping(): 36ac. events are not guaranteed to be properly
     nested relative to each-other: all *note startPrefixMapping():
     36ab. events will occur before the corresponding *note
     startElement(): 14b1. event, and all *note endPrefixMapping():
     36ac. events will occur after the corresponding *note endElement():
     14b2. event, but their order is not guaranteed.

 -- 方法: ContentHandler.endPrefixMapping (prefix)

     End the scope of a prefix-URI mapping.

     See *note startPrefixMapping(): 36ab. for details.  This event will
     always occur after the corresponding *note endElement(): 14b2.
     event, but the order of *note endPrefixMapping(): 36ac. events is
     not otherwise guaranteed.

 -- 方法: ContentHandler.startElement (name, attrs)

     Signals the start of an element in non-namespace mode.

     The 'name' parameter contains the raw XML 1.0 name of the element
     type as a string and the 'attrs' parameter holds an object of the
     ‘Attributes’ interface (see *note The Attributes Interface: 36ad.)
     containing the attributes of the element.  The object passed as
     'attrs' may be re-used by the parser; holding on to a reference to
     it is not a reliable way to keep a copy of the attributes.  To keep
     a copy of the attributes, use the *note copy(): 1e. method of the
     'attrs' object.

 -- 方法: ContentHandler.endElement (name)

     Signals the end of an element in non-namespace mode.

     The 'name' parameter contains the name of the element type, just as
     with the *note startElement(): 14b1. event.

 -- 方法: ContentHandler.startElementNS (name, qname, attrs)

     Signals the start of an element in namespace mode.

     The 'name' parameter contains the name of the element type as a
     ‘(uri, localname)’ tuple, the 'qname' parameter contains the raw
     XML 1.0 name used in the source document, and the 'attrs' parameter
     holds an instance of the ‘AttributesNS’ interface (see *note The
     AttributesNS Interface: 36af.) containing the attributes of the
     element.  If no namespace is associated with the element, the 'uri'
     component of 'name' will be ‘None’.  The object passed as 'attrs'
     may be re-used by the parser; holding on to a reference to it is
     not a reliable way to keep a copy of the attributes.  To keep a
     copy of the attributes, use the *note copy(): 1e. method of the
     'attrs' object.

     Parsers may set the 'qname' parameter to ‘None’, unless the
     ‘feature_namespace_prefixes’ feature is activated.

 -- 方法: ContentHandler.endElementNS (name, qname)

     Signals the end of an element in namespace mode.

     The 'name' parameter contains the name of the element type, just as
     with the *note startElementNS(): 36ae. method, likewise the 'qname'
     parameter.

 -- 方法: ContentHandler.characters (content)

     Receive notification of character data.

     The Parser will call this method to report each chunk of character
     data.  SAX parsers may return all contiguous character data in a
     single chunk, or they may split it into several chunks; however,
     all of the characters in any single event must come from the same
     external entity so that the Locator provides useful information.

     'content' may be a string or bytes instance; the ‘expat’ reader
     module always produces strings.

          備註: The earlier SAX 1 interface provided by the Python XML
          Special Interest Group used a more Java-like interface for
          this method.  Since most parsers used from Python did not take
          advantage of the older interface, the simpler signature was
          chosen to replace it.  To convert old code to the new
          interface, use 'content' instead of slicing content with the
          old 'offset' and 'length' parameters.

 -- 方法: ContentHandler.ignorableWhitespace (whitespace)

     Receive notification of ignorable whitespace in element content.

     Validating Parsers must use this method to report each chunk of
     ignorable whitespace (see the W3C XML 1.0 recommendation, section
     2.10): non-validating parsers may also use this method if they are
     capable of parsing and using content models.

     SAX parsers may return all contiguous whitespace in a single chunk,
     or they may split it into several chunks; however, all of the
     characters in any single event must come from the same external
     entity, so that the Locator provides useful information.

 -- 方法: ContentHandler.processingInstruction (target, data)

     Receive notification of a processing instruction.

     The Parser will invoke this method once for each processing
     instruction found: note that processing instructions may occur
     before or after the main document element.

     A SAX parser should never report an XML declaration (XML 1.0,
     section 2.8) or a text declaration (XML 1.0, section 4.3.1) using
     this method.

 -- 方法: ContentHandler.skippedEntity (name)

     Receive notification of a skipped entity.

     The Parser will invoke this method once for each entity skipped.
     Non-validating processors may skip entities if they have not seen
     the declarations (because, for example, the entity was declared in
     an external DTD subset).  All processors may skip external
     entities, depending on the values of the ‘feature_external_ges’ and
     the ‘feature_external_pes’ properties.


File: python.info,  Node: DTDHandler 物件,  Next: EntityResolver 物件,  Prev: ContentHandler 物件,  Up: xml sax handler --- SAX 處理函式的基本類別

5.20.10.2 DTDHandler 物件
.........................

*note DTDHandler: 3699. instances provide the following methods:

 -- 方法: DTDHandler.notationDecl (name, publicId, systemId)

     Handle a notation declaration event.

 -- 方法: DTDHandler.unparsedEntityDecl (name, publicId, systemId,
          ndata)

     Handle an unparsed entity declaration event.


File: python.info,  Node: EntityResolver 物件,  Next: ErrorHandler 物件,  Prev: DTDHandler 物件,  Up: xml sax handler --- SAX 處理函式的基本類別

5.20.10.3 EntityResolver 物件
.............................

 -- 方法: EntityResolver.resolveEntity (publicId, systemId)

     Resolve the system identifier of an entity and return either the
     system identifier to read from as a string, or an InputSource to
     read from.  The default implementation returns 'systemId'.


File: python.info,  Node: ErrorHandler 物件,  Next: LexicalHandler 物件,  Prev: EntityResolver 物件,  Up: xml sax handler --- SAX 處理函式的基本類別

5.20.10.4 ErrorHandler 物件
...........................

Objects with this interface are used to receive error and warning
information from the *note XMLReader: 3682.  If you create an object
that implements this interface, then register the object with your *note
XMLReader: 3682, the parser will call the methods in your object to
report all warnings and errors.  There are three levels of errors
available: warnings, (possibly) recoverable errors, and unrecoverable
errors.  All methods take a *note SAXParseException: 368e. as the only
parameter.  Errors and warnings may be converted to an exception by
raising the passed-in exception object.

 -- 方法: ErrorHandler.error (exception)

     Called when the parser encounters a recoverable error.  If this
     method does not raise an exception, parsing may continue, but
     further document information should not be expected by the
     application.  Allowing the parser to continue may allow additional
     errors to be discovered in the input document.

 -- 方法: ErrorHandler.fatalError (exception)

     Called when the parser encounters an error it cannot recover from;
     parsing is expected to terminate when this method returns.

 -- 方法: ErrorHandler.warning (exception)

     Called when the parser presents minor warning information to the
     application.  Parsing is expected to continue when this method
     returns, and document information will continue to be passed to the
     application.  Raising an exception in this method will cause
     parsing to end.


File: python.info,  Node: LexicalHandler 物件,  Prev: ErrorHandler 物件,  Up: xml sax handler --- SAX 處理函式的基本類別

5.20.10.5 LexicalHandler 物件
.............................

Optional SAX2 handler for lexical events.

This handler is used to obtain lexical information about an XML
document.  Lexical information includes information describing the
document encoding used and XML comments embedded in the document, as
well as section boundaries for the DTD and for any CDATA sections.  The
lexical handlers are used in the same manner as content handlers.

Set the LexicalHandler of an XMLReader by using the setProperty method
with the property identifier
‘'http://xml.org/sax/properties/lexical-handler'’.

 -- 方法: LexicalHandler.comment (content)

     Reports a comment anywhere in the document (including the DTD and
     outside the document element).

 -- 方法: LexicalHandler.startDTD (name, public_id, system_id)

     Reports the start of the DTD declarations if the document has an
     associated DTD.

 -- 方法: LexicalHandler.endDTD ()

     Reports the end of DTD declaration.

 -- 方法: LexicalHandler.startCDATA ()

     Reports the start of a CDATA marked section.

     The contents of the CDATA marked section will be reported through
     the characters handler.

 -- 方法: LexicalHandler.endCDATA ()

     Reports the end of a CDATA marked section.


File: python.info,  Node: xml sax saxutils --- SAX 工具程式,  Next: xml sax xmlreader --- XML 剖析器的介面,  Prev: xml sax handler --- SAX 處理函式的基本類別,  Up: Structured Markup Processing Tools

5.20.11 ‘xml.sax.saxutils’ -- SAX 工具程式
------------------------------------------

'原始碼：'Lib/xml/sax/saxutils.py(1)

__________________________________________________________________

The module *note xml.sax.saxutils: 112. contains a number of classes and
functions that are commonly useful when creating SAX applications,
either in direct use, or as base classes.

 -- 函式: xml.sax.saxutils.escape (data, entities={})

     Escape ‘'&'’, ‘'<'’, and ‘'>'’ in a string of data.

     You can escape other strings of data by passing a dictionary as the
     optional 'entities' parameter.  The keys and values must all be
     strings; each key will be replaced with its corresponding value.
     The characters ‘'&'’, ‘'<'’ and ‘'>'’ are always escaped, even if
     'entities' is provided.

          備註: This function should only be used to escape characters
          that can't be used directly in XML. Do not use this function
          as a general string translation function.

 -- 函式: xml.sax.saxutils.unescape (data, entities={})

     Unescape ‘'&amp;'’, ‘'&lt;'’, and ‘'&gt;'’ in a string of data.

     You can unescape other strings of data by passing a dictionary as
     the optional 'entities' parameter.  The keys and values must all be
     strings; each key will be replaced with its corresponding value.
     ‘'&amp'’, ‘'&lt;'’, and ‘'&gt;'’ are always unescaped, even if
     'entities' is provided.

 -- 函式: xml.sax.saxutils.quoteattr (data, entities={})

     Similar to *note escape(): 36c9, but also prepares 'data' to be
     used as an attribute value.  The return value is a quoted version
     of 'data' with any additional required replacements.  *note
     quoteattr(): 36cb. will select a quote character based on the
     content of 'data', attempting to avoid encoding any quote
     characters in the string.  If both single- and double-quote
     characters are already in 'data', the double-quote characters will
     be encoded and 'data' will be wrapped in double-quotes.  The
     resulting string can be used directly as an attribute value:

          >>> print("<element attr=%s>" % quoteattr("ab ' cd \" ef"))
          <element attr="ab ' cd &quot; ef">

     This function is useful when generating attribute values for HTML
     or any SGML using the reference concrete syntax.

 -- 類別: xml.sax.saxutils.XMLGenerator (out=None,
          encoding='iso-8859-1', short_empty_elements=False)

     This class implements the *note ContentHandler: 367f. interface by
     writing SAX events back into an XML document.  In other words,
     using an *note XMLGenerator: 36cc. as the content handler will
     reproduce the original document being parsed.  'out' should be a
     file-like object which will default to 'sys.stdout'.  'encoding' is
     the encoding of the output stream which defaults to ‘'iso-8859-1'’.
     'short_empty_elements' controls the formatting of elements that
     contain no content: if ‘False’ (the default) they are emitted as a
     pair of start/end tags, if set to ‘True’ they are emitted as a
     single self-closed tag.

     在 3.2 版的變更: 新增 'short_empty_elements' 參數。

 -- 類別: xml.sax.saxutils.XMLFilterBase (base)

     This class is designed to sit between an *note XMLReader: 3682. and
     the client application's event handlers.  By default, it does
     nothing but pass requests up to the reader and events on to the
     handlers unmodified, but subclasses can override specific methods
     to modify the event stream or the configuration requests as they
     pass through.

 -- 函式: xml.sax.saxutils.prepare_input_source (source, base='')

     This function takes an input source and an optional base URL and
     returns a fully resolved *note InputSource: e3d. object ready for
     reading.  The input source can be given as a string, a file-like
     object, or an *note InputSource: e3d. object; parsers will use this
     function to implement the polymorphic 'source' argument to their
     *note parse(): 36cf. method.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/xml/sax/saxutils.py


File: python.info,  Node: xml sax xmlreader --- XML 剖析器的介面,  Next: xml parsers expat --- 使用 Expat 進行快速 XML 剖析,  Prev: xml sax saxutils --- SAX 工具程式,  Up: Structured Markup Processing Tools

5.20.12 ‘xml.sax.xmlreader’ -- XML 剖析器的介面
-----------------------------------------------

'原始碼：'Lib/xml/sax/xmlreader.py(1)

__________________________________________________________________

SAX parsers implement the *note XMLReader: 3682. interface.  They are
implemented in a Python module, which must provide a function
‘create_parser()’.  This function is invoked by *note
xml.sax.make_parser(): 1941. with no arguments to create a new parser
object.

 -- 類別: xml.sax.xmlreader.XMLReader

     Base class which can be inherited by SAX parsers.

 -- 類別: xml.sax.xmlreader.IncrementalParser

     In some cases, it is desirable not to parse an input source at
     once, but to feed chunks of the document as they get available.
     Note that the reader will normally not read the entire file, but
     read it in chunks as well; still ‘parse()’ won't return until the
     entire document is processed.  So these interfaces should be used
     if the blocking behaviour of ‘parse()’ is not desirable.

     When the parser is instantiated it is ready to begin accepting data
     from the feed method immediately.  After parsing has been finished
     with a call to close the reset method must be called to make the
     parser ready to accept new data, either from feed or using the
     parse method.

     Note that these methods must 'not' be called during parsing, that
     is, after parse has been called and before it returns.

     By default, the class also implements the parse method of the
     XMLReader interface using the feed, close and reset methods of the
     IncrementalParser interface as a convenience to SAX 2.0 driver
     writers.

 -- 類別: xml.sax.xmlreader.Locator

     Interface for associating a SAX event with a document location.  A
     locator object will return valid results only during calls to
     DocumentHandler methods; at any other time, the results are
     unpredictable.  If information is not available, methods may return
     ‘None’.

 -- 類別: xml.sax.xmlreader.InputSource (system_id=None)

     Encapsulation of the information needed by the *note XMLReader:
     3682. to read entities.

     This class may include information about the public identifier,
     system identifier, byte stream (possibly with character encoding
     information) and/or the character stream of an entity.

     Applications will create objects of this class for use in the *note
     XMLReader.parse(): 36cf. method and for returning from
     EntityResolver.resolveEntity.

     An *note InputSource: e3d. belongs to the application, the *note
     XMLReader: 3682. is not allowed to modify *note InputSource: e3d.
     objects passed to it from the application, although it may make
     copies and modify those.

 -- 類別: xml.sax.xmlreader.AttributesImpl (attrs)

     This is an implementation of the ‘Attributes’ interface (see
     section *note The Attributes Interface: 36ad.).  This is a
     dictionary-like object which represents the element attributes in a
     ‘startElement()’ call.  In addition to the most useful dictionary
     operations, it supports a number of other methods as described by
     the interface.  Objects of this class should be instantiated by
     readers; 'attrs' must be a dictionary-like object containing a
     mapping from attribute names to attribute values.

 -- 類別: xml.sax.xmlreader.AttributesNSImpl (attrs, qnames)

     Namespace-aware variant of *note AttributesImpl: 36d3, which will
     be passed to ‘startElementNS()’.  It is derived from *note
     AttributesImpl: 36d3, but understands attribute names as two-tuples
     of 'namespaceURI' and 'localname'.  In addition, it provides a
     number of methods expecting qualified names as they appear in the
     original document.  This class implements the ‘AttributesNS’
     interface (see section *note The AttributesNS Interface: 36af.).

* Menu:

* XMLReader 物件::
* IncrementalParser 物件::
* Locator Objects::
* InputSource 物件::
* The Attributes Interface::
* The AttributesNS Interface::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/xml/sax/xmlreader.py


File: python.info,  Node: XMLReader 物件,  Next: IncrementalParser 物件,  Up: xml sax xmlreader --- XML 剖析器的介面

5.20.12.1 XMLReader 物件
........................

The *note XMLReader: 3682. interface supports the following methods:

 -- 方法: XMLReader.parse (source)

     Process an input source, producing SAX events.  The 'source' object
     can be a system identifier (a string identifying the input source -
     typically a file name or a URL), a *note pathlib.Path: 20e. or
     *note path-like: ac2. object, or an *note InputSource: e3d. object.
     When *note parse(): 36cf. returns, the input is completely
     processed, and the parser object can be discarded or reset.

     在 3.5 版的變更: 新增對字元串流的支援。

     在 3.8 版的變更: 新增對類路徑物件的支援。

 -- 方法: XMLReader.getContentHandler ()

     Return the current *note ContentHandler: 367f.

 -- 方法: XMLReader.setContentHandler (handler)

     Set the current *note ContentHandler: 367f.  If no *note
     ContentHandler: 367f. is set, content events will be discarded.

 -- 方法: XMLReader.getDTDHandler ()

     Return the current *note DTDHandler: 3699.

 -- 方法: XMLReader.setDTDHandler (handler)

     Set the current *note DTDHandler: 3699.  If no *note DTDHandler:
     3699. is set, DTD events will be discarded.

 -- 方法: XMLReader.getEntityResolver ()

     Return the current *note EntityResolver: 369a.

 -- 方法: XMLReader.setEntityResolver (handler)

     Set the current *note EntityResolver: 369a.  If no *note
     EntityResolver: 369a. is set, attempts to resolve an external
     entity will result in opening the system identifier for the entity,
     and fail if it is not available.

 -- 方法: XMLReader.getErrorHandler ()

     Return the current *note ErrorHandler: 368d.

 -- 方法: XMLReader.setErrorHandler (handler)

     Set the current error handler.  If no *note ErrorHandler: 368d. is
     set, errors will be raised as exceptions, and warnings will be
     printed.

 -- 方法: XMLReader.setLocale (locale)

     Allow an application to set the locale for errors and warnings.

     SAX parsers are not required to provide localization for errors and
     warnings; if they cannot support the requested locale, however,
     they must raise a SAX exception.  Applications may request a locale
     change in the middle of a parse.

 -- 方法: XMLReader.getFeature (featurename)

     Return the current setting for feature 'featurename'.  If the
     feature is not recognized, ‘SAXNotRecognizedException’ is raised.
     The well-known featurenames are listed in the module *note
     xml.sax.handler: 111.

 -- 方法: XMLReader.setFeature (featurename, value)

     Set the 'featurename' to 'value'.  If the feature is not
     recognized, ‘SAXNotRecognizedException’ is raised.  If the feature
     or its setting is not supported by the parser,
     'SAXNotSupportedException' is raised.

 -- 方法: XMLReader.getProperty (propertyname)

     Return the current setting for property 'propertyname'.  If the
     property is not recognized, a ‘SAXNotRecognizedException’ is
     raised.  The well-known propertynames are listed in the module
     *note xml.sax.handler: 111.

 -- 方法: XMLReader.setProperty (propertyname, value)

     Set the 'propertyname' to 'value'.  If the property is not
     recognized, ‘SAXNotRecognizedException’ is raised.  If the property
     or its setting is not supported by the parser,
     'SAXNotSupportedException' is raised.


File: python.info,  Node: IncrementalParser 物件,  Next: Locator Objects,  Prev: XMLReader 物件,  Up: xml sax xmlreader --- XML 剖析器的介面

5.20.12.2 IncrementalParser 物件
................................

Instances of *note IncrementalParser: 36d2. offer the following
additional methods:

 -- 方法: IncrementalParser.feed (data)

     Process a chunk of 'data'.

 -- 方法: IncrementalParser.close ()

     Assume the end of the document.  That will check well-formedness
     conditions that can be checked only at the end, invoke handlers,
     and may clean up resources allocated during parsing.

 -- 方法: IncrementalParser.reset ()

     This method is called after close has been called to reset the
     parser so that it is ready to parse new documents.  The results of
     calling parse or feed after close without calling reset are
     undefined.


File: python.info,  Node: Locator Objects,  Next: InputSource 物件,  Prev: IncrementalParser 物件,  Up: xml sax xmlreader --- XML 剖析器的介面

5.20.12.3 Locator Objects
.........................

Instances of *note Locator: 368f. provide these methods:

 -- 方法: Locator.getColumnNumber ()

     Return the column number where the current event begins.

 -- 方法: Locator.getLineNumber ()

     Return the line number where the current event begins.

 -- 方法: Locator.getPublicId ()

     Return the public identifier for the current event.

 -- 方法: Locator.getSystemId ()

     Return the system identifier for the current event.


File: python.info,  Node: InputSource 物件,  Next: The Attributes Interface,  Prev: Locator Objects,  Up: xml sax xmlreader --- XML 剖析器的介面

5.20.12.4 InputSource 物件
..........................

 -- 方法: InputSource.setPublicId (id)

     Sets the public identifier of this *note InputSource: e3d.

 -- 方法: InputSource.getPublicId ()

     Returns the public identifier of this *note InputSource: e3d.

 -- 方法: InputSource.setSystemId (id)

     Sets the system identifier of this *note InputSource: e3d.

 -- 方法: InputSource.getSystemId ()

     Returns the system identifier of this *note InputSource: e3d.

 -- 方法: InputSource.setEncoding (encoding)

     Sets the character encoding of this *note InputSource: e3d.

     The encoding must be a string acceptable for an XML encoding
     declaration (see section 4.3.3 of the XML recommendation).

     The encoding attribute of the *note InputSource: e3d. is ignored if
     the *note InputSource: e3d. also contains a character stream.

 -- 方法: InputSource.getEncoding ()

     Get the character encoding of this InputSource.

 -- 方法: InputSource.setByteStream (bytefile)

     Set the byte stream (a *note binary file: 1b8b.) for this input
     source.

     The SAX parser will ignore this if there is also a character stream
     specified, but it will use a byte stream in preference to opening a
     URI connection itself.

     If the application knows the character encoding of the byte stream,
     it should set it with the setEncoding method.

 -- 方法: InputSource.getByteStream ()

     Get the byte stream for this input source.

     The getEncoding method will return the character encoding for this
     byte stream, or ‘None’ if unknown.

 -- 方法: InputSource.setCharacterStream (charfile)

     Set the character stream (a *note text file: 1b8a.) for this input
     source.

     If there is a character stream specified, the SAX parser will
     ignore any byte stream and will not attempt to open a URI
     connection to the system identifier.

 -- 方法: InputSource.getCharacterStream ()

     Get the character stream for this input source.


File: python.info,  Node: The Attributes Interface,  Next: The AttributesNS Interface,  Prev: InputSource 物件,  Up: xml sax xmlreader --- XML 剖析器的介面

5.20.12.5 The ‘Attributes’ Interface
....................................

‘Attributes’ objects implement a portion of the *note mapping protocol:
1154, including the methods ‘copy()’, ‘get()’, *note __contains__():
1e33, ‘items()’, ‘keys()’, and ‘values()’.  The following methods are
also provided:

 -- 方法: Attributes.getLength ()

     Return the number of attributes.

 -- 方法: Attributes.getNames ()

     Return the names of the attributes.

 -- 方法: Attributes.getType (name)

     Returns the type of the attribute 'name', which is normally
     ‘'CDATA'’.

 -- 方法: Attributes.getValue (name)

     Return the value of attribute 'name'.


File: python.info,  Node: The AttributesNS Interface,  Prev: The Attributes Interface,  Up: xml sax xmlreader --- XML 剖析器的介面

5.20.12.6 The ‘AttributesNS’ Interface
......................................

This interface is a subtype of the ‘Attributes’ interface (see section
*note The Attributes Interface: 36ad.).  All methods supported by that
interface are also available on ‘AttributesNS’ objects.

The following methods are also available:

 -- 方法: AttributesNS.getValueByQName (name)

     Return the value for a qualified name.

 -- 方法: AttributesNS.getNameByQName (name)

     Return the ‘(namespace, localname)’ pair for a qualified 'name'.

 -- 方法: AttributesNS.getQNameByName (name)

     Return the qualified name for a ‘(namespace, localname)’ pair.

 -- 方法: AttributesNS.getQNames ()

     Return the qualified names of all attributes.


File: python.info,  Node: xml parsers expat --- 使用 Expat 進行快速 XML 剖析,  Prev: xml sax xmlreader --- XML 剖析器的介面,  Up: Structured Markup Processing Tools

5.20.13 ‘xml.parsers.expat’ -- 使用 Expat 進行快速 XML 剖析
-----------------------------------------------------------

__________________________________________________________________

     警告: The ‘pyexpat’ module is not secure against maliciously
     constructed data.  If you need to parse untrusted or
     unauthenticated data see *note XML 漏洞: 3596.

The *note xml.parsers.expat: 10d. module is a Python interface to the
Expat non-validating XML parser.  The module provides a single extension
type, ‘xmlparser’, that represents the current state of an XML parser.
After an ‘xmlparser’ object has been created, various attributes of the
object can be set to handler functions.  When an XML document is then
fed to the parser, the handler functions are called for the character
data and markup in the XML document.

This module uses the ‘pyexpat’ module to provide access to the Expat
parser.  Direct use of the ‘pyexpat’ module is deprecated.

This module provides one exception and one type object:

 -- 例外: xml.parsers.expat.ExpatError

     The exception raised when Expat reports an error.  See section
     *note ExpatError 例外: 3706. for more information on interpreting
     Expat errors.

 -- 例外: xml.parsers.expat.error

     *note ExpatError: 1211. 的別名。

 -- 資料: xml.parsers.expat.XMLParserType

     The type of the return values from the *note ParserCreate(): 3709.
     function.

The *note xml.parsers.expat: 10d. module contains two functions:

 -- 函式: xml.parsers.expat.ErrorString (errno)

     Returns an explanatory string for a given error number 'errno'.

 -- 函式: xml.parsers.expat.ParserCreate (encoding=None,
          namespace_separator=None)

     Creates and returns a new ‘xmlparser’ object.  'encoding', if
     specified, must be a string naming the encoding used by the XML
     data.  Expat doesn't support as many encodings as Python does, and
     its repertoire of encodings can't be extended; it supports UTF-8,
     UTF-16, ISO-8859-1 (Latin1), and ASCII. If 'encoding' (1) is given
     it will override the implicit or explicit encoding of the document.

     Expat can optionally do XML namespace processing for you, enabled
     by providing a value for 'namespace_separator'.  The value must be
     a one-character string; a *note ValueError: 1e7. will be raised if
     the string has an illegal length (‘None’ is considered the same as
     omission).  When namespace processing is enabled, element type
     names and attribute names that belong to a namespace will be
     expanded.  The element name passed to the element handlers
     ‘StartElementHandler’ and ‘EndElementHandler’ will be the
     concatenation of the namespace URI, the namespace separator
     character, and the local part of the name.  If the namespace
     separator is a zero byte (‘chr(0)’) then the namespace URI and the
     local part will be concatenated without any separator.

     For example, if 'namespace_separator' is set to a space character
     (‘' '’) and the following document is parsed:

          <?xml version="1.0"?>
          <root xmlns    = "http://default-namespace.org/"
                xmlns:py = "http://www.python.org/ns/">
            <py:elem1 />
            <elem2 xmlns="" />
          </root>

     ‘StartElementHandler’ will receive the following strings for each
     element:

          http://default-namespace.org/ root
          http://www.python.org/ns/ elem1
          elem2

     Due to limitations in the ‘Expat’ library used by ‘pyexpat’, the
     ‘xmlparser’ instance returned can only be used to parse a single
     XML document.  Call ‘ParserCreate’ for each document to provide
     unique parser instances.

也參考
......

The Expat XML Parser(2)

     Home page of the Expat project.

* Menu:

* XMLParser 物件: XMLParser 物件<2>.
* ExpatError 例外::
* 範例: 範例<33>.
* Content Model Descriptions::
* Expat error constants::

   ---------- Footnotes ----------

   (1) The encoding string included in XML output should conform to the
appropriate standards.  For example, "UTF-8" is valid, but "UTF8" is
not.  See
‘https://www.w3.org/TR/2006/REC-xml11-20060816/#NT-EncodingDecl’ and
‘https://www.iana.org/assignments/character-sets/character-sets.xhtml’.

   (2) http://www.libexpat.org/


File: python.info,  Node: XMLParser 物件<2>,  Next: ExpatError 例外,  Up: xml parsers expat --- 使用 Expat 進行快速 XML 剖析

5.20.13.1 XMLParser 物件
........................

‘xmlparser’ objects have the following methods:

 -- 方法: xmlparser.Parse (data[, isfinal])

     Parses the contents of the string 'data', calling the appropriate
     handler functions to process the parsed data.  'isfinal' must be
     true on the final call to this method; it allows the parsing of a
     single file in fragments, not the submission of multiple files.
     'data' can be the empty string at any time.

 -- 方法: xmlparser.ParseFile (file)

     Parse XML data reading from the object 'file'.  'file' only needs
     to provide the ‘read(nbytes)’ method, returning the empty string
     when there's no more data.

 -- 方法: xmlparser.SetBase (base)

     Sets the base to be used for resolving relative URIs in system
     identifiers in declarations.  Resolving relative identifiers is
     left to the application: this value will be passed through as the
     'base' argument to the *note ExternalEntityRefHandler(): 3710,
     *note NotationDeclHandler(): 3711, and *note
     UnparsedEntityDeclHandler(): 3712. functions.

 -- 方法: xmlparser.GetBase ()

     Returns a string containing the base set by a previous call to
     *note SetBase(): 370f, or ‘None’ if *note SetBase(): 370f. hasn't
     been called.

 -- 方法: xmlparser.GetInputContext ()

     Returns the input data that generated the current event as a
     string.  The data is in the encoding of the entity which contains
     the text.  When called while an event handler is not active, the
     return value is ‘None’.

 -- 方法: xmlparser.ExternalEntityParserCreate (context[, encoding])

     Create a "child" parser which can be used to parse an external
     parsed entity referred to by content parsed by the parent parser.
     The 'context' parameter should be the string passed to the *note
     ExternalEntityRefHandler(): 3710. handler function, described
     below.  The child parser is created with the *note
     ordered_attributes: 3716. and *note specified_attributes: 3717. set
     to the values of this parser.

 -- 方法: xmlparser.SetParamEntityParsing (flag)

     Control parsing of parameter entities (including the external DTD
     subset).  Possible 'flag' values are
     ‘XML_PARAM_ENTITY_PARSING_NEVER’,
     ‘XML_PARAM_ENTITY_PARSING_UNLESS_STANDALONE’ and
     ‘XML_PARAM_ENTITY_PARSING_ALWAYS’.  Return true if setting the flag
     was successful.

 -- 方法: xmlparser.UseForeignDTD ([flag])

     Calling this with a true value for 'flag' (the default) will cause
     Expat to call the *note ExternalEntityRefHandler: 3710. with *note
     None: 61b. for all arguments to allow an alternate DTD to be
     loaded.  If the document does not contain a document type
     declaration, the *note ExternalEntityRefHandler: 3710. will still
     be called, but the *note StartDoctypeDeclHandler: 371a. and *note
     EndDoctypeDeclHandler: 371b. will not be called.

     Passing a false value for 'flag' will cancel a previous call that
     passed a true value, but otherwise has no effect.

     This method can only be called before the *note Parse(): 370d. or
     *note ParseFile(): 370e. methods are called; calling it after
     either of those have been called causes *note ExpatError: 1211. to
     be raised with the *note code: 13. attribute set to
     ‘errors.codes[errors.XML_ERROR_CANT_CHANGE_FEATURE_ONCE_PARSING]’.

 -- 方法: xmlparser.SetReparseDeferralEnabled (enabled)

          警告: Calling ‘SetReparseDeferralEnabled(False)’ has security
          implications, as detailed below; please make sure to
          understand these consequences prior to using the
          ‘SetReparseDeferralEnabled’ method.

     Expat 2.6.0 introduced a security mechanism called "reparse
     deferral" where instead of causing denial of service through
     quadratic runtime from reparsing large tokens, reparsing of
     unfinished tokens is now delayed by default until a sufficient
     amount of input is reached.  Due to this delay, registered handlers
     may — depending of the sizing of input chunks pushed to Expat — no
     longer be called right after pushing new input to the parser.
     Where immediate feedback and taking over responsibility of
     protecting against denial of service from large tokens are both
     wanted, calling ‘SetReparseDeferralEnabled(False)’ disables reparse
     deferral for the current Expat parser instance, temporarily or
     altogether.  Calling ‘SetReparseDeferralEnabled(True)’ allows
     re-enabling reparse deferral.

     Note that *note SetReparseDeferralEnabled(): 257. has been
     backported to some prior releases of CPython as a security fix.
     Check for availability of *note SetReparseDeferralEnabled(): 257.
     using *note hasattr(): 479. if used in code running across a
     variety of Python versions.

     在 3.13 版被加入.

 -- 方法: xmlparser.GetReparseDeferralEnabled ()

     Returns whether reparse deferral is currently enabled for the given
     Expat parser instance.

     在 3.13 版被加入.

‘xmlparser’ 物件擁有以下屬性：

 -- 屬性: xmlparser.buffer_size

     The size of the buffer used when *note buffer_text: 142d. is true.
     A new buffer size can be set by assigning a new integer value to
     this attribute.  When the size is changed, the buffer will be
     flushed.

 -- 屬性: xmlparser.buffer_text

     Setting this to true causes the ‘xmlparser’ object to buffer
     textual content returned by Expat to avoid multiple calls to the
     *note CharacterDataHandler(): 371d. callback whenever possible.
     This can improve performance substantially since Expat normally
     breaks character data into chunks at every line ending.  This
     attribute is false by default, and may be changed at any time.
     Note that when it is false, data that does not contain newlines may
     be chunked too.

 -- 屬性: xmlparser.buffer_used

     If *note buffer_text: 142d. is enabled, the number of bytes stored
     in the buffer.  These bytes represent UTF-8 encoded text.  This
     attribute has no meaningful interpretation when *note buffer_text:
     142d. is false.

 -- 屬性: xmlparser.ordered_attributes

     Setting this attribute to a non-zero integer causes the attributes
     to be reported as a list rather than a dictionary.  The attributes
     are presented in the order found in the document text.  For each
     attribute, two list entries are presented: the attribute name and
     the attribute value.  (Older versions of this module also used this
     format.)  By default, this attribute is false; it may be changed at
     any time.

 -- 屬性: xmlparser.specified_attributes

     If set to a non-zero integer, the parser will report only those
     attributes which were specified in the document instance and not
     those which were derived from attribute declarations.  Applications
     which set this need to be especially careful to use what additional
     information is available from the declarations as needed to comply
     with the standards for the behavior of XML processors.  By default,
     this attribute is false; it may be changed at any time.

The following attributes contain values relating to the most recent
error encountered by an ‘xmlparser’ object, and will only have correct
values once a call to ‘Parse()’ or ‘ParseFile()’ has raised an *note
xml.parsers.expat.ExpatError: 1211. exception.

 -- 屬性: xmlparser.ErrorByteIndex

     Byte index at which an error occurred.

 -- 屬性: xmlparser.ErrorCode

     Numeric code specifying the problem.  This value can be passed to
     the *note ErrorString(): 370a. function, or compared to one of the
     constants defined in the ‘errors’ object.

 -- 屬性: xmlparser.ErrorColumnNumber

     Column number at which an error occurred.

 -- 屬性: xmlparser.ErrorLineNumber

     Line number at which an error occurred.

The following attributes contain values relating to the current parse
location in an ‘xmlparser’ object.  During a callback reporting a parse
event they indicate the location of the first of the sequence of
characters that generated the event.  When called outside of a callback,
the position indicated will be just past the last parse event
(regardless of whether there was an associated callback).

 -- 屬性: xmlparser.CurrentByteIndex

     Current byte index in the parser input.

 -- 屬性: xmlparser.CurrentColumnNumber

     Current column number in the parser input.

 -- 屬性: xmlparser.CurrentLineNumber

     Current line number in the parser input.

Here is the list of handlers that can be set.  To set a handler on an
‘xmlparser’ object 'o', use ‘o.handlername = func’.  'handlername' must
be taken from the following list, and 'func' must be a callable object
accepting the correct number of arguments.  The arguments are all
strings, unless otherwise stated.

 -- 方法: xmlparser.XmlDeclHandler (version, encoding, standalone)

     Called when the XML declaration is parsed.  The XML declaration is
     the (optional) declaration of the applicable version of the XML
     recommendation, the encoding of the document text, and an optional
     "standalone" declaration.  'version' and 'encoding' will be
     strings, and 'standalone' will be ‘1’ if the document is declared
     standalone, ‘0’ if it is declared not to be standalone, or ‘-1’ if
     the standalone clause was omitted.  This is only available with
     Expat version 1.95.0 or newer.

 -- 方法: xmlparser.StartDoctypeDeclHandler (doctypeName, systemId,
          publicId, has_internal_subset)

     Called when Expat begins parsing the document type declaration
     (‘<!DOCTYPE ...’).  The 'doctypeName' is provided exactly as
     presented.  The 'systemId' and 'publicId' parameters give the
     system and public identifiers if specified, or ‘None’ if omitted.
     'has_internal_subset' will be true if the document contains and
     internal document declaration subset.  This requires Expat version
     1.2 or newer.

 -- 方法: xmlparser.EndDoctypeDeclHandler ()

     Called when Expat is done parsing the document type declaration.
     This requires Expat version 1.2 or newer.

 -- 方法: xmlparser.ElementDeclHandler (name, model)

     Called once for each element type declaration.  'name' is the name
     of the element type, and 'model' is a representation of the content
     model.

 -- 方法: xmlparser.AttlistDeclHandler (elname, attname, type, default,
          required)

     Called for each declared attribute for an element type.  If an
     attribute list declaration declares three attributes, this handler
     is called three times, once for each attribute.  'elname' is the
     name of the element to which the declaration applies and 'attname'
     is the name of the attribute declared.  The attribute type is a
     string passed as 'type'; the possible values are ‘'CDATA'’, ‘'ID'’,
     ‘'IDREF'’, ...  'default' gives the default value for the attribute
     used when the attribute is not specified by the document instance,
     or ‘None’ if there is no default value (‘#IMPLIED’ values).  If the
     attribute is required to be given in the document instance,
     'required' will be true.  This requires Expat version 1.95.0 or
     newer.

 -- 方法: xmlparser.StartElementHandler (name, attributes)

     Called for the start of every element.  'name' is a string
     containing the element name, and 'attributes' is the element
     attributes.  If *note ordered_attributes: 3716. is true, this is a
     list (see *note ordered_attributes: 3716. for a full description).
     Otherwise it's a dictionary mapping names to values.

 -- 方法: xmlparser.EndElementHandler (name)

     Called for the end of every element.

 -- 方法: xmlparser.ProcessingInstructionHandler (target, data)

     Called for every processing instruction.

 -- 方法: xmlparser.CharacterDataHandler (data)

     Called for character data.  This will be called for normal
     character data, CDATA marked content, and ignorable whitespace.
     Applications which must distinguish these cases can use the *note
     StartCdataSectionHandler: 372c, *note EndCdataSectionHandler: 372d,
     and *note ElementDeclHandler: 3727. callbacks to collect the
     required information.  Note that the character data may be chunked
     even if it is short and so you may receive more than one call to
     *note CharacterDataHandler(): 371d.  Set the *note buffer_text:
     142d. instance attribute to ‘True’ to avoid that.

 -- 方法: xmlparser.UnparsedEntityDeclHandler (entityName, base,
          systemId, publicId, notationName)

     Called for unparsed (NDATA) entity declarations.  This is only
     present for version 1.2 of the Expat library; for more recent
     versions, use *note EntityDeclHandler: 372e. instead.  (The
     underlying function in the Expat library has been declared
     obsolete.)

 -- 方法: xmlparser.EntityDeclHandler (entityName, is_parameter_entity,
          value, base, systemId, publicId, notationName)

     Called for all entity declarations.  For parameter and internal
     entities, 'value' will be a string giving the declared contents of
     the entity; this will be ‘None’ for external entities.  The
     'notationName' parameter will be ‘None’ for parsed entities, and
     the name of the notation for unparsed entities.
     'is_parameter_entity' will be true if the entity is a parameter
     entity or false for general entities (most applications only need
     to be concerned with general entities).  This is only available
     starting with version 1.95.0 of the Expat library.

 -- 方法: xmlparser.NotationDeclHandler (notationName, base, systemId,
          publicId)

     Called for notation declarations.  'notationName', 'base', and
     'systemId', and 'publicId' are strings if given.  If the public
     identifier is omitted, 'publicId' will be ‘None’.

 -- 方法: xmlparser.StartNamespaceDeclHandler (prefix, uri)

     Called when an element contains a namespace declaration.  Namespace
     declarations are processed before the *note StartElementHandler:
     3729. is called for the element on which declarations are placed.

 -- 方法: xmlparser.EndNamespaceDeclHandler (prefix)

     Called when the closing tag is reached for an element that
     contained a namespace declaration.  This is called once for each
     namespace declaration on the element in the reverse of the order
     for which the *note StartNamespaceDeclHandler: 372f. was called to
     indicate the start of each namespace declaration's scope.  Calls to
     this handler are made after the corresponding *note
     EndElementHandler: 372a. for the end of the element.

 -- 方法: xmlparser.CommentHandler (data)

     Called for comments.  'data' is the text of the comment, excluding
     the leading ‘'<!-’‘-'’ and trailing ‘'-’‘->'’.

 -- 方法: xmlparser.StartCdataSectionHandler ()

     Called at the start of a CDATA section.  This and *note
     EndCdataSectionHandler: 372d. are needed to be able to identify the
     syntactical start and end for CDATA sections.

 -- 方法: xmlparser.EndCdataSectionHandler ()

     Called at the end of a CDATA section.

 -- 方法: xmlparser.DefaultHandler (data)

     Called for any characters in the XML document for which no
     applicable handler has been specified.  This means characters that
     are part of a construct which could be reported, but for which no
     handler has been supplied.

 -- 方法: xmlparser.DefaultHandlerExpand (data)

     This is the same as the *note DefaultHandler(): 3732, but doesn't
     inhibit expansion of internal entities.  The entity reference will
     not be passed to the default handler.

 -- 方法: xmlparser.NotStandaloneHandler ()

     Called if the XML document hasn't been declared as being a
     standalone document.  This happens when there is an external subset
     or a reference to a parameter entity, but the XML declaration does
     not set standalone to ‘yes’ in an XML declaration.  If this handler
     returns ‘0’, then the parser will raise an
     ‘XML_ERROR_NOT_STANDALONE’ error.  If this handler is not set, no
     exception is raised by the parser for this condition.

 -- 方法: xmlparser.ExternalEntityRefHandler (context, base, systemId,
          publicId)

     Called for references to external entities.  'base' is the current
     base, as set by a previous call to *note SetBase(): 370f.  The
     public and system identifiers, 'systemId' and 'publicId', are
     strings if given; if the public identifier is not given, 'publicId'
     will be ‘None’.  The 'context' value is opaque and should only be
     used as described below.

     For external entities to be parsed, this handler must be
     implemented.  It is responsible for creating the sub-parser using
     ‘ExternalEntityParserCreate(context)’, initializing it with the
     appropriate callbacks, and parsing the entity.  This handler should
     return an integer; if it returns ‘0’, the parser will raise an
     ‘XML_ERROR_EXTERNAL_ENTITY_HANDLING’ error, otherwise parsing will
     continue.

     If this handler is not provided, external entities are reported by
     the *note DefaultHandler: 3732. callback, if provided.


File: python.info,  Node: ExpatError 例外,  Next: 範例<33>,  Prev: XMLParser 物件<2>,  Up: xml parsers expat --- 使用 Expat 進行快速 XML 剖析

5.20.13.2 ExpatError 例外
.........................

*note ExpatError: 1211. exceptions have a number of interesting
attributes:

 -- 屬性: ExpatError.code

     Expat's internal error number for the specific error.  The *note
     errors.messages: 3737. dictionary maps these error numbers to
     Expat's error messages.  For example:

          from xml.parsers.expat import ParserCreate, ExpatError, errors

          p = ParserCreate()
          try:
              p.Parse(some_xml_document)
          except ExpatError as err:
              print("Error:", errors.messages[err.code])

     The *note errors: 10e. module also provides error message constants
     and a dictionary *note codes: 3738. mapping these messages back to
     the error codes, see below.

 -- 屬性: ExpatError.lineno

     Line number on which the error was detected.  The first line is
     numbered ‘1’.

 -- 屬性: ExpatError.offset

     Character offset into the line where the error occurred.  The first
     column is numbered ‘0’.


File: python.info,  Node: 範例<33>,  Next: Content Model Descriptions,  Prev: ExpatError 例外,  Up: xml parsers expat --- 使用 Expat 進行快速 XML 剖析

5.20.13.3 範例
..............

The following program defines three handlers that just print out their
arguments.

     import xml.parsers.expat

     # 3 handler functions
     def start_element(name, attrs):
         print('Start element:', name, attrs)
     def end_element(name):
         print('End element:', name)
     def char_data(data):
         print('Character data:', repr(data))

     p = xml.parsers.expat.ParserCreate()

     p.StartElementHandler = start_element
     p.EndElementHandler = end_element
     p.CharacterDataHandler = char_data

     p.Parse("""<?xml version="1.0"?>
     <parent id="top"><child1 name="paul">Text goes here</child1>
     <child2 name="fred">More text</child2>
     </parent>""", 1)

The output from this program is:

     Start element: parent {'id': 'top'}
     Start element: child1 {'name': 'paul'}
     Character data: 'Text goes here'
     End element: child1
     Character data: '\n'
     Start element: child2 {'name': 'fred'}
     Character data: 'More text'
     End element: child2
     Character data: '\n'
     End element: parent


File: python.info,  Node: Content Model Descriptions,  Next: Expat error constants,  Prev: 範例<33>,  Up: xml parsers expat --- 使用 Expat 進行快速 XML 剖析

5.20.13.4 Content Model Descriptions
....................................

Content models are described using nested tuples.  Each tuple contains
four values: the type, the quantifier, the name, and a tuple of
children.  Children are simply additional content model descriptions.

The values of the first two fields are constants defined in the *note
xml.parsers.expat.model: 10f. module.  These constants can be collected
in two groups: the model type group and the quantifier group.

The constants in the model type group are:

 -- 資料: xml.parsers.expat.model.XML_CTYPE_ANY

     The element named by the model name was declared to have a content
     model of ‘ANY’.

 -- 資料: xml.parsers.expat.model.XML_CTYPE_CHOICE

     The named element allows a choice from a number of options; this is
     used for content models such as ‘(A | B | C)’.

 -- 資料: xml.parsers.expat.model.XML_CTYPE_EMPTY

     Elements which are declared to be ‘EMPTY’ have this model type.

 -- 資料: xml.parsers.expat.model.XML_CTYPE_MIXED

 -- 資料: xml.parsers.expat.model.XML_CTYPE_NAME

 -- 資料: xml.parsers.expat.model.XML_CTYPE_SEQ

     Models which represent a series of models which follow one after
     the other are indicated with this model type.  This is used for
     models such as ‘(A, B, C)’.

The constants in the quantifier group are:

 -- 資料: xml.parsers.expat.model.XML_CQUANT_NONE

     No modifier is given, so it can appear exactly once, as for ‘A’.

 -- 資料: xml.parsers.expat.model.XML_CQUANT_OPT

     The model is optional: it can appear once or not at all, as for
     ‘A?’.

 -- 資料: xml.parsers.expat.model.XML_CQUANT_PLUS

     The model must occur one or more times (like ‘A+’).

 -- 資料: xml.parsers.expat.model.XML_CQUANT_REP

     The model must occur zero or more times, as for ‘A*’.


File: python.info,  Node: Expat error constants,  Prev: Content Model Descriptions,  Up: xml parsers expat --- 使用 Expat 進行快速 XML 剖析

5.20.13.5 Expat error constants
...............................

The following constants are provided in the *note
xml.parsers.expat.errors: 10e. module.  These constants are useful in
interpreting some of the attributes of the ‘ExpatError’ exception
objects raised when an error has occurred.  Since for backwards
compatibility reasons, the constants' value is the error 'message' and
not the numeric error 'code', you do this by comparing its *note code:
13. attribute with ‘errors.codes[errors.XML_ERROR_CONSTANT_NAME]’.

The ‘errors’ module has the following attributes:

 -- 資料: xml.parsers.expat.errors.codes

     A dictionary mapping string descriptions to their error codes.

     在 3.2 版被加入.

 -- 資料: xml.parsers.expat.errors.messages

     A dictionary mapping numeric error codes to their string
     descriptions.

     在 3.2 版被加入.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_ASYNC_ENTITY

 -- 資料:
          xml.parsers.expat.errors.XML_ERROR_ATTRIBUTE_EXTERNAL_ENTITY_REF

     An entity reference in an attribute value referred to an external
     entity instead of an internal entity.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_BAD_CHAR_REF

     A character reference referred to a character which is illegal in
     XML (for example, character ‘0’, or '‘&#0;’').

 -- 資料: xml.parsers.expat.errors.XML_ERROR_BINARY_ENTITY_REF

     An entity reference referred to an entity which was declared with a
     notation, so cannot be parsed.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_DUPLICATE_ATTRIBUTE

     An attribute was used more than once in a start tag.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_INCORRECT_ENCODING

 -- 資料: xml.parsers.expat.errors.XML_ERROR_INVALID_TOKEN

     Raised when an input byte could not properly be assigned to a
     character; for example, a NUL byte (value ‘0’) in a UTF-8 input
     stream.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_JUNK_AFTER_DOC_ELEMENT

     Something other than whitespace occurred after the document
     element.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_MISPLACED_XML_PI

     An XML declaration was found somewhere other than the start of the
     input data.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_NO_ELEMENTS

     The document contains no elements (XML requires all documents to
     contain exactly one top-level element)..

 -- 資料: xml.parsers.expat.errors.XML_ERROR_NO_MEMORY

     Expat was not able to allocate memory internally.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_PARAM_ENTITY_REF

     A parameter entity reference was found where it was not allowed.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_PARTIAL_CHAR

     An incomplete character was found in the input.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_RECURSIVE_ENTITY_REF

     An entity reference contained another reference to the same entity;
     possibly via a different name, and possibly indirectly.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_SYNTAX

     Some unspecified syntax error was encountered.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_TAG_MISMATCH

     An end tag did not match the innermost open start tag.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_UNCLOSED_TOKEN

     Some token (such as a start tag) was not closed before the end of
     the stream or the next token was encountered.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_UNDEFINED_ENTITY

     A reference was made to an entity which was not defined.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_UNKNOWN_ENCODING

     The document encoding is not supported by Expat.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_UNCLOSED_CDATA_SECTION

     A CDATA marked section was not closed.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_EXTERNAL_ENTITY_HANDLING

 -- 資料: xml.parsers.expat.errors.XML_ERROR_NOT_STANDALONE

     The parser determined that the document was not "standalone" though
     it declared itself to be in the XML declaration, and the
     ‘NotStandaloneHandler’ was set and returned ‘0’.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_UNEXPECTED_STATE

 -- 資料: xml.parsers.expat.errors.XML_ERROR_ENTITY_DECLARED_IN_PE

 -- 資料: xml.parsers.expat.errors.XML_ERROR_FEATURE_REQUIRES_XML_DTD

     An operation was requested that requires DTD support to be compiled
     in, but Expat was configured without DTD support.  This should
     never be reported by a standard build of the *note
     xml.parsers.expat: 10d. module.

 -- 資料:
          xml.parsers.expat.errors.XML_ERROR_CANT_CHANGE_FEATURE_ONCE_PARSING

     A behavioral change was requested after parsing started that can
     only be changed before parsing has started.  This is (currently)
     only raised by ‘UseForeignDTD()’.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_UNBOUND_PREFIX

     An undeclared prefix was found when namespace processing was
     enabled.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_UNDECLARING_PREFIX

     The document attempted to remove the namespace declaration
     associated with a prefix.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_INCOMPLETE_PE

     A parameter entity contained incomplete markup.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_XML_DECL

     The document contained no document element at all.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_TEXT_DECL

     There was an error parsing a text declaration in an external
     entity.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_PUBLICID

     Characters were found in the public id that are not allowed.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_SUSPENDED

     The requested operation was made on a suspended parser, but isn't
     allowed.  This includes attempts to provide additional input or to
     stop the parser.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_NOT_SUSPENDED

     An attempt to resume the parser was made when the parser had not
     been suspended.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_ABORTED

     This should not be reported to Python applications.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_FINISHED

     The requested operation was made on a parser which was finished
     parsing input, but isn't allowed.  This includes attempts to
     provide additional input or to stop the parser.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_SUSPEND_PE

 -- 資料: xml.parsers.expat.errors.XML_ERROR_RESERVED_PREFIX_XML

     An attempt was made to undeclare reserved namespace prefix ‘xml’ or
     to bind it to another namespace URI.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_RESERVED_PREFIX_XMLNS

     An attempt was made to declare or undeclare reserved namespace
     prefix ‘xmlns’.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_RESERVED_NAMESPACE_URI

     An attempt was made to bind the URI of one the reserved namespace
     prefixes ‘xml’ and ‘xmlns’ to another namespace prefix.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_INVALID_ARGUMENT

     This should not be reported to Python applications.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_NO_BUFFER

     This should not be reported to Python applications.

 -- 資料: xml.parsers.expat.errors.XML_ERROR_AMPLIFICATION_LIMIT_BREACH

     The limit on input amplification factor (from DTD and entities) has
     been breached.

註解
....


File: python.info,  Node: 網路協定 Internet protocols 及支援,  Next: 多媒體服務,  Prev: Structured Markup Processing Tools,  Up: Python 標準函式庫 Standard Library

5.21 網路協定 (Internet protocols) 及支援
=========================================

這個章節講述的模組實作了網路協定及相關技術的支援；他們全都是用 Python 實
作的。這裡的大多數模組都需要相依於系統的模組 *note socket: b8.，目前普遍
的平台都支援該模組。 以下為概述：

* Menu:

* webbrowser: webbrowser --- 方便的網頁瀏覽器控制器. 方便的網頁瀏覽器控制器
* wsgiref: wsgiref --- WSGI 工具與參考實作. WSGI 工具與參考實作
* urllib: urllib --- URL 處理模組. URL 處理模組
* urllib.request: urllib request --- 用來開啟 URLs 的可擴充函式庫. 用來開啟 URLs 的可擴充函式庫
* urllib.response: urllib response --- Response classes used by urllib. Response classes used by urllib
* urllib.parse: urllib parse --- 將 URL 剖析成元件. 將 URL 剖析成元件
* urllib.error: urllib error --- urllib request 引發的例外類別. urllib.request 引發的例外類別
* urllib.robotparser: urllib robotparser --- robots txt 的剖析器. robots.txt 的剖析器
* http: http --- HTTP 模組. HTTP 模組
* http.client: http client --- HTTP 協定用戶端. HTTP 協定用戶端
* ftplib: ftplib --- FTP 協定用戶端. FTP 協定用戶端
* poplib: poplib --- POP3 協定用戶端. POP3 協定用戶端
* imaplib: imaplib --- IMAP4 協定客戶端. IMAP4 協定客戶端
* smtplib: smtplib --- SMTP 協定用戶端. SMTP 協定用戶端
* uuid: uuid --- RFC 4122 定義的 UUID 物件. RFC 4122 定義的 UUID 物件
* socketserver: socketserver --- 用於網路伺服器的框架. 用於網路伺服器的框架
* http.server — HTTP 伺服器: http server — HTTP 伺服器.
* http.cookies: http cookies --- HTTP 狀態管理. HTTP 狀態管理
* http.cookiejar: http cookiejar --- HTTP 客戶端的 Cookie 處理. HTTP 客戶端的 Cookie 處理
* xmlrpc: xmlrpc --- XMLRPC 伺服器與用戶模組. XMLRPC 伺服器與用戶模組
* xmlrpc.client: xmlrpc client --- XML-RPC 客戶端存取. XML-RPC 客戶端存取
* xmlrpc.server: xmlrpc server --- 基本 XML-RPC 伺服器. 基本 XML-RPC 伺服器
* ipaddress: ipaddress --- IPv4/IPv6 操作函式庫. IPv4/IPv6 操作函式庫


File: python.info,  Node: webbrowser --- 方便的網頁瀏覽器控制器,  Next: wsgiref --- WSGI 工具與參考實作,  Up: 網路協定 Internet protocols 及支援

5.21.1 ‘webbrowser’ -- 方便的網頁瀏覽器控制器
---------------------------------------------

'原始碼：'Lib/webbrowser.py(1)

__________________________________________________________________

The *note webbrowser: fd. module provides a high-level interface to
allow displaying web-based documents to users.  Under most
circumstances, simply calling the *note open(): 3771. function from this
module will do the right thing.

Under Unix, graphical browsers are preferred under X11, but text-mode
browsers will be used if graphical browsers are not available or an X11
display isn't available.  If text-mode browsers are used, the calling
process will block until the user exits the browser.

If the environment variable ‘BROWSER’ exists, it is interpreted as the
*note os.pathsep: 1c46.-separated list of browsers to try ahead of the
platform defaults.  When the value of a list part contains the string
‘%s’, then it is interpreted as a literal browser command line to be
used with the argument URL substituted for ‘%s’; if the part does not
contain ‘%s’, it is simply interpreted as the name of the browser to
launch.  (2)

For non-Unix platforms, or when a remote browser is available on Unix,
the controlling process will not wait for the user to finish with the
browser, but allow the remote browser to maintain its own windows on the
display.  If remote browsers are not available on Unix, the controlling
process will launch a new browser and wait.

On iOS, the ‘BROWSER’ environment variable, as well as any arguments
controlling autoraise, browser preference, and new tab/window creation
will be ignored.  Web pages will 'always' be opened in the user's
preferred browser, in a new tab, with the browser being brought to the
foreground.  The use of the *note webbrowser: fd. module on iOS requires
the *note ctypes: 22. module.  If *note ctypes: 22. isn't available,
calls to *note open(): 3771. will fail.

The script ‘webbrowser’ can be used as a command-line interface for the
module.  It accepts a URL as the argument.  It accepts the following
optional parameters:

   * ‘-n’/‘--new-window’ opens the URL in a new browser window, if
     possible.

   * ‘-t’/‘--new-tab’ opens the URL in a new browser page ("tab").

The options are, naturally, mutually exclusive.  Usage example:

     python -m webbrowser -t "https://www.python.org"

*note Availability: 1c56.: not WASI.

This module does not work or is not available on WebAssembly.  See *note
WebAssembly 平台: 16e6. for more information.

The following exception is defined:

 -- 例外: webbrowser.Error

     Exception raised when a browser control error occurs.

The following functions are defined:

 -- 函式: webbrowser.open (url, new=0, autoraise=True)

     Display 'url' using the default browser.  If 'new' is 0, the 'url'
     is opened in the same browser window if possible.  If 'new' is 1, a
     new browser window is opened if possible.  If 'new' is 2, a new
     browser page ("tab") is opened if possible.  If 'autoraise' is
     ‘True’, the window is raised if possible (note that under many
     window managers this will occur regardless of the setting of this
     variable).

     Returns ‘True’ if a browser was successfully launched, ‘False’
     otherwise.

     Note that on some platforms, trying to open a filename using this
     function, may work and start the operating system's associated
     program.  However, this is neither supported nor portable.

     引發一個附帶引數 ‘url’ 的*note 稽核事件: 17bd. ‘webbrowser.open’。

 -- 函式: webbrowser.open_new (url)

     Open 'url' in a new window of the default browser, if possible,
     otherwise, open 'url' in the only browser window.

     Returns ‘True’ if a browser was successfully launched, ‘False’
     otherwise.

 -- 函式: webbrowser.open_new_tab (url)

     Open 'url' in a new page ("tab") of the default browser, if
     possible, otherwise equivalent to *note open_new(): 3773.

     Returns ‘True’ if a browser was successfully launched, ‘False’
     otherwise.

 -- 函式: webbrowser.get (using=None)

     Return a controller object for the browser type 'using'.  If
     'using' is ‘None’, return a controller for a default browser
     appropriate to the caller's environment.

 -- 函式: webbrowser.register (name, constructor, instance=None, *,
          preferred=False)

     Register the browser type 'name'.  Once a browser type is
     registered, the *note get(): 3775. function can return a controller
     for that browser type.  If 'instance' is not provided, or is
     ‘None’, 'constructor' will be called without parameters to create
     an instance when needed.  If 'instance' is provided, 'constructor'
     will never be called, and may be ‘None’.

     Setting 'preferred' to ‘True’ makes this browser a preferred result
     for a *note get(): 3775. call with no argument.  Otherwise, this
     entry point is only useful if you plan to either set the ‘BROWSER’
     variable or call *note get(): 3775. with a nonempty argument
     matching the name of a handler you declare.

     在 3.7 版的變更: 'preferred' keyword-only parameter was added.

A number of browser types are predefined.  This table gives the type
names that may be passed to the *note get(): 3775. function and the
corresponding instantiations for the controller classes, all defined in
this module.

Type Name                    Class Name                                    註解
                                                                           
---------------------------------------------------------------------------------------
                                                                           
‘'mozilla'’                  ‘Mozilla('mozilla')’
                             
                                                                           
‘'firefox'’                  ‘Mozilla('mozilla')’
                             
                                                                           
‘'epiphany'’                 ‘Epiphany('epiphany')’
                             
                                                                           
‘'kfmclient'’                ‘Konqueror()’                                 (1)
                                                                           
                                                                           
‘'konqueror'’                ‘Konqueror()’                                 (1)
                                                                           
                                                                           
‘'kfm'’                      ‘Konqueror()’                                 (1)
                                                                           
                                                                           
‘'opera'’                    ‘Opera()’
                             
                                                                           
‘'links'’                    ‘GenericBrowser('links')’
                             
                                                                           
‘'elinks'’                   ‘Elinks('elinks')’
                             
                                                                           
‘'lynx'’                     ‘GenericBrowser('lynx')’
                             
                                                                           
‘'w3m'’                      ‘GenericBrowser('w3m')’
                             
                                                                           
‘'windows-default'’          ‘WindowsDefault’                              (2)
                                                                           
                                                                           
‘'macosx'’                   ‘MacOSXOSAScript('default')’                  (3)
                                                                           
                                                                           
‘'safari'’                   ‘MacOSXOSAScript('safari')’                   (3)
                                                                           
                                                                           
‘'google-chrome'’            ‘Chrome('google-chrome')’
                             
                                                                           
‘'chrome'’                   ‘Chrome('chrome')’
                             
                                                                           
‘'chromium'’                 ‘Chromium('chromium')’
                             
                                                                           
‘'chromium-browser'’         ‘Chromium('chromium-browser')’
                             
                                                                           
‘'iosbrowser'’               ‘IOSBrowser’                                  (4)
                                                                           

註解：

  1. "Konqueror" is the file manager for the KDE desktop environment for
     Unix, and only makes sense to use if KDE is running.  Some way of
     reliably detecting KDE would be nice; the ‘KDEDIR’ variable is not
     sufficient.  Note also that the name "kfm" is used even when using
     the ‘konqueror’ command with KDE 2 -- the implementation selects
     the best strategy for running Konqueror.

  2. Only on Windows platforms.

  3. Only on macOS.

  4. Only on iOS.

在 3.2 版被加入: A new ‘MacOSXOSAScript’ class has been added and is
used on Mac instead of the previous ‘MacOSX’ class.  This adds support
for opening browsers not currently set as the OS default.

在 3.3 版被加入: Support for Chrome/Chromium has been added.

在 3.12 版的變更: Support for several obsolete browsers has been
removed.  Removed browsers include Grail, Mosaic, Netscape, Galeon,
Skipstone, Iceape, and Firefox versions 35 and below.

在 3.13 版的變更: Support for iOS has been added.

以下是一些簡單範例：

     url = 'https://docs.python.org/'

     # Open URL in a new tab, if a browser window is already open.
     webbrowser.open_new_tab(url)

     # Open URL in new window, raising the window if possible.
     webbrowser.open_new(url)

* Menu:

* Browser Controller Objects::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/webbrowser.py

   (2) Executables named here without a full path will be searched in
the directories given in the ‘PATH’ environment variable.


File: python.info,  Node: Browser Controller Objects,  Up: webbrowser --- 方便的網頁瀏覽器控制器

5.21.1.1 Browser Controller Objects
...................................

Browser controllers provide these methods which parallel three of the
module-level convenience functions:

 -- 屬性: controller.name

     System-dependent name for the browser.

 -- 方法: controller.open (url, new=0, autoraise=True)

     Display 'url' using the browser handled by this controller.  If
     'new' is 1, a new browser window is opened if possible.  If 'new'
     is 2, a new browser page ("tab") is opened if possible.

 -- 方法: controller.open_new (url)

     Open 'url' in a new window of the browser handled by this
     controller, if possible, otherwise, open 'url' in the only browser
     window.  Alias *note open_new(): 3773.

 -- 方法: controller.open_new_tab (url)

     Open 'url' in a new page ("tab") of the browser handled by this
     controller, if possible, otherwise equivalent to *note open_new():
     3773.

註解
....


File: python.info,  Node: wsgiref --- WSGI 工具與參考實作,  Next: urllib --- URL 處理模組,  Prev: webbrowser --- 方便的網頁瀏覽器控制器,  Up: 網路協定 Internet protocols 及支援

5.21.2 ‘wsgiref’ -- WSGI 工具與參考實作
---------------------------------------

'原始碼：'Lib/wsgiref(1)

__________________________________________________________________

網頁伺服器閘道介面 (WSGI) 是一個標準介面，用於連接網頁伺服器軟體與使用
Python 撰寫的網頁應用程式，擁有一個標準介面使得支援 WSGI 的應用程式可以
與多個不同的網頁伺服器運行。

只有網頁伺服器與程式框架的作者需要瞭解 WSGI 設計的每個細節與邊角案例，你
並不需要為了安裝 WSGI 應用程式或是使用現有框架撰寫網頁應用程式而必須理解
每個細節。

*note wsgiref: 100. 是 WSGI 規格的參考實作，可用於新增 WSGI 來支援網頁伺
服器或框架，它提供操作 WSGI 環境變數以及回應標頭的工具，用於實作 WSGI 伺
服器的基本類別，提供用於示範 HTTP 伺服器的 WSGI 應用程式、靜態型別檢查、
以及驗證 WSGI 伺服器與應用程式是否符合 WSGI 規格的驗證工具 ( PEP
3333(2))。

參閱 wsgi.readthedocs.io(3) 更多 WSGI 相關資訊，以及教學連結與其他資源。

* Menu:

* wsgiref.util: wsgiref util -- WSGI 環境工具. WSGI 環境工具
* wsgiref.headers: wsgiref headers -- WSGI 回應標頭工具. WSGI 回應標頭工具
* wsgiref.simple_server: wsgiref simple_server -- 一個簡單的 WSGI HTTP 伺服器. 一個簡單的 WSGI HTTP 伺服器
* wsgiref.validate: wsgiref validate --- WSGI 符合性檢查. WSGI 符合性檢查
* wsgiref.handlers: wsgiref handlers -- 伺服器 / 閘道基本類別. 伺服器 / 閘道基本類別
* wsgiref.types: wsgiref types -- 用於靜態型別檢查的 WSGI 型別. 用於靜態型別檢查的 WSGI 型別
* 範例: 範例<34>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/wsgiref

   (2) https://peps.python.org/pep-3333/

   (3) https://wsgi.readthedocs.io/


File: python.info,  Node: wsgiref util -- WSGI 環境工具,  Next: wsgiref headers -- WSGI 回應標頭工具,  Up: wsgiref --- WSGI 工具與參考實作

5.21.2.1 ‘wsgiref.util’ - WSGI 環境工具
.......................................

這個模組提供許多用於處理 WSGI 環境運作的功能。WSGI 環境是一個包含 HTTP 請
求變數的字典，如 PEP 3333(1) 所述。所有接受 'environ' 的參數的函式都需要
提供符合 WSGI 標準的字典；請參閱 PEP 3333(2) 獲取詳細規格，以及 *note
WSGIEnvironment: 377f. 獲取可用於使用型別註釋的型別別名。

 -- 函式: wsgiref.util.guess_scheme (environ)

     透過檢查 'environ' 字典中的 ‘HTTPS’ 環境變數，回傳
     ‘wsgi.url_scheme’ 應該是 "http" 或 "https" 的猜測。回傳值為一個字串
     。

     當建立一個包裝 CGI 或類似 FastCGI 的 CGI-like 協議閘道時，此函式非
     常有用。例如 FastCGI，通常提供這類協議的伺服器在通過 SSL 接收到請求
     時會包含 "1"，"yes"，或 "on" 的 ‘HTTPS’ 變數，因此，如果找到這樣的
     值，此函式回傳 "https"，否則回傳 "http"。

 -- 函式: wsgiref.util.request_uri (environ, include_query=True)

     根據 PEP 3333(3) 中 "URL Reconstruction" 章節所找到的演算法，回傳完
     整的請求 URI，可選擇性的包含查詢字串，如果 'include_query' 設為
     false，查詢字串不會被包含在結果的 URI 中。

 -- 函式: wsgiref.util.application_uri (environ)

     類似於 *note request_uri(): 3781.，但忽略 ‘PATH_INFO’ 和
     ‘QUERY_STRING’ 變數。結果是請求地址的應用程式物件的的基本 URI。

 -- 函式: wsgiref.util.shift_path_info (environ)

     將單一名稱從 ‘PATH_INFO’ 移到 ‘SCRIPT_NAME’ 並回傳該名稱。'environ'
     字典會在適當時機被 'modified'；如果你需要保留原始完好無損的
     ‘PATH_INFO’ 或 ‘SCRIPT_NAME’ 請使用副本。

     如果在 ‘PATH_INFO’ 中沒有剩餘的路徑片段，則回傳 ‘None’。

     通常，此程式用於處理請求 URI 的每一部分路徑，例如將路徑視為一系列的
     字典鍵此程式會修改傳入的環境，使其適用於呼叫位於目標 URI 的 WSGI 應
     用程式。例如，如果在 ‘/foo’ 上有一個 WSGI 應用程式且請求 URI 路徑為
     ‘/foo/bar/baz’，並且位於 ‘/foo’ 的 WSGI 應用程式呼叫 *note
     shift_path_info(): 3783.，它將接收字串 "bar"，而環境將被更新為適用
     於傳遞給位於 ‘/foo/bar’ 的 WSGI 應用程式。換句話說，‘SCRIPT_NAME’ 將
     從 ‘/foo’ 變更為 ‘/foo/bar’，而 ‘PATH_INFO’ 將從 ‘/bar/baz’ 變更為
     ‘/baz’。

     當 ‘PATH_INFO’ 只是一個 "/" 時， 此程式會回傳一個空字串，並在
     ‘SCRIPT_NAME’ 後添加尾部斜號，即使空路徑片段通常是被忽略的，而且
     ‘SCRIPT_NAME’ 通常不會以斜號結尾。這是刻意行為，以確保應用程式在使
     用這個程式進行物件遍歷時可以區分結尾為 ‘/x’ 和結尾為 ‘/x/’ 的 URIs。

 -- 函式: wsgiref.util.setup_testing_defaults (environ)

     為測試目的，以簡單的預設值更新 'environ' 。

     這個程式新增 WSGI 所需的各種參數，包括 ‘HTTP_HOST’、‘SERVER_NAME’、
     ‘SERVER_PORT’、‘REQUEST_METHOD’、‘SCRIPT_NAME’、‘PATH_INFO’，以及所
     有 PEP 3333(4) 定義的 ‘wsgi.*’ 變數，它只提供預設值，並且不會取代現
     有的這些變數設定。

     這個程式目的為了讓 WSGI 伺服器和應用程式的單元測試更容易建置虛擬環
     境。實際的 WSGI 伺服器或應用程式不應該使用它，因為所產生的數據是假
     的！

     用法範例：

          from wsgiref.util import setup_testing_defaults
          from wsgiref.simple_server import make_server

          # A relatively simple WSGI application. It's going to print out the
          # environment dictionary after being updated by setup_testing_defaults
          def simple_app(environ, start_response):
              setup_testing_defaults(environ)

              status = '200 OK'
              headers = [('Content-type', 'text/plain; charset=utf-8')]

              start_response(status, headers)

              ret = [("%s: %s\n" % (key, value)).encode("utf-8")
                     for key, value in environ.items()]
              return ret

          with make_server('', 8000, simple_app) as httpd:
              print("Serving on port 8000...")
              httpd.serve_forever()

除了上述的環境功能外，*note wsgiref.util: 105. 模組還提供以下各類工具：

 -- 函式: wsgiref.util.is_hop_by_hop (header_name)

     如果 'header_name' 是根據 RFC 2616(5) 所定義的 HTTP/1.1
     "Hop-by-Hop" 標頭，則回傳 ‘True’。

 -- 類別: wsgiref.util.FileWrapper (filelike, blksize=8192)

     *note wsgiref.types.FileWrapper: 3785. 協議的具體實作，用於將類檔案
     物件轉換為 *note iterator: 192.。產生的物件是 *note iterable:
     11bf.。當物件進行疊代時，將可選的 'blksize' 引數重複傳遞給
     'filelike' 物件的 ‘read()’ 方法來獲得將產生（yield）的位元組字串。
     當 ‘read()’ 回傳一個空位元組字串，代表疊代已結束且無法回復。

     如果 'filelike' 有 ‘close()’ 方法，則回傳的物件也會具有 ‘close()’ 方
     法，並在呼叫時呼叫 'filelike' 物件的 ‘close()’ 方法。

     用法範例：

          from io import StringIO
          from wsgiref.util import FileWrapper

          # We're using a StringIO-buffer for as the file-like object
          filelike = StringIO("This is an example file-like object"*10)
          wrapper = FileWrapper(filelike, blksize=5)

          for chunk in wrapper:
              print(chunk)

     在 3.11 版的變更: 已移除對 *note __getitem__(): 266. 方法的支援。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3333/

   (2) https://peps.python.org/pep-3333/

   (3) https://peps.python.org/pep-3333/

   (4) https://peps.python.org/pep-3333/

   (5) https://datatracker.ietf.org/doc/html/rfc2616.html


File: python.info,  Node: wsgiref headers -- WSGI 回應標頭工具,  Next: wsgiref simple_server -- 一個簡單的 WSGI HTTP 伺服器,  Prev: wsgiref util -- WSGI 環境工具,  Up: wsgiref --- WSGI 工具與參考實作

5.21.2.2 ‘wsgiref.headers’ - WSGI 回應標頭工具
..............................................

這個模組提供單一類別 *note Headers: e3a.，用於使用類似對映的介面方便地操
作 WSGI 回應標頭。

 -- 類別: wsgiref.headers.Headers ([headers])

     建立一個類似對映物件並包裝 'headers'，並且必須是符合 PEP 3333(1) 描
     述的 name/value 元組的標頭串列。'headers' 的預設值是一個空串列。

     *note Headers: e3a. 物件支援典型對映操作包括 ‘__getitem__()’、*note
     get(): 211f.、*note __setitem__(): 1434.、*note setdefault():
     101a.、*note __delitem__(): 1435. 以及 *note __contains__(): 1e33.。
     對於這些方法中的每一個，鍵是標頭名稱（以不區分大小寫方式處理），而
     值則是與該標頭名稱關聯的第一個值。設定標頭會刪除該標頭的所有現有值
     ，然後將新值添加到包裝的標頭串列末尾。標頭的現有順序通常保持不變，
     新標頭會添加到包裝串列的末尾。

     不同於字典，當你嘗試取得或刪除包裝的標頭串列不存在的鍵，*note
     Headers: e3a. 物件不會引發例外錯誤。取得不存在的標頭只會回傳
     ‘None’，而刪除不存在的標頭則不會有任何效果。

     *note Headers: e3a. 物件還支援 ‘keys()’、‘value()’、和 ‘items()’ 方
     法。由 ‘keys()’ 和 ‘items()’ 回傳的串列在存在多值標頭時可能會包含相
     同的鍵。*note Headers: e3a. 物件的 ‘len()’ 與 ‘items()’ 的長度相同
     ，也與包裝標頭串列的長度相同。實際上，‘items()’ 方法只是回傳包裝的
     標頭串列的副本。

     對 ‘Header’ 物件呼叫 ‘bytes()’ 會回傳適合作為 HTTP 傳輸回應標頭的格
     式化的位元組字串。每個標頭都與其值一起置於一行上，由冒號與空格分隔
     。每行以回車（carriage return）和換行（line feed）結束，而該位元組
     字串則以空行結束。

     除了對映介面和格式化功能外，*note Headers: e3a. 物件還具有以下查詢
     及附加多值標頭的以及附加 MIME 參數標頭的方法：

      -- 方法: get_all (name)

          回傳指定標頭的所有值的串列。

          回傳的串列按照它們在在原始的標頭串列出現的順序或是被添加到此實
          例的順序進行排序，並且可能包含重複的內容。任何被刪除並重新插入
          的欄位都會被添加到標頭串列的末尾。如果不存在指定名稱的欄位，則
          回傳空串列。

      -- 方法: add_header (name, value, **_params)

          添加一個（可能是多值的）標頭，可通過關鍵字引數來指定選擇性的
          MIME 參數。

          'name' 是要添加的標頭欄位。關鍵字引數可使於設定標頭欄位的 MIME
          參數。每一個參數必須是字串或是 ‘None’。由於破折號在 Python 識
          別符中是非法的，但是許多 MIME 參數名稱包含破折號，因此參數名稱
          的底線會轉換成破折號。如果參數值是字串，則以 ‘name="value"’ 的
          形式添加到標頭值參數中。如果它是 ‘None’，則僅添加參數名稱。（
          這使用於沒有值的 MIME 參數）使用範例：

               h.add_header('content-disposition', 'attachment', filename='bud.gif')

          上述操作將添加看起來像這樣的標頭：

               Content-Disposition: attachment; filename="bud.gif"

     在 3.5 版的變更: 'headers' 參數是可選的。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3333/


File: python.info,  Node: wsgiref simple_server -- 一個簡單的 WSGI HTTP 伺服器,  Next: wsgiref validate --- WSGI 符合性檢查,  Prev: wsgiref headers -- WSGI 回應標頭工具,  Up: wsgiref --- WSGI 工具與參考實作

5.21.2.3 ‘wsgiref.simple_server’ - 一個簡單的 WSGI HTTP 伺服器
..............................................................

這個模組實作一個簡單的的 HTTP 伺服器（基於 *note http.server: 68.）用於
提供 WSGI 應用程式。每個伺服器執行個體在特定的主機與埠提供單一的 WSGI 應
用程式。如果你想要在單一主機與埠上提供多個應用程式，你應該建立一個 WSGI
應用程式以剖析 ‘PATH_INFO’ 去選擇為每個請求呼叫哪個應用程式。（例如，使
用來自 *note wsgiref.util: 105. 的 ‘shift_path_info()’ 函式。）

 -- 函式: wsgiref.simple_server.make_server (host, port, app,
          server_class=WSGIServer, handler_class=WSGIRequestHandler)

     建立一個新的 WSGI 伺服器監聽 'host' 和 'port'，接受 'app' 的連線。
     回傳值是提供 'server_class' 的實例，並將使用指定的 'handler_class'
     處理請求。'app' 必須是一個 WSGI 應用程式物件，如 PEP 3333(1) 所定義
     。

     用法範例：

          from wsgiref.simple_server import make_server, demo_app

          with make_server('', 8000, demo_app) as httpd:
              print("Serving HTTP on port 8000...")

              # Respond to requests until process is killed
              httpd.serve_forever()

              # Alternative: serve one request, then exit
              httpd.handle_request()

 -- 函式: wsgiref.simple_server.demo_app (environ, start_response)

     這個函式是一個簡單但完整的 WSGI 應用程式，它回傳一個包含訊息 "Hello
     world!"  和在 'environ' 參數中提供的鍵值對串列的文字頁面。這對於驗
     證 WSGI 伺服器（例如 *note wsgiref.simple_server: 103.）是否能正確
     執行簡單的 WSGI 應用程式非常有用。

 -- 類別: wsgiref.simple_server.WSGIServer (server_address,
          RequestHandlerClass)

     建立一個 *note WSGIServer: 378c. 實例。'server_address' 應該是一個
     ‘(host, port)’ 元組，而 'RequestHandlerClass' 應該是 *note
     http.server.BaseHTTPRequestHandler: 1065. 的子類別，將用於處理請求
     。

     通常你不需要呼叫這個建構函式（constructor），因為 *note
     make_server(): 378a. 函式可以為你處理所有細節。

     *note WSGIServer: 378c. 是 *note http.server.HTTPServer: 378d. 的子
     類別，因此它的所有方法（例如 ‘serve_forever()’ 和
     ‘handle_request()’）都可用。*note WSGIServer: 378c. 也提供這些特定
     於 WSGI 的方法：

      -- 方法: set_app (application)

          將可呼叫的 'application' 設定為接收請求的 WSGI 應用程式。

      -- 方法: get_app ()

          回傳目前設定應用程式的可呼叫物件。

     然而，通常情況下你不需要去使用這些額外方法，因為 *note set_app():
     378e. 通常會被 *note make_server(): 378a. 呼叫而 *note get_app():
     378f. 主要存在於請求處理程式（handler）實例的好處上。

 -- 類別: wsgiref.simple_server.WSGIRequestHandler (request,
          client_address, server)

     為給定的 'request*（即一個 socket）、*client_address*（一個
     ''(host,port)'' 位元組）、*server' (*note WSGIServer: 378c. 實例) 建
     立一個 HTTP 處理程式（handler）。

     你不需要直接建立這個類別的實例；它們會在需要時由 *note WSGIServer:
     378c. 物件自動建立。不過，你可以建立這個類別的子類別並將其作為
     'handler_class' 提供給 *note make_server(): 378a. 函式。一些可能相
     關的方法可以在子類別中進行覆寫：

      -- 方法: get_environ ()

          唯一個請求回傳一個 *note WSGIEnvironment: 377f. 字典。預設的實
          作會複製 *note WSGIServer: 378c. 物件的 ‘base_environ’ 字典屬
          性的內容以及添加從 HTTP 請求中衍生的各種標頭。每次呼叫這個方法
          都應該回傳一個包含所有如 PEP 3333(2) 所指定的相關 CGI 環境變數
          的新字典。

      -- 方法: get_stderr ()

          回傳的物件應該被用作 ‘wsgi.errors’ 串流。預設實作只會回傳
          ‘sys.stderr’。

      -- 方法: handle ()

          處理 HTTP 請求。預設實作會使用 ‘wsgiref.handler’ 類別來建立處
          置程式（handler）實例來實作實際 WSGI 應用程式介面。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3333/

   (2) https://peps.python.org/pep-3333/


File: python.info,  Node: wsgiref validate --- WSGI 符合性檢查,  Next: wsgiref handlers -- 伺服器 / 閘道基本類別,  Prev: wsgiref simple_server -- 一個簡單的 WSGI HTTP 伺服器,  Up: wsgiref --- WSGI 工具與參考實作

5.21.2.4 ‘wsgiref.validate’ -- WSGI 符合性檢查
..............................................

當建立新的 WSGI 應用程式物件、框架、伺服器、或是中介軟體（middleware）時
，使用 *note wsgiref.validate: 106. 來驗證新程式碼的符合性可能會很有用。
這個模組提供一個函式用於建立 WSGI 應用程式物件，並用於驗證 WSGI 伺服器或
是閘道與 WSGI 應用程式物件之間的通訊，以檢查雙方協議的符合性。

請注意這個工具並不保證完全符合 PEP 3333(1)；這個模組中的錯誤不一定代表不
存在錯誤。但是，如果如果這個模組產生錯誤，那麼幾乎可以確定伺服器或應用程
式不是 100% 符合標準。

這個模組基於 Ian Bicking 的 "Python Paste" 函式庫的 ‘paste.lint’ 模組。

 -- 函式: wsgiref.validate.validator (application)

     包裝 'application' 並回傳一個新的 WSGI 應用程式物件。回傳的應用程式
     將轉發所有請求給原始的 'application'，並檢查 'application' 和呼叫它
     的伺服器是否符合 WSGI 規範和 RFC 2616(2)。

     任何在 *note AssertionError: 64e. 中偵測不符合結果都會發起例外；但
     請注意，如何處理這些錯誤取決於伺服器。例如，基於 *note
     wsgiref.handlers: 101. 的 *note wsgiref.simple_server: 103. 以及其
     他伺服器（未覆蓋錯誤處理方法以執行其他操作的伺服器）將僅輸出一條錯
     誤訊息，指示發生錯誤，並將回溯訊息輸出到 ‘sys.stderr’ 或是其他錯誤
     串流。

     這個包裝器也可以使用 *note warnings: fa. 模組生成輸出去指示一些可能
     有疑慮但實際上可能不會被 PEP 3333(3) 禁止的行為。除非使用 Python 命
     令列選項或 *note warnings: fa. API，抑制了這些警告，否則這類警告將
     被寫入到 ‘sys.stderr’（'not' ‘wsgi.errors’，除非它們碰巧是相同的物
     件）。

     用法範例：

          from wsgiref.validate import validator
          from wsgiref.simple_server import make_server

          # Our callable object which is intentionally not compliant to the
          # standard, so the validator is going to break
          def simple_app(environ, start_response):
              status = '200 OK'  # HTTP Status
              headers = [('Content-type', 'text/plain')]  # HTTP Headers
              start_response(status, headers)

              # This is going to break because we need to return a list, and
              # the validator is going to inform us
              return b"Hello World"

          # This is the application wrapped in a validator
          validator_app = validator(simple_app)

          with make_server('', 8000, validator_app) as httpd:
              print("Listening on port 8000....")
              httpd.serve_forever()

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3333/

   (2) https://datatracker.ietf.org/doc/html/rfc2616.html

   (3) https://peps.python.org/pep-3333/


File: python.info,  Node: wsgiref handlers -- 伺服器 / 閘道基本類別,  Next: wsgiref types -- 用於靜態型別檢查的 WSGI 型別,  Prev: wsgiref validate --- WSGI 符合性檢查,  Up: wsgiref --- WSGI 工具與參考實作

5.21.2.5 ‘wsgiref.handlers’ - 伺服器 / 閘道基本類別
...................................................

這個模組提供實作 WSGI 伺服器和閘道的基礎處理程式（handler）類別。這些基
底類別處理程式大部分與 WSGI 應用程式通訊的工作，只要它們被提供 CGI-like
環境，以及輸入、輸出和錯誤串流。

 -- 類別: wsgiref.handlers.CGIHandler

     這是基於 CGI 的呼叫方式並透過 ‘sys.stdin’、‘sys.stdout’、
     ‘sys.stderr’ 和 ‘os.environ’。當你擁有一個 WSGI 應用程式並希望將其
     作為 CGI 腳本運行時是很有用的。只需呼叫 ‘CGIHandler().run(app)’，其
     中 ‘app’ 是你希望呼叫的 WSGI 應用程式物件。

     這個類別是 *note BaseCGIHandler: 3798. 的子類別將 ‘wsgi.run_once’ 設
     置為 true，‘wsgi.multithread’ 設置為 false，並將
     ‘wsgi.multiprocess’ 設置為 true，並且始終使用 *note sys: c3. 和
     *note os: 91. 來獲取所需的 CGI 串流以及環境。

 -- 類別: wsgiref.handlers.IISCGIHandler

     這是用於在 Microsoft 的 IIS 網頁伺服器上部署時使用的 *note
     CGIHandler: 3797. 的一個專門替代選擇，無需設置 config 的
     allowPathInfo 選項（IIS>=7），或 metabase 的
     allowPathInfoForScriptMappings 選項（IIS<7）。

     預設情況下，IIS 提供的 ‘PATH_INFO’ 會在前面複製 ‘SCRIPT_NAME’，對於
     希望實作路由的 WSGI 應用程式造成問題。這個處理程式（handler）會移除
     任何這樣的重複路徑。

     IIS 可以配置去傳遞正確的 ‘PATH_INFO’，但這會導致 ‘PATH_TRANSLATED’
     是錯誤的問題。幸運的是這個變數很少被使用並且不受 WSGI 保證。然而，
     在 IIS<7 上，這個設置只能在虛擬主機層級進行，影響所有其他腳本的對映
     ，其中許多在暴露 ‘PATH_TRANSLATED’ 問題時會中斷。由於這個原因幾乎從
     不會使用修復的 IIS<7（即使是 IIS7 也很少使用它，因為它仍然沒有相應
     的 UI）。

     CGI 程式碼無法知道是否已設置該選項，因此提供了一個獨立的處理程式（
     handler）類別。它的使用方式與 *note CGIHandler: 3797. 相同，即透過
     呼叫 ‘IISCGIHandler().run(app)’ 來使用，其中 ‘app’ 是你希望呼叫的
     WSGI 應用程式物件。

     在 3.2 版被加入.

 -- 類別: wsgiref.handlers.BaseCGIHandler (stdin, stdout, stderr,
          environ, multithread=True, multiprocess=False)

     類似於 *note CGIHandler: 3797.，但不是使用 *note sys: c3. 和 *note
     os: 91. 模組，而是明確指定 CGI 環境與 I/O 串流。'multithread' 和
     'multiprocess' 值用於設置由處理程式（handler）實例運行的任何應用程
     式的旗標。

     這個類別是專門為除了 HTTP "origin servers" 以外的軟體一起使用的
     *note SimpleHandler: 379a. 的子類別。如果你正在撰寫一個使用
     ‘Status:’ 標頭來發送 HTTP 狀態的閘道協議實作（例如 CGI、FastCGI、
     SCGI 等），你可能會想要子類化這個類別來替代 *note SimpleHandler:
     379a.。

 -- 類別: wsgiref.handlers.SimpleHandler (stdin, stdout, stderr,
          environ, multithread=True, multiprocess=False)

     類似於 *note BaseCGIHandler: 3798.，但是被設計使用在 HTTP origin 伺
     服器。如果你正在撰寫 HTTP 伺服器的實作，你可能會想要子類別化這個類
     別來替代 *note BaseCGIHandler: 3798.。

     這個類別是 *note BaseHandler: 18f5. 的子類別。它透過建構器去覆寫
     ‘__init__()’、*note get_stdin(): 379b.、*note get_stderr(): 379c.、
     *note add_cgi_vars(): 379d.、*note _write(): 379e.、和 *note
     _flush(): 379f. 方法來明確提供設置環境與串流。提供的環境與串流被儲
     存在 ‘stdin’、‘stdout’、‘stderr’、和 ‘environ’ 環境中。

     'stdout' 的 *note write(): c82. 方法應該完整地寫入每個塊（chunk），
     像是 *note io.BufferedIOBase: 63a.。

 -- 類別: wsgiref.handlers.BaseHandler

     這是一個運行 WSGI 應用程式的抽象基底類別。每個實例將處理單個 HTTP 請
     求，儘管原則上你可以建立一個可重用於多個請求的子類別。

     *note BaseHandler: 18f5. 實例只有一個供外部使用的方法：

      -- 方法: run (app)

          運行指定 WSGI 應用程式，'app'。

     此方法在運行應用程式的過程中呼叫了所有其他 *note BaseHandler: 18f5.
     的方法，因此這些方法主要存在是為了允許自定義整個過程。

     以下方法必須在子類別中覆寫：

      -- 方法: _write (data)

          緩衝要傳送給用戶端的位元組 'data'。如果這個方法實際上傳送了數
          據也是可以的；當底層系統實際具有這種區分時，*note BaseHandler:
          18f5. 為了更好的效能進而分離寫入和刷新操作。

      -- 方法: _flush ()

          強制將緩衝數據傳送到用戶端。如果這是一個無操作（no-op）的方法
          （即，如果 *note _write(): 379e. 實際上發送了數據），那麼是可
          以的。

      -- 方法: get_stdin ()

          回傳一個與 *note InputStream: 37a1. 相容的物件並適用於用作當前
          正在處理請求的 ‘wsgi.input’。

      -- 方法: get_stderr ()

          回傳一個與 *note ErrorStream: 37a2. 相容的物件並適用於用作當前
          正在處理請求的 ‘wsgi.errors’。

      -- 方法: add_cgi_vars ()

          將當前請求的 CGI 變數插入到 ‘environ’ 屬性中。

     以下是你可能希望覆寫的其他方法和屬性。這個列表只是一個摘要，然而，
     不包括可以被覆寫的每個方法。在嘗試建立自定義的 *note BaseHandler:
     18f5. 子類別之前，你應該參考文件說明和原始碼以獲得更多資訊。

     用於自定義 WSGI 環境的屬性和方法：

      -- 屬性: wsgi_multithread

          用於 ‘wsgi.multithread’ 環境變數的值。在 *note BaseHandler:
          18f5. 中預設為 true，但在其他子類別中可能有不同的預設值（或由
          建構函式設置）。

      -- 屬性: wsgi_multiprocess

          用於 ‘wsgi.multiprocess’ 環境變數的值。在 *note BaseHandler:
          18f5. 中預設為 true，但在其他子類別中可能有不同的預設值（或由
          建構函式設置）。

      -- 屬性: wsgi_run_once

          用於 ‘wsgi.run_once’ 環境變數的值。在 *note BaseHandler: 18f5.
          中預設為 false，但 *note CGIHandler: 3797. 預設將其設置為
          true。

      -- 屬性: os_environ

          預設環境變數包含在每一個請求的 WSGI 環境中。預設情況下，這是在
          載入 *note wsgiref.handlers: 101. 時的 ‘os.environ’ 副本，但子
          類別可以在類別或實例層級建立自己的副本。注意字典應該被視為唯讀
          ，因為預設值在多個類別與實例中共享。

      -- 屬性: server_software

          如果設置 *note origin_server: 37a8. 屬性，則此屬性的值將用於設
          置預設的 ‘SERVER_SOFTWARE’ WSGI 環境變數，並且還將用於設置
          HTTP 回應中的預設 ‘Server:’ 標頭。對於不是 HTTP origin 伺服器
          的處置程式（例如 *note BaseCGIHandler: 3798. 和 *note
          CGIHandler: 3797.），此屬性將被忽略。

          在 3.3 版的變更: 將術語 "Python" 替換為特定實作的術語，如
          "CPython"、"Jython" 等。

      -- 方法: get_scheme ()

          回傳用於當前請求的 URL scheme。預設的實作使用 *note
          wsgiref.util: 105. 中的 ‘guess_scheme()’ 函式去猜測 scheme 是
          "http" 或是 "https"，基於目前請求的 ‘environ’ 變數。

      -- 方法: setup_environ ()

          將 ‘environ’ 屬性設置為完全填充的 WSGI 環境。預設的實作使用上
          述所有方法和屬性，以及 *note get_stdin(): 379b.、*note
          get_stderr(): 379c. 和 *note add_cgi_vars(): 379d. 方法以及
          *note wsgi_file_wrapper: 37ab. 屬性。如果不呈現它也會插入一個
          ‘SERVER_SOFTWARE’ 關鍵字，只要 *note origin_server: 37a8. 屬性
          是一個 true 值並且 *note server_software: 37a7. 屬性被設置。

     用於自定義例外處理的屬性和方法：

      -- 方法: log_exception (exc_info)

          將 'exc_info' 元組記錄到伺服器日誌中。'exc_info' 是一個
          ‘(type, value, traceback)’ 元組。預設實作只是將追蹤資訊寫入到
          請求的 ‘wsgi.errors’ 串流中並刷新它。子類別可以覆蓋此方法以更
          改格式或重新定向輸出，將追蹤資訊發送給管理員，或執行其他被認為
          合適的操作。

      -- 屬性: traceback_limit

          預設的 *note log_exception(): 37ac. 方法追蹤輸出中包含的最大幀
          數 。如果為 ‘None’，則包含所有幀。

      -- 方法: error_output (environ, start_response)

          這個方法是一個為使用者去產生錯誤頁面的 WSGI 應用程式。只有在標
          頭傳送給用戶端前如果發生錯誤才會被呼叫。

          此方法使用 ‘sys.exception()’ 存取當前的錯誤，當呼叫它（如 PEP
          3333(1) 的 "Error Handling" 部分所描述）時應該傳遞資訊給
          'start_response'。

          預設的實作只是使用 *note error_status: 37af.、*note
          error_headers: 37b0. 和 *note error_body: 37b1. 屬性產生輸出頁
          面。子類別可以覆蓋此方法以生成更動態的錯誤輸出。

          然而，從安全的角度並不建議向任何普通使用者顯示診斷資訊；理想情
          況下，你應該需要採取特殊措施才能啟用診斷輸出，這就是預設實作不
          包括任何診斷資訊的原因。

      -- 屬性: error_status

          用於錯誤回應的 HTTP 狀態。這應該是一個按照 PEP 3333(2) 定義的
          狀態字串；預設為 500 狀態碼和訊息。

      -- 屬性: error_headers

          用於錯誤回應的 HTTP 標頭。這應該是一個 WSGI 回應標頭的串列（
          ‘(name, value)’ 元組），如 PEP 3333(3) 中所描述。預設串列只設
          置內容種類為 ‘text/plain’。

      -- 屬性: error_body

          錯誤回應的主體。這應該是一個 HTTP 回應內容的位元組字串。預設為
          純文字 "A server error occurred.  Please contact the
          administrator."

     用於 PEP 3333(4) 中的 "Optional Platform-Specific File Handling" 功
     能的方法和屬性：

      -- 屬性: wsgi_file_wrapper

          一個 ‘wsgi.file_wrapper’ 工廠函式（factory），與 *note
          wsgiref.types.FileWrapper: 3785. 相容，或者為 ‘None’。這個屬性
          的預設值是 *note wsgiref.util.FileWrapper: 6da. 類別。

      -- 方法: sendfile ()

          覆蓋以實作特定平台的檔案傳輸。只有當應用程式的回傳值是由 *note
          wsgi_file_wrapper: 37ab. 屬性指定的類別實例時才會呼叫此方法。
          如果它能夠成功傳輸檔案應該回傳一個 true 值，以便不執行預設的傳
          輸程式碼。該方法的預設實作只回傳一個 false 值。

     其他方法和屬性：

      -- 屬性: origin_server

          這個屬性應該被設置為 true 值，如果處理程式（handler）的 *note
          _write(): 379e. 和 *note _flush(): 379f. 被用於直接與用戶端通
          訊，而不是透過 CGI-like 的閘道協議希望 HTTP 狀態在特殊的
          ‘Status:’ 標頭中。

          這個屬性在 *note BaseCGIHandler: 3798. 預設值為 true，但是在
          *note BaseCGIHandler: 3798. 和 *note CGIHandler: 3797. 為
          false。

      -- 屬性: http_version

          如果 *note origin_server: 37a8. 為 true，則此字串屬性用於設定
          傳送給用戶端的回應的 HTTP 版本。預設為 ‘"1.0"’。

 -- 函式: wsgiref.handlers.read_environ ()

     從 ‘os.environ’ 轉碼 CGI 變數到 PEP 3333(5) 中的 "bytes in unicode"
     字串，並回傳一個新字典。這個函式被 *note CGIHandler: 3797. 和 *note
     IISCGIHandler: 3799. 使用來直接替代 ‘os.environ’，在所有平台和使用
     Python 3 的網頁伺服器上不一定符合 WSGI 標準，具體來說，在 OS 的實際
     環境是 Unicode（例如 Windows）的情況下，或者在環境是位元組的情況下
     ，但 Python 用於解碼它的系統編碼不是 ISO-8859-1 （例如使用 UTF-8 的
     Unix 系統）。

     如果你自己正在實作 CGI-based 處理程式（handler），你可能想要使用這
     個函式來替換單純直接從 ‘os.environ’ 中複製值。

     在 3.2 版被加入.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3333/

   (2) https://peps.python.org/pep-3333/

   (3) https://peps.python.org/pep-3333/

   (4) https://peps.python.org/pep-3333/

   (5) https://peps.python.org/pep-3333/


File: python.info,  Node: wsgiref types -- 用於靜態型別檢查的 WSGI 型別,  Next: 範例<34>,  Prev: wsgiref handlers -- 伺服器 / 閘道基本類別,  Up: wsgiref --- WSGI 工具與參考實作

5.21.2.6 ‘wsgiref.types’ - 用於靜態型別檢查的 WSGI 型別
.......................................................

這個模組提供在 PEP 3333(1) 中所描述的各種用於靜態型別檢查的型別。

在 3.11 版被加入.

 -- 類別: wsgiref.types.StartResponse

     一個描述 start_response()(2) 可呼叫物件的 *note typing.Protocol:
     249. ( PEP 3333(3))。

 -- 資料: wsgiref.types.WSGIEnvironment

     一個描述 WSGI 環境字典的型別別名。

 -- 資料: wsgiref.types.WSGIApplication

     一個描述 WSGI 應用程式可呼叫物件的型別別名。

 -- 類別: wsgiref.types.InputStream

     一個描述 WSGI 輸入串流(4)的 *note typing.Protocol: 249.。

 -- 類別: wsgiref.types.ErrorStream

     一個描述 WSGI 錯誤串流(5)的 *note typing.Protocol: 249.。

 -- 類別: wsgiref.types.FileWrapper

     一個描述檔案包裝器(6)的 *note typing.Protocol: 249.。請參閱 *note
     wsgiref.util.FileWrapper: 6da. 來瞭解此協議的具體實作。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3333/

   (2) https://peps.python.org/pep-3333/#the-start-response-callable

   (3) https://peps.python.org/pep-3333/

   (4) https://peps.python.org/pep-3333/#input-and-error-streams

   (5) https://peps.python.org/pep-3333/#input-and-error-streams

   (6) 
https://peps.python.org/pep-3333/#optional-platform-specific-file-handling


File: python.info,  Node: 範例<34>,  Prev: wsgiref types -- 用於靜態型別檢查的 WSGI 型別,  Up: wsgiref --- WSGI 工具與參考實作

5.21.2.7 範例
.............

這個一個運作中的 "Hello World" WSGI 應用程式：

     """
     Every WSGI application must have an application object - a callable
     object that accepts two arguments. For that purpose, we're going to
     use a function (note that you're not limited to a function, you can
     use a class for example). The first argument passed to the function
     is a dictionary containing CGI-style environment variables and the
     second variable is the callable object.
     """
     from wsgiref.simple_server import make_server


     def hello_world_app(environ, start_response):
         status = "200 OK"  # HTTP Status
         headers = [("Content-type", "text/plain; charset=utf-8")]  # HTTP Headers
         start_response(status, headers)

         # The returned object is going to be printed
         return [b"Hello World"]

     with make_server("", 8000, hello_world_app) as httpd:
         print("Serving on port 8000...")

         # Serve until process is killed
         httpd.serve_forever()

提供當前目錄的 WSGI 應用程式範例，並接受命令列上的可選目錄和埠號（預設：
8000）：

     """
     Small wsgiref based web server. Takes a path to serve from and an
     optional port number (defaults to 8000), then tries to serve files.
     MIME types are guessed from the file names, 404 errors are raised
     if the file is not found.
     """
     import mimetypes
     import os
     import sys
     from wsgiref import simple_server, util


     def app(environ, respond):
         # Get the file name and MIME type
         fn = os.path.join(path, environ["PATH_INFO"][1:])
         if "." not in fn.split(os.path.sep)[-1]:
             fn = os.path.join(fn, "index.html")
         mime_type = mimetypes.guess_file_type(fn)[0]

         # Return 200 OK if file exists, otherwise 404 Not Found
         if os.path.exists(fn):
             respond("200 OK", [("Content-Type", mime_type)])
             return util.FileWrapper(open(fn, "rb"))
         else:
             respond("404 Not Found", [("Content-Type", "text/plain")])
             return [b"not found"]


     if __name__ == "__main__":
         # Get the path and port from command-line arguments
         path = sys.argv[1] if len(sys.argv) > 1 else os.getcwd()
         port = int(sys.argv[2]) if len(sys.argv) > 2 else 8000

         # Make and start the server until control-c
         httpd = simple_server.make_server("", port, app)
         print(f"Serving {path} on port {port}, control-C to stop")
         try:
             httpd.serve_forever()
         except KeyboardInterrupt:
             print("Shutting down.")
             httpd.server_close()


File: python.info,  Node: urllib --- URL 處理模組,  Next: urllib request --- 用來開啟 URLs 的可擴充函式庫,  Prev: wsgiref --- WSGI 工具與參考實作,  Up: 網路協定 Internet protocols 及支援

5.21.3 ‘urllib’ -- URL 處理模組
-------------------------------

'原始碼：'Lib/urllib/(1)

__________________________________________________________________

‘urllib’ 是一個蒐集了許多處理 URLs 的 module（模組）的 package（套件）：

   * *note urllib.request: f4. 用來開啟和讀取 URLs

   * *note urllib.error: f2. 包含了 *note urllib.request: f4. 所引發的例
     外

   * *note urllib.parse: f3. 用來剖析 URLs

   * *note urllib.robotparser: f6. 用來剖析 ‘robots.txt’ 檔案

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/urllib/


File: python.info,  Node: urllib request --- 用來開啟 URLs 的可擴充函式庫,  Next: urllib response --- Response classes used by urllib,  Prev: urllib --- URL 處理模組,  Up: 網路協定 Internet protocols 及支援

5.21.4 ‘urllib.request’ -- 用來開啟 URLs 的可擴充函式庫
-------------------------------------------------------

'原始碼：'Lib/urllib/request.py(1)

__________________________________________________________________

*note urllib.request: f4. module（模組）定義了一些函式與 class（類別）用
以開啟 URLs（大部分是 HTTP），並處理各式複雜情況如：basic 驗證與 digest
驗證、重新導向、cookies。

也參考
......

有關於更高階的 HTTP 用戶端介面，推薦使用 Requests 套件(2)。

     警告: On macOS it is unsafe to use this module in programs using
     *note os.fork(): 17b. because the *note getproxies(): 37bc.
     implementation for macOS uses a higher-level system API. Set the
     environment variable ‘no_proxy’ to ‘*’ to avoid this problem (e.g.
     ‘os.environ["no_proxy"] = "*"’).

*note Availability: 1c56.: not WASI.

This module does not work or is not available on WebAssembly.  See *note
WebAssembly 平台: 16e6. for more information.

*note urllib.request: f4. module 定義下列函式：

 -- 函式: urllib.request.urlopen (url, data=None[, timeout], *,
          context=None)

     打開 'url'，其值可以是一個包含有效且適當編碼 URL 的字串或是一個
     *note Request: f7b. 物件。

     'data' 必須是一個包含傳送給伺服器額外資料的物件，若不需要傳送額外資
     料則指定為 ‘None’。更多細節請見 *note Request: f7b.。

     urllib.request module 使用 HTTP/1.1 並包含 ‘Connection:close’
     header（標頭）在其 HTTP 請求中。

     透過選擇性參數 'timeout' 來指定 blocking operations（阻塞性操作，如
     ：嘗試連接）的 timeout（超時時間），以秒為單位。若沒有指定值，則會
     使用全域預設超時時間設定。實際上，此參數僅作用於 HTTP、HTTPS 以及
     FTP 的連接。

     若 'context' 有被指定時，它必須是一個 *note ssl.SSLContext: 276. 的
     實例並描述著各種 SSL 選項。更多細節請見 *note HTTPSConnection:
     ae5.。

     這個函式總是回傳一個可作為 *note context manager: 576. 使用的物件，
     並有著特性 (property) 'url'、'headers' 與 'status'。欲知更多這些特
     性細節請參見 *note urllib.response.addinfourl: 37bd.。

     對於 HTTP 與 HTTPS 的 URLs，這個函式回傳一個稍有不同的 *note
     http.client.HTTPResponse: 1068. 物件。除了上述提到的三個方法外，另
     有 msg 屬性並有著與 *note reason: 37be. 相同的資訊 -- 由伺服器回傳
     的原因敘述 (reason phrase)，而不是在 *note HTTPResponse: 1068. 文件
     中提到的回應 headers。

     對於 FTP、檔案、資料的 URLs、以及那些由傳統 classes *note
     URLopener: 2e0. 與 *note FancyURLopener: 2e1. 所處理的請求，這個函
     式會回傳一個 *note urllib.response.addinfourl: 37bd. 物件。

     當遇到協定上的錯誤時會引發 *note URLError: 37bf.。

     請注意若沒有 handler 處理請求時，‘None’ 值將會被回傳。（即使有預設
     的全域類別 *note OpenerDirector: 37c0. 使用 *note UnknownHandler:
     37c1. 來確保這種情況不會發生）

     另外，若有偵測到代理服務的設定（例如當 ‘*_proxy’ 環境變數像是：
     :envvar:!http_proxy' 有被設置時），*note ProxyHandler: 18d5. 會被預
     設使用以確保請求有透過代理服務來處理。

     Python 2.6 或更早版本的遺留函式 ‘urllib.urlopen’ 已經不再被維護；新
     函式 *note urllib.request.urlopen(): 275. 對應到舊函式
     ‘urllib2.urlopen’。有關代理服務的處理，以往是透過傳遞 dictionary（
     字典）參數給 ‘urllib.urlopen’ 來取得的，現在則可以透過 *note
     ProxyHandler: 18d5. 物件來取得。

     預設的 opener 會觸發一個 *note auditing event: 17bd.
     ‘urllib.Request’ 與其從請求物件中所獲得的引數 ‘fullurl’、‘data’、
     ‘headers’、‘method’。

     在 3.2 版的變更: 新增 'cafile' 與 'capath'。

     HTTPS 虛擬主機 (virtual hosts) 現已支援，只要 *note ssl.HAS_SNI:
     32b1. 的值為 true。

     'data' 可以是一個可疊代物件。

     在 3.3 版的變更: 'cadefault' 被新增。

     在 3.4.3 版的變更: 'context' 被新增。

     在 3.10 版的變更: 當 'context' 沒有被指定時，HTTPS 連線現在會傳送一
     個帶有協定指示器 ‘http/1.1’ 的 ALPN 擴充 (extension)。自訂的
     'context' 應該利用 *note set_alpn_protocols(): e06. 來自行設定 ALPN
     協定。

     在 3.13 版的變更: Remove 'cafile', 'capath' and 'cadefault'
     parameters: use the 'context' parameter instead.

 -- 函式: urllib.request.install_opener (opener)

     安裝一個 *note OpenerDirector: 37c0. 實例作為預設的全域 opener。僅
     在當你想要讓 urlopen 使用該 opener 時安裝一個 opener，否則的話應直
     接呼叫 *note OpenerDirector.open(): f7f. 而非 *note urlopen():
     275.。程式碼不會檢查 class 是否真的為 *note OpenerDirector: 37c0.，
     而是任何具有正確介面的 class 都能適用。

 -- 函式: urllib.request.build_opener ([handler, ...])

     回傳一個 *note OpenerDirector: 37c0. 實例，以給定的順序把 handlers
     串接起來。'handler's 可以是 *note BaseHandler: 37c4. 的實例，亦或是
     *note BaseHandler: 37c4. 的 subclasses（這個情況下必須有不帶參數的
     建構函式能夠被呼叫）。以下 classes 的實例順位會在 'handler's 之前，
     除非 'handler's 已經包含它們，是它們的實例，或是它們的 subclasses：
     *note ProxyHandler: 18d5.（如果代理服務設定被偵測到）、*note
     UnknownHandler: 37c1.、*note HTTPHandler: 37c5.、*note
     HTTPDefaultErrorHandler: 37c6.、*note HTTPRedirectHandler: 37c7.、
     *note FTPHandler: 37c8.、*note FileHandler: 37c9.、*note
     HTTPErrorProcessor: 37ca.。

     如果 Python 安裝時已帶有 SSL 支援（如果 *note ssl: bb. module 能夠
     被 import），則 *note HTTPSHandler: 11bb. 也在上述 class 之中。

     一個 *note BaseHandler: 37c4. 的 subclass 可能透過改變其
     ‘handler_order’ 屬性來調整它在 handlers list 中的位置。

 -- 函式: urllib.request.pathname2url (path)

     將路徑名 'path' 從路徑的本地語法 (local syntax) 轉換為 URL 中的
     path component（路徑元件）格式。本函式並不會產生完整的 URL。回傳值
     將使用 *note quote(): b4a. 函式先進行編碼過。

 -- 函式: urllib.request.url2pathname (path)

     將一個用 "%" 編碼過的 URL path component 'path' 轉換為路徑的本地語
     法 (local syntax)。本函式並不接受完整的 URL。本函式使用 *note
     unquote(): 1689. 來將 'path' 解碼。

 -- 函式: urllib.request.getproxies ()

     這個輔助函式 (helper function) 回傳一個代理伺服器 URL mappings（對
     映）的 dictionary。在所有的作業系統中，它首先掃描環境中有著
     ‘<scheme>_proxy’ 名稱的變數（忽略大小寫的），如果找不到的話就會在
     macOS 中的系統設定 (System Configuration) 或是 Windows 系統中的
     Windows Systems Registry 尋找代理服務設定。如果大小寫的環境變數同時
     存在且值有不同，小寫的環境變數會被選用。

          備註: 如果環境變數 ‘REQUEST_METHOD’ 有被設置（通常這代表著你的
          script 是運行在一個共用閘道介面 (CGI) 環境中），那麼環境變數
          ‘HTTP_PROXY’ （大寫的 ‘_PROXY’）將被忽略。這是因為變數可以透過
          使用 "Proxy:" HTTP header 被注入。如果需要在共用閘道介面環境中
          使用 HTTP 代理服務，可以明確使用 ‘ProxyHandler’，亦或是確認變
          數名稱是小寫的（或至少 ‘_proxy’ 後綴是小寫的）。

提供了以下的 classes：

 -- 類別: urllib.request.Request (url, data=None, headers={},
          origin_req_host=None, unverifiable=False, method=None)

     這個 class 是一個 URL 請求的抽象 class。

     'url' 是一個包含有效且適當編碼的 URL 字串。

     'data' 必須是一個包含要送到伺服器的附加資料的物件，若不需帶附加資料
     則其值應為 ‘None’。目前 HTTP 請求是唯一有使用 'data' 參數的，其支援
     的物件型別包含位元組、類檔案物件 (file-like objects)、以及可疊代的
     類位元組串物件 (bytes-like objects)。如果沒有提供 ‘Content-Length’
     及 ‘Transfer-Encoding’ headers 欄位，*note HTTPHandler: 37c5. 將會
     根據 'data' 的型別設置這些 header。‘Content-Length’ 會被用來傳送位
     元組串物件，而 RFC 7230(3) 章節 3.3.1 所定義的 ‘Transfer-Encoding:
     chunked’ 則會被用來傳送檔案或是其它可疊代物件 (iterables)。

     對於一個 HTTP POST 請求方法，'data' 應為一個標準
     ‘application/x-www-form-urlencoded’ 格式的 buffer。*note
     urllib.parse.urlencode(): e37. 方法接受一個 mapping 或是 sequence（
     序列）的 2-tuples，並回傳一個對應格式的 ASCII 字串。在被作為 'data'
     參數前它應該被編碼成位元組串。

     'headers' 必須是一個 dictionary，並會被視為如同每對 key 和 value 作
     為引數來呼叫 *note add_header(): 37cd.。經常用於「偽裝」
     ‘User-Agent’ header 的值，這個 header 是用來讓一個瀏覽器向伺服器表
     明自己的身分 -- 有些 HTTP 伺服器僅允許來自普通瀏覽器的請求，而不接
     受來自程式腳本的請求。例如，Mozilla Firefox 會將 header 的值設為
     ‘"Mozilla/5.0 (X11; U; Linux i686) Gecko/20071127
     Firefox/2.0.0.11"’，而 *note urllib: f1. 的值則是
     ‘"Python-urllib/2.6"’（在 Python 2.6 上）。所有 header 的鍵都會以
     camel case（駝峰式大小寫）來傳送。

     當有給定 'data' 引數時，一個適當的 ‘Content-Type’ header 應該被設置
     。如果這個 header 沒有被提供且 'data' 也不為 ‘None’ 時，預設值
     ‘Content-Type: application/x-www-form-urlencoded’ 會被新增至請求中
     。

     接下來的兩個引數的介紹提供給那些有興趣正確處理第三方 HTTP cookies 的
     使用者：

     'origin_req_host' 應為原始傳輸互動的請求主機 (request-host)，如同在
     RFC 2965(4) 中的定義。預設值為 ‘http.cookiejar.request_host(self)’。
     這是使用者發起的原始請求的主機名稱或是 IP 位址。例如當請求是要求一
     個 HTML 文件中的一個影像，則這個屬性應為請求包含影像頁面的請求主機
     。

     'unverifiable' 應該標示一個請求是否是無法驗證的，如同在 RFC 2965(5)
     中的定義。其預設值為 ‘False’。一個無法驗證的請求是指使用者沒有機會
     去批准請求的 URL，例如一個對於 HTML 文件中的影像所做的請求，而使用
     者沒有機會去批准是否能自動擷取影像，則這個值應該為 true。

     'method' 應為一個標示 HTTP 請求方法的字串（例如：‘'HEAD'’）。如果有
     提供值，則會被存在 *note method: f7c. 屬性中且被 *note
     get_method(): 1102. 所使用。當 'data' 是 ‘None’ 時，其預設值為
     ‘'GET'’，否則預設值為 ‘'POST'’。Subclasses 可以透過設置其 *note
     method: f7c. 屬性來設定不一樣的預設請求方法。

          備註: 如果資料物件無法重複提供其內容（例如一個檔案或是只能產生
          一次內容的可疊代物件）且請求因為 HTTP 重導向 (redirects) 或是
          HTTP 驗證 (authentication) 而被重新嘗試傳送，則該請求不會正常
          運作。'data' 會接在 headers 之後被送至 HTTP 伺服器。此函式庫沒
          有支援 100-continue expectation。

     在 3.3 版的變更: 新增 *note Request.method: f7c. 引數到 Request
     class。

     在 3.4 版的變更: 能夠在 class 中設置預設的 *note Request.method:
     f7c.。

     在 3.6 版的變更: 如果 ‘Content-Length’ 尚未被提供且 'data' 既不是
     ‘None’ 也不是一個位元組串物件，則不會觸發錯誤，並 fall back（後備）
     使用分塊傳輸編碼 (chunked transfer encoding)。

 -- 類別: urllib.request.OpenerDirector

     The *note OpenerDirector: 37c0. class opens URLs via *note
     BaseHandler: 37c4.s chained together.  It manages the chaining of
     handlers, and recovery from errors.

 -- 類別: urllib.request.BaseHandler

     This is the base class for all registered handlers -- and handles
     only the simple mechanics of registration.

 -- 類別: urllib.request.HTTPDefaultErrorHandler

     A class which defines a default handler for HTTP error responses;
     all responses are turned into *note HTTPError: f81. exceptions.

 -- 類別: urllib.request.HTTPRedirectHandler

     A class to handle redirections.

 -- 類別: urllib.request.HTTPCookieProcessor (cookiejar=None)

     A class to handle HTTP Cookies.

 -- 類別: urllib.request.ProxyHandler (proxies=None)

     Cause requests to go through a proxy.  If 'proxies' is given, it
     must be a dictionary mapping protocol names to URLs of proxies.
     The default is to read the list of proxies from the environment
     variables ‘<protocol>_proxy’.  If no proxy environment variables
     are set, then in a Windows environment proxy settings are obtained
     from the registry's Internet Settings section, and in a macOS
     environment proxy information is retrieved from the System
     Configuration Framework.

     To disable autodetected proxy pass an empty dictionary.

     The ‘no_proxy’ environment variable can be used to specify hosts
     which shouldn't be reached via proxy; if set, it should be a
     comma-separated list of hostname suffixes, optionally with ‘:port’
     appended, for example ‘cern.ch,ncsa.uiuc.edu,some.host:8080’.

          備註: ‘HTTP_PROXY’ will be ignored if a variable
          ‘REQUEST_METHOD’ is set; see the documentation on *note
          getproxies(): 37bc.

 -- 類別: urllib.request.HTTPPasswordMgr

     Keep a database of ‘(realm, uri) -> (user, password)’ mappings.

 -- 類別: urllib.request.HTTPPasswordMgrWithDefaultRealm

     Keep a database of ‘(realm, uri) -> (user, password)’ mappings.  A
     realm of ‘None’ is considered a catch-all realm, which is searched
     if no other realm fits.

 -- 類別: urllib.request.HTTPPasswordMgrWithPriorAuth

     A variant of *note HTTPPasswordMgrWithDefaultRealm: 37d0. that also
     has a database of ‘uri -> is_authenticated’ mappings.  Can be used
     by a BasicAuth handler to determine when to send authentication
     credentials immediately instead of waiting for a ‘401’ response
     first.

     在 3.5 版被加入.

 -- 類別: urllib.request.AbstractBasicAuthHandler (password_mgr=None)

     This is a mixin class that helps with HTTP authentication, both to
     the remote host and to a proxy.  'password_mgr', if given, should
     be something that is compatible with *note HTTPPasswordMgr: 37cf.;
     refer to section *note HTTPPasswordMgr 物件: 37d1. for information
     on the interface that must be supported.  If 'passwd_mgr' also
     provides ‘is_authenticated’ and ‘update_authenticated’ methods (see
     *note HTTPPasswordMgrWithPriorAuth 物件: 37d2.), then the handler
     will use the ‘is_authenticated’ result for a given URI to determine
     whether or not to send authentication credentials with the request.
     If ‘is_authenticated’ returns ‘True’ for the URI, credentials are
     sent.  If ‘is_authenticated’ is ‘False’, credentials are not sent,
     and then if a ‘401’ response is received the request is re-sent
     with the authentication credentials.  If authentication succeeds,
     ‘update_authenticated’ is called to set ‘is_authenticated’ ‘True’
     for the URI, so that subsequent requests to the URI or any of its
     super-URIs will automatically include the authentication
     credentials.

     在 3.5 版被加入: 新增 ‘is_authenticated’ 的支援。

 -- 類別: urllib.request.HTTPBasicAuthHandler (password_mgr=None)

     Handle authentication with the remote host.  'password_mgr', if
     given, should be something that is compatible with *note
     HTTPPasswordMgr: 37cf.; refer to section *note HTTPPasswordMgr
     物件: 37d1. for information on the interface that must be
     supported.  HTTPBasicAuthHandler will raise a *note ValueError:
     1e7. when presented with a wrong Authentication scheme.

 -- 類別: urllib.request.ProxyBasicAuthHandler (password_mgr=None)

     Handle authentication with the proxy.  'password_mgr', if given,
     should be something that is compatible with *note HTTPPasswordMgr:
     37cf.; refer to section *note HTTPPasswordMgr 物件: 37d1. for
     information on the interface that must be supported.

 -- 類別: urllib.request.AbstractDigestAuthHandler (password_mgr=None)

     This is a mixin class that helps with HTTP authentication, both to
     the remote host and to a proxy.  'password_mgr', if given, should
     be something that is compatible with *note HTTPPasswordMgr: 37cf.;
     refer to section *note HTTPPasswordMgr 物件: 37d1. for information
     on the interface that must be supported.

 -- 類別: urllib.request.HTTPDigestAuthHandler (password_mgr=None)

     Handle authentication with the remote host.  'password_mgr', if
     given, should be something that is compatible with *note
     HTTPPasswordMgr: 37cf.; refer to section *note HTTPPasswordMgr
     物件: 37d1. for information on the interface that must be
     supported.  When both Digest Authentication Handler and Basic
     Authentication Handler are both added, Digest Authentication is
     always tried first.  If the Digest Authentication returns a 40x
     response again, it is sent to Basic Authentication handler to
     Handle.  This Handler method will raise a *note ValueError: 1e7.
     when presented with an authentication scheme other than Digest or
     Basic.

     在 3.3 版的變更: Raise *note ValueError: 1e7. on unsupported
     Authentication Scheme.

 -- 類別: urllib.request.ProxyDigestAuthHandler (password_mgr=None)

     Handle authentication with the proxy.  'password_mgr', if given,
     should be something that is compatible with *note HTTPPasswordMgr:
     37cf.; refer to section *note HTTPPasswordMgr 物件: 37d1. for
     information on the interface that must be supported.

 -- 類別: urllib.request.HTTPHandler

     A class to handle opening of HTTP URLs.

 -- 類別: urllib.request.HTTPSHandler (debuglevel=0, context=None,
          check_hostname=None)

     A class to handle opening of HTTPS URLs.  'context' and
     'check_hostname' have the same meaning as in *note
     http.client.HTTPSConnection: ae5.

     在 3.2 版的變更: 新增 'context' 與 'check_hostname'。

 -- 類別: urllib.request.FileHandler

     Open local files.

 -- 類別: urllib.request.DataHandler

     Open data URLs.

     在 3.4 版被加入.

 -- 類別: urllib.request.FTPHandler

     Open FTP URLs.

 -- 類別: urllib.request.CacheFTPHandler

     Open FTP URLs, keeping a cache of open FTP connections to minimize
     delays.

 -- 類別: urllib.request.UnknownHandler

     A catch-all class to handle unknown URLs.

 -- 類別: urllib.request.HTTPErrorProcessor

     Process HTTP error responses.

* Menu:

* Request Objects::
* OpenerDirector 物件::
* BaseHandler 物件::
* HTTPRedirectHandler 物件::
* HTTPCookieProcessor 物件::
* ProxyHandler 物件::
* HTTPPasswordMgr 物件::
* HTTPPasswordMgrWithPriorAuth 物件::
* AbstractBasicAuthHandler 物件::
* HTTPBasicAuthHandler 物件::
* ProxyBasicAuthHandler 物件::
* AbstractDigestAuthHandler 物件::
* HTTPDigestAuthHandler 物件::
* ProxyDigestAuthHandler 物件::
* HTTPHandler 物件::
* HTTPSHandler 物件::
* FileHandler 物件::
* DataHandler 物件::
* FTPHandler 物件::
* CacheFTPHandler 物件::
* UnknownHandler 物件::
* HTTPErrorProcessor 物件::
* 範例: 範例<35>.
* Legacy interface::
* urllib.request Restrictions: urllib request Restrictions.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/urllib/request.py

   (2) https://requests.readthedocs.io/en/master/

   (3) https://datatracker.ietf.org/doc/html/rfc7230.html

   (4) https://datatracker.ietf.org/doc/html/rfc2965.html

   (5) https://datatracker.ietf.org/doc/html/rfc2965.html


File: python.info,  Node: Request Objects,  Next: OpenerDirector 物件,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.1 Request Objects
........................

The following methods describe *note Request: f7b.'s public interface,
and so all may be overridden in subclasses.  It also defines several
public attributes that can be used by clients to inspect the parsed
request.

 -- 屬性: Request.full_url

     The original URL passed to the constructor.

     在 3.4 版的變更.

     Request.full_url is a property with setter, getter and a deleter.
     Getting *note full_url: f7d. returns the original request URL with
     the fragment, if it was present.

 -- 屬性: Request.type

     The URI scheme.

 -- 屬性: Request.host

     The URI authority, typically a host, but may also contain a port
     separated by a colon.

 -- 屬性: Request.origin_req_host

     The original host for the request, without port.

 -- 屬性: Request.selector

     The URI path.  If the *note Request: f7b. uses a proxy, then
     selector will be the full URL that is passed to the proxy.

 -- 屬性: Request.data

     The entity body for the request, or ‘None’ if not specified.

     在 3.4 版的變更: Changing value of *note Request.data: f7e. now
     deletes "Content-Length" header if it was previously set or
     calculated.

 -- 屬性: Request.unverifiable

     boolean, indicates whether the request is unverifiable as defined
     by RFC 2965(1).

 -- 屬性: Request.method

     The HTTP request method to use.  By default its value is *note
     None: 61b, which means that *note get_method(): 1102. will do its
     normal computation of the method to be used.  Its value can be set
     (thus overriding the default computation in *note get_method():
     1102.) either by providing a default value by setting it at the
     class level in a *note Request: f7b. subclass, or by passing a
     value in to the *note Request: f7b. constructor via the 'method'
     argument.

     在 3.3 版被加入.

     在 3.4 版的變更: A default value can now be set in subclasses;
     previously it could only be set via the constructor argument.

 -- 方法: Request.get_method ()

     Return a string indicating the HTTP request method.  If *note
     Request.method: f7c. is not ‘None’, return its value, otherwise
     return ‘'GET'’ if *note Request.data: f7e. is ‘None’, or ‘'POST'’
     if it's not.  This is only meaningful for HTTP requests.

     在 3.3 版的變更: get_method now looks at the value of *note
     Request.method: f7c.

 -- 方法: Request.add_header (key, val)

     Add another header to the request.  Headers are currently ignored
     by all handlers except HTTP handlers, where they are added to the
     list of headers sent to the server.  Note that there cannot be more
     than one header with the same name, and later calls will overwrite
     previous calls in case the 'key' collides.  Currently, this is no
     loss of HTTP functionality, since all headers which have meaning
     when used more than once have a (header-specific) way of gaining
     the same functionality using only one header.  Note that headers
     added using this method are also added to redirected requests.

 -- 方法: Request.add_unredirected_header (key, header)

     Add a header that will not be added to a redirected request.

 -- 方法: Request.has_header (header)

     Return whether the instance has the named header (checks both
     regular and unredirected).

 -- 方法: Request.remove_header (header)

     Remove named header from the request instance (both from regular
     and unredirected headers).

     在 3.4 版被加入.

 -- 方法: Request.get_full_url ()

     Return the URL given in the constructor.

     在 3.4 版的變更.

     Returns *note Request.full_url: f7d.

 -- 方法: Request.set_proxy (host, type)

     Prepare the request by connecting to a proxy server.  The 'host'
     and 'type' will replace those of the instance, and the instance's
     selector will be the original URL given in the constructor.

 -- 方法: Request.get_header (header_name, default=None)

     Return the value of the given header.  If the header is not
     present, return the default value.

 -- 方法: Request.header_items ()

     Return a list of tuples (header_name, header_value) of the Request
     headers.

在 3.4 版的變更: The request methods add_data, has_data, get_data,
get_type, get_host, get_selector, get_origin_req_host and
is_unverifiable that were deprecated since 3.3 have been removed.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2965.html


File: python.info,  Node: OpenerDirector 物件,  Next: BaseHandler 物件,  Prev: Request Objects,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.2 OpenerDirector 物件
............................

*note OpenerDirector: 37c0. instances have the following methods:

 -- 方法: OpenerDirector.add_handler (handler)

     'handler' should be an instance of *note BaseHandler: 37c4.  The
     following methods are searched, and added to the possible chains
     (note that HTTP errors are a special case).  Note that, in the
     following, 'protocol' should be replaced with the actual protocol
     to handle, for example ‘http_response()’ would be the HTTP protocol
     response handler.  Also 'type' should be replaced with the actual
     HTTP code, for example ‘http_error_404()’ would handle HTTP 404
     errors.

        * ‘<protocol>_open()’ -- signal that the handler knows how to
          open 'protocol' URLs.

          更多資訊請見 *note BaseHandler.<protocol>_open(): 37e7.。

        * ‘http_error_<type>()’ -- signal that the handler knows how to
          handle HTTP errors with HTTP error code 'type'.

          更多資訊請見 *note BaseHandler.http_error_<nnn>(): 37e8.。

        * ‘<protocol>_error()’ -- signal that the handler knows how to
          handle errors from (non-‘http’) 'protocol'.

        * ‘<protocol>_request()’ -- signal that the handler knows how to
          pre-process 'protocol' requests.

          更多資訊請見 *note BaseHandler.<protocol>_request(): 37e9.。

        * ‘<protocol>_response()’ -- signal that the handler knows how
          to post-process 'protocol' responses.

          更多資訊請見 *note BaseHandler.<protocol>_response(): 37ea.。

 -- 方法: OpenerDirector.open (url, data=None[, timeout])

     Open the given 'url' (which can be a request object or a string),
     optionally passing the given 'data'.  Arguments, return values and
     exceptions raised are the same as those of *note urlopen(): 275.
     (which simply calls the *note open(): 4c0. method on the currently
     installed global *note OpenerDirector: 37c0.).  The optional
     'timeout' parameter specifies a timeout in seconds for blocking
     operations like the connection attempt (if not specified, the
     global default timeout setting will be used).  The timeout feature
     actually works only for HTTP, HTTPS and FTP connections.

 -- 方法: OpenerDirector.error (proto, *args)

     Handle an error of the given protocol.  This will call the
     registered error handlers for the given protocol with the given
     arguments (which are protocol specific).  The HTTP protocol is a
     special case which uses the HTTP response code to determine the
     specific error handler; refer to the ‘http_error_<type>()’ methods
     of the handler classes.

     Return values and exceptions raised are the same as those of *note
     urlopen(): 275.

OpenerDirector objects open URLs in three stages:

The order in which these methods are called within each stage is
determined by sorting the handler instances.

  1. Every handler with a method named like ‘<protocol>_request()’ has
     that method called to pre-process the request.

  2. Handlers with a method named like ‘<protocol>_open()’ are called to
     handle the request.  This stage ends when a handler either returns
     a non-*note None: 61b. value (ie.  a response), or raises an
     exception (usually *note URLError: 37bf.).  Exceptions are allowed
     to propagate.

     In fact, the above algorithm is first tried for methods named *note
     default_open(): 37ec.  If all such methods return *note None: 61b,
     the algorithm is repeated for methods named like
     ‘<protocol>_open()’.  If all such methods return *note None: 61b,
     the algorithm is repeated for methods named *note unknown_open():
     37ed.

     Note that the implementation of these methods may involve calls of
     the parent *note OpenerDirector: 37c0. instance's *note open():
     f7f. and *note error(): 37eb. methods.

  3. Every handler with a method named like ‘<protocol>_response()’ has
     that method called to post-process the response.


File: python.info,  Node: BaseHandler 物件,  Next: HTTPRedirectHandler 物件,  Prev: OpenerDirector 物件,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.3 BaseHandler 物件
.........................

*note BaseHandler: 37c4. objects provide a couple of methods that are
directly useful, and others that are meant to be used by derived
classes.  These are intended for direct use:

 -- 方法: BaseHandler.add_parent (director)

     Add a director as parent.

 -- 方法: BaseHandler.close ()

     Remove any parents.

The following attribute and methods should only be used by classes
derived from *note BaseHandler: 37c4.

     備註: The convention has been adopted that subclasses defining
     ‘<protocol>_request()’ or ‘<protocol>_response()’ methods are named
     ‘*Processor’; all others are named ‘*Handler’.

 -- 屬性: BaseHandler.parent

     A valid *note OpenerDirector: 37c0, which can be used to open using
     a different protocol, or handle errors.

 -- 方法: BaseHandler.default_open (req)

     This method is 'not' defined in *note BaseHandler: 37c4, but
     subclasses should define it if they want to catch all URLs.

     This method, if implemented, will be called by the parent *note
     OpenerDirector: 37c0.  It should return a file-like object as
     described in the return value of the *note open(): f7f. method of
     *note OpenerDirector: 37c0, or ‘None’.  It should raise *note
     URLError: 37bf, unless a truly exceptional thing happens (for
     example, *note MemoryError: 15bc. should not be mapped to *note
     URLError: 37bf.).

     This method will be called before any protocol-specific open
     method.

 -- 方法: BaseHandler.<protocol>_open(req)

     This method is 'not' defined in *note BaseHandler: 37c4, but
     subclasses should define it if they want to handle URLs with the
     given protocol.

     This method, if defined, will be called by the parent *note
     OpenerDirector: 37c0.  Return values should be the same as for
     *note default_open(): 37ec.

 -- 方法: BaseHandler.unknown_open (req)

     This method is 'not' defined in *note BaseHandler: 37c4, but
     subclasses should define it if they want to catch all URLs with no
     specific registered handler to open it.

     This method, if implemented, will be called by the *note parent:
     37f2. *note OpenerDirector: 37c0.  Return values should be the same
     as for *note default_open(): 37ec.

 -- 方法: BaseHandler.http_error_default (req, fp, code, msg, hdrs)

     This method is 'not' defined in *note BaseHandler: 37c4, but
     subclasses should override it if they intend to provide a catch-all
     for otherwise unhandled HTTP errors.  It will be called
     automatically by the *note OpenerDirector: 37c0. getting the error,
     and should not normally be called in other circumstances.

     'req' will be a *note Request: f7b. object, 'fp' will be a
     file-like object with the HTTP error body, 'code' will be the
     three-digit code of the error, 'msg' will be the user-visible
     explanation of the code and 'hdrs' will be a mapping object with
     the headers of the error.

     Return values and exceptions raised should be the same as those of
     *note urlopen(): 275.

 -- 方法: BaseHandler.http_error_<nnn>(req, fp, code, msg, hdrs)

     'nnn' should be a three-digit HTTP error code.  This method is also
     not defined in *note BaseHandler: 37c4, but will be called, if it
     exists, on an instance of a subclass, when an HTTP error with code
     'nnn' occurs.

     Subclasses should override this method to handle specific HTTP
     errors.

     Arguments, return values and exceptions raised should be the same
     as for *note http_error_default(): 37f3.

 -- 方法: BaseHandler.<protocol>_request(req)

     This method is 'not' defined in *note BaseHandler: 37c4, but
     subclasses should define it if they want to pre-process requests of
     the given protocol.

     This method, if defined, will be called by the parent *note
     OpenerDirector: 37c0.  'req' will be a *note Request: f7b. object.
     The return value should be a *note Request: f7b. object.

 -- 方法: BaseHandler.<protocol>_response(req, response)

     This method is 'not' defined in *note BaseHandler: 37c4, but
     subclasses should define it if they want to post-process responses
     of the given protocol.

     This method, if defined, will be called by the parent *note
     OpenerDirector: 37c0.  'req' will be a *note Request: f7b. object.
     'response' will be an object implementing the same interface as the
     return value of *note urlopen(): 275.  The return value should
     implement the same interface as the return value of *note
     urlopen(): 275.


File: python.info,  Node: HTTPRedirectHandler 物件,  Next: HTTPCookieProcessor 物件,  Prev: BaseHandler 物件,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.4 HTTPRedirectHandler 物件
.................................

     備註: Some HTTP redirections require action from this module's
     client code.  If this is the case, *note HTTPError: f81. is raised.
     See RFC 2616(1) for details of the precise meanings of the various
     redirection codes.

     An *note HTTPError: f81. exception raised as a security
     consideration if the HTTPRedirectHandler is presented with a
     redirected URL which is not an HTTP, HTTPS or FTP URL.

 -- 方法: HTTPRedirectHandler.redirect_request (req, fp, code, msg,
          hdrs, newurl)

     Return a *note Request: f7b. or ‘None’ in response to a redirect.
     This is called by the default implementations of the
     ‘http_error_30*()’ methods when a redirection is received from the
     server.  If a redirection should take place, return a new *note
     Request: f7b. to allow ‘http_error_30*()’ to perform the redirect
     to 'newurl'.  Otherwise, raise *note HTTPError: f81. if no other
     handler should try to handle this URL, or return ‘None’ if you
     can't but another handler might.

          備註: The default implementation of this method does not
          strictly follow RFC 2616(2), which says that 301 and 302
          responses to ‘POST’ requests must not be automatically
          redirected without confirmation by the user.  In reality,
          browsers do allow automatic redirection of these responses,
          changing the POST to a ‘GET’, and the default implementation
          reproduces this behavior.

 -- 方法: HTTPRedirectHandler.http_error_301 (req, fp, code, msg, hdrs)

     Redirect to the ‘Location:’ or ‘URI:’ URL. This method is called by
     the parent *note OpenerDirector: 37c0. when getting an HTTP 'moved
     permanently' response.

 -- 方法: HTTPRedirectHandler.http_error_302 (req, fp, code, msg, hdrs)

     The same as *note http_error_301(): 37f7, but called for the
     'found' response.

 -- 方法: HTTPRedirectHandler.http_error_303 (req, fp, code, msg, hdrs)

     The same as *note http_error_301(): 37f7, but called for the 'see
     other' response.

 -- 方法: HTTPRedirectHandler.http_error_307 (req, fp, code, msg, hdrs)

     The same as *note http_error_301(): 37f7, but called for the
     'temporary redirect' response.  It does not allow changing the
     request method from ‘POST’ to ‘GET’.

 -- 方法: HTTPRedirectHandler.http_error_308 (req, fp, code, msg, hdrs)

     The same as *note http_error_301(): 37f7, but called for the
     'permanent redirect' response.  It does not allow changing the
     request method from ‘POST’ to ‘GET’.

     在 3.11 版被加入.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2616.html

   (2) https://datatracker.ietf.org/doc/html/rfc2616.html


File: python.info,  Node: HTTPCookieProcessor 物件,  Next: ProxyHandler 物件,  Prev: HTTPRedirectHandler 物件,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.5 HTTPCookieProcessor 物件
.................................

*note HTTPCookieProcessor: 37ce. instances have one attribute:

 -- 屬性: HTTPCookieProcessor.cookiejar

     The *note http.cookiejar.CookieJar: 37ff. in which cookies are
     stored.


File: python.info,  Node: ProxyHandler 物件,  Next: HTTPPasswordMgr 物件,  Prev: HTTPCookieProcessor 物件,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.6 ProxyHandler 物件
..........................

 -- 方法: ProxyHandler.<protocol>_open(request)

     The *note ProxyHandler: 18d5. will have a method
     ‘<protocol>_open()’ for every 'protocol' which has a proxy in the
     'proxies' dictionary given in the constructor.  The method will
     modify requests to go through the proxy, by calling
     ‘request.set_proxy()’, and call the next handler in the chain to
     actually execute the protocol.


File: python.info,  Node: HTTPPasswordMgr 物件,  Next: HTTPPasswordMgrWithPriorAuth 物件,  Prev: ProxyHandler 物件,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.7 HTTPPasswordMgr 物件
.............................

These methods are available on *note HTTPPasswordMgr: 37cf. and *note
HTTPPasswordMgrWithDefaultRealm: 37d0. objects.

 -- 方法: HTTPPasswordMgr.add_password (realm, uri, user, passwd)

     'uri' can be either a single URI, or a sequence of URIs.  'realm',
     'user' and 'passwd' must be strings.  This causes ‘(user, passwd)’
     to be used as authentication tokens when authentication for 'realm'
     and a super-URI of any of the given URIs is given.

 -- 方法: HTTPPasswordMgr.find_user_password (realm, authuri)

     Get user/password for given realm and URI, if any.  This method
     will return ‘(None, None)’ if there is no matching user/password.

     For *note HTTPPasswordMgrWithDefaultRealm: 37d0. objects, the realm
     ‘None’ will be searched if the given 'realm' has no matching
     user/password.


File: python.info,  Node: HTTPPasswordMgrWithPriorAuth 物件,  Next: AbstractBasicAuthHandler 物件,  Prev: HTTPPasswordMgr 物件,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.8 HTTPPasswordMgrWithPriorAuth 物件
..........................................

This password manager extends *note HTTPPasswordMgrWithDefaultRealm:
37d0. to support tracking URIs for which authentication credentials
should always be sent.

 -- 方法: HTTPPasswordMgrWithPriorAuth.add_password (realm, uri, user,
          passwd, is_authenticated=False)

     'realm', 'uri', 'user', 'passwd' are as for *note
     HTTPPasswordMgr.add_password(): 3803.  'is_authenticated' sets the
     initial value of the ‘is_authenticated’ flag for the given URI or
     list of URIs.  If 'is_authenticated' is specified as ‘True’,
     'realm' is ignored.

 -- 方法: HTTPPasswordMgrWithPriorAuth.find_user_password (realm,
          authuri)

     Same as for *note HTTPPasswordMgrWithDefaultRealm: 37d0. objects

 -- 方法: HTTPPasswordMgrWithPriorAuth.update_authenticated (self, uri,
          is_authenticated=False)

     Update the ‘is_authenticated’ flag for the given 'uri' or list of
     URIs.

 -- 方法: HTTPPasswordMgrWithPriorAuth.is_authenticated (self, authuri)

     Returns the current state of the ‘is_authenticated’ flag for the
     given URI.


File: python.info,  Node: AbstractBasicAuthHandler 物件,  Next: HTTPBasicAuthHandler 物件,  Prev: HTTPPasswordMgrWithPriorAuth 物件,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.9 AbstractBasicAuthHandler 物件
......................................

 -- 方法: AbstractBasicAuthHandler.http_error_auth_reqed (authreq, host,
          req, headers)

     Handle an authentication request by getting a user/password pair,
     and re-trying the request.  'authreq' should be the name of the
     header where the information about the realm is included in the
     request, 'host' specifies the URL and path to authenticate for,
     'req' should be the (failed) *note Request: f7b. object, and
     'headers' should be the error headers.

     'host' is either an authority (e.g.  ‘"python.org"’) or a URL
     containing an authority component (e.g.  ‘"http://python.org/"’).
     In either case, the authority must not contain a userinfo component
     (so, ‘"python.org"’ and ‘"python.org:80"’ are fine,
     ‘"joe:password@python.org"’ is not).


File: python.info,  Node: HTTPBasicAuthHandler 物件,  Next: ProxyBasicAuthHandler 物件,  Prev: AbstractBasicAuthHandler 物件,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.10 HTTPBasicAuthHandler 物件
...................................

 -- 方法: HTTPBasicAuthHandler.http_error_401 (req, fp, code, msg, hdrs)

     Retry the request with authentication information, if available.


File: python.info,  Node: ProxyBasicAuthHandler 物件,  Next: AbstractDigestAuthHandler 物件,  Prev: HTTPBasicAuthHandler 物件,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.11 ProxyBasicAuthHandler 物件
....................................

 -- 方法: ProxyBasicAuthHandler.http_error_407 (req, fp, code, msg,
          hdrs)

     Retry the request with authentication information, if available.


File: python.info,  Node: AbstractDigestAuthHandler 物件,  Next: HTTPDigestAuthHandler 物件,  Prev: ProxyBasicAuthHandler 物件,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.12 AbstractDigestAuthHandler 物件
........................................

 -- 方法: AbstractDigestAuthHandler.http_error_auth_reqed (authreq,
          host, req, headers)

     'authreq' should be the name of the header where the information
     about the realm is included in the request, 'host' should be the
     host to authenticate to, 'req' should be the (failed) *note
     Request: f7b. object, and 'headers' should be the error headers.


File: python.info,  Node: HTTPDigestAuthHandler 物件,  Next: ProxyDigestAuthHandler 物件,  Prev: AbstractDigestAuthHandler 物件,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.13 HTTPDigestAuthHandler 物件
....................................

 -- 方法: HTTPDigestAuthHandler.http_error_401 (req, fp, code, msg,
          hdrs)

     Retry the request with authentication information, if available.


File: python.info,  Node: ProxyDigestAuthHandler 物件,  Next: HTTPHandler 物件,  Prev: HTTPDigestAuthHandler 物件,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.14 ProxyDigestAuthHandler 物件
.....................................

 -- 方法: ProxyDigestAuthHandler.http_error_407 (req, fp, code, msg,
          hdrs)

     Retry the request with authentication information, if available.


File: python.info,  Node: HTTPHandler 物件,  Next: HTTPSHandler 物件,  Prev: ProxyDigestAuthHandler 物件,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.15 HTTPHandler 物件
..........................

 -- 方法: HTTPHandler.http_open (req)

     Send an HTTP request, which can be either GET or POST, depending on
     ‘req.has_data()’.


File: python.info,  Node: HTTPSHandler 物件,  Next: FileHandler 物件,  Prev: HTTPHandler 物件,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.16 HTTPSHandler 物件
...........................

 -- 方法: HTTPSHandler.https_open (req)

     Send an HTTPS request, which can be either GET or POST, depending
     on ‘req.has_data()’.


File: python.info,  Node: FileHandler 物件,  Next: DataHandler 物件,  Prev: HTTPSHandler 物件,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.17 FileHandler 物件
..........................

 -- 方法: FileHandler.file_open (req)

     Open the file locally, if there is no host name, or the host name
     is ‘'localhost'’.

     在 3.2 版的變更: This method is applicable only for local
     hostnames.  When a remote hostname is given, a *note URLError:
     37bf. is raised.


File: python.info,  Node: DataHandler 物件,  Next: FTPHandler 物件,  Prev: FileHandler 物件,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.18 DataHandler 物件
..........................

 -- 方法: DataHandler.data_open (req)

     Read a data URL. This kind of URL contains the content encoded in
     the URL itself.  The data URL syntax is specified in RFC 2397(1).
     This implementation ignores white spaces in base64 encoded data
     URLs so the URL may be wrapped in whatever source file it comes
     from.  But even though some browsers don't mind about a missing
     padding at the end of a base64 encoded data URL, this
     implementation will raise a *note ValueError: 1e7. in that case.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2397.html


File: python.info,  Node: FTPHandler 物件,  Next: CacheFTPHandler 物件,  Prev: DataHandler 物件,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.19 FTPHandler 物件
.........................

 -- 方法: FTPHandler.ftp_open (req)

     Open the FTP file indicated by 'req'.  The login is always done
     with empty username and password.


File: python.info,  Node: CacheFTPHandler 物件,  Next: UnknownHandler 物件,  Prev: FTPHandler 物件,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.20 CacheFTPHandler 物件
..............................

*note CacheFTPHandler: 1626. objects are *note FTPHandler: 37c8. objects
with the following additional methods:

 -- 方法: CacheFTPHandler.setTimeout (t)

     Set timeout of connections to 't' seconds.

 -- 方法: CacheFTPHandler.setMaxConns (m)

     Set maximum number of cached connections to 'm'.


File: python.info,  Node: UnknownHandler 物件,  Next: HTTPErrorProcessor 物件,  Prev: CacheFTPHandler 物件,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.21 UnknownHandler 物件
.............................

 -- 方法: UnknownHandler.unknown_open ()

     Raise a *note URLError: 37bf. exception.


File: python.info,  Node: HTTPErrorProcessor 物件,  Next: 範例<35>,  Prev: UnknownHandler 物件,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.22 HTTPErrorProcessor 物件
.................................

 -- 方法: HTTPErrorProcessor.http_response (request, response)

     Process HTTP error responses.

     For 200 error codes, the response object is returned immediately.

     For non-200 error codes, this simply passes the job on to the
     ‘http_error_<type>()’ handler methods, via *note
     OpenerDirector.error(): 37eb.  Eventually, *note
     HTTPDefaultErrorHandler: 37c6. will raise an *note HTTPError: f81.
     if no other handler handles the error.

 -- 方法: HTTPErrorProcessor.https_response (request, response)

     Process HTTPS error responses.

     The behavior is same as *note http_response(): 3832.


File: python.info,  Node: 範例<35>,  Next: Legacy interface,  Prev: HTTPErrorProcessor 物件,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.23 範例
..............

In addition to the examples below, more examples are given in *note
如何使用 urllib 套件取得網路資源: 3836.

This example gets the python.org main page and displays the first 300
bytes of it.

     >>> import urllib.request
     >>> with urllib.request.urlopen('http://www.python.org/') as f:
     ...     print(f.read(300))
     ...
     b'<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">\n\n\n<html
     xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">\n\n<head>\n
     <meta http-equiv="content-type" content="text/html; charset=utf-8" />\n
     <title>Python Programming '

Note that urlopen returns a bytes object.  This is because there is no
way for urlopen to automatically determine the encoding of the byte
stream it receives from the HTTP server.  In general, a program will
decode the returned bytes object to string once it determines or guesses
the appropriate encoding.

The following W3C document,
‘https://www.w3.org/International/O-charset’, lists the various ways in
which an (X)HTML or an XML document could have specified its encoding
information.

As the python.org website uses 'utf-8' encoding as specified in its meta
tag, we will use the same for decoding the bytes object.

     >>> with urllib.request.urlopen('http://www.python.org/') as f:
     ...     print(f.read(100).decode('utf-8'))
     ...
     <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtm

It is also possible to achieve the same result without using the *note
context manager: 576. approach.

     >>> import urllib.request
     >>> f = urllib.request.urlopen('http://www.python.org/')
     >>> print(f.read(100).decode('utf-8'))
     <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtm

In the following example, we are sending a data-stream to the stdin of a
CGI and reading the data it returns to us.  Note that this example will
only work when the Python installation supports SSL.

     >>> import urllib.request
     >>> req = urllib.request.Request(url='https://localhost/cgi-bin/test.cgi',
     ...                       data=b'This data is passed to stdin of the CGI')
     >>> with urllib.request.urlopen(req) as f:
     ...     print(f.read().decode('utf-8'))
     ...
     Got Data: "This data is passed to stdin of the CGI"

The code for the sample CGI used in the above example is:

     #!/usr/bin/env python
     import sys
     data = sys.stdin.read()
     print('Content-type: text/plain\n\nGot Data: "%s"' % data)

Here is an example of doing a ‘PUT’ request using *note Request: f7b.:

     import urllib.request
     DATA = b'some data'
     req = urllib.request.Request(url='http://localhost:8080', data=DATA, method='PUT')
     with urllib.request.urlopen(req) as f:
         pass
     print(f.status)
     print(f.reason)

Use of Basic HTTP Authentication:

     import urllib.request
     # Create an OpenerDirector with support for Basic HTTP Authentication...
     auth_handler = urllib.request.HTTPBasicAuthHandler()
     auth_handler.add_password(realm='PDQ Application',
                               uri='https://mahler:8092/site-updates.py',
                               user='klem',
                               passwd='kadidd!ehopper')
     opener = urllib.request.build_opener(auth_handler)
     # ...and install it globally so it can be used with urlopen.
     urllib.request.install_opener(opener)
     urllib.request.urlopen('http://www.example.com/login.html')

*note build_opener(): 37c3. provides many handlers by default, including
a *note ProxyHandler: 18d5.  By default, *note ProxyHandler: 18d5. uses
the environment variables named ‘<scheme>_proxy’, where ‘<scheme>’ is
the URL scheme involved.  For example, the ‘http_proxy’ environment
variable is read to obtain the HTTP proxy's URL.

This example replaces the default *note ProxyHandler: 18d5. with one
that uses programmatically supplied proxy URLs, and adds proxy
authorization support with *note ProxyBasicAuthHandler: 37d4.

     proxy_handler = urllib.request.ProxyHandler({'http': 'http://www.example.com:3128/'})
     proxy_auth_handler = urllib.request.ProxyBasicAuthHandler()
     proxy_auth_handler.add_password('realm', 'host', 'username', 'password')

     opener = urllib.request.build_opener(proxy_handler, proxy_auth_handler)
     # 這次我們直接使用它而不安裝 OpenerDirector:
     opener.open('http://www.example.com/login.html')

Adding HTTP headers:

Use the 'headers' argument to the *note Request: f7b. constructor, or:

     import urllib.request
     req = urllib.request.Request('http://www.example.com/')
     req.add_header('Referer', 'http://www.python.org/')
     # Customize the default User-Agent header value:
     req.add_header('User-Agent', 'urllib-example/0.1 (Contact: . . .)')
     r = urllib.request.urlopen(req)

*note OpenerDirector: 37c0. automatically adds a ‘User-Agent’ header to
every *note Request: f7b.  To change this:

     import urllib.request
     opener = urllib.request.build_opener()
     opener.addheaders = [('User-agent', 'Mozilla/5.0')]
     opener.open('http://www.example.com/')

Also, remember that a few standard headers (‘Content-Length’,
‘Content-Type’ and ‘Host’) are added when the *note Request: f7b. is
passed to *note urlopen(): 275. (or *note OpenerDirector.open(): f7f.).
Here is an example session that uses the ‘GET’ method to retrieve a URL
containing parameters:

     >>> import urllib.request
     >>> import urllib.parse
     >>> params = urllib.parse.urlencode({'spam': 1, 'eggs': 2, 'bacon': 0})
     >>> url = "http://www.musi-cal.com/cgi-bin/query?%s" % params
     >>> with urllib.request.urlopen(url) as f:
     ...     print(f.read().decode('utf-8'))
     ...

The following example uses the ‘POST’ method instead.  Note that params
output from urlencode is encoded to bytes before it is sent to urlopen
as data:

     >>> import urllib.request
     >>> import urllib.parse
     >>> data = urllib.parse.urlencode({'spam': 1, 'eggs': 2, 'bacon': 0})
     >>> data = data.encode('ascii')
     >>> with urllib.request.urlopen("http://requestb.in/xrbl82xr", data) as f:
     ...     print(f.read().decode('utf-8'))
     ...

The following example uses an explicitly specified HTTP proxy,
overriding environment settings:

     >>> import urllib.request
     >>> proxies = {'http': 'http://proxy.example.com:8080/'}
     >>> opener = urllib.request.FancyURLopener(proxies)
     >>> with opener.open("http://www.python.org") as f:
     ...     f.read().decode('utf-8')
     ...

The following example uses no proxies at all, overriding environment
settings:

     >>> import urllib.request
     >>> opener = urllib.request.FancyURLopener({})
     >>> with opener.open("http://www.python.org/") as f:
     ...     f.read().decode('utf-8')
     ...


File: python.info,  Node: Legacy interface,  Next: urllib request Restrictions,  Prev: 範例<35>,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.24 Legacy interface
..........................

The following functions and classes are ported from the Python 2 module
‘urllib’ (as opposed to ‘urllib2’).  They might become deprecated at
some point in the future.

 -- 函式: urllib.request.urlretrieve (url, filename=None,
          reporthook=None, data=None)

     Copy a network object denoted by a URL to a local file.  If the URL
     points to a local file, the object will not be copied unless
     filename is supplied.  Return a tuple ‘(filename, headers)’ where
     'filename' is the local file name under which the object can be
     found, and 'headers' is whatever the ‘info()’ method of the object
     returned by *note urlopen(): 275. returned (for a remote object).
     Exceptions are the same as for *note urlopen(): 275.

     The second argument, if present, specifies the file location to
     copy to (if absent, the location will be a tempfile with a
     generated name).  The third argument, if present, is a callable
     that will be called once on establishment of the network connection
     and once after each block read thereafter.  The callable will be
     passed three arguments; a count of blocks transferred so far, a
     block size in bytes, and the total size of the file.  The third
     argument may be ‘-1’ on older FTP servers which do not return a
     file size in response to a retrieval request.

     The following example illustrates the most common usage scenario:

          >>> import urllib.request
          >>> local_filename, headers = urllib.request.urlretrieve('http://python.org/')
          >>> html = open(local_filename)
          >>> html.close()

     If the 'url' uses the ‘http:’ scheme identifier, the optional
     'data' argument may be given to specify a ‘POST’ request (normally
     the request type is ‘GET’).  The 'data' argument must be a bytes
     object in standard ‘application/x-www-form-urlencoded’ format; see
     the *note urllib.parse.urlencode(): e37. function.

     *note urlretrieve(): 3839. will raise *note ContentTooShortError:
     383a. when it detects that the amount of data available was less
     than the expected amount (which is the size reported by a
     'Content-Length' header).  This can occur, for example, when the
     download is interrupted.

     The 'Content-Length' is treated as a lower bound: if there's more
     data to read, urlretrieve reads more data, but if less data is
     available, it raises the exception.

     You can still retrieve the downloaded data in this case, it is
     stored in the ‘content’ attribute of the exception instance.

     If no 'Content-Length' header was supplied, urlretrieve can not
     check the size of the data it has downloaded, and just returns it.
     In this case you just have to assume that the download was
     successful.

 -- 函式: urllib.request.urlcleanup ()

     Cleans up temporary files that may have been left behind by
     previous calls to *note urlretrieve(): 3839.

 -- 類別: urllib.request.URLopener (proxies=None, **x509)

     在 3.3 版之後被棄用.

     Base class for opening and reading URLs.  Unless you need to
     support opening objects using schemes other than ‘http:’, ‘ftp:’,
     or ‘file:’, you probably want to use *note FancyURLopener: 2e1.

     By default, the *note URLopener: 2e0. class sends a ‘User-Agent’
     header of ‘urllib/VVV’, where 'VVV' is the *note urllib: f1.
     version number.  Applications can define their own ‘User-Agent’
     header by subclassing *note URLopener: 2e0. or *note
     FancyURLopener: 2e1. and setting the class attribute *note version:
     383b. to an appropriate string value in the subclass definition.

     The optional 'proxies' parameter should be a dictionary mapping
     scheme names to proxy URLs, where an empty dictionary turns proxies
     off completely.  Its default value is ‘None’, in which case
     environmental proxy settings will be used if present, as discussed
     in the definition of *note urlopen(): 275, above.

     Additional keyword parameters, collected in 'x509', may be used for
     authentication of the client when using the ‘https:’ scheme.  The
     keywords 'key_file' and 'cert_file' are supported to provide an SSL
     key and certificate; both are needed to support client
     authentication.

     *note URLopener: 2e0. objects will raise an *note OSError: 350.
     exception if the server returns an error code.

      -- 方法: open (fullurl, data=None)

          Open 'fullurl' using the appropriate protocol.  This method
          sets up cache and proxy information, then calls the
          appropriate open method with its input arguments.  If the
          scheme is not recognized, *note open_unknown(): 383d. is
          called.  The 'data' argument has the same meaning as the
          'data' argument of *note urlopen(): 275.

          This method always quotes 'fullurl' using *note quote(): b4a.

      -- 方法: open_unknown (fullurl, data=None)

          Overridable interface to open unknown URL types.

      -- 方法: retrieve (url, filename=None, reporthook=None, data=None)

          Retrieves the contents of 'url' and places it in 'filename'.
          The return value is a tuple consisting of a local filename and
          either an *note email.message.Message: 261. object containing
          the response headers (for remote URLs) or ‘None’ (for local
          URLs).  The caller must then open and read the contents of
          'filename'.  If 'filename' is not given and the URL refers to
          a local file, the input filename is returned.  If the URL is
          non-local and 'filename' is not given, the filename is the
          output of *note tempfile.mktemp(): 1790. with a suffix that
          matches the suffix of the last path component of the input
          URL.  If 'reporthook' is given, it must be a function
          accepting three numeric parameters: A chunk number, the
          maximum size chunks are read in and the total size of the
          download (-1 if unknown).  It will be called once at the start
          and after each chunk of data is read from the network.
          'reporthook' is ignored for local URLs.

          If the 'url' uses the ‘http:’ scheme identifier, the optional
          'data' argument may be given to specify a ‘POST’ request
          (normally the request type is ‘GET’).  The 'data' argument
          must in standard ‘application/x-www-form-urlencoded’ format;
          see the *note urllib.parse.urlencode(): e37. function.

      -- 屬性: version

          Variable that specifies the user agent of the opener object.
          To get *note urllib: f1. to tell servers that it is a
          particular user agent, set this in a subclass as a class
          variable or in the constructor before calling the base
          constructor.

 -- 類別: urllib.request.FancyURLopener (...)

     在 3.3 版之後被棄用.

     *note FancyURLopener: 2e1. subclasses *note URLopener: 2e0.
     providing default handling for the following HTTP response codes:
     301, 302, 303, 307 and 401.  For the 30x response codes listed
     above, the ‘Location’ header is used to fetch the actual URL. For
     401 response codes (authentication required), basic HTTP
     authentication is performed.  For the 30x response codes, recursion
     is bounded by the value of the 'maxtries' attribute, which defaults
     to 10.

     For all other response codes, the method *note
     http_error_default(): 37f3. is called which you can override in
     subclasses to handle the error appropriately.

          備註: According to the letter of RFC 2616(1), 301 and 302
          responses to POST requests must not be automatically
          redirected without confirmation by the user.  In reality,
          browsers do allow automatic redirection of these responses,
          changing the POST to a GET, and *note urllib: f1. reproduces
          this behaviour.

     The parameters to the constructor are the same as those for *note
     URLopener: 2e0.

          備註: When performing basic authentication, a *note
          FancyURLopener: 2e1. instance calls its *note
          prompt_user_passwd(): 383e. method.  The default
          implementation asks the users for the required information on
          the controlling terminal.  A subclass may override this method
          to support more appropriate behavior if needed.

     The *note FancyURLopener: 2e1. class offers one additional method
     that should be overloaded to provide the appropriate behavior:

      -- 方法: prompt_user_passwd (host, realm)

          Return information needed to authenticate the user at the
          given host in the specified security realm.  The return value
          should be a tuple, ‘(user, password)’, which can be used for
          basic authentication.

          The implementation prompts for this information on the
          terminal; an application should override this method to use an
          appropriate interaction model in the local environment.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2616.html


File: python.info,  Node: urllib request Restrictions,  Prev: Legacy interface,  Up: urllib request --- 用來開啟 URLs 的可擴充函式庫

5.21.4.25 ‘urllib.request’ Restrictions
.......................................

   * Currently, only the following protocols are supported: HTTP
     (versions 0.9 and 1.0), FTP, local files, and data URLs.

     在 3.4 版的變更: Added support for data URLs.

   * The caching feature of *note urlretrieve(): 3839. has been disabled
     until someone finds the time to hack proper processing of
     Expiration time headers.

   * There should be a function to query whether a particular URL is in
     the cache.

   * For backward compatibility, if a URL appears to point to a local
     file but the file can't be opened, the URL is re-interpreted using
     the FTP protocol.  This can sometimes cause confusing error
     messages.

   * The *note urlopen(): 275. and *note urlretrieve(): 3839. functions
     can cause arbitrarily long delays while waiting for a network
     connection to be set up.  This means that it is difficult to build
     an interactive web client using these functions without using
     threads.

   * The data returned by *note urlopen(): 275. or *note urlretrieve():
     3839. is the raw data returned by the server.  This may be binary
     data (such as an image), plain text or (for example) HTML. The HTTP
     protocol provides type information in the reply header, which can
     be inspected by looking at the ‘Content-Type’ header.  If the
     returned data is HTML, you can use the module *note html.parser:
     63. to parse it.

   * The code handling the FTP protocol cannot differentiate between a
     file and a directory.  This can lead to unexpected behavior when
     attempting to read a URL that points to a file that is not
     accessible.  If the URL ends in a ‘/’, it is assumed to refer to a
     directory and will be handled accordingly.  But if an attempt to
     read a file leads to a 550 error (meaning the URL cannot be found
     or is not accessible, often for permission reasons), then the path
     is treated as a directory in order to handle the case when a
     directory is specified by a URL but the trailing ‘/’ has been left
     off.  This can cause misleading results when you try to fetch a
     file whose read permissions make it inaccessible; the FTP code will
     try to read it, fail with a 550 error, and then perform a directory
     listing for the unreadable file.  If fine-grained control is
     needed, consider using the *note ftplib: 54. module, subclassing
     *note FancyURLopener: 2e1, or changing '_urlopener' to meet your
     needs.


File: python.info,  Node: urllib response --- Response classes used by urllib,  Next: urllib parse --- 將 URL 剖析成元件,  Prev: urllib request --- 用來開啟 URLs 的可擴充函式庫,  Up: 網路協定 Internet protocols 及支援

5.21.5 ‘urllib.response’ -- Response classes used by urllib
-----------------------------------------------------------

The *note urllib.response: f5. module defines functions and classes
which define a minimal file-like interface, including ‘read()’ and
‘readline()’.  Functions defined by this module are used internally by
the *note urllib.request: f4. module.  The typical response object is a
*note urllib.response.addinfourl: 37bd. instance:

 -- 類別: urllib.response.addinfourl

      -- 屬性: url

          URL of the resource retrieved, commonly used to determine if a
          redirect was followed.

      -- 屬性: headers

          Returns the headers of the response in the form of an *note
          EmailMessage: 260. instance.

      -- 屬性: status

          在 3.9 版被加入.

          Status code returned by server.

      -- 方法: geturl ()

          在 3.9 版之後被棄用: Deprecated in favor of *note url: 3841.

      -- 方法: info ()

          在 3.9 版之後被棄用: Deprecated in favor of *note headers:
          3842.

      -- 屬性: code

          在 3.9 版之後被棄用: Deprecated in favor of *note status:
          3843.

      -- 方法: getcode ()

          在 3.9 版之後被棄用: Deprecated in favor of *note status:
          3843.


File: python.info,  Node: urllib parse --- 將 URL 剖析成元件,  Next: urllib error --- urllib request 引發的例外類別,  Prev: urllib response --- Response classes used by urllib,  Up: 網路協定 Internet protocols 及支援

5.21.6 ‘urllib.parse’ -- 將 URL 剖析成元件
------------------------------------------

'原始碼：'Lib/urllib/parse.py(1)

__________________________________________________________________

This module defines a standard interface to break Uniform Resource
Locator (URL) strings up in components (addressing scheme, network
location, path etc.), to combine the components back into a URL string,
and to convert a "relative URL" to an absolute URL given a "base URL."

The module has been designed to match the internet RFC on Relative
Uniform Resource Locators.  It supports the following URL schemes:
‘file’, ‘ftp’, ‘gopher’, ‘hdl’, ‘http’, ‘https’, ‘imap’,
‘itms-services’, ‘mailto’, ‘mms’, ‘news’, ‘nntp’, ‘prospero’, ‘rsync’,
‘rtsp’, ‘rtsps’, ‘rtspu’, ‘sftp’, ‘shttp’, ‘sip’, ‘sips’, ‘snews’,
‘svn’, ‘svn+ssh’, ‘telnet’, ‘wais’, ‘ws’, ‘wss’.

'CPython 實作細節：' The inclusion of the ‘itms-services’ URL scheme can
prevent an app from passing Apple's App Store review process for the
macOS and iOS App Stores.  Handling for the ‘itms-services’ scheme is
always removed on iOS; on macOS, it 'may' be removed if CPython has been
built with the *note -with-app-store-compliance: 14e6. option.

The *note urllib.parse: f3. module defines functions that fall into two
broad categories: URL parsing and URL quoting.  These are covered in
detail in the following sections.

This module's functions use the deprecated term ‘netloc’ (or ‘net_loc’),
which was introduced in RFC 1808(2).  However, this term has been
obsoleted by RFC 3986(3), which introduced the term ‘authority’ as its
replacement.  The use of ‘netloc’ is continued for backward
compatibility.

* Menu:

* URL Parsing::
* URL parsing security::
* Parsing ASCII Encoded Bytes::
* Structured Parse Results::
* URL Quoting::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/urllib/parse.py

   (2) https://datatracker.ietf.org/doc/html/rfc1808.html

   (3) https://datatracker.ietf.org/doc/html/rfc3986.html


File: python.info,  Node: URL Parsing,  Next: URL parsing security,  Up: urllib parse --- 將 URL 剖析成元件

5.21.6.1 URL Parsing
....................

The URL parsing functions focus on splitting a URL string into its
components, or on combining URL components into a URL string.

 -- 函式: urllib.parse.urlparse (urlstring, scheme='',
          allow_fragments=True)

     Parse a URL into six components, returning a 6-item *note named
     tuple: 5f4.  This corresponds to the general structure of a URL:
     ‘scheme://netloc/path;parameters?query#fragment’.  Each tuple item
     is a string, possibly empty.  The components are not broken up into
     smaller parts (for example, the network location is a single
     string), and % escapes are not expanded.  The delimiters as shown
     above are not part of the result, except for a leading slash in the
     'path' component, which is retained if present.  For example:

          >>> from urllib.parse import urlparse
          >>> urlparse("scheme://netloc/path;parameters?query#fragment")
          ParseResult(scheme='scheme', netloc='netloc', path='/path;parameters', params='',
                      query='query', fragment='fragment')
          >>> o = urlparse("http://docs.python.org:80/3/library/urllib.parse.html?"
          ...              "highlight=params#url-parsing")
          >>> o
          ParseResult(scheme='http', netloc='docs.python.org:80',
                      path='/3/library/urllib.parse.html', params='',
                      query='highlight=params', fragment='url-parsing')
          >>> o.scheme
          'http'
          >>> o.netloc
          'docs.python.org:80'
          >>> o.hostname
          'docs.python.org'
          >>> o.port
          80
          >>> o._replace(fragment="").geturl()
          'http://docs.python.org:80/3/library/urllib.parse.html?highlight=params'

     Following the syntax specifications in RFC 1808(1), urlparse
     recognizes a netloc only if it is properly introduced by '//'.
     Otherwise the input is presumed to be a relative URL and thus to
     start with a path component.

          >>> from urllib.parse import urlparse
          >>> urlparse('//www.cwi.nl:80/%7Eguido/Python.html')
          ParseResult(scheme='', netloc='www.cwi.nl:80', path='/%7Eguido/Python.html',
                      params='', query='', fragment='')
          >>> urlparse('www.cwi.nl/%7Eguido/Python.html')
          ParseResult(scheme='', netloc='', path='www.cwi.nl/%7Eguido/Python.html',
                      params='', query='', fragment='')
          >>> urlparse('help/Python.html')
          ParseResult(scheme='', netloc='', path='help/Python.html', params='',
                      query='', fragment='')

     The 'scheme' argument gives the default addressing scheme, to be
     used only if the URL does not specify one.  It should be the same
     type (text or bytes) as 'urlstring', except that the default value
     ‘''’ is always allowed, and is automatically converted to ‘b''’ if
     appropriate.

     If the 'allow_fragments' argument is false, fragment identifiers
     are not recognized.  Instead, they are parsed as part of the path,
     parameters or query component, and ‘fragment’ is set to the empty
     string in the return value.

     The return value is a *note named tuple: 5f4, which means that its
     items can be accessed by index or as named attributes, which are:

     屬性                   Index       Value                         Value if not present
                                                                      
     ----------------------------------------------------------------------------------------------
                                                                      
     ‘scheme’               0           URL scheme specifier          'scheme' parameter
                                                                      
                                                                      
     ‘netloc’               1           Network location part         empty string
                                                                      
                                                                      
     ‘path’                 2           Hierarchical path             empty string
                                                                      
                                                                      
     ‘params’               3           Parameters for last path      empty string
                                        element                       
                                        
                                                                      
     ‘query’                4           Query component               empty string
                                                                      
                                                                      
     ‘fragment’             5           Fragment identifier           empty string
                                                                      
                                                                      
     ‘username’                         User name                     *note None: 61b.
                                                                      
                                                                      
     ‘password’                         Password                      *note None: 61b.
                                                                      
                                                                      
     ‘hostname’                         Host name (lower case)        *note None: 61b.
                                                                      
                                                                      
     ‘port’                             Port number as integer, if    *note None: 61b.
                                        present                       
                                        

     Reading the ‘port’ attribute will raise a *note ValueError: 1e7. if
     an invalid port is specified in the URL. See section *note
     Structured Parse Results: 384b. for more information on the result
     object.

     Unmatched square brackets in the ‘netloc’ attribute will raise a
     *note ValueError: 1e7.

     Characters in the ‘netloc’ attribute that decompose under NFKC
     normalization (as used by the IDNA encoding) into any of ‘/’, ‘?’,
     ‘#’, ‘@’, or ‘:’ will raise a *note ValueError: 1e7.  If the URL is
     decomposed before parsing, no error will be raised.

     As is the case with all named tuples, the subclass has a few
     additional methods and attributes that are particularly useful.
     One such method is ‘_replace()’.  The ‘_replace()’ method will
     return a new ParseResult object replacing specified fields with new
     values.

          >>> from urllib.parse import urlparse
          >>> u = urlparse('//www.cwi.nl:80/%7Eguido/Python.html')
          >>> u
          ParseResult(scheme='', netloc='www.cwi.nl:80', path='/%7Eguido/Python.html',
                      params='', query='', fragment='')
          >>> u._replace(scheme='http')
          ParseResult(scheme='http', netloc='www.cwi.nl:80', path='/%7Eguido/Python.html',
                      params='', query='', fragment='')

          警告: *note urlparse(): 2df. does not perform validation.  See
          *note URL parsing security: 384c. for details.

     在 3.2 版的變更: 新增剖析 IPv6 URL 的能力。

     在 3.3 版的變更: The fragment is now parsed for all URL schemes
     (unless 'allow_fragments' is false), in accordance with RFC
     3986(2).  Previously, an allowlist of schemes that support
     fragments existed.

     在 3.6 版的變更: Out-of-range port numbers now raise *note
     ValueError: 1e7, instead of returning *note None: 61b.

     在 3.8 版的變更: Characters that affect netloc parsing under NFKC
     normalization will now raise *note ValueError: 1e7.

 -- 函式: urllib.parse.parse_qs (qs, keep_blank_values=False,
          strict_parsing=False, encoding='utf-8', errors='replace',
          max_num_fields=None, separator='&')

     Parse a query string given as a string argument (data of type
     ‘application/x-www-form-urlencoded’).  Data are returned as a
     dictionary.  The dictionary keys are the unique query variable
     names and the values are lists of values for each name.

     The optional argument 'keep_blank_values' is a flag indicating
     whether blank values in percent-encoded queries should be treated
     as blank strings.  A true value indicates that blanks should be
     retained as blank strings.  The default false value indicates that
     blank values are to be ignored and treated as if they were not
     included.

     The optional argument 'strict_parsing' is a flag indicating what to
     do with parsing errors.  If false (the default), errors are
     silently ignored.  If true, errors raise a *note ValueError: 1e7.
     exception.

     The optional 'encoding' and 'errors' parameters specify how to
     decode percent-encoded sequences into Unicode characters, as
     accepted by the *note bytes.decode(): 87b. method.

     The optional argument 'max_num_fields' is the maximum number of
     fields to read.  If set, then throws a *note ValueError: 1e7. if
     there are more than 'max_num_fields' fields read.

     The optional argument 'separator' is the symbol to use for
     separating the query arguments.  It defaults to ‘&’.

     Use the *note urllib.parse.urlencode(): e37. function (with the
     ‘doseq’ parameter set to ‘True’) to convert such dictionaries into
     query strings.

     在 3.2 版的變更: Add 'encoding' and 'errors' parameters.

     在 3.8 版的變更: 新增 'max_num_fields' 參數。

     在 3.10 版的變更: Added 'separator' parameter with the default
     value of ‘&’.  Python versions earlier than Python 3.10 allowed
     using both ‘;’ and ‘&’ as query parameter separator.  This has been
     changed to allow only a single separator key, with ‘&’ as the
     default separator.

 -- 函式: urllib.parse.parse_qsl (qs, keep_blank_values=False,
          strict_parsing=False, encoding='utf-8', errors='replace',
          max_num_fields=None, separator='&')

     Parse a query string given as a string argument (data of type
     ‘application/x-www-form-urlencoded’).  Data are returned as a list
     of name, value pairs.

     The optional argument 'keep_blank_values' is a flag indicating
     whether blank values in percent-encoded queries should be treated
     as blank strings.  A true value indicates that blanks should be
     retained as blank strings.  The default false value indicates that
     blank values are to be ignored and treated as if they were not
     included.

     The optional argument 'strict_parsing' is a flag indicating what to
     do with parsing errors.  If false (the default), errors are
     silently ignored.  If true, errors raise a *note ValueError: 1e7.
     exception.

     The optional 'encoding' and 'errors' parameters specify how to
     decode percent-encoded sequences into Unicode characters, as
     accepted by the *note bytes.decode(): 87b. method.

     The optional argument 'max_num_fields' is the maximum number of
     fields to read.  If set, then throws a *note ValueError: 1e7. if
     there are more than 'max_num_fields' fields read.

     The optional argument 'separator' is the symbol to use for
     separating the query arguments.  It defaults to ‘&’.

     Use the *note urllib.parse.urlencode(): e37. function to convert
     such lists of pairs into query strings.

     在 3.2 版的變更: Add 'encoding' and 'errors' parameters.

     在 3.8 版的變更: 新增 'max_num_fields' 參數。

     在 3.10 版的變更: Added 'separator' parameter with the default
     value of ‘&’.  Python versions earlier than Python 3.10 allowed
     using both ‘;’ and ‘&’ as query parameter separator.  This has been
     changed to allow only a single separator key, with ‘&’ as the
     default separator.

 -- 函式: urllib.parse.urlunparse (parts)

     Construct a URL from a tuple as returned by ‘urlparse()’.  The
     'parts' argument can be any six-item iterable.  This may result in
     a slightly different, but equivalent URL, if the URL that was
     parsed originally had unnecessary delimiters (for example, a ‘?’
     with an empty query; the RFC states that these are equivalent).

 -- 函式: urllib.parse.urlsplit (urlstring, scheme='',
          allow_fragments=True)

     This is similar to *note urlparse(): 2df, but does not split the
     params from the URL. This should generally be used instead of *note
     urlparse(): 2df. if the more recent URL syntax allowing parameters
     to be applied to each segment of the 'path' portion of the URL (see
     RFC 2396(3)) is wanted.  A separate function is needed to separate
     the path segments and parameters.  This function returns a 5-item
     *note named tuple: 5f4.:

          (addressing scheme, network location, path, query, fragment identifier).

     The return value is a *note named tuple: 5f4, its items can be
     accessed by index or as named attributes:

     屬性                   Index       Value                         Value if not present
                                                                      
     --------------------------------------------------------------------------------------------
                                                                      
     ‘scheme’               0           URL scheme specifier          'scheme' parameter
                                                                      
                                                                      
     ‘netloc’               1           Network location part         empty string
                                                                      
                                                                      
     ‘path’                 2           Hierarchical path             empty string
                                                                      
                                                                      
     ‘query’                3           Query component               empty string
                                                                      
                                                                      
     ‘fragment’             4           Fragment identifier           empty string
                                                                      
                                                                      
     ‘username’                         User name                     *note None: 61b.
                                                                      
                                                                      
     ‘password’                         Password                      *note None: 61b.
                                                                      
                                                                      
     ‘hostname’                         Host name (lower case)        *note None: 61b.
                                                                      
                                                                      
     ‘port’                             Port number as integer, if    *note None: 61b.
                                        present                       
                                        

     Reading the ‘port’ attribute will raise a *note ValueError: 1e7. if
     an invalid port is specified in the URL. See section *note
     Structured Parse Results: 384b. for more information on the result
     object.

     Unmatched square brackets in the ‘netloc’ attribute will raise a
     *note ValueError: 1e7.

     Characters in the ‘netloc’ attribute that decompose under NFKC
     normalization (as used by the IDNA encoding) into any of ‘/’, ‘?’,
     ‘#’, ‘@’, or ‘:’ will raise a *note ValueError: 1e7.  If the URL is
     decomposed before parsing, no error will be raised.

     Following some of the WHATWG spec(4) that updates RFC 3986, leading
     C0 control and space characters are stripped from the URL. ‘\n’,
     ‘\r’ and tab ‘\t’ characters are removed from the URL at any
     position.

          警告: *note urlsplit(): ce6. does not perform validation.  See
          *note URL parsing security: 384c. for details.

     在 3.6 版的變更: Out-of-range port numbers now raise *note
     ValueError: 1e7, instead of returning *note None: 61b.

     在 3.8 版的變更: Characters that affect netloc parsing under NFKC
     normalization will now raise *note ValueError: 1e7.

     在 3.10 版的變更: ASCII newline and tab characters are stripped
     from the URL.

     在 3.12 版的變更: Leading WHATWG C0 control and space characters
     are stripped from the URL.

 -- 函式: urllib.parse.urlunsplit (parts)

     Combine the elements of a tuple as returned by *note urlsplit():
     ce6. into a complete URL as a string.  The 'parts' argument can be
     any five-item iterable.  This may result in a slightly different,
     but equivalent URL, if the URL that was parsed originally had
     unnecessary delimiters (for example, a ?  with an empty query; the
     RFC states that these are equivalent).

 -- 函式: urllib.parse.urljoin (base, url, allow_fragments=True)

     Construct a full ("absolute") URL by combining a "base URL"
     ('base') with another URL ('url').  Informally, this uses
     components of the base URL, in particular the addressing scheme,
     the network location and (part of) the path, to provide missing
     components in the relative URL. For example:

          >>> from urllib.parse import urljoin
          >>> urljoin('http://www.cwi.nl/%7Eguido/Python.html', 'FAQ.html')
          'http://www.cwi.nl/%7Eguido/FAQ.html'

     The 'allow_fragments' argument has the same meaning and default as
     for *note urlparse(): 2df.

          備註: If 'url' is an absolute URL (that is, it starts with
          ‘//’ or ‘scheme://’), the 'url"s hostname and/or scheme will
          be present in the result.  For example:

               >>> urljoin('http://www.cwi.nl/%7Eguido/Python.html',
               ...         '//www.python.org/%7Eguido')
               'http://www.python.org/%7Eguido'

          If you do not want that behavior, preprocess the 'url' with
          *note urlsplit(): ce6. and *note urlunsplit(): 14c8, removing
          possible 'scheme' and 'netloc' parts.

     在 3.5 版的變更: Behavior updated to match the semantics defined in
     RFC 3986(5).

 -- 函式: urllib.parse.urldefrag (url)

     If 'url' contains a fragment identifier, return a modified version
     of 'url' with no fragment identifier, and the fragment identifier
     as a separate string.  If there is no fragment identifier in 'url',
     return 'url' unmodified and an empty string.

     The return value is a *note named tuple: 5f4, its items can be
     accessed by index or as named attributes:

     屬性                   Index       Value                         Value if not present
                                                                      
     --------------------------------------------------------------------------------------------
                                                                      
     ‘url’                  0           URL with no fragment          empty string
                                                                      
                                                                      
     ‘fragment’             1           Fragment identifier           empty string
                                                                      

     See section *note Structured Parse Results: 384b. for more
     information on the result object.

     在 3.2 版的變更: Result is a structured object rather than a simple
     2-tuple.

 -- 函式: urllib.parse.unwrap (url)

     Extract the url from a wrapped URL (that is, a string formatted as
     ‘<URL:scheme://host/path>’, ‘<scheme://host/path>’,
     ‘URL:scheme://host/path’ or ‘scheme://host/path’).  If 'url' is not
     a wrapped URL, it is returned without changes.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc1808.html

   (2) https://datatracker.ietf.org/doc/html/rfc3986.html

   (3) https://datatracker.ietf.org/doc/html/rfc2396.html

   (4) https://url.spec.whatwg.org/#concept-basic-url-parser

   (5) https://datatracker.ietf.org/doc/html/rfc3986.html


File: python.info,  Node: URL parsing security,  Next: Parsing ASCII Encoded Bytes,  Prev: URL Parsing,  Up: urllib parse --- 將 URL 剖析成元件

5.21.6.2 URL parsing security
.............................

The *note urlsplit(): ce6. and *note urlparse(): 2df. APIs do not
perform 'validation' of inputs.  They may not raise errors on inputs
that other applications consider invalid.  They may also succeed on some
inputs that might not be considered URLs elsewhere.  Their purpose is
for practical functionality rather than purity.

Instead of raising an exception on unusual input, they may instead
return some component parts as empty strings.  Or components may contain
more than perhaps they should.

We recommend that users of these APIs where the values may be used
anywhere with security implications code defensively.  Do some
verification within your code before trusting a returned component part.
Does that ‘scheme’ make sense?  Is that a sensible ‘path’?  Is there
anything strange about that ‘hostname’?  etc.

What constitutes a URL is not universally well defined.  Different
applications have different needs and desired constraints.  For instance
the living WHATWG spec(1) describes what user facing web clients such as
a web browser require.  While RFC 3986(2) is more general.  These
functions incorporate some aspects of both, but cannot be claimed
compliant with either.  The APIs and existing user code with
expectations on specific behaviors predate both standards leading us to
be very cautious about making API behavior changes.

   ---------- Footnotes ----------

   (1) https://url.spec.whatwg.org/#concept-basic-url-parser

   (2) https://datatracker.ietf.org/doc/html/rfc3986.html


File: python.info,  Node: Parsing ASCII Encoded Bytes,  Next: Structured Parse Results,  Prev: URL parsing security,  Up: urllib parse --- 將 URL 剖析成元件

5.21.6.3 Parsing ASCII Encoded Bytes
....................................

The URL parsing functions were originally designed to operate on
character strings only.  In practice, it is useful to be able to
manipulate properly quoted and encoded URLs as sequences of ASCII bytes.
Accordingly, the URL parsing functions in this module all operate on
*note bytes: 1a5. and *note bytearray: 4e3. objects in addition to *note
str: 3f2. objects.

If *note str: 3f2. data is passed in, the result will also contain only
*note str: 3f2. data.  If *note bytes: 1a5. or *note bytearray: 4e3.
data is passed in, the result will contain only *note bytes: 1a5. data.

Attempting to mix *note str: 3f2. data with *note bytes: 1a5. or *note
bytearray: 4e3. in a single function call will result in a *note
TypeError: 4dd. being raised, while attempting to pass in non-ASCII byte
values will trigger *note UnicodeDecodeError: 9b7.

To support easier conversion of result objects between *note str: 3f2.
and *note bytes: 1a5, all return values from URL parsing functions
provide either an ‘encode()’ method (when the result contains *note str:
3f2. data) or a ‘decode()’ method (when the result contains *note bytes:
1a5. data).  The signatures of these methods match those of the
corresponding *note str: 3f2. and *note bytes: 1a5. methods (except that
the default encoding is ‘'ascii'’ rather than ‘'utf-8'’).  Each produces
a value of a corresponding type that contains either *note bytes: 1a5.
data (for ‘encode()’ methods) or *note str: 3f2. data (for ‘decode()’
methods).

Applications that need to operate on potentially improperly quoted URLs
that may contain non-ASCII data will need to do their own decoding from
bytes to characters before invoking the URL parsing methods.

The behaviour described in this section applies only to the URL parsing
functions.  The URL quoting functions use their own rules when producing
or consuming byte sequences as detailed in the documentation of the
individual URL quoting functions.

在 3.2 版的變更: URL parsing functions now accept ASCII encoded byte
sequences


File: python.info,  Node: Structured Parse Results,  Next: URL Quoting,  Prev: Parsing ASCII Encoded Bytes,  Up: urllib parse --- 將 URL 剖析成元件

5.21.6.4 Structured Parse Results
.................................

The result objects from the *note urlparse(): 2df, *note urlsplit():
ce6. and *note urldefrag(): 11e0. functions are subclasses of the *note
tuple: 322. type.  These subclasses add the attributes listed in the
documentation for those functions, the encoding and decoding support
described in the previous section, as well as an additional method:

 -- 方法: urllib.parse.SplitResult.geturl ()

     Return the re-combined version of the original URL as a string.
     This may differ from the original URL in that the scheme may be
     normalized to lower case and empty components may be dropped.
     Specifically, empty parameters, queries, and fragment identifiers
     will be removed.

     For *note urldefrag(): 11e0. results, only empty fragment
     identifiers will be removed.  For *note urlsplit(): ce6. and *note
     urlparse(): 2df. results, all noted changes will be made to the URL
     returned by this method.

     The result of this method remains unchanged if passed back through
     the original parsing function:

          >>> from urllib.parse import urlsplit
          >>> url = 'HTTP://www.Python.org/doc/#'
          >>> r1 = urlsplit(url)
          >>> r1.geturl()
          'http://www.Python.org/doc/'
          >>> r2 = urlsplit(r1.geturl())
          >>> r2.geturl()
          'http://www.Python.org/doc/'

The following classes provide the implementations of the structured
parse results when operating on *note str: 3f2. objects:

 -- 類別: urllib.parse.DefragResult (url, fragment)

     Concrete class for *note urldefrag(): 11e0. results containing
     *note str: 3f2. data.  The ‘encode()’ method returns a *note
     DefragResultBytes: 3853. instance.

     在 3.2 版被加入.

 -- 類別: urllib.parse.ParseResult (scheme, netloc, path, params, query,
          fragment)

     Concrete class for *note urlparse(): 2df. results containing *note
     str: 3f2. data.  The ‘encode()’ method returns a *note
     ParseResultBytes: 3855. instance.

 -- 類別: urllib.parse.SplitResult (scheme, netloc, path, query,
          fragment)

     Concrete class for *note urlsplit(): ce6. results containing *note
     str: 3f2. data.  The ‘encode()’ method returns a *note
     SplitResultBytes: 3857. instance.

The following classes provide the implementations of the parse results
when operating on *note bytes: 1a5. or *note bytearray: 4e3. objects:

 -- 類別: urllib.parse.DefragResultBytes (url, fragment)

     Concrete class for *note urldefrag(): 11e0. results containing
     *note bytes: 1a5. data.  The ‘decode()’ method returns a *note
     DefragResult: 3852. instance.

     在 3.2 版被加入.

 -- 類別: urllib.parse.ParseResultBytes (scheme, netloc, path, params,
          query, fragment)

     Concrete class for *note urlparse(): 2df. results containing *note
     bytes: 1a5. data.  The ‘decode()’ method returns a *note
     ParseResult: 3854. instance.

     在 3.2 版被加入.

 -- 類別: urllib.parse.SplitResultBytes (scheme, netloc, path, query,
          fragment)

     Concrete class for *note urlsplit(): ce6. results containing *note
     bytes: 1a5. data.  The ‘decode()’ method returns a *note
     SplitResult: 3856. instance.

     在 3.2 版被加入.


File: python.info,  Node: URL Quoting,  Prev: Structured Parse Results,  Up: urllib parse --- 將 URL 剖析成元件

5.21.6.5 URL Quoting
....................

The URL quoting functions focus on taking program data and making it
safe for use as URL components by quoting special characters and
appropriately encoding non-ASCII text.  They also support reversing
these operations to recreate the original data from the contents of a
URL component if that task isn't already covered by the URL parsing
functions above.

 -- 函式: urllib.parse.quote (string, safe='/', encoding=None,
          errors=None)

     Replace special characters in 'string' using the ‘%XX’ escape.
     Letters, digits, and the characters ‘'_.-~'’ are never quoted.  By
     default, this function is intended for quoting the path section of
     a URL. The optional 'safe' parameter specifies additional ASCII
     characters that should not be quoted -- its default value is ‘'/'’.

     'string' may be either a *note str: 3f2. or a *note bytes: 1a5.
     object.

     在 3.7 版的變更: Moved from RFC 2396(1) to RFC 3986(2) for quoting
     URL strings.  "~" is now included in the set of unreserved
     characters.

     The optional 'encoding' and 'errors' parameters specify how to deal
     with non-ASCII characters, as accepted by the *note str.encode():
     87a. method.  'encoding' defaults to ‘'utf-8'’.  'errors' defaults
     to ‘'strict'’, meaning unsupported characters raise a *note
     UnicodeEncodeError: 61d.  'encoding' and 'errors' must not be
     supplied if 'string' is a *note bytes: 1a5, or a *note TypeError:
     4dd. is raised.

     Note that ‘quote(string, safe, encoding, errors)’ is equivalent to
     ‘quote_from_bytes(string.encode(encoding, errors), safe)’.

     Example: ‘quote('/El Niño/')’ yields ‘'/El%20Ni%C3%B1o/'’.

 -- 函式: urllib.parse.quote_plus (string, safe='', encoding=None,
          errors=None)

     Like *note quote(): b4a, but also replace spaces with plus signs,
     as required for quoting HTML form values when building up a query
     string to go into a URL. Plus signs in the original string are
     escaped unless they are included in 'safe'.  It also does not have
     'safe' default to ‘'/'’.

     Example: ‘quote_plus('/El Niño/')’ yields ‘'%2FEl+Ni%C3%B1o%2F'’.

 -- 函式: urllib.parse.quote_from_bytes (bytes, safe='/')

     Like *note quote(): b4a, but accepts a *note bytes: 1a5. object
     rather than a *note str: 3f2, and does not perform string-to-bytes
     encoding.

     Example: ‘quote_from_bytes(b'a&\xef')’ yields ‘'a%26%EF'’.

 -- 函式: urllib.parse.unquote (string, encoding='utf-8',
          errors='replace')

     Replace ‘%XX’ escapes with their single-character equivalent.  The
     optional 'encoding' and 'errors' parameters specify how to decode
     percent-encoded sequences into Unicode characters, as accepted by
     the *note bytes.decode(): 87b. method.

     'string' may be either a *note str: 3f2. or a *note bytes: 1a5.
     object.

     'encoding' defaults to ‘'utf-8'’.  'errors' defaults to
     ‘'replace'’, meaning invalid sequences are replaced by a
     placeholder character.

     Example: ‘unquote('/El%20Ni%C3%B1o/')’ yields ‘'/El Niño/'’.

     在 3.9 版的變更: 'string' parameter supports bytes and str objects
     (previously only str).

 -- 函式: urllib.parse.unquote_plus (string, encoding='utf-8',
          errors='replace')

     Like *note unquote(): 1689, but also replace plus signs with
     spaces, as required for unquoting HTML form values.

     'string' must be a *note str: 3f2.

     Example: ‘unquote_plus('/El+Ni%C3%B1o/')’ yields ‘'/El Niño/'’.

 -- 函式: urllib.parse.unquote_to_bytes (string)

     Replace ‘%XX’ escapes with their single-octet equivalent, and
     return a *note bytes: 1a5. object.

     'string' may be either a *note str: 3f2. or a *note bytes: 1a5.
     object.

     If it is a *note str: 3f2, unescaped non-ASCII characters in
     'string' are encoded into UTF-8 bytes.

     Example: ‘unquote_to_bytes('a%26%EF')’ yields ‘b'a&\xef'’.

 -- 函式: urllib.parse.urlencode (query, doseq=False, safe='',
          encoding=None, errors=None, quote_via=quote_plus)

     Convert a mapping object or a sequence of two-element tuples, which
     may contain *note str: 3f2. or *note bytes: 1a5. objects, to a
     percent-encoded ASCII text string.  If the resultant string is to
     be used as a 'data' for POST operation with the *note urlopen():
     275. function, then it should be encoded to bytes, otherwise it
     would result in a *note TypeError: 4dd.

     The resulting string is a series of ‘key=value’ pairs separated by
     ‘'&'’ characters, where both 'key' and 'value' are quoted using the
     'quote_via' function.  By default, *note quote_plus(): 11e1. is
     used to quote the values, which means spaces are quoted as a ‘'+'’
     character and '/' characters are encoded as ‘%2F’, which follows
     the standard for GET requests
     (‘application/x-www-form-urlencoded’).  An alternate function that
     can be passed as 'quote_via' is *note quote(): b4a, which will
     encode spaces as ‘%20’ and not encode '/' characters.  For maximum
     control of what is quoted, use ‘quote’ and specify a value for
     'safe'.

     When a sequence of two-element tuples is used as the 'query'
     argument, the first element of each tuple is a key and the second
     is a value.  The value element in itself can be a sequence and in
     that case, if the optional parameter 'doseq' evaluates to ‘True’,
     individual ‘key=value’ pairs separated by ‘'&'’ are generated for
     each element of the value sequence for the key.  The order of
     parameters in the encoded string will match the order of parameter
     tuples in the sequence.

     The 'safe', 'encoding', and 'errors' parameters are passed down to
     'quote_via' (the 'encoding' and 'errors' parameters are only passed
     when a query element is a *note str: 3f2.).

     To reverse this encoding process, *note parse_qs(): 25f. and *note
     parse_qsl(): 25e. are provided in this module to parse query
     strings into Python data structures.

     Refer to *note urllib examples: 3837. to find out how the *note
     urllib.parse.urlencode(): e37. method can be used for generating
     the query string of a URL or data for a POST request.

     在 3.2 版的變更: 'query' supports bytes and string objects.

     在 3.5 版的變更: 新增 'quote_via' 參數。

也參考
......

WHATWG(3) - URL Living standard

     Working Group for the URL Standard that defines URLs, domains, IP
     addresses, the application/x-www-form-urlencoded format, and their
     API.

RFC 3986(4) - Uniform Resource Identifiers

     This is the current standard (STD66).  Any changes to urllib.parse
     module should conform to this.  Certain deviations could be
     observed, which are mostly for backward compatibility purposes and
     for certain de-facto parsing requirements as commonly observed in
     major browsers.

RFC 2732(5) - Format for Literal IPv6 Addresses in URL's.

     This specifies the parsing requirements of IPv6 URLs.

RFC 2396(6) - Uniform Resource Identifiers (URI): Generic Syntax

     Document describing the generic syntactic requirements for both
     Uniform Resource Names (URNs) and Uniform Resource Locators (URLs).

RFC 2368(7) - The mailto URL scheme.

     Parsing requirements for mailto URL schemes.

RFC 1808(8) - 相對的統一資源定位器 (Relative Uniform Resource Locators)

     This Request For Comments includes the rules for joining an
     absolute and a relative URL, including a fair number of "Abnormal
     Examples" which govern the treatment of border cases.

RFC 1738(9) - 統一資源定位器 (URL, Uniform Resource Locators)

     This specifies the formal syntax and semantics of absolute URLs.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2396.html

   (2) https://datatracker.ietf.org/doc/html/rfc3986.html

   (3) https://url.spec.whatwg.org/

   (4) https://datatracker.ietf.org/doc/html/rfc3986.html

   (5) https://datatracker.ietf.org/doc/html/rfc2732.html

   (6) https://datatracker.ietf.org/doc/html/rfc2396.html

   (7) https://datatracker.ietf.org/doc/html/rfc2368.html

   (8) https://datatracker.ietf.org/doc/html/rfc1808.html

   (9) https://datatracker.ietf.org/doc/html/rfc1738.html


File: python.info,  Node: urllib error --- urllib request 引發的例外類別,  Next: urllib robotparser --- robots txt 的剖析器,  Prev: urllib parse --- 將 URL 剖析成元件,  Up: 網路協定 Internet protocols 及支援

5.21.7 ‘urllib.error’ -- urllib.request 引發的例外類別
------------------------------------------------------

'原始碼：'Lib/urllib/error.py(1)

__________________________________________________________________

*note urllib.error: f2. module（模組）為 *note urllib.request: f4. 所引
發的例外定義了例外 (exception) 類別。基礎例外類別是 *note URLError:
37bf.。

下列例外會被 *note urllib.error: f2. 適時引發：

 -- 例外: urllib.error.URLError

     處理程式 (handler) 在遇到問題時會引發此例外（或其衍生例外）。它是
     *note OSError: 350. 的一個子類別。

      -- 屬性: reason

          此錯誤的原因。它可以是一個訊息字串或另一個例外實例。

     在 3.3 版的變更: *note URLError: 37bf. 過去是 *note OSError: 350. 的
     子類別，但現在為 *note OSError: 350. 的別名。

 -- 例外: urllib.error.HTTPError (url, code, msg, hdrs, fp)

     雖然是一個例外（*note URLError: 37bf. 的一個子類別），*note
     HTTPError: f81. 也可以作為一個非例外的類檔案回傳值（與 *note
     urlopen(): 275. 所回傳的物件相同）。這適用於處理特殊 HTTP 錯誤，例
     如為請求認證。

      -- 屬性: url

          包含請求 URL。'filename' 屬性的別名。

      -- 屬性: code

          一個 HTTP 狀態碼，具體定義見 RFC 2616(2)。這個數值會對應到存放
          在 *note http.server.BaseHTTPRequestHandler.responses: 385f. 程
          式碼 dictionary 中的某個值。

      -- 屬性: reason

          這通常是一個解釋本次錯誤原因的字串。為 'msg' 屬性的別名。

      -- 屬性: headers

          導致 *note HTTPError: f81. 的特定 HTTP 請求的 HTTP 回應
          header。為 'hdrs' 屬性的別名。

          在 3.4 版被加入.

      -- 屬性: fp

          一個類檔案物件，可以從中讀取 HTTP 錯誤主體 (body)。

 -- 例外: urllib.error.ContentTooShortError (msg, content)

     此例外會在 *note urlretrieve(): 3839. 函式檢查到已下載的資料量小於
     期待的資料量（由 'Content-Length' header 給定）時被引發。

      -- 屬性: content

          已下載（可能已被截斷）的資料。

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/urllib/error.py

   (2) https://datatracker.ietf.org/doc/html/rfc2616.html


File: python.info,  Node: urllib robotparser --- robots txt 的剖析器,  Next: http --- HTTP 模組,  Prev: urllib error --- urllib request 引發的例外類別,  Up: 網路協定 Internet protocols 及支援

5.21.8 ‘urllib.robotparser’ -- robots.txt 的剖析器
--------------------------------------------------

'原始碼：'Lib/urllib/robotparser.py(1)

__________________________________________________________________

此模組 (module) 提供了一個單獨的類別 (class) *note RobotFileParser:
ca4.，它可以知道某個特定 user agent（使用者代理）是否能在有發布
‘robots.txt’ 文件的網站 fetch（擷取）特定 URL。有關 ‘robots.txt’ 文件結
構的更多細節，請參閱 ‘http://www.robotstxt.org/orig.html’。

 -- 類別: urllib.robotparser.RobotFileParser (url='')

     此類別提供了一些方法可以讀取、剖析和回答關於 'url' 上的
     ‘robots.txt’ 文件的問題。

      -- 方法: set_url (url)

          設置指向 ‘robots.txt’ 文件的 URL。

      -- 方法: read ()

          讀取 ‘robots.txt’ URL 並將其輸入到剖析器。

      -- 方法: parse (lines)

          剖析 lines 引數。

      -- 方法: can_fetch (useragent, url)

          根據從 ‘robots.txt’ 文件中剖析出的規則，如果 'useragent' 被允
          許 fetch 'url' 的話，則回傳 ‘True’。

      -- 方法: mtime ()

          回傳最近一次 fetch ‘robots.txt’ 文件的時間。這適用於需要定期檢
          查 ‘robots.txt’ 文件更新情況的長時間運行網頁爬蟲。

      -- 方法: modified ()

          將最近一次 fetch ‘robots.txt’ 文件的時間設置為當前時間。

      -- 方法: crawl_delay (useragent)

          針對指定的 'useragent' 從 ‘robots.txt’ 回傳 ‘Crawl-delay’ 參數
          的值。如果此參數不存在、不適用於指定的 'useragent' ，或是此參
          數在 ‘robots.txt’ 中所指的條目含有無效語法，則回傳 ‘None’。

          在 3.6 版被加入.

      -- 方法: request_rate (useragent)

          以 *note named tuple: 5f4. ‘RequestRate(requests, seconds)’ 的
          形式從 ‘robots.txt’ 回傳 ‘Request-rate’ 參數的內容。如果此參數
          不存在、不適用於指定的 'useragent' ，或是此參數在 ‘robots.txt’
          中所指的條目含有無效語法，則回傳 ‘None’。

          在 3.6 版被加入.

      -- 方法: site_maps ()

          以 *note list(): 5b6. 的形式從 ‘robots.txt’ 回傳 ‘Sitemap’ 參
          數的內容。如果此參數不存在或此參數在 ‘robots.txt’ 中所指的條目
          含有無效語法，則回傳 ‘None’。

          在 3.8 版被加入.

下面的範例展示了 *note RobotFileParser: ca4. 類別的基本用法：

     >>> import urllib.robotparser
     >>> rp = urllib.robotparser.RobotFileParser()
     >>> rp.set_url("http://www.musi-cal.com/robots.txt")
     >>> rp.read()
     >>> rrate = rp.request_rate("*")
     >>> rrate.requests
     3
     >>> rrate.seconds
     20
     >>> rp.crawl_delay("*")
     6
     >>> rp.can_fetch("*", "http://www.musi-cal.com/cgi-bin/search?city=San+Francisco")
     False
     >>> rp.can_fetch("*", "http://www.musi-cal.com/")
     True

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/urllib/robotparser.py


File: python.info,  Node: http --- HTTP 模組,  Next: http client --- HTTP 協定用戶端,  Prev: urllib robotparser --- robots txt 的剖析器,  Up: 網路協定 Internet protocols 及支援

5.21.9 ‘http’ -- HTTP 模組
--------------------------

'原始碼：'Lib/http/__init__.py(1)

__________________________________________________________________

*note http: 64. 是一個收集了多個用於處理超文本傳輸協定 (HyperText
Transfer Protocol) 之模組 (module) 的套件：

   * *note http.client: 65. 是一個低階的 HTTP 協定客戶端；對於高階的 URL
     訪問請使用 *note urllib.request: f4.

   * *note http.server: 68. 包含基於 *note socketserver: b9. 的基本 HTTP
     伺服器類別

   * *note http.cookies: 67. 包含通過 cookies 實作狀態管理的工具程式
     (utilities)

   * *note http.cookiejar: 66. 提供了 cookies 的持續留存 (persistence)

The *note http: 64. module also defines the following enums that help
you work with http related code:

 -- 類別: http.HTTPStatus

     在 3.5 版被加入.

     *note enum.IntEnum: c86. 的子類別，它定義了一組 HTTP 狀態碼、原理短
     語 (reason phrase) 以及英文長描述。

     用法：

          >>> from http import HTTPStatus
          >>> HTTPStatus.OK
          HTTPStatus.OK
          >>> HTTPStatus.OK == 200
          True
          >>> HTTPStatus.OK.value
          200
          >>> HTTPStatus.OK.phrase
          'OK'
          >>> HTTPStatus.OK.description
          'Request fulfilled, document follows'
          >>> list(HTTPStatus)
          [HTTPStatus.CONTINUE, HTTPStatus.SWITCHING_PROTOCOLS, ...]

* Menu:

* HTTP 狀態碼::
* HTTP 狀態分類::
* HTTP 方法::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/http/__init__.py


File: python.info,  Node: HTTP 狀態碼,  Next: HTTP 狀態分類,  Up: http --- HTTP 模組

5.21.9.1 HTTP 狀態碼
....................

*note http.HTTPStatus: 8a5. 當中，已支援並且有於 IANA 註冊的狀態碼(1)有
：

狀態碼      列舉名稱                                詳情
                                                    
----------------------------------------------------------------------------------------------------------------------------------------
                                                    
‘100’       ‘CONTINUE’                              HTTP Semantics RFC 9110(2), Section 15.2.1
                                                    
                                                    
‘101’       ‘SWITCHING_PROTOCOLS’                   HTTP Semantics RFC 9110(3), Section 15.2.2
                                                    
                                                    
‘102’       ‘PROCESSING’                            WebDAV RFC 2518(4)，10.1 節
                                                    
                                                    
‘103’       ‘EARLY_HINTS’                           用於指定提示 (Indicating Hints) RFC 8297(5) 的 HTTP 狀態碼
                                                    
                                                    
‘200’       ‘OK’                                    HTTP Semantics RFC 9110(6), Section 15.3.1
                                                    
                                                    
‘201’       ‘CREATED’                               HTTP Semantics RFC 9110(7), Section 15.3.2
                                                    
                                                    
‘202’       ‘ACCEPTED’                              HTTP Semantics RFC 9110(8), Section 15.3.3
                                                    
                                                    
‘203’       ‘NON_AUTHORITATIVE_INFORMATION’         HTTP Semantics RFC 9110(9), Section 15.3.4
                                                    
                                                    
‘204’       ‘NO_CONTENT’                            HTTP Semantics RFC 9110(10), Section 15.3.5
                                                    
                                                    
‘205’       ‘RESET_CONTENT’                         HTTP Semantics RFC 9110(11), Section 15.3.6
                                                    
                                                    
‘206’       ‘PARTIAL_CONTENT’                       HTTP Semantics RFC 9110(12), Section 15.3.7
                                                    
                                                    
‘207’       ‘MULTI_STATUS’                          WebDAV RFC 4918(13)，11.1 節
                                                    
                                                    
‘208’       ‘ALREADY_REPORTED’                      WebDAV 繫結擴充 (Binding Extensions) RFC 5842(14)，7.1 節（實驗性）
                                                    
                                                    
‘226’       ‘IM_USED’                               HTTP 中的差分編碼 RFC 3229(15)，10.4.1 節
                                                    
                                                    
‘300’       ‘MULTIPLE_CHOICES’                      HTTP Semantics RFC 9110(16), Section 15.4.1
                                                    
                                                    
‘301’       ‘MOVED_PERMANENTLY’                     HTTP Semantics RFC 9110(17), Section 15.4.2
                                                    
                                                    
‘302’       ‘FOUND’                                 HTTP Semantics RFC 9110(18), Section 15.4.3
                                                    
                                                    
‘303’       ‘SEE_OTHER’                             HTTP Semantics RFC 9110(19), Section 15.4.4
                                                    
                                                    
‘304’       ‘NOT_MODIFIED’                          HTTP Semantics RFC 9110(20), Section 15.4.5
                                                    
                                                    
‘305’       ‘USE_PROXY’                             HTTP Semantics RFC 9110(21), Section 15.4.6
                                                    
                                                    
‘307’       ‘TEMPORARY_REDIRECT’                    HTTP Semantics RFC 9110(22), Section 15.4.8
                                                    
                                                    
‘308’       ‘PERMANENT_REDIRECT’                    HTTP Semantics RFC 9110(23), Section 15.4.9
                                                    
                                                    
‘400’       ‘BAD_REQUEST’                           HTTP Semantics RFC 9110(24), Section 15.5.1
                                                    
                                                    
‘401’       ‘UNAUTHORIZED’                          HTTP Semantics RFC 9110(25), Section 15.5.2
                                                    
                                                    
‘402’       ‘PAYMENT_REQUIRED’                      HTTP Semantics RFC 9110(26), Section 15.5.3
                                                    
                                                    
‘403’       ‘FORBIDDEN’                             HTTP Semantics RFC 9110(27), Section 15.5.4
                                                    
                                                    
‘404’       ‘NOT_FOUND’                             HTTP Semantics RFC 9110(28), Section 15.5.5
                                                    
                                                    
‘405’       ‘METHOD_NOT_ALLOWED’                    HTTP Semantics RFC 9110(29), Section 15.5.6
                                                    
                                                    
‘406’       ‘NOT_ACCEPTABLE’                        HTTP Semantics RFC 9110(30), Section 15.5.7
                                                    
                                                    
‘407’       ‘PROXY_AUTHENTICATION_REQUIRED’         HTTP Semantics RFC 9110(31), Section 15.5.8
                                                    
                                                    
‘408’       ‘REQUEST_TIMEOUT’                       HTTP Semantics RFC 9110(32), Section 15.5.9
                                                    
                                                    
‘409’       ‘CONFLICT’                              HTTP Semantics RFC 9110(33), Section 15.5.10
                                                    
                                                    
‘410’       ‘GONE’                                  HTTP Semantics RFC 9110(34), Section 15.5.11
                                                    
                                                    
‘411’       ‘LENGTH_REQUIRED’                       HTTP Semantics RFC 9110(35), Section 15.5.12
                                                    
                                                    
‘412’       ‘PRECONDITION_FAILED’                   HTTP Semantics RFC 9110(36), Section 15.5.13
                                                    
                                                    
‘413’       ‘CONTENT_TOO_LARGE’                     HTTP Semantics RFC 9110(37), Section 15.5.14
                                                    
                                                    
‘414’       ‘URI_TOO_LONG’                          HTTP Semantics RFC 9110(38), Section 15.5.15
                                                    
                                                    
‘415’       ‘UNSUPPORTED_MEDIA_TYPE’                HTTP Semantics RFC 9110(39), Section 15.5.16
                                                    
                                                    
‘416’       ‘RANGE_NOT_SATISFIABLE’                 HTTP Semantics RFC 9110(40), Section 15.5.17
                                                    
                                                    
‘417’       ‘EXPECTATION_FAILED’                    HTTP Semantics RFC 9110(41), Section 15.5.18
                                                    
                                                    
‘418’       ‘IM_A_TEAPOT’                           HTCPCP/1.0 RFC 2324(42)，Section 2.3.2
                                                    
                                                    
‘421’       ‘MISDIRECTED_REQUEST’                   HTTP Semantics RFC 9110(43), Section 15.5.20
                                                    
                                                    
‘422’       ‘UNPROCESSABLE_CONTENT’                 HTTP Semantics RFC 9110(44), Section 15.5.21
                                                    
                                                    
‘423’       ‘LOCKED’                                WebDAV RFC 4918(45)，11.3 節
                                                    
                                                    
‘424’       ‘FAILED_DEPENDENCY’                     WebDAV RFC 4918(46)，11.4 節
                                                    
                                                    
‘425’       ‘TOO_EARLY’                             使用 HTTP 中的早期資料 RFC 8470(47)
                                                    
                                                    
‘426’       ‘UPGRADE_REQUIRED’                      HTTP Semantics RFC 9110(48), Section 15.5.22
                                                    
                                                    
‘428’       ‘PRECONDITION_REQUIRED’                 額外的 HTTP 狀態碼 RFC 6585(49)
                                                    
                                                    
‘429’       ‘TOO_MANY_REQUESTS’                     額外的 HTTP 狀態碼 RFC 6585(50)
                                                    
                                                    
‘431’       ‘REQUEST_HEADER_FIELDS_TOO_LARGE’       額外的 HTTP 狀態碼 RFC 6585(51)
                                                    
                                                    
‘451’       ‘UNAVAILABLE_FOR_LEGAL_REASONS’         一個用來回報合法性障礙 (Legal Obstacles) 的 HTTP 狀態碼 RFC 7725(52)
                                                    
                                                    
‘500’       ‘INTERNAL_SERVER_ERROR’                 HTTP Semantics RFC 9110(53), Section 15.6.1
                                                    
                                                    
‘501’       ‘NOT_IMPLEMENTED’                       HTTP Semantics RFC 9110(54), Section 15.6.2
                                                    
                                                    
‘502’       ‘BAD_GATEWAY’                           HTTP Semantics RFC 9110(55), Section 15.6.3
                                                    
                                                    
‘503’       ‘SERVICE_UNAVAILABLE’                   HTTP Semantics RFC 9110(56), Section 15.6.4
                                                    
                                                    
‘504’       ‘GATEWAY_TIMEOUT’                       HTTP Semantics RFC 9110(57), Section 15.6.5
                                                    
                                                    
‘505’       ‘HTTP_VERSION_NOT_SUPPORTED’            HTTP Semantics RFC 9110(58), Section 15.6.6
                                                    
                                                    
‘506’       ‘VARIANT_ALSO_NEGOTIATES’               HTTP 中的透明內容協商 (Transparent Content Negotiation) RFC 2295(59)，8.1 節（實
                                                    驗性）
                                                    
                                                    
‘507’       ‘INSUFFICIENT_STORAGE’                  WebDAV RFC 4918(60)，11.5 節
                                                    
                                                    
‘508’       ‘LOOP_DETECTED’                         WebDAV 繫結擴充 RFC 5842(61)，7.2 節（實驗性）
                                                    
                                                    
‘510’       ‘NOT_EXTENDED’                          一個 HTTP 擴充框架 RFC 2774(62)，7 節（實驗性）
                                                    
                                                    
‘511’       ‘NETWORK_AUTHENTICATION_REQUIRED’       額外的 HTTP 狀態碼 RFC 6585(63)，6 節
                                                    

為了向後相容性，列舉值也以常數形式出現在 *note http.client: 65. 模組中。
列舉名稱等於常數名稱（例如 ‘http.HTTPStatus.OK’ 也可以是
‘http.client.OK’）。

在 3.7 版的變更: 新增 ‘421 MISDIRECTED_REQUEST’ 狀態碼。

在 3.8 版被加入: 新增 ‘451 UNAVAILABLE_FOR_LEGAL_REASONS’ 狀態碼。

在 3.9 版被加入: 新增 ‘103 EARLY_HINTS’、‘418 IM_A_TEAPOT’ 與 ‘425
TOO_EARLY’ 狀態碼。

在 3.13 版的變更: Implemented RFC9110 naming for status constants.  Old
constant names are preserved for backwards compatibility.

   ---------- Footnotes ----------

   (1) 
https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml

   (2) https://datatracker.ietf.org/doc/html/rfc9110.html

   (3) https://datatracker.ietf.org/doc/html/rfc9110.html

   (4) https://datatracker.ietf.org/doc/html/rfc2518.html

   (5) https://datatracker.ietf.org/doc/html/rfc8297.html

   (6) https://datatracker.ietf.org/doc/html/rfc9110.html

   (7) https://datatracker.ietf.org/doc/html/rfc9110.html

   (8) https://datatracker.ietf.org/doc/html/rfc9110.html

   (9) https://datatracker.ietf.org/doc/html/rfc9110.html

   (10) https://datatracker.ietf.org/doc/html/rfc9110.html

   (11) https://datatracker.ietf.org/doc/html/rfc9110.html

   (12) https://datatracker.ietf.org/doc/html/rfc9110.html

   (13) https://datatracker.ietf.org/doc/html/rfc4918.html

   (14) https://datatracker.ietf.org/doc/html/rfc5842.html

   (15) https://datatracker.ietf.org/doc/html/rfc3229.html

   (16) https://datatracker.ietf.org/doc/html/rfc9110.html

   (17) https://datatracker.ietf.org/doc/html/rfc9110.html

   (18) https://datatracker.ietf.org/doc/html/rfc9110.html

   (19) https://datatracker.ietf.org/doc/html/rfc9110.html

   (20) https://datatracker.ietf.org/doc/html/rfc9110.html

   (21) https://datatracker.ietf.org/doc/html/rfc9110.html

   (22) https://datatracker.ietf.org/doc/html/rfc9110.html

   (23) https://datatracker.ietf.org/doc/html/rfc9110.html

   (24) https://datatracker.ietf.org/doc/html/rfc9110.html

   (25) https://datatracker.ietf.org/doc/html/rfc9110.html

   (26) https://datatracker.ietf.org/doc/html/rfc9110.html

   (27) https://datatracker.ietf.org/doc/html/rfc9110.html

   (28) https://datatracker.ietf.org/doc/html/rfc9110.html

   (29) https://datatracker.ietf.org/doc/html/rfc9110.html

   (30) https://datatracker.ietf.org/doc/html/rfc9110.html

   (31) https://datatracker.ietf.org/doc/html/rfc9110.html

   (32) https://datatracker.ietf.org/doc/html/rfc9110.html

   (33) https://datatracker.ietf.org/doc/html/rfc9110.html

   (34) https://datatracker.ietf.org/doc/html/rfc9110.html

   (35) https://datatracker.ietf.org/doc/html/rfc9110.html

   (36) https://datatracker.ietf.org/doc/html/rfc9110.html

   (37) https://datatracker.ietf.org/doc/html/rfc9110.html

   (38) https://datatracker.ietf.org/doc/html/rfc9110.html

   (39) https://datatracker.ietf.org/doc/html/rfc9110.html

   (40) https://datatracker.ietf.org/doc/html/rfc9110.html

   (41) https://datatracker.ietf.org/doc/html/rfc9110.html

   (42) https://datatracker.ietf.org/doc/html/rfc2324.html

   (43) https://datatracker.ietf.org/doc/html/rfc9110.html

   (44) https://datatracker.ietf.org/doc/html/rfc9110.html

   (45) https://datatracker.ietf.org/doc/html/rfc4918.html

   (46) https://datatracker.ietf.org/doc/html/rfc4918.html

   (47) https://datatracker.ietf.org/doc/html/rfc8470.html

   (48) https://datatracker.ietf.org/doc/html/rfc9110.html

   (49) https://datatracker.ietf.org/doc/html/rfc6585.html

   (50) https://datatracker.ietf.org/doc/html/rfc6585.html

   (51) https://datatracker.ietf.org/doc/html/rfc6585.html

   (52) https://datatracker.ietf.org/doc/html/rfc7725.html

   (53) https://datatracker.ietf.org/doc/html/rfc9110.html

   (54) https://datatracker.ietf.org/doc/html/rfc9110.html

   (55) https://datatracker.ietf.org/doc/html/rfc9110.html

   (56) https://datatracker.ietf.org/doc/html/rfc9110.html

   (57) https://datatracker.ietf.org/doc/html/rfc9110.html

   (58) https://datatracker.ietf.org/doc/html/rfc9110.html

   (59) https://datatracker.ietf.org/doc/html/rfc2295.html

   (60) https://datatracker.ietf.org/doc/html/rfc4918.html

   (61) https://datatracker.ietf.org/doc/html/rfc5842.html

   (62) https://datatracker.ietf.org/doc/html/rfc2774.html

   (63) https://datatracker.ietf.org/doc/html/rfc6585.html


File: python.info,  Node: HTTP 狀態分類,  Next: HTTP 方法,  Prev: HTTP 狀態碼,  Up: http --- HTTP 模組

5.21.9.2 HTTP 狀態分類
......................

在 3.12 版被加入.

The enum values have several properties to indicate the HTTP status
category:

Property                 Indicates that               詳情
                                                      
-------------------------------------------------------------------------------------------------
                                                      
‘is_informational’       ‘100 <= status <= 199’       HTTP Semantics RFC 9110(1), Section 15
                                                      
                                                      
‘is_success’             ‘200 <= status <= 299’       HTTP Semantics RFC 9110(2), Section 15
                                                      
                                                      
‘is_redirection’         ‘300 <= status <= 399’       HTTP Semantics RFC 9110(3), Section 15
                                                      
                                                      
‘is_client_error’        ‘400 <= status <= 499’       HTTP Semantics RFC 9110(4), Section 15
                                                      
                                                      
‘is_server_error’        ‘500 <= status <= 599’       HTTP Semantics RFC 9110(5), Section 15
                                                      

     用法：

          >>> from http import HTTPStatus
          >>> HTTPStatus.OK.is_success
          True
          >>> HTTPStatus.OK.is_client_error
          False

 -- 類別: http.HTTPMethod

     在 3.11 版被加入.

     *note enum.StrEnum: 5c0. 的子類別，它定義了一組 HTTP 方法以及英文描
     述。

     用法：

          >>> from http import HTTPMethod
          >>>
          >>> HTTPMethod.GET
          <HTTPMethod.GET>
          >>> HTTPMethod.GET == 'GET'
          True
          >>> HTTPMethod.GET.value
          'GET'
          >>> HTTPMethod.GET.description
          'Retrieve the target.'
          >>> list(HTTPMethod)
          [<HTTPMethod.CONNECT>,
           <HTTPMethod.DELETE>,
           <HTTPMethod.GET>,
           <HTTPMethod.HEAD>,
           <HTTPMethod.OPTIONS>,
           <HTTPMethod.PATCH>,
           <HTTPMethod.POST>,
           <HTTPMethod.PUT>,
           <HTTPMethod.TRACE>]

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc9110.html

   (2) https://datatracker.ietf.org/doc/html/rfc9110.html

   (3) https://datatracker.ietf.org/doc/html/rfc9110.html

   (4) https://datatracker.ietf.org/doc/html/rfc9110.html

   (5) https://datatracker.ietf.org/doc/html/rfc9110.html


File: python.info,  Node: HTTP 方法,  Prev: HTTP 狀態分類,  Up: http --- HTTP 模組

5.21.9.3 HTTP 方法
..................

*note http.HTTPStatus: 8a5. 當中，已支援並且有於 IANA 註冊的狀態碼(1)有
：

方法            列舉名稱                                詳情
                                                        
-------------------------------------------------------------------------------------------------------------------------------
                                                        
‘GET’           ‘GET’                                   HTTP Semantics RFC 9110(2), Section 9.3.1
                                                        
                                                        
‘HEAD’          ‘HEAD’                                  HTTP Semantics RFC 9110(3), Section 9.3.2
                                                        
                                                        
‘POST’          ‘POST’                                  HTTP Semantics RFC 9110(4), Section 9.3.3
                                                        
                                                        
‘PUT’           ‘PUT’                                   HTTP Semantics RFC 9110(5), Section 9.3.4
                                                        
                                                        
‘DELETE’        ‘DELETE’                                HTTP Semantics RFC 9110(6), Section 9.3.5
                                                        
                                                        
‘CONNECT’       ‘CONNECT’                               HTTP Semantics RFC 9110(7), Section 9.3.6
                                                        
                                                        
‘OPTIONS’       ‘OPTIONS’                               HTTP Semantics RFC 9110(8), Section 9.3.7
                                                        
                                                        
‘TRACE’         ‘TRACE’                                 HTTP Semantics RFC 9110(9), Section 9.3.8
                                                        
                                                        
‘PATCH’         ‘PATCH’                                 HTTP/1.1 RFC 5789(10)
                                                        

   ---------- Footnotes ----------

   (1) 
https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml

   (2) https://datatracker.ietf.org/doc/html/rfc9110.html

   (3) https://datatracker.ietf.org/doc/html/rfc9110.html

   (4) https://datatracker.ietf.org/doc/html/rfc9110.html

   (5) https://datatracker.ietf.org/doc/html/rfc9110.html

   (6) https://datatracker.ietf.org/doc/html/rfc9110.html

   (7) https://datatracker.ietf.org/doc/html/rfc9110.html

   (8) https://datatracker.ietf.org/doc/html/rfc9110.html

   (9) https://datatracker.ietf.org/doc/html/rfc9110.html

   (10) https://datatracker.ietf.org/doc/html/rfc5789.html


File: python.info,  Node: http client --- HTTP 協定用戶端,  Next: ftplib --- FTP 協定用戶端,  Prev: http --- HTTP 模組,  Up: 網路協定 Internet protocols 及支援

5.21.10 ‘http.client’ -- HTTP 協定用戶端
----------------------------------------

'原始碼：'Lib/http/client.py(1)

__________________________________________________________________

This module defines classes that implement the client side of the HTTP
and HTTPS protocols.  It is normally not used directly -- the module
*note urllib.request: f4. uses it to handle URLs that use HTTP and
HTTPS.

也參考
......

The Requests package(2) is recommended for a higher-level HTTP client
interface.

     備註: HTTPS support is only available if Python was compiled with
     SSL support (through the *note ssl: bb. module).

*note Availability: 1c56.: not WASI.

This module does not work or is not available on WebAssembly.  See *note
WebAssembly 平台: 16e6. for more information.

The module provides the following classes:

 -- 類別: http.client.HTTPConnection (host, port=None[, timeout],
          source_address=None, blocksize=8192)

     An *note HTTPConnection: ae4. instance represents one transaction
     with an HTTP server.  It should be instantiated by passing it a
     host and optional port number.  If no port number is passed, the
     port is extracted from the host string if it has the form
     ‘host:port’, else the default HTTP port (80) is used.  If the
     optional 'timeout' parameter is given, blocking operations (like
     connection attempts) will timeout after that many seconds (if it is
     not given, the global default timeout setting is used).  The
     optional 'source_address' parameter may be a tuple of a (host,
     port) to use as the source address the HTTP connection is made
     from.  The optional 'blocksize' parameter sets the buffer size in
     bytes for sending a file-like message body.

     For example, the following calls all create instances that connect
     to the server at the same host and port:

          >>> h1 = http.client.HTTPConnection('www.python.org')
          >>> h2 = http.client.HTTPConnection('www.python.org:80')
          >>> h3 = http.client.HTTPConnection('www.python.org', 80)
          >>> h4 = http.client.HTTPConnection('www.python.org', 80, timeout=10)

     在 3.2 版的變更: 新增 'source_address'。

     在 3.4 版的變更: The 'strict' parameter was removed.  HTTP
     0.9-style "Simple Responses" are no longer supported.

     在 3.7 版的變更: 新增 'blocksize' 參數。

 -- 類別: http.client.HTTPSConnection (host, port=None, *[, timeout],
          source_address=None, context=None, blocksize=8192)

     A subclass of *note HTTPConnection: ae4. that uses SSL for
     communication with secure servers.  Default port is ‘443’.  If
     'context' is specified, it must be a *note ssl.SSLContext: 276.
     instance describing the various SSL options.

     Please read *note Security considerations: 317d. for more
     information on best practices.

     在 3.2 版的變更: 新增 'source_address'、'context' 與
     'check_hostname'。

     在 3.2 版的變更: This class now supports HTTPS virtual hosts if
     possible (that is, if *note ssl.HAS_SNI: 32b1. is true).

     在 3.4 版的變更: The 'strict' parameter was removed.  HTTP
     0.9-style "Simple Responses" are no longer supported.

     在 3.4.3 版的變更: This class now performs all the necessary
     certificate and hostname checks by default.  To revert to the
     previous, unverified, behavior ‘ssl._create_unverified_context()’
     can be passed to the 'context' parameter.

     在 3.8 版的變更: This class now enables TLS 1.3 *note
     ssl.SSLContext.post_handshake_auth: 9d5. for the default 'context'
     or when 'cert_file' is passed with a custom 'context'.

     在 3.10 版的變更: This class now sends an ALPN extension with
     protocol indicator ‘http/1.1’ when no 'context' is given.  Custom
     'context' should set ALPN protocols with *note
     set_alpn_protocols(): e06.

     在 3.12 版的變更: The deprecated 'key_file', 'cert_file' and
     'check_hostname' parameters have been removed.

 -- 類別: http.client.HTTPResponse (sock, debuglevel=0, method=None,
          url=None)

     Class whose instances are returned upon successful connection.  Not
     instantiated directly by user.

     在 3.4 版的變更: The 'strict' parameter was removed.  HTTP 0.9
     style "Simple Responses" are no longer supported.

This module provides the following function:

 -- 函式: http.client.parse_headers (fp)

     Parse the headers from a file pointer 'fp' representing a HTTP
     request/response.  The file has to be a *note BufferedIOBase: 63a.
     reader (i.e.  not text) and must provide a valid RFC 2822(3) style
     header.

     This function returns an instance of *note http.client.HTTPMessage:
     3876. that holds the header fields, but no payload (the same as
     *note HTTPResponse.msg: 3877. and *note
     http.server.BaseHTTPRequestHandler.headers: 3878.).  After
     returning, the file pointer 'fp' is ready to read the HTTP body.

          備註: *note parse_headers(): 194f. does not parse the
          start-line of a HTTP message; it only parses the ‘Name: value’
          lines.  The file has to be ready to read these field lines, so
          the first line should already be consumed before calling the
          function.

The following exceptions are raised as appropriate:

 -- 例外: http.client.HTTPException

     The base class of the other exceptions in this module.  It is a
     subclass of *note Exception: 97d.

 -- 例外: http.client.NotConnected

     A subclass of *note HTTPException: 3879.

 -- 例外: http.client.InvalidURL

     A subclass of *note HTTPException: 3879, raised if a port is given
     and is either non-numeric or empty.

 -- 例外: http.client.UnknownProtocol

     A subclass of *note HTTPException: 3879.

 -- 例外: http.client.UnknownTransferEncoding

     A subclass of *note HTTPException: 3879.

 -- 例外: http.client.UnimplementedFileMode

     A subclass of *note HTTPException: 3879.

 -- 例外: http.client.IncompleteRead

     A subclass of *note HTTPException: 3879.

 -- 例外: http.client.ImproperConnectionState

     A subclass of *note HTTPException: 3879.

 -- 例外: http.client.CannotSendRequest

     A subclass of *note ImproperConnectionState: 3880.

 -- 例外: http.client.CannotSendHeader

     A subclass of *note ImproperConnectionState: 3880.

 -- 例外: http.client.ResponseNotReady

     A subclass of *note ImproperConnectionState: 3880.

 -- 例外: http.client.BadStatusLine

     A subclass of *note HTTPException: 3879.  Raised if a server
     responds with a HTTP status code that we don't understand.

 -- 例外: http.client.LineTooLong

     A subclass of *note HTTPException: 3879.  Raised if an excessively
     long line is received in the HTTP protocol from the server.

 -- 例外: http.client.RemoteDisconnected

     A subclass of *note ConnectionResetError: 1002. and *note
     BadStatusLine: 3884.  Raised by *note HTTPConnection.getresponse():
     dae. when the attempt to read the response results in no data read
     from the connection, indicating that the remote end has closed the
     connection.

     在 3.5 版被加入: Previously, *note BadStatusLine: 3884.‘('')’ was
     raised.

The constants defined in this module are:

 -- 資料: http.client.HTTP_PORT

     The default port for the HTTP protocol (always ‘80’).

 -- 資料: http.client.HTTPS_PORT

     The default port for the HTTPS protocol (always ‘443’).

 -- 資料: http.client.responses

     This dictionary maps the HTTP 1.1 status codes to the W3C names.

     Example: ‘http.client.responses[http.client.NOT_FOUND]’ is ‘'Not
     Found'’.

See *note HTTP 狀態碼: 386e. for a list of HTTP status codes that are
available in this module as constants.

* Menu:

* HTTPConnection 物件::
* HTTPResponse 物件::
* 範例: 範例<36>.
* HTTPMessage 物件::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/http/client.py

   (2) https://requests.readthedocs.io/en/latest/

   (3) https://datatracker.ietf.org/doc/html/rfc2822.html


File: python.info,  Node: HTTPConnection 物件,  Next: HTTPResponse 物件,  Up: http client --- HTTP 協定用戶端

5.21.10.1 HTTPConnection 物件
.............................

*note HTTPConnection: ae4. instances have the following methods:

 -- 方法: HTTPConnection.request (method, url, body=None, headers={}, *,
          encode_chunked=False)

     This will send a request to the server using the HTTP request
     method 'method' and the request URI 'url'.  The provided 'url' must
     be an absolute path to conform with RFC 2616 §5.1.2(1) (unless
     connecting to an HTTP proxy server or using the ‘OPTIONS’ or
     ‘CONNECT’ methods).

     If 'body' is specified, the specified data is sent after the
     headers are finished.  It may be a *note str: 3f2, a *note
     bytes-like object: cd4, an open *note file object: 115b, or an
     iterable of *note bytes: 1a5.  If 'body' is a string, it is encoded
     as ISO-8859-1, the default for HTTP. If it is a bytes-like object,
     the bytes are sent as is.  If it is a *note file object: 115b, the
     contents of the file is sent; this file object should support at
     least the ‘read()’ method.  If the file object is an instance of
     *note io.TextIOBase: 63b, the data returned by the ‘read()’ method
     will be encoded as ISO-8859-1, otherwise the data returned by
     ‘read()’ is sent as is.  If 'body' is an iterable, the elements of
     the iterable are sent as is until the iterable is exhausted.

     The 'headers' argument should be a mapping of extra HTTP headers to
     send with the request.  A Host header(2) must be provided to
     conform with RFC 2616 §5.1.2(3) (unless connecting to an HTTP proxy
     server or using the ‘OPTIONS’ or ‘CONNECT’ methods).

     If 'headers' contains neither Content-Length nor Transfer-Encoding,
     but there is a request body, one of those header fields will be
     added automatically.  If 'body' is ‘None’, the Content-Length
     header is set to ‘0’ for methods that expect a body (‘PUT’, ‘POST’,
     and ‘PATCH’).  If 'body' is a string or a bytes-like object that is
     not also a *note file: 115b, the Content-Length header is set to
     its length.  Any other type of 'body' (files and iterables in
     general) will be chunk-encoded, and the Transfer-Encoding header
     will automatically be set instead of Content-Length.

     The 'encode_chunked' argument is only relevant if Transfer-Encoding
     is specified in 'headers'.  If 'encode_chunked' is ‘False’, the
     HTTPConnection object assumes that all encoding is handled by the
     calling code.  If it is ‘True’, the body will be chunk-encoded.

     For example, to perform a ‘GET’ request to
     ‘https://docs.python.org/3/’:

          >>> import http.client
          >>> host = "docs.python.org"
          >>> conn = http.client.HTTPSConnection(host)
          >>> conn.request("GET", "/3/", headers={"Host": host})
          >>> response = conn.getresponse()
          >>> print(response.status, response.reason)
          200 OK

          備註: Chunked transfer encoding has been added to the HTTP
          protocol version 1.1.  Unless the HTTP server is known to
          handle HTTP 1.1, the caller must either specify the
          Content-Length, or must pass a *note str: 3f2. or bytes-like
          object that is not also a file as the body representation.

     在 3.2 版的變更: 'body' can now be an iterable.

     在 3.6 版的變更: If neither Content-Length nor Transfer-Encoding
     are set in 'headers', file and iterable 'body' objects are now
     chunk-encoded.  The 'encode_chunked' argument was added.  No
     attempt is made to determine the Content-Length for file objects.

 -- 方法: HTTPConnection.getresponse ()

     Should be called after a request is sent to get the response from
     the server.  Returns an *note HTTPResponse: 1068. instance.

          備註: Note that you must have read the whole response before
          you can send a new request to the server.

     在 3.5 版的變更: If a *note ConnectionError: db0. or subclass is
     raised, the *note HTTPConnection: ae4. object will be ready to
     reconnect when a new request is sent.

 -- 方法: HTTPConnection.set_debuglevel (level)

     Set the debugging level.  The default debug level is ‘0’, meaning
     no debugging output is printed.  Any value greater than ‘0’ will
     cause all currently defined debug output to be printed to stdout.
     The ‘debuglevel’ is passed to any new *note HTTPResponse: 1068.
     objects that are created.

     在 3.1 版被加入.

 -- 方法: HTTPConnection.set_tunnel (host, port=None, headers=None)

     Set the host and the port for HTTP Connect Tunnelling.  This allows
     running the connection through a proxy server.

     The 'host' and 'port' arguments specify the endpoint of the
     tunneled connection (i.e.  the address included in the CONNECT
     request, 'not' the address of the proxy server).

     The 'headers' argument should be a mapping of extra HTTP headers to
     send with the CONNECT request.

     As HTTP/1.1 is used for HTTP CONNECT tunnelling request, as per the
     RFC(4), a HTTP ‘Host:’ header must be provided, matching the
     authority-form of the request target provided as the destination
     for the CONNECT request.  If a HTTP ‘Host:’ header is not provided
     via the headers argument, one is generated and transmitted
     automatically.

     For example, to tunnel through a HTTPS proxy server running locally
     on port 8080, we would pass the address of the proxy to the *note
     HTTPSConnection: ae5. constructor, and the address of the host that
     we eventually want to reach to the *note set_tunnel(): 11c0.
     method:

          >>> import http.client
          >>> conn = http.client.HTTPSConnection("localhost", 8080)
          >>> conn.set_tunnel("www.python.org")
          >>> conn.request("HEAD","/index.html")

     在 3.2 版被加入.

     在 3.12 版的變更: HTTP CONNECT tunnelling requests use protocol
     HTTP/1.1, upgraded from protocol HTTP/1.0.  ‘Host:’ HTTP headers
     are mandatory for HTTP/1.1, so one will be automatically generated
     and transmitted if not provided in the headers argument.

 -- 方法: HTTPConnection.get_proxy_response_headers ()

     Returns a dictionary with the headers of the response received from
     the proxy server to the CONNECT request.

     If the CONNECT request was not sent, the method returns ‘None’.

     在 3.12 版被加入.

 -- 方法: HTTPConnection.connect ()

     Connect to the server specified when the object was created.  By
     default, this is called automatically when making a request if the
     client does not already have a connection.

     引發一個附帶引數 ‘self’、‘host’、‘port’ 的*note 稽核事件: 17bd.
     ‘http.client.connect’。

 -- 方法: HTTPConnection.close ()

     Close the connection to the server.

 -- 屬性: HTTPConnection.blocksize

     Buffer size in bytes for sending a file-like message body.

     在 3.7 版被加入.

As an alternative to using the *note request(): c50. method described
above, you can also send your request step by step, by using the four
functions below.

 -- 方法: HTTPConnection.putrequest (method, url, skip_host=False,
          skip_accept_encoding=False)

     This should be the first call after the connection to the server
     has been made.  It sends a line to the server consisting of the
     'method' string, the 'url' string, and the HTTP version
     (‘HTTP/1.1’).  To disable automatic sending of ‘Host:’ or
     ‘Accept-Encoding:’ headers (for example to accept additional
     content encodings), specify 'skip_host' or 'skip_accept_encoding'
     with non-False values.

 -- 方法: HTTPConnection.putheader (header, argument[, ...])

     Send an RFC 822(5)-style header to the server.  It sends a line to
     the server consisting of the header, a colon and a space, and the
     first argument.  If more arguments are given, continuation lines
     are sent, each consisting of a tab and an argument.

 -- 方法: HTTPConnection.endheaders (message_body=None, *,
          encode_chunked=False)

     Send a blank line to the server, signalling the end of the headers.
     The optional 'message_body' argument can be used to pass a message
     body associated with the request.

     If 'encode_chunked' is ‘True’, the result of each iteration of
     'message_body' will be chunk-encoded as specified in RFC 7230(6),
     Section 3.3.1.  How the data is encoded is dependent on the type of
     'message_body'.  If 'message_body' implements the *note buffer
     interface: 367. the encoding will result in a single chunk.  If
     'message_body' is a *note collections.abc.Iterable: 212a, each
     iteration of 'message_body' will result in a chunk.  If
     'message_body' is a *note file object: 115b, each call to ‘.read()’
     will result in a chunk.  The method automatically signals the end
     of the chunk-encoded data immediately after 'message_body'.

          備註: Due to the chunked encoding specification, empty chunks
          yielded by an iterator body will be ignored by the
          chunk-encoder.  This is to avoid premature termination of the
          read of the request by the target server due to malformed
          encoding.

     在 3.6 版的變更: Added chunked encoding support and the
     'encode_chunked' parameter.

 -- 方法: HTTPConnection.send (data)

     Send data to the server.  This should be used directly only after
     the *note endheaders(): c51. method has been called and before
     *note getresponse(): dae. is called.

     引發一個附帶引數 ‘self’、‘data’ 的*note 稽核事件: 17bd.
     ‘http.client.send’。

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2616.html#section-5.1.2

   (2) https://datatracker.ietf.org/doc/html/rfc2616.html#section-14.23

   (3) https://datatracker.ietf.org/doc/html/rfc2616.html#section-5.1.2

   (4) https://datatracker.ietf.org/doc/html/rfc7231#section-4.3.6

   (5) https://datatracker.ietf.org/doc/html/rfc822.html

   (6) https://datatracker.ietf.org/doc/html/rfc7230.html


File: python.info,  Node: HTTPResponse 物件,  Next: 範例<36>,  Prev: HTTPConnection 物件,  Up: http client --- HTTP 協定用戶端

5.21.10.2 HTTPResponse 物件
...........................

An *note HTTPResponse: 1068. instance wraps the HTTP response from the
server.  It provides access to the request headers and the entity body.
The response is an iterable object and can be used in a with statement.

在 3.5 版的變更: The *note io.BufferedIOBase: 63a. interface is now
implemented and all of its reader operations are supported.

 -- 方法: HTTPResponse.read ([amt])

     Reads and returns the response body, or up to the next 'amt' bytes.

 -- 方法: HTTPResponse.readinto (b)

     Reads up to the next len(b) bytes of the response body into the
     buffer 'b'.  Returns the number of bytes read.

     在 3.3 版被加入.

 -- 方法: HTTPResponse.getheader (name, default=None)

     Return the value of the header 'name', or 'default' if there is no
     header matching 'name'.  If there is more than one header with the
     name 'name', return all of the values joined by ', '.  If 'default'
     is any iterable other than a single string, its elements are
     similarly returned joined by commas.

 -- 方法: HTTPResponse.getheaders ()

     Return a list of (header, value) tuples.

 -- 方法: HTTPResponse.fileno ()

     Return the ‘fileno’ of the underlying socket.

 -- 屬性: HTTPResponse.msg

     A *note http.client.HTTPMessage: 3876. instance containing the
     response headers.  *note http.client.HTTPMessage: 3876. is a
     subclass of *note email.message.Message: 261.

 -- 屬性: HTTPResponse.version

     HTTP protocol version used by server.  10 for HTTP/1.0, 11 for
     HTTP/1.1.

 -- 屬性: HTTPResponse.url

     URL of the resource retrieved, commonly used to determine if a
     redirect was followed.

 -- 屬性: HTTPResponse.headers

     Headers of the response in the form of an *note
     email.message.EmailMessage: 260. instance.

 -- 屬性: HTTPResponse.status

     Status code returned by server.

 -- 屬性: HTTPResponse.reason

     Reason phrase returned by server.

 -- 屬性: HTTPResponse.debuglevel

     A debugging hook.  If *note debuglevel: 389b. is greater than zero,
     messages will be printed to stdout as the response is read and
     parsed.

 -- 屬性: HTTPResponse.closed

     Is ‘True’ if the stream is closed.

 -- 方法: HTTPResponse.geturl ()

     在 3.9 版之後被棄用: Deprecated in favor of *note url: 3898.

 -- 方法: HTTPResponse.info ()

     在 3.9 版之後被棄用: Deprecated in favor of *note headers: 3899.

 -- 方法: HTTPResponse.getcode ()

     在 3.9 版之後被棄用: Deprecated in favor of *note status: 389a.


File: python.info,  Node: 範例<36>,  Next: HTTPMessage 物件,  Prev: HTTPResponse 物件,  Up: http client --- HTTP 協定用戶端

5.21.10.3 範例
..............

Here is an example session that uses the ‘GET’ method:

     >>> import http.client
     >>> conn = http.client.HTTPSConnection("www.python.org")
     >>> conn.request("GET", "/")
     >>> r1 = conn.getresponse()
     >>> print(r1.status, r1.reason)
     200 OK
     >>> data1 = r1.read()  # This will return entire content.
     >>> # The following example demonstrates reading data in chunks.
     >>> conn.request("GET", "/")
     >>> r1 = conn.getresponse()
     >>> while chunk := r1.read(200):
     ...     print(repr(chunk))
     b'<!doctype html>\n<!--[if"...
     ...
     >>> # Example of an invalid request
     >>> conn = http.client.HTTPSConnection("docs.python.org")
     >>> conn.request("GET", "/parrot.spam")
     >>> r2 = conn.getresponse()
     >>> print(r2.status, r2.reason)
     404 Not Found
     >>> data2 = r2.read()
     >>> conn.close()

Here is an example session that uses the ‘HEAD’ method.  Note that the
‘HEAD’ method never returns any data.

     >>> import http.client
     >>> conn = http.client.HTTPSConnection("www.python.org")
     >>> conn.request("HEAD", "/")
     >>> res = conn.getresponse()
     >>> print(res.status, res.reason)
     200 OK
     >>> data = res.read()
     >>> print(len(data))
     0
     >>> data == b''
     True

Here is an example session that uses the ‘POST’ method:

     >>> import http.client, urllib.parse
     >>> params = urllib.parse.urlencode({'@number': 12524, '@type': 'issue', '@action': 'show'})
     >>> headers = {"Content-type": "application/x-www-form-urlencoded",
     ...            "Accept": "text/plain"}
     >>> conn = http.client.HTTPConnection("bugs.python.org")
     >>> conn.request("POST", "", params, headers)
     >>> response = conn.getresponse()
     >>> print(response.status, response.reason)
     302 Found
     >>> data = response.read()
     >>> data
     b'Redirecting to <a href="https://bugs.python.org/issue12524">https://bugs.python.org/issue12524</a>'
     >>> conn.close()

Client side HTTP ‘PUT’ requests are very similar to ‘POST’ requests.
The difference lies only on the server side where HTTP servers will
allow resources to be created via ‘PUT’ requests.  It should be noted
that custom HTTP methods are also handled in *note
urllib.request.Request: f7b. by setting the appropriate method
attribute.  Here is an example session that uses the ‘PUT’ method:

     >>> # This creates an HTTP request
     >>> # with the content of BODY as the enclosed representation
     >>> # for the resource http://localhost:8080/file
     ...
     >>> import http.client
     >>> BODY = "***filecontents***"
     >>> conn = http.client.HTTPConnection("localhost", 8080)
     >>> conn.request("PUT", "/file", BODY)
     >>> response = conn.getresponse()
     >>> print(response.status, response.reason)
     200, OK


File: python.info,  Node: HTTPMessage 物件,  Prev: 範例<36>,  Up: http client --- HTTP 協定用戶端

5.21.10.4 HTTPMessage 物件
..........................

 -- 類別: http.client.HTTPMessage (email.message.Message)

An *note http.client.HTTPMessage: 3876. instance holds the headers from
an HTTP response.  It is implemented using the *note
email.message.Message: 261. class.


File: python.info,  Node: ftplib --- FTP 協定用戶端,  Next: poplib --- POP3 協定用戶端,  Prev: http client --- HTTP 協定用戶端,  Up: 網路協定 Internet protocols 及支援

5.21.11 ‘ftplib’ -- FTP 協定用戶端
----------------------------------

'原始碼：'Lib/ftplib.py(1)

__________________________________________________________________

這個模組定義了 *note FTP: 89f. 類別和一些相關的項目。*note FTP: 89f. 類
別實作了 FTP 協定的用戶端。你可以使用它來編寫能夠執行各種 FTP 自動作業的
Python 程式，例如鏡像 (mirror) 其他 FTP 伺服器。*note urllib.request:
f4. 模組也使用它來處理使用 FTP 的 URL。有關 FTP（檔案傳輸協定）的更多資
訊，請參閱 RFC 959(2)。

預設編碼是 UTF-8，遵循 RFC 2640(3)。

*note Availability: 1c56.: not WASI.

This module does not work or is not available on WebAssembly.  See *note
WebAssembly 平台: 16e6. for more information.

這是一個使用 *note ftplib: 54. 模組的會話範例：

     >>> from ftplib import FTP
     >>> ftp = FTP('ftp.us.debian.org')  # connect to host, default port
     >>> ftp.login()                     # user anonymous, passwd anonymous@
     '230 Login successful.'
     >>> ftp.cwd('debian')               # change into "debian" directory
     '250 Directory successfully changed.'
     >>> ftp.retrlines('LIST')           # list directory contents
     -rw-rw-r--    1 1176     1176         1063 Jun 15 10:18 README
     ...
     drwxr-sr-x    5 1176     1176         4096 Dec 19  2000 pool
     drwxr-sr-x    4 1176     1176         4096 Nov 17  2008 project
     drwxr-xr-x    3 1176     1176         4096 Oct 10  2012 tools
     '226 Directory send OK.'
     >>> with open('README', 'wb') as fp:
     >>>     ftp.retrbinary('RETR README', fp.write)
     '226 Transfer complete.'
     >>> ftp.quit()
     '221 Goodbye.'

* Menu:

* 參考::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/ftplib.py

   (2) https://datatracker.ietf.org/doc/html/rfc959.html

   (3) https://datatracker.ietf.org/doc/html/rfc2640.html


File: python.info,  Node: 參考,  Up: ftplib --- FTP 協定用戶端

5.21.11.1 參考
..............

* Menu:

* FTP 物件::
* FTP_TLS 物件::
* 模組變數::


File: python.info,  Node: FTP 物件,  Next: FTP_TLS 物件,  Up: 參考

5.21.11.2 FTP 物件
..................

 -- 類別: ftplib.FTP (host='', user='', passwd='', acct='',
          timeout=None, source_address=None, *, encoding='utf-8')

     回傳一個新的 *note FTP: 89f. 類別實例。


     參數:

        * ‘host’ (*note str: 3f2.) - 要連接的主機名稱。如果有給定，
          ‘connect(host)’ 會由建構函式來隱式地呼叫。

        * ‘user’ (*note str: 3f2.) - The username to log in with
          (default: ‘'anonymous'’).  如果有給定，‘login(host, passwd,
          acct)’ 會由建構函式來隱式地呼叫。

        * ‘passwd’ (*note str: 3f2.) - The password to use when logging
          in.  If not given, and if 'passwd' is the empty string or
          ‘"-"’, a password will be automatically generated.

        * ‘acct’ (*note str: 3f2.) - Account information to be used for
          the ‘ACCT’ FTP command.  Few systems implement this.  See
          RFC-959(1) for more details.

        * ‘timeout’ (*note float: 2c8.‘ | ’‘None’) - 如 *note connect():
          38a9. 的阻塞操作的超時設定，以秒為單位（預設：使用全域預設超時
          設定）。

        * ‘source_address’ (*note tuple: 322.‘ | ’‘None’) - A 2-tuple
          ‘(host, port)’ for the socket to bind to as its source address
          before connecting.

        * ‘encoding’ (*note str: 3f2.) - The encoding for directories
          and filenames (default: ‘'utf-8'’).

     *note FTP: 89f. 類別支援 *note with: 577. 陳述式，例如：

          >>> from ftplib import FTP
          >>> with FTP("ftp1.at.proftpd.org") as ftp:
          ...     ftp.login()
          ...     ftp.dir()
          ...
          '230 Anonymous login ok, restrictions apply.'
          dr-xr-xr-x   9 ftp      ftp           154 May  6 10:43 .
          dr-xr-xr-x   9 ftp      ftp           154 May  6 10:43 ..
          dr-xr-xr-x   5 ftp      ftp          4096 May  6 10:43 CentOS
          dr-xr-xr-x   3 ftp      ftp            18 Jul 10  2008 Fedora
          >>>

     在 3.2 版的變更: 新增了對 *note with: 577. 陳述式的支援。

     在 3.3 版的變更: 新增 'source_address' 參數。

     在 3.9 版的變更: 如果 'timeout' 參數設定為零，它將引發 *note
     ValueError: 1e7. 以防止建立非阻塞 socket。新增了 'encoding' 參數，
     預設值從 Latin-1 更改為 UTF-8 以遵循 RFC 2640(2)。

     ‘FTP’ 的多個可用方法大致有分為兩個方向：一種用於處理文本檔案 (text
     files)，另一種用於二進位檔案 (binary files)。這些以在文本檔案的
     ‘lines’ 或二進位檔案的 ‘binary’ 前使用的命令命名。

     *note FTP: 89f. 實例具有以下方法：

      -- 方法: set_debuglevel (level)

          將實例的偵錯級別設定為一個 *note int: 23c.，這控制印出的偵錯訊
          息輸出量。

             * ‘0’（預設值）：不產生偵錯輸出。

             * ‘1’：會產生適量的偵錯輸出，通常是每個請求輸出一行。

             * ‘2’ 或更高的值：會產生最大量的偵錯輸出，以日誌紀錄下控制
               連線發送和接收的每個步驟。

      -- 方法: connect (host='', port=0, timeout=None,
               source_address=None)

          連線到給定的主機 (host) 和連接埠 (port)。每個實例只應呼叫此函
          式一次；如果在建立 *note FTP: 89f. 實例時有給定 'host' 引數，
          則不應呼叫它。所有其他的 ‘FTP’ 方法只能在成功建立連線後使用。


          參數:

             * ‘host’ (*note str: 3f2.) - 要連接的主機。

             * ‘port’ (*note int: 23c.) - 要連接的 TCP 連接埠（預設值：
               ‘21’，由 FTP 協定規範指定）。很少需要指定不同的連接埠號碼
               。

             * ‘timeout’ (*note float: 2c8.‘ | ’‘None’) - 連線嘗試的超時
               設定，以秒為單位（預設：全域預設超時設定）。

             * ‘source_address’ (*note tuple: 322.‘ | ’‘None’) - A
               2-tuple ‘(host, port)’ for the socket to bind to as its
               source address before connecting.

          引發一個附帶引數 ‘self’、‘host’、‘port’ 的*note 稽核事件:
          17bd. ‘ftplib.connect’。

          在 3.3 版的變更: 新增 'source_address' 參數。

      -- 方法: getwelcome ()

          回傳伺服器為回應初始連線而發送的歡迎訊息。（此訊息有時會包含與
          使用者相關的免責聲明或幫助資訊。）

      -- 方法: login (user='anonymous', passwd='', acct='')

          在以連線的伺服器上登入。在建立連線後，每個實例只應呼叫此函式一
          次；如果在建立 *note FTP: 89f. 實例時有給定 'host' 和 'user' 引
          數，則不應呼叫它。大多數 FTP 命令僅在用戶端登錄後才允許使用


          參數:

             * ‘user’ (*note str: 3f2.) - The username to log in with
               (default: ‘'anonymous'’).

             * ‘passwd’ (*note str: 3f2.) - The password to use when
               logging in.  If not given, and if 'passwd' is the empty
               string or ‘"-"’, a password will be automatically
               generated.

             * ‘acct’ (*note str: 3f2.) - Account information to be used
               for the ‘ACCT’ FTP command.  Few systems implement this.
               See RFC-959(3) for more details.

      -- 方法: abort ()

          中止正在進行的檔案傳輸。使用它並不是都會成功，但值得一試。

      -- 方法: sendcmd (cmd)

          向伺服器發送一個簡單的命令字串並回傳回應字串。

          引發一個附帶引數 ‘self’、‘cmd’ 的*note 稽核事件: 17bd.
          ‘ftplib.sendcmd’。

      -- 方法: voidcmd (cmd)

          向伺服器發送一個簡單的命令字串並處理回應。如果收到代表成功的回
          應狀態碼（範圍為 200-299 的狀態碼），則回傳回應字串，否則引發
          *note error_reply: 38b0.。

          引發一個附帶引數 ‘self’、‘cmd’ 的*note 稽核事件: 17bd.
          ‘ftplib.sendcmd’。

      -- 方法: retrbinary (cmd, callback, blocksize=8192, rest=None)

          以二進位傳輸模式 (binary transfer mode) 取得檔案。


          參數:

             * ‘cmd’ (*note str: 3f2.) - 一個正確的 ‘RETR’ 指令：‘"RETR
               FILENAME"’。

             * ‘callback’ (*note callable: 27d4.) - 為接收到的每個資料區
               塊呼叫的單一參數可呼叫物件，其單一引數是以 *note bytes:
               1a5. 為形式的資料。

             * ‘blocksize’ (*note int: 23c.) - 在執行實際傳輸時所建立的
               低階 *note socket: d47. 物件上讀取的最大分塊 (chunk) 大小
               。這也對應於將傳遞給 'callback' 的最大資料大小。預設為
               ‘8192’。

             * ‘rest’ (*note int: 23c.) - 一個要發送到伺服器的 ‘REST’ 命
               令。參見 *note transfercmd(): 38b2. 方法之 'rest' 參數的
               文件。

      -- 方法: retrlines (cmd, callback=None)

          在初始化時以 'encoding' 參數指定的編碼來取得檔案或目錄列表。
          'cmd' 要是一個正確的 ‘RETR’ 命令（見 *note retrbinary():
          38b1.）或者一個像 ‘LIST’ 或 ‘NLST’ 的命令（通常只是字串
          ‘'LIST'’ )。 ‘LIST’ 會取得檔案列表和這些檔案的相關資訊。
          ‘NLST’ 取得檔案名稱列表。會為每一行以一個字串引數呼叫
          'callback' 函式，其引數包含已經刪除尾隨 CRLF 的一行。預設的
          'callback' 會將各行印出到 *note sys.stdout: a79.。

      -- 方法: set_pasv (val)

          如果 'val' 為真，則啟用「被動」模式，否則禁用被動模式。被動模
          式預設開啟。

      -- 方法: storbinary (cmd, fp, blocksize=8192, callback=None,
               rest=None)

          以二進位傳輸模式儲存檔案。


          參數:

             * ‘cmd’ (*note str: 3f2.) - 一個正確的 ‘STOR’ 指令：‘"STOR
               FILENAME"’。

             * ‘fp’ (*note file object: 115b.) - 一個檔案物件（以二進位
               模式開啟），在大小為 'blocksize' 的區塊中使用其 *note
               read(): dc2. 方法讀取直到 EOF 來提供要儲存的資料。

             * ‘blocksize’ (*note int: 23c.) - 讀取區塊大小。預設為
               ‘8192’。

             * ‘callback’ (*note callable: 27d4.) - 為發送的每個資料區塊
               來呼叫的單一參數可呼叫物件，其單一引數是以 *note bytes:
               1a5. 為形式的資料。

             * ‘rest’ (*note int: 23c.) - 一個要發送到伺服器的 ‘REST’ 命
               令。參見 *note transfercmd(): 38b2. 方法之 'rest' 參數的
               文件。

          在 3.2 版的變更: 新增 'rest' 參數。

      -- 方法: storlines (cmd, fp, callback=None)

          以行模式 (line mode) 儲存檔案。 'cmd' 應是一個正確的 ‘STOR’ 命
          令（參見 *note storbinary(): 129d.）。使用其 *note readline():
          12bd. 方法從*note 檔案物件: 115b. 'fp' （以二進位模式打開）讀
          取各行、直到 EOF，以提供要儲存的資料。 'callback' 是可選的單參
          數可呼叫物件，於發送後以各行進行呼叫。

      -- 方法: transfercmd (cmd, rest=None)

          通過資料連線啟動傳輸。如果傳輸為主動 (active) 模式，則發送
          ‘EPRT’ 或 ‘PORT’ 命令和 'cmd' 指定的傳輸命令，並接受連線。如果
          伺服器是被動 (passive) 模式，則發送 ‘EPSV’ 或 ‘PASV’ 命令、連
          線、並啟動傳輸命令。無論哪種方式，都是回傳連線的 socket。

          如果有給定可選的 'rest'，一個 ‘REST’ 命令會被發送到伺服器，並
          以 'rest' 作為引數。'rest' 通常是請求檔案的一個位元組偏移量
          (byte offset)，告訴伺服器以請求的偏移量重新開始發送檔案的位元
          組，並跳過初始位元組。但是請注意，*note transfercmd(): 38b2. 方
          法將 'rest' 轉換為帶有初始化時指定的 'encoding' 參數的字串，但
          不會對字串的內容執行檢查。如果伺服器無法識別 ‘REST’ 命令，則會
          引發 *note error_reply: 38b0. 例外。如果發生這種情況，只需在沒
          有 'rest' 引數的情況下呼叫 *note transfercmd(): 38b2.。

      -- 方法: ntransfercmd (cmd, rest=None)

          類似於 *note transfercmd(): 38b2.，但回傳一個帶有資料連線和資
          料預期大小的元組。如果無法計算預期大小，則回傳 ‘None’。 'cmd'
          和 'rest' 與 *note transfercmd(): 38b2. 中的含義相同。

      -- 方法: mlsd (path='', facts=[])

          使用 ‘MLSD’ 命令 ( RFC 3659(4)) 列出標準格式的目錄。如果省略
          'path' 則假定為作用於當前目錄。'facts' 是表示所需資訊類型的字
          串列表（例如 ‘["type", "size", "perm"]’ ）。會回傳一個產生器物
          件，為每個在路徑中找到的檔案生成一個包含兩個元素的元組，第一個
          元素是檔案名稱，第二個元素是包含有關檔案名稱 facts的字典。該字
          典的內容可能受 'facts' 引數限制，但不保證伺服器會回傳所有請求
          的 facts。

          在 3.3 版被加入.

      -- 方法: nlst (argument[, ...])

          回傳由 ‘NLST’ 命令回傳的檔案名稱列表。可選的 'argument' 是要列
          出的目錄（預設為當前伺服器目錄）。多個引數可用於將非標準選項傳
          遞給 ‘NLST’ 命令。

               備註: 如果你的伺服器支援該命令，*note mlsd(): 105c. 會提
               供更好的 API。

      -- 方法: dir (argument[, ...])

          生成由 ‘LIST’ 命令回傳的目錄列表，並將其印出到標準輸出
          (standard output)。可選的 'argument' 是要列出的目錄（預設為當
          前伺服器目錄）。有多個引數可用於將非標準選項傳遞給 ‘LIST’ 命令
          。如果最後一個引數是一個函式，它被用作 *note retrlines():
          38b3. 的 'callback' 函式；預設印出到 *note sys.stdout: a79.。
          此方法回傳 ‘None’。

               備註: 如果你的伺服器支援該命令，*note mlsd(): 105c. 會提
               供更好的 API。

      -- 方法: rename (fromname, toname)

          將伺服器上的檔案 'fromname' 重新命名為 'toname'。

      -- 方法: delete (filename)

          從伺服器中刪除名為 'filename' 的檔案。如果成功，回傳回應的文字
          ，否則引發 *note error_perm: 38b9. 權限錯誤或在其他錯誤發生時
          引發 *note error_reply: 38b0.。

      -- 方法: cwd (pathname)

          設定伺服器上的當前目錄。

      -- 方法: mkd (pathname)

          在伺服器上建立一個新目錄。

      -- 方法: pwd ()

          回傳伺服器上當前目錄的路徑名。

      -- 方法: rmd (dirname)

          刪除伺服器上名為 'dirname' 的目錄。

      -- 方法: size (filename)

          請求伺服器上名為 'filename' 的檔案的大小。成功時，檔案的大小作
          為整數回傳，否則回傳 ‘None’。請注意，‘SIZE’ 命令不是標準化的，
          但被許多常見的伺服器實作支援。

      -- 方法: quit ()

          向伺服器發送 ‘QUIT’ 命令並關閉連線。這是關閉連線的「禮貌」方式
          ，但如果伺服器對 ‘QUIT’ 命令作出錯誤回應，它可能會引發例外。這
          意味著呼叫 *note close(): 38c0. 方法使 *note FTP: 89f. 實例無
          法用於後續呼叫（見下文）。

      -- 方法: close ()

          單方面關閉連線。這不應該使用於已經關閉的連線，例如在成功呼叫
          *note quit(): 38bf. 之後。呼叫後就不應該再次使用 *note FTP:
          89f. 實例（在呼叫 *note close(): 38c0. 或 *note quit(): 38bf.
          後，你不能通過發出另一個 *note login(): 38ac. 方法重新打開連線
          ）。

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc959.html

   (2) https://datatracker.ietf.org/doc/html/rfc2640.html

   (3) https://datatracker.ietf.org/doc/html/rfc959.html

   (4) https://datatracker.ietf.org/doc/html/rfc3659.html


File: python.info,  Node: FTP_TLS 物件,  Next: 模組變數,  Prev: FTP 物件,  Up: 參考

5.21.11.3 FTP_TLS 物件
......................

 -- 類別: ftplib.FTP_TLS (host='', user='', passwd='', acct='', *,
          context=None, timeout=None, source_address=None,
          encoding='utf-8')

     An *note FTP: 89f. subclass which adds TLS support to FTP as
     described in RFC 4217(1).  Connect to port 21 implicitly securing
     the FTP control connection before authenticating.

          備註: The user must explicitly secure the data connection by
          calling the *note prot_p(): 38c2. method.


     參數:

        * ‘host’ (*note str: 3f2.) - 要連接的主機名稱。如果有給定，
          ‘connect(host)’ 會由建構函式來隱式地呼叫。

        * ‘user’ (*note str: 3f2.) - The username to log in with
          (default: ‘'anonymous'’).  如果有給定，‘login(host, passwd,
          acct)’ 會由建構函式來隱式地呼叫。

        * ‘passwd’ (*note str: 3f2.) - The password to use when logging
          in.  If not given, and if 'passwd' is the empty string or
          ‘"-"’, a password will be automatically generated.

        * ‘acct’ (*note str: 3f2.) - Account information to be used for
          the ‘ACCT’ FTP command.  Few systems implement this.  See
          RFC-959(2) for more details.

        * ‘context’ (*note ssl.SSLContext: 276.) - An SSL context object
          which allows bundling SSL configuration options, certificates
          and private keys into a single, potentially long-lived,
          structure.  Please read *note Security considerations: 317d.
          for best practices.

        * ‘timeout’ (*note float: 2c8.‘ | ’‘None’) - 如 *note connect():
          38a9. 的阻塞操作的超時設定，以秒為單位（預設：使用全域預設超時
          設定）。

        * ‘source_address’ (*note tuple: 322.‘ | ’‘None’) - A 2-tuple
          ‘(host, port)’ for the socket to bind to as its source address
          before connecting.

        * ‘encoding’ (*note str: 3f2.) - The encoding for directories
          and filenames (default: ‘'utf-8'’).

     在 3.2 版被加入.

     在 3.3 版的變更: 新增 'source_address' 參數。

     在 3.4 版的變更: 該類別現在支援使用 *note
     ssl.SSLContext.check_hostname: 329f. 和 'Server Name Indication' 進
     行主機名 (hostname) 檢查（參見 *note ssl.HAS_SNI: 32b1.）。

     在 3.9 版的變更: 如果 'timeout' 參數設定為零，它將引發 *note
     ValueError: 1e7. 以防止建立非阻塞 socket。新增了 'encoding' 參數，
     預設值從 Latin-1 更改為 UTF-8 以遵循 RFC 2640(3)。

     在 3.12 版的變更: 已棄用的 'keyfile' 和 'certfile' 參數已被移除。

     這是一個使用 *note FTP_TLS: 8a0. 類別的範例會話：

          >>> ftps = FTP_TLS('ftp.pureftpd.org')
          >>> ftps.login()
          '230 Anonymous user logged in'
          >>> ftps.prot_p()
          '200 Data protection level set to "private"'
          >>> ftps.nlst()
          ['6jack', 'OpenBSD', 'antilink', 'blogbench', 'bsdcam', 'clockspeed', 'djbdns-jedi', 'docs', 'eaccelerator-jedi', 'favicon.ico', 'francotone', 'fugu', 'ignore', 'libpuzzle', 'metalog', 'minidentd', 'misc', 'mysql-udf-global-user-variables', 'php-jenkins-hash', 'php-skein-hash', 'php-webdav', 'phpaudit', 'phpbench', 'pincaster', 'ping', 'posto', 'pub', 'public', 'public_keys', 'pure-ftpd', 'qscan', 'qtc', 'sharedance', 'skycache', 'sound', 'tmp', 'ucarp']

     ‘FTP_TLS’ 類別繼承自 *note FTP: 89f.，並另外定義了這些的方法與屬性
     ：

      -- 屬性: ssl_version

          要使用的 SSL 版本（預設為 *note ssl.PROTOCOL_SSLv23: 32a3.）。

      -- 方法: auth ()

          根據 *note ssl_version: 38c3. 屬性中指定的內容，使用 TLS 或
          SSL 設定安全控制連線。

          在 3.4 版的變更: 該方法現在支援使用 *note
          ssl.SSLContext.check_hostname: 329f. 和 'Server Name
          Indication' 進行主機名檢查（參見 *note ssl.HAS_SNI: 32b1.）。

      -- 方法: ccc ()

          將控制通道恢復為純文本。這對於利用知道如何在不打開固定連接埠的
          情況下使用非安全 (non-secure) FTP 以處理 NAT 的防火牆很有用。

          在 3.3 版被加入.

      -- 方法: prot_p ()

          設定安全資料連線。

      -- 方法: prot_c ()

          設定明文資料 (clear text data) 連線。

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc4217.html

   (2) https://datatracker.ietf.org/doc/html/rfc959.html

   (3) https://datatracker.ietf.org/doc/html/rfc2640.html


File: python.info,  Node: 模組變數,  Prev: FTP_TLS 物件,  Up: 參考

5.21.11.4 模組變數
..................

 -- 例外: ftplib.error_reply

     伺服器收到意外回覆時所引發的例外。

 -- 例外: ftplib.error_temp

     當收到表示暫時錯誤的錯誤碼（400-499 範圍內的回應狀態碼）時引發的例
     外。

 -- 例外: ftplib.error_perm

     當收到表示永久錯誤的錯誤碼（500-599 範圍內的回應狀態碼）時引發的例
     外。

 -- 例外: ftplib.error_proto

     當從伺服器收到不符合檔案傳輸協定回應規範的回覆時引發例外，即 1-5 範
     圍內的數字開頭。

 -- 資料: ftplib.all_errors

     *note FTP: 89f. 實例方法由於 FTP 連線問題（相對於呼叫者的程式錯誤）
     而可能引發的所有例外集合（元組形式）。該集合包括上面列出的四個例外
     以及 *note OSError: 350. 和 *note EOFError: 126c.。

也參考
......

*note netrc: 8d. 模組

     ‘.netrc’ 檔案格式的剖析器。‘.netrc’ 檔案通常被 FTP 用戶端用來在提示
     使用者之前載入使用者身份驗證資訊。


File: python.info,  Node: poplib --- POP3 協定用戶端,  Next: imaplib --- IMAP4 協定客戶端,  Prev: ftplib --- FTP 協定用戶端,  Up: 網路協定 Internet protocols 及支援

5.21.12 ‘poplib’ -- POP3 協定用戶端
-----------------------------------

'原始碼：'Lib/poplib.py(1)

__________________________________________________________________

This module defines a class, *note POP3: 8c9, which encapsulates a
connection to a POP3 server and implements the protocol as defined in
RFC 1939(2).  The *note POP3: 8c9. class supports both the minimal and
optional command sets from RFC 1939(3).  The *note POP3: 8c9. class also
supports the ‘STLS’ command introduced in RFC 2595(4) to enable
encrypted communication on an already established connection.

Additionally, this module provides a class *note POP3_SSL: 8ca, which
provides support for connecting to POP3 servers that use SSL as an
underlying protocol layer.

Note that POP3, though widely supported, is obsolescent.  The
implementation quality of POP3 servers varies widely, and too many are
quite poor.  If your mailserver supports IMAP, you would be better off
using the *note imaplib.IMAP4: 8a8. class, as IMAP servers tend to be
better implemented.

*note Availability: 1c56.: not WASI.

This module does not work or is not available on WebAssembly.  See *note
WebAssembly 平台: 16e6. for more information.

The *note poplib: 9a. module provides two classes:

 -- 類別: poplib.POP3 (host, port=POP3_PORT[, timeout])

     This class implements the actual POP3 protocol.  The connection is
     created when the instance is initialized.  If 'port' is omitted,
     the standard POP3 port (110) is used.  The optional 'timeout'
     parameter specifies a timeout in seconds for the connection attempt
     (if not specified, the global default timeout setting will be
     used).

     引發一個附帶引數 ‘self’、‘host’、‘port’ 的*note 稽核事件: 17bd.
     ‘poplib.connect’。

     引發一個附帶引數 ‘self’、‘line’ 的*note 稽核事件: 17bd.
     ‘poplib.putline’。其中 ‘line’ 為即將傳送給遠端的位元組。

     在 3.9 版的變更: If the 'timeout' parameter is set to be zero, it
     will raise a *note ValueError: 1e7. to prevent the creation of a
     non-blocking socket.

 -- 類別: poplib.POP3_SSL (host, port=POP3_SSL_PORT, *, timeout=None,
          context=None)

     This is a subclass of *note POP3: 8c9. that connects to the server
     over an SSL encrypted socket.  If 'port' is not specified, 995, the
     standard POP3-over-SSL port is used.  'timeout' works as in the
     *note POP3: 8c9. constructor.  'context' is an optional *note
     ssl.SSLContext: 276. object which allows bundling SSL configuration
     options, certificates and private keys into a single (potentially
     long-lived) structure.  Please read *note Security considerations:
     317d. for best practices.

     引發一個附帶引數 ‘self’、‘host’、‘port’ 的*note 稽核事件: 17bd.
     ‘poplib.connect’。

     引發一個附帶引數 ‘self’、‘line’ 的*note 稽核事件: 17bd.
     ‘poplib.putline’。其中 ‘line’ 為即將傳送給遠端的位元組。

     在 3.2 版的變更: 'context' parameter added.

     在 3.4 版的變更: The class now supports hostname check with *note
     ssl.SSLContext.check_hostname: 329f. and 'Server Name Indication'
     (see *note ssl.HAS_SNI: 32b1.).

     在 3.9 版的變更: If the 'timeout' parameter is set to be zero, it
     will raise a *note ValueError: 1e7. to prevent the creation of a
     non-blocking socket.

     在 3.12 版的變更: The deprecated 'keyfile' and 'certfile'
     parameters have been removed.

One exception is defined as an attribute of the *note poplib: 9a.
module:

 -- 例外: poplib.error_proto

     Exception raised on any errors from this module (errors from *note
     socket: b8. module are not caught).  The reason for the exception
     is passed to the constructor as a string.

也參考
......

*note imaplib: 6a. 模組

     The standard Python IMAP module.

關於 Fetchmail 的常見問題(5)

     The FAQ for the ‘fetchmail’ POP/IMAP client collects information on
     POP3 server variations and RFC noncompliance that may be useful if
     you need to write an application based on the POP protocol.

* Menu:

* POP3 物件::
* POP3 範例::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/poplib.py

   (2) https://datatracker.ietf.org/doc/html/rfc1939.html

   (3) https://datatracker.ietf.org/doc/html/rfc1939.html

   (4) https://datatracker.ietf.org/doc/html/rfc2595.html

   (5) http://www.catb.org/~esr/fetchmail/fetchmail-FAQ.html


File: python.info,  Node: POP3 物件,  Next: POP3 範例,  Up: poplib --- POP3 協定用戶端

5.21.12.1 POP3 物件
...................

All POP3 commands are represented by methods of the same name, in
lowercase; most return the response text sent by the server.

A *note POP3: 8c9. instance has the following methods:

 -- 方法: POP3.set_debuglevel (level)

     Set the instance's debugging level.  This controls the amount of
     debugging output printed.  The default, ‘0’, produces no debugging
     output.  A value of ‘1’ produces a moderate amount of debugging
     output, generally a single line per request.  A value of ‘2’ or
     higher produces the maximum amount of debugging output, logging
     each line sent and received on the control connection.

 -- 方法: POP3.getwelcome ()

     Returns the greeting string sent by the POP3 server.

 -- 方法: POP3.capa ()

     Query the server's capabilities as specified in RFC 2449(1).
     Returns a dictionary in the form ‘{'name': ['param'...]}’.

     在 3.4 版被加入.

 -- 方法: POP3.user (username)

     Send user command, response should indicate that a password is
     required.

 -- 方法: POP3.pass_ (password)

     Send password, response includes message count and mailbox size.
     Note: the mailbox on the server is locked until *note quit(): 1134.
     is called.

 -- 方法: POP3.apop (user, secret)

     Use the more secure APOP authentication to log into the POP3
     server.

 -- 方法: POP3.rpop (user)

     Use RPOP authentication (similar to UNIX r-commands) to log into
     POP3 server.

 -- 方法: POP3.stat ()

     Get mailbox status.  The result is a tuple of 2 integers: ‘(message
     count, mailbox size)’.

 -- 方法: POP3.list ([which])

     Request message list, result is in the form ‘(response, ['mesg_num
     octets', ...], octets)’.  If 'which' is set, it is the message to
     list.

 -- 方法: POP3.retr (which)

     Retrieve whole message number 'which', and set its seen flag.
     Result is in form ‘(response, ['line', ...], octets)’.

 -- 方法: POP3.dele (which)

     Flag message number 'which' for deletion.  On most servers
     deletions are not actually performed until QUIT (the major
     exception is Eudora QPOP, which deliberately violates the RFCs by
     doing pending deletes on any disconnect).

 -- 方法: POP3.rset ()

     Remove any deletion marks for the mailbox.

 -- 方法: POP3.noop ()

     Do nothing.  Might be used as a keep-alive.

 -- 方法: POP3.quit ()

     Signoff: commit changes, unlock mailbox, drop connection.

 -- 方法: POP3.top (which, howmuch)

     Retrieves the message header plus 'howmuch' lines of the message
     after the header of message number 'which'.  Result is in form
     ‘(response, ['line', ...], octets)’.

     The POP3 TOP command this method uses, unlike the RETR command,
     doesn't set the message's seen flag; unfortunately, TOP is poorly
     specified in the RFCs and is frequently broken in off-brand
     servers.  Test this method by hand against the POP3 servers you
     will use before trusting it.

 -- 方法: POP3.uidl (which=None)

     Return message digest (unique id) list.  If 'which' is specified,
     result contains the unique id for that message in the form
     ‘'response mesgnum uid’, otherwise result is list ‘(response,
     ['mesgnum uid', ...], octets)’.

 -- 方法: POP3.utf8 ()

     Try to switch to UTF-8 mode.  Returns the server response if
     successful, raises *note error_proto: 1135. if not.  Specified in
     RFC 6856(2).

     在 3.5 版被加入.

 -- 方法: POP3.stls (context=None)

     Start a TLS session on the active connection as specified in RFC
     2595(3).  This is only allowed before user authentication

     'context' parameter is a *note ssl.SSLContext: 276. object which
     allows bundling SSL configuration options, certificates and private
     keys into a single (potentially long-lived) structure.  Please read
     *note Security considerations: 317d. for best practices.

     This method supports hostname checking via *note
     ssl.SSLContext.check_hostname: 329f. and 'Server Name Indication'
     (see *note ssl.HAS_SNI: 32b1.).

     在 3.4 版被加入.

Instances of *note POP3_SSL: 8ca. have no additional methods.  The
interface of this subclass is identical to its parent.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2449.html

   (2) https://datatracker.ietf.org/doc/html/rfc6856.html

   (3) https://datatracker.ietf.org/doc/html/rfc2595.html


File: python.info,  Node: POP3 範例,  Prev: POP3 物件,  Up: poplib --- POP3 協定用戶端

5.21.12.2 POP3 範例
...................

Here is a minimal example (without error checking) that opens a mailbox
and retrieves and prints all messages:

     import getpass, poplib

     M = poplib.POP3('localhost')
     M.user(getpass.getuser())
     M.pass_(getpass.getpass())
     numMessages = len(M.list()[1])
     for i in range(numMessages):
         for j in M.retr(i+1)[1]:
             print(j)

At the end of the module, there is a test section that contains a more
extensive example of usage.


File: python.info,  Node: imaplib --- IMAP4 協定客戶端,  Next: smtplib --- SMTP 協定用戶端,  Prev: poplib --- POP3 協定用戶端,  Up: 網路協定 Internet protocols 及支援

5.21.13 ‘imaplib’ -- IMAP4 協定客戶端
-------------------------------------

'原始碼：'Lib/imaplib.py(1)

__________________________________________________________________

This module defines three classes, *note IMAP4: 8a8, *note IMAP4_SSL:
8a9. and *note IMAP4_stream: 8ab, which encapsulate a connection to an
IMAP4 server and implement a large subset of the IMAP4rev1 client
protocol as defined in RFC 2060(2).  It is backward compatible with
IMAP4 ( RFC 1730(3)) servers, but note that the ‘STATUS’ command is not
supported in IMAP4.

*note Availability: 1c56.: not WASI.

This module does not work or is not available on WebAssembly.  See *note
WebAssembly 平台: 16e6. for more information.

Three classes are provided by the *note imaplib: 6a. module, *note
IMAP4: 8a8. is the base class:

 -- 類別: imaplib.IMAP4 (host='', port=IMAP4_PORT, timeout=None)

     This class implements the actual IMAP4 protocol.  The connection is
     created and protocol version (IMAP4 or IMAP4rev1) is determined
     when the instance is initialized.  If 'host' is not specified, ‘''’
     (the local host) is used.  If 'port' is omitted, the standard IMAP4
     port (143) is used.  The optional 'timeout' parameter specifies a
     timeout in seconds for the connection attempt.  If timeout is not
     given or is ‘None’, the global default socket timeout is used.

     The *note IMAP4: 8a8. class supports the *note with: 577.
     statement.  When used like this, the IMAP4 ‘LOGOUT’ command is
     issued automatically when the ‘with’ statement exits.  E.g.:

          >>> from imaplib import IMAP4
          >>> with IMAP4("domain.org") as M:
          ...     M.noop()
          ...
          ('OK', [b'Nothing Accomplished. d25if65hy903weo.87'])

     在 3.5 版的變更: Support for the *note with: 577. statement was
     added.

     在 3.9 版的變更: 新增 'timeout' 選用參數。

Three exceptions are defined as attributes of the *note IMAP4: 8a8.
class:

 -- 例外: IMAP4.error

     Exception raised on any errors.  The reason for the exception is
     passed to the constructor as a string.

 -- 例外: IMAP4.abort

     IMAP4 server errors cause this exception to be raised.  This is a
     sub-class of *note IMAP4.error: 38e0.  Note that closing the
     instance and instantiating a new one will usually allow recovery
     from this exception.

 -- 例外: IMAP4.readonly

     This exception is raised when a writable mailbox has its status
     changed by the server.  This is a sub-class of *note IMAP4.error:
     38e0.  Some other client now has write permission, and the mailbox
     will need to be re-opened to re-obtain write permission.

There's also a subclass for secure connections:

 -- 類別: imaplib.IMAP4_SSL (host='', port=IMAP4_SSL_PORT, *,
          ssl_context=None, timeout=None)

     This is a subclass derived from *note IMAP4: 8a8. that connects
     over an SSL encrypted socket (to use this class you need a socket
     module that was compiled with SSL support).  If 'host' is not
     specified, ‘''’ (the local host) is used.  If 'port' is omitted,
     the standard IMAP4-over-SSL port (993) is used.  'ssl_context' is a
     *note ssl.SSLContext: 276. object which allows bundling SSL
     configuration options, certificates and private keys into a single
     (potentially long-lived) structure.  Please read *note Security
     considerations: 317d. for best practices.

     The optional 'timeout' parameter specifies a timeout in seconds for
     the connection attempt.  If timeout is not given or is ‘None’, the
     global default socket timeout is used.

     在 3.3 版的變更: 新增 'ssl_context' 參數。

     在 3.4 版的變更: The class now supports hostname check with *note
     ssl.SSLContext.check_hostname: 329f. and 'Server Name Indication'
     (see *note ssl.HAS_SNI: 32b1.).

     在 3.9 版的變更: 新增 'timeout' 選用參數。

     在 3.12 版的變更: The deprecated 'keyfile' and 'certfile'
     parameters have been removed.

The second subclass allows for connections created by a child process:

 -- 類別: imaplib.IMAP4_stream (command)

     This is a subclass derived from *note IMAP4: 8a8. that connects to
     the ‘stdin/stdout’ file descriptors created by passing 'command' to
     ‘subprocess.Popen()’.

The following utility functions are defined:

 -- 函式: imaplib.Internaldate2tuple (datestr)

     Parse an IMAP4 ‘INTERNALDATE’ string and return corresponding local
     time.  The return value is a *note time.struct_time: c91. tuple or
     ‘None’ if the string has wrong format.

 -- 函式: imaplib.Int2AP (num)

     Converts an integer into a bytes representation using characters
     from the set [‘A’ ..  ‘P’].

 -- 函式: imaplib.ParseFlags (flagstr)

     Converts an IMAP4 ‘FLAGS’ response to a tuple of individual flags.

 -- 函式: imaplib.Time2Internaldate (date_time)

     Convert 'date_time' to an IMAP4 ‘INTERNALDATE’ representation.  The
     return value is a string in the form: ‘"DD-Mmm-YYYY HH:MM:SS
     +HHMM"’ (including double-quotes).  The 'date_time' argument can be
     a number (int or float) representing seconds since epoch (as
     returned by *note time.time(): 239.), a 9-tuple representing local
     time an instance of *note time.struct_time: c91. (as returned by
     *note time.localtime(): 1467.), an aware instance of *note
     datetime.datetime: 1b0, or a double-quoted string.  In the last
     case, it is assumed to already be in the correct format.

Note that IMAP4 message numbers change as the mailbox changes; in
particular, after an ‘EXPUNGE’ command performs deletions the remaining
messages are renumbered.  So it is highly advisable to use UIDs instead,
with the UID command.

At the end of the module, there is a test section that contains a more
extensive example of usage.

也參考
......

Documents describing the protocol, sources for servers implementing it,
by the University of Washington's IMAP Information Center can all be
found at ('Source Code') ‘https://github.com/uw-imap/imap’ ('Not
Maintained').

* Menu:

* IMAP4 物件::
* IMAP4 範例::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/imaplib.py

   (2) https://datatracker.ietf.org/doc/html/rfc2060.html

   (3) https://datatracker.ietf.org/doc/html/rfc1730.html


File: python.info,  Node: IMAP4 物件,  Next: IMAP4 範例,  Up: imaplib --- IMAP4 協定客戶端

5.21.13.1 IMAP4 物件
....................

All IMAP4rev1 commands are represented by methods of the same name,
either uppercase or lowercase.

All arguments to commands are converted to strings, except for
‘AUTHENTICATE’, and the last argument to ‘APPEND’ which is passed as an
IMAP4 literal.  If necessary (the string contains IMAP4
protocol-sensitive characters and isn't enclosed with either parentheses
or double quotes) each string is quoted.  However, the 'password'
argument to the ‘LOGIN’ command is always quoted.  If you want to avoid
having an argument string quoted (eg: the 'flags' argument to ‘STORE’)
then enclose the string in parentheses (eg: ‘r'(\Deleted)'’).

Each command returns a tuple: ‘(type, [data, ...])’ where 'type' is
usually ‘'OK'’ or ‘'NO'’, and 'data' is either the text from the command
response, or mandated results from the command.  Each 'data' is either a
‘bytes’, or a tuple.  If a tuple, then the first part is the header of
the response, and the second part contains the data (ie: 'literal'
value).

The 'message_set' options to commands below is a string specifying one
or more messages to be acted upon.  It may be a simple message number
(‘'1'’), a range of message numbers (‘'2:4'’), or a group of
non-contiguous ranges separated by commas (‘'1:3,6:9'’).  A range can
contain an asterisk to indicate an infinite upper bound (‘'3:*'’).

An *note IMAP4: 8a8. instance has the following methods:

 -- 方法: IMAP4.append (mailbox, flags, date_time, message)

     Append 'message' to named mailbox.

 -- 方法: IMAP4.authenticate (mechanism, authobject)

     Authenticate command -- requires response processing.

     'mechanism' specifies which authentication mechanism is to be used
     - it should appear in the instance variable ‘capabilities’ in the
     form ‘AUTH=mechanism’.

     'authobject' must be a callable object:

          data = authobject(response)

     It will be called to process server continuation responses; the
     'response' argument it is passed will be ‘bytes’.  It should return
     ‘bytes’ 'data' that will be base64 encoded and sent to the server.
     It should return ‘None’ if the client abort response ‘*’ should be
     sent instead.

     在 3.5 版的變更: string usernames and passwords are now encoded to
     ‘utf-8’ instead of being limited to ASCII.

 -- 方法: IMAP4.check ()

     Checkpoint mailbox on server.

 -- 方法: IMAP4.close ()

     Close currently selected mailbox.  Deleted messages are removed
     from writable mailbox.  This is the recommended command before
     ‘LOGOUT’.

 -- 方法: IMAP4.copy (message_set, new_mailbox)

     Copy 'message_set' messages onto end of 'new_mailbox'.

 -- 方法: IMAP4.create (mailbox)

     Create new mailbox named 'mailbox'.

 -- 方法: IMAP4.delete (mailbox)

     Delete old mailbox named 'mailbox'.

 -- 方法: IMAP4.deleteacl (mailbox, who)

     Delete the ACLs (remove any rights) set for who on mailbox.

 -- 方法: IMAP4.enable (capability)

     Enable 'capability' (see RFC 5161(1)).  Most capabilities do not
     need to be enabled.  Currently only the ‘UTF8=ACCEPT’ capability is
     supported (see RFC 6855(2)).

     在 3.5 版被加入: The *note enable(): db3. method itself, and RFC
     6855(3) support.

 -- 方法: IMAP4.expunge ()

     Permanently remove deleted items from selected mailbox.  Generates
     an ‘EXPUNGE’ response for each deleted message.  Returned data
     contains a list of ‘EXPUNGE’ message numbers in order received.

 -- 方法: IMAP4.fetch (message_set, message_parts)

     Fetch (parts of) messages.  'message_parts' should be a string of
     message part names enclosed within parentheses, eg: ‘"(UID
     BODY[TEXT])"’.  Returned data are tuples of message part envelope
     and data.

 -- 方法: IMAP4.getacl (mailbox)

     Get the ‘ACL’s for 'mailbox'.  The method is non-standard, but is
     supported by the ‘Cyrus’ server.

 -- 方法: IMAP4.getannotation (mailbox, entry, attribute)

     Retrieve the specified ‘ANNOTATION’s for 'mailbox'.  The method is
     non-standard, but is supported by the ‘Cyrus’ server.

 -- 方法: IMAP4.getquota (root)

     Get the ‘quota’ 'root"s resource usage and limits.  This method is
     part of the IMAP4 QUOTA extension defined in rfc2087.

 -- 方法: IMAP4.getquotaroot (mailbox)

     Get the list of ‘quota’ ‘roots’ for the named 'mailbox'.  This
     method is part of the IMAP4 QUOTA extension defined in rfc2087.

 -- 方法: IMAP4.list ([directory[, pattern]])

     List mailbox names in 'directory' matching 'pattern'.  'directory'
     defaults to the top-level mail folder, and 'pattern' defaults to
     match anything.  Returned data contains a list of ‘LIST’ responses.

 -- 方法: IMAP4.login (user, password)

     Identify the client using a plaintext password.  The 'password'
     will be quoted.

 -- 方法: IMAP4.login_cram_md5 (user, password)

     Force use of ‘CRAM-MD5’ authentication when identifying the client
     to protect the password.  Will only work if the server ‘CAPABILITY’
     response includes the phrase ‘AUTH=CRAM-MD5’.

 -- 方法: IMAP4.logout ()

     Shutdown connection to server.  Returns server ‘BYE’ response.

     在 3.8 版的變更: The method no longer ignores silently arbitrary
     exceptions.

 -- 方法: IMAP4.lsub (directory='""', pattern='*')

     List subscribed mailbox names in directory matching pattern.
     'directory' defaults to the top level directory and 'pattern'
     defaults to match any mailbox.  Returned data are tuples of message
     part envelope and data.

 -- 方法: IMAP4.myrights (mailbox)

     Show my ACLs for a mailbox (i.e.  the rights that I have on
     mailbox).

 -- 方法: IMAP4.namespace ()

     Returns IMAP namespaces as defined in RFC 2342(4).

 -- 方法: IMAP4.noop ()

     Send ‘NOOP’ to server.

 -- 方法: IMAP4.open (host, port, timeout=None)

     Opens socket to 'port' at 'host'.  The optional 'timeout' parameter
     specifies a timeout in seconds for the connection attempt.  If
     timeout is not given or is ‘None’, the global default socket
     timeout is used.  Also note that if the 'timeout' parameter is set
     to be zero, it will raise a *note ValueError: 1e7. to reject
     creating a non-blocking socket.  This method is implicitly called
     by the *note IMAP4: 8a8. constructor.  The connection objects
     established by this method will be used in the *note IMAP4.read():
     38fe, *note IMAP4.readline(): 38ff, *note IMAP4.send(): 3900, and
     *note IMAP4.shutdown(): 3901. methods.  You may override this
     method.

     引發一個附帶引數 ‘self’、‘host’、‘port’ 的*note 稽核事件: 17bd.
     ‘imaplib.open’。

     在 3.9 版的變更: 新增 'timeout' 參數。

 -- 方法: IMAP4.partial (message_num, message_part, start, length)

     Fetch truncated part of a message.  Returned data is a tuple of
     message part envelope and data.

 -- 方法: IMAP4.proxyauth (user)

     Assume authentication as 'user'.  Allows an authorised
     administrator to proxy into any user's mailbox.

 -- 方法: IMAP4.read (size)

     Reads 'size' bytes from the remote server.  You may override this
     method.

 -- 方法: IMAP4.readline ()

     Reads one line from the remote server.  You may override this
     method.

 -- 方法: IMAP4.recent ()

     Prompt server for an update.  Returned data is ‘None’ if no new
     messages, else value of ‘RECENT’ response.

 -- 方法: IMAP4.rename (oldmailbox, newmailbox)

     Rename mailbox named 'oldmailbox' to 'newmailbox'.

 -- 方法: IMAP4.response (code)

     Return data for response 'code' if received, or ‘None’.  Returns
     the given code, instead of the usual type.

 -- 方法: IMAP4.search (charset, criterion[, ...])

     Search mailbox for matching messages.  'charset' may be ‘None’, in
     which case no ‘CHARSET’ will be specified in the request to the
     server.  The IMAP protocol requires that at least one criterion be
     specified; an exception will be raised when the server returns an
     error.  'charset' must be ‘None’ if the ‘UTF8=ACCEPT’ capability
     was enabled using the *note enable(): db3. command.

     範例：

          # M is a connected IMAP4 instance...
          typ, msgnums = M.search(None, 'FROM', '"LDJ"')

          # or:
          typ, msgnums = M.search(None, '(FROM "LDJ")')

 -- 方法: IMAP4.select (mailbox='INBOX', readonly=False)

     Select a mailbox.  Returned data is the count of messages in
     'mailbox' (‘EXISTS’ response).  The default 'mailbox' is ‘'INBOX'’.
     If the 'readonly' flag is set, modifications to the mailbox are not
     allowed.

 -- 方法: IMAP4.send (data)

     Sends ‘data’ to the remote server.  You may override this method.

     引發一個附帶引數 ‘self’、‘data’ 的*note 稽核事件: 17bd.
     ‘imaplib.send’。

 -- 方法: IMAP4.setacl (mailbox, who, what)

     Set an ‘ACL’ for 'mailbox'.  The method is non-standard, but is
     supported by the ‘Cyrus’ server.

 -- 方法: IMAP4.setannotation (mailbox, entry, attribute[, ...])

     Set ‘ANNOTATION’s for 'mailbox'.  The method is non-standard, but
     is supported by the ‘Cyrus’ server.

 -- 方法: IMAP4.setquota (root, limits)

     Set the ‘quota’ 'root"s resource 'limits'.  This method is part of
     the IMAP4 QUOTA extension defined in rfc2087.

 -- 方法: IMAP4.shutdown ()

     Close connection established in ‘open’.  This method is implicitly
     called by *note IMAP4.logout(): 38f9.  You may override this
     method.

 -- 方法: IMAP4.socket ()

     Returns socket instance used to connect to server.

 -- 方法: IMAP4.sort (sort_criteria, charset, search_criterion[, ...])

     The ‘sort’ command is a variant of ‘search’ with sorting semantics
     for the results.  Returned data contains a space separated list of
     matching message numbers.

     Sort has two arguments before the 'search_criterion' argument(s); a
     parenthesized list of 'sort_criteria', and the searching 'charset'.
     Note that unlike ‘search’, the searching 'charset' argument is
     mandatory.  There is also a ‘uid sort’ command which corresponds to
     ‘sort’ the way that ‘uid search’ corresponds to ‘search’.  The
     ‘sort’ command first searches the mailbox for messages that match
     the given searching criteria using the charset argument for the
     interpretation of strings in the searching criteria.  It then
     returns the numbers of matching messages.

     This is an ‘IMAP4rev1’ extension command.

 -- 方法: IMAP4.starttls (ssl_context=None)

     Send a ‘STARTTLS’ command.  The 'ssl_context' argument is optional
     and should be a *note ssl.SSLContext: 276. object.  This will
     enable encryption on the IMAP connection.  Please read *note
     Security considerations: 317d. for best practices.

     在 3.2 版被加入.

     在 3.4 版的變更: The method now supports hostname check with *note
     ssl.SSLContext.check_hostname: 329f. and 'Server Name Indication'
     (see *note ssl.HAS_SNI: 32b1.).

 -- 方法: IMAP4.status (mailbox, names)

     Request named status conditions for 'mailbox'.

 -- 方法: IMAP4.store (message_set, command, flag_list)

     Alters flag dispositions for messages in mailbox.  'command' is
     specified by section 6.4.6 of RFC 2060(5) as being one of "FLAGS",
     "+FLAGS", or "-FLAGS", optionally with a suffix of ".SILENT".

     For example, to set the delete flag on all messages:

          typ, data = M.search(None, 'ALL')
          for num in data[0].split():
             M.store(num, '+FLAGS', '\\Deleted')
          M.expunge()

          備註: Creating flags containing ']' (for example: "[test]")
          violates RFC 3501(6) (the IMAP protocol).  However, imaplib
          has historically allowed creation of such tags, and popular
          IMAP servers, such as Gmail, accept and produce such flags.
          There are non-Python programs which also create such tags.
          Although it is an RFC violation and IMAP clients and servers
          are supposed to be strict, imaplib still continues to allow
          such tags to be created for backward compatibility reasons,
          and as of Python 3.6, handles them if they are sent from the
          server, since this improves real-world compatibility.

 -- 方法: IMAP4.subscribe (mailbox)

     Subscribe to new mailbox.

 -- 方法: IMAP4.thread (threading_algorithm, charset, search_criterion[,
          ...])

     The ‘thread’ command is a variant of ‘search’ with threading
     semantics for the results.  Returned data contains a space
     separated list of thread members.

     Thread members consist of zero or more messages numbers, delimited
     by spaces, indicating successive parent and child.

     Thread has two arguments before the 'search_criterion' argument(s);
     a 'threading_algorithm', and the searching 'charset'.  Note that
     unlike ‘search’, the searching 'charset' argument is mandatory.
     There is also a ‘uid thread’ command which corresponds to ‘thread’
     the way that ‘uid search’ corresponds to ‘search’.  The ‘thread’
     command first searches the mailbox for messages that match the
     given searching criteria using the 'charset' argument for the
     interpretation of strings in the searching criteria.  It then
     returns the matching messages threaded according to the specified
     threading algorithm.

     This is an ‘IMAP4rev1’ extension command.

 -- 方法: IMAP4.uid (command, arg[, ...])

     Execute command args with messages identified by UID, rather than
     message number.  Returns response appropriate to command.  At least
     one argument must be supplied; if none are provided, the server
     will return an error and an exception will be raised.

 -- 方法: IMAP4.unsubscribe (mailbox)

     Unsubscribe from old mailbox.

 -- 方法: IMAP4.unselect ()

     *note imaplib.IMAP4.unselect(): 8ac. frees server's resources
     associated with the selected mailbox and returns the server to the
     authenticated state.  This command performs the same actions as
     *note imaplib.IMAP4.close(): 8ad, except that no messages are
     permanently removed from the currently selected mailbox.

     在 3.9 版被加入.

 -- 方法: IMAP4.xatom (name[, ...])

     Allow simple extension commands notified by server in ‘CAPABILITY’
     response.

The following attributes are defined on instances of *note IMAP4: 8a8.:

 -- 屬性: IMAP4.PROTOCOL_VERSION

     The most recent supported protocol in the ‘CAPABILITY’ response
     from the server.

 -- 屬性: IMAP4.debug

     Integer value to control debugging output.  The initialize value is
     taken from the module variable ‘Debug’.  Values greater than three
     trace each command.

 -- 屬性: IMAP4.utf8_enabled

     Boolean value that is normally ‘False’, but is set to ‘True’ if an
     *note enable(): db3. command is successfully issued for the
     ‘UTF8=ACCEPT’ capability.

     在 3.5 版被加入.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc5161.html

   (2) https://datatracker.ietf.org/doc/html/rfc6855.html

   (3) https://datatracker.ietf.org/doc/html/rfc6855.html

   (4) https://datatracker.ietf.org/doc/html/rfc2342.html

   (5) https://datatracker.ietf.org/doc/html/rfc2060.html

   (6) https://datatracker.ietf.org/doc/html/rfc3501.html


File: python.info,  Node: IMAP4 範例,  Prev: IMAP4 物件,  Up: imaplib --- IMAP4 協定客戶端

5.21.13.2 IMAP4 範例
....................

Here is a minimal example (without error checking) that opens a mailbox
and retrieves and prints all messages:

     import getpass, imaplib

     M = imaplib.IMAP4(host='example.org')
     M.login(getpass.getuser(), getpass.getpass())
     M.select()
     typ, data = M.search(None, 'ALL')
     for num in data[0].split():
         typ, data = M.fetch(num, '(RFC822)')
         print('Message %s\n%s\n' % (num, data[0][1]))
     M.close()
     M.logout()


File: python.info,  Node: smtplib --- SMTP 協定用戶端,  Next: uuid --- RFC 4122 定義的 UUID 物件,  Prev: imaplib --- IMAP4 協定客戶端,  Up: 網路協定 Internet protocols 及支援

5.21.14 ‘smtplib’ -- SMTP 協定用戶端
------------------------------------

'原始碼：'Lib/smtplib.py(1)

__________________________________________________________________

The *note smtplib: b7. module defines an SMTP client session object that
can be used to send mail to any internet machine with an SMTP or ESMTP
listener daemon.  For details of SMTP and ESMTP operation, consult RFC
821(2) (Simple Mail Transfer Protocol) and RFC 1869(3) (SMTP Service
Extensions).

*note Availability: 1c56.: not WASI.

This module does not work or is not available on WebAssembly.  See *note
WebAssembly 平台: 16e6. for more information.

 -- 類別: smtplib.SMTP (host='', port=0, local_hostname=None[, timeout],
          source_address=None)

     An *note SMTP: 8d1. instance encapsulates an SMTP connection.  It
     has methods that support a full repertoire of SMTP and ESMTP
     operations.  If the optional 'host' and 'port' parameters are
     given, the SMTP *note connect(): 18cf. method is called with those
     parameters during initialization.  If specified, 'local_hostname'
     is used as the FQDN of the local host in the HELO/EHLO command.
     Otherwise, the local hostname is found using *note
     socket.getfqdn(): 167f.  If the *note connect(): 18cf. call returns
     anything other than a success code, an *note SMTPConnectError:
     391b. is raised.  The optional 'timeout' parameter specifies a
     timeout in seconds for blocking operations like the connection
     attempt (if not specified, the global default timeout setting will
     be used).  If the timeout expires, *note TimeoutError: 7d9. is
     raised.  The optional 'source_address' parameter allows binding to
     some specific source address in a machine with multiple network
     interfaces, and/or to some specific source TCP port.  It takes a
     2-tuple ‘(host, port)’, for the socket to bind to as its source
     address before connecting.  If omitted (or if 'host' or 'port' are
     ‘''’ and/or ‘0’ respectively) the OS default behavior will be used.

     For normal use, you should only require the initialization/connect,
     *note sendmail(): dfb, and *note SMTP.quit(): 391c. methods.  An
     example is included below.

     The *note SMTP: 8d1. class supports the *note with: 577. statement.
     When used like this, the SMTP ‘QUIT’ command is issued
     automatically when the ‘with’ statement exits.  E.g.:

          >>> from smtplib import SMTP
          >>> with SMTP("domain.org") as smtp:
          ...     smtp.noop()
          ...
          (250, b'Ok')
          >>>

     所有指令都會引發一個附帶引數 ‘self’、‘data’ 的*note 稽核事件: 17bd.
     ‘smtplib.SMTP.send’，其中 ‘data’ 為即將傳送至遠端的位元組。

     在 3.3 版的變更: Support for the *note with: 577. statement was
     added.

     在 3.3 版的變更: 新增 source_address 引數。

     在 3.5 版被加入: The SMTPUTF8 extension ( RFC 6531(4)) is now
     supported.

     在 3.9 版的變更: If the 'timeout' parameter is set to be zero, it
     will raise a *note ValueError: 1e7. to prevent the creation of a
     non-blocking socket.

 -- 類別: smtplib.SMTP_SSL (host='', port=0, local_hostname=None, *[,
          timeout], context=None, source_address=None)

     An *note SMTP_SSL: 8d2. instance behaves exactly the same as
     instances of *note SMTP: 8d1.  *note SMTP_SSL: 8d2. should be used
     for situations where SSL is required from the beginning of the
     connection and using ‘starttls()’ is not appropriate.  If 'host' is
     not specified, the local host is used.  If 'port' is zero, the
     standard SMTP-over-SSL port (465) is used.  The optional arguments
     'local_hostname', 'timeout' and 'source_address' have the same
     meaning as they do in the *note SMTP: 8d1. class.  'context', also
     optional, can contain a *note SSLContext: 276. and allows
     configuring various aspects of the secure connection.  Please read
     *note Security considerations: 317d. for best practices.

     在 3.3 版的變更: 新增 'context'。

     在 3.3 版的變更: 新增 'source_address' 引數。

     在 3.4 版的變更: The class now supports hostname check with *note
     ssl.SSLContext.check_hostname: 329f. and 'Server Name Indication'
     (see *note ssl.HAS_SNI: 32b1.).

     在 3.9 版的變更: If the 'timeout' parameter is set to be zero, it
     will raise a *note ValueError: 1e7. to prevent the creation of a
     non-blocking socket

     在 3.12 版的變更: The deprecated 'keyfile' and 'certfile'
     parameters have been removed.

 -- 類別: smtplib.LMTP (host='', port=LMTP_PORT, local_hostname=None,
          source_address=None[, timeout])

     The LMTP protocol, which is very similar to ESMTP, is heavily based
     on the standard SMTP client.  It's common to use Unix sockets for
     LMTP, so our ‘connect()’ method must support that as well as a
     regular host:port server.  The optional arguments 'local_hostname'
     and 'source_address' have the same meaning as they do in the *note
     SMTP: 8d1. class.  To specify a Unix socket, you must use an
     absolute path for 'host', starting with a '/'.

     Authentication is supported, using the regular SMTP mechanism.
     When using a Unix socket, LMTP generally don't support or require
     any authentication, but your mileage might vary.

     在 3.9 版的變更: 新增 'timeout' 選用參數。

A nice selection of exceptions is defined as well:

 -- 例外: smtplib.SMTPException

     Subclass of *note OSError: 350. that is the base exception class
     for all the other exceptions provided by this module.

     在 3.4 版的變更: SMTPException became subclass of *note OSError:
     350.

 -- 例外: smtplib.SMTPServerDisconnected

     This exception is raised when the server unexpectedly disconnects,
     or when an attempt is made to use the *note SMTP: 8d1. instance
     before connecting it to a server.

 -- 例外: smtplib.SMTPResponseException

     Base class for all exceptions that include an SMTP error code.
     These exceptions are generated in some instances when the SMTP
     server returns an error code.  The error code is stored in the
     ‘smtp_code’ attribute of the error, and the ‘smtp_error’ attribute
     is set to the error message.

 -- 例外: smtplib.SMTPSenderRefused

     Sender address refused.  In addition to the attributes set by on
     all *note SMTPResponseException: 391e. exceptions, this sets
     'sender' to the string that the SMTP server refused.

 -- 例外: smtplib.SMTPRecipientsRefused

     All recipient addresses refused.  The errors for each recipient are
     accessible through the attribute ‘recipients’, which is a
     dictionary of exactly the same sort as *note SMTP.sendmail(): dfb.
     returns.

 -- 例外: smtplib.SMTPDataError

     The SMTP server refused to accept the message data.

 -- 例外: smtplib.SMTPConnectError

     Error occurred during establishment of a connection with the
     server.

 -- 例外: smtplib.SMTPHeloError

     The server refused our ‘HELO’ message.

 -- 例外: smtplib.SMTPNotSupportedError

     The command or option attempted is not supported by the server.

     在 3.5 版被加入.

 -- 例外: smtplib.SMTPAuthenticationError

     SMTP authentication went wrong.  Most probably the server didn't
     accept the username/password combination provided.

也參考
......

RFC 821(5) - Simple Mail Transfer Protocol

     Protocol definition for SMTP. This document covers the model,
     operating procedure, and protocol details for SMTP.

RFC 1869(6) - SMTP Service Extensions

     Definition of the ESMTP extensions for SMTP. This describes a
     framework for extending SMTP with new commands, supporting dynamic
     discovery of the commands provided by the server, and defines a few
     additional commands.

* Menu:

* SMTP 物件::
* SMTP 範例::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/smtplib.py

   (2) https://datatracker.ietf.org/doc/html/rfc821.html

   (3) https://datatracker.ietf.org/doc/html/rfc1869.html

   (4) https://datatracker.ietf.org/doc/html/rfc6531.html

   (5) https://datatracker.ietf.org/doc/html/rfc821.html

   (6) https://datatracker.ietf.org/doc/html/rfc1869.html


File: python.info,  Node: SMTP 物件,  Next: SMTP 範例,  Up: smtplib --- SMTP 協定用戶端

5.21.14.1 SMTP 物件
...................

An *note SMTP: 8d1. instance has the following methods:

 -- 方法: SMTP.set_debuglevel (level)

     Set the debug output level.  A value of 1 or ‘True’ for 'level'
     results in debug messages for connection and for all messages sent
     to and received from the server.  A value of 2 for 'level' results
     in these messages being timestamped.

     在 3.5 版的變更: Added debuglevel 2.

 -- 方法: SMTP.docmd (cmd, args='')

     Send a command 'cmd' to the server.  The optional argument 'args'
     is simply concatenated to the command, separated by a space.

     This returns a 2-tuple composed of a numeric response code and the
     actual response line (multiline responses are joined into one long
     line.)

     In normal operation it should not be necessary to call this method
     explicitly.  It is used to implement other methods and may be
     useful for testing private extensions.

     If the connection to the server is lost while waiting for the
     reply, *note SMTPServerDisconnected: 391d. will be raised.

 -- 方法: SMTP.connect (host='localhost', port=0)

     Connect to a host on a given port.  The defaults are to connect to
     the local host at the standard SMTP port (25).  If the hostname
     ends with a colon (‘':'’) followed by a number, that suffix will be
     stripped off and the number interpreted as the port number to use.
     This method is automatically invoked by the constructor if a host
     is specified during instantiation.  Returns a 2-tuple of the
     response code and message sent by the server in its connection
     response.

     引發一個附帶引數 ‘self’、‘host’、‘port’ 的*note 稽核事件: 17bd.
     ‘smtplib.connect’。

 -- 方法: SMTP.helo (name='')

     Identify yourself to the SMTP server using ‘HELO’.  The hostname
     argument defaults to the fully qualified domain name of the local
     host.  The message returned by the server is stored as the
     ‘helo_resp’ attribute of the object.

     In normal operation it should not be necessary to call this method
     explicitly.  It will be implicitly called by the *note sendmail():
     dfb. when necessary.

 -- 方法: SMTP.ehlo (name='')

     Identify yourself to an ESMTP server using ‘EHLO’.  The hostname
     argument defaults to the fully qualified domain name of the local
     host.  Examine the response for ESMTP option and store them for use
     by *note has_extn(): 3929.  Also sets several informational
     attributes: the message returned by the server is stored as the
     ‘ehlo_resp’ attribute, ‘does_esmtp’ is set to ‘True’ or ‘False’
     depending on whether the server supports ESMTP, and
     ‘esmtp_features’ will be a dictionary containing the names of the
     SMTP service extensions this server supports, and their parameters
     (if any).

     Unless you wish to use *note has_extn(): 3929. before sending mail,
     it should not be necessary to call this method explicitly.  It will
     be implicitly called by *note sendmail(): dfb. when necessary.

 -- 方法: SMTP.ehlo_or_helo_if_needed ()

     This method calls *note ehlo(): 3928. and/or *note helo(): 3927. if
     there has been no previous ‘EHLO’ or ‘HELO’ command this session.
     It tries ESMTP ‘EHLO’ first.

     *note SMTPHeloError: 3922.

          The server didn't reply properly to the ‘HELO’ greeting.

 -- 方法: SMTP.has_extn (name)

     Return *note True: bb4. if 'name' is in the set of SMTP service
     extensions returned by the server, *note False: adb. otherwise.
     Case is ignored.

 -- 方法: SMTP.verify (address)

     Check the validity of an address on this server using SMTP ‘VRFY’.
     Returns a tuple consisting of code 250 and a full RFC 822(1)
     address (including human name) if the user address is valid.
     Otherwise returns an SMTP error code of 400 or greater and an error
     string.

          備註: Many sites disable SMTP ‘VRFY’ in order to foil
          spammers.

 -- 方法: SMTP.login (user, password, *, initial_response_ok=True)

     Log in on an SMTP server that requires authentication.  The
     arguments are the username and the password to authenticate with.
     If there has been no previous ‘EHLO’ or ‘HELO’ command this
     session, this method tries ESMTP ‘EHLO’ first.  This method will
     return normally if the authentication was successful, or may raise
     the following exceptions:

     *note SMTPHeloError: 3922.

          The server didn't reply properly to the ‘HELO’ greeting.

     *note SMTPAuthenticationError: 3923.

          The server didn't accept the username/password combination.

     *note SMTPNotSupportedError: 18ce.

          The ‘AUTH’ command is not supported by the server.

     *note SMTPException: f43.

          No suitable authentication method was found.

     Each of the authentication methods supported by *note smtplib: b7.
     are tried in turn if they are advertised as supported by the
     server.  See *note auth(): df9. for a list of supported
     authentication methods.  'initial_response_ok' is passed through to
     *note auth(): df9.

     Optional keyword argument 'initial_response_ok' specifies whether,
     for authentication methods that support it, an "initial response"
     as specified in RFC 4954(2) can be sent along with the ‘AUTH’
     command, rather than requiring a challenge/response.

     在 3.5 版的變更: *note SMTPNotSupportedError: 18ce. may be raised,
     and the 'initial_response_ok' parameter was added.

 -- 方法: SMTP.auth (mechanism, authobject, *, initial_response_ok=True)

     Issue an ‘SMTP’ ‘AUTH’ command for the specified authentication
     'mechanism', and handle the challenge response via 'authobject'.

     'mechanism' specifies which authentication mechanism is to be used
     as argument to the ‘AUTH’ command; the valid values are those
     listed in the ‘auth’ element of ‘esmtp_features’.

     'authobject' must be a callable object taking an optional single
     argument:

          data = authobject(challenge=None)

     If optional keyword argument 'initial_response_ok' is true,
     ‘authobject()’ will be called first with no argument.  It can
     return the RFC 4954(3) "initial response" ASCII ‘str’ which will be
     encoded and sent with the ‘AUTH’ command as below.  If the
     ‘authobject()’ does not support an initial response (e.g.  because
     it requires a challenge), it should return ‘None’ when called with
     ‘challenge=None’.  If 'initial_response_ok' is false, then
     ‘authobject()’ will not be called first with ‘None’.

     If the initial response check returns ‘None’, or if
     'initial_response_ok' is false, ‘authobject()’ will be called to
     process the server's challenge response; the 'challenge' argument
     it is passed will be a ‘bytes’.  It should return ASCII ‘str’
     'data' that will be base64 encoded and sent to the server.

     The ‘SMTP’ class provides ‘authobjects’ for the ‘CRAM-MD5’,
     ‘PLAIN’, and ‘LOGIN’ mechanisms; they are named
     ‘SMTP.auth_cram_md5’, ‘SMTP.auth_plain’, and ‘SMTP.auth_login’
     respectively.  They all require that the ‘user’ and ‘password’
     properties of the ‘SMTP’ instance are set to appropriate values.

     User code does not normally need to call ‘auth’ directly, but can
     instead call the *note login(): 392c. method, which will try each
     of the above mechanisms in turn, in the order listed.  ‘auth’ is
     exposed to facilitate the implementation of authentication methods
     not (or not yet) supported directly by *note smtplib: b7.

     在 3.5 版被加入.

 -- 方法: SMTP.starttls (*, context=None)

     Put the SMTP connection in TLS (Transport Layer Security) mode.
     All SMTP commands that follow will be encrypted.  You should then
     call *note ehlo(): 3928. again.

     If 'keyfile' and 'certfile' are provided, they are used to create
     an *note ssl.SSLContext: 276.

     Optional 'context' parameter is an *note ssl.SSLContext: 276.
     object; This is an alternative to using a keyfile and a certfile
     and if specified both 'keyfile' and 'certfile' should be ‘None’.

     If there has been no previous ‘EHLO’ or ‘HELO’ command this
     session, this method tries ESMTP ‘EHLO’ first.

     在 3.12 版的變更: The deprecated 'keyfile' and 'certfile'
     parameters have been removed.

     *note SMTPHeloError: 3922.

          The server didn't reply properly to the ‘HELO’ greeting.

     *note SMTPNotSupportedError: 18ce.

          The server does not support the STARTTLS extension.

     *note RuntimeError: 179.

          SSL/TLS support is not available to your Python interpreter.

     在 3.3 版的變更: 新增 'context'。

     在 3.4 版的變更: The method now supports hostname check with
     ‘SSLContext.check_hostname’ and 'Server Name Indicator' (see *note
     HAS_SNI: 32b1.).

     在 3.5 版的變更: The error raised for lack of STARTTLS support is
     now the *note SMTPNotSupportedError: 18ce. subclass instead of the
     base *note SMTPException: f43.

 -- 方法: SMTP.sendmail (from_addr, to_addrs, msg, mail_options=(),
          rcpt_options=())

     Send mail.  The required arguments are an RFC 822(4) from-address
     string, a list of RFC 822(5) to-address strings (a bare string will
     be treated as a list with 1 address), and a message string.  The
     caller may pass a list of ESMTP options (such as ‘8bitmime’) to be
     used in ‘MAIL FROM’ commands as 'mail_options'.  ESMTP options
     (such as ‘DSN’ commands) that should be used with all ‘RCPT’
     commands can be passed as 'rcpt_options'.  (If you need to use
     different ESMTP options to different recipients you have to use the
     low-level methods such as ‘mail()’, ‘rcpt()’ and ‘data()’ to send
     the message.)

          備註: The 'from_addr' and 'to_addrs' parameters are used to
          construct the message envelope used by the transport agents.
          ‘sendmail’ does not modify the message headers in any way.

     'msg' may be a string containing characters in the ASCII range, or
     a byte string.  A string is encoded to bytes using the ascii codec,
     and lone ‘\r’ and ‘\n’ characters are converted to ‘\r\n’
     characters.  A byte string is not modified.

     If there has been no previous ‘EHLO’ or ‘HELO’ command this
     session, this method tries ESMTP ‘EHLO’ first.  If the server does
     ESMTP, message size and each of the specified options will be
     passed to it (if the option is in the feature set the server
     advertises).  If ‘EHLO’ fails, ‘HELO’ will be tried and ESMTP
     options suppressed.

     This method will return normally if the mail is accepted for at
     least one recipient.  Otherwise it will raise an exception.  That
     is, if this method does not raise an exception, then someone should
     get your mail.  If this method does not raise an exception, it
     returns a dictionary, with one entry for each recipient that was
     refused.  Each entry contains a tuple of the SMTP error code and
     the accompanying error message sent by the server.

     If ‘SMTPUTF8’ is included in 'mail_options', and the server
     supports it, 'from_addr' and 'to_addrs' may contain non-ASCII
     characters.

     This method may raise the following exceptions:

     *note SMTPRecipientsRefused: 3920.

          All recipients were refused.  Nobody got the mail.  The
          ‘recipients’ attribute of the exception object is a dictionary
          with information about the refused recipients (like the one
          returned when at least one recipient was accepted).

     *note SMTPHeloError: 3922.

          The server didn't reply properly to the ‘HELO’ greeting.

     *note SMTPSenderRefused: 391f.

          The server didn't accept the 'from_addr'.

     *note SMTPDataError: 3921.

          The server replied with an unexpected error code (other than a
          refusal of a recipient).

     *note SMTPNotSupportedError: 18ce.

          ‘SMTPUTF8’ was given in the 'mail_options' but is not
          supported by the server.

     Unless otherwise noted, the connection will be open even after an
     exception is raised.

     在 3.2 版的變更: 'msg' may be a byte string.

     在 3.5 版的變更: ‘SMTPUTF8’ support added, and *note
     SMTPNotSupportedError: 18ce. may be raised if ‘SMTPUTF8’ is
     specified but the server does not support it.

 -- 方法: SMTP.send_message (msg, from_addr=None, to_addrs=None,
          mail_options=(), rcpt_options=())

     This is a convenience method for calling *note sendmail(): dfb.
     with the message represented by an *note email.message.Message:
     261. object.  The arguments have the same meaning as for *note
     sendmail(): dfb, except that 'msg' is a ‘Message’ object.

     If 'from_addr' is ‘None’ or 'to_addrs' is ‘None’, ‘send_message’
     fills those arguments with addresses extracted from the headers of
     'msg' as specified in RFC 5322(6): 'from_addr' is set to the
     ‘Sender’ field if it is present, and otherwise to the ‘From’ field.
     'to_addrs' combines the values (if any) of the ‘To’, ‘Cc’, and
     ‘Bcc’ fields from 'msg'.  If exactly one set of ‘Resent-*’ headers
     appear in the message, the regular headers are ignored and the
     ‘Resent-*’ headers are used instead.  If the message contains more
     than one set of ‘Resent-*’ headers, a *note ValueError: 1e7. is
     raised, since there is no way to unambiguously detect the most
     recent set of ‘Resent-’ headers.

     ‘send_message’ serializes 'msg' using *note BytesGenerator: 1167.
     with ‘\r\n’ as the 'linesep', and calls *note sendmail(): dfb. to
     transmit the resulting message.  Regardless of the values of
     'from_addr' and 'to_addrs', ‘send_message’ does not transmit any
     ‘Bcc’ or ‘Resent-Bcc’ headers that may appear in 'msg'.  If any of
     the addresses in 'from_addr' and 'to_addrs' contain non-ASCII
     characters and the server does not advertise ‘SMTPUTF8’ support, an
     ‘SMTPNotSupported’ error is raised.  Otherwise the ‘Message’ is
     serialized with a clone of its *note policy: 46. with the *note
     utf8: d9e. attribute set to ‘True’, and ‘SMTPUTF8’ and
     ‘BODY=8BITMIME’ are added to 'mail_options'.

     在 3.2 版被加入.

     在 3.5 版被加入: Support for internationalized addresses
     (‘SMTPUTF8’).

 -- 方法: SMTP.quit ()

     Terminate the SMTP session and close the connection.  Return the
     result of the SMTP ‘QUIT’ command.

Low-level methods corresponding to the standard SMTP/ESMTP commands
‘HELP’, ‘RSET’, ‘NOOP’, ‘MAIL’, ‘RCPT’, and ‘DATA’ are also supported.
Normally these do not need to be called directly, so they are not
documented here.  For details, consult the module code.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc822.html

   (2) https://datatracker.ietf.org/doc/html/rfc4954.html

   (3) https://datatracker.ietf.org/doc/html/rfc4954.html

   (4) https://datatracker.ietf.org/doc/html/rfc822.html

   (5) https://datatracker.ietf.org/doc/html/rfc822.html

   (6) https://datatracker.ietf.org/doc/html/rfc5322.html


File: python.info,  Node: SMTP 範例,  Prev: SMTP 物件,  Up: smtplib --- SMTP 協定用戶端

5.21.14.2 SMTP 範例
...................

This example prompts the user for addresses needed in the message
envelope ('To' and 'From' addresses), and the message to be delivered.
Note that the headers to be included with the message must be included
in the message as entered; this example doesn't do any processing of the
RFC 822(1) headers.  In particular, the 'To' and 'From' addresses must
be included in the message headers explicitly:

     import smtplib

     def prompt(title):
         return input(title).strip()

     from_addr = prompt("From: ")
     to_addrs  = prompt("To: ").split()
     print("Enter message, end with ^D (Unix) or ^Z (Windows):")

     # Add the From: and To: headers at the start!
     lines = [f"From: {from_addr}", f"To: {', '.join(to_addrs)}", ""]
     while True:
         try:
             line = input()
         except EOFError:
             break
         else:
             lines.append(line)

     msg = "\r\n".join(lines)
     print("Message length is", len(msg))

     server = smtplib.SMTP("localhost")
     server.set_debuglevel(1)
     server.sendmail(from_addr, to_addrs, msg)
     server.quit()

     備註: In general, you will want to use the *note email: 32.
     package's features to construct an email message, which you can
     then send via *note send_message(): dfc.; see *note email：範例:
     ee0.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc822.html


File: python.info,  Node: uuid --- RFC 4122 定義的 UUID 物件,  Next: socketserver --- 用於網路伺服器的框架,  Prev: smtplib --- SMTP 協定用戶端,  Up: 網路協定 Internet protocols 及支援

5.21.15 ‘uuid’ --
-----------------

'RFC 4122' 定義的 UUID 物件

'原始碼：'Lib/uuid.py(1)

__________________________________________________________________

這個模組提供了不可變的 *note UUID: a04. 物件（*note UUID: a04. 類別）和
*note uuid1(): b4f.、*note uuid3(): 1647.、*note uuid4(): 3931.、*note
uuid5(): 1648. 等函式，用於生成 RFC 4122(2) 定義的第 1、3、4、5 版本的
UUID。

如果你只需要一個唯一的 ID，你應該呼叫 *note uuid1(): b4f. 或 *note
uuid4(): 3931.。需要注意的是，*note uuid1(): b4f. 可能會危害隱私，因為它
會建立一個包含了電腦網路位址的 UUID。而 *note uuid4(): 3931. 則會建立一
個隨機的 UUID。

根據底層平台的支援情況，*note uuid1(): b4f. 可能會也可能不會回傳一個「安
全的」UUID。安全的 UUID 是使用同步方法生成的，以確保不會有兩個行程獲取到
相同的 UUID。所有 *note UUID: a04. 的實例都有一個 *note is_safe: b4d. 屬
性，該屬性使用下面這個列舉來傳遞有關 UUID 安全性的任何資訊：

 -- 類別: uuid.SafeUUID

     在 3.7 版被加入.

      -- 屬性: safe

          該 UUID 是由平台以多行程安全的 (multiprocessing-safe) 方式生成
          的。

      -- 屬性: unsafe

          該 UUID 不是以多行程安全的方式生成的。

      -- 屬性: unknown

          該平台不提供 UUID 是否為安全生成的資訊。

 -- 類別: uuid.UUID (hex=None, bytes=None, bytes_le=None, fields=None,
          int=None, version=None, *, is_safe=SafeUUID.unknown)

     從以下其中一種引數來建立 UUID：由 32 個十六進位的數字組成的字串、以
     大端順序 (big-endian) 排列的 16 個位元組組成的字串作為 'bytes' 引數
     、以小端順序 (little-endian) 排列的 16 個位元組組成的字串作為
     'bytes_le' 引數、由 6 個整數（32 位元的 'time_low'、16 位元的
     'time_mid'、16 位元的 'time_hi_version'、8 位元的
     'clock_seq_hi_variant'、8 位元的 'clock_seq_low'、48 位元的 'node'）
     組成的元組 (tuple) 作為 'fields' 引數，或者是單一的 128 位元整數作
     為 'int' 引數。當給定由十六進位的數字組成的字串時，大括號、連字符號
     和 URN 前綴都是可以選用的。例如，以下這些運算式都會產生相同的 UUID：

          UUID('{12345678-1234-5678-1234-567812345678}')
          UUID('12345678123456781234567812345678')
          UUID('urn:uuid:12345678-1234-5678-1234-567812345678')
          UUID(bytes=b'\x12\x34\x56\x78'*4)
          UUID(bytes_le=b'\x78\x56\x34\x12\x34\x12\x78\x56' +
                        b'\x12\x34\x56\x78\x12\x34\x56\x78')
          UUID(fields=(0x12345678, 0x1234, 0x5678, 0x12, 0x34, 0x567812345678))
          UUID(int=0x12345678123456781234567812345678)

     必須正好給定其中一個引數 'hex'、'bytes'、'bytes_le'、'fields' 或
     'int'。'version' 引數是選用的；如果給定了該引數，生成的 UUID 將根據
     RFC 4122(3) 設置其變體 (variant) 和版本號，覆蓋掉給定的 'hex'、
     'bytes'、'bytes_le'、'fields' 或 'int' 中的位元。

     UUID 物件之間的比較是透過比較它們的 *note UUID.int: 3936. 屬性。與
     非 UUID 的物件進行比較會引發 *note TypeError: 4dd.。

     ‘str(uuid)’ 會回傳一個像是 ‘12345678-1234-5678-1234-567812345678’ 形
     式的字串，其中 32 個十六進位的數字代表 UUID。

*note UUID: a04. 實例有以下唯讀的屬性：

 -- 屬性: UUID.bytes

     UUID 以 16 位元組的字串表示（包含 6 個整數欄位，按照大端位元組順序
     排列）。

 -- 屬性: UUID.bytes_le

     UUID 以 16 位元組的字串表示（其中 'time_low'、'time_mid' 和
     'time_hi_version' 按照小端位元組順序排列）。

 -- 屬性: UUID.fields

     UUID 以 6 個整數欄位所組成的元組表示，也可以看作有 6 個個別屬性和 2
     個衍生屬性：

欄位                                                   意義
                                                       
                                                       
 -- 屬性: UUID.time_low                                UUID 的前 32 位元。
                                                       
                                                       
 -- 屬性: UUID.time_mid                                UUID 接下來的 16 位元。
                                                       
                                                       
 -- 屬性: UUID.time_hi_version                         UUID 接下來的 16 位元。
                                                       
                                                       
 -- 屬性: UUID.clock_seq_hi_variant                    UUID 接下來的 8 位元。
                                                       
                                                       
 -- 屬性: UUID.clock_seq_low                           UUID 接下來的 8 位元。
                                                       
                                                       
 -- 屬性: UUID.node                                    UUID 最後的 48 位元。
                                                       
                                                       
 -- 屬性: UUID.time                                    60 位元的時間戳。
                                                       
                                                       
 -- 屬性: UUID.clock_seq                               14 位元的序列號。
                                                       

 -- 屬性: UUID.hex

     UUID 以 32 個小寫十六進位字元組成的字串表示。

 -- 屬性: UUID.int

     UUID 以 128 位元的整數表示。

 -- 屬性: UUID.urn

     UUID 以 RFC 4122(4) 中指定的 URN 形式表示。

 -- 屬性: UUID.variant

     UUID 的變體，決定 UUID 內部的佈局 (layout)，是 *note RESERVED_NCS:
     3945.、*note RFC_4122: 3946.、*note RESERVED_MICROSOFT: 3947. 或
     *note RESERVED_FUTURE: 3948. 其中一個常數。

 -- 屬性: UUID.version

     UUID 的版本號（1 到 5，只有當變體是 *note RFC_4122: 3946. 時才有意
     義）。

 -- 屬性: UUID.is_safe

     *note SafeUUID: 3932. 的列舉，表示平台是否以多行程安全的方式產生
     UUID。

     在 3.7 版被加入.

*note uuid: f8. 模組定義了以下函式：

 -- 函式: uuid.getnode ()

     取得 48 位元正整數形式的硬體位址。第一次執行時，有可能會啟動一個獨
     立的程式，這也許會相當耗時。如果所有獲取硬體位址的嘗試都失敗，我們
     會根據 RFC 4122(5) 中的建議，使用一個 48 位元的隨機數，其中群播位元
     (multicast bit)（第一個八位元組的最低有效位）設置為 1。「硬體位址」
     指的是網路介面 (network interface) 的 MAC 位址。在具有多個網路介面
     的機器上，將優先選擇通用管理 (universally administered) 的 MAC 位址
     （即第一個八位元組的第二個最低有效位是 '未設置的'），而不是本地管理
     (locally administered) 的 MAC 位址，除此之外不保證任何選擇的順序。

     在 3.7 版的變更: 通用管理的 MAC 位址優於本地管理的 MAC 位址，因為前
     者保證是全球唯一的，而後者不是。

 -- 函式: uuid.uuid1 (node=None, clock_seq=None)

     從主機 ID、序列號和當前時間生成 UUID。如果未給定 'node'，將使用
     *note getnode(): b4e. 獲取硬體位址。如果給定 'clock_seq'，會將其用
     作序列號；否則將使用一個隨機 14 位元的序列號。

 -- 函式: uuid.uuid3 (namespace, name)

     基於命名空間識別碼 (namespace identifier)（一個 UUID）和名稱（一個
     *note bytes: 1a5. 物件或使用 UTF-8 編碼的字串）的 MD5 hash 來生成
     UUID。

 -- 函式: uuid.uuid4 ()

     生成一個隨機的 UUID。

 -- 函式: uuid.uuid5 (namespace, name)

     基於命名空間識別碼（一個 UUID）和名稱（一個 *note bytes: 1a5. 物件
     或使用 UTF-8 編碼的字串）的 SHA-1 hash 來生成 UUID。

*note uuid: f8. 模組為 *note uuid3(): 1647. 或 *note uuid5(): 1648. 定義
了以下的命名空間識別碼。

 -- 資料: uuid.NAMESPACE_DNS

     當指定這個命名空間時，'name' 字串是一個完整網域名稱 (fully
     qualified domain name)。

 -- 資料: uuid.NAMESPACE_URL

     當指定這個命名空間時，'name' 字串是一個 URL。

 -- 資料: uuid.NAMESPACE_OID

     當指定這個命名空間時，'name' 字串是一個 ISO OID。

 -- 資料: uuid.NAMESPACE_X500

     當指定這個命名空間時，'name' 字串是以 DER 或文字輸出格式表示的
     X.500 DN。

*note uuid: f8. 模組為 *note variant: 3944. 屬性的可能值定義了以下常數：

 -- 資料: uuid.RESERVED_NCS

     保留供 NCS 相容性使用。

 -- 資料: uuid.RFC_4122

     使用在 RFC 4122(6) 中給定的 UUID 佈局。

 -- 資料: uuid.RESERVED_MICROSOFT

     保留供 Microsoft 相容性使用。

 -- 資料: uuid.RESERVED_FUTURE

     保留供未來定義使用。

也參考
......

RFC 4122(7) - 通用唯一辨識碼 (UUID, Universally Unique IDentifier) 的 URN 命名空間

     這個規範定義了 UUID 的統一資源名稱 (Uniform Resource Name) 命名空間
     、UUID 的內部格式和生成 UUID 的方法。

* Menu:

* 命令列的用法::
* 範例: 範例<37>.
* 命令列的範例::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/uuid.py

   (2) https://datatracker.ietf.org/doc/html/rfc4122.html

   (3) https://datatracker.ietf.org/doc/html/rfc4122.html

   (4) https://datatracker.ietf.org/doc/html/rfc4122.html

   (5) https://datatracker.ietf.org/doc/html/rfc4122.html

   (6) https://datatracker.ietf.org/doc/html/rfc4122.html

   (7) https://datatracker.ietf.org/doc/html/rfc4122.html


File: python.info,  Node: 命令列的用法,  Next: 範例<37>,  Up: uuid --- RFC 4122 定義的 UUID 物件

5.21.15.1 命令列的用法
......................

在 3.12 版被加入.

*note uuid: f8. 模組可以在命令列下作為腳本來執行。

     python -m uuid [-h] [-u {uuid1,uuid3,uuid4,uuid5}] [-n NAMESPACE] [-N NAME]

可以接受以下選項：

 -- Option: -h, --help

     顯示幫助訊息並退出。

 -- Option: -u <uuid>
 -- Option: --uuid <uuid>

     指定要用來生成 UUID 的函式名稱。預設使用 *note uuid4(): 3931.。

 -- Option: -n <namespace>
 -- Option: --namespace <namespace>

     該命名空間是一個 ‘UUID’ 或 ‘@ns’，其中 ‘ns’ 是指知名預定義 UUID 的
     命名空間名稱，例如 ‘@dns’、‘@url’、‘@oid’ 和 ‘@x500’。 只有 *note
     uuid3(): 1647. / *note uuid5(): 1648. 函式會需要。

 -- Option: -N <name>
 -- Option: --name <name>

     用於生成 uuid 的名稱。只有 *note uuid3(): 1647. / *note uuid5():
     1648. 函式會需要。


File: python.info,  Node: 範例<37>,  Next: 命令列的範例,  Prev: 命令列的用法,  Up: uuid --- RFC 4122 定義的 UUID 物件

5.21.15.2 範例
..............

以下是一些 *note uuid: f8. 模組的典型使用範例：

     >>> import uuid

     >>> # make a UUID based on the host ID and current time
     >>> uuid.uuid1()
     UUID('a8098c1a-f86e-11da-bd1a-00112444be1e')

     >>> # make a UUID using an MD5 hash of a namespace UUID and a name
     >>> uuid.uuid3(uuid.NAMESPACE_DNS, 'python.org')
     UUID('6fa459ea-ee8a-3ca4-894e-db77e160355e')

     >>> # make a random UUID
     >>> uuid.uuid4()
     UUID('16fd2706-8baf-433b-82eb-8c7fada847da')

     >>> # make a UUID using a SHA-1 hash of a namespace UUID and a name
     >>> uuid.uuid5(uuid.NAMESPACE_DNS, 'python.org')
     UUID('886313e1-3b8a-5372-9b90-0c9aee199e5d')

     >>> # make a UUID from a string of hex digits (braces and hyphens ignored)
     >>> x = uuid.UUID('{00010203-0405-0607-0809-0a0b0c0d0e0f}')

     >>> # convert a UUID to a string of hex digits in standard form
     >>> str(x)
     '00010203-0405-0607-0809-0a0b0c0d0e0f'

     >>> # get the raw 16 bytes of the UUID
     >>> x.bytes
     b'\x00\x01\x02\x03\x04\x05\x06\x07\x08\t\n\x0b\x0c\r\x0e\x0f'

     >>> # make a UUID from a 16-byte string
     >>> uuid.UUID(bytes=x.bytes)
     UUID('00010203-0405-0607-0809-0a0b0c0d0e0f')


File: python.info,  Node: 命令列的範例,  Prev: 範例<37>,  Up: uuid --- RFC 4122 定義的 UUID 物件

5.21.15.3 命令列的範例
......................

以下是一些 *note uuid: f8. 命令列介面的典型使用範例：

     # generate a random uuid - by default uuid4() is used
     $ python -m uuid

     # generate a uuid using uuid1()
     $ python -m uuid -u uuid1

     # generate a uuid using uuid5
     $ python -m uuid -u uuid5 -n @url -N example.com


File: python.info,  Node: socketserver --- 用於網路伺服器的框架,  Next: http server — HTTP 伺服器,  Prev: uuid --- RFC 4122 定義的 UUID 物件,  Up: 網路協定 Internet protocols 及支援

5.21.16 ‘socketserver’ -- 用於網路伺服器的框架
----------------------------------------------

'原始碼：'Lib/socketserver.py(1)

__________________________________________________________________

The *note socketserver: b9. module simplifies the task of writing
network servers.

*note Availability: 1c56.: not WASI.

This module does not work or is not available on WebAssembly.  See *note
WebAssembly 平台: 16e6. for more information.

There are four basic concrete server classes:

 -- 類別: socketserver.TCPServer (server_address, RequestHandlerClass,
          bind_and_activate=True)

     This uses the internet TCP protocol, which provides for continuous
     streams of data between the client and server.  If
     'bind_and_activate' is true, the constructor automatically attempts
     to invoke *note server_bind(): 395d. and *note server_activate():
     395e.  The other parameters are passed to the *note BaseServer:
     10d6. base class.

 -- 類別: socketserver.UDPServer (server_address, RequestHandlerClass,
          bind_and_activate=True)

     This uses datagrams, which are discrete packets of information that
     may arrive out of order or be lost while in transit.  The
     parameters are the same as for *note TCPServer: 12b3.

 -- 類別: socketserver.UnixStreamServer (server_address,
          RequestHandlerClass, bind_and_activate=True)
 -- 類別: socketserver.UnixDatagramServer (server_address,
          RequestHandlerClass, bind_and_activate=True)

     These more infrequently used classes are similar to the TCP and UDP
     classes, but use Unix domain sockets; they're not available on
     non-Unix platforms.  The parameters are the same as for *note
     TCPServer: 12b3.

These four classes process requests 'synchronously'; each request must
be completed before the next request can be started.  This isn't
suitable if each request takes a long time to complete, because it
requires a lot of computation, or because it returns a lot of data which
the client is slow to process.  The solution is to create a separate
process or thread to handle each request; the *note ForkingMixIn: b1b.
and *note ThreadingMixIn: b1c. mix-in classes can be used to support
asynchronous behaviour.

Creating a server requires several steps.  First, you must create a
request handler class by subclassing the *note BaseRequestHandler: 3962.
class and overriding its *note handle(): 3963. method; this method will
process incoming requests.  Second, you must instantiate one of the
server classes, passing it the server's address and the request handler
class.  It is recommended to use the server in a *note with: 577.
statement.  Then call the *note handle_request(): 12b6. or *note
serve_forever(): 10d8. method of the server object to process one or
many requests.  Finally, call *note server_close(): 3964. to close the
socket (unless you used a ‘with’ statement).

When inheriting from *note ThreadingMixIn: b1c. for threaded connection
behavior, you should explicitly declare how you want your threads to
behave on an abrupt shutdown.  The *note ThreadingMixIn: b1c. class
defines an attribute 'daemon_threads', which indicates whether or not
the server should wait for thread termination.  You should set the flag
explicitly if you would like threads to behave autonomously; the default
is *note False: adb, meaning that Python will not exit until all threads
created by *note ThreadingMixIn: b1c. have exited.

Server classes have the same external methods and attributes, no matter
what network protocol they use.

* Menu:

* Server Creation Notes::
* Server Objects::
* Request Handler Objects::
* 範例: 範例<38>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/socketserver.py


File: python.info,  Node: Server Creation Notes,  Next: Server Objects,  Up: socketserver --- 用於網路伺服器的框架

5.21.16.1 Server Creation Notes
...............................

There are five classes in an inheritance diagram, four of which
represent synchronous servers of four types:

     +------------+
     | BaseServer |
     +------------+
           |
           v
     +-----------+        +------------------+
     | TCPServer |------->| UnixStreamServer |
     +-----------+        +------------------+
           |
           v
     +-----------+        +--------------------+
     | UDPServer |------->| UnixDatagramServer |
     +-----------+        +--------------------+

Note that *note UnixDatagramServer: 3961. derives from *note UDPServer:
395f, not from *note UnixStreamServer: 3960. -- the only difference
between an IP and a Unix server is the address family.

 -- 類別: socketserver.ForkingMixIn
 -- 類別: socketserver.ThreadingMixIn

     Forking and threading versions of each type of server can be
     created using these mix-in classes.  For instance, *note
     ThreadingUDPServer: 3966. is created as follows:

          class ThreadingUDPServer(ThreadingMixIn, UDPServer):
              pass

     The mix-in class comes first, since it overrides a method defined
     in *note UDPServer: 395f.  Setting the various attributes also
     changes the behavior of the underlying server mechanism.

     *note ForkingMixIn: b1b. and the Forking classes mentioned below
     are only available on POSIX platforms that support *note fork():
     17b.

      -- 屬性: block_on_close

          *note ForkingMixIn.server_close: 3964. waits until all child
          processes complete, except if *note block_on_close: ba4.
          attribute is ‘False’.

          *note ThreadingMixIn.server_close: 3964. waits until all
          non-daemon threads complete, except if *note block_on_close:
          ba4. attribute is ‘False’.

      -- 屬性: daemon_threads

          For *note ThreadingMixIn: b1c. use daemonic threads by setting
          *note ThreadingMixIn.daemon_threads: 3967. to ‘True’ to not
          wait until threads complete.

     在 3.7 版的變更: *note ForkingMixIn.server_close: 3964. and *note
     ThreadingMixIn.server_close: 3964. now waits until all child
     processes and non-daemonic threads complete.  Add a new *note
     ForkingMixIn.block_on_close: ba4. class attribute to opt-in for the
     pre-3.7 behaviour.

 -- 類別: socketserver.ForkingTCPServer
 -- 類別: socketserver.ForkingUDPServer
 -- 類別: socketserver.ThreadingTCPServer
 -- 類別: socketserver.ThreadingUDPServer
 -- 類別: socketserver.ForkingUnixStreamServer
 -- 類別: socketserver.ForkingUnixDatagramServer
 -- 類別: socketserver.ThreadingUnixStreamServer
 -- 類別: socketserver.ThreadingUnixDatagramServer

     These classes are pre-defined using the mix-in classes.

在 3.12 版被加入: The ‘ForkingUnixStreamServer’ and
‘ForkingUnixDatagramServer’ classes were added.

To implement a service, you must derive a class from *note
BaseRequestHandler: 3962. and redefine its *note handle(): 3963. method.
You can then run various versions of the service by combining one of the
server classes with your request handler class.  The request handler
class must be different for datagram or stream services.  This can be
hidden by using the handler subclasses *note StreamRequestHandler: c81.
or *note DatagramRequestHandler: 396f.

Of course, you still have to use your head!  For instance, it makes no
sense to use a forking server if the service contains state in memory
that can be modified by different requests, since the modifications in
the child process would never reach the initial state kept in the parent
process and passed to each child.  In this case, you can use a threading
server, but you will probably have to use locks to protect the integrity
of the shared data.

On the other hand, if you are building an HTTP server where all data is
stored externally (for instance, in the file system), a synchronous
class will essentially render the service "deaf" while one request is
being handled - which may be for a very long time if a client is slow to
receive all the data it has requested.  Here a threading or forking
server is appropriate.

In some cases, it may be appropriate to process part of a request
synchronously, but to finish processing in a forked child depending on
the request data.  This can be implemented by using a synchronous server
and doing an explicit fork in the request handler class *note handle():
3963. method.

Another approach to handling multiple simultaneous requests in an
environment that supports neither threads nor *note fork(): 17b. (or
where these are too expensive or inappropriate for the service) is to
maintain an explicit table of partially finished requests and to use
*note selectors: b0. to decide which request to work on next (or whether
to handle a new incoming request).  This is particularly important for
stream services where each client can potentially be connected for a
long time (if threads or subprocesses cannot be used).


File: python.info,  Node: Server Objects,  Next: Request Handler Objects,  Prev: Server Creation Notes,  Up: socketserver --- 用於網路伺服器的框架

5.21.16.2 Server Objects
........................

 -- 類別: socketserver.BaseServer (server_address, RequestHandlerClass)

     This is the superclass of all Server objects in the module.  It
     defines the interface, given below, but does not implement most of
     the methods, which is done in subclasses.  The two parameters are
     stored in the respective *note server_address: 3971. and *note
     RequestHandlerClass: 3972. attributes.

      -- 方法: fileno ()

          Return an integer file descriptor for the socket on which the
          server is listening.  This function is most commonly passed to
          *note selectors: b0, to allow monitoring multiple servers in
          the same process.

      -- 方法: handle_request ()

          Process a single request.  This function calls the following
          methods in order: *note get_request(): 3974, *note
          verify_request(): 3975, and *note process_request(): 3976.  If
          the user-provided *note handle(): 3963. method of the handler
          class raises an exception, the server's *note handle_error():
          ce8. method will be called.  If no request is received within
          *note timeout: 12b4. seconds, *note handle_timeout(): 12b5.
          will be called and *note handle_request(): 12b6. will return.

      -- 方法: serve_forever (poll_interval=0.5)

          Handle requests until an explicit *note shutdown(): 193b.
          request.  Poll for shutdown every 'poll_interval' seconds.
          Ignores the *note timeout: 12b4. attribute.  It also calls
          *note service_actions(): 10d7, which may be used by a subclass
          or mixin to provide actions specific to a given service.  For
          example, the *note ForkingMixIn: b1b. class uses *note
          service_actions(): 10d7. to clean up zombie child processes.

          在 3.3 版的變更: Added ‘service_actions’ call to the
          ‘serve_forever’ method.

      -- 方法: service_actions ()

          This is called in the *note serve_forever(): 10d8. loop.  This
          method can be overridden by subclasses or mixin classes to
          perform actions specific to a given service, such as cleanup
          actions.

          在 3.3 版被加入.

      -- 方法: shutdown ()

          Tell the *note serve_forever(): 10d8. loop to stop and wait
          until it does.  *note shutdown(): 193b. must be called while
          *note serve_forever(): 10d8. is running in a different thread
          otherwise it will deadlock.

      -- 方法: server_close ()

          Clean up the server.  May be overridden.

      -- 屬性: address_family

          The family of protocols to which the server's socket belongs.
          Common examples are *note socket.AF_INET: 1722. and *note
          socket.AF_UNIX: 1724.

      -- 屬性: RequestHandlerClass

          The user-provided request handler class; an instance of this
          class is created for each request.

      -- 屬性: server_address

          The address on which the server is listening.  The format of
          addresses varies depending on the protocol family; see the
          documentation for the *note socket: b8. module for details.
          For internet protocols, this is a tuple containing a string
          giving the address, and an integer port number: ‘('127.0.0.1',
          80)’, for example.

      -- 屬性: socket

          The socket object on which the server will listen for incoming
          requests.

     The server classes support the following class variables:

      -- 屬性: allow_reuse_address

          Whether the server will allow the reuse of an address.  This
          defaults to *note False: adb, and can be set in subclasses to
          change the policy.

      -- 屬性: request_queue_size

          The size of the request queue.  If it takes a long time to
          process a single request, any requests that arrive while the
          server is busy are placed into a queue, up to *note
          request_queue_size: 397a. requests.  Once the queue is full,
          further requests from clients will get a "Connection denied"
          error.  The default value is usually 5, but this can be
          overridden by subclasses.

      -- 屬性: socket_type

          The type of socket used by the server; *note
          socket.SOCK_STREAM: 1286. and *note socket.SOCK_DGRAM: 1285.
          are two common values.

      -- 屬性: timeout

          Timeout duration, measured in seconds, or *note None: 61b. if
          no timeout is desired.  If *note handle_request(): 12b6.
          receives no incoming requests within the timeout period, the
          *note handle_timeout(): 12b5. method is called.

     There are various server methods that can be overridden by
     subclasses of base server classes like *note TCPServer: 12b3.;
     these methods aren't useful to external users of the server object.

      -- 方法: finish_request (request, client_address)

          Actually processes the request by instantiating *note
          RequestHandlerClass: 3972. and calling its *note handle():
          3963. method.

      -- 方法: get_request ()

          Must accept a request from the socket, and return a 2-tuple
          containing the 'new' socket object to be used to communicate
          with the client, and the client's address.

      -- 方法: handle_error (request, client_address)

          This function is called if the *note handle(): 3963. method of
          a *note RequestHandlerClass: 3972. instance raises an
          exception.  The default action is to print the traceback to
          standard error and continue handling further requests.

          在 3.6 版的變更: Now only called for exceptions derived from
          the *note Exception: 97d. class.

      -- 方法: handle_timeout ()

          This function is called when the *note timeout: 12b4.
          attribute has been set to a value other than *note None: 61b.
          and the timeout period has passed with no requests being
          received.  The default action for forking servers is to
          collect the status of any child processes that have exited,
          while in threading servers this method does nothing.

      -- 方法: process_request (request, client_address)

          Calls *note finish_request(): 397c. to create an instance of
          the *note RequestHandlerClass: 3972.  If desired, this
          function can create a new process or thread to handle the
          request; the *note ForkingMixIn: b1b. and *note
          ThreadingMixIn: b1c. classes do this.

      -- 方法: server_activate ()

          Called by the server's constructor to activate the server.
          The default behavior for a TCP server just invokes *note
          listen(): e00. on the server's socket.  May be overridden.

      -- 方法: server_bind ()

          Called by the server's constructor to bind the socket to the
          desired address.  May be overridden.

      -- 方法: verify_request (request, client_address)

          Must return a Boolean value; if the value is *note True: bb4,
          the request will be processed, and if it's *note False: adb,
          the request will be denied.  This function can be overridden
          to implement access controls for a server.  The default
          implementation always returns *note True: bb4.

     在 3.6 版的變更: Support for the *note context manager: 576.
     protocol was added.  Exiting the context manager is equivalent to
     calling *note server_close(): 3964.


File: python.info,  Node: Request Handler Objects,  Next: 範例<38>,  Prev: Server Objects,  Up: socketserver --- 用於網路伺服器的框架

5.21.16.3 Request Handler Objects
.................................

 -- 類別: socketserver.BaseRequestHandler

     This is the superclass of all request handler objects.  It defines
     the interface, given below.  A concrete request handler subclass
     must define a new *note handle(): 3963. method, and can override
     any of the other methods.  A new instance of the subclass is
     created for each request.

      -- 方法: setup ()

          Called before the *note handle(): 3963. method to perform any
          initialization actions required.  The default implementation
          does nothing.

      -- 方法: handle ()

          This function must do all the work required to service a
          request.  The default implementation does nothing.  Several
          instance attributes are available to it; the request is
          available as *note request: 397f.; the client address as *note
          client_address: 3980.; and the server instance as *note
          server: 3981, in case it needs access to per-server
          information.

          The type of *note request: 397f. is different for datagram or
          stream services.  For stream services, *note request: 397f. is
          a socket object; for datagram services, *note request: 397f.
          is a pair of string and socket.

      -- 方法: finish ()

          Called after the *note handle(): 3963. method to perform any
          clean-up actions required.  The default implementation does
          nothing.  If *note setup(): 397e. raises an exception, this
          function will not be called.

      -- 屬性: request

          The 'new' *note socket.socket: d47. object to be used to
          communicate with the client.

      -- 屬性: client_address

          Client address returned by *note BaseServer.get_request():
          3974.

      -- 屬性: server

          *note BaseServer: 10d6. object used for handling the request.

 -- 類別: socketserver.StreamRequestHandler
 -- 類別: socketserver.DatagramRequestHandler

     These *note BaseRequestHandler: 3962. subclasses override the *note
     setup(): 397e. and *note finish(): 3982. methods, and provide *note
     rfile: 3983. and *note wfile: 3984. attributes.

      -- 屬性: rfile

          A file object from which receives the request is read.
          Support the *note io.BufferedIOBase: 63a. readable interface.

      -- 屬性: wfile

          A file object to which the reply is written.  Support the
          *note io.BufferedIOBase: 63a. writable interface

     在 3.6 版的變更: *note wfile: 3984. also supports the *note
     io.BufferedIOBase: 63a. writable interface.


File: python.info,  Node: 範例<38>,  Prev: Request Handler Objects,  Up: socketserver --- 用於網路伺服器的框架

5.21.16.4 範例
..............

* Menu:

* socketserver.TCPServer 範例: socketserver TCPServer 範例.
* socketserver.UDPServer 範例: socketserver UDPServer 範例.
* Asynchronous Mixins::


File: python.info,  Node: socketserver TCPServer 範例,  Next: socketserver UDPServer 範例,  Up: 範例<38>

5.21.16.5 ‘socketserver.TCPServer’ 範例
.......................................

This is the server side:

     import socketserver

     class MyTCPHandler(socketserver.BaseRequestHandler):
         """
         The request handler class for our server.

         It is instantiated once per connection to the server, and must
         override the handle() method to implement communication to the
         client.
         """

         def handle(self):
             # self.request is the TCP socket connected to the client
             self.data = self.request.recv(1024).strip()
             print("Received from {}:".format(self.client_address[0]))
             print(self.data)
             # just send back the same data, but upper-cased
             self.request.sendall(self.data.upper())

     if __name__ == "__main__":
         HOST, PORT = "localhost", 9999

         # Create the server, binding to localhost on port 9999
         with socketserver.TCPServer((HOST, PORT), MyTCPHandler) as server:
             # Activate the server; this will keep running until you
             # interrupt the program with Ctrl-C
             server.serve_forever()

An alternative request handler class that makes use of streams
(file-like objects that simplify communication by providing the standard
file interface):

     class MyTCPHandler(socketserver.StreamRequestHandler):

         def handle(self):
             # self.rfile is a file-like object created by the handler;
             # we can now use e.g. readline() instead of raw recv() calls
             self.data = self.rfile.readline().strip()
             print("{} wrote:".format(self.client_address[0]))
             print(self.data)
             # Likewise, self.wfile is a file-like object used to write back
             # to the client
             self.wfile.write(self.data.upper())

The difference is that the ‘readline()’ call in the second handler will
call ‘recv()’ multiple times until it encounters a newline character,
while the single ‘recv()’ call in the first handler will just return
what has been received so far from the client's ‘sendall()’ call
(typically all of it, but this is not guaranteed by the TCP protocol).

This is the client side:

     import socket
     import sys

     HOST, PORT = "localhost", 9999
     data = " ".join(sys.argv[1:])

     # Create a socket (SOCK_STREAM means a TCP socket)
     with socket.socket(socket.AF_INET, socket.SOCK_STREAM) as sock:
         # Connect to server and send data
         sock.connect((HOST, PORT))
         sock.sendall(bytes(data + "\n", "utf-8"))

         # Receive data from the server and shut down
         received = str(sock.recv(1024), "utf-8")

     print("Sent:     {}".format(data))
     print("Received: {}".format(received))

The output of the example should look something like this:

Server:

     $ python TCPServer.py
     127.0.0.1 wrote:
     b'hello world with TCP'
     127.0.0.1 wrote:
     b'python is nice'

Client:

     $ python TCPClient.py hello world with TCP
     Sent:     hello world with TCP
     Received: HELLO WORLD WITH TCP
     $ python TCPClient.py python is nice
     Sent:     python is nice
     Received: PYTHON IS NICE


File: python.info,  Node: socketserver UDPServer 範例,  Next: Asynchronous Mixins,  Prev: socketserver TCPServer 範例,  Up: 範例<38>

5.21.16.6 ‘socketserver.UDPServer’ 範例
.......................................

This is the server side:

     import socketserver

     class MyUDPHandler(socketserver.BaseRequestHandler):
         """
         This class works similar to the TCP handler class, except that
         self.request consists of a pair of data and client socket, and since
         there is no connection the client address must be given explicitly
         when sending data back via sendto().
         """

         def handle(self):
             data = self.request[0].strip()
             socket = self.request[1]
             print("{} wrote:".format(self.client_address[0]))
             print(data)
             socket.sendto(data.upper(), self.client_address)

     if __name__ == "__main__":
         HOST, PORT = "localhost", 9999
         with socketserver.UDPServer((HOST, PORT), MyUDPHandler) as server:
             server.serve_forever()

This is the client side:

     import socket
     import sys

     HOST, PORT = "localhost", 9999
     data = " ".join(sys.argv[1:])

     # SOCK_DGRAM is the socket type to use for UDP sockets
     sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)

     # As you can see, there is no connect() call; UDP has no connections.
     # Instead, data is directly sent to the recipient via sendto().
     sock.sendto(bytes(data + "\n", "utf-8"), (HOST, PORT))
     received = str(sock.recv(1024), "utf-8")

     print("Sent:     {}".format(data))
     print("Received: {}".format(received))

The output of the example should look exactly like for the TCP server
example.


File: python.info,  Node: Asynchronous Mixins,  Prev: socketserver UDPServer 範例,  Up: 範例<38>

5.21.16.7 Asynchronous Mixins
.............................

To build asynchronous handlers, use the *note ThreadingMixIn: b1c. and
*note ForkingMixIn: b1b. classes.

An example for the *note ThreadingMixIn: b1c. class:

     import socket
     import threading
     import socketserver

     class ThreadedTCPRequestHandler(socketserver.BaseRequestHandler):

         def handle(self):
             data = str(self.request.recv(1024), 'ascii')
             cur_thread = threading.current_thread()
             response = bytes("{}: {}".format(cur_thread.name, data), 'ascii')
             self.request.sendall(response)

     class ThreadedTCPServer(socketserver.ThreadingMixIn, socketserver.TCPServer):
         pass

     def client(ip, port, message):
         with socket.socket(socket.AF_INET, socket.SOCK_STREAM) as sock:
             sock.connect((ip, port))
             sock.sendall(bytes(message, 'ascii'))
             response = str(sock.recv(1024), 'ascii')
             print("Received: {}".format(response))

     if __name__ == "__main__":
         # Port 0 means to select an arbitrary unused port
         HOST, PORT = "localhost", 0

         server = ThreadedTCPServer((HOST, PORT), ThreadedTCPRequestHandler)
         with server:
             ip, port = server.server_address

             # Start a thread with the server -- that thread will then start one
             # more thread for each request
             server_thread = threading.Thread(target=server.serve_forever)
             # Exit the server thread when the main thread terminates
             server_thread.daemon = True
             server_thread.start()
             print("Server loop running in thread:", server_thread.name)

             client(ip, port, "Hello World 1")
             client(ip, port, "Hello World 2")
             client(ip, port, "Hello World 3")

             server.shutdown()

The output of the example should look something like this:

     $ python ThreadedTCPServer.py
     Server loop running in thread: Thread-1
     Received: Thread-2: Hello World 1
     Received: Thread-3: Hello World 2
     Received: Thread-4: Hello World 3

The *note ForkingMixIn: b1b. class is used in the same way, except that
the server will spawn a new process for each request.  Available only on
POSIX platforms that support *note fork(): 17b.


File: python.info,  Node: http server — HTTP 伺服器,  Next: http cookies --- HTTP 狀態管理,  Prev: socketserver --- 用於網路伺服器的框架,  Up: 網路協定 Internet protocols 及支援

5.21.17 ‘http.server’ — HTTP 伺服器
-----------------------------------

'原始碼：'Lib/http/server.py(1)

__________________________________________________________________

此模組定義了用於實作 HTTP 伺服器的類別。

     警告: *note http.server: 68. is not recommended for production.  It
     only implements *note basic security checks: 398b.

*note Availability: 1c56.: not WASI.

This module does not work or is not available on WebAssembly.  See *note
WebAssembly 平台: 16e6. for more information.

One class, *note HTTPServer: 378d, is a *note socketserver.TCPServer:
12b3. subclass.  It creates and listens at the HTTP socket, dispatching
the requests to a handler.  Code to create and run the server looks like
this:

     def run(server_class=HTTPServer, handler_class=BaseHTTPRequestHandler):
         server_address = ('', 8000)
         httpd = server_class(server_address, handler_class)
         httpd.serve_forever()

 -- 類別: http.server.HTTPServer (server_address, RequestHandlerClass)

     This class builds on the *note TCPServer: 12b3. class by storing
     the server address as instance variables named ‘server_name’ and
     ‘server_port’.  The server is accessible by the handler, typically
     through the handler's ‘server’ instance variable.

 -- 類別: http.server.ThreadingHTTPServer (server_address,
          RequestHandlerClass)

     This class is identical to HTTPServer but uses threads to handle
     requests by using the *note ThreadingMixIn: b1c.  This is useful to
     handle web browsers pre-opening sockets, on which *note HTTPServer:
     378d. would wait indefinitely.

     在 3.7 版被加入.

The *note HTTPServer: 378d. and *note ThreadingHTTPServer: ae8. must be
given a 'RequestHandlerClass' on instantiation, of which this module
provides three different variants:

 -- 類別: http.server.BaseHTTPRequestHandler (request, client_address,
          server)

     This class is used to handle the HTTP requests that arrive at the
     server.  By itself, it cannot respond to any actual HTTP requests;
     it must be subclassed to handle each request method (e.g.  GET or
     POST). *note BaseHTTPRequestHandler: 1065. provides a number of
     class and instance variables, and methods for use by subclasses.

     The handler will parse the request and the headers, then call a
     method specific to the request type.  The method name is
     constructed from the request.  For example, for the request method
     ‘SPAM’, the ‘do_SPAM()’ method will be called with no arguments.
     All of the relevant information is stored in instance variables of
     the handler.  Subclasses should not need to override or extend the
     ‘__init__()’ method.

     *note BaseHTTPRequestHandler: 1065. has the following instance
     variables:

      -- 屬性: client_address

          Contains a tuple of the form ‘(host, port)’ referring to the
          client's address.

      -- 屬性: server

          Contains the server instance.

      -- 屬性: close_connection

          Boolean that should be set before *note handle_one_request():
          398f. returns, indicating if another request may be expected,
          or if the connection should be shut down.

      -- 屬性: requestline

          Contains the string representation of the HTTP request line.
          The terminating CRLF is stripped.  This attribute should be
          set by *note handle_one_request(): 398f.  If no valid request
          line was processed, it should be set to the empty string.

      -- 屬性: command

          Contains the command (request type).  For example, ‘'GET'’.

      -- 屬性: path

          Contains the request path.  If query component of the URL is
          present, then ‘path’ includes the query.  Using the
          terminology of RFC 3986(2), ‘path’ here includes ‘hier-part’
          and the ‘query’.

      -- 屬性: request_version

          Contains the version string from the request.  For example,
          ‘'HTTP/1.0'’.

      -- 屬性: headers

          Holds an instance of the class specified by the *note
          MessageClass: 3994. class variable.  This instance parses and
          manages the headers in the HTTP request.  The *note
          parse_headers(): 194f. function from *note http.client: 65. is
          used to parse the headers and it requires that the HTTP
          request provide a valid RFC 2822(3) style header.

      -- 屬性: rfile

          An *note io.BufferedIOBase: 63a. input stream, ready to read
          from the start of the optional input data.

      -- 屬性: wfile

          Contains the output stream for writing a response back to the
          client.  Proper adherence to the HTTP protocol must be used
          when writing to this stream in order to achieve successful
          interoperation with HTTP clients.

          在 3.6 版的變更: This is an *note io.BufferedIOBase: 63a.
          stream.

     *note BaseHTTPRequestHandler: 1065. 擁有以下屬性：

      -- 屬性: server_version

          Specifies the server software version.  You may want to
          override this.  The format is multiple whitespace-separated
          strings, where each string is of the form name[/version].  For
          example, ‘'BaseHTTP/0.2'’.

      -- 屬性: sys_version

          Contains the Python system version, in a form usable by the
          *note version_string: 3999. method and the *note
          server_version: 3997. class variable.  For example,
          ‘'Python/1.4'’.

      -- 屬性: error_message_format

          Specifies a format string that should be used by *note
          send_error(): ef3. method for building an error response to
          the client.  The string is filled by default with variables
          from *note responses: 385f. based on the status code that
          passed to *note send_error(): ef3.

      -- 屬性: error_content_type

          Specifies the Content-Type HTTP header of error responses sent
          to the client.  The default value is ‘'text/html'’.

      -- 屬性: protocol_version

          Specifies the HTTP version to which the server is conformant.
          It is sent in responses to let the client know the server's
          communication capabilities for future requests.  If set to
          ‘'HTTP/1.1'’, the server will permit HTTP persistent
          connections; however, your server 'must' then include an
          accurate ‘Content-Length’ header (using *note send_header():
          399d.) in all of its responses to clients.  For backwards
          compatibility, the setting defaults to ‘'HTTP/1.0'’.

      -- 屬性: MessageClass

          Specifies an *note email.message.Message: 261.-like class to
          parse HTTP headers.  Typically, this is not overridden, and it
          defaults to *note http.client.HTTPMessage: 3876.

      -- 屬性: responses

          This attribute contains a mapping of error code integers to
          two-element tuples containing a short and long message.  For
          example, ‘{code: (shortmessage, longmessage)}’.  The
          'shortmessage' is usually used as the 'message' key in an
          error response, and 'longmessage' as the 'explain' key.  It is
          used by *note send_response_only(): 399e. and *note
          send_error(): ef3. methods.

     A *note BaseHTTPRequestHandler: 1065. instance has the following
     methods:

      -- 方法: handle ()

          Calls *note handle_one_request(): 398f. once (or, if
          persistent connections are enabled, multiple times) to handle
          incoming HTTP requests.  You should never need to override it;
          instead, implement appropriate ‘do_*()’ methods.

      -- 方法: handle_one_request ()

          This method will parse and dispatch the request to the
          appropriate ‘do_*()’ method.  You should never need to
          override it.

      -- 方法: handle_expect_100 ()

          When an HTTP/1.1 conformant server receives an ‘Expect:
          100-continue’ request header it responds back with a ‘100
          Continue’ followed by ‘200 OK’ headers.  This method can be
          overridden to raise an error if the server does not want the
          client to continue.  For e.g.  server can choose to send ‘417
          Expectation Failed’ as a response header and ‘return False’.

          在 3.2 版被加入.

      -- 方法: send_error (code, message=None, explain=None)

          Sends and logs a complete error reply to the client.  The
          numeric 'code' specifies the HTTP error code, with 'message'
          as an optional, short, human readable description of the
          error.  The 'explain' argument can be used to provide more
          detailed information about the error; it will be formatted
          using the *note error_message_format: 399a. attribute and
          emitted, after a complete set of headers, as the response
          body.  The *note responses: 385f. attribute holds the default
          values for 'message' and 'explain' that will be used if no
          value is provided; for unknown codes the default value for
          both is the string ‘???’.  The body will be empty if the
          method is HEAD or the response code is one of the following:
          ‘1XX’, ‘204 No Content’, ‘205 Reset Content’, ‘304 Not
          Modified’.

          在 3.4 版的變更: The error response includes a Content-Length
          header.  Added the 'explain' argument.

      -- 方法: send_response (code, message=None)

          Adds a response header to the headers buffer and logs the
          accepted request.  The HTTP response line is written to the
          internal buffer, followed by 'Server' and 'Date' headers.  The
          values for these two headers are picked up from the *note
          version_string(): 3999. and *note date_time_string(): 39a2.
          methods, respectively.  If the server does not intend to send
          any other headers using the *note send_header(): 399d. method,
          then *note send_response(): 39a1. should be followed by an
          *note end_headers(): 1066. call.

          在 3.3 版的變更: Headers are stored to an internal buffer and
          *note end_headers(): 1066. needs to be called explicitly.

      -- 方法: send_header (keyword, value)

          Adds the HTTP header to an internal buffer which will be
          written to the output stream when either *note end_headers():
          1066. or *note flush_headers(): 1067. is invoked.  'keyword'
          should specify the header keyword, with 'value' specifying its
          value.  Note that, after the send_header calls are done, *note
          end_headers(): 1066. MUST BE called in order to complete the
          operation.

          在 3.2 版的變更: Headers are stored in an internal buffer.

      -- 方法: send_response_only (code, message=None)

          Sends the response header only, used for the purposes when
          ‘100 Continue’ response is sent by the server to the client.
          The headers not buffered and sent directly the output
          stream.If the 'message' is not specified, the HTTP message
          corresponding the response 'code' is sent.

          在 3.2 版被加入.

      -- 方法: end_headers ()

          Adds a blank line (indicating the end of the HTTP headers in
          the response) to the headers buffer and calls *note
          flush_headers(): 1067.

          在 3.2 版的變更: The buffered headers are written to the
          output stream.

      -- 方法: flush_headers ()

          Finally send the headers to the output stream and flush the
          internal headers buffer.

          在 3.3 版被加入.

      -- 方法: log_request (code='-', size='-')

          Logs an accepted (successful) request.  'code' should specify
          the numeric HTTP code associated with the response.  If a size
          of the response is available, then it should be passed as the
          'size' parameter.

      -- 方法: log_error (...)

          Logs an error when a request cannot be fulfilled.  By default,
          it passes the message to *note log_message(): 39a5, so it
          takes the same arguments ('format' and additional values).

      -- 方法: log_message (format, ...)

          Logs an arbitrary message to ‘sys.stderr’.  This is typically
          overridden to create custom error logging mechanisms.  The
          'format' argument is a standard printf-style format string,
          where the additional arguments to *note log_message(): 39a5.
          are applied as inputs to the formatting.  The client ip
          address and current date and time are prefixed to every
          message logged.

      -- 方法: version_string ()

          Returns the server software's version string.  This is a
          combination of the *note server_version: 3997. and *note
          sys_version: 3998. attributes.

      -- 方法: date_time_string (timestamp=None)

          Returns the date and time given by 'timestamp' (which must be
          ‘None’ or in the format returned by *note time.time(): 239.),
          formatted for a message header.  If 'timestamp' is omitted, it
          uses the current date and time.

          The result looks like ‘'Sun, 06 Nov 1994 08:49:37 GMT'’.

      -- 方法: log_date_time_string ()

          Returns the current date and time, formatted for logging.

      -- 方法: address_string ()

          Returns the client address.

          在 3.3 版的變更: Previously, a name lookup was performed.  To
          avoid name resolution delays, it now always returns the IP
          address.

 -- 類別: http.server.SimpleHTTPRequestHandler (request, client_address,
          server, directory=None)

     This class serves files from the directory 'directory' and below,
     or the current directory if 'directory' is not provided, directly
     mapping the directory structure to HTTP requests.

     在 3.7 版的變更: 新增 'directory' 參數。

     在 3.9 版的變更: The 'directory' parameter accepts a *note
     path-like object: ac2.

     A lot of the work, such as parsing the request, is done by the base
     class *note BaseHTTPRequestHandler: 1065.  This class implements
     the *note do_GET(): 39a8. and *note do_HEAD(): 39a9. functions.

     The following are defined as class-level attributes of *note
     SimpleHTTPRequestHandler: ae7.:

      -- 屬性: server_version

          This will be ‘"SimpleHTTP/" + __version__’, where
          ‘__version__’ is defined at the module level.

      -- 屬性: extensions_map

          A dictionary mapping suffixes into MIME types, contains custom
          overrides for the default system mappings.  The mapping is
          used case-insensitively, and so should contain only
          lower-cased keys.

          在 3.9 版的變更: This dictionary is no longer filled with the
          default system mappings, but only contains overrides.

     The *note SimpleHTTPRequestHandler: ae7. class defines the
     following methods:

      -- 方法: do_HEAD ()

          This method serves the ‘'HEAD'’ request type: it sends the
          headers it would send for the equivalent ‘GET’ request.  See
          the *note do_GET(): 39a8. method for a more complete
          explanation of the possible headers.

      -- 方法: do_GET ()

          The request is mapped to a local file by interpreting the
          request as a path relative to the current working directory.

          If the request was mapped to a directory, the directory is
          checked for a file named ‘index.html’ or ‘index.htm’ (in that
          order).  If found, the file's contents are returned; otherwise
          a directory listing is generated by calling the
          ‘list_directory()’ method.  This method uses *note
          os.listdir(): 1092. to scan the directory, and returns a ‘404’
          error response if the *note listdir(): 1092. fails.

          If the request was mapped to a file, it is opened.  Any *note
          OSError: 350. exception in opening the requested file is
          mapped to a ‘404’, ‘'File not found'’ error.  If there was an
          ‘'If-Modified-Since'’ header in the request, and the file was
          not modified after this time, a ‘304’, ‘'Not Modified'’
          response is sent.  Otherwise, the content type is guessed by
          calling the ‘guess_type()’ method, which in turn uses the
          'extensions_map' variable, and the file contents are returned.

          A ‘'Content-type:'’ header with the guessed content type is
          output, followed by a ‘'Content-Length:'’ header with the
          file's size and a ‘'Last-Modified:'’ header with the file's
          modification time.

          Then follows a blank line signifying the end of the headers,
          and then the contents of the file are output.  If the file's
          MIME type starts with ‘text/’ the file is opened in text mode;
          otherwise binary mode is used.

          For example usage, see the implementation of the ‘test’
          function in Lib/http/server.py(4).

          在 3.7 版的變更: Support of the ‘'If-Modified-Since'’ header.

The *note SimpleHTTPRequestHandler: ae7. class can be used in the
following manner in order to create a very basic webserver serving files
relative to the current directory:

     import http.server
     import socketserver

     PORT = 8000

     Handler = http.server.SimpleHTTPRequestHandler

     with socketserver.TCPServer(("", PORT), Handler) as httpd:
         print("serving at port", PORT)
         httpd.serve_forever()

*note SimpleHTTPRequestHandler: ae7. can also be subclassed to enhance
behavior, such as using different index file names by overriding the
class attribute ‘index_pages’.  *note http.server: 68. can also be
invoked directly using the *note -m: 585. switch of the interpreter.
Similar to the previous example, this serves files relative to the
current directory:

     python -m http.server

The server listens to port 8000 by default.  The default can be
overridden by passing the desired port number as an argument:

     python -m http.server 9000

By default, the server binds itself to all interfaces.  The option
‘-b/--bind’ specifies a specific address to which it should bind.  Both
IPv4 and IPv6 addresses are supported.  For example, the following
command causes the server to bind to localhost only:

     python -m http.server --bind 127.0.0.1

在 3.4 版的變更: 新增 ‘--bind’ 選項。

在 3.8 版的變更: 於 ‘--bind’ 選項中支援 IPv6。

By default, the server uses the current directory.  The option
‘-d/--directory’ specifies a directory to which it should serve the
files.  For example, the following command uses a specific directory:

     python -m http.server --directory /tmp/

在 3.7 版的變更: 新增 ‘--directory’ 選項。

By default, the server is conformant to HTTP/1.0.  The option
‘-p/--protocol’ specifies the HTTP version to which the server is
conformant.  For example, the following command runs an HTTP/1.1
conformant server:

     python -m http.server --protocol HTTP/1.1

在 3.11 版的變更: 新增 ‘--protocol’ 選項。

 -- 類別: http.server.CGIHTTPRequestHandler (request, client_address,
          server)

     This class is used to serve either files or output of CGI scripts
     from the current directory and below.  Note that mapping HTTP
     hierarchic structure to local directory structure is exactly as in
     *note SimpleHTTPRequestHandler: ae7.

          備註: CGI scripts run by the *note CGIHTTPRequestHandler: 281.
          class cannot execute redirects (HTTP code 302), because code
          200 (script output follows) is sent prior to execution of the
          CGI script.  This pre-empts the status code.

     The class will however, run the CGI script, instead of serving it
     as a file, if it guesses it to be a CGI script.  Only
     directory-based CGI are used -- the other common server
     configuration is to treat special extensions as denoting CGI
     scripts.

     The ‘do_GET()’ and ‘do_HEAD()’ functions are modified to run CGI
     scripts and serve the output, instead of serving files, if the
     request leads to somewhere below the ‘cgi_directories’ path.

     The *note CGIHTTPRequestHandler: 281. defines the following data
     member:

      -- 屬性: cgi_directories

          This defaults to ‘['/cgi-bin', '/htbin']’ and describes
          directories to treat as containing CGI scripts.

     The *note CGIHTTPRequestHandler: 281. defines the following method:

      -- 方法: do_POST ()

          This method serves the ‘'POST'’ request type, only allowed for
          CGI scripts.  Error 501, "Can only POST to CGI scripts", is
          output when trying to POST to a non-CGI url.

     Note that CGI scripts will be run with UID of user nobody, for
     security reasons.  Problems with the CGI script will be translated
     to error 403.

     Deprecated since version 3.13, will be removed in version 3.15:
     *note CGIHTTPRequestHandler: 281. is being removed in 3.15.  CGI
     has not been considered a good way to do things for well over a
     decade.  This code has been unmaintained for a while now and sees
     very little practical use.  Retaining it could lead to further
     *note security considerations: 398b.

*note CGIHTTPRequestHandler: 281. can be enabled in the command line by
passing the ‘--cgi’ option:

     python -m http.server --cgi

Deprecated since version 3.13, will be removed in version 3.15: *note
http.server: 68. command line ‘--cgi’ support is being removed because
*note CGIHTTPRequestHandler: 281. is being removed.

     警告: *note CGIHTTPRequestHandler: 281. and the ‘--cgi’ command
     line option are not intended for use by untrusted clients and may
     be vulnerable to exploitation.  Always use within a secure
     environment.

* Menu:

* 安全性注意事項: 安全性注意事項<3>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/http/server.py

   (2) https://datatracker.ietf.org/doc/html/rfc3986.html

   (3) https://datatracker.ietf.org/doc/html/rfc2822.html

   (4) https://github.com/python/cpython/tree/3.13/Lib/http/server.py


File: python.info,  Node: 安全性注意事項<3>,  Up: http server — HTTP 伺服器

5.21.17.1 安全性注意事項
........................

*note SimpleHTTPRequestHandler: ae7. will follow symbolic links when
handling requests, this makes it possible for files outside of the
specified directory to be served.

Earlier versions of Python did not scrub control characters from the log
messages emitted to stderr from ‘python -m http.server’ or the default
*note BaseHTTPRequestHandler: 1065. ‘.log_message’ implementation.  This
could allow remote clients connecting to your server to send nefarious
control codes to your terminal.

在 3.12 版的變更: Control characters are scrubbed in stderr logs.


File: python.info,  Node: http cookies --- HTTP 狀態管理,  Next: http cookiejar --- HTTP 客戶端的 Cookie 處理,  Prev: http server — HTTP 伺服器,  Up: 網路協定 Internet protocols 及支援

5.21.18 ‘http.cookies’ -- HTTP 狀態管理
---------------------------------------

'原始碼：'Lib/http/cookies.py(1)

__________________________________________________________________

The *note http.cookies: 67. module defines classes for abstracting the
concept of cookies, an HTTP state management mechanism.  It supports
both simple string-only cookies, and provides an abstraction for having
any serializable data-type as cookie value.

The module formerly strictly applied the parsing rules described in the
RFC 2109(2) and RFC 2068(3) specifications.  It has since been
discovered that MSIE 3.0x didn't follow the character rules outlined in
those specs; many current-day browsers and servers have also relaxed
parsing rules when it comes to cookie handling.  As a result, this
module now uses parsing rules that are a bit less strict than they once
were.

The character set, *note string.ascii_letters: 1258, *note
string.digits: 21a0. and ‘!#$%&'*+-.^_`|~:’ denote the set of valid
characters allowed by this module in a cookie name (as *note key: ba8.).

在 3.3 版的變更: Allowed ':' as a valid cookie name character.

     備註: On encountering an invalid cookie, *note CookieError: 39b1.
     is raised, so if your cookie data comes from a browser you should
     always prepare for invalid data and catch *note CookieError: 39b1.
     on parsing.

 -- 例外: http.cookies.CookieError

     Exception failing because of RFC 2109(4) invalidity: incorrect
     attributes, incorrect ‘Set-Cookie’ header, etc.

 -- 類別: http.cookies.BaseCookie ([input])

     This class is a dictionary-like object whose keys are strings and
     whose values are *note Morsel: bab. instances.  Note that upon
     setting a key to a value, the value is first converted to a *note
     Morsel: bab. containing the key and the value.

     If 'input' is given, it is passed to the *note load(): 39b3.
     method.

 -- 類別: http.cookies.SimpleCookie ([input])

     This class derives from *note BaseCookie: 39b2. and overrides *note
     value_decode(): 39b4. and *note value_encode(): 39b5.
     ‘SimpleCookie’ supports strings as cookie values.  When setting the
     value, ‘SimpleCookie’ calls the builtin *note str(): 3f2. to
     convert the value to a string.  Values received from HTTP are kept
     as strings.

也參考
......

*note http.cookiejar: 66. 模組

     HTTP cookie handling for web 'clients'.  The *note http.cookiejar:
     66. and *note http.cookies: 67. modules do not depend on each
     other.

RFC 2109(5) - HTTP State Management Mechanism

     This is the state management specification implemented by this
     module.

* Menu:

* Cookie 物件::
* Morsel 物件::
* 範例: 範例<39>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/http/cookies.py

   (2) https://datatracker.ietf.org/doc/html/rfc2109.html

   (3) https://datatracker.ietf.org/doc/html/rfc2068.html

   (4) https://datatracker.ietf.org/doc/html/rfc2109.html

   (5) https://datatracker.ietf.org/doc/html/rfc2109.html


File: python.info,  Node: Cookie 物件,  Next: Morsel 物件,  Up: http cookies --- HTTP 狀態管理

5.21.18.1 Cookie 物件
.....................

 -- 方法: BaseCookie.value_decode (val)

     Return a tuple ‘(real_value, coded_value)’ from a string
     representation.  ‘real_value’ can be any type.  This method does no
     decoding in *note BaseCookie: 39b2. -- it exists so it can be
     overridden.

 -- 方法: BaseCookie.value_encode (val)

     Return a tuple ‘(real_value, coded_value)’.  'val' can be any type,
     but ‘coded_value’ will always be converted to a string.  This
     method does no encoding in *note BaseCookie: 39b2. -- it exists so
     it can be overridden.

     In general, it should be the case that *note value_encode(): 39b5.
     and *note value_decode(): 39b4. are inverses on the range of
     'value_decode'.

 -- 方法: BaseCookie.output (attrs=None, header='Set-Cookie:',
          sep='\r\n')

     Return a string representation suitable to be sent as HTTP headers.
     'attrs' and 'header' are sent to each *note Morsel: bab.'s *note
     output(): 39b8. method.  'sep' is used to join the headers
     together, and is by default the combination ‘'\r\n'’ (CRLF).

 -- 方法: BaseCookie.js_output (attrs=None)

     Return an embeddable JavaScript snippet, which, if run on a browser
     which supports JavaScript, will act the same as if the HTTP headers
     was sent.

     The meaning for 'attrs' is the same as in *note output(): 39b8.

 -- 方法: BaseCookie.load (rawdata)

     If 'rawdata' is a string, parse it as an ‘HTTP_COOKIE’ and add the
     values found there as *note Morsel: bab.s.  If it is a dictionary,
     it is equivalent to:

          for k, v in rawdata.items():
              cookie[k] = v


File: python.info,  Node: Morsel 物件,  Next: 範例<39>,  Prev: Cookie 物件,  Up: http cookies --- HTTP 狀態管理

5.21.18.2 Morsel 物件
.....................

 -- 類別: http.cookies.Morsel

     Abstract a key/value pair, which has some RFC 2109(1) attributes.

     Morsels are dictionary-like objects, whose set of keys is constant
     -- the valid RFC 2109(2) attributes, which are:

           -- 屬性: expires
           -- 屬性: path
           -- 屬性: comment
           -- 屬性: domain

           -- 屬性: max-age
           -- 屬性: secure
           -- 屬性: version
           -- 屬性: httponly
           -- 屬性: samesite

     The attribute *note httponly: 133e. specifies that the cookie is
     only transferred in HTTP requests, and is not accessible through
     JavaScript.  This is intended to mitigate some forms of cross-site
     scripting.

     The attribute *note samesite: 39c2. specifies that the browser is
     not allowed to send the cookie along with cross-site requests.
     This helps to mitigate CSRF attacks.  Valid values for this
     attribute are "Strict" and "Lax".

     The keys are case-insensitive and their default value is ‘''’.

     在 3.5 版的變更: ‘__eq__()’ now takes *note key: ba8. and *note
     value: ba9. into account.

     在 3.7 版的變更: Attributes *note key: ba8, *note value: ba9. and
     *note coded_value: baa. are read-only.  Use *note set(): bac. for
     setting them.

     在 3.8 版的變更: 新增 *note samesite: 39c2. 屬性的支援

 -- 屬性: Morsel.value

     The value of the cookie.

 -- 屬性: Morsel.coded_value

     The encoded value of the cookie -- this is what should be sent.

 -- 屬性: Morsel.key

     The name of the cookie.

 -- 方法: Morsel.set (key, value, coded_value)

     Set the 'key', 'value' and 'coded_value' attributes.

 -- 方法: Morsel.isReservedKey (K)

     Whether 'K' is a member of the set of keys of a *note Morsel: bab.

 -- 方法: Morsel.output (attrs=None, header='Set-Cookie:')

     Return a string representation of the Morsel, suitable to be sent
     as an HTTP header.  By default, all the attributes are included,
     unless 'attrs' is given, in which case it should be a list of
     attributes to use.  'header' is by default ‘"Set-Cookie:"’.

 -- 方法: Morsel.js_output (attrs=None)

     Return an embeddable JavaScript snippet, which, if run on a browser
     which supports JavaScript, will act the same as if the HTTP header
     was sent.

     The meaning for 'attrs' is the same as in *note output(): 39c4.

 -- 方法: Morsel.OutputString (attrs=None)

     Return a string representing the Morsel, without any surrounding
     HTTP or JavaScript.

     The meaning for 'attrs' is the same as in *note output(): 39c4.

 -- 方法: Morsel.update (values)

     Update the values in the Morsel dictionary with the values in the
     dictionary 'values'.  Raise an error if any of the keys in the
     'values' dict is not a valid RFC 2109(3) attribute.

     在 3.5 版的變更: an error is raised for invalid keys.

 -- 方法: Morsel.copy (value)

     Return a shallow copy of the Morsel object.

     在 3.5 版的變更: return a Morsel object instead of a dict.

 -- 方法: Morsel.setdefault (key, value=None)

     Raise an error if key is not a valid RFC 2109(4) attribute,
     otherwise behave the same as *note dict.setdefault(): 101a.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2109.html

   (2) https://datatracker.ietf.org/doc/html/rfc2109.html

   (3) https://datatracker.ietf.org/doc/html/rfc2109.html

   (4) https://datatracker.ietf.org/doc/html/rfc2109.html


File: python.info,  Node: 範例<39>,  Prev: Morsel 物件,  Up: http cookies --- HTTP 狀態管理

5.21.18.3 範例
..............

The following example demonstrates how to use the *note http.cookies:
67. module.

     >>> from http import cookies
     >>> C = cookies.SimpleCookie()
     >>> C["fig"] = "newton"
     >>> C["sugar"] = "wafer"
     >>> print(C) # generate HTTP headers
     Set-Cookie: fig=newton
     Set-Cookie: sugar=wafer
     >>> print(C.output()) # same thing
     Set-Cookie: fig=newton
     Set-Cookie: sugar=wafer
     >>> C = cookies.SimpleCookie()
     >>> C["rocky"] = "road"
     >>> C["rocky"]["path"] = "/cookie"
     >>> print(C.output(header="Cookie:"))
     Cookie: rocky=road; Path=/cookie
     >>> print(C.output(attrs=[], header="Cookie:"))
     Cookie: rocky=road
     >>> C = cookies.SimpleCookie()
     >>> C.load("chips=ahoy; vienna=finger") # load from a string (HTTP header)
     >>> print(C)
     Set-Cookie: chips=ahoy
     Set-Cookie: vienna=finger
     >>> C = cookies.SimpleCookie()
     >>> C.load('keebler="E=everybody; L=\\"Loves\\"; fudge=\\012;";')
     >>> print(C)
     Set-Cookie: keebler="E=everybody; L=\"Loves\"; fudge=\012;"
     >>> C = cookies.SimpleCookie()
     >>> C["oreo"] = "doublestuff"
     >>> C["oreo"]["path"] = "/"
     >>> print(C)
     Set-Cookie: oreo=doublestuff; Path=/
     >>> C = cookies.SimpleCookie()
     >>> C["twix"] = "none for you"
     >>> C["twix"].value
     'none for you'
     >>> C = cookies.SimpleCookie()
     >>> C["number"] = 7 # equivalent to C["number"] = str(7)
     >>> C["string"] = "seven"
     >>> C["number"].value
     '7'
     >>> C["string"].value
     'seven'
     >>> print(C)
     Set-Cookie: number=7
     Set-Cookie: string=seven


File: python.info,  Node: http cookiejar --- HTTP 客戶端的 Cookie 處理,  Next: xmlrpc --- XMLRPC 伺服器與用戶模組,  Prev: http cookies --- HTTP 狀態管理,  Up: 網路協定 Internet protocols 及支援

5.21.19 ‘http.cookiejar’ -- HTTP 客戶端的 Cookie 處理
-----------------------------------------------------

'原始碼：'Lib/http/cookiejar.py(1)

__________________________________________________________________

The *note http.cookiejar: 66. module defines classes for automatic
handling of HTTP cookies.  It is useful for accessing web sites that
require small pieces of data - 'cookies' - to be set on the client
machine by an HTTP response from a web server, and then returned to the
server in later HTTP requests.

Both the regular Netscape cookie protocol and the protocol defined by
RFC 2965(2) are handled.  RFC 2965 handling is switched off by default.
RFC 2109(3) cookies are parsed as Netscape cookies and subsequently
treated either as Netscape or RFC 2965 cookies according to the 'policy'
in effect.  Note that the great majority of cookies on the internet are
Netscape cookies.  *note http.cookiejar: 66. attempts to follow the
de-facto Netscape cookie protocol (which differs substantially from that
set out in the original Netscape specification), including taking note
of the ‘max-age’ and ‘port’ cookie-attributes introduced with RFC 2965.

     備註: The various named parameters found in ‘Set-Cookie’ and
     ‘Set-Cookie2’ headers (eg.  ‘domain’ and ‘expires’) are
     conventionally referred to as 'attributes'.  To distinguish them
     from Python attributes, the documentation for this module uses the
     term 'cookie-attribute' instead.

The module defines the following exception:

 -- 例外: http.cookiejar.LoadError

     Instances of *note FileCookieJar: 39cd. raise this exception on
     failure to load cookies from a file.  *note LoadError: 39cc. is a
     subclass of *note OSError: 350.

     在 3.3 版的變更: *note LoadError: 39cc. used to be a subtype of
     *note IOError: ff5, which is now an alias of *note OSError: 350.

提供了以下類別：

 -- 類別: http.cookiejar.CookieJar (policy=None)

     'policy' is an object implementing the *note CookiePolicy: 39ce.
     interface.

     The *note CookieJar: 37ff. class stores HTTP cookies.  It extracts
     cookies from HTTP requests, and returns them in HTTP responses.
     *note CookieJar: 37ff. instances automatically expire contained
     cookies when necessary.  Subclasses are also responsible for
     storing and retrieving cookies from a file or database.

 -- 類別: http.cookiejar.FileCookieJar (filename=None, delayload=None,
          policy=None)

     'policy' is an object implementing the *note CookiePolicy: 39ce.
     interface.  For the other arguments, see the documentation for the
     corresponding attributes.

     A *note CookieJar: 37ff. which can load cookies from, and perhaps
     save cookies to, a file on disk.  Cookies are 'NOT' loaded from the
     named file until either the *note load(): 39cf. or *note revert():
     39d0. method is called.  Subclasses of this class are documented in
     section *note FileCookieJar subclasses and co-operation with web
     browsers: 39d1.

     This should not be initialized directly – use its subclasses below
     instead.

     在 3.8 版的變更: The filename parameter supports a *note path-like
     object: ac2.

 -- 類別: http.cookiejar.CookiePolicy

     This class is responsible for deciding whether each cookie should
     be accepted from / returned to the server.

 -- 類別: http.cookiejar.DefaultCookiePolicy (blocked_domains=None,
          allowed_domains=None, netscape=True, rfc2965=False,
          rfc2109_as_netscape=None, hide_cookie2=False,
          strict_domain=False, strict_rfc2965_unverifiable=True,
          strict_ns_unverifiable=False,
          strict_ns_domain=DefaultCookiePolicy.DomainLiberal,
          strict_ns_set_initial_dollar=False, strict_ns_set_path=False,
          secure_protocols=('https', 'wss'))

     Constructor arguments should be passed as keyword arguments only.
     'blocked_domains' is a sequence of domain names that we never
     accept cookies from, nor return cookies to.  'allowed_domains' if
     not *note None: 61b, this is a sequence of the only domains for
     which we accept and return cookies.  'secure_protocols' is a
     sequence of protocols for which secure cookies can be added to.  By
     default 'https' and 'wss' (secure websocket) are considered secure
     protocols.  For all other arguments, see the documentation for
     *note CookiePolicy: 39ce. and *note DefaultCookiePolicy: 1917.
     objects.

     *note DefaultCookiePolicy: 1917. implements the standard accept /
     reject rules for Netscape and RFC 2965(4) cookies.  By default, RFC
     2109(5) cookies (ie.  cookies received in a ‘Set-Cookie’ header
     with a version cookie-attribute of 1) are treated according to the
     RFC 2965 rules.  However, if RFC 2965 handling is turned off or
     *note rfc2109_as_netscape: 39d2. is ‘True’, RFC 2109 cookies are
     'downgraded' by the *note CookieJar: 37ff. instance to Netscape
     cookies, by setting the ‘version’ attribute of the *note Cookie:
     39d3. instance to 0.  *note DefaultCookiePolicy: 1917. also
     provides some parameters to allow some fine-tuning of policy.

 -- 類別: http.cookiejar.Cookie

     This class represents Netscape, RFC 2109(6) and RFC 2965(7)
     cookies.  It is not expected that users of *note http.cookiejar:
     66. construct their own *note Cookie: 39d3. instances.  Instead, if
     necessary, call ‘make_cookies()’ on a *note CookieJar: 37ff.
     instance.

也參考
......

*note urllib.request: f4. 模組

     URL opening with automatic cookie handling.

*note http.cookies: 67. 模組

     HTTP cookie classes, principally useful for server-side code.  The
     *note http.cookiejar: 66. and *note http.cookies: 67. modules do
     not depend on each other.

‘https://curl.se/rfc/cookie_spec.html’

     The specification of the original Netscape cookie protocol.  Though
     this is still the dominant protocol, the 'Netscape cookie protocol'
     implemented by all the major browsers (and *note http.cookiejar:
     66.) only bears a passing resemblance to the one sketched out in
     ‘cookie_spec.html’.

RFC 2109(8) - HTTP State Management Mechanism

     Obsoleted by RFC 2965(9).  Uses ‘Set-Cookie’ with version=1.

RFC 2965(10) - HTTP State Management Mechanism

     The Netscape protocol with the bugs fixed.  Uses ‘Set-Cookie2’ in
     place of ‘Set-Cookie’.  Not widely used.

‘http://kristol.org/cookie/errata.html’

     Unfinished errata to RFC 2965(11).

RFC 2964(12) - Use of HTTP State Management

* Menu:

* CookieJar 與 FileCookieJar 物件::
* FileCookieJar subclasses and co-operation with web browsers::
* CookiePolicy 物件::
* DefaultCookiePolicy 物件::
* Cookie 物件: Cookie 物件<2>.
* 範例: 範例<40>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/http/cookiejar.py

   (2) https://datatracker.ietf.org/doc/html/rfc2965.html

   (3) https://datatracker.ietf.org/doc/html/rfc2109.html

   (4) https://datatracker.ietf.org/doc/html/rfc2965.html

   (5) https://datatracker.ietf.org/doc/html/rfc2109.html

   (6) https://datatracker.ietf.org/doc/html/rfc2109.html

   (7) https://datatracker.ietf.org/doc/html/rfc2965.html

   (8) https://datatracker.ietf.org/doc/html/rfc2109.html

   (9) https://datatracker.ietf.org/doc/html/rfc2965.html

   (10) https://datatracker.ietf.org/doc/html/rfc2965.html

   (11) https://datatracker.ietf.org/doc/html/rfc2965.html

   (12) https://datatracker.ietf.org/doc/html/rfc2964.html


File: python.info,  Node: CookieJar 與 FileCookieJar 物件,  Next: FileCookieJar subclasses and co-operation with web browsers,  Up: http cookiejar --- HTTP 客戶端的 Cookie 處理

5.21.19.1 CookieJar 與 FileCookieJar 物件
.........................................

*note CookieJar: 37ff. objects support the *note iterator: 192. protocol
for iterating over contained *note Cookie: 39d3. objects.

*note CookieJar: 37ff. has the following methods:

 -- 方法: CookieJar.add_cookie_header (request)

     Add correct ‘Cookie’ header to 'request'.

     If policy allows (ie.  the ‘rfc2965’ and ‘hide_cookie2’ attributes
     of the *note CookieJar: 37ff.'s *note CookiePolicy: 39ce. instance
     are true and false respectively), the ‘Cookie2’ header is also
     added when appropriate.

     The 'request' object (usually a *note urllib.request.Request: f7b.
     instance) must support the methods ‘get_full_url()’,
     ‘has_header()’, ‘get_header()’, ‘header_items()’,
     ‘add_unredirected_header()’ and the attributes ‘host’, ‘type’,
     ‘unverifiable’ and ‘origin_req_host’ as documented by *note
     urllib.request: f4.

     在 3.3 版的變更: 'request' object needs ‘origin_req_host’
     attribute.  Dependency on a deprecated method
     ‘get_origin_req_host()’ has been removed.

 -- 方法: CookieJar.extract_cookies (response, request)

     Extract cookies from HTTP 'response' and store them in the *note
     CookieJar: 37ff, where allowed by policy.

     The *note CookieJar: 37ff. will look for allowable ‘Set-Cookie’ and
     ‘Set-Cookie2’ headers in the 'response' argument, and store cookies
     as appropriate (subject to the *note CookiePolicy.set_ok(): 39d8.
     method's approval).

     The 'response' object (usually the result of a call to *note
     urllib.request.urlopen(): 275, or similar) should support an
     ‘info()’ method, which returns an *note email.message.Message: 261.
     instance.

     The 'request' object (usually a *note urllib.request.Request: f7b.
     instance) must support the method ‘get_full_url()’ and the
     attributes ‘host’, ‘unverifiable’ and ‘origin_req_host’, as
     documented by *note urllib.request: f4.  The request is used to set
     default values for cookie-attributes as well as for checking that
     the cookie is allowed to be set.

     在 3.3 版的變更: 'request' object needs ‘origin_req_host’
     attribute.  Dependency on a deprecated method
     ‘get_origin_req_host()’ has been removed.

 -- 方法: CookieJar.set_policy (policy)

     Set the *note CookiePolicy: 39ce. instance to be used.

 -- 方法: CookieJar.make_cookies (response, request)

     Return sequence of *note Cookie: 39d3. objects extracted from
     'response' object.

     See the documentation for *note extract_cookies(): 39d7. for the
     interfaces required of the 'response' and 'request' arguments.

 -- 方法: CookieJar.set_cookie_if_ok (cookie, request)

     Set a *note Cookie: 39d3. if policy says it's OK to do so.

 -- 方法: CookieJar.set_cookie (cookie)

     Set a *note Cookie: 39d3, without checking with policy to see
     whether or not it should be set.

 -- 方法: CookieJar.clear ([domain[, path[, name]]])

     Clear some cookies.

     If invoked without arguments, clear all cookies.  If given a single
     argument, only cookies belonging to that 'domain' will be removed.
     If given two arguments, cookies belonging to the specified 'domain'
     and URL 'path' are removed.  If given three arguments, then the
     cookie with the specified 'domain', 'path' and 'name' is removed.

     Raises *note KeyError: 2fb. if no matching cookie exists.

 -- 方法: CookieJar.clear_session_cookies ()

     Discard all session cookies.

     Discards all contained cookies that have a true ‘discard’ attribute
     (usually because they had either no ‘max-age’ or ‘expires’
     cookie-attribute, or an explicit ‘discard’ cookie-attribute).  For
     interactive browsers, the end of a session usually corresponds to
     closing the browser window.

     Note that the ‘save()’ method won't save session cookies anyway,
     unless you ask otherwise by passing a true 'ignore_discard'
     argument.

*note FileCookieJar: 39cd. implements the following additional methods:

 -- 方法: FileCookieJar.save (filename=None, ignore_discard=False,
          ignore_expires=False)

     Save cookies to a file.

     This base class raises *note NotImplementedError: 20d.  Subclasses
     may leave this method unimplemented.

     'filename' is the name of file in which to save cookies.  If
     'filename' is not specified, ‘self.filename’ is used (whose default
     is the value passed to the constructor, if any); if ‘self.filename’
     is *note None: 61b, *note ValueError: 1e7. is raised.

     'ignore_discard': save even cookies set to be discarded.
     'ignore_expires': save even cookies that have expired

     The file is overwritten if it already exists, thus wiping all the
     cookies it contains.  Saved cookies can be restored later using the
     *note load(): 39cf. or *note revert(): 39d0. methods.

 -- 方法: FileCookieJar.load (filename=None, ignore_discard=False,
          ignore_expires=False)

     Load cookies from a file.

     Old cookies are kept unless overwritten by newly loaded ones.

     Arguments are as for *note save(): 39df.

     The named file must be in the format understood by the class, or
     *note LoadError: 39cc. will be raised.  Also, *note OSError: 350.
     may be raised, for example if the file does not exist.

     在 3.3 版的變更: *note IOError: ff5. used to be raised, it is now
     an alias of *note OSError: 350.

 -- 方法: FileCookieJar.revert (filename=None, ignore_discard=False,
          ignore_expires=False)

     Clear all cookies and reload cookies from a saved file.

     *note revert(): 39d0. can raise the same exceptions as *note
     load(): 39cf.  If there is a failure, the object's state will not
     be altered.

*note FileCookieJar: 39cd. instances have the following public
attributes:

 -- 屬性: FileCookieJar.filename

     Filename of default file in which to keep cookies.  This attribute
     may be assigned to.

 -- 屬性: FileCookieJar.delayload

     If true, load cookies lazily from disk.  This attribute should not
     be assigned to.  This is only a hint, since this only affects
     performance, not behaviour (unless the cookies on disk are
     changing).  A *note CookieJar: 37ff. object may ignore it.  None of
     the *note FileCookieJar: 39cd. classes included in the standard
     library lazily loads cookies.


File: python.info,  Node: FileCookieJar subclasses and co-operation with web browsers,  Next: CookiePolicy 物件,  Prev: CookieJar 與 FileCookieJar 物件,  Up: http cookiejar --- HTTP 客戶端的 Cookie 處理

5.21.19.2 FileCookieJar subclasses and co-operation with web browsers
.....................................................................

The following *note CookieJar: 37ff. subclasses are provided for reading
and writing.

 -- 類別: http.cookiejar.MozillaCookieJar (filename=None,
          delayload=None, policy=None)

     A *note FileCookieJar: 39cd. that can load from and save cookies to
     disk in the Mozilla ‘cookies.txt’ file format (which is also used
     by curl and the Lynx and Netscape browsers).

          備註: This loses information about RFC 2965(1) cookies, and
          also about newer or non-standard cookie-attributes such as
          ‘port’.

          警告: Back up your cookies before saving if you have cookies
          whose loss / corruption would be inconvenient (there are some
          subtleties which may lead to slight changes in the file over a
          load / save round-trip).

     Also note that cookies saved while Mozilla is running will get
     clobbered by Mozilla.

 -- 類別: http.cookiejar.LWPCookieJar (filename=None, delayload=None,
          policy=None)

     A *note FileCookieJar: 39cd. that can load from and save cookies to
     disk in format compatible with the libwww-perl library's
     ‘Set-Cookie3’ file format.  This is convenient if you want to store
     cookies in a human-readable file.

     在 3.8 版的變更: The filename parameter supports a *note path-like
     object: ac2.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2965.html


File: python.info,  Node: CookiePolicy 物件,  Next: DefaultCookiePolicy 物件,  Prev: FileCookieJar subclasses and co-operation with web browsers,  Up: http cookiejar --- HTTP 客戶端的 Cookie 處理

5.21.19.3 CookiePolicy 物件
...........................

Objects implementing the *note CookiePolicy: 39ce. interface have the
following methods:

 -- 方法: CookiePolicy.set_ok (cookie, request)

     Return boolean value indicating whether cookie should be accepted
     from server.

     'cookie' is a *note Cookie: 39d3. instance.  'request' is an object
     implementing the interface defined by the documentation for *note
     CookieJar.extract_cookies(): 39d7.

 -- 方法: CookiePolicy.return_ok (cookie, request)

     Return boolean value indicating whether cookie should be returned
     to server.

     'cookie' is a *note Cookie: 39d3. instance.  'request' is an object
     implementing the interface defined by the documentation for *note
     CookieJar.add_cookie_header(): 39d6.

 -- 方法: CookiePolicy.domain_return_ok (domain, request)

     Return ‘False’ if cookies should not be returned, given cookie
     domain.

     This method is an optimization.  It removes the need for checking
     every cookie with a particular domain (which might involve reading
     many files).  Returning true from *note domain_return_ok(): 39e8.
     and *note path_return_ok(): 39e9. leaves all the work to *note
     return_ok(): 39e7.

     If *note domain_return_ok(): 39e8. returns true for the cookie
     domain, *note path_return_ok(): 39e9. is called for the cookie
     path.  Otherwise, *note path_return_ok(): 39e9. and *note
     return_ok(): 39e7. are never called for that cookie domain.  If
     *note path_return_ok(): 39e9. returns true, *note return_ok():
     39e7. is called with the *note Cookie: 39d3. object itself for a
     full check.  Otherwise, *note return_ok(): 39e7. is never called
     for that cookie path.

     Note that *note domain_return_ok(): 39e8. is called for every
     'cookie' domain, not just for the 'request' domain.  For example,
     the function might be called with both ‘".example.com"’ and
     ‘"www.example.com"’ if the request domain is ‘"www.example.com"’.
     The same goes for *note path_return_ok(): 39e9.

     The 'request' argument is as documented for *note return_ok():
     39e7.

 -- 方法: CookiePolicy.path_return_ok (path, request)

     Return ‘False’ if cookies should not be returned, given cookie
     path.

     關於 *note domain_return_ok(): 39e8. 請見文件。

In addition to implementing the methods above, implementations of the
*note CookiePolicy: 39ce. interface must also supply the following
attributes, indicating which protocols should be used, and how.  All of
these attributes may be assigned to.

 -- 屬性: CookiePolicy.netscape

     Implement Netscape protocol.

 -- 屬性: CookiePolicy.rfc2965

     Implement RFC 2965(1) protocol.

 -- 屬性: CookiePolicy.hide_cookie2

     Don't add ‘Cookie2’ header to requests (the presence of this header
     indicates to the server that we understand RFC 2965(2) cookies).

The most useful way to define a *note CookiePolicy: 39ce. class is by
subclassing from *note DefaultCookiePolicy: 1917. and overriding some or
all of the methods above.  *note CookiePolicy: 39ce. itself may be used
as a 'null policy' to allow setting and receiving any and all cookies
(this is unlikely to be useful).

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2965.html

   (2) https://datatracker.ietf.org/doc/html/rfc2965.html


File: python.info,  Node: DefaultCookiePolicy 物件,  Next: Cookie 物件<2>,  Prev: CookiePolicy 物件,  Up: http cookiejar --- HTTP 客戶端的 Cookie 處理

5.21.19.4 DefaultCookiePolicy 物件
..................................

Implements the standard rules for accepting and returning cookies.

Both RFC 2965(1) and Netscape cookies are covered.  RFC 2965 handling is
switched off by default.

The easiest way to provide your own policy is to override this class and
call its methods in your overridden implementations before adding your
own additional checks:

     import http.cookiejar
     class MyCookiePolicy(http.cookiejar.DefaultCookiePolicy):
         def set_ok(self, cookie, request):
             if not http.cookiejar.DefaultCookiePolicy.set_ok(self, cookie, request):
                 return False
             if i_dont_want_to_store_this_cookie(cookie):
                 return False
             return True

In addition to the features required to implement the *note
CookiePolicy: 39ce. interface, this class allows you to block and allow
domains from setting and receiving cookies.  There are also some
strictness switches that allow you to tighten up the rather loose
Netscape protocol rules a little bit (at the cost of blocking some
benign cookies).

A domain blocklist and allowlist is provided (both off by default).
Only domains not in the blocklist and present in the allowlist (if the
allowlist is active) participate in cookie setting and returning.  Use
the 'blocked_domains' constructor argument, and ‘blocked_domains()’ and
‘set_blocked_domains()’ methods (and the corresponding argument and
methods for 'allowed_domains').  If you set an allowlist, you can turn
it off again by setting it to *note None: 61b.

Domains in block or allow lists that do not start with a dot must equal
the cookie domain to be matched.  For example, ‘"example.com"’ matches a
blocklist entry of ‘"example.com"’, but ‘"www.example.com"’ does not.
Domains that do start with a dot are matched by more specific domains
too.  For example, both ‘"www.example.com"’ and
‘"www.coyote.example.com"’ match ‘".example.com"’ (but ‘"example.com"’
itself does not).  IP addresses are an exception, and must match
exactly.  For example, if blocked_domains contains ‘"192.168.1.2"’ and
‘".168.1.2"’, 192.168.1.2 is blocked, but 193.168.1.2 is not.

*note DefaultCookiePolicy: 1917. implements the following additional
methods:

 -- 方法: DefaultCookiePolicy.blocked_domains ()

     Return the sequence of blocked domains (as a tuple).

 -- 方法: DefaultCookiePolicy.set_blocked_domains (blocked_domains)

     Set the sequence of blocked domains.

 -- 方法: DefaultCookiePolicy.is_blocked (domain)

     Return ‘True’ if 'domain' is on the blocklist for setting or
     receiving cookies.

 -- 方法: DefaultCookiePolicy.allowed_domains ()

     Return *note None: 61b, or the sequence of allowed domains (as a
     tuple).

 -- 方法: DefaultCookiePolicy.set_allowed_domains (allowed_domains)

     Set the sequence of allowed domains, or *note None: 61b.

 -- 方法: DefaultCookiePolicy.is_not_allowed (domain)

     Return ‘True’ if 'domain' is not on the allowlist for setting or
     receiving cookies.

*note DefaultCookiePolicy: 1917. instances have the following
attributes, which are all initialised from the constructor arguments of
the same name, and which may all be assigned to.

 -- 屬性: DefaultCookiePolicy.rfc2109_as_netscape

     If true, request that the *note CookieJar: 37ff. instance downgrade
     RFC 2109(2) cookies (ie.  cookies received in a ‘Set-Cookie’ header
     with a version cookie-attribute of 1) to Netscape cookies by
     setting the version attribute of the *note Cookie: 39d3. instance
     to 0.  The default value is *note None: 61b, in which case RFC 2109
     cookies are downgraded if and only if RFC 2965(3) handling is
     turned off.  Therefore, RFC 2109 cookies are downgraded by default.

General strictness switches:

 -- 屬性: DefaultCookiePolicy.strict_domain

     Don't allow sites to set two-component domains with country-code
     top-level domains like ‘.co.uk’, ‘.gov.uk’, ‘.co.nz’.etc.  This is
     far from perfect and isn't guaranteed to work!

RFC 2965(4) protocol strictness switches:

 -- 屬性: DefaultCookiePolicy.strict_rfc2965_unverifiable

     Follow RFC 2965(5) rules on unverifiable transactions (usually, an
     unverifiable transaction is one resulting from a redirect or a
     request for an image hosted on another site).  If this is false,
     cookies are 'never' blocked on the basis of verifiability

Netscape protocol strictness switches:

 -- 屬性: DefaultCookiePolicy.strict_ns_unverifiable

     Apply RFC 2965(6) rules on unverifiable transactions even to
     Netscape cookies.

 -- 屬性: DefaultCookiePolicy.strict_ns_domain

     Flags indicating how strict to be with domain-matching rules for
     Netscape cookies.  See below for acceptable values.

 -- 屬性: DefaultCookiePolicy.strict_ns_set_initial_dollar

     Ignore cookies in Set-Cookie: headers that have names starting with
     ‘'$'’.

 -- 屬性: DefaultCookiePolicy.strict_ns_set_path

     Don't allow setting cookies whose path doesn't path-match request
     URI.

‘strict_ns_domain’ is a collection of flags.  Its value is constructed
by or-ing together (for example,
‘DomainStrictNoDots|DomainStrictNonDomain’ means both flags are set).

 -- 屬性: DefaultCookiePolicy.DomainStrictNoDots

     When setting cookies, the 'host prefix' must not contain a dot (eg.
     ‘www.foo.bar.com’ can't set a cookie for ‘.bar.com’, because
     ‘www.foo’ contains a dot).

 -- 屬性: DefaultCookiePolicy.DomainStrictNonDomain

     Cookies that did not explicitly specify a ‘domain’ cookie-attribute
     can only be returned to a domain equal to the domain that set the
     cookie (eg.  ‘spam.example.com’ won't be returned cookies from
     ‘example.com’ that had no ‘domain’ cookie-attribute).

 -- 屬性: DefaultCookiePolicy.DomainRFC2965Match

     When setting cookies, require a full RFC 2965(7) domain-match.

The following attributes are provided for convenience, and are the most
useful combinations of the above flags:

 -- 屬性: DefaultCookiePolicy.DomainLiberal

     Equivalent to 0 (ie.  all of the above Netscape domain strictness
     flags switched off).

 -- 屬性: DefaultCookiePolicy.DomainStrict

     等價於 ‘DomainStrictNoDots|DomainStrictNonDomain’。

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2965.html

   (2) https://datatracker.ietf.org/doc/html/rfc2109.html

   (3) https://datatracker.ietf.org/doc/html/rfc2965.html

   (4) https://datatracker.ietf.org/doc/html/rfc2965.html

   (5) https://datatracker.ietf.org/doc/html/rfc2965.html

   (6) https://datatracker.ietf.org/doc/html/rfc2965.html

   (7) https://datatracker.ietf.org/doc/html/rfc2965.html


File: python.info,  Node: Cookie 物件<2>,  Next: 範例<40>,  Prev: DefaultCookiePolicy 物件,  Up: http cookiejar --- HTTP 客戶端的 Cookie 處理

5.21.19.5 Cookie 物件
.....................

*note Cookie: 39d3. instances have Python attributes roughly
corresponding to the standard cookie-attributes specified in the various
cookie standards.  The correspondence is not one-to-one, because there
are complicated rules for assigning default values, because the
‘max-age’ and ‘expires’ cookie-attributes contain equivalent
information, and because RFC 2109(1) cookies may be 'downgraded' by
*note http.cookiejar: 66. from version 1 to version 0 (Netscape)
cookies.

Assignment to these attributes should not be necessary other than in
rare circumstances in a *note CookiePolicy: 39ce. method.  The class
does not enforce internal consistency, so you should know what you're
doing if you do that.

 -- 屬性: Cookie.version

     Integer or *note None: 61b.  Netscape cookies have *note version:
     3a01. 0.  RFC 2965(2) and RFC 2109(3) cookies have a ‘version’
     cookie-attribute of 1.  However, note that *note http.cookiejar:
     66. may 'downgrade' RFC 2109 cookies to Netscape cookies, in which
     case *note version: 3a01. is 0.

 -- 屬性: Cookie.name

     Cookie name (a string).

 -- 屬性: Cookie.value

     Cookie value (a string), or *note None: 61b.

 -- 屬性: Cookie.port

     String representing a port or a set of ports (eg.  '80', or
     '80,8080'), or *note None: 61b.

 -- 屬性: Cookie.domain

     Cookie domain (a string).

 -- 屬性: Cookie.path

     Cookie path (a string, eg.  ‘'/acme/rocket_launchers'’).

 -- 屬性: Cookie.secure

     ‘True’ if cookie should only be returned over a secure connection.

 -- 屬性: Cookie.expires

     Integer expiry date in seconds since epoch, or *note None: 61b.
     See also the *note is_expired(): 3a09. method.

 -- 屬性: Cookie.discard

     ‘True’ if this is a session cookie.

 -- 屬性: Cookie.comment

     String comment from the server explaining the function of this
     cookie, or *note None: 61b.

 -- 屬性: Cookie.comment_url

     URL linking to a comment from the server explaining the function of
     this cookie, or *note None: 61b.

 -- 屬性: Cookie.rfc2109

     ‘True’ if this cookie was received as an RFC 2109(4) cookie (ie.
     the cookie arrived in a ‘Set-Cookie’ header, and the value of the
     Version cookie-attribute in that header was 1).  This attribute is
     provided because *note http.cookiejar: 66. may 'downgrade' RFC 2109
     cookies to Netscape cookies, in which case *note version: 3a01. is
     0.

 -- 屬性: Cookie.port_specified

     ‘True’ if a port or set of ports was explicitly specified by the
     server (in the ‘Set-Cookie’ / ‘Set-Cookie2’ header).

 -- 屬性: Cookie.domain_specified

     ‘True’ if a domain was explicitly specified by the server.

 -- 屬性: Cookie.domain_initial_dot

     ‘True’ if the domain explicitly specified by the server began with
     a dot (‘'.'’).

Cookies may have additional non-standard cookie-attributes.  These may
be accessed using the following methods:

 -- 方法: Cookie.has_nonstandard_attr (name)

     Return ‘True’ if cookie has the named cookie-attribute.

 -- 方法: Cookie.get_nonstandard_attr (name, default=None)

     If cookie has the named cookie-attribute, return its value.
     Otherwise, return 'default'.

 -- 方法: Cookie.set_nonstandard_attr (name, value)

     Set the value of the named cookie-attribute.

The *note Cookie: 39d3. class also defines the following method:

 -- 方法: Cookie.is_expired (now=None)

     ‘True’ if cookie has passed the time at which the server requested
     it should expire.  If 'now' is given (in seconds since the epoch),
     return whether the cookie has expired at the specified time.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2109.html

   (2) https://datatracker.ietf.org/doc/html/rfc2965.html

   (3) https://datatracker.ietf.org/doc/html/rfc2109.html

   (4) https://datatracker.ietf.org/doc/html/rfc2109.html


File: python.info,  Node: 範例<40>,  Prev: Cookie 物件<2>,  Up: http cookiejar --- HTTP 客戶端的 Cookie 處理

5.21.19.6 範例
..............

The first example shows the most common usage of *note http.cookiejar:
66.:

     import http.cookiejar, urllib.request
     cj = http.cookiejar.CookieJar()
     opener = urllib.request.build_opener(urllib.request.HTTPCookieProcessor(cj))
     r = opener.open("http://example.com/")

This example illustrates how to open a URL using your Netscape, Mozilla,
or Lynx cookies (assumes Unix/Netscape convention for location of the
cookies file):

     import os, http.cookiejar, urllib.request
     cj = http.cookiejar.MozillaCookieJar()
     cj.load(os.path.join(os.path.expanduser("~"), ".netscape", "cookies.txt"))
     opener = urllib.request.build_opener(urllib.request.HTTPCookieProcessor(cj))
     r = opener.open("http://example.com/")

The next example illustrates the use of *note DefaultCookiePolicy: 1917.
Turn on RFC 2965(1) cookies, be more strict about domains when setting
and returning Netscape cookies, and block some domains from setting
cookies or having them returned:

     import urllib.request
     from http.cookiejar import CookieJar, DefaultCookiePolicy
     policy = DefaultCookiePolicy(
         rfc2965=True, strict_ns_domain=Policy.DomainStrict,
         blocked_domains=["ads.net", ".ads.net"])
     cj = CookieJar(policy)
     opener = urllib.request.build_opener(urllib.request.HTTPCookieProcessor(cj))
     r = opener.open("http://example.com/")

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2965.html


File: python.info,  Node: xmlrpc --- XMLRPC 伺服器與用戶模組,  Next: xmlrpc client --- XML-RPC 客戶端存取,  Prev: http cookiejar --- HTTP 客戶端的 Cookie 處理,  Up: 網路協定 Internet protocols 及支援

5.21.20 ‘xmlrpc’ -- XMLRPC 伺服器與用戶模組
-------------------------------------------

XML-RPC 是一種遠端程序呼叫 (Remote Procedure Call) 方法，它使用通過 HTTP
傳輸（transport）的 XML 來做傳遞。有了它，用戶端可以在遠端伺服器上呼叫帶
有參數的方法（伺服器以 URI 命名）並獲取結構化的資料。

‘xmlrpc’ 是一個集合了 XML-RPC 伺服器與用戶端模組實作的套件。這些模組是：

   * *note xmlrpc.client: 114.

   * *note xmlrpc.server: 115.


File: python.info,  Node: xmlrpc client --- XML-RPC 客戶端存取,  Next: xmlrpc server --- 基本 XML-RPC 伺服器,  Prev: xmlrpc --- XMLRPC 伺服器與用戶模組,  Up: 網路協定 Internet protocols 及支援

5.21.21 ‘xmlrpc.client’ -- XML-RPC 客戶端存取
---------------------------------------------

'原始碼：'Lib/xmlrpc/client.py(1)

__________________________________________________________________

XML-RPC is a Remote Procedure Call method that uses XML passed via
HTTP(S) as a transport.  With it, a client can call methods with
parameters on a remote server (the server is named by a URI) and get
back structured data.  This module supports writing XML-RPC client code;
it handles all the details of translating between conformable Python
objects and XML on the wire.

     警告: The *note xmlrpc.client: 114. module is not secure against
     maliciously constructed data.  If you need to parse untrusted or
     unauthenticated data see *note XML 漏洞: 3596.

在 3.5 版的變更: For HTTPS URIs, *note xmlrpc.client: 114. now performs
all the necessary certificate and hostname checks by default.

*note Availability: 1c56.: not WASI.

This module does not work or is not available on WebAssembly.  See *note
WebAssembly 平台: 16e6. for more information.

 -- 類別: xmlrpc.client.ServerProxy (uri, transport=None, encoding=None,
          verbose=False, allow_none=False, use_datetime=False,
          use_builtin_types=False, *, headers=(), context=None)

     A *note ServerProxy: 9fa. instance is an object that manages
     communication with a remote XML-RPC server.  The required first
     argument is a URI (Uniform Resource Indicator), and will normally
     be the URL of the server.  The optional second argument is a
     transport factory instance; by default it is an internal
     ‘SafeTransport’ instance for https: URLs and an internal HTTP
     ‘Transport’ instance otherwise.  The optional third argument is an
     encoding, by default UTF-8.  The optional fourth argument is a
     debugging flag.

     The following parameters govern the use of the returned proxy
     instance.  If 'allow_none' is true, the Python constant ‘None’ will
     be translated into XML; the default behaviour is for ‘None’ to
     raise a *note TypeError: 4dd.  This is a commonly used extension to
     the XML-RPC specification, but isn't supported by all clients and
     servers; see http://ontosys.com/xml-rpc/extensions.php(2) for a
     description.  The 'use_builtin_types' flag can be used to cause
     date/time values to be presented as *note datetime.datetime: 1b0.
     objects and binary data to be presented as *note bytes: 1a5.
     objects; this flag is false by default.  *note datetime.datetime:
     1b0, *note bytes: 1a5. and *note bytearray: 4e3. objects may be
     passed to calls.  The 'headers' parameter is an optional sequence
     of HTTP headers to send with each request, expressed as a sequence
     of 2-tuples representing the header name and value.  (e.g.
     ‘[('Header-Name', 'value')]’).  The obsolete 'use_datetime' flag is
     similar to 'use_builtin_types' but it applies only to date/time
     values.

在 3.3 版的變更: 新增 'use_builtin_types' 旗標。

在 3.8 版的變更: 新增 'headers' 參數。

Both the HTTP and HTTPS transports support the URL syntax extension for
HTTP Basic Authentication: ‘http://user:pass@host:port/path’.  The
‘user:pass’ portion will be base64-encoded as an HTTP 'Authorization'
header, and sent to the remote server as part of the connection process
when invoking an XML-RPC method.  You only need to use this if the
remote server requires a Basic Authentication user and password.  If an
HTTPS URL is provided, 'context' may be *note ssl.SSLContext: 276. and
configures the SSL settings of the underlying HTTPS connection.

The returned instance is a proxy object with methods that can be used to
invoke corresponding RPC calls on the remote server.  If the remote
server supports the introspection API, the proxy can also be used to
query the remote server for the methods it supports (service discovery)
and fetch other server-associated metadata.

Types that are conformable (e.g.  that can be marshalled through XML),
include the following (and except where noted, they are unmarshalled as
the same Python type):

XML-RPC type               Python type
                           
---------------------------------------------------------------------------------------
                           
‘boolean’                  *note bool: 40e.
                           
                           
‘int’、‘i1’、‘i2’、        *note int: 23c. in range from -2147483648 to 2147483647.
‘i4’、‘i8’ 或              Values get the ‘<int>’ tag.
‘biginteger’               

‘double’ 或 ‘float’        *note float: 2c8.  Values get the ‘<double>’ tag.
                           
                           
‘string’                   *note str: 3f2.
                           
                           
‘array’                    *note list: 5b6. or *note tuple: 322. containing
                           conformable elements.  Arrays are returned as
                           *note lists: 5b6.
                           
                           
‘struct’                   *note dict: 23b.  Keys must be strings, values may be any
                           conformable type.  Objects of user-defined classes can be
                           passed in; only their *note __dict__: c04. attribute is
                           transmitted.
                           
                           
‘dateTime.iso8601’         *note DateTime: 1351. or *note datetime.datetime: 1b0.
                           Returned type depends on values of 'use_builtin_types'
                           and 'use_datetime' flags.
                           
                           
‘base64’                   *note Binary: 3a19, *note bytes: 1a5. or
                           *note bytearray: 4e3.  Returned type depends on the value
                           of the 'use_builtin_types' flag.
                           
                           
‘nil’                      The ‘None’ constant.  Passing is allowed only if
                           'allow_none' is true.
                           
                           
‘bigdecimal’               *note decimal.Decimal: 27c.  Returned type only.
                           

This is the full set of data types supported by XML-RPC. Method calls
may also raise a special *note Fault: 3a1a. instance, used to signal
XML-RPC server errors, or *note ProtocolError: 3a1b. used to signal an
error in the HTTP/HTTPS transport layer.  Both *note Fault: 3a1a. and
*note ProtocolError: 3a1b. derive from a base class called ‘Error’.
Note that the xmlrpc client module currently does not marshal instances
of subclasses of built-in types.

When passing strings, characters special to XML such as ‘<’, ‘>’, and
‘&’ will be automatically escaped.  However, it's the caller's
responsibility to ensure that the string is free of characters that
aren't allowed in XML, such as the control characters with ASCII values
between 0 and 31 (except, of course, tab, newline and carriage return);
failing to do this will result in an XML-RPC request that isn't
well-formed XML. If you have to pass arbitrary bytes via XML-RPC, use
*note bytes: 1a5. or *note bytearray: 4e3. classes or the *note Binary:
3a19. wrapper class described below.

‘Server’ is retained as an alias for *note ServerProxy: 9fa. for
backwards compatibility.  New code should use *note ServerProxy: 9fa.

在 3.5 版的變更: 加入 'context' 引數。

在 3.6 版的變更: Added support of type tags with prefixes (e.g.
‘ex:nil’).  Added support of unmarshalling additional types used by
Apache XML-RPC implementation for numerics: ‘i1’, ‘i2’, ‘i8’,
‘biginteger’, ‘float’ and ‘bigdecimal’.  See
‘https://ws.apache.org/xmlrpc/types.html’ for a description.

也參考
......

XML-RPC HOWTO(3)

     A good description of XML-RPC operation and client software in
     several languages.  Contains pretty much everything an XML-RPC
     client developer needs to know.

XML-RPC Introspection(4)

     Describes the XML-RPC protocol extension for introspection.

XML-RPC Specification(5)

     The official specification.

* Menu:

* ServerProxy 物件::
* 日期時間物件::
* Binary Objects::
* Fault Objects::
* ProtocolError 物件::
* MultiCall 物件::
* 便捷的函式::
* Example of Client Usage::
* Example of Client and Server Usage::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/xmlrpc/client.py

   (2) 
https://web.archive.org/web/20130120074804/http://ontosys.com/xml-rpc/extensions.php

   (3) https://tldp.org/HOWTO/XML-RPC-HOWTO/index.html

   (4) https://xmlrpc-c.sourceforge.net/introspection.html

   (5) http://xmlrpc.scripting.com/spec.html


File: python.info,  Node: ServerProxy 物件,  Next: 日期時間物件,  Up: xmlrpc client --- XML-RPC 客戶端存取

5.21.21.1 ServerProxy 物件
..........................

A *note ServerProxy: 9fa. instance has a method corresponding to each
remote procedure call accepted by the XML-RPC server.  Calling the
method performs an RPC, dispatched by both name and argument signature
(e.g.  the same method name can be overloaded with multiple argument
signatures).  The RPC finishes by returning a value, which may be either
returned data in a conformant type or a *note Fault: 3a1a. or *note
ProtocolError: 3a1b. object indicating an error.

Servers that support the XML introspection API support some common
methods grouped under the reserved ‘system’ attribute:

 -- 方法: ServerProxy.system.listMethods ()

     This method returns a list of strings, one for each (non-system)
     method supported by the XML-RPC server.

 -- 方法: ServerProxy.system.methodSignature (name)

     This method takes one parameter, the name of a method implemented
     by the XML-RPC server.  It returns an array of possible signatures
     for this method.  A signature is an array of types.  The first of
     these types is the return type of the method, the rest are
     parameters.

     Because multiple signatures (ie.  overloading) is permitted, this
     method returns a list of signatures rather than a singleton.

     Signatures themselves are restricted to the top level parameters
     expected by a method.  For instance if a method expects one array
     of structs as a parameter, and it returns a string, its signature
     is simply "string, array".  If it expects three integers and
     returns a string, its signature is "string, int, int, int".

     If no signature is defined for the method, a non-array value is
     returned.  In Python this means that the type of the returned value
     will be something other than list.

 -- 方法: ServerProxy.system.methodHelp (name)

     This method takes one parameter, the name of a method implemented
     by the XML-RPC server.  It returns a documentation string
     describing the use of that method.  If no such string is available,
     an empty string is returned.  The documentation string may contain
     HTML markup.

在 3.5 版的變更: Instances of *note ServerProxy: 9fa. support the *note
context manager: 576. protocol for closing the underlying transport.

A working example follows.  The server code:

     from xmlrpc.server import SimpleXMLRPCServer

     def is_even(n):
         return n % 2 == 0

     server = SimpleXMLRPCServer(("localhost", 8000))
     print("Listening on port 8000...")
     server.register_function(is_even, "is_even")
     server.serve_forever()

The client code for the preceding server:

     import xmlrpc.client

     with xmlrpc.client.ServerProxy("http://localhost:8000/") as proxy:
         print("3 is even: %s" % str(proxy.is_even(3)))
         print("100 is even: %s" % str(proxy.is_even(100)))


File: python.info,  Node: 日期時間物件,  Next: Binary Objects,  Prev: ServerProxy 物件,  Up: xmlrpc client --- XML-RPC 客戶端存取

5.21.21.2 日期時間物件
......................

 -- 類別: xmlrpc.client.DateTime

     This class may be initialized with seconds since the epoch, a time
     tuple, an ISO 8601 time/date string, or a *note datetime.datetime:
     1b0. instance.  It has the following methods, supported mainly for
     internal use by the marshalling/unmarshalling code:

      -- 方法: decode (string)

          Accept a string as the instance's new time value.

      -- 方法: encode (out)

          Write the XML-RPC encoding of this *note DateTime: 1351. item
          to the 'out' stream object.

     It also supports certain of Python's built-in operators through
     *note rich comparison: 129e. and *note __repr__(): 5c2. methods.

A working example follows.  The server code:

     import datetime
     from xmlrpc.server import SimpleXMLRPCServer
     import xmlrpc.client

     def today():
         today = datetime.datetime.today()
         return xmlrpc.client.DateTime(today)

     server = SimpleXMLRPCServer(("localhost", 8000))
     print("Listening on port 8000...")
     server.register_function(today, "today")
     server.serve_forever()

The client code for the preceding server:

     import xmlrpc.client
     import datetime

     proxy = xmlrpc.client.ServerProxy("http://localhost:8000/")

     today = proxy.today()
     # 將 ISO8601 字串轉換成 datetime 物件
     converted = datetime.datetime.strptime(today.value, "%Y%m%dT%H:%M:%S")
     print("Today: %s" % converted.strftime("%d.%m.%Y, %H:%M"))


File: python.info,  Node: Binary Objects,  Next: Fault Objects,  Prev: 日期時間物件,  Up: xmlrpc client --- XML-RPC 客戶端存取

5.21.21.3 Binary Objects
........................

 -- 類別: xmlrpc.client.Binary

     This class may be initialized from bytes data (which may include
     NULs).  The primary access to the content of a *note Binary: 3a19.
     object is provided by an attribute:

      -- 屬性: data

          The binary data encapsulated by the *note Binary: 3a19.
          instance.  The data is provided as a *note bytes: 1a5. object.

     *note Binary: 3a19. objects have the following methods, supported
     mainly for internal use by the marshalling/unmarshalling code:

      -- 方法: decode (bytes)

          Accept a base64 *note bytes: 1a5. object and decode it as the
          instance's new data.

      -- 方法: encode (out)

          Write the XML-RPC base 64 encoding of this binary item to the
          'out' stream object.

          The encoded data will have newlines every 76 characters as per
          RFC 2045 section 6.8(1), which was the de facto standard
          base64 specification when the XML-RPC spec was written.

     It also supports certain of Python's built-in operators through
     *note __eq__(): a9d. and *note __ne__(): 1486. methods.

Example usage of the binary objects.  We're going to transfer an image
over XMLRPC:

     from xmlrpc.server import SimpleXMLRPCServer
     import xmlrpc.client

     def python_logo():
         with open("python_logo.jpg", "rb") as handle:
             return xmlrpc.client.Binary(handle.read())

     server = SimpleXMLRPCServer(("localhost", 8000))
     print("Listening on port 8000...")
     server.register_function(python_logo, 'python_logo')

     server.serve_forever()

The client gets the image and saves it to a file:

     import xmlrpc.client

     proxy = xmlrpc.client.ServerProxy("http://localhost:8000/")
     with open("fetched_python_logo.jpg", "wb") as handle:
         handle.write(proxy.python_logo().data)

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2045.html#section-6.8


File: python.info,  Node: Fault Objects,  Next: ProtocolError 物件,  Prev: Binary Objects,  Up: xmlrpc client --- XML-RPC 客戶端存取

5.21.21.4 Fault Objects
.......................

 -- 類別: xmlrpc.client.Fault

     A *note Fault: 3a1a. object encapsulates the content of an XML-RPC
     fault tag.  Fault objects have the following attributes:

      -- 屬性: faultCode

          An int indicating the fault type.

      -- 屬性: faultString

          A string containing a diagnostic message associated with the
          fault.

In the following example we're going to intentionally cause a *note
Fault: 3a1a. by returning a complex type object.  The server code:

     from xmlrpc.server import SimpleXMLRPCServer

     # A marshalling error is going to occur because we're returning a
     # complex number
     def add(x, y):
         return x+y+0j

     server = SimpleXMLRPCServer(("localhost", 8000))
     print("Listening on port 8000...")
     server.register_function(add, 'add')

     server.serve_forever()

The client code for the preceding server:

     import xmlrpc.client

     proxy = xmlrpc.client.ServerProxy("http://localhost:8000/")
     try:
         proxy.add(2, 5)
     except xmlrpc.client.Fault as err:
         print("A fault occurred")
         print("Fault code: %d" % err.faultCode)
         print("Fault string: %s" % err.faultString)


File: python.info,  Node: ProtocolError 物件,  Next: MultiCall 物件,  Prev: Fault Objects,  Up: xmlrpc client --- XML-RPC 客戶端存取

5.21.21.5 ProtocolError 物件
............................

 -- 類別: xmlrpc.client.ProtocolError

     A *note ProtocolError: 3a1b. object describes a protocol error in
     the underlying transport layer (such as a 404 'not found' error if
     the server named by the URI does not exist).  It has the following
     attributes:

      -- 屬性: url

          The URI or URL that triggered the error.

      -- 屬性: errcode

          The error code.

      -- 屬性: errmsg

          The error message or diagnostic string.

      -- 屬性: headers

          A dict containing the headers of the HTTP/HTTPS request that
          triggered the error.

In the following example we're going to intentionally cause a *note
ProtocolError: 3a1b. by providing an invalid URI:

     import xmlrpc.client

     # create a ServerProxy with a URI that doesn't respond to XMLRPC requests
     proxy = xmlrpc.client.ServerProxy("http://google.com/")

     try:
         proxy.some_method()
     except xmlrpc.client.ProtocolError as err:
         print("A protocol error occurred")
         print("URL: %s" % err.url)
         print("HTTP/HTTPS headers: %s" % err.headers)
         print("Error code: %d" % err.errcode)
         print("Error message: %s" % err.errmsg)


File: python.info,  Node: MultiCall 物件,  Next: 便捷的函式,  Prev: ProtocolError 物件,  Up: xmlrpc client --- XML-RPC 客戶端存取

5.21.21.6 MultiCall 物件
........................

The *note MultiCall: 3a35. object provides a way to encapsulate multiple
calls to a remote server into a single request (1).

 -- 類別: xmlrpc.client.MultiCall (server)

     Create an object used to boxcar method calls.  'server' is the
     eventual target of the call.  Calls can be made to the result
     object, but they will immediately return ‘None’, and only store the
     call name and parameters in the *note MultiCall: 3a35. object.
     Calling the object itself causes all stored calls to be transmitted
     as a single ‘system.multicall’ request.  The result of this call is
     a *note generator: 1004.; iterating over this generator yields the
     individual results.

A usage example of this class follows.  The server code:

     from xmlrpc.server import SimpleXMLRPCServer

     def add(x, y):
         return x + y

     def subtract(x, y):
         return x - y

     def multiply(x, y):
         return x * y

     def divide(x, y):
         return x // y

     # A simple server with simple arithmetic functions
     server = SimpleXMLRPCServer(("localhost", 8000))
     print("Listening on port 8000...")
     server.register_multicall_functions()
     server.register_function(add, 'add')
     server.register_function(subtract, 'subtract')
     server.register_function(multiply, 'multiply')
     server.register_function(divide, 'divide')
     server.serve_forever()

The client code for the preceding server:

     import xmlrpc.client

     proxy = xmlrpc.client.ServerProxy("http://localhost:8000/")
     multicall = xmlrpc.client.MultiCall(proxy)
     multicall.add(7, 3)
     multicall.subtract(7, 3)
     multicall.multiply(7, 3)
     multicall.divide(7, 3)
     result = multicall()

     print("7+3=%d, 7-3=%d, 7*3=%d, 7//3=%d" % tuple(result))

   ---------- Footnotes ----------

   (1) This approach has been first presented in a discussion on
xmlrpc.com
(https://web.archive.org/web/20060624230303/http://www.xmlrpc.com/discuss/msgReader$1208?mode=topic).


File: python.info,  Node: 便捷的函式,  Next: Example of Client Usage,  Prev: MultiCall 物件,  Up: xmlrpc client --- XML-RPC 客戶端存取

5.21.21.7 便捷的函式
....................

 -- 函式: xmlrpc.client.dumps (params, methodname=None,
          methodresponse=None, encoding=None, allow_none=False)

     Convert 'params' into an XML-RPC request.  or into a response if
     'methodresponse' is true.  'params' can be either a tuple of
     arguments or an instance of the *note Fault: 3a1a. exception class.
     If 'methodresponse' is true, only a single value can be returned,
     meaning that 'params' must be of length 1.  'encoding', if
     supplied, is the encoding to use in the generated XML; the default
     is UTF-8.  Python's *note None: 61b. value cannot be used in
     standard XML-RPC; to allow using it via an extension, provide a
     true value for 'allow_none'.

 -- 函式: xmlrpc.client.loads (data, use_datetime=False,
          use_builtin_types=False)

     Convert an XML-RPC request or response into Python objects, a
     ‘(params, methodname)’.  'params' is a tuple of argument;
     'methodname' is a string, or ‘None’ if no method name is present in
     the packet.  If the XML-RPC packet represents a fault condition,
     this function will raise a *note Fault: 3a1a. exception.  The
     'use_builtin_types' flag can be used to cause date/time values to
     be presented as *note datetime.datetime: 1b0. objects and binary
     data to be presented as *note bytes: 1a5. objects; this flag is
     false by default.

     The obsolete 'use_datetime' flag is similar to 'use_builtin_types'
     but it applies only to date/time values.

     在 3.3 版的變更: 新增 'use_builtin_types' 旗標。


File: python.info,  Node: Example of Client Usage,  Next: Example of Client and Server Usage,  Prev: 便捷的函式,  Up: xmlrpc client --- XML-RPC 客戶端存取

5.21.21.8 Example of Client Usage
.................................

     # simple test program (from the XML-RPC specification)
     from xmlrpc.client import ServerProxy, Error

     # server = ServerProxy("http://localhost:8000") # local server
     with ServerProxy("http://betty.userland.com") as proxy:

         print(proxy)

         try:
             print(proxy.examples.getStateName(41))
         except Error as v:
             print("ERROR", v)

To access an XML-RPC server through a HTTP proxy, you need to define a
custom transport.  The following example shows how:

     import http.client
     import xmlrpc.client

     class ProxiedTransport(xmlrpc.client.Transport):

         def set_proxy(self, host, port=None, headers=None):
             self.proxy = host, port
             self.proxy_headers = headers

         def make_connection(self, host):
             connection = http.client.HTTPConnection(*self.proxy)
             connection.set_tunnel(host, headers=self.proxy_headers)
             self._connection = host, connection
             return connection

     transport = ProxiedTransport()
     transport.set_proxy('proxy-server', 8080)
     server = xmlrpc.client.ServerProxy('http://betty.userland.com', transport=transport)
     print(server.examples.getStateName(41))


File: python.info,  Node: Example of Client and Server Usage,  Prev: Example of Client Usage,  Up: xmlrpc client --- XML-RPC 客戶端存取

5.21.21.9 Example of Client and Server Usage
............................................

See *note SimpleXMLRPCServer 範例: 3a3b.


File: python.info,  Node: xmlrpc server --- 基本 XML-RPC 伺服器,  Next: ipaddress --- IPv4/IPv6 操作函式庫,  Prev: xmlrpc client --- XML-RPC 客戶端存取,  Up: 網路協定 Internet protocols 及支援

5.21.22 ‘xmlrpc.server’ -- 基本 XML-RPC 伺服器
----------------------------------------------

'原始碼：'Lib/xmlrpc/server.py(1)

__________________________________________________________________

The *note xmlrpc.server: 115. module provides a basic server framework
for XML-RPC servers written in Python.  Servers can either be free
standing, using *note SimpleXMLRPCServer: 3a3e, or embedded in a CGI
environment, using *note CGIXMLRPCRequestHandler: 3a3f.

     警告: The *note xmlrpc.server: 115. module is not secure against
     maliciously constructed data.  If you need to parse untrusted or
     unauthenticated data see *note XML 漏洞: 3596.

*note Availability: 1c56.: not WASI.

This module does not work or is not available on WebAssembly.  See *note
WebAssembly 平台: 16e6. for more information.

 -- 類別: xmlrpc.server.SimpleXMLRPCServer (addr,
          requestHandler=SimpleXMLRPCRequestHandler, logRequests=True,
          allow_none=False, encoding=None, bind_and_activate=True,
          use_builtin_types=False)

     Create a new server instance.  This class provides methods for
     registration of functions that can be called by the XML-RPC
     protocol.  The 'requestHandler' parameter should be a factory for
     request handler instances; it defaults to *note
     SimpleXMLRPCRequestHandler: 12bb.  The 'addr' and 'requestHandler'
     parameters are passed to the *note socketserver.TCPServer: 12b3.
     constructor.  If 'logRequests' is true (the default), requests will
     be logged; setting this parameter to false will turn off logging.
     The 'allow_none' and 'encoding' parameters are passed on to *note
     xmlrpc.client: 114. and control the XML-RPC responses that will be
     returned from the server.  The 'bind_and_activate' parameter
     controls whether ‘server_bind()’ and ‘server_activate()’ are called
     immediately by the constructor; it defaults to true.  Setting it to
     false allows code to manipulate the 'allow_reuse_address' class
     variable before the address is bound.  The 'use_builtin_types'
     parameter is passed to the *note loads(): 13a2. function and
     controls which types are processed when date/times values or binary
     data are received; it defaults to false.

     在 3.3 版的變更: The 'use_builtin_types' flag was added.

 -- 類別: xmlrpc.server.CGIXMLRPCRequestHandler (allow_none=False,
          encoding=None, use_builtin_types=False)

     Create a new instance to handle XML-RPC requests in a CGI
     environment.  The 'allow_none' and 'encoding' parameters are passed
     on to *note xmlrpc.client: 114. and control the XML-RPC responses
     that will be returned from the server.  The 'use_builtin_types'
     parameter is passed to the *note loads(): 13a2. function and
     controls which types are processed when date/times values or binary
     data are received; it defaults to false.

     在 3.3 版的變更: The 'use_builtin_types' flag was added.

 -- 類別: xmlrpc.server.SimpleXMLRPCRequestHandler

     Create a new request handler instance.  This request handler
     supports ‘POST’ requests and modifies logging so that the
     'logRequests' parameter to the *note SimpleXMLRPCServer: 3a3e.
     constructor parameter is honored.

* Menu:

* SimpleXMLRPCServer 物件::
* CGIXMLRPCRequestHandler::
* Documenting XMLRPC server::
* DocXMLRPCServer 物件::
* DocCGIXMLRPCRequestHandler::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/xmlrpc/server.py


File: python.info,  Node: SimpleXMLRPCServer 物件,  Next: CGIXMLRPCRequestHandler,  Up: xmlrpc server --- 基本 XML-RPC 伺服器

5.21.22.1 SimpleXMLRPCServer 物件
.................................

The *note SimpleXMLRPCServer: 3a3e. class is based on *note
socketserver.TCPServer: 12b3. and provides a means of creating simple,
stand alone XML-RPC servers.

 -- 方法: SimpleXMLRPCServer.register_function (function=None,
          name=None)

     Register a function that can respond to XML-RPC requests.  If
     'name' is given, it will be the method name associated with
     'function', otherwise *note function.__name__: 1267. will be used.
     'name' is a string, and may contain characters not legal in Python
     identifiers, including the period character.

     This method can also be used as a decorator.  When used as a
     decorator, 'name' can only be given as a keyword argument to
     register 'function' under 'name'.  If no 'name' is given, *note
     function.__name__: 1267. will be used.

     在 3.7 版的變更: *note register_function(): 3a42. 也可被當作裝飾器
     使用。

 -- 方法: SimpleXMLRPCServer.register_instance (instance,
          allow_dotted_names=False)

     Register an object which is used to expose method names which have
     not been registered using *note register_function(): 3a42.  If
     'instance' contains a ‘_dispatch()’ method, it is called with the
     requested method name and the parameters from the request.  Its API
     is ‘def _dispatch(self, method, params)’ (note that 'params' does
     not represent a variable argument list).  If it calls an underlying
     function to perform its task, that function is called as
     ‘func(*params)’, expanding the parameter list.  The return value
     from ‘_dispatch()’ is returned to the client as the result.  If
     'instance' does not have a ‘_dispatch()’ method, it is searched for
     an attribute matching the name of the requested method.

     If the optional 'allow_dotted_names' argument is true and the
     instance does not have a ‘_dispatch()’ method, then if the
     requested method name contains periods, each component of the
     method name is searched for individually, with the effect that a
     simple hierarchical search is performed.  The value found from this
     search is then called with the parameters from the request, and the
     return value is passed back to the client.

          警告: Enabling the 'allow_dotted_names' option allows
          intruders to access your module's global variables and may
          allow intruders to execute arbitrary code on your machine.
          Only use this option on a secure, closed network.

 -- 方法: SimpleXMLRPCServer.register_introspection_functions ()

     Registers the XML-RPC introspection functions ‘system.listMethods’,
     ‘system.methodHelp’ and ‘system.methodSignature’.

 -- 方法: SimpleXMLRPCServer.register_multicall_functions ()

     Registers the XML-RPC multicall function system.multicall.

 -- 屬性: SimpleXMLRPCRequestHandler.rpc_paths

     An attribute value that must be a tuple listing valid path portions
     of the URL for receiving XML-RPC requests.  Requests posted to
     other paths will result in a 404 "no such page" HTTP error.  If
     this tuple is empty, all paths will be considered valid.  The
     default value is ‘('/', '/RPC2')’.

* Menu:

* SimpleXMLRPCServer 範例::


File: python.info,  Node: SimpleXMLRPCServer 範例,  Up: SimpleXMLRPCServer 物件

5.21.22.2 SimpleXMLRPCServer 範例
.................................

Server code:

     from xmlrpc.server import SimpleXMLRPCServer
     from xmlrpc.server import SimpleXMLRPCRequestHandler

     # Restrict to a particular path.
     class RequestHandler(SimpleXMLRPCRequestHandler):
         rpc_paths = ('/RPC2',)

     # Create server
     with SimpleXMLRPCServer(('localhost', 8000),
                             requestHandler=RequestHandler) as server:
         server.register_introspection_functions()

         # Register pow() function; this will use the value of
         # pow.__name__ as the name, which is just 'pow'.
         server.register_function(pow)

         # Register a function under a different name
         def adder_function(x, y):
             return x + y
         server.register_function(adder_function, 'add')

         # Register an instance; all the methods of the instance are
         # published as XML-RPC methods (in this case, just 'mul').
         class MyFuncs:
             def mul(self, x, y):
                 return x * y

         server.register_instance(MyFuncs())

         # Run the server's main loop
         server.serve_forever()

The following client code will call the methods made available by the
preceding server:

     import xmlrpc.client

     s = xmlrpc.client.ServerProxy('http://localhost:8000')
     print(s.pow(2,3))  # Returns 2**3 = 8
     print(s.add(2,3))  # Returns 5
     print(s.mul(5,2))  # Returns 5*2 = 10

     # Print list of available methods
     print(s.system.listMethods())

‘register_function()’ can also be used as a decorator.  The previous
server example can register functions in a decorator way:

     from xmlrpc.server import SimpleXMLRPCServer
     from xmlrpc.server import SimpleXMLRPCRequestHandler

     class RequestHandler(SimpleXMLRPCRequestHandler):
         rpc_paths = ('/RPC2',)

     with SimpleXMLRPCServer(('localhost', 8000),
                             requestHandler=RequestHandler) as server:
         server.register_introspection_functions()

         # Register pow() function; this will use the value of
         # pow.__name__ as the name, which is just 'pow'.
         server.register_function(pow)

         # Register a function under a different name, using
         # register_function as a decorator. *name* can only be given
         # as a keyword argument.
         @server.register_function(name='add')
         def adder_function(x, y):
             return x + y

         # Register a function under function.__name__.
         @server.register_function
         def mul(x, y):
             return x * y

         server.serve_forever()

The following example included in the ‘Lib/xmlrpc/server.py’ module
shows a server allowing dotted names and registering a multicall
function.

     警告: Enabling the 'allow_dotted_names' option allows intruders to
     access your module's global variables and may allow intruders to
     execute arbitrary code on your machine.  Only use this example only
     within a secure, closed network.

     import datetime

     class ExampleService:
         def getData(self):
             return '42'

         class currentTime:
             @staticmethod
             def getCurrentTime():
                 return datetime.datetime.now()

     with SimpleXMLRPCServer(("localhost", 8000)) as server:
         server.register_function(pow)
         server.register_function(lambda x,y: x+y, 'add')
         server.register_instance(ExampleService(), allow_dotted_names=True)
         server.register_multicall_functions()
         print('Serving XML-RPC on localhost port 8000')
         try:
             server.serve_forever()
         except KeyboardInterrupt:
             print("\nKeyboard interrupt received, exiting.")
             sys.exit(0)

This ExampleService demo can be invoked from the command line:

     python -m xmlrpc.server

The client that interacts with the above server is included in
‘Lib/xmlrpc/client.py’:

     server = ServerProxy("http://localhost:8000")

     try:
         print(server.currentTime.getCurrentTime())
     except Error as v:
         print("ERROR", v)

     multi = MultiCall(server)
     multi.getData()
     multi.pow(2,9)
     multi.add(1,2)
     try:
         for response in multi():
             print(response)
     except Error as v:
         print("ERROR", v)

This client which interacts with the demo XMLRPC server can be invoked
as:

     python -m xmlrpc.client


File: python.info,  Node: CGIXMLRPCRequestHandler,  Next: Documenting XMLRPC server,  Prev: SimpleXMLRPCServer 物件,  Up: xmlrpc server --- 基本 XML-RPC 伺服器

5.21.22.3 CGIXMLRPCRequestHandler
.................................

The *note CGIXMLRPCRequestHandler: 3a3f. class can be used to handle
XML-RPC requests sent to Python CGI scripts.

 -- 方法: CGIXMLRPCRequestHandler.register_function (function=None,
          name=None)

     Register a function that can respond to XML-RPC requests.  If
     'name' is given, it will be the method name associated with
     'function', otherwise *note function.__name__: 1267. will be used.
     'name' is a string, and may contain characters not legal in Python
     identifiers, including the period character.

     This method can also be used as a decorator.  When used as a
     decorator, 'name' can only be given as a keyword argument to
     register 'function' under 'name'.  If no 'name' is given, *note
     function.__name__: 1267. will be used.

     在 3.7 版的變更: *note register_function(): 3a49. 也可被當作裝飾器
     使用。

 -- 方法: CGIXMLRPCRequestHandler.register_instance (instance)

     Register an object which is used to expose method names which have
     not been registered using *note register_function(): 3a49.  If
     instance contains a ‘_dispatch()’ method, it is called with the
     requested method name and the parameters from the request; the
     return value is returned to the client as the result.  If instance
     does not have a ‘_dispatch()’ method, it is searched for an
     attribute matching the name of the requested method; if the
     requested method name contains periods, each component of the
     method name is searched for individually, with the effect that a
     simple hierarchical search is performed.  The value found from this
     search is then called with the parameters from the request, and the
     return value is passed back to the client.

 -- 方法: CGIXMLRPCRequestHandler.register_introspection_functions ()

     Register the XML-RPC introspection functions ‘system.listMethods’,
     ‘system.methodHelp’ and ‘system.methodSignature’.

 -- 方法: CGIXMLRPCRequestHandler.register_multicall_functions ()

     Register the XML-RPC multicall function ‘system.multicall’.

 -- 方法: CGIXMLRPCRequestHandler.handle_request (request_text=None)

     Handle an XML-RPC request.  If 'request_text' is given, it should
     be the POST data provided by the HTTP server, otherwise the
     contents of stdin will be used.

範例：

     class MyFuncs:
         def mul(self, x, y):
             return x * y


     handler = CGIXMLRPCRequestHandler()
     handler.register_function(pow)
     handler.register_function(lambda x,y: x+y, 'add')
     handler.register_introspection_functions()
     handler.register_instance(MyFuncs())
     handler.handle_request()


File: python.info,  Node: Documenting XMLRPC server,  Next: DocXMLRPCServer 物件,  Prev: CGIXMLRPCRequestHandler,  Up: xmlrpc server --- 基本 XML-RPC 伺服器

5.21.22.4 Documenting XMLRPC server
...................................

These classes extend the above classes to serve HTML documentation in
response to HTTP GET requests.  Servers can either be free standing,
using *note DocXMLRPCServer: 18c3, or embedded in a CGI environment,
using *note DocCGIXMLRPCRequestHandler: 3a4f.

 -- 類別: xmlrpc.server.DocXMLRPCServer (addr,
          requestHandler=DocXMLRPCRequestHandler, logRequests=True,
          allow_none=False, encoding=None, bind_and_activate=True,
          use_builtin_types=True)

     Create a new server instance.  All parameters have the same meaning
     as for *note SimpleXMLRPCServer: 3a3e.; 'requestHandler' defaults
     to *note DocXMLRPCRequestHandler: 3a50.

     在 3.3 版的變更: The 'use_builtin_types' flag was added.

 -- 類別: xmlrpc.server.DocCGIXMLRPCRequestHandler

     Create a new instance to handle XML-RPC requests in a CGI
     environment.

 -- 類別: xmlrpc.server.DocXMLRPCRequestHandler

     Create a new request handler instance.  This request handler
     supports XML-RPC POST requests, documentation GET requests, and
     modifies logging so that the 'logRequests' parameter to the *note
     DocXMLRPCServer: 18c3. constructor parameter is honored.


File: python.info,  Node: DocXMLRPCServer 物件,  Next: DocCGIXMLRPCRequestHandler,  Prev: Documenting XMLRPC server,  Up: xmlrpc server --- 基本 XML-RPC 伺服器

5.21.22.5 DocXMLRPCServer 物件
..............................

The *note DocXMLRPCServer: 18c3. class is derived from *note
SimpleXMLRPCServer: 3a3e. and provides a means of creating
self-documenting, stand alone XML-RPC servers.  HTTP POST requests are
handled as XML-RPC method calls.  HTTP GET requests are handled by
generating pydoc-style HTML documentation.  This allows a server to
provide its own web-based documentation.

 -- 方法: DocXMLRPCServer.set_server_title (server_title)

     Set the title used in the generated HTML documentation.  This title
     will be used inside the HTML "title" element.

 -- 方法: DocXMLRPCServer.set_server_name (server_name)

     Set the name used in the generated HTML documentation.  This name
     will appear at the top of the generated documentation inside a "h1"
     element.

 -- 方法: DocXMLRPCServer.set_server_documentation
          (server_documentation)

     Set the description used in the generated HTML documentation.  This
     description will appear as a paragraph, below the server name, in
     the documentation.


File: python.info,  Node: DocCGIXMLRPCRequestHandler,  Prev: DocXMLRPCServer 物件,  Up: xmlrpc server --- 基本 XML-RPC 伺服器

5.21.22.6 DocCGIXMLRPCRequestHandler
....................................

The *note DocCGIXMLRPCRequestHandler: 3a4f. class is derived from *note
CGIXMLRPCRequestHandler: 3a3f. and provides a means of creating
self-documenting, XML-RPC CGI scripts.  HTTP POST requests are handled
as XML-RPC method calls.  HTTP GET requests are handled by generating
pydoc-style HTML documentation.  This allows a server to provide its own
web-based documentation.

 -- 方法: DocCGIXMLRPCRequestHandler.set_server_title (server_title)

     Set the title used in the generated HTML documentation.  This title
     will be used inside the HTML "title" element.

 -- 方法: DocCGIXMLRPCRequestHandler.set_server_name (server_name)

     Set the name used in the generated HTML documentation.  This name
     will appear at the top of the generated documentation inside a "h1"
     element.

 -- 方法: DocCGIXMLRPCRequestHandler.set_server_documentation
          (server_documentation)

     Set the description used in the generated HTML documentation.  This
     description will appear as a paragraph, below the server name, in
     the documentation.


File: python.info,  Node: ipaddress --- IPv4/IPv6 操作函式庫,  Prev: xmlrpc server --- 基本 XML-RPC 伺服器,  Up: 網路協定 Internet protocols 及支援

5.21.23 ‘ipaddress’ -- IPv4/IPv6 操作函式庫
-------------------------------------------

'原始碼：'Lib/ipaddress.py(1)

__________________________________________________________________

*note ipaddress: 74. provides the capabilities to create, manipulate and
operate on IPv4 and IPv6 addresses and networks.

The functions and classes in this module make it straightforward to
handle various tasks related to IP addresses, including checking whether
or not two hosts are on the same subnet, iterating over all hosts in a
particular subnet, checking whether or not a string represents a valid
IP address or network definition, and so on.

This is the full module API reference—for an overview and introduction,
see *note ipaddress 模組介紹: 3a5c.

在 3.3 版被加入.

* Menu:

* Convenience factory functions::
* IP Addresses::
* IP Network definitions::
* Interface objects::
* Other Module Level Functions::
* Custom Exceptions::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/ipaddress.py


File: python.info,  Node: Convenience factory functions,  Next: IP Addresses,  Up: ipaddress --- IPv4/IPv6 操作函式庫

5.21.23.1 Convenience factory functions
.......................................

The *note ipaddress: 74. module provides factory functions to
conveniently create IP addresses, networks and interfaces:

 -- 函式: ipaddress.ip_address (address)

     Return an *note IPv4Address: 1e1. or *note IPv6Address: 1e2. object
     depending on the IP address passed as argument.  Either IPv4 or
     IPv6 addresses may be supplied; integers less than ‘2**32’ will be
     considered to be IPv4 by default.  A *note ValueError: 1e7. is
     raised if 'address' does not represent a valid IPv4 or IPv6
     address.

          >>> ipaddress.ip_address('192.168.0.1')
          IPv4Address('192.168.0.1')
          >>> ipaddress.ip_address('2001:db8::')
          IPv6Address('2001:db8::')

 -- 函式: ipaddress.ip_network (address, strict=True)

     Return an *note IPv4Network: 1e3. or *note IPv6Network: 1e4. object
     depending on the IP address passed as argument.  'address' is a
     string or integer representing the IP network.  Either IPv4 or IPv6
     networks may be supplied; integers less than ‘2**32’ will be
     considered to be IPv4 by default.  'strict' is passed to *note
     IPv4Network: 1e3. or *note IPv6Network: 1e4. constructor.  A *note
     ValueError: 1e7. is raised if 'address' does not represent a valid
     IPv4 or IPv6 address, or if the network has host bits set.

          >>> ipaddress.ip_network('192.168.0.0/28')
          IPv4Network('192.168.0.0/28')

 -- 函式: ipaddress.ip_interface (address)

     Return an *note IPv4Interface: 1713. or *note IPv6Interface: 1714.
     object depending on the IP address passed as argument.  'address'
     is a string or integer representing the IP address.  Either IPv4 or
     IPv6 addresses may be supplied; integers less than ‘2**32’ will be
     considered to be IPv4 by default.  A *note ValueError: 1e7. is
     raised if 'address' does not represent a valid IPv4 or IPv6
     address.

One downside of these convenience functions is that the need to handle
both IPv4 and IPv6 formats means that error messages provide minimal
information on the precise error, as the functions don't know whether
the IPv4 or IPv6 format was intended.  More detailed error reporting can
be obtained by calling the appropriate version specific class
constructors directly.


File: python.info,  Node: IP Addresses,  Next: IP Network definitions,  Prev: Convenience factory functions,  Up: ipaddress --- IPv4/IPv6 操作函式庫

5.21.23.2 IP Addresses
......................

* Menu:

* Address objects::
* Conversion to Strings and Integers::
* Operators: Operators<2>.


File: python.info,  Node: Address objects,  Next: Conversion to Strings and Integers,  Up: IP Addresses

5.21.23.3 Address objects
.........................

The *note IPv4Address: 1e1. and *note IPv6Address: 1e2. objects share a
lot of common attributes.  Some attributes that are only meaningful for
IPv6 addresses are also implemented by *note IPv4Address: 1e1. objects,
in order to make it easier to write code that handles both IP versions
correctly.  Address objects are *note hashable: 5b5, so they can be used
as keys in dictionaries.

 -- 類別: ipaddress.IPv4Address (address)

     Construct an IPv4 address.  An *note AddressValueError: 3a63. is
     raised if 'address' is not a valid IPv4 address.

     The following constitutes a valid IPv4 address:

       1. A string in decimal-dot notation, consisting of four decimal
          integers in the inclusive range 0-255, separated by dots (e.g.
          ‘192.168.0.1’).  Each integer represents an octet (byte) in
          the address.  Leading zeroes are not tolerated to prevent
          confusion with octal notation.

       2. An integer that fits into 32 bits.

       3. An integer packed into a *note bytes: 1a5. object of length 4
          (most significant octet first).

          >>> ipaddress.IPv4Address('192.168.0.1')
          IPv4Address('192.168.0.1')
          >>> ipaddress.IPv4Address(3232235521)
          IPv4Address('192.168.0.1')
          >>> ipaddress.IPv4Address(b'\xC0\xA8\x00\x01')
          IPv4Address('192.168.0.1')

     在 3.8 版的變更: Leading zeros are tolerated, even in ambiguous
     cases that look like octal notation.

     在 3.9.5 版的變更: Leading zeros are no longer tolerated and are
     treated as an error.  IPv4 address strings are now parsed as strict
     as glibc *note inet_pton(): 906.

      -- 屬性: version

          The appropriate version number: ‘4’ for IPv4, ‘6’ for IPv6.

      -- 屬性: max_prefixlen

          The total number of bits in the address representation for
          this version: ‘32’ for IPv4, ‘128’ for IPv6.

          The prefix defines the number of leading bits in an address
          that are compared to determine whether or not an address is
          part of a network.

      -- 屬性: compressed

      -- 屬性: exploded

          The string representation in dotted decimal notation.  Leading
          zeroes are never included in the representation.

          As IPv4 does not define a shorthand notation for addresses
          with octets set to zero, these two attributes are always the
          same as ‘str(addr)’ for IPv4 addresses.  Exposing these
          attributes makes it easier to write display code that can
          handle both IPv4 and IPv6 addresses.

      -- 屬性: packed

          The binary representation of this address - a *note bytes:
          1a5. object of the appropriate length (most significant octet
          first).  This is 4 bytes for IPv4 and 16 bytes for IPv6.

      -- 屬性: reverse_pointer

          The name of the reverse DNS PTR record for the IP address,
          e.g.:

               >>> ipaddress.ip_address("127.0.0.1").reverse_pointer
               '1.0.0.127.in-addr.arpa'
               >>> ipaddress.ip_address("2001:db8::1").reverse_pointer
               '1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa'

          This is the name that could be used for performing a PTR
          lookup, not the resolved hostname itself.

          在 3.5 版被加入.

      -- 屬性: is_multicast

          ‘True’ if the address is reserved for multicast use.  See RFC
          3171(1) (for IPv4) or RFC 2373(2) (for IPv6).

      -- 屬性: is_private

          ‘True’ if the address is defined as not globally reachable by
          iana-ipv4-special-registry(3) (for IPv4) or
          iana-ipv6-special-registry(4) (for IPv6) with the following
          exceptions:

             * ‘is_private’ is ‘False’ for the shared address space
               (‘100.64.0.0/10’)

             * For IPv4-mapped IPv6-addresses the ‘is_private’ value is
               determined by the semantics of the underlying IPv4
               addresses and the following condition holds (see *note
               IPv6Address.ipv4_mapped: 3a6b.):

                    address.is_private == address.ipv4_mapped.is_private

          ‘is_private’ has value opposite to *note is_global: f02,
          except for the shared address space (‘100.64.0.0/10’ range)
          where they are both ‘False’.

          在 3.13 版的變更: Fixed some false positives and false
          negatives.

             * ‘192.0.0.0/24’ is considered private with the exception
               of ‘192.0.0.9/32’ and ‘192.0.0.10/32’ (previously: only
               the ‘192.0.0.0/29’ sub-range was considered private).

             * ‘64:ff9b:1::/48’ is considered private.

             * ‘2002::/16’ is considered private.

             * There are exceptions within ‘2001::/23’ (otherwise
               considered private): ‘2001:1::1/128’, ‘2001:1::2/128’,
               ‘2001:3::/32’, ‘2001:4:112::/48’, ‘2001:20::/28’,
               ‘2001:30::/28’.  The exceptions are not considered
               private.

      -- 屬性: is_global

          ‘True’ if the address is defined as globally reachable by
          iana-ipv4-special-registry(5) (for IPv4) or
          iana-ipv6-special-registry(6) (for IPv6) with the following
          exception:

          For IPv4-mapped IPv6-addresses the ‘is_private’ value is
          determined by the semantics of the underlying IPv4 addresses
          and the following condition holds (see *note
          IPv6Address.ipv4_mapped: 3a6b.):

               address.is_global == address.ipv4_mapped.is_global

          ‘is_global’ has value opposite to *note is_private: 153d,
          except for the shared address space (‘100.64.0.0/10’ range)
          where they are both ‘False’.

          在 3.4 版被加入.

          在 3.13 版的變更: Fixed some false positives and false
          negatives, see *note is_private: 153d. for details.

      -- 屬性: is_unspecified

          ‘True’ if the address is unspecified.  See RFC 5735(7) (for
          IPv4) or RFC 2373(8) (for IPv6).

      -- 屬性: is_reserved

          ‘True’ if the address is otherwise IETF reserved.

      -- 屬性: is_loopback

          ‘True’ if this is a loopback address.  See RFC 3330(9) (for
          IPv4) or RFC 2373(10) (for IPv6).

      -- 屬性: is_link_local

          ‘True’ if the address is reserved for link-local usage.  See
          RFC 3927(11).

      -- 屬性: ipv6_mapped

          *note IPv4Address: 1e1. object representing the IPv4-mapped
          IPv6 address.  See RFC 4291(12).

          在 3.13 版被加入.

 -- 方法: IPv4Address.__format__ (fmt)

     Returns a string representation of the IP address, controlled by an
     explicit format string.  'fmt' can be one of the following: ‘'s'’,
     the default option, equivalent to *note str(): 3f2, ‘'b'’ for a
     zero-padded binary string, ‘'X'’ or ‘'x'’ for an uppercase or
     lowercase hexadecimal representation, or ‘'n'’, which is equivalent
     to ‘'b'’ for IPv4 addresses and ‘'x'’ for IPv6.  For binary and
     hexadecimal representations, the form specifier ‘'#'’ and the
     grouping option ‘'_'’ are available.  ‘__format__’ is used by
     ‘format’, ‘str.format’ and f-strings.

          >>> format(ipaddress.IPv4Address('192.168.0.1'))
          '192.168.0.1'
          >>> '{:#b}'.format(ipaddress.IPv4Address('192.168.0.1'))
          '0b11000000101010000000000000000001'
          >>> f'{ipaddress.IPv6Address("2001:db8::1000"):s}'
          '2001:db8::1000'
          >>> format(ipaddress.IPv6Address('2001:db8::1000'), '_X')
          '2001_0DB8_0000_0000_0000_0000_0000_1000'
          >>> '{:#_n}'.format(ipaddress.IPv6Address('2001:db8::1000'))
          '0x2001_0db8_0000_0000_0000_0000_0000_1000'

     在 3.9 版被加入.

 -- 類別: ipaddress.IPv6Address (address)

     Construct an IPv6 address.  An *note AddressValueError: 3a63. is
     raised if 'address' is not a valid IPv6 address.

     The following constitutes a valid IPv6 address:

       1. A string consisting of eight groups of four hexadecimal
          digits, each group representing 16 bits.  The groups are
          separated by colons.  This describes an 'exploded' (longhand)
          notation.  The string can also be 'compressed' (shorthand
          notation) by various means.  See RFC 4291(13) for details.
          For example, ‘"0000:0000:0000:0000:0000:0abc:0007:0def"’ can
          be compressed to ‘"::abc:7:def"’.

          Optionally, the string may also have a scope zone ID,
          expressed with a suffix ‘%scope_id’.  If present, the scope ID
          must be non-empty, and may not contain ‘%’.  See RFC 4007(14)
          for details.  For example, ‘fe80::1234%1’ might identify
          address ‘fe80::1234’ on the first link of the node.

       2. An integer that fits into 128 bits.

       3. An integer packed into a *note bytes: 1a5. object of length
          16, big-endian.

          >>> ipaddress.IPv6Address('2001:db8::1000')
          IPv6Address('2001:db8::1000')
          >>> ipaddress.IPv6Address('ff02::5678%1')
          IPv6Address('ff02::5678%1')

      -- 屬性: compressed

     The short form of the address representation, with leading zeroes
     in groups omitted and the longest sequence of groups consisting
     entirely of zeroes collapsed to a single empty group.

     This is also the value returned by ‘str(addr)’ for IPv6 addresses.

      -- 屬性: exploded

     The long form of the address representation, with all leading
     zeroes and groups consisting entirely of zeroes included.

     For the following attributes and methods, see the corresponding
     documentation of the *note IPv4Address: 1e1. class:

      -- 屬性: packed

      -- 屬性: reverse_pointer

      -- 屬性: version

      -- 屬性: max_prefixlen

      -- 屬性: is_multicast

      -- 屬性: is_private

      -- 屬性: is_global

          在 3.4 版被加入.

      -- 屬性: is_unspecified

      -- 屬性: is_reserved

      -- 屬性: is_loopback

      -- 屬性: is_link_local

      -- 屬性: is_site_local

          ‘True’ if the address is reserved for site-local usage.  Note
          that the site-local address space has been deprecated by RFC
          3879(15).  Use *note is_private: 153d. to test if this address
          is in the space of unique local addresses as defined by RFC
          4193(16).

      -- 屬性: ipv4_mapped

          For addresses that appear to be IPv4 mapped addresses
          (starting with ‘::FFFF/96’), this property will report the
          embedded IPv4 address.  For any other address, this property
          will be ‘None’.

      -- 屬性: scope_id

          For scoped addresses as defined by RFC 4007(17), this property
          identifies the particular zone of the address's scope that the
          address belongs to, as a string.  When no scope zone is
          specified, this property will be ‘None’.

      -- 屬性: sixtofour

          For addresses that appear to be 6to4 addresses (starting with
          ‘2002::/16’) as defined by RFC 3056(18), this property will
          report the embedded IPv4 address.  For any other address, this
          property will be ‘None’.

      -- 屬性: teredo

          For addresses that appear to be Teredo addresses (starting
          with ‘2001::/32’) as defined by RFC 4380(19), this property
          will report the embedded ‘(server, client)’ IP address pair.
          For any other address, this property will be ‘None’.

 -- 方法: IPv6Address.__format__ (fmt)

     Refer to the corresponding method documentation in *note
     IPv4Address: 1e1.

     在 3.9 版被加入.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc3171.html

   (2) https://datatracker.ietf.org/doc/html/rfc2373.html

   (3) 
https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml

   (4) 
https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml

   (5) 
https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml

   (6) 
https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml

   (7) https://datatracker.ietf.org/doc/html/rfc5735.html

   (8) https://datatracker.ietf.org/doc/html/rfc2373.html

   (9) https://datatracker.ietf.org/doc/html/rfc3330.html

   (10) https://datatracker.ietf.org/doc/html/rfc2373.html

   (11) https://datatracker.ietf.org/doc/html/rfc3927.html

   (12) https://datatracker.ietf.org/doc/html/rfc4291.html

   (13) https://datatracker.ietf.org/doc/html/rfc4291.html

   (14) https://datatracker.ietf.org/doc/html/rfc4007.html

   (15) https://datatracker.ietf.org/doc/html/rfc3879.html

   (16) https://datatracker.ietf.org/doc/html/rfc4193.html

   (17) https://datatracker.ietf.org/doc/html/rfc4007.html

   (18) https://datatracker.ietf.org/doc/html/rfc3056.html

   (19) https://datatracker.ietf.org/doc/html/rfc4380.html


File: python.info,  Node: Conversion to Strings and Integers,  Next: Operators<2>,  Prev: Address objects,  Up: IP Addresses

5.21.23.4 Conversion to Strings and Integers
............................................

To interoperate with networking interfaces such as the socket module,
addresses must be converted to strings or integers.  This is handled
using the *note str(): 3f2. and *note int(): 23c. builtin functions:

     >>> str(ipaddress.IPv4Address('192.168.0.1'))
     '192.168.0.1'
     >>> int(ipaddress.IPv4Address('192.168.0.1'))
     3232235521
     >>> str(ipaddress.IPv6Address('::1'))
     '::1'
     >>> int(ipaddress.IPv6Address('::1'))
     1

Note that IPv6 scoped addresses are converted to integers without scope
zone ID.


File: python.info,  Node: Operators<2>,  Prev: Conversion to Strings and Integers,  Up: IP Addresses

5.21.23.5 Operators
...................

Address objects support some operators.  Unless stated otherwise,
operators can only be applied between compatible objects (i.e.  IPv4
with IPv4, IPv6 with IPv6).

* Menu:

* Comparison operators::
* Arithmetic operators::


File: python.info,  Node: Comparison operators,  Next: Arithmetic operators,  Up: Operators<2>

5.21.23.6 Comparison operators
..............................

Address objects can be compared with the usual set of comparison
operators.  Same IPv6 addresses with different scope zone IDs are not
equal.  Some examples:

     >>> IPv4Address('127.0.0.2') > IPv4Address('127.0.0.1')
     True
     >>> IPv4Address('127.0.0.2') == IPv4Address('127.0.0.1')
     False
     >>> IPv4Address('127.0.0.2') != IPv4Address('127.0.0.1')
     True
     >>> IPv6Address('fe80::1234') == IPv6Address('fe80::1234%1')
     False
     >>> IPv6Address('fe80::1234%1') != IPv6Address('fe80::1234%2')
     True


File: python.info,  Node: Arithmetic operators,  Prev: Comparison operators,  Up: Operators<2>

5.21.23.7 Arithmetic operators
..............................

Integers can be added to or subtracted from address objects.  Some
examples:

     >>> IPv4Address('127.0.0.2') + 3
     IPv4Address('127.0.0.5')
     >>> IPv4Address('127.0.0.2') - 3
     IPv4Address('126.255.255.255')
     >>> IPv4Address('255.255.255.255') + 1
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     ipaddress.AddressValueError: 4294967296 (>= 2**32) is not permitted as an IPv4 address


File: python.info,  Node: IP Network definitions,  Next: Interface objects,  Prev: IP Addresses,  Up: ipaddress --- IPv4/IPv6 操作函式庫

5.21.23.8 IP Network definitions
................................

The *note IPv4Network: 1e3. and *note IPv6Network: 1e4. objects provide
a mechanism for defining and inspecting IP network definitions.  A
network definition consists of a 'mask' and a 'network address', and as
such defines a range of IP addresses that equal the network address when
masked (binary AND) with the mask.  For example, a network definition
with the mask ‘255.255.255.0’ and the network address ‘192.168.1.0’
consists of IP addresses in the inclusive range ‘192.168.1.0’ to
‘192.168.1.255’.

* Menu:

* Prefix, net mask and host mask: Prefix net mask and host mask.
* Network objects::
* Operators: Operators<3>.


File: python.info,  Node: Prefix net mask and host mask,  Next: Network objects,  Up: IP Network definitions

5.21.23.9 Prefix, net mask and host mask
........................................

There are several equivalent ways to specify IP network masks.  A
'prefix' ‘/<nbits>’ is a notation that denotes how many high-order bits
are set in the network mask.  A 'net mask' is an IP address with some
number of high-order bits set.  Thus the prefix ‘/24’ is equivalent to
the net mask ‘255.255.255.0’ in IPv4, or ‘ffff:ff00::’ in IPv6.  In
addition, a 'host mask' is the logical inverse of a 'net mask', and is
sometimes used (for example in Cisco access control lists) to denote a
network mask.  The host mask equivalent to ‘/24’ in IPv4 is ‘0.0.0.255’.


File: python.info,  Node: Network objects,  Next: Operators<3>,  Prev: Prefix net mask and host mask,  Up: IP Network definitions

5.21.23.10 Network objects
..........................

All attributes implemented by address objects are implemented by network
objects as well.  In addition, network objects implement additional
attributes.  All of these are common between *note IPv4Network: 1e3. and
*note IPv6Network: 1e4, so to avoid duplication they are only documented
for *note IPv4Network: 1e3.  Network objects are *note hashable: 5b5, so
they can be used as keys in dictionaries.

 -- 類別: ipaddress.IPv4Network (address, strict=True)

     Construct an IPv4 network definition.  'address' can be one of the
     following:

       1. A string consisting of an IP address and an optional mask,
          separated by a slash (‘/’).  The IP address is the network
          address, and the mask can be either a single number, which
          means it's a 'prefix', or a string representation of an IPv4
          address.  If it's the latter, the mask is interpreted as a
          'net mask' if it starts with a non-zero field, or as a 'host
          mask' if it starts with a zero field, with the single
          exception of an all-zero mask which is treated as a 'net
          mask'.  If no mask is provided, it's considered to be ‘/32’.

          For example, the following 'address' specifications are
          equivalent: ‘192.168.1.0/24’, ‘192.168.1.0/255.255.255.0’ and
          ‘192.168.1.0/0.0.0.255’.

       2. An integer that fits into 32 bits.  This is equivalent to a
          single-address network, with the network address being
          'address' and the mask being ‘/32’.

       3. An integer packed into a *note bytes: 1a5. object of length 4,
          big-endian.  The interpretation is similar to an integer
          'address'.

       4. A two-tuple of an address description and a netmask, where the
          address description is either a string, a 32-bits integer, a
          4-bytes packed integer, or an existing IPv4Address object; and
          the netmask is either an integer representing the prefix
          length (e.g.  ‘24’) or a string representing the prefix mask
          (e.g.  ‘255.255.255.0’).

     An *note AddressValueError: 3a63. is raised if 'address' is not a
     valid IPv4 address.  A *note NetmaskValueError: 3a85. is raised if
     the mask is not valid for an IPv4 address.

     If 'strict' is ‘True’ and host bits are set in the supplied
     address, then *note ValueError: 1e7. is raised.  Otherwise, the
     host bits are masked out to determine the appropriate network
     address.

     Unless stated otherwise, all network methods accepting other
     network/address objects will raise *note TypeError: 4dd. if the
     argument's IP version is incompatible to ‘self’.

     在 3.5 版的變更: Added the two-tuple form for the 'address'
     constructor parameter.

      -- 屬性: version

      -- 屬性: max_prefixlen

          Refer to the corresponding attribute documentation in *note
          IPv4Address: 1e1.

      -- 屬性: is_multicast

      -- 屬性: is_private

      -- 屬性: is_unspecified

      -- 屬性: is_reserved

      -- 屬性: is_loopback

      -- 屬性: is_link_local

          These attributes are true for the network as a whole if they
          are true for both the network address and the broadcast
          address.

      -- 屬性: network_address

          The network address for the network.  The network address and
          the prefix length together uniquely define a network.

      -- 屬性: broadcast_address

          The broadcast address for the network.  Packets sent to the
          broadcast address should be received by every host on the
          network.

      -- 屬性: hostmask

          The host mask, as an *note IPv4Address: 1e1. object.

      -- 屬性: netmask

          The net mask, as an *note IPv4Address: 1e1. object.

      -- 屬性: with_prefixlen

      -- 屬性: compressed

      -- 屬性: exploded

          A string representation of the network, with the mask in
          prefix notation.

          ‘with_prefixlen’ and ‘compressed’ are always the same as
          ‘str(network)’.  ‘exploded’ uses the exploded form the network
          address.

      -- 屬性: with_netmask

          A string representation of the network, with the mask in net
          mask notation.

      -- 屬性: with_hostmask

          A string representation of the network, with the mask in host
          mask notation.

      -- 屬性: num_addresses

          The total number of addresses in the network.

      -- 屬性: prefixlen

          Length of the network prefix, in bits.

      -- 方法: hosts ()

          Returns an iterator over the usable hosts in the network.  The
          usable hosts are all the IP addresses that belong to the
          network, except the network address itself and the network
          broadcast address.  For networks with a mask length of 31, the
          network address and network broadcast address are also
          included in the result.  Networks with a mask of 32 will
          return a list containing the single host address.

               >>> list(ip_network('192.0.2.0/29').hosts())
               [IPv4Address('192.0.2.1'), IPv4Address('192.0.2.2'),
                IPv4Address('192.0.2.3'), IPv4Address('192.0.2.4'),
                IPv4Address('192.0.2.5'), IPv4Address('192.0.2.6')]
               >>> list(ip_network('192.0.2.0/31').hosts())
               [IPv4Address('192.0.2.0'), IPv4Address('192.0.2.1')]
               >>> list(ip_network('192.0.2.1/32').hosts())
               [IPv4Address('192.0.2.1')]

      -- 方法: overlaps (other)

          ‘True’ if this network is partly or wholly contained in
          'other' or 'other' is wholly contained in this network.

      -- 方法: address_exclude (network)

          Computes the network definitions resulting from removing the
          given 'network' from this one.  Returns an iterator of network
          objects.  Raises *note ValueError: 1e7. if 'network' is not
          completely contained in this network.

               >>> n1 = ip_network('192.0.2.0/28')
               >>> n2 = ip_network('192.0.2.1/32')
               >>> list(n1.address_exclude(n2))
               [IPv4Network('192.0.2.8/29'), IPv4Network('192.0.2.4/30'),
                IPv4Network('192.0.2.2/31'), IPv4Network('192.0.2.0/32')]

      -- 方法: subnets (prefixlen_diff=1, new_prefix=None)

          The subnets that join to make the current network definition,
          depending on the argument values.  'prefixlen_diff' is the
          amount our prefix length should be increased by.  'new_prefix'
          is the desired new prefix of the subnets; it must be larger
          than our prefix.  One and only one of 'prefixlen_diff' and
          'new_prefix' must be set.  Returns an iterator of network
          objects.

               >>> list(ip_network('192.0.2.0/24').subnets())
               [IPv4Network('192.0.2.0/25'), IPv4Network('192.0.2.128/25')]
               >>> list(ip_network('192.0.2.0/24').subnets(prefixlen_diff=2))
               [IPv4Network('192.0.2.0/26'), IPv4Network('192.0.2.64/26'),
                IPv4Network('192.0.2.128/26'), IPv4Network('192.0.2.192/26')]
               >>> list(ip_network('192.0.2.0/24').subnets(new_prefix=26))
               [IPv4Network('192.0.2.0/26'), IPv4Network('192.0.2.64/26'),
                IPv4Network('192.0.2.128/26'), IPv4Network('192.0.2.192/26')]
               >>> list(ip_network('192.0.2.0/24').subnets(new_prefix=23))
               Traceback (most recent call last):
                 File "<stdin>", line 1, in <module>
                   raise ValueError('new prefix must be longer')
               ValueError: new prefix must be longer
               >>> list(ip_network('192.0.2.0/24').subnets(new_prefix=25))
               [IPv4Network('192.0.2.0/25'), IPv4Network('192.0.2.128/25')]

      -- 方法: supernet (prefixlen_diff=1, new_prefix=None)

          The supernet containing this network definition, depending on
          the argument values.  'prefixlen_diff' is the amount our
          prefix length should be decreased by.  'new_prefix' is the
          desired new prefix of the supernet; it must be smaller than
          our prefix.  One and only one of 'prefixlen_diff' and
          'new_prefix' must be set.  Returns a single network object.

               >>> ip_network('192.0.2.0/24').supernet()
               IPv4Network('192.0.2.0/23')
               >>> ip_network('192.0.2.0/24').supernet(prefixlen_diff=2)
               IPv4Network('192.0.0.0/22')
               >>> ip_network('192.0.2.0/24').supernet(new_prefix=20)
               IPv4Network('192.0.0.0/20')

      -- 方法: subnet_of (other)

          Return ‘True’ if this network is a subnet of 'other'.

               >>> a = ip_network('192.168.1.0/24')
               >>> b = ip_network('192.168.1.128/30')
               >>> b.subnet_of(a)
               True

          在 3.7 版被加入.

      -- 方法: supernet_of (other)

          Return ‘True’ if this network is a supernet of 'other'.

               >>> a = ip_network('192.168.1.0/24')
               >>> b = ip_network('192.168.1.128/30')
               >>> a.supernet_of(b)
               True

          在 3.7 版被加入.

      -- 方法: compare_networks (other)

          Compare this network to 'other'.  In this comparison only the
          network addresses are considered; host bits aren't.  Returns
          either ‘-1’, ‘0’ or ‘1’.

               >>> ip_network('192.0.2.1/32').compare_networks(ip_network('192.0.2.2/32'))
               -1
               >>> ip_network('192.0.2.1/32').compare_networks(ip_network('192.0.2.0/32'))
               1
               >>> ip_network('192.0.2.1/32').compare_networks(ip_network('192.0.2.1/32'))
               0

          在 3.7 版之後被棄用: It uses the same ordering and comparison
          algorithm as "<", "==", and ">"

 -- 類別: ipaddress.IPv6Network (address, strict=True)

     Construct an IPv6 network definition.  'address' can be one of the
     following:

       1. A string consisting of an IP address and an optional prefix
          length, separated by a slash (‘/’).  The IP address is the
          network address, and the prefix length must be a single
          number, the 'prefix'.  If no prefix length is provided, it's
          considered to be ‘/128’.

          Note that currently expanded netmasks are not supported.  That
          means ‘2001:db00::0/24’ is a valid argument while
          ‘2001:db00::0/ffff:ff00::’ is not.

       2. An integer that fits into 128 bits.  This is equivalent to a
          single-address network, with the network address being
          'address' and the mask being ‘/128’.

       3. An integer packed into a *note bytes: 1a5. object of length
          16, big-endian.  The interpretation is similar to an integer
          'address'.

       4. A two-tuple of an address description and a netmask, where the
          address description is either a string, a 128-bits integer, a
          16-bytes packed integer, or an existing IPv6Address object;
          and the netmask is an integer representing the prefix length.

     An *note AddressValueError: 3a63. is raised if 'address' is not a
     valid IPv6 address.  A *note NetmaskValueError: 3a85. is raised if
     the mask is not valid for an IPv6 address.

     If 'strict' is ‘True’ and host bits are set in the supplied
     address, then *note ValueError: 1e7. is raised.  Otherwise, the
     host bits are masked out to determine the appropriate network
     address.

     在 3.5 版的變更: Added the two-tuple form for the 'address'
     constructor parameter.

      -- 屬性: version

      -- 屬性: max_prefixlen

      -- 屬性: is_multicast

      -- 屬性: is_private

      -- 屬性: is_unspecified

      -- 屬性: is_reserved

      -- 屬性: is_loopback

      -- 屬性: is_link_local

      -- 屬性: network_address

      -- 屬性: broadcast_address

      -- 屬性: hostmask

      -- 屬性: netmask

      -- 屬性: with_prefixlen

      -- 屬性: compressed

      -- 屬性: exploded

      -- 屬性: with_netmask

      -- 屬性: with_hostmask

      -- 屬性: num_addresses

      -- 屬性: prefixlen

      -- 方法: hosts ()

          Returns an iterator over the usable hosts in the network.  The
          usable hosts are all the IP addresses that belong to the
          network, except the Subnet-Router anycast address.  For
          networks with a mask length of 127, the Subnet-Router anycast
          address is also included in the result.  Networks with a mask
          of 128 will return a list containing the single host address.

      -- 方法: overlaps (other)

      -- 方法: address_exclude (network)

      -- 方法: subnets (prefixlen_diff=1, new_prefix=None)

      -- 方法: supernet (prefixlen_diff=1, new_prefix=None)

      -- 方法: subnet_of (other)

      -- 方法: supernet_of (other)

      -- 方法: compare_networks (other)

          Refer to the corresponding attribute documentation in *note
          IPv4Network: 1e3.

      -- 屬性: is_site_local

          These attribute is true for the network as a whole if it is
          true for both the network address and the broadcast address.


File: python.info,  Node: Operators<3>,  Prev: Network objects,  Up: IP Network definitions

5.21.23.11 Operators
....................

Network objects support some operators.  Unless stated otherwise,
operators can only be applied between compatible objects (i.e.  IPv4
with IPv4, IPv6 with IPv6).

* Menu:

* Logical operators::
* Iteration::
* Networks as containers of addresses::


File: python.info,  Node: Logical operators,  Next: Iteration,  Up: Operators<3>

5.21.23.12 Logical operators
............................

Network objects can be compared with the usual set of logical operators.
Network objects are ordered first by network address, then by net mask.


File: python.info,  Node: Iteration,  Next: Networks as containers of addresses,  Prev: Logical operators,  Up: Operators<3>

5.21.23.13 Iteration
....................

Network objects can be iterated to list all the addresses belonging to
the network.  For iteration, 'all' hosts are returned, including
unusable hosts (for usable hosts, use the *note hosts(): 3a99. method).
An example:

     >>> for addr in IPv4Network('192.0.2.0/28'):
     ...     addr
     ...
     IPv4Address('192.0.2.0')
     IPv4Address('192.0.2.1')
     IPv4Address('192.0.2.2')
     IPv4Address('192.0.2.3')
     IPv4Address('192.0.2.4')
     IPv4Address('192.0.2.5')
     IPv4Address('192.0.2.6')
     IPv4Address('192.0.2.7')
     IPv4Address('192.0.2.8')
     IPv4Address('192.0.2.9')
     IPv4Address('192.0.2.10')
     IPv4Address('192.0.2.11')
     IPv4Address('192.0.2.12')
     IPv4Address('192.0.2.13')
     IPv4Address('192.0.2.14')
     IPv4Address('192.0.2.15')


File: python.info,  Node: Networks as containers of addresses,  Prev: Iteration,  Up: Operators<3>

5.21.23.14 Networks as containers of addresses
..............................................

Network objects can act as containers of addresses.  Some examples:

     >>> IPv4Network('192.0.2.0/28')[0]
     IPv4Address('192.0.2.0')
     >>> IPv4Network('192.0.2.0/28')[15]
     IPv4Address('192.0.2.15')
     >>> IPv4Address('192.0.2.6') in IPv4Network('192.0.2.0/28')
     True
     >>> IPv4Address('192.0.3.6') in IPv4Network('192.0.2.0/28')
     False


File: python.info,  Node: Interface objects,  Next: Other Module Level Functions,  Prev: IP Network definitions,  Up: ipaddress --- IPv4/IPv6 操作函式庫

5.21.23.15 Interface objects
............................

Interface objects are *note hashable: 5b5, so they can be used as keys
in dictionaries.

 -- 類別: ipaddress.IPv4Interface (address)

     Construct an IPv4 interface.  The meaning of 'address' is as in the
     constructor of *note IPv4Network: 1e3, except that arbitrary host
     addresses are always accepted.

     *note IPv4Interface: 1713. is a subclass of *note IPv4Address: 1e1,
     so it inherits all the attributes from that class.  In addition,
     the following attributes are available:

      -- 屬性: ip

          The address (*note IPv4Address: 1e1.) without network
          information.

               >>> interface = IPv4Interface('192.0.2.5/24')
               >>> interface.ip
               IPv4Address('192.0.2.5')

      -- 屬性: network

          The network (*note IPv4Network: 1e3.) this interface belongs
          to.

               >>> interface = IPv4Interface('192.0.2.5/24')
               >>> interface.network
               IPv4Network('192.0.2.0/24')

      -- 屬性: with_prefixlen

          A string representation of the interface with the mask in
          prefix notation.

               >>> interface = IPv4Interface('192.0.2.5/24')
               >>> interface.with_prefixlen
               '192.0.2.5/24'

      -- 屬性: with_netmask

          A string representation of the interface with the network as a
          net mask.

               >>> interface = IPv4Interface('192.0.2.5/24')
               >>> interface.with_netmask
               '192.0.2.5/255.255.255.0'

      -- 屬性: with_hostmask

          A string representation of the interface with the network as a
          host mask.

               >>> interface = IPv4Interface('192.0.2.5/24')
               >>> interface.with_hostmask
               '192.0.2.5/0.0.0.255'

 -- 類別: ipaddress.IPv6Interface (address)

     Construct an IPv6 interface.  The meaning of 'address' is as in the
     constructor of *note IPv6Network: 1e4, except that arbitrary host
     addresses are always accepted.

     *note IPv6Interface: 1714. is a subclass of *note IPv6Address: 1e2,
     so it inherits all the attributes from that class.  In addition,
     the following attributes are available:

      -- 屬性: ip

      -- 屬性: network

      -- 屬性: with_prefixlen

      -- 屬性: with_netmask

      -- 屬性: with_hostmask

          Refer to the corresponding attribute documentation in *note
          IPv4Interface: 1713.

* Menu:

* Operators: Operators<4>.


File: python.info,  Node: Operators<4>,  Up: Interface objects

5.21.23.16 Operators
....................

Interface objects support some operators.  Unless stated otherwise,
operators can only be applied between compatible objects (i.e.  IPv4
with IPv4, IPv6 with IPv6).

* Menu:

* Logical operators: Logical operators<2>.


File: python.info,  Node: Logical operators<2>,  Up: Operators<4>

5.21.23.17 Logical operators
............................

Interface objects can be compared with the usual set of logical
operators.

For equality comparison (‘==’ and ‘!=’), both the IP address and network
must be the same for the objects to be equal.  An interface will not
compare equal to any address or network object.

For ordering (‘<’, ‘>’, etc) the rules are different.  Interface and
address objects with the same IP version can be compared, and the
address objects will always sort before the interface objects.  Two
interface objects are first compared by their networks and, if those are
the same, then by their IP addresses.


File: python.info,  Node: Other Module Level Functions,  Next: Custom Exceptions,  Prev: Interface objects,  Up: ipaddress --- IPv4/IPv6 操作函式庫

5.21.23.18 Other Module Level Functions
.......................................

The module also provides the following module level functions:

 -- 函式: ipaddress.v4_int_to_packed (address)

     Represent an address as 4 packed bytes in network (big-endian)
     order.  'address' is an integer representation of an IPv4 IP
     address.  A *note ValueError: 1e7. is raised if the integer is
     negative or too large to be an IPv4 IP address.

          >>> ipaddress.ip_address(3221225985)
          IPv4Address('192.0.2.1')
          >>> ipaddress.v4_int_to_packed(3221225985)
          b'\xc0\x00\x02\x01'

 -- 函式: ipaddress.v6_int_to_packed (address)

     Represent an address as 16 packed bytes in network (big-endian)
     order.  'address' is an integer representation of an IPv6 IP
     address.  A *note ValueError: 1e7. is raised if the integer is
     negative or too large to be an IPv6 IP address.

 -- 函式: ipaddress.summarize_address_range (first, last)

     Return an iterator of the summarized network range given the first
     and last IP addresses.  'first' is the first *note IPv4Address:
     1e1. or *note IPv6Address: 1e2. in the range and 'last' is the last
     *note IPv4Address: 1e1. or *note IPv6Address: 1e2. in the range.  A
     *note TypeError: 4dd. is raised if 'first' or 'last' are not IP
     addresses or are not of the same version.  A *note ValueError: 1e7.
     is raised if 'last' is not greater than 'first' or if 'first'
     address version is not 4 or 6.

          >>> [ipaddr for ipaddr in ipaddress.summarize_address_range(
          ...    ipaddress.IPv4Address('192.0.2.0'),
          ...    ipaddress.IPv4Address('192.0.2.130'))]
          [IPv4Network('192.0.2.0/25'), IPv4Network('192.0.2.128/31'), IPv4Network('192.0.2.130/32')]

 -- 函式: ipaddress.collapse_addresses (addresses)

     Return an iterator of the collapsed *note IPv4Network: 1e3. or
     *note IPv6Network: 1e4. objects.  'addresses' is an *note iterable:
     11bf. of *note IPv4Network: 1e3. or *note IPv6Network: 1e4.
     objects.  A *note TypeError: 4dd. is raised if 'addresses' contains
     mixed version objects.

          >>> [ipaddr for ipaddr in
          ... ipaddress.collapse_addresses([ipaddress.IPv4Network('192.0.2.0/25'),
          ... ipaddress.IPv4Network('192.0.2.128/25')])]
          [IPv4Network('192.0.2.0/24')]

 -- 函式: ipaddress.get_mixed_type_key (obj)

     Return a key suitable for sorting between networks and addresses.
     Address and Network objects are not sortable by default; they're
     fundamentally different, so the expression:

          IPv4Address('192.0.2.0') <= IPv4Network('192.0.2.0/24')

     doesn't make sense.  There are some times however, where you may
     wish to have *note ipaddress: 74. sort these anyway.  If you need
     to do this, you can use this function as the 'key' argument to
     *note sorted(): b75.

     'obj' is either a network or address object.


File: python.info,  Node: Custom Exceptions,  Prev: Other Module Level Functions,  Up: ipaddress --- IPv4/IPv6 操作函式庫

5.21.23.19 Custom Exceptions
............................

To support more specific error reporting from class constructors, the
module defines the following exceptions:

 -- 例外: ipaddress.AddressValueError (ValueError)

     Any value error related to the address.

 -- 例外: ipaddress.NetmaskValueError (ValueError)

     Any value error related to the net mask.


File: python.info,  Node: 多媒體服務,  Next: 國際化,  Prev: 網路協定 Internet protocols 及支援,  Up: Python 標準函式庫 Standard Library

5.22 多媒體服務
===============

此章節所描述的模組 (module) 實作了多種在多媒體服務中相當有用的演算法和介
面，並可在安裝時決定是否要使用它們。以下為綜述：

* Menu:

* wave: wave --- 讀寫 WAV 檔案. 讀寫 WAV 檔案
* colorsys: colorsys --- 顏色系統間的轉換. 顏色系統間的轉換


File: python.info,  Node: wave --- 讀寫 WAV 檔案,  Next: colorsys --- 顏色系統間的轉換,  Up: 多媒體服務

5.22.1 ‘wave’ -- 讀寫 WAV 檔案
------------------------------

'原始碼：'Lib/wave.py(1)

__________________________________________________________________

*note wave: fb. 模組為波形音訊檔案格式「WAVE」（或稱「WAV」）提供了便捷
的介面。僅支援未壓縮的 PCM 編碼波形檔。

在 3.12 版的變更: 增加了標頭 ‘WAVE_FORMAT_EXTENSIBLE’ 的支援，要求的擴展
格式為 ‘KSDATAFORMAT_SUBTYPE_PCM’。

*note wave: fb. 模組定義了以下的函式和例外:

 -- 函式: wave.open (file, mode=None)

     如果 'file' 是一個字串，會打開對應名稱的檔案，否則會以類檔案物件處
     理。'mode' 可以是：

     ‘'rb'’

          唯讀模式。

     ‘'wb'’

          唯寫模式。

     請注意，不支援同時讀寫 WAV 檔案。

     'mode' 設定為 ‘'rb'’ 時，會回傳一個 *note Wave_read: 297. 物件，
     'mode' 設定為 ‘'wb'’ 時，則回傳一個 *note Wave_write: 298. 物件。如
     果省略 'mode'，並且將類檔案 (file-like) 物件作為 'file' 參數傳遞，
     則 ‘file.mode’ 會是 'mode' 的預設值。

     如果你傳遞一個類檔案物件，當呼叫其 ‘close()’ 方法時，wave 物件不會
     自動關閉該物件；關閉檔案物件的責任會在呼叫者上。

     *note open(): 8ef. 函式可以在 *note with: 577. 陳述式中使用。當
     ‘with’ 區塊完成時，會呼叫 *note Wave_read.close(): 3ad6. 或是 *note
     Wave_write.close(): 3ad7. 方法。

     在 3.4 版的變更: 增加對不可搜尋 (unseekable) 檔案的支援。

 -- 例外: wave.Error

     當不符合 WAV 格式或無法操作時會引發錯誤。

* Menu:

* Wave_read 物件::
* Wave_write 物件::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/wave.py


File: python.info,  Node: Wave_read 物件,  Next: Wave_write 物件,  Up: wave --- 讀寫 WAV 檔案

5.22.1.1 Wave_read 物件
.......................

 -- 類別: wave.Wave_read

     讀取一個 WAV 檔案。

     由 *note open(): 8ef. 回傳的 Wave_read 物件具有以下方法：

      -- 方法: close ()

          關閉 *note wave: fb. 開啟的串流並使該實例無法使用。當物件回收
          時自動呼叫。

      -- 方法: getnchannels ()

          回傳音訊聲道的數量（單聲道為 ‘1’，立體聲為 ‘2’）。

      -- 方法: getsampwidth ()

          回傳以位元組表示的取樣寬度 (sample width)。

      -- 方法: getframerate ()

          回傳取樣率。

      -- 方法: getnframes ()

          回傳音訊幀數。

      -- 方法: getcomptype ()

          回傳壓縮類型（僅支援 ‘'NONE'’ 類型）。

      -- 方法: getcompname ()

          *note getcomptype(): 3adf. 的人類可讀的版本。通常使用 ‘'not
          compressed'’ 代替 ‘'NONE'’。

      -- 方法: getparams ()

          回傳一個 *note namedtuple(): 1ae. ‘(nchannels, sampwidth,
          framerate, nframes, comptype, compname)’，等同於 ‘get*()’ 方法
          的輸出。

      -- 方法: readframes (n)

          讀取並回傳以 *note bytes: 1a5. 物件表示的最多 'n' 個音訊幀。

      -- 方法: rewind ()

          重置檔案指標至音訊流的開頭。

     The following two methods are defined for compatibility with the
     old ‘aifc’ module, and don't do anything interesting.

      -- 方法: getmarkers ()

          回傳 ‘None’。

          Deprecated since version 3.13, will be removed in version
          3.15: The method only existed for compatibility with the
          ‘aifc’ module which has been removed in Python 3.13.

      -- 方法: getmark (id)

          引發錯誤。

          Deprecated since version 3.13, will be removed in version
          3.15: The method only existed for compatibility with the
          ‘aifc’ module which has been removed in Python 3.13.

     以下兩個方法所定義的「位置」，在它們之間是相容的，但其他情況下則取
     決於具體實作方式。

      -- 方法: setpos (pos)

          將檔案指標設定為指定的位置。

      -- 方法: tell ()

          回傳目前的檔案指標位置。


File: python.info,  Node: Wave_write 物件,  Prev: Wave_read 物件,  Up: wave --- 讀寫 WAV 檔案

5.22.1.2 Wave_write 物件
........................

 -- 類別: wave.Wave_write

     寫入一個 WAV 檔案。

     Wave_write 物件，由 *note open(): 8ef. 回傳。

     對於可搜尋 (seekable) 的輸出串流，‘wave’ 標頭將自動更新，以反映實際
     寫入的幀數。對於不可搜尋的串流，當寫入第一個幀資料時，'nframes' 的
     值必須是準確的。要取得準確的 'nframes' 值，可以通過呼叫 *note
     setnframes(): 3ae9. 或 *note setparams(): 3aea. 方法，並在呼叫
     *note close(): 3ad7. 之前設定將寫入的幀數量，然後使用 *note
     writeframesraw(): f8d. 方法寫入幀資料；或者通過呼叫 *note
     writeframes(): f8e. 方法一次性寫入所有的幀資料。在後一種情況下，
     *note writeframes(): f8e. 方法將計算資料中的幀數量，並在寫入幀資料
     之前相應地設定 'nframes' 的值。

     在 3.4 版的變更: 增加對不可搜尋 (unseekable) 檔案的支援。

     Wave_write 物件具有以下方法：

      -- 方法: close ()

          確保 'nframes' 正確，如果該檔案是由 *note wave: fb. 開啟的，則
          關閉該檔案。此方法在物件回收時被呼叫。如果輸出串流不可搜尋且
          'nframes' 不符合實際寫入的幀數，則會引發例外。

      -- 方法: setnchannels (n)

          設定音訊的通道數量。

      -- 方法: setsampwidth (n)

          設定取樣寬度為 'n' 個位元組。

      -- 方法: setframerate (n)

          設定取樣頻率為 'n'。

          在 3.2 版的變更: 此方法的非整數輸入會被將四捨五入到最接近的整
          數。

      -- 方法: setnframes (n)

          設定幀數為 'n'。如果實際寫入的幀數不同，則稍後將進行更改（如果
          輸出串流不可搜尋，則此嘗試將引發錯誤）。

      -- 方法: setcomptype (type, name)

          設定壓縮類型和描述。目前只支援壓縮類型為 ‘NONE’，表示無壓縮。

      -- 方法: setparams (tuple)

          這個 'tuple' 應該是 ‘(nchannels, sampwidth, framerate,
          nframes, comptype, compname)’，值需要是符合 ‘set*()’ 方法的參
          數。設定所有參數。

      -- 方法: tell ()

          回傳檔案中的指標位置，其指標位置含意與 *note Wave_read.tell():
          3ae7. 和 *note Wave_read.setpos(): 3ae6. 是一致的。

      -- 方法: writeframesraw (data)

          寫入音訊幀，不修正 'nframes'。

          在 3.4 版的變更: 現在可接受任何 *note bytes-like object: cd4.。

      -- 方法: writeframes (data)

          寫入音訊幀並確保 'nframes' 正確。如果輸出串流不可搜尋，並且在
          寫入 'data' 後已寫入的總幀數與先前設定的 'nframes' 值不符，則
          會引發錯誤。

          在 3.4 版的變更: 現在可接受任何 *note bytes-like object: cd4.。

          注意在呼叫 *note writeframes(): f8e. 或 *note
          writeframesraw(): f8d. 之後設置任何參數都是無效的，任何嘗試這
          樣做的操作都會引發 *note wave.Error: 3ad8.。


File: python.info,  Node: colorsys --- 顏色系統間的轉換,  Prev: wave --- 讀寫 WAV 檔案,  Up: 多媒體服務

5.22.2 ‘colorsys’ -- 顏色系統間的轉換
-------------------------------------

'原始碼：'Lib/colorsys.py(1)

__________________________________________________________________

*note colorsys: 18. 模組 (module) 定義了電腦顯示器所用的 RGB （紅綠藍）
色彩空間與三種其他色彩座標系統：YIQ、HLS (色相、亮度、飽和度) 和 HSV (色
相、 飽和度、 明度) 所表示的顏色值之間的雙向轉換。所有這些色彩空間的座標
都使用浮點數值 (floating-point) 來表示。在 YIQ 空間中，Y 座標值為 0 和 1
之間，而 I 和 Q 座標均可以為正數或負數。在所有其他空間中，座標值均為 0 和
1 之間。

也參考
......

有關色彩空間的更多資訊請見 ‘https://poynton.ca/ColorFAQ.html’ 和
‘https://www.cambridgeincolour.com/tutorials/color-spaces.htm’。

*note colorsys: 18. 模組定義了以下函式：

 -- 函式: colorsys.rgb_to_yiq (r, g, b)

     將顏色自 RGB 座標轉換至 YIQ 座標。

 -- 函式: colorsys.yiq_to_rgb (y, i, q)

     將顏色自 YIQ 座標轉換至 RGB 座標。

 -- 函式: colorsys.rgb_to_hls (r, g, b)

     將顏色自 RGB 座標轉換至 HLS 座標。

 -- 函式: colorsys.hls_to_rgb (h, l, s)

     將顏色自 HLS 座標轉換至 RGB 座標。

 -- 函式: colorsys.rgb_to_hsv (r, g, b)

     將顏色自 RGB 座標轉換至 HSV 座標。

 -- 函式: colorsys.hsv_to_rgb (h, s, v)

     將顏色自 HSV 座標轉換至 RGB 座標。

範例：

     >>> import colorsys
     >>> colorsys.rgb_to_hsv(0.2, 0.4, 0.4)
     (0.5, 0.5, 0.4)
     >>> colorsys.hsv_to_rgb(0.5, 0.5, 0.4)
     (0.2, 0.4, 0.4)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/colorsys.py


File: python.info,  Node: 國際化,  Next: 程式框架,  Prev: 多媒體服務,  Up: Python 標準函式庫 Standard Library

5.23 國際化
===========

The modules described in this chapter help you write software that is
independent of language and locale by providing mechanisms for selecting
a language to be used in program messages or by tailoring output to
match local conventions.

本章節所描述的模組列表為：

* Menu:

* gettext: gettext --- 多語言國際化服務. 多語言國際化服務
* locale: locale --- 國際化服務. 國際化服務


File: python.info,  Node: gettext --- 多語言國際化服務,  Next: locale --- 國際化服務,  Up: 國際化

5.23.1 ‘gettext’ -- 多語言國際化服務
------------------------------------

'原始碼：'Lib/gettext.py(1)

__________________________________________________________________

The *note gettext: 59. module provides internationalization (I18N) and
localization (L10N) services for your Python modules and applications.
It supports both the GNU ‘gettext’ message catalog API and a higher
level, class-based API that may be more appropriate for Python files.
The interface described below allows you to write your module and
application messages in one natural language, and provide a catalog of
translated messages for running under different natural languages.

Some hints on localizing your Python modules and applications are also
given.

* Menu:

* GNU gettext API::
* Class-based API::
* Internationalizing your programs and modules::
* 致謝: 致謝<9>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/gettext.py


File: python.info,  Node: GNU gettext API,  Next: Class-based API,  Up: gettext --- 多語言國際化服務

5.23.1.1 GNU ‘gettext’ API
..........................

The *note gettext: 59. module defines the following API, which is very
similar to the GNU ‘gettext’ API. If you use this API you will affect
the translation of your entire application globally.  Often this is what
you want if your application is monolingual, with the choice of language
dependent on the locale of your user.  If you are localizing a Python
module, or if your application needs to switch languages on the fly, you
probably want to use the class-based API instead.

 -- 函式: gettext.bindtextdomain (domain, localedir=None)

     Bind the 'domain' to the locale directory 'localedir'.  More
     concretely, *note gettext: 59. will look for binary ‘.mo’ files for
     the given domain using the path (on Unix):
     ‘`localedir'/`language'/LC_MESSAGES/`domain'.mo’, where 'language'
     is searched for in the environment variables ‘LANGUAGE’, ‘LC_ALL’,
     ‘LC_MESSAGES’, and ‘LANG’ respectively.

     If 'localedir' is omitted or ‘None’, then the current binding for
     'domain' is returned.  (1)

 -- 函式: gettext.textdomain (domain=None)

     Change or query the current global domain.  If 'domain' is ‘None’,
     then the current global domain is returned, otherwise the global
     domain is set to 'domain', which is returned.

 -- 函式: gettext.gettext (message)

     Return the localized translation of 'message', based on the current
     global domain, language, and locale directory.  This function is
     usually aliased as ‘_()’ in the local namespace (see examples
     below).

 -- 函式: gettext.dgettext (domain, message)

     Like *note gettext(): 13d4, but look the message up in the
     specified 'domain'.

 -- 函式: gettext.ngettext (singular, plural, n)

     Like *note gettext(): 13d4, but consider plural forms.  If a
     translation is found, apply the plural formula to 'n', and return
     the resulting message (some languages have more than two plural
     forms).  If no translation is found, return 'singular' if 'n' is 1;
     return 'plural' otherwise.

     The Plural formula is taken from the catalog header.  It is a C or
     Python expression that has a free variable 'n'; the expression
     evaluates to the index of the plural in the catalog.  See the GNU
     gettext documentation(2) for the precise syntax to be used in ‘.po’
     files and the formulas for a variety of languages.

 -- 函式: gettext.dngettext (domain, singular, plural, n)

     Like *note ngettext(): 3b01, but look the message up in the
     specified 'domain'.

 -- 函式: gettext.pgettext (context, message)

 -- 函式: gettext.dpgettext (domain, context, message)

 -- 函式: gettext.npgettext (context, singular, plural, n)

 -- 函式: gettext.dnpgettext (domain, context, singular, plural, n)

     Similar to the corresponding functions without the ‘p’ in the
     prefix (that is, *note gettext(): 59, *note dgettext(): 3b00, *note
     ngettext(): 3b01, *note dngettext(): 3b02.), but the translation is
     restricted to the given message 'context'.

     在 3.8 版被加入.

Note that GNU ‘gettext’ also defines a ‘dcgettext()’ method, but this
was deemed not useful and so it is currently unimplemented.

Here's an example of typical usage for this API:

     import gettext
     gettext.bindtextdomain('myapplication', '/path/to/my/language/directory')
     gettext.textdomain('myapplication')
     _ = gettext.gettext
     # ...
     print(_('This is a translatable string.'))

   ---------- Footnotes ----------

   (1) The default locale directory is system dependent; for example, on
Red Hat Linux it is ‘/usr/share/locale’, but on Solaris it is
‘/usr/lib/locale’.  The ‘gettext’ module does not try to support these
system dependent defaults; instead its default is
‘`sys.base_prefix'/share/locale’ (see *note sys.base_prefix: 3afe.).
For this reason, it is always best to call *note bindtextdomain(): 3afd.
with an explicit absolute path at the start of your application.

   (2) https://www.gnu.org/software/gettext/manual/gettext.html


File: python.info,  Node: Class-based API,  Next: Internationalizing your programs and modules,  Prev: GNU gettext API,  Up: gettext --- 多語言國際化服務

5.23.1.2 Class-based API
........................

The class-based API of the *note gettext: 59. module gives you more
flexibility and greater convenience than the GNU ‘gettext’ API. It is
the recommended way of localizing your Python applications and modules.
‘gettext’ defines a *note GNUTranslations: 3b07. class which implements
the parsing of GNU ‘.mo’ format files, and has methods for returning
strings.  Instances of this class can also install themselves in the
built-in namespace as the function ‘_()’.

 -- 函式: gettext.find (domain, localedir=None, languages=None,
          all=False)

     This function implements the standard ‘.mo’ file search algorithm.
     It takes a 'domain', identical to what *note textdomain(): 3aff.
     takes.  Optional 'localedir' is as in *note bindtextdomain(): 3afd.
     Optional 'languages' is a list of strings, where each string is a
     language code.

     If 'localedir' is not given, then the default system locale
     directory is used.  (1)  If 'languages' is not given, then the
     following environment variables are searched: ‘LANGUAGE’, ‘LC_ALL’,
     ‘LC_MESSAGES’, and ‘LANG’.  The first one returning a non-empty
     value is used for the 'languages' variable.  The environment
     variables should contain a colon separated list of languages, which
     will be split on the colon to produce the expected list of language
     code strings.

     *note find(): 3b08. then expands and normalizes the languages, and
     then iterates through them, searching for an existing file built of
     these components:

     ‘`localedir'/`language'/LC_MESSAGES/`domain'.mo’

     The first such file name that exists is returned by *note find():
     3b08.  If no such file is found, then ‘None’ is returned.  If 'all'
     is given, it returns a list of all file names, in the order in
     which they appear in the languages list or the environment
     variables.

 -- 函式: gettext.translation (domain, localedir=None, languages=None,
          class_=None, fallback=False)

     Return a ‘*Translations’ instance based on the 'domain',
     'localedir', and 'languages', which are first passed to *note
     find(): 3b08. to get a list of the associated ‘.mo’ file paths.
     Instances with identical ‘.mo’ file names are cached.  The actual
     class instantiated is 'class_' if provided, otherwise *note
     GNUTranslations: 3b07.  The class's constructor must take a single
     *note file object: 115b. argument.

     If multiple files are found, later files are used as fallbacks for
     earlier ones.  To allow setting the fallback, *note copy.copy():
     4d8. is used to clone each translation object from the cache; the
     actual instance data is still shared with the cache.

     If no ‘.mo’ file is found, this function raises *note OSError: 350.
     if 'fallback' is false (which is the default), and returns a *note
     NullTranslations: 3b09. instance if 'fallback' is true.

     在 3.3 版的變更: *note IOError: ff5. used to be raised, it is now
     an alias of *note OSError: 350.

     在 3.11 版的變更: 'codeset' 參數被移除。

 -- 函式: gettext.install (domain, localedir=None, *, names=None)

     This installs the function ‘_()’ in Python's builtins namespace,
     based on 'domain' and 'localedir' which are passed to the function
     *note translation(): a1c.

     For the 'names' parameter, please see the description of the
     translation object's *note install(): 3b0a. method.

     As seen below, you usually mark the strings in your application
     that are candidates for translation, by wrapping them in a call to
     the ‘_()’ function, like this:

          print(_('This string will be translated.'))

     For convenience, you want the ‘_()’ function to be installed in
     Python's builtins namespace, so it is easily accessible in all
     modules of your application.

     在 3.11 版的變更: 'names' is now a keyword-only parameter.

* Menu:

* The NullTranslations class::
* The GNUTranslations class::
* Solaris message catalog support::
* The Catalog constructor::

   ---------- Footnotes ----------

   (1) 請見上方 *note bindtextdomain(): 3afd. 之註解。


File: python.info,  Node: The NullTranslations class,  Next: The GNUTranslations class,  Up: Class-based API

5.23.1.3 The ‘NullTranslations’ class
.....................................

Translation classes are what actually implement the translation of
original source file message strings to translated message strings.  The
base class used by all translation classes is *note NullTranslations:
3b09.; this provides the basic interface you can use to write your own
specialized translation classes.  Here are the methods of
‘NullTranslations’:

 -- 類別: gettext.NullTranslations (fp=None)

     Takes an optional *note file object: 115b. 'fp', which is ignored
     by the base class.  Initializes "protected" instance variables
     '_info' and '_charset' which are set by derived classes, as well as
     '_fallback', which is set through *note add_fallback(): 3b0c.  It
     then calls ‘self._parse(fp)’ if 'fp' is not ‘None’.

      -- 方法: _parse (fp)

          No-op in the base class, this method takes file object 'fp',
          and reads the data from the file, initializing its message
          catalog.  If you have an unsupported message catalog file
          format, you should override this method to parse your format.

      -- 方法: add_fallback (fallback)

          Add 'fallback' as the fallback object for the current
          translation object.  A translation object should consult the
          fallback if it cannot provide a translation for a given
          message.

      -- 方法: gettext (message)

          If a fallback has been set, forward ‘gettext()’ to the
          fallback.  Otherwise, return 'message'.  Overridden in derived
          classes.

      -- 方法: ngettext (singular, plural, n)

          If a fallback has been set, forward ‘ngettext()’ to the
          fallback.  Otherwise, return 'singular' if 'n' is 1; return
          'plural' otherwise.  Overridden in derived classes.

      -- 方法: pgettext (context, message)

          If a fallback has been set, forward *note pgettext(): 999. to
          the fallback.  Otherwise, return the translated message.
          Overridden in derived classes.

          在 3.8 版被加入.

      -- 方法: npgettext (context, singular, plural, n)

          If a fallback has been set, forward *note npgettext(): 3b04.
          to the fallback.  Otherwise, return the translated message.
          Overridden in derived classes.

          在 3.8 版被加入.

      -- 方法: info ()

          Return a dictionary containing the metadata found in the
          message catalog file.

      -- 方法: charset ()

          Return the encoding of the message catalog file.

      -- 方法: install (names=None)

          This method installs *note gettext(): 3b0e. into the built-in
          namespace, binding it to ‘_’.

          If the 'names' parameter is given, it must be a sequence
          containing the names of functions you want to install in the
          builtins namespace in addition to ‘_()’.  Supported names are
          ‘'gettext'’, ‘'ngettext'’, ‘'pgettext'’, and ‘'npgettext'’.

          Note that this is only one way, albeit the most convenient
          way, to make the ‘_()’ function available to your application.
          Because it affects the entire application globally, and
          specifically the built-in namespace, localized modules should
          never install ‘_()’.  Instead, they should use this code to
          make ‘_()’ available to their module:

               import gettext
               t = gettext.translation('mymodule', ...)
               _ = t.gettext

          This puts ‘_()’ only in the module's global namespace and so
          only affects calls within this module.

          在 3.8 版的變更: 新增 ‘'pgettext'’ 與 ‘'npgettext'’。


File: python.info,  Node: The GNUTranslations class,  Next: Solaris message catalog support,  Prev: The NullTranslations class,  Up: Class-based API

5.23.1.4 The ‘GNUTranslations’ class
....................................

The ‘gettext’ module provides one additional class derived from *note
NullTranslations: 3b09.: *note GNUTranslations: 3b07.  This class
overrides ‘_parse()’ to enable reading GNU ‘gettext’ format ‘.mo’ files
in both big-endian and little-endian format.

*note GNUTranslations: 3b07. parses optional metadata out of the
translation catalog.  It is convention with GNU ‘gettext’ to include
metadata as the translation for the empty string.  This metadata is in
RFC 822(1)-style ‘key: value’ pairs, and should contain the
‘Project-Id-Version’ key.  If the key ‘Content-Type’ is found, then the
‘charset’ property is used to initialize the "protected" ‘_charset’
instance variable, defaulting to ‘None’ if not found.  If the charset
encoding is specified, then all message ids and message strings read
from the catalog are converted to Unicode using this encoding, else
ASCII is assumed.

Since message ids are read as Unicode strings too, all ‘*gettext()’
methods will assume message ids as Unicode strings, not byte strings.

The entire set of key/value pairs are placed into a dictionary and set
as the "protected" ‘_info’ instance variable.

If the ‘.mo’ file's magic number is invalid, the major version number is
unexpected, or if other problems occur while reading the file,
instantiating a *note GNUTranslations: 3b07. class can raise *note
OSError: 350.

 -- 類別: gettext.GNUTranslations

     The following methods are overridden from the base class
     implementation:

      -- 方法: gettext (message)

          Look up the 'message' id in the catalog and return the
          corresponding message string, as a Unicode string.  If there
          is no entry in the catalog for the 'message' id, and a
          fallback has been set, the look up is forwarded to the
          fallback's *note gettext(): 3b0e. method.  Otherwise, the
          'message' id is returned.

      -- 方法: ngettext (singular, plural, n)

          Do a plural-forms lookup of a message id.  'singular' is used
          as the message id for purposes of lookup in the catalog, while
          'n' is used to determine which plural form to use.  The
          returned message string is a Unicode string.

          If the message id is not found in the catalog, and a fallback
          is specified, the request is forwarded to the fallback's *note
          ngettext(): 3b0f. method.  Otherwise, when 'n' is 1 'singular'
          is returned, and 'plural' is returned in all other cases.

          以下是個範例：

               n = len(os.listdir('.'))
               cat = GNUTranslations(somefile)
               message = cat.ngettext(
                   'There is %(num)d file in this directory',
                   'There are %(num)d files in this directory',
                   n) % {'num': n}

      -- 方法: pgettext (context, message)

          Look up the 'context' and 'message' id in the catalog and
          return the corresponding message string, as a Unicode string.
          If there is no entry in the catalog for the 'message' id and
          'context', and a fallback has been set, the look up is
          forwarded to the fallback's *note pgettext(): 999. method.
          Otherwise, the 'message' id is returned.

          在 3.8 版被加入.

      -- 方法: npgettext (context, singular, plural, n)

          Do a plural-forms lookup of a message id.  'singular' is used
          as the message id for purposes of lookup in the catalog, while
          'n' is used to determine which plural form to use.

          If the message id for 'context' is not found in the catalog,
          and a fallback is specified, the request is forwarded to the
          fallback's *note npgettext(): 3b04. method.  Otherwise, when
          'n' is 1 'singular' is returned, and 'plural' is returned in
          all other cases.

          在 3.8 版被加入.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc822.html


File: python.info,  Node: Solaris message catalog support,  Next: The Catalog constructor,  Prev: The GNUTranslations class,  Up: Class-based API

5.23.1.5 Solaris message catalog support
........................................

The Solaris operating system defines its own binary ‘.mo’ file format,
but since no documentation can be found on this format, it is not
supported at this time.


File: python.info,  Node: The Catalog constructor,  Prev: Solaris message catalog support,  Up: Class-based API

5.23.1.6 The Catalog constructor
................................

GNOME uses a version of the *note gettext: 59. module by James
Henstridge, but this version has a slightly different API. Its
documented usage was:

     import gettext
     cat = gettext.Catalog(domain, localedir)
     _ = cat.gettext
     print(_('hello world'))

For compatibility with this older module, the function ‘Catalog()’ is an
alias for the *note translation(): a1c. function described above.

One difference between this module and Henstridge's: his catalog objects
supported access through a mapping API, but this appears to be unused
and so is not currently supported.


File: python.info,  Node: Internationalizing your programs and modules,  Next: 致謝<9>,  Prev: Class-based API,  Up: gettext --- 多語言國際化服務

5.23.1.7 Internationalizing your programs and modules
.....................................................

Internationalization (I18N) refers to the operation by which a program
is made aware of multiple languages.  Localization (L10N) refers to the
adaptation of your program, once internationalized, to the local
language and cultural habits.  In order to provide multilingual messages
for your Python programs, you need to take the following steps:

  1. prepare your program or module by specially marking translatable
     strings

  2. run a suite of tools over your marked files to generate raw
     messages catalogs

  3. create language-specific translations of the message catalogs

  4. use the *note gettext: 59. module so that message strings are
     properly translated

In order to prepare your code for I18N, you need to look at all the
strings in your files.  Any string that needs to be translated should be
marked by wrapping it in ‘_('...')’ -- that is, a call to the function
*note _: 59.  For example:

     filename = 'mylog.txt'
     message = _('writing a log message')
     with open(filename, 'w') as fp:
         fp.write(message)

In this example, the string ‘'writing a log message'’ is marked as a
candidate for translation, while the strings ‘'mylog.txt'’ and ‘'w'’ are
not.

There are a few tools to extract the strings meant for translation.  The
original GNU ‘gettext’ only supported C or C++ source code but its
extended version ‘xgettext’ scans code written in a number of languages,
including Python, to find strings marked as translatable.  Babel(1) is a
Python internationalization library that includes a ‘pybabel’ script to
extract and compile message catalogs.  François Pinard's program called
‘xpot’ does a similar job and is available as part of his po-utils
package(2).

(Python also includes pure-Python versions of these programs, called
‘pygettext.py’ and ‘msgfmt.py’; some Python distributions will install
them for you.  ‘pygettext.py’ is similar to ‘xgettext’, but only
understands Python source code and cannot handle other programming
languages such as C or C++.  ‘pygettext.py’ supports a command-line
interface similar to ‘xgettext’; for details on its use, run
‘pygettext.py --help’.  ‘msgfmt.py’ is binary compatible with GNU
‘msgfmt’.  With these two programs, you may not need the GNU ‘gettext’
package to internationalize your Python applications.)

‘xgettext’, ‘pygettext’, and similar tools generate ‘.po’ files that are
message catalogs.  They are structured human-readable files that contain
every marked string in the source code, along with a placeholder for the
translated versions of these strings.

Copies of these ‘.po’ files are then handed over to the individual human
translators who write translations for every supported natural language.
They send back the completed language-specific versions as a
‘<language-name>.po’ file that's compiled into a machine-readable ‘.mo’
binary catalog file using the ‘msgfmt’ program.  The ‘.mo’ files are
used by the *note gettext: 59. module for the actual translation
processing at run-time.

How you use the *note gettext: 59. module in your code depends on
whether you are internationalizing a single module or your entire
application.  The next two sections will discuss each case.

* Menu:

* Localizing your module::
* Localizing your application::
* Changing languages on the fly::
* Deferred translations::

   ---------- Footnotes ----------

   (1) https://babel.pocoo.org/

   (2) https://github.com/pinard/po-utils


File: python.info,  Node: Localizing your module,  Next: Localizing your application,  Up: Internationalizing your programs and modules

5.23.1.8 Localizing your module
...............................

If you are localizing your module, you must take care not to make global
changes, e.g.  to the built-in namespace.  You should not use the GNU
‘gettext’ API but instead the class-based API.

Let's say your module is called "spam" and the module's various natural
language translation ‘.mo’ files reside in ‘/usr/share/locale’ in GNU
‘gettext’ format.  Here's what you would put at the top of your module:

     import gettext
     t = gettext.translation('spam', '/usr/share/locale')
     _ = t.gettext


File: python.info,  Node: Localizing your application,  Next: Changing languages on the fly,  Prev: Localizing your module,  Up: Internationalizing your programs and modules

5.23.1.9 Localizing your application
....................................

If you are localizing your application, you can install the ‘_()’
function globally into the built-in namespace, usually in the main
driver file of your application.  This will let all your
application-specific files just use ‘_('...')’ without having to
explicitly install it in each file.

In the simple case then, you need only add the following bit of code to
the main driver file of your application:

     import gettext
     gettext.install('myapplication')

If you need to set the locale directory, you can pass it into the *note
install(): a1d. function:

     import gettext
     gettext.install('myapplication', '/usr/share/locale')


File: python.info,  Node: Changing languages on the fly,  Next: Deferred translations,  Prev: Localizing your application,  Up: Internationalizing your programs and modules

5.23.1.10 Changing languages on the fly
.......................................

If your program needs to support many languages at the same time, you
may want to create multiple translation instances and then switch
between them explicitly, like so:

     import gettext

     lang1 = gettext.translation('myapplication', languages=['en'])
     lang2 = gettext.translation('myapplication', languages=['fr'])
     lang3 = gettext.translation('myapplication', languages=['de'])

     # start by using language1
     lang1.install()

     # ... time goes by, user selects language 2
     lang2.install()

     # ... more time goes by, user selects language 3
     lang3.install()


File: python.info,  Node: Deferred translations,  Prev: Changing languages on the fly,  Up: Internationalizing your programs and modules

5.23.1.11 Deferred translations
...............................

In most coding situations, strings are translated where they are coded.
Occasionally however, you need to mark strings for translation, but
defer actual translation until later.  A classic example is:

     animals = ['mollusk',
                'albatross',
                'rat',
                'penguin',
                'python', ]
     # ...
     for a in animals:
         print(a)

Here, you want to mark the strings in the ‘animals’ list as being
translatable, but you don't actually want to translate them until they
are printed.

Here is one way you can handle this situation:

     def _(message): return message

     animals = [_('mollusk'),
                _('albatross'),
                _('rat'),
                _('penguin'),
                _('python'), ]

     del _

     # ...
     for a in animals:
         print(_(a))

This works because the dummy definition of ‘_()’ simply returns the
string unchanged.  And this dummy definition will temporarily override
any definition of ‘_()’ in the built-in namespace (until the *note del:
16a9. command).  Take care, though if you have a previous definition of
‘_()’ in the local namespace.

Note that the second use of ‘_()’ will not identify "a" as being
translatable to the ‘gettext’ program, because the parameter is not a
string literal.

Another way to handle this is with the following example:

     def N_(message): return message

     animals = [N_('mollusk'),
                N_('albatross'),
                N_('rat'),
                N_('penguin'),
                N_('python'), ]

     # ...
     for a in animals:
         print(_(a))

In this case, you are marking translatable strings with the function
‘N_()’, which won't conflict with any definition of ‘_()’.  However, you
will need to teach your message extraction program to look for
translatable strings marked with ‘N_()’.  ‘xgettext’, ‘pygettext’,
‘pybabel extract’, and ‘xpot’ all support this through the use of the
‘-k’ command-line switch.  The choice of ‘N_()’ here is totally
arbitrary; it could have just as easily been
‘MarkThisStringForTranslation()’.


File: python.info,  Node: 致謝<9>,  Prev: Internationalizing your programs and modules,  Up: gettext --- 多語言國際化服務

5.23.1.12 致謝
..............

The following people contributed code, feedback, design suggestions,
previous implementations, and valuable experience to the creation of
this module:

   * Peter Funk

   * James Henstridge

   * Juan David Ibáñez Palomar

   * Marc-André Lemburg

   * Martin von Löwis

   * François Pinard

   * Barry Warsaw

   * Gustavo Niemeyer

註解
....


File: python.info,  Node: locale --- 國際化服務,  Prev: gettext --- 多語言國際化服務,  Up: 國際化

5.23.2 ‘locale’ -- 國際化服務
-----------------------------

'原始碼：'Lib/locale.py(1)

__________________________________________________________________

The *note locale: 7a. module opens access to the POSIX locale database
and functionality.  The POSIX locale mechanism allows programmers to
deal with certain cultural issues in an application, without requiring
the programmer to know all the specifics of each country where the
software is executed.

The *note locale: 7a. module is implemented on top of the ‘_locale’
module, which in turn uses an ANSI C locale implementation if available.

The *note locale: 7a. module defines the following exception and
functions:

 -- 例外: locale.Error

     Exception raised when the locale passed to *note setlocale(): 2bb.
     is not recognized.

 -- 函式: locale.setlocale (category, locale=None)

     If 'locale' is given and not ‘None’, *note setlocale(): 2bb.
     modifies the locale setting for the 'category'.  The available
     categories are listed in the data description below.  'locale' may
     be a string, or an iterable of two strings (language code and
     encoding).  If it's an iterable, it's converted to a locale name
     using the locale aliasing engine.  An empty string specifies the
     user's default settings.  If the modification of the locale fails,
     the exception *note Error: 3b24. is raised.  If successful, the new
     locale setting is returned.

     If 'locale' is omitted or ‘None’, the current setting for
     'category' is returned.

     *note setlocale(): 2bb. is not thread-safe on most systems.
     Applications typically start with a call of

          import locale
          locale.setlocale(locale.LC_ALL, '')

     This sets the locale for all categories to the user's default
     setting (typically specified in the ‘LANG’ environment variable).
     If the locale is not changed thereafter, using multithreading
     should not cause problems.

 -- 函式: locale.localeconv ()

     Returns the database of the local conventions as a dictionary.
     This dictionary has the following strings as keys:

     分類                       Key                                       含義
                                                                          
     ----------------------------------------------------------------------------------------------------------
                                                                          
     *note LC_NUMERIC: 3b25.    ‘'decimal_point'’                         Decimal point character.
                                                                          
                                                                          
                                ‘'grouping'’                              Sequence of numbers specifying
                                                                          which relative positions the
                                                                          ‘'thousands_sep'’ is expected.  If
                                                                          the sequence is terminated with
                                                                          *note CHAR_MAX: 3b26, no further
                                                                          grouping is performed.  If the
                                                                          sequence terminates with a ‘0’,
                                                                          the last group size is repeatedly
                                                                          used.
                                                                          
                                                                          
                                ‘'thousands_sep'’                         Character used between groups.
                                                                          
                                                                          
     *note LC_MONETARY: 3b27.   ‘'int_curr_symbol'’                       International currency symbol.
                                                                          
                                                                          
                                ‘'currency_symbol'’                       Local currency symbol.
                                                                          
                                                                          
                                ‘'p_cs_precedes/n_cs_precedes'’           Whether the currency symbol
                                                                          precedes the value (for positive
                                                                          resp.  negative values).
                                                                          
                                                                          
                                ‘'p_sep_by_space/n_sep_by_space'’         Whether the currency symbol is
                                                                          separated from the value by a
                                                                          space (for positive resp.
                                                                          negative values).
                                                                          
                                                                          
                                ‘'mon_decimal_point'’                     Decimal point used for monetary
                                                                          values.
                                                                          
                                                                          
                                ‘'frac_digits'’                           Number of fractional digits used
                                                                          in local formatting of monetary
                                                                          values.
                                                                          
                                                                          
                                ‘'int_frac_digits'’                       Number of fractional digits used
                                                                          in international formatting of
                                                                          monetary values.
                                                                          
                                                                          
                                ‘'mon_thousands_sep'’                     Group separator used for monetary
                                                                          values.
                                                                          
                                                                          
                                ‘'mon_grouping'’                          Equivalent to ‘'grouping'’, used
                                                                          for monetary values.
                                                                          
                                                                          
                                ‘'positive_sign'’                         Symbol used to annotate a positive
                                                                          monetary value.
                                                                          
                                                                          
                                ‘'negative_sign'’                         Symbol used to annotate a negative
                                                                          monetary value.
                                                                          
                                                                          
                                ‘'p_sign_posn/n_sign_posn'’               The position of the sign (for
                                                                          positive resp.  negative values),
                                                                          see below.
                                                                          

     All numeric values can be set to *note CHAR_MAX: 3b26. to indicate
     that there is no value specified in this locale.

     The possible values for ‘'p_sign_posn'’ and ‘'n_sign_posn'’ are
     given below.

     Value              Explanation
                        
     -----------------------------------------------------------------
                        
     ‘0’                Currency and value are surrounded by
                        parentheses.
                        
                        
     ‘1’                The sign should precede the value and
                        currency symbol.
                        
                        
     ‘2’                The sign should follow the value and
                        currency symbol.
                        
                        
     ‘3’                The sign should immediately precede the
                        value.
                        
                        
     ‘4’                The sign should immediately follow the
                        value.
                        
                        
     ‘CHAR_MAX’         Nothing is specified in this locale.
                        

     The function temporarily sets the ‘LC_CTYPE’ locale to the
     ‘LC_NUMERIC’ locale or the ‘LC_MONETARY’ locale if locales are
     different and numeric or monetary strings are non-ASCII. This
     temporary change affects other threads.

     在 3.7 版的變更: The function now temporarily sets the ‘LC_CTYPE’
     locale to the ‘LC_NUMERIC’ locale in some cases.

 -- 函式: locale.nl_langinfo (option)

     Return some locale-specific information as a string.  This function
     is not available on all systems, and the set of possible options
     might also vary across platforms.  The possible argument values are
     numbers, for which symbolic constants are available in the locale
     module.

     The *note nl_langinfo(): 3b28. function accepts one of the
     following keys.  Most descriptions are taken from the corresponding
     description in the GNU C library.

      -- 資料: locale.CODESET

          Get a string with the name of the character encoding used in
          the selected locale.

      -- 資料: locale.D_T_FMT

          Get a string that can be used as a format string for *note
          time.strftime(): 1181. to represent date and time in a
          locale-specific way.

      -- 資料: locale.D_FMT

          Get a string that can be used as a format string for *note
          time.strftime(): 1181. to represent a date in a
          locale-specific way.

      -- 資料: locale.T_FMT

          Get a string that can be used as a format string for *note
          time.strftime(): 1181. to represent a time in a
          locale-specific way.

      -- 資料: locale.T_FMT_AMPM

          Get a format string for *note time.strftime(): 1181. to
          represent time in the am/pm format.

      -- 資料: locale.DAY_1
      -- 資料: locale.DAY_2
      -- 資料: locale.DAY_3
      -- 資料: locale.DAY_4
      -- 資料: locale.DAY_5
      -- 資料: locale.DAY_6
      -- 資料: locale.DAY_7

          Get the name of the n-th day of the week.

               備註: This follows the US convention of *note DAY_1:
               3b2e. being Sunday, not the international convention (ISO
               8601) that Monday is the first day of the week.

      -- 資料: locale.ABDAY_1
      -- 資料: locale.ABDAY_2
      -- 資料: locale.ABDAY_3
      -- 資料: locale.ABDAY_4
      -- 資料: locale.ABDAY_5
      -- 資料: locale.ABDAY_6
      -- 資料: locale.ABDAY_7

          Get the abbreviated name of the n-th day of the week.

      -- 資料: locale.MON_1
      -- 資料: locale.MON_2
      -- 資料: locale.MON_3
      -- 資料: locale.MON_4
      -- 資料: locale.MON_5
      -- 資料: locale.MON_6
      -- 資料: locale.MON_7
      -- 資料: locale.MON_8
      -- 資料: locale.MON_9
      -- 資料: locale.MON_10
      -- 資料: locale.MON_11
      -- 資料: locale.MON_12

          Get the name of the n-th month.

      -- 資料: locale.ABMON_1
      -- 資料: locale.ABMON_2
      -- 資料: locale.ABMON_3
      -- 資料: locale.ABMON_4
      -- 資料: locale.ABMON_5
      -- 資料: locale.ABMON_6
      -- 資料: locale.ABMON_7
      -- 資料: locale.ABMON_8
      -- 資料: locale.ABMON_9
      -- 資料: locale.ABMON_10
      -- 資料: locale.ABMON_11
      -- 資料: locale.ABMON_12

          Get the abbreviated name of the n-th month.

      -- 資料: locale.RADIXCHAR

          Get the radix character (decimal dot, decimal comma, etc.).

      -- 資料: locale.THOUSEP

          Get the separator character for thousands (groups of three
          digits).

      -- 資料: locale.YESEXPR

          Get a regular expression that can be used with the regex
          function to recognize a positive response to a yes/no
          question.

      -- 資料: locale.NOEXPR

          Get a regular expression that can be used with the ‘regex(3)’
          function to recognize a negative response to a yes/no
          question.

               備註: The regular expressions for *note YESEXPR: 3b56.
               and *note NOEXPR: 3b57. use syntax suitable for the
               ‘regex’ function from the C library, which might differ
               from the syntax used in *note re: a7.

      -- 資料: locale.CRNCYSTR

          Get the currency symbol, preceded by "-" if the symbol should
          appear before the value, "+" if the symbol should appear after
          the value, or "."  if the symbol should replace the radix
          character.

      -- 資料: locale.ERA

          Get a string that represents the era used in the current
          locale.

          Most locales do not define this value.  An example of a locale
          which does define this value is the Japanese one.  In Japan,
          the traditional representation of dates includes the name of
          the era corresponding to the then-emperor's reign.

          Normally it should not be necessary to use this value
          directly.  Specifying the ‘E’ modifier in their format strings
          causes the *note time.strftime(): 1181. function to use this
          information.  The format of the returned string is not
          specified, and therefore you should not assume knowledge of it
          on different systems.

      -- 資料: locale.ERA_D_T_FMT

          Get a format string for *note time.strftime(): 1181. to
          represent date and time in a locale-specific era-based way.

      -- 資料: locale.ERA_D_FMT

          Get a format string for *note time.strftime(): 1181. to
          represent a date in a locale-specific era-based way.

      -- 資料: locale.ERA_T_FMT

          Get a format string for *note time.strftime(): 1181. to
          represent a time in a locale-specific era-based way.

      -- 資料: locale.ALT_DIGITS

          Get a representation of up to 100 values used to represent the
          values 0 to 99.

 -- 函式: locale.getdefaultlocale ([envvars])

     Tries to determine the default locale settings and returns them as
     a tuple of the form ‘(language code, encoding)’.

     According to POSIX, a program which has not called
     ‘setlocale(LC_ALL, '')’ runs using the portable ‘'C'’ locale.
     Calling ‘setlocale(LC_ALL, '')’ lets it use the default locale as
     defined by the ‘LANG’ variable.  Since we do not want to interfere
     with the current locale setting we thus emulate the behavior in the
     way described above.

     To maintain compatibility with other platforms, not only the ‘LANG’
     variable is tested, but a list of variables given as envvars
     parameter.  The first found to be defined will be used.  'envvars'
     defaults to the search path used in GNU gettext; it must always
     contain the variable name ‘'LANG'’.  The GNU gettext search path
     contains ‘'LC_ALL'’, ‘'LC_CTYPE'’, ‘'LANG'’ and ‘'LANGUAGE'’, in
     that order.

     Except for the code ‘'C'’, the language code corresponds to RFC
     1766(2).  'language code' and 'encoding' may be ‘None’ if their
     values cannot be determined.

     Deprecated since version 3.11, will be removed in version 3.15.

 -- 函式: locale.getlocale (category=LC_CTYPE)

     Returns the current setting for the given locale category as
     sequence containing 'language code', 'encoding'.  'category' may be
     one of the ‘LC_*’ values except *note LC_ALL: 3b5e.  It defaults to
     *note LC_CTYPE: 3b5f.

     Except for the code ‘'C'’, the language code corresponds to RFC
     1766(3).  'language code' and 'encoding' may be ‘None’ if their
     values cannot be determined.

 -- 函式: locale.getpreferredencoding (do_setlocale=True)

     Return the *note locale encoding: 227. used for text data,
     according to user preferences.  User preferences are expressed
     differently on different systems, and might not be available
     programmatically on some systems, so this function only returns a
     guess.

     On some systems, it is necessary to invoke *note setlocale(): 2bb.
     to obtain the user preferences, so this function is not
     thread-safe.  If invoking setlocale is not necessary or desired,
     'do_setlocale' should be set to ‘False’.

     On Android or if the *note Python UTF-8 Mode: 5fc. is enabled,
     always return ‘'utf-8'’, the *note locale encoding: 227. and the
     'do_setlocale' argument are ignored.

     The *note Python preinitialization: 3b60. configures the LC_CTYPE
     locale.  See also the *note filesystem encoding and error handler:
     4e0.

     在 3.7 版的變更: The function now always returns ‘"utf-8"’ on
     Android or if the *note Python UTF-8 Mode: 5fc. is enabled.

 -- 函式: locale.getencoding ()

     Get the current *note locale encoding: 227.:

        * On Android and VxWorks, return ‘"utf-8"’.

        * On Unix, return the encoding of the current *note LC_CTYPE:
          3b5f. locale.  Return ‘"utf-8"’ if ‘nl_langinfo(CODESET)’
          returns an empty string: for example, if the current LC_CTYPE
          locale is not supported.

        * On Windows, return the ANSI code page.

     The *note Python preinitialization: 3b60. configures the LC_CTYPE
     locale.  See also the *note filesystem encoding and error handler:
     4e0.

     This function is similar to *note getpreferredencoding(False): 4df.
     except this function ignores the *note Python UTF-8 Mode: 5fc.

     在 3.11 版被加入.

 -- 函式: locale.normalize (localename)

     Returns a normalized locale code for the given locale name.  The
     returned locale code is formatted for use with *note setlocale():
     2bb.  If normalization fails, the original name is returned
     unchanged.

     If the given encoding is not known, the function defaults to the
     default encoding for the locale code just like *note setlocale():
     2bb.

 -- 函式: locale.strcoll (string1, string2)

     Compares two strings according to the current *note LC_COLLATE:
     3b63. setting.  As any other compare function, returns a negative,
     or a positive value, or ‘0’, depending on whether 'string1'
     collates before or after 'string2' or is equal to it.

 -- 函式: locale.strxfrm (string)

     Transforms a string to one that can be used in locale-aware
     comparisons.  For example, ‘strxfrm(s1) < strxfrm(s2)’ is
     equivalent to ‘strcoll(s1, s2) < 0’.  This function can be used
     when the same string is compared repeatedly, e.g.  when collating a
     sequence of strings.

 -- 函式: locale.format_string (format, val, grouping=False,
          monetary=False)

     Formats a number 'val' according to the current *note LC_NUMERIC:
     3b25. setting.  The format follows the conventions of the ‘%’
     operator.  For floating-point values, the decimal point is modified
     if appropriate.  If 'grouping' is ‘True’, also takes the grouping
     into account.

     If 'monetary' is true, the conversion uses monetary thousands
     separator and grouping strings.

     Processes formatting specifiers as in ‘format % val’, but takes the
     current locale settings into account.

     在 3.7 版的變更: The 'monetary' keyword parameter was added.

 -- 函式: locale.currency (val, symbol=True, grouping=False,
          international=False)

     Formats a number 'val' according to the current *note LC_MONETARY:
     3b27. settings.

     The returned string includes the currency symbol if 'symbol' is
     true, which is the default.  If 'grouping' is ‘True’ (which is not
     the default), grouping is done with the value.  If 'international'
     is ‘True’ (which is not the default), the international currency
     symbol is used.

          備註: This function will not work with the 'C' locale, so you
          have to set a locale via *note setlocale(): 2bb. first.

 -- 函式: locale.str (float)

     Formats a floating-point number using the same format as the
     built-in function ‘str(float)’, but takes the decimal point into
     account.

 -- 函式: locale.delocalize (string)

     Converts a string into a normalized number string, following the
     *note LC_NUMERIC: 3b25. settings.

     在 3.5 版被加入.

 -- 函式: locale.localize (string, grouping=False, monetary=False)

     Converts a normalized number string into a formatted string
     following the *note LC_NUMERIC: 3b25. settings.

     在 3.10 版被加入.

 -- 函式: locale.atof (string, func=float)

     Converts a string to a number, following the *note LC_NUMERIC:
     3b25. settings, by calling 'func' on the result of calling *note
     delocalize(): dcb. on 'string'.

 -- 函式: locale.atoi (string)

     Converts a string to an integer, following the *note LC_NUMERIC:
     3b25. conventions.

 -- 資料: locale.LC_CTYPE

     Locale category for the character type functions.  Most
     importantly, this category defines the text encoding, i.e.  how
     bytes are interpreted as Unicode codepoints.  See PEP 538(4) and
     PEP 540(5) for how this variable might be automatically coerced to
     ‘C.UTF-8’ to avoid issues created by invalid settings in containers
     or incompatible settings passed over remote SSH connections.

     Python doesn't internally use locale-dependent character
     transformation functions from ‘ctype.h’.  Instead, an internal
     ‘pyctype.h’ provides locale-independent equivalents like
     ‘Py_TOLOWER’.

 -- 資料: locale.LC_COLLATE

     Locale category for sorting strings.  The functions *note
     strcoll(): 3b62. and *note strxfrm(): 3b64. of the *note locale:
     7a. module are affected.

 -- 資料: locale.LC_TIME

     Locale category for the formatting of time.  The function *note
     time.strftime(): 1181. follows these conventions.

 -- 資料: locale.LC_MONETARY

     Locale category for formatting of monetary values.  The available
     options are available from the *note localeconv(): ba5. function.

 -- 資料: locale.LC_MESSAGES

     Locale category for message display.  Python currently does not
     support application specific locale-aware messages.  Messages
     displayed by the operating system, like those returned by *note
     os.strerror(): 2a0f. might be affected by this category.

     This value may not be available on operating systems not conforming
     to the POSIX standard, most notably Windows.

 -- 資料: locale.LC_NUMERIC

     Locale category for formatting numbers.  The functions *note
     format_string(): 4c3, *note atoi(): 3b69, *note atof(): 3b68. and
     *note str(): 3b66. of the *note locale: 7a. module are affected by
     that category.  All other numeric formatting operations are not
     affected.

 -- 資料: locale.LC_ALL

     Combination of all locale settings.  If this flag is used when the
     locale is changed, setting the locale for all categories is
     attempted.  If that fails for any category, no category is changed
     at all.  When the locale is retrieved using this flag, a string
     indicating the setting for all categories is returned.  This string
     can be later used to restore the settings.

 -- 資料: locale.CHAR_MAX

     This is a symbolic constant used for different values returned by
     *note localeconv(): ba5.

範例：

     >>> import locale
     >>> loc = locale.getlocale()  # get current locale
     # use German locale; name might vary with platform
     >>> locale.setlocale(locale.LC_ALL, 'de_DE')
     >>> locale.strcoll('f\xe4n', 'foo')  # compare a string containing an umlaut
     >>> locale.setlocale(locale.LC_ALL, '')   # use user's preferred locale
     >>> locale.setlocale(locale.LC_ALL, 'C')  # use default (C) locale
     >>> locale.setlocale(locale.LC_ALL, loc)  # restore saved locale

* Menu:

* Background, details, hints, tips and caveats: Background details hints tips and caveats.
* For extension writers and programs that embed Python::
* Access to message catalogs::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/locale.py

   (2) https://datatracker.ietf.org/doc/html/rfc1766.html

   (3) https://datatracker.ietf.org/doc/html/rfc1766.html

   (4) https://peps.python.org/pep-0538/

   (5) https://peps.python.org/pep-0540/


File: python.info,  Node: Background details hints tips and caveats,  Next: For extension writers and programs that embed Python,  Up: locale --- 國際化服務

5.23.2.1 Background, details, hints, tips and caveats
.....................................................

The C standard defines the locale as a program-wide property that may be
relatively expensive to change.  On top of that, some implementations
are broken in such a way that frequent locale changes may cause core
dumps.  This makes the locale somewhat painful to use correctly.

Initially, when a program is started, the locale is the ‘C’ locale, no
matter what the user's preferred locale is.  There is one exception: the
*note LC_CTYPE: 3b5f. category is changed at startup to set the current
locale encoding to the user's preferred locale encoding.  The program
must explicitly say that it wants the user's preferred locale settings
for other categories by calling ‘setlocale(LC_ALL, '')’.

It is generally a bad idea to call *note setlocale(): 2bb. in some
library routine, since as a side effect it affects the entire program.
Saving and restoring it is almost as bad: it is expensive and affects
other threads that happen to run before the settings have been restored.

If, when coding a module for general use, you need a locale independent
version of an operation that is affected by the locale (such as certain
formats used with *note time.strftime(): 1181.), you will have to find a
way to do it without using the standard library routine.  Even better is
convincing yourself that using locale settings is okay.  Only as a last
resort should you document that your module is not compatible with
non-‘C’ locale settings.

The only way to perform numeric operations according to the locale is to
use the special functions defined by this module: *note atof(): 3b68,
*note atoi(): 3b69, *note format_string(): 4c3, *note str(): 3b66.

There is no way to perform case conversions and character
classifications according to the locale.  For (Unicode) text strings
these are done according to the character value only, while for byte
strings, the conversions and classifications are done according to the
ASCII value of the byte, and bytes whose high bit is set (i.e.,
non-ASCII bytes) are never converted or considered part of a character
class such as letter or whitespace.


File: python.info,  Node: For extension writers and programs that embed Python,  Next: Access to message catalogs,  Prev: Background details hints tips and caveats,  Up: locale --- 國際化服務

5.23.2.2 For extension writers and programs that embed Python
.............................................................

Extension modules should never call *note setlocale(): 2bb, except to
find out what the current locale is.  But since the return value can
only be used portably to restore it, that is not very useful (except
perhaps to find out whether or not the locale is ‘C’).

When Python code uses the *note locale: 7a. module to change the locale,
this also affects the embedding application.  If the embedding
application doesn't want this to happen, it should remove the ‘_locale’
extension module (which does all the work) from the table of built-in
modules in the ‘config.c’ file, and make sure that the ‘_locale’ module
is not accessible as a shared library.


File: python.info,  Node: Access to message catalogs,  Prev: For extension writers and programs that embed Python,  Up: locale --- 國際化服務

5.23.2.3 Access to message catalogs
...................................

 -- 函式: locale.gettext (msg)

 -- 函式: locale.dgettext (domain, msg)

 -- 函式: locale.dcgettext (domain, msg, category)

 -- 函式: locale.textdomain (domain)

 -- 函式: locale.bindtextdomain (domain, dir)

 -- 函式: locale.bind_textdomain_codeset (domain, codeset)

The locale module exposes the C library's gettext interface on systems
that provide this interface.  It consists of the functions *note
gettext(): 59, *note dgettext(): 3b72, *note dcgettext(): 3b73, *note
textdomain(): 3b74, *note bindtextdomain(): 3b75, and *note
bind_textdomain_codeset(): 3b76.  These are similar to the same
functions in the *note gettext: 59. module, but use the C library's
binary format for message catalogs, and the C library's search
algorithms for locating message catalogs.

Python applications should normally find no need to invoke these
functions, and should use *note gettext: 59. instead.  A known exception
to this rule are applications that link with additional C libraries
which internally invoke C functions ‘gettext’ or ‘dcgettext’.  For these
applications, it may be necessary to bind the text domain, so that the
libraries can properly locate their message catalogs.


File: python.info,  Node: 程式框架,  Next: 以 Tk 打造圖形使用者介面 Graphical User Interfaces,  Prev: 國際化,  Up: Python 標準函式庫 Standard Library

5.24 程式框架
=============

The modules described in this chapter are frameworks that will largely
dictate the structure of your program.  Currently the modules described
here are all oriented toward writing command-line interfaces.

完整的模組列表為：

* Menu:

* turtle: turtle --- 龜圖學 Turtle graphics. 龜圖學 (Turtle graphics)
* cmd: cmd --- 以列為導向的指令直譯器支援. 以列為導向的指令直譯器支援
* shlex: shlex --- 簡單的語法分析. 簡單的語法分析


File: python.info,  Node: turtle --- 龜圖學 Turtle graphics,  Next: cmd --- 以列為導向的指令直譯器支援,  Up: 程式框架

5.24.1 ‘turtle’ -- 龜圖學 (Turtle graphics)
-------------------------------------------

'原始碼：'Lib/turtle.py(1)

__________________________________________________________________

* Menu:

* 介紹::
* Get started::
* 教學: 教學<3>.
* How to...: How to.
* Turtle graphics reference::
* Methods of RawTurtle/Turtle and corresponding functions::
* Methods of TurtleScreen/Screen and corresponding functions::
* Public classes::
* 解釋: 解釋<2>.
* Help and configuration::
* turtledemo: turtledemo --- Demo scripts. Demo scripts
* Changes since Python 2.6: Changes since Python 2 6.
* Changes since Python 3.0: Changes since Python 3 0.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/turtle.py


File: python.info,  Node: 介紹,  Next: Get started,  Up: turtle --- 龜圖學 Turtle graphics

5.24.1.1 介紹
.............

龜圖學是由 Wally Feurzeig，Seymour Papert 與 Cynthia Solomon 於 1967 年
開發的，一個 以 Logo 程式語言撰寫的廣受歡迎的幾何繪圖工具(1)。

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Turtle_(robot)


File: python.info,  Node: Get started,  Next: 教學<3>,  Prev: 介紹,  Up: turtle --- 龜圖學 Turtle graphics

5.24.1.2 Get started
....................

Imagine a robotic turtle starting at (0, 0) in the x-y plane.  After an
‘import turtle’, give it the command ‘turtle.forward(15)’, and it moves
(on-screen!)  15 pixels in the direction it is facing, drawing a line as
it moves.  Give it the command ‘turtle.right(25)’, and it rotates
in-place 25 degrees clockwise.

Turtle star
...........

龜可以使用重複簡單動作之程式來畫出複雜的形狀。

[image src="python-figures/turtle-star.png"]


In Python, turtle graphics provides a representation of a physical
"turtle" (a little robot with a pen) that draws on a sheet of paper on
the floor.

It's an effective and well-proven way for learners to encounter
programming concepts and interaction with software, as it provides
instant, visible feedback.  It also provides convenient access to
graphical output in general.

Turtle drawing was originally created as an educational tool, to be used
by teachers in the classroom.  For the programmer who needs to produce
some graphical output it can be a way to do that without the overhead of
introducing more complex or external libraries into their work.


File: python.info,  Node: 教學<3>,  Next: How to,  Prev: Get started,  Up: turtle --- 龜圖學 Turtle graphics

5.24.1.3 教學
.............

New users should start here.  In this tutorial we'll explore some of the
basics of turtle drawing.

* Menu:

* 啟動一個烏龜環境::
* 基本繪圖::
* Making algorithmic patterns::


File: python.info,  Node: 啟動一個烏龜環境,  Next: 基本繪圖,  Up: 教學<3>

5.24.1.4 啟動一個烏龜環境
.........................

在 Python shell 中，引入 ‘turtle’ 模組中所有物件：

     from turtle import *

If you run into a ‘No module named '_tkinter'’ error, you'll have to
install the *note Tk interface package: d9. on your system.


File: python.info,  Node: 基本繪圖,  Next: Making algorithmic patterns,  Prev: 啟動一個烏龜環境,  Up: 教學<3>

5.24.1.5 基本繪圖
.................

Send the turtle forward 100 steps:

     forward(100)

You should see (most likely, in a new window on your display) a line
drawn by the turtle, heading East.  Change the direction of the turtle,
so that it turns 120 degrees left (anti-clockwise):

     left(120)

Let's continue by drawing a triangle:

     forward(100)
     left(120)
     forward(100)

Notice how the turtle, represented by an arrow, points in different
directions as you steer it.

Experiment with those commands, and also with ‘backward()’ and
‘right()’.

* Menu:

* Pen control::
* The turtle's position::


File: python.info,  Node: Pen control,  Next: The turtle's position,  Up: 基本繪圖

5.24.1.6 Pen control
....................

Try changing the color - for example, ‘color('blue')’ - and width of the
line - for example, ‘width(3)’ - and then drawing again.

You can also move the turtle around without drawing, by lifting up the
pen: ‘up()’ before moving.  To start drawing again, use ‘down()’.


File: python.info,  Node: The turtle's position,  Prev: Pen control,  Up: 基本繪圖

5.24.1.7 The turtle's position
..............................

Send your turtle back to its starting-point (useful if it has
disappeared off-screen):

     home()

The home position is at the center of the turtle's screen.  If you ever
need to know them, get the turtle's x-y coordinates with:

     pos()

Home is at ‘(0, 0)’.

And after a while, it will probably help to clear the window so we can
start anew:

     clearscreen()


File: python.info,  Node: Making algorithmic patterns,  Prev: 基本繪圖,  Up: 教學<3>

5.24.1.8 Making algorithmic patterns
....................................

Using loops, it's possible to build up geometric patterns:

     for steps in range(100):
         for c in ('blue', 'red', 'green'):
             color(c)
             forward(steps)
             right(30)

- which of course, are limited only by the imagination!

Let's draw the star shape at the top of this page.  We want red lines,
filled in with yellow:

     color('red')
     fillcolor('yellow')

Just as ‘up()’ and ‘down()’ determine whether lines will be drawn,
filling can be turned on and off:

     begin_fill()

Next we'll create a loop:

     while True:
         forward(200)
         left(170)
         if abs(pos()) < 1:
             break

‘abs(pos()) < 1’ is a good way to know when the turtle is back at its
home position.

Finally, complete the filling:

     end_fill()

(Note that filling only actually takes place when you give the
‘end_fill()’ command.)


File: python.info,  Node: How to,  Next: Turtle graphics reference,  Prev: 教學<3>,  Up: turtle --- 龜圖學 Turtle graphics

5.24.1.9 How to...
..................

This section covers some typical turtle use-cases and approaches.

* Menu:

* Get started as quickly as possible::
* Use the turtle module namespace::
* Use turtle graphics in a script::
* Use object-oriented turtle graphics::


File: python.info,  Node: Get started as quickly as possible,  Next: Use the turtle module namespace,  Up: How to

5.24.1.10 Get started as quickly as possible
............................................

One of the joys of turtle graphics is the immediate, visual feedback
that's available from simple commands - it's an excellent way to
introduce children to programming ideas, with a minimum of overhead (not
just children, of course).

The turtle module makes this possible by exposing all its basic
functionality as functions, available with ‘from turtle import *’.  The
*note turtle graphics tutorial: 3b7e. covers this approach.

It's worth noting that many of the turtle commands also have even more
terse equivalents, such as ‘fd()’ for *note forward(): 3b88.  These are
especially useful when working with learners for whom typing is not a
skill.

     You'll need to have the *note Tk interface package: d9. installed
     on your system for turtle graphics to work.  Be warned that this is
     not always straightforward, so check this in advance if you're
     planning to use turtle graphics with a learner.


File: python.info,  Node: Use the turtle module namespace,  Next: Use turtle graphics in a script,  Prev: Get started as quickly as possible,  Up: How to

5.24.1.11 Use the ‘turtle’ module namespace
...........................................

Using ‘from turtle import *’ is convenient - but be warned that it
imports a rather large collection of objects, and if you're doing
anything but turtle graphics you run the risk of a name conflict (this
becomes even more an issue if you're using turtle graphics in a script
where other modules might be imported).

The solution is to use ‘import turtle’ - ‘fd()’ becomes ‘turtle.fd()’,
‘width()’ becomes ‘turtle.width()’ and so on.  (If typing "turtle" over
and over again becomes tedious, use for example ‘import turtle as t’
instead.)


File: python.info,  Node: Use turtle graphics in a script,  Next: Use object-oriented turtle graphics,  Prev: Use the turtle module namespace,  Up: How to

5.24.1.12 Use turtle graphics in a script
.........................................

It's recommended to use the ‘turtle’ module namespace as described
immediately above, for example:

     import turtle as t
     from random import random

     for i in range(100):
         steps = int(random() * 100)
         angle = int(random() * 360)
         t.right(angle)
         t.fd(steps)

Another step is also required though - as soon as the script ends,
Python will also close the turtle's window.  Add:

     t.mainloop()

to the end of the script.  The script will now wait to be dismissed and
will not exit until it is terminated, for example by closing the turtle
graphics window.


File: python.info,  Node: Use object-oriented turtle graphics,  Prev: Use turtle graphics in a script,  Up: How to

5.24.1.13 Use object-oriented turtle graphics
.............................................

也參考
......

*note Explanation of the object-oriented interface: 3b8d.

Other than for very basic introductory purposes, or for trying things
out as quickly as possible, it's more usual and much more powerful to
use the object-oriented approach to turtle graphics.  For example, this
allows multiple turtles on screen at once.

In this approach, the various turtle commands are methods of objects
(mostly of ‘Turtle’ objects).  You 'can' use the object-oriented
approach in the shell, but it would be more typical in a Python script.

The example above then becomes:

     from turtle import Turtle
     from random import random

     t = Turtle()
     for i in range(100):
         steps = int(random() * 100)
         angle = int(random() * 360)
         t.right(angle)
         t.fd(steps)

     t.screen.mainloop()

Note the last line.  ‘t.screen’ is an instance of the *note Screen:
3b8e. that a Turtle instance exists on; it's created automatically along
with the turtle.

The turtle's screen can be customised, for example:

     t.screen.title('Object-oriented turtle demo')
     t.screen.bgcolor("orange")


File: python.info,  Node: Turtle graphics reference,  Next: Methods of RawTurtle/Turtle and corresponding functions,  Prev: How to,  Up: turtle --- 龜圖學 Turtle graphics

5.24.1.14 Turtle graphics reference
...................................

     備註: In the following documentation the argument list for
     functions is given.  Methods, of course, have the additional first
     argument 'self' which is omitted here.

* Menu:

* Turtle methods::
* Methods of TurtleScreen/Screen::


File: python.info,  Node: Turtle methods,  Next: Methods of TurtleScreen/Screen,  Up: Turtle graphics reference

5.24.1.15 Turtle methods
........................

Turtle motion

     Move and draw

               *note forward(): 3b88. | *note fd(): 3b91.
               *note backward(): 3b92. | *note bk(): 3b93. | *note back(): 3b94.
               *note right(): 3b95. | *note rt(): 3b96.
               *note left(): 3b97. | *note lt(): 3b98.
               *note goto(): 3b99. | *note setpos(): 3b9a. | *note setposition(): 3b9b.
               *note teleport(): 1624.
               *note setx(): 3b9c.
               *note sety(): 3b9d.
               *note setheading(): 3b9e. | *note seth(): 3b9f.
               *note home(): 3ba0.
               *note circle(): 3ba1.
               *note dot(): 3ba2.
               *note stamp(): 3ba3.
               *note clearstamp(): 3ba4.
               *note clearstamps(): 3ba5.
               *note undo(): 3ba6.
               *note speed(): 3ba7.

     Tell Turtle's state

               *note position(): 3ba8. | *note pos(): 3ba9.
               *note towards(): 3baa.
               *note xcor(): 3bab.
               *note ycor(): 3bac.
               *note heading(): 3bad.
               *note distance(): 3bae.

     Setting and measurement

               *note degrees(): 3baf.
               *note radians(): 3bb0.

Pen control

     Drawing state

               *note pendown(): 3bb1. | *note pd(): 3bb2. | *note down(): 3bb3.
               *note penup(): 3bb4. | *note pu(): 3bb5. | *note up(): 3bb6.
               *note pensize(): 3bb7. | *note width(): 3bb8.
               *note pen(): 3bb9.
               *note isdown(): 3bba.

     Color control

               *note color(): 3bbb.
               *note pencolor(): 3bbc.
               *note fillcolor(): 3bbd.

     Filling

               *note filling(): 3bbe.
               *note begin_fill(): 3bbf.
               *note end_fill(): 3bc0.

     More drawing control

               *note reset(): 3bc1.
               *note clear(): 3bc2.
               *note write(): 3bc3.

Turtle state

     Visibility

               *note showturtle(): 3bc4. | *note st(): 3bc5.
               *note hideturtle(): 3bc6. | *note ht(): 3bc7.
               *note isvisible(): 3bc8.

     Appearance

               *note shape(): 3bc9.
               *note resizemode(): 3bca.
               *note shapesize(): 3bcb. | *note turtlesize(): 3bcc.
               *note shearfactor(): 3bcd.
               *note tiltangle(): 6c9.
               *note tilt(): 3bce.
               *note shapetransform(): 3bcf.
               *note get_shapepoly(): 3bd0.

Using events

          *note onclick(): 3bd1.
          *note onrelease(): 3bd2.
          *note ondrag(): 3bd3.

Special Turtle methods

          *note begin_poly(): 3bd4.
          *note end_poly(): 3bd5.
          *note get_poly(): 3bd6.
          *note clone(): 3bd7.
          *note getturtle(): 3bd8. | *note getpen(): 3bd9.
          *note getscreen(): 3bda.
          *note setundobuffer(): 3bdb.
          *note undobufferentries(): 3bdc.


File: python.info,  Node: Methods of TurtleScreen/Screen,  Prev: Turtle methods,  Up: Turtle graphics reference

5.24.1.16 Methods of TurtleScreen/Screen
........................................

Window control

          *note bgcolor(): 3bde.
          *note bgpic(): 3bdf.
          *note clearscreen(): 3be0.
          *note resetscreen(): 3be1.
          *note screensize(): 3be2.
          *note setworldcoordinates(): 3be3.

Animation control

          *note delay(): 3be4.
          *note tracer(): 3be5.
          *note update(): 3be6.

Using screen events

          *note listen(): 3be7.
          *note onkey(): 3be8. | *note onkeyrelease(): 3be9.
          *note onkeypress(): 3bea.
          *note onclick(): 3bd1. | *note onscreenclick(): 3beb.
          *note ontimer(): 3bec.
          *note mainloop(): 3bed. | *note done(): 3bee.

Settings and special methods

          *note mode(): 3bef.
          *note colormode(): 3bf0.
          *note getcanvas(): 3bf1.
          *note getshapes(): 3bf2.
          *note register_shape(): 3bf3. | *note addshape(): 3bf4.
          *note turtles(): 3bf5.
          *note window_height(): 3bf6.
          *note window_width(): 3bf7.

Input methods

          *note textinput(): 17c5.
          *note numinput(): 17c6.

Methods specific to Screen

          *note bye(): 3bf8.
          *note exitonclick(): 3bf9.
          *note setup(): 3bfa.
          *note title(): 3bfb.


File: python.info,  Node: Methods of RawTurtle/Turtle and corresponding functions,  Next: Methods of TurtleScreen/Screen and corresponding functions,  Prev: Turtle graphics reference,  Up: turtle --- 龜圖學 Turtle graphics

5.24.1.17 Methods of RawTurtle/Turtle and corresponding functions
.................................................................

Most of the examples in this section refer to a Turtle instance called
‘turtle’.

* Menu:

* Turtle motion::
* Tell Turtle's state::
* Settings for measurement::
* Pen control: Pen control<2>.
* Turtle state::
* Using events::
* Special Turtle methods::
* Compound shapes::


File: python.info,  Node: Turtle motion,  Next: Tell Turtle's state,  Up: Methods of RawTurtle/Turtle and corresponding functions

5.24.1.18 Turtle motion
.......................

 -- 函式: turtle.forward (distance)
 -- 函式: turtle.fd (distance)


     參數: ‘distance’ - a number (integer or float)

     Move the turtle forward by the specified 'distance', in the
     direction the turtle is headed.

          >>> turtle.position()
          (0.00,0.00)
          >>> turtle.forward(25)
          >>> turtle.position()
          (25.00,0.00)
          >>> turtle.forward(-75)
          >>> turtle.position()
          (-50.00,0.00)

 -- 函式: turtle.back (distance)
 -- 函式: turtle.bk (distance)
 -- 函式: turtle.backward (distance)


     參數: ‘distance’ - a number

     Move the turtle backward by 'distance', opposite to the direction
     the turtle is headed.  Do not change the turtle's heading.

          >>> turtle.position()
          (0.00,0.00)
          >>> turtle.backward(30)
          >>> turtle.position()
          (-30.00,0.00)

 -- 函式: turtle.right (angle)
 -- 函式: turtle.rt (angle)


     參數: ‘angle’ - a number (integer or float)

     Turn turtle right by 'angle' units.  (Units are by default degrees,
     but can be set via the *note degrees(): 3baf. and *note radians():
     3bb0. functions.)  Angle orientation depends on the turtle mode,
     see *note mode(): 3bef.

          >>> turtle.heading()
          22.0
          >>> turtle.right(45)
          >>> turtle.heading()
          337.0

 -- 函式: turtle.left (angle)
 -- 函式: turtle.lt (angle)


     參數: ‘angle’ - a number (integer or float)

     Turn turtle left by 'angle' units.  (Units are by default degrees,
     but can be set via the *note degrees(): 3baf. and *note radians():
     3bb0. functions.)  Angle orientation depends on the turtle mode,
     see *note mode(): 3bef.

          >>> turtle.heading()
          22.0
          >>> turtle.left(45)
          >>> turtle.heading()
          67.0

 -- 函式: turtle.goto (x, y=None)
 -- 函式: turtle.setpos (x, y=None)
 -- 函式: turtle.setposition (x, y=None)


     參數:

        * ‘x’ - a number or a pair/vector of numbers

        * ‘y’ - a number or ‘None’

     If 'y' is ‘None’, 'x' must be a pair of coordinates or a *note
     Vec2D: 3bfe. (e.g.  as returned by *note pos(): 3ba9.).

     Move turtle to an absolute position.  If the pen is down, draw
     line.  Do not change the turtle's orientation.

          >>> tp = turtle.pos()
          >>> tp
          (0.00,0.00)
          >>> turtle.setpos(60,30)
          >>> turtle.pos()
          (60.00,30.00)
          >>> turtle.setpos((20,80))
          >>> turtle.pos()
          (20.00,80.00)
          >>> turtle.setpos(tp)
          >>> turtle.pos()
          (0.00,0.00)

 -- 函式: turtle.teleport (x, y=None, *, fill_gap=False)


     參數:

        * ‘x’ - a number or ‘None’

        * ‘y’ - a number or ‘None’

        * ‘fill_gap’ - a boolean

     Move turtle to an absolute position.  Unlike goto(x, y), a line
     will not be drawn.  The turtle's orientation does not change.  If
     currently filling, the polygon(s) teleported from will be filled
     after leaving, and filling will begin again after teleporting.
     This can be disabled with fill_gap=True, which makes the imaginary
     line traveled during teleporting act as a fill barrier like in
     goto(x, y).

          >>> tp = turtle.pos()
          >>> tp
          (0.00,0.00)
          >>> turtle.teleport(60)
          >>> turtle.pos()
          (60.00,0.00)
          >>> turtle.teleport(y=10)
          >>> turtle.pos()
          (60.00,10.00)
          >>> turtle.teleport(20, 30)
          >>> turtle.pos()
          (20.00,30.00)

     在 3.12 版被加入.

 -- 函式: turtle.setx (x)


     參數: ‘x’ - a number (integer or float)

     Set the turtle's first coordinate to 'x', leave second coordinate
     unchanged.

          >>> turtle.position()
          (0.00,240.00)
          >>> turtle.setx(10)
          >>> turtle.position()
          (10.00,240.00)

 -- 函式: turtle.sety (y)


     參數: ‘y’ - a number (integer or float)

     Set the turtle's second coordinate to 'y', leave first coordinate
     unchanged.

          >>> turtle.position()
          (0.00,40.00)
          >>> turtle.sety(-10)
          >>> turtle.position()
          (0.00,-10.00)

 -- 函式: turtle.setheading (to_angle)
 -- 函式: turtle.seth (to_angle)


     參數: ‘to_angle’ - a number (integer or float)

     Set the orientation of the turtle to 'to_angle'.  Here are some
     common directions in degrees:

     standard mode           logo mode
                             
     -------------------------------------------------
                             
     0 - east                0 - north
                             
                             
     90 - north              90 - east
                             
                             
     180 - west              180 - south
                             
                             
     270 - south             270 - west
                             

          >>> turtle.setheading(90)
          >>> turtle.heading()
          90.0

 -- 函式: turtle.home ()

     Move turtle to the origin - coordinates (0,0) - and set its heading
     to its start-orientation (which depends on the mode, see *note
     mode(): 3bef.).

          >>> turtle.heading()
          90.0
          >>> turtle.position()
          (0.00,-10.00)
          >>> turtle.home()
          >>> turtle.position()
          (0.00,0.00)
          >>> turtle.heading()
          0.0

 -- 函式: turtle.circle (radius, extent=None, steps=None)


     參數:

        * ‘radius’ - a number

        * ‘extent’ - a number (or ‘None’)

        * ‘steps’ - an integer (or ‘None’)

     Draw a circle with given 'radius'.  The center is 'radius' units
     left of the turtle; 'extent' - an angle - determines which part of
     the circle is drawn.  If 'extent' is not given, draw the entire
     circle.  If 'extent' is not a full circle, one endpoint of the arc
     is the current pen position.  Draw the arc in counterclockwise
     direction if 'radius' is positive, otherwise in clockwise
     direction.  Finally the direction of the turtle is changed by the
     amount of 'extent'.

     As the circle is approximated by an inscribed regular polygon,
     'steps' determines the number of steps to use.  If not given, it
     will be calculated automatically.  May be used to draw regular
     polygons.

          >>> turtle.home()
          >>> turtle.position()
          (0.00,0.00)
          >>> turtle.heading()
          0.0
          >>> turtle.circle(50)
          >>> turtle.position()
          (-0.00,0.00)
          >>> turtle.heading()
          0.0
          >>> turtle.circle(120, 180)  # draw a semicircle
          >>> turtle.position()
          (0.00,240.00)
          >>> turtle.heading()
          180.0

 -- 函式: turtle.dot (size=None, *color)


     參數:

        * ‘size’ - an integer >= 1 (if given)

        * ‘color’ - a colorstring or a numeric color tuple

     Draw a circular dot with diameter 'size', using 'color'.  If 'size'
     is not given, the maximum of pensize+4 and 2*pensize is used.

          >>> turtle.home()
          >>> turtle.dot()
          >>> turtle.fd(50); turtle.dot(20, "blue"); turtle.fd(50)
          >>> turtle.position()
          (100.00,-0.00)
          >>> turtle.heading()
          0.0

 -- 函式: turtle.stamp ()

     Stamp a copy of the turtle shape onto the canvas at the current
     turtle position.  Return a stamp_id for that stamp, which can be
     used to delete it by calling ‘clearstamp(stamp_id)’.

          >>> turtle.color("blue")
          >>> stamp_id = turtle.stamp()
          >>> turtle.fd(50)

 -- 函式: turtle.clearstamp (stampid)


     參數: ‘stampid’ - an integer, must be return value of previous
     *note stamp(): 3ba3. call

     Delete stamp with given 'stampid'.

          >>> turtle.position()
          (150.00,-0.00)
          >>> turtle.color("blue")
          >>> astamp = turtle.stamp()
          >>> turtle.fd(50)
          >>> turtle.position()
          (200.00,-0.00)
          >>> turtle.clearstamp(astamp)
          >>> turtle.position()
          (200.00,-0.00)

 -- 函式: turtle.clearstamps (n=None)


     參數: ‘n’ - an integer (or ‘None’)

     Delete all or first/last 'n' of turtle's stamps.  If 'n' is ‘None’,
     delete all stamps, if 'n' > 0 delete first 'n' stamps, else if 'n'
     < 0 delete last 'n' stamps.

          >>> for i in range(8):
          ...     unused_stamp_id = turtle.stamp()
          ...     turtle.fd(30)
          >>> turtle.clearstamps(2)
          >>> turtle.clearstamps(-2)
          >>> turtle.clearstamps()

 -- 函式: turtle.undo ()

     Undo (repeatedly) the last turtle action(s).  Number of available
     undo actions is determined by the size of the undobuffer.

          >>> for i in range(4):
          ...     turtle.fd(50); turtle.lt(80)
          ...
          >>> for i in range(8):
          ...     turtle.undo()

 -- 函式: turtle.speed (speed=None)


     參數: ‘speed’ - an integer in the range 0..10 or a speedstring (see
     below)

     Set the turtle's speed to an integer value in the range 0..10.  If
     no argument is given, return current speed.

     If input is a number greater than 10 or smaller than 0.5, speed is
     set to 0.  Speedstrings are mapped to speedvalues as follows:

        * "fastest": 0

        * "fast": 10

        * "normal": 6

        * "slow": 3

        * "slowest": 1

     Speeds from 1 to 10 enforce increasingly faster animation of line
     drawing and turtle turning.

     Attention: 'speed' = 0 means that 'no' animation takes place.
     forward/back makes turtle jump and likewise left/right make the
     turtle turn instantly.

          >>> turtle.speed()
          3
          >>> turtle.speed('normal')
          >>> turtle.speed()
          6
          >>> turtle.speed(9)
          >>> turtle.speed()
          9


File: python.info,  Node: Tell Turtle's state,  Next: Settings for measurement,  Prev: Turtle motion,  Up: Methods of RawTurtle/Turtle and corresponding functions

5.24.1.19 Tell Turtle's state
.............................

 -- 函式: turtle.position ()
 -- 函式: turtle.pos ()

     Return the turtle's current location (x,y) (as a *note Vec2D: 3bfe.
     vector).

          >>> turtle.pos()
          (440.00,-0.00)

 -- 函式: turtle.towards (x, y=None)


     參數:

        * ‘x’ - a number or a pair/vector of numbers or a turtle
          instance

        * ‘y’ - a number if 'x' is a number, else ‘None’

     Return the angle between the line from turtle position to position
     specified by (x,y), the vector or the other turtle.  This depends
     on the turtle's start orientation which depends on the mode -
     "standard"/"world" or "logo".

          >>> turtle.goto(10, 10)
          >>> turtle.towards(0,0)
          225.0

 -- 函式: turtle.xcor ()

     Return the turtle's x coordinate.

          >>> turtle.home()
          >>> turtle.left(50)
          >>> turtle.forward(100)
          >>> turtle.pos()
          (64.28,76.60)
          >>> print(round(turtle.xcor(), 5))
          64.27876

 -- 函式: turtle.ycor ()

     Return the turtle's y coordinate.

          >>> turtle.home()
          >>> turtle.left(60)
          >>> turtle.forward(100)
          >>> print(turtle.pos())
          (50.00,86.60)
          >>> print(round(turtle.ycor(), 5))
          86.60254

 -- 函式: turtle.heading ()

     Return the turtle's current heading (value depends on the turtle
     mode, see *note mode(): 3bef.).

          >>> turtle.home()
          >>> turtle.left(67)
          >>> turtle.heading()
          67.0

 -- 函式: turtle.distance (x, y=None)


     參數:

        * ‘x’ - a number or a pair/vector of numbers or a turtle
          instance

        * ‘y’ - a number if 'x' is a number, else ‘None’

     Return the distance from the turtle to (x,y), the given vector, or
     the given other turtle, in turtle step units.

          >>> turtle.home()
          >>> turtle.distance(30,40)
          50.0
          >>> turtle.distance((30,40))
          50.0
          >>> joe = Turtle()
          >>> joe.forward(77)
          >>> turtle.distance(joe)
          77.0


File: python.info,  Node: Settings for measurement,  Next: Pen control<2>,  Prev: Tell Turtle's state,  Up: Methods of RawTurtle/Turtle and corresponding functions

5.24.1.20 Settings for measurement
..................................

 -- 函式: turtle.degrees (fullcircle=360.0)


     參數: ‘fullcircle’ - a number

     Set angle measurement units, i.e.  set number of "degrees" for a
     full circle.  Default value is 360 degrees.

          >>> turtle.home()
          >>> turtle.left(90)
          >>> turtle.heading()
          90.0

          Change angle measurement unit to grad (also known as gon,
          grade, or gradian and equals 1/100-th of the right angle.)
          >>> turtle.degrees(400.0)
          >>> turtle.heading()
          100.0
          >>> turtle.degrees(360)
          >>> turtle.heading()
          90.0

 -- 函式: turtle.radians ()

     Set the angle measurement units to radians.  Equivalent to
     ‘degrees(2*math.pi)’.

          >>> turtle.home()
          >>> turtle.left(90)
          >>> turtle.heading()
          90.0
          >>> turtle.radians()
          >>> turtle.heading()
          1.5707963267948966


File: python.info,  Node: Pen control<2>,  Next: Turtle state,  Prev: Settings for measurement,  Up: Methods of RawTurtle/Turtle and corresponding functions

5.24.1.21 Pen control
.....................

* Menu:

* Drawing state::
* Color control::
* Filling::
* More drawing control::


File: python.info,  Node: Drawing state,  Next: Color control,  Up: Pen control<2>

5.24.1.22 Drawing state
.......................

 -- 函式: turtle.pendown ()
 -- 函式: turtle.pd ()
 -- 函式: turtle.down ()

     Pull the pen down - drawing when moving.

 -- 函式: turtle.penup ()
 -- 函式: turtle.pu ()
 -- 函式: turtle.up ()

     Pull the pen up - no drawing when moving.

 -- 函式: turtle.pensize (width=None)
 -- 函式: turtle.width (width=None)


     參數: ‘width’ - a positive number

     Set the line thickness to 'width' or return it.  If resizemode is
     set to "auto" and turtleshape is a polygon, that polygon is drawn
     with the same line thickness.  If no argument is given, the current
     pensize is returned.

          >>> turtle.pensize()
          1
          >>> turtle.pensize(10)   # from here on lines of width 10 are drawn

 -- 函式: turtle.pen (pen=None, **pendict)


     參數:

        * ‘pen’ - a dictionary with some or all of the below listed keys

        * ‘pendict’ - one or more keyword-arguments with the below
          listed keys as keywords

     Return or set the pen's attributes in a "pen-dictionary" with the
     following key/value pairs:

        * "shown": True/False

        * "pendown": True/False

        * "pencolor": color-string or color-tuple

        * "fillcolor": color-string or color-tuple

        * "pensize": positive number

        * "speed": number in range 0..10

        * "resizemode": "auto" or "user" or "noresize"

        * "stretchfactor": (positive number, positive number)

        * "outline": positive number

        * "tilt": number

     This dictionary can be used as argument for a subsequent call to
     *note pen(): 3bb9. to restore the former pen-state.  Moreover one
     or more of these attributes can be provided as keyword-arguments.
     This can be used to set several pen attributes in one statement.

          >>> turtle.pen(fillcolor="black", pencolor="red", pensize=10)
          >>> sorted(turtle.pen().items())
          [('fillcolor', 'black'), ('outline', 1), ('pencolor', 'red'),
           ('pendown', True), ('pensize', 10), ('resizemode', 'noresize'),
           ('shearfactor', 0.0), ('shown', True), ('speed', 9),
           ('stretchfactor', (1.0, 1.0)), ('tilt', 0.0)]
          >>> penstate=turtle.pen()
          >>> turtle.color("yellow", "")
          >>> turtle.penup()
          >>> sorted(turtle.pen().items())[:3]
          [('fillcolor', ''), ('outline', 1), ('pencolor', 'yellow')]
          >>> turtle.pen(penstate, fillcolor="green")
          >>> sorted(turtle.pen().items())[:3]
          [('fillcolor', 'green'), ('outline', 1), ('pencolor', 'red')]

 -- 函式: turtle.isdown ()

     Return ‘True’ if pen is down, ‘False’ if it's up.

          >>> turtle.penup()
          >>> turtle.isdown()
          False
          >>> turtle.pendown()
          >>> turtle.isdown()
          True


File: python.info,  Node: Color control,  Next: Filling,  Prev: Drawing state,  Up: Pen control<2>

5.24.1.23 Color control
.......................

 -- 函式: turtle.pencolor (*args)

     Return or set the pencolor.

     Four input formats are allowed:

     ‘pencolor()’

          Return the current pencolor as color specification string or
          as a tuple (see example).  May be used as input to another
          color/pencolor/fillcolor call.

     ‘pencolor(colorstring)’

          Set pencolor to 'colorstring', which is a Tk color
          specification string, such as ‘"red"’, ‘"yellow"’, or
          ‘"#33cc8c"’.

     ‘pencolor((r, g, b))’

          Set pencolor to the RGB color represented by the tuple of 'r',
          'g', and 'b'.  Each of 'r', 'g', and 'b' must be in the range
          0..colormode, where colormode is either 1.0 or 255 (see *note
          colormode(): 3bf0.).

     ‘pencolor(r, g, b)’

          Set pencolor to the RGB color represented by 'r', 'g', and
          'b'.  Each of 'r', 'g', and 'b' must be in the range
          0..colormode.

     If turtleshape is a polygon, the outline of that polygon is drawn
     with the newly set pencolor.

          >>> colormode()
          1.0
          >>> turtle.pencolor()
          'red'
          >>> turtle.pencolor("brown")
          >>> turtle.pencolor()
          'brown'
          >>> tup = (0.2, 0.8, 0.55)
          >>> turtle.pencolor(tup)
          >>> turtle.pencolor()
          (0.2, 0.8, 0.5490196078431373)
          >>> colormode(255)
          >>> turtle.pencolor()
          (51.0, 204.0, 140.0)
          >>> turtle.pencolor('#32c18f')
          >>> turtle.pencolor()
          (50.0, 193.0, 143.0)

 -- 函式: turtle.fillcolor (*args)

     Return or set the fillcolor.

     Four input formats are allowed:

     ‘fillcolor()’

          Return the current fillcolor as color specification string,
          possibly in tuple format (see example).  May be used as input
          to another color/pencolor/fillcolor call.

     ‘fillcolor(colorstring)’

          Set fillcolor to 'colorstring', which is a Tk color
          specification string, such as ‘"red"’, ‘"yellow"’, or
          ‘"#33cc8c"’.

     ‘fillcolor((r, g, b))’

          Set fillcolor to the RGB color represented by the tuple of
          'r', 'g', and 'b'.  Each of 'r', 'g', and 'b' must be in the
          range 0..colormode, where colormode is either 1.0 or 255 (see
          *note colormode(): 3bf0.).

     ‘fillcolor(r, g, b)’

          Set fillcolor to the RGB color represented by 'r', 'g', and
          'b'.  Each of 'r', 'g', and 'b' must be in the range
          0..colormode.

     If turtleshape is a polygon, the interior of that polygon is drawn
     with the newly set fillcolor.

          >>> turtle.fillcolor("violet")
          >>> turtle.fillcolor()
          'violet'
          >>> turtle.pencolor()
          (50.0, 193.0, 143.0)
          >>> turtle.fillcolor((50, 193, 143))  # 為整數而非浮點數
          >>> turtle.fillcolor()
          (50.0, 193.0, 143.0)
          >>> turtle.fillcolor('#ffffff')
          >>> turtle.fillcolor()
          (255.0, 255.0, 255.0)

 -- 函式: turtle.color (*args)

     Return or set pencolor and fillcolor.

     Several input formats are allowed.  They use 0 to 3 arguments as
     follows:

     ‘color()’

          Return the current pencolor and the current fillcolor as a
          pair of color specification strings or tuples as returned by
          *note pencolor(): 3bbc. and *note fillcolor(): 3bbd.

     ‘color(colorstring)’, ‘color((r,g,b))’, ‘color(r,g,b)’

          Inputs as in *note pencolor(): 3bbc, set both, fillcolor and
          pencolor, to the given value.

     ‘color(colorstring1, colorstring2)’, ‘color((r1,g1,b1), (r2,g2,b2))’

          Equivalent to ‘pencolor(colorstring1)’ and
          ‘fillcolor(colorstring2)’ and analogously if the other input
          format is used.

     If turtleshape is a polygon, outline and interior of that polygon
     is drawn with the newly set colors.

          >>> turtle.color("red", "green")
          >>> turtle.color()
          ('red', 'green')
          >>> color("#285078", "#a0c8f0")
          >>> color()
          ((40.0, 80.0, 120.0), (160.0, 200.0, 240.0))

See also: Screen method *note colormode(): 3bf0.


File: python.info,  Node: Filling,  Next: More drawing control,  Prev: Color control,  Up: Pen control<2>

5.24.1.24 Filling
.................

 -- 函式: turtle.filling ()

     Return fillstate (‘True’ if filling, ‘False’ else).

          >>> turtle.begin_fill()
          >>> if turtle.filling():
          ...    turtle.pensize(5)
          ... else:
          ...    turtle.pensize(3)

 -- 函式: turtle.begin_fill ()

     To be called just before drawing a shape to be filled.

 -- 函式: turtle.end_fill ()

     Fill the shape drawn after the last call to *note begin_fill():
     3bbf.

     Whether or not overlap regions for self-intersecting polygons or
     multiple shapes are filled depends on the operating system
     graphics, type of overlap, and number of overlaps.  For example,
     the Turtle star above may be either all yellow or have some white
     regions.

          >>> turtle.color("black", "red")
          >>> turtle.begin_fill()
          >>> turtle.circle(80)
          >>> turtle.end_fill()


File: python.info,  Node: More drawing control,  Prev: Filling,  Up: Pen control<2>

5.24.1.25 More drawing control
..............................

 -- 函式: turtle.reset ()

     Delete the turtle's drawings from the screen, re-center the turtle
     and set variables to the default values.

          >>> turtle.goto(0,-22)
          >>> turtle.left(100)
          >>> turtle.position()
          (0.00,-22.00)
          >>> turtle.heading()
          100.0
          >>> turtle.reset()
          >>> turtle.position()
          (0.00,0.00)
          >>> turtle.heading()
          0.0

 -- 函式: turtle.clear ()

     Delete the turtle's drawings from the screen.  Do not move turtle.
     State and position of the turtle as well as drawings of other
     turtles are not affected.

 -- 函式: turtle.write (arg, move=False, align='left', font=('Arial', 8,
          'normal'))


     參數:

        * ‘arg’ - object to be written to the TurtleScreen

        * ‘move’ - True/False

        * ‘align’ - one of the strings "left", "center" or right"

        * ‘font’ - a triple (fontname, fontsize, fonttype)

     Write text - the string representation of 'arg' - at the current
     turtle position according to 'align' ("left", "center" or "right")
     and with the given font.  If 'move' is true, the pen is moved to
     the bottom-right corner of the text.  By default, 'move' is
     ‘False’.

          >>> turtle.write("Home = ", True, align="center")
          >>> turtle.write((0,0), True)


File: python.info,  Node: Turtle state,  Next: Using events,  Prev: Pen control<2>,  Up: Methods of RawTurtle/Turtle and corresponding functions

5.24.1.26 Turtle state
......................

* Menu:

* Visibility::
* Appearance::


File: python.info,  Node: Visibility,  Next: Appearance,  Up: Turtle state

5.24.1.27 Visibility
....................

 -- 函式: turtle.hideturtle ()
 -- 函式: turtle.ht ()

     Make the turtle invisible.  It's a good idea to do this while
     you're in the middle of doing some complex drawing, because hiding
     the turtle speeds up the drawing observably.

          >>> turtle.hideturtle()

 -- 函式: turtle.showturtle ()
 -- 函式: turtle.st ()

     Make the turtle visible.

          >>> turtle.showturtle()

 -- 函式: turtle.isvisible ()

     Return ‘True’ if the Turtle is shown, ‘False’ if it's hidden.

          >>> turtle.hideturtle()
          >>> turtle.isvisible()
          False
          >>> turtle.showturtle()
          >>> turtle.isvisible()
          True


File: python.info,  Node: Appearance,  Prev: Visibility,  Up: Turtle state

5.24.1.28 Appearance
....................

 -- 函式: turtle.shape (name=None)


     參數: ‘name’ - a string which is a valid shapename

     Set turtle shape to shape with given 'name' or, if name is not
     given, return name of current shape.  Shape with 'name' must exist
     in the TurtleScreen's shape dictionary.  Initially there are the
     following polygon shapes: "arrow", "turtle", "circle", "square",
     "triangle", "classic".  To learn about how to deal with shapes see
     Screen method *note register_shape(): 3bf3.

          >>> turtle.shape()
          'classic'
          >>> turtle.shape("turtle")
          >>> turtle.shape()
          'turtle'

 -- 函式: turtle.resizemode (rmode=None)


     參數: ‘rmode’ - one of the strings "auto", "user", "noresize"

     Set resizemode to one of the values: "auto", "user", "noresize".
     If 'rmode' is not given, return current resizemode.  Different
     resizemodes have the following effects:

        - "auto": adapts the appearance of the turtle corresponding to
          the value of pensize.

        - "user": adapts the appearance of the turtle according to the
          values of stretchfactor and outlinewidth (outline), which are
          set by *note shapesize(): 3bcb.

        - "noresize": no adaption of the turtle's appearance takes
          place.

     ‘resizemode("user")’ is called by *note shapesize(): 3bcb. when
     used with arguments.

          >>> turtle.resizemode()
          'noresize'
          >>> turtle.resizemode("auto")
          >>> turtle.resizemode()
          'auto'

 -- 函式: turtle.shapesize (stretch_wid=None, stretch_len=None,
          outline=None)
 -- 函式: turtle.turtlesize (stretch_wid=None, stretch_len=None,
          outline=None)


     參數:

        * ‘stretch_wid’ - positive number

        * ‘stretch_len’ - positive number

        * ‘outline’ - positive number

     Return or set the pen's attributes x/y-stretchfactors and/or
     outline.  Set resizemode to "user".  If and only if resizemode is
     set to "user", the turtle will be displayed stretched according to
     its stretchfactors: 'stretch_wid' is stretchfactor perpendicular to
     its orientation, 'stretch_len' is stretchfactor in direction of its
     orientation, 'outline' determines the width of the shape's outline.

          >>> turtle.shapesize()
          (1.0, 1.0, 1)
          >>> turtle.resizemode("user")
          >>> turtle.shapesize(5, 5, 12)
          >>> turtle.shapesize()
          (5, 5, 12)
          >>> turtle.shapesize(outline=8)
          >>> turtle.shapesize()
          (5, 5, 8)

 -- 函式: turtle.shearfactor (shear=None)


     參數: ‘shear’ - number (optional)

     Set or return the current shearfactor.  Shear the turtleshape
     according to the given shearfactor shear, which is the tangent of
     the shear angle.  Do 'not' change the turtle's heading (direction
     of movement).  If shear is not given: return the current
     shearfactor, i.  e.  the tangent of the shear angle, by which lines
     parallel to the heading of the turtle are sheared.

          >>> turtle.shape("circle")
          >>> turtle.shapesize(5,2)
          >>> turtle.shearfactor(0.5)
          >>> turtle.shearfactor()
          0.5

 -- 函式: turtle.tilt (angle)


     參數: ‘angle’ - a number

     Rotate the turtleshape by 'angle' from its current tilt-angle, but
     do 'not' change the turtle's heading (direction of movement).

          >>> turtle.reset()
          >>> turtle.shape("circle")
          >>> turtle.shapesize(5,2)
          >>> turtle.tilt(30)
          >>> turtle.fd(50)
          >>> turtle.tilt(30)
          >>> turtle.fd(50)

 -- 函式: turtle.tiltangle (angle=None)


     參數: ‘angle’ - a number (optional)

     Set or return the current tilt-angle.  If angle is given, rotate
     the turtleshape to point in the direction specified by angle,
     regardless of its current tilt-angle.  Do 'not' change the turtle's
     heading (direction of movement).  If angle is not given: return the
     current tilt-angle, i.  e.  the angle between the orientation of
     the turtleshape and the heading of the turtle (its direction of
     movement).

          >>> turtle.reset()
          >>> turtle.shape("circle")
          >>> turtle.shapesize(5,2)
          >>> turtle.tilt(45)
          >>> turtle.tiltangle()
          45.0

 -- 函式: turtle.shapetransform (t11=None, t12=None, t21=None, t22=None)


     參數:

        * ‘t11’ - a number (optional)

        * ‘t12’ - a number (optional)

        * ‘t21’ - a number (optional)

        * ‘t12’ - a number (optional)

     Set or return the current transformation matrix of the turtle
     shape.

     If none of the matrix elements are given, return the transformation
     matrix as a tuple of 4 elements.  Otherwise set the given elements
     and transform the turtleshape according to the matrix consisting of
     first row t11, t12 and second row t21, t22.  The determinant t11 *
     t22 - t12 * t21 must not be zero, otherwise an error is raised.
     Modify stretchfactor, shearfactor and tiltangle according to the
     given matrix.

          >>> turtle = Turtle()
          >>> turtle.shape("square")
          >>> turtle.shapesize(4,2)
          >>> turtle.shearfactor(-0.5)
          >>> turtle.shapetransform()
          (4.0, -1.0, -0.0, 2.0)

 -- 函式: turtle.get_shapepoly ()

     Return the current shape polygon as tuple of coordinate pairs.
     This can be used to define a new shape or components of a compound
     shape.

          >>> turtle.shape("square")
          >>> turtle.shapetransform(4, -1, 0, 2)
          >>> turtle.get_shapepoly()
          ((50, -20), (30, 20), (-50, 20), (-30, -20))


File: python.info,  Node: Using events,  Next: Special Turtle methods,  Prev: Turtle state,  Up: Methods of RawTurtle/Turtle and corresponding functions

5.24.1.29 Using events
......................

 -- 函式: turtle.onclick (fun, btn=1, add=None)


     參數:

        * ‘fun’ - a function with two arguments which will be called
          with the coordinates of the clicked point on the canvas

        * ‘btn’ - number of the mouse-button, defaults to 1 (left mouse
          button)

        * ‘add’ - ‘True’ or ‘False’ - if ‘True’, a new binding will be
          added, otherwise it will replace a former binding

     Bind 'fun' to mouse-click events on this turtle.  If 'fun' is
     ‘None’, existing bindings are removed.  Example for the anonymous
     turtle, i.e.  the procedural way:

          >>> def turn(x, y):
          ...     left(180)
          ...
          >>> onclick(turn)  # Now clicking into the turtle will turn it.
          >>> onclick(None)  # event-binding will be removed

 -- 函式: turtle.onrelease (fun, btn=1, add=None)


     參數:

        * ‘fun’ - a function with two arguments which will be called
          with the coordinates of the clicked point on the canvas

        * ‘btn’ - number of the mouse-button, defaults to 1 (left mouse
          button)

        * ‘add’ - ‘True’ or ‘False’ - if ‘True’, a new binding will be
          added, otherwise it will replace a former binding

     Bind 'fun' to mouse-button-release events on this turtle.  If 'fun'
     is ‘None’, existing bindings are removed.

          >>> class MyTurtle(Turtle):
          ...     def glow(self,x,y):
          ...         self.fillcolor("red")
          ...     def unglow(self,x,y):
          ...         self.fillcolor("")
          ...
          >>> turtle = MyTurtle()
          >>> turtle.onclick(turtle.glow)     # clicking on turtle turns fillcolor red,
          >>> turtle.onrelease(turtle.unglow) # releasing turns it to transparent.

 -- 函式: turtle.ondrag (fun, btn=1, add=None)


     參數:

        * ‘fun’ - a function with two arguments which will be called
          with the coordinates of the clicked point on the canvas

        * ‘btn’ - number of the mouse-button, defaults to 1 (left mouse
          button)

        * ‘add’ - ‘True’ or ‘False’ - if ‘True’, a new binding will be
          added, otherwise it will replace a former binding

     Bind 'fun' to mouse-move events on this turtle.  If 'fun' is
     ‘None’, existing bindings are removed.

     Remark: Every sequence of mouse-move-events on a turtle is preceded
     by a mouse-click event on that turtle.

          >>> turtle.ondrag(turtle.goto)

     Subsequently, clicking and dragging the Turtle will move it across
     the screen thereby producing handdrawings (if pen is down).


File: python.info,  Node: Special Turtle methods,  Next: Compound shapes,  Prev: Using events,  Up: Methods of RawTurtle/Turtle and corresponding functions

5.24.1.30 Special Turtle methods
................................

 -- 函式: turtle.begin_poly ()

     Start recording the vertices of a polygon.  Current turtle position
     is first vertex of polygon.

 -- 函式: turtle.end_poly ()

     Stop recording the vertices of a polygon.  Current turtle position
     is last vertex of polygon.  This will be connected with the first
     vertex.

 -- 函式: turtle.get_poly ()

     Return the last recorded polygon.

          >>> turtle.home()
          >>> turtle.begin_poly()
          >>> turtle.fd(100)
          >>> turtle.left(20)
          >>> turtle.fd(30)
          >>> turtle.left(60)
          >>> turtle.fd(50)
          >>> turtle.end_poly()
          >>> p = turtle.get_poly()
          >>> register_shape("myFavouriteShape", p)

 -- 函式: turtle.clone ()

     Create and return a clone of the turtle with same position, heading
     and turtle properties.

          >>> mick = Turtle()
          >>> joe = mick.clone()

 -- 函式: turtle.getturtle ()
 -- 函式: turtle.getpen ()

     Return the Turtle object itself.  Only reasonable use: as a
     function to return the "anonymous turtle":

          >>> pet = getturtle()
          >>> pet.fd(50)
          >>> pet
          <turtle.Turtle object at 0x...>

 -- 函式: turtle.getscreen ()

     Return the *note TurtleScreen: 3c0b. object the turtle is drawing
     on.  TurtleScreen methods can then be called for that object.

          >>> ts = turtle.getscreen()
          >>> ts
          <turtle._Screen object at 0x...>
          >>> ts.bgcolor("pink")

 -- 函式: turtle.setundobuffer (size)


     參數: ‘size’ - 一個整數或 ‘None’

     Set or disable undobuffer.  If 'size' is an integer, an empty
     undobuffer of given size is installed.  'size' gives the maximum
     number of turtle actions that can be undone by the *note undo():
     3ba6. method/function.  If 'size' is ‘None’, the undobuffer is
     disabled.

          >>> turtle.setundobuffer(42)

 -- 函式: turtle.undobufferentries ()

     Return number of entries in the undobuffer.

          >>> while undobufferentries():
          ...     undo()


File: python.info,  Node: Compound shapes,  Prev: Special Turtle methods,  Up: Methods of RawTurtle/Turtle and corresponding functions

5.24.1.31 Compound shapes
.........................

To use compound turtle shapes, which consist of several polygons of
different color, you must use the helper class *note Shape: 3c0e.
explicitly as described below:

  1. Create an empty Shape object of type "compound".

  2. Add as many components to this object as desired, using the *note
     addcomponent(): 3c0f. method.

     舉例來說：

          >>> s = Shape("compound")
          >>> poly1 = ((0,0),(10,-5),(0,10),(-10,-5))
          >>> s.addcomponent(poly1, "red", "blue")
          >>> poly2 = ((0,0),(10,-5),(-10,-5))
          >>> s.addcomponent(poly2, "blue", "red")

  3. Now add the Shape to the Screen's shapelist and use it:

          >>> register_shape("myshape", s)
          >>> shape("myshape")

     備註: The *note Shape: 3c0e. class is used internally by the *note
     register_shape(): 3bf3. method in different ways.  The application
     programmer has to deal with the Shape class 'only' when using
     compound shapes like shown above!


File: python.info,  Node: Methods of TurtleScreen/Screen and corresponding functions,  Next: Public classes,  Prev: Methods of RawTurtle/Turtle and corresponding functions,  Up: turtle --- 龜圖學 Turtle graphics

5.24.1.32 Methods of TurtleScreen/Screen and corresponding functions
....................................................................

Most of the examples in this section refer to a TurtleScreen instance
called ‘screen’.

* Menu:

* Window control::
* Animation control::
* Using screen events::
* Input methods::
* Settings and special methods::
* Methods specific to Screen, not inherited from TurtleScreen: Methods specific to Screen not inherited from TurtleScreen.


File: python.info,  Node: Window control,  Next: Animation control,  Up: Methods of TurtleScreen/Screen and corresponding functions

5.24.1.33 Window control
........................

 -- 函式: turtle.bgcolor (*args)


     參數: ‘args’ - a color string or three numbers in the range
     0..colormode or a 3-tuple of such numbers

     Set or return background color of the TurtleScreen.

          >>> screen.bgcolor("orange")
          >>> screen.bgcolor()
          'orange'
          >>> screen.bgcolor("#800080")
          >>> screen.bgcolor()
          (128.0, 0.0, 128.0)

 -- 函式: turtle.bgpic (picname=None)


     參數: ‘picname’ - a string, name of a gif-file or ‘"nopic"’, or
     ‘None’

     Set background image or return name of current backgroundimage.  If
     'picname' is a filename, set the corresponding image as background.
     If 'picname' is ‘"nopic"’, delete background image, if present.  If
     'picname' is ‘None’, return the filename of the current
     backgroundimage.

          >>> screen.bgpic()
          'nopic'
          >>> screen.bgpic("landscape.gif")
          >>> screen.bgpic()
          "landscape.gif"

 -- 函式: turtle.clear ()

          備註: This TurtleScreen method is available as a global
          function only under the name ‘clearscreen’.  The global
          function ‘clear’ is a different one derived from the Turtle
          method ‘clear’.

 -- 函式: turtle.clearscreen ()

     Delete all drawings and all turtles from the TurtleScreen.  Reset
     the now empty TurtleScreen to its initial state: white background,
     no background image, no event bindings and tracing on.

 -- 函式: turtle.reset ()

          備註: This TurtleScreen method is available as a global
          function only under the name ‘resetscreen’.  The global
          function ‘reset’ is another one derived from the Turtle method
          ‘reset’.

 -- 函式: turtle.resetscreen ()

     Reset all Turtles on the Screen to their initial state.

 -- 函式: turtle.screensize (canvwidth=None, canvheight=None, bg=None)


     參數:

        * ‘canvwidth’ - positive integer, new width of canvas in pixels

        * ‘canvheight’ - positive integer, new height of canvas in
          pixels

        * ‘bg’ - colorstring or color-tuple, new background color

     If no arguments are given, return current (canvaswidth,
     canvasheight).  Else resize the canvas the turtles are drawing on.
     Do not alter the drawing window.  To observe hidden parts of the
     canvas, use the scrollbars.  With this method, one can make visible
     those parts of a drawing which were outside the canvas before.

          >>> screen.screensize()
          (400, 300)
          >>> screen.screensize(2000,1500)
          >>> screen.screensize()
          (2000, 1500)

     e.g.  to search for an erroneously escaped turtle ;-)

 -- 函式: turtle.setworldcoordinates (llx, lly, urx, ury)


     參數:

        * ‘llx’ - a number, x-coordinate of lower left corner of canvas

        * ‘lly’ - a number, y-coordinate of lower left corner of canvas

        * ‘urx’ - a number, x-coordinate of upper right corner of canvas

        * ‘ury’ - a number, y-coordinate of upper right corner of canvas

     Set up user-defined coordinate system and switch to mode "world" if
     necessary.  This performs a ‘screen.reset()’.  If mode "world" is
     already active, all drawings are redrawn according to the new
     coordinates.

     'ATTENTION': in user-defined coordinate systems angles may appear
     distorted.

          >>> screen.reset()
          >>> screen.setworldcoordinates(-50,-7.5,50,7.5)
          >>> for _ in range(72):
          ...     left(10)
          ...
          >>> for _ in range(8):
          ...     left(45); fd(2)   # a regular octagon


File: python.info,  Node: Animation control,  Next: Using screen events,  Prev: Window control,  Up: Methods of TurtleScreen/Screen and corresponding functions

5.24.1.34 Animation control
...........................

 -- 函式: turtle.delay (delay=None)


     參數: ‘delay’ - positive integer

     Set or return the drawing 'delay' in milliseconds.  (This is
     approximately the time interval between two consecutive canvas
     updates.)  The longer the drawing delay, the slower the animation.

     Optional argument:

          >>> screen.delay()
          10
          >>> screen.delay(5)
          >>> screen.delay()
          5

 -- 函式: turtle.tracer (n=None, delay=None)


     參數:

        * ‘n’ - nonnegative integer

        * ‘delay’ - nonnegative integer

     Turn turtle animation on/off and set delay for update drawings.  If
     'n' is given, only each n-th regular screen update is really
     performed.  (Can be used to accelerate the drawing of complex
     graphics.)  When called without arguments, returns the currently
     stored value of n.  Second argument sets delay value (see *note
     delay(): 3be4.).

          >>> screen.tracer(8, 25)
          >>> dist = 2
          >>> for i in range(200):
          ...     fd(dist)
          ...     rt(90)
          ...     dist += 2

 -- 函式: turtle.update ()

     Perform a TurtleScreen update.  To be used when tracer is turned
     off.

See also the RawTurtle/Turtle method *note speed(): 3ba7.


File: python.info,  Node: Using screen events,  Next: Input methods,  Prev: Animation control,  Up: Methods of TurtleScreen/Screen and corresponding functions

5.24.1.35 Using screen events
.............................

 -- 函式: turtle.listen (xdummy=None, ydummy=None)

     Set focus on TurtleScreen (in order to collect key-events).  Dummy
     arguments are provided in order to be able to pass *note listen():
     3be7. to the onclick method.

 -- 函式: turtle.onkey (fun, key)
 -- 函式: turtle.onkeyrelease (fun, key)


     參數:

        * ‘fun’ - a function with no arguments or ‘None’

        * ‘key’ - a string: key (e.g.  "a") or key-symbol (e.g.
          "space")

     Bind 'fun' to key-release event of key.  If 'fun' is ‘None’, event
     bindings are removed.  Remark: in order to be able to register
     key-events, TurtleScreen must have the focus.  (See method *note
     listen(): 3be7.)

          >>> def f():
          ...     fd(50)
          ...     lt(60)
          ...
          >>> screen.onkey(f, "Up")
          >>> screen.listen()

 -- 函式: turtle.onkeypress (fun, key=None)


     參數:

        * ‘fun’ - a function with no arguments or ‘None’

        * ‘key’ - a string: key (e.g.  "a") or key-symbol (e.g.
          "space")

     Bind 'fun' to key-press event of key if key is given, or to any
     key-press-event if no key is given.  Remark: in order to be able to
     register key-events, TurtleScreen must have focus.  (See method
     *note listen(): 3be7.)

          >>> def f():
          ...     fd(50)
          ...
          >>> screen.onkey(f, "Up")
          >>> screen.listen()

 -- 函式: turtle.onclick (fun, btn=1, add=None)
 -- 函式: turtle.onscreenclick (fun, btn=1, add=None)


     參數:

        * ‘fun’ - a function with two arguments which will be called
          with the coordinates of the clicked point on the canvas

        * ‘btn’ - number of the mouse-button, defaults to 1 (left mouse
          button)

        * ‘add’ - ‘True’ or ‘False’ - if ‘True’, a new binding will be
          added, otherwise it will replace a former binding

     Bind 'fun' to mouse-click events on this screen.  If 'fun' is
     ‘None’, existing bindings are removed.

     Example for a TurtleScreen instance named ‘screen’ and a Turtle
     instance named ‘turtle’:

          >>> screen.onclick(turtle.goto) # Subsequently clicking into the TurtleScreen will
          >>>                             # make the turtle move to the clicked point.
          >>> screen.onclick(None)        # remove event binding again

          備註: This TurtleScreen method is available as a global
          function only under the name ‘onscreenclick’.  The global
          function ‘onclick’ is another one derived from the Turtle
          method ‘onclick’.

 -- 函式: turtle.ontimer (fun, t=0)


     參數:

        * ‘fun’ - a function with no arguments

        * ‘t’ - a number >= 0

     Install a timer that calls 'fun' after 't' milliseconds.

          >>> running = True
          >>> def f():
          ...     if running:
          ...         fd(50)
          ...         lt(60)
          ...         screen.ontimer(f, 250)
          >>> f()   ### makes the turtle march around
          >>> running = False

 -- 函式: turtle.mainloop ()
 -- 函式: turtle.done ()

     Starts event loop - calling Tkinter's mainloop function.  Must be
     the last statement in a turtle graphics program.  Must 'not' be
     used if a script is run from within IDLE in -n mode (No subprocess)
     - for interactive use of turtle graphics.

          >>> screen.mainloop()


File: python.info,  Node: Input methods,  Next: Settings and special methods,  Prev: Using screen events,  Up: Methods of TurtleScreen/Screen and corresponding functions

5.24.1.36 Input methods
.......................

 -- 函式: turtle.textinput (title, prompt)


     參數:

        * ‘title’ - string（字串）

        * ‘prompt’ - string（字串）

     Pop up a dialog window for input of a string.  Parameter title is
     the title of the dialog window, prompt is a text mostly describing
     what information to input.  Return the string input.  If the dialog
     is canceled, return ‘None’.

          >>> screen.textinput("NIM", "Name of first player:")

 -- 函式: turtle.numinput (title, prompt, default=None, minval=None,
          maxval=None)


     參數:

        * ‘title’ - string（字串）

        * ‘prompt’ - string（字串）

        * ‘default’ - number (optional)

        * ‘minval’ - number (optional)

        * ‘maxval’ - number (optional)

     Pop up a dialog window for input of a number.  title is the title
     of the dialog window, prompt is a text mostly describing what
     numerical information to input.  default: default value, minval:
     minimum value for input, maxval: maximum value for input.  The
     number input must be in the range minval ..  maxval if these are
     given.  If not, a hint is issued and the dialog remains open for
     correction.  Return the number input.  If the dialog is canceled,
     return ‘None’.

          >>> screen.numinput("Poker", "Your stakes:", 1000, minval=10, maxval=10000)


File: python.info,  Node: Settings and special methods,  Next: Methods specific to Screen not inherited from TurtleScreen,  Prev: Input methods,  Up: Methods of TurtleScreen/Screen and corresponding functions

5.24.1.37 Settings and special methods
......................................

 -- 函式: turtle.mode (mode=None)


     參數: ‘mode’ - one of the strings "standard", "logo" or "world"

     Set turtle mode ("standard", "logo" or "world") and perform reset.
     If mode is not given, current mode is returned.

     Mode "standard" is compatible with old *note turtle: ea.  Mode
     "logo" is compatible with most Logo turtle graphics.  Mode "world"
     uses user-defined "world coordinates".  'Attention': in this mode
     angles appear distorted if ‘x/y’ unit-ratio doesn't equal 1.

     Mode             Initial turtle heading        positive angles
                                                    
     -----------------------------------------------------------------------
                                                    
     "standard"       to the right (east)           counterclockwise
                                                    
                                                    
     "logo"           upward (north)                clockwise
                                                    

          >>> mode("logo")   # resets turtle heading to north
          >>> mode()
          'logo'

 -- 函式: turtle.colormode (cmode=None)


     參數: ‘cmode’ - one of the values 1.0 or 255

     Return the colormode or set it to 1.0 or 255.  Subsequently 'r',
     'g', 'b' values of color triples have to be in the range
     0..*cmode*.

          >>> screen.colormode(1)
          >>> turtle.pencolor(240, 160, 80)
          Traceback (most recent call last):
               ...
          TurtleGraphicsError: bad color sequence: (240, 160, 80)
          >>> screen.colormode()
          1.0
          >>> screen.colormode(255)
          >>> screen.colormode()
          255
          >>> turtle.pencolor(240,160,80)

 -- 函式: turtle.getcanvas ()

     Return the Canvas of this TurtleScreen.  Useful for insiders who
     know what to do with a Tkinter Canvas.

          >>> cv = screen.getcanvas()
          >>> cv
          <turtle.ScrolledCanvas object ...>

 -- 函式: turtle.getshapes ()

     Return a list of names of all currently available turtle shapes.

          >>> screen.getshapes()
          ['arrow', 'blank', 'circle', ..., 'turtle']

 -- 函式: turtle.register_shape (name, shape=None)
 -- 函式: turtle.addshape (name, shape=None)

     There are three different ways to call this function:

       1. 'name' is the name of a gif-file and 'shape' is ‘None’:
          Install the corresponding image shape.

               >>> screen.register_shape("turtle.gif")

               備註: Image shapes 'do not' rotate when turning the
               turtle, so they do not display the heading of the turtle!

       2. 'name' is an arbitrary string and 'shape' is a tuple of pairs
          of coordinates: Install the corresponding polygon shape.

               >>> screen.register_shape("triangle", ((5,-3), (0,5), (-5,-3)))

       3. 'name' is an arbitrary string and 'shape' is a (compound)
          *note Shape: 3c0e. object: Install the corresponding compound
          shape.

     Add a turtle shape to TurtleScreen's shapelist.  Only thusly
     registered shapes can be used by issuing the command
     ‘shape(shapename)’.

 -- 函式: turtle.turtles ()

     Return the list of turtles on the screen.

          >>> for turtle in screen.turtles():
          ...     turtle.color("red")

 -- 函式: turtle.window_height ()

     Return the height of the turtle window.

          >>> screen.window_height()
          480

 -- 函式: turtle.window_width ()

     Return the width of the turtle window.

          >>> screen.window_width()
          640


File: python.info,  Node: Methods specific to Screen not inherited from TurtleScreen,  Prev: Settings and special methods,  Up: Methods of TurtleScreen/Screen and corresponding functions

5.24.1.38 Methods specific to Screen, not inherited from TurtleScreen
.....................................................................

 -- 函式: turtle.bye ()

     Shut the turtlegraphics window.

 -- 函式: turtle.exitonclick ()

     Bind ‘bye()’ method to mouse clicks on the Screen.

     If the value "using_IDLE" in the configuration dictionary is
     ‘False’ (default value), also enter mainloop.  Remark: If IDLE with
     the ‘-n’ switch (no subprocess) is used, this value should be set
     to ‘True’ in ‘turtle.cfg’.  In this case IDLE's own mainloop is
     active also for the client script.

 -- 函式: turtle.setup (width=_CFG['width'], height=_CFG['height'],
          startx=_CFG['leftright'], starty=_CFG['topbottom'])

     Set the size and position of the main window.  Default values of
     arguments are stored in the configuration dictionary and can be
     changed via a ‘turtle.cfg’ file.


     參數:

        * ‘width’ - if an integer, a size in pixels, if a float, a
          fraction of the screen; default is 50% of screen

        * ‘height’ - if an integer, the height in pixels, if a float, a
          fraction of the screen; default is 75% of screen

        * ‘startx’ - if positive, starting position in pixels from the
          left edge of the screen, if negative from the right edge, if
          ‘None’, center window horizontally

        * ‘starty’ - if positive, starting position in pixels from the
          top edge of the screen, if negative from the bottom edge, if
          ‘None’, center window vertically

          >>> screen.setup (width=200, height=200, startx=0, starty=0)
          >>>              # sets window to 200x200 pixels, in upper left of screen
          >>> screen.setup(width=.75, height=0.5, startx=None, starty=None)
          >>>              # sets window to 75% of screen by 50% of screen and centers

 -- 函式: turtle.title (titlestring)


     參數: ‘titlestring’ - a string that is shown in the titlebar of the
     turtle graphics window

     Set title of turtle window to 'titlestring'.

          >>> screen.title("Welcome to the turtle zoo!")


File: python.info,  Node: Public classes,  Next: 解釋<2>,  Prev: Methods of TurtleScreen/Screen and corresponding functions,  Up: turtle --- 龜圖學 Turtle graphics

5.24.1.39 Public classes
........................

 -- 類別: turtle.RawTurtle (canvas)
 -- 類別: turtle.RawPen (canvas)


     參數: ‘canvas’ - a ‘tkinter.Canvas’, a *note ScrolledCanvas: 3c1b.
     or a *note TurtleScreen: 3c0b.

     Create a turtle.  The turtle has all methods described above as
     "methods of Turtle/RawTurtle".

 -- 類別: turtle.Turtle

     Subclass of RawTurtle, has the same interface but draws on a
     default *note Screen: 3b8e. object created automatically when
     needed for the first time.

 -- 類別: turtle.TurtleScreen (cv)


     參數: ‘cv’ - a ‘tkinter.Canvas’

     Provides screen oriented methods like *note bgcolor(): 3bde. etc.
     that are described above.

 -- 類別: turtle.Screen

     Subclass of TurtleScreen, with *note four methods added: 3c17.

 -- 類別: turtle.ScrolledCanvas (master)


     參數: ‘master’ - some Tkinter widget to contain the ScrolledCanvas,
     i.e.  a Tkinter-canvas with scrollbars added

     Used by class Screen, which thus automatically provides a
     ScrolledCanvas as playground for the turtles.

 -- 類別: turtle.Shape (type_, data)


     參數: ‘type_’ - one of the strings "polygon", "image", "compound"

     Data structure modeling shapes.  The pair ‘(type_, data)’ must
     follow this specification:

     'type_'         'data'
                     
     -------------------------------------------------------------------------------
                     
     "polygon"       a polygon-tuple, i.e.  a tuple of pairs of coordinates
                     
                     
     "image"         an image (in this form only used internally!)
                     
                     
     "compound"      ‘None’ (a compound shape has to be constructed using the
                     *note addcomponent(): 3c0f. method)
                     

      -- 方法: addcomponent (poly, fill, outline=None)


          參數:

             * ‘poly’ - a polygon, i.e.  a tuple of pairs of numbers

             * ‘fill’ - a color the 'poly' will be filled with

             * ‘outline’ - a color for the poly's outline (if given)

          例如：

               >>> poly = ((0,0),(10,-5),(0,10),(-10,-5))
               >>> s = Shape("compound")
               >>> s.addcomponent(poly, "red", "blue")
               >>> # ... add more components and then use register_shape()

          請見*note Compound shapes: 3c0d.。

 -- 類別: turtle.Vec2D (x, y)

     A two-dimensional vector class, used as a helper class for
     implementing turtle graphics.  May be useful for turtle graphics
     programs too.  Derived from tuple, so a vector is a tuple!

     Provides (for 'a', 'b' vectors, 'k' number):

        * ‘a + b’ 向量加法

        * ‘a - b’ 向量減法

        * ‘a * b’ 內積

        * ‘k * a’ and ‘a * k’ multiplication with scalar

        * ‘abs(a)’ a 的絕對值

        * ‘a.rotate(angle)’ 旋轉


File: python.info,  Node: 解釋<2>,  Next: Help and configuration,  Prev: Public classes,  Up: turtle --- 龜圖學 Turtle graphics

5.24.1.40 解釋
..............

A turtle object draws on a screen object, and there a number of key
classes in the turtle object-oriented interface that can be used to
create them and relate them to each other.

A *note Turtle: 3c1c. instance will automatically create a *note Screen:
3b8e. instance if one is not already present.

‘Turtle’ is a subclass of *note RawTurtle: 3c19, which 'doesn't'
automatically create a drawing surface - a 'canvas' will need to be
provided or created for it.  The 'canvas' can be a ‘tkinter.Canvas’,
*note ScrolledCanvas: 3c1b. or *note TurtleScreen: 3c0b.

*note TurtleScreen: 3c0b. is the basic drawing surface for a turtle.
*note Screen: 3b8e. is a subclass of ‘TurtleScreen’, and includes *note
some additional methods: 3c17. for managing its appearance (including
size and title) and behaviour.  ‘TurtleScreen’'s constructor needs a
‘tkinter.Canvas’ or a *note ScrolledCanvas: 3c1b. as an argument.

The functional interface for turtle graphics uses the various methods of
‘Turtle’ and ‘TurtleScreen’/‘Screen’.  Behind the scenes, a screen
object is automatically created whenever a function derived from a
‘Screen’ method is called.  Similarly, a turtle object is automatically
created whenever any of the functions derived from a Turtle method is
called.

To use multiple turtles on a screen, the object-oriented interface must
be used.


File: python.info,  Node: Help and configuration,  Next: turtledemo --- Demo scripts,  Prev: 解釋<2>,  Up: turtle --- 龜圖學 Turtle graphics

5.24.1.41 Help and configuration
................................

* Menu:

* How to use help::
* Translation of docstrings into different languages::
* How to configure Screen and Turtles::


File: python.info,  Node: How to use help,  Next: Translation of docstrings into different languages,  Up: Help and configuration

5.24.1.42 How to use help
.........................

The public methods of the Screen and Turtle classes are documented
extensively via docstrings.  So these can be used as online-help via the
Python help facilities:

   - When using IDLE, tooltips show the signatures and first lines of
     the docstrings of typed in function-/method calls.

   - Calling *note help(): 87c. on methods or functions displays the
     docstrings:

          >>> help(Screen.bgcolor)
          Help on method bgcolor in module turtle:

          bgcolor(self, *args) unbound turtle.Screen method
              Set or return backgroundcolor of the TurtleScreen.

              Arguments (if given): a color string or three numbers
              in the range 0..colormode or a 3-tuple of such numbers.


              >>> screen.bgcolor("orange")
              >>> screen.bgcolor()
              "orange"
              >>> screen.bgcolor(0.5,0,0.5)
              >>> screen.bgcolor()
              "#800080"

          >>> help(Turtle.penup)
          Help on method penup in module turtle:

          penup(self) unbound turtle.Turtle method
              Pull the pen up -- no drawing when moving.

              Aliases: penup | pu | up

              No argument

              >>> turtle.penup()

   - The docstrings of the functions which are derived from methods have
     a modified form:

          >>> help(bgcolor)
          Help on function bgcolor in module turtle:

          bgcolor(*args)
              Set or return backgroundcolor of the TurtleScreen.

              Arguments (if given): a color string or three numbers
              in the range 0..colormode or a 3-tuple of such numbers.

              Example::

                >>> bgcolor("orange")
                >>> bgcolor()
                "orange"
                >>> bgcolor(0.5,0,0.5)
                >>> bgcolor()
                "#800080"

          >>> help(penup)
          Help on function penup in module turtle:

          penup()
              Pull the pen up -- no drawing when moving.

              Aliases: penup | pu | up

              No argument

              Example:
              >>> penup()

These modified docstrings are created automatically together with the
function definitions that are derived from the methods at import time.


File: python.info,  Node: Translation of docstrings into different languages,  Next: How to configure Screen and Turtles,  Prev: How to use help,  Up: Help and configuration

5.24.1.43 Translation of docstrings into different languages
............................................................

There is a utility to create a dictionary the keys of which are the
method names and the values of which are the docstrings of the public
methods of the classes Screen and Turtle.

 -- 函式: turtle.write_docstringdict (filename='turtle_docstringdict')


     參數: ‘filename’ - a string, used as filename

     Create and write docstring-dictionary to a Python script with the
     given filename.  This function has to be called explicitly (it is
     not used by the turtle graphics classes).  The docstring dictionary
     will be written to the Python script ‘`filename'.py’.  It is
     intended to serve as a template for translation of the docstrings
     into different languages.

If you (or your students) want to use *note turtle: ea. with online help
in your native language, you have to translate the docstrings and save
the resulting file as e.g.  ‘turtle_docstringdict_german.py’.

If you have an appropriate entry in your ‘turtle.cfg’ file this
dictionary will be read in at import time and will replace the original
English docstrings.

At the time of this writing there are docstring dictionaries in German
and in Italian.  (Requests please to <glingl@aon.at>.)


File: python.info,  Node: How to configure Screen and Turtles,  Prev: Translation of docstrings into different languages,  Up: Help and configuration

5.24.1.44 How to configure Screen and Turtles
.............................................

The built-in default configuration mimics the appearance and behaviour
of the old turtle module in order to retain best possible compatibility
with it.

If you want to use a different configuration which better reflects the
features of this module or which better fits to your needs, e.g.  for
use in a classroom, you can prepare a configuration file ‘turtle.cfg’
which will be read at import time and modify the configuration according
to its settings.

The built in configuration would correspond to the following
‘turtle.cfg’:

     width = 0.5
     height = 0.75
     leftright = None
     topbottom = None
     canvwidth = 400
     canvheight = 300
     mode = standard
     colormode = 1.0
     delay = 10
     undobuffersize = 1000
     shape = classic
     pencolor = black
     fillcolor = black
     resizemode = noresize
     visible = True
     language = english
     exampleturtle = turtle
     examplescreen = screen
     title = Python Turtle Graphics
     using_IDLE = False

Short explanation of selected entries:

   - The first four lines correspond to the arguments of the *note
     Screen.setup: 3bfa. method.

   - Line 5 and 6 correspond to the arguments of the method *note
     Screen.screensize: 3be2.

   - 'shape' can be any of the built-in shapes, e.g: arrow, turtle, etc.
     For more info try ‘help(shape)’.

   - If you want to use no fill color (i.e.  make the turtle
     transparent), you have to write ‘fillcolor = ""’ (but all nonempty
     strings must not have quotes in the cfg file).

   - If you want to reflect the turtle its state, you have to use
     ‘resizemode = auto’.

   - If you set e.g.  ‘language = italian’ the docstringdict
     ‘turtle_docstringdict_italian.py’ will be loaded at import time (if
     present on the import path, e.g.  in the same directory as *note
     turtle: ea.).

   - The entries 'exampleturtle' and 'examplescreen' define the names of
     these objects as they occur in the docstrings.  The transformation
     of method-docstrings to function-docstrings will delete these names
     from the docstrings.

   - 'using_IDLE': Set this to ‘True’ if you regularly work with IDLE
     and its ‘-n’ switch ("no subprocess").  This will prevent *note
     exitonclick(): 3bf9. to enter the mainloop.

There can be a ‘turtle.cfg’ file in the directory where *note turtle:
ea. is stored and an additional one in the current working directory.
The latter will override the settings of the first one.

The ‘Lib/turtledemo’ directory contains a ‘turtle.cfg’ file.  You can
study it as an example and see its effects when running the demos
(preferably not from within the demo-viewer).


File: python.info,  Node: turtledemo --- Demo scripts,  Next: Changes since Python 2 6,  Prev: Help and configuration,  Up: turtle --- 龜圖學 Turtle graphics

5.24.1.45 ‘turtledemo’ -- Demo scripts
......................................

The *note turtledemo: eb. package includes a set of demo scripts.  These
scripts can be run and viewed using the supplied demo viewer as follows:

     python -m turtledemo

Alternatively, you can run the demo scripts individually.  For example,

     python -m turtledemo.bytedesign

The *note turtledemo: eb. package directory contains:

   - A demo viewer ‘__main__.py’ which can be used to view the
     sourcecode of the scripts and run them at the same time.

   - Multiple scripts demonstrating different features of the *note
     turtle: ea. module.  Examples can be accessed via the Examples
     menu.  They can also be run standalone.

   - A ‘turtle.cfg’ file which serves as an example of how to write and
     use such files.

The demo scripts are:

Name                 描述                               Features
                                                        
------------------------------------------------------------------------------------
                                                        
bytedesign           complex classical turtle           *note tracer(): 3be5,
                     graphics pattern                   delay,
                                                        *note update(): 3be6.
                                                        
                                                        
chaos                graphs Verhulst dynamics, shows    world coordinates
                     that computer's computations can   
                     generate results sometimes
                     against the common sense
                     expectations
                     
                                                        
clock                analog clock showing time of       turtles as clock's hands,
                     your computer                      ontimer
                                                        
                                                        
colormixer           experiment with r, g, b            *note ondrag(): 3bd3.
                                                        
                                                        
forest               3 breadth-first trees              randomization
                                                        
                                                        
fractalcurves        Hilbert & Koch curves              recursion
                                                        
                                                        
lindenmayer          ethnomathematics (indian kolams)   L-System
                                                        
                                                        
minimal_hanoi        Towers of Hanoi                    Rectangular Turtles as
                                                        Hanoi discs (shape,
                                                        shapesize)
                                                        
                                                        
nim                  play the classical nim game with   turtles as nimsticks,
                     three heaps of sticks against      event driven (mouse,
                     the computer.                      keyboard)
                                                        
                                                        
paint                super minimalistic drawing         *note onclick(): 3bd1.
                     program                            
                     
                                                        
peace                elementary                         turtle: appearance and
                                                        animation
                                                        
                                                        
penrose              aperiodic tiling with kites and    *note stamp(): 3ba3.
                     darts                              
                     
                                                        
planet_and_moon      simulation of gravitational        compound shapes,
                     system                             *note Vec2D: 3bfe.
                                                        
                                                        
rosette              a pattern from the wikipedia       *note clone(): 3bd7,
                     article on turtle graphics         *note undo(): 3ba6.
                                                        
                                                        
round_dance          dancing turtles rotating           compound shapes, clone
                     pairwise in opposite direction     shapesize, tilt,
                                                        get_shapepoly, update
                                                        
                                                        
sorting_animate      visual demonstration of            simple alignment,
                     different sorting methods          randomization
                                                        
                                                        
tree                 a (graphical) breadth first tree   *note clone(): 3bd7.
                     (using generators)                 
                     
                                                        
two_canvases         simple design                      turtles on two canvases
                                                        
                                                        
yinyang              another elementary example         *note circle(): 3ba1.
                                                        

Have fun!


File: python.info,  Node: Changes since Python 2 6,  Next: Changes since Python 3 0,  Prev: turtledemo --- Demo scripts,  Up: turtle --- 龜圖學 Turtle graphics

5.24.1.46 Changes since Python 2.6
..................................

   - The methods *note Turtle.tracer: 3be5, *note Turtle.window_width:
     3bf7. and *note Turtle.window_height: 3bf6. have been eliminated.
     Methods with these names and functionality are now available only
     as methods of *note Screen: 3b8e.  The functions derived from these
     remain available.  (In fact already in Python 2.6 these methods
     were merely duplications of the corresponding *note TurtleScreen:
     3c0b./*note Screen: 3b8e. methods.)

   - The method ‘Turtle.fill()’ has been eliminated.  The behaviour of
     *note begin_fill(): 3bbf. and *note end_fill(): 3bc0. have changed
     slightly: now every filling process must be completed with an
     ‘end_fill()’ call.

   - A method *note Turtle.filling: 3bbe. has been added.  It returns a
     boolean value: ‘True’ if a filling process is under way, ‘False’
     otherwise.  This behaviour corresponds to a ‘fill()’ call without
     arguments in Python 2.6.


File: python.info,  Node: Changes since Python 3 0,  Prev: Changes since Python 2 6,  Up: turtle --- 龜圖學 Turtle graphics

5.24.1.47 Changes since Python 3.0
..................................

   - The *note Turtle: 3c1c. methods *note shearfactor(): 3bcd, *note
     shapetransform(): 3bcf. and *note get_shapepoly(): 3bd0. have been
     added.  Thus the full range of regular linear transforms is now
     available for transforming turtle shapes.  *note tiltangle(): 6c9.
     has been enhanced in functionality: it now can be used to get or
     set the tilt angle.

   - The *note Screen: 3b8e. method *note onkeypress(): 3bea. has been
     added as a complement to *note onkey(): 3be8.  As the latter binds
     actions to the key release event, an alias: *note onkeyrelease():
     3be9. was also added for it.

   - The method *note Screen.mainloop: 3bed. has been added, so there is
     no longer a need to use the standalone *note mainloop(): 3bed.
     function when working with *note Screen: 3b8e. and *note Turtle:
     3c1c. objects.

   - Two input methods have been added: *note Screen.textinput: 17c5.
     and *note Screen.numinput: 17c6.  These pop up input dialogs and
     return strings and numbers respectively.

   - Two example scripts ‘tdemo_nim.py’ and ‘tdemo_round_dance.py’ have
     been added to the ‘Lib/turtledemo’ directory.


File: python.info,  Node: cmd --- 以列為導向的指令直譯器支援,  Next: shlex --- 簡單的語法分析,  Prev: turtle --- 龜圖學 Turtle graphics,  Up: 程式框架

5.24.2 ‘cmd’ -- 以列為導向的指令直譯器支援
------------------------------------------

'原始碼：'Lib/cmd.py(1)

__________________________________________________________________

The *note Cmd: 15c0. class provides a simple framework for writing
line-oriented command interpreters.  These are often useful for test
harnesses, administrative tools, and prototypes that will later be
wrapped in a more sophisticated interface.

 -- 類別: cmd.Cmd (completekey='tab', stdin=None, stdout=None)

     A *note Cmd: 15c0. instance or subclass instance is a line-oriented
     interpreter framework.  There is no good reason to instantiate
     *note Cmd: 15c0. itself; rather, it's useful as a superclass of an
     interpreter class you define yourself in order to inherit *note
     Cmd: 15c0.'s methods and encapsulate action methods.

     The optional argument 'completekey' is the *note readline: a8. name
     of a completion key; it defaults to ‘Tab’.  If 'completekey' is not
     *note None: 61b. and *note readline: a8. is available, command
     completion is done automatically.

     The default, ‘'tab'’, is treated specially, so that it refers to
     the ‘Tab’ key on every *note readline.backend: 15a7.  Specifically,
     if *note readline.backend: 15a7. is ‘editline’, ‘Cmd’ will use
     ‘'^I'’ instead of ‘'tab'’.  Note that other values are not treated
     this way, and might only work with a specific backend.

     The optional arguments 'stdin' and 'stdout' specify the input and
     output file objects that the Cmd instance or subclass instance will
     use for input and output.  If not specified, they will default to
     *note sys.stdin: 4e2. and *note sys.stdout: a79.

     If you want a given 'stdin' to be used, make sure to set the
     instance's *note use_rawinput: 3c28. attribute to ‘False’,
     otherwise 'stdin' will be ignored.

     在 3.13 版的變更: ‘completekey='tab'’ is replaced by ‘'^I'’ for
     ‘editline’.

* Menu:

* Cmd 物件::
* Cmd Example::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/cmd.py


File: python.info,  Node: Cmd 物件,  Next: Cmd Example,  Up: cmd --- 以列為導向的指令直譯器支援

5.24.2.1 Cmd 物件
.................

A *note Cmd: 15c0. instance has the following methods:

 -- 方法: Cmd.cmdloop (intro=None)

     Repeatedly issue a prompt, accept input, parse an initial prefix
     off the received input, and dispatch to action methods, passing
     them the remainder of the line as argument.

     The optional argument is a banner or intro string to be issued
     before the first prompt (this overrides the *note intro: 3c2c.
     class attribute).

     If the *note readline: a8. module is loaded, input will
     automatically inherit ‘bash’-like history-list editing (e.g.
     ‘Control-P’ scrolls back to the last command, ‘Control-N’ forward
     to the next one, ‘Control-F’ moves the cursor to the right
     non-destructively, ‘Control-B’ moves the cursor to the left
     non-destructively, etc.).

     An end-of-file on input is passed back as the string ‘'EOF'’.

     An interpreter instance will recognize a command name ‘foo’ if and
     only if it has a method ‘do_foo()’.  As a special case, a line
     beginning with the character ‘'?'’ is dispatched to the method
     *note do_help(): 15ac.  As another special case, a line beginning
     with the character ‘'!'’ is dispatched to the method ‘do_shell()’
     (if such a method is defined).

     This method will return when the *note postcmd(): 3c2d. method
     returns a true value.  The 'stop' argument to *note postcmd():
     3c2d. is the return value from the command's corresponding ‘do_*()’
     method.

     If completion is enabled, completing commands will be done
     automatically, and completing of commands args is done by calling
     ‘complete_foo()’ with arguments 'text', 'line', 'begidx', and
     'endidx'.  'text' is the string prefix we are attempting to match:
     all returned matches must begin with it.  'line' is the current
     input line with leading whitespace removed, 'begidx' and 'endidx'
     are the beginning and ending indexes of the prefix text, which
     could be used to provide different completion depending upon which
     position the argument is in.

 -- 方法: Cmd.do_help (arg)

     All subclasses of *note Cmd: 15c0. inherit a predefined
     ‘do_help()’.  This method, called with an argument ‘'bar'’, invokes
     the corresponding method ‘help_bar()’, and if that is not present,
     prints the docstring of ‘do_bar()’, if available.  With no
     argument, ‘do_help()’ lists all available help topics (that is, all
     commands with corresponding ‘help_*()’ methods or commands that
     have docstrings), and also lists any undocumented commands.

 -- 方法: Cmd.onecmd (str)

     Interpret the argument as though it had been typed in response to
     the prompt.  This may be overridden, but should not normally need
     to be; see the *note precmd(): 3c2f. and *note postcmd(): 3c2d.
     methods for useful execution hooks.  The return value is a flag
     indicating whether interpretation of commands by the interpreter
     should stop.  If there is a ‘do_*()’ method for the command 'str',
     the return value of that method is returned, otherwise the return
     value from the *note default(): 3c30. method is returned.

 -- 方法: Cmd.emptyline ()

     Method called when an empty line is entered in response to the
     prompt.  If this method is not overridden, it repeats the last
     nonempty command entered.

 -- 方法: Cmd.default (line)

     Method called on an input line when the command prefix is not
     recognized.  If this method is not overridden, it prints an error
     message and returns.

 -- 方法: Cmd.completedefault (text, line, begidx, endidx)

     Method called to complete an input line when no command-specific
     ‘complete_*()’ method is available.  By default, it returns an
     empty list.

 -- 方法: Cmd.columnize (list, displaywidth=80)

     Method called to display a list of strings as a compact set of
     columns.  Each column is only as wide as necessary.  Columns are
     separated by two spaces for readability.

 -- 方法: Cmd.precmd (line)

     Hook method executed just before the command line 'line' is
     interpreted, but after the input prompt is generated and issued.
     This method is a stub in *note Cmd: 15c0.; it exists to be
     overridden by subclasses.  The return value is used as the command
     which will be executed by the *note onecmd(): 3c2e. method; the
     *note precmd(): 3c2f. implementation may re-write the command or
     simply return 'line' unchanged.

 -- 方法: Cmd.postcmd (stop, line)

     Hook method executed just after a command dispatch is finished.
     This method is a stub in *note Cmd: 15c0.; it exists to be
     overridden by subclasses.  'line' is the command line which was
     executed, and 'stop' is a flag which indicates whether execution
     will be terminated after the call to *note postcmd(): 3c2d.; this
     will be the return value of the *note onecmd(): 3c2e. method.  The
     return value of this method will be used as the new value for the
     internal flag which corresponds to 'stop'; returning false will
     cause interpretation to continue.

 -- 方法: Cmd.preloop ()

     Hook method executed once when *note cmdloop(): 3c2b. is called.
     This method is a stub in *note Cmd: 15c0.; it exists to be
     overridden by subclasses.

 -- 方法: Cmd.postloop ()

     Hook method executed once when *note cmdloop(): 3c2b. is about to
     return.  This method is a stub in *note Cmd: 15c0.; it exists to be
     overridden by subclasses.

Instances of *note Cmd: 15c0. subclasses have some public instance
variables:

 -- 屬性: Cmd.prompt

     The prompt issued to solicit input.

 -- 屬性: Cmd.identchars

     The string of characters accepted for the command prefix.

 -- 屬性: Cmd.lastcmd

     The last nonempty command prefix seen.

 -- 屬性: Cmd.cmdqueue

     A list of queued input lines.  The cmdqueue list is checked in
     *note cmdloop(): 3c2b. when new input is needed; if it is nonempty,
     its elements will be processed in order, as if entered at the
     prompt.

 -- 屬性: Cmd.intro

     A string to issue as an intro or banner.  May be overridden by
     giving the *note cmdloop(): 3c2b. method an argument.

 -- 屬性: Cmd.doc_header

     The header to issue if the help output has a section for documented
     commands.

 -- 屬性: Cmd.misc_header

     The header to issue if the help output has a section for
     miscellaneous help topics (that is, there are ‘help_*()’ methods
     without corresponding ‘do_*()’ methods).

 -- 屬性: Cmd.undoc_header

     The header to issue if the help output has a section for
     undocumented commands (that is, there are ‘do_*()’ methods without
     corresponding ‘help_*()’ methods).

 -- 屬性: Cmd.ruler

     The character used to draw separator lines under the help-message
     headers.  If empty, no ruler line is drawn.  It defaults to ‘'='’.

 -- 屬性: Cmd.use_rawinput

     A flag, defaulting to true.  If true, *note cmdloop(): 3c2b. uses
     *note input(): 126b. to display a prompt and read the next command;
     if false, *note sys.stdout.write(): a79. and *note
     sys.stdin.readline(): 4e2. are used.  (This means that by importing
     *note readline: a8, on systems that support it, the interpreter
     will automatically support ‘Emacs’-like line editing and
     command-history keystrokes.)


File: python.info,  Node: Cmd Example,  Prev: Cmd 物件,  Up: cmd --- 以列為導向的指令直譯器支援

5.24.2.2 Cmd Example
....................

The *note cmd: 12. module is mainly useful for building custom shells
that let a user work with a program interactively.

This section presents a simple example of how to build a shell around a
few of the commands in the *note turtle: ea. module.

Basic turtle commands such as *note forward(): 3b88. are added to a
*note Cmd: 15c0. subclass with method named ‘do_forward()’.  The
argument is converted to a number and dispatched to the turtle module.
The docstring is used in the help utility provided by the shell.

The example also includes a basic record and playback facility
implemented with the *note precmd(): 3c2f. method which is responsible
for converting the input to lowercase and writing the commands to a
file.  The ‘do_playback()’ method reads the file and adds the recorded
commands to the *note cmdqueue: 3c38. for immediate playback:

     import cmd, sys
     from turtle import *

     class TurtleShell(cmd.Cmd):
         intro = 'Welcome to the turtle shell.   Type help or ? to list commands.\n'
         prompt = '(turtle) '
         file = None

         # ----- basic turtle commands -----
         def do_forward(self, arg):
             'Move the turtle forward by the specified distance:  FORWARD 10'
             forward(*parse(arg))
         def do_right(self, arg):
             'Turn turtle right by given number of degrees:  RIGHT 20'
             right(*parse(arg))
         def do_left(self, arg):
             'Turn turtle left by given number of degrees:  LEFT 90'
             left(*parse(arg))
         def do_goto(self, arg):
             'Move turtle to an absolute position with changing orientation.  GOTO 100 200'
             goto(*parse(arg))
         def do_home(self, arg):
             'Return turtle to the home position:  HOME'
             home()
         def do_circle(self, arg):
             'Draw circle with given radius an options extent and steps:  CIRCLE 50'
             circle(*parse(arg))
         def do_position(self, arg):
             'Print the current turtle position:  POSITION'
             print('Current position is %d %d\n' % position())
         def do_heading(self, arg):
             'Print the current turtle heading in degrees:  HEADING'
             print('Current heading is %d\n' % (heading(),))
         def do_color(self, arg):
             'Set the color:  COLOR BLUE'
             color(arg.lower())
         def do_undo(self, arg):
             'Undo (repeatedly) the last turtle action(s):  UNDO'
         def do_reset(self, arg):
             'Clear the screen and return turtle to center:  RESET'
             reset()
         def do_bye(self, arg):
             'Stop recording, close the turtle window, and exit:  BYE'
             print('Thank you for using Turtle')
             self.close()
             bye()
             return True

         # ----- record and playback -----
         def do_record(self, arg):
             'Save future commands to filename:  RECORD rose.cmd'
             self.file = open(arg, 'w')
         def do_playback(self, arg):
             'Playback commands from a file:  PLAYBACK rose.cmd'
             self.close()
             with open(arg) as f:
                 self.cmdqueue.extend(f.read().splitlines())
         def precmd(self, line):
             line = line.lower()
             if self.file and 'playback' not in line:
                 print(line, file=self.file)
             return line
         def close(self):
             if self.file:
                 self.file.close()
                 self.file = None

     def parse(arg):
         'Convert a series of zero or more numbers to an argument tuple'
         return tuple(map(int, arg.split()))

     if __name__ == '__main__':
         TurtleShell().cmdloop()

Here is a sample session with the turtle shell showing the help
functions, using blank lines to repeat commands, and the simple record
and playback facility:

     Welcome to the turtle shell.   Type help or ? to list commands.

     (turtle) ?

     Documented commands (type help <topic>):
     ========================================
     bye     color    goto     home  playback  record  right
     circle  forward  heading  left  position  reset   undo

     (turtle) help forward
     Move the turtle forward by the specified distance:  FORWARD 10
     (turtle) record spiral.cmd
     (turtle) position
     Current position is 0 0

     (turtle) heading
     Current heading is 0

     (turtle) reset
     (turtle) circle 20
     (turtle) right 30
     (turtle) circle 40
     (turtle) right 30
     (turtle) circle 60
     (turtle) right 30
     (turtle) circle 80
     (turtle) right 30
     (turtle) circle 100
     (turtle) right 30
     (turtle) circle 120
     (turtle) right 30
     (turtle) circle 120
     (turtle) heading
     Current heading is 180

     (turtle) forward 100
     (turtle)
     (turtle) right 90
     (turtle) forward 100
     (turtle)
     (turtle) right 90
     (turtle) forward 400
     (turtle) right 90
     (turtle) forward 500
     (turtle) right 90
     (turtle) forward 400
     (turtle) right 90
     (turtle) forward 300
     (turtle) playback spiral.cmd
     Current position is 0 0

     Current heading is 0

     Current heading is 180

     (turtle) bye
     Thank you for using Turtle


File: python.info,  Node: shlex --- 簡單的語法分析,  Prev: cmd --- 以列為導向的指令直譯器支援,  Up: 程式框架

5.24.3 ‘shlex’ -- 簡單的語法分析
--------------------------------

'原始碼：'Lib/shlex.py(1)

__________________________________________________________________

The *note shlex: c74. class makes it easy to write lexical analyzers for
simple syntaxes resembling that of the Unix shell.  This will often be
useful for writing minilanguages, (for example, in run control files for
Python applications) or for parsing quoted strings.

The *note shlex: b2. module defines the following functions:

 -- 函式: shlex.split (s, comments=False, posix=True)

     Split the string 's' using shell-like syntax.  If 'comments' is
     *note False: adb. (the default), the parsing of comments in the
     given string will be disabled (setting the *note commenters: 3c41.
     attribute of the *note shlex: c74. instance to the empty string).
     This function operates in POSIX mode by default, but uses non-POSIX
     mode if the 'posix' argument is false.

     在 3.12 版的變更: Passing ‘None’ for 's' argument now raises an
     exception, rather than reading *note sys.stdin: 4e2.

 -- 函式: shlex.join (split_command)

     Concatenate the tokens of the list 'split_command' and return a
     string.  This function is the inverse of *note split(): 4e1.

          >>> from shlex import join
          >>> print(join(['echo', '-n', 'Multiple words']))
          echo -n 'Multiple words'

     The returned value is shell-escaped to protect against injection
     vulnerabilities (see *note quote(): 10c4.).

     在 3.8 版被加入.

 -- 函式: shlex.quote (s)

     Return a shell-escaped version of the string 's'.  The returned
     value is a string that can safely be used as one token in a shell
     command line, for cases where you cannot use a list.
          警告: The ‘shlex’ module is 'only designed for Unix shells'.

          The *note quote(): 10c4. function is not guaranteed to be
          correct on non-POSIX compliant shells or shells from other
          operating systems such as Windows.  Executing commands quoted
          by this module on such shells can open up the possibility of a
          command injection vulnerability.

          Consider using functions that pass command arguments with
          lists such as *note subprocess.run(): b2c. with ‘shell=False’.

     This idiom would be unsafe:

          >>> filename = 'somefile; rm -rf ~'
          >>> command = 'ls -l {}'.format(filename)
          >>> print(command)  # executed by a shell: boom!
          ls -l somefile; rm -rf ~

     *note quote(): 10c4. lets you plug the security hole:

          >>> from shlex import quote
          >>> command = 'ls -l {}'.format(quote(filename))
          >>> print(command)
          ls -l 'somefile; rm -rf ~'
          >>> remote_command = 'ssh home {}'.format(quote(command))
          >>> print(remote_command)
          ssh home 'ls -l '"'"'somefile; rm -rf ~'"'"''

     The quoting is compatible with UNIX shells and with *note split():
     4e1.:

          >>> from shlex import split
          >>> remote_command = split(remote_command)
          >>> remote_command
          ['ssh', 'home', "ls -l 'somefile; rm -rf ~'"]
          >>> command = split(remote_command[-1])
          >>> command
          ['ls', '-l', 'somefile; rm -rf ~']

     在 3.3 版被加入.

The *note shlex: b2. module defines the following class:

 -- 類別: shlex.shlex (instream=None, infile=None, posix=False,
          punctuation_chars=False)

     A *note shlex: c74. instance or subclass instance is a lexical
     analyzer object.  The initialization argument, if present,
     specifies where to read characters from.  It must be a
     file-/stream-like object with *note read(): 1b89. and *note
     readline(): 1bc0. methods, or a string.  If no argument is given,
     input will be taken from ‘sys.stdin’.  The second optional argument
     is a filename string, which sets the initial value of the *note
     infile: 3c42. attribute.  If the 'instream' argument is omitted or
     equal to ‘sys.stdin’, this second argument defaults to "stdin".
     The 'posix' argument defines the operational mode: when 'posix' is
     not true (default), the *note shlex: c74. instance will operate in
     compatibility mode.  When operating in POSIX mode, *note shlex:
     c74. will try to be as close as possible to the POSIX shell parsing
     rules.  The 'punctuation_chars' argument provides a way to make the
     behaviour even closer to how real shells parse.  This can take a
     number of values: the default value, ‘False’, preserves the
     behaviour seen under Python 3.5 and earlier.  If set to ‘True’,
     then parsing of the characters ‘();<>|&’ is changed: any run of
     these characters (considered punctuation characters) is returned as
     a single token.  If set to a non-empty string of characters, those
     characters will be used as the punctuation characters.  Any
     characters in the *note wordchars: 3c43. attribute that appear in
     'punctuation_chars' will be removed from *note wordchars: 3c43.
     See *note Improved Compatibility with Shells: c75. for more
     information.  'punctuation_chars' can be set only upon *note shlex:
     c74. instance creation and can't be modified later.

     在 3.6 版的變更: 新增 'punctuation_chars' 參數。

也參考
......

*note configparser: 1b. 模組

     Parser for configuration files similar to the Windows ‘.ini’ files.

* Menu:

* shlex 物件::
* Parsing Rules::
* Improved Compatibility with Shells::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/shlex.py


File: python.info,  Node: shlex 物件,  Next: Parsing Rules,  Up: shlex --- 簡單的語法分析

5.24.3.1 shlex 物件
...................

A *note shlex: c74. instance has the following methods:

 -- 方法: shlex.get_token ()

     Return a token.  If tokens have been stacked using *note
     push_token(): 3c47, pop a token off the stack.  Otherwise, read one
     from the input stream.  If reading encounters an immediate
     end-of-file, *note eof: 3c48. is returned (the empty string (‘''’)
     in non-POSIX mode, and ‘None’ in POSIX mode).

 -- 方法: shlex.push_token (str)

     Push the argument onto the token stack.

 -- 方法: shlex.read_token ()

     Read a raw token.  Ignore the pushback stack, and do not interpret
     source requests.  (This is not ordinarily a useful entry point, and
     is documented here only for the sake of completeness.)

 -- 方法: shlex.sourcehook (filename)

     When *note shlex: c74. detects a source request (see *note source:
     3c4b. below) this method is given the following token as argument,
     and expected to return a tuple consisting of a filename and an open
     file-like object.

     Normally, this method first strips any quotes off the argument.  If
     the result is an absolute pathname, or there was no previous source
     request in effect, or the previous source was a stream (such as
     ‘sys.stdin’), the result is left alone.  Otherwise, if the result
     is a relative pathname, the directory part of the name of the file
     immediately before it on the source inclusion stack is prepended
     (this behavior is like the way the C preprocessor handles ‘#include
     "file.h"’).

     The result of the manipulations is treated as a filename, and
     returned as the first component of the tuple, with *note open():
     4c0. called on it to yield the second component.  (Note: this is
     the reverse of the order of arguments in instance initialization!)

     This hook is exposed so that you can use it to implement directory
     search paths, addition of file extensions, and other namespace
     hacks.  There is no corresponding 'close' hook, but a shlex
     instance will call the *note close(): 1db. method of the sourced
     input stream when it returns EOF.

     For more explicit control of source stacking, use the *note
     push_source(): 3c4c. and *note pop_source(): 3c4d. methods.

 -- 方法: shlex.push_source (newstream, newfile=None)

     Push an input source stream onto the input stack.  If the filename
     argument is specified it will later be available for use in error
     messages.  This is the same method used internally by the *note
     sourcehook(): 3c4a. method.

 -- 方法: shlex.pop_source ()

     Pop the last-pushed input source from the input stack.  This is the
     same method used internally when the lexer reaches EOF on a stacked
     input stream.

 -- 方法: shlex.error_leader (infile=None, lineno=None)

     This method generates an error message leader in the format of a
     Unix C compiler error label; the format is ‘'"%s", line %d: '’,
     where the ‘%s’ is replaced with the name of the current source file
     and the ‘%d’ with the current input line number (the optional
     arguments can be used to override these).

     This convenience is provided to encourage *note shlex: b2. users to
     generate error messages in the standard, parseable format
     understood by Emacs and other Unix tools.

Instances of *note shlex: c74. subclasses have some public instance
variables which either control lexical analysis or can be used for
debugging:

 -- 屬性: shlex.commenters

     The string of characters that are recognized as comment beginners.
     All characters from the comment beginner to end of line are
     ignored.  Includes just ‘'#'’ by default.

 -- 屬性: shlex.wordchars

     The string of characters that will accumulate into multi-character
     tokens.  By default, includes all ASCII alphanumerics and
     underscore.  In POSIX mode, the accented characters in the Latin-1
     set are also included.  If *note punctuation_chars: 18d6. is not
     empty, the characters ‘~-./*?=’, which can appear in filename
     specifications and command line parameters, will also be included
     in this attribute, and any characters which appear in
     ‘punctuation_chars’ will be removed from ‘wordchars’ if they are
     present there.  If *note whitespace_split: 3c4f. is set to ‘True’,
     this will have no effect.

 -- 屬性: shlex.whitespace

     Characters that will be considered whitespace and skipped.
     Whitespace bounds tokens.  By default, includes space, tab,
     linefeed and carriage-return.

 -- 屬性: shlex.escape

     Characters that will be considered as escape.  This will be only
     used in POSIX mode, and includes just ‘'\'’ by default.

 -- 屬性: shlex.quotes

     Characters that will be considered string quotes.  The token
     accumulates until the same quote is encountered again (thus,
     different quote types protect each other as in the shell.)  By
     default, includes ASCII single and double quotes.

 -- 屬性: shlex.escapedquotes

     Characters in *note quotes: 3c52. that will interpret escape
     characters defined in *note escape: 3c51.  This is only used in
     POSIX mode, and includes just ‘'"'’ by default.

 -- 屬性: shlex.whitespace_split

     If ‘True’, tokens will only be split in whitespaces.  This is
     useful, for example, for parsing command lines with *note shlex:
     c74, getting tokens in a similar way to shell arguments.  When used
     in combination with *note punctuation_chars: 18d6, tokens will be
     split on whitespace in addition to those characters.

     在 3.8 版的變更: The *note punctuation_chars: 18d6. attribute was
     made compatible with the *note whitespace_split: 3c4f. attribute.

 -- 屬性: shlex.infile

     The name of the current input file, as initially set at class
     instantiation time or stacked by later source requests.  It may be
     useful to examine this when constructing error messages.

 -- 屬性: shlex.instream

     The input stream from which this *note shlex: c74. instance is
     reading characters.

 -- 屬性: shlex.source

     This attribute is ‘None’ by default.  If you assign a string to it,
     that string will be recognized as a lexical-level inclusion request
     similar to the ‘source’ keyword in various shells.  That is, the
     immediately following token will be opened as a filename and input
     will be taken from that stream until EOF, at which point the *note
     close(): 1db. method of that stream will be called and the input
     source will again become the original input stream.  Source
     requests may be stacked any number of levels deep.

 -- 屬性: shlex.debug

     If this attribute is numeric and ‘1’ or more, a *note shlex: c74.
     instance will print verbose progress output on its behavior.  If
     you need to use this, you can read the module source code to learn
     the details.

 -- 屬性: shlex.lineno

     Source line number (count of newlines seen so far plus one).

 -- 屬性: shlex.token

     The token buffer.  It may be useful to examine this when catching
     exceptions.

 -- 屬性: shlex.eof

     Token used to determine end of file.  This will be set to the empty
     string (‘''’), in non-POSIX mode, and to ‘None’ in POSIX mode.

 -- 屬性: shlex.punctuation_chars

     A read-only property.  Characters that will be considered
     punctuation.  Runs of punctuation characters will be returned as a
     single token.  However, note that no semantic validity checking
     will be performed: for example, '>>>' could be returned as a token,
     even though it may not be recognised as such by shells.

     在 3.6 版被加入.


File: python.info,  Node: Parsing Rules,  Next: Improved Compatibility with Shells,  Prev: shlex 物件,  Up: shlex --- 簡單的語法分析

5.24.3.2 Parsing Rules
......................

When operating in non-POSIX mode, *note shlex: c74. will try to obey to
the following rules.

   * Quote characters are not recognized within words (‘Do"Not"Separate’
     is parsed as the single word ‘Do"Not"Separate’);

   * Escape characters are not recognized;

   * Enclosing characters in quotes preserve the literal value of all
     characters within the quotes;

   * Closing quotes separate words (‘"Do"Separate’ is parsed as ‘"Do"’
     and ‘Separate’);

   * If *note whitespace_split: 3c4f. is ‘False’, any character not
     declared to be a word character, whitespace, or a quote will be
     returned as a single-character token.  If it is ‘True’, *note
     shlex: c74. will only split words in whitespaces;

   * EOF is signaled with an empty string (‘''’);

   * It's not possible to parse empty strings, even if quoted.

When operating in POSIX mode, *note shlex: c74. will try to obey to the
following parsing rules.

   * Quotes are stripped out, and do not separate words
     (‘"Do"Not"Separate"’ is parsed as the single word ‘DoNotSeparate’);

   * Non-quoted escape characters (e.g.  ‘'\'’) preserve the literal
     value of the next character that follows;

   * Enclosing characters in quotes which are not part of *note
     escapedquotes: 3c53. (e.g.  ‘"'"’)  preserve the literal value of
     all characters within the quotes;

   * Enclosing characters in quotes which are part of *note
     escapedquotes: 3c53. (e.g.  ‘'"'’)  preserves the literal value of
     all characters within the quotes, with the exception of the
     characters mentioned in *note escape: 3c51.  The escape characters
     retain its special meaning only when followed by the quote in use,
     or the escape character itself.  Otherwise the escape character
     will be considered a normal character.

   * EOF is signaled with a *note None: 61b. value;

   * Quoted empty strings (‘''’) are allowed.


File: python.info,  Node: Improved Compatibility with Shells,  Prev: Parsing Rules,  Up: shlex --- 簡單的語法分析

5.24.3.3 Improved Compatibility with Shells
...........................................

在 3.6 版被加入.

The *note shlex: b2. class provides compatibility with the parsing
performed by common Unix shells like ‘bash’, ‘dash’, and ‘sh’.  To take
advantage of this compatibility, specify the ‘punctuation_chars’
argument in the constructor.  This defaults to ‘False’, which preserves
pre-3.6 behaviour.  However, if it is set to ‘True’, then parsing of the
characters ‘();<>|&’ is changed: any run of these characters is returned
as a single token.  While this is short of a full parser for shells
(which would be out of scope for the standard library, given the
multiplicity of shells out there), it does allow you to perform
processing of command lines more easily than you could otherwise.  To
illustrate, you can see the difference in the following snippet:

     >>> import shlex
     >>> text = "a && b; c && d || e; f >'abc'; (def \"ghi\")"
     >>> s = shlex.shlex(text, posix=True)
     >>> s.whitespace_split = True
     >>> list(s)
     ['a', '&&', 'b;', 'c', '&&', 'd', '||', 'e;', 'f', '>abc;', '(def', 'ghi)']
     >>> s = shlex.shlex(text, posix=True, punctuation_chars=True)
     >>> s.whitespace_split = True
     >>> list(s)
     ['a', '&&', 'b', ';', 'c', '&&', 'd', '||', 'e', ';', 'f', '>', 'abc', ';',
     '(', 'def', 'ghi', ')']

Of course, tokens will be returned which are not valid for shells, and
you'll need to implement your own error checks on the returned tokens.

Instead of passing ‘True’ as the value for the punctuation_chars
parameter, you can pass a string with specific characters, which will be
used to determine which characters constitute punctuation.  For example:

     >>> import shlex
     >>> s = shlex.shlex("a && b || c", punctuation_chars="|")
     >>> list(s)
     ['a', '&', '&', 'b', '||', 'c']

     備註: When ‘punctuation_chars’ is specified, the *note wordchars:
     3c43. attribute is augmented with the characters ‘~-./*?=’.  That
     is because these characters can appear in file names (including
     wildcards) and command-line arguments (e.g.  ‘--color=auto’).
     Hence:

          >>> import shlex
          >>> s = shlex.shlex('~/a && b-c --color=auto || d *.py?',
          ...                 punctuation_chars=True)
          >>> list(s)
          ['~/a', '&&', 'b-c', '--color=auto', '||', 'd', '*.py?']

     However, to match the shell as closely as possible, it is
     recommended to always use ‘posix’ and *note whitespace_split: 3c4f.
     when using *note punctuation_chars: 18d6, which will negate *note
     wordchars: 3c43. entirely.

For best effect, ‘punctuation_chars’ should be set in conjunction with
‘posix=True’.  (Note that ‘posix=False’ is the default for *note shlex:
c74.)


File: python.info,  Node: 以 Tk 打造圖形使用者介面 Graphical User Interfaces,  Next: 開發工具,  Prev: 程式框架,  Up: Python 標準函式庫 Standard Library

5.25 以 Tk 打造圖形使用者介面 (Graphical User Interfaces)
=========================================================

Tk/Tcl has long been an integral part of Python.  It provides a robust
and platform independent windowing toolkit, that is available to Python
programmers using the *note tkinter: d9. package, and its extension, the
*note tkinter.ttk: e2. module.

*note tkinter: d9. 套件是 Tcl/Tk 之上的一個輕薄物件導向層。要使用 *note
tkinter: d9.，你不需要編寫 Tcl 程式，但會需要查閱 Tk 文件和部份 Tcl 文件
。*note tkinter: d9. 是一組將 Tk 小工具 (widget) 實作為 Python 類別的包
裝器。

*note tkinter: d9. 的主要優點是速度快，而且通常與 Python 捆綁 (bundle) 在
一起。儘管其標準文件不是很完整，但還是有些不錯的材料，包括：參考資料、教
學、書籍等。*note tkinter: d9. 曾因其過時的外觀而眾所皆知，但這在 Tk 8.5
中得到了極大的改進。此外，還有許多其他你可能會感興趣的 GUI 函式庫。
Python wiki 列出了幾個替代的 GUI 框架和工具(1)。

* Menu:

* tkinter: tkinter --- Tcl/Tk 的 Python 介面. Tcl/Tk 的 Python 介面
* tkinter.colorchooser: tkinter colorchooser --- 顏色選擇對話框. 顏色選擇對話框
* tkinter.font: tkinter font --- Tkinter 字型包裝器. Tkinter 字型包裝器
* Tkinter 對話框::
* tkinter.messagebox: tkinter messagebox --- Tkinter 訊息提示. Tkinter 訊息提示
* tkinter.scrolledtext: tkinter scrolledtext --- 捲動文字小工具. 捲動文字小工具
* tkinter.dnd: tkinter dnd --- 拖放支援. 拖放支援
* tkinter.ttk: tkinter ttk --- Tk 主題化小工具. Tk 主題化小工具
* IDLE: IDLE<62>.

   ---------- Footnotes ----------

   (1) https://wiki.python.org/moin/GuiProgramming


File: python.info,  Node: tkinter --- Tcl/Tk 的 Python 介面,  Next: tkinter colorchooser --- 顏色選擇對話框,  Up: 以 Tk 打造圖形使用者介面 Graphical User Interfaces

5.25.1 ‘tkinter’ -- Tcl/Tk 的 Python 介面
-----------------------------------------

'原始碼：'Lib/tkinter/__init__.py(1)

__________________________________________________________________

The *note tkinter: d9. package ("Tk interface") is the standard Python
interface to the Tcl/Tk GUI toolkit.  Both Tk and *note tkinter: d9. are
available on most Unix platforms, including macOS, as well as on Windows
systems.

Running ‘python -m tkinter’ from the command line should open a window
demonstrating a simple Tk interface, letting you know that *note
tkinter: d9. is properly installed on your system, and also showing what
version of Tcl/Tk is installed, so you can read the Tcl/Tk documentation
specific to that version.

Tkinter supports a range of Tcl/Tk versions, built either with or
without thread support.  The official Python binary release bundles
Tcl/Tk 8.6 threaded.  See the source code for the *note _tkinter: 3.
module for more information about supported versions.

Tkinter is not a thin wrapper, but adds a fair amount of its own logic
to make the experience more pythonic.  This documentation will
concentrate on these additions and changes, and refer to the official
Tcl/Tk documentation for details that are unchanged.

     備註: Tcl/Tk 8.5 (2007) introduced a modern set of themed user
     interface components along with a new API to use them.  Both old
     and new APIs are still available.  Most documentation you will find
     online still uses the old API and can be woefully outdated.

也參考
......

   * 
     TkDocs(2)

          Extensive tutorial on creating user interfaces with Tkinter.
          Explains key concepts, and illustrates recommended approaches
          using the modern API.

   * 
     Tkinter 8.5 reference: a GUI for Python(3)

          Reference documentation for Tkinter 8.5 detailing available
          classes, methods, and options.

Tcl/Tk 相關資源：

   * 
     Tk 指令(4)

          Comprehensive reference to each of the underlying Tcl/Tk
          commands used by Tkinter.

   * 
     Tcl/Tk 首頁(5)

          Additional documentation, and links to Tcl/Tk core
          development.

書籍：

   * 
     Modern Tkinter for Busy Python Developers(6)

          由 Mark Roseman 所著。(ISBN 978-1999149567)

   * 
     Python GUI programming with Tkinter(7)

          由 Alan D. Moore 所著。(ISBN 978-1788835886)

   * 
     Programming Python(8)

          由 Mark Lutz 所著；大部分 Tkinter 主題都有涵蓋。(ISBN
          978-0596158101)

   * 
     Tcl and the Tk Toolkit (2nd edition)(9)

          由 Tcl/Tk 發明者 John Ousterhout 與 Ken Jones 所著；不包含
          Tkinter。(ISBN 978-0321336330)

* Menu:

* Architecture::
* Tkinter Modules::
* Tkinter Life Preserver::
* Threading model::
* Handy Reference::
* File Handlers::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/tkinter/__init__.py

   (2) https://tkdocs.com/

   (3) https://www.tkdocs.com/shipman/

   (4) https://www.tcl.tk/man/tcl8.6/TkCmd/contents.htm

   (5) https://www.tcl.tk

   (6) https://tkdocs.com/book.html

   (7) 
https://www.packtpub.com/product/python-gui-programming-with-tkinter/9781788835886

   (8) https://learning-python.com/about-pp4e.html

   (9) https://www.amazon.com/exec/obidos/ASIN/032133633X


File: python.info,  Node: Architecture,  Next: Tkinter Modules,  Up: tkinter --- Tcl/Tk 的 Python 介面

5.25.1.1 Architecture
.....................

Tcl/Tk is not a single library but rather consists of a few distinct
modules, each with separate functionality and its own official
documentation.  Python's binary releases also ship an add-on module
together with it.

Tcl

     Tcl is a dynamic interpreted programming language, just like
     Python.  Though it can be used on its own as a general-purpose
     programming language, it is most commonly embedded into C
     applications as a scripting engine or an interface to the Tk
     toolkit.  The Tcl library has a C interface to create and manage
     one or more instances of a Tcl interpreter, run Tcl commands and
     scripts in those instances, and add custom commands implemented in
     either Tcl or C. Each interpreter has an event queue, and there are
     facilities to send events to it and process them.  Unlike Python,
     Tcl's execution model is designed around cooperative multitasking,
     and Tkinter bridges this difference (see *note Threading model:
     3c61. for details).

Tk

     Tk is a Tcl package(1) implemented in C that adds custom commands
     to create and manipulate GUI widgets.  Each *note Tk: 152a. object
     embeds its own Tcl interpreter instance with Tk loaded into it.
     Tk's widgets are very customizable, though at the cost of a dated
     appearance.  Tk uses Tcl's event queue to generate and process GUI
     events.

Ttk

     Themed Tk (Ttk) is a newer family of Tk widgets that provide a much
     better appearance on different platforms than many of the classic
     Tk widgets.  Ttk is distributed as part of Tk, starting with Tk
     version 8.5.  Python bindings are provided in a separate module,
     *note tkinter.ttk: e2.

Internally, Tk and Ttk use facilities of the underlying operating
system, i.e., Xlib on Unix/X11, Cocoa on macOS, GDI on Windows.

When your Python application uses a class in Tkinter, e.g., to create a
widget, the *note tkinter: d9. module first assembles a Tcl/Tk command
string.  It passes that Tcl command string to an internal *note
_tkinter: 3. binary module, which then calls the Tcl interpreter to
evaluate it.  The Tcl interpreter will then call into the Tk and/or Ttk
packages, which will in turn make calls to Xlib, Cocoa, or GDI.

   ---------- Footnotes ----------

   (1) https://wiki.tcl-lang.org/37432


File: python.info,  Node: Tkinter Modules,  Next: Tkinter Life Preserver,  Prev: Architecture,  Up: tkinter --- Tcl/Tk 的 Python 介面

5.25.1.2 Tkinter Modules
........................

Support for Tkinter is spread across several modules.  Most applications
will need the main *note tkinter: d9. module, as well as the *note
tkinter.ttk: e2. module, which provides the modern themed widget set and
API:

     from tkinter import *
     from tkinter import ttk

 -- 類別: tkinter.Tk (screenName=None, baseName=None, className='Tk',
          useTk=True, sync=False, use=None)

     Construct a toplevel Tk widget, which is usually the main window of
     an application, and initialize a Tcl interpreter for this widget.
     Each instance has its own associated Tcl interpreter.

     The *note Tk: 152a. class is typically instantiated using all
     default values.  However, the following keyword arguments are
     currently recognized:

     'screenName'

          When given (as a string), sets the ‘DISPLAY’ environment
          variable.  (X11 only)

     'baseName'

          Name of the profile file.  By default, 'baseName' is derived
          from the program name (‘sys.argv[0]’).

     'className'

          Name of the widget class.  Used as a profile file and also as
          the name with which Tcl is invoked ('argv0' in 'interp').

     'useTk'

          If ‘True’, initialize the Tk subsystem.  The *note
          tkinter.Tcl(): 3c63. function sets this to ‘False’.

     'sync'

          If ‘True’, execute all X server commands synchronously, so
          that errors are reported immediately.  Can be used for
          debugging.  (X11 only)

     'use'

          Specifies the 'id' of the window in which to embed the
          application, instead of it being created as an independent
          toplevel window.  'id' must be specified in the same way as
          the value for the -use option for toplevel widgets (that is,
          it has a form like that returned by ‘winfo_id()’).

          Note that on some platforms this will only work correctly if
          'id' refers to a Tk frame or toplevel that has its -container
          option enabled.

     *note Tk: 152a. reads and interprets profile files, named
     ‘.`className'.tcl’ and ‘.`baseName'.tcl’, into the Tcl interpreter
     and calls *note exec(): 162. on the contents of ‘.`className'.py’
     and ‘.`baseName'.py’.  The path for the profile files is the ‘HOME’
     environment variable or, if that isn't defined, then *note
     os.curdir: 26b7.

      -- 屬性: tk

          The Tk application object created by instantiating *note Tk:
          152a.  This provides access to the Tcl interpreter.  Each
          widget that is attached the same instance of *note Tk: 152a.
          has the same value for its *note tk: 3c64. attribute.

      -- 屬性: master

          The widget object that contains this widget.  For *note Tk:
          152a, the 'master' is *note None: 61b. because it is the main
          window.  The terms 'master' and 'parent' are similar and
          sometimes used interchangeably as argument names; however,
          calling ‘winfo_parent()’ returns a string of the widget name
          whereas *note master: 3c65. returns the object.
          'parent'/'child' reflects the tree-like relationship while
          'master'/'slave' reflects the container structure.

      -- 屬性: children

          The immediate descendants of this widget as a *note dict: 23b.
          with the child widget names as the keys and the child instance
          objects as the values.

 -- 函式: tkinter.Tcl (screenName=None, baseName=None, className='Tk',
          useTk=False)

     The *note Tcl(): 3c63. function is a factory function which creates
     an object much like that created by the *note Tk: 152a. class,
     except that it does not initialize the Tk subsystem.  This is most
     often useful when driving the Tcl interpreter in an environment
     where one doesn't want to create extraneous toplevel windows, or
     where one cannot (such as Unix/Linux systems without an X server).
     An object created by the *note Tcl(): 3c63. object can have a
     Toplevel window created (and the Tk subsystem initialized) by
     calling its ‘loadtk()’ method.

The modules that provide Tk support include:

*note tkinter: d9.

     主要的 Tkinter 模組。

*note tkinter.colorchooser: da.

     Dialog to let the user choose a color.

*note tkinter.commondialog: db.

     Base class for the dialogs defined in the other modules listed
     here.

*note tkinter.filedialog: dd.

     Common dialogs to allow the user to specify a file to open or save.

*note tkinter.font: de.

     Utilities to help work with fonts.

*note tkinter.messagebox: df.

     Access to standard Tk dialog boxes.

*note tkinter.scrolledtext: e0.

     Text widget with a vertical scroll bar built in.

*note tkinter.simpledialog: e1.

     Basic dialogs and convenience functions.

*note tkinter.ttk: e2.

     Themed widget set introduced in Tk 8.5, providing modern
     alternatives for many of the classic widgets in the main *note
     tkinter: d9. module.

Additional modules:

*note _tkinter: 3.

     A binary module that contains the low-level interface to Tcl/Tk.
     It is automatically imported by the main *note tkinter: d9. module,
     and should never be used directly by application programmers.  It
     is usually a shared library (or DLL), but might in some cases be
     statically linked with the Python interpreter.

*note idlelib: 69.

     Python's Integrated Development and Learning Environment (IDLE).
     Based on *note tkinter: d9.

‘tkinter.constants’

     Symbolic constants that can be used in place of strings when
     passing various parameters to Tkinter calls.  Automatically
     imported by the main *note tkinter: d9. module.

*note tkinter.dnd: dc.

     (experimental) Drag-and-drop support for *note tkinter: d9.  This
     will become deprecated when it is replaced with the Tk DND.

*note turtle: ea.

     Turtle graphics in a Tk window.


File: python.info,  Node: Tkinter Life Preserver,  Next: Threading model,  Prev: Tkinter Modules,  Up: tkinter --- Tcl/Tk 的 Python 介面

5.25.1.3 Tkinter Life Preserver
...............................

This section is not designed to be an exhaustive tutorial on either Tk
or Tkinter.  For that, refer to one of the external resources noted
earlier.  Instead, this section provides a very quick orientation to
what a Tkinter application looks like, identifies foundational Tk
concepts, and explains how the Tkinter wrapper is structured.

The remainder of this section will help you to identify the classes,
methods, and options you'll need in your Tkinter application, and where
to find more detailed documentation on them, including in the official
Tcl/Tk reference manual.

* Menu:

* A Hello World Program::
* Important Tk Concepts::
* Understanding How Tkinter Wraps Tcl/Tk::
* How do I...? What option does...?: How do I ? What option does ?.
* Navigating the Tcl/Tk Reference Manual::


File: python.info,  Node: A Hello World Program,  Next: Important Tk Concepts,  Up: Tkinter Life Preserver

5.25.1.4 A Hello World Program
..............................

We'll start by walking through a "Hello World" application in Tkinter.
This isn't the smallest one we could write, but has enough to illustrate
some key concepts you'll need to know.

     from tkinter import *
     from tkinter import ttk
     root = Tk()
     frm = ttk.Frame(root, padding=10)
     frm.grid()
     ttk.Label(frm, text="Hello World!").grid(column=0, row=0)
     ttk.Button(frm, text="Quit", command=root.destroy).grid(column=1, row=0)
     root.mainloop()

After the imports, the next line creates an instance of the ‘Tk’ class,
which initializes Tk and creates its associated Tcl interpreter.  It
also creates a toplevel window, known as the root window, which serves
as the main window of the application.

The following line creates a frame widget, which in this case will
contain a label and a button we'll create next.  The frame is fit inside
the root window.

The next line creates a label widget holding a static text string.  The
‘grid()’ method is used to specify the relative layout (position) of the
label within its containing frame widget, similar to how tables in HTML
work.

A button widget is then created, and placed to the right of the label.
When pressed, it will call the ‘destroy()’ method of the root window.

Finally, the ‘mainloop()’ method puts everything on the display, and
responds to user input until the program terminates.


File: python.info,  Node: Important Tk Concepts,  Next: Understanding How Tkinter Wraps Tcl/Tk,  Prev: A Hello World Program,  Up: Tkinter Life Preserver

5.25.1.5 Important Tk Concepts
..............................

Even this simple program illustrates the following key Tk concepts:

widgets

     A Tkinter user interface is made up of individual 'widgets'.  Each
     widget is represented as a Python object, instantiated from classes
     like ‘ttk.Frame’, ‘ttk.Label’, and ‘ttk.Button’.

widget hierarchy

     Widgets are arranged in a 'hierarchy'.  The label and button were
     contained within a frame, which in turn was contained within the
     root window.  When creating each 'child' widget, its 'parent'
     widget is passed as the first argument to the widget constructor.

configuration options

     Widgets have 'configuration options', which modify their appearance
     and behavior, such as the text to display in a label or button.
     Different classes of widgets will have different sets of options.

geometry management

     Widgets aren't automatically added to the user interface when they
     are created.  A 'geometry manager' like ‘grid’ controls where in
     the user interface they are placed.

event loop

     Tkinter reacts to user input, changes from your program, and even
     refreshes the display only when actively running an 'event loop'.
     If your program isn't running the event loop, your user interface
     won't update.


File: python.info,  Node: Understanding How Tkinter Wraps Tcl/Tk,  Next: How do I ? What option does ?,  Prev: Important Tk Concepts,  Up: Tkinter Life Preserver

5.25.1.6 Understanding How Tkinter Wraps Tcl/Tk
...............................................

When your application uses Tkinter's classes and methods, internally
Tkinter is assembling strings representing Tcl/Tk commands, and
executing those commands in the Tcl interpreter attached to your
application's ‘Tk’ instance.

Whether it's trying to navigate reference documentation, trying to find
the right method or option, adapting some existing code, or debugging
your Tkinter application, there are times that it will be useful to
understand what those underlying Tcl/Tk commands look like.

To illustrate, here is the Tcl/Tk equivalent of the main part of the
Tkinter script above.

     ttk::frame .frm -padding 10
     grid .frm
     grid [ttk::label .frm.lbl -text "Hello World!"] -column 0 -row 0
     grid [ttk::button .frm.btn -text "Quit" -command "destroy ."] -column 1 -row 0

Tcl's syntax is similar to many shell languages, where the first word is
the command to be executed, with arguments to that command following it,
separated by spaces.  Without getting into too many details, notice the
following:

   * The commands used to create widgets (like ‘ttk::frame’) correspond
     to widget classes in Tkinter.

   * Tcl widget options (like ‘-text’) correspond to keyword arguments
     in Tkinter.

   * Widgets are referred to by a 'pathname' in Tcl (like ‘.frm.btn’),
     whereas Tkinter doesn't use names but object references.

   * A widget's place in the widget hierarchy is encoded in its
     (hierarchical) pathname, which uses a ‘.’ (dot) as a path
     separator.  The pathname for the root window is just ‘.’ (dot).  In
     Tkinter, the hierarchy is defined not by pathname but by specifying
     the parent widget when creating each child widget.

   * Operations which are implemented as separate 'commands' in Tcl
     (like ‘grid’ or ‘destroy’) are represented as 'methods' on Tkinter
     widget objects.  As you'll see shortly, at other times Tcl uses
     what appear to be method calls on widget objects, which more
     closely mirror what would is used in Tkinter.


File: python.info,  Node: How do I ? What option does ?,  Next: Navigating the Tcl/Tk Reference Manual,  Prev: Understanding How Tkinter Wraps Tcl/Tk,  Up: Tkinter Life Preserver

5.25.1.7 How do I...? What option does...?
..........................................

If you're not sure how to do something in Tkinter, and you can't
immediately find it in the tutorial or reference documentation you're
using, there are a few strategies that can be helpful.

First, remember that the details of how individual widgets work may vary
across different versions of both Tkinter and Tcl/Tk.  If you're
searching documentation, make sure it corresponds to the Python and
Tcl/Tk versions installed on your system.

When searching for how to use an API, it helps to know the exact name of
the class, option, or method that you're using.  Introspection, either
in an interactive Python shell or with *note print(): f18, can help you
identify what you need.

To find out what configuration options are available on any widget, call
its ‘configure()’ method, which returns a dictionary containing a
variety of information about each object, including its default and
current values.  Use ‘keys()’ to get just the names of each option.

     btn = ttk.Button(frm, ...)
     print(btn.configure().keys())

As most widgets have many configuration options in common, it can be
useful to find out which are specific to a particular widget class.
Comparing the list of options to that of a simpler widget, like a frame,
is one way to do that.

     print(set(btn.configure().keys()) - set(frm.configure().keys()))

Similarly, you can find the available methods for a widget object using
the standard *note dir(): 5d8. function.  If you try it, you'll see
there are over 200 common widget methods, so again identifying those
specific to a widget class is helpful.

     print(dir(btn))
     print(set(dir(btn)) - set(dir(frm)))


File: python.info,  Node: Navigating the Tcl/Tk Reference Manual,  Prev: How do I ? What option does ?,  Up: Tkinter Life Preserver

5.25.1.8 Navigating the Tcl/Tk Reference Manual
...............................................

As noted, the official Tk commands(1) reference manual (man pages) is
often the most accurate description of what specific operations on
widgets do.  Even when you know the name of the option or method that
you need, you may still have a few places to look.

While all operations in Tkinter are implemented as method calls on
widget objects, you've seen that many Tcl/Tk operations appear as
commands that take a widget pathname as its first parameter, followed by
optional parameters, e.g.

     destroy .
     grid .frm.btn -column 0 -row 0

Others, however, look more like methods called on a widget object (in
fact, when you create a widget in Tcl/Tk, it creates a Tcl command with
the name of the widget pathname, with the first parameter to that
command being the name of a method to call).

     .frm.btn invoke
     .frm.lbl configure -text "Goodbye"

In the official Tcl/Tk reference documentation, you'll find most
operations that look like method calls on the man page for a specific
widget (e.g., you'll find the ‘invoke()’ method on the ttk::button(2)
man page), while functions that take a widget as a parameter often have
their own man page (e.g., grid(3)).

You'll find many common options and methods in the options(4) or
ttk::widget(5) man pages, while others are found in the man page for a
specific widget class.

You'll also find that many Tkinter methods have compound names, e.g.,
‘winfo_x()’, ‘winfo_height()’, ‘winfo_viewable()’.  You'd find
documentation for all of these in the winfo(6) man page.

     備註: Somewhat confusingly, there are also methods on all Tkinter
     widgets that don't actually operate on the widget, but operate at a
     global scope, independent of any widget.  Examples are methods for
     accessing the clipboard or the system bell.  (They happen to be
     implemented as methods in the base ‘Widget’ class that all Tkinter
     widgets inherit from).

   ---------- Footnotes ----------

   (1) https://www.tcl.tk/man/tcl8.6/TkCmd/contents.htm

   (2) https://www.tcl.tk/man/tcl8.6/TkCmd/ttk_button.htm

   (3) https://www.tcl.tk/man/tcl8.6/TkCmd/grid.htm

   (4) https://www.tcl.tk/man/tcl8.6/TkCmd/options.htm

   (5) https://www.tcl.tk/man/tcl8.6/TkCmd/ttk_widget.htm

   (6) https://www.tcl.tk/man/tcl8.6/TkCmd/winfo.htm


File: python.info,  Node: Threading model,  Next: Handy Reference,  Prev: Tkinter Life Preserver,  Up: tkinter --- Tcl/Tk 的 Python 介面

5.25.1.9 Threading model
........................

Python and Tcl/Tk have very different threading models, which *note
tkinter: d9. tries to bridge.  If you use threads, you may need to be
aware of this.

A Python interpreter may have many threads associated with it.  In Tcl,
multiple threads can be created, but each thread has a separate Tcl
interpreter instance associated with it.  Threads can also create more
than one interpreter instance, though each interpreter instance can be
used only by the one thread that created it.

Each ‘Tk’ object created by *note tkinter: d9. contains a Tcl
interpreter.  It also keeps track of which thread created that
interpreter.  Calls to *note tkinter: d9. can be made from any Python
thread.  Internally, if a call comes from a thread other than the one
that created the ‘Tk’ object, an event is posted to the interpreter's
event queue, and when executed, the result is returned to the calling
Python thread.

Tcl/Tk applications are normally event-driven, meaning that after
initialization, the interpreter runs an event loop (i.e.
‘Tk.mainloop()’) and responds to events.  Because it is single-threaded,
event handlers must respond quickly, otherwise they will block other
events from being processed.  To avoid this, any long-running
computations should not run in an event handler, but are either broken
into smaller pieces using timers, or run in another thread.  This is
different from many GUI toolkits where the GUI runs in a completely
separate thread from all application code including event handlers.

If the Tcl interpreter is not running the event loop and processing
events, any *note tkinter: d9. calls made from threads other than the
one running the Tcl interpreter will fail.

A number of special cases exist:

   * Tcl/Tk libraries can be built so they are not thread-aware.  In
     this case, *note tkinter: d9. calls the library from the
     originating Python thread, even if this is different than the
     thread that created the Tcl interpreter.  A global lock ensures
     only one call occurs at a time.

   * While *note tkinter: d9. allows you to create more than one
     instance of a ‘Tk’ object (with its own interpreter), all
     interpreters that are part of the same thread share a common event
     queue, which gets ugly fast.  In practice, don't create more than
     one instance of ‘Tk’ at a time.  Otherwise, it's best to create
     them in separate threads and ensure you're running a thread-aware
     Tcl/Tk build.

   * Blocking event handlers are not the only way to prevent the Tcl
     interpreter from reentering the event loop.  It is even possible to
     run multiple nested event loops or abandon the event loop entirely.
     If you're doing anything tricky when it comes to events or threads,
     be aware of these possibilities.

   * There are a few select *note tkinter: d9. functions that presently
     work only when called from the thread that created the Tcl
     interpreter.


File: python.info,  Node: Handy Reference,  Next: File Handlers,  Prev: Threading model,  Up: tkinter --- Tcl/Tk 的 Python 介面

5.25.1.10 Handy Reference
.........................

* Menu:

* Setting Options::
* The Packer::
* Packer Options::
* Coupling Widget Variables::
* The Window Manager::
* Tk Option Data Types::
* Bindings and Events::
* The index Parameter::
* Images::


File: python.info,  Node: Setting Options,  Next: The Packer,  Up: Handy Reference

5.25.1.11 Setting Options
.........................

Options control things like the color and border width of a widget.
Options can be set in three ways:

At object creation time, using keyword arguments

          fred = Button(self, fg="red", bg="blue")

After object creation, treating the option name like a dictionary index

          fred["fg"] = "red"
          fred["bg"] = "blue"

Use the config() method to update multiple attrs subsequent to object creation

          fred.config(fg="red", bg="blue")

For a complete explanation of a given option and its behavior, see the
Tk man pages for the widget in question.

Note that the man pages list "STANDARD OPTIONS" and "WIDGET SPECIFIC
OPTIONS" for each widget.  The former is a list of options that are
common to many widgets, the latter are the options that are
idiosyncratic to that particular widget.  The Standard Options are
documented on the ‘options(3)(1)’ man page.

No distinction between standard and widget-specific options is made in
this document.  Some options don't apply to some kinds of widgets.
Whether a given widget responds to a particular option depends on the
class of the widget; buttons have a ‘command’ option, labels do not.

The options supported by a given widget are listed in that widget's man
page, or can be queried at runtime by calling the ‘config()’ method
without arguments, or by calling the ‘keys()’ method on that widget.
The return value of these calls is a dictionary whose key is the name of
the option as a string (for example, ‘'relief'’) and whose values are
5-tuples.

Some options, like ‘bg’ are synonyms for common options with long names
(‘bg’ is shorthand for "background").  Passing the ‘config()’ method the
name of a shorthand option will return a 2-tuple, not 5-tuple.  The
2-tuple passed back will contain the name of the synonym and the "real"
option (such as ‘('bg', 'background')’).

Index       含義                                  範例
                                                  
---------------------------------------------------------------------
                                                  
0           option name                           ‘'relief'’
                                                  
                                                  
1           option name for database lookup       ‘'relief'’
                                                  
                                                  
2           option class for database lookup      ‘'Relief'’
                                                  
                                                  
3           default value                         ‘'raised'’
                                                  
                                                  
4           current value                         ‘'groove'’
                                                  

範例：

     >>> print(fred.config())
     {'relief': ('relief', 'relief', 'Relief', 'raised', 'groove')}

Of course, the dictionary printed will include all the options available
and their values.  This is meant only as an example.

   ---------- Footnotes ----------

   (1) https://manpages.debian.org/options(3)


File: python.info,  Node: The Packer,  Next: Packer Options,  Prev: Setting Options,  Up: Handy Reference

5.25.1.12 The Packer
....................

The packer is one of Tk's geometry-management mechanisms.  Geometry
managers are used to specify the relative positioning of widgets within
their container - their mutual 'master'.  In contrast to the more
cumbersome 'placer' (which is used less commonly, and we do not cover
here), the packer takes qualitative relationship specification -
'above', 'to the left of', 'filling', etc - and works everything out to
determine the exact placement coordinates for you.

The size of any 'master' widget is determined by the size of the "slave
widgets" inside.  The packer is used to control where slave widgets
appear inside the master into which they are packed.  You can pack
widgets into frames, and frames into other frames, in order to achieve
the kind of layout you desire.  Additionally, the arrangement is
dynamically adjusted to accommodate incremental changes to the
configuration, once it is packed.

Note that widgets do not appear until they have had their geometry
specified with a geometry manager.  It's a common early mistake to leave
out the geometry specification, and then be surprised when the widget is
created but nothing appears.  A widget will appear only after it has
had, for example, the packer's ‘pack()’ method applied to it.

The pack() method can be called with keyword-option/value pairs that
control where the widget is to appear within its container, and how it
is to behave when the main application window is resized.  Here are some
examples:

     fred.pack()                     # defaults to side = "top"
     fred.pack(side="left")
     fred.pack(expand=1)


File: python.info,  Node: Packer Options,  Next: Coupling Widget Variables,  Prev: The Packer,  Up: Handy Reference

5.25.1.13 Packer Options
........................

For more extensive information on the packer and the options that it can
take, see the man pages and page 183 of John Ousterhout's book.

anchor

     Anchor type.  Denotes where the packer is to place each slave in
     its parcel.

expand

     Boolean, ‘0’ or ‘1’.

fill

     Legal values: ‘'x'’, ‘'y'’, ‘'both'’, ‘'none'’.

ipadx and ipady

     A distance - designating internal padding on each side of the slave
     widget.

padx and pady

     A distance - designating external padding on each side of the slave
     widget.

side

     Legal values are: ‘'left'’, ‘'right'’, ‘'top'’, ‘'bottom'’.


File: python.info,  Node: Coupling Widget Variables,  Next: The Window Manager,  Prev: Packer Options,  Up: Handy Reference

5.25.1.14 Coupling Widget Variables
...................................

The current-value setting of some widgets (like text entry widgets) can
be connected directly to application variables by using special options.
These options are ‘variable’, ‘textvariable’, ‘onvalue’, ‘offvalue’, and
‘value’.  This connection works both ways: if the variable changes for
any reason, the widget it's connected to will be updated to reflect the
new value.

Unfortunately, in the current implementation of *note tkinter: d9. it is
not possible to hand over an arbitrary Python variable to a widget
through a ‘variable’ or ‘textvariable’ option.  The only kinds of
variables for which this works are variables that are subclassed from a
class called Variable, defined in *note tkinter: d9.

There are many useful subclasses of Variable already defined:
‘StringVar’, ‘IntVar’, ‘DoubleVar’, and ‘BooleanVar’.  To read the
current value of such a variable, call the ‘get()’ method on it, and to
change its value you call the ‘set()’ method.  If you follow this
protocol, the widget will always track the value of the variable, with
no further intervention on your part.

舉例來說：

     import tkinter as tk

     class App(tk.Frame):
         def __init__(self, master):
             super().__init__(master)
             self.pack()

             self.entrythingy = tk.Entry()
             self.entrythingy.pack()

             # Create the application variable.
             self.contents = tk.StringVar()
             # Set it to some value.
             self.contents.set("this is a variable")
             # Tell the entry widget to watch this variable.
             self.entrythingy["textvariable"] = self.contents

             # Define a callback for when the user hits return.
             # It prints the current value of the variable.
             self.entrythingy.bind('<Key-Return>',
                                  self.print_contents)

         def print_contents(self, event):
             print("Hi. The current entry content is:",
                   self.contents.get())

     root = tk.Tk()
     myapp = App(root)
     myapp.mainloop()


File: python.info,  Node: The Window Manager,  Next: Tk Option Data Types,  Prev: Coupling Widget Variables,  Up: Handy Reference

5.25.1.15 The Window Manager
............................

In Tk, there is a utility command, ‘wm’, for interacting with the window
manager.  Options to the ‘wm’ command allow you to control things like
titles, placement, icon bitmaps, and the like.  In *note tkinter: d9,
these commands have been implemented as methods on the ‘Wm’ class.
Toplevel widgets are subclassed from the ‘Wm’ class, and so can call the
‘Wm’ methods directly.

To get at the toplevel window that contains a given widget, you can
often just refer to the widget's master.  Of course if the widget has
been packed inside of a frame, the master won't represent a toplevel
window.  To get at the toplevel window that contains an arbitrary
widget, you can call the ‘_root()’ method.  This method begins with an
underscore to denote the fact that this function is part of the
implementation, and not an interface to Tk functionality.

以下是一些常見用法範例：

     import tkinter as tk

     class App(tk.Frame):
         def __init__(self, master=None):
             super().__init__(master)
             self.pack()

     # create the application
     myapp = App()

     #
     # here are method calls to the window manager class
     #
     myapp.master.title("My Do-Nothing Application")
     myapp.master.maxsize(1000, 400)

     # start the program
     myapp.mainloop()


File: python.info,  Node: Tk Option Data Types,  Next: Bindings and Events,  Prev: The Window Manager,  Up: Handy Reference

5.25.1.16 Tk Option Data Types
..............................

anchor

     Legal values are points of the compass: ‘"n"’, ‘"ne"’, ‘"e"’,
     ‘"se"’, ‘"s"’, ‘"sw"’, ‘"w"’, ‘"nw"’, and also ‘"center"’.

bitmap

     There are eight built-in, named bitmaps: ‘'error'’, ‘'gray25'’,
     ‘'gray50'’, ‘'hourglass'’, ‘'info'’, ‘'questhead'’, ‘'question'’,
     ‘'warning'’.  To specify an X bitmap filename, give the full path
     to the file, preceded with an ‘@’, as in
     ‘"@/usr/contrib/bitmap/gumby.bit"’.

boolean

     You can pass integers 0 or 1 or the strings ‘"yes"’ or ‘"no"’.

callback

     This is any Python function that takes no arguments.  For example:

          def print_it():
              print("hi there")
          fred["command"] = print_it

color

     Colors can be given as the names of X colors in the rgb.txt file,
     or as strings representing RGB values in 4 bit: ‘"#RGB"’, 8 bit:
     ‘"#RRGGBB"’, 12 bit: ‘"#RRRGGGBBB"’, or 16 bit: ‘"#RRRRGGGGBBBB"’
     ranges, where R,G,B here represent any legal hex digit.  See page
     160 of Ousterhout's book for details.

cursor

     The standard X cursor names from ‘cursorfont.h’ can be used,
     without the ‘XC_’ prefix.  For example to get a hand cursor
     (‘XC_hand2’), use the string ‘"hand2"’.  You can also specify a
     bitmap and mask file of your own.  See page 179 of Ousterhout's
     book.

distance

     Screen distances can be specified in either pixels or absolute
     distances.  Pixels are given as numbers and absolute distances as
     strings, with the trailing character denoting units: ‘c’ for
     centimetres, ‘i’ for inches, ‘m’ for millimetres, ‘p’ for printer's
     points.  For example, 3.5 inches is expressed as ‘"3.5i"’.

font

     Tk uses a list font name format, such as ‘{courier 10 bold}’.  Font
     sizes with positive numbers are measured in points; sizes with
     negative numbers are measured in pixels.

geometry

     This is a string of the form ‘widthxheight’, where width and height
     are measured in pixels for most widgets (in characters for widgets
     displaying text).  For example: ‘fred["geometry"] = "200x100"’.

justify

     Legal values are the strings: ‘"left"’, ‘"center"’, ‘"right"’, and
     ‘"fill"’.

region

     This is a string with four space-delimited elements, each of which
     is a legal distance (see above).  For example: ‘"2 3 4 5"’ and ‘"3i
     2i 4.5i 2i"’ and ‘"3c 2c 4c 10.43c"’ are all legal regions.

relief

     Determines what the border style of a widget will be.  Legal values
     are: ‘"raised"’, ‘"sunken"’, ‘"flat"’, ‘"groove"’, and ‘"ridge"’.

scrollcommand

     This is almost always the ‘set()’ method of some scrollbar widget,
     but can be any widget method that takes a single argument.

wrap

     Must be one of: ‘"none"’, ‘"char"’, or ‘"word"’.


File: python.info,  Node: Bindings and Events,  Next: The index Parameter,  Prev: Tk Option Data Types,  Up: Handy Reference

5.25.1.17 Bindings and Events
.............................

The bind method from the widget command allows you to watch for certain
events and to have a callback function trigger when that event type
occurs.  The form of the bind method is:

     def bind(self, sequence, func, add=''):

where:

sequence（序列）

     is a string that denotes the target kind of event.  (See the
     ‘bind(3tk)(1)’ man page, and page 201 of John Ousterhout's book,
     ‘Tcl and the Tk Toolkit (2nd edition)’, for details).

func

     is a Python function, taking one argument, to be invoked when the
     event occurs.  An Event instance will be passed as the argument.
     (Functions deployed this way are commonly known as 'callbacks'.)

add

     is optional, either ‘''’ or ‘'+'’.  Passing an empty string denotes
     that this binding is to replace any other bindings that this event
     is associated with.  Passing a ‘'+'’ means that this function is to
     be added to the list of functions bound to this event type.

舉例來說：

     def turn_red(self, event):
         event.widget["activeforeground"] = "red"

     self.button.bind("<Enter>", self.turn_red)

Notice how the widget field of the event is being accessed in the
‘turn_red()’ callback.  This field contains the widget that caught the X
event.  The following table lists the other event fields you can access,
and how they are denoted in Tk, which can be useful when referring to
the Tk man pages.

Tk       Tkinter Event Field       Tk       Tkinter Event Field
                                            
----------------------------------------------------------------------
                                            
%f       focus                     %A       char
                                            
                                            
%h       height                    %E       send_event
                                            
                                            
%k       keycode                   %K       keysym
                                            
                                            
%s       state                     %N       keysym_num
                                            
                                            
%t       time                      %T       type
                                            
                                            
%w       width                     %W       widget
                                            
                                            
%x       x                         %X       x_root
                                            
                                            
%y       y                         %Y       y_root
                                            

   ---------- Footnotes ----------

   (1) https://manpages.debian.org/bind(3tk)


File: python.info,  Node: The index Parameter,  Next: Images,  Prev: Bindings and Events,  Up: Handy Reference

5.25.1.18 The index Parameter
.............................

A number of widgets require "index" parameters to be passed.  These are
used to point at a specific place in a Text widget, or to particular
characters in an Entry widget, or to particular menu items in a Menu
widget.

Entry widget indexes (index, view index, etc.)

     Entry widgets have options that refer to character positions in the
     text being displayed.  You can use these *note tkinter: d9.
     functions to access these special points in text widgets:

Text widget indexes

     The index notation for Text widgets is very rich and is best
     described in the Tk man pages.

Menu indexes (menu.invoke(), menu.entryconfig(), etc.)

     Some options and methods for menus manipulate specific menu
     entries.  Anytime a menu index is needed for an option or a
     parameter, you may pass in:

        * an integer which refers to the numeric position of the entry
          in the widget, counted from the top, starting with 0;

        * the string ‘"active"’, which refers to the menu position that
          is currently under the cursor;

        * the string ‘"last"’ which refers to the last menu item;

        * An integer preceded by ‘@’, as in ‘@6’, where the integer is
          interpreted as a y pixel coordinate in the menu's coordinate
          system;

        * the string ‘"none"’, which indicates no menu entry at all,
          most often used with menu.activate() to deactivate all
          entries, and finally,

        * a text string that is pattern matched against the label of the
          menu entry, as scanned from the top of the menu to the bottom.
          Note that this index type is considered after all the others,
          which means that matches for menu items labelled ‘last’,
          ‘active’, or ‘none’ may be interpreted as the above literals,
          instead.


File: python.info,  Node: Images,  Prev: The index Parameter,  Up: Handy Reference

5.25.1.19 Images
................

Images of different formats can be created through the corresponding
subclass of ‘tkinter.Image’:

   * ‘BitmapImage’ for images in XBM format.

   * ‘PhotoImage’ for images in PGM, PPM, GIF and PNG formats.  The
     latter is supported starting with Tk 8.6.

Either type of image is created through either the ‘file’ or the ‘data’
option (other options are available as well).

在 3.13 版的變更: Added the ‘PhotoImage’ method ‘copy_replace()’ to copy
a region from one image to other image, possibly with pixel zooming
and/or subsampling.  Add 'from_coords' parameter to ‘PhotoImage’ methods
‘copy()’, ‘zoom()’ and ‘subsample()’.  Add 'zoom' and 'subsample'
parameters to ‘PhotoImage’ method ‘copy()’.

The image object can then be used wherever an ‘image’ option is
supported by some widget (e.g.  labels, buttons, menus).  In these
cases, Tk will not keep a reference to the image.  When the last Python
reference to the image object is deleted, the image data is deleted as
well, and Tk will display an empty box wherever the image was used.

也參考
......

The Pillow(1) package adds support for formats such as BMP, JPEG, TIFF,
and WebP, among others.

   ---------- Footnotes ----------

   (1) https://python-pillow.org/


File: python.info,  Node: File Handlers,  Prev: Handy Reference,  Up: tkinter --- Tcl/Tk 的 Python 介面

5.25.1.20 File Handlers
.......................

Tk allows you to register and unregister a callback function which will
be called from the Tk mainloop when I/O is possible on a file
descriptor.  Only one handler may be registered per file descriptor.
Example code:

     import tkinter
     widget = tkinter.Tk()
     mask = tkinter.READABLE | tkinter.WRITABLE
     widget.tk.createfilehandler(file, mask, callback)
     ...
     widget.tk.deletefilehandler(file)

This feature is not available on Windows.

Since you don't know how many bytes are available for reading, you may
not want to use the *note BufferedIOBase: 63a. or *note TextIOBase: 63b.
*note read(): 12bc. or *note readline(): 12bd. methods, since these will
insist on reading a predefined number of bytes.  For sockets, the *note
recv(): d4a. or *note recvfrom(): d4b. methods will work fine; for other
files, use raw reads or ‘os.read(file.fileno(), maxbytecount)’.

 -- 方法: Widget.tk.createfilehandler (file, mask, func)

     Registers the file handler callback function 'func'.  The 'file'
     argument may either be an object with a *note fileno(): 2732.
     method (such as a file or socket object), or an integer file
     descriptor.  The 'mask' argument is an ORed combination of any of
     the three constants below.  The callback is called as follows:

          callback(file, mask)

 -- 方法: Widget.tk.deletefilehandler (file)

     Unregisters a file handler.

 -- 資料: _tkinter.READABLE
 -- 資料: _tkinter.WRITABLE
 -- 資料: _tkinter.EXCEPTION

     Constants used in the 'mask' arguments.


File: python.info,  Node: tkinter colorchooser --- 顏色選擇對話框,  Next: tkinter font --- Tkinter 字型包裝器,  Prev: tkinter --- Tcl/Tk 的 Python 介面,  Up: 以 Tk 打造圖形使用者介面 Graphical User Interfaces

5.25.2 ‘tkinter.colorchooser’ -- 顏色選擇對話框
-----------------------------------------------

'原始碼：'Lib/tkinter/colorchooser.py(1)

__________________________________________________________________

*note tkinter.colorchooser: da. 模組提供類別 *note Chooser: 3c82. 當作與
原生顏色選擇器對話框的介面。‘Chooser’ 實作了一個顏色選擇的互動視窗。類別
‘Chooser’ 繼承了類別 *note Dialog: 3c83.。

 -- 類別: tkinter.colorchooser.Chooser (master=None, **options)

 -- 函式: tkinter.colorchooser.askcolor (color=None, **options)

     建立一個顏色選擇對話框。一旦呼叫這個方法便會顯示視窗，等待使用者做
     出選擇後，回傳選擇的顏色（或者是 ‘None’）給呼叫者。

也參考
......

*note tkinter.commondialog: db. 模組

     Tkinter 標準對話框模組

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/tkinter/colorchooser.py


File: python.info,  Node: tkinter font --- Tkinter 字型包裝器,  Next: Tkinter 對話框,  Prev: tkinter colorchooser --- 顏色選擇對話框,  Up: 以 Tk 打造圖形使用者介面 Graphical User Interfaces

5.25.3 ‘tkinter.font’ -- Tkinter 字型包裝器
-------------------------------------------

'原始碼：'Lib/tkinter/font.py(1)

__________________________________________________________________

*note tkinter.font: de. 模組提供類別 *note Font: 180d.，可以建立及使用已
命名的字型。

不同的字重 (font weights) 以及傾斜 (slant) 是：

 -- 資料: tkinter.font.NORMAL
 -- 資料: tkinter.font.BOLD
 -- 資料: tkinter.font.ITALIC
 -- 資料: tkinter.font.ROMAN

 -- 類別: tkinter.font.Font (root=None, font=None, name=None,
          exists=False, **options)

     類別 *note Font: 180d. 代表一個已命名字型。'Font' 實例會被賦予一個
     的名字，也可以特指他們的字型家族 (font family)、字級 (size)、以及外
     觀設定。已命名字型是 Tk 建立及辨識字型為單一物件的方式，而不是每次
     出現時特指字型的屬性。

          引數：

                    'font' - 字型指定符號元組 (family, size, options)
                    'name' - 獨特字型名稱
                    'exists' - 如果存在的話，指向現有的已命名字型

          額外的關鍵字選項（若已指定 'font' 則會忽略）：

                    'family' - 字型家族，例如：Courier、Times
                    'size' - 字級
                         如果 'size' 是正數則會直譯成以點 (point) 為單位的字級。
                         如果 'size' 是負數則會變成絕對值
                         以像素 (pixel) 為單位的字級。
                    'weight' - 強調字型，例如：NORMAL（標準體）、BOLD（粗體）
                    'slant' - 例如：ROMAN（正體）、ITALIC（斜體）
                    'underline' - 字型加上底線（0 - 無底線、 1 - 加上底線）
                    'overstrike' - 字型加上刪除線（0 - 無刪除線、 1 - 加上刪除線）

      -- 方法: actual (option=None, displayof=None)

          回傳字型的屬性。

      -- 方法: cget (option)

          取得字型的其中一個屬性。

      -- 方法: config (**options)

          修改字體的多個屬性。

      -- 方法: copy ()

          回傳目前字體的新實例。

      -- 方法: measure (text, displayof=None)

          回傳目前字型被格式化時，在特定顯示區域中文字所用的空間。若顯示
          區域沒有被指定，則會假定主程式視窗為顯示區域。

      -- 方法: metrics (*options, **kw)

          回傳字型特定的資料。其選項包含：

          'ascent' - 基準線以及最高點的距離

               在字型中的一個字母可以佔用的空間

          'descent' - 基準線以及最低點的距離

               在字型中的一個字母可以佔用的空間

          'linespace' - 最小所需的垂直間距

               在字型中的任兩個字母之間，確保跨行時不會有垂直重疊。

          'fixed' - 若字型為等寬 (fixed-width) 的則為 1，否則為 0

 -- 函式: tkinter.font.families (root=None, displayof=None)

     回傳不同的字型家族。

 -- 函式: tkinter.font.names (root=None)

     回傳已定義字型的名字。

 -- 函式: tkinter.font.nametofont (name, root=None)

     回傳一個 *note Font: 180d.，代表一個 tk 已命名字型。

     在 3.10 版的變更: 新增 'root' 參數。

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/tkinter/font.py


File: python.info,  Node: Tkinter 對話框,  Next: tkinter messagebox --- Tkinter 訊息提示,  Prev: tkinter font --- Tkinter 字型包裝器,  Up: 以 Tk 打造圖形使用者介面 Graphical User Interfaces

5.25.4 Tkinter 對話框
---------------------

* Menu:

* tkinter.simpledialog: tkinter simpledialog --- 標準 Tkinter 輸入對話框. 標準 Tkinter 輸入對話框
* tkinter.filedialog: tkinter filedialog --- File selection dialogs. File selection dialogs
* tkinter.commondialog: tkinter commondialog --- Dialog window templates. Dialog window templates


File: python.info,  Node: tkinter simpledialog --- 標準 Tkinter 輸入對話框,  Next: tkinter filedialog --- File selection dialogs,  Up: Tkinter 對話框

5.25.4.1 ‘tkinter.simpledialog’ -- 標準 Tkinter 輸入對話框
..........................................................

'原始碼：'Lib/tkinter/simpledialog.py(1)

__________________________________________________________________

The *note tkinter.simpledialog: e1. module contains convenience classes
and functions for creating simple modal dialogs to get a value from the
user.

 -- 函式: tkinter.simpledialog.askfloat (title, prompt, **kw)
 -- 函式: tkinter.simpledialog.askinteger (title, prompt, **kw)
 -- 函式: tkinter.simpledialog.askstring (title, prompt, **kw)

     The above three functions provide dialogs that prompt the user to
     enter a value of the desired type.

 -- 類別: tkinter.simpledialog.Dialog (parent, title=None)

     The base class for custom dialogs.

      -- 方法: body (master)

          Override to construct the dialog's interface and return the
          widget that should have initial focus.

      -- 方法: buttonbox ()

          Default behaviour adds OK and Cancel buttons.  Override for
          custom button layouts.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/tkinter/simpledialog.py


File: python.info,  Node: tkinter filedialog --- File selection dialogs,  Next: tkinter commondialog --- Dialog window templates,  Prev: tkinter simpledialog --- 標準 Tkinter 輸入對話框,  Up: Tkinter 對話框

5.25.4.2 ‘tkinter.filedialog’ -- File selection dialogs
.......................................................

'原始碼：'Lib/tkinter/filedialog.py(1)

__________________________________________________________________

The *note tkinter.filedialog: dd. module provides classes and factory
functions for creating file/directory selection windows.

* Menu:

* Native Load/Save Dialogs::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/tkinter/filedialog.py


File: python.info,  Node: Native Load/Save Dialogs,  Up: tkinter filedialog --- File selection dialogs

5.25.4.3 Native Load/Save Dialogs
.................................

The following classes and functions provide file dialog windows that
combine a native look-and-feel with configuration options to customize
behaviour.  The following keyword arguments are applicable to the
classes and functions listed below:

          'parent' - the window to place the dialog on top of

          'title' - the title of the window

          'initialdir' - the directory that the dialog starts in

          'initialfile' - the file selected upon opening of the dialog

          'filetypes' - a sequence of (label, pattern) tuples, '*' wildcard is allowed

          'defaultextension' - default extension to append to file (save dialogs)

          'multiple' - when true, selection of multiple items is allowed

'Static factory functions'

The below functions when called create a modal, native look-and-feel
dialog, wait for the user's selection, then return the selected value(s)
or ‘None’ to the caller.

 -- 函式: tkinter.filedialog.askopenfile (mode='r', **options)
 -- 函式: tkinter.filedialog.askopenfiles (mode='r', **options)

     The above two functions create an *note Open: 3c9f. dialog and
     return the opened file object(s) in read-only mode.

 -- 函式: tkinter.filedialog.asksaveasfile (mode='w', **options)

     Create a *note SaveAs: 3ca1. dialog and return a file object opened
     in write-only mode.

 -- 函式: tkinter.filedialog.askopenfilename (**options)
 -- 函式: tkinter.filedialog.askopenfilenames (**options)

     The above two functions create an *note Open: 3c9f. dialog and
     return the selected filename(s) that correspond to existing
     file(s).

 -- 函式: tkinter.filedialog.asksaveasfilename (**options)

     Create a *note SaveAs: 3ca1. dialog and return the selected
     filename.

 -- 函式: tkinter.filedialog.askdirectory (**options)

          Prompt user to select a directory.
          Additional keyword option:
               'mustexist' - determines if selection must be an existing directory.

 -- 類別: tkinter.filedialog.Open (master=None, **options)
 -- 類別: tkinter.filedialog.SaveAs (master=None, **options)

     The above two classes provide native dialog windows for saving and
     loading files.

'Convenience classes'

The below classes are used for creating file/directory windows from
scratch.  These do not emulate the native look-and-feel of the platform.

 -- 類別: tkinter.filedialog.Directory (master=None, **options)

     Create a dialog prompting the user to select a directory.

     備註: The 'FileDialog' class should be subclassed for custom event
     handling and behaviour.

 -- 類別: tkinter.filedialog.FileDialog (master, title=None)

     Create a basic file selection dialog.

      -- 方法: cancel_command (event=None)

          Trigger the termination of the dialog window.

      -- 方法: dirs_double_event (event)

          Event handler for double-click event on directory.

      -- 方法: dirs_select_event (event)

          Event handler for click event on directory.

      -- 方法: files_double_event (event)

          Event handler for double-click event on file.

      -- 方法: files_select_event (event)

          Event handler for single-click event on file.

      -- 方法: filter_command (event=None)

          Filter the files by directory.

      -- 方法: get_filter ()

          Retrieve the file filter currently in use.

      -- 方法: get_selection ()

          Retrieve the currently selected item.

      -- 方法: go (dir_or_file=os.curdir, pattern='*', default='',
               key=None)

          Render dialog and start event loop.

      -- 方法: ok_event (event)

          Exit dialog returning current selection.

      -- 方法: quit (how=None)

          Exit dialog returning filename, if any.

      -- 方法: set_filter (dir, pat)

          Set the file filter.

      -- 方法: set_selection (file)

          Update the current file selection to 'file'.

 -- 類別: tkinter.filedialog.LoadFileDialog (master, title=None)

     A subclass of FileDialog that creates a dialog window for selecting
     an existing file.

      -- 方法: ok_command ()

          Test that a file is provided and that the selection indicates
          an already existing file.

 -- 類別: tkinter.filedialog.SaveFileDialog (master, title=None)

     A subclass of FileDialog that creates a dialog window for selecting
     a destination file.

      -- 方法: ok_command ()

          Test whether or not the selection points to a valid file that
          is not a directory.  Confirmation is required if an already
          existing file is selected.


File: python.info,  Node: tkinter commondialog --- Dialog window templates,  Prev: tkinter filedialog --- File selection dialogs,  Up: Tkinter 對話框

5.25.4.4 ‘tkinter.commondialog’ -- Dialog window templates
..........................................................

'原始碼：'Lib/tkinter/commondialog.py(1)

__________________________________________________________________

The *note tkinter.commondialog: db. module provides the *note Dialog:
3c83. class that is the base class for dialogs defined in other
supporting modules.

 -- 類別: tkinter.commondialog.Dialog (master=None, **options)

      -- 方法: show (color=None, **options)

          Render the Dialog window.

也參考
......

*note tkinter.messagebox: df. 模組、*note 讀寫檔案: 1b83.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/tkinter/commondialog.py


File: python.info,  Node: tkinter messagebox --- Tkinter 訊息提示,  Next: tkinter scrolledtext --- 捲動文字小工具,  Prev: Tkinter 對話框,  Up: 以 Tk 打造圖形使用者介面 Graphical User Interfaces

5.25.5 ‘tkinter.messagebox’ -- Tkinter 訊息提示
-----------------------------------------------

'原始碼：'Lib/tkinter/messagebox.py(1)

__________________________________________________________________

*note tkinter.messagebox: df. 模組提供了模板基底類別以及各種常用配置的便
捷方法。訊息框 (message box) 是互動視窗 (modal)，會基於使用者的選擇回傳
（‘True’、‘False’、‘None’、*note OK: 3cbd.、*note CANCEL: 3cbe.、*note
YES: 3cbf.、*note NO: 3cc0.）的子集。常見的訊息框樣式 (style) 和版面配置
(layout) 包括但不限於：

[image src="python-figures/tk_msg.png"]


Figure
 -- 類別: tkinter.messagebox.Message (master=None, **options)

     建立一個訊息視窗，其中包含應用程式指定的訊息、一個圖示和一組按鈕。
     訊息視窗中的每個按鈕都有唯一的符號名稱作為識別（請參考 'type' 選項
     ）。

     支援以下選項：

          'command'

               指定當使用者關閉對話框 (dialog) 時要呼叫的函式。使用者按
               一下以關閉對話框的按鈕的名稱作為引數傳遞。此選項僅適用於
               macOS。

          'default'

               給出此訊息視窗的預設按鈕的*note 符號名稱: 3cc2.（*note
               OK: 3cbd.、*note CANCEL: 3cbe. 等）。如果未指定此選項，則
               對話框中的第一個按鈕將成為預設按鈕。

          'detail'

               透過 'message' 選項指定將輔助訊息給主訊息。訊息詳細資訊將
               顯示在主要訊息下方，並且在作業系統支援的情況下，將以比主
               要訊息更不強調的字體顯示。

          'icon'

               指定要顯示的*note 圖示: 3cc3.。如果未指定此選項，則會顯示
               *note INFO: 3cc4. 圖示。

          'message'

               指定要在此訊息框中顯示的訊息。預設值為空字串。

          'parent'

               使指定視窗成為訊息框的邏輯父視窗 (logical parent window)。
               訊息框顯示在其父視窗的頂部。

          'title'

               指定顯示為訊息框標題的字串。此選項在 macOS 上被忽略，其平
               台指南禁止在此類對話方塊上使用標題。

          'type'

               安排一組需顯示的*note 預先定義的按鈕組合: 3cc5.。

      -- 方法: show (**options)

          顯示訊息視窗並等待使用者選擇其中一個按鈕。然後回傳所選按鈕的符
          號名稱。關鍵字引數可以覆寫建構函式中指定的選項。

'資訊訊息框'

 -- 函式: tkinter.messagebox.showinfo (title=None, message=None,
          **options)

     建立並顯示具有指定標題和訊息的資訊訊息框。

'警告訊息框'

 -- 函式: tkinter.messagebox.showwarning (title=None, message=None,
          **options)

     建立並顯示具有指定標題和訊息的警告訊息框。

 -- 函式: tkinter.messagebox.showerror (title=None, message=None,
          **options)

     建立並顯示具有指定標題和訊息的錯誤訊息框。

'問題留言框'

 -- 函式: tkinter.messagebox.askquestion (title=None, message=None, *,
          type=YESNO, **options)

     問一個問題。預設顯示按鈕 *note YES: 3cbf. 和 *note NO: 3cc0.。回傳
     所選按鈕的符號名稱。

 -- 函式: tkinter.messagebox.askokcancel (title=None, message=None,
          **options)

     詢問操作是否應該繼續。顯示按鈕 *note OK: 3cbd. 和 *note CANCEL:
     3cbe.。如果答案正確則傳回 ‘True’，否則回傳 ‘False’。

 -- 函式: tkinter.messagebox.askretrycancel (title=None, message=None,
          **options)

     詢問是否應重試操作。顯示按鈕 *note RETRY: 3ccd. 和 *note CANCEL:
     3cbe.。如果答案為是，則回傳 ‘True’，否則回傳 ‘False’。

 -- 函式: tkinter.messagebox.askyesno (title=None, message=None,
          **options)

     問一個問題。顯示按鈕 *note YES: 3cbf. 和 *note NO: 3cc0.。如果答案
     為是，則回傳 ‘True’，否則回傳 ‘False’。

 -- 函式: tkinter.messagebox.askyesnocancel (title=None, message=None,
          **options)

     問一個問題。顯示按鈕 *note YES: 3cbf.、*note NO: 3cc0. 和 *note
     CANCEL: 3cbe.。如果答案為是，則回傳 ‘True’；如果取消則回傳 ‘None’，
     否則回傳 ‘False’。
按鈕的符號名稱：

 -- 資料: tkinter.messagebox.ABORT = 'abort'

 -- 資料: tkinter.messagebox.RETRY = 'retry'

 -- 資料: tkinter.messagebox.IGNORE = 'ignore'

 -- 資料: tkinter.messagebox.OK = 'ok'

 -- 資料: tkinter.messagebox.CANCEL = 'cancel'

 -- 資料: tkinter.messagebox.YES = 'yes'

 -- 資料: tkinter.messagebox.NO = 'no'
預先定義的按鈕組合：

 -- 資料: tkinter.messagebox.ABORTRETRYIGNORE = 'abortretryignore'

     顯示三個按鈕，其符號名稱為 *note ABORT: 3cd0.、*note RETRY: 3ccd. 和
     *note IGNORE: 3cd1.。

 -- 資料: tkinter.messagebox.OK = 'ok'

     顯示一個按鈕，其符號名稱為 *note OK: 3cbd.。

 -- 資料: tkinter.messagebox.OKCANCEL = 'okcancel'

     顯示兩個按鈕，其符號名稱為 *note OK: 3cbd. 和 *note CANCEL: 3cbe.。

 -- 資料: tkinter.messagebox.RETRYCANCEL = 'retrycancel'

     顯示兩個按鈕，其符號名稱為 *note RETRY: 3ccd. 和 *note CANCEL:
     3cbe.。

 -- 資料: tkinter.messagebox.YESNO = 'yesno'

     顯示兩個按鈕，其符號名稱為 *note YES: 3cbf. 和 *note NO: 3cc0.。

 -- 資料: tkinter.messagebox.YESNOCANCEL = 'yesnocancel'

     顯示三個按鈕，其符號名稱為 *note YES: 3cbf.、*note NO: 3cc0. 和
     *note CANCEL: 3cbe.。
圖示圖像：

 -- 資料: tkinter.messagebox.ERROR = 'error'

 -- 資料: tkinter.messagebox.INFO = 'info'

 -- 資料: tkinter.messagebox.QUESTION = 'question'

 -- 資料: tkinter.messagebox.WARNING = 'warning'

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/tkinter/messagebox.py


File: python.info,  Node: tkinter scrolledtext --- 捲動文字小工具,  Next: tkinter dnd --- 拖放支援,  Prev: tkinter messagebox --- Tkinter 訊息提示,  Up: 以 Tk 打造圖形使用者介面 Graphical User Interfaces

5.25.6 ‘tkinter.scrolledtext’ -- 捲動文字小工具
-----------------------------------------------

'原始碼：'Lib/tkinter/scrolledtext.py(1)

__________________________________________________________________

The *note tkinter.scrolledtext: e0. module provides a class of the same
name which implements a basic text widget which has a vertical scroll
bar configured to do the "right thing."  Using the *note ScrolledText:
3cdc. class is a lot easier than setting up a text widget and scroll bar
directly.

The text widget and scrollbar are packed together in a ‘Frame’, and the
methods of the ‘Grid’ and ‘Pack’ geometry managers are acquired from the
‘Frame’ object.  This allows the *note ScrolledText: 3cdc. widget to be
used directly to achieve most normal geometry management behavior.

Should more specific control be necessary, the following attributes are
available:

 -- 類別: tkinter.scrolledtext.ScrolledText (master=None, **kw)

      -- 屬性: frame

          The frame which surrounds the text and scroll bar widgets.

      -- 屬性: vbar

          The scroll bar widget.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/tkinter/scrolledtext.py


File: python.info,  Node: tkinter dnd --- 拖放支援,  Next: tkinter ttk --- Tk 主題化小工具,  Prev: tkinter scrolledtext --- 捲動文字小工具,  Up: 以 Tk 打造圖形使用者介面 Graphical User Interfaces

5.25.7 ‘tkinter.dnd’ -- 拖放支援
--------------------------------

'原始碼：'Lib/tkinter/dnd.py(1)

__________________________________________________________________

     備註: This is experimental and due to be deprecated when it is
     replaced with the Tk DND.

The *note tkinter.dnd: dc. module provides drag-and-drop support for
objects within a single application, within the same window or between
windows.  To enable an object to be dragged, you must create an event
binding for it that starts the drag-and-drop process.  Typically, you
bind a ButtonPress event to a callback function that you write (see
*note Bindings and Events: 3c75.).  The function should call *note
dnd_start(): 3ce1, where 'source' is the object to be dragged, and
'event' is the event that invoked the call (the argument to your
callback function).

Selection of a target object occurs as follows:

  1. Top-down search of area under mouse for target widget

        * Target widget should have a callable 'dnd_accept' attribute

        * If 'dnd_accept' is not present or returns ‘None’, search moves
          to parent widget

        * If no target widget is found, then the target object is ‘None’

  2. Call to '<old_target>.dnd_leave(source, event)'

  3. Call to '<new_target>.dnd_enter(source, event)'

  4. Call to '<target>.dnd_commit(source, event)' to notify of drop

  5. Call to '<source>.dnd_end(target, event)' to signal end of
     drag-and-drop

 -- 類別: tkinter.dnd.DndHandler (source, event)

     The 'DndHandler' class handles drag-and-drop events tracking Motion
     and ButtonRelease events on the root of the event widget.

      -- 方法: cancel (event=None)

          Cancel the drag-and-drop process.

      -- 方法: finish (event, commit=0)

          Execute end of drag-and-drop functions.

      -- 方法: on_motion (event)

          Inspect area below mouse for target objects while drag is
          performed.

      -- 方法: on_release (event)

          Signal end of drag when the release pattern is triggered.

 -- 函式: tkinter.dnd.dnd_start (source, event)

     Factory function for drag-and-drop process.

也參考
......

*note Bindings and Events: 3c75.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/tkinter/dnd.py


File: python.info,  Node: tkinter ttk --- Tk 主題化小工具,  Next: IDLE<62>,  Prev: tkinter dnd --- 拖放支援,  Up: 以 Tk 打造圖形使用者介面 Graphical User Interfaces

5.25.8 ‘tkinter.ttk’ -- Tk 主題化小工具
---------------------------------------

'原始碼：'Lib/tkinter/ttk.py(1)

__________________________________________________________________

The *note tkinter.ttk: e2. module provides access to the Tk themed
widget set, introduced in Tk 8.5.  It provides additional benefits
including anti-aliased font rendering under X11 and window transparency
(requiring a composition window manager on X11).

The basic idea for *note tkinter.ttk: e2. is to separate, to the extent
possible, the code implementing a widget's behavior from the code
implementing its appearance.

也參考
......

Tk Widget Styling Support(2)

     A document introducing theming support for Tk

* Menu:

* 使用 Ttk::
* Ttk Widgets::
* Widget::
* Combobox::
* Spinbox::
* Notebook::
* Progressbar::
* Separator::
* Sizegrip::
* Treeview::
* Ttk Styling::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/tkinter/ttk.py

   (2) https://core.tcl.tk/tips/doc/trunk/tip/48.md


File: python.info,  Node: 使用 Ttk,  Next: Ttk Widgets,  Up: tkinter ttk --- Tk 主題化小工具

5.25.8.1 使用 Ttk
.................

To start using Ttk, import its module:

     from tkinter import ttk

To override the basic Tk widgets, the import should follow the Tk
import:

     from tkinter import *
     from tkinter.ttk import *

That code causes several *note tkinter.ttk: e2. widgets (‘Button’,
‘Checkbutton’, ‘Entry’, ‘Frame’, ‘Label’, ‘LabelFrame’, ‘Menubutton’,
‘PanedWindow’, ‘Radiobutton’, ‘Scale’ and ‘Scrollbar’) to automatically
replace the Tk widgets.

This has the direct benefit of using the new widgets which gives a
better look and feel across platforms; however, the replacement widgets
are not completely compatible.  The main difference is that widget
options such as "fg", "bg" and others related to widget styling are no
longer present in Ttk widgets.  Instead, use the ‘ttk.Style’ class for
improved styling effects.

也參考
......

Converting existing applications to use Tile widgets(1)

     A monograph (using Tcl terminology) about differences typically
     encountered when moving applications to use the new widgets.

   ---------- Footnotes ----------

   (1) https://tktable.sourceforge.net/tile/doc/converting.txt


File: python.info,  Node: Ttk Widgets,  Next: Widget,  Prev: 使用 Ttk,  Up: tkinter ttk --- Tk 主題化小工具

5.25.8.2 Ttk Widgets
....................

Ttk comes with 18 widgets, twelve of which already existed in tkinter:
‘Button’, ‘Checkbutton’, ‘Entry’, ‘Frame’, ‘Label’, ‘LabelFrame’,
‘Menubutton’, ‘PanedWindow’, ‘Radiobutton’, ‘Scale’, ‘Scrollbar’, and
*note Spinbox: b3b.  The other six are new: *note Combobox: 3ceb, *note
Notebook: 3cec, *note Progressbar: 3ced, ‘Separator’, ‘Sizegrip’ and
*note Treeview: a37.  And all them are subclasses of *note Widget: 3cee.

Using the Ttk widgets gives the application an improved look and feel.
As discussed above, there are differences in how the styling is coded.

Tk code:

     l1 = tkinter.Label(text="Test", fg="black", bg="white")
     l2 = tkinter.Label(text="Test", fg="black", bg="white")

Ttk code:

     style = ttk.Style()
     style.configure("BW.TLabel", foreground="black", background="white")

     l1 = ttk.Label(text="Test", style="BW.TLabel")
     l2 = ttk.Label(text="Test", style="BW.TLabel")

For more information about *note TtkStyling: 3cef, see the *note Style:
23e. class documentation.


File: python.info,  Node: Widget,  Next: Combobox,  Prev: Ttk Widgets,  Up: tkinter ttk --- Tk 主題化小工具

5.25.8.3 Widget
...............

‘ttk.Widget’ defines standard options and methods supported by Tk themed
widgets and is not supposed to be directly instantiated.

* Menu:

* 標準選項::
* Scrollable Widget Options::
* Label Options::
* 相容性選項::
* Widget States::
* ttk.Widget: ttk Widget.


File: python.info,  Node: 標準選項,  Next: Scrollable Widget Options,  Up: Widget

5.25.8.4 標準選項
.................

All the ‘ttk’ Widgets accept the following options:

選項            描述
                
-----------------------------------------------------------------------------------
                
class           Specifies the window class.  The class is used when querying the
                option database for the window's other options, to determine the
                default bindtags for the window, and to select the widget's
                default layout and style.  This option is read-only, and may
                only be specified when the window is created.
                
                
cursor          Specifies the mouse cursor to be used for the widget.  If set to
                the empty string (the default), the cursor is inherited for the
                parent widget.
                
                
takefocus       Determines whether the window accepts the focus during keyboard
                traversal.  0, 1 or an empty string is returned.  If 0 is
                returned, it means that the window should be skipped entirely
                during keyboard traversal.  If 1, it means that the window
                should receive the input focus as long as it is viewable.  And
                an empty string means that the traversal scripts make the
                decision about whether or not to focus on the window.
                
                
style           May be used to specify a custom widget style.
                


File: python.info,  Node: Scrollable Widget Options,  Next: Label Options,  Prev: 標準選項,  Up: Widget

5.25.8.5 Scrollable Widget Options
..................................

The following options are supported by widgets that are controlled by a
scrollbar.

選項                 描述
                     
-----------------------------------------------------------------------------------
                     
xscrollcommand       Used to communicate with horizontal scrollbars.
                     
                     When the view in the widget's window change, the widget
                     will generate a Tcl command based on the scrollcommand.
                     
                     Usually this option consists of the method
                     ‘Scrollbar.set()’ of some scrollbar.  This will cause the
                     scrollbar to be updated whenever the view in the window
                     changes.
                     
                     
yscrollcommand       Used to communicate with vertical scrollbars.  For some
                     more information, see above.
                     


File: python.info,  Node: Label Options,  Next: 相容性選項,  Prev: Scrollable Widget Options,  Up: Widget

5.25.8.6 Label Options
......................

The following options are supported by labels, buttons and other
button-like widgets.

選項               描述
                   
-----------------------------------------------------------------------------------
                   
text               Specifies a text string to be displayed inside the widget.
                   
                   
textvariable       Specifies a name whose value will be used in place of the
                   text option resource.
                   
                   
underline          If set, specifies the index (0-based) of a character to
                   underline in the text string.  The underline character is
                   used for mnemonic activation.
                   
                   
image              Specifies an image to display.  This is a list of 1 or more
                   elements.  The first element is the default image name.  The
                   rest of the list if a sequence of statespec/value pairs as
                   defined by *note Style.map(): 1820, specifying different
                   images to use when the widget is in a particular state or a
                   combination of states.  All images in the list should have
                   the same size.
                   
                   
compound           Specifies how to display the image relative to the text, in
                   the case both text and images options are present.  Valid
                   values are:
                   
                      * text: display text only
                   
                      * image: display image only
                   
                      * top, bottom, left, right: display image above, below,
                        left of, or right of the text, respectively.
                   
                      * none: the default.  display the image if present,
                        otherwise the text.
                   
                   
width              If greater than zero, specifies how much space, in character
                   widths, to allocate for the text label, if less than zero,
                   specifies a minimum width.  If zero or unspecified, the
                   natural width of the text label is used.
                   


File: python.info,  Node: 相容性選項,  Next: Widget States,  Prev: Label Options,  Up: Widget

5.25.8.7 相容性選項
...................

選項         描述
             
----------------------------------------------------------------------------------
             
state        May be set to "normal" or "disabled" to control the "disabled"
             state bit.  This is a write-only option: setting it changes the
             widget state, but the *note Widget.state(): 3cf5. method does not
             affect this option.
             


File: python.info,  Node: Widget States,  Next: ttk Widget,  Prev: 相容性選項,  Up: Widget

5.25.8.8 Widget States
......................

The widget state is a bitmap of independent state flags.

旗標             描述
                 
-----------------------------------------------------------------------------------
                 
active           The mouse cursor is over the widget and pressing a mouse button
                 will cause some action to occur
                 
                 
disabled         Widget is disabled under program control
                 
                 
focus            Widget has keyboard focus
                 
                 
pressed          Widget is being pressed
                 
                 
selected         "On", "true", or "current" for things like Checkbuttons and
                 radiobuttons
                 
                 
background       Windows and Mac have a notion of an "active" or foreground
                 window.  The 'background' state is set for widgets in a
                 background window, and cleared for those in the foreground
                 window
                 
                 
readonly         Widget should not allow user modification
                 
                 
alternate        A widget-specific alternate display format
                 
                 
invalid          The widget's value is invalid
                 

A state specification is a sequence of state names, optionally prefixed
with an exclamation point indicating that the bit is off.


File: python.info,  Node: ttk Widget,  Prev: Widget States,  Up: Widget

5.25.8.9 ttk.Widget
...................

Besides the methods described below, the ‘ttk.Widget’ supports the
methods ‘tkinter.Widget.cget()’ and ‘tkinter.Widget.configure()’.

 -- 類別: tkinter.ttk.Widget

      -- 方法: identify (x, y)

          Returns the name of the element at position 'x' 'y', or the
          empty string if the point does not lie within any element.

          'x' and 'y' are pixel coordinates relative to the widget.

      -- 方法: instate (statespec, callback=None, *args, **kw)

          Test the widget's state.  If a callback is not specified,
          returns ‘True’ if the widget state matches 'statespec' and
          ‘False’ otherwise.  If callback is specified then it is called
          with args if widget state matches 'statespec'.

      -- 方法: state (statespec=None)

          Modify or inquire widget state.  If 'statespec' is specified,
          sets the widget state according to it and return a new
          'statespec' indicating which flags were changed.  If
          'statespec' is not specified, returns the currently enabled
          state flags.

     'statespec' will usually be a list or a tuple.


File: python.info,  Node: Combobox,  Next: Spinbox,  Prev: Widget,  Up: tkinter ttk --- Tk 主題化小工具

5.25.8.10 Combobox
..................

The ‘ttk.Combobox’ widget combines a text field with a pop-down list of
values.  This widget is a subclass of ‘Entry’.

Besides the methods inherited from *note Widget: 3cee.: ‘Widget.cget()’,
‘Widget.configure()’, *note Widget.identify(): 3cf8, *note
Widget.instate(): 3cf9. and *note Widget.state(): 3cf5, and the
following inherited from ‘Entry’: ‘Entry.bbox()’, ‘Entry.delete()’,
‘Entry.icursor()’, ‘Entry.index()’, ‘Entry.insert()’,
‘Entry.selection()’, ‘Entry.xview()’, it has some other methods,
described at ‘ttk.Combobox’.

* Menu:

* 選項::
* Virtual events::
* ttk.Combobox: ttk Combobox.


File: python.info,  Node: 選項,  Next: Virtual events,  Up: Combobox

5.25.8.11 選項
..............

This widget accepts the following specific options:

選項                  描述
                      
-----------------------------------------------------------------------------------
                      
exportselection       Boolean value.  If set, the widget selection is linked to
                      the Window Manager selection (which can be returned by
                      invoking Misc.selection_get, for example).
                      
                      
justify               Specifies how the text is aligned within the widget.  One
                      of "left", "center", or "right".
                      
                      
height                Specifies the height of the pop-down listbox, in rows.
                      
                      
postcommand           A script (possibly registered with Misc.register) that is
                      called immediately before displaying the values.  It may
                      specify which values to display.
                      
                      
state                 One of "normal", "readonly", or "disabled".  In the
                      "readonly" state, the value may not be edited directly,
                      and the user can only selection of the values from the
                      dropdown list.  In the "normal" state, the text field is
                      directly editable.  In the "disabled" state, no
                      interaction is possible.
                      
                      
textvariable          Specifies a name whose value is linked to the widget
                      value.  Whenever the value associated with that name
                      changes, the widget value is updated, and vice versa.  See
                      ‘tkinter.StringVar’.
                      
                      
values                Specifies the list of values to display in the drop-down
                      listbox.
                      
                      
width                 Specifies an integer value indicating the desired width of
                      the entry window, in average-size characters of the
                      widget's font.
                      


File: python.info,  Node: Virtual events,  Next: ttk Combobox,  Prev: 選項,  Up: Combobox

5.25.8.12 Virtual events
........................

The combobox widgets generates a '<<ComboboxSelected>>' virtual event
when the user selects an element from the list of values.


File: python.info,  Node: ttk Combobox,  Prev: Virtual events,  Up: Combobox

5.25.8.13 ttk.Combobox
......................

 -- 類別: tkinter.ttk.Combobox

      -- 方法: current (newindex=None)

          If 'newindex' is specified, sets the combobox value to the
          element position 'newindex'.  Otherwise, returns the index of
          the current value or -1 if the current value is not in the
          values list.

      -- 方法: get ()

          Returns the current value of the combobox.

      -- 方法: set (value)

          Sets the value of the combobox to 'value'.


File: python.info,  Node: Spinbox,  Next: Notebook,  Prev: Combobox,  Up: tkinter ttk --- Tk 主題化小工具

5.25.8.14 Spinbox
.................

The ‘ttk.Spinbox’ widget is a ‘ttk.Entry’ enhanced with increment and
decrement arrows.  It can be used for numbers or lists of string values.
This widget is a subclass of ‘Entry’.

Besides the methods inherited from *note Widget: 3cee.: ‘Widget.cget()’,
‘Widget.configure()’, *note Widget.identify(): 3cf8, *note
Widget.instate(): 3cf9. and *note Widget.state(): 3cf5, and the
following inherited from ‘Entry’: ‘Entry.bbox()’, ‘Entry.delete()’,
‘Entry.icursor()’, ‘Entry.index()’, ‘Entry.insert()’, ‘Entry.xview()’,
it has some other methods, described at ‘ttk.Spinbox’.

* Menu:

* 選項: 選項<2>.
* Virtual events: Virtual events<2>.
* ttk.Spinbox: ttk Spinbox.


File: python.info,  Node: 選項<2>,  Next: Virtual events<2>,  Up: Spinbox

5.25.8.15 選項
..............

This widget accepts the following specific options:

選項                       描述
                           
--------------------------------------------------------------------------------------
                           
from                       Float value.  If set, this is the minimum value to which
                           the decrement button will decrement.  Must be spelled as
                           ‘from_’ when used as an argument, since ‘from’ is a
                           Python keyword.
                           
                           
to                         Float value.  If set, this is the maximum value to which
                           the increment button will increment.
                           
                           
increment                  Float value.  Specifies the amount which the
                           increment/decrement buttons change the value.  Defaults
                           to 1.0.
                           
                           
values                     Sequence of string or float values.  If specified, the
                           increment/decrement buttons will cycle through the items
                           in this sequence rather than incrementing or
                           decrementing numbers.
                           
                           
wrap                       Boolean value.  If ‘True’, increment and decrement
                           buttons will cycle from the ‘to’ value to the ‘from’
                           value or the ‘from’ value to the ‘to’ value,
                           respectively.
                           
                           
format                     String value.  This specifies the format of numbers set
                           by the increment/decrement buttons.  It must be in the
                           form "%W.Pf", where W is the padded width of the value,
                           P is the precision, and '%' and 'f' are literal.
                           
                           
command                    Python callable.  Will be called with no arguments
                           whenever either of the increment or decrement buttons
                           are pressed.
                           


File: python.info,  Node: Virtual events<2>,  Next: ttk Spinbox,  Prev: 選項<2>,  Up: Spinbox

5.25.8.16 Virtual events
........................

The spinbox widget generates an '<<Increment>>' virtual event when the
user presses <Up>, and a '<<Decrement>>' virtual event when the user
presses <Down>.


File: python.info,  Node: ttk Spinbox,  Prev: Virtual events<2>,  Up: Spinbox

5.25.8.17 ttk.Spinbox
.....................

 -- 類別: tkinter.ttk.Spinbox

      -- 方法: get ()

          Returns the current value of the spinbox.

      -- 方法: set (value)

          Sets the value of the spinbox to 'value'.


File: python.info,  Node: Notebook,  Next: Progressbar,  Prev: Spinbox,  Up: tkinter ttk --- Tk 主題化小工具

5.25.8.18 Notebook
..................

Ttk Notebook widget manages a collection of windows and displays a
single one at a time.  Each child window is associated with a tab, which
the user may select to change the currently displayed window.

* Menu:

* 選項: 選項<3>.
* Tab Options::
* Tab Identifiers::
* 虛擬事件::
* ttk.Notebook: ttk Notebook.


File: python.info,  Node: 選項<3>,  Next: Tab Options,  Up: Notebook

5.25.8.19 選項
..............

This widget accepts the following specific options:

選項          描述
              
-----------------------------------------------------------------------------------
              
height        If present and greater than zero, specifies the desired height of
              the pane area (not including internal padding or tabs).
              Otherwise, the maximum height of all panes is used.
              
              
padding       Specifies the amount of extra space to add around the outside of
              the notebook.  The padding is a list up to four length
              specifications left top right bottom.  If fewer than four elements
              are specified, bottom defaults to top, right defaults to left, and
              top defaults to left.
              
              
width         If present and greater than zero, specified the desired width of
              the pane area (not including internal padding).  Otherwise, the
              maximum width of all panes is used.
              


File: python.info,  Node: Tab Options,  Next: Tab Identifiers,  Prev: 選項<3>,  Up: Notebook

5.25.8.20 Tab Options
.....................

There are also specific options for tabs:

選項            描述
                
-----------------------------------------------------------------------------------
                
state           Either "normal", "disabled" or "hidden".  If "disabled", then
                the tab is not selectable.  If "hidden", then the tab is not
                shown.
                
                
sticky          Specifies how the child window is positioned within the pane
                area.  Value is a string containing zero or more of the
                characters "n", "s", "e" or "w".  Each letter refers to a side
                (north, south, east or west) that the child window will stick
                to, as per the ‘grid()’ geometry manager.
                
                
padding         Specifies the amount of extra space to add between the notebook
                and this pane.  Syntax is the same as for the option padding
                used by this widget.
                
                
text            Specifies a text to be displayed in the tab.
                
                
image           Specifies an image to display in the tab.  See the option image
                described in *note Widget: 3cee.
                
                
compound        Specifies how to display the image relative to the text, in the
                case both options text and image are present.  See
                *note Label Options: 3cf3. for legal values.
                
                
underline       Specifies the index (0-based) of a character to underline in the
                text string.  The underlined character is used for mnemonic
                activation if *note Notebook.enable_traversal(): 3d0a. is
                called.
                


File: python.info,  Node: Tab Identifiers,  Next: 虛擬事件,  Prev: Tab Options,  Up: Notebook

5.25.8.21 Tab Identifiers
.........................

The tab_id present in several methods of ‘ttk.Notebook’ may take any of
the following forms:

   * An integer between zero and the number of tabs

   * The name of a child window

   * A positional specification of the form "@x,y", which identifies the
     tab

   * The literal string "current", which identifies the currently
     selected tab

   * The literal string "end", which returns the number of tabs (only
     valid for *note Notebook.index(): 3d0c.)


File: python.info,  Node: 虛擬事件,  Next: ttk Notebook,  Prev: Tab Identifiers,  Up: Notebook

5.25.8.22 虛擬事件
..................

This widget generates a '<<NotebookTabChanged>>' virtual event after a
new tab is selected.


File: python.info,  Node: ttk Notebook,  Prev: 虛擬事件,  Up: Notebook

5.25.8.23 ttk.Notebook
......................

 -- 類別: tkinter.ttk.Notebook

      -- 方法: add (child, **kw)

          Adds a new tab to the notebook.

          If window is currently managed by the notebook but hidden, it
          is restored to its previous position.

          可用的選項清單請見 *note Tab Options: 3d09.。

      -- 方法: forget (tab_id)

          Removes the tab specified by 'tab_id', unmaps and unmanages
          the associated window.

      -- 方法: hide (tab_id)

          Hides the tab specified by 'tab_id'.

          The tab will not be displayed, but the associated window
          remains managed by the notebook and its configuration
          remembered.  Hidden tabs may be restored with the *note add():
          3d0f. command.

      -- 方法: identify (x, y)

          Returns the name of the tab element at position 'x', 'y', or
          the empty string if none.

      -- 方法: index (tab_id)

          Returns the numeric index of the tab specified by 'tab_id', or
          the total number of tabs if 'tab_id' is the string "end".

      -- 方法: insert (pos, child, **kw)

          Inserts a pane at the specified position.

          'pos' is either the string "end", an integer index, or the
          name of a managed child.  If 'child' is already managed by the
          notebook, moves it to the specified position.

          可用的選項清單請見 *note Tab Options: 3d09.。

      -- 方法: select (tab_id=None)

          Selects the specified 'tab_id'.

          The associated child window will be displayed, and the
          previously selected window (if different) is unmapped.  If
          'tab_id' is omitted, returns the widget name of the currently
          selected pane.

      -- 方法: tab (tab_id, option=None, **kw)

          Query or modify the options of the specific 'tab_id'.

          If 'kw' is not given, returns a dictionary of the tab option
          values.  If 'option' is specified, returns the value of that
          'option'.  Otherwise, sets the options to the corresponding
          values.

      -- 方法: tabs ()

          Returns a list of windows managed by the notebook.

      -- 方法: enable_traversal ()

          Enable keyboard traversal for a toplevel window containing
          this notebook.

          This will extend the bindings for the toplevel window
          containing the notebook as follows:

             * ‘Control-Tab’: selects the tab following the currently
               selected one.

             * ‘Shift-Control-Tab’: selects the tab preceding the
               currently selected one.

             * ‘Alt-K’: where 'K' is the mnemonic (underlined) character
               of any tab, will select that tab.

          Multiple notebooks in a single toplevel may be enabled for
          traversal, including nested notebooks.  However, notebook
          traversal only works properly if all panes have the notebook
          they are in as master.


File: python.info,  Node: Progressbar,  Next: Separator,  Prev: Notebook,  Up: tkinter ttk --- Tk 主題化小工具

5.25.8.24 Progressbar
.....................

The ‘ttk.Progressbar’ widget shows the status of a long-running
operation.  It can operate in two modes: 1) the determinate mode which
shows the amount completed relative to the total amount of work to be
done and 2) the indeterminate mode which provides an animated display to
let the user know that work is progressing.

* Menu:

* 選項: 選項<4>.
* ttk.Progressbar: ttk Progressbar.


File: python.info,  Node: 選項<4>,  Next: ttk Progressbar,  Up: Progressbar

5.25.8.25 選項
..............

This widget accepts the following specific options:

選項           描述
               
-----------------------------------------------------------------------------------
               
orient         One of "horizontal" or "vertical".  Specifies the orientation of
               the progress bar.
               
               
length         Specifies the length of the long axis of the progress bar (width
               if horizontal, height if vertical).
               
               
mode           "determinate" 與 "indeterminate" 其中之一
               
               
maximum        A number specifying the maximum value.  Defaults to 100.
               
               
value          The current value of the progress bar.  In "determinate" mode,
               this represents the amount of work completed.  In "indeterminate"
               mode, it is interpreted as modulo 'maximum'; that is, the
               progress bar completes one "cycle" when its value increases by
               'maximum'.
               
               
variable       A name which is linked to the option value.  If specified, the
               value of the progress bar is automatically set to the value of
               this name whenever the latter is modified.
               
               
phase          Read-only option.  The widget periodically increments the value
               of this option whenever its value is greater than 0 and, in
               determinate mode, less than maximum.  This option may be used by
               the current theme to provide additional animation effects.
               


File: python.info,  Node: ttk Progressbar,  Prev: 選項<4>,  Up: Progressbar

5.25.8.26 ttk.Progressbar
.........................

 -- 類別: tkinter.ttk.Progressbar

      -- 方法: start (interval=None)

          Begin autoincrement mode: schedules a recurring timer event
          that calls *note Progressbar.step(): 3d1b. every 'interval'
          milliseconds.  If omitted, 'interval' defaults to 50
          milliseconds.

      -- 方法: step (amount=None)

          Increments the progress bar's value by 'amount'.

          'amount' defaults to 1.0 if omitted.

      -- 方法: stop ()

          Stop autoincrement mode: cancels any recurring timer event
          initiated by *note Progressbar.start(): 3d1a. for this
          progress bar.


File: python.info,  Node: Separator,  Next: Sizegrip,  Prev: Progressbar,  Up: tkinter ttk --- Tk 主題化小工具

5.25.8.27 Separator
...................

The ‘ttk.Separator’ widget displays a horizontal or vertical separator
bar.

It has no other methods besides the ones inherited from ‘ttk.Widget’.

* Menu:

* 選項: 選項<5>.


File: python.info,  Node: 選項<5>,  Up: Separator

5.25.8.28 選項
..............

This widget accepts the following specific option:

選項         描述
             
----------------------------------------------------------------------------------
             
orient       One of "horizontal" or "vertical".  Specifies the orientation of
             the separator.
             


File: python.info,  Node: Sizegrip,  Next: Treeview,  Prev: Separator,  Up: tkinter ttk --- Tk 主題化小工具

5.25.8.29 Sizegrip
..................

The ‘ttk.Sizegrip’ widget (also known as a grow box) allows the user to
resize the containing toplevel window by pressing and dragging the grip.

This widget has neither specific options nor specific methods, besides
the ones inherited from ‘ttk.Widget’.

* Menu:

* Platform-specific notes::
* Bugs::


File: python.info,  Node: Platform-specific notes,  Next: Bugs,  Up: Sizegrip

5.25.8.30 Platform-specific notes
.................................

   * On macOS, toplevel windows automatically include a built-in size
     grip by default.  Adding a ‘Sizegrip’ is harmless, since the
     built-in grip will just mask the widget.


File: python.info,  Node: Bugs,  Prev: Platform-specific notes,  Up: Sizegrip

5.25.8.31 Bugs
..............

   * If the containing toplevel's position was specified relative to the
     right or bottom of the screen (e.g.  ....), the ‘Sizegrip’ widget
     will not resize the window.

   * This widget supports only "southeast" resizing.


File: python.info,  Node: Treeview,  Next: Ttk Styling,  Prev: Sizegrip,  Up: tkinter ttk --- Tk 主題化小工具

5.25.8.32 Treeview
..................

The ‘ttk.Treeview’ widget displays a hierarchical collection of items.
Each item has a textual label, an optional image, and an optional list
of data values.  The data values are displayed in successive columns
after the tree label.

The order in which data values are displayed may be controlled by
setting the widget option ‘displaycolumns’.  The tree widget can also
display column headings.  Columns may be accessed by number or symbolic
names listed in the widget option columns.  See *note Column
Identifiers: 3d23.

Each item is identified by a unique name.  The widget will generate item
IDs if they are not supplied by the caller.  There is a distinguished
root item, named ‘{}’.  The root item itself is not displayed; its
children appear at the top level of the hierarchy.

Each item also has a list of tags, which can be used to associate event
bindings with individual items and control the appearance of the item.

The Treeview widget supports horizontal and vertical scrolling,
according to the options described in *note Scrollable Widget Options:
3cf2. and the methods *note Treeview.xview(): 3d24. and *note
Treeview.yview(): 3d25.

* Menu:

* 選項: 選項<6>.
* Item Options::
* Tag Options::
* Column Identifiers::
* 虛擬事件: 虛擬事件<2>.
* ttk.Treeview: ttk Treeview.


File: python.info,  Node: 選項<6>,  Next: Item Options,  Up: Treeview

5.25.8.33 選項
..............

This widget accepts the following specific options:

選項                 描述
                     
----------------------------------------------------------------------------------
                     
columns              A list of column identifiers, specifying the number of
                     columns and their names.
                     
                     
displaycolumns       A list of column identifiers (either symbolic or integer
                     indices) specifying which data columns are displayed and
                     the order in which they appear, or the string "#all".
                     
                     
height               Specifies the number of rows which should be visible.
                     Note: the requested width is determined from the sum of
                     the column widths.
                     
                     
padding              Specifies the internal padding for the widget.  The
                     padding is a list of up to four length specifications.
                     
                     
selectmode           Controls how the built-in class bindings manage the
                     selection.  One of "extended", "browse" or "none".  If set
                     to "extended" (the default), multiple items may be
                     selected.  If "browse", only a single item will be
                     selected at a time.  If "none", the selection will not be
                     changed.
                     
                     Note that the application code and tag bindings can set
                     the selection however they wish, regardless of the value
                     of this option.
                     
                     
show                 A list containing zero or more of the following values,
                     specifying which elements of the tree to display.
                     
                        * tree: display tree labels in column #0.
                     
                        * headings: display the heading row.
                     
                     The default is "tree headings", i.e., show all elements.
                     
                     'Note': Column #0 always refers to the tree column, even
                     if show="tree" is not specified.
                     


File: python.info,  Node: Item Options,  Next: Tag Options,  Prev: 選項<6>,  Up: Treeview

5.25.8.34 Item Options
......................

The following item options may be specified for items in the insert and
item widget commands.

選項         描述
             
---------------------------------------------------------------------------------
             
text         The textual label to display for the item.
             
             
image        A Tk Image, displayed to the left of the label.
             
             
values       The list of values associated with the item.
             
             Each item should have the same number of values as the widget
             option columns.  If there are fewer values than columns, the
             remaining values are assumed empty.  If there are more values
             than columns, the extra values are ignored.
             
             
open         ‘True’/‘False’ value indicating whether the item's children
             should be displayed or hidden.
             
             
tags         A list of tags associated with this item.
             


File: python.info,  Node: Tag Options,  Next: Column Identifiers,  Prev: Item Options,  Up: Treeview

5.25.8.35 Tag Options
.....................

The following options may be specified on tags:

選項             描述
                 
---------------------------------------------------------------------------------
                 
foreground       Specifies the text foreground color.
                 
                 
background       Specifies the cell or item background color.
                 
                 
font             Specifies the font to use when drawing text.
                 
                 
image            Specifies the item image, in case the item's image option is
                 empty.
                 


File: python.info,  Node: Column Identifiers,  Next: 虛擬事件<2>,  Prev: Tag Options,  Up: Treeview

5.25.8.36 Column Identifiers
............................

Column identifiers take any of the following forms:

   * A symbolic name from the list of columns option.

   * An integer n, specifying the nth data column.

   * A string of the form #n, where n is an integer, specifying the nth
     display column.

註解：

   * Item's option values may be displayed in a different order than the
     order in which they are stored.

   * Column #0 always refers to the tree column, even if show="tree" is
     not specified.

A data column number is an index into an item's option values list; a
display column number is the column number in the tree where the values
are displayed.  Tree labels are displayed in column #0.  If option
displaycolumns is not set, then data column n is displayed in column
#n+1.  Again, 'column #0 always refers to the tree column'.


File: python.info,  Node: 虛擬事件<2>,  Next: ttk Treeview,  Prev: Column Identifiers,  Up: Treeview

5.25.8.37 虛擬事件
..................

The Treeview widget generates the following virtual events.

事件                     描述
                         
--------------------------------------------------------------------------------
                         
<<TreeviewSelect>>       Generated whenever the selection changes.
                         
                         
<<TreeviewOpen>>         Generated just before settings the focus item to
                         open=True.
                         
                         
<<TreeviewClose>>        Generated just after setting the focus item to
                         open=False.
                         

The *note Treeview.focus(): 3d2a. and *note Treeview.selection(): a36.
methods can be used to determine the affected item or items.


File: python.info,  Node: ttk Treeview,  Prev: 虛擬事件<2>,  Up: Treeview

5.25.8.38 ttk.Treeview
......................

 -- 類別: tkinter.ttk.Treeview

      -- 方法: bbox (item, column=None)

          Returns the bounding box (relative to the treeview widget's
          window) of the specified 'item' in the form (x, y, width,
          height).

          If 'column' is specified, returns the bounding box of that
          cell.  If the 'item' is not visible (i.e., if it is a
          descendant of a closed item or is scrolled offscreen), returns
          an empty string.

      -- 方法: get_children (item=None)

          Returns the list of children belonging to 'item'.

          If 'item' is not specified, returns root children.

      -- 方法: set_children (item, *newchildren)

          Replaces 'item"s child with 'newchildren'.

          Children present in 'item' that are not present in
          'newchildren' are detached from the tree.  No items in
          'newchildren' may be an ancestor of 'item'.  Note that not
          specifying 'newchildren' results in detaching 'item"s
          children.

      -- 方法: column (column, option=None, **kw)

          Query or modify the options for the specified 'column'.

          If 'kw' is not given, returns a dict of the column option
          values.  If 'option' is specified then the value for that
          'option' is returned.  Otherwise, sets the options to the
          corresponding values.

          有效的選項/值為：

          'id'

               回傳欄位名稱。這是唯讀選項。

          'anchor': One of the standard Tk anchor values.

               Specifies how the text in this column should be aligned
               with respect to the cell.

          'minwidth': width

               The minimum width of the column in pixels.  The treeview
               widget will not make the column any smaller than
               specified by this option when the widget is resized or
               the user drags a column.

          'stretch': ‘True’/‘False’

               Specifies whether the column's width should be adjusted
               when the widget is resized.

          'width': width

               The width of the column in pixels.

          To configure the tree column, call this with column = "#0"

      -- 方法: delete (*items)

          Delete all specified 'items' and all their descendants.

          The root item may not be deleted.

      -- 方法: detach (*items)

          Unlinks all of the specified 'items' from the tree.

          The items and all of their descendants are still present, and
          may be reinserted at another point in the tree, but will not
          be displayed.

          The root item may not be detached.

      -- 方法: exists (item)

          Returns ‘True’ if the specified 'item' is present in the tree.

      -- 方法: focus (item=None)

          If 'item' is specified, sets the focus item to 'item'.
          Otherwise, returns the current focus item, or '' if there is
          none.

      -- 方法: heading (column, option=None, **kw)

          Query or modify the heading options for the specified
          'column'.

          If 'kw' is not given, returns a dict of the heading option
          values.  If 'option' is specified then the value for that
          'option' is returned.  Otherwise, sets the options to the
          corresponding values.

          有效的選項/值為：

          'text': text

               The text to display in the column heading.

          'image': imageName

               Specifies an image to display to the right of the column
               heading.

          'anchor': anchor

               Specifies how the heading text should be aligned.  One of
               the standard Tk anchor values.

          'command': callback

               A callback to be invoked when the heading label is
               pressed.

          To configure the tree column heading, call this with column =
          "#0".

      -- 方法: identify (component, x, y)

          Returns a description of the specified 'component' under the
          point given by 'x' and 'y', or the empty string if no such
          'component' is present at that position.

      -- 方法: identify_row (y)

          Returns the item ID of the item at position 'y'.

      -- 方法: identify_column (x)

          Returns the data column identifier of the cell at position
          'x'.

          The tree column has ID #0.

      -- 方法: identify_region (x, y)

          Returns one of:

          region          meaning
                          
          -----------------------------------------------------------
                          
          heading         Tree heading area.
                          
                          
          separator       Space between two columns headings.
                          
                          
          tree            The tree area.
                          
                          
          cell            A data cell.
                          

          Availability: Tk 8.6.

      -- 方法: identify_element (x, y)

          Returns the element at position 'x', 'y'.

          Availability: Tk 8.6.

      -- 方法: index (item)

          Returns the integer index of 'item' within its parent's list
          of children.

      -- 方法: insert (parent, index, iid=None, **kw)

          Creates a new item and returns the item identifier of the
          newly created item.

          'parent' is the item ID of the parent item, or the empty
          string to create a new top-level item.  'index' is an integer,
          or the value "end", specifying where in the list of parent's
          children to insert the new item.  If 'index' is less than or
          equal to zero, the new node is inserted at the beginning; if
          'index' is greater than or equal to the current number of
          children, it is inserted at the end.  If 'iid' is specified,
          it is used as the item identifier; 'iid' must not already
          exist in the tree.  Otherwise, a new unique identifier is
          generated.

          可用的選項清單請見 *note Item Options: 3d27.。

      -- 方法: item (item, option=None, **kw)

          Query or modify the options for the specified 'item'.

          If no options are given, a dict with options/values for the
          item is returned.  If 'option' is specified then the value for
          that option is returned.  Otherwise, sets the options to the
          corresponding values as given by 'kw'.

      -- 方法: move (item, parent, index)

          Moves 'item' to position 'index' in 'parent"s list of
          children.

          It is illegal to move an item under one of its descendants.
          If 'index' is less than or equal to zero, 'item' is moved to
          the beginning; if greater than or equal to the number of
          children, it is moved to the end.  If 'item' was detached it
          is reattached.

      -- 方法: next (item)

          Returns the identifier of 'item"s next sibling, or '' if
          'item' is the last child of its parent.

      -- 方法: parent (item)

          Returns the ID of the parent of 'item', or '' if 'item' is at
          the top level of the hierarchy.

      -- 方法: prev (item)

          Returns the identifier of 'item"s previous sibling, or '' if
          'item' is the first child of its parent.

      -- 方法: reattach (item, parent, index)

          一個 *note Treeview.move(): 3d3c. 的別名。

      -- 方法: see (item)

          確保 'item' 是可見的。

          Sets all of 'item"s ancestors open option to ‘True’, and
          scrolls the widget if necessary so that 'item' is within the
          visible portion of the tree.

      -- 方法: selection ()

          Returns a tuple of selected items.

          在 3.8 版的變更: ‘selection()’ no longer takes arguments.  For
          changing the selection state use the following selection
          methods.

      -- 方法: selection_set (*items)

          'items' becomes the new selection.

          在 3.6 版的變更: 'items' can be passed as separate arguments,
          not just as a single tuple.

      -- 方法: selection_add (*items)

          將 'items' 加入選擇。

          在 3.6 版的變更: 'items' can be passed as separate arguments,
          not just as a single tuple.

      -- 方法: selection_remove (*items)

          從選擇中移除 'items'。

          在 3.6 版的變更: 'items' can be passed as separate arguments,
          not just as a single tuple.

      -- 方法: selection_toggle (*items)

          Toggle the selection state of each item in 'items'.

          在 3.6 版的變更: 'items' can be passed as separate arguments,
          not just as a single tuple.

      -- 方法: set (item, column=None, value=None)

          With one argument, returns a dictionary of column/value pairs
          for the specified 'item'.  With two arguments, returns the
          current value of the specified 'column'.  With three
          arguments, sets the value of given 'column' in given 'item' to
          the specified 'value'.

      -- 方法: tag_bind (tagname, sequence=None, callback=None)

          Bind a callback for the given event 'sequence' to the tag
          'tagname'.  When an event is delivered to an item, the
          callbacks for each of the item's tags option are called.

      -- 方法: tag_configure (tagname, option=None, **kw)

          Query or modify the options for the specified 'tagname'.

          If 'kw' is not given, returns a dict of the option settings
          for 'tagname'.  If 'option' is specified, returns the value
          for that 'option' for the specified 'tagname'.  Otherwise,
          sets the options to the corresponding values for the given
          'tagname'.

      -- 方法: tag_has (tagname, item=None)

          If 'item' is specified, returns 1 or 0 depending on whether
          the specified 'item' has the given 'tagname'.  Otherwise,
          returns a list of all items that have the specified tag.

          Availability: Tk 8.6

      -- 方法: xview (*args)

          Query or modify horizontal position of the treeview.

      -- 方法: yview (*args)

          Query or modify vertical position of the treeview.


File: python.info,  Node: Ttk Styling,  Prev: Treeview,  Up: tkinter ttk --- Tk 主題化小工具

5.25.8.39 Ttk Styling
.....................

Each widget in ‘ttk’ is assigned a style, which specifies the set of
elements making up the widget and how they are arranged, along with
dynamic and default settings for element options.  By default the style
name is the same as the widget's class name, but it may be overridden by
the widget's style option.  If you don't know the class name of a
widget, use the method ‘Misc.winfo_class()’ (somewidget.winfo_class()).

也參考
......

Tcl'2004 conference presentation(1)

     This document explains how the theme engine works

 -- 類別: tkinter.ttk.Style

     This class is used to manipulate the style database.

      -- 方法: configure (style, query_opt=None, **kw)

          Query or set the default value of the specified option(s) in
          'style'.

          Each key in 'kw' is an option and each value is a string
          identifying the value for that option.

          For example, to change every default button to be a flat
          button with some padding and a different background color:

               from tkinter import ttk
               import tkinter

               root = tkinter.Tk()

               ttk.Style().configure("TButton", padding=6, relief="flat",
                  background="#ccc")

               btn = ttk.Button(text="Sample")
               btn.pack()

               root.mainloop()

      -- 方法: map (style, query_opt=None, **kw)

          Query or sets dynamic values of the specified option(s) in
          'style'.

          Each key in 'kw' is an option and each value should be a list
          or a tuple (usually) containing statespecs grouped in tuples,
          lists, or some other preference.  A statespec is a compound of
          one or more states and then a value.

          An example may make it more understandable:

               import tkinter
               from tkinter import ttk

               root = tkinter.Tk()

               style = ttk.Style()
               style.map("C.TButton",
                   foreground=[('pressed', 'red'), ('active', 'blue')],
                   background=[('pressed', '!disabled', 'black'), ('active', 'white')]
                   )

               colored_btn = ttk.Button(text="Test", style="C.TButton").pack()

               root.mainloop()

          Note that the order of the (states, value) sequences for an
          option does matter, if the order is changed to ‘[('active',
          'blue'), ('pressed', 'red')]’ in the foreground option, for
          example, the result would be a blue foreground when the widget
          were in active or pressed states.

      -- 方法: lookup (style, option, state=None, default=None)

          Returns the value specified for 'option' in 'style'.

          If 'state' is specified, it is expected to be a sequence of
          one or more states.  If the 'default' argument is set, it is
          used as a fallback value in case no specification for option
          is found.

          To check what font a Button uses by default:

               from tkinter import ttk

               print(ttk.Style().lookup("TButton", "font"))

      -- 方法: layout (style, layoutspec=None)

          Define the widget layout for given 'style'.  If 'layoutspec'
          is omitted, return the layout specification for given style.

          'layoutspec', if specified, is expected to be a list or some
          other sequence type (excluding strings), where each item
          should be a tuple and the first item is the layout name and
          the second item should have the format described in *note
          Layouts: 3d4d.

          To understand the format, see the following example (it is not
          intended to do anything useful):

               from tkinter import ttk
               import tkinter

               root = tkinter.Tk()

               style = ttk.Style()
               style.layout("TMenubutton", [
                  ("Menubutton.background", None),
                  ("Menubutton.button", {"children":
                      [("Menubutton.focus", {"children":
                          [("Menubutton.padding", {"children":
                              [("Menubutton.label", {"side": "left", "expand": 1})]
                          })]
                      })]
                  }),
               ])

               mbtn = ttk.Menubutton(text='Text')
               mbtn.pack()
               root.mainloop()

      -- 方法: element_create (elementname, etype, *args, **kw)

          Create a new element in the current theme, of the given
          'etype' which is expected to be either "image", "from" or
          "vsapi".  The latter is only available in Tk 8.6 on Windows.

          If "image" is used, 'args' should contain the default image
          name followed by statespec/value pairs (this is the
          imagespec), and 'kw' may have the following options:

          border=padding

               padding is a list of up to four integers, specifying the
               left, top, right, and bottom borders, respectively.

          height=height

               Specifies a minimum height for the element.  If less than
               zero, the base image's height is used as a default.

          padding=padding

               Specifies the element's interior padding.  Defaults to
               border's value if not specified.

          sticky=spec

               Specifies how the image is placed within the final
               parcel.  spec contains zero or more characters "n", "s",
               "w", or "e".

          width=width

               Specifies a minimum width for the element.  If less than
               zero, the base image's width is used as a default.

          範例：

               img1 = tkinter.PhotoImage(master=root, file='button.png')
               img1 = tkinter.PhotoImage(master=root, file='button-pressed.png')
               img1 = tkinter.PhotoImage(master=root, file='button-active.png')
               style = ttk.Style(root)
               style.element_create('Button.button', 'image',
                                    img1, ('pressed', img2), ('active', img3),
                                    border=(2, 4), sticky='we')

          If "from" is used as the value of 'etype', *note
          element_create(): 23d. will clone an existing element.  'args'
          is expected to contain a themename, from which the element
          will be cloned, and optionally an element to clone from.  If
          this element to clone from is not specified, an empty element
          will be used.  'kw' is discarded.

          範例：

               style = ttk.Style(root)
               style.element_create('plain.background', 'from', 'default')

          If "vsapi" is used as the value of 'etype', *note
          element_create(): 23d. will create a new element in the
          current theme whose visual appearance is drawn using the
          Microsoft Visual Styles API which is responsible for the
          themed styles on Windows XP and Vista.  'args' is expected to
          contain the Visual Styles class and part as given in the
          Microsoft documentation followed by an optional sequence of
          tuples of ttk states and the corresponding Visual Styles API
          state value.  'kw' may have the following options:

          padding=padding

               Specify the element's interior padding.  'padding' is a
               list of up to four integers specifying the left, top,
               right and bottom padding quantities respectively.  If
               fewer than four elements are specified, bottom defaults
               to top, right defaults to left, and top defaults to left.
               In other words, a list of three numbers specify the left,
               vertical, and right padding; a list of two numbers
               specify the horizontal and the vertical padding; a single
               number specifies the same padding all the way around the
               widget.  This option may not be mixed with any other
               options.

          margins=padding

               Specifies the elements exterior padding.  'padding' is a
               list of up to four integers specifying the left, top,
               right and bottom padding quantities respectively.  This
               option may not be mixed with any other options.

          width=width

               Specifies the width for the element.  If this option is
               set then the Visual Styles API will not be queried for
               the recommended size or the part.  If this option is set
               then 'height' should also be set.  The 'width' and
               'height' options cannot be mixed with the 'padding' or
               'margins' options.

          height=height

               Specifies the height of the element.  See the comments
               for 'width'.

          範例：

               style = ttk.Style(root)
               style.element_create('pin', 'vsapi', 'EXPLORERBAR', 3, [
                                    ('pressed', '!selected', 3),
                                    ('active', '!selected', 2),
                                    ('pressed', 'selected', 6),
                                    ('active', 'selected', 5),
                                    ('selected', 4),
                                    ('', 1)])
               style.layout('Explorer.Pin',
                            [('Explorer.Pin.pin', {'sticky': 'news'})])
               pin = ttk.Checkbutton(style='Explorer.Pin')
               pin.pack(expand=True, fill='both')

          在 3.13 版的變更: Added support of the "vsapi" element
          factory.

      -- 方法: element_names ()

          Returns the list of elements defined in the current theme.

      -- 方法: element_options (elementname)

          Returns the list of 'elementname"s options.

      -- 方法: theme_create (themename, parent=None, settings=None)

          Create a new theme.

          It is an error if 'themename' already exists.  If 'parent' is
          specified, the new theme will inherit styles, elements and
          layouts from the parent theme.  If 'settings' are present they
          are expected to have the same syntax used for *note
          theme_settings(): 3d51.

      -- 方法: theme_settings (themename, settings)

          Temporarily sets the current theme to 'themename', apply
          specified 'settings' and then restore the previous theme.

          Each key in 'settings' is a style and each value may contain
          the keys 'configure', 'map', 'layout' and 'element create' and
          they are expected to have the same format as specified by the
          methods *note Style.configure(): 3d4a, *note Style.map():
          1820, *note Style.layout(): 3d4c. and *note
          Style.element_create(): 23d. respectively.

          As an example, let's change the Combobox for the default theme
          a bit:

               from tkinter import ttk
               import tkinter

               root = tkinter.Tk()

               style = ttk.Style()
               style.theme_settings("default", {
                  "TCombobox": {
                      "configure": {"padding": 5},
                      "map": {
                          "background": [("active", "green2"),
                                         ("!disabled", "green4")],
                          "fieldbackground": [("!disabled", "green3")],
                          "foreground": [("focus", "OliveDrab1"),
                                         ("!disabled", "OliveDrab2")]
                      }
                  }
               })

               combo = ttk.Combobox().pack()

               root.mainloop()

      -- 方法: theme_names ()

          回傳所有已知的主題。

      -- 方法: theme_use (themename=None)

          If 'themename' is not given, returns the theme in use.
          Otherwise, sets the current theme to 'themename', refreshes
          all widgets and emits a <<ThemeChanged>> event.

* Menu:

* Layouts::

   ---------- Footnotes ----------

   (1) https://tktable.sourceforge.net/tile/tile-tcl2004.pdf


File: python.info,  Node: Layouts,  Up: Ttk Styling

5.25.8.40 Layouts
.................

A layout can be just ‘None’, if it takes no options, or a dict of
options specifying how to arrange the element.  The layout mechanism
uses a simplified version of the pack geometry manager: given an initial
cavity, each element is allocated a parcel.

有效的選項/值為：

'side': whichside

     Specifies which side of the cavity to place the element; one of
     top, right, bottom or left.  If omitted, the element occupies the
     entire cavity.

'sticky': nswe

     Specifies where the element is placed inside its allocated parcel.

'unit'：0 或 1

     If set to 1, causes the element and all of its descendants to be
     treated as a single element for the purposes of *note
     Widget.identify(): 3cf8. et al.  It's used for things like
     scrollbar thumbs with grips.

'children': [sublayout... ]

     Specifies a list of elements to place inside the element.  Each
     element is a tuple (or other sequence type) where the first item is
     the layout name, and the other is a *note Layout: 3d4d.


File: python.info,  Node: IDLE<62>,  Prev: tkinter ttk --- Tk 主題化小工具,  Up: 以 Tk 打造圖形使用者介面 Graphical User Interfaces

5.25.9 IDLE
-----------

'原始碼：'Lib/idlelib/(1)

__________________________________________________________________

IDLE is Python's Integrated Development and Learning Environment.

IDLE has the following features:

   * cross-platform: works mostly the same on Windows, Unix, and macOS

   * Python shell window (interactive interpreter) with colorizing of
     code input, output, and error messages

   * multi-window text editor with multiple undo, Python colorizing,
     smart indent, call tips, auto completion, and other features

   * search within any window, replace within editor windows, and search
     through multiple files (grep)

   * debugger with persistent breakpoints, stepping, and viewing of
     global and local namespaces

   * configuration, browsers, and other dialogs

* Menu:

* 目錄::
* Editing and Navigation::
* Startup and Code Execution::
* Help and Preferences::
* idlelib::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/idlelib/


File: python.info,  Node: 目錄,  Next: Editing and Navigation,  Up: IDLE<62>

5.25.9.1 目錄
.............

IDLE has two main window types, the Shell window and the Editor window.
It is possible to have multiple editor windows simultaneously.  On
Windows and Linux, each has its own top menu.  Each menu documented
below indicates which window type it is associated with.

Output windows, such as used for Edit => Find in Files, are a subtype of
editor window.  They currently have the same top menu but a different
default title and context menu.

On macOS, there is one application menu.  It dynamically changes
according to the window currently selected.  It has an IDLE menu, and
some entries described below are moved around to conform to Apple
guidelines.

* Menu:

* File menu (Shell and Editor): File menu Shell and Editor.
* Edit menu (Shell and Editor): Edit menu Shell and Editor.
* Format menu (Editor window only): Format menu Editor window only.
* Run menu (Editor window only): Run menu Editor window only.
* Shell menu (Shell window only): Shell menu Shell window only.
* Debug menu (Shell window only): Debug menu Shell window only.
* Options menu (Shell and Editor): Options menu Shell and Editor.
* Window menu (Shell and Editor): Window menu Shell and Editor.
* Help menu (Shell and Editor): Help menu Shell and Editor.
* Context menus::


File: python.info,  Node: File menu Shell and Editor,  Next: Edit menu Shell and Editor,  Up: 目錄

5.25.9.2 File menu (Shell and Editor)
.....................................

新增檔案

     Create a new file editing window.

Open...

     Open an existing file with an Open dialog.

Open Module...

     Open an existing module (searches sys.path).

Recent Files

     Open a list of recent files.  Click one to open it.

Module Browser

     Show functions, classes, and methods in the current Editor file in
     a tree structure.  In the shell, open a module first.

Path Browser

     Show sys.path directories, modules, functions, classes and methods
     in a tree structure.

Save

     Save the current window to the associated file, if there is one.
     Windows that have been changed since being opened or last saved
     have a * before and after the window title.  If there is no
     associated file, do Save As instead.

Save As...

     Save the current window with a Save As dialog.  The file saved
     becomes the new associated file for the window.  (If your file
     namager is set to hide extensions, the current extension will be
     omitted in the file name box.  If the new filename has no '.',
     '.py' and '.txt' will be added for Python and text files, except
     that on macOS Aqua,'.py' is added for all files.)

Save Copy As...

     Save the current window to different file without changing the
     associated file.  (See Save As note above about filename
     extensions.)

Print Window

     Print the current window to the default printer.

Close Window

     Close the current window (if an unsaved editor, ask to save; if an
     unsaved Shell, ask to quit execution).  Calling ‘exit()’ or
     ‘close()’ in the Shell window also closes Shell.  If this is the
     only window, also exit IDLE.

離開 IDLE

     Close all windows and quit IDLE (ask to save unsaved edit windows).


File: python.info,  Node: Edit menu Shell and Editor,  Next: Format menu Editor window only,  Prev: File menu Shell and Editor,  Up: 目錄

5.25.9.3 Edit menu (Shell and Editor)
.....................................

Undo

     Undo the last change to the current window.  A maximum of 1000
     changes may be undone.

Redo

     Redo the last undone change to the current window.

Select All（選擇全部）

     Select the entire contents of the current window.

Cut（剪下）

     Copy selection into the system-wide clipboard; then delete the
     selection.

Copy（複製）

     Copy selection into the system-wide clipboard.

Paste（貼上）

     Insert contents of the system-wide clipboard into the current
     window.

The clipboard functions are also available in context menus.

Find...

     Open a search dialog with many options

Find Again

     Repeat the last search, if there is one.

Find Selection

     Search for the currently selected string, if there is one.

Find in Files...

     Open a file search dialog.  Put results in a new output window.

Replace...

     Open a search-and-replace dialog.

Go to Line

     Move the cursor to the beginning of the line requested and make
     that line visible.  A request past the end of the file goes to the
     end.  Clear any selection and update the line and column status.

Show Completions

     Open a scrollable list allowing selection of existing names.  See
     *note Completions: 3d5a. in the Editing and navigation section
     below.

Expand Word

     Expand a prefix you have typed to match a full word in the same
     window; repeat to get a different expansion.

Show Call Tip

     After an unclosed parenthesis for a function, open a small window
     with function parameter hints.  See *note Calltips: 3d5b. in the
     Editing and navigation section below.

Show Surrounding Parens

     Highlight the surrounding parenthesis.


File: python.info,  Node: Format menu Editor window only,  Next: Run menu Editor window only,  Prev: Edit menu Shell and Editor,  Up: 目錄

5.25.9.4 Format menu (Editor window only)
.........................................

Format Paragraph

     Reformat the current blank-line-delimited paragraph in comment
     block or multiline string or selected line in a string.  All lines
     in the paragraph will be formatted to less than N columns, where N
     defaults to 72.

Indent Region

     Shift selected lines right by the indent width (default 4 spaces).

Dedent Region

     Shift selected lines left by the indent width (default 4 spaces).

Comment Out Region

     Insert ## in front of selected lines.

Uncomment Region

     Remove leading # or ## from selected lines.

Tabify Region

     Turn 'leading' stretches of spaces into tabs.  (Note: We recommend
     using 4 space blocks to indent Python code.)

Untabify Region

     Turn 'all' tabs into the correct number of spaces.

Toggle Tabs

     Open a dialog to switch between indenting with spaces and tabs.

New Indent Width

     Open a dialog to change indent width.  The accepted default by the
     Python community is 4 spaces.

Strip Trailing Chitespace

     Remove trailing space and other whitespace characters after the
     last non-whitespace character of a line by applying str.rstrip to
     each line, including lines within multiline strings.  Except for
     Shell windows, remove extra newlines at the end of the file.


File: python.info,  Node: Run menu Editor window only,  Next: Shell menu Shell window only,  Prev: Format menu Editor window only,  Up: 目錄

5.25.9.5 Run menu (Editor window only)
......................................

Run Module

     Do *note Check Module: 3d60.  If no error, restart the shell to
     clean the environment, then execute the module.  Output is
     displayed in the Shell window.  Note that output requires use of
     ‘print’ or ‘write’.  When execution is complete, the Shell retains
     focus and displays a prompt.  At this point, one may interactively
     explore the result of execution.  This is similar to executing a
     file with ‘python -i file’ at a command line.

Run... Customized

     Same as *note Run Module: 3d5f, but run the module with customized
     settings.  'Command Line Arguments' extend *note sys.argv: 11fd. as
     if passed on a command line.  The module can be run in the Shell
     without restarting.

Check Module

     Check the syntax of the module currently open in the Editor window.
     If the module has not been saved IDLE will either prompt the user
     to save or autosave, as selected in the General tab of the Idle
     Settings dialog.  If there is a syntax error, the approximate
     location is indicated in the Editor window.

Python Shell

     Open or wake up the Python Shell window.


File: python.info,  Node: Shell menu Shell window only,  Next: Debug menu Shell window only,  Prev: Run menu Editor window only,  Up: 目錄

5.25.9.6 Shell menu (Shell window only)
.......................................

View Last Restart

     Scroll the shell window to the last Shell restart.

Restart Shell

     Restart the shell to clean the environment and reset display and
     exception handling.

Previous History

     Cycle through earlier commands in history which match the current
     entry.

Next History

     Cycle through later commands in history which match the current
     entry.

Interrupt Execution

     Stop a running program.


File: python.info,  Node: Debug menu Shell window only,  Next: Options menu Shell and Editor,  Prev: Shell menu Shell window only,  Up: 目錄

5.25.9.7 Debug menu (Shell window only)
.......................................

Go to File/Line

     Look on the current line.  with the cursor, and the line above for
     a filename and line number.  If found, open the file if not already
     open, and show the line.  Use this to view source lines referenced
     in an exception traceback and lines found by Find in Files.  Also
     available in the context menu of the Shell window and Output
     windows.

Debugger (toggle)

     When activated, code entered in the Shell or run from an Editor
     will run under the debugger.  In the Editor, breakpoints can be set
     with the context menu.  This feature is still incomplete and
     somewhat experimental.

Stack Viewer

     Show the stack traceback of the last exception in a tree widget,
     with access to locals and globals.

Auto-open Stack Viewer

     Toggle automatically opening the stack viewer on an unhandled
     exception.


File: python.info,  Node: Options menu Shell and Editor,  Next: Window menu Shell and Editor,  Prev: Debug menu Shell window only,  Up: 目錄

5.25.9.8 Options menu (Shell and Editor)
........................................

Configure IDLE

     Open a configuration dialog and change preferences for the
     following: fonts, indentation, keybindings, text color themes,
     startup windows and size, additional help sources, and extensions.
     On macOS, open the configuration dialog by selecting Preferences in
     the application menu.  For more details, see *note Setting
     preferences: 3d66. under Help and preferences.

Most configuration options apply to all windows or all future windows.
The option items below only apply to the active window.

Show/Hide Code Context (Editor Window only)

     Open a pane at the top of the edit window which shows the block
     context of the code which has scrolled above the top of the window.
     See *note Code Context: 3d67. in the Editing and Navigation section
     below.

Show/Hide Line Numbers (Editor Window only)

     Open a column to the left of the edit window which shows the number
     of each line of text.  The default is off, which may be changed in
     the preferences (see *note Setting preferences: 3d66.).

Zoom/Restore Height

     Toggles the window between normal size and maximum height.  The
     initial size defaults to 40 lines by 80 chars unless changed on the
     General tab of the Configure IDLE dialog.  The maximum height for a
     screen is determined by momentarily maximizing a window the first
     time one is zoomed on the screen.  Changing screen settings may
     invalidate the saved height.  This toggle has no effect when a
     window is maximized.


File: python.info,  Node: Window menu Shell and Editor,  Next: Help menu Shell and Editor,  Prev: Options menu Shell and Editor,  Up: 目錄

5.25.9.9 Window menu (Shell and Editor)
.......................................

Lists the names of all open windows; select one to bring it to the
foreground (deiconifying it if necessary).


File: python.info,  Node: Help menu Shell and Editor,  Next: Context menus,  Prev: Window menu Shell and Editor,  Up: 目錄

5.25.9.10 Help menu (Shell and Editor)
......................................

About IDLE

     Display version, copyright, license, credits, and more.

IDLE Help

     Display this IDLE document, detailing the menu options, basic
     editing and navigation, and other tips.

Python Docs

     Access local Python documentation, if installed, or start a web
     browser and open docs.python.org showing the latest Python
     documentation.

Turtle Demo

     Run the turtledemo module with example Python code and turtle
     drawings.

Additional help sources may be added here with the Configure IDLE dialog
under the General tab.  See the *note Help sources: 3d6a. subsection
below for more on Help menu choices.


File: python.info,  Node: Context menus,  Prev: Help menu Shell and Editor,  Up: 目錄

5.25.9.11 Context menus
.......................

Open a context menu by right-clicking in a window (Control-click on
macOS). Context menus have the standard clipboard functions also on the
Edit menu.

Cut（剪下）

     Copy selection into the system-wide clipboard; then delete the
     selection.

Copy（複製）

     Copy selection into the system-wide clipboard.

Paste（貼上）

     Insert contents of the system-wide clipboard into the current
     window.

Editor windows also have breakpoint functions.  Lines with a breakpoint
set are specially marked.  Breakpoints only have an effect when running
under the debugger.  Breakpoints for a file are saved in the user's
‘.idlerc’ directory.

Set Breakpoint

     Set a breakpoint on the current line.

Clear Breakpoint

     Clear the breakpoint on that line.

Shell and Output windows also have the following.

Go to file/line

     Same as in Debug menu.

The Shell window also has an output squeezing facility explained in the
'Python Shell window' subsection below.

Squeeze

     If the cursor is over an output line, squeeze all the output
     between the code above and the prompt below down to a 'Squeezed
     text' label.


File: python.info,  Node: Editing and Navigation,  Next: Startup and Code Execution,  Prev: 目錄,  Up: IDLE<62>

5.25.9.12 Editing and Navigation
................................

* Menu:

* Editor windows::
* Key bindings::
* Automatic indentation::
* Search and Replace::
* Completions::
* Calltips::
* Code Context::
* Shell window::
* Text colors::


File: python.info,  Node: Editor windows,  Next: Key bindings,  Up: Editing and Navigation

5.25.9.13 Editor windows
........................

IDLE may open editor windows when it starts, depending on settings and
how you start IDLE. Thereafter, use the File menu.  There can be only
one open editor window for a given file.

The title bar contains the name of the file, the full path, and the
version of Python and IDLE running the window.  The status bar contains
the line number ('Ln') and column number ('Col').  Line numbers start
with 1; column numbers with 0.

IDLE assumes that files with a known .py* extension contain Python code
and that other files do not.  Run Python code with the Run menu.


File: python.info,  Node: Key bindings,  Next: Automatic indentation,  Prev: Editor windows,  Up: Editing and Navigation

5.25.9.14 Key bindings
......................

The IDLE insertion cursor is a thin vertical bar between character
positions.  When characters are entered, the insertion cursor and
everything to its right moves right one character and the new character
is entered in the new space.

Several non-character keys move the cursor and possibly delete
characters.  Deletion does not puts text on the clipboard, but IDLE has
an undo list.  Wherever this doc discusses keys, 'C' refers to the
‘Control’ key on Windows and Unix and the ‘Command’ key on macOS. (And
all such discussions assume that the keys have not been re-bound to
something else.)

   * Arrow keys move the cursor one character or line.

   * ‘C-LeftArrow’ and ‘C-RightArrow’ moves left or right one word.

   * ‘Home’ and ‘End’ go to the beginning or end of the line.

   * ‘Page Up’ and ‘Page Down’ go up or down one screen.

   * ‘C-Home’ and ‘C-End’ go to beginning or end of the file.

   * ‘Backspace’ and ‘Del’ (or ‘C-d’) delete the previous or next
     character.

   * ‘C-Backspace’ and ‘C-Del’ delete one word left or right.

   * ‘C-k’ deletes ('kills') everything to the right.

Standard keybindings (like ‘C-c’ to copy and ‘C-v’ to paste) may work.
Keybindings are selected in the Configure IDLE dialog.


File: python.info,  Node: Automatic indentation,  Next: Search and Replace,  Prev: Key bindings,  Up: Editing and Navigation

5.25.9.15 Automatic indentation
...............................

After a block-opening statement, the next line is indented by 4 spaces
(in the Python Shell window by one tab).  After certain keywords (break,
return etc.)  the next line is dedented.  In leading indentation,
‘Backspace’ deletes up to 4 spaces if they are there.  ‘Tab’ inserts
spaces (in the Python Shell window one tab), number depends on Indent
width.  Currently, tabs are restricted to four spaces due to Tcl/Tk
limitations.

See also the indent/dedent region commands on the *note Format menu:
3d5c.


File: python.info,  Node: Search and Replace,  Next: Completions,  Prev: Automatic indentation,  Up: Editing and Navigation

5.25.9.16 Search and Replace
............................

Any selection becomes a search target.  However, only selections within
a line work because searches are only performed within lines with the
terminal newline removed.  If ‘[x] Regular expression’ is checked, the
target is interpreted according to the Python re module.


File: python.info,  Node: Completions,  Next: Calltips,  Prev: Search and Replace,  Up: Editing and Navigation

5.25.9.17 Completions
.....................

Completions are supplied, when requested and available, for module
names, attributes of classes or functions, or filenames.  Each request
method displays a completion box with existing names.  (See tab
completions below for an exception.)  For any box, change the name being
completed and the item highlighted in the box by typing and deleting
characters; by hitting ‘Up’, ‘Down’, ‘PageUp’, ‘PageDown’, ‘Home’, and
‘End’ keys; and by a single click within the box.  Close the box with
‘Escape’, ‘Enter’, and double ‘Tab’ keys or clicks outside the box.  A
double click within the box selects and closes.

One way to open a box is to type a key character and wait for a
predefined interval.  This defaults to 2 seconds; customize it in the
settings dialog.  (To prevent auto popups, set the delay to a large
number of milliseconds, such as 100000000.)  For imported module names
or class or function attributes, type '.'.  For filenames in the root
directory, type *note os.sep: 610. or *note os.altsep: 611. immediately
after an opening quote.  (On Windows, one can specify a drive first.)
Move into subdirectories by typing a directory name and a separator.

Instead of waiting, or after a box is closed, open a completion box
immediately with Show Completions on the Edit menu.  The default hot key
is ‘C-space’.  If one types a prefix for the desired name before opening
the box, the first match or near miss is made visible.  The result is
the same as if one enters a prefix after the box is displayed.  Show
Completions after a quote completes filenames in the current directory
instead of a root directory.

Hitting ‘Tab’ after a prefix usually has the same effect as Show
Completions.  (With no prefix, it indents.)  However, if there is only
one match to the prefix, that match is immediately added to the editor
text without opening a box.

Invoking 'Show Completions', or hitting ‘Tab’ after a prefix, outside of
a string and without a preceding '.'  opens a box with keywords, builtin
names, and available module-level names.

When editing code in an editor (as oppose to Shell), increase the
available module-level names by running your code and not restarting the
Shell thereafter.  This is especially useful after adding imports at the
top of a file.  This also increases possible attribute completions.

Completion boxes initially exclude names beginning with '_' or, for
modules, not included in '__all__'.  The hidden names can be accessed by
typing '_' after '.', either before or after the box is opened.


File: python.info,  Node: Calltips,  Next: Code Context,  Prev: Completions,  Up: Editing and Navigation

5.25.9.18 Calltips
..................

A calltip is shown automatically when one types ‘(’ after the name of an
'accessible' function.  A function name expression may include dots and
subscripts.  A calltip remains until it is clicked, the cursor is moved
out of the argument area, or ‘)’ is typed.  Whenever the cursor is in
the argument part of a definition, select Edit and "Show Call Tip" on
the menu or enter its shortcut to display a calltip.

The calltip consists of the function's signature and docstring up to the
latter's first blank line or the fifth non-blank line.  (Some builtin
functions lack an accessible signature.)  A '/' or '*' in the signature
indicates that the preceding or following arguments are passed by
position or name (keyword) only.  Details are subject to change.

In Shell, the accessible functions depends on what modules have been
imported into the user process, including those imported by Idle itself,
and which definitions have been run, all since the last restart.

For example, restart the Shell and enter ‘itertools.count(’.  A calltip
appears because Idle imports itertools into the user process for its own
use.  (This could change.)  Enter ‘turtle.write(’ and nothing appears.
Idle does not itself import turtle.  The menu entry and shortcut also do
nothing.  Enter ‘import turtle’.  Thereafter, ‘turtle.write(’ will
display a calltip.

In an editor, import statements have no effect until one runs the file.
One might want to run a file after writing import statements, after
adding function definitions, or after opening an existing file.


File: python.info,  Node: Code Context,  Next: Shell window,  Prev: Calltips,  Up: Editing and Navigation

5.25.9.19 Code Context
......................

Within an editor window containing Python code, code context can be
toggled in order to show or hide a pane at the top of the window.  When
shown, this pane freezes the opening lines for block code, such as those
beginning with ‘class’, ‘def’, or ‘if’ keywords, that would have
otherwise scrolled out of view.  The size of the pane will be expanded
and contracted as needed to show the all current levels of context, up
to the maximum number of lines defined in the Configure IDLE dialog
(which defaults to 15).  If there are no current context lines and the
feature is toggled on, a single blank line will display.  Clicking on a
line in the context pane will move that line to the top of the editor.

The text and background colors for the context pane can be configured
under the Highlights tab in the Configure IDLE dialog.


File: python.info,  Node: Shell window,  Next: Text colors,  Prev: Code Context,  Up: Editing and Navigation

5.25.9.20 Shell window
......................

In IDLE's Shell, enter, edit, and recall complete statements.  (Most
consoles and terminals only work with a single physical line at a time).

Submit a single-line statement for execution by hitting ‘Return’ with
the cursor anywhere on the line.  If a line is extended with Backslash
(‘\’), the cursor must be on the last physical line.  Submit a
multi-line compound statement by entering a blank line after the
statement.

When one pastes code into Shell, it is not compiled and possibly
executed until one hits ‘Return’, as specified above.  One may edit
pasted code first.  If one pastes more than one statement into Shell,
the result will be a *note SyntaxError: 173. when multiple statements
are compiled as if they were one.

Lines containing ‘RESTART’ mean that the user execution process has been
re-started.  This occurs when the user execution process has crashed,
when one requests a restart on the Shell menu, or when one runs code in
an editor window.

The editing features described in previous subsections work when
entering code interactively.  IDLE's Shell window also responds to the
following:

   * ‘C-c’ attempts to interrupt statement execution (but may fail).

   * ‘C-d’ closes Shell if typed at a ‘>>>’ prompt.

   * ‘Alt-p’ and ‘Alt-n’ (‘C-p’ and ‘C-n’ on macOS) retrieve to the
     current prompt the previous or next previously entered statement
     that matches anything already typed.

   * ‘Return’ while the cursor is on any previous statement appends the
     latter to anything already typed at the prompt.


File: python.info,  Node: Text colors,  Prev: Shell window,  Up: Editing and Navigation

5.25.9.21 Text colors
.....................

Idle defaults to black on white text, but colors text with special
meanings.  For the shell, these are shell output, shell error, user
output, and user error.  For Python code, at the shell prompt or in an
editor, these are keywords, builtin class and function names, names
following ‘class’ and ‘def’, strings, and comments.  For any text
window, these are the cursor (when present), found text (when possible),
and selected text.

IDLE also highlights the *note soft keywords: 7b0. *note match: 7b1,
*note case: 7b1, and *note _: 7b2. in pattern-matching statements.
However, this highlighting is not perfect and will be incorrect in some
rare cases, including some ‘_’-s in ‘case’ patterns.

Text coloring is done in the background, so uncolorized text is
occasionally visible.  To change the color scheme, use the Configure
IDLE dialog Highlighting tab.  The marking of debugger breakpoint lines
in the editor and text in popups and dialogs is not user-configurable.


File: python.info,  Node: Startup and Code Execution,  Next: Help and Preferences,  Prev: Editing and Navigation,  Up: IDLE<62>

5.25.9.22 Startup and Code Execution
....................................

Upon startup with the ‘-s’ option, IDLE will execute the file referenced
by the environment variables ‘IDLESTARTUP’ or *note PYTHONSTARTUP: f6b.
IDLE first checks for ‘IDLESTARTUP’; if ‘IDLESTARTUP’ is present the
file referenced is run.  If ‘IDLESTARTUP’ is not present, IDLE checks
for ‘PYTHONSTARTUP’.  Files referenced by these environment variables
are convenient places to store functions that are used frequently from
the IDLE shell, or for executing import statements to import common
modules.

In addition, ‘Tk’ also loads a startup file if it is present.  Note that
the Tk file is loaded unconditionally.  This additional file is
‘.Idle.py’ and is looked for in the user's home directory.  Statements
in this file will be executed in the Tk namespace, so this file is not
useful for importing functions to be used from IDLE's Python shell.

* Menu:

* 命令列用法: 命令列用法<2>.
* Startup failure::
* Running user code::
* User output in Shell::
* Developing tkinter applications::
* Running without a subprocess::


File: python.info,  Node: 命令列用法<2>,  Next: Startup failure,  Up: Startup and Code Execution

5.25.9.23 命令列用法
....................

     idle.py [-c command] [-d] [-e] [-h] [-i] [-r file] [-s] [-t title] [-] [arg] ...

     -c command  run command in the shell window
     -d          enable debugger and open shell window
     -e          open editor window
     -h          print help message with legal combinations and exit
     -i          open shell window
     -r file     run file in shell window
     -s          run $IDLESTARTUP or $PYTHONSTARTUP first, in shell window
     -t title    set title of shell window
     -           run stdin in shell (- must be last option before args)

If there are arguments:

   * If ‘-’, ‘-c’, or ‘r’ is used, all arguments are placed in
     ‘sys.argv[1:...]’ and ‘sys.argv[0]’ is set to ‘''’, ‘'-c'’, or
     ‘'-r'’.  No editor window is opened, even if that is the default
     set in the Options dialog.

   * Otherwise, arguments are files opened for editing and ‘sys.argv’
     reflects the arguments passed to IDLE itself.


File: python.info,  Node: Startup failure,  Next: Running user code,  Prev: 命令列用法<2>,  Up: Startup and Code Execution

5.25.9.24 Startup failure
.........................

IDLE uses a socket to communicate between the IDLE GUI process and the
user code execution process.  A connection must be established whenever
the Shell starts or restarts.  (The latter is indicated by a divider
line that says 'RESTART'). If the user process fails to connect to the
GUI process, it usually displays a ‘Tk’ error box with a 'cannot
connect' message that directs the user here.  It then exits.

One specific connection failure on Unix systems results from
misconfigured masquerading rules somewhere in a system's network setup.
When IDLE is started from a terminal, one will see a message starting
with ‘** Invalid host:’.  The valid value is ‘127.0.0.1
(idlelib.rpc.LOCALHOST)’.  One can diagnose with ‘tcpconnect -irv
127.0.0.1 6543’ in one terminal window and ‘tcplisten <same args>’ in
another.

A common cause of failure is a user-written file with the same name as a
standard library module, such as 'random.py' and 'tkinter.py'.  When
such a file is located in the same directory as a file that is about to
be run, IDLE cannot import the stdlib file.  The current fix is to
rename the user file.

Though less common than in the past, an antivirus or firewall program
may stop the connection.  If the program cannot be taught to allow the
connection, then it must be turned off for IDLE to work.  It is safe to
allow this internal connection because no data is visible on external
ports.  A similar problem is a network mis-configuration that blocks
connections.

Python installation issues occasionally stop IDLE: multiple versions can
clash, or a single installation might need admin access.  If one undo
the clash, or cannot or does not want to run as admin, it might be
easiest to completely remove Python and start over.

A zombie pythonw.exe process could be a problem.  On Windows, use Task
Manager to check for one and stop it if there is.  Sometimes a restart
initiated by a program crash or Keyboard Interrupt (control-C) may fail
to connect.  Dismissing the error box or using Restart Shell on the
Shell menu may fix a temporary problem.

When IDLE first starts, it attempts to read user configuration files in
‘~/.idlerc/’ (~ is one's home directory).  If there is a problem, an
error message should be displayed.  Leaving aside random disk glitches,
this can be prevented by never editing the files by hand.  Instead, use
the configuration dialog, under Options.  Once there is an error in a
user configuration file, the best solution may be to delete it and start
over with the settings dialog.

If IDLE quits with no message, and it was not started from a console,
try starting it from a console or terminal (‘python -m idlelib’) and see
if this results in an error message.

On Unix-based systems with tcl/tk older than ‘8.6.11’ (see ‘About IDLE’)
certain characters of certain fonts can cause a tk failure with a
message to the terminal.  This can happen either if one starts IDLE to
edit a file with such a character or later when entering such a
character.  If one cannot upgrade tcl/tk, then re-configure IDLE to use
a font that works better.


File: python.info,  Node: Running user code,  Next: User output in Shell,  Prev: Startup failure,  Up: Startup and Code Execution

5.25.9.25 Running user code
...........................

With rare exceptions, the result of executing Python code with IDLE is
intended to be the same as executing the same code by the default
method, directly with Python in a text-mode system console or terminal
window.  However, the different interface and operation occasionally
affect visible results.  For instance, ‘sys.modules’ starts with more
entries, and ‘threading.active_count()’ returns 2 instead of 1.

By default, IDLE runs user code in a separate OS process rather than in
the user interface process that runs the shell and editor.  In the
execution process, it replaces ‘sys.stdin’, ‘sys.stdout’, and
‘sys.stderr’ with objects that get input from and send output to the
Shell window.  The original values stored in ‘sys.__stdin__’,
‘sys.__stdout__’, and ‘sys.__stderr__’ are not touched, but may be
‘None’.

Sending print output from one process to a text widget in another is
slower than printing to a system terminal in the same process.  This has
the most effect when printing multiple arguments, as the string for each
argument, each separator, the newline are sent separately.  For
development, this is usually not a problem, but if one wants to print
faster in IDLE, format and join together everything one wants displayed
together and then print a single string.  Both format strings and *note
str.join(): 2088. can help combine fields and lines.

IDLE's standard stream replacements are not inherited by subprocesses
created in the execution process, whether directly by user code or by
modules such as multiprocessing.  If such subprocess use ‘input’ from
sys.stdin or ‘print’ or ‘write’ to sys.stdout or sys.stderr, IDLE should
be started in a command line window.  (On Windows, use ‘python’ or ‘py’
rather than ‘pythonw’ or ‘pyw’.)  The secondary subprocess will then be
attached to that window for input and output.

If ‘sys’ is reset by user code, such as with ‘importlib.reload(sys)’,
IDLE's changes are lost and input from the keyboard and output to the
screen will not work correctly.

When Shell has the focus, it controls the keyboard and screen.  This is
normally transparent, but functions that directly access the keyboard
and screen will not work.  These include system-specific functions that
determine whether a key has been pressed and if so, which.

The IDLE code running in the execution process adds frames to the call
stack that would not be there otherwise.  IDLE wraps
‘sys.getrecursionlimit’ and ‘sys.setrecursionlimit’ to reduce the effect
of the additional stack frames.

When user code raises SystemExit either directly or by calling sys.exit,
IDLE returns to a Shell prompt instead of exiting.


File: python.info,  Node: User output in Shell,  Next: Developing tkinter applications,  Prev: Running user code,  Up: Startup and Code Execution

5.25.9.26 User output in Shell
..............................

When a program outputs text, the result is determined by the
corresponding output device.  When IDLE executes user code, ‘sys.stdout’
and ‘sys.stderr’ are connected to the display area of IDLE's Shell.
Some of its features are inherited from the underlying Tk Text widget.
Others are programmed additions.  Where it matters, Shell is designed
for development rather than production runs.

For instance, Shell never throws away output.  A program that sends
unlimited output to Shell will eventually fill memory, resulting in a
memory error.  In contrast, some system text windows only keep the last
n lines of output.  A Windows console, for instance, keeps a
user-settable 1 to 9999 lines, with 300 the default.

A Tk Text widget, and hence IDLE's Shell, displays characters
(codepoints) in the BMP (Basic Multilingual Plane) subset of Unicode.
Which characters are displayed with a proper glyph and which with a
replacement box depends on the operating system and installed fonts.
Tab characters cause the following text to begin after the next tab
stop.  (They occur every 8 'characters').  Newline characters cause
following text to appear on a new line.  Other control characters are
ignored or displayed as a space, box, or something else, depending on
the operating system and font.  (Moving the text cursor through such
output with arrow keys may exhibit some surprising spacing behavior.)

     >>> s = 'a\tb\a<\x02><\r>\bc\nd'  # Enter 22 chars.
     >>> len(s)
     14
     >>> s  # Display repr(s)
     'a\tb\x07<\x02><\r>\x08c\nd'
     >>> print(s, end='')  # Display s as is.
     # Result varies by OS and font.  Try it.

The ‘repr’ function is used for interactive echo of expression values.
It returns an altered version of the input string in which control
codes, some BMP codepoints, and all non-BMP codepoints are replaced with
escape codes.  As demonstrated above, it allows one to identify the
characters in a string, regardless of how they are displayed.

Normal and error output are generally kept separate (on separate lines)
from code input and each other.  They each get different highlight
colors.

For SyntaxError tracebacks, the normal '^' marking where the error was
detected is replaced by coloring the text with an error highlight.  When
code run from a file causes other exceptions, one may right click on a
traceback line to jump to the corresponding line in an IDLE editor.  The
file will be opened if necessary.

Shell has a special facility for squeezing output lines down to a
'Squeezed text' label.  This is done automatically for output over N
lines (N = 50 by default).  N can be changed in the PyShell section of
the General page of the Settings dialog.  Output with fewer lines can be
squeezed by right clicking on the output.  This can be useful lines long
enough to slow down scrolling.

Squeezed output is expanded in place by double-clicking the label.  It
can also be sent to the clipboard or a separate view window by
right-clicking the label.


File: python.info,  Node: Developing tkinter applications,  Next: Running without a subprocess,  Prev: User output in Shell,  Up: Startup and Code Execution

5.25.9.27 Developing tkinter applications
.........................................

IDLE is intentionally different from standard Python in order to
facilitate development of tkinter programs.  Enter ‘import tkinter as
tk; root = tk.Tk()’ in standard Python and nothing appears.  Enter the
same in IDLE and a tk window appears.  In standard Python, one must also
enter ‘root.update()’ to see the window.  IDLE does the equivalent in
the background, about 20 times a second, which is about every 50
milliseconds.  Next enter ‘b = tk.Button(root, text='button');
b.pack()’.  Again, nothing visibly changes in standard Python until one
enters ‘root.update()’.

Most tkinter programs run ‘root.mainloop()’, which usually does not
return until the tk app is destroyed.  If the program is run with
‘python -i’ or from an IDLE editor, a ‘>>>’ shell prompt does not appear
until ‘mainloop()’ returns, at which time there is nothing left to
interact with.

When running a tkinter program from an IDLE editor, one can comment out
the mainloop call.  One then gets a shell prompt immediately and can
interact with the live application.  One just has to remember to
re-enable the mainloop call when running in standard Python.


File: python.info,  Node: Running without a subprocess,  Prev: Developing tkinter applications,  Up: Startup and Code Execution

5.25.9.28 Running without a subprocess
......................................

By default, IDLE executes user code in a separate subprocess via a
socket, which uses the internal loopback interface.  This connection is
not externally visible and no data is sent to or received from the
internet.  If firewall software complains anyway, you can ignore it.

If the attempt to make the socket connection fails, Idle will notify
you.  Such failures are sometimes transient, but if persistent, the
problem may be either a firewall blocking the connection or
misconfiguration of a particular system.  Until the problem is fixed,
one can run Idle with the -n command line switch.

If IDLE is started with the -n command line switch it will run in a
single process and will not create the subprocess which runs the RPC
Python execution server.  This can be useful if Python cannot create the
subprocess or the RPC socket interface on your platform.  However, in
this mode user code is not isolated from IDLE itself.  Also, the
environment is not restarted when Run/Run Module (F5) is selected.  If
your code has been modified, you must reload() the affected modules and
re-import any specific items (e.g.  from foo import baz) if the changes
are to take effect.  For these reasons, it is preferable to run IDLE
with the default subprocess if at all possible.

在 3.4 版之後被棄用.


File: python.info,  Node: Help and Preferences,  Next: idlelib,  Prev: Startup and Code Execution,  Up: IDLE<62>

5.25.9.29 Help and Preferences
..............................

* Menu:

* Help sources::
* Setting preferences::
* IDLE on macOS::
* Extensions::


File: python.info,  Node: Help sources,  Next: Setting preferences,  Up: Help and Preferences

5.25.9.30 Help sources
......................

Help menu entry "IDLE Help" displays a formatted html version of the
IDLE chapter of the Library Reference.  The result, in a read-only
tkinter text window, is close to what one sees in a web browser.
Navigate through the text with a mousewheel, the scrollbar, or up and
down arrow keys held down.  Or click the TOC (Table of Contents) button
and select a section header in the opened box.

Help menu entry "Python Docs" opens the extensive sources of help,
including tutorials, available at ‘docs.python.org/x.y’, where 'x.y' is
the currently running Python version.  If your system has an off-line
copy of the docs (this may be an installation option), that will be
opened instead.

Selected URLs can be added or removed from the help menu at any time
using the General tab of the Configure IDLE dialog.


File: python.info,  Node: Setting preferences,  Next: IDLE on macOS,  Prev: Help sources,  Up: Help and Preferences

5.25.9.31 Setting preferences
.............................

The font preferences, highlighting, keys, and general preferences can be
changed via Configure IDLE on the Option menu.  Non-default user
settings are saved in a ‘.idlerc’ directory in the user's home
directory.  Problems caused by bad user configuration files are solved
by editing or deleting one or more of the files in ‘.idlerc’.

On the Font tab, see the text sample for the effect of font face and
size on multiple characters in multiple languages.  Edit the sample to
add other characters of personal interest.  Use the sample to select
monospaced fonts.  If particular characters have problems in Shell or an
editor, add them to the top of the sample and try changing first size
and then font.

On the Highlights and Keys tab, select a built-in or custom color theme
and key set.  To use a newer built-in color theme or key set with older
IDLEs, save it as a new custom theme or key set and it well be
accessible to older IDLEs.


File: python.info,  Node: IDLE on macOS,  Next: Extensions,  Prev: Setting preferences,  Up: Help and Preferences

5.25.9.32 IDLE on macOS
.......................

Under System Preferences: Dock, one can set "Prefer tabs when opening
documents" to "Always".  This setting is not compatible with the
tk/tkinter GUI framework used by IDLE, and it breaks a few IDLE
features.


File: python.info,  Node: Extensions,  Prev: IDLE on macOS,  Up: Help and Preferences

5.25.9.33 Extensions
....................

IDLE contains an extension facility.  Preferences for extensions can be
changed with the Extensions tab of the preferences dialog.  See the
beginning of config-extensions.def in the idlelib directory for further
information.  The only current default extension is zzdummy, an example
also used for testing.


File: python.info,  Node: idlelib,  Prev: Help and Preferences,  Up: IDLE<62>

5.25.9.34 idlelib
.................

'原始碼：'Lib/idlelib/(1)

__________________________________________________________________

The Lib/idlelib package implements the IDLE application.  See the rest
of this page for how to use IDLE.

The files in idlelib are described in idlelib/README.txt.  Access it
either in idlelib or click Help => About IDLE on the IDLE menu.  This
file also maps IDLE menu items to the code that implements the item.
Except for files listed under 'Startup', the idlelib code is 'private'
in sense that feature changes can be backported (see PEP 434(2)).

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/idlelib/

   (2) https://peps.python.org/pep-0434/


File: python.info,  Node: 開發工具,  Next: 除錯與效能分析,  Prev: 以 Tk 打造圖形使用者介面 Graphical User Interfaces,  Up: Python 標準函式庫 Standard Library

5.26 開發工具
=============

The modules described in this chapter help you write software.  For
example, the *note pydoc: a3. module takes a module and generates
documentation based on the module's contents.  The *note doctest: 31.
and *note unittest: ef. modules contains frameworks for writing unit
tests that automatically exercise code and verify that the expected
output is produced.

The list of modules described in this chapter is:

* Menu:

* typing: typing --- 支援型別提示. 支援型別提示
* pydoc: pydoc --- 文件產生器與線上幫助系統. 文件產生器與線上幫助系統
* Python 開發模式::
* doctest: doctest --- 測試互動式 Python 範例. 測試互動式 Python 範例
* unittest: unittest --- 單元測試框架. 單元測試框架
* unittest.mock — mock 物件函式庫: unittest mock — mock 物件函式庫.
* unittest.mock: unittest mock --- 入門指南. 入門指南
* test: test --- Python 的回歸測試 regression tests 套件. Python 的回歸測試 (regression tests) 套件
* test.support: test support --- Python 測試套件的工具. Python 測試套件的工具
* test.support.socket_helper: test support socket_helper --- 用於 socket 測試的工具. 用於 socket 測試的工具
* test.support.script_helper: test support script_helper --- 用於 Python 執行測試的工具. 用於 Python 執行測試的工具
* test.support.bytecode_helper: test support bytecode_helper --- 用於測試位元組碼能正確產生的支援工具. 用於測試位元組碼能正確產生的支援工具
* test.support.threading_helper: test support threading_helper --- Utilities for threading tests. Utilities for threading tests
* test.support.os_helper: test support os_helper --- 用於 os 測試的工具. 用於 os 測試的工具
* test.support.import_helper: test support import_helper --- 用於 import 測試的工具. 用於 import 測試的工具
* test.support.warnings_helper: test support warnings_helper --- 用於 warnings 測試的工具. 用於 warnings 測試的工具


File: python.info,  Node: typing --- 支援型別提示,  Next: pydoc --- 文件產生器與線上幫助系統,  Up: 開發工具

5.26.1 ‘typing’ -- 支援型別提示
-------------------------------

在 3.5 版被加入.

'原始碼：'Lib/typing.py(1)

     備註: Python runtime 不強制要求函式與變數的型別註釋。他們可以被第三
     方工具使用，如：*note 型別檢查器: 252.、IDE、linter 等。

__________________________________________________________________

此模組提供 runtime 型別提示支援。

動腦筋思考下面的函式：

     def surface_area_of_cube(edge_length: float) -> str:
         return f"The surface area of the cube is {6 * edge_length ** 2}."

函式 ‘surface_area_of_cube’ 需要一個引數且預期是一個 *note float: 2c8. 的
實例，如 ‘edge_length: float’ 所指出的*note 型別提示: 1e58.。這個函式預
期會回傳一個 *note str: 3f2. 的實例，如 ‘-> str’ 所指出的提示。

儘管型別提示可以是簡單類別，像是 *note float: 2c8. 或 *note str: 3f2.，
他們也可以變得更為複雜。模組 *note typing: ed. 提供一組更高階的型別提示
詞彙。

新功能會頻繁的新增至 ‘typing’ 模組中。typing_extensions(2) 套件為這些新
功能提供了 backport（向後移植的）版本，提供給舊版本的 Python 使用。

也參考
......

"型別小抄 (Typing cheat sheet)"(3)

     型別提示的快速預覽（發布於 mypy 的文件中）

mypy 文件(4)的 "型別系統參考資料 (Type System Reference)" 章節

     Python 的加註型別系統是基於 PEPs 進行標準化，所以這個參照
     (reference) 應該在多數 Python 型別檢查器中廣為使用。（某些部分依然
     是特定給 mypy 使用。）

"Python 的靜態型別 (Static Typing)"(5)

     由社群編寫的跨平台型別檢查器文件 (type-checker-agnostic) 詳細描述加
     註型別系統的功能、實用的加註型別衍伸工具、以及加註型別的最佳實踐
     (best practice)。

* Menu:

* Python 型別系統的技術規範::
* 型別別名::
* NewType::
* 註釋 callable 物件::
* 泛型::
* 註釋元組 (tuple): 註釋元組 tuple.
* 類別物件的型別::
* Annotating generators and coroutines::
* 使用者定義泛型型別::
* Any 型別::
* 標稱 (nominal) 子型別 vs 結構子型別: 標稱 nominal 子型別 vs 結構子型別.
* 模組內容: 模組內容<7>.
* Deprecation Timeline of Major Features::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/typing.py

   (2) https://pypi.org/project/typing_extensions/

   (3) https://mypy.readthedocs.io/en/stable/cheat_sheet_py3.html

   (4) https://mypy.readthedocs.io/en/stable/index.html

   (5) https://typing.readthedocs.io/en/latest/


File: python.info,  Node: Python 型別系統的技術規範,  Next: 型別別名,  Up: typing --- 支援型別提示

5.26.1.1 Python 型別系統的技術規範
..................................

關於 Python 型別系統標準的 (canonical)、最新的技術規範可以在「Python 型
別系統的技術規範」(1)找到。

   ---------- Footnotes ----------

   (1) https://typing.readthedocs.io/en/latest/spec/index.html


File: python.info,  Node: 型別別名,  Next: NewType,  Prev: Python 型別系統的技術規範,  Up: typing --- 支援型別提示

5.26.1.2 型別別名
.................

一個型別別名被定義來使用 *note type: 3de. 陳述式，其建立了 *note
TypeAliasType: 3fb. 的實例。在這個範例中，‘Vector’ 及 ‘list[float]’ 會被
當作和靜態型別檢查器一樣同等對待：

     type Vector = list[float]

     def scale(scalar: float, vector: Vector) -> Vector:
         return [scalar * num for num in vector]

     # passes type checking; a list of floats qualifies as a Vector.
     new_vector = scale(2.0, [1.0, -4.2, 5.4])

型別別名對於簡化複雜的型別簽名 (complex type signature) 非常好用。舉例來
說：

     from collections.abc import Sequence

     type ConnectionOptions = dict[str, str]
     type Address = tuple[str, int]
     type Server = tuple[Address, ConnectionOptions]

     def broadcast_message(message: str, servers: Sequence[Server]) -> None:
         ...

     # The static type checker will treat the previous type signature as
     # being exactly equivalent to this one.
     def broadcast_message(
         message: str,
         servers: Sequence[tuple[tuple[str, int], dict[str, str]]]
     ) -> None:
         ...

*note type: 3de. 陳述式是 Python 3.12 的新功能。為了向後相容性，型別別名
可以透過簡單的賦值來建立：

     Vector = list[float]

或是用 *note TypeAlias: 76d. 標記，讓它明確的表示這是一個型別別名，而非
一般的變數賦值：

     from typing import TypeAlias

     Vector: TypeAlias = list[float]


File: python.info,  Node: NewType,  Next: 註釋 callable 物件,  Prev: 型別別名,  Up: typing --- 支援型別提示

5.26.1.3 NewType
................

使用 *note NewType: c9c. 輔助工具 (helper) 建立獨特型別：

     from typing import NewType

     UserId = NewType('UserId', int)
     some_id = UserId(524313)

若它是原本型別的子類別，靜態型別檢查器會將其視為一個新的型別。這對於幫助
擷取邏輯性錯誤非常有用：

     def get_user_name(user_id: UserId) -> str:
         ...

     # passes type checking
     user_a = get_user_name(UserId(42351))

     # fails type checking; an int is not a UserId
     user_b = get_user_name(-1)

你依然可以在對於型別 ‘UserId’ 的變數中執行所有 ‘int’ 的操作。這讓你可以
在預期接受 ‘int’ 的地方傳遞一個 ‘UserId’，還能預防你意外使用無效的方法建
立一個 ‘UserId’：

     # 'output' is of type 'int', not 'UserId'
     output = UserId(23413) + UserId(54341)

注意這只會透過靜態型別檢查器強制檢查。在 runtime 中，陳述式 (statement)
‘Derived = NewType('Derived', Base)’ 會使 ‘Derived’ 成為一個 callable（
可呼叫物件），會立即回傳任何你傳遞的引數。這意味著 expression （運算式）
‘Derived(some_value)’ 不會建立一個新的類別或過度引入原有的函式呼叫。

更精確地說，expression ‘some_value is Derived(some_value)’ 在 runtime 永
遠為 true。

這會無法建立一個 ‘Derived’ 的子型別：

     from typing import NewType

     UserId = NewType('UserId', int)

     # Fails at runtime and does not pass type checking
     class AdminUserId(UserId): pass

無論如何，這有辦法基於 '衍生的' ‘NewType’ 建立一個 *note NewType: c9c.：

     from typing import NewType

     UserId = NewType('UserId', int)

     ProUserId = NewType('ProUserId', UserId)

以及針對 ‘ProUserId’ 的型別檢查會如期運作。

更多細節請見 PEP 484(1)。

     備註: 請記得使用型別別名是宣告兩種型別是互相'相等'的。使用 ‘type
     Alias = Original’ 則會讓靜態型別檢查器在任何情況之下將 ‘Alias’ 視為
     與 ‘Original’ '完全相等'。這當你想把複雜的型別簽名進行簡化時，非常
     好用。

     相反的，‘NewType’ 宣告一個型別會是另外一種型別的子類別。使用
     ‘Derived = NewType('Derived', Original)’ 會使靜態型別檢查器將
     ‘Derived’ 視為 ‘Original’ 的子類別，也意味著一個型別為 ‘Original’ 的
     值，不能被使用在任何預期接收到型別 ‘Derived’ 的值的區域。這當你想用
     最小的 runtime 成本預防邏輯性錯誤而言，非常有用。

在 3.5.2 版被加入.

在 3.10 版的變更: 現在的 ‘NewType’ 比起一個函式更像一個類別。因此，比起
一般的函式，呼叫 ‘NewType’ 需要額外的 runtime 成本。

在 3.11 版的變更: 呼叫 ‘NewType’ 的效能已經恢復與 Python 3.9 相同的水準
。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0484/


File: python.info,  Node: 註釋 callable 物件,  Next: 泛型,  Prev: NewType,  Up: typing --- 支援型別提示

5.26.1.4 註釋 callable 物件
...........................

函式，或者是其他 *note callable: 27d4. 物件，可以使用 *note
collections.abc.Callable: 78e. 或以棄用的 *note typing.Callable: 769. 進
行註釋。 ‘Callable[[int], str]’ 象徵為一個函式，可以接受一個型別為 *note
int: 23c. 的引數，並回傳一個 *note str: 3f2.。

舉例來說：

     from collections.abc import Callable, Awaitable

     def feeder(get_next_item: Callable[[], str]) -> None:
         ...  # Body

     def async_query(on_success: Callable[[int], None],
                     on_error: Callable[[int, Exception], None]) -> None:
         ...  # Body

     async def on_update(value: str) -> None:
         ...  # Body

     callback: Callable[[str], Awaitable[None]] = on_update

使用下標語法 (subscription syntax) 時，必須使用到兩個值，分別為引述串列
以及回傳類別。引數串列必須為一個型別串列：*note ParamSpec: 142.、*note
Concatenate: 768. 或是一個刪節號 (ellipsis)。回傳類別必為一個單一類別。

若刪節號文字 ‘...’ 被當作引數串列給定，其指出一個具任何、任意參數列表的
callable 會被接受：

     def concat(x: str, y: str) -> str:
         return x + y

     x: Callable[..., str]
     x = str     # OK
     x = concat  # Also OK

‘Callable’ 不如有可變數量引數的函式、*note overloaded functions: 3d8f.、
或是僅限關鍵字參數的函式，可以表示複雜簽名。然而，這些簽名可以透過定義一
個具有 *note __call__(): 4fe. 方法的 *note Protocol: 249. 類別進行表示：

     from collections.abc import Iterable
     from typing import Protocol

     class Combiner(Protocol):
         def __call__(self, *vals: bytes, maxlen: int | None = None) -> list[bytes]: ...

     def batch_proc(data: Iterable[bytes], cb_results: Combiner) -> bytes:
         for item in data:
             ...

     def good_cb(*vals: bytes, maxlen: int | None = None) -> list[bytes]:
         ...
     def bad_cb(*vals: bytes, maxitems: int | None) -> list[bytes]:
         ...

     batch_proc([], good_cb)  # OK
     batch_proc([], bad_cb)   # Error! Argument 2 has incompatible type because of
                              # different name and kind in the callback

Callable 物件可以取用其他 callable 當作引數使用，可以透過 *note
ParamSpec: 142. 指出他們的參數型別是個別獨立的。另外，如果這個 callable
從其他 callable 新增或刪除引數時，將會使用到 *note Concatenate: 768. 運
算子。他們可以分別採用 ‘Callable[ParamSpecVariable, ReturnType]’ 以及
‘Callable[Concatenate[Arg1Type, Arg2Type, ..., ParamSpecVariable],
ReturnType]’ 的形式。

在 3.10 版的變更: ‘Callable’ 現已支援 *note ParamSpec: 142. 以及 *note
Concatenate: 768.。請參閱 PEP 612(1) 閱讀詳細內容。

也參考
......

*note ParamSpec: 142. 以及 *note Concatenate: 768. 的文件中，提供範例如
何在 ‘Callable’ 中使用。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0612/


File: python.info,  Node: 泛型,  Next: 註釋元組 tuple,  Prev: 註釋 callable 物件,  Up: typing --- 支援型別提示

5.26.1.5 泛型
.............

因為關於物件的型別資訊留存在容器之內，且無法使用通用的方式進行靜態推論
(statically inferred)，許多標準函式庫的容器類別支援以下標來表示容器內預
期的元素。

     from collections.abc import Mapping, Sequence

     class Employee: ...

     # Sequence[Employee] indicates that all elements in the sequence
     # must be instances of "Employee".
     # Mapping[str, str] indicates that all keys and all values in the mapping
     # must be strings.
     def notify_by_email(employees: Sequence[Employee],
                         overrides: Mapping[str, str]) -> None: ...

泛型函式及類別可以使用*note 型別參數語法 (type parameter syntax): 294. 進
行參數化 (parameterize) ：

     from collections.abc import Sequence

     def first[T](l: Sequence[T]) -> T:  # Function is generic over the TypeVar "T"
         return l[0]

或是直接使用 *note TypeVar: 141. 工廠 (factory)：

     from collections.abc import Sequence
     from typing import TypeVar

     U = TypeVar('U')                  # Declare type variable "U"

     def second(l: Sequence[U]) -> U:  # Function is generic over the TypeVar "U"
         return l[1]

在 3.12 版的變更: 在 Python 3.12 中，泛型的語法支援是全新功能。


File: python.info,  Node: 註釋元組 tuple,  Next: 類別物件的型別,  Prev: 泛型,  Up: typing --- 支援型別提示

5.26.1.6 註釋元組 (tuple)
.........................

在 Python 大多數的容器當中，加註型別系統認為容器內的所有元素會是相同型別
。舉例來說：

     from collections.abc import Mapping

     # Type checker will infer that all elements in ``x`` are meant to be ints
     x: list[int] = []

     # Type checker error: ``list`` only accepts a single type argument:
     y: list[int, str] = [1, 'foo']

     # Type checker will infer that all keys in ``z`` are meant to be strings,
     # and that all values in ``z`` are meant to be either strings or ints
     z: Mapping[str, str | int] = {}

*note list: 5b6. 只接受一個型別引數，所以型別檢查器可能在上述 ‘y’ 賦值
(assignment) 觸發錯誤。類似的範例，*note Mapping: 86f. 只接受兩個型別引
數：第一個引數指出 keys（鍵）的型別；第二個引數指出 values（值）的型別。

然而，與其他多數的 Python 容器不同，在慣用的 (idiomatic) Python 程式碼中
，元組可以擁有不完全相同型別的元素是相當常見的。為此，元組在 Python 的加
註型別系統中是個特例 (special-cased)。*note tuple: 322. 接受'任何數量'的
型別引數：

     # OK: ``x`` is assigned to a tuple of length 1 where the sole element is an int
     x: tuple[int] = (5,)

     # OK: ``y`` is assigned to a tuple of length 2;
     # element 1 is an int, element 2 is a str
     y: tuple[int, str] = (5, "foo")

     # Error: the type annotation indicates a tuple of length 1,
     # but ``z`` has been assigned to a tuple of length 3
     z: tuple[int] = (1, 2, 3)

為了標示一個元組可以為'任意'長度，且所有元素皆是相同型別 ‘T’，請使用
‘tuple[T, ...]’ 進行標示。為了標示一個空元組，請使用 ‘tuple[()]’。單純使
用 ‘tuple’ 作為註釋，會與使用 ‘tuple[Any, ...]’ 是相等的：

     x: tuple[int, ...] = (1, 2)
     # These reassignments are OK: ``tuple[int, ...]`` indicates x can be of any length
     x = (1, 2, 3)
     x = ()
     # This reassignment is an error: all elements in ``x`` must be ints
     x = ("foo", "bar")

     # ``y`` can only ever be assigned to an empty tuple
     y: tuple[()] = ()

     z: tuple = ("foo", "bar")
     # These reassignments are OK: plain ``tuple`` is equivalent to ``tuple[Any, ...]``
     z = (1, 2, 3)
     z = ()


File: python.info,  Node: 類別物件的型別,  Next: Annotating generators and coroutines,  Prev: 註釋元組 tuple,  Up: typing --- 支援型別提示

5.26.1.7 類別物件的型別
.......................

一個變數被註釋為 ‘C’ 可以接受一個型別為 ‘C’ 的值。相對的，一個變數備註解
為 ‘type[C]’ （或已棄用的 *note typing.Type[C]: 3d95.）可以接受本身為該
類別的值 - 具體來說，他可能會接受 ‘C’ 的'類別物件'。舉例來說：

     a = 3         # Has type ``int``
     b = int       # Has type ``type[int]``
     c = type(a)   # Also has type ``type[int]``

請記得 ‘type[C]’ 是共變 (covariant) 的：

     class User: ...
     class ProUser(User): ...
     class TeamUser(User): ...

     def make_new_user(user_class: type[User]) -> User:
         # ...
         return user_class()

     make_new_user(User)      # OK
     make_new_user(ProUser)   # Also OK: ``type[ProUser]`` is a subtype of ``type[User]``
     make_new_user(TeamUser)  # Still fine
     make_new_user(User())    # Error: expected ``type[User]`` but got ``User``
     make_new_user(int)       # Error: ``type[int]`` is not a subtype of ``type[User]``

*note type: cef. 僅有的合法參數是類別、*note Any: 651.、*note 型別變數:
1e56.以及這些型別任意組合成的聯集。舉例來說：

     def new_non_team_user(user_class: type[BasicUser | ProUser]): ...

     new_non_team_user(BasicUser)  # OK
     new_non_team_user(ProUser)    # OK
     new_non_team_user(TeamUser)   # Error: ``type[TeamUser]`` is not a subtype
                                   # of ``type[BasicUser | ProUser]``
     new_non_team_user(User)       # Also an error

‘type[Any]’ 等價於 *note type: cef. ，其為 Python *note metaclass
階層結構 (hierachy): 1e4a.。


File: python.info,  Node: Annotating generators and coroutines,  Next: 使用者定義泛型型別,  Prev: 類別物件的型別,  Up: typing --- 支援型別提示

5.26.1.8 Annotating generators and coroutines
.............................................

A generator can be annotated using the generic type *note
Generator[YieldType, SendType, ReturnType]: d81.  For example:

     def echo_round() -> Generator[int, float, str]:
         sent = yield 0
         while sent >= 0:
             sent = yield round(sent)
         return 'Done'

Note that unlike many other generic classes in the standard library, the
‘SendType’ of *note Generator: d81. behaves contravariantly, not
covariantly or invariantly.

The ‘SendType’ and ‘ReturnType’ parameters default to ‘None’:

     def infinite_stream(start: int) -> Generator[int]:
         while True:
             yield start
             start += 1

It is also possible to set these types explicitly:

     def infinite_stream(start: int) -> Generator[int, None, None]:
         while True:
             yield start
             start += 1

Simple generators that only ever yield values can also be annotated as
having a return type of either *note Iterable[YieldType]: 212a. or *note
Iterator[YieldType]: 212b.:

     def infinite_stream(start: int) -> Iterator[int]:
         while True:
             yield start
             start += 1

Async generators are handled in a similar fashion, but don't expect a
‘ReturnType’ type argument (*note AsyncGenerator[YieldType, SendType]:
c31.).  The ‘SendType’ argument defaults to ‘None’, so the following
definitions are equivalent:

     async def infinite_stream(start: int) -> AsyncGenerator[int]:
         while True:
             yield start
             start = await increment(start)

     async def infinite_stream(start: int) -> AsyncGenerator[int, None]:
         while True:
             yield start
             start = await increment(start)

As in the synchronous case, *note AsyncIterable[YieldType]: d85. and
*note AsyncIterator[YieldType]: d84. are available as well:

     async def infinite_stream(start: int) -> AsyncIterator[int]:
         while True:
             yield start
             start = await increment(start)

Coroutines can be annotated using *note Coroutine[YieldType, SendType,
ReturnType]: d83.  Generic arguments correspond to those of *note
Generator: d81, for example:

     from collections.abc import Coroutine
     c: Coroutine[list[str], str, int]  # Some coroutine defined elsewhere
     x = c.send('hi')                   # Inferred type of 'x' is list[str]
     async def bar() -> None:
         y = await c                    # Inferred type of 'y' is int


File: python.info,  Node: 使用者定義泛型型別,  Next: Any 型別,  Prev: Annotating generators and coroutines,  Up: typing --- 支援型別提示

5.26.1.9 使用者定義泛型型別
...........................

一個使用者定義的類別可以被定義成一個泛型類別。

     from logging import Logger

     class LoggedVar[T]:
         def __init__(self, value: T, name: str, logger: Logger) -> None:
             self.name = name
             self.logger = logger
             self.value = value

         def set(self, new: T) -> None:
             self.log('Set ' + repr(self.value))
             self.value = new

         def get(self) -> T:
             self.log('Get ' + repr(self.value))
             return self.value

         def log(self, message: str) -> None:
             self.logger.info('%s: %s', self.name, message)

這個語法指出類別 ‘LoggedVar’ 透過一個單一的 *note 型別變數: 3d98. ‘T’ 進
行參數化 (parameterised)。這使得 ‘T’ 在類別中有效的成為型別。

泛型類別隱性繼承了 *note Generic: 150c.。為了相容 Python 3.11 及更早版本
，也可以明確的繼承 *note Generic: 150c. 並指出是一個泛型類別：

     from typing import TypeVar, Generic

     T = TypeVar('T')

     class LoggedVar(Generic[T]):
         ...

泛型類別有 *note __class_getitem__(): 6df. 方法，其意味著可以在 runtime
進行參數化（如下述的 ‘LoggedVar[int]’）：

     from collections.abc import Iterable

     def zero_all_vars(vars: Iterable[LoggedVar[int]]) -> None:
         for var in vars:
             var.set(0)

一個泛型型別可以有任意數量的型別變數。所有種類的 *note TypeVar: 141. 都
可以作為泛型型別的參數：

     from typing import TypeVar, Generic, Sequence

     class WeirdTrio[T, B: Sequence[bytes], S: (int, str)]:
         ...

     OldT = TypeVar('OldT', contravariant=True)
     OldB = TypeVar('OldB', bound=Sequence[bytes], covariant=True)
     OldS = TypeVar('OldS', int, str)

     class OldWeirdTrio(Generic[OldT, OldB, OldS]):
         ...

*note Generic: 150c. 的每個型別變數引數必不相同。因此以下是無效的：

     from typing import TypeVar, Generic
     ...

     class Pair[M, M]:  # SyntaxError
         ...

     T = TypeVar('T')

     class Pair(Generic[T, T]):   # INVALID
         ...

泛型類別亦可以繼承其他類別：

     from collections.abc import Sized

     class LinkedList[T](Sized):
         ...

當繼承泛型類別時，部份的型別參數可固定：

     from collections.abc import Mapping

     class MyDict[T](Mapping[str, T]):
         ...

在這種情況下 ‘MyDict’ 有一個單一的參數 ‘T’。

若使用泛型類別卻沒有特指型別參數，則會將每個位置視為 *note Any: 651.。在
下列的範例中 ‘MyIterable’ 不是泛型，但隱性繼承了 ‘Iterable[Any]’：

     from collections.abc import Iterable

     class MyIterable(Iterable): # Same as Iterable[Any]
         ...

使用者定義的泛型型別別名也有支援。例如：

     from collections.abc import Iterable

     type Response[S] = Iterable[S] | int

     # Return type here is same as Iterable[str] | int
     def response(query: str) -> Response[str]:
         ...

     type Vec[T] = Iterable[tuple[T, T]]

     def inproduct[T: (int, float, complex)](v: Vec[T]) -> T: # Same as Iterable[tuple[T, T]]
         return sum(x*y for x, y in v)

為了向後相容性，泛型型別別名可以透過簡單的賦值來建立：

     from collections.abc import Iterable
     from typing import TypeVar

     S = TypeVar("S")
     Response = Iterable[S] | int

在 3.7 版的變更: *note Generic: 150c. 不再是一個自訂的 metaclass。

在 3.12 版的變更: 在版本 3.12 新增了泛型及型別別名的語法支援。在之前的版
本中，泛型類別必須顯性繼承 *note Generic: 150c. 或是包含一個型別變數在基
底類別 (base) 當中。

使用者定義的參數運算式 (parameter expression) 泛型一樣有支援，透過
‘[**P]’ 格式的參數規格變數來進行表示。對於上述作為參數規格變數的型別變數
，將持續被型別模組視為一個特定的型別變數。對此，其中一個例外是一個型別列
表可以替代 *note ParamSpec: 142.：

     >>> class Z[T, **P]: ...  # T is a TypeVar; P is a ParamSpec
     ...
     >>> Z[int, [dict, float]]
     __main__.Z[int, [dict, float]]

具有 *note ParamSpec: 142. 的泛型類別可以透過顯性繼承 *note Generic:
150c. 進行建立。在這種情況下，不需要使用 ‘**’：

     from typing import ParamSpec, Generic

     P = ParamSpec('P')

     class Z(Generic[P]):
         ...

另外一個 *note TypeVar: 141. 以及 *note ParamSpec: 142. 之間的差異是，基
於美觀因素，只有一個參數規格變數的泛型可以接受如 ‘X[[Type1, Type2,
...]]’ 以及 ‘X[Type1, Type2, ...]’ 的參數列表。在內部中，後者會被轉換為
前者，所以在下方的範例中為相等的：

     >>> class X[**P]: ...
     ...
     >>> X[int, str]
     __main__.X[[int, str]]
     >>> X[[int, str]]
     __main__.X[[int, str]]

請記得，具有 *note ParamSpec: 142. 的泛型在某些情況下替換之後可能不會有
正確的 ‘__parameters__’，因為參數規格主要還是用於靜態型別檢查。

在 3.10 版的變更: *note Generic: 150c. 現在可以透過參數運算式來進行參數
化。詳細內容請見 *note ParamSpec: 142. 以及 PEP 612(1)。

一個使用者定義的泛型類別可以將 ABC 作為他們的基底類別，且不會有
metaclass 衝突。泛型的 metaclass 則不支援。參數化泛型的輸出將被存為快取
，而在型別模組中多數的型別皆為 *note hashable: 5b5. 且可以比較相等性。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0612/


File: python.info,  Node: Any 型別,  Next: 標稱 nominal 子型別 vs 結構子型別,  Prev: 使用者定義泛型型別,  Up: typing --- 支援型別提示

5.26.1.10 ‘Any’ 型別
....................

*note Any: 651. 是一種特別的型別。一個靜態型別檢查器會將每個型別視為可相
容於 *note Any: 651. 且 *note Any: 651. 也可以相容於每個型別。

這意味著如果在一個為 *note Any: 651. 的值上執行任何操作或呼叫方法是可行
的，且可以賦值給任意變數：

     from typing import Any

     a: Any = None
     a = []          # OK
     a = 2           # OK

     s: str = ''
     s = a           # OK

     def foo(item: Any) -> int:
         # Passes type checking; 'item' could be any type,
         # and that type might have a 'bar' method
         item.bar()
         ...

請注意，當賦予型別為 *note Any: 651. 的值更精確的型別時，將不會執行任何
型別檢查。舉例來說，靜態型別檢查器不會在 runtime 中，將 ‘a’ 賦值給 ‘s’ 的
情況下回報錯誤，儘管 ‘s’ 是被宣告為型別 *note str: 3f2. 卻接收到 *note
int: 23c. 的值！

另外，所有缺少回傳型別或參數型別的函式將會隱性預設為 *note Any: 651.：

     def legacy_parser(text):
         ...
         return data

     # A static type checker will treat the above
     # as having the same signature as:
     def legacy_parser(text: Any) -> Any:
         ...
         return data

當你需要混和動態及靜態的型別程式碼，這個行為允許 *note Any: 651. 被當作
一個'緊急出口 (escape hatch)'使用。

*note Any: 651. 的行為對比 *note object: a2f. 的行為。與 *note Any: 651.
相似，所有的型別會作為 *note object: a2f. 的子型別。然而，不像 *note
Any: 651.，反之不亦然：*note object: a2f. 並'不是'一個其他型別的子型別。

這意味著當一個值的型別為 *note object: a2f. 時，型別檢查器會拒絕幾乎所有
的操作，並將賦予這個值到一個特定型別變數（或是當作回傳值使用）視為一個型
別錯誤。舉例來說：

     def hash_a(item: object) -> int:
         # Fails type checking; an object does not have a 'magic' method.
         item.magic()
         ...

     def hash_b(item: Any) -> int:
         # Passes type checking
         item.magic()
         ...

     # Passes type checking, since ints and strs are subclasses of object
     hash_a(42)
     hash_a("foo")

     # Passes type checking, since Any is compatible with all types
     hash_b(42)
     hash_b("foo")

使用 *note object: a2f. ，將指出在型別安全 (typesafe) 的習慣之下一個值可
以為任意型別。使用 *note Any: 651.，將指出這個值是個動態型別。


File: python.info,  Node: 標稱 nominal 子型別 vs 結構子型別,  Next: 模組內容<7>,  Prev: Any 型別,  Up: typing --- 支援型別提示

5.26.1.11 標稱 (nominal) 子型別 vs 結構子型別
.............................................

最初 PEP 484(1) 定義 Python 靜態型別系統使用'標稱子型別'。這意味著只有
‘A’ 為 ‘B’ 的子類別時，‘A’ 才被允許使用在預期是類別 ‘B’ 出現的地方。

這個需求之前也被運用在抽象基底類別，例如 *note Iterable: 212a.。這種方式
的問題在於，一個類別需要顯式的標記來支援他們，這並不符合 Python 風格，也
不像一個常見的慣用動態型別 Python 程式碼。舉例來說，下列程式碼符合 PEP
484(2)：

     from collections.abc import Sized, Iterable, Iterator

     class Bucket(Sized, Iterable[int]):
         ...
         def __len__(self) -> int: ...
         def __iter__(self) -> Iterator[int]: ...

PEP 544(3) 可以透過使用上方的程式碼，且在類別定義時不用顯式基底類別解決
這個問題，讓 ‘Bucket’ 被靜態型別檢查器隱性認為是 ‘Sized’ 以及
‘Iterable[int]’ 兩者的子型別。這就是眾所周知的'結構子型別'（或是靜態鴨子
型別）：

     from collections.abc import Iterator, Iterable

     class Bucket:  # Note: no base classes
         ...
         def __len__(self) -> int: ...
         def __iter__(self) -> Iterator[int]: ...

     def collect(items: Iterable[int]) -> int: ...
     result = collect(Bucket())  # Passes type check

而且，基於一個特別的型別 *note Protocol: 249. 建立子型別時，使用者可以定
義新的協定並充份發揮結構子型別的優勢（請見下方範例）。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0484/

   (2) https://peps.python.org/pep-0484/

   (3) https://peps.python.org/pep-0544/


File: python.info,  Node: 模組內容<7>,  Next: Deprecation Timeline of Major Features,  Prev: 標稱 nominal 子型別 vs 結構子型別,  Up: typing --- 支援型別提示

5.26.1.12 模組內容
..................

模組 ‘typing’ 定義了下列的類別、函式以及裝飾器。

* Menu:

* 特別型別原語 (primitive): 特別型別原語 primitive.
* 協定: 協定<2>.
* ABCs for working with IO::
* 函式與裝飾器::
* Introspection helpers::
* 常數: 常數<9>.
* 棄用的別名::


File: python.info,  Node: 特別型別原語 primitive,  Next: 協定<2>,  Up: 模組內容<7>

5.26.1.13 特別型別原語 (primitive)
..................................

* Menu:

* 特別型別::
* 特別型式::
* Building generic types and type aliases::
* Other special directives::


File: python.info,  Node: 特別型別,  Next: 特別型式,  Up: 特別型別原語 primitive

5.26.1.14 特別型別
..................

這些可以在註釋中做為型別。他們並不支援 ‘[]’ 的下標使用。

 -- 資料: typing.Any

     特別型別，指出一個不受約束 (unconstrained) 的型別。

        * 所有型別皆與 *note Any: 651. 相容。

        * *note Any: 651. 相容於所有型別。

     在 3.11 版的變更: *note Any: 651. 可以作為一個基礎類別。這對於在任
     何地方使用鴨子型別或是高度動態的型別，避免型別檢查器的錯誤是非常有
     用的。

 -- 資料: typing.AnyStr

     一個*note 不受約束的型別變數: 3d9e.。

     定義：

          AnyStr = TypeVar('AnyStr', str, bytes)

     ‘AnyStr’ 是對於函式有用的，他可以接受 *note str: 3f2. 或 *note
     bytes: 1a5. 引數但不可以將此兩種混合。

     舉例來說：

          def concat(a: AnyStr, b: AnyStr) -> AnyStr:
              return a + b

          concat("foo", "bar")    # OK, output has type 'str'
          concat(b"foo", b"bar")  # OK, output has type 'bytes'
          concat("foo", b"bar")   # Error, cannot mix str and bytes

     請注意，儘管他的名稱相近，‘AnyStr’ 與 *note Any: 651. 型別無關，更
     不代表是「任何字串」的意思。尤其，‘AnyStr’ 與 ‘str | bytes’ 兩者不
     同且具有不同的使用情境：

          # Invalid use of AnyStr:
          # The type variable is used only once in the function signature,
          # so cannot be "solved" by the type checker
          def greet_bad(cond: bool) -> AnyStr:
              return "hi there!" if cond else b"greetings!"

          # The better way of annotating this function:
          def greet_proper(cond: bool) -> str | bytes:
              return "hi there!" if cond else b"greetings!"

     Deprecated since version 3.13, will be removed in version 3.18:
     Deprecated in favor of the new *note type parameter syntax: 294.
     Use ‘class A[T: (str, bytes)]: ...’ instead of importing ‘AnyStr’.
     See PEP 695(1) for more details.

     In Python 3.16, ‘AnyStr’ will be removed from ‘typing.__all__’, and
     deprecation warnings will be emitted at runtime when it is accessed
     or imported from ‘typing’.  ‘AnyStr’ will be removed from ‘typing’
     in Python 3.18.

 -- 資料: typing.LiteralString

     特別型別，只包含文本字串。

     任何文本字串都相容於 ‘LiteralString’，對於另一個 ‘LiteralString’ 亦
     是如此。然而，若是一個型別僅為 ‘str’ 的物件則不相容。一個字串若是透
     過組合多個 ‘LiteralString’ 型別的物件建立，則此字串也可以視為
     ‘LiteralString’。

     舉例來說：

          def run_query(sql: LiteralString) -> None:
              ...

          def caller(arbitrary_string: str, literal_string: LiteralString) -> None:
              run_query("SELECT * FROM students")  # OK
              run_query(literal_string)  # OK
              run_query("SELECT * FROM " + literal_string)  # OK
              run_query(arbitrary_string)  # type checker error
              run_query(  # type checker error
                  f"SELECT * FROM students WHERE name = {arbitrary_string}"
              )

     ‘LiteralString’ 對於敏感的 API 來說是有用的，其中任意的使用者產生的
     字串可能會產生問題。舉例來說，上面兩個案例中產生的型別檢查器錯誤是
     脆弱的且容易受到 SQL 注入攻擊。

     更多細節請見 PEP 675(2)。

     在 3.11 版被加入.

 -- 資料: typing.Never
 -- 資料: typing.NoReturn

     ‘Never’ 和 ‘NoReturn’ 表示底部型別 (bottom type)(3)，為一個沒有任何
     成員的型別。

     它們可以被用來代表一個不會回傳的函式，像是 *note sys.exit(): 12dd.：

          from typing import Never  # or NoReturn

          def stop() -> Never:
              raise RuntimeError('no way')

     或被用來定義一個不應被呼叫的函式，因為不會有有效的引數，、像是
     *note assert_never(): 64c.：

          from typing import Never  # or NoReturn

          def never_call_me(arg: Never) -> None:
              pass

          def int_or_str(arg: int | str) -> None:
              never_call_me(arg)  # type checker error
              match arg:
                  case int():
                      print("It's an int")
                  case str():
                      print("It's a str")
                  case _:
                      never_call_me(arg)  # OK, arg is of type Never (or NoReturn)

     ‘Never’ 以及 ‘NoReturn’ 在型別系統中具有相同的意義且靜態型別檢查器
     會將兩者視為相等。

     在 3.6.2 版被加入: 新增 *note NoReturn: 3d9f.。

     在 3.11 版被加入: 新增 *note Never: 64d.。

 -- 資料: typing.Self

     特別型別，用來表示當前類別之內 (enclosed class)。

     舉例來說：

          from typing import Self, reveal_type

          class Foo:
              def return_self(self) -> Self:
                  ...
                  return self

          class SubclassOfFoo(Foo): pass

          reveal_type(Foo().return_self())  # Revealed type is "Foo"
          reveal_type(SubclassOfFoo().return_self())  # Revealed type is "SubclassOfFoo"

     這個註釋在語意上相等於下列內容，且形式更為簡潔：

          from typing import TypeVar

          Self = TypeVar("Self", bound="Foo")

          class Foo:
              def return_self(self: Self) -> Self:
                  ...
                  return self

     一般來說，如果某個東西回傳 ‘self’ 如上方的範例所示，你則應該使用
     ‘Self’ 做為回傳值的註釋。若 ‘Foo.return_self’ 被註釋為回傳 ‘"Foo"’，
     則型別檢查器應該推論這個從 ‘SubclassOfFoo.return_self’ 回傳的物件為
     ‘Foo’ 型別，而並非回傳 ‘SubclassOfFoo’ 型別。

     其他常見的使用案例包含：

        - *note classmethod: 14a. 被用來作為替代的建構函式 (constructor)
          並回傳 ‘cls’ 參數的實例。

        - 註釋一個回傳自己的 *note __enter__(): 56c. 方法。

     當類別被子類別化時，若方法不保證回傳一個子類別的實例，你不應該使用
     ‘Self’ 作為回傳註釋：

          class Eggs:
              # Self would be an incorrect return annotation here,
              # as the object returned is always an instance of Eggs,
              # even in subclasses
              def returns_eggs(self) -> "Eggs":
                  return Eggs()

     更多細節請見 PEP 673(4)。

     在 3.11 版被加入.

 -- 資料: typing.TypeAlias

     做為明確宣告一個*note 型別別名: 3fa. 的特別註釋。

     舉例來說：

          from typing import TypeAlias

          Factors: TypeAlias = list[int]

     ‘TypeAlias’ 在舊的 Python 版本中特別有用，其註釋別名可以用來進行傳
     遞參照 (forward reference)，因為對於型別檢查器來說，分辨這些別名與
     一般的變數賦值相當困難：

          from typing import Generic, TypeAlias, TypeVar

          T = TypeVar("T")

          # "Box" does not exist yet,
          # so we have to use quotes for the forward reference on Python <3.12.
          # Using ``TypeAlias`` tells the type checker that this is a type alias declaration,
          # not a variable assignment to a string.
          BoxOfStrings: TypeAlias = "Box[str]"

          class Box(Generic[T]):
              @classmethod
              def make_box_of_strings(cls) -> BoxOfStrings: ...

     更多細節請見 PEP 613(5)。

     在 3.10 版被加入.

     在 3.12 版之後被棄用: *note TypeAlias: 76d. 被棄用，請改用 *note
     type: 3de. 陳述式來建立 *note TypeAliasType: 3fb. 的實例，其自然可
     以支援傳遞參照的使用。請注意，雖然 *note TypeAlias: 76d. 以及 *note
     TypeAliasType: 3fb. 提供相似的用途且具有相似的名稱，他們是不同的，
     且後者不是前者的型別。現在還沒有移除 *note TypeAlias: 76d. 的計畫，
     但鼓勵使用者們遷移 (migrate) 至 *note type: 3de. 陳述式。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0695/

   (2) https://peps.python.org/pep-0675/

   (3) https://en.wikipedia.org/wiki/Bottom_type

   (4) https://peps.python.org/pep-0673/

   (5) https://peps.python.org/pep-0613/


File: python.info,  Node: 特別型式,  Next: Building generic types and type aliases,  Prev: 特別型別,  Up: 特別型別原語 primitive

5.26.1.15 特別型式
..................

這些在註釋中可以當作型別使用。他們全都支援 ‘[]’ 的下標使用，但每個都具有
獨特的語法。

 -- 資料: typing.Union

     聯集型別；‘Union[X, Y]’ 與 ‘X | Y’ 是相等的，且都意味著 X 或 Y 兩者
     其一。

     為了定義聯集，例如可以使用 ‘Union[int, str]’ 或是使用簡寫
     (shorthand) ‘int | str’。使用這種簡寫是非常推薦的。詳細請看：

        * 引數必須為型別且必須有至少一個。

        * 聯集中的聯集會是扁平化的 (flattened)，舉例來說：

               Union[Union[int, str], float] == Union[int, str, float]

        * 單一引數的聯集會消失不見，舉例來說：

               Union[int] == int  # The constructor actually returns int

        * 多餘的引數會被略過，舉例來說：

               Union[int, str, int] == Union[int, str] == int | str

        * 當比較聯集時，引數的順序會被忽略，舉例來說：

               Union[int, str] == Union[str, int]

        * 你不能建立 ‘Union’ 的子類別或是實例。

        * 你不能寫成 ‘Union[X][Y]’。

     在 3.7 版的變更: 請勿在 runtime 中將顯性子類別從聯集中移除。

     在 3.10 版的變更: 現在可以將聯集寫成 ‘X | Y’。請見*note
     聯集型別運算式: 766.。

 -- 資料: typing.Optional

     ‘Optional[X]’ 與 ‘X | None’ 是相等的（或是 ‘Union[X, None]’）。

     請注意，這與具有預設值的選擇性引數 (optional argument) 不是相同的概
     念。一個具有預設值的選擇性引數的型別註釋中不具有 ‘Optional’ 限定符
     (qualifier)，單純的因為它就是選擇性的。舉例來說：

          def foo(arg: int = 0) -> None:
              ...

     另一方面，如果一個顯性的值 ‘None’ 是被允許的，不論引數是不是選擇性
     的，‘Optional’ 都適用。舉例來說：

          def foo(arg: Optional[int] = None) -> None:
              ...

     在 3.10 版的變更: 現在可以將 Optional 寫成 ‘X | None’。請見*note
     聯集型別運算式: 766.。

 -- 資料: typing.Concatenate

     用於註釋高階函式的特別型式。

     ‘Concatenate’ 可以被用在*note 可呼叫物件: 2403.與 *note ParamSpec:
     142. 的接合 (conjunction) 並註釋一個高階的 Callable 物件可以新增、
     移除、轉換另一個 Callable 物件的參數。使用方法是依照這個格式
     ‘Concatenate[Arg1Type, Arg2Type, ..., ParamSpecVariable]’。
     ‘Concatenate’ 目前只在 *note Callable 物件: 2403.中第一個引數使用時
     有效。‘Concatenate’ 的最後一個參數必須為一個 *note ParamSpec: 142.
     或是刪節號 (‘...’)。

     舉例來說，註釋一個為裝飾過後的函式提供 *note threading.Lock: 156d.
     的裝飾器 ‘with_lock’，‘Concatenate’ 可以用於指出 ‘with_lock’ 預期一
     個 Callable 物件，該物件可以接受 ‘Lock’ 作為第一引數，並回傳一個具
     有不同型別簽名 Callable 物件。在這種情況下，*note ParamSpec: 142. 指
     出回傳的 Callable 物件的參數型別會依賴傳遞的 Callable 物件的參數型
     別：

          from collections.abc import Callable
          from threading import Lock
          from typing import Concatenate

          # Use this lock to ensure that only one thread is executing a function
          # at any time.
          my_lock = Lock()

          def with_lock[**P, R](f: Callable[Concatenate[Lock, P], R]) -> Callable[P, R]:
              '''A type-safe decorator which provides a lock.'''
              def inner(*args: P.args, **kwargs: P.kwargs) -> R:
                  # Provide the lock as the first argument.
                  return f(my_lock, *args, **kwargs)
              return inner

          @with_lock
          def sum_threadsafe(lock: Lock, numbers: list[float]) -> float:
              '''Add a list of numbers together in a thread-safe manner.'''
              with lock:
                  return sum(numbers)

          # We don't need to pass in the lock ourselves thanks to the decorator.
          sum_threadsafe([1.1, 2.2, 3.3])

     在 3.10 版被加入.

     也參考
     ......

        * PEP 612(1) - 參數技術規範變數

        * *note ParamSpec: 142.

        * *note 註釋 callable 物件: 2403.

 -- 資料: typing.Literal

     特殊型別格式，用於定義「文本型別 (literal type)」。

     ‘Literal’ 可以用於型別檢查器並指出註釋物件具有一個與提供的文本相同
     的值。

     舉例來說：

          def validate_simple(data: Any) -> Literal[True]:  # always returns True
              ...

          type Mode = Literal['r', 'rb', 'w', 'wb']
          def open_helper(file: str, mode: Mode) -> str:
              ...

          open_helper('/some/path', 'r')      # Passes type check
          open_helper('/other/path', 'typo')  # Error in type checker

     ‘Literal[...]’ 不可以進行子類別化。在 runtime 之中，任意的值是允許
     作為 ‘Literal[...]’ 的型別引數，但型別檢查器可能會加強限制。更多有
     關文本型別的詳細資訊請看 PEP 586(2)。

     在 3.8 版被加入.

     在 3.9.1 版的變更: ‘Literal’ 現在可以刪除重複 (de-deplicate) 的參數
     。‘Literal’ 物件的相等性比較不再依照相依性排序。‘Literal’ 物件現在
     會在相等性比較期間，若任一個其中的參數無法 *note hashable: 5b5. 時
     ，則會引發一個 *note TypeError: 4dd. 例外。

 -- 資料: typing.ClassVar

     特殊型別建構，用來標記類別變數。

     如同在 PEP 526(3) 中的介紹，一個變數註解被包裝在 ClassVar 中時，會
     指出一個給定的屬性 (attribute) 意圖被當作類別變數使用，且不該被設定
     成該類別的實例。使用方法如下：

          class Starship:
              stats: ClassVar[dict[str, int]] = {} # class variable
              damage: int = 10                     # instance variable

     *note ClassVar: 24b. 只接受型別請不得使用下標。

     *note ClassVar: 24b. 並不代表該類別本身，而且不應該和 *note
     isinstance(): 3e8. 或是 *note issubclass(): 765. 一起使用。*note
     ClassVar: 24b. 不會改變 Python runtime 的行為，但它可以被第三方的型
     別檢查器使用。舉例來說，一個型別檢查器可能會標記下方的程式碼為一個
     錯誤：

          enterprise_d = Starship(3000)
          enterprise_d.stats = {} # Error, setting class variable on instance
          Starship.stats = {}     # This is OK

     在 3.5.3 版被加入.

     在 3.13 版的變更: *note ClassVar: 24b. can now be nested in *note
     Final: 24c. and vice versa.

 -- 資料: typing.Final

     特殊型別建構，用來指出最終名稱給型別檢查器。

     最終名稱不可以在任何作用域 (scope) 中重新賦值。在類別作用域中宣告的
     最終名稱，不得在子類別中進行覆寫 (override)。

     舉例來說：

          MAX_SIZE: Final = 9000
          MAX_SIZE += 1  # Error reported by type checker

          class Connection:
              TIMEOUT: Final[int] = 10

          class FastConnector(Connection):
              TIMEOUT = 1  # Error reported by type checker

     這些屬性 (property) 不會在 runtime 時進行檢查。更多詳細資訊請看 PEP
     591(4)。

     在 3.8 版被加入.

     在 3.13 版的變更: *note Final: 24c. can now be nested in *note
     ClassVar: 24b. and vice versa.

 -- 資料: typing.Required

     特殊型別建構，用來標記一個 *note TypedDict: 146. 鍵值是必須的。

     主要用於 ‘total=False’ 的 TypedDict。更多細節請見 *note TypedDict:
     146. 與 PEP 655(5)。

     在 3.11 版被加入.

 -- 資料: typing.NotRequired

     特殊型別建構，用來標記一個 *note TypedDict: 146. 鍵值是可能消失的。

     更多細節請見 *note TypedDict: 146. 與 PEP 655(6)。

     在 3.11 版被加入.

 -- 資料: typing.ReadOnly

     A special typing construct to mark an item of a *note TypedDict:
     146. as read-only.

     舉例來說：

          class Movie(TypedDict):
             title: ReadOnly[str]
             year: int

          def mutate_movie(m: Movie) -> None:
             m["year"] = 1992  # allowed
             m["title"] = "The Matrix"  # typechecker error

     There is no runtime checking for this property.

     See *note TypedDict: 146. and PEP 705(7) for more details.

     在 3.13 版被加入.

 -- 資料: typing.Annotated

     Special typing form to add context-specific metadata to an
     annotation.

     Add metadata ‘x’ to a given type ‘T’ by using the annotation
     ‘Annotated[T, x]’.  Metadata added using ‘Annotated’ can be used by
     static analysis tools or at runtime.  At runtime, the metadata is
     stored in a ‘__metadata__’ attribute.

     If a library or tool encounters an annotation ‘Annotated[T, x]’ and
     has no special logic for the metadata, it should ignore the
     metadata and simply treat the annotation as ‘T’.  As such,
     ‘Annotated’ can be useful for code that wants to use annotations
     for purposes outside Python's static typing system.

     Using ‘Annotated[T, x]’ as an annotation still allows for static
     typechecking of ‘T’, as type checkers will simply ignore the
     metadata ‘x’.  In this way, ‘Annotated’ differs from the *note
     @no_type_check: 659. decorator, which can also be used for adding
     annotations outside the scope of the typing system, but completely
     disables typechecking for a function or class.

     The responsibility of how to interpret the metadata lies with the
     tool or library encountering an ‘Annotated’ annotation.  A tool or
     library encountering an ‘Annotated’ type can scan through the
     metadata elements to determine if they are of interest (e.g., using
     *note isinstance(): 3e8.).

      -- Describe: Annotated[<type>, <metadata>]

     Here is an example of how you might use ‘Annotated’ to add metadata
     to type annotations if you were doing range analysis:

          @dataclass
          class ValueRange:
              lo: int
              hi: int

          T1 = Annotated[int, ValueRange(-10, 5)]
          T2 = Annotated[T1, ValueRange(-20, 3)]

     Details of the syntax:

        * The first argument to ‘Annotated’ must be a valid type

        * Multiple metadata elements can be supplied (‘Annotated’
          supports variadic arguments):

               @dataclass
               class ctype:
                   kind: str

               Annotated[int, ValueRange(3, 10), ctype("char")]

          It is up to the tool consuming the annotations to decide
          whether the client is allowed to add multiple metadata
          elements to one annotation and how to merge those annotations.

        * ‘Annotated’ must be subscripted with at least two arguments (
          ‘Annotated[int]’ is not valid)

        * The order of the metadata elements is preserved and matters
          for equality checks:

               assert Annotated[int, ValueRange(3, 10), ctype("char")] != Annotated[
                   int, ctype("char"), ValueRange(3, 10)
               ]

        * Nested ‘Annotated’ types are flattened.  The order of the
          metadata elements starts with the innermost annotation:

               assert Annotated[Annotated[int, ValueRange(3, 10)], ctype("char")] == Annotated[
                   int, ValueRange(3, 10), ctype("char")
               ]

        * Duplicated metadata elements are not removed:

               assert Annotated[int, ValueRange(3, 10)] != Annotated[
                   int, ValueRange(3, 10), ValueRange(3, 10)
               ]

        * ‘Annotated’ can be used with nested and generic aliases:

               @dataclass
               class MaxLen:
                   value: int

               type Vec[T] = Annotated[list[tuple[T, T]], MaxLen(10)]

               # When used in a type annotation, a type checker will treat "V" the same as
               # ``Annotated[list[tuple[int, int]], MaxLen(10)]``:
               type V = Vec[int]

        * ‘Annotated’ cannot be used with an unpacked *note
          TypeVarTuple: 143.:

               type Variadic[*Ts] = Annotated[*Ts, Ann1]  # NOT valid

          這會等價於：

               Annotated[T1, T2, T3, ..., Ann1]

          where ‘T1’, ‘T2’, etc.  are *note TypeVars: 141.  This would
          be invalid: only one type should be passed to Annotated.

        * By default, *note get_type_hints(): 657. strips the metadata
          from annotations.  Pass ‘include_extras=True’ to have the
          metadata preserved:

               >>> from typing import Annotated, get_type_hints
               >>> def func(x: Annotated[int, "metadata"]) -> None: pass
               ...
               >>> get_type_hints(func)
               {'x': <class 'int'>, 'return': <class 'NoneType'>}
               >>> get_type_hints(func, include_extras=True)
               {'x': typing.Annotated[int, 'metadata'], 'return': <class 'NoneType'>}

        * At runtime, the metadata associated with an ‘Annotated’ type
          can be retrieved via the ‘__metadata__’ attribute:

               >>> from typing import Annotated
               >>> X = Annotated[int, "very", "important", "metadata"]
               >>> X
               typing.Annotated[int, 'very', 'important', 'metadata']
               >>> X.__metadata__
               ('very', 'important', 'metadata')

     也參考
     ......

     PEP 593(8) - Flexible function and variable annotations

          The PEP introducing ‘Annotated’ to the standard library.

     在 3.9 版被加入.

 -- 資料: typing.TypeIs

     Special typing construct for marking user-defined type predicate
     functions.

     ‘TypeIs’ can be used to annotate the return type of a user-defined
     type predicate function.  ‘TypeIs’ only accepts a single type
     argument.  At runtime, functions marked this way should return a
     boolean and take at least one positional argument.

     ‘TypeIs’ aims to benefit 'type narrowing' - a technique used by
     static type checkers to determine a more precise type of an
     expression within a program's code flow.  Usually type narrowing is
     done by analyzing conditional code flow and applying the narrowing
     to a block of code.  The conditional expression here is sometimes
     referred to as a "type predicate":

          def is_str(val: str | float):
              # "isinstance" type predicate
              if isinstance(val, str):
                  # Type of ``val`` is narrowed to ``str``
                  ...
              else:
                  # Else, type of ``val`` is narrowed to ``float``.
                  ...

     Sometimes it would be convenient to use a user-defined boolean
     function as a type predicate.  Such a function should use
     ‘TypeIs[...]’ or *note TypeGuard: 148. as its return type to alert
     static type checkers to this intention.  ‘TypeIs’ usually has more
     intuitive behavior than ‘TypeGuard’, but it cannot be used when the
     input and output types are incompatible (e.g., ‘list[object]’ to
     ‘list[int]’) or when the function does not return ‘True’ for all
     instances of the narrowed type.

     Using ‘-> TypeIs[NarrowedType]’ tells the static type checker that
     for a given function:

       1. The return value is a boolean.

       2. If the return value is ‘True’, the type of its argument is the
          intersection of the argument's original type and
          ‘NarrowedType’.

       3. If the return value is ‘False’, the type of its argument is
          narrowed to exclude ‘NarrowedType’.

     舉例來說：

          from typing import assert_type, final, TypeIs

          class Parent: pass
          class Child(Parent): pass
          @final
          class Unrelated: pass

          def is_parent(val: object) -> TypeIs[Parent]:
              return isinstance(val, Parent)

          def run(arg: Child | Unrelated):
              if is_parent(arg):
                  # Type of ``arg`` is narrowed to the intersection
                  # of ``Parent`` and ``Child``, which is equivalent to
                  # ``Child``.
                  assert_type(arg, Child)
              else:
                  # Type of ``arg`` is narrowed to exclude ``Parent``,
                  # so only ``Unrelated`` is left.
                  assert_type(arg, Unrelated)

     The type inside ‘TypeIs’ must be consistent with the type of the
     function's argument; if it is not, static type checkers will raise
     an error.  An incorrectly written ‘TypeIs’ function can lead to
     unsound behavior in the type system; it is the user's
     responsibility to write such functions in a type-safe manner.

     If a ‘TypeIs’ function is a class or instance method, then the type
     in ‘TypeIs’ maps to the type of the second parameter (after ‘cls’
     or ‘self’).

     In short, the form ‘def foo(arg: TypeA) -> TypeIs[TypeB]: ...’,
     means that if ‘foo(arg)’ returns ‘True’, then ‘arg’ is an instance
     of ‘TypeB’, and if it returns ‘False’, it is not an instance of
     ‘TypeB’.

     ‘TypeIs’ also works with type variables.  For more information, see
     PEP 742(9) (Narrowing types with ‘TypeIs’).

     在 3.13 版被加入.

 -- 資料: typing.TypeGuard

     Special typing construct for marking user-defined type predicate
     functions.

     Type predicate functions are user-defined functions that return
     whether their argument is an instance of a particular type.
     ‘TypeGuard’ works similarly to *note TypeIs: 147, but has subtly
     different effects on type checking behavior (see below).

     Using ‘-> TypeGuard’ tells the static type checker that for a given
     function:

       1. The return value is a boolean.

       2. If the return value is ‘True’, the type of its argument is the
          type inside ‘TypeGuard’.

     ‘TypeGuard’ also works with type variables.  See PEP 647(10) for
     more details.

     舉例來說：

          def is_str_list(val: list[object]) -> TypeGuard[list[str]]:
              '''Determines whether all objects in the list are strings'''
              return all(isinstance(x, str) for x in val)

          def func1(val: list[object]):
              if is_str_list(val):
                  # Type of ``val`` is narrowed to ``list[str]``.
                  print(" ".join(val))
              else:
                  # Type of ``val`` remains as ``list[object]``.
                  print("Not a list of strings!")

     ‘TypeIs’ and ‘TypeGuard’ differ in the following ways:

        * ‘TypeIs’ requires the narrowed type to be a subtype of the
          input type, while ‘TypeGuard’ does not.  The main reason is to
          allow for things like narrowing ‘list[object]’ to ‘list[str]’
          even though the latter is not a subtype of the former, since
          ‘list’ is invariant.

        * When a ‘TypeGuard’ function returns ‘True’, type checkers
          narrow the type of the variable to exactly the ‘TypeGuard’
          type.  When a ‘TypeIs’ function returns ‘True’, type checkers
          can infer a more precise type combining the previously known
          type of the variable with the ‘TypeIs’ type.  (Technically,
          this is known as an intersection type.)

        * When a ‘TypeGuard’ function returns ‘False’, type checkers
          cannot narrow the type of the variable at all.  When a
          ‘TypeIs’ function returns ‘False’, type checkers can narrow
          the type of the variable to exclude the ‘TypeIs’ type.

     在 3.10 版被加入.

 -- 資料: typing.Unpack

     Typing operator to conceptually mark an object as having been
     unpacked.

     For example, using the unpack operator ‘*’ on a *note type variable
     tuple: 3da1. is equivalent to using ‘Unpack’ to mark the type
     variable tuple as having been unpacked:

          Ts = TypeVarTuple('Ts')
          tup: tuple[*Ts]
          # Effectively does:
          tup: tuple[Unpack[Ts]]

     In fact, ‘Unpack’ can be used interchangeably with ‘*’ in the
     context of *note typing.TypeVarTuple: 143. and *note
     builtins.tuple: 322. types.  You might see ‘Unpack’ being used
     explicitly in older versions of Python, where ‘*’ couldn't be used
     in certain places:

          # In older versions of Python, TypeVarTuple and Unpack
          # are located in the `typing_extensions` backports package.
          from typing_extensions import TypeVarTuple, Unpack

          Ts = TypeVarTuple('Ts')
          tup: tuple[*Ts]         # Syntax error on Python <= 3.10!
          tup: tuple[Unpack[Ts]]  # Semantically equivalent, and backwards-compatible

     ‘Unpack’ can also be used along with *note typing.TypedDict: 146.
     for typing ‘**kwargs’ in a function signature:

          from typing import TypedDict, Unpack

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

          # This function expects two keyword arguments - `name` of type `str`
          # and `year` of type `int`.
          def foo(**kwargs: Unpack[Movie]): ...

     See PEP 692(11) for more details on using ‘Unpack’ for ‘**kwargs’
     typing.

     在 3.11 版被加入.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0612/

   (2) https://peps.python.org/pep-0586/

   (3) https://peps.python.org/pep-0526/

   (4) https://peps.python.org/pep-0591/

   (5) https://peps.python.org/pep-0655/

   (6) https://peps.python.org/pep-0655/

   (7) https://peps.python.org/pep-0705/

   (8) https://peps.python.org/pep-0593/

   (9) https://peps.python.org/pep-0742/

   (10) https://peps.python.org/pep-0647/

   (11) https://peps.python.org/pep-0692/


File: python.info,  Node: Building generic types and type aliases,  Next: Other special directives,  Prev: 特別型式,  Up: 特別型別原語 primitive

5.26.1.16 Building generic types and type aliases
.................................................

The following classes should not be used directly as annotations.  Their
intended purpose is to be building blocks for creating generic types and
type aliases.

These objects can be created through special syntax (*note type
parameter lists: 294. and the *note type: 3de. statement).  For
compatibility with Python 3.11 and earlier, they can also be created
without the dedicated syntax, as documented below.

 -- 類別: typing.Generic

     Abstract base class for generic types.

     A generic type is typically declared by adding a list of type
     parameters after the class name:

          class Mapping[KT, VT]:
              def __getitem__(self, key: KT) -> VT:
                  ...
                  # Etc.

     Such a class implicitly inherits from ‘Generic’.  The runtime
     semantics of this syntax are discussed in the *note Language
     Reference: 3f8.

     This class can then be used as follows:

          def lookup_name[X, Y](mapping: Mapping[X, Y], key: X, default: Y) -> Y:
              try:
                  return mapping[key]
              except KeyError:
                  return default

     Here the brackets after the function name indicate a *note generic
     function: 3f9.

     For backwards compatibility, generic classes can also be declared
     by explicitly inheriting from ‘Generic’.  In this case, the type
     parameters must be declared separately:

          KT = TypeVar('KT')
          VT = TypeVar('VT')

          class Mapping(Generic[KT, VT]):
              def __getitem__(self, key: KT) -> VT:
                  ...
                  # Etc.

 -- 類別: typing.TypeVar (name, *constraints, bound=None,
          covariant=False, contravariant=False, infer_variance=False,
          default=typing.NoDefault)

     Type variable.

     The preferred way to construct a type variable is via the dedicated
     syntax for *note generic functions: 3f9, *note generic classes:
     3f8, and *note generic type aliases: 3fc.:

          class Sequence[T]:  # T 是一個 TypeVar
              ...

     This syntax can also be used to create bound and constrained type
     variables:

          class StrSequence[S: str]:  # S is a TypeVar bound to str
              ...


          class StrOrBytesSequence[A: (str, bytes)]:  # A is a TypeVar constrained to str or bytes
              ...

     However, if desired, reusable type variables can also be
     constructed manually, like so:

          T = TypeVar('T')  # Can be anything
          S = TypeVar('S', bound=str)  # Can be any subtype of str
          A = TypeVar('A', str, bytes)  # Must be exactly str or bytes

     Type variables exist primarily for the benefit of static type
     checkers.  They serve as the parameters for generic types as well
     as for generic function and type alias definitions.  See *note
     Generic: 150c. for more information on generic types.  Generic
     functions work as follows:

          def repeat[T](x: T, n: int) -> Sequence[T]:
              """Return a list containing n references to x."""
              return [x]*n


          def print_capitalized[S: str](x: S) -> S:
              """Print x capitalized, and return x."""
              print(x.capitalize())
              return x


          def concatenate[A: (str, bytes)](x: A, y: A) -> A:
              """Add two strings or bytes objects together."""
              return x + y

     Note that type variables can be 'bound', 'constrained', or neither,
     but cannot be both bound 'and' constrained.

     The variance of type variables is inferred by type checkers when
     they are created through the *note type parameter syntax: 294. or
     when ‘infer_variance=True’ is passed.  Manually created type
     variables may be explicitly marked covariant or contravariant by
     passing ‘covariant=True’ or ‘contravariant=True’.  By default,
     manually created type variables are invariant.  See PEP 484(1) and
     PEP 695(2) for more details.

     Bound type variables and constrained type variables have different
     semantics in several important ways.  Using a 'bound' type variable
     means that the ‘TypeVar’ will be solved using the most specific
     type possible:

          x = print_capitalized('a string')
          reveal_type(x)  # revealed type is str

          class StringSubclass(str):
              pass

          y = print_capitalized(StringSubclass('another string'))
          reveal_type(y)  # revealed type is StringSubclass

          z = print_capitalized(45)  # error: int is not a subtype of str

     Type variables can be bound to concrete types, abstract types (ABCs
     or protocols), and even unions of types:

          # Can be anything with an __abs__ method
          def print_abs[T: SupportsAbs](arg: T) -> None:
              print("Absolute value:", abs(arg))

          U = TypeVar('U', bound=str|bytes)  # Can be any subtype of the union str|bytes
          V = TypeVar('V', bound=SupportsAbs)  # Can be anything with an __abs__ method
     Using a 'constrained' type variable, however, means that the
     ‘TypeVar’ can only ever be solved as being exactly one of the
     constraints given:

          a = concatenate('one', 'two')
          reveal_type(a)  # revealed type is str

          b = concatenate(StringSubclass('one'), StringSubclass('two'))
          reveal_type(b)  # revealed type is str, despite StringSubclass being passed in

          c = concatenate('one', b'two')  # error: type variable 'A' can be either str or bytes in a function call, but not both

     At runtime, ‘isinstance(x, T)’ will raise *note TypeError: 4dd.

      -- 屬性: __name__

          The name of the type variable.

      -- 屬性: __covariant__

          Whether the type var has been explicitly marked as covariant.

      -- 屬性: __contravariant__

          Whether the type var has been explicitly marked as
          contravariant.

      -- 屬性: __infer_variance__

          Whether the type variable's variance should be inferred by
          type checkers.

          在 3.12 版被加入.

      -- 屬性: __bound__

          The bound of the type variable, if any.

          在 3.12 版的變更: For type variables created through *note
          type parameter syntax: 294, the bound is evaluated only when
          the attribute is accessed, not when the type variable is
          created (see *note Lazy evaluation: 3fd.).

      -- 屬性: __constraints__

          A tuple containing the constraints of the type variable, if
          any.

          在 3.12 版的變更: For type variables created through *note
          type parameter syntax: 294, the constraints are evaluated only
          when the attribute is accessed, not when the type variable is
          created (see *note Lazy evaluation: 3fd.).

      -- 屬性: __default__

          The default value of the type variable, or *note
          typing.NoDefault: 247. if it has no default.

          在 3.13 版被加入.

      -- 方法: has_default ()

          Return whether or not the type variable has a default value.
          This is equivalent to checking whether *note __default__:
          3da9. is not the *note typing.NoDefault: 247. singleton,
          except that it does not force evaluation of the *note lazily
          evaluated: 3fd. default value.

          在 3.13 版被加入.

     在 3.12 版的變更: Type variables can now be declared using the
     *note type parameter: 294. syntax introduced by PEP 695(3).  The
     ‘infer_variance’ parameter was added.

     在 3.13 版的變更: Support for default values was added.

 -- 類別: typing.TypeVarTuple (name, *, default=typing.NoDefault)

     Type variable tuple.  A specialized form of *note type variable:
     3d98. that enables 'variadic' generics.

     Type variable tuples can be declared in *note type parameter lists:
     294. using a single asterisk (‘*’) before the name:

          def move_first_element_to_last[T, *Ts](tup: tuple[T, *Ts]) -> tuple[*Ts, T]:
              return (*tup[1:], tup[0])

     Or by explicitly invoking the ‘TypeVarTuple’ constructor:

          T = TypeVar("T")
          Ts = TypeVarTuple("Ts")

          def move_first_element_to_last(tup: tuple[T, *Ts]) -> tuple[*Ts, T]:
              return (*tup[1:], tup[0])

     A normal type variable enables parameterization with a single type.
     A type variable tuple, in contrast, allows parameterization with an
     'arbitrary' number of types by acting like an 'arbitrary' number of
     type variables wrapped in a tuple.  For example:

          # T is bound to int, Ts is bound to ()
          # Return value is (1,), which has type tuple[int]
          move_first_element_to_last(tup=(1,))

          # T is bound to int, Ts is bound to (str,)
          # Return value is ('spam', 1), which has type tuple[str, int]
          move_first_element_to_last(tup=(1, 'spam'))

          # T is bound to int, Ts is bound to (str, float)
          # Return value is ('spam', 3.0, 1), which has type tuple[str, float, int]
          move_first_element_to_last(tup=(1, 'spam', 3.0))

          # This fails to type check (and fails at runtime)
          # because tuple[()] is not compatible with tuple[T, *Ts]
          # (at least one element is required)
          move_first_element_to_last(tup=())

     Note the use of the unpacking operator ‘*’ in ‘tuple[T, *Ts]’.
     Conceptually, you can think of ‘Ts’ as a tuple of type variables
     ‘(T1, T2, ...)’.  ‘tuple[T, *Ts]’ would then become ‘tuple[T, *(T1,
     T2, ...)]’, which is equivalent to ‘tuple[T, T1, T2, ...]’.  (Note
     that in older versions of Python, you might see this written using
     *note Unpack: 1523. instead, as ‘Unpack[Ts]’.)

     Type variable tuples must 'always' be unpacked.  This helps
     distinguish type variable tuples from normal type variables:

          x: Ts          # Not valid
          x: tuple[Ts]   # Not valid
          x: tuple[*Ts]  # The correct way to do it

     Type variable tuples can be used in the same contexts as normal
     type variables.  For example, in class definitions, arguments, and
     return types:

          class Array[*Shape]:
              def __getitem__(self, key: tuple[*Shape]) -> float: ...
              def __abs__(self) -> "Array[*Shape]": ...
              def get_shape(self) -> tuple[*Shape]: ...

     Type variable tuples can be happily combined with normal type
     variables:

          class Array[DType, *Shape]:  # This is fine
              pass

          class Array2[*Shape, DType]:  # This would also be fine
              pass

          class Height: ...
          class Width: ...

          float_array_1d: Array[float, Height] = Array()     # Totally fine
          int_array_2d: Array[int, Height, Width] = Array()  # Yup, fine too

     However, note that at most one type variable tuple may appear in a
     single list of type arguments or type parameters:

          x: tuple[*Ts, *Ts]            # Not valid
          class Array[*Shape, *Shape]:  # Not valid
              pass

     Finally, an unpacked type variable tuple can be used as the type
     annotation of ‘*args’:

          def call_soon[*Ts](
              callback: Callable[[*Ts], None],
              *args: *Ts
          ) -> None:
              ...
              callback(*args)

     In contrast to non-unpacked annotations of ‘*args’ - e.g.  ‘*args:
     int’, which would specify that 'all' arguments are ‘int’ - ‘*args:
     *Ts’ enables reference to the types of the 'individual' arguments
     in ‘*args’.  Here, this allows us to ensure the types of the
     ‘*args’ passed to ‘call_soon’ match the types of the (positional)
     arguments of ‘callback’.

     See PEP 646(4) for more details on type variable tuples.

      -- 屬性: __name__

          The name of the type variable tuple.

      -- 屬性: __default__

          The default value of the type variable tuple, or *note
          typing.NoDefault: 247. if it has no default.

          在 3.13 版被加入.

      -- 方法: has_default ()

          Return whether or not the type variable tuple has a default
          value.  This is equivalent to checking whether *note
          __default__: 3dac. is not the *note typing.NoDefault: 247.
          singleton, except that it does not force evaluation of the
          *note lazily evaluated: 3fd. default value.

          在 3.13 版被加入.

     在 3.11 版被加入.

     在 3.12 版的變更: Type variable tuples can now be declared using
     the *note type parameter: 294. syntax introduced by PEP 695(5).

     在 3.13 版的變更: Support for default values was added.

 -- 類別: typing.ParamSpec (name, *, bound=None, covariant=False,
          contravariant=False, default=typing.NoDefault)

     Parameter specification variable.  A specialized version of *note
     type variables: 3d98.

     In *note type parameter lists: 294, parameter specifications can be
     declared with two asterisks (‘**’):

          type IntFunc[**P] = Callable[P, int]

     For compatibility with Python 3.11 and earlier, ‘ParamSpec’ objects
     can also be created as follows:

          P = ParamSpec('P')

     Parameter specification variables exist primarily for the benefit
     of static type checkers.  They are used to forward the parameter
     types of one callable to another callable - a pattern commonly
     found in higher order functions and decorators.  They are only
     valid when used in ‘Concatenate’, or as the first argument to
     ‘Callable’, or as parameters for user-defined Generics.  See *note
     Generic: 150c. for more information on generic types.

     For example, to add basic logging to a function, one can create a
     decorator ‘add_logging’ to log function calls.  The parameter
     specification variable tells the type checker that the callable
     passed into the decorator and the new callable returned by it have
     inter-dependent type parameters:

          from collections.abc import Callable
          import logging

          def add_logging[T, **P](f: Callable[P, T]) -> Callable[P, T]:
              '''A type-safe decorator to add logging to a function.'''
              def inner(*args: P.args, **kwargs: P.kwargs) -> T:
                  logging.info(f'{f.__name__} was called')
                  return f(*args, **kwargs)
              return inner

          @add_logging
          def add_two(x: float, y: float) -> float:
              '''Add two numbers together.'''
              return x + y

     Without ‘ParamSpec’, the simplest way to annotate this previously
     was to use a *note TypeVar: 141. with bound ‘Callable[..., Any]’.
     However this causes two problems:

       1. The type checker can't type check the ‘inner’ function because
          ‘*args’ and ‘**kwargs’ have to be typed *note Any: 651.

       2. *note cast(): 3dae. may be required in the body of the
          ‘add_logging’ decorator when returning the ‘inner’ function,
          or the static type checker must be told to ignore the ‘return
          inner’.

      -- 屬性: args

      -- 屬性: kwargs

          Since ‘ParamSpec’ captures both positional and keyword
          parameters, ‘P.args’ and ‘P.kwargs’ can be used to split a
          ‘ParamSpec’ into its components.  ‘P.args’ represents the
          tuple of positional parameters in a given call and should only
          be used to annotate ‘*args’.  ‘P.kwargs’ represents the
          mapping of keyword parameters to their values in a given call,
          and should be only be used to annotate ‘**kwargs’.  Both
          attributes require the annotated parameter to be in scope.  At
          runtime, ‘P.args’ and ‘P.kwargs’ are instances respectively of
          *note ParamSpecArgs: 76a. and *note ParamSpecKwargs: 76b.

      -- 屬性: __name__

          The name of the parameter specification.

      -- 屬性: __default__

          The default value of the parameter specification, or *note
          typing.NoDefault: 247. if it has no default.

          在 3.13 版被加入.

      -- 方法: has_default ()

          Return whether or not the parameter specification has a
          default value.  This is equivalent to checking whether *note
          __default__: 3db2. is not the *note typing.NoDefault: 247.
          singleton, except that it does not force evaluation of the
          *note lazily evaluated: 3fd. default value.

          在 3.13 版被加入.

     Parameter specification variables created with ‘covariant=True’ or
     ‘contravariant=True’ can be used to declare covariant or
     contravariant generic types.  The ‘bound’ argument is also
     accepted, similar to *note TypeVar: 141.  However the actual
     semantics of these keywords are yet to be decided.

     在 3.10 版被加入.

     在 3.12 版的變更: Parameter specifications can now be declared
     using the *note type parameter: 294. syntax introduced by PEP
     695(6).

     在 3.13 版的變更: Support for default values was added.

          備註: Only parameter specification variables defined in global
          scope can be pickled.

     也參考
     ......

        * PEP 612(7) - 參數技術規範變數

        * *note Concatenate: 768.

        * *note 註釋 callable 物件: 2403.

 -- 資料: typing.ParamSpecArgs
 -- 資料: typing.ParamSpecKwargs

     Arguments and keyword arguments attributes of a *note ParamSpec:
     142.  The ‘P.args’ attribute of a ‘ParamSpec’ is an instance of
     ‘ParamSpecArgs’, and ‘P.kwargs’ is an instance of
     ‘ParamSpecKwargs’.  They are intended for runtime introspection and
     have no special meaning to static type checkers.

     Calling *note get_origin(): 9ea. on either of these objects will
     return the original ‘ParamSpec’:

          >>> from typing import ParamSpec, get_origin
          >>> P = ParamSpec("P")
          >>> get_origin(P.args) is P
          True
          >>> get_origin(P.kwargs) is P
          True

     在 3.10 版被加入.

 -- 類別: typing.TypeAliasType (name, value, *, type_params=())

     The type of type aliases created through the *note type: 3de.
     statement.

     舉例來說：

          >>> type Alias = int
          >>> type(Alias)
          <class 'typing.TypeAliasType'>

     在 3.12 版被加入.

      -- 屬性: __name__

          The name of the type alias:

               >>> type Alias = int
               >>> Alias.__name__
               'Alias'

      -- 屬性: __module__

          The module in which the type alias was defined:

               >>> type Alias = int
               >>> Alias.__module__
               '__main__'

      -- 屬性: __type_params__

          The type parameters of the type alias, or an empty tuple if
          the alias is not generic:

               >>> type ListOrSet[T] = list[T] | set[T]
               >>> ListOrSet.__type_params__
               (T,)
               >>> type NotGeneric = int
               >>> NotGeneric.__type_params__
               ()

      -- 屬性: __value__

          The type alias's value.  This is *note lazily evaluated: 3fd,
          so names used in the definition of the alias are not resolved
          until the ‘__value__’ attribute is accessed:

               >>> type Mutually = Recursive
               >>> type Recursive = Mutually
               >>> Mutually
               Mutually
               >>> Recursive
               Recursive
               >>> Mutually.__value__
               Recursive
               >>> Recursive.__value__
               Mutually

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0484/

   (2) https://peps.python.org/pep-0695/

   (3) https://peps.python.org/pep-0695/

   (4) https://peps.python.org/pep-0646/

   (5) https://peps.python.org/pep-0695/

   (6) https://peps.python.org/pep-0695/

   (7) https://peps.python.org/pep-0612/


File: python.info,  Node: Other special directives,  Prev: Building generic types and type aliases,  Up: 特別型別原語 primitive

5.26.1.17 Other special directives
..................................

These functions and classes should not be used directly as annotations.
Their intended purpose is to be building blocks for creating and
declaring types.

 -- 類別: typing.NamedTuple

     Typed version of *note collections.namedtuple(): 1ae.

     Usage:

          class Employee(NamedTuple):
              name: str
              id: int

     這等價於：

          Employee = collections.namedtuple('Employee', ['name', 'id'])

     To give a field a default value, you can assign to it in the class
     body:

          class Employee(NamedTuple):
              name: str
              id: int = 3

          employee = Employee('Guido')
          assert employee.id == 3

     Fields with a default value must come after any fields without a
     default.

     The resulting class has an extra attribute ‘__annotations__’ giving
     a dict that maps the field names to the field types.  (The field
     names are in the ‘_fields’ attribute and the default values are in
     the ‘_field_defaults’ attribute, both of which are part of the
     *note namedtuple(): 1ae. API.)

     ‘NamedTuple’ subclasses can also have docstrings and methods:

          class Employee(NamedTuple):
              """Represents an employee."""
              name: str
              id: int = 3

              def __repr__(self) -> str:
                  return f'<Employee {self.name}, id={self.id}>'

     ‘NamedTuple’ subclasses can be generic:

          class Group[T](NamedTuple):
              key: T
              group: list[T]

     Backward-compatible usage:

          # For creating a generic NamedTuple on Python 3.11 or lower
          class Group(NamedTuple, Generic[T]):
              key: T
              group: list[T]

          # A functional syntax is also supported
          Employee = NamedTuple('Employee', [('name', str), ('id', int)])

     在 3.6 版的變更: Added support for PEP 526(1) variable annotation
     syntax.

     在 3.6.1 版的變更: Added support for default values, methods, and
     docstrings.

     在 3.8 版的變更: The ‘_field_types’ and ‘__annotations__’
     attributes are now regular dictionaries instead of instances of
     ‘OrderedDict’.

     在 3.9 版的變更: Removed the ‘_field_types’ attribute in favor of
     the more standard ‘__annotations__’ attribute which has the same
     information.

     在 3.11 版的變更: Added support for generic namedtuples.

     Deprecated since version 3.13, will be removed in version 3.15: The
     undocumented keyword argument syntax for creating NamedTuple
     classes (‘NT = NamedTuple("NT", x=int)’) is deprecated, and will be
     disallowed in 3.15.  Use the class-based syntax or the functional
     syntax instead.

     Deprecated since version 3.13, will be removed in version 3.15:
     When using the functional syntax to create a NamedTuple class,
     failing to pass a value to the 'fields' parameter (‘NT =
     NamedTuple("NT")’) is deprecated.  Passing ‘None’ to the 'fields'
     parameter (‘NT = NamedTuple("NT", None)’) is also deprecated.  Both
     will be disallowed in Python 3.15.  To create a NamedTuple class
     with 0 fields, use ‘class NT(NamedTuple): pass’ or ‘NT =
     NamedTuple("NT", [])’.

 -- 類別: typing.NewType (name, tp)

     Helper class to create low-overhead *note distinct types: 3d8c.

     A ‘NewType’ is considered a distinct type by a typechecker.  At
     runtime, however, calling a ‘NewType’ returns its argument
     unchanged.

     Usage:

          UserId = NewType('UserId', int)  # Declare the NewType "UserId"
          first_user = UserId(1)  # "UserId" returns the argument unchanged at runtime

      -- 屬性: __module__

          The module in which the new type is defined.

      -- 屬性: __name__

          The name of the new type.

      -- 屬性: __supertype__

          The type that the new type is based on.

     在 3.5.2 版被加入.

     在 3.10 版的變更: ‘NewType’ is now a class rather than a function.

 -- 類別: typing.Protocol (Generic)

     Base class for protocol classes.

     Protocol classes are defined like this:

          class Proto(Protocol):
              def meth(self) -> int:
                  ...

     Such classes are primarily used with static type checkers that
     recognize structural subtyping (static duck-typing), for example:

          class C:
              def meth(self) -> int:
                  return 0

          def func(x: Proto) -> int:
              return x.meth()

          func(C())  # Passes static type check

     See PEP 544(2) for more details.  Protocol classes decorated with
     *note runtime_checkable(): 3e9. (described later) act as
     simple-minded runtime protocols that check only the presence of
     given attributes, ignoring their type signatures.

     Protocol classes can be generic, for example:

          class GenProto[T](Protocol):
              def meth(self) -> T:
                  ...

     In code that needs to be compatible with Python 3.11 or older,
     generic Protocols can be written as follows:

          T = TypeVar("T")

          class GenProto(Protocol[T]):
              def meth(self) -> T:
                  ...

     在 3.8 版被加入.

 -- 函式: @typing.runtime_checkable

     Mark a protocol class as a runtime protocol.

     Such a protocol can be used with *note isinstance(): 3e8. and *note
     issubclass(): 765.  This raises *note TypeError: 4dd. when applied
     to a non-protocol class.  This allows a simple-minded structural
     check, very similar to "one trick ponies" in *note collections.abc:
     17. such as *note Iterable: 212a.  For example:

          @runtime_checkable
          class Closable(Protocol):
              def close(self): ...

          assert isinstance(open('/some/file'), Closable)

          @runtime_checkable
          class Named(Protocol):
              name: str

          import threading
          assert isinstance(threading.Thread(name='Bob'), Named)

          備註: ‘runtime_checkable()’ will check only the presence of
          the required methods or attributes, not their type signatures
          or types.  For example, *note ssl.SSLObject: b25. is a class,
          therefore it passes an *note issubclass(): 765. check against
          *note Callable: 2403.  However, the ‘ssl.SSLObject.__init__’
          method exists only to raise a *note TypeError: 4dd. with a
          more informative message, therefore making it impossible to
          call (instantiate) *note ssl.SSLObject: b25.

          備註: An *note isinstance(): 3e8. check against a
          runtime-checkable protocol can be surprisingly slow compared
          to an ‘isinstance()’ check against a non-protocol class.
          Consider using alternative idioms such as *note hasattr():
          479. calls for structural checks in performance-sensitive
          code.

     在 3.8 版被加入.

     在 3.12 版的變更: The internal implementation of *note
     isinstance(): 3e8. checks against runtime-checkable protocols now
     uses *note inspect.getattr_static(): 43c. to look up attributes
     (previously, *note hasattr(): 479. was used).  As a result, 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.

     在 3.12 版的變更: 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 *note
     isinstance(): 3e8. checks comparing objects to the protocol.  See
     *note "What's new in Python 3.12": 478. for more details.

 -- 類別: typing.TypedDict (dict)

     Special construct to add type hints to a dictionary.  At runtime it
     is a plain *note dict: 23b.

     ‘TypedDict’ declares a dictionary type that expects all of its
     instances to have a certain set of keys, where each key is
     associated with a value of a consistent type.  This expectation is
     not checked at runtime but is only enforced by type checkers.
     Usage:

          class Point2D(TypedDict):
              x: int
              y: int
              label: str

          a: Point2D = {'x': 1, 'y': 2, 'label': 'good'}  # OK
          b: Point2D = {'z': 3, 'label': 'bad'}           # Fails type check

          assert Point2D(x=1, y=2, label='first') == dict(x=1, y=2, label='first')

     An alternative way to create a ‘TypedDict’ is by using
     function-call syntax.  The second argument must be a literal *note
     dict: 23b.:

          Point2D = TypedDict('Point2D', {'x': int, 'y': int, 'label': str})

     This functional syntax allows defining keys which are not valid
     *note identifiers: 1d86, for example because they are keywords or
     contain hyphens:

          # raises SyntaxError
          class Point2D(TypedDict):
              in: int  # 'in' is a keyword
              x-y: int  # name with hyphens

          # OK, functional syntax
          Point2D = TypedDict('Point2D', {'in': int, 'x-y': int})

     By default, all keys must be present in a ‘TypedDict’.  It is
     possible to mark individual keys as non-required using *note
     NotRequired: 569.:

          class Point2D(TypedDict):
              x: int
              y: int
              label: NotRequired[str]

          # Alternative syntax
          Point2D = TypedDict('Point2D', {'x': int, 'y': int, 'label': NotRequired[str]})

     This means that a ‘Point2D’ ‘TypedDict’ can have the ‘label’ key
     omitted.

     It is also possible to mark all keys as non-required by default by
     specifying a totality of ‘False’:

          class Point2D(TypedDict, total=False):
              x: int
              y: int

          # Alternative syntax
          Point2D = TypedDict('Point2D', {'x': int, 'y': int}, total=False)

     This means that a ‘Point2D’ ‘TypedDict’ can have any of the keys
     omitted.  A type checker is only expected to support a literal
     ‘False’ or ‘True’ as the value of the ‘total’ argument.  ‘True’ is
     the default, and makes all items defined in the class body
     required.

     Individual keys of a ‘total=False’ ‘TypedDict’ can be marked as
     required using *note Required: 568.:

          class Point2D(TypedDict, total=False):
              x: Required[int]
              y: Required[int]
              label: str

          # Alternative syntax
          Point2D = TypedDict('Point2D', {
              'x': Required[int],
              'y': Required[int],
              'label': str
          }, total=False)

     It is possible for a ‘TypedDict’ type to inherit from one or more
     other ‘TypedDict’ types using the class-based syntax.  Usage:

          class Point3D(Point2D):
              z: int

     ‘Point3D’ has three items: ‘x’, ‘y’ and ‘z’.  It is equivalent to
     this definition:

          class Point3D(TypedDict):
              x: int
              y: int
              z: int

     A ‘TypedDict’ cannot inherit from a non-‘TypedDict’ class, except
     for *note Generic: 150c.  For example:

          class X(TypedDict):
              x: int

          class Y(TypedDict):
              y: int

          class Z(object): pass  # A non-TypedDict class

          class XY(X, Y): pass  # OK

          class XZ(X, Z): pass  # raises TypeError

     A ‘TypedDict’ can be generic:

          class Group[T](TypedDict):
              key: T
              group: list[T]

     To create a generic ‘TypedDict’ that is compatible with Python 3.11
     or lower, inherit from *note Generic: 150c. explicitly:

          T = TypeVar("T")

          class Group(TypedDict, Generic[T]):
              key: T
              group: list[T]

     A ‘TypedDict’ can be introspected via annotations dicts (see *note
     註釋 (annotation) 最佳實踐: 77d. for more information on
     annotations best practices), *note __total__: 3dbc, *note
     __required_keys__: 3dbd, and *note __optional_keys__: 3dbe.

      -- 屬性: __total__

          ‘Point2D.__total__’ gives the value of the ‘total’ argument.
          Example:

               >>> from typing import TypedDict
               >>> class Point2D(TypedDict): pass
               >>> Point2D.__total__
               True
               >>> class Point2D(TypedDict, total=False): pass
               >>> Point2D.__total__
               False
               >>> class Point3D(Point2D): pass
               >>> Point3D.__total__
               True

          This attribute reflects 'only' the value of the ‘total’
          argument to the current ‘TypedDict’ class, not whether the
          class is semantically total.  For example, a ‘TypedDict’ with
          ‘__total__’ set to ‘True’ may have keys marked with *note
          NotRequired: 569, or it may inherit from another ‘TypedDict’
          with ‘total=False’.  Therefore, it is generally better to use
          *note __required_keys__: 3dbd. and *note __optional_keys__:
          3dbe. for introspection.

      -- 屬性: __required_keys__

          在 3.9 版被加入.

      -- 屬性: __optional_keys__

          ‘Point2D.__required_keys__’ and ‘Point2D.__optional_keys__’
          return *note frozenset: 57e. objects containing required and
          non-required keys, respectively.

          Keys marked with *note Required: 568. will always appear in
          ‘__required_keys__’ and keys marked with *note NotRequired:
          569. will always appear in ‘__optional_keys__’.

          For backwards compatibility with Python 3.10 and below, it is
          also possible to use inheritance to declare both required and
          non-required keys in the same ‘TypedDict’ .  This is done by
          declaring a ‘TypedDict’ with one value for the ‘total’
          argument and then inheriting from it in another ‘TypedDict’
          with a different value for ‘total’:

               >>> class Point2D(TypedDict, total=False):
               ...     x: int
               ...     y: int
               ...
               >>> class Point3D(Point2D):
               ...     z: int
               ...
               >>> Point3D.__required_keys__ == frozenset({'z'})
               True
               >>> Point3D.__optional_keys__ == frozenset({'x', 'y'})
               True

          在 3.9 版被加入.

               備註: If ‘from __future__ import annotations’ is used or
               if annotations are given as strings, annotations are not
               evaluated when the ‘TypedDict’ is defined.  Therefore,
               the runtime introspection that ‘__required_keys__’ and
               ‘__optional_keys__’ rely on may not work properly, and
               the values of the attributes may be incorrect.

     Support for *note ReadOnly: 145. is reflected in the following
     attributes:

      -- 屬性: __readonly_keys__

          A *note frozenset: 57e. containing the names of all read-only
          keys.  Keys are read-only if they carry the *note ReadOnly:
          145. qualifier.

          在 3.13 版被加入.

      -- 屬性: __mutable_keys__

          A *note frozenset: 57e. containing the names of all mutable
          keys.  Keys are mutable if they do not carry the *note
          ReadOnly: 145. qualifier.

          在 3.13 版被加入.

     See PEP 589(3) for more examples and detailed rules of using
     ‘TypedDict’.

     在 3.8 版被加入.

     在 3.11 版的變更: Added support for marking individual keys as
     *note Required: 568. or *note NotRequired: 569.  See PEP 655(4).

     在 3.11 版的變更: Added support for generic ‘TypedDict’s.

     在 3.13 版的變更: Removed support for the keyword-argument method
     of creating ‘TypedDict’s.

     在 3.13 版的變更: Support for the *note ReadOnly: 145. qualifier
     was added.

     Deprecated since version 3.13, will be removed in version 3.15:
     When using the functional syntax to create a TypedDict class,
     failing to pass a value to the 'fields' parameter (‘TD =
     TypedDict("TD")’) is deprecated.  Passing ‘None’ to the 'fields'
     parameter (‘TD = TypedDict("TD", None)’) is also deprecated.  Both
     will be disallowed in Python 3.15.  To create a TypedDict class
     with 0 fields, use ‘class TD(TypedDict): pass’ or ‘TD =
     TypedDict("TD", {})’.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0526/

   (2) https://peps.python.org/pep-0544/

   (3) https://peps.python.org/pep-0589/

   (4) https://peps.python.org/pep-0655/


File: python.info,  Node: 協定<2>,  Next: ABCs for working with IO,  Prev: 特別型別原語 primitive,  Up: 模組內容<7>

5.26.1.18 協定
..............

The following protocols are provided by the typing module.  All are
decorated with *note @runtime_checkable: 3e9.

 -- 類別: typing.SupportsAbs

     An ABC with one abstract method ‘__abs__’ that is covariant in its
     return type.

 -- 類別: typing.SupportsBytes

     一個有抽象方法 ‘__bytes__’ 的 ABC。

 -- 類別: typing.SupportsComplex

     一個有抽象方法 ‘__complex__’ 的 ABC。

 -- 類別: typing.SupportsFloat

     一個有抽象方法 ‘__float__’ 的 ABC。

 -- 類別: typing.SupportsIndex

     一個有抽象方法 ‘__index__’ 的 ABC。

     在 3.8 版被加入.

 -- 類別: typing.SupportsInt

     一個有抽象方法 ‘__int__’ 的 ABC。

 -- 類別: typing.SupportsRound

     An ABC with one abstract method ‘__round__’ that is covariant in
     its return type.


File: python.info,  Node: ABCs for working with IO,  Next: 函式與裝飾器,  Prev: 協定<2>,  Up: 模組內容<7>

5.26.1.19 ABCs for working with IO
..................................

 -- 類別: typing.IO
 -- 類別: typing.TextIO
 -- 類別: typing.BinaryIO

     Generic type ‘IO[AnyStr]’ and its subclasses ‘TextIO(IO[str])’ and
     ‘BinaryIO(IO[bytes])’ represent the types of I/O streams such as
     returned by *note open(): 4c0.


File: python.info,  Node: 函式與裝飾器,  Next: Introspection helpers,  Prev: ABCs for working with IO,  Up: 模組內容<7>

5.26.1.20 函式與裝飾器
......................

 -- 函式: typing.cast (typ, val)

     Cast a value to a type.

     This returns the value unchanged.  To the type checker this signals
     that the return value has the designated type, but at runtime we
     intentionally don't check anything (we want this to be as fast as
     possible).

 -- 函式: typing.assert_type (val, typ, /)

     Ask a static type checker to confirm that 'val' has an inferred
     type of 'typ'.

     At runtime this does nothing: it returns the first argument
     unchanged with no checks or side effects, no matter the actual type
     of the argument.

     When a static type checker encounters a call to ‘assert_type()’, it
     emits an error if the value is not of the specified type:

          def greet(name: str) -> None:
              assert_type(name, str)  # OK, inferred type of `name` is `str`
              assert_type(name, int)  # type checker error

     This function is useful for ensuring the type checker's
     understanding of a script is in line with the developer's
     intentions:

          def complex_function(arg: object):
              # Do some complex type-narrowing logic,
              # after which we hope the inferred type will be `int`
              ...
              # Test whether the type checker correctly understands our function
              assert_type(arg, int)

     在 3.11 版被加入.

 -- 函式: typing.assert_never (arg, /)

     Ask a static type checker to confirm that a line of code is
     unreachable.

     舉例來說：

          def int_or_str(arg: int | str) -> None:
              match arg:
                  case int():
                      print("It's an int")
                  case str():
                      print("It's a str")
                  case _ as unreachable:
                      assert_never(unreachable)

     Here, the annotations allow the type checker to infer that the last
     case can never execute, because ‘arg’ is either an *note int: 23c.
     or a *note str: 3f2, and both options are covered by earlier cases.

     If a type checker finds that a call to ‘assert_never()’ is
     reachable, it will emit an error.  For example, if the type
     annotation for ‘arg’ was instead ‘int | str | float’, the type
     checker would emit an error pointing out that ‘unreachable’ is of
     type *note float: 2c8.  For a call to ‘assert_never’ to pass type
     checking, the inferred type of the argument passed in must be the
     bottom type, *note Never: 64d, and nothing else.

     At runtime, this throws an exception when called.

     也參考
     ......

     Unreachable Code and Exhaustiveness Checking(1) has more
     information about exhaustiveness checking with static typing.

     在 3.11 版被加入.

 -- 函式: typing.reveal_type (obj, /)

     Ask a static type checker to reveal the inferred type of an
     expression.

     When a static type checker encounters a call to this function, it
     emits a diagnostic with the inferred type of the argument.  For
     example:

          x: int = 1
          reveal_type(x)  # Revealed type is "builtins.int"

     This can be useful when you want to debug how your type checker
     handles a particular piece of code.

     At runtime, this function prints the runtime type of its argument
     to *note sys.stderr: 8dd. and returns the argument unchanged
     (allowing the call to be used within an expression):

          x = reveal_type(1)  # 印出 "Runtime type is int"
          print(x)  # 印出 "1"

     Note that the runtime type may be different from (more or less
     specific than) the type statically inferred by a type checker.

     Most type checkers support ‘reveal_type()’ anywhere, even if the
     name is not imported from ‘typing’.  Importing the name from
     ‘typing’, however, allows your code to run without runtime errors
     and communicates intent more clearly.

     在 3.11 版被加入.

 -- 函式: @typing.dataclass_transform (*, eq_default=True,
          order_default=False, kw_only_default=False,
          frozen_default=False, field_specifiers=(), **kwargs)

     Decorator to mark an object as providing *note dataclass: 1af.-like
     behavior.

     ‘dataclass_transform’ may be used to decorate a class, metaclass,
     or a function that is itself a decorator.  The presence of
     ‘@dataclass_transform()’ tells a static type checker that the
     decorated object performs runtime "magic" that transforms a class
     in a similar way to *note @dataclasses.dataclass: 1af.

     Example usage with a decorator function:

          @dataclass_transform()
          def create_model[T](cls: type[T]) -> type[T]:
              ...
              return cls

          @create_model
          class CustomerModel:
              id: int
              name: str

     On a base class:

          @dataclass_transform()
          class ModelBase: ...

          class CustomerModel(ModelBase):
              id: int
              name: str

     On a metaclass:

          @dataclass_transform()
          class ModelMeta(type): ...

          class ModelBase(metaclass=ModelMeta): ...

          class CustomerModel(ModelBase):
              id: int
              name: str

     The ‘CustomerModel’ classes defined above will be treated by type
     checkers similarly to classes created with *note
     @dataclasses.dataclass: 1af.  For example, type checkers will
     assume these classes have ‘__init__’ methods that accept ‘id’ and
     ‘name’.

     The decorated class, metaclass, or function may accept the
     following bool arguments which type checkers will assume have the
     same effect as they would have on the *note @dataclasses.dataclass:
     1af. decorator: ‘init’, ‘eq’, ‘order’, ‘unsafe_hash’, ‘frozen’,
     ‘match_args’, ‘kw_only’, and ‘slots’.  It must be possible for the
     value of these arguments (‘True’ or ‘False’) to be statically
     evaluated.

     The arguments to the ‘dataclass_transform’ decorator can be used to
     customize the default behaviors of the decorated class, metaclass,
     or function:


     參數:

        * ‘eq_default’ (*note bool: 40e.) - Indicates whether the ‘eq’
          parameter is assumed to be ‘True’ or ‘False’ if it is omitted
          by the caller.  Defaults to ‘True’.

        * ‘order_default’ (*note bool: 40e.) - Indicates whether the
          ‘order’ parameter is assumed to be ‘True’ or ‘False’ if it is
          omitted by the caller.  Defaults to ‘False’.

        * ‘kw_only_default’ (*note bool: 40e.) - Indicates whether the
          ‘kw_only’ parameter is assumed to be ‘True’ or ‘False’ if it
          is omitted by the caller.  Defaults to ‘False’.

        * ‘frozen_default’ (*note bool: 40e.) - Indicates whether the
          ‘frozen’ parameter is assumed to be ‘True’ or ‘False’ if it is
          omitted by the caller.  Defaults to ‘False’.

          在 3.12 版被加入.

        * ‘field_specifiers’ (*note tuple: 322.‘[’*note Callable:
          78e.‘[’‘...’‘, ’‘Any’‘]’‘, ’‘...’‘]’) - Specifies a static
          list of supported classes or functions that describe fields,
          similar to *note dataclasses.field(): 1926.  Defaults to ‘()’.

        * ‘**kwargs’ (‘Any’) - Arbitrary other keyword arguments are
          accepted in order to allow for possible future extensions.

     Type checkers recognize the following optional parameters on field
     specifiers: 'Recognised parameters for field specifiers'

     Parameter name           Description
                              
     --------------------------------------------------------------------------------------------------------------
                              
     ‘init’                   Indicates whether the field should be included in the synthesized ‘__init__’
                              method.  If unspecified, ‘init’ defaults to ‘True’.
                              
                              
     ‘default’                Provides the default value for the field.
                              
                              
     ‘default_factory’        Provides a runtime callback that returns the default value for the field.  If
                              neither ‘default’ nor ‘default_factory’ are specified, the field is assumed to
                              have no default value and must be provided a value when the class is instantiated.
                              
                              
     ‘factory’                An alias for the ‘default_factory’ parameter on field specifiers.
                              
                              
     ‘kw_only’                Indicates whether the field should be marked as keyword-only.  If ‘True’, the
                              field will be keyword-only.  If ‘False’, it will not be keyword-only.  If
                              unspecified, the value of the ‘kw_only’ parameter on the object decorated with
                              ‘dataclass_transform’ will be used, or if that is unspecified, the value of
                              ‘kw_only_default’ on ‘dataclass_transform’ will be used.
                              
                              
     ‘alias’                  Provides an alternative name for the field.  This alternative name is used in the
                              synthesized ‘__init__’ method.
                              

     At runtime, this decorator records its arguments in the
     ‘__dataclass_transform__’ attribute on the decorated object.  It
     has no other runtime effect.

     更多細節請見 PEP 681(2)。

     在 3.11 版被加入.

 -- 函式: @typing.overload

     Decorator for creating overloaded functions and methods.

     The ‘@overload’ decorator allows describing functions and methods
     that support multiple different combinations of argument types.  A
     series of ‘@overload’-decorated definitions must be followed by
     exactly one non-‘@overload’-decorated definition (for the same
     function/method).

     ‘@overload’-decorated definitions are for the benefit of the type
     checker only, since they will be overwritten by the
     non-‘@overload’-decorated definition.  The
     non-‘@overload’-decorated definition, meanwhile, will be used at
     runtime but should be ignored by a type checker.  At runtime,
     calling an ‘@overload’-decorated function directly will raise *note
     NotImplementedError: 20d.

     An example of overload that gives a more precise type than can be
     expressed using a union or a type variable:

          @overload
          def process(response: None) -> None:
              ...
          @overload
          def process(response: int) -> tuple[int, str]:
              ...
          @overload
          def process(response: bytes) -> str:
              ...
          def process(response):
              ...  # actual implementation goes here

     See PEP 484(3) for more details and comparison with other typing
     semantics.

     在 3.11 版的變更: Overloaded functions can now be introspected at
     runtime using *note get_overloads(): 653.

 -- 函式: typing.get_overloads (func)

     Return a sequence of *note @overload: 3d8f.-decorated definitions
     for 'func'.

     'func' is the function object for the implementation of the
     overloaded function.  For example, given the definition of
     ‘process’ in the documentation for *note @overload: 3d8f,
     ‘get_overloads(process)’ will return a sequence of three function
     objects for the three defined overloads.  If called on a function
     with no overloads, ‘get_overloads()’ returns an empty sequence.

     ‘get_overloads()’ can be used for introspecting an overloaded
     function at runtime.

     在 3.11 版被加入.

 -- 函式: typing.clear_overloads ()

     Clear all registered overloads in the internal registry.

     This can be used to reclaim the memory used by the registry.

     在 3.11 版被加入.

 -- 函式: @typing.final

     Decorator to indicate final methods and final classes.

     Decorating a method with ‘@final’ indicates to a type checker that
     the method cannot be overridden in a subclass.  Decorating a class
     with ‘@final’ indicates that it cannot be subclassed.

     舉例來說：

          class Base:
              @final
              def done(self) -> None:
                  ...
          class Sub(Base):
              def done(self) -> None:  # Error reported by type checker
                  ...

          @final
          class Leaf:
              ...
          class Other(Leaf):  # Error reported by type checker
              ...

     這些屬性 (property) 不會在 runtime 時進行檢查。更多詳細資訊請看 PEP
     591(4)。

     在 3.8 版被加入.

     在 3.11 版的變更: The decorator will now attempt to set a
     ‘__final__’ attribute to ‘True’ on the decorated object.  Thus, a
     check like ‘if getattr(obj, "__final__", False)’ can be used at
     runtime to determine whether an object ‘obj’ has been marked as
     final.  If the decorated object does not support setting
     attributes, the decorator returns the object unchanged without
     raising an exception.

 -- 函式: @typing.no_type_check

     Decorator to indicate that annotations are not type hints.

     This works as a class or function *note decorator: 6d5.  With a
     class, it applies recursively to all methods and classes defined in
     that class (but not to methods defined in its superclasses or
     subclasses).  Type checkers will ignore all annotations in a
     function or class with this decorator.

     ‘@no_type_check’ mutates the decorated object in place.

 -- 函式: @typing.no_type_check_decorator

     Decorator to give another decorator the *note no_type_check(): 659.
     effect.

     This wraps the decorator with something that wraps the decorated
     function in *note no_type_check(): 659.

     Deprecated since version 3.13, will be removed in version 3.15: No
     type checker ever added support for ‘@no_type_check_decorator’.  It
     is therefore deprecated, and will be removed in Python 3.15.

 -- 函式: @typing.override

     Decorator to indicate that a method in a subclass is intended to
     override a method or attribute in a superclass.

     Type checkers should emit an error if a method decorated with
     ‘@override’ does not, in fact, override anything.  This helps
     prevent bugs that may occur when a base class is changed without an
     equivalent change to a child class.

     舉例來說：

          class Base:
              def log_status(self) -> None:
                  ...

          class Sub(Base):
              @override
              def log_status(self) -> None:  # Okay: overrides Base.log_status
                  ...

              @override
              def done(self) -> None:  # Error reported by type checker
                  ...

     There is no runtime checking of this property.

     The decorator will attempt to set an ‘__override__’ attribute to
     ‘True’ on the decorated object.  Thus, a check like ‘if
     getattr(obj, "__override__", False)’ can be used at runtime to
     determine whether an object ‘obj’ has been marked as an override.
     If the decorated object does not support setting attributes, the
     decorator returns the object unchanged without raising an
     exception.

     更多細節請見 PEP 698(5)。

     在 3.12 版被加入.

 -- 函式: @typing.type_check_only

     Decorator to mark a class or function as unavailable at runtime.

     This decorator is itself not available at runtime.  It is mainly
     intended to mark classes that are defined in type stub files if an
     implementation returns an instance of a private class:

          @type_check_only
          class Response:  # private or not available at runtime
              code: int
              def get_header(self, name: str) -> str: ...

          def fetch_response() -> Response: ...

     Note that returning instances of private classes is not
     recommended.  It is usually preferable to make such classes public.

   ---------- Footnotes ----------

   (1) https://typing.readthedocs.io/en/latest/source/unreachable.html

   (2) https://peps.python.org/pep-0681/

   (3) https://peps.python.org/pep-0484/

   (4) https://peps.python.org/pep-0591/

   (5) https://peps.python.org/pep-0698/


File: python.info,  Node: Introspection helpers,  Next: 常數<9>,  Prev: 函式與裝飾器,  Up: 模組內容<7>

5.26.1.21 Introspection helpers
...............................

 -- 函式: typing.get_type_hints (obj, globalns=None, localns=None,
          include_extras=False)

     Return a dictionary containing type hints for a function, method,
     module or class object.

     This is often the same as ‘obj.__annotations__’, but this function
     makes the following changes to the annotations dictionary:

        * Forward references encoded as string literals or *note
          ForwardRef: 1748. objects are handled by evaluating them in
          'globalns', 'localns', and (where applicable) 'obj"s *note
          type parameter: 294. namespace.  If 'globalns' or 'localns' is
          not given, appropriate namespace dictionaries are inferred
          from 'obj'.

        * ‘None’ is replaced with *note types.NoneType: 7f6.

        * If *note @no_type_check: 659. has been applied to 'obj', an
          empty dictionary is returned.

        * If 'obj' is a class ‘C’, the function returns a dictionary
          that merges annotations from ‘C’'s base classes with those on
          ‘C’ directly.  This is done by traversing ‘C.__mro__’ and
          iteratively combining ‘__annotations__’ dictionaries.
          Annotations on classes appearing earlier in the *note method
          resolution order: 205c. always take precedence over
          annotations on classes appearing later in the method
          resolution order.

        * The function recursively replaces all occurrences of
          ‘Annotated[T, ...]’ with ‘T’, unless 'include_extras' is set
          to ‘True’ (see *note Annotated: 8e1. for more information).

     See also *note inspect.get_annotations(): 7b7, a lower-level
     function that returns annotations more directly.

          備註: If any forward references in the annotations of 'obj'
          are not resolvable or are not valid Python code, this function
          will raise an exception such as *note NameError: 3e5.  For
          example, this can happen with imported *note type aliases:
          3fa. that include forward references, or with names imported
          under *note if TYPE_CHECKING: c9b.

     在 3.9 版的變更: 新增 ‘include_extras’ 參數（如 PEP 593(1) 中所述）
     。更多資訊請見 *note Annotated: 8e1. 的文件。

     在 3.11 版的變更: Previously, ‘Optional[t]’ was added for function
     and method annotations if a default value equal to ‘None’ was set.
     Now the annotation is returned unchanged.

 -- 函式: typing.get_origin (tp)

     Get the unsubscripted version of a type: for a typing object of the
     form ‘X[Y, Z, ...]’ return ‘X’.

     If ‘X’ is a typing-module alias for a builtin or *note collections:
     16. class, it will be normalized to the original class.  If ‘X’ is
     an instance of *note ParamSpecArgs: 76a. or *note ParamSpecKwargs:
     76b, return the underlying *note ParamSpec: 142.  Return ‘None’ for
     unsupported objects.

     舉例：

          assert get_origin(str) is None
          assert get_origin(Dict[str, int]) is dict
          assert get_origin(Union[int, str]) is Union
          P = ParamSpec('P')
          assert get_origin(P.args) is P
          assert get_origin(P.kwargs) is P

     在 3.8 版被加入.

 -- 函式: typing.get_args (tp)

     Get type arguments with all substitutions performed: for a typing
     object of the form ‘X[Y, Z, ...]’ return ‘(Y, Z, ...)’.

     If ‘X’ is a union or *note Literal: 7f9. contained in another
     generic type, the order of ‘(Y, Z, ...)’ may be different from the
     order of the original arguments ‘[Y, Z, ...]’ due to type caching.
     Return ‘()’ for unsupported objects.

     舉例：

          assert get_args(int) == ()
          assert get_args(Dict[int, str]) == (int, str)
          assert get_args(Union[int, str]) == (int, str)

     在 3.8 版被加入.

 -- 函式: typing.get_protocol_members (tp)

     Return the set of members defined in a *note Protocol: 249.

          >>> from typing import Protocol, get_protocol_members
          >>> class P(Protocol):
          ...     def a(self) -> str: ...
          ...     b: int
          >>> get_protocol_members(P) == frozenset({'a', 'b'})
          True

     Raise *note TypeError: 4dd. for arguments that are not Protocols.

     在 3.13 版被加入.

 -- 函式: typing.is_protocol (tp)

     Determine if a type is a *note Protocol: 249.

     舉例來說：

          class P(Protocol):
              def a(self) -> str: ...
              b: int

          is_protocol(P)    # => True
          is_protocol(int)  # => False

     在 3.13 版被加入.

 -- 函式: typing.is_typeddict (tp)

     Check if a type is a *note TypedDict: 146.

     舉例來說：

          class Film(TypedDict):
              title: str
              year: int

          assert is_typeddict(Film)
          assert not is_typeddict(list | str)

          # TypedDict is a factory for creating typed dicts,
          # not a typed dict itself
          assert not is_typeddict(TypedDict)

     在 3.10 版被加入.

 -- 類別: typing.ForwardRef

     Class used for internal typing representation of string forward
     references.

     For example, ‘List["SomeClass"]’ is implicitly transformed into
     ‘List[ForwardRef("SomeClass")]’.  ‘ForwardRef’ should not be
     instantiated by a user, but may be used by introspection tools.

          備註: PEP 585(2) generic types such as ‘list["SomeClass"]’
          will not be implicitly transformed into
          ‘list[ForwardRef("SomeClass")]’ and thus will not
          automatically resolve to ‘list[SomeClass]’.

     在 3.7.4 版被加入.

 -- 資料: typing.NoDefault

     A sentinel object used to indicate that a type parameter has no
     default value.  For example:

          >>> T = TypeVar("T")
          >>> T.__default__ is typing.NoDefault
          True
          >>> S = TypeVar("S", default=None)
          >>> S.__default__ is None
          True

     在 3.13 版被加入.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0593/

   (2) https://peps.python.org/pep-0585/


File: python.info,  Node: 常數<9>,  Next: 棄用的別名,  Prev: Introspection helpers,  Up: 模組內容<7>

5.26.1.22 常數
..............

 -- 資料: typing.TYPE_CHECKING

     A special constant that is assumed to be ‘True’ by 3rd party static
     type checkers.  It is ‘False’ at runtime.

     Usage:

          if TYPE_CHECKING:
              import expensive_mod

          def fun(arg: 'expensive_mod.SomeType') -> None:
              local_var: expensive_mod.AnotherType = other_fun()

     The first type annotation must be enclosed in quotes, making it a
     "forward reference", to hide the ‘expensive_mod’ reference from the
     interpreter runtime.  Type annotations for local variables are not
     evaluated, so the second annotation does not need to be enclosed in
     quotes.

          備註: If ‘from __future__ import annotations’ is used,
          annotations are not evaluated at function definition time.
          Instead, they are stored as strings in ‘__annotations__’.
          This makes it unnecessary to use quotes around the annotation
          (see PEP 563(1)).

     在 3.5.2 版被加入.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0563/


File: python.info,  Node: 棄用的別名,  Prev: 常數<9>,  Up: 模組內容<7>

5.26.1.23 棄用的別名
....................

This module defines several deprecated aliases to pre-existing standard
library classes.  These were originally included in the typing module in
order to support parameterizing these generic classes using ‘[]’.
However, the aliases became redundant in Python 3.9 when the
corresponding pre-existing classes were enhanced to support ‘[]’ (see
PEP 585(1)).

The redundant types are deprecated as of Python 3.9.  However, while the
aliases may be removed at some point, removal of these aliases is not
currently planned.  As such, no deprecation warnings are currently
issued by the interpreter for these aliases.

If at some point it is decided to remove these deprecated aliases, a
deprecation warning will be issued by the interpreter for at least two
releases prior to removal.  The aliases are guaranteed to remain in the
typing module without deprecation warnings until at least Python 3.14.

Type checkers are encouraged to flag uses of the deprecated types if the
program they are checking targets a minimum Python version of 3.9 or
newer.

* Menu:

* 內建型別的別名::
* collections 中型別的別名::
* Aliases to other concrete types::
* collections.abc 中容器 ABC 的別名: collections abc 中容器 ABC 的別名.
* Aliases to asynchronous ABCs in collections.abc: Aliases to asynchronous ABCs in collections abc.
* Aliases to other ABCs in collections.abc: Aliases to other ABCs in collections abc.
* contextlib ABC 的別名::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0585/


File: python.info,  Node: 內建型別的別名,  Next: collections 中型別的別名,  Up: 棄用的別名

5.26.1.24 內建型別的別名
........................

 -- 類別: typing.Dict (dict, MutableMapping[KT, VT])

     棄用 *note dict: 23b. 的別名。

     Note that to annotate arguments, it is preferred to use an abstract
     collection type such as *note Mapping: 86f. rather than to use
     *note dict: 23b. or ‘typing.Dict’.

     在 3.9 版之後被棄用: *note builtins.dict: 23b. now supports
     subscripting (‘[]’).  See PEP 585(1) and *note 泛型別名型別: 656.

 -- 類別: typing.List (list, MutableSequence[T])

     棄用 *note list: 5b6. 的別名。

     Note that to annotate arguments, it is preferred to use an abstract
     collection type such as *note Sequence: 115c. or *note Iterable:
     212a. rather than to use *note list: 5b6. or ‘typing.List’.

     在 3.9 版之後被棄用: *note builtins.list: 5b6. now supports
     subscripting (‘[]’).  See PEP 585(2) and *note 泛型別名型別: 656.

 -- 類別: typing.Set (set, MutableSet[T])

     棄用 *note builtins.set: 57d. 的別名。

     Note that to annotate arguments, it is preferred to use an abstract
     collection type such as *note collections.abc.Set: 2122. rather
     than to use *note set: 57d. or *note typing.Set: 3dd4.

     在 3.9 版之後被棄用: *note builtins.set: 57d. now supports
     subscripting (‘[]’).  See PEP 585(3) and *note 泛型別名型別: 656.

 -- 類別: typing.FrozenSet (frozenset, AbstractSet[T_co])

     棄用 *note builtins.frozenset: 57e. 的別名。

     在 3.9 版之後被棄用: *note builtins.frozenset: 57e. now supports
     subscripting (‘[]’).  See PEP 585(4) and *note 泛型別名型別: 656.

 -- 資料: typing.Tuple

     棄用 *note tuple: 322. 的別名。

     *note tuple: 322. and ‘Tuple’ are special-cased in the type system;
     see *note 註釋元組 (tuple): 3d91. for more details.

     在 3.9 版之後被棄用: *note builtins.tuple: 322. now supports
     subscripting (‘[]’).  See PEP 585(5) and *note 泛型別名型別: 656.

 -- 類別: typing.Type (Generic[CT_co])

     棄用 *note type: cef. 的別名。

     See *note 類別物件的型別: 3d94. for details on using *note type:
     cef. or ‘typing.Type’ in type annotations.

     在 3.5.2 版被加入.

     在 3.9 版之後被棄用: *note builtins.type: cef. now supports
     subscripting (‘[]’).  See PEP 585(6) and *note 泛型別名型別: 656.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0585/

   (2) https://peps.python.org/pep-0585/

   (3) https://peps.python.org/pep-0585/

   (4) https://peps.python.org/pep-0585/

   (5) https://peps.python.org/pep-0585/

   (6) https://peps.python.org/pep-0585/


File: python.info,  Node: collections 中型別的別名,  Next: Aliases to other concrete types,  Prev: 內建型別的別名,  Up: 棄用的別名

5.26.1.25 ‘collections’ 中型別的別名
....................................

 -- 類別: typing.DefaultDict (collections.defaultdict,
          MutableMapping[KT, VT])

     棄用 *note collections.defaultdict: 1155. 的別名。

     在 3.5.2 版被加入.

     在 3.9 版之後被棄用: *note collections.defaultdict: 1155. now
     supports subscripting (‘[]’).  See PEP 585(1) and *note
     泛型別名型別: 656.

 -- 類別: typing.OrderedDict (collections.OrderedDict,
          MutableMapping[KT, VT])

     棄用 *note collections.OrderedDict: 57f. 的別名。

     在 3.7.2 版被加入.

     在 3.9 版之後被棄用: *note collections.OrderedDict: 57f. now
     supports subscripting (‘[]’).  See PEP 585(2) and *note
     泛型別名型別: 656.

 -- 類別: typing.ChainMap (collections.ChainMap, MutableMapping[KT, VT])

     棄用 *note collections.ChainMap: bc3. 的別名。

     在 3.6.1 版被加入.

     在 3.9 版之後被棄用: *note collections.ChainMap: bc3. now supports
     subscripting (‘[]’).  See PEP 585(3) and *note 泛型別名型別: 656.

 -- 類別: typing.Counter (collections.Counter, Dict[T, int])

     棄用 *note collections.Counter: 1033. 的別名。

     在 3.6.1 版被加入.

     在 3.9 版之後被棄用: *note collections.Counter: 1033. now supports
     subscripting (‘[]’).  See PEP 585(4) and *note 泛型別名型別: 656.

 -- 類別: typing.Deque (deque, MutableSequence[T])

     棄用 *note collections.deque: 580. 的別名。

     在 3.6.1 版被加入.

     在 3.9 版之後被棄用: *note collections.deque: 580. now supports
     subscripting (‘[]’).  See PEP 585(5) and *note 泛型別名型別: 656.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0585/

   (2) https://peps.python.org/pep-0585/

   (3) https://peps.python.org/pep-0585/

   (4) https://peps.python.org/pep-0585/

   (5) https://peps.python.org/pep-0585/


File: python.info,  Node: Aliases to other concrete types,  Next: collections abc 中容器 ABC 的別名,  Prev: collections 中型別的別名,  Up: 棄用的別名

5.26.1.26 Aliases to other concrete types
.........................................

 -- 類別: typing.Pattern
 -- 類別: typing.Match

     Deprecated aliases corresponding to the return types from *note
     re.compile(): b7a. and *note re.match(): 11c5.

     These types (and the corresponding functions) are generic over
     *note AnyStr: 293.  ‘Pattern’ can be specialised as ‘Pattern[str]’
     or ‘Pattern[bytes]’; ‘Match’ can be specialised as ‘Match[str]’ or
     ‘Match[bytes]’.

     在 3.9 版之後被棄用: Classes ‘Pattern’ and ‘Match’ from *note re:
     a7. now support ‘[]’.  See PEP 585(1) and *note 泛型別名型別: 656.

 -- 類別: typing.Text

     棄用 *note str: 3f2. 的別名。

     ‘Text’ is provided to supply a forward compatible path for Python 2
     code: in Python 2, ‘Text’ is an alias for ‘unicode’.

     Use ‘Text’ to indicate that a value must contain a unicode string
     in a manner that is compatible with both Python 2 and Python 3:

          def add_unicode_checkmark(text: Text) -> Text:
              return text + u' \u2713'

     在 3.5.2 版被加入.

     在 3.11 版之後被棄用: Python 2 is no longer supported, and most
     type checkers also no longer support type checking Python 2 code.
     Removal of the alias is not currently planned, but users are
     encouraged to use *note str: 3f2. instead of ‘Text’.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0585/


File: python.info,  Node: collections abc 中容器 ABC 的別名,  Next: Aliases to asynchronous ABCs in collections abc,  Prev: Aliases to other concrete types,  Up: 棄用的別名

5.26.1.27 ‘collections.abc’ 中容器 ABC 的別名
.............................................

 -- 類別: typing.AbstractSet (Collection[T_co])

     棄用 *note collections.abc.Set: 2122. 的別名。

     在 3.9 版之後被棄用: *note collections.abc.Set: 2122. now supports
     subscripting (‘[]’).  See PEP 585(1) and *note 泛型別名型別: 656.

 -- 類別: typing.ByteString (Sequence[int])

     This type represents the types *note bytes: 1a5, *note bytearray:
     4e3, and *note memoryview: 40f. of byte sequences.

     Deprecated since version 3.9, will be removed in version 3.14:
     Prefer *note collections.abc.Buffer: 2a5, or a union like ‘bytes |
     bytearray | memoryview’.

 -- 類別: typing.Collection (Sized, Iterable[T_co], Container[T_co])

     棄用 *note collections.abc.Collection: c2f. 的別名。

     在 3.6 版被加入.

     在 3.9 版之後被棄用: *note collections.abc.Collection: c2f. now
     supports subscripting (‘[]’).  See PEP 585(2) and *note
     泛型別名型別: 656.

 -- 類別: typing.Container (Generic[T_co])

     棄用 *note collections.abc.Container: 212c. 的別名。

     在 3.9 版之後被棄用: *note collections.abc.Container: 212c. now
     supports subscripting (‘[]’).  See PEP 585(3) and *note
     泛型別名型別: 656.

 -- 類別: typing.ItemsView (MappingView, AbstractSet[tuple[KT_co,
          VT_co]])

     棄用 *note collections.abc.ItemsView: 2130. 的別名。

     在 3.9 版之後被棄用: *note collections.abc.ItemsView: 2130. now
     supports subscripting (‘[]’).  See PEP 585(4) and *note
     泛型別名型別: 656.

 -- 類別: typing.KeysView (MappingView, AbstractSet[KT_co])

     棄用 *note collections.abc.KeysView: 212f. 的別名。

     在 3.9 版之後被棄用: *note collections.abc.KeysView: 212f. now
     supports subscripting (‘[]’).  See PEP 585(5) and *note
     泛型別名型別: 656.

 -- 類別: typing.Mapping (Collection[KT], Generic[KT, VT_co])

     棄用 *note collections.abc.Mapping: 86f. 的別名。

     在 3.9 版之後被棄用: *note collections.abc.Mapping: 86f. now
     supports subscripting (‘[]’).  See PEP 585(6) and *note
     泛型別名型別: 656.

 -- 類別: typing.MappingView (Sized)

     棄用 *note collections.abc.MappingView: 212e. 的別名。

     在 3.9 版之後被棄用: *note collections.abc.MappingView: 212e. now
     supports subscripting (‘[]’).  See PEP 585(7) and *note
     泛型別名型別: 656.

 -- 類別: typing.MutableMapping (Mapping[KT, VT])

     棄用 *note collections.abc.MutableMapping: 1048. 的別名。

     在 3.9 版之後被棄用: *note collections.abc.MutableMapping: 1048.
     now supports subscripting (‘[]’).  See PEP 585(8) and *note
     泛型別名型別: 656.

 -- 類別: typing.MutableSequence (Sequence[T])

     棄用 *note collections.abc.MutableSequence: 187. 的別名。

     在 3.9 版之後被棄用: *note collections.abc.MutableSequence: 187.
     now supports subscripting (‘[]’).  See PEP 585(9) and *note
     泛型別名型別: 656.

 -- 類別: typing.MutableSet (AbstractSet[T])

     棄用 *note collections.abc.MutableSet: 212d. 的別名。

     在 3.9 版之後被棄用: *note collections.abc.MutableSet: 212d. now
     supports subscripting (‘[]’).  See PEP 585(10) and *note
     泛型別名型別: 656.

 -- 類別: typing.Sequence (Reversible[T_co], Collection[T_co])

     棄用 *note collections.abc.Sequence: 115c. 的別名。

     在 3.9 版之後被棄用: *note collections.abc.Sequence: 115c. now
     supports subscripting (‘[]’).  See PEP 585(11) and *note
     泛型別名型別: 656.

 -- 類別: typing.ValuesView (MappingView, Collection[_VT_co])

     棄用 *note collections.abc.ValuesView: 2131. 的別名。

     在 3.9 版之後被棄用: *note collections.abc.ValuesView: 2131. now
     supports subscripting (‘[]’).  See PEP 585(12) and *note
     泛型別名型別: 656.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0585/

   (2) https://peps.python.org/pep-0585/

   (3) https://peps.python.org/pep-0585/

   (4) https://peps.python.org/pep-0585/

   (5) https://peps.python.org/pep-0585/

   (6) https://peps.python.org/pep-0585/

   (7) https://peps.python.org/pep-0585/

   (8) https://peps.python.org/pep-0585/

   (9) https://peps.python.org/pep-0585/

   (10) https://peps.python.org/pep-0585/

   (11) https://peps.python.org/pep-0585/

   (12) https://peps.python.org/pep-0585/


File: python.info,  Node: Aliases to asynchronous ABCs in collections abc,  Next: Aliases to other ABCs in collections abc,  Prev: collections abc 中容器 ABC 的別名,  Up: 棄用的別名

5.26.1.28 Aliases to asynchronous ABCs in ‘collections.abc’
...........................................................

 -- 類別: typing.Coroutine (Awaitable[ReturnType], Generic[YieldType,
          SendType, ReturnType])

     棄用 *note collections.abc.Coroutine: d83. 的別名。

     See *note Annotating generators and coroutines: 2404. for details
     on using *note collections.abc.Coroutine: d83. and
     ‘typing.Coroutine’ in type annotations.

     在 3.5.3 版被加入.

     在 3.9 版之後被棄用: *note collections.abc.Coroutine: d83. now
     supports subscripting (‘[]’).  See PEP 585(1) and *note
     泛型別名型別: 656.

 -- 類別: typing.AsyncGenerator (AsyncIterator[YieldType],
          Generic[YieldType, SendType])

     棄用 *note collections.abc.AsyncGenerator: c31. 的別名。

     See *note Annotating generators and coroutines: 2404. for details
     on using *note collections.abc.AsyncGenerator: c31. and
     ‘typing.AsyncGenerator’ in type annotations.

     在 3.6.1 版被加入.

     在 3.9 版之後被棄用: *note collections.abc.AsyncGenerator: c31. now
     supports subscripting (‘[]’).  See PEP 585(2) and *note
     泛型別名型別: 656.

     在 3.13 版的變更: The ‘SendType’ parameter now has a default.

 -- 類別: typing.AsyncIterable (Generic[T_co])

     棄用 *note collections.abc.AsyncIterable: d85. 的別名。

     在 3.5.2 版被加入.

     在 3.9 版之後被棄用: *note collections.abc.AsyncIterable: d85. now
     supports subscripting (‘[]’).  See PEP 585(3) and *note
     泛型別名型別: 656.

 -- 類別: typing.AsyncIterator (AsyncIterable[T_co])

     棄用 *note collections.abc.AsyncIterator: d84. 的別名。

     在 3.5.2 版被加入.

     在 3.9 版之後被棄用: *note collections.abc.AsyncIterator: d84. now
     supports subscripting (‘[]’).  See PEP 585(4) and *note
     泛型別名型別: 656.

 -- 類別: typing.Awaitable (Generic[T_co])

     棄用 *note collections.abc.Awaitable: d82. 的別名。

     在 3.5.2 版被加入.

     在 3.9 版之後被棄用: *note collections.abc.Awaitable: d82. now
     supports subscripting (‘[]’).  See PEP 585(5) and *note
     泛型別名型別: 656.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0585/

   (2) https://peps.python.org/pep-0585/

   (3) https://peps.python.org/pep-0585/

   (4) https://peps.python.org/pep-0585/

   (5) https://peps.python.org/pep-0585/


File: python.info,  Node: Aliases to other ABCs in collections abc,  Next: contextlib ABC 的別名,  Prev: Aliases to asynchronous ABCs in collections abc,  Up: 棄用的別名

5.26.1.29 Aliases to other ABCs in ‘collections.abc’
....................................................

 -- 類別: typing.Iterable (Generic[T_co])

     棄用 *note collections.abc.Iterable: 212a. 的別名。

     在 3.9 版之後被棄用: *note collections.abc.Iterable: 212a. now
     supports subscripting (‘[]’).  See PEP 585(1) and *note
     泛型別名型別: 656.

 -- 類別: typing.Iterator (Iterable[T_co])

     棄用 *note collections.abc.Iterator: 212b. 的別名。

     在 3.9 版之後被棄用: *note collections.abc.Iterator: 212b. now
     supports subscripting (‘[]’).  See PEP 585(2) and *note
     泛型別名型別: 656.

 -- 資料: typing.Callable

     棄用 *note collections.abc.Callable: 78e. 的別名。

     See *note 註釋 callable 物件: 2403. for details on how to use *note
     collections.abc.Callable: 78e. and ‘typing.Callable’ in type
     annotations.

     在 3.9 版之後被棄用: *note collections.abc.Callable: 78e. now
     supports subscripting (‘[]’).  See PEP 585(3) and *note
     泛型別名型別: 656.

     在 3.10 版的變更: ‘Callable’ 現已支援 *note ParamSpec: 142. 以及
     *note Concatenate: 768.。請參閱 PEP 612(4) 閱讀詳細內容。

 -- 類別: typing.Generator (Iterator[YieldType], Generic[YieldType,
          SendType, ReturnType])

     棄用 *note collections.abc.Generator: d81. 的別名。

     See *note Annotating generators and coroutines: 2404. for details
     on using *note collections.abc.Generator: d81. and
     ‘typing.Generator’ in type annotations.

     在 3.9 版之後被棄用: *note collections.abc.Generator: d81. now
     supports subscripting (‘[]’).  See PEP 585(5) and *note
     泛型別名型別: 656.

     在 3.13 版的變更: Default values for the send and return types were
     added.

 -- 類別: typing.Hashable

     棄用 *note collections.abc.Hashable: 49d. 的別名。

     在 3.12 版之後被棄用: 改為直接使用 *note collections.abc.Hashable:
     49d.。

 -- 類別: typing.Reversible (Iterable[T_co])

     棄用 *note collections.abc.Reversible: c30. 的別名。

     在 3.9 版之後被棄用: *note collections.abc.Reversible: c30. now
     supports subscripting (‘[]’).  See PEP 585(6) and *note
     泛型別名型別: 656.

 -- 類別: typing.Sized

     棄用 *note collections.abc.Sized: 49e. 的別名。

     在 3.12 版之後被棄用: 改為直接使用 *note collections.abc.Sized:
     49e.。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0585/

   (2) https://peps.python.org/pep-0585/

   (3) https://peps.python.org/pep-0585/

   (4) https://peps.python.org/pep-0612/

   (5) https://peps.python.org/pep-0585/

   (6) https://peps.python.org/pep-0585/


File: python.info,  Node: contextlib ABC 的別名,  Prev: Aliases to other ABCs in collections abc,  Up: 棄用的別名

5.26.1.30 ‘contextlib’ ABC 的別名
.................................

 -- 類別: typing.ContextManager (Generic[T_co, ExitT_co])

     Deprecated alias to *note contextlib.AbstractContextManager: c34.

     The first type parameter, ‘T_co’, represents the type returned by
     the *note __enter__(): 56c. method.  The optional second type
     parameter, ‘ExitT_co’, which defaults to ‘bool | None’, represents
     the type returned by the *note __exit__(): 1293. method.

     在 3.5.4 版被加入.

     在 3.9 版之後被棄用: *note contextlib.AbstractContextManager: c34.
     now supports subscripting (‘[]’).  See PEP 585(1) and *note
     泛型別名型別: 656.

     在 3.13 版的變更: Added the optional second type parameter,
     ‘ExitT_co’.

 -- 類別: typing.AsyncContextManager (Generic[T_co, AExitT_co])

     Deprecated alias to *note contextlib.AbstractAsyncContextManager:
     acf.

     The first type parameter, ‘T_co’, represents the type returned by
     the *note __aenter__(): 1ea6. method.  The optional second type
     parameter, ‘AExitT_co’, which defaults to ‘bool | None’, represents
     the type returned by the *note __aexit__(): 151e. method.

     在 3.6.2 版被加入.

     在 3.9 版之後被棄用: *note contextlib.AbstractAsyncContextManager:
     acf. now supports subscripting (‘[]’).  See PEP 585(2) and *note
     泛型別名型別: 656.

     在 3.13 版的變更: Added the optional second type parameter,
     ‘AExitT_co’.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0585/

   (2) https://peps.python.org/pep-0585/


File: python.info,  Node: Deprecation Timeline of Major Features,  Prev: 模組內容<7>,  Up: typing --- 支援型別提示

5.26.1.31 Deprecation Timeline of Major Features
................................................

Certain features in ‘typing’ are deprecated and may be removed in a
future version of Python.  The following table summarizes major
deprecations for your convenience.  This is subject to change, and not
all deprecations are listed.

Feature                       棄用於                        Projected removal             PEP/issue
                                                                                          
------------------------------------------------------------------------------------------------------------------------
                                                                                          
‘typing’ versions of          3.9                           Undecided (see                PEP 585(1)
standard collections                                        *note 棄用的別名: 3dce. for   
                                                            more information)
                                                            
                                                                                          
*note typing.ByteString: 2b8. 3.9                           3.14                          gh-91896(2)
                                                                                          
                                                                                          
*note typing.Text: 2dd.       3.11                          Undecided                     gh-92332(3)
                                                                                          
                                                                                          
*note typing.Hashable: 49b.   3.12                          Undecided                     gh-94309(4)
和 *note typing.Sized: 49c.                                                               

*note typing.TypeAlias: 76d.  3.12                          Undecided                     PEP 695(5)
                                                                                          
                                                                                          
*note @typing.no_type_check_decorator: 292.3.13             3.15                          gh-106309(6)
                                                                                          
                                                                                          
*note typing.AnyStr: 293.     3.13                          3.18                          gh-105578(7)
                                                                                          

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0585/

   (2) https://github.com/python/cpython/issues/91896

   (3) https://github.com/python/cpython/issues/92332

   (4) https://github.com/python/cpython/issues/94309

   (5) https://peps.python.org/pep-0695/

   (6) https://github.com/python/cpython/issues/106309

   (7) https://github.com/python/cpython/issues/105578


File: python.info,  Node: pydoc --- 文件產生器與線上幫助系統,  Next: Python 開發模式,  Prev: typing --- 支援型別提示,  Up: 開發工具

5.26.2 ‘pydoc’ -- 文件產生器與線上幫助系統
------------------------------------------

'原始碼：'Lib/pydoc.py(1)

__________________________________________________________________

The ‘pydoc’ module automatically generates documentation from Python
modules.  The documentation can be presented as pages of text on the
console, served to a web browser, or saved to HTML files.

For modules, classes, functions and methods, the displayed documentation
is derived from the docstring (i.e.  the ‘__doc__’ attribute) of the
object, and recursively of its documentable members.  If there is no
docstring, ‘pydoc’ tries to obtain a description from the block of
comment lines just above the definition of the class, function or method
in the source file, or at the top of the module (see *note
inspect.getcomments(): 3dfe.).

The built-in function *note help(): 87c. invokes the online help system
in the interactive interpreter, which uses ‘pydoc’ to generate its
documentation as text on the console.  The same text documentation can
also be viewed from outside the Python interpreter by running ‘pydoc’ as
a script at the operating system's command prompt.  For example, running

     python -m pydoc sys

at a shell prompt will display documentation on the *note sys: c3.
module, in a style similar to the manual pages shown by the Unix ‘man’
command.  The argument to ‘pydoc’ can be the name of a function, module,
or package, or a dotted reference to a class, method, or function within
a module or module in a package.  If the argument to ‘pydoc’ looks like
a path (that is, it contains the path separator for your operating
system, such as a slash in Unix), and refers to an existing Python
source file, then documentation is produced for that file.

     備註: In order to find objects and their documentation, ‘pydoc’
     imports the module(s) to be documented.  Therefore, any code on
     module level will be executed on that occasion.  Use an ‘if
     __name__ == '__main__':’ guard to only execute code when a file is
     invoked as a script and not just imported.

When printing output to the console, ‘pydoc’ attempts to paginate the
output for easier reading.  If the ‘PAGER’ environment variable is set,
‘pydoc’ will use its value as a pagination program.

Specifying a ‘-w’ flag before the argument will cause HTML documentation
to be written out to a file in the current directory, instead of
displaying text on the console.

Specifying a ‘-k’ flag before the argument will search the synopsis
lines of all available modules for the keyword given as the argument,
again in a manner similar to the Unix ‘man’ command.  The synopsis line
of a module is the first line of its documentation string.

You can also use ‘pydoc’ to start an HTTP server on the local machine
that will serve documentation to visiting web browsers.  ‘python -m
pydoc -p 1234’ will start a HTTP server on port 1234, allowing you to
browse the documentation at ‘http://localhost:1234/’ in your preferred
web browser.  Specifying ‘0’ as the port number will select an arbitrary
unused port.

‘python -m pydoc -n <hostname>’ will start the server listening at the
given hostname.  By default the hostname is 'localhost' but if you want
the server to be reached from other machines, you may want to change the
host name that the server responds to.  During development this is
especially useful if you want to run pydoc from within a container.

‘python -m pydoc -b’ will start the server and additionally open a web
browser to a module index page.  Each served page has a navigation bar
at the top where you can 'Get' help on an individual item, 'Search' all
modules with a keyword in their synopsis line, and go to the 'Module
index', 'Topics' and 'Keywords' pages.

When ‘pydoc’ generates documentation, it uses the current environment
and path to locate modules.  Thus, invoking ‘pydoc spam’ documents
precisely the version of the module you would get if you started the
Python interpreter and typed ‘import spam’.

Module docs for core modules are assumed to reside in
‘https://docs.python.org/X.Y/library/’ where ‘X’ and ‘Y’ are the major
and minor version numbers of the Python interpreter.  This can be
overridden by setting the ‘PYTHONDOCS’ environment variable to a
different URL or to a local directory containing the Library Reference
Manual pages.

在 3.2 版的變更: 新增 ‘-b’ 選項。

在 3.3 版的變更: The ‘-g’ command line option was removed.

在 3.4 版的變更: ‘pydoc’ now uses *note inspect.signature(): 6dc. rather
than *note inspect.getfullargspec(): 6dd. to extract signature
information from callables.

在 3.7 版的變更: 新增 ‘-n’ 選項。

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/pydoc.py


File: python.info,  Node: Python 開發模式,  Next: doctest --- 測試互動式 Python 範例,  Prev: pydoc --- 文件產生器與線上幫助系統,  Up: 開發工具

5.26.3 Python 開發模式
----------------------

在 3.7 版被加入.

Python 開發模式引入了額外的 runtime 檢查，預設啟用這些檢查的成本太高。如
果程式碼正確，它不應比預設值更詳細；僅當偵測到問題時才會發出新警告。

可以使用 *note -X dev: 15a. 命令列選項或將 *note PYTHONDEVMODE: a90. 環
境變數設為 1 來啟用它。

另請參閱 *note Python 除錯建置: 1de.。

* Menu:

* Python 開發模式的影響::
* ResourceWarning 範例::
* 檔案描述器的錯誤範例::


File: python.info,  Node: Python 開發模式的影響,  Next: ResourceWarning 範例,  Up: Python 開發模式

5.26.3.1 Python 開發模式的影響
..............................

啟用 Python 開發模式類似以下指令，但具有如下所述的附加效果：

     PYTHONMALLOC=debug PYTHONASYNCIODEBUG=1 python -W default -X faulthandler

Python 開發模式的效果：

   * 新增 ‘default’ *note 警告過濾器: 1c3b.。以下警告會被顯示：

        * *note DeprecationWarning: 18b.

        * *note ImportWarning: 4a2.

        * *note PendingDeprecationWarning: 86d.

        * *note ResourceWarning: 229.

     一般來說，上述警告會被預設的*note 警告過濾器: 1c3b.給過濾掉。

     它的行為就像使用 *note -W default: 86c. 命令列選項一樣。

     使用 *note -W error: 86c. 命令列選項或將 *note PYTHONWARNINGS: b51.
     環境變數設為 ‘error’ 會將警告視為錯誤。

   * 在記憶體分配器上安裝除錯 hook（掛鉤）以檢查：

        * 緩衝區下溢 (underflow)

        * 緩衝區溢位 (overflow)

        * 記憶體分配器 API 違規

        * GIL 的不安全使用

     請參閱 *note PyMem_SetupDebugHooks(): c11. C 函式。

     它的行為就好像是將 *note PYTHONMALLOC: c0b. 環境變數設定為 ‘debug’
     一樣。

     若要啟用 Python 開發模式而不在記憶體分配器上安裝偵錯 hook，請將
     *note PYTHONMALLOC: c0b. 環境變數設為 ‘default’。

   * 在 Python 啟動時呼叫 *note faulthandler.enable(): c45. 來為 *note
     SIGSEGV: 1c4b.、*note SIGFPE: 1c4c.、*note SIGABRT: 1c4d.、*note
     SIGBUS: 1c4e. 和 *note SIGILL: 1c4f. 訊號安裝處理函式以在當機時傾印
     (dump) Python 回溯 (traceback)。

     它的行為就像使用 *note -X faulthandler: 15a. 命令列選項或將 *note
     PYTHONFAULTHANDLER: 1021. 環境變數設定為 ‘1’。

   * 啟用 *note asyncio 除錯模式: 1c51.。例如 *note asyncio: 8. 會檢查未
     被等待的 (not awaited) 協程並記錄 (log) 它們。

     它的行為就像將 *note PYTHONASYNCIODEBUG: 1c50. 環境變數設定為 1 一
     樣。

   * 檢查字串編碼和解碼操作的 'encoding' 和 'errors' 引數。例如：*note
     open(): 4c0.、*note str.encode(): 87a. 和 *note bytes.decode():
     87b.。

     預設情況下，為了獲得最佳效能，僅在第一個編碼/解碼錯誤時檢查
     'errors' 引數，並且有時會因為是空字串而忽略 'encoding' 引數。

   * *note io.IOBase: 1da. 解構函式會記錄 ‘close()’ 例外。

   * 將 *note sys.flags: 632. 的 *note dev_mode: 19a7. 屬性設為 ‘True’。

Python 開發模式預設不會啟用 *note tracemalloc: e8. 模組，因為（效能和記
憶體的）開銷太大。啟用 *note tracemalloc: e8. 模組可提供有關某些錯誤來源
的附加資訊。例如 *note ResourceWarning: 229. 記錄了分配資源之處的回溯、
緩衝區溢位錯誤記錄了分配記憶體區塊的回溯。

Python 開發模式不會防止 *note -O: d5b. 命令列選項刪除 *note assert: 90c.
陳述式，也不會防止將 *note __debug__: 77e. 設定為 ‘False’。

Python 開發模式只能在 Python 啟動時啟用。它的值可以從 *note
sys.flags.dev_mode: 632. 讀取。

在 3.8 版的變更: *note io.IOBase: 1da. 解構函式現在會記錄 ‘close()’ 例外
。

在 3.9 版的變更: 現在會為字串編碼和解碼操作檢查 'encoding' 和 'errors' 引
數。


File: python.info,  Node: ResourceWarning 範例,  Next: 檔案描述器的錯誤範例,  Prev: Python 開發模式的影響,  Up: Python 開發模式

5.26.3.2 ResourceWarning 範例
.............................

計算命令列中指定的文字檔案列數的腳本範例：

     import sys

     def main():
         fp = open(sys.argv[1])
         nlines = len(fp.readlines())
         print(nlines)
         # The file is closed implicitly

     if __name__ == "__main__":
         main()

該腳本不會明確關閉檔案。預設情況下，Python 不會發出任何警告。使用
README.txt 的範例，該檔案有 269 列：

     $ python script.py README.txt
     269

啟用 Python 開發模式會顯示 *note ResourceWarning: 229. 警告：

     $ python -X dev script.py README.txt
     269
     script.py:10: ResourceWarning: unclosed file <_io.TextIOWrapper name='README.rst' mode='r' encoding='UTF-8'>
       main()
     ResourceWarning: Enable tracemalloc to get the object allocation traceback

此外，啟用 *note tracemalloc: e8. 會顯示檔案被開啟的那一列：

     $ python -X dev -X tracemalloc=5 script.py README.rst
     269
     script.py:10: ResourceWarning: unclosed file <_io.TextIOWrapper name='README.rst' mode='r' encoding='UTF-8'>
       main()
     Object allocated at (most recent call last):
       File "script.py", lineno 10
         main()
       File "script.py", lineno 4
         fp = open(sys.argv[1])

修復方法是明確關閉該檔案。以下是使用情境管理器的範例：

     def main():
         # Close the file explicitly when exiting the with block
         with open(sys.argv[1]) as fp:
             nlines = len(fp.readlines())
         print(nlines)

不明確關閉資源可能會使資源開啟的時間比預期的長得多；它可能會在退出
Python 時導致嚴重問題。在 CPython 中很糟糕，但在 PyPy 中更糟。明確關閉資
源使應用程式更具確定性和可靠性。


File: python.info,  Node: 檔案描述器的錯誤範例,  Prev: ResourceWarning 範例,  Up: Python 開發模式

5.26.3.3 檔案描述器的錯誤範例
.............................

顯示自身第一列的腳本：

     import os

     def main():
         fp = open(__file__)
         firstline = fp.readline()
         print(firstline.rstrip())
         os.close(fp.fileno())
         # The file is closed implicitly

     main()

預設情況下，Python 不會發出任何警告：

     $ python script.py
     import os

Python 開發模式在最終化 (finalize) 檔案物件時顯示 *note ResourceWarning:
229. 並記錄 "Bad file descriptor" 錯誤：

     $ python -X dev script.py
     import os
     script.py:10: ResourceWarning: unclosed file <_io.TextIOWrapper name='script.py' mode='r' encoding='UTF-8'>
       main()
     ResourceWarning: Enable tracemalloc to get the object allocation traceback
     Exception ignored in: <_io.TextIOWrapper name='script.py' mode='r' encoding='UTF-8'>
     Traceback (most recent call last):
       File "script.py", line 10, in <module>
         main()
     OSError: [Errno 9] Bad file descriptor

‘os.close(fp.fileno())’ 會關閉檔案描述器。當檔案物件最終化函式
(finalizer) 嘗試再次關閉檔案描述器時，它會失敗並出現 ‘Bad file
descriptor’ 錯誤。檔案描述器只能關閉一次。在最壞的情況下，將它關閉兩次可
能會導致崩潰 (crash)（相關範例請參閱 bpo-18748(1)）。

修復方法是刪除 ‘os.close(fp.fileno())’ 那列，或使用 ‘closefd=False’ 開啟
檔案。

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=18748


File: python.info,  Node: doctest --- 測試互動式 Python 範例,  Next: unittest --- 單元測試框架,  Prev: Python 開發模式,  Up: 開發工具

5.26.4 ‘doctest’ -- 測試互動式 Python 範例
------------------------------------------

'原始碼：'Lib/doctest.py(1)

__________________________________________________________________

The *note doctest: 31. module searches for pieces of text that look like
interactive Python sessions, and then executes those sessions to verify
that they work exactly as shown.  There are several common ways to use
doctest:

   * To check that a module's docstrings are up-to-date by verifying
     that all interactive examples still work as documented.

   * To perform regression testing by verifying that interactive
     examples from a test file or a test object work as expected.

   * To write tutorial documentation for a package, liberally
     illustrated with input-output examples.  Depending on whether the
     examples or the expository text are emphasized, this has the flavor
     of "literate testing" or "executable documentation".

Here's a complete but small example module:

     """
     This is the "example" module.

     The example module supplies one function, factorial().  For example,

     >>> factorial(5)
     120
     """

     def factorial(n):
         """Return the factorial of n, an exact integer >= 0.

         >>> [factorial(n) for n in range(6)]
         [1, 1, 2, 6, 24, 120]
         >>> factorial(30)
         265252859812191058636308480000000
         >>> factorial(-1)
         Traceback (most recent call last):
             ...
         ValueError: n must be >= 0

         Factorials of floats are OK, but the float must be an exact integer:
         >>> factorial(30.1)
         Traceback (most recent call last):
             ...
         ValueError: n must be exact integer
         >>> factorial(30.0)
         265252859812191058636308480000000

         It must also not be ridiculously large:
         >>> factorial(1e100)
         Traceback (most recent call last):
             ...
         OverflowError: n too large
         """

         import math
         if not n >= 0:
             raise ValueError("n must be >= 0")
         if math.floor(n) != n:
             raise ValueError("n must be exact integer")
         if n+1 == n:  # catch a value like 1e300
             raise OverflowError("n too large")
         result = 1
         factor = 2
         while factor <= n:
             result *= factor
             factor += 1
         return result


     if __name__ == "__main__":
         import doctest
         doctest.testmod()

If you run ‘example.py’ directly from the command line, *note doctest:
31. works its magic:

     $ python example.py
     $

There's no output!  That's normal, and it means all the examples worked.
Pass ‘-v’ to the script, and *note doctest: 31. prints a detailed log of
what it's trying, and prints a summary at the end:

     $ python example.py -v
     Trying:
         factorial(5)
     Expecting:
         120
     ok
     Trying:
         [factorial(n) for n in range(6)]
     Expecting:
         [1, 1, 2, 6, 24, 120]
     ok

And so on, eventually ending with:

     Trying:
         factorial(1e100)
     Expecting:
         Traceback (most recent call last):
             ...
         OverflowError: n too large
     ok
     2 items passed all tests:
        1 test in __main__
        6 tests in __main__.factorial
     7 tests in 2 items.
     7 passed.
     Test passed.
     $

That's all you need to know to start making productive use of *note
doctest: 31.!  Jump in.  The following sections provide full details.
Note that there are many examples of doctests in the standard Python
test suite and libraries.  Especially useful examples can be found in
the standard test file ‘Lib/test/test_doctest/test_doctest.py’.

* Menu:

* Simple Usage; Checking Examples in Docstrings: Simple Usage Checking Examples in Docstrings.
* Simple Usage; Checking Examples in a Text File: Simple Usage Checking Examples in a Text File.
* How It Works::
* 基礎 API::
* Unittest API::
* Advanced API::
* Debugging::
* Soapbox::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/doctest.py


File: python.info,  Node: Simple Usage Checking Examples in Docstrings,  Next: Simple Usage Checking Examples in a Text File,  Up: doctest --- 測試互動式 Python 範例

5.26.4.1 Simple Usage: Checking Examples in Docstrings
......................................................

The simplest way to start using doctest (but not necessarily the way
you'll continue to do it) is to end each module ‘M’ with:

     if __name__ == "__main__":
         import doctest
         doctest.testmod()

‘doctest’ then examines docstrings in module ‘M’.

Running the module as a script causes the examples in the docstrings to
get executed and verified:

     python M.py

This won't display anything unless an example fails, in which case the
failing example(s) and the cause(s) of the failure(s) are printed to
stdout, and the final line of output is ‘***Test Failed*** N failures.’,
where 'N' is the number of examples that failed.

Run it with the ‘-v’ switch instead:

     python M.py -v

and a detailed report of all examples tried is printed to standard
output, along with assorted summaries at the end.

You can force verbose mode by passing ‘verbose=True’ to *note testmod():
13d8, or prohibit it by passing ‘verbose=False’.  In either of those
cases, ‘sys.argv’ is not examined by *note testmod(): 13d8. (so passing
‘-v’ or not has no effect).

There is also a command line shortcut for running *note testmod(): 13d8.
You can instruct the Python interpreter to run the doctest module
directly from the standard library and pass the module name(s) on the
command line:

     python -m doctest -v example.py

This will import ‘example.py’ as a standalone module and run *note
testmod(): 13d8. on it.  Note that this may not work correctly if the
file is part of a package and imports other submodules from that
package.

For more information on *note testmod(): 13d8, see section *note 基礎
API: 3e08.


File: python.info,  Node: Simple Usage Checking Examples in a Text File,  Next: How It Works,  Prev: Simple Usage Checking Examples in Docstrings,  Up: doctest --- 測試互動式 Python 範例

5.26.4.2 Simple Usage: Checking Examples in a Text File
.......................................................

Another simple application of doctest is testing interactive examples in
a text file.  This can be done with the *note testfile(): 3e0b.
function:

     import doctest
     doctest.testfile("example.txt")

That short script executes and verifies any interactive Python examples
contained in the file ‘example.txt’.  The file content is treated as if
it were a single giant docstring; the file doesn't need to contain a
Python program!  For example, perhaps ‘example.txt’ contains this:

     The ``example`` module
     ======================

     Using ``factorial``
     -------------------

     This is an example text file in reStructuredText format.  First import
     ``factorial`` from the ``example`` module:

         >>> from example import factorial

     Now use it:

         >>> factorial(6)
         120

Running ‘doctest.testfile("example.txt")’ then finds the error in this
documentation:

     File "./example.txt", line 14, in example.txt
     Failed example:
         factorial(6)
     Expected:
         120
     Got:
         720

As with *note testmod(): 13d8, *note testfile(): 3e0b. won't display
anything unless an example fails.  If an example does fail, then the
failing example(s) and the cause(s) of the failure(s) are printed to
stdout, using the same format as *note testmod(): 13d8.

By default, *note testfile(): 3e0b. looks for files in the calling
module's directory.  See section *note 基礎 API: 3e08. for a description
of the optional arguments that can be used to tell it to look for files
in other locations.

Like *note testmod(): 13d8, *note testfile(): 3e0b.'s verbosity can be
set with the ‘-v’ command-line switch or with the optional keyword
argument 'verbose'.

There is also a command line shortcut for running *note testfile():
3e0b.  You can instruct the Python interpreter to run the doctest module
directly from the standard library and pass the file name(s) on the
command line:

     python -m doctest -v example.txt

Because the file name does not end with ‘.py’, *note doctest: 31. infers
that it must be run with *note testfile(): 3e0b, not *note testmod():
13d8.

For more information on *note testfile(): 3e0b, see section *note 基礎
API: 3e08.


File: python.info,  Node: How It Works,  Next: 基礎 API,  Prev: Simple Usage Checking Examples in a Text File,  Up: doctest --- 測試互動式 Python 範例

5.26.4.3 How It Works
.....................

This section examines in detail how doctest works: which docstrings it
looks at, how it finds interactive examples, what execution context it
uses, how it handles exceptions, and how option flags can be used to
control its behavior.  This is the information that you need to know to
write doctest examples; for information about actually running doctest
on these examples, see the following sections.

* Menu:

* Which Docstrings Are Examined?::
* How are Docstring Examples Recognized?::
* What's the Execution Context?::
* What About Exceptions?::
* 可選旗標::
* Directives::
* 警告: 警告<2>.


File: python.info,  Node: Which Docstrings Are Examined?,  Next: How are Docstring Examples Recognized?,  Up: How It Works

5.26.4.4 Which Docstrings Are Examined?
.......................................

The module docstring, and all function, class and method docstrings are
searched.  Objects imported into the module are not searched.

In addition, there are cases when you want tests to be part of a module
but not part of the help text, which requires that the tests not be
included in the docstring.  Doctest looks for a module-level variable
called ‘__test__’ and uses it to locate other tests.  If ‘M.__test__’
exists, it must be a dict, and each entry maps a (string) name to a
function object, class object, or string.  Function and class object
docstrings found from ‘M.__test__’ are searched, and strings are treated
as if they were docstrings.  In output, a key ‘K’ in ‘M.__test__’
appears with name ‘M.__test__.K’.

For example, place this block of code at the top of ‘example.py’:

     __test__ = {
         'numbers': """
     >>> factorial(6)
     720

     >>> [factorial(n) for n in range(6)]
     [1, 1, 2, 6, 24, 120]
     """
     }

The value of ‘example.__test__["numbers"]’ will be treated as a
docstring and all the tests inside it will be run.  It is important to
note that the value can be mapped to a function, class object, or
module; if so, ‘doctest’ searches them recursively for docstrings, which
are then scanned for tests.

Any classes found are recursively searched similarly, to test docstrings
in their contained methods and nested classes.


File: python.info,  Node: How are Docstring Examples Recognized?,  Next: What's the Execution Context?,  Prev: Which Docstrings Are Examined?,  Up: How It Works

5.26.4.5 How are Docstring Examples Recognized?
...............................................

In most cases a copy-and-paste of an interactive console session works
fine, but doctest isn't trying to do an exact emulation of any specific
Python shell.

     >>> # 註解會被忽略
     >>> x = 12
     >>> x
     12
     >>> if x == 13:
     ...     print("yes")
     ... else:
     ...     print("no")
     ...     print("NO")
     ...     print("NO!!!")
     ...
     no
     NO
     NO!!!
     >>>

Any expected output must immediately follow the final ‘'>>> '’ or ‘'...
'’ line containing the code, and the expected output (if any) extends to
the next ‘'>>> '’ or all-whitespace line.

The fine print:

   * Expected output cannot contain an all-whitespace line, since such a
     line is taken to signal the end of expected output.  If expected
     output does contain a blank line, put ‘<BLANKLINE>’ in your doctest
     example each place a blank line is expected.

   * All hard tab characters are expanded to spaces, using 8-column tab
     stops.  Tabs in output generated by the tested code are not
     modified.  Because any hard tabs in the sample output 'are'
     expanded, this means that if the code output includes hard tabs,
     the only way the doctest can pass is if the *note
     NORMALIZE_WHITESPACE: 3e12. option or *note directive: 3e13. is in
     effect.  Alternatively, the test can be rewritten to capture the
     output and compare it to an expected value as part of the test.
     This handling of tabs in the source was arrived at through trial
     and error, and has proven to be the least error prone way of
     handling them.  It is possible to use a different algorithm for
     handling tabs by writing a custom *note DocTestParser: 3e14. class.

   * Output to stdout is captured, but not output to stderr (exception
     tracebacks are captured via a different means).

   * If you continue a line via backslashing in an interactive session,
     or for any other reason use a backslash, you should use a raw
     docstring, which will preserve your backslashes exactly as you type
     them:

          >>> def f(x):
          ...     r'''Backslashes in a raw docstring: m\n'''
          ...
          >>> print(f.__doc__)
          Backslashes in a raw docstring: m\n

     Otherwise, the backslash will be interpreted as part of the string.
     For example, the ‘\n’ above would be interpreted as a newline
     character.  Alternatively, you can double each backslash in the
     doctest version (and not use a raw string):

          >>> def f(x):
          ...     '''Backslashes in a raw docstring: m\\n'''
          ...
          >>> print(f.__doc__)
          Backslashes in a raw docstring: m\n

   * The starting column doesn't matter:

          >>> assert "Easy!"
                >>> import math
                    >>> math.floor(1.9)
                    1

     and as many leading whitespace characters are stripped from the
     expected output as appeared in the initial ‘'>>> '’ line that
     started the example.


File: python.info,  Node: What's the Execution Context?,  Next: What About Exceptions?,  Prev: How are Docstring Examples Recognized?,  Up: How It Works

5.26.4.6 What's the Execution Context?
......................................

By default, each time *note doctest: 31. finds a docstring to test, it
uses a 'shallow copy' of ‘M’'s globals, so that running tests doesn't
change the module's real globals, and so that one test in ‘M’ can't
leave behind crumbs that accidentally allow another test to work.  This
means examples can freely use any names defined at top-level in ‘M’, and
names defined earlier in the docstring being run.  Examples cannot see
names defined in other docstrings.

You can force use of your own dict as the execution context by passing
‘globs=your_dict’ to *note testmod(): 13d8. or *note testfile(): 3e0b.
instead.


File: python.info,  Node: What About Exceptions?,  Next: 可選旗標,  Prev: What's the Execution Context?,  Up: How It Works

5.26.4.7 What About Exceptions?
...............................

No problem, provided that the traceback is the only output produced by
the example: just paste in the traceback.  (1)  Since tracebacks contain
details that are likely to change rapidly (for example, exact file paths
and line numbers), this is one case where doctest works hard to be
flexible in what it accepts.

簡單範例：

     >>> [1, 2, 3].remove(42)
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     ValueError: list.remove(x): x not in list

That doctest succeeds if *note ValueError: 1e7. is raised, with the
‘list.remove(x): x not in list’ detail as shown.

The expected output for an exception must start with a traceback header,
which may be either of the following two lines, indented the same as the
first line of the example:

     Traceback (most recent call last):
     Traceback (innermost last):

The traceback header is followed by an optional traceback stack, whose
contents are ignored by doctest.  The traceback stack is typically
omitted, or copied verbatim from an interactive session.

The traceback stack is followed by the most interesting part: the
line(s) containing the exception type and detail.  This is usually the
last line of a traceback, but can extend across multiple lines if the
exception has a multi-line detail:

     >>> raise ValueError('multi\n    line\ndetail')
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     ValueError: multi
         line
     detail

The last three lines (starting with *note ValueError: 1e7.) are compared
against the exception's type and detail, and the rest are ignored.

Best practice is to omit the traceback stack, unless it adds significant
documentation value to the example.  So the last example is probably
better as:

     >>> raise ValueError('multi\n    line\ndetail')
     Traceback (most recent call last):
         ...
     ValueError: multi
         line
     detail

Note that tracebacks are treated very specially.  In particular, in the
rewritten example, the use of ‘...’ is independent of doctest's *note
ELLIPSIS: 13d9. option.  The ellipsis in that example could be left out,
or could just as well be three (or three hundred) commas or digits, or
an indented transcript of a Monty Python skit.

Some details you should read once, but won't need to remember:

   * Doctest can't guess whether your expected output came from an
     exception traceback or from ordinary printing.  So, e.g., an
     example that expects ‘ValueError: 42 is prime’ will pass whether
     *note ValueError: 1e7. is actually raised or if the example merely
     prints that traceback text.  In practice, ordinary output rarely
     begins with a traceback header line, so this doesn't create real
     problems.

   * Each line of the traceback stack (if present) must be indented
     further than the first line of the example, 'or' start with a
     non-alphanumeric character.  The first line following the traceback
     header indented the same and starting with an alphanumeric is taken
     to be the start of the exception detail.  Of course this does the
     right thing for genuine tracebacks.

   * When the *note IGNORE_EXCEPTION_DETAIL: 129c. doctest option is
     specified, everything following the leftmost colon and any module
     information in the exception name is ignored.

   * The interactive shell omits the traceback header line for some
     *note SyntaxError: 173.s.  But doctest uses the traceback header
     line to distinguish exceptions from non-exceptions.  So in the rare
     case where you need to test a *note SyntaxError: 173. that omits
     the traceback header, you will need to manually add the traceback
     header line to your test example.

   * For some exceptions, Python displays the position of the error
     using ‘^’ markers and tildes:

          >>> 1 + None
            File "<stdin>", line 1
              1 + None
              ~~^~~~~~
          TypeError: unsupported operand type(s) for +: 'int' and 'NoneType'

     Since the lines showing the position of the error come before the
     exception type and detail, they are not checked by doctest.  For
     example, the following test would pass, even though it puts the ‘^’
     marker in the wrong location:

          >>> 1 + None
            File "<stdin>", line 1
              1 + None
              ^~~~~~~~
          TypeError: unsupported operand type(s) for +: 'int' and 'NoneType'

   ---------- Footnotes ----------

   (1) Examples containing both expected output and an exception are not
supported.  Trying to guess where one ends and the other begins is too
error-prone, and that also makes for a confusing test.


File: python.info,  Node: 可選旗標,  Next: Directives,  Prev: What About Exceptions?,  Up: How It Works

5.26.4.8 可選旗標
.................

A number of option flags control various aspects of doctest's behavior.
Symbolic names for the flags are supplied as module constants, which can
be *note bitwise ORed: 1f48. together and passed to various functions.
The names can also be used in *note doctest directives: 3e13, and may be
passed to the doctest command line interface via the ‘-o’ option.

在 3.4 版被加入: The ‘-o’ command line option.

The first group of options define test semantics, controlling aspects of
how doctest decides whether actual output matches an example's expected
output:

 -- 資料: doctest.DONT_ACCEPT_TRUE_FOR_1

     By default, if an expected output block contains just ‘1’, an
     actual output block containing just ‘1’ or just ‘True’ is
     considered to be a match, and similarly for ‘0’ versus ‘False’.
     When *note DONT_ACCEPT_TRUE_FOR_1: 3e1b. is specified, neither
     substitution is allowed.  The default behavior caters to that
     Python changed the return type of many functions from integer to
     boolean; doctests expecting "little integer" output still work in
     these cases.  This option will probably go away, but not for
     several years.

 -- 資料: doctest.DONT_ACCEPT_BLANKLINE

     By default, if an expected output block contains a line containing
     only the string ‘<BLANKLINE>’, then that line will match a blank
     line in the actual output.  Because a genuinely blank line delimits
     the expected output, this is the only way to communicate that a
     blank line is expected.  When *note DONT_ACCEPT_BLANKLINE: 3e1c. is
     specified, this substitution is not allowed.

 -- 資料: doctest.NORMALIZE_WHITESPACE

     When specified, all sequences of whitespace (blanks and newlines)
     are treated as equal.  Any sequence of whitespace within the
     expected output will match any sequence of whitespace within the
     actual output.  By default, whitespace must match exactly.  *note
     NORMALIZE_WHITESPACE: 3e12. is especially useful when a line of
     expected output is very long, and you want to wrap it across
     multiple lines in your source.

 -- 資料: doctest.ELLIPSIS

     When specified, an ellipsis marker (‘...’) in the expected output
     can match any substring in the actual output.  This includes
     substrings that span line boundaries, and empty substrings, so it's
     best to keep usage of this simple.  Complicated uses can lead to
     the same kinds of "oops, it matched too much!"  surprises that ‘.*’
     is prone to in regular expressions.

 -- 資料: doctest.IGNORE_EXCEPTION_DETAIL

     When specified, doctests expecting exceptions pass so long as an
     exception of the expected type is raised, even if the details
     (message and fully qualified exception name) don't match.

     For example, an example expecting ‘ValueError: 42’ will pass if the
     actual exception raised is ‘ValueError: 3*14’, but will fail if,
     say, a *note TypeError: 4dd. is raised instead.  It will also
     ignore any fully qualified name included before the exception
     class, which can vary between implementations and versions of
     Python and the code/libraries in use.  Hence, all three of these
     variations will work with the flag specified:

          >>> raise Exception('message')
          Traceback (most recent call last):
          Exception: message

          >>> raise Exception('message')
          Traceback (most recent call last):
          builtins.Exception: message

          >>> raise Exception('message')
          Traceback (most recent call last):
          __main__.Exception: message

     Note that *note ELLIPSIS: 13d9. can also be used to ignore the
     details of the exception message, but such a test may still fail
     based on whether the module name is present or matches exactly.

     在 3.2 版的變更: *note IGNORE_EXCEPTION_DETAIL: 129c. now also
     ignores any information relating to the module containing the
     exception under test.

 -- 資料: doctest.SKIP

     When specified, do not run the example at all.  This can be useful
     in contexts where doctest examples serve as both documentation and
     test cases, and an example should be included for documentation
     purposes, but should not be checked.  E.g., the example's output
     might be random; or the example might depend on resources which
     would be unavailable to the test driver.

     The SKIP flag can also be used for temporarily "commenting out"
     examples.

 -- 資料: doctest.COMPARISON_FLAGS

     A bitmask or'ing together all the comparison flags above.

The second group of options controls how test failures are reported:

 -- 資料: doctest.REPORT_UDIFF

     When specified, failures that involve multi-line expected and
     actual outputs are displayed using a unified diff.

 -- 資料: doctest.REPORT_CDIFF

     When specified, failures that involve multi-line expected and
     actual outputs will be displayed using a context diff.

 -- 資料: doctest.REPORT_NDIFF

     When specified, differences are computed by ‘difflib.Differ’, using
     the same algorithm as the popular ‘ndiff.py’ utility.  This is the
     only method that marks differences within lines as well as across
     lines.  For example, if a line of expected output contains digit
     ‘1’ where actual output contains letter ‘l’, a line is inserted
     with a caret marking the mismatching column positions.

 -- 資料: doctest.REPORT_ONLY_FIRST_FAILURE

     When specified, display the first failing example in each doctest,
     but suppress output for all remaining examples.  This will prevent
     doctest from reporting correct examples that break because of
     earlier failures; but it might also hide incorrect examples that
     fail independently of the first failure.  When *note
     REPORT_ONLY_FIRST_FAILURE: 3e1f. is specified, the remaining
     examples are still run, and still count towards the total number of
     failures reported; only the output is suppressed.

 -- 資料: doctest.FAIL_FAST

     When specified, exit after the first failing example and don't
     attempt to run the remaining examples.  Thus, the number of
     failures reported will be at most 1.  This flag may be useful
     during debugging, since examples after the first failure won't even
     produce debugging output.

     The doctest command line accepts the option ‘-f’ as a shorthand for
     ‘-o FAIL_FAST’.

     在 3.4 版被加入.

 -- 資料: doctest.REPORTING_FLAGS

     A bitmask or'ing together all the reporting flags above.

There is also a way to register new option flag names, though this isn't
useful unless you intend to extend *note doctest: 31. internals via
subclassing:

 -- 函式: doctest.register_optionflag (name)

     Create a new option flag with a given name, and return the new
     flag's integer value.  *note register_optionflag(): 3e21. can be
     used when subclassing *note OutputChecker: 3e22. or *note
     DocTestRunner: 3e23. to create new options that are supported by
     your subclasses.  *note register_optionflag(): 3e21. should always
     be called using the following idiom:

          MY_FLAG = register_optionflag('MY_FLAG')


File: python.info,  Node: Directives,  Next: 警告<2>,  Prev: 可選旗標,  Up: How It Works

5.26.4.9 Directives
...................

Doctest directives may be used to modify the *note option flags: ed7.
for an individual example.  Doctest directives are special Python
comments following an example's source code:

     directive             ::= "#" "doctest:" directive_options
     directive_options     ::= directive_option ("," directive_option)*
     directive_option      ::= on_or_off directive_option_name
     on_or_off             ::= "+" | "-"
     directive_option_name ::= "DONT_ACCEPT_BLANKLINE" | "NORMALIZE_WHITESPACE" | ...

Whitespace is not allowed between the ‘+’ or ‘-’ and the directive
option name.  The directive option name can be any of the option flag
names explained above.

An example's doctest directives modify doctest's behavior for that
single example.  Use ‘+’ to enable the named behavior, or ‘-’ to disable
it.

For example, this test passes:

     >>> print(list(range(20)))  # doctest: +NORMALIZE_WHITESPACE
     [0,   1,  2,  3,  4,  5,  6,  7,  8,  9,
     10,  11, 12, 13, 14, 15, 16, 17, 18, 19]

Without the directive it would fail, both because the actual output
doesn't have two blanks before the single-digit list elements, and
because the actual output is on a single line.  This test also passes,
and also requires a directive to do so:

     >>> print(list(range(20)))  # doctest: +ELLIPSIS
     [0, 1, ..., 18, 19]

Multiple directives can be used on a single physical line, separated by
commas:

     >>> print(list(range(20)))  # doctest: +ELLIPSIS, +NORMALIZE_WHITESPACE
     [0,    1, ...,   18,    19]

If multiple directive comments are used for a single example, then they
are combined:

     >>> print(list(range(20)))  # doctest: +ELLIPSIS
     ...                         # doctest: +NORMALIZE_WHITESPACE
     [0,    1, ...,   18,    19]

As the previous example shows, you can add ‘...’ lines to your example
containing only directives.  This can be useful when an example is too
long for a directive to comfortably fit on the same line:

     >>> print(list(range(5)) + list(range(10, 20)) + list(range(30, 40)))
     ... # doctest: +ELLIPSIS
     [0, ..., 4, 10, ..., 19, 30, ..., 39]

Note that since all options are disabled by default, and directives
apply only to the example they appear in, enabling options (via ‘+’ in a
directive) is usually the only meaningful choice.  However, option flags
can also be passed to functions that run doctests, establishing
different defaults.  In such cases, disabling an option via ‘-’ in a
directive can be useful.


File: python.info,  Node: 警告<2>,  Prev: Directives,  Up: How It Works

5.26.4.10 警告
..............

*note doctest: 31. is serious about requiring exact matches in expected
output.  If even a single character doesn't match, the test fails.  This
will probably surprise you a few times, as you learn exactly what Python
does and doesn't guarantee about output.  For example, when printing a
set, Python doesn't guarantee that the element is printed in any
particular order, so a test like

     >>> foo()
     {"spam", "eggs"}

is vulnerable!  One workaround is to do

     >>> foo() == {"spam", "eggs"}
     True

instead.  Another is to do

     >>> d = sorted(foo())
     >>> d
     ['eggs', 'spam']

There are others, but you get the idea.

Another bad idea is to print things that embed an object address, like

     >>> id(1.0)  # certain to fail some of the time
     7948648
     >>> class C: pass
     >>> C()  # the default repr() for instances embeds an address
     <C object at 0x00AC18F0>

The *note ELLIPSIS: 13d9. directive gives a nice approach for the last
example:

     >>> C()  # doctest: +ELLIPSIS
     <C object at 0x...>

Floating-point numbers are also subject to small output variations
across platforms, because Python defers to the platform C library for
float formatting, and C libraries vary widely in quality here.

     >>> 1./7  # risky
     0.14285714285714285
     >>> print(1./7) # safer
     0.142857142857
     >>> print(round(1./7, 6)) # much safer
     0.142857

Numbers of the form ‘I/2.**J’ are safe across all platforms, and I often
contrive doctest examples to produce numbers of that form:

     >>> 3./4  # utterly safe
     0.75

Simple fractions are also easier for people to understand, and that
makes for better documentation.


File: python.info,  Node: 基礎 API,  Next: Unittest API,  Prev: How It Works,  Up: doctest --- 測試互動式 Python 範例

5.26.4.11 基礎 API
..................

The functions *note testmod(): 13d8. and *note testfile(): 3e0b. provide
a simple interface to doctest that should be sufficient for most basic
uses.  For a less formal introduction to these two functions, see
sections *note Simple Usage; Checking Examples in Docstrings: 3e06. and
*note Simple Usage; Checking Examples in a Text File: 3e09.

 -- 函式: doctest.testfile (filename, module_relative=True, name=None,
          package=None, globs=None, verbose=None, report=True,
          optionflags=0, extraglobs=None, raise_on_error=False,
          parser=DocTestParser(), encoding=None)

     All arguments except 'filename' are optional, and should be
     specified in keyword form.

     Test examples in the file named 'filename'.  Return
     ‘(failure_count, test_count)’.

     Optional argument 'module_relative' specifies how the filename
     should be interpreted:

        * If 'module_relative' is ‘True’ (the default), then 'filename'
          specifies an OS-independent module-relative path.  By default,
          this path is relative to the calling module's directory; but
          if the 'package' argument is specified, then it is relative to
          that package.  To ensure OS-independence, 'filename' should
          use ‘/’ characters to separate path segments, and may not be
          an absolute path (i.e., it may not begin with ‘/’).

        * If 'module_relative' is ‘False’, then 'filename' specifies an
          OS-specific path.  The path may be absolute or relative;
          relative paths are resolved with respect to the current
          working directory.

     Optional argument 'name' gives the name of the test; by default, or
     if ‘None’, ‘os.path.basename(filename)’ is used.

     Optional argument 'package' is a Python package or the name of a
     Python package whose directory should be used as the base directory
     for a module-relative filename.  If no package is specified, then
     the calling module's directory is used as the base directory for
     module-relative filenames.  It is an error to specify 'package' if
     'module_relative' is ‘False’.

     Optional argument 'globs' gives a dict to be used as the globals
     when executing examples.  A new shallow copy of this dict is
     created for the doctest, so its examples start with a clean slate.
     By default, or if ‘None’, a new empty dict is used.

     Optional argument 'extraglobs' gives a dict merged into the globals
     used to execute examples.  This works like *note dict.update():
     13d0.: if 'globs' and 'extraglobs' have a common key, the
     associated value in 'extraglobs' appears in the combined dict.  By
     default, or if ‘None’, no extra globals are used.  This is an
     advanced feature that allows parameterization of doctests.  For
     example, a doctest can be written for a base class, using a generic
     name for the class, then reused to test any number of subclasses by
     passing an 'extraglobs' dict mapping the generic name to the
     subclass to be tested.

     Optional argument 'verbose' prints lots of stuff if true, and
     prints only failures if false; by default, or if ‘None’, it's true
     if and only if ‘'-v'’ is in ‘sys.argv’.

     Optional argument 'report' prints a summary at the end when true,
     else prints nothing at the end.  In verbose mode, the summary is
     detailed, else the summary is very brief (in fact, empty if all
     tests passed).

     Optional argument 'optionflags' (default value 0) takes the *note
     bitwise OR: 1f48. of option flags.  See section *note 可選旗標:
     ed7.

     Optional argument 'raise_on_error' defaults to false.  If true, an
     exception is raised upon the first failure or unexpected exception
     in an example.  This allows failures to be post-mortem debugged.
     Default behavior is to continue running examples.

     Optional argument 'parser' specifies a *note DocTestParser: 3e14.
     (or subclass) that should be used to extract tests from the files.
     It defaults to a normal parser (i.e., ‘DocTestParser()’).

     Optional argument 'encoding' specifies an encoding that should be
     used to convert the file to unicode.

 -- 函式: doctest.testmod (m=None, name=None, globs=None, verbose=None,
          report=True, optionflags=0, extraglobs=None,
          raise_on_error=False, exclude_empty=False)

     All arguments are optional, and all except for 'm' should be
     specified in keyword form.

     Test examples in docstrings in functions and classes reachable from
     module 'm' (or module *note __main__: 1. if 'm' is not supplied or
     is ‘None’), starting with ‘m.__doc__’.

     Also test examples reachable from dict ‘m.__test__’, if it exists.
     ‘m.__test__’ maps names (strings) to functions, classes and
     strings; function and class docstrings are searched for examples;
     strings are searched directly, as if they were docstrings.

     Only docstrings attached to objects belonging to module 'm' are
     searched.

     Return ‘(failure_count, test_count)’.

     Optional argument 'name' gives the name of the module; by default,
     or if ‘None’, ‘m.__name__’ is used.

     Optional argument 'exclude_empty' defaults to false.  If true,
     objects for which no doctests are found are excluded from
     consideration.  The default is a backward compatibility hack, so
     that code still using *note doctest.master.summarize: 3e2d. in
     conjunction with *note testmod(): 13d8. continues to get output for
     objects with no tests.  The 'exclude_empty' argument to the newer
     *note DocTestFinder: 1526. constructor defaults to true.

     Optional arguments 'extraglobs', 'verbose', 'report',
     'optionflags', 'raise_on_error', and 'globs' are the same as for
     function *note testfile(): 3e0b. above, except that 'globs'
     defaults to ‘m.__dict__’.

 -- 函式: doctest.run_docstring_examples (f, globs, verbose=False,
          name='NoName', compileflags=None, optionflags=0)

     Test examples associated with object 'f'; for example, 'f' may be a
     string, a module, a function, or a class object.

     A shallow copy of dictionary argument 'globs' is used for the
     execution context.

     Optional argument 'name' is used in failure messages, and defaults
     to ‘"NoName"’.

     If optional argument 'verbose' is true, output is generated even if
     there are no failures.  By default, output is generated only in
     case of an example failure.

     Optional argument 'compileflags' gives the set of flags that should
     be used by the Python compiler when running the examples.  By
     default, or if ‘None’, flags are deduced corresponding to the set
     of future features found in 'globs'.

     Optional argument 'optionflags' works as for function *note
     testfile(): 3e0b. above.


File: python.info,  Node: Unittest API,  Next: Advanced API,  Prev: 基礎 API,  Up: doctest --- 測試互動式 Python 範例

5.26.4.12 Unittest API
......................

As your collection of doctest'ed modules grows, you'll want a way to run
all their doctests systematically.  *note doctest: 31. provides two
functions that can be used to create *note unittest: ef. test suites
from modules and text files containing doctests.  To integrate with
*note unittest: ef. test discovery, include a *note load_tests: 3e31.
function in your test module:

     import unittest
     import doctest
     import my_module_with_doctests

     def load_tests(loader, tests, ignore):
         tests.addTests(doctest.DocTestSuite(my_module_with_doctests))
         return tests

There are two main functions for creating *note unittest.TestSuite: d9a.
instances from text files and modules with doctests:

 -- 函式: doctest.DocFileSuite (*paths, module_relative=True,
          package=None, setUp=None, tearDown=None, globs=None,
          optionflags=0, parser=DocTestParser(), encoding=None)

     Convert doctest tests from one or more text files to a *note
     unittest.TestSuite: d9a.

     The returned *note unittest.TestSuite: d9a. is to be run by the
     unittest framework and runs the interactive examples in each file.
     If an example in any file fails, then the synthesized unit test
     fails, and a *note failureException: 3e33. exception is raised
     showing the name of the file containing the test and a (sometimes
     approximate) line number.  If all the examples in a file are
     skipped, then the synthesized unit test is also marked as skipped.

     Pass one or more paths (as strings) to text files to be examined.

     Options may be provided as keyword arguments:

     Optional argument 'module_relative' specifies how the filenames in
     'paths' should be interpreted:

        * If 'module_relative' is ‘True’ (the default), then each
          filename in 'paths' specifies an OS-independent
          module-relative path.  By default, this path is relative to
          the calling module's directory; but if the 'package' argument
          is specified, then it is relative to that package.  To ensure
          OS-independence, each filename should use ‘/’ characters to
          separate path segments, and may not be an absolute path (i.e.,
          it may not begin with ‘/’).

        * If 'module_relative' is ‘False’, then each filename in 'paths'
          specifies an OS-specific path.  The path may be absolute or
          relative; relative paths are resolved with respect to the
          current working directory.

     Optional argument 'package' is a Python package or the name of a
     Python package whose directory should be used as the base directory
     for module-relative filenames in 'paths'.  If no package is
     specified, then the calling module's directory is used as the base
     directory for module-relative filenames.  It is an error to specify
     'package' if 'module_relative' is ‘False’.

     Optional argument 'setUp' specifies a set-up function for the test
     suite.  This is called before running the tests in each file.  The
     'setUp' function will be passed a *note DocTest: 15aa. object.  The
     setUp function can access the test globals as the 'globs' attribute
     of the test passed.

     Optional argument 'tearDown' specifies a tear-down function for the
     test suite.  This is called after running the tests in each file.
     The 'tearDown' function will be passed a *note DocTest: 15aa.
     object.  The setUp function can access the test globals as the
     'globs' attribute of the test passed.

     Optional argument 'globs' is a dictionary containing the initial
     global variables for the tests.  A new copy of this dictionary is
     created for each test.  By default, 'globs' is a new empty
     dictionary.

     Optional argument 'optionflags' specifies the default doctest
     options for the tests, created by or-ing together individual option
     flags.  See section *note 可選旗標: ed7.  See function *note
     set_unittest_reportflags(): 3e34. below for a better way to set
     reporting options.

     Optional argument 'parser' specifies a *note DocTestParser: 3e14.
     (or subclass) that should be used to extract tests from the files.
     It defaults to a normal parser (i.e., ‘DocTestParser()’).

     Optional argument 'encoding' specifies an encoding that should be
     used to convert the file to unicode.

     The global ‘__file__’ is added to the globals provided to doctests
     loaded from a text file using *note DocFileSuite(): 3e32.

 -- 函式: doctest.DocTestSuite (module=None, globs=None,
          extraglobs=None, test_finder=None, setUp=None, tearDown=None,
          optionflags=0, checker=None)

     Convert doctest tests for a module to a *note unittest.TestSuite:
     d9a.

     The returned *note unittest.TestSuite: d9a. is to be run by the
     unittest framework and runs each doctest in the module.  If any of
     the doctests fail, then the synthesized unit test fails, and a
     *note failureException: 3e33. exception is raised showing the name
     of the file containing the test and a (sometimes approximate) line
     number.  If all the examples in a docstring are skipped, then the
     synthesized unit test is also marked as skipped.

     Optional argument 'module' provides the module to be tested.  It
     can be a module object or a (possibly dotted) module name.  If not
     specified, the module calling this function is used.

     Optional argument 'globs' is a dictionary containing the initial
     global variables for the tests.  A new copy of this dictionary is
     created for each test.  By default, 'globs' is a new empty
     dictionary.

     Optional argument 'extraglobs' specifies an extra set of global
     variables, which is merged into 'globs'.  By default, no extra
     globals are used.

     Optional argument 'test_finder' is the *note DocTestFinder: 1526.
     object (or a drop-in replacement) that is used to extract doctests
     from the module.

     Optional arguments 'setUp', 'tearDown', and 'optionflags' are the
     same as for function *note DocFileSuite(): 3e32. above.

     This function uses the same search technique as *note testmod():
     13d8.

     在 3.5 版的變更: *note DocTestSuite(): d99. returns an empty *note
     unittest.TestSuite: d9a. if 'module' contains no docstrings instead
     of raising *note ValueError: 1e7.

 -- 例外: doctest.failureException

     When doctests which have been converted to unit tests by *note
     DocFileSuite(): 3e32. or *note DocTestSuite(): d99. fail, this
     exception is raised showing the name of the file containing the
     test and a (sometimes approximate) line number.

Under the covers, *note DocTestSuite(): d99. creates a *note
unittest.TestSuite: d9a. out of ‘doctest.DocTestCase’ instances, and
‘DocTestCase’ is a subclass of *note unittest.TestCase: 3f4.
‘DocTestCase’ isn't documented here (it's an internal detail), but
studying its code can answer questions about the exact details of *note
unittest: ef. integration.

Similarly, *note DocFileSuite(): 3e32. creates a *note
unittest.TestSuite: d9a. out of ‘doctest.DocFileCase’ instances, and
‘DocFileCase’ is a subclass of ‘DocTestCase’.

So both ways of creating a *note unittest.TestSuite: d9a. run instances
of ‘DocTestCase’.  This is important for a subtle reason: when you run
*note doctest: 31. functions yourself, you can control the *note
doctest: 31. options in use directly, by passing option flags to *note
doctest: 31. functions.  However, if you're writing a *note unittest:
ef. framework, *note unittest: ef. ultimately controls when and how
tests get run.  The framework author typically wants to control *note
doctest: 31. reporting options (perhaps, e.g., specified by command line
options), but there's no way to pass options through *note unittest: ef.
to *note doctest: 31. test runners.

For this reason, *note doctest: 31. also supports a notion of *note
doctest: 31. reporting flags specific to *note unittest: ef. support,
via this function:

 -- 函式: doctest.set_unittest_reportflags (flags)

     Set the *note doctest: 31. reporting flags to use.

     Argument 'flags' takes the *note bitwise OR: 1f48. of option flags.
     See section *note 可選旗標: ed7.  Only "reporting flags" can be
     used.

     This is a module-global setting, and affects all future doctests
     run by module *note unittest: ef.: the ‘runTest()’ method of
     ‘DocTestCase’ looks at the option flags specified for the test case
     when the ‘DocTestCase’ instance was constructed.  If no reporting
     flags were specified (which is the typical and expected case),
     ‘doctest’'s *note unittest: ef. reporting flags are *note bitwise
     ORed: 1f48. into the option flags, and the option flags so
     augmented are passed to the *note DocTestRunner: 3e23. instance
     created to run the doctest.  If any reporting flags were specified
     when the ‘DocTestCase’ instance was constructed, ‘doctest’'s *note
     unittest: ef. reporting flags are ignored.

     The value of the *note unittest: ef. reporting flags in effect
     before the function was called is returned by the function.


File: python.info,  Node: Advanced API,  Next: Debugging,  Prev: Unittest API,  Up: doctest --- 測試互動式 Python 範例

5.26.4.13 Advanced API
......................

The basic API is a simple wrapper that's intended to make doctest easy
to use.  It is fairly flexible, and should meet most users' needs;
however, if you require more fine-grained control over testing, or wish
to extend doctest's capabilities, then you should use the advanced API.

The advanced API revolves around two container classes, which are used
to store the interactive examples extracted from doctest cases:

   * *note Example: 3e37.: A single Python *note statement: 265e, paired
     with its expected output.

   * *note DocTest: 15aa.: A collection of *note Example: 3e37.s,
     typically extracted from a single docstring or text file.

Additional processing classes are defined to find, parse, and run, and
check doctest examples:

   * *note DocTestFinder: 1526.: Finds all docstrings in a given module,
     and uses a *note DocTestParser: 3e14. to create a *note DocTest:
     15aa. from every docstring that contains interactive examples.

   * *note DocTestParser: 3e14.: Creates a *note DocTest: 15aa. object
     from a string (such as an object's docstring).

   * *note DocTestRunner: 3e23.: Executes the examples in a *note
     DocTest: 15aa, and uses an *note OutputChecker: 3e22. to verify
     their output.

   * *note OutputChecker: 3e22.: Compares the actual output from a
     doctest example with the expected output, and decides whether they
     match.

The relationships among these processing classes are summarized in the
following diagram:

                                 list of:
     +------+                   +---------+
     |module| --DocTestFinder-> | DocTest | --DocTestRunner-> results
     +------+    |        ^     +---------+     |       ^    (printed)
                 |        |     | Example |     |       |
                 v        |     |   ...   |     v       |
                DocTestParser   | Example |   OutputChecker
                                +---------+

* Menu:

* DocTest 物件::
* Example 物件::
* DocTestFinder 物件::
* DocTestParser 物件::
* TestResults objects::
* DocTestRunner 物件::
* OutputChecker 物件::


File: python.info,  Node: DocTest 物件,  Next: Example 物件,  Up: Advanced API

5.26.4.14 DocTest 物件
......................

 -- 類別: doctest.DocTest (examples, globs, name, filename, lineno,
          docstring)

     A collection of doctest examples that should be run in a single
     namespace.  The constructor arguments are used to initialize the
     attributes of the same names.

     *note DocTest: 15aa. defines the following attributes.  They are
     initialized by the constructor, and should not be modified
     directly.

      -- 屬性: examples

          A list of *note Example: 3e37. objects encoding the individual
          interactive Python examples that should be run by this test.

      -- 屬性: globs

          The namespace (aka globals) that the examples should be run
          in.  This is a dictionary mapping names to values.  Any
          changes to the namespace made by the examples (such as binding
          new variables) will be reflected in *note globs: 3e3b. after
          the test is run.

      -- 屬性: name

          A string name identifying the *note DocTest: 15aa.  Typically,
          this is the name of the object or file that the test was
          extracted from.

      -- 屬性: filename

          The name of the file that this *note DocTest: 15aa. was
          extracted from; or ‘None’ if the filename is unknown, or if
          the *note DocTest: 15aa. was not extracted from a file.

      -- 屬性: lineno

          The line number within *note filename: 3e3d. where this *note
          DocTest: 15aa. begins, or ‘None’ if the line number is
          unavailable.  This line number is zero-based with respect to
          the beginning of the file.

      -- 屬性: docstring

          The string that the test was extracted from, or ‘None’ if the
          string is unavailable, or if the test was not extracted from a
          string.


File: python.info,  Node: Example 物件,  Next: DocTestFinder 物件,  Prev: DocTest 物件,  Up: Advanced API

5.26.4.15 Example 物件
......................

 -- 類別: doctest.Example (source, want, exc_msg=None, lineno=0,
          indent=0, options=None)

     A single interactive example, consisting of a Python statement and
     its expected output.  The constructor arguments are used to
     initialize the attributes of the same names.

     *note Example: 3e37. defines the following attributes.  They are
     initialized by the constructor, and should not be modified
     directly.

      -- 屬性: source

          A string containing the example's source code.  This source
          code consists of a single Python statement, and always ends
          with a newline; the constructor adds a newline when necessary.

      -- 屬性: want

          The expected output from running the example's source code
          (either from stdout, or a traceback in case of exception).
          *note want: 3e42. ends with a newline unless no output is
          expected, in which case it's an empty string.  The constructor
          adds a newline when necessary.

      -- 屬性: exc_msg

          The exception message generated by the example, if the example
          is expected to generate an exception; or ‘None’ if it is not
          expected to generate an exception.  This exception message is
          compared against the return value of *note
          traceback.format_exception_only(): 7f2.  *note exc_msg: 3e43.
          ends with a newline unless it's ‘None’.  The constructor adds
          a newline if needed.

      -- 屬性: lineno

          The line number within the string containing this example
          where the example begins.  This line number is zero-based with
          respect to the beginning of the containing string.

      -- 屬性: indent

          The example's indentation in the containing string, i.e., the
          number of space characters that precede the example's first
          prompt.

      -- 屬性: options

          A dictionary mapping from option flags to ‘True’ or ‘False’,
          which is used to override default options for this example.
          Any option flags not contained in this dictionary are left at
          their default value (as specified by the *note DocTestRunner:
          3e23.'s *note optionflags: ed7.).  By default, no options are
          set.


File: python.info,  Node: DocTestFinder 物件,  Next: DocTestParser 物件,  Prev: Example 物件,  Up: Advanced API

5.26.4.16 DocTestFinder 物件
............................

 -- 類別: doctest.DocTestFinder (verbose=False, parser=DocTestParser(),
          recurse=True, exclude_empty=True)

     A processing class used to extract the *note DocTest: 15aa.s that
     are relevant to a given object, from its docstring and the
     docstrings of its contained objects.  *note DocTest: 15aa.s can be
     extracted from modules, classes, functions, methods, staticmethods,
     classmethods, and properties.

     The optional argument 'verbose' can be used to display the objects
     searched by the finder.  It defaults to ‘False’ (no output).

     The optional argument 'parser' specifies the *note DocTestParser:
     3e14. object (or a drop-in replacement) that is used to extract
     doctests from docstrings.

     If the optional argument 'recurse' is false, then *note
     DocTestFinder.find(): 15fb. will only examine the given object, and
     not any contained objects.

     If the optional argument 'exclude_empty' is false, then *note
     DocTestFinder.find(): 15fb. will include tests for objects with
     empty docstrings.

     *note DocTestFinder: 1526. defines the following method:

      -- 方法: find (obj[, name][, module][, globs][, extraglobs])

          Return a list of the *note DocTest: 15aa.s that are defined by
          'obj"s docstring, or by any of its contained objects'
          docstrings.

          The optional argument 'name' specifies the object's name; this
          name will be used to construct names for the returned *note
          DocTest: 15aa.s.  If 'name' is not specified, then
          ‘obj.__name__’ is used.

          The optional parameter 'module' is the module that contains
          the given object.  If the module is not specified or is
          ‘None’, then the test finder will attempt to automatically
          determine the correct module.  The object's module is used:

             * As a default namespace, if 'globs' is not specified.

             * To prevent the DocTestFinder from extracting DocTests
               from objects that are imported from other modules.
               (Contained objects with modules other than 'module' are
               ignored.)

             * To find the name of the file containing the object.

             * To help find the line number of the object within its
               file.

          If 'module' is ‘False’, no attempt to find the module will be
          made.  This is obscure, of use mostly in testing doctest
          itself: if 'module' is ‘False’, or is ‘None’ but cannot be
          found automatically, then all objects are considered to belong
          to the (non-existent) module, so all contained objects will
          (recursively) be searched for doctests.

          The globals for each *note DocTest: 15aa. is formed by
          combining 'globs' and 'extraglobs' (bindings in 'extraglobs'
          override bindings in 'globs').  A new shallow copy of the
          globals dictionary is created for each *note DocTest: 15aa.
          If 'globs' is not specified, then it defaults to the module's
          '__dict__', if specified, or ‘{}’ otherwise.  If 'extraglobs'
          is not specified, then it defaults to ‘{}’.


File: python.info,  Node: DocTestParser 物件,  Next: TestResults objects,  Prev: DocTestFinder 物件,  Up: Advanced API

5.26.4.17 DocTestParser 物件
............................

 -- 類別: doctest.DocTestParser

     A processing class used to extract interactive examples from a
     string, and use them to create a *note DocTest: 15aa. object.

     *note DocTestParser: 3e14. defines the following methods:

      -- 方法: get_doctest (string, globs, name, filename, lineno)

          Extract all doctest examples from the given string, and
          collect them into a *note DocTest: 15aa. object.

          'globs', 'name', 'filename', and 'lineno' are attributes for
          the new *note DocTest: 15aa. object.  See the documentation
          for *note DocTest: 15aa. for more information.

      -- 方法: get_examples (string, name='<string>')

          Extract all doctest examples from the given string, and return
          them as a list of *note Example: 3e37. objects.  Line numbers
          are 0-based.  The optional argument 'name' is a name
          identifying this string, and is only used for error messages.

      -- 方法: parse (string, name='<string>')

          Divide the given string into examples and intervening text,
          and return them as a list of alternating *note Example: 3e37.s
          and strings.  Line numbers for the *note Example: 3e37.s are
          0-based.  The optional argument 'name' is a name identifying
          this string, and is only used for error messages.


File: python.info,  Node: TestResults objects,  Next: DocTestRunner 物件,  Prev: DocTestParser 物件,  Up: Advanced API

5.26.4.18 TestResults objects
.............................

 -- 類別: doctest.TestResults (failed, attempted)

      -- 屬性: failed

          Number of failed tests.

      -- 屬性: attempted

          Number of attempted tests.

      -- 屬性: skipped

          Number of skipped tests.

          在 3.13 版被加入.


File: python.info,  Node: DocTestRunner 物件,  Next: OutputChecker 物件,  Prev: TestResults objects,  Up: Advanced API

5.26.4.19 DocTestRunner 物件
............................

 -- 類別: doctest.DocTestRunner (checker=None, verbose=None,
          optionflags=0)

     A processing class used to execute and verify the interactive
     examples in a *note DocTest: 15aa.

     The comparison between expected outputs and actual outputs is done
     by an *note OutputChecker: 3e22.  This comparison may be customized
     with a number of option flags; see section *note 可選旗標: ed7. for
     more information.  If the option flags are insufficient, then the
     comparison may also be customized by passing a subclass of *note
     OutputChecker: 3e22. to the constructor.

     The test runner's display output can be controlled in two ways.
     First, an output function can be passed to *note run(): 1bf.; this
     function will be called with strings that should be displayed.  It
     defaults to ‘sys.stdout.write’.  If capturing the output is not
     sufficient, then the display output can be also customized by
     subclassing DocTestRunner, and overriding the methods *note
     report_start(): 3e54, *note report_success(): 3e55, *note
     report_unexpected_exception(): 3e56, and *note report_failure():
     3e57.

     The optional keyword argument 'checker' specifies the *note
     OutputChecker: 3e22. object (or drop-in replacement) that should be
     used to compare the expected outputs to the actual outputs of
     doctest examples.

     The optional keyword argument 'verbose' controls the *note
     DocTestRunner: 3e23.'s verbosity.  If 'verbose' is ‘True’, then
     information is printed about each example, as it is run.  If
     'verbose' is ‘False’, then only failures are printed.  If 'verbose'
     is unspecified, or ‘None’, then verbose output is used iff the
     command-line switch ‘-v’ is used.

     The optional keyword argument 'optionflags' can be used to control
     how the test runner compares expected output to actual output, and
     how it displays failures.  For more information, see section *note
     可選旗標: ed7.

     The test runner accumulates statistics.  The aggregated number of
     attempted, failed and skipped examples is also available via the
     *note tries: 3e58, *note failures: 3e59. and *note skips: 1c0.
     attributes.  The *note run(): 1bf. and *note summarize(): 3e2d.
     methods return a *note TestResults: 3e4f. instance.

     *note DocTestRunner: 3e23. defines the following methods:

      -- 方法: report_start (out, test, example)

          Report that the test runner is about to process the given
          example.  This method is provided to allow subclasses of *note
          DocTestRunner: 3e23. to customize their output; it should not
          be called directly.

          'example' is the example about to be processed.  'test' is the
          test 'containing example'.  'out' is the output function that
          was passed to *note DocTestRunner.run(): 1bf.

      -- 方法: report_success (out, test, example, got)

          Report that the given example ran successfully.  This method
          is provided to allow subclasses of *note DocTestRunner: 3e23.
          to customize their output; it should not be called directly.

          'example' is the example about to be processed.  'got' is the
          actual output from the example.  'test' is the test containing
          'example'.  'out' is the output function that was passed to
          *note DocTestRunner.run(): 1bf.

      -- 方法: report_failure (out, test, example, got)

          Report that the given example failed.  This method is provided
          to allow subclasses of *note DocTestRunner: 3e23. to customize
          their output; it should not be called directly.

          'example' is the example about to be processed.  'got' is the
          actual output from the example.  'test' is the test containing
          'example'.  'out' is the output function that was passed to
          *note DocTestRunner.run(): 1bf.

      -- 方法: report_unexpected_exception (out, test, example,
               exc_info)

          Report that the given example raised an unexpected exception.
          This method is provided to allow subclasses of *note
          DocTestRunner: 3e23. to customize their output; it should not
          be called directly.

          'example' is the example about to be processed.  'exc_info' is
          a tuple containing information about the unexpected exception
          (as returned by *note sys.exc_info(): 630.).  'test' is the
          test containing 'example'.  'out' is the output function that
          was passed to *note DocTestRunner.run(): 1bf.

      -- 方法: run (test, compileflags=None, out=None, clear_globs=True)

          Run the examples in 'test' (a *note DocTest: 15aa. object),
          and display the results using the writer function 'out'.
          Return a *note TestResults: 3e4f. instance.

          The examples are run in the namespace ‘test.globs’.  If
          'clear_globs' is true (the default), then this namespace will
          be cleared after the test runs, to help with garbage
          collection.  If you would like to examine the namespace after
          the test completes, then use 'clear_globs=False'.

          'compileflags' gives the set of flags that should be used by
          the Python compiler when running the examples.  If not
          specified, then it will default to the set of future-import
          flags that apply to 'globs'.

          The output of each example is checked using the *note
          DocTestRunner: 3e23.'s output checker, and the results are
          formatted by the ‘DocTestRunner.report_*()’ methods.

      -- 方法: summarize (verbose=None)

          Print a summary of all the test cases that have been run by
          this DocTestRunner, and return a *note TestResults: 3e4f.
          instance.

          The optional 'verbose' argument controls how detailed the
          summary is.  If the verbosity is not specified, then the *note
          DocTestRunner: 3e23.'s verbosity is used.

     *note DocTestParser: 3e14. has the following attributes:

      -- 屬性: tries

          Number of attempted examples.

      -- 屬性: failures

          Number of failed examples.

      -- 屬性: skips

          Number of skipped examples.

          在 3.13 版被加入.


File: python.info,  Node: OutputChecker 物件,  Prev: DocTestRunner 物件,  Up: Advanced API

5.26.4.20 OutputChecker 物件
............................

 -- 類別: doctest.OutputChecker

     A class used to check the whether the actual output from a doctest
     example matches the expected output.  *note OutputChecker: 3e22.
     defines two methods: *note check_output(): 3e5c, which compares a
     given pair of outputs, and returns ‘True’ if they match; and *note
     output_difference(): 3e5d, which returns a string describing the
     differences between two outputs.

     *note OutputChecker: 3e22. defines the following methods:

      -- 方法: check_output (want, got, optionflags)

          Return ‘True’ iff the actual output from an example ('got')
          matches the expected output ('want').  These strings are
          always considered to match if they are identical; but
          depending on what option flags the test runner is using,
          several non-exact match types are also possible.  See section
          *note 可選旗標: ed7. for more information about option flags.

      -- 方法: output_difference (example, got, optionflags)

          Return a string describing the differences between the
          expected output for a given example ('example') and the actual
          output ('got').  'optionflags' is the set of option flags used
          to compare 'want' and 'got'.


File: python.info,  Node: Debugging,  Next: Soapbox,  Prev: Advanced API,  Up: doctest --- 測試互動式 Python 範例

5.26.4.21 Debugging
...................

Doctest provides several mechanisms for debugging doctest examples:

   * Several functions convert doctests to executable Python programs,
     which can be run under the Python debugger, *note pdb: 94.

   * The *note DebugRunner: 3e60. class is a subclass of *note
     DocTestRunner: 3e23. that raises an exception for the first failing
     example, containing information about that example.  This
     information can be used to perform post-mortem debugging on the
     example.

   * The *note unittest: ef. cases generated by *note DocTestSuite():
     d99. support the *note debug(): 3e61. method defined by *note
     unittest.TestCase: 3f4.

   * You can add a call to *note pdb.set_trace(): 21a. in a doctest
     example, and you'll drop into the Python debugger when that line is
     executed.  Then you can inspect current values of variables, and so
     on.  For example, suppose ‘a.py’ contains just this module
     docstring:

          """
          >>> def f(x):
          ...     g(x*2)
          >>> def g(x):
          ...     print(x+3)
          ...     import pdb; pdb.set_trace()
          >>> f(3)
          9
          """

     Then an interactive Python session may look like this:

          >>> import a, doctest
          >>> doctest.testmod(a)
          --Return--
          > <doctest a[1]>(3)g()->None
          -> import pdb; pdb.set_trace()
          (Pdb) list
            1     def g(x):
            2         print(x+3)
            3  ->     import pdb; pdb.set_trace()
          [EOF]
          (Pdb) p x
          6
          (Pdb) step
          --Return--
          > <doctest a[0]>(2)f()->None
          -> g(x*2)
          (Pdb) list
            1     def f(x):
            2  ->     g(x*2)
          [EOF]
          (Pdb) p x
          3
          (Pdb) step
          --Return--
          > <doctest a[2]>(1)?()->None
          -> f(3)
          (Pdb) cont
          (0, 3)
          >>>

Functions that convert doctests to Python code, and possibly run the
synthesized code under the debugger:

 -- 函式: doctest.script_from_examples (s)

     Convert text with examples to a script.

     Argument 's' is a string containing doctest examples.  The string
     is converted to a Python script, where doctest examples in 's' are
     converted to regular code, and everything else is converted to
     Python comments.  The generated script is returned as a string.
     For example,

          import doctest
          print(doctest.script_from_examples(r"""
              Set x and y to 1 and 2.
              >>> x, y = 1, 2

              Print their sum:
              >>> print(x+y)
              3
          """))

     displays:

          # Set x and y to 1 and 2.
          x, y = 1, 2
          #
          # Print their sum:
          print(x+y)
          # Expected:
          ## 3

     This function is used internally by other functions (see below),
     but can also be useful when you want to transform an interactive
     Python session into a Python script.

 -- 函式: doctest.testsource (module, name)

     Convert the doctest for an object to a script.

     Argument 'module' is a module object, or dotted name of a module,
     containing the object whose doctests are of interest.  Argument
     'name' is the name (within the module) of the object with the
     doctests of interest.  The result is a string, containing the
     object's docstring converted to a Python script, as described for
     *note script_from_examples(): 3e62. above.  For example, if module
     ‘a.py’ contains a top-level function ‘f()’, then

          import a, doctest
          print(doctest.testsource(a, "a.f"))

     prints a script version of function ‘f()’'s docstring, with
     doctests converted to code, and the rest placed in comments.

 -- 函式: doctest.debug (module, name, pm=False)

     Debug the doctests for an object.

     The 'module' and 'name' arguments are the same as for function
     *note testsource(): 3e63. above.  The synthesized Python script for
     the named object's docstring is written to a temporary file, and
     then that file is run under the control of the Python debugger,
     *note pdb: 94.

     A shallow copy of ‘module.__dict__’ is used for both local and
     global execution context.

     Optional argument 'pm' controls whether post-mortem debugging is
     used.  If 'pm' has a true value, the script file is run directly,
     and the debugger gets involved only if the script terminates via
     raising an unhandled exception.  If it does, then post-mortem
     debugging is invoked, via *note pdb.post_mortem(): 1348, passing
     the traceback object from the unhandled exception.  If 'pm' is not
     specified, or is false, the script is run under the debugger from
     the start, via passing an appropriate *note exec(): 162. call to
     *note pdb.run(): 3e64.

 -- 函式: doctest.debug_src (src, pm=False, globs=None)

     Debug the doctests in a string.

     This is like function *note debug(): 3e61. above, except that a
     string containing doctest examples is specified directly, via the
     'src' argument.

     Optional argument 'pm' has the same meaning as in function *note
     debug(): 3e61. above.

     Optional argument 'globs' gives a dictionary to use as both local
     and global execution context.  If not specified, or ‘None’, an
     empty dictionary is used.  If specified, a shallow copy of the
     dictionary is used.

The *note DebugRunner: 3e60. class, and the special exceptions it may
raise, are of most interest to testing framework authors, and will only
be sketched here.  See the source code, and especially *note
DebugRunner: 3e60.'s docstring (which is a doctest!)  for more details:

 -- 類別: doctest.DebugRunner (checker=None, verbose=None,
          optionflags=0)

     A subclass of *note DocTestRunner: 3e23. that raises an exception
     as soon as a failure is encountered.  If an unexpected exception
     occurs, an *note UnexpectedException: 3e66. exception is raised,
     containing the test, the example, and the original exception.  If
     the output doesn't match, then a *note DocTestFailure: 3e67.
     exception is raised, containing the test, the example, and the
     actual output.

     For information about the constructor parameters and methods, see
     the documentation for *note DocTestRunner: 3e23. in section *note
     Advanced API: 3e36.

There are two exceptions that may be raised by *note DebugRunner: 3e60.
instances:

 -- 例外: doctest.DocTestFailure (test, example, got)

     An exception raised by *note DocTestRunner: 3e23. to signal that a
     doctest example's actual output did not match its expected output.
     The constructor arguments are used to initialize the attributes of
     the same names.

*note DocTestFailure: 3e67. 定義了以下屬性：

 -- 屬性: DocTestFailure.test

     The *note DocTest: 15aa. object that was being run when the example
     failed.

 -- 屬性: DocTestFailure.example

     The *note Example: 3e37. that failed.

 -- 屬性: DocTestFailure.got

     The example's actual output.

 -- 例外: doctest.UnexpectedException (test, example, exc_info)

     An exception raised by *note DocTestRunner: 3e23. to signal that a
     doctest example raised an unexpected exception.  The constructor
     arguments are used to initialize the attributes of the same names.

*note UnexpectedException: 3e66. defines the following attributes:

 -- 屬性: UnexpectedException.test

     The *note DocTest: 15aa. object that was being run when the example
     failed.

 -- 屬性: UnexpectedException.example

     The *note Example: 3e37. that failed.

 -- 屬性: UnexpectedException.exc_info

     A tuple containing information about the unexpected exception, as
     returned by *note sys.exc_info(): 630.


File: python.info,  Node: Soapbox,  Prev: Debugging,  Up: doctest --- 測試互動式 Python 範例

5.26.4.22 Soapbox
.................

As mentioned in the introduction, *note doctest: 31. has grown to have
three primary uses:

  1. Checking examples in docstrings.

  2. Regression testing.

  3. Executable documentation / literate testing.

These uses have different requirements, and it is important to
distinguish them.  In particular, filling your docstrings with obscure
test cases makes for bad documentation.

When writing a docstring, choose docstring examples with care.  There's
an art to this that needs to be learned--it may not be natural at first.
Examples should add genuine value to the documentation.  A good example
can often be worth many words.  If done with care, the examples will be
invaluable for your users, and will pay back the time it takes to
collect them many times over as the years go by and things change.  I'm
still amazed at how often one of my *note doctest: 31. examples stops
working after a "harmless" change.

Doctest also makes an excellent tool for regression testing, especially
if you don't skimp on explanatory text.  By interleaving prose and
examples, it becomes much easier to keep track of what's actually being
tested, and why.  When a test fails, good prose can make it much easier
to figure out what the problem is, and how it should be fixed.  It's
true that you could write extensive comments in code-based testing, but
few programmers do.  Many have found that using doctest approaches
instead leads to much clearer tests.  Perhaps this is simply because
doctest makes writing prose a little easier than writing code, while
writing comments in code is a little harder.  I think it goes deeper
than just that: the natural attitude when writing a doctest-based test
is that you want to explain the fine points of your software, and
illustrate them with examples.  This in turn naturally leads to test
files that start with the simplest features, and logically progress to
complications and edge cases.  A coherent narrative is the result,
instead of a collection of isolated functions that test isolated bits of
functionality seemingly at random.  It's a different attitude, and
produces different results, blurring the distinction between testing and
explaining.

Regression testing is best confined to dedicated objects or files.
There are several options for organizing tests:

   * Write text files containing test cases as interactive examples, and
     test the files using *note testfile(): 3e0b. or *note
     DocFileSuite(): 3e32.  This is recommended, although is easiest to
     do for new projects, designed from the start to use doctest.

   * Define functions named ‘_regrtest_topic’ that consist of single
     docstrings, containing test cases for the named topics.  These
     functions can be included in the same file as the module, or
     separated out into a separate test file.

   * Define a ‘__test__’ dictionary mapping from regression test topics
     to docstrings containing test cases.

When you have placed your tests in a module, the module can itself be
the test runner.  When a test fails, you can arrange for your test
runner to re-run only the failing doctest while you debug the problem.
Here is a minimal example of such a test runner:

     if __name__ == '__main__':
         import doctest
         flags = doctest.REPORT_NDIFF|doctest.FAIL_FAST
         if len(sys.argv) > 1:
             name = sys.argv[1]
             if name in globals():
                 obj = globals()[name]
             else:
                 obj = __test__[name]
             doctest.run_docstring_examples(obj, globals(), name=name,
                                            optionflags=flags)
         else:
             fail, total = doctest.testmod(optionflags=flags)
             print(f"{fail} failures out of {total} tests")

註解
....


File: python.info,  Node: unittest --- 單元測試框架,  Next: unittest mock — mock 物件函式庫,  Prev: doctest --- 測試互動式 Python 範例,  Up: 開發工具

5.26.5 ‘unittest’ -- 單元測試框架
---------------------------------

'原始碼：'Lib/unittest/__init__.py(1)

__________________________________________________________________

（假如你已經熟悉相關基礎的測試概念，你可能會希望跳過以下段落，直接參考
*note assert 方法清單: 3e72.。）

*note unittest: ef. 原生的單元測試框架最初由 JUnit 開發，和其他程式語言
相似有主要的單元測試框架。支援自動化測試，對測試分享安裝與關閉程式碼，集
合所有匯總的測試，並且獨立各個測試報告框架。

*note unittest: ef. 用來作為實現支援一些重要的物件導向方法的概念：

test fixture

     一個 'test fixture' 代表執行一個或多個測試所需要的準備，以及其他相
     關清理操作，例如可以是建立臨時性的或是代理用 (proxy) 資料庫、目錄、
     或是啟動一個伺服器程序。

test case（測試用例）

     一個 'test case' 是一個獨立的單元測試。這是用來確認一個特定設定的輸
     入的特殊回饋。 *note unittest: ef. 提供一個基礎類別，類別 *note
     TestCase: 3f4.，可以用來建立一個新的測試條例。

test suite（測試套件）

     'test suite' 是一個搜集測試條例，測試套件，或是兩者皆有。它需要一起
     被執行並用來匯總測試。

test runner（測試執行器）

     'test runner' 是一個編排測試執行與提供結果給使用者的一個元件。執行
     器可以使用圖形化介面，文字介面或是回傳一個特別值用來標示出執行測試
     的結果。

也參考
......

*note doctest: 31. 模組

     另一個執行測試的模組，但使用不一樣的測試方法與規範。

Simple Smalltalk Testing: With Patterns(2)

     Kent Beck 的原始論文討論使用 *note unittest: ef. 這樣模式的測試框架
     。

pytest(3)

     第三方的單元測試框架，但在撰寫測試時使用更輕量的語法。例如：
     ‘assert func(10) == 42’。

The Python Testing Tools Taxonomy(4)

     一份詳細的 Python 測試工具列表，包含 functional testing 框架和mock
     object 函式庫。

Testing in Python Mailing List(5)

     一個專門興趣的群組用來討論 Python 中的測試方式與測試工具。

The script ‘Tools/unittestgui/unittestgui.py’ in the Python source
distribution is a GUI tool for test discovery and execution.  This is
intended largely for ease of use for those new to unit testing.  For
production environments it is recommended that tests be driven by a
continuous integration system such as Buildbot(6), Jenkins(7), GitHub
Actions(8), or AppVeyor(9).

* Menu:

* 簡單範例::
* 命令執行列介面 (Command-Line Interface): 命令執行列介面 Command-Line Interface.
* Test Discovery（測試探索）::
* Organizing test code::
* Re-using old test code::
* Skipping tests and expected failures::
* Distinguishing test iterations using subtests::
* Classes and functions::
* Class and Module Fixtures::
* Signal Handling::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/unittest/__init__.py

   (2) 
https://web.archive.org/web/20150315073817/http://www.xprogramming.com/testfram.htm

   (3) https://docs.pytest.org/

   (4) https://wiki.python.org/moin/PythonTestingToolsTaxonomy

   (5) http://lists.idyll.org/listinfo/testing-in-python

   (6) https://buildbot.net/

   (7) https://www.jenkins.io/

   (8) https://github.com/features/actions

   (9) https://www.appveyor.com/


File: python.info,  Node: 簡單範例,  Next: 命令執行列介面 Command-Line Interface,  Up: unittest --- 單元測試框架

5.26.5.1 簡單範例
.................

*note unittest: ef. 模組提供一系列豐富的工具用來建構與執行測試。本節將展
示這一系列工具中一部份，它們已能滿足大部份使用者需求。

這是一段簡短的腳本用來測試 3 個字串方法：

     import unittest

     class TestStringMethods(unittest.TestCase):

         def test_upper(self):
             self.assertEqual('foo'.upper(), 'FOO')

         def test_isupper(self):
             self.assertTrue('FOO'.isupper())
             self.assertFalse('Foo'.isupper())

         def test_split(self):
             s = 'hello world'
             self.assertEqual(s.split(), ['hello', 'world'])
             # check that s.split fails when the separator is not a string
             with self.assertRaises(TypeError):
                 s.split(2)

     if __name__ == '__main__':
         unittest.main()

測試用例 (testcase) 可以透過繼承 *note unittest.TestCase: 3f4. 類別來建
立。這裡定義了三個獨立的物件方法，名稱皆以 ‘test’ 開頭。這樣的命名方式能
告知 test runner 哪些物件方法為定義的測試。

每個測試的關鍵為呼叫 *note assertEqual(): 4cd. 來確認是否為期望的結果；
*note assertTrue(): 4cb. 或是 *note assertFalse(): 4cc. 用來驗證一個條件
式； *note assertRaises(): 4d1. 用來驗證是否觸發一個特定的 exception。使
用這些物件方法來取代 *note assert: 90c. 陳述句，將能使 test runner 收集
所有的測試結果並產生一個報表。

The *note setUp(): 12cd. and *note tearDown(): 12ce. methods allow you
to define instructions that will be executed before and after each test
method.  They are covered in more detail in the section *note Organizing
test code: 3e75.

最後將顯示一個簡單的方法去執行測試 *note unittest.main(): f86. 提供一個
命令執行列介面測試腳本。當透過命令執行列執行，輸出結果將會像是：

     ...
     ----------------------------------------------------------------------
     Ran 3 tests in 0.000s

     OK

在測試時加入 ‘-v’ 選項將指示 *note unittest.main(): f86. 提高 verbosity
層級，產生以下的輸出：

     test_isupper (__main__.TestStringMethods.test_isupper) ... ok
     test_split (__main__.TestStringMethods.test_split) ... ok
     test_upper (__main__.TestStringMethods.test_upper) ... ok

     ----------------------------------------------------------------------
     Ran 3 tests in 0.001s

     OK

以上的例子顯示大多數使用 *note unittest: ef. 特徵足以滿足大多數日常測試
的需求。接下來第一部分文件的剩餘部分將繼續探索完整特徵設定。

在 3.11 版的變更: The behavior of returning a value from a test method
(other than the default ‘None’ value), is now deprecated.


File: python.info,  Node: 命令執行列介面 Command-Line Interface,  Next: Test Discovery（測試探索）,  Prev: 簡單範例,  Up: unittest --- 單元測試框架

5.26.5.2 命令執行列介面 (Command-Line Interface)
................................................

單元測試模組可以透過命令執行列執行測試模組，物件甚至個別的測試方法：

     python -m unittest test_module1 test_module2
     python -m unittest test_module.TestClass
     python -m unittest test_module.TestClass.test_method

你可以通過一個串列與任何模組名稱的組合，完全符合類別與方法的名稱。

測試模組可以根據檔案路徑指定：

     python -m unittest tests/test_something.py

這允許你使用 shell 檔案名稱補完功能 (filename completion) 來指定測試模組
。給定的檔案路徑必須亦能被當作模組 import。此路徑轉換為模組名稱的方式為
移除 '.py' 並將路徑分隔符 (path separator) 轉換成 '.'。 假如你的測試檔案
無法被 import 成模組，你應該直接執行該測試檔案。

通過增加 -v 的旗標數，可以在你執行測試時得到更多細節（更高的 verbosity）
：

     python -m unittest -v test_module

若執行時不代任何引數，將執行 *note Test Discovery（測試探索）: 3e78.：

     python -m unittest

列出所有命令列選項：

     python -m unittest -h

在 3.2 版的變更: 在早期的版本可以個別執行測試方法和不需要模組或是類別。

* Menu:

* 命令列模式選項::


File: python.info,  Node: 命令列模式選項,  Up: 命令執行列介面 Command-Line Interface

5.26.5.3 命令列模式選項
.......................

‘unittest’ 支援以下命令列選項：

 -- Option: -b, --buffer

     Standard output 與 standard error stream 將在測試執行被緩衝
     (buffer)。這些輸出在測試通過時被丟棄。若是測試錯誤或失則，這些輸出
     將會正常地被印出，並且被加入至錯誤訊息中。

 -- Option: -c, --catch

     ‘Control-C’ 測試執行過程中等待正確的測試結果並回報目前為止所有的測
     試結果。第二個 ‘Control-C’ 拋出一般例外 *note KeyboardInterrupt:
     975.。

     參照 *note Signal Handling: 3e7c. 針對函式提供的功能。

 -- Option: -f, --failfast

     在第一次錯誤或是失敗停止執行測試。

 -- Option: -k

     Only run test methods and classes that match the pattern or
     substring.  This option may be used multiple times, in which case
     all test cases that match any of the given patterns are included.

     Patterns that contain a wildcard character (‘*’) are matched
     against the test name using *note fnmatch.fnmatchcase(): 17a3.;
     otherwise simple case-sensitive substring matching is used.

     Patterns are matched against the fully qualified test method name
     as imported by the test loader.

     For example, ‘-k foo’ matches ‘foo_tests.SomeTest.test_something’,
     ‘bar_tests.SomeTest.test_foo’, but not
     ‘bar_tests.FooTest.test_something’.

 -- Option: --locals

     透過 traceback 顯示本地變數。

 -- Option: --durations N

     Show the N slowest test cases (N=0 for all).

在 3.2 版被加入: 增加命令列模式選項 ‘-b’ 、 ‘-c’ 與 ‘-f’。

在 3.5 版被加入: 命令列選項 ‘--locals’。

在 3.7 版被加入: 命令列選項 ‘-k’。

在 3.12 版被加入: 命令列選項 ‘--durations’。

對執行所有的專案或是一個子集合測試，命令列模式可以可以被用來做測試探索。


File: python.info,  Node: Test Discovery（測試探索）,  Next: Organizing test code,  Prev: 命令執行列介面 Command-Line Interface,  Up: unittest --- 單元測試框架

5.26.5.4 Test Discovery（測試探索）
...................................

在 3.2 版被加入.

單元測試支援簡單的 test discovery（測試探索）。為了相容於測試探索，所有
的測試檔案都要是*note 模組: 1b5a.或是*note 套件: 1b6b.，並能從專案的最上
層目錄中 import（代表它們的檔案名稱必須是有效的 *note identifiers:
1d86.）。

Test discovery（測試探索）實作在 *note TestLoader.discover(): f88.，但也
可以被用於命令列模式。基本的命令列模式用法如下：

     cd project_directory
     python -m unittest discover

     備註: ‘python -m unittest’ 作為捷徑，其功能相當於 ‘python -m
     unittest discover’。假如你想傳遞引數至探索測試的話，一定要明確地加
     入 ‘discover’ 子指令。

‘discover’ 子指令有以下幾個選項：

 -- Option: -v, --verbose

     詳細（verbose）輸出

 -- Option: -s, --start-directory directory

     開始尋找的資料夾（預設為 ‘.’）

 -- Option: -p, --pattern pattern

     匹配測試檔案的模式（預設為 ‘test*.py’）

 -- Option: -t, --top-level-directory directory

     專案的最高階層目錄 (defaults to start directory)

*note -s: 3e84, *note -p: 3e86, 和 *note -t: 3e88. 選項依照傳遞位置作為
引數排序順序。以下兩個命令列被視為等價：

     python -m unittest discover -s project_directory -p "*_test.py"
     python -m unittest discover project_directory "*_test.py"

As well as being a path it is possible to pass a package name, for
example ‘myproject.subpackage.test’, as the start directory.  The
package name you supply will then be imported and its location on the
filesystem will be used as the start directory.

     警示: Test discovery loads tests by importing them.  Once test
     discovery has found all the test files from the start directory you
     specify it turns the paths into package names to import.  For
     example ‘foo/bar/baz.py’ will be imported as ‘foo.bar.baz’.

     If you have a package installed globally and attempt test discovery
     on a different copy of the package then the import 'could' happen
     from the wrong place.  If this happens test discovery will warn you
     and exit.

     If you supply the start directory as a package name rather than a
     path to a directory then discover assumes that whichever location
     it imports from is the location you intended, so you will not get
     the warning.

Test modules and packages can customize test loading and discovery by
through the *note load_tests protocol: 3e8a.

在 3.4 版的變更: Test discovery supports *note namespace packages: 1b6c.
for the start directory.  Note that you need to specify the top level
directory too (e.g.  ‘python -m unittest discover -s root/namespace -t
root’).

在 3.11 版的變更: *note unittest: ef. dropped the *note namespace
packages: 1b6c. support in Python 3.11.  It has been broken since Python
3.7.  Start directory and subdirectories containing tests must be
regular package that have ‘__init__.py’ file.

Directories containing start directory still can be a namespace package.
In this case, you need to specify start directory as dotted package
name, and target directory explicitly.  For example:

     # proj/  <-- current directory
     #   namespace/
     #     mypkg/
     #       __init__.py
     #       test_mypkg.py

     python -m unittest discover -s namespace.mypkg -t .


File: python.info,  Node: Organizing test code,  Next: Re-using old test code,  Prev: Test Discovery（測試探索）,  Up: unittest --- 單元測試框架

5.26.5.5 Organizing test code
.............................

The basic building blocks of unit testing are 'test cases' -- single
scenarios that must be set up and checked for correctness.  In *note
unittest: ef, test cases are represented by *note unittest.TestCase:
3f4. instances.  To make your own test cases you must write subclasses
of *note TestCase: 3f4. or use *note FunctionTestCase: 1605.

The testing code of a *note TestCase: 3f4. instance should be entirely
self contained, such that it can be run either in isolation or in
arbitrary combination with any number of other test cases.

The simplest *note TestCase: 3f4. subclass will simply implement a test
method (i.e.  a method whose name starts with ‘test’) in order to
perform specific testing code:

     import unittest

     class DefaultWidgetSizeTestCase(unittest.TestCase):
         def test_default_widget_size(self):
             widget = Widget('The widget')
             self.assertEqual(widget.size(), (50, 50))

Note that in order to test something, we use one of the *note assert*
methods: 3e72. provided by the *note TestCase: 3f4. base class.  If the
test fails, an exception will be raised with an explanatory message, and
*note unittest: ef. will identify the test case as a 'failure'.  Any
other exceptions will be treated as 'errors'.

Tests can be numerous, and their set-up can be repetitive.  Luckily, we
can factor out set-up code by implementing a method called *note
setUp(): 12cd, which the testing framework will automatically call for
every single test we run:

     import unittest

     class WidgetTestCase(unittest.TestCase):
         def setUp(self):
             self.widget = Widget('The widget')

         def test_default_widget_size(self):
             self.assertEqual(self.widget.size(), (50,50),
                              'incorrect default size')

         def test_widget_resize(self):
             self.widget.resize(100,150)
             self.assertEqual(self.widget.size(), (100,150),
                              'wrong size after resize')

     備註: The order in which the various tests will be run is
     determined by sorting the test method names with respect to the
     built-in ordering for strings.

If the *note setUp(): 12cd. method raises an exception while the test is
running, the framework will consider the test to have suffered an error,
and the test method will not be executed.

Similarly, we can provide a *note tearDown(): 12ce. method that tidies
up after the test method has been run:

     import unittest

     class WidgetTestCase(unittest.TestCase):
         def setUp(self):
             self.widget = Widget('The widget')

         def tearDown(self):
             self.widget.dispose()

If *note setUp(): 12cd. succeeded, *note tearDown(): 12ce. will be run
whether the test method succeeded or not.

Such a working environment for the testing code is called a 'test
fixture'.  A new TestCase instance is created as a unique test fixture
used to execute each individual test method.  Thus *note setUp(): 12cd,
*note tearDown(): 12ce, and ‘__init__()’ will be called once per test.

It is recommended that you use TestCase implementations to group tests
together according to the features they test.  *note unittest: ef.
provides a mechanism for this: the 'test suite', represented by *note
unittest: ef.'s *note TestSuite: d9a. class.  In most cases, calling
*note unittest.main(): f86. will do the right thing and collect all the
module's test cases for you and execute them.

However, should you want to customize the building of your test suite,
you can do it yourself:

     def suite():
         suite = unittest.TestSuite()
         suite.addTest(WidgetTestCase('test_default_widget_size'))
         suite.addTest(WidgetTestCase('test_widget_resize'))
         return suite

     if __name__ == '__main__':
         runner = unittest.TextTestRunner()
         runner.run(suite())

You can place the definitions of test cases and test suites in the same
modules as the code they are to test (such as ‘widget.py’), but there
are several advantages to placing the test code in a separate module,
such as ‘test_widget.py’:

   * The test module can be run standalone from the command line.

   * The test code can more easily be separated from shipped code.

   * There is less temptation to change test code to fit the code it
     tests without a good reason.

   * Test code should be modified much less frequently than the code it
     tests.

   * Tested code can be refactored more easily.

   * Tests for modules written in C must be in separate modules anyway,
     so why not be consistent?

   * If the testing strategy changes, there is no need to change the
     source code.


File: python.info,  Node: Re-using old test code,  Next: Skipping tests and expected failures,  Prev: Organizing test code,  Up: unittest --- 單元測試框架

5.26.5.6 Re-using old test code
...............................

Some users will find that they have existing test code that they would
like to run from *note unittest: ef, without converting every old test
function to a *note TestCase: 3f4. subclass.

For this reason, *note unittest: ef. provides a *note FunctionTestCase:
1605. class.  This subclass of *note TestCase: 3f4. can be used to wrap
an existing test function.  Set-up and tear-down functions can also be
provided.

Given the following test function:

     def testSomething():
         something = makeSomething()
         assert something.name is not None
         # ...

one can create an equivalent test case instance as follows, with
optional set-up and tear-down methods:

     testcase = unittest.FunctionTestCase(testSomething,
                                          setUp=makeSomethingDB,
                                          tearDown=deleteSomethingDB)

     備註: Even though *note FunctionTestCase: 1605. can be used to
     quickly convert an existing test base over to a *note unittest:
     ef.-based system, this approach is not recommended.  Taking the
     time to set up proper *note TestCase: 3f4. subclasses will make
     future test refactorings infinitely easier.

In some cases, the existing tests may have been written using the *note
doctest: 31. module.  If so, *note doctest: 31. provides a
‘DocTestSuite’ class that can automatically build *note
unittest.TestSuite: d9a. instances from the existing *note doctest:
31.-based tests.


File: python.info,  Node: Skipping tests and expected failures,  Next: Distinguishing test iterations using subtests,  Prev: Re-using old test code,  Up: unittest --- 單元測試框架

5.26.5.7 Skipping tests and expected failures
.............................................

在 3.1 版被加入.

Unittest supports skipping individual test methods and even whole
classes of tests.  In addition, it supports marking a test as an
"expected failure," a test that is broken and will fail, but shouldn't
be counted as a failure on a *note TestResult: 1100.

Skipping a test is simply a matter of using the *note skip(): 18de.
*note decorator: 6d5. or one of its conditional variants, calling *note
TestCase.skipTest(): 3e90. within a *note setUp(): 12cd. or test method,
or raising *note SkipTest: f87. directly.

Basic skipping looks like this:

     class MyTestCase(unittest.TestCase):

         @unittest.skip("demonstrating skipping")
         def test_nothing(self):
             self.fail("shouldn't happen")

         @unittest.skipIf(mylib.__version__ < (1, 3),
                          "not supported in this library version")
         def test_format(self):
             # Tests that work for only a certain version of the library.
             pass

         @unittest.skipUnless(sys.platform.startswith("win"), "requires Windows")
         def test_windows_support(self):
             # windows specific testing code
             pass

         def test_maybe_skipped(self):
             if not external_resource_available():
                 self.skipTest("external resource not available")
             # test code that depends on the external resource
             pass

This is the output of running the example above in verbose mode:

     test_format (__main__.MyTestCase.test_format) ... skipped 'not supported in this library version'
     test_nothing (__main__.MyTestCase.test_nothing) ... skipped 'demonstrating skipping'
     test_maybe_skipped (__main__.MyTestCase.test_maybe_skipped) ... skipped 'external resource not available'
     test_windows_support (__main__.MyTestCase.test_windows_support) ... skipped 'requires Windows'

     ----------------------------------------------------------------------
     Ran 4 tests in 0.005s

     OK (skipped=4)

Classes can be skipped just like methods:

     @unittest.skip("showing class skipping")
     class MySkippedTestCase(unittest.TestCase):
         def test_not_run(self):
             pass

*note TestCase.setUp(): 12cd. can also skip the test.  This is useful
when a resource that needs to be set up is not available.

Expected failures use the *note expectedFailure(): 3e91. decorator.

     class ExpectedFailureTestCase(unittest.TestCase):
         @unittest.expectedFailure
         def test_fail(self):
             self.assertEqual(1, 0, "broken")

It's easy to roll your own skipping decorators by making a decorator
that calls *note skip(): 18de. on the test when it wants it to be
skipped.  This decorator skips the test unless the passed object has a
certain attribute:

     def skipUnlessHasattr(obj, attr):
         if hasattr(obj, attr):
             return lambda func: func
         return unittest.skip("{!r} doesn't have {!r}".format(obj, attr))

The following decorators and exception implement test skipping and
expected failures:

 -- 函式: @unittest.skip (reason)

     Unconditionally skip the decorated test.  'reason' should describe
     why the test is being skipped.

 -- 函式: @unittest.skipIf (condition, reason)

     Skip the decorated test if 'condition' is true.

 -- 函式: @unittest.skipUnless (condition, reason)

     Skip the decorated test unless 'condition' is true.

 -- 函式: @unittest.expectedFailure

     Mark the test as an expected failure or error.  If the test fails
     or errors in the test function itself (rather than in one of the
     'test fixture' methods) then it will be considered a success.  If
     the test passes, it will be considered a failure.

 -- 例外: unittest.SkipTest (reason)

     This exception is raised to skip a test.

     Usually you can use *note TestCase.skipTest(): 3e90. or one of the
     skipping decorators instead of raising this directly.

Skipped tests will not have *note setUp(): 12cd. or *note tearDown():
12ce. run around them.  Skipped classes will not have *note
setUpClass(): 9f2. or *note tearDownClass(): 12cb. run.  Skipped modules
will not have ‘setUpModule()’ or ‘tearDownModule()’ run.


File: python.info,  Node: Distinguishing test iterations using subtests,  Next: Classes and functions,  Prev: Skipping tests and expected failures,  Up: unittest --- 單元測試框架

5.26.5.8 Distinguishing test iterations using subtests
......................................................

在 3.4 版被加入.

When there are very small differences among your tests, for instance
some parameters, unittest allows you to distinguish them inside the body
of a test method using the *note subTest(): f84. context manager.

舉例來說，以下測試：

     class NumbersTest(unittest.TestCase):

         def test_even(self):
             """
             Test that numbers between 0 and 5 are all even.
             """
             for i in range(0, 6):
                 with self.subTest(i=i):
                     self.assertEqual(i % 2, 0)

會有以下輸出：

     ======================================================================
     FAIL: test_even (__main__.NumbersTest.test_even) (i=1)
     Test that numbers between 0 and 5 are all even.
     ----------------------------------------------------------------------
     Traceback (most recent call last):
       File "subtests.py", line 11, in test_even
         self.assertEqual(i % 2, 0)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^
     AssertionError: 1 != 0

     ======================================================================
     FAIL: test_even (__main__.NumbersTest.test_even) (i=3)
     Test that numbers between 0 and 5 are all even.
     ----------------------------------------------------------------------
     Traceback (most recent call last):
       File "subtests.py", line 11, in test_even
         self.assertEqual(i % 2, 0)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^
     AssertionError: 1 != 0

     ======================================================================
     FAIL: test_even (__main__.NumbersTest.test_even) (i=5)
     Test that numbers between 0 and 5 are all even.
     ----------------------------------------------------------------------
     Traceback (most recent call last):
       File "subtests.py", line 11, in test_even
         self.assertEqual(i % 2, 0)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^
     AssertionError: 1 != 0

Without using a subtest, execution would stop after the first failure,
and the error would be less easy to diagnose because the value of ‘i’
wouldn't be displayed:

     ======================================================================
     FAIL: test_even (__main__.NumbersTest.test_even)
     ----------------------------------------------------------------------
     Traceback (most recent call last):
       File "subtests.py", line 32, in test_even
         self.assertEqual(i % 2, 0)
     AssertionError: 1 != 0


File: python.info,  Node: Classes and functions,  Next: Class and Module Fixtures,  Prev: Distinguishing test iterations using subtests,  Up: unittest --- 單元測試框架

5.26.5.9 Classes and functions
..............................

This section describes in depth the API of *note unittest: ef.

* Menu:

* Test cases::
* Grouping tests::
* Loading and running tests::


File: python.info,  Node: Test cases,  Next: Grouping tests,  Up: Classes and functions

5.26.5.10 Test cases
....................

 -- 類別: unittest.TestCase (methodName='runTest')

     Instances of the *note TestCase: 3f4. class represent the logical
     test units in the *note unittest: ef. universe.  This class is
     intended to be used as a base class, with specific tests being
     implemented by concrete subclasses.  This class implements the
     interface needed by the test runner to allow it to drive the tests,
     and methods that the test code can use to check for and report
     various kinds of failure.

     Each instance of *note TestCase: 3f4. will run a single base
     method: the method named 'methodName'.  In most uses of *note
     TestCase: 3f4, you will neither change the 'methodName' nor
     reimplement the default ‘runTest()’ method.

     在 3.2 版的變更: *note TestCase: 3f4. can be instantiated
     successfully without providing a 'methodName'.  This makes it
     easier to experiment with *note TestCase: 3f4. from the interactive
     interpreter.

     *note TestCase: 3f4. instances provide three groups of methods: one
     group used to run the test, another used by the test implementation
     to check conditions and report failures, and some inquiry methods
     allowing information about the test itself to be gathered.

     Methods in the first group (running the test) are:

      -- 方法: setUp ()

          Method called to prepare the test fixture.  This is called
          immediately before calling the test method; other than *note
          AssertionError: 64e. or *note SkipTest: f87, any exception
          raised by this method will be considered an error rather than
          a test failure.  The default implementation does nothing.

      -- 方法: tearDown ()

          Method called immediately after the test method has been
          called and the result recorded.  This is called even if the
          test method raised an exception, so the implementation in
          subclasses may need to be particularly careful about checking
          internal state.  Any exception, other than *note
          AssertionError: 64e. or *note SkipTest: f87, raised by this
          method will be considered an additional error rather than a
          test failure (thus increasing the total number of reported
          errors).  This method will only be called if the *note
          setUp(): 12cd. succeeds, regardless of the outcome of the test
          method.  The default implementation does nothing.

      -- 方法: setUpClass ()

          A class method called before tests in an individual class are
          run.  ‘setUpClass’ is called with the class as the only
          argument and must be decorated as a *note classmethod(): 14a.:

               @classmethod
               def setUpClass(cls):
                   ...

          更多細節請見 *note Class and Module Fixtures: 3e99.。

          在 3.2 版被加入.

      -- 方法: tearDownClass ()

          A class method called after tests in an individual class have
          run.  ‘tearDownClass’ is called with the class as the only
          argument and must be decorated as a *note classmethod(): 14a.:

               @classmethod
               def tearDownClass(cls):
                   ...

          更多細節請見 *note Class and Module Fixtures: 3e99.。

          在 3.2 版被加入.

      -- 方法: run (result=None)

          Run the test, collecting the result into the *note TestResult:
          1100. object passed as 'result'.  If 'result' is omitted or
          ‘None’, a temporary result object is created (by calling the
          *note defaultTestResult(): 3e9a. method) and used.  The result
          object is returned to *note run(): 10ff.'s caller.

          The same effect may be had by simply calling the *note
          TestCase: 3f4. instance.

          在 3.3 版的變更: Previous versions of ‘run’ did not return the
          result.  Neither did calling an instance.

      -- 方法: skipTest (reason)

          Calling this during a test method or *note setUp(): 12cd.
          skips the current test.  See *note Skipping tests and expected
          failures: 3e8f. for more information.

          在 3.1 版被加入.

      -- 方法: subTest (msg=None, **params)

          Return a context manager which executes the enclosed code
          block as a subtest.  'msg' and 'params' are optional,
          arbitrary values which are displayed whenever a subtest fails,
          allowing you to identify them clearly.

          A test case can contain any number of subtest declarations,
          and they can be arbitrarily nested.

          更多資訊請見 *note Distinguishing test iterations using
          subtests: f85.。

          在 3.4 版被加入.

      -- 方法: debug ()

          Run the test without collecting the result.  This allows
          exceptions raised by the test to be propagated to the caller,
          and can be used to support running tests under a debugger.
     The *note TestCase: 3f4. class provides several assert methods to
     check for and report failures.  The following table lists the most
     commonly used methods (see the tables below for more assert
     methods):

     Method                                        Checks that                       New in
                                                                                     
     ----------------------------------------------------------------------------------------------------
                                                                                     
     *note assertEqual(a, b): 4cd.                 ‘a == b’
                                                   
                                                                                     
     *note assertNotEqual(a, b): 4ce.              ‘a != b’
                                                   
                                                                                     
     *note assertTrue(x): 4cb.                     ‘bool(x) is True’
                                                   
                                                                                     
     *note assertFalse(x): 4cc.                    ‘bool(x) is False’
                                                   
                                                                                     
     *note assertIs(a, b): 12cf.                   ‘a is b’                          3.1
                                                                                     
                                                                                     
     *note assertIsNot(a, b): 12d0.                ‘a is not b’                      3.1
                                                                                     
                                                                                     
     *note assertIsNone(x): 1222.                  ‘x is None’                       3.1
                                                                                     
                                                                                     
     *note assertIsNotNone(x): 1223.               ‘x is not None’                   3.1
                                                                                     
                                                                                     
     *note assertIn(a, b): 12d8.                   ‘a in b’                          3.1
                                                                                     
                                                                                     
     *note assertNotIn(a, b): 12d9.                ‘a not in b’                      3.1
                                                                                     
                                                                                     
     *note assertIsInstance(a, b): 12d1.           ‘isinstance(a, b)’                3.2
                                                                                     
                                                                                     
     *note assertNotIsInstance(a, b): 12d2.        ‘not isinstance(a, b)’            3.2
                                                                                     

     All the assert methods accept a 'msg' argument that, if specified,
     is used as the error message on failure (see also *note
     longMessage: 12ca.).  Note that the 'msg' keyword argument can be
     passed to *note assertRaises(): 4d1, *note assertRaisesRegex():
     4d3, *note assertWarns(): 10fd, *note assertWarnsRegex(): 10fe.
     only when they are used as a context manager.

      -- 方法: assertEqual (first, second, msg=None)

          Test that 'first' and 'second' are equal.  If the values do
          not compare equal, the test will fail.

          In addition, if 'first' and 'second' are the exact same type
          and one of list, tuple, dict, set, frozenset or str or any
          type that a subclass registers with *note
          addTypeEqualityFunc(): 12dc. the type-specific equality
          function will be called in order to generate a more useful
          default error message (see also the *note list of
          type-specific methods: 3e9b.).

          在 3.1 版的變更: Added the automatic calling of type-specific
          equality function.

          在 3.2 版的變更: *note assertMultiLineEqual(): 12d7. added as
          the default type equality function for comparing strings.

      -- 方法: assertNotEqual (first, second, msg=None)

          Test that 'first' and 'second' are not equal.  If the values
          do compare equal, the test will fail.

      -- 方法: assertTrue (expr, msg=None)
      -- 方法: assertFalse (expr, msg=None)

          Test that 'expr' is true (or false).

          Note that this is equivalent to ‘bool(expr) is True’ and not
          to ‘expr is True’ (use ‘assertIs(expr, True)’ for the latter).
          This method should also be avoided when more specific methods
          are available (e.g.  ‘assertEqual(a, b)’ instead of
          ‘assertTrue(a == b)’), because they provide a better error
          message in case of failure.

      -- 方法: assertIs (first, second, msg=None)
      -- 方法: assertIsNot (first, second, msg=None)

          Test that 'first' and 'second' are (or are not) the same
          object.

          在 3.1 版被加入.

      -- 方法: assertIsNone (expr, msg=None)
      -- 方法: assertIsNotNone (expr, msg=None)

          Test that 'expr' is (or is not) ‘None’.

          在 3.1 版被加入.

      -- 方法: assertIn (member, container, msg=None)
      -- 方法: assertNotIn (member, container, msg=None)

          Test that 'member' is (or is not) in 'container'.

          在 3.1 版被加入.

      -- 方法: assertIsInstance (obj, cls, msg=None)
      -- 方法: assertNotIsInstance (obj, cls, msg=None)

          Test that 'obj' is (or is not) an instance of 'cls' (which can
          be a class or a tuple of classes, as supported by *note
          isinstance(): 3e8.).  To check for the exact type, use *note
          assertIs(type(obj), cls): 12cf.

          在 3.2 版被加入.

     It is also possible to check the production of exceptions,
     warnings, and log messages using the following methods:

     Method                                                        Checks that                                New in
                                                                                                              
     --------------------------------------------------------------------------------------------------------------------------
                                                                                                              
     *note assertRaises(exc, fun, *args, **kwds): 4d1.             ‘fun(*args, **kwds)’ raises 'exc'
                                                                   
                                                                                                              
     *note assertRaisesRegex(exc, r, fun, *args, **kwds): 4d3.     ‘fun(*args, **kwds)’ raises 'exc' and      3.1
                                                                   the message matches regex 'r'              
                                                                   
                                                                                                              
     *note assertWarns(warn, fun, *args, **kwds): 10fd.            ‘fun(*args, **kwds)’ raises 'warn'         3.2
                                                                                                              
                                                                                                              
     *note assertWarnsRegex(warn, r, fun, *args, **kwds): 10fe.    ‘fun(*args, **kwds)’ raises 'warn' and     3.2
                                                                   the message matches regex 'r'              
                                                                   
                                                                                                              
     *note assertLogs(logger, level): 7fd.                         The ‘with’ block logs on 'logger' with     3.4
                                                                   minimum 'level'                            
                                                                   
                                                                                                              
     *note assertNoLogs(logger, level): 7fc.                       The ‘with’ block does not log on           3.10
                                                                                                              
                                                                        'logger' with minimum 'level'
                                                                   

      -- 方法: assertRaises (exception, callable, *args, **kwds)

      -- 方法: assertRaises (exception, *, msg=None)

          Test that an exception is raised when 'callable' is called
          with any positional or keyword arguments that are also passed
          to *note assertRaises(): 4d1.  The test passes if 'exception'
          is raised, is an error if another exception is raised, or
          fails if no exception is raised.  To catch any of a group of
          exceptions, a tuple containing the exception classes may be
          passed as 'exception'.

          If only the 'exception' and possibly the 'msg' arguments are
          given, return a context manager so that the code under test
          can be written inline rather than as a function:

               with self.assertRaises(SomeException):
                   do_something()

          When used as a context manager, *note assertRaises(): 4d1.
          accepts the additional keyword argument 'msg'.

          The context manager will store the caught exception object in
          its ‘exception’ attribute.  This can be useful if the
          intention is to perform additional checks on the exception
          raised:

               with self.assertRaises(SomeException) as cm:
                   do_something()

               the_exception = cm.exception
               self.assertEqual(the_exception.error_code, 3)

          在 3.1 版的變更: 新增 *note assertRaises(): 4d1. 可作為情境管
          理器使用的能力。

          在 3.2 版的變更: 新增 ‘exception’ 屬性。

          在 3.3 版的變更: 新增作為情境管理器使用時的 'msg' 引數。

      -- 方法: assertRaisesRegex (exception, regex, callable, *args,
               **kwds)

      -- 方法: assertRaisesRegex (exception, regex, *, msg=None)

          Like *note assertRaises(): 4d1. but also tests that 'regex'
          matches on the string representation of the raised exception.
          'regex' may be a regular expression object or a string
          containing a regular expression suitable for use by *note
          re.search(): 11c4.  Examples:

               self.assertRaisesRegex(ValueError, "invalid literal for.*XYZ'$",
                                      int, 'XYZ')

          或是：

               with self.assertRaisesRegex(ValueError, 'literal'):
                  int('XYZ')

          在 3.1 版被加入: 以 ‘assertRaisesRegexp’ 為名新增。

          在 3.2 版的變更: 重新命名為 *note assertRaisesRegex(): 4d3.。

          在 3.3 版的變更: 新增作為情境管理器使用時的 'msg' 引數。

      -- 方法: assertWarns (warning, callable, *args, **kwds)

      -- 方法: assertWarns (warning, *, msg=None)

          Test that a warning is triggered when 'callable' is called
          with any positional or keyword arguments that are also passed
          to *note assertWarns(): 10fd.  The test passes if 'warning' is
          triggered and fails if it isn't.  Any exception is an error.
          To catch any of a group of warnings, a tuple containing the
          warning classes may be passed as 'warnings'.

          If only the 'warning' and possibly the 'msg' arguments are
          given, return a context manager so that the code under test
          can be written inline rather than as a function:

               with self.assertWarns(SomeWarning):
                   do_something()

          When used as a context manager, *note assertWarns(): 10fd.
          accepts the additional keyword argument 'msg'.

          The context manager will store the caught warning object in
          its ‘warning’ attribute, and the source line which triggered
          the warnings in the ‘filename’ and ‘lineno’ attributes.  This
          can be useful if the intention is to perform additional checks
          on the warning caught:

               with self.assertWarns(SomeWarning) as cm:
                   do_something()

               self.assertIn('myfile.py', cm.filename)
               self.assertEqual(320, cm.lineno)

          This method works regardless of the warning filters in place
          when it is called.

          在 3.2 版被加入.

          在 3.3 版的變更: 新增作為情境管理器使用時的 'msg' 引數。

      -- 方法: assertWarnsRegex (warning, regex, callable, *args,
               **kwds)

      -- 方法: assertWarnsRegex (warning, regex, *, msg=None)

          Like *note assertWarns(): 10fd. but also tests that 'regex'
          matches on the message of the triggered warning.  'regex' may
          be a regular expression object or a string containing a
          regular expression suitable for use by *note re.search():
          11c4.  Example:

               self.assertWarnsRegex(DeprecationWarning,
                                     r'legacy_function\(\) is deprecated',
                                     legacy_function, 'XYZ')

          或是：

               with self.assertWarnsRegex(RuntimeWarning, 'unsafe frobnicating'):
                   frobnicate('/etc/passwd')

          在 3.2 版被加入.

          在 3.3 版的變更: 新增作為情境管理器使用時的 'msg' 引數。

      -- 方法: assertLogs (logger=None, level=None)

          A context manager to test that at least one message is logged
          on the 'logger' or one of its children, with at least the
          given 'level'.

          If given, 'logger' should be a *note logging.Logger: af3.
          object or a *note str: 3f2. giving the name of a logger.  The
          default is the root logger, which will catch all messages that
          were not blocked by a non-propagating descendent logger.

          If given, 'level' should be either a numeric logging level or
          its string equivalent (for example either ‘"ERROR"’ or *note
          logging.ERROR: 1bf8.).  The default is *note logging.INFO:
          1bf6.

          The test passes if at least one message emitted inside the
          ‘with’ block matches the 'logger' and 'level' conditions,
          otherwise it fails.

          The object returned by the context manager is a recording
          helper which keeps tracks of the matching log messages.  It
          has two attributes:

           -- 屬性: records

               A list of *note logging.LogRecord: f89. objects of the
               matching log messages.

           -- 屬性: output

               A list of *note str: 3f2. objects with the formatted
               output of matching messages.

          範例：

               with self.assertLogs('foo', level='INFO') as cm:
                   logging.getLogger('foo').info('first message')
                   logging.getLogger('foo.bar').error('second message')
               self.assertEqual(cm.output, ['INFO:foo:first message',
                                            'ERROR:foo.bar:second message'])

          在 3.4 版被加入.

      -- 方法: assertNoLogs (logger=None, level=None)

          A context manager to test that no messages are logged on the
          'logger' or one of its children, with at least the given
          'level'.

          If given, 'logger' should be a *note logging.Logger: af3.
          object or a *note str: 3f2. giving the name of a logger.  The
          default is the root logger, which will catch all messages.

          If given, 'level' should be either a numeric logging level or
          its string equivalent (for example either ‘"ERROR"’ or *note
          logging.ERROR: 1bf8.).  The default is *note logging.INFO:
          1bf6.

          Unlike *note assertLogs(): 7fd, nothing will be returned by
          the context manager.

          在 3.10 版被加入.

     There are also other methods used to perform more specific checks,
     such as:

     Method                                      Checks that                          New in
                                                                                      
     ----------------------------------------------------------------------------------------------------
                                                                                      
     *note assertAlmostEqual(a, b): 4cf.         ‘round(a-b, 7) == 0’
                                                 
                                                                                      
     *note assertNotAlmostEqual(a, b): 4d0.      ‘round(a-b, 7) != 0’
                                                 
                                                                                      
     *note assertGreater(a, b): 12d3.            ‘a > b’                              3.1
                                                                                      
                                                                                      
     *note assertGreaterEqual(a, b): 12d4.       ‘a >= b’                             3.1
                                                                                      
                                                                                      
     *note assertLess(a, b): 12d5.               ‘a < b’                              3.1
                                                                                      
                                                                                      
     *note assertLessEqual(a, b): 12d6.          ‘a <= b’                             3.1
                                                                                      
                                                                                      
     *note assertRegex(s, r): 4d2.               ‘r.search(s)’                        3.1
                                                                                      
                                                                                      
     *note assertNotRegex(s, r): 4d4.            ‘not r.search(s)’                    3.2
                                                                                      
                                                                                      
     *note assertCountEqual(a, b): 11c2.         'a' and 'b' have the same elements   3.2
                                                 in the same number, regardless of    
                                                 their order.
                                                 

      -- 方法: assertAlmostEqual (first, second, places=7, msg=None,
               delta=None)
      -- 方法: assertNotAlmostEqual (first, second, places=7, msg=None,
               delta=None)

          Test that 'first' and 'second' are approximately (or not
          approximately) equal by computing the difference, rounding to
          the given number of decimal 'places' (default 7), and
          comparing to zero.  Note that these methods round the values
          to the given number of 'decimal places' (i.e.  like the *note
          round(): 126d. function) and not 'significant digits'.

          If 'delta' is supplied instead of 'places' then the difference
          between 'first' and 'second' must be less or equal to (or
          greater than) 'delta'.

          Supplying both 'delta' and 'places' raises a *note TypeError:
          4dd.

          在 3.2 版的變更: *note assertAlmostEqual(): 4cf. automatically
          considers almost equal objects that compare equal.  *note
          assertNotAlmostEqual(): 4d0. automatically fails if the
          objects compare equal.  Added the 'delta' keyword argument.

      -- 方法: assertGreater (first, second, msg=None)
      -- 方法: assertGreaterEqual (first, second, msg=None)
      -- 方法: assertLess (first, second, msg=None)
      -- 方法: assertLessEqual (first, second, msg=None)

          Test that 'first' is respectively >, >=, < or <= than 'second'
          depending on the method name.  If not, the test will fail:

               >>> self.assertGreaterEqual(3, 4)
               AssertionError: "3" unexpectedly not greater than or equal to "4"

          在 3.1 版被加入.

      -- 方法: assertRegex (text, regex, msg=None)
      -- 方法: assertNotRegex (text, regex, msg=None)

          Test that a 'regex' search matches (or does not match) 'text'.
          In case of failure, the error message will include the pattern
          and the 'text' (or the pattern and the part of 'text' that
          unexpectedly matched).  'regex' may be a regular expression
          object or a string containing a regular expression suitable
          for use by *note re.search(): 11c4.

          在 3.1 版被加入: 以 ‘assertRegexpMatches’ 為名新增。

          在 3.2 版的變更: The method ‘assertRegexpMatches()’ has been
          renamed to *note assertRegex(): 4d2.

          在 3.2 版被加入: *note assertNotRegex(): 4d4.。

      -- 方法: assertCountEqual (first, second, msg=None)

          Test that sequence 'first' contains the same elements as
          'second', regardless of their order.  When they don't, an
          error message listing the differences between the sequences
          will be generated.

          Duplicate elements are 'not' ignored when comparing 'first'
          and 'second'.  It verifies whether each element has the same
          count in both sequences.  Equivalent to:
          ‘assertEqual(Counter(list(first)), Counter(list(second)))’ but
          works with sequences of unhashable objects as well.

          在 3.2 版被加入.

     The *note assertEqual(): 4cd. method dispatches the equality check
     for objects of the same type to different type-specific methods.
     These methods are already implemented for most of the built-in
     types, but it's also possible to register new methods using *note
     addTypeEqualityFunc(): 12dc.:

      -- 方法: addTypeEqualityFunc (typeobj, function)

          Registers a type-specific method called by *note
          assertEqual(): 4cd. to check if two objects of exactly the
          same 'typeobj' (not subclasses) compare equal.  'function'
          must take two positional arguments and a third msg=None
          keyword argument just as *note assertEqual(): 4cd. does.  It
          must raise *note self.failureException(msg): 3e9e. when
          inequality between the first two parameters is detected -
          possibly providing useful information and explaining the
          inequalities in details in the error message.

          在 3.1 版被加入.

     The list of type-specific methods automatically used by *note
     assertEqual(): 4cd. are summarized in the following table.  Note
     that it's usually not necessary to invoke these methods directly.

     Method                                        Used to compare                   New in
                                                                                     
     ---------------------------------------------------------------------------------------------------
                                                                                     
     *note assertMultiLineEqual(a, b): 12d7.       strings                           3.1
                                                                                     
                                                                                     
     *note assertSequenceEqual(a, b): 1221.        sequences                         3.1
                                                                                     
                                                                                     
     *note assertListEqual(a, b): 121f.            lists                             3.1
                                                                                     
                                                                                     
     *note assertTupleEqual(a, b): 1220.           tuples                            3.1
                                                                                     
                                                                                     
     *note assertSetEqual(a, b): 121d.             sets or frozensets                3.1
                                                                                     
                                                                                     
     *note assertDictEqual(a, b): 121e.            dicts                             3.1
                                                                                     

      -- 方法: assertMultiLineEqual (first, second, msg=None)

          Test that the multiline string 'first' is equal to the string
          'second'.  When not equal a diff of the two strings
          highlighting the differences will be included in the error
          message.  This method is used by default when comparing
          strings with *note assertEqual(): 4cd.

          在 3.1 版被加入.

      -- 方法: assertSequenceEqual (first, second, msg=None,
               seq_type=None)

          Tests that two sequences are equal.  If a 'seq_type' is
          supplied, both 'first' and 'second' must be instances of
          'seq_type' or a failure will be raised.  If the sequences are
          different an error message is constructed that shows the
          difference between the two.

          This method is not called directly by *note assertEqual():
          4cd, but it's used to implement *note assertListEqual(): 121f.
          and *note assertTupleEqual(): 1220.

          在 3.1 版被加入.

      -- 方法: assertListEqual (first, second, msg=None)
      -- 方法: assertTupleEqual (first, second, msg=None)

          Tests that two lists or tuples are equal.  If not, an error
          message is constructed that shows only the differences between
          the two.  An error is also raised if either of the parameters
          are of the wrong type.  These methods are used by default when
          comparing lists or tuples with *note assertEqual(): 4cd.

          在 3.1 版被加入.

      -- 方法: assertSetEqual (first, second, msg=None)

          Tests that two sets are equal.  If not, an error message is
          constructed that lists the differences between the sets.  This
          method is used by default when comparing sets or frozensets
          with *note assertEqual(): 4cd.

          Fails if either of 'first' or 'second' does not have a
          ‘set.difference()’ method.

          在 3.1 版被加入.

      -- 方法: assertDictEqual (first, second, msg=None)

          Test that two dictionaries are equal.  If not, an error
          message is constructed that shows the differences in the
          dictionaries.  This method will be used by default to compare
          dictionaries in calls to *note assertEqual(): 4cd.

          在 3.1 版被加入.

     Finally the *note TestCase: 3f4. provides the following methods and
     attributes:

      -- 方法: fail (msg=None)

          Signals a test failure unconditionally, with 'msg' or ‘None’
          for the error message.

      -- 屬性: failureException

          This class attribute gives the exception raised by the test
          method.  If a test framework needs to use a specialized
          exception, possibly to carry additional information, it must
          subclass this exception in order to "play fair" with the
          framework.  The initial value of this attribute is *note
          AssertionError: 64e.

      -- 屬性: longMessage

          This class attribute determines what happens when a custom
          failure message is passed as the msg argument to an assertXYY
          call that fails.  ‘True’ is the default value.  In this case,
          the custom message is appended to the end of the standard
          failure message.  When set to ‘False’, the custom message
          replaces the standard message.

          The class setting can be overridden in individual test methods
          by assigning an instance attribute, self.longMessage, to
          ‘True’ or ‘False’ before calling the assert methods.

          The class setting gets reset before each test call.

          在 3.1 版被加入.

      -- 屬性: maxDiff

          This attribute controls the maximum length of diffs output by
          assert methods that report diffs on failure.  It defaults to
          80*8 characters.  Assert methods affected by this attribute
          are *note assertSequenceEqual(): 1221. (including all the
          sequence comparison methods that delegate to it), *note
          assertDictEqual(): 121e. and *note assertMultiLineEqual():
          12d7.

          Setting ‘maxDiff’ to ‘None’ means that there is no maximum
          length of diffs.

          在 3.2 版被加入.

     Testing frameworks can use the following methods to collect
     information on the test:

      -- 方法: countTestCases ()

          Return the number of tests represented by this test object.
          For *note TestCase: 3f4. instances, this will always be ‘1’.

      -- 方法: defaultTestResult ()

          Return an instance of the test result class that should be
          used for this test case class (if no other result instance is
          provided to the *note run(): 10ff. method).

          For *note TestCase: 3f4. instances, this will always be an
          instance of *note TestResult: 1100.; subclasses of *note
          TestCase: 3f4. should override this as necessary.

      -- 方法: id ()

          Return a string identifying the specific test case.  This is
          usually the full name of the test method, including the module
          and class name.

      -- 方法: shortDescription ()

          Returns a description of the test, or ‘None’ if no description
          has been provided.  The default implementation of this method
          returns the first line of the test method's docstring, if
          available, or ‘None’.

          在 3.1 版的變更: In 3.1 this was changed to add the test name
          to the short description even in the presence of a docstring.
          This caused compatibility issues with unittest extensions and
          adding the test name was moved to the *note TextTestResult:
          4d5. in Python 3.2.

      -- 方法: addCleanup (function, /, *args, **kwargs)

          Add a function to be called after *note tearDown(): 12ce. to
          cleanup resources used during the test.  Functions will be
          called in reverse order to the order they are added (LIFO).
          They are called with any arguments and keyword arguments
          passed into *note addCleanup(): a24. when they are added.

          If *note setUp(): 12cd. fails, meaning that *note tearDown():
          12ce. is not called, then any cleanup functions added will
          still be called.

          在 3.1 版被加入.

      -- 方法: enterContext (cm)

          Enter the supplied *note context manager: 576.  If successful,
          also add its *note __exit__(): 1293. method as a cleanup
          function by *note addCleanup(): a24. and return the result of
          the *note __enter__(): 56c. method.

          在 3.11 版被加入.

      -- 方法: doCleanups ()

          This method is called unconditionally after *note tearDown():
          12ce, or after *note setUp(): 12cd. if *note setUp(): 12cd.
          raises an exception.

          It is responsible for calling all the cleanup functions added
          by *note addCleanup(): a24.  If you need cleanup functions to
          be called 'prior' to *note tearDown(): 12ce. then you can call
          *note doCleanups(): 12cc. yourself.

          *note doCleanups(): 12cc. pops methods off the stack of
          cleanup functions one at a time, so it can be called at any
          time.

          在 3.1 版被加入.

      -- 方法: classmethod addClassCleanup (function, /, *args,
               **kwargs)

          Add a function to be called after *note tearDownClass(): 12cb.
          to cleanup resources used during the test class.  Functions
          will be called in reverse order to the order they are added
          (LIFO).  They are called with any arguments and keyword
          arguments passed into *note addClassCleanup(): 9f1. when they
          are added.

          If *note setUpClass(): 9f2. fails, meaning that *note
          tearDownClass(): 12cb. is not called, then any cleanup
          functions added will still be called.

          在 3.8 版被加入.

      -- 方法: classmethod enterClassContext (cm)

          Enter the supplied *note context manager: 576.  If successful,
          also add its *note __exit__(): 1293. method as a cleanup
          function by *note addClassCleanup(): 9f1. and return the
          result of the *note __enter__(): 56c. method.

          在 3.11 版被加入.

      -- 方法: classmethod doClassCleanups ()

          This method is called unconditionally after *note
          tearDownClass(): 12cb, or after *note setUpClass(): 9f2. if
          *note setUpClass(): 9f2. raises an exception.

          It is responsible for calling all the cleanup functions added
          by *note addClassCleanup(): 9f1.  If you need cleanup
          functions to be called 'prior' to *note tearDownClass(): 12cb.
          then you can call *note doClassCleanups(): 3ea4. yourself.

          *note doClassCleanups(): 3ea4. pops methods off the stack of
          cleanup functions one at a time, so it can be called at any
          time.

          在 3.8 版被加入.

 -- 類別: unittest.IsolatedAsyncioTestCase (methodName='runTest')

     This class provides an API similar to *note TestCase: 3f4. and also
     accepts coroutines as test functions.

     在 3.8 版被加入.

      -- 屬性: loop_factory

          The 'loop_factory' passed to *note asyncio.Runner: 5a5.
          Override in subclasses with *note asyncio.EventLoop: 15f1. to
          avoid using the asyncio policy system.

          在 3.13 版被加入.

      -- 方法: coroutine asyncSetUp ()

          Method called to prepare the test fixture.  This is called
          after ‘setUp()’.  This is called immediately before calling
          the test method; other than *note AssertionError: 64e. or
          *note SkipTest: f87, any exception raised by this method will
          be considered an error rather than a test failure.  The
          default implementation does nothing.

      -- 方法: coroutine asyncTearDown ()

          Method called immediately after the test method has been
          called and the result recorded.  This is called before
          ‘tearDown()’.  This is called even if the test method raised
          an exception, so the implementation in subclasses may need to
          be particularly careful about checking internal state.  Any
          exception, other than *note AssertionError: 64e. or *note
          SkipTest: f87, raised by this method will be considered an
          additional error rather than a test failure (thus increasing
          the total number of reported errors).  This method will only
          be called if the *note asyncSetUp(): 3ea6. succeeds,
          regardless of the outcome of the test method.  The default
          implementation does nothing.

      -- 方法: addAsyncCleanup (function, /, *args, **kwargs)

          This method accepts a coroutine that can be used as a cleanup
          function.

      -- 方法: coroutine enterAsyncContext (cm)

          Enter the supplied *note asynchronous context manager: 579.
          If successful, also add its *note __aexit__(): 151e. method as
          a cleanup function by *note addAsyncCleanup(): 3ea8. and
          return the result of the *note __aenter__(): 1ea6. method.

          在 3.11 版被加入.

      -- 方法: run (result=None)

          Sets up a new event loop to run the test, collecting the
          result into the *note TestResult: 1100. object passed as
          'result'.  If 'result' is omitted or ‘None’, a temporary
          result object is created (by calling the ‘defaultTestResult()’
          method) and used.  The result object is returned to *note
          run(): 3ea9.'s caller.  At the end of the test all the tasks
          in the event loop are cancelled.

     An example illustrating the order:

          from unittest import IsolatedAsyncioTestCase

          events = []


          class Test(IsolatedAsyncioTestCase):


              def setUp(self):
                  events.append("setUp")

              async def asyncSetUp(self):
                  self._async_connection = await AsyncConnection()
                  events.append("asyncSetUp")

              async def test_response(self):
                  events.append("test_response")
                  response = await self._async_connection.get("https://example.com")
                  self.assertEqual(response.status_code, 200)
                  self.addAsyncCleanup(self.on_cleanup)

              def tearDown(self):
                  events.append("tearDown")

              async def asyncTearDown(self):
                  await self._async_connection.close()
                  events.append("asyncTearDown")

              async def on_cleanup(self):
                  events.append("cleanup")

          if __name__ == "__main__":
              unittest.main()

     After running the test, ‘events’ would contain ‘["setUp",
     "asyncSetUp", "test_response", "asyncTearDown", "tearDown",
     "cleanup"]’.

 -- 類別: unittest.FunctionTestCase (testFunc, setUp=None,
          tearDown=None, description=None)

     This class implements the portion of the *note TestCase: 3f4.
     interface which allows the test runner to drive the test, but does
     not provide the methods which test code can use to check and report
     errors.  This is used to create test cases using legacy test code,
     allowing it to be integrated into a *note unittest: ef.-based test
     framework.


File: python.info,  Node: Grouping tests,  Next: Loading and running tests,  Prev: Test cases,  Up: Classes and functions

5.26.5.11 Grouping tests
........................

 -- 類別: unittest.TestSuite (tests=())

     This class represents an aggregation of individual test cases and
     test suites.  The class presents the interface needed by the test
     runner to allow it to be run as any other test case.  Running a
     *note TestSuite: d9a. instance is the same as iterating over the
     suite, running each test individually.

     If 'tests' is given, it must be an iterable of individual test
     cases or other test suites that will be used to build the suite
     initially.  Additional methods are provided to add test cases and
     suites to the collection later on.

     *note TestSuite: d9a. objects behave much like *note TestCase: 3f4.
     objects, except they do not actually implement a test.  Instead,
     they are used to aggregate tests into groups of tests that should
     be run together.  Some additional methods are available to add
     tests to *note TestSuite: d9a. instances:

      -- 方法: addTest (test)

          Add a *note TestCase: 3f4. or *note TestSuite: d9a. to the
          suite.

      -- 方法: addTests (tests)

          Add all the tests from an iterable of *note TestCase: 3f4. and
          *note TestSuite: d9a. instances to this test suite.

          This is equivalent to iterating over 'tests', calling *note
          addTest(): 3eac. for each element.

     *note TestSuite: d9a. shares the following methods with *note
     TestCase: 3f4.:

      -- 方法: run (result)

          Run the tests associated with this suite, collecting the
          result into the test result object passed as 'result'.  Note
          that unlike *note TestCase.run(): 10ff, *note TestSuite.run():
          3eae. requires the result object to be passed in.

      -- 方法: debug ()

          Run the tests associated with this suite without collecting
          the result.  This allows exceptions raised by the test to be
          propagated to the caller and can be used to support running
          tests under a debugger.

      -- 方法: countTestCases ()

          Return the number of tests represented by this test object,
          including all individual tests and sub-suites.

      -- 方法: __iter__ ()

          Tests grouped by a *note TestSuite: d9a. are always accessed
          by iteration.  Subclasses can lazily provide tests by
          overriding ‘__iter__()’.  Note that this method may be called
          several times on a single suite (for example when counting
          tests or comparing for equality) so the tests returned by
          repeated iterations before *note TestSuite.run(): 3eae. must
          be the same for each call iteration.  After *note
          TestSuite.run(): 3eae, callers should not rely on the tests
          returned by this method unless the caller uses a subclass that
          overrides ‘TestSuite._removeTestAtIndex()’ to preserve test
          references.

          在 3.2 版的變更: In earlier versions the *note TestSuite: d9a.
          accessed tests directly rather than through iteration, so
          overriding ‘__iter__()’ wasn't sufficient for providing tests.

          在 3.4 版的變更: In earlier versions the *note TestSuite: d9a.
          held references to each *note TestCase: 3f4. after *note
          TestSuite.run(): 3eae.  Subclasses can restore that behavior
          by overriding ‘TestSuite._removeTestAtIndex()’.

     In the typical usage of a *note TestSuite: d9a. object, the *note
     run(): 3eae. method is invoked by a ‘TestRunner’ rather than by the
     end-user test harness.


File: python.info,  Node: Loading and running tests,  Prev: Grouping tests,  Up: Classes and functions

5.26.5.12 Loading and running tests
...................................

 -- 類別: unittest.TestLoader

     The *note TestLoader: 270. class is used to create test suites from
     classes and modules.  Normally, there is no need to create an
     instance of this class; the *note unittest: ef. module provides an
     instance that can be shared as *note unittest.defaultTestLoader:
     3eb2.  Using a subclass or instance, however, allows customization
     of some configurable properties.

     *note TestLoader: 270. objects have the following attributes:

      -- 屬性: errors

          A list of the non-fatal errors encountered while loading
          tests.  Not reset by the loader at any point.  Fatal errors
          are signalled by the relevant method raising an exception to
          the caller.  Non-fatal errors are also indicated by a
          synthetic test that will raise the original error when run.

          在 3.5 版被加入.

     *note TestLoader: 270. objects have the following methods:

      -- 方法: loadTestsFromTestCase (testCaseClass)

          Return a suite of all test cases contained in the *note
          TestCase: 3f4.-derived ‘testCaseClass’.

          A test case instance is created for each method named by *note
          getTestCaseNames(): 273.  By default these are the method
          names beginning with ‘test’.  If *note getTestCaseNames():
          273. returns no methods, but the ‘runTest()’ method is
          implemented, a single test case is created for that method
          instead.

      -- 方法: loadTestsFromModule (module, *, pattern=None)

          Return a suite of all test cases contained in the given
          module.  This method searches 'module' for classes derived
          from *note TestCase: 3f4. and creates an instance of the class
          for each test method defined for the class.

               備註: While using a hierarchy of *note TestCase:
               3f4.-derived classes can be convenient in sharing
               fixtures and helper functions, defining test methods on
               base classes that are not intended to be instantiated
               directly does not play well with this method.  Doing so,
               however, can be useful when the fixtures are different
               and defined in subclasses.

          If a module provides a ‘load_tests’ function it will be called
          to load the tests.  This allows modules to customize test
          loading.  This is the *note load_tests protocol: 3e8a.  The
          'pattern' argument is passed as the third argument to
          ‘load_tests’.

          在 3.2 版的變更: Support for ‘load_tests’ added.

          在 3.5 版的變更: Support for a keyword-only argument 'pattern'
          has been added.

          在 3.12 版的變更: The undocumented and unofficial
          'use_load_tests' parameter has been removed.

      -- 方法: loadTestsFromName (name, module=None)

          Return a suite of all test cases given a string specifier.

          The specifier 'name' is a "dotted name" that may resolve
          either to a module, a test case class, a test method within a
          test case class, a *note TestSuite: d9a. instance, or a
          callable object which returns a *note TestCase: 3f4. or *note
          TestSuite: d9a. instance.  These checks are applied in the
          order listed here; that is, a method on a possible test case
          class will be picked up as "a test method within a test case
          class", rather than "a callable object".

          For example, if you have a module ‘SampleTests’ containing a
          *note TestCase: 3f4.-derived class ‘SampleTestCase’ with three
          test methods (‘test_one()’, ‘test_two()’, and ‘test_three()’),
          the specifier ‘'SampleTests.SampleTestCase'’ would cause this
          method to return a suite which will run all three test
          methods.  Using the specifier
          ‘'SampleTests.SampleTestCase.test_two'’ would cause it to
          return a test suite which will run only the ‘test_two()’ test
          method.  The specifier can refer to modules and packages which
          have not been imported; they will be imported as a
          side-effect.

          The method optionally resolves 'name' relative to the given
          'module'.

          在 3.5 版的變更: If an *note ImportError: 352. or *note
          AttributeError: 2f6. occurs while traversing 'name' then a
          synthetic test that raises that error when run will be
          returned.  These errors are included in the errors accumulated
          by self.errors.

      -- 方法: loadTestsFromNames (names, module=None)

          Similar to *note loadTestsFromName(): 12da, but takes a
          sequence of names rather than a single name.  The return value
          is a test suite which supports all the tests defined for each
          name.

      -- 方法: getTestCaseNames (testCaseClass)

          Return a sorted sequence of method names found within
          'testCaseClass'; this should be a subclass of *note TestCase:
          3f4.

      -- 方法: discover (start_dir, pattern='test*.py',
               top_level_dir=None)

          Find all the test modules by recursing into subdirectories
          from the specified start directory, and return a TestSuite
          object containing them.  Only test files that match 'pattern'
          will be loaded.  (Using shell style pattern matching.)  Only
          module names that are importable (i.e.  are valid Python
          identifiers) will be loaded.

          All test modules must be importable from the top level of the
          project.  If the start directory is not the top level
          directory then 'top_level_dir' must be specified separately.

          If importing a module fails, for example due to a syntax
          error, then this will be recorded as a single error and
          discovery will continue.  If the import failure is due to
          *note SkipTest: f87. being raised, it will be recorded as a
          skip instead of an error.

          If a package (a directory containing a file named
          ‘__init__.py’) is found, the package will be checked for a
          ‘load_tests’ function.  If this exists then it will be called
          ‘package.load_tests(loader, tests, pattern)’.  Test discovery
          takes care to ensure that a package is only checked for tests
          once during an invocation, even if the load_tests function
          itself calls ‘loader.discover’.

          If ‘load_tests’ exists then discovery does 'not' recurse into
          the package, ‘load_tests’ is responsible for loading all tests
          in the package.

          The pattern is deliberately not stored as a loader attribute
          so that packages can continue discovery themselves.

          'top_level_dir' is stored internally, and used as a default to
          any nested calls to ‘discover()’.  That is, if a package's
          ‘load_tests’ calls ‘loader.discover()’, it does not need to
          pass this argument.

          'start_dir' can be a dotted module name as well as a
          directory.

          在 3.2 版被加入.

          在 3.4 版的變更: Modules that raise *note SkipTest: f87. on
          import are recorded as skips, not errors.

          在 3.4 版的變更: 'start_dir' can be a *note namespace
          packages: 1b6c.

          在 3.4 版的變更: Paths are sorted before being imported so
          that execution order is the same even if the underlying file
          system's ordering is not dependent on file name.

          在 3.5 版的變更: Found packages are now checked for
          ‘load_tests’ regardless of whether their path matches
          'pattern', because it is impossible for a package name to
          match the default pattern.

          在 3.11 版的變更: 'start_dir' can not be a *note namespace
          packages: 1b6c.  It has been broken since Python 3.7 and
          Python 3.11 officially remove it.

          在 3.13 版的變更: 'top_level_dir' is only stored for the
          duration of 'discover' call.

     The following attributes of a *note TestLoader: 270. can be
     configured either by subclassing or assignment on an instance:

      -- 屬性: testMethodPrefix

          String giving the prefix of method names which will be
          interpreted as test methods.  The default value is ‘'test'’.

          This affects *note getTestCaseNames(): 273. and all the
          ‘loadTestsFrom*’ methods.

      -- 屬性: sortTestMethodsUsing

          Function to be used to compare method names when sorting them
          in *note getTestCaseNames(): 273. and all the ‘loadTestsFrom*’
          methods.

      -- 屬性: suiteClass

          Callable object that constructs a test suite from a list of
          tests.  No methods on the resulting object are needed.  The
          default value is the *note TestSuite: d9a. class.

          This affects all the ‘loadTestsFrom*’ methods.

      -- 屬性: testNamePatterns

          List of Unix shell-style wildcard test name patterns that test
          methods have to match to be included in test suites (see ‘-k’
          option).

          If this attribute is not ‘None’ (the default), all test
          methods to be included in test suites must match one of the
          patterns in this list.  Note that matches are always performed
          using *note fnmatch.fnmatchcase(): 17a3, so unlike patterns
          passed to the ‘-k’ option, simple substring patterns will have
          to be converted using ‘*’ wildcards.

          This affects all the ‘loadTestsFrom*’ methods.

          在 3.7 版被加入.

 -- 類別: unittest.TestResult

     This class is used to compile information about which tests have
     succeeded and which have failed.

     A *note TestResult: 1100. object stores the results of a set of
     tests.  The *note TestCase: 3f4. and *note TestSuite: d9a. classes
     ensure that results are properly recorded; test authors do not need
     to worry about recording the outcome of tests.

     Testing frameworks built on top of *note unittest: ef. may want
     access to the *note TestResult: 1100. object generated by running a
     set of tests for reporting purposes; a *note TestResult: 1100.
     instance is returned by the ‘TestRunner.run()’ method for this
     purpose.

     *note TestResult: 1100. instances have the following attributes
     that will be of interest when inspecting the results of running a
     set of tests:

      -- 屬性: errors

          A list containing 2-tuples of *note TestCase: 3f4. instances
          and strings holding formatted tracebacks.  Each tuple
          represents a test which raised an unexpected exception.

      -- 屬性: failures

          A list containing 2-tuples of *note TestCase: 3f4. instances
          and strings holding formatted tracebacks.  Each tuple
          represents a test where a failure was explicitly signalled
          using the *note assert* methods: 3e72.

      -- 屬性: skipped

          A list containing 2-tuples of *note TestCase: 3f4. instances
          and strings holding the reason for skipping the test.

          在 3.1 版被加入.

      -- 屬性: expectedFailures

          A list containing 2-tuples of *note TestCase: 3f4. instances
          and strings holding formatted tracebacks.  Each tuple
          represents an expected failure or error of the test case.

      -- 屬性: unexpectedSuccesses

          A list containing *note TestCase: 3f4. instances that were
          marked as expected failures, but succeeded.

      -- 屬性: collectedDurations

          A list containing 2-tuples of test case names and floats
          representing the elapsed time of each test which was run.

          在 3.12 版被加入.

      -- 屬性: shouldStop

          Set to ‘True’ when the execution of tests should stop by *note
          stop(): 3ebd.

      -- 屬性: testsRun

          The total number of tests run so far.

      -- 屬性: buffer

          If set to true, ‘sys.stdout’ and ‘sys.stderr’ will be buffered
          in between *note startTest(): 3ec0. and *note stopTest():
          3ec1. being called.  Collected output will only be echoed onto
          the real ‘sys.stdout’ and ‘sys.stderr’ if the test fails or
          errors.  Any output is also attached to the failure / error
          message.

          在 3.2 版被加入.

      -- 屬性: failfast

          If set to true *note stop(): 3ebd. will be called on the first
          failure or error, halting the test run.

          在 3.2 版被加入.

      -- 屬性: tb_locals

          If set to true then local variables will be shown in
          tracebacks.

          在 3.5 版被加入.

      -- 方法: wasSuccessful ()

          Return ‘True’ if all tests run so far have passed, otherwise
          returns ‘False’.

          在 3.4 版的變更: Returns ‘False’ if there were any *note
          unexpectedSuccesses: 3ebb. from tests marked with the *note
          expectedFailure(): 3e91. decorator.

      -- 方法: stop ()

          This method can be called to signal that the set of tests
          being run should be aborted by setting the *note shouldStop:
          3ebc. attribute to ‘True’.  ‘TestRunner’ objects should
          respect this flag and return without running any additional
          tests.

          For example, this feature is used by the *note TextTestRunner:
          1644. class to stop the test framework when the user signals
          an interrupt from the keyboard.  Interactive tools which
          provide ‘TestRunner’ implementations can use this in a similar
          manner.

     The following methods of the *note TestResult: 1100. class are used
     to maintain the internal data structures, and may be extended in
     subclasses to support additional reporting requirements.  This is
     particularly useful in building tools which support interactive
     reporting while tests are being run.

      -- 方法: startTest (test)

          Called when the test case 'test' is about to be run.

      -- 方法: stopTest (test)

          Called after the test case 'test' has been executed,
          regardless of the outcome.

      -- 方法: startTestRun ()

          Called once before any tests are executed.

          在 3.1 版被加入.

      -- 方法: stopTestRun ()

          Called once after all tests are executed.

          在 3.1 版被加入.

      -- 方法: addError (test, err)

          Called when the test case 'test' raises an unexpected
          exception.  'err' is a tuple of the form returned by *note
          sys.exc_info(): 630.: ‘(type, value, traceback)’.

          The default implementation appends a tuple ‘(test,
          formatted_err)’ to the instance's *note errors: 3eb7.
          attribute, where 'formatted_err' is a formatted traceback
          derived from 'err'.

      -- 方法: addFailure (test, err)

          Called when the test case 'test' signals a failure.  'err' is
          a tuple of the form returned by *note sys.exc_info(): 630.:
          ‘(type, value, traceback)’.

          The default implementation appends a tuple ‘(test,
          formatted_err)’ to the instance's *note failures: 3eb8.
          attribute, where 'formatted_err' is a formatted traceback
          derived from 'err'.

      -- 方法: addSuccess (test)

          Called when the test case 'test' succeeds.

          The default implementation does nothing.

      -- 方法: addSkip (test, reason)

          Called when the test case 'test' is skipped.  'reason' is the
          reason the test gave for skipping.

          The default implementation appends a tuple ‘(test, reason)’ to
          the instance's *note skipped: 3eb9. attribute.

      -- 方法: addExpectedFailure (test, err)

          Called when the test case 'test' fails or errors, but was
          marked with the *note expectedFailure(): 3e91. decorator.

          The default implementation appends a tuple ‘(test,
          formatted_err)’ to the instance's *note expectedFailures:
          3eba. attribute, where 'formatted_err' is a formatted
          traceback derived from 'err'.

      -- 方法: addUnexpectedSuccess (test)

          Called when the test case 'test' was marked with the *note
          expectedFailure(): 3e91. decorator, but succeeded.

          The default implementation appends the test to the instance's
          *note unexpectedSuccesses: 3ebb. attribute.

      -- 方法: addSubTest (test, subtest, outcome)

          Called when a subtest finishes.  'test' is the test case
          corresponding to the test method.  'subtest' is a custom *note
          TestCase: 3f4. instance describing the subtest.

          If 'outcome' is *note None: 61b, the subtest succeeded.
          Otherwise, it failed with an exception where 'outcome' is a
          tuple of the form returned by *note sys.exc_info(): 630.:
          ‘(type, value, traceback)’.

          The default implementation does nothing when the outcome is a
          success, and records subtest failures as normal failures.

          在 3.4 版被加入.

      -- 方法: addDuration (test, elapsed)

          Called when the test case finishes.  'elapsed' is the time
          represented in seconds, and it includes the execution of
          cleanup functions.

          在 3.12 版被加入.

 -- 類別: unittest.TextTestResult (stream, descriptions, verbosity, *,
          durations=None)

     A concrete implementation of *note TestResult: 1100. used by the
     *note TextTestRunner: 1644.  Subclasses should accept ‘**kwargs’ to
     ensure compatibility as the interface changes.

     在 3.2 版被加入.

     在 3.12 版的變更: 新增 'durations' 關鍵字參數。

 -- 資料: unittest.defaultTestLoader

     Instance of the *note TestLoader: 270. class intended to be shared.
     If no customization of the *note TestLoader: 270. is needed, this
     instance can be used instead of repeatedly creating new instances.

 -- 類別: unittest.TextTestRunner (stream=None, descriptions=True,
          verbosity=1, failfast=False, buffer=False, resultclass=None,
          warnings=None, *, tb_locals=False, durations=None)

     A basic test runner implementation that outputs results to a
     stream.  If 'stream' is ‘None’, the default, *note sys.stderr: 8dd.
     is used as the output stream.  This class has a few configurable
     parameters, but is essentially very simple.  Graphical applications
     which run test suites should provide alternate implementations.
     Such implementations should accept ‘**kwargs’ as the interface to
     construct runners changes when features are added to unittest.

     By default this runner shows *note DeprecationWarning: 18b, *note
     PendingDeprecationWarning: 86d, *note ResourceWarning: 229. and
     *note ImportWarning: 4a2. even if they are *note ignored by
     default: 3ec8.  This behavior can be overridden using Python's
     ‘-Wd’ or ‘-Wa’ options (see *note Warning control: 1c3a.) and
     leaving 'warnings' to ‘None’.

     在 3.2 版的變更: 新增 'warnings' 參數。

     在 3.2 版的變更: The default stream is set to *note sys.stderr:
     8dd. at instantiation time rather than import time.

     在 3.5 版的變更: 新增 'tb_locals' 參數。

     在 3.12 版的變更: 新增 'durations' 參數。

      -- 方法: _makeResult ()

          This method returns the instance of ‘TestResult’ used by *note
          run(): 3eca.  It is not intended to be called directly, but
          can be overridden in subclasses to provide a custom
          ‘TestResult’.

          ‘_makeResult()’ instantiates the class or callable passed in
          the ‘TextTestRunner’ constructor as the ‘resultclass’
          argument.  It defaults to *note TextTestResult: 4d5. if no
          ‘resultclass’ is provided.  The result class is instantiated
          with the following arguments:

               stream, descriptions, verbosity

      -- 方法: run (test)

          This method is the main public interface to the
          ‘TextTestRunner’.  This method takes a *note TestSuite: d9a.
          or *note TestCase: 3f4. instance.  A *note TestResult: 1100.
          is created by calling *note _makeResult(): 3ec9. and the
          test(s) are run and the results printed to stdout.

 -- 函式: unittest.main (module='__main__', defaultTest=None, argv=None,
          testRunner=None, testLoader=unittest.defaultTestLoader,
          exit=True, verbosity=1, failfast=None, catchbreak=None,
          buffer=None, warnings=None)

     A command-line program that loads a set of tests from 'module' and
     runs them; this is primarily for making test modules conveniently
     executable.  The simplest use for this function is to include the
     following line at the end of a test script:

          if __name__ == '__main__':
              unittest.main()

     You can run tests with more detailed information by passing in the
     verbosity argument:

          if __name__ == '__main__':
              unittest.main(verbosity=2)

     The 'defaultTest' argument is either the name of a single test or
     an iterable of test names to run if no test names are specified via
     'argv'.  If not specified or ‘None’ and no test names are provided
     via 'argv', all tests found in 'module' are run.

     The 'argv' argument can be a list of options passed to the program,
     with the first element being the program name.  If not specified or
     ‘None’, the values of *note sys.argv: 11fd. are used.

     The 'testRunner' argument can either be a test runner class or an
     already created instance of it.  By default ‘main’ calls *note
     sys.exit(): 12dd. with an exit code indicating success (0) or
     failure (1) of the tests run.  An exit code of 5 indicates that no
     tests were run or skipped.

     The 'testLoader' argument has to be a *note TestLoader: 270.
     instance, and defaults to *note defaultTestLoader: 3eb2.

     ‘main’ supports being used from the interactive interpreter by
     passing in the argument ‘exit=False’.  This displays the result on
     standard output without calling *note sys.exit(): 12dd.:

          >>> from unittest import main
          >>> main(module='test_module', exit=False)

     The 'failfast', 'catchbreak' and 'buffer' parameters have the same
     effect as the same-name *note command-line options: 3e79.

     The 'warnings' argument specifies the *note warning filter: 86e.
     that should be used while running the tests.  If it's not
     specified, it will remain ‘None’ if a ‘-W’ option is passed to
     ‘python’ (see *note Warning control: 1c3a.), otherwise it will be
     set to ‘'default'’.

     Calling ‘main’ returns an object with the ‘result’ attribute that
     contains the result of the tests run as a *note
     unittest.TestResult: 1100.

     在 3.1 版的變更: 新增 'exit' 參數。

     在 3.2 版的變更: The 'verbosity', 'failfast', 'catchbreak',
     'buffer' and 'warnings' parameters were added.

     在 3.4 版的變更: The 'defaultTest' parameter was changed to also
     accept an iterable of test names.

* Menu:

* load_tests Protocol::


File: python.info,  Node: load_tests Protocol,  Up: Loading and running tests

5.26.5.13 load_tests Protocol
.............................

在 3.2 版被加入.

Modules or packages can customize how tests are loaded from them during
normal test runs or test discovery by implementing a function called
‘load_tests’.

If a test module defines ‘load_tests’ it will be called by *note
TestLoader.loadTestsFromModule(): 271. with the following arguments:

     load_tests(loader, standard_tests, pattern)

where 'pattern' is passed straight through from ‘loadTestsFromModule’.
It defaults to ‘None’.

It should return a *note TestSuite: d9a.

'loader' is the instance of *note TestLoader: 270. doing the loading.
'standard_tests' are the tests that would be loaded by default from the
module.  It is common for test modules to only want to add or remove
tests from the standard set of tests.  The third argument is used when
loading packages as part of test discovery.

A typical ‘load_tests’ function that loads tests from a specific set of
*note TestCase: 3f4. classes may look like:

     test_cases = (TestCase1, TestCase2, TestCase3)

     def load_tests(loader, tests, pattern):
         suite = TestSuite()
         for test_class in test_cases:
             tests = loader.loadTestsFromTestCase(test_class)
             suite.addTests(tests)
         return suite

If discovery is started in a directory containing a package, either from
the command line or by calling *note TestLoader.discover(): f88, then
the package ‘__init__.py’ will be checked for ‘load_tests’.  If that
function does not exist, discovery will recurse into the package as
though it were just another directory.  Otherwise, discovery of the
package's tests will be left up to ‘load_tests’ which is called with the
following arguments:

     load_tests(loader, standard_tests, pattern)

This should return a *note TestSuite: d9a. representing all the tests
from the package.  (‘standard_tests’ will only contain tests collected
from ‘__init__.py’.)

Because the pattern is passed into ‘load_tests’ the package is free to
continue (and potentially modify) test discovery.  A 'do nothing'
‘load_tests’ function for a test package would look like:

     def load_tests(loader, standard_tests, pattern):
         # top level directory cached on loader instance
         this_dir = os.path.dirname(__file__)
         package_tests = loader.discover(start_dir=this_dir, pattern=pattern)
         standard_tests.addTests(package_tests)
         return standard_tests

在 3.5 版的變更: Discovery no longer checks package names for matching
'pattern' due to the impossibility of package names matching the default
pattern.


File: python.info,  Node: Class and Module Fixtures,  Next: Signal Handling,  Prev: Classes and functions,  Up: unittest --- 單元測試框架

5.26.5.14 Class and Module Fixtures
...................................

Class and module level fixtures are implemented in *note TestSuite: d9a.
When the test suite encounters a test from a new class then
‘tearDownClass()’ from the previous class (if there is one) is called,
followed by ‘setUpClass()’ from the new class.

Similarly if a test is from a different module from the previous test
then ‘tearDownModule’ from the previous module is run, followed by
‘setUpModule’ from the new module.

After all the tests have run the final ‘tearDownClass’ and
‘tearDownModule’ are run.

Note that shared fixtures do not play well with [potential] features
like test parallelization and they break test isolation.  They should be
used with care.

The default ordering of tests created by the unittest test loaders is to
group all tests from the same modules and classes together.  This will
lead to ‘setUpClass’ / ‘setUpModule’ (etc) being called exactly once per
class and module.  If you randomize the order, so that tests from
different modules and classes are adjacent to each other, then these
shared fixture functions may be called multiple times in a single test
run.

Shared fixtures are not intended to work with suites with non-standard
ordering.  A ‘BaseTestSuite’ still exists for frameworks that don't want
to support shared fixtures.

If there are any exceptions raised during one of the shared fixture
functions the test is reported as an error.  Because there is no
corresponding test instance an ‘_ErrorHolder’ object (that has the same
interface as a *note TestCase: 3f4.) is created to represent the error.
If you are just using the standard unittest test runner then this detail
doesn't matter, but if you are a framework author it may be relevant.

* Menu:

* setUpClass and tearDownClass::
* setUpModule and tearDownModule::


File: python.info,  Node: setUpClass and tearDownClass,  Next: setUpModule and tearDownModule,  Up: Class and Module Fixtures

5.26.5.15 setUpClass and tearDownClass
......................................

These must be implemented as class methods:

     import unittest

     class Test(unittest.TestCase):
         @classmethod
         def setUpClass(cls):
             cls._connection = createExpensiveConnectionObject()

         @classmethod
         def tearDownClass(cls):
             cls._connection.destroy()

If you want the ‘setUpClass’ and ‘tearDownClass’ on base classes called
then you must call up to them yourself.  The implementations in *note
TestCase: 3f4. are empty.

If an exception is raised during a ‘setUpClass’ then the tests in the
class are not run and the ‘tearDownClass’ is not run.  Skipped classes
will not have ‘setUpClass’ or ‘tearDownClass’ run.  If the exception is
a *note SkipTest: f87. exception then the class will be reported as
having been skipped instead of as an error.


File: python.info,  Node: setUpModule and tearDownModule,  Prev: setUpClass and tearDownClass,  Up: Class and Module Fixtures

5.26.5.16 setUpModule and tearDownModule
........................................

These should be implemented as functions:

     def setUpModule():
         createConnection()

     def tearDownModule():
         closeConnection()

If an exception is raised in a ‘setUpModule’ then none of the tests in
the module will be run and the ‘tearDownModule’ will not be run.  If the
exception is a *note SkipTest: f87. exception then the module will be
reported as having been skipped instead of as an error.

To add cleanup code that must be run even in the case of an exception,
use ‘addModuleCleanup’:

 -- 函式: unittest.addModuleCleanup (function, /, *args, **kwargs)

     Add a function to be called after ‘tearDownModule()’ to cleanup
     resources used during the test class.  Functions will be called in
     reverse order to the order they are added (LIFO).  They are called
     with any arguments and keyword arguments passed into *note
     addModuleCleanup(): 9f0. when they are added.

     If ‘setUpModule()’ fails, meaning that ‘tearDownModule()’ is not
     called, then any cleanup functions added will still be called.

     在 3.8 版被加入.

 -- 方法: classmethod unittest.enterModuleContext (cm)

     Enter the supplied *note context manager: 576.  If successful, also
     add its *note __exit__(): 1293. method as a cleanup function by
     *note addModuleCleanup(): 9f0. and return the result of the *note
     __enter__(): 56c. method.

     在 3.11 版被加入.

 -- 函式: unittest.doModuleCleanups ()

     This function is called unconditionally after ‘tearDownModule()’,
     or after ‘setUpModule()’ if ‘setUpModule()’ raises an exception.

     It is responsible for calling all the cleanup functions added by
     *note addModuleCleanup(): 9f0.  If you need cleanup functions to be
     called 'prior' to ‘tearDownModule()’ then you can call *note
     doModuleCleanups(): 1741. yourself.

     *note doModuleCleanups(): 1741. pops methods off the stack of
     cleanup functions one at a time, so it can be called at any time.

     在 3.8 版被加入.


File: python.info,  Node: Signal Handling,  Prev: Class and Module Fixtures,  Up: unittest --- 單元測試框架

5.26.5.17 Signal Handling
.........................

在 3.2 版被加入.

The *note -c/-catch: 12c7. command-line option to unittest, along with
the ‘catchbreak’ parameter to *note unittest.main(): f86, provide more
friendly handling of control-C during a test run.  With catch break
behavior enabled control-C will allow the currently running test to
complete, and the test run will then end and report all the results so
far.  A second control-c will raise a *note KeyboardInterrupt: 975. in
the usual way.

The control-c handling signal handler attempts to remain compatible with
code or tests that install their own *note signal.SIGINT: 7e8. handler.
If the ‘unittest’ handler is called but 'isn't' the installed *note
signal.SIGINT: 7e8. handler, i.e.  it has been replaced by the system
under test and delegated to, then it calls the default handler.  This
will normally be the expected behavior by code that replaces an
installed handler and delegates to it.  For individual tests that need
‘unittest’ control-c handling disabled the *note removeHandler(): 12c8.
decorator can be used.

There are a few utility functions for framework authors to enable
control-c handling functionality within test frameworks.

 -- 函式: unittest.installHandler ()

     Install the control-c handler.  When a *note signal.SIGINT: 7e8. is
     received (usually in response to the user pressing control-c) all
     registered results have *note stop(): 3ebd. called.

 -- 函式: unittest.registerResult (result)

     Register a *note TestResult: 1100. object for control-c handling.
     Registering a result stores a weak reference to it, so it doesn't
     prevent the result from being garbage collected.

     Registering a *note TestResult: 1100. object has no side-effects if
     control-c handling is not enabled, so test frameworks can
     unconditionally register all results they create independently of
     whether or not handling is enabled.

 -- 函式: unittest.removeResult (result)

     Remove a registered result.  Once a result has been removed then
     *note stop(): 3ebd. will no longer be called on that result object
     in response to a control-c.

 -- 函式: unittest.removeHandler (function=None)

     When called without arguments this function removes the control-c
     handler if it has been installed.  This function can also be used
     as a test decorator to temporarily remove the handler while the
     test is being executed:

          @unittest.removeHandler
          def test_signal_handling(self):
              ...


File: python.info,  Node: unittest mock — mock 物件函式庫,  Next: unittest mock --- 入門指南,  Prev: unittest --- 單元測試框架,  Up: 開發工具

5.26.6 ‘unittest.mock’ — mock 物件函式庫
----------------------------------------

在 3.3 版被加入.

'原始碼：'Lib/unittest/mock.py(1)

__________________________________________________________________

*note unittest.mock: f0. 在 Python 中是一個用於進行測試的函式庫。 它允許
你用 mock 物件在測試中替換部分系統，並判定它們是如何被使用的。

*note unittest.mock: f0. 提供了一個以 *note Mock: 9ef. 為核心的類別，去
除在測試中建立大量 stubs 的需求。 在執行動作之後，你可以判定哪些 method
（方法）／屬性被使用，以及有哪些引數被呼叫。 你還可以用常規的方式指定回
傳值與設定所需的屬性。

此外，mock 還提供了一個 *note patch(): e34. 裝飾器，用於 patching 測試範
圍內對 module（模組）以及 class（類別）級別的屬性，以及用於建立唯一物件
的 *note sentinel: b47.。有關如何使用 *note Mock: 9ef.、*note MagicMock:
e33. 和 *note patch(): e34. 的一些範例，請參閱*note 快速導引: 3ed2.。

Mock 被設計用於與 *note unittest: ef. 一起使用，並且基於 「action（操作
） -> assertion（判定）」 模式，而不是許多 mocking 框架使用的 「record（
記錄） -> replay（重播）」 模式。

對於早期版本的 Python，有一個 backport（向後移植的）*note unittest.mock:
f0. 可以使用，可從 PyPI 下載 mock(2)。

* Menu:

* 快速導引::
* Mock 類別::
* Patchers::
* MagicMock 以及魔術方法支援::
* 輔助函式: 輔助函式<2>.
* side_effect、return_value 和 wraps 的優先順序::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/unittest/mock.py

   (2) https://pypi.org/project/mock/


File: python.info,  Node: 快速導引,  Next: Mock 類別,  Up: unittest mock — mock 物件函式庫

5.26.6.1 快速導引
.................

*note Mock: 9ef. 和 *note MagicMock: e33. 物件在你存取它們時建立所有屬性
和 method（方法），並儲存它們如何被使用的詳細訊息。你可以配置它們，以指
定回傳值或限制可用的屬性，然後對它們的使用方式做出判定：

     >>> from unittest.mock import MagicMock
     >>> thing = ProductionClass()
     >>> thing.method = MagicMock(return_value=3)
     >>> thing.method(3, 4, 5, key='value')
     3
     >>> thing.method.assert_called_with(3, 4, 5, key='value')

‘side_effect’ 允許你執行 side effects，包含在 mock 被呼叫時引發例外：

     >>> from unittest.mock import Mock
     >>> mock = Mock(side_effect=KeyError('foo'))
     >>> mock()
     Traceback (most recent call last):
      ...
     KeyError: 'foo'

     >>> values = {'a': 1, 'b': 2, 'c': 3}
     >>> def side_effect(arg):
     ...     return values[arg]
     ...
     >>> mock.side_effect = side_effect
     >>> mock('a'), mock('b'), mock('c')
     (1, 2, 3)
     >>> mock.side_effect = [5, 4, 3, 2, 1]
     >>> mock(), mock(), mock()
     (5, 4, 3)

Mock 有許多其他方法可以讓你配置與控制它的行為。例如，'spec' 引數可以配置
mock ，讓其從另一個物件獲取規格。嘗試讀取 mock 中不存在於規格中的屬性或
方法將會失敗，並出現 *note AttributeError: 2f6.。

*note patch(): e34. 裝飾器／情境管理器可以在測試中簡單的 mock 模組中的類
別或物件。被指定的物件在測試期間會被替換為 mock（或其他物件），並在測試
結束時恢復：

     >>> from unittest.mock import patch
     >>> @patch('module.ClassName2')
     ... @patch('module.ClassName1')
     ... def test(MockClass1, MockClass2):
     ...     module.ClassName1()
     ...     module.ClassName2()
     ...     assert MockClass1 is module.ClassName1
     ...     assert MockClass2 is module.ClassName2
     ...     assert MockClass1.called
     ...     assert MockClass2.called
     ...
     >>> test()

     備註: 當你巢狀使用 patch 裝飾器時，mock 傳遞到被裝飾函式的順序會跟
     其被應用的順序相同（一般 'Python' 應用裝飾器的順序）。這意味著由下
     而上，因此在上面的範例中，‘module.ClassName1’ 的 mock 會先被傳入。

     使用 *note patch(): e34. 時，需注意的是你得在被查找物件的命名空間中
     （in the namespace where they are looked up）patch 物件。這通常很直
     接，但若需要快速導引，請參閱*note 該 patch 何處: 3ed3.。

裝飾器 *note patch(): e34. 也可以在 with 陳述式中被用來作為情境管理器：

     >>> with patch.object(ProductionClass, 'method', return_value=None) as mock_method:
     ...     thing = ProductionClass()
     ...     thing.method(1, 2, 3)
     ...
     >>> mock_method.assert_called_once_with(1, 2, 3)

也有 *note patch.dict(): 18f8.，用於在測試範圍中設定 dictionary（字典）
內的值，並在測試結束時將其恢復為原始狀態：

     >>> foo = {'key': 'value'}
     >>> original = foo.copy()
     >>> with patch.dict(foo, {'newkey': 'newvalue'}, clear=True):
     ...     assert foo == {'newkey': 'newvalue'}
     ...
     >>> assert foo == original

Mock 支援對 Python 的*note 魔術方法: 3ed4.的 mocking。最簡單使用魔術方法
的方式是使用 *note MagicMock: e33. 類別。它允許你執行以下操作：

     >>> mock = MagicMock()
     >>> mock.__str__.return_value = 'foobarbaz'
     >>> str(mock)
     'foobarbaz'
     >>> mock.__str__.assert_called_with()

Mock 允許你將函式（或其他 Mock 實例）分配給魔術方法，並且它們將被適當地
呼叫。*note MagicMock: e33. 類別是一個 Mock 的變體，它為你預先建好了所有
魔術方法（好吧，所有有用的方法）。

以下是在一般 Mock 類別中使用魔術方法的範例：

     >>> mock = Mock()
     >>> mock.__str__ = Mock(return_value='wheeeeee')
     >>> str(mock)
     'wheeeeee'

為了確保測試中的 mock 物件與它們要替換的物件具有相同的 api，你可以使用
*note 自動規格: 3ed5.。自動規格（auto-speccing）可以通過 patch 的
'autospec' 引數或 *note create_autospec(): 14fb. 函式來完成。自動規格建
立的 mock 物件與它們要替換的物件具有相同的屬性和方法，並且任何函式和方法
（包括建構函式）都具有與真實物件相同的呼叫簽名（call signature）。

這可以確保如果使用方法錯誤，你的 mock 會跟實際程式碼以相同的方式失敗：

     >>> from unittest.mock import create_autospec
     >>> def function(a, b, c):
     ...     pass
     ...
     >>> mock_function = create_autospec(function, return_value='fishy')
     >>> mock_function(1, 2, 3)
     'fishy'
     >>> mock_function.assert_called_once_with(1, 2, 3)
     >>> mock_function('wrong arguments')
     Traceback (most recent call last):
      ...
     TypeError: missing a required argument: 'b'

*note create_autospec(): 14fb. 也可以用在類別上，它複製了 ‘__init__’ 方
法的簽名，它也可以用在可呼叫物件上，其複製了 ‘__call__’ 方法的簽名。


File: python.info,  Node: Mock 類別,  Next: Patchers,  Prev: 快速導引,  Up: unittest mock — mock 物件函式庫

5.26.6.2 Mock 類別
..................

*note Mock: 9ef. 是一個彈性的的 mock 物件，旨在代替程式碼中 stubs 和
test doubles （測試替身）的使用。Mock 是可呼叫的，並在你存取它們時將屬性
建立為新的 mock (1)。存取相同的屬性將永遠回傳相同的 mock。Mock 記錄了你
如何使用它們，允許你判定你的程式碼對 mock 的行為。

*note MagicMock: e33. 是 *note Mock: 9ef. 的子類別，其中所有魔術方法均已
預先建立並可供使用。也有不可呼叫的變體，在你 mock 無法呼叫的物件時很有用
：*note NonCallableMock: 3ed7. 和 *note NonCallableMagicMock: 3ed8.

*note patch(): e34. 裝飾器可以輕鬆地用 *note Mock: 9ef. 物件臨時替換特定
模組中的類別。預設情況下，*note patch(): e34. 會為你建立一個 *note
MagicMock: e33.。你可以使用 *note patch(): e34. 的 'new_callable' 引數指
定 *note Mock: 9ef. 的替代類別。

 -- 類別: unittest.mock.Mock (spec=None, side_effect=None,
          return_value=DEFAULT, wraps=None, name=None, spec_set=None,
          unsafe=False, **kwargs)

     建立一個新的 *note Mock: 9ef. 物件。*note Mock: 9ef. 接受數個可選的
     引數來指定 Mock 物件的行為：

        * 'spec'：這可以是字串的 list（串列），也可以是充當 mock 物件規
          格的現有物件（類別或實例）。如果傳入一個物件，則通過對該物件呼
          叫 dir 來形成字串的串列（不包括不支援的魔術屬性和方法）。存取
          不在此串列中的任何屬性都會引發 *note AttributeError: 2f6.。

          如果 'spec' 是一個物件（而不是一個字串的串列），那麼 *note
          __class__: 1418. 會回傳 spec 物件的類別。這允許 mocks 通過
          *note isinstance(): 3e8. 測試。

        * 'spec_set'：'spec' 的一個更嚴格的變體。如果使用 'spec_set'，在
          mock 上嘗試 'set' 或取得不在傳遞給 'spec_set' 的物件上的屬性將
          會引發 *note AttributeError: 2f6.。

        * 'side_effect'：每當呼叫 Mock 時要呼叫的函式，參見 *note
          side_effect: 3ed9. 屬性，用於引發例外或動態變更回傳值。該函式
          使用與 mock 相同的引數呼叫，且除非它回傳 *note DEFAULT: 3eda.，
          否則此函式的回傳值將用作回傳值。

          'side_effect' 也可以是一個例外的類別或實例。在這種情況下，當呼
          叫 mock 時，該例外將被引發。

          如果 'side_effect' 是一個可疊代物件，那麼對 mock 的每次呼叫將
          回傳可疊代物件中的下一個值。

          'side_effect' 可以通過將其設置為 ‘None’ 來清除。

        * 'return_value'：當呼叫 mock 時回傳的值。預設情況下，這是一個新
          的 Mock（在首次存取時建立）。參見 *note return_value: 3edb. 屬
          性。

        * 'unsafe'：預設情況下，存取任何以 'assert'、'assret'、'asert'、
          'aseert' 或 'assrt' 開頭的屬性將引發 *note AttributeError:
          2f6.。如果傳遞 ‘unsafe=True’，將會允許存取這些屬性。

          在 3.5 版被加入.

        * 'wraps'：被 mock 物件包裝的項目。如果 'wraps' 不是 ‘None’，那
          麼呼叫 Mock 將通過被包裝的物件（回傳真實結果）。存取 mock 的屬
          性將會回傳一個 Mock 物件，該物件包裝了被包裝物件的對應屬性（因
          此嘗試存取不存在的屬性將引發 *note AttributeError: 2f6.）。

          如果 mock 已經明確設定了 'return_value'，那麼呼叫並不會被傳遞
          到被包裝的物件，而是回傳已設定好的 'return_value'。

        * 'name'：如果 mock 有一個名稱，那麼它會被用於 mock 的 repr。這
          對於除錯很有用。此名稱將被傳播到子 mocks。

     Mocks 還可以使用任意的關鍵字引數進行呼叫。這些關鍵字引數將在建立
     mock 之後用於設定 mock 的屬性。欲知更多，請參見 *note
     configure_mock(): 3edc. 方法。

      -- 方法: assert_called ()

          確認 mock 至少被呼叫一次。

               >>> mock = Mock()
               >>> mock.method()
               <Mock name='mock.method()' id='...'>
               >>> mock.method.assert_called()

          在 3.6 版被加入.

      -- 方法: assert_called_once ()

          確認 mock 只被呼叫一次。

               >>> mock = Mock()
               >>> mock.method()
               <Mock name='mock.method()' id='...'>
               >>> mock.method.assert_called_once()
               >>> mock.method()
               <Mock name='mock.method()' id='...'>
               >>> mock.method.assert_called_once()
               Traceback (most recent call last):
               ...
               AssertionError: Expected 'method' to have been called once. Called 2 times.
               Calls: [call(), call()].

          在 3.6 版被加入.

      -- 方法: assert_called_with (*args, **kwargs)

          這個方法是一個便利的方式，用來斷言最後一次呼叫是以特定方式進行
          的：

               >>> mock = Mock()
               >>> mock.method(1, 2, 3, test='wow')
               <Mock name='mock.method()' id='...'>
               >>> mock.method.assert_called_with(1, 2, 3, test='wow')

      -- 方法: assert_called_once_with (*args, **kwargs)

          確認 mock 只被呼叫一次，且該次呼叫使用了指定的引數。

               >>> mock = Mock(return_value=None)
               >>> mock('foo', bar='baz')
               >>> mock.assert_called_once_with('foo', bar='baz')
               >>> mock('other', bar='values')
               >>> mock.assert_called_once_with('other', bar='values')
               Traceback (most recent call last):
                 ...
               AssertionError: Expected 'mock' to be called once. Called 2 times.
               Calls: [call('foo', bar='baz'), call('other', bar='values')].

      -- 方法: assert_any_call (*args, **kwargs)

          斷言 mock 已經被使用指定的引數呼叫。

          這個斷言在 mock 曾經被呼叫過時通過，不同於 *note
          assert_called_with(): 1927. 和 *note
          assert_called_once_with(): 3edd.，他們針對的是最近的一次的呼叫
          ，而且對於 *note assert_called_once_with(): 3edd.，最近一次的
          呼叫還必須也是唯一一次的呼叫。

               >>> mock = Mock(return_value=None)
               >>> mock(1, 2, arg='thing')
               >>> mock('some', 'thing', 'else')
               >>> mock.assert_any_call(1, 2, arg='thing')

      -- 方法: assert_has_calls (calls, any_order=False)

          斷言 mock 已經使用指定的呼叫方式來呼叫。此斷言會檢查 *note
          mock_calls: 3edf. 串列中的呼叫。

          如果 'any_order' 為 false，那麼這些呼叫必須按照順序。在指定的
          呼叫之前或之後可以有額外的呼叫。

          如果 'any_order' 為 true，那麼這些呼叫可以以任何順序出現，但它
          們必須全部出現在 *note mock_calls: 3edf. 中。

               >>> mock = Mock(return_value=None)
               >>> mock(1)
               >>> mock(2)
               >>> mock(3)
               >>> mock(4)
               >>> calls = [call(2), call(3)]
               >>> mock.assert_has_calls(calls)
               >>> calls = [call(4), call(2), call(3)]
               >>> mock.assert_has_calls(calls, any_order=True)

      -- 方法: assert_not_called ()

          斷言 mock 從未被呼叫。

               >>> m = Mock()
               >>> m.hello.assert_not_called()
               >>> obj = m.hello()
               >>> m.hello.assert_not_called()
               Traceback (most recent call last):
                 ...
               AssertionError: Expected 'hello' to not have been called. Called 1 times.
               Calls: [call()].

          在 3.5 版被加入.

      -- 方法: reset_mock (*, return_value=False, side_effect=False)

          reset_mock 方法重置 mock 物件上的所有呼叫屬性：

               >>> mock = Mock(return_value=None)
               >>> mock('hello')
               >>> mock.called
               True
               >>> mock.reset_mock()
               >>> mock.called
               False

          在 3.6 版的變更: reset_mock 函式新增了兩個僅限關鍵字引數
          (keyword-only arguments)。

          這在你想要進行一系列重複使用同一物件的斷言時非常有用。請注意，
          預設情況下，*note reset_mock(): ca1. '不會'清除 *note
          return_value: 3edb.、*note side_effect: 3ed9. 或使用普通賦值設
          定的任何子屬性。如果你想要重置 *note return_value: 3edb. 或
          *note side_effect: 3ed9.，則將相應的參數設置為 ‘True’。Child
          mock 和回傳值 mock（如果有的話）也會被重置。

               備註: 'return_value' 和 'side_effect' 是僅限關鍵字引數。

      -- 方法: mock_add_spec (spec, spec_set=False)

          向 mock 增加一個規格 (spec)。'spec' 可以是一個物件或一個字串串
          列 (list of strings)。只有在 'spec' 上的屬性才能作為 mock 的屬
          性被取得。

          如果 'spec_set' 為 true，那麼只能設定在規格中的屬性。

      -- 方法: attach_mock (mock, attribute)

          將一個 mock 作為這個 Mock 的屬性附加，取代它的名稱和上代
          (parent)。對附加的 mock 的呼叫將被記錄在這個 Mock 的 *note
          method_calls: 3ee1. 和 *note mock_calls: 3edf. 屬性中。

      -- 方法: configure_mock (**kwargs)

          透過關鍵字引數在 mock 上設定屬性。

          可以在使用 method（方法）呼叫時，使用標準點記法 (dot notation)
          並將字典拆開，為 child mock 設定屬性、回傳值和 side effects：

               >>> mock = Mock()
               >>> attrs = {'method.return_value': 3, 'other.side_effect': KeyError}
               >>> mock.configure_mock(**attrs)
               >>> mock.method()
               3
               >>> mock.other()
               Traceback (most recent call last):
                 ...
               KeyError

          同樣的事情可以在 mock 的建構函式呼叫中實現：

               >>> attrs = {'method.return_value': 3, 'other.side_effect': KeyError}
               >>> mock = Mock(some_attribute='eggs', **attrs)
               >>> mock.some_attribute
               'eggs'
               >>> mock.method()
               3
               >>> mock.other()
               Traceback (most recent call last):
                 ...
               KeyError

          *note configure_mock(): 3edc. 的存在是為了在 mock 被建立後更容
          易進行組態設定。

      -- 方法: __dir__ ()

          *note Mock: 9ef. 物件限制了 ‘dir(some_mock)’ 僅顯示有用的結果
          。對於具有 'spec' 的 mock，這包含所有被允許的 mock 屬性。

          請參閱 *note FILTER_DIR: 3ee3. 以了解這種過濾行為的作用，以及
          如何關閉它。

      -- 方法: _get_child_mock (**kw)

          建立為了得到屬性和回傳值的 child mock。預設情況下，child mock
          將與其上代是相同的型別。Mock 的子類別可能會想要置換此行為，以
          自定義 child mock 的建立方式。

          對於不可呼叫的 mock，將使用可呼叫的變體，而不是任何的自定義子
          類別。

      -- 屬性: called

          一個 boolean（布林），表述 mock 物件是否已經被呼叫：

               >>> mock = Mock(return_value=None)
               >>> mock.called
               False
               >>> mock()
               >>> mock.called
               True

      -- 屬性: call_count

          一個整數，告訴你 mock 物件被呼叫的次數：

               >>> mock = Mock(return_value=None)
               >>> mock.call_count
               0
               >>> mock()
               >>> mock()
               >>> mock.call_count
               2

      -- 屬性: return_value

          設定此值以配置呼叫 mock 時回傳的值：

               >>> mock = Mock()
               >>> mock.return_value = 'fish'
               >>> mock()
               'fish'

          預設的回傳值是一個 mock 物件，你也可以按照正常的方式配置它：

               >>> mock = Mock()
               >>> mock.return_value.attribute = sentinel.Attribute
               >>> mock.return_value()
               <Mock name='mock()()' id='...'>
               >>> mock.return_value.assert_called_with()

          *note return_value: 3edb. 也可以在建構函式中設定：

               >>> mock = Mock(return_value=3)
               >>> mock.return_value
               3
               >>> mock()
               3

      -- 屬性: side_effect

          這可以是一個在呼叫 mock 時要呼叫的函式、一個可疊代物件，或者要
          引發的例外（類別或實例）。

          如果你傳遞一個函式，它將被呼叫，其引數與 mock 相同，且除非該函
          式回傳 *note DEFAULT: 3eda. 單例 (singleton)，否則對 mock 的呼
          叫將回傳函式回傳的任何值。如果函式回傳 *note DEFAULT: 3eda.，
          那麼 mock 將回傳其正常的回傳值（從 *note return_value: 3edb. 得
          到）。

          如果你傳遞一個可疊代物件，它將被用於檢索一個疊代器，該疊代器必
          須在每次呼叫時產出 (yield) 一個值。這個值可以是要引發的例外實
          例，或者是對 mock 呼叫時要回傳的值（處理 *note DEFAULT: 3eda.
          的方式與函式的狀況相同）。

          以下是一個引發例外的 mock 的範例（用於測試 API 的例外處理）：

               >>> mock = Mock()
               >>> mock.side_effect = Exception('Boom!')
               >>> mock()
               Traceback (most recent call last):
                 ...
               Exception: Boom!

          使用 *note side_effect: 3ed9. 回傳一連串值的範例：

               >>> mock = Mock()
               >>> mock.side_effect = [3, 2, 1]
               >>> mock(), mock(), mock()
               (3, 2, 1)

          使用可被呼叫物件的範例：

               >>> mock = Mock(return_value=3)
               >>> def side_effect(*args, **kwargs):
               ...     return DEFAULT
               ...
               >>> mock.side_effect = side_effect
               >>> mock()
               3

          *note side_effect: 3ed9. 可以在建構函式中設定。以下是一個範例
          ，它將 mock 被呼叫時給的值加一並回傳：

               >>> side_effect = lambda value: value + 1
               >>> mock = Mock(side_effect=side_effect)
               >>> mock(3)
               4
               >>> mock(-8)
               -7

          將 *note side_effect: 3ed9. 設定為 ‘None’ 可以清除它：

               >>> m = Mock(side_effect=KeyError, return_value=3)
               >>> m()
               Traceback (most recent call last):
                ...
               KeyError
               >>> m.side_effect = None
               >>> m()
               3

      -- 屬性: call_args

          這會是 ‘None’（如果 mock 尚未被呼叫），或是 mock 上次被呼叫時
          使用的引數。這將以元組的形式呈現：第一個成員 (member)，其可以
          通過 ‘args’ 屬性訪問，是 mock 被呼叫時傳遞的所有有序引數（或一
          個空元組）。第二個成員，其可以通過 ‘kwargs’ 屬性訪問，是所有關
          鍵字引數（或一個空字典）。

               >>> mock = Mock(return_value=None)
               >>> print(mock.call_args)
               None
               >>> mock()
               >>> mock.call_args
               call()
               >>> mock.call_args == ()
               True
               >>> mock(3, 4)
               >>> mock.call_args
               call(3, 4)
               >>> mock.call_args == ((3, 4),)
               True
               >>> mock.call_args.args
               (3, 4)
               >>> mock.call_args.kwargs
               {}
               >>> mock(3, 4, 5, key='fish', next='w00t!')
               >>> mock.call_args
               call(3, 4, 5, key='fish', next='w00t!')
               >>> mock.call_args.args
               (3, 4, 5)
               >>> mock.call_args.kwargs
               {'key': 'fish', 'next': 'w00t!'}

          *note call_args: 1884.，以及串列 *note call_args_list: 3ee7.、
          *note method_calls: 3ee1. 和 *note mock_calls: 3edf. 的成員都
          是 *note call: 18d3. 物件。這些都是元組，因此可以解包以獲取各
          個引數並進行更複雜的斷言。參見 *note calls as tuples: 3ee8.。

          在 3.8 版的變更: 新增 ‘args’ 與 ‘kwargs’ 特性。

      -- 屬性: call_args_list

          這是按順序列出所有呼叫 mock 物件的串列（因此串列的長度表示它被
          呼叫的次數）。在任何呼叫發生之前，它會是一個空的串列。 *note
          call: 18d3. 物件可用於方便地建構呼叫的串列，以便與 *note
          call_args_list: 3ee7. 進行比較。

               >>> mock = Mock(return_value=None)
               >>> mock()
               >>> mock(3, 4)
               >>> mock(key='fish', next='w00t!')
               >>> mock.call_args_list
               [call(), call(3, 4), call(key='fish', next='w00t!')]
               >>> expected = [(), ((3, 4),), ({'key': 'fish', 'next': 'w00t!'},)]
               >>> mock.call_args_list == expected
               True

          *note call_args_list: 3ee7. 的成員都是 *note call: 18d3. 物件
          。這些物件可以被拆包為元組，以取得各個引數。參見 *note calls
          as tuples: 3ee8.。

      -- 屬性: method_calls

          除了追蹤對自身的呼叫之外，mock 還會追蹤對方法和屬性的呼叫，以
          及'它們（這些方法和屬性）'的方法和屬性：

               >>> mock = Mock()
               >>> mock.method()
               <Mock name='mock.method()' id='...'>
               >>> mock.property.method.attribute()
               <Mock name='mock.property.method.attribute()' id='...'>
               >>> mock.method_calls
               [call.method(), call.property.method.attribute()]

          *note method_calls: 3ee1. 的成員都是 *note call: 18d3. 物件。
          這些物件可以拆包為元組，以取得各個引數。參見 *note calls as
          tuples: 3ee8.。

      -- 屬性: mock_calls

          *note mock_calls: 3edf. 記錄了 '所有' 對 mock 物件的呼叫，包含
          其方法、魔術方法以及回傳值 mock。

               >>> mock = MagicMock()
               >>> result = mock(1, 2, 3)
               >>> mock.first(a=3)
               <MagicMock name='mock.first()' id='...'>
               >>> mock.second()
               <MagicMock name='mock.second()' id='...'>
               >>> int(mock)
               1
               >>> result(1)
               <MagicMock name='mock()()' id='...'>
               >>> expected = [call(1, 2, 3), call.first(a=3), call.second(),
               ... call.__int__(), call()(1)]
               >>> mock.mock_calls == expected
               True

          ‘method_calls’ 的成員都是 *note call: 18d3. 物件。這些物件可以
          拆包為元組，以取得各個引數。參見 *note calls as tuples: 3ee8.。

               備註: *note mock_calls: 3edf. 記錄的方式意味著在進行巢狀
               呼叫時，上代 (ancestor) 呼叫的參數不會被記錄，因此在比較
               時它們將始終相等：

                    >>> mock = MagicMock()
                    >>> mock.top(a=3).bottom()
                    <MagicMock name='mock.top().bottom()' id='...'>
                    >>> mock.mock_calls
                    [call.top(a=3), call.top().bottom()]
                    >>> mock.mock_calls[-1] == call.top(a=-1).bottom()
                    True

      -- 屬性: __class__

          通常，物件的 *note __class__: 3ee9. 屬性會回傳它的型別。但對於
          擁有 ‘spec’ 的 mock 物件，‘__class__’ 會回傳 spec 的類別。這允
          許 mock 物件通過對它們所替代或偽裝的物件進行的 *note
          isinstance(): 3e8. 測試：

               >>> mock = Mock(spec=3)
               >>> isinstance(mock, int)
               True

          *note __class__: 3ee9. 可以被指定，這允許 mock 通過 *note
          isinstance(): 3e8. 檢查，而不需要強制使用 spec：

               >>> mock = Mock()
               >>> mock.__class__ = dict
               >>> isinstance(mock, dict)
               True

 -- 類別: unittest.mock.NonCallableMock (spec=None, wraps=None,
          name=None, spec_set=None, **kwargs)

     *note Mock: 9ef. 的一個不可呼叫版本。建構函式參數的意義與 *note
     Mock: 9ef. 相同，其例外為 'return_value' 和 'side_effect' 在不可呼
     叫的 mock 上無意義。

使用類別或實例作為 ‘spec’ 或 ‘spec_set’ 的 mock 物件能夠通過 *note
isinstance(): 3e8. 測試：

     >>> mock = Mock(spec=SomeClass)
     >>> isinstance(mock, SomeClass)
     True
     >>> mock = Mock(spec_set=SomeClass())
     >>> isinstance(mock, SomeClass)
     True

*note Mock: 9ef. 類別支援 mock 魔術方法。細節請參考*note 魔術方法:
3ed4.。

Mock類別和 *note patch(): e34. 裝飾器於組態時接受任意的關鍵字引數。對於
*note patch(): e34. 裝飾器，這些關鍵字會傳遞給正在建立 mock 的建構函式。
這些關鍵字引數用於配置 mock 的屬性：

     >>> m = MagicMock(attribute=3, other='fish')
     >>> m.attribute
     3
     >>> m.other
     'fish'

Child mock 的回傳值和 side effect 可以使用使用點記法進行設置。由於你無法
直接在呼叫中使用帶有點 (.)  的名稱，因此你必須建立一個字典並使用 ‘**’ 解
包：

     >>> attrs = {'method.return_value': 3, 'other.side_effect': KeyError}
     >>> mock = Mock(some_attribute='eggs', **attrs)
     >>> mock.some_attribute
     'eggs'
     >>> mock.method()
     3
     >>> mock.other()
     Traceback (most recent call last):
       ...
     KeyError

在匹配對 mock 的呼叫時，使用 'spec'（或 'spec_set'）建立的可呼叫 mock 將
會內省 (introspect) 規格物件的簽名 (signature)。因此，它可以匹配實際呼叫
的引數，無論它們是按位置傳遞還是按名稱傳遞：

     >>> def f(a, b, c): pass
     ...
     >>> mock = Mock(spec=f)
     >>> mock(1, 2, c=3)
     <Mock name='mock()' id='140161580456576'>
     >>> mock.assert_called_with(1, 2, 3)
     >>> mock.assert_called_with(a=1, b=2, c=3)

這適用於 *note assert_called_with(): 1927.、*note
assert_called_once_with(): 3edd.、*note assert_has_calls(): 15a0. 和
*note assert_any_call(): 3ede.。在使用 *note Autospeccing（自動規格）:
3ed5. 時，它還適用於 mock 物件的方法呼叫。

在 3.4 版的變更: 對於已經設置了規格（spec）和自動規格（autospec）的 mock
物件，新增簽名內省功能。

 -- 類別: unittest.mock.PropertyMock (*args, **kwargs)

     一個理應在類別上當成 *note property: 180. 或其他 *note descriptor:
     1e47. 的 mock。*note PropertyMock: 3eea. 提供了 *note __get__():
     16c3. 和 *note __set__(): 1e3f. 方法，因此你可以在它被提取時指定回
     傳值。

     從物件中提取 *note PropertyMock: 3eea. 實例會不帶任何引數呼叫 mock。
     設定它則會用設定的值來呼叫 mock：

          >>> class Foo:
          ...     @property
          ...     def foo(self):
          ...         return 'something'
          ...     @foo.setter
          ...     def foo(self, value):
          ...         pass
          ...
          >>> with patch('__main__.Foo.foo', new_callable=PropertyMock) as mock_foo:
          ...     mock_foo.return_value = 'mockity-mock'
          ...     this_foo = Foo()
          ...     print(this_foo.foo)
          ...     this_foo.foo = 6
          ...
          mockity-mock
          >>> mock_foo.mock_calls
          [call(), call(6)]

由於 mock 屬性的儲存方式，你無法直接將 *note PropertyMock: 3eea. 附加到
mock 物件。但是你可以將其附加到 mock 型別的物件：

     >>> m = MagicMock()
     >>> p = PropertyMock(return_value=3)
     >>> type(m).foo = p
     >>> m.foo
     3
     >>> p.assert_called_once_with()

     警示: If an *note AttributeError: 2f6. is raised by *note
     PropertyMock: 3eea, it will be interpreted as a missing descriptor
     and *note __getattr__(): 47a. will be called on the parent mock:

          >>> m = MagicMock()
          >>> no_attribute = PropertyMock(side_effect=AttributeError)
          >>> type(m).my_property = no_attribute
          >>> m.my_property
          <MagicMock name='mock.my_property' id='140165240345424'>

     詳情請見 *note __getattr__(): 47a.。

 -- 類別: unittest.mock.AsyncMock (spec=None, side_effect=None,
          return_value=DEFAULT, wraps=None, name=None, spec_set=None,
          unsafe=False, **kwargs)

     *note MagicMock: e33. 的非同步版本。*note AsyncMock: 9ee. 物件的表
     現將被視為非同步函式，並且呼叫的結果是一個可等待物件。

          >>> mock = AsyncMock()
          >>> asyncio.iscoroutinefunction(mock)
          True
          >>> inspect.isawaitable(mock())
          True

     ‘mock()’ 的結果是一個非同步函式，在它被等待後將具有 ‘side_effect’ 或
     ‘return_value’ 的結果：

        - 如果 ‘side_effect’ 是一個函式，非同步函式將回傳該函式的結果，

        - 如果 ‘side_effect’ 是一個例外，則非同步函式將引發該例外，

        - 如果 ‘side_effect’ 是一個可疊代物件，非同步函式將回傳可疊代物
          件的下一個值，但如果結果序列耗盡，將立即引發
          ‘StopAsyncIteration’，

        - 如果 ‘side_effect’ 沒有被定義，非同步函式將回傳由
          ‘return_value’ 定義的值，因此在預設情況下，非同步函式回傳一個
          新的 *note AsyncMock: 9ee. 物件。

     將 *note Mock: 9ef. 或 *note MagicMock: e33. 的 'spec' 設定為非同步
     函式將導致在呼叫後回傳一個協程物件。

          >>> async def async_func(): pass
          ...
          >>> mock = MagicMock(async_func)
          >>> mock
          <MagicMock spec='function' id='...'>
          >>> mock()
          <coroutine object AsyncMockMixin._mock_call at ...>

     將 *note Mock: 9ef.、*note MagicMock: e33. 或 *note AsyncMock: 9ee.
     的 'spec' 設定為具有同步和非同步函式的類別，會自動檢測同步函式並將
     其設定為 *note MagicMock: e33.（如果上代 mock 為 *note AsyncMock:
     9ee. 或 *note MagicMock: e33.）或 *note Mock: 9ef.（如果上代 mock 為
     *note Mock: 9ef.）。所有非同步函式將被設定為 *note AsyncMock: 9ee.。

          >>> class ExampleClass:
          ...     def sync_foo():
          ...         pass
          ...     async def async_foo():
          ...         pass
          ...
          >>> a_mock = AsyncMock(ExampleClass)
          >>> a_mock.sync_foo
          <MagicMock name='mock.sync_foo' id='...'>
          >>> a_mock.async_foo
          <AsyncMock name='mock.async_foo' id='...'>
          >>> mock = Mock(ExampleClass)
          >>> mock.sync_foo
          <Mock name='mock.sync_foo' id='...'>
          >>> mock.async_foo
          <AsyncMock name='mock.async_foo' id='...'>

     在 3.8 版被加入.

      -- 方法: assert_awaited ()

          斷言 mock 至少被等待過一次。請注意這與物件是否被呼叫是分開的，
          ‘await’ 關鍵字必須被使用：

               >>> mock = AsyncMock()
               >>> async def main(coroutine_mock):
               ...     await coroutine_mock
               ...
               >>> coroutine_mock = mock()
               >>> mock.called
               True
               >>> mock.assert_awaited()
               Traceback (most recent call last):
               ...
               AssertionError: Expected mock to have been awaited.
               >>> asyncio.run(main(coroutine_mock))
               >>> mock.assert_awaited()

      -- 方法: assert_awaited_once ()

          斷言 mock 正好被等待了一次。

               >>> mock = AsyncMock()
               >>> async def main():
               ...     await mock()
               ...
               >>> asyncio.run(main())
               >>> mock.assert_awaited_once()
               >>> asyncio.run(main())
               >>> mock.assert_awaited_once()
               Traceback (most recent call last):
               ...
               AssertionError: Expected mock to have been awaited once. Awaited 2 times.

      -- 方法: assert_awaited_with (*args, **kwargs)

          斷言最後一次等待使用了指定的引數。

               >>> mock = AsyncMock()
               >>> async def main(*args, **kwargs):
               ...     await mock(*args, **kwargs)
               ...
               >>> asyncio.run(main('foo', bar='bar'))
               >>> mock.assert_awaited_with('foo', bar='bar')
               >>> mock.assert_awaited_with('other')
               Traceback (most recent call last):
               ...
               AssertionError: expected await not found.
               Expected: mock('other')
               Actual: mock('foo', bar='bar')

      -- 方法: assert_awaited_once_with (*args, **kwargs)

          斷言 mock 只被等待了一次並使用了指定的引數。

               >>> mock = AsyncMock()
               >>> async def main(*args, **kwargs):
               ...     await mock(*args, **kwargs)
               ...
               >>> asyncio.run(main('foo', bar='bar'))
               >>> mock.assert_awaited_once_with('foo', bar='bar')
               >>> asyncio.run(main('foo', bar='bar'))
               >>> mock.assert_awaited_once_with('foo', bar='bar')
               Traceback (most recent call last):
               ...
               AssertionError: Expected mock to have been awaited once. Awaited 2 times.

      -- 方法: assert_any_await (*args, **kwargs)

          斷言 mock 曾經被使用指定的引數等待過。

               >>> mock = AsyncMock()
               >>> async def main(*args, **kwargs):
               ...     await mock(*args, **kwargs)
               ...
               >>> asyncio.run(main('foo', bar='bar'))
               >>> asyncio.run(main('hello'))
               >>> mock.assert_any_await('foo', bar='bar')
               >>> mock.assert_any_await('other')
               Traceback (most recent call last):
               ...
               AssertionError: mock('other') await not found

      -- 方法: assert_has_awaits (calls, any_order=False)

          斷言 mock 已被使用指定的呼叫進行等待。*note await_args_list:
          1883. 串列將被檢查以確認等待的內容。

          如果 'any_order' 為 false，則等待必須按照順序。指定的等待之前
          或之後可以有額外的呼叫。

          如果 'any_order' 為 true，則等待可以以任何順序出現，但它們必須
          全部出現在 *note await_args_list: 1883. 中。

               >>> mock = AsyncMock()
               >>> async def main(*args, **kwargs):
               ...     await mock(*args, **kwargs)
               ...
               >>> calls = [call("foo"), call("bar")]
               >>> mock.assert_has_awaits(calls)
               Traceback (most recent call last):
               ...
               AssertionError: Awaits not found.
               Expected: [call('foo'), call('bar')]
               Actual: []
               >>> asyncio.run(main('foo'))
               >>> asyncio.run(main('bar'))
               >>> mock.assert_has_awaits(calls)

      -- 方法: assert_not_awaited ()

          斷言 mock 從未被等待。

               >>> mock = AsyncMock()
               >>> mock.assert_not_awaited()

      -- 方法: reset_mock (*args, **kwargs)

          參見 *note Mock.reset_mock(): ca1.。同時將 *note await_count:
          3ef3. 設定為 0，*note await_args: 3ef4. 設定為 None，並清除
          *note await_args_list: 1883.。

      -- 屬性: await_count

          一個整數，用來記錄 mock 物件已被等待的次數。

               >>> mock = AsyncMock()
               >>> async def main():
               ...     await mock()
               ...
               >>> asyncio.run(main())
               >>> mock.await_count
               1
               >>> asyncio.run(main())
               >>> mock.await_count
               2

      -- 屬性: await_args

          這可能是 ‘None’（如果 mock 尚未被等待），或者是上次等待 mock 時
          使用的引數。與 *note Mock.call_args: 1884. 的功能相同。

               >>> mock = AsyncMock()
               >>> async def main(*args):
               ...     await mock(*args)
               ...
               >>> mock.await_args
               >>> asyncio.run(main('foo'))
               >>> mock.await_args
               call('foo')
               >>> asyncio.run(main('bar'))
               >>> mock.await_args
               call('bar')

      -- 屬性: await_args_list

          這是一個按照順序記錄 mock 物件所有等待的串列（因此串列的長度表
          示該物件已被等待的次數）。在進行任何等待之前，此串列為空。

               >>> mock = AsyncMock()
               >>> async def main(*args):
               ...     await mock(*args)
               ...
               >>> mock.await_args_list
               []
               >>> asyncio.run(main('foo'))
               >>> mock.await_args_list
               [call('foo')]
               >>> asyncio.run(main('bar'))
               >>> mock.await_args_list
               [call('foo'), call('bar')]

 -- 類別: unittest.mock.ThreadingMock (spec=None, side_effect=None,
          return_value=DEFAULT, wraps=None, name=None, spec_set=None,
          unsafe=False, *, timeout=UNSET, **kwargs)

     A version of *note MagicMock: e33. for multithreading tests.  The
     *note ThreadingMock: 3ef5. object provides extra methods to wait
     for a call to be invoked, rather than assert on it immediately.

     The default timeout is specified by the ‘timeout’ argument, or if
     unset by the *note ThreadingMock.DEFAULT_TIMEOUT: 3ef6. attribute,
     which defaults to blocking (‘None’).

     You can configure the global default timeout by setting *note
     ThreadingMock.DEFAULT_TIMEOUT: 3ef6.

      -- 方法: wait_until_called (*, timeout=UNSET)

          Waits until the mock is called.

          If a timeout was passed at the creation of the mock or if a
          timeout argument is passed to this function, the function
          raises an *note AssertionError: 64e. if the call is not
          performed in time.

               >>> mock = ThreadingMock()
               >>> thread = threading.Thread(target=mock)
               >>> thread.start()
               >>> mock.wait_until_called(timeout=1)
               >>> thread.join()

      -- 方法: wait_until_any_call_with (*args, **kwargs)

          Waits until the mock is called with the specified arguments.

          If a timeout was passed at the creation of the mock the
          function raises an *note AssertionError: 64e. if the call is
          not performed in time.

               >>> mock = ThreadingMock()
               >>> thread = threading.Thread(target=mock, args=("arg1", "arg2",), kwargs={"arg": "thing"})
               >>> thread.start()
               >>> mock.wait_until_any_call_with("arg1", "arg2", arg="thing")
               >>> thread.join()

      -- 屬性: DEFAULT_TIMEOUT

          Global default timeout in seconds to create instances of *note
          ThreadingMock: 3ef5.

     在 3.13 版被加入.

* Menu:

* 呼叫::
* 刪除屬性::
* Mock 名稱與名稱屬性::
* 如同屬性一般附加 mock::

   ---------- Footnotes ----------

   (1) 唯一的例外是魔術方法和屬性（具有前後雙底線）。Mock 不會建立這些，
而是會引發 *note AttributeError: 2f6.。這是因為直譯器通常會隱式地要求這
些方法，在期望得到一個魔術方法卻獲得一個新的 Mock 物件時，會讓直譯器'非
常'困惑。如果你需要魔術方法的支援，請參閱*note 魔術方法: 3ed4.。


File: python.info,  Node: 呼叫,  Next: 刪除屬性,  Up: Mock 類別

5.26.6.3 呼叫
.............

Mock 物件可被呼叫。呼叫將回傳設定為 *note return_value: 3edb. 屬性的值。
預設的回傳值是一個新的 Mock 物件；它會在第一次存取回傳值時（無論是顯式存
取還是透過呼叫 Mock）被建立，但是這個回傳值會被儲存，之後每次都回傳同一
個值。

對物件的呼叫會被記錄在如 *note call_args: 1884. 和 *note call_args_list:
3ee7. 等屬性中。

如果 *note side_effect: 3ed9. 被設定，那麼在呼叫被記錄後它才會被呼叫，所
以如果 ‘side_effect’ 引發例外，呼叫仍然會被記錄。

呼叫 mock 時引發例外的最簡單方式是將 *note side_effect: 3ed9. 設定為例外
類別或實例：

     >>> m = MagicMock(side_effect=IndexError)
     >>> m(1, 2, 3)
     Traceback (most recent call last):
       ...
     IndexError
     >>> m.mock_calls
     [call(1, 2, 3)]
     >>> m.side_effect = KeyError('Bang!')
     >>> m('two', 'three', 'four')
     Traceback (most recent call last):
       ...
     KeyError: 'Bang!'
     >>> m.mock_calls
     [call(1, 2, 3), call('two', 'three', 'four')]

如果 ‘side_effect’ 是一個函式，則該函式回傳的東西就是對 mock 的呼叫所回
傳的值。‘side_effect’ 函式會使用與 mock 相同的引數被呼叫。這讓你可以根據
輸入動態地變更呼叫的回傳值：

     >>> def side_effect(value):
     ...     return value + 1
     ...
     >>> m = MagicMock(side_effect=side_effect)
     >>> m(1)
     2
     >>> m(2)
     3
     >>> m.mock_calls
     [call(1), call(2)]

如果你希望 mock 仍然回傳預設的回傳值（一個新的 mock），或者是任何已設定
的回傳值，有兩種方法可以實現。從 ‘side_effect’ 內部回傳
‘mock.return_value’，或回傳 *note DEFAULT: 3eda.：

     >>> m = MagicMock()
     >>> def side_effect(*args, **kwargs):
     ...     return m.return_value
     ...
     >>> m.side_effect = side_effect
     >>> m.return_value = 3
     >>> m()
     3
     >>> def side_effect(*args, **kwargs):
     ...     return DEFAULT
     ...
     >>> m.side_effect = side_effect
     >>> m()
     3

要刪除 ‘side_effect’，並恢復預設行為，將 ‘side_effect’ 設為 ‘None’：

     >>> m = MagicMock(return_value=6)
     >>> def side_effect(*args, **kwargs):
     ...     return 3
     ...
     >>> m.side_effect = side_effect
     >>> m()
     3
     >>> m.side_effect = None
     >>> m()
     6

‘side_effect’ 也可以是任何可疊代的物件。對 mock 的重複呼叫將從可疊代物件
中回傳值（直到疊代物件耗盡並引發 *note StopIteration: ba1. 為止）：

     >>> m = MagicMock(side_effect=[1, 2, 3])
     >>> m()
     1
     >>> m()
     2
     >>> m()
     3
     >>> m()
     Traceback (most recent call last):
       ...
     StopIteration

如果可疊代物件中的任何成員是例外，則它們將被引發而不是被回傳：

     >>> iterable = (33, ValueError, 66)
     >>> m = MagicMock(side_effect=iterable)
     >>> m()
     33
     >>> m()
     Traceback (most recent call last):
      ...
     ValueError
     >>> m()
     66


File: python.info,  Node: 刪除屬性,  Next: Mock 名稱與名稱屬性,  Prev: 呼叫,  Up: Mock 類別

5.26.6.4 刪除屬性
.................

Mock 物件會在需要時建立屬性。這使得它們可以假裝成任何種類的物件。

你可能希望一個 mock 物件在 *note hasattr(): 479. 呼叫時回傳 ‘False’，或
者在屬性被提取時引發 *note AttributeError: 2f6.。你可以通過將物件提供為
mock 的 ‘spec’ 來實現這一點，但這並不總是那麼好用。

你可以通過刪除屬性來「阻擋」它們。一旦刪除，再次存取該屬性將會引發 *note
AttributeError: 2f6.。

     >>> mock = MagicMock()
     >>> hasattr(mock, 'm')
     True
     >>> del mock.m
     >>> hasattr(mock, 'm')
     False
     >>> del mock.f
     >>> mock.f
     Traceback (most recent call last):
         ...
     AttributeError: f


File: python.info,  Node: Mock 名稱與名稱屬性,  Next: 如同屬性一般附加 mock,  Prev: 刪除屬性,  Up: Mock 類別

5.26.6.5 Mock 名稱與名稱屬性
............................

由於 "name" 是傳遞給 *note Mock: 9ef. 建構函式的引數，如果你想讓你的
mock 物件擁有 "name" 屬性，你不能在建立時直接傳遞它。有兩種替代方法。其
中一個選擇是使用 *note configure_mock(): 3edc.：

     >>> mock = MagicMock()
     >>> mock.configure_mock(name='my_name')
     >>> mock.name
     'my_name'

更簡單的方法是在 mock 建立後直接設定 "name" 屬性：

     >>> mock = MagicMock()
     >>> mock.name = "foo"


File: python.info,  Node: 如同屬性一般附加 mock,  Prev: Mock 名稱與名稱屬性,  Up: Mock 類別

5.26.6.6 如同屬性一般附加 mock
..............................

當你將一個 mock 附加為另一個 mock 的屬性（或作為回傳值），它將成為該
mock 的「子代 (child)」。對子代的呼叫將被記錄在上代的 *note
method_calls: 3ee1. 和 *note mock_calls: 3edf. 屬性中。這對於配置子代並
將它們附加到上代，或將 mock 附加到記錄所有對子代的呼叫的上代並允許你對
mock 間的呼叫順序進行斷言非常有用：

     >>> parent = MagicMock()
     >>> child1 = MagicMock(return_value=None)
     >>> child2 = MagicMock(return_value=None)
     >>> parent.child1 = child1
     >>> parent.child2 = child2
     >>> child1(1)
     >>> child2(2)
     >>> parent.mock_calls
     [call.child1(1), call.child2(2)]

如果 mock 有 name 引數，則上述規則會有例外。這使你可以防止「親屬關係
(parenting)」的建立，假設因為某些原因你不希望這種狀況發生。

     >>> mock = MagicMock()
     >>> not_a_child = MagicMock(name='not-a-child')
     >>> mock.attribute = not_a_child
     >>> mock.attribute()
     <MagicMock name='not-a-child()' id='...'>
     >>> mock.mock_calls
     []

由 *note patch(): e34. 為你建立的 mock 會自動被賦予名稱。若要將具有名稱
的 mock 附加到上代，你可以使用 *note attach_mock(): 1502. 方法：

     >>> thing1 = object()
     >>> thing2 = object()
     >>> parent = MagicMock()
     >>> with patch('__main__.thing1', return_value=None) as child1:
     ...     with patch('__main__.thing2', return_value=None) as child2:
     ...         parent.attach_mock(child1, 'child1')
     ...         parent.attach_mock(child2, 'child2')
     ...         child1('one')
     ...         child2('two')
     ...
     >>> parent.mock_calls
     [call.child1('one'), call.child2('two')]


File: python.info,  Node: Patchers,  Next: MagicMock 以及魔術方法支援,  Prev: Mock 類別,  Up: unittest mock — mock 物件函式庫

5.26.6.7 Patchers
.................

patch 裝飾器僅用於在裝飾的函式範圍內對物件進行 patch。它們會自動為你處理
patch 的中止，即使有異常被引發也是如此。所有這些函式也可以在 with 陳述式
中使用，或者作為類別裝飾器使用。

* Menu:

* patch::
* patch.object: patch object.
* patch.dict: patch dict.
* patch.multiple: patch multiple.
* patch 方法：啟動與停止::
* patch 內建函式::
* TEST_PREFIX::
* 巢狀使用 Patch 裝飾器::
* 該 patch 何處::
* Patch 描述器與代理物件 (Proxy Objects): Patch 描述器與代理物件 Proxy Objects.


File: python.info,  Node: patch,  Next: patch object,  Up: Patchers

5.26.6.8 patch
..............

     備註: 關鍵是要在正確的命名空間進行 patch。請參閱 *note where to
     patch: 3f00. 一節。

 -- 函式: unittest.mock.patch (target, new=DEFAULT, spec=None,
          create=False, spec_set=None, autospec=None, new_callable=None,
          **kwargs)

     *note patch(): e34. 充當函式裝飾器、類別裝飾器或情境管理器。在函式
     或 with 陳述式的內部，'目標'會被 patch 成一個'新的'物件。當函式或
     with 陳述式結束時，patch 就會被解除。

     如果 'new' 被省略，則如果被 patch 的物件是非同步函式，目標會被替換
     為 *note AsyncMock: 9ee.，反之則替換為 *note MagicMock: e33.。如果
     *note patch(): e34. 做為裝飾器使用且省略了 'new'，則所建立的 mock 會
     作為額外的引數傳遞給被裝飾的函式。如果 *note patch(): e34. 作為情境
     管理器使用，則所建立的 mock 將由情境管理器回傳。

     'target' 應該是以 ‘'package.module.ClassName'’ 形式出現的字串。
     'target' 會被引入並用 'new' 物件替換指定的物件，因此 'target' 必須
     可從你呼叫 *note patch(): e34. 的環境中引入。target 在執行被裝飾的
     函式時被引入，而不是在裝飾器作用時 (decoration time)。

     'spec' 和 'spec_set' 關鍵字引數會傳遞給 *note MagicMock: e33.，如果
     patch 正在為你建立一個。

     此外，你還可以傳遞 ‘spec=True’ 或 ‘spec_set=True’，這將導致 patch 將
     被 mock 的物件作為 spec/spec_set 物件傳遞。

     'new_callable' 允許你指定一個不同的類別或可呼叫的物件，用於被呼叫並
     建立 'new' 物件。預設情況下，對於非同步函式使用 *note AsyncMock:
     9ee.，而對於其他情況則使用 *note MagicMock: e33.。

     'spec' 的一種更強大的形式是 'autospec'。如果你設定 ‘autospec=True’，
     則該 mock 將使用被替換物件的規格來建立。該 mock 的所有屬性也將具有
     被替換物件的對應屬性的規格。被 mock 的方法和函式將檢查其引數，如果
     呼叫時引數與規格不符（被使用錯誤的簽名 (signature) 呼叫），將引發
     *note TypeError: 4dd.。對於替換類別的 mock，它們的回傳值（即
     'instance'）將具有與類別相同的規格。請參閱 *note create_autospec():
     14fb. 函式和 *note Autospeccing（自動規格）: 3ed5.。

     你可以用 ‘autospec=some_object’ 替代 ‘autospec=True’，以使用任意物
     件作為規格，而不是被替換的物件。

     預設情況下，*note patch(): e34. 將無法取代不存在的屬性。如果你傳入
     ‘create=True’，且屬性不存在，則當被 patch 的函式被呼叫時，patch 將
     為你建立該屬性，並在被 patch 的函式結束後再次刪除它。這對於撰寫針對
     你的生產程式碼在執行環境建立的屬性的測試時非常有用。此功能預設為關
     閉，因為這可能會相當危險。開啟這個功能後，你可以對於實際上不存在的
     API 撰寫會通過的測試！

          備註: 
          在 3.5 版的變更: 如果你正在 patch 模組中的內建函式，那麼你不需
          要傳遞 ‘create=True’，它預設會被加入。

     patch 可以做為 ‘TestCase’ 類別的裝飾器使用。它透過裝飾類別中的每個
     測試方法來運作。當你的測試方法共享一組常見的 patch 時，這會減少繁冗
     的代碼。*note patch(): e34. 通過搜尋以 ‘patch.TEST_PREFIX’ 開頭的方
     法名來尋找測試。預設情況下會是 ‘'test'’，這與 *note unittest: ef. 尋
     找測試的方式相匹配。你可以通過設定 ‘patch.TEST_PREFIX’ 來指定別的前
     綴。

     透過 with 陳述式，Patch 可以做為情境管理器使用。patch 適用於 with 陳
     述式之後的縮排區塊。如果你使用 "as"，則被 patch 的物件將被綁定到
     "as" 後面的名稱；如果 *note patch(): e34. 正在為你建立一個 mock 物
     件，這會非常有用。

     *note patch(): e34. 接受任意的關鍵字引數。如果被 patch 的物件是非同
     步的，這些將會被傳遞給 *note AsyncMock: 9ee.，如果是同步的則會傳遞
     給 *note MagicMock: e33.，或如果指定了 'new_callable'，則傳遞給它。

     ‘patch.dict(...)’、‘patch.multiple(...)’ 和 ‘patch.object(...)’ 可
     用於其餘的使用情境。

*note patch(): e34. 作為函式裝飾器，為你建立 mock 並將其傳遞給被裝飾的函
式：

     >>> @patch('__main__.SomeClass')
     ... def function(normal_argument, mock_class):
     ...     print(mock_class is SomeClass)
     ...
     >>> function(None)
     True

Patch 一個類別會以 *note MagicMock: e33. '實例'取代該類別。如果該類別在
被測試的程式碼中實例化，那麼它將是會被使用的 mock 的 *note return_value:
3edb.。

如果該類別被實例化多次，你可以使用 *note side_effect: 3ed9. 來每次回傳一
個新的 mock。 或者你可以將 'return_value' 設定成你想要的任何值。

若要配置被 patch 的類別的'實例'方法的回傳值，你必須在 ‘return_value’ 上
進行配置。 例如：

     >>> class Class:
     ...     def method(self):
     ...         pass
     ...
     >>> with patch('__main__.Class') as MockClass:
     ...     instance = MockClass.return_value
     ...     instance.method.return_value = 'foo'
     ...     assert Class() is instance
     ...     assert Class().method() == 'foo'
     ...

如果你使用 'spec' 或 'spec_set' 且 *note patch(): e34. 正在取代一個'類別
'，那麼被建立的 mock 的回傳值將具有相同的規格。：

     >>> Original = Class
     >>> patcher = patch('__main__.Class', spec=True)
     >>> MockClass = patcher.start()
     >>> instance = MockClass()
     >>> assert isinstance(instance, Original)
     >>> patcher.stop()

當你想要為被建立的 mock 使用一個替代的類別取代預設的 *note MagicMock:
e33. 時，'new_callable' 引數非常有用。例如，如果你想要一個 *note
NonCallableMock: 3ed7. 被使用：

     >>> thing = object()
     >>> with patch('__main__.thing', new_callable=NonCallableMock) as mock_thing:
     ...     assert thing is mock_thing
     ...     thing()
     ...
     Traceback (most recent call last):
       ...
     TypeError: 'NonCallableMock' object is not callable

另一個用法是用一個 *note io.StringIO: ecb. 實例替換一個物件：

     >>> from io import StringIO
     >>> def foo():
     ...     print('Something')
     ...
     >>> @patch('sys.stdout', new_callable=StringIO)
     ... def test(mock_stdout):
     ...     foo()
     ...     assert mock_stdout.getvalue() == 'Something\n'
     ...
     >>> test()

當 *note patch(): e34. 為你建立 mock 時，通常你需要做的第一件事就是配置
mock。其中一些配置可以在對 patch 的呼叫中完成。你傳遞到呼叫中的任何關鍵
字都將用於在被建立的 mock 上設定屬性：

     >>> patcher = patch('__main__.thing', first='one', second='two')
     >>> mock_thing = patcher.start()
     >>> mock_thing.first
     'one'
     >>> mock_thing.second
     'two'

除了被建立的 mock 上的屬性外，還可以配置 child mock 的 *note
return_value: 3edb. 和 *note side_effect: 3ed9.。它們在語法上不能直接作
為關鍵字引數傳入，但是以它們作為鍵的字典仍然可以使用 ‘**’ 擴充為一個
*note patch(): e34. 呼叫：

     >>> config = {'method.return_value': 3, 'other.side_effect': KeyError}
     >>> patcher = patch('__main__.thing', **config)
     >>> mock_thing = patcher.start()
     >>> mock_thing.method()
     3
     >>> mock_thing.other()
     Traceback (most recent call last):
       ...
     KeyError

預設情況下，嘗試 patch 模組中不存在的函式（或類別中的方法或屬性）將會失
敗，並引發 *note AttributeError: 2f6.：

     >>> @patch('sys.non_existing_attribute', 42)
     ... def test():
     ...     assert sys.non_existing_attribute == 42
     ...
     >>> test()
     Traceback (most recent call last):
       ...
     AttributeError: <module 'sys' (built-in)> does not have the attribute 'non_existing_attribute'

但是在對 *note patch(): e34. 的呼叫中增加 ‘create=True’ 將使前面的範例按
照預期運作：

     >>> @patch('sys.non_existing_attribute', 42, create=True)
     ... def test(mock_stdout):
     ...     assert sys.non_existing_attribute == 42
     ...
     >>> test()

在 3.8 版的變更: 如果目標是一個非同步函式，*note patch(): e34. 現在會回
傳一個 *note AsyncMock: 9ee.。


File: python.info,  Node: patch object,  Next: patch dict,  Prev: patch,  Up: Patchers

5.26.6.9 patch.object
.....................

 -- 函式: patch.object (target, attribute, new=DEFAULT, spec=None,
          create=False, spec_set=None, autospec=None, new_callable=None,
          **kwargs)

     使用一個 mock 物件 patch 一個物件（'目標'）上的命名成員（'屬性'）。

     *note patch.object(): 18bb. 可以做為裝飾器、類別裝飾器或情境管理器
     使用。引數 'new'、'spec'、'create'、'spec_set'、'autospec' 和
     'new_callable' 與在 *note patch(): e34. 中的引數具有相同的意義。與
     *note patch(): e34. 一樣，*note patch.object(): 18bb. 接受任意關鍵
     字引數來配置它所建立的 mock 物件。

     當作為類別裝飾器使用時，*note patch.object(): 18bb. 會遵循
     ‘patch.TEST_PREFIX’ 來選擇要包裝的方法。

你可以使用三個引數或兩個引數來呼叫 *note patch.object(): 18bb.。三個引數
的形式接受要被 patch 的物件、屬性名稱和要替換掉屬性的物件。

當使用兩個引數的形式呼叫時，你會省略要替換的物件，一個 mock 會為你建立並
將其作為額外的引數傳遞給被裝飾的函式：

     >>> @patch.object(SomeClass, 'class_method')
     ... def test(mock_method):
     ...     SomeClass.class_method(3)
     ...     mock_method.assert_called_with(3)
     ...
     >>> test()

'spec'、'create' 和 *note patch.object(): 18bb. 的其他引數與在 *note
patch(): e34. 中的引數具有相同的意義。


File: python.info,  Node: patch dict,  Next: patch multiple,  Prev: patch object,  Up: Patchers

5.26.6.10 patch.dict
....................

 -- 函式: patch.dict (in_dict, values=(), clear=False, **kwargs)

     Patch 字典或類字典的物件，並在測試後將字典回復到其原本的狀態。

     'in_dict' 可以是一個字典或一個類對映的容器。如果它是一個對映，那麼
     它至少必須支援獲取、設定、刪除項目以及對鍵的疊代。

     'in_dict' 也可以是指定字典名稱的字串，然後透過 import 來取得該字典
     。

     'values' 可以是要設定的值的字典。'values' 也可以是 ‘(key, value)’ 對
     (pairs) 的可疊代物件。

     如果 'clear' 為 true，則在設定新值之前字典將被清除。

     也可以使用任意關鍵字引數呼叫 *note patch.dict(): 18f8. 以在字典中設
     定值。

     在 3.8 版的變更: *note patch.dict(): 18f8. 現在在做為情境管理器使用
     時回傳被 patch 的字典。

*note patch.dict(): 18f8. 可以做為情境管理器、裝飾器或類別裝飾器使用：

     >>> foo = {}
     >>> @patch.dict(foo, {'newkey': 'newvalue'})
     ... def test():
     ...     assert foo == {'newkey': 'newvalue'}
     ...
     >>> test()
     >>> assert foo == {}

當作為類別裝飾器使用時，*note patch.dict(): 18f8. 會遵循
‘patch.TEST_PREFIX’（預設為 ‘'test'’）來選擇要包裝的方法：

     >>> import os
     >>> import unittest
     >>> from unittest.mock import patch
     >>> @patch.dict('os.environ', {'newkey': 'newvalue'})
     ... class TestSample(unittest.TestCase):
     ...     def test_sample(self):
     ...         self.assertEqual(os.environ['newkey'], 'newvalue')

如果你想在測試中使用不同的前綴，你可以透過設定 ‘patch.TEST_PREFIX’ 來告
知 patcher 使用不同的前綴。請參閱 *note TEST_PREFIX: 3f03. 以得知如何修
改前綴的更多內容。

*note patch.dict(): 18f8. 可用於在字典中新增成員，或單純地讓測試更改字典
，並確保在測試結束時將字典回復原狀。

     >>> foo = {}
     >>> with patch.dict(foo, {'newkey': 'newvalue'}) as patched_foo:
     ...     assert foo == {'newkey': 'newvalue'}
     ...     assert patched_foo == {'newkey': 'newvalue'}
     ...     # You can add, update or delete keys of foo (or patched_foo, it's the same dict)
     ...     patched_foo['spam'] = 'eggs'
     ...
     >>> assert foo == {}
     >>> assert patched_foo == {}

     >>> import os
     >>> with patch.dict('os.environ', {'newkey': 'newvalue'}):
     ...     print(os.environ['newkey'])
     ...
     newvalue
     >>> assert 'newkey' not in os.environ

可以在 *note patch.dict(): 18f8. 呼叫中使用關鍵字來設定字典中的值：

     >>> mymodule = MagicMock()
     >>> mymodule.function.return_value = 'fish'
     >>> with patch.dict('sys.modules', mymodule=mymodule):
     ...     import mymodule
     ...     mymodule.function('some', 'args')
     ...
     'fish'

*note patch.dict(): 18f8. 可以與實際上不是字典的類字典物件一起使用。最低
限度它們必須支援項目的獲取、設定、刪除以及疊代或隸屬資格檢測。這對應到魔
術方法中的 *note __getitem__(): 266.、*note __setitem__(): 1434.、*note
__delitem__(): 1435. 以及 *note __iter__(): 1bc4. 或 *note
__contains__(): 1e33.。

     >>> class Container:
     ...     def __init__(self):
     ...         self.values = {}
     ...     def __getitem__(self, name):
     ...         return self.values[name]
     ...     def __setitem__(self, name, value):
     ...         self.values[name] = value
     ...     def __delitem__(self, name):
     ...         del self.values[name]
     ...     def __iter__(self):
     ...         return iter(self.values)
     ...
     >>> thing = Container()
     >>> thing['one'] = 1
     >>> with patch.dict(thing, one=2, two=3):
     ...     assert thing['one'] == 2
     ...     assert thing['two'] == 3
     ...
     >>> assert thing['one'] == 1
     >>> assert list(thing) == ['one']


File: python.info,  Node: patch multiple,  Next: patch 方法：啟動與停止,  Prev: patch dict,  Up: Patchers

5.26.6.11 patch.multiple
........................

 -- 函式: patch.multiple (target, spec=None, create=False,
          spec_set=None, autospec=None, new_callable=None, **kwargs)

     在一次呼叫中執行多個 patch。它接受被 patch 的物件（作為物件或透過
     import 取得物件的字串）和 patch 的關鍵字引數：

          with patch.multiple(settings, FIRST_PATCH='one', SECOND_PATCH='two'):
              ...

     如果你想要 *note patch.multiple(): 3f05. 為你建立 mock，請使用
     *note DEFAULT: 3eda. 作為值。在這種情況下，被建立的 mock 會透過關鍵
     字傳遞到被裝飾的函式中，並且當 *note patch.multiple(): 3f05. 作為情
     境管理器時會回傳字典。

     *note patch.multiple(): 3f05. 可以做為裝飾器、類別裝飾器或情境管理
     器使用。引數 'spec'、'spec_set'、'create'、'autospec' 和
     'new_callable' 與在 *note patch(): e34. 中的引數具有相同的意義。這
     些引數將應用於由 *note patch.multiple(): 3f05. 完成的'所有' patch。

     當作為類別裝飾器使用時，*note patch.multiple(): 3f05. 遵循
     ‘patch.TEST_PREFIX’ 來選擇要包裝的方法。

如果你想要 *note patch.multiple(): 3f05. 為你建立 mock，那麼你可以使用
*note DEFAULT: 3eda. 作為值。如果你使用 *note patch.multiple(): 3f05. 作
為裝飾器，那麼被建立的 mock 將透過關鍵字傳遞到被裝飾的函式中。：

     >>> thing = object()
     >>> other = object()

     >>> @patch.multiple('__main__', thing=DEFAULT, other=DEFAULT)
     ... def test_function(thing, other):
     ...     assert isinstance(thing, MagicMock)
     ...     assert isinstance(other, MagicMock)
     ...
     >>> test_function()

*note patch.multiple(): 3f05. 可以與其他 ‘patch’ 裝飾器巢狀使用，但需要
將透過關鍵字傳遞的引數放在 *note patch(): e34. 建立的任何標準引數'之後
'：

     >>> @patch('sys.exit')
     ... @patch.multiple('__main__', thing=DEFAULT, other=DEFAULT)
     ... def test_function(mock_exit, other, thing):
     ...     assert 'other' in repr(other)
     ...     assert 'thing' in repr(thing)
     ...     assert 'exit' in repr(mock_exit)
     ...
     >>> test_function()

如果 *note patch.multiple(): 3f05. 作為情境管理器使用，則情境管理器回傳
的值是一個字典，其中被建立的 mock 會按名稱作為其鍵值：

     >>> with patch.multiple('__main__', thing=DEFAULT, other=DEFAULT) as values:
     ...     assert 'other' in repr(values['other'])
     ...     assert 'thing' in repr(values['thing'])
     ...     assert values['thing'] is thing
     ...     assert values['other'] is other
     ...


File: python.info,  Node: patch 方法：啟動與停止,  Next: patch 內建函式,  Prev: patch multiple,  Up: Patchers

5.26.6.12 patch 方法：啟動與停止
................................

所有的 patcher 都有 ‘start()’ 與 ‘stop()’ 方法。這使得在 ‘setUp’ 方法中
進行 patch 或在你想要在沒有巢狀使用裝飾器或 with 陳述式的情況下進行多個
patch 時變得更簡單。

要使用它們，請像平常一樣呼叫 *note patch(): e34.、*note patch.object():
18bb. 或 *note patch.dict(): 18f8. ，並保留對回傳的 ‘patcher’ 物件的參照
。之後你就可以呼叫 ‘start()’ 將 patch 準備就緒，並呼叫 ‘stop()’ 來取消
patch。

如果你使用 *note patch(): e34. 為你建立 mock，那麼它將透過呼叫
‘patcher.start’ 回傳。：

     >>> patcher = patch('package.module.ClassName')
     >>> from package import module
     >>> original = module.ClassName
     >>> new_mock = patcher.start()
     >>> assert module.ClassName is not original
     >>> assert module.ClassName is new_mock
     >>> patcher.stop()
     >>> assert module.ClassName is original
     >>> assert module.ClassName is not new_mock

一個典型的用法是在一個 ‘TestCase’ 的 ‘setUp’ 方法中執行多個 patch：

     >>> class MyTest(unittest.TestCase):
     ...     def setUp(self):
     ...         self.patcher1 = patch('package.module.Class1')
     ...         self.patcher2 = patch('package.module.Class2')
     ...         self.MockClass1 = self.patcher1.start()
     ...         self.MockClass2 = self.patcher2.start()
     ...
     ...     def tearDown(self):
     ...         self.patcher1.stop()
     ...         self.patcher2.stop()
     ...
     ...     def test_something(self):
     ...         assert package.module.Class1 is self.MockClass1
     ...         assert package.module.Class2 is self.MockClass2
     ...
     >>> MyTest('test_something').run()

     警示: 如果你使用這個技巧，你必須確保透過呼叫 ‘stop’ 來 "取消"
     patch。這可能會比你想像的還要複雜一點，因為如果有例外在 ‘setUp’ 中
     被引發，則 ‘tearDown’ 就不會被呼叫。*note
     unittest.TestCase.addCleanup(): a24. 會讓這稍微簡單一點：

          >>> class MyTest(unittest.TestCase):
          ...     def setUp(self):
          ...         patcher = patch('package.module.Class')
          ...         self.MockClass = patcher.start()
          ...         self.addCleanup(patcher.stop)
          ...
          ...     def test_something(self):
          ...         assert package.module.Class is self.MockClass
          ...

     作為額外的好處，你不再需要保留對 ‘patcher’ 物件的參照。

也可以使用 *note patch.stopall(): 3f08. 來停止所有已啟動的 patch。

 -- 函式: patch.stopall ()

     停止所有運作的 patch。只停止以 ‘start’ 啟動的 patch。


File: python.info,  Node: patch 內建函式,  Next: TEST_PREFIX,  Prev: patch 方法：啟動與停止,  Up: Patchers

5.26.6.13 patch 內建函式
........................

你可以 patch 模組內的任何內建函式。以下範例 patch 內建函式 *note ord():
1de1.：

     >>> @patch('__main__.ord')
     ... def test(mock_ord):
     ...     mock_ord.return_value = 101
     ...     print(ord('c'))
     ...
     >>> test()
     101


File: python.info,  Node: TEST_PREFIX,  Next: 巢狀使用 Patch 裝飾器,  Prev: patch 內建函式,  Up: Patchers

5.26.6.14 TEST_PREFIX
.....................

所有 patcher 都可以作為類別裝飾器使用。以這種方式使用時，它們包裝了類別
上的每個測試方法。Patcher 將 ‘'test'’ 開頭的方法認定為測試方法。這與
*note unittest.TestLoader: 270. 預設尋找測試方法的方式相同。

你可能會想為你的測試使用不同的前綴。你可以透過設定 ‘patch.TEST_PREFIX’ 來
告知 patcher 使用不同的前綴：

     >>> patch.TEST_PREFIX = 'foo'
     >>> value = 3
     >>>
     >>> @patch('__main__.value', 'not three')
     ... class Thing:
     ...     def foo_one(self):
     ...         print(value)
     ...     def foo_two(self):
     ...         print(value)
     ...
     >>>
     >>> Thing().foo_one()
     not three
     >>> Thing().foo_two()
     not three
     >>> value
     3


File: python.info,  Node: 巢狀使用 Patch 裝飾器,  Next: 該 patch 何處,  Prev: TEST_PREFIX,  Up: Patchers

5.26.6.15 巢狀使用 Patch 裝飾器
...............................

如果你想執行多個 patch，那麼你可以簡單地堆疊裝飾器。

你可以使用這個模式來堆疊多個 patch 裝飾器：

     >>> @patch.object(SomeClass, 'class_method')
     ... @patch.object(SomeClass, 'static_method')
     ... def test(mock1, mock2):
     ...     assert SomeClass.static_method is mock1
     ...     assert SomeClass.class_method is mock2
     ...     SomeClass.static_method('foo')
     ...     SomeClass.class_method('bar')
     ...     return mock1, mock2
     ...
     >>> mock1, mock2 = test()
     >>> mock1.assert_called_once_with('foo')
     >>> mock2.assert_called_once_with('bar')

請注意，裝飾器是從底部向上應用的。這是 Python 應用裝飾器的標準方式。被建
立的 mock 傳遞到測試函式中的順序與此順序相同。


File: python.info,  Node: 該 patch 何處,  Next: Patch 描述器與代理物件 Proxy Objects,  Prev: 巢狀使用 Patch 裝飾器,  Up: Patchers

5.26.6.16 該 patch 何處
.......................

*note patch(): e34. 的工作原理是（暫時）將 'name' 指向的物件變更為另一個
物件。可以有許多 name 指向任何單一物件，因此為了使 patch 起作用，你必須
確保你 patch 了被測試系統使用的 name。

基本原則是在物件'被查找'的位置進行 patch，該位置不一定與其被定義的位置相
同。幾個範例將有助於闡明這一點。

想像一下，我們想要測試一個專案，其結構如下：

     a.py
         -> Defines SomeClass

     b.py
         -> from a import SomeClass
         -> some_function instantiates SomeClass

現在我們想要測試 ‘some_function’，但我們想使用 *note patch(): e34. mock
‘SomeClass’。問題是，當我們 import 模組 b 時（我們必須這樣做），它會從模
組 a import ‘SomeClass’。如果我們使用 *note patch(): e34. 來 mock
‘a.SomeClass’，那麼它對我們的測試就不會有任何影響；模組 b 已經有了一個
'真實的' ‘SomeClass’ 的參照 ，看起來我們的 patch 並沒有任何效果。

關鍵是在使用（或查找它）的地方 patch ‘SomeClass’。在這個情況下，
‘some_function’ 實際上會在我們 import 它的模組 b 中查找 ‘SomeClass’。這
裡的 patch 應該長得像這樣：

     @patch('b.SomeClass')

然而，考慮另一種情況，其中模組 b 並不是使用 ‘from a import SomeClass’，
而是 ‘import a’，然後 ‘some_function’ 使用 ‘a.SomeClass’。這兩種 import
形式都很常見。在這種情況下，我們想要 patch 的類別正在其模組中被查找，因
此我們必須 patch ‘a.SomeClass’：

     @patch('a.SomeClass')


File: python.info,  Node: Patch 描述器與代理物件 Proxy Objects,  Prev: 該 patch 何處,  Up: Patchers

5.26.6.17 Patch 描述器與代理物件 (Proxy Objects)
................................................

*note patch: 3eff. 和 *note patch.object: 3f01. 都正確地 patch 和還原描
述器：類別方法、靜態方法以及屬性。你應該在 '類別' 而不是實例上 patch 它
們。它們還可以使用代理屬性存取的'一些'物件，例如 django 設定物件(1)。

   ---------- Footnotes ----------

   (1) 
https://web.archive.org/web/20200603181648/http://www.voidspace.org.uk/python/weblog/arch_d7_2010_12_04.shtml#e1198


File: python.info,  Node: MagicMock 以及魔術方法支援,  Next: 輔助函式<2>,  Prev: Patchers,  Up: unittest mock — mock 物件函式庫

5.26.6.18 MagicMock 以及魔術方法支援
....................................

* Menu:

* Mock 魔術方法::
* Magic Mock::


File: python.info,  Node: Mock 魔術方法,  Next: Magic Mock,  Up: MagicMock 以及魔術方法支援

5.26.6.19 Mock 魔術方法
.......................

*note Mock: 9ef. 支援 mock Python 協定方法，其也被稱作 *note "魔術方法":
3f10.。這允許 mock 物件替換容器或實作 Python 協定的其他物件。

由於魔術方法被查找的方式與一般的方法 (1) 不同，因此專門實作了此支援方式
。這代表著僅有特定的魔術方法被此方式支援。現在已支援清單中已經'幾乎'包含
了所有魔術方法。如果你需要 mock 任何魔術方法而其尚未被支援，請讓我們知道
。

你可以透過將你感興趣的方法設定為函式或 mock 實例來 mock 魔術方法。如果你
使用函式，那麼它'必須'將 ‘self’ 作為第一個引數 (2)。

     >>> def __str__(self):
     ...     return 'fooble'
     ...
     >>> mock = Mock()
     >>> mock.__str__ = __str__
     >>> str(mock)
     'fooble'

     >>> mock = Mock()
     >>> mock.__str__ = Mock()
     >>> mock.__str__.return_value = 'fooble'
     >>> str(mock)
     'fooble'

     >>> mock = Mock()
     >>> mock.__iter__ = Mock(return_value=iter([]))
     >>> list(mock)
     []

一個用法是在 *note with: 577. 陳述式中 mock 作為情境管理器使用的物件：

     >>> mock = Mock()
     >>> mock.__enter__ = Mock(return_value='foo')
     >>> mock.__exit__ = Mock(return_value=False)
     >>> with mock as m:
     ...     assert m == 'foo'
     ...
     >>> mock.__enter__.assert_called_with()
     >>> mock.__exit__.assert_called_with(None, None, None)

對魔術方法的呼叫並不會出現在 *note method_calls: 3ee1. 中，它們會被記錄
在 *note mock_calls: 3edf. 內。

     備註: 如果你使用'spec'關鍵字引數來建立一個 mock，則嘗試設定規格中未
     包含的魔術方法將引發一個 *note AttributeError: 2f6.。

已支援的魔術方法的完整列表是：

   * ‘__hash__’、‘__sizeof__’、 ‘__repr__’ 和 ‘__str__’

   * ‘__dir__’、 ‘__format__’ 和 ‘__subclasses__’

   * ‘__round__’、‘__floor__’、‘__trunc__’ 和 ‘__ceil__’

   * 比較方法：‘__lt__’、‘__gt__’、‘__le__’、‘__ge__’、‘__eq__’ 和
     ‘__ne__’

   * 容器方法：‘__getitem__’、‘__setitem__’、‘__delitem__’、
     ‘__contains__’、‘__len__’、‘__iter__’、‘__reversed__’ 和
     ‘__missing__’

   * 情境管理器：‘__enter__’、‘__exit__’、‘__aenter__’ 和 ‘__aexit__’

   * 一元數值方法：‘__neg__’、‘__pos__’ 和 ‘__invert__’

   * 數值方法（包括右側 (right hand) 和原地 (in-place) 變體）：
     ‘__add__’、‘__sub__’、‘__mul__’、‘__matmul__’、‘__truediv__’、
     ‘__floordiv__’、‘__mod__’、‘__divmod__’、‘__lshift__’、
     ‘__rshift__’、‘__and__’、‘__xor__’、‘__or__’ 和 ‘__pow__’

   * 數值轉換方法：‘__complex__’、‘__int__’、‘__float__’ 和 ‘__index__’

   * 描述器方法：‘__get__’、‘__set__’ 和 ‘__delete__’

   * Pickling：‘__reduce__’、‘__reduce_ex__’、‘__getinitargs__’、
     ‘__getnewargs__’、‘__getstate__’ 和 ‘__setstate__’

   * 檔案系統路徑表示法：‘__fspath__’

   * 非同步疊代方法：‘__aiter__’ 和 ‘__anext__’

在 3.8 版的變更: 新增對於 *note os.PathLike.__fspath__(): bf9. 的支援。

在 3.8 版的變更: 新增對於 ‘__aenter__’、‘__aexit__’、‘__aiter__’ 和
‘__anext__’ 的支援。

以下方法存在，但「不」被支援，因為它們在被 mock 使用時，會無法動態設定，
或可能導致問題：

   * ‘__getattr__’、‘__setattr__’、‘__init__’ 和 ‘__new__’

   * ‘__prepare__’、‘__instancecheck__’、‘__subclasscheck__’、‘__del__’

   ---------- Footnotes ----------

   (1) 魔術方法'應該'在類別而不是實例上被查找。不同版本的 Python 對於這
條規則的適用並不一致。支援的協定方法應適用於所有支援的 Python 版本。

   (2) 該函式基本上與類別掛鉤，但每個 ‘Mock’ 實例都與其他實例保持隔離。


File: python.info,  Node: Magic Mock,  Prev: Mock 魔術方法,  Up: MagicMock 以及魔術方法支援

5.26.6.20 Magic Mock
....................

‘MagicMock’ 有兩個變體：*note MagicMock: e33. 和 *note
NonCallableMagicMock: 3ed8.。

 -- 類別: unittest.mock.MagicMock (*args, **kw)

     ‘MagicMock’ 是 *note Mock: 9ef. 的子類別，其預設具有大多數*note
     魔術方法: 3f10.的實作。你可以使用 ‘MagicMock’，而無需自行配置魔術方
     法。

     建構函式參數的意義與 *note Mock: 9ef. 中的參數相同。

     如果你使用 'spec' 或 'spec_set' 引數，那麼'只有'規格中存在的魔術方
     法會被建立。

 -- 類別: unittest.mock.NonCallableMagicMock (*args, **kw)

     *note MagicMock: e33. 的不可呼叫版本。

     建構函式參數的意義與 *note MagicMock: e33. 中的參數相同，但
     'return_value' 和 'side_effect' 除外，它們對不可呼叫的 mock 來說沒
     有任何意義。

魔術方法是使用 *note MagicMock: e33. 物件設定的，因此你可以配置它們並以
一般的方法來使用它們：

     >>> mock = MagicMock()
     >>> mock[3] = 'fish'
     >>> mock.__setitem__.assert_called_with(3, 'fish')
     >>> mock.__getitem__.return_value = 'result'
     >>> mock[2]
     'result'

預設情況下，許多協定方法都需要回傳特定種類的物件。這些方法預先配置了預設
回傳值，因此如果你對回傳值不感興趣，則無需執行任何操作即可使用它們。如果
你想更改預設值，你仍然可以手動'設定'回傳值。

方法及其預設值：

   * ‘__lt__’：*note NotImplemented: 776.

   * ‘__gt__’：‘NotImplemented’

   * ‘__le__’：‘NotImplemented’

   * ‘__ge__’：‘NotImplemented’

   * ‘__int__’：‘1’

   * ‘__contains__’：‘False’

   * ‘__len__’：‘0’

   * ‘__iter__’：‘iter([])’

   * ‘__exit__’：‘False’

   * ‘__aexit__’：‘False’

   * ‘__complex__’：‘1j’

   * ‘__float__’：‘1.0’

   * ‘__bool__’：‘True’

   * ‘__index__’：‘1’

   * ‘__hash__’：mock 的預設雜湊

   * ‘__str__’：mock 的預設字串

   * ‘__sizeof__’：mock 的預設 sizeof

舉例來說：

     >>> mock = MagicMock()
     >>> int(mock)
     1
     >>> len(mock)
     0
     >>> list(mock)
     []
     >>> object() in mock
     False

‘__eq__()’ 和 ‘__ne__()’ 這兩個相等的方法是特別的。它們使用 *note
side_effect: 3ed9. 屬性對識別性 (identity) 進行預設的相等比較，除非你變
更它們的回傳值以回傳其他內容：

     >>> MagicMock() == 3
     False
     >>> MagicMock() != 3
     True
     >>> mock = MagicMock()
     >>> mock.__eq__.return_value = True
     >>> mock == 3
     True

‘MagicMock.__iter__()’ 的回傳值可以是任何可疊代物件，且不需是一個疊代器
：

     >>> mock = MagicMock()
     >>> mock.__iter__.return_value = ['a', 'b', 'c']
     >>> list(mock)
     ['a', 'b', 'c']
     >>> list(mock)
     ['a', 'b', 'c']

如果回傳值'是'一個疊代器，那麼對其進行一次疊代將消耗它，並且後續疊代將產
生一個空串列：

     >>> mock.__iter__.return_value = iter(['a', 'b', 'c'])
     >>> list(mock)
     ['a', 'b', 'c']
     >>> list(mock)
     []

‘MagicMock’ 配置了所有支援的魔術方法，除了一些少見和過時的方法。如果你想
要，你仍然可以設定這些魔術方法。

‘MagicMock’ 中支援但預設未設置的魔術方法包含：

   * ‘__subclasses__’

   * ‘__dir__’

   * ‘__format__’

   * ‘__get__’、‘__set__’ 和 ‘__delete__’

   * ‘__reversed__’ 和 ‘__missing__’

   * ‘__reduce__’、‘__reduce_ex__’、‘__getinitargs__’、
     ‘__getnewargs__’、‘__getstate__’ 和 ‘__setstate__’

   * ‘__getformat__’


File: python.info,  Node: 輔助函式<2>,  Next: side_effect、return_value 和 wraps 的優先順序,  Prev: MagicMock 以及魔術方法支援,  Up: unittest mock — mock 物件函式庫

5.26.6.21 輔助函式
..................

* Menu:

* sentinel（哨兵）::
* DEFAULT::
* call::
* create_autospec::
* ANY::
* FILTER_DIR::
* mock_open::
* Autospeccing（自動規格）::
* 密封 mock::


File: python.info,  Node: sentinel（哨兵）,  Next: DEFAULT,  Up: 輔助函式<2>

5.26.6.22 sentinel（哨兵）
..........................

 -- 資料: unittest.mock.sentinel

     ‘哨兵’物件提供了一種為你的測試提供獨特物件的便利方式。

     當你使用名稱存取屬性時，屬性會根據需要被建立。存取相同的屬性將始終
     回傳相同的物件。回傳的物件會具有合適的 repr，讓測試失敗的訊息是可閱
     讀的。

     在 3.7 版的變更: ‘哨兵’屬性現在當被*note 複製: 1e.或*note 序列化:
     95.時會保留其識別性。

在測試時，有時你需要測試特定物件是否作為引數被傳遞給另一個方法或回傳。建
立命名的哨兵物件來測試這一點是常見的。*note sentinel: b47. 提供了一種此
類建立和測試物件識別性的便利方式。

在這個例子中，我們 monkey patch ‘method’ 以回傳 ‘sentinel.some_object’：

     >>> real = ProductionClass()
     >>> real.method = Mock(name="method")
     >>> real.method.return_value = sentinel.some_object
     >>> result = real.method()
     >>> assert result is sentinel.some_object
     >>> result
     sentinel.some_object


File: python.info,  Node: DEFAULT,  Next: call,  Prev: sentinel（哨兵）,  Up: 輔助函式<2>

5.26.6.23 DEFAULT
.................

 -- 資料: unittest.mock.DEFAULT

     *note DEFAULT: 3eda. 物件是一個預先建立的哨兵（實際上是
     ‘sentinel.DEFAULT’）。它可以被 *note side_effect: 3ed9. 函式使用來
     表示正常的回傳值應該被使用。


File: python.info,  Node: call,  Next: create_autospec,  Prev: DEFAULT,  Up: 輔助函式<2>

5.26.6.24 call
..............

 -- 函式: unittest.mock.call (*args, **kwargs)

     與 *note call_args: 1884.、*note call_args_list: 3ee7.、*note
     mock_calls: 3edf. 和 *note method_calls: 3ee1. 相比，*note call():
     18d3. 是一個用於進行更簡單的斷言的輔助物件。*note call(): 18d3. 也
     可以與 *note assert_has_calls(): 15a0. 一起使用。

          >>> m = MagicMock(return_value=None)
          >>> m(1, 2, a='foo', b='bar')
          >>> m()
          >>> m.call_args_list == [call(1, 2, a='foo', b='bar'), call()]
          True

 -- 方法: call.call_list ()

     對於表示多個呼叫的 call 物件，*note call_list(): 3f16. 回傳所有中間
     呼叫以及最終呼叫的串列。

‘call_list’ 在對「鍊接呼叫 (chained calls)」進行斷言時特別有用。鍊接呼叫
是在單行程式碼進行的多次呼叫。這會導致 mock 上的 *note mock_calls: 3edf.
中出現多個項目。手動建構呼叫序列會相當單調乏味。

*note call_list(): 3f16. 可以從同一個鍊接呼叫建構呼叫序列：

     >>> m = MagicMock()
     >>> m(1).method(arg='foo').other('bar')(2.0)
     <MagicMock name='mock().method().other()()' id='...'>
     >>> kall = call(1).method(arg='foo').other('bar')(2.0)
     >>> kall.call_list()
     [call(1),
      call().method(arg='foo'),
      call().method().other('bar'),
      call().method().other()(2.0)]
     >>> m.mock_calls == kall.call_list()
     True
取決於它的建構方式，一個 ‘call’ 物件會是（位置引數, 關鍵字引數）的元組，
或是 (名稱, 位置引數, 關鍵字引數) 的元組。當你自己建構它們時，這並不是那
麼有趣，但是 *note Mock.call_args: 1884.、*note Mock.call_args_list:
3ee7. 和 *note Mock.mock_calls: 3edf. 屬性中的 ‘call’ 物件可以被內省以取
得它們包含的各個引數。

*note Mock.call_args: 1884. 和 *note Mock.call_args_list: 3ee7. 中的
‘call’ 物件是（位置引數, 關鍵字引數）的二元組，而 *note Mock.mock_calls:
3edf. 中的 ‘call’ 物件以及你自己建立的 ‘call’ 物件是（名稱, 位置引數, 關
鍵字引數）的三元組。

你可以利用它們作為元組的特性來提取單個引數，以進行更複雜的內省和斷言。位
置引數是一個元組（如果沒有位置引數則為空元組），關鍵字引數是一個字典：

     >>> m = MagicMock(return_value=None)
     >>> m(1, 2, 3, arg='one', arg2='two')
     >>> kall = m.call_args
     >>> kall.args
     (1, 2, 3)
     >>> kall.kwargs
     {'arg': 'one', 'arg2': 'two'}
     >>> kall.args is kall[0]
     True
     >>> kall.kwargs is kall[1]
     True

     >>> m = MagicMock()
     >>> m.foo(4, 5, 6, arg='two', arg2='three')
     <MagicMock name='mock.foo()' id='...'>
     >>> kall = m.mock_calls[0]
     >>> name, args, kwargs = kall
     >>> name
     'foo'
     >>> args
     (4, 5, 6)
     >>> kwargs
     {'arg': 'two', 'arg2': 'three'}
     >>> name is m.mock_calls[0][0]
     True


File: python.info,  Node: create_autospec,  Next: ANY,  Prev: call,  Up: 輔助函式<2>

5.26.6.25 create_autospec
.........................

 -- 函式: unittest.mock.create_autospec (spec, spec_set=False,
          instance=False, **kwargs)

     使用另一個物件作為規格建立一個 mock 物件。Mock 上的屬性將使用
     'spec' 物件上的對應屬性作為其規格。

     被 mock 的函式或方法將檢查其引數，以確保他們被使用正確的簽名來呼叫
     。

     如果 'spec_set' 為 ‘True’，則嘗試設定規格物件上不存在的屬性將引發
     *note AttributeError: 2f6.。

     如果一個類別作為規格使用，則 mock（該類別的實例）的回傳值將具有相同
     的規格。你可以透過傳遞 ‘instance=True’ 來使用一個類別作為一個實例物
     件的規格。只有當 mock 的實例是可呼叫物件時，回傳的 mock 才會是可呼
     叫物件。

     *note create_autospec(): 14fb. 也接受任意的關鍵字引數，這些引數會傳
     遞給已建立的 mock 的建構函式。

請參閱 *note Autospeccing（自動規格）: 3ed5. 以得知如何以 *note
create_autospec(): 14fb. 使用自動規格以及如何在 *note patch(): e34. 中使
用 'autospec' 引數的範例。

在 3.8 版的變更: 如果目標是一個非同步函式，*note create_autospec():
14fb. 現在會回傳一個 *note AsyncMock: 9ee.。


File: python.info,  Node: ANY,  Next: FILTER_DIR,  Prev: create_autospec,  Up: 輔助函式<2>

5.26.6.26 ANY
.............

 -- 資料: unittest.mock.ANY

有時你可能需要對 mock 的呼叫中的'某些'引數進行斷言，但你不在意其他的某些
引數，或想將它們單獨從 *note call_args: 1884. 中取出並進行更加複雜的斷言
。

要忽略某些引數，你可以傳入對'所有物件'來說都相等的物件。那麼無論傳入什麼
內容，對 ‘assert_used_with()’ 和 ‘assert_used_once_with()’ 的呼叫都會成
功。

     >>> mock = Mock(return_value=None)
     >>> mock('foo', bar=object())
     >>> mock.assert_called_once_with('foo', bar=ANY)

*note ANY: 18d1. 也可以用來與呼叫串列進行比較，例如 *note mock_calls:
3edf.：

     >>> m = MagicMock(return_value=None)
     >>> m(1)
     >>> m(1, 2)
     >>> m(object())
     >>> m.mock_calls == [call(1), call(1, 2), ANY]
     True

*note ANY: 18d1. 不只能與呼叫物件比較，其也可以在測試斷言中使用：

     class TestStringMethods(unittest.TestCase):

         def test_split(self):
             s = 'hello world'
             self.assertEqual(s.split(), ['hello', ANY])


File: python.info,  Node: FILTER_DIR,  Next: mock_open,  Prev: ANY,  Up: 輔助函式<2>

5.26.6.27 FILTER_DIR
....................

 -- 資料: unittest.mock.FILTER_DIR

*note FILTER_DIR: 3ee3. 是一個模組級別的變數，用於控制 mock 物件回應
*note dir(): 5d8. 的方式。其預設值為 ‘True’，它使用以下描述的過濾方式來
只顯示有用的成員。如果你不喜歡這個過濾方式，或由於診斷意圖而需要將其關閉
，請設定 ‘mock.FILTER_DIR = False’。

當過濾方式開啟時，‘dir(some_mock)’ 僅會顯示有用的屬性，並將包括通常不會
顯示的任何動態建立的屬性。如果 mock 是使用 'spec'（或 'autospec'）來建立
的，那麼源頭的所有屬性都會顯示，即使它們尚未被存取：

     >>> dir(Mock())
     ['assert_any_call',
      'assert_called',
      'assert_called_once',
      'assert_called_once_with',
      'assert_called_with',
      'assert_has_calls',
      'assert_not_called',
      'attach_mock',
      ...
     >>> from urllib import request
     >>> dir(Mock(spec=request))
     ['AbstractBasicAuthHandler',
      'AbstractDigestAuthHandler',
      'AbstractHTTPHandler',
      'BaseHandler',
      ...

許多不是很有用的（對 *note Mock: 9ef. 來說是私有的，而不是被 mock 的東西
）底線和雙底線前綴屬性已從在 *note Mock: 9ef. 上呼叫 *note dir(): 5d8. 的
結果中濾除。如果你不喜歡這種特性，可以透過設定模組級別開關 *note
FILTER_DIR: 3ee3. 來將其關閉：

     >>> from unittest import mock
     >>> mock.FILTER_DIR = False
     >>> dir(mock.Mock())
     ['_NonCallableMock__get_return_value',
      '_NonCallableMock__get_side_effect',
      '_NonCallableMock__return_value_doc',
      '_NonCallableMock__set_return_value',
      '_NonCallableMock__set_side_effect',
      '__call__',
      '__class__',
      ...

或者，你可以只使用 ‘vars(my_mock)’（實例成員）和 ‘dir(type(my_mock))’（
型別成員）來略過過濾，而不考慮 ‘mock.FILTER_DIR’。


File: python.info,  Node: mock_open,  Next: Autospeccing（自動規格）,  Prev: FILTER_DIR,  Up: 輔助函式<2>

5.26.6.28 mock_open
...................

 -- 函式: unittest.mock.mock_open (mock=None, read_data=None)

     用於建立取代 *note open(): 4c0. 用途的 mock 的輔助函式。它適用於直
     接呼叫或用作情境管理器的 *note open(): 4c0.。

     'mock' 引數是要配置的 mock 物件。如果其為 ‘None’（預設值），那麼就
     會為你建立一個 *note MagicMock: e33.，其 API 限制在標準檔案處理上可
     用的方法或屬性。

     'read_data' 是檔案處理方法 ‘read()’、*note readline(): 12bd. 和
     *note readlines(): 2211. 的回傳字串。對這些方法的呼叫將從
     'read_data' 取得資料，直到資料耗盡。對這些方法的 mock 非常單純：每
     次呼叫 'mock' 時，'read_data' 都會倒回到起點。如果你需要對提供給測
     試程式碼的資料進行更多控制，你會需要自行客製化這個 mock。如果這樣還
     不夠，PyPI(1) 上的其中一個記憶體內檔案系統 (in-memory filesystem) 套
     件可以提供用於測試的真實檔案系統。

     在 3.4 版的變更: 新增對 *note readline(): 12bd. 和 *note
     readlines(): 2211. 的支援。‘read()’ 的 mock 更改為消耗 'read_data'
     而不是在每次呼叫時回傳它。

     在 3.5 版的變更: 現在，每次呼叫 'mock' 時都會重置 'read_data'。

     在 3.8 版的變更: 新增 *note __iter__(): 1bc4. 到實作中，以便使疊代
     （例如在 for 迴圈中）正確地消耗 'read_data'。

使用 *note open(): 4c0. 作為情境管理器是確保檔案處理正確關閉的好方式，且
這種方式正在變得普遍：

     with open('/some/path', 'w') as f:
         f.write('something')

問題是，即使你 mock 了對 *note open(): 4c0. 的呼叫，它也是作為情境管理器
使用的'回傳物件'（且其 *note __enter__(): 56c. 和 ‘__exit__()’ 已被呼叫
）。

使用 *note MagicMock: e33. mock 情境管理器相當常見並且精細，因此輔助函式
就非常有用：

     >>> m = mock_open()
     >>> with patch('__main__.open', m):
     ...     with open('foo', 'w') as h:
     ...         h.write('some stuff')
     ...
     >>> m.mock_calls
     [call('foo', 'w'),
      call().__enter__(),
      call().write('some stuff'),
      call().__exit__(None, None, None)]
     >>> m.assert_called_once_with('foo', 'w')
     >>> handle = m()
     >>> handle.write.assert_called_once_with('some stuff')

以及讀取檔案：

     >>> with patch('__main__.open', mock_open(read_data='bibble')) as m:
     ...     with open('foo') as h:
     ...         result = h.read()
     ...
     >>> m.assert_called_once_with('foo')
     >>> assert result == 'bibble'

   ---------- Footnotes ----------

   (1) https://pypi.org


File: python.info,  Node: Autospeccing（自動規格）,  Next: 密封 mock,  Prev: mock_open,  Up: 輔助函式<2>

5.26.6.29 Autospeccing（自動規格）
..................................

自動規格以 mock 現有的 ‘spec’ 功能作為基礎。它將 mock 的 api 限制為原始
物件（規格）的 api，但它是遞迴的（惰性 (lazily) 實現），因此 mock 的屬性
僅具有與規格的屬性相同的 api。此外，被 mock 的函式/方法具有與原始的函式
/方法相同的呼叫簽名，因此如果它們被不正確地呼叫，就會引發 *note
TypeError: 4dd.。

在解釋自動規格如何運作之前，我們先解釋為什麼需要它。

*note Mock: 9ef. 是一個非常強大且靈活的物件，但它有一個常見的 mock 缺陷
。如果你重構某些程式碼或重新命名成員等，則任何仍然使用'舊 api' 但使用
mock 而非真實物件的程式碼測試仍然會通過。這意味著即使你的程式碼壞了，但
測試仍可以全部通過。

在 3.5 版的變更: 在 3.5 之前，當測試應該引發錯誤時，斷言單字中存在拼字錯
誤的測驗會默默地通過。你仍可以透過將 ‘unsafe=True’ 傳遞給 Mock 來實作此
行為。

謹記這是你需要有整合測試和單元測試的另一個原因。單獨測試所有內容都很好，
但如果你不測試你的單元是如何「連接在一起」的，那麼測試還是有機會發現很多
錯誤。

‘mock’ 已經提供了一個功能來幫助解決這個問題，其稱為 speccing。如果你使用
類別或實例作為 mock 的 ‘spec’，那麼你在 mock 上只能存取真實類別中存在的
屬性：

     >>> from urllib import request
     >>> mock = Mock(spec=request.Request)
     >>> mock.assret_called_with  # Intentional typo!
     Traceback (most recent call last):
      ...
     AttributeError: Mock object has no attribute 'assret_called_with'

該規格僅適用於 mock 本身，因此在 mock 上的任何方法仍然有相同的問題：

     >>> mock.has_data()
     <mock.Mock object at 0x...>
     >>> mock.has_data.assret_called_with()  # 故意的錯字！

自動規格解決了這個問題。你可以將 ‘autospec=True’ 傳遞給 *note patch():
e34. / *note patch.object(): 18bb. 或使用 *note create_autospec(): 14fb.
函式建立帶有規格的 mock。如果你對 *note patch(): e34. 使用
‘autospec=True’ 引數，則被取代的物件將作為規格物件使用。因為規格是「惰性
」完成的（規格是在 mock 被存取時作為屬性被建立的），所以你可以將它與非常
複雜或深度巢狀使用的物件（例如連續引用的模組）一起使用，而不會過於影響性
能。

這是一個正在使用的例子：

     >>> from urllib import request
     >>> patcher = patch('__main__.request', autospec=True)
     >>> mock_request = patcher.start()
     >>> request is mock_request
     True
     >>> mock_request.Request
     <MagicMock name='request.Request' spec='Request' id='...'>

你可以看到 ‘request.Request’ 有一個規格。‘request.Request’ 在建構函式中
接受兩個引數（其中之一是 'self'）。如果我們錯誤地呼叫它，會發生以下情況
：

     >>> req = request.Request()
     Traceback (most recent call last):
      ...
     TypeError: <lambda>() takes at least 2 arguments (1 given)

此規格也適用於實例化的類別（即有規格的 mock 的回傳值）：

     >>> req = request.Request('foo')
     >>> req
     <NonCallableMagicMock name='request.Request()' spec='Request' id='...'>

‘Request’ 物件不是可呼叫物件，因此實例化我們 mock out 的
‘request.Request’ 的回傳值是不可呼叫的 mock。規格到位後，斷言中的任何拼
字錯誤都會引發正確的錯誤：

     >>> req.add_header('spam', 'eggs')
     <MagicMock name='request.Request().add_header()' id='...'>
     >>> req.add_header.assret_called_with  # Intentional typo!
     Traceback (most recent call last):
      ...
     AttributeError: Mock object has no attribute 'assret_called_with'
     >>> req.add_header.assert_called_with('spam', 'eggs')

在許多情況下，你只需要將 ‘autospec=True’ 新增至現有的 *note patch():
e34. 呼叫中，然後就可以防止因拼字錯誤和 api 變更而導致的錯誤。

除了透過 *note patch(): e34. 使用 'autospec' 之外，還有一個 *note
create_autospec(): 14fb. 用於直接建立有自動規格的 mock：

     >>> from urllib import request
     >>> mock_request = create_autospec(request)
     >>> mock_request.Request('foo', 'bar')
     <NonCallableMagicMock name='mock.Request()' spec='Request' id='...'>

然而，這並非完全沒有限制，這就是為什麼它不是預設的行為。為了理解規格物件
上有哪些可用屬性，autospec 必須內省（存取屬性）規格。當你遍歷 mock 上的
屬性時，原始物件的對應遍歷正在默默發生。如果你的規格物件具有可以觸發程式
碼執行的屬性或描述器，那麼你可能無法使用 autospec。換句話說，設計你的物
件讓內省是安全的 (1) 會比較好。

一個更嚴重的問題是，在 *note __init__(): 655. 方法中建立實例屬性是常見的
，而其根本不存在於類別中。'autospec' 無法知道任何動態建立的屬性，並將
api 限制為可見的屬性。：

     >>> class Something:
     ...   def __init__(self):
     ...     self.a = 33
     ...
     >>> with patch('__main__.Something', autospec=True):
     ...   thing = Something()
     ...   thing.a
     ...
     Traceback (most recent call last):
       ...
     AttributeError: Mock object has no attribute 'a'

有幾種不同的方法可以解決這個問題。最簡單但可能有點煩人的方法是在建立後簡
單地在 mock 上設定所需的屬性。因為雖然 'autospec' 不允許你取得規格中不存
在的屬性，但是它不會阻止你設定它們：

     >>> with patch('__main__.Something', autospec=True):
     ...   thing = Something()
     ...   thing.a = 33
     ...

'spec' 和 'autospec' 有一個更激進的版本，它會'確實地'阻止你設定不存在的
屬性。如果你想確保你的程式碼僅能'設定'有效的屬性，那麼這會很有用，但顯然
它也順便阻止了這個特殊情況：

     >>> with patch('__main__.Something', autospec=True, spec_set=True):
     ...   thing = Something()
     ...   thing.a = 33
     ...
     Traceback (most recent call last):
      ...
     AttributeError: Mock object has no attribute 'a'

解決問題的最佳方法可能是新增類別屬性作為在 *note __init__(): 655. 中初始
化的實例成員的預設值。請注意，如果你僅在 ‘__init__()’ 中設定預設屬性，那
麼透過類別屬性（當然在實例之間共用）提供它們也會更快。例如：

     class Something:
         a = 33

這就帶來了另一個問題。為稍後將成為不同型別的物件的成員提供預設值 ‘None’
是相對常見的。‘None’ 作為規格是無用的，因為它不允許你存取其上的'任何'屬
性或方法。由於 ‘None’ 作為規格'永遠不會'有用，並且可能表示通常屬於其他型
別的成員，因此自動規格不會對設定為 ‘None’ 的成員使用規格。這些會只是普通
的 mock（通常是 MagicMocks）：

     >>> class Something:
     ...     member = None
     ...
     >>> mock = create_autospec(Something)
     >>> mock.member.foo.bar.baz()
     <MagicMock name='mock.member.foo.bar.baz()' id='...'>

如果修改正式生產 (production) 類別以新增預設值不符合你的喜好，那麼還有更
多選擇。其中之一就是簡單地使用實例作為規格而不是使用類別。另一種是建立一
個正式生產類別的子類別，並將預設值新增至子類別中，而不影響正式生產類別。
這兩個都需要你使用替代物件作為規格。值得慶幸的是 *note patch(): e34. 支
援這一點 - 你可以簡單地將替代物件作為 'autospec' 引數傳遞：

     >>> class Something:
     ...   def __init__(self):
     ...     self.a = 33
     ...
     >>> class SomethingForTest(Something):
     ...   a = 33
     ...
     >>> p = patch('__main__.Something', autospec=SomethingForTest)
     >>> mock = p.start()
     >>> mock.a
     <NonCallableMagicMock name='Something.a' spec='int' id='...'>

   ---------- Footnotes ----------

   (1) 這只適用於類別或已經實例化的物件。呼叫一個被 mock 的類別來建立一
個 mock 實例'不會'建立真的實例。它僅查找屬性及對 *note dir(): 5d8. 的呼
叫。


File: python.info,  Node: 密封 mock,  Prev: Autospeccing（自動規格）,  Up: 輔助函式<2>

5.26.6.30 密封 mock
...................

 -- 函式: unittest.mock.seal (mock)

     當存取被密封的 mock 的屬性或其任何已經遞迴 mock 的屬性時，seal 將停
     用 mock 的自動建立。

     如果將具有名稱或規格的 mock 實例指派給屬性，則不會出現在密封鏈中。
     這表示可藉由固定 mock 物件的一部分來防止密封。：

          >>> mock = Mock()
          >>> mock.submock.attribute1 = 2
          >>> mock.not_submock = mock.Mock(name="sample_name")
          >>> seal(mock)
          >>> mock.new_attribute  # This will raise AttributeError.
          >>> mock.submock.attribute2  # This will raise AttributeError.
          >>> mock.not_submock.attribute2  # This won't raise.

     在 3.7 版被加入.


File: python.info,  Node: side_effect、return_value 和 wraps 的優先順序,  Prev: 輔助函式<2>,  Up: unittest mock — mock 物件函式庫

5.26.6.31 ‘side_effect’、‘return_value’ 和 'wraps' 的優先順序
.............................................................

它們的優先順序是：

  1. *note side_effect: 3ed9.

  2. *note return_value: 3edb.

  3. 'wraps'

如果這三個都有設定，mock 將會回傳來自 *note side_effect: 3ed9. 的值，並
忽略 *note return_value: 3edb. 和被包裝物件。如果設定了任兩項，則優先順
序較高的一項將回傳該值。無論先設定哪個順序，優先順序都保持不變。

     >>> from unittest.mock import Mock
     >>> class Order:
     ...     @staticmethod
     ...     def get_value():
     ...         return "third"
     ...
     >>> order_mock = Mock(spec=Order, wraps=Order)
     >>> order_mock.get_value.side_effect = ["first"]
     >>> order_mock.get_value.return_value = "second"
     >>> order_mock.get_value()
     'first'

由於 ‘None’ 是 *note side_effect: 3ed9. 的預設值，如果將其值重新賦值回為
‘None’，則會檢查 *note return_value: 3edb. 和被包裝物件之間的優先順序，
忽略 *note side_effect: 3ed9.。

     >>> order_mock.get_value.side_effect = None
     >>> order_mock.get_value()
     'second'

如果 *note side_effect: 3ed9. 回傳的值是 *note DEFAULT: 3eda.，它將被忽
略，並且優先順序被移動到後面一個以獲得要回傳的值。

     >>> from unittest.mock import DEFAULT
     >>> order_mock.get_value.side_effect = [DEFAULT]
     >>> order_mock.get_value()
     'second'

當 *note Mock: 9ef. 包裝一個物件時，*note return_value: 3edb. 的預設值將
為 *note DEFAULT: 3eda.。

     >>> order_mock = Mock(spec=Order, wraps=Order)
     >>> order_mock.return_value
     sentinel.DEFAULT
     >>> order_mock.get_value.return_value
     sentinel.DEFAULT

優先順序將忽略該值，並將移動到最後一個，即被包裝物件。

當對被包裝物件進行真正的呼叫時，建立此 mock 的實例將回傳該類別的真實實例
。必須傳遞被包裝物件所需的位置引數（如果存在）。

     >>> order_mock_instance = order_mock()
     >>> isinstance(order_mock_instance, Order)
     True
     >>> order_mock_instance.get_value()
     'third'

     >>> order_mock.get_value.return_value = DEFAULT
     >>> order_mock.get_value()
     'third'

     >>> order_mock.get_value.return_value = "second"
     >>> order_mock.get_value()
     'second'

但如果你為其賦予 ‘None’ 則不會被忽略，因為它是明確賦值。因此，優先順序不
會移至被包裝物件。

     >>> order_mock.get_value.return_value = None
     >>> order_mock.get_value() is None
     True

即使你在初始化 mock 時同時設定所有三個，優先順序也保持不變：

     >>> order_mock = Mock(spec=Order, wraps=Order,
     ...                   **{"get_value.side_effect": ["first"],
     ...                      "get_value.return_value": "second"}
     ...                   )
     ...
     >>> order_mock.get_value()
     'first'
     >>> order_mock.get_value.side_effect = None
     >>> order_mock.get_value()
     'second'
     >>> order_mock.get_value.return_value = DEFAULT
     >>> order_mock.get_value()
     'third'

如果 *note side_effect: 3ed9. 已耗盡，則優先順序將不會使值由後面取得。相
反地這會引發 ‘StopIteration’ 例外。

     >>> order_mock = Mock(spec=Order, wraps=Order)
     >>> order_mock.get_value.side_effect = ["first side effect value",
     ...                                     "another side effect value"]
     >>> order_mock.get_value.return_value = "second"

     >>> order_mock.get_value()
     'first side effect value'
     >>> order_mock.get_value()
     'another side effect value'

     >>> order_mock.get_value()
     Traceback (most recent call last):
      ...
     StopIteration


File: python.info,  Node: unittest mock --- 入門指南,  Next: test --- Python 的回歸測試 regression tests 套件,  Prev: unittest mock — mock 物件函式庫,  Up: 開發工具

5.26.7 ‘unittest.mock’ -- 入門指南
----------------------------------

在 3.3 版被加入.

* Menu:

* 使用 Mock 的方式::
* Patch 裝飾器::
* 更多範例::


File: python.info,  Node: 使用 Mock 的方式,  Next: Patch 裝飾器,  Up: unittest mock --- 入門指南

5.26.7.1 使用 Mock 的方式
.........................

* Menu:

* 使用 Mock 來 patching 方法::
* 對物件的方法呼叫使用 mock::
* Mock 類別: Mock 類別<2>.
* 命名你的 mock::
* 追蹤所有呼叫::
* 設定回傳值和屬性::
* 透過 mock 引發例外::
* Side effect 函式以及可疊代物件::
* Mock 非同步可疊代物件::
* Mock 非同步情境管理器::
* 從現有物件建立 mock::
* 使用 side_effect 回傳各別檔案內容::


File: python.info,  Node: 使用 Mock 來 patching 方法,  Next: 對物件的方法呼叫使用 mock,  Up: 使用 Mock 的方式

5.26.7.2 使用 Mock 來 patching 方法
...................................

*note Mock: 9ef. 物件的常見用法包含：

   * Patching 方法

   * 記錄在物件上的方法呼叫

你可能會想要取代一個物件上的方法，以便檢查系統的另一部分是否使用正確的引
數呼叫它：

     >>> real = SomeClass()
     >>> real.method = MagicMock(name='method')
     >>> real.method(3, 4, 5, key='value')
     <MagicMock name='method()' id='...'>

一旦我們的 mock 已經被使用（例如在這個範例中的 ‘real.method’），它就有了
方法和屬性，允許你對其使用方式進行斷言 (assertions)。

     備註: 在大多數的範例中，*note Mock: 9ef. 和 *note MagicMock: e33. 類
     別是可以互換的。不過由於 ‘MagicMock’ 是功能更強大的類別，因此通常它
     是一個更好的選擇。

一旦 mock 被呼叫，它的 *note called: 3ee5. 屬性將被設定為 ‘True’。更重要
的是，我們可以使用 *note assert_called_with(): 1927. 或 *note
assert_called_once_with(): 3edd. 方法來檢查它是否被使用正確的引數來呼叫
。

這個範例測試呼叫 ‘ProductionClass().method’ 是否導致對 ‘something’ 方法
的呼叫：

     >>> class ProductionClass:
     ...     def method(self):
     ...         self.something(1, 2, 3)
     ...     def something(self, a, b, c):
     ...         pass
     ...
     >>> real = ProductionClass()
     >>> real.something = MagicMock()
     >>> real.method()
     >>> real.something.assert_called_once_with(1, 2, 3)


File: python.info,  Node: 對物件的方法呼叫使用 mock,  Next: Mock 類別<2>,  Prev: 使用 Mock 來 patching 方法,  Up: 使用 Mock 的方式

5.26.7.3 對物件的方法呼叫使用 mock
..................................

在上一個範例中，我們直接對物件上的方法進行 patch，以檢查它是否被正確呼叫
。另一個常見的用法是將一個物件傳遞給一個方法（或受測系統的某一部分），然
後檢查它是否以正確的方式被使用。

下面是一個單純的 ‘ProductionClass’，含有一個 ‘closer’ 方法。如果它被傳入
一個物件，它就會呼叫此物件中的 ‘close’。

     >>> class ProductionClass:
     ...     def closer(self, something):
     ...         something.close()
     ...

因此，為了對此進行測試，我們需要傳遞一個具有 ‘close’ 方法的物件，並檢查
它是否被正確的呼叫。

     >>> real = ProductionClass()
     >>> mock = Mock()
     >>> real.closer(mock)
     >>> mock.close.assert_called_with()

我們不必做任何額外的事情來為 mock 提供 'close' 方法，存取 close 會建立它
。因此，如果 'close' 並未被呼叫過，在測試中存取 'close' 就會建立它，但
*note assert_called_with(): 1927. 就會引發一個失敗的例外。


File: python.info,  Node: Mock 類別<2>,  Next: 命名你的 mock,  Prev: 對物件的方法呼叫使用 mock,  Up: 使用 Mock 的方式

5.26.7.4 Mock 類別
..................

一個常見的使用案例是在測試的時候 mock 被程式碼實例化的類別。當你 patch 一
個類別時，該類別就會被替換為 mock。實例是透過'呼叫類別'建立的。這代表你
可以透過查看被 mock 的類別的回傳值來存取「mock 實例」。

在下面的範例中，我們有一個函式 ‘some_function’，它實例化 ‘Foo’ 並呼叫它
的方法。對 *note patch(): e34. 的呼叫將類別 ‘Foo’ 替換為一個 mock。‘Foo’
實例是呼叫 mock 的結果，因此它是透過修改 mock *note return_value: 3edb.
來配置的。：

     >>> def some_function():
     ...     instance = module.Foo()
     ...     return instance.method()
     ...
     >>> with patch('module.Foo') as mock:
     ...     instance = mock.return_value
     ...     instance.method.return_value = 'the result'
     ...     result = some_function()
     ...     assert result == 'the result'


File: python.info,  Node: 命名你的 mock,  Next: 追蹤所有呼叫,  Prev: Mock 類別<2>,  Up: 使用 Mock 的方式

5.26.7.5 命名你的 mock
......................

為你的 mock 命名可能會很有用。這個名稱會顯示在 mock 的 repr 中，且當
mock 出現在測試的失敗訊息中時，名稱會很有幫助。該名稱也會傳播到 mock 的
屬性或方法：

     >>> mock = MagicMock(name='foo')
     >>> mock
     <MagicMock name='foo' id='...'>
     >>> mock.method
     <MagicMock name='foo.method' id='...'>


File: python.info,  Node: 追蹤所有呼叫,  Next: 設定回傳值和屬性,  Prev: 命名你的 mock,  Up: 使用 Mock 的方式

5.26.7.6 追蹤所有呼叫
.....................

通常你會想要追蹤對一個方法的多個呼叫。*note mock_calls: 3edf. 屬性記錄對
mock 的子屬性以及其子屬性的所有呼叫。

     >>> mock = MagicMock()
     >>> mock.method()
     <MagicMock name='mock.method()' id='...'>
     >>> mock.attribute.method(10, x=53)
     <MagicMock name='mock.attribute.method()' id='...'>
     >>> mock.mock_calls
     [call.method(), call.attribute.method(10, x=53)]

如果你對 ‘mock_calls’ 做出斷言並且有任何不預期的方法被呼叫，則斷言將失敗
。這很有用，因為除了斷言你期望的呼叫已經進行之外，你還可以檢查它們是否按
正確的順序進行，並且沒有多餘的呼叫：

你可以使用 *note call: 18d3. 物件來建構串列以與 ‘mock_calls’ 進行比較：

     >>> expected = [call.method(), call.attribute.method(10, x=53)]
     >>> mock.mock_calls == expected
     True

然而，回傳 mock 的呼叫的參數不會被記錄，這代表在巢狀呼叫中，無法追蹤用於
建立上代的參數 important 的值：

     >>> m = Mock()
     >>> m.factory(important=True).deliver()
     <Mock name='mock.factory().deliver()' id='...'>
     >>> m.mock_calls[-1] == call.factory(important=False).deliver()
     True


File: python.info,  Node: 設定回傳值和屬性,  Next: 透過 mock 引發例外,  Prev: 追蹤所有呼叫,  Up: 使用 Mock 的方式

5.26.7.7 設定回傳值和屬性
.........................

在 mock 物件上設定回傳值非常簡單：

     >>> mock = Mock()
     >>> mock.return_value = 3
     >>> mock()
     3

當然，你可以對 mock 上的方法執行相同的操作：

     >>> mock = Mock()
     >>> mock.method.return_value = 3
     >>> mock.method()
     3

回傳值也可以在建構函式中設定：

     >>> mock = Mock(return_value=3)
     >>> mock()
     3

如果你需要在 mock 上進行屬性設置，只需執行以下操作：

     >>> mock = Mock()
     >>> mock.x = 3
     >>> mock.x
     3

有時你想要 mock 更複雜的情況，例如
‘mock.connection.cursor().execute("SELECT 1")’。如果我們希望此呼叫回傳一
個串列，那麼我們就必須配置巢狀呼叫的結果。

如下所示，我們可以使用 *note call: 18d3. 在「鍊接呼叫 (chained call)」中
建構呼叫的集合，以便在之後輕鬆的進行斷言：

     >>> mock = Mock()
     >>> cursor = mock.connection.cursor.return_value
     >>> cursor.execute.return_value = ['foo']
     >>> mock.connection.cursor().execute("SELECT 1")
     ['foo']
     >>> expected = call.connection.cursor().execute("SELECT 1").call_list()
     >>> mock.mock_calls
     [call.connection.cursor(), call.connection.cursor().execute('SELECT 1')]
     >>> mock.mock_calls == expected
     True

正是對 ‘.call_list()’ 的呼叫將我們的呼叫物件轉換為代表鍊接呼叫的呼叫串列
。


File: python.info,  Node: 透過 mock 引發例外,  Next: Side effect 函式以及可疊代物件,  Prev: 設定回傳值和屬性,  Up: 使用 Mock 的方式

5.26.7.8 透過 mock 引發例外
...........................

一個有用的屬性是 *note side_effect: 3ed9.。如果將其設定為例外類別或實例
，則當 mock 被呼叫時將引發例外。

     >>> mock = Mock(side_effect=Exception('Boom!'))
     >>> mock()
     Traceback (most recent call last):
       ...
     Exception: Boom!


File: python.info,  Node: Side effect 函式以及可疊代物件,  Next: Mock 非同步可疊代物件,  Prev: 透過 mock 引發例外,  Up: 使用 Mock 的方式

5.26.7.9 Side effect 函式以及可疊代物件
.......................................

‘side_effect’ 也可以設定為函式或可疊代物件。‘side_effect’ 作為可疊代物件
的使用案例是：當你的 mock 將會被多次呼叫，且你希望每次呼叫回傳不同的值。
當你將 ‘side_effect’ 設定為可疊代物件時，對 mock 的每次呼叫都會傳回可疊
代物件中的下一個值：

     >>> mock = MagicMock(side_effect=[4, 5, 6])
     >>> mock()
     4
     >>> mock()
     5
     >>> mock()
     6

對於更進階的使用案例，例如根據 mock 被呼叫的內容動態變更回傳值，可以將
‘side_effect’ 設成一個函式。該函式會使用與 mock 相同的引數被呼叫。函式回
傳的內容就會是呼叫回傳的內容：

     >>> vals = {(1, 2): 1, (2, 3): 2}
     >>> def side_effect(*args):
     ...     return vals[args]
     ...
     >>> mock = MagicMock(side_effect=side_effect)
     >>> mock(1, 2)
     1
     >>> mock(2, 3)
     2


File: python.info,  Node: Mock 非同步可疊代物件,  Next: Mock 非同步情境管理器,  Prev: Side effect 函式以及可疊代物件,  Up: 使用 Mock 的方式

5.26.7.10 Mock 非同步可疊代物件
...............................

從 Python 3.8 開始，‘AsyncMock’ 和 ‘MagicMock’ 支援透過 ‘__aiter__’ 來
mock *note Asynchronous Iterators: d20.。‘__aiter__’ 的 *note
return_value: 3edb. 屬性可用來設定用於疊代的回傳值。

     >>> mock = MagicMock()  # AsyncMock also works here
     >>> mock.__aiter__.return_value = [1, 2, 3]
     >>> async def main():
     ...     return [i async for i in mock]
     ...
     >>> asyncio.run(main())
     [1, 2, 3]


File: python.info,  Node: Mock 非同步情境管理器,  Next: 從現有物件建立 mock,  Prev: Mock 非同步可疊代物件,  Up: 使用 Mock 的方式

5.26.7.11 Mock 非同步情境管理器
...............................

從 Python 3.8 開始，‘AsyncMock’ 和 ‘MagicMock’ 支援透過 ‘__aenter__’ 和
‘__aexit__’ 來 mock *note Asynchronous Context Managers: 5a0.。預設情況
下，‘__aenter__’ 和 ‘__aexit__’ 是回傳非同步函式的 ‘AsyncMock’ 實例。

     >>> class AsyncContextManager:
     ...     async def __aenter__(self):
     ...         return self
     ...     async def __aexit__(self, exc_type, exc, tb):
     ...         pass
     ...
     >>> mock_instance = MagicMock(AsyncContextManager())  # AsyncMock also works here
     >>> async def main():
     ...     async with mock_instance as result:
     ...         pass
     ...
     >>> asyncio.run(main())
     >>> mock_instance.__aenter__.assert_awaited_once()
     >>> mock_instance.__aexit__.assert_awaited_once()


File: python.info,  Node: 從現有物件建立 mock,  Next: 使用 side_effect 回傳各別檔案內容,  Prev: Mock 非同步情境管理器,  Up: 使用 Mock 的方式

5.26.7.12 從現有物件建立 mock
.............................

過度使用 mock 的一個問題是，它將你的測試與 mock 的實作結合在一起，而不是
與真實的程式碼結合。假設你有一個實作 ‘some_method’ 的類別，在另一個類別
的測試中，你提供了一個 mock 的物件，其'也'提供了 ‘some_method’。如果之後
你重構第一個類別，使其不再具有 ‘some_method’ - 那麼即使你的程式碼已經損
壞，你的測試也將繼續通過！

*note Mock: 9ef. 允許你使用 'spec' 關鍵字引數提供一個物件作為 mock 的規
格。對 mock 存取規格物件上不存在的方法或屬性將立即引發一個屬性錯誤。如果
你更改規格的實作，那麼使用該類別的測試將立即失敗，而無需在這些測試中實例
化該類別。

     >>> mock = Mock(spec=SomeClass)
     >>> mock.old_method()
     Traceback (most recent call last):
        ...
     AttributeError: Mock object has no attribute 'old_method'. Did you mean: 'class_method'?

使用規格還可以更聰明地匹配對 mock 的呼叫，無論引數是作為位置引數還是命名
引數傳遞：

     >>> def f(a, b, c): pass
     ...
     >>> mock = Mock(spec=f)
     >>> mock(1, 2, 3)
     <Mock name='mock()' id='140161580456576'>
     >>> mock.assert_called_with(a=1, b=2, c=3)

如果你希望這種更聰明的匹配也可以應用於 mock 上的方法呼叫，你可以使用
*note 自動規格: 3ed5.。

如果你想要一種更強大的規格形式來防止設定任意屬性以及取得它們，那麼你可以
使用 'spec_set' 而不是 'spec'。


File: python.info,  Node: 使用 side_effect 回傳各別檔案內容,  Prev: 從現有物件建立 mock,  Up: 使用 Mock 的方式

5.26.7.13 使用 side_effect 回傳各別檔案內容
...........................................

*note mock_open(): 1606. 是用於 patch *note open(): 4c0. 方法。*note
side_effect: 3ed9. 可以用來在每次呼叫回傳一個新的 mock 物件。這可以用於
回傳儲存在字典中的各別檔案的不同內容：

     DEFAULT = "default"
     data_dict = {"file1": "data1",
                  "file2": "data2"}

     def open_side_effect(name):
         return mock_open(read_data=data_dict.get(name, DEFAULT))()

     with patch("builtins.open", side_effect=open_side_effect):
         with open("file1") as file1:
             assert file1.read() == "data1"

         with open("file2") as file2:
             assert file2.read() == "data2"

         with open("file3") as file2:
             assert file2.read() == "default"


File: python.info,  Node: Patch 裝飾器,  Next: 更多範例,  Prev: 使用 Mock 的方式,  Up: unittest mock --- 入門指南

5.26.7.14 Patch 裝飾器
......................

     備註: 使用 *note patch(): e34. 時，需注意的是你得在被查找物件的命名
     空間中（in the namespace where they are looked up）patch 物件。這通
     常很直接，但若需要快速導引，請參閱*note 該 patch 何處: 3ed3.。

測試中的常見需求是 patch 類別屬性或模組屬性，例如 patch 一個內建函式（
built-in）或 patch 模組中的類別以測試它是否已實例化。模組和類別實際上是
全域的，因此在測試後必須撤銷它們的 patch，否則 patch 將延續到其他測試中
並導致難以診斷問題。

mock 為此提供了三個方便的裝飾器：*note patch(): e34.、*note
patch.object(): 18bb. 和 *note patch.dict(): 18f8.。‘patch’ 接受單一字串
，格式為 ‘package.module.Class.attribute’，用來指定要 patch 的屬性。同時
它也可以接受你想要替換的屬性（或類別或其他）的值。‘patch.object’ 接受一
個物件和你想要 patch 的屬性的名稱，同時也可以接受要 patch 的值。

‘patch.object’：

     >>> original = SomeClass.attribute
     >>> @patch.object(SomeClass, 'attribute', sentinel.attribute)
     ... def test():
     ...     assert SomeClass.attribute == sentinel.attribute
     ...
     >>> test()
     >>> assert SomeClass.attribute == original

     >>> @patch('package.module.attribute', sentinel.attribute)
     ... def test():
     ...     from package.module import attribute
     ...     assert attribute is sentinel.attribute
     ...
     >>> test()

如果你要 patch 一個模組（包括 *note builtins: e.），請使用 *note
patch(): e34. 而非 *note patch.object(): 18bb.：

     >>> mock = MagicMock(return_value=sentinel.file_handle)
     >>> with patch('builtins.open', mock):
     ...     handle = open('filename', 'r')
     ...
     >>> mock.assert_called_with('filename', 'r')
     >>> assert handle == sentinel.file_handle, "incorrect file handle returned"

如有需要，模組名稱可以含有 ‘.’，形式為 ‘package.module’：

     >>> @patch('package.module.ClassName.attribute', sentinel.attribute)
     ... def test():
     ...     from package.module import ClassName
     ...     assert ClassName.attribute == sentinel.attribute
     ...
     >>> test()

一個好的模式是實際裝飾測試方法本身：

     >>> class MyTest(unittest.TestCase):
     ...     @patch.object(SomeClass, 'attribute', sentinel.attribute)
     ...     def test_something(self):
     ...         self.assertEqual(SomeClass.attribute, sentinel.attribute)
     ...
     >>> original = SomeClass.attribute
     >>> MyTest('test_something').test_something()
     >>> assert SomeClass.attribute == original

如果你想使用一個 mock 進行 patch，你可以使用僅帶有一個引數的 *note
patch(): e34.（或帶有兩個引數的 *note patch.object(): 18bb.）。Mock 將被
建立並被傳遞到測試函式 / 方法中：

     >>> class MyTest(unittest.TestCase):
     ...     @patch.object(SomeClass, 'static_method')
     ...     def test_something(self, mock_method):
     ...         SomeClass.static_method()
     ...         mock_method.assert_called_with()
     ...
     >>> MyTest('test_something').test_something()

你可以使用這個模式堆疊多個 patch 裝飾器：

     >>> class MyTest(unittest.TestCase):
     ...     @patch('package.module.ClassName1')
     ...     @patch('package.module.ClassName2')
     ...     def test_something(self, MockClass2, MockClass1):
     ...         self.assertIs(package.module.ClassName1, MockClass1)
     ...         self.assertIs(package.module.ClassName2, MockClass2)
     ...
     >>> MyTest('test_something').test_something()

當你巢狀使用 patch 裝飾器時，mock 傳遞到被裝飾函式的順序會跟其被應用的順
序相同（一般 'Python' 應用裝飾器的順序）。這意味著由下而上，因此在上面的
範例中，‘module.ClassName2’ 的 mock 會先被傳入。

也有 *note patch.dict(): 18f8.，用於在測試範圍中設定字典內的值，並在測試
結束時將其恢復為原始狀態：

     >>> foo = {'key': 'value'}
     >>> original = foo.copy()
     >>> with patch.dict(foo, {'newkey': 'newvalue'}, clear=True):
     ...     assert foo == {'newkey': 'newvalue'}
     ...
     >>> assert foo == original

‘patch’、‘patch.object’ 和 ‘patch.dict’ 都可以用來作為情境管理器。

當你使用 *note patch(): e34. 為你建立一個 mock 時，你可以使用 with 陳述
式的 "as" 形式來取得 mock 的參照：

     >>> class ProductionClass:
     ...     def method(self):
     ...         pass
     ...
     >>> with patch.object(ProductionClass, 'method') as mock_method:
     ...     mock_method.return_value = None
     ...     real = ProductionClass()
     ...     real.method(1, 2, 3)
     ...
     >>> mock_method.assert_called_with(1, 2, 3)

另外，“patch”、“patch.object” 和 “patch.dict” 也可以用來作為類別裝飾器。
以這種方式使用時，與將裝飾器單獨應用於每個名稱以 “test” 開頭的方法相同。


File: python.info,  Node: 更多範例,  Prev: Patch 裝飾器,  Up: unittest mock --- 入門指南

5.26.7.15 更多範例
..................

以下是一些更進階一點的情境的範例。

* Menu:

* Mock 鍊接呼叫::
* 部分 mocking::
* Mock 產生器方法::
* 對每個測試方法應用相同的 patch::
* Mock Unbound Methods （未繫結方法）::
* 使用 mock 檢查多個呼叫::
* 應對可變引數::
* 巢狀使用 Patch::
* 使用 MagicMock 來 mock 字典::
* Mock 子類別及其屬性::
* 使用 patch.dict 來 mock import: 使用 patch dict 來 mock import.
* 追蹤呼叫順序與更簡潔的呼叫斷言::
* 更複雜的引數匹配::


File: python.info,  Node: Mock 鍊接呼叫,  Next: 部分 mocking,  Up: 更多範例

5.26.7.16 Mock 鍊接呼叫
.......................

一旦你了解了 *note return_value: 3edb. 屬性，mock 鍊接呼叫其實就很簡單了
。當一個 mock 第一次被呼叫，或者你在它被呼叫之前取得其 ‘return_value’ 時
，一個新的 *note Mock: 9ef. 就會被建立。

這代表你可以透過查問 ‘return_value’ mock 來了解一個對被 mock 的物件的呼
叫回傳的物件是如何被使用的：

     >>> mock = Mock()
     >>> mock().foo(a=2, b=3)
     <Mock name='mock().foo()' id='...'>
     >>> mock.return_value.foo.assert_called_with(a=2, b=3)

這裡只需一個簡單的步驟即可進行配置並對鍊接呼叫進行斷言。當然，另一種選擇
是先以更容易被測試的方式撰寫程式碼...

所以，假設我們有一些程式碼，看起來大概像這樣：

     >>> class Something:
     ...     def __init__(self):
     ...         self.backend = BackendProvider()
     ...     def method(self):
     ...         response = self.backend.get_endpoint('foobar').create_call('spam', 'eggs').start_call()
     ...         # more code

假設 ‘BackendProvider’ 已經經過充分測試，那麼我們該如何測試 ‘method()’？
具體來說，我們要測試程式碼部分 ‘# more code’ 是否以正確的方式使用
‘response’ 物件。

由於此呼叫鍊是從實例屬性進行的，因此我們可以在 ‘Something’ 實例上 monkey
patch ‘backend’ 屬性。在這種特定的情況下，我們只對最終呼叫 ‘start_call’
的回傳值感興趣，因此我們不需要做太多配置。我們假設它傳回的物件是類檔案物
件 (file-like)，因此我們會確保我們的 response 物件使用內建的 *note
open(): 4c0. 作為其 ‘spec’。

為此，我們建立一個 mock 實例作為我們的 mock backend，並為其建立一個 mock
response 物件。要將 response 設定為最後的 ‘start_call’ 的回傳值，我們可
以這樣做：

     mock_backend.get_endpoint.return_value.create_call.return_value.start_call.return_value = mock_response

我們可以使用 *note configure_mock(): 3edc. 方法來以稍微好一點的方式為我
們直接設定回傳值：

     >>> something = Something()
     >>> mock_response = Mock(spec=open)
     >>> mock_backend = Mock()
     >>> config = {'get_endpoint.return_value.create_call.return_value.start_call.return_value': mock_response}
     >>> mock_backend.configure_mock(**config)

有了這些，我們就可以原地 (in place) monkey patch "mock backend"，並且可
以進行真正的呼叫：

     >>> something.backend = mock_backend
     >>> something.method()

藉由使用 *note mock_calls: 3edf.，我們可以使用單一一個斷言來檢查鍊接呼叫
。一個鍊接呼叫是一行程式碼中的多個呼叫，因此 ‘mock_calls’ 中會有多個項目
。我們可以使用 *note call.call_list(): 3f16. 來為我們建立這個呼叫串列：

     >>> chained = call.get_endpoint('foobar').create_call('spam', 'eggs').start_call()
     >>> call_list = chained.call_list()
     >>> assert mock_backend.mock_calls == call_list


File: python.info,  Node: 部分 mocking,  Next: Mock 產生器方法,  Prev: Mock 鍊接呼叫,  Up: 更多範例

5.26.7.17 部分 mocking
......................

在某些測試中，我們會想 mock 對 *note datetime.date.today(): 1439. 的呼叫
以回傳一個已知日期，但我不想阻止測試中的程式碼建立新的日期物件。不幸的是
*note datetime.date: 1b1. 是用 C 語言寫的，所以們我不能 monkey patch 靜
態的 *note datetime.date.today(): 1439. 方法。

我們找到了一種簡單的方法來做到這一點，其用 mock 有效地包裝日期類別，但將
對建構函式的呼叫傳遞給真實的類別（並返回真實的實例）。

這裡使用 *note patch 裝飾器: e34. 來 mock 被測模組中的 ‘date’ 類別。然後
，mock 日期類別上的 *note side_effect: 3ed9. 屬性會被設定為回傳真實日期
的 lambda 函式。當 mock 日期類別被呼叫時，將透過 ‘side_effect’ 建構並回
傳真實日期。：

     >>> from datetime import date
     >>> with patch('mymodule.date') as mock_date:
     ...     mock_date.today.return_value = date(2010, 10, 8)
     ...     mock_date.side_effect = lambda *args, **kw: date(*args, **kw)
     ...
     ...     assert mymodule.date.today() == date(2010, 10, 8)
     ...     assert mymodule.date(2009, 6, 8) == date(2009, 6, 8)

注意，我們沒有全域 patch *note datetime.date: 1b1.，而是在'使用'它的模組
中 patch ‘date’。請參閱 *note 該 patch 何處: 3ed3.。

當 ‘date.today()’ 被呼叫時，一個已知日期會被回傳，但對 ‘date(...)’ 建構
函式的呼叫仍然會回傳正常日期。如果不這樣使用，你可能會發現自己必須使用與
被測程式碼完全相同的演算法來計算預期結果，這是一個典型的測試的反面模式
(anti-pattern)。

對日期建構函式的呼叫被記錄在 ‘mock_date’ 屬性（‘call_count’ 及其相關屬性
）中，這對你的測試也可能有用處。

處理 mock 日期或其他內建類別的另一種方法在 這個 blog(1) 中討論。

   ---------- Footnotes ----------

   (1) 
https://williambert.online/2011/07/how-to-unit-testing-in-django-with-mocking-and-patching/


File: python.info,  Node: Mock 產生器方法,  Next: 對每個測試方法應用相同的 patch,  Prev: 部分 mocking,  Up: 更多範例

5.26.7.18 Mock 產生器方法
.........................

Python 產生器是一個函式或方法，它使用 *note yield: 971. 陳述式在疊代 (1)
時回傳一系列的值。

產生器方法 / 函式會被呼叫以回傳產生器物件。之後此產生器會進行疊代。疊代
的協定方法是 *note __iter__(): 1bc4.，所以我們可以使用 *note MagicMock:
e33. 來 mock 它。

下面是一個範例類別，其包含實作產生器的一個 "iter" 方法：

     >>> class Foo:
     ...     def iter(self):
     ...         for i in [1, 2, 3]:
     ...             yield i
     ...
     >>> foo = Foo()
     >>> list(foo.iter())
     [1, 2, 3]

我們該如何 mock 這個類別，特別是它的 "iter" 方法呢？

要配置從疊代回傳的值（隱含在對 *note list: 5b6. 的呼叫中），我們需要配置
呼叫 ‘foo.iter()’ 所回傳的物件。

     >>> mock_foo = MagicMock()
     >>> mock_foo.iter.return_value = iter([1, 2, 3])
     >>> list(mock_foo.iter())
     [1, 2, 3]

   ---------- Footnotes ----------

   (1) 還有關於產生器運算式及產生器的更多 進階用法
(http://www.dabeaz.com/coroutines/index.html) ，但我們在這裡不考慮它們。
一個關於產生器及其強大功能的優良說明是：Generator Tricks for Systems
Programmers (http://www.dabeaz.com/generators/)。


File: python.info,  Node: 對每個測試方法應用相同的 patch,  Next: Mock Unbound Methods （未繫結方法）,  Prev: Mock 產生器方法,  Up: 更多範例

5.26.7.19 對每個測試方法應用相同的 patch
........................................

如果你希望 patch 能用在多個測試方法上，顯而易見的方式是將 patch 裝飾器應
用於每個方法。這感覺是不必要的重複行為，因此你可以使用 *note patch():
e34.（及其他 patch 的變體）作為類別裝飾器。這會將 patch 應用在該類別的所
有測試方法上。測試方法由名稱以 ‘test’ 開頭來識別：

     >>> @patch('mymodule.SomeClass')
     ... class MyTest(unittest.TestCase):
     ...
     ...     def test_one(self, MockSomeClass):
     ...         self.assertIs(mymodule.SomeClass, MockSomeClass)
     ...
     ...     def test_two(self, MockSomeClass):
     ...         self.assertIs(mymodule.SomeClass, MockSomeClass)
     ...
     ...     def not_a_test(self):
     ...         return 'something'
     ...
     >>> MyTest('test_one').test_one()
     >>> MyTest('test_two').test_two()
     >>> MyTest('test_two').not_a_test()
     'something'

管理 patch 的另一種方式是使用 *note patch 方法：啟動與停止: 3f07.。這允
許你將 patch 移到你的 ‘setUp’ 與 ‘tearDown’ 方法中。：

     >>> class MyTest(unittest.TestCase):
     ...     def setUp(self):
     ...         self.patcher = patch('mymodule.foo')
     ...         self.mock_foo = self.patcher.start()
     ...
     ...     def test_foo(self):
     ...         self.assertIs(mymodule.foo, self.mock_foo)
     ...
     ...     def tearDown(self):
     ...         self.patcher.stop()
     ...
     >>> MyTest('test_foo').run()

如果你使用這個技巧，你必須確保透過呼叫 ‘stop’ 來 "取消" patch。這可能會
比你想像的還要複雜一點，因為如果有例外在 ‘setUp’ 中被引發，則 ‘tearDown’
就不會被呼叫。*note unittest.TestCase.addCleanup(): a24. 會讓這稍微簡單
一點：

     >>> class MyTest(unittest.TestCase):
     ...     def setUp(self):
     ...         patcher = patch('mymodule.foo')
     ...         self.addCleanup(patcher.stop)
     ...         self.mock_foo = patcher.start()
     ...
     ...     def test_foo(self):
     ...         self.assertIs(mymodule.foo, self.mock_foo)
     ...
     >>> MyTest('test_foo').run()


File: python.info,  Node: Mock Unbound Methods （未繫結方法）,  Next: 使用 mock 檢查多個呼叫,  Prev: 對每個測試方法應用相同的 patch,  Up: 更多範例

5.26.7.20 Mock Unbound Methods （未繫結方法）
.............................................

在撰寫測試時，當我們需要 patch 一個'未繫結方法'（patch 類別上的方法而不
是實例上的方法）。我們需要將 self 作為第一個引數傳入，因為我們想斷言哪些
物件正在呼叫這個特定方法。問題是你無法為此使用 mock 進行 patch，因為就算
你用一個 mock 替換未繫結方法，從實例取得它時它也不會成為一個繫結方法，因
此 self 並不會被傳遞。解決方法是使用真實的函式來 patch 未繫結方法。*note
patch(): e34. 裝飾器使得用 mock 來 patch out 方法是如此的簡單，以至於建
立一個真正的函式相對變得很麻煩。

如果你將 ‘autospec=True’ 傳遞給 patch，那麼它會使用'真的'函式物件來進行
patch。此函式物件與它所替換的函式物件具有相同的簽名，但實際上委託給
mock。你仍然會以與之前完全相同的方式自動建立 mock。但這意味著，如果你使
用它來 patch 類別上的未繫結方法，則從實例取得的 mock 函式將轉換為繫結方
法。‘self’ 會作為其第一個引數傳入，而這正是我們想要的：

     >>> class Foo:
     ...   def foo(self):
     ...     pass
     ...
     >>> with patch.object(Foo, 'foo', autospec=True) as mock_foo:
     ...   mock_foo.return_value = 'foo'
     ...   foo = Foo()
     ...   foo.foo()
     ...
     'foo'
     >>> mock_foo.assert_called_once_with(foo)

如果我們不使用 ‘autospec=True’，那麼未繫結方法將使用一個 Mock 實例 patch
out，並且不被使用 ‘self’ 進行呼叫。


File: python.info,  Node: 使用 mock 檢查多個呼叫,  Next: 應對可變引數,  Prev: Mock Unbound Methods （未繫結方法）,  Up: 更多範例

5.26.7.21 使用 mock 檢查多個呼叫
................................

mock 有很好的 API，用於對 mock 物件的使用方式做出斷言。

     >>> mock = Mock()
     >>> mock.foo_bar.return_value = None
     >>> mock.foo_bar('baz', spam='eggs')
     >>> mock.foo_bar.assert_called_with('baz', spam='eggs')

如果你的 mock 只被呼叫一次，你可以使用 *note assert_called_once_with():
3edd. 方法，其也斷言 *note call_count: 3ee6. 是1。

     >>> mock.foo_bar.assert_called_once_with('baz', spam='eggs')
     >>> mock.foo_bar()
     >>> mock.foo_bar.assert_called_once_with('baz', spam='eggs')
     Traceback (most recent call last):
         ...
     AssertionError: Expected 'foo_bar' to be called once. Called 2 times.
     Calls: [call('baz', spam='eggs'), call()].

‘assert_called_with’ 和 ‘assert_called_once_with’ 都對'最近一次'的呼叫做
出斷言。如果你的 mock 將被多次呼叫，並且你想要對'所有'這些呼叫進行斷言，
你可以使用 *note call_args_list: 3ee7.：

     >>> mock = Mock(return_value=None)
     >>> mock(1, 2, 3)
     >>> mock(4, 5, 6)
     >>> mock()
     >>> mock.call_args_list
     [call(1, 2, 3), call(4, 5, 6), call()]

*note call: 18d3. 輔助函式可以輕鬆地對這些呼叫做出斷言。你可以建立預期呼
叫的清單並將其與 ‘call_args_list’ 進行比較。這看起來與 ‘call_args_list’
的 repr 非常相似：

     >>> expected = [call(1, 2, 3), call(4, 5, 6), call()]
     >>> mock.call_args_list == expected
     True


File: python.info,  Node: 應對可變引數,  Next: 巢狀使用 Patch,  Prev: 使用 mock 檢查多個呼叫,  Up: 更多範例

5.26.7.22 應對可變引數
......................

另一種情況很少見，但可能會困擾你，那就是當你的 mock 被使用可變引數呼叫。
‘call_args’ 和 ‘call_args_list’ 儲存對引數的'參照'。如果引數被測試中的程
式碼改變，那麼你將無法再對 mock 被呼叫時的值進行斷言。

這是一些秀出問題的程式碼範例。 想像 'mymodule' 中定義以下函式：

     def frob(val):
         pass

     def grob(val):
         "First frob and then clear val"
         frob(val)
         val.clear()

當我們嘗試測試 ‘grob’ 使用正確的引數呼叫 ‘frob’ 時，看看會發生什麼：

     >>> with patch('mymodule.frob') as mock_frob:
     ...     val = {6}
     ...     mymodule.grob(val)
     ...
     >>> val
     set()
     >>> mock_frob.assert_called_with({6})
     Traceback (most recent call last):
         ...
     AssertionError: Expected: (({6},), {})
     Called with: ((set(),), {})

一種可能是讓 mock 複製你傳入的引數。如果你進行的斷言依賴於物件識別性來確
定相等性，這就可能導致問題。

以下是一種使用 *note side_effect: 3ed9. 功能的解法。如果你為 mock 提供一
個 ‘side_effect’ 函式，則 ‘side_effect’ 將被使用與 mock 相同的引數呼叫。
這使我們有機會複製引數並將其儲存以供之後的斷言。在這個範例中，我們使用
'另一個' mock 來儲存引數，以便我們可以使用 mock 方法來執行斷言。同樣的，
有一個輔助函式為我們設定了這些。：

     >>> from copy import deepcopy
     >>> from unittest.mock import Mock, patch, DEFAULT
     >>> def copy_call_args(mock):
     ...     new_mock = Mock()
     ...     def side_effect(*args, **kwargs):
     ...         args = deepcopy(args)
     ...         kwargs = deepcopy(kwargs)
     ...         new_mock(*args, **kwargs)
     ...         return DEFAULT
     ...     mock.side_effect = side_effect
     ...     return new_mock
     ...
     >>> with patch('mymodule.frob') as mock_frob:
     ...     new_mock = copy_call_args(mock_frob)
     ...     val = {6}
     ...     mymodule.grob(val)
     ...
     >>> new_mock.assert_called_with({6})
     >>> new_mock.call_args
     call({6})

‘copy_call_args’ 與將要被呼叫的 mock 一起被呼叫。它回傳一個我們會對其進
行斷言的新的 mock。‘side_effect’ 函式建立引數們的副本，並用該副本呼叫我
們的 ‘new_mock’。

     備註: 如果你的 mock 只會被使用一次，則有一種更簡單的方法可以在呼叫
     引數時檢查它們。你可以簡單地在 ‘side_effect’ 函式內進行檢查。

          >>> def side_effect(arg):
          ...     assert arg == {6}
          ...
          >>> mock = Mock(side_effect=side_effect)
          >>> mock({6})
          >>> mock(set())
          Traceback (most recent call last):
              ...
          AssertionError

另一種方法是建立 *note Mock: 9ef. 或 *note MagicMock: e33. 的子類別來複
製（使用 *note copy.deepcopy(): b12.）引數。這是一個實作的例子：

     >>> from copy import deepcopy
     >>> class CopyingMock(MagicMock):
     ...     def __call__(self, /, *args, **kwargs):
     ...         args = deepcopy(args)
     ...         kwargs = deepcopy(kwargs)
     ...         return super().__call__(*args, **kwargs)
     ...
     >>> c = CopyingMock(return_value=None)
     >>> arg = set()
     >>> c(arg)
     >>> arg.add(1)
     >>> c.assert_called_with(set())
     >>> c.assert_called_with(arg)
     Traceback (most recent call last):
         ...
     AssertionError: expected call not found.
     Expected: mock({1})
     Actual: mock(set())
     >>> c.foo
     <CopyingMock name='mock.foo' id='...'>

當你將 ‘Mock’ 或 ‘MagicMock’ 子類別化時，所有屬性會被動態建立，且
‘return_value’ 會自動使用你的子類別。這代表著 ‘CopyingMock’ 的所有子代
(child) 也會具有 ‘CopyingMock’ 型別。


File: python.info,  Node: 巢狀使用 Patch,  Next: 使用 MagicMock 來 mock 字典,  Prev: 應對可變引數,  Up: 更多範例

5.26.7.23 巢狀使用 Patch
........................

將 patch 作為情境管理器使用很好，但是如果你使用複數個 patch，你最終可能
會得到巢狀的 with 陳述式，並且越來越向右縮排：

     >>> class MyTest(unittest.TestCase):
     ...
     ...     def test_foo(self):
     ...         with patch('mymodule.Foo') as mock_foo:
     ...             with patch('mymodule.Bar') as mock_bar:
     ...                 with patch('mymodule.Spam') as mock_spam:
     ...                     assert mymodule.Foo is mock_foo
     ...                     assert mymodule.Bar is mock_bar
     ...                     assert mymodule.Spam is mock_spam
     ...
     >>> original = mymodule.Foo
     >>> MyTest('test_foo').test_foo()
     >>> assert mymodule.Foo is original

我們可以使用 unittest 的 ‘cleanup’ 函式以及 *note patch
方法：啟動與停止: 3f07. 來達到相同的效果，而不會出現因巢狀導致的縮排。一
個簡單的輔助方法 ‘create_patch’ 會將 patch 放置到位並為我們回傳被建立的
mock：

     >>> class MyTest(unittest.TestCase):
     ...
     ...     def create_patch(self, name):
     ...         patcher = patch(name)
     ...         thing = patcher.start()
     ...         self.addCleanup(patcher.stop)
     ...         return thing
     ...
     ...     def test_foo(self):
     ...         mock_foo = self.create_patch('mymodule.Foo')
     ...         mock_bar = self.create_patch('mymodule.Bar')
     ...         mock_spam = self.create_patch('mymodule.Spam')
     ...
     ...         assert mymodule.Foo is mock_foo
     ...         assert mymodule.Bar is mock_bar
     ...         assert mymodule.Spam is mock_spam
     ...
     >>> original = mymodule.Foo
     >>> MyTest('test_foo').run()
     >>> assert mymodule.Foo is original


File: python.info,  Node: 使用 MagicMock 來 mock 字典,  Next: Mock 子類別及其屬性,  Prev: 巢狀使用 Patch,  Up: 更多範例

5.26.7.24 使用 MagicMock 來 mock 字典
.....................................

你可能會想要 mock 字典或其他容器物件，記錄對它的所有存取，同時讓它仍然像
字典一樣運作。

我們可以使用 *note MagicMock: e33. 來做到這一點，它的行為會與字典一致，
並使用 *note side_effect: 3ed9. 將字典存取委託給我們控制下的真實底層字典
。

當 ‘MagicMock’ 的 *note __getitem__(): 266. 和 *note __setitem__():
1434. 方法被呼叫時（一般的字典存取）， ‘side_effect’ 會被使用鍵 (key) 來
呼叫 （在 ‘__setitem__’ 的情況也會使用值 (value)）。我們也可以控制回傳的
內容。

使用 ‘MagicMock’ 後，我們可以使用諸如 *note call_args_list: 3ee7. 之類的
屬性來斷言字典被使用的方式：

     >>> my_dict = {'a': 1, 'b': 2, 'c': 3}
     >>> def getitem(name):
     ...      return my_dict[name]
     ...
     >>> def setitem(name, val):
     ...     my_dict[name] = val
     ...
     >>> mock = MagicMock()
     >>> mock.__getitem__.side_effect = getitem
     >>> mock.__setitem__.side_effect = setitem

     備註: 不使用 ‘MagicMock’ 的替代方案是使用 ‘Mock’ 並且'只'提供你特別
     想要的魔術方法：

          >>> mock = Mock()
          >>> mock.__getitem__ = Mock(side_effect=getitem)
          >>> mock.__setitem__ = Mock(side_effect=setitem)

     '第三個'選擇是使用 ‘MagicMock’，但傳入 ‘dict’ 作為 'spec' （或
     'spec_set'）引數，以使被建立的 ‘MagicMock’ 僅具有字典可用的魔術方法
     ：

          >>> mock = MagicMock(spec_set=dict)
          >>> mock.__getitem__.side_effect = getitem
          >>> mock.__setitem__.side_effect = setitem

有了這些 side effect 函式，‘mock’ 會像一般的字典一樣運作，但會記錄存取。
如果你嘗試存取不存在的鍵，它甚至會引發一個 *note KeyError: 2fb.。

     >>> mock['a']
     1
     >>> mock['c']
     3
     >>> mock['d']
     Traceback (most recent call last):
         ...
     KeyError: 'd'
     >>> mock['b'] = 'fish'
     >>> mock['d'] = 'eggs'
     >>> mock['b']
     'fish'
     >>> mock['d']
     'eggs'

在上述方式被使用後，你就可以使用普通的 mock 方法和屬性對存取進行斷言：

     >>> mock.__getitem__.call_args_list
     [call('a'), call('c'), call('d'), call('b'), call('d')]
     >>> mock.__setitem__.call_args_list
     [call('b', 'fish'), call('d', 'eggs')]
     >>> my_dict
     {'a': 1, 'b': 'fish', 'c': 3, 'd': 'eggs'}


File: python.info,  Node: Mock 子類別及其屬性,  Next: 使用 patch dict 來 mock import,  Prev: 使用 MagicMock 來 mock 字典,  Up: 更多範例

5.26.7.25 Mock 子類別及其屬性
.............................

你會想子類別化 *note Mock: 9ef. 的原因可能有很多種。其中之一是增加輔助方
法。以下是一個有點笨的例子：

     >>> class MyMock(MagicMock):
     ...     def has_been_called(self):
     ...         return self.called
     ...
     >>> mymock = MyMock(return_value=None)
     >>> mymock
     <MyMock id='...'>
     >>> mymock.has_been_called()
     False
     >>> mymock()
     >>> mymock.has_been_called()
     True

‘Mock’ 實例的標準行為是屬性 mock 和回傳值 mock 會與存取它們的 mock 具有
相同的型別。這確保了 ‘Mock’ 屬性是 ‘Mocks’，‘MagicMock’ 屬性是
‘MagicMocks’ (1)。因此，如果你要子類別化以新增輔助方法，那麼它們也可用於
子類別實例的屬性 mock 和回傳值 mock。

     >>> mymock.foo
     <MyMock name='mock.foo' id='...'>
     >>> mymock.foo.has_been_called()
     False
     >>> mymock.foo()
     <MyMock name='mock.foo()' id='...'>
     >>> mymock.foo.has_been_called()
     True

有時候這很不方便。例如，有一個使用者(2)正在子類別化 mock 以建立 Twisted
adaptor(3)。將其應用於屬性實際上會導致錯誤。

‘Mock’ （及其各種形式）使用名為 ‘_get_child_mock’ 的方法來為屬性和回傳值
建立這些 "子 mock"。你可以透過置換此方法來防止你的子類別被用為屬性。其簽
名是取用任意的關鍵字引數（‘**kwargs’），然後將其傳遞給 mock 建構函式：

     >>> class Subclass(MagicMock):
     ...     def _get_child_mock(self, /, **kwargs):
     ...         return MagicMock(**kwargs)
     ...
     >>> mymock = Subclass()
     >>> mymock.foo
     <MagicMock name='mock.foo' id='...'>
     >>> assert isinstance(mymock, Subclass)
     >>> assert not isinstance(mymock.foo, Subclass)
     >>> assert not isinstance(mymock(), Subclass)

   ---------- Footnotes ----------

   (1) 此規則的例外是非可呼叫物件的 mock。屬性使用可呼叫物件的變體，否則
非可呼叫物件的 mock 無法具有可呼叫的方法。

   (2) https://code.google.com/archive/p/mock/issues/105

   (3) 
https://twisted.org/documents/11.0.0/api/twisted.python.components.html


File: python.info,  Node: 使用 patch dict 來 mock import,  Next: 追蹤呼叫順序與更簡潔的呼叫斷言,  Prev: Mock 子類別及其屬性,  Up: 更多範例

5.26.7.26 使用 patch.dict 來 mock import
........................................

可能會讓 mock 很困難的一種情況是在函式內部進行區域 import。這些狀況會更
難進行 mock，因為它們沒有使用我們可以 patch out 的模組命名空間中的物件。

一般來說，我們應該避免區域 import 的發生。有時這樣做是為了防止循環相依
(circular dependencies)，為此'通常'有更好的方式來解決問題（例如重構程式
碼）或透過延遲 import 來防止「前期成本 (up front costs)」。這也可以透過
比無條件的區域 import 更好的方式來解決（例如將模組儲存為類別或模組屬性，
並且僅在第一次使用時進行 import）。

除此之外，還有一種方法可以使用 ‘mock’ 來影響 import 的結果。Import 會從
*note sys.modules: 186e. 字典中取得一個'物件'。請注意，它會取得一個'物件
'，而該物件不需要是一個模組。初次 import 模組會導致模組物件被放入
‘sys.modules’ 中，因此通常當你 import 某些東西時，你會得到一個模組。但並
非一定要如此。

這代表你可以使用 *note patch.dict(): 18f8. 來'暫時'在 *note sys.modules:
186e. 中原地放置 mock。在這個 patch 作用時的任何 import 都會取得這個
mock。當 patch 完成時（被裝飾的函式結束、with 陳述式主體完成或
‘patcher.stop()’ 被呼叫），那麼之前在 ‘sys.modules’ 中的任何內容都會被安
全地復原。

下面是一個 mock out 'fooble' 模組的例子。

     >>> import sys
     >>> mock = Mock()
     >>> with patch.dict('sys.modules', {'fooble': mock}):
     ...    import fooble
     ...    fooble.blob()
     ...
     <Mock name='mock.blob()' id='...'>
     >>> assert 'fooble' not in sys.modules
     >>> mock.blob.assert_called_once_with()

如你所見，‘import fooble’ 成功了，但在離開之後，*note sys.modules: 186e.
中就沒有 'fooble' 了。

這也適用於 ‘from module import name’ 形式：

     >>> mock = Mock()
     >>> with patch.dict('sys.modules', {'fooble': mock}):
     ...    from fooble import blob
     ...    blob.blip()
     ...
     <Mock name='mock.blob.blip()' id='...'>
     >>> mock.blob.blip.assert_called_once_with()

透過稍微多一點的處理，你也可以 mock 套件的引入：

     >>> mock = Mock()
     >>> modules = {'package': mock, 'package.module': mock.module}
     >>> with patch.dict('sys.modules', modules):
     ...    from package.module import fooble
     ...    fooble()
     ...
     <Mock name='mock.module.fooble()' id='...'>
     >>> mock.module.fooble.assert_called_once_with()


File: python.info,  Node: 追蹤呼叫順序與更簡潔的呼叫斷言,  Next: 更複雜的引數匹配,  Prev: 使用 patch dict 來 mock import,  Up: 更多範例

5.26.7.27 追蹤呼叫順序與更簡潔的呼叫斷言
........................................

*note Mock: 9ef. 類別可以讓你透過 *note method_calls: 3ee1. 屬性追蹤
mock 物件上方法呼叫的'順序'。這不會讓你可以追蹤不同的 mock 物件之間的呼
叫順序，然而我們可以使用 *note mock_calls: 3edf. 來達到相同的效果。

因為 mock 會在 ‘mock_calls’ 中追蹤對子 mock 的呼叫，且存取 mock 的任意屬
性會建立一個子 mock，所以我們可以從父 mock 建立不同的 mock。之後對這些子
mock 的呼叫將依序全部記錄在父 mock 的 ‘mock_calls’ 中：

     >>> manager = Mock()
     >>> mock_foo = manager.foo
     >>> mock_bar = manager.bar

     >>> mock_foo.something()
     <Mock name='mock.foo.something()' id='...'>
     >>> mock_bar.other.thing()
     <Mock name='mock.bar.other.thing()' id='...'>

     >>> manager.mock_calls
     [call.foo.something(), call.bar.other.thing()]

之後我們可以透過與管理器 (manager) mock 上的 ‘mock_calls’ 屬性進行比較來
斷言呼叫及其順序：

     >>> expected_calls = [call.foo.something(), call.bar.other.thing()]
     >>> manager.mock_calls == expected_calls
     True

如果 ‘patch’ 正在被建立並放置為你的 mock，那麼你可以使用 *note
attach_mock(): 1502. 方法將它們附加到管理器 mock。附加之後，呼叫將被記錄
在管理器的 ‘mock_calls’ 中。：

     >>> manager = MagicMock()
     >>> with patch('mymodule.Class1') as MockClass1:
     ...     with patch('mymodule.Class2') as MockClass2:
     ...         manager.attach_mock(MockClass1, 'MockClass1')
     ...         manager.attach_mock(MockClass2, 'MockClass2')
     ...         MockClass1().foo()
     ...         MockClass2().bar()
     <MagicMock name='mock.MockClass1().foo()' id='...'>
     <MagicMock name='mock.MockClass2().bar()' id='...'>
     >>> manager.mock_calls
     [call.MockClass1(),
     call.MockClass1().foo(),
     call.MockClass2(),
     call.MockClass2().bar()]

如果進行了多次呼叫，但你只對其中特定呼叫的序列感興趣，則可以使用 *note
assert_has_calls(): 15a0. 方法。這需要一個呼叫串列（使用 *note call:
18d3. 物件建構）。如果該呼叫序列位於 *note mock_calls: 3edf. 中，則斷言
成功。

     >>> m = MagicMock()
     >>> m().foo().bar().baz()
     <MagicMock name='mock().foo().bar().baz()' id='...'>
     >>> m.one().two().three()
     <MagicMock name='mock.one().two().three()' id='...'>
     >>> calls = call.one().two().three().call_list()
     >>> m.assert_has_calls(calls)

儘管鍊接呼叫 ‘m.one().two().three()’ 並不是對 mock 進行的唯一呼叫，斷言
仍會成功。

有時可能會對一個 mock 進行多次呼叫，而你只對斷言其中'某些'呼叫感興趣。你
甚至可能不關心順序。在這種情況下，你可以將 ‘any_order=True’ 傳遞給
‘assert_has_calls’：

     >>> m = MagicMock()
     >>> m(1), m.two(2, 3), m.seven(7), m.fifty('50')
     (...)
     >>> calls = [call.fifty('50'), call(1), call.seven(7)]
     >>> m.assert_has_calls(calls, any_order=True)


File: python.info,  Node: 更複雜的引數匹配,  Prev: 追蹤呼叫順序與更簡潔的呼叫斷言,  Up: 更多範例

5.26.7.28 更複雜的引數匹配
..........................

使用與 *note ANY: 18d1. 相同的基本概念，我們可以實作匹配器 (matcher)，對
用來作為 mock 引數的物件進行更複雜的斷言。

假設我們預期某個物件會被傳進 mock，預設情況下，該 mock 會根據物件識別性
進行相等比較（對使用者定義類別的 Python 預設行為）。要使用 *note
assert_called_with(): 1927.，我們需要傳入完全相同的物件。如果我們只對該
物件的某些屬性感興趣，那麼我們可以建立一個匹配器來為我們檢查這些屬性。

你可以在這個範例中看到對 ‘assert_called_with’ 的一個「標準」呼叫是不夠的
：

     >>> class Foo:
     ...     def __init__(self, a, b):
     ...         self.a, self.b = a, b
     ...
     >>> mock = Mock(return_value=None)
     >>> mock(Foo(1, 2))
     >>> mock.assert_called_with(Foo(1, 2))
     Traceback (most recent call last):
         ...
     AssertionError: expected call not found.
     Expected: mock(<__main__.Foo object at 0x...>)
     Actual: mock(<__main__.Foo object at 0x...>)

對我們的 ‘Foo’ 類別的比較函式看起來可能會像這樣：

     >>> def compare(self, other):
     ...     if not type(self) == type(other):
     ...         return False
     ...     if self.a != other.a:
     ...         return False
     ...     if self.b != other.b:
     ...         return False
     ...     return True
     ...

而可以使用像這樣的比較函式進行其相等性運算的匹配器物件會長得像這樣：

     >>> class Matcher:
     ...     def __init__(self, compare, some_obj):
     ...         self.compare = compare
     ...         self.some_obj = some_obj
     ...     def __eq__(self, other):
     ...         return self.compare(self.some_obj, other)
     ...

把這些都放在一起：

     >>> match_foo = Matcher(compare, Foo(1, 2))
     >>> mock.assert_called_with(match_foo)

‘Matcher’ 是用我們想要比較的 ‘Foo’ 物件和比較函式實例化的。在
‘assert_called_with’ 中，‘Matcher’ 相等方法將被呼叫，它將呼叫 mock 時傳
入的物件與我們建立匹配器時傳入的物件進行比較。如果它們匹配，則
‘assert_called_with’ 會通過，如果它們不匹配，則會引發 *note
AssertionError: 64e.：

     >>> match_wrong = Matcher(compare, Foo(3, 4))
     >>> mock.assert_called_with(match_wrong)
     Traceback (most recent call last):
         ...
     AssertionError: Expected: ((<Matcher object at 0x...>,), {})
     Called with: ((<Foo object at 0x...>,), {})

透過一些調整，你可以讓比較函式直接引發 *note AssertionError: 64e. 並提供
更有用的失敗訊息。

從版本 1.5 開始，Python 測試函式庫 PyHamcrest(1) 以其相等匹配器的形式，
提供了類似的功能，在這裡可能是有用的
(hamcrest.library.integration.match_equality(2))。

   ---------- Footnotes ----------

   (1) https://pyhamcrest.readthedocs.io/

   (2) 
https://pyhamcrest.readthedocs.io/en/release-1.8/integration/#module-hamcrest.library.integration.match_equality


File: python.info,  Node: test --- Python 的回歸測試 regression tests 套件,  Next: test support --- Python 測試套件的工具,  Prev: unittest mock --- 入門指南,  Up: 開發工具

5.26.8 ‘test’ -- Python 的回歸測試 (regression tests) 套件
----------------------------------------------------------

     備註: The *note test: cb. package is meant for internal use by
     Python only.  It is documented for the benefit of the core
     developers of Python.  Any use of this package outside of Python's
     standard library is discouraged as code mentioned here can change
     or be removed without notice between releases of Python.

__________________________________________________________________

The *note test: cb. package contains all regression tests for Python as
well as the modules *note test.support: cd. and *note test.regrtest: cc.
*note test.support: cd. is used to enhance your tests while *note
test.regrtest: cc. drives the testing suite.

Each module in the *note test: cb. package whose name starts with
‘test_’ is a testing suite for a specific module or feature.  All new
tests should be written using the *note unittest: ef. or *note doctest:
31. module.  Some older tests are written using a "traditional" testing
style that compares output printed to ‘sys.stdout’; this style of test
is considered deprecated.

也參考
......

*note unittest: ef. 模組

     撰寫 PyUnit 回歸測試。

*note doctest: 31. 模組

     鑲嵌在文件字串中的測試。

* Menu:

* 撰寫 test 套件的單元測試::
* 使用命令列介面執行測試::


File: python.info,  Node: 撰寫 test 套件的單元測試,  Next: 使用命令列介面執行測試,  Up: test --- Python 的回歸測試 regression tests 套件

5.26.8.1 撰寫 ‘test’ 套件的單元測試
...................................

It is preferred that tests that use the *note unittest: ef. module
follow a few guidelines.  One is to name the test module by starting it
with ‘test_’ and end it with the name of the module being tested.  The
test methods in the test module should start with ‘test_’ and end with a
description of what the method is testing.  This is needed so that the
methods are recognized by the test driver as test methods.  Also, no
documentation string for the method should be included.  A comment (such
as ‘# Tests function returns only True or False’) should be used to
provide documentation for test methods.  This is done because
documentation strings get printed out if they exist and thus what test
is being run is not stated.

A basic boilerplate is often used:

     import unittest
     from test import support

     class MyTestCase1(unittest.TestCase):

         # Only use setUp() and tearDown() if necessary

         def setUp(self):
             ... code to execute in preparation for tests ...

         def tearDown(self):
             ... code to execute to clean up after tests ...

         def test_feature_one(self):
             # Test feature one.
             ... testing code ...

         def test_feature_two(self):
             # Test feature two.
             ... testing code ...

         ... more test methods ...

     class MyTestCase2(unittest.TestCase):
         ... same structure as MyTestCase1 ...

     ... more test classes ...

     if __name__ == '__main__':
         unittest.main()

This code pattern allows the testing suite to be run by *note
test.regrtest: cc, on its own as a script that supports the *note
unittest: ef. CLI, or via the ‘python -m unittest’ CLI.

The goal for regression testing is to try to break code.  This leads to
a few guidelines to be followed:

   * The testing suite should exercise all classes, functions, and
     constants.  This includes not just the external API that is to be
     presented to the outside world but also "private" code.

   * Whitebox testing (examining the code being tested when the tests
     are being written) is preferred.  Blackbox testing (testing only
     the published user interface) is not complete enough to make sure
     all boundary and edge cases are tested.

   * Make sure all possible values are tested including invalid ones.
     This makes sure that not only all valid values are acceptable but
     also that improper values are handled correctly.

   * Exhaust as many code paths as possible.  Test where branching
     occurs and thus tailor input to make sure as many different paths
     through the code are taken.

   * Add an explicit test for any bugs discovered for the tested code.
     This will make sure that the error does not crop up again if the
     code is changed in the future.

   * Make sure to clean up after your tests (such as close and remove
     all temporary files).

   * If a test is dependent on a specific condition of the operating
     system then verify the condition already exists before attempting
     the test.

   * Import as few modules as possible and do it as soon as possible.
     This minimizes external dependencies of tests and also minimizes
     possible anomalous behavior from side-effects of importing a
     module.

   * Try to maximize code reuse.  On occasion, tests will vary by
     something as small as what type of input is used.  Minimize code
     duplication by subclassing a basic test class with a class that
     specifies the input:

          class TestFuncAcceptsSequencesMixin:

              func = mySuperWhammyFunction

              def test_func(self):
                  self.func(self.arg)

          class AcceptLists(TestFuncAcceptsSequencesMixin, unittest.TestCase):
              arg = [1, 2, 3]

          class AcceptStrings(TestFuncAcceptsSequencesMixin, unittest.TestCase):
              arg = 'abc'

          class AcceptTuples(TestFuncAcceptsSequencesMixin, unittest.TestCase):
              arg = (1, 2, 3)

     When using this pattern, remember that all classes that inherit
     from *note unittest.TestCase: 3f4. are run as tests.  The
     ‘TestFuncAcceptsSequencesMixin’ class in the example above does not
     have any data and so can't be run by itself, thus it does not
     inherit from *note unittest.TestCase: 3f4.

也參考
......

測試驅動開發

     由 Kent Beck 所著，關於先寫測試再寫程式的書籍。


File: python.info,  Node: 使用命令列介面執行測試,  Prev: 撰寫 test 套件的單元測試,  Up: test --- Python 的回歸測試 regression tests 套件

5.26.8.2 使用命令列介面執行測試
...............................

The *note test: cb. package can be run as a script to drive Python's
regression test suite, thanks to the *note -m: 585. option: ‘python -m
test’.  Under the hood, it uses *note test.regrtest: cc.; the call
‘python -m test.regrtest’ used in previous Python versions still works.
Running the script by itself automatically starts running all regression
tests in the *note test: cb. package.  It does this by finding all
modules in the package whose name starts with ‘test_’, importing them,
and executing the function ‘test_main()’ if present or loading the tests
via unittest.TestLoader.loadTestsFromModule if ‘test_main’ does not
exist.  The names of tests to execute may also be passed to the script.
Specifying a single regression test (‘python -m test test_spam’) will
minimize output and only print whether the test passed or failed.

Running *note test: cb. directly allows what resources are available for
tests to use to be set.  You do this by using the ‘-u’ command-line
option.  Specifying ‘all’ as the value for the ‘-u’ option enables all
possible resources: ‘python -m test -uall’.  If all but one resource is
desired (a more common case), a comma-separated list of resources that
are not desired may be listed after ‘all’.  The command ‘python -m test
-uall,-audio,-largefile’ will run *note test: cb. with all resources
except the ‘audio’ and ‘largefile’ resources.  For a list of all
resources and more command-line options, run ‘python -m test -h’.

Some other ways to execute the regression tests depend on what platform
the tests are being executed on.  On Unix, you can run ‘make test’ at
the top-level directory where Python was built.  On Windows, executing
‘rt.bat’ from your ‘PCbuild’ directory will run all regression tests.


File: python.info,  Node: test support --- Python 測試套件的工具,  Next: test support socket_helper --- 用於 socket 測試的工具,  Prev: test --- Python 的回歸測試 regression tests 套件,  Up: 開發工具

5.26.9 ‘test.support’ -- Python 測試套件的工具
----------------------------------------------

*note test.support: cd. 模組提供 Python 回歸測試套件的支援。

     備註: *note test.support: cd. is not a public module.  It is
     documented here to help Python developers write tests.  The API of
     this module is subject to change without backwards compatibility
     concerns between releases.

此模組定義了以下例外：

 -- 例外: test.support.TestFailed

     Exception to be raised when a test fails.  This is deprecated in
     favor of *note unittest: ef.-based tests and *note
     unittest.TestCase: 3f4.'s assertion methods.

 -- 例外: test.support.ResourceDenied

     Subclass of *note unittest.SkipTest: f87.  Raised when a resource
     (such as a network connection) is not available.  Raised by the
     *note requires(): 3f46. function.

*note test.support: cd. 模組定義了以下常數：

 -- 資料: test.support.verbose

     ‘True’ when verbose output is enabled.  Should be checked when more
     detailed information is desired about a running test.  'verbose' is
     set by *note test.regrtest: cc.

 -- 資料: test.support.is_jython

     如果執行的直譯器是 Jython，則為 ‘True’。

 -- 資料: test.support.is_android

     如果系統是 Android，則為 ‘True’。

 -- 資料: test.support.unix_shell

     Path for shell if not on Windows; otherwise ‘None’.

 -- 資料: test.support.LOOPBACK_TIMEOUT

     Timeout in seconds for tests using a network server listening on
     the network local loopback interface like ‘127.0.0.1’.

     The timeout is long enough to prevent test failure: it takes into
     account that the client and the server can run in different threads
     or even different processes.

     The timeout should be long enough for *note connect(): d49, *note
     recv(): d4a. and *note send(): d4d. methods of *note socket.socket:
     d47.

     預設值為 5 秒。

     另請參閱 *note INTERNET_TIMEOUT: 18b9.。

 -- 資料: test.support.INTERNET_TIMEOUT

     Timeout in seconds for network requests going to the internet.

     The timeout is short enough to prevent a test to wait for too long
     if the internet request is blocked for whatever reason.

     Usually, a timeout using *note INTERNET_TIMEOUT: 18b9. should not
     mark a test as failed, but skip the test instead: see *note
     transient_internet(): 3f4b.

     預設值為 1 分鐘。

     另請參閱 *note LOOPBACK_TIMEOUT: 18b8.。

 -- 資料: test.support.SHORT_TIMEOUT

     Timeout in seconds to mark a test as failed if the test takes "too
     long".

     The timeout value depends on the regrtest ‘--timeout’ command line
     option.

     If a test using *note SHORT_TIMEOUT: 17b1. starts to fail randomly
     on slow buildbots, use *note LONG_TIMEOUT: 18ba. instead.

     預設值為 30 秒。

 -- 資料: test.support.LONG_TIMEOUT

     Timeout in seconds to detect when a test hangs.

     It is long enough to reduce the risk of test failure on the slowest
     Python buildbots.  It should not be used to mark a test as failed
     if the test takes "too long".  The timeout value depends on the
     regrtest ‘--timeout’ command line option.

     預設值為 5 分鐘。

     請參閱 *note LOOPBACK_TIMEOUT: 18b8.、*note INTERNET_TIMEOUT: 18b9.
     和 *note SHORT_TIMEOUT: 17b1.。

 -- 資料: test.support.PGO

     Set when tests can be skipped when they are not useful for PGO.

 -- 資料: test.support.PIPE_MAX_SIZE

     A constant that is likely larger than the underlying OS pipe buffer
     size, to make writes blocking.

 -- 資料: test.support.Py_DEBUG

     ‘True’ if Python was built with the *note Py_DEBUG: 3f4f. macro
     defined, that is, if Python was *note built in debug mode: 1de.

     在 3.12 版被加入.

 -- 資料: test.support.SOCK_MAX_SIZE

     A constant that is likely larger than the underlying OS socket
     buffer size, to make writes blocking.

 -- 資料: test.support.TEST_SUPPORT_DIR

     設定為包含 *note test.support: cd. 的頂層目錄。

 -- 資料: test.support.TEST_HOME_DIR

     設定為測試套件的頂層目錄。

 -- 資料: test.support.TEST_DATA_DIR

     設定為測試套件中的 ‘data’ 目錄。

 -- 資料: test.support.MAX_Py_ssize_t

     設定為 *note sys.maxsize: 115d. 以進行大記憶體測試。

 -- 資料: test.support.max_memuse

     Set by *note set_memlimit(): 3f56. as the memory limit for big
     memory tests.  Limited by *note MAX_Py_ssize_t: 3f54.

 -- 資料: test.support.real_max_memuse

     Set by *note set_memlimit(): 3f56. as the memory limit for big
     memory tests.  Not limited by *note MAX_Py_ssize_t: 3f54.

 -- 資料: test.support.MISSING_C_DOCSTRINGS

     Set to ‘True’ if Python is built without docstrings (the
     ‘WITH_DOC_STRINGS’ macro is not defined).  See the *note configure
     -without-doc-strings: 1cb0. option.

     See also the *note HAVE_DOCSTRINGS: 3f59. variable.

 -- 資料: test.support.HAVE_DOCSTRINGS

     Set to ‘True’ if function docstrings are available.  See the *note
     python -OO: d5b. option, which strips docstrings of functions
     implemented in Python.

     請參閱 *note MISSING_C_DOCSTRINGS: 3f58. 變數。

 -- 資料: test.support.TEST_HTTP_URL

     Define the URL of a dedicated HTTP server for the network tests.

 -- 資料: test.support.ALWAYS_EQ

     Object that is equal to anything.  Used to test mixed type
     comparison.

 -- 資料: test.support.NEVER_EQ

     Object that is not equal to anything (even to *note ALWAYS_EQ:
     3f5b.).  Used to test mixed type comparison.

 -- 資料: test.support.LARGEST

     Object that is greater than anything (except itself).  Used to test
     mixed type comparison.

 -- 資料: test.support.SMALLEST

     Object that is less than anything (except itself).  Used to test
     mixed type comparison.

*note test.support: cd. 模組定義了以下函式：

 -- 函式: test.support.busy_retry (timeout, err_msg=None, /, *,
          error=True)

     執行迴圈主體直到 ‘break’ 停止迴圈。

     After 'timeout' seconds, raise an *note AssertionError: 64e. if
     'error' is true, or just stop the loop if 'error' is false.

     範例：

          for _ in support.busy_retry(support.SHORT_TIMEOUT):
              if check():
                  break

     error=False 用法範例：

          for _ in support.busy_retry(support.SHORT_TIMEOUT, error=False):
              if check():
                  break
          else:
              raise RuntimeError('my custom error')

 -- 函式: test.support.sleeping_retry (timeout, err_msg=None, /, *,
          init_delay=0.010, max_delay=1.0, error=True)

     Wait strategy that applies exponential backoff.

     Run the loop body until ‘break’ stops the loop.  Sleep at each loop
     iteration, but not at the first iteration.  The sleep delay is
     doubled at each iteration (up to 'max_delay' seconds).

     請見 *note busy_retry(): 3f5f. 文件以瞭解參數用法。

     在 SHORT_TIMEOUT 秒後引發例外的範例：

          for _ in support.sleeping_retry(support.SHORT_TIMEOUT):
              if check():
                  break

     error=False 用法範例：

          for _ in support.sleeping_retry(support.SHORT_TIMEOUT, error=False):
              if check():
                  break
          else:
              raise RuntimeError('my custom error')

 -- 函式: test.support.is_resource_enabled (resource)

     Return ‘True’ if 'resource' is enabled and available.  The list of
     available resources is only set when *note test.regrtest: cc. is
     executing the tests.

 -- 函式: test.support.python_is_optimized ()

     如果 Python 不是使用 ‘-O0’ 或 ‘-Og’ 建置則回傳 ‘True’。

 -- 函式: test.support.with_pymalloc ()

     回傳 ‘_testcapi.WITH_PYMALLOC’。

 -- 函式: test.support.requires (resource, msg=None)

     Raise *note ResourceDenied: 3f45. if 'resource' is not available.
     'msg' is the argument to *note ResourceDenied: 3f45. if it is
     raised.  Always returns ‘True’ if called by a function whose
     ‘__name__’ is ‘'__main__'’.  Used when tests are executed by *note
     test.regrtest: cc.

 -- 函式: test.support.sortdict (dict)

     Return a repr of 'dict' with keys sorted.

 -- 函式: test.support.findfile (filename, subdir=None)

     Return the path to the file named 'filename'.  If no match is found
     'filename' is returned.  This does not equal a failure since it
     could be the path to the file.

     Setting 'subdir' indicates a relative path to use to find the file
     rather than looking directly in the path directories.

 -- 函式: test.support.get_pagesize ()

     Get size of a page in bytes.

     在 3.12 版被加入.

 -- 函式: test.support.setswitchinterval (interval)

     Set the *note sys.setswitchinterval(): 8ee. to the given
     'interval'.  Defines a minimum interval for Android systems to
     prevent the system from hanging.

 -- 函式: test.support.check_impl_detail (**guards)

     Use this check to guard CPython's implementation-specific tests or
     to run them only on the implementations guarded by the arguments.
     This function returns ‘True’ or ‘False’ depending on the host
     platform.  Example usage:

          check_impl_detail()               # Only on CPython (default).
          check_impl_detail(jython=True)    # Only on Jython.
          check_impl_detail(cpython=False)  # Everywhere except CPython.

 -- 函式: test.support.set_memlimit (limit)

     Set the values for *note max_memuse: 3f55. and *note
     real_max_memuse: 3f57. for big memory tests.

 -- 函式: test.support.record_original_stdout (stdout)

     Store the value from 'stdout'.  It is meant to hold the stdout at
     the time the regrtest began.

 -- 函式: test.support.get_original_stdout ()

     Return the original stdout set by *note record_original_stdout():
     3f69. or ‘sys.stdout’ if it's not set.

 -- 函式: test.support.args_from_interpreter_flags ()

     Return a list of command line arguments reproducing the current
     settings in ‘sys.flags’ and ‘sys.warnoptions’.

 -- 函式: test.support.optim_args_from_interpreter_flags ()

     Return a list of command line arguments reproducing the current
     optimization settings in ‘sys.flags’.

 -- 函式: test.support.captured_stdin ()
 -- 函式: test.support.captured_stdout ()
 -- 函式: test.support.captured_stderr ()

     A context managers that temporarily replaces the named stream with
     *note io.StringIO: ecb. object.

     使用輸出串流的範例：

          with captured_stdout() as stdout, captured_stderr() as stderr:
              print("hello")
              print("error", file=sys.stderr)
          assert stdout.getvalue() == "hello\n"
          assert stderr.getvalue() == "error\n"

     使用輸入串流的範例：

          with captured_stdin() as stdin:
              stdin.write('hello\n')
              stdin.seek(0)
              # call test code that consumes from sys.stdin
              captured = input()
          self.assertEqual(captured, "hello")

 -- 函式: test.support.disable_faulthandler ()

     A context manager that temporary disables *note faulthandler: 4e.

 -- 函式: test.support.gc_collect ()

     Force as many objects as possible to be collected.  This is needed
     because timely deallocation is not guaranteed by the garbage
     collector.  This means that ‘__del__’ methods may be called later
     than expected and weakrefs may remain alive for longer than
     expected.

 -- 函式: test.support.disable_gc ()

     A context manager that disables the garbage collector on entry.  On
     exit, the garbage collector is restored to its prior state.

 -- 函式: test.support.swap_attr (obj, attr, new_val)

     Context manager to swap out an attribute with a new object.

     用法：

          with swap_attr(obj, "attr", 5):
              ...

     This will set ‘obj.attr’ to 5 for the duration of the ‘with’ block,
     restoring the old value at the end of the block.  If ‘attr’ doesn't
     exist on ‘obj’, it will be created and then deleted at the end of
     the block.

     The old value (or ‘None’ if it doesn't exist) will be assigned to
     the target of the "as" clause, if there is one.

 -- 函式: test.support.swap_item (obj, attr, new_val)

     Context manager to swap out an item with a new object.

     用法：

          with swap_item(obj, "item", 5):
              ...

     This will set ‘obj["item"]’ to 5 for the duration of the ‘with’
     block, restoring the old value at the end of the block.  If ‘item’
     doesn't exist on ‘obj’, it will be created and then deleted at the
     end of the block.

     The old value (or ‘None’ if it doesn't exist) will be assigned to
     the target of the "as" clause, if there is one.

 -- 函式: test.support.flush_std_streams ()

     Call the ‘flush()’ method on *note sys.stdout: a79. and then on
     *note sys.stderr: 8dd.  It can be used to make sure that the logs
     order is consistent before writing into stderr.

     在 3.11 版被加入.

 -- 函式: test.support.print_warning (msg)

     Print a warning into *note sys.__stderr__: 3f76.  Format the
     message as: ‘f"Warning -- {msg}"’.  If 'msg' is made of multiple
     lines, add ‘"Warning -- "’ prefix to each line.

     在 3.9 版被加入.

 -- 函式: test.support.wait_process (pid, *, exitcode, timeout=None)

     Wait until process 'pid' completes and check that the process exit
     code is 'exitcode'.

     如果行程退出代號不等於 'exitcode' 則引發 *note AssertionError:
     64e.。

     If the process runs longer than 'timeout' seconds (*note
     SHORT_TIMEOUT: 17b1. by default), kill the process and raise an
     *note AssertionError: 64e.  The timeout feature is not available on
     Windows.

     在 3.9 版被加入.

 -- 函式: test.support.calcobjsize (fmt)

     Return the size of the *note PyObject: 311. whose structure members
     are defined by 'fmt'.  The returned value includes the size of the
     Python object header and alignment.

 -- 函式: test.support.calcvobjsize (fmt)

     Return the size of the *note PyVarObject: 3f79. whose structure
     members are defined by 'fmt'.  The returned value includes the size
     of the Python object header and alignment.

 -- 函式: test.support.checksizeof (test, o, size)

     For testcase 'test', assert that the ‘sys.getsizeof’ for 'o' plus
     the GC header size equals 'size'.

 -- 函式: @test.support.anticipate_failure (condition)

     A decorator to conditionally mark tests with *note
     unittest.expectedFailure(): 3e91.  Any use of this decorator should
     have an associated comment identifying the relevant tracker issue.

 -- 函式: test.support.system_must_validate_cert (f)

     A decorator that skips the decorated test on TLS certification
     validation failures.

 -- 函式: @test.support.run_with_locale (catstr, *locales)

     A decorator for running a function in a different locale, correctly
     resetting it after it has finished.  'catstr' is the locale
     category as a string (for example ‘"LC_ALL"’).  The 'locales'
     passed will be tried sequentially, and the first valid locale will
     be used.

 -- 函式: @test.support.run_with_tz (tz)

     A decorator for running a function in a specific timezone,
     correctly resetting it after it has finished.

 -- 函式: @test.support.requires_freebsd_version (*min_version)

     Decorator for the minimum version when running test on FreeBSD. If
     the FreeBSD version is less than the minimum, the test is skipped.

 -- 函式: @test.support.requires_linux_version (*min_version)

     Decorator for the minimum version when running test on Linux.  If
     the Linux version is less than the minimum, the test is skipped.

 -- 函式: @test.support.requires_mac_version (*min_version)

     Decorator for the minimum version when running test on macOS. If
     the macOS version is less than the minimum, the test is skipped.

 -- 函式: @test.support.requires_gil_enabled

     Decorator for skipping tests on the free-threaded build.  If the
     *note GIL: 13e. is disabled, the test is skipped.

 -- 函式: @test.support.requires_IEEE_754

     Decorator for skipping tests on non-IEEE 754 platforms.

 -- 函式: @test.support.requires_zlib

     如果 *note zlib: 119. 不存在則跳過測試的裝飾器。

 -- 函式: @test.support.requires_gzip

     如果 *note gzip: 5d. 不存在則跳過測試的裝飾器。

 -- 函式: @test.support.requires_bz2

     如果 *note bz2: f. 不存在則跳過測試的裝飾器。

 -- 函式: @test.support.requires_lzma

     如果 *note lzma: 7e. 不存在則跳過測試的裝飾器。

 -- 函式: @test.support.requires_resource (resource)

     如果 'resource' 不可用則跳過測試的裝飾器。

 -- 函式: @test.support.requires_docstrings

     Decorator for only running the test if *note HAVE_DOCSTRINGS: 3f59.

 -- 函式: @test.support.requires_limited_api

     Decorator for only running the test if *note Limited C API: 318. is
     available.

 -- 函式: @test.support.cpython_only

     Decorator for tests only applicable to CPython.

 -- 函式: @test.support.impl_detail (msg=None, **guards)

     Decorator for invoking *note check_impl_detail(): 3f68. on
     'guards'.  If that returns ‘False’, then uses 'msg' as the reason
     for skipping the test.

 -- 函式: @test.support.no_tracing

     Decorator to temporarily turn off tracing for the duration of the
     test.

 -- 函式: @test.support.refcount_test

     Decorator for tests which involve reference counting.  The
     decorator does not run the test if it is not run by CPython.  Any
     trace function is unset for the duration of the test to prevent
     unexpected refcounts caused by the trace function.

 -- 函式: @test.support.bigmemtest (size, memuse, dry_run=True)

     大記憶體測試的裝飾器。

     'size' is a requested size for the test (in arbitrary,
     test-interpreted units.)  'memuse' is the number of bytes per unit
     for the test, or a good estimate of it.  For example, a test that
     needs two byte buffers, of 4 GiB each, could be decorated with
     ‘@bigmemtest(size=_4G, memuse=2)’.

     The 'size' argument is normally passed to the decorated test method
     as an extra argument.  If 'dry_run' is ‘True’, the value passed to
     the test method may be less than the requested value.  If 'dry_run'
     is ‘False’, it means the test doesn't support dummy runs when ‘-M’
     is not specified.

 -- 函式: @test.support.bigaddrspacetest

     Decorator for tests that fill the address space.

 -- 函式: test.support.check_syntax_error (testcase, statement,
          errtext='', *, lineno=None, offset=None)

     Test for syntax errors in 'statement' by attempting to compile
     'statement'.  'testcase' is the *note unittest: ef. instance for
     the test.  'errtext' is the regular expression which should match
     the string representation of the raised *note SyntaxError: 173.  If
     'lineno' is not ‘None’, compares to the line of the exception.  If
     'offset' is not ‘None’, compares to the offset of the exception.

 -- 函式: test.support.open_urlresource (url, *args, **kw)

     Open 'url'.  If open fails, raises *note TestFailed: 3f44.

 -- 函式: test.support.reap_children ()

     Use this at the end of ‘test_main’ whenever sub-processes are
     started.  This will help ensure that no extra children (zombies)
     stick around to hog resources and create problems when looking for
     refleaks.

 -- 函式: test.support.get_attribute (obj, name)

     Get an attribute, raising *note unittest.SkipTest: f87. if *note
     AttributeError: 2f6. is raised.

 -- 函式: test.support.catch_unraisable_exception ()

     Context manager catching unraisable exception using *note
     sys.unraisablehook(): 1dc.

     Storing the exception value (‘cm.unraisable.exc_value’) creates a
     reference cycle.  The reference cycle is broken explicitly when the
     context manager exits.

     Storing the object (‘cm.unraisable.object’) can resurrect it if it
     is set to an object which is being finalized.  Exiting the context
     manager clears the stored object.

     用法：

          with support.catch_unraisable_exception() as cm:
              # code creating an "unraisable exception"
              ...

              # check the unraisable exception: use cm.unraisable
              ...

          # cm.unraisable attribute no longer exists at this point
          # (to break a reference cycle)

     在 3.8 版被加入.

 -- 函式: test.support.load_package_tests (pkg_dir, loader,
          standard_tests, pattern)

     Generic implementation of the *note unittest: ef. ‘load_tests’
     protocol for use in test packages.  'pkg_dir' is the root directory
     of the package; 'loader', 'standard_tests', and 'pattern' are the
     arguments expected by ‘load_tests’.  In simple cases, the test
     package's ‘__init__.py’ can be the following:

          import os
          from test.support import load_package_tests

          def load_tests(*args):
              return load_package_tests(os.path.dirname(__file__), *args)

 -- 函式: test.support.detect_api_mismatch (ref_api, other_api, *,
          ignore=())

     Returns the set of attributes, functions or methods of 'ref_api'
     not found on 'other_api', except for a defined list of items to be
     ignored in this check specified in 'ignore'.

     這預設會跳過以 '_' 開頭的私有屬性，但會包含所有魔術方法，即以 '__'
     開頭和結尾的方法。

     在 3.5 版被加入.

 -- 函式: test.support.patch (test_instance, object_to_patch, attr_name,
          new_value)

     Override 'object_to_patch.attr_name' with 'new_value'.  Also add
     cleanup procedure to 'test_instance' to restore 'object_to_patch'
     for 'attr_name'.  The 'attr_name' should be a valid attribute for
     'object_to_patch'.

 -- 函式: test.support.run_in_subinterp (code)

     Run 'code' in subinterpreter.  Raise *note unittest.SkipTest: f87.
     if *note tracemalloc: e8. is enabled.

 -- 函式: test.support.check_free_after_iterating (test, iter, cls,
          args=())

     Assert instances of 'cls' are deallocated after iterating.

 -- 函式: test.support.missing_compiler_executable (cmd_names=[])

     Check for the existence of the compiler executables whose names are
     listed in 'cmd_names' or all the compiler executables when
     'cmd_names' is empty and return the first missing executable or
     ‘None’ when none is found missing.

 -- 函式: test.support.check__all__ (test_case, module,
          name_of_module=None, extra=(), not_exported=())

     Assert that the ‘__all__’ variable of 'module' contains all public
     names.

     The module's public names (its API) are detected automatically
     based on whether they match the public name convention and were
     defined in 'module'.

     The 'name_of_module' argument can specify (as a string or tuple
     thereof) what module(s) an API could be defined in order to be
     detected as a public API. One case for this is when 'module'
     imports part of its public API from other modules, possibly a C
     backend (like ‘csv’ and its ‘_csv’).

     The 'extra' argument can be a set of names that wouldn't otherwise
     be automatically detected as "public", like objects without a
     proper ‘__module__’ attribute.  If provided, it will be added to
     the automatically detected ones.

     The 'not_exported' argument can be a set of names that must not be
     treated as part of the public API even though their names indicate
     otherwise.

     用法範例：

          import bar
          import foo
          import unittest
          from test import support

          class MiscTestCase(unittest.TestCase):
              def test__all__(self):
                  support.check__all__(self, foo)

          class OtherTestCase(unittest.TestCase):
              def test__all__(self):
                  extra = {'BAR_CONST', 'FOO_CONST'}
                  not_exported = {'baz'}  # Undocumented name.
                  # bar imports part of its API from _bar.
                  support.check__all__(self, bar, ('bar', '_bar'),
                                       extra=extra, not_exported=not_exported)

     在 3.6 版被加入.

 -- 函式: test.support.skip_if_broken_multiprocessing_synchronize ()

     Skip tests if the ‘multiprocessing.synchronize’ module is missing,
     if there is no available semaphore implementation, or if creating a
     lock raises an *note OSError: 350.

     在 3.10 版被加入.

 -- 函式: test.support.check_disallow_instantiation (test_case, tp,
          *args, **kwds)

     Assert that type 'tp' cannot be instantiated using 'args' and
     'kwds'.

     在 3.10 版被加入.

 -- 函式: test.support.adjust_int_max_str_digits (max_digits)

     This function returns a context manager that will change the global
     *note sys.set_int_max_str_digits(): 16c1. setting for the duration
     of the context to allow execution of test code that needs a
     different limit on the number of digits when converting between an
     integer and string.

     在 3.11 版被加入.

*note test.support: cd. 模組定義了以下類別：

 -- 類別: test.support.SuppressCrashReport

     A context manager used to try to prevent crash dialog popups on
     tests that are expected to crash a subprocess.

     On Windows, it disables Windows Error Reporting dialogs using
     SetErrorMode(1).

     On UNIX, *note resource.setrlimit(): 3f9e. is used to set *note
     resource.RLIMIT_CORE: 3f9f.'s soft limit to 0 to prevent coredump
     file creation.

     在兩個平台上，舊值會被 *note __exit__(): 1293. 還原。

 -- 類別: test.support.SaveSignals

     Class to save and restore signal handlers registered by the Python
     signal handler.

      -- 方法: save (self)

          Save the signal handlers to a dictionary mapping signal
          numbers to the current signal handler.

      -- 方法: restore (self)

          Set the signal numbers from the *note save(): 3fa1. dictionary
          to the saved handler.

 -- 類別: test.support.Matcher

      -- 方法: matches (self, d, **kwargs)

          Try to match a single dict with the supplied arguments.

      -- 方法: match_value (self, k, dv, v)

          Try to match a single stored value ('dv') with a supplied
          value ('v').

   ---------- Footnotes ----------

   (1) 
https://msdn.microsoft.com/en-us/library/windows/desktop/ms680621.aspx


File: python.info,  Node: test support socket_helper --- 用於 socket 測試的工具,  Next: test support script_helper --- 用於 Python 執行測試的工具,  Prev: test support --- Python 測試套件的工具,  Up: 開發工具

5.26.10 ‘test.support.socket_helper’ -- 用於 socket 測試的工具
--------------------------------------------------------------

The *note test.support.socket_helper: d2. module provides support for
socket tests.

在 3.9 版被加入.

 -- 資料: test.support.socket_helper.IPV6_ENABLED

     Set to ‘True’ if IPv6 is enabled on this host, ‘False’ otherwise.

 -- 函式: test.support.socket_helper.find_unused_port
          (family=socket.AF_INET, socktype=socket.SOCK_STREAM)

     Returns an unused port that should be suitable for binding.  This
     is achieved by creating a temporary socket with the same family and
     type as the ‘sock’ parameter (default is *note AF_INET: 1722, *note
     SOCK_STREAM: 1286.), and binding it to the specified host address
     (defaults to ‘0.0.0.0’) with the port set to 0, eliciting an unused
     ephemeral port from the OS. The temporary socket is then closed and
     deleted, and the ephemeral port is returned.

     Either this method or *note bind_port(): 3fa9. should be used for
     any tests where a server socket needs to be bound to a particular
     port for the duration of the test.  Which one to use depends on
     whether the calling code is creating a Python socket, or if an
     unused port needs to be provided in a constructor or passed to an
     external program (i.e.  the ‘-accept’ argument to openssl's
     s_server mode).  Always prefer *note bind_port(): 3fa9. over *note
     find_unused_port(): 3fa8. where possible.  Using a hard coded port
     is discouraged since it can make multiple instances of the test
     impossible to run simultaneously, which is a problem for buildbots.

 -- 函式: test.support.socket_helper.bind_port (sock, host=HOST)

     Bind the socket to a free port and return the port number.  Relies
     on ephemeral ports in order to ensure we are using an unbound port.
     This is important as many tests may be running simultaneously,
     especially in a buildbot environment.  This method raises an
     exception if the ‘sock.family’ is *note AF_INET: 1722. and
     ‘sock.type’ is *note SOCK_STREAM: 1286, and the socket has
     ‘SO_REUSEADDR’ or ‘SO_REUSEPORT’ set on it.  Tests should never set
     these socket options for TCP/IP sockets.  The only case for setting
     these options is testing multicasting via multiple UDP sockets.

     Additionally, if the ‘SO_EXCLUSIVEADDRUSE’ socket option is
     available (i.e.  on Windows), it will be set on the socket.  This
     will prevent anyone else from binding to our host/port for the
     duration of the test.

 -- 函式: test.support.socket_helper.bind_unix_socket (sock, addr)

     Bind a Unix socket, raising *note unittest.SkipTest: f87. if *note
     PermissionError: ce9. is raised.

 -- 函式: @test.support.socket_helper.skip_unless_bind_unix_socket

     A decorator for running tests that require a functional ‘bind()’
     for Unix sockets.

 -- 函式: test.support.socket_helper.transient_internet (resource_name,
          *, timeout=30.0, errnos=())

     A context manager that raises *note ResourceDenied: 3f45. when
     various issues with the internet connection manifest themselves as
     exceptions.


File: python.info,  Node: test support script_helper --- 用於 Python 執行測試的工具,  Next: test support bytecode_helper --- 用於測試位元組碼能正確產生的支援工具,  Prev: test support socket_helper --- 用於 socket 測試的工具,  Up: 開發工具

5.26.11 ‘test.support.script_helper’ -- 用於 Python 執行測試的工具
------------------------------------------------------------------

*note test.support.script_helper: d1. 模組提供 Python 的腳本執行測試的支
援。

 -- 函式: test.support.script_helper.interpreter_requires_environment ()

     Return ‘True’ if ‘sys.executable interpreter’ requires environment
     variables in order to be able to run at all.

     This is designed to be used with ‘@unittest.skipIf()’ to annotate
     tests that need to use an ‘assert_python*()’ function to launch an
     isolated mode (‘-I’) or no environment mode (‘-E’) sub-interpreter
     process.

     A normal build & test does not run into this situation but it can
     happen when trying to run the standard library test suite from an
     interpreter that doesn't have an obvious home with Python's current
     home finding logic.

     Setting *note PYTHONHOME: 387. is one way to get most of the
     testsuite to run in that situation.  *note PYTHONPATH: fbe. or
     ‘PYTHONUSERSITE’ are other common environment variables that might
     impact whether or not the interpreter can start.

 -- 函式: test.support.script_helper.run_python_until_end (*args,
          **env_vars)

     Set up the environment based on 'env_vars' for running the
     interpreter in a subprocess.  The values can include ‘__isolated’,
     ‘__cleanenv’, ‘__cwd’, and ‘TERM’.

     在 3.9 版的變更: 此函式不再從 'stderr' 中移除空白。

 -- 函式: test.support.script_helper.assert_python_ok (*args,
          **env_vars)

     Assert that running the interpreter with 'args' and optional
     environment variables 'env_vars' succeeds (‘rc == 0’) and return a
     ‘(return code, stdout, stderr)’ tuple.

     If the '__cleanenv' keyword-only parameter is set, 'env_vars' is
     used as a fresh environment.

     Python is started in isolated mode (command line option ‘-I’),
     except if the '__isolated' keyword-only parameter is set to
     ‘False’.

     在 3.9 版的變更: 此函式不再從 'stderr' 中移除空白。

 -- 函式: test.support.script_helper.assert_python_failure (*args,
          **env_vars)

     Assert that running the interpreter with 'args' and optional
     environment variables 'env_vars' fails (‘rc != 0’) and return a
     ‘(return code, stdout, stderr)’ tuple.

     更多選項請見 *note assert_python_ok(): 3faf.。

     在 3.9 版的變更: 此函式不再從 'stderr' 中移除空白。

 -- 函式: test.support.script_helper.spawn_python (*args,
          stdout=subprocess.PIPE, stderr=subprocess.STDOUT, **kw)

     Run a Python subprocess with the given arguments.

     'kw' is extra keyword args to pass to *note subprocess.Popen():
     17d.  Returns a *note subprocess.Popen: 17d. object.

 -- 函式: test.support.script_helper.kill_python (p)

     Run the given *note subprocess.Popen: 17d. process until completion
     and return stdout.

 -- 函式: test.support.script_helper.make_script (script_dir,
          script_basename, source, omit_suffix=False)

     Create script containing 'source' in path 'script_dir' and
     'script_basename'.  If 'omit_suffix' is ‘False’, append ‘.py’ to
     the name.  Return the full script path.

 -- 函式: test.support.script_helper.make_zip_script (zip_dir,
          zip_basename, script_name, name_in_zip=None)

     Create zip file at 'zip_dir' and 'zip_basename' with extension
     ‘zip’ which contains the files in 'script_name'.  'name_in_zip' is
     the archive name.  Return a tuple containing ‘(full path, full path
     of archive name)’.

 -- 函式: test.support.script_helper.make_pkg (pkg_dir, init_source='')

     Create a directory named 'pkg_dir' containing an ‘__init__’ file
     with 'init_source' as its contents.

 -- 函式: test.support.script_helper.make_zip_pkg (zip_dir,
          zip_basename, pkg_name, script_basename, source, depth=1,
          compiled=False)

     Create a zip package directory with a path of 'zip_dir' and
     'zip_basename' containing an empty ‘__init__’ file and a file
     'script_basename' containing the 'source'.  If 'compiled' is
     ‘True’, both source files will be compiled and added to the zip
     package.  Return a tuple of the full zip path and the archive name
     for the zip file.


File: python.info,  Node: test support bytecode_helper --- 用於測試位元組碼能正確產生的支援工具,  Next: test support threading_helper --- Utilities for threading tests,  Prev: test support script_helper --- 用於 Python 執行測試的工具,  Up: 開發工具

5.26.12 ‘test.support.bytecode_helper’ -- 用於測試位元組碼能正確產生的支援工具
------------------------------------------------------------------------------

*note test.support.bytecode_helper: ce. 模組提供測試和檢查位元組碼產生的
支援。

在 3.9 版被加入.

此模組定義了以下類別：

 -- 類別: test.support.bytecode_helper.BytecodeTestCase
          (unittest.TestCase)

     This class has custom assertion methods for inspecting bytecode.

 -- 方法: BytecodeTestCase.get_disassembly_as_string (co)

     Return the disassembly of 'co' as string.

 -- 方法: BytecodeTestCase.assertInBytecode (x, opname,
          argval=_UNSPECIFIED)

     Return instr if 'opname' is found, otherwise throws *note
     AssertionError: 64e.

 -- 方法: BytecodeTestCase.assertNotInBytecode (x, opname,
          argval=_UNSPECIFIED)

     Throws *note AssertionError: 64e. if 'opname' is found.


File: python.info,  Node: test support threading_helper --- Utilities for threading tests,  Next: test support os_helper --- 用於 os 測試的工具,  Prev: test support bytecode_helper --- 用於測試位元組碼能正確產生的支援工具,  Up: 開發工具

5.26.13 ‘test.support.threading_helper’ -- Utilities for threading tests
------------------------------------------------------------------------

The *note test.support.threading_helper: d3. module provides support for
threading tests.

在 3.10 版被加入.

 -- 函式: test.support.threading_helper.join_thread (thread,
          timeout=None)

     Join a 'thread' within 'timeout'.  Raise an *note AssertionError:
     64e. if thread is still alive after 'timeout' seconds.

 -- 函式: @test.support.threading_helper.reap_threads

     Decorator to ensure the threads are cleaned up even if the test
     fails.

 -- 函式: test.support.threading_helper.start_threads (threads,
          unlock=None)

     Context manager to start 'threads', which is a sequence of threads.
     'unlock' is a function called after the threads are started, even
     if an exception was raised; an example would be *note
     threading.Event.set(): 2f52.  ‘start_threads’ will attempt to join
     the started threads upon exit.

 -- 函式: test.support.threading_helper.threading_cleanup
          (*original_values)

     Cleanup up threads not specified in 'original_values'.  Designed to
     emit a warning if a test leaves running threads in the background.

 -- 函式: test.support.threading_helper.threading_setup ()

     Return current thread count and copy of dangling threads.

 -- 函式: test.support.threading_helper.wait_threads_exit (timeout=None)

     Context manager to wait until all threads created in the ‘with’
     statement exit.

 -- 函式: test.support.threading_helper.catch_threading_exception ()

     Context manager catching *note threading.Thread: 8f0. exception
     using *note threading.excepthook(): 7ef.

     當捕捉到例外時會設定的屬性：

        * ‘exc_type’

        * ‘exc_value’

        * ‘exc_traceback’

        * ‘thread’

     參閱 *note threading.excepthook(): 7ef. 文件。

     這些屬性會在離開情境管理器時被刪除。

     用法：

          with threading_helper.catch_threading_exception() as cm:
              # code spawning a thread which raises an exception
              ...

              # check the thread exception, use cm attributes:
              # exc_type, exc_value, exc_traceback, thread
              ...

          # exc_type, exc_value, exc_traceback, thread attributes of cm no longer
          # exists at this point
          # (to avoid reference cycles)

     在 3.8 版被加入.


File: python.info,  Node: test support os_helper --- 用於 os 測試的工具,  Next: test support import_helper --- 用於 import 測試的工具,  Prev: test support threading_helper --- Utilities for threading tests,  Up: 開發工具

5.26.14 ‘test.support.os_helper’ -- 用於 os 測試的工具
------------------------------------------------------

*note test.support.os_helper: d0. 模組提供 os 測試的支援。

在 3.10 版被加入.

 -- 資料: test.support.os_helper.FS_NONASCII

     A non-ASCII character encodable by *note os.fsencode(): bfc.

 -- 資料: test.support.os_helper.SAVEDCWD

     設定為 *note os.getcwd(): 1907.。

 -- 資料: test.support.os_helper.TESTFN

     Set to a name that is safe to use as the name of a temporary file.
     Any temporary file that is created should be closed and unlinked
     (removed).

 -- 資料: test.support.os_helper.TESTFN_NONASCII

     Set to a filename containing the *note FS_NONASCII: 3fc5.
     character, if it exists.  This guarantees that if the filename
     exists, it can be encoded and decoded with the default filesystem
     encoding.  This allows tests that require a non-ASCII filename to
     be easily skipped on platforms where they can't work.

 -- 資料: test.support.os_helper.TESTFN_UNENCODABLE

     Set to a filename (str type) that should not be able to be encoded
     by file system encoding in strict mode.  It may be ‘None’ if it's
     not possible to generate such a filename.

 -- 資料: test.support.os_helper.TESTFN_UNDECODABLE

     Set to a filename (bytes type) that should not be able to be
     decoded by file system encoding in strict mode.  It may be ‘None’
     if it's not possible to generate such a filename.

 -- 資料: test.support.os_helper.TESTFN_UNICODE

     Set to a non-ASCII name for a temporary file.

 -- 類別: test.support.os_helper.EnvironmentVarGuard

     Class used to temporarily set or unset environment variables.
     Instances can be used as a context manager and have a complete
     dictionary interface for querying/modifying the underlying
     ‘os.environ’.  After exit from the context manager all changes to
     environment variables done through this instance will be rolled
     back.

     在 3.1 版的變更: 新增字典介面。

 -- 類別: test.support.os_helper.FakePath (path)

     Simple *note path-like object: ac2.  It implements the *note
     __fspath__(): bf9. method which just returns the 'path' argument.
     If 'path' is an exception, it will be raised in ‘__fspath__()’.

 -- 方法: EnvironmentVarGuard.set (envvar, value)

     Temporarily set the environment variable ‘envvar’ to the value of
     ‘value’.

 -- 方法: EnvironmentVarGuard.unset (envvar)

     暫時取消環境變數 ‘envvar’。

 -- 函式: test.support.os_helper.can_symlink ()

     如果作業系統支援符號連結則回傳 ‘True’，否則回傳 ‘False’。

 -- 函式: test.support.os_helper.can_xattr ()

     如果作業系統支援 xattr 則回傳 ‘True’，否則回傳 ‘False’。

 -- 函式: test.support.os_helper.change_cwd (path, quiet=False)

     A context manager that temporarily changes the current working
     directory to 'path' and yields the directory.

     If 'quiet' is ‘False’, the context manager raises an exception on
     error.  Otherwise, it issues only a warning and keeps the current
     working directory the same.

 -- 函式: test.support.os_helper.create_empty_file (filename)

     Create an empty file with 'filename'.  If it already exists,
     truncate it.

 -- 函式: test.support.os_helper.fd_count ()

     Count the number of open file descriptors.

 -- 函式: test.support.os_helper.fs_is_case_insensitive (directory)

     Return ‘True’ if the file system for 'directory' is
     case-insensitive.

 -- 函式: test.support.os_helper.make_bad_fd ()

     Create an invalid file descriptor by opening and closing a
     temporary file, and returning its descriptor.

 -- 函式: test.support.os_helper.rmdir (filename)

     Call *note os.rmdir(): 108c. on 'filename'.  On Windows platforms,
     this is wrapped with a wait loop that checks for the existence of
     the file, which is needed due to antivirus programs that can hold
     files open and prevent deletion.

 -- 函式: test.support.os_helper.rmtree (path)

     Call *note shutil.rmtree(): 2d2. on 'path' or call *note
     os.lstat(): 449. and *note os.rmdir(): 108c. to remove a path and
     its contents.  As with *note rmdir(): 3fd6, on Windows platforms
     this is wrapped with a wait loop that checks for the existence of
     the files.

 -- 函式: @test.support.os_helper.skip_unless_symlink

     A decorator for running tests that require support for symbolic
     links.

 -- 函式: @test.support.os_helper.skip_unless_xattr

     A decorator for running tests that require support for xattr.

 -- 函式: test.support.os_helper.temp_cwd (name='tempcwd', quiet=False)

     A context manager that temporarily creates a new directory and
     changes the current working directory (CWD).

     The context manager creates a temporary directory in the current
     directory with name 'name' before temporarily changing the current
     working directory.  If 'name' is ‘None’, the temporary directory is
     created using *note tempfile.mkdtemp(): 204.

     If 'quiet' is ‘False’ and it is not possible to create or change
     the CWD, an error is raised.  Otherwise, only a warning is raised
     and the original CWD is used.

 -- 函式: test.support.os_helper.temp_dir (path=None, quiet=False)

     A context manager that creates a temporary directory at 'path' and
     yields the directory.

     If 'path' is ‘None’, the temporary directory is created using *note
     tempfile.mkdtemp(): 204.  If 'quiet' is ‘False’, the context
     manager raises an exception on error.  Otherwise, if 'path' is
     specified and cannot be created, only a warning is issued.

 -- 函式: test.support.os_helper.temp_umask (umask)

     A context manager that temporarily sets the process umask.

 -- 函式: test.support.os_helper.unlink (filename)

     Call *note os.unlink(): 108e. on 'filename'.  As with *note
     rmdir(): 3fd6, on Windows platforms, this is wrapped with a wait
     loop that checks for the existence of the file.


File: python.info,  Node: test support import_helper --- 用於 import 測試的工具,  Next: test support warnings_helper --- 用於 warnings 測試的工具,  Prev: test support os_helper --- 用於 os 測試的工具,  Up: 開發工具

5.26.15 ‘test.support.import_helper’ -- 用於 import 測試的工具
--------------------------------------------------------------

*note test.support.import_helper: cf. 模組提供 import 測試的支援。

在 3.10 版被加入.

 -- 函式: test.support.import_helper.forget (module_name)

     Remove the module named 'module_name' from ‘sys.modules’ and delete
     any byte-compiled files of the module.

 -- 函式: test.support.import_helper.import_fresh_module (name,
          fresh=(), blocked=(), deprecated=False)

     This function imports and returns a fresh copy of the named Python
     module by removing the named module from ‘sys.modules’ before doing
     the import.  Note that unlike ‘reload()’, the original module is
     not affected by this operation.

     'fresh' is an iterable of additional module names that are also
     removed from the ‘sys.modules’ cache before doing the import.

     'blocked' is an iterable of module names that are replaced with
     ‘None’ in the module cache during the import to ensure that
     attempts to import them raise *note ImportError: 352.

     The named module and any modules named in the 'fresh' and 'blocked'
     parameters are saved before starting the import and then reinserted
     into ‘sys.modules’ when the fresh import is complete.

     Module and package deprecation messages are suppressed during this
     import if 'deprecated' is ‘True’.

     如果無法引入指定的模組則此函式會引發 *note ImportError: 352.。

     用法範例：

          # Get copies of the warnings module for testing without affecting the
          # version being used by the rest of the test suite. One copy uses the
          # C implementation, the other is forced to use the pure Python fallback
          # implementation
          py_warnings = import_fresh_module('warnings', blocked=['_warnings'])
          c_warnings = import_fresh_module('warnings', fresh=['_warnings'])

     在 3.1 版被加入.

 -- 函式: test.support.import_helper.import_module (name,
          deprecated=False, *, required_on=())

     This function imports and returns the named module.  Unlike a
     normal import, this function raises *note unittest.SkipTest: f87.
     if the module cannot be imported.

     Module and package deprecation messages are suppressed during this
     import if 'deprecated' is ‘True’.  If a module is required on a
     platform but optional for others, set 'required_on' to an iterable
     of platform prefixes which will be compared against *note
     sys.platform: a30.

     在 3.1 版被加入.

 -- 函式: test.support.import_helper.modules_setup ()

     回傳 *note sys.modules: 186e. 的複本。

 -- 函式: test.support.import_helper.modules_cleanup (oldmodules)

     Remove modules except for 'oldmodules' and ‘encodings’ in order to
     preserve internal cache.

 -- 函式: test.support.import_helper.unload (name)

     從 ‘sys.modules’ 中刪除 'name'。

 -- 函式: test.support.import_helper.make_legacy_pyc (source)

     Move a PEP 3147(1)/ PEP 488(2) pyc file to its legacy pyc location
     and return the file system path to the legacy pyc file.  The
     'source' value is the file system path to the source file.  It does
     not need to exist, however the PEP 3147/488 pyc file must exist.

 -- 類別: test.support.import_helper.CleanImport (*module_names)

     A context manager to force import to return a new module reference.
     This is useful for testing module-level behaviors, such as the
     emission of a *note DeprecationWarning: 18b. on import.  Example
     usage:

          with CleanImport('foo'):
              importlib.import_module('foo')  # New reference.

 -- 類別: test.support.import_helper.DirsOnSysPath (*paths)

     A context manager to temporarily add directories to *note sys.path:
     37f.

     This makes a copy of *note sys.path: 37f, appends any directories
     given as positional arguments, then reverts *note sys.path: 37f. to
     the copied settings when the context ends.

     Note that 'all' *note sys.path: 37f. modifications in the body of
     the context manager, including replacement of the object, will be
     reverted at the end of the block.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3147/

   (2) https://peps.python.org/pep-0488/


File: python.info,  Node: test support warnings_helper --- 用於 warnings 測試的工具,  Prev: test support import_helper --- 用於 import 測試的工具,  Up: 開發工具

5.26.16 ‘test.support.warnings_helper’ -- 用於 warnings 測試的工具
------------------------------------------------------------------

*note test.support.warnings_helper: d4. 模組提供 warnings 測試的支援。

在 3.10 版被加入.

 -- 函式: test.support.warnings_helper.ignore_warnings (*, category)

     Suppress warnings that are instances of 'category', which must be
     *note Warning: 2191. or a subclass.  Roughly equivalent to *note
     warnings.catch_warnings(): 52a. with *note
     warnings.simplefilter('ignore', category=category): 666.  For
     example:

          @warning_helper.ignore_warnings(category=DeprecationWarning)
          def test_suppress_warning():
              # do something

     在 3.8 版被加入.

 -- 函式: test.support.warnings_helper.check_no_resource_warning
          (testcase)

     Context manager to check that no *note ResourceWarning: 229. was
     raised.  You must remove the object which may emit *note
     ResourceWarning: 229. before the end of the context manager.

 -- 函式: test.support.warnings_helper.check_syntax_warning (testcase,
          statement, errtext='', *, lineno=1, offset=None)

     Test for syntax warning in 'statement' by attempting to compile
     'statement'.  Test also that the *note SyntaxWarning: 40c. is
     emitted only once, and that it will be converted to a *note
     SyntaxError: 173. when turned into error.  'testcase' is the *note
     unittest: ef. instance for the test.  'errtext' is the regular
     expression which should match the string representation of the
     emitted *note SyntaxWarning: 40c. and raised *note SyntaxError:
     173.  If 'lineno' is not ‘None’, compares to the line of the
     warning and exception.  If 'offset' is not ‘None’, compares to the
     offset of the exception.

     在 3.8 版被加入.

 -- 函式: test.support.warnings_helper.check_warnings (*filters,
          quiet=True)

     A convenience wrapper for *note warnings.catch_warnings(): 52a.
     that makes it easier to test that a warning was correctly raised.
     It is approximately equivalent to calling
     ‘warnings.catch_warnings(record=True)’ with *note
     warnings.simplefilter(): 666. set to ‘always’ and with the option
     to automatically validate the results that are recorded.

     ‘check_warnings’ accepts 2-tuples of the form ‘("message regexp",
     WarningCategory)’ as positional arguments.  If one or more
     'filters' are provided, or if the optional keyword argument 'quiet'
     is ‘False’, it checks to make sure the warnings are as expected:
     each specified filter must match at least one of the warnings
     raised by the enclosed code or the test fails, and if any warnings
     are raised that do not match any of the specified filters the test
     fails.  To disable the first of these checks, set 'quiet' to
     ‘True’.

     如果沒有指定引數，預設為：

          check_warnings(("", Warning), quiet=True)

     In this case all warnings are caught and no errors are raised.

     On entry to the context manager, a ‘WarningRecorder’ instance is
     returned.  The underlying warnings list from *note
     catch_warnings(): 52a. is available via the recorder object's *note
     warnings: fa. attribute.  As a convenience, the attributes of the
     object representing the most recent warning can also be accessed
     directly through the recorder object (see example below).  If no
     warning has been raised, then any of the attributes that would
     otherwise be expected on an object representing a warning will
     return ‘None’.

     The recorder object also has a ‘reset()’ method, which clears the
     warnings list.

     The context manager is designed to be used like this:

          with check_warnings(("assertion is always true", SyntaxWarning),
                              ("", UserWarning)):
              exec('assert(False, "Hey!")')
              warnings.warn(UserWarning("Hide me!"))

     In this case if either warning was not raised, or some other
     warning was raised, *note check_warnings(): 3feb. would raise an
     error.

     When a test needs to look more deeply into the warnings, rather
     than just checking whether or not they occurred, code like this can
     be used:

          with check_warnings(quiet=True) as w:
              warnings.warn("foo")
              assert str(w.args[0]) == "foo"
              warnings.warn("bar")
              assert str(w.args[0]) == "bar"
              assert str(w.warnings[0].args[0]) == "foo"
              assert str(w.warnings[1].args[0]) == "bar"
              w.reset()
              assert len(w.warnings) == 0

     Here all warnings will be caught, and the test code tests the
     captured warnings directly.

     在 3.2 版的變更: 新的可選引數 'filters' 和 'quiet'。

 -- 類別: test.support.warnings_helper.WarningsRecorder

     Class used to record warnings for unit tests.  See documentation of
     *note check_warnings(): 3feb. above for more details.


File: python.info,  Node: 除錯與效能分析,  Next: 軟體封裝與發布,  Prev: 開發工具,  Up: Python 標準函式庫 Standard Library

5.27 除錯與效能分析
===================

這些函式庫幫助你進行 Python 程式開發：除錯器允許你在程式碼中單步 (step)
執行、分析堆疊框 (stack frames) 以及設置中斷點 (breakpoints) 等，效能分
析工具執行程式碼並提供關於執行時間的詳細分析，讓你找到程式中的瓶頸
(bottlenecks)。事件稽核 (auditing events) 提供執行時期行為的可見性，否則
的話可能需要更侵入性的除錯或修補。

* Menu:

* 稽核事件表::
* bdb: bdb --- 偵錯器框架. 偵錯器框架
* faulthandler: faulthandler --- 傾印 Python 回溯. 傾印 Python 回溯
* pdb: pdb --- The Python Debugger. The Python Debugger
* Python 的分析器::
* timeit: timeit --- 測量小量程式片段的執行時間. 測量小量程式片段的執行時間
* trace: trace --- 追蹤或追查 Python 陳述式執行. 追蹤或追查 Python 陳述式執行
* tracemalloc: tracemalloc --- 追蹤記憶體配置. 追蹤記憶體配置


File: python.info,  Node: 稽核事件表,  Next: bdb --- 偵錯器框架,  Up: 除錯與效能分析

5.27.1 稽核事件表
-----------------

這張表包含了所有在 CPython 運行環境 (runtime) 與標準函式庫對於 *note
sys.audit(): 1873. 或 *note PySys_Audit(): 321. 的呼叫所觸發的事件。這些
呼叫是在 3.8 或更新的版本中被新增（請見 PEP 578(1)）。

請參考 *note sys.addaudithook(): 3ff1. 及 *note PySys_AddAuditHook():
3ff2. 來了解如何處理這些事件。

'CPython 實作細節：' 這張表是從 CPython 文件產生的，可能不包含其它實作所
觸發的事件。請參考你的運行環境 (runtime) 特定文件來了解實際會觸發的事件
。

Audit event                        Arguments                                                   References
                                                                                               
-------------------------------------------------------------------------------------------------------------------
                                                                                               
_thread.start_new_thread           ‘function’, ‘args’, ‘kwargs’                                *note [1]: 3ff3.
                                                                                               
                                                                                               
array.__new__                      ‘typecode’, ‘initializer’                                   *note [1]: 186.
                                                                                               
                                                                                               
builtins.breakpoint                ‘breakpointhook’                                            *note [1]: 219.
                                                                                               
                                                                                               
builtins.id                        ‘id’                                                        *note [1]: 1390.
                                                                                               
                                                                                               
builtins.input                     ‘prompt’                                                    *note [1]: 126b.
                                                                                               
                                                                                               
builtins.input/result              ‘result’                                                    *note [1]: 126b.
                                                                                               
                                                                                               
code.__new__                       ‘code’, ‘filename’, ‘name’, ‘argcount’,                     *note [1]: 2b6.
                                   ‘posonlyargcount’, ‘kwonlyargcount’, ‘nlocals’,             
                                   ‘stacksize’, ‘flags’
                                   
                                                                                               
compile                            ‘source’, ‘filename’                                        *note [1]: 178.
                                                                                               
                                                                                               
cpython.PyInterpreterState_Clear                                                               *note [1]: 3ff4.
                                                                                               
                                                                                               
cpython.PyInterpreterState_New                                                                 *note [1]: 3ff5.
                                                                                               
                                                                                               
cpython._PySys_ClearAuditHooks                                                                 *note [1]: cbc.
                                                                                               
                                                                                               
cpython.run_command                ‘command’                                                   *note [1]: 584.
                                                                                               
                                                                                               
cpython.run_file                   ‘filename’                                                  *note [1]: 3ff6.
                                                                                               
                                                                                               
cpython.run_interactivehook        ‘hook’                                                      *note [1]: f6a.
                                                                                               
                                                                                               
cpython.run_module                 ‘module-name’                                               *note [1]: 585.
                                                                                               
                                                                                               
cpython.run_startup                ‘filename’                                                  *note [1]: f6b.
                                                                                               
                                                                                               
cpython.run_stdin                                                                              *note [1]: 3ff7.*note [2]: 3ff8.*note [3]: 3ff9.
                                                                                               
                                                                                               
ctypes.addressof                   ‘obj’                                                       *note [1]: 2f08.
                                                                                               
                                                                                               
ctypes.call_function               ‘func_pointer’, ‘arguments’                                 *note [1]: 2f00.
                                                                                               
                                                                                               
ctypes.cdata                       ‘address’                                                   *note [1]: 2f1a.
                                                                                               
                                                                                               
ctypes.cdata/buffer                ‘pointer’, ‘size’, ‘offset’                                 *note [1]: 2f18.*note [2]: 2f19.
                                                                                               
                                                                                               
ctypes.create_string_buffer        ‘init’, ‘size’                                              *note [1]: 2ebc.
                                                                                               
                                                                                               
ctypes.create_unicode_buffer       ‘init’, ‘size’                                              *note [1]: 18d4.
                                                                                               
                                                                                               
ctypes.dlopen                      ‘name’                                                      *note [1]: 2efe.
                                                                                               
                                                                                               
ctypes.dlsym                       ‘library’, ‘name’                                           *note [1]: 2efe.
                                                                                               
                                                                                               
ctypes.dlsym/handle                ‘handle’, ‘name’                                            *note [1]: 2efe.
                                                                                               
                                                                                               
ctypes.get_errno                                                                               *note [1]: 2ef8.
                                                                                               
                                                                                               
ctypes.get_last_error                                                                          *note [1]: 2efa.
                                                                                               
                                                                                               
ctypes.set_errno                   ‘errno’                                                     *note [1]: 2ef9.
                                                                                               
                                                                                               
ctypes.set_exception               ‘code’                                                      *note [1]: 2f00.
                                                                                               
                                                                                               
ctypes.set_last_error              ‘error’                                                     *note [1]: 2efb.
                                                                                               
                                                                                               
ctypes.string_at                   ‘ptr’, ‘size’                                               *note [1]: 2f11.
                                                                                               
                                                                                               
ctypes.wstring_at                  ‘ptr’, ‘size’                                               *note [1]: 2f13.
                                                                                               
                                                                                               
ensurepip.bootstrap                ‘root’                                                      *note [1]: 3ffa.
                                                                                               
                                                                                               
exec                               ‘code_object’                                               *note [1]: 163.*note [2]: 162.
                                                                                               
                                                                                               
fcntl.fcntl                        ‘fd’, ‘cmd’, ‘arg’                                          *note [1]: 327c.
                                                                                               
                                                                                               
fcntl.flock                        ‘fd’, ‘operation’                                           *note [1]: 3ffb.
                                                                                               
                                                                                               
fcntl.ioctl                        ‘fd’, ‘request’, ‘arg’                                      *note [1]: 13e5.
                                                                                               
                                                                                               
fcntl.lockf                        ‘fd’, ‘cmd’, ‘len’, ‘start’, ‘whence’                       *note [1]: 135a.
                                                                                               
                                                                                               
ftplib.connect                     ‘self’, ‘host’, ‘port’                                      *note [1]: 38a9.
                                                                                               
                                                                                               
ftplib.sendcmd                     ‘self’, ‘cmd’                                               *note [1]: 38ae.*note [2]: 38af.
                                                                                               
                                                                                               
function.__new__                   ‘code’                                                      *note [1]: 827.
                                                                                               
                                                                                               
gc.get_objects                     ‘generation’                                                *note [1]: 7a7.
                                                                                               
                                                                                               
gc.get_referents                   ‘objs’                                                      *note [1]: 7a9.
                                                                                               
                                                                                               
gc.get_referrers                   ‘objs’                                                      *note [1]: 7a8.
                                                                                               
                                                                                               
glob.glob                          ‘pathname’, ‘recursive’                                     *note [1]: 280.*note [2]: 7ab.
                                                                                               
                                                                                               
glob.glob/2                        ‘pathname’, ‘recursive’, ‘root_dir’, ‘dir_fd’               *note [1]: 280.*note [2]: 7ab.
                                                                                               
                                                                                               
http.client.connect                ‘self’, ‘host’, ‘port’                                      *note [1]: 388c.
                                                                                               
                                                                                               
http.client.send                   ‘self’, ‘data’                                              *note [1]: 3891.
                                                                                               
                                                                                               
imaplib.open                       ‘self’, ‘host’, ‘port’                                      *note [1]: 8aa.
                                                                                               
                                                                                               
imaplib.send                       ‘self’, ‘data’                                              *note [1]: 3900.
                                                                                               
                                                                                               
import                             ‘module’, ‘filename’, ‘sys.path’, ‘sys.meta_path’,          *note [1]: 586.
                                   ‘sys.path_hooks’                                            
                                   
                                                                                               
marshal.dumps                      ‘value’, ‘version’                                          *note [1]: 279e.
                                                                                               
                                                                                               
marshal.load                                                                                   *note [1]: 1919.
                                                                                               
                                                                                               
marshal.loads                      ‘bytes’                                                     *note [1]: 1919.
                                                                                               
                                                                                               
mmap.__new__                       ‘fileno’, ‘length’, ‘access’, ‘offset’                      *note [1]: 1f0.
                                                                                               
                                                                                               
msvcrt.get_osfhandle               ‘fd’                                                        *note [1]: 3ffc.
                                                                                               
                                                                                               
msvcrt.locking                     ‘fd’, ‘mode’, ‘nbytes’                                      *note [1]: 3ffd.
                                                                                               
                                                                                               
msvcrt.open_osfhandle              ‘handle’, ‘flags’                                           *note [1]: 3ffe.
                                                                                               
                                                                                               
object.__delattr__                 ‘obj’, ‘name’                                               *note [1]: 1e06.
                                                                                               
                                                                                               
object.__getattr__                 ‘obj’, ‘name’                                               *note [1]: b79.
                                                                                               
                                                                                               
object.__setattr__                 ‘obj’, ‘name’, ‘value’                                      *note [1]: 1e05.
                                                                                               
                                                                                               
open                               ‘path’, ‘mode’, ‘flags’                                     *note [1]: 4c0.*note [2]: 4c1.*note [3]: d38.
                                                                                               
                                                                                               
os.add_dll_directory               ‘path’                                                      *note [1]: 98e.
                                                                                               
                                                                                               
os.chdir                           ‘path’                                                      *note [1]: 5b2.*note [2]: d2f.
                                                                                               
                                                                                               
os.chflags                         ‘path’, ‘flags’                                             *note [1]: 1086.*note [2]: 2a67.
                                                                                               
                                                                                               
os.chmod                           ‘path’, ‘mode’, ‘dir_fd’                                    *note [1]: 200.*note [2]: 201.*note [3]: 1ff.
                                                                                               
                                                                                               
os.chown                           ‘path’, ‘uid’, ‘gid’, ‘dir_fd’                              *note [1]: 1087.*note [2]: d30.*note [3]: 2a68.
                                                                                               
                                                                                               
os.exec                            ‘path’, ‘args’, ‘env’                                       *note [1]: 2aa4.
                                                                                               
                                                                                               
os.fork                                                                                        *note [1]: 17b.
                                                                                               
                                                                                               
os.forkpty                                                                                     *note [1]: 17c.
                                                                                               
                                                                                               
os.fwalk                           ‘top’, ‘topdown’, ‘onerror’, ‘follow_symlinks’, ‘dir_fd’    *note [1]: aff.
                                                                                               
                                                                                               
os.getxattr                        ‘path’, ‘attribute’                                         *note [1]: 109c.
                                                                                               
                                                                                               
os.kill                            ‘pid’, ‘sig’                                                *note [1]: 12f4.
                                                                                               
                                                                                               
os.killpg                          ‘pgid’, ‘sig’                                               *note [1]: 18db.
                                                                                               
                                                                                               
os.link                            ‘src’, ‘dst’, ‘src_dir_fd’, ‘dst_dir_fd’                    *note [1]: 1088.
                                                                                               
                                                                                               
os.listdir                         ‘path’                                                      *note [1]: 1092.
                                                                                               
                                                                                               
os.listdrives                                                                                  *note [1]: 445.
                                                                                               
                                                                                               
os.listmounts                      ‘volume’                                                    *note [1]: 447.
                                                                                               
                                                                                               
os.listvolumes                                                                                 *note [1]: 446.
                                                                                               
                                                                                               
os.listxattr                       ‘path’                                                      *note [1]: 109d.
                                                                                               
                                                                                               
os.lockf                           ‘fd’, ‘cmd’, ‘len’                                          *note [1]: 10ab.
                                                                                               
                                                                                               
os.mkdir                           ‘path’, ‘mode’, ‘dir_fd’                                    *note [1]: 203.*note [2]: 202.
                                                                                               
                                                                                               
os.posix_spawn                     ‘path’, ‘argv’, ‘env’                                       *note [1]: 205.*note [2]: 1935.
                                                                                               
                                                                                               
os.putenv                          ‘key’, ‘value’                                              *note [1]: 8c1.
                                                                                               
                                                                                               
os.remove                          ‘path’, ‘dir_fd’                                            *note [1]: 1089.*note [2]: 2a6c.*note [3]: 108e.
                                                                                               
                                                                                               
os.removexattr                     ‘path’, ‘attribute’                                         *note [1]: 109e.
                                                                                               
                                                                                               
os.rename                          ‘src’, ‘dst’, ‘src_dir_fd’, ‘dst_dir_fd’                    *note [1]: 108a.*note [2]: 2a6d.*note [3]: 108b.
                                                                                               
                                                                                               
os.rmdir                           ‘path’, ‘dir_fd’                                            *note [1]: 108c.
                                                                                               
                                                                                               
os.scandir                         ‘path’                                                      *note [1]: a02.
                                                                                               
                                                                                               
os.setxattr                        ‘path’, ‘attribute’, ‘value’, ‘flags’                       *note [1]: 109f.
                                                                                               
                                                                                               
os.spawn                           ‘mode’, ‘path’, ‘args’, ‘env’                               *note [1]: 1630.
                                                                                               
                                                                                               
os.startfile                       ‘path’, ‘operation’                                         *note [1]: 17ce.
                                                                                               
                                                                                               
os.startfile/2                     ‘path’, ‘operation’, ‘arguments’, ‘cwd’, ‘show_cmd’         *note [1]: 17ce.
                                                                                               
                                                                                               
os.symlink                         ‘src’, ‘dst’, ‘dir_fd’                                      *note [1]: 108d.
                                                                                               
                                                                                               
os.system                          ‘command’                                                   *note [1]: 13c8.
                                                                                               
                                                                                               
os.truncate                        ‘fd’, ‘length’                                              *note [1]: d35.*note [2]: de2.
                                                                                               
                                                                                               
os.unsetenv                        ‘key’                                                       *note [1]: 8c0.
                                                                                               
                                                                                               
os.utime                           ‘path’, ‘times’, ‘ns’, ‘dir_fd’                             *note [1]: 108f.
                                                                                               
                                                                                               
os.walk                            ‘top’, ‘topdown’, ‘onerror’, ‘followlinks’                  *note [1]: 451.
                                                                                               
                                                                                               
pathlib.Path.glob                  ‘self’, ‘pattern’                                           *note [1]: 212.
                                                                                               
                                                                                               
pathlib.Path.rglob                 ‘self’, ‘pattern’                                           *note [1]: 213.
                                                                                               
                                                                                               
pdb.Pdb                                                                                        *note [1]: 8c7.
                                                                                               
                                                                                               
pickle.find_class                  ‘module’, ‘name’                                            *note [1]: 277c.
                                                                                               
                                                                                               
poplib.connect                     ‘self’, ‘host’, ‘port’                                      *note [1]: 8c9.*note [2]: 8ca.
                                                                                               
                                                                                               
poplib.putline                     ‘self’, ‘line’                                              *note [1]: 8c9.*note [2]: 8ca.
                                                                                               
                                                                                               
pty.spawn                          ‘argv’                                                      *note [1]: f25.
                                                                                               
                                                                                               
resource.prlimit                   ‘pid’, ‘resource’, ‘limits’                                 *note [1]: f2c.
                                                                                               
                                                                                               
resource.setrlimit                 ‘resource’, ‘limits’                                        *note [1]: 3f9e.
                                                                                               
                                                                                               
setopencodehook                                                                                *note [1]: 1627.
                                                                                               
                                                                                               
shutil.chown                       ‘path’, ‘user’, ‘group’                                     *note [1]: 225.
                                                                                               
                                                                                               
shutil.copyfile                    ‘src’, ‘dst’                                                *note [1]: 9fd.*note [2]: 9fe.*note [3]: 9fc.
                                                                                               
                                                                                               
shutil.copymode                    ‘src’, ‘dst’                                                *note [1]: 9fd.*note [2]: 15a3.
                                                                                               
                                                                                               
shutil.copystat                    ‘src’, ‘dst’                                                *note [1]: 9fe.*note [2]: 10c7.
                                                                                               
                                                                                               
shutil.copytree                    ‘src’, ‘dst’                                                *note [1]: 9cd.
                                                                                               
                                                                                               
shutil.make_archive                ‘base_name’, ‘format’, ‘root_dir’, ‘base_dir’               *note [1]: 45a.
                                                                                               
                                                                                               
shutil.move                        ‘src’, ‘dst’                                                *note [1]: 9ff.
                                                                                               
                                                                                               
shutil.rmtree                      ‘path’, ‘dir_fd’                                            *note [1]: 2d2.
                                                                                               
                                                                                               
shutil.unpack_archive              ‘filename’, ‘extract_dir’, ‘format’                         *note [1]: 412.
                                                                                               
                                                                                               
signal.pthread_kill                ‘thread_id’, ‘signalnum’                                    *note [1]: 10ca.
                                                                                               
                                                                                               
smtplib.connect                    ‘self’, ‘host’, ‘port’                                      *note [1]: 18cf.
                                                                                               
                                                                                               
smtplib.send                       ‘self’, ‘data’                                              *note [1]: 8d1.
                                                                                               
                                                                                               
socket.__new__                     ‘self’, ‘family’, ‘type’, ‘protocol’                        *note [1]: d47.
                                                                                               
                                                                                               
socket.bind                        ‘self’, ‘address’                                           *note [1]: 14a8.
                                                                                               
                                                                                               
socket.connect                     ‘self’, ‘address’                                           *note [1]: d49.*note [2]: 14a7.
                                                                                               
                                                                                               
socket.getaddrinfo                 ‘host’, ‘port’, ‘family’, ‘type’, ‘protocol’                *note [1]: 1654.
                                                                                               
                                                                                               
socket.gethostbyaddr               ‘ip_address’                                                *note [1]: 17cf.
                                                                                               
                                                                                               
socket.gethostbyname               ‘hostname’                                                  *note [1]: 3271.*note [2]: 17d0.
                                                                                               
                                                                                               
socket.gethostname                                                                             *note [1]: 2a11.
                                                                                               
                                                                                               
socket.getnameinfo                 ‘sockaddr’                                                  *note [1]: 15be.
                                                                                               
                                                                                               
socket.getservbyname               ‘servicename’, ‘protocolname’                               *note [1]: 3273.
                                                                                               
                                                                                               
socket.getservbyport               ‘port’, ‘protocolname’                                      *note [1]: 3274.
                                                                                               
                                                                                               
socket.sendmsg                     ‘self’, ‘address’                                           *note [1]: 41d.
                                                                                               
                                                                                               
socket.sendto                      ‘self’, ‘address’                                           *note [1]: d4f.
                                                                                               
                                                                                               
socket.sethostname                 ‘name’                                                      *note [1]: 10d4.
                                                                                               
                                                                                               
sqlite3.connect                    ‘database’                                                  *note [1]: 288.
                                                                                               
                                                                                               
sqlite3.connect/handle             ‘connection_handle’                                         *note [1]: 288.
                                                                                               
                                                                                               
sqlite3.enable_load_extension      ‘connection’, ‘enabled’                                     *note [1]: 7e2.
                                                                                               
                                                                                               
sqlite3.load_extension             ‘connection’, ‘path’                                        *note [1]: 45f.
                                                                                               
                                                                                               
subprocess.Popen                   ‘executable’, ‘args’, ‘cwd’, ‘env’                          *note [1]: 17d.
                                                                                               
                                                                                               
sys._current_exceptions                                                                        *note [1]: 469.
                                                                                               
                                                                                               
sys._current_frames                                                                            *note [1]: 13a0.
                                                                                               
                                                                                               
sys._getframe                      ‘frame’                                                     *note [1]: 684.
                                                                                               
                                                                                               
sys._getframemodulename            ‘depth’                                                     *note [1]: 1672.
                                                                                               
                                                                                               
sys.addaudithook                                                                               *note [1]: 3ff2.*note [2]: 3ff1.
                                                                                               
                                                                                               
sys.excepthook                     ‘hook’, ‘type’, ‘value’, ‘traceback’                        *note [1]: 7af.
                                                                                               
                                                                                               
sys.set_asyncgen_hooks_finalizer                                                               *note [1]: 151a.
                                                                                               
                                                                                               
sys.set_asyncgen_hooks_firstiter                                                               *note [1]: 151a.
                                                                                               
                                                                                               
sys.setprofile                                                                                 *note [1]: 146d.
                                                                                               
                                                                                               
sys.settrace                                                                                   *note [1]: 146e.
                                                                                               
                                                                                               
sys.unraisablehook                 ‘hook’, ‘unraisable’                                        *note [1]: 1dc.
                                                                                               
                                                                                               
syslog.closelog                                                                                *note [1]: 4e5.
                                                                                               
                                                                                               
syslog.openlog                     ‘ident’, ‘logoption’, ‘facility’                            *note [1]: 4e4.
                                                                                               
                                                                                               
syslog.setlogmask                  ‘maskpri’                                                   *note [1]: 3fff.
                                                                                               
                                                                                               
syslog.syslog                      ‘priority’, ‘message’                                       *note [1]: 4e6.
                                                                                               
                                                                                               
tempfile.mkdtemp                   ‘fullpath’                                                  *note [1]: 11cc.*note [2]: 204.
                                                                                               
                                                                                               
tempfile.mkstemp                   ‘fullpath’                                                  *note [1]: 46d.*note [2]: 272f.*note [3]: 2730.
                                                                                               
                                                                                               
time.sleep                         ‘secs’                                                      *note [1]: 4000.
                                                                                               
                                                                                               
urllib.Request                     ‘fullurl’, ‘data’, ‘headers’, ‘method’                      *note [1]: 275.
                                                                                               
                                                                                               
webbrowser.open                    ‘url’                                                       *note [1]: 3771.
                                                                                               
                                                                                               
winreg.ConnectRegistry             ‘computer_name’, ‘key’                                      *note [1]: 4001.
                                                                                               
                                                                                               
winreg.CreateKey                   ‘key’, ‘sub_key’, ‘access’                                  *note [1]: 4002.*note [2]: 12ef.
                                                                                               
                                                                                               
winreg.DeleteKey                   ‘key’, ‘sub_key’, ‘access’                                  *note [1]: 4003.*note [2]: 12f0.
                                                                                               
                                                                                               
winreg.DeleteValue                 ‘key’, ‘value’                                              *note [1]: 4004.
                                                                                               
                                                                                               
winreg.DisableReflectionKey        ‘key’                                                       *note [1]: 12f1.
                                                                                               
                                                                                               
winreg.EnableReflectionKey         ‘key’                                                       *note [1]: 12f2.
                                                                                               
                                                                                               
winreg.EnumKey                     ‘key’, ‘index’                                              *note [1]: 4005.
                                                                                               
                                                                                               
winreg.EnumValue                   ‘key’, ‘index’                                              *note [1]: 4006.
                                                                                               
                                                                                               
winreg.ExpandEnvironmentStrings    ‘str’                                                       *note [1]: 1366.
                                                                                               
                                                                                               
winreg.LoadKey                     ‘key’, ‘sub_key’, ‘file_name’                               *note [1]: 4007.
                                                                                               
                                                                                               
winreg.OpenKey                     ‘key’, ‘sub_key’, ‘access’                                  *note [1]: 4008.
                                                                                               
                                                                                               
winreg.OpenKey/result              ‘key’                                                       *note [1]: 4002.*note [2]: 12ef.*note [3]: 4008.
                                                                                               
                                                                                               
winreg.PyHKEY.Detach               ‘key’                                                       *note [1]: 4009.
                                                                                               
                                                                                               
winreg.QueryInfoKey                ‘key’                                                       *note [1]: 400a.
                                                                                               
                                                                                               
winreg.QueryReflectionKey          ‘key’                                                       *note [1]: 12f3.
                                                                                               
                                                                                               
winreg.QueryValue                  ‘key’, ‘sub_key’, ‘value_name’                              *note [1]: 400b.*note [2]: 400c.
                                                                                               
                                                                                               
winreg.SaveKey                     ‘key’, ‘file_name’                                          *note [1]: 400d.
                                                                                               
                                                                                               
winreg.SetValue                    ‘key’, ‘sub_key’, ‘type’, ‘value’                           *note [1]: 400e.*note [2]: 1691.
                                                                                               

下列事件是內部觸發的，與任何 CPython 的公開 API 並無關係：

稽核事件                       引數
                               
-------------------------------------------------------------------------------
                               
_winapi.CreateFile             ‘file_name’, ‘desired_access’, ‘share_mode’,
                               ‘creation_disposition’,
                               ‘flags_and_attributes’
                               
                               
_winapi.CreateJunction         ‘src_path’, ‘dst_path’
                               
                               
_winapi.CreateNamedPipe        ‘name’, ‘open_mode’, ‘pipe_mode’
                               
                               
_winapi.CreatePipe

_winapi.CreateProcess          ‘application_name’, ‘command_line’,
                               ‘current_directory’
                               
                               
_winapi.OpenProcess            ‘process_id’, ‘desired_access’
                               
                               
_winapi.TerminateProcess       ‘handle’, ‘exit_code’
                               
                               
ctypes.PyObj_FromPtr           ‘obj’
                               

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0578/


File: python.info,  Node: bdb --- 偵錯器框架,  Next: faulthandler --- 傾印 Python 回溯,  Prev: 稽核事件表,  Up: 除錯與效能分析

5.27.2 ‘bdb’ -- 偵錯器框架
--------------------------

'原始碼：'Lib/bdb.py(1)

__________________________________________________________________

The *note bdb: b. module handles basic debugger functions, like setting
breakpoints or managing execution via the debugger.

有定義以下例外：

 -- 例外: bdb.BdbQuit

     由 *note Bdb: 1295. 類別所引發的例外，用來退出偵錯器。

*note bdb: b. 模組也定義了兩個類別：

 -- 類別: bdb.Breakpoint (self, file, line, temporary=False, cond=None,
          funcname=None)

     This class implements temporary breakpoints, ignore counts,
     disabling and (re-)enabling, and conditionals.

     Breakpoints are indexed by number through a list called *note
     bpbynumber: 4013. and by ‘(file, line)’ pairs through *note bplist:
     4014.  The former points to a single instance of class *note
     Breakpoint: 4012.  The latter points to a list of such instances
     since there may be more than one breakpoint per line.

     When creating a breakpoint, its associated *note file name: 4015.
     should be in canonical form.  If a *note funcname: 4016. is
     defined, a breakpoint *note hit: 4017. will be counted when the
     first line of that function is executed.  A *note conditional:
     4018. breakpoint always counts a *note hit: 4017.

     *note Breakpoint: 4012. 實例有以下方法：

      -- 方法: deleteMe ()

          Delete the breakpoint from the list associated to a file/line.
          If it is the last breakpoint in that position, it also deletes
          the entry for the file/line.

      -- 方法: enable ()

          Mark the breakpoint as enabled.

      -- 方法: disable ()

          Mark the breakpoint as disabled.

      -- 方法: bpformat ()

          Return a string with all the information about the breakpoint,
          nicely formatted:

             * Breakpoint number.

             * Temporary status (del or keep).

             * File/line position.

             * Break condition.

             * Number of times to ignore.

             * Number of times hit.

          在 3.2 版被加入.

      -- 方法: bpprint (out=None)

          Print the output of *note bpformat(): 401c. to the file 'out',
          or if it is ‘None’, to standard output.

     *note Breakpoint: 4012. instances have the following attributes:

      -- 屬性: file

          File name of the *note Breakpoint: 4012.

      -- 屬性: line

          Line number of the *note Breakpoint: 4012. within *note file:
          4015.

      -- 屬性: temporary

          ‘True’ if a *note Breakpoint: 4012. at (file, line) is
          temporary.

      -- 屬性: cond

          Condition for evaluating a *note Breakpoint: 4012. at (file,
          line).

      -- 屬性: funcname

          Function name that defines whether a *note Breakpoint: 4012.
          is hit upon entering the function.

      -- 屬性: enabled

          如 *note Breakpoint: 4012. 有被啟用則為 ‘True’。

      -- 屬性: bpbynumber

          Numeric index for a single instance of a *note Breakpoint:
          4012.

      -- 屬性: bplist

          Dictionary of *note Breakpoint: 4012. instances indexed by
          (*note file: 4015, *note line: 401e.) tuples.

      -- 屬性: ignore

          Number of times to ignore a *note Breakpoint: 4012.

      -- 屬性: hits

          Count of the number of times a *note Breakpoint: 4012. has
          been hit.

 -- 類別: bdb.Bdb (skip=None)

     The *note Bdb: 1295. class acts as a generic Python debugger base
     class.

     This class takes care of the details of the trace facility; a
     derived class should implement user interaction.  The standard
     debugger class (*note pdb.Pdb: 8c7.) is an example.

     The 'skip' argument, if given, must be an iterable of glob-style
     module name patterns.  The debugger will not step into frames that
     originate in a module that matches one of these patterns.  Whether
     a frame is considered to originate in a certain module is
     determined by the ‘__name__’ in the frame globals.

     在 3.1 版的變更: 新增 'skip' 引數。

     The following methods of *note Bdb: 1295. normally don't need to be
     overridden.

      -- 方法: canonic (filename)

          Return canonical form of 'filename'.

          For real file names, the canonical form is an
          operating-system-dependent, *note case-normalized: 26b6. *note
          absolute path: 12af.  A 'filename' with angle brackets, such
          as ‘"<stdin>"’ generated in interactive mode, is returned
          unchanged.

      -- 方法: reset ()

          Set the ‘botframe’, ‘stopframe’, ‘returnframe’ and *note
          quitting: 4024. attributes with values ready to start
          debugging.

      -- 方法: trace_dispatch (frame, event, arg)

          This function is installed as the trace function of debugged
          frames.  Its return value is the new trace function (in most
          cases, that is, itself).

          The default implementation decides how to dispatch a frame,
          depending on the type of event (passed as a string) that is
          about to be executed.  'event' can be one of the following:

             * ‘"line"’: A new line of code is going to be executed.

             * ‘"call"’: A function is about to be called, or another
               code block entered.

             * ‘"return"’: A function or other code block is about to
               return.

             * ‘"exception"’: An exception has occurred.

             * ‘"c_call"’: A C function is about to be called.

             * ‘"c_return"’: A C function has returned.

             * ‘"c_exception"’: A C function has raised an exception.

          For the Python events, specialized functions (see below) are
          called.  For the C events, no action is taken.

          The 'arg' parameter depends on the previous event.

          See the documentation for *note sys.settrace(): 146e. for more
          information on the trace function.  For more information on
          code and frame objects, refer to *note 標準型別階層: 1dd6.

      -- 方法: dispatch_line (frame)

          If the debugger should stop on the current line, invoke the
          *note user_line(): 4027. method (which should be overridden in
          subclasses).  Raise a *note BdbQuit: 4011. exception if the
          *note quitting: 4024. flag is set (which can be set from *note
          user_line(): 4027.).  Return a reference to the *note
          trace_dispatch(): 4025. method for further tracing in that
          scope.

      -- 方法: dispatch_call (frame, arg)

          If the debugger should stop on this function call, invoke the
          *note user_call(): 4029. method (which should be overridden in
          subclasses).  Raise a *note BdbQuit: 4011. exception if the
          *note quitting: 4024. flag is set (which can be set from *note
          user_call(): 4029.).  Return a reference to the *note
          trace_dispatch(): 4025. method for further tracing in that
          scope.

      -- 方法: dispatch_return (frame, arg)

          If the debugger should stop on this function return, invoke
          the *note user_return(): 402b. method (which should be
          overridden in subclasses).  Raise a *note BdbQuit: 4011.
          exception if the *note quitting: 4024. flag is set (which can
          be set from *note user_return(): 402b.).  Return a reference
          to the *note trace_dispatch(): 4025. method for further
          tracing in that scope.

      -- 方法: dispatch_exception (frame, arg)

          If the debugger should stop at this exception, invokes the
          *note user_exception(): 402d. method (which should be
          overridden in subclasses).  Raise a *note BdbQuit: 4011.
          exception if the *note quitting: 4024. flag is set (which can
          be set from *note user_exception(): 402d.).  Return a
          reference to the *note trace_dispatch(): 4025. method for
          further tracing in that scope.

     Normally derived classes don't override the following methods, but
     they may if they want to redefine the definition of stopping and
     breakpoints.

      -- 方法: is_skipped_line (module_name)

          Return ‘True’ if 'module_name' matches any skip pattern.

      -- 方法: stop_here (frame)

          Return ‘True’ if 'frame' is below the starting frame in the
          stack.

      -- 方法: break_here (frame)

          Return ‘True’ if there is an effective breakpoint for this
          line.

          Check whether a line or function breakpoint exists and is in
          effect.  Delete temporary breakpoints based on information
          from *note effective(): 4031.

      -- 方法: break_anywhere (frame)

          Return ‘True’ if any breakpoint exists for 'frame"s filename.

     Derived classes should override these methods to gain control over
     debugger operation.

      -- 方法: user_call (frame, argument_list)

          Called from *note dispatch_call(): 4028. if a break might stop
          inside the called function.

          'argument_list' is not used anymore and will always be ‘None’.
          The argument is kept for backwards compatibility.

      -- 方法: user_line (frame)

          Called from *note dispatch_line(): 4026. when either *note
          stop_here(): 402f. or *note break_here(): 4030. returns
          ‘True’.

      -- 方法: user_return (frame, return_value)

          Called from *note dispatch_return(): 402a. when *note
          stop_here(): 402f. returns ‘True’.

      -- 方法: user_exception (frame, exc_info)

          Called from *note dispatch_exception(): 402c. when *note
          stop_here(): 402f. returns ‘True’.

      -- 方法: do_clear (arg)

          Handle how a breakpoint must be removed when it is a temporary
          one.

          This method must be implemented by derived classes.

     Derived classes and clients can call the following methods to
     affect the stepping state.

      -- 方法: set_step ()

          Stop after one line of code.

      -- 方法: set_next (frame)

          Stop on the next line in or below the given frame.

      -- 方法: set_return (frame)

          Stop when returning from the given frame.

      -- 方法: set_until (frame, lineno=None)

          Stop when the line with the 'lineno' greater than the current
          one is reached or when returning from current frame.

      -- 方法: set_trace ([frame])

          Start debugging from 'frame'.  If 'frame' is not specified,
          debugging starts from caller's frame.

          在 3.13 版的變更: *note set_trace(): 4039. will enter the
          debugger immediately, rather than on the next line of code to
          be executed.

      -- 方法: set_continue ()

          Stop only at breakpoints or when finished.  If there are no
          breakpoints, set the system trace function to ‘None’.

      -- 方法: set_quit ()

          Set the ‘quitting’ attribute to ‘True’.  This raises *note
          BdbQuit: 4011. in the next call to one of the ‘dispatch_*()’
          methods.

     Derived classes and clients can call the following methods to
     manipulate breakpoints.  These methods return a string containing
     an error message if something went wrong, or ‘None’ if all is well.

      -- 方法: set_break (filename, lineno, temporary=False, cond=None,
               funcname=None)

          Set a new breakpoint.  If the 'lineno' line doesn't exist for
          the 'filename' passed as argument, return an error message.
          The 'filename' should be in canonical form, as described in
          the *note canonic(): 4022. method.

      -- 方法: clear_break (filename, lineno)

          Delete the breakpoints in 'filename' and 'lineno'.  If none
          were set, return an error message.

      -- 方法: clear_bpbynumber (arg)

          Delete the breakpoint which has the index 'arg' in the *note
          Breakpoint.bpbynumber: 4013.  If 'arg' is not numeric or out
          of range, return an error message.

      -- 方法: clear_all_file_breaks (filename)

          Delete all breakpoints in 'filename'.  If none were set,
          return an error message.

      -- 方法: clear_all_breaks ()

          Delete all existing breakpoints.  If none were set, return an
          error message.

      -- 方法: get_bpbynumber (arg)

          Return a breakpoint specified by the given number.  If 'arg'
          is a string, it will be converted to a number.  If 'arg' is a
          non-numeric string, if the given breakpoint never existed or
          has been deleted, a *note ValueError: 1e7. is raised.

          在 3.2 版被加入.

      -- 方法: get_break (filename, lineno)

          Return ‘True’ if there is a breakpoint for 'lineno' in
          'filename'.

      -- 方法: get_breaks (filename, lineno)

          Return all breakpoints for 'lineno' in 'filename', or an empty
          list if none are set.

      -- 方法: get_file_breaks (filename)

          Return all breakpoints in 'filename', or an empty list if none
          are set.

      -- 方法: get_all_breaks ()

          Return all breakpoints that are set.

     Derived classes and clients can call the following methods to get a
     data structure representing a stack trace.

      -- 方法: get_stack (f, t)

          Return a list of (frame, lineno) tuples in a stack trace, and
          a size.

          The most recently called frame is last in the list.  The size
          is the number of frames below the frame where the debugger was
          invoked.

      -- 方法: format_stack_entry (frame_lineno, lprefix=': ')

          Return a string with information about a stack entry, which is
          a ‘(frame, lineno)’ tuple.  The return string contains:

             * The canonical filename which contains the frame.

             * 函式名稱或 ‘"<lambda>"’。

             * 輸入引數。

             * 回傳值。

             * The line of code (if it exists).

     The following two methods can be called by clients to use a
     debugger to debug a *note statement: 265e, given as a string.

      -- 方法: run (cmd, globals=None, locals=None)

          Debug a statement executed via the *note exec(): 162.
          function.  'globals' defaults to ‘__main__.__dict__’, 'locals'
          defaults to 'globals'.

      -- 方法: runeval (expr, globals=None, locals=None)

          Debug an expression executed via the *note eval(): 163.
          function.  'globals' and 'locals' have the same meaning as in
          *note run(): 4047.

      -- 方法: runctx (cmd, globals, locals)

          For backwards compatibility.  Calls the *note run(): 4047.
          method.

      -- 方法: runcall (func, /, *args, **kwds)

          Debug a single function call, and return its result.

Finally, the module defines the following functions:

 -- 函式: bdb.checkfuncname (b, frame)

     Return ‘True’ if we should break here, depending on the way the
     *note Breakpoint: 4012. 'b' was set.

     If it was set via line number, it checks if *note b.line: 401e. is
     the same as the one in 'frame'.  If the breakpoint was set via
     *note function name: 4016, we have to check we are in the right
     'frame' (the right function) and if we are on its first executable
     line.

 -- 函式: bdb.effective (file, line, frame)

     Return ‘(active breakpoint, delete temporary flag)’ or ‘(None,
     None)’ as the breakpoint to act upon.

     The 'active breakpoint' is the first entry in *note bplist: 4014.
     for the (*note file: 4015, *note line: 401e.) (which must exist)
     that is *note enabled: 4020, for which *note checkfuncname(): 404a.
     is true, and that has neither a false *note condition: 4018. nor
     positive *note ignore: 4021. count.  The 'flag', meaning that a
     temporary breakpoint should be deleted, is ‘False’ only when the
     *note cond: 4018. cannot be evaluated (in which case, *note ignore:
     4021. count is ignored).

     If no such entry exists, then ‘(None, None)’ is returned.

 -- 函式: bdb.set_trace ()

     Start debugging with a *note Bdb: 1295. instance from caller's
     frame.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/bdb.py


File: python.info,  Node: faulthandler --- 傾印 Python 回溯,  Next: pdb --- The Python Debugger,  Prev: bdb --- 偵錯器框架,  Up: 除錯與效能分析

5.27.3 ‘faulthandler’ -- 傾印 Python 回溯
-----------------------------------------

在 3.3 版被加入.

__________________________________________________________________

This module contains functions to dump Python tracebacks explicitly, on
a fault, after a timeout, or on a user signal.  Call *note
faulthandler.enable(): c45. to install fault handlers for the *note
SIGSEGV: 1c4b, *note SIGFPE: 1c4c, *note SIGABRT: 1c4d, *note SIGBUS:
1c4e, and *note SIGILL: 1c4f. signals.  You can also enable them at
startup by setting the *note PYTHONFAULTHANDLER: 1021. environment
variable or by using the *note -X: 15a. ‘faulthandler’ command line
option.

The fault handler is compatible with system fault handlers like Apport
or the Windows fault handler.  The module uses an alternative stack for
signal handlers if the ‘sigaltstack()’ function is available.  This
allows it to dump the traceback even on a stack overflow.

The fault handler is called on catastrophic cases and therefore can only
use signal-safe functions (e.g.  it cannot allocate memory on the heap).
Because of this limitation traceback dumping is minimal compared to
normal Python tracebacks:

   * Only ASCII is supported.  The ‘backslashreplace’ error handler is
     used on encoding.

   * Each string is limited to 500 characters.

   * Only the filename, the function name and the line number are
     displayed.  (no source code)

   * It is limited to 100 frames and 100 threads.

   * The order is reversed: the most recent call is shown first.

By default, the Python traceback is written to *note sys.stderr: 8dd.
To see tracebacks, applications must be run in the terminal.  A log file
can alternatively be passed to *note faulthandler.enable(): c45.

The module is implemented in C, so tracebacks can be dumped on a crash
or when Python is deadlocked.

The *note Python Development Mode: 1dd. calls *note
faulthandler.enable(): c45. at Python startup.

也參考
......

*note pdb: 94. 模組

     Interactive source code debugger for Python programs.

*note traceback: e7. 模組

     Standard interface to extract, format and print stack traces of
     Python programs.

* Menu:

* Dumping the traceback::
* Fault handler state::
* Dumping the tracebacks after a timeout::
* Dumping the traceback on a user signal::
* Issue with file descriptors::
* 範例: 範例<41>.


File: python.info,  Node: Dumping the traceback,  Next: Fault handler state,  Up: faulthandler --- 傾印 Python 回溯

5.27.3.1 Dumping the traceback
..............................

 -- 函式: faulthandler.dump_traceback (file=sys.stderr,
          all_threads=True)

     Dump the tracebacks of all threads into 'file'.  If 'all_threads'
     is ‘False’, dump only the current thread.

     也參考
     ......

     *note traceback.print_tb(): e29, which can be used to print a
     traceback object.

     在 3.5 版的變更: Added support for passing file descriptor to this
     function.


File: python.info,  Node: Fault handler state,  Next: Dumping the tracebacks after a timeout,  Prev: Dumping the traceback,  Up: faulthandler --- 傾印 Python 回溯

5.27.3.2 Fault handler state
............................

 -- 函式: faulthandler.enable (file=sys.stderr, all_threads=True)

     Enable the fault handler: install handlers for the *note SIGSEGV:
     1c4b, *note SIGFPE: 1c4c, *note SIGABRT: 1c4d, *note SIGBUS: 1c4e.
     and *note SIGILL: 1c4f. signals to dump the Python traceback.  If
     'all_threads' is ‘True’, produce tracebacks for every running
     thread.  Otherwise, dump only the current thread.

     The 'file' must be kept open until the fault handler is disabled:
     see *note issue with file descriptors: 404f.

     在 3.5 版的變更: Added support for passing file descriptor to this
     function.

     在 3.6 版的變更: On Windows, a handler for Windows exception is
     also installed.

     在 3.10 版的變更: The dump now mentions if a garbage collector
     collection is running if 'all_threads' is true.

 -- 函式: faulthandler.disable ()

     Disable the fault handler: uninstall the signal handlers installed
     by *note enable(): c45.

 -- 函式: faulthandler.is_enabled ()

     Check if the fault handler is enabled.


File: python.info,  Node: Dumping the tracebacks after a timeout,  Next: Dumping the traceback on a user signal,  Prev: Fault handler state,  Up: faulthandler --- 傾印 Python 回溯

5.27.3.3 Dumping the tracebacks after a timeout
...............................................

 -- 函式: faulthandler.dump_traceback_later (timeout, repeat=False,
          file=sys.stderr, exit=False)

     Dump the tracebacks of all threads, after a timeout of 'timeout'
     seconds, or every 'timeout' seconds if 'repeat' is ‘True’.  If
     'exit' is ‘True’, call ‘_exit()’ with status=1 after dumping the
     tracebacks.  (Note ‘_exit()’ exits the process immediately, which
     means it doesn't do any cleanup like flushing file buffers.)  If
     the function is called twice, the new call replaces previous
     parameters and resets the timeout.  The timer has a sub-second
     resolution.

     The 'file' must be kept open until the traceback is dumped or *note
     cancel_dump_traceback_later(): 4053. is called: see *note issue
     with file descriptors: 404f.

     This function is implemented using a watchdog thread.

     在 3.5 版的變更: Added support for passing file descriptor to this
     function.

     在 3.7 版的變更: This function is now always available.

 -- 函式: faulthandler.cancel_dump_traceback_later ()

     Cancel the last call to *note dump_traceback_later(): da5.


File: python.info,  Node: Dumping the traceback on a user signal,  Next: Issue with file descriptors,  Prev: Dumping the tracebacks after a timeout,  Up: faulthandler --- 傾印 Python 回溯

5.27.3.4 Dumping the traceback on a user signal
...............................................

 -- 函式: faulthandler.register (signum, file=sys.stderr,
          all_threads=True, chain=False)

     Register a user signal: install a handler for the 'signum' signal
     to dump the traceback of all threads, or of the current thread if
     'all_threads' is ‘False’, into 'file'.  Call the previous handler
     if chain is ‘True’.

     The 'file' must be kept open until the signal is unregistered by
     *note unregister(): 4055.: see *note issue with file descriptors:
     404f.

     Not available on Windows.

     在 3.5 版的變更: Added support for passing file descriptor to this
     function.

 -- 函式: faulthandler.unregister (signum)

     Unregister a user signal: uninstall the handler of the 'signum'
     signal installed by *note register(): da3.  Return ‘True’ if the
     signal was registered, ‘False’ otherwise.

     Not available on Windows.


File: python.info,  Node: Issue with file descriptors,  Next: 範例<41>,  Prev: Dumping the traceback on a user signal,  Up: faulthandler --- 傾印 Python 回溯

5.27.3.5 Issue with file descriptors
....................................

*note enable(): c45, *note dump_traceback_later(): da5. and *note
register(): da3. keep the file descriptor of their 'file' argument.  If
the file is closed and its file descriptor is reused by a new file, or
if *note os.dup2(): b07. is used to replace the file descriptor, the
traceback will be written into a different file.  Call these functions
again each time that the file is replaced.


File: python.info,  Node: 範例<41>,  Prev: Issue with file descriptors,  Up: faulthandler --- 傾印 Python 回溯

5.27.3.6 範例
.............

Example of a segmentation fault on Linux with and without enabling the
fault handler:

     $ python -c "import ctypes; ctypes.string_at(0)"
     Segmentation fault

     $ python -q -X faulthandler
     >>> import ctypes
     >>> ctypes.string_at(0)
     Fatal Python error: Segmentation fault

     Current thread 0x00007fb899f39700 (most recent call first):
       File "/home/python/cpython/Lib/ctypes/__init__.py", line 486 in string_at
       File "<stdin>", line 1 in <module>
     Segmentation fault


File: python.info,  Node: pdb --- The Python Debugger,  Next: Python 的分析器,  Prev: faulthandler --- 傾印 Python 回溯,  Up: 除錯與效能分析

5.27.4 ‘pdb’ -- The Python Debugger
-----------------------------------

'原始碼：'Lib/pdb.py(1)

__________________________________________________________________

The module *note pdb: 94. defines an interactive source code debugger
for Python programs.  It supports setting (conditional) breakpoints and
single stepping at the source line level, inspection of stack frames,
source code listing, and evaluation of arbitrary Python code in the
context of any stack frame.  It also supports post-mortem debugging and
can be called under program control.

The debugger is extensible - it is actually defined as the class *note
Pdb: 8c7.  This is currently undocumented but easily understood by
reading the source.  The extension interface uses the modules *note bdb:
b. and *note cmd: 12.

也參考
......

*note faulthandler: 4e. 模組

     Used to dump Python tracebacks explicitly, on a fault, after a
     timeout, or on a user signal.

*note traceback: e7. 模組

     Standard interface to extract, format and print stack traces of
     Python programs.

The typical usage to break into the debugger is to insert:

     import pdb; pdb.set_trace()

或：

     breakpoint()

at the location you want to break into the debugger, and then run the
program.  You can then step through the code following this statement,
and continue running without the debugger using the *note continue:
405b. command.

在 3.7 版的變更: The built-in *note breakpoint(): 219, when called with
defaults, can be used instead of ‘import pdb; pdb.set_trace()’.

     def double(x):
        breakpoint()
        return x * 2
     val = 3
     print(f"{val} * 2 is {double(val)}")

The debugger's prompt is ‘(Pdb)’, which is the indicator that you are in
debug mode:

     > ...(2)double()
     -> breakpoint()
     (Pdb) p x
     3
     (Pdb) continue
     3 * 2 is 6

在 3.3 版的變更: Tab-completion via the *note readline: a8. module is
available for commands and command arguments, e.g.  the current global
and local names are offered as arguments of the ‘p’ command.

You can also invoke *note pdb: 94. from the command line to debug other
scripts.  For example:

     python -m pdb myscript.py

When invoked as a module, pdb will automatically enter post-mortem
debugging if the program being debugged exits abnormally.  After
post-mortem debugging (or after normal exit of the program), pdb will
restart the program.  Automatic restarting preserves pdb's state (such
as breakpoints) and in most cases is more useful than quitting the
debugger upon program's exit.

在 3.2 版的變更: Added the ‘-c’ option to execute commands as if given
in a ‘.pdbrc’ file; see *note Debugger Commands: 405c.

在 3.7 版的變更: Added the ‘-m’ option to execute modules similar to the
way ‘python -m’ does.  As with a script, the debugger will pause
execution just before the first line of the module.

Typical usage to execute a statement under control of the debugger is:

     >>> import pdb
     >>> def f(x):
     ...     print(1 / x)
     >>> pdb.run("f(2)")
     > <string>(1)<module>()
     (Pdb) continue
     0.5
     >>>

The typical usage to inspect a crashed program is:

     >>> import pdb
     >>> def f(x):
     ...     print(1 / x)
     ...
     >>> f(0)
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
       File "<stdin>", line 2, in f
     ZeroDivisionError: division by zero
     >>> pdb.pm()
     > <stdin>(2)f()
     (Pdb) p x
     0
     (Pdb)

在 3.13 版的變更: The implementation of PEP 667(2) means that name
assignments made via ‘pdb’ will immediately affect the active scope,
even when running inside an *note optimized scope: 161.

The module defines the following functions; each enters the debugger in
a slightly different way:

 -- 函式: pdb.run (statement, globals=None, locals=None)

     Execute the 'statement' (given as a string or a code object) under
     debugger control.  The debugger prompt appears before any code is
     executed; you can set breakpoints and type *note continue: 405b, or
     you can step through the statement using *note step: 405d. or *note
     next: 405e. (all these commands are explained below).  The optional
     'globals' and 'locals' arguments specify the environment in which
     the code is executed; by default the dictionary of the module *note
     __main__: 1. is used.  (See the explanation of the built-in *note
     exec(): 162. or *note eval(): 163. functions.)

 -- 函式: pdb.runeval (expression, globals=None, locals=None)

     Evaluate the 'expression' (given as a string or a code object)
     under debugger control.  When *note runeval(): 405f. returns, it
     returns the value of the 'expression'.  Otherwise this function is
     similar to *note run(): 3e64.

 -- 函式: pdb.runcall (function, *args, **kwds)

     Call the 'function' (a function or method object, not a string)
     with the given arguments.  When *note runcall(): 4060. returns, it
     returns whatever the function call returned.  The debugger prompt
     appears as soon as the function is entered.

 -- 函式: pdb.set_trace (*, header=None)

     Enter the debugger at the calling stack frame.  This is useful to
     hard-code a breakpoint at a given point in a program, even if the
     code is not otherwise being debugged (e.g.  when an assertion
     fails).  If given, 'header' is printed to the console just before
     debugging begins.

     在 3.7 版的變更: The keyword-only argument 'header'.

     在 3.13 版的變更: *note set_trace(): 21a. will enter the debugger
     immediately, rather than on the next line of code to be executed.

 -- 函式: pdb.post_mortem (traceback=None)

     Enter post-mortem debugging of the given 'traceback' object.  If no
     'traceback' is given, it uses the one of the exception that is
     currently being handled (an exception must be being handled if the
     default is to be used).

 -- 函式: pdb.pm ()

     Enter post-mortem debugging of the exception found in *note
     sys.last_exc: 465.

The ‘run*’ functions and *note set_trace(): 21a. are aliases for
instantiating the *note Pdb: 8c7. class and calling the method of the
same name.  If you want to access further features, you have to do this
yourself:

 -- 類別: pdb.Pdb (completekey='tab', stdin=None, stdout=None,
          skip=None, nosigint=False, readrc=True)

     *note Pdb: 8c7. is the debugger class.

     The 'completekey', 'stdin' and 'stdout' arguments are passed to the
     underlying *note cmd.Cmd: 15c0. class; see the description there.

     The 'skip' argument, if given, must be an iterable of glob-style
     module name patterns.  The debugger will not step into frames that
     originate in a module that matches one of these patterns.  (3)

     By default, Pdb sets a handler for the SIGINT signal (which is sent
     when the user presses ‘Ctrl-C’ on the console) when you give a
     *note continue: 405b. command.  This allows you to break into the
     debugger again by pressing ‘Ctrl-C’.  If you want Pdb not to touch
     the SIGINT handler, set 'nosigint' to true.

     The 'readrc' argument defaults to true and controls whether Pdb
     will load .pdbrc files from the filesystem.

     Example call to enable tracing with 'skip':

          import pdb; pdb.Pdb(skip=['django.*']).set_trace()

     引發一個不附帶引數的*note 稽核事件: 17bd. ‘pdb.Pdb’。

     在 3.1 版的變更: Added the 'skip' parameter.

     在 3.2 版的變更: Added the 'nosigint' parameter.  Previously, a
     SIGINT handler was never set by Pdb.

     在 3.6 版的變更: 'readrc' 引數。

      -- 方法: run (statement, globals=None, locals=None)
      -- 方法: runeval (expression, globals=None, locals=None)
      -- 方法: runcall (function, *args, **kwds)
      -- 方法: set_trace ()

          See the documentation for the functions explained above.

* Menu:

* Debugger Commands::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/pdb.py

   (2) https://peps.python.org/pep-0667/

   (3) Whether a frame is considered to originate in a certain module is
determined by the ‘__name__’ in the frame globals.


File: python.info,  Node: Debugger Commands,  Up: pdb --- The Python Debugger

5.27.4.1 Debugger Commands
..........................

The commands recognized by the debugger are listed below.  Most commands
can be abbreviated to one or two letters as indicated; e.g.  ‘h(elp)’
means that either ‘h’ or ‘help’ can be used to enter the help command
(but not ‘he’ or ‘hel’, nor ‘H’ or ‘Help’ or ‘HELP’).  Arguments to
commands must be separated by whitespace (spaces or tabs).  Optional
arguments are enclosed in square brackets (‘[]’) in the command syntax;
the square brackets must not be typed.  Alternatives in the command
syntax are separated by a vertical bar (‘|’).

Entering a blank line repeats the last command entered.  Exception: if
the last command was a *note list: 4066. command, the next 11 lines are
listed.

Commands that the debugger doesn't recognize are assumed to be Python
statements and are executed in the context of the program being
debugged.  Python statements can also be prefixed with an exclamation
point (‘!’).  This is a powerful way to inspect the program being
debugged; it is even possible to change a variable or call a function.
When an exception occurs in such a statement, the exception name is
printed but the debugger's state is not changed.

在 3.13 版的變更: Expressions/Statements whose prefix is a pdb command
are now correctly identified and executed.

The debugger supports *note aliases: 4067.  Aliases can have parameters
which allows one a certain level of adaptability to the context under
examination.

Multiple commands may be entered on a single line, separated by ‘;;’.
(A single ‘;’ is not used as it is the separator for multiple commands
in a line that is passed to the Python parser.)  No intelligence is
applied to separating the commands; the input is split at the first ‘;;’
pair, even if it is in the middle of a quoted string.  A workaround for
strings with double semicolons is to use implicit string concatenation
‘';'';'’ or ‘";"";"’.

To set a temporary global variable, use a 'convenience variable'.  A
'convenience variable' is a variable whose name starts with ‘$’.  For
example, ‘$foo = 1’ sets a global variable ‘$foo’ which you can use in
the debugger session.  The 'convenience variables' are cleared when the
program resumes execution so it's less likely to interfere with your
program compared to using normal variables like ‘foo = 1’.

There are three preset 'convenience variables':

   * ‘$_frame’: the current frame you are debugging

   * ‘$_retval’: the return value if the frame is returning

   * ‘$_exception’: the exception if the frame is raising an exception

在 3.12 版被加入: Added the 'convenience variable' feature.

If a file ‘.pdbrc’ exists in the user's home directory or in the current
directory, it is read with ‘'utf-8'’ encoding and executed as if it had
been typed at the debugger prompt, with the exception that empty lines
and lines starting with ‘#’ are ignored.  This is particularly useful
for aliases.  If both files exist, the one in the home directory is read
first and aliases defined there can be overridden by the local file.

在 3.2 版的變更: ‘.pdbrc’ can now contain commands that continue
debugging, such as *note continue: 405b. or *note next: 405e.
Previously, these commands had no effect.

在 3.11 版的變更: ‘.pdbrc’ is now read with ‘'utf-8'’ encoding.
Previously, it was read with the system locale encoding.

 -- Pdbcommand: h(elp) [command]

     Without argument, print the list of available commands.  With a
     'command' as argument, print help about that command.  ‘help pdb’
     displays the full documentation (the docstring of the *note pdb:
     94. module).  Since the 'command' argument must be an identifier,
     ‘help exec’ must be entered to get help on the ‘!’ command.

 -- Pdbcommand: w(here)

     Print a stack trace, with the most recent frame at the bottom.  An
     arrow (‘>’) indicates the current frame, which determines the
     context of most commands.

 -- Pdbcommand: d(own) [count]

     Move the current frame 'count' (default one) levels down in the
     stack trace (to a newer frame).

 -- Pdbcommand: u(p) [count]

     Move the current frame 'count' (default one) levels up in the stack
     trace (to an older frame).

 -- Pdbcommand: b(reak) [([filename:]lineno | function) [, condition]]

     With a 'lineno' argument, set a break at line 'lineno' in the
     current file.  The line number may be prefixed with a 'filename'
     and a colon, to specify a breakpoint in another file (possibly one
     that hasn't been loaded yet).  The file is searched on *note
     sys.path: 37f.  Accepatable forms of 'filename' are
     ‘/abspath/to/file.py’, ‘relpath/file.py’, ‘module’ and
     ‘package.module’.

     With a 'function' argument, set a break at the first executable
     statement within that function.  'function' can be any expression
     that evaluates to a function in the current namespace.

     If a second argument is present, it is an expression which must
     evaluate to true before the breakpoint is honored.

     Without argument, list all breaks, including for each breakpoint,
     the number of times that breakpoint has been hit, the current
     ignore count, and the associated condition if any.

     Each breakpoint is assigned a number to which all the other
     breakpoint commands refer.

 -- Pdbcommand: tbreak [([filename:]lineno | function) [, condition]]

     Temporary breakpoint, which is removed automatically when it is
     first hit.  The arguments are the same as for *note break: 406c.

 -- Pdbcommand: cl(ear) [filename:lineno | bpnumber ...]

     With a 'filename:lineno' argument, clear all the breakpoints at
     this line.  With a space separated list of breakpoint numbers,
     clear those breakpoints.  Without argument, clear all breaks (but
     first ask confirmation).

 -- Pdbcommand: disable bpnumber [bpnumber ...]

     Disable the breakpoints given as a space separated list of
     breakpoint numbers.  Disabling a breakpoint means it cannot cause
     the program to stop execution, but unlike clearing a breakpoint, it
     remains in the list of breakpoints and can be (re-)enabled.

 -- Pdbcommand: enable bpnumber [bpnumber ...]

     Enable the breakpoints specified.

 -- Pdbcommand: ignore bpnumber [count]

     Set the ignore count for the given breakpoint number.  If 'count'
     is omitted, the ignore count is set to 0.  A breakpoint becomes
     active when the ignore count is zero.  When non-zero, the 'count'
     is decremented each time the breakpoint is reached and the
     breakpoint is not disabled and any associated condition evaluates
     to true.

 -- Pdbcommand: condition bpnumber [condition]

     Set a new 'condition' for the breakpoint, an expression which must
     evaluate to true before the breakpoint is honored.  If 'condition'
     is absent, any existing condition is removed; i.e., the breakpoint
     is made unconditional.

 -- Pdbcommand: commands [bpnumber]

     Specify a list of commands for breakpoint number 'bpnumber'.  The
     commands themselves appear on the following lines.  Type a line
     containing just ‘end’ to terminate the commands.  An example:

          (Pdb) commands 1
          (com) p some_variable
          (com) end
          (Pdb)

     To remove all commands from a breakpoint, type ‘commands’ and
     follow it immediately with ‘end’; that is, give no commands.

     With no 'bpnumber' argument, ‘commands’ refers to the last
     breakpoint set.

     You can use breakpoint commands to start your program up again.
     Simply use the *note continue: 405b. command, or *note step: 405d,
     or any other command that resumes execution.

     Specifying any command resuming execution (currently *note
     continue: 405b, *note step: 405d, *note next: 405e, *note return:
     4074, *note jump: 4075, *note quit: 4076. and their abbreviations)
     terminates the command list (as if that command was immediately
     followed by end).  This is because any time you resume execution
     (even with a simple next or step), you may encounter another
     breakpoint—which could have its own command list, leading to
     ambiguities about which list to execute.

     If you use the ‘silent’ command in the command list, the usual
     message about stopping at a breakpoint is not printed.  This may be
     desirable for breakpoints that are to print a specific message and
     then continue.  If none of the other commands print anything, you
     see no sign that the breakpoint was reached.

 -- Pdbcommand: s(tep)

     Execute the current line, stop at the first possible occasion
     (either in a function that is called or on the next line in the
     current function).

 -- Pdbcommand: n(ext)

     Continue execution until the next line in the current function is
     reached or it returns.  (The difference between *note next: 405e.
     and *note step: 405d. is that *note step: 405d. stops inside a
     called function, while *note next: 405e. executes called functions
     at (nearly) full speed, only stopping at the next line in the
     current function.)

 -- Pdbcommand: unt(il) [lineno]

     Without argument, continue execution until the line with a number
     greater than the current one is reached.

     With 'lineno', continue execution until a line with a number
     greater or equal to 'lineno' is reached.  In both cases, also stop
     when the current frame returns.

     在 3.2 版的變更: Allow giving an explicit line number.

 -- Pdbcommand: r(eturn)

     Continue execution until the current function returns.

 -- Pdbcommand: c(ont(inue))

     Continue execution, only stop when a breakpoint is encountered.

 -- Pdbcommand: j(ump) lineno

     Set the next line that will be executed.  Only available in the
     bottom-most frame.  This lets you jump back and execute code again,
     or jump forward to skip code that you don't want to run.

     It should be noted that not all jumps are allowed - for instance it
     is not possible to jump into the middle of a *note for: 2c3. loop
     or out of a *note finally: 96e. clause.

 -- Pdbcommand: l(ist) [first[, last]]

     List source code for the current file.  Without arguments, list 11
     lines around the current line or continue the previous listing.
     With ‘.’ as argument, list 11 lines around the current line.  With
     one argument, list 11 lines around at that line.  With two
     arguments, list the given range; if the second argument is less
     than the first, it is interpreted as a count.

     The current line in the current frame is indicated by ‘->’.  If an
     exception is being debugged, the line where the exception was
     originally raised or propagated is indicated by ‘>>’, if it differs
     from the current line.

     在 3.2 版的變更: Added the ‘>>’ marker.

 -- Pdbcommand: ll | longlist

     List all source code for the current function or frame.
     Interesting lines are marked as for *note list: 4066.

     在 3.2 版被加入.

 -- Pdbcommand: a(rgs)

     Print the arguments of the current function and their current
     values.

 -- Pdbcommand: p expression

     Evaluate 'expression' in the current context and print its value.

          備註: ‘print()’ can also be used, but is not a debugger
          command -- this executes the Python *note print(): f18.
          function.

 -- Pdbcommand: pp expression

     Like the *note p: f19. command, except the value of 'expression' is
     pretty-printed using the *note pprint: 9c. module.

 -- Pdbcommand: whatis expression

     Print the type of 'expression'.

 -- Pdbcommand: source expression

     Try to get source code of 'expression' and display it.

     在 3.2 版被加入.

 -- Pdbcommand: display [expression]

     Display the value of 'expression' if it changed, each time
     execution stops in the current frame.

     Without 'expression', list all display expressions for the current
     frame.

          備註: Display evaluates 'expression' and compares to the
          result of the previous evaluation of 'expression', so when the
          result is mutable, display may not be able to pick up the
          changes.

     範例：

          lst = []
          breakpoint()
          pass
          lst.append(1)
          print(lst)

     Display won't realize ‘lst’ has been changed because the result of
     evaluation is modified in place by ‘lst.append(1)’ before being
     compared:

          > example.py(3)<module>()
          -> pass
          (Pdb) display lst
          display lst: []
          (Pdb) n
          > example.py(4)<module>()
          -> lst.append(1)
          (Pdb) n
          > example.py(5)<module>()
          -> print(lst)
          (Pdb)

     You can do some tricks with copy mechanism to make it work:

          > example.py(3)<module>()
          -> pass
          (Pdb) display lst[:]
          display lst[:]: []
          (Pdb) n
          > example.py(4)<module>()
          -> lst.append(1)
          (Pdb) n
          > example.py(5)<module>()
          -> print(lst)
          display lst[:]: [1]  [old: []]
          (Pdb)

     在 3.2 版被加入.

 -- Pdbcommand: undisplay [expression]

     Do not display 'expression' anymore in the current frame.  Without
     'expression', clear all display expressions for the current frame.

     在 3.2 版被加入.

 -- Pdbcommand: interact

     Start an interactive interpreter (using the *note code: 13. module)
     in a new global namespace initialised from the local and global
     namespaces for the current scope.  Use ‘exit()’ or ‘quit()’ to exit
     the interpreter and return to the debugger.

          備註: As ‘interact’ creates a new dedicated namespace for code
          execution, assignments to variables will not affect the
          original namespaces.  However, modifications to any referenced
          mutable objects will be reflected in the original namespaces
          as usual.

     在 3.2 版被加入.

     在 3.13 版的變更: ‘exit()’ and ‘quit()’ can be used to exit the
     *note interact: 407f. command.

     在 3.13 版的變更: *note interact: 407f. directs its output to the
     debugger's output channel rather than *note sys.stderr: 8dd.

 -- Pdbcommand: alias [name [command]]

     Create an alias called 'name' that executes 'command'.  The
     'command' must 'not' be enclosed in quotes.  Replaceable parameters
     can be indicated by ‘%1’, ‘%2’, ...  and ‘%9’, while ‘%*’ is
     replaced by all the parameters.  If 'command' is omitted, the
     current alias for 'name' is shown.  If no arguments are given, all
     aliases are listed.

     Aliases may be nested and can contain anything that can be legally
     typed at the pdb prompt.  Note that internal pdb commands 'can' be
     overridden by aliases.  Such a command is then hidden until the
     alias is removed.  Aliasing is recursively applied to the first
     word of the command line; all other words in the line are left
     alone.

     As an example, here are two useful aliases (especially when placed
     in the ‘.pdbrc’ file):

          # Print instance variables (usage "pi classInst")
          alias pi for k in %1.__dict__.keys(): print(f"%1.{k} = {%1.__dict__[k]}")
          # Print instance variables in self
          alias ps pi self

 -- Pdbcommand: unalias name

     Delete the specified alias 'name'.

 -- Pdbcommand: ! statement

     Execute the (one-line) 'statement' in the context of the current
     stack frame.  The exclamation point can be omitted unless the first
     word of the statement resembles a debugger command, e.g.:

          (Pdb) ! n=42
          (Pdb)

     To set a global variable, you can prefix the assignment command
     with a *note global: 170. statement on the same line, e.g.:

          (Pdb) global list_options; list_options = ['-l']
          (Pdb)

 -- Pdbcommand: run [args ...]
 -- Pdbcommand: restart [args ...]

     Restart the debugged Python program.  If 'args' is supplied, it is
     split with *note shlex: b2. and the result is used as the new *note
     sys.argv: 11fd.  History, breakpoints, actions and debugger options
     are preserved.  *note restart: 4084. is an alias for *note run:
     4083.

 -- Pdbcommand: q(uit)

     Quit from the debugger.  The program being executed is aborted.

 -- Pdbcommand: debug code

     Enter a recursive debugger that steps through 'code' (which is an
     arbitrary expression or statement to be executed in the current
     environment).

 -- Pdbcommand: retval

     Print the return value for the last return of the current function.

 -- Pdbcommand: exceptions [excnumber]

     List or jump between chained exceptions.

     When using ‘pdb.pm()’ or ‘Pdb.post_mortem(...)’ with a chained
     exception instead of a traceback, it allows the user to move
     between the chained exceptions using ‘exceptions’ command to list
     exceptions, and ‘exception <number>’ to switch to that exception.

     範例：

          def out():
              try:
                  middle()
              except Exception as e:
                  raise ValueError("reraise middle() error") from e

          def middle():
              try:
                  return inner(0)
              except Exception as e:
                  raise ValueError("Middle fail")

          def inner(x):
              1 / x

           out()

     calling ‘pdb.pm()’ will allow to move between exceptions:

          > example.py(5)out()
          -> raise ValueError("reraise middle() error") from e

          (Pdb) exceptions
            0 ZeroDivisionError('division by zero')
            1 ValueError('Middle fail')
          > 2 ValueError('reraise middle() error')

          (Pdb) exceptions 0
          > example.py(16)inner()
          -> 1 / x

          (Pdb) up
          > example.py(10)middle()
          -> return inner(0)

     在 3.13 版被加入.

註解
....


File: python.info,  Node: Python 的分析器,  Next: timeit --- 測量小量程式片段的執行時間,  Prev: pdb --- The Python Debugger,  Up: 除錯與效能分析

5.27.5 Python 的分析器
----------------------

'原始碼：'Lib/profile.py(1) 與 Lib/pstats.py(2)

__________________________________________________________________

* Menu:

* Introduction to the profilers::
* Instant User's Manual::
* profile and cProfile Module Reference::
* The Stats Class::
* What Is Deterministic Profiling?::
* 限制::
* 校正::
* Using a custom timer::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/profile.py

   (2) https://github.com/python/cpython/tree/3.13/Lib/pstats.py


File: python.info,  Node: Introduction to the profilers,  Next: Instant User's Manual,  Up: Python 的分析器

5.27.5.1 Introduction to the profilers
......................................

*note cProfile: 20. and *note profile: 9d. provide 'deterministic
profiling' of Python programs.  A 'profile' is a set of statistics that
describes how often and for how long various parts of the program
executed.  These statistics can be formatted into reports via the *note
pstats: 9e. module.

The Python standard library provides two different implementations of
the same profiling interface:

  1. *note cProfile: 20. is recommended for most users; it's a C
     extension with reasonable overhead that makes it suitable for
     profiling long-running programs.  Based on ‘lsprof’, contributed by
     Brett Rosen and Ted Czotter.

  2. *note profile: 9d, a pure Python module whose interface is imitated
     by *note cProfile: 20, but which adds significant overhead to
     profiled programs.  If you're trying to extend the profiler in some
     way, the task might be easier with this module.  Originally
     designed and written by Jim Roskind.

     備註: The profiler modules are designed to provide an execution
     profile for a given program, not for benchmarking purposes (for
     that, there is *note timeit: d8. for reasonably accurate results).
     This particularly applies to benchmarking Python code against C
     code: the profilers introduce overhead for Python code, but not for
     C-level functions, and so the C code would seem faster than any
     Python one.


File: python.info,  Node: Instant User's Manual,  Next: profile and cProfile Module Reference,  Prev: Introduction to the profilers,  Up: Python 的分析器

5.27.5.2 Instant User's Manual
..............................

This section is provided for users that "don't want to read the manual."
It provides a very brief overview, and allows a user to rapidly perform
profiling on an existing application.

To profile a function that takes a single argument, you can do:

     import cProfile
     import re
     cProfile.run('re.compile("foo|bar")')

(Use *note profile: 9d. instead of *note cProfile: 20. if the latter is
not available on your system.)

The above action would run *note re.compile(): b7a. and print profile
results like the following:

           214 function calls (207 primitive calls) in 0.002 seconds

     Ordered by: cumulative time

     ncalls  tottime  percall  cumtime  percall filename:lineno(function)
          1    0.000    0.000    0.002    0.002 {built-in method builtins.exec}
          1    0.000    0.000    0.001    0.001 <string>:1(<module>)
          1    0.000    0.000    0.001    0.001 __init__.py:250(compile)
          1    0.000    0.000    0.001    0.001 __init__.py:289(_compile)
          1    0.000    0.000    0.000    0.000 _compiler.py:759(compile)
          1    0.000    0.000    0.000    0.000 _parser.py:937(parse)
          1    0.000    0.000    0.000    0.000 _compiler.py:598(_code)
          1    0.000    0.000    0.000    0.000 _parser.py:435(_parse_sub)

The first line indicates that 214 calls were monitored.  Of those calls,
207 were 'primitive', meaning that the call was not induced via
recursion.  The next line: ‘Ordered by: cumulative time’ indicates the
output is sorted by the ‘cumtime’ values.  The column headings include:

ncalls

     for the number of calls.

tottime

     for the total time spent in the given function (and excluding time
     made in calls to sub-functions)

percall

     is the quotient of ‘tottime’ divided by ‘ncalls’

cumtime

     is the cumulative time spent in this and all subfunctions (from
     invocation till exit).  This figure is accurate 'even' for
     recursive functions.

percall

     is the quotient of ‘cumtime’ divided by primitive calls

filename:lineno(function)

     provides the respective data of each function

When there are two numbers in the first column (for example ‘3/1’), it
means that the function recursed.  The second value is the number of
primitive calls and the former is the total number of calls.  Note that
when the function does not recurse, these two values are the same, and
only the single figure is printed.

Instead of printing the output at the end of the profile run, you can
save the results to a file by specifying a filename to the ‘run()’
function:

     import cProfile
     import re
     cProfile.run('re.compile("foo|bar")', 'restats')

The *note pstats.Stats: 408e. class reads profile results from a file
and formats them in various ways.  The files *note cProfile: 20. and
*note profile: 9d. can also be invoked as a script to profile another
script.  For example:

     python -m cProfile [-o output_file] [-s sort_order] (-m module | myscript.py)

‘-o’ writes the profile results to a file instead of to stdout

‘-s’ specifies one of the *note sort_stats(): 4090. sort values to sort
the output by.  This only applies when ‘-o’ is not supplied.

‘-m’ specifies that a module is being profiled instead of a script.

在 3.7 版被加入: 新增 ‘-m’ 選項到 *note cProfile: 20.。

在 3.8 版被加入: 新增 ‘-m’ 選項到 *note profile: 9d.。

The *note pstats: 9e. module's *note Stats: 408e. class has a variety of
methods for manipulating and printing the data saved into a profile
results file:

     import pstats
     from pstats import SortKey
     p = pstats.Stats('restats')
     p.strip_dirs().sort_stats(-1).print_stats()

The *note strip_dirs(): 4091. method removed the extraneous path from
all the module names.  The *note sort_stats(): 4090. method sorted all
the entries according to the standard module/line/name string that is
printed.  The *note print_stats(): 4092. method printed out all the
statistics.  You might try the following sort calls:

     p.sort_stats(SortKey.NAME)
     p.print_stats()

The first call will actually sort the list by function name, and the
second call will print out the statistics.  The following are some
interesting calls to experiment with:

     p.sort_stats(SortKey.CUMULATIVE).print_stats(10)

This sorts the profile by cumulative time in a function, and then only
prints the ten most significant lines.  If you want to understand what
algorithms are taking time, the above line is what you would use.

If you were looking to see what functions were looping a lot, and taking
a lot of time, you would do:

     p.sort_stats(SortKey.TIME).print_stats(10)

to sort according to time spent within each function, and then print the
statistics for the top ten functions.

You might also try:

     p.sort_stats(SortKey.FILENAME).print_stats('__init__')

This will sort all the statistics by file name, and then print out
statistics for only the class init methods (since they are spelled with
‘__init__’ in them).  As one final example, you could try:

     p.sort_stats(SortKey.TIME, SortKey.CUMULATIVE).print_stats(.5, 'init')

This line sorts statistics with a primary key of time, and a secondary
key of cumulative time, and then prints out some of the statistics.  To
be specific, the list is first culled down to 50% (re: ‘.5’) of its
original size, then only lines containing ‘init’ are maintained, and
that sub-sub-list is printed.

If you wondered what functions called the above functions, you could now
(‘p’ is still sorted according to the last criteria) do:

     p.print_callers(.5, 'init')

and you would get a list of callers for each of the listed functions.

If you want more functionality, you're going to have to read the manual,
or guess what the following functions do:

     p.print_callees()
     p.add('restats')

Invoked as a script, the *note pstats: 9e. module is a statistics
browser for reading and examining profile dumps.  It has a simple
line-oriented interface (implemented using *note cmd: 12.) and
interactive help.


File: python.info,  Node: profile and cProfile Module Reference,  Next: The Stats Class,  Prev: Instant User's Manual,  Up: Python 的分析器

5.27.5.3 ‘profile’ and ‘cProfile’ Module Reference
..................................................

Both the *note profile: 9d. and *note cProfile: 20. modules provide the
following functions:

 -- 函式: profile.run (command, filename=None, sort=-1)

     This function takes a single argument that can be passed to the
     *note exec(): 162. function, and an optional file name.  In all
     cases this routine executes:

          exec(command, __main__.__dict__, __main__.__dict__)

     and gathers profiling statistics from the execution.  If no file
     name is present, then this function automatically creates a *note
     Stats: 408e. instance and prints a simple profiling report.  If the
     sort value is specified, it is passed to this *note Stats: 408e.
     instance to control how the results are sorted.

 -- 函式: profile.runctx (command, globals, locals, filename=None,
          sort=-1)

     This function is similar to *note run(): 4094, with added arguments
     to supply the globals and locals mappings for the 'command' string.
     This routine executes:

          exec(command, globals, locals)

     and gathers profiling statistics as in the *note run(): 4094.
     function above.

 -- 類別: profile.Profile (timer=None, timeunit=0.0, subcalls=True,
          builtins=True)

     This class is normally only used if more precise control over
     profiling is needed than what the ‘cProfile.run()’ function
     provides.

     A custom timer can be supplied for measuring how long code takes to
     run via the 'timer' argument.  This must be a function that returns
     a single number representing the current time.  If the number is an
     integer, the 'timeunit' specifies a multiplier that specifies the
     duration of each unit of time.  For example, if the timer returns
     times measured in thousands of seconds, the time unit would be
     ‘.001’.

     Directly using the *note Profile: 987. class allows formatting
     profile results without writing the profile data to a file:

          import cProfile, pstats, io
          from pstats import SortKey
          pr = cProfile.Profile()
          pr.enable()
          # ... do something ...
          pr.disable()
          s = io.StringIO()
          sortby = SortKey.CUMULATIVE
          ps = pstats.Stats(pr, stream=s).sort_stats(sortby)
          ps.print_stats()
          print(s.getvalue())

     The *note Profile: 987. class can also be used as a context manager
     (supported only in *note cProfile: 20. module.  see *note
     情境管理器型別: 1e95.):

          import cProfile

          with cProfile.Profile() as pr:
              # ... do something ...

              pr.print_stats()

     在 3.8 版的變更: 新增情境管理器的支援。

      -- 方法: enable ()

          Start collecting profiling data.  Only in *note cProfile: 20.

      -- 方法: disable ()

          Stop collecting profiling data.  Only in *note cProfile: 20.

      -- 方法: create_stats ()

          Stop collecting profiling data and record the results
          internally as the current profile.

      -- 方法: print_stats (sort=-1)

          Create a *note Stats: 408e. object based on the current
          profile and print the results to stdout.

          The 'sort' parameter specifies the sorting order of the
          displayed statistics.  It accepts a single key or a tuple of
          keys to enable multi-level sorting, as in *note
          Stats.sort_stats: 4090.

          在 3.13 版被加入: *note print_stats(): 4099. now accepts a
          tuple of keys.

      -- 方法: dump_stats (filename)

          Write the results of the current profile to 'filename'.

      -- 方法: run (cmd)

          Profile the cmd via *note exec(): 162.

      -- 方法: runctx (cmd, globals, locals)

          Profile the cmd via *note exec(): 162. with the specified
          global and local environment.

      -- 方法: runcall (func, /, *args, **kwargs)

          Profile ‘func(*args, **kwargs)’

Note that profiling will only work if the called command/function
actually returns.  If the interpreter is terminated (e.g.  via a *note
sys.exit(): 12dd. call during the called command/function execution) no
profiling results will be printed.


File: python.info,  Node: The Stats Class,  Next: What Is Deterministic Profiling?,  Prev: profile and cProfile Module Reference,  Up: Python 的分析器

5.27.5.4 The ‘Stats’ Class
..........................

Analysis of the profiler data is done using the *note Stats: 408e.
class.

 -- 類別: pstats.Stats (*filenames or profile, stream=sys.stdout)

     This class constructor creates an instance of a "statistics object"
     from a 'filename' (or list of filenames) or from a ‘Profile’
     instance.  Output will be printed to the stream specified by
     'stream'.

     The file selected by the above constructor must have been created
     by the corresponding version of *note profile: 9d. or *note
     cProfile: 20.  To be specific, there is 'no' file compatibility
     guaranteed with future versions of this profiler, and there is no
     compatibility with files produced by other profilers, or the same
     profiler run on a different operating system.  If several files are
     provided, all the statistics for identical functions will be
     coalesced, so that an overall view of several processes can be
     considered in a single report.  If additional files need to be
     combined with data in an existing *note Stats: 408e. object, the
     *note add(): 409f. method can be used.

     Instead of reading the profile data from a file, a
     ‘cProfile.Profile’ or *note profile.Profile: 987. object can be
     used as the profile data source.

     *note Stats: 408e. objects have the following methods:

      -- 方法: strip_dirs ()

          This method for the *note Stats: 408e. class removes all
          leading path information from file names.  It is very useful
          in reducing the size of the printout to fit within (close to)
          80 columns.  This method modifies the object, and the stripped
          information is lost.  After performing a strip operation, the
          object is considered to have its entries in a "random" order,
          as it was just after object initialization and loading.  If
          *note strip_dirs(): 4091. causes two function names to be
          indistinguishable (they are on the same line of the same
          filename, and have the same function name), then the
          statistics for these two entries are accumulated into a single
          entry.

      -- 方法: add (*filenames)

          This method of the *note Stats: 408e. class accumulates
          additional profiling information into the current profiling
          object.  Its arguments should refer to filenames created by
          the corresponding version of *note profile.run(): 4094. or
          ‘cProfile.run()’.  Statistics for identically named (re: file,
          line, name) functions are automatically accumulated into
          single function statistics.

      -- 方法: dump_stats (filename)

          Save the data loaded into the *note Stats: 408e. object to a
          file named 'filename'.  The file is created if it does not
          exist, and is overwritten if it already exists.  This is
          equivalent to the method of the same name on the *note
          profile.Profile: 987. and ‘cProfile.Profile’ classes.

      -- 方法: sort_stats (*keys)

          This method modifies the *note Stats: 408e. object by sorting
          it according to the supplied criteria.  The argument can be
          either a string or a SortKey enum identifying the basis of a
          sort (example: ‘'time'’, ‘'name'’, ‘SortKey.TIME’ or
          ‘SortKey.NAME’).  The SortKey enums argument have advantage
          over the string argument in that it is more robust and less
          error prone.

          When more than one key is provided, then additional keys are
          used as secondary criteria when there is equality in all keys
          selected before them.  For example, ‘sort_stats(SortKey.NAME,
          SortKey.FILE)’ will sort all the entries according to their
          function name, and resolve all ties (identical function names)
          by sorting by file name.

          For the string argument, abbreviations can be used for any key
          names, as long as the abbreviation is unambiguous.

          The following are the valid string and SortKey:

          Valid String Arg       Valid enum Arg            含義
                                                           
          ----------------------------------------------------------------------------
                                                           
          ‘'calls'’              SortKey.CALLS             call count
                                                           
                                                           
          ‘'cumulative'’         SortKey.CUMULATIVE        cumulative time
                                                           
                                                           
          ‘'cumtime'’            N/A                       cumulative time
                                                           
                                                           
          ‘'file'’               N/A                       file name（檔案名稱）
                                                           
                                                           
          ‘'filename'’           SortKey.FILENAME          file name（檔案名稱）
                                                           
                                                           
          ‘'module'’             N/A                       file name（檔案名稱）
                                                           
                                                           
          ‘'ncalls'’             N/A                       call count
                                                           
                                                           
          ‘'pcalls'’             SortKey.PCALLS            primitive call count
                                                           
                                                           
          ‘'line'’               SortKey.LINE              列號
                                                           
                                                           
          ‘'name'’               SortKey.NAME              function name
                                                           
                                                           
          ‘'nfl'’                SortKey.NFL               name/file/line
                                                           
                                                           
          ‘'stdname'’            SortKey.STDNAME           standard name
                                                           
                                                           
          ‘'time'’               SortKey.TIME              internal time
                                                           
                                                           
          ‘'tottime'’            N/A                       internal time
                                                           

          Note that all sorts on statistics are in descending order
          (placing most time consuming items first), where as name,
          file, and line number searches are in ascending order
          (alphabetical).  The subtle distinction between ‘SortKey.NFL’
          and ‘SortKey.STDNAME’ is that the standard name is a sort of
          the name as printed, which means that the embedded line
          numbers get compared in an odd way.  For example, lines 3, 20,
          and 40 would (if the file names were the same) appear in the
          string order 20, 3 and 40.  In contrast, ‘SortKey.NFL’ does a
          numeric compare of the line numbers.  In fact,
          ‘sort_stats(SortKey.NFL)’ is the same as
          ‘sort_stats(SortKey.NAME, SortKey.FILENAME, SortKey.LINE)’.

          For backward-compatibility reasons, the numeric arguments
          ‘-1’, ‘0’, ‘1’, and ‘2’ are permitted.  They are interpreted
          as ‘'stdname'’, ‘'calls'’, ‘'time'’, and ‘'cumulative'’
          respectively.  If this old style format (numeric) is used,
          only one sort key (the numeric key) will be used, and
          additional arguments will be silently ignored.

          在 3.7 版被加入: Added the SortKey enum.

      -- 方法: reverse_order ()

          This method for the *note Stats: 408e. class reverses the
          ordering of the basic list within the object.  Note that by
          default ascending vs descending order is properly selected
          based on the sort key of choice.

      -- 方法: print_stats (*restrictions)

          This method for the *note Stats: 408e. class prints out a
          report as described in the *note profile.run(): 4094.
          definition.

          The order of the printing is based on the last *note
          sort_stats(): 4090. operation done on the object (subject to
          caveats in *note add(): 409f. and *note strip_dirs(): 4091.).

          The arguments provided (if any) can be used to limit the list
          down to the significant entries.  Initially, the list is taken
          to be the complete set of profiled functions.  Each
          restriction is either an integer (to select a count of lines),
          or a decimal fraction between 0.0 and 1.0 inclusive (to select
          a percentage of lines), or a string that will interpreted as a
          regular expression (to pattern match the standard name that is
          printed).  If several restrictions are provided, then they are
          applied sequentially.  For example:

               print_stats(.1, 'foo:')

          would first limit the printing to first 10% of list, and then
          only print functions that were part of filename ‘.*foo:’.  In
          contrast, the command:

               print_stats('foo:', .1)

          would limit the list to all functions having file names
          ‘.*foo:’, and then proceed to only print the first 10% of
          them.

      -- 方法: print_callers (*restrictions)

          This method for the *note Stats: 408e. class prints a list of
          all functions that called each function in the profiled
          database.  The ordering is identical to that provided by *note
          print_stats(): 4092, and the definition of the restricting
          argument is also identical.  Each caller is reported on its
          own line.  The format differs slightly depending on the
          profiler that produced the stats:

             * With *note profile: 9d, a number is shown in parentheses
               after each caller to show how many times this specific
               call was made.  For convenience, a second
               non-parenthesized number repeats the cumulative time
               spent in the function at the right.

             * With *note cProfile: 20, each caller is preceded by three
               numbers: the number of times this specific call was made,
               and the total and cumulative times spent in the current
               function while it was invoked by this specific caller.

      -- 方法: print_callees (*restrictions)

          This method for the *note Stats: 408e. class prints a list of
          all function that were called by the indicated function.
          Aside from this reversal of direction of calls (re: called vs
          was called by), the arguments and ordering are identical to
          the *note print_callers(): 40a2. method.

      -- 方法: get_stats_profile ()

          This method returns an instance of StatsProfile, which
          contains a mapping of function names to instances of
          FunctionProfile.  Each FunctionProfile instance holds
          information related to the function's profile such as how long
          the function took to run, how many times it was called, etc...

          在 3.9 版被加入: Added the following dataclasses:
          StatsProfile, FunctionProfile.  Added the following function:
          get_stats_profile.


File: python.info,  Node: What Is Deterministic Profiling?,  Next: 限制,  Prev: The Stats Class,  Up: Python 的分析器

5.27.5.5 What Is Deterministic Profiling?
.........................................

'Deterministic profiling' is meant to reflect the fact that all
'function call', 'function return', and 'exception' events are
monitored, and precise timings are made for the intervals between these
events (during which time the user's code is executing).  In contrast,
'statistical profiling' (which is not done by this module) randomly
samples the effective instruction pointer, and deduces where time is
being spent.  The latter technique traditionally involves less overhead
(as the code does not need to be instrumented), but provides only
relative indications of where time is being spent.

In Python, since there is an interpreter active during execution, the
presence of instrumented code is not required in order to do
deterministic profiling.  Python automatically provides a 'hook'
(optional callback) for each event.  In addition, the interpreted nature
of Python tends to add so much overhead to execution, that deterministic
profiling tends to only add small processing overhead in typical
applications.  The result is that deterministic profiling is not that
expensive, yet provides extensive run time statistics about the
execution of a Python program.

Call count statistics can be used to identify bugs in code (surprising
counts), and to identify possible inline-expansion points (high call
counts).  Internal time statistics can be used to identify "hot loops"
that should be carefully optimized.  Cumulative time statistics should
be used to identify high level errors in the selection of algorithms.
Note that the unusual handling of cumulative times in this profiler
allows statistics for recursive implementations of algorithms to be
directly compared to iterative implementations.


File: python.info,  Node: 限制,  Next: 校正,  Prev: What Is Deterministic Profiling?,  Up: Python 的分析器

5.27.5.6 限制
.............

One limitation has to do with accuracy of timing information.  There is
a fundamental problem with deterministic profilers involving accuracy.
The most obvious restriction is that the underlying "clock" is only
ticking at a rate (typically) of about .001 seconds.  Hence no
measurements will be more accurate than the underlying clock.  If enough
measurements are taken, then the "error" will tend to average out.
Unfortunately, removing this first error induces a second source of
error.

The second problem is that it "takes a while" from when an event is
dispatched until the profiler's call to get the time actually 'gets' the
state of the clock.  Similarly, there is a certain lag when exiting the
profiler event handler from the time that the clock's value was obtained
(and then squirreled away), until the user's code is once again
executing.  As a result, functions that are called many times, or call
many functions, will typically accumulate this error.  The error that
accumulates in this fashion is typically less than the accuracy of the
clock (less than one clock tick), but it 'can' accumulate and become
very significant.

The problem is more important with *note profile: 9d. than with the
lower-overhead *note cProfile: 20.  For this reason, *note profile: 9d.
provides a means of calibrating itself for a given platform so that this
error can be probabilistically (on the average) removed.  After the
profiler is calibrated, it will be more accurate (in a least square
sense), but it will sometimes produce negative numbers (when call counts
are exceptionally low, and the gods of probability work against you :-).
)  Do 'not' be alarmed by negative numbers in the profile.  They should
'only' appear if you have calibrated your profiler, and the results are
actually better than without calibration.


File: python.info,  Node: 校正,  Next: Using a custom timer,  Prev: 限制,  Up: Python 的分析器

5.27.5.7 校正
.............

The profiler of the *note profile: 9d. module subtracts a constant from
each event handling time to compensate for the overhead of calling the
time function, and socking away the results.  By default, the constant
is 0.  The following procedure can be used to obtain a better constant
for a given platform (see *note 限制: 40a8.).

     import profile
     pr = profile.Profile()
     for i in range(5):
         print(pr.calibrate(10000))

The method executes the number of Python calls given by the argument,
directly and again under the profiler, measuring the time for both.  It
then computes the hidden overhead per profiler event, and returns that
as a float.  For example, on a 1.8Ghz Intel Core i5 running macOS, and
using Python's time.process_time() as the timer, the magical number is
about 4.04e-6.

The object of this exercise is to get a fairly consistent result.  If
your computer is 'very' fast, or your timer function has poor
resolution, you might have to pass 100000, or even 1000000, to get
consistent results.

When you have a consistent answer, there are three ways you can use it:

     import profile

     # 1. Apply computed bias to all Profile instances created hereafter.
     profile.Profile.bias = your_computed_bias

     # 2. Apply computed bias to a specific Profile instance.
     pr = profile.Profile()
     pr.bias = your_computed_bias

     # 3. Specify computed bias in instance constructor.
     pr = profile.Profile(bias=your_computed_bias)

If you have a choice, you are better off choosing a smaller constant,
and then your results will "less often" show up as negative in profile
statistics.


File: python.info,  Node: Using a custom timer,  Prev: 校正,  Up: Python 的分析器

5.27.5.8 Using a custom timer
.............................

If you want to change how current time is determined (for example, to
force use of wall-clock time or elapsed process time), pass the timing
function you want to the ‘Profile’ class constructor:

     pr = profile.Profile(your_time_func)

The resulting profiler will then call ‘your_time_func’.  Depending on
whether you are using *note profile.Profile: 987. or ‘cProfile.Profile’,
‘your_time_func’'s return value will be interpreted differently:

*note profile.Profile: 987.

     ‘your_time_func’ should return a single number, or a list of
     numbers whose sum is the current time (like what *note os.times():
     10ad. returns).  If the function returns a single time number, or
     the list of returned numbers has length 2, then you will get an
     especially fast version of the dispatch routine.

     Be warned that you should calibrate the profiler class for the
     timer function that you choose (see *note 校正: 40aa.).  For most
     machines, a timer that returns a lone integer value will provide
     the best results in terms of low overhead during profiling.  (*note
     os.times(): 10ad. is 'pretty' bad, as it returns a tuple of
     floating-point values).  If you want to substitute a better timer
     in the cleanest fashion, derive a class and hardwire a replacement
     dispatch method that best handles your timer call, along with the
     appropriate calibration constant.

‘cProfile.Profile’

     ‘your_time_func’ should return a single number.  If it returns
     integers, you can also invoke the class constructor with a second
     argument specifying the real duration of one unit of time.  For
     example, if ‘your_integer_time_func’ returns times measured in
     thousands of seconds, you would construct the ‘Profile’ instance as
     follows:

          pr = cProfile.Profile(your_integer_time_func, 0.001)

     As the ‘cProfile.Profile’ class cannot be calibrated, custom timer
     functions should be used with care and should be as fast as
     possible.  For the best results with a custom timer, it might be
     necessary to hard-code it in the C source of the internal ‘_lsprof’
     module.

Python 3.3 adds several new functions in *note time: d7. that can be
used to make precise measurements of process or wall-clock time.  For
example, see *note time.perf_counter(): a2b.


File: python.info,  Node: timeit --- 測量小量程式片段的執行時間,  Next: trace --- 追蹤或追查 Python 陳述式執行,  Prev: Python 的分析器,  Up: 除錯與效能分析

5.27.6 ‘timeit’ -- 測量小量程式片段的執行時間
---------------------------------------------

'原始碼：'Lib/timeit.py(1)

__________________________________________________________________

該模組提供了一種對少量 Python 程式碼進行計時的簡單方法。它有一個*note
命令列介面: 40af.和一個*note 可呼叫介面: 40b0.，它避免了許多測量執行時間
的常見陷阱。另請參閱由 O'Reilly 出版的 'Python 錦囊妙計 (Python
Cookbook)' 第二版中 Tim Peters 所寫的「演算法」章節的介紹。

* Menu:

* 基礎範例: 基礎範例<2>.
* Python 介面::
* 命令列介面: 命令列介面<4>.
* 範例: 範例<42>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/timeit.py


File: python.info,  Node: 基礎範例<2>,  Next: Python 介面,  Up: timeit --- 測量小量程式片段的執行時間

5.27.6.1 基礎範例
.................

以下範例展示了如何使用*note 命令列介面: 40af.來比較三個不同的運算式：

     $ python -m timeit "'-'.join(str(n) for n in range(100))"
     10000 loops, best of 5: 30.2 usec per loop
     $ python -m timeit "'-'.join([str(n) for n in range(100)])"
     10000 loops, best of 5: 27.5 usec per loop
     $ python -m timeit "'-'.join(map(str, range(100)))"
     10000 loops, best of 5: 23.2 usec per loop

這可以透過 *note Python 介面: 40b0.來實現：

     >>> import timeit
     >>> timeit.timeit('"-".join(str(n) for n in range(100))', number=10000)
     0.3018611848820001
     >>> timeit.timeit('"-".join([str(n) for n in range(100)])', number=10000)
     0.2727368790656328
     >>> timeit.timeit('"-".join(map(str, range(100)))', number=10000)
     0.23702679807320237

也可以在 *note Python 介面: 40b0.傳遞可呼叫物件：

     >>> timeit.timeit(lambda: "-".join(map(str, range(100))), number=10000)
     0.19665591977536678

但請注意，僅當使用命令列界面時 *note timeit(): e22. 才會自動確定重複次數
。在*note 範例: 40b2.章節中有更進階的範例。


File: python.info,  Node: Python 介面,  Next: 命令列介面<4>,  Prev: 基礎範例<2>,  Up: timeit --- 測量小量程式片段的執行時間

5.27.6.2 Python 介面
....................

該模組定義了三個便利函式和一個公開類別：

 -- 函式: timeit.timeit (stmt='pass', setup='pass', timer=<default
          timer>, number=1000000, globals=None)

     使用給定的陳述式、'setup' 程式碼和 'timer' 函式建立一個 *note
     Timer: 1433. 實例，並執行其 *note timeit(): c94. 方法 'number' 次。
     可選的 'globals' 引數指定會在其中執行程式碼的命名空間。

     在 3.5 版的變更: 新增 'globals' 選用參數。

 -- 函式: timeit.repeat (stmt='pass', setup='pass', timer=<default
          timer>, repeat=5, number=1000000, globals=None)

     使用給定的陳述式、'setup' 程式碼和 'timer' 函式建立一個 *note
     Timer: 1433. 實例，並使用給定的 'repeat' 計數和 'number' 來運行其
     *note repeat(): 40b5. 方法。可選的 'globals' 引數指定會在其中執行程
     式碼的命名空間。

     在 3.5 版的變更: 新增 'globals' 選用參數。

     在 3.7 版的變更: 'repeat' 的預設值從 3 更改為 5。

 -- 函式: timeit.default_timer ()

     預設計時器始終為 time.perf_counter()，會回傳浮點秒數。另一種方法是
     time.perf_counter_ns，會回傳整數奈秒。

     在 3.3 版的變更: *note time.perf_counter(): a2b. 現在是預設計時器。

 -- 類別: timeit.Timer (stmt='pass', setup='pass', timer=<timer
          function>, globals=None)

     用於計時小程式碼片段執行速度的類別。

     建構函式接受一個要計時的陳述式、一個用於設定的附加陳述式和一個計時
     器函式。兩個陳述式都預設為 ‘'pass'’；計時器函式會與平台相依（請參閱
     模組文件字串 (doc string)）。'stmt' 和 'setup' 還可以包含由 ‘;’ 或
     換行符號分隔的多個陳述式，只要它們不包含多行字串文字即可。預設情況
     下，該陳述式將在 timeit 的命名空間內執行；可以透過將命名空間傳遞給
     'globals' 來控制此行為。

     要測量第一個陳述式的執行時間，請使用 *note timeit(): c94. 方法。
     *note repeat(): 40b5. 和 *note autorange(): c93. 方法是多次呼叫
     *note timeit(): c94. 的便捷方法。

     'setup' 的執行時間不包含在總體運行計時中。

     'stmt' 和 'setup' 參數還可以接受無需引數即可呼叫的物件。這會把對它
     們的呼叫嵌入到計時器函式中，然後由 *note timeit(): c94. 去執行。請
     注意，在這種情況下，因有額外的函式呼叫，時間開銷 (timing overhead)
     會稍大一些。

     在 3.5 版的變更: 新增 'globals' 選用參數。

      -- 方法: timeit (number=1000000)

          主陳述式執行 'number' 次的時間。這將執行一次設定陳述式，然後回
          傳多次執行主陳述式所需的時間。預設計時器以浮點形式回傳秒數，引
          數是迴圈的次數，預設為一百萬次。要使用的主陳述式、設定陳述式和
          計時器函式會被傳遞給建構函式。

               備註: 預設情況下 *note timeit(): c94. 在計時期間會暫時關
               閉*note 垃圾回收: 181c.。這種方法的優點是它使獨立時序更具
               可比較性，缺點是 GC 可能是被測函式性能的重要組成部分。如
               果是這樣，可以將 GC 作為 'setup' 字串中的第一個陳述式以重
               新啟用。例如：

                    timeit.Timer('for i in range(10): oct(i)', 'gc.enable()').timeit()

      -- 方法: autorange (callback=None)

          自動決定呼叫 *note timeit(): c94. 次數。

          這是一個便捷函式，它重複呼叫 *note timeit(): c94. 以使得總時間
          >= 0.2 秒，再回傳最終結果（迴圈數、該迴圈數所花費的時間）。它
          以 1、2、5、10、20、50...  的順序遞增數字來呼叫 *note
          timeit(): c94. 直到所用時間至少為 0.2 秒。

          如果有給定 'callback' 且不是 ‘None’，則每次試驗後都會使用兩個
          引數來呼叫它：‘callback(number, time_taken)’。

          在 3.6 版被加入.

      -- 方法: repeat (repeat=5, number=1000000)

          呼叫 *note timeit(): c94. 數次。

          這是一個方便的函式，它會重複呼叫 *note timeit(): c94. 並回傳結
          果列表。第一個引數指定呼叫 *note timeit(): c94. 的次數，第二個
          引數指定 *note timeit(): c94. 的 'number' 引數。

               備註: 人們很容易根據結果向量來計算出平均值和標準差並將其
               作為依歸，然而這並不是很有用。在典型情況下，最低值給出了
               機器運行給定程式碼片段的速度的下限；結果向量中較高的值通
               常不是由 Python 速度的變化所引起，而是由干擾計時精度的其
               他行程造成的。因此，結果中的 *note min(): eac. 可能是你應
               該感興趣的唯一數字。在解讀該數據後，你應該查看整個向量並
               以常識判讀而非單純仰賴統計資訊。

          在 3.7 版的變更: 'repeat' 的預設值從 3 更改為 5。

      -- 方法: print_exc (file=None)

          從計時程式碼印出回溯 (traceback) 的輔助函式。

          典型用法：

               t = Timer(...)       # outside the try/except
               try:
                   t.timeit(...)    # or t.repeat(...)
               except Exception:
                   t.print_exc()

          相對於標準回溯的優點是，已編譯模板中的原始程式碼會被顯示出來。
          可選的 'file' 引數指定回溯的發送位置；它預設為 *note
          sys.stderr: 8dd.。


File: python.info,  Node: 命令列介面<4>,  Next: 範例<42>,  Prev: Python 介面,  Up: timeit --- 測量小量程式片段的執行時間

5.27.6.3 命令列介面
...................

當從命令列作為程式呼叫時，請使用以下形式：

     python -m timeit [-n N] [-r N] [-u U] [-s S] [-p] [-v] [-h] [statement ...]

其中之以下選項：

 -- Option: -n N, --number=N

     執行 'statement' 多少次

 -- Option: -r N, --repeat=N

     計時器重複多少次（預設 5）

 -- Option: -s S, --setup=S

     會在一開始執行一次的陳述式（預設為 ‘pass’）

 -- Option: -p, --process

     若要測量行程時間 (process time) 而非掛鐘時間 (wallclock time)，請使
     用 *note time.process_time(): a2c. 而不是預設的 *note
     time.perf_counter(): a2b.

     在 3.3 版被加入.

 -- Option: -u, --unit=U

     指定定時器輸出的時間單位；可以選擇 ‘nsec’、‘usec’、‘msec’ 或 ‘sec’

     在 3.5 版被加入.

 -- Option: -v, --verbose

     印出原始計時結果；重複執行以獲得更高的數字精度

 -- Option: -h, --help

     印出一條簡短的使用訊息並退出

可以透過將每一列陳述式指定為單獨引數來給定多列陳述式；可透過將引數括在引
號中並使用前導空格以實現縮進列 (indented lines)。多個 *note -s: 40bd. 選
項的作用類似。

如果沒有給定 *note -n: 40b9.，則透過嘗試從序列 1, 2, 5, 10, 20, 50, ...
中增加數字來計算合適的迴圈次數，直到總時間至少為 0.2 秒。

*note default_timer(): 40b6. 測量可能會受到同一台機器上運行的其他程式的
影響，因此，當需要精確計時時，最好的做法是重複計時幾次並使用最佳時間。
*note -r: 40bb. 選項對此很有用；在大多數情況下，預設的重複 5 次可能就足
夠了。你可以使用 *note time.process_time(): a2c. 來測量 CPU 時間。

     備註: 執行 pass 陳述式會產生一定的基本開銷。這裡的程式碼並不試圖隱
     藏它，但你應該意識到它的存在。可以透過不帶引數呼叫程式來測量這個基
     本開銷，且不同 Python 版本之間的基本開銷可能有所不同。


File: python.info,  Node: 範例<42>,  Prev: 命令列介面<4>,  Up: timeit --- 測量小量程式片段的執行時間

5.27.6.4 範例
.............

可以提供一個僅會在開始時執行一次的設定陳述式：

     $ python -m timeit -s "text = 'sample string'; char = 'g'" "char in text"
     5000000 loops, best of 5: 0.0877 usec per loop
     $ python -m timeit -s "text = 'sample string'; char = 'g'" "text.find(char)"
     1000000 loops, best of 5: 0.342 usec per loop

輸出中包含三個欄位。迴圈計數，它告訴你每次計時迴圈內重複運行陳述式主體的
次數。重複計數（「最好的 5 次」）告訴你計時迴圈重複了多少次。以及最後陳
述式主體在計時迴圈的最佳的幾次重複執行內平均花費的時間。也就是說，最快的
幾次重複執行所花費的總時間除以迴圈計數。

     >>> import timeit
     >>> timeit.timeit('char in text', setup='text = "sample string"; char = "g"')
     0.41440500499993504
     >>> timeit.timeit('text.find(char)', setup='text = "sample string"; char = "g"')
     1.7246671520006203

同樣可以使用 *note Timer: 1433. 類別及其方法來完成：

     >>> import timeit
     >>> t = timeit.Timer('char in text', setup='text = "sample string"; char = "g"')
     >>> t.timeit()
     0.3955516149999312
     >>> t.repeat()
     [0.40183617287970225, 0.37027556854118704, 0.38344867356679524, 0.3712595970846668, 0.37866875250654886]

以下範例展示如何對包含多行的運算式進行計時。這裡我們使用 *note
hasattr(): 479. 與 *note try: 68c./*note except: 171. 來測試缺失和存在之
物件屬性並比較其花費 (cost)：

     $ python -m timeit "try:" "  str.__bool__" "except AttributeError:" "  pass"
     20000 loops, best of 5: 15.7 usec per loop
     $ python -m timeit "if hasattr(str, '__bool__'): pass"
     50000 loops, best of 5: 4.26 usec per loop

     $ python -m timeit "try:" "  int.__bool__" "except AttributeError:" "  pass"
     200000 loops, best of 5: 1.43 usec per loop
     $ python -m timeit "if hasattr(int, '__bool__'): pass"
     100000 loops, best of 5: 2.23 usec per loop

     >>> import timeit
     >>> # attribute is missing
     >>> s = """\
     ... try:
     ...     str.__bool__
     ... except AttributeError:
     ...     pass
     ... """
     >>> timeit.timeit(stmt=s, number=100000)
     0.9138244460009446
     >>> s = "if hasattr(str, '__bool__'): pass"
     >>> timeit.timeit(stmt=s, number=100000)
     0.5829014980008651
     >>>
     >>> # attribute is present
     >>> s = """\
     ... try:
     ...     int.__bool__
     ... except AttributeError:
     ...     pass
     ... """
     >>> timeit.timeit(stmt=s, number=100000)
     0.04215312199994514
     >>> s = "if hasattr(int, '__bool__'): pass"
     >>> timeit.timeit(stmt=s, number=100000)
     0.08588060699912603

要讓 *note timeit: d8. 模組存取你定義的函式，你可以傳遞一個包含 import 陳
述式的 'setup' 參數：

     def test():
         """Stupid test function"""
         L = [i for i in range(100)]

     if __name__ == '__main__':
         import timeit
         print(timeit.timeit("test()", setup="from __main__ import test"))

另一種選擇是將 *note globals(): 176a. 傳遞給 'globals' 參數，這將導致程
式碼在當前的全域命名空間中執行，這比單獨指定 import 更方便：

     def f(x):
         return x**2
     def g(x):
         return x**4
     def h(x):
         return x**8

     import timeit
     print(timeit.timeit('[func(42) for func in (f,g,h)]', globals=globals()))


File: python.info,  Node: trace --- 追蹤或追查 Python 陳述式執行,  Next: tracemalloc --- 追蹤記憶體配置,  Prev: timeit --- 測量小量程式片段的執行時間,  Up: 除錯與效能分析

5.27.7 ‘trace’ -- 追蹤或追查 Python 陳述式執行
----------------------------------------------

'原始碼：'Lib/trace.py(1)

__________________________________________________________________

The *note trace: e6. module allows you to trace program execution,
generate annotated statement coverage listings, print caller/callee
relationships and list functions executed during a program run.  It can
be used in another program or from the command line.

也參考
......

Coverage.py(2)

     A popular third-party coverage tool that provides HTML output along
     with advanced features such as branch coverage.

* Menu:

* Command-Line Usage::
* Programmatic Interface::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/trace.py

   (2) https://coverage.readthedocs.io/


File: python.info,  Node: Command-Line Usage,  Next: Programmatic Interface,  Up: trace --- 追蹤或追查 Python 陳述式執行

5.27.7.1 Command-Line Usage
...........................

The *note trace: e6. module can be invoked from the command line.  It
can be as simple as

     python -m trace --count -C . somefile.py ...

The above will execute ‘somefile.py’ and generate annotated listings of
all Python modules imported during the execution into the current
directory.

 -- Option: --help

     Display usage and exit.

 -- Option: --version

     Display the version of the module and exit.

在 3.8 版被加入: Added ‘--module’ option that allows to run an
executable module.

* Menu:

* Main options::
* Modifiers::
* Filters::


File: python.info,  Node: Main options,  Next: Modifiers,  Up: Command-Line Usage

5.27.7.2 Main options
.....................

At least one of the following options must be specified when invoking
*note trace: e6.  The *note -listfuncs: 40cf. option is mutually
exclusive with the *note -trace: 40d0. and *note -count: 40d1. options.
When *note -listfuncs: 40cf. is provided, neither *note -count: 40d1.
nor *note -trace: 40d0. are accepted, and vice versa.

 -- Option: -c, --count

     Produce a set of annotated listing files upon program completion
     that shows how many times each statement was executed.  See also
     *note -coverdir: 40d3, *note -file: 40d4. and *note -no-report:
     40d5. below.

 -- Option: -t, --trace

     Display lines as they are executed.

 -- Option: -l, --listfuncs

     Display the functions executed by running the program.

 -- Option: -r, --report

     Produce an annotated list from an earlier program run that used the
     *note -count: 40d1. and *note -file: 40d4. option.  This does not
     execute any code.

 -- Option: -T, --trackcalls

     Display the calling relationships exposed by running the program.


File: python.info,  Node: Modifiers,  Next: Filters,  Prev: Main options,  Up: Command-Line Usage

5.27.7.3 Modifiers
..................

 -- Option: -f, --file=<file>

     Name of a file to accumulate counts over several tracing runs.
     Should be used with the *note -count: 40d1. option.

 -- Option: -C, --coverdir=<dir>

     Directory where the report files go.  The coverage report for
     ‘package.module’ is written to file
     ‘`dir'/`package'/`module'.cover’.

 -- Option: -m, --missing

     When generating annotated listings, mark lines which were not
     executed with ‘>>>>>>’.

 -- Option: -s, --summary

     When using *note -count: 40d1. or *note -report: 40d8, write a
     brief summary to stdout for each file processed.

 -- Option: -R, --no-report

     Do not generate annotated listings.  This is useful if you intend
     to make several runs with *note -count: 40d1, and then produce a
     single set of annotated listings at the end.

 -- Option: -g, --timing

     Prefix each line with the time since the program started.  Only
     used while tracing.


File: python.info,  Node: Filters,  Prev: Modifiers,  Up: Command-Line Usage

5.27.7.4 Filters
................

These options may be repeated multiple times.

 -- Option: --ignore-module=<mod>

     Ignore each of the given module names and its submodules (if it is
     a package).  The argument can be a list of names separated by a
     comma.

 -- Option: --ignore-dir=<dir>

     Ignore all modules and packages in the named directory and
     subdirectories.  The argument can be a list of directories
     separated by *note os.pathsep: 1c46.


File: python.info,  Node: Programmatic Interface,  Prev: Command-Line Usage,  Up: trace --- 追蹤或追查 Python 陳述式執行

5.27.7.5 Programmatic Interface
...............................

 -- 類別: trace.Trace (count=1, trace=1, countfuncs=0, countcallers=0,
          ignoremods=(), ignoredirs=(), infile=None, outfile=None,
          timing=False)

     Create an object to trace execution of a single statement or
     expression.  All parameters are optional.  'count' enables counting
     of line numbers.  'trace' enables line execution tracing.
     'countfuncs' enables listing of the functions called during the
     run.  'countcallers' enables call relationship tracking.
     'ignoremods' is a list of modules or packages to ignore.
     'ignoredirs' is a list of directories whose modules or packages
     should be ignored.  'infile' is the name of the file from which to
     read stored count information.  'outfile' is the name of the file
     in which to write updated count information.  'timing' enables a
     timestamp relative to when tracing was started to be displayed.

      -- 方法: run (cmd)

          Execute the command and gather statistics from the execution
          with the current tracing parameters.  'cmd' must be a string
          or code object, suitable for passing into *note exec(): 162.

      -- 方法: runctx (cmd, globals=None, locals=None)

          Execute the command and gather statistics from the execution
          with the current tracing parameters, in the defined global and
          local environments.  If not defined, 'globals' and 'locals'
          default to empty dictionaries.

      -- 方法: runfunc (func, /, *args, **kwds)

          Call 'func' with the given arguments under control of the
          *note Trace: 40eb. object with the current tracing parameters.

      -- 方法: results ()

          Return a *note CoverageResults: 40ef. object that contains the
          cumulative results of all previous calls to ‘run’, ‘runctx’
          and ‘runfunc’ for the given *note Trace: 40eb. instance.  Does
          not reset the accumulated trace results.

 -- 類別: trace.CoverageResults

     A container for coverage results, created by *note Trace.results():
     40ee.  Should not be created directly by the user.

      -- 方法: update (other)

          Merge in data from another *note CoverageResults: 40ef.
          object.

      -- 方法: write_results (show_missing=True, summary=False,
               coverdir=None, *, ignore_missing_files=False)

          Write coverage results.  Set 'show_missing' to show lines that
          had no hits.  Set 'summary' to include in the output the
          coverage summary per module.  'coverdir' specifies the
          directory into which the coverage result files will be output.
          If ‘None’, the results for each source file are placed in its
          directory.

          If 'ignore_missing_files' is ‘True’, coverage counts for files
          that no longer exist are silently ignored.  Otherwise, a
          missing file will raise a *note FileNotFoundError: e67.

          在 3.13 版的變更: Added 'ignore_missing_files' parameter.

A simple example demonstrating the use of the programmatic interface:

     import sys
     import trace

     # create a Trace object, telling it what to ignore, and whether to
     # do tracing or line-counting or both.
     tracer = trace.Trace(
         ignoredirs=[sys.prefix, sys.exec_prefix],
         trace=0,
         count=1)

     # run the new command using the given tracer
     tracer.run('main()')

     # make a report, placing output in the current directory
     r = tracer.results()
     r.write_results(show_missing=True, coverdir=".")


File: python.info,  Node: tracemalloc --- 追蹤記憶體配置,  Prev: trace --- 追蹤或追查 Python 陳述式執行,  Up: 除錯與效能分析

5.27.8 ‘tracemalloc’ -- 追蹤記憶體配置
--------------------------------------

在 3.4 版被加入.

'原始碼：'Lib/tracemalloc.py(1)

__________________________________________________________________

The tracemalloc module is a debug tool to trace memory blocks allocated
by Python.  It provides the following information:

   * Traceback where an object was allocated

   * Statistics on allocated memory blocks per filename and per line
     number: total size, number and average size of allocated memory
     blocks

   * Compute the differences between two snapshots to detect memory
     leaks

To trace most memory blocks allocated by Python, the module should be
started as early as possible by setting the *note PYTHONTRACEMALLOC:
1c3e. environment variable to ‘1’, or by using *note -X: 15a.
‘tracemalloc’ command line option.  The *note tracemalloc.start(): 1c3d.
function can be called at runtime to start tracing Python memory
allocations.

By default, a trace of an allocated memory block only stores the most
recent frame (1 frame).  To store 25 frames at startup: set the *note
PYTHONTRACEMALLOC: 1c3e. environment variable to ‘25’, or use the *note
-X: 15a. ‘tracemalloc=25’ command line option.

* Menu:

* 範例: 範例<43>.
* API::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/tracemalloc.py


File: python.info,  Node: 範例<43>,  Next: API,  Up: tracemalloc --- 追蹤記憶體配置

5.27.8.1 範例
.............

* Menu:

* Display the top 10::
* Compute differences::
* Get the traceback of a memory block::
* Pretty top::


File: python.info,  Node: Display the top 10,  Next: Compute differences,  Up: 範例<43>

5.27.8.2 Display the top 10
...........................

Display the 10 files allocating the most memory:

     import tracemalloc

     tracemalloc.start()

     # ... run your application ...

     snapshot = tracemalloc.take_snapshot()
     top_stats = snapshot.statistics('lineno')

     print("[ Top 10 ]")
     for stat in top_stats[:10]:
         print(stat)

Example of output of the Python test suite:

     [ Top 10 ]
     <frozen importlib._bootstrap>:716: size=4855 KiB, count=39328, average=126 B
     <frozen importlib._bootstrap>:284: size=521 KiB, count=3199, average=167 B
     /usr/lib/python3.4/collections/__init__.py:368: size=244 KiB, count=2315, average=108 B
     /usr/lib/python3.4/unittest/case.py:381: size=185 KiB, count=779, average=243 B
     /usr/lib/python3.4/unittest/case.py:402: size=154 KiB, count=378, average=416 B
     /usr/lib/python3.4/abc.py:133: size=88.7 KiB, count=347, average=262 B
     <frozen importlib._bootstrap>:1446: size=70.4 KiB, count=911, average=79 B
     <frozen importlib._bootstrap>:1454: size=52.0 KiB, count=25, average=2131 B
     <string>:5: size=49.7 KiB, count=148, average=344 B
     /usr/lib/python3.4/sysconfig.py:411: size=48.0 KiB, count=1, average=48.0 KiB

We can see that Python loaded ‘4855 KiB’ data (bytecode and constants)
from modules and that the *note collections: 16. module allocated ‘244
KiB’ to build *note namedtuple: 1ae. types.

更多選項請見 *note Snapshot.statistics(): 40f6.。


File: python.info,  Node: Compute differences,  Next: Get the traceback of a memory block,  Prev: Display the top 10,  Up: 範例<43>

5.27.8.3 Compute differences
............................

Take two snapshots and display the differences:

     import tracemalloc
     tracemalloc.start()
     # ... start your application ...

     snapshot1 = tracemalloc.take_snapshot()
     # ... call the function leaking memory ...
     snapshot2 = tracemalloc.take_snapshot()

     top_stats = snapshot2.compare_to(snapshot1, 'lineno')

     print("[ Top 10 differences ]")
     for stat in top_stats[:10]:
         print(stat)

Example of output before/after running some tests of the Python test
suite:

     [ Top 10 differences ]
     <frozen importlib._bootstrap>:716: size=8173 KiB (+4428 KiB), count=71332 (+39369), average=117 B
     /usr/lib/python3.4/linecache.py:127: size=940 KiB (+940 KiB), count=8106 (+8106), average=119 B
     /usr/lib/python3.4/unittest/case.py:571: size=298 KiB (+298 KiB), count=589 (+589), average=519 B
     <frozen importlib._bootstrap>:284: size=1005 KiB (+166 KiB), count=7423 (+1526), average=139 B
     /usr/lib/python3.4/mimetypes.py:217: size=112 KiB (+112 KiB), count=1334 (+1334), average=86 B
     /usr/lib/python3.4/http/server.py:848: size=96.0 KiB (+96.0 KiB), count=1 (+1), average=96.0 KiB
     /usr/lib/python3.4/inspect.py:1465: size=83.5 KiB (+83.5 KiB), count=109 (+109), average=784 B
     /usr/lib/python3.4/unittest/mock.py:491: size=77.7 KiB (+77.7 KiB), count=143 (+143), average=557 B
     /usr/lib/python3.4/urllib/parse.py:476: size=71.8 KiB (+71.8 KiB), count=969 (+969), average=76 B
     /usr/lib/python3.4/contextlib.py:38: size=67.2 KiB (+67.2 KiB), count=126 (+126), average=546 B

We can see that Python has loaded ‘8173 KiB’ of module data (bytecode
and constants), and that this is ‘4428 KiB’ more than had been loaded
before the tests, when the previous snapshot was taken.  Similarly, the
*note linecache: 79. module has cached ‘940 KiB’ of Python source code
to format tracebacks, all of it since the previous snapshot.

If the system has little free memory, snapshots can be written on disk
using the *note Snapshot.dump(): 40f8. method to analyze the snapshot
offline.  Then use the *note Snapshot.load(): 40f9. method reload the
snapshot.


File: python.info,  Node: Get the traceback of a memory block,  Next: Pretty top,  Prev: Compute differences,  Up: 範例<43>

5.27.8.4 Get the traceback of a memory block
............................................

Code to display the traceback of the biggest memory block:

     import tracemalloc

     # Store 25 frames
     tracemalloc.start(25)

     # ... run your application ...

     snapshot = tracemalloc.take_snapshot()
     top_stats = snapshot.statistics('traceback')

     # pick the biggest memory block
     stat = top_stats[0]
     print("%s memory blocks: %.1f KiB" % (stat.count, stat.size / 1024))
     for line in stat.traceback.format():
         print(line)

Example of output of the Python test suite (traceback limited to 25
frames):

     903 memory blocks: 870.1 KiB
       File "<frozen importlib._bootstrap>", line 716
       File "<frozen importlib._bootstrap>", line 1036
       File "<frozen importlib._bootstrap>", line 934
       File "<frozen importlib._bootstrap>", line 1068
       File "<frozen importlib._bootstrap>", line 619
       File "<frozen importlib._bootstrap>", line 1581
       File "<frozen importlib._bootstrap>", line 1614
       File "/usr/lib/python3.4/doctest.py", line 101
         import pdb
       File "<frozen importlib._bootstrap>", line 284
       File "<frozen importlib._bootstrap>", line 938
       File "<frozen importlib._bootstrap>", line 1068
       File "<frozen importlib._bootstrap>", line 619
       File "<frozen importlib._bootstrap>", line 1581
       File "<frozen importlib._bootstrap>", line 1614
       File "/usr/lib/python3.4/test/support/__init__.py", line 1728
         import doctest
       File "/usr/lib/python3.4/test/test_pickletools.py", line 21
         support.run_doctest(pickletools)
       File "/usr/lib/python3.4/test/regrtest.py", line 1276
         test_runner()
       File "/usr/lib/python3.4/test/regrtest.py", line 976
         display_failure=not verbose)
       File "/usr/lib/python3.4/test/regrtest.py", line 761
         match_tests=ns.match_tests)
       File "/usr/lib/python3.4/test/regrtest.py", line 1563
         main()
       File "/usr/lib/python3.4/test/__main__.py", line 3
         regrtest.main_in_temp_cwd()
       File "/usr/lib/python3.4/runpy.py", line 73
         exec(code, run_globals)
       File "/usr/lib/python3.4/runpy.py", line 160
         "__main__", fname, loader, pkg_name)

We can see that the most memory was allocated in the *note importlib:
6b. module to load data (bytecode and constants) from modules: ‘870.1
KiB’.  The traceback is where the *note importlib: 6b. loaded data most
recently: on the ‘import pdb’ line of the *note doctest: 31. module.
The traceback may change if a new module is loaded.


File: python.info,  Node: Pretty top,  Prev: Get the traceback of a memory block,  Up: 範例<43>

5.27.8.5 Pretty top
...................

Code to display the 10 lines allocating the most memory with a pretty
output, ignoring ‘<frozen importlib._bootstrap>’ and ‘<unknown>’ files:

     import linecache
     import os
     import tracemalloc

     def display_top(snapshot, key_type='lineno', limit=10):
         snapshot = snapshot.filter_traces((
             tracemalloc.Filter(False, "<frozen importlib._bootstrap>"),
             tracemalloc.Filter(False, "<unknown>"),
         ))
         top_stats = snapshot.statistics(key_type)

         print("Top %s lines" % limit)
         for index, stat in enumerate(top_stats[:limit], 1):
             frame = stat.traceback[0]
             print("#%s: %s:%s: %.1f KiB"
                   % (index, frame.filename, frame.lineno, stat.size / 1024))
             line = linecache.getline(frame.filename, frame.lineno).strip()
             if line:
                 print('    %s' % line)

         other = top_stats[limit:]
         if other:
             size = sum(stat.size for stat in other)
             print("%s other: %.1f KiB" % (len(other), size / 1024))
         total = sum(stat.size for stat in top_stats)
         print("Total allocated size: %.1f KiB" % (total / 1024))

     tracemalloc.start()

     # ... run your application ...

     snapshot = tracemalloc.take_snapshot()
     display_top(snapshot)

Example of output of the Python test suite:

     Top 10 lines
     #1: Lib/base64.py:414: 419.8 KiB
         _b85chars2 = [(a + b) for a in _b85chars for b in _b85chars]
     #2: Lib/base64.py:306: 419.8 KiB
         _a85chars2 = [(a + b) for a in _a85chars for b in _a85chars]
     #3: collections/__init__.py:368: 293.6 KiB
         exec(class_definition, namespace)
     #4: Lib/abc.py:133: 115.2 KiB
         cls = super().__new__(mcls, name, bases, namespace)
     #5: unittest/case.py:574: 103.1 KiB
         testMethod()
     #6: Lib/linecache.py:127: 95.4 KiB
         lines = fp.readlines()
     #7: urllib/parse.py:476: 71.8 KiB
         for a in _hexdig for b in _hexdig}
     #8: <string>:5: 62.0 KiB
     #9: Lib/_weakrefset.py:37: 60.0 KiB
         self.data = set()
     #10: Lib/base64.py:142: 59.8 KiB
         _b32tab2 = [a + b for a in _b32tab for b in _b32tab]
     6220 other: 3602.8 KiB
     Total allocated size: 5303.1 KiB

更多選項請見 *note Snapshot.statistics(): 40f6.。

* Menu:

* Record the current and peak size of all traced memory blocks::


File: python.info,  Node: Record the current and peak size of all traced memory blocks,  Up: Pretty top

5.27.8.6 Record the current and peak size of all traced memory blocks
.....................................................................

The following code computes two sums like ‘0 + 1 + 2 + ...’
inefficiently, by creating a list of those numbers.  This list consumes
a lot of memory temporarily.  We can use *note get_traced_memory():
40fd. and *note reset_peak(): 8df. to observe the small memory usage
after the sum is computed as well as the peak memory usage during the
computations:

     import tracemalloc

     tracemalloc.start()

     # Example code: compute a sum with a large temporary list
     large_sum = sum(list(range(100000)))

     first_size, first_peak = tracemalloc.get_traced_memory()

     tracemalloc.reset_peak()

     # Example code: compute a sum with a small temporary list
     small_sum = sum(list(range(1000)))

     second_size, second_peak = tracemalloc.get_traced_memory()

     print(f"{first_size=}, {first_peak=}")
     print(f"{second_size=}, {second_peak=}")

輸出：

     first_size=664, first_peak=3592984
     second_size=804, second_peak=29704

Using *note reset_peak(): 8df. ensured we could accurately record the
peak during the computation of ‘small_sum’, even though it is much
smaller than the overall peak size of memory blocks since the *note
start(): 1c3d. call.  Without the call to *note reset_peak(): 8df,
‘second_peak’ would still be the peak from the computation ‘large_sum’
(that is, equal to ‘first_peak’).  In this case, both peaks are much
higher than the final memory usage, and which suggests we could optimise
(by removing the unnecessary call to *note list: 5b6, and writing
‘sum(range(...))’).


File: python.info,  Node: API,  Prev: 範例<43>,  Up: tracemalloc --- 追蹤記憶體配置

5.27.8.7 API
............

* Menu:

* 函式: 函式<10>.
* DomainFilter::
* Filter::
* Frame::
* Snapshot::
* Statistic::
* StatisticDiff::
* Trace::
* Traceback::


File: python.info,  Node: 函式<10>,  Next: DomainFilter,  Up: API

5.27.8.8 函式
.............

 -- 函式: tracemalloc.clear_traces ()

     Clear traces of memory blocks allocated by Python.

     另請參閱 *note stop(): 4101.。

 -- 函式: tracemalloc.get_object_traceback (obj)

     Get the traceback where the Python object 'obj' was allocated.
     Return a *note Traceback: b3d. instance, or ‘None’ if the *note
     tracemalloc: e8. module is not tracing memory allocations or did
     not trace the allocation of the object.

     另請參閱 *note gc.get_referrers(): 7a8. 與 *note sys.getsizeof():
     166c. 函式。

 -- 函式: tracemalloc.get_traceback_limit ()

     Get the maximum number of frames stored in the traceback of a
     trace.

     The *note tracemalloc: e8. module must be tracing memory
     allocations to get the limit, otherwise an exception is raised.

     The limit is set by the *note start(): 1c3d. function.

 -- 函式: tracemalloc.get_traced_memory ()

     Get the current size and peak size of memory blocks traced by the
     *note tracemalloc: e8. module as a tuple: ‘(current: int, peak:
     int)’.

 -- 函式: tracemalloc.reset_peak ()

     Set the peak size of memory blocks traced by the *note tracemalloc:
     e8. module to the current size.

     Do nothing if the *note tracemalloc: e8. module is not tracing
     memory allocations.

     This function only modifies the recorded peak size, and does not
     modify or clear any traces, unlike *note clear_traces(): 4100.
     Snapshots taken with *note take_snapshot(): 4103. before a call to
     *note reset_peak(): 8df. can be meaningfully compared to snapshots
     taken after the call.

     另請參閱 *note get_traced_memory(): 40fd.。

     在 3.9 版被加入.

 -- 函式: tracemalloc.get_tracemalloc_memory ()

     Get the memory usage in bytes of the *note tracemalloc: e8. module
     used to store traces of memory blocks.  Return an *note int: 23c.

 -- 函式: tracemalloc.is_tracing ()

     ‘True’ if the *note tracemalloc: e8. module is tracing Python
     memory allocations, ‘False’ otherwise.

     另請參閱 *note start(): 1c3d. 與 *note stop(): 4101. 函式。

 -- 函式: tracemalloc.start (nframe: int = 1)

     Start tracing Python memory allocations: install hooks on Python
     memory allocators.  Collected tracebacks of traces will be limited
     to 'nframe' frames.  By default, a trace of a memory block only
     stores the most recent frame: the limit is ‘1’.  'nframe' must be
     greater or equal to ‘1’.

     You can still read the original number of total frames that
     composed the traceback by looking at the *note
     Traceback.total_nframe: 4106. attribute.

     Storing more than ‘1’ frame is only useful to compute statistics
     grouped by ‘'traceback'’ or to compute cumulative statistics: see
     the *note Snapshot.compare_to(): 4107. and *note
     Snapshot.statistics(): 40f6. methods.

     Storing more frames increases the memory and CPU overhead of the
     *note tracemalloc: e8. module.  Use the *note
     get_tracemalloc_memory(): 4104. function to measure how much memory
     is used by the *note tracemalloc: e8. module.

     The *note PYTHONTRACEMALLOC: 1c3e. environment variable
     (‘PYTHONTRACEMALLOC=NFRAME’) and the *note -X: 15a.
     ‘tracemalloc=NFRAME’ command line option can be used to start
     tracing at startup.

     See also *note stop(): 4101, *note is_tracing(): 4105. and *note
     get_traceback_limit(): 4102. functions.

 -- 函式: tracemalloc.stop ()

     Stop tracing Python memory allocations: uninstall hooks on Python
     memory allocators.  Also clears all previously collected traces of
     memory blocks allocated by Python.

     Call *note take_snapshot(): 4103. function to take a snapshot of
     traces before clearing them.

     See also *note start(): 1c3d, *note is_tracing(): 4105. and *note
     clear_traces(): 4100. functions.

 -- 函式: tracemalloc.take_snapshot ()

     Take a snapshot of traces of memory blocks allocated by Python.
     Return a new *note Snapshot: 4108. instance.

     The snapshot does not include memory blocks allocated before the
     *note tracemalloc: e8. module started to trace memory allocations.

     Tracebacks of traces are limited to *note get_traceback_limit():
     4102. frames.  Use the 'nframe' parameter of the *note start():
     1c3d. function to store more frames.

     The *note tracemalloc: e8. module must be tracing memory
     allocations to take a snapshot, see the *note start(): 1c3d.
     function.

     另請參閱 *note get_object_traceback(): 1a5e. 函式。


File: python.info,  Node: DomainFilter,  Next: Filter,  Prev: 函式<10>,  Up: API

5.27.8.9 DomainFilter
.....................

 -- 類別: tracemalloc.DomainFilter (inclusive: bool, domain: int)

     Filter traces of memory blocks by their address space (domain).

     在 3.6 版被加入.

      -- 屬性: inclusive

          If 'inclusive' is ‘True’ (include), match memory blocks
          allocated in the address space *note domain: 410b.

          If 'inclusive' is ‘False’ (exclude), match memory blocks not
          allocated in the address space *note domain: 410b.

      -- 屬性: domain

          Address space of a memory block (‘int’).  Read-only property.


File: python.info,  Node: Filter,  Next: Frame,  Prev: DomainFilter,  Up: API

5.27.8.10 Filter
................

 -- 類別: tracemalloc.Filter (inclusive: bool, filename_pattern: str,
          lineno: int = None, all_frames: bool = False, domain: int =
          None)

     Filter on traces of memory blocks.

     See the *note fnmatch.fnmatch(): 17a2. function for the syntax of
     'filename_pattern'.  The ‘'.pyc'’ file extension is replaced with
     ‘'.py'’.

     範例：

        * ‘Filter(True, subprocess.__file__)’ only includes traces of
          the *note subprocess: c1. module

        * ‘Filter(False, tracemalloc.__file__)’ excludes traces of the
          *note tracemalloc: e8. module

        * ‘Filter(False, "<unknown>")’ excludes empty tracebacks

     在 3.5 版的變更: The ‘'.pyo'’ file extension is no longer replaced
     with ‘'.py'’.

     在 3.6 版的變更: 新增 *note domain: 410e. 屬性。

      -- 屬性: domain

          Address space of a memory block (‘int’ or ‘None’).

          tracemalloc uses the domain ‘0’ to trace memory allocations
          made by Python.  C extensions can use other domains to trace
          other resources.

      -- 屬性: inclusive

          If 'inclusive' is ‘True’ (include), only match memory blocks
          allocated in a file with a name matching *note
          filename_pattern: 4110. at line number *note lineno: 4111.

          If 'inclusive' is ‘False’ (exclude), ignore memory blocks
          allocated in a file with a name matching *note
          filename_pattern: 4110. at line number *note lineno: 4111.

      -- 屬性: lineno

          Line number (‘int’) of the filter.  If 'lineno' is ‘None’, the
          filter matches any line number.

      -- 屬性: filename_pattern

          Filename pattern of the filter (‘str’).  Read-only property.

      -- 屬性: all_frames

          If 'all_frames' is ‘True’, all frames of the traceback are
          checked.  If 'all_frames' is ‘False’, only the most recent
          frame is checked.

          This attribute has no effect if the traceback limit is ‘1’.
          See the *note get_traceback_limit(): 4102. function and *note
          Snapshot.traceback_limit: 4113. attribute.


File: python.info,  Node: Frame,  Next: Snapshot,  Prev: Filter,  Up: API

5.27.8.11 Frame
...............

 -- 類別: tracemalloc.Frame

     Frame of a traceback.

     The *note Traceback: b3d. class is a sequence of *note Frame: 4115.
     instances.

      -- 屬性: filename

          Filename (‘str’).

      -- 屬性: lineno

          Line number (‘int’).


File: python.info,  Node: Snapshot,  Next: Statistic,  Prev: Frame,  Up: API

5.27.8.12 Snapshot
..................

 -- 類別: tracemalloc.Snapshot

     Snapshot of traces of memory blocks allocated by Python.

     The *note take_snapshot(): 4103. function creates a snapshot
     instance.

      -- 方法: compare_to (old_snapshot: Snapshot, key_type: str,
               cumulative: bool = False)

          Compute the differences with an old snapshot.  Get statistics
          as a sorted list of *note StatisticDiff: 4119. instances
          grouped by 'key_type'.

          See the *note Snapshot.statistics(): 40f6. method for
          'key_type' and 'cumulative' parameters.

          The result is sorted from the biggest to the smallest by:
          absolute value of *note StatisticDiff.size_diff: 411a, *note
          StatisticDiff.size: 411b, absolute value of *note
          StatisticDiff.count_diff: 411c, *note Statistic.count: 411d.
          and then by *note StatisticDiff.traceback: 411e.

      -- 方法: dump (filename)

          Write the snapshot into a file.

          Use *note load(): 40f9. to reload the snapshot.

      -- 方法: filter_traces (filters)

          Create a new *note Snapshot: 4108. instance with a filtered
          *note traces: 4120. sequence, 'filters' is a list of *note
          DomainFilter: c98. and *note Filter: 410d. instances.  If
          'filters' is an empty list, return a new *note Snapshot: 4108.
          instance with a copy of the traces.

          All inclusive filters are applied at once, a trace is ignored
          if no inclusive filters match it.  A trace is ignored if at
          least one exclusive filter matches it.

          在 3.6 版的變更: *note DomainFilter: c98. instances are now
          also accepted in 'filters'.

      -- 方法: classmethod load (filename)

          Load a snapshot from a file.

          另請參閱 *note dump(): 40f8.。

      -- 方法: statistics (key_type: str, cumulative: bool = False)

          Get statistics as a sorted list of *note Statistic: 4121.
          instances grouped by 'key_type':

          key_type                  描述
                                    
          -------------------------------------------------------
                                    
          ‘'filename'’              filename
                                    
                                    
          ‘'lineno'’                filename and line number
                                    
                                    
          ‘'traceback'’             traceback
                                    

          If 'cumulative' is ‘True’, cumulate size and count of memory
          blocks of all frames of the traceback of a trace, not only the
          most recent frame.  The cumulative mode can only be used with
          'key_type' equals to ‘'filename'’ and ‘'lineno'’.

          The result is sorted from the biggest to the smallest by:
          *note Statistic.size: 4122, *note Statistic.count: 411d. and
          then by *note Statistic.traceback: 4123.

      -- 屬性: traceback_limit

          Maximum number of frames stored in the traceback of *note
          traces: 4120.: result of the *note get_traceback_limit():
          4102. when the snapshot was taken.

      -- 屬性: traces

          Traces of all memory blocks allocated by Python: sequence of
          *note Trace: 4124. instances.

          The sequence has an undefined order.  Use the *note
          Snapshot.statistics(): 40f6. method to get a sorted list of
          statistics.


File: python.info,  Node: Statistic,  Next: StatisticDiff,  Prev: Snapshot,  Up: API

5.27.8.13 Statistic
...................

 -- 類別: tracemalloc.Statistic

     Statistic on memory allocations.

     *note Snapshot.statistics(): 40f6. returns a list of *note
     Statistic: 4121. instances.

     See also the *note StatisticDiff: 4119. class.

      -- 屬性: count

          Number of memory blocks (‘int’).

      -- 屬性: size

          Total size of memory blocks in bytes (‘int’).

      -- 屬性: traceback

          Traceback where the memory block was allocated, *note
          Traceback: b3d. instance.


File: python.info,  Node: StatisticDiff,  Next: Trace,  Prev: Statistic,  Up: API

5.27.8.14 StatisticDiff
.......................

 -- 類別: tracemalloc.StatisticDiff

     Statistic difference on memory allocations between an old and a new
     *note Snapshot: 4108. instance.

     *note Snapshot.compare_to(): 4107. returns a list of *note
     StatisticDiff: 4119. instances.  See also the *note Statistic:
     4121. class.

      -- 屬性: count

          Number of memory blocks in the new snapshot (‘int’): ‘0’ if
          the memory blocks have been released in the new snapshot.

      -- 屬性: count_diff

          Difference of number of memory blocks between the old and the
          new snapshots (‘int’): ‘0’ if the memory blocks have been
          allocated in the new snapshot.

      -- 屬性: size

          Total size of memory blocks in bytes in the new snapshot
          (‘int’): ‘0’ if the memory blocks have been released in the
          new snapshot.

      -- 屬性: size_diff

          Difference of total size of memory blocks in bytes between the
          old and the new snapshots (‘int’): ‘0’ if the memory blocks
          have been allocated in the new snapshot.

      -- 屬性: traceback

          Traceback where the memory blocks were allocated, *note
          Traceback: b3d. instance.


File: python.info,  Node: Trace,  Next: Traceback,  Prev: StatisticDiff,  Up: API

5.27.8.15 Trace
...............

 -- 類別: tracemalloc.Trace

     Trace of a memory block.

     The *note Snapshot.traces: 4120. attribute is a sequence of *note
     Trace: 4124. instances.

     在 3.6 版的變更: 新增 *note domain: 4129. 屬性。

      -- 屬性: domain

          Address space of a memory block (‘int’).  Read-only property.

          tracemalloc uses the domain ‘0’ to trace memory allocations
          made by Python.  C extensions can use other domains to trace
          other resources.

      -- 屬性: size

          Size of the memory block in bytes (‘int’).

      -- 屬性: traceback

          Traceback where the memory block was allocated, *note
          Traceback: b3d. instance.


File: python.info,  Node: Traceback,  Prev: Trace,  Up: API

5.27.8.16 Traceback
...................

 -- 類別: tracemalloc.Traceback

     Sequence of *note Frame: 4115. instances sorted from the oldest
     frame to the most recent frame.

     A traceback contains at least ‘1’ frame.  If the ‘tracemalloc’
     module failed to get a frame, the filename ‘"<unknown>"’ at line
     number ‘0’ is used.

     When a snapshot is taken, tracebacks of traces are limited to *note
     get_traceback_limit(): 4102. frames.  See the *note
     take_snapshot(): 4103. function.  The original number of frames of
     the traceback is stored in the *note Traceback.total_nframe: 4106.
     attribute.  That allows to know if a traceback has been truncated
     by the traceback limit.

     The *note Trace.traceback: 412b. attribute is an instance of *note
     Traceback: b3d. instance.

     在 3.7 版的變更: Frames are now sorted from the oldest to the most
     recent, instead of most recent to oldest.

      -- 屬性: total_nframe

          Total number of frames that composed the traceback before
          truncation.  This attribute can be set to ‘None’ if the
          information is not available.

     在 3.9 版的變更: The *note Traceback.total_nframe: 4106. attribute
     was added.

      -- 方法: format (limit=None, most_recent_first=False)

          Format the traceback as a list of lines.  Use the *note
          linecache: 79. module to retrieve lines from the source code.
          If 'limit' is set, format the 'limit' most recent frames if
          'limit' is positive.  Otherwise, format the ‘abs(limit)’
          oldest frames.  If 'most_recent_first' is ‘True’, the order of
          the formatted frames is reversed, returning the most recent
          frame first instead of last.

          Similar to the *note traceback.format_tb(): 412d. function,
          except that *note format(): b3e. does not include newlines.

          範例：

               print("Traceback (most recent call first):")
               for line in traceback:
                   print(line)

          輸出：

               Traceback (most recent call first):
                 File "test.py", line 9
                   obj = Object()
                 File "test.py", line 12
                   tb = tracemalloc.get_object_traceback(f())


File: python.info,  Node: 軟體封裝與發布,  Next: Python Runtime 服務,  Prev: 除錯與效能分析,  Up: Python 標準函式庫 Standard Library

5.28 軟體封裝與發布
===================

These libraries help you with publishing and installing Python software.
While these modules are designed to work in conjunction with the Python
Package Index(1), they can also be used with a local index server, or
without any index server at all.

* Menu:

* ensurepip: ensurepip --- pip 安裝器的初始建置 bootstrapping. pip 安裝器的初始建置 (bootstrapping)
* venv: venv --- 建立虛擬環境. 建立虛擬環境
* zipapp —-- 管理可執行的 Python zip 封存檔案::

   ---------- Footnotes ----------

   (1) https://pypi.org


File: python.info,  Node: ensurepip --- pip 安裝器的初始建置 bootstrapping,  Next: venv --- 建立虛擬環境,  Up: 軟體封裝與發布

5.28.1 ‘ensurepip’ -- ‘pip’ 安裝器的初始建置 (bootstrapping)
------------------------------------------------------------

在 3.4 版被加入.

'原始碼：'Lib/ensurepip(1)

__________________________________________________________________

*note ensurepip: 4b. 套件 (package) 為既有的 Python 安裝或虛擬環境提供
‘pip’ 安裝器初始建置 (bootstrapping) 的支援。這個初始建置的方式應證了事
實 —— ‘pip’ 是有其獨立發布週期的專案，且其最新可用穩定的版本，會與
CPython 直譯器 (interpreter) 之維護和功能發布綁定。

大多數情況下，Python 的終端使用者不需要直接調用此模組（因為 ‘pip’ 預設應
為初始建置），但若安裝 Python 時 ‘pip’ 被省略（或建立一虛擬環境時），又
或是 ‘pip’ 被明確解除安裝時，則此模組的初始建置仍有可能用上。

     備註: 此模組'不會'通過網路存取。所有需要用來初始建置 ‘pip’ 的元件都
     已包含在套件之內。

也參考
......

*note 安裝 Python 模組: e99.

     對於終端使用者安裝 Python 套件的指引

PEP 453(2): 在 Python 安裝中的 pip 明確初始建置

     此模組的最初設計理念與規範。

*note Availability: 1c56.: not WASI, not iOS.

This module does not work or is not available on WebAssembly platforms,
or on iOS. See *note WebAssembly 平台: 16e6. for more information on
WASM availability; see *note iOS: 1d56. for more information on iOS
availability.

* Menu:

* 命令列介面: 命令列介面<5>.
* 模組 API::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/ensurepip

   (2) https://peps.python.org/pep-0453/


File: python.info,  Node: 命令列介面<5>,  Next: 模組 API,  Up: ensurepip --- pip 安裝器的初始建置 bootstrapping

5.28.1.1 命令列介面
...................

使用直譯器 (interpreter) 的 ‘-m’ 來調用命令列介面

最簡單可行的調用：

     python -m ensurepip

若 ‘pip’ 未安裝，此調用會將其安裝；否則甚麼也不做。可透過傳入
‘--upgrade’ 參數來確保 ‘pip’ 的安裝版本至少為當前 ‘ensurepip’ 中最新可用
的版本：

     python -m ensurepip --upgrade

預設上，‘pip’ 會被安裝至當前虛擬環境（若已啟動虛擬環境）或系統端的套件（
若沒有啟動的虛擬環境）。安裝位置可透過兩個額外的命令列選項來控制：

   * ‘--root <dir>’：安裝 ‘pip’ 到給定的根目錄 (root directory) 的相對路
     徑，而不是當前虛擬環境（若存在）的根目錄，或當前 Python 安裝版所預
     設的根目錄。

   * ‘--user’ ：安裝 ‘pip’ 到使用者端的套件目錄，而不是全域安裝到當前的
     Python 安裝版（此選項不允許在一啟動的虛擬環境中使用）。

預設會安裝 ‘pipX’ 和 ‘pipX.Y’ 腳本（X.Y 代表用來調用 ‘ensurepip’ 的
Python 之版本）。安裝的腳本可透過兩個額外的命令列選項來控制：

   * ‘--altinstall’：若要求一個替代安裝版，則'不會'安裝 ‘pipX’ 腳本。

   * ‘--default-pip’： 若要求安裝「預設 pip」，則會安裝 ‘pip’ 腳本，及 2
     個常規腳本。

提供兩種指令選項將會導致例外 (exception) 。


File: python.info,  Node: 模組 API,  Prev: 命令列介面<5>,  Up: ensurepip --- pip 安裝器的初始建置 bootstrapping

5.28.1.2 模組 API
.................

*note ensurepip: 4b. 開放了兩個用於編寫程式的函式：

 -- 函式: ensurepip.version ()

     回傳一個字串，用以標明初始建置時，安裝的 pip 的可行版本號。

 -- 函式: ensurepip.bootstrap (root=None, upgrade=False, user=False,
          altinstall=False, default_pip=False, verbosity=0)

     在當前或指定的環境之中建立 ‘pip’。

     'root' 指定一個替代的根目錄，作為安裝的相對路徑。若 'root' 為
     ‘None’，則安裝使用當前環境的預設安裝位置。

     'upgrade' 指出是否要將一個既有的較早版本的 ‘pip’ 升級至可用的新版。

     'user' 指出是否要使用使用者的安裝方案而不是全域安裝。

     預設會安裝 ‘pipX’ 和 ‘pipX.Y’ 腳本（X.Y 代表 Python 的當前版本）。

     如果啟用了 'altinstall'，則不會安裝 ‘pipX’。

     如果啟用了 'default_pip'，則會安裝 ‘pip’，以及 2 個常規腳本。

     同時啟用 'altinstall' 跟 'default_pip'，將會觸發 *note ValueError:
     1e7.。

     'verbosity' 用來控制初始建置操作內，對於 *note sys.stdout: a79. 的
     輸出等級。

     引發一個附帶引數 ‘root’ 的*note 稽核事件: 17bd.
     ‘ensurepip.bootstrap’。

          備註: 初始建置的過程對於 ‘sys.path’ 及 ‘os.environ’ 均有副作用
          。改為在一子行程 (subprocess) 調用命令列介面可避免這些副作用。

          備註: 初始建置的過程也許會安裝 ‘pip’ 所需要的額外的模組，但其
          他軟體不應該假設這些相依 (dependency) 總是預設存在（因為這些相
          依很可能會在未來版本的 ‘pip’ 中被移除）。


File: python.info,  Node: venv --- 建立虛擬環境,  Next: zipapp —-- 管理可執行的 Python zip 封存檔案,  Prev: ensurepip --- pip 安裝器的初始建置 bootstrapping,  Up: 軟體封裝與發布

5.28.2 ‘venv’ -- 建立虛擬環境
-----------------------------

在 3.3 版被加入.

'原始碼：'Lib/venv/(1)

__________________________________________________________________

The ‘venv’ module supports creating lightweight "virtual environments",
each with their own independent set of Python packages installed in
their *note site: b5. directories.  A virtual environment is created on
top of an existing Python installation, known as the virtual
environment's "base" Python, and may optionally be isolated from the
packages in the base environment, so only those explicitly installed in
the virtual environment are available.

When used from within a virtual environment, common installation tools
such as pip(2) will install Python packages into a virtual environment
without needing to be told to do so explicitly.

A virtual environment is (amongst other things):

   * Used to contain a specific Python interpreter and software
     libraries and binaries which are needed to support a project
     (library or application).  These are by default isolated from
     software in other virtual environments and Python interpreters and
     libraries installed in the operating system.

   * Contained in a directory, conventionally either named ‘venv’ or
     ‘.venv’ in the project directory, or under a container directory
     for lots of virtual environments, such as ‘~/.virtualenvs’.

   * Not checked into source control systems such as Git.

   * Considered as disposable - it should be simple to delete and
     recreate it from scratch.  You don't place any project code in the
     environment

   * Not considered as movable or copyable - you just recreate the same
     environment in the target location.

更多關於 Python 虛擬環境的背景資訊請見 PEP 405(3)。

也參考
......

Python Packaging User Guide: Creating and using virtual environments(4)

*note Availability: 1c56.: not WASI, not iOS.

This module does not work or is not available on WebAssembly platforms,
or on iOS. See *note WebAssembly 平台: 16e6. for more information on
WASM availability; see *note iOS: 1d56. for more information on iOS
availability.

* Menu:

* 建立虛擬環境: 建立虛擬環境<2>.
* 虛擬環境如何運作::
* API: API<2>.
* An example of extending EnvBuilder::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/venv/

   (2) https://pypi.org/project/pip/

   (3) https://peps.python.org/pep-0405/

   (4) 
https://packaging.python.org/guides/installing-using-pip-and-virtual-environments/#create-and-use-virtual-environments


File: python.info,  Node: 建立虛擬環境<2>,  Next: 虛擬環境如何運作,  Up: venv --- 建立虛擬環境

5.28.2.1 建立虛擬環境
.....................

建立*note 虛擬環境: 4137.的方法是透過執行指令 ‘venv’：

     python -m venv /path/to/new/virtual/environment

執行此命令會建立目標目錄（同時也會建立任何還不存在的父目錄）並在目錄中放
置一個名為 ‘pyvenv.cfg’ 的檔案，其中包含一個指向執行該命令的 Python 安裝
路徑的 ‘home’ 鍵（目標目錄的常見名稱為 ‘.venv’）。同時，它會建立一個
‘bin’ （在 Windows 上為 ‘Scripts’）子目錄，其中包含一個 Python 二進位檔
案的副本/符號連結（根據建立環境時使用的平台或引數而定）。此外，它還會建
立一個（最初為空的） ‘lib/pythonX.Y/site-packages’ 子目錄（在 Windows 上
為 ‘Lib\site-packages’）。如果指定的目錄已存在，則將重新使用該目錄。

在 3.5 版的變更: 目前建議使用 ‘venv’ 來建立虛擬環境。

在 3.6 版之後被棄用: ‘pyvenv’ 是在 Python 3.3 和 3.4 中建立虛擬環境的推
薦工具，但在 Python 3.6 中已被*note 棄用: cd9.。

在 Windows 上，執行以下命令以使用 ‘venv’：

     c:\>Python35\python -m venv c:\path\to\myenv

或者，如你已經為你的 *note Python 安裝: a4a.配置了 ‘PATH’ 和 ‘PATHEXT’ 變
數，則可以執行以下命令：

     c:\>python -m venv c:\path\to\myenv

如果使用 ‘-h’ 選項執行該命令，將會顯示可用的選項：

     usage: venv [-h] [--system-site-packages] [--symlinks | --copies] [--clear]
                 [--upgrade] [--without-pip] [--prompt PROMPT] [--upgrade-deps]
                 [--without-scm-ignore-file]
                 ENV_DIR [ENV_DIR ...]

     Creates virtual Python environments in one or more target directories.

     positional arguments:
     ENV_DIR               A directory to create the environment in.

     options:
     -h, --help            show this help message and exit
     --system-site-packages
                             Give the virtual environment access to the system
                             site-packages dir.
     --symlinks            Try to use symlinks rather than copies, when
                             symlinks are not the default for the platform.
     --copies              Try to use copies rather than symlinks, even when
                             symlinks are the default for the platform.
     --clear               Delete the contents of the environment directory if
                             it already exists, before environment creation.
     --upgrade             Upgrade the environment directory to use this
                             version of Python, assuming Python has been upgraded
                             in-place.
     --without-pip         Skips installing or upgrading pip in the virtual
                             environment (pip is bootstrapped by default)
     --prompt PROMPT       Provides an alternative prompt prefix for this
                             environment.
     --upgrade-deps        Upgrade core dependencies (pip) to the latest
                             version in PyPI
     --without-scm-ignore-file
                             Skips adding the default SCM ignore file to the
                             environment directory (the default is a .gitignore
                             file).

     Once an environment has been created, you may wish to activate it, e.g. by
     sourcing an activate script in its bin directory.

在 3.13 版的變更: ‘--without-scm-ignore-file’ was added along with
creating an ignore file for ‘git’ by default.

在 3.12 版的變更: ‘setuptools’ is no longer a core venv dependency.

在 3.9 版的變更: 新增 ‘--upgrade-deps’ 選項以將 pip 和 setuptools 升級至
PyPI 上的最新版本

在 3.4 版的變更: 預設情況下安裝 pip，並新增了 ‘--without-pip’ 和
‘--copies’ 選項

在 3.4 版的變更: 在較早的版本中，如果目標目錄已存在，除非提供了
‘--clear’ 或 ‘--upgrade’ 選項，否則會引發錯誤。

     備註: 雖然在 Windows 上支援符號連結，但並不建議使用。特別需要注意的
     是，在檔案總管中按兩下 ‘python.exe’ 會急切地解析符號連結並忽略虛擬
     環境。

     備註: 在 Microsoft Windows 上，可能需要通過設置使用者的執行策略來啟
     用 ‘Activate.ps1’ 腳本。你可以發出以下 PowerShell 命令來執行此操作
     ：

     PS C:> Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope
     CurrentUser

     有關更多資訊，請參閱關於執行策略(1)。

被建立的 ‘pyvenv.cfg’ 檔案還包括了 ‘include-system-site-packages’ 的鍵，
如果使用 ‘venv’ 執行時帶有 ‘--system-site-packages’ 選項，則設置為
‘true’，否則設置為 ‘false’。

除非 ‘--without-pip’ 選項被提供，否則將調用 *note ensurepip: 4b. 來啟動
‘pip’ 到虛擬環境中。

可以向 ‘venv’ 提供多個路徑，這樣每個提供的路徑都將根據給定的選項建立一個
相同的虛擬環境。

   ---------- Footnotes ----------

   (1) https://go.microsoft.com/fwlink/?LinkID=135170


File: python.info,  Node: 虛擬環境如何運作,  Next: API<2>,  Prev: 建立虛擬環境<2>,  Up: venv --- 建立虛擬環境

5.28.2.2 虛擬環境如何運作
.........................

當 Python 直譯器跑在虛擬環境時，*note sys.prefix: 381. 和 *note
sys.exec_prefix: 37d. 會指向虛擬環境的目錄，而 *note sys.base_prefix:
3afe. 和 *note sys.base_exec_prefix: 413b. 會指向建立虛擬環境的基礎
Python 的目錄。檢查 ‘sys.prefix != sys.base_prefix’ 就可以確定目前的直譯
器是否跑在虛擬環境中。

虛擬環境可以透過位於二進位檔案目錄中的腳本「啟用」（在 POSIX 上為 ‘bin’；
在 Windows 上為 ‘Scripts’）這會將該目錄加入到你的 ‘PATH’，當你運行
‘python’ 時就會調用該環境的直譯器並且執行已安裝的腳本，而不需要使用完整
的路徑。啟動腳本的方式因平台而異（‘<VENV>’ 需要替換成包含虛擬環境的目錄
路徑）

平台              Shell            啟動虛擬環境的指令
                                   
------------------------------------------------------------------------------------------
                                   
POSIX             bash/zsh         ‘$ source <VENV>/bin/activate’
                                   
                  
fish              ‘$ source
                  <VENV>/bin/activate.fish’
                  
                  
csh/tcsh          ‘$ source
                  <VENV>/bin/activate.csh’
                  
                  
PowerShell        ‘$
                  <VENV>/bin/Activate.ps1’
                  
                                   
Windows           cmd.exe          ‘C:\> <VENV>\Scripts\activate.bat’
                                   
                  
PowerShell        ‘PS C:\>
                  <VENV>\Scripts\Activate.ps1’
                  

在 3.4 版被加入: ‘fish’ 和 ‘csh’ 啟動腳本。

在 3.8 版被加入: PowerShell 的啟動腳本安裝在 POSIX 上支援 PowerShell
Core。

你不用特別開啟虛擬環境，你可以在調用 Python 時指定該環境下 Python 直譯器
的完整路徑。此外，所有安裝在環境裡的腳本都應該都可以在未啟用虛擬環境的情
況下運行。

為了實現這一點，安裝在虛擬環境中的腳本會有一個 "shebang" 列，此列指向該
環境的 Python 直譯器，例如： ‘#!/<PATH-TO-VENV>/bin/python’。這代表無論
‘PATH’ 的值為何，該腳本都會在直譯器上運行。在 Windows 上，如果你安裝了
*note Python Launcher for Windows: 562.，則支援 "shebang" 列處理。因此，
在 Windows 檔案總管（Windows Explorer）中雙擊已安裝的腳本，應該可以在沒
有啟用環境或將其加入 ‘PATH’ 的情況下正確地運行。

當虛擬環境被啟用時，‘VIRTUAL_ENV’ 環境變數會被設置為該環境的路徑。由於不
需要明確啟用虛擬環境才能使用它。因此，無法依賴 ‘VIRTUAL_ENV’ 來判斷是否
正在使用虛擬環境。

     警告: 因為安裝在環境中的腳本不應該預期該環境已經被啟動，所以它們的
     shebang 列會包含環境直譯器的絕對路徑。因此，在一般情況下，環境本質
     上是不可攜帶的。你應該使用一個簡單的方法來重新建立一個環境（例如：
     如果你有一個名為 ‘requirements.txt’ 的需求檔案，你可以使用環境的
     ‘pip install -r requirements.txt’ 來安裝環境所需的所有套件）。如果
     出於某種原因，你需要將環境移至新位置，你應該在所需位置重新建立它，
     並刪除舊位置的環境。如果你移動環境是因為移動了其父目錄，你應該在新
     位置重新建立環境。否則，安裝在該環境中的軟體可能無法正常運作。

你可以在 shell 輸入 ‘deactivate’ 來關閉虛擬環境。具體的使用方式因平台而
異，是內部實作的細節（通常會使用腳本或是 shell 函式）


File: python.info,  Node: API<2>,  Next: An example of extending EnvBuilder,  Prev: 虛擬環境如何運作,  Up: venv --- 建立虛擬環境

5.28.2.3 API
............

上述提到的高階 method（方法）透過簡單的 API 使用， 為第三方虛擬環境建立
者提供可以依據他們需求來建立環境的客製化機制： *note EnvBuilder: 24f.
class。

 -- 類別: venv.EnvBuilder (system_site_packages=False, clear=False,
          symlinks=False, upgrade=False, with_pip=False, prompt=None,
          upgrade_deps=False, *, scm_ignore_files=frozenset())

     進行實例化時，class *note EnvBuilder: 24f. 接受下列的關鍵字引數：

        * ‘system_site_packages’ - 為一個 Boolean （布林值），並表明系統
          的 Python site-packages 是否可以在環境中可用（預設為 ‘False’ ）
          。

        * ‘clear’ - 為一個 Boolean，如果為 true，則在建立環境之前，刪除
          目標目錄內所有存在的內容。

        * ‘symlinks’ - 為一個 Boolean，並表明是否嘗試與 Python 二進位檔
          案建立符號連結而不是複製該檔案。

        * ‘upgrade’ - 為一個 Boolean，若為 true，則會在執行 Python 時為
          現有的環境進行升級。目的是讓 Python 可以升級到位（預設為
          ‘False’）。

        * ‘with_pip’ - 為一個 Boolean，若為 true，則確保 pip 有安裝至虛
          擬環境之中。當有 ‘--default-pip’ 的選項時，會使用 *note
          ensurepip: 4b.。

        * ‘prompt’ - 為一個 String（字串），該字串會在虛擬環境啟動時被使
          用。（預設為 ‘None’，代表該環境的目錄名稱會被使用）倘若出現特
          殊字串 ‘"."’ ，則當前目錄的 basename 會做為提示路徑使用。

        * ‘upgrade_deps’ - 更新基礎 venv 模組至 PyPI 的最新版本

        * ‘scm_ignore_files’ - Create ignore files based for the
          specified source control managers (SCM) in the iterable.
          Support is defined by having a method named
          ‘create_{scm}_ignore_file’.  The only value supported by
          default is ‘"git"’ via *note create_git_ignore_file(): 413d.

     在 3.4 版的變更: 新增 ‘with_pip’ 參數

     在 3.6 版的變更: 新增 ‘prompt’ 參數

     在 3.9 版的變更: 新增 ‘upgrade_deps’ 參數

     在 3.13 版的變更: Added the ‘scm_ignore_files’ parameter

     第三方虛擬環境工具的建立者可以自由地使用 *note EnvBuilder: 24f.
     class 作為 base class（基底類別）使用.

     回傳的 env-builder 為一個物件，且帶有一個 method ‘create’：

      -- 方法: create (env_dir)

          透過指定將會容納虛擬環境的目標目錄來建立一個虛擬環境（絕對路徑
          或相對路徑到該目錄），也就是在該目錄中容納虛擬環境。‘create’
          method 將會在指定的目錄下建立環境，或是觸發適當的例外。

          *note EnvBuilder: 24f. class 的 ‘create’ method 會闡述可用的
          Hooks 以客製化 subclass （子類別）:

               def create(self, env_dir):
                   """
                   Create a virtualized Python environment in a directory.
                   env_dir is the target directory to create an environment in.
                   """
                   env_dir = os.path.abspath(env_dir)
                   context = self.ensure_directories(env_dir)
                   self.create_configuration(context)
                   self.setup_python(context)
                   self.setup_scripts(context)
                   self.post_setup(context)

          每個 methods *note ensure_directories(): 413f.、*note
          create_configuration(): 4140.、*note setup_python(): 4141.、
          *note setup_scripts(): 4142. 及 *note post_setup(): 4143. 都可
          以被覆寫。

      -- 方法: ensure_directories (env_dir)

          建立還不存在的環境目錄及必要的子目錄，並回傳一個情境物件（
          context object）。這個情境物件只是一個屬性 (例如：路徑) 的所有
          者，可被其他 method 使用。如果 *note EnvBuilder: 24f. 已被建立
          且帶有 ‘clear=True’ 的引數，該環境目錄下的內容將被清空，以及所
          有必要的子目錄將被重新建立。

          回傳的情境物件（context object）其型別會是 *note
          types.SimpleNamespace: 1b5.，並包含以下屬性：

             * ‘env_dir’ - The location of the virtual environment.
               Used for ‘__VENV_DIR__’ in activation scripts (see *note
               install_scripts(): 4144.).

             * ‘env_name’ - The name of the virtual environment.  Used
               for ‘__VENV_NAME__’ in activation scripts (see *note
               install_scripts(): 4144.).

             * ‘prompt’ - The prompt to be used by the activation
               scripts.  Used for ‘__VENV_PROMPT__’ in activation
               scripts (see *note install_scripts(): 4144.).

             * ‘executable’ - The underlying Python executable used by
               the virtual environment.  This takes into account the
               case where a virtual environment is created from another
               virtual environment.

             * ‘inc_path’ - The include path for the virtual
               environment.

             * ‘lib_path’ - The purelib path for the virtual
               environment.

             * ‘bin_path’ - The script path for the virtual environment.

             * ‘bin_name’ - The name of the script path relative to the
               virtual environment location.  Used for
               ‘__VENV_BIN_NAME__’ in activation scripts (see *note
               install_scripts(): 4144.).

             * ‘env_exe’ - The name of the Python interpreter in the
               virtual environment.  Used for ‘__VENV_PYTHON__’ in
               activation scripts (see *note install_scripts(): 4144.).

             * ‘env_exec_cmd’ - The name of the Python interpreter,
               taking into account filesystem redirections.  This can be
               used to run Python in the virtual environment.

          在 3.11 版的變更: The 'venv' *note sysconfig installation
          scheme: 635. is used to construct the paths of the created
          directories.

          在 3.12 版的變更: The attribute ‘lib_path’ was added to the
          context, and the context object was documented.

      -- 方法: create_configuration (context)

          Creates the ‘pyvenv.cfg’ configuration file in the
          environment.

      -- 方法: setup_python (context)

          Creates a copy or symlink to the Python executable in the
          environment.  On POSIX systems, if a specific executable
          ‘python3.x’ was used, symlinks to ‘python’ and ‘python3’ will
          be created pointing to that executable, unless files with
          those names already exist.

      -- 方法: setup_scripts (context)

          Installs activation scripts appropriate to the platform into
          the virtual environment.

      -- 方法: upgrade_dependencies (context)

          Upgrades the core venv dependency packages (currently ‘pip’)
          in the environment.  This is done by shelling out to the ‘pip’
          executable in the environment.

          在 3.9 版被加入.

          在 3.12 版的變更: ‘setuptools’ is no longer a core venv
          dependency.

      -- 方法: post_setup (context)

          A placeholder method which can be overridden in third party
          implementations to pre-install packages in the virtual
          environment or perform other post-creation steps.

     在 3.7.2 版的變更: Windows now uses redirector scripts for
     ‘python[w].exe’ instead of copying the actual binaries.  In 3.7.2
     only *note setup_python(): 4141. does nothing unless running from a
     build in the source tree.

     在 3.7.3 版的變更: Windows copies the redirector scripts as part of
     *note setup_python(): 4141. instead of *note setup_scripts(): 4142.
     This was not the case in 3.7.2.  When using symlinks, the original
     executables will be linked.

     In addition, *note EnvBuilder: 24f. provides this utility method
     that can be called from *note setup_scripts(): 4142. or *note
     post_setup(): 4143. in subclasses to assist in installing custom
     scripts into the virtual environment.

      -- 方法: install_scripts (context, path)

          'path' is the path to a directory that should contain
          subdirectories "common", "posix", "nt", each containing
          scripts destined for the bin directory in the environment.
          The contents of "common" and the directory corresponding to
          *note os.name: 29ed. are copied after some text replacement of
          placeholders:

             * ‘__VENV_DIR__’ is replaced with the absolute path of the
               environment directory.

             * ‘__VENV_NAME__’ is replaced with the environment name
               (final path segment of environment directory).

             * ‘__VENV_PROMPT__’ is replaced with the prompt (the
               environment name surrounded by parentheses and with a
               following space)

             * ‘__VENV_BIN_NAME__’ is replaced with the name of the bin
               directory (either ‘bin’ or ‘Scripts’).

             * ‘__VENV_PYTHON__’ is replaced with the absolute path of
               the environment's executable.

          The directories are allowed to exist (for when an existing
          environment is being upgraded).

      -- 方法: create_git_ignore_file (context)

          Creates a ‘.gitignore’ file within the virtual environment
          that causes the entire directory to be ignored by the ‘git’
          source control manager.

          在 3.13 版被加入.

There is also a module-level convenience function:

 -- 函式: venv.create (env_dir, system_site_packages=False, clear=False,
          symlinks=False, with_pip=False, prompt=None,
          upgrade_deps=False, *, scm_ignore_files=frozenset())

     Create an *note EnvBuilder: 24f. with the given keyword arguments,
     and call its *note create(): 413e. method with the 'env_dir'
     argument.

     在 3.3 版被加入.

     在 3.4 版的變更: 新增 ‘with_pip’ 參數

     在 3.6 版的變更: 新增 ‘prompt’ 參數

     在 3.9 版的變更: 新增 ‘upgrade_deps’ 參數

     在 3.13 版的變更: Added the ‘scm_ignore_files’ parameter


File: python.info,  Node: An example of extending EnvBuilder,  Prev: API<2>,  Up: venv --- 建立虛擬環境

5.28.2.4 An example of extending ‘EnvBuilder’
.............................................

The following script shows how to extend *note EnvBuilder: 24f. by
implementing a subclass which installs setuptools and pip into a created
virtual environment:

     import os
     import os.path
     from subprocess import Popen, PIPE
     import sys
     from threading import Thread
     from urllib.parse import urlparse
     from urllib.request import urlretrieve
     import venv

     class ExtendedEnvBuilder(venv.EnvBuilder):
         """
         This builder installs setuptools and pip so that you can pip or
         easy_install other packages into the created virtual environment.

         :param nodist: If true, setuptools and pip are not installed into the
                        created virtual environment.
         :param nopip: If true, pip is not installed into the created
                       virtual environment.
         :param progress: If setuptools or pip are installed, the progress of the
                          installation can be monitored by passing a progress
                          callable. If specified, it is called with two
                          arguments: a string indicating some progress, and a
                          context indicating where the string is coming from.
                          The context argument can have one of three values:
                          'main', indicating that it is called from virtualize()
                          itself, and 'stdout' and 'stderr', which are obtained
                          by reading lines from the output streams of a subprocess
                          which is used to install the app.

                          If a callable is not specified, default progress
                          information is output to sys.stderr.
         """

         def __init__(self, *args, **kwargs):
             self.nodist = kwargs.pop('nodist', False)
             self.nopip = kwargs.pop('nopip', False)
             self.progress = kwargs.pop('progress', None)
             self.verbose = kwargs.pop('verbose', False)
             super().__init__(*args, **kwargs)

         def post_setup(self, context):
             """
             Set up any packages which need to be pre-installed into the
             virtual environment being created.

             :param context: The information for the virtual environment
                             creation request being processed.
             """
             os.environ['VIRTUAL_ENV'] = context.env_dir
             if not self.nodist:
                 self.install_setuptools(context)
             # Can't install pip without setuptools
             if not self.nopip and not self.nodist:
                 self.install_pip(context)

         def reader(self, stream, context):
             """
             Read lines from a subprocess' output stream and either pass to a progress
             callable (if specified) or write progress information to sys.stderr.
             """
             progress = self.progress
             while True:
                 s = stream.readline()
                 if not s:
                     break
                 if progress is not None:
                     progress(s, context)
                 else:
                     if not self.verbose:
                         sys.stderr.write('.')
                     else:
                         sys.stderr.write(s.decode('utf-8'))
                     sys.stderr.flush()
             stream.close()

         def install_script(self, context, name, url):
             _, _, path, _, _, _ = urlparse(url)
             fn = os.path.split(path)[-1]
             binpath = context.bin_path
             distpath = os.path.join(binpath, fn)
             # Download script into the virtual environment's binaries folder
             urlretrieve(url, distpath)
             progress = self.progress
             if self.verbose:
                 term = '\n'
             else:
                 term = ''
             if progress is not None:
                 progress('Installing %s ...%s' % (name, term), 'main')
             else:
                 sys.stderr.write('Installing %s ...%s' % (name, term))
                 sys.stderr.flush()
             # Install in the virtual environment
             args = [context.env_exe, fn]
             p = Popen(args, stdout=PIPE, stderr=PIPE, cwd=binpath)
             t1 = Thread(target=self.reader, args=(p.stdout, 'stdout'))
             t1.start()
             t2 = Thread(target=self.reader, args=(p.stderr, 'stderr'))
             t2.start()
             p.wait()
             t1.join()
             t2.join()
             if progress is not None:
                 progress('done.', 'main')
             else:
                 sys.stderr.write('done.\n')
             # Clean up - no longer needed
             os.unlink(distpath)

         def install_setuptools(self, context):
             """
             Install setuptools in the virtual environment.

             :param context: The information for the virtual environment
                             creation request being processed.
             """
             url = "https://bootstrap.pypa.io/ez_setup.py"
             self.install_script(context, 'setuptools', url)
             # clear up the setuptools archive which gets downloaded
             pred = lambda o: o.startswith('setuptools-') and o.endswith('.tar.gz')
             files = filter(pred, os.listdir(context.bin_path))
             for f in files:
                 f = os.path.join(context.bin_path, f)
                 os.unlink(f)

         def install_pip(self, context):
             """
             Install pip in the virtual environment.

             :param context: The information for the virtual environment
                             creation request being processed.
             """
             url = 'https://bootstrap.pypa.io/get-pip.py'
             self.install_script(context, 'pip', url)


     def main(args=None):
         import argparse

         parser = argparse.ArgumentParser(prog=__name__,
                                          description='Creates virtual Python '
                                                      'environments in one or '
                                                      'more target '
                                                      'directories.')
         parser.add_argument('dirs', metavar='ENV_DIR', nargs='+',
                             help='A directory in which to create the '
                                  'virtual environment.')
         parser.add_argument('--no-setuptools', default=False,
                             action='store_true', dest='nodist',
                             help="Don't install setuptools or pip in the "
                                  "virtual environment.")
         parser.add_argument('--no-pip', default=False,
                             action='store_true', dest='nopip',
                             help="Don't install pip in the virtual "
                                  "environment.")
         parser.add_argument('--system-site-packages', default=False,
                             action='store_true', dest='system_site',
                             help='Give the virtual environment access to the '
                                  'system site-packages dir.')
         if os.name == 'nt':
             use_symlinks = False
         else:
             use_symlinks = True
         parser.add_argument('--symlinks', default=use_symlinks,
                             action='store_true', dest='symlinks',
                             help='Try to use symlinks rather than copies, '
                                  'when symlinks are not the default for '
                                  'the platform.')
         parser.add_argument('--clear', default=False, action='store_true',
                             dest='clear', help='Delete the contents of the '
                                                'virtual environment '
                                                'directory if it already '
                                                'exists, before virtual '
                                                'environment creation.')
         parser.add_argument('--upgrade', default=False, action='store_true',
                             dest='upgrade', help='Upgrade the virtual '
                                                  'environment directory to '
                                                  'use this version of '
                                                  'Python, assuming Python '
                                                  'has been upgraded '
                                                  'in-place.')
         parser.add_argument('--verbose', default=False, action='store_true',
                             dest='verbose', help='Display the output '
                                                  'from the scripts which '
                                                  'install setuptools and pip.')
         options = parser.parse_args(args)
         if options.upgrade and options.clear:
             raise ValueError('you cannot supply --upgrade and --clear together.')
         builder = ExtendedEnvBuilder(system_site_packages=options.system_site,
                                        clear=options.clear,
                                        symlinks=options.symlinks,
                                        upgrade=options.upgrade,
                                        nodist=options.nodist,
                                        nopip=options.nopip,
                                        verbose=options.verbose)
         for d in options.dirs:
             builder.create(d)

     if __name__ == '__main__':
         rc = 1
         try:
             main()
             rc = 0
         except Exception as e:
             print('Error: %s' % e, file=sys.stderr)
         sys.exit(rc)

This script is also available for download online(1).

   ---------- Footnotes ----------

   (1) https://gist.github.com/vsajip/4673395


File: python.info,  Node: zipapp —-- 管理可執行的 Python zip 封存檔案,  Prev: venv --- 建立虛擬環境,  Up: 軟體封裝與發布

5.28.3 ‘zipapp’ —- 管理可執行的 Python zip 封存檔案
---------------------------------------------------

在 3.5 版被加入.

'原始碼：'Lib/zipapp.py(1)

__________________________________________________________________

This module provides tools to manage the creation of zip files
containing Python code, which can be *note executed directly by the
Python interpreter: 1c2b.  The module provides both a *note
命令執行列介面: 4149. and a *note Python API: 414a.

* Menu:

* 基本範例::
* 命令執行列介面::
* Python API::
* 範例: 範例<44>.
* Specifying the Interpreter::
* Creating Standalone Applications with zipapp::
* The Python Zip Application Archive Format::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/zipapp.py


File: python.info,  Node: 基本範例,  Next: 命令執行列介面,  Up: zipapp —-- 管理可執行的 Python zip 封存檔案

5.28.3.1 基本範例
.................

The following example shows how the *note 命令執行列介面: 4149. can be
used to create an executable archive from a directory containing Python
code.  When run, the archive will execute the ‘main’ function from the
module ‘myapp’ in the archive.

     $ python -m zipapp myapp -m "myapp:main"
     $ python myapp.pyz
     <output from myapp>


File: python.info,  Node: 命令執行列介面,  Next: Python API,  Prev: 基本範例,  Up: zipapp —-- 管理可執行的 Python zip 封存檔案

5.28.3.2 命令執行列介面
.......................

When called as a program from the command line, the following form is
used:

     $ python -m zipapp source [options]

If 'source' is a directory, this will create an archive from the
contents of 'source'.  If 'source' is a file, it should be an archive,
and it will be copied to the target archive (or the contents of its
shebang line will be displayed if the -info option is specified).

The following options are understood:

 -- Option: -o <output>, --output=<output>

     Write the output to a file named 'output'.  If this option is not
     specified, the output filename will be the same as the input
     'source', with the extension ‘.pyz’ added.  If an explicit filename
     is given, it is used as is (so a ‘.pyz’ extension should be
     included if required).

     An output filename must be specified if the 'source' is an archive
     (and in that case, 'output' must not be the same as 'source').

 -- Option: -p <interpreter>, --python=<interpreter>

     Add a ‘#!’ line to the archive specifying 'interpreter' as the
     command to run.  Also, on POSIX, make the archive executable.  The
     default is to write no ‘#!’ line, and not make the file executable.

 -- Option: -m <mainfn>, --main=<mainfn>

     Write a ‘__main__.py’ file to the archive that executes 'mainfn'.
     The 'mainfn' argument should have the form "pkg.mod:fn", where
     "pkg.mod" is a package/module in the archive, and "fn" is a
     callable in the given module.  The ‘__main__.py’ file will execute
     that callable.

     *note -main: 4151. cannot be specified when copying an archive.

 -- Option: -c, --compress

     Compress files with the deflate method, reducing the size of the
     output file.  By default, files are stored uncompressed in the
     archive.

     *note -compress: 4153. has no effect when copying an archive.

     在 3.7 版被加入.

 -- Option: --info

     Display the interpreter embedded in the archive, for diagnostic
     purposes.  In this case, any other options are ignored and SOURCE
     must be an archive, not a directory.

 -- Option: -h, --help

     Print a short usage message and exit.


File: python.info,  Node: Python API,  Next: 範例<44>,  Prev: 命令執行列介面,  Up: zipapp —-- 管理可執行的 Python zip 封存檔案

5.28.3.3 Python API
...................

The module defines two convenience functions:

 -- 函式: zipapp.create_archive (source, target=None, interpreter=None,
          main=None, filter=None, compressed=False)

     Create an application archive from 'source'.  The source can be any
     of the following:

        * The name of a directory, or a *note path-like object: ac2.
          referring to a directory, in which case a new application
          archive will be created from the content of that directory.

        * The name of an existing application archive file, or a *note
          path-like object: ac2. referring to such a file, in which case
          the file is copied to the target (modifying it to reflect the
          value given for the 'interpreter' argument).  The file name
          should include the ‘.pyz’ extension, if required.

        * A file object open for reading in bytes mode.  The content of
          the file should be an application archive, and the file object
          is assumed to be positioned at the start of the archive.

     The 'target' argument determines where the resulting archive will
     be written:

        * If it is the name of a file, or a *note path-like object: ac2,
          the archive will be written to that file.

        * If it is an open file object, the archive will be written to
          that file object, which must be open for writing in bytes
          mode.

        * If the target is omitted (or ‘None’), the source must be a
          directory and the target will be a file with the same name as
          the source, with a ‘.pyz’ extension added.

     The 'interpreter' argument specifies the name of the Python
     interpreter with which the archive will be executed.  It is written
     as a "shebang" line at the start of the archive.  On POSIX, this
     will be interpreted by the OS, and on Windows it will be handled by
     the Python launcher.  Omitting the 'interpreter' results in no
     shebang line being written.  If an interpreter is specified, and
     the target is a filename, the executable bit of the target file
     will be set.

     The 'main' argument specifies the name of a callable which will be
     used as the main program for the archive.  It can only be specified
     if the source is a directory, and the source does not already
     contain a ‘__main__.py’ file.  The 'main' argument should take the
     form "pkg.module:callable" and the archive will be run by importing
     "pkg.module" and executing the given callable with no arguments.
     It is an error to omit 'main' if the source is a directory and does
     not contain a ‘__main__.py’ file, as otherwise the resulting
     archive would not be executable.

     The optional 'filter' argument specifies a callback function that
     is passed a Path object representing the path to the file being
     added (relative to the source directory).  It should return ‘True’
     if the file is to be added.

     The optional 'compressed' argument determines whether files are
     compressed.  If set to ‘True’, files in the archive are compressed
     with the deflate method; otherwise, files are stored uncompressed.
     This argument has no effect when copying an existing archive.

     If a file object is specified for 'source' or 'target', it is the
     caller's responsibility to close it after calling create_archive.

     When copying an existing archive, file objects supplied only need
     ‘read’ and ‘readline’, or ‘write’ methods.  When creating an
     archive from a directory, if the target is a file object it will be
     passed to the ‘zipfile.ZipFile’ class, and must supply the methods
     needed by that class.

     在 3.7 版的變更: 新增 'filter' 與 'compressed' 參數。

 -- 函式: zipapp.get_interpreter (archive)

     Return the interpreter specified in the ‘#!’ line at the start of
     the archive.  If there is no ‘#!’ line, return *note None: 61b.
     The 'archive' argument can be a filename or a file-like object open
     for reading in bytes mode.  It is assumed to be at the start of the
     archive.


File: python.info,  Node: 範例<44>,  Next: Specifying the Interpreter,  Prev: Python API,  Up: zipapp —-- 管理可執行的 Python zip 封存檔案

5.28.3.4 範例
.............

Pack up a directory into an archive, and run it.

     $ python -m zipapp myapp
     $ python myapp.pyz
     <output from myapp>

The same can be done using the *note create_archive(): b57. function:

     >>> import zipapp
     >>> zipapp.create_archive('myapp', 'myapp.pyz')

To make the application directly executable on POSIX, specify an
interpreter to use.

     $ python -m zipapp myapp -p "/usr/bin/env python"
     $ ./myapp.pyz
     <output from myapp>

To replace the shebang line on an existing archive, create a modified
archive using the *note create_archive(): b57. function:

     >>> import zipapp
     >>> zipapp.create_archive('old_archive.pyz', 'new_archive.pyz', '/usr/bin/python3')

To update the file in place, do the replacement in memory using a *note
BytesIO: e46. object, and then overwrite the source afterwards.  Note
that there is a risk when overwriting a file in place that an error will
result in the loss of the original file.  This code does not protect
against such errors, but production code should do so.  Also, this
method will only work if the archive fits in memory:

     >>> import zipapp
     >>> import io
     >>> temp = io.BytesIO()
     >>> zipapp.create_archive('myapp.pyz', temp, '/usr/bin/python2')
     >>> with open('myapp.pyz', 'wb') as f:
     >>>     f.write(temp.getvalue())


File: python.info,  Node: Specifying the Interpreter,  Next: Creating Standalone Applications with zipapp,  Prev: 範例<44>,  Up: zipapp —-- 管理可執行的 Python zip 封存檔案

5.28.3.5 Specifying the Interpreter
...................................

Note that if you specify an interpreter and then distribute your
application archive, you need to ensure that the interpreter used is
portable.  The Python launcher for Windows supports most common forms of
POSIX ‘#!’ line, but there are other issues to consider:

   * If you use "/usr/bin/env python" (or other forms of the "python"
     command, such as "/usr/bin/python"), you need to consider that your
     users may have either Python 2 or Python 3 as their default, and
     write your code to work under both versions.

   * If you use an explicit version, for example "/usr/bin/env python3"
     your application will not work for users who do not have that
     version.  (This may be what you want if you have not made your code
     Python 2 compatible).

   * There is no way to say "python X.Y or later", so be careful of
     using an exact version like "/usr/bin/env python3.4" as you will
     need to change your shebang line for users of Python 3.5, for
     example.

Typically, you should use an "/usr/bin/env python2" or "/usr/bin/env
python3", depending on whether your code is written for Python 2 or 3.


File: python.info,  Node: Creating Standalone Applications with zipapp,  Next: The Python Zip Application Archive Format,  Prev: Specifying the Interpreter,  Up: zipapp —-- 管理可執行的 Python zip 封存檔案

5.28.3.6 Creating Standalone Applications with zipapp
.....................................................

Using the *note zipapp: 116. module, it is possible to create
self-contained Python programs, which can be distributed to end users
who only need to have a suitable version of Python installed on their
system.  The key to doing this is to bundle all of the application's
dependencies into the archive, along with the application code.

The steps to create a standalone archive are as follows:

  1. Create your application in a directory as normal, so you have a
     ‘myapp’ directory containing a ‘__main__.py’ file, and any
     supporting application code.

  2. Install all of your application's dependencies into the ‘myapp’
     directory, using pip:

          $ python -m pip install -r requirements.txt --target myapp

     (this assumes you have your project requirements in a
     ‘requirements.txt’ file - if not, you can just list the
     dependencies manually on the pip command line).

  3. Package the application using:

          $ python -m zipapp -p "interpreter" myapp

This will produce a standalone executable, which can be run on any
machine with the appropriate interpreter available.  See *note
Specifying the Interpreter: 415d. for details.  It can be shipped to
users as a single file.

On Unix, the ‘myapp.pyz’ file is executable as it stands.  You can
rename the file to remove the ‘.pyz’ extension if you prefer a "plain"
command name.  On Windows, the ‘myapp.pyz[w]’ file is executable by
virtue of the fact that the Python interpreter registers the ‘.pyz’ and
‘.pyzw’ file extensions when installed.

* Menu:

* Caveats::


File: python.info,  Node: Caveats,  Up: Creating Standalone Applications with zipapp

5.28.3.7 Caveats
................

If your application depends on a package that includes a C extension,
that package cannot be run from a zip file (this is an OS limitation, as
executable code must be present in the filesystem for the OS loader to
load it).  In this case, you can exclude that dependency from the
zipfile, and either require your users to have it installed, or ship it
alongside your zipfile and add code to your ‘__main__.py’ to include the
directory containing the unzipped module in ‘sys.path’.  In this case,
you will need to make sure to ship appropriate binaries for your target
architecture(s) (and potentially pick the correct version to add to
‘sys.path’ at runtime, based on the user's machine).


File: python.info,  Node: The Python Zip Application Archive Format,  Prev: Creating Standalone Applications with zipapp,  Up: zipapp —-- 管理可執行的 Python zip 封存檔案

5.28.3.8 The Python Zip Application Archive Format
..................................................

Python has been able to execute zip files which contain a ‘__main__.py’
file since version 2.6.  In order to be executed by Python, an
application archive simply has to be a standard zip file containing a
‘__main__.py’ file which will be run as the entry point for the
application.  As usual for any Python script, the parent of the script
(in this case the zip file) will be placed on *note sys.path: 37f. and
thus further modules can be imported from the zip file.

The zip file format allows arbitrary data to be prepended to a zip file.
The zip application format uses this ability to prepend a standard POSIX
"shebang" line to the file (‘#!/path/to/interpreter’).

Formally, the Python zip application format is therefore:

  1. An optional shebang line, containing the characters ‘b'#!'’
     followed by an interpreter name, and then a newline (‘b'\n'’)
     character.  The interpreter name can be anything acceptable to the
     OS "shebang" processing, or the Python launcher on Windows.  The
     interpreter should be encoded in UTF-8 on Windows, and in *note
     sys.getfilesystemencoding(): c00. on POSIX.

  2. Standard zipfile data, as generated by the *note zipfile: 117.
     module.  The zipfile content 'must' include a file called
     ‘__main__.py’ (which must be in the "root" of the zipfile - i.e.,
     it cannot be in a subdirectory).  The zipfile data can be
     compressed or uncompressed.

If an application archive has a shebang line, it may have the executable
bit set on POSIX systems, to allow it to be executed directly.

There is no requirement that the tools in this module are used to create
application archives - the module is a convenience, but archives in the
above format created by any means are acceptable to Python.


File: python.info,  Node: Python Runtime 服務,  Next: 自訂 Python 直譯器,  Prev: 軟體封裝與發布,  Up: Python 標準函式庫 Standard Library

5.29 Python Runtime 服務
========================

The modules described in this chapter provide a wide range of services
related to the Python interpreter and its interaction with its
environment.  Here's an overview:

* Menu:

* sys: sys --- 系統特定的參數與函式. 系統特定的參數與函式
* sys.monitoring: sys monitoring --- Execution event monitoring. Execution event monitoring
* sysconfig: sysconfig --- 提供 Python 設定資訊的存取. 提供 Python 設定資訊的存取
* builtins: builtins --- 內建物件. 內建物件
* __main__: __main__ --- 頂層程式碼環境. 頂層程式碼環境
* warnings: warnings --- 警告控制. 警告控制
* dataclasses: dataclasses --- Data Classes. Data Classes
* contextlib: contextlib --- Utilities for with-statement contexts. Utilities for with-statement contexts
* abc: abc --- 抽象基底類別. 抽象基底類別
* atexit: atexit --- 退出處理函式. 退出處理函式
* traceback: traceback --- 列印或取得堆疊回溯 stack traceback. 列印或取得堆疊回溯 (stack traceback)
* __future__: __future__ --- Future 陳述式定義. Future 陳述式定義
* gc: gc --- 垃圾回收器介面 Garbage Collector interface. 垃圾回收器介面 (Garbage Collector interface)
* inspect: inspect --- 檢視活動物件. 檢視活動物件
* site: site --- Site-specific configuration hook. Site-specific configuration hook


File: python.info,  Node: sys --- 系統特定的參數與函式,  Next: sys monitoring --- Execution event monitoring,  Up: Python Runtime 服務

5.29.1 ‘sys’ -- 系統特定的參數與函式
------------------------------------

__________________________________________________________________

This module provides access to some variables used or maintained by the
interpreter and to functions that interact strongly with the
interpreter.  It is always available.

 -- 資料: sys.abiflags

     On POSIX systems where Python was built with the standard
     ‘configure’ script, this contains the ABI flags as specified by PEP
     3149(1).

     在 3.2 版被加入.

     在 3.8 版的變更: Default flags became an empty string (‘m’ flag for
     pymalloc has been removed).

     *note 適用: 1c56.：Unix。

 -- 函式: sys.addaudithook (hook)

     Append the callable 'hook' to the list of active auditing hooks for
     the current (sub)interpreter.

     When an auditing event is raised through the *note sys.audit():
     1873. function, each hook will be called in the order it was added
     with the event name and the tuple of arguments.  Native hooks added
     by *note PySys_AddAuditHook(): 3ff2. are called first, followed by
     hooks added in the current (sub)interpreter.  Hooks can then log
     the event, raise an exception to abort the operation, or terminate
     the process entirely.

     Note that audit hooks are primarily for collecting information
     about internal or otherwise unobservable actions, whether by Python
     or libraries written in Python.  They are not suitable for
     implementing a "sandbox".  In particular, malicious code can
     trivially disable or bypass hooks added using this function.  At a
     minimum, any security-sensitive hooks must be added using the C API
     *note PySys_AddAuditHook(): 3ff2. before initialising the runtime,
     and any modules allowing arbitrary memory modification (such as
     *note ctypes: 22.) should be completely removed or closely
     monitored.

     呼叫 *note sys.addaudithook(): 3ff1. 本身會引發一個不帶任何引數、名
     為 ‘sys.addaudithook’ 的稽核事件。如果任何現有的 hook 引發從 *note
     RuntimeError: 179. 衍生的例外，則不會添加新的 hook 並抑制異常。因此
     ，除非呼叫者控制所有已存在的 hook，他們不能假設他們的 hook 已被添加
     。

     所有會被 CPython 所引發的事件請參考*note 稽核事件總表: 1773.、設計
     相關討論請見 PEP 578(2)。

     在 3.8 版被加入.

     在 3.8.1 版的變更: Exceptions derived from *note Exception: 97d.
     but not *note RuntimeError: 179. are no longer suppressed.

     'CPython 實作細節：' When tracing is enabled (see *note settrace():
     146e.), Python hooks are only traced if the callable has a
     ‘__cantrace__’ member that is set to a true value.  Otherwise,
     trace functions will skip the hook.

 -- 資料: sys.argv

     The list of command line arguments passed to a Python script.
     ‘argv[0]’ is the script name (it is operating system dependent
     whether this is a full pathname or not).  If the command was
     executed using the *note -c: 584. command line option to the
     interpreter, ‘argv[0]’ is set to the string ‘'-c'’.  If no script
     name was passed to the Python interpreter, ‘argv[0]’ is the empty
     string.

     To loop over the standard input, or the list of files given on the
     command line, see the *note fileinput: 51. module.

     另請參閱 *note sys.orig_argv: 7e4.。

          備註: On Unix, command line arguments are passed by bytes from
          OS. Python decodes them with filesystem encoding and
          "surrogateescape" error handler.  When you need original
          bytes, you can get it by ‘[os.fsencode(arg) for arg in
          sys.argv]’.

 -- 函式: sys.audit (event, *args)

     Raise an auditing event and trigger any active auditing hooks.
     'event' is a string identifying the event, and 'args' may contain
     optional arguments with more information about the event.  The
     number and types of arguments for a given event are considered a
     public and stable API and should not be modified between releases.

     舉例來說，一個名為 ‘os.chdir’ 的稽核事件擁有一個引數 'path'，其內容
     為所要求的新工作目錄。

     *note sys.audit(): 1873. will call the existing auditing hooks,
     passing the event name and arguments, and will re-raise the first
     exception from any hook.  In general, if an exception is raised, it
     should not be handled and the process should be terminated as
     quickly as possible.  This allows hook implementations to decide
     how to respond to particular events: they can merely log the event
     or abort the operation by raising an exception.

     Hooks are added using the *note sys.addaudithook(): 3ff1. or *note
     PySys_AddAuditHook(): 3ff2. functions.

     The native equivalent of this function is *note PySys_Audit(): 321.
     Using the native function is preferred when possible.

     所有會被 CPython 所引發的事件請參考*note 稽核事件總表: 1773.。

     在 3.8 版被加入.

 -- 資料: sys.base_exec_prefix

     Set during Python startup, before ‘site.py’ is run, to the same
     value as *note exec_prefix: 37d.  If not running in a *note virtual
     environment: 4137, the values will stay the same; if ‘site.py’
     finds that a virtual environment is in use, the values of *note
     prefix: 381. and *note exec_prefix: 37d. will be changed to point
     to the virtual environment, whereas *note base_prefix: 3afe. and
     *note base_exec_prefix: 413b. will remain pointing to the base
     Python installation (the one which the virtual environment was
     created from).

     在 3.3 版被加入.

 -- 資料: sys.base_prefix

     Set during Python startup, before ‘site.py’ is run, to the same
     value as *note prefix: 381.  If not running in a *note virtual
     environment: 4137, the values will stay the same; if ‘site.py’
     finds that a virtual environment is in use, the values of *note
     prefix: 381. and *note exec_prefix: 37d. will be changed to point
     to the virtual environment, whereas *note base_prefix: 3afe. and
     *note base_exec_prefix: 413b. will remain pointing to the base
     Python installation (the one which the virtual environment was
     created from).

     在 3.3 版被加入.

 -- 資料: sys.byteorder

     An indicator of the native byte order.  This will have the value
     ‘'big'’ on big-endian (most-significant byte first) platforms, and
     ‘'little'’ on little-endian (least-significant byte first)
     platforms.

 -- 資料: sys.builtin_module_names

     A tuple of strings containing the names of all modules that are
     compiled into this Python interpreter.  (This information is not
     available in any other way -- ‘modules.keys()’ only lists the
     imported modules.)

     另請參閱 *note sys.stdlib_module_names: 7e5. 清單。

 -- 函式: sys.call_tracing (func, args)

     Call ‘func(*args)’, while tracing is enabled.  The tracing state is
     saved, and restored afterwards.  This is intended to be called from
     a debugger from a checkpoint, to recursively debug or profile some
     other code.

     Tracing is suspended while calling a tracing function set by *note
     settrace(): 146e. or *note setprofile(): 146d. to avoid infinite
     recursion.  ‘call_tracing()’ enables explicit recursion of the
     tracing function.

 -- 資料: sys.copyright

     A string containing the copyright pertaining to the Python
     interpreter.

 -- 函式: sys._clear_type_cache ()

     Clear the internal type cache.  The type cache is used to speed up
     attribute and method lookups.  Use the function 'only' to drop
     unnecessary references during reference leak debugging.

     This function should be used for internal and specialized purposes
     only.

     在 3.13 版之後被棄用: Use the more general *note
     _clear_internal_caches(): 1566. function instead.

 -- 函式: sys._clear_internal_caches ()

     Clear all internal performance-related caches.  Use this function
     'only' to release unnecessary references and memory blocks when
     hunting for leaks.

     在 3.13 版被加入.

 -- 函式: sys._current_frames ()

     Return a dictionary mapping each thread's identifier to the topmost
     stack frame currently active in that thread at the time the
     function is called.  Note that functions in the *note traceback:
     e7. module can build the call stack given such a frame.

     This is most useful for debugging deadlock: this function does not
     require the deadlocked threads' cooperation, and such threads' call
     stacks are frozen for as long as they remain deadlocked.  The frame
     returned for a non-deadlocked thread may bear no relationship to
     that thread's current activity by the time calling code examines
     the frame.

     This function should be used for internal and specialized purposes
     only.

     引發一個不附帶引數的*note 稽核事件: 17bd. ‘sys._current_frames’。

 -- 函式: sys._current_exceptions ()

     Return a dictionary mapping each thread's identifier to the topmost
     exception currently active in that thread at the time the function
     is called.  If a thread is not currently handling an exception, it
     is not included in the result dictionary.

     This is most useful for statistical profiling.

     This function should be used for internal and specialized purposes
     only.

     引發一個不附帶引數的*note 稽核事件: 17bd.
     ‘sys._current_exceptions’。

     在 3.12 版的變更: Each value in the dictionary is now a single
     exception instance, rather than a 3-tuple as returned from
     ‘sys.exc_info()’.

 -- 函式: sys.breakpointhook ()

     This hook function is called by built-in *note breakpoint(): 219.
     By default, it drops you into the *note pdb: 94. debugger, but it
     can be set to any other function so that you can choose which
     debugger gets used.

     The signature of this function is dependent on what it calls.  For
     example, the default binding (e.g.  ‘pdb.set_trace()’) expects no
     arguments, but you might bind it to a function that expects
     additional arguments (positional and/or keyword).  The built-in
     ‘breakpoint()’ function passes its ‘*args’ and ‘**kws’ straight
     through.  Whatever ‘breakpointhooks()’ returns is returned from
     ‘breakpoint()’.

     The default implementation first consults the environment variable
     *note PYTHONBREAKPOINT: a7e.  If that is set to ‘"0"’ then this
     function returns immediately; i.e.  it is a no-op.  If the
     environment variable is not set, or is set to the empty string,
     ‘pdb.set_trace()’ is called.  Otherwise this variable should name a
     function to run, using Python's dotted-import nomenclature, e.g.
     ‘package.subpackage.module.function’.  In this case,
     ‘package.subpackage.module’ would be imported and the resulting
     module must have a callable named ‘function()’.  This is run,
     passing in ‘*args’ and ‘**kws’, and whatever ‘function()’ returns,
     ‘sys.breakpointhook()’ returns to the built-in *note breakpoint():
     219. function.

     Note that if anything goes wrong while importing the callable named
     by *note PYTHONBREAKPOINT: a7e, a *note RuntimeWarning: 1a3. is
     reported and the breakpoint is ignored.

     Also note that if ‘sys.breakpointhook()’ is overridden
     programmatically, *note PYTHONBREAKPOINT: a7e. is 'not' consulted.

     在 3.7 版被加入.

 -- 函式: sys._debugmallocstats ()

     Print low-level information to stderr about the state of CPython's
     memory allocator.

     If Python is *note built in debug mode: 1de. (*note configure
     -with-pydebug option: 3d8.), it also performs some expensive
     internal consistency checks.

     在 3.3 版被加入.

     'CPython 實作細節：' This function is specific to CPython.  The
     exact output format is not defined here, and may change.

 -- 資料: sys.dllhandle

     Integer specifying the handle of the Python DLL.

     *note 適用: 1c56.：Windows。

 -- 函式: sys.displayhook (value)

     If 'value' is not ‘None’, this function prints ‘repr(value)’ to
     ‘sys.stdout’, and saves 'value' in ‘builtins._’.  If ‘repr(value)’
     is not encodable to ‘sys.stdout.encoding’ with ‘sys.stdout.errors’
     error handler (which is probably ‘'strict'’), encode it to
     ‘sys.stdout.encoding’ with ‘'backslashreplace'’ error handler.

     ‘sys.displayhook’ is called on the result of evaluating an *note
     expression: 1e5c. entered in an interactive Python session.  The
     display of these values can be customized by assigning another
     one-argument function to ‘sys.displayhook’.

     Pseudo-code:

          def displayhook(value):
              if value is None:
                  return
              # Set '_' to None to avoid recursion
              builtins._ = None
              text = repr(value)
              try:
                  sys.stdout.write(text)
              except UnicodeEncodeError:
                  bytes = text.encode(sys.stdout.encoding, 'backslashreplace')
                  if hasattr(sys.stdout, 'buffer'):
                      sys.stdout.buffer.write(bytes)
                  else:
                      text = bytes.decode(sys.stdout.encoding, 'strict')
                      sys.stdout.write(text)
              sys.stdout.write("\n")
              builtins._ = value

     在 3.2 版的變更: Use ‘'backslashreplace'’ error handler on *note
     UnicodeEncodeError: 61d.

 -- 資料: sys.dont_write_bytecode

     If this is true, Python won't try to write ‘.pyc’ files on the
     import of source modules.  This value is initially set to ‘True’ or
     ‘False’ depending on the *note -B: 133b. command line option and
     the *note PYTHONDONTWRITEBYTECODE: 133c. environment variable, but
     you can set it yourself to control bytecode file generation.

 -- 資料: sys._emscripten_info

     A *note named tuple: 5f4. holding information about the environment
     on the 'wasm32-emscripten' platform.  The named tuple is
     provisional and may change in the future.

      -- 屬性: _emscripten_info.emscripten_version

          Emscripten version as tuple of ints (major, minor, micro),
          e.g.  ‘(3, 1, 8)’.

      -- 屬性: _emscripten_info.runtime

          運行環境字串，例如瀏覽器使用者代理 (browser user agent)
          ‘'Node.js v14.18.2'’ 或 ‘'UNKNOWN'’。

      -- 屬性: _emscripten_info.pthreads

          ‘True’ if Python is compiled with Emscripten pthreads support.

      -- 屬性: _emscripten_info.shared_memory

          ‘True’ if Python is compiled with shared memory support.

     *note 適用: 1c56.：Emscripten。

     在 3.11 版被加入.

 -- 資料: sys.pycache_prefix

     If this is set (not ‘None’), Python will write bytecode-cache
     ‘.pyc’ files to (and read them from) a parallel directory tree
     rooted at this directory, rather than from ‘__pycache__’
     directories in the source code tree.  Any ‘__pycache__’ directories
     in the source code tree will be ignored and new ‘.pyc’ files
     written within the pycache prefix.  Thus if you use *note
     compileall: 19. as a pre-build step, you must ensure you run it
     with the same pycache prefix (if any) that you will use at runtime.

     A relative path is interpreted relative to the current working
     directory.

     This value is initially set based on the value of the *note -X:
     15a. ‘pycache_prefix=PATH’ command-line option or the *note
     PYTHONPYCACHEPREFIX: 947. environment variable (command-line takes
     precedence).  If neither are set, it is ‘None’.

     在 3.8 版被加入.

 -- 函式: sys.excepthook (type, value, traceback)

     This function prints out a given traceback and exception to
     ‘sys.stderr’.

     When an exception other than *note SystemExit: ce7. is raised and
     uncaught, the interpreter calls ‘sys.excepthook’ with three
     arguments, the exception class, exception instance, and a traceback
     object.  In an interactive session this happens just before control
     is returned to the prompt; in a Python program this happens just
     before the program exits.  The handling of such top-level
     exceptions can be customized by assigning another three-argument
     function to ‘sys.excepthook’.

     Raise an auditing event ‘sys.excepthook’ with arguments ‘hook’,
     ‘type’, ‘value’, ‘traceback’ when an uncaught exception occurs.  If
     no hook has been set, ‘hook’ may be ‘None’.  If any hook raises an
     exception derived from *note RuntimeError: 179. the call to the
     hook will be suppressed.  Otherwise, the audit hook exception will
     be reported as unraisable and ‘sys.excepthook’ will be called.

     也參考
     ......

     The *note sys.unraisablehook(): 1dc. function handles unraisable
     exceptions and the *note threading.excepthook(): 7ef. function
     handles exception raised by *note threading.Thread.run(): 9e0.

 -- 資料: sys.__breakpointhook__
 -- 資料: sys.__displayhook__
 -- 資料: sys.__excepthook__
 -- 資料: sys.__unraisablehook__

     These objects contain the original values of ‘breakpointhook’,
     ‘displayhook’, ‘excepthook’, and ‘unraisablehook’ at the start of
     the program.  They are saved so that ‘breakpointhook’,
     ‘displayhook’ and ‘excepthook’, ‘unraisablehook’ can be restored in
     case they happen to get replaced with broken or alternative
     objects.

     在 3.7 版被加入: __breakpointhook__

     在 3.8 版被加入: __unraisablehook__

 -- 函式: sys.exception ()

     This function, when called while an exception handler is executing
     (such as an ‘except’ or ‘except*’ clause), returns the exception
     instance that was caught by this handler.  When exception handlers
     are nested within one another, only the exception handled by the
     innermost handler is accessible.

     If no exception handler is executing, this function returns ‘None’.

     在 3.11 版被加入.

 -- 函式: sys.exc_info ()

     This function returns the old-style representation of the handled
     exception.  If an exception ‘e’ is currently handled (so *note
     exception(): 631. would return ‘e’), *note exc_info(): 630. returns
     the tuple ‘(type(e), e, e.__traceback__)’.  That is, a tuple
     containing the type of the exception (a subclass of *note
     BaseException: 55f.), the exception itself, and a *note traceback
     object: a97. which typically encapsulates the call stack at the
     point where the exception last occurred.

     If no exception is being handled anywhere on the stack, this
     function return a tuple containing three ‘None’ values.

     在 3.11 版的變更: The ‘type’ and ‘traceback’ fields are now derived
     from the ‘value’ (the exception instance), so when an exception is
     modified while it is being handled, the changes are reflected in
     the results of subsequent calls to *note exc_info(): 630.

 -- 資料: sys.exec_prefix

     A string giving the site-specific directory prefix where the
     platform-dependent Python files are installed; by default, this is
     also ‘'/usr/local'’.  This can be set at build time with the
     ‘--exec-prefix’ argument to the ‘configure’ script.  Specifically,
     all configuration files (e.g.  the ‘pyconfig.h’ header file) are
     installed in the directory ‘`exec_prefix'/lib/python`X.Y'/config’,
     and shared library modules are installed in
     ‘`exec_prefix'/lib/python`X.Y'/lib-dynload’, where 'X.Y' is the
     version number of Python, for example ‘3.2’.

          備註: If a *note virtual environment: 4137. is in effect, this
          value will be changed in ‘site.py’ to point to the virtual
          environment.  The value for the Python installation will still
          be available, via *note base_exec_prefix: 413b.

 -- 資料: sys.executable

     A string giving the absolute path of the executable binary for the
     Python interpreter, on systems where this makes sense.  If Python
     is unable to retrieve the real path to its executable, *note
     sys.executable: 383. will be an empty string or ‘None’.

 -- 函式: sys.exit ([arg])

     Raise a *note SystemExit: ce7. exception, signaling an intention to
     exit the interpreter.

     The optional argument 'arg' can be an integer giving the exit
     status (defaulting to zero), or another type of object.  If it is
     an integer, zero is considered "successful termination" and any
     nonzero value is considered "abnormal termination" by shells and
     the like.  Most systems require it to be in the range 0-127, and
     produce undefined results otherwise.  Some systems have a
     convention for assigning specific meanings to specific exit codes,
     but these are generally underdeveloped; Unix programs generally use
     2 for command line syntax errors and 1 for all other kind of
     errors.  If another type of object is passed, ‘None’ is equivalent
     to passing zero, and any other object is printed to *note stderr:
     8dd. and results in an exit code of 1.  In particular,
     ‘sys.exit("some error message")’ is a quick way to exit a program
     when an error occurs.

     Since *note exit(): 2066. ultimately "only" raises an exception, it
     will only exit the process when called from the main thread, and
     the exception is not intercepted.  Cleanup actions specified by
     finally clauses of *note try: 68c. statements are honored, and it
     is possible to intercept the exit attempt at an outer level.

     在 3.6 版的變更: If an error occurs in the cleanup after the Python
     interpreter has caught *note SystemExit: ce7. (such as an error
     flushing buffered data in the standard streams), the exit status is
     changed to 120.

 -- 資料: sys.flags

     The *note named tuple: 5f4. 'flags' exposes the status of command
     line flags.  The attributes are read only.

      -- 屬性: flags.debug                                  *note -d: 1c33.
                                                            
                                                            
      -- 屬性: flags.inspect                                *note -i: 144a.
                                                            
                                                            
      -- 屬性: flags.interactive                            *note -i: 144a.
                                                            
                                                            
      -- 屬性: flags.isolated                               *note -I: 902.
                                                            
                                                            
      -- 屬性: flags.optimize                               *note -O: d5b. 或 *note -OO: d5c.
                                                            
                                                            
      -- 屬性: flags.dont_write_bytecode                    *note -B: 133b.
                                                            
                                                            
      -- 屬性: flags.no_user_site                           *note -s: 1319.
                                                            
                                                            
      -- 屬性: flags.no_site                                *note -S: 1140.
                                                            
                                                            
      -- 屬性: flags.ignore_environment                     *note -E: 901.
                                                            
                                                            
      -- 屬性: flags.verbose                                *note -v: 1392.
                                                            
                                                            
      -- 屬性: flags.bytes_warning                          *note -b: 587.
                                                            
                                                            
      -- 屬性: flags.quiet                                  *note -q: 1c36.
                                                            
                                                            
      -- 屬性: flags.hash_randomization                     *note -R: 199d.
                                                            
                                                            
      -- 屬性: flags.dev_mode                               *note -X dev: 15a. （*note Python 開發模式: 1dd.）
                                                            
                                                            
      -- 屬性: flags.utf8_mode                              *note -X utf8: 15a.
                                                            
                                                            
      -- 屬性: flags.safe_path                              *note -P: 548.
                                                            
                                                            
      -- 屬性: flags.int_max_str_digits                     *note -X int_max_str_digits: 15a.
                                                            (*note integer string conversion length limitation: 599.)
                                                            
                                                            
      -- 屬性: flags.warn_default_encoding                  *note -X warn_default_encoding: 15a.
                                                            

     在 3.2 版的變更: 新增 ‘quiet’ 屬性，用於新的 *note -q: 1c36. 旗標。

     在 3.2.3 版被加入: ‘hash_randomization’ 屬性。

     在 3.3 版的變更: 移除過時的 ‘division_warning’ 屬性。

     在 3.4 版的變更: 新增 ‘isolated’ 屬性，用於 *note -I: 902.
     ‘isolated’ 旗標。

     在 3.7 版的變更: Added the ‘dev_mode’ attribute for the new *note
     Python Development Mode: 1dd. and the ‘utf8_mode’ attribute for the
     new *note -X: 15a. ‘utf8’ flag.

     在 3.10 版的變更: 新增 ‘warn_default_encoding’ 屬性，用於 *note -X:
     15a. ‘warn_default_encoding’ 旗標。

     在 3.11 版的變更: 新增 ‘safe_path’ 屬性，用於 *note -P: 548. 選項。

     在 3.11 版的變更: 新增 ‘int_max_str_digits’ 屬性。

 -- 資料: sys.float_info

     A *note named tuple: 5f4. holding information about the float type.
     It contains low level information about the precision and internal
     representation.  The values correspond to the various
     floating-point constants defined in the standard header file
     ‘float.h’ for the 'C' programming language; see section 5.2.4.2.2
     of the 1999 ISO/IEC C standard *note [C99]: 4181, 'Characteristics
     of floating types', for details.  Attributes of the ‘float_info’
     named tuple

     屬性                                  float.h macro                         解釋
                                                                                 
     ------------------------------------------------------------------------------------------------------------------
                                                                                 
      -- 屬性: float_info.epsilon          ‘DBL_EPSILON’                         difference between 1.0 and the
                                                                                 least value greater than 1.0 that
                                                                                 is representable as a float.
                                                                                 
                                                                                 另請參閱 *note math.ulp(): 8b7.。
                                                                                 
                                                                                 
      -- 屬性: float_info.dig              ‘DBL_DIG’                             The maximum number of decimal
                                                                                 digits that can be faithfully
                                                                                 represented in a float; see below.
                                                                                 
                                                                                 
      -- 屬性: float_info.mant_dig         ‘DBL_MANT_DIG’                        Float precision: the number of
                                                                                 base-‘radix’ digits in the
                                                                                 significand of a float.
                                                                                 
                                                                                 
      -- 屬性: float_info.max              ‘DBL_MAX’                             The maximum representable positive
                                                                                 finite float.
                                                                                 
                                                                                 
      -- 屬性: float_info.max_exp          ‘DBL_MAX_EXP’                         The maximum integer 'e' such that
                                                                                 ‘radix**(e-1)’ is a representable
                                                                                 finite float.
                                                                                 
                                                                                 
      -- 屬性: float_info.max_10_exp       ‘DBL_MAX_10_EXP’                      The maximum integer 'e' such that
                                                                                 ‘10**e’ is in the range of
                                                                                 representable finite floats.
                                                                                 
                                                                                 
      -- 屬性: float_info.min              ‘DBL_MIN’                             The minimum representable positive
                                                                                 'normalized' float.
                                                                                 
                                                                                 Use *note math.ulp(0.0): 8b7. to
                                                                                 get the smallest positive
                                                                                 'denormalized' representable float.
                                                                                 
                                                                                 
      -- 屬性: float_info.min_exp          ‘DBL_MIN_EXP’                         The minimum integer 'e' such that
                                                                                 ‘radix**(e-1)’ is a normalized
                                                                                 float.
                                                                                 
                                                                                 
      -- 屬性: float_info.min_10_exp       ‘DBL_MIN_10_EXP’                      The minimum integer 'e' such that
                                                                                 ‘10**e’ is a normalized float.
                                                                                 
                                                                                 
      -- 屬性: float_info.radix            ‘FLT_RADIX’                           The radix of exponent
                                                                                 representation.
                                                                                 
                                                                                 
      -- 屬性: float_info.rounds           ‘FLT_ROUNDS’                          An integer representing the
                                                                                 rounding mode for floating-point
                                                                                 arithmetic.  This reflects the
                                                                                 value of the system ‘FLT_ROUNDS’
                                                                                 macro at interpreter startup time:
                                                                                 
                                                                                    * ‘-1’: indeterminable
                                                                                 
                                                                                    * ‘0’: toward zero
                                                                                 
                                                                                    * ‘1’: to nearest
                                                                                 
                                                                                    * ‘2’: toward positive infinity
                                                                                 
                                                                                    * ‘3’: toward negative infinity
                                                                                 
                                                                                 All other values for ‘FLT_ROUNDS’
                                                                                 characterize implementation-defined
                                                                                 rounding behavior.
                                                                                 

     The attribute *note sys.float_info.dig: 4183. needs further
     explanation.  If ‘s’ is any string representing a decimal number
     with at most ‘sys.float_info.dig’ significant digits, then
     converting ‘s’ to a float and back again will recover a string
     representing the same decimal value:

          >>> import sys
          >>> sys.float_info.dig
          15
          >>> s = '3.14159265358979'    # decimal string with 15 significant digits
          >>> format(float(s), '.15g')  # convert to float and back -> same value
          '3.14159265358979'

     But for strings with more than *note sys.float_info.dig: 4183.
     significant digits, this isn't always true:

          >>> s = '9876543211234567'    # 16 significant digits is too many!
          >>> format(float(s), '.16g')  # conversion changes value
          '9876543211234568'

 -- 資料: sys.float_repr_style

     A string indicating how the *note repr(): 7a1. function behaves for
     floats.  If the string has value ‘'short'’ then for a finite float
     ‘x’, ‘repr(x)’ aims to produce a short string with the property
     that ‘float(repr(x)) == x’.  This is the usual behaviour in Python
     3.1 and later.  Otherwise, ‘float_repr_style’ has value ‘'legacy'’
     and ‘repr(x)’ behaves in the same way as it did in versions of
     Python prior to 3.1.

     在 3.1 版被加入.

 -- 函式: sys.getallocatedblocks ()

     Return the number of memory blocks currently allocated by the
     interpreter, regardless of their size.  This function is mainly
     useful for tracking and debugging memory leaks.  Because of the
     interpreter's internal caches, the result can vary from call to
     call; you may have to call *note _clear_internal_caches(): 1566.
     and *note gc.collect(): 16b. to get more predictable results.

     If a Python build or implementation cannot reasonably compute this
     information, *note getallocatedblocks(): f68. is allowed to return
     0 instead.

     在 3.4 版被加入.

 -- 函式: sys.getunicodeinternedsize ()

     Return the number of unicode objects that have been interned.

     在 3.12 版被加入.

 -- 函式: sys.getandroidapilevel ()

     Return the build-time API level of Android as an integer.  This
     represents the minimum version of Android this build of Python can
     run on.  For runtime version information, see *note
     platform.android_ver(): 1540.

     *note 適用: 1c56.：Android。

     在 3.7 版被加入.

 -- 函式: sys.getdefaultencoding ()

     Return the name of the current default string encoding used by the
     Unicode implementation.

 -- 函式: sys.getdlopenflags ()

     Return the current value of the flags that are used for ‘dlopen()’
     calls.  Symbolic names for the flag values can be found in the
     *note os: 91. module (‘RTLD_XXX’ constants, e.g.  *note
     os.RTLD_LAZY: 10b0.).

     *note 適用: 1c56.：Unix。

 -- 函式: sys.getfilesystemencoding ()

     Get the *note filesystem encoding: 4e0.: the encoding used with the
     *note filesystem error handler: 4e0. to convert between Unicode
     filenames and bytes filenames.  The filesystem error handler is
     returned from *note getfilesystemencodeerrors(): c8d.

     For best compatibility, str should be used for filenames in all
     cases, although representing filenames as bytes is also supported.
     Functions accepting or returning filenames should support either
     str or bytes and internally convert to the system's preferred
     representation.

     *note os.fsencode(): bfc. and *note os.fsdecode(): bfb. should be
     used to ensure that the correct encoding and errors mode are used.

     The *note filesystem encoding and error handler: 4e0. are
     configured at Python startup by the *note PyConfig_Read(): 734.
     function: see *note filesystem_encoding: 3b3. and *note
     filesystem_errors: 3b4. members of *note PyConfig: 371.

     在 3.2 版的變更: *note getfilesystemencoding(): c00. 的結果不再為
     ‘None’。

     在 3.6 版的變更: Windows is no longer guaranteed to return
     ‘'mbcs'’.  See PEP 529(3) and *note
     _enablelegacywindowsfsencoding(): 28e. for more information.

     在 3.7 版的變更: Return ‘'utf-8'’ if the *note Python UTF-8 Mode:
     5fc. is enabled.

 -- 函式: sys.getfilesystemencodeerrors ()

     Get the *note filesystem error handler: 4e0.: the error handler
     used with the *note filesystem encoding: 4e0. to convert between
     Unicode filenames and bytes filenames.  The filesystem encoding is
     returned from *note getfilesystemencoding(): c00.

     *note os.fsencode(): bfc. and *note os.fsdecode(): bfb. should be
     used to ensure that the correct encoding and errors mode are used.

     The *note filesystem encoding and error handler: 4e0. are
     configured at Python startup by the *note PyConfig_Read(): 734.
     function: see *note filesystem_encoding: 3b3. and *note
     filesystem_errors: 3b4. members of *note PyConfig: 371.

     在 3.6 版被加入.

 -- 函式: sys.get_int_max_str_digits ()

     Returns the current value for the *note integer string conversion
     length limitation: 599.  See also *note set_int_max_str_digits():
     16c1.

     在 3.11 版被加入.

 -- 函式: sys.getrefcount (object)

     Return the reference count of the 'object'.  The count returned is
     generally one higher than you might expect, because it includes the
     (temporary) reference as an argument to *note getrefcount(): 418f.

     Note that the returned value may not actually reflect how many
     references to the object are actually held.  For example, some
     objects are *note immortal: 4190. and have a very high refcount
     that does not reflect the actual number of references.
     Consequently, do not rely on the returned value to be accurate,
     other than a value of 0 or 1.

     在 3.12 版的變更: Immortal objects have very large refcounts that
     do not match the actual number of references to the object.

 -- 函式: sys.getrecursionlimit ()

     Return the current value of the recursion limit, the maximum depth
     of the Python interpreter stack.  This limit prevents infinite
     recursion from causing an overflow of the C stack and crashing
     Python.  It can be set by *note setrecursionlimit(): 46a.

 -- 函式: sys.getsizeof (object[, default])

     Return the size of an object in bytes.  The object can be any type
     of object.  All built-in objects will return correct results, but
     this does not have to hold true for third-party extensions as it is
     implementation specific.

     Only the memory consumption directly attributed to the object is
     accounted for, not the memory consumption of objects it refers to.

     If given, 'default' will be returned if the object does not provide
     means to retrieve the size.  Otherwise a *note TypeError: 4dd. will
     be raised.

     *note getsizeof(): 166c. calls the object's ‘__sizeof__’ method and
     adds an additional garbage collector overhead if the object is
     managed by the garbage collector.

     See recursive sizeof recipe(4) for an example of using *note
     getsizeof(): 166c. recursively to find the size of containers and
     all their contents.

 -- 函式: sys.getswitchinterval ()

     Return the interpreter's "thread switch interval"; see *note
     setswitchinterval(): 8ee.

     在 3.2 版被加入.

 -- 函式: sys._getframe ([depth])

     Return a frame object from the call stack.  If optional integer
     'depth' is given, return the frame object that many calls below the
     top of the stack.  If that is deeper than the call stack, *note
     ValueError: 1e7. is raised.  The default for 'depth' is zero,
     returning the frame at the top of the call stack.

     引發一個附帶引數 ‘frame’ 的*note 稽核事件: 17bd. ‘sys._getframe’。

     'CPython 實作細節：' This function should be used for internal and
     specialized purposes only.  It is not guaranteed to exist in all
     implementations of Python.

 -- 函式: sys._getframemodulename ([depth])

     Return the name of a module from the call stack.  If optional
     integer 'depth' is given, return the module that many calls below
     the top of the stack.  If that is deeper than the call stack, or if
     the module is unidentifiable, ‘None’ is returned.  The default for
     'depth' is zero, returning the module at the top of the call stack.

     引發一個附帶引數 ‘depth’ 的*note 稽核事件: 17bd.
     ‘sys._getframemodulename’。

     'CPython 實作細節：' This function should be used for internal and
     specialized purposes only.  It is not guaranteed to exist in all
     implementations of Python.

 -- 函式: sys.getprofile ()

     Get the profiler function as set by *note setprofile(): 146d.

 -- 函式: sys.gettrace ()

     Get the trace function as set by *note settrace(): 146e.

     'CPython 實作細節：' The *note gettrace(): 134f. function is
     intended only for implementing debuggers, profilers, coverage tools
     and the like.  Its behavior is part of the implementation platform,
     rather than part of the language definition, and thus may not be
     available in all Python implementations.

 -- 函式: sys.getwindowsversion ()

     Return a named tuple describing the Windows version currently
     running.  The named elements are 'major', 'minor', 'build',
     'platform', 'service_pack', 'service_pack_minor',
     'service_pack_major', 'suite_mask', 'product_type' and
     'platform_version'.  'service_pack' contains a string,
     'platform_version' a 3-tuple and all other values are integers.
     The components can also be accessed by name, so
     ‘sys.getwindowsversion()[0]’ is equivalent to
     ‘sys.getwindowsversion().major’.  For compatibility with prior
     versions, only the first 5 elements are retrievable by indexing.

     'platform' will be ‘2’ (VER_PLATFORM_WIN32_NT).

     'product_type' may be one of the following values:

     Constant                                    含義
                                                 
     ----------------------------------------------------------------------------------
                                                 
     ‘1’ (VER_NT_WORKSTATION)                    The system is a workstation.
                                                 
                                                 
     ‘2’ (VER_NT_DOMAIN_CONTROLLER)              The system is a domain controller.
                                                 
                                                 
     ‘3’ (VER_NT_SERVER)                         The system is a server, but not a
                                                 domain controller.
                                                 

     This function wraps the Win32 ‘GetVersionEx()’ function; see the
     Microsoft documentation on ‘OSVERSIONINFOEX()’ for more information
     about these fields.

     'platform_version' returns the major version, minor version and
     build number of the current operating system, rather than the
     version that is being emulated for the process.  It is intended for
     use in logging rather than for feature detection.

          備註: 'platform_version' derives the version from kernel32.dll
          which can be of a different version than the OS version.
          Please use *note platform: 98. module for achieving accurate
          OS version.

     *note 適用: 1c56.：Windows。

     在 3.2 版的變更: Changed to a named tuple and added
     'service_pack_minor', 'service_pack_major', 'suite_mask', and
     'product_type'.

     在 3.6 版的變更: 新增 'platform_version'

 -- 函式: sys.get_asyncgen_hooks ()

     Returns an 'asyncgen_hooks' object, which is similar to a *note
     namedtuple: 1ae. of the form ‘(firstiter, finalizer)’, where
     'firstiter' and 'finalizer' are expected to be either ‘None’ or
     functions which take an *note asynchronous generator iterator:
     4191. as an argument, and are used to schedule finalization of an
     asynchronous generator by an event loop.

     在 3.6 版被加入: 更多細節請見 PEP 525(5)。

          備註: This function has been added on a provisional basis (see
          PEP 411(6) for details.)

 -- 函式: sys.get_coroutine_origin_tracking_depth ()

     Get the current coroutine origin tracking depth, as set by *note
     set_coroutine_origin_tracking_depth(): b32.

     在 3.7 版被加入.

          備註: This function has been added on a provisional basis (see
          PEP 411(7) for details.)  Use it only for debugging purposes.

 -- 資料: sys.hash_info

     A *note named tuple: 5f4. giving parameters of the numeric hash
     implementation.  For more details about hashing of numeric types,
     see *note 數值型別的雜湊: 207d.

      -- 屬性: hash_info.width

          The width in bits used for hash values

      -- 屬性: hash_info.modulus

          The prime modulus P used for numeric hash scheme

      -- 屬性: hash_info.inf

          The hash value returned for a positive infinity

      -- 屬性: hash_info.nan

          (This attribute is no longer used)

      -- 屬性: hash_info.imag

          The multiplier used for the imaginary part of a complex number

      -- 屬性: hash_info.algorithm

          The name of the algorithm for hashing of str, bytes, and
          memoryview

      -- 屬性: hash_info.hash_bits

          The internal output size of the hash algorithm

      -- 屬性: hash_info.seed_bits

          The size of the seed key of the hash algorithm

     在 3.2 版被加入.

     在 3.4 版的變更: 新增 'algorithm'、'hash_bits' 與 'seed_bits'

 -- 資料: sys.hexversion

     The version number encoded as a single integer.  This is guaranteed
     to increase with each version, including proper support for
     non-production releases.  For example, to test that the Python
     interpreter is at least version 1.5.2, use:

          if sys.hexversion >= 0x010502F0:
              # use some advanced feature
              ...
          else:
              # use an alternative implementation or warn the user
              ...

     This is called ‘hexversion’ since it only really looks meaningful
     when viewed as the result of passing it to the built-in *note
     hex(): 1262. function.  The *note named tuple: 5f4. *note
     sys.version_info: 645. may be used for a more human-friendly
     encoding of the same information.

     More details of ‘hexversion’ can be found at *note API 和 ABI
     版本管理: 419a.

 -- 資料: sys.implementation

     An object containing information about the implementation of the
     currently running Python interpreter.  The following attributes are
     required to exist in all Python implementations.

     'name' is the implementation's identifier, e.g.  ‘'cpython'’.  The
     actual string is defined by the Python implementation, but it is
     guaranteed to be lower case.

     'version' is a named tuple, in the same format as *note
     sys.version_info: 645.  It represents the version of the Python
     'implementation'.  This has a distinct meaning from the specific
     version of the Python 'language' to which the currently running
     interpreter conforms, which ‘sys.version_info’ represents.  For
     example, for PyPy 1.8 ‘sys.implementation.version’ might be
     ‘sys.version_info(1, 8, 0, 'final', 0)’, whereas ‘sys.version_info’
     would be ‘sys.version_info(2, 7, 2, 'final', 0)’.  For CPython they
     are the same value, since it is the reference implementation.

     'hexversion' is the implementation version in hexadecimal format,
     like *note sys.hexversion: 4199.

     'cache_tag' is the tag used by the import machinery in the
     filenames of cached modules.  By convention, it would be a
     composite of the implementation's name and version, like
     ‘'cpython-33'’.  However, a Python implementation may use some
     other value if appropriate.  If ‘cache_tag’ is set to ‘None’, it
     indicates that module caching should be disabled.

     *note sys.implementation: 4bb. may contain additional attributes
     specific to the Python implementation.  These non-standard
     attributes must start with an underscore, and are not described
     here.  Regardless of its contents, *note sys.implementation: 4bb.
     will not change during a run of the interpreter, nor between
     implementation versions.  (It may change between Python language
     versions, however.)  See PEP 421(8) for more information.

     在 3.3 版被加入.

          備註: The addition of new required attributes must go through
          the normal PEP process.  See PEP 421(9) for more information.

 -- 資料: sys.int_info

     A *note named tuple: 5f4. that holds information about Python's
     internal representation of integers.  The attributes are read only.

      -- 屬性: int_info.bits_per_digit

          The number of bits held in each digit.  Python integers are
          stored internally in base ‘2**int_info.bits_per_digit’.

      -- 屬性: int_info.sizeof_digit

          The size in bytes of the C type used to represent a digit.

      -- 屬性: int_info.default_max_str_digits

          The default value for *note sys.get_int_max_str_digits():
          215a. when it is not otherwise explicitly configured.

      -- 屬性: int_info.str_digits_check_threshold

          The minimum non-zero value for *note
          sys.set_int_max_str_digits(): 16c1, *note
          PYTHONINTMAXSTRDIGITS: 16c0, or *note -X int_max_str_digits:
          15a.

     在 3.1 版被加入.

     在 3.11 版的變更: 新增 *note default_max_str_digits: 2159. 和 *note
     str_digits_check_threshold: 419d.。

 -- 資料: sys.__interactivehook__

     When this attribute exists, its value is automatically called (with
     no arguments) when the interpreter is launched in *note interactive
     mode: f69.  This is done after the *note PYTHONSTARTUP: f6b. file
     is read, so that you can set this hook there.  The *note site: b5.
     module *note sets this: f6c.

     Raises an *note auditing event: 17bd. ‘cpython.run_interactivehook’
     with the hook object as the argument when the hook is called on
     startup.

     在 3.4 版被加入.

 -- 函式: sys.intern (string)

     Enter 'string' in the table of "interned" strings and return the
     interned string - which is 'string' itself or a copy.  Interning
     strings is useful to gain a little performance on dictionary lookup
     - if the keys in a dictionary are interned, and the lookup key is
     interned, the key comparisons (after hashing) can be done by a
     pointer compare instead of a string compare.  Normally, the names
     used in Python programs are automatically interned, and the
     dictionaries used to hold module, class or instance attributes have
     interned keys.

     Interned strings are not *note immortal: 4190.; you must keep a
     reference to the return value of *note intern(): 126e. around to
     benefit from it.

 -- 函式: sys._is_gil_enabled ()

     Return *note True: bb4. if the *note GIL: 13e. is enabled and *note
     False: adb. if it is disabled.

     在 3.13 版被加入.

 -- 函式: sys.is_finalizing ()

     Return *note True: bb4. if the main Python interpreter is *note
     shutting down: 133.  Return *note False: adb. otherwise.

     See also the *note PythonFinalizationError: 132. exception.

     在 3.5 版被加入.

 -- 資料: sys.last_exc

     This variable is not always defined; it is set to the exception
     instance when an exception is not handled and the interpreter
     prints an error message and a stack traceback.  Its intended use is
     to allow an interactive user to import a debugger module and engage
     in post-mortem debugging without having to re-execute the command
     that caused the error.  (Typical use is ‘import pdb; pdb.pm()’ to
     enter the post-mortem debugger; see *note pdb: 94. module for more
     information.)

     在 3.12 版被加入.

 -- 函式: sys._is_interned (string)

     Return *note True: bb4. if the given string is "interned", *note
     False: adb. otherwise.

     在 3.13 版被加入.

     'CPython 實作細節：' It is not guaranteed to exist in all
     implementations of Python.

 -- 資料: sys.last_type
 -- 資料: sys.last_value
 -- 資料: sys.last_traceback

     These three variables are deprecated; use *note sys.last_exc: 465.
     instead.  They hold the legacy representation of ‘sys.last_exc’, as
     returned from *note exc_info(): 630. above.

 -- 資料: sys.maxsize

     An integer giving the maximum value a variable of type *note
     Py_ssize_t: a03. can take.  It's usually ‘2**31 - 1’ on a 32-bit
     platform and ‘2**63 - 1’ on a 64-bit platform.

 -- 資料: sys.maxunicode

     An integer giving the value of the largest Unicode code point, i.e.
     ‘1114111’ (‘0x10FFFF’ in hexadecimal).

     在 3.3 版的變更: Before PEP 393(10), ‘sys.maxunicode’ used to be
     either ‘0xFFFF’ or ‘0x10FFFF’, depending on the configuration
     option that specified whether Unicode characters were stored as
     UCS-2 or UCS-4.

 -- 資料: sys.meta_path

     A list of *note meta path finder: 1011. objects that have their
     *note find_spec(): 80d. methods called to see if one of the objects
     can find the module to be imported.  By default, it holds entries
     that implement Python's default import semantics.  The *note
     find_spec(): 80d. method is called with at least the absolute name
     of the module being imported.  If the module to be imported is
     contained in a package, then the parent package's *note __path__:
     1b72. attribute is passed in as a second argument.  The method
     returns a *note module spec: 419f, or ‘None’ if the module cannot
     be found.

     也參考
     ......

     *note importlib.abc.MetaPathFinder: 813.

          The abstract base class defining the interface of finder
          objects on *note meta_path: cd2.

     *note importlib.machinery.ModuleSpec: 1d5a.

          The concrete class which *note find_spec(): 80d. should return
          instances of.

     在 3.4 版的變更: *note Module specs: 419f. were introduced in
     Python 3.4, by PEP 451(11).

     在 3.12 版的變更: Removed the fallback that looked for a
     ‘find_module()’ method if a *note meta_path: cd2. entry didn't have
     a *note find_spec(): 80d. method.

 -- 資料: sys.modules

     This is a dictionary that maps module names to modules which have
     already been loaded.  This can be manipulated to force reloading of
     modules and other tricks.  However, replacing the dictionary will
     not necessarily work as expected and deleting essential items from
     the dictionary may cause Python to fail.  If you want to iterate
     over this global dictionary always use ‘sys.modules.copy()’ or
     ‘tuple(sys.modules)’ to avoid exceptions as its size may change
     during iteration as a side effect of code or activity in other
     threads.

 -- 資料: sys.orig_argv

     The list of the original command line arguments passed to the
     Python executable.

     The elements of *note sys.orig_argv: 7e4. are the arguments to the
     Python interpreter, while the elements of *note sys.argv: 11fd. are
     the arguments to the user's program.  Arguments consumed by the
     interpreter itself will be present in *note sys.orig_argv: 7e4. and
     missing from *note sys.argv: 11fd.

     在 3.10 版被加入.

 -- 資料: sys.path

     A list of strings that specifies the search path for modules.
     Initialized from the environment variable *note PYTHONPATH: fbe,
     plus an installation-dependent default.

     By default, as initialized upon program startup, a potentially
     unsafe path is prepended to *note sys.path: 37f. ('before' the
     entries inserted as a result of *note PYTHONPATH: fbe.):

        * ‘python -m module’ command line: prepend the current working
          directory.

        * ‘python script.py’ command line: prepend the script's
          directory.  If it's a symbolic link, resolve symbolic links.

        * ‘python -c code’ and ‘python’ (REPL) command lines: prepend an
          empty string, which means the current working directory.

     To not prepend this potentially unsafe path, use the *note -P: 548.
     command line option or the *note PYTHONSAFEPATH: 549. environment
     variable.

     A program is free to modify this list for its own purposes.  Only
     strings should be added to *note sys.path: 37f.; all other data
     types are ignored during import.

     也參考
     ......

        * Module *note site: b5. This describes how to use .pth files to
          extend *note sys.path: 37f.

 -- 資料: sys.path_hooks

     A list of callables that take a path argument to try to create a
     *note finder: 1eca. for the path.  If a finder can be created, it
     is to be returned by the callable, else raise *note ImportError:
     352.

     Originally specified in PEP 302(12).

 -- 資料: sys.path_importer_cache

     A dictionary acting as a cache for *note finder: 1eca. objects.
     The keys are paths that have been passed to *note sys.path_hooks:
     fc7. and the values are the finders that are found.  If a path is a
     valid file system path but no finder is found on *note
     sys.path_hooks: fc7. then ‘None’ is stored.

     Originally specified in PEP 302(13).

 -- 資料: sys.platform

     A string containing a platform identifier.  Known values are:

     System               ‘platform’ value
                          
     -----------------------------------------------------
                          
     AIX                  ‘'aix'’
                          
                          
     Android              ‘'android'’
                          
                          
     Emscripten           ‘'emscripten'’
                          
                          
     iOS                  ‘'ios'’
                          
                          
     Linux                ‘'linux'’
                          
                          
     macOS                ‘'darwin'’
                          
                          
     Windows              ‘'win32'’
                          
                          
     Windows/Cygwin       ‘'cygwin'’
                          
                          
     WASI                 ‘'wasi'’
                          

     On Unix systems not listed in the table, the value is the
     lowercased OS name as returned by ‘uname -s’, with the first part
     of the version as returned by ‘uname -r’ appended, e.g.  ‘'sunos5'’
     or ‘'freebsd8'’, 'at the time when Python was built'.  Unless you
     want to test for a specific system version, it is therefore
     recommended to use the following idiom:

          if sys.platform.startswith('freebsd'):
              # FreeBSD-specific code here...

     在 3.3 版的變更: On Linux, *note sys.platform: a30. doesn't contain
     the major version anymore.  It is always ‘'linux'’, instead of
     ‘'linux2'’ or ‘'linux3'’.

     在 3.8 版的變更: On AIX, *note sys.platform: a30. doesn't contain
     the major version anymore.  It is always ‘'aix'’, instead of
     ‘'aix5'’ or ‘'aix7'’.

     在 3.13 版的變更: On Android, *note sys.platform: a30. now returns
     ‘'android'’ rather than ‘'linux'’.

     也參考
     ......

     *note os.name: 29ed. has a coarser granularity.  *note os.uname():
     10ae. gives system-dependent version information.

     The *note platform: 98. module provides detailed checks for the
     system's identity.

 -- 資料: sys.platlibdir

     Name of the platform-specific library directory.  It is used to
     build the path of standard library and the paths of installed
     extension modules.

     It is equal to ‘"lib"’ on most platforms.  On Fedora and SuSE, it
     is equal to ‘"lib64"’ on 64-bit platforms which gives the following
     ‘sys.path’ paths (where ‘X.Y’ is the Python ‘major.minor’ version):

        * ‘/usr/lib64/pythonX.Y/’: Standard library (like ‘os.py’ of the
          *note os: 91. module)

        * ‘/usr/lib64/pythonX.Y/lib-dynload/’: C extension modules of
          the standard library (like the *note errno: 4d. module, the
          exact filename is platform specific)

        * ‘/usr/lib/pythonX.Y/site-packages/’ (always use ‘lib’, not
          *note sys.platlibdir: 8dc.): Third-party modules

        * ‘/usr/lib64/pythonX.Y/site-packages/’: C extension modules of
          third-party packages

     在 3.9 版被加入.

 -- 資料: sys.prefix

     A string giving the site-specific directory prefix where the
     platform independent Python files are installed; on Unix, the
     default is ‘/usr/local’.  This can be set at build time with the
     *note -prefix: 1c62. argument to the ‘configure’ script.  See *note
     Installation paths: 635. for derived paths.

          備註: If a *note virtual environment: 4137. is in effect, this
          value will be changed in ‘site.py’ to point to the virtual
          environment.  The value for the Python installation will still
          be available, via *note base_prefix: 3afe.

 -- 資料: sys.ps1
 -- 資料: sys.ps2

     Strings specifying the primary and secondary prompt of the
     interpreter.  These are only defined if the interpreter is in
     interactive mode.  Their initial values in this case are ‘'>>> '’
     and ‘'... '’.  If a non-string object is assigned to either
     variable, its *note str(): 3f2. is re-evaluated each time the
     interpreter prepares to read a new interactive command; this can be
     used to implement a dynamic prompt.

 -- 函式: sys.setdlopenflags (n)

     Set the flags used by the interpreter for ‘dlopen()’ calls, such as
     when the interpreter loads extension modules.  Among other things,
     this will enable a lazy resolving of symbols when importing a
     module, if called as ‘sys.setdlopenflags(0)’.  To share symbols
     across extension modules, call as
     ‘sys.setdlopenflags(os.RTLD_GLOBAL)’.  Symbolic names for the flag
     values can be found in the *note os: 91. module (‘RTLD_XXX’
     constants, e.g.  *note os.RTLD_LAZY: 10b0.).

     *note 適用: 1c56.：Unix。

 -- 函式: sys.set_int_max_str_digits (maxdigits)

     Set the *note integer string conversion length limitation: 599.
     used by this interpreter.  See also *note get_int_max_str_digits():
     215a.

     在 3.11 版被加入.

 -- 函式: sys.setprofile (profilefunc)

     Set the system's profile function, which allows you to implement a
     Python source code profiler in Python.  See chapter *note Python
     的分析器: 4088. for more information on the Python profiler.  The
     system's profile function is called similarly to the system's trace
     function (see *note settrace(): 146e.), but it is called with
     different events, for example it isn't called for each executed
     line of code (only on call and return, but the return event is
     reported even when an exception has been set).  The function is
     thread-specific, but there is no way for the profiler to know about
     context switches between threads, so it does not make sense to use
     this in the presence of multiple threads.  Also, its return value
     is not used, so it can simply return ‘None’.  Error in the profile
     function will cause itself unset.

          備註: The same tracing mechanism is used for ‘setprofile()’ as
          *note settrace(): 146e.  To trace calls with ‘setprofile()’
          inside a tracing function (e.g.  in a debugger breakpoint),
          see *note call_tracing(): 1737.

     Profile functions should have three arguments: 'frame', 'event',
     and 'arg'.  'frame' is the current stack frame.  'event' is a
     string: ‘'call'’, ‘'return'’, ‘'c_call'’, ‘'c_return'’, or
     ‘'c_exception'’.  'arg' depends on the event type.

     The events have the following meaning:

     ‘'call'’

          A function is called (or some other code block entered).  The
          profile function is called; 'arg' is ‘None’.

     ‘'return'’

          A function (or other code block) is about to return.  The
          profile function is called; 'arg' is the value that will be
          returned, or ‘None’ if the event is caused by an exception
          being raised.

     ‘'c_call'’

          A C function is about to be called.  This may be an extension
          function or a built-in.  'arg' is the C function object.

     ‘'c_return'’

          A C function has returned.  'arg' is the C function object.

     ‘'c_exception'’

          A C function has raised an exception.  'arg' is the C function
          object.

     引發一個不附帶引數的*note 稽核事件: 17bd. ‘sys.setprofile’。

 -- 函式: sys.setrecursionlimit (limit)

     Set the maximum depth of the Python interpreter stack to 'limit'.
     This limit prevents infinite recursion from causing an overflow of
     the C stack and crashing Python.

     The highest possible limit is platform-dependent.  A user may need
     to set the limit higher when they have a program that requires deep
     recursion and a platform that supports a higher limit.  This should
     be done with care, because a too-high limit can lead to a crash.

     If the new limit is too low at the current recursion depth, a *note
     RecursionError: d12. exception is raised.

     在 3.5.1 版的變更: A *note RecursionError: d12. exception is now
     raised if the new limit is too low at the current recursion depth.

 -- 函式: sys.setswitchinterval (interval)

     Set the interpreter's thread switch interval (in seconds).  This
     floating-point value determines the ideal duration of the
     "timeslices" allocated to concurrently running Python threads.
     Please note that the actual value can be higher, especially if
     long-running internal functions or methods are used.  Also, which
     thread becomes scheduled at the end of the interval is the
     operating system's decision.  The interpreter doesn't have its own
     scheduler.

     在 3.2 版被加入.

 -- 函式: sys.settrace (tracefunc)

     Set the system's trace function, which allows you to implement a
     Python source code debugger in Python.  The function is
     thread-specific; for a debugger to support multiple threads, it
     must register a trace function using *note settrace(): 146e. for
     each thread being debugged or use *note threading.settrace(): 7ec.

     Trace functions should have three arguments: 'frame', 'event', and
     'arg'.  'frame' is the current stack frame.  'event' is a string:
     ‘'call'’, ‘'line'’, ‘'return'’, ‘'exception'’ or ‘'opcode'’.  'arg'
     depends on the event type.

     The trace function is invoked (with 'event' set to ‘'call'’)
     whenever a new local scope is entered; it should return a reference
     to a local trace function to be used for the new scope, or ‘None’
     if the scope shouldn't be traced.

     The local trace function should return a reference to itself, or to
     another function which would then be used as the local trace
     function for the scope.

     If there is any error occurred in the trace function, it will be
     unset, just like ‘settrace(None)’ is called.

          備註: Tracing is disabled while calling the trace function
          (e.g.  a function set by ‘settrace()’).  For recursive tracing
          see *note call_tracing(): 1737.

     The events have the following meaning:

     ‘'call'’

          A function is called (or some other code block entered).  The
          global trace function is called; 'arg' is ‘None’; the return
          value specifies the local trace function.

     ‘'line'’

          The interpreter is about to execute a new line of code or
          re-execute the condition of a loop.  The local trace function
          is called; 'arg' is ‘None’; the return value specifies the new
          local trace function.  See ‘Objects/lnotab_notes.txt’ for a
          detailed explanation of how this works.  Per-line events may
          be disabled for a frame by setting *note f_trace_lines: b82.
          to *note False: adb. on that *note frame: 27e.

     ‘'return'’

          A function (or other code block) is about to return.  The
          local trace function is called; 'arg' is the value that will
          be returned, or ‘None’ if the event is caused by an exception
          being raised.  The trace function's return value is ignored.

     ‘'exception'’

          An exception has occurred.  The local trace function is
          called; 'arg' is a tuple ‘(exception, value, traceback)’; the
          return value specifies the new local trace function.

     ‘'opcode'’

          The interpreter is about to execute a new opcode (see *note
          dis: 30. for opcode details).  The local trace function is
          called; 'arg' is ‘None’; the return value specifies the new
          local trace function.  Per-opcode events are not emitted by
          default: they must be explicitly requested by setting *note
          f_trace_opcodes: b83. to *note True: bb4. on the *note frame:
          27e.

     Note that as an exception is propagated down the chain of callers,
     an ‘'exception'’ event is generated at each level.

     For more fine-grained usage, it's possible to set a trace function
     by assigning ‘frame.f_trace = tracefunc’ explicitly, rather than
     relying on it being set indirectly via the return value from an
     already installed trace function.  This is also required for
     activating the trace function on the current frame, which *note
     settrace(): 146e. doesn't do.  Note that in order for this to work,
     a global tracing function must have been installed with *note
     settrace(): 146e. in order to enable the runtime tracing machinery,
     but it doesn't need to be the same tracing function (e.g.  it could
     be a low overhead tracing function that simply returns ‘None’ to
     disable itself immediately on each frame).

     For more information on code and frame objects, refer to *note
     標準型別階層: 1dd6.

     引發一個不附帶引數的*note 稽核事件: 17bd. ‘sys.settrace’。

     'CPython 實作細節：' The *note settrace(): 146e. function is
     intended only for implementing debuggers, profilers, coverage tools
     and the like.  Its behavior is part of the implementation platform,
     rather than part of the language definition, and thus may not be
     available in all Python implementations.

     在 3.7 版的變更: ‘'opcode'’ event type added; *note f_trace_lines:
     b82. and *note f_trace_opcodes: b83. attributes added to frames

 -- 函式: sys.set_asyncgen_hooks ([firstiter] [, finalizer])

     Accepts two optional keyword arguments which are callables that
     accept an *note asynchronous generator iterator: 4191. as an
     argument.  The 'firstiter' callable will be called when an
     asynchronous generator is iterated for the first time.  The
     'finalizer' will be called when an asynchronous generator is about
     to be garbage collected.

     引發一個不附帶引數的*note 稽核事件: 17bd.
     ‘sys.set_asyncgen_hooks_firstiter’。

     引發一個不附帶引數的*note 稽核事件: 17bd.
     ‘sys.set_asyncgen_hooks_finalizer’。

     Two auditing events are raised because the underlying API consists
     of two calls, each of which must raise its own event.

     在 3.6 版被加入: See PEP 525(14) for more details, and for a
     reference example of a 'finalizer' method see the implementation of
     ‘asyncio.Loop.shutdown_asyncgens’ in Lib/asyncio/base_events.py(15)

          備註: This function has been added on a provisional basis (see
          PEP 411(16) for details.)

 -- 函式: sys.set_coroutine_origin_tracking_depth (depth)

     Allows enabling or disabling coroutine origin tracking.  When
     enabled, the ‘cr_origin’ attribute on coroutine objects will
     contain a tuple of (filename, line number, function name) tuples
     describing the traceback where the coroutine object was created,
     with the most recent call first.  When disabled, ‘cr_origin’ will
     be ‘None’.

     To enable, pass a 'depth' value greater than zero; this sets the
     number of frames whose information will be captured.  To disable,
     pass set 'depth' to zero.

     This setting is thread-specific.

     在 3.7 版被加入.

          備註: This function has been added on a provisional basis (see
          PEP 411(17) for details.)  Use it only for debugging purposes.

 -- 函式: sys.activate_stack_trampoline (backend, /)

     Activate the stack profiler trampoline 'backend'.  The only
     supported backend is ‘"perf"’.

     *note 適用: 1c56.：Linux。

     在 3.12 版被加入.

     也參考
     ......

        * *note Python 對 Linux perf 分析器的支援: 175.

        * ‘https://perf.wiki.kernel.org’

 -- 函式: sys.deactivate_stack_trampoline ()

     Deactivate the current stack profiler trampoline backend.

     If no stack profiler is activated, this function has no effect.

     *note 適用: 1c56.：Linux。

     在 3.12 版被加入.

 -- 函式: sys.is_stack_trampoline_active ()

     Return ‘True’ if a stack profiler trampoline is active.

     *note 適用: 1c56.：Linux。

     在 3.12 版被加入.

 -- 函式: sys._enablelegacywindowsfsencoding ()

     Changes the *note filesystem encoding and error handler: 4e0. to
     'mbcs' and 'replace' respectively, for consistency with versions of
     Python prior to 3.6.

     This is equivalent to defining the *note
     PYTHONLEGACYWINDOWSFSENCODING: 28f. environment variable before
     launching Python.

     See also *note sys.getfilesystemencoding(): c00. and *note
     sys.getfilesystemencodeerrors(): c8d.

     *note 適用: 1c56.：Windows。

          備註: Changing the filesystem encoding after Python startup is
          risky because the old fsencoding or paths encoded by the old
          fsencoding may be cached somewhere.  Use *note
          PYTHONLEGACYWINDOWSFSENCODING: 28f. instead.

     在 3.6 版被加入: 更多細節請見 PEP 529(18)。

     Deprecated since version 3.13, will be removed in version 3.16: Use
     *note PYTHONLEGACYWINDOWSFSENCODING: 28f. instead.

 -- 資料: sys.stdin
 -- 資料: sys.stdout
 -- 資料: sys.stderr

     *note File objects: 115b. used by the interpreter for standard
     input, output and errors:

        * ‘stdin’ is used for all interactive input (including calls to
          *note input(): 126b.);

        * ‘stdout’ is used for the output of *note print(): f18. and
          *note expression: 1e5c. statements and for the prompts of
          *note input(): 126b.;

        * The interpreter's own prompts and its error messages go to
          ‘stderr’.

     These streams are regular *note text files: 1b8a. like those
     returned by the *note open(): 4c0. function.  Their parameters are
     chosen as follows:

        * The encoding and error handling are is initialized from *note
          PyConfig.stdio_encoding: 36e. and *note PyConfig.stdio_errors:
          41a0.

          On Windows, UTF-8 is used for the console device.
          Non-character devices such as disk files and pipes use the
          system locale encoding (i.e.  the ANSI codepage).  Non-console
          character devices such as NUL (i.e.  where ‘isatty()’ returns
          ‘True’) use the value of the console input and output
          codepages at startup, respectively for stdin and
          stdout/stderr.  This defaults to the system *note locale
          encoding: 227. if the process is not initially attached to a
          console.

          The special behaviour of the console can be overridden by
          setting the environment variable PYTHONLEGACYWINDOWSSTDIO
          before starting Python.  In that case, the console codepages
          are used as for any other character device.

          Under all platforms, you can override the character encoding
          by setting the *note PYTHONIOENCODING: fab. environment
          variable before starting Python or by using the new *note -X:
          15a. ‘utf8’ command line option and *note PYTHONUTF8: a7b.
          environment variable.  However, for the Windows console, this
          only applies when *note PYTHONLEGACYWINDOWSSTDIO: c02. is also
          set.

        * When interactive, the ‘stdout’ stream is line-buffered.
          Otherwise, it is block-buffered like regular text files.  The
          ‘stderr’ stream is line-buffered in both cases.  You can make
          both streams unbuffered by passing the *note -u: 18a8.
          command-line option or setting the *note PYTHONUNBUFFERED:
          18a9. environment variable.

     在 3.9 版的變更: Non-interactive ‘stderr’ is now line-buffered
     instead of fully buffered.

          備註: To write or read binary data from/to the standard
          streams, use the underlying binary *note buffer: 1239. object.
          For example, to write bytes to *note stdout: a79, use
          ‘sys.stdout.buffer.write(b'abc')’.

          However, if you are writing a library (and do not control in
          which context its code will be executed), be aware that the
          standard streams may be replaced with file-like objects like
          *note io.StringIO: ecb. which do not support the ‘buffer’
          attribute.

 -- 資料: sys.__stdin__
 -- 資料: sys.__stdout__
 -- 資料: sys.__stderr__

     These objects contain the original values of ‘stdin’, ‘stderr’ and
     ‘stdout’ at the start of the program.  They are used during
     finalization, and could be useful to print to the actual standard
     stream no matter if the ‘sys.std*’ object has been redirected.

     It can also be used to restore the actual files to known working
     file objects in case they have been overwritten with a broken
     object.  However, the preferred way to do this is to explicitly
     save the previous stream before replacing it, and restore the saved
     object.

          備註: Under some conditions ‘stdin’, ‘stdout’ and ‘stderr’ as
          well as the original values ‘__stdin__’, ‘__stdout__’ and
          ‘__stderr__’ can be ‘None’.  It is usually the case for
          Windows GUI apps that aren't connected to a console and Python
          apps started with ‘pythonw’.

 -- 資料: sys.stdlib_module_names

     A frozenset of strings containing the names of standard library
     modules.

     It is the same on all platforms.  Modules which are not available
     on some platforms and modules disabled at Python build are also
     listed.  All module kinds are listed: pure Python, built-in, frozen
     and extension modules.  Test modules are excluded.

     For packages, only the main package is listed: sub-packages and
     sub-modules are not listed.  For example, the ‘email’ package is
     listed, but the ‘email.mime’ sub-package and the ‘email.message’
     sub-module are not listed.

     另請參閱 *note sys.builtin_module_names: 1b63. 清單。

     在 3.10 版被加入.

 -- 資料: sys.thread_info

     A *note named tuple: 5f4. holding information about the thread
     implementation.

      -- 屬性: thread_info.name

          The name of the thread implementation:

             * ‘"nt"’: Windows 執行緒

             * ‘"pthread"’: POSIX 執行緒

             * ‘"pthread-stubs"’: stub POSIX threads (on WebAssembly
               platforms without threading support)

             * ‘"solaris"’: Solaris threads

      -- 屬性: thread_info.lock

          The name of the lock implementation:

             * ‘"semaphore"’: a lock uses a semaphore

             * ‘"mutex+cond"’: a lock uses a mutex and a condition
               variable

             * 為 ‘None’ 表示此資訊未知

      -- 屬性: thread_info.version

          The name and version of the thread library.  It is a string,
          or ‘None’ if this information is unknown.

     在 3.3 版被加入.

 -- 資料: sys.tracebacklimit

     When this variable is set to an integer value, it determines the
     maximum number of levels of traceback information printed when an
     unhandled exception occurs.  The default is ‘1000’.  When set to
     ‘0’ or less, all traceback information is suppressed and only the
     exception type and value are printed.

 -- 函式: sys.unraisablehook (unraisable, /)

     處理一個不可被引發的例外。

     Called when an exception has occurred but there is no way for
     Python to handle it.  For example, when a destructor raises an
     exception or during garbage collection (*note gc.collect(): 16b.).

     The 'unraisable' argument has the following attributes:

        * ‘exc_type’: 例外型別。

        * ‘exc_value’: 例外值，可以為 ‘None’。

        * ‘exc_traceback’: 例外追蹤，可以為 ‘None’。

        * ‘err_msg’: 錯誤訊息，可以為 ‘None’。

        * ‘object’: 導致例外的物件，可以為 ‘None’。

     The default hook formats ‘err_msg’ and ‘object’ as: ‘f'{err_msg}:
     {object!r}'’; use "Exception ignored in" error message if ‘err_msg’
     is ‘None’.

     *note sys.unraisablehook(): 1dc. can be overridden to control how
     unraisable exceptions are handled.

     也參考
     ......

     處理未被捕捉到例外的 *note excepthook(): 7af.。

          警告: Storing ‘exc_value’ using a custom hook can create a
          reference cycle.  It should be cleared explicitly to break the
          reference cycle when the exception is no longer needed.

          Storing ‘object’ using a custom hook can resurrect it if it is
          set to an object which is being finalized.  Avoid storing
          ‘object’ after the custom hook completes to avoid resurrecting
          objects.

     Raise an auditing event ‘sys.unraisablehook’ with arguments 'hook',
     'unraisable' when an exception that cannot be handled occurs.  The
     'unraisable' object is the same as what will be passed to the hook.
     If no hook has been set, 'hook' may be ‘None’.

     在 3.8 版被加入.

 -- 資料: sys.version

     A string containing the version number of the Python interpreter
     plus additional information on the build number and compiler used.
     This string is displayed when the interactive interpreter is
     started.  Do not extract version information out of it, rather, use
     *note version_info: 645. and the functions provided by the *note
     platform: 98. module.

 -- 資料: sys.api_version

     The C API version for this interpreter.  Programmers may find this
     useful when debugging version conflicts between Python and
     extension modules.

 -- 資料: sys.version_info

     A tuple containing the five components of the version number:
     'major', 'minor', 'micro', 'releaselevel', and 'serial'.  All
     values except 'releaselevel' are integers; the release level is
     ‘'alpha'’, ‘'beta'’, ‘'candidate'’, or ‘'final'’.  The
     ‘version_info’ value corresponding to the Python version 2.0 is
     ‘(2, 0, 0, 'final', 0)’.  The components can also be accessed by
     name, so ‘sys.version_info[0]’ is equivalent to
     ‘sys.version_info.major’ and so on.

     在 3.1 版的變更: 新增了附名的元件屬性。

 -- 資料: sys.warnoptions

     This is an implementation detail of the warnings framework; do not
     modify this value.  Refer to the *note warnings: fa. module for
     more information on the warnings framework.

 -- 資料: sys.winver

     The version number used to form registry keys on Windows platforms.
     This is stored as string resource 1000 in the Python DLL. The value
     is normally the major and minor versions of the running Python
     interpreter.  It is provided in the *note sys: c3. module for
     informational purposes; modifying this value has no effect on the
     registry keys used by Python.

     *note 適用: 1c56.：Windows。

 -- 資料: sys.monitoring

     Namespace containing functions and constants for register callbacks
     and controlling monitoring events.  See *note sys.monitoring: c4.
     for details.

 -- 資料: sys._xoptions

     A dictionary of the various implementation-specific flags passed
     through the *note -X: 15a. command-line option.  Option names are
     either mapped to their values, if given explicitly, or to *note
     True: bb4.  Example:

          $ ./python -Xa=b -Xc
          Python 3.2a3+ (py3k, Oct 16 2010, 20:14:50)
          [GCC 4.4.3] on linux2
          Type "help", "copyright", "credits" or "license" for more information.
          >>> import sys
          >>> sys._xoptions
          {'a': 'b', 'c': True}

     'CPython 實作細節：' This is a CPython-specific way of accessing
     options passed through *note -X: 15a.  Other implementations may
     export them through other means, or not at all.

     在 3.2 版被加入.

引用
....

(C99) ISO/IEC 9899:1999.  "Programming languages - C." 公開草案可在以下
網址取得 ‘https://www.open-std.org/jtc1/sc22/wg14/www/docs/n1256.pdf’。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3149/

   (2) https://peps.python.org/pep-0578/

   (3) https://peps.python.org/pep-0529/

   (4) 
https://code.activestate.com/recipes/577504-compute-memory-footprint-of-an-object-and-its-cont/

   (5) https://peps.python.org/pep-0525/

   (6) https://peps.python.org/pep-0411/

   (7) https://peps.python.org/pep-0411/

   (8) https://peps.python.org/pep-0421/

   (9) https://peps.python.org/pep-0421/

   (10) https://peps.python.org/pep-0393/

   (11) https://peps.python.org/pep-0451/

   (12) https://peps.python.org/pep-0302/

   (13) https://peps.python.org/pep-0302/

   (14) https://peps.python.org/pep-0525/

   (15) 
https://github.com/python/cpython/tree/3.13/Lib/asyncio/base_events.py

   (16) https://peps.python.org/pep-0411/

   (17) https://peps.python.org/pep-0411/

   (18) https://peps.python.org/pep-0529/


File: python.info,  Node: sys monitoring --- Execution event monitoring,  Next: sysconfig --- 提供 Python 設定資訊的存取,  Prev: sys --- 系統特定的參數與函式,  Up: Python Runtime 服務

5.29.2 ‘sys.monitoring’ -- Execution event monitoring
-----------------------------------------------------

在 3.12 版被加入.

__________________________________________________________________

     備註: *note sys.monitoring: c4. is a namespace within the *note
     sys: c3. module, not an independent module, so there is no need to
     ‘import sys.monitoring’, simply ‘import sys’ and then use
     ‘sys.monitoring’.

This namespace provides access to the functions and constants necessary
to activate and control event monitoring.

As programs execute, events occur that might be of interest to tools
that monitor execution.  The *note sys.monitoring: c4. namespace
provides means to receive callbacks when events of interest occur.

The monitoring API consists of three components:

   * *note Tool identifiers: 41a9.

   * *note Events: 41aa.

   * *note 回呼 (callbacks): 41ab.

* Menu:

* Tool identifiers::
* 事件::
* Turning events on and off::
* 註冊回呼函式::


File: python.info,  Node: Tool identifiers,  Next: 事件,  Up: sys monitoring --- Execution event monitoring

5.29.2.1 Tool identifiers
.........................

A tool identifier is an integer and the associated name.  Tool
identifiers are used to discourage tools from interfering with each
other and to allow multiple tools to operate at the same time.
Currently tools are completely independent and cannot be used to monitor
each other.  This restriction may be lifted in the future.

Before registering or activating events, a tool should choose an
identifier.  Identifiers are integers in the range 0 to 5 inclusive.

* Menu:

* Registering and using tools::


File: python.info,  Node: Registering and using tools,  Up: Tool identifiers

5.29.2.2 Registering and using tools
....................................

 -- 函式: sys.monitoring.use_tool_id (tool_id: int, name: str, /) ->
          None

     Must be called before 'tool_id' can be used.  'tool_id' must be in
     the range 0 to 5 inclusive.  Raises a *note ValueError: 1e7. if
     'tool_id' is in use.

 -- 函式: sys.monitoring.free_tool_id (tool_id: int, /) -> None

     Should be called once a tool no longer requires 'tool_id'.

     備註: *note free_tool_id(): 41ae. will not disable global or local
     events associated with 'tool_id', nor will it unregister any
     callback functions.  This function is only intended to be used to
     notify the VM that the particular 'tool_id' is no longer in use.

 -- 函式: sys.monitoring.get_tool (tool_id: int, /) -> str | None

     Returns the name of the tool if 'tool_id' is in use, otherwise it
     returns ‘None’.  'tool_id' must be in the range 0 to 5 inclusive.

All IDs are treated the same by the VM with regard to events, but the
following IDs are pre-defined to make co-operation of tools easier:

     sys.monitoring.DEBUGGER_ID = 0
     sys.monitoring.COVERAGE_ID = 1
     sys.monitoring.PROFILER_ID = 2
     sys.monitoring.OPTIMIZER_ID = 5


File: python.info,  Node: 事件,  Next: Turning events on and off,  Prev: Tool identifiers,  Up: sys monitoring --- Execution event monitoring

5.29.2.3 事件
.............

The following events are supported:

 -- monitoring-event: sys.monitoring.events.BRANCH

     A conditional branch is taken (or not).

 -- monitoring-event: sys.monitoring.events.CALL

     A call in Python code (event occurs before the call).

 -- monitoring-event: sys.monitoring.events.C_RAISE

     An exception raised from any callable, except for Python functions
     (event occurs after the exit).

 -- monitoring-event: sys.monitoring.events.C_RETURN

     Return from any callable, except for Python functions (event occurs
     after the return).

 -- monitoring-event: sys.monitoring.events.EXCEPTION_HANDLED

     An exception is handled.

 -- monitoring-event: sys.monitoring.events.INSTRUCTION

     A VM instruction is about to be executed.

 -- monitoring-event: sys.monitoring.events.JUMP

     An unconditional jump in the control flow graph is made.

 -- monitoring-event: sys.monitoring.events.LINE

     An instruction is about to be executed that has a different line
     number from the preceding instruction.

 -- monitoring-event: sys.monitoring.events.PY_RESUME

     Resumption of a Python function (for generator and coroutine
     functions), except for ‘throw()’ calls.

 -- monitoring-event: sys.monitoring.events.PY_RETURN

     Return from a Python function (occurs immediately before the
     return, the callee's frame will be on the stack).

 -- monitoring-event: sys.monitoring.events.PY_START

     Start of a Python function (occurs immediately after the call, the
     callee's frame will be on the stack)

 -- monitoring-event: sys.monitoring.events.PY_THROW

     A Python function is resumed by a ‘throw()’ call.

 -- monitoring-event: sys.monitoring.events.PY_UNWIND

     Exit from a Python function during exception unwinding.

 -- monitoring-event: sys.monitoring.events.PY_YIELD

     Yield from a Python function (occurs immediately before the yield,
     the callee's frame will be on the stack).

 -- monitoring-event: sys.monitoring.events.RAISE

     An exception is raised, except those that cause a *note
     STOP_ITERATION: 41bd. event.

 -- monitoring-event: sys.monitoring.events.RERAISE

     An exception is re-raised, for example at the end of a *note
     finally: 96e. block.

 -- monitoring-event: sys.monitoring.events.STOP_ITERATION

     An artificial *note StopIteration: ba1. is raised; see *note the
     STOP_ITERATION event: 41bf.

More events may be added in the future.

These events are attributes of the ‘sys.monitoring.events’ namespace.
Each event is represented as a power-of-2 integer constant.  To define a
set of events, simply bitwise or the individual events together.  For
example, to specify both *note PY_RETURN: 41b8. and *note PY_START:
41b9. events, use the expression ‘PY_RETURN | PY_START’.

 -- monitoring-event: sys.monitoring.events.NO_EVENTS

     An alias for ‘0’ so users can do explicit comparisons like:

          if get_events(DEBUGGER_ID) == NO_EVENTS:
              ...

Events are divided into three groups:

* Menu:

* Local events::
* 輔助事件::
* 其他事件::
* The STOP_ITERATION event::


File: python.info,  Node: Local events,  Next: 輔助事件,  Up: 事件

5.29.2.4 Local events
.....................

Local events are associated with normal execution of the program and
happen at clearly defined locations.  All local events can be disabled.
The local events are:

   * *note PY_START: 41b9.

   * *note PY_RESUME: 41b7.

   * *note PY_RETURN: 41b8.

   * *note PY_YIELD: 41bc.

   * *note CALL: 153a.

   * *note LINE: 41b6.

   * *note INSTRUCTION: 41b4.

   * *note JUMP: 41b5.

   * *note BRANCH: 41b0.

   * *note STOP_ITERATION: 41bd.


File: python.info,  Node: 輔助事件,  Next: 其他事件,  Prev: Local events,  Up: 事件

5.29.2.5 輔助事件
.................

Ancillary events can be monitored like other events, but are controlled
by another event:

   * *note C_RAISE: 41b1.

   * *note C_RETURN: 41b2.

The *note C_RETURN: 41b2. and *note C_RAISE: 41b1. events are controlled
by the *note CALL: 153a. event.  *note C_RETURN: 41b2. and *note
C_RAISE: 41b1. events will only be seen if the corresponding *note CALL:
153a. event is being monitored.


File: python.info,  Node: 其他事件,  Next: The STOP_ITERATION event,  Prev: 輔助事件,  Up: 事件

5.29.2.6 其他事件
.................

Other events are not necessarily tied to a specific location in the
program and cannot be individually disabled.

The other events that can be monitored are:

   * *note PY_THROW: 41ba.

   * *note PY_UNWIND: 41bb.

   * *note RAISE: 14e2.

   * *note EXCEPTION_HANDLED: 41b3.


File: python.info,  Node: The STOP_ITERATION event,  Prev: 其他事件,  Up: 事件

5.29.2.7 The STOP_ITERATION event
.................................

PEP 380(1) specifies that a *note StopIteration: ba1. exception is
raised when returning a value from a generator or coroutine.  However,
this is a very inefficient way to return a value, so some Python
implementations, notably CPython 3.12+, do not raise an exception unless
it would be visible to other code.

To allow tools to monitor for real exceptions without slowing down
generators and coroutines, the *note STOP_ITERATION: 41bd. event is
provided.  *note STOP_ITERATION: 41bd. can be locally disabled, unlike
*note RAISE: 14e2.

   ---------- Footnotes ----------

   (1) 
https://peps.python.org/pep-0380/#use-of-stopiteration-to-return-values


File: python.info,  Node: Turning events on and off,  Next: 註冊回呼函式,  Prev: 事件,  Up: sys monitoring --- Execution event monitoring

5.29.2.8 Turning events on and off
..................................

In order to monitor an event, it must be turned on and a corresponding
callback must be registered.  Events can be turned on or off by setting
the events either globally or for a particular code object.

* Menu:

* Setting events globally::
* Per code object events::
* 停用事件::


File: python.info,  Node: Setting events globally,  Next: Per code object events,  Up: Turning events on and off

5.29.2.9 Setting events globally
................................

Events can be controlled globally by modifying the set of events being
monitored.

 -- 函式: sys.monitoring.get_events (tool_id: int, /) -> int

     Returns the ‘int’ representing all the active events.

 -- 函式: sys.monitoring.set_events (tool_id: int, event_set: int, /) ->
          None

     Activates all events which are set in 'event_set'.  Raises a *note
     ValueError: 1e7. if 'tool_id' is not in use.

No events are active by default.


File: python.info,  Node: Per code object events,  Next: 停用事件,  Prev: Setting events globally,  Up: Turning events on and off

5.29.2.10 Per code object events
................................

Events can also be controlled on a per code object basis.  The functions
defined below which accept a *note types.CodeType: 2b6. should be
prepared to accept a look-alike object from functions which are not
defined in Python (see *note Monitoring C API: 41c9.).

 -- 函式: sys.monitoring.get_local_events (tool_id: int, code: CodeType,
          /) -> int

     Returns all the local events for 'code'

 -- 函式: sys.monitoring.set_local_events (tool_id: int, code: CodeType,
          event_set: int, /) -> None

     Activates all the local events for 'code' which are set in
     'event_set'.  Raises a *note ValueError: 1e7. if 'tool_id' is not
     in use.

Local events add to global events, but do not mask them.  In other
words, all global events will trigger for a code object, regardless of
the local events.


File: python.info,  Node: 停用事件,  Prev: Per code object events,  Up: Turning events on and off

5.29.2.11 停用事件
..................

 -- 資料: sys.monitoring.DISABLE

     A special value that can be returned from a callback function to
     disable events for the current code location.

Local events can be disabled for a specific code location by returning
*note sys.monitoring.DISABLE: 41cd. from a callback function.  This does
not change which events are set, or any other code locations for the
same event.

Disabling events for specific locations is very important for high
performance monitoring.  For example, a program can be run under a
debugger with no overhead if the debugger disables all monitoring except
for a few breakpoints.

 -- 函式: sys.monitoring.restart_events () -> None

     Enable all the events that were disabled by *note
     sys.monitoring.DISABLE: 41cd. for all tools.


File: python.info,  Node: 註冊回呼函式,  Prev: Turning events on and off,  Up: sys monitoring --- Execution event monitoring

5.29.2.12 註冊回呼函式
......................

To register a callable for events call

 -- 函式: sys.monitoring.register_callback (tool_id: int, event: int,
          func: Callable | None, /) -> Callable | None

     Registers the callable 'func' for the 'event' with the given
     'tool_id'

     If another callback was registered for the given 'tool_id' and
     'event', it is unregistered and returned.  Otherwise *note
     register_callback(): 41d0. returns ‘None’.

Functions can be unregistered by calling
‘sys.monitoring.register_callback(tool_id, event, None)’.

Callback functions can be registered and unregistered at any time.

Registering or unregistering a callback function will generate a *note
sys.audit(): 1873. event.

* Menu:

* 回呼函式引數::


File: python.info,  Node: 回呼函式引數,  Up: 註冊回呼函式

5.29.2.13 回呼函式引數
......................

 -- 資料: sys.monitoring.MISSING

     A special value that is passed to a callback function to indicate
     that there are no arguments to the call.

When an active event occurs, the registered callback function is called.
Different events will provide the callback function with different
arguments, as follows:

   * *note PY_START: 41b9. 和 *note PY_RESUME: 41b7.：

          func(code: CodeType, instruction_offset: int) -> DISABLE | Any

   * *note PY_RETURN: 41b8. 和 *note PY_YIELD: 41bc.：

          func(code: CodeType, instruction_offset: int, retval: object) -> DISABLE | Any

   * *note CALL: 153a.、*note C_RAISE: 41b1. 和 *note C_RETURN: 41b2.：

          func(code: CodeType, instruction_offset: int, callable: object, arg0: object | MISSING) -> DISABLE | Any

     If there are no arguments, 'arg0' is set to *note
     sys.monitoring.MISSING: 41d2.

   * *note RAISE: 14e2.、*note RERAISE: 41be.、*note EXCEPTION_HANDLED:
     41b3.、*note PY_UNWIND: 41bb.、*note PY_THROW: 41ba. 和 *note
     STOP_ITERATION: 41bd.：

          func(code: CodeType, instruction_offset: int, exception: BaseException) -> DISABLE | Any

   * *note LINE: 41b6.：

          func(code: CodeType, line_number: int) -> DISABLE | Any

   * *note BRANCH: 41b0. 和 *note JUMP: 41b5.：

          func(code: CodeType, instruction_offset: int, destination_offset: int) -> DISABLE | Any

     Note that the 'destination_offset' is where the code will next
     execute.  For an untaken branch this will be the offset of the
     instruction following the branch.

   * *note INSTRUCTION: 41b4.：

          func(code: CodeType, instruction_offset: int) -> DISABLE | Any


File: python.info,  Node: sysconfig --- 提供 Python 設定資訊的存取,  Next: builtins --- 內建物件,  Prev: sys monitoring --- Execution event monitoring,  Up: Python Runtime 服務

5.29.3 ‘sysconfig’ -- 提供 Python 設定資訊的存取
------------------------------------------------

在 3.2 版被加入.

'Source code:' Lib/sysconfig(1)

__________________________________________________________________

The *note sysconfig: c5. module provides access to Python's
configuration information like the list of installation paths and the
configuration variables relevant for the current platform.

* Menu:

* Configuration variables::
* Installation paths::
* User scheme::
* Home scheme::
* Prefix scheme::
* 安裝路徑函式::
* 其他函式: 其他函式<3>.
* 將 sysconfig 作為腳本使用::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/sysconfig


File: python.info,  Node: Configuration variables,  Next: Installation paths,  Up: sysconfig --- 提供 Python 設定資訊的存取

5.29.3.1 Configuration variables
................................

A Python distribution contains a ‘Makefile’ and a ‘pyconfig.h’ header
file that are necessary to build both the Python binary itself and
third-party C extensions compiled using ‘setuptools’.

*note sysconfig: c5. puts all variables found in these files in a
dictionary that can be accessed using *note get_config_vars(): fcf. or
*note get_config_var(): fce.

Notice that on Windows, it's a much smaller set.

 -- 函式: sysconfig.get_config_vars (*args)

     With no arguments, return a dictionary of all configuration
     variables relevant for the current platform.

     With arguments, return a list of values that result from looking up
     each argument in the configuration variable dictionary.

     For each argument, if the value is not found, return ‘None’.

 -- 函式: sysconfig.get_config_var (name)

     Return the value of a single variable 'name'.  Equivalent to
     ‘get_config_vars().get(name)’.

     If 'name' is not found, return ‘None’.

用法範例：

     >>> import sysconfig
     >>> sysconfig.get_config_var('Py_ENABLE_SHARED')
     0
     >>> sysconfig.get_config_var('LIBDIR')
     '/usr/local/lib'
     >>> sysconfig.get_config_vars('AR', 'CXX')
     ['ar', 'g++']


File: python.info,  Node: Installation paths,  Next: User scheme,  Prev: Configuration variables,  Up: sysconfig --- 提供 Python 設定資訊的存取

5.29.3.2 Installation paths
...........................

Python uses an installation scheme that differs depending on the
platform and on the installation options.  These schemes are stored in
*note sysconfig: c5. under unique identifiers based on the value
returned by *note os.name: 29ed.  The schemes are used by package
installers to determine where to copy files to.

Python currently supports nine schemes:

   - 'posix_prefix': scheme for POSIX platforms like Linux or macOS.
     This is the default scheme used when Python or a component is
     installed.

   - 'posix_home': scheme for POSIX platforms, when the 'home' option is
     used.  This scheme defines paths located under a specific home
     prefix.

   - 'posix_user': scheme for POSIX platforms, when the 'user' option is
     used.  This scheme defines paths located under the user's home
     directory (*note site.USER_BASE: 12b0.).

   - 'posix_venv': scheme for *note Python virtual environments: f9. on
     POSIX platforms; by default it is the same as 'posix_prefix'.

   - 'nt': scheme for Windows.  This is the default scheme used when
     Python or a component is installed.

   - 'nt_user': scheme for Windows, when the 'user' option is used.

   - 'nt_venv': scheme for *note Python virtual environments: f9. on
     Windows; by default it is the same as 'nt'.

   - 'venv': a scheme with values from either 'posix_venv' or 'nt_venv'
     depending on the platform Python runs on.

   - 'osx_framework_user': scheme for macOS, when the 'user' option is
     used.

Each scheme is itself composed of a series of paths and each path has a
unique identifier.  Python currently uses eight paths:

   - 'stdlib': directory containing the standard Python library files
     that are not platform-specific.

   - 'platstdlib': directory containing the standard Python library
     files that are platform-specific.

   - 'platlib': directory for site-specific, platform-specific files.

   - 'purelib': directory for site-specific, non-platform-specific files
     ('pure' Python).

   - 'include': directory for non-platform-specific header files for the
     Python C-API.

   - 'platinclude': directory for platform-specific header files for the
     Python C-API.

   - 'scripts': directory for script files.

   - 'data': directory for data files.


File: python.info,  Node: User scheme,  Next: Home scheme,  Prev: Installation paths,  Up: sysconfig --- 提供 Python 設定資訊的存取

5.29.3.3 User scheme
....................

This scheme is designed to be the most convenient solution for users
that don't have write permission to the global site-packages directory
or don't want to install into it.

Files will be installed into subdirectories of *note site.USER_BASE:
12b0. (written as ‘`userbase'’ hereafter).  This scheme installs pure
Python modules and extension modules in the same location (also known as
*note site.USER_SITE: 1c37.).

* Menu:

* posix_user::
* nt_user::
* osx_framework_user::


File: python.info,  Node: posix_user,  Next: nt_user,  Up: User scheme

5.29.3.4 ‘posix_user’
.....................

Path               Installation directory
                   
-----------------------------------------------------------------------------------
                   
'stdlib'           ‘`userbase'/lib/python`X.Y'’
                   
                   
'platstdlib'       ‘`userbase'/lib/python`X.Y'’
                   
                   
'platlib'          ‘`userbase'/lib/python`X.Y'/site-packages’
                   
                   
'purelib'          ‘`userbase'/lib/python`X.Y'/site-packages’
                   
                   
'include'          ‘`userbase'/include/python`X.Y'’
                   
                   
'scripts'          ‘`userbase'/bin’
                   
                   
'data'             ‘`userbase'’
                   


File: python.info,  Node: nt_user,  Next: osx_framework_user,  Prev: posix_user,  Up: User scheme

5.29.3.5 ‘nt_user’
..................

Path               Installation directory
                   
-----------------------------------------------------------------------------------
                   
'stdlib'           ‘`userbase'\Python`XY'’
                   
                   
'platstdlib'       ‘`userbase'\Python`XY'’
                   
                   
'platlib'          ‘`userbase'\Python`XY'\site-packages’
                   
                   
'purelib'          ‘`userbase'\Python`XY'\site-packages’
                   
                   
'include'          ‘`userbase'\Python`XY'\Include’
                   
                   
'scripts'          ‘`userbase'\Python`XY'\Scripts’
                   
                   
'data'             ‘`userbase'’
                   


File: python.info,  Node: osx_framework_user,  Prev: nt_user,  Up: User scheme

5.29.3.6 ‘osx_framework_user’
.............................

Path               Installation directory
                   
-----------------------------------------------------------------------------------
                   
'stdlib'           ‘`userbase'/lib/python’
                   
                   
'platstdlib'       ‘`userbase'/lib/python’
                   
                   
'platlib'          ‘`userbase'/lib/python/site-packages’
                   
                   
'purelib'          ‘`userbase'/lib/python/site-packages’
                   
                   
'include'          ‘`userbase'/include/python`X.Y'’
                   
                   
'scripts'          ‘`userbase'/bin’
                   
                   
'data'             ‘`userbase'’
                   


File: python.info,  Node: Home scheme,  Next: Prefix scheme,  Prev: User scheme,  Up: sysconfig --- 提供 Python 設定資訊的存取

5.29.3.7 Home scheme
....................

The idea behind the "home scheme" is that you build and maintain a
personal stash of Python modules.  This scheme's name is derived from
the idea of a "home" directory on Unix, since it's not unusual for a
Unix user to make their home directory have a layout similar to ‘/usr/’
or ‘/usr/local/’.  This scheme can be used by anyone, regardless of the
operating system they are installing for.

* Menu:

* posix_home::


File: python.info,  Node: posix_home,  Up: Home scheme

5.29.3.8 ‘posix_home’
.....................

Path               Installation directory
                   
-----------------------------------------------------------------------------------
                   
'stdlib'           ‘`home'/lib/python’
                   
                   
'platstdlib'       ‘`home'/lib/python’
                   
                   
'platlib'          ‘`home'/lib/python’
                   
                   
'purelib'          ‘`home'/lib/python’
                   
                   
'include'          ‘`home'/include/python’
                   
                   
'platinclude'      ‘`home'/include/python’
                   
                   
'scripts'          ‘`home'/bin’
                   
                   
'data'             ‘`home'’
                   


File: python.info,  Node: Prefix scheme,  Next: 安裝路徑函式,  Prev: Home scheme,  Up: sysconfig --- 提供 Python 設定資訊的存取

5.29.3.9 Prefix scheme
......................

The "prefix scheme" is useful when you wish to use one Python
installation to perform the build/install (i.e., to run the setup
script), but install modules into the third-party module directory of a
different Python installation (or something that looks like a different
Python installation).  If this sounds a trifle unusual, it is--that's
why the user and home schemes come before.  However, there are at least
two known cases where the prefix scheme will be useful.

First, consider that many Linux distributions put Python in ‘/usr’,
rather than the more traditional ‘/usr/local’.  This is entirely
appropriate, since in those cases Python is part of "the system" rather
than a local add-on.  However, if you are installing Python modules from
source, you probably want them to go in ‘/usr/local/lib/python2.`X'’
rather than ‘/usr/lib/python2.`X'’.

Another possibility is a network filesystem where the name used to write
to a remote directory is different from the name used to read it: for
example, the Python interpreter accessed as ‘/usr/local/bin/python’
might search for modules in ‘/usr/local/lib/python2.`X'’, but those
modules would have to be installed to, say,
‘/mnt/`@server'/export/lib/python2.`X'’.

* Menu:

* posix_prefix::
* nt::


File: python.info,  Node: posix_prefix,  Next: nt,  Up: Prefix scheme

5.29.3.10 ‘posix_prefix’
........................

Path               Installation directory
                   
----------------------------------------------------------------------------------
                   
'stdlib'           ‘`prefix'/lib/python`X.Y'’
                   
                   
'platstdlib'       ‘`prefix'/lib/python`X.Y'’
                   
                   
'platlib'          ‘`prefix'/lib/python`X.Y'/site-packages’
                   
                   
'purelib'          ‘`prefix'/lib/python`X.Y'/site-packages’
                   
                   
'include'          ‘`prefix'/include/python`X.Y'’
                   
                   
'platinclude'      ‘`prefix'/include/python`X.Y'’
                   
                   
'scripts'          ‘`prefix'/bin’
                   
                   
'data'             ‘`prefix'’
                   


File: python.info,  Node: nt,  Prev: posix_prefix,  Up: Prefix scheme

5.29.3.11 ‘nt’
..............

Path               Installation directory
                   
----------------------------------------------------------------------------------
                   
'stdlib'           ‘`prefix'\Lib’
                   
                   
'platstdlib'       ‘`prefix'\Lib’
                   
                   
'platlib'          ‘`prefix'\Lib\site-packages’
                   
                   
'purelib'          ‘`prefix'\Lib\site-packages’
                   
                   
'include'          ‘`prefix'\Include’
                   
                   
'platinclude'      ‘`prefix'\Include’
                   
                   
'scripts'          ‘`prefix'\Scripts’
                   
                   
'data'             ‘`prefix'’
                   


File: python.info,  Node: 安裝路徑函式,  Next: 其他函式<3>,  Prev: Prefix scheme,  Up: sysconfig --- 提供 Python 設定資訊的存取

5.29.3.12 安裝路徑函式
......................

*note sysconfig: c5. provides some functions to determine these
installation paths.

 -- 函式: sysconfig.get_scheme_names ()

     Return a tuple containing all schemes currently supported in *note
     sysconfig: c5.

 -- 函式: sysconfig.get_default_scheme ()

     Return the default scheme name for the current platform.

     在 3.10 版被加入: This function was previously named
     ‘_get_default_scheme()’ and considered an implementation detail.

     在 3.11 版的變更: When Python runs from a virtual environment, the
     'venv' scheme is returned.

 -- 函式: sysconfig.get_preferred_scheme (key)

     Return a preferred scheme name for an installation layout specified
     by 'key'.

     'key' must be either ‘"prefix"’, ‘"home"’, or ‘"user"’.

     The return value is a scheme name listed in *note
     get_scheme_names(): 41e3.  It can be passed to *note sysconfig: c5.
     functions that take a 'scheme' argument, such as *note get_paths():
     11dc.

     在 3.10 版被加入.

     在 3.11 版的變更: When Python runs from a virtual environment and
     ‘key="prefix"’, the 'venv' scheme is returned.

 -- 函式: sysconfig._get_preferred_schemes ()

     Return a dict containing preferred scheme names on the current
     platform.  Python implementers and redistributors may add their
     preferred schemes to the ‘_INSTALL_SCHEMES’ module-level global
     value, and modify this function to return those scheme names, to
     e.g.  provide different schemes for system and language package
     managers to use, so packages installed by either do not mix with
     those by the other.

     End users should not use this function, but *note
     get_default_scheme(): 1728. and *note get_preferred_scheme(): 636.
     instead.

     在 3.10 版被加入.

 -- 函式: sysconfig.get_path_names ()

     Return a tuple containing all path names currently supported in
     *note sysconfig: c5.

 -- 函式: sysconfig.get_path (name[, scheme[, vars[, expand]]])

     Return an installation path corresponding to the path 'name', from
     the install scheme named 'scheme'.

     'name' has to be a value from the list returned by *note
     get_path_names(): 41e5.

     *note sysconfig: c5. stores installation paths corresponding to
     each path name, for each platform, with variables to be expanded.
     For instance the 'stdlib' path for the 'nt' scheme is:
     ‘{base}/Lib’.

     *note get_path(): 12c2. will use the variables returned by *note
     get_config_vars(): fcf. to expand the path.  All variables have
     default values for each platform so one may call this function and
     get the default value.

     If 'scheme' is provided, it must be a value from the list returned
     by *note get_scheme_names(): 41e3.  Otherwise, the default scheme
     for the current platform is used.

     If 'vars' is provided, it must be a dictionary of variables that
     will update the dictionary returned by *note get_config_vars():
     fcf.

     If 'expand' is set to ‘False’, the path will not be expanded using
     the variables.

     如果找不到 'name'，則引發 *note KeyError: 2fb.。

 -- 函式: sysconfig.get_paths ([scheme[, vars[, expand]]])

     Return a dictionary containing all installation paths corresponding
     to an installation scheme.  See *note get_path(): 12c2. for more
     information.

     If 'scheme' is not provided, will use the default scheme for the
     current platform.

     If 'vars' is provided, it must be a dictionary of variables that
     will update the dictionary used to expand the paths.

     If 'expand' is set to false, the paths will not be expanded.

     If 'scheme' is not an existing scheme, *note get_paths(): 11dc.
     will raise a *note KeyError: 2fb.


File: python.info,  Node: 其他函式<3>,  Next: 將 sysconfig 作為腳本使用,  Prev: 安裝路徑函式,  Up: sysconfig --- 提供 Python 設定資訊的存取

5.29.3.13 其他函式
..................

 -- 函式: sysconfig.get_python_version ()

     回傳 ‘MAJOR.MINOR’ Python 版本號碼字串。類似於 ‘'%d.%d' %
     sys.version_info[:2]’。

 -- 函式: sysconfig.get_platform ()

     Return a string that identifies the current platform.

     This is used mainly to distinguish platform-specific build
     directories and platform-specific built distributions.  Typically
     includes the OS name and version and the architecture (as supplied
     by *note os.uname(): 10ae.), although the exact information
     included depends on the OS; e.g., on Linux, the kernel version
     isn't particularly important.

     Examples of returned values:

        - linux-i586

        - linux-alpha (?)

        - solaris-2.6-sun4u

     Windows will return one of:

        - win-amd64 (64bit Windows on AMD64, aka x86_64, Intel64, and
          EM64T)

        - win32 (all others - specifically, sys.platform is returned)

     macOS can return:

        - macosx-10.6-ppc

        - macosx-10.4-ppc64

        - macosx-10.3-i386

        - macosx-10.4-fat

     For other non-POSIX platforms, currently just returns *note
     sys.platform: a30.

 -- 函式: sysconfig.is_python_build ()

     Return ‘True’ if the running Python interpreter was built from
     source and is being run from its built location, and not from a
     location resulting from e.g.  running ‘make install’ or installing
     via a binary installer.

 -- 函式: sysconfig.parse_config_h (fp[, vars])

     Parse a ‘config.h’-style file.

     'fp' is a file-like object pointing to the ‘config.h’-like file.

     A dictionary containing name/value pairs is returned.  If an
     optional dictionary is passed in as the second argument, it is used
     instead of a new dictionary, and updated with the values read in
     the file.

 -- 函式: sysconfig.get_config_h_filename ()

     回傳 ‘pyconfig.h’ 的路徑。

 -- 函式: sysconfig.get_makefile_filename ()

     回傳 ‘Makefile’ 的路徑。


File: python.info,  Node: 將 sysconfig 作為腳本使用,  Prev: 其他函式<3>,  Up: sysconfig --- 提供 Python 設定資訊的存取

5.29.3.14 將 ‘sysconfig’ 作為腳本使用
.....................................

You can use *note sysconfig: c5. as a script with Python's '-m' option:

     $ python -m sysconfig
     Platform: "macosx-10.4-i386"
     Python version: "3.2"
     Current installation scheme: "posix_prefix"

     Paths:
             data = "/usr/local"
             include = "/Users/tarek/Dev/svn.python.org/py3k/Include"
             platinclude = "."
             platlib = "/usr/local/lib/python3.2/site-packages"
             platstdlib = "/usr/local/lib/python3.2"
             purelib = "/usr/local/lib/python3.2/site-packages"
             scripts = "/usr/local/bin"
             stdlib = "/usr/local/lib/python3.2"

     Variables:
             AC_APPLE_UNIVERSAL_BUILD = "0"
             AIX_GENUINE_CPLUSPLUS = "0"
             AR = "ar"
             ARFLAGS = "rc"
             ...

This call will print in the standard output the information returned by
*note get_platform(): 11da, *note get_python_version(): 11db, *note
get_path(): 12c2. and *note get_config_vars(): fcf.


File: python.info,  Node: builtins --- 內建物件,  Next: __main__ --- 頂層程式碼環境,  Prev: sysconfig --- 提供 Python 設定資訊的存取,  Up: Python Runtime 服務

5.29.4 ‘builtins’ -- 內建物件
-----------------------------

__________________________________________________________________

該模組提供對 Python 所有'內建'識別符號的直接存取；例如 ‘builtins.open’ 是
內建函式 *note open(): 4c0. 的全名。請參閱*note 內建函式: 11f5.和*note
內建常數: 2061.的文件。

大多數應用程式通常不會顯式地存取此模組，但在提供與內建值同名之物件的模組
中可能很有用，不過其中還會需要內建該名稱。例如，在一個將內建 *note
open(): 4c0. 包裝起來以實現另一版本 *note open(): 4c0. 函式的模組中，這
個模組可以直接被使用：

     import builtins

     def open(path):
         f = builtins.open(path, 'r')
         return UpperCaser(f)

     class UpperCaser:
         '''Wrapper around a file that converts output to uppercase.'''

         def __init__(self, f):
             self._f = f

         def read(self, count=-1):
             return self._f.read(count).upper()

         # ...

有個實作細節是，大多數模組都將名稱 ‘__builtins__’ 作為其全域性變數的一部
分以提使用。‘__builtins__’ 的值通常是這個模組或者這個模組的 *note
__dict__: c04. 屬性值。由於這是一個實作細節，因此 Python 的其他實作可能
不會使用它。


File: python.info,  Node: __main__ --- 頂層程式碼環境,  Next: warnings --- 警告控制,  Prev: builtins --- 內建物件,  Up: Python Runtime 服務

5.29.5 ‘__main__’ -- 頂層程式碼環境
-----------------------------------

__________________________________________________________________

在 Python 中，特殊名稱 ‘__main__’ 用於兩個重要的建構：

  1. 程式頂層環境的名稱，可以使用 ‘__name__ == '__main__'’ 運算式進行檢
     查；和

  2. 在 Python 套件中的 ‘__main__.py’ 檔案。

這兩種機制都與 Python 模組有關；使用者如何與它們互動以及它們如何彼此互動
。下面會詳細解釋它們。如果你不熟悉 Python 模組，請參閱教學章節 *note 模組
(Module): 1b5a. 的介紹。

* Menu:

* __name__ == '__main__'::
* Python 套件中的 __main__.py: Python 套件中的 __main__ py.
* import __main__::


File: python.info,  Node: __name__ == '__main__',  Next: Python 套件中的 __main__ py,  Up: __main__ --- 頂層程式碼環境

5.29.5.1 ‘__name__ == '__main__'’
.................................

當引入 Python 模組或套件時，‘__name__’ 設定為模組的名稱。通常來說，這是
Python 檔案本身的名稱，且不含 .py 副檔名：

     >>> import configparser
     >>> configparser.__name__
     'configparser'

如果檔案是套件的一部分，則 ‘__name__’ 也會包含父套件 (parent package) 的
路徑：

     >>> from concurrent.futures import process
     >>> process.__name__
     'concurrent.futures.process'

但是，如果模組在頂層程式碼環境中執行，則其 ‘__name__’ 將被設定為字串
‘'__main__'’。

* Menu:

* 什麼是「頂層程式碼環境」？::
* 慣用 (Idiomatic) 用法: 慣用 Idiomatic 用法.
* 打包時須考慮的事情::


File: python.info,  Node: 什麼是「頂層程式碼環境」？,  Next: 慣用 Idiomatic 用法,  Up: __name__ == '__main__'

5.29.5.2 什麼是「頂層程式碼環境」？
...................................

‘__main__’ 是執行頂層程式碼的環境名稱。「頂層程式碼」是使用者指定且第一
個開始運作的 Python 模組。它是「頂層」的原因是因為它引入程式所需的所有其
他模組。有時「頂層程式碼」被稱為應用程式的'入口點'。

頂層程式碼環境可以是：

   * 互動式提示字元的作用域：

          >>> __name__
          '__main__'

   * 將 Python 模組作為檔案引數傳遞給 Python 直譯器：

          $ python helloworld.py
          Hello, world!

   * 使用 *note -m: 585. 引數傳遞給 Python 直譯器的 Python 模組或套件：

          $ python -m tarfile
          usage: tarfile.py [-h] [-v] (...)

   * Python 直譯器從標準輸入讀取 Python 程式碼：

          $ echo "import this" | python
          The Zen of Python, by Tim Peters

          Beautiful is better than ugly.
          Explicit is better than implicit.
          ...

   * 使用 *note -c: 584. 引數傳遞給 Python 直譯器的 Python 程式碼：

          $ python -c "import this"
          The Zen of Python, by Tim Peters

          Beautiful is better than ugly.
          Explicit is better than implicit.
          ...

在這些情況下，頂層模組的 ‘__name__’ 都會設定為 ‘'__main__'’。

因此，模組可以透過檢查自己的 ‘__name__’ 來發現它是否在頂層環境中執行，這
允許當模組未從 import 陳述式初始化時，使用常見的慣用語法 (idiom) 來有條
件地執行程式碼：

     if __name__ == '__main__':
         # Execute when the module is not initialized from an import statement.
         ...

也參考
......

若要更詳細地了解如何在所有情況下設定 ‘__name__’，請參閱教學章節 *note
模組 (Module): 1b5a.。


File: python.info,  Node: 慣用 Idiomatic 用法,  Next: 打包時須考慮的事情,  Prev: 什麼是「頂層程式碼環境」？,  Up: __name__ == '__main__'

5.29.5.3 慣用 (Idiomatic) 用法
..............................

某些模組包含僅供腳本使用的程式碼，例如剖析命令列引數或從標準輸入取得資料
。如果從不同的模組匯入這樣的模組（例如對其進行單元測試 (unit test)），則
腳本程式碼也會無意間執行。

這就是使用 ‘if __name__ == '__main__'’ 程式碼區塊派上用場的地方。除非該
模組在頂層環境中執行，否則此區塊中的程式碼不會執行。

在 ‘if __name__ == '__main__'’ 下面的區塊中放置盡可能少的陳述式可以提高
程式碼的清晰度和正確性。大多數情況下，名為 ‘main’ 的函式封裝
(encapsulate) 了程式的主要行為：

     # echo.py

     import shlex
     import sys

     def echo(phrase: str) -> None:
        """A dummy wrapper around print."""
        # for demonstration purposes, you can imagine that there is some
        # valuable and reusable logic inside this function
        print(phrase)

     def main() -> int:
         """Echo the input arguments to standard output"""
         phrase = shlex.join(sys.argv)
         echo(phrase)
         return 0

     if __name__ == '__main__':
         sys.exit(main())  # next section explains the use of sys.exit

請注意，如果模組沒有將程式碼封裝在 ‘main’ 函式中，而是直接將其放在 ‘if
__name__ == '__main__'’ 區塊中，則 ‘phrase’ 變數對於整個模組來說將是全域
的。這很容易出錯，因為模組中的其他函式可能會無意中使用此全域變數而不是區
域變數。‘main’ 函式解決了這個問題。

使用 ‘main’ 函式還有一個額外的好處，‘echo’ 函式本身是隔離的 (isolated) 並
且可以在其他地方引入。當引入 ‘echo.py’ 時，‘echo’ 和 ‘main’ 函式將被定義
，但它們都不會被呼叫，因為 ‘__name__ != '__main__'’。


File: python.info,  Node: 打包時須考慮的事情,  Prev: 慣用 Idiomatic 用法,  Up: __name__ == '__main__'

5.29.5.4 打包時須考慮的事情
...........................

‘main’ 函式通常用於透過將它們指定為控制台腳本的入口點來建立命令列工具。
完成後，pip(1) 將函式呼叫插入到模板腳本中，其中 ‘main’ 的回傳值被傳遞到
*note sys.exit(): 12dd. 中。例如：

     sys.exit(main())

由於對 ‘main’ 的呼叫包含在 *note sys.exit(): 12dd. 中，因此期望你的函式
將傳回一些可接受作為 *note sys.exit(): 12dd. 輸入的值；通常來說，會是一
個整數或 ‘None’（如果你的函式沒有 return 陳述式，則相當於回傳此值）。

透過我們自己主動遵循這個慣例，我們的模組在直接執行時（即 ‘python
echo.py’）的行為，將和我們稍後將其打包為 pip 可安裝套件中的控制台腳本入
口點相同。

特別是，要謹慎處理從 ‘main’ 函式回傳字串。*note sys.exit(): 12dd. 會將字
串引數直譯為失敗訊息，因此你的程式將有一個表示失敗的結束代碼 ‘1’，並且該
字串將被寫入 *note sys.stderr: 8dd.。前面的 ‘echo.py’ 範例使用慣例的
‘sys.exit(main())’ 進行示範。

也參考
......

Python 打包使用者指南(2)包含一系列如何使用現代工具發行和安裝 Python 套件
的教學和參考資料。

   ---------- Footnotes ----------

   (1) https://pip.pypa.io/

   (2) https://packaging.python.org/


File: python.info,  Node: Python 套件中的 __main__ py,  Next: import __main__,  Prev: __name__ == '__main__',  Up: __main__ --- 頂層程式碼環境

5.29.5.5 Python 套件中的 ‘__main__.py’
......................................

如果你不熟悉 Python 套件，請參閱 *note 套件 (Package): 1b6b. 的教學章節
。最常見的是，‘__main__.py’ 檔案用於為套件提供命令列介面。假設下面有虛構
的套件 "bandclass"：

     bandclass
       ├── __init__.py
       ├── __main__.py
       └── student.py

當使用 *note -m: 585. 旗標 (flag) 直接從命令列呼叫套件本身時，將執行
‘__main__.py’。例如：

     $ python -m bandclass

該命令將導致 ‘__main__.py’ 執行。如何利用此機制將取決於你正在編寫的套件
的性質，但在這種虛構的情況下，允許教師搜尋學生可能是有意義的：

     # bandclass/__main__.py

     import sys
     from .student import search_students

     student_name = sys.argv[1] if len(sys.argv) >= 2 else ''
     print(f'Found student: {search_students(student_name)}')

請注意，‘from .student import search_students’ 是相對引入的範例。在引用
套件內的模組時，可以使用此引入樣式。有關更多詳細資訊，請參閱 *note 模組
(Module): 1b5a. 教學章節中的 *note 套件內引用: 1b70.。

* Menu:

* 慣用 (Idiomatic) 用法: 慣用 Idiomatic 用法<2>.


File: python.info,  Node: 慣用 Idiomatic 用法<2>,  Up: Python 套件中的 __main__ py

5.29.5.6 慣用 (Idiomatic) 用法
..............................

‘__main__.py’ 的內容通常不會被 ‘if __name__ == '__main__'’ 區塊包圍。相
反的，這些檔案保持簡短並引入其他模組的函式來執行。那些其他模組就可以輕鬆
地進行單元測試並且可以正確地重複使用。

如果在套件裡面的 ‘__main__.py’ 檔案使用 ‘if __name__ == '__main__'’ 區塊
，它依然會如預期般地運作。因為當引入套件，其 ‘__name__’ 屬性將會包含套件
的路徑：

     >>> import asyncio.__main__
     >>> asyncio.__main__.__name__
     'asyncio.__main__'

但這對於 ‘.zip’ 檔案根目錄中的 ‘__main__.py’ 檔案不起作用。因此，為了保
持一致性，最小的、沒有 ‘__name__’ 檢查的 ‘__main__.py’ 會是首選。

也參考
......

請參閱 *note venv: f9. 作為標準函式庫中具有最小 ‘__main__.py’ 的套件為範
例。它不包含 ‘if __name__ == '__main__'’ 區塊。你可以使用 ‘python -m
venv [directory]’ 來呼叫它。

請參閱 *note runpy: ac. 取得有關直譯器可執行檔的 *note -m: 585. 旗標的更
多詳細資訊。

請參閱 *note zipapp: 116. 了解如何執行打包成 '.zip' 檔案的應用程式。在這
種情況下，Python 會在封存檔案的根目錄中尋找 ‘__main__.py’ 檔案。


File: python.info,  Node: import __main__,  Prev: Python 套件中的 __main__ py,  Up: __main__ --- 頂層程式碼環境

5.29.5.7 ‘import __main__’
..........................

無論 Python 程式是從哪個模組啟動的，在同一程式中執行的其他模組都可以透過
匯入 ‘__main__’ 模組來引入頂層環境的作用域 (*note namespace: 1b5b.)。這
不會引入 ‘__main__.py’ 檔案，而是引入接收特殊名稱 ‘'__main__'’ 的模組。

這是一個使用 ‘__main__’ 命名空間的範例模組：

     # namely.py

     import __main__

     def did_user_define_their_name():
         return 'my_name' in dir(__main__)

     def print_user_name():
         if not did_user_define_their_name():
             raise ValueError('Define the variable `my_name`!')

         if '__file__' in dir(__main__):
             print(__main__.my_name, "found in file", __main__.__file__)
         else:
             print(__main__.my_name)

該模組的範例用法如下：

     # start.py

     import sys

     from namely import print_user_name

     # my_name = "Dinsdale"

     def main():
         try:
             print_user_name()
         except ValueError as ve:
             return str(ve)

     if __name__ == "__main__":
         sys.exit(main())

現在，如果我們啟動程式，結果將如下所示：

     $ python start.py
     Define the variable `my_name`!

程式的結束代碼將為 1，表示出現錯誤。取消註解 ‘my_name = "Dinsdale"’ 而修
復程式後，現在它以狀態碼 0 結束，表示成功：

     $ python start.py
     Dinsdale found in file /path/to/start.py

請注意，引入 ‘__main__’ 並不會因為不經意地執行放在 ‘start’ 模組中 ‘if
__name__ == "__main__"’ 區塊的頂層程式碼（本來是給腳本使用的）而造成任何
問題。為什麼這樣做會如預期運作？

當 Python 直譯器啟動時，會在 *note sys.modules: 186e. 中插入一個空的
‘__main__’ 模組，並透過執行頂層程式碼來填充它。在我們的範例中，這是
‘start’ 模組，它將逐行執行並引入 ‘namely’。接著，‘namely’ 引入
‘__main__’（其實是 ‘start’）。這就是一個引入循環！幸運的是，由於部分填充
的 ‘__main__’ 模組存在於 *note sys.modules: 186e. 中，Python 將其傳遞給
‘namely’。請參閱引入系統參考文件中的*note 關於 __main__ 的特別考量:
1ee6.了解其工作原理的詳細資訊。

Python REPL 是「頂層環境」的另一個範例，因此 REPL 中定義的任何內容都成為
作域的一部分：

     >>> import namely
     >>> namely.did_user_define_their_name()
     False
     >>> namely.print_user_name()
     Traceback (most recent call last):
     ...
     ValueError: Define the variable `my_name`!
     >>> my_name = 'Jabberwocky'
     >>> namely.did_user_define_their_name()
     True
     >>> namely.print_user_name()
     Jabberwocky

請注意，在這種情況下， ‘__main__’ 作用域不包含 ‘__file__’ 屬性，因為它是
互動式的。

‘__main__’ 作用域用於 *note pdb: 94. 和 *note rlcompleter: ab. 的實作。


File: python.info,  Node: warnings --- 警告控制,  Next: dataclasses --- Data Classes,  Prev: __main__ --- 頂層程式碼環境,  Up: Python Runtime 服務

5.29.6 ‘warnings’ -- 警告控制
-----------------------------

'原始碼：'Lib/warnings.py(1)

__________________________________________________________________

Warning messages are typically issued in situations where it is useful
to alert the user of some condition in a program, where that condition
(normally) doesn't warrant raising an exception and terminating the
program.  For example, one might want to issue a warning when a program
uses an obsolete module.

Python programmers issue warnings by calling the *note warn(): 1488.
function defined in this module.  (C programmers use *note
PyErr_WarnEx(): 13b8.; see *note 例外處理: 41fa. for details).

Warning messages are normally written to *note sys.stderr: 8dd, but
their disposition can be changed flexibly, from ignoring all warnings to
turning them into exceptions.  The disposition of warnings can vary
based on the *note warning category: 2190, the text of the warning
message, and the source location where it is issued.  Repetitions of a
particular warning for the same source location are typically
suppressed.

There are two stages in warning control: first, each time a warning is
issued, a determination is made whether a message should be issued or
not; next, if a message is to be issued, it is formatted and printed
using a user-settable hook.

The determination whether to issue a warning message is controlled by
the *note warning filter: 86e, which is a sequence of matching rules and
actions.  Rules can be added to the filter by calling *note
filterwarnings(): 1414. and reset to its default state by calling *note
resetwarnings(): 41fb.

The printing of warning messages is done by calling *note showwarning():
41fc, which may be overridden; the default implementation of this
function formats the message by calling *note formatwarning(): 191b,
which is also available for use by custom implementations.

也參考
......

*note logging.captureWarnings(): 2bfb. allows you to handle all warnings
with the standard logging infrastructure.

* Menu:

* Warning Categories::
* The Warnings Filter::
* Temporarily Suppressing Warnings::
* Testing Warnings::
* Updating Code For New Versions of Dependencies::
* Available Functions::
* Available Context Managers::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/warnings.py


File: python.info,  Node: Warning Categories,  Next: The Warnings Filter,  Up: warnings --- 警告控制

5.29.6.1 Warning Categories
...........................

There are a number of built-in exceptions that represent warning
categories.  This categorization is useful to be able to filter out
groups of warnings.

While these are technically *note built-in exceptions: 218e, they are
documented here, because conceptually they belong to the warnings
mechanism.

User code can define additional warning categories by subclassing one of
the standard warning categories.  A warning category must always be a
subclass of the *note Warning: 2191. class.

The following warnings category classes are currently defined:

Class                                  描述
                                       
-------------------------------------------------------------------------------------------
                                       
*note Warning: 2191.                   This is the base class of all warning category
                                       classes.  It is a subclass of
                                       *note Exception: 97d.
                                       
                                       
*note UserWarning: 2192.               The default category for *note warn(): 1488.
                                       
                                       
*note DeprecationWarning: 18b.         Base category for warnings about deprecated
                                       features when those warnings are intended for
                                       other Python developers (ignored by default,
                                       unless triggered by code in ‘__main__’).
                                       
                                       
*note SyntaxWarning: 40c.              Base category for warnings about dubious
                                       syntactic features.
                                       
                                       
*note RuntimeWarning: 1a3.             Base category for warnings about dubious runtime
                                       features.
                                       
                                       
*note FutureWarning: 357.              Base category for warnings about deprecated
                                       features when those warnings are intended for end
                                       users of applications that are written in Python.
                                       
                                       
*note PendingDeprecationWarning: 86d.  Base category for warnings about features that
                                       will be deprecated in the future (ignored by
                                       default).
                                       
                                       
*note ImportWarning: 4a2.              Base category for warnings triggered during the
                                       process of importing a module (ignored by
                                       default).
                                       
                                       
*note UnicodeWarning: 1391.            Base category for warnings related to Unicode.
                                       
                                       
*note BytesWarning: bca.               Base category for warnings related to
                                       *note bytes: 1a5. and *note bytearray: 4e3.
                                       
                                       
*note ResourceWarning: 229.            Base category for warnings related to resource
                                       usage (ignored by default).
                                       

在 3.7 版的變更: Previously *note DeprecationWarning: 18b. and *note
FutureWarning: 357. were distinguished based on whether a feature was
being removed entirely or changing its behaviour.  They are now
distinguished based on their intended audience and the way they're
handled by the default warnings filters.


File: python.info,  Node: The Warnings Filter,  Next: Temporarily Suppressing Warnings,  Prev: Warning Categories,  Up: warnings --- 警告控制

5.29.6.2 The Warnings Filter
............................

The warnings filter controls whether warnings are ignored, displayed, or
turned into errors (raising an exception).

Conceptually, the warnings filter maintains an ordered list of filter
specifications; any specific warning is matched against each filter
specification in the list in turn until a match is found; the filter
determines the disposition of the match.  Each entry is a tuple of the
form ('action', 'message', 'category', 'module', 'lineno'), where:

   * 'action' is one of the following strings:

     Value               Disposition
                         
     -----------------------------------------------------------------------
                         
     ‘"default"’         print the first occurrence of matching warnings
                         for each location (module + line number) where
                         the warning is issued
                         
                         
     ‘"error"’           turn matching warnings into exceptions
                         
                         
     ‘"ignore"’          never print matching warnings
                         
                         
     ‘"always"’          always print matching warnings
                         
                         
     ‘"module"’          print the first occurrence of matching warnings
                         for each module where the warning is issued
                         (regardless of line number)
                         
                         
     ‘"once"’            print only the first occurrence of matching
                         warnings, regardless of location
                         

   * 'message' is a string containing a regular expression that the
     start of the warning message must match, case-insensitively.  In
     *note -W: 86c. and *note PYTHONWARNINGS: b51, 'message' is a
     literal string that the start of the warning message must contain
     (case-insensitively), ignoring any whitespace at the start or end
     of 'message'.

   * 'category' is a class (a subclass of *note Warning: 2191.) of which
     the warning category must be a subclass in order to match.

   * 'module' is a string containing a regular expression that the start
     of the fully qualified module name must match, case-sensitively.
     In *note -W: 86c. and *note PYTHONWARNINGS: b51, 'module' is a
     literal string that the fully qualified module name must be equal
     to (case-sensitively), ignoring any whitespace at the start or end
     of 'module'.

   * 'lineno' is an integer that the line number where the warning
     occurred must match, or ‘0’ to match all line numbers.

Since the *note Warning: 2191. class is derived from the built-in *note
Exception: 97d. class, to turn a warning into an error we simply raise
‘category(message)’.

If a warning is reported and doesn't match any registered filter then
the "default" action is applied (hence its name).

* Menu:

* Describing Warning Filters::
* Default Warning Filter::
* Overriding the default filter::


File: python.info,  Node: Describing Warning Filters,  Next: Default Warning Filter,  Up: The Warnings Filter

5.29.6.3 Describing Warning Filters
...................................

The warnings filter is initialized by *note -W: 86c. options passed to
the Python interpreter command line and the *note PYTHONWARNINGS: b51.
environment variable.  The interpreter saves the arguments for all
supplied entries without interpretation in *note sys.warnoptions: 37b.;
the *note warnings: fa. module parses these when it is first imported
(invalid options are ignored, after printing a message to *note
sys.stderr: 8dd.).

Individual warnings filters are specified as a sequence of fields
separated by colons:

     action:message:category:module:line

The meaning of each of these fields is as described in *note The
Warnings Filter: 86e.  When listing multiple filters on a single line
(as for *note PYTHONWARNINGS: b51.), the individual filters are
separated by commas and the filters listed later take precedence over
those listed before them (as they're applied left-to-right, and the most
recently applied filters take precedence over earlier ones).

Commonly used warning filters apply to either all warnings, warnings in
a particular category, or warnings raised by particular modules or
packages.  Some examples:

     default                      # Show all warnings (even those ignored by default)
     ignore                       # Ignore all warnings
     error                        # Convert all warnings to errors
     error::ResourceWarning       # Treat ResourceWarning messages as errors
     default::DeprecationWarning  # Show DeprecationWarning messages
     ignore,default:::mymodule    # Only report warnings triggered by "mymodule"
     error:::mymodule             # Convert warnings to errors in "mymodule"


File: python.info,  Node: Default Warning Filter,  Next: Overriding the default filter,  Prev: Describing Warning Filters,  Up: The Warnings Filter

5.29.6.4 Default Warning Filter
...............................

By default, Python installs several warning filters, which can be
overridden by the *note -W: 86c. command-line option, the *note
PYTHONWARNINGS: b51. environment variable and calls to *note
filterwarnings(): 1414.

In regular release builds, the default warning filter has the following
entries (in order of precedence):

     default::DeprecationWarning:__main__
     ignore::DeprecationWarning
     ignore::PendingDeprecationWarning
     ignore::ImportWarning
     ignore::ResourceWarning

In a *note debug build: 1de, the list of default warning filters is
empty.

在 3.2 版的變更: *note DeprecationWarning: 18b. is now ignored by
default in addition to *note PendingDeprecationWarning: 86d.

在 3.7 版的變更: *note DeprecationWarning: 18b. is once again shown by
default when triggered directly by code in ‘__main__’.

在 3.7 版的變更: *note BytesWarning: bca. no longer appears in the
default filter list and is instead configured via *note sys.warnoptions:
37b. when *note -b: 587. is specified twice.


File: python.info,  Node: Overriding the default filter,  Prev: Default Warning Filter,  Up: The Warnings Filter

5.29.6.5 Overriding the default filter
......................................

Developers of applications written in Python may wish to hide 'all'
Python level warnings from their users by default, and only display them
when running tests or otherwise working on the application.  The *note
sys.warnoptions: 37b. attribute used to pass filter configurations to
the interpreter can be used as a marker to indicate whether or not
warnings should be disabled:

     import sys

     if not sys.warnoptions:
         import warnings
         warnings.simplefilter("ignore")

Developers of test runners for Python code are advised to instead ensure
that 'all' warnings are displayed by default for the code under test,
using code like:

     import sys

     if not sys.warnoptions:
         import os, warnings
         warnings.simplefilter("default") # Change the filter in this process
         os.environ["PYTHONWARNINGS"] = "default" # Also affect subprocesses

Finally, developers of interactive shells that run user code in a
namespace other than ‘__main__’ are advised to ensure that *note
DeprecationWarning: 18b. messages are made visible by default, using
code like the following (where ‘user_ns’ is the module used to execute
code entered interactively):

     import warnings
     warnings.filterwarnings("default", category=DeprecationWarning,
                                        module=user_ns.get("__name__"))


File: python.info,  Node: Temporarily Suppressing Warnings,  Next: Testing Warnings,  Prev: The Warnings Filter,  Up: warnings --- 警告控制

5.29.6.6 Temporarily Suppressing Warnings
.........................................

If you are using code that you know will raise a warning, such as a
deprecated function, but do not want to see the warning (even when
warnings have been explicitly configured via the command line), then it
is possible to suppress the warning using the *note catch_warnings: 52a.
context manager:

     import warnings

     def fxn():
         warnings.warn("deprecated", DeprecationWarning)

     with warnings.catch_warnings():
         warnings.simplefilter("ignore")
         fxn()

While within the context manager all warnings will simply be ignored.
This allows you to use known-deprecated code without having to see the
warning while not suppressing the warning for other code that might not
be aware of its use of deprecated code.  Note: this can only be
guaranteed in a single-threaded application.  If two or more threads use
the *note catch_warnings: 52a. context manager at the same time, the
behavior is undefined.


File: python.info,  Node: Testing Warnings,  Next: Updating Code For New Versions of Dependencies,  Prev: Temporarily Suppressing Warnings,  Up: warnings --- 警告控制

5.29.6.7 Testing Warnings
.........................

To test warnings raised by code, use the *note catch_warnings: 52a.
context manager.  With it you can temporarily mutate the warnings filter
to facilitate your testing.  For instance, do the following to capture
all raised warnings to check:

     import warnings

     def fxn():
         warnings.warn("deprecated", DeprecationWarning)

     with warnings.catch_warnings(record=True) as w:
         # Cause all warnings to always be triggered.
         warnings.simplefilter("always")
         # Trigger a warning.
         fxn()
         # Verify some things
         assert len(w) == 1
         assert issubclass(w[-1].category, DeprecationWarning)
         assert "deprecated" in str(w[-1].message)

One can also cause all warnings to be exceptions by using ‘error’
instead of ‘always’.  One thing to be aware of is that if a warning has
already been raised because of a ‘once’/‘default’ rule, then no matter
what filters are set the warning will not be seen again unless the
warnings registry related to the warning has been cleared.

Once the context manager exits, the warnings filter is restored to its
state when the context was entered.  This prevents tests from changing
the warnings filter in unexpected ways between tests and leading to
indeterminate test results.  The *note showwarning(): 41fc. function in
the module is also restored to its original value.  Note: this can only
be guaranteed in a single-threaded application.  If two or more threads
use the *note catch_warnings: 52a. context manager at the same time, the
behavior is undefined.

When testing multiple operations that raise the same kind of warning, it
is important to test them in a manner that confirms each operation is
raising a new warning (e.g.  set warnings to be raised as exceptions and
check the operations raise exceptions, check that the length of the
warning list continues to increase after each operation, or else delete
the previous entries from the warnings list before each new operation).


File: python.info,  Node: Updating Code For New Versions of Dependencies,  Next: Available Functions,  Prev: Testing Warnings,  Up: warnings --- 警告控制

5.29.6.8 Updating Code For New Versions of Dependencies
.......................................................

Warning categories that are primarily of interest to Python developers
(rather than end users of applications written in Python) are ignored by
default.

Notably, this "ignored by default" list includes *note
DeprecationWarning: 18b. (for every module except ‘__main__’), which
means developers should make sure to test their code with typically
ignored warnings made visible in order to receive timely notifications
of future breaking API changes (whether in the standard library or third
party packages).

In the ideal case, the code will have a suitable test suite, and the
test runner will take care of implicitly enabling all warnings when
running tests (the test runner provided by the *note unittest: ef.
module does this).

In less ideal cases, applications can be checked for use of deprecated
interfaces by passing *note -Wd: 86c. to the Python interpreter (this is
shorthand for ‘-W default’) or setting ‘PYTHONWARNINGS=default’ in the
environment.  This enables default handling for all warnings, including
those that are ignored by default.  To change what action is taken for
encountered warnings you can change what argument is passed to *note -W:
86c. (e.g.  ‘-W error’).  See the *note -W: 86c. flag for more details
on what is possible.


File: python.info,  Node: Available Functions,  Next: Available Context Managers,  Prev: Updating Code For New Versions of Dependencies,  Up: warnings --- 警告控制

5.29.6.9 Available Functions
............................

 -- 函式: warnings.warn (message, category=None, stacklevel=1,
          source=None, *, skip_file_prefixes=None)

     Issue a warning, or maybe ignore it or raise an exception.  The
     'category' argument, if given, must be a *note warning category
     class: 2190.; it defaults to *note UserWarning: 2192.
     Alternatively, 'message' can be a *note Warning: 2191. instance, in
     which case 'category' will be ignored and ‘message.__class__’ will
     be used.  In this case, the message text will be ‘str(message)’.
     This function raises an exception if the particular warning issued
     is changed into an error by the *note warnings filter: 86e.  The
     'stacklevel' argument can be used by wrapper functions written in
     Python, like this:

          def deprecated_api(message):
              warnings.warn(message, DeprecationWarning, stacklevel=2)

     This makes the warning refer to ‘deprecated_api’'s caller, rather
     than to the source of ‘deprecated_api’ itself (since the latter
     would defeat the purpose of the warning message).

     The 'skip_file_prefixes' keyword argument can be used to indicate
     which stack frames are ignored when counting stack levels.  This
     can be useful when you want the warning to always appear at call
     sites outside of a package when a constant 'stacklevel' does not
     fit all call paths or is otherwise challenging to maintain.  If
     supplied, it must be a tuple of strings.  When prefixes are
     supplied, stacklevel is implicitly overridden to be ‘max(2,
     stacklevel)’.  To cause a warning to be attributed to the caller
     from outside of the current package you might write:

          # example/lower.py
          _warn_skips = (os.path.dirname(__file__),)

          def one_way(r_luxury_yacht=None, t_wobbler_mangrove=None):
              if r_luxury_yacht:
                  warnings.warn("Please migrate to t_wobbler_mangrove=.",
                                skip_file_prefixes=_warn_skips)

          # example/higher.py
          from . import lower

          def another_way(**kw):
              lower.one_way(**kw)

     This makes the warning refer to both the ‘example.lower.one_way()’
     and ‘package.higher.another_way()’ call sites only from calling
     code living outside of ‘example’ package.

     'source', if supplied, is the destroyed object which emitted a
     *note ResourceWarning: 229.

     在 3.6 版的變更: 新增 'source' 參數。

     在 3.12 版的變更: 新增 'skip_file_prefixes'。

 -- 函式: warnings.warn_explicit (message, category, filename, lineno,
          module=None, registry=None, module_globals=None, source=None)

     This is a low-level interface to the functionality of *note warn():
     1488, passing in explicitly the message, category, filename and
     line number, and optionally the module name and the registry (which
     should be the ‘__warningregistry__’ dictionary of the module).  The
     module name defaults to the filename with ‘.py’ stripped; if no
     registry is passed, the warning is never suppressed.  'message'
     must be a string and 'category' a subclass of *note Warning: 2191.
     or 'message' may be a *note Warning: 2191. instance, in which case
     'category' will be ignored.

     'module_globals', if supplied, should be the global namespace in
     use by the code for which the warning is issued.  (This argument is
     used to support displaying source for modules found in zipfiles or
     other non-filesystem import sources).

     'source', if supplied, is the destroyed object which emitted a
     *note ResourceWarning: 229.

     在 3.6 版的變更: Add the 'source' parameter.

 -- 函式: warnings.showwarning (message, category, filename, lineno,
          file=None, line=None)

     Write a warning to a file.  The default implementation calls
     ‘formatwarning(message, category, filename, lineno, line)’ and
     writes the resulting string to 'file', which defaults to *note
     sys.stderr: 8dd.  You may replace this function with any callable
     by assigning to ‘warnings.showwarning’.  'line' is a line of source
     code to be included in the warning message; if 'line' is not
     supplied, *note showwarning(): 41fc. will try to read the line
     specified by 'filename' and 'lineno'.

 -- 函式: warnings.formatwarning (message, category, filename, lineno,
          line=None)

     Format a warning the standard way.  This returns a string which may
     contain embedded newlines and ends in a newline.  'line' is a line
     of source code to be included in the warning message; if 'line' is
     not supplied, *note formatwarning(): 191b. will try to read the
     line specified by 'filename' and 'lineno'.

 -- 函式: warnings.filterwarnings (action, message='', category=Warning,
          module='', lineno=0, append=False)

     Insert an entry into the list of *note warnings filter
     specifications: 86e.  The entry is inserted at the front by
     default; if 'append' is true, it is inserted at the end.  This
     checks the types of the arguments, compiles the 'message' and
     'module' regular expressions, and inserts them as a tuple in the
     list of warnings filters.  Entries closer to the front of the list
     override entries later in the list, if both match a particular
     warning.  Omitted arguments default to a value that matches
     everything.

 -- 函式: warnings.simplefilter (action, category=Warning, lineno=0,
          append=False)

     Insert a simple entry into the list of *note warnings filter
     specifications: 86e.  The meaning of the function parameters is as
     for *note filterwarnings(): 1414, but regular expressions are not
     needed as the filter inserted always matches any message in any
     module as long as the category and line number match.

 -- 函式: warnings.resetwarnings ()

     Reset the warnings filter.  This discards the effect of all
     previous calls to *note filterwarnings(): 1414, including that of
     the *note -W: 86c. command line options and calls to *note
     simplefilter(): 666.

 -- 函式: @warnings.deprecated (msg, *, category=DeprecationWarning,
          stacklevel=1)

     Decorator to indicate that a class, function or overload is
     deprecated.

     When this decorator is applied to an object, deprecation warnings
     may be emitted at runtime when the object is used.  *note static
     type checkers: 252. will also generate a diagnostic on usage of the
     deprecated object.

     Usage:

          from warnings import deprecated
          from typing import overload

          @deprecated("Use B instead")
          class A:
              pass

          @deprecated("Use g instead")
          def f():
              pass

          @overload
          @deprecated("int support is deprecated")
          def g(x: int) -> int: ...
          @overload
          def g(x: str) -> int: ...

     The warning specified by 'category' will be emitted at runtime on
     use of deprecated objects.  For functions, that happens on calls;
     for classes, on instantiation and on creation of subclasses.  If
     the 'category' is ‘None’, no warning is emitted at runtime.  The
     'stacklevel' determines where the warning is emitted.  If it is ‘1’
     (the default), the warning is emitted at the direct caller of the
     deprecated object; if it is higher, it is emitted further up the
     stack.  Static type checker behavior is not affected by the
     'category' and 'stacklevel' arguments.

     The deprecation message passed to the decorator is saved in the
     ‘__deprecated__’ attribute on the decorated object.  If applied to
     an overload, the decorator must be after the *note @overload: 3d8f.
     decorator for the attribute to exist on the overload as returned by
     *note typing.get_overloads(): 653.

     在 3.13 版被加入: See PEP 702(1).

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0702/


File: python.info,  Node: Available Context Managers,  Prev: Available Functions,  Up: warnings --- 警告控制

5.29.6.10 Available Context Managers
....................................

 -- 類別: warnings.catch_warnings (*, record=False, module=None,
          action=None, category=Warning, lineno=0, append=False)

     A context manager that copies and, upon exit, restores the warnings
     filter and the *note showwarning(): 41fc. function.  If the
     'record' argument is *note False: adb. (the default) the context
     manager returns *note None: 61b. on entry.  If 'record' is *note
     True: bb4, a list is returned that is progressively populated with
     objects as seen by a custom *note showwarning(): 41fc. function
     (which also suppresses output to ‘sys.stdout’).  Each object in the
     list has attributes with the same names as the arguments to *note
     showwarning(): 41fc.

     The 'module' argument takes a module that will be used instead of
     the module returned when you import *note warnings: fa. whose
     filter will be protected.  This argument exists primarily for
     testing the *note warnings: fa. module itself.

     If the 'action' argument is not ‘None’, the remaining arguments are
     passed to *note simplefilter(): 666. as if it were called
     immediately on entering the context.

          備註: The *note catch_warnings: 52a. manager works by
          replacing and then later restoring the module's *note
          showwarning(): 41fc. function and internal list of filter
          specifications.  This means the context manager is modifying
          global state and therefore is not thread-safe.

     在 3.11 版的變更: 新增 'action'、'category'、'lineno' 和 'append' 參
     數。


File: python.info,  Node: dataclasses --- Data Classes,  Next: contextlib --- Utilities for with-statement contexts,  Prev: warnings --- 警告控制,  Up: Python Runtime 服務

5.29.7 ‘dataclasses’ -- Data Classes
------------------------------------

'原始碼：'Lib/dataclasses.py(1)

__________________________________________________________________

This module provides a decorator and functions for automatically adding
generated *note special methods: 17ae. such as *note __init__(): 655.
and *note __repr__(): 5c2. to user-defined classes.  It was originally
described in PEP 557(2).

The member variables to use in these generated methods are defined using
PEP 526(3) type annotations.  For example, this code:

     from dataclasses import dataclass

     @dataclass
     class InventoryItem:
         """Class for keeping track of an item in inventory."""
         name: str
         unit_price: float
         quantity_on_hand: int = 0

         def total_cost(self) -> float:
             return self.unit_price * self.quantity_on_hand

will add, among other things, a ‘__init__()’ that looks like:

     def __init__(self, name: str, unit_price: float, quantity_on_hand: int = 0):
         self.name = name
         self.unit_price = unit_price
         self.quantity_on_hand = quantity_on_hand

Note that this method is automatically added to the class: it is not
directly specified in the ‘InventoryItem’ definition shown above.

在 3.7 版被加入.

* Menu:

* 模組內容: 模組內容<8>.
* Post-init processing::
* 類別變數::
* Init-only variables::
* 凍結實例::
* 繼承::
* Re-ordering of keyword-only parameters in __init__(): Re-ordering of keyword-only parameters in __init__.
* 預設工廠函式::
* 可變預設值::
* Descriptor-typed fields::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/dataclasses.py

   (2) https://peps.python.org/pep-0557/

   (3) https://peps.python.org/pep-0526/


File: python.info,  Node: 模組內容<8>,  Next: Post-init processing,  Up: dataclasses --- Data Classes

5.29.7.1 模組內容
.................

 -- 函式: @dataclasses.dataclass (*, init=True, repr=True, eq=True,
          order=False, unsafe_hash=False, frozen=False, match_args=True,
          kw_only=False, slots=False, weakref_slot=False)

     This function is a *note decorator: 6d5. that is used to add
     generated *note special methods: 17ae. to classes, as described
     below.

     The ‘@dataclass’ decorator examines the class to find ‘field’s.  A
     ‘field’ is defined as a class variable that has a *note type
     annotation: cfc.  With two exceptions described below, nothing in
     ‘@dataclass’ examines the type specified in the variable
     annotation.

     The order of the fields in all of the generated methods is the
     order in which they appear in the class definition.

     The ‘@dataclass’ decorator will add various "dunder" methods to the
     class, described below.  If any of the added methods already exist
     in the class, the behavior depends on the parameter, as documented
     below.  The decorator returns the same class that it is called on;
     no new class is created.

     If ‘@dataclass’ is used just as a simple decorator with no
     parameters, it acts as if it has the default values documented in
     this signature.  That is, these three uses of ‘@dataclass’ are
     equivalent:

          @dataclass
          class C:
              ...

          @dataclass()
          class C:
              ...

          @dataclass(init=True, repr=True, eq=True, order=False, unsafe_hash=False, frozen=False,
                     match_args=True, kw_only=False, slots=False, weakref_slot=False)
          class C:
              ...

     ‘@dataclass’ 的參數是：

        - 'init': If true (the default), a *note __init__(): 655. method
          will be generated.

          If the class already defines ‘__init__()’, this parameter is
          ignored.

        - 'repr': If true (the default), a *note __repr__(): 5c2. method
          will be generated.  The generated repr string will have the
          class name and the name and repr of each field, in the order
          they are defined in the class.  Fields that are marked as
          being excluded from the repr are not included.  For example:
          ‘InventoryItem(name='widget', unit_price=3.0,
          quantity_on_hand=10)’.

          If the class already defines ‘__repr__()’, this parameter is
          ignored.

        - 'eq': If true (the default), an *note __eq__(): a9d. method
          will be generated.  This method compares the class as if it
          were a tuple of its fields, in order.  Both instances in the
          comparison must be of the identical type.

          If the class already defines ‘__eq__()’, this parameter is
          ignored.

        - 'order': If true (the default is ‘False’), *note __lt__():
          129e, *note __le__(): 129f, *note __gt__(): 12a0, and *note
          __ge__(): 12a1. methods will be generated.  These compare the
          class as if it were a tuple of its fields, in order.  Both
          instances in the comparison must be of the identical type.  If
          'order' is true and 'eq' is false, a *note ValueError: 1e7. is
          raised.

          If the class already defines any of ‘__lt__()’, ‘__le__()’,
          ‘__gt__()’, or ‘__ge__()’, then *note TypeError: 4dd. is
          raised.

        - 'unsafe_hash': If ‘False’ (the default), a *note __hash__():
          a9e. method is generated according to how 'eq' and 'frozen'
          are set.

          ‘__hash__()’ is used by built-in *note hash(): 58f, and when
          objects are added to hashed collections such as dictionaries
          and sets.  Having a ‘__hash__()’ implies that instances of the
          class are immutable.  Mutability is a complicated property
          that depends on the programmer's intent, the existence and
          behavior of ‘__eq__()’, and the values of the 'eq' and
          'frozen' flags in the ‘@dataclass’ decorator.

          By default, ‘@dataclass’ will not implicitly add a *note
          __hash__(): a9e. method unless it is safe to do so.  Neither
          will it add or change an existing explicitly defined
          ‘__hash__()’ method.  Setting the class attribute ‘__hash__ =
          None’ has a specific meaning to Python, as described in the
          ‘__hash__()’ documentation.

          If ‘__hash__()’ is not explicitly defined, or if it is set to
          ‘None’, then ‘@dataclass’ 'may' add an implicit ‘__hash__()’
          method.  Although not recommended, you can force ‘@dataclass’
          to create a ‘__hash__()’ method with ‘unsafe_hash=True’.  This
          might be the case if your class is logically immutable but can
          still be mutated.  This is a specialized use case and should
          be considered carefully.

          Here are the rules governing implicit creation of a
          ‘__hash__()’ method.  Note that you cannot both have an
          explicit ‘__hash__()’ method in your dataclass and set
          ‘unsafe_hash=True’; this will result in a *note TypeError:
          4dd.

          If 'eq' and 'frozen' are both true, by default ‘@dataclass’
          will generate a ‘__hash__()’ method for you.  If 'eq' is true
          and 'frozen' is false, ‘__hash__()’ will be set to ‘None’,
          marking it unhashable (which it is, since it is mutable).  If
          'eq' is false, ‘__hash__()’ will be left untouched meaning the
          ‘__hash__()’ method of the superclass will be used (if the
          superclass is *note object: a2f, this means it will fall back
          to id-based hashing).

        - 'frozen': If true (the default is ‘False’), assigning to
          fields will generate an exception.  This emulates read-only
          frozen instances.  If *note __setattr__(): 1e05. or *note
          __delattr__(): 1e06. is defined in the class, then *note
          TypeError: 4dd. is raised.  See the discussion below.

        - 'match_args': If true (the default is ‘True’), the *note
          __match_args__: 17c2. tuple will be created from the list of
          parameters to the generated *note __init__(): 655. method
          (even if ‘__init__()’ is not generated, see above).  If false,
          or if ‘__match_args__’ is already defined in the class, then
          ‘__match_args__’ will not be generated.

          在 3.10 版被加入.

        - 'kw_only': If true (the default value is ‘False’), then all
          fields will be marked as keyword-only.  If a field is marked
          as keyword-only, then the only effect is that the *note
          __init__(): 655. parameter generated from a keyword-only field
          must be specified with a keyword when ‘__init__()’ is called.
          There is no effect on any other aspect of dataclasses.  See
          the *note parameter: 1dee. glossary entry for details.  Also
          see the *note KW_ONLY: 420f. section.

          在 3.10 版被加入.

        - 'slots': If true (the default is ‘False’), *note __slots__:
          1458. attribute will be generated and new class will be
          returned instead of the original one.  If ‘__slots__’ is
          already defined in the class, then *note TypeError: 4dd. is
          raised.

               警告: Calling no-arg *note super(): 483. in dataclasses
               using ‘slots=True’ will result in the following exception
               being raised: ‘TypeError: super(type, obj): obj must be
               an instance or subtype of type’.  The two-arg *note
               super(): 483. is a valid workaround.  See gh-90562(1) for
               full details.

               警告: Passing parameters to a base class *note
               __init_subclass__(): 5d7. when using ‘slots=True’ will
               result in a *note TypeError: 4dd.  Either use
               ‘__init_subclass__’ with no parameters or use default
               values as a workaround.  See gh-91126(2) for full
               details.

          在 3.10 版被加入.

          在 3.11 版的變更: If a field name is already included in the
          ‘__slots__’ of a base class, it will not be included in the
          generated ‘__slots__’ to prevent *note overriding them: 1e45.
          Therefore, do not use ‘__slots__’ to retrieve the field names
          of a dataclass.  Use *note fields(): 1641. instead.  To be
          able to determine inherited slots, base class ‘__slots__’ may
          be any iterable, but 'not' an iterator.

        - 'weakref_slot': If true (the default is ‘False’), add a slot
          named "__weakref__", which is required to make an instance
          *note weakref-able: f91.  It is an error to specify
          ‘weakref_slot=True’ without also specifying ‘slots=True’.

          在 3.11 版被加入.

     ‘field’s may optionally specify a default value, using normal
     Python syntax:

          @dataclass
          class C:
              a: int       # 'a' has no default value
              b: int = 0   # assign a default value for 'b'

     In this example, both ‘a’ and ‘b’ will be included in the added
     *note __init__(): 655. method, which will be defined as:

          def __init__(self, a: int, b: int = 0):

     *note TypeError: 4dd. will be raised if a field without a default
     value follows a field with a default value.  This is true whether
     this occurs in a single class, or as a result of class inheritance.

 -- 函式: dataclasses.field (*, default=MISSING,
          default_factory=MISSING, init=True, repr=True, hash=None,
          compare=True, metadata=None, kw_only=MISSING)

     For common and simple use cases, no other functionality is
     required.  There are, however, some dataclass features that require
     additional per-field information.  To satisfy this need for
     additional information, you can replace the default field value
     with a call to the provided ‘field()’ function.  For example:

          @dataclass
          class C:
              mylist: list[int] = field(default_factory=list)

          c = C()
          c.mylist += [1, 2, 3]

     As shown above, the *note MISSING: 4210. value is a sentinel object
     used to detect if some parameters are provided by the user.  This
     sentinel is used because ‘None’ is a valid value for some
     parameters with a distinct meaning.  No code should directly use
     the *note MISSING: 4210. value.

     ‘field()’ 的參數是：

        - 'default': If provided, this will be the default value for
          this field.  This is needed because the ‘field()’ call itself
          replaces the normal position of the default value.

        - 'default_factory': If provided, it must be a zero-argument
          callable that will be called when a default value is needed
          for this field.  Among other purposes, this can be used to
          specify fields with mutable default values, as discussed
          below.  It is an error to specify both 'default' and
          'default_factory'.

        - 'init': If true (the default), this field is included as a
          parameter to the generated *note __init__(): 655. method.

        - 'repr': If true (the default), this field is included in the
          string returned by the generated *note __repr__(): 5c2.
          method.

        - 'hash': This can be a bool or ‘None’.  If true, this field is
          included in the generated *note __hash__(): a9e. method.  If
          ‘None’ (the default), use the value of 'compare': this would
          normally be the expected behavior.  A field should be
          considered in the hash if it's used for comparisons.  Setting
          this value to anything other than ‘None’ is discouraged.

          One possible reason to set ‘hash=False’ but ‘compare=True’
          would be if a field is expensive to compute a hash value for,
          that field is needed for equality testing, and there are other
          fields that contribute to the type's hash value.  Even if a
          field is excluded from the hash, it will still be used for
          comparisons.

        - 'compare': If true (the default), this field is included in
          the generated equality and comparison methods (*note __eq__():
          a9d, *note __gt__(): 12a0, et al.).

        - 'metadata': This can be a mapping or ‘None’.  ‘None’ is
          treated as an empty dict.  This value is wrapped in *note
          MappingProxyType(): 414. to make it read-only, and exposed on
          the *note Field: 2132. object.  It is not used at all by Data
          Classes, and is provided as a third-party extension mechanism.
          Multiple third-parties can each have their own key, to use as
          a namespace in the metadata.

        - 'kw_only': If true, this field will be marked as keyword-only.
          This is used when the generated *note __init__(): 655.
          method's parameters are computed.

          在 3.10 版被加入.

     If the default value of a field is specified by a call to
     ‘field()’, then the class attribute for this field will be replaced
     by the specified 'default' value.  If 'default' is not provided,
     then the class attribute will be deleted.  The intent is that after
     the *note @dataclass: 1af. decorator runs, the class attributes
     will all contain the default values for the fields, just as if the
     default value itself were specified.  For example, after:

          @dataclass
          class C:
              x: int
              y: int = field(repr=False)
              z: int = field(repr=False, default=10)
              t: int = 20

     The class attribute ‘C.z’ will be ‘10’, the class attribute ‘C.t’
     will be ‘20’, and the class attributes ‘C.x’ and ‘C.y’ will not be
     set.

 -- 類別: dataclasses.Field

     ‘Field’ objects describe each defined field.  These objects are
     created internally, and are returned by the *note fields(): 1641.
     module-level method (see below).  Users should never instantiate a
     ‘Field’ object directly.  Its documented attributes are:

        - ‘name’：欄位的名稱。

        - ‘type’：欄位的型別。

        - ‘default’, ‘default_factory’, ‘init’, ‘repr’, ‘hash’,
          ‘compare’, ‘metadata’, and ‘kw_only’ have the identical
          meaning and values as they do in the *note field(): 1926.
          function.

     Other attributes may exist, but they are private and must not be
     inspected or relied on.

 -- 函式: dataclasses.fields (class_or_instance)

     Returns a tuple of *note Field: 2132. objects that define the
     fields for this dataclass.  Accepts either a dataclass, or an
     instance of a dataclass.  Raises *note TypeError: 4dd. if not
     passed a dataclass or instance of one.  Does not return
     pseudo-fields which are ‘ClassVar’ or ‘InitVar’.

 -- 函式: dataclasses.asdict (obj, *, dict_factory=dict)

     Converts the dataclass 'obj' to a dict (by using the factory
     function 'dict_factory').  Each dataclass is converted to a dict of
     its fields, as ‘name: value’ pairs.  dataclasses, dicts, lists, and
     tuples are recursed into.  Other objects are copied with *note
     copy.deepcopy(): b12.

     Example of using ‘asdict()’ on nested dataclasses:

          @dataclass
          class Point:
               x: int
               y: int

          @dataclass
          class C:
               mylist: list[Point]

          p = Point(10, 20)
          assert asdict(p) == {'x': 10, 'y': 20}

          c = C([Point(0, 0), Point(10, 4)])
          assert asdict(c) == {'mylist': [{'x': 0, 'y': 0}, {'x': 10, 'y': 4}]}

     To create a shallow copy, the following workaround may be used:

          {field.name: getattr(obj, field.name) for field in fields(obj)}

     ‘asdict()’ raises *note TypeError: 4dd. if 'obj' is not a dataclass
     instance.

 -- 函式: dataclasses.astuple (obj, *, tuple_factory=tuple)

     Converts the dataclass 'obj' to a tuple (by using the factory
     function 'tuple_factory').  Each dataclass is converted to a tuple
     of its field values.  dataclasses, dicts, lists, and tuples are
     recursed into.  Other objects are copied with *note
     copy.deepcopy(): b12.

     從前面的例子繼續：

          assert astuple(p) == (10, 20)
          assert astuple(c) == ([(0, 0), (10, 4)],)

     To create a shallow copy, the following workaround may be used:

          tuple(getattr(obj, field.name) for field in dataclasses.fields(obj))

     ‘astuple()’ raises *note TypeError: 4dd. if 'obj' is not a
     dataclass instance.

 -- 函式: dataclasses.make_dataclass (cls_name, fields, *, bases=(),
          namespace=None, init=True, repr=True, eq=True, order=False,
          unsafe_hash=False, frozen=False, match_args=True,
          kw_only=False, slots=False, weakref_slot=False, module=None)

     Creates a new dataclass with name 'cls_name', fields as defined in
     'fields', base classes as given in 'bases', and initialized with a
     namespace as given in 'namespace'.  'fields' is an iterable whose
     elements are each either ‘name’, ‘(name, type)’, or ‘(name, type,
     Field)’.  If just ‘name’ is supplied, *note typing.Any: 651. is
     used for ‘type’.  The values of 'init', 'repr', 'eq', 'order',
     'unsafe_hash', 'frozen', 'match_args', 'kw_only', 'slots', and
     'weakref_slot' have the same meaning as they do in *note
     @dataclass: 1af.

     If 'module' is defined, the ‘__module__’ attribute of the dataclass
     is set to that value.  By default, it is set to the module name of
     the caller.

     This function is not strictly required, because any Python
     mechanism for creating a new class with ‘__annotations__’ can then
     apply the *note @dataclass: 1af. function to convert that class to
     a dataclass.  This function is provided as a convenience.  For
     example:

          C = make_dataclass('C',
                             [('x', int),
                               'y',
                              ('z', int, field(default=5))],
                             namespace={'add_one': lambda self: self.x + 1})

     相當於：

          @dataclass
          class C:
              x: int
              y: 'typing.Any'
              z: int = 5

              def add_one(self):
                  return self.x + 1

 -- 函式: dataclasses.replace (obj, /, **changes)

     Creates a new object of the same type as 'obj', replacing fields
     with values from 'changes'.  If 'obj' is not a Data Class, raises
     *note TypeError: 4dd.  If keys in 'changes' are not field names of
     the given dataclass, raises *note TypeError: 4dd.

     The newly returned object is created by calling the *note
     __init__(): 655. method of the dataclass.  This ensures that *note
     __post_init__(): 4211, if present, is also called.

     Init-only variables without default values, if any exist, must be
     specified on the call to ‘replace()’ so that they can be passed to
     ‘__init__()’ and *note __post_init__(): 4211.

     It is an error for 'changes' to contain any fields that are defined
     as having ‘init=False’.  A *note ValueError: 1e7. will be raised in
     this case.

     Be forewarned about how ‘init=False’ fields work during a call to
     ‘replace()’.  They are not copied from the source object, but
     rather are initialized in *note __post_init__(): 4211, if they're
     initialized at all.  It is expected that ‘init=False’ fields will
     be rarely and judiciously used.  If they are used, it might be wise
     to have alternate class constructors, or perhaps a custom
     ‘replace()’ (or similarly named) method which handles instance
     copying.

     Dataclass instances are also supported by generic function *note
     copy.replace(): 136.

 -- 函式: dataclasses.is_dataclass (obj)

     Return ‘True’ if its parameter is a dataclass (including subclasses
     of a dataclass) or an instance of one, otherwise return ‘False’.

     If you need to know if a class is an instance of a dataclass (and
     not a dataclass itself), then add a further check for ‘not
     isinstance(obj, type)’:

          def is_dataclass_instance(obj):
              return is_dataclass(obj) and not isinstance(obj, type)

 -- 資料: dataclasses.MISSING

     A sentinel value signifying a missing default or default_factory.

 -- 資料: dataclasses.KW_ONLY

     A sentinel value used as a type annotation.  Any fields after a
     pseudo-field with the type of ‘KW_ONLY’ are marked as keyword-only
     fields.  Note that a pseudo-field of type ‘KW_ONLY’ is otherwise
     completely ignored.  This includes the name of such a field.  By
     convention, a name of ‘_’ is used for a ‘KW_ONLY’ field.
     Keyword-only fields signify *note __init__(): 655. parameters that
     must be specified as keywords when the class is instantiated.

     In this example, the fields ‘y’ and ‘z’ will be marked as
     keyword-only fields:

          @dataclass
          class Point:
              x: float
              _: KW_ONLY
              y: float
              z: float

          p = Point(0, y=1.5, z=2.0)

     In a single dataclass, it is an error to specify more than one
     field whose type is ‘KW_ONLY’.

     在 3.10 版被加入.

 -- 例外: dataclasses.FrozenInstanceError

     Raised when an implicitly defined *note __setattr__(): 1e05. or
     *note __delattr__(): 1e06. is called on a dataclass which was
     defined with ‘frozen=True’.  It is a subclass of *note
     AttributeError: 2f6.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/90562

   (2) https://github.com/python/cpython/issues/91126


File: python.info,  Node: Post-init processing,  Next: 類別變數,  Prev: 模組內容<8>,  Up: dataclasses --- Data Classes

5.29.7.2 Post-init processing
.............................

 -- 函式: dataclasses.__post_init__ ()

     When defined on the class, it will be called by the generated *note
     __init__(): 655, normally as ‘self.__post_init__()’.  However, if
     any ‘InitVar’ fields are defined, they will also be passed to
     ‘__post_init__()’ in the order they were defined in the class.  If
     no ‘__init__()’ method is generated, then ‘__post_init__()’ will
     not automatically be called.

     Among other uses, this allows for initializing field values that
     depend on one or more other fields.  For example:

          @dataclass
          class C:
              a: float
              b: float
              c: float = field(init=False)

              def __post_init__(self):
                  self.c = self.a + self.b

The *note __init__(): 655. method generated by *note @dataclass: 1af.
does not call base class ‘__init__()’ methods.  If the base class has an
‘__init__()’ method that has to be called, it is common to call this
method in a *note __post_init__(): 4211. method:

     class Rectangle:
         def __init__(self, height, width):
             self.height = height
             self.width = width

     @dataclass
     class Square(Rectangle):
         side: float

         def __post_init__(self):
             super().__init__(self.side, self.side)

Note, however, that in general the dataclass-generated ‘__init__()’
methods don't need to be called, since the derived dataclass will take
care of initializing all fields of any base class that is a dataclass
itself.

See the section below on init-only variables for ways to pass parameters
to ‘__post_init__()’.  Also see the warning about how *note replace():
15f4. handles ‘init=False’ fields.


File: python.info,  Node: 類別變數,  Next: Init-only variables,  Prev: Post-init processing,  Up: dataclasses --- Data Classes

5.29.7.3 類別變數
.................

One of the few places where *note @dataclass: 1af. actually inspects the
type of a field is to determine if a field is a class variable as
defined in PEP 526(1).  It does this by checking if the type of the
field is *note typing.ClassVar: 24b.  If a field is a ‘ClassVar’, it is
excluded from consideration as a field and is ignored by the dataclass
mechanisms.  Such ‘ClassVar’ pseudo-fields are not returned by the
module-level *note fields(): 1641. function.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0526/


File: python.info,  Node: Init-only variables,  Next: 凍結實例,  Prev: 類別變數,  Up: dataclasses --- Data Classes

5.29.7.4 Init-only variables
............................

Another place where *note @dataclass: 1af. inspects a type annotation is
to determine if a field is an init-only variable.  It does this by
seeing if the type of a field is of type ‘dataclasses.InitVar’.  If a
field is an ‘InitVar’, it is considered a pseudo-field called an
init-only field.  As it is not a true field, it is not returned by the
module-level *note fields(): 1641. function.  Init-only fields are added
as parameters to the generated *note __init__(): 655. method, and are
passed to the optional *note __post_init__(): 4211. method.  They are
not otherwise used by dataclasses.

For example, suppose a field will be initialized from a database, if a
value is not provided when creating the class:

     @dataclass
     class C:
         i: int
         j: int | None = None
         database: InitVar[DatabaseType | None] = None

         def __post_init__(self, database):
             if self.j is None and database is not None:
                 self.j = database.lookup('j')

     c = C(10, database=my_database)

In this case, *note fields(): 1641. will return *note Field: 2132.
objects for ‘i’ and ‘j’, but not for ‘database’.


File: python.info,  Node: 凍結實例,  Next: 繼承,  Prev: Init-only variables,  Up: dataclasses --- Data Classes

5.29.7.5 凍結實例
.................

It is not possible to create truly immutable Python objects.  However,
by passing ‘frozen=True’ to the *note @dataclass: 1af. decorator you can
emulate immutability.  In that case, dataclasses will add *note
__setattr__(): 1e05. and *note __delattr__(): 1e06. methods to the
class.  These methods will raise a *note FrozenInstanceError: 4212. when
invoked.

There is a tiny performance penalty when using ‘frozen=True’: *note
__init__(): 655. cannot use simple assignment to initialize fields, and
must use ‘object.__setattr__()’.


File: python.info,  Node: 繼承,  Next: Re-ordering of keyword-only parameters in __init__,  Prev: 凍結實例,  Up: dataclasses --- Data Classes

5.29.7.6 繼承
.............

When the dataclass is being created by the *note @dataclass: 1af.
decorator, it looks through all of the class's base classes in reverse
MRO (that is, starting at *note object: a2f.) and, for each dataclass
that it finds, adds the fields from that base class to an ordered
mapping of fields.  After all of the base class fields are added, it
adds its own fields to the ordered mapping.  All of the generated
methods will use this combined, calculated ordered mapping of fields.
Because the fields are in insertion order, derived classes override base
classes.  An example:

     @dataclass
     class Base:
         x: Any = 15.0
         y: int = 0

     @dataclass
     class C(Base):
         z: int = 10
         x: int = 15

The final list of fields is, in order, ‘x’, ‘y’, ‘z’.  The final type of
‘x’ is *note int: 23c, as specified in class ‘C’.

The generated *note __init__(): 655. method for ‘C’ will look like:

     def __init__(self, x: int = 15, y: int = 0, z: int = 10):


File: python.info,  Node: Re-ordering of keyword-only parameters in __init__,  Next: 預設工廠函式,  Prev: 繼承,  Up: dataclasses --- Data Classes

5.29.7.7 Re-ordering of keyword-only parameters in ‘__init__()’
...............................................................

After the parameters needed for *note __init__(): 655. are computed, any
keyword-only parameters are moved to come after all regular
(non-keyword-only) parameters.  This is a requirement of how
keyword-only parameters are implemented in Python: they must come after
non-keyword-only parameters.

In this example, ‘Base.y’, ‘Base.w’, and ‘D.t’ are keyword-only fields,
and ‘Base.x’ and ‘D.z’ are regular fields:

     @dataclass
     class Base:
         x: Any = 15.0
         _: KW_ONLY
         y: int = 0
         w: int = 1

     @dataclass
     class D(Base):
         z: int = 10
         t: int = field(kw_only=True, default=0)

The generated ‘__init__()’ method for ‘D’ will look like:

     def __init__(self, x: Any = 15.0, z: int = 10, *, y: int = 0, w: int = 1, t: int = 0):

Note that the parameters have been re-ordered from how they appear in
the list of fields: parameters derived from regular fields are followed
by parameters derived from keyword-only fields.

The relative ordering of keyword-only parameters is maintained in the
re-ordered ‘__init__()’ parameter list.


File: python.info,  Node: 預設工廠函式,  Next: 可變預設值,  Prev: Re-ordering of keyword-only parameters in __init__,  Up: dataclasses --- Data Classes

5.29.7.8 預設工廠函式
.....................

If a *note field(): 1926. specifies a 'default_factory', it is called
with zero arguments when a default value for the field is needed.  For
example, to create a new instance of a list, use:

     mylist: list = field(default_factory=list)

If a field is excluded from *note __init__(): 655. (using ‘init=False’)
and the field also specifies 'default_factory', then the default factory
function will always be called from the generated ‘__init__()’ function.
This happens because there is no other way to give the field an initial
value.


File: python.info,  Node: 可變預設值,  Next: Descriptor-typed fields,  Prev: 預設工廠函式,  Up: dataclasses --- Data Classes

5.29.7.9 可變預設值
...................

Python stores default member variable values in class attributes.
Consider this example, not using dataclasses:

     class C:
         x = []
         def add(self, element):
             self.x.append(element)

     o1 = C()
     o2 = C()
     o1.add(1)
     o2.add(2)
     assert o1.x == [1, 2]
     assert o1.x is o2.x

Note that the two instances of class ‘C’ share the same class variable
‘x’, as expected.

Using dataclasses, 'if' this code was valid:

     @dataclass
     class D:
         x: list = []      # This code raises ValueError
         def add(self, element):
             self.x.append(element)

它會生成類似的程式碼：

     class D:
         x = []
         def __init__(self, x=x):
             self.x = x
         def add(self, element):
             self.x.append(element)

     assert D().x is D().x

This has the same issue as the original example using class ‘C’.  That
is, two instances of class ‘D’ that do not specify a value for ‘x’ when
creating a class instance will share the same copy of ‘x’.  Because
dataclasses just use normal Python class creation they also share this
behavior.  There is no general way for Data Classes to detect this
condition.  Instead, the *note @dataclass: 1af. decorator will raise a
*note ValueError: 1e7. if it detects an unhashable default parameter.
The assumption is that if a value is unhashable, it is mutable.  This is
a partial solution, but it does protect against many common errors.

Using default factory functions is a way to create new instances of
mutable types as default values for fields:

     @dataclass
     class D:
         x: list = field(default_factory=list)

     assert D().x is not D().x

在 3.11 版的變更: Instead of looking for and disallowing objects of type
*note list: 5b6, *note dict: 23b, or *note set: 57d, unhashable objects
are now not allowed as default values.  Unhashability is used to
approximate mutability.


File: python.info,  Node: Descriptor-typed fields,  Prev: 可變預設值,  Up: dataclasses --- Data Classes

5.29.7.10 Descriptor-typed fields
.................................

Fields that are assigned *note descriptor objects: bf6. as their default
value have the following special behaviors:

   * The value for the field passed to the dataclass's *note __init__():
     655. method is passed to the descriptor's *note __set__(): 1e3f.
     method rather than overwriting the descriptor object.

   * Similarly, when getting or setting the field, the descriptor's
     *note __get__(): 16c3. or ‘__set__()’ method is called rather than
     returning or overwriting the descriptor object.

   * To determine whether a field contains a default value, *note
     @dataclass: 1af. will call the descriptor's ‘__get__()’ method
     using its class access form: ‘descriptor.__get__(obj=None,
     type=cls)’.  If the descriptor returns a value in this case, it
     will be used as the field's default.  On the other hand, if the
     descriptor raises *note AttributeError: 2f6. in this situation, no
     default value will be provided for the field.

     class IntConversionDescriptor:
         def __init__(self, *, default):
             self._default = default

         def __set_name__(self, owner, name):
             self._name = "_" + name

         def __get__(self, obj, type):
             if obj is None:
                 return self._default

             return getattr(obj, self._name, self._default)

         def __set__(self, obj, value):
             setattr(obj, self._name, int(value))

     @dataclass
     class InventoryItem:
         quantity_on_hand: IntConversionDescriptor = IntConversionDescriptor(default=100)

     i = InventoryItem()
     print(i.quantity_on_hand)   # 100
     i.quantity_on_hand = 2.5    # calls __set__ with 2.5
     print(i.quantity_on_hand)   # 2

Note that if a field is annotated with a descriptor type, but is not
assigned a descriptor object as its default value, the field will act
like a normal field.


File: python.info,  Node: contextlib --- Utilities for with-statement contexts,  Next: abc --- 抽象基底類別,  Prev: dataclasses --- Data Classes,  Up: Python Runtime 服務

5.29.8 ‘contextlib’ -- Utilities for ‘with’-statement contexts
--------------------------------------------------------------

'原始碼：'Lib/contextlib.py(1)

__________________________________________________________________

This module provides utilities for common tasks involving the *note
with: 577. statement.  For more information see also *note
情境管理器型別: 1e95. and *note With Statement Context Managers: 1e93.

* Menu:

* Utilities::
* Examples and Recipes: Examples and Recipes<2>.
* Single use, reusable and reentrant context managers: Single use reusable and reentrant context managers.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/contextlib.py


File: python.info,  Node: Utilities,  Next: Examples and Recipes<2>,  Up: contextlib --- Utilities for with-statement contexts

5.29.8.1 Utilities
..................

Functions and classes provided:

 -- 類別: contextlib.AbstractContextManager

     An *note abstract base class: 114e. for classes that implement
     *note object.__enter__(): 56c. and *note object.__exit__(): 1293.
     A default implementation for *note object.__enter__(): 56c. is
     provided which returns ‘self’ while *note object.__exit__(): 1293.
     is an abstract method which by default returns ‘None’.  See also
     the definition of *note 情境管理器型別: 1e95.

     在 3.6 版被加入.

 -- 類別: contextlib.AbstractAsyncContextManager

     An *note abstract base class: 114e. for classes that implement
     *note object.__aenter__(): 1ea6. and *note object.__aexit__():
     151e.  A default implementation for *note object.__aenter__():
     1ea6. is provided which returns ‘self’ while *note
     object.__aexit__(): 151e. is an abstract method which by default
     returns ‘None’.  See also the definition of *note Asynchronous
     Context Managers: 5a0.

     在 3.7 版被加入.

 -- 函式: @contextlib.contextmanager

     This function is a *note decorator: 6d5. that can be used to define
     a factory function for *note with: 577. statement context managers,
     without needing to create a class or separate *note __enter__():
     56c. and *note __exit__(): 1293. methods.

     While many objects natively support use in with statements,
     sometimes a resource needs to be managed that isn't a context
     manager in its own right, and doesn't implement a ‘close()’ method
     for use with ‘contextlib.closing’

     An abstract example would be the following to ensure correct
     resource management:

          from contextlib import contextmanager

          @contextmanager
          def managed_resource(*args, **kwds):
              # Code to acquire resource, e.g.:
              resource = acquire_resource(*args, **kwds)
              try:
                  yield resource
              finally:
                  # Code to release resource, e.g.:
                  release_resource(resource)

     The function can then be used like this:

          >>> with managed_resource(timeout=3600) as resource:
          ...     # Resource is released at the end of this block,
          ...     # even if code in the block raises an exception

     The function being decorated must return a *note generator:
     1004.-iterator when called.  This iterator must yield exactly one
     value, which will be bound to the targets in the *note with: 577.
     statement's ‘as’ clause, if any.

     At the point where the generator yields, the block nested in the
     *note with: 577. statement is executed.  The generator is then
     resumed after the block is exited.  If an unhandled exception
     occurs in the block, it is reraised inside the generator at the
     point where the yield occurred.  Thus, you can use a *note try:
     68c...*note except: 171...*note finally: 96e. statement to trap the
     error (if any), or ensure that some cleanup takes place.  If an
     exception is trapped merely in order to log it or to perform some
     action (rather than to suppress it entirely), the generator must
     reraise that exception.  Otherwise the generator context manager
     will indicate to the ‘with’ statement that the exception has been
     handled, and execution will resume with the statement immediately
     following the ‘with’ statement.

     *note contextmanager(): 119a. uses *note ContextDecorator: 1199. so
     the context managers it creates can be used as decorators as well
     as in *note with: 577. statements.  When used as a decorator, a new
     generator instance is implicitly created on each function call
     (this allows the otherwise "one-shot" context managers created by
     *note contextmanager(): 119a. to meet the requirement that context
     managers support multiple invocations in order to be used as
     decorators).

     在 3.2 版的變更: Use of *note ContextDecorator: 1199.

 -- 函式: @contextlib.asynccontextmanager

          Similar to *note contextmanager(): 119a, but creates an *note
          asynchronous context manager: 5a0.

          This function is a *note decorator: 6d5. that can be used to
          define a factory function for *note async with: 57a. statement
          asynchronous context managers, without needing to create a
          class or separate *note __aenter__(): 1ea6. and *note
          __aexit__(): 151e. methods.  It must be applied to an *note
          asynchronous generator: 1f14. function.

          一個簡單範例：

               from contextlib import asynccontextmanager

               @asynccontextmanager
               async def get_connection():
                   conn = await acquire_db_connection()
                   try:
                       yield conn
                   finally:
                       await release_db_connection(conn)

               async def get_all_users():
                   async with get_connection() as conn:
                       return conn.query('SELECT ...')

          在 3.7 版被加入.

          Context managers defined with *note asynccontextmanager():
          ace. can be used either as decorators or with *note async
          with: 57a. statements:

               import time
               from contextlib import asynccontextmanager

               @asynccontextmanager
               async def timeit():
                   now = time.monotonic()
                   try:
                       yield
                   finally:
                       print(f'it took {time.monotonic() - now}s to run')

               @timeit()
               async def main():
                   # ... async code ...

          When used as a decorator, a new generator instance is
          implicitly created on each function call.  This allows the
          otherwise "one-shot" context managers created by *note
          asynccontextmanager(): ace. to meet the requirement that
          context managers support multiple invocations in order to be
          used as decorators.

     在 3.10 版的變更: Async context managers created with *note
     asynccontextmanager(): ace. can be used as decorators.

 -- 函式: contextlib.closing (thing)

     Return a context manager that closes 'thing' upon completion of the
     block.  This is basically equivalent to:

          from contextlib import contextmanager

          @contextmanager
          def closing(thing):
              try:
                  yield thing
              finally:
                  thing.close()

     And lets you write code like this:

          from contextlib import closing
          from urllib.request import urlopen

          with closing(urlopen('https://www.python.org')) as page:
              for line in page:
                  print(line)

     without needing to explicitly close ‘page’.  Even if an error
     occurs, ‘page.close()’ will be called when the *note with: 577.
     block is exited.

          備註: Most types managing resources support the *note context
          manager: 576. protocol, which closes 'thing' on leaving the
          *note with: 577. statement.  As such, ‘closing()’ is most
          useful for third party types that don't support context
          managers.  This example is purely for illustration purposes,
          as *note urlopen(): 275. would normally be used in a context
          manager.

 -- 函式: contextlib.aclosing (thing)

     Return an async context manager that calls the ‘aclose()’ method of
     'thing' upon completion of the block.  This is basically equivalent
     to:

          from contextlib import asynccontextmanager

          @asynccontextmanager
          async def aclosing(thing):
              try:
                  yield thing
              finally:
                  await thing.aclose()

     Significantly, ‘aclosing()’ supports deterministic cleanup of async
     generators when they happen to exit early by *note break: a4c. or
     an exception.  For example:

          from contextlib import aclosing

          async with aclosing(my_generator()) as values:
              async for value in values:
                  if value == 42:
                      break

     This pattern ensures that the generator's async exit code is
     executed in the same context as its iterations (so that exceptions
     and context variables work as expected, and the exit code isn't run
     after the lifetime of some task it depends on).

     在 3.10 版被加入.

 -- 函式: contextlib.nullcontext (enter_result=None)

     Return a context manager that returns 'enter_result' from
     ‘__enter__’, but otherwise does nothing.  It is intended to be used
     as a stand-in for an optional context manager, for example:

          def myfunction(arg, ignore_exceptions=False):
              if ignore_exceptions:
                  # Use suppress to ignore all exceptions.
                  cm = contextlib.suppress(Exception)
              else:
                  # Do not ignore any exceptions, cm has no effect.
                  cm = contextlib.nullcontext()
              with cm:
                  # Do something

     一個使用 'enter_result' 的範例：

          def process_file(file_or_path):
              if isinstance(file_or_path, str):
                  # If string, open file
                  cm = open(file_or_path)
              else:
                  # Caller is responsible for closing file
                  cm = nullcontext(file_or_path)

              with cm as file:
                  # Perform processing on the file

     It can also be used as a stand-in for *note asynchronous context
     managers: 5a0.:

          async def send_http(session=None):
              if not session:
                  # If no http session, create it with aiohttp
                  cm = aiohttp.ClientSession()
              else:
                  # Caller is responsible for closing the session
                  cm = nullcontext(session)

              async with cm as session:
                  # Send http requests with session

     在 3.7 版被加入.

     在 3.10 版的變更: *note asynchronous context manager: 579. support
     was added.

 -- 函式: contextlib.suppress (*exceptions)

     Return a context manager that suppresses any of the specified
     exceptions if they occur in the body of a ‘with’ statement and then
     resumes execution with the first statement following the end of the
     ‘with’ statement.

     As with any other mechanism that completely suppresses exceptions,
     this context manager should be used only to cover very specific
     errors where silently continuing with program execution is known to
     be the right thing to do.

     舉例來說：

          from contextlib import suppress

          with suppress(FileNotFoundError):
              os.remove('somefile.tmp')

          with suppress(FileNotFoundError):
              os.remove('someotherfile.tmp')

     This code is equivalent to:

          try:
              os.remove('somefile.tmp')
          except FileNotFoundError:
              pass

          try:
              os.remove('someotherfile.tmp')
          except FileNotFoundError:
              pass

     This context manager is *note reentrant: 4225.

     If the code within the ‘with’ block raises a *note
     BaseExceptionGroup: 244, suppressed exceptions are removed from the
     group.  Any exceptions of the group which are not suppressed are
     re-raised in a new group which is created using the original
     group's *note derive(): 15b8. method.

     在 3.4 版被加入.

     在 3.12 版的變更: ‘suppress’ now supports suppressing exceptions
     raised as part of a *note BaseExceptionGroup: 244.

 -- 函式: contextlib.redirect_stdout (new_target)

     Context manager for temporarily redirecting *note sys.stdout: a79.
     to another file or file-like object.

     This tool adds flexibility to existing functions or classes whose
     output is hardwired to stdout.

     For example, the output of *note help(): 87c. normally is sent to
     'sys.stdout'.  You can capture that output in a string by
     redirecting the output to an *note io.StringIO: ecb. object.  The
     replacement stream is returned from the ‘__enter__’ method and so
     is available as the target of the *note with: 577. statement:

          with redirect_stdout(io.StringIO()) as f:
              help(pow)
          s = f.getvalue()

     To send the output of *note help(): 87c. to a file on disk,
     redirect the output to a regular file:

          with open('help.txt', 'w') as f:
              with redirect_stdout(f):
                  help(pow)

     To send the output of *note help(): 87c. to 'sys.stderr':

          with redirect_stdout(sys.stderr):
              help(pow)

     Note that the global side effect on *note sys.stdout: a79. means
     that this context manager is not suitable for use in library code
     and most threaded applications.  It also has no effect on the
     output of subprocesses.  However, it is still a useful approach for
     many utility scripts.

     This context manager is *note reentrant: 4225.

     在 3.4 版被加入.

 -- 函式: contextlib.redirect_stderr (new_target)

     Similar to *note redirect_stdout(): d8e. but redirecting *note
     sys.stderr: 8dd. to another file or file-like object.

     This context manager is *note reentrant: 4225.

     在 3.5 版被加入.

 -- 函式: contextlib.chdir (path)

     Non parallel-safe context manager to change the current working
     directory.  As this changes a global state, the working directory,
     it is not suitable for use in most threaded or async contexts.  It
     is also not suitable for most non-linear code execution, like
     generators, where the program execution is temporarily relinquished
     - unless explicitly desired, you should not yield when this context
     manager is active.

     This is a simple wrapper around *note chdir(): 5b2, it changes the
     current working directory upon entering and restores the old one on
     exit.

     This context manager is *note reentrant: 4225.

     在 3.11 版被加入.

 -- 類別: contextlib.ContextDecorator

     A base class that enables a context manager to also be used as a
     decorator.

     Context managers inheriting from ‘ContextDecorator’ have to
     implement ‘__enter__’ and ‘__exit__’ as normal.  ‘__exit__’ retains
     its optional exception handling even when used as a decorator.

     ‘ContextDecorator’ is used by *note contextmanager(): 119a, so you
     get this functionality automatically.

     ‘ContextDecorator’ 範例：

          from contextlib import ContextDecorator

          class mycontext(ContextDecorator):
              def __enter__(self):
                  print('Starting')
                  return self

              def __exit__(self, *exc):
                  print('Finishing')
                  return False

     The class can then be used like this:

          >>> @mycontext()
          ... def function():
          ...     print('The bit in the middle')
          ...
          >>> function()
          Starting
          The bit in the middle
          Finishing

          >>> with mycontext():
          ...     print('The bit in the middle')
          ...
          Starting
          The bit in the middle
          Finishing

     This change is just syntactic sugar for any construct of the
     following form:

          def f():
              with cm():
                  # Do stuff

     ‘ContextDecorator’ lets you instead write:

          @cm()
          def f():
              # Do stuff

     It makes it clear that the ‘cm’ applies to the whole function,
     rather than just a piece of it (and saving an indentation level is
     nice, too).

     Existing context managers that already have a base class can be
     extended by using ‘ContextDecorator’ as a mixin class:

          from contextlib import ContextDecorator

          class mycontext(ContextBaseClass, ContextDecorator):
              def __enter__(self):
                  return self

              def __exit__(self, *exc):
                  return False

          備註: As the decorated function must be able to be called
          multiple times, the underlying context manager must support
          use in multiple *note with: 577. statements.  If this is not
          the case, then the original construct with the explicit ‘with’
          statement inside the function should be used.

     在 3.2 版被加入.

 -- 類別: contextlib.AsyncContextDecorator

     Similar to *note ContextDecorator: 1199. but only for asynchronous
     functions.

     ‘AsyncContextDecorator’ 範例：

          from asyncio import run
          from contextlib import AsyncContextDecorator

          class mycontext(AsyncContextDecorator):
              async def __aenter__(self):
                  print('Starting')
                  return self

              async def __aexit__(self, *exc):
                  print('Finishing')
                  return False

     The class can then be used like this:

          >>> @mycontext()
          ... async def function():
          ...     print('The bit in the middle')
          ...
          >>> run(function())
          Starting
          The bit in the middle
          Finishing

          >>> async def function():
          ...    async with mycontext():
          ...         print('The bit in the middle')
          ...
          >>> run(function())
          Starting
          The bit in the middle
          Finishing

     在 3.10 版被加入.

 -- 類別: contextlib.ExitStack

     A context manager that is designed to make it easy to
     programmatically combine other context managers and cleanup
     functions, especially those that are optional or otherwise driven
     by input data.

     For example, a set of files may easily be handled in a single with
     statement as follows:

          with ExitStack() as stack:
              files = [stack.enter_context(open(fname)) for fname in filenames]
              # All opened files will automatically be closed at the end of
              # the with statement, even if attempts to open files later
              # in the list raise an exception

     The *note __enter__(): 56c. method returns the *note ExitStack:
     acd. instance, and performs no additional operations.

     Each instance maintains a stack of registered callbacks that are
     called in reverse order when the instance is closed (either
     explicitly or implicitly at the end of a *note with: 577.
     statement).  Note that callbacks are 'not' invoked implicitly when
     the context stack instance is garbage collected.

     This stack model is used so that context managers that acquire
     their resources in their ‘__init__’ method (such as file objects)
     can be handled correctly.

     Since registered callbacks are invoked in the reverse order of
     registration, this ends up behaving as if multiple nested *note
     with: 577. statements had been used with the registered set of
     callbacks.  This even extends to exception handling - if an inner
     callback suppresses or replaces an exception, then outer callbacks
     will be passed arguments based on that updated state.

     This is a relatively low level API that takes care of the details
     of correctly unwinding the stack of exit callbacks.  It provides a
     suitable foundation for higher level context managers that
     manipulate the exit stack in application specific ways.

     在 3.3 版被加入.

      -- 方法: enter_context (cm)

          Enters a new context manager and adds its *note __exit__():
          1293. method to the callback stack.  The return value is the
          result of the context manager's own *note __enter__(): 56c.
          method.

          These context managers may suppress exceptions just as they
          normally would if used directly as part of a *note with: 577.
          statement.

          在 3.11 版的變更: Raises *note TypeError: 4dd. instead of
          *note AttributeError: 2f6. if 'cm' is not a context manager.

      -- 方法: push (exit)

          Adds a context manager's *note __exit__(): 1293. method to the
          callback stack.

          As ‘__enter__’ is 'not' invoked, this method can be used to
          cover part of an *note __enter__(): 56c. implementation with a
          context manager's own *note __exit__(): 1293. method.

          If passed an object that is not a context manager, this method
          assumes it is a callback with the same signature as a context
          manager's *note __exit__(): 1293. method and adds it directly
          to the callback stack.

          By returning true values, these callbacks can suppress
          exceptions the same way context manager *note __exit__():
          1293. methods can.

          The passed in object is returned from the function, allowing
          this method to be used as a function decorator.

      -- 方法: callback (callback, /, *args, **kwds)

          Accepts an arbitrary callback function and arguments and adds
          it to the callback stack.

          Unlike the other methods, callbacks added this way cannot
          suppress exceptions (as they are never passed the exception
          details).

          The passed in callback is returned from the function, allowing
          this method to be used as a function decorator.

      -- 方法: pop_all ()

          Transfers the callback stack to a fresh *note ExitStack: acd.
          instance and returns it.  No callbacks are invoked by this
          operation - instead, they will now be invoked when the new
          stack is closed (either explicitly or implicitly at the end of
          a *note with: 577. statement).

          For example, a group of files can be opened as an "all or
          nothing" operation as follows:

               with ExitStack() as stack:
                   files = [stack.enter_context(open(fname)) for fname in filenames]
                   # Hold onto the close method, but don't call it yet.
                   close_files = stack.pop_all().close
                   # If opening any file fails, all previously opened files will be
                   # closed automatically. If all files are opened successfully,
                   # they will remain open even after the with statement ends.
                   # close_files() can then be invoked explicitly to close them all.

      -- 方法: close ()

          Immediately unwinds the callback stack, invoking callbacks in
          the reverse order of registration.  For any context managers
          and exit callbacks registered, the arguments passed in will
          indicate that no exception occurred.

 -- 類別: contextlib.AsyncExitStack

     An *note asynchronous context manager: 5a0, similar to *note
     ExitStack: acd, that supports combining both synchronous and
     asynchronous context managers, as well as having coroutines for
     cleanup logic.

     The *note close(): 4228. method is not implemented; *note aclose():
     4229. must be used instead.

      -- 方法: coroutine enter_async_context (cm)

          Similar to *note ExitStack.enter_context(): 578. but expects
          an asynchronous context manager.

          在 3.11 版的變更: Raises *note TypeError: 4dd. instead of
          *note AttributeError: 2f6. if 'cm' is not an asynchronous
          context manager.

      -- 方法: push_async_exit (exit)

          Similar to *note ExitStack.push(): 4226. but expects either an
          asynchronous context manager or a coroutine function.

      -- 方法: push_async_callback (callback, /, *args, **kwds)

          Similar to *note ExitStack.callback(): a26. but expects a
          coroutine function.

      -- 方法: coroutine aclose ()

          Similar to *note ExitStack.close(): 4228. but properly handles
          awaitables.

     Continuing the example for *note asynccontextmanager(): ace.:

          async with AsyncExitStack() as stack:
              connections = [await stack.enter_async_context(get_connection())
                  for i in range(5)]
              # All opened connections will automatically be released at the end of
              # the async with statement, even if attempts to open a connection
              # later in the list raise an exception.

     在 3.7 版被加入.


File: python.info,  Node: Examples and Recipes<2>,  Next: Single use reusable and reentrant context managers,  Prev: Utilities,  Up: contextlib --- Utilities for with-statement contexts

5.29.8.2 Examples and Recipes
.............................

This section describes some examples and recipes for making effective
use of the tools provided by *note contextlib: 1c.

* Menu:

* Supporting a variable number of context managers::
* Catching exceptions from __enter__ methods::
* Cleaning up in an __enter__ implementation::
* Replacing any use of try-finally and flag variables::
* Using a context manager as a function decorator::


File: python.info,  Node: Supporting a variable number of context managers,  Next: Catching exceptions from __enter__ methods,  Up: Examples and Recipes<2>

5.29.8.3 Supporting a variable number of context managers
.........................................................

The primary use case for *note ExitStack: acd. is the one given in the
class documentation: supporting a variable number of context managers
and other cleanup operations in a single *note with: 577. statement.
The variability may come from the number of context managers needed
being driven by user input (such as opening a user specified collection
of files), or from some of the context managers being optional:

     with ExitStack() as stack:
         for resource in resources:
             stack.enter_context(resource)
         if need_special_resource():
             special = acquire_special_resource()
             stack.callback(release_special_resource, special)
         # Perform operations that use the acquired resources

As shown, *note ExitStack: acd. also makes it quite easy to use *note
with: 577. statements to manage arbitrary resources that don't natively
support the context management protocol.


File: python.info,  Node: Catching exceptions from __enter__ methods,  Next: Cleaning up in an __enter__ implementation,  Prev: Supporting a variable number of context managers,  Up: Examples and Recipes<2>

5.29.8.4 Catching exceptions from ‘__enter__’ methods
.....................................................

It is occasionally desirable to catch exceptions from an ‘__enter__’
method implementation, 'without' inadvertently catching exceptions from
the *note with: 577. statement body or the context manager's ‘__exit__’
method.  By using *note ExitStack: acd. the steps in the context
management protocol can be separated slightly in order to allow this:

     stack = ExitStack()
     try:
         x = stack.enter_context(cm)
     except Exception:
         # handle __enter__ exception
     else:
         with stack:
             # Handle normal case

Actually needing to do this is likely to indicate that the underlying
API should be providing a direct resource management interface for use
with *note try: 68c./*note except: 171./*note finally: 96e. statements,
but not all APIs are well designed in that regard.  When a context
manager is the only resource management API provided, then *note
ExitStack: acd. can make it easier to handle various situations that
can't be handled directly in a *note with: 577. statement.


File: python.info,  Node: Cleaning up in an __enter__ implementation,  Next: Replacing any use of try-finally and flag variables,  Prev: Catching exceptions from __enter__ methods,  Up: Examples and Recipes<2>

5.29.8.5 Cleaning up in an ‘__enter__’ implementation
.....................................................

As noted in the documentation of *note ExitStack.push(): 4226, this
method can be useful in cleaning up an already allocated resource if
later steps in the *note __enter__(): 56c. implementation fail.

Here's an example of doing this for a context manager that accepts
resource acquisition and release functions, along with an optional
validation function, and maps them to the context management protocol:

     from contextlib import contextmanager, AbstractContextManager, ExitStack

     class ResourceManager(AbstractContextManager):

         def __init__(self, acquire_resource, release_resource, check_resource_ok=None):
             self.acquire_resource = acquire_resource
             self.release_resource = release_resource
             if check_resource_ok is None:
                 def check_resource_ok(resource):
                     return True
             self.check_resource_ok = check_resource_ok

         @contextmanager
         def _cleanup_on_error(self):
             with ExitStack() as stack:
                 stack.push(self)
                 yield
                 # The validation check passed and didn't raise an exception
                 # Accordingly, we want to keep the resource, and pass it
                 # back to our caller
                 stack.pop_all()

         def __enter__(self):
             resource = self.acquire_resource()
             with self._cleanup_on_error():
                 if not self.check_resource_ok(resource):
                     msg = "Failed validation for {!r}"
                     raise RuntimeError(msg.format(resource))
             return resource

         def __exit__(self, *exc_details):
             # We don't need to duplicate any of our resource release logic
             self.release_resource()


File: python.info,  Node: Replacing any use of try-finally and flag variables,  Next: Using a context manager as a function decorator,  Prev: Cleaning up in an __enter__ implementation,  Up: Examples and Recipes<2>

5.29.8.6 Replacing any use of ‘try-finally’ and flag variables
..............................................................

A pattern you will sometimes see is a ‘try-finally’ statement with a
flag variable to indicate whether or not the body of the ‘finally’
clause should be executed.  In its simplest form (that can't already be
handled just by using an ‘except’ clause instead), it looks something
like this:

     cleanup_needed = True
     try:
         result = perform_operation()
         if result:
             cleanup_needed = False
     finally:
         if cleanup_needed:
             cleanup_resources()

As with any ‘try’ statement based code, this can cause problems for
development and review, because the setup code and the cleanup code can
end up being separated by arbitrarily long sections of code.

*note ExitStack: acd. makes it possible to instead register a callback
for execution at the end of a ‘with’ statement, and then later decide to
skip executing that callback:

     from contextlib import ExitStack

     with ExitStack() as stack:
         stack.callback(cleanup_resources)
         result = perform_operation()
         if result:
             stack.pop_all()

This allows the intended cleanup behaviour to be made explicit up front,
rather than requiring a separate flag variable.

If a particular application uses this pattern a lot, it can be
simplified even further by means of a small helper class:

     from contextlib import ExitStack

     class Callback(ExitStack):
         def __init__(self, callback, /, *args, **kwds):
             super().__init__()
             self.callback(callback, *args, **kwds)

         def cancel(self):
             self.pop_all()

     with Callback(cleanup_resources) as cb:
         result = perform_operation()
         if result:
             cb.cancel()

If the resource cleanup isn't already neatly bundled into a standalone
function, then it is still possible to use the decorator form of *note
ExitStack.callback(): a26. to declare the resource cleanup in advance:

     from contextlib import ExitStack

     with ExitStack() as stack:
         @stack.callback
         def cleanup_resources():
             ...
         result = perform_operation()
         if result:
             stack.pop_all()

Due to the way the decorator protocol works, a callback function
declared this way cannot take any parameters.  Instead, any resources to
be released must be accessed as closure variables.


File: python.info,  Node: Using a context manager as a function decorator,  Prev: Replacing any use of try-finally and flag variables,  Up: Examples and Recipes<2>

5.29.8.7 Using a context manager as a function decorator
........................................................

*note ContextDecorator: 1199. makes it possible to use a context manager
in both an ordinary ‘with’ statement and also as a function decorator.

For example, it is sometimes useful to wrap functions or groups of
statements with a logger that can track the time of entry and time of
exit.  Rather than writing both a function decorator and a context
manager for the task, inheriting from *note ContextDecorator: 1199.
provides both capabilities in a single definition:

     from contextlib import ContextDecorator
     import logging

     logging.basicConfig(level=logging.INFO)

     class track_entry_and_exit(ContextDecorator):
         def __init__(self, name):
             self.name = name

         def __enter__(self):
             logging.info('Entering: %s', self.name)

         def __exit__(self, exc_type, exc, exc_tb):
             logging.info('Exiting: %s', self.name)

Instances of this class can be used as both a context manager:

     with track_entry_and_exit('widget loader'):
         print('Some time consuming activity goes here')
         load_widget()

And also as a function decorator:

     @track_entry_and_exit('widget loader')
     def activity():
         print('Some time consuming activity goes here')
         load_widget()

Note that there is one additional limitation when using context managers
as function decorators: there's no way to access the return value of
*note __enter__(): 56c.  If that value is needed, then it is still
necessary to use an explicit ‘with’ statement.

也參考
......

PEP 343(1) - "with" 陳述式

     The specification, background, and examples for the Python *note
     with: 577. statement.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0343/


File: python.info,  Node: Single use reusable and reentrant context managers,  Prev: Examples and Recipes<2>,  Up: contextlib --- Utilities for with-statement contexts

5.29.8.8 Single use, reusable and reentrant context managers
............................................................

Most context managers are written in a way that means they can only be
used effectively in a *note with: 577. statement once.  These single use
context managers must be created afresh each time they're used -
attempting to use them a second time will trigger an exception or
otherwise not work correctly.

This common limitation means that it is generally advisable to create
context managers directly in the header of the *note with: 577.
statement where they are used (as shown in all of the usage examples
above).

Files are an example of effectively single use context managers, since
the first *note with: 577. statement will close the file, preventing any
further IO operations using that file object.

Context managers created using *note contextmanager(): 119a. are also
single use context managers, and will complain about the underlying
generator failing to yield if an attempt is made to use them a second
time:

     >>> from contextlib import contextmanager
     >>> @contextmanager
     ... def singleuse():
     ...     print("Before")
     ...     yield
     ...     print("After")
     ...
     >>> cm = singleuse()
     >>> with cm:
     ...     pass
     ...
     Before
     After
     >>> with cm:
     ...     pass
     ...
     Traceback (most recent call last):
         ...
     RuntimeError: generator didn't yield

* Menu:

* Reentrant context managers::
* Reusable context managers::


File: python.info,  Node: Reentrant context managers,  Next: Reusable context managers,  Up: Single use reusable and reentrant context managers

5.29.8.9 Reentrant context managers
...................................

More sophisticated context managers may be "reentrant".  These context
managers can not only be used in multiple *note with: 577. statements,
but may also be used 'inside' a ‘with’ statement that is already using
the same context manager.

*note threading.RLock: 2be. is an example of a reentrant context
manager, as are *note suppress(): eca, *note redirect_stdout(): d8e, and
*note chdir(): 5b1.  Here's a very simple example of reentrant use:

     >>> from contextlib import redirect_stdout
     >>> from io import StringIO
     >>> stream = StringIO()
     >>> write_to_stream = redirect_stdout(stream)
     >>> with write_to_stream:
     ...     print("This is written to the stream rather than stdout")
     ...     with write_to_stream:
     ...         print("This is also written to the stream")
     ...
     >>> print("This is written directly to stdout")
     This is written directly to stdout
     >>> print(stream.getvalue())
     This is written to the stream rather than stdout
     This is also written to the stream

Real world examples of reentrancy are more likely to involve multiple
functions calling each other and hence be far more complicated than this
example.

Note also that being reentrant is 'not' the same thing as being thread
safe.  *note redirect_stdout(): d8e, for example, is definitely not
thread safe, as it makes a global modification to the system state by
binding *note sys.stdout: a79. to a different stream.


File: python.info,  Node: Reusable context managers,  Prev: Reentrant context managers,  Up: Single use reusable and reentrant context managers

5.29.8.10 Reusable context managers
...................................

Distinct from both single use and reentrant context managers are
"reusable" context managers (or, to be completely explicit, "reusable,
but not reentrant" context managers, since reentrant context managers
are also reusable).  These context managers support being used multiple
times, but will fail (or otherwise not work correctly) if the specific
context manager instance has already been used in a containing with
statement.

*note threading.Lock: 156d. is an example of a reusable, but not
reentrant, context manager (for a reentrant lock, it is necessary to use
*note threading.RLock: 2be. instead).

Another example of a reusable, but not reentrant, context manager is
*note ExitStack: acd, as it invokes 'all' currently registered callbacks
when leaving any with statement, regardless of where those callbacks
were added:

     >>> from contextlib import ExitStack
     >>> stack = ExitStack()
     >>> with stack:
     ...     stack.callback(print, "Callback: from first context")
     ...     print("Leaving first context")
     ...
     Leaving first context
     Callback: from first context
     >>> with stack:
     ...     stack.callback(print, "Callback: from second context")
     ...     print("Leaving second context")
     ...
     Leaving second context
     Callback: from second context
     >>> with stack:
     ...     stack.callback(print, "Callback: from outer context")
     ...     with stack:
     ...         stack.callback(print, "Callback: from inner context")
     ...         print("Leaving inner context")
     ...     print("Leaving outer context")
     ...
     Leaving inner context
     Callback: from inner context
     Callback: from outer context
     Leaving outer context

As the output from the example shows, reusing a single stack object
across multiple with statements works correctly, but attempting to nest
them will cause the stack to be cleared at the end of the innermost with
statement, which is unlikely to be desirable behaviour.

Using separate *note ExitStack: acd. instances instead of reusing a
single instance avoids that problem:

     >>> from contextlib import ExitStack
     >>> with ExitStack() as outer_stack:
     ...     outer_stack.callback(print, "Callback: from outer context")
     ...     with ExitStack() as inner_stack:
     ...         inner_stack.callback(print, "Callback: from inner context")
     ...         print("Leaving inner context")
     ...     print("Leaving outer context")
     ...
     Leaving inner context
     Callback: from inner context
     Leaving outer context
     Callback: from outer context


File: python.info,  Node: abc --- 抽象基底類別,  Next: atexit --- 退出處理函式,  Prev: contextlib --- Utilities for with-statement contexts,  Up: Python Runtime 服務

5.29.9 ‘abc’ -- 抽象基底類別
----------------------------

'原始碼：'Lib/abc.py(1)

__________________________________________________________________

如同在 PEP 3119(2) 中所述，該模組提供了在 Python 中定義*note
抽象基底類別: 114e. (ABC) 的基礎元件；若想瞭解為什麼需要在 Python 中增加
這個模組，請見 PEP 文件。（也請見 PEP 3141(3) 以及 *note numbers: 8e. 模
組以瞭解基於 ABC 的數字型別階層關係。）

*note collections: 16. 模組中有一些衍生自 ABC 的具體類別；當然這些類別還
可以進一步衍生出其他類別。此外，*note collections.abc: 17. 子模組中有一
些 ABC 可被用於測試一個類別或實例是否提供特定介面，例如它是否*note 可雜湊
(hashable): 5b5. 或它是否為*note 對映: 1154.。

該模組提供了一個用來定義 ABC 的元類別 (metaclass) *note ABCMeta: ebc. 和
另一個以繼承的方式定義 ABC 的工具類別 *note ABC: ebb.：

 -- 類別: abc.ABC

     一個使用 *note ABCMeta: ebc. 作為元類別的工具類別。抽象基底類別可以
     透過自 ‘ABC’ 衍生而建立，這就避免了在某些情況下會令人混淆的元類別用
     法，用法如以下範例：

          from abc import ABC

          class MyABC(ABC):
              pass

     注意 ‘ABC’ 的型別仍然是 *note ABCMeta: ebc.，因此繼承 ‘ABC’ 仍然需
     要關注使用元類別的注意事項，如多重繼承可能會導致元類別衝突。當然你
     也可以傳入元類別關鍵字並直接使用 ‘ABCMeta’ 來定義一個抽象基底類別，
     例如：

          from abc import ABCMeta

          class MyABC(metaclass=ABCMeta):
              pass

     在 3.4 版被加入.

 -- 類別: abc.ABCMeta

     用於定義抽象基底類別（ABC）的元類別。

     使用該元類別以建立一個 ABC。一個 ABC 可以像 mix-in 類別一樣直接被子
     類別繼承。你也可以將不相關的具體類別（甚至是內建類別）和 ABC 註冊為
     「虛擬子類別 (virtual subclass)」 —— 這些類別以及它們的子類別會被內
     建函式 *note issubclass(): 765. 識別為已註冊 ABC 的子類別，但是該
     ABC 不會出現在其 MRO（Method Resolution Order，方法解析順序）中，由
     該 ABC 所定義的方法實作也不可呼叫（即使透過 *note super(): 483. 呼
     叫也不行）。(4)

     使用 ‘ABCMeta’ 作為元類別建立的類別含有以下的方法：

      -- 方法: register (subclass)

          將'子類別'註冊為該 ABC 的「抽象子類別」，例如：

               from abc import ABC

               class MyABC(ABC):
                   pass

               MyABC.register(tuple)

               assert issubclass(tuple, MyABC)
               assert isinstance((), MyABC)

          在 3.3 版的變更: 回傳已註冊的子類別，使其能夠作為類別裝飾器。

          在 3.4 版的變更: 你可以使用 *note get_cache_token(): eba. 函式
          來檢測對 ‘register()’ 的呼叫。

     你也可以覆寫 (override) 虛擬基底類別中的這個方法：

      -- 方法: __subclasshook__ (subclass)

          （必須定義為類別方法。）

          檢查 'subclass' 是否該被認為是該 ABC 的子類別，也就是說你可以
          直接自訂 *note issubclass(): 765. 的行為，而不用對於那些你希望
          定義為該 ABC 的子類別的類別都個別呼叫 *note register(): 102a.
          方法。（這個類別方法是在 ABC 的 *note __subclasscheck__():
          1e54. 方法中呼叫。）

          此方法必須回傳 ‘True’、‘False’ 或是 *note NotImplemented:
          776.。如果回傳 ‘True’，'subclass' 就會被認為是這個 ABC 的子類
          別。如果回傳 ‘False’，'subclass' 就會被判定並非該 ABC 的子類別
          ，即便正常情況應如此。如果回傳 ‘NotImplemented’，子類別檢查會
          按照正常機制繼續執行。

     為了對這些概念做一演示，請見以下定義 ABC 的範例：

          class Foo:
              def __getitem__(self, index):
                  ...
              def __len__(self):
                  ...
              def get_iterator(self):
                  return iter(self)

          class MyIterable(ABC):

              @abstractmethod
              def __iter__(self):
                  while False:
                      yield None

              def get_iterator(self):
                  return self.__iter__()

              @classmethod
              def __subclasshook__(cls, C):
                  if cls is MyIterable:
                      if any("__iter__" in B.__dict__ for B in C.__mro__):
                          return True
                  return NotImplemented

          MyIterable.register(Foo)

     ABC ‘MyIterable’ 定義了作為抽象方法的一個標準疊代方法 *note
     __iter__(): 1bc7.。這裡給定的實作仍可在子類別中被呼叫。
     ‘get_iterator()’ 方法也是 ‘MyIterable’ 抽象基底類別的一部分，但它不
     必被非抽象衍生類別覆寫。

     這裡定義的 *note __subclasshook__(): 2401. 類別方法說明任何在其
     *note __dict__: c04. (或在其透過 *note __mro__: 205d. 列表訪問的基
     底類別) 中具有 *note __iter__(): 1bc7. 方法的類別也都會被視為
     ‘MyIterable’。

     最後，即使 ‘Foo’ 沒有定義 *note __iter__(): 1bc7. 方法（它使用了以
     *note __len__(): 1e38. 和 *note __getitem__(): 266. 所定義的舊式可
     疊代物件協定），最末一行使其成為 ‘MyIterable’ 的一個虛擬子類別。請
     注意這不會使 ‘get_iterator’ 成為 ‘Foo’ 的一個可用方法，所以它是需要
     被另外提供的。

‘abc’ 模組也提供了這些裝飾器：

 -- 函式: @abc.abstractmethod

     用於表示抽象方法的裝飾器。

     類別的元類別是 *note ABCMeta: ebc. 或是從該類別衍生才能使用此裝飾器
     。一個具有衍生自 ‘ABCMeta’ 之元類別的類別不可以被實例化，除非它全部
     的抽象方法和特性均已被覆寫。抽象方法可透過任何一般的 'super' 呼叫機
     制來呼叫。‘abstractmethod()’ 可被用於為特性和描述器宣告的抽象方法。

     僅在使用 *note update_abstractmethods(): 4237. 函式時，才能夠動態地
     為一個類別新增抽象方法，或者嘗試在方法或類別被建立後修改其抽象狀態
     。‘abstractmethod()’ 只會影響使用常規繼承所衍生出的子類別；透過 ABC
     的 *note register(): 102a. 方法註冊的「虛擬子類別」不會受到影響。

     當 ‘abstractmethod()’ 與其他方法描述器 (method descriptor) 配合應用
     時，它應被當最內層的裝飾器，如以下用法範例所示：

          class C(ABC):
              @abstractmethod
              def my_abstract_method(self, arg1):
                  ...
              @classmethod
              @abstractmethod
              def my_abstract_classmethod(cls, arg2):
                  ...
              @staticmethod
              @abstractmethod
              def my_abstract_staticmethod(arg3):
                  ...

              @property
              @abstractmethod
              def my_abstract_property(self):
                  ...
              @my_abstract_property.setter
              @abstractmethod
              def my_abstract_property(self, val):
                  ...

              @abstractmethod
              def _get_x(self):
                  ...
              @abstractmethod
              def _set_x(self, val):
                  ...
              x = property(_get_x, _set_x)

     為了能正確地與 ABC 機制實作相互操作，描述器必須使用
     ‘__isabstractmethod__’ 將自身標識為抽象的。一般來說，如果被用於組成
     描述器的任一方法是抽象的，則此屬性應當為 ‘True’。 例如，Python 的內
     建 *note property: 180. 所做的就等價於：

          class Descriptor:
              ...
              @property
              def __isabstractmethod__(self):
                  return any(getattr(f, '__isabstractmethod__', False) for
                             f in (self._fget, self._fset, self._fdel))

          備註: 不同於 Java 抽象方法，這些抽象方法可能具有一個實作。這個
          實作可在覆寫它的類別上透過 *note super(): 483. 機制來呼叫。這
          在使用協作多重繼承 (cooperative multiple-inheritance) 的框架中
          ，可以被用作 super 呼叫的一個端點 (end-point)。

‘abc’ 模組還支援下列舊式裝飾器：

 -- 函式: @abc.abstractclassmethod

     在 3.2 版被加入.

     在 3.3 版之後被棄用: 現在可以讓 *note classmethod: 14a. 配合 *note
     abstractmethod(): 1027. 使用，使得此裝飾器變得冗餘。

     內建 *note classmethod(): 14a. 的子類別，表示為一個抽象類別方法。在
     其他方面它都類似於 *note abstractmethod(): 1027.。

     這個特例已被棄用，因為現在當 *note classmethod(): 14a. 裝飾器應用於
     抽象方法時已會被正確地標識為是抽象的：

          class C(ABC):
              @classmethod
              @abstractmethod
              def my_abstract_classmethod(cls, arg):
                  ...

 -- 函式: @abc.abstractstaticmethod

     在 3.2 版被加入.

     在 3.3 版之後被棄用: 現在可以讓 *note staticmethod: 358. 配合 *note
     abstractmethod(): 1027. 使用，使得此裝飾器變得冗餘。

     內建 *note staticmethod(): 358. 的子類別，表示為一個抽象靜態方法。
     在其他方面它都類似於 *note abstractmethod(): 1027.。

     這個特例已被棄用，因為現在當 *note staticmethod(): 358. 裝飾器應用
     於抽象方法時已會被正確地標識為是抽象的：

          class C(ABC):
              @staticmethod
              @abstractmethod
              def my_abstract_staticmethod(arg):
                  ...

 -- 函式: @abc.abstractproperty

     在 3.3 版之後被棄用: 現在可以讓 *note property: 180.、*note
     property.getter(): 1550.、*note property.setter(): 1551. 和 *note
     property.deleter(): 1552. 配合 *note abstractmethod(): 1027. 使用，
     使得此裝飾器變得冗餘。

     內建 *note property(): 180. 的子類別，表示為一個抽象特性。

     這個特例已被棄用，因為現在當 *note property(): 180. 裝飾器應用於抽
     象方法時已會被正確地標識為是抽象的：

          class C(ABC):
              @property
              @abstractmethod
              def my_abstract_property(self):
                  ...

     上面的例子定義了一個唯讀特性；你也可以透過適當地將一個或多個底層方
     法標記為抽象的來定義可讀寫的抽象特性：

          class C(ABC):
              @property
              def x(self):
                  ...

              @x.setter
              @abstractmethod
              def x(self, val):
                  ...

     如果只有某些元件是抽象的，則只需更新那些元件即可在子類別中建立具體
     的特性：

          class D(C):
              @C.x.setter
              def x(self, val):
                  ...

‘abc’ 模組也提供了這些函式：

 -- 函式: abc.get_cache_token ()

     回傳當前 ABC 快取令牌 (cache token)。

     此令牌是一個（支援相等性測試的）不透明物件 (opaque object)，用於為
     虛擬子類別標識抽象基底類別快取的當前版本。此令牌會在任何 ABC 上每次
     呼叫 *note ABCMeta.register(): 102a. 時發生更改。

     在 3.4 版被加入.

 -- 函式: abc.update_abstractmethods (cls)

     重新計算一個抽象類別之抽象狀態的函式。如果一個類別的抽象方法在建立
     後被實作或被修改，則應當呼叫此函式。通常此函式應在一個類別裝飾器內
     部被呼叫。

     回傳 'cls'，使其能夠用作為類別的裝飾器。

     如果 'cls' 不是 *note ABCMeta: ebc. 的實例則不做任何操作。

          備註: 此函式會假定 'cls' 的超類別 (superclass) 已經被更新。它
          不會更新任何子類別。

     在 3.10 版被加入.

註解
....

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/abc.py

   (2) https://peps.python.org/pep-3119/

   (3) https://peps.python.org/pep-3141/

   (4) C++ 程式設計師需要注意到 Python 中虛擬基底類別的概念和 C++ 中的並
不相同。


File: python.info,  Node: atexit --- 退出處理函式,  Next: traceback --- 列印或取得堆疊回溯 stack traceback,  Prev: abc --- 抽象基底類別,  Up: Python Runtime 服務

5.29.10 ‘atexit’ -- 退出處理函式
--------------------------------

__________________________________________________________________

*note atexit: 9. 模組定義了註冊和註銷清理函式 (cleanup function) 的函式
，這樣的註冊函式會在直譯器正常終止時自動執行。*note atexit: 9. 按照這些
函式註冊之'反序'來運行這些函式；如果你有註冊 ‘A’、‘B’ 和 ‘C’，則在直譯器
終止時它們將按 ‘C’、‘B’、‘A’ 的順序運行。

'注意：'當程式被一個不是來自 Python 的訊號終止、偵測到有 Python 嚴重內部
錯誤時或者 *note os._exit(): 2174. 被呼叫時，透過此模組註冊的函式就不會
被呼叫。

'注意：'在清理函式中註冊或註銷函式的作用並未定義。

在 3.7 版的變更: 當與 C-API 子直譯器 (subinterpreter) 一起使用時，已註冊
函式對於它們所註冊的直譯器來說是區域的 (local)。

 -- 函式: atexit.register (func, *args, **kwargs)

     將 'func' 註冊為要在終止時執行的函式。任何要傳遞給 'func' 的可選引
     數都必須作為引數傳遞給 *note register(): 821.。可以多次註冊相同的函
     式和引數。

     在程式正常終止時（例如呼叫 *note sys.exit(): 12dd. 或主要模組執行完
     成），所有已註冊函式都會依照後進先出的順序呼叫。這邊做的假設是較低
     階的模組通常會在較高階模組之前被引入，因此較低階模組必須在比較後面
     才被清理。

     如果在執行退出處理函式期間引發例外，則會列印回溯 (traceback)（除非
     引發 *note SystemExit: ce7.）並儲存例外資訊。在所有退出處理函式都有
     嘗試運作過後，將重新引發最後一個引發的例外。

     該函式回傳 'func'，這使得可以將其作為裝飾器使用。

          警告: 啟動新執行緒或從已註冊函式呼叫 *note os.fork(): 17b. 可
          能會導致 Python 主要 runtime 執行緒釋放執行緒狀態，而內部
          *note threading: d6. 例程或新行程嘗試使用該狀態所形成的競態條
          件 (race condition)。這可能會導致崩潰 (crash) 而不是完整關閉中
          止。

     在 3.12 版的變更: 嘗試在已註冊函式中啟動新執行緒或 *note os.fork():
     17b. 新行程現在會導致 *note RuntimeError: 179.。

 -- 函式: atexit.unregister (func)

     從在直譯器中止時會執行之函式串列中刪除 'func'。如果 'func' 先前未被
     註冊，則 *note unregister(): 423a. 不會執行任何操作。如果 'func' 已
     被註冊多次，則該函式在 *note atexit: 9. 呼叫堆疊 (call stack) 中的
     所有存在都會被刪除。會在註銷期間於內部使用相等性比較 (‘==’)，因此函
     式參照不需要具有匹配的識別性。

也參考
......

*note readline: a8. 模組

     *note atexit: 9. 用於讀取和寫入 *note readline: a8. 歷史檔案的一個
     不錯的範例。

* Menu:

* atexit 範例::


File: python.info,  Node: atexit 範例,  Up: atexit --- 退出處理函式

5.29.10.1 ‘atexit’ 範例
.......................

以下的簡單範例示範了模組如何在被引入時以檔案來初始化計數器，並在程式終止
時自動儲存計數器的更新值，而不需要仰賴應用程式在終止時明確呼叫該模組。

     try:
         with open('counterfile') as infile:
             _count = int(infile.read())
     except FileNotFoundError:
         _count = 0

     def incrcounter(n):
         global _count
         _count = _count + n

     def savecounter():
         with open('counterfile', 'w') as outfile:
             outfile.write('%d' % _count)

     import atexit

     atexit.register(savecounter)

位置引數和關鍵字引數也可以被傳遞給 *note register(): 821.，以便在呼叫時
也傳遞給已註冊函式：

     def goodbye(name, adjective):
         print('Goodbye %s, it was %s to meet you.' % (name, adjective))

     import atexit

     atexit.register(goodbye, 'Donny', 'nice')
     # or:
     atexit.register(goodbye, adjective='nice', name='Donny')

作為*note 裝飾器: 6d5.使用：

     import atexit

     @atexit.register
     def goodbye():
         print('You are now leaving the Python sector.')

這只適用於可以不帶引數呼叫的函式。


File: python.info,  Node: traceback --- 列印或取得堆疊回溯 stack traceback,  Next: __future__ --- Future 陳述式定義,  Prev: atexit --- 退出處理函式,  Up: Python Runtime 服務

5.29.11 ‘traceback’ -- 列印或取得堆疊回溯 (stack traceback)
-----------------------------------------------------------

'原始碼：'Lib/traceback.py(1)

__________________________________________________________________

This module provides a standard interface to extract, format and print
stack traces of Python programs.  It exactly mimics the behavior of the
Python interpreter when it prints a stack trace.  This is useful when
you want to print stack traces under program control, such as in a
"wrapper" around the interpreter.

The module uses *note traceback objects: a97. -- these are objects of
type *note types.TracebackType: a95, which are assigned to the *note
__traceback__: 125b. field of *note BaseException: 55f. instances.

也參考
......

*note faulthandler: 4e. 模組

     Used to dump Python tracebacks explicitly, on a fault, after a
     timeout, or on a user signal.

*note pdb: 94. 模組

     Interactive source code debugger for Python programs.

此模組定義了以下函式：

 -- 函式: traceback.print_tb (tb, limit=None, file=None)

     Print up to 'limit' stack trace entries from *note traceback
     object: a97. 'tb' (starting from the caller's frame) if 'limit' is
     positive.  Otherwise, print the last ‘abs(limit)’ entries.  If
     'limit' is omitted or ‘None’, all entries are printed.  If 'file'
     is omitted or ‘None’, the output goes to *note sys.stderr: 8dd.;
     otherwise it should be an open *note file: 115b. or *note file-like
     object: 246a. to receive the output.

          備註: The meaning of the 'limit' parameter is different than
          the meaning of *note sys.tracebacklimit: 14cd.  A negative
          'limit' value corresponds to a positive value of
          ‘sys.tracebacklimit’, whereas the behaviour of a positive
          'limit' value cannot be achieved with ‘sys.tracebacklimit’.

     在 3.5 版的變更: 新增負數 'limit' 的支援。

 -- 函式: traceback.print_exception (exc, /[, value, tb], limit=None,
          file=None, chain=True)

     Print exception information and stack trace entries from *note
     traceback object: a97. 'tb' to 'file'.  This differs from *note
     print_tb(): e29. in the following ways:

        * if 'tb' is not ‘None’, it prints a header ‘Traceback (most
          recent call last):’

        * it prints the exception type and 'value' after the stack trace

        * if 'type(value)' is *note SyntaxError: 173. and 'value' has
          the appropriate format, it prints the line where the syntax
          error occurred with a caret indicating the approximate
          position of the error.

     Since Python 3.10, instead of passing 'value' and 'tb', an
     exception object can be passed as the first argument.  If 'value'
     and 'tb' are provided, the first argument is ignored in order to
     provide backwards compatibility.

     The optional 'limit' argument has the same meaning as for *note
     print_tb(): e29.  If 'chain' is true (the default), then chained
     exceptions (the *note __cause__: 125d. or *note __context__: 125c.
     attributes of the exception) will be printed as well, like the
     interpreter itself does when printing an unhandled exception.

     在 3.5 版的變更: The 'etype' argument is ignored and inferred from
     the type of 'value'.

     在 3.10 版的變更: The 'etype' parameter has been renamed to 'exc'
     and is now positional-only.

 -- 函式: traceback.print_exc (limit=None, file=None, chain=True)

     This is a shorthand for ‘print_exception(sys.exception(), limit,
     file, chain)’.

 -- 函式: traceback.print_last (limit=None, file=None, chain=True)

     This is a shorthand for ‘print_exception(sys.last_exc, limit, file,
     chain)’.  In general it will work only after an exception has
     reached an interactive prompt (see *note sys.last_exc: 465.).

 -- 函式: traceback.print_stack (f=None, limit=None, file=None)

     Print up to 'limit' stack trace entries (starting from the
     invocation point) if 'limit' is positive.  Otherwise, print the
     last ‘abs(limit)’ entries.  If 'limit' is omitted or ‘None’, all
     entries are printed.  The optional 'f' argument can be used to
     specify an alternate *note stack frame: 27e. to start.  The
     optional 'file' argument has the same meaning as for *note
     print_tb(): e29.

     在 3.5 版的變更: 新增負數 'limit' 的支援。

 -- 函式: traceback.extract_tb (tb, limit=None)

     Return a *note StackSummary: e27. object representing a list of
     "pre-processed" stack trace entries extracted from the *note
     traceback object: a97. 'tb'.  It is useful for alternate formatting
     of stack traces.  The optional 'limit' argument has the same
     meaning as for *note print_tb(): e29.  A "pre-processed" stack
     trace entry is a *note FrameSummary: e28. object containing
     attributes *note filename: 4241, *note lineno: 4242, *note name:
     4243, and *note line: 4244. representing the information that is
     usually printed for a stack trace.

 -- 函式: traceback.extract_stack (f=None, limit=None)

     Extract the raw traceback from the current *note stack frame: 27e.
     The return value has the same format as for *note extract_tb():
     4240.  The optional 'f' and 'limit' arguments have the same meaning
     as for *note print_stack(): e2a.

 -- 函式: traceback.format_list (extracted_list)

     Given a list of tuples or *note FrameSummary: e28. objects as
     returned by *note extract_tb(): 4240. or *note extract_stack():
     4245, return a list of strings ready for printing.  Each string in
     the resulting list corresponds to the item with the same index in
     the argument list.  Each string ends in a newline; the strings may
     contain internal newlines as well, for those items whose source
     text line is not ‘None’.

 -- 函式: traceback.format_exception_only (exc, /[, value], *,
          show_group=False)

     Format the exception part of a traceback using an exception value
     such as given by *note sys.last_value: 467.  The return value is a
     list of strings, each ending in a newline.  The list contains the
     exception's message, which is normally a single string; however,
     for *note SyntaxError: 173. exceptions, it contains several lines
     that (when printed) display detailed information about where the
     syntax error occurred.  Following the message, the list contains
     the exception's *note notes: 2161.

     Since Python 3.10, instead of passing 'value', an exception object
     can be passed as the first argument.  If 'value' is provided, the
     first argument is ignored in order to provide backwards
     compatibility.

     When 'show_group' is ‘True’, and the exception is an instance of
     *note BaseExceptionGroup: 244, the nested exceptions are included
     as well, recursively, with indentation relative to their nesting
     depth.

     在 3.10 版的變更: The 'etype' parameter has been renamed to 'exc'
     and is now positional-only.

     在 3.11 版的變更: The returned list now includes any *note notes:
     2161. attached to the exception.

     在 3.13 版的變更: 'show_group' parameter was added.

 -- 函式: traceback.format_exception (exc, /[, value, tb], limit=None,
          chain=True)

     Format a stack trace and the exception information.  The arguments
     have the same meaning as the corresponding arguments to *note
     print_exception(): 7f3.  The return value is a list of strings,
     each ending in a newline and some containing internal newlines.
     When these lines are concatenated and printed, exactly the same
     text is printed as does *note print_exception(): 7f3.

     在 3.5 版的變更: The 'etype' argument is ignored and inferred from
     the type of 'value'.

     在 3.10 版的變更: This function's behavior and signature were
     modified to match *note print_exception(): 7f3.

 -- 函式: traceback.format_exc (limit=None, chain=True)

     This is like ‘print_exc(limit)’ but returns a string instead of
     printing to a file.

 -- 函式: traceback.format_tb (tb, limit=None)

     ‘format_list(extract_tb(tb, limit))’ 的簡寫。

 -- 函式: traceback.format_stack (f=None, limit=None)

     ‘format_list(extract_stack(f, limit))’ 的簡寫。

 -- 函式: traceback.clear_frames (tb)

     Clears the local variables of all the stack frames in a *note
     traceback: a97. 'tb' by calling the *note clear(): 27f. method of
     each *note frame object: 27e.

     在 3.4 版被加入.

 -- 函式: traceback.walk_stack (f)

     Walk a stack following *note f.f_back: 730. from the given frame,
     yielding the frame and line number for each frame.  If 'f' is
     ‘None’, the current stack is used.  This helper is used with *note
     StackSummary.extract(): 4249.

     在 3.5 版被加入.

 -- 函式: traceback.walk_tb (tb)

     Walk a traceback following *note tb_next: a96. yielding the frame
     and line number for each frame.  This helper is used with *note
     StackSummary.extract(): 4249.

     在 3.5 版被加入.

The module also defines the following classes:

* Menu:

* TracebackException 物件::
* StackSummary 物件::
* FrameSummary 物件::
* Traceback Examples::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/traceback.py


File: python.info,  Node: TracebackException 物件,  Next: StackSummary 物件,  Up: traceback --- 列印或取得堆疊回溯 stack traceback

5.29.11.1 ‘TracebackException’ 物件
...................................

在 3.5 版被加入.

‘TracebackException’ objects are created from actual exceptions to
capture data for later printing in a lightweight fashion.

 -- 類別: traceback.TracebackException (exc_type, exc_value,
          exc_traceback, *, limit=None, lookup_lines=True,
          capture_locals=False, compact=False, max_group_width=15,
          max_group_depth=10)

     Capture an exception for later rendering.  'limit', 'lookup_lines'
     and 'capture_locals' are as for the *note StackSummary: e27. class.

     If 'compact' is true, only data that is required by
     ‘TracebackException’'s *note format(): 5c3. method is saved in the
     class attributes.  In particular, the *note __context__: 424b.
     field is calculated only if *note __cause__: 424c. is ‘None’ and
     *note __suppress_context__: 424d. is false.

     Note that when locals are captured, they are also shown in the
     traceback.

     'max_group_width' and 'max_group_depth' control the formatting of
     exception groups (see *note BaseExceptionGroup: 244.).  The depth
     refers to the nesting level of the group, and the width refers to
     the size of a single exception group's exceptions array.  The
     formatted output is truncated when either limit is exceeded.

     在 3.10 版的變更: 新增 'compact' 參數。

     在 3.11 版的變更: 新增 'max_group_width' 和 'max_group_depth' 參數
     。

      -- 屬性: __cause__

          A ‘TracebackException’ of the original *note __cause__: 125d.

      -- 屬性: __context__

          A ‘TracebackException’ of the original *note __context__:
          125c.

      -- 屬性: exceptions

          If ‘self’ represents an *note ExceptionGroup: 19c, this field
          holds a list of ‘TracebackException’ instances representing
          the nested exceptions.  Otherwise it is ‘None’.

          在 3.11 版被加入.

      -- 屬性: __suppress_context__

          The *note __suppress_context__: 1f8b. value from the original
          exception.

      -- 屬性: __notes__

          The *note __notes__: 2161. value from the original exception,
          or ‘None’ if the exception does not have any notes.  If it is
          not ‘None’ is it formatted in the traceback after the
          exception string.

          在 3.11 版被加入.

      -- 屬性: stack

          A *note StackSummary: e27. representing the traceback.

      -- 屬性: exc_type

          The class of the original traceback.

          在 3.13 版之後被棄用.

      -- 屬性: exc_type_str

          String display of the class of the original exception.

          在 3.13 版被加入.

      -- 屬性: filename

          For syntax errors - the file name where the error occurred.

      -- 屬性: lineno

          For syntax errors - the line number where the error occurred.

      -- 屬性: end_lineno

          For syntax errors - the end line number where the error
          occurred.  Can be ‘None’ if not present.

          在 3.10 版被加入.

      -- 屬性: text

          For syntax errors - the text where the error occurred.

      -- 屬性: offset

          For syntax errors - the offset into the text where the error
          occurred.

      -- 屬性: end_offset

          For syntax errors - the end offset into the text where the
          error occurred.  Can be ‘None’ if not present.

          在 3.10 版被加入.

      -- 屬性: msg

          For syntax errors - the compiler error message.

      -- 方法: classmethod from_exception (exc, *, limit=None,
               lookup_lines=True, capture_locals=False)

          Capture an exception for later rendering.  'limit',
          'lookup_lines' and 'capture_locals' are as for the *note
          StackSummary: e27. class.

          Note that when locals are captured, they are also shown in the
          traceback.

      -- 方法: print (*, file=None, chain=True)

          Print to 'file' (default ‘sys.stderr’) the exception
          information returned by *note format(): 5c3.

          在 3.11 版被加入.

      -- 方法: format (*, chain=True)

          Format the exception.

          If 'chain' is not ‘True’, *note __cause__: 424c. and *note
          __context__: 424b. will not be formatted.

          The return value is a generator of strings, each ending in a
          newline and some containing internal newlines.  *note
          print_exception(): 7f3. is a wrapper around this method which
          just prints the lines to a file.

      -- 方法: format_exception_only (*, show_group=False)

          Format the exception part of the traceback.

          The return value is a generator of strings, each ending in a
          newline.

          When 'show_group' is ‘False’, the generator emits the
          exception's message followed by its notes (if it has any).
          The exception message is normally a single string; however,
          for *note SyntaxError: 173. exceptions, it consists of several
          lines that (when printed) display detailed information about
          where the syntax error occurred.

          When 'show_group' is ‘True’, and the exception is an instance
          of *note BaseExceptionGroup: 244, the nested exceptions are
          included as well, recursively, with indentation relative to
          their nesting depth.

          在 3.11 版的變更: The exception's *note notes: 2161. are now
          included in the output.

          在 3.13 版的變更: Added the 'show_group' parameter.


File: python.info,  Node: StackSummary 物件,  Next: FrameSummary 物件,  Prev: TracebackException 物件,  Up: traceback --- 列印或取得堆疊回溯 stack traceback

5.29.11.2 ‘StackSummary’ 物件
.............................

在 3.5 版被加入.

‘StackSummary’ objects represent a call stack ready for formatting.

 -- 類別: traceback.StackSummary

      -- 方法: classmethod extract (frame_gen, *, limit=None,
               lookup_lines=True, capture_locals=False)

          Construct a ‘StackSummary’ object from a frame generator (such
          as is returned by *note walk_stack(): e25. or *note walk_tb():
          e26.).

          If 'limit' is supplied, only this many frames are taken from
          'frame_gen'.  If 'lookup_lines' is ‘False’, the returned *note
          FrameSummary: e28. objects will not have read their lines in
          yet, making the cost of creating the ‘StackSummary’ cheaper
          (which may be valuable if it may not actually get formatted).
          If 'capture_locals' is ‘True’ the local variables in each
          ‘FrameSummary’ are captured as object representations.

          在 3.12 版的變更: Exceptions raised from *note repr(): 7a1. on
          a local variable (when 'capture_locals' is ‘True’) are no
          longer propagated to the caller.

      -- 方法: classmethod from_list (a_list)

          Construct a ‘StackSummary’ object from a supplied list of
          *note FrameSummary: e28. objects or old-style list of tuples.
          Each tuple should be a 4-tuple with 'filename', 'lineno',
          'name', 'line' as the elements.

      -- 方法: format ()

          Returns a list of strings ready for printing.  Each string in
          the resulting list corresponds to a single *note frame: 27e.
          from the stack.  Each string ends in a newline; the strings
          may contain internal newlines as well, for those items with
          source text lines.

          For long sequences of the same frame and line, the first few
          repetitions are shown, followed by a summary line stating the
          exact number of further repetitions.

          在 3.6 版的變更: Long sequences of repeated frames are now
          abbreviated.

      -- 方法: format_frame_summary (frame_summary)

          Returns a string for printing one of the *note frames: 27e.
          involved in the stack.  This method is called for each *note
          FrameSummary: e28. object to be printed by *note
          StackSummary.format(): 425c.  If it returns ‘None’, the frame
          is omitted from the output.

          在 3.11 版被加入.


File: python.info,  Node: FrameSummary 物件,  Next: Traceback Examples,  Prev: StackSummary 物件,  Up: traceback --- 列印或取得堆疊回溯 stack traceback

5.29.11.3 ‘FrameSummary’ 物件
.............................

在 3.5 版被加入.

A ‘FrameSummary’ object represents a single *note frame: 27e. in a *note
traceback: a97.

 -- 類別: traceback.FrameSummary (filename, lineno, name,
          lookup_line=True, locals=None, line=None)

     Represents a single *note frame: 27e. in the *note traceback: a97.
     or stack that is being formatted or printed.  It may optionally
     have a stringified version of the frame's locals included in it.
     If 'lookup_line' is ‘False’, the source code is not looked up until
     the ‘FrameSummary’ has the *note line: 4244. attribute accessed
     (which also happens when casting it to a *note tuple: 322.).  *note
     line: 4244. may be directly provided, and will prevent line lookups
     happening at all.  'locals' is an optional local variable mapping,
     and if supplied the variable representations are stored in the
     summary for later display.

     ‘FrameSummary’ instances have the following attributes:

      -- 屬性: filename

          The filename of the source code for this frame.  Equivalent to
          accessing *note f.f_code.co_filename: 12fa. on a *note frame
          object: 27e. 'f'.

      -- 屬性: lineno

          The line number of the source code for this frame.

      -- 屬性: name

          Equivalent to accessing *note f.f_code.co_name: 1e0c. on a
          *note frame object: 27e. 'f'.

      -- 屬性: line

          A string representing the source code for this frame, with
          leading and trailing whitespace stripped.  If the source is
          not available, it is ‘None’.


File: python.info,  Node: Traceback Examples,  Prev: FrameSummary 物件,  Up: traceback --- 列印或取得堆疊回溯 stack traceback

5.29.11.4 Traceback Examples
............................

This simple example implements a basic read-eval-print loop, similar to
(but less useful than) the standard Python interactive interpreter loop.
For a more complete implementation of the interpreter loop, refer to the
*note code: 13. module.

     import sys, traceback

     def run_user_code(envdir):
         source = input(">>> ")
         try:
             exec(source, envdir)
         except Exception:
             print("Exception in user code:")
             print("-"*60)
             traceback.print_exc(file=sys.stdout)
             print("-"*60)

     envdir = {}
     while True:
         run_user_code(envdir)

The following example demonstrates the different ways to print and
format the exception and traceback:

     import sys, traceback

     def lumberjack():
         bright_side_of_life()

     def bright_side_of_life():
         return tuple()[0]

     try:
         lumberjack()
     except IndexError:
         exc = sys.exception()
         print("*** print_tb:")
         traceback.print_tb(exc.__traceback__, limit=1, file=sys.stdout)
         print("*** print_exception:")
         traceback.print_exception(exc, limit=2, file=sys.stdout)
         print("*** print_exc:")
         traceback.print_exc(limit=2, file=sys.stdout)
         print("*** format_exc, first and last line:")
         formatted_lines = traceback.format_exc().splitlines()
         print(formatted_lines[0])
         print(formatted_lines[-1])
         print("*** format_exception:")
         print(repr(traceback.format_exception(exc)))
         print("*** extract_tb:")
         print(repr(traceback.extract_tb(exc.__traceback__)))
         print("*** format_tb:")
         print(repr(traceback.format_tb(exc.__traceback__)))
         print("*** tb_lineno:", exc.__traceback__.tb_lineno)

The output for the example would look similar to this:

     *** print_tb:
       File "<doctest...>", line 10, in <module>
         lumberjack()
         ~~~~~~~~~~^^
     *** print_exception:
     Traceback (most recent call last):
       File "<doctest...>", line 10, in <module>
         lumberjack()
         ~~~~~~~~~~^^
       File "<doctest...>", line 4, in lumberjack
         bright_side_of_life()
         ~~~~~~~~~~~~~~~~~~~^^
     IndexError: tuple index out of range
     *** print_exc:
     Traceback (most recent call last):
       File "<doctest...>", line 10, in <module>
         lumberjack()
         ~~~~~~~~~~^^
       File "<doctest...>", line 4, in lumberjack
         bright_side_of_life()
         ~~~~~~~~~~~~~~~~~~~^^
     IndexError: tuple index out of range
     *** format_exc, first and last line:
     Traceback (most recent call last):
     IndexError: tuple index out of range
     *** format_exception:
     ['Traceback (most recent call last):\n',
      '  File "<doctest default[0]>", line 10, in <module>\n    lumberjack()\n    ~~~~~~~~~~^^\n',
      '  File "<doctest default[0]>", line 4, in lumberjack\n    bright_side_of_life()\n    ~~~~~~~~~~~~~~~~~~~^^\n',
      '  File "<doctest default[0]>", line 7, in bright_side_of_life\n    return tuple()[0]\n           ~~~~~~~^^^\n',
      'IndexError: tuple index out of range\n']
     *** extract_tb:
     [<FrameSummary file <doctest...>, line 10 in <module>>,
      <FrameSummary file <doctest...>, line 4 in lumberjack>,
      <FrameSummary file <doctest...>, line 7 in bright_side_of_life>]
     *** format_tb:
     ['  File "<doctest default[0]>", line 10, in <module>\n    lumberjack()\n    ~~~~~~~~~~^^\n',
      '  File "<doctest default[0]>", line 4, in lumberjack\n    bright_side_of_life()\n    ~~~~~~~~~~~~~~~~~~~^^\n',
      '  File "<doctest default[0]>", line 7, in bright_side_of_life\n    return tuple()[0]\n           ~~~~~~~^^^\n']
     *** tb_lineno: 10

The following example shows the different ways to print and format the
stack:

     >>> import traceback
     >>> def another_function():
     ...     lumberstack()
     ...
     >>> def lumberstack():
     ...     traceback.print_stack()
     ...     print(repr(traceback.extract_stack()))
     ...     print(repr(traceback.format_stack()))
     ...
     >>> another_function()
       File "<doctest>", line 10, in <module>
         another_function()
       File "<doctest>", line 3, in another_function
         lumberstack()
       File "<doctest>", line 6, in lumberstack
         traceback.print_stack()
     [('<doctest>', 10, '<module>', 'another_function()'),
      ('<doctest>', 3, 'another_function', 'lumberstack()'),
      ('<doctest>', 7, 'lumberstack', 'print(repr(traceback.extract_stack()))')]
     ['  File "<doctest>", line 10, in <module>\n    another_function()\n',
      '  File "<doctest>", line 3, in another_function\n    lumberstack()\n',
      '  File "<doctest>", line 8, in lumberstack\n    print(repr(traceback.format_stack()))\n']

This last example demonstrates the final few formatting functions:

     >>> import traceback
     >>> traceback.format_list([('spam.py', 3, '<module>', 'spam.eggs()'),
     ...                        ('eggs.py', 42, 'eggs', 'return "bacon"')])
     ['  File "spam.py", line 3, in <module>\n    spam.eggs()\n',
      '  File "eggs.py", line 42, in eggs\n    return "bacon"\n']
     >>> an_error = IndexError('tuple index out of range')
     >>> traceback.format_exception_only(type(an_error), an_error)
     ['IndexError: tuple index out of range\n']


File: python.info,  Node: __future__ --- Future 陳述式定義,  Next: gc --- 垃圾回收器介面 Garbage Collector interface,  Prev: traceback --- 列印或取得堆疊回溯 stack traceback,  Up: Python Runtime 服務

5.29.12 ‘__future__’ -- Future 陳述式定義
-----------------------------------------

'原始碼：'Lib/__future__.py(1)

__________________________________________________________________

‘from __future__ import feature’ 形式的引入被稱為 *note future 陳述式:
16f.。這些是 Python 編譯器的特殊情況，允許在該功能成為標準版本之前在包含
future 陳述式的模組中使用新的 Python 功能。

雖然這些 future 陳述式被 Python 編譯器賦予了額外的特殊意義，但它們仍然像
任何其他 import 陳述式一樣執行，且 *note __future__: 0. 由引入系統以和任
何其他 Python 模組相同的方式處理。這個設計有三個目的：

   * 為了避免混淆分析引入陳述式並預期要找到它們正在引入之模組的現有工具
     。

   * 記錄何時出現不相容的變更，以及何時開始強制執行這些變更。這是一種可
     執行文件的形式，可以透過引入 *note __future__: 0. 並檢查其內容以程
     式化的方式進行檢查。

   * 確保 *note future 陳述式: 16f.在 Python 2.1 之前的版本中運行至少會
     產生 runtime 例外（*note __future__: 0. 的引入將會失敗，因為 2.1 之
     前沒有該名稱的模組）。

* Menu:

* 模組內容: 模組內容<9>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/__future__.py


File: python.info,  Node: 模組內容<9>,  Up: __future__ --- Future 陳述式定義

5.29.12.1 模組內容
..................

不會從 *note __future__: 0. 中刪除任何功能描述。自從在 Python 2.1 中引入
以來，以下功能已透過這種機制引入到該語言中：

功能                   可選的版本        強制性的版本       影響
                                                            
--------------------------------------------------------------------------------------------------------------
                                                            
nested_scopes          2.1.0b1           2.2                PEP 227(1): '靜態巢狀作用域 (Statically Nested
                                                            Scopes)'
                                                            
                                                            
generators             2.2.0a1           2.3                PEP 255(2): '簡單產生器 (Simple Generators)'
                                                            
                                                            
division               2.2.0a2           3.0                PEP 238(3): '更改除法運算子 (Changing the
                                                            Division Operator)'
                                                            
                                                            
absolute_import        2.5.0a1           3.0                PEP 328(4): '引入：多列與絕對/相對 (Imports:
                                                            Multi-Line and Absolute/Relative)'
                                                            
                                                            
with_statement         2.5.0a1           2.6                PEP 343(5): '"with" 陳述式 (The "with"
                                                            Statement)'
                                                            
                                                            
print_function         2.6.0a2           3.0                PEP 3105(6): '使 print 成為一個函式 (Make print
                                                            a function)'
                                                            
                                                            
unicode_literals       2.6.0a2           3.0                PEP 3112(7): 'Python 3000 中的位元組字面值
                                                            (Bytes literals in Python 3000)'
                                                            
                                                            
generator_stop         3.5.0b1           3.7                PEP 479(8): '產生器內部的 StopIteration 處理
                                                            (StopIteration handling inside generators)'
                                                            
                                                            
annotations            3.7.0b1           TBD (9)            PEP 563(10): '推遲對註釋的求值 (Postponed
                                                            evaluation of annotations)'
                                                            

 -- 類別: __future__._Feature

     ‘__future__.py’ 中的每個陳述式的形式如下：

          FeatureName = _Feature(OptionalRelease, MandatoryRelease,
                                 CompilerFlag)

     通常，'OptionalRelease' 會小於 'MandatoryRelease'，且兩者都是與
     *note sys.version_info: 645. 形式相同的 5 元組 (5-tuple)：

          (PY_MAJOR_VERSION, # the 2 in 2.1.0a3; an int
           PY_MINOR_VERSION, # the 1; an int
           PY_MICRO_VERSION, # the 0; an int
           PY_RELEASE_LEVEL, # "alpha", "beta", "candidate" or "final"; string
           PY_RELEASE_SERIAL # the 3; an int
          )

 -- 方法: _Feature.getOptionalRelease ()

     'OptionalRelease' 記錄該功能首次發布時的 Python 版本。

 -- 方法: _Feature.getMandatoryRelease ()

     如果 'MandatoryRelease' 尚未發布，'MandatoryRelease' 會預測該功能將
     成為該語言一部分的版本。

     否則 'MandatoryRelease' 會記錄該功能是何時成為語言的一部分；在該版
     本或之後的版本中，模組不再需要 future 聲明來使用相關功能，但可以繼
     續使用此種引入方式。

     'MandatoryRelease' 也可能是 ‘None’，這意味著計劃中的功能被丟棄或者
     仍未決定。

 -- 屬性: _Feature.compiler_flag

     'CompilerFlag' 是（位元欄位 (bitfield)）旗標，應在第四個引數中傳遞
     給內建函式 *note compile(): 178. 以在動態編譯的程式碼中啟用該功能。
     此旗標存儲在 *note _Feature: 203d. 實例上的 *note
     _Feature.compiler_flag: 203e. 屬性中。

也參考
......

*note Future statements: 16f.

     編譯器如何處理 future 引入。

PEP 236(11) - 回到 __future__

     __future__ 機制的原始提案。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0227/

   (2) https://peps.python.org/pep-0255/

   (3) https://peps.python.org/pep-0238/

   (4) https://peps.python.org/pep-0328/

   (5) https://peps.python.org/pep-0343/

   (6) https://peps.python.org/pep-3105/

   (7) https://peps.python.org/pep-3112/

   (8) https://peps.python.org/pep-0479/

   (9) 之前原本計劃在 Python 3.10 中強制使用 ‘from __future__ import
annotations’，但 Python 指導委員會 (Python Steering Council) 兩次決議推
遲這一變動（Python 3.10 的公告
(https://mail.python.org/archives/list/python-dev@python.org/message/CLVXXPQ2T2LQ5MP2Y53VVQFCXYWQJHKZ/)；
Python 3.11 的公告
(https://mail.python.org/archives/list/python-dev@python.org/message/VIZEBX5EYMSYIJNDBF6DMUMZOCWHARSO/)）
。目前還尚未做出決定。另請參閱 PEP 563
(https://peps.python.org/pep-0563/) 和 PEP 649
(https://peps.python.org/pep-0649/)。

   (10) https://peps.python.org/pep-0563/

   (11) https://peps.python.org/pep-0236/


File: python.info,  Node: gc --- 垃圾回收器介面 Garbage Collector interface,  Next: inspect --- 檢視活動物件,  Prev: __future__ --- Future 陳述式定義,  Up: Python Runtime 服務

5.29.13 ‘gc’ -- 垃圾回收器介面 (Garbage Collector interface)
------------------------------------------------------------

__________________________________________________________________

此 module（模組）提供可選的垃圾回收器介面，提供的功能包括：關閉回收器、
調整回收頻率、設定除錯選項。它同時提供對回收器有找到但是無法釋放的不可達
物件 (unreachable object) 的存取。由於 Python 使用了帶有參照計數的回收器
，如果你確定你的程式不會產生參照迴圈 (reference cycle)，你可以關閉回收器
。可以透過呼叫 ‘gc.disable()’ 關閉自動垃圾回收。若要為一個存在記憶體流失
的程式 (leaking program) 除錯，請呼叫 ‘gc.set_debug(gc.DEBUG_LEAK)’；需
要注意的是，它包含 ‘gc.DEBUG_SAVEALL’，使得被回收的物件會被存放在
gc.garbage 中以待檢查。

*note gc: 56. module 提供下列函式：

 -- 函式: gc.enable ()

     啟用自動垃圾回收。

 -- 函式: gc.disable ()

     停用自動垃圾回收。

 -- 函式: gc.isenabled ()

     如果啟用了自動回收則回傳 ‘True’。

 -- 函式: gc.collect (generation=2)

     Perform a collection.  The optional argument 'generation' may be an
     integer specifying which generation to collect (from 0 to 2).  A
     *note ValueError: 1e7. is raised if the generation number is
     invalid.  The sum of collected objects and uncollectable objects is
     returned.

     Calling ‘gc.collect(0)’ will perform a GC collection on the young
     generation.

     Calling ‘gc.collect(1)’ will perform a GC collection on the young
     generation and an increment of the old generation.

     Calling ‘gc.collect(2)’ or ‘gc.collect()’ performs a full
     collection

     每當執行完整回收或最高代 (2) 回收時，為多個內建型別所維護的空閒列表
     會被清空。為了特定型別的實現，特別是 *note float: 2c8.，在某些空閒
     列表中並非所有項目都會被釋放。

     The effect of calling ‘gc.collect()’ while the interpreter is
     already performing a collection is undefined.

     在 3.13 版的變更: ‘generation=1’ performs an increment of
     collection.

 -- 函式: gc.set_debug (flags)

     設定垃圾回收器的除錯旗標。除錯資訊會被寫入 ‘sys.stderr’。請見下方的
     除錯旗標列表，可以使用位元操作 (bit operation) 進行設定以控制除錯程
     式。

 -- 函式: gc.get_debug ()

     回傳當前設置的除錯旗標。

 -- 函式: gc.get_objects (generation=None)

     Returns a list of all objects tracked by the collector, excluding
     the list returned.  If 'generation' is not ‘None’, return only the
     objects as follows:

        * 0: All objects in the young generation

        * 1: No objects, as there is no generation 1 (as of Python 3.13)

        * 2: All objects in the old generation

     在 3.8 版的變更: 新增 'generation' 參數。

     在 3.13 版的變更: Generation 1 is removed

     引發一個附帶引數 ‘generation’ 的*note 稽核事件 (auditing event):
     17bd. ‘gc.get_objects’。

 -- 函式: gc.get_stats ()

     回傳一個包含三個字典物件的 list，每個字典分別包含對應代中自從直譯器
     開始執行後的垃圾回收統計資料。字典的鍵的數目在將來可能會改變，但目
     前每個字典包含以下項目：

        * ‘collections’ 是該代被回收的次數；

        * ‘collected’ 是該代中被回收的物件總數；

        * ‘uncollectable’ 是在這一代中被發現無法回收的物件總數（因此被移
          到 *note garbage: 1159. list 中）。

     在 3.4 版被加入.

 -- 函式: gc.set_threshold (threshold0[, threshold1[, threshold2]])

     設定垃圾回收閾值（回收頻率）。 將 'threshold0' 設為零會停止回收。

     The GC classifies objects into two generations depending on whether
     they have survived a collection.  New objects are placed in the
     young generation.  If an object survives a collection it is moved
     into the old generation.

     In order to decide when to run, the collector keeps track of the
     number of object allocations and deallocations since the last
     collection.  When the number of allocations minus the number of
     deallocations exceeds 'threshold0', collection starts.  For each
     collection, all the objects in the young generation and some
     fraction of the old generation is collected.

     The fraction of the old generation that is collected is 'inversely'
     proportional to 'threshold1'.  The larger 'threshold1' is, the
     slower objects in the old generation are collected.  For the
     default value of 10, 1% of the old generation is scanned during
     each collection.

     'threshold2' is ignored.

     See Garbage collector design(1) for more information.

     在 3.13 版的變更: 'threshold2' is ignored

 -- 函式: gc.get_count ()

     將當前回收計數以 ‘(count0, count1, count2)’ 形式的 tuple 回傳。

 -- 函式: gc.get_threshold ()

     將當前回收閾值以 ‘(threshold0, threshold1, threshold2)’ 形式的
     tuple 回傳。

 -- 函式: gc.get_referrers (*objs)

     回傳包含直接參照 objs 中任一個物件的物件 list。這個函式只定位支援垃
     圾回收的容器；參照了其它物件但不支援垃圾回收的擴充套件型別無法被找
     到。

     需要注意的是，已經解除參照的物件，但仍存在於參照迴圈中未被回收時，
     該物件仍然會被作為參照者出現在回傳的 list 中。若只要獲取當前正在參
     照的物件，需要在呼叫 *note get_referrers(): 7a8. 之前呼叫 *note
     collect(): 16b.。

          警告: 在使用 *note get_referrers(): 7a8. 回傳的物件時必須要小
          心，因為其中的一些物件可能仍在建構中而處於暫時無效的狀態。不要
          把 *note get_referrers(): 7a8. 用於除錯以外的其它目的。

     引發一個附帶引數 ‘objs’ 的*note 稽核事件: 17bd. ‘gc.get_referrers’。

 -- 函式: gc.get_referents (*objs)

     回傳包含被任意一個引數直接參照之物件的 list。回傳的被參照物件是有被
     引數的 C 語言級別 *note tp_traverse: 721. 方法（若存在）訪問到的物
     件，可能不是所有的實際直接可達物件。只有支援垃圾回收的物件支援
     *note tp_traverse: 721. 方法，並且此方法只會訪問涉及參照迴圈的物件
     。因此，可以有以下例子：一個整數對於一個引數是直接可達的，這個整數
     物件有可能出現或不出現在結果的 list 當中。

     引發一個附帶引數 ‘objs’ 的*note 稽核事件: 17bd. ‘gc.get_referents’。

 -- 函式: gc.is_tracked (obj)

     當物件正在被垃圾回收器追蹤時回傳 ‘True’，否則回傳 ‘False’。一般來說
     ，原子型別 (atomic type) 的實例不會被追蹤，而非原子型別（如容器、使
     用者自己定義的物件）會被追蹤。然而，有一些特定型別最佳化會被用來減
     少垃圾回收器在簡單實例（如只含有原子性的鍵和值的字典）上的足跡：

          >>> gc.is_tracked(0)
          False
          >>> gc.is_tracked("a")
          False
          >>> gc.is_tracked([])
          True
          >>> gc.is_tracked({})
          False
          >>> gc.is_tracked({"a": 1})
          False
          >>> gc.is_tracked({"a": []})
          True

     在 3.1 版被加入.

 -- 函式: gc.is_finalized (obj)

     如果給定物件已被垃圾回收器終結則回傳 ‘True’，否則回傳 ‘False’。：

          >>> x = None
          >>> class Lazarus:
          ...     def __del__(self):
          ...         global x
          ...         x = self
          ...
          >>> lazarus = Lazarus()
          >>> gc.is_finalized(lazarus)
          False
          >>> del lazarus
          >>> gc.is_finalized(x)
          True

     在 3.9 版被加入.

 -- 函式: gc.freeze ()

     凍結 (freeze) 垃圾回收器所追蹤的所有物件；將它們移至永久代並忽略所
     有未來的收集動作。

     如果一個行程將在沒有 ‘exec()’ 的情況下進行 ‘fork()’，避免子行程中不
     必要的寫入時複製將最大化記憶體共享並減少整體記憶體使用。這需要避免
     在父行程的記憶體頁面中建立已釋放的「漏洞」，並確保子行程中的 GC 收
     集不會觸及源自父行程的長壽命物件的 ‘gc_refs’ 計數器。要實現這兩個目
     標，請在父行程的早期呼叫 ‘gc.disable()’，在 ‘fork()’ 之前呼叫
     ‘gc.freeze()’，並儘早在子行程中呼叫 ‘gc.enable()’。

     在 3.7 版被加入.

 -- 函式: gc.unfreeze ()

     解凍 (unfreeze) 永久代中的物件，並將它們放回到最年老代中。

     在 3.7 版被加入.

 -- 函式: gc.get_freeze_count ()

     回傳永久代中的物件數量。

     在 3.7 版被加入.

以下變數僅供唯讀存取（你可以修改其值但不應該重新繫結 (rebind) 它們）：

 -- 資料: gc.garbage

     一個回收器發現不可達而又無法被釋放的物件（不可回收物件）list。從
     Python 3.4 開始，該 list 在大多數時候都應該是空的，除非使用了有非
     ‘NULL’ ‘tp_del’ 槽位的 C 擴充套件型別的實例。

     如果設定了 *note DEBUG_SAVEALL: 426d.，則所有不可達物件將被加進該
     list 而不會被釋放。

     在 3.2 版的變更: 當 *note interpreter shutdown: 133. 即直譯器關閉時
     ，若此 list 非空，會產生 *note ResourceWarning: 229.，在預設情況下
     此警告不會被提醒。如果設定了 *note DEBUG_UNCOLLECTABLE: 115a.，所有
     無法被回收的物件會被印出。

     在 3.4 版的變更: 根據 PEP 442(2)，帶有 *note __del__(): 1e36.
     method 的物件最終不會在 *note gc.garbage: 1159. 內。

 -- 資料: gc.callbacks

     會被垃圾回收器在回收開始前和完成後呼叫的一系列回呼函式 (callback) 。
     這些回呼函式在被呼叫時附帶兩個引數：'phase' 和 'info'。

     'phase' 可為以下兩者之一：

          "start"：垃圾回收即將開始。

          "stop"：垃圾回收已結束。

     'info' 是一個字典，提供回呼函式更多資訊。已有定義的鍵有：

          "generation"（代）：正在被回收的最年老的一代。

          "collected"（已回收的）：當 'phase' 為 "stop" 時，被成功回收的
          物件的數目。

          "uncollectable"（不可回收的）：當 'phase' 為 "stop" 時，不能被
          回收並被放入 *note garbage: 1159. 的物件的數目。

     應用程式可以把他們自己的回呼函式加入此 list。主要的使用場景有：

          收集垃圾回收的統計資料，如：不同代的回收頻率、回收任務所花費的
          時間。

          讓應用程式可以識別和清理他們自己在 *note garbage: 1159. 中的不
          可回收型別物件。

     在 3.3 版被加入.

以下常數是為了和 *note set_debug(): 426b. 一起使用所提供：

 -- 資料: gc.DEBUG_STATS

     在回收完成後印出統計資訊。當調校回收頻率設定時，這些資訊會很有用。

 -- 資料: gc.DEBUG_COLLECTABLE

     當發現可回收物件時印出資訊。

 -- 資料: gc.DEBUG_UNCOLLECTABLE

     印出找到的不可回收物件的資訊（指不能被回收器回收的不可達物件）。這
     些物件會被新增到 ‘garbage’ list 中。

     在 3.2 版的變更: 當 *note interpreter shutdown: 133.（直譯器關閉）
     時，若 *note garbage: 1159. list 不是空的，那這些內容也會被印出。

 -- 資料: gc.DEBUG_SAVEALL

     設定後，所有回收器找到的不可達物件會被加進 'garbage' 而不是直接被釋
     放。這在為一個記憶體流失的程式除錯時會很有用。

 -- 資料: gc.DEBUG_LEAK

     要印出記憶體流失程式之相關資訊時，回收器所需的除錯旗標。（等同於
     ‘DEBUG_COLLECTABLE | DEBUG_UNCOLLECTABLE | DEBUG_SAVEALL’）。

   ---------- Footnotes ----------

   (1) https://devguide.python.org/garbage_collector

   (2) https://peps.python.org/pep-0442/


File: python.info,  Node: inspect --- 檢視活動物件,  Next: site --- Site-specific configuration hook,  Prev: gc --- 垃圾回收器介面 Garbage Collector interface,  Up: Python Runtime 服務

5.29.14 ‘inspect’ -- 檢視活動物件
---------------------------------

'原始碼：'Lib/inspect.py(1)

__________________________________________________________________

The *note inspect: 72. module provides several useful functions to help
get information about live objects such as modules, classes, methods,
functions, tracebacks, frame objects, and code objects.  For example, it
can help you examine the contents of a class, retrieve the source code
of a method, extract and format the argument list for a function, or get
all the information you need to display a detailed traceback.

There are four main kinds of services provided by this module: type
checking, getting source code, inspecting classes and functions, and
examining the interpreter stack.

* Menu:

* Types and members::
* 取得原始碼::
* Introspecting callables with the Signature object::
* 類別與函式::
* 直譯器堆疊::
* Fetching attributes statically::
* Current State of Generators, Coroutines, and Asynchronous Generators: Current State of Generators Coroutines and Asynchronous Generators.
* Code Objects Bit Flags::
* Buffer flags::
* 命令列介面: 命令列介面<6>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/inspect.py


File: python.info,  Node: Types and members,  Next: 取得原始碼,  Up: inspect --- 檢視活動物件

5.29.14.1 Types and members
...........................

The *note getmembers(): 1758. function retrieves the members of an
object such as a class or module.  The functions whose names begin with
"is" are mainly provided as convenient choices for the second argument
to *note getmembers(): 1758.  They also help you determine when you can
expect to find the following special attributes (see *note
Import-related module attributes: 1ed1. for module attributes):

Type                  屬性                    描述
                                              
------------------------------------------------------------------------------
                                              
class                 __doc__                 documentation string
                                              
                                              
                      __name__                name with which this class
                                              was defined
                                              
                                              
                      __qualname__            qualified name
                                              
                                              
                      __module__              name of module in which this
                                              class was defined
                                              
                                              
                      __type_params__         A tuple containing the
                                              *note type parameters: 294.
                                              of a generic class
                                              
                                              
method                __doc__                 documentation string
                                              
                                              
                      __name__                name with which this method
                                              was defined
                                              
                                              
                      __qualname__            qualified name
                                              
                                              
                      __func__                function object containing
                                              implementation of method
                                              
                                              
                      __self__                instance to which this method
                                              is bound, or ‘None’
                                              
                                              
                      __module__              name of module in which this
                                              method was defined
                                              
                                              
函式                  __doc__                 documentation string
                                              
                                              
                      __name__                name with which this function
                                              was defined
                                              
                                              
                      __qualname__            qualified name
                                              
                                              
                      __code__                code object containing
                                              compiled function
                                              *note bytecode: 16d.
                                              
                                              
                      __defaults__            tuple of any default values
                                              for positional or keyword
                                              parameters
                                              
                                              
                      __kwdefaults__          mapping of any default values
                                              for keyword-only parameters
                                              
                                              
                      __globals__             global namespace in which
                                              this function was defined
                                              
                                              
                      __builtins__            builtins namespace
                                              
                                              
                      __annotations__         mapping of parameters names
                                              to annotations; ‘"return"’
                                              key is reserved for return
                                              annotations.
                                              
                                              
                      __type_params__         A tuple containing the
                                              *note type parameters: 294.
                                              of a generic function
                                              
                                              
                      __module__              name of module in which this
                                              function was defined
                                              
                                              
traceback             tb_frame                frame object at this level
                                              
                                              
                      tb_lasti                index of last attempted
                                              instruction in bytecode
                                              
                                              
                      tb_lineno               current line number in Python
                                              source code
                                              
                                              
                      tb_next                 next inner traceback object
                                              (called by this level)
                                              
                                              
frame                 f_back                  next outer frame object (this
                                              frame's caller)
                                              
                                              
                      f_builtins              builtins namespace seen by
                                              this frame
                                              
                                              
                      f_code                  code object being executed in
                                              this frame
                                              
                                              
                      f_globals               global namespace seen by this
                                              frame
                                              
                                              
                      f_lasti                 index of last attempted
                                              instruction in bytecode
                                              
                                              
                      f_lineno                current line number in Python
                                              source code
                                              
                                              
                      f_locals                local namespace seen by this
                                              frame
                                              
                                              
                      f_trace                 tracing function for this
                                              frame, or ‘None’
                                              
                                              
code（程式碼）        co_argcount             number of arguments (not
                                              including keyword only
                                              arguments, * or ** args)
                                              
                                              
                      co_code                 string of raw compiled
                                              bytecode
                                              
                                              
                      co_cellvars             tuple of names of cell
                                              variables (referenced by
                                              containing scopes)
                                              
                                              
                      co_consts               tuple of constants used in
                                              the bytecode
                                              
                                              
                      co_filename             name of file in which this
                                              code object was created
                                              
                                              
                      co_firstlineno          number of first line in
                                              Python source code
                                              
                                              
                      co_flags                bitmap of ‘CO_*’ flags, read
                                              more *note here: 1e1b.
                                              
                                              
                      co_lnotab               encoded mapping of line
                                              numbers to bytecode indices
                                              
                                              
                      co_freevars             tuple of names of free
                                              variables (referenced via a
                                              function's closure)
                                              
                                              
                      co_posonlyargcount      number of positional only
                                              arguments
                                              
                                              
                      co_kwonlyargcount       number of keyword only
                                              arguments (not including **
                                              arg)
                                              
                                              
                      co_name                 name with which this code
                                              object was defined
                                              
                                              
                      co_qualname             fully qualified name with
                                              which this code object was
                                              defined
                                              
                                              
                      co_names                tuple of names other than
                                              arguments and function locals
                                              
                                              
                      co_nlocals              number of local variables
                                              
                                              
                      co_stacksize            virtual machine stack space
                                              required
                                              
                                              
                      co_varnames             tuple of names of arguments
                                              and local variables
                                              
                                              
generator             __name__                name
                                              
                                              
                      __qualname__            qualified name
                                              
                                              
                      gi_frame                frame
                                              
                                              
                      gi_running              is the generator running?
                                              
                                              
                      gi_code                 code（程式碼）
                                              
                                              
                      gi_yieldfrom            object being iterated by
                                              ‘yield from’, or ‘None’
                                              
                                              
async generator       __name__                name
                                              
                                              
                      __qualname__            qualified name
                                              
                                              
                      ag_await                object being awaited on, or
                                              ‘None’
                                              
                                              
                      ag_frame                frame
                                              
                                              
                      ag_running              is the generator running?
                                              
                                              
                      ag_code                 code（程式碼）
                                              
                                              
coroutine             __name__                name
                                              
                                              
                      __qualname__            qualified name
                                              
                                              
                      cr_await                object being awaited on, or
                                              ‘None’
                                              
                                              
                      cr_frame                frame
                                              
                                              
                      cr_running              is the coroutine running?
                                              
                                              
                      cr_code                 code（程式碼）
                                              
                                              
                      cr_origin               where coroutine was created,
                                              or ‘None’.  See
                                              *note sys.set_coroutine_origin_tracking_depth(): b32.
                                              
                                              
builtin               __doc__                 documentation string
                                              
                                              
                      __name__                original name of this
                                              function or method
                                              
                                              
                      __qualname__            qualified name
                                              
                                              
                      __self__                instance to which a method is
                                              bound, or ‘None’
                                              

在 3.5 版的變更: 將 ‘__qualname__’ 和 ‘gi_yieldfrom’ 屬性加到產生器。

The ‘__name__’ attribute of generators is now set from the function
name, instead of the code name, and it can now be modified.

在 3.7 版的變更: 新增協程的 ‘cr_origin’ 屬性。

在 3.10 版的變更: 新增函式的 ‘__builtins__’ 屬性。

 -- 函式: inspect.getmembers (object[, predicate])

     Return all the members of an object in a list of ‘(name, value)’
     pairs sorted by name.  If the optional 'predicate' argument—which
     will be called with the ‘value’ object of each member—is supplied,
     only members for which the predicate returns a true value are
     included.

          備註: *note getmembers(): 1758. will only return class
          attributes defined in the metaclass when the argument is a
          class and those attributes have been listed in the metaclass'
          custom *note __dir__(): 1e3c.

 -- 函式: inspect.getmembers_static (object[, predicate])

     Return all the members of an object in a list of ‘(name, value)’
     pairs sorted by name without triggering dynamic lookup via the
     descriptor protocol, __getattr__ or __getattribute__.  Optionally,
     only return members that satisfy a given predicate.

          備註: *note getmembers_static(): 5ef. may not be able to
          retrieve all members that getmembers can fetch (like
          dynamically created attributes) and may find members that
          getmembers can't (like descriptors that raise AttributeError).
          It can also return descriptor objects instead of instance
          members in some cases.

     在 3.11 版被加入.

 -- 函式: inspect.getmodulename (path)

     Return the name of the module named by the file 'path', without
     including the names of enclosing packages.  The file extension is
     checked against all of the entries in *note
     importlib.machinery.all_suffixes(): 4274.  If it matches, the final
     path component is returned with the extension removed.  Otherwise,
     ‘None’ is returned.

     Note that this function 'only' returns a meaningful name for actual
     Python modules - paths that potentially refer to Python packages
     will still return ‘None’.

     在 3.3 版的變更: 此函式直接基於 *note importlib: 6b.。

 -- 函式: inspect.ismodule (object)

     如果物件是模組，則回傳 ‘True’。

 -- 函式: inspect.isclass (object)

     Return ‘True’ if the object is a class, whether built-in or created
     in Python code.

 -- 函式: inspect.ismethod (object)

     Return ‘True’ if the object is a bound method written in Python.

 -- 函式: inspect.isfunction (object)

     Return ‘True’ if the object is a Python function, which includes
     functions created by a *note lambda: 2616. expression.

 -- 函式: inspect.isgeneratorfunction (object)

     如果物件是 Python 產生器函式，則回傳 ‘True’。

     在 3.8 版的變更: Functions wrapped in *note functools.partial():
     356. now return ‘True’ if the wrapped function is a Python
     generator function.

     在 3.13 版的變更: Functions wrapped in *note
     functools.partialmethod(): a1e. now return ‘True’ if the wrapped
     function is a Python generator function.

 -- 函式: inspect.isgenerator (object)

     如果物件是產生器，則回傳 ‘True’。

 -- 函式: inspect.iscoroutinefunction (object)

     Return ‘True’ if the object is a *note coroutine function: d1d. (a
     function defined with an *note async def: 575. syntax), a *note
     functools.partial(): 356. wrapping a *note coroutine function: d1d,
     or a sync function marked with *note markcoroutinefunction(): 437.

     在 3.5 版被加入.

     在 3.8 版的變更: Functions wrapped in *note functools.partial():
     356. now return ‘True’ if the wrapped function is a *note coroutine
     function: d1d.

     在 3.12 版的變更: Sync functions marked with *note
     markcoroutinefunction(): 437. now return ‘True’.

     在 3.13 版的變更: Functions wrapped in *note
     functools.partialmethod(): a1e. now return ‘True’ if the wrapped
     function is a *note coroutine function: d1d.

 -- 函式: inspect.markcoroutinefunction (func)

     Decorator to mark a callable as a *note coroutine function: d1d. if
     it would not otherwise be detected by *note iscoroutinefunction():
     439.

     This may be of use for sync functions that return a *note
     coroutine: 438, if the function is passed to an API that requires
     *note iscoroutinefunction(): 439.

     When possible, using an *note async def: 575. function is
     preferred.  Also acceptable is calling the function and testing the
     return with *note iscoroutine(): dbc.

     在 3.12 版被加入.

 -- 函式: inspect.iscoroutine (object)

     Return ‘True’ if the object is a *note coroutine: 438. created by
     an *note async def: 575. function.

     在 3.5 版被加入.

 -- 函式: inspect.isawaitable (object)

     Return ‘True’ if the object can be used in *note await: 19f.
     expression.

     Can also be used to distinguish generator-based coroutines from
     regular generators:

          import types

          def gen():
              yield
          @types.coroutine
          def gen_coro():
              yield

          assert not isawaitable(gen())
          assert isawaitable(gen_coro())

     在 3.5 版被加入.

 -- 函式: inspect.isasyncgenfunction (object)

     Return ‘True’ if the object is an *note asynchronous generator:
     1f14. function, for example:

          >>> async def agen():
          ...     yield 1
          ...
          >>> inspect.isasyncgenfunction(agen)
          True

     在 3.6 版被加入.

     在 3.8 版的變更: Functions wrapped in *note functools.partial():
     356. now return ‘True’ if the wrapped function is an *note
     asynchronous generator: 1f14. function.

     在 3.13 版的變更: Functions wrapped in *note
     functools.partialmethod(): a1e. now return ‘True’ if the wrapped
     function is a *note coroutine function: d1d.

 -- 函式: inspect.isasyncgen (object)

     Return ‘True’ if the object is an *note asynchronous generator
     iterator: 4191. created by an *note asynchronous generator: 1f14.
     function.

     在 3.6 版被加入.

 -- 函式: inspect.istraceback (object)

     Return ‘True’ if the object is a traceback.

 -- 函式: inspect.isframe (object)

     Return ‘True’ if the object is a frame.

 -- 函式: inspect.iscode (object)

     如果物件是程式碼，則回傳 ‘True’。

 -- 函式: inspect.isbuiltin (object)

     Return ‘True’ if the object is a built-in function or a bound
     built-in method.

 -- 函式: inspect.ismethodwrapper (object)

     Return ‘True’ if the type of object is a *note MethodWrapperType:
     5f1.

     These are instances of *note MethodWrapperType: 5f1, such as *note
     __str__(): 5c4, *note __eq__(): a9d. and *note __repr__(): 5c2.

     在 3.11 版被加入.

 -- 函式: inspect.isroutine (object)

     如果物件是使用者定義或內建的函式或方法，則回傳 ‘True’。

 -- 函式: inspect.isabstract (object)

     如果物件是抽象基底類別，則回傳 ‘True’。

 -- 函式: inspect.ismethoddescriptor (object)

     Return ‘True’ if the object is a method descriptor, but not if
     *note ismethod(): 4277, *note isclass(): 4276, *note isfunction():
     4278. or *note isbuiltin(): 427e. are true.

     This, for example, is true of ‘int.__add__’.  An object passing
     this test has a *note __get__(): 16c3. method, but not a *note
     __set__(): 1e3f. method or a *note __delete__(): 14fc. method.
     Beyond that, the set of attributes varies.  A *note __name__: 1416.
     attribute is usually sensible, and ‘__doc__’ often is.

     Methods implemented via descriptors that also pass one of the other
     tests return ‘False’ from the *note ismethoddescriptor(): 14dd.
     test, simply because the other tests promise more - you can, e.g.,
     count on having the *note __func__: 128f. attribute (etc) when an
     object passes *note ismethod(): 4277.

     在 3.13 版的變更: This function no longer incorrectly reports
     objects with *note __get__(): 16c3. and *note __delete__(): 14fc,
     but not *note __set__(): 1e3f, as being method descriptors (such
     objects are data descriptors, not method descriptors).

 -- 函式: inspect.isdatadescriptor (object)

     如果物件是資料描述器，則回傳 ‘True’。

     Data descriptors have a *note __set__: 1e3f. or a *note __delete__:
     14fc. method.  Examples are properties (defined in Python),
     getsets, and members.  The latter two are defined in C and there
     are more specific tests available for those types, which is robust
     across Python implementations.  Typically, data descriptors will
     also have *note __name__: 1416. and ‘__doc__’ attributes
     (properties, getsets, and members have both of these attributes),
     but this is not guaranteed.

 -- 函式: inspect.isgetsetdescriptor (object)

     Return ‘True’ if the object is a getset descriptor.

     'CPython 實作細節：' getsets are attributes defined in extension
     modules via *note PyGetSetDef: b5f. structures.  For Python
     implementations without such types, this method will always return
     ‘False’.

 -- 函式: inspect.ismemberdescriptor (object)

     如果物件是成員描述器，則回傳 ‘True’。

     'CPython 實作細節：' Member descriptors are attributes defined in
     extension modules via *note PyMemberDef: 4f5. structures.  For
     Python implementations without such types, this method will always
     return ‘False’.


File: python.info,  Node: 取得原始碼,  Next: Introspecting callables with the Signature object,  Prev: Types and members,  Up: inspect --- 檢視活動物件

5.29.14.2 取得原始碼
....................

 -- 函式: inspect.getdoc (object)

     Get the documentation string for an object, cleaned up with *note
     cleandoc(): 15ad.  If the documentation string for an object is not
     provided and the object is a class, a method, a property or a
     descriptor, retrieve the documentation string from the inheritance
     hierarchy.  Return ‘None’ if the documentation string is invalid or
     missing.

     在 3.5 版的變更: Documentation strings are now inherited if not
     overridden.

 -- 函式: inspect.getcomments (object)

     Return in a single string any lines of comments immediately
     preceding the object's source code (for a class, function, or
     method), or at the top of the Python source file (if the object is
     a module).  If the object's source code is unavailable, return
     ‘None’.  This could happen if the object has been defined in C or
     the interactive shell.

 -- 函式: inspect.getfile (object)

     Return the name of the (text or binary) file in which an object was
     defined.  This will fail with a *note TypeError: 4dd. if the object
     is a built-in module, class, or function.

 -- 函式: inspect.getmodule (object)

     Try to guess which module an object was defined in.  Return ‘None’
     if the module cannot be determined.

 -- 函式: inspect.getsourcefile (object)

     Return the name of the Python source file in which an object was
     defined or ‘None’ if no way can be identified to get the source.
     This will fail with a *note TypeError: 4dd. if the object is a
     built-in module, class, or function.

 -- 函式: inspect.getsourcelines (object)

     Return a list of source lines and starting line number for an
     object.  The argument may be a module, class, method, function,
     traceback, frame, or code object.  The source code is returned as a
     list of the lines corresponding to the object and the line number
     indicates where in the original source file the first line of code
     was found.  An *note OSError: 350. is raised if the source code
     cannot be retrieved.  A *note TypeError: 4dd. is raised if the
     object is a built-in module, class, or function.

     在 3.3 版的變更: *note OSError: 350. is raised instead of *note
     IOError: ff5, now an alias of the former.

 -- 函式: inspect.getsource (object)

     Return the text of the source code for an object.  The argument may
     be a module, class, method, function, traceback, frame, or code
     object.  The source code is returned as a single string.  An *note
     OSError: 350. is raised if the source code cannot be retrieved.  A
     *note TypeError: 4dd. is raised if the object is a built-in module,
     class, or function.

     在 3.3 版的變更: *note OSError: 350. is raised instead of *note
     IOError: ff5, now an alias of the former.

 -- 函式: inspect.cleandoc (doc)

     Clean up indentation from docstrings that are indented to line up
     with blocks of code.

     All leading whitespace is removed from the first line.  Any leading
     whitespace that can be uniformly removed from the second line
     onwards is removed.  Empty lines at the beginning and end are
     subsequently removed.  Also, all tabs are expanded to spaces.


File: python.info,  Node: Introspecting callables with the Signature object,  Next: 類別與函式,  Prev: 取得原始碼,  Up: inspect --- 檢視活動物件

5.29.14.3 Introspecting callables with the Signature object
...........................................................

在 3.3 版被加入.

The *note Signature: 1b3. object represents the call signature of a
callable object and its return annotation.  To retrieve a ‘Signature’
object, use the ‘signature()’ function.

 -- 函式: inspect.signature (callable, *, follow_wrapped=True,
          globals=None, locals=None, eval_str=False)

     Return a *note Signature: 1b3. object for the given 'callable':

          >>> from inspect import signature
          >>> def foo(a, *, b:int, **kwargs):
          ...     pass

          >>> sig = signature(foo)

          >>> str(sig)
          '(a, *, b: int, **kwargs)'

          >>> str(sig.parameters['b'])
          'b: int'

          >>> sig.parameters['b'].annotation
          <class 'int'>

     Accepts a wide range of Python callables, from plain functions and
     classes to *note functools.partial(): 356. objects.

     For objects defined in modules using stringized annotations (‘from
     __future__ import annotations’), *note signature(): 6dc. will
     attempt to automatically un-stringize the annotations using *note
     get_annotations(): 7b7.  The 'globals', 'locals', and 'eval_str'
     parameters are passed into *note get_annotations(): 7b7. when
     resolving the annotations; see the documentation for *note
     get_annotations(): 7b7. for instructions on how to use these
     parameters.

     Raises *note ValueError: 1e7. if no signature can be provided, and
     *note TypeError: 4dd. if that type of object is not supported.
     Also, if the annotations are stringized, and 'eval_str' is not
     false, the ‘eval()’ call(s) to un-stringize the annotations in
     *note get_annotations(): 7b7. could potentially raise any kind of
     exception.

     A slash(/) in the signature of a function denotes that the
     parameters prior to it are positional-only.  For more info, see
     *note the FAQ entry on positional-only parameters: 204e.

     在 3.5 版的變更: The 'follow_wrapped' parameter was added.  Pass
     ‘False’ to get a signature of 'callable' specifically
     (‘callable.__wrapped__’ will not be used to unwrap decorated
     callables.)

     在 3.10 版的變更: The 'globals', 'locals', and 'eval_str'
     parameters were added.

          備註: Some callables may not be introspectable in certain
          implementations of Python.  For example, in CPython, some
          built-in functions defined in C provide no metadata about
          their arguments.

     'CPython 實作細節：' If the passed object has a ‘__signature__’
     attribute, we may use it to create the signature.  The exact
     semantics are an implementation detail and are subject to
     unannounced changes.  Consult the source code for current
     semantics.

 -- 類別: inspect.Signature (parameters=None, *,
          return_annotation=Signature.empty)

     A ‘Signature’ object represents the call signature of a function
     and its return annotation.  For each parameter accepted by the
     function it stores a *note Parameter: 1b4. object in its *note
     parameters: 4288. collection.

     The optional 'parameters' argument is a sequence of *note
     Parameter: 1b4. objects, which is validated to check that there are
     no parameters with duplicate names, and that the parameters are in
     the right order, i.e.  positional-only first, then
     positional-or-keyword, and that parameters with defaults follow
     parameters without defaults.

     The optional 'return_annotation' argument can be an arbitrary
     Python object.  It represents the "return" annotation of the
     callable.

     ‘Signature’ objects are 'immutable'.  Use *note
     Signature.replace(): 4289. or *note copy.replace(): 136. to make a
     modified copy.

     在 3.5 版的變更: ‘Signature’ objects are now picklable and *note
     hashable: 5b5.

      -- 屬性: empty

          A special class-level marker to specify absence of a return
          annotation.

      -- 屬性: parameters

          An ordered mapping of parameters' names to the corresponding
          *note Parameter: 1b4. objects.  Parameters appear in strict
          definition order, including keyword-only parameters.

          在 3.7 版的變更: Python only explicitly guaranteed that it
          preserved the declaration order of keyword-only parameters as
          of version 3.7, although in practice this order had always
          been preserved in Python 3.

      -- 屬性: return_annotation

          The "return" annotation for the callable.  If the callable has
          no "return" annotation, this attribute is set to *note
          Signature.empty: 428a.

      -- 方法: bind (*args, **kwargs)

          Create a mapping from positional and keyword arguments to
          parameters.  Returns *note BoundArguments: 100a. if ‘*args’
          and ‘**kwargs’ match the signature, or raises a *note
          TypeError: 4dd.

      -- 方法: bind_partial (*args, **kwargs)

          Works the same way as *note Signature.bind(): 150d, but allows
          the omission of some required arguments (mimics *note
          functools.partial(): 356. behavior.)  Returns *note
          BoundArguments: 100a, or raises a *note TypeError: 4dd. if the
          passed arguments do not match the signature.

      -- 方法: replace (*[, parameters][, return_annotation])

          Create a new *note Signature: 1b3. instance based on the
          instance *note replace(): 4289. was invoked on.  It is
          possible to pass different 'parameters' and/or
          'return_annotation' to override the corresponding properties
          of the base signature.  To remove ‘return_annotation’ from the
          copied ‘Signature’, pass in *note Signature.empty: 428a.

               >>> def test(a, b):
               ...     pass
               ...
               >>> sig = signature(test)
               >>> new_sig = sig.replace(return_annotation="new return anno")
               >>> str(new_sig)
               "(a, b) -> 'new return anno'"

          *note Signature: 1b3. objects are also supported by the
          generic function *note copy.replace(): 136.

      -- 方法: format (*, max_width=None)

          Create a string representation of the *note Signature: 1b3.
          object.

          If 'max_width' is passed, the method will attempt to fit the
          signature into lines of at most 'max_width' characters.  If
          the signature is longer than 'max_width', all parameters will
          be on separate lines.

          在 3.13 版被加入.

      -- 方法: classmethod from_callable (obj, *, follow_wrapped=True,
               globals=None, locals=None, eval_str=False)

          Return a *note Signature: 1b3. (or its subclass) object for a
          given callable 'obj'.

          This method simplifies subclassing of *note Signature: 1b3.:

               class MySignature(Signature):
                   pass
               sig = MySignature.from_callable(sum)
               assert isinstance(sig, MySignature)

          Its behavior is otherwise identical to that of *note
          signature(): 6dc.

          在 3.5 版被加入.

          在 3.10 版的變更: The 'globals', 'locals', and 'eval_str'
          parameters were added.

 -- 類別: inspect.Parameter (name, kind, *, default=Parameter.empty,
          annotation=Parameter.empty)

     ‘Parameter’ objects are 'immutable'.  Instead of modifying a
     ‘Parameter’ object, you can use *note Parameter.replace(): 428e. or
     *note copy.replace(): 136. to create a modified copy.

     在 3.5 版的變更: Parameter objects are now picklable and *note
     hashable: 5b5.

      -- 屬性: empty

          A special class-level marker to specify absence of default
          values and annotations.

      -- 屬性: name

          The name of the parameter as a string.  The name must be a
          valid Python identifier.

          'CPython 實作細節：' CPython generates implicit parameter
          names of the form ‘.0’ on the code objects used to implement
          comprehensions and generator expressions.

          在 3.6 版的變更: These parameter names are now exposed by this
          module as names like ‘implicit0’.

      -- 屬性: default

          The default value for the parameter.  If the parameter has no
          default value, this attribute is set to *note Parameter.empty:
          428f.

      -- 屬性: annotation

          The annotation for the parameter.  If the parameter has no
          annotation, this attribute is set to *note Parameter.empty:
          428f.

      -- 屬性: kind

          Describes how argument values are bound to the parameter.  The
          possible values are accessible via *note Parameter: 1b4. (like
          ‘Parameter.KEYWORD_ONLY’), and support comparison and
          ordering, in the following order:

          名稱                         意義
                                       
          --------------------------------------------------------------------------------
                                       
          'POSITIONAL_ONLY'            Value must be supplied as a positional argument.
                                       Positional only parameters are those which
                                       appear before a ‘/’ entry (if present) in a
                                       Python function definition.
                                       
                                       
          'POSITIONAL_OR_KEYWORD'      Value may be supplied as either a keyword or
                                       positional argument (this is the standard
                                       binding behaviour for functions implemented in
                                       Python.)
                                       
                                       
          'VAR_POSITIONAL'             A tuple of positional arguments that aren't
                                       bound to any other parameter.  This corresponds
                                       to a ‘*args’ parameter in a Python function
                                       definition.
                                       
                                       
          'KEYWORD_ONLY'               Value must be supplied as a keyword argument.
                                       Keyword only parameters are those which appear
                                       after a ‘*’ or ‘*args’ entry in a Python
                                       function definition.
                                       
                                       
          'VAR_KEYWORD'                A dict of keyword arguments that aren't bound to
                                       any other parameter.  This corresponds to a
                                       ‘**kwargs’ parameter in a Python function
                                       definition.
                                       

          Example: print all keyword-only arguments without default
          values:

               >>> def foo(a, b, *, c, d=10):
               ...     pass

               >>> sig = signature(foo)
               >>> for param in sig.parameters.values():
               ...     if (param.kind == param.KEYWORD_ONLY and
               ...                        param.default is param.empty):
               ...         print('Parameter:', param)
               Parameter: c

      -- 屬性: kind.description

          Describes an enum value of *note Parameter.kind: 4293.

          在 3.8 版被加入.

          範例：列印所有引數的描述：

               >>> def foo(a, b, *, c, d=10):
               ...     pass

               >>> sig = signature(foo)
               >>> for param in sig.parameters.values():
               ...     print(param.kind.description)
               positional or keyword
               positional or keyword
               keyword-only
               keyword-only

      -- 方法: replace (*[, name][, kind][, default][, annotation])

          Create a new *note Parameter: 1b4. instance based on the
          instance replaced was invoked on.  To override a ‘Parameter’
          attribute, pass the corresponding argument.  To remove a
          default value or/and an annotation from a ‘Parameter’, pass
          *note Parameter.empty: 428f.

               >>> from inspect import Parameter
               >>> param = Parameter('foo', Parameter.KEYWORD_ONLY, default=42)
               >>> str(param)
               'foo=42'

               >>> str(param.replace()) # Will create a shallow copy of 'param'
               'foo=42'

               >>> str(param.replace(default=Parameter.empty, annotation='spam'))
               "foo: 'spam'"

          *note Parameter: 1b4. objects are also supported by the
          generic function *note copy.replace(): 136.

     在 3.4 版的變更: In Python 3.3 *note Parameter: 1b4. objects were
     allowed to have ‘name’ set to ‘None’ if their ‘kind’ was set to
     ‘POSITIONAL_ONLY’.  This is no longer permitted.

 -- 類別: inspect.BoundArguments

     Result of a *note Signature.bind(): 150d. or *note
     Signature.bind_partial(): 428c. call.  Holds the mapping of
     arguments to the function's parameters.

      -- 屬性: arguments

          A mutable mapping of parameters' names to arguments' values.
          Contains only explicitly bound arguments.  Changes in *note
          arguments: 8b1. will reflect in *note args: 4295. and *note
          kwargs: 4296.

          Should be used in conjunction with *note Signature.parameters:
          4288. for any argument processing purposes.

               備註: Arguments for which *note Signature.bind(): 150d.
               or *note Signature.bind_partial(): 428c. relied on a
               default value are skipped.  However, if needed, use *note
               BoundArguments.apply_defaults(): dbb. to add them.

          在 3.9 版的變更: *note arguments: 8b1. is now of type *note
          dict: 23b.  Formerly, it was of type *note
          collections.OrderedDict: 57f.

      -- 屬性: args

          A tuple of positional arguments values.  Dynamically computed
          from the *note arguments: 8b1. attribute.

      -- 屬性: kwargs

          A dict of keyword arguments values.  Dynamically computed from
          the *note arguments: 8b1. attribute.

      -- 屬性: signature

          A reference to the parent *note Signature: 1b3. object.

      -- 方法: apply_defaults ()

          為遺漏的引數設定預設值。

          For variable-positional arguments (‘*args’) the default is an
          empty tuple.

          For variable-keyword arguments (‘**kwargs’) the default is an
          empty dict.

               >>> def foo(a, b='ham', *args): pass
               >>> ba = inspect.signature(foo).bind('spam')
               >>> ba.apply_defaults()
               >>> ba.arguments
               {'a': 'spam', 'b': 'ham', 'args': ()}

          在 3.5 版被加入.

     The *note args: 4295. and *note kwargs: 4296. properties can be
     used to invoke functions:

          def test(a, *, b):
              ...

          sig = signature(test)
          ba = sig.bind(10, b=20)
          test(*ba.args, **ba.kwargs)

也參考
......

PEP 362(1) - Function Signature Object.

     The detailed specification, implementation details and examples.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0362/


File: python.info,  Node: 類別與函式,  Next: 直譯器堆疊,  Prev: Introspecting callables with the Signature object,  Up: inspect --- 檢視活動物件

5.29.14.4 類別與函式
....................

 -- 函式: inspect.getclasstree (classes, unique=False)

     Arrange the given list of classes into a hierarchy of nested lists.
     Where a nested list appears, it contains classes derived from the
     class whose entry immediately precedes the list.  Each entry is a
     2-tuple containing a class and a tuple of its base classes.  If the
     'unique' argument is true, exactly one entry appears in the
     returned structure for each class in the given list.  Otherwise,
     classes using multiple inheritance and their descendants will
     appear multiple times.

 -- 函式: inspect.getfullargspec (func)

     Get the names and default values of a Python function's parameters.
     A *note named tuple: 5f4. is returned:

     ‘FullArgSpec(args, varargs, varkw, defaults, kwonlyargs,
     kwonlydefaults, annotations)’

     'args' is a list of the positional parameter names.  'varargs' is
     the name of the ‘*’ parameter or ‘None’ if arbitrary positional
     arguments are not accepted.  'varkw' is the name of the ‘**’
     parameter or ‘None’ if arbitrary keyword arguments are not
     accepted.  'defaults' is an 'n'-tuple of default argument values
     corresponding to the last 'n' positional parameters, or ‘None’ if
     there are no such defaults defined.  'kwonlyargs' is a list of
     keyword-only parameter names in declaration order.
     'kwonlydefaults' is a dictionary mapping parameter names from
     'kwonlyargs' to the default values used if no argument is supplied.
     'annotations' is a dictionary mapping parameter names to
     annotations.  The special key ‘"return"’ is used to report the
     function return value annotation (if any).

     Note that *note signature(): 6dc. and *note Signature Object: 4286.
     provide the recommended API for callable introspection, and support
     additional behaviours (like positional-only arguments) that are
     sometimes encountered in extension module APIs.  This function is
     retained primarily for use in code that needs to maintain
     compatibility with the Python 2 ‘inspect’ module API.

     在 3.4 版的變更: This function is now based on *note signature():
     6dc, but still ignores ‘__wrapped__’ attributes and includes the
     already bound first parameter in the signature output for bound
     methods.

     在 3.6 版的變更: This method was previously documented as
     deprecated in favour of *note signature(): 6dc. in Python 3.5, but
     that decision has been reversed in order to restore a clearly
     supported standard interface for single-source Python 2/3 code
     migrating away from the legacy ‘getargspec()’ API.

     在 3.7 版的變更: Python only explicitly guaranteed that it
     preserved the declaration order of keyword-only parameters as of
     version 3.7, although in practice this order had always been
     preserved in Python 3.

 -- 函式: inspect.getargvalues (frame)

     Get information about arguments passed into a particular frame.  A
     *note named tuple: 5f4. ‘ArgInfo(args, varargs, keywords, locals)’
     is returned.  'args' is a list of the argument names.  'varargs'
     and 'keywords' are the names of the ‘*’ and ‘**’ arguments or
     ‘None’.  'locals' is the locals dictionary of the given frame.

          備註: This function was inadvertently marked as deprecated in
          Python 3.5.

 -- 函式: inspect.formatargvalues (args[, varargs, varkw, locals,
          formatarg, formatvarargs, formatvarkw, formatvalue])

     Format a pretty argument spec from the four values returned by
     *note getargvalues(): e60.  The format* arguments are the
     corresponding optional formatting functions that are called to turn
     names and values into strings.

          備註: This function was inadvertently marked as deprecated in
          Python 3.5.

 -- 函式: inspect.getmro (cls)

     Return a tuple of class cls's base classes, including cls, in
     method resolution order.  No class appears more than once in this
     tuple.  Note that the method resolution order depends on cls's
     type.  Unless a very peculiar user-defined metatype is in use, cls
     will be the first element of the tuple.

 -- 函式: inspect.getcallargs (func, /, *args, **kwds)

     Bind the 'args' and 'kwds' to the argument names of the Python
     function or method 'func', as if it was called with them.  For
     bound methods, bind also the first argument (typically named
     ‘self’) to the associated instance.  A dict is returned, mapping
     the argument names (including the names of the ‘*’ and ‘**’
     arguments, if any) to their values from 'args' and 'kwds'.  In case
     of invoking 'func' incorrectly, i.e.  whenever ‘func(*args,
     **kwds)’ would raise an exception because of incompatible
     signature, an exception of the same type and the same or similar
     message is raised.  For example:

          >>> from inspect import getcallargs
          >>> def f(a, b=1, *pos, **named):
          ...     pass
          ...
          >>> getcallargs(f, 1, 2, 3) == {'a': 1, 'named': {}, 'b': 2, 'pos': (3,)}
          True
          >>> getcallargs(f, a=2, x=4) == {'a': 2, 'named': {'x': 4}, 'b': 1, 'pos': ()}
          True
          >>> getcallargs(f)
          Traceback (most recent call last):
          ...
          TypeError: f() missing 1 required positional argument: 'a'

     在 3.2 版被加入.

     在 3.5 版之後被棄用: 請改用 *note Signature.bind(): 150d. 與 *note
     Signature.bind_partial(): 428c.。

 -- 函式: inspect.getclosurevars (func)

     Get the mapping of external name references in a Python function or
     method 'func' to their current values.  A *note named tuple: 5f4.
     ‘ClosureVars(nonlocals, globals, builtins, unbound)’ is returned.
     'nonlocals' maps referenced names to lexical closure variables,
     'globals' to the function's module globals and 'builtins' to the
     builtins visible from the function body.  'unbound' is the set of
     names referenced in the function that could not be resolved at all
     given the current module globals and builtins.

     如果 'func' 不是 Python 函式或方法，則引發 *note TypeError: 4dd.。

     在 3.3 版被加入.

 -- 函式: inspect.unwrap (func, *, stop=None)

     Get the object wrapped by 'func'.  It follows the chain of
     ‘__wrapped__’ attributes returning the last object in the chain.

     'stop' is an optional callback accepting an object in the wrapper
     chain as its sole argument that allows the unwrapping to be
     terminated early if the callback returns a true value.  If the
     callback never returns a true value, the last object in the chain
     is returned as usual.  For example, *note signature(): 6dc. uses
     this to stop unwrapping if any object in the chain has a
     ‘__signature__’ attribute defined.

     如果遇到循環，則引發 *note ValueError: 1e7.。

     在 3.4 版被加入.

 -- 函式: inspect.get_annotations (obj, *, globals=None, locals=None,
          eval_str=False)

     Compute the annotations dict for an object.

     ‘obj’ may be a callable, class, or module.  Passing in an object of
     any other type raises *note TypeError: 4dd.

     Returns a dict.  ‘get_annotations()’ returns a new dict every time
     it's called; calling it twice on the same object will return two
     different but equivalent dicts.

     This function handles several details for you:

        * If ‘eval_str’ is true, values of type ‘str’ will be
          un-stringized using *note eval(): 163.  This is intended for
          use with stringized annotations (‘from __future__ import
          annotations’).

        * If ‘obj’ doesn't have an annotations dict, returns an empty
          dict.  (Functions and methods always have an annotations dict;
          classes, modules, and other types of callables may not.)

        * Ignores inherited annotations on classes.  If a class doesn't
          have its own annotations dict, returns an empty dict.

        * All accesses to object members and dict values are done using
          ‘getattr()’ and ‘dict.get()’ for safety.

        * Always, always, always returns a freshly created dict.

     ‘eval_str’ controls whether or not values of type ‘str’ are
     replaced with the result of calling *note eval(): 163. on those
     values:

        * If eval_str is true, *note eval(): 163. is called on values of
          type ‘str’.  (Note that ‘get_annotations’ doesn't catch
          exceptions; if *note eval(): 163. raises an exception, it will
          unwind the stack past the ‘get_annotations’ call.)

        * If eval_str is false (the default), values of type ‘str’ are
          unchanged.

     ‘globals’ and ‘locals’ are passed in to *note eval(): 163.; see the
     documentation for *note eval(): 163. for more information.  If
     ‘globals’ or ‘locals’ is ‘None’, this function may replace that
     value with a context-specific default, contingent on ‘type(obj)’:

        * If ‘obj’ is a module, ‘globals’ defaults to ‘obj.__dict__’.

        * If ‘obj’ is a class, ‘globals’ defaults to
          ‘sys.modules[obj.__module__].__dict__’ and ‘locals’ defaults
          to the ‘obj’ class namespace.

        * If ‘obj’ is a callable, ‘globals’ defaults to *note
          obj.__globals__: 1266, although if ‘obj’ is a wrapped function
          (using *note functools.update_wrapper(): fc5.) it is first
          unwrapped.

     Calling ‘get_annotations’ is best practice for accessing the
     annotations dict of any object.  See *note 註釋 (annotation)
     最佳實踐: 77d. for more information on annotations best practices.

     在 3.10 版被加入.


File: python.info,  Node: 直譯器堆疊,  Next: Fetching attributes statically,  Prev: 類別與函式,  Up: inspect --- 檢視活動物件

5.29.14.5 直譯器堆疊
....................

Some of the following functions return *note FrameInfo: 5f2. objects.
For backwards compatibility these objects allow tuple-like operations on
all attributes except ‘positions’.  This behavior is considered
deprecated and may be removed in the future.

 -- 類別: inspect.FrameInfo

      -- 屬性: frame

          The *note frame object: 27e. that the record corresponds to.

      -- 屬性: filename

          The file name associated with the code being executed by the
          frame this record corresponds to.

      -- 屬性: lineno

          The line number of the current line associated with the code
          being executed by the frame this record corresponds to.

      -- 屬性: function

          The function name that is being executed by the frame this
          record corresponds to.

      -- 屬性: code_context

          A list of lines of context from the source code that's being
          executed by the frame this record corresponds to.

      -- 屬性: index

          The index of the current line being executed in the *note
          code_context: 42a2. list.

      -- 屬性: positions

          A *note dis.Positions: 42a5. object containing the start line
          number, end line number, start column offset, and end column
          offset associated with the instruction being executed by the
          frame this record corresponds to.

     在 3.5 版的變更: Return a *note named tuple: 5f4. instead of a
     *note tuple: 322.

     在 3.11 版的變更: ‘FrameInfo’ is now a class instance (that is
     backwards compatible with the previous *note named tuple: 5f4.).

 -- 類別: inspect.Traceback

      -- 屬性: filename

          The file name associated with the code being executed by the
          frame this traceback corresponds to.

      -- 屬性: lineno

          The line number of the current line associated with the code
          being executed by the frame this traceback corresponds to.

      -- 屬性: function

          The function name that is being executed by the frame this
          traceback corresponds to.

      -- 屬性: code_context

          A list of lines of context from the source code that's being
          executed by the frame this traceback corresponds to.

      -- 屬性: index

          The index of the current line being executed in the *note
          code_context: 42a9. list.

      -- 屬性: positions

          A *note dis.Positions: 42a5. object containing the start line
          number, end line number, start column offset, and end column
          offset associated with the instruction being executed by the
          frame this traceback corresponds to.

     在 3.11 版的變更: ‘Traceback’ is now a class instance (that is
     backwards compatible with the previous *note named tuple: 5f4.).

     備註: Keeping references to frame objects, as found in the first
     element of the frame records these functions return, can cause your
     program to create reference cycles.  Once a reference cycle has
     been created, the lifespan of all objects which can be accessed
     from the objects which form the cycle can become much longer even
     if Python's optional cycle detector is enabled.  If such cycles
     must be created, it is important to ensure they are explicitly
     broken to avoid the delayed destruction of objects and increased
     memory consumption which occurs.

     Though the cycle detector will catch these, destruction of the
     frames (and local variables) can be made deterministic by removing
     the cycle in a *note finally: 96e. clause.  This is also important
     if the cycle detector was disabled when Python was compiled or
     using *note gc.disable(): 4269.  For example:

          def handle_stackframe_without_leak():
              frame = inspect.currentframe()
              try:
                  # do something with the frame
              finally:
                  del frame

     If you want to keep the frame around (for example to print a
     traceback later), you can also break reference cycles by using the
     *note frame.clear(): 27f. method.

The optional 'context' argument supported by most of these functions
specifies the number of lines of context to return, which are centered
around the current line.

 -- 函式: inspect.getframeinfo (frame, context=1)

     Get information about a frame or traceback object.  A *note
     Traceback: 5f3. object is returned.

     在 3.11 版的變更: A *note Traceback: 5f3. object is returned
     instead of a named tuple.

 -- 函式: inspect.getouterframes (frame, context=1)

     Get a list of *note FrameInfo: 5f2. objects for a frame and all
     outer frames.  These frames represent the calls that lead to the
     creation of 'frame'.  The first entry in the returned list
     represents 'frame'; the last entry represents the outermost call on
     'frame"s stack.

     在 3.5 版的變更: A list of *note named tuples: 5f4.
     ‘FrameInfo(frame, filename, lineno, function, code_context, index)’
     is returned.

     在 3.11 版的變更: 回傳一個 *note FrameInfo: 5f2. 物件串列。

 -- 函式: inspect.getinnerframes (traceback, context=1)

     Get a list of *note FrameInfo: 5f2. objects for a traceback's frame
     and all inner frames.  These frames represent calls made as a
     consequence of 'frame'.  The first entry in the list represents
     'traceback'; the last entry represents where the exception was
     raised.

     在 3.5 版的變更: A list of *note named tuples: 5f4.
     ‘FrameInfo(frame, filename, lineno, function, code_context, index)’
     is returned.

     在 3.11 版的變更: 回傳一個 *note FrameInfo: 5f2. 物件串列。

 -- 函式: inspect.currentframe ()

     Return the frame object for the caller's stack frame.

     'CPython 實作細節：' This function relies on Python stack frame
     support in the interpreter, which isn't guaranteed to exist in all
     implementations of Python.  If running in an implementation without
     Python stack frame support this function returns ‘None’.

 -- 函式: inspect.stack (context=1)

     Return a list of *note FrameInfo: 5f2. objects for the caller's
     stack.  The first entry in the returned list represents the caller;
     the last entry represents the outermost call on the stack.

     在 3.5 版的變更: A list of *note named tuples: 5f4.
     ‘FrameInfo(frame, filename, lineno, function, code_context, index)’
     is returned.

     在 3.11 版的變更: 回傳一個 *note FrameInfo: 5f2. 物件串列。

 -- 函式: inspect.trace (context=1)

     Return a list of *note FrameInfo: 5f2. objects for the stack
     between the current frame and the frame in which an exception
     currently being handled was raised in.  The first entry in the list
     represents the caller; the last entry represents where the
     exception was raised.

     在 3.5 版的變更: A list of *note named tuples: 5f4.
     ‘FrameInfo(frame, filename, lineno, function, code_context, index)’
     is returned.

     在 3.11 版的變更: 回傳一個 *note FrameInfo: 5f2. 物件串列。


File: python.info,  Node: Fetching attributes statically,  Next: Current State of Generators Coroutines and Asynchronous Generators,  Prev: 直譯器堆疊,  Up: inspect --- 檢視活動物件

5.29.14.6 Fetching attributes statically
........................................

Both *note getattr(): b78. and *note hasattr(): 479. can trigger code
execution when fetching or checking for the existence of attributes.
Descriptors, like properties, will be invoked and *note __getattr__():
47a. and *note __getattribute__(): b79. may be called.

For cases where you want passive introspection, like documentation
tools, this can be inconvenient.  *note getattr_static(): 43c. has the
same signature as *note getattr(): b78. but avoids executing code when
it fetches attributes.

 -- 函式: inspect.getattr_static (obj, attr, default=None)

     Retrieve attributes without triggering dynamic lookup via the
     descriptor protocol, *note __getattr__(): 47a. or *note
     __getattribute__(): b79.

     Note: this function may not be able to retrieve all attributes that
     getattr can fetch (like dynamically created attributes) and may
     find attributes that getattr can't (like descriptors that raise
     AttributeError).  It can also return descriptors objects instead of
     instance members.

     If the instance *note __dict__: c04. is shadowed by another member
     (for example a property) then this function will be unable to find
     instance members.

     在 3.2 版被加入.

*note getattr_static(): 43c. does not resolve descriptors, for example
slot descriptors or getset descriptors on objects implemented in C. The
descriptor object is returned instead of the underlying attribute.

You can handle these with code like the following.  Note that for
arbitrary getset descriptors invoking these may trigger code execution:

     # example code for resolving the builtin descriptor types
     class _foo:
         __slots__ = ['foo']

     slot_descriptor = type(_foo.foo)
     getset_descriptor = type(type(open(__file__)).name)
     wrapper_descriptor = type(str.__dict__['__add__'])
     descriptor_types = (slot_descriptor, getset_descriptor, wrapper_descriptor)

     result = getattr_static(some_object, 'foo')
     if type(result) in descriptor_types:
         try:
             result = result.__get__()
         except AttributeError:
             # descriptors can raise AttributeError to
             # indicate there is no underlying value
             # in which case the descriptor itself will
             # have to do
             pass


File: python.info,  Node: Current State of Generators Coroutines and Asynchronous Generators,  Next: Code Objects Bit Flags,  Prev: Fetching attributes statically,  Up: inspect --- 檢視活動物件

5.29.14.7 Current State of Generators, Coroutines, and Asynchronous Generators
..............................................................................

When implementing coroutine schedulers and for other advanced uses of
generators, it is useful to determine whether a generator is currently
executing, is waiting to start or resume or execution, or has already
terminated.  *note getgeneratorstate(): 11ce. allows the current state
of a generator to be determined easily.

 -- 函式: inspect.getgeneratorstate (generator)

     Get current state of a generator-iterator.

     Possible states are:

        * GEN_CREATED: Waiting to start execution.

        * GEN_RUNNING: Currently being executed by the interpreter.

        * GEN_SUSPENDED: Currently suspended at a yield expression.

        * GEN_CLOSED: Execution has completed.

     在 3.2 版被加入.

 -- 函式: inspect.getcoroutinestate (coroutine)

     Get current state of a coroutine object.  The function is intended
     to be used with coroutine objects created by *note async def: 575.
     functions, but will accept any coroutine-like object that has
     ‘cr_running’ and ‘cr_frame’ attributes.

     Possible states are:

        * CORO_CREATED: Waiting to start execution.

        * CORO_RUNNING: Currently being executed by the interpreter.

        * CORO_SUSPENDED: Currently suspended at an await expression.

        * CORO_CLOSED: Execution has completed.

     在 3.5 版被加入.

 -- 函式: inspect.getasyncgenstate (agen)

     Get current state of an asynchronous generator object.  The
     function is intended to be used with asynchronous iterator objects
     created by *note async def: 575. functions which use the *note
     yield: 971. statement, but will accept any asynchronous
     generator-like object that has ‘ag_running’ and ‘ag_frame’
     attributes.

     Possible states are:

        * AGEN_CREATED: 等待開始執行。

        * AGEN_RUNNING: 目前正在被直譯器執行。

        * AGEN_SUSPENDED: 目前於 yield 運算式暫停。

        * AGEN_CLOSED: 執行已完成。

     在 3.12 版被加入.

The current internal state of the generator can also be queried.  This
is mostly useful for testing purposes, to ensure that internal state is
being updated as expected:

 -- 函式: inspect.getgeneratorlocals (generator)

     Get the mapping of live local variables in 'generator' to their
     current values.  A dictionary is returned that maps from variable
     names to values.  This is the equivalent of calling *note locals():
     127. in the body of the generator, and all the same caveats apply.

     If 'generator' is a *note generator: 1004. with no currently
     associated frame, then an empty dictionary is returned.  *note
     TypeError: 4dd. is raised if 'generator' is not a Python generator
     object.

     'CPython 實作細節：' This function relies on the generator exposing
     a Python stack frame for introspection, which isn't guaranteed to
     be the case in all implementations of Python.  In such cases, this
     function will always return an empty dictionary.

     在 3.3 版被加入.

 -- 函式: inspect.getcoroutinelocals (coroutine)

     This function is analogous to *note getgeneratorlocals(): 1070, but
     works for coroutine objects created by *note async def: 575.
     functions.

     在 3.5 版被加入.

 -- 函式: inspect.getasyncgenlocals (agen)

     This function is analogous to *note getgeneratorlocals(): 1070, but
     works for asynchronous generator objects created by *note async
     def: 575. functions which use the *note yield: 971. statement.

     在 3.12 版被加入.


File: python.info,  Node: Code Objects Bit Flags,  Next: Buffer flags,  Prev: Current State of Generators Coroutines and Asynchronous Generators,  Up: inspect --- 檢視活動物件

5.29.14.8 Code Objects Bit Flags
................................

Python code objects have a *note co_flags: 1e1a. attribute, which is a
bitmap of the following flags:

 -- 資料: inspect.CO_OPTIMIZED

     The code object is optimized, using fast locals.

 -- 資料: inspect.CO_NEWLOCALS

     If set, a new dict will be created for the frame's *note f_locals:
     165. when the code object is executed.

 -- 資料: inspect.CO_VARARGS

     The code object has a variable positional parameter (‘*args’-like).

 -- 資料: inspect.CO_VARKEYWORDS

     The code object has a variable keyword parameter (‘**kwargs’-like).

 -- 資料: inspect.CO_NESTED

     The flag is set when the code object is a nested function.

 -- 資料: inspect.CO_GENERATOR

     The flag is set when the code object is a generator function, i.e.
     a generator object is returned when the code object is executed.

 -- 資料: inspect.CO_COROUTINE

     The flag is set when the code object is a coroutine function.  When
     the code object is executed it returns a coroutine object.  See PEP
     492(1) for more details.

     在 3.5 版被加入.

 -- 資料: inspect.CO_ITERABLE_COROUTINE

     The flag is used to transform generators into generator-based
     coroutines.  Generator objects with this flag can be used in
     ‘await’ expression, and can ‘yield from’ coroutine objects.  See
     PEP 492(2) for more details.

     在 3.5 版被加入.

 -- 資料: inspect.CO_ASYNC_GENERATOR

     The flag is set when the code object is an asynchronous generator
     function.  When the code object is executed it returns an
     asynchronous generator object.  See PEP 525(3) for more details.

     在 3.6 版被加入.

     備註: The flags are specific to CPython, and may not be defined in
     other Python implementations.  Furthermore, the flags are an
     implementation detail, and can be removed or deprecated in future
     Python releases.  It's recommended to use public APIs from the
     *note inspect: 72. module for any introspection needs.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0492/

   (2) https://peps.python.org/pep-0492/

   (3) https://peps.python.org/pep-0525/


File: python.info,  Node: Buffer flags,  Next: 命令列介面<6>,  Prev: Code Objects Bit Flags,  Up: inspect --- 檢視活動物件

5.29.14.9 Buffer flags
......................

 -- 類別: inspect.BufferFlags

     This is an *note enum.IntFlag: 21d7. that represents the flags that
     can be passed to the *note __buffer__(): 405. method of objects
     implementing the *note buffer protocol: 367.

     The meaning of the flags is explained at *note Buffer request
     types: 42b9.

      -- 屬性: SIMPLE

      -- 屬性: WRITABLE

      -- 屬性: FORMAT

      -- 屬性: ND

      -- 屬性: STRIDES

      -- 屬性: C_CONTIGUOUS

      -- 屬性: F_CONTIGUOUS

      -- 屬性: ANY_CONTIGUOUS

      -- 屬性: INDIRECT

      -- 屬性: CONTIG

      -- 屬性: CONTIG_RO

      -- 屬性: STRIDED

      -- 屬性: STRIDED_RO

      -- 屬性: RECORDS

      -- 屬性: RECORDS_RO

      -- 屬性: FULL

      -- 屬性: FULL_RO

      -- 屬性: READ

      -- 屬性: WRITE

     在 3.12 版被加入.


File: python.info,  Node: 命令列介面<6>,  Prev: Buffer flags,  Up: inspect --- 檢視活動物件

5.29.14.10 命令列介面
.....................

The *note inspect: 72. module also provides a basic introspection
capability from the command line.

By default, accepts the name of a module and prints the source of that
module.  A class or function within the module can be printed instead by
appended a colon and the qualified name of the target object.

 -- Option: --details

     Print information about the specified object rather than the source
     code


File: python.info,  Node: site --- Site-specific configuration hook,  Prev: inspect --- 檢視活動物件,  Up: Python Runtime 服務

5.29.15 ‘site’ -- Site-specific configuration hook
--------------------------------------------------

'原始碼：'Lib/site.py(1)

__________________________________________________________________

'This module is automatically imported during initialization.'  The
automatic import can be suppressed using the interpreter's *note -S:
1140. option.

Importing this module normally appends site-specific paths to the module
search path and adds *note callables: 2064, including *note help(): 87c.
to the built-in namespace.  However, Python startup option *note -S:
1140. blocks this and this module can be safely imported with no
automatic modifications to the module search path or additions to the
builtins.  To explicitly trigger the usual site-specific additions, call
the *note main(): 1c38. function.

在 3.3 版的變更: Importing the module used to trigger paths manipulation
even when using *note -S: 1140.

It starts by constructing up to four directories from a head and a tail
part.  For the head part, it uses ‘sys.prefix’ and ‘sys.exec_prefix’;
empty heads are skipped.  For the tail part, it uses the empty string
and then ‘lib/site-packages’ (on Windows) or
‘lib/python`X.Y[t]'/site-packages’ (on Unix and macOS). (The optional
suffix "t" indicates the *note free threading: 42d1. build, and is
appended if ‘"t"’ is present in the *note sys.abiflags: a07. constant.)
For each of the distinct head-tail combinations, it sees if it refers to
an existing directory, and if so, adds it to ‘sys.path’ and also
inspects the newly added path for configuration files.

在 3.5 版的變更: Support for the "site-python" directory has been
removed.

在 3.13 版的變更: On Unix, *note Free threading: 42d1. Python
installations are identified by the "t" suffix in the version-specific
directory name, such as ‘lib/python3.13t/’.

If a file named "pyvenv.cfg" exists one directory above sys.executable,
sys.prefix and sys.exec_prefix are set to that directory and it is also
checked for site-packages (sys.base_prefix and sys.base_exec_prefix will
always be the "real" prefixes of the Python installation).  If
"pyvenv.cfg" (a bootstrap configuration file) contains the key
"include-system-site-packages" set to anything other than "true"
(case-insensitive), the system-level prefixes will not be searched for
site-packages; otherwise they will.

A path configuration file is a file whose name has the form ‘`name'.pth’
and exists in one of the four directories mentioned above; its contents
are additional items (one per line) to be added to ‘sys.path’.
Non-existing items are never added to ‘sys.path’, and no check is made
that the item refers to a directory rather than a file.  No item is
added to ‘sys.path’ more than once.  Blank lines and lines beginning
with ‘#’ are skipped.  Lines starting with ‘import’ (followed by space
or tab) are executed.

     備註: An executable line in a ‘.pth’ file is run at every Python
     startup, regardless of whether a particular module is actually
     going to be used.  Its impact should thus be kept to a minimum.
     The primary intended purpose of executable lines is to make the
     corresponding module(s) importable (load 3rd-party import hooks,
     adjust ‘PATH’ etc).  Any other initialization is supposed to be
     done upon a module's actual import, if and when it happens.
     Limiting a code chunk to a single line is a deliberate measure to
     discourage putting anything more complex here.

在 3.13 版的變更: The ‘.pth’ files are now decoded by UTF-8 at first and
then by the *note locale encoding: 227. if it fails.

For example, suppose ‘sys.prefix’ and ‘sys.exec_prefix’ are set to
‘/usr/local’.  The Python X.Y library is then installed in
‘/usr/local/lib/python`X.Y'’.  Suppose this has a subdirectory
‘/usr/local/lib/python`X.Y'/site-packages’ with three subsubdirectories,
‘foo’, ‘bar’ and ‘spam’, and two path configuration files, ‘foo.pth’ and
‘bar.pth’.  Assume ‘foo.pth’ contains the following:

     # foo package configuration

     foo
     bar
     bletch

and ‘bar.pth’ contains:

     # bar package configuration

     bar

Then the following version-specific directories are added to ‘sys.path’,
in this order:

     /usr/local/lib/pythonX.Y/site-packages/bar
     /usr/local/lib/pythonX.Y/site-packages/foo

Note that ‘bletch’ is omitted because it doesn't exist; the ‘bar’
directory precedes the ‘foo’ directory because ‘bar.pth’ comes
alphabetically before ‘foo.pth’; and ‘spam’ is omitted because it is not
mentioned in either path configuration file.

* Menu:

* sitecustomize::
* usercustomize::
* Readline configuration::
* 模組內容: 模組內容<10>.
* 命令列介面: 命令列介面<7>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/site.py


File: python.info,  Node: sitecustomize,  Next: usercustomize,  Up: site --- Site-specific configuration hook

5.29.15.1 ‘sitecustomize’
.........................

After these path manipulations, an attempt is made to import a module
named *note sitecustomize: b6, which can perform arbitrary site-specific
customizations.  It is typically created by a system administrator in
the site-packages directory.  If this import fails with an *note
ImportError: 352. or its subclass exception, and the exception's *note
name: 2165. attribute equals to ‘'sitecustomize'’, it is silently
ignored.  If Python is started without output streams available, as with
‘pythonw.exe’ on Windows (which is used by default to start IDLE),
attempted output from *note sitecustomize: b6. is ignored.  Any other
exception causes a silent and perhaps mysterious failure of the process.


File: python.info,  Node: usercustomize,  Next: Readline configuration,  Prev: sitecustomize,  Up: site --- Site-specific configuration hook

5.29.15.2 ‘usercustomize’
.........................

After this, an attempt is made to import a module named *note
usercustomize: f7, which can perform arbitrary user-specific
customizations, if *note ENABLE_USER_SITE: 42d4. is true.  This file is
intended to be created in the user site-packages directory (see below),
which is part of ‘sys.path’ unless disabled by *note -s: 1319.  If this
import fails with an *note ImportError: 352. or its subclass exception,
and the exception's *note name: 2165. attribute equals to
‘'usercustomize'’, it is silently ignored.

Note that for some non-Unix systems, ‘sys.prefix’ and ‘sys.exec_prefix’
are empty, and the path manipulations are skipped; however the import of
*note sitecustomize: b6. and *note usercustomize: f7. is still
attempted.


File: python.info,  Node: Readline configuration,  Next: 模組內容<10>,  Prev: usercustomize,  Up: site --- Site-specific configuration hook

5.29.15.3 Readline configuration
................................

On systems that support *note readline: a8, this module will also import
and configure the *note rlcompleter: ab. module, if Python is started in
*note interactive mode: f69. and without the *note -S: 1140. option.
The default behavior is enable tab-completion and to use
‘~/.python_history’ as the history save file.  To disable it, delete (or
override) the *note sys.__interactivehook__: f6a. attribute in your
*note sitecustomize: b6. or *note usercustomize: f7. module or your
*note PYTHONSTARTUP: f6b. file.

在 3.4 版的變更: Activation of rlcompleter and history was made
automatic.


File: python.info,  Node: 模組內容<10>,  Next: 命令列介面<7>,  Prev: Readline configuration,  Up: site --- Site-specific configuration hook

5.29.15.4 模組內容
..................

 -- 資料: site.PREFIXES

     A list of prefixes for site-packages directories.

 -- 資料: site.ENABLE_USER_SITE

     Flag showing the status of the user site-packages directory.
     ‘True’ means that it is enabled and was added to ‘sys.path’.
     ‘False’ means that it was disabled by user request (with *note -s:
     1319. or *note PYTHONNOUSERSITE: 131a.).  ‘None’ means it was
     disabled for security reasons (mismatch between user or group id
     and effective id) or by an administrator.

 -- 資料: site.USER_SITE

     Path to the user site-packages for the running Python.  Can be
     ‘None’ if *note getusersitepackages(): 11d8. hasn't been called
     yet.  Default value is ‘~/.local/lib/python`X.Y'[t]/site-packages’
     for UNIX and non-framework macOS builds,
     ‘~/Library/Python/`X.Y'/lib/python/site-packages’ for macOS
     framework builds, and ‘`%APPDATA%'\Python\Python`XY'\site-packages’
     on Windows.  The optional "t" indicates the free-threaded build.
     This directory is a site directory, which means that ‘.pth’ files
     in it will be processed.

 -- 資料: site.USER_BASE

     Path to the base directory for the user site-packages.  Can be
     ‘None’ if *note getuserbase(): 11d7. hasn't been called yet.
     Default value is ‘~/.local’ for UNIX and macOS non-framework
     builds, ‘~/Library/Python/`X.Y'’ for macOS framework builds, and
     ‘`%APPDATA%'\Python’ for Windows.  This value is used to compute
     the installation directories for scripts, data files, Python
     modules, etc.  for the *note user installation scheme: 1c49.  See
     also *note PYTHONUSERBASE: 1318.

 -- 函式: site.main ()

     Adds all the standard site-specific directories to the module
     search path.  This function is called automatically when this
     module is imported, unless the Python interpreter was started with
     the *note -S: 1140. flag.

     在 3.3 版的變更: This function used to be called unconditionally.

 -- 函式: site.addsitedir (sitedir, known_paths=None)

     Add a directory to sys.path and process its ‘.pth’ files.
     Typically used in *note sitecustomize: b6. or *note usercustomize:
     f7. (see above).

 -- 函式: site.getsitepackages ()

     Return a list containing all global site-packages directories.

     在 3.2 版被加入.

 -- 函式: site.getuserbase ()

     Return the path of the user base directory, *note USER_BASE: 12b0.
     If it is not initialized yet, this function will also set it,
     respecting *note PYTHONUSERBASE: 1318.

     在 3.2 版被加入.

 -- 函式: site.getusersitepackages ()

     Return the path of the user-specific site-packages directory, *note
     USER_SITE: 1c37.  If it is not initialized yet, this function will
     also set it, respecting *note USER_BASE: 12b0.  To determine if the
     user-specific site-packages was added to ‘sys.path’ *note
     ENABLE_USER_SITE: 42d4. should be used.

     在 3.2 版被加入.


File: python.info,  Node: 命令列介面<7>,  Prev: 模組內容<10>,  Up: site --- Site-specific configuration hook

5.29.15.5 命令列介面
....................

The *note site: b5. module also provides a way to get the user
directories from the command line:

     $ python -m site --user-site
     /home/user/.local/lib/python3.11/site-packages

If it is called without arguments, it will print the contents of *note
sys.path: 37f. on the standard output, followed by the value of *note
USER_BASE: 12b0. and whether the directory exists, then the same thing
for *note USER_SITE: 1c37, and finally the value of *note
ENABLE_USER_SITE: 42d4.

 -- Option: --user-base

     Print the path to the user base directory.

 -- Option: --user-site

     Print the path to the user site-packages directory.

If both options are given, user base and user site will be printed
(always in this order), separated by *note os.pathsep: 1c46.

If any option is given, the script will exit with one of these values:
‘0’ if the user site-packages directory is enabled, ‘1’ if it was
disabled by the user, ‘2’ if it is disabled for security reasons or by
an administrator, and a value greater than 2 if there is an error.

也參考
......

   * PEP 370(1) - Per user site-packages directory

   * *note The initialization of the sys.path module search path: 1b64.
     - The initialization of *note sys.path: 37f.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0370/


File: python.info,  Node: 自訂 Python 直譯器,  Next: 引入模組,  Prev: Python Runtime 服務,  Up: Python 標準函式庫 Standard Library

5.30 自訂 Python 直譯器
=======================

The modules described in this chapter allow writing interfaces similar
to Python's interactive interpreter.  If you want a Python interpreter
that supports some special feature in addition to the Python language,
you should look at the *note code: 13. module.  (The *note codeop: 15.
module is lower-level, used to support compiling a possibly incomplete
chunk of Python code.)

本章節所描述的模組清單為：

* Menu:

* code: code --- 直譯器基底類別. 直譯器基底類別
* codeop: codeop --- 編譯 Python 程式碼. 編譯 Python 程式碼


File: python.info,  Node: code --- 直譯器基底類別,  Next: codeop --- 編譯 Python 程式碼,  Up: 自訂 Python 直譯器

5.30.1 ‘code’ -- 直譯器基底類別
-------------------------------

'原始碼：'Lib/code.py(1)

__________________________________________________________________

The ‘code’ module provides facilities to implement read-eval-print loops
in Python.  Two classes and convenience functions are included which can
be used to build applications which provide an interactive interpreter
prompt.

 -- 類別: code.InteractiveInterpreter (locals=None)

     This class deals with parsing and interpreter state (the user's
     namespace); it does not deal with input buffering or prompting or
     input file naming (the filename is always passed in explicitly).
     The optional 'locals' argument specifies a mapping to use as the
     namespace in which code will be executed; it defaults to a newly
     created dictionary with key ‘'__name__'’ set to ‘'__console__'’ and
     key ‘'__doc__'’ set to ‘None’.

 -- 類別: code.InteractiveConsole (locals=None, filename='<console>',
          local_exit=False)

     Closely emulate the behavior of the interactive Python interpreter.
     This class builds on *note InteractiveInterpreter: 14cc. and adds
     prompting using the familiar ‘sys.ps1’ and ‘sys.ps2’, and input
     buffering.  If 'local_exit' is true, ‘exit()’ and ‘quit()’ in the
     console will not raise *note SystemExit: ce7, but instead return to
     the calling code.

     在 3.13 版的變更: Added 'local_exit' parameter.

 -- 函式: code.interact (banner=None, readfunc=None, local=None,
          exitmsg=None, local_exit=False)

     Convenience function to run a read-eval-print loop.  This creates a
     new instance of *note InteractiveConsole: 227a. and sets 'readfunc'
     to be used as the *note InteractiveConsole.raw_input(): 42e2.
     method, if provided.  If 'local' is provided, it is passed to the
     *note InteractiveConsole: 227a. constructor for use as the default
     namespace for the interpreter loop.  If 'local_exit' is provided,
     it is passed to the *note InteractiveConsole: 227a. constructor.
     The *note interact(): 42e3. method of the instance is then run with
     'banner' and 'exitmsg' passed as the banner and exit message to
     use, if provided.  The console object is discarded after use.

     在 3.6 版的變更: 新增 'exitmsg' 參數。

     在 3.13 版的變更: Added 'local_exit' parameter.

 -- 函式: code.compile_command (source, filename='<input>',
          symbol='single')

     This function is useful for programs that want to emulate Python's
     interpreter main loop (a.k.a.  the read-eval-print loop).  The
     tricky part is to determine when the user has entered an incomplete
     command that can be completed by entering more text (as opposed to
     a complete command or a syntax error).  This function 'almost'
     always makes the same decision as the real interpreter main loop.

     'source' is the source string; 'filename' is the optional filename
     from which source was read, defaulting to ‘'<input>'’; and 'symbol'
     is the optional grammar start symbol, which should be ‘'single'’
     (the default), ‘'eval'’ or ‘'exec'’.

     Returns a code object (the same as ‘compile(source, filename,
     symbol)’) if the command is complete and valid; ‘None’ if the
     command is incomplete; raises *note SyntaxError: 173. if the
     command is complete and contains a syntax error, or raises *note
     OverflowError: 825. or *note ValueError: 1e7. if the command
     contains an invalid literal.

* Menu:

* Interactive Interpreter Objects::
* Interactive Console Objects::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/code.py


File: python.info,  Node: Interactive Interpreter Objects,  Next: Interactive Console Objects,  Up: code --- 直譯器基底類別

5.30.1.1 Interactive Interpreter Objects
........................................

 -- 方法: InteractiveInterpreter.runsource (source, filename='<input>',
          symbol='single')

     Compile and run some source in the interpreter.  Arguments are the
     same as for *note compile_command(): 42e4.; the default for
     'filename' is ‘'<input>'’, and for 'symbol' is ‘'single'’.  One of
     several things can happen:

        * The input is incorrect; *note compile_command(): 42e4. raised
          an exception (*note SyntaxError: 173. or *note OverflowError:
          825.).  A syntax traceback will be printed by calling the
          *note showsyntaxerror(): 42e8. method.  *note runsource():
          42e7. returns ‘False’.

        * The input is incomplete, and more input is required; *note
          compile_command(): 42e4. returned ‘None’.  *note runsource():
          42e7. returns ‘True’.

        * The input is complete; *note compile_command(): 42e4. returned
          a code object.  The code is executed by calling the *note
          runcode(): 42e9. (which also handles run-time exceptions,
          except for *note SystemExit: ce7.).  *note runsource(): 42e7.
          returns ‘False’.

     The return value can be used to decide whether to use ‘sys.ps1’ or
     ‘sys.ps2’ to prompt the next line.

 -- 方法: InteractiveInterpreter.runcode (code)

     Execute a code object.  When an exception occurs, *note
     showtraceback(): d76. is called to display a traceback.  All
     exceptions are caught except *note SystemExit: ce7, which is
     allowed to propagate.

     A note about *note KeyboardInterrupt: 975.: this exception may
     occur elsewhere in this code, and may not always be caught.  The
     caller should be prepared to deal with it.

 -- 方法: InteractiveInterpreter.showsyntaxerror (filename=None)

     Display the syntax error that just occurred.  This does not display
     a stack trace because there isn't one for syntax errors.  If
     'filename' is given, it is stuffed into the exception instead of
     the default filename provided by Python's parser, because it always
     uses ‘'<string>'’ when reading from a string.  The output is
     written by the *note write(): 42ea. method.

 -- 方法: InteractiveInterpreter.showtraceback ()

     Display the exception that just occurred.  We remove the first
     stack item because it is within the interpreter object
     implementation.  The output is written by the *note write(): 42ea.
     method.

     在 3.5 版的變更: The full chained traceback is displayed instead of
     just the primary traceback.

 -- 方法: InteractiveInterpreter.write (data)

     Write a string to the standard error stream (‘sys.stderr’).
     Derived classes should override this to provide the appropriate
     output handling as needed.


File: python.info,  Node: Interactive Console Objects,  Prev: Interactive Interpreter Objects,  Up: code --- 直譯器基底類別

5.30.1.2 Interactive Console Objects
....................................

The *note InteractiveConsole: 227a. class is a subclass of *note
InteractiveInterpreter: 14cc, and so offers all the methods of the
interpreter objects as well as the following additions.

 -- 方法: InteractiveConsole.interact (banner=None, exitmsg=None)

     Closely emulate the interactive Python console.  The optional
     'banner' argument specify the banner to print before the first
     interaction; by default it prints a banner similar to the one
     printed by the standard Python interpreter, followed by the class
     name of the console object in parentheses (so as not to confuse
     this with the real interpreter - since it's so close!).

     The optional 'exitmsg' argument specifies an exit message printed
     when exiting.  Pass the empty string to suppress the exit message.
     If 'exitmsg' is not given or ‘None’, a default message is printed.

     在 3.4 版的變更: To suppress printing any banner, pass an empty
     string.

     在 3.6 版的變更: Print an exit message when exiting.

 -- 方法: InteractiveConsole.push (line)

     Push a line of source text to the interpreter.  The line should not
     have a trailing newline; it may have internal newlines.  The line
     is appended to a buffer and the interpreter's *note runsource():
     42e7. method is called with the concatenated contents of the buffer
     as source.  If this indicates that the command was executed or
     invalid, the buffer is reset; otherwise, the command is incomplete,
     and the buffer is left as it was after the line was appended.  The
     return value is ‘True’ if more input is required, ‘False’ if the
     line was dealt with in some way (this is the same as
     ‘runsource()’).

 -- 方法: InteractiveConsole.resetbuffer ()

     Remove any unhandled source text from the input buffer.

 -- 方法: InteractiveConsole.raw_input (prompt='')

     Write a prompt and read a line.  The returned line does not include
     the trailing newline.  When the user enters the EOF key sequence,
     *note EOFError: 126c. is raised.  The base implementation reads
     from ‘sys.stdin’; a subclass may replace this with a different
     implementation.


File: python.info,  Node: codeop --- 編譯 Python 程式碼,  Prev: code --- 直譯器基底類別,  Up: 自訂 Python 直譯器

5.30.2 ‘codeop’ -- 編譯 Python 程式碼
-------------------------------------

'原始碼：'Lib/codeop.py(1)

__________________________________________________________________

The *note codeop: 15. module provides utilities upon which the Python
read-eval-print loop can be emulated, as is done in the *note code: 13.
module.  As a result, you probably don't want to use the module
directly; if you want to include such a loop in your program you
probably want to use the *note code: 13. module instead.

There are two parts to this job:

  1. Being able to tell if a line of input completes a Python statement:
     in short, telling whether to print '‘>>>’' or '‘...’' next.

  2. Remembering which future statements the user has entered, so
     subsequent input can be compiled with these in effect.

The *note codeop: 15. module provides a way of doing each of these
things, and a way of doing them both.

To do just the former:

 -- 函式: codeop.compile_command (source, filename='<input>',
          symbol='single')

     Tries to compile 'source', which should be a string of Python code
     and return a code object if 'source' is valid Python code.  In that
     case, the filename attribute of the code object will be 'filename',
     which defaults to ‘'<input>'’.  Returns ‘None’ if 'source' is 'not'
     valid Python code, but is a prefix of valid Python code.

     If there is a problem with 'source', an exception will be raised.
     *note SyntaxError: 173. is raised if there is invalid Python
     syntax, and *note OverflowError: 825. or *note ValueError: 1e7. if
     there is an invalid literal.

     The 'symbol' argument determines whether 'source' is compiled as a
     statement (‘'single'’, the default), as a sequence of *note
     statement: 265e. (‘'exec'’) or as an *note expression: 1e5c.
     (‘'eval'’).  Any other value will cause *note ValueError: 1e7. to
     be raised.

          備註: It is possible (but not likely) that the parser stops
          parsing with a successful outcome before reaching the end of
          the source; in this case, trailing symbols may be ignored
          instead of causing an error.  For example, a backslash
          followed by two newlines may be followed by arbitrary garbage.
          This will be fixed once the API for the parser is better.

 -- 類別: codeop.Compile

     Instances of this class have *note __call__(): 4fe. methods
     identical in signature to the built-in function *note compile():
     178, but with the difference that if the instance compiles program
     text containing a *note __future__: 0. statement, the instance
     'remembers' and compiles all subsequent program texts with the
     statement in force.

 -- 類別: codeop.CommandCompiler

     Instances of this class have *note __call__(): 4fe. methods
     identical in signature to *note compile_command(): 16cd.; the
     difference is that if the instance compiles program text containing
     a *note __future__: 0. statement, the instance 'remembers' and
     compiles all subsequent program texts with the statement in force.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/codeop.py


File: python.info,  Node: 引入模組,  Next: Python 語言服務,  Prev: 自訂 Python 直譯器,  Up: Python 標準函式庫 Standard Library

5.31 引入模組
=============

The modules described in this chapter provide new ways to import other
Python modules and hooks for customizing the import process.

The full list of modules described in this chapter is:

* Menu:

* zipimport: zipimport --- 從 Zip 封存檔案匯入模組. 從 Zip 封存檔案匯入模組
* pkgutil: pkgutil --- 套件擴充工具程式. 套件擴充工具程式
* modulefinder: modulefinder --- 搜尋腳本所使用的模組. 搜尋腳本所使用的模組
* runpy: runpy --- 定位並執行 Python 模組. 定位並執行 Python 模組
* importlib: importlib --- import 的實作. import 的實作
* importlib.resources: importlib resources -- Package resource reading opening and access. Package resource reading, opening and access
* importlib.resources.abc: importlib resources abc -- 資源的抽象基底類別. 資源的抽象基底類別
* importlib.metadata: importlib metadata -- 存取套件的元資料. 存取套件的元資料
* The initialization of the sys.path module search path: The initialization of the sys path module search path.


File: python.info,  Node: zipimport --- 從 Zip 封存檔案匯入模組,  Next: pkgutil --- 套件擴充工具程式,  Up: 引入模組

5.31.1 ‘zipimport’ -- 從 Zip 封存檔案匯入模組
---------------------------------------------

'原始碼：'Lib/zipimport.py(1)

__________________________________________________________________

This module adds the ability to import Python modules (‘*.py’, ‘*.pyc’)
and packages from ZIP-format archives.  It is usually not needed to use
the *note zipimport: 118. module explicitly; it is automatically used by
the built-in *note import: 586. mechanism for *note sys.path: 37f. items
that are paths to ZIP archives.

Typically, *note sys.path: 37f. is a list of directory names as strings.
This module also allows an item of *note sys.path: 37f. to be a string
naming a ZIP file archive.  The ZIP archive can contain a subdirectory
structure to support package imports, and a path within the archive can
be specified to only import from a subdirectory.  For example, the path
‘example.zip/lib/’ would only import from the ‘lib/’ subdirectory within
the archive.

Any files may be present in the ZIP archive, but importers are only
invoked for ‘.py’ and ‘.pyc’ files.  ZIP import of dynamic modules
(‘.pyd’, ‘.so’) is disallowed.  Note that if an archive only contains
‘.py’ files, Python will not attempt to modify the archive by adding the
corresponding ‘.pyc’ file, meaning that if a ZIP archive doesn't contain
‘.pyc’ files, importing may be rather slow.

在 3.13 版的變更: ZIP64 is supported

在 3.8 版的變更: Previously, ZIP archives with an archive comment were
not supported.

也參考
......

PKZIP Application Note(2)

     Documentation on the ZIP file format by Phil Katz, the creator of
     the format and algorithms used.

PEP 273(3) - Import Modules from Zip Archives

     Written by James C. Ahlstrom, who also provided an implementation.
     Python 2.3 follows the specification in PEP 273(4), but uses an
     implementation written by Just van Rossum that uses the import
     hooks described in PEP 302(5).

*note importlib: 6b. - The implementation of the import machinery

     Package providing the relevant protocols for all importers to
     implement.

This module defines an exception:

 -- 例外: zipimport.ZipImportError

     Exception raised by zipimporter objects.  It's a subclass of *note
     ImportError: 352, so it can be caught as *note ImportError: 352,
     too.

* Menu:

* zipimporter 物件::
* 範例: 範例<45>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/zipimport.py

   (2) https://pkware.cachefly.net/webdocs/casestudies/APPNOTE.TXT

   (3) https://peps.python.org/pep-0273/

   (4) https://peps.python.org/pep-0273/

   (5) https://peps.python.org/pep-0302/


File: python.info,  Node: zipimporter 物件,  Next: 範例<45>,  Up: zipimport --- 從 Zip 封存檔案匯入模組

5.31.1.1 zipimporter 物件
.........................

*note zipimporter: 42fb. is the class for importing ZIP files.

 -- 類別: zipimport.zipimporter (archivepath)

     Create a new zipimporter instance.  'archivepath' must be a path to
     a ZIP file, or to a specific path within a ZIP file.  For example,
     an 'archivepath' of ‘foo/bar.zip/lib’ will look for modules in the
     ‘lib’ directory inside the ZIP file ‘foo/bar.zip’ (provided that it
     exists).

     *note ZipImportError: 42f8. is raised if 'archivepath' doesn't
     point to a valid ZIP archive.

     在 3.12 版的變更: Methods ‘find_loader()’ and ‘find_module()’,
     deprecated in 3.10 are now removed.  Use *note find_spec(): 802.
     instead.

      -- 方法: create_module (spec)

          Implementation of *note importlib.abc.Loader.create_module():
          c55. that returns *note None: 61b. to explicitly request the
          default semantics.

          在 3.10 版被加入.

      -- 方法: exec_module (module)

          Implementation of *note importlib.abc.Loader.exec_module():
          80f.

          在 3.10 版被加入.

      -- 方法: find_spec (fullname, target=None)

          An implementation of *note
          importlib.abc.PathEntryFinder.find_spec(): 811.

          在 3.10 版被加入.

      -- 方法: get_code (fullname)

          Return the code object for the specified module.  Raise *note
          ZipImportError: 42f8. if the module couldn't be imported.

      -- 方法: get_data (pathname)

          Return the data associated with 'pathname'.  Raise *note
          OSError: 350. if the file wasn't found.

          在 3.3 版的變更: *note IOError: ff5. used to be raised, it is
          now an alias of *note OSError: 350.

      -- 方法: get_filename (fullname)

          Return the value ‘__file__’ would be set to if the specified
          module was imported.  Raise *note ZipImportError: 42f8. if the
          module couldn't be imported.

          在 3.1 版被加入.

      -- 方法: get_source (fullname)

          Return the source code for the specified module.  Raise *note
          ZipImportError: 42f8. if the module couldn't be found, return
          *note None: 61b. if the archive does contain the module, but
          has no source for it.

      -- 方法: is_package (fullname)

          Return ‘True’ if the module specified by 'fullname' is a
          package.  Raise *note ZipImportError: 42f8. if the module
          couldn't be found.

      -- 方法: load_module (fullname)

          Load the module specified by 'fullname'.  'fullname' must be
          the fully qualified (dotted) module name.  Returns the
          imported module on success, raises *note ZipImportError: 42f8.
          on failure.

          在 3.10 版之後被棄用: Use *note exec_module(): 2e4. instead.

      -- 方法: invalidate_caches ()

          Clear out the internal cache of information about files found
          within the ZIP archive.

          在 3.10 版被加入.

      -- 屬性: archive

          The file name of the importer's associated ZIP file, without a
          possible subpath.

      -- 屬性: prefix

          The subpath within the ZIP file where modules are searched.
          This is the empty string for zipimporter objects which point
          to the root of the ZIP file.

     The *note archive: 4301. and *note prefix: 4302. attributes, when
     combined with a slash, equal the original 'archivepath' argument
     given to the *note zipimporter: 42fb. constructor.


File: python.info,  Node: 範例<45>,  Prev: zipimporter 物件,  Up: zipimport --- 從 Zip 封存檔案匯入模組

5.31.1.2 範例
.............

Here is an example that imports a module from a ZIP archive - note that
the *note zipimport: 118. module is not explicitly used.

     $ unzip -l example.zip
     Archive:  example.zip
       Length     Date   Time    Name
      --------    ----   ----    ----
          8467  11-26-02 22:30   jwzthreading.py
      --------                   -------
          8467                   1 file
     $ ./python
     Python 2.3 (#1, Aug 1 2003, 19:54:32)
     >>> import sys
     >>> sys.path.insert(0, 'example.zip')  # 將 .zip 檔案新增到系統路徑的最前面
     >>> import jwzthreading
     >>> jwzthreading.__file__
     'example.zip/jwzthreading.py'


File: python.info,  Node: pkgutil --- 套件擴充工具程式,  Next: modulefinder --- 搜尋腳本所使用的模組,  Prev: zipimport --- 從 Zip 封存檔案匯入模組,  Up: 引入模組

5.31.2 ‘pkgutil’ -- 套件擴充工具程式
------------------------------------

'原始碼：'Lib/pkgutil.py(1)

__________________________________________________________________

此模組提供了引入系統 (import system) 的工具程式，特別是套件相關支援。

 -- 類別: pkgutil.ModuleInfo (module_finder, name, ispkg)

     一個包含模組資訊之簡短摘要的附名元組 (namedtuple)。

     在 3.6 版被加入.

 -- 函式: pkgutil.extend_path (path, name)

     擴充組成一個套件之模組的搜尋路徑。預期用法是將以下程式碼放入套件的
     ‘__init__.py’：

          from pkgutil import extend_path
          __path__ = extend_path(__path__, __name__)

     對於 *note sys.path: 37f. 上具有與套件名稱相符的子目錄的每個目錄，
     將該子目錄新增至套件的 *note __path__: 1b72. 中。如果想要將單一邏輯
     套件的不同部分給分配到多個目錄時，這會非常有用。

     它還會尋找 ‘*.pkg’ 檔案，其中開頭的 ‘*’ 與 'name' 引數相符。此功能
     類似於 ‘*.pth’ 檔案（更多資訊請參閱 *note site: b5. 模組），但他不
     特別處理以 ‘import’ 為開頭的行。‘*.pkg’ 檔案從表面上看是受信任的：
     除了跳過空行和備註之外，在 ‘*.pkg’ 檔案中找到的所有條目都將新增到路
     徑中，無論它們是否存在於檔案系統。（這是一個功能。）

     如果輸入路徑不是串列（像是凍結套件 (frozen package) 的情況），它將
     原封不動地被回傳。輸入路徑不會被修改；而是回傳擴充後的副本。僅將項
     目附加到副本的尾端。

     *note sys.path: 37f. 被假設是一個序列，*note sys.path: 37f. 中的項
     目裡，若不是代表現存目錄的字串則將被忽略。*note sys.path: 37f. 上用
     作檔案名稱時導致錯誤的 Unicode 項目可能會導致此函式引發例外（與
     *note os.path.isdir(): 9b4. 行為一致）。

 -- 函式: pkgutil.find_loader (fullname)

     取得給定之 'fullname' 的模組 *note loader: 15a8.。

     這是一個 *note importlib.util.find_spec(): 2af. 的向後相容包裝器，
     它將大多數的失敗轉換為 *note ImportError: 352. 並且僅回傳載入器而不
     是完整的 *note importlib.machinery.ModuleSpec: 1d5a.。

     在 3.3 版的變更: 更新為直接基於 *note importlib: 6b.，而不是依賴套
     件內部 PEP 302(2) 的引入模擬 (import emulation)。

     在 3.4 版的變更: 基於 PEP 451(3) 來更新

     Deprecated since version 3.12, will be removed in version 3.14: 改
     用 *note importlib.util.find_spec(): 2af.。

 -- 函式: pkgutil.get_importer (path_item)

     取得給定之 'path_item' 的 *note finder: 1eca.。

     如果回傳的尋檢器 (finder) 是由路徑勾點 (path hook) 所新建立的，則它
     會被快取在 *note sys.path_importer_cache: 588. 中。

     如果需要重新掃描 *note sys.path_hooks: fc7.，可以手動清除快取（或部
     分快取）。

     在 3.3 版的變更: 更新為直接基於 *note importlib: 6b.，而不是依賴套
     件內部 PEP 302(4) 的引入模擬 (import emulation)。

 -- 函式: pkgutil.get_loader (module_or_name)

     取得 'module_or_name' 的 *note loader: 15a8. 物件。

     如果可以透過正常引入機制存取模組或套件，則回傳該機制相關部分的包裝
     器。如果找不到或無法引入模組，則回傳 ‘None’。如果指定的模組尚未被引
     入，則引入其包含的套件（如有存在）以建立套件 ‘__path__’。

     在 3.3 版的變更: 更新為直接基於 *note importlib: 6b.，而不是依賴套
     件內部 PEP 302(5) 的引入模擬 (import emulation)。

     在 3.4 版的變更: 基於 PEP 451(6) 來更新

     Deprecated since version 3.12, will be removed in version 3.14: 改
     用 *note importlib.util.find_spec(): 2af.。

 -- 函式: pkgutil.iter_importers (fullname='')

     yield 給定模組名稱的 *note finder: 1eca. 物件。

     如果 fullname 包含 ‘'.'’，則尋檢器將針對包含 fullname 的套件，否則
     它們全部會是在頂層被註冊的尋檢器（即 *note sys.meta_path: cd2. 和
     *note sys.path_hooks: fc7. 上的尋檢器）。

     如果指定的模組位於套件中，則作為呼叫此函式的副作用 (side effect) ，
     該套件會被引入。

     如果未指定模組名稱，則會產生所有頂層尋檢器。

     在 3.3 版的變更: 更新為直接基於 *note importlib: 6b.，而不是依賴套
     件內部 PEP 302(7) 的引入模擬 (import emulation)。

 -- 函式: pkgutil.iter_modules (path=None, prefix='')

     yield 'path' 上所有子模組的 *note ModuleInfo: cf2.，或者如果 'path'
     為 ‘None’，則產生 *note sys.path: 37f. 上的所有頂層模組。

     'path' 應該是 ‘None’ 或用來尋找模組的路徑串列。

     'prefix' 是在輸出的每個模組名稱前面的輸出字串。

          備註: 僅適用於有定義 ‘iter_modules()’ 方法的 *note finder:
          1eca.。此介面並非是標準的，因此該模組還提供了 *note
          importlib.machinery.FileFinder: 1013. 和 *note
          zipimport.zipimporter: 42fb. 的實作。

     在 3.3 版的變更: 更新為直接基於 *note importlib: 6b.，而不是依賴套
     件內部 PEP 302(8) 的引入模擬 (import emulation)。

 -- 函式: pkgutil.walk_packages (path=None, prefix='', onerror=None)

     為 'path' 上的所有模組遞迴 yield 出 *note ModuleInfo: cf2.，或如果
     'path' 為 ‘None’ 則 yield 所有可存取的模組。

     'path' 應該是 ‘None’ 或用來尋找模組的路徑串列。

     'prefix' 是在輸出的每個模組名稱前面的輸出字串。

     請注意，此函式必須引入給定之 'path' 上的所有'套件'（'不是'所有模組
     ！），以便存取 ‘__path__’ 屬性來尋找子模組。

     'onerror' 是一個函式，如果在嘗試引入套件時發生任何例外，則使用一個
     引數（正在引入之套件的名稱）來呼叫函式。如果未提供 'onerror' 函式，
     則會捕獲並忽略 *note ImportError: 352.，同時傳播所有其他例外並終止
     搜尋。

     範例：

          # list all modules python can access
          walk_packages()

          # list all submodules of ctypes
          walk_packages(ctypes.__path__, ctypes.__name__ + '.')

          備註: 僅適用於有定義 ‘iter_modules()’ 方法的 *note finder:
          1eca.。此介面並非是標準的，因此該模組還提供了 *note
          importlib.machinery.FileFinder: 1013. 和 *note
          zipimport.zipimporter: 42fb. 的實作。

     在 3.3 版的變更: 更新為直接基於 *note importlib: 6b.，而不是依賴套
     件內部 PEP 302(9) 的引入模擬 (import emulation)。

 -- 函式: pkgutil.get_data (package, resource)

     從套件中取得資源。

     這是 *note loader: 15a8. *note get_data: 4309. API 的包裝器。
     'package' 引數應該是採用標準模組格式 (‘foo.bar’) 的套件名稱。
     'resource' 引數應為相對檔案名稱的形式，並使用 ‘/’ 作為路徑分隔符號
     。不允許使用父目錄名稱 ‘..’，也不允許使用根目錄名稱（以 ‘/’ 開頭）
     。

     該函式回傳一個二進位字串，它是指定資源的內容。

     對於位於檔案系統中且已被引入過的套件，這大致相當於：

          d = os.path.dirname(sys.modules[package].__file__)
          data = open(os.path.join(d, resource), 'rb').read()

     如果無法定位或載入套件，或者它使用不支援 *note get_data: 4309. 的
     *note loader: 15a8. 則回傳 ‘None’。特別是*note 命名空間套件: 1b6c.的
     *note loader: 15a8. 不支援 *note get_data: 4309.。

 -- 函式: pkgutil.resolve_name (name)

     將名稱解析為物件。

     標準函式庫中的許多地方都使用了此功能（請參閱 bpo-12915(10)），且相
     同功能也被用於擁有廣大使用者的第三方套件，如 setuptools、Django 和
     Pyramid。

     'name' 預期要是以下格式之一的字串，其中 W 是有效 Python 識別字的簡
     寫，而點 (dot) 代表這些偽正規表示式 (pseudo-regex) 中的字面句點
     (literal period)：

        * ‘W(.W)*’

        * ‘W(.W)*:(W(.W)*)?’

     第一種形式僅是為了要向後相容。它假設點名稱 (dotted name) 的某些部分
     是一個套件，其餘部分是該套件內某處的物件，其可能巢狀地存在於
     (nested) 其他物件內。由於無法透過檢查 (inspection) 來推斷出套件停止
     的位置和物件層次結構的開始位置，因此必須使用此形式來重複嘗試引入。

     在第二種形式中，呼叫者透過使用一個冒號來明確標明分隔點：冒號左側的
     點名稱是要引入的套件，右側的點名稱是該套件內的物件層次結構。這種形
     式只需要一次引入。如果它以冒號結尾，則回傳一個模組物件。

     此函式會回傳一個物件（可能是一個模組），或引發以下其中一個例外：

     *note ValueError: 1e7. - 如果 'name' 不是可辨識的格式。

     *note ImportError: 352. - 如果在不應該失敗的情況下引入失敗。

     *note AttributeError: 2f6. - 如果在遍歷引入套件中的物件層次結構以取
     得所需物件時發生失敗。

     在 3.9 版被加入.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/pkgutil.py

   (2) https://peps.python.org/pep-0302/

   (3) https://peps.python.org/pep-0451/

   (4) https://peps.python.org/pep-0302/

   (5) https://peps.python.org/pep-0302/

   (6) https://peps.python.org/pep-0451/

   (7) https://peps.python.org/pep-0302/

   (8) https://peps.python.org/pep-0302/

   (9) https://peps.python.org/pep-0302/

   (10) https://bugs.python.org/issue?@action=redirect&bpo=12915


File: python.info,  Node: modulefinder --- 搜尋腳本所使用的模組,  Next: runpy --- 定位並執行 Python 模組,  Prev: pkgutil --- 套件擴充工具程式,  Up: 引入模組

5.31.3 ‘modulefinder’ -- 搜尋腳本所使用的模組
---------------------------------------------

'原始碼：'Lib/modulefinder.py(1)

__________________________________________________________________

此模組提供了一個 *note ModuleFinder: 1909. 類別，可用於確定腳本引入的模
組集合。‘modulefinder.py’ 也可以作為腳本運行，其將 Python 腳本的檔案名稱
作為它的引數，並在之後會列印出引入模組的報告。

 -- 函式: modulefinder.AddPackagePath (pkg_name, path)

     記錄在指定的 'path' 中可以找到名為 'pkg_name' 的套件。

 -- 函式: modulefinder.ReplacePackage (oldname, newname)

     允許指定名為 'oldname' 的模組實際上是名為 'newname' 的套件。

 -- 類別: modulefinder.ModuleFinder (path=None, debug=0, excludes=[],
          replace_paths=[])

     此類別提供 *note run_script(): 430f. 和 *note report(): 4310. 方法
     來決定腳本引入的模組集合。'path' 可以是搜尋模組的目錄串列；如果未指
     定，則使用 ‘sys.path’。'debug' 設定偵錯等級；較高的值可使類別列印有
     關其即將執行之操作的偵錯訊息。'excludes' 是要從分析中排除的模組名稱
     串列。'replace_paths' 是將在模組路徑中替換的 ‘(oldpath, newpath)’ 元
     組串列。

      -- 方法: report ()

          將報告列印到標準輸出，其中列出了腳本引入的模組及其路徑，以及丟
          失或似乎丟失的模組。

      -- 方法: run_script (pathname)

          分析 'pathname' 檔案的內容，該檔案必須包含 Python 程式碼。

      -- 屬性: modules

          將模組名稱對應到模組的字典。請參閱 *note ModuleFinder
          的用法範例: 4312.。

* Menu:

* ModuleFinder 的用法範例::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/modulefinder.py


File: python.info,  Node: ModuleFinder 的用法範例,  Up: modulefinder --- 搜尋腳本所使用的模組

5.31.3.1 ‘ModuleFinder’ 的用法範例
..................................

將被分析的腳本 (bacon.py)：

     import re, itertools

     try:
         import baconhameggs
     except ImportError:
         pass

     try:
         import guido.python.ham
     except ImportError:
         pass

將輸出 bacon.py 報告的腳本：

     from modulefinder import ModuleFinder

     finder = ModuleFinder()
     finder.run_script('bacon.py')

     print('Loaded modules:')
     for name, mod in finder.modules.items():
         print('%s: ' % name, end='')
         print(','.join(list(mod.globalnames.keys())[:3]))

     print('-'*50)
     print('Modules not imported:')
     print('\n'.join(finder.badmodules.keys()))

範例輸出（可能因架構而異）：

     Loaded modules:
     _types:
     copyreg:  _inverted_registry,_slotnames,__all__
     re._compiler:  isstring,_sre,_optimize_unicode
     _sre:
     re._constants:  REPEAT_ONE,makedict,AT_END_LINE
     sys:
     re:  __module__,finditer,_expand
     itertools:
     __main__:  re,itertools,baconhameggs
     re._parser:  _PATTERNENDERS,SRE_FLAG_UNICODE
     array:
     types:  __module__,IntType,TypeType
     ---------------------------------------------------
     Modules not imported:
     guido.python.ham
     baconhameggs


File: python.info,  Node: runpy --- 定位並執行 Python 模組,  Next: importlib --- import 的實作,  Prev: modulefinder --- 搜尋腳本所使用的模組,  Up: 引入模組

5.31.4 ‘runpy’ -- 定位並執行 Python 模組
----------------------------------------

'原始碼：'Lib/runpy.py(1)

__________________________________________________________________

The *note runpy: ac. module is used to locate and run Python modules
without importing them first.  Its main use is to implement the *note
-m: 585. command line switch that allows scripts to be located using the
Python module namespace rather than the filesystem.

Note that this is 'not' a sandbox module - all code is executed in the
current process, and any side effects (such as cached imports of other
modules) will remain in place after the functions have returned.

Furthermore, any functions and classes defined by the executed code are
not guaranteed to work correctly after a *note runpy: ac. function has
returned.  If that limitation is not acceptable for a given use case,
*note importlib: 6b. is likely to be a more suitable choice than this
module.

The *note runpy: ac. module provides two functions:

 -- 函式: runpy.run_module (mod_name, init_globals=None, run_name=None,
          alter_sys=False)

     Execute the code of the specified module and return the resulting
     module's globals dictionary.  The module's code is first located
     using the standard import mechanism (refer to PEP 302(2) for
     details) and then executed in a fresh module namespace.

     The 'mod_name' argument should be an absolute module name.  If the
     module name refers to a package rather than a normal module, then
     that package is imported and the *note __main__: 1. submodule
     within that package is then executed and the resulting module
     globals dictionary returned.

     The optional dictionary argument 'init_globals' may be used to
     pre-populate the module's globals dictionary before the code is
     executed.  'init_globals' will not be modified.  If any of the
     special global variables below are defined in 'init_globals', those
     definitions are overridden by *note run_module(): 1711.

     The special global variables ‘__name__’, ‘__spec__’, ‘__file__’,
     ‘__cached__’, ‘__loader__’ and ‘__package__’ are set in the globals
     dictionary before the module code is executed.  (Note that this is
     a minimal set of variables - other variables may be set implicitly
     as an interpreter implementation detail.)

     ‘__name__’ is set to 'run_name' if this optional argument is not
     *note None: 61b, to ‘mod_name + '.__main__'’ if the named module is
     a package and to the 'mod_name' argument otherwise.

     ‘__spec__’ will be set appropriately for the 'actually' imported
     module (that is, ‘__spec__.name’ will always be 'mod_name' or
     ‘mod_name + '.__main__'’, never 'run_name').

     ‘__file__’, ‘__cached__’, ‘__loader__’ and ‘__package__’ are *note
     set as normal: 1ed1. based on the module spec.

     If the argument 'alter_sys' is supplied and evaluates to *note
     True: bb4, then ‘sys.argv[0]’ is updated with the value of
     ‘__file__’ and ‘sys.modules[__name__]’ is updated with a temporary
     module object for the module being executed.  Both ‘sys.argv[0]’
     and ‘sys.modules[__name__]’ are restored to their original values
     before the function returns.

     Note that this manipulation of *note sys: c3. is not thread-safe.
     Other threads may see the partially initialised module, as well as
     the altered list of arguments.  It is recommended that the ‘sys’
     module be left alone when invoking this function from threaded
     code.

     也參考
     ......

     The *note -m: 585. option offering equivalent functionality from
     the command line.

     在 3.1 版的變更: Added ability to execute packages by looking for a
     *note __main__: 1. submodule.

     在 3.2 版的變更: Added ‘__cached__’ global variable (see PEP
     3147(3)).

     在 3.4 版的變更: Updated to take advantage of the module spec
     feature added by PEP 451(4).  This allows ‘__cached__’ to be set
     correctly for modules run this way, as well as ensuring the real
     module name is always accessible as ‘__spec__.name’.

     在 3.12 版的變更: The setting of ‘__cached__’, ‘__loader__’, and
     ‘__package__’ are deprecated.  See *note ModuleSpec: 1d5a. for
     alternatives.

 -- 函式: runpy.run_path (path_name, init_globals=None, run_name=None)

     Execute the code at the named filesystem location and return the
     resulting module's globals dictionary.  As with a script name
     supplied to the CPython command line, 'file_path' may refer to a
     Python source file, a compiled bytecode file or a valid *note
     sys.path: 37f. entry containing a *note __main__: 1. module (e.g.
     a zipfile containing a top-level ‘__main__.py’ file).

     For a simple script, the specified code is simply executed in a
     fresh module namespace.  For a valid *note sys.path: 37f. entry
     (typically a zipfile or directory), the entry is first added to the
     beginning of ‘sys.path’.  The function then looks for and executes
     a *note __main__: 1. module using the updated path.  Note that
     there is no special protection against invoking an existing
     ‘__main__’ entry located elsewhere on ‘sys.path’ if there is no
     such module at the specified location.

     The optional dictionary argument 'init_globals' may be used to
     pre-populate the module's globals dictionary before the code is
     executed.  'init_globals' will not be modified.  If any of the
     special global variables below are defined in 'init_globals', those
     definitions are overridden by *note run_path(): 164.

     The special global variables ‘__name__’, ‘__spec__’, ‘__file__’,
     ‘__cached__’, ‘__loader__’ and ‘__package__’ are set in the globals
     dictionary before the module code is executed.  (Note that this is
     a minimal set of variables - other variables may be set implicitly
     as an interpreter implementation detail.)

     ‘__name__’ is set to 'run_name' if this optional argument is not
     *note None: 61b. and to ‘'<run_path>'’ otherwise.

     If 'file_path' directly references a script file (whether as source
     or as precompiled byte code), then ‘__file__’ will be set to
     'file_path', and ‘__spec__’, ‘__cached__’, ‘__loader__’ and
     ‘__package__’ will all be set to *note None: 61b.

     If 'file_path' is a reference to a valid *note sys.path: 37f.
     entry, then ‘__spec__’ will be set appropriately for the imported
     *note __main__: 1. module (that is, ‘__spec__.name’ will always be
     ‘__main__’).  ‘__file__’, ‘__cached__’, ‘__loader__’ and
     ‘__package__’ will be *note set as normal: 1ed1. based on the
     module spec.

     A number of alterations are also made to the *note sys: c3. module.
     Firstly, *note sys.path: 37f. may be altered as described above.
     ‘sys.argv[0]’ is updated with the value of 'file_path' and
     ‘sys.modules[__name__]’ is updated with a temporary module object
     for the module being executed.  All modifications to items in *note
     sys: c3. are reverted before the function returns.

     Note that, unlike *note run_module(): 1711, the alterations made to
     *note sys: c3. are not optional in this function as these
     adjustments are essential to allowing the execution of *note
     sys.path: 37f. entries.  As the thread-safety limitations still
     apply, use of this function in threaded code should be either
     serialised with the import lock or delegated to a separate process.

     也參考
     ......

     *note 介面選項: 1c2b. for equivalent functionality on the command
     line (‘python path/to/script’).

     在 3.2 版被加入.

     在 3.4 版的變更: Updated to take advantage of the module spec
     feature added by PEP 451(5).  This allows ‘__cached__’ to be set
     correctly in the case where ‘__main__’ is imported from a valid
     *note sys.path: 37f. entry rather than being executed directly.

     在 3.12 版的變更: The setting of ‘__cached__’, ‘__loader__’, and
     ‘__package__’ are deprecated.

也參考
......

PEP 338(6) - Executing modules as scripts

     PEP written and implemented by Nick Coghlan.

PEP 366(7) - Main module explicit relative imports

     PEP written and implemented by Nick Coghlan.

PEP 451(8) - A ModuleSpec Type for the Import System

     PEP written and implemented by Eric Snow

*note 命令列與環境: 18c4. - CPython command line details

The *note importlib.import_module(): 4bc. function

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/runpy.py

   (2) https://peps.python.org/pep-0302/

   (3) https://peps.python.org/pep-3147/

   (4) https://peps.python.org/pep-0451/

   (5) https://peps.python.org/pep-0451/

   (6) https://peps.python.org/pep-0338/

   (7) https://peps.python.org/pep-0366/

   (8) https://peps.python.org/pep-0451/


File: python.info,  Node: importlib --- import 的實作,  Next: importlib resources -- Package resource reading opening and access,  Prev: runpy --- 定位並執行 Python 模組,  Up: 引入模組

5.31.5 ‘importlib’ -- ‘import’ 的實作
-------------------------------------

在 3.1 版被加入.

'原始碼：'Lib/importlib/__init__.py(1)

__________________________________________________________________

* Menu:

* 簡介: 簡介<9>.
* 函式: 函式<11>.
* importlib.abc: importlib abc -- Abstract base classes related to import. Abstract base classes related to import
* importlib.machinery: importlib machinery -- Importers and path hooks. Importers and path hooks
* importlib.util: importlib util -- Utility code for importers. Utility code for importers
* 範例: 範例<46>.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/importlib/__init__.py


File: python.info,  Node: 簡介<9>,  Next: 函式<11>,  Up: importlib --- import 的實作

5.31.5.1 簡介
.............

The purpose of the *note importlib: 6b. package is three-fold.

One is to provide the implementation of the *note import: 586. statement
(and thus, by extension, the *note __import__(): 879. function) in
Python source code.  This provides an implementation of ‘import’ which
is portable to any Python interpreter.  This also provides an
implementation which is easier to comprehend than one implemented in a
programming language other than Python.

Two, the components to implement *note import: 586. are exposed in this
package, making it easier for users to create their own custom objects
(known generically as an *note importer: 1ecb.) to participate in the
import process.

Three, the package contains modules exposing additional functionality
for managing aspects of Python packages:

   * *note importlib.metadata: 6e. presents access to metadata from
     third-party distributions.

   * *note importlib.resources: 6f. provides routines for accessing
     non-code "resources" from Python packages.

也參考
......

*note import 陳述式: 586.

     The language reference for the *note import: 586. statement.

Packages specification(1)

     Original specification of packages.  Some semantics have changed
     since the writing of this document (e.g.  redirecting based on
     ‘None’ in *note sys.modules: 186e.).

*note __import__(): 100e. 函式

     The *note import: 586. statement is syntactic sugar for this
     function.

*note The initialization of the sys.path module search path: 1b64.

     The initialization of *note sys.path: 37f.

PEP 235(2)

     Import on Case-Insensitive Platforms

PEP 263(3)

     Defining Python Source Code Encodings

PEP 302(4)

     New Import Hooks

PEP 328(5)

     Imports: Multi-Line and Absolute/Relative

PEP 366(6)

     Main module explicit relative imports

PEP 420(7)

     Implicit namespace packages

PEP 451(8)

     A ModuleSpec Type for the Import System

PEP 488(9)

     Elimination of PYO files

PEP 489(10)

     Multi-phase extension module initialization

PEP 552(11)

     Deterministic pycs

PEP 3120(12)

     Using UTF-8 as the Default Source Encoding

PEP 3147(13)

     PYC Repository Directories

   ---------- Footnotes ----------

   (1) https://www.python.org/doc/essays/packages/

   (2) https://peps.python.org/pep-0235/

   (3) https://peps.python.org/pep-0263/

   (4) https://peps.python.org/pep-0302/

   (5) https://peps.python.org/pep-0328/

   (6) https://peps.python.org/pep-0366/

   (7) https://peps.python.org/pep-0420/

   (8) https://peps.python.org/pep-0451/

   (9) https://peps.python.org/pep-0488/

   (10) https://peps.python.org/pep-0489/

   (11) https://peps.python.org/pep-0552/

   (12) https://peps.python.org/pep-3120/

   (13) https://peps.python.org/pep-3147/


File: python.info,  Node: 函式<11>,  Next: importlib abc -- Abstract base classes related to import,  Prev: 簡介<9>,  Up: importlib --- import 的實作

5.31.5.2 函式
.............

 -- 函式: importlib.__import__ (name, globals=None, locals=None,
          fromlist=(), level=0)

     An implementation of the built-in *note __import__(): 879.
     function.

          備註: Programmatic importing of modules should use *note
          import_module(): 4bc. instead of this function.

 -- 函式: importlib.import_module (name, package=None)

     Import a module.  The 'name' argument specifies what module to
     import in absolute or relative terms (e.g.  either ‘pkg.mod’ or
     ‘..mod’).  If the name is specified in relative terms, then the
     'package' argument must be set to the name of the package which is
     to act as the anchor for resolving the package name (e.g.
     ‘import_module('..mod', 'pkg.subpkg')’ will import ‘pkg.mod’).

     The *note import_module(): 4bc. function acts as a simplifying
     wrapper around *note importlib.__import__(): 100e.  This means all
     semantics of the function are derived from *note
     importlib.__import__(): 100e.  The most important difference
     between these two functions is that *note import_module(): 4bc.
     returns the specified package or module (e.g.  ‘pkg.mod’), while
     *note __import__(): 879. returns the top-level package or module
     (e.g.  ‘pkg’).

     If you are dynamically importing a module that was created since
     the interpreter began execution (e.g., created a Python source
     file), you may need to call *note invalidate_caches(): bb7. in
     order for the new module to be noticed by the import system.

     在 3.3 版的變更: Parent packages are automatically imported.

 -- 函式: importlib.invalidate_caches ()

     Invalidate the internal caches of finders stored at *note
     sys.meta_path: cd2.  If a finder implements ‘invalidate_caches()’
     then it will be called to perform the invalidation.  This function
     should be called if any modules are created/installed while your
     program is running to guarantee all finders will notice the new
     module's existence.

     在 3.3 版被加入.

     在 3.10 版的變更: Namespace packages created/installed in a
     different *note sys.path: 37f. location after the same namespace
     was already imported are noticed.

 -- 函式: importlib.reload (module)

     Reload a previously imported 'module'.  The argument must be a
     module object, so it must have been successfully imported before.
     This is useful if you have edited the module source file using an
     external editor and want to try out the new version without leaving
     the Python interpreter.  The return value is the module object
     (which can be different if re-importing causes a different object
     to be placed in *note sys.modules: 186e.).

     When *note reload(): 4bd. is executed:

        * Python module's code is recompiled and the module-level code
          re-executed, defining a new set of objects which are bound to
          names in the module's dictionary by reusing the *note loader:
          15a8. which originally loaded the module.  The ‘init’ function
          of extension modules is not called a second time.

        * As with all other objects in Python the old objects are only
          reclaimed after their reference counts drop to zero.

        * The names in the module namespace are updated to point to any
          new or changed objects.

        * Other references to the old objects (such as names external to
          the module) are not rebound to refer to the new objects and
          must be updated in each namespace where they occur if that is
          desired.

     There are a number of other caveats:

     When a module is reloaded, its dictionary (containing the module's
     global variables) is retained.  Redefinitions of names will
     override the old definitions, so this is generally not a problem.
     If the new version of a module does not define a name that was
     defined by the old version, the old definition remains.  This
     feature can be used to the module's advantage if it maintains a
     global table or cache of objects -- with a *note try: 68c.
     statement it can test for the table's presence and skip its
     initialization if desired:

          try:
              cache
          except NameError:
              cache = {}

     It is generally not very useful to reload built-in or dynamically
     loaded modules.  Reloading *note sys: c3, *note __main__: 1, *note
     builtins: e. and other key modules is not recommended.  In many
     cases extension modules are not designed to be initialized more
     than once, and may fail in arbitrary ways when reloaded.

     If a module imports objects from another module using *note from:
     1242. ...  *note import: 586. ..., calling *note reload(): 4bd. for
     the other module does not redefine the objects imported from it --
     one way around this is to re-execute the ‘from’ statement, another
     is to use ‘import’ and qualified names ('module.name') instead.

     If a module instantiates instances of a class, reloading the module
     that defines the class does not affect the method definitions of
     the instances -- they continue to use the old class definition.
     The same is true for derived classes.

     在 3.4 版被加入.

     在 3.7 版的變更: *note ModuleNotFoundError: aeb. is raised when the
     module being reloaded lacks a *note ModuleSpec: 1d5a.


File: python.info,  Node: importlib abc -- Abstract base classes related to import,  Next: importlib machinery -- Importers and path hooks,  Prev: 函式<11>,  Up: importlib --- import 的實作

5.31.5.3 ‘importlib.abc’ - Abstract base classes related to import
..................................................................

'原始碼：'Lib/importlib/abc.py(1)

__________________________________________________________________

The *note importlib.abc: 6c. module contains all of the core abstract
base classes used by *note import: 586.  Some subclasses of the core
abstract base classes are also provided to help in implementing the core
ABCs.

ABC hierarchy:

     object
      +-- MetaPathFinder
      +-- PathEntryFinder
      +-- Loader
           +-- ResourceLoader --------+
           +-- InspectLoader          |
                +-- ExecutionLoader --+
                                      +-- FileLoader
                                      +-- SourceLoader

 -- 類別: importlib.abc.MetaPathFinder

     An abstract base class representing a *note meta path finder: 1011.

     在 3.3 版被加入.

     在 3.10 版的變更: No longer a subclass of ‘Finder’.

      -- 方法: find_spec (fullname, path, target=None)

          An abstract method for finding a *note spec: 419f. for the
          specified module.  If this is a top-level import, 'path' will
          be ‘None’.  Otherwise, this is a search for a subpackage or
          module and 'path' will be the value of *note __path__: 1b72.
          from the parent package.  If a spec cannot be found, ‘None’ is
          returned.  When passed in, ‘target’ is a module object that
          the finder may use to make a more educated guess about what
          spec to return.  *note importlib.util.spec_from_loader(): 812.
          may be useful for implementing concrete ‘MetaPathFinders’.

          在 3.4 版被加入.

      -- 方法: invalidate_caches ()

          An optional method which, when called, should invalidate any
          internal cache used by the finder.  Used by *note
          importlib.invalidate_caches(): bb7. when invalidating the
          caches of all finders on *note sys.meta_path: cd2.

          在 3.4 版的變更: Returns ‘None’ when called instead of *note
          NotImplemented: 776.

 -- 類別: importlib.abc.PathEntryFinder

     An abstract base class representing a *note path entry finder:
     1012.  Though it bears some similarities to *note MetaPathFinder:
     813, ‘PathEntryFinder’ is meant for use only within the path-based
     import subsystem provided by *note importlib.machinery.PathFinder:
     fc6.

     在 3.3 版被加入.

     在 3.10 版的變更: No longer a subclass of ‘Finder’.

      -- 方法: find_spec (fullname, target=None)

          An abstract method for finding a *note spec: 419f. for the
          specified module.  The finder will search for the module only
          within the *note path entry: 1edf. to which it is assigned.
          If a spec cannot be found, ‘None’ is returned.  When passed
          in, ‘target’ is a module object that the finder may use to
          make a more educated guess about what spec to return.  *note
          importlib.util.spec_from_loader(): 812. may be useful for
          implementing concrete ‘PathEntryFinders’.

          在 3.4 版被加入.

      -- 方法: invalidate_caches ()

          An optional method which, when called, should invalidate any
          internal cache used by the finder.  Used by *note
          importlib.machinery.PathFinder.invalidate_caches(): bb6. when
          invalidating the caches of all cached finders.

 -- 類別: importlib.abc.Loader

     An abstract base class for a *note loader: 15a8.  See PEP 302(2)
     for the exact definition for a loader.

     Loaders that wish to support resource reading should implement a
     ‘get_resource_reader()’ method as specified by *note
     importlib.resources.abc.ResourceReader: 431d.

     在 3.7 版的變更: Introduced the optional ‘get_resource_reader()’
     method.

      -- 方法: create_module (spec)

          A method that returns the module object to use when importing
          a module.  This method may return ‘None’, indicating that
          default module creation semantics should take place.

          在 3.4 版被加入.

          在 3.6 版的變更: This method is no longer optional when *note
          exec_module(): 80f. is defined.

      -- 方法: exec_module (module)

          An abstract method that executes the module in its own
          namespace when a module is imported or reloaded.  The module
          should already be initialized when *note exec_module(): 80f.
          is called.  When this method exists, *note create_module():
          c55. must be defined.

          在 3.4 版被加入.

          在 3.6 版的變更: *note create_module(): c55. 也必須被定義。

      -- 方法: load_module (fullname)

          A legacy method for loading a module.  If the module cannot be
          loaded, *note ImportError: 352. is raised, otherwise the
          loaded module is returned.

          If the requested module already exists in *note sys.modules:
          186e, that module should be used and reloaded.  Otherwise the
          loader should create a new module and insert it into *note
          sys.modules: 186e. before any loading begins, to prevent
          recursion from the import.  If the loader inserted a module
          and the load fails, it must be removed by the loader from
          *note sys.modules: 186e.; modules already in *note
          sys.modules: 186e. before the loader began execution should be
          left alone.

          The loader should set several attributes on the module (note
          that some of these attributes can change when a module is
          reloaded):

             - 
               *note __name__: 1316.

                    The module's fully qualified name.  It is
                    ‘'__main__'’ for an executed module.

             - 
               *note __file__: 1e02.

                    The location the *note loader: 15a8. used to load
                    the module.  For example, for modules loaded from a
                    .py file this is the filename.  It is not set on all
                    modules (e.g.  built-in modules).

             - 
               *note __cached__: 114d.

                    The filename of a compiled version of the module's
                    code.  It is not set on all modules (e.g.  built-in
                    modules).

             - 
               *note __path__: 1b72.

                    The list of locations where the package's submodules
                    will be found.  Most of the time this is a single
                    directory.  The import system passes this attribute
                    to ‘__import__()’ and to finders in the same way as
                    *note sys.path: 37f. but just for the package.  It
                    is not set on non-package modules so it can be used
                    as an indicator that the module is a package.

             - 
               *note __package__: fc0.

                    The fully qualified name of the package the module
                    is in (or the empty string for a top-level module).
                    If the module is a package then this is the same as
                    *note __name__: 1316.

             - 
               *note __loader__: fc1.

                    The *note loader: 15a8. used to load the module.

          When *note exec_module(): 80f. is available then
          backwards-compatible functionality is provided.

          在 3.4 版的變更: Raise *note ImportError: 352. when called
          instead of *note NotImplementedError: 20d.  Functionality
          provided when *note exec_module(): 80f. is available.

          在 3.4 版之後被棄用: The recommended API for loading a module
          is *note exec_module(): 80f. (and *note create_module():
          c55.).  Loaders should implement it instead of *note
          load_module(): 80e.  The import machinery takes care of all
          the other responsibilities of *note load_module(): 80e. when
          *note exec_module(): 80f. is implemented.

 -- 類別: importlib.abc.ResourceLoader

     An abstract base class for a *note loader: 15a8. which implements
     the optional PEP 302(3) protocol for loading arbitrary resources
     from the storage back-end.

     在 3.7 版之後被棄用: This ABC is deprecated in favour of supporting
     resource loading through *note
     importlib.resources.abc.ResourceReader: 431d.

      -- 方法: abstractmethod get_data (path)

          An abstract method to return the bytes for the data located at
          'path'.  Loaders that have a file-like storage back-end that
          allows storing arbitrary data can implement this abstract
          method to give direct access to the data stored.  *note
          OSError: 350. is to be raised if the 'path' cannot be found.
          The 'path' is expected to be constructed using a module's
          *note __file__: 1e02. attribute or an item from a package's
          *note __path__: 1b72.

          在 3.4 版的變更: Raises *note OSError: 350. instead of *note
          NotImplementedError: 20d.

 -- 類別: importlib.abc.InspectLoader

     An abstract base class for a *note loader: 15a8. which implements
     the optional PEP 302(4) protocol for loaders that inspect modules.

      -- 方法: get_code (fullname)

          Return the code object for a module, or ‘None’ if the module
          does not have a code object (as would be the case, for
          example, for a built-in module).  Raise an *note ImportError:
          352. if loader cannot find the requested module.

               備註: While the method has a default implementation, it
               is suggested that it be overridden if possible for
               performance.

          在 3.4 版的變更: No longer abstract and a concrete
          implementation is provided.

      -- 方法: abstractmethod get_source (fullname)

          An abstract method to return the source of a module.  It is
          returned as a text string using *note universal newlines: ce1,
          translating all recognized line separators into ‘'\n'’
          characters.  Returns ‘None’ if no source is available (e.g.  a
          built-in module).  Raises *note ImportError: 352. if the
          loader cannot find the module specified.

          在 3.4 版的變更: Raises *note ImportError: 352. instead of
          *note NotImplementedError: 20d.

      -- 方法: is_package (fullname)

          An optional method to return a true value if the module is a
          package, a false value otherwise.  *note ImportError: 352. is
          raised if the *note loader: 15a8. cannot find the module.

          在 3.4 版的變更: Raises *note ImportError: 352. instead of
          *note NotImplementedError: 20d.

      -- 方法: static source_to_code (data, path='<string>')

          Create a code object from Python source.

          The 'data' argument can be whatever the *note compile(): 178.
          function supports (i.e.  string or bytes).  The 'path'
          argument should be the "path" to where the source code
          originated from, which can be an abstract concept (e.g.
          location in a zip file).

          With the subsequent code object one can execute it in a module
          by running ‘exec(code, module.__dict__)’.

          在 3.4 版被加入.

          在 3.5 版的變更: Made the method static.

      -- 方法: exec_module (module)

          *note Loader.exec_module(): 80f. 的實作。

          在 3.4 版被加入.

      -- 方法: load_module (fullname)

          *note Loader.load_module(): 80e. 的實作。

          在 3.4 版之後被棄用: 請改用 *note exec_module(): fb3.。

 -- 類別: importlib.abc.ExecutionLoader

     An abstract base class which inherits from *note InspectLoader:
     ef7. that, when implemented, helps a module to be executed as a
     script.  The ABC represents an optional PEP 302(5) protocol.

      -- 方法: abstractmethod get_filename (fullname)

          An abstract method that is to return the value of *note
          __file__: 1e02. for the specified module.  If no path is
          available, *note ImportError: 352. is raised.

          If source code is available, then the method should return the
          path to the source file, regardless of whether a bytecode was
          used to load the module.

          在 3.4 版的變更: Raises *note ImportError: 352. instead of
          *note NotImplementedError: 20d.

 -- 類別: importlib.abc.FileLoader (fullname, path)

     An abstract base class which inherits from *note ResourceLoader:
     b8e. and *note ExecutionLoader: 4320, providing concrete
     implementations of *note ResourceLoader.get_data(): 4309. and *note
     ExecutionLoader.get_filename(): 4321.

     The 'fullname' argument is a fully resolved name of the module the
     loader is to handle.  The 'path' argument is the path to the file
     for the module.

     在 3.3 版被加入.

      -- 屬性: name

          The name of the module the loader can handle.

      -- 屬性: path

          Path to the file of the module.

      -- 方法: load_module (fullname)

          Calls super's ‘load_module()’.

          在 3.4 版之後被棄用: Use *note Loader.exec_module(): 80f.
          instead.

      -- 方法: abstractmethod get_filename (fullname)

          Returns *note path: 4323.

      -- 方法: abstractmethod get_data (path)

          Reads 'path' as a binary file and returns the bytes from it.

 -- 類別: importlib.abc.SourceLoader

     An abstract base class for implementing source (and optionally
     bytecode) file loading.  The class inherits from both *note
     ResourceLoader: b8e. and *note ExecutionLoader: 4320, requiring the
     implementation of:

        * *note ResourceLoader.get_data(): 4309.

        * 
          *note ExecutionLoader.get_filename(): 4321.

               Should only return the path to the source file;
               sourceless loading is not supported.

     The abstract methods defined by this class are to add optional
     bytecode file support.  Not implementing these optional methods (or
     causing them to raise *note NotImplementedError: 20d.) causes the
     loader to only work with source code.  Implementing the methods
     allows the loader to work with source 'and' bytecode files; it does
     not allow for 'sourceless' loading where only bytecode is provided.
     Bytecode files are an optimization to speed up loading by removing
     the parsing step of Python's compiler, and so no bytecode-specific
     API is exposed.

      -- 方法: path_stats (path)

          Optional abstract method which returns a *note dict: 23b.
          containing metadata about the specified path.  Supported
          dictionary keys are:

             - ‘'mtime'’ (mandatory): an integer or floating-point
               number representing the modification time of the source
               code;

             - ‘'size'’ (optional): the size in bytes of the source
               code.

          Any other keys in the dictionary are ignored, to allow for
          future extensions.  If the path cannot be handled, *note
          OSError: 350. is raised.

          在 3.3 版被加入.

          在 3.4 版的變更: Raise *note OSError: 350. instead of *note
          NotImplementedError: 20d.

      -- 方法: path_mtime (path)

          Optional abstract method which returns the modification time
          for the specified path.

          在 3.3 版之後被棄用: This method is deprecated in favour of
          *note path_stats(): 1124.  You don't have to implement it, but
          it is still available for compatibility purposes.  Raise *note
          OSError: 350. if the path cannot be handled.

          在 3.4 版的變更: Raise *note OSError: 350. instead of *note
          NotImplementedError: 20d.

      -- 方法: set_data (path, data)

          Optional abstract method which writes the specified bytes to a
          file path.  Any intermediate directories which do not exist
          are to be created automatically.

          When writing to the path fails because the path is read-only
          (*note errno.EACCES: 218b./*note PermissionError: ce9.), do
          not propagate the exception.

          在 3.4 版的變更: No longer raises *note NotImplementedError:
          20d. when called.

      -- 方法: get_code (fullname)

          Concrete implementation of *note InspectLoader.get_code():
          ef8.

      -- 方法: exec_module (module)

          Concrete implementation of *note Loader.exec_module(): 80f.

          在 3.4 版被加入.

      -- 方法: load_module (fullname)

          Concrete implementation of *note Loader.load_module(): 80e.

          在 3.4 版之後被棄用: Use *note exec_module(): fb4. instead.

      -- 方法: get_source (fullname)

          Concrete implementation of *note InspectLoader.get_source():
          efb.

      -- 方法: is_package (fullname)

          Concrete implementation of *note InspectLoader.is_package():
          431e.  A module is determined to be a package if its file path
          (as provided by *note ExecutionLoader.get_filename(): 4321.)
          is a file named ‘__init__’ when the file extension is removed
          'and' the module name itself does not end in ‘__init__’.

 -- 類別: importlib.abc.ResourceReader

     'Superseded by TraversableResources'

     An *note abstract base class: 114e. to provide the ability to read
     'resources'.

     From the perspective of this ABC, a 'resource' is a binary artifact
     that is shipped within a package.  Typically this is something like
     a data file that lives next to the ‘__init__.py’ file of the
     package.  The purpose of this class is to help abstract out the
     accessing of such data files so that it does not matter if the
     package and its data file(s) are stored e.g.  in a zip file versus
     on the file system.

     For any of methods of this class, a 'resource' argument is expected
     to be a *note path-like object: ac2. which represents conceptually
     just a file name.  This means that no subdirectory paths should be
     included in the 'resource' argument.  This is because the location
     of the package the reader is for, acts as the "directory".  Hence
     the metaphor for directories and file names is packages and
     resources, respectively.  This is also why instances of this class
     are expected to directly correlate to a specific package (instead
     of potentially representing multiple packages or a module).

     Loaders that wish to support resource reading are expected to
     provide a method called ‘get_resource_reader(fullname)’ which
     returns an object implementing this ABC's interface.  If the module
     specified by fullname is not a package, this method should return
     *note None: 61b.  An object compatible with this ABC should only be
     returned when the specified module is a package.

     在 3.7 版被加入.

     Deprecated since version 3.12, will be removed in version 3.14: Use
     *note importlib.resources.abc.TraversableResources: 2a7. instead.

      -- 方法: abstractmethod open_resource (resource)

          Returns an opened, *note file-like object: 246a. for binary
          reading of the 'resource'.

          If the resource cannot be found, *note FileNotFoundError: e67.
          is raised.

      -- 方法: abstractmethod resource_path (resource)

          Returns the file system path to the 'resource'.

          If the resource does not concretely exist on the file system,
          raise *note FileNotFoundError: e67.

      -- 方法: abstractmethod is_resource (name)

          Returns ‘True’ if the named 'name' is considered a resource.
          *note FileNotFoundError: e67. is raised if 'name' does not
          exist.

      -- 方法: abstractmethod contents ()

          Returns an *note iterable: 11bf. of strings over the contents
          of the package.  Do note that it is not required that all
          names returned by the iterator be actual resources, e.g.  it
          is acceptable to return names for which *note is_resource():
          432e. would be false.

          Allowing non-resource names to be returned is to allow for
          situations where how a package and its resources are stored
          are known a priori and the non-resource names would be useful.
          For instance, returning subdirectory names is allowed so that
          when it is known that the package and resources are stored on
          the file system then those subdirectory names can be used
          directly.

          The abstract method returns an iterable of no items.

 -- 類別: importlib.abc.Traversable

     An object with a subset of *note pathlib.Path: 20e. methods
     suitable for traversing directories and opening files.

     For a representation of the object on the file-system, use *note
     importlib.resources.as_file(): 434.

     在 3.9 版被加入.

     Deprecated since version 3.12, will be removed in version 3.14: Use
     *note importlib.resources.abc.Traversable: 1d8. instead.

      -- 屬性: name

          Abstract.  The base name of this object without any parent
          references.

      -- 方法: abstractmethod iterdir ()

          Yield ‘Traversable’ objects in ‘self’.

      -- 方法: abstractmethod is_dir ()

          Return ‘True’ if ‘self’ is a directory.

      -- 方法: abstractmethod is_file ()

          Return ‘True’ if ‘self’ is a file.

      -- 方法: abstractmethod joinpath (child)

          Return Traversable child in ‘self’.

      -- 方法: abstractmethod __truediv__ (child)

          Return ‘Traversable’ child in ‘self’.

      -- 方法: abstractmethod open (mode='r', *args, **kwargs)

          'mode' may be 'r' or 'rb' to open as text or binary.  Return a
          handle suitable for reading (same as *note pathlib.Path.open:
          269e.).

          When opening as text, accepts encoding parameters such as
          those accepted by *note io.TextIOWrapper: 75f.

      -- 方法: read_bytes ()

          Read contents of ‘self’ as bytes.

      -- 方法: read_text (encoding=None)

          Read contents of ‘self’ as text.

 -- 類別: importlib.abc.TraversableResources

     An abstract base class for resource readers capable of serving the
     *note importlib.resources.files(): 435. interface.  Subclasses
     *note importlib.resources.abc.ResourceReader: 431d. and provides
     concrete implementations of the *note
     importlib.resources.abc.ResourceReader: 431d.'s abstract methods.
     Therefore, any loader supplying *note
     importlib.abc.TraversableResources: 1785. also supplies
     ResourceReader.

     Loaders that wish to support resource reading are expected to
     implement this interface.

     在 3.9 版被加入.

     Deprecated since version 3.12, will be removed in version 3.14: Use
     *note importlib.resources.abc.TraversableResources: 2a7. instead.

      -- 方法: abstractmethod files ()

          Returns a *note importlib.resources.abc.Traversable: 1d8.
          object for the loaded package.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/importlib/abc.py

   (2) https://peps.python.org/pep-0302/

   (3) https://peps.python.org/pep-0302/

   (4) https://peps.python.org/pep-0302/

   (5) https://peps.python.org/pep-0302/


File: python.info,  Node: importlib machinery -- Importers and path hooks,  Next: importlib util -- Utility code for importers,  Prev: importlib abc -- Abstract base classes related to import,  Up: importlib --- import 的實作

5.31.5.4 ‘importlib.machinery’ - Importers and path hooks
.........................................................

'原始碼：'Lib/importlib/machinery.py(1)

__________________________________________________________________

This module contains the various objects that help *note import: 586.
find and load modules.

 -- 屬性: importlib.machinery.SOURCE_SUFFIXES

     A list of strings representing the recognized file suffixes for
     source modules.

     在 3.3 版被加入.

 -- 屬性: importlib.machinery.DEBUG_BYTECODE_SUFFIXES

     A list of strings representing the file suffixes for non-optimized
     bytecode modules.

     在 3.3 版被加入.

     在 3.5 版之後被棄用: Use *note BYTECODE_SUFFIXES: 4ba. instead.

 -- 屬性: importlib.machinery.OPTIMIZED_BYTECODE_SUFFIXES

     A list of strings representing the file suffixes for optimized
     bytecode modules.

     在 3.3 版被加入.

     在 3.5 版之後被棄用: Use *note BYTECODE_SUFFIXES: 4ba. instead.

 -- 屬性: importlib.machinery.BYTECODE_SUFFIXES

     A list of strings representing the recognized file suffixes for
     bytecode modules (including the leading dot).

     在 3.3 版被加入.

     在 3.5 版的變更: The value is no longer dependent on ‘__debug__’.

 -- 屬性: importlib.machinery.EXTENSION_SUFFIXES

     A list of strings representing the recognized file suffixes for
     extension modules.

     在 3.3 版被加入.

 -- 函式: importlib.machinery.all_suffixes ()

     Returns a combined list of strings representing all file suffixes
     for modules recognized by the standard import machinery.  This is a
     helper for code which simply needs to know if a filesystem path
     potentially refers to a module without needing any details on the
     kind of module (for example, *note inspect.getmodulename(): ce0.).

     在 3.3 版被加入.

 -- 類別: importlib.machinery.BuiltinImporter

     An *note importer: 1ecb. for built-in modules.  All known built-in
     modules are listed in *note sys.builtin_module_names: 1b63.  This
     class implements the *note importlib.abc.MetaPathFinder: 813. and
     *note importlib.abc.InspectLoader: ef7. ABCs.

     Only class methods are defined by this class to alleviate the need
     for instantiation.

     在 3.5 版的變更: As part of PEP 489(2), the builtin importer now
     implements ‘Loader.create_module()’ and ‘Loader.exec_module()’

 -- 類別: importlib.machinery.FrozenImporter

     An *note importer: 1ecb. for frozen modules.  This class implements
     the *note importlib.abc.MetaPathFinder: 813. and *note
     importlib.abc.InspectLoader: ef7. ABCs.

     Only class methods are defined by this class to alleviate the need
     for instantiation.

     在 3.4 版的變更: Gained ‘create_module()’ and ‘exec_module()’
     methods.

 -- 類別: importlib.machinery.WindowsRegistryFinder

     *note Finder: 1eca. for modules declared in the Windows registry.
     This class implements the *note importlib.abc.MetaPathFinder: 813.
     ABC.

     Only class methods are defined by this class to alleviate the need
     for instantiation.

     在 3.3 版被加入.

     在 3.6 版之後被棄用: Use *note site: b5. configuration instead.
     Future versions of Python may not enable this finder by default.

 -- 類別: importlib.machinery.PathFinder

     A *note Finder: 1eca. for *note sys.path: 37f. and package
     ‘__path__’ attributes.  This class implements the *note
     importlib.abc.MetaPathFinder: 813. ABC.

     Only class methods are defined by this class to alleviate the need
     for instantiation.

      -- 方法: classmethod find_spec (fullname, path=None, target=None)

          Class method that attempts to find a *note spec: 419f. for the
          module specified by 'fullname' on *note sys.path: 37f. or, if
          defined, on 'path'.  For each path entry that is searched,
          *note sys.path_importer_cache: 588. is checked.  If a
          non-false object is found then it is used as the *note path
          entry finder: 1012. to look for the module being searched for.
          If no entry is found in *note sys.path_importer_cache: 588,
          then *note sys.path_hooks: fc7. is searched for a finder for
          the path entry and, if found, is stored in *note
          sys.path_importer_cache: 588. along with being queried about
          the module.  If no finder is ever found then ‘None’ is both
          stored in the cache and returned.

          在 3.4 版被加入.

          在 3.5 版的變更: If the current working directory -
          represented by an empty string - is no longer valid then
          ‘None’ is returned but no value is cached in *note
          sys.path_importer_cache: 588.

      -- 方法: classmethod invalidate_caches ()

          Calls *note importlib.abc.PathEntryFinder.invalidate_caches():
          431c. on all finders stored in *note sys.path_importer_cache:
          588. that define the method.  Otherwise entries in *note
          sys.path_importer_cache: 588. set to ‘None’ are deleted.

          在 3.7 版的變更: Entries of ‘None’ in *note
          sys.path_importer_cache: 588. are deleted.

     在 3.4 版的變更: Calls objects in *note sys.path_hooks: fc7. with
     the current working directory for ‘''’ (i.e.  the empty string).

 -- 類別: importlib.machinery.FileFinder (path, *loader_details)

     A concrete implementation of *note importlib.abc.PathEntryFinder:
     814. which caches results from the file system.

     The 'path' argument is the directory for which the finder is in
     charge of searching.

     The 'loader_details' argument is a variable number of 2-item tuples
     each containing a loader and a sequence of file suffixes the loader
     recognizes.  The loaders are expected to be callables which accept
     two arguments of the module's name and the path to the file found.

     The finder will cache the directory contents as necessary, making
     stat calls for each module search to verify the cache is not
     outdated.  Because cache staleness relies upon the granularity of
     the operating system's state information of the file system, there
     is a potential race condition of searching for a module, creating a
     new file, and then searching for the module the new file
     represents.  If the operations happen fast enough to fit within the
     granularity of stat calls, then the module search will fail.  To
     prevent this from happening, when you create a module dynamically,
     make sure to call *note importlib.invalidate_caches(): bb7.

     在 3.3 版被加入.

      -- 屬性: path

          The path the finder will search in.

      -- 方法: find_spec (fullname, target=None)

          Attempt to find the spec to handle 'fullname' within *note
          path: 433c.

          在 3.4 版被加入.

      -- 方法: invalidate_caches ()

          Clear out the internal cache.

      -- 方法: classmethod path_hook (*loader_details)

          A class method which returns a closure for use on *note
          sys.path_hooks: fc7.  An instance of *note FileFinder: 1013.
          is returned by the closure using the path argument given to
          the closure directly and 'loader_details' indirectly.

          If the argument to the closure is not an existing directory,
          *note ImportError: 352. is raised.

 -- 類別: importlib.machinery.SourceFileLoader (fullname, path)

     A concrete implementation of *note importlib.abc.SourceLoader:
     4327. by subclassing *note importlib.abc.FileLoader: 1014. and
     providing some concrete implementations of other methods.

     在 3.3 版被加入.

      -- 屬性: name

          The name of the module that this loader will handle.

      -- 屬性: path

          The path to the source file.

      -- 方法: is_package (fullname)

          Return ‘True’ if *note path: 4340. appears to be for a
          package.

      -- 方法: path_stats (path)

          Concrete implementation of *note
          importlib.abc.SourceLoader.path_stats(): 1124.

      -- 方法: set_data (path, data)

          Concrete implementation of *note
          importlib.abc.SourceLoader.set_data(): 4328.

      -- 方法: load_module (name=None)

          Concrete implementation of *note
          importlib.abc.Loader.load_module(): 80e. where specifying the
          name of the module to load is optional.

          在 3.6 版之後被棄用: Use *note
          importlib.abc.Loader.exec_module(): 80f. instead.

 -- 類別: importlib.machinery.SourcelessFileLoader (fullname, path)

     A concrete implementation of *note importlib.abc.FileLoader: 1014.
     which can import bytecode files (i.e.  no source code files exist).

     Please note that direct use of bytecode files (and thus not source
     code files) inhibits your modules from being usable by all Python
     implementations or new versions of Python which change the bytecode
     format.

     在 3.3 版被加入.

      -- 屬性: name

          The name of the module the loader will handle.

      -- 屬性: path

          The path to the bytecode file.

      -- 方法: is_package (fullname)

          Determines if the module is a package based on *note path:
          4345.

      -- 方法: get_code (fullname)

          Returns the code object for *note name: 4344. created from
          *note path: 4345.

      -- 方法: get_source (fullname)

          Returns ‘None’ as bytecode files have no source when this
          loader is used.

      -- 方法: load_module (name=None)

     Concrete implementation of *note
     importlib.abc.Loader.load_module(): 80e. where specifying the name
     of the module to load is optional.

     在 3.6 版之後被棄用: Use *note importlib.abc.Loader.exec_module():
     80f. instead.

 -- 類別: importlib.machinery.ExtensionFileLoader (fullname, path)

     A concrete implementation of *note importlib.abc.ExecutionLoader:
     4320. for extension modules.

     The 'fullname' argument specifies the name of the module the loader
     is to support.  The 'path' argument is the path to the extension
     module's file.

     Note that, by default, importing an extension module will fail in
     subinterpreters if it doesn't implement multi-phase init (see PEP
     489(3)), even if it would otherwise import successfully.

     在 3.3 版被加入.

     在 3.12 版的變更: Multi-phase init is now required for use in
     subinterpreters.

      -- 屬性: name

          Name of the module the loader supports.

      -- 屬性: path

          Path to the extension module.

      -- 方法: create_module (spec)

          Creates the module object from the given specification in
          accordance with PEP 489(4).

          在 3.5 版被加入.

      -- 方法: exec_module (module)

          Initializes the given module object in accordance with PEP
          489(5).

          在 3.5 版被加入.

      -- 方法: is_package (fullname)

          Returns ‘True’ if the file path points to a package's
          ‘__init__’ module based on *note EXTENSION_SUFFIXES: 4b9.

      -- 方法: get_code (fullname)

          Returns ‘None’ as extension modules lack a code object.

      -- 方法: get_source (fullname)

          Returns ‘None’ as extension modules do not have source code.

      -- 方法: get_filename (fullname)

          Returns *note path: 434a.

          在 3.4 版被加入.

 -- 類別: importlib.machinery.NamespaceLoader (name, path, path_finder)

     A concrete implementation of *note importlib.abc.InspectLoader:
     ef7. for namespace packages.  This is an alias for a private class
     and is only made public for introspecting the ‘__loader__’
     attribute on namespace packages:

          >>> from importlib.machinery import NamespaceLoader
          >>> import my_namespace
          >>> isinstance(my_namespace.__loader__, NamespaceLoader)
          True
          >>> import importlib.abc
          >>> isinstance(my_namespace.__loader__, importlib.abc.Loader)
          True

     在 3.11 版被加入.

 -- 類別: importlib.machinery.ModuleSpec (name, loader, *, origin=None,
          loader_state=None, is_package=None)

     A specification for a module's import-system-related state.  This
     is typically exposed as the module's *note __spec__: 1ed6.
     attribute.  In the descriptions below, the names in parentheses
     give the corresponding attribute available directly on the module
     object, e.g.  ‘module.__spec__.origin == module.__file__’.  Note,
     however, that while the 'values' are usually equivalent, they can
     differ since there is no synchronization between the two objects.
     For example, it is possible to update the module's *note __file__:
     1e02. at runtime and this will not be automatically reflected in
     the module's ‘__spec__.origin’, and vice versa.

     在 3.4 版被加入.

      -- 屬性: name

     (*note __name__: 1316.)

     The module's fully qualified name.  The *note finder: 1eca. should
     always set this attribute to a non-empty string.

      -- 屬性: loader

     (*note __loader__: fc1.)

     The *note loader: 15a8. used to load the module.  The *note finder:
     1eca. should always set this attribute.

      -- 屬性: origin

     (*note __file__: 1e02.)

     The location the *note loader: 15a8. should use to load the module.
     For example, for modules loaded from a .py file this is the
     filename.  The *note finder: 1eca. should always set this attribute
     to a meaningful value for the *note loader: 15a8. to use.  In the
     uncommon case that there is not one (like for namespace packages),
     it should be set to ‘None’.

      -- 屬性: submodule_search_locations

     (*note __path__: 1b72.)

     The list of locations where the package's submodules will be found.
     Most of the time this is a single directory.  The *note finder:
     1eca. should set this attribute to a list, even an empty one, to
     indicate to the import system that the module is a package.  It
     should be set to ‘None’ for non-package modules.  It is set
     automatically later to a special object for namespace packages.

      -- 屬性: loader_state

     The *note finder: 1eca. may set this attribute to an object
     containing additional, module-specific data to use when loading the
     module.  Otherwise it should be set to ‘None’.

      -- 屬性: cached

     (*note __cached__: 114d.)

     The filename of a compiled version of the module's code.  The *note
     finder: 1eca. should always set this attribute but it may be ‘None’
     for modules that do not need compiled code stored.

      -- 屬性: parent

     (*note __package__: fc0.)

     (Read-only) The fully qualified name of the package the module is
     in (or the empty string for a top-level module).  If the module is
     a package then this is the same as *note name: 2453.

      -- 屬性: has_location

     ‘True’ if the spec's *note origin: 4350. refers to a loadable location,

          ‘False’ otherwise.  This value impacts how *note origin: 4350.
          is interpreted and how the module's *note __file__: 1e02. is
          populated.

 -- 類別: importlib.machinery.AppleFrameworkLoader (name, path)

     A specialization of *note importlib.machinery.ExtensionFileLoader:
     c57. that is able to load extension modules in Framework format.

     For compatibility with the iOS App Store, 'all' binary modules in
     an iOS app must be dynamic libraries, contained in a framework with
     appropriate metadata, stored in the ‘Frameworks’ folder of the
     packaged app.  There can be only a single binary per framework, and
     there can be no executable binary material outside the Frameworks
     folder.

     To accommodate this requirement, when running on iOS, extension
     module binaries are 'not' packaged as ‘.so’ files on ‘sys.path’,
     but as individual standalone frameworks.  To discover those
     frameworks, this loader is be registered against the ‘.fwork’ file
     extension, with a ‘.fwork’ file acting as a placeholder in the
     original location of the binary on ‘sys.path’.  The ‘.fwork’ file
     contains the path of the actual binary in the ‘Frameworks’ folder,
     relative to the app bundle.  To allow for resolving a
     framework-packaged binary back to the original location, the
     framework is expected to contain a ‘.origin’ file that contains the
     location of the ‘.fwork’ file, relative to the app bundle.

     For example, consider the case of an import ‘from foo.bar import
     _whiz’, where ‘_whiz’ is implemented with the binary module
     ‘sources/foo/bar/_whiz.abi3.so’, with ‘sources’ being the location
     registered on ‘sys.path’, relative to the application bundle.  This
     module 'must' be distributed as
     ‘Frameworks/foo.bar._whiz.framework/foo.bar._whiz’ (creating the
     framework name from the full import path of the module), with an
     ‘Info.plist’ file in the ‘.framework’ directory identifying the
     binary as a framework.  The ‘foo.bar._whiz’ module would be
     represented in the original location with a
     ‘sources/foo/bar/_whiz.abi3.fwork’ marker file, containing the path
     ‘Frameworks/foo.bar._whiz/foo.bar._whiz’.  The framework would also
     contain ‘Frameworks/foo.bar._whiz.framework/foo.bar._whiz.origin’,
     containing the path to the ‘.fwork’ file.

     When a module is loaded with this loader, the ‘__file__’ for the
     module will report as the location of the ‘.fwork’ file.  This
     allows code to use the ‘__file__’ of a module as an anchor for file
     system traveral.  However, the spec origin will reference the
     location of the 'actual' binary in the ‘.framework’ folder.

     The Xcode project building the app is responsible for converting
     any ‘.so’ files from wherever they exist in the ‘PYTHONPATH’ into
     frameworks in the ‘Frameworks’ folder (including stripping
     extensions from the module file, the addition of framework
     metadata, and signing the resulting framework), and creating the
     ‘.fwork’ and ‘.origin’ files.  This will usually be done with a
     build step in the Xcode project; see the iOS documentation for
     details on how to construct this build step.

     在 3.13 版被加入.

     *note Availability: 1c56.: iOS.

      -- 屬性: name

          Name of the module the loader supports.

      -- 屬性: path

          Path to the ‘.fwork’ file for the extension module.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/importlib/machinery.py

   (2) https://peps.python.org/pep-0489/

   (3) https://peps.python.org/pep-0489/

   (4) https://peps.python.org/pep-0489/

   (5) https://peps.python.org/pep-0489/


File: python.info,  Node: importlib util -- Utility code for importers,  Next: 範例<46>,  Prev: importlib machinery -- Importers and path hooks,  Up: importlib --- import 的實作

5.31.5.5 ‘importlib.util’ - Utility code for importers
......................................................

'原始碼：'Lib/importlib/util.py(1)

__________________________________________________________________

This module contains the various objects that help in the construction
of an *note importer: 1ecb.

 -- 屬性: importlib.util.MAGIC_NUMBER

     The bytes which represent the bytecode version number.  If you need
     help with loading/writing bytecode then consider *note
     importlib.abc.SourceLoader: 4327.

     在 3.4 版被加入.

 -- 函式: importlib.util.cache_from_source (path, debug_override=None,
          *, optimization=None)

     Return the PEP 3147(2)/ PEP 488(3) path to the byte-compiled file
     associated with the source 'path'.  For example, if 'path' is
     ‘/foo/bar/baz.py’ the return value would be
     ‘/foo/bar/__pycache__/baz.cpython-32.pyc’ for Python 3.2.  The
     ‘cpython-32’ string comes from the current magic tag (see
     ‘get_tag()’; if ‘sys.implementation.cache_tag’ is not defined then
     *note NotImplementedError: 20d. will be raised).

     The 'optimization' parameter is used to specify the optimization
     level of the bytecode file.  An empty string represents no
     optimization, so ‘/foo/bar/baz.py’ with an 'optimization' of ‘''’
     will result in a bytecode path of
     ‘/foo/bar/__pycache__/baz.cpython-32.pyc’.  ‘None’ causes the
     interpreter's optimization level to be used.  Any other value's
     string representation is used, so ‘/foo/bar/baz.py’ with an
     'optimization' of ‘2’ will lead to the bytecode path of
     ‘/foo/bar/__pycache__/baz.cpython-32.opt-2.pyc’.  The string
     representation of 'optimization' can only be alphanumeric, else
     *note ValueError: 1e7. is raised.

     The 'debug_override' parameter is deprecated and can be used to
     override the system's value for ‘__debug__’.  A ‘True’ value is the
     equivalent of setting 'optimization' to the empty string.  A
     ‘False’ value is the same as setting 'optimization' to ‘1’.  If
     both 'debug_override' an 'optimization' are not ‘None’ then *note
     TypeError: 4dd. is raised.

     在 3.4 版被加入.

     在 3.5 版的變更: The 'optimization' parameter was added and the
     'debug_override' parameter was deprecated.

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 函式: importlib.util.source_from_cache (path)

     Given the 'path' to a PEP 3147(4) file name, return the associated
     source code file path.  For example, if 'path' is
     ‘/foo/bar/__pycache__/baz.cpython-32.pyc’ the returned path would
     be ‘/foo/bar/baz.py’.  'path' need not exist, however if it does
     not conform to PEP 3147(5) or PEP 488(6) format, a *note
     ValueError: 1e7. is raised.  If ‘sys.implementation.cache_tag’ is
     not defined, *note NotImplementedError: 20d. is raised.

     在 3.4 版被加入.

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 函式: importlib.util.decode_source (source_bytes)

     Decode the given bytes representing source code and return it as a
     string with universal newlines (as required by *note
     importlib.abc.InspectLoader.get_source(): efb.).

     在 3.4 版被加入.

 -- 函式: importlib.util.resolve_name (name, package)

     Resolve a relative module name to an absolute one.

     If 'name' has no leading dots, then 'name' is simply returned.
     This allows for usage such as ‘importlib.util.resolve_name('sys',
     __spec__.parent)’ without doing a check to see if the 'package'
     argument is needed.

     *note ImportError: 352. is raised if 'name' is a relative module
     name but 'package' is a false value (e.g.  ‘None’ or the empty
     string).  *note ImportError: 352. is also raised if a relative name
     would escape its containing package (e.g.  requesting ‘..bacon’
     from within the ‘spam’ package).

     在 3.3 版被加入.

     在 3.9 版的變更: To improve consistency with import statements,
     raise *note ImportError: 352. instead of *note ValueError: 1e7. for
     invalid relative import attempts.

 -- 函式: importlib.util.find_spec (name, package=None)

     Find the *note spec: 419f. for a module, optionally relative to the
     specified 'package' name.  If the module is in *note sys.modules:
     186e, then ‘sys.modules[name].__spec__’ is returned (unless the
     spec would be ‘None’ or is not set, in which case *note ValueError:
     1e7. is raised).  Otherwise a search using *note sys.meta_path:
     cd2. is done.  ‘None’ is returned if no spec is found.

     If 'name' is for a submodule (contains a dot), the parent module is
     automatically imported.

     'name' and 'package' work the same as for ‘import_module()’.

     在 3.4 版被加入.

     在 3.7 版的變更: Raises *note ModuleNotFoundError: aeb. instead of
     *note AttributeError: 2f6. if 'package' is in fact not a package
     (i.e.  lacks a *note __path__: 1b72. attribute).

 -- 函式: importlib.util.module_from_spec (spec)

     Create a new module based on 'spec' and *note
     spec.loader.create_module: c55.

     If *note spec.loader.create_module: c55. does not return ‘None’,
     then any pre-existing attributes will not be reset.  Also, no *note
     AttributeError: 2f6. will be raised if triggered while accessing
     'spec' or setting an attribute on the module.

     This function is preferred over using *note types.ModuleType: db9.
     to create a new module as 'spec' is used to set as many
     import-controlled attributes on the module as possible.

     在 3.5 版被加入.

 -- 函式: importlib.util.spec_from_loader (name, loader, *, origin=None,
          is_package=None)

     A factory function for creating a *note ModuleSpec: 1d5a. instance
     based on a loader.  The parameters have the same meaning as they do
     for ModuleSpec.  The function uses available *note loader: 15a8.
     APIs, such as ‘InspectLoader.is_package()’, to fill in any missing
     information on the spec.

     在 3.4 版被加入.

 -- 函式: importlib.util.spec_from_file_location (name, location, *,
          loader=None, submodule_search_locations=None)

     A factory function for creating a *note ModuleSpec: 1d5a. instance
     based on the path to a file.  Missing information will be filled in
     on the spec by making use of loader APIs and by the implication
     that the module will be file-based.

     在 3.4 版被加入.

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- 函式: importlib.util.source_hash (source_bytes)

     Return the hash of 'source_bytes' as bytes.  A hash-based ‘.pyc’
     file embeds the *note source_hash(): 4358. of the corresponding
     source file's contents in its header.

     在 3.7 版被加入.

 -- 函式: importlib.util._incompatible_extension_module_restrictions (*,
          disable_check)

     A context manager that can temporarily skip the compatibility check
     for extension modules.  By default the check is enabled and will
     fail when a single-phase init module is imported in a
     subinterpreter.  It will also fail for a multi-phase init module
     that doesn't explicitly support a per-interpreter GIL, when
     imported in an interpreter with its own GIL.

     Note that this function is meant to accommodate an unusual case;
     one which is likely to eventually go away.  There's is a pretty
     good chance this is not what you were looking for.

     You can get the same effect as this function by implementing the
     basic interface of multi-phase init ( PEP 489(7)) and lying about
     support for multiple interpreters (or per-interpreter GIL).

          警告: Using this function to disable the check can lead to
          unexpected behavior and even crashes.  It should only be used
          during extension module development.

     在 3.12 版被加入.

 -- 類別: importlib.util.LazyLoader (loader)

     A class which postpones the execution of the loader of a module
     until the module has an attribute accessed.

     This class 'only' works with loaders that define *note
     exec_module(): 80f. as control over what module type is used for
     the module is required.  For those same reasons, the loader's *note
     create_module(): c55. method must return ‘None’ or a type for which
     its ‘__class__’ attribute can be mutated along with not using *note
     slots: 583.  Finally, modules which substitute the object placed
     into *note sys.modules: 186e. will not work as there is no way to
     properly replace the module references throughout the interpreter
     safely; *note ValueError: 1e7. is raised if such a substitution is
     detected.

          備註: For projects where startup time is critical, this class
          allows for potentially minimizing the cost of loading a module
          if it is never used.  For projects where startup time is not
          essential then use of this class is 'heavily' discouraged due
          to error messages created during loading being postponed and
          thus occurring out of context.

     在 3.5 版被加入.

     在 3.6 版的變更: Began calling *note create_module(): c55, removing
     the compatibility warning for *note
     importlib.machinery.BuiltinImporter: c56. and *note
     importlib.machinery.ExtensionFileLoader: c57.

      -- 方法: classmethod factory (loader)

          A class method which returns a callable that creates a lazy
          loader.  This is meant to be used in situations where the
          loader is passed by class instead of by instance.

               suffixes = importlib.machinery.SOURCE_SUFFIXES
               loader = importlib.machinery.SourceFileLoader
               lazy_loader = importlib.util.LazyLoader.factory(loader)
               finder = importlib.machinery.FileFinder(path, (lazy_loader, suffixes))

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/importlib/util.py

   (2) https://peps.python.org/pep-3147/

   (3) https://peps.python.org/pep-0488/

   (4) https://peps.python.org/pep-3147/

   (5) https://peps.python.org/pep-3147/

   (6) https://peps.python.org/pep-0488/

   (7) https://peps.python.org/pep-0489/


File: python.info,  Node: 範例<46>,  Prev: importlib util -- Utility code for importers,  Up: importlib --- import 的實作

5.31.5.6 範例
.............

* Menu:

* Importing programmatically::
* Checking if a module can be imported::
* Importing a source file directly::
* Implementing lazy imports::
* Setting up an importer::
* Approximating importlib.import_module(): Approximating importlib import_module.


File: python.info,  Node: Importing programmatically,  Next: Checking if a module can be imported,  Up: 範例<46>

5.31.5.7 Importing programmatically
...................................

To programmatically import a module, use *note
importlib.import_module(): 4bc.

     import importlib

     itertools = importlib.import_module('itertools')


File: python.info,  Node: Checking if a module can be imported,  Next: Importing a source file directly,  Prev: Importing programmatically,  Up: 範例<46>

5.31.5.8 Checking if a module can be imported
.............................................

If you need to find out if a module can be imported without actually
doing the import, then you should use *note importlib.util.find_spec():
2af.

Note that if ‘name’ is a submodule (contains a dot), *note
importlib.util.find_spec(): 2af. will import the parent module.

     import importlib.util
     import sys

     # For illustrative purposes.
     name = 'itertools'

     if name in sys.modules:
         print(f"{name!r} already in sys.modules")
     elif (spec := importlib.util.find_spec(name)) is not None:
         # If you chose to perform the actual import ...
         module = importlib.util.module_from_spec(spec)
         sys.modules[name] = module
         spec.loader.exec_module(module)
         print(f"{name!r} has been imported")
     else:
         print(f"can't find the {name!r} module")


File: python.info,  Node: Importing a source file directly,  Next: Implementing lazy imports,  Prev: Checking if a module can be imported,  Up: 範例<46>

5.31.5.9 Importing a source file directly
.........................................

To import a Python source file directly, use the following recipe:

     import importlib.util
     import sys

     # For illustrative purposes.
     import tokenize
     file_path = tokenize.__file__
     module_name = tokenize.__name__

     spec = importlib.util.spec_from_file_location(module_name, file_path)
     module = importlib.util.module_from_spec(spec)
     sys.modules[module_name] = module
     spec.loader.exec_module(module)


File: python.info,  Node: Implementing lazy imports,  Next: Setting up an importer,  Prev: Importing a source file directly,  Up: 範例<46>

5.31.5.10 Implementing lazy imports
...................................

The example below shows how to implement lazy imports:

     >>> import importlib.util
     >>> import sys
     >>> def lazy_import(name):
     ...     spec = importlib.util.find_spec(name)
     ...     loader = importlib.util.LazyLoader(spec.loader)
     ...     spec.loader = loader
     ...     module = importlib.util.module_from_spec(spec)
     ...     sys.modules[name] = module
     ...     loader.exec_module(module)
     ...     return module
     ...
     >>> lazy_typing = lazy_import("typing")
     >>> #lazy_typing is a real module object,
     >>> #but it is not loaded in memory yet.
     >>> lazy_typing.TYPE_CHECKING
     False


File: python.info,  Node: Setting up an importer,  Next: Approximating importlib import_module,  Prev: Implementing lazy imports,  Up: 範例<46>

5.31.5.11 Setting up an importer
................................

For deep customizations of import, you typically want to implement an
*note importer: 1ecb.  This means managing both the *note finder: 1eca.
and *note loader: 15a8. side of things.  For finders there are two
flavours to choose from depending on your needs: a *note meta path
finder: 1011. or a *note path entry finder: 1012.  The former is what
you would put on *note sys.meta_path: cd2. while the latter is what you
create using a *note path entry hook: 1ee1. on *note sys.path_hooks:
fc7. which works with *note sys.path: 37f. entries to potentially create
a finder.  This example will show you how to register your own importers
so that import will use them (for creating an importer for yourself,
read the documentation for the appropriate classes defined within this
package):

     import importlib.machinery
     import sys

     # For illustrative purposes only.
     SpamMetaPathFinder = importlib.machinery.PathFinder
     SpamPathEntryFinder = importlib.machinery.FileFinder
     loader_details = (importlib.machinery.SourceFileLoader,
                       importlib.machinery.SOURCE_SUFFIXES)

     # Setting up a meta path finder.
     # Make sure to put the finder in the proper location in the list in terms of
     # priority.
     sys.meta_path.append(SpamMetaPathFinder)

     # Setting up a path entry finder.
     # Make sure to put the path hook in the proper location in the list in terms
     # of priority.
     sys.path_hooks.append(SpamPathEntryFinder.path_hook(loader_details))


File: python.info,  Node: Approximating importlib import_module,  Prev: Setting up an importer,  Up: 範例<46>

5.31.5.12 Approximating ‘importlib.import_module()’
...................................................

Import itself is implemented in Python code, making it possible to
expose most of the import machinery through importlib.  The following
helps illustrate the various APIs that importlib exposes by providing an
approximate implementation of *note importlib.import_module(): 4bc.:

     import importlib.util
     import sys

     def import_module(name, package=None):
         """An approximate implementation of import."""
         absolute_name = importlib.util.resolve_name(name, package)
         try:
             return sys.modules[absolute_name]
         except KeyError:
             pass

         path = None
         if '.' in absolute_name:
             parent_name, _, child_name = absolute_name.rpartition('.')
             parent_module = import_module(parent_name)
             path = parent_module.__spec__.submodule_search_locations
         for finder in sys.meta_path:
             spec = finder.find_spec(absolute_name, path)
             if spec is not None:
                 break
         else:
             msg = f'No module named {absolute_name!r}'
             raise ModuleNotFoundError(msg, name=absolute_name)
         module = importlib.util.module_from_spec(spec)
         sys.modules[absolute_name] = module
         spec.loader.exec_module(module)
         if path is not None:
             setattr(parent_module, child_name, module)
         return module


File: python.info,  Node: importlib resources -- Package resource reading opening and access,  Next: importlib resources abc -- 資源的抽象基底類別,  Prev: importlib --- import 的實作,  Up: 引入模組

5.31.6 ‘importlib.resources’ - Package resource reading, opening and access
---------------------------------------------------------------------------

'原始碼：'Lib/importlib/resources/__init__.py(1)

__________________________________________________________________

在 3.7 版被加入.

This module leverages Python's import system to provide access to
'resources' within 'packages'.

"Resources" are file-like resources associated with a module or package
in Python.  The resources may be contained directly in a package, within
a subdirectory contained in that package, or adjacent to modules outside
a package.  Resources may be text or binary.  As a result, Python module
sources (.py) of a package and compilation artifacts (pycache) are
technically de-facto resources of that package.  In practice, however,
resources are primarily those non-Python artifacts exposed specifically
by the package author.

Resources can be opened or read in either binary or text mode.

Resources are roughly akin to files inside directories, though it's
important to keep in mind that this is just a metaphor.  Resources and
packages 'do not' have to exist as physical files and directories on the
file system: for example, a package and its resources can be imported
from a zip file using *note zipimport: 118.

     備註: This module provides functionality similar to
     pkg_resources(2) Basic Resource Access(3) without the performance
     overhead of that package.  This makes reading resources included in
     packages easier, with more stable and consistent semantics.

     The standalone backport of this module provides more information on
     using importlib.resources(4) and migrating from pkg_resources to
     importlib.resources(5).

*note Loaders: e69. that wish to support resource reading should
implement a ‘get_resource_reader(fullname)’ method as specified by *note
importlib.resources.abc.ResourceReader: 431d.

 -- 類別: importlib.resources.Anchor

     Represents an anchor for resources, either a *note module object:
     db9. or a module name as a string.  Defined as ‘Union[str,
     ModuleType]’.

 -- 函式: importlib.resources.files (anchor: Anchor | None = None)

     Returns a *note Traversable: 1d8. object representing the resource
     container (think directory) and its resources (think files).  A
     Traversable may contain other containers (think subdirectories).

     'anchor' is an optional *note Anchor: 4365.  If the anchor is a
     package, resources are resolved from that package.  If a module,
     resources are resolved adjacent to that module (in the same package
     or the package root).  If the anchor is omitted, the caller's
     module is used.

     在 3.9 版被加入.

     在 3.12 版的變更: 'package' parameter was renamed to 'anchor'.
     'anchor' can now be a non-package module and if omitted will
     default to the caller's module.  'package' is still accepted for
     compatibility but will raise a *note DeprecationWarning: 18b.
     Consider passing the anchor positionally or using
     ‘importlib_resources >= 5.10’ for a compatible interface on older
     Pythons.

 -- 函式: importlib.resources.as_file (traversable)

     Given a *note Traversable: 1d8. object representing a file or
     directory, typically from *note importlib.resources.files(): 435,
     return a context manager for use in a *note with: 577. statement.
     The context manager provides a *note pathlib.Path: 20e. object.

     Exiting the context manager cleans up any temporary file or
     directory created when the resource was extracted from e.g.  a zip
     file.

     Use ‘as_file’ when the Traversable methods (‘read_text’, etc) are
     insufficient and an actual file or directory on the file system is
     required.

     在 3.9 版被加入.

     在 3.12 版的變更: Added support for 'traversable' representing a
     directory.

* Menu:

* Functional API::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/importlib/resources/__init__.py

   (2) https://setuptools.readthedocs.io/en/latest/pkg_resources.html

   (3) 
https://setuptools.readthedocs.io/en/latest/pkg_resources.html#basic-resource-access

   (4) https://importlib-resources.readthedocs.io/en/latest/using.html

   (5) 
https://importlib-resources.readthedocs.io/en/latest/migration.html


File: python.info,  Node: Functional API,  Up: importlib resources -- Package resource reading opening and access

5.31.6.1 Functional API
.......................

A set of simplified, backwards-compatible helpers is available.  These
allow common operations in a single function call.

For all the following functions:

   - 'anchor' is an *note Anchor: 4365, as in *note files(): 435.
     Unlike in ‘files’, it may not be omitted.

   - 'path_names' are components of a resource's path name, relative to
     the anchor.  For example, to get the text of resource named
     ‘info.txt’, use:

          importlib.resources.read_text(my_module, "info.txt")

     Like *note Traversable.joinpath: 1d8, The individual components
     should use forward slashes (‘/’) as path separators.  For example,
     the following are equivalent:

          importlib.resources.read_binary(my_module, "pics/painting.png")
          importlib.resources.read_binary(my_module, "pics", "painting.png")

     For backward compatibility reasons, functions that read text
     require an explicit 'encoding' argument if multiple 'path_names'
     are given.  For example, to get the text of ‘info/chapter1.txt’,
     use:

          importlib.resources.read_text(my_module, "info", "chapter1.txt",
                                        encoding='utf-8')

 -- 函式: importlib.resources.open_binary (anchor, *path_names)

     Open the named resource for binary reading.

     See *note the introduction: 4367. for details on 'anchor' and
     'path_names'.

     This function returns a *note BinaryIO: 3dc7. object, that is, a
     binary stream open for reading.

     This function is roughly equivalent to:

          files(anchor).joinpath(*path_names).open('rb')

     在 3.13 版的變更: Multiple 'path_names' are accepted.

 -- 函式: importlib.resources.open_text (anchor, *path_names,
          encoding='utf-8', errors='strict')

     Open the named resource for text reading.  By default, the contents
     are read as strict UTF-8.

     See *note the introduction: 4367. for details on 'anchor' and
     'path_names'.  'encoding' and 'errors' have the same meaning as in
     built-in *note open(): 4c0.

     For backward compatibility reasons, the 'encoding' argument must be
     given explicitly if there are multiple 'path_names'.  This
     limitation is scheduled to be removed in Python 3.15.

     This function returns a *note TextIO: 3dc6. object, that is, a text
     stream open for reading.

     This function is roughly equivalent to:

          files(anchor).joinpath(*path_names).open('r', encoding=encoding)

     在 3.13 版的變更: Multiple 'path_names' are accepted.  'encoding'
     and 'errors' must be given as keyword arguments.

 -- 函式: importlib.resources.read_binary (anchor, *path_names)

     Read and return the contents of the named resource as *note bytes:
     1a5.

     See *note the introduction: 4367. for details on 'anchor' and
     'path_names'.

     This function is roughly equivalent to:

          files(anchor).joinpath(*path_names).read_bytes()

     在 3.13 版的變更: Multiple 'path_names' are accepted.

 -- 函式: importlib.resources.read_text (anchor, *path_names,
          encoding='utf-8', errors='strict')

     Read and return the contents of the named resource as *note str:
     3f2.  By default, the contents are read as strict UTF-8.

     See *note the introduction: 4367. for details on 'anchor' and
     'path_names'.  'encoding' and 'errors' have the same meaning as in
     built-in *note open(): 4c0.

     For backward compatibility reasons, the 'encoding' argument must be
     given explicitly if there are multiple 'path_names'.  This
     limitation is scheduled to be removed in Python 3.15.

     This function is roughly equivalent to:

          files(anchor).joinpath(*path_names).read_text(encoding=encoding)

     在 3.13 版的變更: Multiple 'path_names' are accepted.  'encoding'
     and 'errors' must be given as keyword arguments.

 -- 函式: importlib.resources.path (anchor, *path_names)

     Provides the path to the 'resource' as an actual file system path.
     This function returns a context manager for use in a *note with:
     577. statement.  The context manager provides a *note pathlib.Path:
     20e. object.

     Exiting the context manager cleans up any temporary files created,
     e.g.  when the resource needs to be extracted from a zip file.

     For example, the *note stat(): 7c7. method requires an actual file
     system path; it can be used like this:

          with importlib.resources.path(anchor, "resource.txt") as fspath:
              result = fspath.stat()

     See *note the introduction: 4367. for details on 'anchor' and
     'path_names'.

     This function is roughly equivalent to:

          as_file(files(anchor).joinpath(*path_names))

     在 3.13 版的變更: Multiple 'path_names' are accepted.  'encoding'
     and 'errors' must be given as keyword arguments.

 -- 函式: importlib.resources.is_resource (anchor, *path_names)

     Return ‘True’ if the named resource exists, otherwise ‘False’.
     This function does not consider directories to be resources.

     See *note the introduction: 4367. for details on 'anchor' and
     'path_names'.

     This function is roughly equivalent to:

          files(anchor).joinpath(*path_names).is_file()

     在 3.13 版的變更: Multiple 'path_names' are accepted.

 -- 函式: importlib.resources.contents (anchor, *path_names)

     Return an iterable over the named items within the package or path.
     The iterable returns names of resources (e.g.  files) and
     non-resources (e.g.  directories) as *note str: 3f2.  The iterable
     does not recurse into subdirectories.

     See *note the introduction: 4367. for details on 'anchor' and
     'path_names'.

     This function is roughly equivalent to:

          for resource in files(anchor).joinpath(*path_names).iterdir():
              yield resource.name

     在 3.11 版之後被棄用: Prefer ‘iterdir()’ as above, which offers
     more control over the results and richer functionality.


File: python.info,  Node: importlib resources abc -- 資源的抽象基底類別,  Next: importlib metadata -- 存取套件的元資料,  Prev: importlib resources -- Package resource reading opening and access,  Up: 引入模組

5.31.7 ‘importlib.resources.abc’ - 資源的抽象基底類別
-----------------------------------------------------

'原始碼：'Lib/importlib/resources/abc.py(1)

__________________________________________________________________

在 3.11 版被加入.

 -- 類別: importlib.resources.abc.ResourceReader

     'Superseded by TraversableResources'

     An *note abstract base class: 114e. to provide the ability to read
     'resources'.

     From the perspective of this ABC, a 'resource' is a binary artifact
     that is shipped within a package.  Typically this is something like
     a data file that lives next to the ‘__init__.py’ file of the
     package.  The purpose of this class is to help abstract out the
     accessing of such data files so that it does not matter if the
     package and its data file(s) are stored e.g.  in a zip file versus
     on the file system.

     For any of methods of this class, a 'resource' argument is expected
     to be a *note path-like object: ac2. which represents conceptually
     just a file name.  This means that no subdirectory paths should be
     included in the 'resource' argument.  This is because the location
     of the package the reader is for, acts as the "directory".  Hence
     the metaphor for directories and file names is packages and
     resources, respectively.  This is also why instances of this class
     are expected to directly correlate to a specific package (instead
     of potentially representing multiple packages or a module).

     Loaders that wish to support resource reading are expected to
     provide a method called ‘get_resource_reader(fullname)’ which
     returns an object implementing this ABC's interface.  If the module
     specified by fullname is not a package, this method should return
     *note None: 61b.  An object compatible with this ABC should only be
     returned when the specified module is a package.

     Deprecated since version 3.12, will be removed in version 3.14: Use
     *note importlib.resources.abc.TraversableResources: 2a7. instead.

      -- 方法: abstractmethod open_resource (resource)

          Returns an opened, *note file-like object: 246a. for binary
          reading of the 'resource'.

          If the resource cannot be found, *note FileNotFoundError: e67.
          is raised.

      -- 方法: abstractmethod resource_path (resource)

          Returns the file system path to the 'resource'.

          If the resource does not concretely exist on the file system,
          raise *note FileNotFoundError: e67.

      -- 方法: abstractmethod is_resource (name)

          Returns ‘True’ if the named 'name' is considered a resource.
          *note FileNotFoundError: e67. is raised if 'name' does not
          exist.

      -- 方法: abstractmethod contents ()

          Returns an *note iterable: 11bf. of strings over the contents
          of the package.  Do note that it is not required that all
          names returned by the iterator be actual resources, e.g.  it
          is acceptable to return names for which *note is_resource():
          436c. would be false.

          Allowing non-resource names to be returned is to allow for
          situations where how a package and its resources are stored
          are known a priori and the non-resource names would be useful.
          For instance, returning subdirectory names is allowed so that
          when it is known that the package and resources are stored on
          the file system then those subdirectory names can be used
          directly.

          The abstract method returns an iterable of no items.

 -- 類別: importlib.resources.abc.Traversable

     An object with a subset of *note pathlib.Path: 20e. methods
     suitable for traversing directories and opening files.

     For a representation of the object on the file-system, use *note
     importlib.resources.as_file(): 434.

      -- 屬性: name

          Abstract.  The base name of this object without any parent
          references.

      -- 方法: abstractmethod iterdir ()

          Yield Traversable objects in self.

      -- 方法: abstractmethod is_dir ()

          Return ‘True’ if self is a directory.

      -- 方法: abstractmethod is_file ()

          Return ‘True’ if self is a file.

      -- 方法: abstractmethod joinpath (*pathsegments)

          Traverse directories according to 'pathsegments' and return
          the result as ‘Traversable’.

          Each 'pathsegments' argument may contain multiple names
          separated by forward slashes (‘/’, ‘posixpath.sep’ ).  For
          example, the following are equivalent:

               files.joinpath('subdir', 'subsuddir', 'file.txt')
               files.joinpath('subdir/subsuddir/file.txt')

          Note that some ‘Traversable’ implementations might not be
          updated to the latest version of the protocol.  For
          compatibility with such implementations, provide a single
          argument without path separators to each call to ‘joinpath’.
          For example:

               files.joinpath('subdir').joinpath('subsubdir').joinpath('file.txt')

          在 3.11 版的變更: ‘joinpath’ accepts multiple 'pathsegments',
          and these segments may contain forward slashes as path
          separators.  Previously, only a single 'child' argument was
          accepted.

      -- 方法: abstractmethod __truediv__ (child)

          Return Traversable child in self.  Equivalent to
          ‘joinpath(child)’.

      -- 方法: abstractmethod open (mode='r', *args, **kwargs)

          'mode' may be 'r' or 'rb' to open as text or binary.  Return a
          handle suitable for reading (same as *note pathlib.Path.open:
          269e.).

          When opening as text, accepts encoding parameters such as
          those accepted by *note io.TextIOWrapper: 75f.

      -- 方法: read_bytes ()

          Read contents of self as bytes.

      -- 方法: read_text (encoding=None)

          Read contents of self as text.

 -- 類別: importlib.resources.abc.TraversableResources

     An abstract base class for resource readers capable of serving the
     *note importlib.resources.files(): 435. interface.  Subclasses
     *note ResourceReader: 431d. and provides concrete implementations
     of the ‘ResourceReader’'s abstract methods.  Therefore, any loader
     supplying ‘TraversableResources’ also supplies ‘ResourceReader’.

     Loaders that wish to support resource reading are expected to
     implement this interface.

      -- 方法: abstractmethod files ()

          Returns a *note importlib.resources.abc.Traversable: 1d8.
          object for the loaded package.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/importlib/resources/abc.py


File: python.info,  Node: importlib metadata -- 存取套件的元資料,  Next: The initialization of the sys path module search path,  Prev: importlib resources abc -- 資源的抽象基底類別,  Up: 引入模組

5.31.8 ‘importlib.metadata’ - 存取套件的元資料
----------------------------------------------

在 3.8 版被加入.

在 3.10 版的變更: ‘importlib.metadata’ is no longer provisional.

'原始碼：'Lib/importlib/metadata/__init__.py(1)

‘importlib.metadata’ is a library that provides access to the metadata
of an installed Distribution Package(2), such as its entry points or its
top-level names (Import Package(3)s, modules, if any).  Built in part on
Python's import system, this library intends to replace similar
functionality in the entry point API(4) and metadata API(5) of
‘pkg_resources’.  Along with *note importlib.resources: 6f, this package
can eliminate the need to use the older and less efficient
‘pkg_resources’ package.

‘importlib.metadata’ operates on third-party 'distribution packages'
installed into Python's ‘site-packages’ directory via tools such as
pip(6).  Specifically, it works with distributions with discoverable
‘dist-info’ or ‘egg-info’ directories, and metadata defined by the Core
metadata specifications(7).

     重要: These are 'not' necessarily equivalent to or correspond 1:1
     with the top-level 'import package' names that can be imported
     inside Python code.  One 'distribution package' can contain
     multiple 'import packages' (and single modules), and one top-level
     'import package' may map to multiple 'distribution packages' if it
     is a namespace package.  You can use *note
     packages_distributions(): 7b4. to get a mapping between them.

By default, distribution metadata can live on the file system or in zip
archives on *note sys.path: 37f.  Through an extension mechanism, the
metadata can live almost anywhere.

也參考
......

‘https://importlib-metadata.readthedocs.io/’

     The documentation for ‘importlib_metadata’, which supplies a
     backport of ‘importlib.metadata’.  This includes an API
     reference(8) for this module's classes and functions, as well as a
     migration guide(9) for existing users of ‘pkg_resources’.

* Menu:

* Overview: Overview<2>.
* Functional API: Functional API<2>.
* Distributions::
* Distribution Discovery::
* Extending the search algorithm::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/importlib/metadata/__init__.py

   (2) 
https://packaging.python.org/en/latest/glossary/#term-Distribution-Package

   (3) 
https://packaging.python.org/en/latest/glossary/#term-Import-Package

   (4) 
https://setuptools.readthedocs.io/en/latest/pkg_resources.html#entry-points

   (5) 
https://setuptools.readthedocs.io/en/latest/pkg_resources.html#metadata-api

   (6) https://pypi.org/project/pip/

   (7) 
https://packaging.python.org/en/latest/specifications/core-metadata/#core-metadata

   (8) https://importlib-metadata.readthedocs.io/en/latest/api.html

   (9) 
https://importlib-metadata.readthedocs.io/en/latest/migration.html


File: python.info,  Node: Overview<2>,  Next: Functional API<2>,  Up: importlib metadata -- 存取套件的元資料

5.31.8.1 Overview
.................

Let's say you wanted to get the version string for a Distribution
Package(1) you've installed using ‘pip’.  We start by creating a virtual
environment and installing something into it:

     $ python -m venv example
     $ source example/bin/activate
     (example) $ python -m pip install wheel

You can get the version string for ‘wheel’ by running the following:

     (example) $ python
     >>> from importlib.metadata import version
     >>> version('wheel')
     '0.32.3'

You can also get a collection of entry points selectable by properties
of the EntryPoint (typically 'group' or 'name'), such as
‘console_scripts’, ‘distutils.commands’ and others.  Each group contains
a collection of *note EntryPoint: 267. objects.

You can get the *note metadata for a distribution: 437c.:

     >>> list(metadata('wheel'))
     ['Metadata-Version', 'Name', 'Version', 'Summary', 'Home-page', 'Author', 'Author-email', 'Maintainer', 'Maintainer-email', 'License', 'Project-URL', 'Project-URL', 'Project-URL', 'Keywords', 'Platform', 'Classifier', 'Classifier', 'Classifier', 'Classifier', 'Classifier', 'Classifier', 'Classifier', 'Classifier', 'Classifier', 'Classifier', 'Classifier', 'Classifier', 'Requires-Python', 'Provides-Extra', 'Requires-Dist', 'Requires-Dist']

You can also get a *note distribution's version number: 437d, list its
*note constituent files: 437e, and get a list of the distribution's
*note Distribution requirements: 437f.

   ---------- Footnotes ----------

   (1) 
https://packaging.python.org/en/latest/glossary/#term-Distribution-Package


File: python.info,  Node: Functional API<2>,  Next: Distributions,  Prev: Overview<2>,  Up: importlib metadata -- 存取套件的元資料

5.31.8.2 Functional API
.......................

This package provides the following functionality via its public API.

* Menu:

* Entry points::
* Distribution metadata::
* Distribution versions::
* Distribution files::
* Distribution requirements::
* Mapping import to distribution packages::


File: python.info,  Node: Entry points,  Next: Distribution metadata,  Up: Functional API<2>

5.31.8.3 Entry points
.....................

The ‘entry_points()’ function returns a collection of entry points.
Entry points are represented by ‘EntryPoint’ instances; each
‘EntryPoint’ has a ‘.name’, ‘.group’, and ‘.value’ attributes and a
‘.load()’ method to resolve the value.  There are also ‘.module’,
‘.attr’, and ‘.extras’ attributes for getting the components of the
‘.value’ attribute.

Query all entry points:

     >>> eps = entry_points()

The ‘entry_points()’ function returns an ‘EntryPoints’ object, a
collection of all ‘EntryPoint’ objects with ‘names’ and ‘groups’
attributes for convenience:

     >>> sorted(eps.groups)
     ['console_scripts', 'distutils.commands', 'distutils.setup_keywords', 'egg_info.writers', 'setuptools.installation']

‘EntryPoints’ has a ‘select’ method to select entry points matching
specific properties.  Select entry points in the ‘console_scripts’
group:

     >>> scripts = eps.select(group='console_scripts')

Equivalently, since ‘entry_points’ passes keyword arguments through to
select:

     >>> scripts = entry_points(group='console_scripts')

Pick out a specific script named "wheel" (found in the wheel project):

     >>> 'wheel' in scripts.names
     True
     >>> wheel = scripts['wheel']

Equivalently, query for that entry point during selection:

     >>> (wheel,) = entry_points(group='console_scripts', name='wheel')
     >>> (wheel,) = entry_points().select(group='console_scripts', name='wheel')

Inspect the resolved entry point:

     >>> wheel
     EntryPoint(name='wheel', value='wheel.cli:main', group='console_scripts')
     >>> wheel.module
     'wheel.cli'
     >>> wheel.attr
     'main'
     >>> wheel.extras
     []
     >>> main = wheel.load()
     >>> main
     <function main at 0x103528488>

The ‘group’ and ‘name’ are arbitrary values defined by the package
author and usually a client will wish to resolve all entry points for a
particular group.  Read the setuptools docs(1) for more information on
entry points, their definition, and usage.

在 3.12 版的變更: The "selectable" entry points were introduced in
‘importlib_metadata’ 3.6 and Python 3.10.  Prior to those changes,
‘entry_points’ accepted no parameters and always returned a dictionary
of entry points, keyed by group.  With ‘importlib_metadata’ 5.0 and
Python 3.12, ‘entry_points’ always returns an ‘EntryPoints’ object.  See
backports.entry_points_selectable(2) for compatibility options.

在 3.13 版的變更: ‘EntryPoint’ objects no longer present a tuple-like
interface (*note __getitem__(): 266.).

   ---------- Footnotes ----------

   (1) https://setuptools.pypa.io/en/latest/userguide/entry_point.html

   (2) https://pypi.org/project/backports.entry_points_selectable/


File: python.info,  Node: Distribution metadata,  Next: Distribution versions,  Prev: Entry points,  Up: Functional API<2>

5.31.8.4 Distribution metadata
..............................

Every Distribution Package(1) includes some metadata, which you can
extract using the ‘metadata()’ function:

     >>> wheel_metadata = metadata('wheel')

The keys of the returned data structure, a ‘PackageMetadata’, name the
metadata keywords, and the values are returned unparsed from the
distribution metadata:

     >>> wheel_metadata['Requires-Python']
     '>=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*'

‘PackageMetadata’ also presents a ‘json’ attribute that returns all the
metadata in a JSON-compatible form per PEP 566(2):

     >>> wheel_metadata.json['requires_python']
     '>=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*'

     備註: The actual type of the object returned by ‘metadata()’ is an
     implementation detail and should be accessed only through the
     interface described by the PackageMetadata protocol(3).

在 3.10 版的變更: The ‘Description’ is now included in the metadata when
presented through the payload.  Line continuation characters have been
removed.

新增 ‘json’ 屬性。

   ---------- Footnotes ----------

   (1) 
https://packaging.python.org/en/latest/glossary/#term-Distribution-Package

   (2) https://peps.python.org/pep-0566/

   (3) 
https://importlib-metadata.readthedocs.io/en/latest/api.html#importlib_metadata.PackageMetadata


File: python.info,  Node: Distribution versions,  Next: Distribution files,  Prev: Distribution metadata,  Up: Functional API<2>

5.31.8.5 Distribution versions
..............................

The ‘version()’ function is the quickest way to get a Distribution
Package(1)'s version number, as a string:

     >>> version('wheel')
     '0.32.3'

   ---------- Footnotes ----------

   (1) 
https://packaging.python.org/en/latest/glossary/#term-Distribution-Package


File: python.info,  Node: Distribution files,  Next: Distribution requirements,  Prev: Distribution versions,  Up: Functional API<2>

5.31.8.6 Distribution files
...........................

You can also get the full set of files contained within a distribution.
The ‘files()’ function takes a Distribution Package(1) name and returns
all of the files installed by this distribution.  Each file object
returned is a ‘PackagePath’, a *note pathlib.PurePath: 44e. derived
object with additional ‘dist’, ‘size’, and ‘hash’ properties as
indicated by the metadata.  For example:

     >>> util = [p for p in files('wheel') if 'util.py' in str(p)][0]
     >>> util
     PackagePath('wheel/util.py')
     >>> util.size
     859
     >>> util.dist
     <importlib.metadata._hooks.PathDistribution object at 0x101e0cef0>
     >>> util.hash
     <FileHash mode: sha256 value: bYkw5oMccfazVCoYQwKkkemoVyMAFoR34mmKBx8R1NI>

Once you have the file, you can also read its contents:

     >>> print(util.read_text())
     import base64
     import sys
     ...
     def as_bytes(s):
         if isinstance(s, text_type):
             return s.encode('utf-8')
         return s

You can also use the ‘locate’ method to get a the absolute path to the
file:

     >>> util.locate()
     PosixPath('/home/gustav/example/lib/site-packages/wheel/util.py')

In the case where the metadata file listing files (RECORD or
SOURCES.txt) is missing, ‘files()’ will return ‘None’.  The caller may
wish to wrap calls to ‘files()’ in always_iterable(2) or otherwise guard
against this condition if the target distribution is not known to have
the metadata present.

   ---------- Footnotes ----------

   (1) 
https://packaging.python.org/en/latest/glossary/#term-Distribution-Package

   (2) 
https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.always_iterable


File: python.info,  Node: Distribution requirements,  Next: Mapping import to distribution packages,  Prev: Distribution files,  Up: Functional API<2>

5.31.8.7 Distribution requirements
..................................

To get the full set of requirements for a Distribution Package(1), use
the ‘requires()’ function:

     >>> requires('wheel')
     ["pytest (>=3.0.0) ; extra == 'test'", "pytest-cov ; extra == 'test'"]

   ---------- Footnotes ----------

   (1) 
https://packaging.python.org/en/latest/glossary/#term-Distribution-Package


File: python.info,  Node: Mapping import to distribution packages,  Prev: Distribution requirements,  Up: Functional API<2>

5.31.8.8 Mapping import to distribution packages
................................................

A convenience method to resolve the Distribution Package(1) name (or
names, in the case of a namespace package) that provide each importable
top-level Python module or Import Package(2):

     >>> packages_distributions()
     {'importlib_metadata': ['importlib-metadata'], 'yaml': ['PyYAML'], 'jaraco': ['jaraco.classes', 'jaraco.functools'], ...}

Some editable installs, do not supply top-level names(3), and thus this
function is not reliable with such installs.

在 3.10 版被加入.

   ---------- Footnotes ----------

   (1) 
https://packaging.python.org/en/latest/glossary/#term-Distribution-Package

   (2) 
https://packaging.python.org/en/latest/glossary/#term-Import-Package

   (3) https://github.com/pypa/packaging-problems/issues/609


File: python.info,  Node: Distributions,  Next: Distribution Discovery,  Prev: Functional API<2>,  Up: importlib metadata -- 存取套件的元資料

5.31.8.9 Distributions
......................

While the above API is the most common and convenient usage, you can get
all of that information from the ‘Distribution’ class.  A ‘Distribution’
is an abstract object that represents the metadata for a Python
Distribution Package(1).  You can get the ‘Distribution’ instance:

     >>> from importlib.metadata import distribution
     >>> dist = distribution('wheel')

Thus, an alternative way to get the version number is through the
‘Distribution’ instance:

     >>> dist.version
     '0.32.3'

There are all kinds of additional metadata available on the
‘Distribution’ instance:

     >>> dist.metadata['Requires-Python']
     '>=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*'
     >>> dist.metadata['License']
     'MIT'

For editable packages, an ‘origin’ property may present PEP 610(2)
metadata:

     >>> dist.origin.url
     'file:///path/to/wheel-0.32.3.editable-py3-none-any.whl'

The full set of available metadata is not described here.  See the Core
metadata specifications(3) for additional details.

在 3.13 版被加入: The ‘.origin’ property was added.

   ---------- Footnotes ----------

   (1) 
https://packaging.python.org/en/latest/glossary/#term-Distribution-Package

   (2) https://peps.python.org/pep-0610/

   (3) 
https://packaging.python.org/en/latest/specifications/core-metadata/#core-metadata


File: python.info,  Node: Distribution Discovery,  Next: Extending the search algorithm,  Prev: Distributions,  Up: importlib metadata -- 存取套件的元資料

5.31.8.10 Distribution Discovery
................................

By default, this package provides built-in support for discovery of
metadata for file system and zip file Distribution Package(1)s.  This
metadata finder search defaults to ‘sys.path’, but varies slightly in
how it interprets those values from how other import machinery does.  In
particular:

   - ‘importlib.metadata’ does not honor *note bytes: 1a5. objects on
     ‘sys.path’.

   - ‘importlib.metadata’ will incidentally honor *note pathlib.Path:
     20e. objects on ‘sys.path’ even though such values will be ignored
     for imports.

   ---------- Footnotes ----------

   (1) 
https://packaging.python.org/en/latest/glossary/#term-Distribution-Package


File: python.info,  Node: Extending the search algorithm,  Prev: Distribution Discovery,  Up: importlib metadata -- 存取套件的元資料

5.31.8.11 Extending the search algorithm
........................................

Because Distribution Package(1) metadata is not available through *note
sys.path: 37f. searches, or package loaders directly, the metadata for a
distribution is found through import system *note finders: 1ec8.  To
find a distribution package's metadata, ‘importlib.metadata’ queries the
list of *note meta path finders: 1011. on *note sys.meta_path: cd2.

By default ‘importlib.metadata’ installs a finder for distribution
packages found on the file system.  This finder doesn't actually find
any 'distributions', but it can find their metadata.

The abstract class *note importlib.abc.MetaPathFinder: 813. defines the
interface expected of finders by Python's import system.
‘importlib.metadata’ extends this protocol by looking for an optional
‘find_distributions’ callable on the finders from *note sys.meta_path:
cd2. and presents this extended interface as the ‘DistributionFinder’
abstract base class, which defines this abstract method:

     @abc.abstractmethod
     def find_distributions(context=DistributionFinder.Context()):
         """Return an iterable of all Distribution instances capable of
         loading the metadata for packages for the indicated ``context``.
         """

The ‘DistributionFinder.Context’ object provides ‘.path’ and ‘.name’
properties indicating the path to search and name to match and may
supply other relevant context.

What this means in practice is that to support finding distribution
package metadata in locations other than the file system, subclass
‘Distribution’ and implement the abstract methods.  Then from a custom
finder, return instances of this derived ‘Distribution’ in the
‘find_distributions()’ method.

* Menu:

* Example::

   ---------- Footnotes ----------

   (1) 
https://packaging.python.org/en/latest/glossary/#term-Distribution-Package


File: python.info,  Node: Example,  Up: Extending the search algorithm

5.31.8.12 Example
.................

Consider for example a custom finder that loads Python modules from a
database:

     class DatabaseImporter(importlib.abc.MetaPathFinder):
         def __init__(self, db):
             self.db = db

         def find_spec(self, fullname, target=None) -> ModuleSpec:
             return self.db.spec_from_name(fullname)

     sys.meta_path.append(DatabaseImporter(connect_db(...)))

That importer now presumably provides importable modules from a
database, but it provides no metadata or entry points.  For this custom
importer to provide metadata, it would also need to implement
‘DistributionFinder’:

     from importlib.metadata import DistributionFinder

     class DatabaseImporter(DistributionFinder):
         ...

         def find_distributions(self, context=DistributionFinder.Context()):
             query = dict(name=context.name) if context.name else {}
             for dist_record in self.db.query_distributions(query):
                 yield DatabaseDistribution(dist_record)

In this way, ‘query_distributions’ would return records for each
distribution served by the database matching the query.  For example, if
‘requests-1.0’ is in the database, ‘find_distributions’ would yield a
‘DatabaseDistribution’ for ‘Context(name='requests')’ or
‘Context(name=None)’.

For the sake of simplicity, this example ignores ‘context.path’.  The
‘path’ attribute defaults to ‘sys.path’ and is the set of import paths
to be considered in the search.  A ‘DatabaseImporter’ could potentially
function without any concern for a search path.  Assuming the importer
does no partitioning, the "path" would be irrelevant.  In order to
illustrate the purpose of ‘path’, the example would need to illustrate a
more complex ‘DatabaseImporter’ whose behavior varied depending on
‘sys.path’/‘PYTHONPATH’.  In that case, the ‘find_distributions’ should
honor the ‘context.path’ and only yield ‘Distribution’s pertinent to
that path.

‘DatabaseDistribution’, then, would look something like:

     class DatabaseDistribution(importlib.metadata.Distributon):
         def __init__(self, record):
             self.record = record

         def read_text(self, filename):
             """
             Read a file like "METADATA" for the current distribution.
             """
             if filename == "METADATA":
                 return f"""Name: {self.record.name}
     Version: {self.record.version}
     """
             if filename == "entry_points.txt":
                 return "\n".join(
                   f"""[{ep.group}]\n{ep.name}={ep.value}"""
                   for ep in self.record.entry_points)

         def locate_file(self, path):
             raise RuntimeError("This distribution has no file system")

This basic implementation should provide metadata and entry points for
packages served by the ‘DatabaseImporter’, assuming that the ‘record’
supplies suitable ‘.name’, ‘.version’, and ‘.entry_points’ attributes.

The ‘DatabaseDistribution’ may also provide other metadata files, like
‘RECORD’ (required for ‘Distribution.files’) or override the
implementation of ‘Distribution.files’.  See the source for more
inspiration.


File: python.info,  Node: The initialization of the sys path module search path,  Prev: importlib metadata -- 存取套件的元資料,  Up: 引入模組

5.31.9 The initialization of the ‘sys.path’ module search path
--------------------------------------------------------------

A module search path is initialized when Python starts.  This module
search path may be accessed at *note sys.path: 37f.

The first entry in the module search path is the directory that contains
the input script, if there is one.  Otherwise, the first entry is the
current directory, which is the case when executing the interactive
shell, a *note -c: 584. command, or *note -m: 585. module.

The *note PYTHONPATH: fbe. environment variable is often used to add
directories to the search path.  If this environment variable is found
then the contents are added to the module search path.

     備註: *note PYTHONPATH: fbe. will affect all installed Python
     versions/environments.  Be wary of setting this in your shell
     profile or global environment variables.  The *note site: b5.
     module offers more nuanced techniques as mentioned below.

The next items added are the directories containing standard Python
modules as well as any *note extension module: 438e.s that these modules
depend on.  Extension modules are ‘.pyd’ files on Windows and ‘.so’
files on other platforms.  The directory with the platform-independent
Python modules is called ‘prefix’.  The directory with the extension
modules is called ‘exec_prefix’.

The *note PYTHONHOME: 387. environment variable may be used to set the
‘prefix’ and ‘exec_prefix’ locations.  Otherwise these directories are
found by using the Python executable as a starting point and then
looking for various 'landmark' files and directories.  Note that any
symbolic links are followed so the real Python executable location is
used as the search starting point.  The Python executable location is
called ‘home’.

Once ‘home’ is determined, the ‘prefix’ directory is found by first
looking for ‘python`majorversion'`minorversion'.zip’ (‘python311.zip’).
On Windows the zip archive is searched for in ‘home’ and on Unix the
archive is expected to be in ‘lib’.  Note that the expected zip archive
location is added to the module search path even if the archive does not
exist.  If no archive was found, Python on Windows will continue the
search for ‘prefix’ by looking for ‘Lib\os.py’.  Python on Unix will
look for ‘lib/python`majorversion'.`minorversion'/os.py’
(‘lib/python3.11/os.py’).  On Windows ‘prefix’ and ‘exec_prefix’ are the
same, however on other platforms
‘lib/python`majorversion'.`minorversion'/lib-dynload’
(‘lib/python3.11/lib-dynload’) is searched for and used as an anchor for
‘exec_prefix’.  On some platforms ‘lib’ may be ‘lib64’ or another value,
see *note sys.platlibdir: 8dc. and *note PYTHONPLATLIBDIR: 1842.

Once found, ‘prefix’ and ‘exec_prefix’ are available at *note
sys.prefix: 381. and *note sys.exec_prefix: 37d. respectively.

Finally, the *note site: b5. module is processed and ‘site-packages’
directories are added to the module search path.  A common way to
customize the search path is to create *note sitecustomize: b6. or *note
usercustomize: f7. modules as described in the *note site: b5. module
documentation.

     備註: Certain command line options may further affect path
     calculations.  See *note -E: 901, *note -I: 902, *note -s: 1319.
     and *note -S: 1140. for further details.

* Menu:

* Virtual environments::
* _pth files::
* Embedded Python::


File: python.info,  Node: Virtual environments,  Next: _pth files,  Up: The initialization of the sys path module search path

5.31.9.1 Virtual environments
.............................

If Python is run in a virtual environment (as described at *note
虛擬環境與套件: 1c01.) then ‘prefix’ and ‘exec_prefix’ are specific to
the virtual environment.

If a ‘pyvenv.cfg’ file is found alongside the main executable, or in the
directory one level above the executable, the following variations
apply:

   * If ‘home’ is an absolute path and *note PYTHONHOME: 387. is not
     set, this path is used instead of the path to the main executable
     when deducing ‘prefix’ and ‘exec_prefix’.


File: python.info,  Node: _pth files,  Next: Embedded Python,  Prev: Virtual environments,  Up: The initialization of the sys path module search path

5.31.9.2 _pth files
...................

To completely override *note sys.path: 37f. create a ‘._pth’ file with
the same name as the shared library or executable (‘python._pth’ or
‘python311._pth’).  The shared library path is always known on Windows,
however it may not be available on other platforms.  In the ‘._pth’ file
specify one line for each path to add to *note sys.path: 37f.  The file
based on the shared library name overrides the one based on the
executable, which allows paths to be restricted for any program loading
the runtime if desired.

When the file exists, all registry and environment variables are
ignored, isolated mode is enabled, and *note site: b5. is not imported
unless one line in the file specifies ‘import site’.  Blank paths and
lines starting with ‘#’ are ignored.  Each path may be absolute or
relative to the location of the file.  Import statements other than to
‘site’ are not permitted, and arbitrary code cannot be specified.

Note that ‘.pth’ files (without leading underscore) will be processed
normally by the *note site: b5. module when ‘import site’ has been
specified.


File: python.info,  Node: Embedded Python,  Prev: _pth files,  Up: The initialization of the sys path module search path

5.31.9.3 Embedded Python
........................

If Python is embedded within another application *note
Py_InitializeFromConfig(): 390. and the *note PyConfig: 371. structure
can be used to initialize Python.  The path specific details are
described at *note Python Path Configuration: 852.

也參考
......

   * *note 找尋模組: bc8. for detailed Windows notes.

   * *note 在 Unix 平臺上使用 Python: 1c5a. for Unix details.


File: python.info,  Node: Python 語言服務,  Next: MS Windows 特有服務,  Prev: 引入模組,  Up: Python 標準函式庫 Standard Library

5.32 Python 語言服務
====================

Python provides a number of modules to assist in working with the Python
language.  These modules support tokenizing, parsing, syntax analysis,
bytecode disassembly, and various other facilities.

這些模組包括：

* Menu:

* ast: ast --- 抽象語法樹 Abstract Syntax Trees. 抽象語法樹 (Abstract Syntax Trees)
* symtable: symtable --- 存取編譯器的符號表. 存取編譯器的符號表
* token: token --- 與 Python 剖析樹一起使用的常數. 與 Python 剖析樹一起使用的常數
* keyword: keyword --- 檢驗 Python 關鍵字. 檢驗 Python 關鍵字
* tokenize: tokenize --- Tokenizer for Python source. Tokenizer for Python source
* tabnanny: tabnanny --- 偵測不良縮排. 偵測不良縮排
* pyclbr: pyclbr --- Python 模組瀏覽器支援. Python 模組瀏覽器支援
* py_compile — 編譯 Python 來源檔案::
* compileall: compileall --- 位元組編譯 Python 函式庫. 位元組編譯 Python 函式庫
* dis: dis --- Python bytecode 的反組譯器. Python bytecode 的反組譯器
* pickletools: pickletools --- pickle 開發者的工具. pickle 開發者的工具


File: python.info,  Node: ast --- 抽象語法樹 Abstract Syntax Trees,  Next: symtable --- 存取編譯器的符號表,  Up: Python 語言服務

5.32.1 ‘ast’ -- 抽象語法樹 (Abstract Syntax Trees)
--------------------------------------------------

'原始碼：'Lib/ast.py(1)

__________________________________________________________________

*note ast: 7. 模組可以幫助 Python 應用程式處理 Python 抽象語法文法
(abstract syntax grammar) 樹狀資料結構。抽象語法本身可能會隨著每個
Python 版本發布而改變；此模組有助於以程式化的方式來得知當前文法的面貌。

要生成抽象語法樹，可以透過將 *note ast.PyCF_ONLY_AST: 4397. 作為旗標傳遞
給內建函式 *note compile(): 178. 或使用此模組所提供的 *note parse():
18e. 輔助函式。結果將會是一個物件的樹，其類別都繼承自 *note ast.AST:
18c.。可以使用內建的 *note compile(): 178. 函式將抽象語法樹編譯成 Python
程式碼物件。

* Menu:

* 抽象文法 (Abstract Grammar): 抽象文法 Abstract Grammar.
* 節點 (Node) 類別: 節點 Node 類別.
* ast 輔助程式::
* 編譯器旗標: 編譯器旗標<2>.
* 命令列用法: 命令列用法<3>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/ast.py


File: python.info,  Node: 抽象文法 Abstract Grammar,  Next: 節點 Node 類別,  Up: ast --- 抽象語法樹 Abstract Syntax Trees

5.32.1.1 抽象文法 (Abstract Grammar)
....................................

抽象文法目前定義如下：

     -- ASDL's 4 builtin types are:
     -- identifier, int, string, constant

     module Python
     {
         mod = Module(stmt* body, type_ignore* type_ignores)
             | Interactive(stmt* body)
             | Expression(expr body)
             | FunctionType(expr* argtypes, expr returns)

         stmt = FunctionDef(identifier name, arguments args,
                            stmt* body, expr* decorator_list, expr? returns,
                            string? type_comment, type_param* type_params)
               | AsyncFunctionDef(identifier name, arguments args,
                                  stmt* body, expr* decorator_list, expr? returns,
                                  string? type_comment, type_param* type_params)

               | ClassDef(identifier name,
                  expr* bases,
                  keyword* keywords,
                  stmt* body,
                  expr* decorator_list,
                  type_param* type_params)
               | Return(expr? value)

               | Delete(expr* targets)
               | Assign(expr* targets, expr value, string? type_comment)
               | TypeAlias(expr name, type_param* type_params, expr value)
               | AugAssign(expr target, operator op, expr value)
               -- 'simple' indicates that we annotate simple name without parens
               | AnnAssign(expr target, expr annotation, expr? value, int simple)

               -- use 'orelse' because else is a keyword in target languages
               | For(expr target, expr iter, stmt* body, stmt* orelse, string? type_comment)
               | AsyncFor(expr target, expr iter, stmt* body, stmt* orelse, string? type_comment)
               | While(expr test, stmt* body, stmt* orelse)
               | If(expr test, stmt* body, stmt* orelse)
               | With(withitem* items, stmt* body, string? type_comment)
               | AsyncWith(withitem* items, stmt* body, string? type_comment)

               | Match(expr subject, match_case* cases)

               | Raise(expr? exc, expr? cause)
               | Try(stmt* body, excepthandler* handlers, stmt* orelse, stmt* finalbody)
               | TryStar(stmt* body, excepthandler* handlers, stmt* orelse, stmt* finalbody)
               | Assert(expr test, expr? msg)

               | Import(alias* names)
               | ImportFrom(identifier? module, alias* names, int? level)

               | Global(identifier* names)
               | Nonlocal(identifier* names)
               | Expr(expr value)
               | Pass | Break | Continue

               -- col_offset is the byte offset in the utf8 string the parser uses
               attributes (int lineno, int col_offset, int? end_lineno, int? end_col_offset)

               -- BoolOp() can use left & right?
         expr = BoolOp(boolop op, expr* values)
              | NamedExpr(expr target, expr value)
              | BinOp(expr left, operator op, expr right)
              | UnaryOp(unaryop op, expr operand)
              | Lambda(arguments args, expr body)
              | IfExp(expr test, expr body, expr orelse)
              | Dict(expr* keys, expr* values)
              | Set(expr* elts)
              | ListComp(expr elt, comprehension* generators)
              | SetComp(expr elt, comprehension* generators)
              | DictComp(expr key, expr value, comprehension* generators)
              | GeneratorExp(expr elt, comprehension* generators)
              -- the grammar constrains where yield expressions can occur
              | Await(expr value)
              | Yield(expr? value)
              | YieldFrom(expr value)
              -- need sequences for compare to distinguish between
              -- x < 4 < 3 and (x < 4) < 3
              | Compare(expr left, cmpop* ops, expr* comparators)
              | Call(expr func, expr* args, keyword* keywords)
              | FormattedValue(expr value, int conversion, expr? format_spec)
              | JoinedStr(expr* values)
              | Constant(constant value, string? kind)

              -- the following expression can appear in assignment context
              | Attribute(expr value, identifier attr, expr_context ctx)
              | Subscript(expr value, expr slice, expr_context ctx)
              | Starred(expr value, expr_context ctx)
              | Name(identifier id, expr_context ctx)
              | List(expr* elts, expr_context ctx)
              | Tuple(expr* elts, expr_context ctx)

              -- can appear only in Subscript
              | Slice(expr? lower, expr? upper, expr? step)

               -- col_offset is the byte offset in the utf8 string the parser uses
               attributes (int lineno, int col_offset, int? end_lineno, int? end_col_offset)

         expr_context = Load | Store | Del

         boolop = And | Or

         operator = Add | Sub | Mult | MatMult | Div | Mod | Pow | LShift
                      | RShift | BitOr | BitXor | BitAnd | FloorDiv

         unaryop = Invert | Not | UAdd | USub

         cmpop = Eq | NotEq | Lt | LtE | Gt | GtE | Is | IsNot | In | NotIn

         comprehension = (expr target, expr iter, expr* ifs, int is_async)

         excepthandler = ExceptHandler(expr? type, identifier? name, stmt* body)
                         attributes (int lineno, int col_offset, int? end_lineno, int? end_col_offset)

         arguments = (arg* posonlyargs, arg* args, arg? vararg, arg* kwonlyargs,
                      expr* kw_defaults, arg? kwarg, expr* defaults)

         arg = (identifier arg, expr? annotation, string? type_comment)
                attributes (int lineno, int col_offset, int? end_lineno, int? end_col_offset)

         -- keyword arguments supplied to call (NULL identifier for **kwargs)
         keyword = (identifier? arg, expr value)
                    attributes (int lineno, int col_offset, int? end_lineno, int? end_col_offset)

         -- import name with optional 'as' alias.
         alias = (identifier name, identifier? asname)
                  attributes (int lineno, int col_offset, int? end_lineno, int? end_col_offset)

         withitem = (expr context_expr, expr? optional_vars)

         match_case = (pattern pattern, expr? guard, stmt* body)

         pattern = MatchValue(expr value)
                 | MatchSingleton(constant value)
                 | MatchSequence(pattern* patterns)
                 | MatchMapping(expr* keys, pattern* patterns, identifier? rest)
                 | MatchClass(expr cls, pattern* patterns, identifier* kwd_attrs, pattern* kwd_patterns)

                 | MatchStar(identifier? name)
                 -- The optional "rest" MatchMapping parameter handles capturing extra mapping keys

                 | MatchAs(pattern? pattern, identifier? name)
                 | MatchOr(pattern* patterns)

                  attributes (int lineno, int col_offset, int end_lineno, int end_col_offset)

         type_ignore = TypeIgnore(int lineno, string tag)

         type_param = TypeVar(identifier name, expr? bound, expr? default_value)
                    | ParamSpec(identifier name, expr? default_value)
                    | TypeVarTuple(identifier name, expr? default_value)
                    attributes (int lineno, int col_offset, int end_lineno, int end_col_offset)
     }


File: python.info,  Node: 節點 Node 類別,  Next: ast 輔助程式,  Prev: 抽象文法 Abstract Grammar,  Up: ast --- 抽象語法樹 Abstract Syntax Trees

5.32.1.2 節點 (Node) 類別
.........................

 -- 類別: ast.AST

     這是所有 AST 節點類別的基礎。實際的節點類別是衍生自
     ‘Parser/Python.asdl’ 檔案，該檔案在*note 上方: 4398. 重現。它們被定
     義於 ‘_ast’ 的 C 模組中，並於 *note ast: 7. 中重新匯出。

     抽象文法中為每個左側符號定義了一個類別（例如 ‘ast.stmt’ 或
     ‘ast.expr’）。此外，也為每個右側的建構函式 (constructor) 定義了一個
     類別；這些類別繼承自左側樹的類別。例如，*note ast.BinOp: 18d2. 繼承
     自 ‘ast.expr’。對於具有替代方案（即為「和 (sums)」）的生產規則，左
     側類別是抽象的：僅有特定建構函式節點的實例會被建立。

      -- 屬性: _fields

          Each concrete class has an attribute ‘_fields’ which gives the
          names of all child nodes.

          具體類別的每個實例對於每個子節點都有一個屬性，其型別如文法中所
          定義。例如，*note ast.BinOp: 18d2. 實例具有型別為 ‘ast.expr’ 的
          屬性 ‘left’。

          如果這些屬性在文法中被標記為可選（使用問號），則該值可能為
          ‘None’。如果屬性可以有零個或多個值（用星號標記），則這些值將表
          示為 Python 串列。使用 *note compile(): 178. 編譯 AST 時，所有
          可能的屬性都必須存在並且具有有效值。

      -- 屬性: _field_types

          The ‘_field_types’ attribute on each concrete class is a
          dictionary mapping field names (as also listed in *note
          _fields: 439b.) to their types.

               >>> ast.TypeVar._field_types
               {'name': <class 'str'>, 'bound': ast.expr | None, 'default_value': ast.expr | None}

          在 3.13 版被加入.

      -- 屬性: lineno
      -- 屬性: col_offset
      -- 屬性: end_lineno
      -- 屬性: end_col_offset

          ‘ast.expr’ 和 ‘ast.stmt’ 子類別的實例具有 *note lineno: 439c.、
          *note col_offset: 439d.、*note end_lineno: 439e. 和 *note
          end_col_offset: 439f. 屬性。*note lineno: 439c. 和 *note
          end_lineno: 439e. 是原始文本跨度 (source text span) 的第一個和
          最後一個列號（1-indexed，因此第一列號是 1）以及 *note
          col_offset: 439d. 和 *note end_col_offset: 439f. 是生成節點的
          第一個和最後一個標記對應的 UTF-8 位元組偏移量。會記錄 UTF-8 偏
          移量是因為剖析器 (parser) 內部使用 UTF-8。

          請注意，編譯器並不需要結束位置，因此其為可選的。結束偏移量在最
          後一個符號'之後'，例如可以使用 ‘source_line[node.col_offset :
          node.end_col_offset]’ 來獲取單列運算式節點 (expression node) 的
          原始片段。

     ‘ast.T’ 類別的建構函式按以下方式剖析其引數：

        * 如果有位置引數，則必須與 ‘T._fields’ 中的項目一樣多；它們將被
          賦値為這些名稱的屬性。

        * 如果有關鍵字引數，它們會將相同名稱的屬性設定為給定值。

     例如，要建立並填充 (populate) *note ast.UnaryOp: 43a0. 節點，你可以
     使用：

          node = ast.UnaryOp(ast.USub(), ast.Constant(5, lineno=0, col_offset=0),
                             lineno=0, col_offset=0)

     If a field that is optional in the grammar is omitted from the
     constructor, it defaults to ‘None’.  If a list field is omitted, it
     defaults to the empty list.  If a field of type ‘ast.expr_context’
     is omitted, it defaults to *note Load(): 18a.  If any other field
     is omitted, a *note DeprecationWarning: 18b. is raised and the AST
     node will not have this field.  In Python 3.15, this condition will
     raise an error.

在 3.8 版的變更: *note ast.Constant: 29a. 類別現在用於所有常數。

在 3.9 版的變更: 以它們的值表示簡單索引，擴充切片 (slice) 則以元組
(tuple) 表示。

在 3.8 版之後被棄用: 舊的類別 ‘ast.Num’、‘ast.Str’、‘ast.Bytes’、
‘ast.NameConstant’ 和 ‘ast.Ellipsis’ 仍然可用，但它們將在未來的 Python 釋
出版本中移除。與此同時，實例化它們將回傳不同類別的實例。

在 3.9 版之後被棄用: 舊的類別 ‘ast.Index’ 和 ‘ast.ExtSlice’ 仍然可用，但
它們將在未來的 Python 版本中刪除。同時，實例化它們會回傳不同類別的實例。

Deprecated since version 3.13, will be removed in version 3.15: Previous
versions of Python allowed the creation of AST nodes that were missing
required fields.  Similarly, AST node constructors allowed arbitrary
keyword arguments that were set as attributes of the AST node, even if
they did not match any of the fields of the AST node.  This behavior is
deprecated and will be removed in Python 3.15.

     備註: 這裡顯示的特定節點類別的描述最初是從出色的 Green Tree
     Snakes(1) 專案和所有貢獻者那裡改編而來的。

* Menu:

* 根節點::
* 文本 (Literals): 文本 Literals.
* 變數::
* 運算式: 運算式<2>.
* 陳述式::
* 流程控制::
* 模式匹配 (pattern matching): 模式匹配 pattern matching.
* 型別參數 (type parameters): 型別參數 type parameters.
* 函式和類別定義::
* async 和 await::

   ---------- Footnotes ----------

   (1) https://greentreesnakes.readthedocs.io/en/latest/


File: python.info,  Node: 根節點,  Next: 文本 Literals,  Up: 節點 Node 類別

5.32.1.3 根節點
...............

 -- 類別: ast.Module (body, type_ignores)

     一個 Python 模組，與*note 檔案輸入: 2016. 一樣。由 *note
     ast.parse(): 18e. 在預設的 ‘"exec"’ 'mode' 下生成的節點型別。

     'body' 是模組的*note 陳述式: 43a4. 的一個 *note list: 5b6.。

     'type_ignores' 是模組的忽略型別註解的 *note list: 5b6.；有關更多詳
     細資訊，請參閱 *note ast.parse(): 18e.。

          >>> print(ast.dump(ast.parse('x = 1'), indent=4))
          Module(
              body=[
                  Assign(
                      targets=[
                          Name(id='x', ctx=Store())],
                      value=Constant(value=1))])

 -- 類別: ast.Expression (body)

     單個 Python *note 運算式輸入: 201c.。當 'mode' 是 ‘"eval"’ 時節點型
     別由 *note ast.parse(): 18e. 生成。

     'body' 是單個節點，是*note 運算式型別: 43a6.的其中之一。

          >>> print(ast.dump(ast.parse('123', mode='eval'), indent=4))
          Expression(
              body=Constant(value=123))

 -- 類別: ast.Interactive (body)

     單個*note 互動式輸入: 2019.，和*note 互動模式: 153.中所述的相似。當
     'mode' 是 ‘"single"’ 時節點型別由 *note ast.parse(): 18e. 生成。

     'body' 是*note 陳述式節點 (statement nodes): 43a4. 的 *note list:
     5b6.。

          >>> print(ast.dump(ast.parse('x = 1; y = 2', mode='single'), indent=4))
          Interactive(
              body=[
                  Assign(
                      targets=[
                          Name(id='x', ctx=Store())],
                      value=Constant(value=1)),
                  Assign(
                      targets=[
                          Name(id='y', ctx=Store())],
                      value=Constant(value=2))])

 -- 類別: ast.FunctionType (argtypes, returns)

     函式的舊式型別註解的表示法，因為 3.5 之前的 Python 版本不支援 PEP
     484(1) 註釋。當 'mode' 是 ‘"func_type"’ 時節點型別由 *note
     ast.parse(): 18e. 生成。

     這種型別的註解看起來像這樣：

          def sum_two_number(a, b):
              # type: (int, int) -> int
              return a + b

     'argtypes' 是*note 運算式節點: 43a6.的 *note list: 5b6.。

     'returns' 是單個*note 運算式節點: 43a6.。

          >>> print(ast.dump(ast.parse('(int, str) -> List[int]', mode='func_type'), indent=4))
          FunctionType(
              argtypes=[
                  Name(id='int', ctx=Load()),
                  Name(id='str', ctx=Load())],
              returns=Subscript(
                  value=Name(id='List', ctx=Load()),
                  slice=Name(id='int', ctx=Load()),
                  ctx=Load()))

     在 3.8 版被加入.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0484/


File: python.info,  Node: 文本 Literals,  Next: 變數,  Prev: 根節點,  Up: 節點 Node 類別

5.32.1.4 文本 (Literals)
........................

 -- 類別: ast.Constant (value)

     一個常數值。‘Constant’ 文本的 ‘value’ 屬性包含它所代表的 Python 物
     件。表示的值可以是簡單型別，例如數字、字串或 ‘None’，但如果它們的所
     有元素都是常數，也可以是不可變的 (immutable) 容器型別（元組和凍結集
     合 (frozensets)）。

          >>> print(ast.dump(ast.parse('123', mode='eval'), indent=4))
          Expression(
              body=Constant(value=123))

 -- 類別: ast.FormattedValue (value, conversion, format_spec)

     表示 f 字串 (f-string) 中的單個格式化欄位的節點。如果字串包含單個格
     式欄位並且沒有其他內容，則可以隔離 (isolate) 該節點，否則它將出現在
     *note JoinedStr: 15e5. 中。

        * ‘value’ 為任何運算式節點（例如文字、變數或函式呼叫）。

        * ‘conversion’ 是一個整數：

             * -1: 無格式化

             * 115: ‘!s’ 字串格式化

             * 114:‘!r’ 重複格式化化

             * 97: ‘！a’ ascii 格式化

        * ‘format_spec’ 是一個 *note JoinedStr: 15e5. 節點，表示值的格式
          ，若未指定格式則為 ‘None’。‘conversion’ 和 ‘format_spec’ 可以
          同時設定。

 -- 類別: ast.JoinedStr (values)

     一個 f 字串，包含一系列 *note FormattedValue: 43aa. 和 *note
     Constant: 29a. 節點。

          >>> print(ast.dump(ast.parse('f"sin({a}) is {sin(a):.3}"', mode='eval'), indent=4))
          Expression(
              body=JoinedStr(
                  values=[
                      Constant(value='sin('),
                      FormattedValue(
                          value=Name(id='a', ctx=Load()),
                          conversion=-1),
                      Constant(value=') is '),
                      FormattedValue(
                          value=Call(
                              func=Name(id='sin', ctx=Load()),
                              args=[
                                  Name(id='a', ctx=Load())]),
                          conversion=-1,
                          format_spec=JoinedStr(
                              values=[
                                  Constant(value='.3')]))]))

 -- 類別: ast.List (elts, ctx)
 -- 類別: ast.Tuple (elts, ctx)

     串列或元組。‘elts’ 保存表示元素的節點串列。如果容器是賦值目標（即
     ‘(x,y)=something’ ），則 ‘ctx’ 是 *note Store: 43ad.，否則是 *note
     Load: 18a.。

          >>> print(ast.dump(ast.parse('[1, 2, 3]', mode='eval'), indent=4))
          Expression(
              body=List(
                  elts=[
                      Constant(value=1),
                      Constant(value=2),
                      Constant(value=3)],
                  ctx=Load()))
          >>> print(ast.dump(ast.parse('(1, 2, 3)', mode='eval'), indent=4))
          Expression(
              body=Tuple(
                  elts=[
                      Constant(value=1),
                      Constant(value=2),
                      Constant(value=3)],
                  ctx=Load()))

 -- 類別: ast.Set (elts)

     一個集合。‘elts’ 保存表示集合之元素的節點串列。

          >>> print(ast.dump(ast.parse('{1, 2, 3}', mode='eval'), indent=4))
          Expression(
              body=Set(
                  elts=[
                      Constant(value=1),
                      Constant(value=2),
                      Constant(value=3)]))

 -- 類別: ast.Dict (keys, values)

     一個字典 (dictionary)。‘keys’ 和 ‘values’ 分別按匹配順序保存表示鍵
     和值的節點串列（為呼叫 ‘dictionary.keys()’ 和 ‘dictionary.values()’
     時將回傳的內容）。

     當使用字典文本進行字典解包 (unpack) 時，要擴充的運算式位於 ‘values’
     串列中，在 ‘keys’ 中的相應位置有一個 ‘None’。

          >>> print(ast.dump(ast.parse('{"a":1, **d}', mode='eval'), indent=4))
          Expression(
              body=Dict(
                  keys=[
                      Constant(value='a'),
                      None],
                  values=[
                      Constant(value=1),
                      Name(id='d', ctx=Load())]))


File: python.info,  Node: 變數,  Next: 運算式<2>,  Prev: 文本 Literals,  Up: 節點 Node 類別

5.32.1.5 變數
.............

 -- 類別: ast.Name (id, ctx)

     一個變數名稱。‘id’ 將名稱以字串形式保存，且 ‘ctx’ 是以下型別之一。

 -- 類別: ast.Load
 -- 類別: ast.Store
 -- 類別: ast.Del

     變數參照可用於載入變數的值、為其分配新值或刪除它。變數參照被賦予情
     境 (context) 來區分這些情況。

          >>> print(ast.dump(ast.parse('a'), indent=4))
          Module(
              body=[
                  Expr(
                      value=Name(id='a', ctx=Load()))])

          >>> print(ast.dump(ast.parse('a = 1'), indent=4))
          Module(
              body=[
                  Assign(
                      targets=[
                          Name(id='a', ctx=Store())],
                      value=Constant(value=1))])

          >>> print(ast.dump(ast.parse('del a'), indent=4))
          Module(
              body=[
                  Delete(
                      targets=[
                          Name(id='a', ctx=Del())])])

 -- 類別: ast.Starred (value, ctx)

     一個 ‘*var’ 變數參照。‘value’ 保存變數，通常是一個 *note Name:
     1841. 節點。在使用 ‘*args’ 建置 *note Call: 43b2. 節點時必須使用此
     型別。

          >>> print(ast.dump(ast.parse('a, *b = it'), indent=4))
          Module(
              body=[
                  Assign(
                      targets=[
                          Tuple(
                              elts=[
                                  Name(id='a', ctx=Store()),
                                  Starred(
                                      value=Name(id='b', ctx=Store()),
                                      ctx=Store())],
                              ctx=Store())],
                      value=Name(id='it', ctx=Load()))])


File: python.info,  Node: 運算式<2>,  Next: 陳述式,  Prev: 變數,  Up: 節點 Node 類別

5.32.1.6 運算式
...............

 -- 類別: ast.Expr (value)

     當運算式（例如函式呼叫）本身作為陳述式出現且未使用或儲存其回傳值時
     ，它將被包裝在此容器中。‘value’ 保存此區段 (section) 中的一個其他節
     點：*note Constant: 29a.、*note Name: 1841.、*note Lambda: 43b5.、
     *note Yield: 43b6. 或 *note YieldFrom: 43b7.

          >>> print(ast.dump(ast.parse('-a'), indent=4))
          Module(
              body=[
                  Expr(
                      value=UnaryOp(
                          op=USub(),
                          operand=Name(id='a', ctx=Load())))])

 -- 類別: ast.UnaryOp (op, operand)

     一元運算 (unary operation)。‘op’ 是運算子，‘operand’ 是任何運算式節
     點。

 -- 類別: ast.UAdd
 -- 類別: ast.USub
 -- 類別: ast.Not
 -- 類別: ast.Invert

     一元運算子標記。 *note Not: 43ba. 是 ‘not’ 關鍵字、*note Invert:
     43bb. 是 ‘~’ 運算子。

          >>> print(ast.dump(ast.parse('not x', mode='eval'), indent=4))
          Expression(
              body=UnaryOp(
                  op=Not(),
                  operand=Name(id='x', ctx=Load())))

 -- 類別: ast.BinOp (left, op, right)

     二元運算 (binary operation)（如加法或除法）。 ‘op’ 是運算子、‘left’
     和 ‘right’ 是任意運算式節點。

          >>> print(ast.dump(ast.parse('x + y', mode='eval'), indent=4))
          Expression(
              body=BinOp(
                  left=Name(id='x', ctx=Load()),
                  op=Add(),
                  right=Name(id='y', ctx=Load())))

 -- 類別: ast.Add
 -- 類別: ast.Sub
 -- 類別: ast.Mult
 -- 類別: ast.Div
 -- 類別: ast.FloorDiv
 -- 類別: ast.Mod
 -- 類別: ast.Pow
 -- 類別: ast.LShift
 -- 類別: ast.RShift
 -- 類別: ast.BitOr
 -- 類別: ast.BitXor
 -- 類別: ast.BitAnd
 -- 類別: ast.MatMult

     二元運算子 token。

 -- 類別: ast.BoolOp (op, values)

     布林運算 'or' 或 'and'。‘op’ 是 *note Or: 43ca. 或 *note And:
     43cb.。‘values’ 是有所涉及的值。使用同一運算子的連續操作（例如 ‘a
     or b or c’）會被折疊為具有多個值的一個節點。

     這不包括 ‘not’，它是一個 *note UnaryOp: 43a0.。

          >>> print(ast.dump(ast.parse('x or y', mode='eval'), indent=4))
          Expression(
              body=BoolOp(
                  op=Or(),
                  values=[
                      Name(id='x', ctx=Load()),
                      Name(id='y', ctx=Load())]))

 -- 類別: ast.And
 -- 類別: ast.Or

     布林運算子 token。

 -- 類別: ast.Compare (left, ops, comparators)

     兩個或多個值的比較。‘left’ 是比較中的第一個值、‘ops’ 是運算子串列、
     ‘comparators’ 是要比較的第一個元素之後值的串列。

          >>> print(ast.dump(ast.parse('1 <= a < 10', mode='eval'), indent=4))
          Expression(
              body=Compare(
                  left=Constant(value=1),
                  ops=[
                      LtE(),
                      Lt()],
                  comparators=[
                      Name(id='a', ctx=Load()),
                      Constant(value=10)]))

 -- 類別: ast.Eq
 -- 類別: ast.NotEq
 -- 類別: ast.Lt
 -- 類別: ast.LtE
 -- 類別: ast.Gt
 -- 類別: ast.GtE
 -- 類別: ast.Is
 -- 類別: ast.IsNot
 -- 類別: ast.In
 -- 類別: ast.NotIn

     比較運算子 token。

 -- 類別: ast.Call (func, args, keywords)

     一個函式呼叫。‘func’ 是該函式，通常是一個 *note Name: 1841. 或
     *note Attribute: 43d7. 物件。而在引數中：

        * ‘args’ 保存按位置傳遞的引數串列。

        * ‘keywords’ 保存一個 *note keyword: 43d8. 物件串列，表示透過關
          鍵字傳遞的引數。

     The ‘args’ and ‘keywords’ arguments are optional and default to
     empty lists.

          >>> print(ast.dump(ast.parse('func(a, b=c, *d, **e)', mode='eval'), indent=4))
          Expression(
              body=Call(
                  func=Name(id='func', ctx=Load()),
                  args=[
                      Name(id='a', ctx=Load()),
                      Starred(
                          value=Name(id='d', ctx=Load()),
                          ctx=Load())],
                  keywords=[
                      keyword(
                          arg='b',
                          value=Name(id='c', ctx=Load())),
                      keyword(
                          value=Name(id='e', ctx=Load()))]))

 -- 類別: ast.keyword (arg, value)

     函式呼叫或類別定義的關鍵字引數。‘arg’ 是參數名稱的原始字串，‘value’
     是要傳入的節點。

 -- 類別: ast.IfExp (test, body, orelse)

     像是 ‘a if b else c’ 之類的運算式。每個欄位都保存一個節點，因此在以
     下範例中，所有三個都是 *note Name: 1841. 節點。

          >>> print(ast.dump(ast.parse('a if b else c', mode='eval'), indent=4))
          Expression(
              body=IfExp(
                  test=Name(id='b', ctx=Load()),
                  body=Name(id='a', ctx=Load()),
                  orelse=Name(id='c', ctx=Load())))

 -- 類別: ast.Attribute (value, attr, ctx)

     屬性的存取，例如 ‘d.keys’。‘value’ 是一個節點，通常是一個 *note
     Name: 1841.。‘attr’ 是一個屬性名稱的字串，‘ctx’ 根據屬性的作用方式
     可能是 *note Load: 18a.、*note Store: 43ad. 或 *note Del: 43b0.。

          >>> print(ast.dump(ast.parse('snake.colour', mode='eval'), indent=4))
          Expression(
              body=Attribute(
                  value=Name(id='snake', ctx=Load()),
                  attr='colour',
                  ctx=Load()))

 -- 類別: ast.NamedExpr (target, value)

     一個附名運算式 (named expression)。該 AST 節點由賦值運算式運算子（
     也稱為海象運算子）產生。相對於 *note Assign: 43db. 節點之第一個引數
     可為多個節點，在這種情況下 ‘target’ 和 ‘value’ 都必須是單個節點。

          >>> print(ast.dump(ast.parse('(x := 4)', mode='eval'), indent=4))
          Expression(
              body=NamedExpr(
                  target=Name(id='x', ctx=Store()),
                  value=Constant(value=4)))

     在 3.8 版被加入.

* Menu:

* 下標 (Subscripting): 下標 Subscripting.
* 綜合運算式 (comprehensions): 綜合運算式 comprehensions.


File: python.info,  Node: 下標 Subscripting,  Next: 綜合運算式 comprehensions,  Up: 運算式<2>

5.32.1.7 下標 (Subscripting)
............................

 -- 類別: ast.Subscript (value, slice, ctx)

     一個下標，例如 ‘l[1]’。‘value’ 是下標物件（通常是序列或對映）。
     ‘slice’ 是索引、切片或鍵。它可以是一個 *note Tuple: 43ac. 並包含一
     個 *note Slice: 43de.。根據下標執行的操作不同，‘ctx’ 可以是 *note
     Load: 18a.、*note Store: 43ad. 或 *note Del: 43b0.。

          >>> print(ast.dump(ast.parse('l[1:2, 3]', mode='eval'), indent=4))
          Expression(
              body=Subscript(
                  value=Name(id='l', ctx=Load()),
                  slice=Tuple(
                      elts=[
                          Slice(
                              lower=Constant(value=1),
                              upper=Constant(value=2)),
                          Constant(value=3)],
                      ctx=Load()),
                  ctx=Load()))

 -- 類別: ast.Slice (lower, upper, step)

     常規切片（形式為 ‘lower:upper’ 或 ‘lower:upper:step’）。只能直接或
     者或者作為 *note Tuple: 43ac. 的元素出現在 *note Subscript: 43dd. 的
     'slice' 欄位內。

          >>> print(ast.dump(ast.parse('l[1:2]', mode='eval'), indent=4))
          Expression(
              body=Subscript(
                  value=Name(id='l', ctx=Load()),
                  slice=Slice(
                      lower=Constant(value=1),
                      upper=Constant(value=2)),
                  ctx=Load()))


File: python.info,  Node: 綜合運算式 comprehensions,  Prev: 下標 Subscripting,  Up: 運算式<2>

5.32.1.8 綜合運算式 (comprehensions)
....................................

 -- 類別: ast.ListComp (elt, generators)
 -- 類別: ast.SetComp (elt, generators)
 -- 類別: ast.GeneratorExp (elt, generators)
 -- 類別: ast.DictComp (key, value, generators)

     串列和集合綜合運算、生成器運算式和字典綜合運算。‘elt’（或 ‘key’ 和
     ‘value’）是單個節點，表示各個項目會被求值 (evaluate) 的部分。

     ‘generators’ 是一個 *note comprehension: 43e4. 節點的串列。

          >>> print(ast.dump(
          ...     ast.parse('[x for x in numbers]', mode='eval'),
          ...     indent=4,
          ... ))
          Expression(
              body=ListComp(
                  elt=Name(id='x', ctx=Load()),
                  generators=[
                      comprehension(
                          target=Name(id='x', ctx=Store()),
                          iter=Name(id='numbers', ctx=Load()),
                          is_async=0)]))
          >>> print(ast.dump(
          ...     ast.parse('{x: x**2 for x in numbers}', mode='eval'),
          ...     indent=4,
          ... ))
          Expression(
              body=DictComp(
                  key=Name(id='x', ctx=Load()),
                  value=BinOp(
                      left=Name(id='x', ctx=Load()),
                      op=Pow(),
                      right=Constant(value=2)),
                  generators=[
                      comprehension(
                          target=Name(id='x', ctx=Store()),
                          iter=Name(id='numbers', ctx=Load()),
                          is_async=0)]))
          >>> print(ast.dump(
          ...     ast.parse('{x for x in numbers}', mode='eval'),
          ...     indent=4,
          ... ))
          Expression(
              body=SetComp(
                  elt=Name(id='x', ctx=Load()),
                  generators=[
                      comprehension(
                          target=Name(id='x', ctx=Store()),
                          iter=Name(id='numbers', ctx=Load()),
                          is_async=0)]))

 -- 類別: ast.comprehension (target, iter, ifs, is_async)

     綜合運算中的一個 ‘for’ 子句。‘target’ 是用於每個元素的參照 - 通常是
     *note Name: 1841. 或 *note Tuple: 43ac. 節點。‘iter’ 是要疊代的物件
     。‘ifs’ 是測試運算式的串列：每個 ‘for’ 子句可以有多個 ‘ifs’。

     ‘is_async’ 表示綜合運算式是非同步的（使用 ‘async for’ 而不是 ‘for’
     ）。該值為整數（0 或 1）。

          >>> print(ast.dump(ast.parse('[ord(c) for line in file for c in line]', mode='eval'),
          ...                indent=4)) # Multiple comprehensions in one.
          Expression(
              body=ListComp(
                  elt=Call(
                      func=Name(id='ord', ctx=Load()),
                      args=[
                          Name(id='c', ctx=Load())]),
                  generators=[
                      comprehension(
                          target=Name(id='line', ctx=Store()),
                          iter=Name(id='file', ctx=Load()),
                          is_async=0),
                      comprehension(
                          target=Name(id='c', ctx=Store()),
                          iter=Name(id='line', ctx=Load()),
                          is_async=0)]))

          >>> print(ast.dump(ast.parse('(n**2 for n in it if n>5 if n<10)', mode='eval'),
          ...                indent=4)) # generator comprehension
          Expression(
              body=GeneratorExp(
                  elt=BinOp(
                      left=Name(id='n', ctx=Load()),
                      op=Pow(),
                      right=Constant(value=2)),
                  generators=[
                      comprehension(
                          target=Name(id='n', ctx=Store()),
                          iter=Name(id='it', ctx=Load()),
                          ifs=[
                              Compare(
                                  left=Name(id='n', ctx=Load()),
                                  ops=[
                                      Gt()],
                                  comparators=[
                                      Constant(value=5)]),
                              Compare(
                                  left=Name(id='n', ctx=Load()),
                                  ops=[
                                      Lt()],
                                  comparators=[
                                      Constant(value=10)])],
                          is_async=0)]))

          >>> print(ast.dump(ast.parse('[i async for i in soc]', mode='eval'),
          ...                indent=4)) # Async comprehension
          Expression(
              body=ListComp(
                  elt=Name(id='i', ctx=Load()),
                  generators=[
                      comprehension(
                          target=Name(id='i', ctx=Store()),
                          iter=Name(id='soc', ctx=Load()),
                          is_async=1)]))


File: python.info,  Node: 陳述式,  Next: 流程控制,  Prev: 運算式<2>,  Up: 節點 Node 類別

5.32.1.9 陳述式
...............

 -- 類別: ast.Assign (targets, value, type_comment)

     一個賦值。‘targets’ 是節點串列，‘value’ 是單個節點。

     ‘targets’ 中的多個節點表示為每個節點分配相同的值。解包是透過在
     ‘targets’ 中放置一個 *note Tuple: 43ac. 或 *note List: 43ab. 來表示
     的。

      -- 屬性: type_comment

          ‘type_comment’ 是一個可選字串，其中的註解為型別註釋。

          >>> print(ast.dump(ast.parse('a = b = 1'), indent=4)) # Multiple assignment
          Module(
              body=[
                  Assign(
                      targets=[
                          Name(id='a', ctx=Store()),
                          Name(id='b', ctx=Store())],
                      value=Constant(value=1))])

          >>> print(ast.dump(ast.parse('a,b = c'), indent=4)) # Unpacking
          Module(
              body=[
                  Assign(
                      targets=[
                          Tuple(
                              elts=[
                                  Name(id='a', ctx=Store()),
                                  Name(id='b', ctx=Store())],
                              ctx=Store())],
                      value=Name(id='c', ctx=Load()))])

 -- 類別: ast.AnnAssign (target, annotation, value, simple)

     帶有型別註釋的賦值。‘target’ 是單個節點，可以是 *note Name: 1841.、
     *note Attribute: 43d7. 或 *note Subscript: 43dd.。‘annotation’ 是註
     釋，例如 *note Constant: 29a. 或 *note Name: 1841. 節點。‘value’ 是
     單個可選節點。

     ‘simple’ 總會是 0（表示一個「複雜」目標）或 1（表示一個「簡單」目標
     ）。一個「簡單」目標僅包含一個 *note Name: 1841. 節點，且不出現在括
     號之間；所有其他目標都被視為是複雜的。只有簡單目標會出現在模組和類
     別的 ‘__annotations__’ 字典中。

          >>> print(ast.dump(ast.parse('c: int'), indent=4))
          Module(
              body=[
                  AnnAssign(
                      target=Name(id='c', ctx=Store()),
                      annotation=Name(id='int', ctx=Load()),
                      simple=1)])

          >>> print(ast.dump(ast.parse('(a): int = 1'), indent=4)) # Annotation with parenthesis
          Module(
              body=[
                  AnnAssign(
                      target=Name(id='a', ctx=Store()),
                      annotation=Name(id='int', ctx=Load()),
                      value=Constant(value=1),
                      simple=0)])

          >>> print(ast.dump(ast.parse('a.b: int'), indent=4)) # Attribute annotation
          Module(
              body=[
                  AnnAssign(
                      target=Attribute(
                          value=Name(id='a', ctx=Load()),
                          attr='b',
                          ctx=Store()),
                      annotation=Name(id='int', ctx=Load()),
                      simple=0)])

          >>> print(ast.dump(ast.parse('a[1]: int'), indent=4)) # Subscript annotation
          Module(
              body=[
                  AnnAssign(
                      target=Subscript(
                          value=Name(id='a', ctx=Load()),
                          slice=Constant(value=1),
                          ctx=Store()),
                      annotation=Name(id='int', ctx=Load()),
                      simple=0)])

 -- 類別: ast.AugAssign (target, op, value)

     增加賦值 (augmented assignment)，例如 ‘a += 1’。在下面的範例中，
     ‘target’ 是 ‘x’ 的 *note Name: 1841. 節點（帶有 *note Store: 43ad.
     情境），‘op’ 是 *note Add: 43bc.，‘value’ 是一個值為 1 的 *note
     Constant: 29a.。

     與 *note Assign: 43db. 的目標不同，‘target’ 屬性不能屬於 *note
     Tuple: 43ac. 或 *note List: 43ab. 類別。

          >>> print(ast.dump(ast.parse('x += 2'), indent=4))
          Module(
              body=[
                  AugAssign(
                      target=Name(id='x', ctx=Store()),
                      op=Add(),
                      value=Constant(value=2))])

 -- 類別: ast.Raise (exc, cause)

     一個 ‘raise’ 陳述式。‘exc’ 是要引發的例外物件，通常是 *note Call:
     43b2. 或 *note Name: 1841.，若是獨立的 ‘raise’ 則為 ‘None’。‘cause’
     是 ‘raise x from y’ 中的可選部分 ‘y’。

          >>> print(ast.dump(ast.parse('raise x from y'), indent=4))
          Module(
              body=[
                  Raise(
                      exc=Name(id='x', ctx=Load()),
                      cause=Name(id='y', ctx=Load()))])

 -- 類別: ast.Assert (test, msg)

     一個斷言 (assertion)。‘test’ 保存條件，例如 *note Compare: 43cc. 節
     點。‘msg’ 保存失敗訊息。

          >>> print(ast.dump(ast.parse('assert x,y'), indent=4))
          Module(
              body=[
                  Assert(
                      test=Name(id='x', ctx=Load()),
                      msg=Name(id='y', ctx=Load()))])

 -- 類別: ast.Delete (targets)

     代表一個 ‘del’ 陳述式。‘targets’ 是節點串列，例如 *note Name:
     1841.、*note Attribute: 43d7. 或 *note Subscript: 43dd. 節點。

          >>> print(ast.dump(ast.parse('del x,y,z'), indent=4))
          Module(
              body=[
                  Delete(
                      targets=[
                          Name(id='x', ctx=Del()),
                          Name(id='y', ctx=Del()),
                          Name(id='z', ctx=Del())])])

 -- 類別: ast.Pass

     一個 ‘pass’ 陳述式。

          >>> print(ast.dump(ast.parse('pass'), indent=4))
          Module(
              body=[
                  Pass()])

 -- 類別: ast.TypeAlias (name, type_params, value)

     透過 *note type: 3de. 陳述式建立的*note 型別別名 (type alias):
     3fa.。‘name’ 是別名的名稱、‘type_params’ 是*note 型別參數 (type
     parameter): 43ed. 的串列、‘value’ 是型別別名的值。

          >>> print(ast.dump(ast.parse('type Alias = int'), indent=4))
          Module(
              body=[
                  TypeAlias(
                      name=Name(id='Alias', ctx=Store()),
                      value=Name(id='int', ctx=Load()))])

     在 3.12 版被加入.

其他僅適用於函式或迴圈內部的陳述式將在其他部分中描述。

* Menu:

* 引入 (imports): 引入 imports.


File: python.info,  Node: 引入 imports,  Up: 陳述式

5.32.1.10 引入 (imports)
........................

 -- 類別: ast.Import (names)

     一個 import 陳述式。‘names’ 是 *note alias: 17c1. 節點的串列。

          >>> print(ast.dump(ast.parse('import x,y,z'), indent=4))
          Module(
              body=[
                  Import(
                      names=[
                          alias(name='x'),
                          alias(name='y'),
                          alias(name='z')])])

 -- 類別: ast.ImportFrom (module, names, level)

     代表 ‘from x import y’。‘module’ 是 'from' 名稱的原始字串，前面沒有
     任何的點 (dot)，或者對於諸如 ‘from . import foo’ 之類的陳述式則為
     ‘None’。‘level’ 是一個整數，保存相對引入的級別（0 表示絕對引入）。

          >>> print(ast.dump(ast.parse('from y import x,y,z'), indent=4))
          Module(
              body=[
                  ImportFrom(
                      module='y',
                      names=[
                          alias(name='x'),
                          alias(name='y'),
                          alias(name='z')],
                      level=0)])

 -- 類別: ast.alias (name, asname)

     這兩個參數都是名稱的原始字串。如果要使用常規名稱，‘asname’ 可以為
     ‘None’。

          >>> print(ast.dump(ast.parse('from ..foo.bar import a as b, c'), indent=4))
          Module(
              body=[
                  ImportFrom(
                      module='foo.bar',
                      names=[
                          alias(name='a', asname='b'),
                          alias(name='c')],
                      level=2)])


File: python.info,  Node: 流程控制,  Next: 模式匹配 pattern matching,  Prev: 陳述式,  Up: 節點 Node 類別

5.32.1.11 流程控制
..................

     備註: 諸如 ‘else’ 之類的可選子句如果不存在，則將被儲存為空串列。

 -- 類別: ast.If (test, body, orelse)

     一個 ‘if’ 陳述式。‘test’ 保存單個節點，例如 *note Compare: 43cc. 節
     點。‘body’ 和 ‘orelse’ 各自保存一個節點串列。

     ‘elif’ 子句在 AST 中沒有特殊表示，而是在前一個子句的 ‘orelse’ 部分
     中作為額外的 *note If: 43f2. 節點出現。

          >>> print(ast.dump(ast.parse("""
          ... if x:
          ...    ...
          ... elif y:
          ...    ...
          ... else:
          ...    ...
          ... """), indent=4))
          Module(
              body=[
                  If(
                      test=Name(id='x', ctx=Load()),
                      body=[
                          Expr(
                              value=Constant(value=Ellipsis))],
                      orelse=[
                          If(
                              test=Name(id='y', ctx=Load()),
                              body=[
                                  Expr(
                                      value=Constant(value=Ellipsis))],
                              orelse=[
                                  Expr(
                                      value=Constant(value=Ellipsis))])])])

 -- 類別: ast.For (target, iter, body, orelse, type_comment)

     一個 ‘for’ 迴圈。 ‘target’ 保存迴圈賦予的變數，為單個 *note Name:
     1841.、*note Tuple: 43ac.、*note List: 43ab.、*note Attribute:
     43d7. 或 *note Subscript: 43dd. 節點。‘iter’ 保存要迴圈跑過的項目，
     也為單個節點。‘body’ 和 ‘orelse’ 包含要執行的節點串列。如果迴圈正常
     完成，則執行 ‘orelse’ 中的內容，而不是透過 ‘break’ 陳述式執行。

      -- 屬性: type_comment

          ‘type_comment’ 是一個可選字串，其中的註解為型別註釋。

          >>> print(ast.dump(ast.parse("""
          ... for x in y:
          ...     ...
          ... else:
          ...     ...
          ... """), indent=4))
          Module(
              body=[
                  For(
                      target=Name(id='x', ctx=Store()),
                      iter=Name(id='y', ctx=Load()),
                      body=[
                          Expr(
                              value=Constant(value=Ellipsis))],
                      orelse=[
                          Expr(
                              value=Constant(value=Ellipsis))])])

 -- 類別: ast.While (test, body, orelse)

     一個 ‘while’ 迴圈。‘test’ 保存條件，例如 *note Compare: 43cc. 節點
     。

          >> print(ast.dump(ast.parse("""
          ... while x:
          ...    ...
          ... else:
          ...    ...
          ... """), indent=4))
          Module(
              body=[
                  While(
                      test=Name(id='x', ctx=Load()),
                      body=[
                          Expr(
                              value=Constant(value=Ellipsis))],
                      orelse=[
                          Expr(
                              value=Constant(value=Ellipsis))])])

 -- 類別: ast.Break
 -- 類別: ast.Continue

     ‘break’ 和 ‘continue’ 陳述式。

          >>> print(ast.dump(ast.parse("""\
          ... for a in b:
          ...     if a > 5:
          ...         break
          ...     else:
          ...         continue
          ...
          ... """), indent=4))
          Module(
              body=[
                  For(
                      target=Name(id='a', ctx=Store()),
                      iter=Name(id='b', ctx=Load()),
                      body=[
                          If(
                              test=Compare(
                                  left=Name(id='a', ctx=Load()),
                                  ops=[
                                      Gt()],
                                  comparators=[
                                      Constant(value=5)]),
                              body=[
                                  Break()],
                              orelse=[
                                  Continue()])])])

 -- 類別: ast.Try (body, handlers, orelse, finalbody)

     ‘try’ 區塊。除 ‘handlers’ 是 *note ExceptHandler: 43f9. 節點的串列
     外，其他所有屬性都是要執行之節點的串列。

          >>> print(ast.dump(ast.parse("""
          ... try:
          ...    ...
          ... except Exception:
          ...    ...
          ... except OtherException as e:
          ...    ...
          ... else:
          ...    ...
          ... finally:
          ...    ...
          ... """), indent=4))
          Module(
              body=[
                  Try(
                      body=[
                          Expr(
                              value=Constant(value=Ellipsis))],
                      handlers=[
                          ExceptHandler(
                              type=Name(id='Exception', ctx=Load()),
                              body=[
                                  Expr(
                                      value=Constant(value=Ellipsis))]),
                          ExceptHandler(
                              type=Name(id='OtherException', ctx=Load()),
                              name='e',
                              body=[
                                  Expr(
                                      value=Constant(value=Ellipsis))])],
                      orelse=[
                          Expr(
                              value=Constant(value=Ellipsis))],
                      finalbody=[
                          Expr(
                              value=Constant(value=Ellipsis))])])

 -- 類別: ast.TryStar (body, handlers, orelse, finalbody)

     ‘try’ 區塊，後面跟著 ‘except*’ 子句。這些屬性與 *note Try: 43f8. 相
     同，但是 ‘handlers’ 中的 *note ExceptHandler: 43f9. 節點被直譯
     (interpret) 為 ‘except*’ 區塊而不是 ‘except’。

          >>> print(ast.dump(ast.parse("""
          ... try:
          ...    ...
          ... except* Exception:
          ...    ...
          ... """), indent=4))
          Module(
              body=[
                  TryStar(
                      body=[
                          Expr(
                              value=Constant(value=Ellipsis))],
                      handlers=[
                          ExceptHandler(
                              type=Name(id='Exception', ctx=Load()),
                              body=[
                                  Expr(
                                      value=Constant(value=Ellipsis))])])])

     在 3.11 版被加入.

 -- 類別: ast.ExceptHandler (type, name, body)

     單個 ‘except’ 子句。‘type’ 是會被匹配的例外型別，通常是一個 *note
     Name: 1841. 節點（或者 ‘None’ 表示會捕捉到所有例外的 ‘except:’ 子句
     ）。‘name’ 是用於保存例外的名稱之原始字串，如果子句沒有 ‘as foo’ ，
     則為 ‘None’。‘body’ 是節點串列。

          >>> print(ast.dump(ast.parse("""\
          ... try:
          ...     a + 1
          ... except TypeError:
          ...     pass
          ... """), indent=4))
          Module(
              body=[
                  Try(
                      body=[
                          Expr(
                              value=BinOp(
                                  left=Name(id='a', ctx=Load()),
                                  op=Add(),
                                  right=Constant(value=1)))],
                      handlers=[
                          ExceptHandler(
                              type=Name(id='TypeError', ctx=Load()),
                              body=[
                                  Pass()])])])

 -- 類別: ast.With (items, body, type_comment)

     一個 ‘with’ 區塊。‘items’ 是表示情境管理器的 *note withitem: 43fc.
     節點串列，‘body’ 是情境內的縮進區塊。

      -- 屬性: type_comment

          ‘type_comment’ 是一個可選字串，其中的註解為型別註釋。

 -- 類別: ast.withitem (context_expr, optional_vars)

     ‘with’ 區塊中的單個情境管理器。‘context_expr’ 是情境管理器，通常是
     一個 *note Call: 43b2. 節點。‘Optional_vars’ 是 ‘as foo’ 部分的
     *note Name: 1841.、*note Tuple: 43ac. 或 *note List: 43ab.，或者如
     果不使用則為 ‘None’ 。

          >>> print(ast.dump(ast.parse("""\
          ... with a as b, c as d:
          ...    something(b, d)
          ... """), indent=4))
          Module(
              body=[
                  With(
                      items=[
                          withitem(
                              context_expr=Name(id='a', ctx=Load()),
                              optional_vars=Name(id='b', ctx=Store())),
                          withitem(
                              context_expr=Name(id='c', ctx=Load()),
                              optional_vars=Name(id='d', ctx=Store()))],
                      body=[
                          Expr(
                              value=Call(
                                  func=Name(id='something', ctx=Load()),
                                  args=[
                                      Name(id='b', ctx=Load()),
                                      Name(id='d', ctx=Load())]))])])


File: python.info,  Node: 模式匹配 pattern matching,  Next: 型別參數 type parameters,  Prev: 流程控制,  Up: 節點 Node 類別

5.32.1.12 模式匹配 (pattern matching)
.....................................

 -- 類別: ast.Match (subject, cases)

     一個 ‘match’ 陳述式。‘subject’ 保存匹配的主題（與案例匹配的物件），
     ‘cases’ 包含具有不同案例的 *note match_case: 4400. 節點的可疊代物件
     。

     在 3.10 版被加入.

 -- 類別: ast.match_case (pattern, guard, body)

     ‘match’ 陳述式中的單個案例模式。‘pattern’ 包含主題將與之匹配的匹配
     模式。請注意，為模式生成的 *note AST: 18c. 節點與為運算式生成的節點
     不同，即使它們共享相同的語法。

     ‘guard’ 屬性包含一個運算式，如果模式與主題匹配，則將對該運算式求值
     。

     ‘body’ 包含一個節點串列，如果模式匹配並且為防護運算式 (guard
     expression) 的求值 (evaluate) 結果為真，則會執行該節點串列。

          >>> print(ast.dump(ast.parse("""
          ... match x:
          ...     case [x] if x>0:
          ...         ...
          ...     case tuple():
          ...         ...
          ... """), indent=4))
          Module(
              body=[
                  Match(
                      subject=Name(id='x', ctx=Load()),
                      cases=[
                          match_case(
                              pattern=MatchSequence(
                                  patterns=[
                                      MatchAs(name='x')]),
                              guard=Compare(
                                  left=Name(id='x', ctx=Load()),
                                  ops=[
                                      Gt()],
                                  comparators=[
                                      Constant(value=0)]),
                              body=[
                                  Expr(
                                      value=Constant(value=Ellipsis))]),
                          match_case(
                              pattern=MatchClass(
                                  cls=Name(id='tuple', ctx=Load())),
                              body=[
                                  Expr(
                                      value=Constant(value=Ellipsis))])])])

     在 3.10 版被加入.

 -- 類別: ast.MatchValue (value)

     以相等性進行比較的匹配文本或值的模式。‘value’ 是一個運算式節點。允
     許值節點受到匹配陳述式文件中所述的限制。如果匹配主題等於求出值，則
     此模式成功。

          >>> print(ast.dump(ast.parse("""
          ... match x:
          ...     case "Relevant":
          ...         ...
          ... """), indent=4))
          Module(
              body=[
                  Match(
                      subject=Name(id='x', ctx=Load()),
                      cases=[
                          match_case(
                              pattern=MatchValue(
                                  value=Constant(value='Relevant')),
                              body=[
                                  Expr(
                                      value=Constant(value=Ellipsis))])])])

     在 3.10 版被加入.

 -- 類別: ast.MatchSingleton (value)

     按識別性 (identity) 進行比較的匹配文本模式。‘value’ 是要與 ‘None’、
     ‘True’ 或 ‘False’ 進行比較的單例 (singleton)。如果匹配主題是給定的
     常數，則此模式成功。

          >>> print(ast.dump(ast.parse("""
          ... match x:
          ...     case None:
          ...         ...
          ... """), indent=4))
          Module(
              body=[
                  Match(
                      subject=Name(id='x', ctx=Load()),
                      cases=[
                          match_case(
                              pattern=MatchSingleton(value=None),
                              body=[
                                  Expr(
                                      value=Constant(value=Ellipsis))])])])

     在 3.10 版被加入.

 -- 類別: ast.MatchSequence (patterns)

     匹配序列模式。如果主題是一個序列，‘patterns’ 包含與主題元素匹配的模
     式。如果子模式之一是 ‘MatchStar’ 節點，則匹配可變長度序列，否則匹配
     固定長度序列。

          >>> print(ast.dump(ast.parse("""
          ... match x:
          ...     case [1, 2]:
          ...         ...
          ... """), indent=4))
          Module(
              body=[
                  Match(
                      subject=Name(id='x', ctx=Load()),
                      cases=[
                          match_case(
                              pattern=MatchSequence(
                                  patterns=[
                                      MatchValue(
                                          value=Constant(value=1)),
                                      MatchValue(
                                          value=Constant(value=2))]),
                              body=[
                                  Expr(
                                      value=Constant(value=Ellipsis))])])])

     在 3.10 版被加入.

 -- 類別: ast.MatchStar (name)

     以可變長度匹配序列模式匹配序列的其餘部分。如果 ‘name’ 不是 ‘None’，
     則如果整體序列模式成功，則包含其餘序列元素的串列將綁定到該名稱。

          >>> print(ast.dump(ast.parse("""
          ... match x:
          ...     case [1, 2, *rest]:
          ...         ...
          ...     case [*_]:
          ...         ...
          ... """), indent=4))
          Module(
              body=[
                  Match(
                      subject=Name(id='x', ctx=Load()),
                      cases=[
                          match_case(
                              pattern=MatchSequence(
                                  patterns=[
                                      MatchValue(
                                          value=Constant(value=1)),
                                      MatchValue(
                                          value=Constant(value=2)),
                                      MatchStar(name='rest')]),
                              body=[
                                  Expr(
                                      value=Constant(value=Ellipsis))]),
                          match_case(
                              pattern=MatchSequence(
                                  patterns=[
                                      MatchStar()]),
                              body=[
                                  Expr(
                                      value=Constant(value=Ellipsis))])])])

     在 3.10 版被加入.

 -- 類別: ast.MatchMapping (keys, patterns, rest)

     匹配對映模式。‘keys’ 是運算式節點的序列。‘patterns’ 是相應的模式節
     點序列。‘rest’ 是一個可選名稱，可以指定它來捕獲剩餘的對映元素。允許
     的鍵運算式受到匹配陳述式文件中所述的限制。

     如果主題是對映，所有求值出的鍵運算式都存在於對映中，並且與每個鍵對
     應的值與相應的子模式匹配，則此模式成功。如果 ‘rest’ 不是 ‘None’，則
     如果整體對映模式成功，則包含其餘對映元素的字典將綁定到該名稱。

          >>> print(ast.dump(ast.parse("""
          ... match x:
          ...     case {1: _, 2: _}:
          ...         ...
          ...     case {**rest}:
          ...         ...
          ... """), indent=4))
          Module(
              body=[
                  Match(
                      subject=Name(id='x', ctx=Load()),
                      cases=[
                          match_case(
                              pattern=MatchMapping(
                                  keys=[
                                      Constant(value=1),
                                      Constant(value=2)],
                                  patterns=[
                                      MatchAs(),
                                      MatchAs()]),
                              body=[
                                  Expr(
                                      value=Constant(value=Ellipsis))]),
                          match_case(
                              pattern=MatchMapping(rest='rest'),
                              body=[
                                  Expr(
                                      value=Constant(value=Ellipsis))])])])

     在 3.10 版被加入.

 -- 類別: ast.MatchClass (cls, patterns, kwd_attrs, kwd_patterns)

     匹配類別模式。‘cls’ 是一個給定要匹配的名義類別 (nominal class) 的運
     算式。‘patterns’ 是要與類別定義的模式匹配屬性序列進行匹配的模式節點
     序列。‘kwd_attrs’ 是要匹配的附加屬性序列（在類別模式中指定為關鍵字
     引數），‘kwd_patterns’ 是相應的模式（在類別模式中指定為關鍵字的值）
     。

     如果主題是指定類別的實例，所有位置模式都與相應的類別定義屬性匹配，
     並且任何指定的關鍵字屬性與其相應模式匹配，則此模式成功。

     注意：類別可以定義一個回傳 self 的特性 (property)，以便將模式節點與
     正在匹配的實例進行匹配。一些內建型別也以這種方式匹配，如同匹配陳述
     式文件中所述。

          >>> print(ast.dump(ast.parse("""
          ... match x:
          ...     case Point2D(0, 0):
          ...         ...
          ...     case Point3D(x=0, y=0, z=0):
          ...         ...
          ... """), indent=4))
          Module(
              body=[
                  Match(
                      subject=Name(id='x', ctx=Load()),
                      cases=[
                          match_case(
                              pattern=MatchClass(
                                  cls=Name(id='Point2D', ctx=Load()),
                                  patterns=[
                                      MatchValue(
                                          value=Constant(value=0)),
                                      MatchValue(
                                          value=Constant(value=0))]),
                              body=[
                                  Expr(
                                      value=Constant(value=Ellipsis))]),
                          match_case(
                              pattern=MatchClass(
                                  cls=Name(id='Point3D', ctx=Load()),
                                  kwd_attrs=[
                                      'x',
                                      'y',
                                      'z'],
                                  kwd_patterns=[
                                      MatchValue(
                                          value=Constant(value=0)),
                                      MatchValue(
                                          value=Constant(value=0)),
                                      MatchValue(
                                          value=Constant(value=0))]),
                              body=[
                                  Expr(
                                      value=Constant(value=Ellipsis))])])])

     在 3.10 版被加入.

 -- 類別: ast.MatchAs (pattern, name)

     匹配的 「as 模式 (as-pattern)」，為捕獲模式 (capture pattern) 或通
     配模式 (wildcard pattern)。‘pattern’ 包含主題將與之匹配的匹配模式。
     如果模式為 ‘None’，則該節點代表捕獲模式（即裸名 (bare name)）並且始
     終會成功。

     ‘name’ 屬性包含模式成功時將綁定的名稱。如果 ‘name’ 為 ‘None’，則
     ‘pattern’ 也必須為 ‘None’，並且節點代表通配模式。

          >>> print(ast.dump(ast.parse("""
          ... match x:
          ...     case [x] as y:
          ...         ...
          ...     case _:
          ...         ...
          ... """), indent=4))
          Module(
              body=[
                  Match(
                      subject=Name(id='x', ctx=Load()),
                      cases=[
                          match_case(
                              pattern=MatchAs(
                                  pattern=MatchSequence(
                                      patterns=[
                                          MatchAs(name='x')]),
                                  name='y'),
                              body=[
                                  Expr(
                                      value=Constant(value=Ellipsis))]),
                          match_case(
                              pattern=MatchAs(),
                              body=[
                                  Expr(
                                      value=Constant(value=Ellipsis))])])])

     在 3.10 版被加入.

 -- 類別: ast.MatchOr (patterns)

     匹配的 「or 模式 (or-pattern)」。 or 模式依次將其每個子模式與主題進
     行匹配，直到成功為止，然後 or 模式就會被認為是成功的。如果沒有一個
     子模式成功，則 or 模式將失敗。 ‘patterns’ 屬性包含將與主題進行匹配
     的匹配模式節點串列。

          >>> print(ast.dump(ast.parse("""
          ... match x:
          ...     case [x] | (y):
          ...         ...
          ... """), indent=4))
          Module(
              body=[
                  Match(
                      subject=Name(id='x', ctx=Load()),
                      cases=[
                          match_case(
                              pattern=MatchOr(
                                  patterns=[
                                      MatchSequence(
                                          patterns=[
                                              MatchAs(name='x')]),
                                      MatchAs(name='y')]),
                              body=[
                                  Expr(
                                      value=Constant(value=Ellipsis))])])])

     在 3.10 版被加入.


File: python.info,  Node: 型別參數 type parameters,  Next: 函式和類別定義,  Prev: 模式匹配 pattern matching,  Up: 節點 Node 類別

5.32.1.13 型別參數 (type parameters)
....................................

*note 型別參數: 294.可以存在於類別、函式和型別別名上。

 -- 類別: ast.TypeVar (name, bound, default_value)

     A *note typing.TypeVar: 141.  'name' is the name of the type
     variable.  'bound' is the bound or constraints, if any.  If 'bound'
     is a *note Tuple: 43ac, it represents constraints; otherwise it
     represents the bound.  'default_value' is the default value; if the
     ‘TypeVar’ has no default, this attribute will be set to ‘None’.

          >>> print(ast.dump(ast.parse("type Alias[T: int = bool] = list[T]"), indent=4))
          Module(
              body=[
                  TypeAlias(
                      name=Name(id='Alias', ctx=Store()),
                      type_params=[
                          TypeVar(
                              name='T',
                              bound=Name(id='int', ctx=Load()),
                              default_value=Name(id='bool', ctx=Load()))],
                      value=Subscript(
                          value=Name(id='list', ctx=Load()),
                          slice=Name(id='T', ctx=Load()),
                          ctx=Load()))])

     在 3.12 版被加入.

     在 3.13 版的變更: Added the 'default_value' parameter.

 -- 類別: ast.ParamSpec (name, default_value)

     A *note typing.ParamSpec: 142.  'name' is the name of the parameter
     specification.  'default_value' is the default value; if the
     ‘ParamSpec’ has no default, this attribute will be set to ‘None’.

          >>> print(ast.dump(ast.parse("type Alias[**P = (int, str)] = Callable[P, int]"), indent=4))
          Module(
              body=[
                  TypeAlias(
                      name=Name(id='Alias', ctx=Store()),
                      type_params=[
                          ParamSpec(
                              name='P',
                              default_value=Tuple(
                                  elts=[
                                      Name(id='int', ctx=Load()),
                                      Name(id='str', ctx=Load())],
                                  ctx=Load()))],
                      value=Subscript(
                          value=Name(id='Callable', ctx=Load()),
                          slice=Tuple(
                              elts=[
                                  Name(id='P', ctx=Load()),
                                  Name(id='int', ctx=Load())],
                              ctx=Load()),
                          ctx=Load()))])

     在 3.12 版被加入.

     在 3.13 版的變更: Added the 'default_value' parameter.

 -- 類別: ast.TypeVarTuple (name, default_value)

     A *note typing.TypeVarTuple: 143.  'name' is the name of the type
     variable tuple.  'default_value' is the default value; if the
     ‘TypeVarTuple’ has no default, this attribute will be set to
     ‘None’.

          >>> print(ast.dump(ast.parse("type Alias[*Ts = ()] = tuple[*Ts]"), indent=4))
          Module(
              body=[
                  TypeAlias(
                      name=Name(id='Alias', ctx=Store()),
                      type_params=[
                          TypeVarTuple(
                              name='Ts',
                              default_value=Tuple(ctx=Load()))],
                      value=Subscript(
                          value=Name(id='tuple', ctx=Load()),
                          slice=Tuple(
                              elts=[
                                  Starred(
                                      value=Name(id='Ts', ctx=Load()),
                                      ctx=Load())],
                              ctx=Load()),
                          ctx=Load()))])

     在 3.12 版被加入.

     在 3.13 版的變更: Added the 'default_value' parameter.


File: python.info,  Node: 函式和類別定義,  Next: async 和 await,  Prev: 型別參數 type parameters,  Up: 節點 Node 類別

5.32.1.14 函式和類別定義
........................

 -- 類別: ast.FunctionDef (name, args, body, decorator_list, returns,
          type_comment, type_params)

     一個函式定義。

        * ‘name’ 是函式名稱的原始字串。

        * ‘args’ 是一個 *note arguments: 440e. 節點。

        * ‘body’ 是函式內節點的串列。

        * ‘decorator_list’ 是要應用的裝飾器串列，在最外層者會被儲存在首
          位（即串列中首位將會是最後一個被應用的那個）。

        * ‘returns’ 是回傳註釋。

        * ‘type_params’ 是*note 型別參數: 43ed.的串列。

      -- 屬性: type_comment

          ‘type_comment’ 是一個可選字串，其中的註解為型別註釋。

     在 3.12 版的變更: 新增了 ‘type_params’。

 -- 類別: ast.Lambda (args, body)

     ‘lambda’ 是可以在運算式內使用的最小函式定義。與 *note FunctionDef:
     1604. 不同，‘body’ 保存單個節點。

          >>> print(ast.dump(ast.parse('lambda x,y: ...'), indent=4))
          Module(
              body=[
                  Expr(
                      value=Lambda(
                          args=arguments(
                              args=[
                                  arg(arg='x'),
                                  arg(arg='y')]),
                          body=Constant(value=Ellipsis)))])

 -- 類別: ast.arguments (posonlyargs, args, vararg, kwonlyargs,
          kw_defaults, kwarg, defaults)

     函式的引數。

        * ‘posonlyargs’、‘args’ 和 ‘kwonlyargs’ 是 *note arg: 4410. 節點
          的串列。

        * ‘vararg’ 和 ‘kwarg’ 是單個 *note arg: 4410. 節點，指的是
          ‘*args, **kwargs’ 參數。

        * ‘kw_defaults’ 是僅限關鍵字引數的預設值串列。如果其中某個為
          ‘None’，則相應參數就會是必要的。

        * ‘defaults’ 是可以按位置傳遞的引數的預設值串列。如果預設值較少
          ，則它們對應於最後 n 個引數。

 -- 類別: ast.arg (arg, annotation, type_comment)

     串列中的單個引數。‘arg’ 是引數名稱的原始字串，‘annotation’ 是它的註
     釋，例如 *note Name: 1841. 節點。

      -- 屬性: type_comment

          ‘type_comment’ 是一個可選字串，其註解為型別註釋

          >>> print(ast.dump(ast.parse("""\
          ... @decorator1
          ... @decorator2
          ... def f(a: 'annotation', b=1, c=2, *d, e, f=3, **g) -> 'return annotation':
          ...     pass
          ... """), indent=4))
          Module(
              body=[
                  FunctionDef(
                      name='f',
                      args=arguments(
                          args=[
                              arg(
                                  arg='a',
                                  annotation=Constant(value='annotation')),
                              arg(arg='b'),
                              arg(arg='c')],
                          vararg=arg(arg='d'),
                          kwonlyargs=[
                              arg(arg='e'),
                              arg(arg='f')],
                          kw_defaults=[
                              None,
                              Constant(value=3)],
                          kwarg=arg(arg='g'),
                          defaults=[
                              Constant(value=1),
                              Constant(value=2)]),
                      body=[
                          Pass()],
                      decorator_list=[
                          Name(id='decorator1', ctx=Load()),
                          Name(id='decorator2', ctx=Load())],
                      returns=Constant(value='return annotation'))])

 -- 類別: ast.Return (value)

     一個 ‘return’ 陳述式。

          >>> print(ast.dump(ast.parse('return 4'), indent=4))
          Module(
              body=[
                  Return(
                      value=Constant(value=4))])

 -- 類別: ast.Yield (value)
 -- 類別: ast.YieldFrom (value)

     一個 ‘yield’ 或 ‘yield from’ 運算式。因為這些是運算式，所以如果不使
     用發送回來的值，則必須將它們包裝在 *note Expr: 43b4. 節點中。

          >>> print(ast.dump(ast.parse('yield x'), indent=4))
          Module(
              body=[
                  Expr(
                      value=Yield(
                          value=Name(id='x', ctx=Load())))])

          >>> print(ast.dump(ast.parse('yield from x'), indent=4))
          Module(
              body=[
                  Expr(
                      value=YieldFrom(
                          value=Name(id='x', ctx=Load())))])

 -- 類別: ast.Global (names)
 -- 類別: ast.Nonlocal (names)

     ‘global’ 和 ‘nonlocal’ 陳述式。‘names’ 是原始字串的串列。

          >>> print(ast.dump(ast.parse('global x,y,z'), indent=4))
          Module(
              body=[
                  Global(
                      names=[
                          'x',
                          'y',
                          'z'])])

          >>> print(ast.dump(ast.parse('nonlocal x,y,z'), indent=4))
          Module(
              body=[
                  Nonlocal(
                      names=[
                          'x',
                          'y',
                          'z'])])

 -- 類別: ast.ClassDef (name, bases, keywords, body, decorator_list,
          type_params)

     一個類別定義。

        * ‘name’ 是類別名的原始字串

        * ‘bases’ 是被顯式指定的基底類別節點串列。

        * ‘keywords’ 是一個 *note keyword: 43d8. 節點的串列，主要用於
          'metaclass'（元類別）。如 PEP-3115(1) 所述，其他關鍵字將被傳遞
          到 metaclass。

        * ‘body’ 是表示類別定義中程式碼的節點串列。

        * ‘decorator_list’ 是一個節點串列，如 *note FunctionDef: 1604. 中
          所示。

        * ‘type_params’ 是*note 型別參數: 43ed.的串列。

          >>> print(ast.dump(ast.parse("""\
          ... @decorator1
          ... @decorator2
          ... class Foo(base1, base2, metaclass=meta):
          ...     pass
          ... """), indent=4))
          Module(
              body=[
                  ClassDef(
                      name='Foo',
                      bases=[
                          Name(id='base1', ctx=Load()),
                          Name(id='base2', ctx=Load())],
                      keywords=[
                          keyword(
                              arg='metaclass',
                              value=Name(id='meta', ctx=Load()))],
                      body=[
                          Pass()],
                      decorator_list=[
                          Name(id='decorator1', ctx=Load()),
                          Name(id='decorator2', ctx=Load())])])

     在 3.12 版的變更: 新增了 ‘type_params’。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3115/


File: python.info,  Node: async 和 await,  Prev: 函式和類別定義,  Up: 節點 Node 類別

5.32.1.15 async 和 await
........................

 -- 類別: ast.AsyncFunctionDef (name, args, body, decorator_list,
          returns, type_comment, type_params)

     一個 ‘async def’ 函式定義。與 *note FunctionDef: 1604. 具有相同的欄
     位。

     在 3.12 版的變更: 新增了 ‘type_params’。

 -- 類別: ast.Await (value)

     一個 ‘await’ 運算式。‘value’ 是它等待的東西。僅在 *note
     AsyncFunctionDef: 1603. 主體 (body) 中有效。

     >>> print(ast.dump(ast.parse("""\
     ... async def f():
     ...     await other_func()
     ... """), indent=4))
     Module(
         body=[
             AsyncFunctionDef(
                 name='f',
                 args=arguments(),
                 body=[
                     Expr(
                         value=Await(
                             value=Call(
                                 func=Name(id='other_func', ctx=Load()))))])])

 -- 類別: ast.AsyncFor (target, iter, body, orelse, type_comment)
 -- 類別: ast.AsyncWith (items, body, type_comment)

     ‘async for’ 迴圈和 ‘async with’ 情境管理器。它們分別具有與 *note
     For: 43f3. 和 *note With: 43fb. 相同的欄位。僅在 *note
     AsyncFunctionDef: 1603. 主體中有效。

     備註: 當字串被 *note ast.parse(): 18e. 剖析時，回傳樹的運算子節點（
     ‘ast.operator’、‘ast.unaryop’、‘ast.cmpop’、:class: ‘ast.boolop’ 和
     ‘ast.expr_context’）將是單例。對其中之一的更改將反映在所有其他出現
     的相同值中（例如 *note ast.Add: 43bc.）。


File: python.info,  Node: ast 輔助程式,  Next: 編譯器旗標<2>,  Prev: 節點 Node 類別,  Up: ast --- 抽象語法樹 Abstract Syntax Trees

5.32.1.16 ‘ast’ 輔助程式
........................

除了節點類別之外，*note ast: 7. 模組還定義了這些用於遍歷 (traverse) 抽象
語法樹的實用函式和類別：

 -- 函式: ast.parse (source, filename='<unknown>', mode='exec', *,
          type_comments=False, feature_version=None, optimize=-1)

     Parse the source into an AST node.  Equivalent to ‘compile(source,
     filename, mode, flags=FLAGS_VALUE, optimize=optimize)’, where
     ‘FLAGS_VALUE’ is ‘ast.PyCF_ONLY_AST’ if ‘optimize <= 0’ and
     ‘ast.PyCF_OPTIMIZED_AST’ otherwise.

     如果給定 ‘type_comments=True’，剖析器將被修改為檢查並回傳 PEP
     484(1) 和 PEP 526(2) 指定的型別註釋。這相當於將 *note
     ast.PyCF_TYPE_COMMENTS: 441a. 新增到傳遞給 *note compile(): 178. 的
     旗標中。這將報告錯誤型別註釋的語法錯誤。如果沒有此旗標，型別註釋將
     被忽略，並且所選 AST 節點上的 ‘type_comment’ 欄位將始終為 ‘None’。
     此外，‘# type: ignore’ 註釋的位置將作為 *note Module: 43a3. 的
     ‘type_ignores’ 屬性回傳（否則它始終是一個空串列）。

     此外，如果 ‘mode’ 是 ‘'func_type'’，則輸入語法將會依據 PEP 484(3)「
     簽名型別註解 (signature type comments)」而被修改，例如 ‘(str, int)
     -> List[str]’。

     Setting ‘feature_version’ to a tuple ‘(major, minor)’ will result
     in a "best-effort" attempt to parse using that Python version's
     grammar.  For example, setting ‘feature_version=(3, 9)’ will
     attempt to disallow parsing of *note match: 7b1. statements.
     Currently ‘major’ must equal to ‘3’.  The lowest supported version
     is ‘(3, 7)’ (and this may increase in future Python versions); the
     highest is ‘sys.version_info[0:2]’.  "Best-effort" attempt means
     there is no guarantee that the parse (or success of the parse) is
     the same as when run on the Python version corresponding to
     ‘feature_version’.

     如果來源包含 null 字元 (‘\0’)，則會引發 *note ValueError: 1e7.。

          警告: 請注意，成功將原始碼剖析為 AST 物件並不能保證提供的原始
          碼是可以執行的有效 Python 程式碼，因為編譯步驟可能會引發進一步
          的 *note SyntaxError: 173. 例外。例如，原始的 ‘return 42’ 為
          return 陳述式生成一個有效的 AST 節點，但它不能單獨編譯（它需要
          位於函式節點內）。

          特別是 *note ast.parse(): 18e. 不會執行任何範圍檢查，而編譯步
          驟才會執行此操作。

          警告: 由於 Python AST 編譯器中的堆疊 (stack) 深度限制，太大或
          太複雜的字串可能會導致 Python 直譯器崩潰。

     在 3.8 版的變更: 新增 ‘type_comments’、‘mode='func_type'’ 與
     ‘feature_version’。

     在 3.13 版的變更: The minimum supported version for
     ‘feature_version’ is now ‘(3, 7)’.  The ‘optimize’ argument was
     added.

 -- 函式: ast.unparse (ast_obj)

     反剖析 *note ast.AST: 18c. 物件並生成一個帶有程式碼的字串，如果使用
     *note ast.parse(): 18e. 剖析回來，該程式碼將生成等效的 *note
     ast.AST: 18c. 物件。

          警告: 生成的程式碼字串不一定等於生成 *note ast.AST: 18c. 物件
          的原始程式碼（沒有任何編譯器最佳化，例如常數元組/凍結集合）。

          警告: 嘗試剖析高度複雜的運算式會導致 *note RecursionError:
          d12.。

     在 3.9 版被加入.

 -- 函式: ast.literal_eval (node_or_string)

     為僅包含 Python 文本或容器之顯示的運算式節點或字串來求值。提供的字
     串或節點只能包含以下 Python 文本結構：字串、位元組、數字、元組、串
     列、字典、集合、布林值、‘None’ 和 ‘Ellipsis’。

     這可用於為包含 Python 值的字串求值，而無需自己剖析這些值。它無法計
     算任意複雜的運算式，例如涉及運算子或索引。

     該函式過去被記錄為「安全」，但沒有定義其含義，這有點誤導讀者，它是
     特別設計為不去執行 Python 程式碼，與更通用的 *note eval(): 163. 不
     同。沒有命名空間、沒有名稱查找、也沒有呼叫的能力。但它也不能免受攻
     擊：相對較小的輸入可能會導致記憶體耗盡或 C 堆疊耗盡，從而導致行程崩
     潰。某些輸入也可能會出現 CPU 消耗過多而導致拒絕服務的情況。因此不建
     議在不受信任的資料上呼叫它。

          警告: 由於 Python AST 編譯器的堆疊深度限制，Python 直譯器可能
          會崩潰。

          它可能會引發 *note ValueError: 1e7.、*note TypeError: 4dd.、
          *note SyntaxError: 173.、*note MemoryError: 15bc. 和 *note
          RecursionError: d12.，具體取決於格式錯誤的輸入。

     在 3.2 版的變更: 現在允許位元組和集合文本 (set literal)。

     在 3.9 版的變更: 現在支援使用 ‘'set()'’ 建立空集合。

     在 3.10 版的變更: 對於字串輸入，前導空格和定位字元 (tab) 現在已被去
     除。

 -- 函式: ast.get_docstring (node, clean=True)

     回傳給定 'node' 的文件字串 (docstring)（必須是 *note FunctionDef:
     1604.、*note AsyncFunctionDef: 1603.、*note ClassDef: 1602. 或
     *note Module: 43a3. 節點）或如果它沒有文件字串則為 ‘None’。如果
     'clean' 為 true，則使用 *note inspect.cleandoc(): 15ad. 清理文件字
     串的縮排。

     在 3.5 版的變更: 目前已支援 *note AsyncFunctionDef: 1603.。

 -- 函式: ast.get_source_segment (source, node, *, padded=False)

     獲取生成 'node' 的 'source' 的原始碼片段。如果某些位置資訊（*note
     lineno: 439c.、*note end_lineno: 439e.、*note col_offset: 439d. 或
     *note end_col_offset: 439f.）遺漏，則回傳 ‘None’。

     如果 'padded' 為 ‘True’，則多列陳述式的第一列將用空格填充 (padded)
     以匹配其原始位置。

     在 3.8 版被加入.

 -- 函式: ast.fix_missing_locations (node)

     當你使用 *note compile(): 178. 編譯節點樹時，對於每個有支援 *note
     lineno: 439c. 和 *note col_offset: 439d. 屬性之節點，編譯器預期他們
     的這些屬性都要存在。填入生成的節點相當繁瑣，因此該輔助工具透過將這
     些屬性設定為父節點的值，在尚未設定的地方遞迴地新增這些屬性。它從
     'node' 開始遞迴地作用。

 -- 函式: ast.increment_lineno (node, n=1)

     將樹中從 'node' 開始的每個節點的列號和結束列號增加 'n'。這對於「移
     動程式碼」到檔案中的不同位置很有用。

 -- 函式: ast.copy_location (new_node, old_node)

     如果可行，將原始位置（*note lineno: 439c.、*note col_offset: 439d.、
     *note end_lineno: 439e. 和 *note end_col_offset: 439f. ）從
     'old_node' 複製到 'new_node'，並回傳 'new_node' 。

 -- 函式: ast.iter_fields (node)

     為 'node' 上存在的 ‘node._fields’ 中的每個欄位生成一個 ‘(fieldname,
     value)’ 元組。

 -- 函式: ast.iter_child_nodes (node)

     生成 'node' 的所有直接子節點，即作為節點的所有欄位以及作為節點串列
     欄位的所有項目。

 -- 函式: ast.walk (node)

     遞迴地生成樹中從 'node' 開始的所有後代節點（包括 'node' 本身），不
     按指定順序。如果你只想就地修改節點而不關心情境，這非常有用。

 -- 類別: ast.NodeVisitor

     節點訪問者基底類別，它遍歷抽象語法樹並為找到的每個節點呼叫訪問者函
     式。該函式可能會回傳一個由 *note visit(): 4420. 方法轉發的值。

     這個類別應該被子類別化，子類別新增訪問者方法。

      -- 方法: visit (node)

          訪問一個節點。預設實作呼叫名為 ‘self.visit_CLASSNAME’ 的方法，
          其中 'classname' 是節點類別的名稱，或者在該方法不存在時呼叫
          *note generic_visit(): 4421.。

      -- 方法: generic_visit (node)

          該訪問者對該節點的所有子節點呼叫 *note visit(): 4420.。

          請注意，除非訪問者呼叫 *note generic_visit(): 4421. 或訪問它們
          本身，否則不會訪問具有自定義訪問者方法的節點之子節點。

      -- 方法: visit_Constant (node)

          處理所有常數節點。

     如果你想在遍歷期間將變更應用 (apply) 於節點，請不要使用 *note
     NodeVisitor: a10.。為此，有個允許修改的特殊遍歷訪問者工具 *note
     NodeTransformer: 4422.。

     在 3.8 版之後被棄用: ‘visit_Num()’、‘visit_Str()’、
     ‘visit_Bytes()’、‘visit_NameConstant()’ 和 ‘visit_Ellipsis()’ 方法
     現已棄用，並且不會在未來的Python 版本中被呼叫。新增 *note
     visit_Constant(): a11. 方法來處理所有常數節點。

 -- 類別: ast.NodeTransformer

     一個 *note NodeVisitor: a10. 子類別，它會遍歷抽象語法樹並允許修改節
     點。

     *note NodeTransformer: 4422. 將遍歷 AST 並使用訪問者方法的回傳值來
     替換或刪除舊節點。如果訪問者方法的回傳值為 ‘None’，則該節點將從其位
     置中刪除，否則將被替換為回傳值。回傳值可能是原始節點，在這種情況下
     不會發生替換。

     下面是一個示範用的 transformer，它將查找所有出現名稱 (‘foo’) 並改寫
     為 ‘data['foo']’：

          class RewriteName(NodeTransformer):

              def visit_Name(self, node):
                  return Subscript(
                      value=Name(id='data', ctx=Load()),
                      slice=Constant(value=node.id),
                      ctx=node.ctx
                  )

     請記住，如果你正在操作的節點有子節點，你必須自己轉換子節點或先呼叫
     該節點的 *note generic_visit(): 4421. 方法。

     對於屬於陳述式總集 (collection) 一部分的節點（適用於所有陳述式節點
     ），訪問者還可以回傳節點串列，而不僅僅是單個節點。

     如果 *note NodeTransformer: 4422. 引進了新節點（不屬於原始樹的一部
     分），但沒有給它們提供位置資訊（例如 *note lineno: 439c.），則應使
     用新的子樹呼叫 *note fix_missing_locations(): 441b. 以重新計算位置
     資訊：

          tree = ast.parse('foo', mode='eval')
          new_tree = fix_missing_locations(RewriteName().visit(tree))

     你通常會像這樣使用 transformer：

          node = YourTransformer().visit(node)

 -- 函式: ast.dump (node, annotate_fields=True,
          include_attributes=False, *, indent=None, show_empty=False)

     回傳 'node' 中樹的格式化傾印 (formatted dump)，這主要用於除錯。如果
     'annotate_fields' 為 true（為預設值），則回傳的字串將顯示欄位的名稱
     和值。如果 'annotate_fields' 為 false，則透過省略明確的欄位名稱，結
     果字串將更加縮減簡潔。預設情況下，不會傾印列號和行偏移量等屬性。如
     果需要，可以設定 'include_attributes' 為 true。

     如果 'indent' 是非負整數或字串，那麼樹將使用該縮排級別來做漂亮印出
     (pretty-print)。縮排級別 0、負數或 ‘""’ 只會插入換列符號
     (newlines)。‘None’（預設值）代表選擇單列表示。使用正整數縮排可以在
     每個級別縮排相同數量的空格。如果 'indent' 是一個字串（例如 ‘"\t"’）
     ，則該字串用於縮排每個級別。

     If 'show_empty' is ‘False’ (the default), empty lists and fields
     that are ‘None’ will be omitted from the output.

     在 3.9 版的變更: 新增 'indent' 選項。

     在 3.13 版的變更: Added the 'show_empty' option.

          >>> print(ast.dump(ast.parse("""\
          ... async def f():
          ...     await other_func()
          ... """), indent=4, show_empty=True))
          Module(
              body=[
                  AsyncFunctionDef(
                      name='f',
                      args=arguments(
                          posonlyargs=[],
                          args=[],
                          kwonlyargs=[],
                          kw_defaults=[],
                          defaults=[]),
                      body=[
                          Expr(
                              value=Await(
                                  value=Call(
                                      func=Name(id='other_func', ctx=Load()),
                                      args=[],
                                      keywords=[])))],
                      decorator_list=[],
                      type_params=[])],
              type_ignores=[])

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0484/

   (2) https://peps.python.org/pep-0526/

   (3) https://peps.python.org/pep-0484/


File: python.info,  Node: 編譯器旗標<2>,  Next: 命令列用法<3>,  Prev: ast 輔助程式,  Up: ast --- 抽象語法樹 Abstract Syntax Trees

5.32.1.17 編譯器旗標
....................

可以將以下旗標傳遞給 *note compile(): 178. 以變更對程式的編譯效果：

 -- 資料: ast.PyCF_ALLOW_TOP_LEVEL_AWAIT

     啟用對最高階 ‘await’、‘async for’、‘async with’ 和非同步綜合運算的
     支援。

     在 3.8 版被加入.

 -- 資料: ast.PyCF_ONLY_AST

     生成並回傳抽象語法樹，而不是回傳已編譯的程式碼物件。

 -- 資料: ast.PyCF_OPTIMIZED_AST

     The returned AST is optimized according to the 'optimize' argument
     in *note compile(): 178. or *note ast.parse(): 18e.

     在 3.13 版被加入.

 -- 資料: ast.PyCF_TYPE_COMMENTS

     啟用對 PEP 484(1) 和 PEP 526(2) 樣式型別註釋的支援 (‘# type:
     <type>’, ‘# type: ignore <stuff>’)。

     在 3.8 版被加入.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0484/

   (2) https://peps.python.org/pep-0526/


File: python.info,  Node: 命令列用法<3>,  Prev: 編譯器旗標<2>,  Up: ast --- 抽象語法樹 Abstract Syntax Trees

5.32.1.18 命令列用法
....................

在 3.9 版被加入.

*note ast: 7. 模組可以作為腳本從命令列執行，可以像這樣簡單地做到：

     python -m ast [-m <mode>] [-a] [infile]

以下選項可被接受：

 -- Option: -h, --help

     顯示幫助訊息並退出。

 -- Option: -m <mode>
 -- Option: --mode <mode>

     指定必須編譯哪種類型的程式碼，像是 *note parse(): 18e. 中的 'mode'
     引數。

 -- Option: --no-type-comments

     不要剖析型別註解。

 -- Option: -a, --include-attributes

     包括列號和行偏移量等屬性。

 -- Option: -i <indent>
 -- Option: --indent <indent>

     AST 中節點的縮進（空格數）。

如果指定了 ‘infile’，則其內容將被剖析為 AST 並傾印 (dump) 到 stdout。否
則會從 stdin 讀取內容。

也參考
......

Green Tree Snakes(1) 是一個外部文件資源，提供了有關使用 Python AST 的詳
細資訊。

ASTTokens(2) 使用生成它們的原始碼中的標記和文本的位置來註釋 Python AST。
這對於進行原始碼轉換的工具很有幫助。

leoAst.py(3) 透過在 token 和 ast 節點之間插入雙向鏈結，統一了 python 程
式的基於 token 和基於剖析樹的視圖。

LibCST(4) 將程式碼剖析為具體語法樹 (Concrete Syntax Tree)，看起來像 ast
樹並保留所有格式詳細資訊。它對於建置自動重構 (codemod) 應用程式和 linter
非常有用。

Parso(5) 是一個 Python 剖析器，支援不同 Python 版本的錯誤復原和往返剖析
。Parso 還能夠列出 Python 檔案中的多個語法錯誤。

   ---------- Footnotes ----------

   (1) https://greentreesnakes.readthedocs.io/

   (2) https://asttokens.readthedocs.io/en/latest/user-guide.html

   (3) https://leo-editor.github.io/leo-editor/appendices.html#leoast-py

   (4) https://libcst.readthedocs.io/

   (5) https://parso.readthedocs.io


File: python.info,  Node: symtable --- 存取編譯器的符號表,  Next: token --- 與 Python 剖析樹一起使用的常數,  Prev: ast --- 抽象語法樹 Abstract Syntax Trees,  Up: Python 語言服務

5.32.2 ‘symtable’ -- 存取編譯器的符號表
---------------------------------------

'原始碼：'Lib/symtable.py(1)

__________________________________________________________________

符號表 (symbol table) 是在生成位元組碼 (bytecode) 之前由編譯器從 AST 生
成的。符號表負責計算程式碼中每個識別器 (identifier) 的範圍。*note
symtable: c2. 提供了一個介面來檢查這些表。

* Menu:

* 產生符號表::
* 檢查符號表::
* Command-Line Usage: Command-Line Usage<2>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/symtable.py


File: python.info,  Node: 產生符號表,  Next: 檢查符號表,  Up: symtable --- 存取編譯器的符號表

5.32.2.1 產生符號表
...................

 -- 函式: symtable.symtable (code, filename, compile_type)

     回傳 Python 原始 'code' 的頂層 *note SymbolTable: 4434.。'filename'
     是包含程式碼之檔案之名稱。'compile_type' 類似於 *note compile():
     178. 的 'mode' 引數。


File: python.info,  Node: 檢查符號表,  Next: Command-Line Usage<2>,  Prev: 產生符號表,  Up: symtable --- 存取編譯器的符號表

5.32.2.2 檢查符號表
...................

 -- 類別: symtable.SymbolTableType

     An enumeration indicating the type of a *note SymbolTable: 4434.
     object.

      -- 屬性: MODULE = "module"

          Used for the symbol table of a module.

      -- 屬性: FUNCTION = "function"

          Used for the symbol table of a function.

      -- 屬性: CLASS = "class"

          Used for the symbol table of a class.

     The following members refer to different flavors of *note
     annotation scopes: 16e.

      -- 屬性: ANNOTATION = "annotation"

          Used for annotations if ‘from __future__ import annotations’
          is active.

      -- 屬性: TYPE_ALIAS = "type alias"

          Used for the symbol table of *note type: 3de. constructions.

      -- 屬性: TYPE_PARAMETERS = "type parameters"

          Used for the symbol table of *note generic functions: 3f9. or
          *note generic classes: 3f8.

      -- 屬性: TYPE_VARIABLE = "type variable"

          Used for the symbol table of the bound, the constraint tuple
          or the default value of a single type variable in the formal
          sense, i.e., a TypeVar, a TypeVarTuple or a ParamSpec object
          (the latter two do not support a bound or a constraint tuple).

     在 3.13 版被加入.

 -- 類別: symtable.SymbolTable

     一個區塊 (block) 的命名空間表 (namespace table) 。建構函式
     (constructor) 並不公開。

      -- 方法: get_type ()

          Return the type of the symbol table.  Possible values are
          members of the *note SymbolTableType: 1500. enumeration.

          在 3.12 版的變更: 新增了 ‘'annotation'’、‘'TypeVar bound'’、
          ‘'type alias'’ 和 ‘'type parameter'’ 作為可能的回傳值。

          在 3.13 版的變更: Return values are members of the *note
          SymbolTableType: 1500. enumeration.

          The exact values of the returned string may change in the
          future, and thus, it is recommended to use *note
          SymbolTableType: 1500. members instead of hard-coded strings.

      -- 方法: get_id ()

          回傳表的識別器。

      -- 方法: get_name ()

          回傳表的名稱。如果表用於類別，則這是類別的名稱；如果表用於函式
          ，則這是函式的名稱；如果表是全域的，則為 ‘'top'’ （*note
          get_type(): 1501. 會回傳 ‘'module'’）。對於型別參數作用域（用
          於泛型類別、函式和型別別名），它是底層類別、函式或型別別名的名
          稱。對於型別別名作用域，它是型別別名的名稱。對於 *note
          TypeVar: 141. 綁定範圍，它會是 ‘TypeVar’ 的名稱。

      -- 方法: get_lineno ()

          回傳此表所代表的區塊中第一行的編號。

      -- 方法: is_optimized ()

          如果可以最佳化該表中的區域變數，則回傳 ‘True’。

      -- 方法: is_nested ()

          如果區塊是巢狀類別或函式，則回傳 ‘True’。

      -- 方法: has_children ()

          如果區塊內有巢狀命名空間，則回傳 ‘True’。這些可以通過 *note
          get_children(): 4443. 獲得。

      -- 方法: get_identifiers ()

          回傳包含表中符號之名稱的視圖物件 (view object)。請參閱*note
          視圖物件的文件: 2120.。

      -- 方法: lookup (name)

          在表中查找 'name' 並回傳一個 *note Symbol: 15c9. 實例。

      -- 方法: get_symbols ()

          回傳表中名稱的 *note Symbol: 15c9. 實例串列。

      -- 方法: get_children ()

          回傳巢狀符號表的串列。

 -- 類別: symtable.Function

     一個函式或方法的命名空間。該類別繼承自 *note SymbolTable: 4434.。

      -- 方法: get_parameters ()

          回傳一個包含此函式參數名稱的元組 (tuple)。

      -- 方法: get_locals ()

          回傳一個包含此函式中區域變數 (locals) 名稱的元組。

      -- 方法: get_globals ()

          回傳一個包含此函式中全域變數 (globals) 名稱的元組。

      -- 方法: get_nonlocals ()

          回傳一個包含此函式中非區域變數 (nonlocals) 名稱的元組。

      -- 方法: get_frees ()

          回傳一個包含此函式中自由變數 (free variables) 名稱的元組。

 -- 類別: symtable.Class

     一個類別的命名空間。該類別繼承自 *note SymbolTable: 4434.。

      -- 方法: get_methods ()

          回傳一個包含類別中聲明的類似方法之函式名稱的元組。

          Here, the term 'method' designates 'any' function defined in
          the class body via *note def: 13c5. or *note async def: 575.

          Functions defined in a deeper scope (e.g., in an inner class)
          are not picked up by *note get_methods(): 2c0.

          舉例來說：

               >>> import symtable
               >>> st = symtable.symtable('''
               ... def outer(): pass
               ...
               ... class A:
               ...    def f():
               ...        def w(): pass
               ...
               ...    def g(self): pass
               ...
               ...    @classmethod
               ...    async def h(cls): pass
               ...
               ...    global outer
               ...    def outer(self): pass
               ... ''', 'test', 'exec')
               >>> class_A = st.get_children()[1]
               >>> class_A.get_methods()
               ('f', 'g', 'h')

          Although ‘A().f()’ raises *note TypeError: 4dd. at runtime,
          ‘A.f’ is still considered as a method-like function.

 -- 類別: symtable.Symbol

     *note SymbolTable: 4434. 中的條目對應於來源中的識別器。建構函式不是
     公開的。

      -- 方法: get_name ()

          回傳符號的名稱。

      -- 方法: is_referenced ()

          如果該符號在其區塊中使用，則回傳 ‘True’。

      -- 方法: is_imported ()

          如果符號是從 import 陳述式建立的，則回傳 ‘True’。

      -- 方法: is_parameter ()

          如果符號是一個參數，則回傳 ‘True’。

      -- 方法: is_global ()

          如果符號是全域的，則回傳 ‘True’。

      -- 方法: is_nonlocal ()

          如果符號是非區域的，則回傳 ‘True’。

      -- 方法: is_declared_global ()

          如果使用全域陳述式將符號聲明為全域的，則回傳 ‘True’。

      -- 方法: is_local ()

          如果符號是其區塊的區域符號，則回傳 ‘True’。

      -- 方法: is_annotated ()

          如果符號有被註釋，則回傳 ‘True’。

          在 3.6 版被加入.

      -- 方法: is_free ()

          如果該符號在其區塊中被參照 (referenced) 但未被賦值 (assigned)，
          則回傳 ‘True’。

      -- 方法: is_assigned ()

          如果該符號被賦值到其區塊中，則回傳 ‘True’。

      -- 方法: is_namespace ()

          如果名稱綁定引入 (introduce) 新的命名空間，則回傳 ‘True’。

          如果名稱用作函式或類別陳述式的目標，則這將會是 true。

          舉例來說：

               >>> table = symtable.symtable("def some_func(): pass", "string", "exec")
               >>> table.lookup("some_func").is_namespace()
               True

          請注意，單個名稱可以綁定到多個物件。如果結果為 ‘True’，則該名
          稱也可能被綁定到其他物件，例如 int 或 list，而不會引入新的命名
          空間。

      -- 方法: get_namespaces ()

          回傳綁定到該名稱的命名空間的串列。

      -- 方法: get_namespace ()

          回傳綁定到該名稱的命名空間。如果該名稱綁定了多個命名空間或沒有
          命名空間，則會引發 *note ValueError: 1e7.。


File: python.info,  Node: Command-Line Usage<2>,  Prev: 檢查符號表,  Up: symtable --- 存取編譯器的符號表

5.32.2.3 Command-Line Usage
...........................

在 3.13 版被加入.

The *note symtable: c2. module can be executed as a script from the
command line.

     python -m symtable [infile...]

Symbol tables are generated for the specified Python source files and
dumped to stdout.  If no input file is specified, the content is read
from stdin.


File: python.info,  Node: token --- 與 Python 剖析樹一起使用的常數,  Next: keyword --- 檢驗 Python 關鍵字,  Prev: symtable --- 存取編譯器的符號表,  Up: Python 語言服務

5.32.3 ‘token’ -- 與 Python 剖析樹一起使用的常數
------------------------------------------------

'原始碼：'Lib/token.py(1)

__________________________________________________________________

This module provides constants which represent the numeric values of
leaf nodes of the parse tree (terminal tokens).  Refer to the file
‘Grammar/Tokens’ in the Python distribution for the definitions of the
names in the context of the language grammar.  The specific numeric
values which the names map to may change between Python versions.

The module also provides a mapping from numeric codes to names and some
functions.  The functions mirror definitions in the Python C header
files.

 -- 資料: token.tok_name

     Dictionary mapping the numeric values of the constants defined in
     this module back to name strings, allowing more human-readable
     representation of parse trees to be generated.

 -- 函式: token.ISTERMINAL (x)

     Return ‘True’ for terminal token values.

 -- 函式: token.ISNONTERMINAL (x)

     Return ‘True’ for non-terminal token values.

 -- 函式: token.ISEOF (x)

     Return ‘True’ if 'x' is the marker indicating the end of input.

The token constants are:

 -- 資料: token.ENDMARKER

 -- 資料: token.NAME

 -- 資料: token.NUMBER

 -- 資料: token.STRING

 -- 資料: token.NEWLINE

 -- 資料: token.INDENT

 -- 資料: token.DEDENT

 -- 資料: token.LPAR

     Token value for ‘"("’.

 -- 資料: token.RPAR

     Token value for ‘")"’.

 -- 資料: token.LSQB

     Token value for ‘"["’.

 -- 資料: token.RSQB

     Token value for ‘"]"’.

 -- 資料: token.COLON

     Token value for ‘":"’.

 -- 資料: token.COMMA

     Token value for ‘","’.

 -- 資料: token.SEMI

     Token value for ‘";"’.

 -- 資料: token.PLUS

     Token value for ‘"+"’.

 -- 資料: token.MINUS

     Token value for ‘"-"’.

 -- 資料: token.STAR

     Token value for ‘"*"’.

 -- 資料: token.SLASH

     Token value for ‘"/"’.

 -- 資料: token.VBAR

     Token value for ‘"|"’.

 -- 資料: token.AMPER

     Token value for ‘"&"’.

 -- 資料: token.LESS

     Token value for ‘"<"’.

 -- 資料: token.GREATER

     Token value for ‘">"’.

 -- 資料: token.EQUAL

     Token value for ‘"="’.

 -- 資料: token.DOT

     Token value for ‘"."’.

 -- 資料: token.PERCENT

     Token value for ‘"%"’.

 -- 資料: token.LBRACE

     Token value for ‘"{"’.

 -- 資料: token.RBRACE

     Token value for ‘"}"’.

 -- 資料: token.EQEQUAL

     Token value for ‘"=="’.

 -- 資料: token.NOTEQUAL

     Token value for ‘"!="’.

 -- 資料: token.LESSEQUAL

     Token value for ‘"<="’.

 -- 資料: token.GREATEREQUAL

     Token value for ‘">="’.

 -- 資料: token.TILDE

     Token value for ‘"~"’.

 -- 資料: token.CIRCUMFLEX

     Token value for ‘"^"’.

 -- 資料: token.LEFTSHIFT

     Token value for ‘"<<"’.

 -- 資料: token.RIGHTSHIFT

     Token value for ‘">>"’.

 -- 資料: token.DOUBLESTAR

     Token value for ‘"**"’.

 -- 資料: token.PLUSEQUAL

     Token value for ‘"+="’.

 -- 資料: token.MINEQUAL

     Token value for ‘"-="’.

 -- 資料: token.STAREQUAL

     Token value for ‘"*="’.

 -- 資料: token.SLASHEQUAL

     Token value for ‘"/="’.

 -- 資料: token.PERCENTEQUAL

     Token value for ‘"%="’.

 -- 資料: token.AMPEREQUAL

     Token value for ‘"&="’.

 -- 資料: token.VBAREQUAL

     Token value for ‘"|="’.

 -- 資料: token.CIRCUMFLEXEQUAL

     Token value for ‘"^="’.

 -- 資料: token.LEFTSHIFTEQUAL

     Token value for ‘"<<="’.

 -- 資料: token.RIGHTSHIFTEQUAL

     Token value for ‘">>="’.

 -- 資料: token.DOUBLESTAREQUAL

     Token value for ‘"**="’.

 -- 資料: token.DOUBLESLASH

     Token value for ‘"//"’.

 -- 資料: token.DOUBLESLASHEQUAL

     Token value for ‘"//="’.

 -- 資料: token.AT

     Token value for ‘"@"’.

 -- 資料: token.ATEQUAL

     Token value for ‘"@="’.

 -- 資料: token.RARROW

     Token value for ‘"->"’.

 -- 資料: token.ELLIPSIS

     Token value for ‘"..."’.

 -- 資料: token.COLONEQUAL

     Token value for ‘":="’.

 -- 資料: token.EXCLAMATION

     Token value for ‘"!"’.

 -- 資料: token.OP

 -- 資料: token.TYPE_IGNORE

 -- 資料: token.TYPE_COMMENT

 -- 資料: token.SOFT_KEYWORD

 -- 資料: token.FSTRING_START

 -- 資料: token.FSTRING_MIDDLE

 -- 資料: token.FSTRING_END

 -- 資料: token.COMMENT

 -- 資料: token.NL

 -- 資料: token.ERRORTOKEN

 -- 資料: token.N_TOKENS

 -- 資料: token.NT_OFFSET

The following token type values aren't used by the C tokenizer but are
needed for the *note tokenize: e4. module.

 -- 資料: token.COMMENT

     Token value used to indicate a comment.

 -- 資料: token.NL

     Token value used to indicate a non-terminating newline.  The *note
     NEWLINE: 4466. token indicates the end of a logical line of Python
     code; ‘NL’ tokens are generated when a logical line of code is
     continued over multiple physical lines.

 -- 資料: token.ENCODING

     Token value that indicates the encoding used to decode the source
     bytes into text.  The first token returned by *note
     tokenize.tokenize(): 481. will always be an ‘ENCODING’ token.

 -- 資料: token.TYPE_COMMENT

     Token value indicating that a type comment was recognized.  Such
     tokens are only produced when *note ast.parse(): 18e. is invoked
     with ‘type_comments=True’.

在 3.5 版的變更: Added ‘AWAIT’ and ‘ASYNC’ tokens.

在 3.7 版的變更: Added *note COMMENT: 44a0, *note NL: 44a1. and *note
ENCODING: 44a5. tokens.

在 3.7 版的變更: Removed ‘AWAIT’ and ‘ASYNC’ tokens.  "async" and
"await" are now tokenized as *note NAME: 4463. tokens.

在 3.8 版的變更: Added *note TYPE_COMMENT: 449b, *note TYPE_IGNORE:
449a, *note COLONEQUAL: 4497.  Added ‘AWAIT’ and ‘ASYNC’ tokens back
(they're needed to support parsing older Python versions for *note
ast.parse(): 18e. with ‘feature_version’ set to 6 or lower).

在 3.13 版的變更: Removed ‘AWAIT’ and ‘ASYNC’ tokens again.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/token.py


File: python.info,  Node: keyword --- 檢驗 Python 關鍵字,  Next: tokenize --- Tokenizer for Python source,  Prev: token --- 與 Python 剖析樹一起使用的常數,  Up: Python 語言服務

5.32.4 ‘keyword’ -- 檢驗 Python 關鍵字
--------------------------------------

'原始碼：'Lib/keyword.py(1)

__________________________________________________________________

此模組允許 Python 程式確定某個字串是否為*note 關鍵字: 1d8e. 或*note
軟關鍵字 (soft keyword): 7b0.。

 -- 函式: keyword.iskeyword (s)

     如果 's' 是一個 Python *note 關鍵字: 1d8e.則回傳 ‘True’。

 -- 資料: keyword.kwlist

     包含直譯器定義的所有 *note 關鍵字: 1d8e. 的序列。如果所定義的任何關
     鍵字僅在特定 *note __future__: 0. 陳述式生效時被啟用，它們也將被包
     含在內。

 -- 函式: keyword.issoftkeyword (s)

     如果 's' 是一個 Python *note 軟關鍵字: 7b0. 則回傳 ‘True’。

     在 3.9 版被加入.

 -- 資料: keyword.softkwlist

     包含直譯器定義的所有 *note 軟關鍵字: 7b0. 的序列。如果所定義的任何
     軟關鍵字僅在特定 *note __future__: 0. 陳述式生效時被啟用，它們也將
     被包含在內。

     在 3.9 版被加入.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/keyword.py


File: python.info,  Node: tokenize --- Tokenizer for Python source,  Next: tabnanny --- 偵測不良縮排,  Prev: keyword --- 檢驗 Python 關鍵字,  Up: Python 語言服務

5.32.5 ‘tokenize’ -- Tokenizer for Python source
------------------------------------------------

'原始碼：'Lib/tokenize.py(1)

__________________________________________________________________

The *note tokenize: e4. module provides a lexical scanner for Python
source code, implemented in Python.  The scanner in this module returns
comments as tokens as well, making it useful for implementing
"pretty-printers", including colorizers for on-screen displays.

To simplify token stream handling, all *note operator: 1dce. and *note
delimiter: 1dcf. tokens and *note Ellipsis: 2062. are returned using the
generic *note OP: 4499. token type.  The exact type can be determined by
checking the ‘exact_type’ property on the *note named tuple: 5f4.
returned from *note tokenize.tokenize(): 481.

     警告: Note that the functions in this module are only designed to
     parse syntactically valid Python code (code that does not raise
     when parsed using *note ast.parse(): 18e.).  The behavior of the
     functions in this module is 'undefined' when providing invalid
     Python code and it can change at any point.

* Menu:

* Tokenizing Input::
* Command-Line Usage: Command-Line Usage<3>.
* 範例: 範例<47>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/tokenize.py


File: python.info,  Node: Tokenizing Input,  Next: Command-Line Usage<3>,  Up: tokenize --- Tokenizer for Python source

5.32.5.1 Tokenizing Input
.........................

The primary entry point is a *note generator: 1004.:

 -- 函式: tokenize.tokenize (readline)

     The *note tokenize(): 481. generator requires one argument,
     'readline', which must be a callable object which provides the same
     interface as the *note io.IOBase.readline(): 12bd. method of file
     objects.  Each call to the function should return one line of input
     as bytes.

     The generator produces 5-tuples with these members: the token type;
     the token string; a 2-tuple ‘(srow, scol)’ of ints specifying the
     row and column where the token begins in the source; a 2-tuple
     ‘(erow, ecol)’ of ints specifying the row and column where the
     token ends in the source; and the line on which the token was
     found.  The line passed (the last tuple item) is the 'physical'
     line.  The 5 tuple is returned as a *note named tuple: 5f4. with
     the field names: ‘type string start end line’.

     The returned *note named tuple: 5f4. has an additional property
     named ‘exact_type’ that contains the exact operator type for *note
     OP: 4499. tokens.  For all other token types ‘exact_type’ equals
     the named tuple ‘type’ field.

     在 3.1 版的變更: 新增附名元組 (named tuple) 的支援。

     在 3.3 版的變更: 新增 ‘exact_type’ 的支援。

     *note tokenize(): 481. determines the source encoding of the file
     by looking for a UTF-8 BOM or encoding cookie, according to PEP
     263(1).

 -- 函式: tokenize.generate_tokens (readline)

     Tokenize a source reading unicode strings instead of bytes.

     Like *note tokenize(): 481, the 'readline' argument is a callable
     returning a single line of input.  However, *note
     generate_tokens(): 482. expects 'readline' to return a str object
     rather than bytes.

     The result is an iterator yielding named tuples, exactly like *note
     tokenize(): 481.  It does not yield an *note ENCODING: 44a5. token.

All constants from the *note token: e3. module are also exported from
*note tokenize: e4.

Another function is provided to reverse the tokenization process.  This
is useful for creating tools that tokenize a script, modify the token
stream, and write back the modified script.

 -- 函式: tokenize.untokenize (iterable)

     Converts tokens back into Python source code.  The 'iterable' must
     return sequences with at least two elements, the token type and the
     token string.  Any additional sequence elements are ignored.

     The reconstructed script is returned as a single string.  The
     result is guaranteed to tokenize back to match the input so that
     the conversion is lossless and round-trips are assured.  The
     guarantee applies only to the token type and token string as the
     spacing between tokens (column positions) may change.

     It returns bytes, encoded using the *note ENCODING: 44a5. token,
     which is the first token sequence output by *note tokenize(): 481.
     If there is no encoding token in the input, it returns a str
     instead.

*note tokenize(): 481. needs to detect the encoding of source files it
tokenizes.  The function it uses to do this is available:

 -- 函式: tokenize.detect_encoding (readline)

     The *note detect_encoding(): 2744. function is used to detect the
     encoding that should be used to decode a Python source file.  It
     requires one argument, readline, in the same way as the *note
     tokenize(): 481. generator.

     It will call readline a maximum of twice, and return the encoding
     used (as a string) and a list of any lines (not decoded from bytes)
     it has read in.

     It detects the encoding from the presence of a UTF-8 BOM or an
     encoding cookie as specified in PEP 263(2).  If both a BOM and a
     cookie are present, but disagree, a *note SyntaxError: 173. will be
     raised.  Note that if the BOM is found, ‘'utf-8-sig'’ will be
     returned as an encoding.

     If no encoding is specified, then the default of ‘'utf-8'’ will be
     returned.

     Use *note open(): 2743. to open Python source files: it uses *note
     detect_encoding(): 2744. to detect the file encoding.

 -- 函式: tokenize.open (filename)

     Open a file in read only mode using the encoding detected by *note
     detect_encoding(): 2744.

     在 3.2 版被加入.

 -- 例外: tokenize.TokenError

     Raised when either a docstring or expression that may be split over
     several lines is not completed anywhere in the file, for example:

          """Beginning of
          docstring

     或是：

          [1,
           2,
           3

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0263/

   (2) https://peps.python.org/pep-0263/


File: python.info,  Node: Command-Line Usage<3>,  Next: 範例<47>,  Prev: Tokenizing Input,  Up: tokenize --- Tokenizer for Python source

5.32.5.2 Command-Line Usage
...........................

在 3.3 版被加入.

The *note tokenize: e4. module can be executed as a script from the
command line.  It is as simple as:

     python -m tokenize [-e] [filename.py]

The following options are accepted:

 -- Option: -h, --help

     show this help message and exit

 -- Option: -e, --exact

     display token names using the exact type

If ‘filename.py’ is specified its contents are tokenized to stdout.
Otherwise, tokenization is performed on stdin.


File: python.info,  Node: 範例<47>,  Prev: Command-Line Usage<3>,  Up: tokenize --- Tokenizer for Python source

5.32.5.3 範例
.............

Example of a script rewriter that transforms float literals into Decimal
objects:

     from tokenize import tokenize, untokenize, NUMBER, STRING, NAME, OP
     from io import BytesIO

     def decistmt(s):
         """Substitute Decimals for floats in a string of statements.

         >>> from decimal import Decimal
         >>> s = 'print(+21.3e-5*-.1234/81.7)'
         >>> decistmt(s)
         "print (+Decimal ('21.3e-5')*-Decimal ('.1234')/Decimal ('81.7'))"

         The format of the exponent is inherited from the platform C library.
         Known cases are "e-007" (Windows) and "e-07" (not Windows).  Since
         we're only showing 12 digits, and the 13th isn't close to 5, the
         rest of the output should be platform-independent.

         >>> exec(s)  #doctest: +ELLIPSIS
         -3.21716034272e-0...7

         Output from calculations with Decimal should be identical across all
         platforms.

         >>> exec(decistmt(s))
         -3.217160342717258261933904529E-7
         """
         result = []
         g = tokenize(BytesIO(s.encode('utf-8')).readline)  # tokenize the string
         for toknum, tokval, _, _, _ in g:
             if toknum == NUMBER and '.' in tokval:  # replace NUMBER tokens
                 result.extend([
                     (NAME, 'Decimal'),
                     (OP, '('),
                     (STRING, repr(tokval)),
                     (OP, ')')
                 ])
             else:
                 result.append((toknum, tokval))
         return untokenize(result).decode('utf-8')

Example of tokenizing from the command line.  The script:

     def say_hello():
         print("Hello, World!")

     say_hello()

will be tokenized to the following output where the first column is the
range of the line/column coordinates where the token is found, the
second column is the name of the token, and the final column is the
value of the token (if any)

     $ python -m tokenize hello.py
     0,0-0,0:            ENCODING       'utf-8'
     1,0-1,3:            NAME           'def'
     1,4-1,13:           NAME           'say_hello'
     1,13-1,14:          OP             '('
     1,14-1,15:          OP             ')'
     1,15-1,16:          OP             ':'
     1,16-1,17:          NEWLINE        '\n'
     2,0-2,4:            INDENT         '    '
     2,4-2,9:            NAME           'print'
     2,9-2,10:           OP             '('
     2,10-2,25:          STRING         '"Hello, World!"'
     2,25-2,26:          OP             ')'
     2,26-2,27:          NEWLINE        '\n'
     3,0-3,1:            NL             '\n'
     4,0-4,0:            DEDENT         ''
     4,0-4,9:            NAME           'say_hello'
     4,9-4,10:           OP             '('
     4,10-4,11:          OP             ')'
     4,11-4,12:          NEWLINE        '\n'
     5,0-5,0:            ENDMARKER      ''

The exact token type names can be displayed using the *note -e: 44b2.
option:

     $ python -m tokenize -e hello.py
     0,0-0,0:            ENCODING       'utf-8'
     1,0-1,3:            NAME           'def'
     1,4-1,13:           NAME           'say_hello'
     1,13-1,14:          LPAR           '('
     1,14-1,15:          RPAR           ')'
     1,15-1,16:          COLON          ':'
     1,16-1,17:          NEWLINE        '\n'
     2,0-2,4:            INDENT         '    '
     2,4-2,9:            NAME           'print'
     2,9-2,10:           LPAR           '('
     2,10-2,25:          STRING         '"Hello, World!"'
     2,25-2,26:          RPAR           ')'
     2,26-2,27:          NEWLINE        '\n'
     3,0-3,1:            NL             '\n'
     4,0-4,0:            DEDENT         ''
     4,0-4,9:            NAME           'say_hello'
     4,9-4,10:           LPAR           '('
     4,10-4,11:          RPAR           ')'
     4,11-4,12:          NEWLINE        '\n'
     5,0-5,0:            ENDMARKER      ''

Example of tokenizing a file programmatically, reading unicode strings
instead of bytes with *note generate_tokens(): 482.:

     import tokenize

     with tokenize.open('hello.py') as f:
         tokens = tokenize.generate_tokens(f.readline)
         for token in tokens:
             print(token)

Or reading bytes directly with *note tokenize(): 481.:

     import tokenize

     with open('hello.py', 'rb') as f:
         tokens = tokenize.tokenize(f.readline)
         for token in tokens:
             print(token)


File: python.info,  Node: tabnanny --- 偵測不良縮排,  Next: pyclbr --- Python 模組瀏覽器支援,  Prev: tokenize --- Tokenizer for Python source,  Up: Python 語言服務

5.32.6 ‘tabnanny’ -- 偵測不良縮排
---------------------------------

'原始碼：'Lib/tabnanny.py(1)

__________________________________________________________________

目前現況是此模組打算以腳本方式被呼叫使用，但也可以將其引入於 IDE 中並使
用下方敘述的 *note check(): 44b7. 函式。

     備註: 此模組所提供的 API 很有可能會在未來的發佈版本中有所變更，且有
     可能不具有向後相容性。

 -- 函式: tabnanny.check (file_or_dir)

     如果 'file_or_dir' 是個目錄且並非符號鏈接 (symbolic link)，則會遞迴
     地在名為 'file_or_dir' 的目錄樹 (directory tree) 中不斷下行檢查所有
     ‘.py’ 檔案。如果 'file_or_dir' 是個一般 Python 原始檔案，則為其檢查
     空格相關問題。診斷訊息會以 *note print(): f18. 函式輸出至標準輸出
     (standard output) 當中。

 -- 資料: tabnanny.verbose

     標示是否要印出詳細訊息 (verbose message) 的旗標，若是以腳本方式呼叫
     的話則可以用 ‘-v’ 選項來增加。

 -- 資料: tabnanny.filename_only

     標示是否要只印出那些有空白相關問題檔案之檔名的旗標，若是以腳本方式
     呼叫的話則可以用 ‘-q’ 選項來設為真值。

 -- 例外: tabnanny.NannyNag

     當偵測到不良縮排時，此例外會被 *note process_tokens(): 44bb. 引發，
     會在 *note check(): 44b7. 中捕獲與處理。

 -- 函式: tabnanny.process_tokens (tokens)

     此函式被 *note check(): 44b7. 用來處理由 *note tokenize: e4. 產生的
     標記 (token)。

也參考
......

*note tokenize: e4. 模組

     Python 原始程式碼的詞彙掃描器 (lexical scanner)。

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/tabnanny.py


File: python.info,  Node: pyclbr --- Python 模組瀏覽器支援,  Next: py_compile — 編譯 Python 來源檔案,  Prev: tabnanny --- 偵測不良縮排,  Up: Python 語言服務

5.32.7 ‘pyclbr’ -- Python 模組瀏覽器支援
----------------------------------------

'原始碼：'Lib/pyclbr.py(1)

__________________________________________________________________

The *note pyclbr: a2. module provides limited information about the
functions, classes, and methods defined in a Python-coded module.  The
information is sufficient to implement a module browser.  The
information is extracted from the Python source code rather than by
importing the module, so this module is safe to use with untrusted code.
This restriction makes it impossible to use this module with modules not
implemented in Python, including all standard and optional extension
modules.

 -- 函式: pyclbr.readmodule (module, path=None)

     Return a dictionary mapping module-level class names to class
     descriptors.  If possible, descriptors for imported base classes
     are included.  Parameter 'module' is a string with the name of the
     module to read; it may be the name of a module within a package.
     If given, 'path' is a sequence of directory paths prepended to
     ‘sys.path’, which is used to locate the module source code.

     This function is the original interface and is only kept for back
     compatibility.  It returns a filtered version of the following.

 -- 函式: pyclbr.readmodule_ex (module, path=None)

     Return a dictionary-based tree containing a function or class
     descriptors for each function and class defined in the module with
     a ‘def’ or ‘class’ statement.  The returned dictionary maps
     module-level function and class names to their descriptors.  Nested
     objects are entered into the children dictionary of their parent.
     As with readmodule, 'module' names the module to be read and 'path'
     is prepended to sys.path.  If the module being read is a package,
     the returned dictionary has a key ‘'__path__'’ whose value is a
     list containing the package search path.

在 3.7 版被加入: Descriptors for nested definitions.  They are accessed
through the new children attribute.  Each has a new parent attribute.

The descriptors returned by these functions are instances of Function
and Class classes.  Users are not expected to create instances of these
classes.

* Menu:

* 函式物件::
* Class Objects::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/pyclbr.py


File: python.info,  Node: 函式物件,  Next: Class Objects,  Up: pyclbr --- Python 模組瀏覽器支援

5.32.7.1 函式物件
.................

 -- 類別: pyclbr.Function

     Class ‘Function’ instances describe functions defined by def
     statements.  They have the following attributes:

      -- 屬性: file

          Name of the file in which the function is defined.

      -- 屬性: module

          The name of the module defining the function described.

      -- 屬性: name

          The name of the function.

      -- 屬性: lineno

          The line number in the file where the definition starts.

      -- 屬性: parent

          For top-level functions, ‘None’.  For nested functions, the
          parent.

          在 3.7 版被加入.

      -- 屬性: children

          A *note dictionary: 23b. mapping names to descriptors for
          nested functions and classes.

          在 3.7 版被加入.

      -- 屬性: is_async

          ‘True’ for functions that are defined with the *note async:
          575. prefix, ‘False’ otherwise.

          在 3.10 版被加入.


File: python.info,  Node: Class Objects,  Prev: 函式物件,  Up: pyclbr --- Python 模組瀏覽器支援

5.32.7.2 Class Objects
......................

 -- 類別: pyclbr.Class

     Class ‘Class’ instances describe classes defined by class
     statements.  They have the same attributes as *note Functions:
     44c0. and two more.

      -- 屬性: file

          Name of the file in which the class is defined.

      -- 屬性: module

          The name of the module defining the class described.

      -- 屬性: name

          The name of the class.

      -- 屬性: lineno

          The line number in the file where the definition starts.

      -- 屬性: parent

          For top-level classes, ‘None’.  For nested classes, the
          parent.

          在 3.7 版被加入.

      -- 屬性: children

          A dictionary mapping names to descriptors for nested functions
          and classes.

          在 3.7 版被加入.

      -- 屬性: super

          A list of ‘Class’ objects which describe the immediate base
          classes of the class being described.  Classes which are named
          as superclasses but which are not discoverable by *note
          readmodule_ex(): 7d0. are listed as a string with the class
          name instead of as ‘Class’ objects.

      -- 屬性: methods

          A *note dictionary: 23b. mapping method names to line numbers.
          This can be derived from the newer *note children: 44d0.
          dictionary, but remains for back-compatibility.


File: python.info,  Node: py_compile — 編譯 Python 來源檔案,  Next: compileall --- 位元組編譯 Python 函式庫,  Prev: pyclbr --- Python 模組瀏覽器支援,  Up: Python 語言服務

5.32.8 ‘py_compile’ — 編譯 Python 來源檔案
------------------------------------------

'原始碼：'Lib/py_compile.py(1)

__________________________________________________________________

The *note py_compile: a1. module provides a function to generate a
byte-code file from a source file, and another function used when the
module source file is invoked as a script.

Though not often needed, this function can be useful when installing
modules for shared use, especially if some of the users may not have
permission to write the byte-code cache files in the directory
containing the source code.

 -- 例外: py_compile.PyCompileError

     Exception raised when an error occurs while attempting to compile
     the file.

 -- 函式: py_compile.compile (file, cfile=None, dfile=None,
          doraise=False, optimize=-1,
          invalidation_mode=PycInvalidationMode.TIMESTAMP, quiet=0)

     Compile a source file to byte-code and write out the byte-code
     cache file.  The source code is loaded from the file named 'file'.
     The byte-code is written to 'cfile', which defaults to the PEP
     3147(2)/ PEP 488(3) path, ending in ‘.pyc’.  For example, if 'file'
     is ‘/foo/bar/baz.py’ 'cfile' will default to
     ‘/foo/bar/__pycache__/baz.cpython-32.pyc’ for Python 3.2.  If
     'dfile' is specified, it is used instead of 'file' as the name of
     the source file from which source lines are obtained for display in
     exception tracebacks.  If 'doraise' is true, a *note
     PyCompileError: 44d5. is raised when an error is encountered while
     compiling 'file'.  If 'doraise' is false (the default), an error
     string is written to ‘sys.stderr’, but no exception is raised.
     This function returns the path to byte-compiled file, i.e.
     whatever 'cfile' value was used.

     The 'doraise' and 'quiet' arguments determine how errors are
     handled while compiling file.  If 'quiet' is 0 or 1, and 'doraise'
     is false, the default behaviour is enabled: an error string is
     written to ‘sys.stderr’, and the function returns ‘None’ instead of
     a path.  If 'doraise' is true, a *note PyCompileError: 44d5. is
     raised instead.  However if 'quiet' is 2, no message is written,
     and 'doraise' has no effect.

     If the path that 'cfile' becomes (either explicitly specified or
     computed) is a symlink or non-regular file, *note FileExistsError:
     fc3. will be raised.  This is to act as a warning that import will
     turn those paths into regular files if it is allowed to write
     byte-compiled files to those paths.  This is a side-effect of
     import using file renaming to place the final byte-compiled file
     into place to prevent concurrent file writing issues.

     'optimize' controls the optimization level and is passed to the
     built-in *note compile(): 178. function.  The default of ‘-1’
     selects the optimization level of the current interpreter.

     'invalidation_mode' should be a member of the *note
     PycInvalidationMode: 44d6. enum and controls how the generated
     bytecode cache is invalidated at runtime.  The default is *note
     PycInvalidationMode.CHECKED_HASH: 44d7. if the ‘SOURCE_DATE_EPOCH’
     environment variable is set, otherwise the default is *note
     PycInvalidationMode.TIMESTAMP: 44d8.

     在 3.2 版的變更: Changed default value of 'cfile' to be PEP
     3147(4)-compliant.  Previous default was 'file' + ‘'c'’ (‘'o'’ if
     optimization was enabled).  Also added the 'optimize' parameter.

     在 3.4 版的變更: Changed code to use *note importlib: 6b. for the
     byte-code cache file writing.  This means file creation/writing
     semantics now match what *note importlib: 6b. does, e.g.
     permissions, write-and-move semantics, etc.  Also added the caveat
     that *note FileExistsError: fc3. is raised if 'cfile' is a symlink
     or non-regular file.

     在 3.7 版的變更: The 'invalidation_mode' parameter was added as
     specified in PEP 552(5).  If the ‘SOURCE_DATE_EPOCH’ environment
     variable is set, 'invalidation_mode' will be forced to *note
     PycInvalidationMode.CHECKED_HASH: 44d7.

     在 3.7.2 版的變更: The ‘SOURCE_DATE_EPOCH’ environment variable no
     longer overrides the value of the 'invalidation_mode' argument, and
     determines its default value instead.

     在 3.8 版的變更: 新增 'quiet' 參數。

 -- 類別: py_compile.PycInvalidationMode

     An enumeration of possible methods the interpreter can use to
     determine whether a bytecode file is up to date with a source file.
     The ‘.pyc’ file indicates the desired invalidation mode in its
     header.  See *note Cached bytecode invalidation: 590. for more
     information on how Python invalidates ‘.pyc’ files at runtime.

     在 3.7 版被加入.

      -- 屬性: TIMESTAMP

          The ‘.pyc’ file includes the timestamp and size of the source
          file, which Python will compare against the metadata of the
          source file at runtime to determine if the ‘.pyc’ file needs
          to be regenerated.

      -- 屬性: CHECKED_HASH

          The ‘.pyc’ file includes a hash of the source file content,
          which Python will compare against the source at runtime to
          determine if the ‘.pyc’ file needs to be regenerated.

      -- 屬性: UNCHECKED_HASH

          Like *note CHECKED_HASH: 44d7, the ‘.pyc’ file includes a hash
          of the source file content.  However, Python will at runtime
          assume the ‘.pyc’ file is up to date and not validate the
          ‘.pyc’ against the source file at all.

          This option is useful when the ‘.pycs’ are kept up to date by
          some system external to Python like a build system.

* Menu:

* Command-Line Interface: Command-Line Interface<3>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/py_compile.py

   (2) https://peps.python.org/pep-3147/

   (3) https://peps.python.org/pep-0488/

   (4) https://peps.python.org/pep-3147/

   (5) https://peps.python.org/pep-0552/


File: python.info,  Node: Command-Line Interface<3>,  Up: py_compile — 編譯 Python 來源檔案

5.32.8.1 Command-Line Interface
...............................

This module can be invoked as a script to compile several source files.
The files named in 'filenames' are compiled and the resulting bytecode
is cached in the normal manner.  This program does not search a
directory structure to locate source files; it only compiles files named
explicitly.  The exit status is nonzero if one of the files could not be
compiled.

 -- Option: <file> ... <fileN>
 -- Option: -

     Positional arguments are files to compile.  If ‘-’ is the only
     parameter, the list of files is taken from standard input.

 -- Option: -q, --quiet

     Suppress errors output.

在 3.2 版的變更: 新增對 ‘-’ 的支援。

在 3.10 版的變更: 新增對 *note -q: 44de. 的支援。

也參考
......

*note compileall: 19. 模組

     Utilities to compile all Python source files in a directory tree.


File: python.info,  Node: compileall --- 位元組編譯 Python 函式庫,  Next: dis --- Python bytecode 的反組譯器,  Prev: py_compile — 編譯 Python 來源檔案,  Up: Python 語言服務

5.32.9 ‘compileall’ -- 位元組編譯 Python 函式庫
-----------------------------------------------

'原始碼：'Lib/compileall.py(1)

__________________________________________________________________

This module provides some utility functions to support installing Python
libraries.  These functions compile Python source files in a directory
tree.  This module can be used to create the cached byte-code files at
library installation time, which makes them available for use even by
users who don't have write permission to the library directories.

*note Availability: 1c56.: not WASI.

This module does not work or is not available on WebAssembly.  See *note
WebAssembly 平台: 16e6. for more information.

* Menu:

* Command-line use::
* Public functions::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/compileall.py


File: python.info,  Node: Command-line use,  Next: Public functions,  Up: compileall --- 位元組編譯 Python 函式庫

5.32.9.1 Command-line use
.........................

This module can work as a script (using ‘python -m compileall’) to
compile Python sources.

 -- Option: directory ...
 -- Option: file ...

     Positional arguments are files to compile or directories that
     contain source files, traversed recursively.  If no argument is
     given, behave as if the command line was ‘-l <DIRECTORIES FROM
     SYS.PATH>’.

 -- Option: -l

     Do not recurse into subdirectories, only compile source code files
     directly contained in the named or implied directories.

 -- Option: -f

     Force rebuild even if timestamps are up-to-date.

 -- Option: -q

     Do not print the list of files compiled.  If passed once, error
     messages will still be printed.  If passed twice (‘-qq’), all
     output is suppressed.

 -- Option: -d destdir

     Directory prepended to the path to each file being compiled.  This
     will appear in compilation time tracebacks, and is also compiled in
     to the byte-code file, where it will be used in tracebacks and
     other messages in cases where the source file does not exist at the
     time the byte-code file is executed.

 -- Option: -s strip_prefix

 -- Option: -p prepend_prefix

     Remove (‘-s’) or append (‘-p’) the given prefix of paths recorded
     in the ‘.pyc’ files.  Cannot be combined with ‘-d’.

 -- Option: -x regex

     regex is used to search the full path to each file considered for
     compilation, and if the regex produces a match, the file is
     skipped.

 -- Option: -i list

     Read the file ‘list’ and add each line that it contains to the list
     of files and directories to compile.  If ‘list’ is ‘-’, read lines
     from ‘stdin’.

 -- Option: -b

     Write the byte-code files to their legacy locations and names,
     which may overwrite byte-code files created by another version of
     Python.  The default is to write files to their PEP 3147(1)
     locations and names, which allows byte-code files from multiple
     versions of Python to coexist.

 -- Option: -r

     Control the maximum recursion level for subdirectories.  If this is
     given, then ‘-l’ option will not be taken into account.  ‘python -m
     compileall <directory> -r 0’ is equivalent to ‘python -m compileall
     <directory> -l’.

 -- Option: -j N

     Use 'N' workers to compile the files within the given directory.
     If ‘0’ is used, then the result of *note os.process_cpu_count():
     1a7. will be used.

 -- Option: --invalidation-mode [timestamp|checked-hash|unchecked-hash]

     Control how the generated byte-code files are invalidated at
     runtime.  The ‘timestamp’ value, means that ‘.pyc’ files with the
     source timestamp and size embedded will be generated.  The
     ‘checked-hash’ and ‘unchecked-hash’ values cause hash-based pycs to
     be generated.  Hash-based pycs embed a hash of the source file
     contents rather than a timestamp.  See *note Cached bytecode
     invalidation: 590. for more information on how Python validates
     bytecode cache files at runtime.  The default is ‘timestamp’ if the
     ‘SOURCE_DATE_EPOCH’ environment variable is not set, and
     ‘checked-hash’ if the ‘SOURCE_DATE_EPOCH’ environment variable is
     set.

 -- Option: -o level

     Compile with the given optimization level.  May be used multiple
     times to compile for multiple levels at a time (for example,
     ‘compileall -o 1 -o 2’).

 -- Option: -e dir

     Ignore symlinks pointing outside the given directory.

 -- Option: --hardlink-dupes

     If two ‘.pyc’ files with different optimization level have the same
     content, use hard links to consolidate duplicate files.

在 3.2 版的變更: 新增選項 ‘-i’、‘-b’ 與 ‘-h’。

在 3.5 版的變更: Added the ‘-j’, ‘-r’, and ‘-qq’ options.  ‘-q’ option
was changed to a multilevel value.  ‘-b’ will always produce a byte-code
file ending in ‘.pyc’, never ‘.pyo’.

在 3.7 版的變更: 新增選項 ‘--invalidation-mode’。

在 3.9 版的變更: Added the ‘-s’, ‘-p’, ‘-e’ and ‘--hardlink-dupes’
options.  Raised the default recursion limit from 10 to *note
sys.getrecursionlimit(): 46b.  Added the possibility to specify the ‘-o’
option multiple times.

There is no command-line option to control the optimization level used
by the *note compile(): 178. function, because the Python interpreter
itself already provides the option: ‘python -O -m compileall’.

Similarly, the *note compile(): 178. function respects the *note
sys.pycache_prefix: 948. setting.  The generated bytecode cache will
only be useful if *note compile(): 178. is run with the same *note
sys.pycache_prefix: 948. (if any) that will be used at runtime.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3147/


File: python.info,  Node: Public functions,  Prev: Command-line use,  Up: compileall --- 位元組編譯 Python 函式庫

5.32.9.2 Public functions
.........................

 -- 函式: compileall.compile_dir (dir,
          maxlevels=sys.getrecursionlimit(), ddir=None, force=False,
          rx=None, quiet=0, legacy=False, optimize=-1, workers=1,
          invalidation_mode=None, *, stripdir=None, prependdir=None,
          limit_sl_dest=None, hardlink_dupes=False)

     Recursively descend the directory tree named by 'dir', compiling
     all ‘.py’ files along the way.  Return a true value if all the
     files compiled successfully, and a false value otherwise.

     The 'maxlevels' parameter is used to limit the depth of the
     recursion; it defaults to ‘sys.getrecursionlimit()’.

     If 'ddir' is given, it is prepended to the path to each file being
     compiled for use in compilation time tracebacks, and is also
     compiled in to the byte-code file, where it will be used in
     tracebacks and other messages in cases where the source file does
     not exist at the time the byte-code file is executed.

     If 'force' is true, modules are re-compiled even if the timestamps
     are up to date.

     If 'rx' is given, its ‘search’ method is called on the complete
     path to each file considered for compilation, and if it returns a
     true value, the file is skipped.  This can be used to exclude files
     matching a regular expression, given as a *note re.Pattern: f29.
     object.

     If 'quiet' is ‘False’ or ‘0’ (the default), the filenames and other
     information are printed to standard out.  Set to ‘1’, only errors
     are printed.  Set to ‘2’, all output is suppressed.

     If 'legacy' is true, byte-code files are written to their legacy
     locations and names, which may overwrite byte-code files created by
     another version of Python.  The default is to write files to their
     PEP 3147(1) locations and names, which allows byte-code files from
     multiple versions of Python to coexist.

     'optimize' specifies the optimization level for the compiler.  It
     is passed to the built-in *note compile(): 178. function.  Accepts
     also a sequence of optimization levels which lead to multiple
     compilations of one ‘.py’ file in one call.

     The argument 'workers' specifies how many workers are used to
     compile files in parallel.  The default is to not use multiple
     workers.  If the platform can't use multiple workers and 'workers'
     argument is given, then sequential compilation will be used as a
     fallback.  If 'workers' is 0, the number of cores in the system is
     used.  If 'workers' is lower than ‘0’, a *note ValueError: 1e7.
     will be raised.

     'invalidation_mode' should be a member of the *note
     py_compile.PycInvalidationMode: 44d6. enum and controls how the
     generated pycs are invalidated at runtime.

     The 'stripdir', 'prependdir' and 'limit_sl_dest' arguments
     correspond to the ‘-s’, ‘-p’ and ‘-e’ options described above.
     They may be specified as ‘str’ or *note os.PathLike: bf8.

     If 'hardlink_dupes' is true and two ‘.pyc’ files with different
     optimization level have the same content, use hard links to
     consolidate duplicate files.

     在 3.2 版的變更: 新增 'legacy' 與 'optimize' 參數。

     在 3.5 版的變更: 新增 'workers' 參數。

     在 3.5 版的變更: 'quiet' parameter was changed to a multilevel
     value.

     在 3.5 版的變更: The 'legacy' parameter only writes out ‘.pyc’
     files, not ‘.pyo’ files no matter what the value of 'optimize' is.

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

     在 3.7 版的變更: 新增 'invalidation_mode' 參數。

     在 3.7.2 版的變更: 新增 'invalidation_mode' 參數的預設值被更新為
     ‘None’。

     在 3.8 版的變更: Setting 'workers' to 0 now chooses the optimal
     number of cores.

     在 3.9 版的變更: Added 'stripdir', 'prependdir', 'limit_sl_dest'
     and 'hardlink_dupes' arguments.  Default value of 'maxlevels' was
     changed from ‘10’ to ‘sys.getrecursionlimit()’

 -- 函式: compileall.compile_file (fullname, ddir=None, force=False,
          rx=None, quiet=0, legacy=False, optimize=-1,
          invalidation_mode=None, *, stripdir=None, prependdir=None,
          limit_sl_dest=None, hardlink_dupes=False)

     Compile the file with path 'fullname'.  Return a true value if the
     file compiled successfully, and a false value otherwise.

     If 'ddir' is given, it is prepended to the path to the file being
     compiled for use in compilation time tracebacks, and is also
     compiled in to the byte-code file, where it will be used in
     tracebacks and other messages in cases where the source file does
     not exist at the time the byte-code file is executed.

     If 'rx' is given, its ‘search’ method is passed the full path name
     to the file being compiled, and if it returns a true value, the
     file is not compiled and ‘True’ is returned.  This can be used to
     exclude files matching a regular expression, given as a *note
     re.Pattern: f29. object.

     If 'quiet' is ‘False’ or ‘0’ (the default), the filenames and other
     information are printed to standard out.  Set to ‘1’, only errors
     are printed.  Set to ‘2’, all output is suppressed.

     If 'legacy' is true, byte-code files are written to their legacy
     locations and names, which may overwrite byte-code files created by
     another version of Python.  The default is to write files to their
     PEP 3147(2) locations and names, which allows byte-code files from
     multiple versions of Python to coexist.

     'optimize' specifies the optimization level for the compiler.  It
     is passed to the built-in *note compile(): 178. function.  Accepts
     also a sequence of optimization levels which lead to multiple
     compilations of one ‘.py’ file in one call.

     'invalidation_mode' should be a member of the *note
     py_compile.PycInvalidationMode: 44d6. enum and controls how the
     generated pycs are invalidated at runtime.

     The 'stripdir', 'prependdir' and 'limit_sl_dest' arguments
     correspond to the ‘-s’, ‘-p’ and ‘-e’ options described above.
     They may be specified as ‘str’ or *note os.PathLike: bf8.

     If 'hardlink_dupes' is true and two ‘.pyc’ files with different
     optimization level have the same content, use hard links to
     consolidate duplicate files.

     在 3.2 版被加入.

     在 3.5 版的變更: 'quiet' parameter was changed to a multilevel
     value.

     在 3.5 版的變更: The 'legacy' parameter only writes out ‘.pyc’
     files, not ‘.pyo’ files no matter what the value of 'optimize' is.

     在 3.7 版的變更: 新增 'invalidation_mode' 參數。

     在 3.7.2 版的變更: 新增 'invalidation_mode' 參數的預設值被更新為
     ‘None’。

     在 3.9 版的變更: Added 'stripdir', 'prependdir', 'limit_sl_dest'
     and 'hardlink_dupes' arguments.

 -- 函式: compileall.compile_path (skip_curdir=True, maxlevels=0,
          force=False, quiet=0, legacy=False, optimize=-1,
          invalidation_mode=None)

     Byte-compile all the ‘.py’ files found along ‘sys.path’.  Return a
     true value if all the files compiled successfully, and a false
     value otherwise.

     If 'skip_curdir' is true (the default), the current directory is
     not included in the search.  All other parameters are passed to the
     *note compile_dir(): aca. function.  Note that unlike the other
     compile functions, ‘maxlevels’ defaults to ‘0’.

     在 3.2 版的變更: 新增 'legacy' 與 'optimize' 參數。

     在 3.5 版的變更: 'quiet' parameter was changed to a multilevel
     value.

     在 3.5 版的變更: The 'legacy' parameter only writes out ‘.pyc’
     files, not ‘.pyo’ files no matter what the value of 'optimize' is.

     在 3.7 版的變更: 新增 'invalidation_mode' 參數。

     在 3.7.2 版的變更: 新增 'invalidation_mode' 參數的預設值被更新為
     ‘None’。

To force a recompile of all the ‘.py’ files in the ‘Lib/’ subdirectory
and all its subdirectories:

     import compileall

     compileall.compile_dir('Lib/', force=True)

     # Perform same compilation, excluding files in .svn directories.
     import re
     compileall.compile_dir('Lib/', rx=re.compile(r'[/\\][.]svn'), force=True)

     # pathlib.Path objects can also be used.
     import pathlib
     compileall.compile_dir(pathlib.Path('Lib/'), force=True)

也參考
......

*note py_compile: a1. 模組

     Byte-compile a single source file.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3147/

   (2) https://peps.python.org/pep-3147/


File: python.info,  Node: dis --- Python bytecode 的反組譯器,  Next: pickletools --- pickle 開發者的工具,  Prev: compileall --- 位元組編譯 Python 函式庫,  Up: Python 語言服務

5.32.10 ‘dis’ -- Python bytecode 的反組譯器
-------------------------------------------

'原始碼：'Lib/dis.py(1)

__________________________________________________________________

*note dis: 30. 模組支援反組譯分析 CPython *note bytecode: 16d.。CPython
bytecode 作為輸入的模組被定義於 ‘Include/opcode.h’ 並且被編譯器和直譯器
所使用。

'CPython 實作細節：' Bytecode is an implementation detail of the CPython
interpreter.  No guarantees are made that bytecode will not be added,
removed, or changed between versions of Python.  Use of this module
should not be considered to work across Python VMs or Python releases.

在 3.6 版的變更: Use 2 bytes for each instruction.  Previously the
number of bytes varied by instruction.

在 3.10 版的變更: The argument of jump, exception handling and loop
instructions is now the instruction offset rather than the byte offset.

在 3.11 版的變更: Some instructions are accompanied by one or more
inline cache entries, which take the form of *note CACHE: 69c.
instructions.  These instructions are hidden by default, but can be
shown by passing ‘show_caches=True’ to any *note dis: 30. utility.
Furthermore, the interpreter now adapts the bytecode to specialize it
for different runtime conditions.  The adaptive bytecode can be shown by
passing ‘adaptive=True’.

在 3.12 版的變更: The argument of a jump is the offset of the target
instruction relative to the instruction that appears immediately after
the jump instruction's *note CACHE: 69c. entries.

As a consequence, the presence of the *note CACHE: 69c. instructions is
transparent for forward jumps but needs to be taken into account when
reasoning about backward jumps.

在 3.13 版的變更: The output shows logical labels rather than
instruction offsets for jump targets and exception handlers.  The ‘-O’
command line option and the ‘show_offsets’ argument were added.

Example: Given the function ‘myfunc()’:

     def myfunc(alist):
         return len(alist)

the following command can be used to display the disassembly of
‘myfunc()’:

     >>> dis.dis(myfunc)
       2           RESUME                   0

       3           LOAD_GLOBAL              1 (len + NULL)
                   LOAD_FAST                0 (alist)
                   CALL                     1
                   RETURN_VALUE

(The "2" is a line number).

* Menu:

* Command-line interface::
* Bytecode analysis::
* Analysis functions::
* Python Bytecode Instructions::
* Opcode collections::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/dis.py


File: python.info,  Node: Command-line interface,  Next: Bytecode analysis,  Up: dis --- Python bytecode 的反組譯器

5.32.10.1 Command-line interface
................................

The *note dis: 30. module can be invoked as a script from the command
line:

     python -m dis [-h] [-C] [-O] [infile]

The following options are accepted:

 -- 程式選項: -h, --help

     Display usage and exit.

 -- 程式選項: -C, --show-caches

     Show inline caches.

 -- 程式選項: -O, --show-offsets

     Show offsets of instructions.

If ‘infile’ is specified, its disassembled code will be written to
stdout.  Otherwise, disassembly is performed on compiled source code
received from stdin.


File: python.info,  Node: Bytecode analysis,  Next: Analysis functions,  Prev: Command-line interface,  Up: dis --- Python bytecode 的反組譯器

5.32.10.2 Bytecode analysis
...........................

在 3.4 版被加入.

The bytecode analysis API allows pieces of Python code to be wrapped in
a *note Bytecode: ed2. object that provides easy access to details of
the compiled code.

 -- 類別: dis.Bytecode (x, *, first_line=None, current_offset=None,
          show_caches=False, adaptive=False, show_offsets=False)

     Analyse the bytecode corresponding to a function, generator,
     asynchronous generator, coroutine, method, string of source code,
     or a code object (as returned by *note compile(): 178.).

     This is a convenience wrapper around many of the functions listed
     below, most notably *note get_instructions(): 1bc, as iterating
     over a *note Bytecode: ed2. instance yields the bytecode operations
     as *note Instruction: 1bd. instances.

     If 'first_line' is not ‘None’, it indicates the line number that
     should be reported for the first source line in the disassembled
     code.  Otherwise, the source line information (if any) is taken
     directly from the disassembled code object.

     If 'current_offset' is not ‘None’, it refers to an instruction
     offset in the disassembled code.  Setting this means *note dis():
     ed3. will display a "current instruction" marker against the
     specified opcode.

     If 'show_caches' is ‘True’, *note dis(): ed3. will display inline
     cache entries used by the interpreter to specialize the bytecode.

     If 'adaptive' is ‘True’, *note dis(): ed3. will display specialized
     bytecode that may be different from the original bytecode.

     If 'show_offsets' is ‘True’, *note dis(): ed3. will include
     instruction offsets in the output.

      -- 方法: classmethod from_traceback (tb, *, show_caches=False)

          Construct a *note Bytecode: ed2. instance from the given
          traceback, setting 'current_offset' to the instruction
          responsible for the exception.

      -- 資料: codeobj

          The compiled code object.

      -- 資料: first_line

          The first source line of the code object (if available)

      -- 方法: dis ()

          Return a formatted view of the bytecode operations (the same
          as printed by *note dis.dis(): ad8, but returned as a
          multi-line string).

      -- 方法: info ()

          Return a formatted multi-line string with detailed information
          about the code object, like *note code_info(): 11d1.

     在 3.7 版的變更: This can now handle coroutine and asynchronous
     generator objects.

     在 3.11 版的變更: 新增 'show_caches' 與 'adaptive' 參數。

範例：

     >>> bytecode = dis.Bytecode(myfunc)
     >>> for instr in bytecode:
     ...     print(instr.opname)
     ...
     RESUME
     LOAD_GLOBAL
     LOAD_FAST
     CALL
     RETURN_VALUE


File: python.info,  Node: Analysis functions,  Next: Python Bytecode Instructions,  Prev: Bytecode analysis,  Up: dis --- Python bytecode 的反組譯器

5.32.10.3 Analysis functions
............................

The *note dis: 30. module also defines the following analysis functions
that convert the input directly to the desired output.  They can be
useful if only a single operation is being performed, so the
intermediate analysis object isn't useful:

 -- 函式: dis.code_info (x)

     Return a formatted multi-line string with detailed code object
     information for the supplied function, generator, asynchronous
     generator, coroutine, method, source code string or code object.

     Note that the exact contents of code info strings are highly
     implementation dependent and they may change arbitrarily across
     Python VMs or Python releases.

     在 3.2 版被加入.

     在 3.7 版的變更: This can now handle coroutine and asynchronous
     generator objects.

 -- 函式: dis.show_code (x, *, file=None)

     Print detailed code object information for the supplied function,
     method, source code string or code object to 'file' (or
     ‘sys.stdout’ if 'file' is not specified).

     This is a convenient shorthand for ‘print(code_info(x),
     file=file)’, intended for interactive exploration at the
     interpreter prompt.

     在 3.2 版被加入.

     在 3.4 版的變更: 新增 'file' 參數。

 -- 函式: dis.dis (x=None, *, file=None, depth=None, show_caches=False,
          adaptive=False)

     Disassemble the 'x' object.  'x' can denote either a module, a
     class, a method, a function, a generator, an asynchronous
     generator, a coroutine, a code object, a string of source code or a
     byte sequence of raw bytecode.  For a module, it disassembles all
     functions.  For a class, it disassembles all methods (including
     class and static methods).  For a code object or sequence of raw
     bytecode, it prints one line per bytecode instruction.  It also
     recursively disassembles nested code objects.  These can include
     generator expressions, nested functions, the bodies of nested
     classes, and the code objects used for *note annotation scopes:
     16e.  Strings are first compiled to code objects with the *note
     compile(): 178. built-in function before being disassembled.  If no
     object is provided, this function disassembles the last traceback.

     The disassembly is written as text to the supplied 'file' argument
     if provided and to ‘sys.stdout’ otherwise.

     The maximal depth of recursion is limited by 'depth' unless it is
     ‘None’.  ‘depth=0’ means no recursion.

     If 'show_caches' is ‘True’, this function will display inline cache
     entries used by the interpreter to specialize the bytecode.

     If 'adaptive' is ‘True’, this function will display specialized
     bytecode that may be different from the original bytecode.

     在 3.4 版的變更: 新增 'file' 參數。

     在 3.7 版的變更: Implemented recursive disassembling and added
     'depth' parameter.

     在 3.7 版的變更: This can now handle coroutine and asynchronous
     generator objects.

     在 3.11 版的變更: 新增 'show_caches' 與 'adaptive' 參數。

 -- 函式: distb(tb=None, *, file=None, show_caches=False,
          adaptive=False,

 -- 函式: show_offset=False)

     Disassemble the top-of-stack function of a traceback, using the
     last traceback if none was passed.  The instruction causing the
     exception is indicated.

     The disassembly is written as text to the supplied 'file' argument
     if provided and to ‘sys.stdout’ otherwise.

     在 3.4 版的變更: 新增 'file' 參數。

     在 3.11 版的變更: 新增 'show_caches' 與 'adaptive' 參數。

     在 3.13 版的變更: Added the 'show_offsets' parameter.

 -- 函式: dis.disassemble (code, lasti=-1, *, file=None,
          show_caches=False, adaptive=False)

 -- 函式: disco(code, lasti=-1, *, file=None, show_caches=False,
          adaptive=False,

 -- 函式: show_offsets=False)

     Disassemble a code object, indicating the last instruction if
     'lasti' was provided.  The output is divided in the following
     columns:

       1. the line number, for the first instruction of each line

       2. the current instruction, indicated as ‘-->’,

       3. a labelled instruction, indicated with ‘>>’,

       4. the address of the instruction,

       5. the operation code name,

       6. operation parameters, and

       7. interpretation of the parameters in parentheses.

     The parameter interpretation recognizes local and global variable
     names, constant values, branch targets, and compare operators.

     The disassembly is written as text to the supplied 'file' argument
     if provided and to ‘sys.stdout’ otherwise.

     在 3.4 版的變更: 新增 'file' 參數。

     在 3.11 版的變更: 新增 'show_caches' 與 'adaptive' 參數。

     在 3.13 版的變更: Added the 'show_offsets' parameter.

 -- 函式: dis.get_instructions (x, *, first_line=None,
          show_caches=False, adaptive=False)

     Return an iterator over the instructions in the supplied function,
     method, source code string or code object.

     The iterator generates a series of *note Instruction: 1bd. named
     tuples giving the details of each operation in the supplied code.

     If 'first_line' is not ‘None’, it indicates the line number that
     should be reported for the first source line in the disassembled
     code.  Otherwise, the source line information (if any) is taken
     directly from the disassembled code object.

     The 'adaptive' parameter works as it does in *note dis(): 30.

     在 3.4 版被加入.

     在 3.11 版的變更: 新增 'show_caches' 與 'adaptive' 參數。

     在 3.13 版的變更: The 'show_caches' parameter is deprecated and has
     no effect.  The iterator generates the *note Instruction: 1bd.
     instances with the 'cache_info' field populated (regardless of the
     value of 'show_caches') and it no longer generates separate items
     for the cache entries.

 -- 函式: dis.findlinestarts (code)

     This generator function uses the *note co_lines(): 2cc. method of
     the *note code object: 1b6. 'code' to find the offsets which are
     starts of lines in the source code.  They are generated as
     ‘(offset, lineno)’ pairs.

     在 3.6 版的變更: Line numbers can be decreasing.  Before, they were
     always increasing.

     在 3.10 版的變更: The PEP 626(1) *note co_lines(): 2cc. method is
     used instead of the *note co_firstlineno: 1e18. and *note
     co_lnotab: 2b7. attributes of the *note code object: 1b6.

     在 3.13 版的變更: Line numbers can be ‘None’ for bytecode that does
     not map to source lines.

 -- 函式: dis.findlabels (code)

     Detect all offsets in the raw compiled bytecode string 'code' which
     are jump targets, and return a list of these offsets.

 -- 函式: dis.stack_effect (opcode, oparg=None, *, jump=None)

     Compute the stack effect of 'opcode' with argument 'oparg'.

     If the code has a jump target and 'jump' is ‘True’, *note
     stack_effect(): ed5. will return the stack effect of jumping.  If
     'jump' is ‘False’, it will return the stack effect of not jumping.
     And if 'jump' is ‘None’ (default), it will return the maximal stack
     effect of both cases.

     在 3.4 版被加入.

     在 3.8 版的變更: 新增 'jump' 參數。

     在 3.13 版的變更: If ‘oparg’ is omitted (or ‘None’), the stack
     effect is now returned for ‘oparg=0’.  Previously this was an error
     for opcodes that use their arg.  It is also no longer an error to
     pass an integer ‘oparg’ when the ‘opcode’ does not use it; the
     ‘oparg’ in this case is ignored.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0626/


File: python.info,  Node: Python Bytecode Instructions,  Next: Opcode collections,  Prev: Analysis functions,  Up: dis --- Python bytecode 的反組譯器

5.32.10.4 Python Bytecode Instructions
......................................

The *note get_instructions(): 1bc. function and *note Bytecode: ed2.
class provide details of bytecode instructions as *note Instruction:
1bd. instances:

 -- 類別: dis.Instruction

     Details for a bytecode operation

      -- 資料: opcode

          numeric code for operation, corresponding to the opcode values
          listed below and the bytecode values in the *note Opcode
          collections: 4508.

      -- 資料: opname

          human readable name for operation

      -- 資料: baseopcode

          numeric code for the base operation if operation is
          specialized; otherwise equal to *note opcode: 4507.

      -- 資料: baseopname

          human readable name for the base operation if operation is
          specialized; otherwise equal to *note opname: 450c.

      -- 資料: arg

          numeric argument to operation (if any), otherwise ‘None’

      -- 資料: oparg

          alias for *note arg: 450d.

      -- 資料: argval

          resolved arg value (if any), otherwise ‘None’

      -- 資料: argrepr

          human readable description of operation argument (if any),
          otherwise an empty string.

      -- 資料: offset

          start index of operation within bytecode sequence

      -- 資料: start_offset

          start index of operation within bytecode sequence, including
          prefixed ‘EXTENDED_ARG’ operations if present; otherwise equal
          to *note offset: 4511.

      -- 資料: cache_offset

          start index of the cache entries following the operation

      -- 資料: end_offset

          end index of the cache entries following the operation

      -- 資料: starts_line

          ‘True’ if this opcode starts a source line, otherwise ‘False’

      -- 資料: line_number

          source line number associated with this opcode (if any),
          otherwise ‘None’

      -- 資料: is_jump_target

          ‘True’ if other code jumps to here, otherwise ‘False’

      -- 資料: jump_target

          bytecode index of the jump target if this is a jump operation,
          otherwise ‘None’

      -- 資料: positions

          *note dis.Positions: 42a5. object holding the start and end
          locations that are covered by this instruction.

     在 3.4 版被加入.

     在 3.11 版的變更: Field ‘positions’ is added.

     在 3.13 版的變更: Changed field ‘starts_line’.

     Added fields ‘start_offset’, ‘cache_offset’, ‘end_offset’,
     ‘baseopname’, ‘baseopcode’, ‘jump_target’, ‘oparg’, ‘line_number’
     and ‘cache_info’.

 -- 類別: dis.Positions

     In case the information is not available, some fields might be
     ‘None’.

      -- 資料: lineno

      -- 資料: end_lineno

      -- 資料: col_offset

      -- 資料: end_col_offset

     在 3.11 版被加入.

The Python compiler currently generates the following bytecode
instructions.

'General instructions'

In the following, We will refer to the interpreter stack as ‘STACK’ and
describe operations on it as if it was a Python list.  The top of the
stack corresponds to ‘STACK[-1]’ in this language.

 -- Opcode: NOP

     Do nothing code.  Used as a placeholder by the bytecode optimizer,
     and to generate line tracing events.

 -- Opcode: POP_TOP

     Removes the top-of-stack item:

          STACK.pop()

 -- Opcode: END_FOR

     Removes the top-of-stack item.  Equivalent to ‘POP_TOP’.  Used to
     clean up at the end of loops, hence the name.

     在 3.12 版被加入.

 -- Opcode: END_SEND

     Implements ‘del STACK[-2]’.  Used to clean up when a generator
     exits.

     在 3.12 版被加入.

 -- Opcode: COPY (i)

     Push the i-th item to the top of the stack without removing it from
     its original location:

          assert i > 0
          STACK.append(STACK[-i])

     在 3.11 版被加入.

 -- Opcode: SWAP (i)

     Swap the top of the stack with the i-th element:

          STACK[-i], STACK[-1] = STACK[-1], STACK[-i]

     在 3.11 版被加入.

 -- Opcode: CACHE

     Rather than being an actual instruction, this opcode is used to
     mark extra space for the interpreter to cache useful data directly
     in the bytecode itself.  It is automatically hidden by all ‘dis’
     utilities, but can be viewed with ‘show_caches=True’.

     Logically, this space is part of the preceding instruction.  Many
     opcodes expect to be followed by an exact number of caches, and
     will instruct the interpreter to skip over them at runtime.

     Populated caches can look like arbitrary instructions, so great
     care should be taken when reading or modifying raw, adaptive
     bytecode containing quickened data.

     在 3.11 版被加入.

'Unary operations'

Unary operations take the top of the stack, apply the operation, and
push the result back on the stack.

 -- Opcode: UNARY_NEGATIVE

     Implements ‘STACK[-1] = -STACK[-1]’.

 -- Opcode: UNARY_NOT

     Implements ‘STACK[-1] = not STACK[-1]’.

     在 3.13 版的變更: This instruction now requires an exact *note
     bool: 40e. operand.

 -- Opcode: UNARY_INVERT

     Implements ‘STACK[-1] = ~STACK[-1]’.

 -- Opcode: GET_ITER

     Implements ‘STACK[-1] = iter(STACK[-1])’.

 -- Opcode: GET_YIELD_FROM_ITER

     If ‘STACK[-1]’ is a *note generator iterator: b85. or *note
     coroutine: 438. object it is left as is.  Otherwise, implements
     ‘STACK[-1] = iter(STACK[-1])’.

     在 3.5 版被加入.

 -- Opcode: TO_BOOL

     Implements ‘STACK[-1] = bool(STACK[-1])’.

     在 3.13 版被加入.

'Binary and in-place operations'

Binary operations remove the top two items from the stack (‘STACK[-1]’
and ‘STACK[-2]’).  They perform the operation, then put the result back
on the stack.

In-place operations are like binary operations, but the operation is
done in-place when ‘STACK[-2]’ supports it, and the resulting
‘STACK[-1]’ may be (but does not have to be) the original ‘STACK[-2]’.

 -- Opcode: BINARY_OP (op)

     Implements the binary and in-place operators (depending on the
     value of 'op'):

          rhs = STACK.pop()
          lhs = STACK.pop()
          STACK.append(lhs op rhs)

     在 3.11 版被加入.

 -- Opcode: BINARY_SUBSCR

     Implements:

          key = STACK.pop()
          container = STACK.pop()
          STACK.append(container[key])

 -- Opcode: STORE_SUBSCR

     Implements:

          key = STACK.pop()
          container = STACK.pop()
          value = STACK.pop()
          container[key] = value

 -- Opcode: DELETE_SUBSCR

     Implements:

          key = STACK.pop()
          container = STACK.pop()
          del container[key]

 -- Opcode: BINARY_SLICE

     Implements:

          end = STACK.pop()
          start = STACK.pop()
          container = STACK.pop()
          STACK.append(container[start:end])

     在 3.12 版被加入.

 -- Opcode: STORE_SLICE

     Implements:

          end = STACK.pop()
          start = STACK.pop()
          container = STACK.pop()
          values = STACK.pop()
          container[start:end] = value

     在 3.12 版被加入.

'Coroutine opcodes'

 -- Opcode: GET_AWAITABLE (where)

     Implements ‘STACK[-1] = get_awaitable(STACK[-1])’, where
     ‘get_awaitable(o)’ returns ‘o’ if ‘o’ is a coroutine object or a
     generator object with the *note CO_ITERABLE_COROUTINE: 42b6. flag,
     or resolves ‘o.__await__’.

          If the ‘where’ operand is nonzero, it indicates where the
          instruction occurs:

             * ‘1’: After a call to ‘__aenter__’

             * ‘2’: After a call to ‘__aexit__’

     在 3.5 版被加入.

     在 3.11 版的變更: Previously, this instruction did not have an
     oparg.

 -- Opcode: GET_AITER

     Implements ‘STACK[-1] = STACK[-1].__aiter__()’.

     在 3.5 版被加入.

     在 3.7 版的變更: Returning awaitable objects from ‘__aiter__’ is no
     longer supported.

 -- Opcode: GET_ANEXT

     Implement ‘STACK.append(get_awaitable(STACK[-1].__anext__()))’ to
     the stack.  See ‘GET_AWAITABLE’ for details about ‘get_awaitable’.

     在 3.5 版被加入.

 -- Opcode: END_ASYNC_FOR

     Terminates an *note async for: a4e. loop.  Handles an exception
     raised when awaiting a next item.  The stack contains the async
     iterable in ‘STACK[-2]’ and the raised exception in ‘STACK[-1]’.
     Both are popped.  If the exception is not *note StopAsyncIteration:
     1933, it is re-raised.

     在 3.8 版被加入.

     在 3.11 版的變更: Exception representation on the stack now consist
     of one, not three, items.

 -- Opcode: CLEANUP_THROW

     Handles an exception raised during a *note throw(): 4a0. or *note
     close(): 15ee. call through the current frame.  If ‘STACK[-1]’ is
     an instance of *note StopIteration: ba1, pop three values from the
     stack and push its ‘value’ member.  Otherwise, re-raise
     ‘STACK[-1]’.

     在 3.12 版被加入.

 -- Opcode: BEFORE_ASYNC_WITH

     Resolves ‘__aenter__’ and ‘__aexit__’ from ‘STACK[-1]’.  Pushes
     ‘__aexit__’ and result of ‘__aenter__()’ to the stack:

          STACK.extend((__aexit__, __aenter__())

     在 3.5 版被加入.

'Miscellaneous opcodes'

 -- Opcode: SET_ADD (i)

     Implements:

          item = STACK.pop()
          set.add(STACK[-i], item)

     Used to implement set comprehensions.

 -- Opcode: LIST_APPEND (i)

     Implements:

          item = STACK.pop()
          list.append(STACK[-i], item)

     Used to implement list comprehensions.

 -- Opcode: MAP_ADD (i)

     Implements:

          value = STACK.pop()
          key = STACK.pop()
          dict.__setitem__(STACK[-i], key, value)

     Used to implement dict comprehensions.

     在 3.1 版被加入.

     在 3.8 版的變更: Map value is ‘STACK[-1]’ and map key is
     ‘STACK[-2]’.  Before, those were reversed.

For all of the *note SET_ADD: 452a, *note LIST_APPEND: 452b. and *note
MAP_ADD: a4f. instructions, while the added value or key/value pair is
popped off, the container object remains on the stack so that it is
available for further iterations of the loop.

 -- Opcode: RETURN_VALUE

     Returns with ‘STACK[-1]’ to the caller of the function.

 -- Opcode: RETURN_CONST (consti)

     Returns with ‘co_consts[consti]’ to the caller of the function.

     在 3.12 版被加入.

 -- Opcode: YIELD_VALUE

     Yields ‘STACK.pop()’ from a *note generator: 1004.

     在 3.11 版的變更: oparg set to be the stack depth.

     在 3.12 版的變更: oparg set to be the exception block depth, for
     efficient closing of generators.

     在 3.13 版的變更: oparg is ‘1’ if this instruction is part of a
     yield-from or await, and ‘0’ otherwise.

 -- Opcode: SETUP_ANNOTATIONS

     Checks whether ‘__annotations__’ is defined in ‘locals()’, if not
     it is set up to an empty ‘dict’.  This opcode is only emitted if a
     class or module body contains *note variable annotations: cfc.
     statically.

     在 3.6 版被加入.

 -- Opcode: POP_EXCEPT

     Pops a value from the stack, which is used to restore the exception
     state.

     在 3.11 版的變更: Exception representation on the stack now consist
     of one, not three, items.

 -- Opcode: RERAISE

     Re-raises the exception currently on top of the stack.  If oparg is
     non-zero, pops an additional value from the stack which is used to
     set *note f_lasti: 82c. of the current frame.

     在 3.9 版被加入.

     在 3.11 版的變更: Exception representation on the stack now consist
     of one, not three, items.

 -- Opcode: PUSH_EXC_INFO

     Pops a value from the stack.  Pushes the current exception to the
     top of the stack.  Pushes the value originally popped back to the
     stack.  Used in exception handlers.

     在 3.11 版被加入.

 -- Opcode: CHECK_EXC_MATCH

     Performs exception matching for ‘except’.  Tests whether the
     ‘STACK[-2]’ is an exception matching ‘STACK[-1]’.  Pops ‘STACK[-1]’
     and pushes the boolean result of the test.

     在 3.11 版被加入.

 -- Opcode: CHECK_EG_MATCH

     Performs exception matching for ‘except*’.  Applies
     ‘split(STACK[-1])’ on the exception group representing ‘STACK[-2]’.

     In case of a match, pops two items from the stack and pushes the
     non-matching subgroup (‘None’ in case of full match) followed by
     the matching subgroup.  When there is no match, pops one item (the
     match type) and pushes ‘None’.

     在 3.11 版被加入.

 -- Opcode: WITH_EXCEPT_START

     Calls the function in position 4 on the stack with arguments (type,
     val, tb) representing the exception at the top of the stack.  Used
     to implement the call ‘context_manager.__exit__(*exc_info())’ when
     an exception has occurred in a *note with: 577. statement.

     在 3.9 版被加入.

     在 3.11 版的變更: The ‘__exit__’ function is in position 4 of the
     stack rather than 7.  Exception representation on the stack now
     consist of one, not three, items.

 -- Opcode: LOAD_ASSERTION_ERROR

     Pushes *note AssertionError: 64e. onto the stack.  Used by the
     *note assert: 90c. statement.

     在 3.9 版被加入.

 -- Opcode: LOAD_BUILD_CLASS

     Pushes ‘builtins.__build_class__()’ onto the stack.  It is later
     called to construct a class.

 -- Opcode: BEFORE_WITH

     This opcode performs several operations before a with block starts.
     First, it loads *note __exit__(): 1293. from the context manager
     and pushes it onto the stack for later use by *note
     WITH_EXCEPT_START: 452e.  Then, *note __enter__(): 56c. is called.
     Finally, the result of calling the ‘__enter__()’ method is pushed
     onto the stack.

     在 3.11 版被加入.

 -- Opcode: GET_LEN

     Perform ‘STACK.append(len(STACK[-1]))’.

     在 3.10 版被加入.

 -- Opcode: MATCH_MAPPING

     If ‘STACK[-1]’ is an instance of *note collections.abc.Mapping:
     86f. (or, more technically: if it has the *note Py_TPFLAGS_MAPPING:
     17a6. flag set in its *note tp_flags: 17c0.), push ‘True’ onto the
     stack.  Otherwise, push ‘False’.

     在 3.10 版被加入.

 -- Opcode: MATCH_SEQUENCE

     If ‘STACK[-1]’ is an instance of *note collections.abc.Sequence:
     115c. and is 'not' an instance of *note str: 3f2./*note bytes:
     1a5./*note bytearray: 4e3. (or, more technically: if it has the
     *note Py_TPFLAGS_SEQUENCE: 17a7. flag set in its *note tp_flags:
     17c0.), push ‘True’ onto the stack.  Otherwise, push ‘False’.

     在 3.10 版被加入.

 -- Opcode: MATCH_KEYS

     ‘STACK[-1]’ is a tuple of mapping keys, and ‘STACK[-2]’ is the
     match subject.  If ‘STACK[-2]’ contains all of the keys in
     ‘STACK[-1]’, push a *note tuple: 322. containing the corresponding
     values.  Otherwise, push ‘None’.

     在 3.10 版被加入.

     在 3.11 版的變更: Previously, this instruction also pushed a
     boolean value indicating success (‘True’) or failure (‘False’).

 -- Opcode: STORE_NAME (namei)

     Implements ‘name = STACK.pop()’.  'namei' is the index of 'name' in
     the attribute *note co_names: 1e17. of the *note code object: 1b6.
     The compiler tries to use *note STORE_FAST: 15eb. or *note
     STORE_GLOBAL: 4534. if possible.

 -- Opcode: DELETE_NAME (namei)

     Implements ‘del name’, where 'namei' is the index into *note
     co_names: 1e17. attribute of the *note code object: 1b6.

 -- Opcode: UNPACK_SEQUENCE (count)

     Unpacks ‘STACK[-1]’ into 'count' individual values, which are put
     onto the stack right-to-left.  Require there to be exactly 'count'
     values.:

          assert(len(STACK[-1]) == count)
          STACK.extend(STACK.pop()[:-count-1:-1])

 -- Opcode: UNPACK_EX (counts)

     Implements assignment with a starred target: Unpacks an iterable in
     ‘STACK[-1]’ into individual values, where the total number of
     values can be smaller than the number of items in the iterable: one
     of the new values will be a list of all leftover items.

     The number of values before and after the list value is limited to
     255.

     The number of values before the list value is encoded in the
     argument of the opcode.  The number of values after the list if any
     is encoded using an ‘EXTENDED_ARG’.  As a consequence, the argument
     can be seen as a two bytes values where the low byte of 'counts' is
     the number of values before the list value, the high byte of
     'counts' the number of values after it.

     The extracted values are put onto the stack right-to-left, i.e.
     ‘a, *b, c = d’ will be stored after execution as ‘STACK.extend((a,
     b, c))’.

 -- Opcode: STORE_ATTR (namei)

     Implements:

          obj = STACK.pop()
          value = STACK.pop()
          obj.name = value

     where 'namei' is the index of name in *note co_names: 1e17. of the
     *note code object: 1b6.

 -- Opcode: DELETE_ATTR (namei)

     Implements:

          obj = STACK.pop()
          del obj.name

     where 'namei' is the index of name into *note co_names: 1e17. of
     the *note code object: 1b6.

 -- Opcode: STORE_GLOBAL (namei)

     Works as *note STORE_NAME: 4533, but stores the name as a global.

 -- Opcode: DELETE_GLOBAL (namei)

     Works as *note DELETE_NAME: 4535, but deletes a global name.

 -- Opcode: LOAD_CONST (consti)

     Pushes ‘co_consts[consti]’ onto the stack.

 -- Opcode: LOAD_NAME (namei)

     Pushes the value associated with ‘co_names[namei]’ onto the stack.
     The name is looked up within the locals, then the globals, then the
     builtins.

 -- Opcode: LOAD_LOCALS

     Pushes a reference to the locals dictionary onto the stack.  This
     is used to prepare namespace dictionaries for *note
     LOAD_FROM_DICT_OR_DEREF: 48e. and *note LOAD_FROM_DICT_OR_GLOBALS:
     48f.

     在 3.12 版被加入.

 -- Opcode: LOAD_FROM_DICT_OR_GLOBALS (i)

     Pops a mapping off the stack and looks up the value for
     ‘co_names[namei]’.  If the name is not found there, looks it up in
     the globals and then the builtins, similar to *note LOAD_GLOBAL:
     15e4.  This is used for loading global variables in *note
     annotation scopes: 16e. within class bodies.

     在 3.12 版被加入.

 -- Opcode: BUILD_TUPLE (count)

     Creates a tuple consuming 'count' items from the stack, and pushes
     the resulting tuple onto the stack:

          if count == 0:
              value = ()
          else:
              value = tuple(STACK[-count:])
              STACK = STACK[:-count]

          STACK.append(value)

 -- Opcode: BUILD_LIST (count)

     Works as *note BUILD_TUPLE: 453b, but creates a list.

 -- Opcode: BUILD_SET (count)

     Works as *note BUILD_TUPLE: 453b, but creates a set.

 -- Opcode: BUILD_MAP (count)

     Pushes a new dictionary object onto the stack.  Pops ‘2 * count’
     items so that the dictionary holds 'count' entries: ‘{...,
     STACK[-4]: STACK[-3], STACK[-2]: STACK[-1]}’.

     在 3.5 版的變更: The dictionary is created from stack items instead
     of creating an empty dictionary pre-sized to hold 'count' items.

 -- Opcode: BUILD_CONST_KEY_MAP (count)

     The version of *note BUILD_MAP: 15dd. specialized for constant
     keys.  Pops the top element on the stack which contains a tuple of
     keys, then starting from ‘STACK[-2]’, pops 'count' values to form
     values in the built dictionary.

     在 3.6 版被加入.

 -- Opcode: BUILD_STRING (count)

     Concatenates 'count' strings from the stack and pushes the
     resulting string onto the stack.

     在 3.6 版被加入.

 -- Opcode: LIST_EXTEND (i)

     Implements:

          seq = STACK.pop()
          list.extend(STACK[-i], seq)

     Used to build lists.

     在 3.9 版被加入.

 -- Opcode: SET_UPDATE (i)

     Implements:

          seq = STACK.pop()
          set.update(STACK[-i], seq)

     Used to build sets.

     在 3.9 版被加入.

 -- Opcode: DICT_UPDATE (i)

     Implements:

          map = STACK.pop()
          dict.update(STACK[-i], map)

     Used to build dicts.

     在 3.9 版被加入.

 -- Opcode: DICT_MERGE (i)

     Like *note DICT_UPDATE: 4540. but raises an exception for duplicate
     keys.

     在 3.9 版被加入.

 -- Opcode: LOAD_ATTR (namei)

     If the low bit of ‘namei’ is not set, this replaces ‘STACK[-1]’
     with ‘getattr(STACK[-1], co_names[namei>>1])’.

     If the low bit of ‘namei’ is set, this will attempt to load a
     method named ‘co_names[namei>>1]’ from the ‘STACK[-1]’ object.
     ‘STACK[-1]’ is popped.  This bytecode distinguishes two cases: if
     ‘STACK[-1]’ has a method with the correct name, the bytecode pushes
     the unbound method and ‘STACK[-1]’.  ‘STACK[-1]’ will be used as
     the first argument (‘self’) by *note CALL: 6ab. or *note CALL_KW:
     15de. when calling the unbound method.  Otherwise, ‘NULL’ and the
     object returned by the attribute lookup are pushed.

     在 3.12 版的變更: If the low bit of ‘namei’ is set, then a ‘NULL’
     or ‘self’ is pushed to the stack before the attribute or unbound
     method respectively.

 -- Opcode: LOAD_SUPER_ATTR (namei)

     This opcode implements *note super(): 483, both in its
     zero-argument and two-argument forms (e.g.  ‘super().method()’,
     ‘super().attr’ and ‘super(cls, self).method()’, ‘super(cls,
     self).attr’).

     It pops three values from the stack (from top of stack down):

        * ‘self’: the first argument to the current method

        * ‘cls’: the class within which the current method was defined

        * the global ‘super’

     With respect to its argument, it works similarly to *note
     LOAD_ATTR: 486, except that ‘namei’ is shifted left by 2 bits
     instead of 1.

     The low bit of ‘namei’ signals to attempt a method load, as with
     *note LOAD_ATTR: 486, which results in pushing ‘NULL’ and the
     loaded method.  When it is unset a single value is pushed to the
     stack.

     The second-low bit of ‘namei’, if set, means that this was a
     two-argument call to *note super(): 483. (unset means
     zero-argument).

     在 3.12 版被加入.

 -- Opcode: COMPARE_OP (opname)

     Performs a Boolean operation.  The operation name can be found in
     ‘cmp_op[opname >> 5]’.  If the fifth-lowest bit of ‘opname’ is set
     (‘opname & 16’), the result should be coerced to ‘bool’.

     在 3.13 版的變更: The fifth-lowest bit of the oparg now indicates a
     forced conversion to *note bool: 40e.

 -- Opcode: IS_OP (invert)

     Performs ‘is’ comparison, or ‘is not’ if ‘invert’ is 1.

     在 3.9 版被加入.

 -- Opcode: CONTAINS_OP (invert)

     Performs ‘in’ comparison, or ‘not in’ if ‘invert’ is 1.

     在 3.9 版被加入.

 -- Opcode: IMPORT_NAME (namei)

     Imports the module ‘co_names[namei]’.  ‘STACK[-1]’ and ‘STACK[-2]’
     are popped and provide the 'fromlist' and 'level' arguments of
     *note __import__(): 879.  The module object is pushed onto the
     stack.  The current namespace is not affected: for a proper import
     statement, a subsequent *note STORE_FAST: 15eb. instruction
     modifies the namespace.

 -- Opcode: IMPORT_FROM (namei)

     Loads the attribute ‘co_names[namei]’ from the module found in
     ‘STACK[-1]’.  The resulting object is pushed onto the stack, to be
     subsequently stored by a *note STORE_FAST: 15eb. instruction.

 -- Opcode: JUMP_FORWARD (delta)

     Increments bytecode counter by 'delta'.

 -- Opcode: JUMP_BACKWARD (delta)

     Decrements bytecode counter by 'delta'.  Checks for interrupts.

     在 3.11 版被加入.

 -- Opcode: JUMP_BACKWARD_NO_INTERRUPT (delta)

     Decrements bytecode counter by 'delta'.  Does not check for
     interrupts.

     在 3.11 版被加入.

 -- Opcode: POP_JUMP_IF_TRUE (delta)

     If ‘STACK[-1]’ is true, increments the bytecode counter by 'delta'.
     ‘STACK[-1]’ is popped.

     在 3.11 版的變更: The oparg is now a relative delta rather than an
     absolute target.  This opcode is a pseudo-instruction, replaced in
     final bytecode by the directed versions (forward/backward).

     在 3.12 版的變更: This is no longer a pseudo-instruction.

     在 3.13 版的變更: This instruction now requires an exact *note
     bool: 40e. operand.

 -- Opcode: POP_JUMP_IF_FALSE (delta)

     If ‘STACK[-1]’ is false, increments the bytecode counter by
     'delta'.  ‘STACK[-1]’ is popped.

     在 3.11 版的變更: The oparg is now a relative delta rather than an
     absolute target.  This opcode is a pseudo-instruction, replaced in
     final bytecode by the directed versions (forward/backward).

     在 3.12 版的變更: This is no longer a pseudo-instruction.

     在 3.13 版的變更: This instruction now requires an exact *note
     bool: 40e. operand.

 -- Opcode: POP_JUMP_IF_NOT_NONE (delta)

     If ‘STACK[-1]’ is not ‘None’, increments the bytecode counter by
     'delta'.  ‘STACK[-1]’ is popped.

     This opcode is a pseudo-instruction, replaced in final bytecode by
     the directed versions (forward/backward).

     在 3.11 版被加入.

     在 3.12 版的變更: This is no longer a pseudo-instruction.

 -- Opcode: POP_JUMP_IF_NONE (delta)

     If ‘STACK[-1]’ is ‘None’, increments the bytecode counter by
     'delta'.  ‘STACK[-1]’ is popped.

     This opcode is a pseudo-instruction, replaced in final bytecode by
     the directed versions (forward/backward).

     在 3.11 版被加入.

     在 3.12 版的變更: This is no longer a pseudo-instruction.

 -- Opcode: FOR_ITER (delta)

     ‘STACK[-1]’ is an *note iterator: 192.  Call its *note __next__():
     1260. method.  If this yields a new value, push it on the stack
     (leaving the iterator below it).  If the iterator indicates it is
     exhausted then the byte code counter is incremented by 'delta'.

     在 3.12 版的變更: Up until 3.11 the iterator was popped when it was
     exhausted.

 -- Opcode: LOAD_GLOBAL (namei)

     Loads the global named ‘co_names[namei>>1]’ onto the stack.

     在 3.11 版的變更: If the low bit of ‘namei’ is set, then a ‘NULL’
     is pushed to the stack before the global variable.

 -- Opcode: LOAD_FAST (var_num)

     Pushes a reference to the local ‘co_varnames[var_num]’ onto the
     stack.

     在 3.12 版的變更: This opcode is now only used in situations where
     the local variable is guaranteed to be initialized.  It cannot
     raise *note UnboundLocalError: 14a4.

 -- Opcode: LOAD_FAST_CHECK (var_num)

     Pushes a reference to the local ‘co_varnames[var_num]’ onto the
     stack, raising an *note UnboundLocalError: 14a4. if the local
     variable has not been initialized.

     在 3.12 版被加入.

 -- Opcode: LOAD_FAST_AND_CLEAR (var_num)

     Pushes a reference to the local ‘co_varnames[var_num]’ onto the
     stack (or pushes ‘NULL’ onto the stack if the local variable has
     not been initialized) and sets ‘co_varnames[var_num]’ to ‘NULL’.

     在 3.12 版被加入.

 -- Opcode: STORE_FAST (var_num)

     Stores ‘STACK.pop()’ into the local ‘co_varnames[var_num]’.

 -- Opcode: DELETE_FAST (var_num)

     Deletes local ‘co_varnames[var_num]’.

 -- Opcode: MAKE_CELL (i)

     Creates a new cell in slot ‘i’.  If that slot is nonempty then that
     value is stored into the new cell.

     在 3.11 版被加入.

 -- Opcode: LOAD_DEREF (i)

     Loads the cell contained in slot ‘i’ of the "fast locals" storage.
     Pushes a reference to the object the cell contains on the stack.

     在 3.11 版的變更: ‘i’ is no longer offset by the length of *note
     co_varnames: 1e12.

 -- Opcode: LOAD_FROM_DICT_OR_DEREF (i)

     Pops a mapping off the stack and looks up the name associated with
     slot ‘i’ of the "fast locals" storage in this mapping.  If the name
     is not found there, loads it from the cell contained in slot ‘i’,
     similar to *note LOAD_DEREF: 4548.  This is used for loading free
     variables in class bodies (which previously used ‘LOAD_CLASSDEREF’)
     and in *note annotation scopes: 16e. within class bodies.

     在 3.12 版被加入.

 -- Opcode: STORE_DEREF (i)

     Stores ‘STACK.pop()’ into the cell contained in slot ‘i’ of the
     "fast locals" storage.

     在 3.11 版的變更: ‘i’ is no longer offset by the length of *note
     co_varnames: 1e12.

 -- Opcode: DELETE_DEREF (i)

     Empties the cell contained in slot ‘i’ of the "fast locals"
     storage.  Used by the *note del: 16a9. statement.

     在 3.2 版被加入.

     在 3.11 版的變更: ‘i’ is no longer offset by the length of *note
     co_varnames: 1e12.

 -- Opcode: COPY_FREE_VARS (n)

     Copies the ‘n’ free variables from the closure into the frame.
     Removes the need for special code on the caller's side when calling
     closures.

     在 3.11 版被加入.

 -- Opcode: RAISE_VARARGS (argc)

     Raises an exception using one of the 3 forms of the ‘raise’
     statement, depending on the value of 'argc':

        * 0: ‘raise’ (re-raise previous exception)

        * 1: ‘raise STACK[-1]’ (raise exception instance or type at
          ‘STACK[-1]’)

        * 2: ‘raise STACK[-2] from STACK[-1]’ (raise exception instance
          or type at ‘STACK[-2]’ with ‘__cause__’ set to ‘STACK[-1]’)

 -- Opcode: CALL (argc)

     Calls a callable object with the number of arguments specified by
     ‘argc’.  On the stack are (in ascending order):

        * The callable

        * ‘self’ or ‘NULL’

        * The remaining positional arguments

     ‘argc’ is the total of the positional arguments, excluding ‘self’.

     ‘CALL’ pops all arguments and the callable object off the stack,
     calls the callable object with those arguments, and pushes the
     return value returned by the callable object.

     在 3.11 版被加入.

     在 3.13 版的變更: The callable now always appears at the same
     position on the stack.

     在 3.13 版的變更: Calls with keyword arguments are now handled by
     *note CALL_KW: 15de.

 -- Opcode: CALL_KW (argc)

     Calls a callable object with the number of arguments specified by
     ‘argc’, including one or more named arguments.  On the stack are
     (in ascending order):

        * The callable

        * ‘self’ or ‘NULL’

        * The remaining positional arguments

        * The named arguments

        * A *note tuple: 322. of keyword argument names

     ‘argc’ is the total of the positional and named arguments,
     excluding ‘self’.  The length of the tuple of keyword argument
     names is the number of named arguments.

     ‘CALL_KW’ pops all arguments, the keyword names, and the callable
     object off the stack, calls the callable object with those
     arguments, and pushes the return value returned by the callable
     object.

     在 3.13 版被加入.

 -- Opcode: CALL_FUNCTION_EX (flags)

     Calls a callable object with variable set of positional and keyword
     arguments.  If the lowest bit of 'flags' is set, the top of the
     stack contains a mapping object containing additional keyword
     arguments.  Before the callable is called, the mapping object and
     iterable object are each "unpacked" and their contents passed in as
     keyword and positional arguments respectively.  ‘CALL_FUNCTION_EX’
     pops all arguments and the callable object off the stack, calls the
     callable object with those arguments, and pushes the return value
     returned by the callable object.

     在 3.6 版被加入.

 -- Opcode: PUSH_NULL

     Pushes a ‘NULL’ to the stack.  Used in the call sequence to match
     the ‘NULL’ pushed by *note LOAD_METHOD: bc6. for non-method calls.

     在 3.11 版被加入.

 -- Opcode: MAKE_FUNCTION

     Pushes a new function object on the stack built from the code
     object at ‘STACK[1]’.

     在 3.10 版的變更: Flag value ‘0x04’ is a tuple of strings instead
     of dictionary

     在 3.11 版的變更: Qualified name at ‘STACK[-1]’ was removed.

     在 3.13 版的變更: Extra function attributes on the stack, signaled
     by oparg flags, were removed.  They now use *note
     SET_FUNCTION_ATTRIBUTE: 454c.

 -- Opcode: SET_FUNCTION_ATTRIBUTE (flag)

     Sets an attribute on a function object.  Expects the function at
     ‘STACK[-1]’ and the attribute value to set at ‘STACK[-2]’; consumes
     both and leaves the function at ‘STACK[-1]’.  The flag determines
     which attribute to set:

        * ‘0x01’ a tuple of default values for positional-only and
          positional-or-keyword parameters in positional order

        * ‘0x02’ a dictionary of keyword-only parameters' default values

        * ‘0x04’ a tuple of strings containing parameters' annotations

        * ‘0x08’ a tuple containing cells for free variables, making a
          closure

     在 3.13 版被加入.

 -- Opcode: BUILD_SLICE (argc)

     Pushes a slice object on the stack.  'argc' must be 2 or 3.  If it
     is 2, implements:

          end = STACK.pop()
          start = STACK.pop()
          STACK.append(slice(start, end))

     if it is 3, implements:

          step = STACK.pop()
          end = STACK.pop()
          start = STACK.pop()
          STACK.append(slice(start, end, step))

     See the *note slice(): 410. built-in function for more information.

 -- Opcode: EXTENDED_ARG (ext)

     Prefixes any opcode which has an argument too big to fit into the
     default one byte.  'ext' holds an additional byte which act as
     higher bits in the argument.  For each opcode, at most three
     prefixal ‘EXTENDED_ARG’ are allowed, forming an argument from
     two-byte to four-byte.

 -- Opcode: CONVERT_VALUE (oparg)

     Convert value to a string, depending on ‘oparg’:

          value = STACK.pop()
          result = func(value)
          STACK.append(result)

        * ‘oparg == 1’: call *note str(): 3f2. on 'value'

        * ‘oparg == 2’: call *note repr(): 7a1. on 'value'

        * ‘oparg == 3’: call *note ascii(): 1354. on 'value'

     Used for implementing formatted literal strings (f-strings).

     在 3.13 版被加入.

 -- Opcode: FORMAT_SIMPLE

     Formats the value on top of stack:

          value = STACK.pop()
          result = value.__format__("")
          STACK.append(result)

     Used for implementing formatted literal strings (f-strings).

     在 3.13 版被加入.

 -- Opcode: FORMAT_SPEC

     Formats the given value with the given format spec:

          spec = STACK.pop()
          value = STACK.pop()
          result = value.__format__(spec)
          STACK.append(result)

     Used for implementing formatted literal strings (f-strings).

     在 3.13 版被加入.

 -- Opcode: MATCH_CLASS (count)

     ‘STACK[-1]’ is a tuple of keyword attribute names, ‘STACK[-2]’ is
     the class being matched against, and ‘STACK[-3]’ is the match
     subject.  'count' is the number of positional sub-patterns.

     Pop ‘STACK[-1]’, ‘STACK[-2]’, and ‘STACK[-3]’.  If ‘STACK[-3]’ is
     an instance of ‘STACK[-2]’ and has the positional and keyword
     attributes required by 'count' and ‘STACK[-1]’, push a tuple of
     extracted attributes.  Otherwise, push ‘None’.

     在 3.10 版被加入.

     在 3.11 版的變更: Previously, this instruction also pushed a
     boolean value indicating success (‘True’) or failure (‘False’).

 -- Opcode: RESUME (context)

     A no-op.  Performs internal tracing, debugging and optimization
     checks.

     The ‘context’ oparand consists of two parts.  The lowest two bits
     indicate where the ‘RESUME’ occurs:

        * ‘0’ The start of a function, which is neither a generator,
          coroutine nor an async generator

        * ‘1’ After a ‘yield’ expression

        * ‘2’ After a ‘yield from’ expression

        * ‘3’ After an ‘await’ expression

     The next bit is ‘1’ if the RESUME is at except-depth ‘1’, and ‘0’
     otherwise.

     在 3.11 版被加入.

     在 3.13 版的變更: The oparg value changed to include information
     about except-depth

 -- Opcode: RETURN_GENERATOR

     Create a generator, coroutine, or async generator from the current
     frame.  Used as first opcode of in code object for the above
     mentioned callables.  Clear the current frame and return the newly
     created generator.

     在 3.11 版被加入.

 -- Opcode: SEND (delta)

     Equivalent to ‘STACK[-1] = STACK[-2].send(STACK[-1])’.  Used in
     ‘yield from’ and ‘await’ statements.

     If the call raises *note StopIteration: ba1, pop the top value from
     the stack, push the exception's ‘value’ attribute, and increment
     the bytecode counter by 'delta'.

     在 3.11 版被加入.

 -- Opcode: HAVE_ARGUMENT

     This is not really an opcode.  It identifies the dividing line
     between opcodes in the range [0,255] which don't use their argument
     and those that do (‘< HAVE_ARGUMENT’ and ‘>= HAVE_ARGUMENT’,
     respectively).

     If your application uses pseudo instructions or specialized
     instructions, use the *note hasarg: 27d. collection instead.

     在 3.6 版的變更: Now every instruction has an argument, but opcodes
     ‘< HAVE_ARGUMENT’ ignore it.  Before, only opcodes ‘>=
     HAVE_ARGUMENT’ had an argument.

     在 3.12 版的變更: Pseudo instructions were added to the *note dis:
     30. module, and for them it is not true that comparison with
     ‘HAVE_ARGUMENT’ indicates whether they use their arg.

     在 3.13 版之後被棄用: Use *note hasarg: 27d. instead.

 -- Opcode: CALL_INTRINSIC_1

     Calls an intrinsic function with one argument.  Passes ‘STACK[-1]’
     as the argument and sets ‘STACK[-1]’ to the result.  Used to
     implement functionality that is not performance critical.

     The operand determines which intrinsic function is called:

     Operand                                 Description
                                             
     --------------------------------------------------------------------------------
                                             
     ‘INTRINSIC_1_INVALID’                   Not valid
                                             
                                             
     ‘INTRINSIC_PRINT’                       Prints the argument to standard out.
                                             Used in the REPL.
                                             
                                             
     ‘INTRINSIC_IMPORT_STAR’                 Performs ‘import *’ for the named
                                             module.
                                             
                                             
     ‘INTRINSIC_STOPITERATION_ERROR’         Extracts the return value from a
                                             ‘StopIteration’ exception.
                                             
                                             
     ‘INTRINSIC_ASYNC_GEN_WRAP’              Wraps an async generator value
                                             
                                             
     ‘INTRINSIC_UNARY_POSITIVE’              Performs the unary ‘+’ operation
                                             
                                             
     ‘INTRINSIC_LIST_TO_TUPLE’               Converts a list to a tuple
                                             
                                             
     ‘INTRINSIC_TYPEVAR’                     Creates a *note typing.TypeVar: 141.
                                             
                                             
     ‘INTRINSIC_PARAMSPEC’                   Creates a
                                             *note typing.ParamSpec: 142.
                                             
                                             
     ‘INTRINSIC_TYPEVARTUPLE’                Creates a
                                             *note typing.TypeVarTuple: 143.
                                             
                                             
     ‘INTRINSIC_SUBSCRIPT_GENERIC’           Returns *note typing.Generic: 150c.
                                             subscripted with the argument
                                             
                                             
     ‘INTRINSIC_TYPEALIAS’                   Creates a
                                             *note typing.TypeAliasType: 3fb.;
                                             used in the *note type: 3de.
                                             statement.  The argument is a tuple
                                             of the type alias's name, type
                                             parameters, and value.
                                             

     在 3.12 版被加入.

 -- Opcode: CALL_INTRINSIC_2

     Calls an intrinsic function with two arguments.  Used to implement
     functionality that is not performance critical:

          arg2 = STACK.pop()
          arg1 = STACK.pop()
          result = intrinsic2(arg1, arg2)
          STACK.append(result)

     The operand determines which intrinsic function is called:

     Operand                                      Description
                                                  
     -------------------------------------------------------------------------------------
                                                  
     ‘INTRINSIC_2_INVALID’                        Not valid
                                                  
                                                  
     ‘INTRINSIC_PREP_RERAISE_STAR’                Calculates the
                                                  *note ExceptionGroup: 19c. to raise
                                                  from a ‘try-except*’.
                                                  
                                                  
     ‘INTRINSIC_TYPEVAR_WITH_BOUND’               Creates a *note typing.TypeVar: 141.
                                                  with a bound.
                                                  
                                                  
     ‘INTRINSIC_TYPEVAR_WITH_CONSTRAINTS’         Creates a *note typing.TypeVar: 141.
                                                  with constraints.
                                                  
                                                  
     ‘INTRINSIC_SET_FUNCTION_TYPE_PARAMS’         Sets the ‘__type_params__’ attribute
                                                  of a function.
                                                  

     在 3.12 版被加入.

'Pseudo-instructions'

These opcodes do not appear in Python bytecode.  They are used by the
compiler but are replaced by real opcodes or removed before bytecode is
generated.

 -- Opcode: SETUP_FINALLY (target)

     Set up an exception handler for the following code block.  If an
     exception occurs, the value stack level is restored to its current
     state and control is transferred to the exception handler at
     ‘target’.

 -- Opcode: SETUP_CLEANUP (target)

     Like ‘SETUP_FINALLY’, but in case of an exception also pushes the
     last instruction (‘lasti’) to the stack so that ‘RERAISE’ can
     restore it.  If an exception occurs, the value stack level and the
     last instruction on the frame are restored to their current state,
     and control is transferred to the exception handler at ‘target’.

 -- Opcode: SETUP_WITH (target)

     Like ‘SETUP_CLEANUP’, but in case of an exception one more item is
     popped from the stack before control is transferred to the
     exception handler at ‘target’.

     This variant is used in *note with: 577. and *note async with: 57a.
     constructs, which push the return value of the context manager's
     *note __enter__(): 56c. or *note __aenter__(): 1ea6. to the stack.

 -- Opcode: POP_BLOCK

     Marks the end of the code block associated with the last
     ‘SETUP_FINALLY’, ‘SETUP_CLEANUP’ or ‘SETUP_WITH’.

 -- Opcode: JUMP

 -- Opcode: JUMP_NO_INTERRUPT

     Undirected relative jump instructions which are replaced by their
     directed (forward/backward) counterparts by the assembler.

 -- Opcode: LOAD_CLOSURE (i)

     Pushes a reference to the cell contained in slot ‘i’ of the "fast
     locals" storage.

     Note that ‘LOAD_CLOSURE’ is replaced with ‘LOAD_FAST’ in the
     assembler.

     在 3.13 版的變更: This opcode is now a pseudo-instruction.

 -- Opcode: LOAD_METHOD

     Optimized unbound method lookup.  Emitted as a ‘LOAD_ATTR’ opcode
     with a flag set in the arg.


File: python.info,  Node: Opcode collections,  Prev: Python Bytecode Instructions,  Up: dis --- Python bytecode 的反組譯器

5.32.10.5 Opcode collections
............................

These collections are provided for automatic introspection of bytecode
instructions:

在 3.12 版的變更: The collections now contain pseudo instructions and
instrumented instructions as well.  These are opcodes with values ‘>=
MIN_PSEUDO_OPCODE’ and ‘>= MIN_INSTRUMENTED_OPCODE’.

 -- 資料: dis.opname

     Sequence of operation names, indexable using the bytecode.

 -- 資料: dis.opmap

     Dictionary mapping operation names to bytecodes.

 -- 資料: dis.cmp_op

     Sequence of all compare operation names.

 -- 資料: dis.hasarg

     Sequence of bytecodes that use their argument.

     在 3.12 版被加入.

 -- 資料: dis.hasconst

     Sequence of bytecodes that access a constant.

 -- 資料: dis.hasfree

     Sequence of bytecodes that access a free variable.  'free' in this
     context refers to names in the current scope that are referenced by
     inner scopes or names in outer scopes that are referenced from this
     scope.  It does 'not' include references to global or builtin
     scopes.

 -- 資料: dis.hasname

     Sequence of bytecodes that access an attribute by name.

 -- 資料: dis.hasjump

     Sequence of bytecodes that have a jump target.  All jumps are
     relative.

     在 3.13 版被加入.

 -- 資料: dis.haslocal

     Sequence of bytecodes that access a local variable.

 -- 資料: dis.hascompare

     Sequence of bytecodes of Boolean operations.

 -- 資料: dis.hasexc

     Sequence of bytecodes that set an exception handler.

     在 3.12 版被加入.

 -- 資料: dis.hasjrel

     Sequence of bytecodes that have a relative jump target.

     在 3.13 版之後被棄用: All jumps are now relative.  Use *note
     hasjump: 455c.

 -- 資料: dis.hasjabs

     Sequence of bytecodes that have an absolute jump target.

     在 3.13 版之後被棄用: All jumps are now relative.  This list is
     empty.


File: python.info,  Node: pickletools --- pickle 開發者的工具,  Prev: dis --- Python bytecode 的反組譯器,  Up: Python 語言服務

5.32.11 ‘pickletools’ -- pickle 開發者的工具
--------------------------------------------

'原始碼：'Lib/pickletools.py(1)

__________________________________________________________________

該模組包含與 *note pickle: 95. 模組的詳細資訊相關的各種常數、一些有關實
作的冗長註釋以及一些用於分析已 pickle 資料的有用函式。該模組的內容對於有
*note pickle: 95. 相關工作的 Python 核心開發人員很有用；*note pickle:
95. 模組的一般使用者可能不會發現 *note pickletools: 96. 模組。

* Menu:

* 命令列用法: 命令列用法<4>.
* 程式化介面::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/pickletools.py


File: python.info,  Node: 命令列用法<4>,  Next: 程式化介面,  Up: pickletools --- pickle 開發者的工具

5.32.11.1 命令列用法
....................

在 3.2 版被加入.

當從命令列呼叫時，‘python -m pickletools’ 將拆解 (disassemble) 一個或多
個 pickle 檔案的內容。請注意，如果你想查看儲存在 pickle 中的 Python 物件
而不是 pickle 格式的詳細資訊，你可能需要使用 ‘-m pickle’。但是，當你要檢
查的 pickle 檔案來自不受信任的來源時，‘-m pickletools’ 是一個更安全的選
項，因為它不執行 pickle 位元組碼。

例如，pickle 於檔案 ‘x.pickle’ 中的元組 ‘(1, 2)’：

     $ python -m pickle x.pickle
     (1, 2)

     $ python -m pickletools x.pickle
         0: \x80 PROTO      3
         2: K    BININT1    1
         4: K    BININT1    2
         6: \x86 TUPLE2
         7: q    BINPUT     0
         9: .    STOP
     highest protocol among opcodes = 2

* Menu:

* 命令列選項: 命令列選項<4>.


File: python.info,  Node: 命令列選項<4>,  Up: 命令列用法<4>

5.32.11.2 命令列選項
....................

 -- Option: -a, --annotate

     用簡短的操作碼 (opcode) 描述註釋每一行。

 -- Option: -o, --output=<file>

     應將輸出結果寫入之檔案的名稱。

 -- Option: -l, --indentlevel=<num>

     新 MARK 級別縮進的空格數。

 -- Option: -m, --memo

     當拆解多個物件時，會在拆解間保留備忘錄。

 -- Option: -p, --preamble=<preamble>

     當指定多個 pickle 檔案時，會在每次拆解之前印出給定的一段序言
     (preamble)。


File: python.info,  Node: 程式化介面,  Prev: 命令列用法<4>,  Up: pickletools --- pickle 開發者的工具

5.32.11.3 程式化介面
....................

 -- 函式: pickletools.dis (pickle, out=None, memo=None, indentlevel=4,
          annotate=0)

     將 pickle 的符號拆解 (symbolic disassembly) 輸出到類檔案物件 'out'，
     預設為 ‘sys.stdout’。'pickle' 可以是字串或類檔案物件。'memo' 可以是
     一個 Python 字典，將用作 pickle 的備忘錄；它可用於對同一 pickler 建
     立的多個 pickle 執行拆解。串流中由 ‘MARK’ 操作碼指示的連續級別由
     'indentlevel' 空格縮進。如果為 'annotate' 指定非零值，則輸出中的每
     個操作碼都會用簡短的描述進行註釋。'annotate' 的值用作為註釋之起始行
     提示。

     在 3.2 版的變更: 新增 'annotate' 參數。

 -- 函式: pickletools.genops (pickle)

     提供 pickle 中所有操作碼的一個 *note iterator: 192.，回傳形式為
     ‘(opcode, arg, pos)’ 三元組序列。'opcode' 是 ‘OpcodeInfo’ 類別的實
     例；'arg' 是操作碼引數的解碼值（作為 Python 物件）；'pos' 是該操作
     碼所在的位置。'pickle' 可以是字串或類檔案物件。

 -- 函式: pickletools.optimize (picklestring)

     消除未使用的 ‘PUT’ 操作碼後回傳一個新的等效 pickle 字串。最佳化後的
     pickle 更短、傳輸時間更少、需要更小的儲存空間，且 unpickle 效率也更
     高。


File: python.info,  Node: MS Windows 特有服務,  Next: Unix 特有服務,  Prev: Python 語言服務,  Up: Python 標準函式庫 Standard Library

5.33 MS Windows 特有服務
========================

此章節描述僅在 MS Windows 系統上可用的模組 (module)。

* Menu:

* msvcrt: msvcrt --- MS VC++ runtime 提供的有用例程. MS VC++ runtime 提供的有用例程
* winreg: winreg --- Windows 註冊表存取. Windows 註冊表存取
* winsound: winsound --- Windows 的聲音播放介面. Windows 的聲音播放介面


File: python.info,  Node: msvcrt --- MS VC++ runtime 提供的有用例程,  Next: winreg --- Windows 註冊表存取,  Up: MS Windows 特有服務

5.33.1 ‘msvcrt’ -- MS VC++ runtime 提供的有用例程
-------------------------------------------------

__________________________________________________________________

These functions provide access to some useful capabilities on Windows
platforms.  Some higher-level modules use these functions to build the
Windows implementations of their services.  For example, the *note
getpass: 58. module uses this in the implementation of the *note
getpass(): 58. function.

Further documentation on these functions can be found in the Platform
API documentation.

The module implements both the normal and wide char variants of the
console I/O api.  The normal API deals only with ASCII characters and is
of limited use for internationalized applications.  The wide char API
should be used where ever possible.

在 3.3 版的變更: Operations in this module now raise *note OSError: 350.
where *note IOError: ff5. was raised.

* Menu:

* File Operations::
* Console I/O::
* Other Functions::


File: python.info,  Node: File Operations,  Next: Console I/O,  Up: msvcrt --- MS VC++ runtime 提供的有用例程

5.33.1.1 File Operations
........................

 -- 函式: msvcrt.locking (fd, mode, nbytes)

     Lock part of a file based on file descriptor 'fd' from the C
     runtime.  Raises *note OSError: 350. on failure.  The locked region
     of the file extends from the current file position for 'nbytes'
     bytes, and may continue beyond the end of the file.  'mode' must be
     one of the ‘LK_*’ constants listed below.  Multiple regions in a
     file may be locked at the same time, but may not overlap.  Adjacent
     regions are not merged; they must be unlocked individually.

     引發一個附帶引數 ‘fd’、‘mode’、‘nbytes’ 的*note 稽核事件: 17bd.
     ‘msvcrt.locking’。

 -- 資料: msvcrt.LK_LOCK
 -- 資料: msvcrt.LK_RLCK

     Locks the specified bytes.  If the bytes cannot be locked, the
     program immediately tries again after 1 second.  If, after 10
     attempts, the bytes cannot be locked, *note OSError: 350. is
     raised.

 -- 資料: msvcrt.LK_NBLCK
 -- 資料: msvcrt.LK_NBRLCK

     Locks the specified bytes.  If the bytes cannot be locked, *note
     OSError: 350. is raised.

 -- 資料: msvcrt.LK_UNLCK

     Unlocks the specified bytes, which must have been previously
     locked.

 -- 函式: msvcrt.setmode (fd, flags)

     Set the line-end translation mode for the file descriptor 'fd'.  To
     set it to text mode, 'flags' should be *note os.O_TEXT: 2a40.; for
     binary, it should be *note os.O_BINARY: 2a31.

 -- 函式: msvcrt.open_osfhandle (handle, flags)

     Create a C runtime file descriptor from the file handle 'handle'.
     The 'flags' parameter should be a bitwise OR of *note os.O_APPEND:
     2a33, *note os.O_RDONLY: 2a2f, *note os.O_TEXT: 2a40. and *note
     os.O_NOINHERIT: 2a3b.  The returned file descriptor may be used as
     a parameter to *note os.fdopen(): 1e08. to create a file object.

     The file descriptor is inheritable by default.  Pass *note
     os.O_NOINHERIT: 2a3b. flag to make it non inheritable.

     引發一個附帶引數 ‘handle’、‘flags’ 的*note 稽核事件: 17bd.
     ‘msvcrt.open_osfhandle’。

 -- 函式: msvcrt.get_osfhandle (fd)

     Return the file handle for the file descriptor 'fd'.  Raises *note
     OSError: 350. if 'fd' is not recognized.

     引發一個附帶引數 ‘fd’ 的*note 稽核事件: 17bd.
     ‘msvcrt.get_osfhandle’。


File: python.info,  Node: Console I/O,  Next: Other Functions,  Prev: File Operations,  Up: msvcrt --- MS VC++ runtime 提供的有用例程

5.33.1.2 Console I/O
....................

 -- 函式: msvcrt.kbhit ()

     Returns a nonzero value if a keypress is waiting to be read.
     Otherwise, return 0.

 -- 函式: msvcrt.getch ()

     Read a keypress and return the resulting character as a byte
     string.  Nothing is echoed to the console.  This call will block if
     a keypress is not already available, but will not wait for ‘Enter’
     to be pressed.  If the pressed key was a special function key, this
     will return ‘'\000'’ or ‘'\xe0'’; the next call will return the
     keycode.  The ‘Control-C’ keypress cannot be read with this
     function.

 -- 函式: msvcrt.getwch ()

     Wide char variant of *note getch(): 4581, returning a Unicode
     value.

 -- 函式: msvcrt.getche ()

     Similar to *note getch(): 4581, but the keypress will be echoed if
     it represents a printable character.

 -- 函式: msvcrt.getwche ()

     Wide char variant of *note getche(): 4582, returning a Unicode
     value.

 -- 函式: msvcrt.putch (char)

     Print the byte string 'char' to the console without buffering.

 -- 函式: msvcrt.putwch (unicode_char)

     Wide char variant of *note putch(): 4583, accepting a Unicode
     value.

 -- 函式: msvcrt.ungetch (char)

     Cause the byte string 'char' to be "pushed back" into the console
     buffer; it will be the next character read by *note getch(): 4581.
     or *note getche(): 4582.

 -- 函式: msvcrt.ungetwch (unicode_char)

     Wide char variant of *note ungetch(): 4584, accepting a Unicode
     value.


File: python.info,  Node: Other Functions,  Prev: Console I/O,  Up: msvcrt --- MS VC++ runtime 提供的有用例程

5.33.1.3 Other Functions
........................

 -- 函式: msvcrt.heapmin ()

     Force the ‘malloc()’ heap to clean itself up and return unused
     blocks to the operating system.  On failure, this raises *note
     OSError: 350.

 -- 函式: msvcrt.set_error_mode (mode)

     Changes the location where the C runtime writes an error message
     for an error that might end the program.  'mode' must be one of the
     ‘OUT_*’ constants listed below or *note REPORT_ERRMODE: 458a.
     Returns the old setting or -1 if an error occurs.  Only available
     in *note debug build of Python: 1de.

 -- 資料: msvcrt.OUT_TO_DEFAULT

     Error sink is determined by the app's type.  Only available in
     *note debug build of Python: 1de.

 -- 資料: msvcrt.OUT_TO_STDERR

     Error sink is a standard error.  Only available in *note debug
     build of Python: 1de.

 -- 資料: msvcrt.OUT_TO_MSGBOX

     Error sink is a message box.  Only available in *note debug build
     of Python: 1de.

 -- 資料: msvcrt.REPORT_ERRMODE

     Report the current error mode value.  Only available in *note debug
     build of Python: 1de.

 -- 函式: msvcrt.CrtSetReportMode (type, mode)

     Specifies the destination or destinations for a specific report
     type generated by ‘_CrtDbgReport()’ in the MS VC++ runtime.  'type'
     must be one of the ‘CRT_*’ constants listed below.  'mode' must be
     one of the ‘CRTDBG_*’ constants listed below.  Only available in
     *note debug build of Python: 1de.

 -- 函式: msvcrt.CrtSetReportFile (type, file)

     After you use *note CrtSetReportMode(): 458e. to specify *note
     CRTDBG_MODE_FILE: 4590, you can specify the file handle to receive
     the message text.  'type' must be one of the ‘CRT_*’ constants
     listed below.  'file' should be the file handle your want
     specified.  Only available in *note debug build of Python: 1de.

 -- 資料: msvcrt.CRT_WARN

     Warnings, messages, and information that doesn't need immediate
     attention.

 -- 資料: msvcrt.CRT_ERROR

     Errors, unrecoverable problems, and issues that require immediate
     attention.

 -- 資料: msvcrt.CRT_ASSERT

     Assertion failures.

 -- 資料: msvcrt.CRTDBG_MODE_DEBUG

     Writes the message to the debugger's output window.

 -- 資料: msvcrt.CRTDBG_MODE_FILE

     Writes the message to a user-supplied file handle.  *note
     CrtSetReportFile(): 458f. should be called to define the specific
     file or stream to use as the destination.

 -- 資料: msvcrt.CRTDBG_MODE_WNDW

     Creates a message box to display the message along with the
     ‘Abort’, ‘Retry’, and ‘Ignore’ buttons.

 -- 資料: msvcrt.CRTDBG_REPORT_MODE

     Returns current 'mode' for the specified 'type'.

 -- 資料: msvcrt.CRT_ASSEMBLY_VERSION

     The CRT Assembly version, from the ‘crtassem.h’ header file.

 -- 資料: msvcrt.VC_ASSEMBLY_PUBLICKEYTOKEN

     The VC Assembly public key token, from the ‘crtassem.h’ header
     file.

 -- 資料: msvcrt.LIBRARIES_ASSEMBLY_NAME_PREFIX

     The Libraries Assembly name prefix, from the ‘crtassem.h’ header
     file.


File: python.info,  Node: winreg --- Windows 註冊表存取,  Next: winsound --- Windows 的聲音播放介面,  Prev: msvcrt --- MS VC++ runtime 提供的有用例程,  Up: MS Windows 特有服務

5.33.2 ‘winreg’ -- Windows 註冊表存取
-------------------------------------

__________________________________________________________________

These functions expose the Windows registry API to Python.  Instead of
using an integer as the registry handle, a *note handle object: 4599. is
used to ensure that the handles are closed correctly, even if the
programmer neglects to explicitly close them.

在 3.3 版的變更: Several functions in this module used to raise a *note
WindowsError: ff7, which is now an alias of *note OSError: 350.

* Menu:

* 函式: 函式<12>.
* 常數: 常數<10>.
* Registry Handle Objects::


File: python.info,  Node: 函式<12>,  Next: 常數<10>,  Up: winreg --- Windows 註冊表存取

5.33.2.1 函式
.............

This module offers the following functions:

 -- 函式: winreg.CloseKey (hkey)

     Closes a previously opened registry key.  The 'hkey' argument
     specifies a previously opened key.

          備註: If 'hkey' is not closed using this method (or via *note
          hkey.Close(): 459e.), it is closed when the 'hkey' object is
          destroyed by Python.

 -- 函式: winreg.ConnectRegistry (computer_name, key)

     Establishes a connection to a predefined registry handle on another
     computer, and returns a *note handle object: 4599.

     'computer_name' is the name of the remote computer, of the form
     ‘r"\\computername"’.  If ‘None’, the local computer is used.

     'key' is the predefined handle to connect to.

     The return value is the handle of the opened key.  If the function
     fails, an *note OSError: 350. exception is raised.

     引發一個附帶引數 ‘computer_name’、‘key’ 的*note 稽核事件: 17bd.
     ‘winreg.ConnectRegistry’。

     在 3.3 版的變更: See *note above: 459a.

 -- 函式: winreg.CreateKey (key, sub_key)

     Creates or opens the specified key, returning a *note handle
     object: 4599.

     'key' is an already open key, or one of the predefined *note HKEY_*
     constants: 459f.

     'sub_key' is a string that names the key this method opens or
     creates.

     If 'key' is one of the predefined keys, 'sub_key' may be ‘None’.
     In that case, the handle returned is the same key handle passed in
     to the function.

     If the key already exists, this function opens the existing key.

     The return value is the handle of the opened key.  If the function
     fails, an *note OSError: 350. exception is raised.

     引發一個附帶引數 ‘key’、‘sub_key’、‘access’ 的*note 稽核事件: 17bd.
     ‘winreg.CreateKey’。

     引發一個附帶引數 ‘key’ 的*note 稽核事件: 17bd.
     ‘winreg.OpenKey/result’。

     在 3.3 版的變更: See *note above: 459a.

 -- 函式: winreg.CreateKeyEx (key, sub_key, reserved=0,
          access=KEY_WRITE)

     Creates or opens the specified key, returning a *note handle
     object: 4599.

     'key' is an already open key, or one of the predefined *note HKEY_*
     constants: 459f.

     'sub_key' is a string that names the key this method opens or
     creates.

     'reserved' is a reserved integer, and must be zero.  The default is
     zero.

     'access' is an integer that specifies an access mask that describes
     the desired security access for the key.  Default is *note
     KEY_WRITE: 45a0.  See *note Access Rights: 45a1. for other allowed
     values.

     If 'key' is one of the predefined keys, 'sub_key' may be ‘None’.
     In that case, the handle returned is the same key handle passed in
     to the function.

     If the key already exists, this function opens the existing key.

     The return value is the handle of the opened key.  If the function
     fails, an *note OSError: 350. exception is raised.

     引發一個附帶引數 ‘key’、‘sub_key’、‘access’ 的*note 稽核事件: 17bd.
     ‘winreg.CreateKey’。

     引發一個附帶引數 ‘key’ 的*note 稽核事件: 17bd.
     ‘winreg.OpenKey/result’。

     在 3.2 版被加入.

     在 3.3 版的變更: See *note above: 459a.

 -- 函式: winreg.DeleteKey (key, sub_key)

     Deletes the specified key.

     'key' is an already open key, or one of the predefined *note HKEY_*
     constants: 459f.

     'sub_key' is a string that must be a subkey of the key identified
     by the 'key' parameter.  This value must not be ‘None’, and the key
     may not have subkeys.

     'This method can not delete keys with subkeys.'

     If the method succeeds, the entire key, including all of its
     values, is removed.  If the method fails, an *note OSError: 350.
     exception is raised.

     引發一個附帶引數 ‘key’、‘sub_key’、‘access’ 的*note 稽核事件: 17bd.
     ‘winreg.DeleteKey’。

     在 3.3 版的變更: See *note above: 459a.

 -- 函式: winreg.DeleteKeyEx (key, sub_key, access=KEY_WOW64_64KEY,
          reserved=0)

     Deletes the specified key.

     'key' is an already open key, or one of the predefined *note HKEY_*
     constants: 459f.

     'sub_key' is a string that must be a subkey of the key identified
     by the 'key' parameter.  This value must not be ‘None’, and the key
     may not have subkeys.

     'reserved' is a reserved integer, and must be zero.  The default is
     zero.

     'access' is an integer that specifies an access mask that describes
     the desired security access for the key.  Default is *note
     KEY_WOW64_64KEY: 45a2.  On 32-bit Windows, the WOW64 constants are
     ignored.  See *note Access Rights: 45a1. for other allowed values.

     'This method can not delete keys with subkeys.'

     If the method succeeds, the entire key, including all of its
     values, is removed.  If the method fails, an *note OSError: 350.
     exception is raised.

     On unsupported Windows versions, *note NotImplementedError: 20d. is
     raised.

     引發一個附帶引數 ‘key’、‘sub_key’、‘access’ 的*note 稽核事件: 17bd.
     ‘winreg.DeleteKey’。

     在 3.2 版被加入.

     在 3.3 版的變更: See *note above: 459a.

 -- 函式: winreg.DeleteValue (key, value)

     Removes a named value from a registry key.

     'key' is an already open key, or one of the predefined *note HKEY_*
     constants: 459f.

     'value' is a string that identifies the value to remove.

     引發一個附帶引數 ‘key’、‘value’ 的*note 稽核事件: 17bd.
     ‘winreg.DeleteValue’。

 -- 函式: winreg.EnumKey (key, index)

     Enumerates subkeys of an open registry key, returning a string.

     'key' is an already open key, or one of the predefined *note HKEY_*
     constants: 459f.

     'index' is an integer that identifies the index of the key to
     retrieve.

     The function retrieves the name of one subkey each time it is
     called.  It is typically called repeatedly until an *note OSError:
     350. exception is raised, indicating, no more values are available.

     引發一個附帶引數 ‘key’、‘index’ 的*note 稽核事件: 17bd.
     ‘winreg.EnumKey’。

     在 3.3 版的變更: See *note above: 459a.

 -- 函式: winreg.EnumValue (key, index)

     Enumerates values of an open registry key, returning a tuple.

     'key' is an already open key, or one of the predefined *note HKEY_*
     constants: 459f.

     'index' is an integer that identifies the index of the value to
     retrieve.

     The function retrieves the name of one subkey each time it is
     called.  It is typically called repeatedly, until an *note OSError:
     350. exception is raised, indicating no more values.

     The result is a tuple of 3 items:

     Index       含義
                 
     -------------------------------------------------------------
                 
     ‘0’         A string that identifies the value name
                 
                 
     ‘1’         An object that holds the value data, and whose
                 type depends on the underlying registry type
                 
                 
     ‘2’         An integer that identifies the type of the
                 value data (see table in docs for
                 *note SetValueEx(): 1691.)
                 

     引發一個附帶引數 ‘key’、‘index’ 的*note 稽核事件: 17bd.
     ‘winreg.EnumValue’。

     在 3.3 版的變更: See *note above: 459a.

 -- 函式: winreg.ExpandEnvironmentStrings (str)

     Expands environment variable placeholders ‘%NAME%’ in strings like
     *note REG_EXPAND_SZ: 45a3.:

          >>> ExpandEnvironmentStrings('%windir%')
          'C:\\Windows'

     引發一個附帶引數 ‘str’ 的*note 稽核事件: 17bd.
     ‘winreg.ExpandEnvironmentStrings’。

 -- 函式: winreg.FlushKey (key)

     Writes all the attributes of a key to the registry.

     'key' is an already open key, or one of the predefined *note HKEY_*
     constants: 459f.

     It is not necessary to call *note FlushKey(): 45a4. to change a
     key.  Registry changes are flushed to disk by the registry using
     its lazy flusher.  Registry changes are also flushed to disk at
     system shutdown.  Unlike *note CloseKey(): 459d, the *note
     FlushKey(): 45a4. method returns only when all the data has been
     written to the registry.  An application should only call *note
     FlushKey(): 45a4. if it requires absolute certainty that registry
     changes are on disk.

          備註: If you don't know whether a *note FlushKey(): 45a4. call
          is required, it probably isn't.

 -- 函式: winreg.LoadKey (key, sub_key, file_name)

     Creates a subkey under the specified key and stores registration
     information from a specified file into that subkey.

     'key' is a handle returned by *note ConnectRegistry(): 4001. or one
     of the constants *note HKEY_USERS: 45a5. or *note
     HKEY_LOCAL_MACHINE: 45a6.

     'sub_key' is a string that identifies the subkey to load.

     'file_name' is the name of the file to load registry data from.
     This file must have been created with the *note SaveKey(): 400d.
     function.  Under the file allocation table (FAT) file system, the
     filename may not have an extension.

     A call to *note LoadKey(): 4007. fails if the calling process does
     not have the ‘SE_RESTORE_PRIVILEGE’ privilege.  Note that
     privileges are different from permissions - see the RegLoadKey
     documentation(1) for more details.

     If 'key' is a handle returned by *note ConnectRegistry(): 4001,
     then the path specified in 'file_name' is relative to the remote
     computer.

     引發一個附帶引數 ‘key’、‘sub_key’、‘file_name’ 的*note 稽核事件:
     17bd. ‘winreg.LoadKey’。

 -- 函式: winreg.OpenKey (key, sub_key, reserved=0, access=KEY_READ)
 -- 函式: winreg.OpenKeyEx (key, sub_key, reserved=0, access=KEY_READ)

     Opens the specified key, returning a *note handle object: 4599.

     'key' is an already open key, or one of the predefined *note HKEY_*
     constants: 459f.

     'sub_key' is a string that identifies the sub_key to open.

     'reserved' is a reserved integer, and must be zero.  The default is
     zero.

     'access' is an integer that specifies an access mask that describes
     the desired security access for the key.  Default is *note
     KEY_READ: 45a8.  See *note Access Rights: 45a1. for other allowed
     values.

     The result is a new handle to the specified key.

     If the function fails, *note OSError: 350. is raised.

     引發一個附帶引數 ‘key’、‘sub_key’、‘access’ 的*note 稽核事件: 17bd.
     ‘winreg.OpenKey’。

     引發一個附帶引數 ‘key’ 的*note 稽核事件: 17bd.
     ‘winreg.OpenKey/result’。

     在 3.2 版的變更: Allow the use of named arguments.

     在 3.3 版的變更: See *note above: 459a.

 -- 函式: winreg.QueryInfoKey (key)

     Returns information about a key, as a tuple.

     'key' is an already open key, or one of the predefined *note HKEY_*
     constants: 459f.

     The result is a tuple of 3 items:

     Index       含義
                 
     --------------------------------------------------------------
                 
     ‘0’         An integer giving the number of sub keys this
                 key has.
                 
                 
     ‘1’         An integer giving the number of values this key
                 has.
                 
                 
     ‘2’         An integer giving when the key was last
                 modified (if available) as 100's of nanoseconds
                 since Jan 1, 1601.
                 

     引發一個附帶引數 ‘key’ 的*note 稽核事件: 17bd.
     ‘winreg.QueryInfoKey’。

 -- 函式: winreg.QueryValue (key, sub_key)

     Retrieves the unnamed value for a key, as a string.

     'key' is an already open key, or one of the predefined *note HKEY_*
     constants: 459f.

     'sub_key' is a string that holds the name of the subkey with which
     the value is associated.  If this parameter is ‘None’ or empty, the
     function retrieves the value set by the *note SetValue(): 400e.
     method for the key identified by 'key'.

     Values in the registry have name, type, and data components.  This
     method retrieves the data for a key's first value that has a ‘NULL’
     name.  But the underlying API call doesn't return the type, so
     always use *note QueryValueEx(): 400c. if possible.

     引發一個附帶引數 ‘key’、‘sub_key’、‘value_name’ 的*note 稽核事件:
     17bd. ‘winreg.QueryKey’。

 -- 函式: winreg.QueryValueEx (key, value_name)

     Retrieves the type and data for a specified value name associated
     with an open registry key.

     'key' is an already open key, or one of the predefined *note HKEY_*
     constants: 459f.

     'value_name' is a string indicating the value to query.

     The result is a tuple of 2 items:

     Index       含義
                 
     ----------------------------------------------------------
                 
     ‘0’         The value of the registry item.
                 
                 
     ‘1’         An integer giving the registry type for
                 this value (see table in docs for
                 *note SetValueEx(): 1691.)
                 

     引發一個附帶引數 ‘key’、‘sub_key’、‘value_name’ 的*note 稽核事件:
     17bd. ‘winreg.QueryKey’。

 -- 函式: winreg.SaveKey (key, file_name)

     Saves the specified key, and all its subkeys to the specified file.

     'key' is an already open key, or one of the predefined *note HKEY_*
     constants: 459f.

     'file_name' is the name of the file to save registry data to.  This
     file cannot already exist.  If this filename includes an extension,
     it cannot be used on file allocation table (FAT) file systems by
     the *note LoadKey(): 4007. method.

     If 'key' represents a key on a remote computer, the path described
     by 'file_name' is relative to the remote computer.  The caller of
     this method must possess the 'SeBackupPrivilege' security
     privilege.  Note that privileges are different than permissions -
     see the Conflicts Between User Rights and Permissions
     documentation(2) for more details.

     This function passes ‘NULL’ for 'security_attributes' to the API.

     引發一個附帶引數 ‘key’、‘file_name’ 的*note 稽核事件: 17bd.
     ‘winreg.SaveKey’。

 -- 函式: winreg.SetValue (key, sub_key, type, value)

     Associates a value with a specified key.

     'key' is an already open key, or one of the predefined *note HKEY_*
     constants: 459f.

     'sub_key' is a string that names the subkey with which the value is
     associated.

     'type' is an integer that specifies the type of the data.
     Currently this must be *note REG_SZ: 45a9, meaning only strings are
     supported.  Use the *note SetValueEx(): 1691. function for support
     for other data types.

     'value' is a string that specifies the new value.

     If the key specified by the 'sub_key' parameter does not exist, the
     SetValue function creates it.

     Value lengths are limited by available memory.  Long values (more
     than 2048 bytes) should be stored as files with the filenames
     stored in the configuration registry.  This helps the registry
     perform efficiently.

     The key identified by the 'key' parameter must have been opened
     with *note KEY_SET_VALUE: 45aa. access.

     引發一個附帶引數 ‘key’、‘sub_key’、‘type’、‘value’ 的*note
     稽核事件: 17bd. ‘winreg.SetValue’。

 -- 函式: winreg.SetValueEx (key, value_name, reserved, type, value)

     Stores data in the value field of an open registry key.

     'key' is an already open key, or one of the predefined *note HKEY_*
     constants: 459f.

     'value_name' is a string that names the subkey with which the value
     is associated.

     'reserved' can be anything - zero is always passed to the API.

     'type' is an integer that specifies the type of the data.  See
     *note Value Types: 45ab. for the available types.

     'value' is a string that specifies the new value.

     This method can also set additional value and type information for
     the specified key.  The key identified by the key parameter must
     have been opened with *note KEY_SET_VALUE: 45aa. access.

     To open the key, use the *note CreateKey(): 4002. or *note
     OpenKey(): 4008. methods.

     Value lengths are limited by available memory.  Long values (more
     than 2048 bytes) should be stored as files with the filenames
     stored in the configuration registry.  This helps the registry
     perform efficiently.

     引發一個附帶引數 ‘key’、‘sub_key’、‘type’、‘value’ 的*note
     稽核事件: 17bd. ‘winreg.SetValue’。

 -- 函式: winreg.DisableReflectionKey (key)

     Disables registry reflection for 32-bit processes running on a
     64-bit operating system.

     'key' is an already open key, or one of the predefined *note HKEY_*
     constants: 459f.

     Will generally raise *note NotImplementedError: 20d. if executed on
     a 32-bit operating system.

     If the key is not on the reflection list, the function succeeds but
     has no effect.  Disabling reflection for a key does not affect
     reflection of any subkeys.

     引發一個附帶引數 ‘key’ 的*note 稽核事件: 17bd.
     ‘winreg.DsiableReflectionKey’。

 -- 函式: winreg.EnableReflectionKey (key)

     Restores registry reflection for the specified disabled key.

     'key' is an already open key, or one of the predefined *note HKEY_*
     constants: 459f.

     Will generally raise *note NotImplementedError: 20d. if executed on
     a 32-bit operating system.

     Restoring reflection for a key does not affect reflection of any
     subkeys.

     引發一個附帶引數 ‘key’ 的*note 稽核事件: 17bd.
     ‘winreg.EnableReflectionKey’。

 -- 函式: winreg.QueryReflectionKey (key)

     Determines the reflection state for the specified key.

     'key' is an already open key, or one of the predefined *note HKEY_*
     constants: 459f.

     Returns ‘True’ if reflection is disabled.

     Will generally raise *note NotImplementedError: 20d. if executed on
     a 32-bit operating system.

     引發一個附帶引數 ‘key’ 的*note 稽核事件: 17bd.
     ‘winreg.QueryReflectionKey’。

   ---------- Footnotes ----------

   (1) 
https://msdn.microsoft.com/en-us/library/ms724889%28v=VS.85%29.aspx

   (2) 
https://msdn.microsoft.com/en-us/library/ms724878%28v=VS.85%29.aspx


File: python.info,  Node: 常數<10>,  Next: Registry Handle Objects,  Prev: 函式<12>,  Up: winreg --- Windows 註冊表存取

5.33.2.2 常數
.............

The following constants are defined for use in many *note winreg: fe.
functions.

* Menu:

* HKEY_* Constants::
* Access Rights::
* Value Types::


File: python.info,  Node: HKEY_* Constants,  Next: Access Rights,  Up: 常數<10>

5.33.2.3 HKEY_* Constants
.........................

 -- 資料: winreg.HKEY_CLASSES_ROOT

     Registry entries subordinate to this key define types (or classes)
     of documents and the properties associated with those types.  Shell
     and COM applications use the information stored under this key.

 -- 資料: winreg.HKEY_CURRENT_USER

     Registry entries subordinate to this key define the preferences of
     the current user.  These preferences include the settings of
     environment variables, data about program groups, colors, printers,
     network connections, and application preferences.

 -- 資料: winreg.HKEY_LOCAL_MACHINE

     Registry entries subordinate to this key define the physical state
     of the computer, including data about the bus type, system memory,
     and installed hardware and software.

 -- 資料: winreg.HKEY_USERS

     Registry entries subordinate to this key define the default user
     configuration for new users on the local computer and the user
     configuration for the current user.

 -- 資料: winreg.HKEY_PERFORMANCE_DATA

     Registry entries subordinate to this key allow you to access
     performance data.  The data is not actually stored in the registry;
     the registry functions cause the system to collect the data from
     its source.

 -- 資料: winreg.HKEY_CURRENT_CONFIG

     Contains information about the current hardware profile of the
     local computer system.

 -- 資料: winreg.HKEY_DYN_DATA

     This key is not used in versions of Windows after 98.


File: python.info,  Node: Access Rights,  Next: Value Types,  Prev: HKEY_* Constants,  Up: 常數<10>

5.33.2.4 Access Rights
......................

For more information, see Registry Key Security and Access(1).

 -- 資料: winreg.KEY_ALL_ACCESS

     Combines the STANDARD_RIGHTS_REQUIRED, *note KEY_QUERY_VALUE: 45b6,
     *note KEY_SET_VALUE: 45aa, *note KEY_CREATE_SUB_KEY: 45b7, *note
     KEY_ENUMERATE_SUB_KEYS: 45b8, *note KEY_NOTIFY: 45b9, and *note
     KEY_CREATE_LINK: 45ba. access rights.

 -- 資料: winreg.KEY_WRITE

     Combines the STANDARD_RIGHTS_WRITE, *note KEY_SET_VALUE: 45aa, and
     *note KEY_CREATE_SUB_KEY: 45b7. access rights.

 -- 資料: winreg.KEY_READ

     Combines the STANDARD_RIGHTS_READ, *note KEY_QUERY_VALUE: 45b6,
     *note KEY_ENUMERATE_SUB_KEYS: 45b8, and *note KEY_NOTIFY: 45b9.
     values.

 -- 資料: winreg.KEY_EXECUTE

     Equivalent to *note KEY_READ: 45a8.

 -- 資料: winreg.KEY_QUERY_VALUE

     Required to query the values of a registry key.

 -- 資料: winreg.KEY_SET_VALUE

     Required to create, delete, or set a registry value.

 -- 資料: winreg.KEY_CREATE_SUB_KEY

     Required to create a subkey of a registry key.

 -- 資料: winreg.KEY_ENUMERATE_SUB_KEYS

     Required to enumerate the subkeys of a registry key.

 -- 資料: winreg.KEY_NOTIFY

     Required to request change notifications for a registry key or for
     subkeys of a registry key.

 -- 資料: winreg.KEY_CREATE_LINK

     Reserved for system use.

* Menu:

* 64-bit Specific::

   ---------- Footnotes ----------

   (1) 
https://msdn.microsoft.com/en-us/library/ms724878%28v=VS.85%29.aspx


File: python.info,  Node: 64-bit Specific,  Up: Access Rights

5.33.2.5 64-bit Specific
........................

For more information, see Accessing an Alternate Registry View(1).

 -- 資料: winreg.KEY_WOW64_64KEY

     Indicates that an application on 64-bit Windows should operate on
     the 64-bit registry view.  On 32-bit Windows, this constant is
     ignored.

 -- 資料: winreg.KEY_WOW64_32KEY

     Indicates that an application on 64-bit Windows should operate on
     the 32-bit registry view.  On 32-bit Windows, this constant is
     ignored.

   ---------- Footnotes ----------

   (1) https://msdn.microsoft.com/en-us/library/aa384129(v=VS.85).aspx


File: python.info,  Node: Value Types,  Prev: Access Rights,  Up: 常數<10>

5.33.2.6 Value Types
....................

For more information, see Registry Value Types(1).

 -- 資料: winreg.REG_BINARY

     Binary data in any form.

 -- 資料: winreg.REG_DWORD

     32-bit number.

 -- 資料: winreg.REG_DWORD_LITTLE_ENDIAN

     A 32-bit number in little-endian format.  Equivalent to *note
     REG_DWORD: 45c1.

 -- 資料: winreg.REG_DWORD_BIG_ENDIAN

     A 32-bit number in big-endian format.

 -- 資料: winreg.REG_EXPAND_SZ

     Null-terminated string containing references to environment
     variables (‘%PATH%’).

 -- 資料: winreg.REG_LINK

     A Unicode symbolic link.

 -- 資料: winreg.REG_MULTI_SZ

     A sequence of null-terminated strings, terminated by two null
     characters.  (Python handles this termination automatically.)

 -- 資料: winreg.REG_NONE

     No defined value type.

 -- 資料: winreg.REG_QWORD

     A 64-bit number.

     在 3.6 版被加入.

 -- 資料: winreg.REG_QWORD_LITTLE_ENDIAN

     A 64-bit number in little-endian format.  Equivalent to *note
     REG_QWORD: ca9.

     在 3.6 版被加入.

 -- 資料: winreg.REG_RESOURCE_LIST

     A device-driver resource list.

 -- 資料: winreg.REG_FULL_RESOURCE_DESCRIPTOR

     A hardware setting.

 -- 資料: winreg.REG_RESOURCE_REQUIREMENTS_LIST

     A hardware resource list.

 -- 資料: winreg.REG_SZ

     A null-terminated string.

   ---------- Footnotes ----------

   (1) 
https://msdn.microsoft.com/en-us/library/ms724884%28v=VS.85%29.aspx


File: python.info,  Node: Registry Handle Objects,  Prev: 常數<10>,  Up: winreg --- Windows 註冊表存取

5.33.2.7 Registry Handle Objects
................................

This object wraps a Windows HKEY object, automatically closing it when
the object is destroyed.  To guarantee cleanup, you can call either the
*note Close(): 459e. method on the object, or the *note CloseKey():
459d. function.

All registry functions in this module return one of these objects.

All registry functions in this module which accept a handle object also
accept an integer, however, use of the handle object is encouraged.

Handle objects provide semantics for *note __bool__(): 1268. - thus

     if handle:
         print("Yes")

will print ‘Yes’ if the handle is currently valid (has not been closed
or detached).

The object also support comparison semantics, so handle objects will
compare true if they both reference the same underlying Windows handle
value.

Handle objects can be converted to an integer (e.g., using the built-in
*note int(): 23c. function), in which case the underlying Windows handle
value is returned.  You can also use the *note Detach(): 4009. method to
return the integer handle, and also disconnect the Windows handle from
the handle object.

 -- 方法: PyHKEY.Close ()

     Closes the underlying Windows handle.

     If the handle is already closed, no error is raised.

 -- 方法: PyHKEY.Detach ()

     Detaches the Windows handle from the handle object.

     The result is an integer that holds the value of the handle before
     it is detached.  If the handle is already detached or closed, this
     will return zero.

     After calling this function, the handle is effectively invalidated,
     but the handle is not closed.  You would call this function when
     you need the underlying Win32 handle to exist beyond the lifetime
     of the handle object.

     引發一個附帶引數 ‘key’ 的*note 稽核事件: 17bd.
     ‘winreg.PyHKEY.Detach’。

 -- 方法: PyHKEY.__enter__ ()
 -- 方法: PyHKEY.__exit__ (*exc_info)

     The HKEY object implements *note __enter__(): 56c. and *note
     __exit__(): 1293. and thus supports the context protocol for the
     *note with: 577. statement:

          with OpenKey(HKEY_LOCAL_MACHINE, "foo") as key:
              ...  # work with key

     will automatically close 'key' when control leaves the *note with:
     577. block.


File: python.info,  Node: winsound --- Windows 的聲音播放介面,  Prev: winreg --- Windows 註冊表存取,  Up: MS Windows 特有服務

5.33.3 ‘winsound’ -- Windows 的聲音播放介面
-------------------------------------------

__________________________________________________________________

The *note winsound: ff. module provides access to the basic
sound-playing machinery provided by Windows platforms.  It includes
functions and several constants.

 -- 函式: winsound.Beep (frequency, duration)

     Beep the PC's speaker.  The 'frequency' parameter specifies
     frequency, in hertz, of the sound, and must be in the range 37
     through 32,767.  The 'duration' parameter specifies the number of
     milliseconds the sound should last.  If the system is not able to
     beep the speaker, *note RuntimeError: 179. is raised.

 -- 函式: winsound.PlaySound (sound, flags)

     Call the underlying ‘PlaySound()’ function from the Platform API.
     The 'sound' parameter may be a filename, a system sound alias,
     audio data as a *note bytes-like object: cd4, or ‘None’.  Its
     interpretation depends on the value of 'flags', which can be a
     bitwise ORed combination of the constants described below.  If the
     'sound' parameter is ‘None’, any currently playing waveform sound
     is stopped.  If the system indicates an error, *note RuntimeError:
     179. is raised.

 -- 函式: winsound.MessageBeep (type=MB_OK)

     Call the underlying ‘MessageBeep()’ function from the Platform API.
     This plays a sound as specified in the registry.  The 'type'
     argument specifies which sound to play; possible values are ‘-1’,
     ‘MB_ICONASTERISK’, ‘MB_ICONEXCLAMATION’, ‘MB_ICONHAND’,
     ‘MB_ICONQUESTION’, and ‘MB_OK’, all described below.  The value
     ‘-1’ produces a "simple beep"; this is the final fallback if a
     sound cannot be played otherwise.  If the system indicates an
     error, *note RuntimeError: 179. is raised.

 -- 資料: winsound.SND_FILENAME

     The 'sound' parameter is the name of a WAV file.  Do not use with
     *note SND_ALIAS: 45d0.

 -- 資料: winsound.SND_ALIAS

     The 'sound' parameter is a sound association name from the
     registry.  If the registry contains no such name, play the system
     default sound unless *note SND_NODEFAULT: 45d1. is also specified.
     If no default sound is registered, raise *note RuntimeError: 179.
     Do not use with *note SND_FILENAME: 45cf.

     All Win32 systems support at least the following; most systems
     support many more:

     *note PlaySound(): cad.        Corresponding Control Panel Sound name
     'name'                         

     ----------------------------------------------------------------------------
                                    
     ‘'SystemAsterisk'’             Asterisk
                                    
                                    
     ‘'SystemExclamation'’          Exclamation
                                    
                                    
     ‘'SystemExit'’                 Exit Windows
                                    
                                    
     ‘'SystemHand'’                 Critical Stop
                                    
                                    
     ‘'SystemQuestion'’             Question
                                    

     例如說：

          import winsound
          # Play Windows exit sound.
          winsound.PlaySound("SystemExit", winsound.SND_ALIAS)

          # Probably play Windows default sound, if any is registered (because
          # "*" probably isn't the registered name of any sound).
          winsound.PlaySound("*", winsound.SND_ALIAS)

 -- 資料: winsound.SND_LOOP

     Play the sound repeatedly.  The *note SND_ASYNC: 45d3. flag must
     also be used to avoid blocking.  Cannot be used with *note
     SND_MEMORY: 45d4.

 -- 資料: winsound.SND_MEMORY

     The 'sound' parameter to *note PlaySound(): cad. is a memory image
     of a WAV file, as a *note bytes-like object: cd4.

          備註: This module does not support playing from a memory image
          asynchronously, so a combination of this flag and *note
          SND_ASYNC: 45d3. will raise *note RuntimeError: 179.

 -- 資料: winsound.SND_PURGE

     Stop playing all instances of the specified sound.

          備註: This flag is not supported on modern Windows platforms.

 -- 資料: winsound.SND_ASYNC

     Return immediately, allowing sounds to play asynchronously.

 -- 資料: winsound.SND_NODEFAULT

     If the specified sound cannot be found, do not play the system
     default sound.

 -- 資料: winsound.SND_NOSTOP

     Do not interrupt sounds currently playing.

 -- 資料: winsound.SND_NOWAIT

     Return immediately if the sound driver is busy.

          備註: This flag is not supported on modern Windows platforms.

 -- 資料: winsound.MB_ICONASTERISK

     播放 ‘SystemDefault’ 聲音。

 -- 資料: winsound.MB_ICONEXCLAMATION

     播放 ‘SystemExclamation’ 聲音。

 -- 資料: winsound.MB_ICONHAND

     播放 ‘SystemHand’ 聲音。

 -- 資料: winsound.MB_ICONQUESTION

     播放 ‘SystemQuestion’ 聲音。

 -- 資料: winsound.MB_OK

     播放 ‘SystemDefault’ 聲音。


File: python.info,  Node: Unix 特有服務,  Next: 模組命令列介面,  Prev: MS Windows 特有服務,  Up: Python 標準函式庫 Standard Library

5.34 Unix 特有服務
==================

此章節所描述的模組 (module) 提供了針對 Unix 作業系統獨有特性的介面，或在
某些情況下可用於其他 Unix 變形版本。以下為概述：

* Menu:

* posix: posix --- 最常見的 POSIX 系統呼叫. 最常見的 POSIX 系統呼叫
* pwd: pwd --- 密碼資料庫. 密碼資料庫
* grp: grp --- 群組資料庫. 群組資料庫
* termios: termios --- POSIX 風格 tty 控制. POSIX 風格 tty 控制
* tty: tty --- 終端機控制函式. 終端機控制函式
* pty: pty --- 偽終端工具. 偽終端工具
* fcntl: fcntl --- fcntl 和 ioctl 系統呼叫. fcntl 和 ioctl 系統呼叫
* resource: resource --- 資源使用資訊. 資源使用資訊
* syslog: syslog --- Unix syslog 函式庫例程. Unix syslog 函式庫例程


File: python.info,  Node: posix --- 最常見的 POSIX 系統呼叫,  Next: pwd --- 密碼資料庫,  Up: Unix 特有服務

5.34.1 ‘posix’ -- 最常見的 POSIX 系統呼叫
-----------------------------------------

__________________________________________________________________

該模組提供對由 C 標準和 POSIX 標準（一種偽裝的 Unix 介面）所標準化的作業
系統功能的存取。

*note 適用: 1c56.：Unix。

'不要直接引入此模組。'請改為引入 *note os: 91. 模組，它提供了此介面的'可
移植 (portable)' 版本。在 Unix 上，*note os: 91. 模組提供了 *note posix:
9b. 介面的超集 (superset)。在非 Unix 作業系統上，*note posix: 9b. 模組不
可用，但始終可以通過 *note os: 91. 介面使用一個子集。一旦 *note os: 91.
有被引入，使用它代替 *note posix: 9b. '不會有'性能損失。此外，*note os:
91. 提供了一些額外的功能，例如當 ‘os.environ’ 中的條目更改時自動呼叫
*note putenv(): 8c1.。

錯誤會以例外的形式被回報；常見的例外是因為型別錯誤而給出的，而系統呼叫回
報的錯誤會引發 *note OSError: 350.。

* Menu:

* 對大檔案 (Large File) 的支援: 對大檔案 Large File 的支援.
* 值得注意的模組內容::


File: python.info,  Node: 對大檔案 Large File 的支援,  Next: 值得注意的模組內容,  Up: posix --- 最常見的 POSIX 系統呼叫

5.34.1.1 對大檔案 (Large File) 的支援
.....................................

一些作業系統（包括 AIX 和 Solaris）支援來自 C 程式模型且大於 2 GiB 的檔
案，其中 int 和 long 是 32-bit（32 位元）的值。這通常透過將相關大小和偏
移量 (offset) 種類定義為 64-bit 值來實作。此類檔案有時被稱為「大檔案
('large files')」。

當 ‘off_t’ 的大小大於 long 且 long long 的大小至少與 ‘off_t’ 相同時，對
大檔案的支援會被啟用。可能需要使用某些編譯器旗標來配置和編譯 Python 以啟
用此模式。例如，對於 Solaris 2.6 和 2.7，你需要執行如下操作：

     CFLAGS="`getconf LFS_CFLAGS`" OPT="-g -O2 $CFLAGS" \
             ./configure

在支援大檔案的 Linux 系統上，這可能有效：

     CFLAGS='-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64' OPT="-g -O2 $CFLAGS" \
             ./configure


File: python.info,  Node: 值得注意的模組內容,  Prev: 對大檔案 Large File 的支援,  Up: posix --- 最常見的 POSIX 系統呼叫

5.34.1.2 值得注意的模組內容
...........................

除了 *note os: 91. 模組說明文件中描述的許多函式外，*note posix: 9b. 還定
義了以下資料項目：

 -- 資料: posix.environ

     表示直譯器啟動時的字串環境的字典。鍵和值在 Unix 上是位元組，在
     Windows 上是 str。例如，‘environ[b'HOME']’（Windows 上為
     ‘environ['HOME']’）是你的主目錄的路徑名，等同於 C 語言中的
     ‘getenv("HOME")’。

     修改這個字典不會影響由 *note execv(): 2a04.、*note popen(): a2a. 或
     *note system(): 13c8. 傳遞的字串環境；如果你需要更改環境，請將
     ‘environ’ 傳遞給 *note execve(): 1091. 或將變數賦值和匯出陳述句新增
     到 *note system(): 13c8. 或 *note popen(): a2a. 的指令字串中。

     在 3.2 版的變更: 在 Unix 上，鍵和值是位元組。

          備註: *note os: 91. 模組提供了 ‘environ’ 的替代實作，會在修改
          時更新環境。另請注意，更新 *note os.environ: 1152. 將使該字典
          變成過時的。建議使用 *note os: 91. 模組版本，而不是直接存取
          *note posix: 9b. 模組。


File: python.info,  Node: pwd --- 密碼資料庫,  Next: grp --- 群組資料庫,  Prev: posix --- 最常見的 POSIX 系統呼叫,  Up: Unix 特有服務

5.34.2 ‘pwd’ -- 密碼資料庫
--------------------------

__________________________________________________________________

此模組提供對 Unix 使用者帳戶和密碼資料庫的存取介面。它適用於所有 Unix 版
本。

*note Availability: 1c56.: Unix, not WASI, not iOS.

密碼資料庫條目被報告為類似元組的物件 (tuple-like object)，其屬性會對應於
‘passwd’ 結構的成員（屬性欄位請見下面的 ‘<pwd.h>’）：

索引        屬性                意義
                                
------------------------------------------------------------------
                                
0           ‘pw_name’           登錄名
                                
                                
1           ‘pw_passwd’         可選的加密密碼
                                
                                
2           ‘pw_uid’            數值的使用者 ID
                                
                                
3           ‘pw_gid’            數值的群組 ID
                                
                                
4           ‘pw_gecos’          使用者名稱或註解欄位
                                
                                
5           ‘pw_dir’            使用者主目錄 (home directory)
                                
                                
6           ‘pw_shell’          使用者命令直譯器
                                

uid 和 gid 項目為整數，其他項目都是字串。如果找不到請求的條目，則會引發
*note KeyError: 2fb.。

     備註: In traditional Unix the field ‘pw_passwd’ usually contains a
     password encrypted with a DES derived algorithm.  However most
     modern unices use a so-called 'shadow password' system.  On those
     unices the 'pw_passwd' field only contains an asterisk (‘'*'’) or
     the letter ‘'x'’ where the encrypted password is stored in a file
     ‘/etc/shadow’ which is not world readable.  Whether the 'pw_passwd'
     field contains anything useful is system-dependent.

它定義了以下項目：

 -- 函式: pwd.getpwuid (uid)

     回傳給定數值使用者 ID 的密碼資料庫條目。

 -- 函式: pwd.getpwnam (name)

     回傳給定使用者名稱的密碼資料庫條目。

 -- 函式: pwd.getpwall ()

     以任意順序回傳所有可用密碼資料庫條目的 list。

也參考
......

*note grp: 5c. 模組

     群組資料庫的介面，與此模組類似。


File: python.info,  Node: grp --- 群組資料庫,  Next: termios --- POSIX 風格 tty 控制,  Prev: pwd --- 密碼資料庫,  Up: Unix 特有服務

5.34.3 ‘grp’ -- 群組資料庫
--------------------------

__________________________________________________________________

This module provides access to the Unix group database.  It is available
on all Unix versions.

*note Availability: 1c56.: Unix, not WASI, not iOS.

Group database entries are reported as a tuple-like object, whose
attributes correspond to the members of the ‘group’ structure (Attribute
field below, see ‘<grp.h>’):

Index       屬性            含義
                            
------------------------------------------------------------------
                            
0           gr_name         the name of the group
                            
                            
1           gr_passwd       the (encrypted) group password;
                            often empty
                            
                            
2           gr_gid          the numerical group ID
                            
                            
3           gr_mem          all the group member's user names
                            

The gid is an integer, name and password are strings, and the member
list is a list of strings.  (Note that most users are not explicitly
listed as members of the group they are in according to the password
database.  Check both databases to get complete membership information.
Also note that a ‘gr_name’ that starts with a ‘+’ or ‘-’ is likely to be
a YP/NIS reference and may not be accessible via *note getgrnam(): 303b.
or *note getgrgid(): ccd.)

It defines the following items:

 -- 函式: grp.getgrgid (id)

     Return the group database entry for the given numeric group ID.
     *note KeyError: 2fb. is raised if the entry asked for cannot be
     found.

     在 3.10 版的變更: *note TypeError: 4dd. is raised for non-integer
     arguments like floats or strings.

 -- 函式: grp.getgrnam (name)

     Return the group database entry for the given group name.  *note
     KeyError: 2fb. is raised if the entry asked for cannot be found.

 -- 函式: grp.getgrall ()

     Return a list of all available group entries, in arbitrary order.

也參考
......

*note pwd: a0. 模組

     An interface to the user database, similar to this.


File: python.info,  Node: termios --- POSIX 風格 tty 控制,  Next: tty --- 終端機控制函式,  Prev: grp --- 群組資料庫,  Up: Unix 特有服務

5.34.4 ‘termios’ -- POSIX 風格 tty 控制
---------------------------------------

__________________________________________________________________

This module provides an interface to the POSIX calls for tty I/O
control.  For a complete description of these calls, see ‘termios(3)(1)’
Unix manual page.  It is only available for those Unix versions that
support POSIX 'termios' style tty I/O control configured during
installation.

*note 適用: 1c56.：Unix。

All functions in this module take a file descriptor 'fd' as their first
argument.  This can be an integer file descriptor, such as returned by
‘sys.stdin.fileno()’, or a *note file object: 115b, such as ‘sys.stdin’
itself.

This module also defines all the constants needed to work with the
functions provided here; these have the same name as their counterparts
in C. Please refer to your system documentation for more information on
using these terminal control interfaces.

The module defines the following functions:

 -- 函式: termios.tcgetattr (fd)

     Return a list containing the tty attributes for file descriptor
     'fd', as follows: ‘[iflag, oflag, cflag, lflag, ispeed, ospeed,
     cc]’ where 'cc' is a list of the tty special characters (each a
     string of length 1, except the items with indices ‘VMIN’ and
     ‘VTIME’, which are integers when these fields are defined).  The
     interpretation of the flags and the speeds as well as the indexing
     in the 'cc' array must be done using the symbolic constants defined
     in the *note termios: ca. module.

 -- 函式: termios.tcsetattr (fd, when, attributes)

     Set the tty attributes for file descriptor 'fd' from the
     'attributes', which is a list like the one returned by *note
     tcgetattr(): 156c.  The 'when' argument determines when the
     attributes are changed:

      -- 資料: termios.TCSANOW

          Change attributes immediately.

      -- 資料: termios.TCSADRAIN

          Change attributes after transmitting all queued output.

      -- 資料: termios.TCSAFLUSH

          Change attributes after transmitting all queued output and
          discarding all queued input.

 -- 函式: termios.tcsendbreak (fd, duration)

     Send a break on file descriptor 'fd'.  A zero 'duration' sends a
     break for 0.25-0.5 seconds; a nonzero 'duration' has a system
     dependent meaning.

 -- 函式: termios.tcdrain (fd)

     Wait until all output written to file descriptor 'fd' has been
     transmitted.

 -- 函式: termios.tcflush (fd, queue)

     Discard queued data on file descriptor 'fd'.  The 'queue' selector
     specifies which queue: ‘TCIFLUSH’ for the input queue, ‘TCOFLUSH’
     for the output queue, or ‘TCIOFLUSH’ for both queues.

 -- 函式: termios.tcflow (fd, action)

     Suspend or resume input or output on file descriptor 'fd'.  The
     'action' argument can be ‘TCOOFF’ to suspend output, ‘TCOON’ to
     restart output, ‘TCIOFF’ to suspend input, or ‘TCION’ to restart
     input.

 -- 函式: termios.tcgetwinsize (fd)

     Return a tuple ‘(ws_row, ws_col)’ containing the tty window size
     for file descriptor 'fd'.  Requires ‘termios.TIOCGWINSZ’ or
     ‘termios.TIOCGSIZE’.

     在 3.11 版被加入.

 -- 函式: termios.tcsetwinsize (fd, winsize)

     Set the tty window size for file descriptor 'fd' from 'winsize',
     which is a two-item tuple ‘(ws_row, ws_col)’ like the one returned
     by *note tcgetwinsize(): 45f6.  Requires at least one of the pairs
     (‘termios.TIOCGWINSZ’, ‘termios.TIOCSWINSZ’); (‘termios.TIOCGSIZE’,
     ‘termios.TIOCSSIZE’) to be defined.

     在 3.11 版被加入.

也參考
......

*note tty: e9. 模組

     Convenience functions for common terminal control operations.

* Menu:

* 範例: 範例<48>.

   ---------- Footnotes ----------

   (1) https://manpages.debian.org/termios(3)


File: python.info,  Node: 範例<48>,  Up: termios --- POSIX 風格 tty 控制

5.34.4.1 範例
.............

Here's a function that prompts for a password with echoing turned off.
Note the technique using a separate *note tcgetattr(): 156c. call and a
*note try: 68c. ...  *note finally: 96e. statement to ensure that the
old tty attributes are restored exactly no matter what happens:

     def getpass(prompt="Password: "):
         import termios, sys
         fd = sys.stdin.fileno()
         old = termios.tcgetattr(fd)
         new = termios.tcgetattr(fd)
         new[3] = new[3] & ~termios.ECHO          # lflags
         try:
             termios.tcsetattr(fd, termios.TCSADRAIN, new)
             passwd = input(prompt)
         finally:
             termios.tcsetattr(fd, termios.TCSADRAIN, old)
         return passwd


File: python.info,  Node: tty --- 終端機控制函式,  Next: pty --- 偽終端工具,  Prev: termios --- POSIX 風格 tty 控制,  Up: Unix 特有服務

5.34.5 ‘tty’ -- 終端機控制函式
------------------------------

'原始碼：'Lib/tty.py(1)

__________________________________________________________________

*note tty: e9. 模組定義了將 tty 放入 cbreak 和 raw 模式的函式。

*note 適用: 1c56.：Unix。

因為它需要 *note termios: ca. 模組，所以只能在 Unix 上執行。

*note tty: e9. 模組定義了以下函式：

 -- 函式: tty.cfmakeraw (mode)

     Convert the tty attribute list 'mode', which is a list like the one
     returned by *note termios.tcgetattr(): 156c, to that of a tty in
     raw mode.

     在 3.12 版被加入.

 -- 函式: tty.cfmakecbreak (mode)

     Convert the tty attribute list 'mode', which is a list like the one
     returned by *note termios.tcgetattr(): 156c, to that of a tty in
     cbreak mode.

     This clears the ‘ECHO’ and ‘ICANON’ local mode flags in 'mode' as
     well as setting the minimum input to 1 byte with no delay.

     在 3.12 版被加入.

     在 3.12.2 版的變更: The ‘ICRNL’ flag is no longer cleared.  This
     matches Linux and macOS ‘stty cbreak’ behavior and what *note
     setcbreak(): 156e. historically did.

 -- 函式: tty.setraw (fd, when=termios.TCSAFLUSH)

     將檔案描述器 'fd' 的模式更改為 raw。如果 'when' 被省略，則預設為
     *note termios.TCSAFLUSH: 45f1.，並傳遞給 *note termios.tcsetattr():
     15f3.。*note termios.tcgetattr(): 156c. 的回傳值會在設定 'fd' 模式
     為 raw 之前先儲存起來。此函數回傳這個值。

     在 3.12 版的變更: 現在的回傳值為原本的 tty 屬性，而不是 ‘None’。

 -- 函式: tty.setcbreak (fd, when=termios.TCSAFLUSH)

     將檔案描述器 'fd' 的模式更改為 cbreak。如果 'when' 被省略，則預設為
     *note termios.TCSAFLUSH: 45f1.，並傳遞給 *note termios.tcsetattr():
     15f3.。*note termios.tcgetattr(): 156c. 的回傳值會在設定 'fd' 模式
     為 raw 之前先儲存起來。此函數回傳這個值。

     This clears the ‘ECHO’ and ‘ICANON’ local mode flags as well as
     setting the minimum input to 1 byte with no delay.

     在 3.12 版的變更: 現在的回傳值為原本的 tty 屬性，而不是 ‘None’。

     在 3.12.2 版的變更: The ‘ICRNL’ flag is no longer cleared.  This
     restores the behavior of Python 3.11 and earlier as well as
     matching what Linux, macOS, & BSDs describe in their ‘stty(1)’ man
     pages regarding cbreak mode.

也參考
......

*note termios: ca. 模組

     低階終端機控制介面。

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/tty.py


File: python.info,  Node: pty --- 偽終端工具,  Next: fcntl --- fcntl 和 ioctl 系統呼叫,  Prev: tty --- 終端機控制函式,  Up: Unix 特有服務

5.34.6 ‘pty’ -- 偽終端工具
--------------------------

'原始碼：'Lib/pty.py(1)

__________________________________________________________________

The *note pty: 9f. module defines operations for handling the
pseudo-terminal concept: starting another process and being able to
write to and read from its controlling terminal programmatically.

*note 適用: 1c56.：Unix。

Pseudo-terminal handling is highly platform dependent.  This code is
mainly tested on Linux, FreeBSD, and macOS (it is supposed to work on
other POSIX platforms but it's not been thoroughly tested).

The *note pty: 9f. module defines the following functions:

 -- 函式: pty.fork ()

     Fork.  Connect the child's controlling terminal to a
     pseudo-terminal.  Return value is ‘(pid, fd)’.  Note that the child
     gets 'pid' 0, and the 'fd' is 'invalid'.  The parent's return value
     is the 'pid' of the child, and 'fd' is a file descriptor connected
     to the child's controlling terminal (and also to the child's
     standard input and output).

          警告: On macOS the use of this function is unsafe when mixed
          with using higher-level system APIs, and that includes using
          *note urllib.request: f4.

 -- 函式: pty.openpty ()

     Open a new pseudo-terminal pair, using *note os.openpty(): 2a46. if
     possible, or emulation code for generic Unix systems.  Return a
     pair of file descriptors ‘(master, slave)’, for the master and the
     slave end, respectively.

 -- 函式: pty.spawn (argv[, master_read[, stdin_read]])

     Spawn a process, and connect its controlling terminal with the
     current process's standard io.  This is often used to baffle
     programs which insist on reading from the controlling terminal.  It
     is expected that the process spawned behind the pty will eventually
     terminate, and when it does 'spawn' will return.

     A loop copies STDIN of the current process to the child and data
     received from the child to STDOUT of the current process.  It is
     not signaled to the child if STDIN of the current process closes
     down.

     The functions 'master_read' and 'stdin_read' are passed a file
     descriptor which they should read from, and they should always
     return a byte string.  In order to force spawn to return before the
     child process exits an empty byte array should be returned to
     signal end of file.

     The default implementation for both functions will read and return
     up to 1024 bytes each time the function is called.  The
     'master_read' callback is passed the pseudoterminal’s master file
     descriptor to read output from the child process, and 'stdin_read'
     is passed file descriptor 0, to read from the parent process's
     standard input.

     Returning an empty byte string from either callback is interpreted
     as an end-of-file (EOF) condition, and that callback will not be
     called after that.  If 'stdin_read' signals EOF the controlling
     terminal can no longer communicate with the parent process OR the
     child process.  Unless the child process will quit without any
     input, 'spawn' will then loop forever.  If 'master_read' signals
     EOF the same behavior results (on linux at least).

     Return the exit status value from *note os.waitpid(): d40. on the
     child process.

     *note os.waitstatus_to_exitcode(): 8c2. can be used to convert the
     exit status into an exit code.

     引發一個附帶引數 ‘argv’ 的*note 稽核事件: 17bd. ‘pty.spawn’。

     在 3.4 版的變更: *note spawn(): f25. now returns the status value
     from *note os.waitpid(): d40. on the child process.

* Menu:

* 範例: 範例<49>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/pty.py


File: python.info,  Node: 範例<49>,  Up: pty --- 偽終端工具

5.34.6.1 範例
.............

The following program acts like the Unix command ‘script(1)(1)’, using a
pseudo-terminal to record all input and output of a terminal session in
a "typescript".

     import argparse
     import os
     import pty
     import sys
     import time

     parser = argparse.ArgumentParser()
     parser.add_argument('-a', dest='append', action='store_true')
     parser.add_argument('-p', dest='use_python', action='store_true')
     parser.add_argument('filename', nargs='?', default='typescript')
     options = parser.parse_args()

     shell = sys.executable if options.use_python else os.environ.get('SHELL', 'sh')
     filename = options.filename
     mode = 'ab' if options.append else 'wb'

     with open(filename, mode) as script:
         def read(fd):
             data = os.read(fd, 1024)
             script.write(data)
             return data

         print('Script started, file is', filename)
         script.write(('Script started on %s\n' % time.asctime()).encode())

         pty.spawn(shell, read)

         script.write(('Script done on %s\n' % time.asctime()).encode())
         print('Script done, file is', filename)

   ---------- Footnotes ----------

   (1) https://manpages.debian.org/script(1)


File: python.info,  Node: fcntl --- fcntl 和 ioctl 系統呼叫,  Next: resource --- 資源使用資訊,  Prev: pty --- 偽終端工具,  Up: Unix 特有服務

5.34.7 ‘fcntl’ -- ‘fcntl’ 和 ‘ioctl’ 系統呼叫
---------------------------------------------

__________________________________________________________________

This module performs file and I/O control on file descriptors.  It is an
interface to the ‘fcntl()’ and ‘ioctl()’ Unix routines.  See the
‘fcntl(2)(1)’ and ‘ioctl(2)(2)’ Unix manual pages for full details.

*note Availability: 1c56.: Unix, not WASI.

All functions in this module take a file descriptor 'fd' as their first
argument.  This can be an integer file descriptor, such as returned by
‘sys.stdin.fileno()’, or an *note io.IOBase: 1da. object, such as
‘sys.stdin’ itself, which provides a *note fileno(): 2732. that returns
a genuine file descriptor.

在 3.3 版的變更: Operations in this module used to raise an *note
IOError: ff5. where they now raise an *note OSError: 350.

在 3.8 版的變更: The ‘fcntl’ module now contains ‘F_ADD_SEALS’,
‘F_GET_SEALS’, and ‘F_SEAL_*’ constants for sealing of *note
os.memfd_create(): 9af. file descriptors.

在 3.9 版的變更: On macOS, the ‘fcntl’ module exposes the ‘F_GETPATH’
constant, which obtains the path of a file from a file descriptor.  On
Linux(>=3.15), the ‘fcntl’ module exposes the ‘F_OFD_GETLK’,
‘F_OFD_SETLK’ and ‘F_OFD_SETLKW’ constants, which are used when working
with open file description locks.

在 3.10 版的變更: On Linux >= 2.6.11, the ‘fcntl’ module exposes the
‘F_GETPIPE_SZ’ and ‘F_SETPIPE_SZ’ constants, which allow to check and
modify a pipe's size respectively.

在 3.11 版的變更: On FreeBSD, the ‘fcntl’ module exposes the ‘F_DUP2FD’
and ‘F_DUP2FD_CLOEXEC’ constants, which allow to duplicate a file
descriptor, the latter setting ‘FD_CLOEXEC’ flag in addition.

在 3.12 版的變更: On Linux >= 4.5, the *note fcntl: 4f. module exposes
the ‘FICLONE’ and ‘FICLONERANGE’ constants, which allow to share some
data of one file with another file by reflinking on some filesystems
(e.g., btrfs, OCFS2, and XFS). This behavior is commonly referred to as
"copy-on-write".

在 3.13 版的變更: On Linux >= 2.6.32, the ‘fcntl’ module exposes the
‘F_GETOWN_EX’, ‘F_SETOWN_EX’, ‘F_OWNER_TID’, ‘F_OWNER_PID’,
‘F_OWNER_PGRP’ constants, which allow to direct I/O availability signals
to a specific thread, process, or process group.  On Linux >= 4.13, the
‘fcntl’ module exposes the ‘F_GET_RW_HINT’, ‘F_SET_RW_HINT’,
‘F_GET_FILE_RW_HINT’, ‘F_SET_FILE_RW_HINT’, and ‘RWH_WRITE_LIFE_*’
constants, which allow to inform the kernel about the relative expected
lifetime of writes on a given inode or via a particular open file
description.  On Linux >= 5.1 and NetBSD, the ‘fcntl’ module exposes the
‘F_SEAL_FUTURE_WRITE’ constant for use with ‘F_ADD_SEALS’ and
‘F_GET_SEALS’ operations.  On FreeBSD, the ‘fcntl’ module exposes the
‘F_READAHEAD’, ‘F_ISUNIONSTACK’, and ‘F_KINFO’ constants.  On macOS and
FreeBSD, the ‘fcntl’ module exposes the ‘F_RDAHEAD’ constant.  On NetBSD
and AIX, the ‘fcntl’ module exposes the ‘F_CLOSEM’ constant.  On NetBSD,
the ‘fcntl’ module exposes the ‘F_MAXFD’ constant.  On macOS and NetBSD,
the ‘fcntl’ module exposes the ‘F_GETNOSIGPIPE’ and ‘F_SETNOSIGPIPE’
constant.

The module defines the following functions:

 -- 函式: fcntl.fcntl (fd, cmd, arg=0)

     Perform the operation 'cmd' on file descriptor 'fd' (file objects
     providing a *note fileno(): 2732. method are accepted as well).
     The values used for 'cmd' are operating system dependent, and are
     available as constants in the *note fcntl: 4f. module, using the
     same names as used in the relevant C header files.  The argument
     'arg' can either be an integer value, or a *note bytes: 1a5.
     object.  With an integer value, the return value of this function
     is the integer return value of the C ‘fcntl()’ call.  When the
     argument is bytes it represents a binary structure, e.g.  created
     by *note struct.pack(): 120f.  The binary data is copied to a
     buffer whose address is passed to the C ‘fcntl()’ call.  The return
     value after a successful call is the contents of the buffer,
     converted to a *note bytes: 1a5. object.  The length of the
     returned object will be the same as the length of the 'arg'
     argument.  This is limited to 1024 bytes.  If the information
     returned in the buffer by the operating system is larger than 1024
     bytes, this is most likely to result in a segmentation violation or
     a more subtle data corruption.

     If the ‘fcntl()’ call fails, an *note OSError: 350. is raised.

     引發一個附帶引數 ‘fd’、‘cmd’、‘arg’ 的*note 稽核事件: 17bd.
     ‘fcntl.fcntl’。

 -- 函式: fcntl.ioctl (fd, request, arg=0, mutate_flag=True)

     This function is identical to the *note fcntl(): 327c. function,
     except that the argument handling is even more complicated.

     The 'request' parameter is limited to values that can fit in
     32-bits.  Additional constants of interest for use as the 'request'
     argument can be found in the *note termios: ca. module, under the
     same names as used in the relevant C header files.

     The parameter 'arg' can be one of an integer, an object supporting
     the read-only buffer interface (like *note bytes: 1a5.) or an
     object supporting the read-write buffer interface (like *note
     bytearray: 4e3.).

     In all but the last case, behaviour is as for the *note fcntl():
     327c. function.

     If a mutable buffer is passed, then the behaviour is determined by
     the value of the 'mutate_flag' parameter.

     If it is false, the buffer's mutability is ignored and behaviour is
     as for a read-only buffer, except that the 1024 byte limit
     mentioned above is avoided - so long as the buffer you pass is at
     least as long as what the operating system wants to put there,
     things should work.

     If 'mutate_flag' is true (the default), then the buffer is (in
     effect) passed to the underlying *note ioctl(): 13e5. system call,
     the latter's return code is passed back to the calling Python, and
     the buffer's new contents reflect the action of the *note ioctl():
     13e5.  This is a slight simplification, because if the supplied
     buffer is less than 1024 bytes long it is first copied into a
     static buffer 1024 bytes long which is then passed to *note
     ioctl(): 13e5. and copied back into the supplied buffer.

     If the ‘ioctl()’ call fails, an *note OSError: 350. exception is
     raised.

     範例：

          >>> import array, fcntl, struct, termios, os
          >>> os.getpgrp()
          13341
          >>> struct.unpack('h', fcntl.ioctl(0, termios.TIOCGPGRP, "  "))[0]
          13341
          >>> buf = array.array('h', [0])
          >>> fcntl.ioctl(0, termios.TIOCGPGRP, buf, 1)
          0
          >>> buf
          array('h', [13341])

     引發一個附帶引數 ‘fd’、‘request’、‘arg’ 的*note 稽核事件: 17bd.
     ‘fcntl.ioctl’。

 -- 函式: fcntl.flock (fd, operation)

     Perform the lock operation 'operation' on file descriptor 'fd'
     (file objects providing a *note fileno(): 2732. method are accepted
     as well).  See the Unix manual ‘flock(2)(3)’ for details.  (On some
     systems, this function is emulated using ‘fcntl()’.)

     If the ‘flock()’ call fails, an *note OSError: 350. exception is
     raised.

     引發一個附帶引數 ‘fd’、‘operation’ 的*note 稽核事件: 17bd.
     ‘fcntl.flock’。

 -- 函式: fcntl.lockf (fd, cmd, len=0, start=0, whence=0)

     This is essentially a wrapper around the *note fcntl(): 327c.
     locking calls.  'fd' is the file descriptor (file objects providing
     a *note fileno(): 2732. method are accepted as well) of the file to
     lock or unlock, and 'cmd' is one of the following values:

      -- 資料: fcntl.LOCK_UN

          Release an existing lock.

      -- 資料: fcntl.LOCK_SH

          Acquire a shared lock.

      -- 資料: fcntl.LOCK_EX

          Acquire an exclusive lock.

      -- 資料: fcntl.LOCK_NB

          Bitwise OR with any of the other three ‘LOCK_*’ constants to
          make the request non-blocking.

     If ‘LOCK_NB’ is used and the lock cannot be acquired, an *note
     OSError: 350. will be raised and the exception will have an 'errno'
     attribute set to *note EACCES: 218b. or *note EAGAIN: 217c.
     (depending on the operating system; for portability, check for both
     values).  On at least some systems, ‘LOCK_EX’ can only be used if
     the file descriptor refers to a file opened for writing.

     'len' is the number of bytes to lock, 'start' is the byte offset at
     which the lock starts, relative to 'whence', and 'whence' is as
     with *note io.IOBase.seek(): 1224, specifically:

        * ‘0’ - relative to the start of the file (*note os.SEEK_SET:
          1225.)

        * ‘1’ - relative to the current buffer position (*note
          os.SEEK_CUR: 1226.)

        * ‘2’ - relative to the end of the file (*note os.SEEK_END:
          1227.)

     The default for 'start' is 0, which means to start at the beginning
     of the file.  The default for 'len' is 0 which means to lock to the
     end of the file.  The default for 'whence' is also 0.

     引發一個附帶引數 ‘fd’、‘cmd’、‘len’、‘start’、‘whence’ 的*note
     稽核事件: 17bd. ‘fcntl.lockf’。

Examples (all on a SVR4 compliant system):

     import struct, fcntl, os

     f = open(...)
     rv = fcntl.fcntl(f, fcntl.F_SETFL, os.O_NDELAY)

     lockdata = struct.pack('hhllhh', fcntl.F_WRLCK, 0, 0, 0, 0, 0)
     rv = fcntl.fcntl(f, fcntl.F_SETLKW, lockdata)

Note that in the first example the return value variable 'rv' will hold
an integer value; in the second example it will hold a *note bytes: 1a5.
object.  The structure lay-out for the 'lockdata' variable is system
dependent -- therefore using the *note flock(): 3ffb. call may be
better.

也參考
......

*note os: 91. 模組

     If the locking flags *note O_SHLOCK: 139c. and *note O_EXLOCK:
     139d. are present in the *note os: 91. module (on BSD only), the
     *note os.open(): d38. function provides an alternative to the *note
     lockf(): 135a. and *note flock(): 3ffb. functions.

   ---------- Footnotes ----------

   (1) https://manpages.debian.org/fcntl(2)

   (2) https://manpages.debian.org/ioctl(2)

   (3) https://manpages.debian.org/flock(2)


File: python.info,  Node: resource --- 資源使用資訊,  Next: syslog --- Unix syslog 函式庫例程,  Prev: fcntl --- fcntl 和 ioctl 系統呼叫,  Up: Unix 特有服務

5.34.8 ‘resource’ -- 資源使用資訊
---------------------------------

__________________________________________________________________

This module provides basic mechanisms for measuring and controlling
system resources utilized by a program.

*note Availability: 1c56.: Unix, not WASI.

Symbolic constants are used to specify particular system resources and
to request usage information about either the current process or its
children.

An *note OSError: 350. is raised on syscall failure.

 -- 例外: resource.error

     A deprecated alias of *note OSError: 350.

     在 3.3 版的變更: Following PEP 3151(1), this class was made an
     alias of *note OSError: 350.

* Menu:

* Resource Limits::
* Resource Usage::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3151/


File: python.info,  Node: Resource Limits,  Next: Resource Usage,  Up: resource --- 資源使用資訊

5.34.8.1 Resource Limits
........................

Resources usage can be limited using the *note setrlimit(): 3f9e.
function described below.  Each resource is controlled by a pair of
limits: a soft limit and a hard limit.  The soft limit is the current
limit, and may be lowered or raised by a process over time.  The soft
limit can never exceed the hard limit.  The hard limit can be lowered to
any value greater than the soft limit, but not raised.  (Only processes
with the effective UID of the super-user can raise a hard limit.)

The specific resources that can be limited are system dependent.  They
are described in the ‘getrlimit(2)(1)’ man page.  The resources listed
below are supported when the underlying operating system supports them;
resources which cannot be checked or controlled by the operating system
are not defined in this module for those platforms.

 -- 資料: resource.RLIM_INFINITY

     Constant used to represent the limit for an unlimited resource.

 -- 函式: resource.getrlimit (resource)

     Returns a tuple ‘(soft, hard)’ with the current soft and hard
     limits of 'resource'.  Raises *note ValueError: 1e7. if an invalid
     resource is specified, or *note error: 4607. if the underlying
     system call fails unexpectedly.

 -- 函式: resource.setrlimit (resource, limits)

     Sets new limits of consumption of 'resource'.  The 'limits'
     argument must be a tuple ‘(soft, hard)’ of two integers describing
     the new limits.  A value of *note RLIM_INFINITY: 4609. can be used
     to request a limit that is unlimited.

     Raises *note ValueError: 1e7. if an invalid resource is specified,
     if the new soft limit exceeds the hard limit, or if a process tries
     to raise its hard limit.  Specifying a limit of *note
     RLIM_INFINITY: 4609. when the hard or system limit for that
     resource is not unlimited will result in a *note ValueError: 1e7.
     A process with the effective UID of super-user can request any
     valid limit value, including unlimited, but *note ValueError: 1e7.
     will still be raised if the requested limit exceeds the system
     imposed limit.

     ‘setrlimit’ may also raise *note error: 4607. if the underlying
     system call fails.

     VxWorks only supports setting *note RLIMIT_NOFILE: 460b.

     引發一個附帶引數 ‘resource’、‘limits’ 的*note 稽核事件: 17bd.
     ‘resource.setrlimit’。

 -- 函式: resource.prlimit (pid, resource[, limits])

     Combines *note setrlimit(): 3f9e. and *note getrlimit(): 460a. in
     one function and supports to get and set the resources limits of an
     arbitrary process.  If 'pid' is 0, then the call applies to the
     current process.  'resource' and 'limits' have the same meaning as
     in *note setrlimit(): 3f9e, except that 'limits' is optional.

     When 'limits' is not given the function returns the 'resource'
     limit of the process 'pid'.  When 'limits' is given the 'resource'
     limit of the process is set and the former resource limit is
     returned.

     Raises *note ProcessLookupError: ffe. when 'pid' can't be found and
     *note PermissionError: ce9. when the user doesn't have
     ‘CAP_SYS_RESOURCE’ for the process.

     引發一個附帶引數 ‘pid’、‘resource’、‘limits’ 的*note 稽核事件:
     17bd. ‘resource.prlimit’。

     *note 適用: 1c56.：Linux 2.6.36 以上且具有 glibc 2.13 以上。

     在 3.4 版被加入.

These symbols define resources whose consumption can be controlled using
the *note setrlimit(): 3f9e. and *note getrlimit(): 460a. functions
described below.  The values of these symbols are exactly the constants
used by C programs.

The Unix man page for ‘getrlimit(2)(2)’ lists the available resources.
Note that not all systems use the same symbol or same value to denote
the same resource.  This module does not attempt to mask platform
differences -- symbols not defined for a platform will not be available
from this module on that platform.

 -- 資料: resource.RLIMIT_CORE

     The maximum size (in bytes) of a core file that the current process
     can create.  This may result in the creation of a partial core file
     if a larger core would be required to contain the entire process
     image.

 -- 資料: resource.RLIMIT_CPU

     The maximum amount of processor time (in seconds) that a process
     can use.  If this limit is exceeded, a ‘SIGXCPU’ signal is sent to
     the process.  (See the *note signal: b4. module documentation for
     information about how to catch this signal and do something useful,
     e.g.  flush open files to disk.)

 -- 資料: resource.RLIMIT_FSIZE

     The maximum size of a file which the process may create.

 -- 資料: resource.RLIMIT_DATA

     The maximum size (in bytes) of the process's heap.

 -- 資料: resource.RLIMIT_STACK

     The maximum size (in bytes) of the call stack for the current
     process.  This only affects the stack of the main thread in a
     multi-threaded process.

 -- 資料: resource.RLIMIT_RSS

     The maximum resident set size that should be made available to the
     process.

 -- 資料: resource.RLIMIT_NPROC

     The maximum number of processes the current process may create.

 -- 資料: resource.RLIMIT_NOFILE

     The maximum number of open file descriptors for the current
     process.

 -- 資料: resource.RLIMIT_OFILE

     The BSD name for *note RLIMIT_NOFILE: 460b.

 -- 資料: resource.RLIMIT_MEMLOCK

     The maximum address space which may be locked in memory.

 -- 資料: resource.RLIMIT_VMEM

     The largest area of mapped memory which the process may occupy.

     *note 適用: 1c56.：FreeBSD 11 以上。

 -- 資料: resource.RLIMIT_AS

     The maximum area (in bytes) of address space which may be taken by
     the process.

 -- 資料: resource.RLIMIT_MSGQUEUE

     The number of bytes that can be allocated for POSIX message queues.

     *note 適用: 1c56.：Linux 2.6.8 以上。

     在 3.4 版被加入.

 -- 資料: resource.RLIMIT_NICE

     The ceiling for the process's nice level (calculated as 20 -
     rlim_cur).

     *note 適用: 1c56.：Linux 2.6.12 以上。

     在 3.4 版被加入.

 -- 資料: resource.RLIMIT_RTPRIO

     The ceiling of the real-time priority.

     *note 適用: 1c56.：Linux 2.6.12 以上。

     在 3.4 版被加入.

 -- 資料: resource.RLIMIT_RTTIME

     The time limit (in microseconds) on CPU time that a process can
     spend under real-time scheduling without making a blocking syscall.

     *note 適用: 1c56.：Linux 2.6.25 以上。

     在 3.4 版被加入.

 -- 資料: resource.RLIMIT_SIGPENDING

     The number of signals which the process may queue.

     *note 適用: 1c56.：Linux 2.6.8 以上。

     在 3.4 版被加入.

 -- 資料: resource.RLIMIT_SBSIZE

     The maximum size (in bytes) of socket buffer usage for this user.
     This limits the amount of network memory, and hence the amount of
     mbufs, that this user may hold at any time.

     *note 適用: 1c56.：FreeBSD。

     在 3.4 版被加入.

 -- 資料: resource.RLIMIT_SWAP

     The maximum size (in bytes) of the swap space that may be reserved
     or used by all of this user id's processes.  This limit is enforced
     only if bit 1 of the vm.overcommit sysctl is set.  Please see
     tuning(7)(3) for a complete description of this sysctl.

     *note 適用: 1c56.：FreeBSD。

     在 3.4 版被加入.

 -- 資料: resource.RLIMIT_NPTS

     The maximum number of pseudo-terminals created by this user id.

     *note 適用: 1c56.：FreeBSD。

     在 3.4 版被加入.

 -- 資料: resource.RLIMIT_KQUEUES

     The maximum number of kqueues this user id is allowed to create.

     *note 適用: 1c56.：FreeBSD 11 以上。

     在 3.10 版被加入.

   ---------- Footnotes ----------

   (1) https://manpages.debian.org/getrlimit(2)

   (2) https://manpages.debian.org/getrlimit(2)

   (3) https://man.freebsd.org/cgi/man.cgi?query=tuning&sektion=7


File: python.info,  Node: Resource Usage,  Prev: Resource Limits,  Up: resource --- 資源使用資訊

5.34.8.2 Resource Usage
.......................

These functions are used to retrieve resource usage information:

 -- 函式: resource.getrusage (who)

     This function returns an object that describes the resources
     consumed by either the current process or its children, as
     specified by the 'who' parameter.  The 'who' parameter should be
     specified using one of the ‘RUSAGE_*’ constants described below.

     一個簡單範例：

          from resource import *
          import time

          # a non CPU-bound task
          time.sleep(3)
          print(getrusage(RUSAGE_SELF))

          # a CPU-bound task
          for i in range(10 ** 8):
             _ = 1 + 1
          print(getrusage(RUSAGE_SELF))

     The fields of the return value each describe how a particular
     system resource has been used, e.g.  amount of time spent running
     is user mode or number of times the process was swapped out of main
     memory.  Some values are dependent on the clock tick internal, e.g.
     the amount of memory the process is using.

     For backward compatibility, the return value is also accessible as
     a tuple of 16 elements.

     The fields ‘ru_utime’ and ‘ru_stime’ of the return value are
     floating-point values representing the amount of time spent
     executing in user mode and the amount of time spent executing in
     system mode, respectively.  The remaining values are integers.
     Consult the ‘getrusage(2)(1)’ man page for detailed information
     about these values.  A brief summary is presented here:

     Index        Field                     Resource
                                            
     -----------------------------------------------------------------------------------
                                            
     ‘0’          ‘ru_utime’                time in user mode (float seconds)
                                            
                                            
     ‘1’          ‘ru_stime’                time in system mode (float seconds)
                                            
                                            
     ‘2’          ‘ru_maxrss’               maximum resident set size
                                            
                                            
     ‘3’          ‘ru_ixrss’                shared memory size
                                            
                                            
     ‘4’          ‘ru_idrss’                unshared memory size
                                            
                                            
     ‘5’          ‘ru_isrss’                unshared stack size
                                            
                                            
     ‘6’          ‘ru_minflt’               page faults not requiring I/O
                                            
                                            
     ‘7’          ‘ru_majflt’               page faults requiring I/O
                                            
                                            
     ‘8’          ‘ru_nswap’                number of swap outs
                                            
                                            
     ‘9’          ‘ru_inblock’              block input operations
                                            
                                            
     ‘10’         ‘ru_oublock’              block output operations
                                            
                                            
     ‘11’         ‘ru_msgsnd’               messages sent
                                            
                                            
     ‘12’         ‘ru_msgrcv’               messages received
                                            
                                            
     ‘13’         ‘ru_nsignals’             signals received
                                            
                                            
     ‘14’         ‘ru_nvcsw’                voluntary context switches
                                            
                                            
     ‘15’         ‘ru_nivcsw’               involuntary context switches
                                            

     This function will raise a *note ValueError: 1e7. if an invalid
     'who' parameter is specified.  It may also raise *note error: 4607.
     exception in unusual circumstances.

 -- 函式: resource.getpagesize ()

     Returns the number of bytes in a system page.  (This need not be
     the same as the hardware page size.)

The following ‘RUSAGE_*’ symbols are passed to the *note getrusage():
139e. function to specify which processes information should be provided
for.

 -- 資料: resource.RUSAGE_SELF

     Pass to *note getrusage(): 139e. to request resources consumed by
     the calling process, which is the sum of resources used by all
     threads in the process.

 -- 資料: resource.RUSAGE_CHILDREN

     Pass to *note getrusage(): 139e. to request resources consumed by
     child processes of the calling process which have been terminated
     and waited for.

 -- 資料: resource.RUSAGE_BOTH

     Pass to *note getrusage(): 139e. to request resources consumed by
     both the current process and child processes.  May not be available
     on all systems.

 -- 資料: resource.RUSAGE_THREAD

     Pass to *note getrusage(): 139e. to request resources consumed by
     the current thread.  May not be available on all systems.

     在 3.2 版被加入.

   ---------- Footnotes ----------

   (1) https://manpages.debian.org/getrusage(2)


File: python.info,  Node: syslog --- Unix syslog 函式庫例程,  Prev: resource --- 資源使用資訊,  Up: Unix 特有服務

5.34.9 ‘syslog’ -- Unix syslog 函式庫例程
-----------------------------------------

__________________________________________________________________

This module provides an interface to the Unix ‘syslog’ library routines.
Refer to the Unix manual pages for a detailed description of the
‘syslog’ facility.

*note Availability: 1c56.: Unix, not WASI, not iOS.

This module wraps the system ‘syslog’ family of routines.  A pure Python
library that can speak to a syslog server is available in the *note
logging.handlers: 7d. module as *note SysLogHandler: 602.

該模組定義了以下函式：

 -- 函式: syslog.syslog (message)

 -- 函式: syslog.syslog (priority, message)

     Send the string 'message' to the system logger.  A trailing newline
     is added if necessary.  Each message is tagged with a priority
     composed of a 'facility' and a 'level'.  The optional 'priority'
     argument, which defaults to *note LOG_INFO: 461e, determines the
     message priority.  If the facility is not encoded in 'priority'
     using logical-or (‘LOG_INFO | LOG_USER’), the value given in the
     *note openlog(): 4e4. call is used.

     If *note openlog(): 4e4. has not been called prior to the call to
     *note syslog(): c6, *note openlog(): 4e4. will be called with no
     arguments.

     引發一個附帶引數 ‘priority’、‘message’ 的*note 稽核事件: 17bd.
     ‘syslog.syslog’。

     在 3.2 版的變更: In previous versions, *note openlog(): 4e4. would
     not be called automatically if it wasn't called prior to the call
     to *note syslog(): c6, deferring to the syslog implementation to
     call ‘openlog()’.

     在 3.12 版的變更: This function is restricted in subinterpreters.
     (Only code that runs in multiple interpreters is affected and the
     restriction is not relevant for most users.)  *note openlog(): 4e4.
     must be called in the main interpreter before *note syslog(): c6.
     may be used in a subinterpreter.  Otherwise it will raise *note
     RuntimeError: 179.

 -- 函式: syslog.openlog ([ident[, logoption[, facility]]])

     Logging options of subsequent *note syslog(): c6. calls can be set
     by calling *note openlog(): 4e4.  *note syslog(): c6. will call
     *note openlog(): 4e4. with no arguments if the log is not currently
     open.

     The optional 'ident' keyword argument is a string which is
     prepended to every message, and defaults to ‘sys.argv[0]’ with
     leading path components stripped.  The optional 'logoption' keyword
     argument (default is 0) is a bit field - see below for possible
     values to combine.  The optional 'facility' keyword argument
     (default is *note LOG_USER: 461f.) sets the default facility for
     messages which do not have a facility explicitly encoded.

     引發一個附帶引數 ‘ident’、‘logoption’、‘facility’ 的*note 稽核事件:
     17bd. ‘syslog.openlog’。

     在 3.2 版的變更: In previous versions, keyword arguments were not
     allowed, and 'ident' was required.

     在 3.12 版的變更: This function is restricted in subinterpreters.
     (Only code that runs in multiple interpreters is affected and the
     restriction is not relevant for most users.)  This may only be
     called in the main interpreter.  It will raise *note RuntimeError:
     179. if called in a subinterpreter.

 -- 函式: syslog.closelog ()

     Reset the syslog module values and call the system library
     ‘closelog()’.

     This causes the module to behave as it does when initially
     imported.  For example, *note openlog(): 4e4. will be called on the
     first *note syslog(): c6. call (if *note openlog(): 4e4. hasn't
     already been called), and 'ident' and other *note openlog(): 4e4.
     parameters are reset to defaults.

     引發一個不附帶引數的*note 稽核事件: 17bd. ‘syslog.closelog’。

     在 3.12 版的變更: This function is restricted in subinterpreters.
     (Only code that runs in multiple interpreters is affected and the
     restriction is not relevant for most users.)  This may only be
     called in the main interpreter.  It will raise *note RuntimeError:
     179. if called in a subinterpreter.

 -- 函式: syslog.setlogmask (maskpri)

     Set the priority mask to 'maskpri' and return the previous mask
     value.  Calls to *note syslog(): c6. with a priority level not set
     in 'maskpri' are ignored.  The default is to log all priorities.
     The function ‘LOG_MASK(pri)’ calculates the mask for the individual
     priority 'pri'.  The function ‘LOG_UPTO(pri)’ calculates the mask
     for all priorities up to and including 'pri'.

     引發一個附帶引數 ‘maskpri’ 的*note 稽核事件: 17bd.
     ‘syslog.setlogmask’。

The module defines the following constants:

 -- 資料: syslog.LOG_EMERG
 -- 資料: syslog.LOG_ALERT
 -- 資料: syslog.LOG_CRIT
 -- 資料: syslog.LOG_ERR
 -- 資料: syslog.LOG_WARNING
 -- 資料: syslog.LOG_NOTICE
 -- 資料: syslog.LOG_INFO
 -- 資料: syslog.LOG_DEBUG

     Priority levels (high to low).

 -- 資料: syslog.LOG_AUTH
 -- 資料: syslog.LOG_AUTHPRIV
 -- 資料: syslog.LOG_CRON
 -- 資料: syslog.LOG_DAEMON
 -- 資料: syslog.LOG_FTP
 -- 資料: syslog.LOG_INSTALL
 -- 資料: syslog.LOG_KERN
 -- 資料: syslog.LOG_LAUNCHD
 -- 資料: syslog.LOG_LPR
 -- 資料: syslog.LOG_MAIL
 -- 資料: syslog.LOG_NETINFO
 -- 資料: syslog.LOG_NEWS
 -- 資料: syslog.LOG_RAS
 -- 資料: syslog.LOG_REMOTEAUTH
 -- 資料: syslog.LOG_SYSLOG
 -- 資料: syslog.LOG_USER
 -- 資料: syslog.LOG_UUCP
 -- 資料: syslog.LOG_LOCAL0
 -- 資料: syslog.LOG_LOCAL1
 -- 資料: syslog.LOG_LOCAL2
 -- 資料: syslog.LOG_LOCAL3
 -- 資料: syslog.LOG_LOCAL4
 -- 資料: syslog.LOG_LOCAL5
 -- 資料: syslog.LOG_LOCAL6
 -- 資料: syslog.LOG_LOCAL7

     Facilities, depending on availability in ‘<syslog.h>’ for *note
     LOG_AUTHPRIV: 4628, *note LOG_FTP: 462b, *note LOG_NETINFO: 4631,
     *note LOG_REMOTEAUTH: 4634, *note LOG_INSTALL: 462c. and *note
     LOG_RAS: 4633.

     在 3.13 版的變更: Added *note LOG_FTP: 462b, *note LOG_NETINFO:
     4631, *note LOG_REMOTEAUTH: 4634, *note LOG_INSTALL: 462c, *note
     LOG_RAS: 4633, and *note LOG_LAUNCHD: 462e.

 -- 資料: syslog.LOG_PID
 -- 資料: syslog.LOG_CONS
 -- 資料: syslog.LOG_NDELAY
 -- 資料: syslog.LOG_ODELAY
 -- 資料: syslog.LOG_NOWAIT
 -- 資料: syslog.LOG_PERROR

     Log options, depending on availability in ‘<syslog.h>’ for *note
     LOG_ODELAY: 4642, *note LOG_NOWAIT: 4643. and *note LOG_PERROR:
     4644.

* Menu:

* 範例: 範例<50>.


File: python.info,  Node: 範例<50>,  Up: syslog --- Unix syslog 函式庫例程

5.34.9.1 範例
.............

* Menu:

* 簡單範例: 簡單範例<2>.


File: python.info,  Node: 簡單範例<2>,  Up: 範例<50>

5.34.9.2 簡單範例
.................

一組簡單範例：

     import syslog

     syslog.syslog('Processing started')
     if error:
         syslog.syslog(syslog.LOG_ERR, 'Processing started')

An example of setting some log options, these would include the process
ID in logged messages, and write the messages to the destination
facility used for mail logging:

     syslog.openlog(logoption=syslog.LOG_PID, facility=syslog.LOG_MAIL)
     syslog.syslog('E-mail processing initiated...')


File: python.info,  Node: 模組命令列介面,  Next: 已被取代的模組,  Prev: Unix 特有服務,  Up: Python 標準函式庫 Standard Library

5.35 模組命令列介面
===================

以下模組具有命令列介面。

   * *note ast: 4426.

   * *note asyncio: 30b9.

   * *note base64: a.

   * *note calendar: 23c1.

   * *note code: 13.

   * *note compileall: 44e3.

   * *note cProfile: 20.: 請見 *note profile: 408f.

   * *note difflib: 2213.

   * *note dis: 44f9.

   * *note doctest: 31.

   * ‘encodings.rot_13’

   * *note ensurepip: 4b.

   * *note filecmp: 50.

   * *note fileinput: 51.

   * *note ftplib: 54.

   * *note gzip: 284f.

   * *note http.server: ef4.

   * ‘idlelib’

   * *note inspect: efe.

   * *note json.tool: 3499.

   * *note mimetypes: 82.

   * *note pdb: 94.

   * *note pickle: 95.

   * *note pickletools: 4564.

   * *note platform: 98.

   * *note poplib: 9a.

   * *note profile: 408f.

   * *note pstats: 9e.

   * *note py_compile: 44db.

   * *note pyclbr: a2.

   * *note pydoc: a3.

   * *note quopri: a5.

   * *note random: 139.

   * *note runpy: ac.

   * *note site: 42da.

   * *note sqlite3: 3e7.

   * *note sysconfig: 41ea.

   * *note tabnanny: c7.

   * *note tarfile: f6e.

   * ‘this’

   * *note timeit: 40af.

   * *note tokenize: 44af.

   * *note trace: 40cb.

   * *note turtledemo: eb.

   * *note unittest: 3e77.

   * *note uuid: 3ea.

   * *note venv: f9.

   * *note webbrowser: fd.

   * *note zipapp: 4149.

   * *note zipfile: 28bd.

另請見 *note Python 命令列介面: 18c4.。


File: python.info,  Node: 已被取代的模組,  Next: 安全性注意事項<4>,  Prev: 模組命令列介面,  Up: Python 標準函式庫 Standard Library

5.36 已被取代的模組
===================

The modules described in this chapter are deprecated or *note soft
deprecated: 1ee. and only kept for backwards compatibility.  They have
been superseded by other modules.

* Menu:

* getopt: getopt --- 用於命令列選項的 C 風格剖析器. 用於命令列選項的 C 風格剖析器
* optparse: optparse --- 命令列選項剖析器. 命令列選項剖析器


File: python.info,  Node: getopt --- 用於命令列選項的 C 風格剖析器,  Next: optparse --- 命令列選項剖析器,  Up: 已被取代的模組

5.36.1 ‘getopt’ -- 用於命令列選項的 C 風格剖析器
------------------------------------------------

'原始碼：'Lib/getopt.py(1)

在 3.13 版之後被棄用: The *note getopt: 57. module is *note soft
deprecated: 1ee. and will not be developed further; development will
continue with the *note argparse: 5. module.

     備註: The *note getopt: 57. module is a parser for command line
     options whose API is designed to be familiar to users of the C
     ‘getopt()’ function.  Users who are unfamiliar with the C
     ‘getopt()’ function or who would like to write less code and get
     better help and error messages should consider using the *note
     argparse: 5. module instead.

__________________________________________________________________

This module helps scripts to parse the command line arguments in
‘sys.argv’.  It supports the same conventions as the Unix ‘getopt()’
function (including the special meanings of arguments of the form '‘-’'
and '‘--’').  Long options similar to those supported by GNU software
may be used as well via an optional third argument.

This module provides two functions and an exception:

 -- 函式: getopt.getopt (args, shortopts, longopts=[])

     Parses command line options and parameter list.  'args' is the
     argument list to be parsed, without the leading reference to the
     running program.  Typically, this means ‘sys.argv[1:]’.
     'shortopts' is the string of option letters that the script wants
     to recognize, with options that require an argument followed by a
     colon (‘':'’; i.e., the same format that Unix ‘getopt()’ uses).

          備註: Unlike GNU ‘getopt()’, after a non-option argument, all
          further arguments are considered also non-options.  This is
          similar to the way non-GNU Unix systems work.

     'longopts', if specified, must be a list of strings with the names
     of the long options which should be supported.  The leading ‘'--'’
     characters should not be included in the option name.  Long options
     which require an argument should be followed by an equal sign
     (‘'='’).  Optional arguments are not supported.  To accept only
     long options, 'shortopts' should be an empty string.  Long options
     on the command line can be recognized so long as they provide a
     prefix of the option name that matches exactly one of the accepted
     options.  For example, if 'longopts' is ‘['foo', 'frob']’, the
     option ‘--fo’ will match as ‘--foo’, but ‘--f’ will not match
     uniquely, so *note GetoptError: 464e. will be raised.

     The return value consists of two elements: the first is a list of
     ‘(option, value)’ pairs; the second is the list of program
     arguments left after the option list was stripped (this is a
     trailing slice of 'args').  Each option-and-value pair returned has
     the option as its first element, prefixed with a hyphen for short
     options (e.g., ‘'-x'’) or two hyphens for long options (e.g.,
     ‘'--long-option'’), and the option argument as its second element,
     or an empty string if the option has no argument.  The options
     occur in the list in the same order in which they were found, thus
     allowing multiple occurrences.  Long and short options may be
     mixed.

 -- 函式: getopt.gnu_getopt (args, shortopts, longopts=[])

     This function works like *note getopt(): 57, except that GNU style
     scanning mode is used by default.  This means that option and
     non-option arguments may be intermixed.  The *note getopt(): 57.
     function stops processing options as soon as a non-option argument
     is encountered.

     If the first character of the option string is ‘'+'’, or if the
     environment variable ‘POSIXLY_CORRECT’ is set, then option
     processing stops as soon as a non-option argument is encountered.

 -- 例外: getopt.GetoptError

     This is raised when an unrecognized option is found in the argument
     list or when an option requiring an argument is given none.  The
     argument to the exception is a string indicating the cause of the
     error.  For long options, an argument given to an option which does
     not require one will also cause this exception to be raised.  The
     attributes ‘msg’ and ‘opt’ give the error message and related
     option; if there is no specific option to which the exception
     relates, ‘opt’ is an empty string.

 -- 例外: getopt.error

     Alias for *note GetoptError: 464e.; for backward compatibility.

An example using only Unix style options:

     >>> import getopt
     >>> args = '-a -b -cfoo -d bar a1 a2'.split()
     >>> args
     ['-a', '-b', '-cfoo', '-d', 'bar', 'a1', 'a2']
     >>> optlist, args = getopt.getopt(args, 'abc:d:')
     >>> optlist
     [('-a', ''), ('-b', ''), ('-c', 'foo'), ('-d', 'bar')]
     >>> args
     ['a1', 'a2']

Using long option names is equally easy:

     >>> s = '--condition=foo --testing --output-file abc.def -x a1 a2'
     >>> args = s.split()
     >>> args
     ['--condition=foo', '--testing', '--output-file', 'abc.def', '-x', 'a1', 'a2']
     >>> optlist, args = getopt.getopt(args, 'x', [
     ...     'condition=', 'output-file=', 'testing'])
     >>> optlist
     [('--condition', 'foo'), ('--testing', ''), ('--output-file', 'abc.def'), ('-x', '')]
     >>> args
     ['a1', 'a2']

In a script, typical usage is something like this:

     import getopt, sys

     def main():
         try:
             opts, args = getopt.getopt(sys.argv[1:], "ho:v", ["help", "output="])
         except getopt.GetoptError as err:
             # print help information and exit:
             print(err)  # will print something like "option -a not recognized"
             usage()
             sys.exit(2)
         output = None
         verbose = False
         for o, a in opts:
             if o == "-v":
                 verbose = True
             elif o in ("-h", "--help"):
                 usage()
                 sys.exit()
             elif o in ("-o", "--output"):
                 output = a
             else:
                 assert False, "unhandled option"
         # ...

     if __name__ == "__main__":
         main()

Note that an equivalent command line interface could be produced with
less code and more informative help and error messages by using the
*note argparse: 5. module:

     import argparse

     if __name__ == '__main__':
         parser = argparse.ArgumentParser()
         parser.add_argument('-o', '--output')
         parser.add_argument('-v', dest='verbose', action='store_true')
         args = parser.parse_args()
         # ... do something with args.output ...
         # ... do something with args.verbose ..

也參考
......

*note argparse: 5. 模組

     Alternative command line option and argument parsing library.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/getopt.py


File: python.info,  Node: optparse --- 命令列選項剖析器,  Prev: getopt --- 用於命令列選項的 C 風格剖析器,  Up: 已被取代的模組

5.36.2 ‘optparse’ -- 命令列選項剖析器
-------------------------------------

'原始碼：'Lib/optparse.py(1)

在 3.2 版之後被棄用: The *note optparse: 90. module is *note soft
deprecated: 1ee. and will not be developed further; development will
continue with the *note argparse: 5. module.

__________________________________________________________________

*note optparse: 90. is a more convenient, flexible, and powerful library
for parsing command-line options than the old *note getopt: 57. module.
*note optparse: 90. uses a more declarative style of command-line
parsing: you create an instance of *note OptionParser: 143c, populate it
with options, and parse the command line.  *note optparse: 90. allows
users to specify options in the conventional GNU/POSIX syntax, and
additionally generates usage and help messages for you.

Here's an example of using *note optparse: 90. in a simple script:

     from optparse import OptionParser
     ...
     parser = OptionParser()
     parser.add_option("-f", "--file", dest="filename",
                       help="write report to FILE", metavar="FILE")
     parser.add_option("-q", "--quiet",
                       action="store_false", dest="verbose", default=True,
                       help="don't print status messages to stdout")

     (options, args) = parser.parse_args()

With these few lines of code, users of your script can now do the "usual
thing" on the command-line, for example:

     <yourscript> --file=outfile -q

As it parses the command line, *note optparse: 90. sets attributes of
the ‘options’ object returned by *note parse_args(): 143d. based on
user-supplied command-line values.  When *note parse_args(): 143d.
returns from parsing this command line, ‘options.filename’ will be
‘"outfile"’ and ‘options.verbose’ will be ‘False’.  *note optparse: 90.
supports both long and short options, allows short options to be merged
together, and allows options to be associated with their arguments in a
variety of ways.  Thus, the following command lines are all equivalent
to the above example:

     <yourscript> -f outfile --quiet
     <yourscript> --quiet --file outfile
     <yourscript> -q -foutfile
     <yourscript> -qfoutfile

Additionally, users can run one of the following

     <yourscript> -h
     <yourscript> --help

and *note optparse: 90. will print out a brief summary of your script's
options:

     Usage: <yourscript> [options]

     Options:
       -h, --help            show this help message and exit
       -f FILE, --file=FILE  write report to FILE
       -q, --quiet           don't print status messages to stdout

where the value of 'yourscript' is determined at runtime (normally from
‘sys.argv[0]’).

* Menu:

* 背景::
* 教學: 教學<4>.
* Reference Guide::
* Option Callbacks::
* Extending optparse::
* 例外: 例外<16>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Lib/optparse.py


File: python.info,  Node: 背景,  Next: 教學<4>,  Up: optparse --- 命令列選項剖析器

5.36.2.1 背景
.............

*note optparse: 90. was explicitly designed to encourage the creation of
programs with straightforward, conventional command-line interfaces.  To
that end, it supports only the most common command-line syntax and
semantics conventionally used under Unix.  If you are unfamiliar with
these conventions, read this section to acquaint yourself with them.

* Menu:

* 術語::
* What are options for?::
* What are positional arguments for?::


File: python.info,  Node: 術語,  Next: What are options for?,  Up: 背景

5.36.2.2 術語
.............

argument

     a string entered on the command-line, and passed by the shell to
     ‘execl()’ or ‘execv()’.  In Python, arguments are elements of
     ‘sys.argv[1:]’ (‘sys.argv[0]’ is the name of the program being
     executed).  Unix shells also use the term "word".

     It is occasionally desirable to substitute an argument list other
     than ‘sys.argv[1:]’, so you should read "argument" as "an element
     of ‘sys.argv[1:]’, or of some other list provided as a substitute
     for ‘sys.argv[1:]’".

option

     an argument used to supply extra information to guide or customize
     the execution of a program.  There are many different syntaxes for
     options; the traditional Unix syntax is a hyphen ("-") followed by
     a single letter, e.g.  ‘-x’ or ‘-F’.  Also, traditional Unix syntax
     allows multiple options to be merged into a single argument, e.g.
     ‘-x -F’ is equivalent to ‘-xF’.  The GNU project introduced ‘--’
     followed by a series of hyphen-separated words, e.g.  ‘--file’ or
     ‘--dry-run’.  These are the only two option syntaxes provided by
     *note optparse: 90.

     Some other option syntaxes that the world has seen include:

        * a hyphen followed by a few letters, e.g.  ‘-pf’ (this is 'not'
          the same as multiple options merged into a single argument)

        * a hyphen followed by a whole word, e.g.  ‘-file’ (this is
          technically equivalent to the previous syntax, but they aren't
          usually seen in the same program)

        * a plus sign followed by a single letter, or a few letters, or
          a word, e.g.  ‘+f’, ‘+rgb’

        * a slash followed by a letter, or a few letters, or a word,
          e.g.  ‘/f’, ‘/file’

     These option syntaxes are not supported by *note optparse: 90, and
     they never will be.  This is deliberate: the first three are
     non-standard on any environment, and the last only makes sense if
     you're exclusively targeting Windows or certain legacy platforms
     (e.g.  VMS, MS-DOS).

option argument

     an argument that follows an option, is closely associated with that
     option, and is consumed from the argument list when that option is.
     With *note optparse: 90, option arguments may either be in a
     separate argument from their option:

          -f foo
          --file foo

     or included in the same argument:

          -ffoo
          --file=foo

     Typically, a given option either takes an argument or it doesn't.
     Lots of people want an "optional option arguments" feature, meaning
     that some options will take an argument if they see it, and won't
     if they don't.  This is somewhat controversial, because it makes
     parsing ambiguous: if ‘-a’ takes an optional argument and ‘-b’ is
     another option entirely, how do we interpret ‘-ab’?  Because of
     this ambiguity, *note optparse: 90. does not support this feature.

positional argument

     something leftover in the argument list after options have been
     parsed, i.e.  after options and their arguments have been parsed
     and removed from the argument list.

required option

     an option that must be supplied on the command-line; note that the
     phrase "required option" is self-contradictory in English.  *note
     optparse: 90. doesn't prevent you from implementing required
     options, but doesn't give you much help at it either.

For example, consider this hypothetical command-line:

     prog -v --report report.txt foo bar

‘-v’ and ‘--report’ are both options.  Assuming that ‘--report’ takes
one argument, ‘report.txt’ is an option argument.  ‘foo’ and ‘bar’ are
positional arguments.


File: python.info,  Node: What are options for?,  Next: What are positional arguments for?,  Prev: 術語,  Up: 背景

5.36.2.3 What are options for?
..............................

Options are used to provide extra information to tune or customize the
execution of a program.  In case it wasn't clear, options are usually
'optional'.  A program should be able to run just fine with no options
whatsoever.  (Pick a random program from the Unix or GNU toolsets.  Can
it run without any options at all and still make sense?  The main
exceptions are ‘find’, ‘tar’, and ‘dd’--all of which are mutant oddballs
that have been rightly criticized for their non-standard syntax and
confusing interfaces.)

Lots of people want their programs to have "required options".  Think
about it.  If it's required, then it's 'not optional'!  If there is a
piece of information that your program absolutely requires in order to
run successfully, that's what positional arguments are for.

As an example of good command-line interface design, consider the humble
‘cp’ utility, for copying files.  It doesn't make much sense to try to
copy files without supplying a destination and at least one source.
Hence, ‘cp’ fails if you run it with no arguments.  However, it has a
flexible, useful syntax that does not require any options at all:

     cp SOURCE DEST
     cp SOURCE ... DEST-DIR

You can get pretty far with just that.  Most ‘cp’ implementations
provide a bunch of options to tweak exactly how the files are copied:
you can preserve mode and modification time, avoid following symlinks,
ask before clobbering existing files, etc.  But none of this distracts
from the core mission of ‘cp’, which is to copy either one file to
another, or several files to another directory.


File: python.info,  Node: What are positional arguments for?,  Prev: What are options for?,  Up: 背景

5.36.2.4 What are positional arguments for?
...........................................

Positional arguments are for those pieces of information that your
program absolutely, positively requires to run.

A good user interface should have as few absolute requirements as
possible.  If your program requires 17 distinct pieces of information in
order to run successfully, it doesn't much matter 'how' you get that
information from the user--most people will give up and walk away before
they successfully run the program.  This applies whether the user
interface is a command-line, a configuration file, or a GUI: if you make
that many demands on your users, most of them will simply give up.

In short, try to minimize the amount of information that users are
absolutely required to supply--use sensible defaults whenever possible.
Of course, you also want to make your programs reasonably flexible.
That's what options are for.  Again, it doesn't matter if they are
entries in a config file, widgets in the "Preferences" dialog of a GUI,
or command-line options--the more options you implement, the more
flexible your program is, and the more complicated its implementation
becomes.  Too much flexibility has drawbacks as well, of course; too
many options can overwhelm users and make your code much harder to
maintain.


File: python.info,  Node: 教學<4>,  Next: Reference Guide,  Prev: 背景,  Up: optparse --- 命令列選項剖析器

5.36.2.5 教學
.............

While *note optparse: 90. is quite flexible and powerful, it's also
straightforward to use in most cases.  This section covers the code
patterns that are common to any *note optparse: 90.-based program.

First, you need to import the OptionParser class; then, early in the
main program, create an OptionParser instance:

     from optparse import OptionParser
     ...
     parser = OptionParser()

Then you can start defining options.  The basic syntax is:

     parser.add_option(opt_str, ...,
                       attr=value, ...)

Each option has one or more option strings, such as ‘-f’ or ‘--file’,
and several option attributes that tell *note optparse: 90. what to
expect and what to do when it encounters that option on the command
line.

Typically, each option will have one short option string and one long
option string, e.g.:

     parser.add_option("-f", "--file", ...)

You're free to define as many short option strings and as many long
option strings as you like (including zero), as long as there is at
least one option string overall.

The option strings passed to *note OptionParser.add_option(): 2b9e. are
effectively labels for the option defined by that call.  For brevity, we
will frequently refer to 'encountering an option' on the command line;
in reality, *note optparse: 90. encounters 'option strings' and looks up
options from them.

Once all of your options are defined, instruct *note optparse: 90. to
parse your program's command line:

     (options, args) = parser.parse_args()

(If you like, you can pass a custom argument list to *note parse_args():
143d, but that's rarely necessary: by default it uses ‘sys.argv[1:]’.)

*note parse_args(): 143d. 回傳兩個值：

   * ‘options’, an object containing values for all of your
     options--e.g.  if ‘--file’ takes a single string argument, then
     ‘options.file’ will be the filename supplied by the user, or ‘None’
     if the user did not supply that option

   * ‘args’, the list of positional arguments leftover after parsing
     options

This tutorial section only covers the four most important option
attributes: *note action: 465c, *note type: 465d, *note dest: 465e.
(destination), and *note help: 465f.  Of these, *note action: 465c. is
the most fundamental.

* Menu:

* Understanding option actions::
* The store action::
* Handling boolean (flag) options: Handling boolean flag options.
* Other actions::
* Default values::
* Generating help::
* Printing a version string::
* How optparse handles errors::
* Putting it all together::


File: python.info,  Node: Understanding option actions,  Next: The store action,  Up: 教學<4>

5.36.2.6 Understanding option actions
.....................................

Actions tell *note optparse: 90. what to do when it encounters an option
on the command line.  There is a fixed set of actions hard-coded into
*note optparse: 90.; adding new actions is an advanced topic covered in
section *note Extending optparse: 4662.  Most actions tell *note
optparse: 90. to store a value in some variable--for example, take a
string from the command line and store it in an attribute of ‘options’.

If you don't specify an option action, *note optparse: 90. defaults to
‘store’.


File: python.info,  Node: The store action,  Next: Handling boolean flag options,  Prev: Understanding option actions,  Up: 教學<4>

5.36.2.7 The store action
.........................

The most common option action is ‘store’, which tells *note optparse:
90. to take the next argument (or the remainder of the current
argument), ensure that it is of the correct type, and store it to your
chosen destination.

舉例來說：

     parser.add_option("-f", "--file",
                       action="store", type="string", dest="filename")

Now let's make up a fake command line and ask *note optparse: 90. to
parse it:

     args = ["-f", "foo.txt"]
     (options, args) = parser.parse_args(args)

When *note optparse: 90. sees the option string ‘-f’, it consumes the
next argument, ‘foo.txt’, and stores it in ‘options.filename’.  So,
after this call to *note parse_args(): 143d, ‘options.filename’ is
‘"foo.txt"’.

Some other option types supported by *note optparse: 90. are ‘int’ and
‘float’.  Here's an option that expects an integer argument:

     parser.add_option("-n", type="int", dest="num")

Note that this option has no long option string, which is perfectly
acceptable.  Also, there's no explicit action, since the default is
‘store’.

Let's parse another fake command-line.  This time, we'll jam the option
argument right up against the option: since ‘-n42’ (one argument) is
equivalent to ‘-n 42’ (two arguments), the code

     (options, args) = parser.parse_args(["-n42"])
     print(options.num)

will print ‘42’.

If you don't specify a type, *note optparse: 90. assumes ‘string’.
Combined with the fact that the default action is ‘store’, that means
our first example can be a lot shorter:

     parser.add_option("-f", "--file", dest="filename")

If you don't supply a destination, *note optparse: 90. figures out a
sensible default from the option strings: if the first long option
string is ‘--foo-bar’, then the default destination is ‘foo_bar’.  If
there are no long option strings, *note optparse: 90. looks at the first
short option string: the default destination for ‘-f’ is ‘f’.

*note optparse: 90. also includes the built-in ‘complex’ type.  Adding
types is covered in section *note Extending optparse: 4662.


File: python.info,  Node: Handling boolean flag options,  Next: Other actions,  Prev: The store action,  Up: 教學<4>

5.36.2.8 Handling boolean (flag) options
........................................

Flag options--set a variable to true or false when a particular option
is seen--are quite common.  *note optparse: 90. supports them with two
separate actions, ‘store_true’ and ‘store_false’.  For example, you
might have a ‘verbose’ flag that is turned on with ‘-v’ and off with
‘-q’:

     parser.add_option("-v", action="store_true", dest="verbose")
     parser.add_option("-q", action="store_false", dest="verbose")

Here we have two different options with the same destination, which is
perfectly OK. (It just means you have to be a bit careful when setting
default values--see below.)

When *note optparse: 90. encounters ‘-v’ on the command line, it sets
‘options.verbose’ to ‘True’; when it encounters ‘-q’, ‘options.verbose’
is set to ‘False’.


File: python.info,  Node: Other actions,  Next: Default values,  Prev: Handling boolean flag options,  Up: 教學<4>

5.36.2.9 Other actions
......................

Some other actions supported by *note optparse: 90. are:

‘"store_const"’

     store a constant value, pre-set via *note Option.const: 4669.

‘"append"’

     append this option's argument to a list

‘"count"’

     increment a counter by one

‘"callback"’

     call a specified function

These are covered in section *note Reference Guide: 466a, and section
*note Option Callbacks: 466b.


File: python.info,  Node: Default values,  Next: Generating help,  Prev: Other actions,  Up: 教學<4>

5.36.2.10 Default values
........................

All of the above examples involve setting some variable (the
"destination") when certain command-line options are seen.  What happens
if those options are never seen?  Since we didn't supply any defaults,
they are all set to ‘None’.  This is usually fine, but sometimes you
want more control.  *note optparse: 90. lets you supply a default value
for each destination, which is assigned before the command line is
parsed.

First, consider the verbose/quiet example.  If we want *note optparse:
90. to set ‘verbose’ to ‘True’ unless ‘-q’ is seen, then we can do this:

     parser.add_option("-v", action="store_true", dest="verbose", default=True)
     parser.add_option("-q", action="store_false", dest="verbose")

Since default values apply to the 'destination' rather than to any
particular option, and these two options happen to have the same
destination, this is exactly equivalent:

     parser.add_option("-v", action="store_true", dest="verbose")
     parser.add_option("-q", action="store_false", dest="verbose", default=True)

Consider this:

     parser.add_option("-v", action="store_true", dest="verbose", default=False)
     parser.add_option("-q", action="store_false", dest="verbose", default=True)

Again, the default value for ‘verbose’ will be ‘True’: the last default
value supplied for any particular destination is the one that counts.

A clearer way to specify default values is the ‘set_defaults()’ method
of OptionParser, which you can call at any time before calling *note
parse_args(): 143d.:

     parser.set_defaults(verbose=True)
     parser.add_option(...)
     (options, args) = parser.parse_args()

As before, the last value specified for a given option destination is
the one that counts.  For clarity, try to use one method or the other of
setting default values, not both.


File: python.info,  Node: Generating help,  Next: Printing a version string,  Prev: Default values,  Up: 教學<4>

5.36.2.11 Generating help
.........................

*note optparse: 90.'s ability to generate help and usage text
automatically is useful for creating user-friendly command-line
interfaces.  All you have to do is supply a *note help: 465f. value for
each option, and optionally a short usage message for your whole
program.  Here's an OptionParser populated with user-friendly
(documented) options:

     usage = "usage: %prog [options] arg1 arg2"
     parser = OptionParser(usage=usage)
     parser.add_option("-v", "--verbose",
                       action="store_true", dest="verbose", default=True,
                       help="make lots of noise [default]")
     parser.add_option("-q", "--quiet",
                       action="store_false", dest="verbose",
                       help="be vewwy quiet (I'm hunting wabbits)")
     parser.add_option("-f", "--filename",
                       metavar="FILE", help="write output to FILE")
     parser.add_option("-m", "--mode",
                       default="intermediate",
                       help="interaction mode: novice, intermediate, "
                            "or expert [default: %default]")

If *note optparse: 90. encounters either ‘-h’ or ‘--help’ on the
command-line, or if you just call ‘parser.print_help()’, it prints the
following to standard output:

     Usage: <yourscript> [options] arg1 arg2

     Options:
       -h, --help            show this help message and exit
       -v, --verbose         make lots of noise [default]
       -q, --quiet           be vewwy quiet (I'm hunting wabbits)
       -f FILE, --filename=FILE
                             write output to FILE
       -m MODE, --mode=MODE  interaction mode: novice, intermediate, or
                             expert [default: intermediate]

(If the help output is triggered by a help option, *note optparse: 90.
exits after printing the help text.)

There's a lot going on here to help *note optparse: 90. generate the
best possible help message:

   * the script defines its own usage message:

          usage = "usage: %prog [options] arg1 arg2"

     *note optparse: 90. expands ‘%prog’ in the usage string to the name
     of the current program, i.e.  ‘os.path.basename(sys.argv[0])’.  The
     expanded string is then printed before the detailed option help.

     If you don't supply a usage string, *note optparse: 90. uses a
     bland but sensible default: ‘"Usage: %prog [options]"’, which is
     fine if your script doesn't take any positional arguments.

   * every option defines a help string, and doesn't worry about
     line-wrapping--*note optparse: 90. takes care of wrapping lines and
     making the help output look good.

   * options that take a value indicate this fact in their automatically
     generated help message, e.g.  for the "mode" option:

          -m MODE, --mode=MODE

     Here, "MODE" is called the meta-variable: it stands for the
     argument that the user is expected to supply to ‘-m’/‘--mode’.  By
     default, *note optparse: 90. converts the destination variable name
     to uppercase and uses that for the meta-variable.  Sometimes,
     that's not what you want--for example, the ‘--filename’ option
     explicitly sets ‘metavar="FILE"’, resulting in this automatically
     generated option description:

          -f FILE, --filename=FILE

     This is important for more than just saving space, though: the
     manually written help text uses the meta-variable ‘FILE’ to clue
     the user in that there's a connection between the semi-formal
     syntax ‘-f FILE’ and the informal semantic description "write
     output to FILE". This is a simple but effective way to make your
     help text a lot clearer and more useful for end users.

   * options that have a default value can include ‘%default’ in the
     help string--*note optparse: 90. will replace it with *note str():
     3f2. of the option's default value.  If an option has no default
     value (or the default value is ‘None’), ‘%default’ expands to
     ‘none’.

* Menu:

* Grouping Options::


File: python.info,  Node: Grouping Options,  Up: Generating help

5.36.2.12 Grouping Options
..........................

When dealing with many options, it is convenient to group these options
for better help output.  An *note OptionParser: 143c. can contain
several option groups, each of which can contain several options.

An option group is obtained using the class *note OptionGroup: 4671.:

 -- 類別: optparse.OptionGroup (parser, title, description=None)

     where

        * parser is the *note OptionParser: 143c. instance the group
          will be inserted in to

        * title is the group title

        * description, optional, is a long description of the group

*note OptionGroup: 4671. inherits from ‘OptionContainer’ (like *note
OptionParser: 143c.) and so the ‘add_option()’ method can be used to add
an option to the group.

Once all the options are declared, using the *note OptionParser: 143c.
method ‘add_option_group()’ the group is added to the previously defined
parser.

Continuing with the parser defined in the previous section, adding an
*note OptionGroup: 4671. to a parser is easy:

     group = OptionGroup(parser, "Dangerous Options",
                         "Caution: use these options at your own risk.  "
                         "It is believed that some of them bite.")
     group.add_option("-g", action="store_true", help="Group option.")
     parser.add_option_group(group)

This would result in the following help output:

     Usage: <yourscript> [options] arg1 arg2

     Options:
       -h, --help            show this help message and exit
       -v, --verbose         make lots of noise [default]
       -q, --quiet           be vewwy quiet (I'm hunting wabbits)
       -f FILE, --filename=FILE
                             write output to FILE
       -m MODE, --mode=MODE  interaction mode: novice, intermediate, or
                             expert [default: intermediate]

       Dangerous Options:
         Caution: use these options at your own risk.  It is believed that some
         of them bite.

         -g                  Group option.

A bit more complete example might involve using more than one group:
still extending the previous example:

     group = OptionGroup(parser, "Dangerous Options",
                         "Caution: use these options at your own risk.  "
                         "It is believed that some of them bite.")
     group.add_option("-g", action="store_true", help="Group option.")
     parser.add_option_group(group)

     group = OptionGroup(parser, "Debug Options")
     group.add_option("-d", "--debug", action="store_true",
                      help="Print debug information")
     group.add_option("-s", "--sql", action="store_true",
                      help="Print all SQL statements executed")
     group.add_option("-e", action="store_true", help="Print every action done")
     parser.add_option_group(group)

that results in the following output:

     Usage: <yourscript> [options] arg1 arg2

     Options:
       -h, --help            show this help message and exit
       -v, --verbose         make lots of noise [default]
       -q, --quiet           be vewwy quiet (I'm hunting wabbits)
       -f FILE, --filename=FILE
                             write output to FILE
       -m MODE, --mode=MODE  interaction mode: novice, intermediate, or expert
                             [default: intermediate]

       Dangerous Options:
         Caution: use these options at your own risk.  It is believed that some
         of them bite.

         -g                  Group option.

       Debug Options:
         -d, --debug         Print debug information
         -s, --sql           Print all SQL statements executed
         -e                  Print every action done

Another interesting method, in particular when working programmatically
with option groups is:

 -- 方法: OptionParser.get_option_group (opt_str)

     Return the *note OptionGroup: 4671. to which the short or long
     option string 'opt_str' (e.g.  ‘'-o'’ or ‘'--option'’) belongs.  If
     there's no such *note OptionGroup: 4671, return ‘None’.


File: python.info,  Node: Printing a version string,  Next: How optparse handles errors,  Prev: Generating help,  Up: 教學<4>

5.36.2.13 Printing a version string
...................................

Similar to the brief usage string, *note optparse: 90. can also print a
version string for your program.  You have to supply the string as the
‘version’ argument to OptionParser:

     parser = OptionParser(usage="%prog [-f] [-q]", version="%prog 1.0")

‘%prog’ is expanded just like it is in ‘usage’.  Apart from that,
‘version’ can contain anything you like.  When you supply it, *note
optparse: 90. automatically adds a ‘--version’ option to your parser.
If it encounters this option on the command line, it expands your
‘version’ string (by replacing ‘%prog’), prints it to stdout, and exits.

For example, if your script is called ‘/usr/bin/foo’:

     $ /usr/bin/foo --version
     foo 1.0

The following two methods can be used to print and get the ‘version’
string:

 -- 方法: OptionParser.print_version (file=None)

     Print the version message for the current program (‘self.version’)
     to 'file' (default stdout).  As with *note print_usage(): 4676, any
     occurrence of ‘%prog’ in ‘self.version’ is replaced with the name
     of the current program.  Does nothing if ‘self.version’ is empty or
     undefined.

 -- 方法: OptionParser.get_version ()

     Same as *note print_version(): 4675. but returns the version string
     instead of printing it.


File: python.info,  Node: How optparse handles errors,  Next: Putting it all together,  Prev: Printing a version string,  Up: 教學<4>

5.36.2.14 How ‘optparse’ handles errors
.......................................

There are two broad classes of errors that *note optparse: 90. has to
worry about: programmer errors and user errors.  Programmer errors are
usually erroneous calls to *note OptionParser.add_option(): 2b9e, e.g.
invalid option strings, unknown option attributes, missing option
attributes, etc.  These are dealt with in the usual way: raise an
exception (either *note optparse.OptionError: 2ba1. or *note TypeError:
4dd.) and let the program crash.

Handling user errors is much more important, since they are guaranteed
to happen no matter how stable your code is.  *note optparse: 90. can
automatically detect some user errors, such as bad option arguments
(passing ‘-n 4x’ where ‘-n’ takes an integer argument), missing
arguments (‘-n’ at the end of the command line, where ‘-n’ takes an
argument of any type).  Also, you can call ‘OptionParser.error()’ to
signal an application-defined error condition:

     (options, args) = parser.parse_args()
     ...
     if options.a and options.b:
         parser.error("options -a and -b are mutually exclusive")

In either case, *note optparse: 90. handles the error the same way: it
prints the program's usage message and an error message to standard
error and exits with error status 2.

Consider the first example above, where the user passes ‘4x’ to an
option that takes an integer:

     $ /usr/bin/foo -n 4x
     Usage: foo [options]

     foo: error: option -n: invalid integer value: '4x'

Or, where the user fails to pass a value at all:

     $ /usr/bin/foo -n
     Usage: foo [options]

     foo: error: -n option requires an argument

*note optparse: 90.-generated error messages take care always to mention
the option involved in the error; be sure to do the same when calling
‘OptionParser.error()’ from your application code.

If *note optparse: 90.'s default error-handling behaviour does not suit
your needs, you'll need to subclass OptionParser and override its
‘exit()’ and/or ‘error()’ methods.


File: python.info,  Node: Putting it all together,  Prev: How optparse handles errors,  Up: 教學<4>

5.36.2.15 Putting it all together
.................................

Here's what *note optparse: 90.-based scripts usually look like:

     from optparse import OptionParser
     ...
     def main():
         usage = "usage: %prog [options] arg"
         parser = OptionParser(usage)
         parser.add_option("-f", "--file", dest="filename",
                           help="read data from FILENAME")
         parser.add_option("-v", "--verbose",
                           action="store_true", dest="verbose")
         parser.add_option("-q", "--quiet",
                           action="store_false", dest="verbose")
         ...
         (options, args) = parser.parse_args()
         if len(args) != 1:
             parser.error("incorrect number of arguments")
         if options.verbose:
             print("reading %s..." % options.filename)
         ...

     if __name__ == "__main__":
         main()


File: python.info,  Node: Reference Guide,  Next: Option Callbacks,  Prev: 教學<4>,  Up: optparse --- 命令列選項剖析器

5.36.2.16 Reference Guide
.........................

* Menu:

* Creating the parser::
* Populating the parser::
* Defining options::
* Option attributes::
* Standard option actions::
* Standard option types::
* 剖析引數: 剖析引數<2>.
* Querying and manipulating your option parser::
* Conflicts between options::
* Cleanup: Cleanup<2>.
* 其他方法::


File: python.info,  Node: Creating the parser,  Next: Populating the parser,  Up: Reference Guide

5.36.2.17 Creating the parser
.............................

The first step in using *note optparse: 90. is to create an OptionParser
instance.

 -- 類別: optparse.OptionParser (...)

     The OptionParser constructor has no required arguments, but a
     number of optional keyword arguments.  You should always pass them
     as keyword arguments, i.e.  do not rely on the order in which the
     arguments are declared.

     ‘usage’ (default: ‘"%prog [options]"’)

          The usage summary to print when your program is run
          incorrectly or with a help option.  When *note optparse: 90.
          prints the usage string, it expands ‘%prog’ to
          ‘os.path.basename(sys.argv[0])’ (or to ‘prog’ if you passed
          that keyword argument).  To suppress a usage message, pass the
          special value ‘optparse.SUPPRESS_USAGE’.

     ‘option_list’ (default: ‘[]’)

          A list of Option objects to populate the parser with.  The
          options in ‘option_list’ are added after any options in
          ‘standard_option_list’ (a class attribute that may be set by
          OptionParser subclasses), but before any version or help
          options.  Deprecated; use *note add_option(): 2b9e. after
          creating the parser instead.

     ‘option_class’ (default: optparse.Option)

          Class to use when adding options to the parser in *note
          add_option(): 2b9e.

     ‘version’ (default: ‘None’)

          A version string to print when the user supplies a version
          option.  If you supply a true value for ‘version’, *note
          optparse: 90. automatically adds a version option with the
          single option string ‘--version’.  The substring ‘%prog’ is
          expanded the same as for ‘usage’.

     ‘conflict_handler’ (default: ‘"error"’)

          Specifies what to do when options with conflicting option
          strings are added to the parser; see section *note Conflicts
          between options: 467f.

     ‘description’ (default: ‘None’)

          A paragraph of text giving a brief overview of your program.
          *note optparse: 90. reformats this paragraph to fit the
          current terminal width and prints it when the user requests
          help (after ‘usage’, but before the list of options).

     ‘formatter’ (default: a new ‘IndentedHelpFormatter’)

          An instance of optparse.HelpFormatter that will be used for
          printing help text.  *note optparse: 90. provides two concrete
          classes for this purpose: IndentedHelpFormatter and
          TitledHelpFormatter.

     ‘add_help_option’ (default: ‘True’)

          If true, *note optparse: 90. will add a help option (with
          option strings ‘-h’ and ‘--help’) to the parser.

     ‘prog’

          The string to use when expanding ‘%prog’ in ‘usage’ and
          ‘version’ instead of ‘os.path.basename(sys.argv[0])’.

     ‘epilog’ (default: ‘None’)

          A paragraph of help text to print after the option help.


File: python.info,  Node: Populating the parser,  Next: Defining options,  Prev: Creating the parser,  Up: Reference Guide

5.36.2.18 Populating the parser
...............................

There are several ways to populate the parser with options.  The
preferred way is by using *note OptionParser.add_option(): 2b9e, as
shown in section *note 教學: 465a.  ‘add_option()’ can be called in one
of two ways:

   * pass it an Option instance (as returned by ‘make_option()’)

   * pass it any combination of positional and keyword arguments that
     are acceptable to ‘make_option()’ (i.e., to the Option
     constructor), and it will create the Option instance for you

The other alternative is to pass a list of pre-constructed Option
instances to the OptionParser constructor, as in:

     option_list = [
         make_option("-f", "--filename",
                     action="store", type="string", dest="filename"),
         make_option("-q", "--quiet",
                     action="store_false", dest="verbose"),
         ]
     parser = OptionParser(option_list=option_list)

(‘make_option()’ is a factory function for creating Option instances;
currently it is an alias for the Option constructor.  A future version
of *note optparse: 90. may split Option into several classes, and
‘make_option()’ will pick the right class to instantiate.  Do not
instantiate Option directly.)


File: python.info,  Node: Defining options,  Next: Option attributes,  Prev: Populating the parser,  Up: Reference Guide

5.36.2.19 Defining options
..........................

Each Option instance represents a set of synonymous command-line option
strings, e.g.  ‘-f’ and ‘--file’.  You can specify any number of short
or long option strings, but you must specify at least one overall option
string.

The canonical way to create an *note Option: 4684. instance is with the
‘add_option()’ method of *note OptionParser: 143c.

 -- 方法: OptionParser.add_option (option)

 -- 方法: OptionParser.add_option (*opt_str, attr=value, ...)

     To define an option with only a short option string:

          parser.add_option("-f", attr=value, ...)

     And to define an option with only a long option string:

          parser.add_option("--foo", attr=value, ...)

     The keyword arguments define attributes of the new Option object.
     The most important option attribute is *note action: 465c, and it
     largely determines which other attributes are relevant or required.
     If you pass irrelevant option attributes, or fail to pass required
     ones, *note optparse: 90. raises an *note OptionError: 2ba1.
     exception explaining your mistake.

     An option's 'action' determines what *note optparse: 90. does when
     it encounters this option on the command-line.  The standard option
     actions hard-coded into *note optparse: 90. are:

     ‘"store"’

          store this option's argument (default)

     ‘"store_const"’

          store a constant value, pre-set via *note Option.const: 4669.

     ‘"store_true"’

          store ‘True’

     ‘"store_false"’

          store ‘False’

     ‘"append"’

          append this option's argument to a list

     ‘"append_const"’

          append a constant value to a list, pre-set via *note
          Option.const: 4669.

     ‘"count"’

          increment a counter by one

     ‘"callback"’

          call a specified function

     ‘"help"’

          print a usage message including all options and the
          documentation for them

     (If you don't supply an action, the default is ‘"store"’.  For this
     action, you may also supply *note type: 465d. and *note dest: 465e.
     option attributes; see *note Standard option actions: 4685.)

As you can see, most actions involve storing or updating a value
somewhere.  *note optparse: 90. always creates a special object for
this, conventionally called ‘options’, which is an instance of *note
optparse.Values: 2ba0.

 -- 類別: optparse.Values

     An object holding parsed argument names and values as attributes.
     Normally created by calling when calling *note
     OptionParser.parse_args(): 143d, and can be overridden by a custom
     subclass passed to the 'values' argument of *note
     OptionParser.parse_args(): 143d. (as described in *note 剖析引數:
     4686.).

Option arguments (and various other values) are stored as attributes of
this object, according to the *note dest: 465e. (destination) option
attribute.

例如說，當你呼叫：

     parser.parse_args()

one of the first things *note optparse: 90. does is create the ‘options’
object:

     options = Values()

If one of the options in this parser is defined with

     parser.add_option("-f", "--file", action="store", type="string", dest="filename")

and the command-line being parsed includes any of the following:

     -ffoo
     -f foo
     --file=foo
     --file foo

then *note optparse: 90, on seeing this option, will do the equivalent
of

     options.filename = "foo"

The *note type: 465d. and *note dest: 465e. option attributes are almost
as important as *note action: 465c, but *note action: 465c. is the only
one that makes sense for 'all' options.


File: python.info,  Node: Option attributes,  Next: Standard option actions,  Prev: Defining options,  Up: Reference Guide

5.36.2.20 Option attributes
...........................

 -- 類別: optparse.Option

     A single command line argument, with various attributes passed by
     keyword to the constructor.  Normally created with *note
     OptionParser.add_option(): 2b9e. rather than directly, and can be
     overridden by a custom class via the 'option_class' argument to
     *note OptionParser: 143c.

The following option attributes may be passed as keyword arguments to
*note OptionParser.add_option(): 2b9e.  If you pass an option attribute
that is not relevant to a particular option, or fail to pass a required
option attribute, *note optparse: 90. raises *note OptionError: 2ba1.

 -- 屬性: Option.action

     （預設值： ‘"store"’ ）

     Determines *note optparse: 90.'s behaviour when this option is seen
     on the command line; the available options are documented *note
     here: 4685.

 -- 屬性: Option.type

     （預設值： ‘"string"’ ）

     The argument type expected by this option (e.g., ‘"string"’ or
     ‘"int"’); the available option types are documented *note here:
     4689.

 -- 屬性: Option.dest

     (default: derived from option strings)

     If the option's action implies writing or modifying a value
     somewhere, this tells *note optparse: 90. where to write it: *note
     dest: 465e. names an attribute of the ‘options’ object that *note
     optparse: 90. builds as it parses the command line.

 -- 屬性: Option.default

     The value to use for this option's destination if the option is not
     seen on the command line.  See also *note
     OptionParser.set_defaults(): 468b.

 -- 屬性: Option.nargs

     （預設值：1）

     How many arguments of type *note type: 465d. should be consumed
     when this option is seen.  If > 1, *note optparse: 90. will store a
     tuple of values to *note dest: 465e.

 -- 屬性: Option.const

     For actions that store a constant value, the constant value to
     store.

 -- 屬性: Option.choices

     For options of type ‘"choice"’, the list of strings the user may
     choose from.

 -- 屬性: Option.callback

     For options with action ‘"callback"’, the callable to call when
     this option is seen.  See section *note Option Callbacks: 466b. for
     detail on the arguments passed to the callable.

 -- 屬性: Option.callback_args
 -- 屬性: Option.callback_kwargs

     Additional positional and keyword arguments to pass to ‘callback’
     after the four standard callback arguments.

 -- 屬性: Option.help

     Help text to print for this option when listing all available
     options after the user supplies a *note help: 465f. option (such as
     ‘--help’).  If no help text is supplied, the option will be listed
     without help text.  To hide this option, use the special value
     ‘optparse.SUPPRESS_HELP’.

 -- 屬性: Option.metavar

     (default: derived from option strings)

     Stand-in for the option argument(s) to use when printing help text.
     See section *note 教學: 465a. for an example.


File: python.info,  Node: Standard option actions,  Next: Standard option types,  Prev: Option attributes,  Up: Reference Guide

5.36.2.21 Standard option actions
.................................

The various option actions all have slightly different requirements and
effects.  Most actions have several relevant option attributes which you
may specify to guide *note optparse: 90.'s behaviour; a few have
required attributes, which you must specify for any option using that
action.

   * ‘"store"’ [relevant: *note type: 465d, *note dest: 465e, *note
     nargs: 468c, *note choices: 468d.]

     The option must be followed by an argument, which is converted to a
     value according to *note type: 465d. and stored in *note dest:
     465e.  If *note nargs: 468c. > 1, multiple arguments will be
     consumed from the command line; all will be converted according to
     *note type: 465d. and stored to *note dest: 465e. as a tuple.  See
     the *note Standard option types: 4689. section.

     If *note choices: 468d. is supplied (a list or tuple of strings),
     the type defaults to ‘"choice"’.

     If *note type: 465d. is not supplied, it defaults to ‘"string"’.

     If *note dest: 465e. is not supplied, *note optparse: 90. derives a
     destination from the first long option string (e.g., ‘--foo-bar’
     implies ‘foo_bar’).  If there are no long option strings, *note
     optparse: 90. derives a destination from the first short option
     string (e.g., ‘-f’ implies ‘f’).

     範例：

          parser.add_option("-f")
          parser.add_option("-p", type="float", nargs=3, dest="point")

     As it parses the command line

          -f foo.txt -p 1 -3.5 4 -fbar.txt

     *note optparse: 90. will set

          options.f = "foo.txt"
          options.point = (1.0, -3.5, 4.0)
          options.f = "bar.txt"

   * ‘"store_const"’ [required: *note const: 4669.; relevant: *note
     dest: 465e.]

     The value *note const: 4669. is stored in *note dest: 465e.

     範例：

          parser.add_option("-q", "--quiet",
                            action="store_const", const=0, dest="verbose")
          parser.add_option("-v", "--verbose",
                            action="store_const", const=1, dest="verbose")
          parser.add_option("--noisy",
                            action="store_const", const=2, dest="verbose")

     If ‘--noisy’ is seen, *note optparse: 90. will set

          options.verbose = 2

   * ‘"store_true"’ [relevant: *note dest: 465e.]

     A special case of ‘"store_const"’ that stores ‘True’ to *note dest:
     465e.

   * ‘"store_false"’ [relevant: *note dest: 465e.]

     Like ‘"store_true"’, but stores ‘False’.

     範例：

          parser.add_option("--clobber", action="store_true", dest="clobber")
          parser.add_option("--no-clobber", action="store_false", dest="clobber")

   * ‘"append"’ [relevant: *note type: 465d, *note dest: 465e, *note
     nargs: 468c, *note choices: 468d.]

     The option must be followed by an argument, which is appended to
     the list in *note dest: 465e.  If no default value for *note dest:
     465e. is supplied, an empty list is automatically created when
     *note optparse: 90. first encounters this option on the
     command-line.  If *note nargs: 468c. > 1, multiple arguments are
     consumed, and a tuple of length *note nargs: 468c. is appended to
     *note dest: 465e.

     The defaults for *note type: 465d. and *note dest: 465e. are the
     same as for the ‘"store"’ action.

     範例：

          parser.add_option("-t", "--tracks", action="append", type="int")

     If ‘-t3’ is seen on the command-line, *note optparse: 90. does the
     equivalent of:

          options.tracks = []
          options.tracks.append(int("3"))

     If, a little later on, ‘--tracks=4’ is seen, it does:

          options.tracks.append(int("4"))

     The ‘append’ action calls the ‘append’ method on the current value
     of the option.  This means that any default value specified must
     have an ‘append’ method.  It also means that if the default value
     is non-empty, the default elements will be present in the parsed
     value for the option, with any values from the command line
     appended after those default values:

          >>> parser.add_option("--files", action="append", default=['~/.mypkg/defaults'])
          >>> opts, args = parser.parse_args(['--files', 'overrides.mypkg'])
          >>> opts.files
          ['~/.mypkg/defaults', 'overrides.mypkg']

   * ‘"append_const"’ [required: *note const: 4669.; relevant: *note
     dest: 465e.]

     Like ‘"store_const"’, but the value *note const: 4669. is appended
     to *note dest: 465e.; as with ‘"append"’, *note dest: 465e.
     defaults to ‘None’, and an empty list is automatically created the
     first time the option is encountered.

   * ‘"count"’ [relevant: *note dest: 465e.]

     Increment the integer stored at *note dest: 465e.  If no default
     value is supplied, *note dest: 465e. is set to zero before being
     incremented the first time.

     範例：

          parser.add_option("-v", action="count", dest="verbosity")

     The first time ‘-v’ is seen on the command line, *note optparse:
     90. does the equivalent of:

          options.verbosity = 0
          options.verbosity += 1

     Every subsequent occurrence of ‘-v’ results in

          options.verbosity += 1

   * ‘"callback"’ [required: *note callback: 468e.; relevant: *note
     type: 465d, *note nargs: 468c, *note callback_args: 468f, *note
     callback_kwargs: 4690.]

     Call the function specified by *note callback: 468e, which is
     called as

          func(option, opt_str, value, parser, *args, **kwargs)

     更多細節請見 *note Option Callbacks: 466b.。

   * ‘"help"’

     Prints a complete help message for all the options in the current
     option parser.  The help message is constructed from the ‘usage’
     string passed to OptionParser's constructor and the *note help:
     465f. string passed to every option.

     If no *note help: 465f. string is supplied for an option, it will
     still be listed in the help message.  To omit an option entirely,
     use the special value ‘optparse.SUPPRESS_HELP’.

     *note optparse: 90. automatically adds a *note help: 465f. option
     to all OptionParsers, so you do not normally need to create one.

     範例：

          from optparse import OptionParser, SUPPRESS_HELP

          # usually, a help option is added automatically, but that can
          # be suppressed using the add_help_option argument
          parser = OptionParser(add_help_option=False)

          parser.add_option("-h", "--help", action="help")
          parser.add_option("-v", action="store_true", dest="verbose",
                            help="Be moderately verbose")
          parser.add_option("--file", dest="filename",
                            help="Input file to read data from")
          parser.add_option("--secret", help=SUPPRESS_HELP)

     If *note optparse: 90. sees either ‘-h’ or ‘--help’ on the command
     line, it will print something like the following help message to
     stdout (assuming ‘sys.argv[0]’ is ‘"foo.py"’):

          Usage: foo.py [options]

          Options:
            -h, --help        Show this help message and exit
            -v                Be moderately verbose
            --file=FILENAME   Input file to read data from

     After printing the help message, *note optparse: 90. terminates
     your process with ‘sys.exit(0)’.

   * ‘"version"’

     Prints the version number supplied to the OptionParser to stdout
     and exits.  The version number is actually formatted and printed by
     the ‘print_version()’ method of OptionParser.  Generally only
     relevant if the ‘version’ argument is supplied to the OptionParser
     constructor.  As with *note help: 465f. options, you will rarely
     create ‘version’ options, since *note optparse: 90. automatically
     adds them when needed.


File: python.info,  Node: Standard option types,  Next: 剖析引數<2>,  Prev: Standard option actions,  Up: Reference Guide

5.36.2.22 Standard option types
...............................

*note optparse: 90. has five built-in option types: ‘"string"’, ‘"int"’,
‘"choice"’, ‘"float"’ and ‘"complex"’.  If you need to add new option
types, see section *note Extending optparse: 4662.

Arguments to string options are not checked or converted in any way: the
text on the command line is stored in the destination (or passed to the
callback) as-is.

Integer arguments (type ‘"int"’) are parsed as follows:

   * if the number starts with ‘0x’, it is parsed as a hexadecimal
     number

   * if the number starts with ‘0’, it is parsed as an octal number

   * if the number starts with ‘0b’, it is parsed as a binary number

   * otherwise, the number is parsed as a decimal number

The conversion is done by calling *note int(): 23c. with the appropriate
base (2, 8, 10, or 16).  If this fails, so will *note optparse: 90,
although with a more useful error message.

‘"float"’ and ‘"complex"’ option arguments are converted directly with
*note float(): 2c8. and *note complex(): 2c9, with similar
error-handling.

‘"choice"’ options are a subtype of ‘"string"’ options.  The *note
choices: 468d. option attribute (a sequence of strings) defines the set
of allowed option arguments.  ‘optparse.check_choice()’ compares
user-supplied option arguments against this master list and raises *note
OptionValueError: 2ba2. if an invalid string is given.


File: python.info,  Node: 剖析引數<2>,  Next: Querying and manipulating your option parser,  Prev: Standard option types,  Up: Reference Guide

5.36.2.23 剖析引數
..................

The whole point of creating and populating an OptionParser is to call
its *note parse_args(): 143d. method.

 -- 方法: OptionParser.parse_args (args=None, values=None)

     Parse the command-line options found in 'args'.

     The input parameters are

     ‘args’

          the list of arguments to process (default: ‘sys.argv[1:]’)

     ‘values’

          a *note Values: 2ba0. object to store option arguments in
          (default: a new instance of *note Values: 2ba0.) - if you give
          an existing object, the option defaults will not be
          initialized on it

     and the return value is a pair ‘(options, args)’ where

     ‘options’

          the same object that was passed in as 'values', or the
          ‘optparse.Values’ instance created by *note optparse: 90.

     ‘args’

          the leftover positional arguments after all options have been
          processed

The most common usage is to supply neither keyword argument.  If you
supply ‘values’, it will be modified with repeated *note setattr():
2032. calls (roughly one for every option argument stored to an option
destination) and returned by *note parse_args(): 143d.

If *note parse_args(): 143d. encounters any errors in the argument list,
it calls the OptionParser's ‘error()’ method with an appropriate
end-user error message.  This ultimately terminates your process with an
exit status of 2 (the traditional Unix exit status for command-line
errors).


File: python.info,  Node: Querying and manipulating your option parser,  Next: Conflicts between options,  Prev: 剖析引數<2>,  Up: Reference Guide

5.36.2.24 Querying and manipulating your option parser
......................................................

The default behavior of the option parser can be customized slightly,
and you can also poke around your option parser and see what's there.
OptionParser provides several methods to help you out:

 -- 方法: OptionParser.disable_interspersed_args ()

     Set parsing to stop on the first non-option.  For example, if ‘-a’
     and ‘-b’ are both simple options that take no arguments, *note
     optparse: 90. normally accepts this syntax:

          prog -a arg1 -b arg2

     and treats it as equivalent to

          prog -a -b arg1 arg2

     To disable this feature, call *note disable_interspersed_args():
     2b9f.  This restores traditional Unix syntax, where option parsing
     stops with the first non-option argument.

     Use this if you have a command processor which runs another command
     which has options of its own and you want to make sure these
     options don't get confused.  For example, each command might have a
     different set of options.

 -- 方法: OptionParser.enable_interspersed_args ()

     Set parsing to not stop on the first non-option, allowing
     interspersing switches with command arguments.  This is the default
     behavior.

 -- 方法: OptionParser.get_option (opt_str)

     Returns the Option instance with the option string 'opt_str', or
     ‘None’ if no options have that option string.

 -- 方法: OptionParser.has_option (opt_str)

     Return ‘True’ if the OptionParser has an option with option string
     'opt_str' (e.g., ‘-q’ or ‘--verbose’).

 -- 方法: OptionParser.remove_option (opt_str)

     If the *note OptionParser: 143c. has an option corresponding to
     'opt_str', that option is removed.  If that option provided any
     other option strings, all of those option strings become invalid.
     If 'opt_str' does not occur in any option belonging to this *note
     OptionParser: 143c, raises *note ValueError: 1e7.


File: python.info,  Node: Conflicts between options,  Next: Cleanup<2>,  Prev: Querying and manipulating your option parser,  Up: Reference Guide

5.36.2.25 Conflicts between options
...................................

If you're not careful, it's easy to define options with conflicting
option strings:

     parser.add_option("-n", "--dry-run", ...)
     ...
     parser.add_option("-n", "--noisy", ...)

(This is particularly true if you've defined your own OptionParser
subclass with some standard options.)

Every time you add an option, *note optparse: 90. checks for conflicts
with existing options.  If it finds any, it invokes the current
conflict-handling mechanism.  You can set the conflict-handling
mechanism either in the constructor:

     parser = OptionParser(..., conflict_handler=handler)

or with a separate call:

     parser.set_conflict_handler(handler)

The available conflict handlers are:

     ‘"error"’ (default)

          assume option conflicts are a programming error and raise
          *note OptionConflictError: 469c.

     ‘"resolve"’

          resolve option conflicts intelligently (see below)

As an example, let's define an *note OptionParser: 143c. that resolves
conflicts intelligently and add conflicting options to it:

     parser = OptionParser(conflict_handler="resolve")
     parser.add_option("-n", "--dry-run", ..., help="do no harm")
     parser.add_option("-n", "--noisy", ..., help="be noisy")

At this point, *note optparse: 90. detects that a previously added
option is already using the ‘-n’ option string.  Since
‘conflict_handler’ is ‘"resolve"’, it resolves the situation by removing
‘-n’ from the earlier option's list of option strings.  Now ‘--dry-run’
is the only way for the user to activate that option.  If the user asks
for help, the help message will reflect that:

     Options:
       --dry-run     do no harm
       ...
       -n, --noisy   be noisy

It's possible to whittle away the option strings for a previously added
option until there are none left, and the user has no way of invoking
that option from the command-line.  In that case, *note optparse: 90.
removes that option completely, so it doesn't show up in help text or
anywhere else.  Carrying on with our existing OptionParser:

     parser.add_option("--dry-run", ..., help="new dry-run option")

At this point, the original ‘-n’/‘--dry-run’ option is no longer
accessible, so *note optparse: 90. removes it, leaving this help text:

     Options:
       ...
       -n, --noisy   be noisy
       --dry-run     new dry-run option


File: python.info,  Node: Cleanup<2>,  Next: 其他方法,  Prev: Conflicts between options,  Up: Reference Guide

5.36.2.26 Cleanup
.................

OptionParser instances have several cyclic references.  This should not
be a problem for Python's garbage collector, but you may wish to break
the cyclic references explicitly by calling ‘destroy()’ on your
OptionParser once you are done with it.  This is particularly useful in
long-running applications where large object graphs are reachable from
your OptionParser.


File: python.info,  Node: 其他方法,  Prev: Cleanup<2>,  Up: Reference Guide

5.36.2.27 其他方法
..................

OptionParser supports several other public methods:

 -- 方法: OptionParser.set_usage (usage)

     Set the usage string according to the rules described above for the
     ‘usage’ constructor keyword argument.  Passing ‘None’ sets the
     default usage string; use ‘optparse.SUPPRESS_USAGE’ to suppress a
     usage message.

 -- 方法: OptionParser.print_usage (file=None)

     Print the usage message for the current program (‘self.usage’) to
     'file' (default stdout).  Any occurrence of the string ‘%prog’ in
     ‘self.usage’ is replaced with the name of the current program.
     Does nothing if ‘self.usage’ is empty or not defined.

 -- 方法: OptionParser.get_usage ()

     Same as *note print_usage(): 4676. but returns the usage string
     instead of printing it.

 -- 方法: OptionParser.set_defaults (dest=value, ...)

     Set default values for several option destinations at once.  Using
     *note set_defaults(): 468b. is the preferred way to set default
     values for options, since multiple options can share the same
     destination.  For example, if several "mode" options all set the
     same destination, any one of them can set the default, and the last
     one wins:

          parser.add_option("--advanced", action="store_const",
                            dest="mode", const="advanced",
                            default="novice")    # overridden below
          parser.add_option("--novice", action="store_const",
                            dest="mode", const="novice",
                            default="advanced")  # overrides above setting

     To avoid this confusion, use *note set_defaults(): 468b.:

          parser.set_defaults(mode="advanced")
          parser.add_option("--advanced", action="store_const",
                            dest="mode", const="advanced")
          parser.add_option("--novice", action="store_const",
                            dest="mode", const="novice")


File: python.info,  Node: Option Callbacks,  Next: Extending optparse,  Prev: Reference Guide,  Up: optparse --- 命令列選項剖析器

5.36.2.28 Option Callbacks
..........................

When *note optparse: 90.'s built-in actions and types aren't quite
enough for your needs, you have two choices: extend *note optparse: 90.
or define a callback option.  Extending *note optparse: 90. is more
general, but overkill for a lot of simple cases.  Quite often a simple
callback is all you need.

There are two steps to defining a callback option:

   * define the option itself using the ‘"callback"’ action

   * write the callback; this is a function (or method) that takes at
     least four arguments, as described below

* Menu:

* Defining a callback option::
* How callbacks are called::
* Raising errors in a callback::
* Callback example 1; trivial callback: Callback example 1 trivial callback.
* Callback example 2; check option order: Callback example 2 check option order.
* Callback example 3; check option order (generalized): Callback example 3 check option order generalized.
* Callback example 4; check arbitrary condition: Callback example 4 check arbitrary condition.
* Callback example 5; fixed arguments: Callback example 5 fixed arguments.
* Callback example 6; variable arguments: Callback example 6 variable arguments.


File: python.info,  Node: Defining a callback option,  Next: How callbacks are called,  Up: Option Callbacks

5.36.2.29 Defining a callback option
....................................

As always, the easiest way to define a callback option is by using the
*note OptionParser.add_option(): 2b9e. method.  Apart from *note action:
465c, the only option attribute you must specify is ‘callback’, the
function to call:

     parser.add_option("-c", action="callback", callback=my_callback)

‘callback’ is a function (or other callable object), so you must have
already defined ‘my_callback()’ when you create this callback option.
In this simple case, *note optparse: 90. doesn't even know if ‘-c’ takes
any arguments, which usually means that the option takes no
arguments--the mere presence of ‘-c’ on the command-line is all it needs
to know.  In some circumstances, though, you might want your callback to
consume an arbitrary number of command-line arguments.  This is where
writing callbacks gets tricky; it's covered later in this section.

*note optparse: 90. always passes four particular arguments to your
callback, and it will only pass additional arguments if you specify them
via *note callback_args: 468f. and *note callback_kwargs: 4690.  Thus,
the minimal callback function signature is:

     def my_callback(option, opt, value, parser):

The four arguments to a callback are described below.

There are several other option attributes that you can supply when you
define a callback option:

*note type: 465d.

     has its usual meaning: as with the ‘"store"’ or ‘"append"’ actions,
     it instructs *note optparse: 90. to consume one argument and
     convert it to *note type: 465d.  Rather than storing the converted
     value(s) anywhere, though, *note optparse: 90. passes it to your
     callback function.

*note nargs: 468c.

     also has its usual meaning: if it is supplied and > 1, *note
     optparse: 90. will consume *note nargs: 468c. arguments, each of
     which must be convertible to *note type: 465d.  It then passes a
     tuple of converted values to your callback.

*note callback_args: 468f.

     a tuple of extra positional arguments to pass to the callback

*note callback_kwargs: 4690.

     a dictionary of extra keyword arguments to pass to the callback


File: python.info,  Node: How callbacks are called,  Next: Raising errors in a callback,  Prev: Defining a callback option,  Up: Option Callbacks

5.36.2.30 How callbacks are called
..................................

All callbacks are called as follows:

     func(option, opt_str, value, parser, *args, **kwargs)

where

‘option’

     is the Option instance that's calling the callback

‘opt_str’

     is the option string seen on the command-line that's triggering the
     callback.  (If an abbreviated long option was used, ‘opt_str’ will
     be the full, canonical option string--e.g.  if the user puts
     ‘--foo’ on the command-line as an abbreviation for ‘--foobar’, then
     ‘opt_str’ will be ‘"--foobar"’.)

‘value’

     is the argument to this option seen on the command-line.  *note
     optparse: 90. will only expect an argument if *note type: 465d. is
     set; the type of ‘value’ will be the type implied by the option's
     type.  If *note type: 465d. for this option is ‘None’ (no argument
     expected), then ‘value’ will be ‘None’.  If *note nargs: 468c. > 1,
     ‘value’ will be a tuple of values of the appropriate type.

‘parser’

     is the OptionParser instance driving the whole thing, mainly useful
     because you can access some other interesting data through its
     instance attributes:

     ‘parser.largs’

          the current list of leftover arguments, ie.  arguments that
          have been consumed but are neither options nor option
          arguments.  Feel free to modify ‘parser.largs’, e.g.  by
          adding more arguments to it.  (This list will become ‘args’,
          the second return value of *note parse_args(): 143d.)

     ‘parser.rargs’

          the current list of remaining arguments, ie.  with ‘opt_str’
          and ‘value’ (if applicable) removed, and only the arguments
          following them still there.  Feel free to modify
          ‘parser.rargs’, e.g.  by consuming more arguments.

     ‘parser.values’

          the object where option values are by default stored (an
          instance of optparse.OptionValues).  This lets callbacks use
          the same mechanism as the rest of *note optparse: 90. for
          storing option values; you don't need to mess around with
          globals or closures.  You can also access or modify the
          value(s) of any options already encountered on the
          command-line.

‘args’

     is a tuple of arbitrary positional arguments supplied via the *note
     callback_args: 468f. option attribute.

‘kwargs’

     is a dictionary of arbitrary keyword arguments supplied via *note
     callback_kwargs: 4690.


File: python.info,  Node: Raising errors in a callback,  Next: Callback example 1 trivial callback,  Prev: How callbacks are called,  Up: Option Callbacks

5.36.2.31 Raising errors in a callback
......................................

The callback function should raise *note OptionValueError: 2ba2. if
there are any problems with the option or its argument(s).  *note
optparse: 90. catches this and terminates the program, printing the
error message you supply to stderr.  Your message should be clear,
concise, accurate, and mention the option at fault.  Otherwise, the user
will have a hard time figuring out what they did wrong.


File: python.info,  Node: Callback example 1 trivial callback,  Next: Callback example 2 check option order,  Prev: Raising errors in a callback,  Up: Option Callbacks

5.36.2.32 Callback example 1: trivial callback
..............................................

Here's an example of a callback option that takes no arguments, and
simply records that the option was seen:

     def record_foo_seen(option, opt_str, value, parser):
         parser.values.saw_foo = True

     parser.add_option("--foo", action="callback", callback=record_foo_seen)

Of course, you could do that with the ‘"store_true"’ action.


File: python.info,  Node: Callback example 2 check option order,  Next: Callback example 3 check option order generalized,  Prev: Callback example 1 trivial callback,  Up: Option Callbacks

5.36.2.33 Callback example 2: check option order
................................................

Here's a slightly more interesting example: record the fact that ‘-a’ is
seen, but blow up if it comes after ‘-b’ in the command-line.

     def check_order(option, opt_str, value, parser):
         if parser.values.b:
             raise OptionValueError("can't use -a after -b")
         parser.values.a = 1
     ...
     parser.add_option("-a", action="callback", callback=check_order)
     parser.add_option("-b", action="store_true", dest="b")


File: python.info,  Node: Callback example 3 check option order generalized,  Next: Callback example 4 check arbitrary condition,  Prev: Callback example 2 check option order,  Up: Option Callbacks

5.36.2.34 Callback example 3: check option order (generalized)
..............................................................

If you want to reuse this callback for several similar options (set a
flag, but blow up if ‘-b’ has already been seen), it needs a bit of
work: the error message and the flag that it sets must be generalized.

     def check_order(option, opt_str, value, parser):
         if parser.values.b:
             raise OptionValueError("can't use %s after -b" % opt_str)
         setattr(parser.values, option.dest, 1)
     ...
     parser.add_option("-a", action="callback", callback=check_order, dest='a')
     parser.add_option("-b", action="store_true", dest="b")
     parser.add_option("-c", action="callback", callback=check_order, dest='c')


File: python.info,  Node: Callback example 4 check arbitrary condition,  Next: Callback example 5 fixed arguments,  Prev: Callback example 3 check option order generalized,  Up: Option Callbacks

5.36.2.35 Callback example 4: check arbitrary condition
.......................................................

Of course, you could put any condition in there--you're not limited to
checking the values of already-defined options.  For example, if you
have options that should not be called when the moon is full, all you
have to do is this:

     def check_moon(option, opt_str, value, parser):
         if is_moon_full():
             raise OptionValueError("%s option invalid when moon is full"
                                    % opt_str)
         setattr(parser.values, option.dest, 1)
     ...
     parser.add_option("--foo",
                       action="callback", callback=check_moon, dest="foo")

(The definition of ‘is_moon_full()’ is left as an exercise for the
reader.)


File: python.info,  Node: Callback example 5 fixed arguments,  Next: Callback example 6 variable arguments,  Prev: Callback example 4 check arbitrary condition,  Up: Option Callbacks

5.36.2.36 Callback example 5: fixed arguments
.............................................

Things get slightly more interesting when you define callback options
that take a fixed number of arguments.  Specifying that a callback
option takes arguments is similar to defining a ‘"store"’ or ‘"append"’
option: if you define *note type: 465d, then the option takes one
argument that must be convertible to that type; if you further define
*note nargs: 468c, then the option takes *note nargs: 468c. arguments.

Here's an example that just emulates the standard ‘"store"’ action:

     def store_value(option, opt_str, value, parser):
         setattr(parser.values, option.dest, value)
     ...
     parser.add_option("--foo",
                       action="callback", callback=store_value,
                       type="int", nargs=3, dest="foo")

Note that *note optparse: 90. takes care of consuming 3 arguments and
converting them to integers for you; all you have to do is store them.
(Or whatever; obviously you don't need a callback for this example.)


File: python.info,  Node: Callback example 6 variable arguments,  Prev: Callback example 5 fixed arguments,  Up: Option Callbacks

5.36.2.37 Callback example 6: variable arguments
................................................

Things get hairy when you want an option to take a variable number of
arguments.  For this case, you must write a callback, as *note optparse:
90. doesn't provide any built-in capabilities for it.  And you have to
deal with certain intricacies of conventional Unix command-line parsing
that *note optparse: 90. normally handles for you.  In particular,
callbacks should implement the conventional rules for bare ‘--’ and ‘-’
arguments:

   * either ‘--’ or ‘-’ can be option arguments

   * bare ‘--’ (if not the argument to some option): halt command-line
     processing and discard the ‘--’

   * bare ‘-’ (if not the argument to some option): halt command-line
     processing but keep the ‘-’ (append it to ‘parser.largs’)

If you want an option that takes a variable number of arguments, there
are several subtle, tricky issues to worry about.  The exact
implementation you choose will be based on which trade-offs you're
willing to make for your application (which is why *note optparse: 90.
doesn't support this sort of thing directly).

Nevertheless, here's a stab at a callback for an option with variable
arguments:

     def vararg_callback(option, opt_str, value, parser):
         assert value is None
         value = []

         def floatable(str):
             try:
                 float(str)
                 return True
             except ValueError:
                 return False

         for arg in parser.rargs:
             # stop on --foo like options
             if arg[:2] == "--" and len(arg) > 2:
                 break
             # stop on -a, but not on -3 or -3.0
             if arg[:1] == "-" and len(arg) > 1 and not floatable(arg):
                 break
             value.append(arg)

         del parser.rargs[:len(value)]
         setattr(parser.values, option.dest, value)

     ...
     parser.add_option("-c", "--callback", dest="vararg_attr",
                       action="callback", callback=vararg_callback)


File: python.info,  Node: Extending optparse,  Next: 例外<16>,  Prev: Option Callbacks,  Up: optparse --- 命令列選項剖析器

5.36.2.38 Extending ‘optparse’
..............................

Since the two major controlling factors in how *note optparse: 90.
interprets command-line options are the action and type of each option,
the most likely direction of extension is to add new actions and new
types.

* Menu:

* Adding new types::
* Adding new actions::


File: python.info,  Node: Adding new types,  Next: Adding new actions,  Up: Extending optparse

5.36.2.39 Adding new types
..........................

To add new types, you need to define your own subclass of *note
optparse: 90.'s *note Option: 4684. class.  This class has a couple of
attributes that define *note optparse: 90.'s types: *note TYPES: 46b9.
and *note TYPE_CHECKER: 46ba.

 -- 屬性: Option.TYPES

     A tuple of type names; in your subclass, simply define a new tuple
     *note TYPES: 46b9. that builds on the standard one.

 -- 屬性: Option.TYPE_CHECKER

     A dictionary mapping type names to type-checking functions.  A
     type-checking function has the following signature:

          def check_mytype(option, opt, value)

     where ‘option’ is an *note Option: 4684. instance, ‘opt’ is an
     option string (e.g., ‘-f’), and ‘value’ is the string from the
     command line that must be checked and converted to your desired
     type.  ‘check_mytype()’ should return an object of the hypothetical
     type ‘mytype’.  The value returned by a type-checking function will
     wind up in the OptionValues instance returned by *note
     OptionParser.parse_args(): 143d, or be passed to a callback as the
     ‘value’ parameter.

     Your type-checking function should raise *note OptionValueError:
     2ba2. if it encounters any problems.  *note OptionValueError: 2ba2.
     takes a single string argument, which is passed as-is to *note
     OptionParser: 143c.'s ‘error()’ method, which in turn prepends the
     program name and the string ‘"error:"’ and prints everything to
     stderr before terminating the process.

Here's a silly example that demonstrates adding a ‘"complex"’ option
type to parse Python-style complex numbers on the command line.  (This
is even sillier than it used to be, because *note optparse: 90. 1.3
added built-in support for complex numbers, but never mind.)

First, the necessary imports:

     from copy import copy
     from optparse import Option, OptionValueError

You need to define your type-checker first, since it's referred to later
(in the *note TYPE_CHECKER: 46ba. class attribute of your Option
subclass):

     def check_complex(option, opt, value):
         try:
             return complex(value)
         except ValueError:
             raise OptionValueError(
                 "option %s: invalid complex value: %r" % (opt, value))

Finally, the Option subclass:

     class MyOption (Option):
         TYPES = Option.TYPES + ("complex",)
         TYPE_CHECKER = copy(Option.TYPE_CHECKER)
         TYPE_CHECKER["complex"] = check_complex

(If we didn't make a *note copy(): 1e. of *note Option.TYPE_CHECKER:
46ba, we would end up modifying the *note TYPE_CHECKER: 46ba. attribute
of *note optparse: 90.'s Option class.  This being Python, nothing stops
you from doing that except good manners and common sense.)

That's it!  Now you can write a script that uses the new option type
just like any other *note optparse: 90.-based script, except you have to
instruct your OptionParser to use MyOption instead of Option:

     parser = OptionParser(option_class=MyOption)
     parser.add_option("-c", type="complex")

Alternately, you can build your own option list and pass it to
OptionParser; if you don't use ‘add_option()’ in the above way, you
don't need to tell OptionParser which option class to use:

     option_list = [MyOption("-c", action="store", type="complex", dest="c")]
     parser = OptionParser(option_list=option_list)


File: python.info,  Node: Adding new actions,  Prev: Adding new types,  Up: Extending optparse

5.36.2.40 Adding new actions
............................

Adding new actions is a bit trickier, because you have to understand
that *note optparse: 90. has a couple of classifications for actions:

"store" actions

     actions that result in *note optparse: 90. storing a value to an
     attribute of the current OptionValues instance; these options
     require a *note dest: 465e. attribute to be supplied to the Option
     constructor.

"typed" actions

     actions that take a value from the command line and expect it to be
     of a certain type; or rather, a string that can be converted to a
     certain type.  These options require a *note type: 465d. attribute
     to the Option constructor.

These are overlapping sets: some default "store" actions are ‘"store"’,
‘"store_const"’, ‘"append"’, and ‘"count"’, while the default "typed"
actions are ‘"store"’, ‘"append"’, and ‘"callback"’.

When you add an action, you need to categorize it by listing it in at
least one of the following class attributes of Option (all are lists of
strings):

 -- 屬性: Option.ACTIONS

     All actions must be listed in ACTIONS.

 -- 屬性: Option.STORE_ACTIONS

     "store" actions are additionally listed here.

 -- 屬性: Option.TYPED_ACTIONS

     "typed" actions are additionally listed here.

 -- 屬性: Option.ALWAYS_TYPED_ACTIONS

     Actions that always take a type (i.e.  whose options always take a
     value) are additionally listed here.  The only effect of this is
     that *note optparse: 90. assigns the default type, ‘"string"’, to
     options with no explicit type whose action is listed in *note
     ALWAYS_TYPED_ACTIONS: 46c0.

In order to actually implement your new action, you must override
Option's ‘take_action()’ method and add a case that recognizes your
action.

For example, let's add an ‘"extend"’ action.  This is similar to the
standard ‘"append"’ action, but instead of taking a single value from
the command-line and appending it to an existing list, ‘"extend"’ will
take multiple values in a single comma-delimited string, and extend an
existing list with them.  That is, if ‘--names’ is an ‘"extend"’ option
of type ‘"string"’, the command line

     --names=foo,bar --names blah --names ding,dong

would result in a list

     ["foo", "bar", "blah", "ding", "dong"]

Again we define a subclass of Option:

     class MyOption(Option):

         ACTIONS = Option.ACTIONS + ("extend",)
         STORE_ACTIONS = Option.STORE_ACTIONS + ("extend",)
         TYPED_ACTIONS = Option.TYPED_ACTIONS + ("extend",)
         ALWAYS_TYPED_ACTIONS = Option.ALWAYS_TYPED_ACTIONS + ("extend",)

         def take_action(self, action, dest, opt, value, values, parser):
             if action == "extend":
                 lvalue = value.split(",")
                 values.ensure_value(dest, []).extend(lvalue)
             else:
                 Option.take_action(
                     self, action, dest, opt, value, values, parser)

Features of note:

   * ‘"extend"’ both expects a value on the command-line and stores that
     value somewhere, so it goes in both *note STORE_ACTIONS: 46be. and
     *note TYPED_ACTIONS: 46bf.

   * to ensure that *note optparse: 90. assigns the default type of
     ‘"string"’ to ‘"extend"’ actions, we put the ‘"extend"’ action in
     *note ALWAYS_TYPED_ACTIONS: 46c0. as well.

   * ‘MyOption.take_action()’ implements just this one new action, and
     passes control back to ‘Option.take_action()’ for the standard
     *note optparse: 90. actions.

   * ‘values’ is an instance of the optparse_parser.Values class, which
     provides the very useful ‘ensure_value()’ method.  ‘ensure_value()’
     is essentially *note getattr(): b78. with a safety valve; it is
     called as

          values.ensure_value(attr, value)

     If the ‘attr’ attribute of ‘values’ doesn't exist or is ‘None’,
     then ensure_value() first sets it to ‘value’, and then returns
     ‘value’.  This is very handy for actions like ‘"extend"’,
     ‘"append"’, and ‘"count"’, all of which accumulate data in a
     variable and expect that variable to be of a certain type (a list
     for the first two, an integer for the latter).  Using
     ‘ensure_value()’ means that scripts using your action don't have to
     worry about setting a default value for the option destinations in
     question; they can just leave the default as ‘None’ and
     ‘ensure_value()’ will take care of getting it right when it's
     needed.


File: python.info,  Node: 例外<16>,  Prev: Extending optparse,  Up: optparse --- 命令列選項剖析器

5.36.2.41 例外
..............

 -- 例外: optparse.OptionError

     Raised if an *note Option: 4684. instance is created with invalid
     or inconsistent arguments.

 -- 例外: optparse.OptionConflictError

     Raised if conflicting options are added to an *note OptionParser:
     143c.

 -- 例外: optparse.OptionValueError

     Raised if an invalid option value is encountered on the command
     line.

 -- 例外: optparse.BadOptionError

     Raised if an invalid option is passed on the command line.

 -- 例外: optparse.AmbiguousOptionError

     Raised if an ambiguous option is passed on the command line.


File: python.info,  Node: 安全性注意事項<4>,  Prev: 已被取代的模組,  Up: Python 標準函式庫 Standard Library

5.37 安全性注意事項
===================

以下模組具有特定的安全性注意事項：

   * *note base64: a.：*note base64 安全性注意事項: 3567.在 RFC 4648(1)

   * *note hashlib: 5e.：*note 所有建構函式都採用 "usedforsecurity"
     僅限關鍵字引數，並禁用已知的不安全與被阻擋的演算法: 29b5.

   * *note http.server: 68. 不適合在正式環境使用，因其僅實作基本的安全檢
     查。請參閱*note 安全注意事項: 398b.。

   * *note logging: 7b.：*note 日誌配置使用 eval(): 2c03.

   * *note multiprocessing: 86.：*note Connection.recv() 使用 pickle:
     2fa5.

   * *note pickle: 95.：*note 限制 pickle 中的全域變數: 277d.

   * *note random: a6. 不該用於安全性相關用途，請改用 *note secrets: ae.

   * *note shelve: b1.：*note shelve 為基於
     pickle，因此不適合用來處理不受信任的來源: 2799.

   * *note ssl: bb.：*note SSL/TLS 安全性注意事項: 317d.

   * *note subprocess: c1.：*note 子行程安全性注意事項: 304b.

   * *note tempfile: c9.：*note mktemp 由於存在競爭條件 (race condition)
     漏洞而被棄用: 273b.

   * *note xml: 107.：*note XML 漏洞: 3596.

   * *note zipfile: 117.：*note 惡意準備的 .zip
     檔案可能會導致硬碟空間耗盡: 28cc.

*note -I: 902. 命令列選項可用於在隔離模式下運行 Python。若其無法使用，可
以改用 *note -P: 548. 選項或 *note PYTHONSAFEPATH: 549. 環境變數，避免
*note sys.path: 37f. 新增潛在的不安全路徑，例如當前目錄、腳本的目錄或空
字串。

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc4648.html


File: python.info,  Node: 擴充和嵌入 Python 直譯器,  Next: Python/C API 參考手冊,  Prev: Python 標準函式庫 Standard Library,  Up: Top

6 擴充和嵌入 Python 直譯器
**************************

這份說明文件描述如何在 C 或 C++ 中編寫模組，並使用新模組來擴充 Python 直
譯器功能。那些模組不僅可以定義新的函式，也可以定義新的物件型別及其方法
(method)。文件內容也會描述如何將 Python 直譯器嵌入另一個應用程式中，做為
一種擴充語言 (extension language) 使用。最後，它會展示如何編譯及連結擴充
模組，使那些模組可以動態地（在執行環境）被載入到直譯器中，前提是底層作業
系統有支援這個功能。

這份說明文件假設你具備 Python 的基礎知識。關於此語言的非正式介紹，請參閱
*note Python 教學: 1ae0.。*note Python 語言參考手冊: 12b.給予此語言更為
正式的定義。*note Python 標準函式庫 (Standard Library): 12a. 記錄了賦予
此語言廣泛應用範圍的物件型別、函式與（內建的和以 Python 編寫的）模組。

關於完整的 Python/C API 詳細介紹，請參閱另外一份 *note Python/C API
參考手冊: 1ae2.。

* Menu:

* 推薦的第三方工具::
* 不使用第三方工具建立擴充::
* 在更大的應用程式中嵌入 CPython 運行環境 (runtime): 在更大的應用程式中嵌入 CPython 運行環境 runtime.


File: python.info,  Node: 推薦的第三方工具,  Next: 不使用第三方工具建立擴充,  Up: 擴充和嵌入 Python 直譯器

6.1 推薦的第三方工具
====================

這份指南僅涵蓋了此 CPython 版本所提供的、用以建立擴充的基本工具。第三方
工具，例如 Cython(1)、cffi(2)、SWIG(3) 和 Numba(4)，提供了更為簡單及更為
複雜的多種方法，來為 Python 建立 C 和 C ++ 擴充。

也參考
......

Python 封裝使用者指南：二進制擴充(5)

     Python 封裝使用者指南 (Python Packaging User Guide) 不僅涵蓋了數個
     可以用來簡化二進制擴充建立過程的工具，也會討論為何建立一個擴充模組
     可能會是你的優先考量。

   ---------- Footnotes ----------

   (1) https://cython.org/

   (2) https://cffi.readthedocs.io

   (3) https://www.swig.org

   (4) https://numba.pydata.org/

   (5) https://packaging.python.org/guides/packaging-binary-extensions/


File: python.info,  Node: 不使用第三方工具建立擴充,  Next: 在更大的應用程式中嵌入 CPython 運行環境 runtime,  Prev: 推薦的第三方工具,  Up: 擴充和嵌入 Python 直譯器

6.2 不使用第三方工具建立擴充
============================

本指南中的這一節將說明，在沒有第三方工具的協助下，如何建立 C 和 C ++ 擴
充。它主要是寫給使用那些工具的創作者們，而不是讓你建立自己的 C 擴充的推
薦方法。

* Menu:

* 以 C 或 C++ 擴充 Python::
* Defining Extension Types; Tutorial: Defining Extension Types Tutorial.
* Defining Extension Types; Assorted Topics: Defining Extension Types Assorted Topics.
* 建立 C 與 C++ 擴充套件::
* 建置 Windows 上的 C 和 C++ 擴充::


File: python.info,  Node: 以 C 或 C++ 擴充 Python,  Next: Defining Extension Types Tutorial,  Up: 不使用第三方工具建立擴充

6.2.1 以 C 或 C++ 擴充 Python
-----------------------------

It is quite easy to add new built-in modules to Python, if you know how
to program in C. Such 'extension modules' can do two things that can't
be done directly in Python: they can implement new built-in object
types, and they can call C library functions and system calls.

To support extensions, the Python API (Application Programmers
Interface) defines a set of functions, macros and variables that provide
access to most aspects of the Python run-time system.  The Python API is
incorporated in a C source file by including the header ‘"Python.h"’.

The compilation of an extension module depends on its intended use as
well as on your system setup; details are given in later chapters.

     備註: The C extension interface is specific to CPython, and
     extension modules do not work on other Python implementations.  In
     many cases, it is possible to avoid writing C extensions and
     preserve portability to other implementations.  For example, if
     your use case is calling C library functions or system calls, you
     should consider using the *note ctypes: 22. module or the cffi(1)
     library rather than writing custom C code.  These modules let you
     write Python code to interface with C code and are more portable
     between implementations of Python than writing and compiling a C
     extension module.

* Menu:

* 一個簡單範例::
* Intermezzo; Errors and Exceptions: Intermezzo Errors and Exceptions.
* 回到範例::
* The Module's Method Table and Initialization Function::
* Compilation and Linkage::
* Calling Python Functions from C::
* Extracting Parameters in Extension Functions::
* Keyword Parameters for Extension Functions::
* Building Arbitrary Values::
* Reference Counts::
* Writing Extensions in C++::
* Providing a C API for an Extension Module::

   ---------- Footnotes ----------

   (1) https://cffi.readthedocs.io/


File: python.info,  Node: 一個簡單範例,  Next: Intermezzo Errors and Exceptions,  Up: 以 C 或 C++ 擴充 Python

6.2.1.1 一個簡單範例
....................

Let's create an extension module called ‘spam’ (the favorite food of
Monty Python fans...)  and let's say we want to create a Python
interface to the C library function ‘system()’ (1).  This function takes
a null-terminated character string as argument and returns an integer.
We want this function to be callable from Python as follows:

     >>> import spam
     >>> status = spam.system("ls -l")

Begin by creating a file ‘spammodule.c’.  (Historically, if a module is
called ‘spam’, the C file containing its implementation is called
‘spammodule.c’; if the module name is very long, like ‘spammify’, the
module name can be just ‘spammify.c’.)

The first two lines of our file can be:

     #define PY_SSIZE_T_CLEAN
     #include <Python.h>

which pulls in the Python API (you can add a comment describing the
purpose of the module and a copyright notice if you like).

     備註: Since Python may define some pre-processor definitions which
     affect the standard headers on some systems, you 'must' include
     ‘Python.h’ before any standard headers are included.

     ‘#define PY_SSIZE_T_CLEAN’ was used to indicate that ‘Py_ssize_t’
     should be used in some APIs instead of ‘int’.  It is not necessary
     since Python 3.13, but we keep it here for backward compatibility.
     See *note Strings and buffers: 2e8. for a description of this
     macro.

All user-visible symbols defined by ‘Python.h’ have a prefix of ‘Py’ or
‘PY’, except those defined in standard header files.  For convenience,
and since they are used extensively by the Python interpreter,
‘"Python.h"’ includes a few standard header files: ‘<stdio.h>’,
‘<string.h>’, ‘<errno.h>’, and ‘<stdlib.h>’.  If the latter header file
does not exist on your system, it declares the functions ‘malloc()’,
‘free()’ and ‘realloc()’ directly.

The next thing we add to our module file is the C function that will be
called when the Python expression ‘spam.system(string)’ is evaluated
(we'll see shortly how it ends up being called):

     static PyObject *
     spam_system(PyObject *self, PyObject *args)
     {
         const char *command;
         int sts;

         if (!PyArg_ParseTuple(args, "s", &command))
             return NULL;
         sts = system(command);
         return PyLong_FromLong(sts);
     }

There is a straightforward translation from the argument list in Python
(for example, the single expression ‘"ls -l"’) to the arguments passed
to the C function.  The C function always has two arguments,
conventionally named 'self' and 'args'.

The 'self' argument points to the module object for module-level
functions; for a method it would point to the object instance.

The 'args' argument will be a pointer to a Python tuple object
containing the arguments.  Each item of the tuple corresponds to an
argument in the call's argument list.  The arguments are Python objects
-- in order to do anything with them in our C function we have to
convert them to C values.  The function *note PyArg_ParseTuple(): 517.
in the Python API checks the argument types and converts them to C
values.  It uses a template string to determine the required types of
the arguments as well as the types of the C variables into which to
store the converted values.  More about this later.

*note PyArg_ParseTuple(): 517. returns true (nonzero) if all arguments
have the right type and its components have been stored in the variables
whose addresses are passed.  It returns false (zero) if an invalid
argument list was passed.  In the latter case it also raises an
appropriate exception so the calling function can return ‘NULL’
immediately (as we saw in the example).

   ---------- Footnotes ----------

   (1) An interface for this function already exists in the standard
module *note os: 91. -- it was chosen as a simple and straightforward
example.


File: python.info,  Node: Intermezzo Errors and Exceptions,  Next: 回到範例,  Prev: 一個簡單範例,  Up: 以 C 或 C++ 擴充 Python

6.2.1.2 Intermezzo: Errors and Exceptions
.........................................

An important convention throughout the Python interpreter is the
following: when a function fails, it should set an exception condition
and return an error value (usually ‘-1’ or a ‘NULL’ pointer).  Exception
information is stored in three members of the interpreter's thread
state.  These are ‘NULL’ if there is no exception.  Otherwise they are
the C equivalents of the members of the Python tuple returned by *note
sys.exc_info(): 630.  These are the exception type, exception instance,
and a traceback object.  It is important to know about them to
understand how errors are passed around.

The Python API defines a number of functions to set various types of
exceptions.

The most common one is *note PyErr_SetString(): 522.  Its arguments are
an exception object and a C string.  The exception object is usually a
predefined object like ‘PyExc_ZeroDivisionError’.  The C string
indicates the cause of the error and is converted to a Python string
object and stored as the "associated value" of the exception.

Another useful function is *note PyErr_SetFromErrno(): 46d2, which only
takes an exception argument and constructs the associated value by
inspection of the global variable ‘errno’.  The most general function is
*note PyErr_SetObject(): 521, which takes two object arguments, the
exception and its associated value.  You don't need to *note
Py_INCREF(): 514. the objects passed to any of these functions.

You can test non-destructively whether an exception has been set with
*note PyErr_Occurred(): 17f4.  This returns the current exception
object, or ‘NULL’ if no exception has occurred.  You normally don't need
to call *note PyErr_Occurred(): 17f4. to see whether an error occurred
in a function call, since you should be able to tell from the return
value.

When a function 'f' that calls another function 'g' detects that the
latter fails, 'f' should itself return an error value (usually ‘NULL’ or
‘-1’).  It should 'not' call one of the ‘PyErr_*’ functions -- one has
already been called by 'g'.  'f"s caller is then supposed to also return
an error indication to 'its' caller, again 'without' calling ‘PyErr_*’,
and so on -- the most detailed cause of the error was already reported
by the function that first detected it.  Once the error reaches the
Python interpreter's main loop, this aborts the currently executing
Python code and tries to find an exception handler specified by the
Python programmer.

(There are situations where a module can actually give a more detailed
error message by calling another ‘PyErr_*’ function, and in such cases
it is fine to do so.  As a general rule, however, this is not necessary,
and can cause information about the cause of the error to be lost: most
operations can fail for a variety of reasons.)

To ignore an exception set by a function call that failed, the exception
condition must be cleared explicitly by calling *note PyErr_Clear():
fd4.  The only time C code should call *note PyErr_Clear(): fd4. is if
it doesn't want to pass the error on to the interpreter but wants to
handle it completely by itself (possibly by trying something else, or
pretending nothing went wrong).

Every failing ‘malloc()’ call must be turned into an exception -- the
direct caller of ‘malloc()’ (or ‘realloc()’) must call *note
PyErr_NoMemory(): 46d3. and return a failure indicator itself.  All the
object-creating functions (for example, *note PyLong_FromLong(): 173e.)
already do this, so this note is only relevant to those who call
‘malloc()’ directly.

Also note that, with the important exception of *note
PyArg_ParseTuple(): 517. and friends, functions that return an integer
status usually return a positive value or zero for success and ‘-1’ for
failure, like Unix system calls.

Finally, be careful to clean up garbage (by making *note Py_XDECREF():
733. or *note Py_DECREF(): 515. calls for objects you have already
created) when you return an error indicator!

The choice of which exception to raise is entirely yours.  There are
predeclared C objects corresponding to all built-in Python exceptions,
such as ‘PyExc_ZeroDivisionError’, which you can use directly.  Of
course, you should choose exceptions wisely -- don't use
‘PyExc_TypeError’ to mean that a file couldn't be opened (that should
probably be ‘PyExc_OSError’).  If something's wrong with the argument
list, the *note PyArg_ParseTuple(): 517. function usually raises
‘PyExc_TypeError’.  If you have an argument whose value must be in a
particular range or must satisfy other conditions, ‘PyExc_ValueError’ is
appropriate.

You can also define a new exception that is unique to your module.  For
this, you usually declare a static object variable at the beginning of
your file:

     static PyObject *SpamError;

and initialize it in your module's initialization function
(‘PyInit_spam()’) with an exception object:

     PyMODINIT_FUNC
     PyInit_spam(void)
     {
         PyObject *m;

         m = PyModule_Create(&spammodule);
         if (m == NULL)
             return NULL;

         SpamError = PyErr_NewException("spam.error", NULL, NULL);
         if (PyModule_AddObjectRef(m, "error", SpamError) < 0) {
             Py_CLEAR(SpamError);
             Py_DECREF(m);
             return NULL;
         }

         return m;
     }

Note that the Python name for the exception object is ‘spam.error’.  The
*note PyErr_NewException(): 1202. function may create a class with the
base class being *note Exception: 97d. (unless another class is passed
in instead of ‘NULL’), described in *note 內建的例外: 1786.

Note also that the ‘SpamError’ variable retains a reference to the newly
created exception class; this is intentional!  Since the exception could
be removed from the module by external code, an owned reference to the
class is needed to ensure that it will not be discarded, causing
‘SpamError’ to become a dangling pointer.  Should it become a dangling
pointer, C code which raises the exception could cause a core dump or
other unintended side effects.

We discuss the use of *note PyMODINIT_FUNC: 1442. as a function return
type later in this sample.

The ‘spam.error’ exception can be raised in your extension module using
a call to *note PyErr_SetString(): 522. as shown below:

     static PyObject *
     spam_system(PyObject *self, PyObject *args)
     {
         const char *command;
         int sts;

         if (!PyArg_ParseTuple(args, "s", &command))
             return NULL;
         sts = system(command);
         if (sts < 0) {
             PyErr_SetString(SpamError, "System command failed");
             return NULL;
         }
         return PyLong_FromLong(sts);
     }


File: python.info,  Node: 回到範例,  Next: The Module's Method Table and Initialization Function,  Prev: Intermezzo Errors and Exceptions,  Up: 以 C 或 C++ 擴充 Python

6.2.1.3 回到範例
................

Going back to our example function, you should now be able to understand
this statement:

     if (!PyArg_ParseTuple(args, "s", &command))
         return NULL;

It returns ‘NULL’ (the error indicator for functions returning object
pointers) if an error is detected in the argument list, relying on the
exception set by *note PyArg_ParseTuple(): 517.  Otherwise the string
value of the argument has been copied to the local variable ‘command’.
This is a pointer assignment and you are not supposed to modify the
string to which it points (so in Standard C, the variable ‘command’
should properly be declared as ‘const char *command’).

The next statement is a call to the Unix function ‘system()’, passing it
the string we just got from *note PyArg_ParseTuple(): 517.:

     sts = system(command);

Our ‘spam.system()’ function must return the value of ‘sts’ as a Python
object.  This is done using the function *note PyLong_FromLong(): 173e.

     return PyLong_FromLong(sts);

In this case, it will return an integer object.  (Yes, even integers are
objects on the heap in Python!)

If you have a C function that returns no useful argument (a function
returning void), the corresponding Python function must return ‘None’.
You need this idiom to do so (which is implemented by the *note
Py_RETURN_NONE: 13de. macro):

     Py_INCREF(Py_None);
     return Py_None;

*note Py_None: 46d6. is the C name for the special Python object ‘None’.
It is a genuine Python object rather than a ‘NULL’ pointer, which means
"error" in most contexts, as we have seen.


File: python.info,  Node: The Module's Method Table and Initialization Function,  Next: Compilation and Linkage,  Prev: 回到範例,  Up: 以 C 或 C++ 擴充 Python

6.2.1.4 The Module's Method Table and Initialization Function
.............................................................

I promised to show how ‘spam_system()’ is called from Python programs.
First, we need to list its name and address in a "method table":

     static PyMethodDef SpamMethods[] = {
         ...
         {"system",  spam_system, METH_VARARGS,
          "Execute a shell command."},
         ...
         {NULL, NULL, 0, NULL}        /* Sentinel */
     };

Note the third entry (‘METH_VARARGS’).  This is a flag telling the
interpreter the calling convention to be used for the C function.  It
should normally always be ‘METH_VARARGS’ or ‘METH_VARARGS |
METH_KEYWORDS’; a value of ‘0’ means that an obsolete variant of *note
PyArg_ParseTuple(): 517. is used.

When using only ‘METH_VARARGS’, the function should expect the
Python-level parameters to be passed in as a tuple acceptable for
parsing via *note PyArg_ParseTuple(): 517.; more information on this
function is provided below.

The *note METH_KEYWORDS: 46d9. bit may be set in the third field if
keyword arguments should be passed to the function.  In this case, the C
function should accept a third ‘PyObject *’ parameter which will be a
dictionary of keywords.  Use *note PyArg_ParseTupleAndKeywords(): 2e9.
to parse the arguments to such a function.

The method table must be referenced in the module definition structure:

     static struct PyModuleDef spammodule = {
         PyModuleDef_HEAD_INIT,
         "spam",   /* name of module */
         spam_doc, /* module documentation, may be NULL */
         -1,       /* size of per-interpreter state of the module,
                      or -1 if the module keeps state in global variables. */
         SpamMethods
     };

This structure, in turn, must be passed to the interpreter in the
module's initialization function.  The initialization function must be
named ‘PyInit_name()’, where 'name' is the name of the module, and
should be the only non-‘static’ item defined in the module file:

     PyMODINIT_FUNC
     PyInit_spam(void)
     {
         return PyModule_Create(&spammodule);
     }

Note that *note PyMODINIT_FUNC: 1442. declares the function as ‘PyObject
*’ return type, declares any special linkage declarations required by
the platform, and for C++ declares the function as ‘extern "C"’.

When the Python program imports module ‘spam’ for the first time,
‘PyInit_spam()’ is called.  (See below for comments about embedding
Python.)  It calls *note PyModule_Create(): 46da, which returns a module
object, and inserts built-in function objects into the newly created
module based upon the table (an array of *note PyMethodDef: 1446.
structures) found in the module definition.  *note PyModule_Create():
46da. returns a pointer to the module object that it creates.  It may
abort with a fatal error for certain errors, or return ‘NULL’ if the
module could not be initialized satisfactorily.  The init function must
return the module object to its caller, so that it then gets inserted
into ‘sys.modules’.

When embedding Python, the ‘PyInit_spam()’ function is not called
automatically unless there's an entry in the ‘PyImport_Inittab’ table.
To add the module to the initialization table, use *note
PyImport_AppendInittab(): 16a6, optionally followed by an import of the
module:

     #define PY_SSIZE_T_CLEAN
     #include <Python.h>

     int
     main(int argc, char *argv[])
     {
         PyStatus status;
         PyConfig config;
         PyConfig_InitPythonConfig(&config);

         /* Add a built-in module, before Py_Initialize */
         if (PyImport_AppendInittab("spam", PyInit_spam) == -1) {
             fprintf(stderr, "Error: could not extend in-built modules table\n");
             exit(1);
         }

         /* Pass argv[0] to the Python interpreter */
         status = PyConfig_SetBytesString(&config, &config.program_name, argv[0]);
         if (PyStatus_Exception(status)) {
             goto exception;
         }

         /* Initialize the Python interpreter.  Required.
            If this step fails, it will be a fatal error. */
         status = Py_InitializeFromConfig(&config);
         if (PyStatus_Exception(status)) {
             goto exception;
         }
         PyConfig_Clear(&config);

         /* Optionally import the module; alternatively,
            import can be deferred until the embedded script
            imports it. */
         PyObject *pmodule = PyImport_ImportModule("spam");
         if (!pmodule) {
             PyErr_Print();
             fprintf(stderr, "Error: could not import module 'spam'\n");
         }

         // ... use Python C API here ...

         return 0;

       exception:
          PyConfig_Clear(&config);
          Py_ExitStatusException(status);
     }

     備註: Removing entries from ‘sys.modules’ or importing compiled
     modules into multiple interpreters within a process (or following a
     ‘fork()’ without an intervening ‘exec()’) can create problems for
     some extension modules.  Extension module authors should exercise
     caution when initializing internal data structures.

A more substantial example module is included in the Python source
distribution as ‘Modules/xxmodule.c’.  This file may be used as a
template or simply read as an example.

     備註: Unlike our ‘spam’ example, ‘xxmodule’ uses 'multi-phase
     initialization' (new in Python 3.5), where a PyModuleDef structure
     is returned from ‘PyInit_spam’, and creation of the module is left
     to the import machinery.  For details on multi-phase
     initialization, see PEP 489(1).

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0489/


File: python.info,  Node: Compilation and Linkage,  Next: Calling Python Functions from C,  Prev: The Module's Method Table and Initialization Function,  Up: 以 C 或 C++ 擴充 Python

6.2.1.5 Compilation and Linkage
...............................

There are two more things to do before you can use your new extension:
compiling and linking it with the Python system.  If you use dynamic
loading, the details may depend on the style of dynamic loading your
system uses; see the chapters about building extension modules (chapter
*note 建立 C 與 C++ 擴充套件: 46dd.) and additional information that
pertains only to building on Windows (chapter *note 建置 Windows 上的 C
和 C++ 擴充: 1d37.) for more information about this.

If you can't use dynamic loading, or if you want to make your module a
permanent part of the Python interpreter, you will have to change the
configuration setup and rebuild the interpreter.  Luckily, this is very
simple on Unix: just place your file (‘spammodule.c’ for example) in the
‘Modules/’ directory of an unpacked source distribution, add a line to
the file ‘Modules/Setup.local’ describing your file:

     spam spammodule.o

and rebuild the interpreter by running ‘make’ in the toplevel directory.
You can also run ‘make’ in the ‘Modules/’ subdirectory, but then you
must first rebuild ‘Makefile’ there by running '‘make’ Makefile'.  (This
is necessary each time you change the ‘Setup’ file.)

If your module requires additional libraries to link with, these can be
listed on the line in the configuration file as well, for instance:

     spam spammodule.o -lX11


File: python.info,  Node: Calling Python Functions from C,  Next: Extracting Parameters in Extension Functions,  Prev: Compilation and Linkage,  Up: 以 C 或 C++ 擴充 Python

6.2.1.6 Calling Python Functions from C
.......................................

So far we have concentrated on making C functions callable from Python.
The reverse is also useful: calling Python functions from C. This is
especially the case for libraries that support so-called "callback"
functions.  If a C interface makes use of callbacks, the equivalent
Python often needs to provide a callback mechanism to the Python
programmer; the implementation will require calling the Python callback
functions from a C callback.  Other uses are also imaginable.

Fortunately, the Python interpreter is easily called recursively, and
there is a standard interface to call a Python function.  (I won't dwell
on how to call the Python parser with a particular string as input -- if
you're interested, have a look at the implementation of the *note -c:
584. command line option in ‘Modules/main.c’ from the Python source
code.)

Calling a Python function is easy.  First, the Python program must
somehow pass you the Python function object.  You should provide a
function (or some other interface) to do this.  When this function is
called, save a pointer to the Python function object (be careful to
*note Py_INCREF(): 514. it!)  in a global variable -- or wherever you
see fit.  For example, the following function might be part of a module
definition:

     static PyObject *my_callback = NULL;

     static PyObject *
     my_set_callback(PyObject *dummy, PyObject *args)
     {
         PyObject *result = NULL;
         PyObject *temp;

         if (PyArg_ParseTuple(args, "O:set_callback", &temp)) {
             if (!PyCallable_Check(temp)) {
                 PyErr_SetString(PyExc_TypeError, "parameter must be callable");
                 return NULL;
             }
             Py_XINCREF(temp);         /* Add a reference to new callback */
             Py_XDECREF(my_callback);  /* Dispose of previous callback */
             my_callback = temp;       /* Remember new callback */
             /* Boilerplate to return "None" */
             Py_INCREF(Py_None);
             result = Py_None;
         }
         return result;
     }

This function must be registered with the interpreter using the *note
METH_VARARGS: 1478. flag; this is described in section *note The
Module's Method Table and Initialization Function: 46d7.  The *note
PyArg_ParseTuple(): 517. function and its arguments are documented in
section *note Extracting Parameters in Extension Functions: 46e0.

The macros *note Py_XINCREF(): a08. and *note Py_XDECREF(): 733.
increment/decrement the reference count of an object and are safe in the
presence of ‘NULL’ pointers (but note that 'temp' will not be ‘NULL’ in
this context).  More info on them in section *note Reference Counts:
46e1.

Later, when it is time to call the function, you call the C function
*note PyObject_CallObject(): 46e2.  This function has two arguments,
both pointers to arbitrary Python objects: the Python function, and the
argument list.  The argument list must always be a tuple object, whose
length is the number of arguments.  To call the Python function with no
arguments, pass in ‘NULL’, or an empty tuple; to call it with one
argument, pass a singleton tuple.  *note Py_BuildValue(): 84c. returns a
tuple when its format string consists of zero or more format codes
between parentheses.  For example:

     int arg;
     PyObject *arglist;
     PyObject *result;
     ...
     arg = 123;
     ...
     /* Time to call the callback */
     arglist = Py_BuildValue("(i)", arg);
     result = PyObject_CallObject(my_callback, arglist);
     Py_DECREF(arglist);

*note PyObject_CallObject(): 46e2. returns a Python object pointer: this
is the return value of the Python function.  *note
PyObject_CallObject(): 46e2. is "reference-count-neutral" with respect
to its arguments.  In the example a new tuple was created to serve as
the argument list, which is *note Py_DECREF(): 515.-ed immediately after
the *note PyObject_CallObject(): 46e2. call.

The return value of *note PyObject_CallObject(): 46e2. is "new": either
it is a brand new object, or it is an existing object whose reference
count has been incremented.  So, unless you want to save it in a global
variable, you should somehow *note Py_DECREF(): 515. the result, even
(especially!)  if you are not interested in its value.

Before you do this, however, it is important to check that the return
value isn't ‘NULL’.  If it is, the Python function terminated by raising
an exception.  If the C code that called *note PyObject_CallObject():
46e2. is called from Python, it should now return an error indication to
its Python caller, so the interpreter can print a stack trace, or the
calling Python code can handle the exception.  If this is not possible
or desirable, the exception should be cleared by calling *note
PyErr_Clear(): fd4.  For example:

     if (result == NULL)
         return NULL; /* Pass error back */
     ...use result...
     Py_DECREF(result);

Depending on the desired interface to the Python callback function, you
may also have to provide an argument list to *note
PyObject_CallObject(): 46e2.  In some cases the argument list is also
provided by the Python program, through the same interface that
specified the callback function.  It can then be saved and used in the
same manner as the function object.  In other cases, you may have to
construct a new tuple to pass as the argument list.  The simplest way to
do this is to call *note Py_BuildValue(): 84c.  For example, if you want
to pass an integral event code, you might use the following code:

     PyObject *arglist;
     ...
     arglist = Py_BuildValue("(l)", eventcode);
     result = PyObject_CallObject(my_callback, arglist);
     Py_DECREF(arglist);
     if (result == NULL)
         return NULL; /* Pass error back */
     /* Here maybe use the result */
     Py_DECREF(result);

Note the placement of ‘Py_DECREF(arglist)’ immediately after the call,
before the error check!  Also note that strictly speaking this code is
not complete: *note Py_BuildValue(): 84c. may run out of memory, and
this should be checked.

You may also call a function with keyword arguments by using *note
PyObject_Call(): 363, which supports arguments and keyword arguments.
As in the above example, we use *note Py_BuildValue(): 84c. to construct
the dictionary.

     PyObject *dict;
     ...
     dict = Py_BuildValue("{s:i}", "name", val);
     result = PyObject_Call(my_callback, NULL, dict);
     Py_DECREF(dict);
     if (result == NULL)
         return NULL; /* Pass error back */
     /* Here maybe use the result */
     Py_DECREF(result);


File: python.info,  Node: Extracting Parameters in Extension Functions,  Next: Keyword Parameters for Extension Functions,  Prev: Calling Python Functions from C,  Up: 以 C 或 C++ 擴充 Python

6.2.1.7 Extracting Parameters in Extension Functions
....................................................

The *note PyArg_ParseTuple(): 517. function is declared as follows:

     int PyArg_ParseTuple(PyObject *arg, const char *format, ...);

The 'arg' argument must be a tuple object containing an argument list
passed from Python to a C function.  The 'format' argument must be a
format string, whose syntax is explained in *note 剖析引數與建置數值:
84d. in the Python/C API Reference Manual.  The remaining arguments must
be addresses of variables whose type is determined by the format string.

Note that while *note PyArg_ParseTuple(): 517. checks that the Python
arguments have the required types, it cannot check the validity of the
addresses of C variables passed to the call: if you make mistakes there,
your code will probably crash or at least overwrite random bits in
memory.  So be careful!

Note that any Python object references which are provided to the caller
are 'borrowed' references; do not decrement their reference count!

一些呼叫範例：

     #define PY_SSIZE_T_CLEAN
     #include <Python.h>

     int ok;
     int i, j;
     long k, l;
     const char *s;
     Py_ssize_t size;

     ok = PyArg_ParseTuple(args, ""); /* 沒有引數 */
         /* Python 呼叫：f() */

     ok = PyArg_ParseTuple(args, "s", &s); /* A string */
         /* Possible Python call: f('whoops!') */

     ok = PyArg_ParseTuple(args, "lls", &k, &l, &s); /* Two longs and a string */
         /* Possible Python call: f(1, 2, 'three') */

     ok = PyArg_ParseTuple(args, "(ii)s#", &i, &j, &s, &size);
         /* A pair of ints and a string, whose size is also returned */
         /* Possible Python call: f((1, 2), 'three') */

     {
         const char *file;
         const char *mode = "r";
         int bufsize = 0;
         ok = PyArg_ParseTuple(args, "s|si", &file, &mode, &bufsize);
         /* A string, and optionally another string and an integer */
         /* Possible Python calls:
            f('spam')
            f('spam', 'w')
            f('spam', 'wb', 100000) */
     }

     {
         int left, top, right, bottom, h, v;
         ok = PyArg_ParseTuple(args, "((ii)(ii))(ii)",
                  &left, &top, &right, &bottom, &h, &v);
         /* A rectangle and a point */
         /* Possible Python call:
            f(((0, 0), (400, 300)), (10, 10)) */
     }

     {
         Py_complex c;
         ok = PyArg_ParseTuple(args, "D:myfunction", &c);
         /* a complex, also providing a function name for errors */
         /* Possible Python call: myfunction(1+2j) */
     }


File: python.info,  Node: Keyword Parameters for Extension Functions,  Next: Building Arbitrary Values,  Prev: Extracting Parameters in Extension Functions,  Up: 以 C 或 C++ 擴充 Python

6.2.1.8 Keyword Parameters for Extension Functions
..................................................

The *note PyArg_ParseTupleAndKeywords(): 2e9. function is declared as
follows:

     int PyArg_ParseTupleAndKeywords(PyObject *arg, PyObject *kwdict,
                                     const char *format, char * const *kwlist, ...);

The 'arg' and 'format' parameters are identical to those of the *note
PyArg_ParseTuple(): 517. function.  The 'kwdict' parameter is the
dictionary of keywords received as the third parameter from the Python
runtime.  The 'kwlist' parameter is a ‘NULL’-terminated list of strings
which identify the parameters; the names are matched with the type
information from 'format' from left to right.  On success, *note
PyArg_ParseTupleAndKeywords(): 2e9. returns true, otherwise it returns
false and raises an appropriate exception.

     備註: Nested tuples cannot be parsed when using keyword arguments!
     Keyword parameters passed in which are not present in the 'kwlist'
     will cause *note TypeError: 4dd. to be raised.

Here is an example module which uses keywords, based on an example by
Geoff Philbrick (<philbrick@hks.com>):

     #define PY_SSIZE_T_CLEAN
     #include <Python.h>

     static PyObject *
     keywdarg_parrot(PyObject *self, PyObject *args, PyObject *keywds)
     {
         int voltage;
         const char *state = "a stiff";
         const char *action = "voom";
         const char *type = "Norwegian Blue";

         static char *kwlist[] = {"voltage", "state", "action", "type", NULL};

         if (!PyArg_ParseTupleAndKeywords(args, keywds, "i|sss", kwlist,
                                          &voltage, &state, &action, &type))
             return NULL;

         printf("-- This parrot wouldn't %s if you put %i Volts through it.\n",
                action, voltage);
         printf("-- Lovely plumage, the %s -- It's %s!\n", type, state);

         Py_RETURN_NONE;
     }

     static PyMethodDef keywdarg_methods[] = {
         /* The cast of the function is necessary since PyCFunction values
          * only take two PyObject* parameters, and keywdarg_parrot() takes
          * three.
          */
         {"parrot", (PyCFunction)(void(*)(void))keywdarg_parrot, METH_VARARGS | METH_KEYWORDS,
          "Print a lovely skit to standard output."},
         {NULL, NULL, 0, NULL}   /* sentinel */
     };

     static struct PyModuleDef keywdargmodule = {
         PyModuleDef_HEAD_INIT,
         "keywdarg",
         NULL,
         -1,
         keywdarg_methods
     };

     PyMODINIT_FUNC
     PyInit_keywdarg(void)
     {
         return PyModule_Create(&keywdargmodule);
     }


File: python.info,  Node: Building Arbitrary Values,  Next: Reference Counts,  Prev: Keyword Parameters for Extension Functions,  Up: 以 C 或 C++ 擴充 Python

6.2.1.9 Building Arbitrary Values
.................................

This function is the counterpart to *note PyArg_ParseTuple(): 517.  It
is declared as follows:

     PyObject *Py_BuildValue(const char *format, ...);

It recognizes a set of format units similar to the ones recognized by
*note PyArg_ParseTuple(): 517, but the arguments (which are input to the
function, not output) must not be pointers, just values.  It returns a
new Python object, suitable for returning from a C function called from
Python.

One difference with *note PyArg_ParseTuple(): 517.: while the latter
requires its first argument to be a tuple (since Python argument lists
are always represented as tuples internally), *note Py_BuildValue():
84c. does not always build a tuple.  It builds a tuple only if its
format string contains two or more format units.  If the format string
is empty, it returns ‘None’; if it contains exactly one format unit, it
returns whatever object is described by that format unit.  To force it
to return a tuple of size 0 or one, parenthesize the format string.

Examples (to the left the call, to the right the resulting Python
value):

     Py_BuildValue("")                        None
     Py_BuildValue("i", 123)                  123
     Py_BuildValue("iii", 123, 456, 789)      (123, 456, 789)
     Py_BuildValue("s", "hello")              'hello'
     Py_BuildValue("y", "hello")              b'hello'
     Py_BuildValue("ss", "hello", "world")    ('hello', 'world')
     Py_BuildValue("s#", "hello", 4)          'hell'
     Py_BuildValue("y#", "hello", 4)          b'hell'
     Py_BuildValue("()")                      ()
     Py_BuildValue("(i)", 123)                (123,)
     Py_BuildValue("(ii)", 123, 456)          (123, 456)
     Py_BuildValue("(i,i)", 123, 456)         (123, 456)
     Py_BuildValue("[i,i]", 123, 456)         [123, 456]
     Py_BuildValue("{s:i,s:i}",
                   "abc", 123, "def", 456)    {'abc': 123, 'def': 456}
     Py_BuildValue("((ii)(ii)) (ii)",
                   1, 2, 3, 4, 5, 6)          (((1, 2), (3, 4)), (5, 6))


File: python.info,  Node: Reference Counts,  Next: Writing Extensions in C++,  Prev: Building Arbitrary Values,  Up: 以 C 或 C++ 擴充 Python

6.2.1.10 Reference Counts
.........................

In languages like C or C++, the programmer is responsible for dynamic
allocation and deallocation of memory on the heap.  In C, this is done
using the functions ‘malloc()’ and ‘free()’.  In C++, the operators
‘new’ and ‘delete’ are used with essentially the same meaning and we'll
restrict the following discussion to the C case.

Every block of memory allocated with ‘malloc()’ should eventually be
returned to the pool of available memory by exactly one call to
‘free()’.  It is important to call ‘free()’ at the right time.  If a
block's address is forgotten but ‘free()’ is not called for it, the
memory it occupies cannot be reused until the program terminates.  This
is called a 'memory leak'.  On the other hand, if a program calls
‘free()’ for a block and then continues to use the block, it creates a
conflict with reuse of the block through another ‘malloc()’ call.  This
is called 'using freed memory'.  It has the same bad consequences as
referencing uninitialized data -- core dumps, wrong results, mysterious
crashes.

Common causes of memory leaks are unusual paths through the code.  For
instance, a function may allocate a block of memory, do some
calculation, and then free the block again.  Now a change in the
requirements for the function may add a test to the calculation that
detects an error condition and can return prematurely from the function.
It's easy to forget to free the allocated memory block when taking this
premature exit, especially when it is added later to the code.  Such
leaks, once introduced, often go undetected for a long time: the error
exit is taken only in a small fraction of all calls, and most modern
machines have plenty of virtual memory, so the leak only becomes
apparent in a long-running process that uses the leaking function
frequently.  Therefore, it's important to prevent leaks from happening
by having a coding convention or strategy that minimizes this kind of
errors.

Since Python makes heavy use of ‘malloc()’ and ‘free()’, it needs a
strategy to avoid memory leaks as well as the use of freed memory.  The
chosen method is called 'reference counting'.  The principle is simple:
every object contains a counter, which is incremented when a reference
to the object is stored somewhere, and which is decremented when a
reference to it is deleted.  When the counter reaches zero, the last
reference to the object has been deleted and the object is freed.

An alternative strategy is called 'automatic garbage collection'.
(Sometimes, reference counting is also referred to as a garbage
collection strategy, hence my use of "automatic" to distinguish the
two.)  The big advantage of automatic garbage collection is that the
user doesn't need to call ‘free()’ explicitly.  (Another claimed
advantage is an improvement in speed or memory usage -- this is no hard
fact however.)  The disadvantage is that for C, there is no truly
portable automatic garbage collector, while reference counting can be
implemented portably (as long as the functions ‘malloc()’ and ‘free()’
are available -- which the C Standard guarantees).  Maybe some day a
sufficiently portable automatic garbage collector will be available for
C. Until then, we'll have to live with reference counts.

While Python uses the traditional reference counting implementation, it
also offers a cycle detector that works to detect reference cycles.
This allows applications to not worry about creating direct or indirect
circular references; these are the weakness of garbage collection
implemented using only reference counting.  Reference cycles consist of
objects which contain (possibly indirect) references to themselves, so
that each object in the cycle has a reference count which is non-zero.
Typical reference counting implementations are not able to reclaim the
memory belonging to any objects in a reference cycle, or referenced from
the objects in the cycle, even though there are no further references to
the cycle itself.

The cycle detector is able to detect garbage cycles and can reclaim
them.  The *note gc: 56. module exposes a way to run the detector (the
*note collect(): 16b. function), as well as configuration interfaces and
the ability to disable the detector at runtime.

* Menu:

* Reference Counting in Python::
* Ownership Rules::
* Thin Ice::
* NULL 指標::


File: python.info,  Node: Reference Counting in Python,  Next: Ownership Rules,  Up: Reference Counts

6.2.1.11 Reference Counting in Python
.....................................

There are two macros, ‘Py_INCREF(x)’ and ‘Py_DECREF(x)’, which handle
the incrementing and decrementing of the reference count.  *note
Py_DECREF(): 515. also frees the object when the count reaches zero.
For flexibility, it doesn't call ‘free()’ directly -- rather, it makes a
call through a function pointer in the object's 'type object'.  For this
purpose (and others), every object also contains a pointer to its type
object.

The big question now remains: when to use ‘Py_INCREF(x)’ and
‘Py_DECREF(x)’?  Let's first introduce some terms.  Nobody "owns" an
object; however, you can 'own a reference' to an object.  An object's
reference count is now defined as the number of owned references to it.
The owner of a reference is responsible for calling *note Py_DECREF():
515. when the reference is no longer needed.  Ownership of a reference
can be transferred.  There are three ways to dispose of an owned
reference: pass it on, store it, or call *note Py_DECREF(): 515.
Forgetting to dispose of an owned reference creates a memory leak.

It is also possible to 'borrow' (1) a reference to an object.  The
borrower of a reference should not call *note Py_DECREF(): 515.  The
borrower must not hold on to the object longer than the owner from which
it was borrowed.  Using a borrowed reference after the owner has
disposed of it risks using freed memory and should be avoided completely
(2).

The advantage of borrowing over owning a reference is that you don't
need to take care of disposing of the reference on all possible paths
through the code -- in other words, with a borrowed reference you don't
run the risk of leaking when a premature exit is taken.  The
disadvantage of borrowing over owning is that there are some subtle
situations where in seemingly correct code a borrowed reference can be
used after the owner from which it was borrowed has in fact disposed of
it.

A borrowed reference can be changed into an owned reference by calling
*note Py_INCREF(): 514.  This does not affect the status of the owner
from which the reference was borrowed -- it creates a new owned
reference, and gives full owner responsibilities (the new owner must
dispose of the reference properly, as well as the previous owner).

   ---------- Footnotes ----------

   (1) The metaphor of "borrowing" a reference is not completely
correct: the owner still has a copy of the reference.

   (2) Checking that the reference count is at least 1 'does not work'
-- the reference count itself could be in freed memory and may thus be
reused for another object!


File: python.info,  Node: Ownership Rules,  Next: Thin Ice,  Prev: Reference Counting in Python,  Up: Reference Counts

6.2.1.12 Ownership Rules
........................

Whenever an object reference is passed into or out of a function, it is
part of the function's interface specification whether ownership is
transferred with the reference or not.

Most functions that return a reference to an object pass on ownership
with the reference.  In particular, all functions whose function it is
to create a new object, such as *note PyLong_FromLong(): 173e. and *note
Py_BuildValue(): 84c, pass ownership to the receiver.  Even if the
object is not actually new, you still receive ownership of a new
reference to that object.  For instance, *note PyLong_FromLong(): 173e.
maintains a cache of popular values and can return a reference to a
cached item.

Many functions that extract objects from other objects also transfer
ownership with the reference, for instance *note
PyObject_GetAttrString(): 2f5.  The picture is less clear, here,
however, since a few common routines are exceptions: *note
PyTuple_GetItem(): 46ed, *note PyList_GetItem(): 313, *note
PyDict_GetItem(): 35b, and *note PyDict_GetItemString(): 35c. all return
references that you borrow from the tuple, list or dictionary.

The function *note PyImport_AddModule(): 2ed. also returns a borrowed
reference, even though it may actually create the object it returns:
this is possible because an owned reference to the object is stored in
‘sys.modules’.

When you pass an object reference into another function, in general, the
function borrows the reference from you -- if it needs to store it, it
will use *note Py_INCREF(): 514. to become an independent owner.  There
are exactly two important exceptions to this rule: *note
PyTuple_SetItem(): 46ee. and *note PyList_SetItem(): 46ef.  These
functions take over ownership of the item passed to them -- even if they
fail!  (Note that *note PyDict_SetItem(): 46f0. and friends don't take
over ownership -- they are "normal.")

When a C function is called from Python, it borrows references to its
arguments from the caller.  The caller owns a reference to the object,
so the borrowed reference's lifetime is guaranteed until the function
returns.  Only when such a borrowed reference must be stored or passed
on, it must be turned into an owned reference by calling *note
Py_INCREF(): 514.

The object reference returned from a C function that is called from
Python must be an owned reference -- ownership is transferred from the
function to its caller.


File: python.info,  Node: Thin Ice,  Next: NULL 指標,  Prev: Ownership Rules,  Up: Reference Counts

6.2.1.13 Thin Ice
.................

There are a few situations where seemingly harmless use of a borrowed
reference can lead to problems.  These all have to do with implicit
invocations of the interpreter, which can cause the owner of a reference
to dispose of it.

The first and most important case to know about is using *note
Py_DECREF(): 515. on an unrelated object while borrowing a reference to
a list item.  For instance:

     void
     bug(PyObject *list)
     {
         PyObject *item = PyList_GetItem(list, 0);

         PyList_SetItem(list, 1, PyLong_FromLong(0L));
         PyObject_Print(item, stdout, 0); /* BUG! */
     }

This function first borrows a reference to ‘list[0]’, then replaces
‘list[1]’ with the value ‘0’, and finally prints the borrowed reference.
Looks harmless, right?  But it's not!

Let's follow the control flow into *note PyList_SetItem(): 46ef.  The
list owns references to all its items, so when item 1 is replaced, it
has to dispose of the original item 1.  Now let's suppose the original
item 1 was an instance of a user-defined class, and let's further
suppose that the class defined a ‘__del__()’ method.  If this class
instance has a reference count of 1, disposing of it will call its
‘__del__()’ method.

Since it is written in Python, the ‘__del__()’ method can execute
arbitrary Python code.  Could it perhaps do something to invalidate the
reference to ‘item’ in ‘bug()’?  You bet!  Assuming that the list passed
into ‘bug()’ is accessible to the ‘__del__()’ method, it could execute a
statement to the effect of ‘del list[0]’, and assuming this was the last
reference to that object, it would free the memory associated with it,
thereby invalidating ‘item’.

The solution, once you know the source of the problem, is easy:
temporarily increment the reference count.  The correct version of the
function reads:

     void
     no_bug(PyObject *list)
     {
         PyObject *item = PyList_GetItem(list, 0);

         Py_INCREF(item);
         PyList_SetItem(list, 1, PyLong_FromLong(0L));
         PyObject_Print(item, stdout, 0);
         Py_DECREF(item);
     }

This is a true story.  An older version of Python contained variants of
this bug and someone spent a considerable amount of time in a C debugger
to figure out why his ‘__del__()’ methods would fail...

The second case of problems with a borrowed reference is a variant
involving threads.  Normally, multiple threads in the Python interpreter
can't get in each other's way, because there is a global lock protecting
Python's entire object space.  However, it is possible to temporarily
release this lock using the macro *note Py_BEGIN_ALLOW_THREADS: 46f3,
and to re-acquire it using *note Py_END_ALLOW_THREADS: a31.  This is
common around blocking I/O calls, to let other threads use the processor
while waiting for the I/O to complete.  Obviously, the following
function has the same problem as the previous one:

     void
     bug(PyObject *list)
     {
         PyObject *item = PyList_GetItem(list, 0);
         Py_BEGIN_ALLOW_THREADS
         ...some blocking I/O call...
         Py_END_ALLOW_THREADS
         PyObject_Print(item, stdout, 0); /* BUG! */
     }


File: python.info,  Node: NULL 指標,  Prev: Thin Ice,  Up: Reference Counts

6.2.1.14 NULL 指標
..................

In general, functions that take object references as arguments do not
expect you to pass them ‘NULL’ pointers, and will dump core (or cause
later core dumps) if you do so.  Functions that return object references
generally return ‘NULL’ only to indicate that an exception occurred.
The reason for not testing for ‘NULL’ arguments is that functions often
pass the objects they receive on to other function -- if each function
were to test for ‘NULL’, there would be a lot of redundant tests and the
code would run more slowly.

It is better to test for ‘NULL’ only at the "source:" when a pointer
that may be ‘NULL’ is received, for example, from ‘malloc()’ or from a
function that may raise an exception.

The macros *note Py_INCREF(): 514. and *note Py_DECREF(): 515. do not
check for ‘NULL’ pointers -- however, their variants *note Py_XINCREF():
a08. and *note Py_XDECREF(): 733. do.

The macros for checking for a particular object type (‘Pytype_Check()’)
don't check for ‘NULL’ pointers -- again, there is much code that calls
several of these in a row to test an object against various different
expected types, and this would generate redundant tests.  There are no
variants with ‘NULL’ checking.

The C function calling mechanism guarantees that the argument list
passed to C functions (‘args’ in the examples) is never ‘NULL’ -- in
fact it guarantees that it is always a tuple (1).

It is a severe error to ever let a ‘NULL’ pointer "escape" to the Python
user.

   ---------- Footnotes ----------

   (1) These guarantees don't hold when you use the "old" style calling
convention -- this is still found in much existing code.


File: python.info,  Node: Writing Extensions in C++,  Next: Providing a C API for an Extension Module,  Prev: Reference Counts,  Up: 以 C 或 C++ 擴充 Python

6.2.1.15 Writing Extensions in C++
..................................

It is possible to write extension modules in C++.  Some restrictions
apply.  If the main program (the Python interpreter) is compiled and
linked by the C compiler, global or static objects with constructors
cannot be used.  This is not a problem if the main program is linked by
the C++ compiler.  Functions that will be called by the Python
interpreter (in particular, module initialization functions) have to be
declared using ‘extern "C"’.  It is unnecessary to enclose the Python
header files in ‘extern "C" {...}’ -- they use this form already if the
symbol ‘__cplusplus’ is defined (all recent C++ compilers define this
symbol).


File: python.info,  Node: Providing a C API for an Extension Module,  Prev: Writing Extensions in C++,  Up: 以 C 或 C++ 擴充 Python

6.2.1.16 Providing a C API for an Extension Module
..................................................

Many extension modules just provide new functions and types to be used
from Python, but sometimes the code in an extension module can be useful
for other extension modules.  For example, an extension module could
implement a type "collection" which works like lists without order.
Just like the standard Python list type has a C API which permits
extension modules to create and manipulate lists, this new collection
type should have a set of C functions for direct manipulation from other
extension modules.

At first sight this seems easy: just write the functions (without
declaring them ‘static’, of course), provide an appropriate header file,
and document the C API. And in fact this would work if all extension
modules were always linked statically with the Python interpreter.  When
modules are used as shared libraries, however, the symbols defined in
one module may not be visible to another module.  The details of
visibility depend on the operating system; some systems use one global
namespace for the Python interpreter and all extension modules (Windows,
for example), whereas others require an explicit list of imported
symbols at module link time (AIX is one example), or offer a choice of
different strategies (most Unices).  And even if symbols are globally
visible, the module whose functions one wishes to call might not have
been loaded yet!

Portability therefore requires not to make any assumptions about symbol
visibility.  This means that all symbols in extension modules should be
declared ‘static’, except for the module's initialization function, in
order to avoid name clashes with other extension modules (as discussed
in section *note The Module's Method Table and Initialization Function:
46d7.).  And it means that symbols that 'should' be accessible from
other extension modules must be exported in a different way.

Python provides a special mechanism to pass C-level information
(pointers) from one extension module to another one: Capsules.  A
Capsule is a Python data type which stores a pointer (void*).  Capsules
can only be created and accessed via their C API, but they can be passed
around like any other Python object.  In particular, they can be
assigned to a name in an extension module's namespace.  Other extension
modules can then import this module, retrieve the value of this name,
and then retrieve the pointer from the Capsule.

There are many ways in which Capsules can be used to export the C API of
an extension module.  Each function could get its own Capsule, or all C
API pointers could be stored in an array whose address is published in a
Capsule.  And the various tasks of storing and retrieving the pointers
can be distributed in different ways between the module providing the
code and the client modules.

Whichever method you choose, it's important to name your Capsules
properly.  The function *note PyCapsule_New(): 46f9. takes a name
parameter (const char*); you're permitted to pass in a ‘NULL’ name, but
we strongly encourage you to specify a name.  Properly named Capsules
provide a degree of runtime type-safety; there is no feasible way to
tell one unnamed Capsule from another.

In particular, Capsules used to expose C APIs should be given a name
following this convention:

     modulename.attributename

The convenience function *note PyCapsule_Import(): 1770. makes it easy
to load a C API provided via a Capsule, but only if the Capsule's name
matches this convention.  This behavior gives C API users a high degree
of certainty that the Capsule they load contains the correct C API.

The following example demonstrates an approach that puts most of the
burden on the writer of the exporting module, which is appropriate for
commonly used library modules.  It stores all C API pointers (just one
in the example!)  in an array of void pointers which becomes the value
of a Capsule.  The header file corresponding to the module provides a
macro that takes care of importing the module and retrieving its C API
pointers; client modules only have to call this macro before accessing
the C API.

The exporting module is a modification of the ‘spam’ module from section
*note 一個簡單範例: 46cf.  The function ‘spam.system()’ does not call
the C library function ‘system()’ directly, but a function
‘PySpam_System()’, which would of course do something more complicated
in reality (such as adding "spam" to every command).  This function
‘PySpam_System()’ is also exported to other extension modules.

The function ‘PySpam_System()’ is a plain C function, declared ‘static’
like everything else:

     static int
     PySpam_System(const char *command)
     {
         return system(command);
     }

The function ‘spam_system()’ is modified in a trivial way:

     static PyObject *
     spam_system(PyObject *self, PyObject *args)
     {
         const char *command;
         int sts;

         if (!PyArg_ParseTuple(args, "s", &command))
             return NULL;
         sts = PySpam_System(command);
         return PyLong_FromLong(sts);
     }

In the beginning of the module, right after the line

     #include <Python.h>

two more lines must be added:

     #define SPAM_MODULE
     #include "spammodule.h"

The ‘#define’ is used to tell the header file that it is being included
in the exporting module, not a client module.  Finally, the module's
initialization function must take care of initializing the C API pointer
array:

     PyMODINIT_FUNC
     PyInit_spam(void)
     {
         PyObject *m;
         static void *PySpam_API[PySpam_API_pointers];
         PyObject *c_api_object;

         m = PyModule_Create(&spammodule);
         if (m == NULL)
             return NULL;

         /* Initialize the C API pointer array */
         PySpam_API[PySpam_System_NUM] = (void *)PySpam_System;

         /* Create a Capsule containing the API pointer array's address */
         c_api_object = PyCapsule_New((void *)PySpam_API, "spam._C_API", NULL);

         if (PyModule_Add(m, "_C_API", c_api_object) < 0) {
             Py_DECREF(m);
             return NULL;
         }

         return m;
     }

Note that ‘PySpam_API’ is declared ‘static’; otherwise the pointer array
would disappear when ‘PyInit_spam()’ terminates!

The bulk of the work is in the header file ‘spammodule.h’, which looks
like this:

     #ifndef Py_SPAMMODULE_H
     #define Py_SPAMMODULE_H
     #ifdef __cplusplus
     extern "C" {
     #endif

     /* Header file for spammodule */

     /* C API functions */
     #define PySpam_System_NUM 0
     #define PySpam_System_RETURN int
     #define PySpam_System_PROTO (const char *command)

     /* Total number of C API pointers */
     #define PySpam_API_pointers 1


     #ifdef SPAM_MODULE
     /* This section is used when compiling spammodule.c */

     static PySpam_System_RETURN PySpam_System PySpam_System_PROTO;

     #else
     /* This section is used in modules that use spammodule's API */

     static void **PySpam_API;

     #define PySpam_System \
      (*(PySpam_System_RETURN (*)PySpam_System_PROTO) PySpam_API[PySpam_System_NUM])

     /* Return -1 on error, 0 on success.
      * PyCapsule_Import will set an exception if there's an error.
      */
     static int
     import_spam(void)
     {
         PySpam_API = (void **)PyCapsule_Import("spam._C_API", 0);
         return (PySpam_API != NULL) ? 0 : -1;
     }

     #endif

     #ifdef __cplusplus
     }
     #endif

     #endif /* !defined(Py_SPAMMODULE_H) */

All that a client module must do in order to have access to the function
‘PySpam_System()’ is to call the function (or rather macro)
‘import_spam()’ in its initialization function:

     PyMODINIT_FUNC
     PyInit_client(void)
     {
         PyObject *m;

         m = PyModule_Create(&clientmodule);
         if (m == NULL)
             return NULL;
         if (import_spam() < 0)
             return NULL;
         /* additional initialization can happen here */
         return m;
     }

The main disadvantage of this approach is that the file ‘spammodule.h’
is rather complicated.  However, the basic structure is the same for
each function that is exported, so it has to be learned only once.

Finally it should be mentioned that Capsules offer additional
functionality, which is especially useful for memory allocation and
deallocation of the pointer stored in a Capsule.  The details are
described in the Python/C API Reference Manual in the section *note
Capsules: 245e. and in the implementation of Capsules (files
‘Include/pycapsule.h’ and ‘Objects/pycapsule.c’ in the Python source
code distribution).

註解
....


File: python.info,  Node: Defining Extension Types Tutorial,  Next: Defining Extension Types Assorted Topics,  Prev: 以 C 或 C++ 擴充 Python,  Up: 不使用第三方工具建立擴充

6.2.2 Defining Extension Types: Tutorial
----------------------------------------

Python allows the writer of a C extension module to define new types
that can be manipulated from Python code, much like the built-in *note
str: 3f2. and *note list: 5b6. types.  The code for all extension types
follows a pattern, but there are some details that you need to
understand before you can get started.  This document is a gentle
introduction to the topic.

* Menu:

* The Basics::
* Adding data and methods to the Basic example::
* Providing finer control over data attributes::
* Supporting cyclic garbage collection::
* Subclassing other types::


File: python.info,  Node: The Basics,  Next: Adding data and methods to the Basic example,  Up: Defining Extension Types Tutorial

6.2.2.1 The Basics
..................

The *note CPython: 699. runtime sees all Python objects as variables of
type *note PyObject: 311.*, which serves as a "base type" for all Python
objects.  The *note PyObject: 311. structure itself only contains the
object's *note reference count: 46fe. and a pointer to the object's
"type object".  This is where the action is; the type object determines
which (C) functions get called by the interpreter when, for instance, an
attribute gets looked up on an object, a method called, or it is
multiplied by another object.  These C functions are called "type
methods".

So, if you want to define a new extension type, you need to create a new
type object.

This sort of thing can only be explained by example, so here's a
minimal, but complete, module that defines a new type named ‘Custom’
inside a C extension module ‘custom’:

     備註: What we're showing here is the traditional way of defining
     'static' extension types.  It should be adequate for most uses.
     The C API also allows defining heap-allocated extension types using
     the *note PyType_FromSpec(): 523. function, which isn't covered in
     this tutorial.

     #define PY_SSIZE_T_CLEAN
     #include <Python.h>

     typedef struct {
         PyObject_HEAD
         /* Type-specific fields go here. */
     } CustomObject;

     static PyTypeObject CustomType = {
         .ob_base = PyVarObject_HEAD_INIT(NULL, 0)
         .tp_name = "custom.Custom",
         .tp_doc = PyDoc_STR("Custom objects"),
         .tp_basicsize = sizeof(CustomObject),
         .tp_itemsize = 0,
         .tp_flags = Py_TPFLAGS_DEFAULT,
         .tp_new = PyType_GenericNew,
     };

     static PyModuleDef custommodule = {
         .m_base = PyModuleDef_HEAD_INIT,
         .m_name = "custom",
         .m_doc = "Example module that creates an extension type.",
         .m_size = -1,
     };

     PyMODINIT_FUNC
     PyInit_custom(void)
     {
         PyObject *m;
         if (PyType_Ready(&CustomType) < 0)
             return NULL;

         m = PyModule_Create(&custommodule);
         if (m == NULL)
             return NULL;

         if (PyModule_AddObjectRef(m, "Custom", (PyObject *) &CustomType) < 0) {
             Py_DECREF(m);
             return NULL;
         }

         return m;
     }

Now that's quite a bit to take in at once, but hopefully bits will seem
familiar from the previous chapter.  This file defines three things:

  1. What a ‘Custom’ 'object' contains: this is the ‘CustomObject’
     struct, which is allocated once for each ‘Custom’ instance.

  2. How the ‘Custom’ 'type' behaves: this is the ‘CustomType’ struct,
     which defines a set of flags and function pointers that the
     interpreter inspects when specific operations are requested.

  3. How to initialize the ‘custom’ module: this is the ‘PyInit_custom’
     function and the associated ‘custommodule’ struct.

The first bit is:

     typedef struct {
         PyObject_HEAD
     } CustomObject;

This is what a Custom object will contain.  ‘PyObject_HEAD’ is mandatory
at the start of each object struct and defines a field called ‘ob_base’
of type *note PyObject: 311, containing a pointer to a type object and a
reference count (these can be accessed using the macros *note Py_TYPE:
724. and *note Py_REFCNT: 84e. respectively).  The reason for the macro
is to abstract away the layout and to enable additional fields in *note
debug builds: 1de.

     備註: There is no semicolon above after the *note PyObject_HEAD:
     1271. macro.  Be wary of adding one by accident: some compilers
     will complain.

Of course, objects generally store additional data besides the standard
‘PyObject_HEAD’ boilerplate; for example, here is the definition for
standard Python floats:

     typedef struct {
         PyObject_HEAD
         double ob_fval;
     } PyFloatObject;

The second bit is the definition of the type object.

     static PyTypeObject CustomType = {
         .ob_base = PyVarObject_HEAD_INIT(NULL, 0)
         .tp_name = "custom.Custom",
         .tp_doc = PyDoc_STR("Custom objects"),
         .tp_basicsize = sizeof(CustomObject),
         .tp_itemsize = 0,
         .tp_flags = Py_TPFLAGS_DEFAULT,
         .tp_new = PyType_GenericNew,
     };

     備註: We recommend using C99-style designated initializers as
     above, to avoid listing all the *note PyTypeObject: a48. fields
     that you don't care about and also to avoid caring about the
     fields' declaration order.

The actual definition of *note PyTypeObject: a48. in ‘object.h’ has many
more *note fields: 931. than the definition above.  The remaining fields
will be filled with zeros by the C compiler, and it's common practice to
not specify them explicitly unless you need them.

We're going to pick it apart, one field at a time:

     .ob_base = PyVarObject_HEAD_INIT(NULL, 0)

This line is mandatory boilerplate to initialize the ‘ob_base’ field
mentioned above.

     .tp_name = "custom.Custom",

The name of our type.  This will appear in the default textual
representation of our objects and in some error messages, for example:

     >>> "" + custom.Custom()
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: can only concatenate str (not "custom.Custom") to str

Note that the name is a dotted name that includes both the module name
and the name of the type within the module.  The module in this case is
‘custom’ and the type is ‘Custom’, so we set the type name to
‘custom.Custom’.  Using the real dotted import path is important to make
your type compatible with the *note pydoc: a3. and *note pickle: 95.
modules.

     .tp_basicsize = sizeof(CustomObject),
     .tp_itemsize = 0,

This is so that Python knows how much memory to allocate when creating
new ‘Custom’ instances.  *note tp_itemsize: 1e46. is only used for
variable-sized objects and should otherwise be zero.

     備註: If you want your type to be subclassable from Python, and
     your type has the same *note tp_basicsize: 92b. as its base type,
     you may have problems with multiple inheritance.  A Python subclass
     of your type will have to list your type first in its *note
     __bases__: 1417, or else it will not be able to call your type's
     *note __new__(): 526. method without getting an error.  You can
     avoid this problem by ensuring that your type has a larger value
     for *note tp_basicsize: 92b. than its base type does.  Most of the
     time, this will be true anyway, because either your base type will
     be *note object: a2f, or else you will be adding data members to
     your base type, and therefore increasing its size.

We set the class flags to *note Py_TPFLAGS_DEFAULT: 46ff.

     .tp_flags = Py_TPFLAGS_DEFAULT,

All types should include this constant in their flags.  It enables all
of the members defined until at least Python 3.3.  If you need further
members, you will need to OR the corresponding flags.

We provide a doc string for the type in *note tp_doc: 4700.

     .tp_doc = PyDoc_STR("Custom objects"),

To enable object creation, we have to provide a *note tp_new: 525.
handler.  This is the equivalent of the Python method *note __new__():
526, but has to be specified explicitly.  In this case, we can just use
the default implementation provided by the API function *note
PyType_GenericNew(): 4701.

     .tp_new = PyType_GenericNew,

Everything else in the file should be familiar, except for some code in
‘PyInit_custom()’:

     if (PyType_Ready(&CustomType) < 0)
         return;

This initializes the ‘Custom’ type, filling in a number of members to
the appropriate default values, including *note ob_type: 4702. that we
initially set to ‘NULL’.

     if (PyModule_AddObjectRef(m, "Custom", (PyObject *) &CustomType) < 0) {
         Py_DECREF(m);
         return NULL;
     }

This adds the type to the module dictionary.  This allows us to create
‘Custom’ instances by calling the ‘Custom’ class:

     >>> import custom
     >>> mycustom = custom.Custom()

That's it!  All that remains is to build it; put the above code in a
file called ‘custom.c’,

     [build-system]
     requires = ["setuptools"]
     build-backend = "setuptools.build_meta"

     [project]
     name = "custom"
     version = "1"

in a file called ‘pyproject.toml’, and

     from setuptools import Extension, setup
     setup(ext_modules=[Extension("custom", ["custom.c"])])

in a file called ‘setup.py’; then typing

     $ python -m pip install .

in a shell should produce a file ‘custom.so’ in a subdirectory and
install it; now fire up Python -- you should be able to ‘import custom’
and play around with ‘Custom’ objects.

That wasn't so hard, was it?

Of course, the current Custom type is pretty uninteresting.  It has no
data and doesn't do anything.  It can't even be subclassed.


File: python.info,  Node: Adding data and methods to the Basic example,  Next: Providing finer control over data attributes,  Prev: The Basics,  Up: Defining Extension Types Tutorial

6.2.2.2 Adding data and methods to the Basic example
....................................................

Let's extend the basic example to add some data and methods.  Let's also
make the type usable as a base class.  We'll create a new module,
‘custom2’ that adds these capabilities:

     #define PY_SSIZE_T_CLEAN
     #include <Python.h>
     #include <stddef.h> /* for offsetof() */

     typedef struct {
         PyObject_HEAD
         PyObject *first; /* first name */
         PyObject *last;  /* last name */
         int number;
     } CustomObject;

     static void
     Custom_dealloc(CustomObject *self)
     {
         Py_XDECREF(self->first);
         Py_XDECREF(self->last);
         Py_TYPE(self)->tp_free((PyObject *) self);
     }

     static PyObject *
     Custom_new(PyTypeObject *type, PyObject *args, PyObject *kwds)
     {
         CustomObject *self;
         self = (CustomObject *) type->tp_alloc(type, 0);
         if (self != NULL) {
             self->first = PyUnicode_FromString("");
             if (self->first == NULL) {
                 Py_DECREF(self);
                 return NULL;
             }
             self->last = PyUnicode_FromString("");
             if (self->last == NULL) {
                 Py_DECREF(self);
                 return NULL;
             }
             self->number = 0;
         }
         return (PyObject *) self;
     }

     static int
     Custom_init(CustomObject *self, PyObject *args, PyObject *kwds)
     {
         static char *kwlist[] = {"first", "last", "number", NULL};
         PyObject *first = NULL, *last = NULL;

         if (!PyArg_ParseTupleAndKeywords(args, kwds, "|OOi", kwlist,
                                          &first, &last,
                                          &self->number))
             return -1;

         if (first) {
             Py_XSETREF(self->first, Py_NewRef(first));
         }
         if (last) {
             Py_XSETREF(self->last, Py_NewRef(last));
         }
         return 0;
     }

     static PyMemberDef Custom_members[] = {
         {"first", Py_T_OBJECT_EX, offsetof(CustomObject, first), 0,
          "first name"},
         {"last", Py_T_OBJECT_EX, offsetof(CustomObject, last), 0,
          "last name"},
         {"number", Py_T_INT, offsetof(CustomObject, number), 0,
          "custom number"},
         {NULL}  /* Sentinel */
     };

     static PyObject *
     Custom_name(CustomObject *self, PyObject *Py_UNUSED(ignored))
     {
         if (self->first == NULL) {
             PyErr_SetString(PyExc_AttributeError, "first");
             return NULL;
         }
         if (self->last == NULL) {
             PyErr_SetString(PyExc_AttributeError, "last");
             return NULL;
         }
         return PyUnicode_FromFormat("%S %S", self->first, self->last);
     }

     static PyMethodDef Custom_methods[] = {
         {"name", (PyCFunction) Custom_name, METH_NOARGS,
          "Return the name, combining the first and last name"
         },
         {NULL}  /* Sentinel */
     };

     static PyTypeObject CustomType = {
         .ob_base = PyVarObject_HEAD_INIT(NULL, 0)
         .tp_name = "custom2.Custom",
         .tp_doc = PyDoc_STR("Custom objects"),
         .tp_basicsize = sizeof(CustomObject),
         .tp_itemsize = 0,
         .tp_flags = Py_TPFLAGS_DEFAULT | Py_TPFLAGS_BASETYPE,
         .tp_new = Custom_new,
         .tp_init = (initproc) Custom_init,
         .tp_dealloc = (destructor) Custom_dealloc,
         .tp_members = Custom_members,
         .tp_methods = Custom_methods,
     };

     static PyModuleDef custommodule = {
         .m_base =PyModuleDef_HEAD_INIT,
         .m_name = "custom2",
         .m_doc = "Example module that creates an extension type.",
         .m_size = -1,
     };

     PyMODINIT_FUNC
     PyInit_custom2(void)
     {
         PyObject *m;
         if (PyType_Ready(&CustomType) < 0)
             return NULL;

         m = PyModule_Create(&custommodule);
         if (m == NULL)
             return NULL;

         if (PyModule_AddObjectRef(m, "Custom", (PyObject *) &CustomType) < 0) {
             Py_DECREF(m);
             return NULL;
         }

         return m;
     }

This version of the module has a number of changes.

The ‘Custom’ type now has three data attributes in its C struct,
'first', 'last', and 'number'.  The 'first' and 'last' variables are
Python strings containing first and last names.  The 'number' attribute
is a C integer.

The object structure is updated accordingly:

     typedef struct {
         PyObject_HEAD
         PyObject *first; /* first name */
         PyObject *last;  /* last name */
         int number;
     } CustomObject;

Because we now have data to manage, we have to be more careful about
object allocation and deallocation.  At a minimum, we need a
deallocation method:

     static void
     Custom_dealloc(CustomObject *self)
     {
         Py_XDECREF(self->first);
         Py_XDECREF(self->last);
         Py_TYPE(self)->tp_free((PyObject *) self);
     }

which is assigned to the *note tp_dealloc: 4704. member:

     .tp_dealloc = (destructor) Custom_dealloc,

This method first clears the reference counts of the two Python
attributes.  *note Py_XDECREF(): 733. correctly handles the case where
its argument is ‘NULL’ (which might happen here if ‘tp_new’ failed
midway).  It then calls the *note tp_free: 4705. member of the object's
type (computed by ‘Py_TYPE(self)’) to free the object's memory.  Note
that the object's type might not be ‘CustomType’, because the object may
be an instance of a subclass.

     備註: The explicit cast to ‘destructor’ above is needed because we
     defined ‘Custom_dealloc’ to take a ‘CustomObject *’ argument, but
     the ‘tp_dealloc’ function pointer expects to receive a ‘PyObject *’
     argument.  Otherwise, the compiler will emit a warning.  This is
     object-oriented polymorphism, in C!

We want to make sure that the first and last names are initialized to
empty strings, so we provide a ‘tp_new’ implementation:

     static PyObject *
     Custom_new(PyTypeObject *type, PyObject *args, PyObject *kwds)
     {
         CustomObject *self;
         self = (CustomObject *) type->tp_alloc(type, 0);
         if (self != NULL) {
             self->first = PyUnicode_FromString("");
             if (self->first == NULL) {
                 Py_DECREF(self);
                 return NULL;
             }
             self->last = PyUnicode_FromString("");
             if (self->last == NULL) {
                 Py_DECREF(self);
                 return NULL;
             }
             self->number = 0;
         }
         return (PyObject *) self;
     }

and install it in the *note tp_new: 525. member:

     .tp_new = Custom_new,

The ‘tp_new’ handler is responsible for creating (as opposed to
initializing) objects of the type.  It is exposed in Python as the *note
__new__(): 526. method.  It is not required to define a ‘tp_new’ member,
and indeed many extension types will simply reuse *note
PyType_GenericNew(): 4701. as done in the first version of the ‘Custom’
type above.  In this case, we use the ‘tp_new’ handler to initialize the
‘first’ and ‘last’ attributes to non-‘NULL’ default values.

‘tp_new’ is passed the type being instantiated (not necessarily
‘CustomType’, if a subclass is instantiated) and any arguments passed
when the type was called, and is expected to return the instance
created.  ‘tp_new’ handlers always accept positional and keyword
arguments, but they often ignore the arguments, leaving the argument
handling to initializer (a.k.a.  ‘tp_init’ in C or ‘__init__’ in Python)
methods.

     備註: ‘tp_new’ shouldn't call ‘tp_init’ explicitly, as the
     interpreter will do it itself.

The ‘tp_new’ implementation calls the *note tp_alloc: 4706. slot to
allocate memory:

     self = (CustomObject *) type->tp_alloc(type, 0);

Since memory allocation may fail, we must check the *note tp_alloc:
4706. result against ‘NULL’ before proceeding.

     備註: We didn't fill the *note tp_alloc: 4706. slot ourselves.
     Rather *note PyType_Ready(): 722. fills it for us by inheriting it
     from our base class, which is *note object: a2f. by default.  Most
     types use the default allocation strategy.

     備註: If you are creating a co-operative *note tp_new: 525. (one
     that calls a base type's *note tp_new: 525. or *note __new__():
     526.), you must 'not' try to determine what method to call using
     method resolution order at runtime.  Always statically determine
     what type you are going to call, and call its *note tp_new: 525.
     directly, or via ‘type->tp_base->tp_new’.  If you do not do this,
     Python subclasses of your type that also inherit from other
     Python-defined classes may not work correctly.  (Specifically, you
     may not be able to create instances of such subclasses without
     getting a *note TypeError: 4dd.)

We also define an initialization function which accepts arguments to
provide initial values for our instance:

     static int
     Custom_init(CustomObject *self, PyObject *args, PyObject *kwds)
     {
         static char *kwlist[] = {"first", "last", "number", NULL};
         PyObject *first = NULL, *last = NULL, *tmp;

         if (!PyArg_ParseTupleAndKeywords(args, kwds, "|OOi", kwlist,
                                          &first, &last,
                                          &self->number))
             return -1;

         if (first) {
             tmp = self->first;
             Py_INCREF(first);
             self->first = first;
             Py_XDECREF(tmp);
         }
         if (last) {
             tmp = self->last;
             Py_INCREF(last);
             self->last = last;
             Py_XDECREF(tmp);
         }
         return 0;
     }

by filling the *note tp_init: 527. slot.

     .tp_init = (initproc) Custom_init,

The *note tp_init: 527. slot is exposed in Python as the *note
__init__(): 655. method.  It is used to initialize an object after it's
created.  Initializers always accept positional and keyword arguments,
and they should return either ‘0’ on success or ‘-1’ on error.

Unlike the ‘tp_new’ handler, there is no guarantee that ‘tp_init’ is
called at all (for example, the *note pickle: 95. module by default
doesn't call *note __init__(): 655. on unpickled instances).  It can
also be called multiple times.  Anyone can call the ‘__init__()’ method
on our objects.  For this reason, we have to be extra careful when
assigning the new attribute values.  We might be tempted, for example to
assign the ‘first’ member like this:

     if (first) {
         Py_XDECREF(self->first);
         Py_INCREF(first);
         self->first = first;
     }

But this would be risky.  Our type doesn't restrict the type of the
‘first’ member, so it could be any kind of object.  It could have a
destructor that causes code to be executed that tries to access the
‘first’ member; or that destructor could release the *note Global
interpreter Lock: 13e. and let arbitrary code run in other threads that
accesses and modifies our object.

To be paranoid and protect ourselves against this possibility, we almost
always reassign members before decrementing their reference counts.
When don't we have to do this?

   * when we absolutely know that the reference count is greater than 1;

   * when we know that deallocation of the object (1) will neither
     release the *note GIL: 13e. nor cause any calls back into our
     type's code;

   * when decrementing a reference count in a *note tp_dealloc: 4704.
     handler on a type which doesn't support cyclic garbage collection
     (2).

We want to expose our instance variables as attributes.  There are a
number of ways to do that.  The simplest way is to define member
definitions:

     static PyMemberDef Custom_members[] = {
         {"first", Py_T_OBJECT_EX, offsetof(CustomObject, first), 0,
          "first name"},
         {"last", Py_T_OBJECT_EX, offsetof(CustomObject, last), 0,
          "last name"},
         {"number", Py_T_INT, offsetof(CustomObject, number), 0,
          "custom number"},
         {NULL}  /* Sentinel */
     };

and put the definitions in the *note tp_members: 4707. slot:

     .tp_members = Custom_members,

Each member definition has a member name, type, offset, access flags and
documentation string.  See the *note Generic Attribute Management: 4708.
section below for details.

A disadvantage of this approach is that it doesn't provide a way to
restrict the types of objects that can be assigned to the Python
attributes.  We expect the first and last names to be strings, but any
Python objects can be assigned.  Further, the attributes can be deleted,
setting the C pointers to ‘NULL’.  Even though we can make sure the
members are initialized to non-‘NULL’ values, the members can be set to
‘NULL’ if the attributes are deleted.

We define a single method, ‘Custom.name()’, that outputs the objects
name as the concatenation of the first and last names.

     static PyObject *
     Custom_name(CustomObject *self, PyObject *Py_UNUSED(ignored))
     {
         if (self->first == NULL) {
             PyErr_SetString(PyExc_AttributeError, "first");
             return NULL;
         }
         if (self->last == NULL) {
             PyErr_SetString(PyExc_AttributeError, "last");
             return NULL;
         }
         return PyUnicode_FromFormat("%S %S", self->first, self->last);
     }

The method is implemented as a C function that takes a ‘Custom’ (or
‘Custom’ subclass) instance as the first argument.  Methods always take
an instance as the first argument.  Methods often take positional and
keyword arguments as well, but in this case we don't take any and don't
need to accept a positional argument tuple or keyword argument
dictionary.  This method is equivalent to the Python method:

     def name(self):
         return "%s %s" % (self.first, self.last)

Note that we have to check for the possibility that our ‘first’ and
‘last’ members are ‘NULL’.  This is because they can be deleted, in
which case they are set to ‘NULL’.  It would be better to prevent
deletion of these attributes and to restrict the attribute values to be
strings.  We'll see how to do that in the next section.

Now that we've defined the method, we need to create an array of method
definitions:

     static PyMethodDef Custom_methods[] = {
         {"name", (PyCFunction) Custom_name, METH_NOARGS,
          "Return the name, combining the first and last name"
         },
         {NULL}  /* Sentinel */
     };

(note that we used the *note METH_NOARGS: 1443. flag to indicate that
the method is expecting no arguments other than 'self')

and assign it to the *note tp_methods: 4709. slot:

     .tp_methods = Custom_methods,

Finally, we'll make our type usable as a base class for subclassing.
We've written our methods carefully so far so that they don't make any
assumptions about the type of the object being created or used, so all
we need to do is to add the *note Py_TPFLAGS_BASETYPE: 470a. to our
class flag definition:

     .tp_flags = Py_TPFLAGS_DEFAULT | Py_TPFLAGS_BASETYPE,

We rename ‘PyInit_custom()’ to ‘PyInit_custom2()’, update the module
name in the *note PyModuleDef: 921. struct, and update the full class
name in the *note PyTypeObject: a48. struct.

Finally, we update our ‘setup.py’ file to include the new module,

     from setuptools import Extension, setup
     setup(ext_modules=[
         Extension("custom", ["custom.c"]),
         Extension("custom2", ["custom2.c"]),
     ])

and then we re-install so that we can ‘import custom2’:

     $ python -m pip install .

   ---------- Footnotes ----------

   (1) This is true when we know that the object is a basic type, like a
string or a float.

   (2) We relied on this in the *note tp_dealloc: 4704. handler in this
example, because our type doesn't support garbage collection.


File: python.info,  Node: Providing finer control over data attributes,  Next: Supporting cyclic garbage collection,  Prev: Adding data and methods to the Basic example,  Up: Defining Extension Types Tutorial

6.2.2.3 Providing finer control over data attributes
....................................................

In this section, we'll provide finer control over how the ‘first’ and
‘last’ attributes are set in the ‘Custom’ example.  In the previous
version of our module, the instance variables ‘first’ and ‘last’ could
be set to non-string values or even deleted.  We want to make sure that
these attributes always contain strings.

     #define PY_SSIZE_T_CLEAN
     #include <Python.h>
     #include <stddef.h> /* for offsetof() */

     typedef struct {
         PyObject_HEAD
         PyObject *first; /* first name */
         PyObject *last;  /* last name */
         int number;
     } CustomObject;

     static void
     Custom_dealloc(CustomObject *self)
     {
         Py_XDECREF(self->first);
         Py_XDECREF(self->last);
         Py_TYPE(self)->tp_free((PyObject *) self);
     }

     static PyObject *
     Custom_new(PyTypeObject *type, PyObject *args, PyObject *kwds)
     {
         CustomObject *self;
         self = (CustomObject *) type->tp_alloc(type, 0);
         if (self != NULL) {
             self->first = PyUnicode_FromString("");
             if (self->first == NULL) {
                 Py_DECREF(self);
                 return NULL;
             }
             self->last = PyUnicode_FromString("");
             if (self->last == NULL) {
                 Py_DECREF(self);
                 return NULL;
             }
             self->number = 0;
         }
         return (PyObject *) self;
     }

     static int
     Custom_init(CustomObject *self, PyObject *args, PyObject *kwds)
     {
         static char *kwlist[] = {"first", "last", "number", NULL};
         PyObject *first = NULL, *last = NULL;

         if (!PyArg_ParseTupleAndKeywords(args, kwds, "|UUi", kwlist,
                                          &first, &last,
                                          &self->number))
             return -1;

         if (first) {
             Py_SETREF(self->first, Py_NewRef(first));
         }
         if (last) {
             Py_SETREF(self->last, Py_NewRef(last));
         }
         return 0;
     }

     static PyMemberDef Custom_members[] = {
         {"number", Py_T_INT, offsetof(CustomObject, number), 0,
          "custom number"},
         {NULL}  /* Sentinel */
     };

     static PyObject *
     Custom_getfirst(CustomObject *self, void *closure)
     {
         return Py_NewRef(self->first);
     }

     static int
     Custom_setfirst(CustomObject *self, PyObject *value, void *closure)
     {
         if (value == NULL) {
             PyErr_SetString(PyExc_TypeError, "Cannot delete the first attribute");
             return -1;
         }
         if (!PyUnicode_Check(value)) {
             PyErr_SetString(PyExc_TypeError,
                             "The first attribute value must be a string");
             return -1;
         }
         Py_SETREF(self->first, Py_NewRef(value));
         return 0;
     }

     static PyObject *
     Custom_getlast(CustomObject *self, void *closure)
     {
         return Py_NewRef(self->last);
     }

     static int
     Custom_setlast(CustomObject *self, PyObject *value, void *closure)
     {
         if (value == NULL) {
             PyErr_SetString(PyExc_TypeError, "Cannot delete the last attribute");
             return -1;
         }
         if (!PyUnicode_Check(value)) {
             PyErr_SetString(PyExc_TypeError,
                             "The last attribute value must be a string");
             return -1;
         }
         Py_SETREF(self->last, Py_NewRef(value));
         return 0;
     }

     static PyGetSetDef Custom_getsetters[] = {
         {"first", (getter) Custom_getfirst, (setter) Custom_setfirst,
          "first name", NULL},
         {"last", (getter) Custom_getlast, (setter) Custom_setlast,
          "last name", NULL},
         {NULL}  /* Sentinel */
     };

     static PyObject *
     Custom_name(CustomObject *self, PyObject *Py_UNUSED(ignored))
     {
         return PyUnicode_FromFormat("%S %S", self->first, self->last);
     }

     static PyMethodDef Custom_methods[] = {
         {"name", (PyCFunction) Custom_name, METH_NOARGS,
          "Return the name, combining the first and last name"
         },
         {NULL}  /* Sentinel */
     };

     static PyTypeObject CustomType = {
         .ob_base = PyVarObject_HEAD_INIT(NULL, 0)
         .tp_name = "custom3.Custom",
         .tp_doc = PyDoc_STR("Custom objects"),
         .tp_basicsize = sizeof(CustomObject),
         .tp_itemsize = 0,
         .tp_flags = Py_TPFLAGS_DEFAULT | Py_TPFLAGS_BASETYPE,
         .tp_new = Custom_new,
         .tp_init = (initproc) Custom_init,
         .tp_dealloc = (destructor) Custom_dealloc,
         .tp_members = Custom_members,
         .tp_methods = Custom_methods,
         .tp_getset = Custom_getsetters,
     };

     static PyModuleDef custommodule = {
         .m_base = PyModuleDef_HEAD_INIT,
         .m_name = "custom3",
         .m_doc = "Example module that creates an extension type.",
         .m_size = -1,
     };

     PyMODINIT_FUNC
     PyInit_custom3(void)
     {
         PyObject *m;
         if (PyType_Ready(&CustomType) < 0)
             return NULL;

         m = PyModule_Create(&custommodule);
         if (m == NULL)
             return NULL;

         if (PyModule_AddObjectRef(m, "Custom", (PyObject *) &CustomType) < 0) {
             Py_DECREF(m);
             return NULL;
         }

         return m;
     }

To provide greater control, over the ‘first’ and ‘last’ attributes,
we'll use custom getter and setter functions.  Here are the functions
for getting and setting the ‘first’ attribute:

     static PyObject *
     Custom_getfirst(CustomObject *self, void *closure)
     {
         Py_INCREF(self->first);
         return self->first;
     }

     static int
     Custom_setfirst(CustomObject *self, PyObject *value, void *closure)
     {
         PyObject *tmp;
         if (value == NULL) {
             PyErr_SetString(PyExc_TypeError, "Cannot delete the first attribute");
             return -1;
         }
         if (!PyUnicode_Check(value)) {
             PyErr_SetString(PyExc_TypeError,
                             "The first attribute value must be a string");
             return -1;
         }
         tmp = self->first;
         Py_INCREF(value);
         self->first = value;
         Py_DECREF(tmp);
         return 0;
     }

The getter function is passed a ‘Custom’ object and a "closure", which
is a void pointer.  In this case, the closure is ignored.  (The closure
supports an advanced usage in which definition data is passed to the
getter and setter.  This could, for example, be used to allow a single
set of getter and setter functions that decide the attribute to get or
set based on data in the closure.)

The setter function is passed the ‘Custom’ object, the new value, and
the closure.  The new value may be ‘NULL’, in which case the attribute
is being deleted.  In our setter, we raise an error if the attribute is
deleted or if its new value is not a string.

We create an array of *note PyGetSetDef: b5f. structures:

     static PyGetSetDef Custom_getsetters[] = {
         {"first", (getter) Custom_getfirst, (setter) Custom_setfirst,
          "first name", NULL},
         {"last", (getter) Custom_getlast, (setter) Custom_setlast,
          "last name", NULL},
         {NULL}  /* Sentinel */
     };

and register it in the *note tp_getset: 470c. slot:

     .tp_getset = Custom_getsetters,

The last item in a *note PyGetSetDef: b5f. structure is the "closure"
mentioned above.  In this case, we aren't using a closure, so we just
pass ‘NULL’.

We also remove the member definitions for these attributes:

     static PyMemberDef Custom_members[] = {
         {"number", Py_T_INT, offsetof(CustomObject, number), 0,
          "custom number"},
         {NULL}  /* Sentinel */
     };

We also need to update the *note tp_init: 527. handler to only allow
strings (1) to be passed:

     static int
     Custom_init(CustomObject *self, PyObject *args, PyObject *kwds)
     {
         static char *kwlist[] = {"first", "last", "number", NULL};
         PyObject *first = NULL, *last = NULL, *tmp;

         if (!PyArg_ParseTupleAndKeywords(args, kwds, "|UUi", kwlist,
                                          &first, &last,
                                          &self->number))
             return -1;

         if (first) {
             tmp = self->first;
             Py_INCREF(first);
             self->first = first;
             Py_DECREF(tmp);
         }
         if (last) {
             tmp = self->last;
             Py_INCREF(last);
             self->last = last;
             Py_DECREF(tmp);
         }
         return 0;
     }

With these changes, we can assure that the ‘first’ and ‘last’ members
are never ‘NULL’ so we can remove checks for ‘NULL’ values in almost all
cases.  This means that most of the *note Py_XDECREF(): 733. calls can
be converted to *note Py_DECREF(): 515. calls.  The only place we can't
change these calls is in the ‘tp_dealloc’ implementation, where there is
the possibility that the initialization of these members failed in
‘tp_new’.

We also rename the module initialization function and module name in the
initialization function, as we did before, and we add an extra
definition to the ‘setup.py’ file.

   ---------- Footnotes ----------

   (1) We now know that the first and last members are strings, so
perhaps we could be less careful about decrementing their reference
counts, however, we accept instances of string subclasses.  Even though
deallocating normal strings won't call back into our objects, we can't
guarantee that deallocating an instance of a string subclass won't call
back into our objects.


File: python.info,  Node: Supporting cyclic garbage collection,  Next: Subclassing other types,  Prev: Providing finer control over data attributes,  Up: Defining Extension Types Tutorial

6.2.2.4 Supporting cyclic garbage collection
............................................

Python has a *note cyclic garbage collector (GC): 181c. that can
identify unneeded objects even when their reference counts are not zero.
This can happen when objects are involved in cycles.  For example,
consider:

     >>> l = []
     >>> l.append(l)
     >>> del l

In this example, we create a list that contains itself.  When we delete
it, it still has a reference from itself.  Its reference count doesn't
drop to zero.  Fortunately, Python's cyclic garbage collector will
eventually figure out that the list is garbage and free it.

In the second version of the ‘Custom’ example, we allowed any kind of
object to be stored in the ‘first’ or ‘last’ attributes (1).  Besides,
in the second and third versions, we allowed subclassing ‘Custom’, and
subclasses may add arbitrary attributes.  For any of those two reasons,
‘Custom’ objects can participate in cycles:

     >>> import custom3
     >>> class Derived(custom3.Custom): pass
     ...
     >>> n = Derived()
     >>> n.some_attribute = n

To allow a ‘Custom’ instance participating in a reference cycle to be
properly detected and collected by the cyclic GC, our ‘Custom’ type
needs to fill two additional slots and to enable a flag that enables
these slots:

     #define PY_SSIZE_T_CLEAN
     #include <Python.h>
     #include <stddef.h> /* for offsetof() */

     typedef struct {
         PyObject_HEAD
         PyObject *first; /* first name */
         PyObject *last;  /* last name */
         int number;
     } CustomObject;

     static int
     Custom_traverse(CustomObject *self, visitproc visit, void *arg)
     {
         Py_VISIT(self->first);
         Py_VISIT(self->last);
         return 0;
     }

     static int
     Custom_clear(CustomObject *self)
     {
         Py_CLEAR(self->first);
         Py_CLEAR(self->last);
         return 0;
     }

     static void
     Custom_dealloc(CustomObject *self)
     {
         PyObject_GC_UnTrack(self);
         Custom_clear(self);
         Py_TYPE(self)->tp_free((PyObject *) self);
     }

     static PyObject *
     Custom_new(PyTypeObject *type, PyObject *args, PyObject *kwds)
     {
         CustomObject *self;
         self = (CustomObject *) type->tp_alloc(type, 0);
         if (self != NULL) {
             self->first = PyUnicode_FromString("");
             if (self->first == NULL) {
                 Py_DECREF(self);
                 return NULL;
             }
             self->last = PyUnicode_FromString("");
             if (self->last == NULL) {
                 Py_DECREF(self);
                 return NULL;
             }
             self->number = 0;
         }
         return (PyObject *) self;
     }

     static int
     Custom_init(CustomObject *self, PyObject *args, PyObject *kwds)
     {
         static char *kwlist[] = {"first", "last", "number", NULL};
         PyObject *first = NULL, *last = NULL;

         if (!PyArg_ParseTupleAndKeywords(args, kwds, "|UUi", kwlist,
                                          &first, &last,
                                          &self->number))
             return -1;

         if (first) {
             Py_SETREF(self->first, Py_NewRef(first));
         }
         if (last) {
             Py_SETREF(self->last, Py_NewRef(last));
         }
         return 0;
     }

     static PyMemberDef Custom_members[] = {
         {"number", Py_T_INT, offsetof(CustomObject, number), 0,
          "custom number"},
         {NULL}  /* Sentinel */
     };

     static PyObject *
     Custom_getfirst(CustomObject *self, void *closure)
     {
         return Py_NewRef(self->first);
     }

     static int
     Custom_setfirst(CustomObject *self, PyObject *value, void *closure)
     {
         if (value == NULL) {
             PyErr_SetString(PyExc_TypeError, "Cannot delete the first attribute");
             return -1;
         }
         if (!PyUnicode_Check(value)) {
             PyErr_SetString(PyExc_TypeError,
                             "The first attribute value must be a string");
             return -1;
         }
         Py_XSETREF(self->first, Py_NewRef(value));
         return 0;
     }

     static PyObject *
     Custom_getlast(CustomObject *self, void *closure)
     {
         return Py_NewRef(self->last);
     }

     static int
     Custom_setlast(CustomObject *self, PyObject *value, void *closure)
     {
         if (value == NULL) {
             PyErr_SetString(PyExc_TypeError, "Cannot delete the last attribute");
             return -1;
         }
         if (!PyUnicode_Check(value)) {
             PyErr_SetString(PyExc_TypeError,
                             "The last attribute value must be a string");
             return -1;
         }
         Py_XSETREF(self->last, Py_NewRef(value));
         return 0;
     }

     static PyGetSetDef Custom_getsetters[] = {
         {"first", (getter) Custom_getfirst, (setter) Custom_setfirst,
          "first name", NULL},
         {"last", (getter) Custom_getlast, (setter) Custom_setlast,
          "last name", NULL},
         {NULL}  /* Sentinel */
     };

     static PyObject *
     Custom_name(CustomObject *self, PyObject *Py_UNUSED(ignored))
     {
         return PyUnicode_FromFormat("%S %S", self->first, self->last);
     }

     static PyMethodDef Custom_methods[] = {
         {"name", (PyCFunction) Custom_name, METH_NOARGS,
          "Return the name, combining the first and last name"
         },
         {NULL}  /* Sentinel */
     };

     static PyTypeObject CustomType = {
         .ob_base = PyVarObject_HEAD_INIT(NULL, 0)
         .tp_name = "custom4.Custom",
         .tp_doc = PyDoc_STR("Custom objects"),
         .tp_basicsize = sizeof(CustomObject),
         .tp_itemsize = 0,
         .tp_flags = Py_TPFLAGS_DEFAULT | Py_TPFLAGS_BASETYPE | Py_TPFLAGS_HAVE_GC,
         .tp_new = Custom_new,
         .tp_init = (initproc) Custom_init,
         .tp_dealloc = (destructor) Custom_dealloc,
         .tp_traverse = (traverseproc) Custom_traverse,
         .tp_clear = (inquiry) Custom_clear,
         .tp_members = Custom_members,
         .tp_methods = Custom_methods,
         .tp_getset = Custom_getsetters,
     };

     static PyModuleDef custommodule = {
         .m_base = PyModuleDef_HEAD_INIT,
         .m_name = "custom4",
         .m_doc = "Example module that creates an extension type.",
         .m_size = -1,
     };

     PyMODINIT_FUNC
     PyInit_custom4(void)
     {
         PyObject *m;
         if (PyType_Ready(&CustomType) < 0)
             return NULL;

         m = PyModule_Create(&custommodule);
         if (m == NULL)
             return NULL;

         if (PyModule_AddObjectRef(m, "Custom", (PyObject *) &CustomType) < 0) {
             Py_DECREF(m);
             return NULL;
         }

         return m;
     }

First, the traversal method lets the cyclic GC know about subobjects
that could participate in cycles:

     static int
     Custom_traverse(CustomObject *self, visitproc visit, void *arg)
     {
         int vret;
         if (self->first) {
             vret = visit(self->first, arg);
             if (vret != 0)
                 return vret;
         }
         if (self->last) {
             vret = visit(self->last, arg);
             if (vret != 0)
                 return vret;
         }
         return 0;
     }

For each subobject that can participate in cycles, we need to call the
‘visit()’ function, which is passed to the traversal method.  The
‘visit()’ function takes as arguments the subobject and the extra
argument 'arg' passed to the traversal method.  It returns an integer
value that must be returned if it is non-zero.

Python provides a *note Py_VISIT(): 470e. macro that automates calling
visit functions.  With *note Py_VISIT(): 470e, we can minimize the
amount of boilerplate in ‘Custom_traverse’:

     static int
     Custom_traverse(CustomObject *self, visitproc visit, void *arg)
     {
         Py_VISIT(self->first);
         Py_VISIT(self->last);
         return 0;
     }

     備註: The *note tp_traverse: 721. implementation must name its
     arguments exactly 'visit' and 'arg' in order to use *note
     Py_VISIT(): 470e.

Second, we need to provide a method for clearing any subobjects that can
participate in cycles:

     static int
     Custom_clear(CustomObject *self)
     {
         Py_CLEAR(self->first);
         Py_CLEAR(self->last);
         return 0;
     }

Notice the use of the *note Py_CLEAR(): 51e. macro.  It is the
recommended and safe way to clear data attributes of arbitrary types
while decrementing their reference counts.  If you were to call *note
Py_XDECREF(): 733. instead on the attribute before setting it to ‘NULL’,
there is a possibility that the attribute's destructor would call back
into code that reads the attribute again ('especially' if there is a
reference cycle).

     備註: You could emulate *note Py_CLEAR(): 51e. by writing:

          PyObject *tmp;
          tmp = self->first;
          self->first = NULL;
          Py_XDECREF(tmp);

     Nevertheless, it is much easier and less error-prone to always use
     *note Py_CLEAR(): 51e. when deleting an attribute.  Don't try to
     micro-optimize at the expense of robustness!

The deallocator ‘Custom_dealloc’ may call arbitrary code when clearing
attributes.  It means the circular GC can be triggered inside the
function.  Since the GC assumes reference count is not zero, we need to
untrack the object from the GC by calling *note PyObject_GC_UnTrack():
1475. before clearing members.  Here is our reimplemented deallocator
using *note PyObject_GC_UnTrack(): 1475. and ‘Custom_clear’:

     static void
     Custom_dealloc(CustomObject *self)
     {
         PyObject_GC_UnTrack(self);
         Custom_clear(self);
         Py_TYPE(self)->tp_free((PyObject *) self);
     }

Finally, we add the *note Py_TPFLAGS_HAVE_GC: 720. flag to the class
flags:

     .tp_flags = Py_TPFLAGS_DEFAULT | Py_TPFLAGS_BASETYPE | Py_TPFLAGS_HAVE_GC,

That's pretty much it.  If we had written custom *note tp_alloc: 4706.
or *note tp_free: 4705. handlers, we'd need to modify them for cyclic
garbage collection.  Most extensions will use the versions automatically
provided.

   ---------- Footnotes ----------

   (1) Also, even with our attributes restricted to strings instances,
the user could pass arbitrary *note str: 3f2. subclasses and therefore
still create reference cycles.


File: python.info,  Node: Subclassing other types,  Prev: Supporting cyclic garbage collection,  Up: Defining Extension Types Tutorial

6.2.2.5 Subclassing other types
...............................

It is possible to create new extension types that are derived from
existing types.  It is easiest to inherit from the built in types, since
an extension can easily use the *note PyTypeObject: a48. it needs.  It
can be difficult to share these *note PyTypeObject: a48. structures
between extension modules.

In this example we will create a ‘SubList’ type that inherits from the
built-in *note list: 5b6. type.  The new type will be completely
compatible with regular lists, but will have an additional ‘increment()’
method that increases an internal counter:

     >>> import sublist
     >>> s = sublist.SubList(range(3))
     >>> s.extend(s)
     >>> print(len(s))
     6
     >>> print(s.increment())
     1
     >>> print(s.increment())
     2

     #define PY_SSIZE_T_CLEAN
     #include <Python.h>

     typedef struct {
         PyListObject list;
         int state;
     } SubListObject;

     static PyObject *
     SubList_increment(SubListObject *self, PyObject *unused)
     {
         self->state++;
         return PyLong_FromLong(self->state);
     }

     static PyMethodDef SubList_methods[] = {
         {"increment", (PyCFunction) SubList_increment, METH_NOARGS,
          PyDoc_STR("increment state counter")},
         {NULL},
     };

     static int
     SubList_init(SubListObject *self, PyObject *args, PyObject *kwds)
     {
         if (PyList_Type.tp_init((PyObject *) self, args, kwds) < 0)
             return -1;
         self->state = 0;
         return 0;
     }

     static PyTypeObject SubListType = {
         PyVarObject_HEAD_INIT(NULL, 0)
         .tp_name = "sublist.SubList",
         .tp_doc = PyDoc_STR("SubList objects"),
         .tp_basicsize = sizeof(SubListObject),
         .tp_itemsize = 0,
         .tp_flags = Py_TPFLAGS_DEFAULT | Py_TPFLAGS_BASETYPE,
         .tp_init = (initproc) SubList_init,
         .tp_methods = SubList_methods,
     };

     static PyModuleDef sublistmodule = {
         PyModuleDef_HEAD_INIT,
         .m_name = "sublist",
         .m_doc = "Example module that creates an extension type.",
         .m_size = -1,
     };

     PyMODINIT_FUNC
     PyInit_sublist(void)
     {
         PyObject *m;
         SubListType.tp_base = &PyList_Type;
         if (PyType_Ready(&SubListType) < 0)
             return NULL;

         m = PyModule_Create(&sublistmodule);
         if (m == NULL)
             return NULL;

         if (PyModule_AddObjectRef(m, "SubList", (PyObject *) &SubListType) < 0) {
             Py_DECREF(m);
             return NULL;
         }

         return m;
     }

As you can see, the source code closely resembles the ‘Custom’ examples
in previous sections.  We will break down the main differences between
them.

     typedef struct {
         PyListObject list;
         int state;
     } SubListObject;

The primary difference for derived type objects is that the base type's
object structure must be the first value.  The base type will already
include the *note PyObject_HEAD(): 1271. at the beginning of its
structure.

When a Python object is a ‘SubList’ instance, its ‘PyObject *’ pointer
can be safely cast to both ‘PyListObject *’ and ‘SubListObject *’:

     static int
     SubList_init(SubListObject *self, PyObject *args, PyObject *kwds)
     {
         if (PyList_Type.tp_init((PyObject *) self, args, kwds) < 0)
             return -1;
         self->state = 0;
         return 0;
     }

We see above how to call through to the *note __init__(): 655. method of
the base type.

This pattern is important when writing a type with custom *note tp_new:
525. and *note tp_dealloc: 4704. members.  The *note tp_new: 525.
handler should not actually create the memory for the object with its
*note tp_alloc: 4706, but let the base class handle it by calling its
own *note tp_new: 525.

The *note PyTypeObject: a48. struct supports a *note tp_base: 4710.
specifying the type's concrete base class.  Due to cross-platform
compiler issues, you can't fill that field directly with a reference to
*note PyList_Type: 4711.; it should be done later in the module
initialization function:

     PyMODINIT_FUNC
     PyInit_sublist(void)
     {
         PyObject* m;
         SubListType.tp_base = &PyList_Type;
         if (PyType_Ready(&SubListType) < 0)
             return NULL;

         m = PyModule_Create(&sublistmodule);
         if (m == NULL)
             return NULL;

         if (PyModule_AddObjectRef(m, "SubList", (PyObject *) &SubListType) < 0) {
             Py_DECREF(m);
             return NULL;
         }

         return m;
     }

Before calling *note PyType_Ready(): 722, the type structure must have
the *note tp_base: 4710. slot filled in.  When we are deriving an
existing type, it is not necessary to fill out the *note tp_alloc: 4706.
slot with *note PyType_GenericNew(): 4701. - the allocation function
from the base type will be inherited.

After that, calling *note PyType_Ready(): 722. and adding the type
object to the module is the same as with the basic ‘Custom’ examples.

註解
....


File: python.info,  Node: Defining Extension Types Assorted Topics,  Next: 建立 C 與 C++ 擴充套件,  Prev: Defining Extension Types Tutorial,  Up: 不使用第三方工具建立擴充

6.2.3 Defining Extension Types: Assorted Topics
-----------------------------------------------

This section aims to give a quick fly-by on the various type methods you
can implement and what they do.

Here is the definition of *note PyTypeObject: a48, with some fields only
used in *note debug builds: 1de. omitted:

     typedef struct _typeobject {
         PyObject_VAR_HEAD
         const char *tp_name; /* For printing, in format "<module>.<name>" */
         Py_ssize_t tp_basicsize, tp_itemsize; /* For allocation */

         /* Methods to implement standard operations */

         destructor tp_dealloc;
         Py_ssize_t tp_vectorcall_offset;
         getattrfunc tp_getattr;
         setattrfunc tp_setattr;
         PyAsyncMethods *tp_as_async; /* formerly known as tp_compare (Python 2)
                                         or tp_reserved (Python 3) */
         reprfunc tp_repr;

         /* Method suites for standard classes */

         PyNumberMethods *tp_as_number;
         PySequenceMethods *tp_as_sequence;
         PyMappingMethods *tp_as_mapping;

         /* More standard operations (here for binary compatibility) */

         hashfunc tp_hash;
         ternaryfunc tp_call;
         reprfunc tp_str;
         getattrofunc tp_getattro;
         setattrofunc tp_setattro;

         /* Functions to access object as input/output buffer */
         PyBufferProcs *tp_as_buffer;

         /* Flags to define presence of optional/expanded features */
         unsigned long tp_flags;

         const char *tp_doc; /* Documentation string */

         /* Assigned meaning in release 2.0 */
         /* call function for all accessible objects */
         traverseproc tp_traverse;

         /* delete references to contained objects */
         inquiry tp_clear;

         /* Assigned meaning in release 2.1 */
         /* rich comparisons */
         richcmpfunc tp_richcompare;

         /* weak reference enabler */
         Py_ssize_t tp_weaklistoffset;

         /* Iterators */
         getiterfunc tp_iter;
         iternextfunc tp_iternext;

         /* Attribute descriptor and subclassing stuff */
         struct PyMethodDef *tp_methods;
         struct PyMemberDef *tp_members;
         struct PyGetSetDef *tp_getset;
         // Strong reference on a heap type, borrowed reference on a static type
         struct _typeobject *tp_base;
         PyObject *tp_dict;
         descrgetfunc tp_descr_get;
         descrsetfunc tp_descr_set;
         Py_ssize_t tp_dictoffset;
         initproc tp_init;
         allocfunc tp_alloc;
         newfunc tp_new;
         freefunc tp_free; /* Low-level free-memory routine */
         inquiry tp_is_gc; /* For PyObject_IS_GC */
         PyObject *tp_bases;
         PyObject *tp_mro; /* method resolution order */
         PyObject *tp_cache;
         PyObject *tp_subclasses;
         PyObject *tp_weaklist;
         destructor tp_del;

         /* Type attribute cache version tag. Added in version 2.6 */
         unsigned int tp_version_tag;

         destructor tp_finalize;
         vectorcallfunc tp_vectorcall;

         /* bitset of which type-watchers care about this type */
         unsigned char tp_watched;
     } PyTypeObject;

Now that's a 'lot' of methods.  Don't worry too much though - if you
have a type you want to define, the chances are very good that you will
only implement a handful of these.

As you probably expect by now, we're going to go over this and give more
information about the various handlers.  We won't go in the order they
are defined in the structure, because there is a lot of historical
baggage that impacts the ordering of the fields.  It's often easiest to
find an example that includes the fields you need and then change the
values to suit your new type.

     const char *tp_name; /* For printing */

The name of the type - as mentioned in the previous chapter, this will
appear in various places, almost entirely for diagnostic purposes.  Try
to choose something that will be helpful in such a situation!

     Py_ssize_t tp_basicsize, tp_itemsize; /* For allocation */

These fields tell the runtime how much memory to allocate when new
objects of this type are created.  Python has some built-in support for
variable length structures (think: strings, tuples) which is where the
*note tp_itemsize: 1e46. field comes in.  This will be dealt with later.

     const char *tp_doc;

Here you can put a string (or its address) that you want returned when
the Python script references ‘obj.__doc__’ to retrieve the doc string.

Now we come to the basic type methods - the ones most extension types
will implement.

* Menu:

* Finalization and De-allocation::
* Object Presentation::
* Attribute Management::
* Object Comparison::
* Abstract Protocol Support::
* Weak Reference Support::
* More Suggestions::


File: python.info,  Node: Finalization and De-allocation,  Next: Object Presentation,  Up: Defining Extension Types Assorted Topics

6.2.3.1 Finalization and De-allocation
......................................

     destructor tp_dealloc;

This function is called when the reference count of the instance of your
type is reduced to zero and the Python interpreter wants to reclaim it.
If your type has memory to free or other clean-up to perform, you can
put it here.  The object itself needs to be freed here as well.  Here is
an example of this function:

     static void
     newdatatype_dealloc(newdatatypeobject *obj)
     {
         free(obj->obj_UnderlyingDatatypePtr);
         Py_TYPE(obj)->tp_free((PyObject *)obj);
     }

If your type supports garbage collection, the destructor should call
*note PyObject_GC_UnTrack(): 1475. before clearing any member fields:

     static void
     newdatatype_dealloc(newdatatypeobject *obj)
     {
         PyObject_GC_UnTrack(obj);
         Py_CLEAR(obj->other_obj);
         ...
         Py_TYPE(obj)->tp_free((PyObject *)obj);
     }

One important requirement of the deallocator function is that it leaves
any pending exceptions alone.  This is important since deallocators are
frequently called as the interpreter unwinds the Python stack; when the
stack is unwound due to an exception (rather than normal returns),
nothing is done to protect the deallocators from seeing that an
exception has already been set.  Any actions which a deallocator
performs which may cause additional Python code to be executed may
detect that an exception has been set.  This can lead to misleading
errors from the interpreter.  The proper way to protect against this is
to save a pending exception before performing the unsafe action, and
restoring it when done.  This can be done using the *note PyErr_Fetch():
3bb. and *note PyErr_Restore(): 3be. functions:

     static void
     my_dealloc(PyObject *obj)
     {
         MyObject *self = (MyObject *) obj;
         PyObject *cbresult;

         if (self->my_callback != NULL) {
             PyObject *err_type, *err_value, *err_traceback;

             /* This saves the current exception state */
             PyErr_Fetch(&err_type, &err_value, &err_traceback);

             cbresult = PyObject_CallNoArgs(self->my_callback);
             if (cbresult == NULL)
                 PyErr_WriteUnraisable(self->my_callback);
             else
                 Py_DECREF(cbresult);

             /* This restores the saved exception state */
             PyErr_Restore(err_type, err_value, err_traceback);

             Py_DECREF(self->my_callback);
         }
         Py_TYPE(obj)->tp_free((PyObject*)self);
     }

     備註: There are limitations to what you can safely do in a
     deallocator function.  First, if your type supports garbage
     collection (using *note tp_traverse: 721. and/or *note tp_clear:
     4717.), some of the object's members can have been cleared or
     finalized by the time *note tp_dealloc: 4704. is called.  Second,
     in *note tp_dealloc: 4704, your object is in an unstable state: its
     reference count is equal to zero.  Any call to a non-trivial object
     or API (as in the example above) might end up calling *note
     tp_dealloc: 4704. again, causing a double free and a crash.

     Starting with Python 3.4, it is recommended not to put any complex
     finalization code in *note tp_dealloc: 4704, and instead use the
     new *note tp_finalize: a49. type method.

     也參考
     ......

     PEP 442(1) explains the new finalization scheme.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0442/


File: python.info,  Node: Object Presentation,  Next: Attribute Management,  Prev: Finalization and De-allocation,  Up: Defining Extension Types Assorted Topics

6.2.3.2 Object Presentation
...........................

In Python, there are two ways to generate a textual representation of an
object: the *note repr(): 7a1. function, and the *note str(): 3f2.
function.  (The *note print(): f18. function just calls *note str():
3f2.)  These handlers are both optional.

     reprfunc tp_repr;
     reprfunc tp_str;

The *note tp_repr: 4719. handler should return a string object
containing a representation of the instance for which it is called.
Here is a simple example:

     static PyObject *
     newdatatype_repr(newdatatypeobject *obj)
     {
         return PyUnicode_FromFormat("Repr-ified_newdatatype{{size:%d}}",
                                     obj->obj_UnderlyingDatatypePtr->size);
     }

If no *note tp_repr: 4719. handler is specified, the interpreter will
supply a representation that uses the type's *note tp_name: 17f5. and a
uniquely identifying value for the object.

The *note tp_str: 471a. handler is to *note str(): 3f2. what the *note
tp_repr: 4719. handler described above is to *note repr(): 7a1.; that
is, it is called when Python code calls *note str(): 3f2. on an instance
of your object.  Its implementation is very similar to the *note
tp_repr: 4719. function, but the resulting string is intended for human
consumption.  If *note tp_str: 471a. is not specified, the *note
tp_repr: 4719. handler is used instead.

以下是個簡單的範例：

     static PyObject *
     newdatatype_str(newdatatypeobject *obj)
     {
         return PyUnicode_FromFormat("Stringified_newdatatype{{size:%d}}",
                                     obj->obj_UnderlyingDatatypePtr->size);
     }


File: python.info,  Node: Attribute Management,  Next: Object Comparison,  Prev: Object Presentation,  Up: Defining Extension Types Assorted Topics

6.2.3.3 Attribute Management
............................

For every object which can support attributes, the corresponding type
must provide the functions that control how the attributes are resolved.
There needs to be a function which can retrieve attributes (if any are
defined), and another to set attributes (if setting attributes is
allowed).  Removing an attribute is a special case, for which the new
value passed to the handler is ‘NULL’.

Python supports two pairs of attribute handlers; a type that supports
attributes only needs to implement the functions for one pair.  The
difference is that one pair takes the name of the attribute as a char*,
while the other accepts a *note PyObject: 311.*.  Each type can use
whichever pair makes more sense for the implementation's convenience.

     getattrfunc  tp_getattr;        /* char * version */
     setattrfunc  tp_setattr;
     /* ... */
     getattrofunc tp_getattro;       /* PyObject * version */
     setattrofunc tp_setattro;

If accessing attributes of an object is always a simple operation (this
will be explained shortly), there are generic implementations which can
be used to provide the *note PyObject: 311.* version of the attribute
management functions.  The actual need for type-specific attribute
handlers almost completely disappeared starting with Python 2.2, though
there are many examples which have not been updated to use some of the
new generic mechanism that is available.

* Menu:

* Generic Attribute Management::
* Type-specific Attribute Management::


File: python.info,  Node: Generic Attribute Management,  Next: Type-specific Attribute Management,  Up: Attribute Management

6.2.3.4 Generic Attribute Management
....................................

Most extension types only use 'simple' attributes.  So, what makes the
attributes simple?  There are only a couple of conditions that must be
met:

  1. The name of the attributes must be known when *note PyType_Ready():
     722. is called.

  2. No special processing is needed to record that an attribute was
     looked up or set, nor do actions need to be taken based on the
     value.

Note that this list does not place any restrictions on the values of the
attributes, when the values are computed, or how relevant data is
stored.

When *note PyType_Ready(): 722. is called, it uses three tables
referenced by the type object to create *note descriptor: 1e47.s which
are placed in the dictionary of the type object.  Each descriptor
controls access to one attribute of the instance object.  Each of the
tables is optional; if all three are ‘NULL’, instances of the type will
only have attributes that are inherited from their base type, and should
leave the *note tp_getattro: 15ec. and *note tp_setattro: 471d. fields
‘NULL’ as well, allowing the base type to handle attributes.

The tables are declared as three fields of the type object:

     struct PyMethodDef *tp_methods;
     struct PyMemberDef *tp_members;
     struct PyGetSetDef *tp_getset;

If *note tp_methods: 4709. is not ‘NULL’, it must refer to an array of
*note PyMethodDef: 1446. structures.  Each entry in the table is an
instance of this structure:

     typedef struct PyMethodDef {
         const char  *ml_name;       /* method name */
         PyCFunction  ml_meth;       /* implementation function */
         int          ml_flags;      /* flags */
         const char  *ml_doc;        /* docstring */
     } PyMethodDef;

One entry should be defined for each method provided by the type; no
entries are needed for methods inherited from a base type.  One
additional entry is needed at the end; it is a sentinel that marks the
end of the array.  The *note ml_name: 471e. field of the sentinel must
be ‘NULL’.

The second table is used to define attributes which map directly to data
stored in the instance.  A variety of primitive C types are supported,
and access may be read-only or read-write.  The structures in the table
are defined as:

     typedef struct PyMemberDef {
         const char *name;
         int         type;
         int         offset;
         int         flags;
         const char *doc;
     } PyMemberDef;

For each entry in the table, a *note descriptor: 1e47. will be
constructed and added to the type which will be able to extract a value
from the instance structure.  The *note type: 471f. field should contain
a type code like *note Py_T_INT: 535. or *note Py_T_DOUBLE: 536.; the
value will be used to determine how to convert Python values to and from
C values.  The *note flags: 4720. field is used to store flags which
control how the attribute can be accessed: you can set it to *note
Py_READONLY: 537. to prevent Python code from setting it.

An interesting advantage of using the *note tp_members: 4707. table to
build descriptors that are used at runtime is that any attribute defined
this way can have an associated doc string simply by providing the text
in the table.  An application can use the introspection API to retrieve
the descriptor from the class object, and get the doc string using its
‘__doc__’ attribute.

As with the *note tp_methods: 4709. table, a sentinel entry with a *note
ml_name: 471e. value of ‘NULL’ is required.


File: python.info,  Node: Type-specific Attribute Management,  Prev: Generic Attribute Management,  Up: Attribute Management

6.2.3.5 Type-specific Attribute Management
..........................................

For simplicity, only the char* version will be demonstrated here; the
type of the name parameter is the only difference between the char* and
*note PyObject: 311.* flavors of the interface.  This example
effectively does the same thing as the generic example above, but does
not use the generic support added in Python 2.2.  It explains how the
handler functions are called, so that if you do need to extend their
functionality, you'll understand what needs to be done.

The *note tp_getattr: 4722. handler is called when the object requires
an attribute look-up.  It is called in the same situations where the
*note __getattr__(): 47a. method of a class would be called.

舉例來說：

     static PyObject *
     newdatatype_getattr(newdatatypeobject *obj, char *name)
     {
         if (strcmp(name, "data") == 0)
         {
             return PyLong_FromLong(obj->data);
         }

         PyErr_Format(PyExc_AttributeError,
                      "'%.100s' object has no attribute '%.400s'",
                      Py_TYPE(obj)->tp_name, name);
         return NULL;
     }

The *note tp_setattr: 4723. handler is called when the *note
__setattr__(): 1e05. or *note __delattr__(): 1e06. method of a class
instance would be called.  When an attribute should be deleted, the
third parameter will be ‘NULL’.  Here is an example that simply raises
an exception; if this were really all you wanted, the *note tp_setattr:
4723. handler should be set to ‘NULL’.

     static int
     newdatatype_setattr(newdatatypeobject *obj, char *name, PyObject *v)
     {
         PyErr_Format(PyExc_RuntimeError, "Read-only attribute: %s", name);
         return -1;
     }


File: python.info,  Node: Object Comparison,  Next: Abstract Protocol Support,  Prev: Attribute Management,  Up: Defining Extension Types Assorted Topics

6.2.3.6 Object Comparison
.........................

     richcmpfunc tp_richcompare;

The *note tp_richcompare: 4725. handler is called when comparisons are
needed.  It is analogous to the *note rich comparison methods: 1e37,
like ‘__lt__()’, and also called by *note PyObject_RichCompare(): 4726.
and *note PyObject_RichCompareBool(): 18a7.

This function is called with two Python objects and the operator as
arguments, where the operator is one of ‘Py_EQ’, ‘Py_NE’, ‘Py_LE’,
‘Py_GE’, ‘Py_LT’ or ‘Py_GT’.  It should compare the two objects with
respect to the specified operator and return ‘Py_True’ or ‘Py_False’ if
the comparison is successful, ‘Py_NotImplemented’ to indicate that
comparison is not implemented and the other object's comparison method
should be tried, or ‘NULL’ if an exception was set.

Here is a sample implementation, for a datatype that is considered equal
if the size of an internal pointer is equal:

     static PyObject *
     newdatatype_richcmp(newdatatypeobject *obj1, newdatatypeobject *obj2, int op)
     {
         PyObject *result;
         int c, size1, size2;

         /* code to make sure that both arguments are of type
            newdatatype omitted */

         size1 = obj1->obj_UnderlyingDatatypePtr->size;
         size2 = obj2->obj_UnderlyingDatatypePtr->size;

         switch (op) {
         case Py_LT: c = size1 <  size2; break;
         case Py_LE: c = size1 <= size2; break;
         case Py_EQ: c = size1 == size2; break;
         case Py_NE: c = size1 != size2; break;
         case Py_GT: c = size1 >  size2; break;
         case Py_GE: c = size1 >= size2; break;
         }
         result = c ? Py_True : Py_False;
         Py_INCREF(result);
         return result;
      }


File: python.info,  Node: Abstract Protocol Support,  Next: Weak Reference Support,  Prev: Object Comparison,  Up: Defining Extension Types Assorted Topics

6.2.3.7 Abstract Protocol Support
.................................

Python supports a variety of 'abstract' 'protocols;' the specific
interfaces provided to use these interfaces are documented in *note
抽象物件層 (Abstract Objects Layer): 4728.

A number of these abstract interfaces were defined early in the
development of the Python implementation.  In particular, the number,
mapping, and sequence protocols have been part of Python since the
beginning.  Other protocols have been added over time.  For protocols
which depend on several handler routines from the type implementation,
the older protocols have been defined as optional blocks of handlers
referenced by the type object.  For newer protocols there are additional
slots in the main type object, with a flag bit being set to indicate
that the slots are present and should be checked by the interpreter.
(The flag bit does not indicate that the slot values are non-‘NULL’.
The flag may be set to indicate the presence of a slot, but a slot may
still be unfilled.)

     PyNumberMethods   *tp_as_number;
     PySequenceMethods *tp_as_sequence;
     PyMappingMethods  *tp_as_mapping;

If you wish your object to be able to act like a number, a sequence, or
a mapping object, then you place the address of a structure that
implements the C type *note PyNumberMethods: 138b, *note
PySequenceMethods: 4729, or *note PyMappingMethods: 472a, respectively.
It is up to you to fill in this structure with appropriate values.  You
can find examples of the use of each of these in the ‘Objects’ directory
of the Python source distribution.

     hashfunc tp_hash;

This function, if you choose to provide it, should return a hash number
for an instance of your data type.  Here is a simple example:

     static Py_hash_t
     newdatatype_hash(newdatatypeobject *obj)
     {
         Py_hash_t result;
         result = obj->some_size + 32767 * obj->some_number;
         if (result == -1)
            result = -2;
         return result;
     }

*note Py_hash_t: 11fc. is a signed integer type with a platform-varying
width.  Returning ‘-1’ from *note tp_hash: 472b. indicates an error,
which is why you should be careful to avoid returning it when hash
computation is successful, as seen above.

     ternaryfunc tp_call;

This function is called when an instance of your data type is "called",
for example, if ‘obj1’ is an instance of your data type and the Python
script contains ‘obj1('hello')’, the *note tp_call: 4ff. handler is
invoked.

This function takes three arguments:

  1. 'self' is the instance of the data type which is the subject of the
     call.  If the call is ‘obj1('hello')’, then 'self' is ‘obj1’.

  2. 'args' is a tuple containing the arguments to the call.  You can
     use *note PyArg_ParseTuple(): 517. to extract the arguments.

  3. 'kwds' is a dictionary of keyword arguments that were passed.  If
     this is non-‘NULL’ and you support keyword arguments, use *note
     PyArg_ParseTupleAndKeywords(): 2e9. to extract the arguments.  If
     you do not want to support keyword arguments and this is
     non-‘NULL’, raise a *note TypeError: 4dd. with a message saying
     that keyword arguments are not supported.

Here is a toy ‘tp_call’ implementation:

     static PyObject *
     newdatatype_call(newdatatypeobject *obj, PyObject *args, PyObject *kwds)
     {
         PyObject *result;
         const char *arg1;
         const char *arg2;
         const char *arg3;

         if (!PyArg_ParseTuple(args, "sss:call", &arg1, &arg2, &arg3)) {
             return NULL;
         }
         result = PyUnicode_FromFormat(
             "Returning -- value: [%d] arg1: [%s] arg2: [%s] arg3: [%s]\n",
             obj->obj_UnderlyingDatatypePtr->size,
             arg1, arg2, arg3);
         return result;
     }

     /* 疊代器 */
     getiterfunc tp_iter;
     iternextfunc tp_iternext;

These functions provide support for the iterator protocol.  Both
handlers take exactly one parameter, the instance for which they are
being called, and return a new reference.  In the case of an error, they
should set an exception and return ‘NULL’.  *note tp_iter: 145c.
corresponds to the Python *note __iter__(): 1e31. method, while *note
tp_iternext: 145d. corresponds to the Python *note __next__(): 1260.
method.

Any *note iterable: 11bf. object must implement the *note tp_iter: 145c.
handler, which must return an *note iterator: 192. object.  Here the
same guidelines apply as for Python classes:

   * For collections (such as lists and tuples) which can support
     multiple independent iterators, a new iterator should be created
     and returned by each call to *note tp_iter: 145c.

   * Objects which can only be iterated over once (usually due to side
     effects of iteration, such as file objects) can implement *note
     tp_iter: 145c. by returning a new reference to themselves - and
     should also therefore implement the *note tp_iternext: 145d.
     handler.

Any *note iterator: 192. object should implement both *note tp_iter:
145c. and *note tp_iternext: 145d.  An iterator's *note tp_iter: 145c.
handler should return a new reference to the iterator.  Its *note
tp_iternext: 145d. handler should return a new reference to the next
object in the iteration, if there is one.  If the iteration has reached
the end, *note tp_iternext: 145d. may return ‘NULL’ without setting an
exception, or it may set *note StopIteration: ba1. 'in addition' to
returning ‘NULL’; avoiding the exception can yield slightly better
performance.  If an actual error occurs, *note tp_iternext: 145d. should
always set an exception and return ‘NULL’.


File: python.info,  Node: Weak Reference Support,  Next: More Suggestions,  Prev: Abstract Protocol Support,  Up: Defining Extension Types Assorted Topics

6.2.3.8 Weak Reference Support
..............................

One of the goals of Python's weak reference implementation is to allow
any type to participate in the weak reference mechanism without
incurring the overhead on performance-critical objects (such as
numbers).

也參考
......

Documentation for the *note weakref: fc. module.

For an object to be weakly referenceable, the extension type must set
the ‘Py_TPFLAGS_MANAGED_WEAKREF’ bit of the *note tp_flags: 17c0. field.
The legacy *note tp_weaklistoffset: 92c. field should be left as zero.

Concretely, here is how the statically declared type object would look:

     static PyTypeObject TrivialType = {
         PyVarObject_HEAD_INIT(NULL, 0)
         /* ... other members omitted for brevity ... */
         .tp_flags = Py_TPFLAGS_MANAGED_WEAKREF | ...,
     };

The only further addition is that ‘tp_dealloc’ needs to clear any weak
references (by calling *note PyObject_ClearWeakRefs(): 51c.):

     static void
     Trivial_dealloc(TrivialObject *self)
     {
         /* Clear weakrefs first before calling any destructors */
         PyObject_ClearWeakRefs((PyObject *) self);
         /* ... remainder of destruction code omitted for brevity ... */
         Py_TYPE(self)->tp_free((PyObject *) self);
     }


File: python.info,  Node: More Suggestions,  Prev: Weak Reference Support,  Up: Defining Extension Types Assorted Topics

6.2.3.9 More Suggestions
........................

In order to learn how to implement any specific method for your new data
type, get the *note CPython: 699. source code.  Go to the ‘Objects’
directory, then search the C source files for ‘tp_’ plus the function
you want (for example, ‘tp_richcompare’).  You will find examples of the
function you want to implement.

When you need to verify that an object is a concrete instance of the
type you are implementing, use the *note PyObject_TypeCheck(): 17fa.
function.  A sample of its use might be something like the following:

     if (!PyObject_TypeCheck(some_object, &MyType)) {
         PyErr_SetString(PyExc_TypeError, "arg #1 not a mything");
         return NULL;
     }

也參考
......

Download CPython source releases.

     ‘https://www.python.org/downloads/source/’

The CPython project on GitHub, where the CPython source code is developed.

     ‘https://github.com/python/cpython’


File: python.info,  Node: 建立 C 與 C++ 擴充套件,  Next: 建置 Windows 上的 C 和 C++ 擴充,  Prev: Defining Extension Types Assorted Topics,  Up: 不使用第三方工具建立擴充

6.2.4 建立 C 與 C++ 擴充套件
----------------------------

一個 CPython 的 C 擴充套件是一個共用函式庫（例如在 Linux 上的 ‘.so’ 檔案
，在 Windows 上的 ‘.pyd’），會匯出一個'初始化函式'。

To be importable, the shared library must be available on *note
PYTHONPATH: fbe, and must be named after the module name, with an
appropriate extension.  When using setuptools, the correct filename is
generated automatically.

The initialization function has the signature:

 -- C 函式: *note PyObject: 311. *PyInit_modulename (void)

It returns either a fully initialized module, or a *note PyModuleDef:
921. instance.  See *note 初始化 C 模組: 4731. for details.

For modules with ASCII-only names, the function must be named
‘PyInit_<modulename>’, with ‘<modulename>’ replaced by the name of the
module.  When using *note Multi-phase initialization: 4732, non-ASCII
module names are allowed.  In this case, the initialization function
name is ‘PyInitU_<modulename>’, with ‘<modulename>’ encoded using
Python's 'punycode' encoding with hyphens replaced by underscores.  In
Python:

     def initfunc_name(name):
         try:
             suffix = b'_' + name.encode('ascii')
         except UnicodeEncodeError:
             suffix = b'U_' + name.encode('punycode').replace(b'-', b'_')
         return b'PyInit' + suffix

It is possible to export multiple modules from a single shared library
by defining multiple initialization functions.  However, importing them
requires using symbolic links or a custom importer, because by default
only the function corresponding to the filename is found.  See the
'"Multiple modules in one library"' section in PEP 489(1) for details.
* Menu:

* Building C and C++ Extensions with setuptools::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0489/


File: python.info,  Node: Building C and C++ Extensions with setuptools,  Up: 建立 C 與 C++ 擴充套件

6.2.4.1 Building C and C++ Extensions with setuptools
.....................................................

Python 3.12 and newer no longer come with distutils.  Please refer to
the ‘setuptools’ documentation at
‘https://setuptools.readthedocs.io/en/latest/setuptools.html’ to learn
more about how build and distribute C/C++ extensions with setuptools.


File: python.info,  Node: 建置 Windows 上的 C 和 C++ 擴充,  Prev: 建立 C 與 C++ 擴充套件,  Up: 不使用第三方工具建立擴充

6.2.5 建置 Windows 上的 C 和 C++ 擴充
-------------------------------------

This chapter briefly explains how to create a Windows extension module
for Python using Microsoft Visual C++, and follows with more detailed
background information on how it works.  The explanatory material is
useful for both the Windows programmer learning to build Python
extensions and the Unix programmer interested in producing software
which can be successfully built on both Unix and Windows.

Module authors are encouraged to use the distutils approach for building
extension modules, instead of the one described in this section.  You
will still need the C compiler that was used to build Python; typically
Microsoft Visual C++.

     備註: This chapter mentions a number of filenames that include an
     encoded Python version number.  These filenames are represented
     with the version number shown as ‘XY’; in practice, ‘'X'’ will be
     the major version number and ‘'Y'’ will be the minor version number
     of the Python release you're working with.  For example, if you are
     using Python 2.2.1, ‘XY’ will actually be ‘22’.

* Menu:

* A Cookbook Approach::
* Differences Between Unix and Windows::
* Using DLLs in Practice::


File: python.info,  Node: A Cookbook Approach,  Next: Differences Between Unix and Windows,  Up: 建置 Windows 上的 C 和 C++ 擴充

6.2.5.1 A Cookbook Approach
...........................

There are two approaches to building extension modules on Windows, just
as there are on Unix: use the ‘setuptools’ package to control the build
process, or do things manually.  The setuptools approach works well for
most extensions; documentation on using ‘setuptools’ to build and
package extension modules is available in *note Building C and C++
Extensions with setuptools: e9b.  If you find you really need to do
things manually, it may be instructive to study the project file for the
winsound(1) standard library module.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/PCbuild/winsound.vcxproj


File: python.info,  Node: Differences Between Unix and Windows,  Next: Using DLLs in Practice,  Prev: A Cookbook Approach,  Up: 建置 Windows 上的 C 和 C++ 擴充

6.2.5.2 Differences Between Unix and Windows
............................................

Unix and Windows use completely different paradigms for run-time loading
of code.  Before you try to build a module that can be dynamically
loaded, be aware of how your system works.

In Unix, a shared object (‘.so’) file contains code to be used by the
program, and also the names of functions and data that it expects to
find in the program.  When the file is joined to the program, all
references to those functions and data in the file's code are changed to
point to the actual locations in the program where the functions and
data are placed in memory.  This is basically a link operation.

In Windows, a dynamic-link library (‘.dll’) file has no dangling
references.  Instead, an access to functions or data goes through a
lookup table.  So the DLL code does not have to be fixed up at runtime
to refer to the program's memory; instead, the code already uses the
DLL's lookup table, and the lookup table is modified at runtime to point
to the functions and data.

In Unix, there is only one type of library file (‘.a’) which contains
code from several object files (‘.o’).  During the link step to create a
shared object file (‘.so’), the linker may find that it doesn't know
where an identifier is defined.  The linker will look for it in the
object files in the libraries; if it finds it, it will include all the
code from that object file.

In Windows, there are two types of library, a static library and an
import library (both called ‘.lib’).  A static library is like a Unix
‘.a’ file; it contains code to be included as necessary.  An import
library is basically used only to reassure the linker that a certain
identifier is legal, and will be present in the program when the DLL is
loaded.  So the linker uses the information from the import library to
build the lookup table for using identifiers that are not included in
the DLL. When an application or a DLL is linked, an import library may
be generated, which will need to be used for all future DLLs that depend
on the symbols in the application or DLL.

Suppose you are building two dynamic-load modules, B and C, which should
share another block of code A. On Unix, you would 'not' pass ‘A.a’ to
the linker for ‘B.so’ and ‘C.so’; that would cause it to be included
twice, so that B and C would each have their own copy.  In Windows,
building ‘A.dll’ will also build ‘A.lib’.  You 'do' pass ‘A.lib’ to the
linker for B and C. ‘A.lib’ does not contain code; it just contains
information which will be used at runtime to access A's code.

In Windows, using an import library is sort of like using ‘import spam’;
it gives you access to spam's names, but does not create a separate
copy.  On Unix, linking with a library is more like ‘from spam import
*’; it does create a separate copy.


File: python.info,  Node: Using DLLs in Practice,  Prev: Differences Between Unix and Windows,  Up: 建置 Windows 上的 C 和 C++ 擴充

6.2.5.3 Using DLLs in Practice
..............................

Windows Python is built in Microsoft Visual C++; using other compilers
may or may not work.  The rest of this section is MSVC++ specific.

When creating DLLs in Windows, you must pass ‘pythonXY.lib’ to the
linker.  To build two DLLs, spam and ni (which uses C functions found in
spam), you could use these commands:

     cl /LD /I/python/include spam.c ../libs/pythonXY.lib
     cl /LD /I/python/include ni.c spam.lib ../libs/pythonXY.lib

The first command created three files: ‘spam.obj’, ‘spam.dll’ and
‘spam.lib’.  ‘Spam.dll’ does not contain any Python functions (such as
*note PyArg_ParseTuple(): 517.), but it does know how to find the Python
code thanks to ‘pythonXY.lib’.

The second command created ‘ni.dll’ (and ‘.obj’ and ‘.lib’), which knows
how to find the necessary functions from spam, and also from the Python
executable.

Not every identifier is exported to the lookup table.  If you want any
other modules (including Python) to be able to see your identifiers, you
have to say ‘_declspec(dllexport)’, as in ‘void _declspec(dllexport)
initspam(void)’ or ‘PyObject _declspec(dllexport) *NiGetSpamData(void)’.

Developer Studio will throw in a lot of import libraries that you do not
really need, adding about 100K to your executable.  To get rid of them,
use the Project Settings dialog, Link tab, to specify 'ignore default
libraries'.  Add the correct ‘msvcrt`xx'.lib’ to the list of libraries.


File: python.info,  Node: 在更大的應用程式中嵌入 CPython 運行環境 runtime,  Prev: 不使用第三方工具建立擴充,  Up: 擴充和嵌入 Python 直譯器

6.3 在更大的應用程式中嵌入 CPython 運行環境 (runtime)
=====================================================

有時候，相較於建立一個擴充，使其在 Python 直譯器中可作為主應用程式運行，
還不如將 CPython 運行環境嵌入至一個更大的應用程式中更可取。本節將涵蓋一
些要成功完成此任務所涉及的細節。

* Menu:

* 在其它 App 內嵌入 Python::


File: python.info,  Node: 在其它 App 內嵌入 Python,  Up: 在更大的應用程式中嵌入 CPython 運行環境 runtime

6.3.1 在其它 App 內嵌入 Python
------------------------------

The previous chapters discussed how to extend Python, that is, how to
extend the functionality of Python by attaching a library of C functions
to it.  It is also possible to do it the other way around: enrich your
C/C++ application by embedding Python in it.  Embedding provides your
application with the ability to implement some of the functionality of
your application in Python rather than C or C++.  This can be used for
many purposes; one example would be to allow users to tailor the
application to their needs by writing some scripts in Python.  You can
also use it yourself if some of the functionality can be written in
Python more easily.

Embedding Python is similar to extending it, but not quite.  The
difference is that when you extend Python, the main program of the
application is still the Python interpreter, while if you embed Python,
the main program may have nothing to do with Python -- instead, some
parts of the application occasionally call the Python interpreter to run
some Python code.

So if you are embedding Python, you are providing your own main program.
One of the things this main program has to do is initialize the Python
interpreter.  At the very least, you have to call the function *note
Py_Initialize(): 851.  There are optional calls to pass command line
arguments to Python.  Then later you can call the interpreter from any
part of the application.

There are several different ways to call the interpreter: you can pass a
string containing Python statements to *note PyRun_SimpleString(): 473f,
or you can pass a stdio file pointer and a file name (for identification
in error messages only) to *note PyRun_SimpleFile(): 4740.  You can also
call the lower-level operations described in the previous chapters to
construct and use Python objects.

也參考
......

*note Python/C API 參考手冊: 1ae2.

     The details of Python's C interface are given in this manual.  A
     great deal of necessary information can be found here.

* Menu:

* Very High Level Embedding::
* Beyond Very High Level Embedding; An overview: Beyond Very High Level Embedding An overview.
* Pure Embedding::
* Extending Embedded Python::
* Embedding Python in C++::
* Compiling and Linking under Unix-like systems::


File: python.info,  Node: Very High Level Embedding,  Next: Beyond Very High Level Embedding An overview,  Up: 在其它 App 內嵌入 Python

6.3.1.1 Very High Level Embedding
.................................

The simplest form of embedding Python is the use of the very high level
interface.  This interface is intended to execute a Python script
without needing to interact with the application directly.  This can for
example be used to perform some operation on a file.

     #define PY_SSIZE_T_CLEAN
     #include <Python.h>

     int
     main(int argc, char *argv[])
     {
         PyStatus status;
         PyConfig config;
         PyConfig_InitPythonConfig(&config);

         /* optional but recommended */
         status = PyConfig_SetBytesString(&config, &config.program_name, argv[0]);
         if (PyStatus_Exception(status)) {
             goto exception;
         }

         status = Py_InitializeFromConfig(&config);
         if (PyStatus_Exception(status)) {
             goto exception;
         }
         PyConfig_Clear(&config);

         PyRun_SimpleString("from time import time,ctime\n"
                            "print('Today is', ctime(time()))\n");
         if (Py_FinalizeEx() < 0) {
             exit(120);
         }
         return 0;

       exception:
          PyConfig_Clear(&config);
          Py_ExitStatusException(status);
     }

     備註: ‘#define PY_SSIZE_T_CLEAN’ was used to indicate that
     ‘Py_ssize_t’ should be used in some APIs instead of ‘int’.  It is
     not necessary since Python 3.13, but we keep it here for backward
     compatibility.  See *note Strings and buffers: 2e8. for a
     description of this macro.

Setting *note PyConfig.program_name: 38f. should be called before *note
Py_InitializeFromConfig(): 390. to inform the interpreter about paths to
Python run-time libraries.  Next, the Python interpreter is initialized
with *note Py_Initialize(): 851, followed by the execution of a
hard-coded Python script that prints the date and time.  Afterwards, the
*note Py_FinalizeEx(): cbc. call shuts the interpreter down, followed by
the end of the program.  In a real program, you may want to get the
Python script from another source, perhaps a text-editor routine, a
file, or a database.  Getting the Python code from a file can better be
done by using the *note PyRun_SimpleFile(): 4740. function, which saves
you the trouble of allocating memory space and loading the file
contents.


File: python.info,  Node: Beyond Very High Level Embedding An overview,  Next: Pure Embedding,  Prev: Very High Level Embedding,  Up: 在其它 App 內嵌入 Python

6.3.1.2 Beyond Very High Level Embedding: An overview
.....................................................

The high level interface gives you the ability to execute arbitrary
pieces of Python code from your application, but exchanging data values
is quite cumbersome to say the least.  If you want that, you should use
lower level calls.  At the cost of having to write more C code, you can
achieve almost anything.

It should be noted that extending Python and embedding Python is quite
the same activity, despite the different intent.  Most topics discussed
in the previous chapters are still valid.  To show this, consider what
the extension code from Python to C really does:

  1. Convert data values from Python to C,

  2. Perform a function call to a C routine using the converted values,
     and

  3. Convert the data values from the call from C to Python.

When embedding Python, the interface code does:

  1. Convert data values from C to Python,

  2. Perform a function call to a Python interface routine using the
     converted values, and

  3. Convert the data values from the call from Python to C.

As you can see, the data conversion steps are simply swapped to
accommodate the different direction of the cross-language transfer.  The
only difference is the routine that you call between both data
conversions.  When extending, you call a C routine, when embedding, you
call a Python routine.

This chapter will not discuss how to convert data from Python to C and
vice versa.  Also, proper use of references and dealing with errors is
assumed to be understood.  Since these aspects do not differ from
extending the interpreter, you can refer to earlier chapters for the
required information.


File: python.info,  Node: Pure Embedding,  Next: Extending Embedded Python,  Prev: Beyond Very High Level Embedding An overview,  Up: 在其它 App 內嵌入 Python

6.3.1.3 Pure Embedding
......................

The first program aims to execute a function in a Python script.  Like
in the section about the very high level interface, the Python
interpreter does not directly interact with the application (but that
will change in the next section).

The code to run a function defined in a Python script is:

     #define PY_SSIZE_T_CLEAN
     #include <Python.h>

     int
     main(int argc, char *argv[])
     {
         PyObject *pName, *pModule, *pFunc;
         PyObject *pArgs, *pValue;
         int i;

         if (argc < 3) {
             fprintf(stderr,"Usage: call pythonfile funcname [args]\n");
             return 1;
         }

         Py_Initialize();
         pName = PyUnicode_DecodeFSDefault(argv[1]);
         /* Error checking of pName left out */

         pModule = PyImport_Import(pName);
         Py_DECREF(pName);

         if (pModule != NULL) {
             pFunc = PyObject_GetAttrString(pModule, argv[2]);
             /* pFunc is a new reference */

             if (pFunc && PyCallable_Check(pFunc)) {
                 pArgs = PyTuple_New(argc - 3);
                 for (i = 0; i < argc - 3; ++i) {
                     pValue = PyLong_FromLong(atoi(argv[i + 3]));
                     if (!pValue) {
                         Py_DECREF(pArgs);
                         Py_DECREF(pModule);
                         fprintf(stderr, "Cannot convert argument\n");
                         return 1;
                     }
                     /* pValue reference stolen here: */
                     PyTuple_SetItem(pArgs, i, pValue);
                 }
                 pValue = PyObject_CallObject(pFunc, pArgs);
                 Py_DECREF(pArgs);
                 if (pValue != NULL) {
                     printf("Result of call: %ld\n", PyLong_AsLong(pValue));
                     Py_DECREF(pValue);
                 }
                 else {
                     Py_DECREF(pFunc);
                     Py_DECREF(pModule);
                     PyErr_Print();
                     fprintf(stderr,"Call failed\n");
                     return 1;
                 }
             }
             else {
                 if (PyErr_Occurred())
                     PyErr_Print();
                 fprintf(stderr, "Cannot find function \"%s\"\n", argv[2]);
             }
             Py_XDECREF(pFunc);
             Py_DECREF(pModule);
         }
         else {
             PyErr_Print();
             fprintf(stderr, "Failed to load \"%s\"\n", argv[1]);
             return 1;
         }
         if (Py_FinalizeEx() < 0) {
             return 120;
         }
         return 0;
     }

This code loads a Python script using ‘argv[1]’, and calls the function
named in ‘argv[2]’.  Its integer arguments are the other values of the
‘argv’ array.  If you *note compile and link: 4747. this program (let's
call the finished executable ‘call’), and use it to execute a Python
script, such as:

     def multiply(a,b):
         print("Will compute", a, "times", b)
         c = 0
         for i in range(0, a):
             c = c + b
         return c

then the result should be:

     $ call multiply multiply 3 2
     Will compute 3 times 2
     Result of call: 6

Although the program is quite large for its functionality, most of the
code is for data conversion between Python and C, and for error
reporting.  The interesting part with respect to embedding Python starts
with

     Py_Initialize();
     pName = PyUnicode_DecodeFSDefault(argv[1]);
     /* Error checking of pName left out */
     pModule = PyImport_Import(pName);

After initializing the interpreter, the script is loaded using *note
PyImport_Import(): 136a.  This routine needs a Python string as its
argument, which is constructed using the *note PyUnicode_FromString():
4748. data conversion routine.

     pFunc = PyObject_GetAttrString(pModule, argv[2]);
     /* pFunc is a new reference */

     if (pFunc && PyCallable_Check(pFunc)) {
         ...
     }
     Py_XDECREF(pFunc);

Once the script is loaded, the name we're looking for is retrieved using
*note PyObject_GetAttrString(): 2f5.  If the name exists, and the object
returned is callable, you can safely assume that it is a function.  The
program then proceeds by constructing a tuple of arguments as normal.
The call to the Python function is then made with:

     pValue = PyObject_CallObject(pFunc, pArgs);

Upon return of the function, ‘pValue’ is either ‘NULL’ or it contains a
reference to the return value of the function.  Be sure to release the
reference after examining the value.


File: python.info,  Node: Extending Embedded Python,  Next: Embedding Python in C++,  Prev: Pure Embedding,  Up: 在其它 App 內嵌入 Python

6.3.1.4 Extending Embedded Python
.................................

Until now, the embedded Python interpreter had no access to
functionality from the application itself.  The Python API allows this
by extending the embedded interpreter.  That is, the embedded
interpreter gets extended with routines provided by the application.
While it sounds complex, it is not so bad.  Simply forget for a while
that the application starts the Python interpreter.  Instead, consider
the application to be a set of subroutines, and write some glue code
that gives Python access to those routines, just like you would write a
normal Python extension.  For example:

     static int numargs=0;

     /* Return the number of arguments of the application command line */
     static PyObject*
     emb_numargs(PyObject *self, PyObject *args)
     {
         if(!PyArg_ParseTuple(args, ":numargs"))
             return NULL;
         return PyLong_FromLong(numargs);
     }

     static PyMethodDef EmbMethods[] = {
         {"numargs", emb_numargs, METH_VARARGS,
          "Return the number of arguments received by the process."},
         {NULL, NULL, 0, NULL}
     };

     static PyModuleDef EmbModule = {
         PyModuleDef_HEAD_INIT, "emb", NULL, -1, EmbMethods,
         NULL, NULL, NULL, NULL
     };

     static PyObject*
     PyInit_emb(void)
     {
         return PyModule_Create(&EmbModule);
     }

Insert the above code just above the ‘main()’ function.  Also, insert
the following two statements before the call to *note Py_Initialize():
851.:

     numargs = argc;
     PyImport_AppendInittab("emb", &PyInit_emb);

These two lines initialize the ‘numargs’ variable, and make the
‘emb.numargs()’ function accessible to the embedded Python interpreter.
With these extensions, the Python script can do things like

     import emb
     print("Number of arguments", emb.numargs())

In a real application, the methods will expose an API of the application
to Python.


File: python.info,  Node: Embedding Python in C++,  Next: Compiling and Linking under Unix-like systems,  Prev: Extending Embedded Python,  Up: 在其它 App 內嵌入 Python

6.3.1.5 Embedding Python in C++
...............................

It is also possible to embed Python in a C++ program; precisely how this
is done will depend on the details of the C++ system used; in general
you will need to write the main program in C++, and use the C++ compiler
to compile and link your program.  There is no need to recompile Python
itself using C++.


File: python.info,  Node: Compiling and Linking under Unix-like systems,  Prev: Embedding Python in C++,  Up: 在其它 App 內嵌入 Python

6.3.1.6 Compiling and Linking under Unix-like systems
.....................................................

It is not necessarily trivial to find the right flags to pass to your
compiler (and linker) in order to embed the Python interpreter into your
application, particularly because Python needs to load library modules
implemented as C dynamic extensions (‘.so’ files) linked against it.

To find out the required compiler and linker flags, you can execute the
‘python`X.Y'-config’ script which is generated as part of the
installation process (a ‘python3-config’ script may also be available).
This script has several options, of which the following will be directly
useful to you:

   * ‘pythonX.Y-config --cflags’ will give you the recommended flags
     when compiling:

          $ /opt/bin/python3.11-config --cflags
          -I/opt/include/python3.11 -I/opt/include/python3.11 -Wsign-compare  -DNDEBUG -g -fwrapv -O3 -Wall

   * ‘pythonX.Y-config --ldflags --embed’ will give you the recommended
     flags when linking:

          $ /opt/bin/python3.11-config --ldflags --embed
          -L/opt/lib/python3.11/config-3.11-x86_64-linux-gnu -L/opt/lib -lpython3.11 -lpthread -ldl  -lutil -lm

     備註: To avoid confusion between several Python installations (and
     especially between the system Python and your own compiled Python),
     it is recommended that you use the absolute path to
     ‘python`X.Y'-config’, as in the above example.

If this procedure doesn't work for you (it is not guaranteed to work for
all Unix-like platforms; however, we welcome *note bug reports: 474e.)
you will have to read your system's documentation about dynamic linking
and/or examine Python's ‘Makefile’ (use *note
sysconfig.get_makefile_filename(): 41e9. to find its location) and
compilation options.  In this case, the *note sysconfig: c5. module is a
useful tool to programmatically extract the configuration values that
you will want to combine together.  For example:

     >>> import sysconfig
     >>> sysconfig.get_config_var('LIBS')
     '-lpthread -ldl  -lutil'
     >>> sysconfig.get_config_var('LINKFORSHARED')
     '-Xlinker -export-dynamic'


File: python.info,  Node: Python/C API 參考手冊,  Next: 安裝 Python 模組,  Prev: 擴充和嵌入 Python 直譯器,  Up: Top

7 Python/C API 參考手冊
***********************

對於想要編寫擴充模組或是嵌入 Python 的 C 和 C++ 程式設計師們，這份手冊記
錄了可使用的 API（應用程式介面）。在*note 擴充和嵌入 Python 直譯器:
1ae1.中也有相關的內容，它描述了編寫擴充的一般原則，但並沒有詳細說明 API
函式。

* Menu:

* 簡介: 簡介<10>.
* C API 穩定性::
* The Very High Level Layer::
* 參照計數: 參照計數<2>.
* 例外處理::
* 工具::
* 抽象物件層 (Abstract Objects Layer): 抽象物件層 Abstract Objects Layer.
* 具體物件層::
* Initialization, Finalization, and Threads: Initialization Finalization and Threads.
* Python 初始化設定::
* 記憶體管理::
* Object Implementation Support::
* API 和 ABI 版本管理::
* Monitoring C API::
* Generating Execution Events::


File: python.info,  Node: 簡介<10>,  Next: C API 穩定性,  Up: Python/C API 參考手冊

7.1 簡介
========

對於 Python 的應用程式開發介面使得 C 和 C++ 開發者能夠在各種層級存取
Python 直譯器。該 API 同樣可用於 C++，但為簡潔起見，通常將其稱為
Python/C API。使用 Python/C API 有兩個不同的原因，第一個是為特定目的來編
寫'擴充模組'；這些是擴充 Python 直譯器的 C 模組，這可能是最常見的用法。
第二個原因是在更大的應用程式中將 Python 作為零件使用；這種技術通常在應用
程式中稱為 'embedding'（嵌入式）Python。

編寫擴充模組是一個相對容易理解的過程，其中「食譜 (cookbook)」方法很有效
。有幾種工具可以在一定程度上自動化該過程，儘管人們從早期就將 Python 嵌入
到其他應用程式中，但嵌入 Python 的過程並不像編寫擴充那樣簡單。

不論你是嵌入還是擴充 Python，許多 API 函式都是很有用的；此外，大多數嵌入
Python 的應用程式也需要提供自定義擴充模組，因此在嘗試將 Python 嵌入實際
應用程式之前熟悉編寫擴充可能是個好主意。

* Menu:

* 編寫標準::
* 引入檔案 (include files): 引入檔案 include files.
* 有用的巨集::
* 物件、型別和參照計數::
* 例外: 例外<17>.
* 嵌入式Python::
* 除錯建置::


File: python.info,  Node: 編寫標準,  Next: 引入檔案 include files,  Up: 簡介<10>

7.1.1 編寫標準
--------------

如果你正在編寫要引入於 CPython 中的 C 程式碼，你'必須'遵循 PEP 7(1) 中定
義的指南和標準。無論你貢獻的 Python 版本如何，這些指南都適用。對於你自己
的第三方擴充模組，則不必遵循這些約定，除非你希望最終將它們貢獻給 Python。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0007/


File: python.info,  Node: 引入檔案 include files,  Next: 有用的巨集,  Prev: 編寫標準,  Up: 簡介<10>

7.1.2 引入檔案 (include files)
------------------------------

使用 Python/C API 所需的所有函式、型別和巨集的定義都透過以下這幾行來在你
的程式碼中引入：

     #define PY_SSIZE_T_CLEAN
     #include <Python.h>

這意味著會引入以下標準標頭：‘<stdio.h>’、‘<string.h>’、‘<errno.h>’、
‘<limits.h>’、‘<assert.h>’ 和 ‘<stdlib.h>’（如果可用）。

     備註: 由於 Python 可能會定義一些會影響某些系統上標準標頭檔的預處理
     器 (pre-processor)，因此你'必須'在引入任何標準標頭檔之前引入
     ‘Python.h’。

     建議在引入 ‘Python.h’ 之前都要定義 ‘PY_SSIZE_T_CLEAN’。有關此巨集的
     說明，請參閱*note 剖析引數與建置數值: 84d.。

所有定義於 Python.h 中且使用者可見的名稱（另外透過標準標頭檔引入的除外）
都具有 ‘Py’ 或 ‘_Py’ 前綴。以 ‘_Py’ 開頭的名稱供 Python 實作內部使用，擴
充編寫者不應使用。結構成員名稱沒有保留前綴。

     備註: 使用者程式碼不應定義任何以 ‘Py’ 或 ‘_Py’ 開頭的名稱。這會讓讀
     者感到困惑，並危及使用者程式碼在未來 Python 版本上的可移植性，這些
     版本可能會定義以這些前綴之一開頭的其他名稱。

標頭檔通常隨 Python 一起安裝。在 Unix 上它們位於目錄
‘`prefix'/include/pythonversion/’ 和
‘`exec_prefix'/include/pythonversion/’，其中 *note prefix: 1c62. 和
*note exec_prefix: 1c63. 由 Python 的 ‘configure’ 腳本的相應參數定義，
'version' 是 ‘'%d.%d' % sys.version_info[:2]’。在 Windows 上，標頭安裝在
‘`prefix'/include’ 中，其中 ‘prefix’ 是指定給安裝程式 (installer) 用的安
裝目錄。

要引入標頭，請將兩個（如果不同）目錄放在編譯器的引入搜索路徑 (search
path) 中。'不要'將父目錄放在搜索路徑上，然後使用 ‘#include
<pythonX.Y/Python.h>’；這會在多平台建置上壞掉，因為 *note prefix: 1c62.
下獨立於平台的標頭包括來自 *note exec_prefix: 1c63. 的平台特定標頭。

C++ 使用者應注意，儘管 API 完全使用 C 來定義，但標頭檔適當地將入口點聲明
為 ‘extern "C"’。因此，無需執行任何特殊操作即可使用 C++ 中的 API。


File: python.info,  Node: 有用的巨集,  Next: 物件、型別和參照計數,  Prev: 引入檔案 include files,  Up: 簡介<10>

7.1.3 有用的巨集
----------------

Python 標頭檔中定義了幾個有用的巨集，大多被定義在它們有用的地方附近（例
如 *note Py_RETURN_NONE: 13de.），其他是更通用的工具程式。以下並不一定是
完整的列表。

 -- C 巨集: PyMODINIT_FUNC

     Declare an extension module ‘PyInit’ initialization function.  The
     function return type is *note PyObject: 311.*.  The macro declares
     any special linkage declarations required by the platform, and for
     C++ declares the function as ‘extern "C"’.

     The initialization function must be named ‘PyInit_NAME’, where
     'name' is the name of the module, and should be the only
     non-‘static’ item defined in the module file.  Example:

          static struct PyModuleDef spam_module = {
              PyModuleDef_HEAD_INIT,
              .m_name = "spam",
              ...
          };

          PyMODINIT_FUNC
          PyInit_spam(void)
          {
              return PyModule_Create(&spam_module);
          }

 -- C 巨集: Py_ABS (x)

     回傳 ‘x’ 的絕對值。

     在 3.3 版被加入.

 -- C 巨集: Py_ALWAYS_INLINE

     要求編譯器總是嵌入靜態行內函式 (static inline function)，編譯器可以
     忽略它並決定不嵌入該函式。

     在禁用函式嵌入的除錯模式下建置 Python 時，它可用於嵌入有性能要求的
     靜態行內函式。例如，MSC 在除錯模式下建置時禁用函式嵌入。

     盲目地使用 Py_ALWAYS_INLINE 標記靜態行內函式可能會導致更差的性能（
     例如程式碼大小增加）。在成本/收益分析方面，編譯器通常比開發人員更聰
     明。

     如果 Python 是*note 在除錯模式下建置: 1de.（如果 *note Py_DEBUG:
     3f4f. 巨集有被定義），*note Py_ALWAYS_INLINE: 17b9. 巨集就什麼都不
     會做。

     它必須在函式回傳型別之前被指定。用法：

          static inline Py_ALWAYS_INLINE int random(void) { return 4; }

     在 3.11 版被加入.

 -- C 巨集: Py_CHARMASK (c)

     引數必須是 [-128, 127] 或 [0, 255] 範圍內的字元或整數。這個巨集會將
     ‘c’ 轉換為 ‘unsigned char’ 並回傳。

 -- C 巨集: Py_DEPRECATED (version)

     將其用於已棄用的聲明。巨集必須放在符號名稱之前。

     範例：

          Py_DEPRECATED(3.8) PyAPI_FUNC(int) Py_OldFunction(void);

     在 3.8 版的變更: 新增了 MSVC 支援。

 -- C 巨集: Py_GETENV (s)

     類似於 ‘getenv(s)’，但如果在命令列上傳遞了 *note -E: 901. 則回傳
     ‘NULL’ （請見 *note PyConfig.use_environment: 3a4.）。

 -- C 巨集: Py_MAX (x, y)

     回傳 ‘x’ 和 ‘y’ 之間的最大值。

     在 3.3 版被加入.

 -- C 巨集: Py_MEMBER_SIZE (type, member)

     以位元組為單位回傳結構 (‘type’) ‘member’ 的大小。

     在 3.6 版被加入.

 -- C 巨集: Py_MIN (x, y)

     回傳 ‘x’ 和 ‘y’ 之間的最小值。

     在 3.3 版被加入.

 -- C 巨集: Py_NO_INLINE

     禁用函式的嵌入。例如，它減少了 C 堆疊的消耗：對大量嵌入程式碼的
     LTO+PGO 建置很有用（請參閱 bpo-33720(1)）。

     用法：

          Py_NO_INLINE static int random(void) { return 4; }

     在 3.11 版被加入.

 -- C 巨集: Py_STRINGIFY (x)

     將 ‘x’ 轉換為 C 字串。例如 ‘Py_STRINGIFY(123)’ 會回傳 ‘"123"’。

     在 3.4 版被加入.

 -- C 巨集: Py_UNREACHABLE ()

     當你的設計中有無法達到的程式碼路徑時，請使用此選項。例如在 ‘case’ 語
     句已涵蓋了所有可能值的 ‘switch’ 陳述式中的 ‘default:’ 子句。在你可
     能想要呼叫 ‘assert(0)’ 或 ‘abort()’ 的地方使用它。

     在發布模式 (release mode) 下，巨集幫助編譯器最佳化程式碼，並避免有
     關無法存取程式碼的警告。例如該巨集是在發布模式下於 GCC 使用
     ‘__builtin_unreachable()’ 來實作。

     ‘Py_UNREACHABLE()’ 的一個用途是，在對一個永不回傳但並未聲明為
     ‘_Py_NO_RETURN’ 的函式之呼叫後使用。

     如果程式碼路徑是極不可能但在特殊情況下可以到達，則不得使用此巨集。
     例如在低記憶體條件下或系統呼叫回傳了超出預期範圍的值。在這種情況下
     ，最好將錯誤回報給呼叫者。如果無法回報錯誤則可以使用 *note
     Py_FatalError(): 927.。

     在 3.7 版被加入.

 -- C 巨集: Py_UNUSED (arg)

     將此用於函式定義中未使用的參數以消除編譯器警告。例如：‘int func(int
     a, int Py_UNUSED(b)) { return a; }’。

     在 3.4 版被加入.

 -- C 巨集: PyDoc_STRVAR (name, str)

     建立一個名為 ‘name’ 的變數，可以在文件字串中使用。如果 Python 是在
     沒有文件字串的情況下建置，則該值將為空。

     如 PEP 7(2) 中所指明，使用 *note PyDoc_STRVAR: 1876. 作為文件字串可
     以支援在沒有文件字串的情況下建置 Python。

     範例：

          PyDoc_STRVAR(pop_doc, "Remove and return the rightmost element.");

          static PyMethodDef deque_methods[] = {
              // ...
              {"pop", (PyCFunction)deque_pop, METH_NOARGS, pop_doc},
              // ...
          }

 -- C 巨集: PyDoc_STR (str)

     為給定的輸入字串建立一個文件字串，如果文件字串被禁用則建立空字串。

     如 PEP 7(3) 中所指明，使用 *note PyDoc_STR: 1710. 指定文件字串以支
     援在沒有文件字串下建置 Python。

     範例：

          static PyMethodDef pysqlite_row_methods[] = {
              {"keys", (PyCFunction)pysqlite_row_keys, METH_NOARGS,
                  PyDoc_STR("Returns the keys of the row.")},
              {NULL, NULL}
          };

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=33720

   (2) https://peps.python.org/pep-0007/

   (3) https://peps.python.org/pep-0007/


File: python.info,  Node: 物件、型別和參照計數,  Next: 例外<17>,  Prev: 有用的巨集,  Up: 簡介<10>

7.1.4 物件、型別和參照計數
--------------------------

大多數 Python/C API 函式都有一個或多個引數以及一個型別為 *note PyObject:
311.* 的回傳值，此型別是一個指標，指向一個表示任意 Python 物件的晦暗
(opaque) 資料型別。由於在大多數情況下，Python 語言以相同的方式處理所有
Python 物件型別（例如賦值、作用域規則和引數傳遞），因此它們應該由單個 C
型別來表示。幾乎所有的 Python 物件都存在於堆積 (heap) 中：你永遠不會聲明
*note PyObject: 311. 型別的自動變數或靜態變數，只能聲明 *note PyObject:
311.* 型別的指標變數。唯一的例外是型別物件；由於它們絕不能被釋放，因此它
們通常是靜態 *note PyTypeObject: a48. 物件。

所有 Python 物件（甚至是 Python 整數）都有一個型別 ('type') 和一個參照計
數 ('reference count')。一個物件的型別決定了它是什麼種類的物件（例如一個
整數、一個 list 或一個使用者定義的函式；還有更多型別，請見*note
標準型別階層: 1dd6.）。對於每個眾所周知的型別，都有一個巨集來檢查物件是
否屬於該型別；例如，若（且唯若）*a* 指向的物件是 Python list 時，
‘PyList_Check(a)’ 為真。

* Menu:

* 參照計數::
* 型別::


File: python.info,  Node: 參照計數,  Next: 型別,  Up: 物件、型別和參照計數

7.1.4.1 參照計數
................

參照計數很重要，因為現今的電腦記憶體大小是有限的（而且通常是非常有限的）
；它計算有多少個不同的地方用有了一個物件的*note 強參照: 2ee.。這樣的地方
可以是另一個物件，或者全域（或靜態）C 變數，或者某個 C 函式中的本地變數
。當一個物件的最後一個*note 強參照: 2ee.被釋放時（即其的參照計數變為零）
，該物件將被解除配置 (deallocated)。如果它包含對其他物件的參照，則它們的
參照會被釋放。如果這樣的釋放使得再也沒有任何對於它們的參照，則可以依次為
那些其他物件解除配置，依此類推。（此處相互參照物件的存在是個明顯的問題；
目前，解決方案是「就不要那樣做」。）

參照計數總是被明確地操作。正常的方法是使用巨集 *note Py_INCREF(): 514. 來
取得對於物件的參照（即參照計數加一），並使用巨集 *note Py_DECREF(): 515.
來釋放參照（即將參照計數減一）。*note Py_DECREF(): 515. 巨集比 incref 巨
集複雜得多，因為它必須檢查參照計數是否變為零，然後呼叫物件的釋放器
(deallocator)。釋放器是包含在物件型別結構中的函式指標。特定型別的釋放器
，在如果是一個複合物件型別（例如 list）時負責釋放物件中包含的其他物件的
參照，並執行任何需要的額外完結步驟。參照計數不可能溢出；至少與虛擬記憶體
中用來保存參照計數的不同記憶體位置數量一樣多的位元會被使用（假設
‘sizeof(Py_ssize_t) >= sizeof(void*)’）。因此參照計數增加是一個簡單的操
作。

沒有必要為每個包含物件指標的本地變數物件都持有一個*note 強參照: 2ee.（即
增加參照計數）。理論上，當變數指向它時，物件的參照計數會增加 1，而當變數
離開作用域時就會減少 1。然而這兩者會相互抵消，所以最後參照計數沒有改變。
使用參照計數的唯一真正原因是防止物件還有變數指向它時被解除配置。如果我們
知道至少有一個物件的其他參照生存了至少與我們的變數一樣久，就不需要臨時增
加建立新的*note 強參照: 2ee.（即增加參照計數）。出現這種情況的一個重要情
況是在從 Python 呼叫的擴充模組中作為引數傳遞給 C 函式的物件；呼叫機制保
證在呼叫期間保持對每個參數的參照。

然而，一個常見的陷阱是從一個 list 中提取一個物件並保留它一段時間而不取得
其參照。某些其他操作可能會從列表中刪除該物件，減少其參照計數並可能取消分
配它。真正的危險是看似無害的操作可能會呼叫可以執行此操作的任意 Python 程
式碼；有一個程式碼路徑允許控制權從 *note Py_DECREF(): 515. 回歸使用者，
因此幾乎任何操作都有潛在危險。

一種安全的方法是都使用通用 (generics) 操作（名稱以 ‘PyObject_’、
‘PyNumber_’、‘PySequence_’ 或 ‘PyMapping_’ 開頭的函式）。這些操作總是建
立新的對於它們回傳物件的*note 強參照: 2ee.（即增加其參照計數）。這讓呼叫
者有責任在處理完結果後呼叫 *note Py_DECREF(): 515.；這就成為第二本質。

* Menu:

* 參照計數詳細資訊::


File: python.info,  Node: 參照計數詳細資訊,  Up: 參照計數

7.1.4.2 參照計數詳細資訊
........................

Python/C API 中函式的參照計數行為最好用'參照的所有權'來解釋。所有權附屬
於參照而非物件（物件並非被擁有，它們總是共享的）。「擁有參照」意味著當不
再需要該參照時，負責在其上呼叫 Py_DECREF。所有權也可以轉移，這意味著接收
參照所有權的程式碼最終會負責在不需要參照時透過呼叫 *note Py_DECREF():
515. 或 *note Py_XDECREF(): 733. 釋放參照 -- 或者將這個責任再傳遞出去（
通常是給它的呼叫者）。當一個函式將參照的所有權傳遞給它的呼叫者時，呼叫者
被稱為接收到一個'新'參照。當沒有所有權轉移時，呼叫者被稱為'借用'參照。如
果是*note 借用參照: 2ef.就不需要做任何事情。

相反地，當呼叫的函式傳入物件的參照時，有兩種可能性：函式有'竊取 (steal)'
物件的參照，或者沒有。 '竊取參照'意味著當你將參照傳遞給函式時，該函式假
定它現在擁有該參照，並且你不再對它負責。

很少有函式會竊取參照；兩個值得注意的例外是 *note PyList_SetItem(): 46ef.
和 *note PyTuple_SetItem(): 46ee.，它們竊取了對項目的參照（但不是對項目
所在的 tuple 或 list 的參照！）。因為有著使用新建立的物件來增加
(populate) tuple 或 list 的習慣，這些函式旨在竊取參照；例如，建立 tuple
‘(1, 2, "three")’ 的程式碼可以如下所示（先暫時忘記錯誤處理；更好的編寫方
式如下所示）：

     PyObject *t;

     t = PyTuple_New(3);
     PyTuple_SetItem(t, 0, PyLong_FromLong(1L));
     PyTuple_SetItem(t, 1, PyLong_FromLong(2L));
     PyTuple_SetItem(t, 2, PyUnicode_FromString("three"));

這裡 *note PyLong_FromLong(): 173e. 會回傳一個新的參照，它立即被 *note
PyTuple_SetItem(): 46ee. 竊取。如果你想繼續使用一個物件，儘管對它的參照
將被竊取，請在呼叫參照竊取函式之前使用 *note Py_INCREF(): 514. 來獲取另
一個參照。

附帶地說，*note PyTuple_SetItem(): 46ee. 是設定 tuple 項目的'唯一'方法；
*note PySequence_SetItem(): 195a. 和 *note PyObject_SetItem(): 4764. 拒
絕這樣做，因為 tuple 是一種不可變 (immutable) 的資料型別。你應該只對你自
己建立的 tuple 使用 *note PyTuple_SetItem(): 46ee.。

可以使用 *note PyList_New(): 4765. 和 *note PyList_SetItem(): 46ef. 編寫
用於填充列表的等效程式碼。

但是在實際操作中你很少會使用這些方法來建立和增加 tuple 和 list。有一個通
用函式 *note Py_BuildValue(): 84c. 可以從 C 值建立最常見的物件，由
'format string' 引導。例如上面的兩個程式碼可以用以下程式碼替換（它還負責
了錯誤檢查）：

     PyObject *tuple, *list;

     tuple = Py_BuildValue("(iis)", 1, 2, "three");
     list = Py_BuildValue("[iis]", 1, 2, "three");

更常見的是以那些借用參照的項目來使用 *note PyObject_SetItem(): 4764. 及
其系列函式，比如傳遞給你正在編寫的函式的引數。在那種情況下，他們關於參照
的行為會比較穩健，因為你不取得新的一個參照就可以放棄參照（「讓它被竊取」
）。例如，此函式將 list（實際上是任何可變序列）的所有項目設定於給定項目
：

     int
     set_all(PyObject *target, PyObject *item)
     {
         Py_ssize_t i, n;

         n = PyObject_Length(target);
         if (n < 0)
             return -1;
         for (i = 0; i < n; i++) {
             PyObject *index = PyLong_FromSsize_t(i);
             if (!index)
                 return -1;
             if (PyObject_SetItem(target, index, item) < 0) {
                 Py_DECREF(index);
                 return -1;
             }
             Py_DECREF(index);
         }
         return 0;
     }

函式回傳值的情況略有不同。雖然傳遞對大多數函式的參照不會改變你對該參照的
所有權責任，但許多回傳物件參照的函式會給你該參照的所有權。原因很簡單：在
很多情況下，回傳的物件是即時建立的，你獲得的參照是對該物件的唯一參照。因
此回傳物件參照的通用函式，如 *note PyObject_GetItem(): 2f9. 和 *note
PySequence_GetItem(): 1959.，總是回傳一個新的參照（呼叫者成為參照的所有
者）。

重要的是要意識到你是否擁有一個函式回傳的參照只取決於你呼叫哪個函式 -- '羽
毛 (plumage)*（作為引數傳遞給函式的物件之型別）*不會進入它！'因此，如果
你使用 *note PyList_GetItem(): 313. 從 list 中提取一個項目，你不會擁有其
參照 -- 但如果你使用 *note PySequence_GetItem(): 1959. 從同一 list 中獲
取相同的項目（且恰好使用完全相同的引數），你確實會擁有對回傳物件的參照。

以下是一個範例，說明如何編寫函式來計算一個整數 list 中項目的總和；一次使
用 *note PyList_GetItem(): 313.，一次使用 *note PySequence_GetItem():
1959.：

     long
     sum_list(PyObject *list)
     {
         Py_ssize_t i, n;
         long total = 0, value;
         PyObject *item;

         n = PyList_Size(list);
         if (n < 0)
             return -1; /* Not a list */
         for (i = 0; i < n; i++) {
             item = PyList_GetItem(list, i); /* Can't fail */
             if (!PyLong_Check(item)) continue; /* Skip non-integers */
             value = PyLong_AsLong(item);
             if (value == -1 && PyErr_Occurred())
                 /* Integer too big to fit in a C long, bail out */
                 return -1;
             total += value;
         }
         return total;
     }

     long
     sum_sequence(PyObject *sequence)
     {
         Py_ssize_t i, n;
         long total = 0, value;
         PyObject *item;
         n = PySequence_Length(sequence);
         if (n < 0)
             return -1; /* Has no length */
         for (i = 0; i < n; i++) {
             item = PySequence_GetItem(sequence, i);
             if (item == NULL)
                 return -1; /* Not a sequence, or other failure */
             if (PyLong_Check(item)) {
                 value = PyLong_AsLong(item);
                 Py_DECREF(item);
                 if (value == -1 && PyErr_Occurred())
                     /* Integer too big to fit in a C long, bail out */
                     return -1;
                 total += value;
             }
             else {
                 Py_DECREF(item); /* Discard reference ownership */
             }
         }
         return total;
     }


File: python.info,  Node: 型別,  Prev: 參照計數,  Up: 物件、型別和參照計數

7.1.4.3 型別
............

有少數幾個其他的資料型別在 Python/C API 中發揮重要作用；大多數是簡單的 C
型別，例如 int、long、double 和 char*。一些結構型別被用於描述用於列出模
組所匯出的函式或新物件型別的資料屬性的靜態表，其他則用於描述複數的值。這
些將與使用它們的函式一起討論。

 -- C 型別: type Py_ssize_t
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  一個帶符號的整數型別，使得
     ‘sizeof(Py_ssize_t) == sizeof(size_t)’。 C99 沒有直接定義這樣的東西
     （size_t 是無符號整數型別）。有關詳細資訊，請參閱 PEP 353(1)。
     ‘PY_SSIZE_T_MAX’ 是 *note Py_ssize_t: a03. 型別的最大正值。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0353/


File: python.info,  Node: 例外<17>,  Next: 嵌入式Python,  Prev: 物件、型別和參照計數,  Up: 簡介<10>

7.1.5 例外
----------

如果需要特定的錯誤處理，Python 開發者就只需要處理例外；未處理的例外會自
動傳遞給呼叫者，然後傳遞給呼叫者的呼叫者，依此類推，直到它們到達頂層直譯
器，在那裡它們透過堆疊回溯 (stack trace) 回報給使用者。

然而，對於 C 開發者來說，錯誤檢查總是必須是顯式的。除非在函式的文件中另
有明確聲明，否則 Python/C API 中的所有函式都可以引發例外。通常當一個函式
遇到錯誤時，它會設定一個例外，丟棄它擁有的任何物件參照，並回傳一個錯誤指
示器。如果沒有另外文件記錄，這個指示器要麼是 ‘NULL’ 不然就是 ‘-1’，取決
於函式的回傳型別。有些函式會回傳布林值 true/false 結果，false 表示錯誤。
很少有函式不回傳明確的錯誤指示器或者有不明確的回傳值，而需要使用 *note
PyErr_Occurred(): 17f4. 明確測試錯誤。這些例外都會被明確地記錄於文件。

例外的狀態會在個別執行緒的存儲空間 (per-thread storage) 中維護（這相當於
在非執行緒應用程式中使用全域存儲空間）。執行緒可以處於兩種狀態之一：發生
例外或未發生例外。函式 *note PyErr_Occurred(): 17f4. 可用於檢查這一點：
當例外發生時，它回傳對例外型別物件的借用參照，否則回傳 ‘NULL’。設定例外
狀態的函式有很多：*note PyErr_SetString(): 522. 是最常見的（儘管不是最通
用的）設定例外狀態的函式，而 *note PyErr_Clear(): fd4. 是用來清除例外狀
態。

完整的例外狀態由三個（都可以為 ‘NULL’ 的）物件組成：例外型別、對應的例外
值和回溯。這些與 ‘sys.exc_info()’ 的 Python 結果具有相同的含義；但是它們
並不相同：Python 物件表示由 Python *note try: 68c. ...  *note except:
171. 陳述式處理的最後一個例外，而 C 層級的例外狀態僅在例外在 C 函式間傳
遞時存在，直到它到達 Python 位元組碼直譯器的主迴圈，該迴圈負責將它傳遞給
‘sys.exc_info()’ 和其系列函式。

請注意，從 Python 1.5 開始，從 Python 程式碼存取例外狀態的首選且支援執行
緒安全的方法是呼叫 *note sys.exc_info(): 630. 函式，它回傳 Python 程式碼
的個別執行緒例外狀態。此外，兩種存取例外狀態方法的語義都發生了變化，因此
捕獲例外的函式將保存和恢復其執行緒的例外狀態，從而保留其呼叫者的例外狀態
。這可以防止例外處理程式碼中的常見錯誤，這些錯誤是由看似無辜的函式覆蓋了
正在處理的例外而引起的；它還替回溯中被堆疊幀 (stack frame) 參照的物件減
少了通常不需要的生命週期延長。

作為一般原則，呼叫另一個函式來執行某些任務的函式應該檢查被呼叫函式是否引
發了例外，如果是，則將例外狀態傳遞給它的呼叫者。它應該丟棄它擁有的任何物
件參照，並回傳一個錯誤指示符，但它'不應該'設定另一個例外 -- 這將覆蓋剛剛
引發的例外，並丟失關於錯誤確切原因的重要資訊。

上面的 ‘sum_sequence()’ 範例展示了一個檢測例外並將其繼續傳遞的例子。碰巧
這個例子在檢測到錯誤時不需要清理任何擁有的參照。以下範例函式展示了一些錯
誤清理。首先，為了提醒你為什麼喜歡 Python，我們展示了等效的 Python 程式
碼：

     def incr_item(dict, key):
         try:
             item = dict[key]
         except KeyError:
             item = 0
         dict[key] = item + 1

這是相應的 C 程式碼：

     int
     incr_item(PyObject *dict, PyObject *key)
     {
         /* Objects all initialized to NULL for Py_XDECREF */
         PyObject *item = NULL, *const_one = NULL, *incremented_item = NULL;
         int rv = -1; /* Return value initialized to -1 (failure) */

         item = PyObject_GetItem(dict, key);
         if (item == NULL) {
             /* Handle KeyError only: */
             if (!PyErr_ExceptionMatches(PyExc_KeyError))
                 goto error;

             /* Clear the error and use zero: */
             PyErr_Clear();
             item = PyLong_FromLong(0L);
             if (item == NULL)
                 goto error;
         }
         const_one = PyLong_FromLong(1L);
         if (const_one == NULL)
             goto error;

         incremented_item = PyNumber_Add(item, const_one);
         if (incremented_item == NULL)
             goto error;

         if (PyObject_SetItem(dict, key, incremented_item) < 0)
             goto error;
         rv = 0; /* Success */
         /* Continue with cleanup code */

      error:
         /* Cleanup code, shared by success and failure path */

         /* Use Py_XDECREF() to ignore NULL references */
         Py_XDECREF(item);
         Py_XDECREF(const_one);
         Py_XDECREF(incremented_item);

         return rv; /* -1 for error, 0 for success */
     }

這個例子代表了在 C 語言中對使用 ‘goto’ 陳述句的認同！它闡述了以 *note
PyErr_ExceptionMatches(): 476a. 和 *note PyErr_Clear(): fd4. 來處理特定
的例外，以及以 *note Py_XDECREF(): 733. 來配置其所擁有且可能為 ‘NULL’ 的
參照（注意名稱中的 ‘'X'’；*note Py_DECREF(): 515. 在遇到 ‘NULL’ 參照時會
崩潰）。重要的是，用於保存擁有的參照的變數被初始化為 ‘NULL’ 以使其能夠順
利作用；同樣地，回傳值被初始化為 ‘-1’（失敗），並且僅在最後一次呼叫成功
後才設定為成功。


File: python.info,  Node: 嵌入式Python,  Next: 除錯建置,  Prev: 例外<17>,  Up: 簡介<10>

7.1.6 嵌入式Python
------------------

只有 Python 直譯器的嵌入者（而不是擴充編寫者）需要擔心的一項重要任務是
Python 直譯器的初始化與完成階段。直譯器的大部分功能只能在直譯器初始化後
使用。

基本的初始化函式是 *note Py_Initialize(): 851.。這會初始化帶有載入模組的
表，並建立基礎模組 *note builtins: e.、*note __main__: 1. 和 *note sys:
c3.。它還會初始化模組搜索路徑 (‘sys.path’)。

*note Py_Initialize(): 851. 不設定「腳本引數列表 (script argument list)」
(‘sys.argv’)。如果稍後將要執行的 Python 程式碼需要此變數，則必須設定
*note PyConfig.argv: 38e. 和 *note PyConfig.parse_argv: 182b.，請見
*note Python 初始化配置: 372.。

在大多數系統上（特別是在 Unix 和 Windows 上，儘管細節略有不同），*note
Py_Initialize(): 851. 會假設Python 函式庫相對於 Python 直譯器可執行檔案
的位置固定，並根據其對標準 Python 直譯器可執行檔案位置的最佳猜測來計算模
組搜索路徑。或者更詳細地說，它會在 shell 命令搜索路徑（環境變數 ‘PATH’）
中找到名為 ‘python’ 的可執行檔案，並在其父目錄中查找一個名為
‘lib/python`X.Y'’ 的目錄的相對位置。

例如，如果在 ‘/usr/local/bin/python’ 中找到 Python 可執行檔案，它將假定
函式庫位於 ‘/usr/local/lib/python`X.Y'’ 中。（事實上這個特定的路徑也是「
後備 (fallback)」位置，當在 ‘PATH’ 中找不到名為 ‘python’ 的可執行檔案時
使用。）使用者可以透過設定環境變數來覆蓋此行為 *note PYTHONHOME: 387.，
或者透過設定 *note PYTHONPATH: fbe. 在標準路徑前面插入額外的目錄。

The embedding application can steer the search by setting *note
PyConfig.program_name: 38f. 'before' calling *note
Py_InitializeFromConfig(): 390.  Note that *note PYTHONHOME: 387. still
overrides this and *note PYTHONPATH: fbe. is still inserted in front of
the standard path.  An application that requires total control has to
provide its own implementation of *note Py_GetPath(): 37e, *note
Py_GetPrefix(): 380, *note Py_GetExecPrefix(): 37c, and *note
Py_GetProgramFullPath(): 382. (all defined in ‘Modules/getpath.c’).

有時會希望能夠「取消初始化 (uninitialize)」Python。例如，應用程式可能想
要重新開始（再次呼叫 *note Py_Initialize(): 851.）或者應用程式簡單地完成
了對 Python 的使用並想要釋放 Python 分配的記憶體。這可以透過呼叫 *note
Py_FinalizeEx(): cbc. 來完成。如果 Python 當前處於初始化狀態，函式 *note
Py_IsInitialized(): 476d. 會回傳 true。有關這些功能的更多資訊將在後面的
章節中給出。請注意 *note Py_FinalizeEx(): cbc. '不會'釋放由 Python 直譯
器分配的所有記憶體，例如目前無法釋放被擴充模組所分配的記憶體。


File: python.info,  Node: 除錯建置,  Prev: 嵌入式Python,  Up: 簡介<10>

7.1.7 除錯建置
--------------

Python 可以在建置時使用多個巨集來啟用對直譯器和擴充模組的額外檢查，這些
檢查往往會在執行環境 (runtime) 增加大量開銷 (overhead)，因此預設情況下不
啟用它們。

Python 原始碼發佈版本中的 ‘Misc/SpecialBuilds.txt’ 檔案有一份包含多種除
錯構置的完整列表，為支援追蹤參照計數、為記憶體分配器除錯或對主直譯器迴圈
進行低階分析的建置。本節的其餘部分將僅描述最常用的建置。

 -- C 巨集: Py_DEBUG

使用定義的 ‘Py_DEBUG’ 巨集編譯直譯器會生成 *note Python 的除錯建置:
1de.。 ‘Py_DEBUG’ 在 Unix 建置中要透過在 ‘./configure’ 命令中加入 *note
-with-pydebug: 3d8. 來啟用。非 Python 限定的 ‘_DEBUG’ 巨集的存在也暗示了
這一點。當 ‘Py_DEBUG’ 在 Unix 建置中啟用時，編譯器最佳化會被禁用。

除了下面描述的參照計數除錯之外，還會執行額外的檢查，請參閱 *note Python
除錯建置: 1de.。

定義 ‘Py_TRACE_REFS’ 來啟用參照追蹤（參見*note 調用 -with-trace-refs
選項: 317.）。當有定義時，透過向每個 *note PyObject: 311. 新增兩個額外欄
位來維護有效物件的循環雙向鍊表 (circular doubly linked list)。全體分配也
有被追蹤。退出時將印出所有現行參照。（在交互模式下，這發生在直譯器運行的
每個陳述句之後。）

有關更多詳細資訊，請參閱 Python 原始碼發布版中的
‘Misc/SpecialBuilds.txt’。


File: python.info,  Node: C API 穩定性,  Next: The Very High Level Layer,  Prev: 簡介<10>,  Up: Python/C API 參考手冊

7.2 C API 穩定性
================

除非有另外記錄於文件，Python 的 C API 被包含在向後相容性策略 PEP 387(1)
中。大多數改動都是相容於原始碼的（通常只會增加新的 API）。更改現有 API 或
刪除 API 僅在棄用期後或修復嚴重問題時進行。

CPython 的應用程式二進位介面 (Application Binary Interface, ABI) 在次要
版本中是向前和向後相容的（如果它們以相同的方式編譯；請參閱下面的*note
平台注意事項: 4772.）。因此，為 Python 3.10.0 編譯的程式碼將能夠在
3.10.8 上運行，反之亦然，但 3.9.x 和 3.11.x 就需要分別編譯。

C API 有兩層級，有不同的穩定性期望：

   - *note 不穩定 API: 4ed.，可能會在次要版本中發生變化，而沒有棄用階段
     。會在名稱中以 ‘PyUnstable’ 前綴來標記。

   - *note 受限 API: 318.，在多個次要版本之間相容。當有定義 *note
     Py_LIMITED_API: 35a. 時，只有這個子集會從 ‘Python.h’ 公開。

下面將更詳細地討論這些內容。

帶有底線前綴的名稱是私有 API (private API)，像是 ‘_Py_InternalState’，即
使在補丁版本 (patch release) 中也可能被更改，不會另行通知。如果你需要使
用這個 API，可以聯繫 CPython 開發者(2) 並針對你的使用方法來討論是否新增
公開的 API。

* Menu:

* 不穩定的 C API::
* 穩定的應用程式二進位介面::
* 平台注意事項::
* 受限 API 的內容::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0387/

   (2) https://discuss.python.org/c/core-dev/c-api/30


File: python.info,  Node: 不穩定的 C API,  Next: 穩定的應用程式二進位介面,  Up: C API 穩定性

7.2.1 不穩定的 C API
--------------------

任何以 ‘PyUnstable’ 前綴命名的 API 都會公開 CPython 實作細節，並可能在每
個次要版本中進行更改（例如從 3.9 到 3.10），而不會出現任何棄用警告。但是
它不會在錯誤修復發布版本中發生變化（例如從 3.10.0 到 3.10.1）。

它通常用於專門的低階工具，例如偵錯器。

使用此 API 的專案應該要遵循 CPython 開發細節，並花費額外的力氣來針對這些
變動來做調整。


File: python.info,  Node: 穩定的應用程式二進位介面,  Next: 平台注意事項,  Prev: 不穩定的 C API,  Up: C API 穩定性

7.2.2 穩定的應用程式二進位介面
------------------------------

為簡單起見，本文件討論'擴充 (extension)'，但受限 API 和穩定 ABI 在所有
API 使用方式中都以相同的方式運作 - 例如在嵌入式 Python (embedding
Python) 中。

* Menu:

* 受限 C API::
* 穩定 ABI::
* 受限 API 範圍和性能::
* 受限 API 注意事項::


File: python.info,  Node: 受限 C API,  Next: 穩定 ABI,  Up: 穩定的應用程式二進位介面

7.2.2.1 受限 C API
..................

Python 3.2 引入了'受限 API (Limited API)'，它是 Python C API 的一個子集
。僅使用受限 API 的擴充可以只編譯一次就使用於多個版本的 Python。受限 API
的內容*note 列在下方: 73e.。

 -- C 巨集: Py_LIMITED_API

     在包含 ‘Python.h’ 之前定義此巨集以選擇只使用受限 API，並挑選受限
     API 版本。

     將 ‘Py_LIMITED_API’ 定義為對應於你的擴充有支援的最低 Python 版本的
     *note PY_VERSION_HEX: 6fb. 值。該擴充無需重新編譯即可與從指定版本開
     始的所有 Python 3 版本一起使用，並且可以使用過去版本有引入的受限
     API。

     與其直接使用 ‘PY_VERSION_HEX’ 巨集，不如寫死 (hardcode) 最小次要版
     本（例如代表 Python 3.10 的 ‘0x030A0000’），以便在使用未來的 Python
     版本進行編譯時仍保持穩定性。

     你還可以將 ‘Py_LIMITED_API’ 定義為 ‘3’，這與 ‘0x03020000’（Python
     3.2，引入了受限 API 的版本）相同。


File: python.info,  Node: 穩定 ABI,  Next: 受限 API 範圍和性能,  Prev: 受限 C API,  Up: 穩定的應用程式二進位介面

7.2.2.2 穩定 ABI
................

為了實現它，Python 提供了一個'穩定 ABI (Stable ABI)'：一組將在各個
Python 3.x 版本之間保持相容的符號。

穩定 ABI 被包含在*note 受限 API: 318. 中開放的符號，但也包含其他符號 - 例
如，支援舊版受限 API 所必需的函式。

在 Windows 上，使用穩定 ABI 的擴充應該連接到 ‘python3.dll’ 而不是特定版
本的函式庫，例如 ‘python39.dll’。

在某些平台上，Python 將查找並加載以 ‘abi3’ 標籤命名的共享函式庫檔案（例
如 ‘mymodule.abi3.so’）。它不檢查此類擴充是否符合穩定的 ABI。確保的責任
在使用者（或者打包工具）身上，例如使用 3.10+ 受限 API 建置的擴充不會為較
低版本的 Python 所安裝。

穩定 ABI 中的所有函式都作為函式存在於 Python 的共享函式庫中，而不僅是作
為巨集。這使得它們可被用於不使用 C 預處理器 (preprocessor) 的語言。


File: python.info,  Node: 受限 API 範圍和性能,  Next: 受限 API 注意事項,  Prev: 穩定 ABI,  Up: 穩定的應用程式二進位介面

7.2.2.3 受限 API 範圍和性能
...........................

受限 API 的目標是允許使用完整的 C API 進行所有可能的操作，但可能會降低性
能。

例如，雖然 *note PyList_GetItem(): 313. 可用，但它的「不安全」巨集變體
*note PyList_GET_ITEM(): 4779. 為不可用。巨集運行可以更快，因為它可以依
賴 list 物件的特定版本實作細節。

如果沒有定義 ‘Py_LIMITED_API’，一些 C API 函式將被嵌入或被替換為巨集。定
義 ‘Py_LIMITED_API’ 會禁用嵌入，從而隨著 Python 資料結構的改進而提高穩定
性，但可能會降低性能。

通過省略 ‘Py_LIMITED_API’ 定義，可以使用特定版本的 ABI 編譯受限 API 擴充
。這可以提高該 Python 版本的性能，但會限制相容性。使用 ‘Py_LIMITED_API’
編譯將產生一個擴充，可以在特定版本的擴充不可用的地方發布 — 例如，用於即
將發布的 Python 版本的預發布版本 (prerelease)。


File: python.info,  Node: 受限 API 注意事項,  Prev: 受限 API 範圍和性能,  Up: 穩定的應用程式二進位介面

7.2.2.4 受限 API 注意事項
.........................

請注意，使用 ‘Py_LIMITED_API’ 進行編譯'不'完全保證程式碼符合*note 受限
API: 318. 或*note 穩定 ABI: 4777.。‘Py_LIMITED_API’ 僅涵蓋定義，但 API 還
包括其他議題，例如預期的語義 (semantic)。

‘Py_LIMITED_API’ 無法防範的一個問題是使用在較低 Python 版本中無效的引數
來呼叫函式。例如一個開始接受 ‘NULL’ 作為引數的函式。在 Python 3.9 中，
‘NULL’ 現在代表選擇預設行為，但在 Python 3.8 中，引數將被直接使用，導致
‘NULL’ 取消參照 (dereference) 且崩潰 (crash)。類似的引數適用於結構
(struct) 的欄位。

另一個問題是，當有定義 ‘Py_LIMITED_API’ 時，一些結構欄位目前不會被隱藏，
即使它們是受限 API 的一部分。

出於這些原因，我們建議要以它支援的'所有'次要 Python 版本來測試擴充，並且
最好使用'最低'版本進行建置。

我們也建議要查看所有使用過的 API 的文件，檢查它是否明確屬於受限 API。即
使有定義 ‘Py_LIMITED_API’，一些私有聲明也會因為技術原因（或者甚至是無意
地，例如臭蟲）而被公開出來。

另請注意，受限 API 不一定是穩定的：在 Python 3.8 中使用 ‘Py_LIMITED_API’
進行編譯意味著擴充將能以 Python 3.12 運行，但不一定能以 Python 3.12 '編
譯'。特別是如果穩定 ABI 保持穩定，部分受限 API 可能會被棄用和刪除。


File: python.info,  Node: 平台注意事項,  Next: 受限 API 的內容,  Prev: 穩定的應用程式二進位介面,  Up: C API 穩定性

7.2.3 平台注意事項
------------------

ABI 穩定性不僅取決於 Python，還取決於使用的編譯器、低階函式庫和編譯器選
項。出於*note 穩定 ABI: 4777. 的目的，這些細節定義了一個「平台」。它們通
常取決於作業系統種類和處理器架構

每個特定的 Python 發布者都有責任確保特定平台上的所有 Python 版本都以不破
壞穩定 ABI 的方式建置。‘python.org’ 和許多第三方發布者發布的 Windows 和
macOS 版本就是這種情況。


File: python.info,  Node: 受限 API 的內容,  Prev: 平台注意事項,  Up: C API 穩定性

7.2.4 受限 API 的內容
---------------------

目前，*note 受限 API: 318. 包括以下項目：

   * *note PY_VECTORCALL_ARGUMENTS_OFFSET: 503.

   * *note PyAIter_Check(): 477d.

   * *note PyArg_Parse(): 18e9.

   * *note PyArg_ParseTuple(): 517.

   * *note PyArg_ParseTupleAndKeywords(): 2e9.

   * *note PyArg_UnpackTuple(): 1476.

   * *note PyArg_VaParse(): 477e.

   * *note PyArg_VaParseTupleAndKeywords(): 2ea.

   * *note PyArg_ValidateKeywordArguments(): 477f.

   * ‘PyBaseObject_Type’

   * *note PyBool_FromLong(): 4780.

   * *note PyBool_Type: 4781.

   * *note PyBuffer_FillContiguousStrides(): 703.

   * *note PyBuffer_FillInfo(): 704.

   * *note PyBuffer_FromContiguous(): 700.

   * *note PyBuffer_GetPointer(): 6fd.

   * *note PyBuffer_IsContiguous(): 702.

   * *note PyBuffer_Release(): 36a.

   * *note PyBuffer_SizeFromFormat(): 6fe.

   * *note PyBuffer_ToContiguous(): 6ff.

   * ‘PyByteArrayIter_Type’

   * *note PyByteArray_AsString(): 4782.

   * *note PyByteArray_Concat(): 4783.

   * *note PyByteArray_FromObject(): 1324.

   * *note PyByteArray_FromStringAndSize(): 1325.

   * *note PyByteArray_Resize(): 4784.

   * *note PyByteArray_Size(): 4785.

   * *note PyByteArray_Type: 4786.

   * ‘PyBytesIter_Type’

   * *note PyBytes_AsString(): 82b.

   * *note PyBytes_AsStringAndSize(): 4787.

   * *note PyBytes_Concat(): 4788.

   * *note PyBytes_ConcatAndDel(): 4789.

   * ‘PyBytes_DecodeEscape()’

   * *note PyBytes_FromFormat(): 192f.

   * *note PyBytes_FromFormatV(): 478a.

   * *note PyBytes_FromObject(): 478b.

   * *note PyBytes_FromString(): 478c.

   * *note PyBytes_FromStringAndSize(): 1323.

   * ‘PyBytes_Repr()’

   * *note PyBytes_Size(): 478d.

   * *note PyBytes_Type: 478e.

   * *note PyCFunction: 13e2.

   * *note PyCFunctionFast: 478f.

   * *note PyCFunctionFastWithKeywords: 4790.

   * *note PyCFunctionWithKeywords: 4791.

   * ‘PyCFunction_GetFlags()’

   * ‘PyCFunction_GetFunction()’

   * ‘PyCFunction_GetSelf()’

   * *note PyCFunction_New(): 17f6.

   * *note PyCFunction_NewEx(): 1891.

   * ‘PyCFunction_Type’

   * *note PyCMethod_New(): 17f0.

   * *note PyCallIter_New(): 4792.

   * *note PyCallIter_Type: 4793.

   * *note PyCallable_Check(): 4794.

   * *note PyCapsule_Destructor: 4795.

   * *note PyCapsule_GetContext(): 4796.

   * *note PyCapsule_GetDestructor(): 4797.

   * *note PyCapsule_GetName(): 4798.

   * *note PyCapsule_GetPointer(): 4799.

   * *note PyCapsule_Import(): 1770.

   * *note PyCapsule_IsValid(): 12e9.

   * *note PyCapsule_New(): 46f9.

   * *note PyCapsule_SetContext(): 479a.

   * *note PyCapsule_SetDestructor(): 479b.

   * *note PyCapsule_SetName(): 479c.

   * *note PyCapsule_SetPointer(): 479d.

   * ‘PyCapsule_Type’

   * ‘PyClassMethodDescr_Type’

   * *note PyCodec_BackslashReplaceErrors(): 479e.

   * *note PyCodec_Decode(): 3c7.

   * *note PyCodec_Decoder(): 479f.

   * *note PyCodec_Encode(): 3c8.

   * *note PyCodec_Encoder(): 47a0.

   * *note PyCodec_IgnoreErrors(): 47a1.

   * *note PyCodec_IncrementalDecoder(): 47a2.

   * *note PyCodec_IncrementalEncoder(): 47a3.

   * *note PyCodec_KnownEncoding(): 47a4.

   * *note PyCodec_LookupError(): 47a5.

   * *note PyCodec_NameReplaceErrors(): e51.

   * *note PyCodec_Register(): 47a6.

   * *note PyCodec_RegisterError(): 47a7.

   * *note PyCodec_ReplaceErrors(): 47a8.

   * *note PyCodec_StreamReader(): 47a9.

   * *note PyCodec_StreamWriter(): 47aa.

   * *note PyCodec_StrictErrors(): 47ab.

   * *note PyCodec_Unregister(): 83b.

   * *note PyCodec_XMLCharRefReplaceErrors(): 47ac.

   * *note PyComplex_FromDoubles(): 47ad.

   * *note PyComplex_ImagAsDouble(): 158e.

   * *note PyComplex_RealAsDouble(): 158d.

   * *note PyComplex_Type: 47ae.

   * *note PyDescr_NewClassMethod(): 47af.

   * *note PyDescr_NewGetSet(): 47b0.

   * *note PyDescr_NewMember(): 47b1.

   * *note PyDescr_NewMethod(): 1890.

   * ‘PyDictItems_Type’

   * ‘PyDictIterItem_Type’

   * ‘PyDictIterKey_Type’

   * ‘PyDictIterValue_Type’

   * ‘PyDictKeys_Type’

   * *note PyDictProxy_New(): 47b2.

   * ‘PyDictProxy_Type’

   * ‘PyDictRevIterItem_Type’

   * ‘PyDictRevIterKey_Type’

   * ‘PyDictRevIterValue_Type’

   * ‘PyDictValues_Type’

   * *note PyDict_Clear(): 47b3.

   * *note PyDict_Contains(): 310.

   * *note PyDict_Copy(): 360.

   * *note PyDict_DelItem(): 47b4.

   * *note PyDict_DelItemString(): 47b5.

   * *note PyDict_GetItem(): 35b.

   * *note PyDict_GetItemRef(): 30a.

   * *note PyDict_GetItemString(): 35c.

   * *note PyDict_GetItemStringRef(): 30b.

   * *note PyDict_GetItemWithError(): 30c.

   * *note PyDict_Items(): 47b6.

   * *note PyDict_Keys(): 47b7.

   * *note PyDict_Merge(): 47b8.

   * *note PyDict_MergeFromSeq2(): 47b9.

   * *note PyDict_New(): 47ba.

   * *note PyDict_Next(): 1505.

   * *note PyDict_SetItem(): 46f0.

   * *note PyDict_SetItemString(): 14f3.

   * *note PyDict_Size(): 47bb.

   * *note PyDict_Type: 47bc.

   * *note PyDict_Update(): 47bd.

   * *note PyDict_Values(): 47be.

   * ‘PyEllipsis_Type’

   * ‘PyEnum_Type’

   * *note PyErr_BadArgument(): 47bf.

   * *note PyErr_BadInternalCall(): 47c0.

   * *note PyErr_CheckSignals(): 40d.

   * *note PyErr_Clear(): fd4.

   * ‘PyErr_Display()’

   * *note PyErr_DisplayException(): 3ca.

   * *note PyErr_ExceptionMatches(): 476a.

   * *note PyErr_Fetch(): 3bb.

   * *note PyErr_Format(): e53.

   * *note PyErr_FormatV(): e52.

   * *note PyErr_GetExcInfo(): 716.

   * *note PyErr_GetHandledException(): 713.

   * *note PyErr_GetRaisedException(): 3bc.

   * *note PyErr_GivenExceptionMatches(): 47c1.

   * *note PyErr_NewException(): 1202.

   * *note PyErr_NewExceptionWithDoc(): 1201.

   * *note PyErr_NoMemory(): 46d3.

   * *note PyErr_NormalizeException(): 3bd.

   * *note PyErr_Occurred(): 17f4.

   * *note PyErr_Print(): 1847.

   * *note PyErr_PrintEx(): 47c2.

   * ‘PyErr_ProgramText()’

   * *note PyErr_ResourceWarning(): cbe.

   * *note PyErr_Restore(): 3be.

   * *note PyErr_SetExcFromWindowsErr(): 47c3.

   * *note PyErr_SetExcFromWindowsErrWithFilename(): 1615.

   * *note PyErr_SetExcFromWindowsErrWithFilenameObject(): 47c4.

   * *note PyErr_SetExcFromWindowsErrWithFilenameObjects(): 47c5.

   * *note PyErr_SetExcInfo(): 715.

   * *note PyErr_SetFromErrno(): 46d2.

   * *note PyErr_SetFromErrnoWithFilename(): 1614.

   * *note PyErr_SetFromErrnoWithFilenameObject(): 47c6.

   * *note PyErr_SetFromErrnoWithFilenameObjects(): 47c7.

   * *note PyErr_SetFromWindowsErr(): 47c8.

   * *note PyErr_SetFromWindowsErrWithFilename(): 1616.

   * *note PyErr_SetHandledException(): 714.

   * *note PyErr_SetImportError(): ce5.

   * *note PyErr_SetImportErrorSubclass(): cbd.

   * *note PyErr_SetInterrupt(): 47c9.

   * *note PyErr_SetInterruptEx(): 842.

   * *note PyErr_SetNone(): 47ca.

   * *note PyErr_SetObject(): 521.

   * *note PyErr_SetRaisedException(): 3bf.

   * *note PyErr_SetString(): 522.

   * *note PyErr_SyntaxLocation(): 47cb.

   * *note PyErr_SyntaxLocationEx(): 47cc.

   * *note PyErr_WarnEx(): 13b8.

   * *note PyErr_WarnExplicit(): 161d.

   * *note PyErr_WarnFormat(): 47cd.

   * *note PyErr_WriteUnraisable(): 328.

   * *note PyEval_AcquireThread(): 375.

   * *note PyEval_EvalCode(): 82a.

   * *note PyEval_EvalCodeEx(): 166b.

   * *note PyEval_EvalFrame(): 47ce.

   * *note PyEval_EvalFrameEx(): fd1.

   * *note PyEval_GetBuiltins(): 348.

   * *note PyEval_GetFrame(): 16bf.

   * *note PyEval_GetFrameBuiltins(): 345.

   * *note PyEval_GetFrameGlobals(): 346.

   * *note PyEval_GetFrameLocals(): 347.

   * *note PyEval_GetFuncDesc(): 47cf.

   * *note PyEval_GetFuncName(): 47d0.

   * *note PyEval_GetGlobals(): 349.

   * *note PyEval_GetLocals(): 34a.

   * *note PyEval_InitThreads(): 1535.

   * *note PyEval_ReleaseThread(): 47d1.

   * *note PyEval_RestoreThread(): 374.

   * *note PyEval_SaveThread(): 373.

   * ‘PyExc_ArithmeticError’

   * ‘PyExc_AssertionError’

   * ‘PyExc_AttributeError’

   * ‘PyExc_BaseException’

   * ‘PyExc_BaseExceptionGroup’

   * ‘PyExc_BlockingIOError’

   * ‘PyExc_BrokenPipeError’

   * ‘PyExc_BufferError’

   * ‘PyExc_BytesWarning’

   * ‘PyExc_ChildProcessError’

   * ‘PyExc_ConnectionAbortedError’

   * ‘PyExc_ConnectionError’

   * ‘PyExc_ConnectionRefusedError’

   * ‘PyExc_ConnectionResetError’

   * ‘PyExc_DeprecationWarning’

   * ‘PyExc_EOFError’

   * ‘PyExc_EncodingWarning’

   * ‘PyExc_EnvironmentError’

   * ‘PyExc_Exception’

   * ‘PyExc_FileExistsError’

   * ‘PyExc_FileNotFoundError’

   * ‘PyExc_FloatingPointError’

   * ‘PyExc_FutureWarning’

   * ‘PyExc_GeneratorExit’

   * ‘PyExc_IOError’

   * ‘PyExc_ImportError’

   * ‘PyExc_ImportWarning’

   * ‘PyExc_IndentationError’

   * ‘PyExc_IndexError’

   * ‘PyExc_InterruptedError’

   * ‘PyExc_IsADirectoryError’

   * ‘PyExc_KeyError’

   * ‘PyExc_KeyboardInterrupt’

   * ‘PyExc_LookupError’

   * ‘PyExc_MemoryError’

   * ‘PyExc_ModuleNotFoundError’

   * ‘PyExc_NameError’

   * ‘PyExc_NotADirectoryError’

   * ‘PyExc_NotImplementedError’

   * ‘PyExc_OSError’

   * ‘PyExc_OverflowError’

   * ‘PyExc_PendingDeprecationWarning’

   * ‘PyExc_PermissionError’

   * ‘PyExc_ProcessLookupError’

   * ‘PyExc_RecursionError’

   * ‘PyExc_ReferenceError’

   * ‘PyExc_ResourceWarning’

   * ‘PyExc_RuntimeError’

   * ‘PyExc_RuntimeWarning’

   * ‘PyExc_StopAsyncIteration’

   * ‘PyExc_StopIteration’

   * ‘PyExc_SyntaxError’

   * ‘PyExc_SyntaxWarning’

   * ‘PyExc_SystemError’

   * ‘PyExc_SystemExit’

   * ‘PyExc_TabError’

   * ‘PyExc_TimeoutError’

   * ‘PyExc_TypeError’

   * ‘PyExc_UnboundLocalError’

   * ‘PyExc_UnicodeDecodeError’

   * ‘PyExc_UnicodeEncodeError’

   * ‘PyExc_UnicodeError’

   * ‘PyExc_UnicodeTranslateError’

   * ‘PyExc_UnicodeWarning’

   * ‘PyExc_UserWarning’

   * ‘PyExc_ValueError’

   * ‘PyExc_Warning’

   * ‘PyExc_WindowsError’

   * ‘PyExc_ZeroDivisionError’

   * ‘PyExceptionClass_Name()’

   * *note PyException_GetArgs(): 510.

   * *note PyException_GetCause(): 47d2.

   * *note PyException_GetContext(): 47d3.

   * *note PyException_GetTraceback(): 47d4.

   * *note PyException_SetArgs(): 511.

   * *note PyException_SetCause(): 47d5.

   * *note PyException_SetContext(): 47d6.

   * *note PyException_SetTraceback(): 18ef.

   * *note PyFile_FromFd(): 47d7.

   * *note PyFile_GetLine(): 47d8.

   * *note PyFile_WriteObject(): 47d9.

   * *note PyFile_WriteString(): 47da.

   * ‘PyFilter_Type’

   * *note PyFloat_AsDouble(): a0c.

   * *note PyFloat_FromDouble(): 47db.

   * *note PyFloat_FromString(): 47dc.

   * *note PyFloat_GetInfo(): 135e.

   * *note PyFloat_GetMax(): 135c.

   * *note PyFloat_GetMin(): 135d.

   * *note PyFloat_Type: 47dd.

   * *note PyFrameObject: 72d.

   * *note PyFrame_GetCode(): 72e.

   * *note PyFrame_GetLineNumber(): 72f.

   * *note PyFrozenSet_New(): 13b3.

   * *note PyFrozenSet_Type: 47de.

   * *note PyGC_Collect(): 932.

   * *note PyGC_Disable(): 849.

   * *note PyGC_Enable(): 848.

   * *note PyGC_IsEnabled(): 84a.

   * *note PyGILState_Ensure(): 376.

   * *note PyGILState_GetThisThreadState(): 47df.

   * *note PyGILState_Release(): 377.

   * ‘PyGILState_STATE’

   * *note PyGetSetDef: b5f.

   * ‘PyGetSetDescr_Type’

   * *note PyImport_AddModule(): 2ed.

   * *note PyImport_AddModuleObject(): 47e0.

   * *note PyImport_AddModuleRef(): 2ec.

   * *note PyImport_AppendInittab(): 16a6.

   * *note PyImport_ExecCodeModule(): 47e1.

   * *note PyImport_ExecCodeModuleEx(): 47e2.

   * *note PyImport_ExecCodeModuleObject(): 47e3.

   * *note PyImport_ExecCodeModuleWithPathnames(): 47e4.

   * *note PyImport_GetImporter(): 1613.

   * *note PyImport_GetMagicNumber(): 113b.

   * *note PyImport_GetMagicTag(): 47e5.

   * *note PyImport_GetModule(): b5a.

   * *note PyImport_GetModuleDict(): 47e6.

   * *note PyImport_Import(): 136a.

   * *note PyImport_ImportFrozenModule(): 47e7.

   * *note PyImport_ImportFrozenModuleObject(): 47e8.

   * *note PyImport_ImportModule(): 389.

   * *note PyImport_ImportModuleLevel(): 113c.

   * *note PyImport_ImportModuleLevelObject(): 47e9.

   * *note PyImport_ImportModuleNoBlock(): 388.

   * *note PyImport_ReloadModule(): 47ea.

   * *note PyIndex_Check(): 92e.

   * *note PyInterpreterState: 862.

   * *note PyInterpreterState_Clear(): 3ff4.

   * *note PyInterpreterState_Delete(): 47eb.

   * *note PyInterpreterState_Get(): 378.

   * *note PyInterpreterState_GetDict(): 47ec.

   * *note PyInterpreterState_GetID(): b6d.

   * *note PyInterpreterState_New(): 3ff5.

   * *note PyIter_Check(): 17f7.

   * *note PyIter_Next(): 47ed.

   * *note PyIter_Send(): 83c.

   * ‘PyListIter_Type’

   * ‘PyListRevIter_Type’

   * *note PyList_Append(): 47ee.

   * *note PyList_AsTuple(): 47ef.

   * *note PyList_GetItem(): 313.

   * *note PyList_GetItemRef(): 312.

   * *note PyList_GetSlice(): 47f0.

   * *note PyList_Insert(): 47f1.

   * *note PyList_New(): 4765.

   * *note PyList_Reverse(): 47f2.

   * *note PyList_SetItem(): 46ef.

   * *note PyList_SetSlice(): 47f3.

   * *note PyList_Size(): 1387.

   * *note PyList_Sort(): 47f4.

   * *note PyList_Type: 4711.

   * *note PyLongObject: 52e.

   * ‘PyLongRangeIter_Type’

   * *note PyLong_AsDouble(): 47f5.

   * *note PyLong_AsInt(): 315.

   * *note PyLong_AsLong(): 316.

   * *note PyLong_AsLongAndOverflow(): 11ff.

   * *note PyLong_AsLongLong(): 47f6.

   * *note PyLong_AsLongLongAndOverflow(): 11fe.

   * *note PyLong_AsSize_t(): 47f7.

   * *note PyLong_AsSsize_t(): 47f8.

   * *note PyLong_AsUnsignedLong(): 47f9.

   * *note PyLong_AsUnsignedLongLong(): 122c.

   * *note PyLong_AsUnsignedLongLongMask(): 18eb.

   * *note PyLong_AsUnsignedLongMask(): 47fa.

   * *note PyLong_AsVoidPtr(): 47fb.

   * *note PyLong_FromDouble(): 8e6.

   * *note PyLong_FromLong(): 173e.

   * *note PyLong_FromLongLong(): 173f.

   * *note PyLong_FromSize_t(): 18c8.

   * *note PyLong_FromSsize_t(): 47fc.

   * *note PyLong_FromString(): 47fd.

   * *note PyLong_FromUnsignedLong(): 18c6.

   * *note PyLong_FromUnsignedLongLong(): 18c7.

   * *note PyLong_FromVoidPtr(): 47fe.

   * *note PyLong_GetInfo(): 47ff.

   * *note PyLong_Type: 4800.

   * ‘PyMap_Type’

   * *note PyMapping_Check(): 4801.

   * *note PyMapping_GetItemString(): 2fa.

   * *note PyMapping_GetOptionalItem(): 2f7.

   * *note PyMapping_GetOptionalItemString(): 2f8.

   * *note PyMapping_HasKey(): 301.

   * *note PyMapping_HasKeyString(): 303.

   * *note PyMapping_HasKeyStringWithError(): 302.

   * *note PyMapping_HasKeyWithError(): 300.

   * *note PyMapping_Items(): b65.

   * *note PyMapping_Keys(): b63.

   * *note PyMapping_Length(): 4802.

   * *note PyMapping_SetItemString(): 4803.

   * *note PyMapping_Size(): 195c.

   * *note PyMapping_Values(): b64.

   * *note PyMem_Calloc(): e4f.

   * *note PyMem_Free(): 13b0.

   * *note PyMem_Malloc(): c0d.

   * *note PyMem_RawCalloc(): 324.

   * *note PyMem_RawFree(): 326.

   * *note PyMem_RawMalloc(): 323.

   * *note PyMem_RawRealloc(): 325.

   * *note PyMem_Realloc(): fd5.

   * *note PyMemberDef: 4f5.

   * ‘PyMemberDescr_Type’

   * *note PyMember_GetOne(): 533.

   * *note PyMember_SetOne(): 534.

   * *note PyMemoryView_FromBuffer(): 705.

   * *note PyMemoryView_FromMemory(): 1109.

   * *note PyMemoryView_FromObject(): 4804.

   * *note PyMemoryView_GetContiguous(): 4805.

   * ‘PyMemoryView_Type’

   * *note PyMethodDef: 1446.

   * ‘PyMethodDescr_Type’

   * *note PyModuleDef: 921.

   * ‘PyModuleDef_Base’

   * *note PyModuleDef_Init(): 4806.

   * ‘PyModuleDef_Type’

   * *note PyModule_Add(): 307.

   * *note PyModule_AddFunctions(): 4807.

   * *note PyModule_AddIntConstant(): 14aa.

   * *note PyModule_AddObject(): 309.

   * *note PyModule_AddObjectRef(): 308.

   * *note PyModule_AddStringConstant(): 14ab.

   * *note PyModule_AddType(): 919.

   * *note PyModule_Create2(): 4808.

   * *note PyModule_ExecDef(): e56.

   * *note PyModule_FromDefAndSpec2(): e55.

   * *note PyModule_GetDef(): 4809.

   * *note PyModule_GetDict(): 480a.

   * *note PyModule_GetFilename(): 3c0.

   * *note PyModule_GetFilenameObject(): 3c1.

   * *note PyModule_GetName(): 480b.

   * *note PyModule_GetNameObject(): 480c.

   * *note PyModule_GetState(): 924.

   * *note PyModule_New(): 480d.

   * *note PyModule_NewObject(): 480e.

   * *note PyModule_SetDocString(): 480f.

   * *note PyModule_Type: 4810.

   * *note PyNumber_Absolute(): 4811.

   * *note PyNumber_Add(): 4812.

   * *note PyNumber_And(): 4813.

   * *note PyNumber_AsSsize_t(): 4814.

   * *note PyNumber_Check(): a09.

   * *note PyNumber_Divmod(): 4815.

   * *note PyNumber_Float(): a0b.

   * *note PyNumber_FloorDivide(): 4816.

   * *note PyNumber_InPlaceAdd(): 4817.

   * *note PyNumber_InPlaceAnd(): 4818.

   * *note PyNumber_InPlaceFloorDivide(): 4819.

   * *note PyNumber_InPlaceLshift(): 481a.

   * *note PyNumber_InPlaceMatrixMultiply(): e58.

   * *note PyNumber_InPlaceMultiply(): 481b.

   * *note PyNumber_InPlaceOr(): 481c.

   * *note PyNumber_InPlacePower(): 481d.

   * *note PyNumber_InPlaceRemainder(): 481e.

   * *note PyNumber_InPlaceRshift(): 481f.

   * *note PyNumber_InPlaceSubtract(): 4820.

   * *note PyNumber_InPlaceTrueDivide(): 4821.

   * *note PyNumber_InPlaceXor(): 4822.

   * *note PyNumber_Index(): 837.

   * *note PyNumber_Invert(): 4823.

   * *note PyNumber_Long(): a0a.

   * *note PyNumber_Lshift(): 4824.

   * *note PyNumber_MatrixMultiply(): e57.

   * *note PyNumber_Multiply(): 4825.

   * *note PyNumber_Negative(): 4826.

   * *note PyNumber_Or(): 4827.

   * *note PyNumber_Positive(): 4828.

   * *note PyNumber_Power(): 4829.

   * *note PyNumber_Remainder(): 482a.

   * *note PyNumber_Rshift(): 482b.

   * *note PyNumber_Subtract(): 482c.

   * *note PyNumber_ToBase(): 16ef.

   * *note PyNumber_TrueDivide(): 482d.

   * *note PyNumber_Xor(): 482e.

   * *note PyOS_AfterFork(): 3c2.

   * *note PyOS_AfterFork_Child(): 3c3.

   * *note PyOS_AfterFork_Parent(): b67.

   * *note PyOS_BeforeFork(): b66.

   * *note PyOS_CheckStack(): 171b.

   * *note PyOS_FSPath(): cbf.

   * *note PyOS_InputHook: 52b.

   * ‘PyOS_InterruptOccurred()’

   * *note PyOS_double_to_string(): 482f.

   * *note PyOS_getsig(): 14ac.

   * ‘PyOS_mystricmp()’

   * ‘PyOS_mystrnicmp()’

   * *note PyOS_setsig(): 14ad.

   * *note PyOS_sighandler_t: 4830.

   * *note PyOS_snprintf(): 1479.

   * *note PyOS_string_to_double(): 122d.

   * *note PyOS_strtol(): 4831.

   * *note PyOS_strtoul(): 4832.

   * *note PyOS_vsnprintf(): 147a.

   * *note PyObject: 311.

   * *note PyObject.ob_refcnt: 843.

   * *note PyObject.ob_type: 4702.

   * *note PyObject_ASCII(): 4833.

   * *note PyObject_AsFileDescriptor(): 4834.

   * *note PyObject_Bytes(): 4835.

   * *note PyObject_Call(): 363.

   * *note PyObject_CallFunction(): 365.

   * *note PyObject_CallFunctionObjArgs(): 4836.

   * *note PyObject_CallMethod(): 366.

   * *note PyObject_CallMethodObjArgs(): 1902.

   * *note PyObject_CallNoArgs(): 362.

   * *note PyObject_CallObject(): 46e2.

   * *note PyObject_Calloc(): e50.

   * *note PyObject_CheckBuffer(): 368.

   * *note PyObject_ClearWeakRefs(): 51c.

   * *note PyObject_CopyData(): 701.

   * *note PyObject_DelAttr(): 161a.

   * *note PyObject_DelAttrString(): 14f5.

   * *note PyObject_DelItem(): 4837.

   * ‘PyObject_DelItemString()’

   * *note PyObject_Dir(): 4838.

   * *note PyObject_Format(): 4839.

   * *note PyObject_Free(): c0c.

   * *note PyObject_GC_Del(): 1473.

   * *note PyObject_GC_IsFinalized(): 91b.

   * *note PyObject_GC_IsTracked(): 91a.

   * *note PyObject_GC_Track(): 1474.

   * *note PyObject_GC_UnTrack(): 1475.

   * *note PyObject_GenericGetAttr(): 483a.

   * *note PyObject_GenericGetDict(): 183c.

   * *note PyObject_GenericSetAttr(): 483b.

   * *note PyObject_GenericSetDict(): 483c.

   * *note PyObject_GetAIter(): 483d.

   * *note PyObject_GetAttr(): 2f4.

   * *note PyObject_GetAttrString(): 2f5.

   * *note PyObject_GetBuffer(): 369.

   * *note PyObject_GetItem(): 2f9.

   * *note PyObject_GetIter(): 483e.

   * *note PyObject_GetOptionalAttr(): 2f2.

   * *note PyObject_GetOptionalAttrString(): 2f3.

   * *note PyObject_GetTypeData(): 4ef.

   * *note PyObject_HasAttr(): 2fd.

   * *note PyObject_HasAttrString(): 2ff.

   * *note PyObject_HasAttrStringWithError(): 2fe.

   * *note PyObject_HasAttrWithError(): 2fc.

   * *note PyObject_Hash(): 3cb.

   * *note PyObject_HashNotImplemented(): 1334.

   * *note PyObject_Init(): a0d.

   * *note PyObject_InitVar(): 1857.

   * *note PyObject_IsInstance(): e48.

   * *note PyObject_IsSubclass(): e49.

   * *note PyObject_IsTrue(): 483f.

   * *note PyObject_Length(): 4840.

   * *note PyObject_Malloc(): c0f.

   * *note PyObject_Not(): 4841.

   * *note PyObject_Realloc(): 13b1.

   * *note PyObject_Repr(): fd2.

   * *note PyObject_RichCompare(): 4726.

   * *note PyObject_RichCompareBool(): 18a7.

   * ‘PyObject_SelfIter()’

   * *note PyObject_SetAttr(): 4842.

   * *note PyObject_SetAttrString(): 14f4.

   * *note PyObject_SetItem(): 4764.

   * *note PyObject_Size(): 4843.

   * *note PyObject_Str(): fd3.

   * *note PyObject_Type(): 4844.

   * *note PyObject_Vectorcall(): 501.

   * *note PyObject_VectorcallMethod(): 502.

   * *note PyProperty_Type: 4845.

   * ‘PyRangeIter_Type’

   * ‘PyRange_Type’

   * ‘PyReversed_Type’

   * *note PySeqIter_New(): 4846.

   * *note PySeqIter_Type: 4847.

   * *note PySequence_Check(): 4848.

   * *note PySequence_Concat(): 4849.

   * *note PySequence_Contains(): 484a.

   * *note PySequence_Count(): 484b.

   * *note PySequence_DelItem(): 195b.

   * *note PySequence_DelSlice(): 484c.

   * *note PySequence_Fast(): 484d.

   * *note PySequence_GetItem(): 1959.

   * *note PySequence_GetSlice(): 484e.

   * ‘PySequence_In()’

   * *note PySequence_InPlaceConcat(): 484f.

   * *note PySequence_InPlaceRepeat(): 4850.

   * *note PySequence_Index(): 4851.

   * *note PySequence_Length(): 4852.

   * *note PySequence_List(): 4853.

   * *note PySequence_Repeat(): 4854.

   * *note PySequence_SetItem(): 195a.

   * *note PySequence_SetSlice(): 4855.

   * *note PySequence_Size(): 1958.

   * *note PySequence_Tuple(): 4856.

   * ‘PySetIter_Type’

   * *note PySet_Add(): 13b4.

   * *note PySet_Clear(): 4857.

   * *note PySet_Contains(): 13b6.

   * *note PySet_Discard(): 13b5.

   * *note PySet_New(): 13b2.

   * *note PySet_Pop(): 4858.

   * *note PySet_Size(): 13b7.

   * *note PySet_Type: 4859.

   * *note PySlice_AdjustIndices(): 3c6.

   * *note PySlice_GetIndices(): 485a.

   * *note PySlice_GetIndicesEx(): 3c4.

   * *note PySlice_New(): 485b.

   * *note PySlice_Type: 485c.

   * *note PySlice_Unpack(): 3c5.

   * *note PyState_AddModule(): 485d.

   * *note PyState_FindModule(): 485e.

   * *note PyState_RemoveModule(): 485f.

   * *note PyStructSequence_Desc: b61.

   * *note PyStructSequence_Field: b60.

   * *note PyStructSequence_GetItem(): 4860.

   * *note PyStructSequence_New(): 4861.

   * *note PyStructSequence_NewType(): 4862.

   * *note PyStructSequence_SetItem(): 4863.

   * *note PyStructSequence_UnnamedField: 926.

   * ‘PySuper_Type’

   * *note PySys_Audit(): 321.

   * *note PySys_AuditTuple(): 320.

   * *note PySys_FormatStderr(): 4864.

   * *note PySys_FormatStdout(): 4865.

   * *note PySys_GetObject(): 35d.

   * *note PySys_GetXOptions(): 4866.

   * *note PySys_ResetWarnOptions(): 37a.

   * *note PySys_SetArgv(): 1534.

   * *note PySys_SetArgvEx(): 1533.

   * *note PySys_SetObject(): 4867.

   * *note PySys_WriteStderr(): 4868.

   * *note PySys_WriteStdout(): 4869.

   * *note PyThreadState: 731.

   * *note PyThreadState_Clear(): 1515.

   * *note PyThreadState_Delete(): 18a4.

   * *note PyThreadState_Get(): 31f.

   * *note PyThreadState_GetDict(): 486a.

   * *note PyThreadState_GetFrame(): 732.

   * *note PyThreadState_GetID(): 916.

   * *note PyThreadState_GetInterpreter(): 915.

   * *note PyThreadState_New(): 486b.

   * *note PyThreadState_SetAsyncExc(): b6b.

   * *note PyThreadState_Swap(): 486c.

   * ‘PyThread_GetInfo()’

   * *note PyThread_ReInitTLS(): 3d6.

   * ‘PyThread_acquire_lock()’

   * ‘PyThread_acquire_lock_timed()’

   * ‘PyThread_allocate_lock()’

   * *note PyThread_create_key(): 3cc.

   * *note PyThread_delete_key(): 3ce.

   * *note PyThread_delete_key_value(): 3d4.

   * ‘PyThread_exit_thread()’

   * ‘PyThread_free_lock()’

   * *note PyThread_get_key_value(): 3d2.

   * ‘PyThread_get_stacksize()’

   * ‘PyThread_get_thread_ident()’

   * ‘PyThread_get_thread_native_id()’

   * ‘PyThread_init_thread()’

   * ‘PyThread_release_lock()’

   * *note PyThread_set_key_value(): 3d0.

   * ‘PyThread_set_stacksize()’

   * ‘PyThread_start_new_thread()’

   * *note PyThread_tss_alloc(): 3cd.

   * *note PyThread_tss_create(): 486d.

   * *note PyThread_tss_delete(): 3d5.

   * *note PyThread_tss_free(): 3cf.

   * *note PyThread_tss_get(): 3d3.

   * *note PyThread_tss_is_created(): 486e.

   * *note PyThread_tss_set(): 3d1.

   * ‘PyTraceBack_Here()’

   * ‘PyTraceBack_Print()’

   * ‘PyTraceBack_Type’

   * ‘PyTupleIter_Type’

   * *note PyTuple_GetItem(): 46ed.

   * *note PyTuple_GetSlice(): 486f.

   * *note PyTuple_New(): 364.

   * *note PyTuple_Pack(): 4870.

   * *note PyTuple_SetItem(): 46ee.

   * *note PyTuple_Size(): 4871.

   * *note PyTuple_Type: 4872.

   * *note PyTypeObject: a48.

   * *note PyType_ClearCache(): 4873.

   * *note PyType_FromMetaclass(): 4f6.

   * *note PyType_FromModuleAndSpec(): 4f7.

   * *note PyType_FromSpec(): 523.

   * *note PyType_FromSpecWithBases(): 524.

   * *note PyType_GenericAlloc(): a0e.

   * *note PyType_GenericNew(): 4701.

   * *note PyType_GetFlags(): 1856.

   * *note PyType_GetFullyQualifiedName(): 33d.

   * *note PyType_GetModule(): 912.

   * *note PyType_GetModuleByDef(): 342.

   * *note PyType_GetModuleName(): 33e.

   * *note PyType_GetModuleState(): 913.

   * *note PyType_GetName(): 6f6.

   * *note PyType_GetQualName(): 6f7.

   * *note PyType_GetSlot(): 840.

   * *note PyType_GetTypeDataSize(): 4f0.

   * *note PyType_IsSubtype(): 4874.

   * *note PyType_Modified(): 16f7.

   * *note PyType_Ready(): 722.

   * *note PyType_Slot: 4875.

   * *note PyType_Spec: 1618.

   * *note PyType_Type: 4f3.

   * *note PyUnicodeDecodeError_Create(): 4876.

   * *note PyUnicodeDecodeError_GetEncoding(): 4877.

   * *note PyUnicodeDecodeError_GetEnd(): 4878.

   * *note PyUnicodeDecodeError_GetObject(): 4879.

   * *note PyUnicodeDecodeError_GetReason(): 487a.

   * *note PyUnicodeDecodeError_GetStart(): 487b.

   * *note PyUnicodeDecodeError_SetEnd(): 487c.

   * *note PyUnicodeDecodeError_SetReason(): 487d.

   * *note PyUnicodeDecodeError_SetStart(): 487e.

   * *note PyUnicodeEncodeError_GetEncoding(): 487f.

   * *note PyUnicodeEncodeError_GetEnd(): 4880.

   * *note PyUnicodeEncodeError_GetObject(): 4881.

   * *note PyUnicodeEncodeError_GetReason(): 4882.

   * *note PyUnicodeEncodeError_GetStart(): 4883.

   * *note PyUnicodeEncodeError_SetEnd(): 4884.

   * *note PyUnicodeEncodeError_SetReason(): 4885.

   * *note PyUnicodeEncodeError_SetStart(): 4886.

   * ‘PyUnicodeIter_Type’

   * *note PyUnicodeTranslateError_GetEnd(): 4887.

   * *note PyUnicodeTranslateError_GetObject(): 4888.

   * *note PyUnicodeTranslateError_GetReason(): 4889.

   * *note PyUnicodeTranslateError_GetStart(): 488a.

   * *note PyUnicodeTranslateError_SetEnd(): 488b.

   * *note PyUnicodeTranslateError_SetReason(): 488c.

   * *note PyUnicodeTranslateError_SetStart(): 488d.

   * ‘PyUnicode_Append()’

   * ‘PyUnicode_AppendAndDel()’

   * *note PyUnicode_AsASCIIString(): 112c.

   * *note PyUnicode_AsCharmapString(): 488e.

   * ‘PyUnicode_AsDecodedObject()’

   * ‘PyUnicode_AsDecodedUnicode()’

   * ‘PyUnicode_AsEncodedObject()’

   * *note PyUnicode_AsEncodedString(): 488f.

   * ‘PyUnicode_AsEncodedUnicode()’

   * *note PyUnicode_AsLatin1String(): 112b.

   * *note PyUnicode_AsMBCSString(): 112d.

   * *note PyUnicode_AsRawUnicodeEscapeString(): 112a.

   * *note PyUnicode_AsUCS4(): 1112.

   * *note PyUnicode_AsUCS4Copy(): 860.

   * *note PyUnicode_AsUTF16String(): 4890.

   * *note PyUnicode_AsUTF32String(): 4891.

   * *note PyUnicode_AsUTF8AndSize(): 83d.

   * *note PyUnicode_AsUTF8String(): 1128.

   * *note PyUnicode_AsUnicodeEscapeString(): 1129.

   * *note PyUnicode_AsWideChar(): 195d.

   * *note PyUnicode_AsWideCharString(): 861.

   * ‘PyUnicode_BuildEncodingMap()’

   * *note PyUnicode_Compare(): 85c.

   * *note PyUnicode_CompareWithASCIIString(): 1200.

   * *note PyUnicode_Concat(): 1139.

   * *note PyUnicode_Contains(): 4892.

   * *note PyUnicode_Count(): 4893.

   * *note PyUnicode_Decode(): 18e7.

   * *note PyUnicode_DecodeASCII(): 4894.

   * *note PyUnicode_DecodeCharmap(): 4895.

   * ‘PyUnicode_DecodeCodePageStateful()’

   * *note PyUnicode_DecodeFSDefault(): 1617.

   * *note PyUnicode_DecodeFSDefaultAndSize(): 4896.

   * *note PyUnicode_DecodeLatin1(): 4897.

   * *note PyUnicode_DecodeLocale(): 4898.

   * *note PyUnicode_DecodeLocaleAndSize(): b70.

   * *note PyUnicode_DecodeMBCS(): 4899.

   * *note PyUnicode_DecodeMBCSStateful(): 489a.

   * *note PyUnicode_DecodeRawUnicodeEscape(): 489b.

   * *note PyUnicode_DecodeUTF16(): 489c.

   * *note PyUnicode_DecodeUTF16Stateful(): 489d.

   * *note PyUnicode_DecodeUTF32(): 489e.

   * *note PyUnicode_DecodeUTF32Stateful(): 489f.

   * *note PyUnicode_DecodeUTF7(): 48a0.

   * *note PyUnicode_DecodeUTF7Stateful(): 48a1.

   * *note PyUnicode_DecodeUTF8(): 48a2.

   * *note PyUnicode_DecodeUTF8Stateful(): 16a2.

   * *note PyUnicode_DecodeUnicodeEscape(): 48a3.

   * *note PyUnicode_EncodeCodePage(): 112e.

   * *note PyUnicode_EncodeFSDefault(): 1957.

   * *note PyUnicode_EncodeLocale(): b71.

   * *note PyUnicode_EqualToUTF8(): 31d.

   * *note PyUnicode_EqualToUTF8AndSize(): 31c.

   * *note PyUnicode_FSConverter(): cc0.

   * *note PyUnicode_FSDecoder(): 51d.

   * *note PyUnicode_Find(): 48a4.

   * *note PyUnicode_FindChar(): 85e.

   * *note PyUnicode_Format(): 48a5.

   * *note PyUnicode_FromEncodedObject(): 48a6.

   * *note PyUnicode_FromFormat(): 33f.

   * *note PyUnicode_FromFormatV(): 51a.

   * *note PyUnicode_FromObject(): 48a7.

   * ‘PyUnicode_FromOrdinal()’

   * *note PyUnicode_FromString(): 4748.

   * *note PyUnicode_FromStringAndSize(): 48a8.

   * *note PyUnicode_FromWideChar(): 1126.

   * ‘PyUnicode_GetDefaultEncoding()’

   * *note PyUnicode_GetLength(): 858.

   * *note PyUnicode_InternFromString(): 14f2.

   * *note PyUnicode_InternInPlace(): 856.

   * *note PyUnicode_IsIdentifier(): 18a1.

   * *note PyUnicode_Join(): 113a.

   * ‘PyUnicode_Partition()’

   * ‘PyUnicode_RPartition()’

   * ‘PyUnicode_RSplit()’

   * *note PyUnicode_ReadChar(): 110a.

   * *note PyUnicode_Replace(): 48a9.

   * ‘PyUnicode_Resize()’

   * *note PyUnicode_RichCompare(): 48aa.

   * *note PyUnicode_Split(): 48ab.

   * *note PyUnicode_Splitlines(): 48ac.

   * *note PyUnicode_Substring(): 85b.

   * *note PyUnicode_Tailmatch(): 85d.

   * *note PyUnicode_Translate(): 48ad.

   * *note PyUnicode_Type: 48ae.

   * *note PyUnicode_WriteChar(): 110b.

   * *note PyVarObject: 3f79.

   * ‘PyVarObject.ob_base’

   * *note PyVarObject.ob_size: 48af.

   * *note PyVectorcall_Call(): 4fc.

   * *note PyVectorcall_NARGS(): 4fb.

   * ‘PyWeakReference’

   * *note PyWeakref_GetObject(): 2f1.

   * *note PyWeakref_GetRef(): 2f0.

   * *note PyWeakref_NewProxy(): 48b0.

   * *note PyWeakref_NewRef(): 1753.

   * ‘PyWrapperDescr_Type’

   * *note PyWrapper_New(): 48b1.

   * ‘PyZip_Type’

   * *note Py_AddPendingCall(): 925.

   * *note Py_AtExit(): 48b2.

   * *note Py_BEGIN_ALLOW_THREADS: 46f3.

   * *note Py_BLOCK_THREADS: 48b3.

   * *note Py_BuildValue(): 84c.

   * *note Py_BytesMain(): 965.

   * *note Py_CompileString(): 829.

   * *note Py_DecRef(): 48b4.

   * *note Py_DecodeLocale(): b6e.

   * *note Py_END_ALLOW_THREADS: a31.

   * *note Py_EncodeLocale(): b6f.

   * *note Py_EndInterpreter(): 1762.

   * *note Py_EnterRecursiveCall(): 917.

   * *note Py_Exit(): cf5.

   * *note Py_FatalError(): 927.

   * ‘Py_FileSystemDefaultEncodeErrors’

   * ‘Py_FileSystemDefaultEncoding’

   * *note Py_Finalize(): 12e6.

   * *note Py_FinalizeEx(): cbc.

   * *note Py_GenericAlias(): 48b5.

   * *note Py_GenericAliasType: 48b6.

   * *note Py_GetBuildInfo(): 139f.

   * *note Py_GetCompiler(): 48b7.

   * *note Py_GetConstant(): 340.

   * *note Py_GetConstantBorrowed(): 341.

   * *note Py_GetCopyright(): 48b8.

   * *note Py_GetExecPrefix(): 37c.

   * *note Py_GetPath(): 37e.

   * *note Py_GetPlatform(): 48b9.

   * *note Py_GetPrefix(): 380.

   * *note Py_GetProgramFullPath(): 382.

   * *note Py_GetProgramName(): 384.

   * *note Py_GetPythonHome(): 385.

   * ‘Py_GetRecursionLimit()’

   * *note Py_GetVersion(): 48ba.

   * ‘Py_HasFileSystemDefaultEncoding’

   * *note Py_IncRef(): 48bb.

   * *note Py_Initialize(): 851.

   * *note Py_InitializeEx(): 48bc.

   * *note Py_Is(): 844.

   * *note Py_IsFalse(): 847.

   * *note Py_IsFinalizing(): 314.

   * *note Py_IsInitialized(): 476d.

   * *note Py_IsNone(): 845.

   * *note Py_IsTrue(): 846.

   * *note Py_LeaveRecursiveCall(): 918.

   * *note Py_Main(): bcc.

   * ‘Py_MakePendingCalls()’

   * *note Py_NewInterpreter(): 16b9.

   * *note Py_NewRef(): 83e.

   * *note Py_ReprEnter(): 48bd.

   * *note Py_ReprLeave(): 48be.

   * *note Py_SetProgramName(): 1532.

   * *note Py_SetPythonHome(): 1531.

   * ‘Py_SetRecursionLimit()’

   * *note Py_UCS4: 110e.

   * *note Py_UNBLOCK_THREADS: 48bf.

   * ‘Py_UTF8Mode’

   * *note Py_VaBuildValue(): 48c0.

   * *note Py_Version: 6fa.

   * *note Py_XNewRef(): 83f.

   * *note Py_buffer: 6fc.

   * ‘Py_intptr_t’

   * *note Py_ssize_t: a03.

   * ‘Py_uintptr_t’

   * *note allocfunc: 48c1.

   * *note binaryfunc: 48c2.

   * *note descrgetfunc: 48c3.

   * *note descrsetfunc: 48c4.

   * *note destructor: 48c5.

   * *note getattrfunc: 48c6.

   * *note getattrofunc: 48c7.

   * *note getbufferproc: 48c8.

   * *note getiterfunc: 48c9.

   * *note getter: 48ca.

   * *note hashfunc: 48cb.

   * *note initproc: 48cc.

   * *note inquiry: 48cd.

   * *note iternextfunc: 48ce.

   * *note lenfunc: 48cf.

   * *note newfunc: 48d0.

   * *note objobjargproc: 48d1.

   * *note objobjproc: 48d2.

   * *note releasebufferproc: 48d3.

   * *note reprfunc: 48d4.

   * *note richcmpfunc: 48d5.

   * *note setattrfunc: 48d6.

   * *note setattrofunc: 48d7.

   * *note setter: 48d8.

   * *note ssizeargfunc: 48d9.

   * *note ssizeobjargproc: 48da.

   * ‘ssizessizeargfunc’

   * ‘ssizessizeobjargproc’

   * ‘symtable’

   * *note ternaryfunc: 48db.

   * *note traverseproc: 48dc.

   * *note unaryfunc: 48dd.

   * *note vectorcallfunc: 4fd.

   * *note visitproc: 48de.


File: python.info,  Node: The Very High Level Layer,  Next: 參照計數<2>,  Prev: C API 穩定性,  Up: Python/C API 參考手冊

7.3 The Very High Level Layer
=============================

The functions in this chapter will let you execute Python source code
given in a file or a buffer, but they will not let you interact in a
more detailed way with the interpreter.

Several of these functions accept a start symbol from the grammar as a
parameter.  The available start symbols are *note Py_eval_input: 48e2,
*note Py_file_input: 48e3, and *note Py_single_input: 48e4.  These are
described following the functions which accept them as parameters.

Note also that several of these functions take FILE* parameters.  One
particular issue which needs to be handled carefully is that the ‘FILE’
structure for different C libraries can be different and incompatible.
Under Windows (at least), it is possible for dynamically linked
extensions to actually use different libraries, so care should be taken
that FILE* parameters are only passed to these functions if it is
certain that they were created by the same library that the Python
runtime is using.

 -- C 函式: int Py_Main (int argc, wchar_t **argv)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  The main program for the
     standard interpreter.  This is made available for programs which
     embed Python.  The 'argc' and 'argv' parameters should be prepared
     exactly as those which are passed to a C program's ‘main()’
     function (converted to wchar_t according to the user's locale).  It
     is important to note that the argument list may be modified (but
     the contents of the strings pointed to by the argument list are
     not).  The return value will be ‘0’ if the interpreter exits
     normally (i.e., without an exception), ‘1’ if the interpreter exits
     due to an exception, or ‘2’ if the parameter list does not
     represent a valid Python command line.

     Note that if an otherwise unhandled *note SystemExit: ce7. is
     raised, this function will not return ‘1’, but exit the process, as
     long as *note PyConfig.inspect: 39a. is zero.

 -- C 函式: int Py_BytesMain (int argc, char **argv)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.8 版本開始.'  Similar to
     *note Py_Main(): bcc. but 'argv' is an array of bytes strings.

     在 3.8 版被加入.

 -- C 函式: int PyRun_AnyFile (FILE *fp, const char *filename)

     This is a simplified interface to *note PyRun_AnyFileExFlags():
     48e6. below, leaving 'closeit' set to ‘0’ and 'flags' set to
     ‘NULL’.

 -- C 函式: int PyRun_AnyFileFlags (FILE *fp, const char *filename,
          PyCompilerFlags *flags)

     This is a simplified interface to *note PyRun_AnyFileExFlags():
     48e6. below, leaving the 'closeit' argument set to ‘0’.

 -- C 函式: int PyRun_AnyFileEx (FILE *fp, const char *filename, int
          closeit)

     This is a simplified interface to *note PyRun_AnyFileExFlags():
     48e6. below, leaving the 'flags' argument set to ‘NULL’.

 -- C 函式: int PyRun_AnyFileExFlags (FILE *fp, const char *filename,
          int closeit, PyCompilerFlags *flags)

     If 'fp' refers to a file associated with an interactive device
     (console or terminal input or Unix pseudo-terminal), return the
     value of *note PyRun_InteractiveLoop(): 48e9, otherwise return the
     result of *note PyRun_SimpleFile(): 4740.  'filename' is decoded
     from the filesystem encoding (*note sys.getfilesystemencoding():
     c00.).  If 'filename' is ‘NULL’, this function uses ‘"???"’ as the
     filename.  If 'closeit' is true, the file is closed before
     ‘PyRun_SimpleFileExFlags()’ returns.

 -- C 函式: int PyRun_SimpleString (const char *command)

     This is a simplified interface to *note PyRun_SimpleStringFlags():
     48ea. below, leaving the *note PyCompilerFlags: a44.* argument set
     to ‘NULL’.

 -- C 函式: int PyRun_SimpleStringFlags (const char *command,
          PyCompilerFlags *flags)

     Executes the Python source code from 'command' in the *note
     __main__: 1. module according to the 'flags' argument.  If *note
     __main__: 1. does not already exist, it is created.  Returns ‘0’ on
     success or ‘-1’ if an exception was raised.  If there was an error,
     there is no way to get the exception information.  For the meaning
     of 'flags', see below.

     Note that if an otherwise unhandled *note SystemExit: ce7. is
     raised, this function will not return ‘-1’, but exit the process,
     as long as *note PyConfig.inspect: 39a. is zero.

 -- C 函式: int PyRun_SimpleFile (FILE *fp, const char *filename)

     This is a simplified interface to *note PyRun_SimpleFileExFlags():
     180b. below, leaving 'closeit' set to ‘0’ and 'flags' set to
     ‘NULL’.

 -- C 函式: int PyRun_SimpleFileEx (FILE *fp, const char *filename, int
          closeit)

     This is a simplified interface to *note PyRun_SimpleFileExFlags():
     180b. below, leaving 'flags' set to ‘NULL’.

 -- C 函式: int PyRun_SimpleFileExFlags (FILE *fp, const char *filename,
          int closeit, PyCompilerFlags *flags)

     Similar to *note PyRun_SimpleStringFlags(): 48ea, but the Python
     source code is read from 'fp' instead of an in-memory string.
     'filename' should be the name of the file, it is decoded from *note
     filesystem encoding and error handler: 4e0.  If 'closeit' is true,
     the file is closed before ‘PyRun_SimpleFileExFlags()’ returns.

          備註: On Windows, 'fp' should be opened as binary mode (e.g.
          ‘fopen(filename, "rb")’).  Otherwise, Python may not handle
          script file with LF line ending correctly.

 -- C 函式: int PyRun_InteractiveOne (FILE *fp, const char *filename)

     This is a simplified interface to *note
     PyRun_InteractiveOneFlags(): 48ed. below, leaving 'flags' set to
     ‘NULL’.

 -- C 函式: int PyRun_InteractiveOneFlags (FILE *fp, const char
          *filename, PyCompilerFlags *flags)

     Read and execute a single statement from a file associated with an
     interactive device according to the 'flags' argument.  The user
     will be prompted using ‘sys.ps1’ and ‘sys.ps2’.  'filename' is
     decoded from the *note filesystem encoding and error handler: 4e0.

     Returns ‘0’ when the input was executed successfully, ‘-1’ if there
     was an exception, or an error code from the ‘errcode.h’ include
     file distributed as part of Python if there was a parse error.
     (Note that ‘errcode.h’ is not included by ‘Python.h’, so must be
     included specifically if needed.)

 -- C 函式: int PyRun_InteractiveLoop (FILE *fp, const char *filename)

     This is a simplified interface to *note
     PyRun_InteractiveLoopFlags(): 48ee. below, leaving 'flags' set to
     ‘NULL’.

 -- C 函式: int PyRun_InteractiveLoopFlags (FILE *fp, const char
          *filename, PyCompilerFlags *flags)

     Read and execute statements from a file associated with an
     interactive device until EOF is reached.  The user will be prompted
     using ‘sys.ps1’ and ‘sys.ps2’.  'filename' is decoded from the
     *note filesystem encoding and error handler: 4e0.  Returns ‘0’ at
     EOF or a negative number upon failure.

 -- C 變數: int (*PyOS_InputHook)(void)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Can be set to point to a
     function with the prototype ‘int func(void)’.  The function will be
     called when Python's interpreter prompt is about to become idle and
     wait for user input from the terminal.  The return value is
     ignored.  Overriding this hook can be used to integrate the
     interpreter's prompt with other event loops, as done in the
     ‘Modules/_tkinter.c’ in the Python source code.

     在 3.12 版的變更: This function is only called from the *note main
     interpreter: 52d.

 -- C 變數: char *(*PyOS_ReadlineFunctionPointer)(FILE*, FILE*, const
          char*)

     Can be set to point to a function with the prototype ‘char
     *func(FILE *stdin, FILE *stdout, char *prompt)’, overriding the
     default function used to read a single line of input at the
     interpreter's prompt.  The function is expected to output the
     string 'prompt' if it's not ‘NULL’, and then read a line of input
     from the provided standard input file, returning the resulting
     string.  For example, The *note readline: a8. module sets this hook
     to provide line-editing and tab-completion features.

     The result must be a string allocated by *note PyMem_RawMalloc():
     323. or *note PyMem_RawRealloc(): 325, or ‘NULL’ if an error
     occurred.

     在 3.4 版的變更: The result must be allocated by *note
     PyMem_RawMalloc(): 323. or *note PyMem_RawRealloc(): 325, instead
     of being allocated by *note PyMem_Malloc(): c0d. or *note
     PyMem_Realloc(): fd5.

     在 3.12 版的變更: This function is only called from the *note main
     interpreter: 52d.

 -- C 函式: *note PyObject: 311. *PyRun_String (const char *str, int
          start, PyObject *globals, PyObject *locals)
     '回傳值：新的參照。' This is a simplified interface to *note
     PyRun_StringFlags(): 48ef. below, leaving 'flags' set to ‘NULL’.

 -- C 函式: *note PyObject: 311. *PyRun_StringFlags (const char *str,
          int start, PyObject *globals, PyObject *locals,
          PyCompilerFlags *flags)
     '回傳值：新的參照。' Execute Python source code from 'str' in the
     context specified by the objects 'globals' and 'locals' with the
     compiler flags specified by 'flags'.  'globals' must be a
     dictionary; 'locals' can be any object that implements the mapping
     protocol.  The parameter 'start' specifies the start token that
     should be used to parse the source code.

     Returns the result of executing the code as a Python object, or
     ‘NULL’ if an exception was raised.

 -- C 函式: *note PyObject: 311. *PyRun_File (FILE *fp, const char
          *filename, int start, PyObject *globals, PyObject *locals)
     '回傳值：新的參照。' This is a simplified interface to *note
     PyRun_FileExFlags(): 48f1. below, leaving 'closeit' set to ‘0’ and
     'flags' set to ‘NULL’.

 -- C 函式: *note PyObject: 311. *PyRun_FileEx (FILE *fp, const char
          *filename, int start, PyObject *globals, PyObject *locals, int
          closeit)
     '回傳值：新的參照。' This is a simplified interface to *note
     PyRun_FileExFlags(): 48f1. below, leaving 'flags' set to ‘NULL’.

 -- C 函式: *note PyObject: 311. *PyRun_FileFlags (FILE *fp, const char
          *filename, int start, PyObject *globals, PyObject *locals,
          PyCompilerFlags *flags)
     '回傳值：新的參照。' This is a simplified interface to *note
     PyRun_FileExFlags(): 48f1. below, leaving 'closeit' set to ‘0’.

 -- C 函式: *note PyObject: 311. *PyRun_FileExFlags (FILE *fp, const
          char *filename, int start, PyObject *globals, PyObject
          *locals, int closeit, PyCompilerFlags *flags)
     '回傳值：新的參照。' Similar to *note PyRun_StringFlags(): 48ef,
     but the Python source code is read from 'fp' instead of an
     in-memory string.  'filename' should be the name of the file, it is
     decoded from the *note filesystem encoding and error handler: 4e0.
     If 'closeit' is true, the file is closed before *note
     PyRun_FileExFlags(): 48f1. returns.

 -- C 函式: *note PyObject: 311. *Py_CompileString (const char *str,
          const char *filename, int start)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  This is a
     simplified interface to *note Py_CompileStringFlags(): 48f4. below,
     leaving 'flags' set to ‘NULL’.

 -- C 函式: *note PyObject: 311. *Py_CompileStringFlags (const char
          *str, const char *filename, int start, PyCompilerFlags *flags)
     '回傳值：新的參照。' This is a simplified interface to *note
     Py_CompileStringExFlags(): 48f5. below, with 'optimize' set to
     ‘-1’.

 -- C 函式: *note PyObject: 311. *Py_CompileStringObject (const char
          *str, PyObject *filename, int start, PyCompilerFlags *flags,
          int optimize)
     '回傳值：新的參照。' Parse and compile the Python source code in
     'str', returning the resulting code object.  The start token is
     given by 'start'; this can be used to constrain the code which can
     be compiled and should be *note Py_eval_input: 48e2, *note
     Py_file_input: 48e3, or *note Py_single_input: 48e4.  The filename
     specified by 'filename' is used to construct the code object and
     may appear in tracebacks or *note SyntaxError: 173. exception
     messages.  This returns ‘NULL’ if the code cannot be parsed or
     compiled.

     The integer 'optimize' specifies the optimization level of the
     compiler; a value of ‘-1’ selects the optimization level of the
     interpreter as given by *note -O: d5b. options.  Explicit levels
     are ‘0’ (no optimization; ‘__debug__’ is true), ‘1’ (asserts are
     removed, ‘__debug__’ is false) or ‘2’ (docstrings are removed too).

     在 3.4 版被加入.

 -- C 函式: *note PyObject: 311. *Py_CompileStringExFlags (const char
          *str, const char *filename, int start, PyCompilerFlags *flags,
          int optimize)
     '回傳值：新的參照。' Like *note Py_CompileStringObject(): 48f6, but
     'filename' is a byte string decoded from the *note filesystem
     encoding and error handler: 4e0.

     在 3.2 版被加入.

 -- C 函式: *note PyObject: 311. *PyEval_EvalCode (PyObject *co,
          PyObject *globals, PyObject *locals)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  This is a
     simplified interface to *note PyEval_EvalCodeEx(): 166b, with just
     the code object, and global and local variables.  The other
     arguments are set to ‘NULL’.

 -- C 函式: *note PyObject: 311. *PyEval_EvalCodeEx (PyObject *co,
          PyObject *globals, PyObject *locals, PyObject *const *args,
          int argcount, PyObject *const *kws, int kwcount, PyObject
          *const *defs, int defcount, PyObject *kwdefs, PyObject
          *closure)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Evaluate a
     precompiled code object, given a particular environment for its
     evaluation.  This environment consists of a dictionary of global
     variables, a mapping object of local variables, arrays of
     arguments, keywords and defaults, a dictionary of default values
     for *note keyword-only: 285. arguments and a closure tuple of
     cells.

 -- C 函式: *note PyObject: 311. *PyEval_EvalFrame (PyFrameObject *f)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Evaluate
     an execution frame.  This is a simplified interface to *note
     PyEval_EvalFrameEx(): fd1, for backward compatibility.

 -- C 函式: *note PyObject: 311. *PyEval_EvalFrameEx (PyFrameObject *f,
          int throwflag)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  This is
     the main, unvarnished function of Python interpretation.  The code
     object associated with the execution frame 'f' is executed,
     interpreting bytecode and executing calls as needed.  The
     additional 'throwflag' parameter can mostly be ignored - if true,
     then it causes an exception to immediately be thrown; this is used
     for the *note throw(): 4a0. methods of generator objects.

     在 3.4 版的變更: This function now includes a debug assertion to
     help ensure that it does not silently discard an active exception.

 -- C 函式: int PyEval_MergeCompilerFlags (PyCompilerFlags *cf)

     This function changes the flags of the current evaluation frame,
     and returns true on success, false on failure.

 -- C 變數: int Py_eval_input

     The start symbol from the Python grammar for isolated expressions;
     for use with *note Py_CompileString(): 829.

 -- C 變數: int Py_file_input

     The start symbol from the Python grammar for sequences of
     statements as read from a file or other source; for use with *note
     Py_CompileString(): 829.  This is the symbol to use when compiling
     arbitrarily long Python source code.

 -- C 變數: int Py_single_input

     The start symbol from the Python grammar for a single statement;
     for use with *note Py_CompileString(): 829.  This is the symbol
     used for the interactive interpreter loop.

 -- C 結構: struct PyCompilerFlags

     This is the structure used to hold compiler flags.  In cases where
     code is only being compiled, it is passed as ‘int flags’, and in
     cases where code is being executed, it is passed as
     ‘PyCompilerFlags *flags’.  In this case, ‘from __future__ import’
     can modify 'flags'.

     Whenever ‘PyCompilerFlags *flags’ is ‘NULL’, *note cf_flags: 48f8.
     is treated as equal to ‘0’, and any modification due to ‘from
     __future__ import’ is discarded.

      -- C 成員函數: int cf_flags

          Compiler flags.

      -- C 成員函數: int cf_feature_version

          'cf_feature_version' is the minor Python version.  It should
          be initialized to ‘PY_MINOR_VERSION’.

          The field is ignored by default, it is used if and only if
          ‘PyCF_ONLY_AST’ flag is set in *note cf_flags: 48f8.

     在 3.8 版的變更: 新增 'cf_feature_version' 欄位。

 -- C 變數: int CO_FUTURE_DIVISION

     This bit can be set in 'flags' to cause division operator ‘/’ to be
     interpreted as "true division" according to PEP 238(1).

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0238/


File: python.info,  Node: 參照計數<2>,  Next: 例外處理,  Prev: The Very High Level Layer,  Up: Python/C API 參考手冊

7.4 參照計數
============

本節中的函式與巨集用於管理 Python 物件的參照計數。

 -- C 函式: *note Py_ssize_t: a03. Py_REFCNT (PyObject *o)

     取得物件 'o' 的參照計數。

     Note that the returned value may not actually reflect how many
     references to the object are actually held.  For example, some
     objects are *note immortal: 4190. and have a very high refcount
     that does not reflect the actual number of references.
     Consequently, do not rely on the returned value to be accurate,
     other than a value of 0 or 1.

     使用 *note Py_SET_REFCNT(): 84f. 函式設定物件參照計數。

     在 3.10 版的變更: *note Py_REFCNT(): 84e. 更改為行內靜態函式
     (inline static function)。

     在 3.11 版的變更: 參數型別不再是 const *note PyObject: 311.*。

 -- C 函式: void Py_SET_REFCNT (PyObject *o, Py_ssize_t refcnt)

     設定物件 'o' 的參照計數。

     On *note Python build with Free Threading: 1c7a, if 'refcnt' is
     larger than ‘UINT32_MAX’, the object is made *note immortal: 4190.

     This function has no effect on *note immortal: 4190. objects.

     在 3.9 版被加入.

     在 3.12 版的變更: 不滅的物件不會被修改。

 -- C 函式: void Py_INCREF (PyObject *o)

     代表取得對於物件 'o' 的新*note 強參照: 2ee.，即它正在使用且不應被銷
     毀。

     This function has no effect on *note immortal: 4190. objects.

     此函式通常用於將*note 借用參照: 2ef.原地 (in-place) 轉換為*note
     強參照: 2ee.。*note Py_NewRef(): 83e. 函式可用於建立新的*note
     強參照: 2ee.。

     When done using the object, release is by calling *note
     Py_DECREF(): 515.

     該物件不能為 ‘NULL’；如果你不確定它不是 ‘NULL’，請使用 *note
     Py_XINCREF(): a08.。

     不要期望此函式會以任何方式實際修改 'o'，至少對於某些物件(1)來說，此
     函式沒有任何效果。

     在 3.12 版的變更: 不滅的物件不會被修改。

 -- C 函式: void Py_XINCREF (PyObject *o)

     與 *note Py_INCREF(): 514. 類似，但物件 'o' 可以為 ‘NULL’，在這種情
     況下這就不會有任何效果。

     另請見 *note Py_XNewRef(): 83f.。

 -- C 函式: *note PyObject: 311. *Py_NewRef (PyObject *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本開始.'  建立對物件的
     新*note 強參照: 2ee.：於 'o' 呼叫 *note Py_INCREF(): 514. 並回傳物
     件 'o'。

     當不再需要*note 強參照: 2ee.時，應對其呼叫 *note Py_DECREF(): 515.
     以釋放該參照。

     物件 'o' 不能為 ‘NULL’；如果 'o' 可以為 ‘NULL’，則使用 *note
     Py_XNewRef(): 83f.。

     舉例來說：

          Py_INCREF(obj);
          self->attr = obj;

     可以寫成：

          self->attr = Py_NewRef(obj);

     另請參閱 *note Py_INCREF(): 514.。

     在 3.10 版被加入.

 -- C 函式: *note PyObject: 311. *Py_XNewRef (PyObject *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本開始.'  與 *note
     Py_NewRef(): 83e. 類似，但物件 'o' 可以為 NULL。

     如果物件 'o' 為 ‘NULL’，則該函式僅回傳 ‘NULL’。

     在 3.10 版被加入.

 -- C 函式: void Py_DECREF (PyObject *o)

     釋放一個對物件 'o' 的*note 強參照: 2ee.，代表該參照不會再被使用。

     This function has no effect on *note immortal: 4190. objects.

     如果最後一個*note 強參照: 2ee.被釋放（即物件的參照計數達到零），則
     觸發物件之型別的釋放函式 (deallocation function)（不得為 ‘NULL’）。

     此函式通常用於在退出作用域之前刪除*note 強參照: 2ee.。

     該物件不能為 ‘NULL’；如果你不確定它不是 ‘NULL’，請改用 *note
     Py_XDECREF(): 733.。

     不要期望此函式會以任何方式實際修改 'o'，至少對於某些物件(2)來說，此
     函式沒有任何效果。

          警告: 釋放函式可以導致任意 Python 程式碼被調用（例如，當釋放具
          有 *note __del__(): 1e36. 方法的類別實例時）。雖然此類程式碼中
          的例外不會被傳遞出來，但​​執行的程式碼可以自由存取所有 Python 全
          域變數。這意味著在調用 *note Py_DECREF(): 515. 之前，可從全域
          變數存取的任何物件都應處於一致狀態。例如，從 list 中刪除物件的
          程式碼應將已刪除物件的參照複製到臨時變數中，更新 list 資料結構
          ，然後為臨時變數呼叫 *note Py_DECREF(): 515.。

     在 3.12 版的變更: 不滅的物件不會被修改。

 -- C 函式: void Py_XDECREF (PyObject *o)

     和 *note Py_DECREF(): 515. 類似，但該物件可以是 ‘NULL’，在這種情況
     下巨集不起作用。在這裡也會出現與 *note Py_DECREF(): 515. 相同的警告
     。

 -- C 函式: void Py_CLEAR (PyObject *o)

     釋放對於物件 'o' 的*note 強參照: 2ee.。該物件可能是 ‘NULL’，在這種
     情況下巨集不起作用；否則，效果與 *note Py_DECREF(): 515. 相同，除非
     引數也設定為 ‘NULL’。*note Py_DECREF(): 515. 的警告不適用於傳遞的物
     件，因為巨集在釋放其參照之前小心地使用臨時變數並將引數設定為
     ‘NULL’。

     每當要釋放垃圾回收 (garbage collection) 期間可能被遍歷到之對於物件
     的參照時，使用此巨集是個好主意。

     在 3.12 版的變更: 巨集引數現在僅會被求值 (evaluate) 一次。如果引數
     有其他副作用，則不再重複作用。

 -- C 函式: void Py_IncRef (PyObject *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  代表取得對於物件 'o' 的*note
     強參照: 2ee.。*note Py_XINCREF(): a08. 的函式版本。它可用於 Python
     的 runtime 動態嵌入。

 -- C 函式: void Py_DecRef (PyObject *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  釋放對物件 'o' 的*note 強參照:
     2ee.。*note Py_XDECREF(): 733. 的函式版本。它可用於 Python 的
     runtime 動態嵌入。

 -- C 巨集: Py_SETREF (dst, src)

     巨集安全地釋放對於物件 'dst' 的*note 強參照: 2ee.並將 'dst' 設定為
     'src'。

     與 *note Py_CLEAR(): 51e. 的情況一樣，「明顯的」程式碼可能是致命的
     ：

          Py_DECREF(dst);
          dst = src;

     安全的方法是：

          Py_SETREF(dst, src);

     這會在釋放對 'dst' 舊值的參照_之前_將 'dst' 設定為 'src'，使得因
     'dst' 被拆除而觸發的任何副作用 (side-effect) 之程式碼不會相信 'dst'
     是指向一個有效物件。

     在 3.6 版被加入.

     在 3.12 版的變更: 巨集引數現在僅會被求值一次。如果引數有其他副作用
     ，則不再重複作用。

 -- C 巨集: Py_XSETREF (dst, src)

     *note Py_SETREF: 51f. 巨集的變體，請改用 *note Py_XDECREF(): 733. 而
     非 *note Py_DECREF(): 515.。

     在 3.6 版被加入.

     在 3.12 版的變更: 巨集引數現在僅會被求值一次。如果引數有其他副作用
     ，則不再重複作用。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0683/

   (2) https://peps.python.org/pep-0683/


File: python.info,  Node: 例外處理,  Next: 工具,  Prev: 參照計數<2>,  Up: Python/C API 參考手冊

7.5 例外處理
============

The functions described in this chapter will let you handle and raise
Python exceptions.  It is important to understand some of the basics of
Python exception handling.  It works somewhat like the POSIX ‘errno’
variable: there is a global indicator (per thread) of the last error
that occurred.  Most C API functions don't clear this on success, but
will set it to indicate the cause of the error on failure.  Most C API
functions also return an error indicator, usually ‘NULL’ if they are
supposed to return a pointer, or ‘-1’ if they return an integer
(exception: the ‘PyArg_*’ functions return ‘1’ for success and ‘0’ for
failure).

Concretely, the error indicator consists of three object pointers: the
exception's type, the exception's value, and the traceback object.  Any
of those pointers can be ‘NULL’ if non-set (although some combinations
are forbidden, for example you can't have a non-‘NULL’ traceback if the
exception type is ‘NULL’).

When a function must fail because some function it called failed, it
generally doesn't set the error indicator; the function it called
already set it.  It is responsible for either handling the error and
clearing the exception or returning after cleaning up any resources it
holds (such as object references or memory allocations); it should 'not'
continue normally if it is not prepared to handle the error.  If
returning due to an error, it is important to indicate to the caller
that an error has been set.  If the error is not handled or carefully
propagated, additional calls into the Python/C API may not behave as
intended and may fail in mysterious ways.

     備註: The error indicator is 'not' the result of *note
     sys.exc_info(): 630.  The former corresponds to an exception that
     is not yet caught (and is therefore still propagating), while the
     latter returns an exception after it is caught (and has therefore
     stopped propagating).

* Menu:

* Printing and clearing::
* Raising exceptions::
* Issuing warnings::
* Querying the error indicator::
* Signal Handling: Signal Handling<2>.
* 例外類別: 例外類別<2>.
* 例外物件::
* Unicode Exception Objects::
* Recursion Control::
* Standard Exceptions::
* Standard Warning Categories::


File: python.info,  Node: Printing and clearing,  Next: Raising exceptions,  Up: 例外處理

7.5.1 Printing and clearing
---------------------------

 -- C 函式: void PyErr_Clear ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Clear the error indicator.  If
     the error indicator is not set, there is no effect.

 -- C 函式: void PyErr_PrintEx (int set_sys_last_vars)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Print a standard traceback to
     ‘sys.stderr’ and clear the error indicator.  'Unless' the error is
     a ‘SystemExit’, in that case no traceback is printed and the Python
     process will exit with the error code specified by the ‘SystemExit’
     instance.

     Call this function 'only' when the error indicator is set.
     Otherwise it will cause a fatal error!

     If 'set_sys_last_vars' is nonzero, the variable *note sys.last_exc:
     465. is set to the printed exception.  For backwards compatibility,
     the deprecated variables *note sys.last_type: 466, *note
     sys.last_value: 467. and *note sys.last_traceback: 468. are also
     set to the type, value and traceback of this exception,
     respectively.

     在 3.12 版的變更: The setting of *note sys.last_exc: 465. was
     added.

 -- C 函式: void PyErr_Print ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  ‘PyErr_PrintEx(1)’ 的別名。

 -- C 函式: void PyErr_WriteUnraisable (PyObject *obj)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Call *note
     sys.unraisablehook(): 1dc. using the current exception and 'obj'
     argument.

     This utility function prints a warning message to ‘sys.stderr’ when
     an exception has been set but it is impossible for the interpreter
     to actually raise the exception.  It is used, for example, when an
     exception occurs in an *note __del__(): 1e36. method.

     The function is called with a single argument 'obj' that identifies
     the context in which the unraisable exception occurred.  If
     possible, the repr of 'obj' will be printed in the warning message.
     If 'obj' is ‘NULL’, only the traceback is printed.

     An exception must be set when calling this function.

     在 3.4 版的變更: Print a traceback.  Print only traceback if 'obj'
     is ‘NULL’.

     在 3.8 版的變更: 使用 *note sys.unraisablehook(): 1dc.。

 -- C 函式: void PyErr_FormatUnraisable (const char *format, ...)

     Similar to *note PyErr_WriteUnraisable(): 328, but the 'format' and
     subsequent parameters help format the warning message; they have
     the same meaning and values as in *note PyUnicode_FromFormat():
     33f.  ‘PyErr_WriteUnraisable(obj)’ is roughly equivalent to
     ‘PyErr_FormatUnraisable("Exception ignored in: %R", obj)’.  If
     'format' is ‘NULL’, only the traceback is printed.

     在 3.13 版被加入.

 -- C 函式: void PyErr_DisplayException (PyObject *exc)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.12 版本開始.'  Print the
     standard traceback display of ‘exc’ to ‘sys.stderr’, including
     chained exceptions and notes.

     在 3.12 版被加入.


File: python.info,  Node: Raising exceptions,  Next: Issuing warnings,  Prev: Printing and clearing,  Up: 例外處理

7.5.2 Raising exceptions
------------------------

These functions help you set the current thread's error indicator.  For
convenience, some of these functions will always return a ‘NULL’ pointer
for use in a ‘return’ statement.

 -- C 函式: void PyErr_SetString (PyObject *type, const char *message)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This is the most common way to
     set the error indicator.  The first argument specifies the
     exception type; it is normally one of the standard exceptions, e.g.
     ‘PyExc_RuntimeError’.  You need not create a new *note strong
     reference: 2ee. to it (e.g.  with *note Py_INCREF(): 514.).  The
     second argument is an error message; it is decoded from ‘'utf-8'’.

 -- C 函式: void PyErr_SetObject (PyObject *type, PyObject *value)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This function is similar to
     *note PyErr_SetString(): 522. but lets you specify an arbitrary
     Python object for the "value" of the exception.

 -- C 函式: *note PyObject: 311. *PyErr_Format (PyObject *exception,
          const char *format, ...)
     '回傳值：總是為 NULL。'' 為 *note 穩定 ABI 的一部分: 4f9.'  This
     function sets the error indicator and returns ‘NULL’.  'exception'
     should be a Python exception class.  The 'format' and subsequent
     parameters help format the error message; they have the same
     meaning and values as in *note PyUnicode_FromFormat(): 33f.
     'format' is an ASCII-encoded string.

 -- C 函式: *note PyObject: 311. *PyErr_FormatV (PyObject *exception,
          const char *format, va_list vargs)
     '回傳值：總是為 NULL。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.5 版
     本開始.'  Same as *note PyErr_Format(): e53, but taking a ‘va_list’
     argument rather than a variable number of arguments.

     在 3.5 版被加入.

 -- C 函式: void PyErr_SetNone (PyObject *type)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This is a shorthand for
     ‘PyErr_SetObject(type, Py_None)’.

 -- C 函式: int PyErr_BadArgument ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This is a shorthand for
     ‘PyErr_SetString(PyExc_TypeError, message)’, where 'message'
     indicates that a built-in operation was invoked with an illegal
     argument.  It is mostly for internal use.

 -- C 函式: *note PyObject: 311. *PyErr_NoMemory ()
     '回傳值：總是為 NULL。'' 為 *note 穩定 ABI 的一部分: 4f9.'  This is
     a shorthand for ‘PyErr_SetNone(PyExc_MemoryError)’; it returns
     ‘NULL’ so an object allocation function can write ‘return
     PyErr_NoMemory();’ when it runs out of memory.

 -- C 函式: *note PyObject: 311. *PyErr_SetFromErrno (PyObject *type)
     '回傳值：總是為 NULL。'' 為 *note 穩定 ABI 的一部分: 4f9.'

     This is a convenience function to raise an exception when a C
     library function has returned an error and set the C variable
     ‘errno’.  It constructs a tuple object whose first item is the
     integer ‘errno’ value and whose second item is the corresponding
     error message (gotten from ‘strerror()’), and then calls
     ‘PyErr_SetObject(type, object)’.  On Unix, when the ‘errno’ value
     is ‘EINTR’, indicating an interrupted system call, this calls *note
     PyErr_CheckSignals(): 40d, and if that set the error indicator,
     leaves it set to that.  The function always returns ‘NULL’, so a
     wrapper function around a system call can write ‘return
     PyErr_SetFromErrno(type);’ when the system call returns an error.

 -- C 函式: *note PyObject: 311. *PyErr_SetFromErrnoWithFilenameObject
          (PyObject *type, PyObject *filenameObject)
     '回傳值：總是為 NULL。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Similar
     to *note PyErr_SetFromErrno(): 46d2, with the additional behavior
     that if 'filenameObject' is not ‘NULL’, it is passed to the
     constructor of 'type' as a third parameter.  In the case of *note
     OSError: 350. exception, this is used to define the ‘filename’
     attribute of the exception instance.

 -- C 函式: *note PyObject: 311. *PyErr_SetFromErrnoWithFilenameObjects
          (PyObject *type, PyObject *filenameObject, PyObject
          *filenameObject2)
     '回傳值：總是為 NULL。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版
     本開始.'  Similar to *note PyErr_SetFromErrnoWithFilenameObject():
     47c6, but takes a second filename object, for raising errors when a
     function that takes two filenames fails.

     在 3.4 版被加入.

 -- C 函式: *note PyObject: 311. *PyErr_SetFromErrnoWithFilename
          (PyObject *type, const char *filename)
     '回傳值：總是為 NULL。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Similar
     to *note PyErr_SetFromErrnoWithFilenameObject(): 47c6, but the
     filename is given as a C string.  'filename' is decoded from the
     *note filesystem encoding and error handler: 4e0.

 -- C 函式: *note PyObject: 311. *PyErr_SetFromWindowsErr (int ierr)
     '回傳值：總是為 NULL。'' 為 *note 穩定 ABI 的一部分: 4f9. on
     Windows 自 3.7 版本開始.'  This is a convenience function to raise
     *note OSError: 350.  If called with 'ierr' of ‘0’, the error code
     returned by a call to ‘GetLastError()’ is used instead.  It calls
     the Win32 function ‘FormatMessage()’ to retrieve the Windows
     description of error code given by 'ierr' or ‘GetLastError()’, then
     it constructs a *note OSError: 350. object with the *note winerror:
     216a. attribute set to the error code, the *note strerror: 216b.
     attribute set to the corresponding error message (gotten from
     ‘FormatMessage()’), and then calls ‘PyErr_SetObject(PyExc_OSError,
     object)’.  This function always returns ‘NULL’.

     *note 適用: 1c56.：Windows。

 -- C 函式: *note PyObject: 311. *PyErr_SetExcFromWindowsErr (PyObject
          *type, int ierr)
     '回傳值：總是為 NULL。'' 為 *note 穩定 ABI 的一部分: 4f9. on
     Windows 自 3.7 版本開始.'  Similar to *note
     PyErr_SetFromWindowsErr(): 47c8, with an additional parameter
     specifying the exception type to be raised.

     *note 適用: 1c56.：Windows。

 -- C 函式: *note PyObject: 311. *PyErr_SetFromWindowsErrWithFilename
          (int ierr, const char *filename)
     '回傳值：總是為 NULL。'' 為 *note 穩定 ABI 的一部分: 4f9. on
     Windows 自 3.7 版本開始.'  Similar to *note
     PyErr_SetFromWindowsErr(): 47c8, with the additional behavior that
     if 'filename' is not ‘NULL’, it is decoded from the filesystem
     encoding (*note os.fsdecode(): bfb.) and passed to the constructor
     of *note OSError: 350. as a third parameter to be used to define
     the ‘filename’ attribute of the exception instance.

     *note 適用: 1c56.：Windows。

 -- C 函式: *note PyObject: 311.
          *PyErr_SetExcFromWindowsErrWithFilenameObject (PyObject *type,
          int ierr, PyObject *filename)
     '回傳值：總是為 NULL。'' 為 *note 穩定 ABI 的一部分: 4f9. on
     Windows 自 3.7 版本開始.'  Similar to *note
     PyErr_SetExcFromWindowsErr(): 47c3, with the additional behavior
     that if 'filename' is not ‘NULL’, it is passed to the constructor
     of *note OSError: 350. as a third parameter to be used to define
     the ‘filename’ attribute of the exception instance.

     *note 適用: 1c56.：Windows。

 -- C 函式: *note PyObject: 311.
          *PyErr_SetExcFromWindowsErrWithFilenameObjects (PyObject
          *type, int ierr, PyObject *filename, PyObject *filename2)
     '回傳值：總是為 NULL。'' 為 *note 穩定 ABI 的一部分: 4f9. on
     Windows 自 3.7 版本開始.'  Similar to *note
     PyErr_SetExcFromWindowsErrWithFilenameObject(): 47c4, but accepts a
     second filename object.

     *note 適用: 1c56.：Windows。

     在 3.4 版被加入.

 -- C 函式: *note PyObject: 311. *PyErr_SetExcFromWindowsErrWithFilename
          (PyObject *type, int ierr, const char *filename)
     '回傳值：總是為 NULL。'' 為 *note 穩定 ABI 的一部分: 4f9. on
     Windows 自 3.7 版本開始.'  Similar to *note
     PyErr_SetFromWindowsErrWithFilename(): 1616, with an additional
     parameter specifying the exception type to be raised.

     *note 適用: 1c56.：Windows。

 -- C 函式: *note PyObject: 311. *PyErr_SetImportError (PyObject *msg,
          PyObject *name, PyObject *path)
     '回傳值：總是為 NULL。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版
     本開始.'  This is a convenience function to raise *note
     ImportError: 352.  'msg' will be set as the exception's message
     string.  'name' and 'path', both of which can be ‘NULL’, will be
     set as the *note ImportError: 352.'s respective ‘name’ and ‘path’
     attributes.

     在 3.3 版被加入.

 -- C 函式: *note PyObject: 311. *PyErr_SetImportErrorSubclass (PyObject
          *exception, PyObject *msg, PyObject *name, PyObject *path)
     '回傳值：總是為 NULL。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.6 版
     本開始.'  Much like *note PyErr_SetImportError(): ce5. but this
     function allows for specifying a subclass of *note ImportError:
     352. to raise.

     在 3.6 版被加入.

 -- C 函式: void PyErr_SyntaxLocationObject (PyObject *filename, int
          lineno, int col_offset)

     Set file, line, and offset information for the current exception.
     If the current exception is not a *note SyntaxError: 173, then it
     sets additional attributes, which make the exception printing
     subsystem think the exception is a *note SyntaxError: 173.

     在 3.4 版被加入.

 -- C 函式: void PyErr_SyntaxLocationEx (const char *filename, int
          lineno, int col_offset)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Like *note
     PyErr_SyntaxLocationObject(): 4902, but 'filename' is a byte string
     decoded from the *note filesystem encoding and error handler: 4e0.

     在 3.2 版被加入.

 -- C 函式: void PyErr_SyntaxLocation (const char *filename, int lineno)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Like *note
     PyErr_SyntaxLocationEx(): 47cc, but the 'col_offset' parameter is
     omitted.

 -- C 函式: void PyErr_BadInternalCall ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This is a shorthand for
     ‘PyErr_SetString(PyExc_SystemError, message)’, where 'message'
     indicates that an internal operation (e.g.  a Python/C API
     function) was invoked with an illegal argument.  It is mostly for
     internal use.


File: python.info,  Node: Issuing warnings,  Next: Querying the error indicator,  Prev: Raising exceptions,  Up: 例外處理

7.5.3 Issuing warnings
----------------------

Use these functions to issue warnings from C code.  They mirror similar
functions exported by the Python *note warnings: fa. module.  They
normally print a warning message to 'sys.stderr'; however, it is also
possible that the user has specified that warnings are to be turned into
errors, and in that case they will raise an exception.  It is also
possible that the functions raise an exception because of a problem with
the warning machinery.  The return value is ‘0’ if no exception is
raised, or ‘-1’ if an exception is raised.  (It is not possible to
determine whether a warning message is actually printed, nor what the
reason is for the exception; this is intentional.)  If an exception is
raised, the caller should do its normal exception handling (for example,
*note Py_DECREF(): 515. owned references and return an error value).

 -- C 函式: int PyErr_WarnEx (PyObject *category, const char *message,
          Py_ssize_t stack_level)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Issue a warning message.  The
     'category' argument is a warning category (see below) or ‘NULL’;
     the 'message' argument is a UTF-8 encoded string.  'stack_level' is
     a positive number giving a number of stack frames; the warning will
     be issued from the currently executing line of code in that stack
     frame.  A 'stack_level' of 1 is the function calling *note
     PyErr_WarnEx(): 13b8, 2 is the function above that, and so forth.

     Warning categories must be subclasses of ‘PyExc_Warning’;
     ‘PyExc_Warning’ is a subclass of ‘PyExc_Exception’; the default
     warning category is ‘PyExc_RuntimeWarning’.  The standard Python
     warning categories are available as global variables whose names
     are enumerated at *note Standard Warning Categories: 4904.

     For information about warning control, see the documentation for
     the *note warnings: fa. module and the *note -W: 86c. option in the
     command line documentation.  There is no C API for warning control.

 -- C 函式: int PyErr_WarnExplicitObject (PyObject *category, PyObject
          *message, PyObject *filename, int lineno, PyObject *module,
          PyObject *registry)

     Issue a warning message with explicit control over all warning
     attributes.  This is a straightforward wrapper around the Python
     function *note warnings.warn_explicit(): ca7.; see there for more
     information.  The 'module' and 'registry' arguments may be set to
     ‘NULL’ to get the default effect described there.

     在 3.4 版被加入.

 -- C 函式: int PyErr_WarnExplicit (PyObject *category, const char
          *message, const char *filename, int lineno, const char
          *module, PyObject *registry)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Similar to *note
     PyErr_WarnExplicitObject(): 4905. except that 'message' and
     'module' are UTF-8 encoded strings, and 'filename' is decoded from
     the *note filesystem encoding and error handler: 4e0.

 -- C 函式: int PyErr_WarnFormat (PyObject *category, Py_ssize_t
          stack_level, const char *format, ...)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Function similar to *note
     PyErr_WarnEx(): 13b8, but use *note PyUnicode_FromFormat(): 33f. to
     format the warning message.  'format' is an ASCII-encoded string.

     在 3.2 版被加入.

 -- C 函式: int PyErr_ResourceWarning (PyObject *source, Py_ssize_t
          stack_level, const char *format, ...)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.6 版本開始.'  Function
     similar to *note PyErr_WarnFormat(): 47cd, but 'category' is *note
     ResourceWarning: 229. and it passes 'source' to
     ‘warnings.WarningMessage’.

     在 3.6 版被加入.


File: python.info,  Node: Querying the error indicator,  Next: Signal Handling<2>,  Prev: Issuing warnings,  Up: 例外處理

7.5.4 Querying the error indicator
----------------------------------

 -- C 函式: *note PyObject: 311. *PyErr_Occurred ()
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Test
     whether the error indicator is set.  If set, return the exception
     'type' (the first argument to the last call to one of the
     ‘PyErr_Set*’ functions or to *note PyErr_Restore(): 3be.).  If not
     set, return ‘NULL’.  You do not own a reference to the return
     value, so you do not need to *note Py_DECREF(): 515. it.

     The caller must hold the GIL.

          備註: Do not compare the return value to a specific exception;
          use *note PyErr_ExceptionMatches(): 476a. instead, shown
          below.  (The comparison could easily fail since the exception
          may be an instance instead of a class, in the case of a class
          exception, or it may be a subclass of the expected exception.)

 -- C 函式: int PyErr_ExceptionMatches (PyObject *exc)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Equivalent to
     ‘PyErr_GivenExceptionMatches(PyErr_Occurred(), exc)’.  This should
     only be called when an exception is actually set; a memory access
     violation will occur if no exception has been raised.

 -- C 函式: int PyErr_GivenExceptionMatches (PyObject *given, PyObject
          *exc)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return true if the 'given'
     exception matches the exception type in 'exc'.  If 'exc' is a class
     object, this also returns true when 'given' is an instance of a
     subclass.  If 'exc' is a tuple, all exception types in the tuple
     (and recursively in subtuples) are searched for a match.

 -- C 函式: *note PyObject: 311. *PyErr_GetRaisedException (void)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.12 版本
     開始.'  Return the exception currently being raised, clearing the
     error indicator at the same time.  Return ‘NULL’ if the error
     indicator is not set.

     This function is used by code that needs to catch exceptions, or
     code that needs to save and restore the error indicator
     temporarily.

     舉例來說：

          {
             PyObject *exc = PyErr_GetRaisedException();

             /* ... code that might produce other errors ... */

             PyErr_SetRaisedException(exc);
          }

     也參考
     ......

     *note PyErr_GetHandledException(): 713, to save the exception
     currently being handled.

     在 3.12 版被加入.

 -- C 函式: void PyErr_SetRaisedException (PyObject *exc)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.12 版本開始.'  Set 'exc' as
     the exception currently being raised, clearing the existing
     exception if one is set.

          警告: This call steals a reference to 'exc', which must be a
          valid exception.

     在 3.12 版被加入.

 -- C 函式: void PyErr_Fetch (PyObject **ptype, PyObject **pvalue,
          PyObject **ptraceback)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     在 3.12 版之後被棄用: Use *note PyErr_GetRaisedException(): 3bc.
     instead.

     Retrieve the error indicator into three variables whose addresses
     are passed.  If the error indicator is not set, set all three
     variables to ‘NULL’.  If it is set, it will be cleared and you own
     a reference to each object retrieved.  The value and traceback
     object may be ‘NULL’ even when the type object is not.

          備註: This function is normally only used by legacy code that
          needs to catch exceptions or save and restore the error
          indicator temporarily.

          舉例來說：

               {
                  PyObject *type, *value, *traceback;
                  PyErr_Fetch(&type, &value, &traceback);

                  /* ... code that might produce other errors ... */

                  PyErr_Restore(type, value, traceback);
               }

 -- C 函式: void PyErr_Restore (PyObject *type, PyObject *value,
          PyObject *traceback)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     在 3.12 版之後被棄用: Use *note PyErr_SetRaisedException(): 3bf.
     instead.

     Set the error indicator from the three objects, 'type', 'value',
     and 'traceback', clearing the existing exception if one is set.  If
     the objects are ‘NULL’, the error indicator is cleared.  Do not
     pass a ‘NULL’ type and non-‘NULL’ value or traceback.  The
     exception type should be a class.  Do not pass an invalid exception
     type or value.  (Violating these rules will cause subtle problems
     later.)  This call takes away a reference to each object: you must
     own a reference to each object before the call and after the call
     you no longer own these references.  (If you don't understand this,
     don't use this function.  I warned you.)

          備註: This function is normally only used by legacy code that
          needs to save and restore the error indicator temporarily.
          Use *note PyErr_Fetch(): 3bb. to save the current error
          indicator.

 -- C 函式: void PyErr_NormalizeException (PyObject **exc, PyObject
          **val, PyObject **tb)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     在 3.12 版之後被棄用: Use *note PyErr_GetRaisedException(): 3bc.
     instead, to avoid any possible de-normalization.

     Under certain circumstances, the values returned by *note
     PyErr_Fetch(): 3bb. below can be "unnormalized", meaning that
     ‘*exc’ is a class object but ‘*val’ is not an instance of the same
     class.  This function can be used to instantiate the class in that
     case.  If the values are already normalized, nothing happens.  The
     delayed normalization is implemented to improve performance.

          備註: This function 'does not' implicitly set the *note
          __traceback__: 125b. attribute on the exception value.  If
          setting the traceback appropriately is desired, the following
          additional snippet is needed:

               if (tb != NULL) {
                 PyException_SetTraceback(val, tb);
               }

 -- C 函式: *note PyObject: 311. *PyErr_GetHandledException (void)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.11 版本開始.'  Retrieve the
     active exception instance, as would be returned by *note
     sys.exception(): 631.  This refers to an exception that was
     'already caught', not to an exception that was freshly raised.
     Returns a new reference to the exception or ‘NULL’.  Does not
     modify the interpreter's exception state.

          備註: This function is not normally used by code that wants to
          handle exceptions.  Rather, it can be used when code needs to
          save and restore the exception state temporarily.  Use *note
          PyErr_SetHandledException(): 714. to restore or clear the
          exception state.

     在 3.11 版被加入.

 -- C 函式: void PyErr_SetHandledException (PyObject *exc)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.11 版本開始.'  Set the
     active exception, as known from ‘sys.exception()’.  This refers to
     an exception that was 'already caught', not to an exception that
     was freshly raised.  To clear the exception state, pass ‘NULL’.

          備註: This function is not normally used by code that wants to
          handle exceptions.  Rather, it can be used when code needs to
          save and restore the exception state temporarily.  Use *note
          PyErr_GetHandledException(): 713. to get the exception state.

     在 3.11 版被加入.

 -- C 函式: void PyErr_GetExcInfo (PyObject **ptype, PyObject **pvalue,
          PyObject **ptraceback)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Retrieve the
     old-style representation of the exception info, as known from *note
     sys.exc_info(): 630.  This refers to an exception that was 'already
     caught', not to an exception that was freshly raised.  Returns new
     references for the three objects, any of which may be ‘NULL’.  Does
     not modify the exception info state.  This function is kept for
     backwards compatibility.  Prefer using *note
     PyErr_GetHandledException(): 713.

          備註: This function is not normally used by code that wants to
          handle exceptions.  Rather, it can be used when code needs to
          save and restore the exception state temporarily.  Use *note
          PyErr_SetExcInfo(): 715. to restore or clear the exception
          state.

     在 3.3 版被加入.

 -- C 函式: void PyErr_SetExcInfo (PyObject *type, PyObject *value,
          PyObject *traceback)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Set the
     exception info, as known from ‘sys.exc_info()’.  This refers to an
     exception that was 'already caught', not to an exception that was
     freshly raised.  This function steals the references of the
     arguments.  To clear the exception state, pass ‘NULL’ for all three
     arguments.  This function is kept for backwards compatibility.
     Prefer using *note PyErr_SetHandledException(): 714.

          備註: This function is not normally used by code that wants to
          handle exceptions.  Rather, it can be used when code needs to
          save and restore the exception state temporarily.  Use *note
          PyErr_GetExcInfo(): 716. to read the exception state.

     在 3.3 版被加入.

     在 3.11 版的變更: The ‘type’ and ‘traceback’ arguments are no
     longer used and can be NULL. The interpreter now derives them from
     the exception instance (the ‘value’ argument).  The function still
     steals references of all three arguments.


File: python.info,  Node: Signal Handling<2>,  Next: 例外類別<2>,  Prev: Querying the error indicator,  Up: 例外處理

7.5.5 Signal Handling
---------------------

 -- C 函式: int PyErr_CheckSignals ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     This function interacts with Python's signal handling.

     If the function is called from the main thread and under the main
     Python interpreter, it checks whether a signal has been sent to the
     processes and if so, invokes the corresponding signal handler.  If
     the *note signal: b4. module is supported, this can invoke a signal
     handler written in Python.

     The function attempts to handle all pending signals, and then
     returns ‘0’.  However, if a Python signal handler raises an
     exception, the error indicator is set and the function returns ‘-1’
     immediately (such that other pending signals may not have been
     handled yet: they will be on the next *note PyErr_CheckSignals():
     40d. invocation).

     If the function is called from a non-main thread, or under a
     non-main Python interpreter, it does nothing and returns ‘0’.

     This function can be called by long-running C code that wants to be
     interruptible by user requests (such as by pressing Ctrl-C).

          備註: The default Python signal handler for ‘SIGINT’ raises
          the *note KeyboardInterrupt: 975. exception.

 -- C 函式: void PyErr_SetInterrupt ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     Simulate the effect of a ‘SIGINT’ signal arriving.  This is
     equivalent to ‘PyErr_SetInterruptEx(SIGINT)’.

          備註: This function is async-signal-safe.  It can be called
          without the *note GIL: 13e. and from a C signal handler.

 -- C 函式: int PyErr_SetInterruptEx (int signum)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本開始.'

     Simulate the effect of a signal arriving.  The next time *note
     PyErr_CheckSignals(): 40d. is called, the Python signal handler for
     the given signal number will be called.

     This function can be called by C code that sets up its own signal
     handling and wants Python signal handlers to be invoked as expected
     when an interruption is requested (for example when the user
     presses Ctrl-C to interrupt an operation).

     If the given signal isn't handled by Python (it was set to *note
     signal.SIG_DFL: 1726. or *note signal.SIG_IGN: 1725.), it will be
     ignored.

     If 'signum' is outside of the allowed range of signal numbers, ‘-1’
     is returned.  Otherwise, ‘0’ is returned.  The error indicator is
     never changed by this function.

          備註: This function is async-signal-safe.  It can be called
          without the *note GIL: 13e. and from a C signal handler.

     在 3.10 版被加入.

 -- C 函式: int PySignal_SetWakeupFd (int fd)

     This utility function specifies a file descriptor to which the
     signal number is written as a single byte whenever a signal is
     received.  'fd' must be non-blocking.  It returns the previous such
     file descriptor.

     The value ‘-1’ disables the feature; this is the initial state.
     This is equivalent to *note signal.set_wakeup_fd(): b14. in Python,
     but without any error checking.  'fd' should be a valid file
     descriptor.  The function should only be called from the main
     thread.

     在 3.5 版的變更: On Windows, the function now also supports socket
     handles.


File: python.info,  Node: 例外類別<2>,  Next: 例外物件,  Prev: Signal Handling<2>,  Up: 例外處理

7.5.6 例外類別
--------------

 -- C 函式: *note PyObject: 311. *PyErr_NewException (const char *name,
          PyObject *base, PyObject *dict)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  This
     utility function creates and returns a new exception class.  The
     'name' argument must be the name of the new exception, a C string
     of the form ‘module.classname’.  The 'base' and 'dict' arguments
     are normally ‘NULL’.  This creates a class object derived from
     *note Exception: 97d. (accessible in C as ‘PyExc_Exception’).

     The ‘__module__’ attribute of the new class is set to the first
     part (up to the last dot) of the 'name' argument, and the class
     name is set to the last part (after the last dot).  The 'base'
     argument can be used to specify alternate base classes; it can
     either be only one class or a tuple of classes.  The 'dict'
     argument can be used to specify a dictionary of class variables and
     methods.

 -- C 函式: *note PyObject: 311. *PyErr_NewExceptionWithDoc (const char
          *name, const char *doc, PyObject *base, PyObject *dict)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Same as
     *note PyErr_NewException(): 1202, except that the new exception
     class can easily be given a docstring: If 'doc' is non-‘NULL’, it
     will be used as the docstring for the exception class.

     在 3.2 版被加入.


File: python.info,  Node: 例外物件,  Next: Unicode Exception Objects,  Prev: 例外類別<2>,  Up: 例外處理

7.5.7 例外物件
--------------

 -- C 函式: *note PyObject: 311. *PyException_GetTraceback (PyObject
          *ex)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the
     traceback associated with the exception as a new reference, as
     accessible from Python through the *note __traceback__: 125b.
     attribute.  If there is no traceback associated, this returns
     ‘NULL’.

 -- C 函式: int PyException_SetTraceback (PyObject *ex, PyObject *tb)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Set the traceback associated
     with the exception to 'tb'.  Use ‘Py_None’ to clear it.

 -- C 函式: *note PyObject: 311. *PyException_GetContext (PyObject *ex)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the
     context (another exception instance during whose handling 'ex' was
     raised) associated with the exception as a new reference, as
     accessible from Python through the *note __context__: 125c.
     attribute.  If there is no context associated, this returns ‘NULL’.

 -- C 函式: void PyException_SetContext (PyObject *ex, PyObject *ctx)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Set the context associated
     with the exception to 'ctx'.  Use ‘NULL’ to clear it.  There is no
     type check to make sure that 'ctx' is an exception instance.  This
     steals a reference to 'ctx'.

 -- C 函式: *note PyObject: 311. *PyException_GetCause (PyObject *ex)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the
     cause (either an exception instance, or ‘None’, set by ‘raise ...
     from ...’) associated with the exception as a new reference, as
     accessible from Python through the *note __cause__: 125d.
     attribute.

 -- C 函式: void PyException_SetCause (PyObject *ex, PyObject *cause)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Set the cause associated with
     the exception to 'cause'.  Use ‘NULL’ to clear it.  There is no
     type check to make sure that 'cause' is either an exception
     instance or ‘None’.  This steals a reference to 'cause'.

     The *note __suppress_context__: 1f8b. attribute is implicitly set
     to ‘True’ by this function.

 -- C 函式: *note PyObject: 311. *PyException_GetArgs (PyObject *ex)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.12 版本
     開始.'  Return *note args: 512. of exception 'ex'.

 -- C 函式: void PyException_SetArgs (PyObject *ex, PyObject *args)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.12 版本開始.'  Set *note
     args: 512. of exception 'ex' to 'args'.

 -- C 函式: *note PyObject: 311. *PyUnstable_Exc_PrepReraiseStar
          (PyObject *orig, PyObject *excs)

          這是 不穩定 API，它可能在小版本發布中沒有任何警告地被變更。 '這是 *note 不穩定 API: 4ed.，它可能在小版本發布中沒有任何警告地被變更。': 
     Implement part of the interpreter's implementation of ‘except*’.
     'orig' is the original exception that was caught, and 'excs' is the
     list of the exceptions that need to be raised.  This list contains
     the unhandled part of 'orig', if any, as well as the exceptions
     that were raised from the ‘except*’ clauses (so they have a
     different traceback from 'orig') and those that were reraised (and
     have the same traceback as 'orig').  Return the *note
     ExceptionGroup: 19c. that needs to be reraised in the end, or
     ‘None’ if there is nothing to reraise.

     在 3.12 版被加入.


File: python.info,  Node: Unicode Exception Objects,  Next: Recursion Control,  Prev: 例外物件,  Up: 例外處理

7.5.8 Unicode Exception Objects
-------------------------------

The following functions are used to create and modify Unicode exceptions
from C.

 -- C 函式: *note PyObject: 311. *PyUnicodeDecodeError_Create (const
          char *encoding, const char *object, Py_ssize_t length,
          Py_ssize_t start, Py_ssize_t end, const char *reason)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a
     *note UnicodeDecodeError: 9b7. object with the attributes
     'encoding', 'object', 'length', 'start', 'end' and 'reason'.
     'encoding' and 'reason' are UTF-8 encoded strings.

 -- C 函式: *note PyObject: 311. *PyUnicodeDecodeError_GetEncoding
          (PyObject *exc)
 -- C 函式: *note PyObject: 311. *PyUnicodeEncodeError_GetEncoding
          (PyObject *exc)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the
     'encoding' attribute of the given exception object.

 -- C 函式: *note PyObject: 311. *PyUnicodeDecodeError_GetObject
          (PyObject *exc)
 -- C 函式: *note PyObject: 311. *PyUnicodeEncodeError_GetObject
          (PyObject *exc)
 -- C 函式: *note PyObject: 311. *PyUnicodeTranslateError_GetObject
          (PyObject *exc)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the
     'object' attribute of the given exception object.

 -- C 函式: int PyUnicodeDecodeError_GetStart (PyObject *exc, Py_ssize_t
          *start)
 -- C 函式: int PyUnicodeEncodeError_GetStart (PyObject *exc, Py_ssize_t
          *start)
 -- C 函式: int PyUnicodeTranslateError_GetStart (PyObject *exc,
          Py_ssize_t *start)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Get the 'start' attribute of
     the given exception object and place it into '*start'.  'start'
     must not be ‘NULL’.  Return ‘0’ on success, ‘-1’ on failure.

 -- C 函式: int PyUnicodeDecodeError_SetStart (PyObject *exc, Py_ssize_t
          start)
 -- C 函式: int PyUnicodeEncodeError_SetStart (PyObject *exc, Py_ssize_t
          start)
 -- C 函式: int PyUnicodeTranslateError_SetStart (PyObject *exc,
          Py_ssize_t start)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Set the 'start' attribute of
     the given exception object to 'start'.  Return ‘0’ on success, ‘-1’
     on failure.

 -- C 函式: int PyUnicodeDecodeError_GetEnd (PyObject *exc, Py_ssize_t
          *end)
 -- C 函式: int PyUnicodeEncodeError_GetEnd (PyObject *exc, Py_ssize_t
          *end)
 -- C 函式: int PyUnicodeTranslateError_GetEnd (PyObject *exc,
          Py_ssize_t *end)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Get the 'end' attribute of the
     given exception object and place it into '*end'.  'end' must not be
     ‘NULL’.  Return ‘0’ on success, ‘-1’ on failure.

 -- C 函式: int PyUnicodeDecodeError_SetEnd (PyObject *exc, Py_ssize_t
          end)
 -- C 函式: int PyUnicodeEncodeError_SetEnd (PyObject *exc, Py_ssize_t
          end)
 -- C 函式: int PyUnicodeTranslateError_SetEnd (PyObject *exc,
          Py_ssize_t end)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Set the 'end' attribute of the
     given exception object to 'end'.  Return ‘0’ on success, ‘-1’ on
     failure.

 -- C 函式: *note PyObject: 311. *PyUnicodeDecodeError_GetReason
          (PyObject *exc)
 -- C 函式: *note PyObject: 311. *PyUnicodeEncodeError_GetReason
          (PyObject *exc)
 -- C 函式: *note PyObject: 311. *PyUnicodeTranslateError_GetReason
          (PyObject *exc)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the
     'reason' attribute of the given exception object.

 -- C 函式: int PyUnicodeDecodeError_SetReason (PyObject *exc, const
          char *reason)
 -- C 函式: int PyUnicodeEncodeError_SetReason (PyObject *exc, const
          char *reason)
 -- C 函式: int PyUnicodeTranslateError_SetReason (PyObject *exc, const
          char *reason)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Set the 'reason' attribute of
     the given exception object to 'reason'.  Return ‘0’ on success,
     ‘-1’ on failure.


File: python.info,  Node: Recursion Control,  Next: Standard Exceptions,  Prev: Unicode Exception Objects,  Up: 例外處理

7.5.9 Recursion Control
-----------------------

These two functions provide a way to perform safe recursive calls at the
C level, both in the core and in extension modules.  They are needed if
the recursive code does not necessarily invoke Python code (which tracks
its recursion depth automatically).  They are also not needed for
'tp_call' implementations because the *note call protocol: 529. takes
care of recursion handling.

 -- C 函式: int Py_EnterRecursiveCall (const char *where)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.9 版本開始.'  Marks a point
     where a recursive C-level call is about to be performed.

     If ‘USE_STACKCHECK’ is defined, this function checks if the OS
     stack overflowed using *note PyOS_CheckStack(): 171b.  If this is
     the case, it sets a *note MemoryError: 15bc. and returns a nonzero
     value.

     The function then checks if the recursion limit is reached.  If
     this is the case, a *note RecursionError: d12. is set and a nonzero
     value is returned.  Otherwise, zero is returned.

     'where' should be a UTF-8 encoded string such as ‘" in instance
     check"’ to be concatenated to the *note RecursionError: d12.
     message caused by the recursion depth limit.

     在 3.9 版的變更: This function is now also available in the *note
     limited API: 318.

 -- C 函式: void Py_LeaveRecursiveCall (void)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.9 版本開始.'  Ends a *note
     Py_EnterRecursiveCall(): 917.  Must be called once for each
     'successful' invocation of *note Py_EnterRecursiveCall(): 917.

     在 3.9 版的變更: This function is now also available in the *note
     limited API: 318.

Properly implementing *note tp_repr: 4719. for container types requires
special recursion handling.  In addition to protecting the stack, *note
tp_repr: 4719. also needs to track objects to prevent cycles.  The
following two functions facilitate this functionality.  Effectively,
these are the C equivalent to *note reprlib.recursive_repr(): 118b.

 -- C 函式: int Py_ReprEnter (PyObject *object)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Called at the beginning of the
     *note tp_repr: 4719. implementation to detect cycles.

     If the object has already been processed, the function returns a
     positive integer.  In that case the *note tp_repr: 4719.
     implementation should return a string object indicating a cycle.
     As examples, *note dict: 23b. objects return ‘{...}’ and *note
     list: 5b6. objects return ‘[...]’.

     The function will return a negative integer if the recursion limit
     is reached.  In that case the *note tp_repr: 4719. implementation
     should typically return ‘NULL’.

     Otherwise, the function returns zero and the *note tp_repr: 4719.
     implementation can continue normally.

 -- C 函式: void Py_ReprLeave (PyObject *object)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Ends a *note Py_ReprEnter():
     48bd.  Must be called once for each invocation of *note
     Py_ReprEnter(): 48bd. that returns zero.


File: python.info,  Node: Standard Exceptions,  Next: Standard Warning Categories,  Prev: Recursion Control,  Up: 例外處理

7.5.10 Standard Exceptions
--------------------------

All standard Python exceptions are available as global variables whose
names are ‘PyExc_’ followed by the Python exception name.  These have
the type *note PyObject: 311.*; they are all class objects.  For
completeness, here are all the variables:

C 名稱                                        Python 名稱                           註解
                                                                                    
---------------------------------------------------------------------------------------------------
                                                                                    
‘PyExc_BaseException’                         *note BaseException: 55f.             (1)
                                                                                    
                                                                                    
‘PyExc_Exception’                             *note Exception: 97d.                 (2)
                                                                                    
                                                                                    
‘PyExc_ArithmeticError’                       *note ArithmeticError: 2162.          (3)
                                                                                    
                                                                                    
‘PyExc_AssertionError’                        *note AssertionError: 64e.
                                              
                                                                                    
‘PyExc_AttributeError’                        *note AttributeError: 2f6.
                                              
                                                                                    
‘PyExc_BlockingIOError’                       *note BlockingIOError: ffa.
                                              
                                                                                    
‘PyExc_BrokenPipeError’                       *note BrokenPipeError: fff.
                                              
                                                                                    
‘PyExc_BufferError’                           *note BufferError: 1729.
                                              
                                                                                    
‘PyExc_ChildProcessError’                     *note ChildProcessError: ffb.
                                              
                                                                                    
‘PyExc_ConnectionAbortedError’                *note ConnectionAbortedError: 1000.
                                              
                                                                                    
‘PyExc_ConnectionError’                       *note ConnectionError: db0.
                                              
                                                                                    
‘PyExc_ConnectionRefusedError’                *note ConnectionRefusedError: 1001.
                                              
                                                                                    
‘PyExc_ConnectionResetError’                  *note ConnectionResetError: 1002.
                                              
                                                                                    
‘PyExc_EOFError’                              *note EOFError: 126c.
                                              
                                                                                    
‘PyExc_FileExistsError’                       *note FileExistsError: fc3.
                                              
                                                                                    
‘PyExc_FileNotFoundError’                     *note FileNotFoundError: e67.
                                              
                                                                                    
‘PyExc_FloatingPointError’                    *note FloatingPointError: 2163.
                                              
                                                                                    
‘PyExc_GeneratorExit’                         *note GeneratorExit: 1335.
                                              
                                                                                    
‘PyExc_ImportError’                           *note ImportError: 352.
                                              
                                                                                    
‘PyExc_IndentationError’                      *note IndentationError: 74c.
                                              
                                                                                    
‘PyExc_IndexError’                            *note IndexError: 14a3.
                                              
                                                                                    
‘PyExc_InterruptedError’                      *note InterruptedError: d2e.
                                              
                                                                                    
‘PyExc_IsADirectoryError’                     *note IsADirectoryError: ffc.
                                              
                                                                                    
‘PyExc_KeyError’                              *note KeyError: 2fb.
                                              
                                                                                    
‘PyExc_KeyboardInterrupt’                     *note KeyboardInterrupt: 975.
                                              
                                                                                    
‘PyExc_LookupError’                           *note LookupError: 20a9.              (4)
                                                                                    
                                                                                    
‘PyExc_MemoryError’                           *note MemoryError: 15bc.
                                              
                                                                                    
‘PyExc_ModuleNotFoundError’                   *note ModuleNotFoundError: aeb.
                                              
                                                                                    
‘PyExc_NameError’                             *note NameError: 3e5.
                                              
                                                                                    
‘PyExc_NotADirectoryError’                    *note NotADirectoryError: ffd.
                                              
                                                                                    
‘PyExc_NotImplementedError’                   *note NotImplementedError: 20d.
                                              
                                                                                    
‘PyExc_OSError’                               *note OSError: 350.                   (5)
                                                                                    
                                                                                    
‘PyExc_OverflowError’                         *note OverflowError: 825.
                                              
                                                                                    
‘PyExc_PermissionError’                       *note PermissionError: ce9.
                                              
                                                                                    
‘PyExc_ProcessLookupError’                    *note ProcessLookupError: ffe.
                                              
                                                                                    
‘PyExc_RecursionError’                        *note RecursionError: d12.
                                              
                                                                                    
‘PyExc_ReferenceError’                        *note ReferenceError: 147d.
                                              
                                                                                    
‘PyExc_RuntimeError’                          *note RuntimeError: 179.
                                              
                                                                                    
‘PyExc_StopAsyncIteration’                    *note StopAsyncIteration: 1933.
                                              
                                                                                    
‘PyExc_StopIteration’                         *note StopIteration: ba1.
                                              
                                                                                    
‘PyExc_SyntaxError’                           *note SyntaxError: 173.
                                              
                                                                                    
‘PyExc_SystemError’                           *note SystemError: 51b.
                                              
                                                                                    
‘PyExc_SystemExit’                            *note SystemExit: ce7.
                                              
                                                                                    
‘PyExc_TabError’                              *note TabError: 4e9.
                                              
                                                                                    
‘PyExc_TimeoutError’                          *note TimeoutError: 7d9.
                                              
                                                                                    
‘PyExc_TypeError’                             *note TypeError: 4dd.
                                              
                                                                                    
‘PyExc_UnboundLocalError’                     *note UnboundLocalError: 14a4.
                                              
                                                                                    
‘PyExc_UnicodeDecodeError’                    *note UnicodeDecodeError: 9b7.
                                              
                                                                                    
‘PyExc_UnicodeEncodeError’                    *note UnicodeEncodeError: 61d.
                                              
                                                                                    
‘PyExc_UnicodeError’                          *note UnicodeError: 123a.
                                              
                                                                                    
‘PyExc_UnicodeTranslateError’                 *note UnicodeTranslateError: 217b.
                                              
                                                                                    
‘PyExc_ValueError’                            *note ValueError: 1e7.
                                              
                                                                                    
‘PyExc_ZeroDivisionError’                     *note ZeroDivisionError: 8e9.
                                              

在 3.3 版被加入: ‘PyExc_BlockingIOError’, ‘PyExc_BrokenPipeError’,
‘PyExc_ChildProcessError’, ‘PyExc_ConnectionError’,
‘PyExc_ConnectionAbortedError’, ‘PyExc_ConnectionRefusedError’,
‘PyExc_ConnectionResetError’, ‘PyExc_FileExistsError’,
‘PyExc_FileNotFoundError’, ‘PyExc_InterruptedError’,
‘PyExc_IsADirectoryError’, ‘PyExc_NotADirectoryError’,
‘PyExc_PermissionError’, ‘PyExc_ProcessLookupError’ 和
‘PyExc_TimeoutError’ 是在 PEP 3151(6) 被引入。

在 3.5 版被加入: ‘PyExc_StopAsyncIteration’ 和 ‘PyExc_RecursionError’。

在 3.6 版被加入: ‘PyExc_ModuleNotFoundError’。

These are compatibility aliases to ‘PyExc_OSError’:

C 名稱                                    註解
                                          
---------------------------------------------------------
                                          
‘PyExc_EnvironmentError’

‘PyExc_IOError’

‘PyExc_WindowsError’                      (7)
                                          

在 3.3 版的變更: These aliases used to be separate exception types.

註解：

   ---------- Footnotes ----------

   (1) This is a base class for other standard exceptions.

   (2) This is a base class for other standard exceptions.

   (3) This is a base class for other standard exceptions.

   (4) This is a base class for other standard exceptions.

   (5) This is a base class for other standard exceptions.

   (6) https://peps.python.org/pep-3151/

   (7) Only defined on Windows; protect code that uses this by testing
that the preprocessor macro ‘MS_WINDOWS’ is defined.


File: python.info,  Node: Standard Warning Categories,  Prev: Standard Exceptions,  Up: 例外處理

7.5.11 Standard Warning Categories
----------------------------------

All standard Python warning categories are available as global variables
whose names are ‘PyExc_’ followed by the Python exception name.  These
have the type *note PyObject: 311.*; they are all class objects.  For
completeness, here are all the variables:

C 名稱                                         Python 名稱                           註解
                                                                                     
----------------------------------------------------------------------------------------------------
                                                                                     
‘PyExc_Warning’                                *note Warning: 2191.                  (1)
                                                                                     
                                                                                     
‘PyExc_BytesWarning’                           *note BytesWarning: bca.
                                               
                                                                                     
‘PyExc_DeprecationWarning’                     *note DeprecationWarning: 18b.
                                               
                                                                                     
‘PyExc_FutureWarning’                          *note FutureWarning: 357.
                                               
                                                                                     
‘PyExc_ImportWarning’                          *note ImportWarning: 4a2.
                                               
                                                                                     
‘PyExc_PendingDeprecationWarning’              *note PendingDeprecationWarning: 86d.
                                               
                                                                                     
‘PyExc_ResourceWarning’                        *note ResourceWarning: 229.
                                               
                                                                                     
‘PyExc_RuntimeWarning’                         *note RuntimeWarning: 1a3.
                                               
                                                                                     
‘PyExc_SyntaxWarning’                          *note SyntaxWarning: 40c.
                                               
                                                                                     
‘PyExc_UnicodeWarning’                         *note UnicodeWarning: 1391.
                                               
                                                                                     
‘PyExc_UserWarning’                            *note UserWarning: 2192.
                                               

在 3.2 版被加入: ‘PyExc_ResourceWarning’.

註解：

   ---------- Footnotes ----------

   (1) This is a base class for other standard warning categories.


File: python.info,  Node: 工具,  Next: 抽象物件層 Abstract Objects Layer,  Prev: 例外處理,  Up: Python/C API 參考手冊

7.6 工具
========

本章中的函式可用來執行各種工具任務，包括幫助 C 程式碼提升跨平臺可攜性
(portable)、在 C 中使用 Python module（模組）、以及剖析函式引數並基於 C
中的值來構建 Python 中的值等。

* Menu:

* 作業系統工具::
* 系統函式::
* 行程控制::
* 引入模組: 引入模組<2>.
* 資料 marshal 的支援::
* 剖析引數與建置數值::
* 字串轉換與格式化::
* PyHash API::
* Reflection::
* 編解碼器註冊表和支援函式::
* PyTime C API::
* 對 Perf Map 的支援::


File: python.info,  Node: 作業系統工具,  Next: 系統函式,  Up: 工具

7.6.1 作業系統工具
------------------

 -- C 函式: *note PyObject: 311. *PyOS_FSPath (PyObject *path)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.6 版本
     開始.'  Return the file system representation for 'path'.  If the
     object is a *note str: 3f2. or *note bytes: 1a5. object, then a new
     *note strong reference: 2ee. is returned.  If the object implements
     the *note os.PathLike: bf8. interface, then *note __fspath__():
     bf9. is returned as long as it is a *note str: 3f2. or *note bytes:
     1a5. object.  Otherwise *note TypeError: 4dd. is raised and ‘NULL’
     is returned.

     在 3.6 版被加入.

 -- C 函式: int Py_FdIsInteractive (FILE *fp, const char *filename)

     Return true (nonzero) if the standard I/O file 'fp' with name
     'filename' is deemed interactive.  This is the case for files for
     which ‘isatty(fileno(fp))’ is true.  If the *note
     PyConfig.interactive: 398. is non-zero, this function also returns
     true if the 'filename' pointer is ‘NULL’ or if the name is equal to
     one of the strings ‘'<stdin>'’ or ‘'???'’.

     This function must not be called before Python is initialized.

 -- C 函式: void PyOS_BeforeFork ()
     ' 為 *note 穩定 ABI 的一部分: 4f9. on platforms with fork() 自 3.7
     版本開始.'  Function to prepare some internal state before a
     process fork.  This should be called before calling ‘fork()’ or any
     similar function that clones the current process.  Only available
     on systems where ‘fork()’ is defined.

          警告: The C ‘fork()’ call should only be made from the *note
          "main" thread: 4919. (of the *note "main" interpreter: 52d.).
          The same is true for ‘PyOS_BeforeFork()’.

     在 3.7 版被加入.

 -- C 函式: void PyOS_AfterFork_Parent ()
     ' 為 *note 穩定 ABI 的一部分: 4f9. on platforms with fork() 自 3.7
     版本開始.'  Function to update some internal state after a process
     fork.  This should be called from the parent process after calling
     ‘fork()’ or any similar function that clones the current process,
     regardless of whether process cloning was successful.  Only
     available on systems where ‘fork()’ is defined.

          警告: The C ‘fork()’ call should only be made from the *note
          "main" thread: 4919. (of the *note "main" interpreter: 52d.).
          The same is true for ‘PyOS_AfterFork_Parent()’.

     在 3.7 版被加入.

 -- C 函式: void PyOS_AfterFork_Child ()
     ' 為 *note 穩定 ABI 的一部分: 4f9. on platforms with fork() 自 3.7
     版本開始.'  Function to update internal interpreter state after a
     process fork.  This must be called from the child process after
     calling ‘fork()’, or any similar function that clones the current
     process, if there is any chance the process will call back into the
     Python interpreter.  Only available on systems where ‘fork()’ is
     defined.

          警告: The C ‘fork()’ call should only be made from the *note
          "main" thread: 4919. (of the *note "main" interpreter: 52d.).
          The same is true for ‘PyOS_AfterFork_Child()’.

     在 3.7 版被加入.

     也參考
     ......

     *note os.register_at_fork(): 2d1. allows registering custom Python
     functions to be called by *note PyOS_BeforeFork(): b66, *note
     PyOS_AfterFork_Parent(): b67. and *note PyOS_AfterFork_Child():
     3c3.

 -- C 函式: void PyOS_AfterFork ()
     ' 為 *note 穩定 ABI 的一部分: 4f9. on platforms with fork().'
     Function to update some internal state after a process fork; this
     should be called in the new process if the Python interpreter will
     continue to be used.  If a new executable is loaded into the new
     process, this function does not need to be called.

     在 3.7 版之後被棄用: This function is superseded by *note
     PyOS_AfterFork_Child(): 3c3.

 -- C 函式: int PyOS_CheckStack ()
     ' 為 *note 穩定 ABI 的一部分: 4f9. on platforms with USE_STACKCHECK
     自 3.7 版本開始.'

     Return true when the interpreter runs out of stack space.  This is
     a reliable check, but is only available when ‘USE_STACKCHECK’ is
     defined (currently on certain versions of Windows using the
     Microsoft Visual C++ compiler).  ‘USE_STACKCHECK’ will be defined
     automatically; you should never change the definition in your own
     code.

 -- C 型別: typedef void (*PyOS_sighandler_t)(int)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

 -- C 函式: *note PyOS_sighandler_t: 4830. PyOS_getsig (int i)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the current signal
     handler for signal 'i'.  This is a thin wrapper around either
     ‘sigaction()’ or ‘signal()’.  Do not call those functions directly!

 -- C 函式: *note PyOS_sighandler_t: 4830. PyOS_setsig (int i,
          PyOS_sighandler_t h)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Set the signal handler for
     signal 'i' to be 'h'; return the old signal handler.  This is a
     thin wrapper around either ‘sigaction()’ or ‘signal()’.  Do not
     call those functions directly!

 -- C 函式: wchar_t *Py_DecodeLocale (const char *arg, size_t *size)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'
          警告: This function should not be called directly: use the
          *note PyConfig: 371. API with the *note
          PyConfig_SetBytesString(): 958. function which ensures that
          *note Python is preinitialized: 3b60.

          This function must not be called before *note Python is
          preinitialized: 3b60. and so that the LC_CTYPE locale is
          properly configured: see the *note Py_PreInitialize(): 3b6.
          function.

     Decode a byte string from the *note filesystem encoding and error
     handler: 4e0.  If the error handler is *note surrogateescape error
     handler: 22c2, undecodable bytes are decoded as characters in range
     U+DC80..U+DCFF; and if a byte sequence can be decoded as a
     surrogate character, the bytes are escaped using the
     surrogateescape error handler instead of decoding them.

     Return a pointer to a newly allocated wide character string, use
     *note PyMem_RawFree(): 326. to free the memory.  If size is not
     ‘NULL’, write the number of wide characters excluding the null
     character into ‘*size’

     Return ‘NULL’ on decoding error or memory allocation error.  If
     'size' is not ‘NULL’, ‘*size’ is set to ‘(size_t)-1’ on memory
     error or set to ‘(size_t)-2’ on decoding error.

     The *note filesystem encoding and error handler: 4e0. are selected
     by *note PyConfig_Read(): 734.: see *note filesystem_encoding: 3b3.
     and *note filesystem_errors: 3b4. members of *note PyConfig: 371.

     Decoding errors should never happen, unless there is a bug in the C
     library.

     Use the *note Py_EncodeLocale(): b6f. function to encode the
     character string back to a byte string.

     也參考
     ......

     The *note PyUnicode_DecodeFSDefaultAndSize(): 4896. and *note
     PyUnicode_DecodeLocaleAndSize(): b70. functions.

     在 3.5 版被加入.

     在 3.7 版的變更: The function now uses the UTF-8 encoding in the
     *note Python UTF-8 Mode: 5fc.

     在 3.8 版的變更: The function now uses the UTF-8 encoding on
     Windows if *note PyPreConfig.legacy_windows_fs_encoding: 3b1. is
     zero;

 -- C 函式: char *Py_EncodeLocale (const wchar_t *text, size_t
          *error_pos)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Encode a wide
     character string to the *note filesystem encoding and error
     handler: 4e0.  If the error handler is *note surrogateescape error
     handler: 22c2, surrogate characters in the range U+DC80..U+DCFF are
     converted to bytes 0x80..0xFF.

     Return a pointer to a newly allocated byte string, use *note
     PyMem_Free(): 13b0. to free the memory.  Return ‘NULL’ on encoding
     error or memory allocation error.

     If error_pos is not ‘NULL’, ‘*error_pos’ is set to ‘(size_t)-1’ on
     success, or set to the index of the invalid character on encoding
     error.

     The *note filesystem encoding and error handler: 4e0. are selected
     by *note PyConfig_Read(): 734.: see *note filesystem_encoding: 3b3.
     and *note filesystem_errors: 3b4. members of *note PyConfig: 371.

     Use the *note Py_DecodeLocale(): b6e. function to decode the bytes
     string back to a wide character string.

          警告: This function must not be called before *note Python is
          preinitialized: 3b60. and so that the LC_CTYPE locale is
          properly configured: see the *note Py_PreInitialize(): 3b6.
          function.

     也參考
     ......

     The *note PyUnicode_EncodeFSDefault(): 1957. and *note
     PyUnicode_EncodeLocale(): b71. functions.

     在 3.5 版被加入.

     在 3.7 版的變更: The function now uses the UTF-8 encoding in the
     *note Python UTF-8 Mode: 5fc.

     在 3.8 版的變更: The function now uses the UTF-8 encoding on
     Windows if *note PyPreConfig.legacy_windows_fs_encoding: 3b1. is
     zero.


File: python.info,  Node: 系統函式,  Next: 行程控制,  Prev: 作業系統工具,  Up: 工具

7.6.2 系統函式
--------------

These are utility functions that make functionality from the *note sys:
c3. module accessible to C code.  They all work with the current
interpreter thread's *note sys: c3. module's dict, which is contained in
the internal thread state structure.

 -- C 函式: *note PyObject: 311. *PySys_GetObject (const char *name)
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the
     object 'name' from the *note sys: c3. module or ‘NULL’ if it does
     not exist, without setting an exception.

 -- C 函式: int PySys_SetObject (const char *name, PyObject *v)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Set 'name' in the *note sys:
     c3. module to 'v' unless 'v' is ‘NULL’, in which case 'name' is
     deleted from the sys module.  Returns ‘0’ on success, ‘-1’ on
     error.

 -- C 函式: void PySys_ResetWarnOptions ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Reset *note sys.warnoptions:
     37b. to an empty list.  This function may be called prior to *note
     Py_Initialize(): 851.

     Deprecated since version 3.13, will be removed in version 3.15:
     Clear *note sys.warnoptions: 37b. and ‘warnings.filters’ instead.

 -- C 函式: void PySys_WriteStdout (const char *format, ...)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Write the output string
     described by 'format' to *note sys.stdout: a79.  No exceptions are
     raised, even if truncation occurs (see below).

     'format' should limit the total size of the formatted output string
     to 1000 bytes or less - after 1000 bytes, the output string is
     truncated.  In particular, this means that no unrestricted "%s"
     formats should occur; these should be limited using "%.<N>s" where
     <N> is a decimal number calculated so that <N> plus the maximum
     size of other formatted text does not exceed 1000 bytes.  Also
     watch out for "%f", which can print hundreds of digits for very
     large numbers.

     If a problem occurs, or *note sys.stdout: a79. is unset, the
     formatted message is written to the real (C level) 'stdout'.

 -- C 函式: void PySys_WriteStderr (const char *format, ...)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  As *note PySys_WriteStdout():
     4869, but write to *note sys.stderr: 8dd. or 'stderr' instead.

 -- C 函式: void PySys_FormatStdout (const char *format, ...)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Function similar to
     PySys_WriteStdout() but format the message using *note
     PyUnicode_FromFormatV(): 51a. and don't truncate the message to an
     arbitrary length.

     在 3.2 版被加入.

 -- C 函式: void PySys_FormatStderr (const char *format, ...)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  As *note PySys_FormatStdout():
     4865, but write to *note sys.stderr: 8dd. or 'stderr' instead.

     在 3.2 版被加入.

 -- C 函式: *note PyObject: 311. *PySys_GetXOptions ()
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本
     開始.'  Return the current dictionary of *note -X: 15a. options,
     similarly to *note sys._xoptions: 1c41.  On error, ‘NULL’ is
     returned and an exception is set.

     在 3.2 版被加入.

 -- C 函式: int PySys_Audit (const char *event, const char *format, ...)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Raise an
     auditing event with any active hooks.  Return zero for success and
     non-zero with an exception set on failure.

     The 'event' string argument must not be 'NULL'.

     If any hooks have been added, 'format' and other arguments will be
     used to construct a tuple to pass.  Apart from ‘N’, the same format
     characters as used in *note Py_BuildValue(): 84c. are available.
     If the built value is not a tuple, it will be added into a
     single-element tuple.

     The ‘N’ format option must not be used.  It consumes a reference,
     but since there is no way to know whether arguments to this
     function will be consumed, using it may cause reference leaks.

     Note that ‘#’ format characters should always be treated as *note
     Py_ssize_t: a03, regardless of whether ‘PY_SSIZE_T_CLEAN’ was
     defined.

     *note sys.audit(): 1873. performs the same function from Python
     code.

     See also *note PySys_AuditTuple(): 320.

     在 3.8 版被加入.

     在 3.8.2 版的變更: Require *note Py_ssize_t: a03. for ‘#’ format
     characters.  Previously, an unavoidable deprecation warning was
     raised.

 -- C 函式: int PySys_AuditTuple (const char *event, PyObject *args)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Similar to
     *note PySys_Audit(): 321, but pass arguments as a Python object.
     'args' must be a *note tuple: 322.  To pass no arguments, 'args'
     can be 'NULL'.

     在 3.13 版被加入.

 -- C 函式: int PySys_AddAuditHook (Py_AuditHookFunction hook, void
          *userData)

     Append the callable 'hook' to the list of active auditing hooks.
     Return zero on success and non-zero on failure.  If the runtime has
     been initialized, also set an error on failure.  Hooks added
     through this API are called for all interpreters created by the
     runtime.

     The 'userData' pointer is passed into the hook function.  Since
     hook functions may be called from different runtimes, this pointer
     should not refer directly to Python state.

     This function is safe to call before *note Py_Initialize(): 851.
     When called after runtime initialization, existing audit hooks are
     notified and may silently abort the operation by raising an error
     subclassed from *note Exception: 97d. (other errors will not be
     silenced).

     The hook function is always called with the GIL held by the Python
     interpreter that raised the event.

     See PEP 578(1) for a detailed description of auditing.  Functions
     in the runtime and standard library that raise events are listed in
     the *note audit events table: 1773.  Details are in each function's
     documentation.

     If the interpreter is initialized, this function raises an auditing
     event ‘sys.addaudithook’ with no arguments.  If any existing hooks
     raise an exception derived from *note Exception: 97d, the new hook
     will not be added and the exception is cleared.  As a result,
     callers cannot assume that their hook has been added unless they
     control all existing hooks.

      -- C 型別: typedef int (*Py_AuditHookFunction)(const char *event,
               *note PyObject: 311. *args, void *userData)

          The type of the hook function.  'event' is the C string event
          argument passed to *note PySys_Audit(): 321. or *note
          PySys_AuditTuple(): 320.  'args' is guaranteed to be a *note
          PyTupleObject: 491d.  'userData' is the argument passed to
          PySys_AddAuditHook().

     在 3.8 版被加入.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0578/


File: python.info,  Node: 行程控制,  Next: 引入模組<2>,  Prev: 系統函式,  Up: 工具

7.6.3 行程控制
--------------

 -- C 函式: void Py_FatalError (const char *message)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     Print a fatal error message and kill the process.  No cleanup is
     performed.  This function should only be invoked when a condition
     is detected that would make it dangerous to continue using the
     Python interpreter; e.g., when the object administration appears to
     be corrupted.  On Unix, the standard C library function ‘abort()’
     is called which will attempt to produce a ‘core’ file.

     The ‘Py_FatalError()’ function is replaced with a macro which logs
     automatically the name of the current function, unless the
     ‘Py_LIMITED_API’ macro is defined.

     在 3.9 版的變更: Log the function name automatically.

 -- C 函式: void Py_Exit (int status)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     Exit the current process.  This calls *note Py_FinalizeEx(): cbc.
     and then calls the standard C library function ‘exit(status)’.  If
     *note Py_FinalizeEx(): cbc. indicates an error, the exit status is
     set to 120.

     在 3.6 版的變更: Errors from finalization no longer ignored.

 -- C 函式: int Py_AtExit (void (*func)())
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     Register a cleanup function to be called by *note Py_FinalizeEx():
     cbc.  The cleanup function will be called with no arguments and
     should return no value.  At most 32 cleanup functions can be
     registered.  When the registration is successful, *note
     Py_AtExit(): 48b2. returns ‘0’; on failure, it returns ‘-1’.  The
     cleanup function registered last is called first.  Each cleanup
     function will be called at most once.  Since Python's internal
     finalization will have completed before the cleanup function, no
     Python APIs should be called by 'func'.


File: python.info,  Node: 引入模組<2>,  Next: 資料 marshal 的支援,  Prev: 行程控制,  Up: 工具

7.6.4 引入模組
--------------

 -- C 函式: *note PyObject: 311. *PyImport_ImportModule (const char
          *name)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

     This is a wrapper around *note PyImport_Import(): 136a. which takes
     a const char* as an argument instead of a *note PyObject: 311.*.

 -- C 函式: *note PyObject: 311. *PyImport_ImportModuleNoBlock (const
          char *name)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  This
     function is a deprecated alias of *note PyImport_ImportModule():
     389.

     在 3.3 版的變更: This function used to fail immediately when the
     import lock was held by another thread.  In Python 3.3 though, the
     locking scheme switched to per-module locks for most purposes, so
     this function's special behaviour isn't needed anymore.

     Deprecated since version 3.13, will be removed in version 3.15: Use
     *note PyImport_ImportModule(): 389. instead.

 -- C 函式: *note PyObject: 311. *PyImport_ImportModuleEx (const char
          *name, PyObject *globals, PyObject *locals, PyObject
          *fromlist)
     '回傳值：新的參照。'

     Import a module.  This is best described by referring to the
     built-in Python function *note __import__(): 879.

     The return value is a new reference to the imported module or
     top-level package, or ‘NULL’ with an exception set on failure.
     Like for *note __import__(): 879, the return value when a submodule
     of a package was requested is normally the top-level package,
     unless a non-empty 'fromlist' was given.

     Failing imports remove incomplete module objects, like with *note
     PyImport_ImportModule(): 389.

 -- C 函式: *note PyObject: 311. *PyImport_ImportModuleLevelObject
          (PyObject *name, PyObject *globals, PyObject *locals, PyObject
          *fromlist, int level)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本
     開始.'  Import a module.  This is best described by referring to
     the built-in Python function *note __import__(): 879, as the
     standard *note __import__(): 879. function calls this function
     directly.

     The return value is a new reference to the imported module or
     top-level package, or ‘NULL’ with an exception set on failure.
     Like for *note __import__(): 879, the return value when a submodule
     of a package was requested is normally the top-level package,
     unless a non-empty 'fromlist' was given.

     在 3.3 版被加入.

 -- C 函式: *note PyObject: 311. *PyImport_ImportModuleLevel (const char
          *name, PyObject *globals, PyObject *locals, PyObject
          *fromlist, int level)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Similar to
     *note PyImport_ImportModuleLevelObject(): 47e9, but the name is a
     UTF-8 encoded string instead of a Unicode object.

     在 3.3 版的變更: Negative values for 'level' are no longer
     accepted.

 -- C 函式: *note PyObject: 311. *PyImport_Import (PyObject *name)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  This is a
     higher-level interface that calls the current "import hook
     function" (with an explicit 'level' of 0, meaning absolute import).
     It invokes the *note __import__(): 879. function from the
     ‘__builtins__’ of the current globals.  This means that the import
     is done using whatever import hooks are installed in the current
     environment.

     This function always uses absolute imports.

 -- C 函式: *note PyObject: 311. *PyImport_ReloadModule (PyObject *m)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Reload a
     module.  Return a new reference to the reloaded module, or ‘NULL’
     with an exception set on failure (the module still exists in this
     case).

 -- C 函式: *note PyObject: 311. *PyImport_AddModuleRef (const char
          *name)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本
     開始.'  Return the module object corresponding to a module name.

     The 'name' argument may be of the form ‘package.module’.  First
     check the modules dictionary if there's one there, and if not,
     create a new one and insert it in the modules dictionary.

     Return a *note strong reference: 2ee. to the module on success.
     Return ‘NULL’ with an exception set on failure.

     The module name 'name' is decoded from UTF-8.

     This function does not load or import the module; if the module
     wasn't already loaded, you will get an empty module object.  Use
     *note PyImport_ImportModule(): 389. or one of its variants to
     import a module.  Package structures implied by a dotted name for
     'name' are not created if not already present.

     在 3.13 版被加入.

 -- C 函式: *note PyObject: 311. *PyImport_AddModuleObject (PyObject
          *name)
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本
     開始.'  Similar to *note PyImport_AddModuleRef(): 2ec, but return a
     *note borrowed reference: 2ef. and 'name' is a Python *note str:
     3f2. object.

     在 3.3 版被加入.

 -- C 函式: *note PyObject: 311. *PyImport_AddModule (const char *name)
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Similar to
     *note PyImport_AddModuleRef(): 2ec, but return a *note borrowed
     reference: 2ef.

 -- C 函式: *note PyObject: 311. *PyImport_ExecCodeModule (const char
          *name, PyObject *co)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

     Given a module name (possibly of the form ‘package.module’) and a
     code object read from a Python bytecode file or obtained from the
     built-in function *note compile(): 178, load the module.  Return a
     new reference to the module object, or ‘NULL’ with an exception set
     if an error occurred.  'name' is removed from *note sys.modules:
     186e. in error cases, even if 'name' was already in *note
     sys.modules: 186e. on entry to *note PyImport_ExecCodeModule():
     47e1.  Leaving incompletely initialized modules in *note
     sys.modules: 186e. is dangerous, as imports of such modules have no
     way to know that the module object is an unknown (and probably
     damaged with respect to the module author's intents) state.

     The module's *note __spec__: 1ed6. and *note __loader__: fc1. will
     be set, if not set already, with the appropriate values.  The
     spec's loader will be set to the module's ‘__loader__’ (if set) and
     to an instance of *note SourceFileLoader: 1015. otherwise.

     The module's *note __file__: 1e02. attribute will be set to the
     code object's *note co_filename: 12fa.  If applicable, *note
     __cached__: 114d. will also be set.

     This function will reload the module if it was already imported.
     See *note PyImport_ReloadModule(): 47ea. for the intended way to
     reload a module.

     If 'name' points to a dotted name of the form ‘package.module’, any
     package structures not already created will still not be created.

     See also *note PyImport_ExecCodeModuleEx(): 47e2. and *note
     PyImport_ExecCodeModuleWithPathnames(): 47e4.

     在 3.12 版的變更: The setting of *note __cached__: 114d. and *note
     __loader__: fc1. is deprecated.  See *note ModuleSpec: 1d5a. for
     alternatives.

 -- C 函式: *note PyObject: 311. *PyImport_ExecCodeModuleEx (const char
          *name, PyObject *co, const char *pathname)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Like *note
     PyImport_ExecCodeModule(): 47e1, but the *note __file__: 1e02.
     attribute of the module object is set to 'pathname' if it is
     non-‘NULL’.

     也請見 *note PyImport_ExecCodeModuleWithPathnames(): 47e4.。

 -- C 函式: *note PyObject: 311. *PyImport_ExecCodeModuleObject
          (PyObject *name, PyObject *co, PyObject *pathname, PyObject
          *cpathname)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本
     開始.'  Like *note PyImport_ExecCodeModuleEx(): 47e2, but the *note
     __cached__: 114d. attribute of the module object is set to
     'cpathname' if it is non-‘NULL’.  Of the three functions, this is
     the preferred one to use.

     在 3.3 版被加入.

     在 3.12 版的變更: Setting *note __cached__: 114d. is deprecated.
     See *note ModuleSpec: 1d5a. for alternatives.

 -- C 函式: *note PyObject: 311. *PyImport_ExecCodeModuleWithPathnames
          (const char *name, PyObject *co, const char *pathname, const
          char *cpathname)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Like *note
     PyImport_ExecCodeModuleObject(): 47e3, but 'name', 'pathname' and
     'cpathname' are UTF-8 encoded strings.  Attempts are also made to
     figure out what the value for 'pathname' should be from 'cpathname'
     if the former is set to ‘NULL’.

     在 3.2 版被加入.

     在 3.3 版的變更: Uses ‘imp.source_from_cache()’ in calculating the
     source path if only the bytecode path is provided.

     在 3.12 版的變更: 不再使用已被移除的 ‘imp’ 模組。

 -- C 函式: long PyImport_GetMagicNumber ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the magic number for
     Python bytecode files (a.k.a.  ‘.pyc’ file).  The magic number
     should be present in the first four bytes of the bytecode file, in
     little-endian byte order.  Returns ‘-1’ on error.

     在 3.3 版的變更: 當失敗時回傳 ‘-1’。

 -- C 函式: const char *PyImport_GetMagicTag ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the magic tag string
     for PEP 3147(1) format Python bytecode file names.  Keep in mind
     that the value at ‘sys.implementation.cache_tag’ is authoritative
     and should be used instead of this function.

     在 3.2 版被加入.

 -- C 函式: *note PyObject: 311. *PyImport_GetModuleDict ()
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the
     dictionary used for the module administration (a.k.a.
     ‘sys.modules’).  Note that this is a per-interpreter variable.

 -- C 函式: *note PyObject: 311. *PyImport_GetModule (PyObject *name)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.8 版本
     開始.'  Return the already imported module with the given name.  If
     the module has not been imported yet then returns ‘NULL’ but does
     not set an error.  Returns ‘NULL’ and sets an error if the lookup
     failed.

     在 3.7 版被加入.

 -- C 函式: *note PyObject: 311. *PyImport_GetImporter (PyObject *path)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     finder object for a *note sys.path: 37f./‘pkg.__path__’ item
     'path', possibly by fetching it from the *note
     sys.path_importer_cache: 588. dict.  If it wasn't yet cached,
     traverse *note sys.path_hooks: fc7. until a hook is found that can
     handle the path item.  Return ‘None’ if no hook could; this tells
     our caller that the *note path based finder: 1ecf. could not find a
     finder for this path item.  Cache the result in *note
     sys.path_importer_cache: 588.  Return a new reference to the finder
     object.

 -- C 函式: int PyImport_ImportFrozenModuleObject (PyObject *name)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Load a frozen
     module named 'name'.  Return ‘1’ for success, ‘0’ if the module is
     not found, and ‘-1’ with an exception set if the initialization
     failed.  To access the imported module on a successful load, use
     *note PyImport_ImportModule(): 389.  (Note the misnomer -- this
     function would reload the module if it was already imported.)

     在 3.3 版被加入.

     在 3.4 版的變更: The ‘__file__’ attribute is no longer set on the
     module.

 -- C 函式: int PyImport_ImportFrozenModule (const char *name)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Similar to *note
     PyImport_ImportFrozenModuleObject(): 47e8, but the name is a UTF-8
     encoded string instead of a Unicode object.

 -- C 結構: struct _frozen

     This is the structure type definition for frozen module
     descriptors, as generated by the ‘freeze’ utility (see
     ‘Tools/freeze/’ in the Python source distribution).  Its
     definition, found in ‘Include/import.h’, is:

          struct _frozen {
              const char *name;
              const unsigned char *code;
              int size;
              bool is_package;
          };

     在 3.11 版的變更: The new ‘is_package’ field indicates whether the
     module is a package or not.  This replaces setting the ‘size’ field
     to a negative value.

 -- C 變數: const struct *note _frozen: 719. *PyImport_FrozenModules

     This pointer is initialized to point to an array of *note _frozen:
     719. records, terminated by one whose members are all ‘NULL’ or
     zero.  When a frozen module is imported, it is searched in this
     table.  Third-party code could play tricks with this to provide a
     dynamically created collection of frozen modules.

 -- C 函式: int PyImport_AppendInittab (const char *name, PyObject
          *(*initfunc)(void))
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Add a single module to the
     existing table of built-in modules.  This is a convenience wrapper
     around *note PyImport_ExtendInittab(): 16a7, returning ‘-1’ if the
     table could not be extended.  The new module can be imported by the
     name 'name', and uses the function 'initfunc' as the initialization
     function called on the first attempted import.  This should be
     called before *note Py_Initialize(): 851.

 -- C 結構: struct _inittab

     Structure describing a single entry in the list of built-in
     modules.  Programs which embed Python may use an array of these
     structures in conjunction with *note PyImport_ExtendInittab():
     16a7. to provide additional built-in modules.  The structure
     consists of two members:

      -- C 成員函數: const char *name

          The module name, as an ASCII encoded string.

      -- C 成員函數: *note PyObject: 311. *(*initfunc)(void)

          Initialization function for a module built into the
          interpreter.

 -- C 函式: int PyImport_ExtendInittab (struct _inittab *newtab)

     Add a collection of modules to the table of built-in modules.  The
     'newtab' array must end with a sentinel entry which contains ‘NULL’
     for the *note name: 4924. field; failure to provide the sentinel
     value can result in a memory fault.  Returns ‘0’ on success or ‘-1’
     if insufficient memory could be allocated to extend the internal
     table.  In the event of failure, no modules are added to the
     internal table.  This must be called before *note Py_Initialize():
     851.

     If Python is initialized multiple times, *note
     PyImport_AppendInittab(): 16a6. or *note PyImport_ExtendInittab():
     16a7. must be called before each Python initialization.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3147/


File: python.info,  Node: 資料 marshal 的支援,  Next: 剖析引數與建置數值,  Prev: 引入模組<2>,  Up: 工具

7.6.5 資料 marshal 的支援
-------------------------

These routines allow C code to work with serialized objects using the
same data format as the *note marshal: 80. module.  There are functions
to write data into the serialization format, and additional functions
that can be used to read the data back.  Files used to store marshalled
data must be opened in binary mode.

Numeric values are stored with the least significant byte first.

The module supports two versions of the data format: version 0 is the
historical version, version 1 shares interned strings in the file, and
upon unmarshalling.  Version 2 uses a binary format for floating-point
numbers.  ‘Py_MARSHAL_VERSION’ indicates the current file format
(currently 2).

 -- C 函式: void PyMarshal_WriteLongToFile (long value, FILE *file, int
          version)

     Marshal a long integer, 'value', to 'file'.  This will only write
     the least-significant 32 bits of 'value'; regardless of the size of
     the native long type.  'version' indicates the file format.

     This function can fail, in which case it sets the error indicator.
     Use *note PyErr_Occurred(): 17f4. to check for that.

 -- C 函式: void PyMarshal_WriteObjectToFile (PyObject *value, FILE
          *file, int version)

     Marshal a Python object, 'value', to 'file'.  'version' indicates
     the file format.

     This function can fail, in which case it sets the error indicator.
     Use *note PyErr_Occurred(): 17f4. to check for that.

 -- C 函式: *note PyObject: 311. *PyMarshal_WriteObjectToString
          (PyObject *value, int version)
     '回傳值：新的參照。' Return a bytes object containing the
     marshalled representation of 'value'.  'version' indicates the file
     format.

The following functions allow marshalled values to be read back in.

 -- C 函式: long PyMarshal_ReadLongFromFile (FILE *file)

     Return a C long from the data stream in a FILE* opened for reading.
     Only a 32-bit value can be read in using this function, regardless
     of the native size of long.

     On error, sets the appropriate exception (*note EOFError: 126c.)
     and returns ‘-1’.

 -- C 函式: int PyMarshal_ReadShortFromFile (FILE *file)

     Return a C short from the data stream in a FILE* opened for
     reading.  Only a 16-bit value can be read in using this function,
     regardless of the native size of short.

     On error, sets the appropriate exception (*note EOFError: 126c.)
     and returns ‘-1’.

 -- C 函式: *note PyObject: 311. *PyMarshal_ReadObjectFromFile (FILE
          *file)
     '回傳值：新的參照。' Return a Python object from the data stream in
     a FILE* opened for reading.

     On error, sets the appropriate exception (*note EOFError: 126c,
     *note ValueError: 1e7. or *note TypeError: 4dd.) and returns
     ‘NULL’.

 -- C 函式: *note PyObject: 311. *PyMarshal_ReadLastObjectFromFile (FILE
          *file)
     '回傳值：新的參照。' Return a Python object from the data stream in
     a FILE* opened for reading.  Unlike *note
     PyMarshal_ReadObjectFromFile(): 492b, this function assumes that no
     further objects will be read from the file, allowing it to
     aggressively load file data into memory so that the
     de-serialization can operate from data in memory rather than
     reading a byte at a time from the file.  Only use these variant if
     you are certain that you won't be reading anything else from the
     file.

     On error, sets the appropriate exception (*note EOFError: 126c,
     *note ValueError: 1e7. or *note TypeError: 4dd.) and returns
     ‘NULL’.

 -- C 函式: *note PyObject: 311. *PyMarshal_ReadObjectFromString (const
          char *data, Py_ssize_t len)
     '回傳值：新的參照。' Return a Python object from the data stream in
     a byte buffer containing 'len' bytes pointed to by 'data'.

     On error, sets the appropriate exception (*note EOFError: 126c,
     *note ValueError: 1e7. or *note TypeError: 4dd.) and returns
     ‘NULL’.


File: python.info,  Node: 剖析引數與建置數值,  Next: 字串轉換與格式化,  Prev: 資料 marshal 的支援,  Up: 工具

7.6.6 剖析引數與建置數值
------------------------

These functions are useful when creating your own extensions functions
and methods.  Additional information and examples are available in *note
擴充和嵌入 Python 直譯器: 1ae1.

The first three of these functions described, *note PyArg_ParseTuple():
517, *note PyArg_ParseTupleAndKeywords(): 2e9, and *note PyArg_Parse():
18e9, all use 'format strings' which are used to tell the function about
the expected arguments.  The format strings use the same syntax for each
of these functions.

* Menu:

* Parsing arguments::
* Building values::


File: python.info,  Node: Parsing arguments,  Next: Building values,  Up: 剖析引數與建置數值

7.6.6.1 Parsing arguments
.........................

A format string consists of zero or more "format units."  A format unit
describes one Python object; it is usually a single character or a
parenthesized sequence of format units.  With a few exceptions, a format
unit that is not a parenthesized sequence normally corresponds to a
single address argument to these functions.  In the following
description, the quoted form is the format unit; the entry in (round)
parentheses is the Python object type that matches the format unit; and
the entry in [square] brackets is the type of the C variable(s) whose
address should be passed.

* Menu:

* Strings and buffers::
* 數字::
* 其他物件::
* API 函式::


File: python.info,  Node: Strings and buffers,  Next: 數字,  Up: Parsing arguments

7.6.6.2 Strings and buffers
...........................

     備註: On Python 3.12 and older, the macro ‘PY_SSIZE_T_CLEAN’ must
     be defined before including ‘Python.h’ to use all ‘#’ variants of
     formats (‘s#’, ‘y#’, etc.)  explained below.  This is not necessary
     on Python 3.13 and later.

These formats allow accessing an object as a contiguous chunk of memory.
You don't have to provide raw storage for the returned unicode or bytes
area.

Unless otherwise stated, buffers are not NUL-terminated.

There are three ways strings and buffers can be converted to C:

   * Formats such as ‘y*’ and ‘s*’ fill a *note Py_buffer: 6fc.
     structure.  This locks the underlying buffer so that the caller can
     subsequently use the buffer even inside a *note
     Py_BEGIN_ALLOW_THREADS: 46f3. block without the risk of mutable
     data being resized or destroyed.  As a result, 'you have to call'
     *note PyBuffer_Release(): 36a. after you have finished processing
     the data (or in any early abort case).

   * The ‘es’, ‘es#’, ‘et’ and ‘et#’ formats allocate the result buffer.
     'You have to call' *note PyMem_Free(): 13b0. after you have
     finished processing the data (or in any early abort case).

   * Other formats take a *note str: 3f2. or a read-only *note
     bytes-like object: cd4, such as *note bytes: 1a5, and provide a
     ‘const char *’ pointer to its buffer.  In this case the buffer is
     "borrowed": it is managed by the corresponding Python object, and
     shares the lifetime of this object.  You won't have to release any
     memory yourself.

     To ensure that the underlying buffer may be safely borrowed, the
     object's *note PyBufferProcs.bf_releasebuffer: 707. field must be
     ‘NULL’.  This disallows common mutable objects such as *note
     bytearray: 4e3, but also some read-only objects such as *note
     memoryview: 40f. of *note bytes: 1a5.

     Besides this ‘bf_releasebuffer’ requirement, there is no check to
     verify whether the input object is immutable (e.g.  whether it
     would honor a request for a writable buffer, or whether another
     thread can mutate the data).

‘s’ (*note str: 3f2.) [const char *]

     Convert a Unicode object to a C pointer to a character string.  A
     pointer to an existing string is stored in the character pointer
     variable whose address you pass.  The C string is NUL-terminated.
     The Python string must not contain embedded null code points; if it
     does, a *note ValueError: 1e7. exception is raised.  Unicode
     objects are converted to C strings using ‘'utf-8'’ encoding.  If
     this conversion fails, a *note UnicodeError: 123a. is raised.

          備註: This format does not accept *note bytes-like objects:
          cd4.  If you want to accept filesystem paths and convert them
          to C character strings, it is preferable to use the ‘O&’
          format with *note PyUnicode_FSConverter(): cc0. as
          'converter'.

     在 3.5 版的變更: Previously, *note TypeError: 4dd. was raised when
     embedded null code points were encountered in the Python string.

‘s*’（*note str: 3f2. 或 *note bytes-like object: cd4.）[Py_buffer]

     This format accepts Unicode objects as well as bytes-like objects.
     It fills a *note Py_buffer: 6fc. structure provided by the caller.
     In this case the resulting C string may contain embedded NUL bytes.
     Unicode objects are converted to C strings using ‘'utf-8'’
     encoding.

‘s#’ (*note str: 3f2, read-only *note bytes-like object: cd4.) [const char *, *note Py_ssize_t: a03.]

     Like ‘s*’, except that it provides a *note borrowed buffer: 4931.
     The result is stored into two C variables, the first one a pointer
     to a C string, the second one its length.  The string may contain
     embedded null bytes.  Unicode objects are converted to C strings
     using ‘'utf-8'’ encoding.

‘z’（*note str: 3f2. 或 ‘None’）[const char *]

     Like ‘s’, but the Python object may also be ‘None’, in which case
     the C pointer is set to ‘NULL’.

‘z*’（*note str: 3f2.、*note bytes-like object: cd4. 或 ‘None’）[Py_buffer]

     Like ‘s*’, but the Python object may also be ‘None’, in which case
     the ‘buf’ member of the *note Py_buffer: 6fc. structure is set to
     ‘NULL’.

‘z#’ (*note str: 3f2, read-only *note bytes-like object: cd4. or ‘None’) [const char *, *note Py_ssize_t: a03.]

     Like ‘s#’, but the Python object may also be ‘None’, in which case
     the C pointer is set to ‘NULL’.

‘y’（唯讀 *note bytes-like object: cd4.）[const char *]

     This format converts a bytes-like object to a C pointer to a *note
     borrowed: 4931. character string; it does not accept Unicode
     objects.  The bytes buffer must not contain embedded null bytes; if
     it does, a *note ValueError: 1e7. exception is raised.

     在 3.5 版的變更: Previously, *note TypeError: 4dd. was raised when
     embedded null bytes were encountered in the bytes buffer.

‘y*’ (*note bytes-like object: cd4.) [Py_buffer]

     This variant on ‘s*’ doesn't accept Unicode objects, only
     bytes-like objects.  'This is the recommended way to accept binary
     data.'

‘y#’ (read-only *note bytes-like object: cd4.) [const char *, *note Py_ssize_t: a03.]

     This variant on ‘s#’ doesn't accept Unicode objects, only
     bytes-like objects.

‘S’ (*note bytes: 1a5.) [PyBytesObject *]

     Requires that the Python object is a *note bytes: 1a5. object,
     without attempting any conversion.  Raises *note TypeError: 4dd. if
     the object is not a bytes object.  The C variable may also be
     declared as *note PyObject: 311.*.

‘Y’ (*note bytearray: 4e3.) [PyByteArrayObject *]

     Requires that the Python object is a *note bytearray: 4e3. object,
     without attempting any conversion.  Raises *note TypeError: 4dd. if
     the object is not a *note bytearray: 4e3. object.  The C variable
     may also be declared as *note PyObject: 311.*.

‘U’ (*note str: 3f2.) [PyObject *]

     Requires that the Python object is a Unicode object, without
     attempting any conversion.  Raises *note TypeError: 4dd. if the
     object is not a Unicode object.  The C variable may also be
     declared as *note PyObject: 311.*.

‘w*’ （可讀寫 *note bytes-like object: cd4.） [Py_buffer]

     This format accepts any object which implements the read-write
     buffer interface.  It fills a *note Py_buffer: 6fc. structure
     provided by the caller.  The buffer may contain embedded null
     bytes.  The caller have to call *note PyBuffer_Release(): 36a. when
     it is done with the buffer.

‘es’ (*note str: 3f2.) [const char *encoding, char **buffer]

     This variant on ‘s’ is used for encoding Unicode into a character
     buffer.  It only works for encoded data without embedded NUL bytes.

     This format requires two arguments.  The first is only used as
     input, and must be a const char* which points to the name of an
     encoding as a NUL-terminated string, or ‘NULL’, in which case
     ‘'utf-8'’ encoding is used.  An exception is raised if the named
     encoding is not known to Python.  The second argument must be a
     char**; the value of the pointer it references will be set to a
     buffer with the contents of the argument text.  The text will be
     encoded in the encoding specified by the first argument.

     *note PyArg_ParseTuple(): 517. will allocate a buffer of the needed
     size, copy the encoded data into this buffer and adjust '*buffer'
     to reference the newly allocated storage.  The caller is
     responsible for calling *note PyMem_Free(): 13b0. to free the
     allocated buffer after use.

‘et’ (*note str: 3f2, *note bytes: 1a5. or *note bytearray: 4e3.) [const char *encoding, char **buffer]

     Same as ‘es’ except that byte string objects are passed through
     without recoding them.  Instead, the implementation assumes that
     the byte string object uses the encoding passed in as parameter.

‘es#’ (*note str: 3f2.) [const char *encoding, char **buffer, *note Py_ssize_t: a03. *buffer_length]

     This variant on ‘s#’ is used for encoding Unicode into a character
     buffer.  Unlike the ‘es’ format, this variant allows input data
     which contains NUL characters.

     It requires three arguments.  The first is only used as input, and
     must be a const char* which points to the name of an encoding as a
     NUL-terminated string, or ‘NULL’, in which case ‘'utf-8'’ encoding
     is used.  An exception is raised if the named encoding is not known
     to Python.  The second argument must be a char**; the value of the
     pointer it references will be set to a buffer with the contents of
     the argument text.  The text will be encoded in the encoding
     specified by the first argument.  The third argument must be a
     pointer to an integer; the referenced integer will be set to the
     number of bytes in the output buffer.

     There are two modes of operation:

     If '*buffer' points a ‘NULL’ pointer, the function will allocate a
     buffer of the needed size, copy the encoded data into this buffer
     and set '*buffer' to reference the newly allocated storage.  The
     caller is responsible for calling *note PyMem_Free(): 13b0. to free
     the allocated buffer after usage.

     If '*buffer' points to a non-‘NULL’ pointer (an already allocated
     buffer), *note PyArg_ParseTuple(): 517. will use this location as
     the buffer and interpret the initial value of '*buffer_length' as
     the buffer size.  It will then copy the encoded data into the
     buffer and NUL-terminate it.  If the buffer is not large enough, a
     *note ValueError: 1e7. will be set.

     In both cases, '*buffer_length' is set to the length of the encoded
     data without the trailing NUL byte.

‘et#’ (*note str: 3f2, *note bytes: 1a5. or *note bytearray: 4e3.) [const char *encoding, char **buffer, *note Py_ssize_t: a03. *buffer_length]

     Same as ‘es#’ except that byte string objects are passed through
     without recoding them.  Instead, the implementation assumes that
     the byte string object uses the encoding passed in as parameter.

在 3.12 版的變更: ‘u’, ‘u#’, ‘Z’, and ‘Z#’ are removed because they used
a legacy ‘Py_UNICODE*’ representation.


File: python.info,  Node: 數字,  Next: 其他物件,  Prev: Strings and buffers,  Up: Parsing arguments

7.6.6.3 數字
............

‘b’ (*note int: 23c.) [unsigned char]

     Convert a nonnegative Python integer to an unsigned tiny int,
     stored in a C unsigned char.

‘B’ (*note int: 23c.) [unsigned char]

     Convert a Python integer to a tiny int without overflow checking,
     stored in a C unsigned char.

‘h’ (*note int: 23c.) [short int]

     將一個 Python 整數轉換成 C 的 short int。

‘H’ (*note int: 23c.) [unsigned short int]

     將一個 Python 整數轉換成 C 的 unsigned short int，轉換過程無溢位檢
     查。

‘i’ (*note int: 23c.) [int]

     將一個 Python 整數轉換成 C 的 int。

‘I’ (*note int: 23c.) [unsigned int]

     將一個 Python 整數轉換成 C 的 unsigned int，轉換過程無溢位檢查。

‘l’ (*note int: 23c.) [long int]

     將一個 Python 整數轉換成 C 的 long int。

‘k’ (*note int: 23c.) [unsigned long]

     將一個 Python 整數轉換成 C 的 unsigned long，轉換過程無溢位檢查。

‘L’ (*note int: 23c.) [long long]

     將一個 Python 整數轉換成 C 的 long long。

‘K’ (*note int: 23c.) [unsigned long long]

     將一個 Python 整數轉換成 C 的 unsigned long long，轉換過程無溢位檢
     查。

‘n’ (*note int: 23c.) [*note Py_ssize_t: a03.]

     將一個 Python 整數轉換成 C 的 *note Py_ssize_t: a03.。

‘c’（*note bytes: 1a5. 或長度為 1 的 *note bytearray: 4e3.）[char]

     Convert a Python byte, represented as a *note bytes: 1a5. or *note
     bytearray: 4e3. object of length 1, to a C char.

     在 3.3 版的變更: 允許 *note bytearray: 4e3. 物件。

‘C’（長度為 1 的 *note str: 3f2.）[int]

     Convert a Python character, represented as a *note str: 3f2. object
     of length 1, to a C int.

‘f’ (*note float: 2c8.) [float]

     將一個 Python 浮點數轉換成 C 的 :c:type:float。

‘d’ (*note float: 2c8.) [double]

     將一個 Python 浮點數轉換成 C 的 :c:type:double。

‘D’ (*note complex: 2c9.) [Py_complex]

     將一個 Python 複數轉換成 C 的 *note Py_complex: 4933. 結構。


File: python.info,  Node: 其他物件,  Next: API 函式,  Prev: 數字,  Up: Parsing arguments

7.6.6.4 其他物件
................

‘O’（物件）[PyObject *]

     Store a Python object (without any conversion) in a C object
     pointer.  The C program thus receives the actual object that was
     passed.  A new *note strong reference: 2ee. to the object is not
     created (i.e.  its reference count is not increased).  The pointer
     stored is not ‘NULL’.

‘O!’（物件）['typeobject', PyObject *]

     Store a Python object in a C object pointer.  This is similar to
     ‘O’, but takes two C arguments: the first is the address of a
     Python type object, the second is the address of the C variable (of
     type *note PyObject: 311.*) into which the object pointer is
     stored.  If the Python object does not have the required type,
     *note TypeError: 4dd. is raised.

‘O&’（物件）['converter', 'anything']

     Convert a Python object to a C variable through a 'converter'
     function.  This takes two arguments: the first is a function, the
     second is the address of a C variable (of arbitrary type),
     converted to void*.  The 'converter' function in turn is called as
     follows:

          status = converter(object, address);

     where 'object' is the Python object to be converted and 'address'
     is the void* argument that was passed to the ‘PyArg_Parse*’
     function.  The returned 'status' should be ‘1’ for a successful
     conversion and ‘0’ if the conversion has failed.  When the
     conversion fails, the 'converter' function should raise an
     exception and leave the content of 'address' unmodified.

     If the 'converter' returns ‘Py_CLEANUP_SUPPORTED’, it may get
     called a second time if the argument parsing eventually fails,
     giving the converter a chance to release any memory that it had
     already allocated.  In this second call, the 'object' parameter
     will be ‘NULL’; 'address' will have the same value as in the
     original call.

     在 3.1 版的變更: 加入 ‘Py_CLEANUP_SUPPORTED’。

‘p’ (*note bool: 40e.) [int]

     Tests the value passed in for truth (a boolean 'p'redicate) and
     converts the result to its equivalent C true/false integer value.
     Sets the int to ‘1’ if the expression was true and ‘0’ if it was
     false.  This accepts any valid Python value.  See *note 真值檢測:
     2035. for more information about how Python tests values for truth.

     在 3.3 版被加入.

‘(items)’ (*note tuple: 322.) ['matching-items']

     The object must be a Python sequence whose length is the number of
     format units in 'items'.  The C arguments must correspond to the
     individual format units in 'items'.  Format units for sequences may
     be nested.

It is possible to pass "long" integers (integers whose value exceeds the
platform's ‘LONG_MAX’) however no proper range checking is done -- the
most significant bits are silently truncated when the receiving field is
too small to receive the value (actually, the semantics are inherited
from downcasts in C -- your mileage may vary).

A few other characters have a meaning in a format string.  These may not
occur inside nested parentheses.  They are:

‘|’

     Indicates that the remaining arguments in the Python argument list
     are optional.  The C variables corresponding to optional arguments
     should be initialized to their default value -- when an optional
     argument is not specified, *note PyArg_ParseTuple(): 517. does not
     touch the contents of the corresponding C variable(s).

‘$’

     *note PyArg_ParseTupleAndKeywords(): 2e9. only: Indicates that the
     remaining arguments in the Python argument list are keyword-only.
     Currently, all keyword-only arguments must also be optional
     arguments, so ‘|’ must always be specified before ‘$’ in the format
     string.

     在 3.3 版被加入.

‘:’

     The list of format units ends here; the string after the colon is
     used as the function name in error messages (the "associated value"
     of the exception that *note PyArg_ParseTuple(): 517. raises).

‘;’

     The list of format units ends here; the string after the semicolon
     is used as the error message 'instead' of the default error
     message.  ‘:’ and ‘;’ mutually exclude each other.

Note that any Python object references which are provided to the caller
are 'borrowed' references; do not release them (i.e.  do not decrement
their reference count)!

Additional arguments passed to these functions must be addresses of
variables whose type is determined by the format string; these are used
to store values from the input tuple.  There are a few cases, as
described in the list of format units above, where these parameters are
used as input values; they should match what is specified for the
corresponding format unit in that case.

For the conversion to succeed, the 'arg' object must match the format
and the format must be exhausted.  On success, the ‘PyArg_Parse*’
functions return true, otherwise they return false and raise an
appropriate exception.  When the ‘PyArg_Parse*’ functions fail due to
conversion failure in one of the format units, the variables at the
addresses corresponding to that and the following format units are left
untouched.


File: python.info,  Node: API 函式,  Prev: 其他物件,  Up: Parsing arguments

7.6.6.5 API 函式
................

 -- C 函式: int PyArg_ParseTuple (PyObject *args, const char *format,
          ...)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Parse the parameters of a
     function that takes only positional parameters into local
     variables.  Returns true on success; on failure, it returns false
     and raises the appropriate exception.

 -- C 函式: int PyArg_VaParse (PyObject *args, const char *format,
          va_list vargs)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Identical to *note
     PyArg_ParseTuple(): 517, except that it accepts a va_list rather
     than a variable number of arguments.

 -- C 函式: int PyArg_ParseTupleAndKeywords (PyObject *args, PyObject
          *kw, const char *format, char *const *keywords, ...)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Parse the parameters of a
     function that takes both positional and keyword parameters into
     local variables.  The 'keywords' argument is a ‘NULL’-terminated
     array of keyword parameter names specified as null-terminated ASCII
     or UTF-8 encoded C strings.  Empty names denote *note
     positional-only parameters: a28.  Returns true on success; on
     failure, it returns false and raises the appropriate exception.

          備註: The 'keywords' parameter declaration is char *const* in
          C and const char *const* in C++.  This can be overridden with
          the *note PY_CXX_CONST: 2eb. macro.

     在 3.6 版的變更: Added support for *note positional-only
     parameters: a28.

     在 3.13 版的變更: The 'keywords' parameter has now type char
     *const* in C and const char *const* in C++, instead of char**.
     Added support for non-ASCII keyword parameter names.

 -- C 函式: int PyArg_VaParseTupleAndKeywords (PyObject *args, PyObject
          *kw, const char *format, char *const *keywords, va_list vargs)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Identical to *note
     PyArg_ParseTupleAndKeywords(): 2e9, except that it accepts a
     va_list rather than a variable number of arguments.

 -- C 函式: int PyArg_ValidateKeywordArguments (PyObject*)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Ensure that the keys in the
     keywords argument dictionary are strings.  This is only needed if
     *note PyArg_ParseTupleAndKeywords(): 2e9. is not used, since the
     latter already does this check.

     在 3.2 版被加入.

 -- C 函式: int PyArg_Parse (PyObject *args, const char *format, ...)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Parse the parameter of a
     function that takes a single positional parameter into a local
     variable.  Returns true on success; on failure, it returns false
     and raises the appropriate exception.

     Example:

          // Function using METH_O calling convention
          static PyObject*
          my_function(PyObject *module, PyObject *arg)
          {
              int value;
              if (!PyArg_Parse(arg, "i:my_function", &value)) {
                  return NULL;
              }
              // ... use value ...
          }

 -- C 函式: int PyArg_UnpackTuple (PyObject *args, const char *name,
          Py_ssize_t min, Py_ssize_t max, ...)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  A simpler form of parameter
     retrieval which does not use a format string to specify the types
     of the arguments.  Functions which use this method to retrieve
     their parameters should be declared as *note METH_VARARGS: 1478. in
     function or method tables.  The tuple containing the actual
     parameters should be passed as 'args'; it must actually be a tuple.
     The length of the tuple must be at least 'min' and no more than
     'max'; 'min' and 'max' may be equal.  Additional arguments must be
     passed to the function, each of which should be a pointer to a
     *note PyObject: 311.* variable; these will be filled in with the
     values from 'args'; they will contain *note borrowed references:
     2ef.  The variables which correspond to optional parameters not
     given by 'args' will not be filled in; these should be initialized
     by the caller.  This function returns true on success and false if
     'args' is not a tuple or contains the wrong number of elements; an
     exception will be set if there was a failure.

     This is an example of the use of this function, taken from the
     sources for the ‘_weakref’ helper module for weak references:

          static PyObject *
          weakref_ref(PyObject *self, PyObject *args)
          {
              PyObject *object;
              PyObject *callback = NULL;
              PyObject *result = NULL;

              if (PyArg_UnpackTuple(args, "ref", 1, 2, &object, &callback)) {
                  result = PyWeakref_NewRef(object, callback);
              }
              return result;
          }

     The call to *note PyArg_UnpackTuple(): 1476. in this example is
     entirely equivalent to this call to *note PyArg_ParseTuple(): 517.:

          PyArg_ParseTuple(args, "O|O:ref", &object, &callback)

 -- C 巨集: PY_CXX_CONST

     The value to be inserted, if any, before char *const* in the
     'keywords' parameter declaration of *note
     PyArg_ParseTupleAndKeywords(): 2e9. and *note
     PyArg_VaParseTupleAndKeywords(): 2ea.  Default empty for C and
     ‘const’ for C++ (const char *const*).  To override, define it to
     the desired value before including ‘Python.h’.

     在 3.13 版被加入.


File: python.info,  Node: Building values,  Prev: Parsing arguments,  Up: 剖析引數與建置數值

7.6.6.6 Building values
.......................

 -- C 函式: *note PyObject: 311. *Py_BuildValue (const char *format,
          ...)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a
     new value based on a format string similar to those accepted by the
     ‘PyArg_Parse*’ family of functions and a sequence of values.
     Returns the value or ‘NULL’ in the case of an error; an exception
     will be raised if ‘NULL’ is returned.

     *note Py_BuildValue(): 84c. does not always build a tuple.  It
     builds a tuple only if its format string contains two or more
     format units.  If the format string is empty, it returns ‘None’; if
     it contains exactly one format unit, it returns whatever object is
     described by that format unit.  To force it to return a tuple of
     size 0 or one, parenthesize the format string.

     When memory buffers are passed as parameters to supply data to
     build objects, as for the ‘s’ and ‘s#’ formats, the required data
     is copied.  Buffers provided by the caller are never referenced by
     the objects created by *note Py_BuildValue(): 84c.  In other words,
     if your code invokes ‘malloc()’ and passes the allocated memory to
     *note Py_BuildValue(): 84c, your code is responsible for calling
     ‘free()’ for that memory once *note Py_BuildValue(): 84c. returns.

     In the following description, the quoted form is the format unit;
     the entry in (round) parentheses is the Python object type that the
     format unit will return; and the entry in [square] brackets is the
     type of the C value(s) to be passed.

     The characters space, tab, colon and comma are ignored in format
     strings (but not within format units such as ‘s#’).  This can be
     used to make long format strings a tad more readable.

     ‘s’（*note str: 3f2. 或 ‘None’）[const char *]

          Convert a null-terminated C string to a Python *note str: 3f2.
          object using ‘'utf-8'’ encoding.  If the C string pointer is
          ‘NULL’, ‘None’ is used.

     ‘s#’（*note str: 3f2. 或 ‘None’）[const char *, *note Py_ssize_t: a03.]

          Convert a C string and its length to a Python *note str: 3f2.
          object using ‘'utf-8'’ encoding.  If the C string pointer is
          ‘NULL’, the length is ignored and ‘None’ is returned.

     ‘y’ (*note bytes: 1a5.) [const char *]

          This converts a C string to a Python *note bytes: 1a5. object.
          If the C string pointer is ‘NULL’, ‘None’ is returned.

     ‘y#’ (*note bytes: 1a5.) [const char *, *note Py_ssize_t: a03.]

          This converts a C string and its lengths to a Python object.
          If the C string pointer is ‘NULL’, ‘None’ is returned.

     ‘z’（*note str: 3f2. 或 ‘None’）[const char *]

          和 ‘s’ 相同。

     ‘z#’（*note str: 3f2. 或 ‘None’）[const char *, *note Py_ssize_t: a03.]

          和 ‘s#’ 相同。

     ‘u’ (*note str: 3f2.) [const wchar_t *]

          Convert a null-terminated ‘wchar_t’ buffer of Unicode (UTF-16
          or UCS-4) data to a Python Unicode object.  If the Unicode
          buffer pointer is ‘NULL’, ‘None’ is returned.

     ‘u#’ (*note str: 3f2.) [const wchar_t *, *note Py_ssize_t: a03.]

          Convert a Unicode (UTF-16 or UCS-4) data buffer and its length
          to a Python Unicode object.  If the Unicode buffer pointer is
          ‘NULL’, the length is ignored and ‘None’ is returned.

     ‘U’（*note str: 3f2. 或 ‘None’）[const char *]

          和 ‘s’ 相同。

     ‘U#’（*note str: 3f2. 或 ‘None’）[const char *, *note Py_ssize_t: a03.]

          和 ‘s#’ 相同。

     ‘i’ (*note int: 23c.) [int]

          將一個 C 的 int 轉換成 Python 整數物件。

     ‘b’ (*note int: 23c.) [char]

          將一個 C 的 char 轉換成 Python 整數物件。

     ‘h’ (*note int: 23c.) [short int]

          將一個 C 的 short int 轉換成 Python 整數物件。

     ‘l’ (*note int: 23c.) [long int]

          將一個 C 的 long int 轉換成 Python 整數物件。

     ‘B’ (*note int: 23c.) [unsigned char]

          將一個 C 的 unsigned char 轉換成 Python 整數物件。

     ‘H’ (*note int: 23c.) [unsigned short int]

          將一個 C 的 unsigned short int 轉換成 Python 整數物件。

     ‘I’ (*note int: 23c.) [unsigned int]

          將一個 C 的 unsigned int 轉換成 Python 整數物件。

     ‘k’ (*note int: 23c.) [unsigned long]

          將一個 C 的 unsigned long 轉換成 Python 整數物件。

     ‘L’ (*note int: 23c.) [long long]

          將一個 C 的 long long 轉換成 Python 整數物件。

     ‘K’ (*note int: 23c.) [unsigned long long]

          將一個 C 的 unsigned long long 轉換成 Python 整數物件。

     ‘n’ (*note int: 23c.) [*note Py_ssize_t: a03.]

          將一個 C 的 *note Py_ssize_t: a03. 轉換成 Python 整數。

     ‘c’（長度為 1 的 *note bytes: 1a5.）[char]

          將一個 C 中代表一個位元組的 int 轉換成 Python 中長度為一的
          *note bytes: 1a5.。

     ‘C’（長度為 1 的 *note str: 3f2.）[int]

          將一個 C 中代表一個字元的 int 轉換成 Python 中長度為一的 *note
          str: 3f2.。

     ‘d’ (*note float: 2c8.) [double]

          將一個 C 的 double 轉換成 Python 浮點數。

     ‘f’ (*note float: 2c8.) [float]

          將一個 C 的 float 轉換成 Python 浮點數。

     ‘D’ (*note complex: 2c9.) [Py_complex *]

          將一個 C 的 *note Py_complex: 4933. 結構轉換成 Python 複數。

     ‘O’（物件）[PyObject *]

          Pass a Python object untouched but create a new *note strong
          reference: 2ee. to it (i.e.  its reference count is
          incremented by one).  If the object passed in is a ‘NULL’
          pointer, it is assumed that this was caused because the call
          producing the argument found an error and set an exception.
          Therefore, *note Py_BuildValue(): 84c. will return ‘NULL’ but
          won't raise an exception.  If no exception has been raised
          yet, *note SystemError: 51b. is set.

     ‘S’（物件）[PyObject *]

          和 ‘O’ 相同。

     ‘N’（物件）[PyObject *]

          Same as ‘O’, except it doesn't create a new *note strong
          reference: 2ee.  Useful when the object is created by a call
          to an object constructor in the argument list.

     ‘O&’（物件）['converter', 'anything']

          Convert 'anything' to a Python object through a 'converter'
          function.  The function is called with 'anything' (which
          should be compatible with void*) as its argument and should
          return a "new" Python object, or ‘NULL’ if an error occurred.

     ‘(items)’ (*note tuple: 322.) ['matching-items']

          Convert a sequence of C values to a Python tuple with the same
          number of items.

     ‘[items]’ (*note list: 5b6.) ['matching-items']

          Convert a sequence of C values to a Python list with the same
          number of items.

     ‘{items}’ (*note dict: 23b.) ['matching-items']

          Convert a sequence of C values to a Python dictionary.  Each
          pair of consecutive C values adds one item to the dictionary,
          serving as key and value, respectively.

     If there is an error in the format string, the *note SystemError:
     51b. exception is set and ‘NULL’ returned.

 -- C 函式: *note PyObject: 311. *Py_VaBuildValue (const char *format,
          va_list vargs)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Identical
     to *note Py_BuildValue(): 84c, except that it accepts a va_list
     rather than a variable number of arguments.


File: python.info,  Node: 字串轉換與格式化,  Next: PyHash API,  Prev: 剖析引數與建置數值,  Up: 工具

7.6.7 字串轉換與格式化
----------------------

用於數字轉換和格式化字串輸出的函式。

 -- C 函式: int PyOS_snprintf (char *str, size_t size, const char
          *format, ...)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  根據格式字串 'format' 和額外引
     數，輸出不超過 'size' 位元組給 'str'。請參閱 Unix 手冊頁面
     ‘snprintf(3)(1)’。

 -- C 函式: int PyOS_vsnprintf (char *str, size_t size, const char
          *format, va_list va)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  根據格式字串 'format' 和變數引
     數串列 'va'，輸出不超過 'size' 位元組給 'str'。Unix 手冊頁面
     ‘vsnprintf(3)(2)’。

*note PyOS_snprintf(): 1479. 和 *note PyOS_vsnprintf(): 147a. 包裝標準 C
函式庫函式 ‘snprintf()’ 和 ‘vsnprintf()’。它們的目的是確保邊角案例
(corner case) 下的行為一致，而標準 C 函式則不然。

包裝器確保回傳時 ‘str[size-1]’ 始終為 ‘'\0'’。他們永遠不會在 str 中寫入
超過 'size' 位元組（包括尾隨的 ‘'\0'’）。這兩個函式都要求 ‘str != NULL’、
‘size > 0’、‘format != NULL’ 和 ‘size < INT_MAX’。請注意，這表示沒有與
C99 ‘n = snprintf(NULL, 0, ...)’ 等效的函式來決定必要的緩衝區大小。

這些函式的回傳值 ('rv') 應如下被直譯：

   * 當 ‘0 <= rv < size’ 時，輸出轉換成功，'rv' 字元被寫入 'str'（不包括
     ‘str[rv]’ 處的尾隨 ‘'\0'’ 位元組）。

   * 當 ‘rv >= size’ 時，輸出轉換被截斷，並且需要具有 ‘rv + 1’ 位元組的
     緩衝區才能成功。在這種情況下，‘str[size-1]’ 是 ‘'\0'’。

   * 當 ‘rv < 0’ 時，代表「有不好的事情發生了」。在這種情況下，
     ‘str[size-1]’ 也是 ‘'\0'’，但 'str' 的其餘部分未定義。錯誤的確切原
     因取決於底層平台。

以下函式提供與區域設定無關 (locale-independent) 的字串到數字的轉換。

 -- C 函式: unsigned long PyOS_strtoul (const char *str, char **ptr, int
          base)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Convert the initial part of
     the string in ‘str’ to an unsigned long value according to the
     given ‘base’, which must be between ‘2’ and ‘36’ inclusive, or be
     the special value ‘0’.

     Leading white space and case of characters are ignored.  If ‘base’
     is zero it looks for a leading ‘0b’, ‘0o’ or ‘0x’ to tell which
     base.  If these are absent it defaults to ‘10’.  Base must be 0 or
     between 2 and 36 (inclusive).  If ‘ptr’ is non-‘NULL’ it will
     contain a pointer to the end of the scan.

     If the converted value falls out of range of corresponding return
     type, range error occurs (‘errno’ is set to ‘ERANGE’) and
     ‘ULONG_MAX’ is returned.  If no conversion can be performed, ‘0’ is
     returned.

     也請見 Unix 手冊頁面 ‘strtoul(3)(3)’。

     在 3.2 版被加入.

 -- C 函式: long PyOS_strtol (const char *str, char **ptr, int base)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Convert the initial part of
     the string in ‘str’ to an long value according to the given ‘base’,
     which must be between ‘2’ and ‘36’ inclusive, or be the special
     value ‘0’.

     Same as *note PyOS_strtoul(): 4832, but return a long value instead
     and ‘LONG_MAX’ on overflows.

     也請見 Unix 手冊頁面 ‘strtol(3)(4)’。

     在 3.2 版被加入.

 -- C 函式: double PyOS_string_to_double (const char *s, char **endptr,
          PyObject *overflow_exception)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  將字串 ‘s’ 轉換為 double，失敗
     時引發 Python 例外。接受的字串集合對應於 Python 的 *note float():
     2c8. 建構函式接受的字串集合，但 ‘s’ 不得有前導或尾隨的空格。轉換與
     目前區域設定無關。

     如果 ‘endptr’ 為 ‘NULL’，則轉換整個字串。如果字串不是浮點數的有效表
     示，則引發 *note ValueError: 1e7. 並回傳 ‘-1.0’。

     如果 endptr 不是 ‘NULL’，則盡可能轉換字串，並將 ‘*endptr’ 設定為指
     向第一個未轉換的字元。如果字串的初始片段都不是浮點數的有效表示，則
     設定 ‘*endptr’ 指向字串的開頭，引發 ValueError 並回傳 ‘-1.0’。

     如果 ‘s’ 表示的值太大而無法儲存在浮點數中（例如 ‘"1e500"’ 在許多平
     台上都是這樣的字串），如果 ‘overflow_exception’ 為 ‘NULL’ 則回傳
     ‘Py_HUGE_VAL’（會帶有適當的符號）並且不設定任何例外。否則，
     ‘overflow_exception’ 必須指向一個 Python 例外物件；引發該例外並回傳
     ‘-1.0’。在這兩種情況下，將 ‘*endptr’ 設定為指向轉換後的值之後的第一
     個字元。

     如果轉換期間發生任何其他錯誤（例如記憶體不足的錯誤），請設定適當的
     Python 例外並回傳 ‘-1.0’。

     在 3.1 版被加入.

 -- C 函式: char *PyOS_double_to_string (double val, char format_code,
          int precision, int flags, int *ptype)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  使用提供的 'format_code'、
     'precision' 和 'flags' 將 double 'val' 轉換為字串。

     'format_code' 必須是 ‘'e'’、‘'E'’、‘'f'’、‘'F'’、‘'g'’、‘'G'’ 或
     ‘'r'’ 其中之一。對於 ‘'r'’，提供的 'precision' 必須為 0 並會被忽略
     。‘'r'’ 格式碼指定標準 *note repr(): 7a1. 格式。

     'flags' 可以是零個或多個值 ‘Py_DTSF_SIGN’、‘Py_DTSF_ADD_DOT_0’ 或
     ‘Py_DTSF_ALT’，會被聯集在一起：

        * ‘Py_DTSF_SIGN’ 代表總是在回傳的字串前面加上符號字元，即使
          'val' 非負數。

        * ‘Py_DTSF_ADD_DOT_0’ 代表確保回傳的字串看起來不會像整數。

        * ‘Py_DTSF_ALT’ 代表要套用「備用的 (alternate)」格式化規則。有關
          詳細資訊，請參閱 *note PyOS_snprintf(): 1479. ‘'#'’ 的文件。

     如果 'ptype' 是非 ‘NULL’，那麼它指向的值將被設定為
     ‘Py_DTST_FINITE’、‘Py_DTST_INFINITE’ 或 ‘Py_DTST_NAN’ 其中之一，分
     別代表 'val' 是有限數、無限數或非數。

     回傳值是指向 'buffer' 的指標，其中包含轉換後的字串，如果轉換失敗則
     回傳 ‘NULL’。呼叫者負責透過呼叫 *note PyMem_Free(): 13b0. 來釋放回
     傳的字串。

     在 3.1 版被加入.

 -- C 函式: int PyOS_stricmp (const char *s1, const char *s2)

     不區分大小寫的字串比較。函式的作用方式幾乎與 ‘strcmp()’ 相同，只是
     它忽略大小寫。

 -- C 函式: int PyOS_strnicmp (const char *s1, const char *s2,
          Py_ssize_t size)

     不區分大小寫的字串比較。函式的作用方式幾乎與 ‘strncmp()’ 相同，只是
     它忽略大小寫。

   ---------- Footnotes ----------

   (1) https://manpages.debian.org/snprintf(3)

   (2) https://manpages.debian.org/vsnprintf(3)

   (3) https://manpages.debian.org/strtoul(3)

   (4) https://manpages.debian.org/strtol(3)


File: python.info,  Node: PyHash API,  Next: Reflection,  Prev: 字串轉換與格式化,  Up: 工具

7.6.8 PyHash API
----------------

See also the *note PyTypeObject.tp_hash: 472b. member and *note
數值型別的雜湊: 207d.

 -- C 型別: type Py_hash_t

     雜湊值型別：有符號整數。

     在 3.2 版被加入.

 -- C 型別: type Py_uhash_t

     雜湊值型別：無符號整數。

     在 3.2 版被加入.

 -- C 巨集: PyHASH_MODULUS

     The Mersenne prime(1) ‘P = 2**n -1’, used for numeric hash scheme.

     在 3.13 版被加入.

 -- C 巨集: PyHASH_BITS

     The exponent ‘n’ of ‘P’ in *note PyHASH_MODULUS: 155f.

     在 3.13 版被加入.

 -- C 巨集: PyHASH_MULTIPLIER

     Prime multiplier used in string and various other hashes.

     在 3.13 版被加入.

 -- C 巨集: PyHASH_INF

     The hash value returned for a positive infinity.

     在 3.13 版被加入.

 -- C 巨集: PyHASH_IMAG

     The multiplier used for the imaginary part of a complex number.

     在 3.13 版被加入.

 -- C 型別: type PyHash_FuncDef

     *note PyHash_GetFuncDef(): 4941. 所使用的雜湊函式定義。

      -- C 成員函數: const char *name

          雜湊函式名稱（UTF-8 編碼字串）。

      -- C 成員函數: const int hash_bits

          雜湊值的內部大小（以位元為單位）。

      -- C 成員函數: const int seed_bits

          Seed 輸入的大小（以位元為單位）。

     在 3.4 版被加入.

 -- C 函式: *note PyHash_FuncDef: 4940. *PyHash_GetFuncDef (void)

     取得雜湊函式定義。

     也參考
     ......

     PEP 456(2)「安全且可交替使用的雜湊演算法 (Secure and
     interchangeable hash algorithm)」。

     在 3.4 版被加入.

 -- C 函式: *note Py_hash_t: 11fc. Py_HashPointer (const void *ptr)

     Hash a pointer value: process the pointer value as an integer (cast
     it to ‘uintptr_t’ internally).  The pointer is not dereferenced.

     The function cannot fail: it cannot return ‘-1’.

     在 3.13 版被加入.

 -- C 函式: *note Py_hash_t: 11fc. PyObject_GenericHash (PyObject *obj)

     Generic hashing function that is meant to be put into a type
     object's ‘tp_hash’ slot.  Its result only depends on the object's
     identity.

     'CPython 實作細節：' In CPython, it is equivalent to *note
     Py_HashPointer(): 32e.

     在 3.13 版被加入.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Mersenne_prime

   (2) https://peps.python.org/pep-0456/


File: python.info,  Node: Reflection,  Next: 編解碼器註冊表和支援函式,  Prev: PyHash API,  Up: 工具

7.6.9 Reflection
----------------

 -- C 函式: *note PyObject: 311. *PyEval_GetBuiltins (void)
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

     在 3.13 版之後被棄用: Use *note PyEval_GetFrameBuiltins(): 345.
     instead.

     Return a dictionary of the builtins in the current execution frame,
     or the interpreter of the thread state if no frame is currently
     executing.

 -- C 函式: *note PyObject: 311. *PyEval_GetLocals (void)
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

     在 3.13 版之後被棄用: Use either *note PyEval_GetFrameLocals():
     347. to obtain the same behaviour as calling *note locals(): 127.
     in Python code, or else call *note PyFrame_GetLocals(): 35f. on the
     result of *note PyEval_GetFrame(): 16bf. to access the *note
     f_locals: 165. attribute of the currently executing frame.

     Return a mapping providing access to the local variables in the
     current execution frame, or ‘NULL’ if no frame is currently
     executing.

     Refer to *note locals(): 127. for details of the mapping returned
     at different scopes.

     As this function returns a *note borrowed reference: 2ef, the
     dictionary returned for *note optimized scopes: 161. is cached on
     the frame object and will remain alive as long as the frame object
     does.  Unlike *note PyEval_GetFrameLocals(): 347. and *note
     locals(): 127, subsequent calls to this function in the same frame
     will update the contents of the cached dictionary to reflect
     changes in the state of the local variables rather than returning a
     new snapshot.

     在 3.13 版的變更: As part of PEP 667(1), *note PyFrame_GetLocals():
     35f, *note locals(): 127, and *note FrameType.f_locals: 165. no
     longer make use of the shared cache dictionary.  Refer to the *note
     What's New entry: 128. for additional details.

 -- C 函式: *note PyObject: 311. *PyEval_GetGlobals (void)
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

     在 3.13 版之後被棄用: Use *note PyEval_GetFrameGlobals(): 346.
     instead.

     Return a dictionary of the global variables in the current
     execution frame, or ‘NULL’ if no frame is currently executing.

 -- C 函式: *note PyFrameObject: 72d. *PyEval_GetFrame (void)
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the
     current thread state's frame, which is ‘NULL’ if no frame is
     currently executing.

     另請見 *note PyThreadState_GetFrame(): 732.。

 -- C 函式: *note PyObject: 311. *PyEval_GetFrameBuiltins (void)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本
     開始.'  Return a dictionary of the builtins in the current
     execution frame, or the interpreter of the thread state if no frame
     is currently executing.

     在 3.13 版被加入.

 -- C 函式: *note PyObject: 311. *PyEval_GetFrameLocals (void)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本
     開始.'  Return a dictionary of the local variables in the current
     execution frame, or ‘NULL’ if no frame is currently executing.
     Equivalent to calling *note locals(): 127. in Python code.

     To access *note f_locals: 165. on the current frame without making
     an independent snapshot in *note optimized scopes: 161, call *note
     PyFrame_GetLocals(): 35f. on the result of *note PyEval_GetFrame():
     16bf.

     在 3.13 版被加入.

 -- C 函式: *note PyObject: 311. *PyEval_GetFrameGlobals (void)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本
     開始.'  Return a dictionary of the global variables in the current
     execution frame, or ‘NULL’ if no frame is currently executing.
     Equivalent to calling *note globals(): 176a. in Python code.

     在 3.13 版被加入.

 -- C 函式: const char *PyEval_GetFuncName (PyObject *func)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the name of 'func' if
     it is a function, class or instance object, else the name of
     'func's type.

 -- C 函式: const char *PyEval_GetFuncDesc (PyObject *func)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a description string,
     depending on the type of 'func'.  Return values include "()" for
     functions and methods, " constructor", " instance", and " object".
     Concatenated with the result of *note PyEval_GetFuncName(): 47d0,
     the result will be a description of 'func'.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0667/


File: python.info,  Node: 編解碼器註冊表和支援函式,  Next: PyTime C API,  Prev: Reflection,  Up: 工具

7.6.10 編解碼器註冊表和支援函式
-------------------------------

 -- C 函式: int PyCodec_Register (PyObject *search_function)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  註冊一個新的編解碼器搜索函式。

     作為副作用 (side effect)，這會嘗試載入 ‘encodings’（如果尚未完成）
     ，以確保它始終位於搜索函式列表中的第一個。

 -- C 函式: int PyCodec_Unregister (PyObject *search_function)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本開始.'  取消註冊編解
     碼器搜索函式並清除註冊表 (registry) 的快取。如果搜索函式並未被註冊
     ，則不執行任何操作。成功回傳 0，發生錯誤時會引發例外並回傳 -1。

     在 3.10 版被加入.

 -- C 函式: int PyCodec_KnownEncoding (const char *encoding)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  回傳 ‘1’ 或 ‘0’，具體取決於是
     否有給定 'encoding' 的已註冊編解碼器。這個函式總會成功。

 -- C 函式: *note PyObject: 311. *PyCodec_Encode (PyObject *object,
          const char *encoding, const char *errors)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  基於泛用編
     解碼器的編碼 API。

     'object' 被傳遞給以給定 'encoding' 所查找到的編碼器函式，並使用以
     'errors' 定義的錯誤處理方法。'errors' 可以設為 ‘NULL’ 來使用編解碼
     器定義的預設方法。如果找不到編碼器，則引發 *note LookupError:
     20a9.。

 -- C 函式: *note PyObject: 311. *PyCodec_Decode (PyObject *object,
          const char *encoding, const char *errors)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  基於泛用編
     解碼器的解碼 API。

     'object' 被傳遞給以給定 'encoding' 所查找到的解碼器函式，並使用以
     'errors' 定義的錯誤處理方法。'errors' 可以設為 ‘NULL’ 來使用編解碼
     器定義的預設方法。如果找不到編碼器，則引發 *note LookupError:
     20a9.。

* Menu:

* 編解碼器查找 API::
* 用於 Unicode 編碼錯誤處理程式的註冊 API::


File: python.info,  Node: 編解碼器查找 API,  Next: 用於 Unicode 編碼錯誤處理程式的註冊 API,  Up: 編解碼器註冊表和支援函式

7.6.10.1 編解碼器查找 API
.........................

在以下函式中，查找的 'encoding' 字串的所有字元將轉換為小寫，這使得透過此
機制查找的編碼可以不區分大小寫而更有效率。如果未找到編解碼器，則會設定
*note KeyError: 2fb. 並回傳 ‘NULL’。

 -- C 函式: *note PyObject: 311. *PyCodec_Encoder (const char *encoding)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  取得給定
     'encoding' 的編碼器函式。

 -- C 函式: *note PyObject: 311. *PyCodec_Decoder (const char *encoding)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  取得給定
     'encoding' 的解碼器函式。

 -- C 函式: *note PyObject: 311. *PyCodec_IncrementalEncoder (const char
          *encoding, const char *errors)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  取得給定
     'encoding' 的 *note IncrementalEncoder: 22a6. 物件。

 -- C 函式: *note PyObject: 311. *PyCodec_IncrementalDecoder (const char
          *encoding, const char *errors)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  取得給定
     'encoding' 的 *note IncrementalDecoder: 22a7. 物件。

 -- C 函式: *note PyObject: 311. *PyCodec_StreamReader (const char
          *encoding, PyObject *stream, const char *errors)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  取得給定
     'encoding' 的 *note StreamReader: 22ab. 工廠函式。

 -- C 函式: *note PyObject: 311. *PyCodec_StreamWriter (const char
          *encoding, PyObject *stream, const char *errors)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  取得給定
     'encoding' 的 *note StreamWriter: 22aa. 工廠函式。


File: python.info,  Node: 用於 Unicode 編碼錯誤處理程式的註冊 API,  Prev: 編解碼器查找 API,  Up: 編解碼器註冊表和支援函式

7.6.10.2 用於 Unicode 編碼錯誤處理程式的註冊 API
................................................

 -- C 函式: int PyCodec_RegisterError (const char *name, PyObject
          *error)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  在給定的 'name' 下註冊錯誤處理
     回呼 (callback) 函式 'error'。當編解碼器遇到無法編碼的字元/無法解碼
     的位元組並且 'name' 被指定為呼叫編碼/解碼函式時的錯誤參數時，將呼叫
     此回呼函式。

     回呼取得單個引數，即 *note UnicodeEncodeError: 61d.、*note
     UnicodeDecodeError: 9b7. 或 *note UnicodeTranslateError: 217b. 的實
     例，其中包含關於有問題的字元或位元組序列及其在原始字串中偏移量的資
     訊（有關取得此資訊的函式，請參閱 *note Unicode Exception Objects:
     490c.）。回呼必須引發給定的例外，或者回傳一個包含有問題序列的替換的
     二元組 (two-item tuple)，以及一個代表原始字串中應該被恢復的編碼/解
     碼偏移量的整數。

     成功時回傳 ‘0’，錯誤時回傳 ‘-1’。

 -- C 函式: *note PyObject: 311. *PyCodec_LookupError (const char *name)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  查找
     'name' 下已註冊的錯誤處理回呼函式。作為一種特殊情況，可以傳遞
     ‘NULL’，在這種情況下，將回傳 "strict" 的錯誤處理回呼。

 -- C 函式: *note PyObject: 311. *PyCodec_StrictErrors (PyObject *exc)
     '回傳值：總是為 NULL。'' 為 *note 穩定 ABI 的一部分: 4f9.'  引發
     'exc' 作為例外。

 -- C 函式: *note PyObject: 311. *PyCodec_IgnoreErrors (PyObject *exc)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  忽略
     unicode 錯誤，跳過錯誤的輸入。

 -- C 函式: *note PyObject: 311. *PyCodec_ReplaceErrors (PyObject *exc)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  將 unicode
     編碼錯誤替換為 ‘?’ 或 ‘U+FFFD’。

 -- C 函式: *note PyObject: 311. *PyCodec_XMLCharRefReplaceErrors
          (PyObject *exc)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  將 unicode
     編碼錯誤替換為 XML 字元參照。

 -- C 函式: *note PyObject: 311. *PyCodec_BackslashReplaceErrors
          (PyObject *exc)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  將 unicode
     編碼錯誤替換為反斜線跳脫（‘\x’、‘\u’ 和 ‘\U’）。

 -- C 函式: *note PyObject: 311. *PyCodec_NameReplaceErrors (PyObject
          *exc)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本
     開始.'  將 unicode 編碼錯誤替換為 ‘\N{...}’ 跳脫。

     在 3.5 版被加入.


File: python.info,  Node: PyTime C API,  Next: 對 Perf Map 的支援,  Prev: 編解碼器註冊表和支援函式,  Up: 工具

7.6.11 PyTime C API
-------------------

在 3.13 版被加入.

The clock C API provides access to system clocks.  It is similar to the
Python *note time: d7. module.

For C API related to the *note datetime: 28. module, see *note DateTime
物件: 494d.

* Menu:

* Types::
* Clock Functions::
* Raw Clock Functions::
* Conversion functions::


File: python.info,  Node: Types,  Next: Clock Functions,  Up: PyTime C API

7.6.11.1 Types
..............

 -- C 型別: type PyTime_t

     A timestamp or duration in nanoseconds, represented as a signed
     64-bit integer.

     The reference point for timestamps depends on the clock used.  For
     example, *note PyTime_Time(): 338. returns timestamps relative to
     the UNIX epoch.

     The supported range is around [-292.3 years; +292.3 years].  Using
     the Unix epoch (January 1st, 1970) as reference, the supported date
     range is around [1677-09-21; 2262-04-11].  The exact limits are
     exposed as constants:

 -- C 變數: *note PyTime_t: 330. PyTime_MIN

     Minimum value of *note PyTime_t: 330.

 -- C 變數: *note PyTime_t: 330. PyTime_MAX

     Maximum value of *note PyTime_t: 330.


File: python.info,  Node: Clock Functions,  Next: Raw Clock Functions,  Prev: Types,  Up: PyTime C API

7.6.11.2 Clock Functions
........................

The following functions take a pointer to a *note PyTime_t: 330. that
they set to the value of a particular clock.  Details of each clock are
given in the documentation of the corresponding Python function.

The functions return ‘0’ on success, or ‘-1’ (with an exception set) on
failure.

On integer overflow, they set the ‘PyExc_OverflowError’ exception and
set ‘*result’ to the value clamped to the ‘[PyTime_MIN; PyTime_MAX]’
range.  (On current systems, integer overflows are likely caused by
misconfigured system time.)

As any other C API (unless otherwise specified), the functions must be
called with the *note GIL: 13e. held.

 -- C 函式: int PyTime_Monotonic (PyTime_t *result)

     Read the monotonic clock.  See *note time.monotonic(): 238. for
     important details on this clock.

 -- C 函式: int PyTime_PerfCounter (PyTime_t *result)

     Read the performance counter.  See *note time.perf_counter(): a2b.
     for important details on this clock.

 -- C 函式: int PyTime_Time (PyTime_t *result)

     Read the “wall clock” time.  See *note time.time(): 239. for
     details important on this clock.


File: python.info,  Node: Raw Clock Functions,  Next: Conversion functions,  Prev: Clock Functions,  Up: PyTime C API

7.6.11.3 Raw Clock Functions
............................

Similar to clock functions, but don't set an exception on error and
don't require the caller to hold the GIL.

On success, the functions return ‘0’.

On failure, they set ‘*result’ to ‘0’ and return ‘-1’, 'without' setting
an exception.  To get the cause of the error, acquire the GIL and call
the regular (non-‘Raw’) function.  Note that the regular function may
succeed after the ‘Raw’ one failed.

 -- C 函式: int PyTime_MonotonicRaw (PyTime_t *result)

     Similar to *note PyTime_Monotonic(): 334, but don't set an
     exception on error and don't require holding the GIL.

 -- C 函式: int PyTime_PerfCounterRaw (PyTime_t *result)

     Similar to *note PyTime_PerfCounter(): 336, but don't set an
     exception on error and don't require holding the GIL.

 -- C 函式: int PyTime_TimeRaw (PyTime_t *result)

     Similar to *note PyTime_Time(): 338, but don't set an exception on
     error and don't require holding the GIL.


File: python.info,  Node: Conversion functions,  Prev: Raw Clock Functions,  Up: PyTime C API

7.6.11.4 Conversion functions
.............................

 -- C 函式: double PyTime_AsSecondsDouble (PyTime_t t)

     Convert a timestamp to a number of seconds as a C double.

     The function cannot fail, but note that double has limited accuracy
     for large values.


File: python.info,  Node: 對 Perf Map 的支援,  Prev: PyTime C API,  Up: 工具

7.6.12 對 Perf Map 的支援
-------------------------

在支援的平台上（截至撰寫本文時，僅限 Linux），runtime 可以利用 'perf map
檔案'使得外部分析工具（例如 perf(1)）可以見到 Python 函式。正在運行的行
程可能會在 ‘/tmp’ 目錄中建立一個檔案，其中包含可以將一段可執行程式碼對映
到名稱的各個條目。此介面在 Linux Perf 工具的文件(2)中有被描述。

在 Python 中，這些輔助 API 可以被依賴於運行期間 (on the fly) 產生機器碼
的函式庫和功能所使用。

請注意，這些 API 不需要持有全域直譯器鎖 (GIL)。

 -- C 函式: int PyUnstable_PerfMapState_Init (void)

          這是 不穩定 API，它可能在小版本發布中沒有任何警告地被變更。 '這是 *note 不穩定 API: 4ed.，它可能在小版本發布中沒有任何警告地被變更。': 
     打開 ‘/tmp/perf-$pid.map’ 檔案，除非它已經打開，並建立一個鎖以確保
     執行緒安全地 (thread-safe) 寫入該檔案（前提是寫入是透過 *note
     PyUnstable_WritePerfMapEntry(): 1638. 完成的）。通常不需要明確地呼
     叫它；只需使用 *note PyUnstable_WritePerfMapEntry(): 1638. 它就會在
     首次呼叫時初始化狀態。

     建立/打開 perf map 檔案成功時回傳 ‘0’，失敗時回傳 ‘-1’，建立鎖時失
     敗則回傳 ‘-2’。檢查 ‘errno’ 以獲取更多造成失敗的資訊。

 -- C 函式: int PyUnstable_WritePerfMapEntry (const void *code_addr,
          unsigned int code_size, const char *entry_name)

          這是 不穩定 API，它可能在小版本發布中沒有任何警告地被變更。 '這是 *note 不穩定 API: 4ed.，它可能在小版本發布中沒有任何警告地被變更。': 
     將單一條目寫入 ‘/tmp/perf-$pid.map’ 檔案。此函式是執行緒安全的。以
     下是一個條目的範例：

          # address      size  name
          7f3529fcf759 b     py::bar:/run/t.py

     如果尚未開啟 perf map 檔案，將在寫入條目之前呼叫 *note
     PyUnstable_PerfMapState_Init(): 1639.。成功時回傳 ‘0’，失敗時回傳與
     *note PyUnstable_PerfMapState_Init(): 1639. 失敗時相同的錯誤碼。

 -- C 函式: void PyUnstable_PerfMapState_Fini (void)

          這是 不穩定 API，它可能在小版本發布中沒有任何警告地被變更。 '這是 *note 不穩定 API: 4ed.，它可能在小版本發布中沒有任何警告地被變更。': 
     關閉由 *note PyUnstable_PerfMapState_Init(): 1639. 開啟的 perf map
     檔案，這是在直譯器關閉期間由 runtime 本身呼叫的。一般來說，除了處理
     forking 等特定場景外，不應該明確地呼叫它。

   ---------- Footnotes ----------

   (1) https://perf.wiki.kernel.org/index.php/Main_Page

   (2) 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/perf/Documentation/jit-interface.txt


File: python.info,  Node: 抽象物件層 Abstract Objects Layer,  Next: 具體物件層,  Prev: 工具,  Up: Python/C API 參考手冊

7.7 抽象物件層 (Abstract Objects Layer)
=======================================

本章中的函式與 Python 物件相互作用，無論其型別、或具有廣泛類別的物件型別
（例如所有數值型別或所有序列型別）。當使用於不適用的物件型別時，他們會引
發一個 Python 異常 (exception)。

這些函式是不可能用於未正確初始化的物件（例如一個由 *note PyList_New():
4765. 建立的 list 物件），而其中的項目沒有被設為一些非 ‘NULL’ 的值。

* Menu:

* 物件協定::
* 呼叫協定 (Call Protocol): 呼叫協定 Call Protocol.
* 數字協定::
* 序列協定::
* 對映協定::
* 疊代器協議::
* 緩衝協定 (Buffer Protocol): 緩衝協定 Buffer Protocol.


File: python.info,  Node: 物件協定,  Next: 呼叫協定 Call Protocol,  Up: 抽象物件層 Abstract Objects Layer

7.7.1 物件協定
--------------

 -- C 函式: *note PyObject: 311. *Py_GetConstant (unsigned int
          constant_id)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Get a *note
     strong reference: 2ee. to a constant.

     Set an exception and return ‘NULL’ if 'constant_id' is invalid.

     'constant_id' must be one of these constant identifiers:

     Constant Identifier                          Value     Returned object
                                                            
     -------------------------------------------------------------------------------------
                                                            
      -- C 巨集: Py_CONSTANT_NONE                 ‘0’       *note None: 61b.
                                                            
                                                            
      -- C 巨集: Py_CONSTANT_FALSE                ‘1’       *note False: adb.
                                                            
                                                            
      -- C 巨集: Py_CONSTANT_TRUE                 ‘2’       *note True: bb4.
                                                            
                                                            
      -- C 巨集: Py_CONSTANT_ELLIPSIS             ‘3’       *note Ellipsis: 2062.
                                                            
                                                            
      -- C 巨集: Py_CONSTANT_NOT_IMPLEMENTED      ‘4’       *note NotImplemented: 776.
                                                            
                                                            
      -- C 巨集: Py_CONSTANT_ZERO                 ‘5’       ‘0’
                                                            
                                                            
      -- C 巨集: Py_CONSTANT_ONE                  ‘6’       ‘1’
                                                            
                                                            
      -- C 巨集: Py_CONSTANT_EMPTY_STR            ‘7’       ‘''’
                                                            
                                                            
      -- C 巨集: Py_CONSTANT_EMPTY_BYTES          ‘8’       ‘b''’
                                                            
                                                            
      -- C 巨集: Py_CONSTANT_EMPTY_TUPLE          ‘9’       ‘()’
                                                            

     Numeric values are only given for projects which cannot use the
     constant identifiers.

     在 3.13 版被加入.

     'CPython 實作細節：' In CPython, all of these constants are *note
     immortal: 4190.

 -- C 函式: *note PyObject: 311. *Py_GetConstantBorrowed (unsigned int
          constant_id)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Similar to
     *note Py_GetConstant(): 340, but return a *note borrowed reference:
     2ef.

     This function is primarily intended for backwards compatibility:
     using *note Py_GetConstant(): 340. is recommended for new code.

     The reference is borrowed from the interpreter, and is valid until
     the interpreter finalization.

     在 3.13 版被加入.

 -- C 變數: *note PyObject: 311. *Py_NotImplemented

     The ‘NotImplemented’ singleton, used to signal that an operation is
     not implemented for the given type combination.

 -- C 巨集: Py_RETURN_NOTIMPLEMENTED

     Properly handle returning *note Py_NotImplemented: 4964. from
     within a C function (that is, create a new *note strong reference:
     2ee. to *note NotImplemented: 776. and return it).

 -- C 巨集: Py_PRINT_RAW

     Flag to be used with multiple functions that print the object (like
     *note PyObject_Print(): 14e4. and *note PyFile_WriteObject():
     47d9.).  If passed, these function would use the *note str(): 3f2.
     of the object instead of the *note repr(): 7a1.

 -- C 函式: int PyObject_Print (PyObject *o, FILE *fp, int flags)

     Print an object 'o', on file 'fp'.  Returns ‘-1’ on error.  The
     flags argument is used to enable certain printing options.  The
     only option currently supported is *note Py_PRINT_RAW: 4966.; if
     given, the *note str(): 3f2. of the object is written instead of
     the *note repr(): 7a1.

 -- C 函式: int PyObject_HasAttrWithError (PyObject *o, const char
          *attr_name)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Returns ‘1’
     if 'o' has the attribute 'attr_name', and ‘0’ otherwise.  This is
     equivalent to the Python expression ‘hasattr(o, attr_name)’.  On
     failure, return ‘-1’.

     在 3.13 版被加入.

 -- C 函式: int PyObject_HasAttrStringWithError (PyObject *o, const char
          *attr_name)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  This is the
     same as *note PyObject_HasAttrWithError(): 2fc, but 'attr_name' is
     specified as a const char* UTF-8 encoded bytes string, rather than
     a *note PyObject: 311.*.

     在 3.13 版被加入.

 -- C 函式: int PyObject_HasAttr (PyObject *o, PyObject *attr_name)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns ‘1’ if 'o' has the
     attribute 'attr_name', and ‘0’ otherwise.  This function always
     succeeds.

          備註: Exceptions that occur when this calls *note
          __getattr__(): 47a. and *note __getattribute__(): b79. methods
          are silently ignored.  For proper error handling, use *note
          PyObject_HasAttrWithError(): 2fc, *note
          PyObject_GetOptionalAttr(): 2f2. or *note PyObject_GetAttr():
          2f4. instead.

 -- C 函式: int PyObject_HasAttrString (PyObject *o, const char
          *attr_name)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This is the same as *note
     PyObject_HasAttr(): 2fd, but 'attr_name' is specified as a const
     char* UTF-8 encoded bytes string, rather than a *note PyObject:
     311.*.

          備註: Exceptions that occur when this calls *note
          __getattr__(): 47a. and *note __getattribute__(): b79. methods
          or while creating the temporary *note str: 3f2. object are
          silently ignored.  For proper error handling, use *note
          PyObject_HasAttrStringWithError(): 2fe, *note
          PyObject_GetOptionalAttrString(): 2f3. or *note
          PyObject_GetAttrString(): 2f5. instead.

 -- C 函式: *note PyObject: 311. *PyObject_GetAttr (PyObject *o,
          PyObject *attr_name)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Retrieve
     an attribute named 'attr_name' from object 'o'.  Returns the
     attribute value on success, or ‘NULL’ on failure.  This is the
     equivalent of the Python expression ‘o.attr_name’.

     If the missing attribute should not be treated as a failure, you
     can use *note PyObject_GetOptionalAttr(): 2f2. instead.

 -- C 函式: *note PyObject: 311. *PyObject_GetAttrString (PyObject *o,
          const char *attr_name)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  This is
     the same as *note PyObject_GetAttr(): 2f4, but 'attr_name' is
     specified as a const char* UTF-8 encoded bytes string, rather than
     a *note PyObject: 311.*.

     If the missing attribute should not be treated as a failure, you
     can use *note PyObject_GetOptionalAttrString(): 2f3. instead.

 -- C 函式: int PyObject_GetOptionalAttr (PyObject *obj, PyObject
          *attr_name, PyObject **result);
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Variant of
     *note PyObject_GetAttr(): 2f4. which doesn't raise *note
     AttributeError: 2f6. if the attribute is not found.

     If the attribute is found, return ‘1’ and set '*result' to a new
     *note strong reference: 2ee. to the attribute.  If the attribute is
     not found, return ‘0’ and set '*result' to ‘NULL’; the *note
     AttributeError: 2f6. is silenced.  If an error other than *note
     AttributeError: 2f6. is raised, return ‘-1’ and set '*result' to
     ‘NULL’.

     在 3.13 版被加入.

 -- C 函式: int PyObject_GetOptionalAttrString (PyObject *obj, const
          char *attr_name, PyObject **result);
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  This is the
     same as *note PyObject_GetOptionalAttr(): 2f2, but 'attr_name' is
     specified as a const char* UTF-8 encoded bytes string, rather than
     a *note PyObject: 311.*.

     在 3.13 版被加入.

 -- C 函式: *note PyObject: 311. *PyObject_GenericGetAttr (PyObject *o,
          PyObject *name)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Generic
     attribute getter function that is meant to be put into a type
     object's ‘tp_getattro’ slot.  It looks for a descriptor in the
     dictionary of classes in the object's MRO as well as an attribute
     in the object's *note __dict__: c04. (if present).  As outlined in
     *note Implementing Descriptors: bf6, data descriptors take
     preference over instance attributes, while non-data descriptors
     don't.  Otherwise, an *note AttributeError: 2f6. is raised.

 -- C 函式: int PyObject_SetAttr (PyObject *o, PyObject *attr_name,
          PyObject *v)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Set the value of the attribute
     named 'attr_name', for object 'o', to the value 'v'.  Raise an
     exception and return ‘-1’ on failure; return ‘0’ on success.  This
     is the equivalent of the Python statement ‘o.attr_name = v’.

     If 'v' is ‘NULL’, the attribute is deleted.  This behaviour is
     deprecated in favour of using *note PyObject_DelAttr(): 161a, but
     there are currently no plans to remove it.

 -- C 函式: int PyObject_SetAttrString (PyObject *o, const char
          *attr_name, PyObject *v)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This is the same as *note
     PyObject_SetAttr(): 4842, but 'attr_name' is specified as a const
     char* UTF-8 encoded bytes string, rather than a *note PyObject:
     311.*.

     If 'v' is ‘NULL’, the attribute is deleted, but this feature is
     deprecated in favour of using *note PyObject_DelAttrString(): 14f5.

     The number of different attribute names passed to this function
     should be kept small, usually by using a statically allocated
     string as 'attr_name'.  For attribute names that aren't known at
     compile time, prefer calling *note PyUnicode_FromString(): 4748.
     and *note PyObject_SetAttr(): 4842. directly.  For more details,
     see *note PyUnicode_InternFromString(): 14f2, which may be used
     internally to create a key object.

 -- C 函式: int PyObject_GenericSetAttr (PyObject *o, PyObject *name,
          PyObject *value)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Generic attribute setter and
     deleter function that is meant to be put into a type object's *note
     tp_setattro: 471d. slot.  It looks for a data descriptor in the
     dictionary of classes in the object's MRO, and if found it takes
     preference over setting or deleting the attribute in the instance
     dictionary.  Otherwise, the attribute is set or deleted in the
     object's *note __dict__: c04. (if present).  On success, ‘0’ is
     returned, otherwise an *note AttributeError: 2f6. is raised and
     ‘-1’ is returned.

 -- C 函式: int PyObject_DelAttr (PyObject *o, PyObject *attr_name)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Delete
     attribute named 'attr_name', for object 'o'.  Returns ‘-1’ on
     failure.  This is the equivalent of the Python statement ‘del
     o.attr_name’.

 -- C 函式: int PyObject_DelAttrString (PyObject *o, const char
          *attr_name)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  This is the
     same as *note PyObject_DelAttr(): 161a, but 'attr_name' is
     specified as a const char* UTF-8 encoded bytes string, rather than
     a *note PyObject: 311.*.

     The number of different attribute names passed to this function
     should be kept small, usually by using a statically allocated
     string as 'attr_name'.  For attribute names that aren't known at
     compile time, prefer calling *note PyUnicode_FromString(): 4748.
     and *note PyObject_DelAttr(): 161a. directly.  For more details,
     see *note PyUnicode_InternFromString(): 14f2, which may be used
     internally to create a key object for lookup.

 -- C 函式: *note PyObject: 311. *PyObject_GenericGetDict (PyObject *o,
          void *context)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本
     開始.'  A generic implementation for the getter of a ‘__dict__’
     descriptor.  It creates the dictionary if necessary.

     This function may also be called to get the *note __dict__: c04. of
     the object 'o'.  Pass ‘NULL’ for 'context' when calling it.  Since
     this function may need to allocate memory for the dictionary, it
     may be more efficient to call *note PyObject_GetAttr(): 2f4. when
     accessing an attribute on the object.

     在失敗時，會回傳 ‘NULL’ 並設定例外。

     在 3.3 版被加入.

 -- C 函式: int PyObject_GenericSetDict (PyObject *o, PyObject *value,
          void *context)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  A generic
     implementation for the setter of a ‘__dict__’ descriptor.  This
     implementation does not allow the dictionary to be deleted.

     在 3.3 版被加入.

 -- C 函式: *note PyObject: 311. **_PyObject_GetDictPtr (PyObject *obj)

     Return a pointer to *note __dict__: c04. of the object 'obj'.  If
     there is no ‘__dict__’, return ‘NULL’ without setting an exception.

     This function may need to allocate memory for the dictionary, so it
     may be more efficient to call *note PyObject_GetAttr(): 2f4. when
     accessing an attribute on the object.

 -- C 函式: *note PyObject: 311. *PyObject_RichCompare (PyObject *o1,
          PyObject *o2, int opid)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Compare
     the values of 'o1' and 'o2' using the operation specified by
     'opid', which must be one of *note Py_LT: 4968, *note Py_LE: 4969,
     *note Py_EQ: 496a, *note Py_NE: 496b, *note Py_GT: 496c, or *note
     Py_GE: 496d, corresponding to ‘<’, ‘<=’, ‘==’, ‘!=’, ‘>’, or ‘>=’
     respectively.  This is the equivalent of the Python expression ‘o1
     op o2’, where ‘op’ is the operator corresponding to 'opid'.
     Returns the value of the comparison on success, or ‘NULL’ on
     failure.

 -- C 函式: int PyObject_RichCompareBool (PyObject *o1, PyObject *o2,
          int opid)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Compare the values of 'o1' and
     'o2' using the operation specified by 'opid', like *note
     PyObject_RichCompare(): 4726, but returns ‘-1’ on error, ‘0’ if the
     result is false, ‘1’ otherwise.

     備註: If 'o1' and 'o2' are the same object, *note
     PyObject_RichCompareBool(): 18a7. will always return ‘1’ for *note
     Py_EQ: 496a. and ‘0’ for *note Py_NE: 496b.

 -- C 函式: *note PyObject: 311. *PyObject_Format (PyObject *obj,
          PyObject *format_spec)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Format 'obj' using
     'format_spec'.  This is equivalent to the Python expression
     ‘format(obj, format_spec)’.

     'format_spec' may be ‘NULL’.  In this case the call is equivalent
     to ‘format(obj)’.  Returns the formatted string on success, ‘NULL’
     on failure.

 -- C 函式: *note PyObject: 311. *PyObject_Repr (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

     Compute a string representation of object 'o'.  Returns the string
     representation on success, ‘NULL’ on failure.  This is the
     equivalent of the Python expression ‘repr(o)’.  Called by the *note
     repr(): 7a1. built-in function.

     在 3.4 版的變更: This function now includes a debug assertion to
     help ensure that it does not silently discard an active exception.

 -- C 函式: *note PyObject: 311. *PyObject_ASCII (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

     As *note PyObject_Repr(): fd2, compute a string representation of
     object 'o', but escape the non-ASCII characters in the string
     returned by *note PyObject_Repr(): fd2. with ‘\x’, ‘\u’ or ‘\U’
     escapes.  This generates a string similar to that returned by *note
     PyObject_Repr(): fd2. in Python 2.  Called by the *note ascii():
     1354. built-in function.

 -- C 函式: *note PyObject: 311. *PyObject_Str (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Compute a
     string representation of object 'o'.  Returns the string
     representation on success, ‘NULL’ on failure.  This is the
     equivalent of the Python expression ‘str(o)’.  Called by the *note
     str(): 3f2. built-in function and, therefore, by the *note print():
     f18. function.

     在 3.4 版的變更: This function now includes a debug assertion to
     help ensure that it does not silently discard an active exception.

 -- C 函式: *note PyObject: 311. *PyObject_Bytes (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

     Compute a bytes representation of object 'o'.  ‘NULL’ is returned
     on failure and a bytes object on success.  This is equivalent to
     the Python expression ‘bytes(o)’, when 'o' is not an integer.
     Unlike ‘bytes(o)’, a TypeError is raised when 'o' is an integer
     instead of a zero-initialized bytes object.

 -- C 函式: int PyObject_IsSubclass (PyObject *derived, PyObject *cls)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return ‘1’ if the class
     'derived' is identical to or derived from the class 'cls',
     otherwise return ‘0’.  In case of an error, return ‘-1’.

     If 'cls' is a tuple, the check will be done against every entry in
     'cls'.  The result will be ‘1’ when at least one of the checks
     returns ‘1’, otherwise it will be ‘0’.

     If 'cls' has a *note __subclasscheck__(): 1e54. method, it will be
     called to determine the subclass status as described in PEP
     3119(1).  Otherwise, 'derived' is a subclass of 'cls' if it is a
     direct or indirect subclass, i.e.  contained in ‘cls.__mro__’.

     Normally only class objects, i.e.  instances of *note type: cef. or
     a derived class, are considered classes.  However, objects can
     override this by having a *note __bases__: 1417. attribute (which
     must be a tuple of base classes).

 -- C 函式: int PyObject_IsInstance (PyObject *inst, PyObject *cls)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return ‘1’ if 'inst' is an
     instance of the class 'cls' or a subclass of 'cls', or ‘0’ if not.
     On error, returns ‘-1’ and sets an exception.

     If 'cls' is a tuple, the check will be done against every entry in
     'cls'.  The result will be ‘1’ when at least one of the checks
     returns ‘1’, otherwise it will be ‘0’.

     If 'cls' has a *note __instancecheck__(): 1e53. method, it will be
     called to determine the subclass status as described in PEP
     3119(2).  Otherwise, 'inst' is an instance of 'cls' if its class is
     a subclass of 'cls'.

     An instance 'inst' can override what is considered its class by
     having a *note __class__: 1418. attribute.

     An object 'cls' can override if it is considered a class, and what
     its base classes are, by having a *note __bases__: 1417. attribute
     (which must be a tuple of base classes).

 -- C 函式: *note Py_hash_t: 11fc. PyObject_Hash (PyObject *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     Compute and return the hash value of an object 'o'.  On failure,
     return ‘-1’.  This is the equivalent of the Python expression
     ‘hash(o)’.

     在 3.2 版的變更: The return type is now Py_hash_t.  This is a
     signed integer the same size as *note Py_ssize_t: a03.

 -- C 函式: *note Py_hash_t: 11fc. PyObject_HashNotImplemented (PyObject
          *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Set a *note TypeError: 4dd.
     indicating that ‘type(o)’ is not *note hashable: 5b5. and return
     ‘-1’.  This function receives special treatment when stored in a
     ‘tp_hash’ slot, allowing a type to explicitly indicate to the
     interpreter that it is not hashable.

 -- C 函式: int PyObject_IsTrue (PyObject *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns ‘1’ if the object 'o'
     is considered to be true, and ‘0’ otherwise.  This is equivalent to
     the Python expression ‘not not o’.  On failure, return ‘-1’.

 -- C 函式: int PyObject_Not (PyObject *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns ‘0’ if the object 'o'
     is considered to be true, and ‘1’ otherwise.  This is equivalent to
     the Python expression ‘not o’.  On failure, return ‘-1’.

 -- C 函式: *note PyObject: 311. *PyObject_Type (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

     When 'o' is non-‘NULL’, returns a type object corresponding to the
     object type of object 'o'.  On failure, raises *note SystemError:
     51b. and returns ‘NULL’.  This is equivalent to the Python
     expression ‘type(o)’.  This function creates a new *note strong
     reference: 2ee. to the return value.  There's really no reason to
     use this function instead of the *note Py_TYPE(): 724. function,
     which returns a pointer of type *note PyTypeObject: a48.*, except
     when a new *note strong reference: 2ee. is needed.

 -- C 函式: int PyObject_TypeCheck (PyObject *o, PyTypeObject *type)

     Return non-zero if the object 'o' is of type 'type' or a subtype of
     'type', and ‘0’ otherwise.  Both parameters must be non-‘NULL’.

 -- C 函式: *note Py_ssize_t: a03. PyObject_Size (PyObject *o)
 -- C 函式: *note Py_ssize_t: a03. PyObject_Length (PyObject *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     Return the length of object 'o'.  If the object 'o' provides either
     the sequence and mapping protocols, the sequence length is
     returned.  On error, ‘-1’ is returned.  This is the equivalent to
     the Python expression ‘len(o)’.

 -- C 函式: *note Py_ssize_t: a03. PyObject_LengthHint (PyObject *o,
          Py_ssize_t defaultvalue)

     Return an estimated length for the object 'o'.  First try to return
     its actual length, then an estimate using *note __length_hint__():
     eaf, and finally return the default value.  On error return ‘-1’.
     This is the equivalent to the Python expression
     ‘operator.length_hint(o, defaultvalue)’.

     在 3.4 版被加入.

 -- C 函式: *note PyObject: 311. *PyObject_GetItem (PyObject *o,
          PyObject *key)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return
     element of 'o' corresponding to the object 'key' or ‘NULL’ on
     failure.  This is the equivalent of the Python expression ‘o[key]’.

 -- C 函式: int PyObject_SetItem (PyObject *o, PyObject *key, PyObject
          *v)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Map the object 'key' to the
     value 'v'.  Raise an exception and return ‘-1’ on failure; return
     ‘0’ on success.  This is the equivalent of the Python statement
     ‘o[key] = v’.  This function 'does not' steal a reference to 'v'.

 -- C 函式: int PyObject_DelItem (PyObject *o, PyObject *key)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Remove the mapping for the
     object 'key' from the object 'o'.  Return ‘-1’ on failure.  This is
     equivalent to the Python statement ‘del o[key]’.

 -- C 函式: *note PyObject: 311. *PyObject_Dir (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  This is
     equivalent to the Python expression ‘dir(o)’, returning a (possibly
     empty) list of strings appropriate for the object argument, or
     ‘NULL’ if there was an error.  If the argument is ‘NULL’, this is
     like the Python ‘dir()’, returning the names of the current locals;
     in this case, if no execution frame is active then ‘NULL’ is
     returned but *note PyErr_Occurred(): 17f4. will return false.

 -- C 函式: *note PyObject: 311. *PyObject_GetIter (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  This is
     equivalent to the Python expression ‘iter(o)’.  It returns a new
     iterator for the object argument, or the object itself if the
     object is already an iterator.  Raises *note TypeError: 4dd. and
     returns ‘NULL’ if the object cannot be iterated.

 -- C 函式: *note PyObject: 311. *PyObject_GetAIter (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本
     開始.'  This is the equivalent to the Python expression ‘aiter(o)’.
     Takes an ‘AsyncIterable’ object and returns an ‘AsyncIterator’ for
     it.  This is typically a new iterator but if the argument is an
     ‘AsyncIterator’, this returns itself.  Raises *note TypeError: 4dd.
     and returns ‘NULL’ if the object cannot be iterated.

     在 3.10 版被加入.

 -- C 函式: void *PyObject_GetTypeData (PyObject *o, PyTypeObject *cls)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.12 版本開始.'  Get a
     pointer to subclass-specific data reserved for 'cls'.

     The object 'o' must be an instance of 'cls', and 'cls' must have
     been created using negative *note PyType_Spec.basicsize: 4ee.
     Python does not check this.

     On error, set an exception and return ‘NULL’.

     在 3.12 版被加入.

 -- C 函式: *note Py_ssize_t: a03. PyType_GetTypeDataSize (PyTypeObject
          *cls)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.12 版本開始.'  Return the
     size of the instance memory space reserved for 'cls', i.e.  the
     size of the memory *note PyObject_GetTypeData(): 4ef. returns.

     This may be larger than requested using *note
     -PyType_Spec.basicsize: 4ee.; it is safe to use this larger size
     (e.g.  with ‘memset()’).

     The type 'cls' 'must' have been created using negative *note
     PyType_Spec.basicsize: 4ee.  Python does not check this.

     On error, set an exception and return a negative value.

     在 3.12 版被加入.

 -- C 函式: void *PyObject_GetItemData (PyObject *o)

     Get a pointer to per-item data for a class with *note
     Py_TPFLAGS_ITEMS_AT_END: 4f1.

     On error, set an exception and return ‘NULL’.  *note TypeError:
     4dd. is raised if 'o' does not have *note Py_TPFLAGS_ITEMS_AT_END:
     4f1. set.

     在 3.12 版被加入.

 -- C 函式: int PyObject_VisitManagedDict (PyObject *obj, visitproc
          visit, void *arg)

     Visit the managed dictionary of 'obj'.

     This function must only be called in a traverse function of the
     type which has the *note Py_TPFLAGS_MANAGED_DICT: 31b. flag set.

     在 3.13 版被加入.

 -- C 函式: void PyObject_ClearManagedDict (PyObject *obj)

     Clear the managed dictionary of 'obj'.

     This function must only be called in a traverse function of the
     type which has the *note Py_TPFLAGS_MANAGED_DICT: 31b. flag set.

     在 3.13 版被加入.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3119/

   (2) https://peps.python.org/pep-3119/


File: python.info,  Node: 呼叫協定 Call Protocol,  Next: 數字協定,  Prev: 物件協定,  Up: 抽象物件層 Abstract Objects Layer

7.7.2 呼叫協定 (Call Protocol)
------------------------------

CPython 支援兩種不同的呼叫協定：'tp_call' 和 vectorcall（向量呼叫）。

* Menu:

* tp_call 協定::
* Vectorcall 協定::
* 物件呼叫 API::
* 呼叫支援 API::


File: python.info,  Node: tp_call 協定,  Next: Vectorcall 協定,  Up: 呼叫協定 Call Protocol

7.7.2.1 'tp_call' 協定
......................

設定 *note tp_call: 4ff. 的類別之實例都是可呼叫的。該擴充槽 (slot) 的簽
章為：

     PyObject *tp_call(PyObject *callable, PyObject *args, PyObject *kwargs);

要達成一個呼叫會使用一個 tuple（元組）表示位置引數、一個 dict 表示關鍵字
引數，類似於 Python 程式碼中的 ‘callable(*args, **kwargs)’。'args' 必須
不為 NULL（如果沒有引數，會使用一個空 tuple），但如果沒有關鍵字引數，
'kwargs' 可以是 'NULL'。

這個慣例不僅會被 'tp_call' 使用，*note tp_new: 525. 和 *note tp_init:
527. 也這樣傳遞引數。

使用 *note PyObject_Call(): 363. 或其他*note 呼叫 API: 4971. 來呼叫一個
物件。


File: python.info,  Node: Vectorcall 協定,  Next: 物件呼叫 API,  Prev: tp_call 協定,  Up: 呼叫協定 Call Protocol

7.7.2.2 Vectorcall 協定
.......................

在 3.9 版被加入.

Vectorcall 協定是在 PEP 590(1) 被引入的，它是使函式呼叫更加有效率的附加
協定。

經驗法則上，如果可呼叫物件有支援，CPython 於內部呼叫中會更傾向使用
vectorcall。然而，這並不是一個硬性規定。此外，有些第三方擴充套件會直接使
用 'tp_call'（而不是使用 *note PyObject_Call(): 363.）。因此，一個支援
vectorcall 的類別也必須實作 *note tp_call: 4ff.。此外，無論使用哪種協定
，可呼叫物件的行為都必須是相同的。要達成這個目的的推薦做法是將 *note
tp_call: 4ff. 設定為 *note PyVectorcall_Call(): 4fc.。這值得一再提醒：

     警告: 一個支援 vectorcall 的類別'必須'也實作具有相同語義的 *note
     tp_call: 4ff.。

在 3.12 版的變更: The *note Py_TPFLAGS_HAVE_VECTORCALL: 4fa. flag is now
removed from a class when the class's *note __call__(): 4fe. method is
reassigned.  (This internally sets *note tp_call: 4ff. only, and thus
may make it behave differently than the vectorcall function.)  In
earlier Python versions, vectorcall should only be used with *note
immutable: 38d. or static types.

如果一個類別的 vectorcall 比 'tp_call' 慢，就不應該實作 vectorcall。例如
，如果被呼叫者需要將引數轉換為 args tuple（引數元組）和 kwargs dict（關
鍵字引數字典），那麼實作 vectorcall 就沒有意義。

類別可以透過啟用 *note Py_TPFLAGS_HAVE_VECTORCALL: 4fa. 旗標並將 *note
tp_vectorcall_offset: 4973. 設定為物件結構中有出現 'vectorcallfunc' 的
offset 來實作 vectorcall 協定。這是一個指向具有以下簽章之函式的指標：

 -- C 型別: typedef *note PyObject: 311. *(*vectorcallfunc)(*note
          PyObject: 311. *callable, *note PyObject: 311. *const *args,
          size_t nargsf, *note PyObject: 311. *kwnames)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.12 版本開始.'

   - 'callable' 是指被呼叫的物件。

   - 
     'args' 是一個 C 語言陣列 (array)，包含位置引數與後面

          關鍵字引數的值。如果沒有引數，這個值可以是 'NULL'。

   - 
     'nargsf' 是位置引數的數量加上可能會有的

          *note PY_VECTORCALL_ARGUMENTS_OFFSET: 503. 旗標。如果要從
          'nargsf' 獲得實際的位置引數數量，請使用 *note
          PyVectorcall_NARGS(): 4fb.。

   - 
     'kwnames' 是一個包含所有關鍵字引數名稱的 tuple；

          換句話說，就是 kwargs 字典的鍵。這些名字必須是字串（‘str’ 或其
          子類別的實例)，並且它們必須是不重複的。如果沒有關鍵字引數，那
          麼 'kwnames' 可以用 'NULL' 代替。

 -- C 巨集: PY_VECTORCALL_ARGUMENTS_OFFSET
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.12 版本開始.'  如果在
     vectorcall 的 'nargsf' 引數中設定了此旗標，則允許被呼叫者臨時更改
     ‘args[-1]’ 的值。換句話說，'args' 指向向量中的引數 1（不是 0）。被
     呼叫方必須在回傳之前還原 ‘args[-1]’ 的值。

     對於 *note PyObject_VectorcallMethod(): 502.，這個旗標的改變意味著
     可能是 ‘args[0]’ 被改變。

     當可以以幾乎無代價的方式（無需佔據額外的記憶體）來達成，那麼會推薦
     呼叫者使用 *note PY_VECTORCALL_ARGUMENTS_OFFSET: 503.。這樣做會讓如
     bound method（繫結方法）之類的可呼叫函式非常有效地繼續向前呼叫（這
     類函式包含一個在首位的 'self' 引數）。

     在 3.8 版被加入.

要呼叫一個實作了 vectorcall 的物件，請就像其他可呼叫物件一樣使用*note
呼叫 API: 4971. 中的函式。*note PyObject_Vectorcall(): 501. 通常是最有效
率的。

* Menu:

* 遞迴控制::
* Vectorcall 支援 API::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0590/


File: python.info,  Node: 遞迴控制,  Next: Vectorcall 支援 API,  Up: Vectorcall 協定

7.7.2.3 遞迴控制
................

在使用 'tp_call' 時，被呼叫者不必擔心*note 遞迴: 490d.：CPython 對於使用
'tp_call' 的呼叫會使用 *note Py_EnterRecursiveCall(): 917. 和 *note
Py_LeaveRecursiveCall(): 918.。

為保證效率，這不適用於使用 vectorcall 的呼叫：被呼叫方在需要時應當使用
'Py_EnterRecursiveCall' 和 'Py_LeaveRecursiveCall'。


File: python.info,  Node: Vectorcall 支援 API,  Prev: 遞迴控制,  Up: Vectorcall 協定

7.7.2.4 Vectorcall 支援 API
...........................

 -- C 函式: *note Py_ssize_t: a03. PyVectorcall_NARGS (size_t nargsf)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.12 版本開始.'  給定一個
     vectorcall 'nargsf' 引數，回傳引數的實際數量。目前等同於：

          (Py_ssize_t)(nargsf & ~PY_VECTORCALL_ARGUMENTS_OFFSET)

     然而，應使用 ‘PyVectorcall_NARGS’ 函式以便將來需要擴充。

     在 3.8 版被加入.

 -- C 函式: *note vectorcallfunc: 4fd. PyVectorcall_Function (PyObject
          *op)

     如果 'op' 不支援 vectorcall 協定（因為型別不支援或特定實例不支援）
     ，就回傳 'NULL'。否則，回傳儲存在 'op' 中的 vectorcall 函式指標。這
     個函式不會引發例外。

     這大多在檢查 'op' 是否支援 vectorcall 時能派上用場，可以透過檢查
     ‘PyVectorcall_Function(op) != NULL’ 來達成。

     在 3.9 版被加入.

 -- C 函式: *note PyObject: 311. *PyVectorcall_Call (PyObject *callable,
          PyObject *tuple, PyObject *dict)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.12 版本開始.'  呼叫
     'callable' 的 *note vectorcallfunc: 4fd.，其位置引數和關鍵字引數分
     別以 tuple 和 dict 格式給定。

     這是一個專門函式，其目的是被放入 *note tp_call: 4ff. 擴充槽或是用於
     ‘tp_call’ 的實作。它不會檢查 *note Py_TPFLAGS_HAVE_VECTORCALL: 4fa.
     旗標並且它不會退回 (fall back) 使用 ‘tp_call’。

     在 3.8 版被加入.


File: python.info,  Node: 物件呼叫 API,  Next: 呼叫支援 API,  Prev: Vectorcall 協定,  Up: 呼叫協定 Call Protocol

7.7.2.5 物件呼叫 API
....................

有多個函式可被用來呼叫 Python 物件。各個函式會將其引數轉換為被呼叫物件所
支援的慣用形式 – 可以是 'tp_call' 或 vectorcall。為了儘可能減少轉換的進
行，請選擇一個適合你所擁有資料格式的函式。

下表總結了可用的函式；請參閱各個說明文件以瞭解詳情。

函式                                           callable               args                     kwargs
                                                                                               
-------------------------------------------------------------------------------------------------------------------
                                                                                               
*note PyObject_Call(): 363.                    ‘PyObject *’           tuple                    dict/‘NULL’
                                                                                               
                                                                                               
*note PyObject_CallNoArgs(): 362.              ‘PyObject *’           --                       --
                                                                                               
                                                                                               
*note PyObject_CallOneArg(): 91c.              ‘PyObject *’           一個物件                 --
                                                                                               
                                                                                               
*note PyObject_CallObject(): 46e2.             ‘PyObject *’           tuple/‘NULL’             --
                                                                                               
                                                                                               
*note PyObject_CallFunction(): 365.            ‘PyObject *’           format                   --
                                                                                               
                                                                                               
*note PyObject_CallMethod(): 366.              物件 + ‘char*’         format                   --
                                                                                               
                                                                                               
*note PyObject_CallFunctionObjArgs(): 4836.    ‘PyObject *’           可變引數                 --
                                                                                               
                                                                                               
*note PyObject_CallMethodObjArgs(): 1902.      物件 + 名稱            可變引數                 --
                                                                                               
                                                                                               
*note PyObject_CallMethodNoArgs(): 4978.       物件 + 名稱            --                       --
                                                                                               
                                                                                               
*note PyObject_CallMethodOneArg(): 4979.       物件 + 名稱            一個物件                 --
                                                                                               
                                                                                               
*note PyObject_Vectorcall(): 501.              ‘PyObject *’           vectorcall               vectorcall
                                                                                               
                                                                                               
*note PyObject_VectorcallDict(): 497a.         ‘PyObject *’           vectorcall               dict/‘NULL’
                                                                                               
                                                                                               
*note PyObject_VectorcallMethod(): 502.        引數 + 名稱            vectorcall               vectorcall
                                                                                               

 -- C 函式: *note PyObject: 311. *PyObject_Call (PyObject *callable,
          PyObject *args, PyObject *kwargs)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  呼叫一個可
     呼叫的 Python 物件 'callable'，附帶由 tuple 'args' 所給定的引數及由
     字典 'kwargs' 所給定的關鍵字引數。

     'args' 必須不為 'NULL'；如果不需要引數，請使用一個空 tuple。如果不
     需要關鍵字引數，則 'kwargs' 可以為 'NULL'。

     成功時回傳結果，或在失敗時引發一個例外並回傳 'NULL'。

     這等價於 Python 運算式 ‘callable(*args, **kwargs)’。

 -- C 函式: *note PyObject: 311. *PyObject_CallNoArgs (PyObject
          *callable)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本
     開始.'  呼叫一個可呼叫的 Python 物件 'callable' 並不附帶任何引數。
     這是不帶引數呼叫 Python 可呼叫物件的最有效方式。

     成功時回傳結果，或在失敗時引發一個例外並回傳 'NULL'。

     在 3.9 版被加入.

 -- C 函式: *note PyObject: 311. *PyObject_CallOneArg (PyObject
          *callable, PyObject *arg)
     '回傳值：新的參照。' 呼叫一個可呼叫的 Python 物件 'callable' 並附帶
     正好一個位置引數 'arg' 而沒有關鍵字引數。

     成功時回傳結果，或在失敗時引發一個例外並回傳 'NULL'。

     在 3.9 版被加入.

 -- C 函式: *note PyObject: 311. *PyObject_CallObject (PyObject
          *callable, PyObject *args)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  呼叫一個可
     呼叫的 Python 物件 'callable'，附帶由 tuple 'args' 所給定的引數。如
     果不需要傳入引數，則 'args' 可以為 'NULL'。

     成功時回傳結果，或在失敗時引發一個例外並回傳 'NULL'。

     這等價於 Python 運算式 ‘callable(*args)’。

 -- C 函式: *note PyObject: 311. *PyObject_CallFunction (PyObject
          *callable, const char *format, ...)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  呼叫一個可
     呼叫的 Python 物件 'callable'，附帶數量可變的 C 引數。這些 C 引數使
     用 *note Py_BuildValue(): 84c. 風格的格式字串來描述。格式可以為
     'NULL'，表示沒有提供任何引數。

     成功時回傳結果，或在失敗時引發一個例外並回傳 'NULL'。

     這等價於 Python 運算式 ‘callable(*args)’。

     注意，如果你只傳入 *note PyObject: 311.* 引數，則 *note
     PyObject_CallFunctionObjArgs(): 4836. 是另一個更快速的選擇。

     在 3.4 版的變更: 這個 'format' 的型別已從 ‘char *’ 更改。

 -- C 函式: *note PyObject: 311. *PyObject_CallMethod (PyObject *obj,
          const char *name, const char *format, ...)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  呼叫 'obj'
     物件中名為 'name' 的 method 並附帶數量可變的 C 引數。這些 C 引數由
     *note Py_BuildValue(): 84c. 格式字串來描述，並應當生成一個 tuple。

     格式可以為 'NULL'，表示沒有提供任何引數。

     成功時回傳結果，或在失敗時引發一個例外並回傳 'NULL'。

     這等價於 Python 運算式 ‘obj.name(arg1, arg2, ...)’。

     注意，如果你只傳入 *note PyObject: 311.* 引數，則 *note
     PyObject_CallMethodObjArgs(): 1902. 是另一個更快速的選擇。

     在 3.4 版的變更: 'name' 和 'format' 的型別已從 ‘char *’ 更改。

 -- C 函式: *note PyObject: 311. *PyObject_CallFunctionObjArgs (PyObject
          *callable, ...)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  呼叫一個可
     呼叫的 Python 物件 'callable'，附帶數量可變的 *note PyObject: 311.*
     引數。這些引數是以位置在 'NULL' 後面、數量可變的參數來提供。

     成功時回傳結果，或在失敗時引發一個例外並回傳 'NULL'。

     這等價於 Python 運算式 ‘callable(arg1, arg2, ...)’。

 -- C 函式: *note PyObject: 311. *PyObject_CallMethodObjArgs (PyObject
          *obj, PyObject *name, ...)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  呼叫
     Python 物件 'obj' 中的一個 method，其中 method 名稱由 'name' 中的
     Python 字串物件給定。被呼叫時會附帶數量可變的 *note PyObject: 311.*
     引數。這些引數是以位置在 'NULL' 後面、且數量可變的參數來提供。

     成功時回傳結果，或在失敗時引發一個例外並回傳 'NULL'。

 -- C 函式: *note PyObject: 311. *PyObject_CallMethodNoArgs (PyObject
          *obj, PyObject *name)

     不附帶任何引數地呼叫 Python 物件 'obj' 中的一個 method，其中 method
     名稱由 'name' 中的 Python 字串物件給定。

     成功時回傳結果，或在失敗時引發一個例外並回傳 'NULL'。

     在 3.9 版被加入.

 -- C 函式: *note PyObject: 311. *PyObject_CallMethodOneArg (PyObject
          *obj, PyObject *name, PyObject *arg)

     附帶一個位置引數 'arg' 地呼叫 Python 物件 'obj' 中的一個 method，其
     中 method 名稱由 'name' 中的 Python 字串物件給定。

     成功時回傳結果，或在失敗時引發一個例外並回傳 'NULL'。

     在 3.9 版被加入.

 -- C 函式: *note PyObject: 311. *PyObject_Vectorcall (PyObject
          *callable, PyObject *const *args, size_t nargsf, PyObject
          *kwnames)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.12 版本開始.'  呼叫一個可呼
     叫的 Python 物件 'callable'。附帶引數與 *note vectorcallfunc: 4fd.
     的相同。如果 'callable' 支援 *note vectorcall: 4f8.，則它會直接呼叫
     存放在 'callable' 中的 vectorcall 函式。

     成功時回傳結果，或在失敗時引發一個例外並回傳 'NULL'。

     在 3.9 版被加入.

 -- C 函式: *note PyObject: 311. *PyObject_VectorcallDict (PyObject
          *callable, PyObject *const *args, size_t nargsf, PyObject
          *kwdict)

     附帶與在 *note vectorcall: 4f8. 協定中傳入的相同位置引數來呼叫
     'callable'，但會加上以字典 'kwdict' 格式傳入的關鍵字引數。'args' 陣
     列將只包含位置引數。

     無論內部使用了哪一種協定，都會需要進行引數的轉換。因此，此函式應該
     只有在呼叫方已經擁有一個要作為關鍵字引數的字典、但沒有作為位置引數
     的 tuple 時才被使用。

     在 3.9 版被加入.

 -- C 函式: *note PyObject: 311. *PyObject_VectorcallMethod (PyObject
          *name, PyObject *const *args, size_t nargsf, PyObject
          *kwnames)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.12 版本開始.'  使用
     vectorcall 呼叫慣例來呼叫一個 method。method 的名稱以 Python 字串
     'name' 的格式給定。被呼叫 method 的物件為 'args[0]'，而 'args' 陣列
     從 'args[1]' 開始的部分則代表呼叫的引數。必須傳入至少一個位置引數。
     'nargsf' 為包括 'args[0]' 在內的位置引數的數量，如果 ‘args[0]’ 的值
     可能被臨時改變則要再加上 *note PY_VECTORCALL_ARGUMENTS_OFFSET:
     503.。關鍵字引數可以像在 *note PyObject_Vectorcall(): 501. 中一樣被
     傳入。

     如果物件具有 *note Py_TPFLAGS_METHOD_DESCRIPTOR: 497b. 特性，這將以
     完整的 'args' 向量作為引數來呼叫 unbound method（未繫結方法）物件。

     成功時回傳結果，或在失敗時引發一個例外並回傳 'NULL'。

     在 3.9 版被加入.


File: python.info,  Node: 呼叫支援 API,  Prev: 物件呼叫 API,  Up: 呼叫協定 Call Protocol

7.7.2.6 呼叫支援 API
....................

 -- C 函式: int PyCallable_Check (PyObject *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  判定物件 'o' 是否為可呼叫的。
     如果物件是可呼叫物件則回傳 ‘1’，其他情況回傳 ‘0’。這個函式不會呼叫
     失敗。


File: python.info,  Node: 數字協定,  Next: 序列協定,  Prev: 呼叫協定 Call Protocol,  Up: 抽象物件層 Abstract Objects Layer

7.7.3 數字協定
--------------

 -- C 函式: int PyNumber_Check (PyObject *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns ‘1’ if the object 'o'
     provides numeric protocols, and false otherwise.  This function
     always succeeds.

     在 3.8 版的變更: Returns ‘1’ if 'o' is an index integer.

 -- C 函式: *note PyObject: 311. *PyNumber_Add (PyObject *o1, PyObject
          *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the result of adding 'o1' and 'o2', or ‘NULL’ on failure.  This is
     the equivalent of the Python expression ‘o1 + o2’.

 -- C 函式: *note PyObject: 311. *PyNumber_Subtract (PyObject *o1,
          PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the result of subtracting 'o2' from 'o1', or ‘NULL’ on failure.
     This is the equivalent of the Python expression ‘o1 - o2’.

 -- C 函式: *note PyObject: 311. *PyNumber_Multiply (PyObject *o1,
          PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the result of multiplying 'o1' and 'o2', or ‘NULL’ on failure.
     This is the equivalent of the Python expression ‘o1 * o2’.

 -- C 函式: *note PyObject: 311. *PyNumber_MatrixMultiply (PyObject *o1,
          PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本
     開始.'  Returns the result of matrix multiplication on 'o1' and
     'o2', or ‘NULL’ on failure.  This is the equivalent of the Python
     expression ‘o1 @ o2’.

     在 3.5 版被加入.

 -- C 函式: *note PyObject: 311. *PyNumber_FloorDivide (PyObject *o1,
          PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the
     floor of 'o1' divided by 'o2', or ‘NULL’ on failure.  This is the
     equivalent of the Python expression ‘o1 // o2’.

 -- C 函式: *note PyObject: 311. *PyNumber_TrueDivide (PyObject *o1,
          PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     reasonable approximation for the mathematical value of 'o1' divided
     by 'o2', or ‘NULL’ on failure.  The return value is "approximate"
     because binary floating-point numbers are approximate; it is not
     possible to represent all real numbers in base two.  This function
     can return a floating-point value when passed two integers.  This
     is the equivalent of the Python expression ‘o1 / o2’.

 -- C 函式: *note PyObject: 311. *PyNumber_Remainder (PyObject *o1,
          PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the remainder of dividing 'o1' by 'o2', or ‘NULL’ on failure.  This
     is the equivalent of the Python expression ‘o1 % o2’.

 -- C 函式: *note PyObject: 311. *PyNumber_Divmod (PyObject *o1,
          PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

     See the built-in function *note divmod(): 945.  Returns ‘NULL’ on
     failure.  This is the equivalent of the Python expression
     ‘divmod(o1, o2)’.

 -- C 函式: *note PyObject: 311. *PyNumber_Power (PyObject *o1, PyObject
          *o2, PyObject *o3)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

     See the built-in function *note pow(): 976.  Returns ‘NULL’ on
     failure.  This is the equivalent of the Python expression ‘pow(o1,
     o2, o3)’, where 'o3' is optional.  If 'o3' is to be ignored, pass
     *note Py_None: 46d6. in its place (passing ‘NULL’ for 'o3' would
     cause an illegal memory access).

 -- C 函式: *note PyObject: 311. *PyNumber_Negative (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the negation of 'o' on success, or ‘NULL’ on failure.  This is the
     equivalent of the Python expression ‘-o’.

 -- C 函式: *note PyObject: 311. *PyNumber_Positive (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     'o' on success, or ‘NULL’ on failure.  This is the equivalent of
     the Python expression ‘+o’.

 -- C 函式: *note PyObject: 311. *PyNumber_Absolute (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

     Returns the absolute value of 'o', or ‘NULL’ on failure.  This is
     the equivalent of the Python expression ‘abs(o)’.

 -- C 函式: *note PyObject: 311. *PyNumber_Invert (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the bitwise negation of 'o' on success, or ‘NULL’ on failure.  This
     is the equivalent of the Python expression ‘~o’.

 -- C 函式: *note PyObject: 311. *PyNumber_Lshift (PyObject *o1,
          PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the result of left shifting 'o1' by 'o2' on success, or ‘NULL’ on
     failure.  This is the equivalent of the Python expression ‘o1 <<
     o2’.

 -- C 函式: *note PyObject: 311. *PyNumber_Rshift (PyObject *o1,
          PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the result of right shifting 'o1' by 'o2' on success, or ‘NULL’ on
     failure.  This is the equivalent of the Python expression ‘o1 >>
     o2’.

 -- C 函式: *note PyObject: 311. *PyNumber_And (PyObject *o1, PyObject
          *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the "bitwise and" of 'o1' and 'o2' on success and ‘NULL’ on
     failure.  This is the equivalent of the Python expression ‘o1 &
     o2’.

 -- C 函式: *note PyObject: 311. *PyNumber_Xor (PyObject *o1, PyObject
          *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the "bitwise exclusive or" of 'o1' by 'o2' on success, or ‘NULL’ on
     failure.  This is the equivalent of the Python expression ‘o1 ^
     o2’.

 -- C 函式: *note PyObject: 311. *PyNumber_Or (PyObject *o1, PyObject
          *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the "bitwise or" of 'o1' and 'o2' on success, or ‘NULL’ on failure.
     This is the equivalent of the Python expression ‘o1 | o2’.

 -- C 函式: *note PyObject: 311. *PyNumber_InPlaceAdd (PyObject *o1,
          PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the result of adding 'o1' and 'o2', or ‘NULL’ on failure.  The
     operation is done 'in-place' when 'o1' supports it.  This is the
     equivalent of the Python statement ‘o1 += o2’.

 -- C 函式: *note PyObject: 311. *PyNumber_InPlaceSubtract (PyObject
          *o1, PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the result of subtracting 'o2' from 'o1', or ‘NULL’ on failure.
     The operation is done 'in-place' when 'o1' supports it.  This is
     the equivalent of the Python statement ‘o1 -= o2’.

 -- C 函式: *note PyObject: 311. *PyNumber_InPlaceMultiply (PyObject
          *o1, PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the result of multiplying 'o1' and 'o2', or ‘NULL’ on failure.  The
     operation is done 'in-place' when 'o1' supports it.  This is the
     equivalent of the Python statement ‘o1 *= o2’.

 -- C 函式: *note PyObject: 311. *PyNumber_InPlaceMatrixMultiply
          (PyObject *o1, PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本
     開始.'  Returns the result of matrix multiplication on 'o1' and
     'o2', or ‘NULL’ on failure.  The operation is done 'in-place' when
     'o1' supports it.  This is the equivalent of the Python statement
     ‘o1 @= o2’.

     在 3.5 版被加入.

 -- C 函式: *note PyObject: 311. *PyNumber_InPlaceFloorDivide (PyObject
          *o1, PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the mathematical floor of dividing 'o1' by 'o2', or ‘NULL’ on
     failure.  The operation is done 'in-place' when 'o1' supports it.
     This is the equivalent of the Python statement ‘o1 //= o2’.

 -- C 函式: *note PyObject: 311. *PyNumber_InPlaceTrueDivide (PyObject
          *o1, PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     reasonable approximation for the mathematical value of 'o1' divided
     by 'o2', or ‘NULL’ on failure.  The return value is "approximate"
     because binary floating-point numbers are approximate; it is not
     possible to represent all real numbers in base two.  This function
     can return a floating-point value when passed two integers.  The
     operation is done 'in-place' when 'o1' supports it.  This is the
     equivalent of the Python statement ‘o1 /= o2’.

 -- C 函式: *note PyObject: 311. *PyNumber_InPlaceRemainder (PyObject
          *o1, PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the remainder of dividing 'o1' by 'o2', or ‘NULL’ on failure.  The
     operation is done 'in-place' when 'o1' supports it.  This is the
     equivalent of the Python statement ‘o1 %= o2’.

 -- C 函式: *note PyObject: 311. *PyNumber_InPlacePower (PyObject *o1,
          PyObject *o2, PyObject *o3)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

     See the built-in function *note pow(): 976.  Returns ‘NULL’ on
     failure.  The operation is done 'in-place' when 'o1' supports it.
     This is the equivalent of the Python statement ‘o1 **= o2’ when o3
     is *note Py_None: 46d6, or an in-place variant of ‘pow(o1, o2, o3)’
     otherwise.  If 'o3' is to be ignored, pass *note Py_None: 46d6. in
     its place (passing ‘NULL’ for 'o3' would cause an illegal memory
     access).

 -- C 函式: *note PyObject: 311. *PyNumber_InPlaceLshift (PyObject *o1,
          PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the result of left shifting 'o1' by 'o2' on success, or ‘NULL’ on
     failure.  The operation is done 'in-place' when 'o1' supports it.
     This is the equivalent of the Python statement ‘o1 <<= o2’.

 -- C 函式: *note PyObject: 311. *PyNumber_InPlaceRshift (PyObject *o1,
          PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the result of right shifting 'o1' by 'o2' on success, or ‘NULL’ on
     failure.  The operation is done 'in-place' when 'o1' supports it.
     This is the equivalent of the Python statement ‘o1 >>= o2’.

 -- C 函式: *note PyObject: 311. *PyNumber_InPlaceAnd (PyObject *o1,
          PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the "bitwise and" of 'o1' and 'o2' on success and ‘NULL’ on
     failure.  The operation is done 'in-place' when 'o1' supports it.
     This is the equivalent of the Python statement ‘o1 &= o2’.

 -- C 函式: *note PyObject: 311. *PyNumber_InPlaceXor (PyObject *o1,
          PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the "bitwise exclusive or" of 'o1' by 'o2' on success, or ‘NULL’ on
     failure.  The operation is done 'in-place' when 'o1' supports it.
     This is the equivalent of the Python statement ‘o1 ^= o2’.

 -- C 函式: *note PyObject: 311. *PyNumber_InPlaceOr (PyObject *o1,
          PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the "bitwise or" of 'o1' and 'o2' on success, or ‘NULL’ on failure.
     The operation is done 'in-place' when 'o1' supports it.  This is
     the equivalent of the Python statement ‘o1 |= o2’.

 -- C 函式: *note PyObject: 311. *PyNumber_Long (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

     Returns the 'o' converted to an integer object on success, or
     ‘NULL’ on failure.  This is the equivalent of the Python expression
     ‘int(o)’.

 -- C 函式: *note PyObject: 311. *PyNumber_Float (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

     Returns the 'o' converted to a float object on success, or ‘NULL’
     on failure.  This is the equivalent of the Python expression
     ‘float(o)’.

 -- C 函式: *note PyObject: 311. *PyNumber_Index (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the 'o' converted to a Python int on success or ‘NULL’ with a *note
     TypeError: 4dd. exception raised on failure.

     在 3.10 版的變更: The result always has exact type *note int: 23c.
     Previously, the result could have been an instance of a subclass of
     ‘int’.

 -- C 函式: *note PyObject: 311. *PyNumber_ToBase (PyObject *n, int
          base)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the integer 'n' converted to base 'base' as a string.  The 'base'
     argument must be one of 2, 8, 10, or 16.  For base 2, 8, or 16, the
     returned string is prefixed with a base marker of ‘'0b'’, ‘'0o'’,
     or ‘'0x'’, respectively.  If 'n' is not a Python int, it is
     converted with *note PyNumber_Index(): 837. first.

 -- C 函式: *note Py_ssize_t: a03. PyNumber_AsSsize_t (PyObject *o,
          PyObject *exc)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns 'o' converted to a
     *note Py_ssize_t: a03. value if 'o' can be interpreted as an
     integer.  If the call fails, an exception is raised and ‘-1’ is
     returned.

     If 'o' can be converted to a Python int but the attempt to convert
     to a *note Py_ssize_t: a03. value would raise an *note
     OverflowError: 825, then the 'exc' argument is the type of
     exception that will be raised (usually *note IndexError: 14a3. or
     *note OverflowError: 825.).  If 'exc' is ‘NULL’, then the exception
     is cleared and the value is clipped to ‘PY_SSIZE_T_MIN’ for a
     negative integer or ‘PY_SSIZE_T_MAX’ for a positive integer.

 -- C 函式: int PyIndex_Check (PyObject *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.8 版本開始.'  Returns ‘1’
     if 'o' is an index integer (has the ‘nb_index’ slot of the
     ‘tp_as_number’ structure filled in), and ‘0’ otherwise.  This
     function always succeeds.


File: python.info,  Node: 序列協定,  Next: 對映協定,  Prev: 數字協定,  Up: 抽象物件層 Abstract Objects Layer

7.7.4 序列協定
--------------

 -- C 函式: int PySequence_Check (PyObject *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return ‘1’ if the object
     provides the sequence protocol, and ‘0’ otherwise.  Note that it
     returns ‘1’ for Python classes with a *note __getitem__(): 266.
     method, unless they are *note dict: 23b. subclasses, since in
     general it is impossible to determine what type of keys the class
     supports.  This function always succeeds.

 -- C 函式: *note Py_ssize_t: a03. PySequence_Size (PyObject *o)
 -- C 函式: *note Py_ssize_t: a03. PySequence_Length (PyObject *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     Returns the number of objects in sequence 'o' on success, and ‘-1’
     on failure.  This is equivalent to the Python expression ‘len(o)’.

 -- C 函式: *note PyObject: 311. *PySequence_Concat (PyObject *o1,
          PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the
     concatenation of 'o1' and 'o2' on success, and ‘NULL’ on failure.
     This is the equivalent of the Python expression ‘o1 + o2’.

 -- C 函式: *note PyObject: 311. *PySequence_Repeat (PyObject *o,
          Py_ssize_t count)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the
     result of repeating sequence object 'o' 'count' times, or ‘NULL’ on
     failure.  This is the equivalent of the Python expression ‘o *
     count’.

 -- C 函式: *note PyObject: 311. *PySequence_InPlaceConcat (PyObject
          *o1, PyObject *o2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the
     concatenation of 'o1' and 'o2' on success, and ‘NULL’ on failure.
     The operation is done 'in-place' when 'o1' supports it.  This is
     the equivalent of the Python expression ‘o1 += o2’.

 -- C 函式: *note PyObject: 311. *PySequence_InPlaceRepeat (PyObject *o,
          Py_ssize_t count)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the
     result of repeating sequence object 'o' 'count' times, or ‘NULL’ on
     failure.  The operation is done 'in-place' when 'o' supports it.
     This is the equivalent of the Python expression ‘o *= count’.

 -- C 函式: *note PyObject: 311. *PySequence_GetItem (PyObject *o,
          Py_ssize_t i)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the
     'i'th element of 'o', or ‘NULL’ on failure.  This is the equivalent
     of the Python expression ‘o[i]’.

 -- C 函式: *note PyObject: 311. *PySequence_GetSlice (PyObject *o,
          Py_ssize_t i1, Py_ssize_t i2)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the
     slice of sequence object 'o' between 'i1' and 'i2', or ‘NULL’ on
     failure.  This is the equivalent of the Python expression
     ‘o[i1:i2]’.

 -- C 函式: int PySequence_SetItem (PyObject *o, Py_ssize_t i, PyObject
          *v)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Assign object 'v' to the 'i'th
     element of 'o'.  Raise an exception and return ‘-1’ on failure;
     return ‘0’ on success.  This is the equivalent of the Python
     statement ‘o[i] = v’.  This function 'does not' steal a reference
     to 'v'.

     If 'v' is ‘NULL’, the element is deleted, but this feature is
     deprecated in favour of using *note PySequence_DelItem(): 195b.

 -- C 函式: int PySequence_DelItem (PyObject *o, Py_ssize_t i)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Delete the 'i'th element of
     object 'o'.  Returns ‘-1’ on failure.  This is the equivalent of
     the Python statement ‘del o[i]’.

 -- C 函式: int PySequence_SetSlice (PyObject *o, Py_ssize_t i1,
          Py_ssize_t i2, PyObject *v)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Assign the sequence object 'v'
     to the slice in sequence object 'o' from 'i1' to 'i2'.  This is the
     equivalent of the Python statement ‘o[i1:i2] = v’.

 -- C 函式: int PySequence_DelSlice (PyObject *o, Py_ssize_t i1,
          Py_ssize_t i2)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Delete the slice in sequence
     object 'o' from 'i1' to 'i2'.  Returns ‘-1’ on failure.  This is
     the equivalent of the Python statement ‘del o[i1:i2]’.

 -- C 函式: *note Py_ssize_t: a03. PySequence_Count (PyObject *o,
          PyObject *value)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the number of
     occurrences of 'value' in 'o', that is, return the number of keys
     for which ‘o[key] == value’.  On failure, return ‘-1’.  This is
     equivalent to the Python expression ‘o.count(value)’.

 -- C 函式: int PySequence_Contains (PyObject *o, PyObject *value)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Determine if 'o' contains
     'value'.  If an item in 'o' is equal to 'value', return ‘1’,
     otherwise return ‘0’.  On error, return ‘-1’.  This is equivalent
     to the Python expression ‘value in o’.

 -- C 函式: *note Py_ssize_t: a03. PySequence_Index (PyObject *o,
          PyObject *value)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the first index 'i' for
     which ‘o[i] == value’.  On error, return ‘-1’.  This is equivalent
     to the Python expression ‘o.index(value)’.

 -- C 函式: *note PyObject: 311. *PySequence_List (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     list object with the same contents as the sequence or iterable 'o',
     or ‘NULL’ on failure.  The returned list is guaranteed to be new.
     This is equivalent to the Python expression ‘list(o)’.

 -- C 函式: *note PyObject: 311. *PySequence_Tuple (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

     Return a tuple object with the same contents as the sequence or
     iterable 'o', or ‘NULL’ on failure.  If 'o' is a tuple, a new
     reference will be returned, otherwise a tuple will be constructed
     with the appropriate contents.  This is equivalent to the Python
     expression ‘tuple(o)’.

 -- C 函式: *note PyObject: 311. *PySequence_Fast (PyObject *o, const
          char *m)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the
     sequence or iterable 'o' as an object usable by the other
     ‘PySequence_Fast*’ family of functions.  If the object is not a
     sequence or iterable, raises *note TypeError: 4dd. with 'm' as the
     message text.  Returns ‘NULL’ on failure.

     The ‘PySequence_Fast*’ functions are thus named because they assume
     'o' is a *note PyTupleObject: 491d. or a *note PyListObject: 4983.
     and access the data fields of 'o' directly.

     As a CPython implementation detail, if 'o' is already a sequence or
     list, it will be returned.

 -- C 函式: *note Py_ssize_t: a03. PySequence_Fast_GET_SIZE (PyObject
          *o)

     Returns the length of 'o', assuming that 'o' was returned by *note
     PySequence_Fast(): 484d. and that 'o' is not ‘NULL’.  The size can
     also be retrieved by calling *note PySequence_Size(): 1958. on 'o',
     but *note PySequence_Fast_GET_SIZE(): 4984. is faster because it
     can assume 'o' is a list or tuple.

 -- C 函式: *note PyObject: 311. *PySequence_Fast_GET_ITEM (PyObject *o,
          Py_ssize_t i)
     '回傳值：借用參照。' Return the 'i'th element of 'o', assuming that
     'o' was returned by *note PySequence_Fast(): 484d, 'o' is not
     ‘NULL’, and that 'i' is within bounds.

 -- C 函式: *note PyObject: 311. **PySequence_Fast_ITEMS (PyObject *o)

     Return the underlying array of PyObject pointers.  Assumes that 'o'
     was returned by *note PySequence_Fast(): 484d. and 'o' is not
     ‘NULL’.

     Note, if a list gets resized, the reallocation may relocate the
     items array.  So, only use the underlying array pointer in contexts
     where the sequence cannot change.

 -- C 函式: *note PyObject: 311. *PySequence_ITEM (PyObject *o,
          Py_ssize_t i)
     '回傳值：新的參照。' Return the 'i'th element of 'o' or ‘NULL’ on
     failure.  Faster form of *note PySequence_GetItem(): 1959. but
     without checking that *note PySequence_Check(): 4848. on 'o' is
     true and without adjustment for negative indices.


File: python.info,  Node: 對映協定,  Next: 疊代器協議,  Prev: 序列協定,  Up: 抽象物件層 Abstract Objects Layer

7.7.5 對映協定
--------------

另請參閱 *note PyObject_GetItem(): 2f9.、*note PyObject_SetItem(): 4764.
和 *note PyObject_DelItem(): 4837.。

 -- C 函式: int PyMapping_Check (PyObject *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  如果物件有提供對映協定或支援切
     片 (slicing) 則回傳 ‘1’，否則回傳 ‘0’。請注意，對於具有 *note
     __getitem__(): 266. 方法的 Python 類別，它會回傳 ‘1’，因為通常無法
     確定該類別支援什麼類型的鍵。這個函式總會是成功的。

 -- C 函式: *note Py_ssize_t: a03. PyMapping_Size (PyObject *o)
 -- C 函式: *note Py_ssize_t: a03. PyMapping_Length (PyObject *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     成功時回傳物件 'o' 中的鍵數，失敗時回傳 ‘-1’。這相當於 Python 運算
     式 ‘len(o)’。

 -- C 函式: *note PyObject: 311. *PyMapping_GetItemString (PyObject *o,
          const char *key)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  這與 *note
     PyObject_GetItem(): 2f9. 相同，但 'key' 被指定為 const char* UTF-8
     編碼位元組字串，而不是 *note PyObject: 311.*。

 -- C 函式: int PyMapping_GetOptionalItem (PyObject *obj, PyObject *key,
          PyObject **result)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Variant of
     *note PyObject_GetItem(): 2f9. which doesn't raise *note KeyError:
     2fb. if the key is not found.

     If the key is found, return ‘1’ and set '*result' to a new *note
     strong reference: 2ee. to the corresponding value.  If the key is
     not found, return ‘0’ and set '*result' to ‘NULL’; the *note
     KeyError: 2fb. is silenced.  If an error other than *note KeyError:
     2fb. is raised, return ‘-1’ and set '*result' to ‘NULL’.

     在 3.13 版被加入.

 -- C 函式: int PyMapping_GetOptionalItemString (PyObject *obj, const
          char *key, PyObject **result)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  This is the
     same as *note PyMapping_GetOptionalItem(): 2f7, but 'key' is
     specified as a const char* UTF-8 encoded bytes string, rather than
     a *note PyObject: 311.*.

     在 3.13 版被加入.

 -- C 函式: int PyMapping_SetItemString (PyObject *o, const char *key,
          PyObject *v)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  這與 *note PyObject_SetItem():
     4764. 相同，但 'key' 被指定為 const char* UTF-8 編碼位元組字串，而
     不是 *note PyObject: 311.*。

 -- C 函式: int PyMapping_DelItem (PyObject *o, PyObject *key)

     這是 *note PyObject_DelItem(): 4837. 的別名。

 -- C 函式: int PyMapping_DelItemString (PyObject *o, const char *key)

     這與 *note PyObject_DelItem(): 4837. 相同，但 'key' 被指定為 const
     char* UTF-8 編碼位元組字串，而不是 *note PyObject: 311.*。

 -- C 函式: int PyMapping_HasKeyWithError (PyObject *o, PyObject *key)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Return ‘1’
     if the mapping object has the key 'key' and ‘0’ otherwise.  This is
     equivalent to the Python expression ‘key in o’.  On failure, return
     ‘-1’.

     在 3.13 版被加入.

 -- C 函式: int PyMapping_HasKeyStringWithError (PyObject *o, const char
          *key)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  This is the
     same as *note PyMapping_HasKeyWithError(): 300, but 'key' is
     specified as a const char* UTF-8 encoded bytes string, rather than
     a *note PyObject: 311.*.

     在 3.13 版被加入.

 -- C 函式: int PyMapping_HasKey (PyObject *o, PyObject *key)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  如果對映物件具有鍵 'key' 則回
     傳 ‘1’，否則回傳 ‘0’。這相當於 Python 運算式 ‘key in o’。這個函式總
     會是成功的。

          備註: Exceptions which occur when this calls *note
          __getitem__(): 266. method are silently ignored.  For proper
          error handling, use *note PyMapping_HasKeyWithError(): 300,
          *note PyMapping_GetOptionalItem(): 2f7. or *note
          PyObject_GetItem(): 2f9. instead.

 -- C 函式: int PyMapping_HasKeyString (PyObject *o, const char *key)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  這與 *note PyMapping_HasKey():
     301. 相同，但 'key' 被指定為 const char* UTF-8 編碼位元組字串，而不
     是 *note PyObject: 311.*。

          備註: Exceptions that occur when this calls *note
          __getitem__(): 266. method or while creating the temporary
          *note str: 3f2. object are silently ignored.  For proper error
          handling, use *note PyMapping_HasKeyStringWithError(): 302,
          *note PyMapping_GetOptionalItemString(): 2f8. or *note
          PyMapping_GetItemString(): 2fa. instead.

 -- C 函式: *note PyObject: 311. *PyMapping_Keys (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  成功時回傳
     一個物件 'o' 內之鍵的串列，失敗時回傳 ‘NULL’。

     在 3.7 版的變更: 在以前，該函式會回傳串列或元組。

 -- C 函式: *note PyObject: 311. *PyMapping_Values (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  成功時回傳
     物件 'o' 中值的串列。失敗時回傳 ‘NULL’。

     在 3.7 版的變更: 在以前，該函式會回傳串列或元組。

 -- C 函式: *note PyObject: 311. *PyMapping_Items (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  成功時回傳
     物件 'o' 內之項目的串列，其中每個項目都是包含鍵值對的元組。失敗時回
     傳 ‘NULL’。

     在 3.7 版的變更: 在以前，該函式會回傳串列或元組。


File: python.info,  Node: 疊代器協議,  Next: 緩衝協定 Buffer Protocol,  Prev: 對映協定,  Up: 抽象物件層 Abstract Objects Layer

7.7.6 疊代器協議
----------------

有兩個專門用於疊代器的函式。

 -- C 函式: int PyIter_Check (PyObject *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.8 版本開始.'  如果物件 'o'
     可以安全地傳遞給 *note PyIter_Next(): 47ed. 則回傳非零 (non-zero)，
     否則回傳 0。這個函式一定會執行成功。

 -- C 函式: int PyAIter_Check (PyObject *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本開始.'  如果物件 'o'
     有提供 ‘AsyncIterator’ 協議，則回傳非零，否則回傳 0。這個函式一定會
     執行成功。

     在 3.10 版被加入.

 -- C 函式: *note PyObject: 311. *PyIter_Next (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  回傳疊代器
     'o' 的下一個值。根據 *note PyIter_Check(): 17f7.，該物件必須是一個
     疊代器（由呼叫者檢查）。如果沒有剩餘值，則回傳 ‘NULL’ 且不設定例外
     。如果檢索項目時發生錯誤，則回傳 ‘NULL’ 並傳遞例外。

要編寫一個疊代於疊代器的迴圈，C 程式碼應該會像這樣：

     PyObject *iterator = PyObject_GetIter(obj);
     PyObject *item;

     if (iterator == NULL) {
         /* propagate error */
     }

     while ((item = PyIter_Next(iterator))) {
         /* do something with item */
         ...
         /* release reference when done */
         Py_DECREF(item);
     }

     Py_DECREF(iterator);

     if (PyErr_Occurred()) {
         /* propagate error */
     }
     else {
         /* continue doing useful work */
     }

 -- C 型別: type PySendResult

     用於表示 *note PyIter_Send(): 83c. 不同結果的列舉 (enum) 值。

     在 3.10 版被加入.

 -- C 函式: *note PySendResult: 4990. PyIter_Send (PyObject *iter,
          PyObject *arg, PyObject **presult)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本開始.'  將 'arg' 值
     發送到疊代器 'iter' 中。回傳：

        - 如果疊代器有回傳則為 ‘PYGEN_RETURN’。回傳值透過 'presult' 回傳
          。

        - 如果疊代器有產生 (yield) 則為 ‘PYGEN_NEXT’。產生值透過
          'presult' 回傳。

        - 如果疊代器引發例外則為 ‘PYGEN_ERROR’。 'presult' 被設定為
          ‘NULL’。

     在 3.10 版被加入.


File: python.info,  Node: 緩衝協定 Buffer Protocol,  Prev: 疊代器協議,  Up: 抽象物件層 Abstract Objects Layer

7.7.7 緩衝協定 (Buffer Protocol)
--------------------------------

Certain objects available in Python wrap access to an underlying memory
array or 'buffer'.  Such objects include the built-in *note bytes: 1a5.
and *note bytearray: 4e3, and some extension types like *note
array.array: 186.  Third-party libraries may define their own types for
special purposes, such as image processing or numeric analysis.

While each of these types have their own semantics, they share the
common characteristic of being backed by a possibly large memory buffer.
It is then desirable, in some situations, to access that buffer directly
and without intermediate copying.

Python provides such a facility at the C level in the form of the *note
buffer protocol: 367.  This protocol has two sides:

   - on the producer side, a type can export a "buffer interface" which
     allows objects of that type to expose information about their
     underlying buffer.  This interface is described in the section
     *note Buffer Object Structures: 4993.;

   - on the consumer side, several means are available to obtain a
     pointer to the raw underlying data of an object (for example a
     method parameter).

Simple objects such as *note bytes: 1a5. and *note bytearray: 4e3.
expose their underlying buffer in byte-oriented form.  Other forms are
possible; for example, the elements exposed by an *note array.array:
186. can be multi-byte values.

An example consumer of the buffer interface is the *note write(): c82.
method of file objects: any object that can export a series of bytes
through the buffer interface can be written to a file.  While ‘write()’
only needs read-only access to the internal contents of the object
passed to it, other methods such as *note readinto(): 2b09. need write
access to the contents of their argument.  The buffer interface allows
objects to selectively allow or reject exporting of read-write and
read-only buffers.

There are two ways for a consumer of the buffer interface to acquire a
buffer over a target object:

   * call *note PyObject_GetBuffer(): 369. with the right parameters;

   * call *note PyArg_ParseTuple(): 517. (or one of its siblings) with
     one of the ‘y*’, ‘w*’ or ‘s*’ *note format codes: 84d.

In both cases, *note PyBuffer_Release(): 36a. must be called when the
buffer isn't needed anymore.  Failure to do so could lead to various
issues such as resource leaks.

* Menu:

* Buffer structure::
* Buffer request types::
* Complex arrays::
* Buffer-related functions::


File: python.info,  Node: Buffer structure,  Next: Buffer request types,  Up: 緩衝協定 Buffer Protocol

7.7.7.1 Buffer structure
........................

Buffer structures (or simply "buffers") are useful as a way to expose
the binary data from another object to the Python programmer.  They can
also be used as a zero-copy slicing mechanism.  Using their ability to
reference a block of memory, it is possible to expose any data to the
Python programmer quite easily.  The memory could be a large, constant
array in a C extension, it could be a raw block of memory for
manipulation before passing to an operating system library, or it could
be used to pass around structured data in its native, in-memory format.

Contrary to most data types exposed by the Python interpreter, buffers
are not *note PyObject: 311. pointers but rather simple C structures.
This allows them to be created and copied very simply.  When a generic
wrapper around a buffer is needed, a *note memoryview: 4996. object can
be created.

For short instructions how to write an exporting object, see *note
Buffer Object Structures: 4993.  For obtaining a buffer, see *note
PyObject_GetBuffer(): 369.

 -- C 型別: type Py_buffer
     ' 為 *note 穩定 ABI 的一部分: 4f9. （包含所有成員） 自 3.11 版本開
     始.'
      -- C 成員函數: void *buf

          A pointer to the start of the logical structure described by
          the buffer fields.  This can be any location within the
          underlying physical memory block of the exporter.  For
          example, with negative *note strides: 4998. the value may
          point to the end of the memory block.

          For *note contiguous: 2103. arrays, the value points to the
          beginning of the memory block.

      -- C 成員函數: *note PyObject: 311. *obj

          A new reference to the exporting object.  The reference is
          owned by the consumer and automatically released (i.e.
          reference count decremented) and set to ‘NULL’ by *note
          PyBuffer_Release(): 36a.  The field is the equivalent of the
          return value of any standard C-API function.

          As a special case, for 'temporary' buffers that are wrapped by
          *note PyMemoryView_FromBuffer(): 705. or *note
          PyBuffer_FillInfo(): 704. this field is ‘NULL’.  In general,
          exporting objects MUST NOT use this scheme.

      -- C 成員函數: *note Py_ssize_t: a03. len

          ‘product(shape) * itemsize’.  For contiguous arrays, this is
          the length of the underlying memory block.  For non-contiguous
          arrays, it is the length that the logical structure would have
          if it were copied to a contiguous representation.

          Accessing ‘((char *)buf)[0] up to ((char *)buf)[len-1]’ is
          only valid if the buffer has been obtained by a request that
          guarantees contiguity.  In most cases such a request will be
          *note PyBUF_SIMPLE: 499b. or *note PyBUF_WRITABLE: 1328.

      -- C 成員函數: int readonly

          An indicator of whether the buffer is read-only.  This field
          is controlled by the *note PyBUF_WRITABLE: 1328. flag.

      -- C 成員函數: *note Py_ssize_t: a03. itemsize

          Item size in bytes of a single element.  Same as the value of
          *note struct.calcsize(): 18c9. called on non-‘NULL’ *note
          format: 499e. values.

          Important exception: If a consumer requests a buffer without
          the *note PyBUF_FORMAT: 499f. flag, *note format: 499e. will
          be set to ‘NULL’, but *note itemsize: 499d. still has the
          value for the original format.

          If *note shape: 49a0. is present, the equality ‘product(shape)
          * itemsize == len’ still holds and the consumer can use *note
          itemsize: 499d. to navigate the buffer.

          If *note shape: 49a0. is ‘NULL’ as a result of a *note
          PyBUF_SIMPLE: 499b. or a *note PyBUF_WRITABLE: 1328. request,
          the consumer must disregard *note itemsize: 499d. and assume
          ‘itemsize == 1’.

      -- C 成員函數: char *format

          A 'NULL' terminated string in *note struct: c0. module style
          syntax describing the contents of a single item.  If this is
          ‘NULL’, ‘"B"’ (unsigned bytes) is assumed.

          This field is controlled by the *note PyBUF_FORMAT: 499f.
          flag.

      -- C 成員函數: int ndim

          The number of dimensions the memory represents as an
          n-dimensional array.  If it is ‘0’, *note buf: 4997. points to
          a single item representing a scalar.  In this case, *note
          shape: 49a0, *note strides: 4998. and *note suboffsets: 49a2.
          MUST be ‘NULL’.  The maximum number of dimensions is given by
          *note PyBUF_MAX_NDIM: 49a3.

      -- C 成員函數: *note Py_ssize_t: a03. *shape

          An array of *note Py_ssize_t: a03. of length *note ndim: 49a1.
          indicating the shape of the memory as an n-dimensional array.
          Note that ‘shape[0] * ... * shape[ndim-1] * itemsize’ MUST be
          equal to *note len: 499a.

          Shape values are restricted to ‘shape[n] >= 0’.  The case
          ‘shape[n] == 0’ requires special attention.  See *note complex
          arrays: 49a4. for further information.

          The shape array is read-only for the consumer.

      -- C 成員函數: *note Py_ssize_t: a03. *strides

          An array of *note Py_ssize_t: a03. of length *note ndim: 49a1.
          giving the number of bytes to skip to get to a new element in
          each dimension.

          Stride values can be any integer.  For regular arrays, strides
          are usually positive, but a consumer MUST be able to handle
          the case ‘strides[n] <= 0’.  See *note complex arrays: 49a4.
          for further information.

          The strides array is read-only for the consumer.

      -- C 成員函數: *note Py_ssize_t: a03. *suboffsets

          An array of *note Py_ssize_t: a03. of length *note ndim: 49a1.
          If ‘suboffsets[n] >= 0’, the values stored along the nth
          dimension are pointers and the suboffset value dictates how
          many bytes to add to each pointer after de-referencing.  A
          suboffset value that is negative indicates that no
          de-referencing should occur (striding in a contiguous memory
          block).

          If all suboffsets are negative (i.e.  no de-referencing is
          needed), then this field must be ‘NULL’ (the default value).

          This type of array representation is used by the Python
          Imaging Library (PIL). See *note complex arrays: 49a4. for
          further information how to access elements of such an array.

          The suboffsets array is read-only for the consumer.

      -- C 成員函數: void *internal

          This is for use internally by the exporting object.  For
          example, this might be re-cast as an integer by the exporter
          and used to store flags about whether or not the shape,
          strides, and suboffsets arrays must be freed when the buffer
          is released.  The consumer MUST NOT alter this value.

常數：

 -- C 巨集: PyBUF_MAX_NDIM

     The maximum number of dimensions the memory represents.  Exporters
     MUST respect this limit, consumers of multi-dimensional buffers
     SHOULD be able to handle up to ‘PyBUF_MAX_NDIM’ dimensions.
     Currently set to 64.


File: python.info,  Node: Buffer request types,  Next: Complex arrays,  Prev: Buffer structure,  Up: 緩衝協定 Buffer Protocol

7.7.7.2 Buffer request types
............................

Buffers are usually obtained by sending a buffer request to an exporting
object via *note PyObject_GetBuffer(): 369.  Since the complexity of the
logical structure of the memory can vary drastically, the consumer uses
the 'flags' argument to specify the exact buffer type it can handle.

All *note Py_buffer: 6fc. fields are unambiguously defined by the
request type.

* Menu:

* request-independent fields::
* readonly, format: readonly format.
* shape, strides, suboffsets: shape strides suboffsets.
* contiguity requests::
* compound requests::


File: python.info,  Node: request-independent fields,  Next: readonly format,  Up: Buffer request types

7.7.7.3 request-independent fields
..................................

The following fields are not influenced by 'flags' and must always be
filled in with the correct values: *note obj: 4999, *note buf: 4997,
*note len: 499a, *note itemsize: 499d, *note ndim: 49a1.


File: python.info,  Node: readonly format,  Next: shape strides suboffsets,  Prev: request-independent fields,  Up: Buffer request types

7.7.7.4 readonly, format
........................

      -- C 巨集: PyBUF_WRITABLE

          Controls the *note readonly: 499c. field.  If set, the
          exporter MUST provide a writable buffer or else report
          failure.  Otherwise, the exporter MAY provide either a
          read-only or writable buffer, but the choice MUST be
          consistent for all consumers.

      -- C 巨集: PyBUF_FORMAT

          Controls the *note format: 499e. field.  If set, this field
          MUST be filled in correctly.  Otherwise, this field MUST be
          ‘NULL’.

*note PyBUF_WRITABLE: 1328. can be |'d to any of the flags in the next
section.  Since *note PyBUF_SIMPLE: 499b. is defined as 0, *note
PyBUF_WRITABLE: 1328. can be used as a stand-alone flag to request a
simple writable buffer.

*note PyBUF_FORMAT: 499f. can be |'d to any of the flags except *note
PyBUF_SIMPLE: 499b.  The latter already implies format ‘B’ (unsigned
bytes).


File: python.info,  Node: shape strides suboffsets,  Next: contiguity requests,  Prev: readonly format,  Up: Buffer request types

7.7.7.5 shape, strides, suboffsets
..................................

The flags that control the logical structure of the memory are listed in
decreasing order of complexity.  Note that each flag contains all bits
of the flags below it.

Request                           shape       strides       suboffsets
                                                            
-----------------------------------------------------------------------------
                                                            
 -- C 巨集: PyBUF_INDIRECT        yes         yes           if needed
                                                            
                                                            
 -- C 巨集: PyBUF_STRIDES         yes         yes           NULL
                                                            
                                                            
 -- C 巨集: PyBUF_ND              yes         NULL          NULL
                                                            
                                                            
 -- C 巨集: PyBUF_SIMPLE          NULL        NULL          NULL
                                                            


File: python.info,  Node: contiguity requests,  Next: compound requests,  Prev: shape strides suboffsets,  Up: Buffer request types

7.7.7.6 contiguity requests
...........................

C or Fortran *note contiguity: 2103. can be explicitly requested, with
and without stride information.  Without stride information, the buffer
must be C-contiguous.

Request                                 shape       strides       suboffsets       contig
                                                                                   
------------------------------------------------------------------------------------------------
                                                                                   
 -- C 巨集: PyBUF_C_CONTIGUOUS          yes         yes           NULL             C
                                                                                   
                                                                                   
 -- C 巨集: PyBUF_F_CONTIGUOUS          yes         yes           NULL             F
                                                                                   
                                                                                   
 -- C 巨集: PyBUF_ANY_CONTIGUOUS        yes         yes           NULL             C 或 F
                                                                                   
                                                                                   
*note PyBUF_ND: 49ac.                   yes         NULL          NULL             C
                                                                                   


File: python.info,  Node: compound requests,  Prev: contiguity requests,  Up: Buffer request types

7.7.7.7 compound requests
.........................

All possible requests are fully defined by some combination of the flags
in the previous section.  For convenience, the buffer protocol provides
frequently used combinations as single flags.

In the following table 'U' stands for undefined contiguity.  The
consumer would have to call *note PyBuffer_IsContiguous(): 702. to
determine contiguity.

Request                             shape       strides       suboffsets       contig       readonly       format
                                                                                                           
------------------------------------------------------------------------------------------------------------------------
                                                                                                           
 -- C 巨集: PyBUF_FULL              yes         yes           if needed        U            0              yes
                                                                                                           
                                                                                                           
 -- C 巨集: PyBUF_FULL_RO           yes         yes           if needed        U            1 或 0         yes
                                                                                                           
                                                                                                           
 -- C 巨集: PyBUF_RECORDS           yes         yes           NULL             U            0              yes
                                                                                                           
                                                                                                           
 -- C 巨集: PyBUF_RECORDS_RO        yes         yes           NULL             U            1 或 0         yes
                                                                                                           
                                                                                                           
 -- C 巨集: PyBUF_STRIDED           yes         yes           NULL             U            0              NULL
                                                                                                           
                                                                                                           
 -- C 巨集: PyBUF_STRIDED_RO        yes         yes           NULL             U            1 或 0         NULL
                                                                                                           
                                                                                                           
 -- C 巨集: PyBUF_CONTIG            yes         NULL          NULL             C            0              NULL
                                                                                                           
                                                                                                           
 -- C 巨集: PyBUF_CONTIG_RO         yes         NULL          NULL             C            1 或 0         NULL
                                                                                                           


File: python.info,  Node: Complex arrays,  Next: Buffer-related functions,  Prev: Buffer request types,  Up: 緩衝協定 Buffer Protocol

7.7.7.8 Complex arrays
......................

* Menu:

* NumPy-style; shape and strides: NumPy-style shape and strides.
* PIL-style; shape, strides and suboffsets: PIL-style shape strides and suboffsets.


File: python.info,  Node: NumPy-style shape and strides,  Next: PIL-style shape strides and suboffsets,  Up: Complex arrays

7.7.7.9 NumPy-style: shape and strides
......................................

The logical structure of NumPy-style arrays is defined by *note
itemsize: 499d, *note ndim: 49a1, *note shape: 49a0. and *note strides:
4998.

If ‘ndim == 0’, the memory location pointed to by *note buf: 4997. is
interpreted as a scalar of size *note itemsize: 499d.  In that case,
both *note shape: 49a0. and *note strides: 4998. are ‘NULL’.

If *note strides: 4998. is ‘NULL’, the array is interpreted as a
standard n-dimensional C-array.  Otherwise, the consumer must access an
n-dimensional array as follows:

     ptr = (char *)buf + indices[0] * strides[0] + ... + indices[n-1] * strides[n-1];
     item = *((typeof(item) *)ptr);

As noted above, *note buf: 4997. can point to any location within the
actual memory block.  An exporter can check the validity of a buffer
with this function:

     def verify_structure(memlen, itemsize, ndim, shape, strides, offset):
         """Verify that the parameters represent a valid array within
            the bounds of the allocated memory:
                char *mem: start of the physical memory block
                memlen: length of the physical memory block
                offset: (char *)buf - mem
         """
         if offset % itemsize:
             return False
         if offset < 0 or offset+itemsize > memlen:
             return False
         if any(v % itemsize for v in strides):
             return False

         if ndim <= 0:
             return ndim == 0 and not shape and not strides
         if 0 in shape:
             return True

         imin = sum(strides[j]*(shape[j]-1) for j in range(ndim)
                    if strides[j] <= 0)
         imax = sum(strides[j]*(shape[j]-1) for j in range(ndim)
                    if strides[j] > 0)

         return 0 <= offset+imin and offset+imax+itemsize <= memlen


File: python.info,  Node: PIL-style shape strides and suboffsets,  Prev: NumPy-style shape and strides,  Up: Complex arrays

7.7.7.10 PIL-style: shape, strides and suboffsets
.................................................

In addition to the regular items, PIL-style arrays can contain pointers
that must be followed in order to get to the next element in a
dimension.  For example, the regular three-dimensional C-array ‘char
v[2][2][3]’ can also be viewed as an array of 2 pointers to 2
two-dimensional arrays: ‘char (*v[2])[2][3]’.  In suboffsets
representation, those two pointers can be embedded at the start of *note
buf: 4997, pointing to two ‘char x[2][3]’ arrays that can be located
anywhere in memory.

Here is a function that returns a pointer to the element in an N-D array
pointed to by an N-dimensional index when there are both non-‘NULL’
strides and suboffsets:

     void *get_item_pointer(int ndim, void *buf, Py_ssize_t *strides,
                            Py_ssize_t *suboffsets, Py_ssize_t *indices) {
         char *pointer = (char*)buf;
         int i;
         for (i = 0; i < ndim; i++) {
             pointer += strides[i] * indices[i];
             if (suboffsets[i] >=0 ) {
                 pointer = *((char**)pointer) + suboffsets[i];
             }
         }
         return (void*)pointer;
     }


File: python.info,  Node: Buffer-related functions,  Prev: Complex arrays,  Up: 緩衝協定 Buffer Protocol

7.7.7.11 Buffer-related functions
.................................

 -- C 函式: int PyObject_CheckBuffer (PyObject *obj)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.11 版本開始.'  Return ‘1’
     if 'obj' supports the buffer interface otherwise ‘0’.  When ‘1’ is
     returned, it doesn't guarantee that *note PyObject_GetBuffer():
     369. will succeed.  This function always succeeds.

 -- C 函式: int PyObject_GetBuffer (PyObject *exporter, Py_buffer *view,
          int flags)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.11 版本開始.'  Send a
     request to 'exporter' to fill in 'view' as specified by 'flags'.
     If the exporter cannot provide a buffer of the exact type, it MUST
     raise *note BufferError: 1729, set ‘view->obj’ to ‘NULL’ and return
     ‘-1’.

     On success, fill in 'view', set ‘view->obj’ to a new reference to
     'exporter' and return 0.  In the case of chained buffer providers
     that redirect requests to a single object, ‘view->obj’ MAY refer to
     this object instead of 'exporter' (See *note Buffer Object
     Structures: 4993.).

     Successful calls to *note PyObject_GetBuffer(): 369. must be paired
     with calls to *note PyBuffer_Release(): 36a, similar to ‘malloc()’
     and ‘free()’.  Thus, after the consumer is done with the buffer,
     *note PyBuffer_Release(): 36a. must be called exactly once.

 -- C 函式: void PyBuffer_Release (Py_buffer *view)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.11 版本開始.'  Release the
     buffer 'view' and release the *note strong reference: 2ee. (i.e.
     decrement the reference count) to the view's supporting object,
     ‘view->obj’.  This function MUST be called when the buffer is no
     longer being used, otherwise reference leaks may occur.

     It is an error to call this function on a buffer that was not
     obtained via *note PyObject_GetBuffer(): 369.

 -- C 函式: *note Py_ssize_t: a03. PyBuffer_SizeFromFormat (const char
          *format)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.11 版本開始.'  Return the
     implied *note itemsize: 499d. from *note format: 499e.  On error,
     raise an exception and return -1.

     在 3.9 版被加入.

 -- C 函式: int PyBuffer_IsContiguous (const Py_buffer *view, char
          order)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.11 版本開始.'  Return ‘1’
     if the memory defined by the 'view' is C-style ('order' is ‘'C'’)
     or Fortran-style ('order' is ‘'F'’) *note contiguous: 2103. or
     either one ('order' is ‘'A'’).  Return ‘0’ otherwise.  This
     function always succeeds.

 -- C 函式: void *PyBuffer_GetPointer (const Py_buffer *view, const
          Py_ssize_t *indices)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.11 版本開始.'  Get the
     memory area pointed to by the 'indices' inside the given 'view'.
     'indices' must point to an array of ‘view->ndim’ indices.

 -- C 函式: int PyBuffer_FromContiguous (const Py_buffer *view, const
          void *buf, Py_ssize_t len, char fort)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.11 版本開始.'  Copy
     contiguous 'len' bytes from 'buf' to 'view'.  'fort' can be ‘'C'’
     or ‘'F'’ (for C-style or Fortran-style ordering).  ‘0’ is returned
     on success, ‘-1’ on error.

 -- C 函式: int PyBuffer_ToContiguous (void *buf, const Py_buffer *src,
          Py_ssize_t len, char order)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.11 版本開始.'  Copy 'len'
     bytes from 'src' to its contiguous representation in 'buf'.
     'order' can be ‘'C'’ or ‘'F'’ or ‘'A'’ (for C-style or
     Fortran-style ordering or either one).  ‘0’ is returned on success,
     ‘-1’ on error.

     This function fails if 'len' != 'src->len'.

 -- C 函式: int PyObject_CopyData (PyObject *dest, PyObject *src)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.11 版本開始.'  Copy data
     from 'src' to 'dest' buffer.  Can convert between C-style and or
     Fortran-style buffers.

     ‘0’ is returned on success, ‘-1’ on error.

 -- C 函式: void PyBuffer_FillContiguousStrides (int ndims, Py_ssize_t
          *shape, Py_ssize_t *strides, int itemsize, char order)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.11 版本開始.'  Fill the
     'strides' array with byte-strides of a *note contiguous: 2103.
     (C-style if 'order' is ‘'C'’ or Fortran-style if 'order' is ‘'F'’)
     array of the given shape with the given number of bytes per
     element.

 -- C 函式: int PyBuffer_FillInfo (Py_buffer *view, PyObject *exporter,
          void *buf, Py_ssize_t len, int readonly, int flags)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.11 版本開始.'  Handle
     buffer requests for an exporter that wants to expose 'buf' of size
     'len' with writability set according to 'readonly'.  'buf' is
     interpreted as a sequence of unsigned bytes.

     The 'flags' argument indicates the request type.  This function
     always fills in 'view' as specified by flags, unless 'buf' has been
     designated as read-only and *note PyBUF_WRITABLE: 1328. is set in
     'flags'.

     On success, set ‘view->obj’ to a new reference to 'exporter' and
     return 0.  Otherwise, raise *note BufferError: 1729, set
     ‘view->obj’ to ‘NULL’ and return ‘-1’;

     If this function is used as part of a *note getbufferproc: 4993,
     'exporter' MUST be set to the exporting object and 'flags' must be
     passed unmodified.  Otherwise, 'exporter' MUST be ‘NULL’.


File: python.info,  Node: 具體物件層,  Next: Initialization Finalization and Threads,  Prev: 抽象物件層 Abstract Objects Layer,  Up: Python/C API 參考手冊

7.8 具體物件層
==============

此章節列出的函式僅能接受某些特定的 Python 物件型別，將錯誤型別的物件傳遞
給它們並不是什麼好事，如果你從 Python 程式當中接收到一個不確定是否為正確
型別的物件，那麼請一定要先做型別檢查。例如使用 *note PyDict_Check():
49be. 來確認一個物件是否為字典。本章結構類似於 Python 物件型別的"族譜圖
(family tree)"。

     警告: 雖然本章所述之函式仔細地檢查了傳入物件的型別，但大多並無檢查
     是否為 ‘NULL’。允許 ‘NULL’ 的傳入可能造成記憶體的不合法存取和直譯器
     的立即中止。

* Menu:

* 基礎物件::
* 數值物件::
* 序列物件::
* 容器物件::
* 函式物件: 函式物件<2>.
* 其他物件: 其他物件<2>.


File: python.info,  Node: 基礎物件,  Next: 數值物件,  Up: 具體物件層

7.8.1 基礎物件
--------------

此段落描述 Python 型別物件與單例 (singleton) 物件 ‘None’。

* Menu:

* 型別物件::
* None 物件::


File: python.info,  Node: 型別物件,  Next: None 物件,  Up: 基礎物件

7.8.1.1 型別物件
................

 -- C 型別: type PyTypeObject
     ' 為 *note 受限 API 的一部分: 4f9. （做為一個不透明結構 (opaque
     struct)）.'  The C structure of the objects used to describe
     built-in types.

 -- C 變數: *note PyTypeObject: a48. PyType_Type
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This is the type object for
     type objects; it is the same object as *note type: cef. in the
     Python layer.

 -- C 函式: int PyType_Check (PyObject *o)

     Return non-zero if the object 'o' is a type object, including
     instances of types derived from the standard type object.  Return 0
     in all other cases.  This function always succeeds.

 -- C 函式: int PyType_CheckExact (PyObject *o)

     Return non-zero if the object 'o' is a type object, but not a
     subtype of the standard type object.  Return 0 in all other cases.
     This function always succeeds.

 -- C 函式: unsigned int PyType_ClearCache ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Clear the internal lookup
     cache.  Return the current version tag.

 -- C 函式: unsigned long PyType_GetFlags (PyTypeObject *type)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the *note tp_flags:
     17c0. member of 'type'.  This function is primarily meant for use
     with ‘Py_LIMITED_API’; the individual flag bits are guaranteed to
     be stable across Python releases, but access to *note tp_flags:
     17c0. itself is not part of the *note limited API: 318.

     在 3.2 版被加入.

     在 3.4 版的變更: The return type is now ‘unsigned long’ rather than
     ‘long’.

 -- C 函式: *note PyObject: 311. *PyType_GetDict (PyTypeObject *type)

     Return the type object's internal namespace, which is otherwise
     only exposed via a read-only proxy (‘cls.__dict__’).  This is a
     replacement for accessing *note tp_dict: 161c. directly.  The
     returned dictionary must be treated as read-only.

     This function is meant for specific embedding and language-binding
     cases, where direct access to the dict is necessary and indirect
     access (e.g.  via the proxy or *note PyObject_GetAttr(): 2f4.)
     isn't adequate.

     Extension modules should continue to use ‘tp_dict’, directly or
     indirectly, when setting up their own types.

     在 3.12 版被加入.

 -- C 函式: void PyType_Modified (PyTypeObject *type)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Invalidate the internal lookup
     cache for the type and all of its subtypes.  This function must be
     called after any manual modification of the attributes or base
     classes of the type.

 -- C 函式: int PyType_AddWatcher (PyType_WatchCallback callback)

     Register 'callback' as a type watcher.  Return a non-negative
     integer ID which must be passed to future calls to *note
     PyType_Watch(): 50b.  In case of error (e.g.  no more watcher IDs
     available), return ‘-1’ and set an exception.

     在 3.12 版被加入.

 -- C 函式: int PyType_ClearWatcher (int watcher_id)

     Clear watcher identified by 'watcher_id' (previously returned from
     *note PyType_AddWatcher(): 50a.).  Return ‘0’ on success, ‘-1’ on
     error (e.g.  if 'watcher_id' was never registered.)

     An extension should never call ‘PyType_ClearWatcher’ with a
     'watcher_id' that was not returned to it by a previous call to
     *note PyType_AddWatcher(): 50a.

     在 3.12 版被加入.

 -- C 函式: int PyType_Watch (int watcher_id, PyObject *type)

     Mark 'type' as watched.  The callback granted 'watcher_id' by *note
     PyType_AddWatcher(): 50a. will be called whenever *note
     PyType_Modified(): 16f7. reports a change to 'type'.  (The callback
     may be called only once for a series of consecutive modifications
     to 'type', if ‘_PyType_Lookup()’ is not called on 'type' between
     the modifications; this is an implementation detail and subject to
     change.)

     An extension should never call ‘PyType_Watch’ with a 'watcher_id'
     that was not returned to it by a previous call to *note
     PyType_AddWatcher(): 50a.

     在 3.12 版被加入.

 -- C 型別: typedef int (*PyType_WatchCallback)(*note PyObject: 311.
          *type)

     Type of a type-watcher callback function.

     The callback must not modify 'type' or cause *note
     PyType_Modified(): 16f7. to be called on 'type' or any type in its
     MRO; violating this rule could cause infinite recursion.

     在 3.12 版被加入.

 -- C 函式: int PyType_HasFeature (PyTypeObject *o, int feature)

     Return non-zero if the type object 'o' sets the feature 'feature'.
     Type features are denoted by single bit flags.

 -- C 函式: int PyType_IS_GC (PyTypeObject *o)

     Return true if the type object includes support for the cycle
     detector; this tests the type flag *note Py_TPFLAGS_HAVE_GC: 720.

 -- C 函式: int PyType_IsSubtype (PyTypeObject *a, PyTypeObject *b)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return true if 'a' is a
     subtype of 'b'.

     This function only checks for actual subtypes, which means that
     *note __subclasscheck__(): 1e54. is not called on 'b'.  Call *note
     PyObject_IsSubclass(): e49. to do the same check that *note
     issubclass(): 765. would do.

 -- C 函式: *note PyObject: 311. *PyType_GenericAlloc (PyTypeObject
          *type, Py_ssize_t nitems)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Generic
     handler for the *note tp_alloc: 4706. slot of a type object.  Use
     Python's default memory allocation mechanism to allocate a new
     instance and initialize all its contents to ‘NULL’.

 -- C 函式: *note PyObject: 311. *PyType_GenericNew (PyTypeObject *type,
          PyObject *args, PyObject *kwds)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Generic
     handler for the *note tp_new: 525. slot of a type object.  Create a
     new instance using the type's *note tp_alloc: 4706. slot.

 -- C 函式: int PyType_Ready (PyTypeObject *type)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Finalize a type object.  This
     should be called on all type objects to finish their
     initialization.  This function is responsible for adding inherited
     slots from a type's base class.  Return ‘0’ on success, or return
     ‘-1’ and sets an exception on error.

          備註: If some of the base classes implements the GC protocol
          and the provided type does not include the *note
          Py_TPFLAGS_HAVE_GC: 720. in its flags, then the GC protocol
          will be automatically implemented from its parents.  On the
          contrary, if the type being created does include *note
          Py_TPFLAGS_HAVE_GC: 720. in its flags then it 'must' implement
          the GC protocol itself by at least implementing the *note
          tp_traverse: 721. handle.

 -- C 函式: *note PyObject: 311. *PyType_GetName (PyTypeObject *type)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.11 版本
     開始.'  Return the type's name.  Equivalent to getting the type's
     ‘__name__’ attribute.

     在 3.11 版被加入.

 -- C 函式: *note PyObject: 311. *PyType_GetQualName (PyTypeObject
          *type)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.11 版本
     開始.'  Return the type's qualified name.  Equivalent to getting
     the type's ‘__qualname__’ attribute.

     在 3.11 版被加入.

 -- C 函式: *note PyObject: 311. *PyType_GetFullyQualifiedName
          (PyTypeObject *type)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Return the
     type's fully qualified name.  Equivalent to
     ‘f"{type.__module__}.{type.__qualname__}"’, or ‘type.__qualname__’
     if ‘type.__module__’ is not a string or is equal to ‘"builtins"’.

     在 3.13 版被加入.

 -- C 函式: *note PyObject: 311. *PyType_GetModuleName (PyTypeObject
          *type)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Return the
     type's module name.  Equivalent to getting the ‘type.__module__’
     attribute.

     在 3.13 版被加入.

 -- C 函式: void *PyType_GetSlot (PyTypeObject *type, int slot)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.4 版本開始.'  Return the
     function pointer stored in the given slot.  If the result is
     ‘NULL’, this indicates that either the slot is ‘NULL’, or that the
     function was called with invalid parameters.  Callers will
     typically cast the result pointer into the appropriate function
     type.

     See *note PyType_Slot.slot: 49c7. for possible values of the 'slot'
     argument.

     在 3.4 版被加入.

     在 3.10 版的變更: *note PyType_GetSlot(): 840. can now accept all
     types.  Previously, it was limited to *note heap types: 909.

 -- C 函式: *note PyObject: 311. *PyType_GetModule (PyTypeObject *type)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本開始.'  Return the
     module object associated with the given type when the type was
     created using *note PyType_FromModuleAndSpec(): 4f7.

     If no module is associated with the given type, sets *note
     TypeError: 4dd. and returns ‘NULL’.

     This function is usually used to get the module in which a method
     is defined.  Note that in such a method,
     ‘PyType_GetModule(Py_TYPE(self))’ may not return the intended
     result.  ‘Py_TYPE(self)’ may be a 'subclass' of the intended class,
     and subclasses are not necessarily defined in the same module as
     their superclass.  See *note PyCMethod: 708. to get the class that
     defines the method.  See *note PyType_GetModuleByDef(): 342. for
     cases when ‘PyCMethod’ cannot be used.

     在 3.9 版被加入.

 -- C 函式: void *PyType_GetModuleState (PyTypeObject *type)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本開始.'  Return the
     state of the module object associated with the given type.  This is
     a shortcut for calling *note PyModule_GetState(): 924. on the
     result of *note PyType_GetModule(): 912.

     If no module is associated with the given type, sets *note
     TypeError: 4dd. and returns ‘NULL’.

     If the 'type' has an associated module but its state is ‘NULL’,
     returns ‘NULL’ without setting an exception.

     在 3.9 版被加入.

 -- C 函式: *note PyObject: 311. *PyType_GetModuleByDef (PyTypeObject
          *type, struct PyModuleDef *def)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Find the
     first superclass whose module was created from the given *note
     PyModuleDef: 921. 'def', and return that module.

     If no module is found, raises a *note TypeError: 4dd. and returns
     ‘NULL’.

     This function is intended to be used together with *note
     PyModule_GetState(): 924. to get module state from slot methods
     (such as *note tp_init: 527. or *note nb_add: 49c8.) and other
     places where a method's defining class cannot be passed using the
     *note PyCMethod: 708. calling convention.

     在 3.11 版被加入.

 -- C 函式: int PyUnstable_Type_AssignVersionTag (PyTypeObject *type)

          這是 不穩定 API，它可能在小版本發布中沒有任何警告地被變更。 '這是 *note 不穩定 API: 4ed.，它可能在小版本發布中沒有任何警告地被變更。': 
     Attempt to assign a version tag to the given type.

     Returns 1 if the type already had a valid version tag or a new one
     was assigned, or 0 if a new tag could not be assigned.

     在 3.12 版被加入.

* Menu:

* Creating Heap-Allocated Types::


File: python.info,  Node: Creating Heap-Allocated Types,  Up: 型別物件

7.8.1.2 Creating Heap-Allocated Types
.....................................

The following functions and structs are used to create *note heap types:
909.

 -- C 函式: *note PyObject: 311. *PyType_FromMetaclass (PyTypeObject
          *metaclass, PyObject *module, PyType_Spec *spec, PyObject
          *bases)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.12 版本開始.'  Create and
     return a *note heap type: 909. from the 'spec' (see *note
     Py_TPFLAGS_HEAPTYPE: 854.).

     The metaclass 'metaclass' is used to construct the resulting type
     object.  When 'metaclass' is ‘NULL’, the metaclass is derived from
     'bases' (or 'Py_tp_base[s]' slots if 'bases' is ‘NULL’, see below).

     Metaclasses that override *note tp_new: 525. are not supported,
     except if ‘tp_new’ is ‘NULL’.  (For backwards compatibility, other
     ‘PyType_From*’ functions allow such metaclasses.  They ignore
     ‘tp_new’, which may result in incomplete initialization.  This is
     deprecated and in Python 3.14+ such metaclasses will not be
     supported.)

     The 'bases' argument can be used to specify base classes; it can
     either be only one class or a tuple of classes.  If 'bases' is
     ‘NULL’, the 'Py_tp_bases' slot is used instead.  If that also is
     ‘NULL’, the 'Py_tp_base' slot is used instead.  If that also is
     ‘NULL’, the new type derives from *note object: a2f.

     The 'module' argument can be used to record the module in which the
     new class is defined.  It must be a module object or ‘NULL’.  If
     not ‘NULL’, the module is associated with the new type and can
     later be retrieved with *note PyType_GetModule(): 912.  The
     associated module is not inherited by subclasses; it must be
     specified for each class individually.

     This function calls *note PyType_Ready(): 722. on the new type.

     Note that this function does 'not' fully match the behavior of
     calling *note type(): cef. or using the *note class: 126a.
     statement.  With user-provided base types or metaclasses, prefer
     *note calling: 4971. *note type: cef. (or the metaclass) over
     ‘PyType_From*’ functions.  Specifically:

        * *note __new__(): 526. is not called on the new class (and it
          must be set to ‘type.__new__’).

        * *note __init__(): 655. is not called on the new class.

        * *note __init_subclass__(): 5d7. is not called on any bases.

        * *note __set_name__(): bf5. is not called on new descriptors.

     在 3.12 版被加入.

 -- C 函式: *note PyObject: 311. *PyType_FromModuleAndSpec (PyObject
          *module, PyType_Spec *spec, PyObject *bases)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本
     開始.'  等價於 ‘PyType_FromMetaclass(NULL, module, spec, bases)’。

     在 3.9 版被加入.

     在 3.10 版的變更: The function now accepts a single class as the
     'bases' argument and ‘NULL’ as the ‘tp_doc’ slot.

     在 3.12 版的變更: The function now finds and uses a metaclass
     corresponding to the provided base classes.  Previously, only *note
     type: cef. instances were returned.

     The *note tp_new: 525. of the metaclass is 'ignored'.  which may
     result in incomplete initialization.  Creating classes whose
     metaclass overrides *note tp_new: 525. is deprecated and in Python
     3.14+ it will be no longer allowed.

 -- C 函式: *note PyObject: 311. *PyType_FromSpecWithBases (PyType_Spec
          *spec, PyObject *bases)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.3 版本
     開始.'  等價於 ‘PyType_FromMetaclass(NULL, NULL, spec, bases)’。

     在 3.3 版被加入.

     在 3.12 版的變更: The function now finds and uses a metaclass
     corresponding to the provided base classes.  Previously, only *note
     type: cef. instances were returned.

     The *note tp_new: 525. of the metaclass is 'ignored'.  which may
     result in incomplete initialization.  Creating classes whose
     metaclass overrides *note tp_new: 525. is deprecated and in Python
     3.14+ it will be no longer allowed.

 -- C 函式: *note PyObject: 311. *PyType_FromSpec (PyType_Spec *spec)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  等價於
     ‘PyType_FromMetaclass(NULL, NULL, spec, NULL)’。

     在 3.12 版的變更: The function now finds and uses a metaclass
     corresponding to the base classes provided in 'Py_tp_base[s]'
     slots.  Previously, only *note type: cef. instances were returned.

     The *note tp_new: 525. of the metaclass is 'ignored'.  which may
     result in incomplete initialization.  Creating classes whose
     metaclass overrides *note tp_new: 525. is deprecated and in Python
     3.14+ it will be no longer allowed.

 -- C 型別: type PyType_Spec
     ' 為 *note 穩定 ABI 的一部分: 4f9. （包含所有成員）.'  Structure
     defining a type's behavior.

      -- C 成員函數: const char *name

          Name of the type, used to set *note PyTypeObject.tp_name:
          17f5.

      -- C 成員函數: int basicsize

          If positive, specifies the size of the instance in bytes.  It
          is used to set *note PyTypeObject.tp_basicsize: 92b.

          If zero, specifies that *note tp_basicsize: 92b. should be
          inherited.

          If negative, the absolute value specifies how much space
          instances of the class need 'in addition' to the superclass.
          Use *note PyObject_GetTypeData(): 4ef. to get a pointer to
          subclass-specific memory reserved this way.

          在 3.12 版的變更: Previously, this field could not be
          negative.

      -- C 成員函數: int itemsize

          Size of one element of a variable-size type, in bytes.  Used
          to set *note PyTypeObject.tp_itemsize: 1e46.  See
          ‘tp_itemsize’ documentation for caveats.

          If zero, *note tp_itemsize: 1e46. is inherited.  Extending
          arbitrary variable-sized classes is dangerous, since some
          types use a fixed offset for variable-sized memory, which can
          then overlap fixed-sized memory used by a subclass.  To help
          prevent mistakes, inheriting ‘itemsize’ is only possible in
          the following situations:

             - The base is not variable-sized (its *note tp_itemsize:
               1e46.).

             - The requested *note PyType_Spec.basicsize: 4ee. is
               positive, suggesting that the memory layout of the base
               class is known.

             - The requested *note PyType_Spec.basicsize: 4ee. is zero,
               suggesting that the subclass does not access the
               instance's memory directly.

             - With the *note Py_TPFLAGS_ITEMS_AT_END: 4f1. flag.

      -- C 成員函數: unsigned int flags

          Type flags, used to set *note PyTypeObject.tp_flags: 17c0.

          If the ‘Py_TPFLAGS_HEAPTYPE’ flag is not set, *note
          PyType_FromSpecWithBases(): 524. sets it automatically.

      -- C 成員函數: *note PyType_Slot: 4875. *slots

          Array of *note PyType_Slot: 4875. structures.  Terminated by
          the special slot value ‘{0, NULL}’.

          Each slot ID should be specified at most once.

 -- C 型別: type PyType_Slot
     ' 為 *note 穩定 ABI 的一部分: 4f9. （包含所有成員）.'  Structure
     defining optional functionality of a type, containing a slot ID and
     a value pointer.

      -- C 成員函數: int slot

               A slot ID.

               Slot IDs are named like the field names of the structures
               *note PyTypeObject: a48, *note PyNumberMethods: 138b,
               *note PySequenceMethods: 4729, *note PyMappingMethods:
               472a. and *note PyAsyncMethods: 49cf. with an added ‘Py_’
               prefix.  For example, use:

                  * ‘Py_tp_dealloc’ to set *note
                    PyTypeObject.tp_dealloc: 4704.

                  * ‘Py_nb_add’ to set *note PyNumberMethods.nb_add:
                    49c8.

                  * ‘Py_sq_length’ to set *note
                    PySequenceMethods.sq_length: 49d0.

               The following “offset” fields cannot be set using *note
               PyType_Slot: 4875.:

                       * *note tp_weaklistoffset: 92c. (use *note
                         Py_TPFLAGS_MANAGED_WEAKREF: 500. instead if
                         possible)

                       * *note tp_dictoffset: 49d1.（如果可能，請改用
                         *note Py_TPFLAGS_MANAGED_DICT: 31b.）

                       * *note tp_vectorcall_offset: 4973.（請用 *note
                         PyMemberDef: 49d2. 中的
                         ‘"__vectorcalloffset__"’）

                    If it is not possible to switch to a ‘MANAGED’ flag
                    (for example, for vectorcall or to support Python
                    older than 3.12), specify the offset in *note
                    Py_tp_members: 4707.  See *note PyMemberDef
                    documentation: 49d2. for details.

               The following fields cannot be set at all when creating a
               heap type:

                  * *note tp_vectorcall: 49d3. (use *note tp_new: 525.
                    and/or *note tp_init: 527.)

                  * Internal fields: *note tp_dict: 161c, *note tp_mro:
                    49d4, *note tp_cache: 49d5, *note tp_subclasses:
                    518, and *note tp_weaklist: 49d6.

               Setting ‘Py_tp_bases’ or ‘Py_tp_base’ may be problematic
               on some platforms.  To avoid issues, use the 'bases'
               argument of *note PyType_FromSpecWithBases(): 524.
               instead.

          在 3.9 版的變更: Slots in *note PyBufferProcs: 49d7. may be
          set in the unlimited API.

          在 3.11 版的變更: *note bf_getbuffer: 706. and *note
          bf_releasebuffer: 707. are now available under the *note
          limited API: 318.

      -- C 成員函數: void *pfunc

          The desired value of the slot.  In most cases, this is a
          pointer to a function.

          Slots other than ‘Py_tp_doc’ may not be ‘NULL’.


File: python.info,  Node: None 物件,  Prev: 型別物件,  Up: 基礎物件

7.8.1.3 ‘None’ 物件
...................

Note that the *note PyTypeObject: a48. for ‘None’ is not directly
exposed in the Python/C API. Since ‘None’ is a singleton, testing for
object identity (using ‘==’ in C) is sufficient.  There is no
‘PyNone_Check()’ function for the same reason.

 -- C 變數: *note PyObject: 311. *Py_None

     The Python ‘None’ object, denoting lack of value.  This object has
     no methods and is *note immortal: 4190.

     在 3.12 版的變更: *note Py_None: 46d6. is *note immortal: 4190.

 -- C 巨集: Py_RETURN_NONE

     Return *note Py_None: 46d6. from a function.


File: python.info,  Node: 數值物件,  Next: 序列物件,  Prev: 基礎物件,  Up: 具體物件層

7.8.2 數值物件
--------------

* Menu:

* 整數物件::
* Boolean（布林）物件::
* 浮點數（Floating-Point）物件::
* 複數物件::


File: python.info,  Node: 整數物件,  Next: Boolean（布林）物件,  Up: 數值物件

7.8.2.1 整數物件
................

All integers are implemented as "long" integer objects of arbitrary
size.

On error, most ‘PyLong_As*’ APIs return ‘(return type)-1’ which cannot
be distinguished from a number.  Use *note PyErr_Occurred(): 17f4. to
disambiguate.

 -- C 型別: type PyLongObject
     ' 為 *note 受限 API 的一部分: 4f9. （做為一個不透明結構 (opaque
     struct)）.'  This subtype of *note PyObject: 311. represents a
     Python integer object.

 -- C 變數: *note PyTypeObject: a48. PyLong_Type
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This instance of *note
     PyTypeObject: a48. represents the Python integer type.  This is the
     same object as *note int: 23c. in the Python layer.

 -- C 函式: int PyLong_Check (PyObject *p)

     Return true if its argument is a *note PyLongObject: 52e. or a
     subtype of *note PyLongObject: 52e.  This function always succeeds.

 -- C 函式: int PyLong_CheckExact (PyObject *p)

     Return true if its argument is a *note PyLongObject: 52e, but not a
     subtype of *note PyLongObject: 52e.  This function always succeeds.

 -- C 函式: *note PyObject: 311. *PyLong_FromLong (long v)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     new *note PyLongObject: 52e. object from 'v', or ‘NULL’ on failure.

     The current implementation keeps an array of integer objects for
     all integers between ‘-5’ and ‘256’.  When you create an int in
     that range you actually just get back a reference to the existing
     object.

 -- C 函式: *note PyObject: 311. *PyLong_FromUnsignedLong (unsigned long
          v)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     new *note PyLongObject: 52e. object from a C unsigned long, or
     ‘NULL’ on failure.

 -- C 函式: *note PyObject: 311. *PyLong_FromSsize_t (Py_ssize_t v)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     new *note PyLongObject: 52e. object from a C *note Py_ssize_t: a03,
     or ‘NULL’ on failure.

 -- C 函式: *note PyObject: 311. *PyLong_FromSize_t (size_t v)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     new *note PyLongObject: 52e. object from a C ‘size_t’, or ‘NULL’ on
     failure.

 -- C 函式: *note PyObject: 311. *PyLong_FromLongLong (long long v)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     new *note PyLongObject: 52e. object from a C long long, or ‘NULL’
     on failure.

 -- C 函式: *note PyObject: 311. *PyLong_FromUnsignedLongLong (unsigned
          long long v)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     new *note PyLongObject: 52e. object from a C unsigned long long, or
     ‘NULL’ on failure.

 -- C 函式: *note PyObject: 311. *PyLong_FromDouble (double v)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     new *note PyLongObject: 52e. object from the integer part of 'v',
     or ‘NULL’ on failure.

 -- C 函式: *note PyObject: 311. *PyLong_FromString (const char *str,
          char **pend, int base)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     new *note PyLongObject: 52e. based on the string value in 'str',
     which is interpreted according to the radix in 'base', or ‘NULL’ on
     failure.  If 'pend' is non-‘NULL’, '*pend' will point to the end of
     'str' on success or to the first character that could not be
     processed on error.  If 'base' is ‘0’, 'str' is interpreted using
     the *note Integer literals: 1db7. definition; in this case, leading
     zeros in a non-zero decimal number raises a *note ValueError: 1e7.
     If 'base' is not ‘0’, it must be between ‘2’ and ‘36’, inclusive.
     Leading and trailing whitespace and single underscores after a base
     specifier and between digits are ignored.  If there are no digits
     or 'str' is not NULL-terminated following the digits and trailing
     whitespace, *note ValueError: 1e7. will be raised.

     也參考
     ......

     Python methods *note int.to_bytes(): 1792. and *note
     int.from_bytes(): 1754. to convert a *note PyLongObject: 52e.
     to/from an array of bytes in base ‘256’.  You can call those from C
     using *note PyObject_CallMethod(): 366.

 -- C 函式: *note PyObject: 311. *PyLong_FromUnicodeObject (PyObject *u,
          int base)
     '回傳值：新的參照。' Convert a sequence of Unicode digits in the
     string 'u' to a Python integer value.

     在 3.3 版被加入.

 -- C 函式: *note PyObject: 311. *PyLong_FromVoidPtr (void *p)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a
     Python integer from the pointer 'p'.  The pointer value can be
     retrieved from the resulting value using *note PyLong_AsVoidPtr():
     47fb.

 -- C 函式: *note PyObject: 311. *PyLong_FromNativeBytes (const void
          *buffer, size_t n_bytes, int flags)

     Create a Python integer from the value contained in the first
     'n_bytes' of 'buffer', interpreted as a two's-complement signed
     number.

     'flags' are as for *note PyLong_AsNativeBytes(): 33a.  Passing ‘-1’
     will select the native endian that CPython was compiled with and
     assume that the most-significant bit is a sign bit.  Passing
     ‘Py_ASNATIVEBYTES_UNSIGNED_BUFFER’ will produce the same result as
     calling *note PyLong_FromUnsignedNativeBytes(): 33c.  Other flags
     are ignored.

     在 3.13 版被加入.

 -- C 函式: *note PyObject: 311. *PyLong_FromUnsignedNativeBytes (const
          void *buffer, size_t n_bytes, int flags)

     Create a Python integer from the value contained in the first
     'n_bytes' of 'buffer', interpreted as an unsigned number.

     'flags' are as for *note PyLong_AsNativeBytes(): 33a.  Passing ‘-1’
     will select the native endian that CPython was compiled with and
     assume that the most-significant bit is not a sign bit.  Flags
     other than endian are ignored.

     在 3.13 版被加入.

 -- C 函式: long PyLong_AsLong (PyObject *obj)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     Return a C long representation of 'obj'.  If 'obj' is not an
     instance of *note PyLongObject: 52e, first call its *note
     __index__(): 6c1. method (if present) to convert it to a *note
     PyLongObject: 52e.

     Raise *note OverflowError: 825. if the value of 'obj' is out of
     range for a long.

     Returns ‘-1’ on error.  Use *note PyErr_Occurred(): 17f4. to
     disambiguate.

     在 3.8 版的變更: Use *note __index__(): 6c1. if available.

     在 3.10 版的變更: This function will no longer use *note __int__():
     6c0.

 -- C 函式: int PyLong_AsInt (PyObject *obj)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Similar to
     *note PyLong_AsLong(): 316, but store the result in a C int instead
     of a C long.

     在 3.13 版被加入.

 -- C 函式: long PyLong_AsLongAndOverflow (PyObject *obj, int *overflow)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a C long representation
     of 'obj'.  If 'obj' is not an instance of *note PyLongObject: 52e,
     first call its *note __index__(): 6c1. method (if present) to
     convert it to a *note PyLongObject: 52e.

     If the value of 'obj' is greater than ‘LONG_MAX’ or less than
     ‘LONG_MIN’, set '*overflow' to ‘1’ or ‘-1’, respectively, and
     return ‘-1’; otherwise, set '*overflow' to ‘0’.  If any other
     exception occurs set '*overflow' to ‘0’ and return ‘-1’ as usual.

     Returns ‘-1’ on error.  Use *note PyErr_Occurred(): 17f4. to
     disambiguate.

     在 3.8 版的變更: Use *note __index__(): 6c1. if available.

     在 3.10 版的變更: This function will no longer use *note __int__():
     6c0.

 -- C 函式: long long PyLong_AsLongLong (PyObject *obj)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     Return a C long long representation of 'obj'.  If 'obj' is not an
     instance of *note PyLongObject: 52e, first call its *note
     __index__(): 6c1. method (if present) to convert it to a *note
     PyLongObject: 52e.

     Raise *note OverflowError: 825. if the value of 'obj' is out of
     range for a long long.

     Returns ‘-1’ on error.  Use *note PyErr_Occurred(): 17f4. to
     disambiguate.

     在 3.8 版的變更: Use *note __index__(): 6c1. if available.

     在 3.10 版的變更: This function will no longer use *note __int__():
     6c0.

 -- C 函式: long long PyLong_AsLongLongAndOverflow (PyObject *obj, int
          *overflow)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a C long long
     representation of 'obj'.  If 'obj' is not an instance of *note
     PyLongObject: 52e, first call its *note __index__(): 6c1. method
     (if present) to convert it to a *note PyLongObject: 52e.

     If the value of 'obj' is greater than ‘LLONG_MAX’ or less than
     ‘LLONG_MIN’, set '*overflow' to ‘1’ or ‘-1’, respectively, and
     return ‘-1’; otherwise, set '*overflow' to ‘0’.  If any other
     exception occurs set '*overflow' to ‘0’ and return ‘-1’ as usual.

     Returns ‘-1’ on error.  Use *note PyErr_Occurred(): 17f4. to
     disambiguate.

     在 3.2 版被加入.

     在 3.8 版的變更: Use *note __index__(): 6c1. if available.

     在 3.10 版的變更: This function will no longer use *note __int__():
     6c0.

 -- C 函式: *note Py_ssize_t: a03. PyLong_AsSsize_t (PyObject *pylong)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     Return a C *note Py_ssize_t: a03. representation of 'pylong'.
     'pylong' must be an instance of *note PyLongObject: 52e.

     Raise *note OverflowError: 825. if the value of 'pylong' is out of
     range for a *note Py_ssize_t: a03.

     Returns ‘-1’ on error.  Use *note PyErr_Occurred(): 17f4. to
     disambiguate.

 -- C 函式: unsigned long PyLong_AsUnsignedLong (PyObject *pylong)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     Return a C unsigned long representation of 'pylong'.  'pylong' must
     be an instance of *note PyLongObject: 52e.

     Raise *note OverflowError: 825. if the value of 'pylong' is out of
     range for a unsigned long.

     Returns ‘(unsigned long)-1’ on error.  Use *note PyErr_Occurred():
     17f4. to disambiguate.

 -- C 函式: size_t PyLong_AsSize_t (PyObject *pylong)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     Return a C ‘size_t’ representation of 'pylong'.  'pylong' must be
     an instance of *note PyLongObject: 52e.

     Raise *note OverflowError: 825. if the value of 'pylong' is out of
     range for a ‘size_t’.

     Returns ‘(size_t)-1’ on error.  Use *note PyErr_Occurred(): 17f4.
     to disambiguate.

 -- C 函式: unsigned long long PyLong_AsUnsignedLongLong (PyObject
          *pylong)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     Return a C unsigned long long representation of 'pylong'.  'pylong'
     must be an instance of *note PyLongObject: 52e.

     Raise *note OverflowError: 825. if the value of 'pylong' is out of
     range for an unsigned long long.

     Returns ‘(unsigned long long)-1’ on error.  Use *note
     PyErr_Occurred(): 17f4. to disambiguate.

     在 3.1 版的變更: A negative 'pylong' now raises *note
     OverflowError: 825, not *note TypeError: 4dd.

 -- C 函式: unsigned long PyLong_AsUnsignedLongMask (PyObject *obj)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a C unsigned long
     representation of 'obj'.  If 'obj' is not an instance of *note
     PyLongObject: 52e, first call its *note __index__(): 6c1. method
     (if present) to convert it to a *note PyLongObject: 52e.

     If the value of 'obj' is out of range for an unsigned long, return
     the reduction of that value modulo ‘ULONG_MAX + 1’.

     Returns ‘(unsigned long)-1’ on error.  Use *note PyErr_Occurred():
     17f4. to disambiguate.

     在 3.8 版的變更: Use *note __index__(): 6c1. if available.

     在 3.10 版的變更: This function will no longer use *note __int__():
     6c0.

 -- C 函式: unsigned long long PyLong_AsUnsignedLongLongMask (PyObject
          *obj)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a C unsigned long long
     representation of 'obj'.  If 'obj' is not an instance of *note
     PyLongObject: 52e, first call its *note __index__(): 6c1. method
     (if present) to convert it to a *note PyLongObject: 52e.

     If the value of 'obj' is out of range for an unsigned long long,
     return the reduction of that value modulo ‘ULLONG_MAX + 1’.

     Returns ‘(unsigned long long)-1’ on error.  Use *note
     PyErr_Occurred(): 17f4. to disambiguate.

     在 3.8 版的變更: Use *note __index__(): 6c1. if available.

     在 3.10 版的變更: This function will no longer use *note __int__():
     6c0.

 -- C 函式: double PyLong_AsDouble (PyObject *pylong)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a C double
     representation of 'pylong'.  'pylong' must be an instance of *note
     PyLongObject: 52e.

     Raise *note OverflowError: 825. if the value of 'pylong' is out of
     range for a double.

     Returns ‘-1.0’ on error.  Use *note PyErr_Occurred(): 17f4. to
     disambiguate.

 -- C 函式: void *PyLong_AsVoidPtr (PyObject *pylong)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Convert a Python integer
     'pylong' to a C void pointer.  If 'pylong' cannot be converted, an
     *note OverflowError: 825. will be raised.  This is only assured to
     produce a usable void pointer for values created with *note
     PyLong_FromVoidPtr(): 47fe.

     Returns ‘NULL’ on error.  Use *note PyErr_Occurred(): 17f4. to
     disambiguate.

 -- C 函式: *note Py_ssize_t: a03. PyLong_AsNativeBytes (PyObject
          *pylong, void *buffer, Py_ssize_t n_bytes, int flags)

     Copy the Python integer value 'pylong' to a native 'buffer' of size
     'n_bytes'.  The 'flags' can be set to ‘-1’ to behave similarly to a
     C cast, or to values documented below to control the behavior.

     Returns ‘-1’ with an exception raised on error.  This may happen if
     'pylong' cannot be interpreted as an integer, or if 'pylong' was
     negative and the ‘Py_ASNATIVEBYTES_REJECT_NEGATIVE’ flag was set.

     Otherwise, returns the number of bytes required to store the value.
     If this is equal to or less than 'n_bytes', the entire value was
     copied.  All 'n_bytes' of the buffer are written: large buffers are
     padded with zeroes.

     If the returned value is greater than than 'n_bytes', the value was
     truncated: as many of the lowest bits of the value as could fit are
     written, and the higher bits are ignored.  This matches the typical
     behavior of a C-style downcast.

          備註: Overflow is not considered an error.  If the returned
          value is larger than 'n_bytes', most significant bits were
          discarded.

     ‘0’ will never be returned.

     Values are always copied as two's-complement.

     Usage example:

          int32_t value;
          Py_ssize_t bytes = PyLong_AsNativeBytes(pylong, &value, sizeof(value), -1);
          if (bytes < 0) {
              // Failed. A Python exception was set with the reason.
              return NULL;
          }
          else if (bytes <= (Py_ssize_t)sizeof(value)) {
              // Success!
          }
          else {
              // Overflow occurred, but 'value' contains the truncated
              // lowest bits of pylong.
          }

     Passing zero to 'n_bytes' will return the size of a buffer that
     would be large enough to hold the value.  This may be larger than
     technically necessary, but not unreasonably so.  If 'n_bytes=0',
     'buffer' may be ‘NULL’.

          備註: Passing 'n_bytes=0' to this function is not an accurate
          way to determine the bit length of the value.

     To get at the entire Python value of an unknown size, the function
     can be called twice: first to determine the buffer size, then to
     fill it:

          // Ask how much space we need.
          Py_ssize_t expected = PyLong_AsNativeBytes(pylong, NULL, 0, -1);
          if (expected < 0) {
              // Failed. A Python exception was set with the reason.
              return NULL;
          }
          assert(expected != 0);  // Impossible per the API definition.
          uint8_t *bignum = malloc(expected);
          if (!bignum) {
              PyErr_SetString(PyExc_MemoryError, "bignum malloc failed.");
              return NULL;
          }
          // Safely get the entire value.
          Py_ssize_t bytes = PyLong_AsNativeBytes(pylong, bignum, expected, -1);
          if (bytes < 0) {  // Exception has been set.
              free(bignum);
              return NULL;
          }
          else if (bytes > expected) {  // This should not be possible.
              PyErr_SetString(PyExc_RuntimeError,
                  "Unexpected bignum truncation after a size check.");
              free(bignum);
              return NULL;
          }
          // The expected success given the above pre-check.
          // ... use bignum ...
          free(bignum);

     'flags' is either ‘-1’ (‘Py_ASNATIVEBYTES_DEFAULTS’) to select
     defaults that behave most like a C cast, or a combintation of the
     other flags in the table below.  Note that ‘-1’ cannot be combined
     with other flags.

     Currently, ‘-1’ corresponds to ‘Py_ASNATIVEBYTES_NATIVE_ENDIAN |
     Py_ASNATIVEBYTES_UNSIGNED_BUFFER’.

     Flag                                              Value
                                                       
     -------------------------------------------------------------
                                                       
      -- C 巨集: Py_ASNATIVEBYTES_DEFAULTS             ‘-1’
                                                       
                                                       
      -- C 巨集: Py_ASNATIVEBYTES_BIG_ENDIAN           ‘0’
                                                       
                                                       
      -- C 巨集: Py_ASNATIVEBYTES_LITTLE_ENDIAN        ‘1’
                                                       
                                                       
      -- C 巨集: Py_ASNATIVEBYTES_NATIVE_ENDIAN        ‘3’
                                                       
                                                       
      -- C 巨集: Py_ASNATIVEBYTES_UNSIGNED_BUFFER      ‘4’
                                                       
                                                       
      -- C 巨集: Py_ASNATIVEBYTES_REJECT_NEGATIVE      ‘8’
                                                       
                                                       
      -- C 巨集: Py_ASNATIVEBYTES_ALLOW_INDEX          ‘16’
                                                       

     Specifying ‘Py_ASNATIVEBYTES_NATIVE_ENDIAN’ will override any other
     endian flags.  Passing ‘2’ is reserved.

     By default, sufficient buffer will be requested to include a sign
     bit.  For example, when converting 128 with 'n_bytes=1', the
     function will return 2 (or more) in order to store a zero sign bit.

     If ‘Py_ASNATIVEBYTES_UNSIGNED_BUFFER’ is specified, a zero sign bit
     will be omitted from size calculations.  This allows, for example,
     128 to fit in a single-byte buffer.  If the destination buffer is
     later treated as signed, a positive input value may become
     negative.  Note that the flag does not affect handling of negative
     values: for those, space for a sign bit is always requested.

     Specifying ‘Py_ASNATIVEBYTES_REJECT_NEGATIVE’ causes an exception
     to be set if 'pylong' is negative.  Without this flag, negative
     values will be copied provided there is enough space for at least
     one sign bit, regardless of whether
     ‘Py_ASNATIVEBYTES_UNSIGNED_BUFFER’ was specified.

     If ‘Py_ASNATIVEBYTES_ALLOW_INDEX’ is specified and a non-integer
     value is passed, its *note __index__(): 6c1. method will be called
     first.  This may result in Python code executing and other threads
     being allowed to run, which could cause changes to other objects or
     values in use.  When 'flags' is ‘-1’, this option is not set, and
     non-integer values will raise *note TypeError: 4dd.

          備註: With the default 'flags' (‘-1’, or 'UNSIGNED_BUFFER'
          without 'REJECT_NEGATIVE'), multiple Python integers can map
          to a single value without overflow.  For example, both ‘255’
          and ‘-1’ fit a single-byte buffer and set all its bits.  This
          matches typical C cast behavior.

     在 3.13 版被加入.

 -- C 函式: *note PyObject: 311. *PyLong_GetInfo (void)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  On success, return a read only
     *note named tuple: 5f4, that holds information about Python's
     internal representation of integers.  See *note sys.int_info: 122b.
     for description of individual fields.

     在失敗時，會回傳 ‘NULL’ 並設定例外。

     在 3.1 版被加入.

 -- C 函式: int PyUnstable_Long_IsCompact (const PyLongObject *op)

          這是 不穩定 API，它可能在小版本發布中沒有任何警告地被變更。 '這是 *note 不穩定 API: 4ed.，它可能在小版本發布中沒有任何警告地被變更。': 
     Return 1 if 'op' is compact, 0 otherwise.

     This function makes it possible for performance-critical code to
     implement a “fast path” for small integers.  For compact values use
     *note PyUnstable_Long_CompactValue(): 530.; for others fall back to
     a *note PyLong_As*: 47f7. function or *note PyLong_AsNativeBytes():
     33a.

     The speedup is expected to be negligible for most users.

     Exactly what values are considered compact is an implementation
     detail and is subject to change.

 -- C 函式: *note Py_ssize_t: a03. PyUnstable_Long_CompactValue (const
          PyLongObject *op)

          這是 不穩定 API，它可能在小版本發布中沒有任何警告地被變更。 '這是 *note 不穩定 API: 4ed.，它可能在小版本發布中沒有任何警告地被變更。': 
     If 'op' is compact, as determined by *note
     PyUnstable_Long_IsCompact(): 52f, return its value.

     Otherwise, the return value is undefined.


File: python.info,  Node: Boolean（布林）物件,  Next: 浮點數（Floating-Point）物件,  Prev: 整數物件,  Up: 數值物件

7.8.2.2 Boolean（布林）物件
...........................

Python 中的 boolean 是以整數子類別化來實現的。只有 *note Py_False: 49ed.
和 *note Py_True: 49ee. 兩個 boolean。因此一般的建立和刪除函式並不適用於
boolean。但下列巨集 (macro) 是可用的。

 -- C 變數: *note PyTypeObject: a48. PyBool_Type
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This instance of *note
     PyTypeObject: a48. represents the Python boolean type; it is the
     same object as *note bool: 40e. in the Python layer.

 -- C 函式: int PyBool_Check (PyObject *o)

     如果 'o' 的型別為 *note PyBool_Type: 4781. 則回傳真值。此函式總是會
     成功執行。

 -- C 變數: *note PyObject: 311. *Py_False

     The Python ‘False’ object.  This object has no methods and is *note
     immortal: 4190.

     在 3.12 版的變更: *note Py_False: 49ed. is *note immortal: 4190.

 -- C 變數: *note PyObject: 311. *Py_True

     The Python ‘True’ object.  This object has no methods and is *note
     immortal: 4190.

     在 3.12 版的變更: *note Py_True: 49ee. is *note immortal: 4190.

 -- C 巨集: Py_RETURN_FALSE

     從函式回傳 *note Py_False: 49ed.。

 -- C 巨集: Py_RETURN_TRUE

     從函式回傳 *note Py_True: 49ee.。

 -- C 函式: *note PyObject: 311. *PyBool_FromLong (long v)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  根據 'v' 的
     實際值來回傳 *note Py_True: 49ee. 或者 *note Py_False: 49ed.。


File: python.info,  Node: 浮點數（Floating-Point）物件,  Next: 複數物件,  Prev: Boolean（布林）物件,  Up: 數值物件

7.8.2.3 浮點數（Floating-Point）物件
....................................

 -- C 型別: type PyFloatObject

     This subtype of *note PyObject: 311. represents a Python
     floating-point object.

 -- C 變數: *note PyTypeObject: a48. PyFloat_Type
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This instance of *note
     PyTypeObject: a48. represents the Python floating-point type.  This
     is the same object as *note float: 2c8. in the Python layer.

 -- C 函式: int PyFloat_Check (PyObject *p)

     Return true if its argument is a *note PyFloatObject: 49f3. or a
     subtype of *note PyFloatObject: 49f3.  This function always
     succeeds.

 -- C 函式: int PyFloat_CheckExact (PyObject *p)

     Return true if its argument is a *note PyFloatObject: 49f3, but not
     a subtype of *note PyFloatObject: 49f3.  This function always
     succeeds.

 -- C 函式: *note PyObject: 311. *PyFloat_FromString (PyObject *str)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a
     *note PyFloatObject: 49f3. object based on the string value in
     'str', or ‘NULL’ on failure.

 -- C 函式: *note PyObject: 311. *PyFloat_FromDouble (double v)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a
     *note PyFloatObject: 49f3. object from 'v', or ‘NULL’ on failure.

 -- C 函式: double PyFloat_AsDouble (PyObject *pyfloat)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a C double
     representation of the contents of 'pyfloat'.  If 'pyfloat' is not a
     Python floating-point object but has a *note __float__(): 970.
     method, this method will first be called to convert 'pyfloat' into
     a float.  If ‘__float__()’ is not defined then it falls back to
     *note __index__(): 6c1.  This method returns ‘-1.0’ upon failure,
     so one should call *note PyErr_Occurred(): 17f4. to check for
     errors.

     在 3.8 版的變更: Use *note __index__(): 6c1. if available.

 -- C 函式: double PyFloat_AS_DOUBLE (PyObject *pyfloat)

     Return a C double representation of the contents of 'pyfloat', but
     without error checking.

 -- C 函式: *note PyObject: 311. *PyFloat_GetInfo (void)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     structseq instance which contains information about the precision,
     minimum and maximum values of a float.  It's a thin wrapper around
     the header file ‘float.h’.

 -- C 函式: double PyFloat_GetMax ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the maximum
     representable finite float 'DBL_MAX' as C double.

 -- C 函式: double PyFloat_GetMin ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the minimum normalized
     positive float 'DBL_MIN' as C double.

* Menu:

* Pack and Unpack functions::


File: python.info,  Node: Pack and Unpack functions,  Up: 浮點數（Floating-Point）物件

7.8.2.4 Pack and Unpack functions
.................................

The pack and unpack functions provide an efficient platform-independent
way to store floating-point values as byte strings.  The Pack routines
produce a bytes string from a C double, and the Unpack routines produce
a C double from such a bytes string.  The suffix (2, 4 or 8) specifies
the number of bytes in the bytes string.

On platforms that appear to use IEEE 754 formats these functions work by
copying bits.  On other platforms, the 2-byte format is identical to the
IEEE 754 binary16 half-precision format, the 4-byte format (32-bit) is
identical to the IEEE 754 binary32 single precision format, and the
8-byte format to the IEEE 754 binary64 double precision format, although
the packing of INFs and NaNs (if such things exist on the platform)
isn't handled correctly, and attempting to unpack a bytes string
containing an IEEE INF or NaN will raise an exception.

On non-IEEE platforms with more precision, or larger dynamic range, than
IEEE 754 supports, not all values can be packed; on non-IEEE platforms
with less precision, or smaller dynamic range, not all values can be
unpacked.  What happens in such cases is partly accidental (alas).

在 3.11 版被加入.

* Menu:

* Pack functions::
* Unpack functions::


File: python.info,  Node: Pack functions,  Next: Unpack functions,  Up: Pack and Unpack functions

7.8.2.5 Pack functions
......................

The pack routines write 2, 4 or 8 bytes, starting at 'p'.  'le' is an
int argument, non-zero if you want the bytes string in little-endian
format (exponent last, at ‘p+1’, ‘p+3’, or ‘p+6’ ‘p+7’), zero if you
want big-endian format (exponent first, at 'p').  The ‘PY_BIG_ENDIAN’
constant can be used to use the native endian: it is equal to ‘1’ on big
endian processor, or ‘0’ on little endian processor.

Return value: ‘0’ if all is OK, ‘-1’ if error (and an exception is set,
most likely *note OverflowError: 825.).

There are two problems on non-IEEE platforms:

   * What this does is undefined if 'x' is a NaN or infinity.

   * ‘-0.0’ and ‘+0.0’ produce the same bytes string.

 -- C 函式: int PyFloat_Pack2 (double x, unsigned char *p, int le)

     Pack a C double as the IEEE 754 binary16 half-precision format.

 -- C 函式: int PyFloat_Pack4 (double x, unsigned char *p, int le)

     Pack a C double as the IEEE 754 binary32 single precision format.

 -- C 函式: int PyFloat_Pack8 (double x, unsigned char *p, int le)

     Pack a C double as the IEEE 754 binary64 double precision format.


File: python.info,  Node: Unpack functions,  Prev: Pack functions,  Up: Pack and Unpack functions

7.8.2.6 Unpack functions
........................

The unpack routines read 2, 4 or 8 bytes, starting at 'p'.  'le' is an
int argument, non-zero if the bytes string is in little-endian format
(exponent last, at ‘p+1’, ‘p+3’ or ‘p+6’ and ‘p+7’), zero if big-endian
(exponent first, at 'p').  The ‘PY_BIG_ENDIAN’ constant can be used to
use the native endian: it is equal to ‘1’ on big endian processor, or
‘0’ on little endian processor.

Return value: The unpacked double.  On error, this is ‘-1.0’ and *note
PyErr_Occurred(): 17f4. is true (and an exception is set, most likely
*note OverflowError: 825.).

Note that on a non-IEEE platform this will refuse to unpack a bytes
string that represents a NaN or infinity.

 -- C 函式: double PyFloat_Unpack2 (const unsigned char *p, int le)

     Unpack the IEEE 754 binary16 half-precision format as a C double.

 -- C 函式: double PyFloat_Unpack4 (const unsigned char *p, int le)

     Unpack the IEEE 754 binary32 single precision format as a C double.

 -- C 函式: double PyFloat_Unpack8 (const unsigned char *p, int le)

     Unpack the IEEE 754 binary64 double precision format as a C double.


File: python.info,  Node: 複數物件,  Prev: 浮點數（Floating-Point）物件,  Up: 數值物件

7.8.2.7 複數物件
................

從 C API 來看，Python 的複數物件被實作為兩種不同的型別：一種是公開給
Python 程式的 Python 物件，另一種是表示實際複數值的 C 結構。API 提供了與
兩者一起作用的函式。

* Menu:

* 作為 C 結構的複數::
* 作為 Python 物件的複數::


File: python.info,  Node: 作為 C 結構的複數,  Next: 作為 Python 物件的複數,  Up: 複數物件

7.8.2.8 作為 C 結構的複數
.........................

請注意，接受這些結構作為參數並將它們作為結果回傳的函式是'按值 (by
value)' 執行的，而不是透過指標取消參照 (dereference) 它們。這在整個 API
中都是一致的。

 -- C 型別: type Py_complex

     相對於 Python 複數物件之數值部分的 C 結構。大多數處理複數物件的函式
     根據需求會使用這種型別的結構作為輸入或輸出值。

      -- C 成員函數: double real
      -- C 成員函數: double imag

     該結構被定義為：

          typedef struct {
              double real;
              double imag;
          } Py_complex;

 -- C 函式: *note Py_complex: 4933. _Py_c_sum (Py_complex left,
          Py_complex right)

     以 C 的 *note Py_complex: 4933. 表示形式來回傳兩個複數之和。

 -- C 函式: *note Py_complex: 4933. _Py_c_diff (Py_complex left,
          Py_complex right)

     以 C 的 *note Py_complex: 4933. 表示形式來回傳兩個複數間的差。

 -- C 函式: *note Py_complex: 4933. _Py_c_neg (Py_complex num)

     以 C 的 *note Py_complex: 4933. 表示形式來回傳複數 'num' 的相反數
     (negation)。

 -- C 函式: *note Py_complex: 4933. _Py_c_prod (Py_complex left,
          Py_complex right)

     以 C 的 *note Py_complex: 4933. 表示形式來回傳兩個複數的乘積。

 -- C 函式: *note Py_complex: 4933. _Py_c_quot (Py_complex dividend,
          Py_complex divisor)

     以 C 的 *note Py_complex: 4933. 表示形式來回傳兩個複數的商。

     如果 'divisor' 為 null，則此方法會回傳零並將 ‘errno’ 設定為 ‘EDOM’。

 -- C 函式: *note Py_complex: 4933. _Py_c_pow (Py_complex num,
          Py_complex exp)

     以 C 的 *note Py_complex: 4933. 表示形式來回傳 'num' 的 'exp' 次方
     的結果。

     如果 'num' 為 null 且 'exp' 不是正實數，則此方法會回傳零並將
     ‘errno’ 設定為 ‘EDOM’。


File: python.info,  Node: 作為 Python 物件的複數,  Prev: 作為 C 結構的複數,  Up: 複數物件

7.8.2.9 作為 Python 物件的複數
..............................

 -- C 型別: type PyComplexObject

     這個 *note PyObject: 311. 的子型別代表一個 Python 複數物件。

 -- C 變數: *note PyTypeObject: a48. PyComplex_Type
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  這個 *note PyTypeObject: a48.
     的實例代表 Python 複數型別。它與 Python 層中的 *note complex: 2c9.
     是同一個物件。

 -- C 函式: int PyComplex_Check (PyObject *p)

     如果其引數是一個 *note PyComplexObject: 4a07. 或者是 *note
     PyComplexObject: 4a07. 的子型別，則會回傳 true。這個函式不會失敗。

 -- C 函式: int PyComplex_CheckExact (PyObject *p)

     如果其引數是一個 *note PyComplexObject: 4a07.，但不是 *note
     PyComplexObject: 4a07. 的子型別，則會回傳 true。這個函式不會失敗。

 -- C 函式: *note PyObject: 311. *PyComplex_FromCComplex (Py_complex v)
     '回傳值：新的參照。' 從 C 的 *note Py_complex: 4933. 值建立一個新的
     Python 複數物件。在錯誤時回傳 ‘NULL’ 並設定例外。

 -- C 函式: *note PyObject: 311. *PyComplex_FromDoubles (double real,
          double imag)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  從 'real'
     和 'imag' 回傳一個新的 *note PyComplexObject: 4a07. 物件。在錯誤時
     回傳 ‘NULL’ 並設定例外。

 -- C 函式: double PyComplex_RealAsDouble (PyObject *op)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  以 C 的 double 形式回傳 'op' 的
     實部。

     If 'op' is not a Python complex number object but has a *note
     __complex__(): 58d. method, this method will first be called to
     convert 'op' to a Python complex number object.  If ‘__complex__()’
     is not defined then it falls back to call *note PyFloat_AsDouble():
     a0c. and returns its result.

     失敗時，此方法回傳 ‘-1.0’ 並設定例外，因此應該呼叫 *note
     PyErr_Occurred(): 17f4. 來檢查錯誤。

     在 3.13 版的變更: Use *note __complex__(): 58d. if available.

 -- C 函式: double PyComplex_ImagAsDouble (PyObject *op)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  將 'op' 的虛部作為 C 的 double
     回傳。

     If 'op' is not a Python complex number object but has a *note
     __complex__(): 58d. method, this method will first be called to
     convert 'op' to a Python complex number object.  If ‘__complex__()’
     is not defined then it falls back to call *note PyFloat_AsDouble():
     a0c. and returns ‘0.0’ on success.

     失敗時，此方法回傳 ‘-1.0’ 並設定例外，因此應該呼叫 *note
     PyErr_Occurred(): 17f4. 來檢查錯誤。

     在 3.13 版的變更: Use *note __complex__(): 58d. if available.

 -- C 函式: *note Py_complex: 4933. PyComplex_AsCComplex (PyObject *op)

     回傳複數 'op' 的 *note Py_complex: 4933. 值。

     如果 'op' 不是 Python 複數物件，但有一個 *note __complex__(): 58d.
     方法，則首先會呼叫該方法將 'op' 轉換為 Python 複數物件。如果
     ‘__complex__()’ 並未定義，那麼它會回退到 *note __float__(): 970.。
     如果 ‘__float__()’ 未定義，則它將繼續回退為 *note __index__():
     6c1.。

     失敗時，此方法回傳 *note Py_complex: 4933. 並將 *note real: 49fe. 設
     為 ‘-1.0’，並設定例外，因此應該呼叫 *note PyErr_Occurred(): 17f4. 來
     檢查錯誤。

     在 3.8 版的變更: 如果可用則使用 *note __index__(): 6c1.。


File: python.info,  Node: 序列物件,  Next: 容器物件,  Prev: 數值物件,  Up: 具體物件層

7.8.3 序列物件
--------------

序列物件的一般操作在前一章節討論過了；此段落將討論 Python 語言特有的特定
型別序列物件。

* Menu:

* 位元組物件 (Bytes Objects): 位元組物件 Bytes Objects.
* 位元組陣列物件 (Byte Array Objects): 位元組陣列物件 Byte Array Objects.
* Unicode 物件與編解碼器::
* Tuple（元組）物件::
* Struct Sequence Objects::
* List（串列）物件::


File: python.info,  Node: 位元組物件 Bytes Objects,  Next: 位元組陣列物件 Byte Array Objects,  Up: 序列物件

7.8.3.1 位元組物件 (Bytes Objects)
..................................

These functions raise *note TypeError: 4dd. when expecting a bytes
parameter and called with a non-bytes parameter.

 -- C 型別: type PyBytesObject

     This subtype of *note PyObject: 311. represents a Python bytes
     object.

 -- C 變數: *note PyTypeObject: a48. PyBytes_Type
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This instance of *note
     PyTypeObject: a48. represents the Python bytes type; it is the same
     object as *note bytes: 1a5. in the Python layer.

 -- C 函式: int PyBytes_Check (PyObject *o)

     Return true if the object 'o' is a bytes object or an instance of a
     subtype of the bytes type.  This function always succeeds.

 -- C 函式: int PyBytes_CheckExact (PyObject *o)

     Return true if the object 'o' is a bytes object, but not an
     instance of a subtype of the bytes type.  This function always
     succeeds.

 -- C 函式: *note PyObject: 311. *PyBytes_FromString (const char *v)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     new bytes object with a copy of the string 'v' as value on success,
     and ‘NULL’ on failure.  The parameter 'v' must not be ‘NULL’; it
     will not be checked.

 -- C 函式: *note PyObject: 311. *PyBytes_FromStringAndSize (const char
          *v, Py_ssize_t len)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     new bytes object with a copy of the string 'v' as value and length
     'len' on success, and ‘NULL’ on failure.  If 'v' is ‘NULL’, the
     contents of the bytes object are uninitialized.

 -- C 函式: *note PyObject: 311. *PyBytes_FromFormat (const char
          *format, ...)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Take a C
     ‘printf()’-style 'format' string and a variable number of
     arguments, calculate the size of the resulting Python bytes object
     and return a bytes object with the values formatted into it.  The
     variable arguments must be C types and must correspond exactly to
     the format characters in the 'format' string.  The following format
     characters are allowed:

     Format Characters       Type                Comment
                                                 
     ---------------------------------------------------------------------------------
                                                 
     ‘%%’                    'n/a'               The literal % character.
                                                 
                                                 
     ‘%c’                    int                 A single byte, represented as a C
                                                 int.
                                                 
                                                 
     ‘%d’                    int                 等價於 ‘printf("%d")’.  (1)
                                                 
                                                 
     ‘%u’                    unsigned int        等價於 ‘printf("%u")’.  (2)
                                                 
                                                 
     ‘%ld’                   long                等價於 ‘printf("%ld")’.  (3)
                                                 
                                                 
     ‘%lu’                   unsigned long       等價於 ‘printf("%lu")’.  (4)
                                                 
                                                 
     ‘%zd’                   *note Py_ssize_t: a03.等價於 ‘printf("%zd")’.  (5)
                                                 
                                                 
     ‘%zu’                   size_t              等價於 ‘printf("%zu")’.  (6)
                                                 
                                                 
     ‘%i’                    int                 等價於 ‘printf("%i")’.  (7)
                                                 
                                                 
     ‘%x’                    int                 等價於 ‘printf("%x")’.  (8)
                                                 
                                                 
     ‘%s’                    const char*         A null-terminated C character
                                                 array.
                                                 
                                                 
     ‘%p’                    const void*         The hex representation of a C
                                                 pointer.  Mostly equivalent to
                                                 ‘printf("%p")’ except that it is
                                                 guaranteed to start with the
                                                 literal ‘0x’ regardless of what
                                                 the platform's ‘printf’ yields.
                                                 

     An unrecognized format character causes all the rest of the format
     string to be copied as-is to the result object, and any extra
     arguments discarded.

 -- C 函式: *note PyObject: 311. *PyBytes_FromFormatV (const char
          *format, va_list vargs)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Identical
     to *note PyBytes_FromFormat(): 192f. except that it takes exactly
     two arguments.

 -- C 函式: *note PyObject: 311. *PyBytes_FromObject (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the
     bytes representation of object 'o' that implements the buffer
     protocol.

 -- C 函式: *note Py_ssize_t: a03. PyBytes_Size (PyObject *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the length of the bytes
     in bytes object 'o'.

 -- C 函式: *note Py_ssize_t: a03. PyBytes_GET_SIZE (PyObject *o)

     Similar to *note PyBytes_Size(): 478d, but without error checking.

 -- C 函式: char *PyBytes_AsString (PyObject *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a pointer to the
     contents of 'o'.  The pointer refers to the internal buffer of 'o',
     which consists of ‘len(o) + 1’ bytes.  The last byte in the buffer
     is always null, regardless of whether there are any other null
     bytes.  The data must not be modified in any way, unless the object
     was just created using ‘PyBytes_FromStringAndSize(NULL, size)’.  It
     must not be deallocated.  If 'o' is not a bytes object at all,
     *note PyBytes_AsString(): 82b. returns ‘NULL’ and raises *note
     TypeError: 4dd.

 -- C 函式: char *PyBytes_AS_STRING (PyObject *string)

     Similar to *note PyBytes_AsString(): 82b, but without error
     checking.

 -- C 函式: int PyBytes_AsStringAndSize (PyObject *obj, char **buffer,
          Py_ssize_t *length)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the null-terminated
     contents of the object 'obj' through the output variables 'buffer'
     and 'length'.  Returns ‘0’ on success.

     If 'length' is ‘NULL’, the bytes object may not contain embedded
     null bytes; if it does, the function returns ‘-1’ and a *note
     ValueError: 1e7. is raised.

     The buffer refers to an internal buffer of 'obj', which includes an
     additional null byte at the end (not counted in 'length').  The
     data must not be modified in any way, unless the object was just
     created using ‘PyBytes_FromStringAndSize(NULL, size)’.  It must not
     be deallocated.  If 'obj' is not a bytes object at all, *note
     PyBytes_AsStringAndSize(): 4787. returns ‘-1’ and raises *note
     TypeError: 4dd.

     在 3.5 版的變更: Previously, *note TypeError: 4dd. was raised when
     embedded null bytes were encountered in the bytes object.

 -- C 函式: void PyBytes_Concat (PyObject **bytes, PyObject *newpart)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a new bytes object in
     '*bytes' containing the contents of 'newpart' appended to 'bytes';
     the caller will own the new reference.  The reference to the old
     value of 'bytes' will be stolen.  If the new object cannot be
     created, the old reference to 'bytes' will still be discarded and
     the value of '*bytes' will be set to ‘NULL’; the appropriate
     exception will be set.

 -- C 函式: void PyBytes_ConcatAndDel (PyObject **bytes, PyObject
          *newpart)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a new bytes object in
     '*bytes' containing the contents of 'newpart' appended to 'bytes'.
     This version releases the *note strong reference: 2ee. to 'newpart'
     (i.e.  decrements its reference count).

 -- C 函式: int _PyBytes_Resize (PyObject **bytes, Py_ssize_t newsize)

     Resize a bytes object.  'newsize' will be the new length of the
     bytes object.  You can think of it as creating a new bytes object
     and destroying the old one, only more efficiently.  Pass the
     address of an existing bytes object as an lvalue (it may be written
     into), and the new size desired.  On success, '*bytes' holds the
     resized bytes object and ‘0’ is returned; the address in '*bytes'
     may differ from its input value.  If the reallocation fails, the
     original bytes object at '*bytes' is deallocated, '*bytes' is set
     to ‘NULL’, *note MemoryError: 15bc. is set, and ‘-1’ is returned.

   ---------- Footnotes ----------

   (1) For integer specifiers (d, u, ld, lu, zd, zu, i, x): the
0-conversion flag has effect even when a precision is given.

   (2) For integer specifiers (d, u, ld, lu, zd, zu, i, x): the
0-conversion flag has effect even when a precision is given.

   (3) For integer specifiers (d, u, ld, lu, zd, zu, i, x): the
0-conversion flag has effect even when a precision is given.

   (4) For integer specifiers (d, u, ld, lu, zd, zu, i, x): the
0-conversion flag has effect even when a precision is given.

   (5) For integer specifiers (d, u, ld, lu, zd, zu, i, x): the
0-conversion flag has effect even when a precision is given.

   (6) For integer specifiers (d, u, ld, lu, zd, zu, i, x): the
0-conversion flag has effect even when a precision is given.

   (7) For integer specifiers (d, u, ld, lu, zd, zu, i, x): the
0-conversion flag has effect even when a precision is given.

   (8) For integer specifiers (d, u, ld, lu, zd, zu, i, x): the
0-conversion flag has effect even when a precision is given.


File: python.info,  Node: 位元組陣列物件 Byte Array Objects,  Next: Unicode 物件與編解碼器,  Prev: 位元組物件 Bytes Objects,  Up: 序列物件

7.8.3.2 位元組陣列物件 (Byte Array Objects)
...........................................

 -- C 型別: type PyByteArrayObject

     這個 *note PyObject: 311. 的子型別代表了 Python 的位元組陣列物件。

 -- C 變數: *note PyTypeObject: a48. PyByteArray_Type
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  這個 *note PyTypeObject: a48.
     的實例代表了 Python 的位元組陣列型別；在 Python 層中的 *note
     bytearray: 4e3. 為同一個物件。

* Menu:

* 型別檢查巨集::
* 直接 API 函式::
* 巨集::


File: python.info,  Node: 型別檢查巨集,  Next: 直接 API 函式,  Up: 位元組陣列物件 Byte Array Objects

7.8.3.3 型別檢查巨集
....................

 -- C 函式: int PyByteArray_Check (PyObject *o)

     如果物件 'o' 是一個位元組陣列物件，或者是位元組陣列型別的子型別的實
     例，則回傳真值。此函式總是會成功執行。

 -- C 函式: int PyByteArray_CheckExact (PyObject *o)

     如果物件 'o' 是一個位元組陣列物件，但不是位元組陣列型別的子型別的實
     例，則回傳真值。此函式總是會成功執行。


File: python.info,  Node: 直接 API 函式,  Next: 巨集,  Prev: 型別檢查巨集,  Up: 位元組陣列物件 Byte Array Objects

7.8.3.4 直接 API 函式
.....................

 -- C 函式: *note PyObject: 311. *PyByteArray_FromObject (PyObject *o)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  由任意物件
     'o' 回傳一個新的位元組陣列物件，並實作了*note 緩衝協議 (buffer
     protocol): 367.。

     在失敗時，會回傳 ‘NULL’ 並設定例外。

 -- C 函式: *note PyObject: 311. *PyByteArray_FromStringAndSize (const
          char *string, Py_ssize_t len)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  從
     'string' 及其長度 'len' 建立一個新的位元組陣列物件。

     在失敗時，會回傳 ‘NULL’ 並設定例外。

 -- C 函式: *note PyObject: 311. *PyByteArray_Concat (PyObject *a,
          PyObject *b)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  連接位元組
     陣列 'a' 和 'b'，並回傳一個包含結果的新位元組陣列。

     在失敗時，會回傳 ‘NULL’ 並設定例外。

 -- C 函式: *note Py_ssize_t: a03. PyByteArray_Size (PyObject
          *bytearray)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  在檢查為 ‘NULL’ 指標後，回傳
     'bytearray' 的大小。

 -- C 函式: char *PyByteArray_AsString (PyObject *bytearray)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  在檢查是否為 ‘NULL’ 指標後，將
     'bytearray' 的內容回傳為字元陣列。回傳的陣列總是會多附加一個空位元
     組。

 -- C 函式: int PyByteArray_Resize (PyObject *bytearray, Py_ssize_t len)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  將 'bytearray' 的內部緩衝區大
     小調整為 'len'。


File: python.info,  Node: 巨集,  Prev: 直接 API 函式,  Up: 位元組陣列物件 Byte Array Objects

7.8.3.5 巨集
............

這些巨集犧牲了安全性以換取速度，並且它們不會檢查指標。

 -- C 函式: char *PyByteArray_AS_STRING (PyObject *bytearray)

     與 *note PyByteArray_AsString(): 4782. 類似，但沒有錯誤檢查。

 -- C 函式: *note Py_ssize_t: a03. PyByteArray_GET_SIZE (PyObject
          *bytearray)

     與 *note PyByteArray_Size(): 4785. 類似，但沒有錯誤檢查。


File: python.info,  Node: Unicode 物件與編解碼器,  Next: Tuple（元組）物件,  Prev: 位元組陣列物件 Byte Array Objects,  Up: 序列物件

7.8.3.6 Unicode 物件與編解碼器
..............................

* Menu:

* Unicode 物件::
* Built-in Codecs::
* Methods and Slot Functions::


File: python.info,  Node: Unicode 物件,  Next: Built-in Codecs,  Up: Unicode 物件與編解碼器

7.8.3.7 Unicode 物件
....................

Since the implementation of PEP 393(1) in Python 3.3, Unicode objects
internally use a variety of representations, in order to allow handling
the complete range of Unicode characters while staying memory efficient.
There are special cases for strings where all code points are below 128,
256, or 65536; otherwise, code points must be below 1114112 (which is
the full Unicode range).

UTF-8 representation is created on demand and cached in the Unicode
object.

     備註: The *note Py_UNICODE: 3b8. representation has been removed
     since Python 3.12 with deprecated APIs.  See PEP 623(2) for more
     information.

* Menu:

* Unicode Type::
* Unicode Character Properties::
* Creating and accessing Unicode strings::
* Locale Encoding::
* File System Encoding::
* wchar_t 支援::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0393/

   (2) https://peps.python.org/pep-0623/


File: python.info,  Node: Unicode Type,  Next: Unicode Character Properties,  Up: Unicode 物件

7.8.3.8 Unicode Type
....................

These are the basic Unicode object types used for the Unicode
implementation in Python:

 -- C 型別: type Py_UCS4
 -- C 型別: type Py_UCS2
 -- C 型別: type Py_UCS1
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  These types are typedefs for
     unsigned integer types wide enough to contain characters of 32
     bits, 16 bits and 8 bits, respectively.  When dealing with single
     Unicode characters, use *note Py_UCS4: 110e.

     在 3.3 版被加入.

 -- C 型別: type Py_UNICODE

     This is a typedef of ‘wchar_t’, which is a 16-bit type or 32-bit
     type depending on the platform.

     在 3.3 版的變更: In previous versions, this was a 16-bit type or a
     32-bit type depending on whether you selected a "narrow" or "wide"
     Unicode version of Python at build time.

     Deprecated since version 3.13, will be removed in version 3.15.

 -- C 型別: type PyASCIIObject
 -- C 型別: type PyCompactUnicodeObject
 -- C 型別: type PyUnicodeObject

     These subtypes of *note PyObject: 311. represent a Python Unicode
     object.  In almost all cases, they shouldn't be used directly,
     since all API functions that deal with Unicode objects take and
     return *note PyObject: 311. pointers.

     在 3.3 版被加入.

 -- C 變數: *note PyTypeObject: a48. PyUnicode_Type
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This instance of *note
     PyTypeObject: a48. represents the Python Unicode type.  It is
     exposed to Python code as ‘str’.

The following APIs are C macros and static inlined functions for fast
checks and access to internal read-only data of Unicode objects:

 -- C 函式: int PyUnicode_Check (PyObject *obj)

     Return true if the object 'obj' is a Unicode object or an instance
     of a Unicode subtype.  This function always succeeds.

 -- C 函式: int PyUnicode_CheckExact (PyObject *obj)

     Return true if the object 'obj' is a Unicode object, but not an
     instance of a subtype.  This function always succeeds.

 -- C 函式: int PyUnicode_READY (PyObject *unicode)

     Returns ‘0’.  This API is kept only for backward compatibility.

     在 3.3 版被加入.

     在 3.10 版之後被棄用: This API does nothing since Python 3.12.

 -- C 函式: *note Py_ssize_t: a03. PyUnicode_GET_LENGTH (PyObject
          *unicode)

     Return the length of the Unicode string, in code points.  'unicode'
     has to be a Unicode object in the "canonical" representation (not
     checked).

     在 3.3 版被加入.

 -- C 函式: *note Py_UCS1: 110c. *PyUnicode_1BYTE_DATA (PyObject
          *unicode)
 -- C 函式: *note Py_UCS2: 110d. *PyUnicode_2BYTE_DATA (PyObject
          *unicode)
 -- C 函式: *note Py_UCS4: 110e. *PyUnicode_4BYTE_DATA (PyObject
          *unicode)

     Return a pointer to the canonical representation cast to UCS1, UCS2
     or UCS4 integer types for direct character access.  No checks are
     performed if the canonical representation has the correct character
     size; use *note PyUnicode_KIND(): 1117. to select the right
     function.

     在 3.3 版被加入.

 -- C 巨集: PyUnicode_1BYTE_KIND
 -- C 巨集: PyUnicode_2BYTE_KIND
 -- C 巨集: PyUnicode_4BYTE_KIND

     Return values of the *note PyUnicode_KIND(): 1117. macro.

     在 3.3 版被加入.

     在 3.12 版的變更: ‘PyUnicode_WCHAR_KIND’ 已被移除。

 -- C 函式: int PyUnicode_KIND (PyObject *unicode)

     Return one of the PyUnicode kind constants (see above) that
     indicate how many bytes per character this Unicode object uses to
     store its data.  'unicode' has to be a Unicode object in the
     "canonical" representation (not checked).

     在 3.3 版被加入.

 -- C 函式: void *PyUnicode_DATA (PyObject *unicode)

     Return a void pointer to the raw Unicode buffer.  'unicode' has to
     be a Unicode object in the "canonical" representation (not
     checked).

     在 3.3 版被加入.

 -- C 函式: void PyUnicode_WRITE (int kind, void *data, Py_ssize_t
          index, Py_UCS4 value)

     Write into a canonical representation 'data' (as obtained with
     *note PyUnicode_DATA(): 1113.).  This function performs no sanity
     checks, and is intended for usage in loops.  The caller should
     cache the 'kind' value and 'data' pointer as obtained from other
     calls.  'index' is the index in the string (starts at 0) and
     'value' is the new code point value which should be written to that
     location.

     在 3.3 版被加入.

 -- C 函式: *note Py_UCS4: 110e. PyUnicode_READ (int kind, void *data,
          Py_ssize_t index)

     Read a code point from a canonical representation 'data' (as
     obtained with *note PyUnicode_DATA(): 1113.).  No checks or ready
     calls are performed.

     在 3.3 版被加入.

 -- C 函式: *note Py_UCS4: 110e. PyUnicode_READ_CHAR (PyObject *unicode,
          Py_ssize_t index)

     Read a character from a Unicode object 'unicode', which must be in
     the "canonical" representation.  This is less efficient than *note
     PyUnicode_READ(): 111b. if you do multiple consecutive reads.

     在 3.3 版被加入.

 -- C 函式: *note Py_UCS4: 110e. PyUnicode_MAX_CHAR_VALUE (PyObject
          *unicode)

     Return the maximum code point that is suitable for creating another
     string based on 'unicode', which must be in the "canonical"
     representation.  This is always an approximation but more efficient
     than iterating over the string.

     在 3.3 版被加入.

 -- C 函式: int PyUnicode_IsIdentifier (PyObject *unicode)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return ‘1’ if the string is a
     valid identifier according to the language definition, section
     *note Identifiers and keywords: 1d86.  Return ‘0’ otherwise.

     在 3.9 版的變更: The function does not call *note Py_FatalError():
     927. anymore if the string is not ready.


File: python.info,  Node: Unicode Character Properties,  Next: Creating and accessing Unicode strings,  Prev: Unicode Type,  Up: Unicode 物件

7.8.3.9 Unicode Character Properties
....................................

Unicode provides many different character properties.  The most often
needed ones are available through these macros which are mapped to C
functions depending on the Python configuration.

 -- C 函式: int Py_UNICODE_ISSPACE (Py_UCS4 ch)

     Return ‘1’ or ‘0’ depending on whether 'ch' is a whitespace
     character.

 -- C 函式: int Py_UNICODE_ISLOWER (Py_UCS4 ch)

     Return ‘1’ or ‘0’ depending on whether 'ch' is a lowercase
     character.

 -- C 函式: int Py_UNICODE_ISUPPER (Py_UCS4 ch)

     Return ‘1’ or ‘0’ depending on whether 'ch' is an uppercase
     character.

 -- C 函式: int Py_UNICODE_ISTITLE (Py_UCS4 ch)

     Return ‘1’ or ‘0’ depending on whether 'ch' is a titlecase
     character.

 -- C 函式: int Py_UNICODE_ISLINEBREAK (Py_UCS4 ch)

     Return ‘1’ or ‘0’ depending on whether 'ch' is a linebreak
     character.

 -- C 函式: int Py_UNICODE_ISDECIMAL (Py_UCS4 ch)

     Return ‘1’ or ‘0’ depending on whether 'ch' is a decimal character.

 -- C 函式: int Py_UNICODE_ISDIGIT (Py_UCS4 ch)

     Return ‘1’ or ‘0’ depending on whether 'ch' is a digit character.

 -- C 函式: int Py_UNICODE_ISNUMERIC (Py_UCS4 ch)

     Return ‘1’ or ‘0’ depending on whether 'ch' is a numeric character.

 -- C 函式: int Py_UNICODE_ISALPHA (Py_UCS4 ch)

     Return ‘1’ or ‘0’ depending on whether 'ch' is an alphabetic
     character.

 -- C 函式: int Py_UNICODE_ISALNUM (Py_UCS4 ch)

     Return ‘1’ or ‘0’ depending on whether 'ch' is an alphanumeric
     character.

 -- C 函式: int Py_UNICODE_ISPRINTABLE (Py_UCS4 ch)

     Return ‘1’ or ‘0’ depending on whether 'ch' is a printable
     character.  Nonprintable characters are those characters defined in
     the Unicode character database as "Other" or "Separator", excepting
     the ASCII space (0x20) which is considered printable.  (Note that
     printable characters in this context are those which should not be
     escaped when *note repr(): 7a1. is invoked on a string.  It has no
     bearing on the handling of strings written to *note sys.stdout:
     a79. or *note sys.stderr: 8dd.)

These APIs can be used for fast direct character conversions:

 -- C 函式: *note Py_UCS4: 110e. Py_UNICODE_TOLOWER (Py_UCS4 ch)

     Return the character 'ch' converted to lower case.

 -- C 函式: *note Py_UCS4: 110e. Py_UNICODE_TOUPPER (Py_UCS4 ch)

     Return the character 'ch' converted to upper case.

 -- C 函式: *note Py_UCS4: 110e. Py_UNICODE_TOTITLE (Py_UCS4 ch)

     Return the character 'ch' converted to title case.

 -- C 函式: int Py_UNICODE_TODECIMAL (Py_UCS4 ch)

     Return the character 'ch' converted to a decimal positive integer.
     Return ‘-1’ if this is not possible.  This function does not raise
     exceptions.

 -- C 函式: int Py_UNICODE_TODIGIT (Py_UCS4 ch)

     Return the character 'ch' converted to a single digit integer.
     Return ‘-1’ if this is not possible.  This function does not raise
     exceptions.

 -- C 函式: double Py_UNICODE_TONUMERIC (Py_UCS4 ch)

     Return the character 'ch' converted to a double.  Return ‘-1.0’ if
     this is not possible.  This function does not raise exceptions.

These APIs can be used to work with surrogates:

 -- C 函式: int Py_UNICODE_IS_SURROGATE (Py_UCS4 ch)

     Check if 'ch' is a surrogate (‘0xD800 <= ch <= 0xDFFF’).

 -- C 函式: int Py_UNICODE_IS_HIGH_SURROGATE (Py_UCS4 ch)

     Check if 'ch' is a high surrogate (‘0xD800 <= ch <= 0xDBFF’).

 -- C 函式: int Py_UNICODE_IS_LOW_SURROGATE (Py_UCS4 ch)

     Check if 'ch' is a low surrogate (‘0xDC00 <= ch <= 0xDFFF’).

 -- C 函式: *note Py_UCS4: 110e. Py_UNICODE_JOIN_SURROGATES (Py_UCS4
          high, Py_UCS4 low)

     Join two surrogate characters and return a single *note Py_UCS4:
     110e. value.  'high' and 'low' are respectively the leading and
     trailing surrogates in a surrogate pair.  'high' must be in the
     range [0xD800; 0xDBFF] and 'low' must be in the range [0xDC00;
     0xDFFF].


File: python.info,  Node: Creating and accessing Unicode strings,  Next: Locale Encoding,  Prev: Unicode Character Properties,  Up: Unicode 物件

7.8.3.10 Creating and accessing Unicode strings
...............................................

To create Unicode objects and access their basic sequence properties,
use these APIs:

 -- C 函式: *note PyObject: 311. *PyUnicode_New (Py_ssize_t size,
          Py_UCS4 maxchar)
     '回傳值：新的參照。' Create a new Unicode object.  'maxchar' should
     be the true maximum code point to be placed in the string.  As an
     approximation, it can be rounded up to the nearest value in the
     sequence 127, 255, 65535, 1114111.

     This is the recommended way to allocate a new Unicode object.
     Objects created using this function are not resizable.

     在 3.3 版被加入.

 -- C 函式: *note PyObject: 311. *PyUnicode_FromKindAndData (int kind,
          const void *buffer, Py_ssize_t size)
     '回傳值：新的參照。' Create a new Unicode object with the given
     'kind' (possible values are *note PyUnicode_1BYTE_KIND: 1118. etc.,
     as returned by *note PyUnicode_KIND(): 1117.).  The 'buffer' must
     point to an array of 'size' units of 1, 2 or 4 bytes per character,
     as given by the kind.

     If necessary, the input 'buffer' is copied and transformed into the
     canonical representation.  For example, if the 'buffer' is a UCS4
     string (*note PyUnicode_4BYTE_KIND: 111a.) and it consists only of
     codepoints in the UCS1 range, it will be transformed into UCS1
     (*note PyUnicode_1BYTE_KIND: 1118.).

     在 3.3 版被加入.

 -- C 函式: *note PyObject: 311. *PyUnicode_FromStringAndSize (const
          char *str, Py_ssize_t size)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a
     Unicode object from the char buffer 'str'.  The bytes will be
     interpreted as being UTF-8 encoded.  The buffer is copied into the
     new object.  The return value might be a shared object, i.e.
     modification of the data is not allowed.

     This function raises *note SystemError: 51b. when:

        * 'size' < 0,

        * 'str' is ‘NULL’ and 'size' > 0

     在 3.12 版的變更: 'str' == ‘NULL’ with 'size' > 0 is not allowed
     anymore.

 -- C 函式: *note PyObject: 311. *PyUnicode_FromString (const char *str)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a
     Unicode object from a UTF-8 encoded null-terminated char buffer
     'str'.

 -- C 函式: *note PyObject: 311. *PyUnicode_FromFormat (const char
          *format, ...)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Take a C
     ‘printf()’-style 'format' string and a variable number of
     arguments, calculate the size of the resulting Python Unicode
     string and return a string with the values formatted into it.  The
     variable arguments must be C types and must correspond exactly to
     the format characters in the 'format' ASCII-encoded string.

     A conversion specifier contains two or more characters and has the
     following components, which must occur in this order:

       1. The ‘'%'’ character, which marks the start of the specifier.

       2. Conversion flags (optional), which affect the result of some
          conversion types.

       3. Minimum field width (optional).  If specified as an ‘'*'’
          (asterisk), the actual width is given in the next argument,
          which must be of type int, and the object to convert comes
          after the minimum field width and optional precision.

       4. Precision (optional), given as a ‘'.'’ (dot) followed by the
          precision.  If specified as ‘'*'’ (an asterisk), the actual
          precision is given in the next argument, which must be of type
          int, and the value to convert comes after the precision.

       5. Length modifier (optional).

       6. Conversion type.

     The conversion flag characters are:

     旗標        含義
                 
     ------------------------------------------------------------------------------
                 
     ‘0’         The conversion will be zero padded for numeric values.
                 
                 
     ‘-’         The converted value is left adjusted (overrides the ‘0’ flag if
                 both are given).
                 

     The length modifiers for following integer conversions (‘d’, ‘i’,
     ‘o’, ‘u’, ‘x’, or ‘X’) specify the type of the argument (int by
     default):

     Modifier       Types
                    
     -------------------------------------------------------------------------
                    
     ‘l’            long 或 unsigned long
                    
                    
     ‘ll’           long long 或 unsigned long long
                    
                    
     ‘j’            ‘intmax_t’ 或 ‘uintmax_t’
                    
                    
     ‘z’            ‘size_t’ 或 ‘ssize_t’
                    
                    
     ‘t’            ‘ptrdiff_t’
                    

     The length modifier ‘l’ for following conversions ‘s’ or ‘V’
     specify that the type of the argument is const wchar_t*.

     The conversion specifiers are:

     Conversion Specifier                  Type                                  Comment
                                                                                 
     ------------------------------------------------------------------------------------------------------------------
                                                                                 
     ‘%’                                   'n/a'                                 The literal ‘%’ character.
                                                                                 
                                                                                 
     ‘d’, ‘i’                              Specified by the length modifier      The decimal representation of a
                                                                                 signed C integer.
                                                                                 
                                                                                 
     ‘u’                                   Specified by the length modifier      The decimal representation of an
                                                                                 unsigned C integer.
                                                                                 
                                                                                 
     ‘o’                                   Specified by the length modifier      The octal representation of an
                                                                                 unsigned C integer.
                                                                                 
                                                                                 
     ‘x’                                   Specified by the length modifier      The hexadecimal representation of
                                                                                 an unsigned C integer (lowercase).
                                                                                 
                                                                                 
     ‘X’                                   Specified by the length modifier      The hexadecimal representation of
                                                                                 an unsigned C integer (uppercase).
                                                                                 
                                                                                 
     ‘c’                                   int                                   A single character.
                                                                                 
                                                                                 
     ‘s’                                   const char* 或 const wchar_t*         A null-terminated C character
                                                                                 array.
                                                                                 
                                                                                 
     ‘p’                                   const void*                           The hex representation of a C
                                                                                 pointer.  Mostly equivalent to
                                                                                 ‘printf("%p")’ except that it is
                                                                                 guaranteed to start with the
                                                                                 literal ‘0x’ regardless of what the
                                                                                 platform's ‘printf’ yields.
                                                                                 
                                                                                 
     ‘A’                                   *note PyObject: 311.*                 The result of calling
                                                                                 *note ascii(): 1354.
                                                                                 
                                                                                 
     ‘U’                                   *note PyObject: 311.*                 一 Unicode 物件。
                                                                                 
                                                                                 
     ‘V’                                   *note PyObject: 311.*、const char*    A Unicode object (which may be
                                           或 const wchar_t*                     ‘NULL’) and a null-terminated C
                                                                                 character array as a second
                                                                                 parameter (which will be used, if
                                                                                 the first parameter is ‘NULL’).
                                                                                 
                                                                                 
     ‘S’                                   *note PyObject: 311.*                 The result of calling
                                                                                 *note PyObject_Str(): fd3.
                                                                                 
                                                                                 
     ‘R’                                   *note PyObject: 311.*                 The result of calling
                                                                                 *note PyObject_Repr(): fd2.
                                                                                 
                                                                                 
     ‘T’                                   *note PyObject: 311.*                 Get the fully qualified name of an
                                                                                 object type; call
                                                                                 *note PyType_GetFullyQualifiedName(): 33d.
                                                                                 
                                                                                 
     ‘#T’                                  *note PyObject: 311.*                 Similar to ‘T’ format, but use a
                                                                                 colon (‘:’) as separator between
                                                                                 the module name and the qualified
                                                                                 name.
                                                                                 
                                                                                 
     ‘N’                                   *note PyTypeObject: a48.*             Get the fully qualified name of a
                                                                                 type; call
                                                                                 *note PyType_GetFullyQualifiedName(): 33d.
                                                                                 
                                                                                 
     ‘#N’                                  *note PyTypeObject: a48.*             Similar to ‘N’ format, but use a
                                                                                 colon (‘:’) as separator between
                                                                                 the module name and the qualified
                                                                                 name.
                                                                                 

          備註: The width formatter unit is number of characters rather
          than bytes.  The precision formatter unit is number of bytes
          or ‘wchar_t’ items (if the length modifier ‘l’ is used) for
          ‘"%s"’ and ‘"%V"’ (if the ‘PyObject*’ argument is ‘NULL’), and
          a number of characters for ‘"%A"’, ‘"%U"’, ‘"%S"’, ‘"%R"’ and
          ‘"%V"’ (if the ‘PyObject*’ argument is not ‘NULL’).

          備註: Unlike to C ‘printf()’ the ‘0’ flag has effect even when
          a precision is given for integer conversions (‘d’, ‘i’, ‘u’,
          ‘o’, ‘x’, or ‘X’).

     在 3.2 版的變更: Support for ‘"%lld"’ and ‘"%llu"’ added.

     在 3.3 版的變更: Support for ‘"%li"’, ‘"%lli"’ and ‘"%zi"’ added.

     在 3.4 版的變更: Support width and precision formatter for ‘"%s"’,
     ‘"%A"’, ‘"%U"’, ‘"%V"’, ‘"%S"’, ‘"%R"’ added.

     在 3.12 版的變更: Support for conversion specifiers ‘o’ and ‘X’.
     Support for length modifiers ‘j’ and ‘t’.  Length modifiers are now
     applied to all integer conversions.  Length modifier ‘l’ is now
     applied to conversion specifiers ‘s’ and ‘V’.  Support for variable
     width and precision ‘*’.  Support for flag ‘-’.

     An unrecognized format character now sets a *note SystemError: 51b.
     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.

     在 3.13 版的變更: Support for ‘%T’, ‘%#T’, ‘%N’ and ‘%#N’ formats
     added.

 -- C 函式: *note PyObject: 311. *PyUnicode_FromFormatV (const char
          *format, va_list vargs)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Identical
     to *note PyUnicode_FromFormat(): 33f. except that it takes exactly
     two arguments.

 -- C 函式: *note PyObject: 311. *PyUnicode_FromObject (PyObject *obj)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Copy an
     instance of a Unicode subtype to a new true Unicode object if
     necessary.  If 'obj' is already a true Unicode object (not a
     subtype), return a new *note strong reference: 2ee. to the object.

     Objects other than Unicode or its subtypes will cause a *note
     TypeError: 4dd.

 -- C 函式: *note PyObject: 311. *PyUnicode_FromEncodedObject (PyObject
          *obj, const char *encoding, const char *errors)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Decode an
     encoded object 'obj' to a Unicode object.

     *note bytes: 1a5, *note bytearray: 4e3. and other *note bytes-like
     objects: cd4. are decoded according to the given 'encoding' and
     using the error handling defined by 'errors'.  Both can be ‘NULL’
     to have the interface use the default values (see *note Built-in
     Codecs: 4a3a. for details).

     All other objects, including Unicode objects, cause a *note
     TypeError: 4dd. to be set.

     The API returns ‘NULL’ if there was an error.  The caller is
     responsible for decref'ing the returned objects.

 -- C 函式: *note Py_ssize_t: a03. PyUnicode_GetLength (PyObject
          *unicode)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Return the
     length of the Unicode object, in code points.

     在 3.3 版被加入.

 -- C 函式: *note Py_ssize_t: a03. PyUnicode_CopyCharacters (PyObject
          *to, Py_ssize_t to_start, PyObject *from, Py_ssize_t
          from_start, Py_ssize_t how_many)

     Copy characters from one Unicode object into another.  This
     function performs character conversion when necessary and falls
     back to ‘memcpy()’ if possible.  Returns ‘-1’ and sets an exception
     on error, otherwise returns the number of copied characters.

     在 3.3 版被加入.

 -- C 函式: *note Py_ssize_t: a03. PyUnicode_Fill (PyObject *unicode,
          Py_ssize_t start, Py_ssize_t length, Py_UCS4 fill_char)

     Fill a string with a character: write 'fill_char' into
     ‘unicode[start:start+length]’.

     Fail if 'fill_char' is bigger than the string maximum character, or
     if the string has more than 1 reference.

     Return the number of written character, or return ‘-1’ and raise an
     exception on error.

     在 3.3 版被加入.

 -- C 函式: int PyUnicode_WriteChar (PyObject *unicode, Py_ssize_t
          index, Py_UCS4 character)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Write a
     character to a string.  The string must have been created through
     *note PyUnicode_New(): 850.  Since Unicode strings are supposed to
     be immutable, the string must not be shared, or have been hashed
     yet.

     This function checks that 'unicode' is a Unicode object, that the
     index is not out of bounds, and that the object can be modified
     safely (i.e.  that it its reference count is one).

     在 3.3 版被加入.

 -- C 函式: *note Py_UCS4: 110e. PyUnicode_ReadChar (PyObject *unicode,
          Py_ssize_t index)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Read a
     character from a string.  This function checks that 'unicode' is a
     Unicode object and the index is not out of bounds, in contrast to
     *note PyUnicode_READ_CHAR(): 111c, which performs no error
     checking.

     在 3.3 版被加入.

 -- C 函式: *note PyObject: 311. *PyUnicode_Substring (PyObject
          *unicode, Py_ssize_t start, Py_ssize_t end)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本
     開始.'  Return a substring of 'unicode', from character index
     'start' (included) to character index 'end' (excluded).  Negative
     indices are not supported.

     在 3.3 版被加入.

 -- C 函式: *note Py_UCS4: 110e. *PyUnicode_AsUCS4 (PyObject *unicode,
          Py_UCS4 *buffer, Py_ssize_t buflen, int copy_null)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Copy the
     string 'unicode' into a UCS4 buffer, including a null character, if
     'copy_null' is set.  Returns ‘NULL’ and sets an exception on error
     (in particular, a *note SystemError: 51b. if 'buflen' is smaller
     than the length of 'unicode').  'buffer' is returned on success.

     在 3.3 版被加入.

 -- C 函式: *note Py_UCS4: 110e. *PyUnicode_AsUCS4Copy (PyObject
          *unicode)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Copy the
     string 'unicode' into a new UCS4 buffer that is allocated using
     *note PyMem_Malloc(): c0d.  If this fails, ‘NULL’ is returned with
     a *note MemoryError: 15bc. set.  The returned buffer always has an
     extra null code point appended.

     在 3.3 版被加入.


File: python.info,  Node: Locale Encoding,  Next: File System Encoding,  Prev: Creating and accessing Unicode strings,  Up: Unicode 物件

7.8.3.11 Locale Encoding
........................

The current locale encoding can be used to decode text from the
operating system.

 -- C 函式: *note PyObject: 311. *PyUnicode_DecodeLocaleAndSize (const
          char *str, Py_ssize_t length, const char *errors)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本
     開始.'  Decode a string from UTF-8 on Android and VxWorks, or from
     the current locale encoding on other platforms.  The supported
     error handlers are ‘"strict"’ and ‘"surrogateescape"’ ( PEP
     383(1)).  The decoder uses ‘"strict"’ error handler if 'errors' is
     ‘NULL’.  'str' must end with a null character but cannot contain
     embedded null characters.

     Use *note PyUnicode_DecodeFSDefaultAndSize(): 4896. to decode a
     string from the *note filesystem encoding and error handler: 4e0.

     This function ignores the *note Python UTF-8 Mode: 5fc.

     也參考
     ......

     *note Py_DecodeLocale(): b6e. 函式。

     在 3.3 版被加入.

     在 3.7 版的變更: The function now also uses the current locale
     encoding for the ‘surrogateescape’ error handler, except on
     Android.  Previously, *note Py_DecodeLocale(): b6e. was used for
     the ‘surrogateescape’, and the current locale encoding was used for
     ‘strict’.

 -- C 函式: *note PyObject: 311. *PyUnicode_DecodeLocale (const char
          *str, const char *errors)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本
     開始.'  Similar to *note PyUnicode_DecodeLocaleAndSize(): b70, but
     compute the string length using ‘strlen()’.

     在 3.3 版被加入.

 -- C 函式: *note PyObject: 311. *PyUnicode_EncodeLocale (PyObject
          *unicode, const char *errors)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本
     開始.'  Encode a Unicode object to UTF-8 on Android and VxWorks, or
     to the current locale encoding on other platforms.  The supported
     error handlers are ‘"strict"’ and ‘"surrogateescape"’ ( PEP
     383(2)).  The encoder uses ‘"strict"’ error handler if 'errors' is
     ‘NULL’.  Return a *note bytes: 1a5. object.  'unicode' cannot
     contain embedded null characters.

     Use *note PyUnicode_EncodeFSDefault(): 1957. to encode a string to
     the *note filesystem encoding and error handler: 4e0.

     This function ignores the *note Python UTF-8 Mode: 5fc.

     也參考
     ......

     *note Py_EncodeLocale(): b6f. 函式。

     在 3.3 版被加入.

     在 3.7 版的變更: The function now also uses the current locale
     encoding for the ‘surrogateescape’ error handler, except on
     Android.  Previously, *note Py_EncodeLocale(): b6f. was used for
     the ‘surrogateescape’, and the current locale encoding was used for
     ‘strict’.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0383/

   (2) https://peps.python.org/pep-0383/


File: python.info,  Node: File System Encoding,  Next: wchar_t 支援,  Prev: Locale Encoding,  Up: Unicode 物件

7.8.3.12 File System Encoding
.............................

Functions encoding to and decoding from the *note filesystem encoding
and error handler: 4e0. ( PEP 383(1) and PEP 529(2)).

To encode file names to *note bytes: 1a5. during argument parsing, the
‘"O&"’ converter should be used, passing *note PyUnicode_FSConverter():
cc0. as the conversion function:

 -- C 函式: int PyUnicode_FSConverter (PyObject *obj, void *result)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  ParseTuple converter: encode
     *note str: 3f2. objects - obtained directly or through the *note
     os.PathLike: bf8. interface - to *note bytes: 1a5. using *note
     PyUnicode_EncodeFSDefault(): 1957.; *note bytes: 1a5. objects are
     output as-is.  'result' must be a *note PyBytesObject: 736.* which
     must be released when it is no longer used.

     在 3.1 版被加入.

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

To decode file names to *note str: 3f2. during argument parsing, the
‘"O&"’ converter should be used, passing *note PyUnicode_FSDecoder():
51d. as the conversion function:

 -- C 函式: int PyUnicode_FSDecoder (PyObject *obj, void *result)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  ParseTuple converter: decode
     *note bytes: 1a5. objects - obtained either directly or indirectly
     through the *note os.PathLike: bf8. interface - to *note str: 3f2.
     using *note PyUnicode_DecodeFSDefaultAndSize(): 4896.; *note str:
     3f2. objects are output as-is.  'result' must be a *note
     PyUnicodeObject: 738.* which must be released when it is no longer
     used.

     在 3.2 版被加入.

     在 3.6 版的變更: Accepts a *note path-like object: ac2.

 -- C 函式: *note PyObject: 311. *PyUnicode_DecodeFSDefaultAndSize
          (const char *str, Py_ssize_t size)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Decode a
     string from the *note filesystem encoding and error handler: 4e0.

     If you need to decode a string from the current locale encoding,
     use *note PyUnicode_DecodeLocaleAndSize(): b70.

     也參考
     ......

     *note Py_DecodeLocale(): b6e. 函式。

     在 3.6 版的變更: The *note filesystem error handler: 4e0. is now
     used.

 -- C 函式: *note PyObject: 311. *PyUnicode_DecodeFSDefault (const char
          *str)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Decode a
     null-terminated string from the *note filesystem encoding and error
     handler: 4e0.

     If the string length is known, use *note
     PyUnicode_DecodeFSDefaultAndSize(): 4896.

     在 3.6 版的變更: The *note filesystem error handler: 4e0. is now
     used.

 -- C 函式: *note PyObject: 311. *PyUnicode_EncodeFSDefault (PyObject
          *unicode)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Encode a
     Unicode object to the *note filesystem encoding and error handler:
     4e0, and return *note bytes: 1a5.  Note that the resulting *note
     bytes: 1a5. object can contain null bytes.

     If you need to encode a string to the current locale encoding, use
     *note PyUnicode_EncodeLocale(): b71.

     也參考
     ......

     *note Py_EncodeLocale(): b6f. 函式。

     在 3.2 版被加入.

     在 3.6 版的變更: The *note filesystem error handler: 4e0. is now
     used.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0383/

   (2) https://peps.python.org/pep-0529/


File: python.info,  Node: wchar_t 支援,  Prev: File System Encoding,  Up: Unicode 物件

7.8.3.13 wchar_t 支援
.....................

‘wchar_t’ support for platforms which support it:

 -- C 函式: *note PyObject: 311. *PyUnicode_FromWideChar (const wchar_t
          *wstr, Py_ssize_t size)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a
     Unicode object from the ‘wchar_t’ buffer 'wstr' of the given
     'size'.  Passing ‘-1’ as the 'size' indicates that the function
     must itself compute the length, using ‘wcslen()’.  Return ‘NULL’ on
     failure.

 -- C 函式: *note Py_ssize_t: a03. PyUnicode_AsWideChar (PyObject
          *unicode, wchar_t *wstr, Py_ssize_t size)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Copy the Unicode object
     contents into the ‘wchar_t’ buffer 'wstr'.  At most 'size'
     ‘wchar_t’ characters are copied (excluding a possibly trailing null
     termination character).  Return the number of ‘wchar_t’ characters
     copied or ‘-1’ in case of an error.

     When 'wstr' is ‘NULL’, instead return the 'size' that would be
     required to store all of 'unicode' including a terminating null.

     Note that the resulting wchar_t* string may or may not be
     null-terminated.  It is the responsibility of the caller to make
     sure that the wchar_t* string is null-terminated in case this is
     required by the application.  Also, note that the wchar_t* string
     might contain null characters, which would cause the string to be
     truncated when used with most C functions.

 -- C 函式: wchar_t *PyUnicode_AsWideCharString (PyObject *unicode,
          Py_ssize_t *size)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Convert the
     Unicode object to a wide character string.  The output string
     always ends with a null character.  If 'size' is not ‘NULL’, write
     the number of wide characters (excluding the trailing null
     termination character) into '*size'.  Note that the resulting
     ‘wchar_t’ string might contain null characters, which would cause
     the string to be truncated when used with most C functions.  If
     'size' is ‘NULL’ and the wchar_t* string contains null characters a
     *note ValueError: 1e7. is raised.

     Returns a buffer allocated by *note PyMem_New: 1493. (use *note
     PyMem_Free(): 13b0. to free it) on success.  On error, returns
     ‘NULL’ and '*size' is undefined.  Raises a *note MemoryError: 15bc.
     if memory allocation is failed.

     在 3.2 版被加入.

     在 3.7 版的變更: Raises a *note ValueError: 1e7. if 'size' is
     ‘NULL’ and the wchar_t* string contains null characters.


File: python.info,  Node: Built-in Codecs,  Next: Methods and Slot Functions,  Prev: Unicode 物件,  Up: Unicode 物件與編解碼器

7.8.3.14 Built-in Codecs
........................

Python provides a set of built-in codecs which are written in C for
speed.  All of these codecs are directly usable via the following
functions.

Many of the following APIs take two arguments encoding and errors, and
they have the same semantics as the ones of the built-in *note str():
3f2. string object constructor.

Setting encoding to ‘NULL’ causes the default encoding to be used which
is UTF-8.  The file system calls should use *note
PyUnicode_FSConverter(): cc0. for encoding file names.  This uses the
*note filesystem encoding and error handler: 4e0. internally.

Error handling is set by errors which may also be set to ‘NULL’ meaning
to use the default handling defined for the codec.  Default error
handling for all built-in codecs is "strict" (*note ValueError: 1e7. is
raised).

The codecs all use a similar interface.  Only deviations from the
following generic ones are documented for simplicity.

* Menu:

* Generic Codecs::
* UTF-8 編解碼器::
* UTF-32 編解碼器::
* UTF-16 編解碼器::
* UTF-7 編解碼器::
* Unicode-Escape Codecs::
* Raw-Unicode-Escape Codecs::
* Latin-1 編解碼器::
* ASCII 編解碼器::
* Character Map Codecs::
* MBCS codecs for Windows::
* Methods & Slots::


File: python.info,  Node: Generic Codecs,  Next: UTF-8 編解碼器,  Up: Built-in Codecs

7.8.3.15 Generic Codecs
.......................

These are the generic codec APIs:

 -- C 函式: *note PyObject: 311. *PyUnicode_Decode (const char *str,
          Py_ssize_t size, const char *encoding, const char *errors)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a
     Unicode object by decoding 'size' bytes of the encoded string
     'str'.  'encoding' and 'errors' have the same meaning as the
     parameters of the same name in the *note str(): 3f2. built-in
     function.  The codec to be used is looked up using the Python codec
     registry.  Return ‘NULL’ if an exception was raised by the codec.

 -- C 函式: *note PyObject: 311. *PyUnicode_AsEncodedString (PyObject
          *unicode, const char *encoding, const char *errors)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Encode a
     Unicode object and return the result as Python bytes object.
     'encoding' and 'errors' have the same meaning as the parameters of
     the same name in the Unicode *note encode(): 87a. method.  The
     codec to be used is looked up using the Python codec registry.
     Return ‘NULL’ if an exception was raised by the codec.


File: python.info,  Node: UTF-8 編解碼器,  Next: UTF-32 編解碼器,  Prev: Generic Codecs,  Up: Built-in Codecs

7.8.3.16 UTF-8 編解碼器
.......................

These are the UTF-8 codec APIs:

 -- C 函式: *note PyObject: 311. *PyUnicode_DecodeUTF8 (const char *str,
          Py_ssize_t size, const char *errors)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a
     Unicode object by decoding 'size' bytes of the UTF-8 encoded string
     'str'.  Return ‘NULL’ if an exception was raised by the codec.

 -- C 函式: *note PyObject: 311. *PyUnicode_DecodeUTF8Stateful (const
          char *str, Py_ssize_t size, const char *errors, Py_ssize_t
          *consumed)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  If
     'consumed' is ‘NULL’, behave like *note PyUnicode_DecodeUTF8():
     48a2.  If 'consumed' is not ‘NULL’, trailing incomplete UTF-8 byte
     sequences will not be treated as an error.  Those bytes will not be
     decoded and the number of bytes that have been decoded will be
     stored in 'consumed'.

 -- C 函式: *note PyObject: 311. *PyUnicode_AsUTF8String (PyObject
          *unicode)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Encode a
     Unicode object using UTF-8 and return the result as Python bytes
     object.  Error handling is "strict".  Return ‘NULL’ if an exception
     was raised by the codec.

 -- C 函式: const char *PyUnicode_AsUTF8AndSize (PyObject *unicode,
          Py_ssize_t *size)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本開始.'  Return a
     pointer to the UTF-8 encoding of the Unicode object, and store the
     size of the encoded representation (in bytes) in 'size'.  The
     'size' argument can be ‘NULL’; in this case no size will be stored.
     The returned buffer always has an extra null byte appended (not
     included in 'size'), regardless of whether there are any other null
     code points.

     On error, set an exception, set 'size' to ‘-1’ (if it's not NULL)
     and return ‘NULL’.

     This caches the UTF-8 representation of the string in the Unicode
     object, and subsequent calls will return a pointer to the same
     buffer.  The caller is not responsible for deallocating the buffer.
     The buffer is deallocated and pointers to it become invalid when
     the Unicode object is garbage collected.

     在 3.3 版被加入.

     在 3.7 版的變更: The return type is now ‘const char *’ rather of
     ‘char *’.

     在 3.10 版的變更: This function is a part of the *note limited API:
     318.

 -- C 函式: const char *PyUnicode_AsUTF8 (PyObject *unicode)

     As *note PyUnicode_AsUTF8AndSize(): 83d, but does not store the
     size.

     在 3.3 版被加入.

     在 3.7 版的變更: The return type is now ‘const char *’ rather of
     ‘char *’.


File: python.info,  Node: UTF-32 編解碼器,  Next: UTF-16 編解碼器,  Prev: UTF-8 編解碼器,  Up: Built-in Codecs

7.8.3.17 UTF-32 編解碼器
........................

These are the UTF-32 codec APIs:

 -- C 函式: *note PyObject: 311. *PyUnicode_DecodeUTF32 (const char
          *str, Py_ssize_t size, const char *errors, int *byteorder)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Decode
     'size' bytes from a UTF-32 encoded buffer string and return the
     corresponding Unicode object.  'errors' (if non-‘NULL’) defines the
     error handling.  It defaults to "strict".

     If 'byteorder' is non-‘NULL’, the decoder starts decoding using the
     given byte order:

          *byteorder == -1: little endian
          *byteorder == 0:  native order
          *byteorder == 1:  big endian

     If ‘*byteorder’ is zero, and the first four bytes of the input data
     are a byte order mark (BOM), the decoder switches to this byte
     order and the BOM is not copied into the resulting Unicode string.
     If ‘*byteorder’ is ‘-1’ or ‘1’, any byte order mark is copied to
     the output.

     After completion, '*byteorder' is set to the current byte order at
     the end of input data.

     If 'byteorder' is ‘NULL’, the codec starts in native order mode.

     Return ‘NULL’ if an exception was raised by the codec.

 -- C 函式: *note PyObject: 311. *PyUnicode_DecodeUTF32Stateful (const
          char *str, Py_ssize_t size, const char *errors, int
          *byteorder, Py_ssize_t *consumed)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  If
     'consumed' is ‘NULL’, behave like *note PyUnicode_DecodeUTF32():
     489e.  If 'consumed' is not ‘NULL’, *note
     PyUnicode_DecodeUTF32Stateful(): 489f. will not treat trailing
     incomplete UTF-32 byte sequences (such as a number of bytes not
     divisible by four) as an error.  Those bytes will not be decoded
     and the number of bytes that have been decoded will be stored in
     'consumed'.

 -- C 函式: *note PyObject: 311. *PyUnicode_AsUTF32String (PyObject
          *unicode)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     Python byte string using the UTF-32 encoding in native byte order.
     The string always starts with a BOM mark.  Error handling is
     "strict".  Return ‘NULL’ if an exception was raised by the codec.


File: python.info,  Node: UTF-16 編解碼器,  Next: UTF-7 編解碼器,  Prev: UTF-32 編解碼器,  Up: Built-in Codecs

7.8.3.18 UTF-16 編解碼器
........................

These are the UTF-16 codec APIs:

 -- C 函式: *note PyObject: 311. *PyUnicode_DecodeUTF16 (const char
          *str, Py_ssize_t size, const char *errors, int *byteorder)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Decode
     'size' bytes from a UTF-16 encoded buffer string and return the
     corresponding Unicode object.  'errors' (if non-‘NULL’) defines the
     error handling.  It defaults to "strict".

     If 'byteorder' is non-‘NULL’, the decoder starts decoding using the
     given byte order:

          *byteorder == -1: little endian
          *byteorder == 0:  native order
          *byteorder == 1:  big endian

     If ‘*byteorder’ is zero, and the first two bytes of the input data
     are a byte order mark (BOM), the decoder switches to this byte
     order and the BOM is not copied into the resulting Unicode string.
     If ‘*byteorder’ is ‘-1’ or ‘1’, any byte order mark is copied to
     the output (where it will result in either a ‘\ufeff’ or a ‘\ufffe’
     character).

     After completion, ‘*byteorder’ is set to the current byte order at
     the end of input data.

     If 'byteorder' is ‘NULL’, the codec starts in native order mode.

     Return ‘NULL’ if an exception was raised by the codec.

 -- C 函式: *note PyObject: 311. *PyUnicode_DecodeUTF16Stateful (const
          char *str, Py_ssize_t size, const char *errors, int
          *byteorder, Py_ssize_t *consumed)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  If
     'consumed' is ‘NULL’, behave like *note PyUnicode_DecodeUTF16():
     489c.  If 'consumed' is not ‘NULL’, *note
     PyUnicode_DecodeUTF16Stateful(): 489d. will not treat trailing
     incomplete UTF-16 byte sequences (such as an odd number of bytes or
     a split surrogate pair) as an error.  Those bytes will not be
     decoded and the number of bytes that have been decoded will be
     stored in 'consumed'.

 -- C 函式: *note PyObject: 311. *PyUnicode_AsUTF16String (PyObject
          *unicode)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     Python byte string using the UTF-16 encoding in native byte order.
     The string always starts with a BOM mark.  Error handling is
     "strict".  Return ‘NULL’ if an exception was raised by the codec.


File: python.info,  Node: UTF-7 編解碼器,  Next: Unicode-Escape Codecs,  Prev: UTF-16 編解碼器,  Up: Built-in Codecs

7.8.3.19 UTF-7 編解碼器
.......................

These are the UTF-7 codec APIs:

 -- C 函式: *note PyObject: 311. *PyUnicode_DecodeUTF7 (const char *str,
          Py_ssize_t size, const char *errors)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a
     Unicode object by decoding 'size' bytes of the UTF-7 encoded string
     'str'.  Return ‘NULL’ if an exception was raised by the codec.

 -- C 函式: *note PyObject: 311. *PyUnicode_DecodeUTF7Stateful (const
          char *str, Py_ssize_t size, const char *errors, Py_ssize_t
          *consumed)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  If
     'consumed' is ‘NULL’, behave like *note PyUnicode_DecodeUTF7():
     48a0.  If 'consumed' is not ‘NULL’, trailing incomplete UTF-7
     base-64 sections will not be treated as an error.  Those bytes will
     not be decoded and the number of bytes that have been decoded will
     be stored in 'consumed'.


File: python.info,  Node: Unicode-Escape Codecs,  Next: Raw-Unicode-Escape Codecs,  Prev: UTF-7 編解碼器,  Up: Built-in Codecs

7.8.3.20 Unicode-Escape Codecs
..............................

These are the "Unicode Escape" codec APIs:

 -- C 函式: *note PyObject: 311. *PyUnicode_DecodeUnicodeEscape (const
          char *str, Py_ssize_t size, const char *errors)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a
     Unicode object by decoding 'size' bytes of the Unicode-Escape
     encoded string 'str'.  Return ‘NULL’ if an exception was raised by
     the codec.

 -- C 函式: *note PyObject: 311. *PyUnicode_AsUnicodeEscapeString
          (PyObject *unicode)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Encode a
     Unicode object using Unicode-Escape and return the result as a
     bytes object.  Error handling is "strict".  Return ‘NULL’ if an
     exception was raised by the codec.


File: python.info,  Node: Raw-Unicode-Escape Codecs,  Next: Latin-1 編解碼器,  Prev: Unicode-Escape Codecs,  Up: Built-in Codecs

7.8.3.21 Raw-Unicode-Escape Codecs
..................................

These are the "Raw Unicode Escape" codec APIs:

 -- C 函式: *note PyObject: 311. *PyUnicode_DecodeRawUnicodeEscape
          (const char *str, Py_ssize_t size, const char *errors)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a
     Unicode object by decoding 'size' bytes of the Raw-Unicode-Escape
     encoded string 'str'.  Return ‘NULL’ if an exception was raised by
     the codec.

 -- C 函式: *note PyObject: 311. *PyUnicode_AsRawUnicodeEscapeString
          (PyObject *unicode)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Encode a
     Unicode object using Raw-Unicode-Escape and return the result as a
     bytes object.  Error handling is "strict".  Return ‘NULL’ if an
     exception was raised by the codec.


File: python.info,  Node: Latin-1 編解碼器,  Next: ASCII 編解碼器,  Prev: Raw-Unicode-Escape Codecs,  Up: Built-in Codecs

7.8.3.22 Latin-1 編解碼器
.........................

These are the Latin-1 codec APIs: Latin-1 corresponds to the first 256
Unicode ordinals and only these are accepted by the codecs during
encoding.

 -- C 函式: *note PyObject: 311. *PyUnicode_DecodeLatin1 (const char
          *str, Py_ssize_t size, const char *errors)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a
     Unicode object by decoding 'size' bytes of the Latin-1 encoded
     string 'str'.  Return ‘NULL’ if an exception was raised by the
     codec.

 -- C 函式: *note PyObject: 311. *PyUnicode_AsLatin1String (PyObject
          *unicode)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Encode a
     Unicode object using Latin-1 and return the result as Python bytes
     object.  Error handling is "strict".  Return ‘NULL’ if an exception
     was raised by the codec.


File: python.info,  Node: ASCII 編解碼器,  Next: Character Map Codecs,  Prev: Latin-1 編解碼器,  Up: Built-in Codecs

7.8.3.23 ASCII 編解碼器
.......................

These are the ASCII codec APIs.  Only 7-bit ASCII data is accepted.  All
other codes generate errors.

 -- C 函式: *note PyObject: 311. *PyUnicode_DecodeASCII (const char
          *str, Py_ssize_t size, const char *errors)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a
     Unicode object by decoding 'size' bytes of the ASCII encoded string
     'str'.  Return ‘NULL’ if an exception was raised by the codec.

 -- C 函式: *note PyObject: 311. *PyUnicode_AsASCIIString (PyObject
          *unicode)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Encode a
     Unicode object using ASCII and return the result as Python bytes
     object.  Error handling is "strict".  Return ‘NULL’ if an exception
     was raised by the codec.


File: python.info,  Node: Character Map Codecs,  Next: MBCS codecs for Windows,  Prev: ASCII 編解碼器,  Up: Built-in Codecs

7.8.3.24 Character Map Codecs
.............................

This codec is special in that it can be used to implement many different
codecs (and this is in fact what was done to obtain most of the standard
codecs included in the ‘encodings’ package).  The codec uses mappings to
encode and decode characters.  The mapping objects provided must support
the *note __getitem__(): 266. mapping interface; dictionaries and
sequences work well.

These are the mapping codec APIs:

 -- C 函式: *note PyObject: 311. *PyUnicode_DecodeCharmap (const char
          *str, Py_ssize_t length, PyObject *mapping, const char
          *errors)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a
     Unicode object by decoding 'size' bytes of the encoded string 'str'
     using the given 'mapping' object.  Return ‘NULL’ if an exception
     was raised by the codec.

     If 'mapping' is ‘NULL’, Latin-1 decoding will be applied.  Else
     'mapping' must map bytes ordinals (integers in the range from 0 to
     255) to Unicode strings, integers (which are then interpreted as
     Unicode ordinals) or ‘None’.  Unmapped data bytes - ones which
     cause a *note LookupError: 20a9, as well as ones which get mapped
     to ‘None’, ‘0xFFFE’ or ‘'\ufffe'’, are treated as undefined
     mappings and cause an error.

 -- C 函式: *note PyObject: 311. *PyUnicode_AsCharmapString (PyObject
          *unicode, PyObject *mapping)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Encode a
     Unicode object using the given 'mapping' object and return the
     result as a bytes object.  Error handling is "strict".  Return
     ‘NULL’ if an exception was raised by the codec.

     The 'mapping' object must map Unicode ordinal integers to bytes
     objects, integers in the range from 0 to 255 or ‘None’.  Unmapped
     character ordinals (ones which cause a *note LookupError: 20a9.) as
     well as mapped to ‘None’ are treated as "undefined mapping" and
     cause an error.

The following codec API is special in that maps Unicode to Unicode.

 -- C 函式: *note PyObject: 311. *PyUnicode_Translate (PyObject
          *unicode, PyObject *table, const char *errors)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Translate
     a string by applying a character mapping table to it and return the
     resulting Unicode object.  Return ‘NULL’ if an exception was raised
     by the codec.

     The mapping table must map Unicode ordinal integers to Unicode
     ordinal integers or ‘None’ (causing deletion of the character).

     Mapping tables need only provide the *note __getitem__(): 266.
     interface; dictionaries and sequences work well.  Unmapped
     character ordinals (ones which cause a *note LookupError: 20a9.)
     are left untouched and are copied as-is.

     'errors' has the usual meaning for codecs.  It may be ‘NULL’ which
     indicates to use the default error handling.


File: python.info,  Node: MBCS codecs for Windows,  Next: Methods & Slots,  Prev: Character Map Codecs,  Up: Built-in Codecs

7.8.3.25 MBCS codecs for Windows
................................

These are the MBCS codec APIs.  They are currently only available on
Windows and use the Win32 MBCS converters to implement the conversions.
Note that MBCS (or DBCS) is a class of encodings, not just one.  The
target encoding is defined by the user settings on the machine running
the codec.

 -- C 函式: *note PyObject: 311. *PyUnicode_DecodeMBCS (const char *str,
          Py_ssize_t size, const char *errors)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. on Windows 自
     3.7 版本開始.'  Create a Unicode object by decoding 'size' bytes of
     the MBCS encoded string 'str'.  Return ‘NULL’ if an exception was
     raised by the codec.

 -- C 函式: *note PyObject: 311. *PyUnicode_DecodeMBCSStateful (const
          char *str, Py_ssize_t size, const char *errors, Py_ssize_t
          *consumed)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. on Windows 自
     3.7 版本開始.'  If 'consumed' is ‘NULL’, behave like *note
     PyUnicode_DecodeMBCS(): 4899.  If 'consumed' is not ‘NULL’, *note
     PyUnicode_DecodeMBCSStateful(): 489a. will not decode trailing lead
     byte and the number of bytes that have been decoded will be stored
     in 'consumed'.

 -- C 函式: *note PyObject: 311. *PyUnicode_AsMBCSString (PyObject
          *unicode)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. on Windows 自
     3.7 版本開始.'  Encode a Unicode object using MBCS and return the
     result as Python bytes object.  Error handling is "strict".  Return
     ‘NULL’ if an exception was raised by the codec.

 -- C 函式: *note PyObject: 311. *PyUnicode_EncodeCodePage (int
          code_page, PyObject *unicode, const char *errors)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. on Windows 自
     3.7 版本開始.'  Encode the Unicode object using the specified code
     page and return a Python bytes object.  Return ‘NULL’ if an
     exception was raised by the codec.  Use ‘CP_ACP’ code page to get
     the MBCS encoder.

     在 3.3 版被加入.


File: python.info,  Node: Methods & Slots,  Prev: MBCS codecs for Windows,  Up: Built-in Codecs

7.8.3.26 Methods & Slots
........................


File: python.info,  Node: Methods and Slot Functions,  Prev: Built-in Codecs,  Up: Unicode 物件與編解碼器

7.8.3.27 Methods and Slot Functions
...................................

The following APIs are capable of handling Unicode objects and strings
on input (we refer to them as strings in the descriptions) and return
Unicode objects or integers as appropriate.

They all return ‘NULL’ or ‘-1’ if an exception occurs.

 -- C 函式: *note PyObject: 311. *PyUnicode_Concat (PyObject *left,
          PyObject *right)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Concat two
     strings giving a new Unicode string.

 -- C 函式: *note PyObject: 311. *PyUnicode_Split (PyObject *unicode,
          PyObject *sep, Py_ssize_t maxsplit)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Split a
     string giving a list of Unicode strings.  If 'sep' is ‘NULL’,
     splitting will be done at all whitespace substrings.  Otherwise,
     splits occur at the given separator.  At most 'maxsplit' splits
     will be done.  If negative, no limit is set.  Separators are not
     included in the resulting list.

 -- C 函式: *note PyObject: 311. *PyUnicode_Splitlines (PyObject
          *unicode, int keepends)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Split a
     Unicode string at line breaks, returning a list of Unicode strings.
     CRLF is considered to be one line break.  If 'keepends' is ‘0’, the
     Line break characters are not included in the resulting strings.

 -- C 函式: *note PyObject: 311. *PyUnicode_Join (PyObject *separator,
          PyObject *seq)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Join a
     sequence of strings using the given 'separator' and return the
     resulting Unicode string.

 -- C 函式: *note Py_ssize_t: a03. PyUnicode_Tailmatch (PyObject
          *unicode, PyObject *substr, Py_ssize_t start, Py_ssize_t end,
          int direction)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return ‘1’ if 'substr' matches
     ‘unicode[start:end]’ at the given tail end ('direction' == ‘-1’
     means to do a prefix match, 'direction' == ‘1’ a suffix match), ‘0’
     otherwise.  Return ‘-1’ if an error occurred.

 -- C 函式: *note Py_ssize_t: a03. PyUnicode_Find (PyObject *unicode,
          PyObject *substr, Py_ssize_t start, Py_ssize_t end, int
          direction)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the first position of
     'substr' in ‘unicode[start:end]’ using the given 'direction'
     ('direction' == ‘1’ means to do a forward search, 'direction' ==
     ‘-1’ a backward search).  The return value is the index of the
     first match; a value of ‘-1’ indicates that no match was found, and
     ‘-2’ indicates that an error occurred and an exception has been
     set.

 -- C 函式: *note Py_ssize_t: a03. PyUnicode_FindChar (PyObject
          *unicode, Py_UCS4 ch, Py_ssize_t start, Py_ssize_t end, int
          direction)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Return the
     first position of the character 'ch' in ‘unicode[start:end]’ using
     the given 'direction' ('direction' == ‘1’ means to do a forward
     search, 'direction' == ‘-1’ a backward search).  The return value
     is the index of the first match; a value of ‘-1’ indicates that no
     match was found, and ‘-2’ indicates that an error occurred and an
     exception has been set.

     在 3.3 版被加入.

     在 3.7 版的變更: 'start' and 'end' are now adjusted to behave like
     ‘unicode[start:end]’.

 -- C 函式: *note Py_ssize_t: a03. PyUnicode_Count (PyObject *unicode,
          PyObject *substr, Py_ssize_t start, Py_ssize_t end)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the number of
     non-overlapping occurrences of 'substr' in ‘unicode[start:end]’.
     Return ‘-1’ if an error occurred.

 -- C 函式: *note PyObject: 311. *PyUnicode_Replace (PyObject *unicode,
          PyObject *substr, PyObject *replstr, Py_ssize_t maxcount)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Replace at
     most 'maxcount' occurrences of 'substr' in 'unicode' with 'replstr'
     and return the resulting Unicode object.  'maxcount' == ‘-1’ means
     replace all occurrences.

 -- C 函式: int PyUnicode_Compare (PyObject *left, PyObject *right)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Compare two strings and return
     ‘-1’, ‘0’, ‘1’ for less than, equal, and greater than,
     respectively.

     This function returns ‘-1’ upon failure, so one should call *note
     PyErr_Occurred(): 17f4. to check for errors.

 -- C 函式: int PyUnicode_EqualToUTF8AndSize (PyObject *unicode, const
          char *string, Py_ssize_t size)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Compare a
     Unicode object with a char buffer which is interpreted as being
     UTF-8 or ASCII encoded and return true (‘1’) if they are equal, or
     false (‘0’) otherwise.  If the Unicode object contains surrogate
     characters or the C string is not valid UTF-8, false (‘0’) is
     returned.

     This function does not raise exceptions.

     在 3.13 版被加入.

 -- C 函式: int PyUnicode_EqualToUTF8 (PyObject *unicode, const char
          *string)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Similar to
     *note PyUnicode_EqualToUTF8AndSize(): 31c, but compute 'string'
     length using ‘strlen()’.  If the Unicode object contains null
     characters, false (‘0’) is returned.

     在 3.13 版被加入.

 -- C 函式: int PyUnicode_CompareWithASCIIString (PyObject *unicode,
          const char *string)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Compare a Unicode object,
     'unicode', with 'string' and return ‘-1’, ‘0’, ‘1’ for less than,
     equal, and greater than, respectively.  It is best to pass only
     ASCII-encoded strings, but the function interprets the input string
     as ISO-8859-1 if it contains non-ASCII characters.

     This function does not raise exceptions.

 -- C 函式: *note PyObject: 311. *PyUnicode_RichCompare (PyObject *left,
          PyObject *right, int op)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Rich
     compare two Unicode strings and return one of the following:

        * ‘NULL’ in case an exception was raised

        * *note Py_True: 49ee. or *note Py_False: 49ed. for successful
          comparisons

        * *note Py_NotImplemented: 4964. in case the type combination is
          unknown

     Possible values for 'op' are *note Py_GT: 496c, *note Py_GE: 496d,
     *note Py_EQ: 496a, *note Py_NE: 496b, *note Py_LT: 4968, and *note
     Py_LE: 4969.

 -- C 函式: *note PyObject: 311. *PyUnicode_Format (PyObject *format,
          PyObject *args)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     new string object from 'format' and 'args'; this is analogous to
     ‘format % args’.

 -- C 函式: int PyUnicode_Contains (PyObject *unicode, PyObject *substr)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Check whether 'substr' is
     contained in 'unicode' and return true or false accordingly.

     'substr' has to coerce to a one element Unicode string.  ‘-1’ is
     returned if there was an error.

 -- C 函式: void PyUnicode_InternInPlace (PyObject **p_unicode)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Intern the argument **note
     p_unicode: 856. in place.  The argument must be the address of a
     pointer variable pointing to a Python Unicode string object.  If
     there is an existing interned string that is the same as **note
     p_unicode: 856, it sets **note p_unicode: 856. to it (releasing the
     reference to the old string object and creating a new *note strong
     reference: 2ee. to the interned string object), otherwise it leaves
     **note p_unicode: 856. alone and interns it.

     (Clarification: even though there is a lot of talk about
     references, think of this function as reference-neutral.  You must
     own the object you pass in; after the call you no longer own the
     passed-in reference, but you newly own the result.)

     This function never raises an exception.  On error, it leaves its
     argument unchanged without interning it.

     Instances of subclasses of *note str: 3f2. may not be interned,
     that is, *note PyUnicode_CheckExact: 4a23.(**note p_unicode: 856.)
     must be true.  If it is not, then - as with any other error - the
     argument is left unchanged.

     Note that interned strings are not “immortal”.  You must keep a
     reference to the result to benefit from interning.

 -- C 函式: *note PyObject: 311. *PyUnicode_InternFromString (const char
          *str)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  A
     combination of *note PyUnicode_FromString(): 4748. and *note
     PyUnicode_InternInPlace(): 856, meant for statically allocated
     strings.

     Return a new ("owned") reference to either a new Unicode string
     object that has been interned, or an earlier interned string object
     with the same value.

     Python may keep a reference to the result, or make it *note
     immortal: 4190, preventing it from being garbage-collected
     promptly.  For interning an unbounded number of different strings,
     such as ones coming from user input, prefer calling *note
     PyUnicode_FromString(): 4748. and *note PyUnicode_InternInPlace():
     856. directly.

     'CPython 實作細節：' Strings interned this way are made *note
     immortal: 4190.


File: python.info,  Node: Tuple（元組）物件,  Next: Struct Sequence Objects,  Prev: Unicode 物件與編解碼器,  Up: 序列物件

7.8.3.28 Tuple（元組）物件
..........................

 -- C 型別: type PyTupleObject

     This subtype of *note PyObject: 311. represents a Python tuple
     object.

 -- C 變數: *note PyTypeObject: a48. PyTuple_Type
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This instance of *note
     PyTypeObject: a48. represents the Python tuple type; it is the same
     object as *note tuple: 322. in the Python layer.

 -- C 函式: int PyTuple_Check (PyObject *p)

     Return true if 'p' is a tuple object or an instance of a subtype of
     the tuple type.  This function always succeeds.

 -- C 函式: int PyTuple_CheckExact (PyObject *p)

     Return true if 'p' is a tuple object, but not an instance of a
     subtype of the tuple type.  This function always succeeds.

 -- C 函式: *note PyObject: 311. *PyTuple_New (Py_ssize_t len)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     new tuple object of size 'len', or ‘NULL’ with an exception set on
     failure.

 -- C 函式: *note PyObject: 311. *PyTuple_Pack (Py_ssize_t n, ...)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     new tuple object of size 'n', or ‘NULL’ with an exception set on
     failure.  The tuple values are initialized to the subsequent 'n' C
     arguments pointing to Python objects.  ‘PyTuple_Pack(2, a, b)’ is
     equivalent to ‘Py_BuildValue("(OO)", a, b)’.

 -- C 函式: *note Py_ssize_t: a03. PyTuple_Size (PyObject *p)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Take a pointer to a tuple
     object, and return the size of that tuple.  On error, return ‘-1’
     and with an exception set.

 -- C 函式: *note Py_ssize_t: a03. PyTuple_GET_SIZE (PyObject *p)

     Like *note PyTuple_Size(): 4871, but without error checking.

 -- C 函式: *note PyObject: 311. *PyTuple_GetItem (PyObject *p,
          Py_ssize_t pos)
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the
     object at position 'pos' in the tuple pointed to by 'p'.  If 'pos'
     is negative or out of bounds, return ‘NULL’ and set an *note
     IndexError: 14a3. exception.

     The returned reference is borrowed from the tuple 'p' (that is: it
     is only valid as long as you hold a reference to 'p').  To get a
     *note strong reference: 2ee, use *note
     Py_NewRef(PyTuple_GetItem(...)): 83e. or *note
     PySequence_GetItem(): 1959.

 -- C 函式: *note PyObject: 311. *PyTuple_GET_ITEM (PyObject *p,
          Py_ssize_t pos)
     '回傳值：借用參照。' Like *note PyTuple_GetItem(): 46ed, but does
     no checking of its arguments.

 -- C 函式: *note PyObject: 311. *PyTuple_GetSlice (PyObject *p,
          Py_ssize_t low, Py_ssize_t high)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the
     slice of the tuple pointed to by 'p' between 'low' and 'high', or
     ‘NULL’ with an exception set on failure.

     This is the equivalent of the Python expression ‘p[low:high]’.
     Indexing from the end of the tuple is not supported.

 -- C 函式: int PyTuple_SetItem (PyObject *p, Py_ssize_t pos, PyObject
          *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Insert a reference to object
     'o' at position 'pos' of the tuple pointed to by 'p'.  Return ‘0’
     on success.  If 'pos' is out of bounds, return ‘-1’ and set an
     *note IndexError: 14a3. exception.

          備註: This function "steals" a reference to 'o' and discards a
          reference to an item already in the tuple at the affected
          position.

 -- C 函式: void PyTuple_SET_ITEM (PyObject *p, Py_ssize_t pos, PyObject
          *o)

     Like *note PyTuple_SetItem(): 46ee, but does no error checking, and
     should 'only' be used to fill in brand new tuples.

     Bounds checking is performed as an assertion if Python is built in
     *note debug mode: 1de. or *note with assertions: 304.

          備註: This function "steals" a reference to 'o', and, unlike
          *note PyTuple_SetItem(): 46ee, does 'not' discard a reference
          to any item that is being replaced; any reference in the tuple
          at position 'pos' will be leaked.

 -- C 函式: int _PyTuple_Resize (PyObject **p, Py_ssize_t newsize)

     Can be used to resize a tuple.  'newsize' will be the new length of
     the tuple.  Because tuples are 'supposed' to be immutable, this
     should only be used if there is only one reference to the object.
     Do 'not' use this if the tuple may already be known to some other
     part of the code.  The tuple will always grow or shrink at the end.
     Think of this as destroying the old tuple and creating a new one,
     only more efficiently.  Returns ‘0’ on success.  Client code should
     never assume that the resulting value of ‘*p’ will be the same as
     before calling this function.  If the object referenced by ‘*p’ is
     replaced, the original ‘*p’ is destroyed.  On failure, returns ‘-1’
     and sets ‘*p’ to ‘NULL’, and raises *note MemoryError: 15bc. or
     *note SystemError: 51b.


File: python.info,  Node: Struct Sequence Objects,  Next: List（串列）物件,  Prev: Tuple（元組）物件,  Up: 序列物件

7.8.3.29 Struct Sequence Objects
................................

Struct sequence objects are the C equivalent of *note namedtuple(): 1ae.
objects, i.e.  a sequence whose items can also be accessed through
attributes.  To create a struct sequence, you first have to create a
specific struct sequence type.

 -- C 函式: *note PyTypeObject: a48. *PyStructSequence_NewType
          (PyStructSequence_Desc *desc)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a
     new struct sequence type from the data in 'desc', described below.
     Instances of the resulting type can be created with *note
     PyStructSequence_New(): 4861.

     Return ‘NULL’ with an exception set on failure.

 -- C 函式: void PyStructSequence_InitType (PyTypeObject *type,
          PyStructSequence_Desc *desc)

     Initializes a struct sequence type 'type' from 'desc' in place.

 -- C 函式: int PyStructSequence_InitType2 (PyTypeObject *type,
          PyStructSequence_Desc *desc)

     Like *note PyStructSequence_InitType(): fa4, but returns ‘0’ on
     success and ‘-1’ with an exception set on failure.

     在 3.4 版被加入.

 -- C 型別: type PyStructSequence_Desc
     ' 為 *note 穩定 ABI 的一部分: 4f9. （包含所有成員）.'  Contains the
     meta information of a struct sequence type to create.

      -- C 成員函數: const char *name

          Name of the struct sequence type.

      -- C 成員函數: const char *doc

          Pointer to docstring for the type or ‘NULL’ to omit.

      -- C 成員函數: *note PyStructSequence_Field: b60. *fields

          Pointer to ‘NULL’-terminated array with field names of the new
          type.

      -- C 成員函數: int n_in_sequence

          Number of fields visible to the Python side (if used as
          tuple).

 -- C 型別: type PyStructSequence_Field
     ' 為 *note 穩定 ABI 的一部分: 4f9. （包含所有成員）.'  Describes a
     field of a struct sequence.  As a struct sequence is modeled as a
     tuple, all fields are typed as *note PyObject: 311.*.  The index in
     the *note fields: 4a57. array of the *note PyStructSequence_Desc:
     b61. determines which field of the struct sequence is described.

      -- C 成員函數: const char *name

          Name for the field or ‘NULL’ to end the list of named fields,
          set to *note PyStructSequence_UnnamedField: 926. to leave
          unnamed.

      -- C 成員函數: const char *doc

          Field docstring or ‘NULL’ to omit.

 -- C 變數: const char *const PyStructSequence_UnnamedField
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.11 版本開始.'  Special
     value for a field name to leave it unnamed.

     在 3.9 版的變更: The type was changed from ‘char *’.

 -- C 函式: *note PyObject: 311. *PyStructSequence_New (PyTypeObject
          *type)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Creates an
     instance of 'type', which must have been created with *note
     PyStructSequence_NewType(): 4862.

     Return ‘NULL’ with an exception set on failure.

 -- C 函式: *note PyObject: 311. *PyStructSequence_GetItem (PyObject *p,
          Py_ssize_t pos)
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the
     object at position 'pos' in the struct sequence pointed to by 'p'.

     Bounds checking is performed as an assertion if Python is built in
     *note debug mode: 1de. or *note with assertions: 304.

 -- C 函式: *note PyObject: 311. *PyStructSequence_GET_ITEM (PyObject
          *p, Py_ssize_t pos)
     '回傳值：借用參照。' Alias to *note PyStructSequence_GetItem():
     4860.

     在 3.13 版的變更: Now implemented as an alias to *note
     PyStructSequence_GetItem(): 4860.

 -- C 函式: void PyStructSequence_SetItem (PyObject *p, Py_ssize_t pos,
          PyObject *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Sets the field at index 'pos'
     of the struct sequence 'p' to value 'o'.  Like *note
     PyTuple_SET_ITEM(): 305, this should only be used to fill in brand
     new instances.

     Bounds checking is performed as an assertion if Python is built in
     *note debug mode: 1de. or *note with assertions: 304.

          備註: This function "steals" a reference to 'o'.

 -- C 函式: void PyStructSequence_SET_ITEM (PyObject *p, Py_ssize_t
          *pos, PyObject *o)

     Alias to *note PyStructSequence_SetItem(): 4863.

     在 3.13 版的變更: Now implemented as an alias to *note
     PyStructSequence_SetItem(): 4863.


File: python.info,  Node: List（串列）物件,  Prev: Struct Sequence Objects,  Up: 序列物件

7.8.3.30 List（串列）物件
.........................

 -- C 型別: type PyListObject

     *note PyObject: 311. 的這個子型別表示 Python 的 list（串列）物件。

 -- C 變數: *note PyTypeObject: a48. PyList_Type
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  此 *note PyTypeObject: a48. 實
     例表示 Python 的 list 型別。這與 Python 層中的 *note list: 5b6. 是
     同一個物件。

 -- C 函式: int PyList_Check (PyObject *p)

     如果 'p' 是一個 list 物件或者是 list 型別之子型別的實例，就回傳
     true。這個函式永遠會成功執行。

 -- C 函式: int PyList_CheckExact (PyObject *p)

     如果 'p' 是一個 list 物件但不是 list 型別的子型別的實例，就回傳
     true。這個函式永遠會成功執行。

 -- C 函式: *note PyObject: 311. *PyList_New (Py_ssize_t len)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  成功時回傳
     長度為 'len' 的新串列，失敗時回傳 ‘NULL’。

          備註: If 'len' is greater than zero, the returned list
          object's items are set to ‘NULL’.  Thus you cannot use
          abstract API functions such as *note PySequence_SetItem():
          195a. or expose the object to Python code before setting all
          items to a real object with *note PyList_SetItem(): 46ef. or
          *note PyList_SET_ITEM(): 306.  The following APIs are safe
          APIs before the list is fully initialized: *note
          PyList_SetItem(): 46ef. and *note PyList_SET_ITEM(): 306.

 -- C 函式: *note Py_ssize_t: a03. PyList_Size (PyObject *list)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     回傳 'list' 串列物件的長度；這相當於串列物件的 ‘len(list)’。

 -- C 函式: *note Py_ssize_t: a03. PyList_GET_SIZE (PyObject *list)

     與 *note PyList_Size(): 1387. 類似，但沒有錯誤檢查。

 -- C 函式: *note PyObject: 311. *PyList_GetItemRef (PyObject *list,
          Py_ssize_t index)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本
     開始.'  Return the object at position 'index' in the list pointed
     to by 'list'.  The position must be non-negative; indexing from the
     end of the list is not supported.  If 'index' is out of bounds (‘<0
     or >=len(list)’), return ‘NULL’ and set an *note IndexError: 14a3.
     exception.

     在 3.13 版被加入.

 -- C 函式: *note PyObject: 311. *PyList_GetItem (PyObject *list,
          Py_ssize_t index)
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Like *note
     PyList_GetItemRef(): 312, but returns a *note borrowed reference:
     2ef. instead of a *note strong reference: 2ee.

 -- C 函式: *note PyObject: 311. *PyList_GET_ITEM (PyObject *list,
          Py_ssize_t i)
     '回傳值：借用參照。' 與 *note PyList_GetItem(): 313. 類似，但沒有錯
     誤檢查。

 -- C 函式: int PyList_SetItem (PyObject *list, Py_ssize_t index,
          PyObject *item)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  將串列中索引 'index' 處的項目
     設定為 'item'。成功時回傳 ‘0’。如果 'index' 超出邊界範圍則回傳 ‘-1’
     並設定一個 *note IndexError: 14a3. 例外。

          備註: 此函式「竊取」對 'item' 的參照，並丟棄對串列中受影響位置
          上已存在項目的參照。

 -- C 函式: void PyList_SET_ITEM (PyObject *list, Py_ssize_t i, PyObject
          *o)

     *note PyList_SetItem(): 46ef. 的巨集形式，沒有錯誤檢查。這通常僅用
     於填充沒有已存在內容的新串列。

     Bounds checking is performed as an assertion if Python is built in
     *note debug mode: 1de. or *note with assertions: 304.

          備註: 該巨集「竊取」對 'item' 的參照，並且與 *note
          PyList_SetItem(): 46ef. 不同的是，它'不會'丟棄對任意被替換項目
          的參照；'list' 中位置 'i' 的任何參照都將被洩漏 (leak)。

 -- C 函式: int PyList_Insert (PyObject *list, Py_ssize_t index,
          PyObject *item)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  將項目 'item' 插入串列 'list'
     中索引 'index' 的位置之前。如果成功則回傳 ‘0’；如果失敗則回傳 ‘-1’
     並設定例外。類似於 ‘list.insert(index, item)’。

 -- C 函式: int PyList_Append (PyObject *list, PyObject *item)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  將物件 'item' 附加到串列
     'list' 的最後面。如果成功則回傳 ‘0’；如果不成功，則回傳 ‘-1’ 並設定
     例外。類似於 ‘list.append(item)’。

 -- C 函式: *note PyObject: 311. *PyList_GetSlice (PyObject *list,
          Py_ssize_t low, Py_ssize_t high)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  回傳
     'list' 中的物件串列，其中包含 'low' 和 'high' '之間'的物件。如果沒
     有成功則回傳 ‘NULL’ 並設定例外。類似於 ‘list[low:high]’。不支援從串
     列尾末開始索引。

 -- C 函式: int PyList_SetSlice (PyObject *list, Py_ssize_t low,
          Py_ssize_t high, PyObject *itemlist)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  將 'low' 和 'high' 之間的
     'list' 切片設定為 'itemlist' 的內容。類似於 ‘list[low:high] =
     itemlist’。'itemlist' 可能為 ‘NULL’，表示分配一個空串列（切片刪除）
     。成功時回傳 ‘0’，失敗時則回傳 ‘-1’。不支援從串列尾末開始索引。

 -- C 函式: int PyList_Extend (PyObject *list, PyObject *iterable)

     Extend 'list' with the contents of 'iterable'.  This is the same as
     ‘PyList_SetSlice(list, PY_SSIZE_T_MAX, PY_SSIZE_T_MAX, iterable)’
     and analogous to ‘list.extend(iterable)’ or ‘list += iterable’.

     Raise an exception and return ‘-1’ if 'list' is not a *note list:
     5b6. object.  Return 0 on success.

     在 3.13 版被加入.

 -- C 函式: int PyList_Clear (PyObject *list)

     Remove all items from 'list'.  This is the same as
     ‘PyList_SetSlice(list, 0, PY_SSIZE_T_MAX, NULL)’ and analogous to
     ‘list.clear()’ or ‘del list[:]’.

     Raise an exception and return ‘-1’ if 'list' is not a *note list:
     5b6. object.  Return 0 on success.

     在 3.13 版被加入.

 -- C 函式: int PyList_Sort (PyObject *list)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  對 'list' 的項目進行原地 (in
     place) 排序。成功時回傳 ‘0’，失敗時回傳 ‘-1’。這相當於
     ‘list.sort()’。

 -- C 函式: int PyList_Reverse (PyObject *list)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  原地反轉 'list' 的項目。成功時
     回傳 ‘0’，失敗時回傳 ‘-1’。這相當於 ‘list.reverse()’。

 -- C 函式: *note PyObject: 311. *PyList_AsTuple (PyObject *list)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

     回傳一個新的 tuple（元組）物件，其中包含 'list' 的內容；相當於
     ‘tuple(list)’。


File: python.info,  Node: 容器物件,  Next: 函式物件<2>,  Prev: 序列物件,  Up: 具體物件層

7.8.4 容器物件
--------------

* Menu:

* 字典物件::
* 集合物件::


File: python.info,  Node: 字典物件,  Next: 集合物件,  Up: 容器物件

7.8.4.1 字典物件
................

 -- C 型別: type PyDictObject

     *note PyObject: 311. 子型態代表一個 Python 字典物件。

 -- C 變數: *note PyTypeObject: a48. PyDict_Type
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  *note PyTypeObject: a48. 實例
     代表一個 Python 字典型態。此與 Python 層中的 *note dict: 23b. 為同
     一個物件。

 -- C 函式: int PyDict_Check (PyObject *p)

     若 'p' 是一個字典物件或字典的子型態實例則會回傳 true。此函式每次都
     會執行成功。

 -- C 函式: int PyDict_CheckExact (PyObject *p)

     若 'p' 是一個字典物件但並不是一個字典子型態的實例，則回傳 true。此
     函式每次都會執行成功。

 -- C 函式: *note PyObject: 311. *PyDict_New ()
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  回傳一個新
     的空字典，或在失敗時回傳 ‘NULL’。

 -- C 函式: *note PyObject: 311. *PyDictProxy_New (PyObject *mapping)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     *note types.MappingProxyType: 414. object for a mapping which
     enforces read-only behavior.  This is normally used to create a
     view to prevent modification of the dictionary for non-dynamic
     class types.

 -- C 函式: void PyDict_Clear (PyObject *p)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Empty an existing dictionary
     of all key-value pairs.

 -- C 函式: int PyDict_Contains (PyObject *p, PyObject *key)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Determine if dictionary 'p'
     contains 'key'.  If an item in 'p' is matches 'key', return ‘1’,
     otherwise return ‘0’.  On error, return ‘-1’.  This is equivalent
     to the Python expression ‘key in p’.

 -- C 函式: int PyDict_ContainsString (PyObject *p, const char *key)

     This is the same as *note PyDict_Contains(): 310, but 'key' is
     specified as a const char* UTF-8 encoded bytes string, rather than
     a *note PyObject: 311.*.

     在 3.13 版被加入.

 -- C 函式: *note PyObject: 311. *PyDict_Copy (PyObject *p)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     new dictionary that contains the same key-value pairs as 'p'.

 -- C 函式: int PyDict_SetItem (PyObject *p, PyObject *key, PyObject
          *val)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Insert 'val' into the
     dictionary 'p' with a key of 'key'.  'key' must be *note hashable:
     5b5.; if it isn't, *note TypeError: 4dd. will be raised.  Return
     ‘0’ on success or ‘-1’ on failure.  This function 'does not' steal
     a reference to 'val'.

 -- C 函式: int PyDict_SetItemString (PyObject *p, const char *key,
          PyObject *val)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This is the same as *note
     PyDict_SetItem(): 46f0, but 'key' is specified as a const char*
     UTF-8 encoded bytes string, rather than a *note PyObject: 311.*.

 -- C 函式: int PyDict_DelItem (PyObject *p, PyObject *key)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Remove the entry in dictionary
     'p' with key 'key'.  'key' must be *note hashable: 5b5.; if it
     isn't, *note TypeError: 4dd. is raised.  If 'key' is not in the
     dictionary, *note KeyError: 2fb. is raised.  Return ‘0’ on success
     or ‘-1’ on failure.

 -- C 函式: int PyDict_DelItemString (PyObject *p, const char *key)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This is the same as *note
     PyDict_DelItem(): 47b4, but 'key' is specified as a const char*
     UTF-8 encoded bytes string, rather than a *note PyObject: 311.*.

 -- C 函式: int PyDict_GetItemRef (PyObject *p, PyObject *key, PyObject
          **result)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Return a new
     *note strong reference: 2ee. to the object from dictionary 'p'
     which has a key 'key':

        * If the key is present, set '*result' to a new *note strong
          reference: 2ee. to the value and return ‘1’.

        * If the key is missing, set '*result' to ‘NULL’ and return ‘0’.

        * On error, raise an exception and return ‘-1’.

     在 3.13 版被加入.

     See also the *note PyObject_GetItem(): 2f9. function.

 -- C 函式: *note PyObject: 311. *PyDict_GetItem (PyObject *p, PyObject
          *key)
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     *note borrowed reference: 2ef. to the object from dictionary 'p'
     which has a key 'key'.  Return ‘NULL’ if the key 'key' is missing
     'without' setting an exception.

          備註: Exceptions that occur while this calls *note __hash__():
          a9e. and *note __eq__(): a9d. methods are silently ignored.
          Prefer the *note PyDict_GetItemWithError(): 30c. function
          instead.

     在 3.10 版的變更: Calling this API without *note GIL: 13e. held had
     been allowed for historical reason.  It is no longer allowed.

 -- C 函式: *note PyObject: 311. *PyDict_GetItemWithError (PyObject *p,
          PyObject *key)
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Variant of
     *note PyDict_GetItem(): 35b. that does not suppress exceptions.
     Return ‘NULL’ 'with' an exception set if an exception occurred.
     Return ‘NULL’ 'without' an exception set if the key wasn't present.

 -- C 函式: *note PyObject: 311. *PyDict_GetItemString (PyObject *p,
          const char *key)
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  This is
     the same as *note PyDict_GetItem(): 35b, but 'key' is specified as
     a const char* UTF-8 encoded bytes string, rather than a *note
     PyObject: 311.*.

          備註: Exceptions that occur while this calls *note __hash__():
          a9e. and *note __eq__(): a9d. methods or while creating the
          temporary *note str: 3f2. object are silently ignored.  Prefer
          using the *note PyDict_GetItemWithError(): 30c. function with
          your own *note PyUnicode_FromString(): 4748. 'key' instead.

 -- C 函式: int PyDict_GetItemStringRef (PyObject *p, const char *key,
          PyObject **result)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Similar than
     *note PyDict_GetItemRef(): 30a, but 'key' is specified as a const
     char* UTF-8 encoded bytes string, rather than a *note PyObject:
     311.*.

     在 3.13 版被加入.

 -- C 函式: *note PyObject: 311. *PyDict_SetDefault (PyObject *p,
          PyObject *key, PyObject *defaultobj)
     '回傳值：借用參照。' This is the same as the Python-level *note
     dict.setdefault(): 101a.  If present, it returns the value
     corresponding to 'key' from the dictionary 'p'.  If the key is not
     in the dict, it is inserted with value 'defaultobj' and
     'defaultobj' is returned.  This function evaluates the hash
     function of 'key' only once, instead of evaluating it independently
     for the lookup and the insertion.

     在 3.4 版被加入.

 -- C 函式: int PyDict_SetDefaultRef (PyObject *p, PyObject *key,
          PyObject *default_value, PyObject **result)

     Inserts 'default_value' into the dictionary 'p' with a key of 'key'
     if the key is not already present in the dictionary.  If 'result'
     is not ‘NULL’, then '*result' is set to a *note strong reference:
     2ee. to either 'default_value', if the key was not present, or the
     existing value, if 'key' was already present in the dictionary.
     Returns ‘1’ if the key was present and 'default_value' was not
     inserted, or ‘0’ if the key was not present and 'default_value' was
     inserted.  On failure, returns ‘-1’, sets an exception, and sets
     ‘*result’ to ‘NULL’.

     For clarity: if you have a strong reference to 'default_value'
     before calling this function, then after it returns, you hold a
     strong reference to both 'default_value' and '*result' (if it's not
     ‘NULL’).  These may refer to the same object: in that case you hold
     two separate references to it.

     在 3.13 版被加入.

 -- C 函式: int PyDict_Pop (PyObject *p, PyObject *key, PyObject
          **result)

     Remove 'key' from dictionary 'p' and optionally return the removed
     value.  Do not raise *note KeyError: 2fb. if the key missing.

        - If the key is present, set '*result' to a new reference to the
          removed value if 'result' is not ‘NULL’, and return ‘1’.

        - If the key is missing, set '*result' to ‘NULL’ if 'result' is
          not ‘NULL’, and return ‘0’.

        - On error, raise an exception and return ‘-1’.

     This is similar to *note dict.pop(): 32d, but without the default
     value and not raising *note KeyError: 2fb. if the key missing.

     在 3.13 版被加入.

 -- C 函式: int PyDict_PopString (PyObject *p, const char *key, PyObject
          **result)

     Similar to *note PyDict_Pop(): 32b, but 'key' is specified as a
     const char* UTF-8 encoded bytes string, rather than a *note
     PyObject: 311.*.

     在 3.13 版被加入.

 -- C 函式: *note PyObject: 311. *PyDict_Items (PyObject *p)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     *note PyListObject: 4983. containing all the items from the
     dictionary.

 -- C 函式: *note PyObject: 311. *PyDict_Keys (PyObject *p)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     *note PyListObject: 4983. containing all the keys from the
     dictionary.

 -- C 函式: *note PyObject: 311. *PyDict_Values (PyObject *p)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     *note PyListObject: 4983. containing all the values from the
     dictionary 'p'.

 -- C 函式: *note Py_ssize_t: a03. PyDict_Size (PyObject *p)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     Return the number of items in the dictionary.  This is equivalent
     to ‘len(p)’ on a dictionary.

 -- C 函式: int PyDict_Next (PyObject *p, Py_ssize_t *ppos, PyObject
          **pkey, PyObject **pvalue)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Iterate over all key-value
     pairs in the dictionary 'p'.  The *note Py_ssize_t: a03. referred
     to by 'ppos' must be initialized to ‘0’ prior to the first call to
     this function to start the iteration; the function returns true for
     each pair in the dictionary, and false once all pairs have been
     reported.  The parameters 'pkey' and 'pvalue' should either point
     to *note PyObject: 311.* variables that will be filled in with each
     key and value, respectively, or may be ‘NULL’.  Any references
     returned through them are borrowed.  'ppos' should not be altered
     during iteration.  Its value represents offsets within the internal
     dictionary structure, and since the structure is sparse, the
     offsets are not consecutive.

     舉例來說：

          PyObject *key, *value;
          Py_ssize_t pos = 0;

          while (PyDict_Next(self->dict, &pos, &key, &value)) {
              /* do something interesting with the values... */
              ...
          }

     The dictionary 'p' should not be mutated during iteration.  It is
     safe to modify the values of the keys as you iterate over the
     dictionary, but only so long as the set of keys does not change.
     For example:

          PyObject *key, *value;
          Py_ssize_t pos = 0;

          while (PyDict_Next(self->dict, &pos, &key, &value)) {
              long i = PyLong_AsLong(value);
              if (i == -1 && PyErr_Occurred()) {
                  return -1;
              }
              PyObject *o = PyLong_FromLong(i + 1);
              if (o == NULL)
                  return -1;
              if (PyDict_SetItem(self->dict, key, o) < 0) {
                  Py_DECREF(o);
                  return -1;
              }
              Py_DECREF(o);
          }

     The function is not thread-safe in the *note free-threaded: 42d1.
     build without external synchronization.  You can use *note
     Py_BEGIN_CRITICAL_SECTION: 4a69. to lock the dictionary while
     iterating over it:

          Py_BEGIN_CRITICAL_SECTION(self->dict);
          while (PyDict_Next(self->dict, &pos, &key, &value)) {
              ...
          }
          Py_END_CRITICAL_SECTION();

 -- C 函式: int PyDict_Merge (PyObject *a, PyObject *b, int override)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Iterate over mapping object
     'b' adding key-value pairs to dictionary 'a'.  'b' may be a
     dictionary, or any object supporting *note PyMapping_Keys(): b63.
     and *note PyObject_GetItem(): 2f9.  If 'override' is true, existing
     pairs in 'a' will be replaced if a matching key is found in 'b',
     otherwise pairs will only be added if there is not a matching key
     in 'a'.  Return ‘0’ on success or ‘-1’ if an exception was raised.

 -- C 函式: int PyDict_Update (PyObject *a, PyObject *b)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This is the same as
     ‘PyDict_Merge(a, b, 1)’ in C, and is similar to ‘a.update(b)’ in
     Python except that *note PyDict_Update(): 47bd. doesn't fall back
     to the iterating over a sequence of key value pairs if the second
     argument has no "keys" attribute.  Return ‘0’ on success or ‘-1’ if
     an exception was raised.

 -- C 函式: int PyDict_MergeFromSeq2 (PyObject *a, PyObject *seq2, int
          override)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Update or merge into
     dictionary 'a', from the key-value pairs in 'seq2'.  'seq2' must be
     an iterable object producing iterable objects of length 2, viewed
     as key-value pairs.  In case of duplicate keys, the last wins if
     'override' is true, else the first wins.  Return ‘0’ on success or
     ‘-1’ if an exception was raised.  Equivalent Python (except for the
     return value):

          def PyDict_MergeFromSeq2(a, seq2, override):
              for key, value in seq2:
                  if override or key not in a:
                      a[key] = value

 -- C 函式: int PyDict_AddWatcher (PyDict_WatchCallback callback)

     Register 'callback' as a dictionary watcher.  Return a non-negative
     integer id which must be passed to future calls to *note
     PyDict_Watch(): 509.  In case of error (e.g.  no more watcher IDs
     available), return ‘-1’ and set an exception.

     在 3.12 版被加入.

 -- C 函式: int PyDict_ClearWatcher (int watcher_id)

     Clear watcher identified by 'watcher_id' previously returned from
     *note PyDict_AddWatcher(): 508.  Return ‘0’ on success, ‘-1’ on
     error (e.g.  if the given 'watcher_id' was never registered.)

     在 3.12 版被加入.

 -- C 函式: int PyDict_Watch (int watcher_id, PyObject *dict)

     Mark dictionary 'dict' as watched.  The callback granted
     'watcher_id' by *note PyDict_AddWatcher(): 508. will be called when
     'dict' is modified or deallocated.  Return ‘0’ on success or ‘-1’
     on error.

     在 3.12 版被加入.

 -- C 函式: int PyDict_Unwatch (int watcher_id, PyObject *dict)

     Mark dictionary 'dict' as no longer watched.  The callback granted
     'watcher_id' by *note PyDict_AddWatcher(): 508. will no longer be
     called when 'dict' is modified or deallocated.  The dict must
     previously have been watched by this watcher.  Return ‘0’ on
     success or ‘-1’ on error.

     在 3.12 版被加入.

 -- C 型別: type PyDict_WatchEvent

     Enumeration of possible dictionary watcher events:
     ‘PyDict_EVENT_ADDED’, ‘PyDict_EVENT_MODIFIED’,
     ‘PyDict_EVENT_DELETED’, ‘PyDict_EVENT_CLONED’,
     ‘PyDict_EVENT_CLEARED’, or ‘PyDict_EVENT_DEALLOCATED’.

     在 3.12 版被加入.

 -- C 型別: typedef int (*PyDict_WatchCallback)(*note PyDict_WatchEvent:
          4a6c. event, *note PyObject: 311. *dict, *note PyObject: 311.
          *key, *note PyObject: 311. *new_value)

     Type of a dict watcher callback function.

     If 'event' is ‘PyDict_EVENT_CLEARED’ or ‘PyDict_EVENT_DEALLOCATED’,
     both 'key' and 'new_value' will be ‘NULL’.  If 'event' is
     ‘PyDict_EVENT_ADDED’ or ‘PyDict_EVENT_MODIFIED’, 'new_value' will
     be the new value for 'key'.  If 'event' is ‘PyDict_EVENT_DELETED’,
     'key' is being deleted from the dictionary and 'new_value' will be
     ‘NULL’.

     ‘PyDict_EVENT_CLONED’ occurs when 'dict' was previously empty and
     another dict is merged into it.  To maintain efficiency of this
     operation, per-key ‘PyDict_EVENT_ADDED’ events are not issued in
     this case; instead a single ‘PyDict_EVENT_CLONED’ is issued, and
     'key' will be the source dictionary.

     The callback may inspect but must not modify 'dict'; doing so could
     have unpredictable effects, including infinite recursion.  Do not
     trigger Python code execution in the callback, as it could modify
     the dict as a side effect.

     If 'event' is ‘PyDict_EVENT_DEALLOCATED’, taking a new reference in
     the callback to the about-to-be-destroyed dictionary will resurrect
     it and prevent it from being freed at this time.  When the
     resurrected object is destroyed later, any watcher callbacks active
     at that time will be called again.

     Callbacks occur before the notified modification to 'dict' takes
     place, so the prior state of 'dict' can be inspected.

     If the callback sets an exception, it must return ‘-1’; this
     exception will be printed as an unraisable exception using *note
     PyErr_WriteUnraisable(): 328.  Otherwise it should return ‘0’.

     There may already be a pending exception set on entry to the
     callback.  In this case, the callback should return ‘0’ with the
     same exception still set.  This means the callback may not call any
     other API that can set an exception unless it saves and clears the
     exception state first, and restores it before returning.

     在 3.12 版被加入.


File: python.info,  Node: 集合物件,  Prev: 字典物件,  Up: 容器物件

7.8.4.2 集合物件
................

This section details the public API for *note set: 57d. and *note
frozenset: 57e. objects.  Any functionality not listed below is best
accessed using either the abstract object protocol (including *note
PyObject_CallMethod(): 366, *note PyObject_RichCompareBool(): 18a7,
*note PyObject_Hash(): 3cb, *note PyObject_Repr(): fd2, *note
PyObject_IsTrue(): 483f, *note PyObject_Print(): 14e4, and *note
PyObject_GetIter(): 483e.) or the abstract number protocol (including
*note PyNumber_And(): 4813, *note PyNumber_Subtract(): 482c, *note
PyNumber_Or(): 4827, *note PyNumber_Xor(): 482e, *note
PyNumber_InPlaceAnd(): 4818, *note PyNumber_InPlaceSubtract(): 4820,
*note PyNumber_InPlaceOr(): 481c, and *note PyNumber_InPlaceXor():
4822.).

 -- C 型別: type PySetObject

     This subtype of *note PyObject: 311. is used to hold the internal
     data for both *note set: 57d. and *note frozenset: 57e. objects.
     It is like a *note PyDictObject: 38c. in that it is a fixed size
     for small sets (much like tuple storage) and will point to a
     separate, variable sized block of memory for medium and large sized
     sets (much like list storage).  None of the fields of this
     structure should be considered public and all are subject to
     change.  All access should be done through the documented API
     rather than by manipulating the values in the structure.

 -- C 變數: *note PyTypeObject: a48. PySet_Type
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This is an instance of *note
     PyTypeObject: a48. representing the Python *note set: 57d. type.

 -- C 變數: *note PyTypeObject: a48. PyFrozenSet_Type
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This is an instance of *note
     PyTypeObject: a48. representing the Python *note frozenset: 57e.
     type.

The following type check macros work on pointers to any Python object.
Likewise, the constructor functions work with any iterable Python
object.

 -- C 函式: int PySet_Check (PyObject *p)

     Return true if 'p' is a *note set: 57d. object or an instance of a
     subtype.  This function always succeeds.

 -- C 函式: int PyFrozenSet_Check (PyObject *p)

     Return true if 'p' is a *note frozenset: 57e. object or an instance
     of a subtype.  This function always succeeds.

 -- C 函式: int PyAnySet_Check (PyObject *p)

     Return true if 'p' is a *note set: 57d. object, a *note frozenset:
     57e. object, or an instance of a subtype.  This function always
     succeeds.

 -- C 函式: int PySet_CheckExact (PyObject *p)

     Return true if 'p' is a *note set: 57d. object but not an instance
     of a subtype.  This function always succeeds.

     在 3.10 版被加入.

 -- C 函式: int PyAnySet_CheckExact (PyObject *p)

     Return true if 'p' is a *note set: 57d. object or a *note
     frozenset: 57e. object but not an instance of a subtype.  This
     function always succeeds.

 -- C 函式: int PyFrozenSet_CheckExact (PyObject *p)

     Return true if 'p' is a *note frozenset: 57e. object but not an
     instance of a subtype.  This function always succeeds.

 -- C 函式: *note PyObject: 311. *PySet_New (PyObject *iterable)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     new *note set: 57d. containing objects returned by the 'iterable'.
     The 'iterable' may be ‘NULL’ to create a new empty set.  Return the
     new set on success or ‘NULL’ on failure.  Raise *note TypeError:
     4dd. if 'iterable' is not actually iterable.  The constructor is
     also useful for copying a set (‘c=set(s)’).

 -- C 函式: *note PyObject: 311. *PyFrozenSet_New (PyObject *iterable)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     new *note frozenset: 57e. containing objects returned by the
     'iterable'.  The 'iterable' may be ‘NULL’ to create a new empty
     frozenset.  Return the new set on success or ‘NULL’ on failure.
     Raise *note TypeError: 4dd. if 'iterable' is not actually iterable.

The following functions and macros are available for instances of *note
set: 57d. or *note frozenset: 57e. or instances of their subtypes.

 -- C 函式: *note Py_ssize_t: a03. PySet_Size (PyObject *anyset)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     Return the length of a *note set: 57d. or *note frozenset: 57e.
     object.  Equivalent to ‘len(anyset)’.  Raises a *note SystemError:
     51b. if 'anyset' is not a *note set: 57d, *note frozenset: 57e, or
     an instance of a subtype.

 -- C 函式: *note Py_ssize_t: a03. PySet_GET_SIZE (PyObject *anyset)

     Macro form of *note PySet_Size(): 13b7. without error checking.

 -- C 函式: int PySet_Contains (PyObject *anyset, PyObject *key)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return ‘1’ if found, ‘0’ if
     not found, and ‘-1’ if an error is encountered.  Unlike the Python
     *note __contains__(): 1e33. method, this function does not
     automatically convert unhashable sets into temporary frozensets.
     Raise a *note TypeError: 4dd. if the 'key' is unhashable.  Raise
     *note SystemError: 51b. if 'anyset' is not a *note set: 57d, *note
     frozenset: 57e, or an instance of a subtype.

 -- C 函式: int PySet_Add (PyObject *set, PyObject *key)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Add 'key' to a *note set: 57d.
     instance.  Also works with *note frozenset: 57e. instances (like
     *note PyTuple_SetItem(): 46ee. it can be used to fill in the values
     of brand new frozensets before they are exposed to other code).
     Return ‘0’ on success or ‘-1’ on failure.  Raise a *note TypeError:
     4dd. if the 'key' is unhashable.  Raise a *note MemoryError: 15bc.
     if there is no room to grow.  Raise a *note SystemError: 51b. if
     'set' is not an instance of *note set: 57d. or its subtype.

The following functions are available for instances of *note set: 57d.
or its subtypes but not for instances of *note frozenset: 57e. or its
subtypes.

 -- C 函式: int PySet_Discard (PyObject *set, PyObject *key)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return ‘1’ if found and
     removed, ‘0’ if not found (no action taken), and ‘-1’ if an error
     is encountered.  Does not raise *note KeyError: 2fb. for missing
     keys.  Raise a *note TypeError: 4dd. if the 'key' is unhashable.
     Unlike the Python *note discard(): 2119. method, this function does
     not automatically convert unhashable sets into temporary
     frozensets.  Raise *note SystemError: 51b. if 'set' is not an
     instance of *note set: 57d. or its subtype.

 -- C 函式: *note PyObject: 311. *PySet_Pop (PyObject *set)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     new reference to an arbitrary object in the 'set', and removes the
     object from the 'set'.  Return ‘NULL’ on failure.  Raise *note
     KeyError: 2fb. if the set is empty.  Raise a *note SystemError:
     51b. if 'set' is not an instance of *note set: 57d. or its subtype.

 -- C 函式: int PySet_Clear (PyObject *set)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Empty an existing set of all
     elements.  Return ‘0’ on success.  Return ‘-1’ and raise *note
     SystemError: 51b. if 'set' is not an instance of *note set: 57d. or
     its subtype.


File: python.info,  Node: 函式物件<2>,  Next: 其他物件<2>,  Prev: 容器物件,  Up: 具體物件層

7.8.5 函式物件
--------------

* Menu:

* 函式物件 (Function Objects): 函式物件 Function Objects.
* 實例方法物件 (Instance Method Objects): 實例方法物件 Instance Method Objects.
* 方法物件 (Method Objects): 方法物件 Method Objects.
* Cell 物件::
* 程式碼物件::
* Extra information::


File: python.info,  Node: 函式物件 Function Objects,  Next: 實例方法物件 Instance Method Objects,  Up: 函式物件<2>

7.8.5.1 函式物件 (Function Objects)
...................................

這有一些特用於 Python 函式的函式。

 -- C 型別: type PyFunctionObject

     用於函式的 C 結構。

 -- C 變數: *note PyTypeObject: a48. PyFunction_Type

     這是個 *note PyTypeObject: a48. 的實例，且代表了 Python 函式型別，
     Python 程式設計者可透過 ‘types.FunctionType’ 使用它。

 -- C 函式: int PyFunction_Check (PyObject *o)

     如果 'o' 是個函式物件（擁有 *note PyFunction_Type: 4a7d. 的型別）則
     回傳 true。參數必須不為 ‘NULL’。此函式必能成功執行。

 -- C 函式: *note PyObject: 311. *PyFunction_New (PyObject *code,
          PyObject *globals)
     '回傳值：新的參照。' 回傳一個與程式碼物件 'code' 相關聯的函式物件。
     'globals' 必須是一個帶有函式能夠存取的全域變數的字典。

     函式的文件字串 (docstring) 和名稱是從程式碼物件所取得，*note
     __module__: 1ded. 是自 'globals' 所取得。引數預設值、標註
     (annotation) 和閉包 (closure) 被設為 ‘NULL’，*note __qualname__:
     1deb. 被設為和程式碼物件 *note co_qualname: 1e0d. 欄位相同的值。

 -- C 函式: *note PyObject: 311. *PyFunction_NewWithQualName (PyObject
          *code, PyObject *globals, PyObject *qualname)
     '回傳值：新的參照。' 和 *note PyFunction_New(): 4a7f. 相似，但也允
     許函式物件 *note __qualname__: 1deb. 屬性的設定，'qualname' 應為一
     個 unicode 物件或是 ‘NULL’；如為 ‘NULL’，‘__qualname__’ 屬性會被設
     為與程式碼物件 *note co_qualname: 1e0d. 欄位相同的值。

     在 3.3 版被加入.

 -- C 函式: *note PyObject: 311. *PyFunction_GetCode (PyObject *op)
     '回傳值：借用參照。' 回傳與程式碼物件相關的函式物件 'op'。

 -- C 函式: *note PyObject: 311. *PyFunction_GetGlobals (PyObject *op)
     '回傳值：借用參照。' 回傳與全域函式字典相關的函式物件 'op'。

 -- C 函式: *note PyObject: 311. *PyFunction_GetModule (PyObject *op)
     '回傳值：借用參照。' 回傳一個*note 函式物件: 295. 'op' 之 *note
     __module__: 1ded. 屬性的 *note borrowed reference: 2ef.，它可以是
     'NULL'。

     這通常是個包含模組名稱的*note 字串: 3f2.，但可以被 Python 程式設為
     任何其他物件。

 -- C 函式: *note PyObject: 311. *PyFunction_GetDefaults (PyObject *op)
     '回傳值：借用參照。' 回傳函式物件 'op' 的引數預設值，這可以是一個含
     有多個引數的 tuple（元組）或 ‘NULL’。

 -- C 函式: int PyFunction_SetDefaults (PyObject *op, PyObject
          *defaults)

     設定函式物件 'op' 的引數預設值。'defaults' 必須是 ‘Py_None’ 或一個
     tuple。

     引發 *note SystemError: 51b. 且在失敗時回傳 ‘-1’。

 -- C 函式: void PyFunction_SetVectorcall (PyFunctionObject *func,
          vectorcallfunc vectorcall)

     為一個給定的函式物件 'func' 設定 vectorcall 欄位。

     Warning: extensions using this API must preserve the behavior of
     the unaltered (default) vectorcall function!

     在 3.12 版被加入.

 -- C 函式: *note PyObject: 311. *PyFunction_GetClosure (PyObject *op)
     '回傳值：借用參照。' 回傳與函式物件 'op' 相關聯的閉包，這可以是個
     ‘NULL’ 或是一個包含 cell 物件的 tuple。

 -- C 函式: int PyFunction_SetClosure (PyObject *op, PyObject *closure)

     設定與函式物件 'op' 相關聯的閉包，'closure' 必須是 ‘Py_None’ 或是一
     個包含 cell 物件的 tuple。

     引發 *note SystemError: 51b. 且在失敗時回傳 ‘-1’。

 -- C 函式: *note PyObject: 311. *PyFunction_GetAnnotations (PyObject
          *op)
     '回傳值：借用參照。' 回傳函式物件 'op' 的標註，這可以是一個可變動的
     (mutable) 字典或 ‘NULL’。

 -- C 函式: int PyFunction_SetAnnotations (PyObject *op, PyObject
          *annotations)

     設定函式物件 'op' 的標註，'annotations' 必須是一個字典或 ‘Py_None’。

     引發 *note SystemError: 51b. 且在失敗時回傳 ‘-1’。

 -- C 函式: int PyFunction_AddWatcher (PyFunction_WatchCallback
          callback)

     Register 'callback' as a function watcher for the current
     interpreter.  Return an ID which may be passed to *note
     PyFunction_ClearWatcher(): 4a8a.  In case of error (e.g.  no more
     watcher IDs available), return ‘-1’ and set an exception.

     在 3.12 版被加入.

 -- C 函式: int PyFunction_ClearWatcher (int watcher_id)

     Clear watcher identified by 'watcher_id' previously returned from
     *note PyFunction_AddWatcher(): 4a89. for the current interpreter.
     Return ‘0’ on success, or ‘-1’ and set an exception on error (e.g.
     if the given 'watcher_id' was never registered.)

     在 3.12 版被加入.

 -- C 型別: type PyFunction_WatchEvent

     Enumeration of possible function watcher events: -
     ‘PyFunction_EVENT_CREATE’ - ‘PyFunction_EVENT_DESTROY’ -
     ‘PyFunction_EVENT_MODIFY_CODE’ - ‘PyFunction_EVENT_MODIFY_DEFAULTS’
     - ‘PyFunction_EVENT_MODIFY_KWDEFAULTS’

     在 3.12 版被加入.

 -- C 型別: typedef int (*PyFunction_WatchCallback)(*note
          PyFunction_WatchEvent: 4a8b. event, *note PyFunctionObject:
          507. *func, *note PyObject: 311. *new_value)

     Type of a function watcher callback function.

     If 'event' is ‘PyFunction_EVENT_CREATE’ or
     ‘PyFunction_EVENT_DESTROY’ then 'new_value' will be ‘NULL’.
     Otherwise, 'new_value' will hold a *note borrowed reference: 2ef.
     to the new value that is about to be stored in 'func' for the
     attribute that is being modified.

     The callback may inspect but must not modify 'func'; doing so could
     have unpredictable effects, including infinite recursion.

     If 'event' is ‘PyFunction_EVENT_CREATE’, then the callback is
     invoked after ‘func’ has been fully initialized.  Otherwise, the
     callback is invoked before the modification to 'func' takes place,
     so the prior state of 'func' can be inspected.  The runtime is
     permitted to optimize away the creation of function objects when
     possible.  In such cases no event will be emitted.  Although this
     creates the possibility of an observable difference of runtime
     behavior depending on optimization decisions, it does not change
     the semantics of the Python code being executed.

     If 'event' is ‘PyFunction_EVENT_DESTROY’, Taking a reference in the
     callback to the about-to-be-destroyed function will resurrect it,
     preventing it from being freed at this time.  When the resurrected
     object is destroyed later, any watcher callbacks active at that
     time will be called again.

     If the callback sets an exception, it must return ‘-1’; this
     exception will be printed as an unraisable exception using *note
     PyErr_WriteUnraisable(): 328.  Otherwise it should return ‘0’.

     There may already be a pending exception set on entry to the
     callback.  In this case, the callback should return ‘0’ with the
     same exception still set.  This means the callback may not call any
     other API that can set an exception unless it saves and clears the
     exception state first, and restores it before returning.

     在 3.12 版被加入.


File: python.info,  Node: 實例方法物件 Instance Method Objects,  Next: 方法物件 Method Objects,  Prev: 函式物件 Function Objects,  Up: 函式物件<2>

7.8.5.2 實例方法物件 (Instance Method Objects)
..............................................

實例方法是 *note PyCFunction: 13e2. 的包裝器 (wrapper)，也是將 *note
PyCFunction: 13e2. 繫結 (bind) 到類別物件的一種新方式。它替代了原先對
‘PyMethod_New(func, NULL, class)’ 的呼叫。

 -- C 變數: *note PyTypeObject: a48. PyInstanceMethod_Type

     *note PyTypeObject: a48. 的實例代表 Python 實例方法型別。它不會公開
     (expose) 給 Python 程式。

 -- C 函式: int PyInstanceMethod_Check (PyObject *o)

     如果 'o' 是一個實例方法物件（型別為 *note PyInstanceMethod_Type:
     4a90.）則回傳 true。參數必須不為 ‘NULL’。此函式總是會成功執行。

 -- C 函式: *note PyObject: 311. *PyInstanceMethod_New (PyObject *func)
     '回傳值：新的參照。' 回傳一個新的實例方法物件，'func' 為任意可呼叫
     物件，在實例方法被呼叫時 'func' 函式也會被呼叫。

 -- C 函式: *note PyObject: 311. *PyInstanceMethod_Function (PyObject
          *im)
     '回傳值：借用參照。' 回傳關聯到實例方法 'im' 的函式物件。

 -- C 函式: *note PyObject: 311. *PyInstanceMethod_GET_FUNCTION
          (PyObject *im)
     '回傳值：借用參照。' 巨集 (macro) 版本的 *note
     PyInstanceMethod_Function(): 4a93.，忽略了錯誤檢查。


File: python.info,  Node: 方法物件 Method Objects,  Next: Cell 物件,  Prev: 實例方法物件 Instance Method Objects,  Up: 函式物件<2>

7.8.5.3 方法物件 (Method Objects)
.................................

方法為繫結函式 (bound function) 物件。方法總是會被繫結到一個使用者定義類
別的實例。未繫結方法（繫結到一個類別的方法）已不可用。

 -- C 變數: *note PyTypeObject: a48. PyMethod_Type

     這個 *note PyTypeObject: a48. 實例代表 Python 方法型別。它作為
     ‘types.MethodType’ 公開給 Python 程式。

 -- C 函式: int PyMethod_Check (PyObject *o)

     如果 'o' 是一個方法物件（型別為 *note PyMethod_Type: 4a97.）則回傳
     true。參數必須不為 ‘NULL’。此函式總是會成功執行。

 -- C 函式: *note PyObject: 311. *PyMethod_New (PyObject *func, PyObject
          *self)
     '回傳值：新的參照。' 回傳一個新的方法物件，'func' 應為任意可呼叫物
     件，'self' 為該方法應繫結的實例。在方法被呼叫時，'func' 函式也會被
     呼叫。'self' 必須不為 ‘NULL’。

 -- C 函式: *note PyObject: 311. *PyMethod_Function (PyObject *meth)
     '回傳值：借用參照。' 回傳關聯到方法 'meth' 的函式物件。

 -- C 函式: *note PyObject: 311. *PyMethod_GET_FUNCTION (PyObject *meth)
     '回傳值：借用參照。' 巨集版本的 *note PyMethod_Function(): 4a9a.，
     忽略了錯誤檢查。

 -- C 函式: *note PyObject: 311. *PyMethod_Self (PyObject *meth)
     '回傳值：借用參照。' 回傳關聯到方法 'meth' 的實例。

 -- C 函式: *note PyObject: 311. *PyMethod_GET_SELF (PyObject *meth)
     '回傳值：借用參照。' 巨集版本的 *note PyMethod_Self(): 4a9c.，忽略
     了錯誤檢查。


File: python.info,  Node: Cell 物件,  Next: 程式碼物件,  Prev: 方法物件 Method Objects,  Up: 函式物件<2>

7.8.5.4 Cell 物件
.................

"Cell" 物件用於實現被多個作用域所參照 (reference) 的變數。對於每個這樣的
變數，都會有個 cell 物件為了儲存該值而被建立；參照該值的每個 stack frame
中的區域性變數包含外部作用域的 cell 參照，它同樣使用了該變數。存取該值時
，將使用 cell 中包含的值而不是 cell 物件本身。這種對 cell 物件的去除參照
(de-reference) 需要生成的位元組碼 (byte-code) 有支援；存取時不會自動去除
參照。cell 物件在其他地方可能不太有用。

 -- C 型別: type PyCellObject

     Cell 物件所用之 C 結構。

 -- C 變數: *note PyTypeObject: a48. PyCell_Type

     對應 cell 物件的物件型別。

 -- C 函式: int PyCell_Check (PyObject *ob)

     如果 'ob' 是一個 cell 物件則回傳真值；'ob' 必須不為 ‘NULL’。此函式
     總是會成功執行。

 -- C 函式: *note PyObject: 311. *PyCell_New (PyObject *ob)
     '回傳值：新的參照。' 建立並回傳一個包含 'ob' 的新 cell 物件。參數可
     以為 ‘NULL’。

 -- C 函式: *note PyObject: 311. *PyCell_Get (PyObject *cell)
     '回傳值：新的參照。' 回傳 cell 物件 'cell' 的內容，其可能為 ‘NULL’。
     如果 'cell' 不是一個 cell 物件，則將回傳 ‘NULL’ 並設定例外。

 -- C 函式: *note PyObject: 311. *PyCell_GET (PyObject *cell)
     '回傳值：借用參照。' 回傳 cell 物件 'cell' 的內容，但是不檢查
     'cell' 是否非 ‘NULL’ 並且為一個 cell 物件。

 -- C 函式: int PyCell_Set (PyObject *cell, PyObject *value)

     將 cell 物件 'cell' 的內容設為 'value'。這將釋放任何對 cell 物件當
     前內容的參照。'value' 可以為 ‘NULL’。'cell' 必須不為 ‘NULL’。

     在成功時回傳 ‘0’。如果 'cell' 不是一個 cell 物件，則將設定例外並回
     傳 ‘-1’。

 -- C 函式: void PyCell_SET (PyObject *cell, PyObject *value)

     將 cell 物件 'cell' 的值設為 'value'。不會調整參照計數，並且不會進
     行任何安全檢查；'cell' 必須為非 ‘NULL’ 並且為一個 cell 物件。


File: python.info,  Node: 程式碼物件,  Next: Extra information,  Prev: Cell 物件,  Up: 函式物件<2>

7.8.5.5 程式碼物件
..................

Code objects are a low-level detail of the CPython implementation.  Each
one represents a chunk of executable code that hasn't yet been bound
into a function.

 -- C 型別: type PyCodeObject

     The C structure of the objects used to describe code objects.  The
     fields of this type are subject to change at any time.

 -- C 變數: *note PyTypeObject: a48. PyCode_Type

     This is an instance of *note PyTypeObject: a48. representing the
     Python *note code object: 1b6.

 -- C 函式: int PyCode_Check (PyObject *co)

     Return true if 'co' is a *note code object: 1b6.  This function
     always succeeds.

 -- C 函式: *note Py_ssize_t: a03. PyCode_GetNumFree (PyCodeObject *co)

     Return the number of free variables in a code object.

 -- C 函式: int PyUnstable_Code_GetFirstFree (PyCodeObject *co)

          這是 不穩定 API，它可能在小版本發布中沒有任何警告地被變更。 '這是 *note 不穩定 API: 4ed.，它可能在小版本發布中沒有任何警告地被變更。': 
     Return the position of the first free variable in a code object.

     在 3.13 版的變更: Renamed from ‘PyCode_GetFirstFree’ as part of
     *note 不穩定的 C API: 4ed.  The old name is deprecated, but will
     remain available until the signature changes again.

 -- C 函式: *note PyCodeObject: 71b. *PyUnstable_Code_New (int argcount,
          int kwonlyargcount, int nlocals, int stacksize, int flags,
          PyObject *code, PyObject *consts, PyObject *names, PyObject
          *varnames, PyObject *freevars, PyObject *cellvars, PyObject
          *filename, PyObject *name, PyObject *qualname, int
          firstlineno, PyObject *linetable, PyObject *exceptiontable)

          這是 不穩定 API，它可能在小版本發布中沒有任何警告地被變更。 '這是 *note 不穩定 API: 4ed.，它可能在小版本發布中沒有任何警告地被變更。': 
     Return a new code object.  If you need a dummy code object to
     create a frame, use *note PyCode_NewEmpty(): 12e5. instead.

     Since the definition of the bytecode changes often, calling *note
     PyUnstable_Code_New(): 4aac. directly can bind you to a precise
     Python version.

     The many arguments of this function are inter-dependent in complex
     ways, meaning that subtle changes to values are likely to result in
     incorrect execution or VM crashes.  Use this function only with
     extreme care.

     在 3.11 版的變更: 新增 ‘qualname’ 和 ‘exceptiontable’ 參數。

     在 3.12 版的變更: Renamed from ‘PyCode_New’ as part of *note
     不穩定的 C API: 4ed.  The old name is deprecated, but will remain
     available until the signature changes again.

 -- C 函式: *note PyCodeObject: 71b. *PyUnstable_Code_NewWithPosOnlyArgs
          (int argcount, int posonlyargcount, int kwonlyargcount, int
          nlocals, int stacksize, int flags, PyObject *code, PyObject
          *consts, PyObject *names, PyObject *varnames, PyObject
          *freevars, PyObject *cellvars, PyObject *filename, PyObject
          *name, PyObject *qualname, int firstlineno, PyObject
          *linetable, PyObject *exceptiontable)

          這是 不穩定 API，它可能在小版本發布中沒有任何警告地被變更。 '這是 *note 不穩定 API: 4ed.，它可能在小版本發布中沒有任何警告地被變更。': 
     Similar to *note PyUnstable_Code_New(): 4aac, but with an extra
     "posonlyargcount" for positional-only arguments.  The same caveats
     that apply to ‘PyUnstable_Code_New’ also apply to this function.

     在 3.8 版被加入: as ‘PyCode_NewWithPosOnlyArgs’

     在 3.11 版的變更: 新增 ‘qualname’ 和 ‘exceptiontable’ 參數。

     在 3.12 版的變更: Renamed to ‘PyUnstable_Code_NewWithPosOnlyArgs’.
     The old name is deprecated, but will remain available until the
     signature changes again.

 -- C 函式: *note PyCodeObject: 71b. *PyCode_NewEmpty (const char
          *filename, const char *funcname, int firstlineno)
     '回傳值：新的參照。' Return a new empty code object with the
     specified filename, function name, and first line number.  The
     resulting code object will raise an ‘Exception’ if executed.

 -- C 函式: int PyCode_Addr2Line (PyCodeObject *co, int byte_offset)

     Return the line number of the instruction that occurs on or before
     ‘byte_offset’ and ends after it.  If you just need the line number
     of a frame, use *note PyFrame_GetLineNumber(): 72f. instead.

     For efficiently iterating over the line numbers in a code object,
     use the API described in PEP 626(1).

 -- C 函式: int PyCode_Addr2Location (PyObject *co, int byte_offset, int
          *start_line, int *start_column, int *end_line, int
          *end_column)

     Sets the passed ‘int’ pointers to the source code line and column
     numbers for the instruction at ‘byte_offset’.  Sets the value to
     ‘0’ when information is not available for any particular element.

     Returns ‘1’ if the function succeeds and 0 otherwise.

     在 3.11 版被加入.

 -- C 函式: *note PyObject: 311. *PyCode_GetCode (PyCodeObject *co)

     Equivalent to the Python code ‘getattr(co, 'co_code')’.  Returns a
     strong reference to a *note PyBytesObject: 736. representing the
     bytecode in a code object.  On error, ‘NULL’ is returned and an
     exception is raised.

     This ‘PyBytesObject’ may be created on-demand by the interpreter
     and does not necessarily represent the bytecode actually executed
     by CPython.  The primary use case for this function is debuggers
     and profilers.

     在 3.11 版被加入.

 -- C 函式: *note PyObject: 311. *PyCode_GetVarnames (PyCodeObject *co)

     Equivalent to the Python code ‘getattr(co, 'co_varnames')’.
     Returns a new reference to a *note PyTupleObject: 491d. containing
     the names of the local variables.  On error, ‘NULL’ is returned and
     an exception is raised.

     在 3.11 版被加入.

 -- C 函式: *note PyObject: 311. *PyCode_GetCellvars (PyCodeObject *co)

     Equivalent to the Python code ‘getattr(co, 'co_cellvars')’.
     Returns a new reference to a *note PyTupleObject: 491d. containing
     the names of the local variables that are referenced by nested
     functions.  On error, ‘NULL’ is returned and an exception is
     raised.

     在 3.11 版被加入.

 -- C 函式: *note PyObject: 311. *PyCode_GetFreevars (PyCodeObject *co)

     Equivalent to the Python code ‘getattr(co, 'co_freevars')’.
     Returns a new reference to a *note PyTupleObject: 491d. containing
     the names of the free variables.  On error, ‘NULL’ is returned and
     an exception is raised.

     在 3.11 版被加入.

 -- C 函式: int PyCode_AddWatcher (PyCode_WatchCallback callback)

     Register 'callback' as a code object watcher for the current
     interpreter.  Return an ID which may be passed to *note
     PyCode_ClearWatcher(): 50d.  In case of error (e.g.  no more
     watcher IDs available), return ‘-1’ and set an exception.

     在 3.12 版被加入.

 -- C 函式: int PyCode_ClearWatcher (int watcher_id)

     Clear watcher identified by 'watcher_id' previously returned from
     *note PyCode_AddWatcher(): 50c. for the current interpreter.
     Return ‘0’ on success, or ‘-1’ and set an exception on error (e.g.
     if the given 'watcher_id' was never registered.)

     在 3.12 版被加入.

 -- C 型別: type PyCodeEvent

     Enumeration of possible code object watcher events: -
     ‘PY_CODE_EVENT_CREATE’ - ‘PY_CODE_EVENT_DESTROY’

     在 3.12 版被加入.

 -- C 型別: typedef int (*PyCode_WatchCallback)(*note PyCodeEvent: 4aae.
          event, *note PyCodeObject: 71b. *co)

     Type of a code object watcher callback function.

     If 'event' is ‘PY_CODE_EVENT_CREATE’, then the callback is invoked
     after ‘co’ has been fully initialized.  Otherwise, the callback is
     invoked before the destruction of 'co' takes place, so the prior
     state of 'co' can be inspected.

     If 'event' is ‘PY_CODE_EVENT_DESTROY’, taking a reference in the
     callback to the about-to-be-destroyed code object will resurrect it
     and prevent it from being freed at this time.  When the resurrected
     object is destroyed later, any watcher callbacks active at that
     time will be called again.

     Users of this API should not rely on internal runtime
     implementation details.  Such details may include, but are not
     limited to, the exact order and timing of creation and destruction
     of code objects.  While changes in these details may result in
     differences observable by watchers (including whether a callback is
     invoked or not), it does not change the semantics of the Python
     code being executed.

     If the callback sets an exception, it must return ‘-1’; this
     exception will be printed as an unraisable exception using *note
     PyErr_WriteUnraisable(): 328.  Otherwise it should return ‘0’.

     There may already be a pending exception set on entry to the
     callback.  In this case, the callback should return ‘0’ with the
     same exception still set.  This means the callback may not call any
     other API that can set an exception unless it saves and clears the
     exception state first, and restores it before returning.

     在 3.12 版被加入.

   ---------- Footnotes ----------

   (1) 
https://peps.python.org/pep-0626/#out-of-process-debuggers-and-profilers


File: python.info,  Node: Extra information,  Prev: 程式碼物件,  Up: 函式物件<2>

7.8.5.6 Extra information
.........................

To support low-level extensions to frame evaluation, such as external
just-in-time compilers, it is possible to attach arbitrary extra data to
code objects.

These functions are part of the unstable C API tier: this functionality
is a CPython implementation detail, and the API may change without
deprecation warnings.

 -- C 函式: *note Py_ssize_t: a03. PyUnstable_Eval_RequestCodeExtraIndex
          (freefunc free)

          這是 不穩定 API，它可能在小版本發布中沒有任何警告地被變更。 '這是 *note 不穩定 API: 4ed.，它可能在小版本發布中沒有任何警告地被變更。': 
     Return a new an opaque index value used to adding data to code
     objects.

     You generally call this function once (per interpreter) and use the
     result with ‘PyCode_GetExtra’ and ‘PyCode_SetExtra’ to manipulate
     data on individual code objects.

     If 'free' is not ‘NULL’: when a code object is deallocated, 'free'
     will be called on non-‘NULL’ data stored under the new index.  Use
     *note Py_DecRef(): 48b4. when storing *note PyObject: 311.

     在 3.6 版被加入: as ‘_PyEval_RequestCodeExtraIndex’

     在 3.12 版的變更: Renamed to
     ‘PyUnstable_Eval_RequestCodeExtraIndex’.  The old private name is
     deprecated, but will be available until the API changes.

 -- C 函式: int PyUnstable_Code_GetExtra (PyObject *code, Py_ssize_t
          index, void **extra)

          這是 不穩定 API，它可能在小版本發布中沒有任何警告地被變更。 '這是 *note 不穩定 API: 4ed.，它可能在小版本發布中沒有任何警告地被變更。': 
     Set 'extra' to the extra data stored under the given index.  Return
     0 on success.  Set an exception and return -1 on failure.

     If no data was set under the index, set 'extra' to ‘NULL’ and
     return 0 without setting an exception.

     在 3.6 版被加入: as ‘_PyCode_GetExtra’

     在 3.12 版的變更: Renamed to ‘PyUnstable_Code_GetExtra’.  The old
     private name is deprecated, but will be available until the API
     changes.

 -- C 函式: int PyUnstable_Code_SetExtra (PyObject *code, Py_ssize_t
          index, void *extra)

          這是 不穩定 API，它可能在小版本發布中沒有任何警告地被變更。 '這是 *note 不穩定 API: 4ed.，它可能在小版本發布中沒有任何警告地被變更。': 
     Set the extra data stored under the given index to 'extra'.  Return
     0 on success.  Set an exception and return -1 on failure.

     在 3.6 版被加入: as ‘_PyCode_SetExtra’

     在 3.12 版的變更: Renamed to ‘PyUnstable_Code_SetExtra’.  The old
     private name is deprecated, but will be available until the API
     changes.


File: python.info,  Node: 其他物件<2>,  Prev: 函式物件<2>,  Up: 具體物件層

7.8.6 其他物件
--------------

* Menu:

* 檔案物件 (File Objects): 檔案物件 File Objects.
* 模組物件::
* 疊代器（Iterator）物件::
* Descriptor（描述器）物件::
* 切片物件::
* MemoryView 物件::
* 弱參照物件: 弱參照物件<2>.
* Capsules: Capsules<2>.
* Frame 物件::
* 產生器 (Generator) 物件: 產生器 Generator 物件.
* Coroutine（協程）物件::
* 情境變數物件::
* DateTime 物件::
* 型別提示物件::


File: python.info,  Node: 檔案物件 File Objects,  Next: 模組物件,  Up: 其他物件<2>

7.8.6.1 檔案物件 (File Objects)
...............................

這些 API 是用於內建檔案物件的 Python 2 C API 的最小模擬 (minimal
emulation)，它過去依賴於 C 標準函式庫對於緩衝 I/O (FILE*) 的支援。在
Python 3 中，檔案和串流使用新的 *note io: 73. 模組，它在操作系統的低階無
緩衝 I/O 上定義了多個層級。下面描述的函式是這些新 API 的便捷 C 包裝器，
主要用於直譯器中的內部錯誤報告；建議第三方程式碼改為存取 *note io: 73.
API。

 -- C 函式: *note PyObject: 311. *PyFile_FromFd (int fd, const char
          *name, const char *mode, int buffering, const char *encoding,
          const char *errors, const char *newline, int closefd)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a
     Python file object from the file descriptor of an already opened
     file 'fd'.  The arguments 'name', 'encoding', 'errors' and
     'newline' can be ‘NULL’ to use the defaults; 'buffering' can be
     '-1' to use the default.  'name' is ignored and kept for backward
     compatibility.  Return ‘NULL’ on failure.  For a more comprehensive
     description of the arguments, please refer to the *note io.open():
     4c1. function documentation.

          警告: 由於 Python 串流有自己的緩衝層，將它們與操作系統層級檔案
          描述器混合使用會產生各種問題（例如資料的排序不符合預期）。

     在 3.2 版的變更: 忽略 'name' 屬性。

 -- C 函式: int PyObject_AsFileDescriptor (PyObject *p)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  回傳與 'p' 關聯的檔案描述器作
     為 int。如果物件是整數，則回傳其值。如果不是整數，則呼叫物件的
     *note fileno(): 2732. 方法（如果存在）；該方法必須回傳一個整數，它
     作為檔案描述器值回傳。設定例外並在失敗時回傳 ‘-1’。

 -- C 函式: *note PyObject: 311. *PyFile_GetLine (PyObject *p, int n)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

     Equivalent to ‘p.readline([n])’, this function reads one line from
     the object 'p'.  'p' may be a file object or any object with a
     *note readline(): 12bd. method.  If 'n' is ‘0’, exactly one line is
     read, regardless of the length of the line.  If 'n' is greater than
     ‘0’, no more than 'n' bytes will be read from the file; a partial
     line can be returned.  In both cases, an empty string is returned
     if the end of the file is reached immediately.  If 'n' is less than
     ‘0’, however, one line is read regardless of length, but *note
     EOFError: 126c. is raised if the end of the file is reached
     immediately.

 -- C 函式: int PyFile_SetOpenCodeHook (Py_OpenCodeHookFunction handler)

     覆蓋 *note io.open_code(): 1625. 的正常行為以透過提供的處理程式
     (handler) 傳遞其參數。

     The 'handler' is a function of type:

      -- C 型別: typedef *note PyObject: 311.
               *(*Py_OpenCodeHookFunction)(*note PyObject: 311.*, void*)

          Equivalent of *note PyObject: 311. *(*)(*note PyObject: 311.
          *path, void *userData), where 'path' is guaranteed to be *note
          PyUnicodeObject: 738.

     'userData' 指標被傳遞到掛鉤函式 (hook function) 中。由於可能會從不
     同的執行環境 (runtime) 呼叫掛鉤函式，因此該指標不應直接指向 Python
     狀態。

     由於此掛鉤函式是在導入期間有意使用的，因此請避免在其執行期間導入新
     模組，除非它們已知有被凍結或在 ‘sys.modules’ 中可用。

     Once a hook has been set, it cannot be removed or replaced, and
     later calls to *note PyFile_SetOpenCodeHook(): 1627. will fail.  On
     failure, the function returns -1 and sets an exception if the
     interpreter has been initialized.

     在 *note Py_Initialize(): 851. 之前呼叫此函式是安全的。

     不帶引數地引發一個*note 稽核事件 (auditing event): 17bd.
     ‘setopencodehook’。

     在 3.8 版被加入.

 -- C 函式: int PyFile_WriteObject (PyObject *obj, PyObject *p, int
          flags)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     將物件 'obj' 寫入檔案物件 'p'。 'flags' 唯一支援的旗標是 *note
     Py_PRINT_RAW: 4966.；如果有給定，則寫入物件的 *note str(): 3f2. 而
     不是 *note repr(): 7a1.。在成功回傳 ‘0’ 或在失敗回傳 ‘-1’；將設定適
     當的例外。

 -- C 函式: int PyFile_WriteString (const char *s, PyObject *p)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  寫入字串 's' 到 檔案物件 'p'。
     當成功時回傳 0，而當失敗時回傳 -1，並會設定合適的例外狀況。


File: python.info,  Node: 模組物件,  Next: 疊代器（Iterator）物件,  Prev: 檔案物件 File Objects,  Up: 其他物件<2>

7.8.6.2 模組物件
................

 -- C 變數: *note PyTypeObject: a48. PyModule_Type
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     This instance of *note PyTypeObject: a48. represents the Python
     module type.  This is exposed to Python programs as
     ‘types.ModuleType’.

 -- C 函式: int PyModule_Check (PyObject *p)

     Return true if 'p' is a module object, or a subtype of a module
     object.  This function always succeeds.

 -- C 函式: int PyModule_CheckExact (PyObject *p)

     Return true if 'p' is a module object, but not a subtype of *note
     PyModule_Type: 4810.  This function always succeeds.

 -- C 函式: *note PyObject: 311. *PyModule_NewObject (PyObject *name)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本
     開始.'

     Return a new module object with the *note __name__: 1316. attribute
     set to 'name'.  The module's *note __name__: 1316, ‘__doc__’, *note
     __package__: fc0, and *note __loader__: fc1. attributes are filled
     in (all but *note __name__: 1316. are set to ‘None’); the caller is
     responsible for providing a *note __file__: 1e02. attribute.

     在失敗時回傳 ‘NULL’ 並設定例外。

     在 3.3 版被加入.

     在 3.4 版的變更: *note __package__: fc0. 和 *note __loader__: fc1.
     被設為 ‘None’。

 -- C 函式: *note PyObject: 311. *PyModule_New (const char *name)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Similar to
     *note PyModule_NewObject(): 480e, but the name is a UTF-8 encoded
     string instead of a Unicode object.

 -- C 函式: *note PyObject: 311. *PyModule_GetDict (PyObject *module)
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

     Return the dictionary object that implements 'module"s namespace;
     this object is the same as the *note __dict__: c04. attribute of
     the module object.  If 'module' is not a module object (or a
     subtype of a module object), *note SystemError: 51b. is raised and
     ‘NULL’ is returned.

     It is recommended extensions use other ‘PyModule_*’ and
     ‘PyObject_*’ functions rather than directly manipulate a module's
     *note __dict__: c04.

 -- C 函式: *note PyObject: 311. *PyModule_GetNameObject (PyObject
          *module)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本
     開始.'

     Return 'module"s *note __name__: 1316. value.  If the module does
     not provide one, or if it is not a string, *note SystemError: 51b.
     is raised and ‘NULL’ is returned.

     在 3.3 版被加入.

 -- C 函式: const char *PyModule_GetName (PyObject *module)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Similar to *note
     PyModule_GetNameObject(): 480c. but return the name encoded to
     ‘'utf-8'’.

 -- C 函式: void *PyModule_GetState (PyObject *module)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the "state" of the
     module, that is, a pointer to the block of memory allocated at
     module creation time, or ‘NULL’.  See *note PyModuleDef.m_size:
     923.

 -- C 函式: *note PyModuleDef: 921. *PyModule_GetDef (PyObject *module)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a pointer to the *note
     PyModuleDef: 921. struct from which the module was created, or
     ‘NULL’ if the module wasn't created from a definition.

 -- C 函式: *note PyObject: 311. *PyModule_GetFilenameObject (PyObject
          *module)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

     Return the name of the file from which 'module' was loaded using
     'module"s *note __file__: 1e02. attribute.  If this is not defined,
     or if it is not a unicode string, raise *note SystemError: 51b. and
     return ‘NULL’; otherwise return a reference to a Unicode object.

     在 3.2 版被加入.

 -- C 函式: const char *PyModule_GetFilename (PyObject *module)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Similar to *note
     PyModule_GetFilenameObject(): 3c1. but return the filename encoded
     to 'utf-8'.

     在 3.2 版之後被棄用: *note PyModule_GetFilename(): 3c0. raises
     *note UnicodeEncodeError: 61d. on unencodable filenames, use *note
     PyModule_GetFilenameObject(): 3c1. instead.

* Menu:

* 初始化 C 模組::
* 模組查找::


File: python.info,  Node: 初始化 C 模組,  Next: 模組查找,  Up: 模組物件

7.8.6.3 初始化 C 模組
.....................

Modules objects are usually created from extension modules (shared
libraries which export an initialization function), or compiled-in
modules (where the initialization function is added using *note
PyImport_AppendInittab(): 16a6.).  See *note 建立 C 與 C++ 擴充套件:
46dd. or *note Extending Embedded Python: 474a. for details.

The initialization function can either pass a module definition instance
to *note PyModule_Create(): 46da, and return the resulting module
object, or request "multi-phase initialization" by returning the
definition struct itself.

 -- C 型別: type PyModuleDef
     ' 為 *note 穩定 ABI 的一部分: 4f9. （包含所有成員）.'  The module
     definition struct, which holds all information needed to create a
     module object.  There is usually only one statically initialized
     variable of this type for each module.

      -- C 成員函數: PyModuleDef_Base m_base

          Always initialize this member to ‘PyModuleDef_HEAD_INIT’.

      -- C 成員函數: const char *m_name

          Name for the new module.

      -- C 成員函數: const char *m_doc

          Docstring for the module; usually a docstring variable created
          with *note PyDoc_STRVAR: 1876. is used.

      -- C 成員函數: *note Py_ssize_t: a03. m_size

          Module state may be kept in a per-module memory area that can
          be retrieved with *note PyModule_GetState(): 924, rather than
          in static globals.  This makes modules safe for use in
          multiple sub-interpreters.

          This memory area is allocated based on 'm_size' on module
          creation, and freed when the module object is deallocated,
          after the *note m_free: 920. function has been called, if
          present.

          Setting ‘m_size’ to ‘-1’ means that the module does not
          support sub-interpreters, because it has global state.

          Setting it to a non-negative value means that the module can
          be re-initialized and specifies the additional amount of
          memory it requires for its state.  Non-negative ‘m_size’ is
          required for multi-phase initialization.

          更多詳情請見 PEP 3121(1)。

      -- C 成員函數: *note PyMethodDef: 1446. *m_methods

          A pointer to a table of module-level functions, described by
          *note PyMethodDef: 1446. values.  Can be ‘NULL’ if no
          functions are present.

      -- C 成員函數: *note PyModuleDef_Slot: 4ac4. *m_slots

          An array of slot definitions for multi-phase initialization,
          terminated by a ‘{0, NULL}’ entry.  When using single-phase
          initialization, 'm_slots' must be ‘NULL’.

          在 3.5 版的變更: Prior to version 3.5, this member was always
          set to ‘NULL’, and was defined as:

                -- C 成員函數: *note inquiry: 48cd. m_reload

      -- C 成員函數: *note traverseproc: 48dc. m_traverse

          A traversal function to call during GC traversal of the module
          object, or ‘NULL’ if not needed.

          This function is not called if the module state was requested
          but is not allocated yet.  This is the case immediately after
          the module is created and before the module is executed (*note
          Py_mod_exec: 922. function).  More precisely, this function is
          not called if *note m_size: 923. is greater than 0 and the
          module state (as returned by *note PyModule_GetState(): 924.)
          is ‘NULL’.

          在 3.9 版的變更: No longer called before the module state is
          allocated.

      -- C 成員函數: *note inquiry: 48cd. m_clear

          A clear function to call during GC clearing of the module
          object, or ‘NULL’ if not needed.

          This function is not called if the module state was requested
          but is not allocated yet.  This is the case immediately after
          the module is created and before the module is executed (*note
          Py_mod_exec: 922. function).  More precisely, this function is
          not called if *note m_size: 923. is greater than 0 and the
          module state (as returned by *note PyModule_GetState(): 924.)
          is ‘NULL’.

          Like *note PyTypeObject.tp_clear: 4717, this function is not
          'always' called before a module is deallocated.  For example,
          when reference counting is enough to determine that an object
          is no longer used, the cyclic garbage collector is not
          involved and *note m_free: 920. is called directly.

          在 3.9 版的變更: No longer called before the module state is
          allocated.

      -- C 成員函數: *note freefunc: 4ac6. m_free

          A function to call during deallocation of the module object,
          or ‘NULL’ if not needed.

          This function is not called if the module state was requested
          but is not allocated yet.  This is the case immediately after
          the module is created and before the module is executed (*note
          Py_mod_exec: 922. function).  More precisely, this function is
          not called if *note m_size: 923. is greater than 0 and the
          module state (as returned by *note PyModule_GetState(): 924.)
          is ‘NULL’.

          在 3.9 版的變更: No longer called before the module state is
          allocated.

* Menu:

* Single-phase initialization::
* Multi-phase initialization::
* Low-level module creation functions::
* 支援的函式::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3121/


File: python.info,  Node: Single-phase initialization,  Next: Multi-phase initialization,  Up: 初始化 C 模組

7.8.6.4 Single-phase initialization
...................................

The module initialization function may create and return the module
object directly.  This is referred to as "single-phase initialization",
and uses one of the following two module creation functions:

 -- C 函式: *note PyObject: 311. *PyModule_Create (PyModuleDef *def)
     '回傳值：新的參照。' Create a new module object, given the
     definition in 'def'.  This behaves like *note PyModule_Create2():
     4808. with 'module_api_version' set to ‘PYTHON_API_VERSION’.

 -- C 函式: *note PyObject: 311. *PyModule_Create2 (PyModuleDef *def,
          int module_api_version)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a
     new module object, given the definition in 'def', assuming the API
     version 'module_api_version'.  If that version does not match the
     version of the running interpreter, a *note RuntimeWarning: 1a3. is
     emitted.

     在失敗時回傳 ‘NULL’ 並設定例外。

          備註: Most uses of this function should be using *note
          PyModule_Create(): 46da. instead; only use this if you are
          sure you need it.

Before it is returned from in the initialization function, the resulting
module object is typically populated using functions like *note
PyModule_AddObjectRef(): 308.


File: python.info,  Node: Multi-phase initialization,  Next: Low-level module creation functions,  Prev: Single-phase initialization,  Up: 初始化 C 模組

7.8.6.5 Multi-phase initialization
..................................

An alternate way to specify extensions is to request "multi-phase
initialization".  Extension modules created this way behave more like
Python modules: the initialization is split between the 'creation
phase', when the module object is created, and the 'execution phase',
when it is populated.  The distinction is similar to the ‘__new__()’ and
‘__init__()’ methods of classes.

Unlike modules created using single-phase initialization, these modules
are not singletons: if the 'sys.modules' entry is removed and the module
is re-imported, a new module object is created, and the old module is
subject to normal garbage collection - as with Python modules.  By
default, multiple modules created from the same definition should be
independent: changes to one should not affect the others.  This means
that all state should be specific to the module object (using e.g.
using *note PyModule_GetState(): 924.), or its contents (such as the
module's *note __dict__: c04. or individual classes created with *note
PyType_FromSpec(): 523.).

All modules created using multi-phase initialization are expected to
support *note sub-interpreters: 52d.  Making sure multiple modules are
independent is typically enough to achieve this.

To request multi-phase initialization, the initialization function
(PyInit_modulename) returns a *note PyModuleDef: 921. instance with
non-empty *note m_slots: 4ac3.  Before it is returned, the ‘PyModuleDef’
instance must be initialized with the following function:

 -- C 函式: *note PyObject: 311. *PyModuleDef_Init (PyModuleDef *def)
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.5 版本
     開始.'  Ensures a module definition is a properly initialized
     Python object that correctly reports its type and reference count.

     Returns 'def' cast to ‘PyObject*’, or ‘NULL’ if an error occurred.

     在 3.5 版被加入.

The 'm_slots' member of the module definition must point to an array of
‘PyModuleDef_Slot’ structures:

 -- C 型別: type PyModuleDef_Slot

      -- C 成員函數: int slot

          A slot ID, chosen from the available values explained below.

      -- C 成員函數: void *value

          Value of the slot, whose meaning depends on the slot ID.

     在 3.5 版被加入.

The 'm_slots' array must be terminated by a slot with id 0.

The available slot types are:

 -- C 巨集: Py_mod_create

     Specifies a function that is called to create the module object
     itself.  The 'value' pointer of this slot must point to a function
     of the signature:

      -- C 函式: *note PyObject: 311. *create_module (PyObject *spec,
               PyModuleDef *def)

     The function receives a *note ModuleSpec: 1d5a. instance, as
     defined in PEP 451(1), and the module definition.  It should return
     a new module object, or set an error and return ‘NULL’.

     This function should be kept minimal.  In particular, it should not
     call arbitrary Python code, as trying to import the same module
     again may result in an infinite loop.

     Multiple ‘Py_mod_create’ slots may not be specified in one module
     definition.

     If ‘Py_mod_create’ is not specified, the import machinery will
     create a normal module object using *note PyModule_New(): 480d.
     The name is taken from 'spec', not the definition, to allow
     extension modules to dynamically adjust to their place in the
     module hierarchy and be imported under different names through
     symlinks, all while sharing a single module definition.

     There is no requirement for the returned object to be an instance
     of *note PyModule_Type: 4810.  Any type can be used, as long as it
     supports setting and getting import-related attributes.  However,
     only ‘PyModule_Type’ instances may be returned if the ‘PyModuleDef’
     has non-‘NULL’ ‘m_traverse’, ‘m_clear’, ‘m_free’; non-zero
     ‘m_size’; or slots other than ‘Py_mod_create’.

 -- C 巨集: Py_mod_exec

     Specifies a function that is called to 'execute' the module.  This
     is equivalent to executing the code of a Python module: typically,
     this function adds classes and constants to the module.  The
     signature of the function is:

      -- C 函式: int exec_module (PyObject *module)

     If multiple ‘Py_mod_exec’ slots are specified, they are processed
     in the order they appear in the 'm_slots' array.

 -- C 巨集: Py_mod_multiple_interpreters

     Specifies one of the following values:

      -- C 巨集: Py_MOD_MULTIPLE_INTERPRETERS_NOT_SUPPORTED

          The module does not support being imported in subinterpreters.

      -- C 巨集: Py_MOD_MULTIPLE_INTERPRETERS_SUPPORTED

          The module supports being imported in subinterpreters, but
          only when they share the main interpreter's GIL. (See *note
          隔離擴充模組: 4ad1.)

      -- C 巨集: Py_MOD_PER_INTERPRETER_GIL_SUPPORTED

          The module supports being imported in subinterpreters, even
          when they have their own GIL. (See *note 隔離擴充模組: 4ad1.)

     This slot determines whether or not importing this module in a
     subinterpreter will fail.

     Multiple ‘Py_mod_multiple_interpreters’ slots may not be specified
     in one module definition.

     If ‘Py_mod_multiple_interpreters’ is not specified, the import
     machinery defaults to ‘Py_MOD_MULTIPLE_INTERPRETERS_NOT_SUPPORTED’.

     在 3.12 版被加入.

 -- C 巨集: Py_mod_gil

     Specifies one of the following values:

      -- C 巨集: Py_MOD_GIL_USED

          The module depends on the presence of the global interpreter
          lock (GIL), and may access global state without
          synchronization.

      -- C 巨集: Py_MOD_GIL_NOT_USED

          The module is safe to run without an active GIL.

     This slot is ignored by Python builds not configured with *note
     -disable-gil: 158.  Otherwise, it determines whether or not
     importing this module will cause the GIL to be automatically
     enabled.  See *note Free-threaded CPython: 125. for more detail.

     Multiple ‘Py_mod_gil’ slots may not be specified in one module
     definition.

     If ‘Py_mod_gil’ is not specified, the import machinery defaults to
     ‘Py_MOD_GIL_USED’.

     在 3.13 版被加入.

See PEP 489(2) for more details on multi-phase initialization.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0451/

   (2) https://peps.python.org/pep-0489/


File: python.info,  Node: Low-level module creation functions,  Next: 支援的函式,  Prev: Multi-phase initialization,  Up: 初始化 C 模組

7.8.6.6 Low-level module creation functions
...........................................

The following functions are called under the hood when using multi-phase
initialization.  They can be used directly, for example when creating
module objects dynamically.  Note that both ‘PyModule_FromDefAndSpec’
and ‘PyModule_ExecDef’ must be called to fully initialize a module.

 -- C 函式: *note PyObject: 311. *PyModule_FromDefAndSpec (PyModuleDef
          *def, PyObject *spec)
     '回傳值：新的參照。' Create a new module object, given the
     definition in 'def' and the ModuleSpec 'spec'.  This behaves like
     *note PyModule_FromDefAndSpec2(): e55. with 'module_api_version'
     set to ‘PYTHON_API_VERSION’.

     在 3.5 版被加入.

 -- C 函式: *note PyObject: 311. *PyModule_FromDefAndSpec2 (PyModuleDef
          *def, PyObject *spec, int module_api_version)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本
     開始.'  Create a new module object, given the definition in 'def'
     and the ModuleSpec 'spec', assuming the API version
     'module_api_version'.  If that version does not match the version
     of the running interpreter, a *note RuntimeWarning: 1a3. is
     emitted.

     在失敗時回傳 ‘NULL’ 並設定例外。

          備註: Most uses of this function should be using *note
          PyModule_FromDefAndSpec(): e54. instead; only use this if you
          are sure you need it.

     在 3.5 版被加入.

 -- C 函式: int PyModule_ExecDef (PyObject *module, PyModuleDef *def)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Process any
     execution slots (*note Py_mod_exec: 922.) given in 'def'.

     在 3.5 版被加入.

 -- C 函式: int PyModule_SetDocString (PyObject *module, const char
          *docstring)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Set the
     docstring for 'module' to 'docstring'.  This function is called
     automatically when creating a module from ‘PyModuleDef’, using
     either ‘PyModule_Create’ or ‘PyModule_FromDefAndSpec’.

     在 3.5 版被加入.

 -- C 函式: int PyModule_AddFunctions (PyObject *module, PyMethodDef
          *functions)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Add the
     functions from the ‘NULL’ terminated 'functions' array to 'module'.
     Refer to the *note PyMethodDef: 1446. documentation for details on
     individual entries (due to the lack of a shared module namespace,
     module level "functions" implemented in C typically receive the
     module as their first parameter, making them similar to instance
     methods on Python classes).  This function is called automatically
     when creating a module from ‘PyModuleDef’, using either
     ‘PyModule_Create’ or ‘PyModule_FromDefAndSpec’.

     在 3.5 版被加入.


File: python.info,  Node: 支援的函式,  Prev: Low-level module creation functions,  Up: 初始化 C 模組

7.8.6.7 支援的函式
..................

The module initialization function (if using single phase
initialization) or a function called from a module execution slot (if
using multi-phase initialization), can use the following functions to
help initialize the module state:

 -- C 函式: int PyModule_AddObjectRef (PyObject *module, const char
          *name, PyObject *value)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本開始.'  Add an
     object to 'module' as 'name'.  This is a convenience function which
     can be used from the module's initialization function.

     On success, return ‘0’.  On error, raise an exception and return
     ‘-1’.

     Return ‘-1’ if 'value' is ‘NULL’.  It must be called with an
     exception raised in this case.

     用法範例：

          static int
          add_spam(PyObject *module, int value)
          {
              PyObject *obj = PyLong_FromLong(value);
              if (obj == NULL) {
                  return -1;
              }
              int res = PyModule_AddObjectRef(module, "spam", obj);
              Py_DECREF(obj);
              return res;
           }

     The example can also be written without checking explicitly if
     'obj' is ‘NULL’:

          static int
          add_spam(PyObject *module, int value)
          {
              PyObject *obj = PyLong_FromLong(value);
              int res = PyModule_AddObjectRef(module, "spam", obj);
              Py_XDECREF(obj);
              return res;
           }

     Note that ‘Py_XDECREF()’ should be used instead of ‘Py_DECREF()’ in
     this case, since 'obj' can be ‘NULL’.

     The number of different 'name' strings passed to this function
     should be kept small, usually by only using statically allocated
     strings as 'name'.  For names that aren't known at compile time,
     prefer calling *note PyUnicode_FromString(): 4748. and *note
     PyObject_SetAttr(): 4842. directly.  For more details, see *note
     PyUnicode_InternFromString(): 14f2, which may be used internally to
     create a key object.

     在 3.10 版被加入.

 -- C 函式: int PyModule_Add (PyObject *module, const char *name,
          PyObject *value)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Similar to
     *note PyModule_AddObjectRef(): 308, but "steals" a reference to
     'value'.  It can be called with a result of function that returns a
     new reference without bothering to check its result or even saving
     it to a variable.

     用法範例：

          if (PyModule_Add(module, "spam", PyBytes_FromString(value)) < 0) {
              goto error;
          }

     在 3.13 版被加入.

 -- C 函式: int PyModule_AddObject (PyObject *module, const char *name,
          PyObject *value)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Similar to *note
     PyModule_AddObjectRef(): 308, but steals a reference to 'value' on
     success (if it returns ‘0’).

     The new *note PyModule_Add(): 307. or *note
     PyModule_AddObjectRef(): 308. functions are recommended, since it
     is easy to introduce reference leaks by misusing the *note
     PyModule_AddObject(): 309. function.

          備註: Unlike other functions that steal references,
          ‘PyModule_AddObject()’ only releases the reference to 'value'
          'on success'.

          This means that its return value must be checked, and calling
          code must *note Py_XDECREF(): 733. 'value' manually on error.

     用法範例：

          PyObject *obj = PyBytes_FromString(value);
          if (PyModule_AddObject(module, "spam", obj) < 0) {
              // If 'obj' is not NULL and PyModule_AddObject() failed,
              // 'obj' strong reference must be deleted with Py_XDECREF().
              // If 'obj' is NULL, Py_XDECREF() does nothing.
              Py_XDECREF(obj);
              goto error;
          }
          // PyModule_AddObject() stole a reference to obj:
          // Py_XDECREF(obj) is not needed here.

     在 3.13 版之後被棄用: *note PyModule_AddObject(): 309. is *note
     soft deprecated: 1ee.

 -- C 函式: int PyModule_AddIntConstant (PyObject *module, const char
          *name, long value)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Add an integer constant to
     'module' as 'name'.  This convenience function can be used from the
     module's initialization function.  Return ‘-1’ with an exception
     set on error, ‘0’ on success.

     This is a convenience function that calls *note PyLong_FromLong():
     173e. and *note PyModule_AddObjectRef(): 308.; see their
     documentation for details.

 -- C 函式: int PyModule_AddStringConstant (PyObject *module, const char
          *name, const char *value)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Add a string constant to
     'module' as 'name'.  This convenience function can be used from the
     module's initialization function.  The string 'value' must be
     ‘NULL’-terminated.  Return ‘-1’ with an exception set on error, ‘0’
     on success.

     This is a convenience function that calls *note
     PyUnicode_InternFromString(): 14f2. and *note
     PyModule_AddObjectRef(): 308.; see their documentation for details.

 -- C 巨集: PyModule_AddIntMacro (module, macro)

     Add an int constant to 'module'.  The name and the value are taken
     from 'macro'.  For example ‘PyModule_AddIntMacro(module, AF_INET)’
     adds the int constant 'AF_INET' with the value of 'AF_INET' to
     'module'.  Return ‘-1’ with an exception set on error, ‘0’ on
     success.

 -- C 巨集: PyModule_AddStringMacro (module, macro)

     Add a string constant to 'module'.

 -- C 函式: int PyModule_AddType (PyObject *module, PyTypeObject *type)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本開始.'  Add a type
     object to 'module'.  The type object is finalized by calling
     internally *note PyType_Ready(): 722.  The name of the type object
     is taken from the last component of *note tp_name: 17f5. after dot.
     Return ‘-1’ with an exception set on error, ‘0’ on success.

     在 3.9 版被加入.

 -- C 函式: int PyUnstable_Module_SetGIL (PyObject *module, void *gil)

          這是 不穩定 API，它可能在小版本發布中沒有任何警告地被變更。 '這是 *note 不穩定 API: 4ed.，它可能在小版本發布中沒有任何警告地被變更。': 
     Indicate that 'module' does or does not support running without the
     global interpreter lock (GIL), using one of the values from *note
     Py_mod_gil: 13d.  It must be called during 'module"s initialization
     function.  If this function is not called during module
     initialization, the import machinery assumes the module does not
     support running without the GIL. This function is only available in
     Python builds configured with *note -disable-gil: 158.  Return ‘-1’
     with an exception set on error, ‘0’ on success.

     在 3.13 版被加入.


File: python.info,  Node: 模組查找,  Prev: 初始化 C 模組,  Up: 模組物件

7.8.6.8 模組查找
................

Single-phase initialization creates singleton modules that can be looked
up in the context of the current interpreter.  This allows the module
object to be retrieved later with only a reference to the module
definition.

These functions will not work on modules created using multi-phase
initialization, since multiple such modules can be created from a single
definition.

 -- C 函式: *note PyObject: 311. *PyState_FindModule (PyModuleDef *def)
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Returns
     the module object that was created from 'def' for the current
     interpreter.  This method requires that the module object has been
     attached to the interpreter state with *note PyState_AddModule():
     485d. beforehand.  In case the corresponding module object is not
     found or has not been attached to the interpreter state yet, it
     returns ‘NULL’.

 -- C 函式: int PyState_AddModule (PyObject *module, PyModuleDef *def)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.3 版本開始.'  Attaches the
     module object passed to the function to the interpreter state.
     This allows the module object to be accessible via *note
     PyState_FindModule(): 485e.

     Only effective on modules created using single-phase
     initialization.

     Python calls ‘PyState_AddModule’ automatically after importing a
     module, so it is unnecessary (but harmless) to call it from module
     initialization code.  An explicit call is needed only if the
     module's own init code subsequently calls ‘PyState_FindModule’.
     The function is mainly intended for implementing alternative import
     mechanisms (either by calling it directly, or by referring to its
     implementation for details of the required state updates).

     The caller must hold the GIL.

     成功時回傳 ‘0’，在失敗時回傳 ‘-1’ 並設定例外。

     在 3.3 版被加入.

 -- C 函式: int PyState_RemoveModule (PyModuleDef *def)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.3 版本開始.'  Removes the
     module object created from 'def' from the interpreter state.
     Return ‘-1’ with an exception set on error, ‘0’ on success.

     The caller must hold the GIL.

     在 3.3 版被加入.


File: python.info,  Node: 疊代器（Iterator）物件,  Next: Descriptor（描述器）物件,  Prev: 模組物件,  Up: 其他物件<2>

7.8.6.9 疊代器（Iterator）物件
..............................

Python 提供了兩種通用的疊代器 (iterator) 物件，第一種是序列疊代器
(sequence iterator)，適用於支援 *note __getitem__(): 266. 方法的任意序列
，第二種是與可呼叫 (callable) 物件和哨兵值 (sentinel value) 一起使用，會
呼叫序列中的每個可呼叫物件，當回傳哨兵值時就結束疊代。

 -- C 變數: *note PyTypeObject: a48. PySeqIter_Type
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  此型別物件用於由 *note
     PySeqIter_New(): 4846. 所回傳的疊代器物件以及用於內建序列型別的內建
     函式 *note iter(): 77b. 的單引數形式。

 -- C 函式: int PySeqIter_Check (PyObject *op)

     Return true if the type of 'op' is *note PySeqIter_Type: 4847.
     This function always succeeds.

 -- C 函式: *note PyObject: 311. *PySeqIter_New (PyObject *seq)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return an
     iterator that works with a general sequence object, 'seq'.  The
     iteration ends when the sequence raises *note IndexError: 14a3. for
     the subscripting operation.

 -- C 變數: *note PyTypeObject: a48. PyCallIter_Type
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Type object for iterator
     objects returned by *note PyCallIter_New(): 4792. and the
     two-argument form of the *note iter(): 77b. built-in function.

 -- C 函式: int PyCallIter_Check (PyObject *op)

     Return true if the type of 'op' is *note PyCallIter_Type: 4793.
     This function always succeeds.

 -- C 函式: *note PyObject: 311. *PyCallIter_New (PyObject *callable,
          PyObject *sentinel)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     new iterator.  The first parameter, 'callable', can be any Python
     callable object that can be called with no parameters; each call to
     it should return the next item in the iteration.  When 'callable'
     returns a value equal to 'sentinel', the iteration will be
     terminated.


File: python.info,  Node: Descriptor（描述器）物件,  Next: 切片物件,  Prev: 疊代器（Iterator）物件,  Up: 其他物件<2>

7.8.6.10 Descriptor（描述器）物件
.................................

"Descriptor" 是描述物件某些屬性的物件，它們存在於型別物件的 dictionary（
字典）中。

 -- C 變數: *note PyTypeObject: a48. PyProperty_Type
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  內建 descriptor 型別的型別物件
     。

 -- C 函式: *note PyObject: 311. *PyDescr_NewGetSet (PyTypeObject *type,
          struct PyGetSetDef *getset)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

 -- C 函式: *note PyObject: 311. *PyDescr_NewMember (PyTypeObject *type,
          struct PyMemberDef *meth)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

 -- C 函式: *note PyObject: 311. *PyDescr_NewMethod (PyTypeObject *type,
          struct PyMethodDef *meth)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

 -- C 函式: *note PyObject: 311. *PyDescr_NewWrapper (PyTypeObject
          *type, struct wrapperbase *wrapper, void *wrapped)
     '回傳值：新的參照。'

 -- C 函式: *note PyObject: 311. *PyDescr_NewClassMethod (PyTypeObject
          *type, PyMethodDef *method)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'

 -- C 函式: int PyDescr_IsData (PyObject *descr)

     如果 descriptor 物件 'descr' 描述的是一個資料屬性則回傳非零值，或者
     如果它描述的是一個方法則返回 ‘0’。'descr' 必須為一個 descriptor 物
     件；沒有錯誤檢查。

 -- C 函式: *note PyObject: 311. *PyWrapper_New (PyObject*, PyObject*)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'


File: python.info,  Node: 切片物件,  Next: MemoryView 物件,  Prev: Descriptor（描述器）物件,  Up: 其他物件<2>

7.8.6.11 切片物件
.................

 -- C 變數: *note PyTypeObject: a48. PySlice_Type
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  The type object for slice
     objects.  This is the same as *note slice: 410. in the Python
     layer.

 -- C 函式: int PySlice_Check (PyObject *ob)

     Return true if 'ob' is a slice object; 'ob' must not be ‘NULL’.
     This function always succeeds.

 -- C 函式: *note PyObject: 311. *PySlice_New (PyObject *start, PyObject
          *stop, PyObject *step)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     new slice object with the given values.  The 'start', 'stop', and
     'step' parameters are used as the values of the slice object
     attributes of the same names.  Any of the values may be ‘NULL’, in
     which case the ‘None’ will be used for the corresponding attribute.

     Return ‘NULL’ with an exception set if the new object could not be
     allocated.

 -- C 函式: int PySlice_GetIndices (PyObject *slice, Py_ssize_t length,
          Py_ssize_t *start, Py_ssize_t *stop, Py_ssize_t *step)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Retrieve the start, stop and
     step indices from the slice object 'slice', assuming a sequence of
     length 'length'.  Treats indices greater than 'length' as errors.

     Returns ‘0’ on success and ‘-1’ on error with no exception set
     (unless one of the indices was not ‘None’ and failed to be
     converted to an integer, in which case ‘-1’ is returned with an
     exception set).

     You probably do not want to use this function.

     在 3.2 版的變更: The parameter type for the 'slice' parameter was
     ‘PySliceObject*’ before.

 -- C 函式: int PySlice_GetIndicesEx (PyObject *slice, Py_ssize_t
          length, Py_ssize_t *start, Py_ssize_t *stop, Py_ssize_t *step,
          Py_ssize_t *slicelength)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Usable replacement for *note
     PySlice_GetIndices(): 485a.  Retrieve the start, stop, and step
     indices from the slice object 'slice' assuming a sequence of length
     'length', and store the length of the slice in 'slicelength'.  Out
     of bounds indices are clipped in a manner consistent with the
     handling of normal slices.

     成功時回傳 ‘0’ ，在失敗時回傳 ‘-1’ 並設定例外。

          備註: This function is considered not safe for resizable
          sequences.  Its invocation should be replaced by a combination
          of *note PySlice_Unpack(): 3c5. and *note
          PySlice_AdjustIndices(): 3c6. where

               if (PySlice_GetIndicesEx(slice, length, &start, &stop, &step, &slicelength) < 0) {
                   // return error
               }

          is replaced by

               if (PySlice_Unpack(slice, &start, &stop, &step) < 0) {
                   // return error
               }
               slicelength = PySlice_AdjustIndices(length, &start, &stop, step);

     在 3.2 版的變更: The parameter type for the 'slice' parameter was
     ‘PySliceObject*’ before.

     在 3.6.1 版的變更: If ‘Py_LIMITED_API’ is not set or set to the
     value between ‘0x03050400’ and ‘0x03060000’ (not including) or
     ‘0x03060100’ or higher ‘PySlice_GetIndicesEx()’ is implemented as a
     macro using ‘PySlice_Unpack()’ and ‘PySlice_AdjustIndices()’.
     Arguments 'start', 'stop' and 'step' are evaluated more than once.

     在 3.6.1 版之後被棄用: If ‘Py_LIMITED_API’ is set to the value less
     than ‘0x03050400’ or between ‘0x03060000’ and ‘0x03060100’ (not
     including) ‘PySlice_GetIndicesEx()’ is a deprecated function.

 -- C 函式: int PySlice_Unpack (PyObject *slice, Py_ssize_t *start,
          Py_ssize_t *stop, Py_ssize_t *step)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Extract the
     start, stop and step data members from a slice object as C
     integers.  Silently reduce values larger than ‘PY_SSIZE_T_MAX’ to
     ‘PY_SSIZE_T_MAX’, silently boost the start and stop values less
     than ‘PY_SSIZE_T_MIN’ to ‘PY_SSIZE_T_MIN’, and silently boost the
     step values less than ‘-PY_SSIZE_T_MAX’ to ‘-PY_SSIZE_T_MAX’.

     成功時回傳 ‘0’，在失敗時回傳 ‘-1’ 並設定例外。

     在 3.6.1 版被加入.

 -- C 函式: *note Py_ssize_t: a03. PySlice_AdjustIndices (Py_ssize_t
          length, Py_ssize_t *start, Py_ssize_t *stop, Py_ssize_t step)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Adjust
     start/end slice indices assuming a sequence of the specified
     length.  Out of bounds indices are clipped in a manner consistent
     with the handling of normal slices.

     Return the length of the slice.  Always successful.  Doesn't call
     Python code.

     在 3.6.1 版被加入.

* Menu:

* Ellipsis Object::


File: python.info,  Node: Ellipsis Object,  Up: 切片物件

7.8.6.12 Ellipsis Object
........................

 -- C 變數: *note PyObject: 311. *Py_Ellipsis

     The Python ‘Ellipsis’ object.  This object has no methods.  Like
     *note Py_None: 46d6, it is an *note immortal: 4190. singleton
     object.

     在 3.12 版的變更: *note Py_Ellipsis: 4ae6. 為不滅的 (immortal)。


File: python.info,  Node: MemoryView 物件,  Next: 弱參照物件<2>,  Prev: 切片物件,  Up: 其他物件<2>

7.8.6.13 MemoryView 物件
........................

A *note memoryview: 40f. object exposes the C level *note buffer
interface: 367. as a Python object which can then be passed around like
any other object.

 -- C 函式: *note PyObject: 311. *PyMemoryView_FromObject (PyObject
          *obj)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a
     memoryview object from an object that provides the buffer
     interface.  If 'obj' supports writable buffer exports, the
     memoryview object will be read/write, otherwise it may be either
     read-only or read/write at the discretion of the exporter.

 -- C 巨集: PyBUF_READ

     Flag to request a readonly buffer.

 -- C 巨集: PyBUF_WRITE

     Flag to request a writable buffer.

 -- C 函式: *note PyObject: 311. *PyMemoryView_FromMemory (char *mem,
          Py_ssize_t size, int flags)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本
     開始.'  Create a memoryview object using 'mem' as the underlying
     buffer.  'flags' can be one of *note PyBUF_READ: 1586. or *note
     PyBUF_WRITE: 1587.

     在 3.3 版被加入.

 -- C 函式: *note PyObject: 311. *PyMemoryView_FromBuffer (const
          Py_buffer *view)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.11 版本
     開始.'  Create a memoryview object wrapping the given buffer
     structure 'view'.  For simple byte buffers, *note
     PyMemoryView_FromMemory(): 1109. is the preferred function.

 -- C 函式: *note PyObject: 311. *PyMemoryView_GetContiguous (PyObject
          *obj, int buffertype, char order)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a
     memoryview object to a *note contiguous: 2103. chunk of memory (in
     either 'C' or 'F'ortran 'order') from an object that defines the
     buffer interface.  If memory is contiguous, the memoryview object
     points to the original memory.  Otherwise, a copy is made and the
     memoryview points to a new bytes object.

     'buffertype' can be one of *note PyBUF_READ: 1586. or *note
     PyBUF_WRITE: 1587.

 -- C 函式: int PyMemoryView_Check (PyObject *obj)

     Return true if the object 'obj' is a memoryview object.  It is not
     currently allowed to create subclasses of *note memoryview: 40f.
     This function always succeeds.

 -- C 函式: *note Py_buffer: 6fc. *PyMemoryView_GET_BUFFER (PyObject
          *mview)

     Return a pointer to the memoryview's private copy of the exporter's
     buffer.  'mview' 'must' be a memoryview instance; this macro
     doesn't check its type, you must do it yourself or you will risk
     crashes.

 -- C 函式: *note PyObject: 311. *PyMemoryView_GET_BASE (PyObject
          *mview)

     Return either a pointer to the exporting object that the memoryview
     is based on or ‘NULL’ if the memoryview has been created by one of
     the functions *note PyMemoryView_FromMemory(): 1109. or *note
     PyMemoryView_FromBuffer(): 705.  'mview' 'must' be a memoryview
     instance.


File: python.info,  Node: 弱參照物件<2>,  Next: Capsules<2>,  Prev: MemoryView 物件,  Up: 其他物件<2>

7.8.6.14 弱參照物件
...................

Python supports 'weak references' as first-class objects.  There are two
specific object types which directly implement weak references.  The
first is a simple reference object, and the second acts as a proxy for
the original object as much as it can.

 -- C 函式: int PyWeakref_Check (PyObject *ob)

     Return non-zero if 'ob' is either a reference or proxy object.
     This function always succeeds.

 -- C 函式: int PyWeakref_CheckRef (PyObject *ob)

     Return non-zero if 'ob' is a reference object.  This function
     always succeeds.

 -- C 函式: int PyWeakref_CheckProxy (PyObject *ob)

     Return non-zero if 'ob' is a proxy object.  This function always
     succeeds.

 -- C 函式: *note PyObject: 311. *PyWeakref_NewRef (PyObject *ob,
          PyObject *callback)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     weak reference object for the object 'ob'.  This will always return
     a new reference, but is not guaranteed to create a new object; an
     existing reference object may be returned.  The second parameter,
     'callback', can be a callable object that receives notification
     when 'ob' is garbage collected; it should accept a single
     parameter, which will be the weak reference object itself.
     'callback' may also be ‘None’ or ‘NULL’.  If 'ob' is not a weakly
     referenceable object, or if 'callback' is not callable, ‘None’, or
     ‘NULL’, this will return ‘NULL’ and raise *note TypeError: 4dd.

 -- C 函式: *note PyObject: 311. *PyWeakref_NewProxy (PyObject *ob,
          PyObject *callback)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     weak reference proxy object for the object 'ob'.  This will always
     return a new reference, but is not guaranteed to create a new
     object; an existing proxy object may be returned.  The second
     parameter, 'callback', can be a callable object that receives
     notification when 'ob' is garbage collected; it should accept a
     single parameter, which will be the weak reference object itself.
     'callback' may also be ‘None’ or ‘NULL’.  If 'ob' is not a weakly
     referenceable object, or if 'callback' is not callable, ‘None’, or
     ‘NULL’, this will return ‘NULL’ and raise *note TypeError: 4dd.

 -- C 函式: int PyWeakref_GetRef (PyObject *ref, PyObject **pobj)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Get a *note
     strong reference: 2ee. to the referenced object from a weak
     reference, 'ref', into '*pobj'.

        * On success, set '*pobj' to a new *note strong reference: 2ee.
          to the referenced object and return 1.

        * If the reference is dead, set '*pobj' to ‘NULL’ and return 0.

        * On error, raise an exception and return -1.

     在 3.13 版被加入.

 -- C 函式: *note PyObject: 311. *PyWeakref_GetObject (PyObject *ref)
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     *note borrowed reference: 2ef. to the referenced object from a weak
     reference, 'ref'.  If the referent is no longer live, returns
     ‘Py_None’.

          備註: This function returns a *note borrowed reference: 2ef.
          to the referenced object.  This means that you should always
          call *note Py_INCREF(): 514. on the object except when it
          cannot be destroyed before the last usage of the borrowed
          reference.

     Deprecated since version 3.13, will be removed in version 3.15: Use
     *note PyWeakref_GetRef(): 2f0. instead.

 -- C 函式: *note PyObject: 311. *PyWeakref_GET_OBJECT (PyObject *ref)
     '回傳值：借用參照。' Similar to *note PyWeakref_GetObject(): 2f1,
     but does no error checking.

     Deprecated since version 3.13, will be removed in version 3.15: Use
     *note PyWeakref_GetRef(): 2f0. instead.

 -- C 函式: void PyObject_ClearWeakRefs (PyObject *object)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This function is called by the
     *note tp_dealloc: 4704. handler to clear weak references.

     This iterates through the weak references for 'object' and calls
     callbacks for those references which have one.  It returns when all
     callbacks have been attempted.

 -- C 函式: void PyUnstable_Object_ClearWeakRefsNoCallbacks (PyObject
          *object)

          這是 不穩定 API，它可能在小版本發布中沒有任何警告地被變更。 '這是 *note 不穩定 API: 4ed.，它可能在小版本發布中沒有任何警告地被變更。': 
     Clears the weakrefs for 'object' without calling the callbacks.

     This function is called by the *note tp_dealloc: 4704. handler for
     types with finalizers (i.e., *note __del__(): 1e36.).  The handler
     for those objects first calls *note PyObject_ClearWeakRefs(): 51c.
     to clear weakrefs and call their callbacks, then the finalizer, and
     finally this function to clear any weakrefs that may have been
     created by the finalizer.

     In most circumstances, it's more appropriate to use *note
     PyObject_ClearWeakRefs(): 51c. to clear weakrefs instead of this
     function.

     在 3.13 版被加入.


File: python.info,  Node: Capsules<2>,  Next: Frame 物件,  Prev: 弱參照物件<2>,  Up: 其他物件<2>

7.8.6.15 Capsules
.................

Refer to *note Providing a C API for an Extension Module: 12ea. for more
information on using these objects.

在 3.1 版被加入.

 -- C 型別: type PyCapsule

     This subtype of *note PyObject: 311. represents an opaque value,
     useful for C extension modules who need to pass an opaque value (as
     a void* pointer) through Python code to other C code.  It is often
     used to make a C function pointer defined in one module available
     to other modules, so the regular import mechanism can be used to
     access C APIs defined in dynamically loaded modules.

 -- C 型別: type PyCapsule_Destructor
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  The type of a destructor
     callback for a capsule.  Defined as:

          typedef void (*PyCapsule_Destructor)(PyObject *);

     See *note PyCapsule_New(): 46f9. for the semantics of
     PyCapsule_Destructor callbacks.

 -- C 函式: int PyCapsule_CheckExact (PyObject *p)

     Return true if its argument is a *note PyCapsule: 120b.  This
     function always succeeds.

 -- C 函式: *note PyObject: 311. *PyCapsule_New (void *pointer, const
          char *name, PyCapsule_Destructor destructor)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a
     *note PyCapsule: 120b. encapsulating the 'pointer'.  The 'pointer'
     argument may not be ‘NULL’.

     On failure, set an exception and return ‘NULL’.

     The 'name' string may either be ‘NULL’ or a pointer to a valid C
     string.  If non-‘NULL’, this string must outlive the capsule.
     (Though it is permitted to free it inside the 'destructor'.)

     If the 'destructor' argument is not ‘NULL’, it will be called with
     the capsule as its argument when it is destroyed.

     If this capsule will be stored as an attribute of a module, the
     'name' should be specified as ‘modulename.attributename’.  This
     will enable other modules to import the capsule using *note
     PyCapsule_Import(): 1770.

 -- C 函式: void *PyCapsule_GetPointer (PyObject *capsule, const char
          *name)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Retrieve the 'pointer' stored
     in the capsule.  On failure, set an exception and return ‘NULL’.

     The 'name' parameter must compare exactly to the name stored in the
     capsule.  If the name stored in the capsule is ‘NULL’, the 'name'
     passed in must also be ‘NULL’.  Python uses the C function
     ‘strcmp()’ to compare capsule names.

 -- C 函式: *note PyCapsule_Destructor: 4795. PyCapsule_GetDestructor
          (PyObject *capsule)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the current destructor
     stored in the capsule.  On failure, set an exception and return
     ‘NULL’.

     It is legal for a capsule to have a ‘NULL’ destructor.  This makes
     a ‘NULL’ return code somewhat ambiguous; use *note
     PyCapsule_IsValid(): 12e9. or *note PyErr_Occurred(): 17f4. to
     disambiguate.

 -- C 函式: void *PyCapsule_GetContext (PyObject *capsule)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the current context
     stored in the capsule.  On failure, set an exception and return
     ‘NULL’.

     It is legal for a capsule to have a ‘NULL’ context.  This makes a
     ‘NULL’ return code somewhat ambiguous; use *note
     PyCapsule_IsValid(): 12e9. or *note PyErr_Occurred(): 17f4. to
     disambiguate.

 -- C 函式: const char *PyCapsule_GetName (PyObject *capsule)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the current name stored
     in the capsule.  On failure, set an exception and return ‘NULL’.

     It is legal for a capsule to have a ‘NULL’ name.  This makes a
     ‘NULL’ return code somewhat ambiguous; use *note
     PyCapsule_IsValid(): 12e9. or *note PyErr_Occurred(): 17f4. to
     disambiguate.

 -- C 函式: void *PyCapsule_Import (const char *name, int no_block)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Import a pointer to a C object
     from a capsule attribute in a module.  The 'name' parameter should
     specify the full name to the attribute, as in ‘module.attribute’.
     The 'name' stored in the capsule must match this string exactly.

     Return the capsule's internal 'pointer' on success.  On failure,
     set an exception and return ‘NULL’.

     在 3.3 版的變更: 'no_block' has no effect anymore.

 -- C 函式: int PyCapsule_IsValid (PyObject *capsule, const char *name)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Determines whether or not
     'capsule' is a valid capsule.  A valid capsule is non-‘NULL’,
     passes *note PyCapsule_CheckExact(): 4af4, has a non-‘NULL’ pointer
     stored in it, and its internal name matches the 'name' parameter.
     (See *note PyCapsule_GetPointer(): 4799. for information on how
     capsule names are compared.)

     In other words, if *note PyCapsule_IsValid(): 12e9. returns a true
     value, calls to any of the accessors (any function starting with
     ‘PyCapsule_Get’) are guaranteed to succeed.

     Return a nonzero value if the object is valid and matches the name
     passed in.  Return ‘0’ otherwise.  This function will not fail.

 -- C 函式: int PyCapsule_SetContext (PyObject *capsule, void *context)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Set the context pointer inside
     'capsule' to 'context'.

     Return ‘0’ on success.  Return nonzero and set an exception on
     failure.

 -- C 函式: int PyCapsule_SetDestructor (PyObject *capsule,
          PyCapsule_Destructor destructor)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Set the destructor inside
     'capsule' to 'destructor'.

     Return ‘0’ on success.  Return nonzero and set an exception on
     failure.

 -- C 函式: int PyCapsule_SetName (PyObject *capsule, const char *name)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Set the name inside 'capsule'
     to 'name'.  If non-‘NULL’, the name must outlive the capsule.  If
     the previous 'name' stored in the capsule was not ‘NULL’, no
     attempt is made to free it.

     Return ‘0’ on success.  Return nonzero and set an exception on
     failure.

 -- C 函式: int PyCapsule_SetPointer (PyObject *capsule, void *pointer)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Set the void pointer inside
     'capsule' to 'pointer'.  The pointer may not be ‘NULL’.

     Return ‘0’ on success.  Return nonzero and set an exception on
     failure.


File: python.info,  Node: Frame 物件,  Next: 產生器 Generator 物件,  Prev: Capsules<2>,  Up: 其他物件<2>

7.8.6.16 Frame 物件
...................

 -- C 型別: type PyFrameObject
     ' 為 *note 受限 API 的一部分: 4f9. （做為一個不透明結構 (opaque
     struct)）.'  用來描述 frame 物件的 C 結構。

     在這個結構中沒有公開的成員。

     在 3.11 版的變更: The members of this structure were removed from
     the public C API. Refer to the *note What's New entry: 72c. for
     details.

The *note PyEval_GetFrame(): 16bf. and *note PyThreadState_GetFrame():
732. functions can be used to get a frame object.

See also *note Reflection: 4947.

 -- C 變數: *note PyTypeObject: a48. PyFrame_Type

     The type of frame objects.  It is the same object as *note
     types.FrameType: 1756. in the Python layer.

     在 3.11 版的變更: Previously, this type was only available after
     including ‘<frameobject.h>’.

 -- C 函式: int PyFrame_Check (PyObject *obj)

     Return non-zero if 'obj' is a frame object.

     在 3.11 版的變更: Previously, this function was only available
     after including ‘<frameobject.h>’.

 -- C 函式: *note PyFrameObject: 72d. *PyFrame_GetBack (PyFrameObject
          *frame)
     '回傳值：新的參照。' Get the 'frame' next outer frame.

     Return a *note strong reference: 2ee, or ‘NULL’ if 'frame' has no
     outer frame.

     在 3.9 版被加入.

 -- C 函式: *note PyObject: 311. *PyFrame_GetBuiltins (PyFrameObject
          *frame)
     '回傳值：新的參照。' 取得 'frame' 的 *note f_builtins: 1e22. 屬性。

     回傳 *note strong reference: 2ee.。結果不能為 ‘NULL’。

     在 3.11 版被加入.

 -- C 函式: *note PyCodeObject: 71b. *PyFrame_GetCode (PyFrameObject
          *frame)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本
     開始.'  Get the 'frame' code.

     回傳 *note strong reference: 2ee.。

     The result (frame code) cannot be ‘NULL’.

     在 3.9 版被加入.

 -- C 函式: *note PyObject: 311. *PyFrame_GetGenerator (PyFrameObject
          *frame)
     '回傳值：新的參照。' Get the generator, coroutine, or async
     generator that owns this frame, or ‘NULL’ if this frame is not
     owned by a generator.  Does not raise an exception, even if the
     return value is ‘NULL’.

     回傳 *note strong reference: 2ee. 或 ‘NULL’。

     在 3.11 版被加入.

 -- C 函式: *note PyObject: 311. *PyFrame_GetGlobals (PyFrameObject
          *frame)
     '回傳值：新的參照。' 取得 'frame' 的 *note f_globals: 1e21. 屬性。

     回傳 *note strong reference: 2ee.。結果不能為 ‘NULL’。

     在 3.11 版被加入.

 -- C 函式: int PyFrame_GetLasti (PyFrameObject *frame)

     取得 'frame' 的 *note f_lasti: 82c. 屬性。

     如果 ‘frame.f_lasti’ 是 ‘None’ 則回傳 -1。

     在 3.11 版被加入.

 -- C 函式: *note PyObject: 311. *PyFrame_GetVar (PyFrameObject *frame,
          PyObject *name)
     '回傳值：新的參照。' 取得 'frame' 的變數 'name'。

        * 在成功時回傳變數值的 *note strong reference: 2ee.。

        * 如果變數不存在，則引發 *note NameError: 3e5. 並回傳 ‘NULL’。

        * 在錯誤時引發例外並回傳 ‘NULL’。

     'name' 的型別必須是 *note str: 3f2.。

     在 3.12 版被加入.

 -- C 函式: *note PyObject: 311. *PyFrame_GetVarString (PyFrameObject
          *frame, const char *name)
     '回傳值：新的參照。' Similar to *note PyFrame_GetVar(): 50e, but
     the variable name is a C string encoded in UTF-8.

     在 3.12 版被加入.

 -- C 函式: *note PyObject: 311. *PyFrame_GetLocals (PyFrameObject
          *frame)
     '回傳值：新的參照。' Get the 'frame"s *note f_locals: 165.
     attribute.  If the frame refers to an *note optimized scope: 161,
     this returns a write-through proxy object that allows modifying the
     locals.  In all other cases (classes, modules, *note exec(): 162,
     *note eval(): 163.) it returns the mapping representing the frame
     locals directly (as described for *note locals(): 127.).

     回傳 *note strong reference: 2ee.。

     在 3.11 版被加入.

     在 3.13 版的變更: As part of PEP 667(1), return a proxy object for
     optimized scopes.

 -- C 函式: int PyFrame_GetLineNumber (PyFrameObject *frame)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本開始.'  Return the
     line number that 'frame' is currently executing.

* Menu:

* Internal Frames::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0667/


File: python.info,  Node: Internal Frames,  Up: Frame 物件

7.8.6.17 Internal Frames
........................

Unless using PEP 523(1), you will not need this.

 -- C 結構: struct _PyInterpreterFrame

     The interpreter's internal frame representation.

     在 3.11 版被加入.

 -- C 函式: *note PyObject: 311. *PyUnstable_InterpreterFrame_GetCode
          (struct _PyInterpreterFrame *frame);

          這是 不穩定 API，它可能在小版本發布中沒有任何警告地被變更。 '這是 *note 不穩定 API: 4ed.，它可能在小版本發布中沒有任何警告地被變更。': 
          Return a *note strong reference: 2ee. to the code object for
          the frame.

     在 3.12 版被加入.

 -- C 函式: int PyUnstable_InterpreterFrame_GetLasti (struct
          _PyInterpreterFrame *frame);

          這是 不穩定 API，它可能在小版本發布中沒有任何警告地被變更。 '這是 *note 不穩定 API: 4ed.，它可能在小版本發布中沒有任何警告地被變更。': 
     Return the byte offset into the last executed instruction.

     在 3.12 版被加入.

 -- C 函式: int PyUnstable_InterpreterFrame_GetLine (struct
          _PyInterpreterFrame *frame);

          這是 不穩定 API，它可能在小版本發布中沒有任何警告地被變更。 '這是 *note 不穩定 API: 4ed.，它可能在小版本發布中沒有任何警告地被變更。': 
     Return the currently executing line number, or -1 if there is no
     line number.

     在 3.12 版被加入.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0523/


File: python.info,  Node: 產生器 Generator 物件,  Next: Coroutine（協程）物件,  Prev: Frame 物件,  Up: 其他物件<2>

7.8.6.18 產生器 (Generator) 物件
................................

產生器物件是 Python 用來實現產生器疊代器 (generator iterator) 的物件。它
們通常透過疊代會產生值的函式來建立，而不是顯式呼叫 *note PyGen_New():
4aff. 或 *note PyGen_NewWithQualName(): 4b00.。

 -- C 型別: type PyGenObject

     用於產生器物件的 C 結構。

 -- C 變數: *note PyTypeObject: a48. PyGen_Type

     與產生器物件對應的型別物件。

 -- C 函式: int PyGen_Check (PyObject *ob)

     如果 'ob' 是一個產生器 (generator) 物件則回傳真值；'ob' 必須不為
     ‘NULL’。此函式總是會成功執行。

 -- C 函式: int PyGen_CheckExact (PyObject *ob)

     如果 'ob' 的型別是 *note PyGen_Type: 4b02. 則回傳真值；'ob' 必須不
     為 ‘NULL’。此函式總是會成功執行。

 -- C 函式: *note PyObject: 311. *PyGen_New (PyFrameObject *frame)
     '回傳值：新的參照。' 基於 'frame' 物件建立並回傳一個新的產生器物件
     。此函式會取走一個對 'frame' 的參照 (reference)。引數必須不為
     ‘NULL’。

 -- C 函式: *note PyObject: 311. *PyGen_NewWithQualName (PyFrameObject
          *frame, PyObject *name, PyObject *qualname)
     '回傳值：新的參照。' 基於 'frame' 物件建立並回傳一個新的產生器物件
     ，其中 ‘__name__’ 和 ‘__qualname__’ 設為 'name' 和 'qualname'。此函
     式會取走一個對 'frame' 的參照。'frame' 引數必須不為 ‘NULL’。


File: python.info,  Node: Coroutine（協程）物件,  Next: 情境變數物件,  Prev: 產生器 Generator 物件,  Up: 其他物件<2>

7.8.6.19 Coroutine（協程）物件
..............................

在 3.5 版被加入.

Coroutine 物件是那些以 ‘async’ 關鍵字來宣告的函式所回傳的物件。

 -- C 型別: type PyCoroObject

     用於 coroutine 物件的 C 結構。

 -- C 變數: *note PyTypeObject: a48. PyCoro_Type

     與 coroutine 物件對應的型別物件。

 -- C 函式: int PyCoro_CheckExact (PyObject *ob)

     如果 'ob' 的型別是 *note PyCoro_Type: 4b08. 則回傳真值；'ob' 必須不
     為 ‘NULL’。此函式總是會執行成功。

 -- C 函式: *note PyObject: 311. *PyCoro_New (PyFrameObject *frame,
          PyObject *name, PyObject *qualname)
     '回傳值：新的參照。' 基於 'frame' 物件來建立並回傳一個新的
     coroutine 物件，其中 ‘__name__’ 和 ‘__qualname__’ 被設為 'name' 和
     'qualname'。此函式會取得一個對 'frame' 的參照 (reference)。'frame'
     引數必須不為 ‘NULL’。


File: python.info,  Node: 情境變數物件,  Next: DateTime 物件,  Prev: Coroutine（協程）物件,  Up: 其他物件<2>

7.8.6.20 情境變數物件
.....................

在 3.7 版被加入.

在 3.7.1 版的變更:

     備註: In Python 3.7.1 the signatures of all context variables C
     APIs were 'changed' to use *note PyObject: 311. pointers instead of
     *note PyContext: 4b0d, *note PyContextVar: 4b0e, and *note
     PyContextToken: 4b0f, e.g.:

          // in 3.7.0:
          PyContext *PyContext_New(void);

          // in 3.7.1+:
          PyObject *PyContext_New(void);

     更多細節請見 bpo-34762(1)。

This section details the public C API for the *note contextvars: 1d.
module.

 -- C 型別: type PyContext

     The C structure used to represent a *note contextvars.Context:
     308c. object.

 -- C 型別: type PyContextVar

     The C structure used to represent a *note contextvars.ContextVar:
     308a. object.

 -- C 型別: type PyContextToken

     The C structure used to represent a *note contextvars.Token: 3091.
     object.

 -- C 變數: *note PyTypeObject: a48. PyContext_Type

     The type object representing the 'context' type.

 -- C 變數: *note PyTypeObject: a48. PyContextVar_Type

     The type object representing the 'context variable' type.

 -- C 變數: *note PyTypeObject: a48. PyContextToken_Type

     The type object representing the 'context variable token' type.

Type-check macros:

 -- C 函式: int PyContext_CheckExact (PyObject *o)

     Return true if 'o' is of type *note PyContext_Type: 4b10.  'o' must
     not be ‘NULL’.  This function always succeeds.

 -- C 函式: int PyContextVar_CheckExact (PyObject *o)

     Return true if 'o' is of type *note PyContextVar_Type: 4b11.  'o'
     must not be ‘NULL’.  This function always succeeds.

 -- C 函式: int PyContextToken_CheckExact (PyObject *o)

     Return true if 'o' is of type *note PyContextToken_Type: 4b12.  'o'
     must not be ‘NULL’.  This function always succeeds.

Context object management functions:

 -- C 函式: *note PyObject: 311. *PyContext_New (void)
     '回傳值：新的參照。' Create a new empty context object.  Returns
     ‘NULL’ if an error has occurred.

 -- C 函式: *note PyObject: 311. *PyContext_Copy (PyObject *ctx)
     '回傳值：新的參照。' Create a shallow copy of the passed 'ctx'
     context object.  Returns ‘NULL’ if an error has occurred.

 -- C 函式: *note PyObject: 311. *PyContext_CopyCurrent (void)
     '回傳值：新的參照。' Create a shallow copy of the current thread
     context.  Returns ‘NULL’ if an error has occurred.

 -- C 函式: int PyContext_Enter (PyObject *ctx)

     Set 'ctx' as the current context for the current thread.  Returns
     ‘0’ on success, and ‘-1’ on error.

 -- C 函式: int PyContext_Exit (PyObject *ctx)

     Deactivate the 'ctx' context and restore the previous context as
     the current context for the current thread.  Returns ‘0’ on
     success, and ‘-1’ on error.

Context variable functions:

 -- C 函式: *note PyObject: 311. *PyContextVar_New (const char *name,
          PyObject *def)
     '回傳值：新的參照。' Create a new ‘ContextVar’ object.  The 'name'
     parameter is used for introspection and debug purposes.  The 'def'
     parameter specifies a default value for the context variable, or
     ‘NULL’ for no default.  If an error has occurred, this function
     returns ‘NULL’.

 -- C 函式: int PyContextVar_Get (PyObject *var, PyObject
          *default_value, PyObject **value)

     Get the value of a context variable.  Returns ‘-1’ if an error has
     occurred during lookup, and ‘0’ if no error occurred, whether or
     not a value was found.

     If the context variable was found, 'value' will be a pointer to it.
     If the context variable was 'not' found, 'value' will point to:

        - 'default_value', if not ‘NULL’;

        - the default value of 'var', if not ‘NULL’;

        - ‘NULL’

     Except for ‘NULL’, the function returns a new reference.

 -- C 函式: *note PyObject: 311. *PyContextVar_Set (PyObject *var,
          PyObject *value)
     '回傳值：新的參照。' Set the value of 'var' to 'value' in the
     current context.  Returns a new token object for this change, or
     ‘NULL’ if an error has occurred.

 -- C 函式: int PyContextVar_Reset (PyObject *var, PyObject *token)

     Reset the state of the 'var' context variable to that it was in
     before *note PyContextVar_Set(): 4b1d. that returned the 'token'
     was called.  This function returns ‘0’ on success and ‘-1’ on
     error.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue?@action=redirect&bpo=34762


File: python.info,  Node: DateTime 物件,  Next: 型別提示物件,  Prev: 情境變數物件,  Up: 其他物件<2>

7.8.6.21 DateTime 物件
......................

*note datetime: 28. 模組提供各種日期和時間物件。在使用任何這些函式之前，
必須將標頭檔 ‘datetime.h’ 引入於原始碼中（請注意，‘Python.h’ 並無引入該
標頭檔），且巨集 ‘PyDateTime_IMPORT’ 必須被調用，而這通常作為模組初始化
函式的一部分。該巨集將指向 C 結構的指標放入靜態變數 ‘PyDateTimeAPI’ 中，
該變數會被以下巨集使用。

 -- C 型別: type PyDateTime_Date

     This subtype of *note PyObject: 311. represents a Python date
     object.

 -- C 型別: type PyDateTime_DateTime

     This subtype of *note PyObject: 311. represents a Python datetime
     object.

 -- C 型別: type PyDateTime_Time

     This subtype of *note PyObject: 311. represents a Python time
     object.

 -- C 型別: type PyDateTime_Delta

     This subtype of *note PyObject: 311. represents the difference
     between two datetime values.

 -- C 變數: *note PyTypeObject: a48. PyDateTime_DateType

     This instance of *note PyTypeObject: a48. represents the Python
     date type; it is the same object as *note datetime.date: 1b1. in
     the Python layer.

 -- C 變數: *note PyTypeObject: a48. PyDateTime_DateTimeType

     This instance of *note PyTypeObject: a48. represents the Python
     datetime type; it is the same object as *note datetime.datetime:
     1b0. in the Python layer.

 -- C 變數: *note PyTypeObject: a48. PyDateTime_TimeType

     This instance of *note PyTypeObject: a48. represents the Python
     time type; it is the same object as *note datetime.time: 1b2. in
     the Python layer.

 -- C 變數: *note PyTypeObject: a48. PyDateTime_DeltaType

     This instance of *note PyTypeObject: a48. represents Python type
     for the difference between two datetime values; it is the same
     object as *note datetime.timedelta: 973. in the Python layer.

 -- C 變數: *note PyTypeObject: a48. PyDateTime_TZInfoType

     This instance of *note PyTypeObject: a48. represents the Python
     time zone info type; it is the same object as *note
     datetime.tzinfo: 582. in the Python layer.

用於存取 UTC 單例 (singleton) 的巨集：

 -- C 變數: *note PyObject: 311. *PyDateTime_TimeZone_UTC

     回傳表示 UTC 的時區單例，是與 *note datetime.timezone.utc: 5b9. 相
     同的物件。

     在 3.7 版被加入.

型別檢查巨集：

 -- C 函式: int PyDate_Check (PyObject *ob)

     如果 'ob' 的型別為 *note PyDateTime_DateType: 4b25. 或
     ‘PyDateTime_DateType’ 的子型別，則回傳 true。 'ob' 不得為 ‘NULL’。
     這個函式一定會執行成功。

 -- C 函式: int PyDate_CheckExact (PyObject *ob)

     如果 'ob' 的型別為 *note PyDateTime_DateType: 4b25.，則回傳 true。
     'ob' 不得為 ‘NULL’。這個函式一定會執行成功。

 -- C 函式: int PyDateTime_Check (PyObject *ob)

     如果 'ob' 的型別為 *note PyDateTime_DateTimeType: 4b26. 或
     ‘PyDateTime_DateTimeType’ 的子型別，則回傳 true。'ob' 不得為
     ‘NULL’。這個函式一定會執行成功。

 -- C 函式: int PyDateTime_CheckExact (PyObject *ob)

     如果 'ob' 的型別為 *note PyDateTime_DateTimeType: 4b26.，則回傳
     true。'ob' 不得為 ‘NULL’。這個函式一定會執行成功。

 -- C 函式: int PyTime_Check (PyObject *ob)

     如果 'ob' 的型別為 *note PyDateTime_TimeType: 4b27. 或
     ‘PyDateTime_TimeType’ 的子型別，則回傳 true。'ob' 不得為 ‘NULL’。這
     個函式一定會執行成功。

 -- C 函式: int PyTime_CheckExact (PyObject *ob)

     如果 'ob' 的型別為 *note PyDateTime_TimeType: 4b27.，則回傳 true。
     'ob' 不得為 ‘NULL’。這個函式一定會執行成功。

 -- C 函式: int PyDelta_Check (PyObject *ob)

     如果 'ob' 的型別為 *note PyDateTime_DeltaType: 4b28. 或
     ‘PyDateTime_DeltaType’ 的子型別，則回傳 true。'ob' 不得為 ‘NULL’。
     這個函式一定會執行成功。

 -- C 函式: int PyDelta_CheckExact (PyObject *ob)

     如果 'ob' 的型別為 *note PyDateTime_DeltaType: 4b28.，則回傳 true。
     'ob' 不得為 ‘NULL’。這個函式一定會執行成功。

 -- C 函式: int PyTZInfo_Check (PyObject *ob)

     如果 'ob' 的型別為 *note PyDateTime_TZInfoType: 4b29. 或
     ‘PyDateTime_TZInfoType’ 的子型別，則回傳 true。'ob' 不得為 ‘NULL’。
     這個函式一定會執行成功。

 -- C 函式: int PyTZInfo_CheckExact (PyObject *ob)

     如果 'ob' 的型別為 *note PyDateTime_TZInfoType: 4b29.，則回傳 true。
     'ob' 不得為 ‘NULL’。這個函式一定會執行成功。

建立物件的巨集：

 -- C 函式: *note PyObject: 311. *PyDate_FromDate (int year, int month,
          int day)
     '回傳值：新的參照。' 回傳一個有特定年、月、日的物件 *note
     datetime.date: 1b1.。

 -- C 函式: *note PyObject: 311. *PyDateTime_FromDateAndTime (int year,
          int month, int day, int hour, int minute, int second, int
          usecond)
     '回傳值：新的參照。' 回傳一個有特定年、月、日、時、分、秒、微秒的物
     件 *note datetime.datetime: 1b0.。

 -- C 函式: *note PyObject: 311. *PyDateTime_FromDateAndTimeAndFold (int
          year, int month, int day, int hour, int minute, int second,
          int usecond, int fold)
     '回傳值：新的參照。' 回傳一個有特定年、月、日、時、分、秒、微秒與
     fold（時間折疊）的物件 *note datetime.datetime: 1b0.。

     在 3.6 版被加入.

 -- C 函式: *note PyObject: 311. *PyTime_FromTime (int hour, int minute,
          int second, int usecond)
     '回傳值：新的參照。' 回傳一個有特定時、分、秒、微秒的物件 *note
     datetime.date: 1b1.。

 -- C 函式: *note PyObject: 311. *PyTime_FromTimeAndFold (int hour, int
          minute, int second, int usecond, int fold)
     '回傳值：新的參照。' 回傳一個有特定時、分、秒、微秒與 fold（時間折
     疊）的物件 *note datetime.time: 1b2.。

     在 3.6 版被加入.

 -- C 函式: *note PyObject: 311. *PyDelta_FromDSU (int days, int
          seconds, int useconds)
     '回傳值：新的參照。' 回傳一個 *note datetime.timedelta: 973. 物件，
     表示給定的天數、秒數和微秒數。執行標準化 (normalization) 以便生成的
     微秒數和秒數位於 *note datetime.timedelta: 973. 物件記錄的範圍內。

 -- C 函式: *note PyObject: 311. *PyTimeZone_FromOffset (PyObject
          *offset)
     '回傳值：新的參照。' 回傳一個 *note datetime.timezone: 1059. 物件，
     其未命名的固定偏移量由 'offset' 引數表示。

     在 3.7 版被加入.

 -- C 函式: *note PyObject: 311. *PyTimeZone_FromOffsetAndName (PyObject
          *offset, PyObject *name)
     '回傳值：新的參照。' 回傳一個 *note datetime.timezone: 1059. 物件，
     其固定偏移量由 'offset' 引數表示，並帶有 tzname 'name'。

     在 3.7 版被加入.

從 date 物件中提取欄位的巨集。引數必須是個 *note PyDateTime_Date: 4b21.
的實例，包括子類別（例如 *note PyDateTime_DateTime: 4b22.）。引數不得為
‘NULL’，並且不會檢查型別：

 -- C 函式: int PyDateTime_GET_YEAR (PyDateTime_Date *o)

     回傳年份，為正整數。

 -- C 函式: int PyDateTime_GET_MONTH (PyDateTime_Date *o)

     回傳月份，為正整數，從 1 到 12。

 -- C 函式: int PyDateTime_GET_DAY (PyDateTime_Date *o)

     回傳日期，為正整數，從 1 到 31。

從 datetime 物件中提取欄位的巨集。引數必須是個 *note
PyDateTime_DateTime: 4b22. 的實例，包括子類別。引數不得為 ‘NULL’，並且不
會檢查型別：

 -- C 函式: int PyDateTime_DATE_GET_HOUR (PyDateTime_DateTime *o)

     回傳小時，為正整數，從 0 到 23。

 -- C 函式: int PyDateTime_DATE_GET_MINUTE (PyDateTime_DateTime *o)

     回傳分鐘，為正整數，從 0 到 59。

 -- C 函式: int PyDateTime_DATE_GET_SECOND (PyDateTime_DateTime *o)

     回傳秒，為正整數，從0 到59。

 -- C 函式: int PyDateTime_DATE_GET_MICROSECOND (PyDateTime_DateTime *o)

     回傳微秒，為正整數，從 0 到 999999。

 -- C 函式: int PyDateTime_DATE_GET_FOLD (PyDateTime_DateTime *o)

     回傳 fold，為 0 或 1 的正整數。

     在 3.6 版被加入.

 -- C 函式: *note PyObject: 311. *PyDateTime_DATE_GET_TZINFO
          (PyDateTime_DateTime *o)

     回傳 tzinfo（可能是 ‘None’）。

     在 3.10 版被加入.

從 time 物件中提取欄位的巨集。引數必須是個 *note PyDateTime_Time: 4b23.
的實例，包括子類別。引數不得為 ‘NULL’，並且不會檢查型別：

 -- C 函式: int PyDateTime_TIME_GET_HOUR (PyDateTime_Time *o)

     回傳小時，為正整數，從 0 到 23。

 -- C 函式: int PyDateTime_TIME_GET_MINUTE (PyDateTime_Time *o)

     回傳分鐘，為正整數，從 0 到 59。

 -- C 函式: int PyDateTime_TIME_GET_SECOND (PyDateTime_Time *o)

     回傳秒，為正整數，從0 到59。

 -- C 函式: int PyDateTime_TIME_GET_MICROSECOND (PyDateTime_Time *o)

     回傳微秒，為正整數，從 0 到 999999。

 -- C 函式: int PyDateTime_TIME_GET_FOLD (PyDateTime_Time *o)

     回傳 fold，為 0 或 1 的正整數。

     在 3.6 版被加入.

 -- C 函式: *note PyObject: 311. *PyDateTime_TIME_GET_TZINFO
          (PyDateTime_Time *o)

     回傳 tzinfo（可能是 ‘None’）。

     在 3.10 版被加入.

從 time delta 物件中提取欄位的巨集。引數必須是個 *note PyDateTime_Delta:
4b24. 的實例，包括子類別。引數不能為 ‘NULL’，並且不會檢查型別：

 -- C 函式: int PyDateTime_DELTA_GET_DAYS (PyDateTime_Delta *o)

     以 -999999999 到 999999999 之間的整數形式回傳天數。

     在 3.3 版被加入.

 -- C 函式: int PyDateTime_DELTA_GET_SECONDS (PyDateTime_Delta *o)

     以 0 到 86399 之間的整數形式回傳秒數。

     在 3.3 版被加入.

 -- C 函式: int PyDateTime_DELTA_GET_MICROSECONDS (PyDateTime_Delta *o)

     以 0 到 999999 之間的整數形式回傳微秒數。

     在 3.3 版被加入.

為了方便模組實作 DB API 的巨集：

 -- C 函式: *note PyObject: 311. *PyDateTime_FromTimestamp (PyObject
          *args)
     '回傳值：新的參照。' 給定一個適合傳遞給 *note
     datetime.datetime.fromtimestamp(): 495. 的引數元組，建立並回傳一個
     新的 *note datetime.datetime: 1b0. 物件。

 -- C 函式: *note PyObject: 311. *PyDate_FromTimestamp (PyObject *args)
     '回傳值：新的參照。' 給定一個適合傳遞給 *note
     datetime.date.fromtimestamp(): 14fd. 的引數元組，建立並回傳一個新的
     *note datetime.date: 1b1. 物件。


File: python.info,  Node: 型別提示物件,  Prev: DateTime 物件,  Up: 其他物件<2>

7.8.6.22 型別提示物件
.....................

提供了數個用於型別提示的內建型別。目前有兩種 - *note GenericAlias: 656.
和 *note Union: 766.。只有 ‘GenericAlias’ 有公開 (expose) 給 C。

 -- C 函式: *note PyObject: 311. *Py_GenericAlias (PyObject *origin,
          PyObject *args)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.9 版本開始.'  建立一個
     *note GenericAlias: 656. 物件，等同於呼叫 Python 的 *note
     types.GenericAlias: 78f. class。 'origin' 和 'args' 引數分別設定了
     ‘GenericAlias’ 的 ‘__origin__’ 與 ‘__args__’ 屬性。'origin' 應該要
     是個 *note PyTypeObject: a48.* 且 'args' 可以是個 *note
     PyTupleObject: 491d.* 或任意 ‘PyObject*’。如果傳入的 'args' 不是個
     tuple（元組），則會自動建立一個長度為 1 的 tuple 且 ‘__args__’ 會被
     設為 ‘(args,)’。只會進行最少的引數檢查，所以即便 'origin' 不是個型
     別，函式也會不會失敗。 ‘GenericAlias’ 的 ‘__parameters__’ 屬性會自
     ‘__args__’ 惰性地建立 (constructed lazily)。當失敗時，會引發一個例
     外並回傳 ‘NULL’。

     以下是個讓一個擴充型別泛用化 (generic) 的例子：

          ...
          static PyMethodDef my_obj_methods[] = {
              // Other methods.
              ...
              {"__class_getitem__", Py_GenericAlias, METH_O|METH_CLASS, "See PEP 585"}
              ...
          }

     也參考
     ......

     資料模型方法 *note __class_getitem__(): 6df.。

     在 3.9 版被加入.

 -- C 變數: *note PyTypeObject: a48. Py_GenericAliasType
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.9 版本開始.'  *note
     Py_GenericAlias(): 48b5. 所回傳該物件的 C 型別。等價於 Python 中的
     *note types.GenericAlias: 78f.。

     在 3.9 版被加入.


File: python.info,  Node: Initialization Finalization and Threads,  Next: Python 初始化設定,  Prev: 具體物件層,  Up: Python/C API 參考手冊

7.9 Initialization, Finalization, and Threads
=============================================

也請參見 *note Python 初始化設定: 372.。

* Menu:

* Python 初始化之前::
* Global configuration variables::
* Initializing and finalizing the interpreter::
* Process-wide parameters::
* Thread State and the Global Interpreter Lock::
* Sub-interpreter support::
* Asynchronous Notifications::
* Profiling and Tracing::
* Reference tracing::
* Advanced Debugger Support::
* Thread Local Storage Support::
* Synchronization Primitives::


File: python.info,  Node: Python 初始化之前,  Next: Global configuration variables,  Up: Initialization Finalization and Threads

7.9.1 Python 初始化之前
-----------------------

In an application embedding Python, the *note Py_Initialize(): 851.
function must be called before using any other Python/C API functions;
with the exception of a few functions and the *note global configuration
variables: 4b52.

The following functions can be safely called before Python is
initialized:

   * Configuration functions:

        * *note PyImport_AppendInittab(): 16a6.

        * *note PyImport_ExtendInittab(): 16a7.

        * ‘PyInitFrozenExtensions()’

        * *note PyMem_SetAllocator(): 531.

        * *note PyMem_SetupDebugHooks(): c11.

        * *note PyObject_SetArenaAllocator(): 4b53.

        * *note Py_SetProgramName(): 1532.

        * *note Py_SetPythonHome(): 1531.

        * *note PySys_ResetWarnOptions(): 37a.

   * Informative functions:

        * *note Py_IsInitialized(): 476d.

        * *note PyMem_GetAllocator(): 4b54.

        * *note PyObject_GetArenaAllocator(): 4b55.

        * *note Py_GetBuildInfo(): 139f.

        * *note Py_GetCompiler(): 48b7.

        * *note Py_GetCopyright(): 48b8.

        * *note Py_GetPlatform(): 48b9.

        * *note Py_GetVersion(): 48ba.

   * Utilities:

        * *note Py_DecodeLocale(): b6e.

   * Memory allocators:

        * *note PyMem_RawMalloc(): 323.

        * *note PyMem_RawRealloc(): 325.

        * *note PyMem_RawCalloc(): 324.

        * *note PyMem_RawFree(): 326.

   * Synchronization:

        * *note PyMutex_Lock(): 34b.

        * *note PyMutex_Unlock(): 4b56.

     備註: The following functions 'should not be called' before *note
     Py_Initialize(): 851.: *note Py_EncodeLocale(): b6f, *note
     Py_GetPath(): 37e, *note Py_GetPrefix(): 380, *note
     Py_GetExecPrefix(): 37c, *note Py_GetProgramFullPath(): 382, *note
     Py_GetPythonHome(): 385, *note Py_GetProgramName(): 384. and *note
     PyEval_InitThreads(): 1535.


File: python.info,  Node: Global configuration variables,  Next: Initializing and finalizing the interpreter,  Prev: Python 初始化之前,  Up: Initialization Finalization and Threads

7.9.2 Global configuration variables
------------------------------------

Python has variables for the global configuration to control different
features and options.  By default, these flags are controlled by *note
command line options: 1c2b.

When a flag is set by an option, the value of the flag is the number of
times that the option was set.  For example, ‘-b’ sets *note
Py_BytesWarningFlag: 39f. to 1 and ‘-bb’ sets *note Py_BytesWarningFlag:
39f. to 2.

 -- C 變數: int Py_BytesWarningFlag

     This API is kept for backward compatibility: setting *note
     PyConfig.bytes_warning: 3a0. should be used instead, see *note
     Python Initialization Configuration: 372.

     Issue a warning when comparing *note bytes: 1a5. or *note
     bytearray: 4e3. with *note str: 3f2. or *note bytes: 1a5. with
     *note int: 23c.  Issue an error if greater or equal to ‘2’.

     由 *note -b: 587. 選項設定。

     Deprecated since version 3.12, will be removed in version 3.14.

 -- C 變數: int Py_DebugFlag

     This API is kept for backward compatibility: setting *note
     PyConfig.parser_debug: 392. should be used instead, see *note
     Python Initialization Configuration: 372.

     Turn on parser debugging output (for expert only, depending on
     compilation options).

     由 *note -d: 1c33. 選項與 *note PYTHONDEBUG: 1c34. 環境變數設定。

     Deprecated since version 3.12, will be removed in version 3.14.

 -- C 變數: int Py_DontWriteBytecodeFlag

     This API is kept for backward compatibility: setting *note
     PyConfig.write_bytecode: 3a6. should be used instead, see *note
     Python Initialization Configuration: 372.

     If set to non-zero, Python won't try to write ‘.pyc’ files on the
     import of source modules.

     由 *note -B: 133b. 選項與 *note PYTHONDONTWRITEBYTECODE: 133c. 環境
     變數設定。

     Deprecated since version 3.12, will be removed in version 3.14.

 -- C 變數: int Py_FrozenFlag

     This API is kept for backward compatibility: setting *note
     PyConfig.pathconfig_warnings: 3a2. should be used instead, see
     *note Python Initialization Configuration: 372.

     Suppress error messages when calculating the module search path in
     *note Py_GetPath(): 37e.

     Private flag used by ‘_freeze_module’ and ‘frozenmain’ programs.

     Deprecated since version 3.12, will be removed in version 3.14.

 -- C 變數: int Py_HashRandomizationFlag

     This API is kept for backward compatibility: setting *note
     PyConfig.hash_seed: 3ad. and *note PyConfig.use_hash_seed: 3ac.
     should be used instead, see *note Python Initialization
     Configuration: 372.

     如果環境變數 *note PYTHONHASHSEED: 101e. 被設定為一個非空字串則設為
     ‘1’。

     If the flag is non-zero, read the *note PYTHONHASHSEED: 101e.
     environment variable to initialize the secret hash seed.

     Deprecated since version 3.12, will be removed in version 3.14.

 -- C 變數: int Py_IgnoreEnvironmentFlag

     This API is kept for backward compatibility: setting *note
     PyConfig.use_environment: 3a4. should be used instead, see *note
     Python Initialization Configuration: 372.

     忽略所有可能被設定的 ‘PYTHON*’ 環境變數，例如 *note PYTHONPATH:
     fbe. 與 *note PYTHONHOME: 387.。

     由 *note -E: 901. 與 *note -I: 902. 選項設定。

     Deprecated since version 3.12, will be removed in version 3.14.

 -- C 變數: int Py_InspectFlag

     This API is kept for backward compatibility: setting *note
     PyConfig.inspect: 39a. should be used instead, see *note Python
     Initialization Configuration: 372.

     When a script is passed as first argument or the *note -c: 584.
     option is used, enter interactive mode after executing the script
     or the command, even when *note sys.stdin: 4e2. does not appear to
     be a terminal.

     由 *note -i: 144a. 選項與 *note PYTHONINSPECT: 1449. 環境變數設定。

     Deprecated since version 3.12, will be removed in version 3.14.

 -- C 變數: int Py_InteractiveFlag

     This API is kept for backward compatibility: setting *note
     PyConfig.interactive: 398. should be used instead, see *note Python
     Initialization Configuration: 372.

     由 *note -i: 144a. 選項設定。

     在 3.12 版之後被棄用.

 -- C 變數: int Py_IsolatedFlag

     This API is kept for backward compatibility: setting *note
     PyConfig.isolated: 3af. should be used instead, see *note Python
     Initialization Configuration: 372.

     Run Python in isolated mode.  In isolated mode *note sys.path: 37f.
     contains neither the script's directory nor the user's
     site-packages directory.

     由 *note -i: 144a. 選項設定。

     在 3.4 版被加入.

     Deprecated since version 3.12, will be removed in version 3.14.

 -- C 變數: int Py_LegacyWindowsFSEncodingFlag

     This API is kept for backward compatibility: setting *note
     PyPreConfig.legacy_windows_fs_encoding: 3b1. should be used
     instead, see *note Python Initialization Configuration: 372.

     If the flag is non-zero, use the ‘mbcs’ encoding with ‘replace’
     error handler, instead of the UTF-8 encoding with ‘surrogatepass’
     error handler, for the *note filesystem encoding and error handler:
     4e0.

     如果環境變數 *note PYTHONLEGACYWINDOWSFSENCODING: 28f. 被設定為一個
     非空字串則設為 ‘1’。

     更多詳情請見 PEP 529(1)。

     *note 適用: 1c56.：Windows。

     Deprecated since version 3.12, will be removed in version 3.14.

 -- C 變數: int Py_LegacyWindowsStdioFlag

     This API is kept for backward compatibility: setting *note
     PyConfig.legacy_windows_stdio: 36f. should be used instead, see
     *note Python Initialization Configuration: 372.

     If the flag is non-zero, use *note io.FileIO: 12a4. instead of
     ‘io._WindowsConsoleIO’ for *note sys: c3. standard streams.

     Set to ‘1’ if the *note PYTHONLEGACYWINDOWSSTDIO: c02. environment
     variable is set to a non-empty string.

     更多詳情請見 PEP 528(2)。

     *note 適用: 1c56.：Windows。

     Deprecated since version 3.12, will be removed in version 3.14.

 -- C 變數: int Py_NoSiteFlag

     This API is kept for backward compatibility: setting *note
     PyConfig.site_import: 39e. should be used instead, see *note Python
     Initialization Configuration: 372.

     Disable the import of the module *note site: b5. and the
     site-dependent manipulations of *note sys.path: 37f. that it
     entails.  Also disable these manipulations if *note site: b5. is
     explicitly imported later (call *note site.main(): 1c38. if you
     want them to be triggered).

     由 *note -S: 1140. 選項設定。

     Deprecated since version 3.12, will be removed in version 3.14.

 -- C 變數: int Py_NoUserSiteDirectory

     This API is kept for backward compatibility: setting *note
     PyConfig.user_site_directory: 3a8. should be used instead, see
     *note Python Initialization Configuration: 372.

     Don't add the *note user site-packages directory: 1c37. to *note
     sys.path: 37f.

     由 *note -s: 1319. 選項、*note -I: 902. 選項與 *note
     PYTHONNOUSERSITE: 131a. 環境變數設定。

     Deprecated since version 3.12, will be removed in version 3.14.

 -- C 變數: int Py_OptimizeFlag

     This API is kept for backward compatibility: setting *note
     PyConfig.optimization_level: 39c. should be used instead, see *note
     Python Initialization Configuration: 372.

     由 *note -O: d5b. 選項與 *note PYTHONOPTIMIZE: 1c35. 環境變數設定。

     Deprecated since version 3.12, will be removed in version 3.14.

 -- C 變數: int Py_QuietFlag

     This API is kept for backward compatibility: setting *note
     PyConfig.quiet: 396. should be used instead, see *note Python
     Initialization Configuration: 372.

     Don't display the copyright and version messages even in
     interactive mode.

     由 *note -q: 1c36. 選項設定。

     在 3.2 版被加入.

     Deprecated since version 3.12, will be removed in version 3.14.

 -- C 變數: int Py_UnbufferedStdioFlag

     This API is kept for backward compatibility: setting *note
     PyConfig.buffered_stdio: 3aa. should be used instead, see *note
     Python Initialization Configuration: 372.

     Force the stdout and stderr streams to be unbuffered.

     由 *note -u: 18a8. 選項與 *note PYTHONUNBUFFERED: 18a9. 環境變數設
     定。

     Deprecated since version 3.12, will be removed in version 3.14.

 -- C 變數: int Py_VerboseFlag

     This API is kept for backward compatibility: setting *note
     PyConfig.verbose: 394. should be used instead, see *note Python
     Initialization Configuration: 372.

     Print a message each time a module is initialized, showing the
     place (filename or built-in module) from which it is loaded.  If
     greater or equal to ‘2’, print a message for each file that is
     checked for when searching for a module.  Also provides information
     on module cleanup at exit.

     由 *note -v: 1392. 選項與 *note PYTHONVERBOSE: 1c39. 環境變數設定。

     Deprecated since version 3.12, will be removed in version 3.14.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0529/

   (2) https://peps.python.org/pep-0528/


File: python.info,  Node: Initializing and finalizing the interpreter,  Next: Process-wide parameters,  Prev: Global configuration variables,  Up: Initialization Finalization and Threads

7.9.3 Initializing and finalizing the interpreter
-------------------------------------------------

 -- C 函式: void Py_Initialize ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     Initialize the Python interpreter.  In an application embedding
     Python, this should be called before using any other Python/C API
     functions; see *note Before Python Initialization: b6c. for the few
     exceptions.

     This initializes the table of loaded modules (‘sys.modules’), and
     creates the fundamental modules *note builtins: e, *note __main__:
     1. and *note sys: c3.  It also initializes the module search path
     (‘sys.path’).  It does not set ‘sys.argv’; use the new *note
     PyConfig: 371. API of the *note Python Initialization
     Configuration: 372. for that.  This is a no-op when called for a
     second time (without calling *note Py_FinalizeEx(): cbc. first).
     There is no return value; it is a fatal error if the initialization
     fails.

     Use the *note Py_InitializeFromConfig(): 390. function to customize
     the *note Python Initialization Configuration: 372.

          備註: On Windows, changes the console mode from ‘O_TEXT’ to
          ‘O_BINARY’, which will also affect non-Python uses of the
          console using the C Runtime.

 -- C 函式: void Py_InitializeEx (int initsigs)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This function works like *note
     Py_Initialize(): 851. if 'initsigs' is ‘1’.  If 'initsigs' is ‘0’,
     it skips initialization registration of signal handlers, which
     might be useful when Python is embedded.

     Use the *note Py_InitializeFromConfig(): 390. function to customize
     the *note Python Initialization Configuration: 372.

 -- C 函式: int Py_IsInitialized ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return true (nonzero) when the
     Python interpreter has been initialized, false (zero) if not.
     After *note Py_FinalizeEx(): cbc. is called, this returns false
     until *note Py_Initialize(): 851. is called again.

 -- C 函式: int Py_IsFinalizing ()
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Return true
     (non-zero) if the main Python interpreter is *note shutting down:
     133.  Return false (zero) otherwise.

     在 3.13 版被加入.

 -- C 函式: int Py_FinalizeEx ()
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.6 版本開始.'  Undo all
     initializations made by *note Py_Initialize(): 851. and subsequent
     use of Python/C API functions, and destroy all sub-interpreters
     (see *note Py_NewInterpreter(): 16b9. below) that were created and
     not yet destroyed since the last call to *note Py_Initialize():
     851.  Ideally, this frees all memory allocated by the Python
     interpreter.  This is a no-op when called for a second time
     (without calling *note Py_Initialize(): 851. again first).

     Since this is the reverse of *note Py_Initialize(): 851, it should
     be called in the same thread with the same interpreter active.
     That means the main thread and the main interpreter.  This should
     never be called while *note Py_RunMain(): 969. is running.

     Normally the return value is ‘0’.  If there were errors during
     finalization (flushing buffered data), ‘-1’ is returned.

     This function is provided for a number of reasons.  An embedding
     application might want to restart Python without having to restart
     the application itself.  An application that has loaded the Python
     interpreter from a dynamically loadable library (or DLL) might want
     to free all memory allocated by Python before unloading the DLL.
     During a hunt for memory leaks in an application a developer might
     want to free all memory allocated by Python before exiting from the
     application.

     'Bugs and caveats:' The destruction of modules and objects in
     modules is done in random order; this may cause destructors (*note
     __del__(): 1e36. methods) to fail when they depend on other objects
     (even functions) or modules.  Dynamically loaded extension modules
     loaded by Python are not unloaded.  Small amounts of memory
     allocated by the Python interpreter may not be freed (if you find a
     leak, please report it).  Memory tied up in circular references
     between objects is not freed.  Some memory allocated by extension
     modules may not be freed.  Some extensions may not work properly if
     their initialization routine is called more than once; this can
     happen if an application calls *note Py_Initialize(): 851. and
     *note Py_FinalizeEx(): cbc. more than once.

     引發一個不附帶引數的*note 稽核事件: 17bd.
     ‘cpython._PySys_ClearAuditHooks’。

     在 3.6 版被加入.

 -- C 函式: void Py_Finalize ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This is a backwards-compatible
     version of *note Py_FinalizeEx(): cbc. that disregards the return
     value.


File: python.info,  Node: Process-wide parameters,  Next: Thread State and the Global Interpreter Lock,  Prev: Initializing and finalizing the interpreter,  Up: Initialization Finalization and Threads

7.9.4 Process-wide parameters
-----------------------------

 -- C 函式: void Py_SetProgramName (const wchar_t *name)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     This API is kept for backward compatibility: setting *note
     PyConfig.program_name: 38f. should be used instead, see *note
     Python Initialization Configuration: 372.

     This function should be called before *note Py_Initialize(): 851.
     is called for the first time, if it is called at all.  It tells the
     interpreter the value of the ‘argv[0]’ argument to the ‘main()’
     function of the program (converted to wide characters).  This is
     used by *note Py_GetPath(): 37e. and some other functions below to
     find the Python run-time libraries relative to the interpreter
     executable.  The default value is ‘'python'’.  The argument should
     point to a zero-terminated wide character string in static storage
     whose contents will not change for the duration of the program's
     execution.  No code in the Python interpreter will change the
     contents of this storage.

     Use *note Py_DecodeLocale(): b6e. to decode a bytes string to get a
     wchar_* string.

     在 3.11 版之後被棄用.

 -- C 函式: wchar_t *Py_GetProgramName ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the program name set
     with *note PyConfig.program_name: 38f, or the default.  The
     returned string points into static storage; the caller should not
     modify its value.

     此函式不應該在 *note Py_Initialize(): 851. 之前呼叫，否則會回傳
     ‘NULL’。

     在 3.10 版的變更: 如果在 *note Py_Initialize(): 851. 之前呼叫，現在
     會回傳 ‘NULL’。

     Deprecated since version 3.13, will be removed in version 3.15: Get
     *note sys.executable: 383. instead.

 -- C 函式: wchar_t *Py_GetPrefix ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the 'prefix' for
     installed platform-independent files.  This is derived through a
     number of complicated rules from the program name set with *note
     PyConfig.program_name: 38f. and some environment variables; for
     example, if the program name is ‘'/usr/local/bin/python'’, the
     prefix is ‘'/usr/local'’.  The returned string points into static
     storage; the caller should not modify its value.  This corresponds
     to the ‘prefix’ variable in the top-level ‘Makefile’ and the *note
     -prefix: 1c62. argument to the ‘configure’ script at build time.
     The value is available to Python code as ‘sys.prefix’.  It is only
     useful on Unix.  See also the next function.

     此函式不應該在 *note Py_Initialize(): 851. 之前呼叫，否則會回傳
     ‘NULL’。

     在 3.10 版的變更: 如果在 *note Py_Initialize(): 851. 之前呼叫，現在
     會回傳 ‘NULL’。

     Deprecated since version 3.13, will be removed in version 3.15: Get
     *note sys.prefix: 381. instead.

 -- C 函式: wchar_t *Py_GetExecPrefix ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the 'exec-prefix' for
     installed platform-'dependent' files.  This is derived through a
     number of complicated rules from the program name set with *note
     PyConfig.program_name: 38f. and some environment variables; for
     example, if the program name is ‘'/usr/local/bin/python'’, the
     exec-prefix is ‘'/usr/local'’.  The returned string points into
     static storage; the caller should not modify its value.  This
     corresponds to the ‘exec_prefix’ variable in the top-level
     ‘Makefile’ and the ‘--exec-prefix’ argument to the ‘configure’
     script at build time.  The value is available to Python code as
     ‘sys.exec_prefix’.  It is only useful on Unix.

     Background: The exec-prefix differs from the prefix when platform
     dependent files (such as executables and shared libraries) are
     installed in a different directory tree.  In a typical
     installation, platform dependent files may be installed in the
     ‘/usr/local/plat’ subtree while platform independent may be
     installed in ‘/usr/local’.

     Generally speaking, a platform is a combination of hardware and
     software families, e.g.  Sparc machines running the Solaris 2.x
     operating system are considered the same platform, but Intel
     machines running Solaris 2.x are another platform, and Intel
     machines running Linux are yet another platform.  Different major
     revisions of the same operating system generally also form
     different platforms.  Non-Unix operating systems are a different
     story; the installation strategies on those systems are so
     different that the prefix and exec-prefix are meaningless, and set
     to the empty string.  Note that compiled Python bytecode files are
     platform independent (but not independent from the Python version
     by which they were compiled!).

     System administrators will know how to configure the ‘mount’ or
     ‘automount’ programs to share ‘/usr/local’ between platforms while
     having ‘/usr/local/plat’ be a different filesystem for each
     platform.

     此函式不應該在 *note Py_Initialize(): 851. 之前呼叫，否則會回傳
     ‘NULL’。

     在 3.10 版的變更: 如果在 *note Py_Initialize(): 851. 之前呼叫，現在
     會回傳 ‘NULL’。

     Deprecated since version 3.13, will be removed in version 3.15: Get
     *note sys.exec_prefix: 37d. instead.

 -- C 函式: wchar_t *Py_GetProgramFullPath ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     Return the full program name of the Python executable; this is
     computed as a side-effect of deriving the default module search
     path from the program name (set by *note PyConfig.program_name:
     38f.).  The returned string points into static storage; the caller
     should not modify its value.  The value is available to Python code
     as ‘sys.executable’.

     此函式不應該在 *note Py_Initialize(): 851. 之前呼叫，否則會回傳
     ‘NULL’。

     在 3.10 版的變更: 如果在 *note Py_Initialize(): 851. 之前呼叫，現在
     會回傳 ‘NULL’。

     Deprecated since version 3.13, will be removed in version 3.15: Get
     *note sys.executable: 383. instead.

 -- C 函式: wchar_t *Py_GetPath ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     Return the default module search path; this is computed from the
     program name (set by *note PyConfig.program_name: 38f.) and some
     environment variables.  The returned string consists of a series of
     directory names separated by a platform dependent delimiter
     character.  The delimiter character is ‘':'’ on Unix and macOS,
     ‘';'’ on Windows.  The returned string points into static storage;
     the caller should not modify its value.  The list *note sys.path:
     37f. is initialized with this value on interpreter startup; it can
     be (and usually is) modified later to change the search path for
     loading modules.

     此函式不應該在 *note Py_Initialize(): 851. 之前呼叫，否則會回傳
     ‘NULL’。

     在 3.10 版的變更: 如果在 *note Py_Initialize(): 851. 之前呼叫，現在
     會回傳 ‘NULL’。

     Deprecated since version 3.13, will be removed in version 3.15: Get
     *note sys.path: 37f. instead.

 -- C 函式: const char *Py_GetVersion ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the version of this
     Python interpreter.  This is a string that looks something like

          "3.0a5+ (py3k:63103M, May 12 2008, 00:53:55) \n[GCC 4.2.3]"

     The first word (up to the first space character) is the current
     Python version; the first characters are the major and minor
     version separated by a period.  The returned string points into
     static storage; the caller should not modify its value.  The value
     is available to Python code as *note sys.version: 15c.

     See also the *note Py_Version: 6fa. constant.

 -- C 函式: const char *Py_GetPlatform ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     Return the platform identifier for the current platform.  On Unix,
     this is formed from the "official" name of the operating system,
     converted to lower case, followed by the major revision number;
     e.g., for Solaris 2.x, which is also known as SunOS 5.x, the value
     is ‘'sunos5'’.  On macOS, it is ‘'darwin'’.  On Windows, it is
     ‘'win'’.  The returned string points into static storage; the
     caller should not modify its value.  The value is available to
     Python code as ‘sys.platform’.

 -- C 函式: const char *Py_GetCopyright ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the official copyright
     string for the current Python version, for example

     ‘'Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam'’

     The returned string points into static storage; the caller should
     not modify its value.  The value is available to Python code as
     ‘sys.copyright’.

 -- C 函式: const char *Py_GetCompiler ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return an indication of the
     compiler used to build the current Python version, in square
     brackets, for example:

          "[GCC 2.7.2.2]"

     The returned string points into static storage; the caller should
     not modify its value.  The value is available to Python code as
     part of the variable ‘sys.version’.

 -- C 函式: const char *Py_GetBuildInfo ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return information about the
     sequence number and build date and time of the current Python
     interpreter instance, for example

          "#67, Aug  1 1997, 22:34:28"

     The returned string points into static storage; the caller should
     not modify its value.  The value is available to Python code as
     part of the variable ‘sys.version’.

 -- C 函式: void PySys_SetArgvEx (int argc, wchar_t **argv, int
          updatepath)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     This API is kept for backward compatibility: setting *note
     PyConfig.argv: 38e, *note PyConfig.parse_argv: 182b. and *note
     PyConfig.safe_path: 717. should be used instead, see *note Python
     Initialization Configuration: 372.

     Set *note sys.argv: 11fd. based on 'argc' and 'argv'.  These
     parameters are similar to those passed to the program's ‘main()’
     function with the difference that the first entry should refer to
     the script file to be executed rather than the executable hosting
     the Python interpreter.  If there isn't a script that will be run,
     the first entry in 'argv' can be an empty string.  If this function
     fails to initialize *note sys.argv: 11fd, a fatal condition is
     signalled using *note Py_FatalError(): 927.

     If 'updatepath' is zero, this is all the function does.  If
     'updatepath' is non-zero, the function also modifies *note
     sys.path: 37f. according to the following algorithm:

        - If the name of an existing script is passed in ‘argv[0]’, the
          absolute path of the directory where the script is located is
          prepended to *note sys.path: 37f.

        - Otherwise (that is, if 'argc' is ‘0’ or ‘argv[0]’ doesn't
          point to an existing file name), an empty string is prepended
          to *note sys.path: 37f, which is the same as prepending the
          current working directory (‘"."’).

     Use *note Py_DecodeLocale(): b6e. to decode a bytes string to get a
     wchar_* string.

     See also *note PyConfig.orig_argv: 838. and *note PyConfig.argv:
     38e. members of the *note Python Initialization Configuration: 372.

          備註: It is recommended that applications embedding the Python
          interpreter for purposes other than executing a single script
          pass ‘0’ as 'updatepath', and update *note sys.path: 37f.
          themselves if desired.  See CVE-2008-5983(1).

          On versions before 3.1.3, you can achieve the same effect by
          manually popping the first *note sys.path: 37f. element after
          having called *note PySys_SetArgv(): 1534, for example using:

               PyRun_SimpleString("import sys; sys.path.pop(0)\n");

     在 3.1.3 版被加入.

     在 3.11 版之後被棄用.

 -- C 函式: void PySys_SetArgv (int argc, wchar_t **argv)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This API is kept for backward
     compatibility: setting *note PyConfig.argv: 38e. and *note
     PyConfig.parse_argv: 182b. should be used instead, see *note Python
     Initialization Configuration: 372.

     This function works like *note PySys_SetArgvEx(): 1533. with
     'updatepath' set to ‘1’ unless the ‘python’ interpreter was started
     with the *note -I: 902.

     Use *note Py_DecodeLocale(): b6e. to decode a bytes string to get a
     wchar_* string.

     See also *note PyConfig.orig_argv: 838. and *note PyConfig.argv:
     38e. members of the *note Python Initialization Configuration: 372.

     在 3.4 版的變更: The 'updatepath' value depends on *note -I: 902.

     在 3.11 版之後被棄用.

 -- C 函式: void Py_SetPythonHome (const wchar_t *home)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This API is kept for backward
     compatibility: setting *note PyConfig.home: 386. should be used
     instead, see *note Python Initialization Configuration: 372.

     Set the default "home" directory, that is, the location of the
     standard Python libraries.  See *note PYTHONHOME: 387. for the
     meaning of the argument string.

     The argument should point to a zero-terminated character string in
     static storage whose contents will not change for the duration of
     the program's execution.  No code in the Python interpreter will
     change the contents of this storage.

     Use *note Py_DecodeLocale(): b6e. to decode a bytes string to get a
     wchar_* string.

     在 3.11 版之後被棄用.

 -- C 函式: wchar_t *Py_GetPythonHome ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the default "home",
     that is, the value set by *note PyConfig.home: 386, or the value of
     the *note PYTHONHOME: 387. environment variable if it is set.

     此函式不應該在 *note Py_Initialize(): 851. 之前呼叫，否則會回傳
     ‘NULL’。

     在 3.10 版的變更: 如果在 *note Py_Initialize(): 851. 之前呼叫，現在
     會回傳 ‘NULL’。

     Deprecated since version 3.13, will be removed in version 3.15: Get
     *note PyConfig.home: 386. or *note PYTHONHOME: 387. environment
     variable instead.

   ---------- Footnotes ----------

   (1) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5983


File: python.info,  Node: Thread State and the Global Interpreter Lock,  Next: Sub-interpreter support,  Prev: Process-wide parameters,  Up: Initialization Finalization and Threads

7.9.5 Thread State and the Global Interpreter Lock
--------------------------------------------------

The Python interpreter is not fully thread-safe.  In order to support
multi-threaded Python programs, there's a global lock, called the *note
global interpreter lock: 12e. or *note GIL: 13e, that must be held by
the current thread before it can safely access Python objects.  Without
the lock, even the simplest operations could cause problems in a
multi-threaded program: for example, when two threads simultaneously
increment the reference count of the same object, the reference count
could end up being incremented only once instead of twice.

Therefore, the rule exists that only the thread that has acquired the
*note GIL: 13e. may operate on Python objects or call Python/C API
functions.  In order to emulate concurrency of execution, the
interpreter regularly tries to switch threads (see *note
sys.setswitchinterval(): 8ee.).  The lock is also released around
potentially blocking I/O operations like reading or writing a file, so
that other Python threads can run in the meantime.

The Python interpreter keeps some thread-specific bookkeeping
information inside a data structure called *note PyThreadState: 731.
There's also one global variable pointing to the current *note
PyThreadState: 731.: it can be retrieved using *note
PyThreadState_Get(): 31f.

* Menu:

* Releasing the GIL from extension code::
* Non-Python created threads::
* Cautions about fork(): Cautions about fork.
* 高階 API::
* 低階 API::


File: python.info,  Node: Releasing the GIL from extension code,  Next: Non-Python created threads,  Up: Thread State and the Global Interpreter Lock

7.9.5.1 Releasing the GIL from extension code
.............................................

Most extension code manipulating the *note GIL: 13e. has the following
simple structure:

     Save the thread state in a local variable.
     Release the global interpreter lock.
     ... Do some blocking I/O operation ...
     Reacquire the global interpreter lock.
     Restore the thread state from the local variable.

This is so common that a pair of macros exists to simplify it:

     Py_BEGIN_ALLOW_THREADS
     ... Do some blocking I/O operation ...
     Py_END_ALLOW_THREADS

The *note Py_BEGIN_ALLOW_THREADS: 46f3. macro opens a new block and
declares a hidden local variable; the *note Py_END_ALLOW_THREADS: a31.
macro closes the block.

The block above expands to the following code:

     PyThreadState *_save;

     _save = PyEval_SaveThread();
     ... Do some blocking I/O operation ...
     PyEval_RestoreThread(_save);

Here is how these functions work: the global interpreter lock is used to
protect the pointer to the current thread state.  When releasing the
lock and saving the thread state, the current thread state pointer must
be retrieved before the lock is released (since another thread could
immediately acquire the lock and store its own thread state in the
global variable).  Conversely, when acquiring the lock and restoring the
thread state, the lock must be acquired before storing the thread state
pointer.

     備註: Calling system I/O functions is the most common use case for
     releasing the GIL, but it can also be useful before calling
     long-running computations which don't need access to Python
     objects, such as compression or cryptographic functions operating
     over memory buffers.  For example, the standard *note zlib: 119.
     and *note hashlib: 5e. modules release the GIL when compressing or
     hashing data.


File: python.info,  Node: Non-Python created threads,  Next: Cautions about fork,  Prev: Releasing the GIL from extension code,  Up: Thread State and the Global Interpreter Lock

7.9.5.2 Non-Python created threads
..................................

When threads are created using the dedicated Python APIs (such as the
*note threading: d6. module), a thread state is automatically associated
to them and the code showed above is therefore correct.  However, when
threads are created from C (for example by a third-party library with
its own thread management), they don't hold the GIL, nor is there a
thread state structure for them.

If you need to call Python code from these threads (often this will be
part of a callback API provided by the aforementioned third-party
library), you must first register these threads with the interpreter by
creating a thread state data structure, then acquiring the GIL, and
finally storing their thread state pointer, before you can start using
the Python/C API. When you are done, you should reset the thread state
pointer, release the GIL, and finally free the thread state data
structure.

The *note PyGILState_Ensure(): 376. and *note PyGILState_Release(): 377.
functions do all of the above automatically.  The typical idiom for
calling into Python from a C thread is:

     PyGILState_STATE gstate;
     gstate = PyGILState_Ensure();

     /* Perform Python actions here. */
     result = CallSomeFunction();
     /* evaluate result or handle exception */

     /* Release the thread. No Python API allowed beyond this point. */
     PyGILState_Release(gstate);

Note that the ‘PyGILState_*’ functions assume there is only one global
interpreter (created automatically by *note Py_Initialize(): 851.).
Python supports the creation of additional interpreters (using *note
Py_NewInterpreter(): 16b9.), but mixing multiple interpreters and the
‘PyGILState_*’ API is unsupported.


File: python.info,  Node: Cautions about fork,  Next: 高階 API,  Prev: Non-Python created threads,  Up: Thread State and the Global Interpreter Lock

7.9.5.3 Cautions about fork()
.............................

Another important thing to note about threads is their behaviour in the
face of the C ‘fork()’ call.  On most systems with ‘fork()’, after a
process forks only the thread that issued the fork will exist.  This has
a concrete impact both on how locks must be handled and on all stored
state in CPython's runtime.

The fact that only the "current" thread remains means any locks held by
other threads will never be released.  Python solves this for *note
os.fork(): 17b. by acquiring the locks it uses internally before the
fork, and releasing them afterwards.  In addition, it resets any *note
Lock Objects: 2f40. in the child.  When extending or embedding Python,
there is no way to inform Python of additional (non-Python) locks that
need to be acquired before or reset after a fork.  OS facilities such as
‘pthread_atfork()’ would need to be used to accomplish the same thing.
Additionally, when extending or embedding Python, calling ‘fork()’
directly rather than through *note os.fork(): 17b. (and returning to or
calling into Python) may result in a deadlock by one of Python's
internal locks being held by a thread that is defunct after the fork.
*note PyOS_AfterFork_Child(): 3c3. tries to reset the necessary locks,
but is not always able to.

The fact that all other threads go away also means that CPython's
runtime state there must be cleaned up properly, which *note os.fork():
17b. does.  This means finalizing all other *note PyThreadState: 731.
objects belonging to the current interpreter and all other *note
PyInterpreterState: 862. objects.  Due to this and the special nature of
the *note "main" interpreter: 52d, ‘fork()’ should only be called in
that interpreter's "main" thread, where the CPython global runtime was
originally initialized.  The only exception is if ‘exec()’ will be
called immediately after.


File: python.info,  Node: 高階 API,  Next: 低階 API,  Prev: Cautions about fork,  Up: Thread State and the Global Interpreter Lock

7.9.5.4 高階 API
................

These are the most commonly used types and functions when writing C
extension code, or when embedding the Python interpreter:

 -- C 型別: type PyInterpreterState
     ' 為 *note 受限 API 的一部分: 4f9. （做為一個不透明結構 (opaque
     struct)）.'  This data structure represents the state shared by a
     number of cooperating threads.  Threads belonging to the same
     interpreter share their module administration and a few other
     internal items.  There are no public members in this structure.

     Threads belonging to different interpreters initially share
     nothing, except process state like available memory, open file
     descriptors and such.  The global interpreter lock is also shared
     by all threads, regardless of to which interpreter they belong.

 -- C 型別: type PyThreadState
     ' 為 *note 受限 API 的一部分: 4f9. （做為一個不透明結構 (opaque
     struct)）.'  This data structure represents the state of a single
     thread.  The only public data member is:

      -- C 成員函數: *note PyInterpreterState: 862. *interp

          This thread's interpreter state.

 -- C 函式: void PyEval_InitThreads ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     Deprecated function which does nothing.

     In Python 3.6 and older, this function created the GIL if it didn't
     exist.

     在 3.9 版的變更: 此函式現在不會做任何事情。

     在 3.7 版的變更: This function is now called by *note
     Py_Initialize(): 851, so you don't have to call it yourself
     anymore.

     在 3.2 版的變更: This function cannot be called before *note
     Py_Initialize(): 851. anymore.

     在 3.9 版之後被棄用.

 -- C 函式: *note PyThreadState: 731. *PyEval_SaveThread ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Release the global interpreter
     lock (if it has been created) and reset the thread state to ‘NULL’,
     returning the previous thread state (which is not ‘NULL’).  If the
     lock has been created, the current thread must have acquired it.

 -- C 函式: void PyEval_RestoreThread (PyThreadState *tstate)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Acquire the global interpreter
     lock (if it has been created) and set the thread state to 'tstate',
     which must not be ‘NULL’.  If the lock has been created, the
     current thread must not have acquired it, otherwise deadlock
     ensues.

          備註: Calling this function from a thread when the runtime is
          finalizing will terminate the thread, even if the thread was
          not created by Python.  You can use *note Py_IsFinalizing():
          314. or *note sys.is_finalizing(): a32. to check if the
          interpreter is in process of being finalized before calling
          this function to avoid unwanted termination.

 -- C 函式: *note PyThreadState: 731. *PyThreadState_Get ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the current thread
     state.  The global interpreter lock must be held.  When the current
     thread state is ‘NULL’, this issues a fatal error (so that the
     caller needn't check for ‘NULL’).

     See also *note PyThreadState_GetUnchecked(): 31e.

 -- C 函式: *note PyThreadState: 731. *PyThreadState_GetUnchecked ()

     Similar to *note PyThreadState_Get(): 31f, but don't kill the
     process with a fatal error if it is NULL. The caller is responsible
     to check if the result is NULL.

     在 3.13 版被加入: In Python 3.5 to 3.12, the function was private
     and known as ‘_PyThreadState_UncheckedGet()’.

 -- C 函式: *note PyThreadState: 731. *PyThreadState_Swap (PyThreadState
          *tstate)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Swap the current thread state
     with the thread state given by the argument 'tstate', which may be
     ‘NULL’.  The global interpreter lock must be held and is not
     released.

The following functions use thread-local storage, and are not compatible
with sub-interpreters:

 -- C 函式: PyGILState_STATE PyGILState_Ensure ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Ensure that the current thread
     is ready to call the Python C API regardless of the current state
     of Python, or of the global interpreter lock.  This may be called
     as many times as desired by a thread as long as each call is
     matched with a call to *note PyGILState_Release(): 377.  In
     general, other thread-related APIs may be used between *note
     PyGILState_Ensure(): 376. and *note PyGILState_Release(): 377.
     calls as long as the thread state is restored to its previous state
     before the Release().  For example, normal usage of the *note
     Py_BEGIN_ALLOW_THREADS: 46f3. and *note Py_END_ALLOW_THREADS: a31.
     macros is acceptable.

     The return value is an opaque "handle" to the thread state when
     *note PyGILState_Ensure(): 376. was called, and must be passed to
     *note PyGILState_Release(): 377. to ensure Python is left in the
     same state.  Even though recursive calls are allowed, these handles
     'cannot' be shared - each unique call to *note PyGILState_Ensure():
     376. must save the handle for its call to *note
     PyGILState_Release(): 377.

     When the function returns, the current thread will hold the GIL and
     be able to call arbitrary Python code.  Failure is a fatal error.

          備註: Calling this function from a thread when the runtime is
          finalizing will terminate the thread, even if the thread was
          not created by Python.  You can use *note Py_IsFinalizing():
          314. or *note sys.is_finalizing(): a32. to check if the
          interpreter is in process of being finalized before calling
          this function to avoid unwanted termination.

 -- C 函式: void PyGILState_Release (PyGILState_STATE)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Release any resources
     previously acquired.  After this call, Python's state will be the
     same as it was prior to the corresponding *note
     PyGILState_Ensure(): 376. call (but generally this state will be
     unknown to the caller, hence the use of the GILState API).

     Every call to *note PyGILState_Ensure(): 376. must be matched by a
     call to *note PyGILState_Release(): 377. on the same thread.

 -- C 函式: *note PyThreadState: 731. *PyGILState_GetThisThreadState ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Get the current thread state
     for this thread.  May return ‘NULL’ if no GILState API has been
     used on the current thread.  Note that the main thread always has
     such a thread-state, even if no auto-thread-state call has been
     made on the main thread.  This is mainly a helper/diagnostic
     function.

 -- C 函式: int PyGILState_Check ()

     Return ‘1’ if the current thread is holding the GIL and ‘0’
     otherwise.  This function can be called from any thread at any
     time.  Only if it has had its Python thread state initialized and
     currently is holding the GIL will it return ‘1’.  This is mainly a
     helper/diagnostic function.  It can be useful for example in
     callback contexts or memory allocation functions when knowing that
     the GIL is locked can allow the caller to perform sensitive actions
     or otherwise behave differently.

     在 3.4 版被加入.

The following macros are normally used without a trailing semicolon;
look for example usage in the Python source distribution.

 -- C 巨集: Py_BEGIN_ALLOW_THREADS
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This macro expands to ‘{
     PyThreadState *_save; _save = PyEval_SaveThread();’.  Note that it
     contains an opening brace; it must be matched with a following
     *note Py_END_ALLOW_THREADS: a31. macro.  See above for further
     discussion of this macro.

 -- C 巨集: Py_END_ALLOW_THREADS
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This macro expands to
     ‘PyEval_RestoreThread(_save); }’.  Note that it contains a closing
     brace; it must be matched with an earlier *note
     Py_BEGIN_ALLOW_THREADS: 46f3. macro.  See above for further
     discussion of this macro.

 -- C 巨集: Py_BLOCK_THREADS
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This macro expands to
     ‘PyEval_RestoreThread(_save);’: it is equivalent to *note
     Py_END_ALLOW_THREADS: a31. without the closing brace.

 -- C 巨集: Py_UNBLOCK_THREADS
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This macro expands to ‘_save =
     PyEval_SaveThread();’: it is equivalent to *note
     Py_BEGIN_ALLOW_THREADS: 46f3. without the opening brace and
     variable declaration.


File: python.info,  Node: 低階 API,  Prev: 高階 API,  Up: Thread State and the Global Interpreter Lock

7.9.5.5 低階 API
................

All of the following functions must be called after *note
Py_Initialize(): 851.

在 3.7 版的變更: *note Py_Initialize(): 851. now initializes the *note
GIL: 13e.

 -- C 函式: *note PyInterpreterState: 862. *PyInterpreterState_New ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a new interpreter state
     object.  The global interpreter lock need not be held, but may be
     held if it is necessary to serialize calls to this function.

     引發一個不附帶引數的*note 稽核事件: 17bd.
     ‘cpython.PyInterpreterState_New’。

 -- C 函式: void PyInterpreterState_Clear (PyInterpreterState *interp)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Reset all information in an
     interpreter state object.  The global interpreter lock must be
     held.

     引發一個不附帶引數的*note 稽核事件: 17bd.
     ‘cpython.PyInterpreterState_Clear’。

 -- C 函式: void PyInterpreterState_Delete (PyInterpreterState *interp)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Destroy an interpreter state
     object.  The global interpreter lock need not be held.  The
     interpreter state must have been reset with a previous call to
     *note PyInterpreterState_Clear(): 3ff4.

 -- C 函式: *note PyThreadState: 731. *PyThreadState_New
          (PyInterpreterState *interp)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Create a new thread state
     object belonging to the given interpreter object.  The global
     interpreter lock need not be held, but may be held if it is
     necessary to serialize calls to this function.

 -- C 函式: void PyThreadState_Clear (PyThreadState *tstate)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Reset all information in a
     thread state object.  The global interpreter lock must be held.

     在 3.9 版的變更: This function now calls the
     ‘PyThreadState.on_delete’ callback.  Previously, that happened in
     *note PyThreadState_Delete(): 18a4.

 -- C 函式: void PyThreadState_Delete (PyThreadState *tstate)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Destroy a thread state object.
     The global interpreter lock need not be held.  The thread state
     must have been reset with a previous call to *note
     PyThreadState_Clear(): 1515.

 -- C 函式: void PyThreadState_DeleteCurrent (void)

     Destroy the current thread state and release the global interpreter
     lock.  Like *note PyThreadState_Delete(): 18a4, the global
     interpreter lock need not be held.  The thread state must have been
     reset with a previous call to *note PyThreadState_Clear(): 1515.

 -- C 函式: *note PyFrameObject: 72d. *PyThreadState_GetFrame
          (PyThreadState *tstate)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本開始.'  Get the
     current frame of the Python thread state 'tstate'.

     Return a *note strong reference: 2ee.  Return ‘NULL’ if no frame is
     currently executing.

     也請見 *note PyEval_GetFrame(): 16bf.。

     'tstate' 不可為 ‘NULL’。

     在 3.9 版被加入.

 -- C 函式: uint64_t PyThreadState_GetID (PyThreadState *tstate)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本開始.'  Get the
     unique thread state identifier of the Python thread state 'tstate'.

     'tstate' 不可為 ‘NULL’。

     在 3.9 版被加入.

 -- C 函式: *note PyInterpreterState: 862. *PyThreadState_GetInterpreter
          (PyThreadState *tstate)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本開始.'  Get the
     interpreter of the Python thread state 'tstate'.

     'tstate' 不可為 ‘NULL’。

     在 3.9 版被加入.

 -- C 函式: void PyThreadState_EnterTracing (PyThreadState *tstate)

     Suspend tracing and profiling in the Python thread state 'tstate'.

     Resume them using the *note PyThreadState_LeaveTracing(): 6f9.
     function.

     在 3.11 版被加入.

 -- C 函式: void PyThreadState_LeaveTracing (PyThreadState *tstate)

     Resume tracing and profiling in the Python thread state 'tstate'
     suspended by the *note PyThreadState_EnterTracing(): 6f8. function.

     See also *note PyEval_SetTrace(): 146c. and *note
     PyEval_SetProfile(): 146b. functions.

     在 3.11 版被加入.

 -- C 函式: *note PyInterpreterState: 862. *PyInterpreterState_Get
          (void)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.9 版本開始.'  Get the
     current interpreter.

     Issue a fatal error if there no current Python thread state or no
     current interpreter.  It cannot return NULL.

     The caller must hold the GIL.

     在 3.9 版被加入.

 -- C 函式: int64_t PyInterpreterState_GetID (PyInterpreterState
          *interp)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Return the
     interpreter's unique ID. If there was any error in doing so then
     ‘-1’ is returned and an error is set.

     The caller must hold the GIL.

     在 3.7 版被加入.

 -- C 函式: *note PyObject: 311. *PyInterpreterState_GetDict
          (PyInterpreterState *interp)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.8 版本開始.'  Return a
     dictionary in which interpreter-specific data may be stored.  If
     this function returns ‘NULL’ then no exception has been raised and
     the caller should assume no interpreter-specific dict is available.

     This is not a replacement for *note PyModule_GetState(): 924, which
     extensions should use to store interpreter-specific state
     information.

     在 3.8 版被加入.

 -- C 型別: typedef *note PyObject: 311. *(*_PyFrameEvalFunction)(*note
          PyThreadState: 731. *tstate, *note _PyInterpreterFrame: 4af8.
          *frame, int throwflag)

     Type of a frame evaluation function.

     The 'throwflag' parameter is used by the ‘throw()’ method of
     generators: if non-zero, handle the current exception.

     在 3.9 版的變更: The function now takes a 'tstate' parameter.

     在 3.11 版的變更: The 'frame' parameter changed from
     ‘PyFrameObject*’ to ‘_PyInterpreterFrame*’.

 -- C 函式: *note _PyFrameEvalFunction: 71a.
          _PyInterpreterState_GetEvalFrameFunc (PyInterpreterState
          *interp)

     Get the frame evaluation function.

     See the PEP 523(1) "Adding a frame evaluation API to CPython".

     在 3.9 版被加入.

 -- C 函式: void _PyInterpreterState_SetEvalFrameFunc
          (PyInterpreterState *interp, _PyFrameEvalFunction eval_frame)

     Set the frame evaluation function.

     See the PEP 523(2) "Adding a frame evaluation API to CPython".

     在 3.9 版被加入.

 -- C 函式: *note PyObject: 311. *PyThreadState_GetDict ()
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  Return a
     dictionary in which extensions can store thread-specific state
     information.  Each extension should use a unique key to use to
     store state in the dictionary.  It is okay to call this function
     when no current thread state is available.  If this function
     returns ‘NULL’, no exception has been raised and the caller should
     assume no current thread state is available.

 -- C 函式: int PyThreadState_SetAsyncExc (unsigned long id, PyObject
          *exc)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Asynchronously raise an
     exception in a thread.  The 'id' argument is the thread id of the
     target thread; 'exc' is the exception object to be raised.  This
     function does not steal any references to 'exc'.  To prevent naive
     misuse, you must write your own C extension to call this.  Must be
     called with the GIL held.  Returns the number of thread states
     modified; this is normally one, but will be zero if the thread id
     isn't found.  If 'exc' is ‘NULL’, the pending exception (if any)
     for the thread is cleared.  This raises no exceptions.

     在 3.7 版的變更: The type of the 'id' parameter changed from long
     to unsigned long.

 -- C 函式: void PyEval_AcquireThread (PyThreadState *tstate)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Acquire the global interpreter
     lock and set the current thread state to 'tstate', which must not
     be ‘NULL’.  The lock must have been created earlier.  If this
     thread already has the lock, deadlock ensues.

          備註: Calling this function from a thread when the runtime is
          finalizing will terminate the thread, even if the thread was
          not created by Python.  You can use *note Py_IsFinalizing():
          314. or *note sys.is_finalizing(): a32. to check if the
          interpreter is in process of being finalized before calling
          this function to avoid unwanted termination.

     在 3.8 版的變更: Updated to be consistent with *note
     PyEval_RestoreThread(): 374, *note Py_END_ALLOW_THREADS(): a31, and
     *note PyGILState_Ensure(): 376, and terminate the current thread if
     called while the interpreter is finalizing.

     *note PyEval_RestoreThread(): 374. is a higher-level function which
     is always available (even when threads have not been initialized).

 -- C 函式: void PyEval_ReleaseThread (PyThreadState *tstate)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Reset the current thread state
     to ‘NULL’ and release the global interpreter lock.  The lock must
     have been created earlier and must be held by the current thread.
     The 'tstate' argument, which must not be ‘NULL’, is only used to
     check that it represents the current thread state -- if it isn't, a
     fatal error is reported.

     *note PyEval_SaveThread(): 373. is a higher-level function which is
     always available (even when threads have not been initialized).

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0523/

   (2) https://peps.python.org/pep-0523/


File: python.info,  Node: Sub-interpreter support,  Next: Asynchronous Notifications,  Prev: Thread State and the Global Interpreter Lock,  Up: Initialization Finalization and Threads

7.9.6 Sub-interpreter support
-----------------------------

While in most uses, you will only embed a single Python interpreter,
there are cases where you need to create several independent
interpreters in the same process and perhaps even in the same thread.
Sub-interpreters allow you to do that.

The "main" interpreter is the first one created when the runtime
initializes.  It is usually the only Python interpreter in a process.
Unlike sub-interpreters, the main interpreter has unique process-global
responsibilities like signal handling.  It is also responsible for
execution during runtime initialization and is usually the active
interpreter during runtime finalization.  The *note
PyInterpreterState_Main(): 4b65. function returns a pointer to its
state.

You can switch between sub-interpreters using the *note
PyThreadState_Swap(): 486c. function.  You can create and destroy them
using the following functions:

 -- C 型別: type PyInterpreterConfig

     Structure containing most parameters to configure a
     sub-interpreter.  Its values are used only in *note
     Py_NewInterpreterFromConfig(): 402. and never modified by the
     runtime.

     在 3.12 版被加入.

     Structure fields:

      -- C 成員函數: int use_main_obmalloc

          If this is ‘0’ then the sub-interpreter will use its own
          "object" allocator state.  Otherwise it will use (share) the
          main interpreter's.

          If this is ‘0’ then *note check_multi_interp_extensions: 4b67.
          must be ‘1’ (non-zero).  If this is ‘1’ then *note gil: 4b68.
          must not be *note PyInterpreterConfig_OWN_GIL: 4b69.

      -- C 成員函數: int allow_fork

          If this is ‘0’ then the runtime will not support forking the
          process in any thread where the sub-interpreter is currently
          active.  Otherwise fork is unrestricted.

          Note that the *note subprocess: c1. module still works when
          fork is disallowed.

      -- C 成員函數: int allow_exec

          If this is ‘0’ then the runtime will not support replacing the
          current process via exec (e.g.  *note os.execv(): 2a04.) in
          any thread where the sub-interpreter is currently active.
          Otherwise exec is unrestricted.

          Note that the *note subprocess: c1. module still works when
          exec is disallowed.

      -- C 成員函數: int allow_threads

          If this is ‘0’ then the sub-interpreter's *note threading: d6.
          module won't create threads.  Otherwise threads are allowed.

      -- C 成員函數: int allow_daemon_threads

          If this is ‘0’ then the sub-interpreter's *note threading: d6.
          module won't create daemon threads.  Otherwise daemon threads
          are allowed (as long as *note allow_threads: 4b6c. is
          non-zero).

      -- C 成員函數: int check_multi_interp_extensions

          If this is ‘0’ then all extension modules may be imported,
          including legacy (single-phase init) modules, in any thread
          where the sub-interpreter is currently active.  Otherwise only
          multi-phase init extension modules (see PEP 489(1)) may be
          imported.  (Also see *note Py_mod_multiple_interpreters:
          4ace.)

          This must be ‘1’ (non-zero) if *note use_main_obmalloc: 4b66.
          is ‘0’.

      -- C 成員函數: int gil

          This determines the operation of the GIL for the
          sub-interpreter.  It may be one of the following:

           -- C 巨集: PyInterpreterConfig_DEFAULT_GIL

               Use the default selection (*note
               PyInterpreterConfig_SHARED_GIL: 4b6f.).

           -- C 巨集: PyInterpreterConfig_SHARED_GIL

               Use (share) the main interpreter's GIL.

           -- C 巨集: PyInterpreterConfig_OWN_GIL

               Use the sub-interpreter's own GIL.

          If this is *note PyInterpreterConfig_OWN_GIL: 4b69. then *note
          PyInterpreterConfig.use_main_obmalloc: 4b66. must be ‘0’.

 -- C 函式: *note PyStatus: 951. Py_NewInterpreterFromConfig
          (PyThreadState **tstate_p, const PyInterpreterConfig *config)

     Create a new sub-interpreter.  This is an (almost) totally separate
     environment for the execution of Python code.  In particular, the
     new interpreter has separate, independent versions of all imported
     modules, including the fundamental modules *note builtins: e, *note
     __main__: 1. and *note sys: c3.  The table of loaded modules
     (‘sys.modules’) and the module search path (‘sys.path’) are also
     separate.  The new environment has no ‘sys.argv’ variable.  It has
     new standard I/O stream file objects ‘sys.stdin’, ‘sys.stdout’ and
     ‘sys.stderr’ (however these refer to the same underlying file
     descriptors).

     The given 'config' controls the options with which the interpreter
     is initialized.

     Upon success, 'tstate_p' will be set to the first thread state
     created in the new sub-interpreter.  This thread state is made in
     the current thread state.  Note that no actual thread is created;
     see the discussion of thread states below.  If creation of the new
     interpreter is unsuccessful, 'tstate_p' is set to ‘NULL’; no
     exception is set since the exception state is stored in the current
     thread state and there may not be a current thread state.

     Like all other Python/C API functions, the global interpreter lock
     must be held before calling this function and is still held when it
     returns.  Likewise a current thread state must be set on entry.  On
     success, the returned thread state will be set as current.  If the
     sub-interpreter is created with its own GIL then the GIL of the
     calling interpreter will be released.  When the function returns,
     the new interpreter's GIL will be held by the current thread and
     the previously interpreter's GIL will remain released here.

     在 3.12 版被加入.

     Sub-interpreters are most effective when isolated from each other,
     with certain functionality restricted:

          PyInterpreterConfig config = {
              .use_main_obmalloc = 0,
              .allow_fork = 0,
              .allow_exec = 0,
              .allow_threads = 1,
              .allow_daemon_threads = 0,
              .check_multi_interp_extensions = 1,
              .gil = PyInterpreterConfig_OWN_GIL,
          };
          PyThreadState *tstate = Py_NewInterpreterFromConfig(&config);

     Note that the config is used only briefly and does not get
     modified.  During initialization the config's values are converted
     into various *note PyInterpreterState: 862. values.  A read-only
     copy of the config may be stored internally on the *note
     PyInterpreterState: 862.

     Extension modules are shared between (sub-)interpreters as follows:

        * For modules using multi-phase initialization, e.g.  *note
          PyModule_FromDefAndSpec(): e54, a separate module object is
          created and initialized for each interpreter.  Only C-level
          static and global variables are shared between these module
          objects.

        * For modules using single-phase initialization, e.g.  *note
          PyModule_Create(): 46da, the first time a particular extension
          is imported, it is initialized normally, and a (shallow) copy
          of its module's dictionary is squirreled away.  When the same
          extension is imported by another (sub-)interpreter, a new
          module is initialized and filled with the contents of this
          copy; the extension's ‘init’ function is not called.  Objects
          in the module's dictionary thus end up shared across
          (sub-)interpreters, which might cause unwanted behavior (see
          *note Bugs and caveats: 4b70. below).

          Note that this is different from what happens when an
          extension is imported after the interpreter has been
          completely re-initialized by calling *note Py_FinalizeEx():
          cbc. and *note Py_Initialize(): 851.; in that case, the
          extension's ‘initmodule’ function 'is' called again.  As with
          multi-phase initialization, this means that only C-level
          static and global variables are shared between these modules.

 -- C 函式: *note PyThreadState: 731. *Py_NewInterpreter (void)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     Create a new sub-interpreter.  This is essentially just a wrapper
     around *note Py_NewInterpreterFromConfig(): 402. with a config that
     preserves the existing behavior.  The result is an unisolated
     sub-interpreter that shares the main interpreter's GIL, allows
     fork/exec, allows daemon threads, and allows single-phase init
     modules.

 -- C 函式: void Py_EndInterpreter (PyThreadState *tstate)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

     Destroy the (sub-)interpreter represented by the given thread
     state.  The given thread state must be the current thread state.
     See the discussion of thread states below.  When the call returns,
     the current thread state is ‘NULL’.  All thread states associated
     with this interpreter are destroyed.  The global interpreter lock
     used by the target interpreter must be held before calling this
     function.  No GIL is held when it returns.

     *note Py_FinalizeEx(): cbc. will destroy all sub-interpreters that
     haven't been explicitly destroyed at that point.

* Menu:

* A Per-Interpreter GIL::
* Bugs and caveats::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0489/


File: python.info,  Node: A Per-Interpreter GIL,  Next: Bugs and caveats,  Up: Sub-interpreter support

7.9.6.1 A Per-Interpreter GIL
.............................

Using *note Py_NewInterpreterFromConfig(): 402. you can create a
sub-interpreter that is completely isolated from other interpreters,
including having its own GIL. The most important benefit of this
isolation is that such an interpreter can execute Python code without
being blocked by other interpreters or blocking any others.  Thus a
single Python process can truly take advantage of multiple CPU cores
when running Python code.  The isolation also encourages a different
approach to concurrency than that of just using threads.  (See PEP
554(1).)

Using an isolated interpreter requires vigilance in preserving that
isolation.  That especially means not sharing any objects or mutable
state without guarantees about thread-safety.  Even objects that are
otherwise immutable (e.g.  ‘None’, ‘(1, 5)’) can't normally be shared
because of the refcount.  One simple but less-efficient approach around
this is to use a global lock around all use of some state (or object).
Alternately, effectively immutable objects (like integers or strings)
can be made safe in spite of their refcounts by making them *note
immortal: 4190.  In fact, this has been done for the builtin singletons,
small integers, and a number of other builtin objects.

If you preserve isolation then you will have access to proper multi-core
computing without the complications that come with free-threading.
Failure to preserve isolation will expose you to the full consequences
of free-threading, including races and hard-to-debug crashes.

Aside from that, one of the main challenges of using multiple isolated
interpreters is how to communicate between them safely (not break
isolation) and efficiently.  The runtime and stdlib do not provide any
standard approach to this yet.  A future stdlib module would help
mitigate the effort of preserving isolation and expose effective tools
for communicating (and sharing) data between interpreters.

在 3.12 版被加入.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0554/


File: python.info,  Node: Bugs and caveats,  Prev: A Per-Interpreter GIL,  Up: Sub-interpreter support

7.9.6.2 Bugs and caveats
........................

Because sub-interpreters (and the main interpreter) are part of the same
process, the insulation between them isn't perfect -- for example, using
low-level file operations like *note os.close(): b18. they can
(accidentally or maliciously) affect each other's open files.  Because
of the way extensions are shared between (sub-)interpreters, some
extensions may not work properly; this is especially likely when using
single-phase initialization or (static) global variables.  It is
possible to insert objects created in one sub-interpreter into a
namespace of another (sub-)interpreter; this should be avoided if
possible.

Special care should be taken to avoid sharing user-defined functions,
methods, instances or classes between sub-interpreters, since import
operations executed by such objects may affect the wrong
(sub-)interpreter's dictionary of loaded modules.  It is equally
important to avoid sharing objects from which the above are reachable.

Also note that combining this functionality with ‘PyGILState_*’ APIs is
delicate, because these APIs assume a bijection between Python thread
states and OS-level threads, an assumption broken by the presence of
sub-interpreters.  It is highly recommended that you don't switch
sub-interpreters between a pair of matching *note PyGILState_Ensure():
376. and *note PyGILState_Release(): 377. calls.  Furthermore,
extensions (such as *note ctypes: 22.) using these APIs to allow calling
of Python code from non-Python created threads will probably be broken
when using sub-interpreters.


File: python.info,  Node: Asynchronous Notifications,  Next: Profiling and Tracing,  Prev: Sub-interpreter support,  Up: Initialization Finalization and Threads

7.9.7 Asynchronous Notifications
--------------------------------

A mechanism is provided to make asynchronous notifications to the main
interpreter thread.  These notifications take the form of a function
pointer and a void pointer argument.

 -- C 函式: int Py_AddPendingCall (int (*func)(void*), void *arg)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Schedule a function to be
     called from the main interpreter thread.  On success, ‘0’ is
     returned and 'func' is queued for being called in the main thread.
     On failure, ‘-1’ is returned without setting any exception.

     When successfully queued, 'func' will be 'eventually' called from
     the main interpreter thread with the argument 'arg'.  It will be
     called asynchronously with respect to normally running Python code,
     but with both these conditions met:

        * on a *note bytecode: 16d. boundary;

        * with the main thread holding the *note global interpreter
          lock: 12e. ('func' can therefore use the full C API).

     'func' must return ‘0’ on success, or ‘-1’ on failure with an
     exception set.  'func' won't be interrupted to perform another
     asynchronous notification recursively, but it can still be
     interrupted to switch threads if the global interpreter lock is
     released.

     This function doesn't need a current thread state to run, and it
     doesn't need the global interpreter lock.

     To call this function in a subinterpreter, the caller must hold the
     GIL. Otherwise, the function 'func' can be scheduled to be called
     from the wrong interpreter.

          警告: This is a low-level function, only useful for very
          special cases.  There is no guarantee that 'func' will be
          called as quick as possible.  If the main thread is busy
          executing a system call, 'func' won't be called before the
          system call returns.  This function is generally 'not'
          suitable for calling Python code from arbitrary C threads.
          Instead, use the *note PyGILState API: 4b5d.

     在 3.1 版被加入.

     在 3.9 版的變更: If this function is called in a subinterpreter,
     the function 'func' is now scheduled to be called from the
     subinterpreter, rather than being called from the main interpreter.
     Each subinterpreter now has its own list of scheduled calls.


File: python.info,  Node: Profiling and Tracing,  Next: Reference tracing,  Prev: Asynchronous Notifications,  Up: Initialization Finalization and Threads

7.9.8 Profiling and Tracing
---------------------------

The Python interpreter provides some low-level support for attaching
profiling and execution tracing facilities.  These are used for
profiling, debugging, and coverage analysis tools.

This C interface allows the profiling or tracing code to avoid the
overhead of calling through Python-level callable objects, making a
direct C function call instead.  The essential attributes of the
facility have not changed; the interface allows trace functions to be
installed per-thread, and the basic events reported to the trace
function are the same as had been reported to the Python-level trace
functions in previous versions.

 -- C 型別: typedef int (*Py_tracefunc)(*note PyObject: 311. *obj, *note
          PyFrameObject: 72d. *frame, int what, *note PyObject: 311.
          *arg)

     The type of the trace function registered using *note
     PyEval_SetProfile(): 146b. and *note PyEval_SetTrace(): 146c.  The
     first parameter is the object passed to the registration function
     as 'obj', 'frame' is the frame object to which the event pertains,
     'what' is one of the constants *note PyTrace_CALL: 4b76, *note
     PyTrace_EXCEPTION: 4b77, *note PyTrace_LINE: 4b78, *note
     PyTrace_RETURN: 4b79, *note PyTrace_C_CALL: 4b7a, *note
     PyTrace_C_EXCEPTION: 4b7b, *note PyTrace_C_RETURN: 4b7c, or *note
     PyTrace_OPCODE: 4b7d, and 'arg' depends on the value of 'what':

     Value of 'what'                     'arg' 的含義
                                         
     ---------------------------------------------------------------------------------
                                         
     *note PyTrace_CALL: 4b76.           Always *note Py_None: 46d6.
                                         
                                         
     *note PyTrace_EXCEPTION: 4b77.      Exception information as returned by
                                         *note sys.exc_info(): 630.
                                         
                                         
     *note PyTrace_LINE: 4b78.           Always *note Py_None: 46d6.
                                         
                                         
     *note PyTrace_RETURN: 4b79.         Value being returned to the caller, or
                                         ‘NULL’ if caused by an exception.
                                         
                                         
     *note PyTrace_C_CALL: 4b7a.         被呼叫的函式物件。
                                         
                                         
     *note PyTrace_C_EXCEPTION: 4b7b.    被呼叫的函式物件。
                                         
                                         
     *note PyTrace_C_RETURN: 4b7c.       被呼叫的函式物件。
                                         
                                         
     *note PyTrace_OPCODE: 4b7d.         Always *note Py_None: 46d6.
                                         

 -- C 變數: int PyTrace_CALL

     The value of the 'what' parameter to a *note Py_tracefunc: 4b75.
     function when a new call to a function or method is being reported,
     or a new entry into a generator.  Note that the creation of the
     iterator for a generator function is not reported as there is no
     control transfer to the Python bytecode in the corresponding frame.

 -- C 變數: int PyTrace_EXCEPTION

     The value of the 'what' parameter to a *note Py_tracefunc: 4b75.
     function when an exception has been raised.  The callback function
     is called with this value for 'what' when after any bytecode is
     processed after which the exception becomes set within the frame
     being executed.  The effect of this is that as exception
     propagation causes the Python stack to unwind, the callback is
     called upon return to each frame as the exception propagates.  Only
     trace functions receives these events; they are not needed by the
     profiler.

 -- C 變數: int PyTrace_LINE

     The value passed as the 'what' parameter to a *note Py_tracefunc:
     4b75. function (but not a profiling function) when a line-number
     event is being reported.  It may be disabled for a frame by setting
     *note f_trace_lines: b82. to '0' on that frame.

 -- C 變數: int PyTrace_RETURN

     The value for the 'what' parameter to *note Py_tracefunc: 4b75.
     functions when a call is about to return.

 -- C 變數: int PyTrace_C_CALL

     The value for the 'what' parameter to *note Py_tracefunc: 4b75.
     functions when a C function is about to be called.

 -- C 變數: int PyTrace_C_EXCEPTION

     The value for the 'what' parameter to *note Py_tracefunc: 4b75.
     functions when a C function has raised an exception.

 -- C 變數: int PyTrace_C_RETURN

     The value for the 'what' parameter to *note Py_tracefunc: 4b75.
     functions when a C function has returned.

 -- C 變數: int PyTrace_OPCODE

     The value for the 'what' parameter to *note Py_tracefunc: 4b75.
     functions (but not profiling functions) when a new opcode is about
     to be executed.  This event is not emitted by default: it must be
     explicitly requested by setting *note f_trace_opcodes: b83. to '1'
     on the frame.

 -- C 函式: void PyEval_SetProfile (Py_tracefunc func, PyObject *obj)

     Set the profiler function to 'func'.  The 'obj' parameter is passed
     to the function as its first parameter, and may be any Python
     object, or ‘NULL’.  If the profile function needs to maintain
     state, using a different value for 'obj' for each thread provides a
     convenient and thread-safe place to store it.  The profile function
     is called for all monitored events except *note PyTrace_LINE: 4b78.
     *note PyTrace_OPCODE: 4b7d. and *note PyTrace_EXCEPTION: 4b77.

     See also the *note sys.setprofile(): 146d. function.

     呼叫者必須持有 *note GIL: 13e.。

 -- C 函式: void PyEval_SetProfileAllThreads (Py_tracefunc func,
          PyObject *obj)

     Like *note PyEval_SetProfile(): 146b. but sets the profile function
     in all running threads belonging to the current interpreter instead
     of the setting it only on the current thread.

     呼叫者必須持有 *note GIL: 13e.。

     As *note PyEval_SetProfile(): 146b, this function ignores any
     exceptions raised while setting the profile functions in all
     threads.

在 3.12 版被加入.

 -- C 函式: void PyEval_SetTrace (Py_tracefunc func, PyObject *obj)

     Set the tracing function to 'func'.  This is similar to *note
     PyEval_SetProfile(): 146b, except the tracing function does receive
     line-number events and per-opcode events, but does not receive any
     event related to C function objects being called.  Any trace
     function registered using *note PyEval_SetTrace(): 146c. will not
     receive *note PyTrace_C_CALL: 4b7a, *note PyTrace_C_EXCEPTION:
     4b7b. or *note PyTrace_C_RETURN: 4b7c. as a value for the 'what'
     parameter.

     也請見 *note sys.settrace(): 146e. 函式。

     呼叫者必須持有 *note GIL: 13e.。

 -- C 函式: void PyEval_SetTraceAllThreads (Py_tracefunc func, PyObject
          *obj)

     Like *note PyEval_SetTrace(): 146c. but sets the tracing function
     in all running threads belonging to the current interpreter instead
     of the setting it only on the current thread.

     呼叫者必須持有 *note GIL: 13e.。

     As *note PyEval_SetTrace(): 146c, this function ignores any
     exceptions raised while setting the trace functions in all threads.

在 3.12 版被加入.


File: python.info,  Node: Reference tracing,  Next: Advanced Debugger Support,  Prev: Profiling and Tracing,  Up: Initialization Finalization and Threads

7.9.9 Reference tracing
-----------------------

在 3.13 版被加入.

 -- C 型別: typedef int (*PyRefTracer)(*note PyObject: 311.*, int event,
          void *data)

     The type of the trace function registered using *note
     PyRefTracer_SetTracer(): 343.  The first parameter is a Python
     object that has been just created (when 'event' is set to *note
     PyRefTracer_CREATE: 4b80.) or about to be destroyed (when 'event'
     is set to *note PyRefTracer_DESTROY: 4b81.).  The 'data' argument
     is the opaque pointer that was provided when *note
     PyRefTracer_SetTracer(): 343. was called.

在 3.13 版被加入.

 -- C 變數: int PyRefTracer_CREATE

     The value for the 'event' parameter to *note PyRefTracer: 4b7f.
     functions when a Python object has been created.

 -- C 變數: int PyRefTracer_DESTROY

     The value for the 'event' parameter to *note PyRefTracer: 4b7f.
     functions when a Python object has been destroyed.

 -- C 函式: int PyRefTracer_SetTracer (PyRefTracer tracer, void *data)

     Register a reference tracer function.  The function will be called
     when a new Python has been created or when an object is going to be
     destroyed.  If 'data' is provided it must be an opaque pointer that
     will be provided when the tracer function is called.  Return ‘0’ on
     success.  Set an exception and return ‘-1’ on error.

     Not that tracer functions 'must not' create Python objects inside
     or otherwise the call will be re-entrant.  The tracer also 'must
     not' clear any existing exception or set an exception.  The GIL
     will be held every time the tracer function is called.

     The GIL must be held when calling this function.

在 3.13 版被加入.

 -- C 函式: *note PyRefTracer: 4b7f. PyRefTracer_GetTracer (void **data)

     Get the registered reference tracer function and the value of the
     opaque data pointer that was registered when *note
     PyRefTracer_SetTracer(): 343. was called.  If no tracer was
     registered this function will return NULL and will set the 'data'
     pointer to NULL.

     The GIL must be held when calling this function.

在 3.13 版被加入.


File: python.info,  Node: Advanced Debugger Support,  Next: Thread Local Storage Support,  Prev: Reference tracing,  Up: Initialization Finalization and Threads

7.9.10 Advanced Debugger Support
--------------------------------

These functions are only intended to be used by advanced debugging
tools.

 -- C 函式: *note PyInterpreterState: 862. *PyInterpreterState_Head ()

     Return the interpreter state object at the head of the list of all
     such objects.

 -- C 函式: *note PyInterpreterState: 862. *PyInterpreterState_Main ()

     Return the main interpreter state object.

 -- C 函式: *note PyInterpreterState: 862. *PyInterpreterState_Next
          (PyInterpreterState *interp)

     Return the next interpreter state object after 'interp' from the
     list of all such objects.

 -- C 函式: *note PyThreadState: 731. *PyInterpreterState_ThreadHead
          (PyInterpreterState *interp)

     Return the pointer to the first *note PyThreadState: 731. object in
     the list of threads associated with the interpreter 'interp'.

 -- C 函式: *note PyThreadState: 731. *PyThreadState_Next (PyThreadState
          *tstate)

     Return the next thread state object after 'tstate' from the list of
     all such objects belonging to the same *note PyInterpreterState:
     862. object.


File: python.info,  Node: Thread Local Storage Support,  Next: Synchronization Primitives,  Prev: Advanced Debugger Support,  Up: Initialization Finalization and Threads

7.9.11 Thread Local Storage Support
-----------------------------------

The Python interpreter provides low-level support for thread-local
storage (TLS) which wraps the underlying native TLS implementation to
support the Python-level thread local storage API (*note
threading.local: 166d.).  The CPython C level APIs are similar to those
offered by pthreads and Windows: use a thread key and functions to
associate a void* value per thread.

The GIL does 'not' need to be held when calling these functions; they
supply their own locking.

Note that ‘Python.h’ does not include the declaration of the TLS APIs,
you need to include ‘pythread.h’ to use thread-local storage.

     備註: None of these API functions handle memory management on
     behalf of the void* values.  You need to allocate and deallocate
     them yourself.  If the void* values happen to be *note PyObject:
     311.*, these functions don't do refcount operations on them either.

* Menu:

* Thread Specific Storage (TSS) API: Thread Specific Storage TSS API.
* 執行緒局部儲存 (Thread Local Storage, TLS) API：: 執行緒局部儲存 Thread Local Storage TLS API：.


File: python.info,  Node: Thread Specific Storage TSS API,  Next: 執行緒局部儲存 Thread Local Storage TLS API：,  Up: Thread Local Storage Support

7.9.11.1 Thread Specific Storage (TSS) API
..........................................

TSS API is introduced to supersede the use of the existing TLS API
within the CPython interpreter.  This API uses a new type *note
Py_tss_t: a82. instead of int to represent thread keys.

在 3.7 版被加入.

也參考
......

"A New C-API for Thread-Local Storage in CPython" ( PEP 539(1))

 -- C 型別: type Py_tss_t

     This data structure represents the state of a thread key, the
     definition of which may depend on the underlying TLS
     implementation, and it has an internal field representing the key's
     initialization state.  There are no public members in this
     structure.

     When *note Py_LIMITED_API: 4f9. is not defined, static allocation
     of this type by *note Py_tss_NEEDS_INIT: 4b87. is allowed.

 -- C 巨集: Py_tss_NEEDS_INIT

     This macro expands to the initializer for *note Py_tss_t: a82.
     variables.  Note that this macro won't be defined with *note
     Py_LIMITED_API: 4f9.

* Menu:

* Dynamic Allocation::
* 方法::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0539/


File: python.info,  Node: Dynamic Allocation,  Next: 方法,  Up: Thread Specific Storage TSS API

7.9.11.2 Dynamic Allocation
...........................

Dynamic allocation of the *note Py_tss_t: a82, required in extension
modules built with *note Py_LIMITED_API: 4f9, where static allocation of
this type is not possible due to its implementation being opaque at
build time.

 -- C 函式: *note Py_tss_t: a82. *PyThread_tss_alloc ()
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Return a
     value which is the same state as a value initialized with *note
     Py_tss_NEEDS_INIT: 4b87, or ‘NULL’ in the case of dynamic
     allocation failure.

 -- C 函式: void PyThread_tss_free (Py_tss_t *key)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Free the
     given 'key' allocated by *note PyThread_tss_alloc(): 3cd, after
     first calling *note PyThread_tss_delete(): 3d5. to ensure any
     associated thread locals have been unassigned.  This is a no-op if
     the 'key' argument is ‘NULL’.

          備註: A freed key becomes a dangling pointer.  You should
          reset the key to ‘NULL’.


File: python.info,  Node: 方法,  Prev: Dynamic Allocation,  Up: Thread Specific Storage TSS API

7.9.11.3 方法
.............

The parameter 'key' of these functions must not be ‘NULL’.  Moreover,
the behaviors of *note PyThread_tss_set(): 3d1. and *note
PyThread_tss_get(): 3d3. are undefined if the given *note Py_tss_t: a82.
has not been initialized by *note PyThread_tss_create(): 486d.

 -- C 函式: int PyThread_tss_is_created (Py_tss_t *key)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Return a
     non-zero value if the given *note Py_tss_t: a82. has been
     initialized by *note PyThread_tss_create(): 486d.

 -- C 函式: int PyThread_tss_create (Py_tss_t *key)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Return a zero
     value on successful initialization of a TSS key.  The behavior is
     undefined if the value pointed to by the 'key' argument is not
     initialized by *note Py_tss_NEEDS_INIT: 4b87.  This function can be
     called repeatedly on the same key - calling it on an already
     initialized key is a no-op and immediately returns success.

 -- C 函式: void PyThread_tss_delete (Py_tss_t *key)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Destroy a TSS
     key to forget the values associated with the key across all
     threads, and change the key's initialization state to
     uninitialized.  A destroyed key is able to be initialized again by
     *note PyThread_tss_create(): 486d.  This function can be called
     repeatedly on the same key - calling it on an already destroyed key
     is a no-op.

 -- C 函式: int PyThread_tss_set (Py_tss_t *key, void *value)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Return a zero
     value to indicate successfully associating a void* value with a TSS
     key in the current thread.  Each thread has a distinct mapping of
     the key to a void* value.

 -- C 函式: void *PyThread_tss_get (Py_tss_t *key)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Return the
     void* value associated with a TSS key in the current thread.  This
     returns ‘NULL’ if no value is associated with the key in the
     current thread.


File: python.info,  Node: 執行緒局部儲存 Thread Local Storage TLS API：,  Prev: Thread Specific Storage TSS API,  Up: Thread Local Storage Support

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

在 3.7 版之後被棄用: This API is superseded by *note Thread Specific
Storage (TSS) API: a81.

     備註: This version of the API does not support platforms where the
     native TLS key is defined in a way that cannot be safely cast to
     ‘int’.  On such platforms, *note PyThread_create_key(): 3cc. will
     return immediately with a failure status, and the other TLS
     functions will all be no-ops on such platforms.

Due to the compatibility problem noted above, this version of the API
should not be used in new code.

 -- C 函式: int PyThread_create_key ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

 -- C 函式: void PyThread_delete_key (int key)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

 -- C 函式: int PyThread_set_key_value (int key, void *value)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

 -- C 函式: void *PyThread_get_key_value (int key)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

 -- C 函式: void PyThread_delete_key_value (int key)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

 -- C 函式: void PyThread_ReInitTLS ()
     ' 為 *note 穩定 ABI 的一部分: 4f9.'


File: python.info,  Node: Synchronization Primitives,  Prev: Thread Local Storage Support,  Up: Initialization Finalization and Threads

7.9.12 Synchronization Primitives
---------------------------------

The C-API provides a basic mutual exclusion lock.

 -- C 型別: type PyMutex

     A mutual exclusion lock.  The ‘PyMutex’ should be initialized to
     zero to represent the unlocked state.  For example:

          PyMutex mutex = {0};

     Instances of ‘PyMutex’ should not be copied or moved.  Both the
     contents and address of a ‘PyMutex’ are meaningful, and it must
     remain at a fixed, writable location in memory.

          備註: A ‘PyMutex’ currently occupies one byte, but the size
          should be considered unstable.  The size may change in future
          Python releases without a deprecation period.

     在 3.13 版被加入.

 -- C 函式: void PyMutex_Lock (PyMutex *m)

     Lock mutex 'm'.  If another thread has already locked it, the
     calling thread will block until the mutex is unlocked.  While
     blocked, the thread will temporarily release the *note GIL: 13e. if
     it is held.

     在 3.13 版被加入.

 -- C 函式: void PyMutex_Unlock (PyMutex *m)

     Unlock mutex 'm'.  The mutex must be locked -- otherwise, the
     function will issue a fatal error.

     在 3.13 版被加入.

* Menu:

* Python Critical Section API::


File: python.info,  Node: Python Critical Section API,  Up: Synchronization Primitives

7.9.12.1 Python Critical Section API
....................................

The critical section API provides a deadlock avoidance layer on top of
per-object locks for *note free-threaded: 42d1. CPython.  They are
intended to replace reliance on the *note global interpreter lock: 12e,
and are no-ops in versions of Python with the global interpreter lock.

Critical sections avoid deadlocks by implicitly suspending active
critical sections and releasing the locks during calls to *note
PyEval_SaveThread(): 373.  When *note PyEval_RestoreThread(): 374. is
called, the most recent critical section is resumed, and its locks
reacquired.  This means the critical section API provides weaker
guarantees than traditional locks - they are useful because their
behavior is similar to the *note GIL: 13e.

The functions and structs used by the macros are exposed for cases where
C macros are not available.  They should only be used as in the given
macro expansions.  Note that the sizes and contents of the structures
may change in future Python versions.

     備註: Operations that need to lock two objects at once must use
     *note Py_BEGIN_CRITICAL_SECTION2: 4b8e.  You 'cannot' use nested
     critical sections to lock more than one object at once, because the
     inner critical section may suspend the outer critical sections.
     This API does not provide a way to lock more than two objects at
     once.

Example usage:

     static PyObject *
     set_field(MyObject *self, PyObject *value)
     {
        Py_BEGIN_CRITICAL_SECTION(self);
        Py_SETREF(self->field, Py_XNewRef(value));
        Py_END_CRITICAL_SECTION();
        Py_RETURN_NONE;
     }

In the above example, *note Py_SETREF: 51f. calls *note Py_DECREF: 515,
which can call arbitrary code through an object's deallocation function.
The critical section API avoids potentital deadlocks due to reentrancy
and lock ordering by allowing the runtime to temporarily suspend the
critical section if the code triggered by the finalizer blocks and calls
*note PyEval_SaveThread(): 373.

 -- C 巨集: Py_BEGIN_CRITICAL_SECTION (op)

     Acquires the per-object lock for the object 'op' and begins a
     critical section.

     In the free-threaded build, this macro expands to:

          {
              PyCriticalSection _py_cs;
              PyCriticalSection_Begin(&_py_cs, (PyObject*)(op))

     In the default build, this macro expands to ‘{’.

     在 3.13 版被加入.

 -- C 巨集: Py_END_CRITICAL_SECTION ()

     Ends the critical section and releases the per-object lock.

     In the free-threaded build, this macro expands to:

              PyCriticalSection_End(&_py_cs);
          }

     In the default build, this macro expands to ‘}’.

     在 3.13 版被加入.

 -- C 巨集: Py_BEGIN_CRITICAL_SECTION2 (a, b)

     Acquires the per-objects locks for the objects 'a' and 'b' and
     begins a critical section.  The locks are acquired in a consistent
     order (lowest address first) to avoid lock ordering deadlocks.

     In the free-threaded build, this macro expands to:

          {
              PyCriticalSection2 _py_cs2;
              PyCriticalSection_Begin2(&_py_cs2, (PyObject*)(a), (PyObject*)(b))

     In the default build, this macro expands to ‘{’.

     在 3.13 版被加入.

 -- C 巨集: Py_END_CRITICAL_SECTION2 ()

     Ends the critical section and releases the per-object locks.

     In the free-threaded build, this macro expands to:

              PyCriticalSection_End2(&_py_cs2);
          }

     In the default build, this macro expands to ‘}’.

     在 3.13 版被加入.


File: python.info,  Node: Python 初始化設定,  Next: 記憶體管理,  Prev: Initialization Finalization and Threads,  Up: Python/C API 參考手冊

7.10 Python 初始化設定
======================

在 3.8 版被加入.

Python can be initialized with *note Py_InitializeFromConfig(): 390. and
the *note PyConfig: 371. structure.  It can be preinitialized with *note
Py_PreInitialize(): 3b6. and the *note PyPreConfig: 950. structure.

There are two kinds of configuration:

   * The *note Python Configuration: 4b93. can be used to build a
     customized Python which behaves as the regular Python.  For
     example, environment variables and command line arguments are used
     to configure Python.

   * The *note Isolated Configuration: 4b94. can be used to embed Python
     into an application.  It isolates Python from the system.  For
     example, environment variables are ignored, the LC_CTYPE locale is
     left unchanged and no signal handler is registered.

The *note Py_RunMain(): 969. function can be used to write a customized
Python program.

See also *note Initialization, Finalization, and Threads: 4b4f.

也參考
......

PEP 587(1) "Python Initialization Configuration".

* Menu:

* 範例: 範例<51>.
* PyWideStringList::
* PyStatus::
* PyPreConfig::
* Preinitialize Python with PyPreConfig::
* PyConfig::
* Initialization with PyConfig::
* Isolated Configuration::
* Python Configuration::
* Python Path Configuration::
* Py_RunMain(): Py_RunMain.
* Py_GetArgcArgv(): Py_GetArgcArgv.
* Multi-Phase Initialization Private Provisional API::

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0587/


File: python.info,  Node: 範例<51>,  Next: PyWideStringList,  Up: Python 初始化設定

7.10.1 範例
-----------

Example of customized Python always running in isolated mode:

     int main(int argc, char **argv)
     {
         PyStatus status;

         PyConfig config;
         PyConfig_InitPythonConfig(&config);
         config.isolated = 1;

         /* Decode command line arguments.
            Implicitly preinitialize Python (in isolated mode). */
         status = PyConfig_SetBytesArgv(&config, argc, argv);
         if (PyStatus_Exception(status)) {
             goto exception;
         }

         status = Py_InitializeFromConfig(&config);
         if (PyStatus_Exception(status)) {
             goto exception;
         }
         PyConfig_Clear(&config);

         return Py_RunMain();

     exception:
         PyConfig_Clear(&config);
         if (PyStatus_IsExit(status)) {
             return status.exitcode;
         }
         /* Display the error message and exit the process with
            non-zero exit code */
         Py_ExitStatusException(status);
     }


File: python.info,  Node: PyWideStringList,  Next: PyStatus,  Prev: 範例<51>,  Up: Python 初始化設定

7.10.2 PyWideStringList
-----------------------

 -- C 型別: type PyWideStringList

     ‘wchar_t*’ 字串串列。

     If 'length' is non-zero, 'items' must be non-‘NULL’ and all strings
     must be non-‘NULL’.

     方法：

      -- C 函式: *note PyStatus: 951. PyWideStringList_Append
               (PyWideStringList *list, const wchar_t *item)

          Append 'item' to 'list'.

          Python must be preinitialized to call this function.

      -- C 函式: *note PyStatus: 951. PyWideStringList_Insert
               (PyWideStringList *list, Py_ssize_t index, const wchar_t
               *item)

          Insert 'item' into 'list' at 'index'.

          If 'index' is greater than or equal to 'list' length, append
          'item' to 'list'.

          'index' must be greater than or equal to ‘0’.

          Python must be preinitialized to call this function.

     Structure fields:

      -- C 成員函數: *note Py_ssize_t: a03. length

          串列長度。

      -- C 成員函數: wchar_t **items

          List items.


File: python.info,  Node: PyStatus,  Next: PyPreConfig,  Prev: PyWideStringList,  Up: Python 初始化設定

7.10.3 PyStatus
---------------

 -- C 型別: type PyStatus

     Structure to store an initialization function status: success,
     error or exit.

     For an error, it can store the C function name which created the
     error.

     Structure fields:

      -- C 成員函數: int exitcode

          Exit code.  Argument passed to ‘exit()’.

      -- C 成員函數: const char *err_msg

          錯誤訊息。

      -- C 成員函數: const char *func

          Name of the function which created an error, can be ‘NULL’.

     Functions to create a status:

      -- C 函式: *note PyStatus: 951. PyStatus_Ok (void)

          Success.

      -- C 函式: *note PyStatus: 951. PyStatus_Error (const char
               *err_msg)

          Initialization error with a message.

          'err_msg' 不可為 ‘NULL’。

      -- C 函式: *note PyStatus: 951. PyStatus_NoMemory (void)

          Memory allocation failure (out of memory).

      -- C 函式: *note PyStatus: 951. PyStatus_Exit (int exitcode)

          Exit Python with the specified exit code.

     Functions to handle a status:

      -- C 函式: int PyStatus_Exception (PyStatus status)

          Is the status an error or an exit?  If true, the exception
          must be handled; by calling *note Py_ExitStatusException():
          966. for example.

      -- C 函式: int PyStatus_IsError (PyStatus status)

          Is the result an error?

      -- C 函式: int PyStatus_IsExit (PyStatus status)

          Is the result an exit?

      -- C 函式: void Py_ExitStatusException (PyStatus status)

          Call ‘exit(exitcode)’ if 'status' is an exit.  Print the error
          message and exit with a non-zero exit code if 'status' is an
          error.  Must only be called if ‘PyStatus_Exception(status)’ is
          non-zero.

     備註: Internally, Python uses macros which set ‘PyStatus.func’,
     whereas functions to create a status set ‘func’ to ‘NULL’.

範例：

     PyStatus alloc(void **ptr, size_t size)
     {
         *ptr = PyMem_RawMalloc(size);
         if (*ptr == NULL) {
             return PyStatus_NoMemory();
         }
         return PyStatus_Ok();
     }

     int main(int argc, char **argv)
     {
         void *ptr;
         PyStatus status = alloc(&ptr, 16);
         if (PyStatus_Exception(status)) {
             Py_ExitStatusException(status);
         }
         PyMem_Free(ptr);
         return 0;
     }


File: python.info,  Node: PyPreConfig,  Next: Preinitialize Python with PyPreConfig,  Prev: PyStatus,  Up: Python 初始化設定

7.10.4 PyPreConfig
------------------

 -- C 型別: type PyPreConfig

     Structure used to preinitialize Python.

     Function to initialize a preconfiguration:

      -- C 函式: void PyPreConfig_InitPythonConfig (PyPreConfig
               *preconfig)

          Initialize the preconfiguration with *note Python
          Configuration: 4b93.

      -- C 函式: void PyPreConfig_InitIsolatedConfig (PyPreConfig
               *preconfig)

          Initialize the preconfiguration with *note Isolated
          Configuration: 4b94.

     Structure fields:

      -- C 成員函數: int allocator

          Name of the Python memory allocators:

             * ‘PYMEM_ALLOCATOR_NOT_SET’ (‘0’): don't change memory
               allocators (use defaults).

             * ‘PYMEM_ALLOCATOR_DEFAULT’ (‘1’): *note default memory
               allocators: 1c52.

             * ‘PYMEM_ALLOCATOR_DEBUG’ (‘2’): *note default memory
               allocators: 1c52. with *note debug hooks: 1c55.

             * ‘PYMEM_ALLOCATOR_MALLOC’ (‘3’): use ‘malloc()’ of the C
               library.

             * ‘PYMEM_ALLOCATOR_MALLOC_DEBUG’ (‘4’): force usage of
               ‘malloc()’ with *note debug hooks: 1c55.

             * ‘PYMEM_ALLOCATOR_PYMALLOC’ (‘5’): *note Python pymalloc
               memory allocator: cb6.

             * ‘PYMEM_ALLOCATOR_PYMALLOC_DEBUG’ (‘6’): *note Python
               pymalloc memory allocator: cb6. with *note debug hooks:
               1c55.

             * ‘PYMEM_ALLOCATOR_MIMALLOC’ (‘6’): use ‘mimalloc’, a fast
               malloc replacement.

             * ‘PYMEM_ALLOCATOR_MIMALLOC_DEBUG’ (‘7’): use ‘mimalloc’, a
               fast malloc replacement with *note debug hooks: 1c55.

          ‘PYMEM_ALLOCATOR_PYMALLOC’ and
          ‘PYMEM_ALLOCATOR_PYMALLOC_DEBUG’ are not supported if Python
          is *note configured using -without-pymalloc: 1caf.

          ‘PYMEM_ALLOCATOR_MIMALLOC’ and
          ‘PYMEM_ALLOCATOR_MIMALLOC_DEBUG’ are not supported if Python
          is *note configured using -without-mimalloc: 1cae. or if the
          underlying atomic support isn't available.

          請見*note 記憶體管理: 4b9f.。

          預設：‘PYMEM_ALLOCATOR_NOT_SET’。

      -- C 成員函數: int configure_locale

          Set the LC_CTYPE locale to the user preferred locale.

          If equals to ‘0’, set *note coerce_c_locale: 4ba1. and *note
          coerce_c_locale_warn: 4ba2. members to ‘0’.

          請見 *note locale encoding: 227.。

          Default: ‘1’ in Python config, ‘0’ in isolated config.

      -- C 成員函數: int coerce_c_locale

          If equals to ‘2’, coerce the C locale.

          If equals to ‘1’, read the LC_CTYPE locale to decide if it
          should be coerced.

          請見 *note locale encoding: 227.。

          Default: ‘-1’ in Python config, ‘0’ in isolated config.

      -- C 成員函數: int coerce_c_locale_warn

          If non-zero, emit a warning if the C locale is coerced.

          Default: ‘-1’ in Python config, ‘0’ in isolated config.

      -- C 成員函數: int dev_mode

          *note Python Development Mode: 1dd.: see *note
          PyConfig.dev_mode: 4ba4.

          Default: ‘-1’ in Python mode, ‘0’ in isolated mode.

      -- C 成員函數: int isolated

          Isolated mode: see *note PyConfig.isolated: 3af.

          Default: ‘0’ in Python mode, ‘1’ in isolated mode.

      -- C 成員函數: int legacy_windows_fs_encoding

          如果不為 0：

             * 將 *note PyPreConfig.utf8_mode: 3b5. 設為 ‘0’、

             * 將 *note PyConfig.filesystem_encoding: 3b3. 設為
               ‘"mbcs"’、

             * 將 *note PyConfig.filesystem_errors: 3b4. 設為
               ‘"replace"’。

          Initialized from the *note PYTHONLEGACYWINDOWSFSENCODING: 28f.
          environment variable value.

          Only available on Windows.  ‘#ifdef MS_WINDOWS’ macro can be
          used for Windows specific code.

          預設：‘0’。

      -- C 成員函數: int parse_argv

          If non-zero, *note Py_PreInitializeFromArgs(): 967. and *note
          Py_PreInitializeFromBytesArgs(): 968. parse their ‘argv’
          argument the same way the regular Python parses command line
          arguments: see *note Command Line Arguments: fa8.

          Default: ‘1’ in Python config, ‘0’ in isolated config.

      -- C 成員函數: int use_environment

          Use *note environment variables: 595.?  See *note
          PyConfig.use_environment: 3a4.

          Default: ‘1’ in Python config and ‘0’ in isolated config.

      -- C 成員函數: int utf8_mode

          If non-zero, enable the *note Python UTF-8 Mode: 5fc.

          Set to ‘0’ or ‘1’ by the *note -X utf8: 15a. command line
          option and the *note PYTHONUTF8: a7b. environment variable.

          Also set to ‘1’ if the ‘LC_CTYPE’ locale is ‘C’ or ‘POSIX’.

          Default: ‘-1’ in Python config and ‘0’ in isolated config.


File: python.info,  Node: Preinitialize Python with PyPreConfig,  Next: PyConfig,  Prev: PyPreConfig,  Up: Python 初始化設定

7.10.5 Preinitialize Python with PyPreConfig
--------------------------------------------

The preinitialization of Python:

   * Set the Python memory allocators (*note PyPreConfig.allocator:
     4b9e.)

   * Configure the LC_CTYPE locale (*note locale encoding: 227.)

   * Set the *note Python UTF-8 Mode: 5fc. (*note PyPreConfig.utf8_mode:
     3b5.)

The current preconfiguration (‘PyPreConfig’ type) is stored in
‘_PyRuntime.preconfig’.

Functions to preinitialize Python:

 -- C 函式: *note PyStatus: 951. Py_PreInitialize (const PyPreConfig
          *preconfig)

     Preinitialize Python from 'preconfig' preconfiguration.

     'preconfig' 不可為 ‘NULL’。

 -- C 函式: *note PyStatus: 951. Py_PreInitializeFromBytesArgs (const
          PyPreConfig *preconfig, int argc, char *const *argv)

     Preinitialize Python from 'preconfig' preconfiguration.

     Parse 'argv' command line arguments (bytes strings) if *note
     parse_argv: 4ba6. of 'preconfig' is non-zero.

     'preconfig' 不可為 ‘NULL’。

 -- C 函式: *note PyStatus: 951. Py_PreInitializeFromArgs (const
          PyPreConfig *preconfig, int argc, wchar_t *const *argv)

     Preinitialize Python from 'preconfig' preconfiguration.

     Parse 'argv' command line arguments (wide strings) if *note
     parse_argv: 4ba6. of 'preconfig' is non-zero.

     'preconfig' 不可為 ‘NULL’。

The caller is responsible to handle exceptions (error or exit) using
*note PyStatus_Exception(): 95d. and *note Py_ExitStatusException():
966.

For *note Python Configuration: 4b93. (*note
PyPreConfig_InitPythonConfig(): 95b.), if Python is initialized with
command line arguments, the command line arguments must also be passed
to preinitialize Python, since they have an effect on the
pre-configuration like encodings.  For example, the *note -X utf8: 15a.
command line option enables the *note Python UTF-8 Mode: 5fc.

‘PyMem_SetAllocator()’ can be called after *note Py_PreInitialize():
3b6. and before *note Py_InitializeFromConfig(): 390. to install a
custom memory allocator.  It can be called before *note
Py_PreInitialize(): 3b6. if *note PyPreConfig.allocator: 4b9e. is set to
‘PYMEM_ALLOCATOR_NOT_SET’.

Python memory allocation functions like *note PyMem_RawMalloc(): 323.
must not be used before the Python preinitialization, whereas calling
directly ‘malloc()’ and ‘free()’ is always safe.  *note
Py_DecodeLocale(): b6e. must not be called before the Python
preinitialization.

Example using the preinitialization to enable the *note Python UTF-8
Mode: 5fc.:

     PyStatus status;
     PyPreConfig preconfig;
     PyPreConfig_InitPythonConfig(&preconfig);

     preconfig.utf8_mode = 1;

     status = Py_PreInitialize(&preconfig);
     if (PyStatus_Exception(status)) {
         Py_ExitStatusException(status);
     }

     /* at this point, Python speaks UTF-8 */

     Py_Initialize();
     /* ... use Python API here ... */
     Py_Finalize();


File: python.info,  Node: PyConfig,  Next: Initialization with PyConfig,  Prev: Preinitialize Python with PyPreConfig,  Up: Python 初始化設定

7.10.6 PyConfig
---------------

 -- C 型別: type PyConfig

     Structure containing most parameters to configure Python.

     When done, the *note PyConfig_Clear(): 953. function must be used
     to release the configuration memory.

     Structure methods:

      -- C 函式: void PyConfig_InitPythonConfig (PyConfig *config)

          Initialize configuration with the *note Python Configuration:
          4b93.

      -- C 函式: void PyConfig_InitIsolatedConfig (PyConfig *config)

          Initialize configuration with the *note Isolated
          Configuration: 4b94.

      -- C 函式: *note PyStatus: 951. PyConfig_SetString (PyConfig
               *config, wchar_t *const *config_str, const wchar_t *str)

          Copy the wide character string 'str' into ‘*config_str’.

          *note Preinitialize Python: 3b60. if needed.

      -- C 函式: *note PyStatus: 951. PyConfig_SetBytesString (PyConfig
               *config, wchar_t *const *config_str, const char *str)

          Decode 'str' using *note Py_DecodeLocale(): b6e. and set the
          result into ‘*config_str’.

          *note Preinitialize Python: 3b60. if needed.

      -- C 函式: *note PyStatus: 951. PyConfig_SetArgv (PyConfig
               *config, int argc, wchar_t *const *argv)

          Set command line arguments (*note argv: 38e. member of
          'config') from the 'argv' list of wide character strings.

          *note Preinitialize Python: 3b60. if needed.

      -- C 函式: *note PyStatus: 951. PyConfig_SetBytesArgv (PyConfig
               *config, int argc, char *const *argv)

          Set command line arguments (*note argv: 38e. member of
          'config') from the 'argv' list of bytes strings.  Decode bytes
          using *note Py_DecodeLocale(): b6e.

          *note Preinitialize Python: 3b60. if needed.

      -- C 函式: *note PyStatus: 951. PyConfig_SetWideStringList
               (PyConfig *config, PyWideStringList *list, Py_ssize_t
               length, wchar_t **items)

          Set the list of wide strings 'list' to 'length' and 'items'.

          *note Preinitialize Python: 3b60. if needed.

      -- C 函式: *note PyStatus: 951. PyConfig_Read (PyConfig *config)

          Read all Python configuration.

          Fields which are already initialized are left unchanged.

          Fields for *note path configuration: 852. are no longer
          calculated or modified when calling this function, as of
          Python 3.11.

          The *note PyConfig_Read(): 734. function only parses *note
          PyConfig.argv: 38e. arguments once: *note PyConfig.parse_argv:
          182b. is set to ‘2’ after arguments are parsed.  Since Python
          arguments are stripped from *note PyConfig.argv: 38e, parsing
          arguments twice would parse the application options as Python
          options.

          *note Preinitialize Python: 3b60. if needed.

          在 3.10 版的變更: The *note PyConfig.argv: 38e. arguments are
          now only parsed once, *note PyConfig.parse_argv: 182b. is set
          to ‘2’ after arguments are parsed, and arguments are only
          parsed if *note PyConfig.parse_argv: 182b. equals ‘1’.

          在 3.11 版的變更: *note PyConfig_Read(): 734. no longer
          calculates all paths, and so fields listed under *note Python
          Path Configuration: 852. may no longer be updated until *note
          Py_InitializeFromConfig(): 390. is called.

      -- C 函式: void PyConfig_Clear (PyConfig *config)

          Release configuration memory.

     Most ‘PyConfig’ methods *note preinitialize Python: 3b60. if
     needed.  In that case, the Python preinitialization configuration
     (*note PyPreConfig: 950.) in based on the *note PyConfig: 371.  If
     configuration fields which are in common with *note PyPreConfig:
     950. are tuned, they must be set before calling a *note PyConfig:
     371. method:

        * *note PyConfig.dev_mode: 4ba4.

        * *note PyConfig.isolated: 3af.

        * *note PyConfig.parse_argv: 182b.

        * *note PyConfig.use_environment: 3a4.

     Moreover, if *note PyConfig_SetArgv(): 956. or *note
     PyConfig_SetBytesArgv(): 957. is used, this method must be called
     before other methods, since the preinitialization configuration
     depends on command line arguments (if *note parse_argv: 182b. is
     non-zero).

     The caller of these methods is responsible to handle exceptions
     (error or exit) using ‘PyStatus_Exception()’ and
     ‘Py_ExitStatusException()’.

     Structure fields:

      -- C 成員函數: *note PyWideStringList: 952. argv

          Set *note sys.argv: 11fd. command line arguments based on
          *note argv: 38e.  These parameters are similar to those passed
          to the program's ‘main()’ function with the difference that
          the first entry should refer to the script file to be executed
          rather than the executable hosting the Python interpreter.  If
          there isn't a script that will be run, the first entry in
          *note argv: 38e. can be an empty string.

          Set *note parse_argv: 182b. to ‘1’ to parse *note argv: 38e.
          the same way the regular Python parses Python command line
          arguments and then to strip Python arguments from *note argv:
          38e.

          If *note argv: 38e. is empty, an empty string is added to
          ensure that *note sys.argv: 11fd. always exists and is never
          empty.

          預設值：‘NULL’。

          See also the *note orig_argv: 838. member.

      -- C 成員函數: int safe_path

          If equals to zero, ‘Py_RunMain()’ prepends a potentially
          unsafe path to *note sys.path: 37f. at startup:

             * If *note argv[0]: 38e. is equal to ‘L"-m"’ (‘python -m
               module’), prepend the current working directory.

             * If running a script (‘python script.py’), prepend the
               script's directory.  If it's a symbolic link, resolve
               symbolic links.

             * Otherwise (‘python -c code’ and ‘python’), prepend an
               empty string, which means the current working directory.

          Set to ‘1’ by the *note -P: 548. command line option and the
          *note PYTHONSAFEPATH: 549. environment variable.

          Default: ‘0’ in Python config, ‘1’ in isolated config.

          在 3.11 版被加入.

      -- C 成員函數: wchar_t *base_exec_prefix

          *note sys.base_exec_prefix: 413b.。

          預設值：‘NULL’。

          Part of the *note Python Path Configuration: 852. output.

          See also *note PyConfig.exec_prefix: 4bab.

      -- C 成員函數: wchar_t *base_executable

          Python base executable: ‘sys._base_executable’.

          Set by the ‘__PYVENV_LAUNCHER__’ environment variable.

          Set from *note PyConfig.executable: 370. if ‘NULL’.

          預設值：‘NULL’。

          Part of the *note Python Path Configuration: 852. output.

          See also *note PyConfig.executable: 370.

      -- C 成員函數: wchar_t *base_prefix

          *note sys.base_prefix: 3afe.。

          預設值：‘NULL’。

          Part of the *note Python Path Configuration: 852. output.

          See also *note PyConfig.prefix: 4bae.

      -- C 成員函數: int buffered_stdio

          If equals to ‘0’ and *note configure_c_stdio: 4baf. is
          non-zero, disable buffering on the C streams stdout and
          stderr.

          Set to ‘0’ by the *note -u: 18a8. command line option and the
          *note PYTHONUNBUFFERED: 18a9. environment variable.

          stdin is always opened in buffered mode.

          預設值：‘1’。

      -- C 成員函數: int bytes_warning

          If equals to ‘1’, issue a warning when comparing *note bytes:
          1a5. or *note bytearray: 4e3. with *note str: 3f2, or
          comparing *note bytes: 1a5. with *note int: 23c.

          If equal or greater to ‘2’, raise a *note BytesWarning: bca.
          exception in these cases.

          Incremented by the *note -b: 587. command line option.

          預設：‘0’。

      -- C 成員函數: int warn_default_encoding

          If non-zero, emit a *note EncodingWarning: 1c3f. warning when
          *note io.TextIOWrapper: 75f. uses its default encoding.  See
          *note 選擇性加入的編碼警告: 1c57. for details.

          預設：‘0’。

          在 3.10 版被加入.

      -- C 成員函數: int code_debug_ranges

          If equals to ‘0’, disables the inclusion of the end line and
          column mappings in code objects.  Also disables traceback
          printing carets to specific error locations.

          Set to ‘0’ by the *note PYTHONNODEBUGRANGES: 55a. environment
          variable and by the *note -X no_debug_ranges: 15a. command
          line option.

          預設值：‘1’。

          在 3.11 版被加入.

      -- C 成員函數: wchar_t *check_hash_pycs_mode

          Control the validation behavior of hash-based ‘.pyc’ files:
          value of the *note -check-hash-based-pycs: 1c32. command line
          option.

          Valid values:

             - ‘L"always"’: Hash the source file for invalidation
               regardless of value of the 'check_source' flag.

             - ‘L"never"’: Assume that hash-based pycs always are valid.

             - ‘L"default"’: The 'check_source' flag in hash-based pycs
               determines invalidation.

          預設：‘L"default"’。

          See also PEP 552(1) "Deterministic pycs".

      -- C 成員函數: int configure_c_stdio

          If non-zero, configure C standard streams:

             * On Windows, set the binary mode (‘O_BINARY’) on stdin,
               stdout and stderr.

             * If *note buffered_stdio: 3aa. equals zero, disable
               buffering of stdin, stdout and stderr streams.

             * If *note interactive: 398. is non-zero, enable stream
               buffering on stdin and stdout (only stdout on Windows).

          Default: ‘1’ in Python config, ‘0’ in isolated config.

      -- C 成員函數: int dev_mode

          If non-zero, enable the *note Python Development Mode: 1dd.

          Set to ‘1’ by the *note -X dev: 15a. option and the *note
          PYTHONDEVMODE: a90. environment variable.

          Default: ‘-1’ in Python mode, ‘0’ in isolated mode.

      -- C 成員函數: int dump_refs

          Dump Python references?

          If non-zero, dump all objects which are still alive at exit.

          Set to ‘1’ by the *note PYTHONDUMPREFS: 94a. environment
          variable.

          Needs a special build of Python with the ‘Py_TRACE_REFS’ macro
          defined: see the *note configure -with-trace-refs option: 317.

          預設：‘0’。

      -- C 成員函數: wchar_t *exec_prefix

          The site-specific directory prefix where the
          platform-dependent Python files are installed: *note
          sys.exec_prefix: 37d.

          預設值：‘NULL’。

          Part of the *note Python Path Configuration: 852. output.

          See also *note PyConfig.base_exec_prefix: 4baa.

      -- C 成員函數: wchar_t *executable

          The absolute path of the executable binary for the Python
          interpreter: *note sys.executable: 383.

          預設值：‘NULL’。

          Part of the *note Python Path Configuration: 852. output.

          See also *note PyConfig.base_executable: 4bac.

      -- C 成員函數: int faulthandler

          Enable faulthandler?

          If non-zero, call *note faulthandler.enable(): c45. at
          startup.

          Set to ‘1’ by *note -X faulthandler: 15a. and the *note
          PYTHONFAULTHANDLER: 1021. environment variable.

          Default: ‘-1’ in Python mode, ‘0’ in isolated mode.

      -- C 成員函數: wchar_t *filesystem_encoding

          *note Filesystem encoding: 4e0.: *note
          sys.getfilesystemencoding(): c00.

          On macOS, Android and VxWorks: use ‘"utf-8"’ by default.

          On Windows: use ‘"utf-8"’ by default, or ‘"mbcs"’ if *note
          legacy_windows_fs_encoding: 3b1. of *note PyPreConfig: 950. is
          non-zero.

          Default encoding on other platforms:

             * ‘"utf-8"’ if *note PyPreConfig.utf8_mode: 3b5. is
               non-zero.

             * ‘"ascii"’ if Python detects that ‘nl_langinfo(CODESET)’
               announces the ASCII encoding, whereas the ‘mbstowcs()’
               function decodes from a different encoding (usually
               Latin1).

             * ‘"utf-8"’ if ‘nl_langinfo(CODESET)’ returns an empty
               string.

             * Otherwise, use the *note locale encoding: 227.:
               ‘nl_langinfo(CODESET)’ result.

          At Python startup, the encoding name is normalized to the
          Python codec name.  For example, ‘"ANSI_X3.4-1968"’ is
          replaced with ‘"ascii"’.

          See also the *note filesystem_errors: 3b4. member.

      -- C 成員函數: wchar_t *filesystem_errors

          *note Filesystem error handler: 4e0.: *note
          sys.getfilesystemencodeerrors(): c8d.

          On Windows: use ‘"surrogatepass"’ by default, or ‘"replace"’
          if *note legacy_windows_fs_encoding: 3b1. of *note
          PyPreConfig: 950. is non-zero.

          On other platforms: use ‘"surrogateescape"’ by default.

          Supported error handlers:

             * ‘"strict"’

             * ‘"surrogateescape"’

             * ‘"surrogatepass"’ (only supported with the UTF-8
               encoding)

          See also the *note filesystem_encoding: 3b3. member.

      -- C 成員函數: unsigned long hash_seed

      -- C 成員函數: int use_hash_seed

          Randomized hash function seed.

          If *note use_hash_seed: 3ac. is zero, a seed is chosen
          randomly at Python startup, and *note hash_seed: 3ad. is
          ignored.

          Set by the *note PYTHONHASHSEED: 101e. environment variable.

          Default 'use_hash_seed' value: ‘-1’ in Python mode, ‘0’ in
          isolated mode.

      -- C 成員函數: wchar_t *home

          Set the default Python "home" directory, that is, the location
          of the standard Python libraries (see *note PYTHONHOME: 387.).

          Set by the *note PYTHONHOME: 387. environment variable.

          預設值：‘NULL’。

          Part of the *note Python Path Configuration: 852. input.

      -- C 成員函數: int import_time

          If non-zero, profile import time.

          Set the ‘1’ by the *note -X importtime: 15a. option and the
          *note PYTHONPROFILEIMPORTTIME: a98. environment variable.

          預設：‘0’。

      -- C 成員函數: int inspect

          Enter interactive mode after executing a script or a command.

          If greater than ‘0’, enable inspect: when a script is passed
          as first argument or the -c option is used, enter interactive
          mode after executing the script or the command, even when
          *note sys.stdin: 4e2. does not appear to be a terminal.

          Incremented by the *note -i: 144a. command line option.  Set
          to ‘1’ if the *note PYTHONINSPECT: 1449. environment variable
          is non-empty.

          預設：‘0’。

      -- C 成員函數: int install_signal_handlers

          Install Python signal handlers?

          Default: ‘1’ in Python mode, ‘0’ in isolated mode.

      -- C 成員函數: int interactive

          If greater than ‘0’, enable the interactive mode (REPL).

          Incremented by the *note -i: 144a. command line option.

          預設：‘0’。

      -- C 成員函數: int int_max_str_digits

          Configures the *note integer string conversion length
          limitation: 599.  An initial value of ‘-1’ means the value
          will be taken from the command line or environment or
          otherwise default to 4300 (*note
          sys.int_info.default_max_str_digits: 2159.).  A value of ‘0’
          disables the limitation.  Values greater than zero but less
          than 640 (*note sys.int_info.str_digits_check_threshold:
          419d.) are unsupported and will produce an error.

          Configured by the *note -X int_max_str_digits: 15a. command
          line flag or the *note PYTHONINTMAXSTRDIGITS: 16c0.
          environment variable.

          Default: ‘-1’ in Python mode.  4300 (*note
          sys.int_info.default_max_str_digits: 2159.) in isolated mode.

          在 3.12 版被加入.

      -- C 成員函數: int cpu_count

          If the value of *note cpu_count: 4bb7. is not ‘-1’ then it
          will override the return values of *note os.cpu_count(): 1a8,
          *note os.process_cpu_count(): 1a7, and *note
          multiprocessing.cpu_count(): f12.

          Configured by the ‘-X cpu_count=N|DEFAULT’ command line flag
          or the *note PYTHON_CPU_COUNT: 1f5. environment variable.

          預設值：‘1’。

          在 3.13 版被加入.

      -- C 成員函數: int isolated

          If greater than ‘0’, enable isolated mode:

             * Set *note safe_path: 717. to ‘1’: don't prepend a
               potentially unsafe path to *note sys.path: 37f. at Python
               startup, such as the current directory, the script's
               directory or an empty string.

             * 將 *note use_environment: 3a4. 設定為 ‘0’：忽略 ‘PYTHON’
               環境變數。

             * Set *note user_site_directory: 3a8. to ‘0’: don't add the
               user site directory to *note sys.path: 37f.

             * Python REPL doesn't import *note readline: a8. nor enable
               default readline configuration on interactive prompts.

          Set to ‘1’ by the *note -I: 902. command line option.

          Default: ‘0’ in Python mode, ‘1’ in isolated mode.

          See also the *note Isolated Configuration: 4b94. and *note
          PyPreConfig.isolated: 4ba5.

      -- C 成員函數: int legacy_windows_stdio

          If non-zero, use *note io.FileIO: 12a4. instead of
          ‘io._WindowsConsoleIO’ for *note sys.stdin: 4e2, *note
          sys.stdout: a79. and *note sys.stderr: 8dd.

          Set to ‘1’ if the *note PYTHONLEGACYWINDOWSSTDIO: c02.
          environment variable is set to a non-empty string.

          Only available on Windows.  ‘#ifdef MS_WINDOWS’ macro can be
          used for Windows specific code.

          預設：‘0’。

          See also the PEP 528(2) (Change Windows console encoding to
          UTF-8).

      -- C 成員函數: int malloc_stats

          If non-zero, dump statistics on *note Python pymalloc memory
          allocator: cb6. at exit.

          Set to ‘1’ by the *note PYTHONMALLOCSTATS: 1a5c. environment
          variable.

          The option is ignored if Python is *note configured using the
          -without-pymalloc option: 1caf.

          預設：‘0’。

      -- C 成員函數: wchar_t *platlibdir

          Platform library directory name: *note sys.platlibdir: 8dc.

          Set by the *note PYTHONPLATLIBDIR: 1842. environment variable.

          Default: value of the ‘PLATLIBDIR’ macro which is set by the
          *note configure -with-platlibdir option: 1c78. (default:
          ‘"lib"’, or ‘"DLLs"’ on Windows).

          Part of the *note Python Path Configuration: 852. input.

          在 3.9 版被加入.

          在 3.11 版的變更: This macro is now used on Windows to locate
          the standard library extension modules, typically under
          ‘DLLs’.  However, for compatibility, note that this value is
          ignored for any non-standard layouts, including in-tree builds
          and virtual environments.

      -- C 成員函數: wchar_t *pythonpath_env

          Module search paths (*note sys.path: 37f.) as a string
          separated by ‘DELIM’ (*note os.pathsep: 1c46.).

          Set by the *note PYTHONPATH: fbe. environment variable.

          預設值：‘NULL’。

          Part of the *note Python Path Configuration: 852. input.

      -- C 成員函數: *note PyWideStringList: 952. module_search_paths

      -- C 成員函數: int module_search_paths_set

          Module search paths: *note sys.path: 37f.

          If *note module_search_paths_set: 593. is equal to ‘0’, *note
          Py_InitializeFromConfig(): 390. will replace *note
          module_search_paths: 36d. and sets *note
          module_search_paths_set: 593. to ‘1’.

          Default: empty list (‘module_search_paths’) and ‘0’
          (‘module_search_paths_set’).

          Part of the *note Python Path Configuration: 852. output.

      -- C 成員函數: int optimization_level

          Compilation optimization level:

             * ‘0’: Peephole optimizer, set ‘__debug__’ to ‘True’.

             * ‘1’: Level 0, remove assertions, set ‘__debug__’ to
               ‘False’.

             * ‘2’: Level 1, strip docstrings.

          Incremented by the *note -O: d5b. command line option.  Set to
          the *note PYTHONOPTIMIZE: 1c35. environment variable value.

          預設：‘0’。

      -- C 成員函數: *note PyWideStringList: 952. orig_argv

          The list of the original command line arguments passed to the
          Python executable: *note sys.orig_argv: 7e4.

          If *note orig_argv: 838. list is empty and *note argv: 38e. is
          not a list only containing an empty string, *note
          PyConfig_Read(): 734. copies *note argv: 38e. into *note
          orig_argv: 838. before modifying *note argv: 38e. (if *note
          parse_argv: 182b. is non-zero).

          See also the *note argv: 38e. member and the *note
          Py_GetArgcArgv(): 1858. function.

          Default: empty list.

          在 3.10 版被加入.

      -- C 成員函數: int parse_argv

          Parse command line arguments?

          If equals to ‘1’, parse *note argv: 38e. the same way the
          regular Python parses *note command line arguments: fa8, and
          strip Python arguments from *note argv: 38e.

          The *note PyConfig_Read(): 734. function only parses *note
          PyConfig.argv: 38e. arguments once: *note PyConfig.parse_argv:
          182b. is set to ‘2’ after arguments are parsed.  Since Python
          arguments are stripped from *note PyConfig.argv: 38e, parsing
          arguments twice would parse the application options as Python
          options.

          Default: ‘1’ in Python mode, ‘0’ in isolated mode.

          在 3.10 版的變更: The *note PyConfig.argv: 38e. arguments are
          now only parsed if *note PyConfig.parse_argv: 182b. equals to
          ‘1’.

      -- C 成員函數: int parser_debug

          Parser debug mode.  If greater than ‘0’, turn on parser
          debugging output (for expert only, depending on compilation
          options).

          Incremented by the *note -d: 1c33. command line option.  Set
          to the *note PYTHONDEBUG: 1c34. environment variable value.

          Needs a *note debug build of Python: 1de. (the ‘Py_DEBUG’
          macro must be defined).

          預設：‘0’。

      -- C 成員函數: int pathconfig_warnings

          If non-zero, calculation of path configuration is allowed to
          log warnings into ‘stderr’.  If equals to ‘0’, suppress these
          warnings.

          Default: ‘1’ in Python mode, ‘0’ in isolated mode.

          Part of the *note Python Path Configuration: 852. input.

          在 3.11 版的變更: Now also applies on Windows.

      -- C 成員函數: wchar_t *prefix

          The site-specific directory prefix where the platform
          independent Python files are installed: *note sys.prefix: 381.

          預設值：‘NULL’。

          Part of the *note Python Path Configuration: 852. output.

          See also *note PyConfig.base_prefix: 4bad.

      -- C 成員函數: wchar_t *program_name

          Program name used to initialize *note executable: 370. and in
          early error messages during Python initialization.

             * On macOS, use *note PYTHONEXECUTABLE: 1c4a. environment
               variable if set.

             * If the ‘WITH_NEXT_FRAMEWORK’ macro is defined, use
               ‘__PYVENV_LAUNCHER__’ environment variable if set.

             * Use ‘argv[0]’ of *note argv: 38e. if available and
               non-empty.

             * Otherwise, use ‘L"python"’ on Windows, or ‘L"python3"’ on
               other platforms.

          預設值：‘NULL’。

          Part of the *note Python Path Configuration: 852. input.

      -- C 成員函數: wchar_t *pycache_prefix

          Directory where cached ‘.pyc’ files are written: *note
          sys.pycache_prefix: 948.

          Set by the *note -X pycache_prefix=PATH: 15a. command line
          option and the *note PYTHONPYCACHEPREFIX: 947. environment
          variable.  The command-line option takes precedence.

          If ‘NULL’, *note sys.pycache_prefix: 948. is set to ‘None’.

          預設值：‘NULL’。

      -- C 成員函數: int quiet

          Quiet mode.  If greater than ‘0’, don't display the copyright
          and version at Python startup in interactive mode.

          Incremented by the *note -q: 1c36. command line option.

          預設：‘0’。

      -- C 成員函數: wchar_t *run_command

          Value of the *note -c: 584. command line option.

          Used by *note Py_RunMain(): 969.

          預設值：‘NULL’。

      -- C 成員函數: wchar_t *run_filename

          Filename passed on the command line: trailing command line
          argument without *note -c: 584. or *note -m: 585.  It is used
          by the *note Py_RunMain(): 969. function.

          For example, it is set to ‘script.py’ by the ‘python3
          script.py arg’ command line.

          也請見 *note PyConfig.skip_source_first_line: 4bbd. 選項。

          預設值：‘NULL’。

      -- C 成員函數: wchar_t *run_module

          Value of the *note -m: 585. command line option.

          Used by *note Py_RunMain(): 969.

          預設值：‘NULL’。

      -- C 成員函數: wchar_t *run_presite

          ‘package.module’ path to module that should be imported before
          ‘site.py’ is run.

          Set by the *note -X presite=package.module: 15a. command-line
          option and the *note PYTHON_PRESITE: 1c40. environment
          variable.  The command-line option takes precedence.

          Needs a *note debug build of Python: 1de. (the ‘Py_DEBUG’
          macro must be defined).

          預設值：‘NULL’。

      -- C 成員函數: int show_ref_count

          Show total reference count at exit (excluding *note immortal:
          4190. objects)?

          Set to ‘1’ by *note -X showrefcount: 15a. command line option.

          Needs a *note debug build of Python: 1de. (the ‘Py_REF_DEBUG’
          macro must be defined).

          預設：‘0’。

      -- C 成員函數: int site_import

          Import the *note site: b5. module at startup?

          If equal to zero, disable the import of the module site and
          the site-dependent manipulations of *note sys.path: 37f. that
          it entails.

          Also disable these manipulations if the *note site: b5. module
          is explicitly imported later (call *note site.main(): 1c38. if
          you want them to be triggered).

          Set to ‘0’ by the *note -S: 1140. command line option.

          *note sys.flags.no_site: 632. is set to the inverted value of
          *note site_import: 39e.

          預設值：‘1’。

      -- C 成員函數: int skip_source_first_line

          If non-zero, skip the first line of the *note
          PyConfig.run_filename: 4bbc. source.

          It allows the usage of non-Unix forms of ‘#!cmd’.  This is
          intended for a DOS specific hack only.

          Set to ‘1’ by the *note -x: 1c3c. command line option.

          預設：‘0’。

      -- C 成員函數: wchar_t *stdio_encoding

      -- C 成員函數: wchar_t *stdio_errors

          Encoding and encoding errors of *note sys.stdin: 4e2, *note
          sys.stdout: a79. and *note sys.stderr: 8dd. (but *note
          sys.stderr: 8dd. always uses ‘"backslashreplace"’ error
          handler).

          Use the *note PYTHONIOENCODING: fab. environment variable if
          it is non-empty.

          Default encoding:

             * ‘"UTF-8"’ if *note PyPreConfig.utf8_mode: 3b5. is
               non-zero.

             * Otherwise, use the *note locale encoding: 227.

          Default error handler:

             * On Windows: use ‘"surrogateescape"’.

             * ‘"surrogateescape"’ if *note PyPreConfig.utf8_mode: 3b5.
               is non-zero, or if the LC_CTYPE locale is "C" or "POSIX".

             * ‘"strict"’ otherwise.

          See also *note PyConfig.legacy_windows_stdio: 36f.

      -- C 成員函數: int tracemalloc

          Enable tracemalloc?

          If non-zero, call *note tracemalloc.start(): 1c3d. at startup.

          Set by *note -X tracemalloc=N: 15a. command line option and by
          the *note PYTHONTRACEMALLOC: 1c3e. environment variable.

          Default: ‘-1’ in Python mode, ‘0’ in isolated mode.

      -- C 成員函數: int perf_profiling

          Enable compatibility mode with the perf profiler?

          If non-zero, initialize the perf trampoline.  See *note Python
          對 Linux perf 分析器的支援: 175. for more information.

          Set by *note -X perf: 15a. command-line option and by the
          *note PYTHON_PERF_JIT_SUPPORT: 176. environment variable for
          perf support with stack pointers and *note -X perf_jit: 15a.
          command-line option and by the *note PYTHON_PERF_JIT_SUPPORT:
          176. environment variable for perf support with DWARF JIT
          information.

          預設值：‘1’。

          在 3.12 版被加入.

      -- C 成員函數: int use_environment

          Use *note environment variables: 595.?

          If equals to zero, ignore the *note environment variables:
          595.

          Set to ‘0’ by the *note -E: 901. environment variable.

          Default: ‘1’ in Python config and ‘0’ in isolated config.

      -- C 成員函數: int user_site_directory

          If non-zero, add the user site directory to *note sys.path:
          37f.

          Set to ‘0’ by the *note -s: 1319. and *note -I: 902. command
          line options.

          Set to ‘0’ by the *note PYTHONNOUSERSITE: 131a. environment
          variable.

          Default: ‘1’ in Python mode, ‘0’ in isolated mode.

      -- C 成員函數: int verbose

          Verbose mode.  If greater than ‘0’, print a message each time
          a module is imported, showing the place (filename or built-in
          module) from which it is loaded.

          If greater than or equal to ‘2’, print a message for each file
          that is checked for when searching for a module.  Also
          provides information on module cleanup at exit.

          Incremented by the *note -v: 1392. command line option.

          Set by the *note PYTHONVERBOSE: 1c39. environment variable
          value.

          預設：‘0’。

      -- C 成員函數: *note PyWideStringList: 952. warnoptions

          Options of the *note warnings: fa. module to build warnings
          filters, lowest to highest priority: *note sys.warnoptions:
          37b.

          The *note warnings: fa. module adds *note sys.warnoptions:
          37b. in the reverse order: the last *note
          PyConfig.warnoptions: 36b. item becomes the first item of
          ‘warnings.filters’ which is checked first (highest priority).

          The *note -W: 86c. command line options adds its value to
          *note warnoptions: 36b, it can be used multiple times.

          The *note PYTHONWARNINGS: b51. environment variable can also
          be used to add warning options.  Multiple options can be
          specified, separated by commas (‘,’).

          Default: empty list.

      -- C 成員函數: int write_bytecode

          If equal to ‘0’, Python won't try to write ‘.pyc’ files on the
          import of source modules.

          Set to ‘0’ by the *note -B: 133b. command line option and the
          *note PYTHONDONTWRITEBYTECODE: 133c. environment variable.

          *note sys.dont_write_bytecode: 4169. is initialized to the
          inverted value of *note write_bytecode: 3a6.

          預設值：‘1’。

      -- C 成員函數: *note PyWideStringList: 952. xoptions

          Values of the *note -X: 15a. command line options: *note
          sys._xoptions: 1c41.

          Default: empty list.

If *note parse_argv: 182b. is non-zero, *note argv: 38e. arguments are
parsed the same way the regular Python parses *note command line
arguments: fa8, and Python arguments are stripped from *note argv: 38e.

The *note xoptions: 36c. options are parsed to set other options: see
the *note -X: 15a. command line option.

在 3.9 版的變更: The ‘show_alloc_count’ field has been removed.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0552/

   (2) https://peps.python.org/pep-0528/


File: python.info,  Node: Initialization with PyConfig,  Next: Isolated Configuration,  Prev: PyConfig,  Up: Python 初始化設定

7.10.7 Initialization with PyConfig
-----------------------------------

Function to initialize Python:

 -- C 函式: *note PyStatus: 951. Py_InitializeFromConfig (const PyConfig
          *config)

     Initialize Python from 'config' configuration.

The caller is responsible to handle exceptions (error or exit) using
*note PyStatus_Exception(): 95d. and *note Py_ExitStatusException():
966.

If *note PyImport_FrozenModules(): 2eeb, *note PyImport_AppendInittab():
16a6. or *note PyImport_ExtendInittab(): 16a7. are used, they must be
set or called after Python preinitialization and before the Python
initialization.  If Python is initialized multiple times, *note
PyImport_AppendInittab(): 16a6. or *note PyImport_ExtendInittab(): 16a7.
must be called before each Python initialization.

The current configuration (‘PyConfig’ type) is stored in
‘PyInterpreterState.config’.

Example setting the program name:

     void init_python(void)
     {
         PyStatus status;

         PyConfig config;
         PyConfig_InitPythonConfig(&config);

         /* Set the program name. Implicitly preinitialize Python. */
         status = PyConfig_SetString(&config, &config.program_name,
                                     L"/path/to/my_program");
         if (PyStatus_Exception(status)) {
             goto exception;
         }

         status = Py_InitializeFromConfig(&config);
         if (PyStatus_Exception(status)) {
             goto exception;
         }
         PyConfig_Clear(&config);
         return;

     exception:
         PyConfig_Clear(&config);
         Py_ExitStatusException(status);
     }

More complete example modifying the default configuration, read the
configuration, and then override some parameters.  Note that since 3.11,
many parameters are not calculated until initialization, and so values
cannot be read from the configuration structure.  Any values set before
initialize is called will be left unchanged by initialization:

     PyStatus init_python(const char *program_name)
     {
         PyStatus status;

         PyConfig config;
         PyConfig_InitPythonConfig(&config);

         /* Set the program name before reading the configuration
            (decode byte string from the locale encoding).

            Implicitly preinitialize Python. */
         status = PyConfig_SetBytesString(&config, &config.program_name,
                                          program_name);
         if (PyStatus_Exception(status)) {
             goto done;
         }

         /* Read all configuration at once */
         status = PyConfig_Read(&config);
         if (PyStatus_Exception(status)) {
             goto done;
         }

         /* Specify sys.path explicitly */
         /* If you want to modify the default set of paths, finish
            initialization first and then use PySys_GetObject("path") */
         config.module_search_paths_set = 1;
         status = PyWideStringList_Append(&config.module_search_paths,
                                          L"/path/to/stdlib");
         if (PyStatus_Exception(status)) {
             goto done;
         }
         status = PyWideStringList_Append(&config.module_search_paths,
                                          L"/path/to/more/modules");
         if (PyStatus_Exception(status)) {
             goto done;
         }

         /* Override executable computed by PyConfig_Read() */
         status = PyConfig_SetString(&config, &config.executable,
                                     L"/path/to/my_executable");
         if (PyStatus_Exception(status)) {
             goto done;
         }

         status = Py_InitializeFromConfig(&config);

     done:
         PyConfig_Clear(&config);
         return status;
     }


File: python.info,  Node: Isolated Configuration,  Next: Python Configuration,  Prev: Initialization with PyConfig,  Up: Python 初始化設定

7.10.8 Isolated Configuration
-----------------------------

*note PyPreConfig_InitIsolatedConfig(): 95a. and *note
PyConfig_InitIsolatedConfig(): 954. functions create a configuration to
isolate Python from the system.  For example, to embed Python into an
application.

This configuration ignores global configuration variables, environment
variables, command line arguments (*note PyConfig.argv: 38e. is not
parsed) and user site directory.  The C standard streams (ex: ‘stdout’)
and the LC_CTYPE locale are left unchanged.  Signal handlers are not
installed.

Configuration files are still used with this configuration to determine
paths that are unspecified.  Ensure *note PyConfig.home: 386. is
specified to avoid computing the default path configuration.


File: python.info,  Node: Python Configuration,  Next: Python Path Configuration,  Prev: Isolated Configuration,  Up: Python 初始化設定

7.10.9 Python Configuration
---------------------------

*note PyPreConfig_InitPythonConfig(): 95b. and *note
PyConfig_InitPythonConfig(): 955. functions create a configuration to
build a customized Python which behaves as the regular Python.

Environments variables and command line arguments are used to configure
Python, whereas global configuration variables are ignored.

This function enables C locale coercion ( PEP 538(1)) and *note Python
UTF-8 Mode: 5fc. ( PEP 540(2)) depending on the LC_CTYPE locale, *note
PYTHONUTF8: a7b. and *note PYTHONCOERCECLOCALE: a78. environment
variables.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0538/

   (2) https://peps.python.org/pep-0540/


File: python.info,  Node: Python Path Configuration,  Next: Py_RunMain,  Prev: Python Configuration,  Up: Python 初始化設定

7.10.10 Python Path Configuration
---------------------------------

*note PyConfig: 371. contains multiple fields for the path
configuration:

   * Path configuration inputs:

        * *note PyConfig.home: 386.

        * *note PyConfig.platlibdir: 1840.

        * *note PyConfig.pathconfig_warnings: 3a2.

        * *note PyConfig.program_name: 38f.

        * *note PyConfig.pythonpath_env: 4bb9.

        * current working directory: to get absolute paths

        * ‘PATH’ environment variable to get the program full path (from
          *note PyConfig.program_name: 38f.)

        * ‘__PYVENV_LAUNCHER__’ 環境變數

        * (Windows only) Application paths in the registry under
          "SoftwarePythonPythonCoreX.YPythonPath" of HKEY_CURRENT_USER
          and HKEY_LOCAL_MACHINE (where X.Y is the Python version).

   * Path configuration output fields:

        * *note PyConfig.base_exec_prefix: 4baa.

        * *note PyConfig.base_executable: 4bac.

        * *note PyConfig.base_prefix: 4bad.

        * *note PyConfig.exec_prefix: 4bab.

        * *note PyConfig.executable: 370.

        * *note PyConfig.module_search_paths_set: 593, *note
          PyConfig.module_search_paths: 36d.

        * *note PyConfig.prefix: 4bae.

If at least one "output field" is not set, Python calculates the path
configuration to fill unset fields.  If *note module_search_paths_set:
593. is equal to ‘0’, *note module_search_paths: 36d. is overridden and
*note module_search_paths_set: 593. is set to ‘1’.

It is possible to completely ignore the function calculating the default
path configuration by setting explicitly all path configuration output
fields listed above.  A string is considered as set even if it is
non-empty.  ‘module_search_paths’ is considered as set if
‘module_search_paths_set’ is set to ‘1’.  In this case,
‘module_search_paths’ will be used without modification.

Set *note pathconfig_warnings: 3a2. to ‘0’ to suppress warnings when
calculating the path configuration (Unix only, Windows does not log any
warning).

If *note base_prefix: 4bad. or *note base_exec_prefix: 4baa. fields are
not set, they inherit their value from *note prefix: 4bae. and *note
exec_prefix: 4bab. respectively.

*note Py_RunMain(): 969. and *note Py_Main(): bcc. modify *note
sys.path: 37f.:

   * If *note run_filename: 4bbc. is set and is a directory which
     contains a ‘__main__.py’ script, prepend *note run_filename: 4bbc.
     to *note sys.path: 37f.

   * If *note isolated: 3af. is zero:

        * If *note run_module: 4bbe. is set, prepend the current
          directory to *note sys.path: 37f.  Do nothing if the current
          directory cannot be read.

        * If *note run_filename: 4bbc. is set, prepend the directory of
          the filename to *note sys.path: 37f.

        * Otherwise, prepend an empty string to *note sys.path: 37f.

If *note site_import: 39e. is non-zero, *note sys.path: 37f. can be
modified by the *note site: b5. module.  If *note user_site_directory:
3a8. is non-zero and the user's site-package directory exists, the *note
site: b5. module appends the user's site-package directory to *note
sys.path: 37f.

The following configuration files are used by the path configuration:

   * ‘pyvenv.cfg’

   * ‘._pth’ file (ex: ‘python._pth’)

   * ‘pybuilddir.txt’ (Unix only)

If a ‘._pth’ file is present:

   * 將 *note isolated: 3af. 設定為 ‘1’。

   * 將 *note use_environment: 3a4. 設定為 ‘0’。

   * 將 *note site_import: 39e. 設定為 ‘0’。

   * 將 *note safe_path: 717. 設定為 ‘1’。

The ‘__PYVENV_LAUNCHER__’ environment variable is used to set *note
PyConfig.base_executable: 4bac.


File: python.info,  Node: Py_RunMain,  Next: Py_GetArgcArgv,  Prev: Python Path Configuration,  Up: Python 初始化設定

7.10.11 Py_RunMain()
--------------------

 -- C 函式: int Py_RunMain (void)

     Execute the command (*note PyConfig.run_command: 4bbb.), the script
     (*note PyConfig.run_filename: 4bbc.) or the module (*note
     PyConfig.run_module: 4bbe.) specified on the command line or in the
     configuration.

     By default and when if *note -i: 144a. option is used, run the
     REPL.

     Finally, finalizes Python and returns an exit status that can be
     passed to the ‘exit()’ function.

See *note Python Configuration: 4b93. for an example of customized
Python always running in isolated mode using *note Py_RunMain(): 969.


File: python.info,  Node: Py_GetArgcArgv,  Next: Multi-Phase Initialization Private Provisional API,  Prev: Py_RunMain,  Up: Python 初始化設定

7.10.12 Py_GetArgcArgv()
------------------------

 -- C 函式: void Py_GetArgcArgv (int *argc, wchar_t ***argv)

     Get the original command line arguments, before Python modified
     them.

     See also *note PyConfig.orig_argv: 838. member.


File: python.info,  Node: Multi-Phase Initialization Private Provisional API,  Prev: Py_GetArgcArgv,  Up: Python 初始化設定

7.10.13 Multi-Phase Initialization Private Provisional API
----------------------------------------------------------

This section is a private provisional API introducing multi-phase
initialization, the core feature of PEP 432(1):

   * "Core" initialization phase, "bare minimum Python":

        * 內建型別；

        * 內建例外；

        * Builtin and frozen modules;

        * The *note sys: c3. module is only partially initialized (ex:
          *note sys.path: 37f. doesn't exist yet).

   * "Main" initialization phase, Python is fully initialized:

        * Install and configure *note importlib: 6b.;

        * Apply the *note Path Configuration: 852.;

        * Install signal handlers;

        * Finish *note sys: c3. module initialization (ex: create *note
          sys.stdout: a79. and *note sys.path: 37f.);

        * Enable optional features like *note faulthandler: 4e. and
          *note tracemalloc: e8.;

        * 引入 *note site: b5. 模組；

        * etc.

Private provisional API:

   * ‘PyConfig._init_main’: if set to ‘0’, *note
     Py_InitializeFromConfig(): 390. stops at the "Core" initialization
     phase.

 -- C 函式: *note PyStatus: 951. _Py_InitializeMain (void)

     Move to the "Main" initialization phase, finish the Python
     initialization.

No module is imported during the "Core" phase and the ‘importlib’ module
is not configured: the *note Path Configuration: 852. is only applied
during the "Main" phase.  It may allow to customize Python in Python to
override or tune the *note Path Configuration: 852, maybe install a
custom *note sys.meta_path: cd2. importer or an import hook, etc.

It may become possible to calculate the *note Path Configuration: 852.
in Python, after the Core phase and before the Main phase, which is one
of the PEP 432(2) motivation.

The "Core" phase is not properly defined: what should be and what should
not be available at this phase is not specified yet.  The API is marked
as private and provisional: the API can be modified or even be removed
anytime until a proper public API is designed.

Example running Python code between "Core" and "Main" initialization
phases:

     void init_python(void)
     {
         PyStatus status;

         PyConfig config;
         PyConfig_InitPythonConfig(&config);
         config._init_main = 0;

         /* ... customize 'config' configuration ... */

         status = Py_InitializeFromConfig(&config);
         PyConfig_Clear(&config);
         if (PyStatus_Exception(status)) {
             Py_ExitStatusException(status);
         }

         /* Use sys.stderr because sys.stdout is only created
            by _Py_InitializeMain() */
         int res = PyRun_SimpleString(
             "import sys; "
             "print('Run Python code before _Py_InitializeMain', "
                    "file=sys.stderr)");
         if (res < 0) {
             exit(1);
         }

         /* ... put more configuration code here ... */

         status = _Py_InitializeMain();
         if (PyStatus_Exception(status)) {
             Py_ExitStatusException(status);
         }
     }

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0432/

   (2) https://peps.python.org/pep-0432/


File: python.info,  Node: 記憶體管理,  Next: Object Implementation Support,  Prev: Python 初始化設定,  Up: Python/C API 參考手冊

7.11 記憶體管理
===============

* Menu:

* 總覽: 總覽<2>.
* Allocator Domains::
* Raw Memory Interface::
* 記憶體介面::
* Object allocators::
* Default Memory Allocators::
* Customize Memory Allocators::
* Debug hooks on the Python memory allocators::
* The pymalloc allocator::
* The mimalloc allocator::
* tracemalloc C API::
* 範例: 範例<52>.


File: python.info,  Node: 總覽<2>,  Next: Allocator Domains,  Up: 記憶體管理

7.11.1 總覽
-----------

Memory management in Python involves a private heap containing all
Python objects and data structures.  The management of this private heap
is ensured internally by the 'Python memory manager'.  The Python memory
manager has different components which deal with various dynamic storage
management aspects, like sharing, segmentation, preallocation or
caching.

At the lowest level, a raw memory allocator ensures that there is enough
room in the private heap for storing all Python-related data by
interacting with the memory manager of the operating system.  On top of
the raw memory allocator, several object-specific allocators operate on
the same heap and implement distinct memory management policies adapted
to the peculiarities of every object type.  For example, integer objects
are managed differently within the heap than strings, tuples or
dictionaries because integers imply different storage requirements and
speed/space tradeoffs.  The Python memory manager thus delegates some of
the work to the object-specific allocators, but ensures that the latter
operate within the bounds of the private heap.

It is important to understand that the management of the Python heap is
performed by the interpreter itself and that the user has no control
over it, even if they regularly manipulate object pointers to memory
blocks inside that heap.  The allocation of heap space for Python
objects and other internal buffers is performed on demand by the Python
memory manager through the Python/C API functions listed in this
document.

To avoid memory corruption, extension writers should never try to
operate on Python objects with the functions exported by the C library:
‘malloc()’, ‘calloc()’, ‘realloc()’ and ‘free()’.  This will result in
mixed calls between the C allocator and the Python memory manager with
fatal consequences, because they implement different algorithms and
operate on different heaps.  However, one may safely allocate and
release memory blocks with the C library allocator for individual
purposes, as shown in the following example:

     PyObject *res;
     char *buf = (char *) malloc(BUFSIZ); /* for I/O */

     if (buf == NULL)
         return PyErr_NoMemory();
     ...Do some I/O operation involving buf...
     res = PyBytes_FromString(buf);
     free(buf); /* malloc'ed */
     return res;

In this example, the memory request for the I/O buffer is handled by the
C library allocator.  The Python memory manager is involved only in the
allocation of the bytes object returned as a result.

In most situations, however, it is recommended to allocate memory from
the Python heap specifically because the latter is under control of the
Python memory manager.  For example, this is required when the
interpreter is extended with new object types written in C. Another
reason for using the Python heap is the desire to 'inform' the Python
memory manager about the memory needs of the extension module.  Even
when the requested memory is used exclusively for internal, highly
specific purposes, delegating all memory requests to the Python memory
manager causes the interpreter to have a more accurate image of its
memory footprint as a whole.  Consequently, under certain circumstances,
the Python memory manager may or may not trigger appropriate actions,
like garbage collection, memory compaction or other preventive
procedures.  Note that by using the C library allocator as shown in the
previous example, the allocated memory for the I/O buffer escapes
completely the Python memory manager.

也參考
......

The *note PYTHONMALLOC: c0b. environment variable can be used to
configure the memory allocators used by Python.

The *note PYTHONMALLOCSTATS: 1a5c. environment variable can be used to
print statistics of the *note pymalloc memory allocator: cb6. every time
a new pymalloc object arena is created, and on shutdown.


File: python.info,  Node: Allocator Domains,  Next: Raw Memory Interface,  Prev: 總覽<2>,  Up: 記憶體管理

7.11.2 Allocator Domains
------------------------

All allocating functions belong to one of three different "domains" (see
also *note PyMemAllocatorDomain: 4bd1.).  These domains represent
different allocation strategies and are optimized for different
purposes.  The specific details on how every domain allocates memory or
what internal functions each domain calls is considered an
implementation detail, but for debugging purposes a simplified table can
be found at *note here: 1c52.  There is no hard requirement to use the
memory returned by the allocation functions belonging to a given domain
for only the purposes hinted by that domain (although this is the
recommended practice).  For example, one could use the memory returned
by *note PyMem_RawMalloc(): 323. for allocating Python objects or the
memory returned by *note PyObject_Malloc(): c0f. for allocating memory
for buffers.

The three allocation domains are:

   * Raw domain: intended for allocating memory for general-purpose
     memory buffers where the allocation 'must' go to the system
     allocator or where the allocator can operate without the *note GIL:
     13e.  The memory is requested directly to the system.

   * "Mem" domain: intended for allocating memory for Python buffers and
     general-purpose memory buffers where the allocation must be
     performed with the *note GIL: 13e. held.  The memory is taken from
     the Python private heap.

   * Object domain: intended for allocating memory belonging to Python
     objects.  The memory is taken from the Python private heap.

When freeing memory previously allocated by the allocating functions
belonging to a given domain,the matching specific deallocating functions
must be used.  For example, *note PyMem_Free(): 13b0. must be used to
free memory allocated using *note PyMem_Malloc(): c0d.


File: python.info,  Node: Raw Memory Interface,  Next: 記憶體介面,  Prev: Allocator Domains,  Up: 記憶體管理

7.11.3 Raw Memory Interface
---------------------------

The following function sets are wrappers to the system allocator.  These
functions are thread-safe, the *note GIL: 12e. does not need to be held.

The *note default raw memory allocator: 1c52. uses the following
functions: ‘malloc()’, ‘calloc()’, ‘realloc()’ and ‘free()’; call
‘malloc(1)’ (or ‘calloc(1, 1)’) when requesting zero bytes.

在 3.4 版被加入.

 -- C 函式: void *PyMem_RawMalloc (size_t n)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Allocates
     'n' bytes and returns a pointer of type void* to the allocated
     memory, or ‘NULL’ if the request fails.

     Requesting zero bytes returns a distinct non-‘NULL’ pointer if
     possible, as if ‘PyMem_RawMalloc(1)’ had been called instead.  The
     memory will not have been initialized in any way.

 -- C 函式: void *PyMem_RawCalloc (size_t nelem, size_t elsize)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Allocates
     'nelem' elements each whose size in bytes is 'elsize' and returns a
     pointer of type void* to the allocated memory, or ‘NULL’ if the
     request fails.  The memory is initialized to zeros.

     Requesting zero elements or elements of size zero bytes returns a
     distinct non-‘NULL’ pointer if possible, as if ‘PyMem_RawCalloc(1,
     1)’ had been called instead.

     在 3.5 版被加入.

 -- C 函式: void *PyMem_RawRealloc (void *p, size_t n)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Resizes the
     memory block pointed to by 'p' to 'n' bytes.  The contents will be
     unchanged to the minimum of the old and the new sizes.

     If 'p' is ‘NULL’, the call is equivalent to ‘PyMem_RawMalloc(n)’;
     else if 'n' is equal to zero, the memory block is resized but is
     not freed, and the returned pointer is non-‘NULL’.

     Unless 'p' is ‘NULL’, it must have been returned by a previous call
     to *note PyMem_RawMalloc(): 323, *note PyMem_RawRealloc(): 325. or
     *note PyMem_RawCalloc(): 324.

     If the request fails, *note PyMem_RawRealloc(): 325. returns ‘NULL’
     and 'p' remains a valid pointer to the previous memory area.

 -- C 函式: void PyMem_RawFree (void *p)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Frees the
     memory block pointed to by 'p', which must have been returned by a
     previous call to *note PyMem_RawMalloc(): 323, *note
     PyMem_RawRealloc(): 325. or *note PyMem_RawCalloc(): 324.
     Otherwise, or if ‘PyMem_RawFree(p)’ has been called before,
     undefined behavior occurs.

     If 'p' is ‘NULL’, no operation is performed.


File: python.info,  Node: 記憶體介面,  Next: Object allocators,  Prev: Raw Memory Interface,  Up: 記憶體管理

7.11.4 記憶體介面
-----------------

The following function sets, modeled after the ANSI C standard, but
specifying behavior when requesting zero bytes, are available for
allocating and releasing memory from the Python heap.

The *note default memory allocator: 1c52. uses the *note pymalloc memory
allocator: cb6.

     警告: The *note GIL: 12e. must be held when using these functions.

在 3.6 版的變更: The default allocator is now pymalloc instead of system
‘malloc()’.

 -- C 函式: void *PyMem_Malloc (size_t n)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Allocates 'n' bytes and
     returns a pointer of type void* to the allocated memory, or ‘NULL’
     if the request fails.

     Requesting zero bytes returns a distinct non-‘NULL’ pointer if
     possible, as if ‘PyMem_Malloc(1)’ had been called instead.  The
     memory will not have been initialized in any way.

 -- C 函式: void *PyMem_Calloc (size_t nelem, size_t elsize)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Allocates
     'nelem' elements each whose size in bytes is 'elsize' and returns a
     pointer of type void* to the allocated memory, or ‘NULL’ if the
     request fails.  The memory is initialized to zeros.

     Requesting zero elements or elements of size zero bytes returns a
     distinct non-‘NULL’ pointer if possible, as if ‘PyMem_Calloc(1, 1)’
     had been called instead.

     在 3.5 版被加入.

 -- C 函式: void *PyMem_Realloc (void *p, size_t n)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Resizes the memory block
     pointed to by 'p' to 'n' bytes.  The contents will be unchanged to
     the minimum of the old and the new sizes.

     If 'p' is ‘NULL’, the call is equivalent to ‘PyMem_Malloc(n)’; else
     if 'n' is equal to zero, the memory block is resized but is not
     freed, and the returned pointer is non-‘NULL’.

     Unless 'p' is ‘NULL’, it must have been returned by a previous call
     to *note PyMem_Malloc(): c0d, *note PyMem_Realloc(): fd5. or *note
     PyMem_Calloc(): e4f.

     If the request fails, *note PyMem_Realloc(): fd5. returns ‘NULL’
     and 'p' remains a valid pointer to the previous memory area.

 -- C 函式: void PyMem_Free (void *p)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Frees the memory block pointed
     to by 'p', which must have been returned by a previous call to
     *note PyMem_Malloc(): c0d, *note PyMem_Realloc(): fd5. or *note
     PyMem_Calloc(): e4f.  Otherwise, or if ‘PyMem_Free(p)’ has been
     called before, undefined behavior occurs.

     If 'p' is ‘NULL’, no operation is performed.

The following type-oriented macros are provided for convenience.  Note
that 'TYPE' refers to any C type.

 -- C 巨集: PyMem_New (TYPE, n)

     Same as *note PyMem_Malloc(): c0d, but allocates ‘(n *
     sizeof(TYPE))’ bytes of memory.  Returns a pointer cast to ‘TYPE*’.
     The memory will not have been initialized in any way.

 -- C 巨集: PyMem_Resize (p, TYPE, n)

     Same as *note PyMem_Realloc(): fd5, but the memory block is resized
     to ‘(n * sizeof(TYPE))’ bytes.  Returns a pointer cast to ‘TYPE*’.
     On return, 'p' will be a pointer to the new memory area, or ‘NULL’
     in the event of failure.

     This is a C preprocessor macro; 'p' is always reassigned.  Save the
     original value of 'p' to avoid losing memory when handling errors.

 -- C 函式: void PyMem_Del (void *p)

     和 *note PyMem_Free(): 13b0. 相同。

In addition, the following macro sets are provided for calling the
Python memory allocator directly, without involving the C API functions
listed above.  However, note that their use does not preserve binary
compatibility across Python versions and is therefore deprecated in
extension modules.

   * ‘PyMem_MALLOC(size)’

   * ‘PyMem_NEW(type, size)’

   * ‘PyMem_REALLOC(ptr, size)’

   * ‘PyMem_RESIZE(ptr, type, size)’

   * ‘PyMem_FREE(ptr)’

   * ‘PyMem_DEL(ptr)’


File: python.info,  Node: Object allocators,  Next: Default Memory Allocators,  Prev: 記憶體介面,  Up: 記憶體管理

7.11.5 Object allocators
------------------------

The following function sets, modeled after the ANSI C standard, but
specifying behavior when requesting zero bytes, are available for
allocating and releasing memory from the Python heap.

     備註: There is no guarantee that the memory returned by these
     allocators can be successfully cast to a Python object when
     intercepting the allocating functions in this domain by the methods
     described in the *note Customize Memory Allocators: 4bd7. section.

The *note default object allocator: 1c52. uses the *note pymalloc memory
allocator: cb6.

     警告: The *note GIL: 12e. must be held when using these functions.

 -- C 函式: void *PyObject_Malloc (size_t n)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Allocates 'n' bytes and
     returns a pointer of type void* to the allocated memory, or ‘NULL’
     if the request fails.

     Requesting zero bytes returns a distinct non-‘NULL’ pointer if
     possible, as if ‘PyObject_Malloc(1)’ had been called instead.  The
     memory will not have been initialized in any way.

 -- C 函式: void *PyObject_Calloc (size_t nelem, size_t elsize)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.7 版本開始.'  Allocates
     'nelem' elements each whose size in bytes is 'elsize' and returns a
     pointer of type void* to the allocated memory, or ‘NULL’ if the
     request fails.  The memory is initialized to zeros.

     Requesting zero elements or elements of size zero bytes returns a
     distinct non-‘NULL’ pointer if possible, as if ‘PyObject_Calloc(1,
     1)’ had been called instead.

     在 3.5 版被加入.

 -- C 函式: void *PyObject_Realloc (void *p, size_t n)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Resizes the memory block
     pointed to by 'p' to 'n' bytes.  The contents will be unchanged to
     the minimum of the old and the new sizes.

     If 'p' is ‘NULL’, the call is equivalent to ‘PyObject_Malloc(n)’;
     else if 'n' is equal to zero, the memory block is resized but is
     not freed, and the returned pointer is non-‘NULL’.

     Unless 'p' is ‘NULL’, it must have been returned by a previous call
     to *note PyObject_Malloc(): c0f, *note PyObject_Realloc(): 13b1. or
     *note PyObject_Calloc(): e50.

     If the request fails, *note PyObject_Realloc(): 13b1. returns
     ‘NULL’ and 'p' remains a valid pointer to the previous memory area.

 -- C 函式: void PyObject_Free (void *p)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Frees the memory block pointed
     to by 'p', which must have been returned by a previous call to
     *note PyObject_Malloc(): c0f, *note PyObject_Realloc(): 13b1. or
     *note PyObject_Calloc(): e50.  Otherwise, or if ‘PyObject_Free(p)’
     has been called before, undefined behavior occurs.

     If 'p' is ‘NULL’, no operation is performed.


File: python.info,  Node: Default Memory Allocators,  Next: Customize Memory Allocators,  Prev: Object allocators,  Up: 記憶體管理

7.11.6 Default Memory Allocators
--------------------------------

Default memory allocators:

配置                                名稱                     PyMem_RawMalloc        PyMem_Malloc              PyObject_Malloc
                                                                                                              
---------------------------------------------------------------------------------------------------------------------------------------
                                                                                                              
Release build                       ‘"pymalloc"’             ‘malloc’               ‘pymalloc’                ‘pymalloc’
                                                                                                              
                                                                                                              
Debug build                         ‘"pymalloc_debug"’       ‘malloc’ + debug       ‘pymalloc’ + debug        ‘pymalloc’ + debug
                                                                                                              
                                                                                                              
Release build, without pymalloc     ‘"malloc"’               ‘malloc’               ‘malloc’                  ‘malloc’
                                                                                                              
                                                                                                              
Debug build, without pymalloc       ‘"malloc_debug"’         ‘malloc’ + debug       ‘malloc’ + debug          ‘malloc’ + debug
                                                                                                              

Legend:

   * Name: value for *note PYTHONMALLOC: c0b. environment variable.

   * ‘malloc’: system allocators from the standard C library, C
     functions: ‘malloc()’, ‘calloc()’, ‘realloc()’ and ‘free()’.

   * ‘pymalloc’: *note pymalloc memory allocator: cb6.

   * ‘mimalloc’: *note mimalloc memory allocator: 1c54.  The pymalloc
     allocator will be used if mimalloc support isn't available.

   * "+ debug": with *note debug hooks on the Python memory allocators:
     1c55.

   * "Debug build": *note Python build in debug mode: 1de.


File: python.info,  Node: Customize Memory Allocators,  Next: Debug hooks on the Python memory allocators,  Prev: Default Memory Allocators,  Up: 記憶體管理

7.11.7 Customize Memory Allocators
----------------------------------

在 3.4 版被加入.

 -- C 型別: type PyMemAllocatorEx

     Structure used to describe a memory block allocator.  The structure
     has the following fields:

     欄位                                                           意義
                                                                    
     -----------------------------------------------------------------------------------------------------------
                                                                    
     ‘void *ctx’                                                    user context passed as first argument
                                                                    
                                                                    
     ‘void* malloc(void *ctx, size_t size)’                         allocate a memory block
                                                                    
                                                                    
     ‘void* calloc(void *ctx, size_t nelem, size_t elsize)’         allocate a memory block initialized with
                                                                    zeros
                                                                    
                                                                    
     ‘void* realloc(void *ctx, void *ptr, size_t new_size)’         allocate or resize a memory block
                                                                    
                                                                    
     ‘void free(void *ctx, void *ptr)’                              free a memory block
                                                                    

     在 3.5 版的變更: The ‘PyMemAllocator’ structure was renamed to
     *note PyMemAllocatorEx: e70. and a new ‘calloc’ field was added.

 -- C 型別: type PyMemAllocatorDomain

     Enum used to identify an allocator domain.  Domains:

      -- C 巨集: PYMEM_DOMAIN_RAW

          函式：

             * *note PyMem_RawMalloc(): 323.

             * *note PyMem_RawRealloc(): 325.

             * *note PyMem_RawCalloc(): 324.

             * *note PyMem_RawFree(): 326.

      -- C 巨集: PYMEM_DOMAIN_MEM

          函式：

             * *note PyMem_Malloc(): c0d,

             * *note PyMem_Realloc(): fd5.

             * *note PyMem_Calloc(): e4f.

             * *note PyMem_Free(): 13b0.

      -- C 巨集: PYMEM_DOMAIN_OBJ

          函式：

             * *note PyObject_Malloc(): c0f.

             * *note PyObject_Realloc(): 13b1.

             * *note PyObject_Calloc(): e50.

             * *note PyObject_Free(): c0c.

 -- C 函式: void PyMem_GetAllocator (PyMemAllocatorDomain domain,
          PyMemAllocatorEx *allocator)

     Get the memory block allocator of the specified domain.

 -- C 函式: void PyMem_SetAllocator (PyMemAllocatorDomain domain,
          PyMemAllocatorEx *allocator)

     Set the memory block allocator of the specified domain.

     The new allocator must return a distinct non-‘NULL’ pointer when
     requesting zero bytes.

     For the *note PYMEM_DOMAIN_RAW: 1c53. domain, the allocator must be
     thread-safe: the *note GIL: 12e. is not held when the allocator is
     called.

     For the remaining domains, the allocator must also be thread-safe:
     the allocator may be called in different interpreters that do not
     share a ‘GIL’.

     If the new allocator is not a hook (does not call the previous
     allocator), the *note PyMem_SetupDebugHooks(): c11. function must
     be called to reinstall the debug hooks on top on the new allocator.

     See also *note PyPreConfig.allocator: 4b9e. and *note Preinitialize
     Python with PyPreConfig: 3b60.

          警告: *note PyMem_SetAllocator(): 531. does have the following
          contract:

             * It can be called after *note Py_PreInitialize(): 3b6. and
               before *note Py_InitializeFromConfig(): 390. to install a
               custom memory allocator.  There are no restrictions over
               the installed allocator other than the ones imposed by
               the domain (for instance, the Raw Domain allows the
               allocator to be called without the GIL held).  See *note
               the section on allocator domains: 4bd0. for more
               information.

             * If called after Python has finish initializing (after
               *note Py_InitializeFromConfig(): 390. has been called)
               the allocator 'must' wrap the existing allocator.
               Substituting the current allocator for some other
               arbitrary one is 'not supported'.

     在 3.12 版的變更: All allocators must be thread-safe.

 -- C 函式: void PyMem_SetupDebugHooks (void)

     Setup *note debug hooks in the Python memory allocators: 1c55. to
     detect memory errors.


File: python.info,  Node: Debug hooks on the Python memory allocators,  Next: The pymalloc allocator,  Prev: Customize Memory Allocators,  Up: 記憶體管理

7.11.8 Debug hooks on the Python memory allocators
--------------------------------------------------

When *note Python is built in debug mode: 1de, the *note
PyMem_SetupDebugHooks(): c11. function is called at the *note Python
preinitialization: 3b60. to setup debug hooks on Python memory
allocators to detect memory errors.

The *note PYTHONMALLOC: c0b. environment variable can be used to install
debug hooks on a Python compiled in release mode (ex:
‘PYTHONMALLOC=debug’).

The *note PyMem_SetupDebugHooks(): c11. function can be used to set
debug hooks after calling *note PyMem_SetAllocator(): 531.

These debug hooks fill dynamically allocated memory blocks with special,
recognizable bit patterns.  Newly allocated memory is filled with the
byte ‘0xCD’ (‘PYMEM_CLEANBYTE’), freed memory is filled with the byte
‘0xDD’ (‘PYMEM_DEADBYTE’).  Memory blocks are surrounded by "forbidden
bytes" filled with the byte ‘0xFD’ (‘PYMEM_FORBIDDENBYTE’).  Strings of
these bytes are unlikely to be valid addresses, floats, or ASCII
strings.

Runtime 檢查：

   - Detect API violations.  For example, detect if *note
     PyObject_Free(): c0c. is called on a memory block allocated by
     *note PyMem_Malloc(): c0d.

   - Detect write before the start of the buffer (buffer underflow).

   - Detect write after the end of the buffer (buffer overflow).

   - Check that the *note GIL: 12e. is held when allocator functions of
     *note PYMEM_DOMAIN_OBJ: c0e. (ex: *note PyObject_Malloc(): c0f.)
     and *note PYMEM_DOMAIN_MEM: c10. (ex: *note PyMem_Malloc(): c0d.)
     domains are called.

On error, the debug hooks use the *note tracemalloc: e8. module to get
the traceback where a memory block was allocated.  The traceback is only
displayed if *note tracemalloc: e8. is tracing Python memory allocations
and the memory block was traced.

Let 'S' = ‘sizeof(size_t)’.  ‘2*S’ bytes are added at each end of each
block of 'N' bytes requested.  The memory layout is like so, where p
represents the address returned by a malloc-like or realloc-like
function (‘p[i:j]’ means the slice of bytes from ‘*(p+i)’ inclusive up
to ‘*(p+j)’ exclusive; note that the treatment of negative indices
differs from a Python slice):

‘p[-2*S:-S]’

     Number of bytes originally asked for.  This is a size_t, big-endian
     (easier to read in a memory dump).

‘p[-S]’

     API identifier (ASCII character):

        * ‘'r'’ for *note PYMEM_DOMAIN_RAW: 1c53.

        * ‘'m'’ for *note PYMEM_DOMAIN_MEM: c10.

        * ‘'o'’ for *note PYMEM_DOMAIN_OBJ: c0e.

‘p[-S+1:0]’

     Copies of PYMEM_FORBIDDENBYTE. Used to catch under- writes and
     reads.

‘p[0:N]’

     The requested memory, filled with copies of PYMEM_CLEANBYTE, used
     to catch reference to uninitialized memory.  When a realloc-like
     function is called requesting a larger memory block, the new excess
     bytes are also filled with PYMEM_CLEANBYTE. When a free-like
     function is called, these are overwritten with PYMEM_DEADBYTE, to
     catch reference to freed memory.  When a realloc- like function is
     called requesting a smaller memory block, the excess old bytes are
     also filled with PYMEM_DEADBYTE.

‘p[N:N+S]’

     Copies of PYMEM_FORBIDDENBYTE. Used to catch over- writes and
     reads.

‘p[N+S:N+2*S]’

     Only used if the ‘PYMEM_DEBUG_SERIALNO’ macro is defined (not
     defined by default).

     A serial number, incremented by 1 on each call to a malloc-like or
     realloc-like function.  Big-endian ‘size_t’.  If "bad memory" is
     detected later, the serial number gives an excellent way to set a
     breakpoint on the next run, to capture the instant at which this
     block was passed out.  The static function bumpserialno() in
     obmalloc.c is the only place the serial number is incremented, and
     exists so you can set such a breakpoint easily.

A realloc-like or free-like function first checks that the
PYMEM_FORBIDDENBYTE bytes at each end are intact.  If they've been
altered, diagnostic output is written to stderr, and the program is
aborted via Py_FatalError().  The other main failure mode is provoking a
memory error when a program reads up one of the special bit patterns and
tries to use it as an address.  If you get in a debugger then and look
at the object, you're likely to see that it's entirely filled with
PYMEM_DEADBYTE (meaning freed memory is getting used) or PYMEM_CLEANBYTE
(meaning uninitialized memory is getting used).

在 3.6 版的變更: The *note PyMem_SetupDebugHooks(): c11. function now
also works on Python compiled in release mode.  On error, the debug
hooks now use *note tracemalloc: e8. to get the traceback where a memory
block was allocated.  The debug hooks now also check if the GIL is held
when functions of *note PYMEM_DOMAIN_OBJ: c0e. and *note
PYMEM_DOMAIN_MEM: c10. domains are called.

在 3.8 版的變更: Byte patterns ‘0xCB’ (‘PYMEM_CLEANBYTE’), ‘0xDB’
(‘PYMEM_DEADBYTE’) and ‘0xFB’ (‘PYMEM_FORBIDDENBYTE’) have been replaced
with ‘0xCD’, ‘0xDD’ and ‘0xFD’ to use the same values than Windows CRT
debug ‘malloc()’ and ‘free()’.


File: python.info,  Node: The pymalloc allocator,  Next: The mimalloc allocator,  Prev: Debug hooks on the Python memory allocators,  Up: 記憶體管理

7.11.9 The pymalloc allocator
-----------------------------

Python has a 'pymalloc' allocator optimized for small objects (smaller
or equal to 512 bytes) with a short lifetime.  It uses memory mappings
called "arenas" with a fixed size of either 256 KiB on 32-bit platforms
or 1 MiB on 64-bit platforms.  It falls back to *note PyMem_RawMalloc():
323. and *note PyMem_RawRealloc(): 325. for allocations larger than 512
bytes.

'pymalloc' is the *note default allocator: 1c52. of the *note
PYMEM_DOMAIN_MEM: c10. (ex: *note PyMem_Malloc(): c0d.) and *note
PYMEM_DOMAIN_OBJ: c0e. (ex: *note PyObject_Malloc(): c0f.) domains.

The arena allocator uses the following functions:

   * ‘VirtualAlloc()’ and ‘VirtualFree()’ on Windows,

   * ‘mmap()’ and ‘munmap()’ if available,

   * ‘malloc()’ and ‘free()’ otherwise.

This allocator is disabled if Python is configured with the *note
-without-pymalloc: 1caf. option.  It can also be disabled at runtime
using the *note PYTHONMALLOC: c0b. environment variable (ex:
‘PYTHONMALLOC=malloc’).

* Menu:

* Customize pymalloc Arena Allocator::


File: python.info,  Node: Customize pymalloc Arena Allocator,  Up: The pymalloc allocator

7.11.9.1 Customize pymalloc Arena Allocator
...........................................

在 3.4 版被加入.

 -- C 型別: type PyObjectArenaAllocator

     Structure used to describe an arena allocator.  The structure has
     three fields:

     欄位                                                   意義
                                                            
     ---------------------------------------------------------------------------------------------------
                                                            
     ‘void *ctx’                                            user context passed as first argument
                                                            
                                                            
     ‘void* alloc(void *ctx, size_t size)’                  allocate an arena of size bytes
                                                            
                                                            
     ‘void free(void *ctx, void *ptr, size_t size)’         free an arena
                                                            

 -- C 函式: void PyObject_GetArenaAllocator (PyObjectArenaAllocator
          *allocator)

     Get the arena allocator.

 -- C 函式: void PyObject_SetArenaAllocator (PyObjectArenaAllocator
          *allocator)

     Set the arena allocator.


File: python.info,  Node: The mimalloc allocator,  Next: tracemalloc C API,  Prev: The pymalloc allocator,  Up: 記憶體管理

7.11.10 The mimalloc allocator
------------------------------

在 3.13 版被加入.

Python supports the mimalloc allocator when the underlying platform
support is available.  mimalloc "is a general purpose allocator with
excellent performance characteristics.  Initially developed by Daan
Leijen for the runtime systems of the Koka and Lean languages."


File: python.info,  Node: tracemalloc C API,  Next: 範例<52>,  Prev: The mimalloc allocator,  Up: 記憶體管理

7.11.11 tracemalloc C API
-------------------------

在 3.7 版被加入.

 -- C 函式: int PyTraceMalloc_Track (unsigned int domain, uintptr_t ptr,
          size_t size)

     Track an allocated memory block in the *note tracemalloc: e8.
     module.

     Return ‘0’ on success, return ‘-1’ on error (failed to allocate
     memory to store the trace).  Return ‘-2’ if tracemalloc is
     disabled.

     If memory block is already tracked, update the existing trace.

 -- C 函式: int PyTraceMalloc_Untrack (unsigned int domain, uintptr_t
          ptr)

     Untrack an allocated memory block in the *note tracemalloc: e8.
     module.  Do nothing if the block was not tracked.

     Return ‘-2’ if tracemalloc is disabled, otherwise return ‘0’.


File: python.info,  Node: 範例<52>,  Prev: tracemalloc C API,  Up: 記憶體管理

7.11.12 範例
------------

Here is the example from section *note 總覽: 4bcd, rewritten so that the
I/O buffer is allocated from the Python heap by using the first function
set:

     PyObject *res;
     char *buf = (char *) PyMem_Malloc(BUFSIZ); /* for I/O */

     if (buf == NULL)
         return PyErr_NoMemory();
     /* ...Do some I/O operation involving buf... */
     res = PyBytes_FromString(buf);
     PyMem_Free(buf); /* allocated with PyMem_Malloc */
     return res;

The same code using the type-oriented function set:

     PyObject *res;
     char *buf = PyMem_New(char, BUFSIZ); /* for I/O */

     if (buf == NULL)
         return PyErr_NoMemory();
     /* ...Do some I/O operation involving buf... */
     res = PyBytes_FromString(buf);
     PyMem_Del(buf); /* allocated with PyMem_New */
     return res;

Note that in the two examples above, the buffer is always manipulated
via functions belonging to the same set.  Indeed, it is required to use
the same memory API family for a given memory block, so that the risk of
mixing different allocators is reduced to a minimum.  The following code
sequence contains two errors, one of which is labeled as 'fatal' because
it mixes two different allocators operating on different heaps.

     char *buf1 = PyMem_New(char, BUFSIZ);
     char *buf2 = (char *) malloc(BUFSIZ);
     char *buf3 = (char *) PyMem_Malloc(BUFSIZ);
     ...
     PyMem_Del(buf3);  /* Wrong -- should be PyMem_Free() */
     free(buf2);       /* Right -- allocated via malloc() */
     free(buf1);       /* Fatal -- should be PyMem_Del()  */

In addition to the functions aimed at handling raw memory blocks from
the Python heap, objects in Python are allocated and released with *note
PyObject_New: 929, *note PyObject_NewVar: 92a. and *note PyObject_Del():
1440.

These will be explained in the next chapter on defining and implementing
new object types in C.


File: python.info,  Node: Object Implementation Support,  Next: API 和 ABI 版本管理,  Prev: 記憶體管理,  Up: Python/C API 參考手冊

7.12 Object Implementation Support
==================================

This chapter describes the functions, types, and macros used when
defining new object types.

* Menu:

* 在 heap 上分配物件::
* 通用物件結構::
* 型別物件: 型別物件<2>.
* Number Object Structures::
* Mapping Object Structures::
* Sequence Object Structures::
* Buffer Object Structures::
* Async Object Structures::
* Slot Type typedefs::
* 範例: 範例<53>.
* 循環垃圾回收的支援::


File: python.info,  Node: 在 heap 上分配物件,  Next: 通用物件結構,  Up: Object Implementation Support

7.12.1 在 heap 上分配物件
-------------------------

 -- C 函式: *note PyObject: 311. *_PyObject_New (PyTypeObject *type)
     '回傳值：新的參照。'

 -- C 函式: *note PyVarObject: 3f79. *_PyObject_NewVar (PyTypeObject
          *type, Py_ssize_t size)
     '回傳值：新的參照。'

 -- C 函式: *note PyObject: 311. *PyObject_Init (PyObject *op,
          PyTypeObject *type)
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  用它的型別
     和初始參照來初始化新分配物件 'op'。已初始化的物件會被回傳。如果
     'type' 表示了該物件參與迴圈垃圾檢查器，則將其新增到檢查器的觀察物件
     集合中。物件的其他欄位不受影響。

 -- C 函式: *note PyVarObject: 3f79. *PyObject_InitVar (PyVarObject *op,
          PyTypeObject *type, Py_ssize_t size)
     '回傳值：借用參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  它會做到
     *note PyObject_Init(): a0d. 的所有功能，並且會初始化一個大小可變物
     件的長度資訊。

 -- C 巨集: PyObject_New (TYPE, typeobj)

     使用 C 結構型別 'TYPE' 和 Python 型別物件 'typeobj'
     (‘PyTypeObject*’) 分配一個新的 Python 物件。未在該 Python 物件標頭
     (header) 中定義的欄位不會被初始化；呼叫者會擁有那個對於物件的唯一參
     照（物件的參照計數為一）。記憶體分配大小由 type 物件的 *note
     tp_basicsize: 92b. 欄位來指定。

 -- C 巨集: PyObject_NewVar (TYPE, typeobj, size)

     使用 C 的結構型別 'TYPE' 和 Python 的型別物件 'typeobj'
     (‘PyTypeObject*’) 分配一個新的 Python 物件。未在該 Python 物件標頭
     中定義的欄位不會被初始化。記憶體空間預留了 'TYPE' 結構大小再加上
     'typeobj' 物件中 *note tp_itemsize: 1e46. 欄位提供的 'size'
     (‘Py_ssize_t’) 欄位的值。這對於實現如 tuple 這種能夠在建立期間決定
     自己大小的物件是很實用的。將欄位的陣列嵌入到相同的記憶體分配中可以
     減少記憶體分配的次數，這提高了記憶體管理的效率。

 -- C 函式: void PyObject_Del (void *op)

     釋放由 *note PyObject_New: 929. 或者 *note PyObject_NewVar: 92a. 分
     配給物件的記憶體。這通常是在物件型別所指定的 *note tp_dealloc:
     4704. handler 中呼叫。呼叫這個函式以後，物件的各欄位都不可以被存取
     ，因為原本分配的記憶體已不再是一個有效的 Python 物件。

 -- C 變數: *note PyObject: 311. _Py_NoneStruct

     這個物件像是 Python 中的 ‘None’。它只應該透過 *note Py_None: 46d6.
     巨集來存取，該巨集的拿到指向該物件的指標。

也參考
......

*note PyModule_Create(): 46da.

     分配記憶體和建立擴充模組。


File: python.info,  Node: 通用物件結構,  Next: 型別物件<2>,  Prev: 在 heap 上分配物件,  Up: Object Implementation Support

7.12.2 通用物件結構
-------------------

There are a large number of structures which are used in the definition
of object types for Python.  This section describes these structures and
how they are used.

* Menu:

* Base object types and macros::
* 實作函式與方法::
* Accessing attributes of extension types::


File: python.info,  Node: Base object types and macros,  Next: 實作函式與方法,  Up: 通用物件結構

7.12.2.1 Base object types and macros
.....................................

All Python objects ultimately share a small number of fields at the
beginning of the object's representation in memory.  These are
represented by the *note PyObject: 311. and *note PyVarObject: 3f79.
types, which are defined, in turn, by the expansions of some macros also
used, whether directly or indirectly, in the definition of all other
Python objects.  Additional macros can be found under *note reference
counting: 48fc.

 -- C 型別: type PyObject
     ' 為 *note 受限 API 的一部分: 4f9.  （只有部分成員是穩定 ABI 的一部
     分。）' All object types are extensions of this type.  This is a
     type which contains the information Python needs to treat a pointer
     to an object as an object.  In a normal "release" build, it
     contains only the object's reference count and a pointer to the
     corresponding type object.  Nothing is actually declared to be a
     *note PyObject: 311, but every pointer to a Python object can be
     cast to a *note PyObject: 311.*.  Access to the members must be
     done by using the macros *note Py_REFCNT: 84e. and *note Py_TYPE:
     724.

 -- C 型別: type PyVarObject
     ' 為 *note 受限 API 的一部分: 4f9.  （只有部分成員是穩定 ABI 的一部
     分。）' This is an extension of *note PyObject: 311. that adds the
     *note ob_size: 48af. field.  This is only used for objects that
     have some notion of 'length'.  This type does not often appear in
     the Python/C API. Access to the members must be done by using the
     macros *note Py_REFCNT: 84e, *note Py_TYPE: 724, and *note Py_SIZE:
     726.

 -- C 巨集: PyObject_HEAD

     This is a macro used when declaring new types which represent
     objects without a varying length.  The PyObject_HEAD macro expands
     to:

          PyObject ob_base;

     See documentation of *note PyObject: 311. above.

 -- C 巨集: PyObject_VAR_HEAD

     This is a macro used when declaring new types which represent
     objects with a length that varies from instance to instance.  The
     PyObject_VAR_HEAD macro expands to:

          PyVarObject ob_base;

     請見上面 *note PyVarObject: 3f79. 的文件。

 -- C 函式: int Py_Is (PyObject *x, PyObject *y)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本開始.'  Test if the
     'x' object is the 'y' object, the same as ‘x is y’ in Python.

     在 3.10 版被加入.

 -- C 函式: int Py_IsNone (PyObject *x)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本開始.'  Test if an
     object is the ‘None’ singleton, the same as ‘x is None’ in Python.

     在 3.10 版被加入.

 -- C 函式: int Py_IsTrue (PyObject *x)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本開始.'  Test if an
     object is the ‘True’ singleton, the same as ‘x is True’ in Python.

     在 3.10 版被加入.

 -- C 函式: int Py_IsFalse (PyObject *x)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本開始.'  Test if an
     object is the ‘False’ singleton, the same as ‘x is False’ in
     Python.

     在 3.10 版被加入.

 -- C 函式: *note PyTypeObject: a48. *Py_TYPE (PyObject *o)
     '回傳值：借用參照。' Get the type of the Python object 'o'.

     Return a *note borrowed reference: 2ef.

     Use the *note Py_SET_TYPE(): 725. function to set an object type.

     在 3.11 版的變更: *note Py_TYPE(): 724. is changed to an inline
     static function.  The parameter type is no longer const *note
     PyObject: 311.*.

 -- C 函式: int Py_IS_TYPE (PyObject *o, PyTypeObject *type)

     Return non-zero if the object 'o' type is 'type'.  Return zero
     otherwise.  Equivalent to: ‘Py_TYPE(o) == type’.

     在 3.9 版被加入.

 -- C 函式: void Py_SET_TYPE (PyObject *o, PyTypeObject *type)

     將物件 'o' 的型別設為 'type'。

     在 3.9 版被加入.

 -- C 函式: *note Py_ssize_t: a03. Py_SIZE (PyVarObject *o)

     取得 Python 物件 'o' 的大小。

     Use the *note Py_SET_SIZE(): 727. function to set an object size.

     在 3.11 版的變更: *note Py_SIZE(): 726. is changed to an inline
     static function.  The parameter type is no longer const *note
     PyVarObject: 3f79.*.

 -- C 函式: void Py_SET_SIZE (PyVarObject *o, Py_ssize_t size)

     將物件 'o' 的大小設為 'size'。

     在 3.9 版被加入.

 -- C 巨集: PyObject_HEAD_INIT (type)

     This is a macro which expands to initialization values for a new
     *note PyObject: 311. type.  This macro expands to:

          _PyObject_EXTRA_INIT
          1, type,

 -- C 巨集: PyVarObject_HEAD_INIT (type, size)

     This is a macro which expands to initialization values for a new
     *note PyVarObject: 3f79. type, including the *note ob_size: 48af.
     field.  This macro expands to:

          _PyObject_EXTRA_INIT
          1, type, size,


File: python.info,  Node: 實作函式與方法,  Next: Accessing attributes of extension types,  Prev: Base object types and macros,  Up: 通用物件結構

7.12.2.2 實作函式與方法
.......................

 -- C 型別: type PyCFunction
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Type of the functions used to
     implement most Python callables in C. Functions of this type take
     two *note PyObject: 311.* parameters and return one such value.  If
     the return value is ‘NULL’, an exception shall have been set.  If
     not ‘NULL’, the return value is interpreted as the return value of
     the function as exposed in Python.  The function must return a new
     reference.

     The function signature is:

          PyObject *PyCFunction(PyObject *self,
                                PyObject *args);

 -- C 型別: type PyCFunctionWithKeywords
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Type of the functions used to
     implement Python callables in C with signature *note METH_VARARGS |
     METH_KEYWORDS: 4bf3.  The function signature is:

          PyObject *PyCFunctionWithKeywords(PyObject *self,
                                            PyObject *args,
                                            PyObject *kwargs);

 -- C 型別: type PyCFunctionFast
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Type of the
     functions used to implement Python callables in C with signature
     *note METH_FASTCALL: 151b.  The function signature is:

          PyObject *PyCFunctionFast(PyObject *self,
                                    PyObject *const *args,
                                    Py_ssize_t nargs);

 -- C 型別: type PyCFunctionFastWithKeywords
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.13 版本開始.'  Type of the
     functions used to implement Python callables in C with signature
     *note METH_FASTCALL | METH_KEYWORDS: 4bf4.  The function signature
     is:

          PyObject *PyCFunctionFastWithKeywords(PyObject *self,
                                                PyObject *const *args,
                                                Py_ssize_t nargs,
                                                PyObject *kwnames);

 -- C 型別: type PyCMethod

     Type of the functions used to implement Python callables in C with
     signature *note METH_METHOD | METH_FASTCALL | METH_KEYWORDS: 1584.
     The function signature is:

          PyObject *PyCMethod(PyObject *self,
                              PyTypeObject *defining_class,
                              PyObject *const *args,
                              Py_ssize_t nargs,
                              PyObject *kwnames)

     在 3.9 版被加入.

 -- C 型別: type PyMethodDef
     ' 為 *note 穩定 ABI 的一部分: 4f9. （包含所有成員）.'  Structure
     used to describe a method of an extension type.  This structure has
     four fields:

      -- C 成員函數: const char *ml_name

          Name of the method.

      -- C 成員函數: *note PyCFunction: 13e2. ml_meth

          Pointer to the C implementation.

      -- C 成員函數: int ml_flags

          Flags bits indicating how the call should be constructed.

      -- C 成員函數: const char *ml_doc

          Points to the contents of the docstring.

The *note ml_meth: 4bf5. is a C function pointer.  The functions may be
of different types, but they always return *note PyObject: 311.*.  If
the function is not of the *note PyCFunction: 13e2, the compiler will
require a cast in the method table.  Even though *note PyCFunction:
13e2. defines the first parameter as *note PyObject: 311.*, it is common
that the method implementation uses the specific C type of the 'self'
object.

The *note ml_flags: 4bf6. field is a bitfield which can include the
following flags.  The individual flags indicate either a calling
convention or a binding convention.

There are these calling conventions:

 -- C 巨集: METH_VARARGS

     This is the typical calling convention, where the methods have the
     type *note PyCFunction: 13e2.  The function expects two *note
     PyObject: 311.* values.  The first one is the 'self' object for
     methods; for module functions, it is the module object.  The second
     parameter (often called 'args') is a tuple object representing all
     arguments.  This parameter is typically processed using *note
     PyArg_ParseTuple(): 517. or *note PyArg_UnpackTuple(): 1476.

 -- C 巨集: METH_KEYWORDS

     Can only be used in certain combinations with other flags: *note
     METH_VARARGS | METH_KEYWORDS: 4bf3, *note METH_FASTCALL |
     METH_KEYWORDS: 4bf4. and *note METH_METHOD | METH_FASTCALL |
     METH_KEYWORDS: 1584.

*note METH_VARARGS: 1478. | *note METH_KEYWORDS: 46d9.

     Methods with these flags must be of type *note
     PyCFunctionWithKeywords: 4791.  The function expects three
     parameters: 'self', 'args', 'kwargs' where 'kwargs' is a dictionary
     of all the keyword arguments or possibly ‘NULL’ if there are no
     keyword arguments.  The parameters are typically processed using
     *note PyArg_ParseTupleAndKeywords(): 2e9.

 -- C 巨集: METH_FASTCALL

     Fast calling convention supporting only positional arguments.  The
     methods have the type *note PyCFunctionFast: 478f.  The first
     parameter is 'self', the second parameter is a C array of *note
     PyObject: 311.* values indicating the arguments and the third
     parameter is the number of arguments (the length of the array).

     在 3.7 版被加入.

     在 3.10 版的變更: ‘METH_FASTCALL’ is now part of the *note stable
     ABI: 4777.

*note METH_FASTCALL: 151b. | *note METH_KEYWORDS: 46d9.

     Extension of *note METH_FASTCALL: 151b. supporting also keyword
     arguments, with methods of type *note PyCFunctionFastWithKeywords:
     4790.  Keyword arguments are passed the same way as in the *note
     vectorcall protocol: 4f8.: there is an additional fourth *note
     PyObject: 311.* parameter which is a tuple representing the names
     of the keyword arguments (which are guaranteed to be strings) or
     possibly ‘NULL’ if there are no keywords.  The values of the
     keyword arguments are stored in the 'args' array, after the
     positional arguments.

     在 3.7 版被加入.

 -- C 巨集: METH_METHOD

     Can only be used in the combination with other flags: *note
     METH_METHOD | METH_FASTCALL | METH_KEYWORDS: 1584.

*note METH_METHOD: 914. | *note METH_FASTCALL: 151b. | *note METH_KEYWORDS: 46d9.

     Extension of *note METH_FASTCALL | METH_KEYWORDS: 4bf4. supporting
     the 'defining class', that is, the class that contains the method
     in question.  The defining class might be a superclass of
     ‘Py_TYPE(self)’.

     The method needs to be of type *note PyCMethod: 708, the same as
     for ‘METH_FASTCALL | METH_KEYWORDS’ with ‘defining_class’ argument
     added after ‘self’.

     在 3.9 版被加入.

 -- C 巨集: METH_NOARGS

     Methods without parameters don't need to check whether arguments
     are given if they are listed with the *note METH_NOARGS: 1443.
     flag.  They need to be of type *note PyCFunction: 13e2.  The first
     parameter is typically named 'self' and will hold a reference to
     the module or object instance.  In all cases the second parameter
     will be ‘NULL’.

     The function must have 2 parameters.  Since the second parameter is
     unused, *note Py_UNUSED: 1619. can be used to prevent a compiler
     warning.

 -- C 巨集: METH_O

     Methods with a single object argument can be listed with the *note
     METH_O: 1477. flag, instead of invoking *note PyArg_ParseTuple():
     517. with a ‘"O"’ argument.  They have the type *note PyCFunction:
     13e2, with the 'self' parameter, and a *note PyObject: 311.*
     parameter representing the single argument.

These two constants are not used to indicate the calling convention but
the binding when use with methods of classes.  These may not be used for
functions defined for modules.  At most one of these flags may be set
for any given method.

 -- C 巨集: METH_CLASS

     The method will be passed the type object as the first parameter
     rather than an instance of the type.  This is used to create 'class
     methods', similar to what is created when using the *note
     classmethod(): 14a. built-in function.

 -- C 巨集: METH_STATIC

     The method will be passed ‘NULL’ as the first parameter rather than
     an instance of the type.  This is used to create 'static methods',
     similar to what is created when using the *note staticmethod():
     358. built-in function.

One other constant controls whether a method is loaded in place of
another definition with the same method name.

 -- C 巨集: METH_COEXIST

     The method will be loaded in place of existing definitions.
     Without 'METH_COEXIST', the default is to skip repeated
     definitions.  Since slot wrappers are loaded before the method
     table, the existence of a 'sq_contains' slot, for example, would
     generate a wrapped method named *note __contains__(): 1e33. and
     preclude the loading of a corresponding PyCFunction with the same
     name.  With the flag defined, the PyCFunction will be loaded in
     place of the wrapper object and will co-exist with the slot.  This
     is helpful because calls to PyCFunctions are optimized more than
     wrapper object calls.

 -- C 函式: *note PyObject: 311. *PyCMethod_New (PyMethodDef *ml,
          PyObject *self, PyObject *module, PyTypeObject *cls)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.9 版本
     開始.'  Turn 'ml' into a Python *note callable: 27d4. object.  The
     caller must ensure that 'ml' outlives the *note callable: 27d4.
     Typically, 'ml' is defined as a static variable.

     The 'self' parameter will be passed as the 'self' argument to the C
     function in ‘ml->ml_meth’ when invoked.  'self' can be ‘NULL’.

     The *note callable: 27d4. object's ‘__module__’ attribute can be
     set from the given 'module' argument.  'module' should be a Python
     string, which will be used as name of the module the function is
     defined in.  If unavailable, it can be set to *note None: 61b. or
     ‘NULL’.

     也參考
     ......

     *note function.__module__: 1ded.

     The 'cls' parameter will be passed as the 'defining_class' argument
     to the C function.  Must be set if *note METH_METHOD: 914. is set
     on ‘ml->ml_flags’.

     在 3.9 版被加入.

 -- C 函式: *note PyObject: 311. *PyCFunction_NewEx (PyMethodDef *ml,
          PyObject *self, PyObject *module)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9.'  等價於
     ‘PyCMethod_New(ml, self, module, NULL)’。

 -- C 函式: *note PyObject: 311. *PyCFunction_New (PyMethodDef *ml,
          PyObject *self)
     '回傳值：新的參照。'' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.4 版本
     開始.'  等價於 ‘PyCMethod_New(ml, self, NULL, NULL)’。


File: python.info,  Node: Accessing attributes of extension types,  Prev: 實作函式與方法,  Up: 通用物件結構

7.12.2.3 Accessing attributes of extension types
................................................

 -- C 型別: type PyMemberDef
     ' 為 *note 穩定 ABI 的一部分: 4f9. （包含所有成員）.'  Structure
     which describes an attribute of a type which corresponds to a C
     struct member.  When defining a class, put a NULL-terminated array
     of these structures in the *note tp_members: 4707. slot.

     Its fields are, in order:

      -- C 成員函數: const char *name

          Name of the member.  A NULL value marks the end of a
          ‘PyMemberDef[]’ array.

          The string should be static, no copy is made of it.

      -- C 成員函數: int type

          The type of the member in the C struct.  See *note Member
          types: 1569. for the possible values.

      -- C 成員函數: *note Py_ssize_t: a03. offset

          The offset in bytes that the member is located on the type’s
          object struct.

      -- C 成員函數: int flags

          Zero or more of the *note Member flags: 4bfb, combined using
          bitwise OR.

      -- C 成員函數: const char *doc

          The docstring, or NULL. The string should be static, no copy
          is made of it.  Typically, it is defined using *note
          PyDoc_STR: 1710.

     By default (when *note flags: 4720. is ‘0’), members allow both
     read and write access.  Use the *note Py_READONLY: 537. flag for
     read-only access.  Certain types, like *note Py_T_STRING: 4bfd,
     imply *note Py_READONLY: 537.  Only *note Py_T_OBJECT_EX: 53a. (and
     legacy *note T_OBJECT: 539.) members can be deleted.  For
     heap-allocated types (created using *note PyType_FromSpec(): 523.
     or similar), ‘PyMemberDef’ may contain a definition for the special
     member ‘"__vectorcalloffset__"’, corresponding to *note
     tp_vectorcall_offset: 4973. in type objects.  These must be defined
     with ‘Py_T_PYSSIZET’ and ‘Py_READONLY’, for example:

          static PyMemberDef spam_type_members[] = {
              {"__vectorcalloffset__", Py_T_PYSSIZET,
               offsetof(Spam_object, vectorcall), Py_READONLY},
              {NULL}  /* Sentinel */
          };

     (You may need to ‘#include <stddef.h>’ for ‘offsetof()’.)

     The legacy offsets *note tp_dictoffset: 49d1. and *note
     tp_weaklistoffset: 92c. can be defined similarly using
     ‘"__dictoffset__"’ and ‘"__weaklistoffset__"’ members, but
     extensions are strongly encouraged to use *note
     Py_TPFLAGS_MANAGED_DICT: 31b. and *note Py_TPFLAGS_MANAGED_WEAKREF:
     500. instead.

     在 3.12 版的變更: ‘PyMemberDef’ is always available.  Previously,
     it required including ‘"structmember.h"’.

 -- C 函式: *note PyObject: 311. *PyMember_GetOne (const char *obj_addr,
          struct PyMemberDef *m)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Get an attribute belonging to
     the object at address 'obj_addr'.  The attribute is described by
     ‘PyMemberDef’ 'm'.  Returns ‘NULL’ on error.

     在 3.12 版的變更: ‘PyMember_GetOne’ is always available.
     Previously, it required including ‘"structmember.h"’.

 -- C 函式: int PyMember_SetOne (char *obj_addr, struct PyMemberDef *m,
          PyObject *o)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Set an attribute belonging to
     the object at address 'obj_addr' to object 'o'.  The attribute to
     set is described by ‘PyMemberDef’ 'm'.  Returns ‘0’ if successful
     and a negative value on failure.

     在 3.12 版的變更: ‘PyMember_SetOne’ is always available.
     Previously, it required including ‘"structmember.h"’.

* Menu:

* Member flags::
* Member types::
* Defining Getters and Setters::


File: python.info,  Node: Member flags,  Next: Member types,  Up: Accessing attributes of extension types

7.12.2.4 Member flags
.....................

The following flags can be used with *note PyMemberDef.flags: 4720.:

 -- C 巨集: Py_READONLY

     不可寫入。

 -- C 巨集: Py_AUDIT_READ

     Emit an ‘object.__getattr__’ *note audit event: 1773. before
     reading.

 -- C 巨集: Py_RELATIVE_OFFSET

     Indicates that the *note offset: 4bfa. of this ‘PyMemberDef’ entry
     indicates an offset from the subclass-specific data, rather than
     from ‘PyObject’.

     Can only be used as part of *note Py_tp_members: 4707. *note slot:
     4875. when creating a class using negative *note basicsize: 4ee.
     It is mandatory in that case.

     This flag is only used in *note PyType_Slot: 4875.  When setting
     *note tp_members: 4707. during class creation, Python clears it and
     sets *note PyMemberDef.offset: 4bfa. to the offset from the
     ‘PyObject’ struct.

在 3.10 版的變更: The ‘RESTRICTED’, ‘READ_RESTRICTED’ and
‘WRITE_RESTRICTED’ macros available with ‘#include "structmember.h"’ are
deprecated.  ‘READ_RESTRICTED’ and ‘RESTRICTED’ are equivalent to *note
Py_AUDIT_READ: 538.; ‘WRITE_RESTRICTED’ does nothing.

在 3.12 版的變更: The ‘READONLY’ macro was renamed to *note Py_READONLY:
537.  The ‘PY_AUDIT_READ’ macro was renamed with the ‘Py_’ prefix.  The
new names are now always available.  Previously, these required
‘#include "structmember.h"’.  The header is still available and it
provides the old names.


File: python.info,  Node: Member types,  Next: Defining Getters and Setters,  Prev: Member flags,  Up: Accessing attributes of extension types

7.12.2.5 Member types
.....................

*note PyMemberDef.type: 471f. can be one of the following macros
corresponding to various C types.  When the member is accessed in
Python, it will be converted to the equivalent Python type.  When it is
set from Python, it will be converted back to the C type.  If that is
not possible, an exception such as *note TypeError: 4dd. or *note
ValueError: 1e7. is raised.

Unless marked (D), attributes defined this way cannot be deleted using
e.g.  *note del: 16a9. or *note delattr(): 202b.

巨集名稱                             C type                            Python type
                                                                       
--------------------------------------------------------------------------------------------------
                                                                       
 -- C 巨集: Py_T_BYTE                char                              *note int: 23c.
                                                                       
                                                                       
 -- C 巨集: Py_T_SHORT               short                             *note int: 23c.
                                                                       
                                                                       
 -- C 巨集: Py_T_INT                 int                               *note int: 23c.
                                                                       
                                                                       
 -- C 巨集: Py_T_LONG                long                              *note int: 23c.
                                                                       
                                                                       
 -- C 巨集: Py_T_LONGLONG            long long                         *note int: 23c.
                                                                       
                                                                       
 -- C 巨集: Py_T_UBYTE               unsigned char                     *note int: 23c.
                                                                       
                                                                       
 -- C 巨集: Py_T_UINT                unsigned int                      *note int: 23c.
                                                                       
                                                                       
 -- C 巨集: Py_T_USHORT              unsigned short                    *note int: 23c.
                                                                       
                                                                       
 -- C 巨集: Py_T_ULONG               unsigned long                     *note int: 23c.
                                                                       
                                                                       
 -- C 巨集: Py_T_ULONGLONG           unsigned long long                *note int: 23c.
                                                                       
                                                                       
 -- C 巨集: Py_T_PYSSIZET            *note Py_ssize_t: a03.            *note int: 23c.
                                                                       
                                                                       
 -- C 巨集: Py_T_FLOAT               float                             *note float: 2c8.
                                                                       
                                                                       
 -- C 巨集: Py_T_DOUBLE              double                            *note float: 2c8.
                                                                       
                                                                       
 -- C 巨集: Py_T_BOOL                char （寫成 0 或 1）              *note bool: 40e.
                                                                       
                                                                       
 -- C 巨集: Py_T_STRING              const char* (*)                   *note str: 3f2. (RO)
                                                                       
                                                                       
 -- C 巨集: Py_T_STRING_INPLACE      const char[] (*)                  *note str: 3f2. (RO)
                                                                       
                                                                       
 -- C 巨集: Py_T_CHAR                char (0-127)                      *note str: 3f2. (**)
                                                                       
                                                                       
 -- C 巨集: Py_T_OBJECT_EX           *note PyObject: 311.*             *note object: a2f. (D)
                                                                       

     (*): Zero-terminated, UTF8-encoded C string.  With ‘Py_T_STRING’
     the C representation is a pointer; with ‘Py_T_STRING_INPLACE’ the
     string is stored directly in the structure.

     (**): String of length 1.  Only ASCII is accepted.

     (RO): Implies *note Py_READONLY: 537.

     (D): Can be deleted, in which case the pointer is set to ‘NULL’.
     Reading a ‘NULL’ pointer raises *note AttributeError: 2f6.

在 3.12 版被加入: In previous versions, the macros were only available
with ‘#include "structmember.h"’ and were named without the ‘Py_’ prefix
(e.g.  as ‘T_INT’).  The header is still available and contains the old
names, along with the following deprecated types:

 -- C 巨集: T_OBJECT

     Like ‘Py_T_OBJECT_EX’, but ‘NULL’ is converted to ‘None’.  This
     results in surprising behavior in Python: deleting the attribute
     effectively sets it to ‘None’.

 -- C 巨集: T_NONE

     Always ‘None’.  Must be used with *note Py_READONLY: 537.


File: python.info,  Node: Defining Getters and Setters,  Prev: Member types,  Up: Accessing attributes of extension types

7.12.2.6 Defining Getters and Setters
.....................................

 -- C 型別: type PyGetSetDef
     ' 為 *note 穩定 ABI 的一部分: 4f9. （包含所有成員）.'  Structure to
     define property-like access for a type.  See also description of
     the *note PyTypeObject.tp_getset: 470c. slot.

      -- C 成員函數: const char *name

          屬性名稱

      -- C 成員函數: *note getter: 48ca. get

          C function to get the attribute.

      -- C 成員函數: *note setter: 48d8. set

          Optional C function to set or delete the attribute.  If
          ‘NULL’, the attribute is read-only.

      -- C 成員函數: const char *doc

          可選的文件字串

      -- C 成員函數: void *closure

          Optional user data pointer, providing additional data for
          getter and setter.

 -- C 型別: typedef *note PyObject: 311. *(*getter)(*note PyObject:
          311.*, void*)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  The ‘get’ function takes one
     *note PyObject: 311.* parameter (the instance) and a user data
     pointer (the associated ‘closure’):

     It should return a new reference on success or ‘NULL’ with a set
     exception on failure.

 -- C 型別: typedef int (*setter)(*note PyObject: 311.*, *note PyObject:
          311.*, void*)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  ‘set’ functions take two *note
     PyObject: 311.* parameters (the instance and the value to be set)
     and a user data pointer (the associated ‘closure’):

     In case the attribute should be deleted the second parameter is
     ‘NULL’.  Should return ‘0’ on success or ‘-1’ with a set exception
     on failure.


File: python.info,  Node: 型別物件<2>,  Next: Number Object Structures,  Prev: 通用物件結構,  Up: Object Implementation Support

7.12.3 型別物件
---------------

Perhaps one of the most important structures of the Python object system
is the structure that defines a new type: the *note PyTypeObject: a48.
structure.  Type objects can be handled using any of the ‘PyObject_*’ or
‘PyType_*’ functions, but do not offer much that's interesting to most
Python applications.  These objects are fundamental to how objects
behave, so they are very important to the interpreter itself and to any
extension module that implements new types.

Type objects are fairly large compared to most of the standard types.
The reason for the size is that each type object stores a large number
of values, mostly C function pointers, each of which implements a small
part of the type's functionality.  The fields of the type object are
examined in detail in this section.  The fields will be described in the
order in which they occur in the structure.

In addition to the following quick reference, the *note 範例: 4c16.
section provides at-a-glance insight into the meaning and use of *note
PyTypeObject: a48.

* Menu:

* Quick Reference::
* PyTypeObject Definition::
* PyObject Slots::
* PyVarObject Slots::
* PyTypeObject Slots::
* Static Types::
* Heap Types::


File: python.info,  Node: Quick Reference,  Next: PyTypeObject Definition,  Up: 型別物件<2>

7.12.3.1 Quick Reference
........................

* Menu:

* "tp slots"::
* sub-slots::
* slot typedefs::


File: python.info,  Node: "tp slots",  Next: sub-slots,  Up: Quick Reference

7.12.3.2 "tp slots"
...................

PyTypeObject Slot      *note Type: 4c1a.      special                Info
(1)                                           methods/attrs          (2)
                                                                     
---------------------------------------------------------------------------------------------
                                                                     
O                      T                      D                      I
                                                                     
                                                                                       
<R>                    const char *           __name__               X     X
*note tp_name: 17f5.                                                       

*note tp_basicsize: 92b.*note Py_ssize_t: a03.                       X     X           X
                                                                                       
                                                                                       
*note tp_itemsize: 1e46.*note Py_ssize_t: a03.                             X           X
                                                                                       
                                                                                       
*note tp_dealloc: 4704.*note destructor: 48c5.                       X     X           X
                                                                                       
                                                                                       
*note tp_vectorcall_offset: 4973.*note Py_ssize_t: a03.                    X           X
                                                                                       
                                                                                       
(*note tp_getattr: 4722.)*note getattrfunc: 48c6.__getattribute__,                     G
                                              __getattr__                              
                                              
                                                                                       
(*note tp_setattr: 4723.)*note setattrfunc: 48d6.__setattr__,                          G
                                              __delattr__                              
                                              
                                                                                       
*note tp_as_async: e71.*note PyAsyncMethods: 49cf.*note sub-slots: 4c1b.               %
                       *                                                               
                       
                                                                                       
*note tp_repr: 4719.   *note reprfunc: 48d4.  __repr__               X     X           X
                                                                                       
                                                                                       
*note tp_as_number: 92f.*note PyNumberMethods: 138b.*note sub-slots: 4c1b.             %
                       *                                                               
                       
                                                                                       
*note tp_as_sequence: 4c1c.*note PySequenceMethods: 4729.*note sub-slots: 4c1b.        %
                       *                                                               
                       
                                                                                       
*note tp_as_mapping: 4c1d.*note PyMappingMethods: 472a.*note sub-slots: 4c1b.          %
                       *                                                               
                       
                                                                                       
*note tp_hash: 472b.   *note hashfunc: 48cb.  __hash__               X                 G
                                                                                       
                                                                                       
*note tp_call: 4ff.    *note ternaryfunc: 48db.__call__                    X           X
                                                                                       
                                                                                       
*note tp_str: 471a.    *note reprfunc: 48d4.  __str__                X                 X
                                                                                       
                                                                                       
*note tp_getattro: 15ec.*note getattrofunc: 48c7.__getattribute__,   X     X           G
                                              __getattr__                              
                                              
                                                                                       
*note tp_setattro: 471d.*note setattrofunc: 48d7.__setattr__,        X     X           G
                                              __delattr__                              
                                              
                                                                                       
*note tp_as_buffer: 92d.*note PyBufferProcs: 49d7.                                     %
                       *                                                               
                       
                                                                                       
*note tp_flags: 17c0.  unsigned long                                 X     X           ?
                                                                                       
                                                                                       
*note tp_doc: 4700.    const char *           __doc__                X     X
                                                                           
                                                                                       
*note tp_traverse: 721.*note traverseproc: 48dc.                           X           G
                                                                                       
                                                                                       
*note tp_clear: 4717.  *note inquiry: 48cd.                                X           G
                                                                                       
                                                                                       
*note tp_richcompare: 4725.*note richcmpfunc: 48d5.__lt__, __le__,   X                 G
                                              __eq__, __ne__,                          
                                              __gt__, __ge__
                                              
                                                                                       
(*note tp_weaklistoffset: 92c.)*note Py_ssize_t: a03.                      X           ?
                                                                                       
                                                                                       
*note tp_iter: 145c.   *note getiterfunc: 48c9.__iter__                                X
                                                                                       
                                                                                       
*note tp_iternext: 145d.*note iternextfunc: 48ce.__next__                              X
                                                                                       
                                                                                       
*note tp_methods: 4709.*note PyMethodDef: 1446.                      X     X
                       []                                                  
                       
                                                                                       
*note tp_members: 4707.*note PyMemberDef: 4f5.                             X
                       []                                                  
                       
                                                                                       
*note tp_getset: 470c. *note PyGetSetDef: b5f.                       X     X
                       []                                                  
                       
                                                                                       
*note tp_base: 4710.   *note PyTypeObject: a48.__base__                          X
                       *                                                         
                       
                                                                                       
*note tp_dict: 161c.   *note PyObject: 311.   __dict__                           ?
                       *                                                         
                       
                                                                                       
*note tp_descr_get: 4c1e.*note descrgetfunc: 48c3.__get__                              X
                                                                                       
                                                                                       
*note tp_descr_set: 17f9.*note descrsetfunc: 48c4.__set__, __delete__                  X
                                                                                       
                                                                                       
(*note tp_dictoffset: 49d1.)*note Py_ssize_t: a03.                         X           ?
                                                                                       
                                                                                       
*note tp_init: 527.    *note initproc: 48cc.  __init__               X     X           X
                                                                                       
                                                                                       
*note tp_alloc: 4706.  *note allocfunc: 48c1.                        X           ?     ?
                                                                                       
                                                                                       
*note tp_new: 525.     *note newfunc: 48d0.   __new__                X     X     ?     ?
                                                                                       
                                                                                       
*note tp_free: 4705.   *note freefunc: 4ac6.                         X     X     ?     ?
                                                                                       
                                                                                       
*note tp_is_gc: 4c1f.  *note inquiry: 48cd.                                X           X
                                                                                       
                                                                                       
<*note tp_bases: 4c20.>*note PyObject: 311.   __bases__                          ~
                       *                                                         
                       
                                                                                       
<*note tp_mro: 49d4.>  *note PyObject: 311.   __mro__                            ~
                       *                                                         
                       
                                                                                       
[*note tp_cache: 49d5.]*note PyObject: 311.
                       *
                       
                                                                                       
[*note tp_subclasses: 518.]void *             __subclasses__
                                              
                                                                                       
[*note tp_weaklist: 49d6.]*note PyObject: 311.
                       *
                       
                                                                                       
(*note tp_del: 4c21.)  *note destructor: 48c5.
                       
                                                                                       
[*note tp_version_tag: 4c22.]unsigned int
                       
                                                                                       
*note tp_finalize: a49.*note destructor: 48c5.__del__                                  X
                                                                                       
                                                                                       
*note tp_vectorcall: 49d3.*note vectorcallfunc: 4fd.
                       
                                                                                       
[*note tp_watched: 4c23.]unsigned char
                       

   ---------- Footnotes ----------

   (1) '()': A slot name in parentheses indicates it is (effectively)
deprecated.

'<>': Names in angle brackets should be initially set to ‘NULL’ and
treated as read-only.

'[]': Names in square brackets are for internal use only.

'<R>' (as a prefix) means the field is required (must be non-‘NULL’).

   (2) Columns:

'"O"': set on ‘PyBaseObject_Type’

'"T"': set on *note PyType_Type: 4f3.

'"D"': default (if slot is set to ‘NULL’)

     X - PyType_Ready sets this value if it is NULL
     ~ - PyType_Ready always sets this value (it should be NULL)
     ? - PyType_Ready may set this value depending on other slots

     Also see the inheritance column ("I").

'"I"': inheritance

     X - type slot is inherited via *PyType_Ready* if defined with a *NULL* value
     % - the slots of the sub-struct are inherited individually
     G - inherited, but only in combination with other slots; see the slot's description
     ? - it's complicated; see the slot's description

Note that some slots are effectively inherited through the normal
attribute lookup chain.


File: python.info,  Node: sub-slots,  Next: slot typedefs,  Prev: "tp slots",  Up: Quick Reference

7.12.3.3 sub-slots
..................

Slot                           *note Type: 4c1a.     special
                                                     methods
                                                     
----------------------------------------------------------------------
                                                     
*note am_await: 4c25.          *note unaryfunc: 48dd.__await__
                                                     
                                                     
*note am_aiter: 4c26.          *note unaryfunc: 48dd.__aiter__
                                                     
                                                     
*note am_anext: 4c27.          *note unaryfunc: 48dd.__anext__
                                                     
                                                     
*note am_send: 4c28.           *note sendfunc: 4c29.
                               
                                                     
                                                     
*note nb_add: 49c8.            *note binaryfunc: 48c2.__add__
                                                     __radd__
                                                     
                                                     
*note nb_inplace_add: 4c2a.    *note binaryfunc: 48c2.__iadd__
                                                     
                                                     
*note nb_subtract: 4c2b.       *note binaryfunc: 48c2.__sub__
                                                     __rsub__
                                                     
                                                     
*note nb_inplace_subtract: 4c2c.*note binaryfunc: 48c2.__isub__
                                                     
                                                     
*note nb_multiply: 4c2d.       *note binaryfunc: 48c2.__mul__
                                                     __rmul__
                                                     
                                                     
*note nb_inplace_multiply: 4c2e.*note binaryfunc: 48c2.__imul__
                                                     
                                                     
*note nb_remainder: 4c2f.      *note binaryfunc: 48c2.__mod__
                                                     __rmod__
                                                     
                                                     
*note nb_inplace_remainder: 4c30.*note binaryfunc: 48c2.__imod__
                                                     
                                                     
*note nb_divmod: 4c31.         *note binaryfunc: 48c2.__divmod__
                                                     __rdivmod__
                                                     
                                                     
*note nb_power: 4c32.          *note ternaryfunc: 48db.__pow__
                                                     __rpow__
                                                     
                                                     
*note nb_inplace_power: 4c33.  *note ternaryfunc: 48db.__ipow__
                                                     
                                                     
*note nb_negative: 4c34.       *note unaryfunc: 48dd.__neg__
                                                     
                                                     
*note nb_positive: 4c35.       *note unaryfunc: 48dd.__pos__
                                                     
                                                     
*note nb_absolute: 4c36.       *note unaryfunc: 48dd.__abs__
                                                     
                                                     
*note nb_bool: 4c37.           *note inquiry: 48cd.  __bool__
                                                     
                                                     
*note nb_invert: 4c38.         *note unaryfunc: 48dd.__invert__
                                                     
                                                     
*note nb_lshift: 4c39.         *note binaryfunc: 48c2.__lshift__
                                                     __rlshift__
                                                     
                                                     
*note nb_inplace_lshift: 4c3a. *note binaryfunc: 48c2.__ilshift__
                                                     
                                                     
*note nb_rshift: 4c3b.         *note binaryfunc: 48c2.__rshift__
                                                     __rrshift__
                                                     
                                                     
*note nb_inplace_rshift: 4c3c. *note binaryfunc: 48c2.__irshift__
                                                     
                                                     
*note nb_and: 4c3d.            *note binaryfunc: 48c2.__and__
                                                     __rand__
                                                     
                                                     
*note nb_inplace_and: 4c3e.    *note binaryfunc: 48c2.__iand__
                                                     
                                                     
*note nb_xor: 4c3f.            *note binaryfunc: 48c2.__xor__
                                                     __rxor__
                                                     
                                                     
*note nb_inplace_xor: 4c40.    *note binaryfunc: 48c2.__ixor__
                                                     
                                                     
*note nb_or: 4c41.             *note binaryfunc: 48c2.__or__ __ror__
                                                     
                                                     
*note nb_inplace_or: 4c42.     *note binaryfunc: 48c2.__ior__
                                                     
                                                     
*note nb_int: 4c43.            *note unaryfunc: 48dd.__int__
                                                     
                                                     
*note nb_reserved: 4c44.       void *
                               
                                                     
*note nb_float: 4c45.          *note unaryfunc: 48dd.__float__
                                                     
                                                     
*note nb_floor_divide: 4c46.   *note binaryfunc: 48c2.__floordiv__
                                                     
                                                     
*note nb_inplace_floor_divide: 4c47.*note binaryfunc: 48c2.__ifloordiv__
                                                     
                                                     
*note nb_true_divide: 4c48.    *note binaryfunc: 48c2.__truediv__
                                                     
                                                     
*note nb_inplace_true_divide: 4c49.*note binaryfunc: 48c2.__itruediv__
                                                     
                                                     
*note nb_index: 138a.          *note unaryfunc: 48dd.__index__
                                                     
                                                     
*note nb_matrix_multiply: 4c4a.*note binaryfunc: 48c2.__matmul__
                                                     __rmatmul__
                                                     
                                                     
*note nb_inplace_matrix_multiply: 4c4b.*note binaryfunc: 48c2.__imatmul__
                                                     
                                                     
                                                     
*note mp_length: 4c4c.         *note lenfunc: 48cf.  __len__
                                                     
                                                     
*note mp_subscript: 1830.      *note binaryfunc: 48c2.__getitem__
                                                     
                                                     
*note mp_ass_subscript: 4c4d.  *note objobjargproc: 48d1.__setitem__,
                                                     __delitem__
                                                     
                                                     
                                                     
*note sq_length: 49d0.         *note lenfunc: 48cf.  __len__
                                                     
                                                     
*note sq_concat: 4c4e.         *note binaryfunc: 48c2.__add__
                                                     
                                                     
*note sq_repeat: 4c4f.         *note ssizeargfunc: 48d9.__mul__
                                                     
                                                     
*note sq_item: 182f.           *note ssizeargfunc: 48d9.__getitem__
                                                     
                                                     
*note sq_ass_item: 4c50.       *note ssizeobjargproc: 48da.__setitem__
                                                     __delitem__
                                                     
                                                     
*note sq_contains: 4c51.       *note objobjproc: 48d2.__contains__
                                                     
                                                     
*note sq_inplace_concat: 4c52. *note binaryfunc: 48c2.__iadd__
                                                     
                                                     
*note sq_inplace_repeat: 4c53. *note ssizeargfunc: 48d9.__imul__
                                                     
                                                     
                                                     
*note bf_getbuffer: 706.       *note getbufferproc(): 48c8.
                               
                                                     
*note bf_releasebuffer: 707.   *note releasebufferproc(): 48d3.
                               


File: python.info,  Node: slot typedefs,  Prev: sub-slots,  Up: Quick Reference

7.12.3.4 slot typedefs
......................

typedef                           Parameter Types                   Return Type
                                                                    
-----------------------------------------------------------------------------------------------
                                                                    
*note allocfunc: 48c1.                 *note PyTypeObject: a48. *   *note PyObject: 311. *
                                       *note Py_ssize_t: a03.       
                                  
                                                                    
*note destructor: 48c5.           *note PyObject: 311. *            void
                                                                    
                                                                    
*note freefunc: 4ac6.             void *                            void
                                                                    
                                                                    
*note traverseproc: 48dc.              *note PyObject: 311. *       int
                                       *note visitproc: 48de.       
                                       void *
                                  
                                                                    
*note newfunc: 48d0.                   *note PyObject: 311. *       *note PyObject: 311. *
                                       *note PyObject: 311. *       
                                       *note PyObject: 311. *
                                  
                                                                    
*note initproc: 48cc.                  *note PyObject: 311. *       int
                                       *note PyObject: 311. *       
                                       *note PyObject: 311. *
                                  
                                                                    
*note reprfunc: 48d4.             *note PyObject: 311. *            *note PyObject: 311. *
                                                                    
                                                                    
*note getattrfunc: 48c6.               *note PyObject: 311. *       *note PyObject: 311. *
                                       const char *                 
                                  
                                                                    
*note setattrfunc: 48d6.               *note PyObject: 311. *       int
                                       const char *                 
                                       *note PyObject: 311. *
                                  
                                                                    
*note getattrofunc: 48c7.              *note PyObject: 311. *       *note PyObject: 311. *
                                       *note PyObject: 311. *       
                                  
                                                                    
*note setattrofunc: 48d7.              *note PyObject: 311. *       int
                                       *note PyObject: 311. *       
                                       *note PyObject: 311. *
                                  
                                                                    
*note descrgetfunc: 48c3.              *note PyObject: 311. *       *note PyObject: 311. *
                                       *note PyObject: 311. *       
                                       *note PyObject: 311. *
                                  
                                                                    
*note descrsetfunc: 48c4.              *note PyObject: 311. *       int
                                       *note PyObject: 311. *       
                                       *note PyObject: 311. *
                                  
                                                                    
*note hashfunc: 48cb.             *note PyObject: 311. *            Py_hash_t
                                                                    
                                                                    
*note richcmpfunc: 48d5.               *note PyObject: 311. *       *note PyObject: 311. *
                                       *note PyObject: 311. *       
                                       int
                                  
                                                                    
*note getiterfunc: 48c9.          *note PyObject: 311. *            *note PyObject: 311. *
                                                                    
                                                                    
*note iternextfunc: 48ce.         *note PyObject: 311. *            *note PyObject: 311. *
                                                                    
                                                                    
*note lenfunc: 48cf.              *note PyObject: 311. *            *note Py_ssize_t: a03.
                                                                    
                                                                    
*note getbufferproc: 48c8.             *note PyObject: 311. *       int
                                       *note Py_buffer: 6fc. *      
                                       int
                                  
                                                                    
*note releasebufferproc: 48d3.         *note PyObject: 311. *       void
                                       *note Py_buffer: 6fc. *      
                                  
                                                                    
*note inquiry: 48cd.              *note PyObject: 311. *            int
                                                                    
                                                                    
*note unaryfunc: 48dd.                 *note PyObject: 311. *       *note PyObject: 311. *
                                                                    
                                                                    
*note binaryfunc: 48c2.                *note PyObject: 311. *       *note PyObject: 311. *
                                       *note PyObject: 311. *       
                                  
                                                                    
*note ternaryfunc: 48db.               *note PyObject: 311. *       *note PyObject: 311. *
                                       *note PyObject: 311. *       
                                       *note PyObject: 311. *
                                  
                                                                    
*note ssizeargfunc: 48d9.              *note PyObject: 311. *       *note PyObject: 311. *
                                       *note Py_ssize_t: a03.       
                                  
                                                                    
*note ssizeobjargproc: 48da.           *note PyObject: 311. *       int
                                       *note Py_ssize_t: a03.       
                                       *note PyObject: 311. *
                                  
                                                                    
*note objobjproc: 48d2.                *note PyObject: 311. *       int
                                       *note PyObject: 311. *       
                                  
                                                                    
*note objobjargproc: 48d1.             *note PyObject: 311. *       int
                                       *note PyObject: 311. *       
                                       *note PyObject: 311. *
                                  

更多細節請見下方的 *note Slot Type typedefs: 4c55.。


File: python.info,  Node: PyTypeObject Definition,  Next: PyObject Slots,  Prev: Quick Reference,  Up: 型別物件<2>

7.12.3.5 PyTypeObject Definition
................................

The structure definition for *note PyTypeObject: a48. can be found in
‘Include/object.h’.  For convenience of reference, this repeats the
definition found there:

     typedef struct _typeobject {
         PyObject_VAR_HEAD
         const char *tp_name; /* For printing, in format "<module>.<name>" */
         Py_ssize_t tp_basicsize, tp_itemsize; /* For allocation */

         /* Methods to implement standard operations */

         destructor tp_dealloc;
         Py_ssize_t tp_vectorcall_offset;
         getattrfunc tp_getattr;
         setattrfunc tp_setattr;
         PyAsyncMethods *tp_as_async; /* formerly known as tp_compare (Python 2)
                                         or tp_reserved (Python 3) */
         reprfunc tp_repr;

         /* Method suites for standard classes */

         PyNumberMethods *tp_as_number;
         PySequenceMethods *tp_as_sequence;
         PyMappingMethods *tp_as_mapping;

         /* More standard operations (here for binary compatibility) */

         hashfunc tp_hash;
         ternaryfunc tp_call;
         reprfunc tp_str;
         getattrofunc tp_getattro;
         setattrofunc tp_setattro;

         /* Functions to access object as input/output buffer */
         PyBufferProcs *tp_as_buffer;

         /* Flags to define presence of optional/expanded features */
         unsigned long tp_flags;

         const char *tp_doc; /* Documentation string */

         /* Assigned meaning in release 2.0 */
         /* call function for all accessible objects */
         traverseproc tp_traverse;

         /* delete references to contained objects */
         inquiry tp_clear;

         /* Assigned meaning in release 2.1 */
         /* rich comparisons */
         richcmpfunc tp_richcompare;

         /* weak reference enabler */
         Py_ssize_t tp_weaklistoffset;

         /* Iterators */
         getiterfunc tp_iter;
         iternextfunc tp_iternext;

         /* Attribute descriptor and subclassing stuff */
         struct PyMethodDef *tp_methods;
         struct PyMemberDef *tp_members;
         struct PyGetSetDef *tp_getset;
         // Strong reference on a heap type, borrowed reference on a static type
         struct _typeobject *tp_base;
         PyObject *tp_dict;
         descrgetfunc tp_descr_get;
         descrsetfunc tp_descr_set;
         Py_ssize_t tp_dictoffset;
         initproc tp_init;
         allocfunc tp_alloc;
         newfunc tp_new;
         freefunc tp_free; /* Low-level free-memory routine */
         inquiry tp_is_gc; /* For PyObject_IS_GC */
         PyObject *tp_bases;
         PyObject *tp_mro; /* method resolution order */
         PyObject *tp_cache;
         PyObject *tp_subclasses;
         PyObject *tp_weaklist;
         destructor tp_del;

         /* Type attribute cache version tag. Added in version 2.6 */
         unsigned int tp_version_tag;

         destructor tp_finalize;
         vectorcallfunc tp_vectorcall;

         /* bitset of which type-watchers care about this type */
         unsigned char tp_watched;
     } PyTypeObject;


File: python.info,  Node: PyObject Slots,  Next: PyVarObject Slots,  Prev: PyTypeObject Definition,  Up: 型別物件<2>

7.12.3.6 PyObject Slots
.......................

The type object structure extends the *note PyVarObject: 3f79.
structure.  The *note ob_size: 48af. field is used for dynamic types
(created by ‘type_new()’, usually called from a class statement).  Note
that *note PyType_Type: 4f3. (the metatype) initializes *note
tp_itemsize: 1e46, which means that its instances (i.e.  type objects)
'must' have the *note ob_size: 48af. field.

 -- C 成員函數: *note Py_ssize_t: a03. *note PyObject: 311.ob_refcnt
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This is the type object's
     reference count, initialized to ‘1’ by the ‘PyObject_HEAD_INIT’
     macro.  Note that for *note statically allocated type objects: 723,
     the type's instances (objects whose *note ob_type: 4702. points
     back to the type) do 'not' count as references.  But for *note
     dynamically allocated type objects: 909, the instances 'do' count
     as references.

     'Inheritance:'

     This field is not inherited by subtypes.

 -- C 成員函數: *note PyTypeObject: a48. **note PyObject: 311.ob_type
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  This is the type's type, in
     other words its metatype.  It is initialized by the argument to the
     ‘PyObject_HEAD_INIT’ macro, and its value should normally be
     ‘&PyType_Type’.  However, for dynamically loadable extension
     modules that must be usable on Windows (at least), the compiler
     complains that this is not a valid initializer.  Therefore, the
     convention is to pass ‘NULL’ to the ‘PyObject_HEAD_INIT’ macro and
     to initialize this field explicitly at the start of the module's
     initialization function, before doing anything else.  This is
     typically done like this:

          Foo_Type.ob_type = &PyType_Type;

     This should be done before any instances of the type are created.
     *note PyType_Ready(): 722. checks if *note ob_type: 4702. is
     ‘NULL’, and if so, initializes it to the *note ob_type: 4702. field
     of the base class.  *note PyType_Ready(): 722. will not change this
     field if it is non-zero.

     'Inheritance:'

     This field is inherited by subtypes.


File: python.info,  Node: PyVarObject Slots,  Next: PyTypeObject Slots,  Prev: PyObject Slots,  Up: 型別物件<2>

7.12.3.7 PyVarObject Slots
..........................

 -- C 成員函數: *note Py_ssize_t: a03. *note PyVarObject: 3f79.ob_size
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  For *note statically allocated
     type objects: 723, this should be initialized to zero.  For *note
     dynamically allocated type objects: 909, this field has a special
     internal meaning.

     'Inheritance:'

     This field is not inherited by subtypes.


File: python.info,  Node: PyTypeObject Slots,  Next: Static Types,  Prev: PyVarObject Slots,  Up: 型別物件<2>

7.12.3.8 PyTypeObject Slots
...........................

Each slot has a section describing inheritance.  If *note
PyType_Ready(): 722. may set a value when the field is set to ‘NULL’
then there will also be a "Default" section.  (Note that many fields set
on ‘PyBaseObject_Type’ and *note PyType_Type: 4f3. effectively act as
defaults.)

 -- C 成員函數: const char **note PyTypeObject: a48.tp_name

     Pointer to a NUL-terminated string containing the name of the type.
     For types that are accessible as module globals, the string should
     be the full module name, followed by a dot, followed by the type
     name; for built-in types, it should be just the type name.  If the
     module is a submodule of a package, the full package name is part
     of the full module name.  For example, a type named ‘T’ defined in
     module ‘M’ in subpackage ‘Q’ in package ‘P’ should have the *note
     tp_name: 17f5. initializer ‘"P.Q.M.T"’.

     For *note dynamically allocated type objects: 909, this should just
     be the type name, and the module name explicitly stored in the type
     dict as the value for key ‘'__module__'’.

     For *note statically allocated type objects: 723, the 'tp_name'
     field should contain a dot.  Everything before the last dot is made
     accessible as the ‘__module__’ attribute, and everything after the
     last dot is made accessible as the *note __name__: 1416. attribute.

     If no dot is present, the entire *note tp_name: 17f5. field is made
     accessible as the *note __name__: 1416. attribute, and the
     ‘__module__’ attribute is undefined (unless explicitly set in the
     dictionary, as explained above).  This means your type will be
     impossible to pickle.  Additionally, it will not be listed in
     module documentations created with pydoc.

     This field must not be ‘NULL’.  It is the only required field in
     *note PyTypeObject(): a48. (other than potentially *note
     tp_itemsize: 1e46.).

     'Inheritance:'

     This field is not inherited by subtypes.

 -- C 成員函數: *note Py_ssize_t: a03. *note PyTypeObject:
          a48.tp_basicsize
 -- C 成員函數: *note Py_ssize_t: a03. *note PyTypeObject:
          a48.tp_itemsize

     These fields allow calculating the size in bytes of instances of
     the type.

     There are two kinds of types: types with fixed-length instances
     have a zero *note tp_itemsize: 1e46. field, types with
     variable-length instances have a non-zero *note tp_itemsize: 1e46.
     field.  For a type with fixed-length instances, all instances have
     the same size, given in *note tp_basicsize: 92b.

     For a type with variable-length instances, the instances must have
     an *note ob_size: 48af. field, and the instance size is *note
     tp_basicsize: 92b. plus N times *note tp_itemsize: 1e46, where N is
     the "length" of the object.  The value of N is typically stored in
     the instance's *note ob_size: 48af. field.  There are exceptions:
     for example, ints use a negative *note ob_size: 48af. to indicate a
     negative number, and N is ‘abs(ob_size)’ there.  Also, the presence
     of an *note ob_size: 48af. field in the instance layout doesn't
     mean that the instance structure is variable-length (for example,
     the structure for the list type has fixed-length instances, yet
     those instances have a meaningful *note ob_size: 48af. field).

     The basic size includes the fields in the instance declared by the
     macro *note PyObject_HEAD: 1271. or *note PyObject_VAR_HEAD: 4bef.
     (whichever is used to declare the instance struct) and this in turn
     includes the ‘_ob_prev’ and ‘_ob_next’ fields if they are present.
     This means that the only correct way to get an initializer for the
     *note tp_basicsize: 92b. is to use the ‘sizeof’ operator on the
     struct used to declare the instance layout.  The basic size does
     not include the GC header size.

     A note about alignment: if the variable items require a particular
     alignment, this should be taken care of by the value of *note
     tp_basicsize: 92b.  Example: suppose a type implements an array of
     ‘double’.  *note tp_itemsize: 1e46. is ‘sizeof(double)’.  It is the
     programmer's responsibility that *note tp_basicsize: 92b. is a
     multiple of ‘sizeof(double)’ (assuming this is the alignment
     requirement for ‘double’).

     For any type with variable-length instances, this field must not be
     ‘NULL’.

     'Inheritance:'

     These fields are inherited separately by subtypes.  If the base
     type has a non-zero *note tp_itemsize: 1e46, it is generally not
     safe to set *note tp_itemsize: 1e46. to a different non-zero value
     in a subtype (though this depends on the implementation of the base
     type).

 -- C 成員函數: *note destructor: 48c5. *note PyTypeObject:
          a48.tp_dealloc

     A pointer to the instance destructor function.  This function must
     be defined unless the type guarantees that its instances will never
     be deallocated (as is the case for the singletons ‘None’ and
     ‘Ellipsis’).  The function signature is:

          void tp_dealloc(PyObject *self);

     The destructor function is called by the *note Py_DECREF(): 515.
     and *note Py_XDECREF(): 733. macros when the new reference count is
     zero.  At this point, the instance is still in existence, but there
     are no references to it.  The destructor function should free all
     references which the instance owns, free all memory buffers owned
     by the instance (using the freeing function corresponding to the
     allocation function used to allocate the buffer), and call the
     type's *note tp_free: 4705. function.  If the type is not
     subtypable (doesn't have the *note Py_TPFLAGS_BASETYPE: 470a. flag
     bit set), it is permissible to call the object deallocator directly
     instead of via *note tp_free: 4705.  The object deallocator should
     be the one used to allocate the instance; this is normally *note
     PyObject_Del(): 1440. if the instance was allocated using *note
     PyObject_New: 929. or *note PyObject_NewVar: 92a, or *note
     PyObject_GC_Del(): 1473. if the instance was allocated using *note
     PyObject_GC_New: a45. or *note PyObject_GC_NewVar: a46.

     If the type supports garbage collection (has the *note
     Py_TPFLAGS_HAVE_GC: 720. flag bit set), the destructor should call
     *note PyObject_GC_UnTrack(): 1475. before clearing any member
     fields.

          static void foo_dealloc(foo_object *self) {
              PyObject_GC_UnTrack(self);
              Py_CLEAR(self->ref);
              Py_TYPE(self)->tp_free((PyObject *)self);
          }

     Finally, if the type is heap allocated (*note Py_TPFLAGS_HEAPTYPE:
     854.), the deallocator should release the owned reference to its
     type object (via *note Py_DECREF(): 515.) after calling the type
     deallocator.  In order to avoid dangling pointers, the recommended
     way to achieve this is:

          static void foo_dealloc(foo_object *self) {
              PyTypeObject *tp = Py_TYPE(self);
              // free references and buffers here
              tp->tp_free(self);
              Py_DECREF(tp);
          }

     'Inheritance:'

     This field is inherited by subtypes.

 -- C 成員函數: *note Py_ssize_t: a03. *note PyTypeObject:
          a48.tp_vectorcall_offset

     An optional offset to a per-instance function that implements
     calling the object using the *note vectorcall protocol: 4f8, a more
     efficient alternative of the simpler *note tp_call: 4ff.

     This field is only used if the flag *note
     Py_TPFLAGS_HAVE_VECTORCALL: 4fa. is set.  If so, this must be a
     positive integer containing the offset in the instance of a *note
     vectorcallfunc: 4fd. pointer.

     The 'vectorcallfunc' pointer may be ‘NULL’, in which case the
     instance behaves as if *note Py_TPFLAGS_HAVE_VECTORCALL: 4fa. was
     not set: calling the instance falls back to *note tp_call: 4ff.

     Any class that sets ‘Py_TPFLAGS_HAVE_VECTORCALL’ must also set
     *note tp_call: 4ff. and make sure its behaviour is consistent with
     the 'vectorcallfunc' function.  This can be done by setting
     'tp_call' to *note PyVectorcall_Call(): 4fc.

     在 3.8 版的變更: Before version 3.8, this slot was named
     ‘tp_print’.  In Python 2.x, it was used for printing to a file.  In
     Python 3.0 to 3.7, it was unused.

     在 3.12 版的變更: Before version 3.12, it was not recommended for
     *note mutable heap types: 909. to implement the vectorcall
     protocol.  When a user sets *note __call__: 4fe. in Python code,
     only 'tp_call' is updated, likely making it inconsistent with the
     vectorcall function.  Since 3.12, setting ‘__call__’ will disable
     vectorcall optimization by clearing the *note
     Py_TPFLAGS_HAVE_VECTORCALL: 4fa. flag.

     'Inheritance:'

     This field is always inherited.  However, the *note
     Py_TPFLAGS_HAVE_VECTORCALL: 4fa. flag is not always inherited.  If
     it's not set, then the subclass won't use *note vectorcall: 4f8,
     except when *note PyVectorcall_Call(): 4fc. is explicitly called.

 -- C 成員函數: *note getattrfunc: 48c6. *note PyTypeObject:
          a48.tp_getattr

     An optional pointer to the get-attribute-string function.

     This field is deprecated.  When it is defined, it should point to a
     function that acts the same as the *note tp_getattro: 15ec.
     function, but taking a C string instead of a Python string object
     to give the attribute name.

     'Inheritance:'

     群組：*note tp_getattr: 4722.、*note tp_getattro: 15ec.

     This field is inherited by subtypes together with *note
     tp_getattro: 15ec.: a subtype inherits both *note tp_getattr: 4722.
     and *note tp_getattro: 15ec. from its base type when the subtype's
     *note tp_getattr: 4722. and *note tp_getattro: 15ec. are both
     ‘NULL’.

 -- C 成員函數: *note setattrfunc: 48d6. *note PyTypeObject:
          a48.tp_setattr

     An optional pointer to the function for setting and deleting
     attributes.

     This field is deprecated.  When it is defined, it should point to a
     function that acts the same as the *note tp_setattro: 471d.
     function, but taking a C string instead of a Python string object
     to give the attribute name.

     'Inheritance:'

     群組：*note tp_setattr: 4723.、*note tp_setattro: 471d.

     This field is inherited by subtypes together with *note
     tp_setattro: 471d.: a subtype inherits both *note tp_setattr: 4723.
     and *note tp_setattro: 471d. from its base type when the subtype's
     *note tp_setattr: 4723. and *note tp_setattro: 471d. are both
     ‘NULL’.

 -- C 成員函數: *note PyAsyncMethods: 49cf. **note PyTypeObject:
          a48.tp_as_async

     Pointer to an additional structure that contains fields relevant
     only to objects which implement *note awaitable: 193. and *note
     asynchronous iterator: 191. protocols at the C-level.  See *note
     Async Object Structures: 4c5a. for details.

     在 3.5 版被加入: Formerly known as ‘tp_compare’ and ‘tp_reserved’.

     'Inheritance:'

     The *note tp_as_async: e71. field is not inherited, but the
     contained fields are inherited individually.

 -- C 成員函數: *note reprfunc: 48d4. *note PyTypeObject: a48.tp_repr

     An optional pointer to a function that implements the built-in
     function *note repr(): 7a1.

     The signature is the same as for *note PyObject_Repr(): fd2.:

          PyObject *tp_repr(PyObject *self);

     The function must return a string or a Unicode object.  Ideally,
     this function should return a string that, when passed to *note
     eval(): 163, given a suitable environment, returns an object with
     the same value.  If this is not feasible, it should return a string
     starting with ‘'<'’ and ending with ‘'>'’ from which both the type
     and the value of the object can be deduced.

     'Inheritance:'

     This field is inherited by subtypes.

     '預設：'

     When this field is not set, a string of the form ‘<%s object at
     %p>’ is returned, where ‘%s’ is replaced by the type name, and ‘%p’
     by the object's memory address.

 -- C 成員函數: *note PyNumberMethods: 138b. **note PyTypeObject:
          a48.tp_as_number

     Pointer to an additional structure that contains fields relevant
     only to objects which implement the number protocol.  These fields
     are documented in *note Number Object Structures: 4c5b.

     'Inheritance:'

     The *note tp_as_number: 92f. field is not inherited, but the
     contained fields are inherited individually.

 -- C 成員函數: *note PySequenceMethods: 4729. **note PyTypeObject:
          a48.tp_as_sequence

     Pointer to an additional structure that contains fields relevant
     only to objects which implement the sequence protocol.  These
     fields are documented in *note Sequence Object Structures: 4c5c.

     'Inheritance:'

     The *note tp_as_sequence: 4c1c. field is not inherited, but the
     contained fields are inherited individually.

 -- C 成員函數: *note PyMappingMethods: 472a. **note PyTypeObject:
          a48.tp_as_mapping

     Pointer to an additional structure that contains fields relevant
     only to objects which implement the mapping protocol.  These fields
     are documented in *note Mapping Object Structures: 4c5d.

     'Inheritance:'

     The *note tp_as_mapping: 4c1d. field is not inherited, but the
     contained fields are inherited individually.

 -- C 成員函數: *note hashfunc: 48cb. *note PyTypeObject: a48.tp_hash

     An optional pointer to a function that implements the built-in
     function *note hash(): 58f.

     The signature is the same as for *note PyObject_Hash(): 3cb.:

          Py_hash_t tp_hash(PyObject *);

     The value ‘-1’ should not be returned as a normal return value;
     when an error occurs during the computation of the hash value, the
     function should set an exception and return ‘-1’.

     When this field is not set ('and' *note tp_richcompare: 4725. is
     not set), an attempt to take the hash of the object raises *note
     TypeError: 4dd.  This is the same as setting it to *note
     PyObject_HashNotImplemented(): 1334.

     This field can be set explicitly to *note
     PyObject_HashNotImplemented(): 1334. to block inheritance of the
     hash method from a parent type.  This is interpreted as the
     equivalent of ‘__hash__ = None’ at the Python level, causing
     ‘isinstance(o, collections.Hashable)’ to correctly return ‘False’.
     Note that the converse is also true - setting ‘__hash__ = None’ on
     a class at the Python level will result in the ‘tp_hash’ slot being
     set to *note PyObject_HashNotImplemented(): 1334.

     'Inheritance:'

     群組：*note tp_hash: 472b.、*note tp_richcompare: 4725.

     This field is inherited by subtypes together with *note
     tp_richcompare: 4725.: a subtype inherits both of *note
     tp_richcompare: 4725. and *note tp_hash: 472b, when the subtype's
     *note tp_richcompare: 4725. and *note tp_hash: 472b. are both
     ‘NULL’.

     '預設：'

     ‘PyBaseObject_Type’ uses *note PyObject_GenericHash(): 32f.

 -- C 成員函數: *note ternaryfunc: 48db. *note PyTypeObject: a48.tp_call

     An optional pointer to a function that implements calling the
     object.  This should be ‘NULL’ if the object is not callable.  The
     signature is the same as for *note PyObject_Call(): 363.:

          PyObject *tp_call(PyObject *self, PyObject *args, PyObject *kwargs);

     'Inheritance:'

     This field is inherited by subtypes.

 -- C 成員函數: *note reprfunc: 48d4. *note PyTypeObject: a48.tp_str

     An optional pointer to a function that implements the built-in
     operation *note str(): 3f2.  (Note that *note str: 3f2. is a type
     now, and *note str(): 3f2. calls the constructor for that type.
     This constructor calls *note PyObject_Str(): fd3. to do the actual
     work, and *note PyObject_Str(): fd3. will call this handler.)

     The signature is the same as for *note PyObject_Str(): fd3.:

          PyObject *tp_str(PyObject *self);

     The function must return a string or a Unicode object.  It should
     be a "friendly" string representation of the object, as this is the
     representation that will be used, among other things, by the *note
     print(): f18. function.

     'Inheritance:'

     This field is inherited by subtypes.

     '預設：'

     When this field is not set, *note PyObject_Repr(): fd2. is called
     to return a string representation.

 -- C 成員函數: *note getattrofunc: 48c7. *note PyTypeObject:
          a48.tp_getattro

     An optional pointer to the get-attribute function.

     The signature is the same as for *note PyObject_GetAttr(): 2f4.:

          PyObject *tp_getattro(PyObject *self, PyObject *attr);

     It is usually convenient to set this field to *note
     PyObject_GenericGetAttr(): 483a, which implements the normal way of
     looking for object attributes.

     'Inheritance:'

     群組：*note tp_getattr: 4722.、*note tp_getattro: 15ec.

     This field is inherited by subtypes together with *note tp_getattr:
     4722.: a subtype inherits both *note tp_getattr: 4722. and *note
     tp_getattro: 15ec. from its base type when the subtype's *note
     tp_getattr: 4722. and *note tp_getattro: 15ec. are both ‘NULL’.

     '預設：'

     ‘PyBaseObject_Type’ uses *note PyObject_GenericGetAttr(): 483a.

 -- C 成員函數: *note setattrofunc: 48d7. *note PyTypeObject:
          a48.tp_setattro

     An optional pointer to the function for setting and deleting
     attributes.

     The signature is the same as for *note PyObject_SetAttr(): 4842.:

          int tp_setattro(PyObject *self, PyObject *attr, PyObject *value);

     In addition, setting 'value' to ‘NULL’ to delete an attribute must
     be supported.  It is usually convenient to set this field to *note
     PyObject_GenericSetAttr(): 483b, which implements the normal way of
     setting object attributes.

     'Inheritance:'

     群組：*note tp_setattr: 4723.、*note tp_setattro: 471d.

     This field is inherited by subtypes together with *note tp_setattr:
     4723.: a subtype inherits both *note tp_setattr: 4723. and *note
     tp_setattro: 471d. from its base type when the subtype's *note
     tp_setattr: 4723. and *note tp_setattro: 471d. are both ‘NULL’.

     '預設：'

     ‘PyBaseObject_Type’ uses *note PyObject_GenericSetAttr(): 483b.

 -- C 成員函數: *note PyBufferProcs: 49d7. **note PyTypeObject:
          a48.tp_as_buffer

     Pointer to an additional structure that contains fields relevant
     only to objects which implement the buffer interface.  These fields
     are documented in *note Buffer Object Structures: 4993.

     'Inheritance:'

     The *note tp_as_buffer: 92d. field is not inherited, but the
     contained fields are inherited individually.

 -- C 成員函數: unsigned long *note PyTypeObject: a48.tp_flags

     This field is a bit mask of various flags.  Some flags indicate
     variant semantics for certain situations; others are used to
     indicate that certain fields in the type object (or in the
     extension structures referenced via *note tp_as_number: 92f, *note
     tp_as_sequence: 4c1c, *note tp_as_mapping: 4c1d, and *note
     tp_as_buffer: 92d.) that were historically not always present are
     valid; if such a flag bit is clear, the type fields it guards must
     not be accessed and must be considered to have a zero or ‘NULL’
     value instead.

     'Inheritance:'

     Inheritance of this field is complicated.  Most flag bits are
     inherited individually, i.e.  if the base type has a flag bit set,
     the subtype inherits this flag bit.  The flag bits that pertain to
     extension structures are strictly inherited if the extension
     structure is inherited, i.e.  the base type's value of the flag bit
     is copied into the subtype together with a pointer to the extension
     structure.  The *note Py_TPFLAGS_HAVE_GC: 720. flag bit is
     inherited together with the *note tp_traverse: 721. and *note
     tp_clear: 4717. fields, i.e.  if the *note Py_TPFLAGS_HAVE_GC: 720.
     flag bit is clear in the subtype and the *note tp_traverse: 721.
     and *note tp_clear: 4717. fields in the subtype exist and have
     ‘NULL’ values.  ..  XXX are most flag bits 'really' inherited
     individually?

     '預設：'

     ‘PyBaseObject_Type’ 使用 ‘Py_TPFLAGS_DEFAULT |
     Py_TPFLAGS_BASETYPE’。

     'Bit Masks:'

     The following bit masks are currently defined; these can be ORed
     together using the ‘|’ operator to form the value of the *note
     tp_flags: 17c0. field.  The macro *note PyType_HasFeature(): 1855.
     takes a type and a flags value, 'tp' and 'f', and checks whether
     ‘tp->tp_flags & f’ is non-zero.

      -- C 巨集: Py_TPFLAGS_HEAPTYPE

          This bit is set when the type object itself is allocated on
          the heap, for example, types created dynamically using *note
          PyType_FromSpec(): 523.  In this case, the *note ob_type:
          4702. field of its instances is considered a reference to the
          type, and the type object is INCREF'ed when a new instance is
          created, and DECREF'ed when an instance is destroyed (this
          does not apply to instances of subtypes; only the type
          referenced by the instance's ob_type gets INCREF'ed or
          DECREF'ed).  Heap types should also *note support garbage
          collection: 4c5e. as they can form a reference cycle with
          their own module object.

          'Inheritance:'

          ???

      -- C 巨集: Py_TPFLAGS_BASETYPE

          This bit is set when the type can be used as the base type of
          another type.  If this bit is clear, the type cannot be
          subtyped (similar to a "final" class in Java).

          'Inheritance:'

          ???

      -- C 巨集: Py_TPFLAGS_READY

          This bit is set when the type object has been fully
          initialized by *note PyType_Ready(): 722.

          'Inheritance:'

          ???

      -- C 巨集: Py_TPFLAGS_READYING

          This bit is set while *note PyType_Ready(): 722. is in the
          process of initializing the type object.

          'Inheritance:'

          ???

      -- C 巨集: Py_TPFLAGS_HAVE_GC

          This bit is set when the object supports garbage collection.
          If this bit is set, instances must be created using *note
          PyObject_GC_New: a45. and destroyed using *note
          PyObject_GC_Del(): 1473.  More information in section *note
          循環垃圾回收的支援: 4c5e.  This bit also implies that the
          GC-related fields *note tp_traverse: 721. and *note tp_clear:
          4717. are present in the type object.

          'Inheritance:'

          Group: *note Py_TPFLAGS_HAVE_GC: 720, *note tp_traverse: 721,
          *note tp_clear: 4717.

          The *note Py_TPFLAGS_HAVE_GC: 720. flag bit is inherited
          together with the *note tp_traverse: 721. and *note tp_clear:
          4717. fields, i.e.  if the *note Py_TPFLAGS_HAVE_GC: 720. flag
          bit is clear in the subtype and the *note tp_traverse: 721.
          and *note tp_clear: 4717. fields in the subtype exist and have
          ‘NULL’ values.

      -- C 巨集: Py_TPFLAGS_DEFAULT

          This is a bitmask of all the bits that pertain to the
          existence of certain fields in the type object and its
          extension structures.  Currently, it includes the following
          bits: ‘Py_TPFLAGS_HAVE_STACKLESS_EXTENSION’.

          'Inheritance:'

          ???

      -- C 巨集: Py_TPFLAGS_METHOD_DESCRIPTOR

          This bit indicates that objects behave like unbound methods.

          If this flag is set for ‘type(meth)’, then:

             - ‘meth.__get__(obj, cls)(*args, **kwds)’ (with ‘obj’ not
               None) must be equivalent to ‘meth(obj, *args, **kwds)’.

             - ‘meth.__get__(None, cls)(*args, **kwds)’ must be
               equivalent to ‘meth(*args, **kwds)’.

          This flag enables an optimization for typical method calls
          like ‘obj.meth()’: it avoids creating a temporary "bound
          method" object for ‘obj.meth’.

          在 3.8 版被加入.

          'Inheritance:'

          This flag is never inherited by types without the *note
          Py_TPFLAGS_IMMUTABLETYPE: 38d. flag set.  For extension types,
          it is inherited whenever *note tp_descr_get: 4c1e. is
          inherited.

      -- C 巨集: Py_TPFLAGS_MANAGED_DICT

          This bit indicates that instances of the class have a
          ‘__dict__’ attribute, and that the space for the dictionary is
          managed by the VM.

          If this flag is set, *note Py_TPFLAGS_HAVE_GC: 720. should
          also be set.

          The type traverse function must call *note
          PyObject_VisitManagedDict(): 319. and its clear function must
          call *note PyObject_ClearManagedDict(): 31a.

          在 3.12 版被加入.

          'Inheritance:'

          This flag is inherited unless the *note tp_dictoffset: 49d1.
          field is set in a superclass.

      -- C 巨集: Py_TPFLAGS_MANAGED_WEAKREF

          This bit indicates that instances of the class should be
          weakly referenceable.

          在 3.12 版被加入.

          'Inheritance:'

          This flag is inherited unless the *note tp_weaklistoffset:
          92c. field is set in a superclass.

      -- C 巨集: Py_TPFLAGS_ITEMS_AT_END

          Only usable with variable-size types, i.e.  ones with non-zero
          *note tp_itemsize: 1e46.

          Indicates that the variable-sized portion of an instance of
          this type is at the end of the instance's memory area, at an
          offset of ‘Py_TYPE(obj)->tp_basicsize’ (which may be different
          in each subclass).

          When setting this flag, be sure that all superclasses either
          use this memory layout, or are not variable-sized.  Python
          does not check this.

          在 3.12 版被加入.

          'Inheritance:'

          This flag is inherited.

      -- C 巨集: Py_TPFLAGS_LONG_SUBCLASS

      -- C 巨集: Py_TPFLAGS_LIST_SUBCLASS

      -- C 巨集: Py_TPFLAGS_TUPLE_SUBCLASS

      -- C 巨集: Py_TPFLAGS_BYTES_SUBCLASS

      -- C 巨集: Py_TPFLAGS_UNICODE_SUBCLASS

      -- C 巨集: Py_TPFLAGS_DICT_SUBCLASS

      -- C 巨集: Py_TPFLAGS_BASE_EXC_SUBCLASS

      -- C 巨集: Py_TPFLAGS_TYPE_SUBCLASS

          These flags are used by functions such as *note
          PyLong_Check(): 49e1. to quickly determine if a type is a
          subclass of a built-in type; such specific checks are faster
          than a generic check, like *note PyObject_IsInstance(): e48.
          Custom types that inherit from built-ins should have their
          *note tp_flags: 17c0. set appropriately, or the code that
          interacts with such types will behave differently depending on
          what kind of check is used.

      -- C 巨集: Py_TPFLAGS_HAVE_FINALIZE

          This bit is set when the *note tp_finalize: a49. slot is
          present in the type structure.

          在 3.4 版被加入.

          在 3.8 版之後被棄用: This flag isn't necessary anymore, as the
          interpreter assumes the *note tp_finalize: a49. slot is always
          present in the type structure.

      -- C 巨集: Py_TPFLAGS_HAVE_VECTORCALL

          This bit is set when the class implements the *note vectorcall
          protocol: 4f8.  See *note tp_vectorcall_offset: 4973. for
          details.

          'Inheritance:'

          This bit is inherited if *note tp_call: 4ff. is also
          inherited.

          在 3.9 版被加入.

          在 3.12 版的變更: This flag is now removed from a class when
          the class's *note __call__(): 4fe. method is reassigned.

          This flag can now be inherited by mutable classes.

      -- C 巨集: Py_TPFLAGS_IMMUTABLETYPE

          This bit is set for type objects that are immutable: type
          attributes cannot be set nor deleted.

          *note PyType_Ready(): 722. automatically applies this flag to
          *note static types: 723.

          'Inheritance:'

          This flag is not inherited.

          在 3.10 版被加入.

      -- C 巨集: Py_TPFLAGS_DISALLOW_INSTANTIATION

          Disallow creating instances of the type: set *note tp_new:
          525. to NULL and don't create the ‘__new__’ key in the type
          dictionary.

          The flag must be set before creating the type, not after.  For
          example, it must be set before *note PyType_Ready(): 722. is
          called on the type.

          The flag is set automatically on *note static types: 723. if
          *note tp_base: 4710. is NULL or ‘&PyBaseObject_Type’ and *note
          tp_new: 525. is NULL.

          'Inheritance:'

          This flag is not inherited.  However, subclasses will not be
          instantiable unless they provide a non-NULL *note tp_new: 525.
          (which is only possible via the C API).

               備註: To disallow instantiating a class directly but
               allow instantiating its subclasses (e.g.  for an *note
               abstract base class: 114e.), do not use this flag.
               Instead, make *note tp_new: 525. only succeed for
               subclasses.

          在 3.10 版被加入.

      -- C 巨集: Py_TPFLAGS_MAPPING

          This bit indicates that instances of the class may match
          mapping patterns when used as the subject of a *note match:
          7b1. block.  It is automatically set when registering or
          subclassing *note collections.abc.Mapping: 86f, and unset when
          registering *note collections.abc.Sequence: 115c.

               備註: *note Py_TPFLAGS_MAPPING: 17a6. and *note
               Py_TPFLAGS_SEQUENCE: 17a7. are mutually exclusive; it is
               an error to enable both flags simultaneously.

          'Inheritance:'

          This flag is inherited by types that do not already set *note
          Py_TPFLAGS_SEQUENCE: 17a7.

          也參考
          ......

          PEP 634(1) - Structural Pattern Matching: Specification

          在 3.10 版被加入.

      -- C 巨集: Py_TPFLAGS_SEQUENCE

          This bit indicates that instances of the class may match
          sequence patterns when used as the subject of a *note match:
          7b1. block.  It is automatically set when registering or
          subclassing *note collections.abc.Sequence: 115c, and unset
          when registering *note collections.abc.Mapping: 86f.

               備註: *note Py_TPFLAGS_MAPPING: 17a6. and *note
               Py_TPFLAGS_SEQUENCE: 17a7. are mutually exclusive; it is
               an error to enable both flags simultaneously.

          'Inheritance:'

          This flag is inherited by types that do not already set *note
          Py_TPFLAGS_MAPPING: 17a6.

          也參考
          ......

          PEP 634(2) - Structural Pattern Matching: Specification

          在 3.10 版被加入.

      -- C 巨集: Py_TPFLAGS_VALID_VERSION_TAG

          Internal.  Do not set or unset this flag.  To indicate that a
          class has changed call *note PyType_Modified(): 16f7.

               警告: This flag is present in header files, but is not be
               used.  It will be removed in a future version of CPython

 -- C 成員函數: const char **note PyTypeObject: a48.tp_doc

     An optional pointer to a NUL-terminated C string giving the
     docstring for this type object.  This is exposed as the ‘__doc__’
     attribute on the type and instances of the type.

     'Inheritance:'

     This field is 'not' inherited by subtypes.

 -- C 成員函數: *note traverseproc: 48dc. *note PyTypeObject:
          a48.tp_traverse

     An optional pointer to a traversal function for the garbage
     collector.  This is only used if the *note Py_TPFLAGS_HAVE_GC: 720.
     flag bit is set.  The signature is:

          int tp_traverse(PyObject *self, visitproc visit, void *arg);

     More information about Python's garbage collection scheme can be
     found in section *note 循環垃圾回收的支援: 4c5e.

     The *note tp_traverse: 721. pointer is used by the garbage
     collector to detect reference cycles.  A typical implementation of
     a *note tp_traverse: 721. function simply calls *note Py_VISIT():
     470e. on each of the instance's members that are Python objects
     that the instance owns.  For example, this is function
     ‘local_traverse()’ from the ‘_thread’ extension module:

          static int
          local_traverse(localobject *self, visitproc visit, void *arg)
          {
              Py_VISIT(self->args);
              Py_VISIT(self->kw);
              Py_VISIT(self->dict);
              return 0;
          }

     Note that *note Py_VISIT(): 470e. is called only on those members
     that can participate in reference cycles.  Although there is also a
     ‘self->key’ member, it can only be ‘NULL’ or a Python string and
     therefore cannot be part of a reference cycle.

     On the other hand, even if you know a member can never be part of a
     cycle, as a debugging aid you may want to visit it anyway just so
     the *note gc: 56. module's *note get_referents(): 7a9. function
     will include it.

     Heap types (*note Py_TPFLAGS_HEAPTYPE: 854.) must visit their type
     with:

          Py_VISIT(Py_TYPE(self));

     It is only needed since Python 3.9.  To support Python 3.8 and
     older, this line must be conditional:

          #if PY_VERSION_HEX >= 0x03090000
              Py_VISIT(Py_TYPE(self));
          #endif

     If the *note Py_TPFLAGS_MANAGED_DICT: 31b. bit is set in the *note
     tp_flags: 17c0. field, the traverse function must call *note
     PyObject_VisitManagedDict(): 319. like this:

          PyObject_VisitManagedDict((PyObject*)self, visit, arg);

          警告: When implementing *note tp_traverse: 721, only the
          members that the instance 'owns' (by having *note strong
          references: 2ee. to them) must be visited.  For instance, if
          an object supports weak references via the *note tp_weaklist:
          49d6. slot, the pointer supporting the linked list (what
          'tp_weaklist' points to) must 'not' be visited as the instance
          does not directly own the weak references to itself (the
          weakreference list is there to support the weak reference
          machinery, but the instance has no strong reference to the
          elements inside it, as they are allowed to be removed even if
          the instance is still alive).

     Note that *note Py_VISIT(): 470e. requires the 'visit' and 'arg'
     parameters to ‘local_traverse()’ to have these specific names;
     don't name them just anything.

     Instances of *note heap-allocated types: 909. hold a reference to
     their type.  Their traversal function must therefore either visit
     *note Py_TYPE(self): 724, or delegate this responsibility by
     calling ‘tp_traverse’ of another heap-allocated type (such as a
     heap-allocated superclass).  If they do not, the type object may
     not be garbage-collected.

     在 3.9 版的變更: Heap-allocated types are expected to visit
     ‘Py_TYPE(self)’ in ‘tp_traverse’.  In earlier versions of Python,
     due to bug 40217(3), doing this may lead to crashes in subclasses.

     'Inheritance:'

     Group: *note Py_TPFLAGS_HAVE_GC: 720, *note tp_traverse: 721, *note
     tp_clear: 4717.

     This field is inherited by subtypes together with *note tp_clear:
     4717. and the *note Py_TPFLAGS_HAVE_GC: 720. flag bit: the flag
     bit, *note tp_traverse: 721, and *note tp_clear: 4717. are all
     inherited from the base type if they are all zero in the subtype.

 -- C 成員函數: *note inquiry: 48cd. *note PyTypeObject: a48.tp_clear

     An optional pointer to a clear function for the garbage collector.
     This is only used if the *note Py_TPFLAGS_HAVE_GC: 720. flag bit is
     set.  The signature is:

          int tp_clear(PyObject *);

     The *note tp_clear: 4717. member function is used to break
     reference cycles in cyclic garbage detected by the garbage
     collector.  Taken together, all *note tp_clear: 4717. functions in
     the system must combine to break all reference cycles.  This is
     subtle, and if in any doubt supply a *note tp_clear: 4717.
     function.  For example, the tuple type does not implement a *note
     tp_clear: 4717. function, because it's possible to prove that no
     reference cycle can be composed entirely of tuples.  Therefore the
     *note tp_clear: 4717. functions of other types must be sufficient
     to break any cycle containing a tuple.  This isn't immediately
     obvious, and there's rarely a good reason to avoid implementing
     *note tp_clear: 4717.

     Implementations of *note tp_clear: 4717. should drop the instance's
     references to those of its members that may be Python objects, and
     set its pointers to those members to ‘NULL’, as in the following
     example:

          static int
          local_clear(localobject *self)
          {
              Py_CLEAR(self->key);
              Py_CLEAR(self->args);
              Py_CLEAR(self->kw);
              Py_CLEAR(self->dict);
              return 0;
          }

     The *note Py_CLEAR(): 51e. macro should be used, because clearing
     references is delicate: the reference to the contained object must
     not be released (via *note Py_DECREF(): 515.) until after the
     pointer to the contained object is set to ‘NULL’.  This is because
     releasing the reference may cause the contained object to become
     trash, triggering a chain of reclamation activity that may include
     invoking arbitrary Python code (due to finalizers, or weakref
     callbacks, associated with the contained object).  If it's possible
     for such code to reference 'self' again, it's important that the
     pointer to the contained object be ‘NULL’ at that time, so that
     'self' knows the contained object can no longer be used.  The *note
     Py_CLEAR(): 51e. macro performs the operations in a safe order.

     If the *note Py_TPFLAGS_MANAGED_DICT: 31b. bit is set in the *note
     tp_flags: 17c0. field, the traverse function must call *note
     PyObject_ClearManagedDict(): 31a. like this:

          PyObject_ClearManagedDict((PyObject*)self);

     Note that *note tp_clear: 4717. is not 'always' called before an
     instance is deallocated.  For example, when reference counting is
     enough to determine that an object is no longer used, the cyclic
     garbage collector is not involved and *note tp_dealloc: 4704. is
     called directly.

     Because the goal of *note tp_clear: 4717. functions is to break
     reference cycles, it's not necessary to clear contained objects
     like Python strings or Python integers, which can't participate in
     reference cycles.  On the other hand, it may be convenient to clear
     all contained Python objects, and write the type's *note
     tp_dealloc: 4704. function to invoke *note tp_clear: 4717.

     More information about Python's garbage collection scheme can be
     found in section *note 循環垃圾回收的支援: 4c5e.

     'Inheritance:'

     Group: *note Py_TPFLAGS_HAVE_GC: 720, *note tp_traverse: 721, *note
     tp_clear: 4717.

     This field is inherited by subtypes together with *note
     tp_traverse: 721. and the *note Py_TPFLAGS_HAVE_GC: 720. flag bit:
     the flag bit, *note tp_traverse: 721, and *note tp_clear: 4717. are
     all inherited from the base type if they are all zero in the
     subtype.

 -- C 成員函數: *note richcmpfunc: 48d5. *note PyTypeObject:
          a48.tp_richcompare

     An optional pointer to the rich comparison function, whose
     signature is:

          PyObject *tp_richcompare(PyObject *self, PyObject *other, int op);

     The first parameter is guaranteed to be an instance of the type
     that is defined by *note PyTypeObject: a48.

     The function should return the result of the comparison (usually
     ‘Py_True’ or ‘Py_False’).  If the comparison is undefined, it must
     return ‘Py_NotImplemented’, if another error occurred it must
     return ‘NULL’ and set an exception condition.

     The following constants are defined to be used as the third
     argument for *note tp_richcompare: 4725. and for *note
     PyObject_RichCompare(): 4726.:

     常數                     Comparison
                              
     ------------------------------------------
                              
      -- C 巨集: Py_LT        ‘<’
                              
                              
      -- C 巨集: Py_LE        ‘<=’
                              
                              
      -- C 巨集: Py_EQ        ‘==’
                              
                              
      -- C 巨集: Py_NE        ‘!=’
                              
                              
      -- C 巨集: Py_GT        ‘>’
                              
                              
      -- C 巨集: Py_GE        ‘>=’
                              

     The following macro is defined to ease writing rich comparison
     functions:

      -- C 巨集: Py_RETURN_RICHCOMPARE (VAL_A, VAL_B, op)

          Return ‘Py_True’ or ‘Py_False’ from the function, depending on
          the result of a comparison.  VAL_A and VAL_B must be orderable
          by C comparison operators (for example, they may be C ints or
          floats).  The third argument specifies the requested
          operation, as for *note PyObject_RichCompare(): 4726.

          The returned value is a new *note strong reference: 2ee.

          On error, sets an exception and returns ‘NULL’ from the
          function.

          在 3.7 版被加入.

     'Inheritance:'

     群組：*note tp_hash: 472b.、*note tp_richcompare: 4725.

     This field is inherited by subtypes together with *note tp_hash:
     472b.: a subtype inherits *note tp_richcompare: 4725. and *note
     tp_hash: 472b. when the subtype's *note tp_richcompare: 4725. and
     *note tp_hash: 472b. are both ‘NULL’.

     '預設：'

     ‘PyBaseObject_Type’ provides a *note tp_richcompare: 4725.
     implementation, which may be inherited.  However, if only *note
     tp_hash: 472b. is defined, not even the inherited function is used
     and instances of the type will not be able to participate in any
     comparisons.

 -- C 成員函數: *note Py_ssize_t: a03. *note PyTypeObject:
          a48.tp_weaklistoffset

     While this field is still supported, *note
     Py_TPFLAGS_MANAGED_WEAKREF: 500. should be used instead, if at all
     possible.

     If the instances of this type are weakly referenceable, this field
     is greater than zero and contains the offset in the instance
     structure of the weak reference list head (ignoring the GC header,
     if present); this offset is used by *note PyObject_ClearWeakRefs():
     51c. and the ‘PyWeakref_*’ functions.  The instance structure needs
     to include a field of type *note PyObject: 311.* which is
     initialized to ‘NULL’.

     Do not confuse this field with *note tp_weaklist: 49d6.; that is
     the list head for weak references to the type object itself.

     It is an error to set both the *note Py_TPFLAGS_MANAGED_WEAKREF:
     500. bit and *note tp_weaklistoffset: 92c.

     'Inheritance:'

     This field is inherited by subtypes, but see the rules listed
     below.  A subtype may override this offset; this means that the
     subtype uses a different weak reference list head than the base
     type.  Since the list head is always found via *note
     tp_weaklistoffset: 92c, this should not be a problem.

     '預設：'

     If the *note Py_TPFLAGS_MANAGED_WEAKREF: 500. bit is set in the
     *note tp_flags: 17c0. field, then *note tp_weaklistoffset: 92c.
     will be set to a negative value, to indicate that it is unsafe to
     use this field.

 -- C 成員函數: *note getiterfunc: 48c9. *note PyTypeObject: a48.tp_iter

     An optional pointer to a function that returns an *note iterator:
     192. for the object.  Its presence normally signals that the
     instances of this type are *note iterable: 11bf. (although
     sequences may be iterable without this function).

     This function has the same signature as *note PyObject_GetIter():
     483e.:

          PyObject *tp_iter(PyObject *self);

     'Inheritance:'

     This field is inherited by subtypes.

 -- C 成員函數: *note iternextfunc: 48ce. *note PyTypeObject:
          a48.tp_iternext

     An optional pointer to a function that returns the next item in an
     *note iterator: 192.  The signature is:

          PyObject *tp_iternext(PyObject *self);

     When the iterator is exhausted, it must return ‘NULL’; a *note
     StopIteration: ba1. exception may or may not be set.  When another
     error occurs, it must return ‘NULL’ too.  Its presence signals that
     the instances of this type are iterators.

     Iterator types should also define the *note tp_iter: 145c.
     function, and that function should return the iterator instance
     itself (not a new iterator instance).

     This function has the same signature as *note PyIter_Next(): 47ed.

     'Inheritance:'

     This field is inherited by subtypes.

 -- C 成員函數: struct *note PyMethodDef: 1446. **note PyTypeObject:
          a48.tp_methods

     An optional pointer to a static ‘NULL’-terminated array of *note
     PyMethodDef: 1446. structures, declaring regular methods of this
     type.

     For each entry in the array, an entry is added to the type's
     dictionary (see *note tp_dict: 161c. below) containing a method
     descriptor.

     'Inheritance:'

     This field is not inherited by subtypes (methods are inherited
     through a different mechanism).

 -- C 成員函數: struct *note PyMemberDef: 4f5. **note PyTypeObject:
          a48.tp_members

     An optional pointer to a static ‘NULL’-terminated array of *note
     PyMemberDef: 4f5. structures, declaring regular data members
     (fields or slots) of instances of this type.

     For each entry in the array, an entry is added to the type's
     dictionary (see *note tp_dict: 161c. below) containing a member
     descriptor.

     'Inheritance:'

     This field is not inherited by subtypes (members are inherited
     through a different mechanism).

 -- C 成員函數: struct *note PyGetSetDef: b5f. **note PyTypeObject:
          a48.tp_getset

     An optional pointer to a static ‘NULL’-terminated array of *note
     PyGetSetDef: b5f. structures, declaring computed attributes of
     instances of this type.

     For each entry in the array, an entry is added to the type's
     dictionary (see *note tp_dict: 161c. below) containing a getset
     descriptor.

     'Inheritance:'

     This field is not inherited by subtypes (computed attributes are
     inherited through a different mechanism).

 -- C 成員函數: *note PyTypeObject: a48. **note PyTypeObject:
          a48.tp_base

     An optional pointer to a base type from which type properties are
     inherited.  At this level, only single inheritance is supported;
     multiple inheritance require dynamically creating a type object by
     calling the metatype.

          備註: 
          Slot initialization is subject to the rules of initializing
          globals.  C99 requires the initializers to be "address
          constants".  Function designators like *note
          PyType_GenericNew(): 4701, with implicit conversion to a
          pointer, are valid C99 address constants.

          However, the unary '&' operator applied to a non-static
          variable like ‘PyBaseObject_Type’ is not required to produce
          an address constant.  Compilers may support this (gcc does),
          MSVC does not.  Both compilers are strictly standard
          conforming in this particular behavior.

          Consequently, *note tp_base: 4710. should be set in the
          extension module's init function.

     'Inheritance:'

     This field is not inherited by subtypes (obviously).

     '預設：'

     This field defaults to ‘&PyBaseObject_Type’ (which to Python
     programmers is known as the type *note object: a2f.).

 -- C 成員函數: *note PyObject: 311. **note PyTypeObject: a48.tp_dict

     The type's dictionary is stored here by *note PyType_Ready(): 722.

     This field should normally be initialized to ‘NULL’ before
     PyType_Ready is called; it may also be initialized to a dictionary
     containing initial attributes for the type.  Once *note
     PyType_Ready(): 722. has initialized the type, extra attributes for
     the type may be added to this dictionary only if they don't
     correspond to overloaded operations (like *note __add__(): 1e62.).
     Once initialization for the type has finished, this field should be
     treated as read-only.

     Some types may not store their dictionary in this slot.  Use *note
     PyType_GetDict(): 161b. to retrieve the dictionary for an arbitrary
     type.

     在 3.12 版的變更: Internals detail: For static builtin types, this
     is always ‘NULL’.  Instead, the dict for such types is stored on
     ‘PyInterpreterState’.  Use *note PyType_GetDict(): 161b. to get the
     dict for an arbitrary type.

     'Inheritance:'

     This field is not inherited by subtypes (though the attributes
     defined in here are inherited through a different mechanism).

     '預設：'

     If this field is ‘NULL’, *note PyType_Ready(): 722. will assign a
     new dictionary to it.

          警告: It is not safe to use *note PyDict_SetItem(): 46f0. on
          or otherwise modify *note tp_dict: 161c. with the dictionary
          C-API.

 -- C 成員函數: *note descrgetfunc: 48c3. *note PyTypeObject:
          a48.tp_descr_get

     An optional pointer to a "descriptor get" function.

     The function signature is:

          PyObject * tp_descr_get(PyObject *self, PyObject *obj, PyObject *type);

     'Inheritance:'

     This field is inherited by subtypes.

 -- C 成員函數: *note descrsetfunc: 48c4. *note PyTypeObject:
          a48.tp_descr_set

     An optional pointer to a function for setting and deleting a
     descriptor's value.

     The function signature is:

          int tp_descr_set(PyObject *self, PyObject *obj, PyObject *value);

     The 'value' argument is set to ‘NULL’ to delete the value.

     'Inheritance:'

     This field is inherited by subtypes.

 -- C 成員函數: *note Py_ssize_t: a03. *note PyTypeObject:
          a48.tp_dictoffset

     While this field is still supported, *note Py_TPFLAGS_MANAGED_DICT:
     31b. should be used instead, if at all possible.

     If the instances of this type have a dictionary containing instance
     variables, this field is non-zero and contains the offset in the
     instances of the type of the instance variable dictionary; this
     offset is used by *note PyObject_GenericGetAttr(): 483a.

     Do not confuse this field with *note tp_dict: 161c.; that is the
     dictionary for attributes of the type object itself.

     The value specifies the offset of the dictionary from the start of
     the instance structure.

     The *note tp_dictoffset: 49d1. should be regarded as write-only.
     To get the pointer to the dictionary call *note
     PyObject_GenericGetDict(): 183c.  Calling *note
     PyObject_GenericGetDict(): 183c. may need to allocate memory for
     the dictionary, so it is may be more efficient to call *note
     PyObject_GetAttr(): 2f4. when accessing an attribute on the object.

     It is an error to set both the *note Py_TPFLAGS_MANAGED_WEAKREF:
     500. bit and *note tp_dictoffset: 49d1.

     'Inheritance:'

     This field is inherited by subtypes.  A subtype should not override
     this offset; doing so could be unsafe, if C code tries to access
     the dictionary at the previous offset.  To properly support
     inheritance, use *note Py_TPFLAGS_MANAGED_DICT: 31b.

     '預設：'

     This slot has no default.  For *note static types: 723, if the
     field is ‘NULL’ then no *note __dict__: c04. gets created for
     instances.

     If the *note Py_TPFLAGS_MANAGED_DICT: 31b. bit is set in the *note
     tp_flags: 17c0. field, then *note tp_dictoffset: 49d1. will be set
     to ‘-1’, to indicate that it is unsafe to use this field.

 -- C 成員函數: *note initproc: 48cc. *note PyTypeObject: a48.tp_init

     An optional pointer to an instance initialization function.

     This function corresponds to the *note __init__(): 655. method of
     classes.  Like ‘__init__()’, it is possible to create an instance
     without calling ‘__init__()’, and it is possible to reinitialize an
     instance by calling its ‘__init__()’ method again.

     The function signature is:

          int tp_init(PyObject *self, PyObject *args, PyObject *kwds);

     The self argument is the instance to be initialized; the 'args' and
     'kwds' arguments represent positional and keyword arguments of the
     call to *note __init__(): 655.

     The *note tp_init: 527. function, if not ‘NULL’, is called when an
     instance is created normally by calling its type, after the type's
     *note tp_new: 525. function has returned an instance of the type.
     If the *note tp_new: 525. function returns an instance of some
     other type that is not a subtype of the original type, no *note
     tp_init: 527. function is called; if *note tp_new: 525. returns an
     instance of a subtype of the original type, the subtype's *note
     tp_init: 527. is called.

     Returns ‘0’ on success, ‘-1’ and sets an exception on error.

     'Inheritance:'

     This field is inherited by subtypes.

     '預設：'

     For *note static types: 723. this field does not have a default.

 -- C 成員函數: *note allocfunc: 48c1. *note PyTypeObject: a48.tp_alloc

     An optional pointer to an instance allocation function.

     The function signature is:

          PyObject *tp_alloc(PyTypeObject *self, Py_ssize_t nitems);

     'Inheritance:'

     This field is inherited by static subtypes, but not by dynamic
     subtypes (subtypes created by a class statement).

     '預設：'

     For dynamic subtypes, this field is always set to *note
     PyType_GenericAlloc(): a0e, to force a standard heap allocation
     strategy.

     For static subtypes, ‘PyBaseObject_Type’ uses *note
     PyType_GenericAlloc(): a0e.  That is the recommended value for all
     statically defined types.

 -- C 成員函數: *note newfunc: 48d0. *note PyTypeObject: a48.tp_new

     An optional pointer to an instance creation function.

     The function signature is:

          PyObject *tp_new(PyTypeObject *subtype, PyObject *args, PyObject *kwds);

     The 'subtype' argument is the type of the object being created; the
     'args' and 'kwds' arguments represent positional and keyword
     arguments of the call to the type.  Note that 'subtype' doesn't
     have to equal the type whose *note tp_new: 525. function is called;
     it may be a subtype of that type (but not an unrelated type).

     The *note tp_new: 525. function should call
     ‘subtype->tp_alloc(subtype, nitems)’ to allocate space for the
     object, and then do only as much further initialization as is
     absolutely necessary.  Initialization that can safely be ignored or
     repeated should be placed in the *note tp_init: 527. handler.  A
     good rule of thumb is that for immutable types, all initialization
     should take place in *note tp_new: 525, while for mutable types,
     most initialization should be deferred to *note tp_init: 527.

     Set the *note Py_TPFLAGS_DISALLOW_INSTANTIATION: 528. flag to
     disallow creating instances of the type in Python.

     'Inheritance:'

     This field is inherited by subtypes, except it is not inherited by
     *note static types: 723. whose *note tp_base: 4710. is ‘NULL’ or
     ‘&PyBaseObject_Type’.

     '預設：'

     For *note static types: 723. this field has no default.  This means
     if the slot is defined as ‘NULL’, the type cannot be called to
     create new instances; presumably there is some other way to create
     instances, like a factory function.

 -- C 成員函數: *note freefunc: 4ac6. *note PyTypeObject: a48.tp_free

     An optional pointer to an instance deallocation function.  Its
     signature is:

          void tp_free(void *self);

     An initializer that is compatible with this signature is *note
     PyObject_Free(): c0c.

     'Inheritance:'

     This field is inherited by static subtypes, but not by dynamic
     subtypes (subtypes created by a class statement)

     '預設：'

     In dynamic subtypes, this field is set to a deallocator suitable to
     match *note PyType_GenericAlloc(): a0e. and the value of the *note
     Py_TPFLAGS_HAVE_GC: 720. flag bit.

     For static subtypes, ‘PyBaseObject_Type’ uses *note PyObject_Del():
     1440.

 -- C 成員函數: *note inquiry: 48cd. *note PyTypeObject: a48.tp_is_gc

     An optional pointer to a function called by the garbage collector.

     The garbage collector needs to know whether a particular object is
     collectible or not.  Normally, it is sufficient to look at the
     object's type's *note tp_flags: 17c0. field, and check the *note
     Py_TPFLAGS_HAVE_GC: 720. flag bit.  But some types have a mixture
     of statically and dynamically allocated instances, and the
     statically allocated instances are not collectible.  Such types
     should define this function; it should return ‘1’ for a collectible
     instance, and ‘0’ for a non-collectible instance.  The signature
     is:

          int tp_is_gc(PyObject *self);

     (The only example of this are types themselves.  The metatype,
     *note PyType_Type: 4f3, defines this function to distinguish
     between statically and *note dynamically allocated types: 909.)

     'Inheritance:'

     This field is inherited by subtypes.

     '預設：'

     This slot has no default.  If this field is ‘NULL’, *note
     Py_TPFLAGS_HAVE_GC: 720. is used as the functional equivalent.

 -- C 成員函數: *note PyObject: 311. **note PyTypeObject: a48.tp_bases

     Tuple of base types.

     This field should be set to ‘NULL’ and treated as read-only.
     Python will fill it in when the type is *note initialized: 722.

     For dynamically created classes, the ‘Py_tp_bases’ *note slot:
     4875. can be used instead of the 'bases' argument of *note
     PyType_FromSpecWithBases(): 524.  The argument form is preferred.

          警告: Multiple inheritance does not work well for statically
          defined types.  If you set ‘tp_bases’ to a tuple, Python will
          not raise an error, but some slots will only be inherited from
          the first base.

     'Inheritance:'

     This field is not inherited.

 -- C 成員函數: *note PyObject: 311. **note PyTypeObject: a48.tp_mro

     Tuple containing the expanded set of base types, starting with the
     type itself and ending with *note object: a2f, in Method Resolution
     Order.

     This field should be set to ‘NULL’ and treated as read-only.
     Python will fill it in when the type is *note initialized: 722.

     'Inheritance:'

     This field is not inherited; it is calculated fresh by *note
     PyType_Ready(): 722.

 -- C 成員函數: *note PyObject: 311. **note PyTypeObject: a48.tp_cache

     Unused.  Internal use only.

     'Inheritance:'

     This field is not inherited.

 -- C 成員函數: void **note PyTypeObject: a48.tp_subclasses

     A collection of subclasses.  Internal use only.  May be an invalid
     pointer.

     To get a list of subclasses, call the Python method *note
     __subclasses__(): 519.

     在 3.12 版的變更: For some types, this field does not hold a valid
     *note PyObject: 311.*.  The type was changed to void* to indicate
     this.

     'Inheritance:'

     This field is not inherited.

 -- C 成員函數: *note PyObject: 311. **note PyTypeObject:
          a48.tp_weaklist

     Weak reference list head, for weak references to this type object.
     Not inherited.  Internal use only.

     在 3.12 版的變更: Internals detail: For the static builtin types
     this is always ‘NULL’, even if weakrefs are added.  Instead, the
     weakrefs for each are stored on ‘PyInterpreterState’.  Use the
     public C-API or the internal ‘_PyObject_GET_WEAKREFS_LISTPTR()’
     macro to avoid the distinction.

     'Inheritance:'

     This field is not inherited.

 -- C 成員函數: *note destructor: 48c5. *note PyTypeObject: a48.tp_del

     This field is deprecated.  Use *note tp_finalize: a49. instead.

 -- C 成員函數: unsigned int *note PyTypeObject: a48.tp_version_tag

     Used to index into the method cache.  Internal use only.

     'Inheritance:'

     This field is not inherited.

 -- C 成員函數: *note destructor: 48c5. *note PyTypeObject:
          a48.tp_finalize

     An optional pointer to an instance finalization function.  Its
     signature is:

          void tp_finalize(PyObject *self);

     If *note tp_finalize: a49. is set, the interpreter calls it once
     when finalizing an instance.  It is called either from the garbage
     collector (if the instance is part of an isolated reference cycle)
     or just before the object is deallocated.  Either way, it is
     guaranteed to be called before attempting to break reference
     cycles, ensuring that it finds the object in a sane state.

     *note tp_finalize: a49. should not mutate the current exception
     status; therefore, a recommended way to write a non-trivial
     finalizer is:

          static void
          local_finalize(PyObject *self)
          {
              PyObject *error_type, *error_value, *error_traceback;

              /* Save the current exception, if any. */
              PyErr_Fetch(&error_type, &error_value, &error_traceback);

              /* ... */

              /* Restore the saved exception. */
              PyErr_Restore(error_type, error_value, error_traceback);
          }

     Also, note that, in a garbage collected Python, *note tp_dealloc:
     4704. may be called from any Python thread, not just the thread
     which created the object (if the object becomes part of a refcount
     cycle, that cycle might be collected by a garbage collection on any
     thread).  This is not a problem for Python API calls, since the
     thread on which tp_dealloc is called will own the Global
     Interpreter Lock (GIL). However, if the object being destroyed in
     turn destroys objects from some other C or C++ library, care should
     be taken to ensure that destroying those objects on the thread
     which called tp_dealloc will not violate any assumptions of the
     library.

     'Inheritance:'

     This field is inherited by subtypes.

     在 3.4 版被加入.

     在 3.8 版的變更: Before version 3.8 it was necessary to set the
     *note Py_TPFLAGS_HAVE_FINALIZE: 3ba. flags bit in order for this
     field to be used.  This is no longer required.

     也參考
     ......

     "Safe object finalization" ( PEP 442(4))

 -- C 成員函數: *note vectorcallfunc: 4fd. *note PyTypeObject:
          a48.tp_vectorcall

     Vectorcall function to use for calls of this type object.  In other
     words, it is used to implement *note vectorcall: 4f8. for
     ‘type.__call__’.  If ‘tp_vectorcall’ is ‘NULL’, the default call
     implementation using *note __new__(): 526. and *note __init__():
     655. is used.

     'Inheritance:'

     This field is never inherited.

     在 3.9 版被加入: (the field exists since 3.8 but it's only used
     since 3.9)

 -- C 成員函數: unsigned char *note PyTypeObject: a48.tp_watched

     Internal.  Do not use.

     在 3.12 版被加入.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0634/

   (2) https://peps.python.org/pep-0634/

   (3) https://bugs.python.org/issue40217

   (4) https://peps.python.org/pep-0442/


File: python.info,  Node: Static Types,  Next: Heap Types,  Prev: PyTypeObject Slots,  Up: 型別物件<2>

7.12.3.9 Static Types
.....................

Traditionally, types defined in C code are 'static', that is, a static
*note PyTypeObject: a48. structure is defined directly in code and
initialized using *note PyType_Ready(): 722.

This results in types that are limited relative to types defined in
Python:

   * Static types are limited to one base, i.e.  they cannot use
     multiple inheritance.

   * Static type objects (but not necessarily their instances) are
     immutable.  It is not possible to add or modify the type object's
     attributes from Python.

   * Static type objects are shared across *note sub-interpreters: 52d,
     so they should not include any subinterpreter-specific state.

Also, since *note PyTypeObject: a48. is only part of the *note Limited
API: 318. as an opaque struct, any extension modules using static types
must be compiled for a specific Python minor version.


File: python.info,  Node: Heap Types,  Prev: Static Types,  Up: 型別物件<2>

7.12.3.10 Heap Types
....................

An alternative to *note static types: 723. is 'heap-allocated types', or
'heap types' for short, which correspond closely to classes created by
Python's ‘class’ statement.  Heap types have the *note
Py_TPFLAGS_HEAPTYPE: 854. flag set.

This is done by filling a *note PyType_Spec: 1618. structure and calling
*note PyType_FromSpec(): 523, *note PyType_FromSpecWithBases(): 524,
*note PyType_FromModuleAndSpec(): 4f7, or *note PyType_FromMetaclass():
4f6.


File: python.info,  Node: Number Object Structures,  Next: Mapping Object Structures,  Prev: 型別物件<2>,  Up: Object Implementation Support

7.12.4 Number Object Structures
-------------------------------

 -- C 型別: type PyNumberMethods

     This structure holds pointers to the functions which an object uses
     to implement the number protocol.  Each function is used by the
     function of similar name documented in the *note 數字協定: 497e.
     section.

     Here is the structure definition:

          typedef struct {
               binaryfunc nb_add;
               binaryfunc nb_subtract;
               binaryfunc nb_multiply;
               binaryfunc nb_remainder;
               binaryfunc nb_divmod;
               ternaryfunc nb_power;
               unaryfunc nb_negative;
               unaryfunc nb_positive;
               unaryfunc nb_absolute;
               inquiry nb_bool;
               unaryfunc nb_invert;
               binaryfunc nb_lshift;
               binaryfunc nb_rshift;
               binaryfunc nb_and;
               binaryfunc nb_xor;
               binaryfunc nb_or;
               unaryfunc nb_int;
               void *nb_reserved;
               unaryfunc nb_float;

               binaryfunc nb_inplace_add;
               binaryfunc nb_inplace_subtract;
               binaryfunc nb_inplace_multiply;
               binaryfunc nb_inplace_remainder;
               ternaryfunc nb_inplace_power;
               binaryfunc nb_inplace_lshift;
               binaryfunc nb_inplace_rshift;
               binaryfunc nb_inplace_and;
               binaryfunc nb_inplace_xor;
               binaryfunc nb_inplace_or;

               binaryfunc nb_floor_divide;
               binaryfunc nb_true_divide;
               binaryfunc nb_inplace_floor_divide;
               binaryfunc nb_inplace_true_divide;

               unaryfunc nb_index;

               binaryfunc nb_matrix_multiply;
               binaryfunc nb_inplace_matrix_multiply;
          } PyNumberMethods;

          備註: Binary and ternary functions must check the type of all
          their operands, and implement the necessary conversions (at
          least one of the operands is an instance of the defined type).
          If the operation is not defined for the given operands, binary
          and ternary functions must return ‘Py_NotImplemented’, if
          another error occurred they must return ‘NULL’ and set an
          exception.

          備註: The *note nb_reserved: 4c44. field should always be
          ‘NULL’.  It was previously called ‘nb_long’, and was renamed
          in Python 3.0.1.

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_add

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_subtract

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_multiply

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_remainder

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_divmod

 -- C 成員函數: *note ternaryfunc: 48db. *note PyNumberMethods:
          138b.nb_power

 -- C 成員函數: *note unaryfunc: 48dd. *note PyNumberMethods:
          138b.nb_negative

 -- C 成員函數: *note unaryfunc: 48dd. *note PyNumberMethods:
          138b.nb_positive

 -- C 成員函數: *note unaryfunc: 48dd. *note PyNumberMethods:
          138b.nb_absolute

 -- C 成員函數: *note inquiry: 48cd. *note PyNumberMethods: 138b.nb_bool

 -- C 成員函數: *note unaryfunc: 48dd. *note PyNumberMethods:
          138b.nb_invert

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_lshift

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_rshift

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_and

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_xor

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_or

 -- C 成員函數: *note unaryfunc: 48dd. *note PyNumberMethods:
          138b.nb_int

 -- C 成員函數: void **note PyNumberMethods: 138b.nb_reserved

 -- C 成員函數: *note unaryfunc: 48dd. *note PyNumberMethods:
          138b.nb_float

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_inplace_add

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_inplace_subtract

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_inplace_multiply

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_inplace_remainder

 -- C 成員函數: *note ternaryfunc: 48db. *note PyNumberMethods:
          138b.nb_inplace_power

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_inplace_lshift

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_inplace_rshift

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_inplace_and

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_inplace_xor

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_inplace_or

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_floor_divide

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_true_divide

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_inplace_floor_divide

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_inplace_true_divide

 -- C 成員函數: *note unaryfunc: 48dd. *note PyNumberMethods:
          138b.nb_index

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_matrix_multiply

 -- C 成員函數: *note binaryfunc: 48c2. *note PyNumberMethods:
          138b.nb_inplace_matrix_multiply


File: python.info,  Node: Mapping Object Structures,  Next: Sequence Object Structures,  Prev: Number Object Structures,  Up: Object Implementation Support

7.12.5 Mapping Object Structures
--------------------------------

 -- C 型別: type PyMappingMethods

     This structure holds pointers to the functions which an object uses
     to implement the mapping protocol.  It has three members:

 -- C 成員函數: *note lenfunc: 48cf. *note PyMappingMethods:
          472a.mp_length

     This function is used by *note PyMapping_Size(): 195c. and *note
     PyObject_Size(): 4843, and has the same signature.  This slot may
     be set to ‘NULL’ if the object has no defined length.

 -- C 成員函數: *note binaryfunc: 48c2. *note PyMappingMethods:
          472a.mp_subscript

     This function is used by *note PyObject_GetItem(): 2f9. and *note
     PySequence_GetSlice(): 484e, and has the same signature as
     ‘PyObject_GetItem()’.  This slot must be filled for the *note
     PyMapping_Check(): 4801. function to return ‘1’, it can be ‘NULL’
     otherwise.

 -- C 成員函數: *note objobjargproc: 48d1. *note PyMappingMethods:
          472a.mp_ass_subscript

     This function is used by *note PyObject_SetItem(): 4764, *note
     PyObject_DelItem(): 4837, *note PySequence_SetSlice(): 4855. and
     *note PySequence_DelSlice(): 484c.  It has the same signature as
     ‘PyObject_SetItem()’, but 'v' can also be set to ‘NULL’ to delete
     an item.  If this slot is ‘NULL’, the object does not support item
     assignment and deletion.


File: python.info,  Node: Sequence Object Structures,  Next: Buffer Object Structures,  Prev: Mapping Object Structures,  Up: Object Implementation Support

7.12.6 Sequence Object Structures
---------------------------------

 -- C 型別: type PySequenceMethods

     This structure holds pointers to the functions which an object uses
     to implement the sequence protocol.

 -- C 成員函數: *note lenfunc: 48cf. *note PySequenceMethods:
          4729.sq_length

     This function is used by *note PySequence_Size(): 1958. and *note
     PyObject_Size(): 4843, and has the same signature.  It is also used
     for handling negative indices via the *note sq_item: 182f. and the
     *note sq_ass_item: 4c50. slots.

 -- C 成員函數: *note binaryfunc: 48c2. *note PySequenceMethods:
          4729.sq_concat

     This function is used by *note PySequence_Concat(): 4849. and has
     the same signature.  It is also used by the ‘+’ operator, after
     trying the numeric addition via the *note nb_add: 49c8. slot.

 -- C 成員函數: *note ssizeargfunc: 48d9. *note PySequenceMethods:
          4729.sq_repeat

     This function is used by *note PySequence_Repeat(): 4854. and has
     the same signature.  It is also used by the ‘*’ operator, after
     trying numeric multiplication via the *note nb_multiply: 4c2d.
     slot.

 -- C 成員函數: *note ssizeargfunc: 48d9. *note PySequenceMethods:
          4729.sq_item

     This function is used by *note PySequence_GetItem(): 1959. and has
     the same signature.  It is also used by *note PyObject_GetItem():
     2f9, after trying the subscription via the *note mp_subscript:
     1830. slot.  This slot must be filled for the *note
     PySequence_Check(): 4848. function to return ‘1’, it can be ‘NULL’
     otherwise.

     Negative indexes are handled as follows: if the *note sq_length:
     49d0. slot is filled, it is called and the sequence length is used
     to compute a positive index which is passed to *note sq_item: 182f.
     If ‘sq_length’ is ‘NULL’, the index is passed as is to the
     function.

 -- C 成員函數: *note ssizeobjargproc: 48da. *note PySequenceMethods:
          4729.sq_ass_item

     This function is used by *note PySequence_SetItem(): 195a. and has
     the same signature.  It is also used by *note PyObject_SetItem():
     4764. and *note PyObject_DelItem(): 4837, after trying the item
     assignment and deletion via the *note mp_ass_subscript: 4c4d. slot.
     This slot may be left to ‘NULL’ if the object does not support item
     assignment and deletion.

 -- C 成員函數: *note objobjproc: 48d2. *note PySequenceMethods:
          4729.sq_contains

     This function may be used by *note PySequence_Contains(): 484a. and
     has the same signature.  This slot may be left to ‘NULL’, in this
     case ‘PySequence_Contains()’ simply traverses the sequence until it
     finds a match.

 -- C 成員函數: *note binaryfunc: 48c2. *note PySequenceMethods:
          4729.sq_inplace_concat

     This function is used by *note PySequence_InPlaceConcat(): 484f.
     and has the same signature.  It should modify its first operand,
     and return it.  This slot may be left to ‘NULL’, in this case
     ‘PySequence_InPlaceConcat()’ will fall back to *note
     PySequence_Concat(): 4849.  It is also used by the augmented
     assignment ‘+=’, after trying numeric in-place addition via the
     *note nb_inplace_add: 4c2a. slot.

 -- C 成員函數: *note ssizeargfunc: 48d9. *note PySequenceMethods:
          4729.sq_inplace_repeat

     This function is used by *note PySequence_InPlaceRepeat(): 4850.
     and has the same signature.  It should modify its first operand,
     and return it.  This slot may be left to ‘NULL’, in this case
     ‘PySequence_InPlaceRepeat()’ will fall back to *note
     PySequence_Repeat(): 4854.  It is also used by the augmented
     assignment ‘*=’, after trying numeric in-place multiplication via
     the *note nb_inplace_multiply: 4c2e. slot.


File: python.info,  Node: Buffer Object Structures,  Next: Async Object Structures,  Prev: Sequence Object Structures,  Up: Object Implementation Support

7.12.7 Buffer Object Structures
-------------------------------

 -- C 型別: type PyBufferProcs

     This structure holds pointers to the functions required by the
     *note Buffer protocol: 367.  The protocol defines how an exporter
     object can expose its internal data to consumer objects.

 -- C 成員函數: *note getbufferproc: 48c8. *note PyBufferProcs:
          49d7.bf_getbuffer

     The signature of this function is:

          int (PyObject *exporter, Py_buffer *view, int flags);

     Handle a request to 'exporter' to fill in 'view' as specified by
     'flags'.  Except for point (3), an implementation of this function
     MUST take these steps:

       1. Check if the request can be met.  If not, raise *note
          BufferError: 1729, set view->obj to ‘NULL’ and return ‘-1’.

       2. Fill in the requested fields.

       3. Increment an internal counter for the number of exports.

       4. Set view->obj to 'exporter' and increment view->obj.

       5. 回傳 ‘0’。

     If 'exporter' is part of a chain or tree of buffer providers, two
     main schemes can be used:

        * Re-export: Each member of the tree acts as the exporting
          object and sets view->obj to a new reference to itself.

        * Redirect: The buffer request is redirected to the root object
          of the tree.  Here, view->obj will be a new reference to the
          root object.

     The individual fields of 'view' are described in section *note
     Buffer structure: 4994, the rules how an exporter must react to
     specific requests are in section *note Buffer request types: 42b9.

     All memory pointed to in the *note Py_buffer: 6fc. structure
     belongs to the exporter and must remain valid until there are no
     consumers left.  *note format: 499e, *note shape: 49a0, *note
     strides: 4998, *note suboffsets: 49a2. and *note internal: 49a5.
     are read-only for the consumer.

     *note PyBuffer_FillInfo(): 704. provides an easy way of exposing a
     simple bytes buffer while dealing correctly with all request types.

     *note PyObject_GetBuffer(): 369. is the interface for the consumer
     that wraps this function.

 -- C 成員函數: *note releasebufferproc: 48d3. *note PyBufferProcs:
          49d7.bf_releasebuffer

     The signature of this function is:

          void (PyObject *exporter, Py_buffer *view);

     Handle a request to release the resources of the buffer.  If no
     resources need to be released, *note
     PyBufferProcs.bf_releasebuffer: 707. may be ‘NULL’.  Otherwise, a
     standard implementation of this function will take these optional
     steps:

       1. Decrement an internal counter for the number of exports.

       2. If the counter is ‘0’, free all memory associated with 'view'.

     The exporter MUST use the *note internal: 49a5. field to keep track
     of buffer-specific resources.  This field is guaranteed to remain
     constant, while a consumer MAY pass a copy of the original buffer
     as the 'view' argument.

     This function MUST NOT decrement view->obj, since that is done
     automatically in *note PyBuffer_Release(): 36a. (this scheme is
     useful for breaking reference cycles).

     *note PyBuffer_Release(): 36a. is the interface for the consumer
     that wraps this function.


File: python.info,  Node: Async Object Structures,  Next: Slot Type typedefs,  Prev: Buffer Object Structures,  Up: Object Implementation Support

7.12.8 Async Object Structures
------------------------------

在 3.5 版被加入.

 -- C 型別: type PyAsyncMethods

     This structure holds pointers to the functions required to
     implement *note awaitable: 193. and *note asynchronous iterator:
     191. objects.

     Here is the structure definition:

          typedef struct {
              unaryfunc am_await;
              unaryfunc am_aiter;
              unaryfunc am_anext;
              sendfunc am_send;
          } PyAsyncMethods;

 -- C 成員函數: *note unaryfunc: 48dd. *note PyAsyncMethods:
          49cf.am_await

     The signature of this function is:

          PyObject *am_await(PyObject *self);

     The returned object must be an *note iterator: 192, i.e.  *note
     PyIter_Check(): 17f7. must return ‘1’ for it.

     This slot may be set to ‘NULL’ if an object is not an *note
     awaitable: 193.

 -- C 成員函數: *note unaryfunc: 48dd. *note PyAsyncMethods:
          49cf.am_aiter

     The signature of this function is:

          PyObject *am_aiter(PyObject *self);

     Must return an *note asynchronous iterator: 191. object.  See *note
     __anext__(): 1dfa. for details.

     This slot may be set to ‘NULL’ if an object does not implement
     asynchronous iteration protocol.

 -- C 成員函數: *note unaryfunc: 48dd. *note PyAsyncMethods:
          49cf.am_anext

     The signature of this function is:

          PyObject *am_anext(PyObject *self);

     Must return an *note awaitable: 193. object.  See *note
     __anext__(): 1dfa. for details.  This slot may be set to ‘NULL’.

 -- C 成員函數: *note sendfunc: 4c29. *note PyAsyncMethods: 49cf.am_send

     The signature of this function is:

          PySendResult am_send(PyObject *self, PyObject *arg, PyObject **result);

     See *note PyIter_Send(): 83c. for details.  This slot may be set to
     ‘NULL’.

     在 3.10 版被加入.


File: python.info,  Node: Slot Type typedefs,  Next: 範例<53>,  Prev: Async Object Structures,  Up: Object Implementation Support

7.12.9 Slot Type typedefs
-------------------------

 -- C 型別: typedef *note PyObject: 311. *(*allocfunc)(*note
          PyTypeObject: a48. *cls, *note Py_ssize_t: a03. nitems)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  The purpose of this function
     is to separate memory allocation from memory initialization.  It
     should return a pointer to a block of memory of adequate length for
     the instance, suitably aligned, and initialized to zeros, but with
     *note ob_refcnt: 843. set to ‘1’ and *note ob_type: 4702. set to
     the type argument.  If the type's *note tp_itemsize: 1e46. is
     non-zero, the object's *note ob_size: 48af. field should be
     initialized to 'nitems' and the length of the allocated memory
     block should be ‘tp_basicsize + nitems*tp_itemsize’, rounded up to
     a multiple of ‘sizeof(void*)’; otherwise, 'nitems' is not used and
     the length of the block should be *note tp_basicsize: 92b.

     This function should not do any other instance initialization, not
     even to allocate additional memory; that should be done by *note
     tp_new: 525.

 -- C 型別: typedef void (*destructor)(*note PyObject: 311.*)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

 -- C 型別: typedef void (*freefunc)(void*)

     請見 *note tp_free: 4705.。

 -- C 型別: typedef *note PyObject: 311. *(*newfunc)(*note PyObject:
          311.*, *note PyObject: 311.*, *note PyObject: 311.*)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  請見 *note tp_new: 525.。

 -- C 型別: typedef int (*initproc)(*note PyObject: 311.*, *note
          PyObject: 311.*, *note PyObject: 311.*)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  請見 *note tp_init: 527.。

 -- C 型別: typedef *note PyObject: 311. *(*reprfunc)(*note PyObject:
          311.*)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  請見 *note tp_repr: 4719.。

 -- C 型別: typedef *note PyObject: 311. *(*getattrfunc)(*note PyObject:
          311. *self, char *attr)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the value of the named
     attribute for the object.

 -- C 型別: typedef int (*setattrfunc)(*note PyObject: 311. *self, char
          *attr, *note PyObject: 311. *value)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Set the value of the named
     attribute for the object.  The value argument is set to ‘NULL’ to
     delete the attribute.

 -- C 型別: typedef *note PyObject: 311. *(*getattrofunc)(*note
          PyObject: 311. *self, *note PyObject: 311. *attr)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Return the value of the named
     attribute for the object.

     請見 *note tp_getattro: 15ec.。

 -- C 型別: typedef int (*setattrofunc)(*note PyObject: 311. *self,
          *note PyObject: 311. *attr, *note PyObject: 311. *value)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Set the value of the named
     attribute for the object.  The value argument is set to ‘NULL’ to
     delete the attribute.

     請見 *note tp_setattro: 471d.。

 -- C 型別: typedef *note PyObject: 311. *(*descrgetfunc)(*note
          PyObject: 311.*, *note PyObject: 311.*, *note PyObject: 311.*)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  請見 *note tp_descr_get:
     4c1e.。

 -- C 型別: typedef int (*descrsetfunc)(*note PyObject: 311.*, *note
          PyObject: 311.*, *note PyObject: 311.*)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  請見 *note tp_descr_set:
     17f9.。

 -- C 型別: typedef *note Py_hash_t: 11fc. (*hashfunc)(*note PyObject:
          311.*)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  請見 *note tp_hash: 472b.。

 -- C 型別: typedef *note PyObject: 311. *(*richcmpfunc)(*note PyObject:
          311.*, *note PyObject: 311.*, int)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  請見 *note tp_richcompare:
     4725.。

 -- C 型別: typedef *note PyObject: 311. *(*getiterfunc)(*note PyObject:
          311.*)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  請見 *note tp_iter: 145c.。

 -- C 型別: typedef *note PyObject: 311. *(*iternextfunc)(*note
          PyObject: 311.*)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  請見 *note tp_iternext: 145d.。

 -- C 型別: typedef *note Py_ssize_t: a03. (*lenfunc)(*note PyObject:
          311.*)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

 -- C 型別: typedef int (*getbufferproc)(*note PyObject: 311.*, *note
          Py_buffer: 6fc.*, int)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.12 版本開始.'

 -- C 型別: typedef void (*releasebufferproc)(*note PyObject: 311.*,
          *note Py_buffer: 6fc.*)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.12 版本開始.'

 -- C 型別: typedef *note PyObject: 311. *(*unaryfunc)(*note PyObject:
          311.*)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

 -- C 型別: typedef *note PyObject: 311. *(*binaryfunc)(*note PyObject:
          311.*, *note PyObject: 311.*)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

 -- C 型別: typedef *note PySendResult: 4990. (*sendfunc)(*note
          PyObject: 311.*, *note PyObject: 311.*, *note PyObject:
          311.**)

     請見 *note am_send: 4c28.。

 -- C 型別: typedef *note PyObject: 311. *(*ternaryfunc)(*note PyObject:
          311.*, *note PyObject: 311.*, *note PyObject: 311.*)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

 -- C 型別: typedef *note PyObject: 311. *(*ssizeargfunc)(*note
          PyObject: 311.*, *note Py_ssize_t: a03.)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

 -- C 型別: typedef int (*ssizeobjargproc)(*note PyObject: 311.*, *note
          Py_ssize_t: a03, *note PyObject: 311.*)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

 -- C 型別: typedef int (*objobjproc)(*note PyObject: 311.*, *note
          PyObject: 311.*)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'

 -- C 型別: typedef int (*objobjargproc)(*note PyObject: 311.*, *note
          PyObject: 311.*, *note PyObject: 311.*)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'


File: python.info,  Node: 範例<53>,  Next: 循環垃圾回收的支援,  Prev: Slot Type typedefs,  Up: Object Implementation Support

7.12.10 範例
------------

The following are simple examples of Python type definitions.  They
include common usage you may encounter.  Some demonstrate tricky corner
cases.  For more examples, practical info, and a tutorial, see *note
Defining Extension Types; Tutorial: 46fb. and *note Defining Extension
Types; Assorted Topics: 4714.

A basic *note static type: 723.:

     typedef struct {
         PyObject_HEAD
         const char *data;
     } MyObject;

     static PyTypeObject MyObject_Type = {
         PyVarObject_HEAD_INIT(NULL, 0)
         .tp_name = "mymod.MyObject",
         .tp_basicsize = sizeof(MyObject),
         .tp_doc = PyDoc_STR("My objects"),
         .tp_new = myobj_new,
         .tp_dealloc = (destructor)myobj_dealloc,
         .tp_repr = (reprfunc)myobj_repr,
     };

You may also find older code (especially in the CPython code base) with
a more verbose initializer:

     static PyTypeObject MyObject_Type = {
         PyVarObject_HEAD_INIT(NULL, 0)
         "mymod.MyObject",               /* tp_name */
         sizeof(MyObject),               /* tp_basicsize */
         0,                              /* tp_itemsize */
         (destructor)myobj_dealloc,      /* tp_dealloc */
         0,                              /* tp_vectorcall_offset */
         0,                              /* tp_getattr */
         0,                              /* tp_setattr */
         0,                              /* tp_as_async */
         (reprfunc)myobj_repr,           /* tp_repr */
         0,                              /* tp_as_number */
         0,                              /* tp_as_sequence */
         0,                              /* tp_as_mapping */
         0,                              /* tp_hash */
         0,                              /* tp_call */
         0,                              /* tp_str */
         0,                              /* tp_getattro */
         0,                              /* tp_setattro */
         0,                              /* tp_as_buffer */
         0,                              /* tp_flags */
         PyDoc_STR("My objects"),        /* tp_doc */
         0,                              /* tp_traverse */
         0,                              /* tp_clear */
         0,                              /* tp_richcompare */
         0,                              /* tp_weaklistoffset */
         0,                              /* tp_iter */
         0,                              /* tp_iternext */
         0,                              /* tp_methods */
         0,                              /* tp_members */
         0,                              /* tp_getset */
         0,                              /* tp_base */
         0,                              /* tp_dict */
         0,                              /* tp_descr_get */
         0,                              /* tp_descr_set */
         0,                              /* tp_dictoffset */
         0,                              /* tp_init */
         0,                              /* tp_alloc */
         myobj_new,                      /* tp_new */
     };

A type that supports weakrefs, instance dicts, and hashing:

     typedef struct {
         PyObject_HEAD
         const char *data;
     } MyObject;

     static PyTypeObject MyObject_Type = {
         PyVarObject_HEAD_INIT(NULL, 0)
         .tp_name = "mymod.MyObject",
         .tp_basicsize = sizeof(MyObject),
         .tp_doc = PyDoc_STR("My objects"),
         .tp_flags = Py_TPFLAGS_DEFAULT | Py_TPFLAGS_BASETYPE |
              Py_TPFLAGS_HAVE_GC | Py_TPFLAGS_MANAGED_DICT |
              Py_TPFLAGS_MANAGED_WEAKREF,
         .tp_new = myobj_new,
         .tp_traverse = (traverseproc)myobj_traverse,
         .tp_clear = (inquiry)myobj_clear,
         .tp_alloc = PyType_GenericNew,
         .tp_dealloc = (destructor)myobj_dealloc,
         .tp_repr = (reprfunc)myobj_repr,
         .tp_hash = (hashfunc)myobj_hash,
         .tp_richcompare = PyBaseObject_Type.tp_richcompare,
     };

A str subclass that cannot be subclassed and cannot be called to create
instances (e.g.  uses a separate factory func) using *note
Py_TPFLAGS_DISALLOW_INSTANTIATION: 528. flag:

     typedef struct {
         PyUnicodeObject raw;
         char *extra;
     } MyStr;

     static PyTypeObject MyStr_Type = {
         PyVarObject_HEAD_INIT(NULL, 0)
         .tp_name = "mymod.MyStr",
         .tp_basicsize = sizeof(MyStr),
         .tp_base = NULL,  // set to &PyUnicode_Type in module init
         .tp_doc = PyDoc_STR("my custom str"),
         .tp_flags = Py_TPFLAGS_DEFAULT | Py_TPFLAGS_DISALLOW_INSTANTIATION,
         .tp_repr = (reprfunc)myobj_repr,
     };

The simplest *note static type: 723. with fixed-length instances:

     typedef struct {
         PyObject_HEAD
     } MyObject;

     static PyTypeObject MyObject_Type = {
         PyVarObject_HEAD_INIT(NULL, 0)
         .tp_name = "mymod.MyObject",
     };

The simplest *note static type: 723. with variable-length instances:

     typedef struct {
         PyObject_VAR_HEAD
         const char *data[1];
     } MyObject;

     static PyTypeObject MyObject_Type = {
         PyVarObject_HEAD_INIT(NULL, 0)
         .tp_name = "mymod.MyObject",
         .tp_basicsize = sizeof(MyObject) - sizeof(char *),
         .tp_itemsize = sizeof(char *),
     };


File: python.info,  Node: 循環垃圾回收的支援,  Prev: 範例<53>,  Up: Object Implementation Support

7.12.11 循環垃圾回收的支援
--------------------------

Python's support for detecting and collecting garbage which involves
circular references requires support from object types which are
"containers" for other objects which may also be containers.  Types
which do not store references to other objects, or which only store
references to atomic types (such as numbers or strings), do not need to
provide any explicit support for garbage collection.

To create a container type, the *note tp_flags: 17c0. field of the type
object must include the *note Py_TPFLAGS_HAVE_GC: 720. and provide an
implementation of the *note tp_traverse: 721. handler.  If instances of
the type are mutable, a *note tp_clear: 4717. implementation must also
be provided.

*note Py_TPFLAGS_HAVE_GC: 720.

     Objects with a type with this flag set must conform with the rules
     documented here.  For convenience these objects will be referred to
     as container objects.

Constructors for container types must conform to two rules:

  1. The memory for the object must be allocated using *note
     PyObject_GC_New: a45. or *note PyObject_GC_NewVar: a46.

  2. Once all the fields which may contain references to other
     containers are initialized, it must call *note PyObject_GC_Track():
     1474.

Similarly, the deallocator for the object must conform to a similar pair
of rules:

  1. Before fields which refer to other containers are invalidated,
     *note PyObject_GC_UnTrack(): 1475. must be called.

  2. The object's memory must be deallocated using *note
     PyObject_GC_Del(): 1473.

          警告: If a type adds the Py_TPFLAGS_HAVE_GC, then it 'must'
          implement at least a *note tp_traverse: 721. handler or
          explicitly use one from its subclass or subclasses.

          When calling *note PyType_Ready(): 722. or some of the APIs
          that indirectly call it like *note PyType_FromSpecWithBases():
          524. or *note PyType_FromSpec(): 523. the interpreter will
          automatically populate the *note tp_flags: 17c0, *note
          tp_traverse: 721. and *note tp_clear: 4717. fields if the type
          inherits from a class that implements the garbage collector
          protocol and the child class does 'not' include the *note
          Py_TPFLAGS_HAVE_GC: 720. flag.

 -- C 巨集: PyObject_GC_New (TYPE, typeobj)

     Analogous to *note PyObject_New: 929. but for container objects
     with the *note Py_TPFLAGS_HAVE_GC: 720. flag set.

 -- C 巨集: PyObject_GC_NewVar (TYPE, typeobj, size)

     Analogous to *note PyObject_NewVar: 92a. but for container objects
     with the *note Py_TPFLAGS_HAVE_GC: 720. flag set.

 -- C 函式: *note PyObject: 311. *PyUnstable_Object_GC_NewWithExtraData
          (PyTypeObject *type, size_t extra_size)

          這是 不穩定 API，它可能在小版本發布中沒有任何警告地被變更。 '這是 *note 不穩定 API: 4ed.，它可能在小版本發布中沒有任何警告地被變更。': 
     Analogous to *note PyObject_GC_New: a45. but allocates 'extra_size'
     bytes at the end of the object (at offset *note tp_basicsize:
     92b.).  The allocated memory is initialized to zeros, except for
     the *note Python object header: 311.

     The extra data will be deallocated with the object, but otherwise
     it is not managed by Python.

          警告: The function is marked as unstable because the final
          mechanism for reserving extra data after an instance is not
          yet decided.  For allocating a variable number of fields,
          prefer using *note PyVarObject: 3f79. and *note tp_itemsize:
          1e46. instead.

     在 3.12 版被加入.

 -- C 巨集: PyObject_GC_Resize (TYPE, op, newsize)

     Resize an object allocated by *note PyObject_NewVar: 92a.  Returns
     the resized object of type ‘TYPE*’ (refers to any C type) or ‘NULL’
     on failure.

     'op' must be of type *note PyVarObject: 3f79.* and must not be
     tracked by the collector yet.  'newsize' must be of type *note
     Py_ssize_t: a03.

 -- C 函式: void PyObject_GC_Track (PyObject *op)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Adds the object 'op' to the
     set of container objects tracked by the collector.  The collector
     can run at unexpected times so objects must be valid while being
     tracked.  This should be called once all the fields followed by the
     *note tp_traverse: 721. handler become valid, usually near the end
     of the constructor.

 -- C 函式: int PyObject_IS_GC (PyObject *obj)

     Returns non-zero if the object implements the garbage collector
     protocol, otherwise returns 0.

     The object cannot be tracked by the garbage collector if this
     function returns 0.

 -- C 函式: int PyObject_GC_IsTracked (PyObject *op)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.9 版本開始.'  Returns 1 if
     the object type of 'op' implements the GC protocol and 'op' is
     being currently tracked by the garbage collector and 0 otherwise.

     This is analogous to the Python function *note gc.is_tracked():
     12a2.

     在 3.9 版被加入.

 -- C 函式: int PyObject_GC_IsFinalized (PyObject *op)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.9 版本開始.'  Returns 1 if
     the object type of 'op' implements the GC protocol and 'op' has
     been already finalized by the garbage collector and 0 otherwise.

     This is analogous to the Python function *note gc.is_finalized():
     8a2.

     在 3.9 版被加入.

 -- C 函式: void PyObject_GC_Del (void *op)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Releases memory allocated to
     an object using *note PyObject_GC_New: a45. or *note
     PyObject_GC_NewVar: a46.

 -- C 函式: void PyObject_GC_UnTrack (void *op)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Remove the object 'op' from
     the set of container objects tracked by the collector.  Note that
     *note PyObject_GC_Track(): 1474. can be called again on this object
     to add it back to the set of tracked objects.  The deallocator
     (*note tp_dealloc: 4704. handler) should call this for the object
     before any of the fields used by the *note tp_traverse: 721.
     handler become invalid.

在 3.8 版的變更: The ‘_PyObject_GC_TRACK()’ and ‘_PyObject_GC_UNTRACK()’
macros have been removed from the public C API.

The *note tp_traverse: 721. handler accepts a function parameter of this
type:

 -- C 型別: typedef int (*visitproc)(*note PyObject: 311. *object, void
          *arg)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Type of the visitor function
     passed to the *note tp_traverse: 721. handler.  The function should
     be called with an object to traverse as 'object' and the third
     parameter to the *note tp_traverse: 721. handler as 'arg'.  The
     Python core uses several visitor functions to implement cyclic
     garbage detection; it's not expected that users will need to write
     their own visitor functions.

The *note tp_traverse: 721. handler must have the following type:

 -- C 型別: typedef int (*traverseproc)(*note PyObject: 311. *self,
          *note visitproc: 48de. visit, void *arg)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Traversal function for a
     container object.  Implementations must call the 'visit' function
     for each object directly contained by 'self', with the parameters
     to 'visit' being the contained object and the 'arg' value passed to
     the handler.  The 'visit' function must not be called with a ‘NULL’
     object argument.  If 'visit' returns a non-zero value that value
     should be returned immediately.

To simplify writing *note tp_traverse: 721. handlers, a *note
Py_VISIT(): 470e. macro is provided.  In order to use this macro, the
*note tp_traverse: 721. implementation must name its arguments exactly
'visit' and 'arg':

 -- C 函式: void Py_VISIT (PyObject *o)

     If 'o' is not ‘NULL’, call the 'visit' callback, with arguments 'o'
     and 'arg'.  If 'visit' returns a non-zero value, then return it.
     Using this macro, *note tp_traverse: 721. handlers look like:

          static int
          my_traverse(Noddy *self, visitproc visit, void *arg)
          {
              Py_VISIT(self->foo);
              Py_VISIT(self->bar);
              return 0;
          }

The *note tp_clear: 4717. handler must be of the *note inquiry: 48cd.
type, or ‘NULL’ if the object is immutable.

 -- C 型別: typedef int (*inquiry)(*note PyObject: 311. *self)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Drop references that may have
     created reference cycles.  Immutable objects do not have to define
     this method since they can never directly create reference cycles.
     Note that the object must still be valid after calling this method
     (don't just call *note Py_DECREF(): 515. on a reference).  The
     collector will call this method if it detects that this object is
     involved in a reference cycle.

* Menu:

* Controlling the Garbage Collector State::
* Querying Garbage Collector State::


File: python.info,  Node: Controlling the Garbage Collector State,  Next: Querying Garbage Collector State,  Up: 循環垃圾回收的支援

7.12.11.1 Controlling the Garbage Collector State
.................................................

The C-API provides the following functions for controlling garbage
collection runs.

 -- C 函式: *note Py_ssize_t: a03. PyGC_Collect (void)
     ' 為 *note 穩定 ABI 的一部分: 4f9.'  Perform a full garbage
     collection, if the garbage collector is enabled.  (Note that *note
     gc.collect(): 16b. runs it unconditionally.)

     Returns the number of collected + unreachable objects which cannot
     be collected.  If the garbage collector is disabled or already
     collecting, returns ‘0’ immediately.  Errors during garbage
     collection are passed to *note sys.unraisablehook: 1dc.  This
     function does not raise exceptions.

 -- C 函式: int PyGC_Enable (void)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本開始.'  Enable the
     garbage collector: similar to *note gc.enable(): 4268.  Returns the
     previous state, 0 for disabled and 1 for enabled.

     在 3.10 版被加入.

 -- C 函式: int PyGC_Disable (void)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本開始.'  Disable the
     garbage collector: similar to *note gc.disable(): 4269.  Returns
     the previous state, 0 for disabled and 1 for enabled.

     在 3.10 版被加入.

 -- C 函式: int PyGC_IsEnabled (void)
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.10 版本開始.'  Query the
     state of the garbage collector: similar to *note gc.isenabled():
     426a.  Returns the current state, 0 for disabled and 1 for enabled.

     在 3.10 版被加入.


File: python.info,  Node: Querying Garbage Collector State,  Prev: Controlling the Garbage Collector State,  Up: 循環垃圾回收的支援

7.12.11.2 Querying Garbage Collector State
..........................................

The C-API provides the following interface for querying information
about the garbage collector.

 -- C 函式: void PyUnstable_GC_VisitObjects (gcvisitobjects_t callback,
          void *arg)

          這是 不穩定 API，它可能在小版本發布中沒有任何警告地被變更。 '這是 *note 不穩定 API: 4ed.，它可能在小版本發布中沒有任何警告地被變更。': 
     Run supplied 'callback' on all live GC-capable objects.  'arg' is
     passed through to all invocations of 'callback'.

          警告: If new objects are (de)allocated by the callback it is
          undefined if they will be visited.

          Garbage collection is disabled during operation.  Explicitly
          running a collection in the callback may lead to undefined
          behaviour e.g.  visiting the same objects multiple times or
          not at all.

     在 3.12 版被加入.

 -- C 型別: typedef int (*gcvisitobjects_t)(*note PyObject: 311.
          *object, void *arg)

     Type of the visitor function to be passed to *note
     PyUnstable_GC_VisitObjects(): 4c77.  'arg' is the same as the 'arg'
     passed to ‘PyUnstable_GC_VisitObjects’.  Return ‘0’ to continue
     iteration, return ‘1’ to stop iteration.  Other return values are
     reserved for now so behavior on returning anything else is
     undefined.

     在 3.12 版被加入.


File: python.info,  Node: API 和 ABI 版本管理,  Next: Monitoring C API,  Prev: Object Implementation Support,  Up: Python/C API 參考手冊

7.13 API 和 ABI 版本管理
========================

CPython 透過以下巨集 (macro) 公開其版本號。請注意，對應到的是'建置
(built)' 所用到的版本，並不一定是'執行環境 (run time)' 所使用的版本。

關於跨版本 API 和 ABI 穩定性的討論，請見 *note C API 穩定性: 4f9.。

 -- C 巨集: PY_MAJOR_VERSION

     在 ‘3.4.1a2’ 中的 ‘3’。

 -- C 巨集: PY_MINOR_VERSION

     在 ‘3.4.1a2’ 中的 ‘4’。

 -- C 巨集: PY_MICRO_VERSION

     在 ‘3.4.1a2’ 中的 ‘1’。

 -- C 巨集: PY_RELEASE_LEVEL

     在 ‘3.4.1a2’ 中的 ‘a’。‘0xA’ 代表 alpha 版本、‘0xB’ 代表 beta 版本
     、‘0xC’ 為發布候選版本、‘0xF’ 則為最終版。

 -- C 巨集: PY_RELEASE_SERIAL

     在 ‘3.4.1a2’ 中的 ‘2’。零則為最終發布版本。

 -- C 巨集: PY_VERSION_HEX

     被編碼為單一整數的 Python 版本號。

     所代表的版本資訊可以用以下規則將其看做是一個 32 位元數字來獲得：

     位元組串    位元（大端位元組序 (big       意義                          ‘3.4.1a2’ 中的值
                 endian order)）                                             
                 
     -------------------------------------------------------------------------------------------------------
                                                                             
     1           1-8                           ‘PY_MAJOR_VERSION’            ‘0x03’
                                                                             
                                                                             
     2           9-16                          ‘PY_MINOR_VERSION’            ‘0x04’
                                                                             
                                                                             
     3           17-24                         ‘PY_MICRO_VERSION’            ‘0x01’
                                                                             
                                                                             
     4           25-28                         ‘PY_RELEASE_LEVEL’            ‘0xA’
                                                                             
                                               
     29-32       ‘PY_RELEASE_SERIAL’           ‘0x2’
                                               

     因此 ‘3.4.1a2’ 代表 hexversion ‘0x030401a2’、‘3.10.0’ 代表
     hexversion ‘0x030a00f0’。

     使用它進行數值比較，例如 ‘#if PY_VERSION_HEX >= ...’。

     該版本也可透過符號 *note Py_Version: 6fa. 獲得。

 -- C 變數: const unsigned long Py_Version
     ' 為 *note 穩定 ABI 的一部分: 4f9. 自 3.11 版本開始.'  編碼為單個常
     數整數的 Python 執行環境版本號，格式與 *note PY_VERSION_HEX: 6fb. 巨
     集相同。這包含在執行環境使用的 Python 版本。

     在 3.11 版被加入.

所有提到的巨集都定義在 Include/patchlevel.h(1)。

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Include/patchlevel.h


File: python.info,  Node: Monitoring C API,  Next: Generating Execution Events,  Prev: API 和 ABI 版本管理,  Up: Python/C API 參考手冊

7.14 Monitoring C API
=====================

Added in version 3.13.

An extension may need to interact with the event monitoring system.
Subscribing to events and registering callbacks can be done via the
Python API exposed in *note sys.monitoring: c4.


File: python.info,  Node: Generating Execution Events,  Prev: Monitoring C API,  Up: Python/C API 參考手冊

7.15 Generating Execution Events
================================

The functions below make it possible for an extension to fire monitoring
events as it emulates the execution of Python code.  Each of these
functions accepts a ‘PyMonitoringState’ struct which contains concise
information about the activation state of events, as well as the event
arguments, which include a ‘PyObject*’ representing the code object, the
instruction offset and sometimes additional, event-specific arguments
(see *note sys.monitoring: c4. for details about the signatures of the
different event callbacks).  The ‘codelike’ argument should be an
instance of *note types.CodeType: 2b6. or of a type that emulates it.

The VM disables tracing when firing an event, so there is no need for
user code to do that.

Monitoring functions should not be called with an exception set, except
those listed below as working with the current exception.

 -- C 型別: type PyMonitoringState

     Representation of the state of an event type.  It is allocated by
     the user while its contents are maintained by the monitoring API
     functions described below.

All of the functions below return 0 on success and -1 (with an exception
set) on error.

See *note sys.monitoring: c4. for descriptions of the events.

 -- C 函式: int PyMonitoring_FirePyStartEvent (PyMonitoringState *state,
          PyObject *codelike, int32_t offset)

     Fire a ‘PY_START’ event.

 -- C 函式: int PyMonitoring_FirePyResumeEvent (PyMonitoringState
          *state, PyObject *codelike, int32_t offset)

     Fire a ‘PY_RESUME’ event.

 -- C 函式: int PyMonitoring_FirePyReturnEvent (PyMonitoringState
          *state, PyObject *codelike, int32_t offset, PyObject *retval)

     Fire a ‘PY_RETURN’ event.

 -- C 函式: int PyMonitoring_FirePyYieldEvent (PyMonitoringState *state,
          PyObject *codelike, int32_t offset, PyObject *retval)

     Fire a ‘PY_YIELD’ event.

 -- C 函式: int PyMonitoring_FireCallEvent (PyMonitoringState *state,
          PyObject *codelike, int32_t offset, PyObject *callable,
          PyObject *arg0)

     Fire a ‘CALL’ event.

 -- C 函式: int PyMonitoring_FireLineEvent (PyMonitoringState *state,
          PyObject *codelike, int32_t offset, int lineno)

     Fire a ‘LINE’ event.

 -- C 函式: int PyMonitoring_FireJumpEvent (PyMonitoringState *state,
          PyObject *codelike, int32_t offset, PyObject *target_offset)

     Fire a ‘JUMP’ event.

 -- C 函式: int PyMonitoring_FireBranchEvent (PyMonitoringState *state,
          PyObject *codelike, int32_t offset, PyObject *target_offset)

     Fire a ‘BRANCH’ event.

 -- C 函式: int PyMonitoring_FireCReturnEvent (PyMonitoringState *state,
          PyObject *codelike, int32_t offset, PyObject *retval)

     Fire a ‘C_RETURN’ event.

 -- C 函式: int PyMonitoring_FirePyThrowEvent (PyMonitoringState *state,
          PyObject *codelike, int32_t offset)

     Fire a ‘PY_THROW’ event with the current exception (as returned by
     *note PyErr_GetRaisedException(): 3bc.).

 -- C 函式: int PyMonitoring_FireRaiseEvent (PyMonitoringState *state,
          PyObject *codelike, int32_t offset)

     Fire a ‘RAISE’ event with the current exception (as returned by
     *note PyErr_GetRaisedException(): 3bc.).

 -- C 函式: int PyMonitoring_FireCRaiseEvent (PyMonitoringState *state,
          PyObject *codelike, int32_t offset)

     Fire a ‘C_RAISE’ event with the current exception (as returned by
     *note PyErr_GetRaisedException(): 3bc.).

 -- C 函式: int PyMonitoring_FireReraiseEvent (PyMonitoringState *state,
          PyObject *codelike, int32_t offset)

     Fire a ‘RERAISE’ event with the current exception (as returned by
     *note PyErr_GetRaisedException(): 3bc.).

 -- C 函式: int PyMonitoring_FireExceptionHandledEvent
          (PyMonitoringState *state, PyObject *codelike, int32_t offset)

     Fire an ‘EXCEPTION_HANDLED’ event with the current exception (as
     returned by *note PyErr_GetRaisedException(): 3bc.).

 -- C 函式: int PyMonitoring_FirePyUnwindEvent (PyMonitoringState
          *state, PyObject *codelike, int32_t offset)

     Fire a ‘PY_UNWIND’ event with the current exception (as returned by
     *note PyErr_GetRaisedException(): 3bc.).

 -- C 函式: int PyMonitoring_FireStopIterationEvent (PyMonitoringState
          *state, PyObject *codelike, int32_t offset, PyObject *value)

     Fire a ‘STOP_ITERATION’ event.  If ‘value’ is an instance of *note
     StopIteration: ba1, it is used.  Otherwise, a new *note
     StopIteration: ba1. instance is created with ‘value’ as its
     argument.

* Menu:

* Managing the Monitoring State::


File: python.info,  Node: Managing the Monitoring State,  Up: Generating Execution Events

7.15.1 Managing the Monitoring State
------------------------------------

Monitoring states can be managed with the help of monitoring scopes.  A
scope would typically correspond to a python function.


File: python.info,  Node: 安裝 Python 模組,  Next: Python 如何達成任務,  Prev: Python/C API 參考手冊,  Up: Top

8 安裝 Python 模組
******************


電子郵件: <distutils-sig@python.org>

作為一個普及的開源開發專案，Python 有一個活躍的支持社群，由其貢獻者及使
用者組成，而他們也讓他們的軟體可被其他 Python 開發者在開源授權條款下使用
。

這樣可以讓 Python 使用者們有效地共享和合作，並受益於其他人對常見（有時甚
至是罕見）的問題已經建立的解決方案，更可以在公用社群中潛在地貢獻他們自己
的解決方案。

這份指南涵蓋了上述過程中的安裝部分。如果是要建立及分享你自己的 Python 專
案，請參考 Python packaging user guide(1)。

     備註: 對於企業和其他機構的使用者，要注意到，許多組織對於使用和貢獻
     開源軟體都有自己的政策。在開始使用配備 Python 的發布及安裝工具時，
     請將那些政策納入考量。

* Menu:

* 關鍵術語::
* 基本用法: 基本用法<3>.
* 我該如何...？: 我該如何 ？.
* 常見的安裝問題::

   ---------- Footnotes ----------

   (1) 
https://packaging.python.org/en/latest/tutorials/packaging-projects/


File: python.info,  Node: 關鍵術語,  Next: 基本用法<3>,  Up: 安裝 Python 模組

8.1 關鍵術語
============

   * ‘pip’ 是首選的安裝程式。從 Python 3.4 開始，它被預設包含在 Python 二
     進制安裝程式中。

   * 'virtual environment（虛擬環境）'是一種半隔離的 Python 環境，可以為
     某個特定應用程式安裝其所需的套件，而不用在整個系統上安裝它們。

   * ‘venv’ 是建立虛擬環境的標準工具，它從 Python 3.3 開始成為 Python 的
     一部分。從 Python 3.4 開始，它會預設地安裝 ‘pip’ 到所有被建立的虛擬
     環境。

   * ‘virtualenv’ 是 ‘venv’ 的一個第三方替代方案（及其前身）。它使虛擬環
     境可以在 Python 3.4 之前的版本被使用，那些版本要不是根本沒提供
     ‘venv’，就是無法自動安裝 ‘pip’ 到所建立的環境中。

   * Python 套件索引 (Python Package Index)(1) 是開源授權套件的一個公共
     儲存庫，其中的套件皆可被其他 Python 使用者所使用。

   * Python 封裝管理站 (Python Packaging Authority)(2) 是一個由開發者和
     說明文件作者組成的團隊，負責維護及改進標準封裝工具，以及相關的元資
     料 (metadata) 和檔案格式標準。他們在 GitHub(3) 平台上維護各種工具、
     說明文件及問題追蹤系統。

   * ‘distutils’ 是最早的建置和發布系統，於 1998 年首次被加入 Python 標
     準函式庫。雖然直接使用 ‘distutils’ 的方式已經被逐步淘汰，它仍然是現
     今封裝和發布的基礎結構根基，而且它不僅仍然是標準函式庫的一部分，它
     的名稱也以其他的方式存活著（例如：用於協調 Python 封裝標準開發的郵
     寄清單就是以它命名）。

在 3.5 版的變更: 對於建立虛擬環境，現在推薦使用 ‘venv’。

也參考
......

Python 封裝使用者指南：建立和使用虛擬環境(4)

   ---------- Footnotes ----------

   (1) https://pypi.org

   (2) https://www.pypa.io/

   (3) https://github.com/pypa

   (4) 
https://packaging.python.org/installing/#creating-virtual-environments


File: python.info,  Node: 基本用法<3>,  Next: 我該如何 ？,  Prev: 關鍵術語,  Up: 安裝 Python 模組

8.2 基本用法
============

標準封裝工具皆是以能從命令列使用的方式被設計的。

以下指令將從 Python 套件索引安裝一個模組的最新版本及其依賴套件
(dependencies)：

     python -m pip install SomePackage

     備註: 對於 POSIX 使用者（包括 macOS 和 Linux 使用者），本指南中的範
     例皆假設有使用 *note virtual environment: 1c04.。

     對於 Windows 使用者，本指南中的範例皆假設在安裝 Python 時，「可調整
     系統 PATH 環境變數」的選項已被選取。

在命令列中直接指定一個明確的或最小的版本也是可行的。當使用像是 ‘>’、‘<’
的比較運算子，或某些可被 shell 所解釋的其他特殊字元時，套件名稱與版本編
號應該要放在雙引號內：

     python -m pip install SomePackage==1.0.4    # specific version
     python -m pip install "SomePackage>=1.0.4"  # minimum version

通常，如果一個合適的模組已被安裝，嘗試再次安裝它將不會有任何效果。要升級
現有的模組就必須明確地請求：

     python -m pip install --upgrade SomePackage

關於 ‘pip’ 及其能力的更多資訊和資源，可以在 Python 封裝使用者指南(1)中找
到。

虛擬環境的建立是使用 *note venv: f9. 模組來完成。要在一個已啟用的虛擬環
境中安裝套件，可使用前面展示的指令。

也參考
......

Python 封裝使用者指南：安裝 Python 發布套件(2)

   ---------- Footnotes ----------

   (1) https://packaging.python.org

   (2) https://packaging.python.org/installing/


File: python.info,  Node: 我該如何 ？,  Next: 常見的安裝問題,  Prev: 基本用法<3>,  Up: 安裝 Python 模組

8.3 我該如何...？
=================

接下來是關於一些常見任務的快速解答或連結。

* Menu:

* ...在 Python 3.4 之前的 Python 版本中安裝 pip？: 在 Python 3 4 之前的 Python 版本中安裝 pip？.
* ...只為目前的使用者安裝套件？: 只為目前的使用者安裝套件？.
* ...安裝科學的 Python 套件？: 安裝科學的 Python 套件？.
* ...平行安裝多個 Python 版本並使用它們？: 平行安裝多個 Python 版本並使用它們？.


File: python.info,  Node: 在 Python 3 4 之前的 Python 版本中安裝 pip？,  Next: 只為目前的使用者安裝套件？,  Up: 我該如何 ？

8.3.1 ...在 Python 3.4 之前的 Python 版本中安裝 ‘pip’？
-------------------------------------------------------

Python 是從 Python 3.4 才開始綁定 ‘pip’ 的。對於更早的版本，‘pip’ 需要被
「自助安裝 (bootstrapped)」，請參考 Python 封裝使用者指南中的說明。

也參考
......

Python 封裝使用者指南：安裝套件的需求(1)

   ---------- Footnotes ----------

   (1) 
https://packaging.python.org/installing/#requirements-for-installing-packages


File: python.info,  Node: 只為目前的使用者安裝套件？,  Next: 安裝科學的 Python 套件？,  Prev: 在 Python 3 4 之前的 Python 版本中安裝 pip？,  Up: 我該如何 ？

8.3.2 ...只為目前的使用者安裝套件？
-----------------------------------

把 ‘--user’ 選項傳給 ‘python -m pip install’，這樣將會只為目前使用者而非
系統的所有使用者安裝套件。


File: python.info,  Node: 安裝科學的 Python 套件？,  Next: 平行安裝多個 Python 版本並使用它們？,  Prev: 只為目前的使用者安裝套件？,  Up: 我該如何 ？

8.3.3 ...安裝科學的 Python 套件？
---------------------------------

許多科學類 Python 套件都有複雜的二進制依賴套件，且目前不太容易直接使用
‘pip’ 安裝。目前為止，使用其他方法(1)而非嘗試用 ‘pip’ 來安裝它們，對使用
者來說通常會更簡單。

也參考
......

Python 封裝使用者指南：安裝科學套件(2)

   ---------- Footnotes ----------

   (1) https://packaging.python.org/science/

   (2) https://packaging.python.org/science/


File: python.info,  Node: 平行安裝多個 Python 版本並使用它們？,  Prev: 安裝科學的 Python 套件？,  Up: 我該如何 ？

8.3.4 ...平行安裝多個 Python 版本並使用它們？
---------------------------------------------

在 Linux、macOS 以及其他 POSIX 系統中，使用帶有版本編號的 Python 指令並
結合 ‘-m’ 開關參數 (switch)，來運行 ‘pip’ 的適當副本：

     python2   -m pip install SomePackage  # default Python 2
     python2.7 -m pip install SomePackage  # specifically Python 2.7
     python3   -m pip install SomePackage  # default Python 3
     python3.4 -m pip install SomePackage  # specifically Python 3.4

使用帶有合適版本編號的 ‘pip’ 指令，也是可行的。

在 Windows 中，使用 Python 啟動指令 ‘py’ 並結合 ‘-m’ 開關參數 (switch)：

     py -2   -m pip install SomePackage  # default Python 2
     py -2.7 -m pip install SomePackage  # specifically Python 2.7
     py -3   -m pip install SomePackage  # default Python 3
     py -3.4 -m pip install SomePackage  # specifically Python 3.4


File: python.info,  Node: 常見的安裝問題,  Prev: 我該如何 ？,  Up: 安裝 Python 模組

8.4 常見的安裝問題
==================

* Menu:

* 在 Linux 上安裝套件至系統 Python::
* 未安裝 pip::
* 安裝二進制擴充 (binary extension): 安裝二進制擴充 binary extension.


File: python.info,  Node: 在 Linux 上安裝套件至系統 Python,  Next: 未安裝 pip,  Up: 常見的安裝問題

8.4.1 在 Linux 上安裝套件至系統 Python
--------------------------------------

在 Linux 系統，Python 的某個安裝版本通常會被內含在 Linux 的發行版中。要
安裝套件到這個 Python 版本上需要系統的 root 權限，並且可能會干擾到系統套
件管理器的運作。如果其他系統組件非預期地以 ‘pip’ 被升級，也會干擾這些組
件的運作。

在這樣的系統上，以 ‘pip’ 安裝套件時，通常較好的方式是使用虛擬環境，或以
個別使用者安裝。


File: python.info,  Node: 未安裝 pip,  Next: 安裝二進制擴充 binary extension,  Prev: 在 Linux 上安裝套件至系統 Python,  Up: 常見的安裝問題

8.4.2 未安裝 pip
----------------

‘pip’ 沒有預設被安裝也是有可能的。一個潛在的解法是：

     python -m ensurepip --default-pip

這裡還有其他關於安裝 pip(1)的資源。

   ---------- Footnotes ----------

   (1) 
https://packaging.python.org/en/latest/tutorials/installing-packages/#ensure-pip-setuptools-and-wheel-are-up-to-date


File: python.info,  Node: 安裝二進制擴充 binary extension,  Prev: 未安裝 pip,  Up: 常見的安裝問題

8.4.3 安裝二進制擴充 (binary extension)
---------------------------------------

Python 基本上相當倚賴以原始碼為基礎的發布方式，也會期望使用者在安裝過程
的某個階段，從原始碼來編譯擴充模組。

隨著引入對二進制 ‘wheel’ 格式的支援，以及透過 Python 套件索引能夠至少在
Windows 和 macOS 發布 wheel 檔案，這個問題預期將會逐漸消失，因為使用者將
能夠更頻繁地安裝預建置 (pre-built) 的擴充，而不再需要自己建置它們。

有一些解決方案，可用來安裝那些還無法以預建置的 ‘wheel’ 檔案被使用的科學
軟體(1)，這些方案也有助於取得其他的二進制擴充，且無需在本機對它們進行建
置。

也參考
......

Python 封裝使用者指南：二進制擴充(2)

   ---------- Footnotes ----------

   (1) https://packaging.python.org/science/

   (2) https://packaging.python.org/extensions/


File: python.info,  Node: Python 如何達成任務,  Next: Python 常見問題,  Prev: 安裝 Python 模組,  Up: Top

9 Python 如何達成任務
*********************

Python HOWTOs are documents that cover a specific topic in-depth.
Modeled on the Linux Documentation Project's HOWTO collection, this
collection is an effort to foster documentation that's more detailed
than the Python Library Reference.

* Menu:

* 遷移延伸模組到 Python 3::
* Curses Programming with Python::
* 描述器 (Descriptor) 指南: 描述器 Descriptor 指南.
* 使用 GDB 來為 C API 擴充功能和 CPython 內部偵錯::
* Enum HOWTO::
* 函式編程 HOWTO::
* 如何使用 Logging 模組::
* Logging Cookbook::
* 如何使用正規表示式::
* Socket 程式設計指南::
* 排序技法::
* Unicode HOWTO::
* 如何使用 urllib 套件取得網路資源::
* Argparse 教學::
* ipaddress 模組介紹::
* 使用 DTrace 和 SystemTap 檢測 CPython::
* Python 對 Linux perf 分析器的支援::
* 註釋 (annotation) 最佳實踐: 註釋 annotation 最佳實踐.
* 隔離擴充模組::
* timer file descriptor HOWTO::
* The Python 2.3 Method Resolution Order: The Python 2 3 Method Resolution Order.
* C API Extension Support for Free Threading::


File: python.info,  Node: 遷移延伸模組到 Python 3,  Next: Curses Programming with Python,  Up: Python 如何達成任務

9.1 遷移延伸模組到 Python 3
===========================

We recommend the following resources for porting extension modules to
Python 3:

   * The Migrating C extensions(1) chapter from 'Supporting Python 3: An
     in-depth guide', a book on moving from Python 2 to Python 3 in
     general, guides the reader through porting an extension module.

   * The Porting guide(2) from the 'py3c' project provides opinionated
     suggestions with supporting code.

   * The Cython(3) and CFFI(4) libraries offer abstractions over
     Python's C API. Extensions generally need to be re-written to use
     one of them, but the library then handles differences between
     various Python versions and implementations.

   ---------- Footnotes ----------

   (1) http://python3porting.com/cextensions.html

   (2) https://py3c.readthedocs.io/en/latest/guide.html

   (3) https://cython.org/

   (4) https://cffi.readthedocs.io/en/latest/


File: python.info,  Node: Curses Programming with Python,  Next: 描述器 Descriptor 指南,  Prev: 遷移延伸模組到 Python 3,  Up: Python 如何達成任務

9.2 Curses Programming with Python
==================================


作者: A.M. Kuchling, Eric S. Raymond


發佈版本: 2.04

摘要
....

This document describes how to use the *note curses: 23. extension
module to control text-mode displays.

* Menu:

* What is curses?::
* Starting and ending a curses application::
* Windows and Pads::
* Displaying Text::
* 使用者輸入::
* For More Information::


File: python.info,  Node: What is curses?,  Next: Starting and ending a curses application,  Up: Curses Programming with Python

9.2.1 What is curses?
---------------------

The curses library supplies a terminal-independent screen-painting and
keyboard-handling facility for text-based terminals; such terminals
include VT100s, the Linux console, and the simulated terminal provided
by various programs.  Display terminals support various control codes to
perform common operations such as moving the cursor, scrolling the
screen, and erasing areas.  Different terminals use widely differing
codes, and often have their own minor quirks.

In a world of graphical displays, one might ask "why bother"?  It's true
that character-cell display terminals are an obsolete technology, but
there are niches in which being able to do fancy things with them are
still valuable.  One niche is on small-footprint or embedded Unixes that
don't run an X server.  Another is tools such as OS installers and
kernel configurators that may have to run before any graphical support
is available.

The curses library provides fairly basic functionality, providing the
programmer with an abstraction of a display containing multiple
non-overlapping windows of text.  The contents of a window can be
changed in various ways--adding text, erasing it, changing its
appearance--and the curses library will figure out what control codes
need to be sent to the terminal to produce the right output.  curses
doesn't provide many user-interface concepts such as buttons,
checkboxes, or dialogs; if you need such features, consider a user
interface library such as Urwid(1).

The curses library was originally written for BSD Unix; the later System
V versions of Unix from AT&T added many enhancements and new functions.
BSD curses is no longer maintained, having been replaced by ncurses,
which is an open-source implementation of the AT&T interface.  If you're
using an open-source Unix such as Linux or FreeBSD, your system almost
certainly uses ncurses.  Since most current commercial Unix versions are
based on System V code, all the functions described here will probably
be available.  The older versions of curses carried by some proprietary
Unixes may not support everything, though.

The Windows version of Python doesn't include the *note curses: 23.
module.  A ported version called UniCurses(2) is available.

* Menu:

* Python curses 模組::

   ---------- Footnotes ----------

   (1) https://pypi.org/project/Urwid/

   (2) https://pypi.org/project/UniCurses/


File: python.info,  Node: Python curses 模組,  Up: What is curses?

9.2.1.1 Python curses 模組
..........................

The Python module is a fairly simple wrapper over the C functions
provided by curses; if you're already familiar with curses programming
in C, it's really easy to transfer that knowledge to Python.  The
biggest difference is that the Python interface makes things simpler by
merging different C functions such as ‘addstr()’, ‘mvaddstr()’, and
‘mvwaddstr()’ into a single *note addstr(): 2c98. method.  You'll see
this covered in more detail later.

This HOWTO is an introduction to writing text-mode programs with curses
and Python.  It doesn't attempt to be a complete guide to the curses
API; for that, see the Python library guide's section on ncurses, and
the C manual pages for ncurses.  It will, however, give you the basic
ideas.


File: python.info,  Node: Starting and ending a curses application,  Next: Windows and Pads,  Prev: What is curses?,  Up: Curses Programming with Python

9.2.2 Starting and ending a curses application
----------------------------------------------

Before doing anything, curses must be initialized.  This is done by
calling the *note initscr(): 2c9e. function, which will determine the
terminal type, send any required setup codes to the terminal, and create
various internal data structures.  If successful, ‘initscr()’ returns a
window object representing the entire screen; this is usually called
‘stdscr’ after the name of the corresponding C variable.

     import curses
     stdscr = curses.initscr()

Usually curses applications turn off automatic echoing of keys to the
screen, in order to be able to read keys and only display them under
certain circumstances.  This requires calling the *note noecho(): 2cc5.
function.

     curses.noecho()

Applications will also commonly need to react to keys instantly, without
requiring the Enter key to be pressed; this is called cbreak mode, as
opposed to the usual buffered input mode.

     curses.cbreak()

Terminals usually return special keys, such as the cursor keys or
navigation keys such as Page Up and Home, as a multibyte escape
sequence.  While you could write your application to expect such
sequences and process them accordingly, curses can do it for you,
returning a special value such as *note curses.KEY_LEFT: 2d40.  To get
curses to do the job, you'll have to enable keypad mode.

     stdscr.keypad(True)

Terminating a curses application is much easier than starting one.
You'll need to call:

     curses.nocbreak()
     stdscr.keypad(False)
     curses.echo()

to reverse the curses-friendly terminal settings.  Then call the *note
endwin(): 2c9b. function to restore the terminal to its original
operating mode.

     curses.endwin()

A common problem when debugging a curses application is to get your
terminal messed up when the application dies without restoring the
terminal to its previous state.  In Python this commonly happens when
your code is buggy and raises an uncaught exception.  Keys are no longer
echoed to the screen when you type them, for example, which makes using
the shell difficult.

In Python you can avoid these complications and make debugging much
easier by importing the *note curses.wrapper(): a23. function and using
it like this:

     from curses import wrapper

     def main(stdscr):
         # Clear screen
         stdscr.clear()

         # This raises ZeroDivisionError when i == 10.
         for i in range(0, 11):
             v = i-10
             stdscr.addstr(i, 0, '10 divided by {} is {}'.format(v, 10/v))

         stdscr.refresh()
         stdscr.getkey()

     wrapper(main)

The *note wrapper(): a23. function takes a callable object and does the
initializations described above, also initializing colors if color
support is present.  ‘wrapper()’ then runs your provided callable.  Once
the callable returns, ‘wrapper()’ will restore the original state of the
terminal.  The callable is called inside a *note try: 68c...*note
except: 171. that catches exceptions, restores the state of the
terminal, and then re-raises the exception.  Therefore your terminal
won't be left in a funny state on exception and you'll be able to read
the exception's message and traceback.


File: python.info,  Node: Windows and Pads,  Next: Displaying Text,  Prev: Starting and ending a curses application,  Up: Curses Programming with Python

9.2.3 Windows and Pads
----------------------

Windows are the basic abstraction in curses.  A window object represents
a rectangular area of the screen, and supports methods to display text,
erase it, allow the user to input strings, and so forth.

The ‘stdscr’ object returned by the *note initscr(): 2c9e. function is a
window object that covers the entire screen.  Many programs may need
only this single window, but you might wish to divide the screen into
smaller windows, in order to redraw or clear them separately.  The *note
newwin(): 2cc3. function creates a new window of a given size, returning
the new window object.

     begin_x = 20; begin_y = 7
     height = 5; width = 40
     win = curses.newwin(height, width, begin_y, begin_x)

Note that the coordinate system used in curses is unusual.  Coordinates
are always passed in the order 'y,x', and the top-left corner of a
window is coordinate (0,0).  This breaks the normal convention for
handling coordinates where the 'x' coordinate comes first.  This is an
unfortunate difference from most other computer applications, but it's
been part of curses since it was first written, and it's too late to
change things now.

Your application can determine the size of the screen by using the *note
curses.LINES: 1608. and *note curses.COLS: 1609. variables to obtain the
'y' and 'x' sizes.  Legal coordinates will then extend from ‘(0,0)’ to
‘(curses.LINES - 1, curses.COLS - 1)’.

When you call a method to display or erase text, the effect doesn't
immediately show up on the display.  Instead you must call the *note
refresh(): 2c99. method of window objects to update the screen.

This is because curses was originally written with slow 300-baud
terminal connections in mind; with these terminals, minimizing the time
required to redraw the screen was very important.  Instead curses
accumulates changes to the screen and displays them in the most
efficient manner when you call ‘refresh()’.  For example, if your
program displays some text in a window and then clears the window,
there's no need to send the original text because they're never visible.

In practice, explicitly telling curses to redraw a window doesn't really
complicate programming with curses much.  Most programs go into a flurry
of activity, and then pause waiting for a keypress or some other action
on the part of the user.  All you have to do is to be sure that the
screen has been redrawn before pausing to wait for user input, by first
calling ‘stdscr.refresh()’ or the ‘refresh()’ method of some other
relevant window.

A pad is a special case of a window; it can be larger than the actual
display screen, and only a portion of the pad displayed at a time.
Creating a pad requires the pad's height and width, while refreshing a
pad requires giving the coordinates of the on-screen area where a
subsection of the pad will be displayed.

     pad = curses.newpad(100, 100)
     # These loops fill the pad with letters; addch() is
     # explained in the next section
     for y in range(0, 99):
         for x in range(0, 99):
             pad.addch(y,x, ord('a') + (x*x+y*y) % 26)

     # Displays a section of the pad in the middle of the screen.
     # (0,0) : coordinate of upper-left corner of pad area to display.
     # (5,5) : coordinate of upper-left corner of window area to be filled
     #         with pad content.
     # (20, 75) : coordinate of lower-right corner of window area to be
     #          : filled with pad content.
     pad.refresh( 0,0, 5,5, 20,75)

The ‘refresh()’ call displays a section of the pad in the rectangle
extending from coordinate (5,5) to coordinate (20,75) on the screen; the
upper left corner of the displayed section is coordinate (0,0) on the
pad.  Beyond that difference, pads are exactly like ordinary windows and
support the same methods.

If you have multiple windows and pads on screen there is a more
efficient way to update the screen and prevent annoying screen flicker
as each part of the screen gets updated.  ‘refresh()’ actually does two
things:

  1. Calls the *note noutrefresh(): 2c97. method of each window to
     update an underlying data structure representing the desired state
     of the screen.

  2. Calls the function *note doupdate(): 2c96. function to change the
     physical screen to match the desired state recorded in the data
     structure.

Instead you can call ‘noutrefresh()’ on a number of windows to update
the data structure, and then call ‘doupdate()’ to update the screen.


File: python.info,  Node: Displaying Text,  Next: 使用者輸入,  Prev: Windows and Pads,  Up: Curses Programming with Python

9.2.4 Displaying Text
---------------------

From a C programmer's point of view, curses may sometimes look like a
twisty maze of functions, all subtly different.  For example, ‘addstr()’
displays a string at the current cursor location in the ‘stdscr’ window,
while ‘mvaddstr()’ moves to a given y,x coordinate first before
displaying the string.  ‘waddstr()’ is just like ‘addstr()’, but allows
specifying a window to use instead of using ‘stdscr’ by default.
‘mvwaddstr()’ allows specifying both a window and a coordinate.

Fortunately the Python interface hides all these details.  ‘stdscr’ is a
window object like any other, and methods such as *note addstr(): 2c98.
accept multiple argument forms.  Usually there are four different forms.

Form                                  描述
                                      
------------------------------------------------------------------------------------------
                                      
'str' 或 'ch'                         Display the string 'str' or character 'ch' at the
                                      current position
                                      
                                      
'str' or 'ch', 'attr'                 Display the string 'str' or character 'ch', using
                                      attribute 'attr' at the current position
                                      
                                      
'y'、'x'、'str' 或 'ch'               Move to position 'y,x' within the window, and
                                      display 'str' or 'ch'
                                      
                                      
'y'、'x'、'str' 或 'ch'、'attr'       Move to position 'y,x' within the window, and
                                      display 'str' or 'ch', using attribute 'attr'
                                      

Attributes allow displaying text in highlighted forms such as boldface,
underline, reverse code, or in color.  They'll be explained in more
detail in the next subsection.

The *note addstr(): 2c98. method takes a Python string or bytestring as
the value to be displayed.  The contents of bytestrings are sent to the
terminal as-is.  Strings are encoded to bytes using the value of the
window's *note encoding: 1037. attribute; this defaults to the default
system encoding as returned by *note locale.getencoding(): 2bc.

The *note addch(): 2cdf. methods take a character, which can be either a
string of length 1, a bytestring of length 1, or an integer.

Constants are provided for extension characters; these constants are
integers greater than 255.  For example, *note ACS_PLMINUS: 2dad. is a
+/- symbol, and *note ACS_ULCORNER: 2ce9. is the upper left corner of a
box (handy for drawing borders).  You can also use the appropriate
Unicode character.

Windows remember where the cursor was left after the last operation, so
if you leave out the 'y,x' coordinates, the string or character will be
displayed wherever the last operation left off.  You can also move the
cursor with the ‘move(y,x)’ method.  Because some terminals always
display a flashing cursor, you may want to ensure that the cursor is
positioned in some location where it won't be distracting; it can be
confusing to have the cursor blinking at some apparently random
location.

If your application doesn't need a blinking cursor at all, you can call
‘curs_set(False)’ to make it invisible.  For compatibility with older
curses versions, there's a ‘leaveok(bool)’ function that's a synonym for
*note curs_set(): 2c90.  When 'bool' is true, the curses library will
attempt to suppress the flashing cursor, and you won't need to worry
about leaving it in odd locations.

* Menu:

* Attributes and Color::


File: python.info,  Node: Attributes and Color,  Up: Displaying Text

9.2.4.1 Attributes and Color
............................

Characters can be displayed in different ways.  Status lines in a
text-based application are commonly shown in reverse video, or a text
viewer may need to highlight certain words.  curses supports this by
allowing you to specify an attribute for each cell on the screen.

An attribute is an integer, each bit representing a different attribute.
You can try to display text with multiple attribute bits set, but curses
doesn't guarantee that all the possible combinations are available, or
that they're all visually distinct.  That depends on the ability of the
terminal being used, so it's safest to stick to the most commonly
available attributes, listed here.

屬性                       描述
                           
----------------------------------------------------------------------
                           
*note A_BLINK: 2d2c.       Blinking text
                           
                           
*note A_BOLD: 2d2d.        Extra bright or bold text
                           
                           
*note A_DIM: 2d2e.         Half bright text
                           
                           
*note A_REVERSE: 2c8e.     Reverse-video text
                           
                           
*note A_STANDOUT: 2c8d.    The best highlighting mode available
                           
                           
*note A_UNDERLINE: 2d32.   Underlined text
                           

So, to display a reverse-video status line on the top line of the
screen, you could code:

     stdscr.addstr(0, 0, "Current mode: Typing mode",
                   curses.A_REVERSE)
     stdscr.refresh()

The curses library also supports color on those terminals that provide
it.  The most common such terminal is probably the Linux console,
followed by color xterms.

To use color, you must call the *note start_color(): 2cd0. function soon
after calling *note initscr(): 2c9e, to initialize the default color set
(the *note curses.wrapper(): a23. function does this automatically).
Once that's done, the *note has_colors(): 2cb0. function returns TRUE if
the terminal in use can actually display color.  (Note: curses uses the
American spelling 'color', instead of the Canadian/British spelling
'colour'.  If you're used to the British spelling, you'll have to resign
yourself to misspelling it for the sake of these functions.)

The curses library maintains a finite number of color pairs, containing
a foreground (or text) color and a background color.  You can get the
attribute value corresponding to a color pair with the *note
color_pair(): 2c8c. function; this can be bitwise-OR'ed with other
attributes such as *note A_REVERSE: 2c8e, but again, such combinations
are not guaranteed to work on all terminals.

An example, which displays a line of text using color pair 1:

     stdscr.addstr("Pretty text", curses.color_pair(1))
     stdscr.refresh()

As I said before, a color pair consists of a foreground and background
color.  The ‘init_pair(n, f, b)’ function changes the definition of
color pair 'n', to foreground color f and background color b.  Color
pair 0 is hard-wired to white on black, and cannot be changed.

Colors are numbered, and *note start_color(): 2cd0. initializes 8 basic
colors when it activates color mode.  They are: 0:black, 1:red, 2:green,
3:yellow, 4:blue, 5:magenta, 6:cyan, and 7:white.  The *note curses: 23.
module defines named constants for each of these colors: *note
curses.COLOR_BLACK: 2dbf, *note curses.COLOR_RED: 2dc4, and so forth.

Let's put all this together.  To change color 1 to red text on a white
background, you would call:

     curses.init_pair(1, curses.COLOR_RED, curses.COLOR_WHITE)

When you change a color pair, any text already displayed using that
color pair will change to the new colors.  You can also display new text
in this color with:

     stdscr.addstr(0,0, "RED ALERT!", curses.color_pair(1))

Very fancy terminals can change the definitions of the actual colors to
a given RGB value.  This lets you change color 1, which is usually red,
to purple or blue or any other color you like.  Unfortunately, the Linux
console doesn't support this, so I'm unable to try it out, and can't
provide any examples.  You can check if your terminal can do this by
calling *note can_change_color(): 2c89, which returns ‘True’ if the
capability is there.  If you're lucky enough to have such a talented
terminal, consult your system's man pages for more information.


File: python.info,  Node: 使用者輸入,  Next: For More Information,  Prev: Displaying Text,  Up: Curses Programming with Python

9.2.5 使用者輸入
----------------

The C curses library offers only very simple input mechanisms.  Python's
*note curses: 23. module adds a basic text-input widget.  (Other
libraries such as Urwid(1) have more extensive collections of widgets.)

There are two methods for getting input from a window:

   * *note getch(): 2ca2. refreshes the screen and then waits for the
     user to hit a key, displaying the key if *note echo(): 2c9a. has
     been called earlier.  You can optionally specify a coordinate to
     which the cursor should be moved before pausing.

   * *note getkey(): 2cfd. does the same thing but converts the integer
     to a string.  Individual characters are returned as 1-character
     strings, and special keys such as function keys return longer
     strings containing a key name such as ‘KEY_UP’ or ‘^G’.

It's possible to not wait for the user using the *note nodelay(): 2d13.
window method.  After ‘nodelay(True)’, ‘getch()’ and ‘getkey()’ for the
window become non-blocking.  To signal that no input is ready, ‘getch()’
returns ‘curses.ERR’ (a value of -1) and ‘getkey()’ raises an exception.
There's also a *note halfdelay(): 2cb4. function, which can be used to
(in effect) set a timer on each ‘getch()’; if no input becomes available
within a specified delay (measured in tenths of a second), curses raises
an exception.

The ‘getch()’ method returns an integer; if it's between 0 and 255, it
represents the ASCII code of the key pressed.  Values greater than 255
are special keys such as Page Up, Home, or the cursor keys.  You can
compare the value returned to constants such as *note curses.KEY_PPAGE:
2d51, *note curses.KEY_HOME: 2d42, or *note curses.KEY_LEFT: 2d40.  The
main loop of your program may look something like this:

     while True:
         c = stdscr.getch()
         if c == ord('p'):
             PrintDocument()
         elif c == ord('q'):
             break  # Exit the while loop
         elif c == curses.KEY_HOME:
             x = y = 0

The *note curses.ascii: 24. module supplies ASCII class membership
functions that take either integer or 1-character string arguments;
these may be useful in writing more readable tests for such loops.  It
also supplies conversion functions that take either integer or
1-character-string arguments and return the same type.  For example,
*note curses.ascii.ctrl(): 2e06. returns the control character
corresponding to its argument.

There's also a method to retrieve an entire string, *note getstr():
2d00.  It isn't used very often, because its functionality is quite
limited; the only editing keys available are the backspace key and the
Enter key, which terminates the string.  It can optionally be limited to
a fixed number of characters.

     curses.echo()            # Enable echoing of characters

     # Get a 15-character string, with the cursor on the top line
     s = stdscr.getstr(0,0, 15)

The *note curses.textpad: 26. module supplies a text box that supports
an Emacs-like set of keybindings.  Various methods of the *note Textbox:
2dc8. class support editing with input validation and gathering the edit
results either with or without trailing spaces.  Here's an example:

     import curses
     from curses.textpad import Textbox, rectangle

     def main(stdscr):
         stdscr.addstr(0, 0, "Enter IM message: (hit Ctrl-G to send)")

         editwin = curses.newwin(5,30, 2,1)
         rectangle(stdscr, 1,0, 1+5+1, 1+30+1)
         stdscr.refresh()

         box = Textbox(editwin)

         # Let the user edit until Ctrl-G is struck.
         box.edit()

         # Get resulting contents
         message = box.gather()

See the library documentation on *note curses.textpad: 26. for more
details.

   ---------- Footnotes ----------

   (1) https://pypi.org/project/Urwid/


File: python.info,  Node: For More Information,  Prev: 使用者輸入,  Up: Curses Programming with Python

9.2.6 For More Information
--------------------------

This HOWTO doesn't cover some advanced topics, such as reading the
contents of the screen or capturing mouse events from an xterm instance,
but the Python library page for the *note curses: 23. module is now
reasonably complete.  You should browse it next.

If you're in doubt about the detailed behavior of the curses functions,
consult the manual pages for your curses implementation, whether it's
ncurses or a proprietary Unix vendor's.  The manual pages will document
any quirks, and provide complete lists of all the functions, attributes,
and *note ACS_*: 2d99. characters available to you.

Because the curses API is so large, some functions aren't supported in
the Python interface.  Often this isn't because they're difficult to
implement, but because no one has needed them yet.  Also, Python doesn't
yet support the menu library associated with ncurses.  Patches adding
support for these would be welcome; see the Python Developer's Guide(1)
to learn more about submitting patches to Python.

   * Writing Programs with NCURSES(2): a lengthy tutorial for C
     programmers.

   * ncurses 使用者手冊(3)

   * ncurses 問答集(4)

   * "Use curses...  don't swear"(5): video of a PyCon 2013 talk on
     controlling terminals using curses or Urwid.

   * "Console Applications with Urwid"(6): video of a PyCon CA 2012 talk
     demonstrating some applications written using Urwid.

   ---------- Footnotes ----------

   (1) https://devguide.python.org/

   (2) https://invisible-island.net/ncurses/ncurses-intro.html

   (3) https://linux.die.net/man/3/ncurses

   (4) https://invisible-island.net/ncurses/ncurses.faq.html

   (5) https://www.youtube.com/watch?v=eN1eZtjLEnU

   (6) https://pyvideo.org/video/1568/console-applications-with-urwid


File: python.info,  Node: 描述器 Descriptor 指南,  Next: 使用 GDB 來為 C API 擴充功能和 CPython 內部偵錯,  Prev: Curses Programming with Python,  Up: Python 如何達成任務

9.3 描述器 (Descriptor) 指南
============================


作者: Raymond Hettinger


聯絡方式: <python at rcn dot com>

*note 描述器: 1e47.讓物件自訂屬性能夠被查找、儲存和刪除。

此指南有四個主要章節：

  1. The "primer" gives a basic overview, moving gently from simple
     examples, adding one feature at a time.  Start here if you're new
     to descriptors.

  2. The second section shows a complete, practical descriptor example.
     If you already know the basics, start there.

  3. The third section provides a more technical tutorial that goes into
     the detailed mechanics of how descriptors work.  Most people don't
     need this level of detail.

  4. The last section has pure Python equivalents for built-in
     descriptors that are written in C. Read this if you're curious
     about how functions turn into bound methods or about the
     implementation of common tools like *note classmethod(): 14a, *note
     staticmethod(): 358, *note property(): 180, and *note __slots__:
     583.

* Menu:

* Primer::
* Complete Practical Example::
* Technical Tutorial::
* Pure Python Equivalents::


File: python.info,  Node: Primer,  Next: Complete Practical Example,  Up: 描述器 Descriptor 指南

9.3.1 Primer
------------

In this primer, we start with the most basic possible example and then
we'll add new capabilities one by one.

* Menu:

* Simple example; A descriptor that returns a constant: Simple example A descriptor that returns a constant.
* Dynamic lookups::
* Managed attributes::
* Customized names::
* Closing thoughts::


File: python.info,  Node: Simple example A descriptor that returns a constant,  Next: Dynamic lookups,  Up: Primer

9.3.1.1 Simple example: A descriptor that returns a constant
............................................................

The ‘Ten’ class is a descriptor whose ‘__get__()’ method always returns
the constant ‘10’:

     class Ten:
         def __get__(self, obj, objtype=None):
             return 10

To use the descriptor, it must be stored as a class variable in another
class:

     class A:
         x = 5                       # Regular class attribute
         y = Ten()                   # Descriptor instance

An interactive session shows the difference between normal attribute
lookup and descriptor lookup:

     >>> a = A()                     # Make an instance of class A
     >>> a.x                         # Normal attribute lookup
     5
     >>> a.y                         # Descriptor lookup
     10

In the ‘a.x’ attribute lookup, the dot operator finds ‘'x': 5’ in the
class dictionary.  In the ‘a.y’ lookup, the dot operator finds a
descriptor instance, recognized by its ‘__get__’ method.  Calling that
method returns ‘10’.

Note that the value ‘10’ is not stored in either the class dictionary or
the instance dictionary.  Instead, the value ‘10’ is computed on demand.

This example shows how a simple descriptor works, but it isn't very
useful.  For retrieving constants, normal attribute lookup would be
better.

In the next section, we'll create something more useful, a dynamic
lookup.


File: python.info,  Node: Dynamic lookups,  Next: Managed attributes,  Prev: Simple example A descriptor that returns a constant,  Up: Primer

9.3.1.2 Dynamic lookups
.......................

Interesting descriptors typically run computations instead of returning
constants:

     import os

     class DirectorySize:

         def __get__(self, obj, objtype=None):
             return len(os.listdir(obj.dirname))

     class Directory:

         size = DirectorySize()              # Descriptor instance

         def __init__(self, dirname):
             self.dirname = dirname          # Regular instance attribute

An interactive session shows that the lookup is dynamic — it computes
different, updated answers each time:

     >>> s = Directory('songs')
     >>> g = Directory('games')
     >>> s.size                              # The songs directory has twenty files
     20
     >>> g.size                              # The games directory has three files
     3
     >>> os.remove('games/chess')            # Delete a game
     >>> g.size                              # File count is automatically updated
     2

Besides showing how descriptors can run computations, this example also
reveals the purpose of the parameters to ‘__get__()’.  The 'self'
parameter is 'size', an instance of 'DirectorySize'.  The 'obj'
parameter is either 'g' or 's', an instance of 'Directory'.  It is the
'obj' parameter that lets the ‘__get__()’ method learn the target
directory.  The 'objtype' parameter is the class 'Directory'.


File: python.info,  Node: Managed attributes,  Next: Customized names,  Prev: Dynamic lookups,  Up: Primer

9.3.1.3 Managed attributes
..........................

A popular use for descriptors is managing access to instance data.  The
descriptor is assigned to a public attribute in the class dictionary
while the actual data is stored as a private attribute in the instance
dictionary.  The descriptor's ‘__get__()’ and ‘__set__()’ methods are
triggered when the public attribute is accessed.

In the following example, 'age' is the public attribute and '_age' is
the private attribute.  When the public attribute is accessed, the
descriptor logs the lookup or update:

     import logging

     logging.basicConfig(level=logging.INFO)

     class LoggedAgeAccess:

         def __get__(self, obj, objtype=None):
             value = obj._age
             logging.info('Accessing %r giving %r', 'age', value)
             return value

         def __set__(self, obj, value):
             logging.info('Updating %r to %r', 'age', value)
             obj._age = value

     class Person:

         age = LoggedAgeAccess()             # Descriptor instance

         def __init__(self, name, age):
             self.name = name                # Regular instance attribute
             self.age = age                  # Calls __set__()

         def birthday(self):
             self.age += 1                   # Calls both __get__() and __set__()

An interactive session shows that all access to the managed attribute
'age' is logged, but that the regular attribute 'name' is not logged:

     >>> mary = Person('Mary M', 30)         # The initial age update is logged
     INFO:root:Updating 'age' to 30
     >>> dave = Person('David D', 40)
     INFO:root:Updating 'age' to 40

     >>> vars(mary)                          # The actual data is in a private attribute
     {'name': 'Mary M', '_age': 30}
     >>> vars(dave)
     {'name': 'David D', '_age': 40}

     >>> mary.age                            # Access the data and log the lookup
     INFO:root:Accessing 'age' giving 30
     30
     >>> mary.birthday()                     # Updates are logged as well
     INFO:root:Accessing 'age' giving 30
     INFO:root:Updating 'age' to 31

     >>> dave.name                           # Regular attribute lookup isn't logged
     'David D'
     >>> dave.age                            # Only the managed attribute is logged
     INFO:root:Accessing 'age' giving 40
     40

One major issue with this example is that the private name '_age' is
hardwired in the 'LoggedAgeAccess' class.  That means that each instance
can only have one logged attribute and that its name is unchangeable.
In the next example, we'll fix that problem.


File: python.info,  Node: Customized names,  Next: Closing thoughts,  Prev: Managed attributes,  Up: Primer

9.3.1.4 Customized names
........................

When a class uses descriptors, it can inform each descriptor about which
variable name was used.

In this example, the ‘Person’ class has two descriptor instances, 'name'
and 'age'.  When the ‘Person’ class is defined, it makes a callback to
‘__set_name__()’ in 'LoggedAccess' so that the field names can be
recorded, giving each descriptor its own 'public_name' and
'private_name':

     import logging

     logging.basicConfig(level=logging.INFO)

     class LoggedAccess:

         def __set_name__(self, owner, name):
             self.public_name = name
             self.private_name = '_' + name

         def __get__(self, obj, objtype=None):
             value = getattr(obj, self.private_name)
             logging.info('Accessing %r giving %r', self.public_name, value)
             return value

         def __set__(self, obj, value):
             logging.info('Updating %r to %r', self.public_name, value)
             setattr(obj, self.private_name, value)

     class Person:

         name = LoggedAccess()                # First descriptor instance
         age = LoggedAccess()                 # Second descriptor instance

         def __init__(self, name, age):
             self.name = name                 # Calls the first descriptor
             self.age = age                   # Calls the second descriptor

         def birthday(self):
             self.age += 1

An interactive session shows that the ‘Person’ class has called
‘__set_name__()’ so that the field names would be recorded.  Here we
call *note vars(): 1948. to look up the descriptor without triggering
it:

     >>> vars(vars(Person)['name'])
     {'public_name': 'name', 'private_name': '_name'}
     >>> vars(vars(Person)['age'])
     {'public_name': 'age', 'private_name': '_age'}

The new class now logs access to both 'name' and 'age':

     >>> pete = Person('Peter P', 10)
     INFO:root:Updating 'name' to 'Peter P'
     INFO:root:Updating 'age' to 10
     >>> kate = Person('Catherine C', 20)
     INFO:root:Updating 'name' to 'Catherine C'
     INFO:root:Updating 'age' to 20

The two 'Person' instances contain only the private names:

     >>> vars(pete)
     {'_name': 'Peter P', '_age': 10}
     >>> vars(kate)
     {'_name': 'Catherine C', '_age': 20}


File: python.info,  Node: Closing thoughts,  Prev: Customized names,  Up: Primer

9.3.1.5 Closing thoughts
........................

A *note descriptor: 1e47. is what we call any object that defines
‘__get__()’, ‘__set__()’, or ‘__delete__()’.

Optionally, descriptors can have a ‘__set_name__()’ method.  This is
only used in cases where a descriptor needs to know either the class
where it was created or the name of class variable it was assigned to.
(This method, if present, is called even if the class is not a
descriptor.)

Descriptors get invoked by the dot operator during attribute lookup.  If
a descriptor is accessed indirectly with
‘vars(some_class)[descriptor_name]’, the descriptor instance is returned
without invoking it.

Descriptors only work when used as class variables.  When put in
instances, they have no effect.

The main motivation for descriptors is to provide a hook allowing
objects stored in class variables to control what happens during
attribute lookup.

Traditionally, the calling class controls what happens during lookup.
Descriptors invert that relationship and allow the data being looked-up
to have a say in the matter.

Descriptors are used throughout the language.  It is how functions turn
into bound methods.  Common tools like *note classmethod(): 14a, *note
staticmethod(): 358, *note property(): 180, and *note
functools.cached_property(): 4e7. are all implemented as descriptors.


File: python.info,  Node: Complete Practical Example,  Next: Technical Tutorial,  Prev: Primer,  Up: 描述器 Descriptor 指南

9.3.2 Complete Practical Example
--------------------------------

In this example, we create a practical and powerful tool for locating
notoriously hard to find data corruption bugs.

* Menu:

* Validator class::
* Custom validators::
* Practical application::


File: python.info,  Node: Validator class,  Next: Custom validators,  Up: Complete Practical Example

9.3.2.1 Validator class
.......................

A validator is a descriptor for managed attribute access.  Prior to
storing any data, it verifies that the new value meets various type and
range restrictions.  If those restrictions aren't met, it raises an
exception to prevent data corruption at its source.

This ‘Validator’ class is both an *note abstract base class: 114e. and a
managed attribute descriptor:

     from abc import ABC, abstractmethod

     class Validator(ABC):

         def __set_name__(self, owner, name):
             self.private_name = '_' + name

         def __get__(self, obj, objtype=None):
             return getattr(obj, self.private_name)

         def __set__(self, obj, value):
             self.validate(value)
             setattr(obj, self.private_name, value)

         @abstractmethod
         def validate(self, value):
             pass

Custom validators need to inherit from ‘Validator’ and must supply a
‘validate()’ method to test various restrictions as needed.


File: python.info,  Node: Custom validators,  Next: Practical application,  Prev: Validator class,  Up: Complete Practical Example

9.3.2.2 Custom validators
.........................

Here are three practical data validation utilities:

  1. ‘OneOf’ verifies that a value is one of a restricted set of
     options.

  2. ‘Number’ verifies that a value is either an *note int: 23c. or
     *note float: 2c8.  Optionally, it verifies that a value is between
     a given minimum or maximum.

  3. ‘String’ verifies that a value is a *note str: 3f2.  Optionally, it
     validates a given minimum or maximum length.  It can validate a
     user-defined predicate(1) as well.

     class OneOf(Validator):

         def __init__(self, *options):
             self.options = set(options)

         def validate(self, value):
             if value not in self.options:
                 raise ValueError(f'Expected {value!r} to be one of {self.options!r}')

     class Number(Validator):

         def __init__(self, minvalue=None, maxvalue=None):
             self.minvalue = minvalue
             self.maxvalue = maxvalue

         def validate(self, value):
             if not isinstance(value, (int, float)):
                 raise TypeError(f'Expected {value!r} to be an int or float')
             if self.minvalue is not None and value < self.minvalue:
                 raise ValueError(
                     f'Expected {value!r} to be at least {self.minvalue!r}'
                 )
             if self.maxvalue is not None and value > self.maxvalue:
                 raise ValueError(
                     f'Expected {value!r} to be no more than {self.maxvalue!r}'
                 )

     class String(Validator):

         def __init__(self, minsize=None, maxsize=None, predicate=None):
             self.minsize = minsize
             self.maxsize = maxsize
             self.predicate = predicate

         def validate(self, value):
             if not isinstance(value, str):
                 raise TypeError(f'Expected {value!r} to be an str')
             if self.minsize is not None and len(value) < self.minsize:
                 raise ValueError(
                     f'Expected {value!r} to be no smaller than {self.minsize!r}'
                 )
             if self.maxsize is not None and len(value) > self.maxsize:
                 raise ValueError(
                     f'Expected {value!r} to be no bigger than {self.maxsize!r}'
                 )
             if self.predicate is not None and not self.predicate(value):
                 raise ValueError(
                     f'Expected {self.predicate} to be true for {value!r}'
                 )

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Predicate_(mathematical_logic)


File: python.info,  Node: Practical application,  Prev: Custom validators,  Up: Complete Practical Example

9.3.2.3 Practical application
.............................

Here's how the data validators can be used in a real class:

     class Component:

         name = String(minsize=3, maxsize=10, predicate=str.isupper)
         kind = OneOf('wood', 'metal', 'plastic')
         quantity = Number(minvalue=0)

         def __init__(self, name, kind, quantity):
             self.name = name
             self.kind = kind
             self.quantity = quantity

The descriptors prevent invalid instances from being created:

     >>> Component('Widget', 'metal', 5)      # Blocked: 'Widget' is not all uppercase
     Traceback (most recent call last):
         ...
     ValueError: Expected <method 'isupper' of 'str' objects> to be true for 'Widget'

     >>> Component('WIDGET', 'metle', 5)      # Blocked: 'metle' is misspelled
     Traceback (most recent call last):
         ...
     ValueError: Expected 'metle' to be one of {'metal', 'plastic', 'wood'}

     >>> Component('WIDGET', 'metal', -5)     # Blocked: -5 is negative
     Traceback (most recent call last):
         ...
     ValueError: Expected -5 to be at least 0
     >>> Component('WIDGET', 'metal', 'V')    # Blocked: 'V' isn't a number
     Traceback (most recent call last):
         ...
     TypeError: Expected 'V' to be an int or float

     >>> c = Component('WIDGET', 'metal', 5)  # Allowed:  The inputs are valid


File: python.info,  Node: Technical Tutorial,  Next: Pure Python Equivalents,  Prev: Complete Practical Example,  Up: 描述器 Descriptor 指南

9.3.3 Technical Tutorial
------------------------

What follows is a more technical tutorial for the mechanics and details
of how descriptors work.

* Menu:

* 摘要::
* Definition and introduction::
* 描述器協定::
* Overview of descriptor invocation::
* Invocation from an instance::
* Invocation from a class::
* Invocation from super::
* Summary of invocation logic::
* Automatic name notification::
* ORM 範例::


File: python.info,  Node: 摘要,  Next: Definition and introduction,  Up: Technical Tutorial

9.3.3.1 摘要
............

Defines descriptors, summarizes the protocol, and shows how descriptors
are called.  Provides an example showing how object relational mappings
work.

Learning about descriptors not only provides access to a larger toolset,
it creates a deeper understanding of how Python works.


File: python.info,  Node: Definition and introduction,  Next: 描述器協定,  Prev: 摘要,  Up: Technical Tutorial

9.3.3.2 Definition and introduction
...................................

In general, a descriptor is an attribute value that has one of the
methods in the descriptor protocol.  Those methods are ‘__get__()’,
‘__set__()’, and ‘__delete__()’.  If any of those methods are defined
for an attribute, it is said to be a *note descriptor: 1e47.

The default behavior for attribute access is to get, set, or delete the
attribute from an object's dictionary.  For instance, ‘a.x’ has a lookup
chain starting with ‘a.__dict__['x']’, then ‘type(a).__dict__['x']’, and
continuing through the method resolution order of ‘type(a)’.  If the
looked-up value is an object defining one of the descriptor methods,
then Python may override the default behavior and invoke the descriptor
method instead.  Where this occurs in the precedence chain depends on
which descriptor methods were defined.

Descriptors are a powerful, general purpose protocol.  They are the
mechanism behind properties, methods, static methods, class methods, and
*note super(): 483.  They are used throughout Python itself.
Descriptors simplify the underlying C code and offer a flexible set of
new tools for everyday Python programs.


File: python.info,  Node: 描述器協定,  Next: Overview of descriptor invocation,  Prev: Definition and introduction,  Up: Technical Tutorial

9.3.3.3 描述器協定
..................

‘descr.__get__(self, obj, type=None)’

‘descr.__set__(self, obj, value)’

‘descr.__delete__(self, obj)’

That is all there is to it.  Define any of these methods and an object
is considered a descriptor and can override default behavior upon being
looked up as an attribute.

If an object defines ‘__set__()’ or ‘__delete__()’, it is considered a
data descriptor.  Descriptors that only define ‘__get__()’ are called
non-data descriptors (they are often used for methods but other uses are
possible).

Data and non-data descriptors differ in how overrides are calculated
with respect to entries in an instance's dictionary.  If an instance's
dictionary has an entry with the same name as a data descriptor, the
data descriptor takes precedence.  If an instance's dictionary has an
entry with the same name as a non-data descriptor, the dictionary entry
takes precedence.

To make a read-only data descriptor, define both ‘__get__()’ and
‘__set__()’ with the ‘__set__()’ raising an *note AttributeError: 2f6.
when called.  Defining the ‘__set__()’ method with an exception raising
placeholder is enough to make it a data descriptor.


File: python.info,  Node: Overview of descriptor invocation,  Next: Invocation from an instance,  Prev: 描述器協定,  Up: Technical Tutorial

9.3.3.4 Overview of descriptor invocation
.........................................

A descriptor can be called directly with ‘desc.__get__(obj)’ or
‘desc.__get__(None, cls)’.

But it is more common for a descriptor to be invoked automatically from
attribute access.

The expression ‘obj.x’ looks up the attribute ‘x’ in the chain of
namespaces for ‘obj’.  If the search finds a descriptor outside of the
instance ‘__dict__’, its ‘__get__()’ method is invoked according to the
precedence rules listed below.

The details of invocation depend on whether ‘obj’ is an object, class,
or instance of super.


File: python.info,  Node: Invocation from an instance,  Next: Invocation from a class,  Prev: Overview of descriptor invocation,  Up: Technical Tutorial

9.3.3.5 Invocation from an instance
...................................

Instance lookup scans through a chain of namespaces giving data
descriptors the highest priority, followed by instance variables, then
non-data descriptors, then class variables, and lastly ‘__getattr__()’
if it is provided.

If a descriptor is found for ‘a.x’, then it is invoked with:
‘desc.__get__(a, type(a))’.

The logic for a dotted lookup is in *note object.__getattribute__():
b79.  Here is a pure Python equivalent:

     def find_name_in_mro(cls, name, default):
         "Emulate _PyType_Lookup() in Objects/typeobject.c"
         for base in cls.__mro__:
             if name in vars(base):
                 return vars(base)[name]
         return default

     def object_getattribute(obj, name):
         "Emulate PyObject_GenericGetAttr() in Objects/object.c"
         null = object()
         objtype = type(obj)
         cls_var = find_name_in_mro(objtype, name, null)
         descr_get = getattr(type(cls_var), '__get__', null)
         if descr_get is not null:
             if (hasattr(type(cls_var), '__set__')
                 or hasattr(type(cls_var), '__delete__')):
                 return descr_get(cls_var, obj, objtype)     # data descriptor
         if hasattr(obj, '__dict__') and name in vars(obj):
             return vars(obj)[name]                          # instance variable
         if descr_get is not null:
             return descr_get(cls_var, obj, objtype)         # non-data descriptor
         if cls_var is not null:
             return cls_var                                  # class variable
         raise AttributeError(name)

Note, there is no ‘__getattr__()’ hook in the ‘__getattribute__()’ code.
That is why calling ‘__getattribute__()’ directly or with
‘super().__getattribute__’ will bypass ‘__getattr__()’ entirely.

Instead, it is the dot operator and the *note getattr(): b78. function
that are responsible for invoking ‘__getattr__()’ whenever
‘__getattribute__()’ raises an *note AttributeError: 2f6.  Their logic
is encapsulated in a helper function:

     def getattr_hook(obj, name):
         "Emulate slot_tp_getattr_hook() in Objects/typeobject.c"
         try:
             return obj.__getattribute__(name)
         except AttributeError:
             if not hasattr(type(obj), '__getattr__'):
                 raise
         return type(obj).__getattr__(obj, name)             # __getattr__


File: python.info,  Node: Invocation from a class,  Next: Invocation from super,  Prev: Invocation from an instance,  Up: Technical Tutorial

9.3.3.6 Invocation from a class
...............................

The logic for a dotted lookup such as ‘A.x’ is in
‘type.__getattribute__()’.  The steps are similar to those for *note
object.__getattribute__(): b79. but the instance dictionary lookup is
replaced by a search through the class's *note method resolution order:
205c.

If a descriptor is found, it is invoked with ‘desc.__get__(None, A)’.

The full C implementation can be found in ‘type_getattro()’ and
‘_PyType_Lookup()’ in Objects/typeobject.c(1).

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Objects/typeobject.c


File: python.info,  Node: Invocation from super,  Next: Summary of invocation logic,  Prev: Invocation from a class,  Up: Technical Tutorial

9.3.3.7 Invocation from super
.............................

The logic for super's dotted lookup is in the ‘__getattribute__()’
method for object returned by *note super(): 483.

A dotted lookup such as ‘super(A, obj).m’ searches
‘obj.__class__.__mro__’ for the base class ‘B’ immediately following ‘A’
and then returns ‘B.__dict__['m'].__get__(obj, A)’.  If not a
descriptor, ‘m’ is returned unchanged.

The full C implementation can be found in ‘super_getattro()’ in
Objects/typeobject.c(1).  A pure Python equivalent can be found in
Guido's Tutorial(2).

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Objects/typeobject.c

   (2) 
https://www.python.org/download/releases/2.2.3/descrintro/#cooperation


File: python.info,  Node: Summary of invocation logic,  Next: Automatic name notification,  Prev: Invocation from super,  Up: Technical Tutorial

9.3.3.8 Summary of invocation logic
...................................

The mechanism for descriptors is embedded in the ‘__getattribute__()’
methods for *note object: a2f, *note type: cef, and *note super(): 483.

要記住的重點是：

   * Descriptors are invoked by the ‘__getattribute__()’ method.

   * Classes inherit this machinery from *note object: a2f, *note type:
     cef, or *note super(): 483.

   * Overriding ‘__getattribute__()’ prevents automatic descriptor calls
     because all the descriptor logic is in that method.

   * *note object.__getattribute__(): b79. and ‘type.__getattribute__()’
     make different calls to ‘__get__()’.  The first includes the
     instance and may include the class.  The second puts in ‘None’ for
     the instance and always includes the class.

   * Data descriptors always override instance dictionaries.

   * Non-data descriptors may be overridden by instance dictionaries.


File: python.info,  Node: Automatic name notification,  Next: ORM 範例,  Prev: Summary of invocation logic,  Up: Technical Tutorial

9.3.3.9 Automatic name notification
...................................

Sometimes it is desirable for a descriptor to know what class variable
name it was assigned to.  When a new class is created, the *note type:
cef. metaclass scans the dictionary of the new class.  If any of the
entries are descriptors and if they define ‘__set_name__()’, that method
is called with two arguments.  The 'owner' is the class where the
descriptor is used, and the 'name' is the class variable the descriptor
was assigned to.

The implementation details are in ‘type_new()’ and ‘set_names()’ in
Objects/typeobject.c(1).

Since the update logic is in ‘type.__new__()’, notifications only take
place at the time of class creation.  If descriptors are added to the
class afterwards, ‘__set_name__()’ will need to be called manually.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Objects/typeobject.c


File: python.info,  Node: ORM 範例,  Prev: Automatic name notification,  Up: Technical Tutorial

9.3.3.10 ORM 範例
.................

The following code is a simplified skeleton showing how data descriptors
could be used to implement an object relational mapping(1).

The essential idea is that the data is stored in an external database.
The Python instances only hold keys to the database's tables.
Descriptors take care of lookups or updates:

     class Field:

         def __set_name__(self, owner, name):
             self.fetch = f'SELECT {name} FROM {owner.table} WHERE {owner.key}=?;'
             self.store = f'UPDATE {owner.table} SET {name}=? WHERE {owner.key}=?;'

         def __get__(self, obj, objtype=None):
             return conn.execute(self.fetch, [obj.key]).fetchone()[0]

         def __set__(self, obj, value):
             conn.execute(self.store, [value, obj.key])
             conn.commit()

We can use the ‘Field’ class to define models(2) that describe the
schema for each table in a database:

     class Movie:
         table = 'Movies'                    # Table name
         key = 'title'                       # Primary key
         director = Field()
         year = Field()

         def __init__(self, key):
             self.key = key

     class Song:
         table = 'Music'
         key = 'title'
         artist = Field()
         year = Field()
         genre = Field()

         def __init__(self, key):
             self.key = key

To use the models, first connect to the database:

     >>> import sqlite3
     >>> conn = sqlite3.connect('entertainment.db')

An interactive session shows how data is retrieved from the database and
how it can be updated:

     >>> Movie('Star Wars').director
     'George Lucas'
     >>> jaws = Movie('Jaws')
     >>> f'Released in {jaws.year} by {jaws.director}'
     'Released in 1975 by Steven Spielberg'

     >>> Song('Country Roads').artist
     'John Denver'

     >>> Movie('Star Wars').director = 'J.J. Abrams'
     >>> Movie('Star Wars').director
     'J.J. Abrams'

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Object%E2%80%93relational_mapping

   (2) https://en.wikipedia.org/wiki/Database_model


File: python.info,  Node: Pure Python Equivalents,  Prev: Technical Tutorial,  Up: 描述器 Descriptor 指南

9.3.4 Pure Python Equivalents
-----------------------------

The descriptor protocol is simple and offers exciting possibilities.
Several use cases are so common that they have been prepackaged into
built-in tools.  Properties, bound methods, static methods, class
methods, and __slots__ are all based on the descriptor protocol.

* Menu:

* Properties::
* Functions and methods::
* Kinds of methods::
* Static methods::
* Class methods::
* Member objects and __slots__::


File: python.info,  Node: Properties,  Next: Functions and methods,  Up: Pure Python Equivalents

9.3.4.1 Properties
..................

Calling *note property(): 180. is a succinct way of building a data
descriptor that triggers a function call upon access to an attribute.
Its signature is:

     property(fget=None, fset=None, fdel=None, doc=None) -> property

The documentation shows a typical use to define a managed attribute ‘x’:

     class C:
         def getx(self): return self.__x
         def setx(self, value): self.__x = value
         def delx(self): del self.__x
         x = property(getx, setx, delx, "I'm the 'x' property.")

To see how *note property(): 180. is implemented in terms of the
descriptor protocol, here is a pure Python equivalent that implements
most of the core functionality:

     class Property:
         "Emulate PyProperty_Type() in Objects/descrobject.c"

         def __init__(self, fget=None, fset=None, fdel=None, doc=None):
             self.fget = fget
             self.fset = fset
             self.fdel = fdel
             if doc is None and fget is not None:
                 doc = fget.__doc__
             self.__doc__ = doc
             self.__name__ = ''

         def __set_name__(self, owner, name):
             self.__name__ = name

         def __get__(self, obj, objtype=None):
             if obj is None:
                 return self
             if self.fget is None:
                 raise AttributeError
             return self.fget(obj)

         def __set__(self, obj, value):
             if self.fset is None:
                 raise AttributeError
             self.fset(obj, value)

         def __delete__(self, obj):
             if self.fdel is None:
                 raise AttributeError
             self.fdel(obj)

         def getter(self, fget):
             return type(self)(fget, self.fset, self.fdel, self.__doc__)

         def setter(self, fset):
             return type(self)(self.fget, fset, self.fdel, self.__doc__)

         def deleter(self, fdel):
             return type(self)(self.fget, self.fset, fdel, self.__doc__)

The *note property(): 180. builtin helps whenever a user interface has
granted attribute access and then subsequent changes require the
intervention of a method.

For instance, a spreadsheet class may grant access to a cell value
through ‘Cell('b10').value’.  Subsequent improvements to the program
require the cell to be recalculated on every access; however, the
programmer does not want to affect existing client code accessing the
attribute directly.  The solution is to wrap access to the value
attribute in a property data descriptor:

     class Cell:
         ...

         @property
         def value(self):
             "Recalculate the cell before returning value"
             self.recalc()
             return self._value

Either the built-in *note property(): 180. or our ‘Property()’
equivalent would work in this example.


File: python.info,  Node: Functions and methods,  Next: Kinds of methods,  Prev: Properties,  Up: Pure Python Equivalents

9.3.4.2 Functions and methods
.............................

Python's object oriented features are built upon a function based
environment.  Using non-data descriptors, the two are merged seamlessly.

Functions stored in class dictionaries get turned into methods when
invoked.  Methods only differ from regular functions in that the object
instance is prepended to the other arguments.  By convention, the
instance is called 'self' but could be called 'this' or any other
variable name.

Methods can be created manually with *note types.MethodType: 16fe. which
is roughly equivalent to:

     class MethodType:
         "Emulate PyMethod_Type in Objects/classobject.c"

         def __init__(self, func, obj):
             self.__func__ = func
             self.__self__ = obj

         def __call__(self, *args, **kwargs):
             func = self.__func__
             obj = self.__self__
             return func(obj, *args, **kwargs)

         def __getattribute__(self, name):
             "Emulate method_getset() in Objects/classobject.c"
             if name == '__doc__':
                 return self.__func__.__doc__
             return object.__getattribute__(self, name)

         def __getattr__(self, name):
             "Emulate method_getattro() in Objects/classobject.c"
             return getattr(self.__func__, name)

         def __get__(self, obj, objtype=None):
             "Emulate method_descr_get() in Objects/classobject.c"
             return self

To support automatic creation of methods, functions include the
‘__get__()’ method for binding methods during attribute access.  This
means that functions are non-data descriptors that return bound methods
during dotted lookup from an instance.  Here's how it works:

     class Function:
         ...

         def __get__(self, obj, objtype=None):
             "Simulate func_descr_get() in Objects/funcobject.c"
             if obj is None:
                 return self
             return MethodType(self, obj)

Running the following class in the interpreter shows how the function
descriptor works in practice:

     class D:
         def f(self):
              return self

     class D2:
         pass

The function has a *note qualified name: 1843. attribute to support
introspection:

     >>> D.f.__qualname__
     'D.f'

Accessing the function through the class dictionary does not invoke
‘__get__()’.  Instead, it just returns the underlying function object:

     >>> D.__dict__['f']
     <function D.f at 0x00C45070>

Dotted access from a class calls ‘__get__()’ which just returns the
underlying function unchanged:

     >>> D.f
     <function D.f at 0x00C45070>

The interesting behavior occurs during dotted access from an instance.
The dotted lookup calls ‘__get__()’ which returns a bound method object:

     >>> d = D()
     >>> d.f
     <bound method D.f of <__main__.D object at 0x00B18C90>>

Internally, the bound method stores the underlying function and the
bound instance:

     >>> d.f.__func__
     <function D.f at 0x00C45070>

     >>> d.f.__self__
     <__main__.D object at 0x00B18C90>

If you have ever wondered where 'self' comes from in regular methods or
where 'cls' comes from in class methods, this is it!


File: python.info,  Node: Kinds of methods,  Next: Static methods,  Prev: Functions and methods,  Up: Pure Python Equivalents

9.3.4.3 Kinds of methods
........................

Non-data descriptors provide a simple mechanism for variations on the
usual patterns of binding functions into methods.

To recap, functions have a ‘__get__()’ method so that they can be
converted to a method when accessed as attributes.  The non-data
descriptor transforms an ‘obj.f(*args)’ call into ‘f(obj, *args)’.
Calling ‘cls.f(*args)’ becomes ‘f(*args)’.

This chart summarizes the binding and its two most useful variants:

     Transformation        Called from an object      Called from a class
                                                      
     ------------------------------------------------------------------------
                                                      
     函式                  f(obj, *args)              f(*args)
                                                      
                                                      
     staticmethod          f(*args)                   f(*args)
                                                      
                                                      
     classmethod           f(type(obj), *args)        f(cls, *args)
                                                      


File: python.info,  Node: Static methods,  Next: Class methods,  Prev: Kinds of methods,  Up: Pure Python Equivalents

9.3.4.4 Static methods
......................

Static methods return the underlying function without changes.  Calling
either ‘c.f’ or ‘C.f’ is the equivalent of a direct lookup into
‘object.__getattribute__(c, "f")’ or ‘object.__getattribute__(C, "f")’.
As a result, the function becomes identically accessible from either an
object or a class.

Good candidates for static methods are methods that do not reference the
‘self’ variable.

For instance, a statistics package may include a container class for
experimental data.  The class provides normal methods for computing the
average, mean, median, and other descriptive statistics that depend on
the data.  However, there may be useful functions which are conceptually
related but do not depend on the data.  For instance, ‘erf(x)’ is handy
conversion routine that comes up in statistical work but does not
directly depend on a particular dataset.  It can be called either from
an object or the class: ‘s.erf(1.5) --> .9332’ or ‘Sample.erf(1.5) -->
.9332’.

Since static methods return the underlying function with no changes, the
example calls are unexciting:

     class E:
         @staticmethod
         def f(x):
             return x * 10

     >>> E.f(3)
     30
     >>> E().f(3)
     30

Using the non-data descriptor protocol, a pure Python version of *note
staticmethod(): 358. would look like this:

     import functools

     class StaticMethod:
         "Emulate PyStaticMethod_Type() in Objects/funcobject.c"

         def __init__(self, f):
             self.f = f
             functools.update_wrapper(self, f)

         def __get__(self, obj, objtype=None):
             return self.f

         def __call__(self, *args, **kwds):
             return self.f(*args, **kwds)

The *note functools.update_wrapper(): fc5. call adds a ‘__wrapped__’
attribute that refers to the underlying function.  Also it carries
forward the attributes necessary to make the wrapper look like the
wrapped function: *note __name__: 1267, *note __qualname__: 1deb, *note
__doc__: 1171, and *note __annotations__: 1170.


File: python.info,  Node: Class methods,  Next: Member objects and __slots__,  Prev: Static methods,  Up: Pure Python Equivalents

9.3.4.5 Class methods
.....................

Unlike static methods, class methods prepend the class reference to the
argument list before calling the function.  This format is the same for
whether the caller is an object or a class:

     class F:
         @classmethod
         def f(cls, x):
             return cls.__name__, x

     >>> F.f(3)
     ('F', 3)
     >>> F().f(3)
     ('F', 3)

This behavior is useful whenever the method only needs to have a class
reference and does not rely on data stored in a specific instance.  One
use for class methods is to create alternate class constructors.  For
example, the classmethod *note dict.fromkeys(): 211e. creates a new
dictionary from a list of keys.  The pure Python equivalent is:

     class Dict(dict):
         @classmethod
         def fromkeys(cls, iterable, value=None):
             "Emulate dict_fromkeys() in Objects/dictobject.c"
             d = cls()
             for key in iterable:
                 d[key] = value
             return d

Now a new dictionary of unique keys can be constructed like this:

     >>> d = Dict.fromkeys('abracadabra')
     >>> type(d) is Dict
     True
     >>> d
     {'a': None, 'b': None, 'r': None, 'c': None, 'd': None}

Using the non-data descriptor protocol, a pure Python version of *note
classmethod(): 14a. would look like this:

     import functools

     class ClassMethod:
         "Emulate PyClassMethod_Type() in Objects/funcobject.c"

         def __init__(self, f):
             self.f = f
             functools.update_wrapper(self, f)

         def __get__(self, obj, cls=None):
             if cls is None:
                 cls = type(obj)
             return MethodType(self.f, cls)

The *note functools.update_wrapper(): fc5. call in ‘ClassMethod’ adds a
‘__wrapped__’ attribute that refers to the underlying function.  Also it
carries forward the attributes necessary to make the wrapper look like
the wrapped function: *note __name__: 1267, *note __qualname__: 1deb,
*note __doc__: 1171, and *note __annotations__: 1170.


File: python.info,  Node: Member objects and __slots__,  Prev: Class methods,  Up: Pure Python Equivalents

9.3.4.6 Member objects and __slots__
....................................

When a class defines ‘__slots__’, it replaces instance dictionaries with
a fixed-length array of slot values.  From a user point of view that has
several effects:

1.  Provides immediate detection of bugs due to misspelled attribute
assignments.  Only attribute names specified in ‘__slots__’ are allowed:

     class Vehicle:
         __slots__ = ('id_number', 'make', 'model')

     >>> auto = Vehicle()
     >>> auto.id_nubmer = 'VYE483814LQEX'
     Traceback (most recent call last):
         ...
     AttributeError: 'Vehicle' object has no attribute 'id_nubmer'

2.  Helps create immutable objects where descriptors manage access to
private attributes stored in ‘__slots__’:

     class Immutable:

         __slots__ = ('_dept', '_name')          # Replace the instance dictionary

         def __init__(self, dept, name):
             self._dept = dept                   # Store to private attribute
             self._name = name                   # Store to private attribute

         @property                               # Read-only descriptor
         def dept(self):
             return self._dept

         @property
         def name(self):                         # Read-only descriptor
             return self._name

     >>> mark = Immutable('Botany', 'Mark Watney')
     >>> mark.dept
     'Botany'
     >>> mark.dept = 'Space Pirate'
     Traceback (most recent call last):
         ...
     AttributeError: property 'dept' of 'Immutable' object has no setter
     >>> mark.location = 'Mars'
     Traceback (most recent call last):
         ...
     AttributeError: 'Immutable' object has no attribute 'location'

3.  Saves memory.  On a 64-bit Linux build, an instance with two
attributes takes 48 bytes with ‘__slots__’ and 152 bytes without.  This
flyweight design pattern(1) likely only matters when a large number of
instances are going to be created.

4.  Improves speed.  Reading instance variables is 35% faster with
‘__slots__’ (as measured with Python 3.10 on an Apple M1 processor).

5.  Blocks tools like *note functools.cached_property(): 4e7. which
require an instance dictionary to function correctly:

     from functools import cached_property

     class CP:
         __slots__ = ()                          # Eliminates the instance dict

         @cached_property                        # Requires an instance dict
         def pi(self):
             return 4 * sum((-1.0)**n / (2.0*n + 1.0)
                            for n in reversed(range(100_000)))

     >>> CP().pi
     Traceback (most recent call last):
       ...
     TypeError: No '__dict__' attribute on 'CP' instance to cache 'pi' property.

It is not possible to create an exact drop-in pure Python version of
‘__slots__’ because it requires direct access to C structures and
control over object memory allocation.  However, we can build a mostly
faithful simulation where the actual C structure for slots is emulated
by a private ‘_slotvalues’ list.  Reads and writes to that private
structure are managed by member descriptors:

     null = object()

     class Member:

         def __init__(self, name, clsname, offset):
             'Emulate PyMemberDef in Include/structmember.h'
             # Also see descr_new() in Objects/descrobject.c
             self.name = name
             self.clsname = clsname
             self.offset = offset

         def __get__(self, obj, objtype=None):
             'Emulate member_get() in Objects/descrobject.c'
             # Also see PyMember_GetOne() in Python/structmember.c
             if obj is None:
                 return self
             value = obj._slotvalues[self.offset]
             if value is null:
                 raise AttributeError(self.name)
             return value

         def __set__(self, obj, value):
             'Emulate member_set() in Objects/descrobject.c'
             obj._slotvalues[self.offset] = value

         def __delete__(self, obj):
             'Emulate member_delete() in Objects/descrobject.c'
             value = obj._slotvalues[self.offset]
             if value is null:
                 raise AttributeError(self.name)
             obj._slotvalues[self.offset] = null

         def __repr__(self):
             'Emulate member_repr() in Objects/descrobject.c'
             return f'<Member {self.name!r} of {self.clsname!r}>'

The ‘type.__new__()’ method takes care of adding member objects to class
variables:

     class Type(type):
         'Simulate how the type metaclass adds member objects for slots'

         def __new__(mcls, clsname, bases, mapping, **kwargs):
             'Emulate type_new() in Objects/typeobject.c'
             # type_new() calls PyTypeReady() which calls add_methods()
             slot_names = mapping.get('slot_names', [])
             for offset, name in enumerate(slot_names):
                 mapping[name] = Member(name, clsname, offset)
             return type.__new__(mcls, clsname, bases, mapping, **kwargs)

The *note object.__new__(): 526. method takes care of creating instances
that have slots instead of an instance dictionary.  Here is a rough
simulation in pure Python:

     class Object:
         'Simulate how object.__new__() allocates memory for __slots__'

         def __new__(cls, *args, **kwargs):
             'Emulate object_new() in Objects/typeobject.c'
             inst = super().__new__(cls)
             if hasattr(cls, 'slot_names'):
                 empty_slots = [null] * len(cls.slot_names)
                 object.__setattr__(inst, '_slotvalues', empty_slots)
             return inst

         def __setattr__(self, name, value):
             'Emulate _PyObject_GenericSetAttrWithDict() Objects/object.c'
             cls = type(self)
             if hasattr(cls, 'slot_names') and name not in cls.slot_names:
                 raise AttributeError(
                     f'{cls.__name__!r} object has no attribute {name!r}'
                 )
             super().__setattr__(name, value)

         def __delattr__(self, name):
             'Emulate _PyObject_GenericSetAttrWithDict() Objects/object.c'
             cls = type(self)
             if hasattr(cls, 'slot_names') and name not in cls.slot_names:
                 raise AttributeError(
                     f'{cls.__name__!r} object has no attribute {name!r}'
                 )
             super().__delattr__(name)

To use the simulation in a real class, just inherit from ‘Object’ and
set the *note metaclass: 1e5d. to ‘Type’:

     class H(Object, metaclass=Type):
         'Instance variables stored in slots'

         slot_names = ['x', 'y']

         def __init__(self, x, y):
             self.x = x
             self.y = y

At this point, the metaclass has loaded member objects for 'x' and 'y':

     >>> from pprint import pp
     >>> pp(dict(vars(H)))
     {'__module__': '__main__',
      '__doc__': 'Instance variables stored in slots',
      'slot_names': ['x', 'y'],
      '__init__': <function H.__init__ at 0x7fb5d302f9d0>,
      'x': <Member 'x' of 'H'>,
      'y': <Member 'y' of 'H'>}

When instances are created, they have a ‘slot_values’ list where the
attributes are stored:

     >>> h = H(10, 20)
     >>> vars(h)
     {'_slotvalues': [10, 20]}
     >>> h.x = 55
     >>> vars(h)
     {'_slotvalues': [55, 20]}

Misspelled or unassigned attributes will raise an exception:

     >>> h.xz
     Traceback (most recent call last):
         ...
     AttributeError: 'H' object has no attribute 'xz'

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Flyweight_pattern


File: python.info,  Node: 使用 GDB 來為 C API 擴充功能和 CPython 內部偵錯,  Next: Enum HOWTO,  Prev: 描述器 Descriptor 指南,  Up: Python 如何達成任務

9.4 使用 GDB 來為 C API 擴充功能和 CPython 內部偵錯
===================================================

本文件解釋如何將 Python GDB 擴充功能 ‘python-gdb.py’ 與 GDB 偵錯器一起使
用來為 CPython 擴充功能和 CPython 直譯器本身偵錯。

在為崩潰或死鎖等低階問題幀錯時，低階偵錯器（例如 GDB）對於診斷和修正問題
非常有用。預設情況下，GDB（或其任何前端）不支援特定於 CPython 直譯器的高
階資訊。

‘python-gdb.py’ 擴充功能將 CPython 直譯器資訊新增至 GDB。此擴充有助於內
省 (introspect) 目前執行的 Python 函式的堆疊。給定一個由 *note PyObject:
311.* 指標表示的 Python 物件，擴充功能會顯示該物件的型別和值。

正在開發 CPython 擴充功能或修補用 C 編寫之 CPython 部分的開發人員可以使
用本文件來學習如何將 ‘python-gdb.py’ 擴充功能與 GDB 一起使用。

     備註: 本文件假設你熟悉 GDB 和 CPython C API 的基礎知識。它整合了
     devguide(1) 和 Python wiki(2) 的指引。

* Menu:

* 先決條件::
* 使用偵錯建置與使用開發模式::
* 使用 python-gdb 擴充功能::
* 與 GDB 指令一起使用::

   ---------- Footnotes ----------

   (1) https://devguide.python.org

   (2) https://wiki.python.org/moin/DebuggingWithGdb


File: python.info,  Node: 先決條件,  Next: 使用偵錯建置與使用開發模式,  Up: 使用 GDB 來為 C API 擴充功能和 CPython 內部偵錯

9.4.1 先決條件
--------------

你需要有：

   - GDB 7 或更之後的版本。（對於早期版本的 GDB，請參閱 Python 3.11 或更
     早版本的原始程式碼中的 ‘Misc/gdbinit’。）

   - 對 Python 和你在偵錯的任何擴充功能來說的與 GDB 相容的偵錯資訊。

   - ‘python-gdb.py’ 擴充。

該擴充功能是用 Python 建置的，但可能會單獨發布或根本不發布。以下我們將一
些常見系統的提示作為範例。請注意，即使說明與你的系統匹配，它們也可能已過
時。

* Menu:

* 使用從原始碼建置的 Python 進行設定::
* 從 Linux 發行版設定 Python::


File: python.info,  Node: 使用從原始碼建置的 Python 進行設定,  Next: 從 Linux 發行版設定 Python,  Up: 先決條件

9.4.1.1 使用從原始碼建置的 Python 進行設定
..........................................

當你從原始程式碼建立 CPython 時，偵錯資訊應該可用，並且建置應該將
‘python-gdb.py’ 檔案新增至儲存庫的根目錄中。

若要啟用支援，你必須將包含 ‘python-gdb.py’ 的目錄新增至 GDB 的
"auto-load-safe-path"。如果你還沒有這樣做，最新版本的 GDB 將列印警告，其
中包含有關如何執行此操作的說明。

     備註: 如果你沒有看到適合你的 GDB 版本的說明，請將其放入你的設定檔中
     （‘~/.gdbinit’ 或 ‘~/.config/gdb/gdbinit’）：

          add-auto-load-safe-path /path/to/cpython

     你也可以新增多個路徑，要以 ‘:’ 分隔。


File: python.info,  Node: 從 Linux 發行版設定 Python,  Prev: 使用從原始碼建置的 Python 進行設定,  Up: 先決條件

9.4.1.2 從 Linux 發行版設定 Python
..................................

大多數 Linux 系統在名為 ‘python-debuginfo’、‘python-dbg’ 或類似的套件中
提供系統 Python 的偵錯資訊。例如：

   - Fedora：

               sudo dnf install gdb
               sudo dnf debuginfo-install python3

   - Ubuntu：

               sudo apt install gdb python3-dbg

在最近的幾個 Linux 系統上，GDB 可以使用 'debuginfod' 自動下載偵錯符號。
但是這不會安裝 ‘python-gdb.py’ 擴充功能；你通常需要另外安裝偵錯資訊套件
。


File: python.info,  Node: 使用偵錯建置與使用開發模式,  Next: 使用 python-gdb 擴充功能,  Prev: 先決條件,  Up: 使用 GDB 來為 C API 擴充功能和 CPython 內部偵錯

9.4.2 使用偵錯建置與使用開發模式
--------------------------------

為了更輕鬆地進行偵錯，你可能需要：

   - 使用 Python 的*note 偵錯建置: 1de.。（從原始碼建置時，請使用
     ‘configure --with-pydebug’。在 Linux 發行版上，安裝並執行諸如
     ‘python-debug’ 或 ‘python-dbg’ 之類的套件（如果可用））。

   - 使用 runtime *note 開發模式: 1dd. (‘-X dev’)。

兩者都啟用額外的斷言 (assertion) 並停用一些最佳化。有時這會隱藏你試圖想
尋找的錯誤，但在大多數情況下，它們會使過程變得更容易。


File: python.info,  Node: 使用 python-gdb 擴充功能,  Next: 與 GDB 指令一起使用,  Prev: 使用偵錯建置與使用開發模式,  Up: 使用 GDB 來為 C API 擴充功能和 CPython 內部偵錯

9.4.3 使用 ‘python-gdb’ 擴充功能
--------------------------------

載入擴充功能後，它提供兩個主要功能：Python 值的漂亮列印器和附加命令。

* Menu:

* 漂亮列印器::
* py-list::
* py-up 和 py-down::
* py-bt::
* py-print::
* py-locals::


File: python.info,  Node: 漂亮列印器,  Next: py-list,  Up: 使用 python-gdb 擴充功能

9.4.3.1 漂亮列印器
..................

這是啟用此擴充功能時 GDB 回溯 (backtrace) 的樣子（有被截斷）：

     #0  0x000000000041a6b1 in PyObject_Malloc (nbytes=Cannot access memory at address 0x7fffff7fefe8
     ) at Objects/obmalloc.c:748
     #1  0x000000000041b7c0 in _PyObject_DebugMallocApi (id=111 'o', nbytes=24) at Objects/obmalloc.c:1445
     #2  0x000000000041b717 in _PyObject_DebugMalloc (nbytes=24) at Objects/obmalloc.c:1412
     #3  0x000000000044060a in _PyUnicode_New (length=11) at Objects/unicodeobject.c:346
     #4  0x00000000004466aa in PyUnicodeUCS2_DecodeUTF8Stateful (s=0x5c2b8d "__lltrace__", size=11, errors=0x0, consumed=
         0x0) at Objects/unicodeobject.c:2531
     #5  0x0000000000446647 in PyUnicodeUCS2_DecodeUTF8 (s=0x5c2b8d "__lltrace__", size=11, errors=0x0)
         at Objects/unicodeobject.c:2495
     #6  0x0000000000440d1b in PyUnicodeUCS2_FromStringAndSize (u=0x5c2b8d "__lltrace__", size=11)
         at Objects/unicodeobject.c:551
     #7  0x0000000000440d94 in PyUnicodeUCS2_FromString (u=0x5c2b8d "__lltrace__") at Objects/unicodeobject.c:569
     #8  0x0000000000584abd in PyDict_GetItemString (v=
         {'Yuck': <type at remote 0xad4730>, '__builtins__': <module at remote 0x7ffff7fd5ee8>, '__file__': 'Lib/test/crashers/nasty_eq_vs_dict.py', '__package__': None, 'y': <Yuck(i=0) at remote 0xaacd80>, 'dict': {0: 0, 1: 1, 2: 2, 3: 3}, '__cached__': None, '__name__': '__main__', 'z': <Yuck(i=0) at remote 0xaace60>, '__doc__': None}, key=
         0x5c2b8d "__lltrace__") at Objects/dictobject.c:2171

請注意 ‘PyDict_GetItemString’ 的字典引數如何顯示為其 ‘repr()’，而不是不
透明的 ‘PyObject *’ 指標。

該擴充功能透過為 ‘PyObject *’ 型別的值提供自訂列印例程來運作。如果需要存
取物件較低階的詳細資訊，請將值轉換為適當型別的指標。例如：

     (gdb) p globals
     $1 = {'__builtins__': <module at remote 0x7ffff7fb1868>, '__name__':
     '__main__', 'ctypes': <module at remote 0x7ffff7f14360>, '__doc__': None,
     '__package__': None}

     (gdb) p *(PyDictObject*)globals
     $2 = {ob_refcnt = 3, ob_type = 0x3dbdf85820, ma_fill = 5, ma_used = 5,
     ma_mask = 7, ma_table = 0x63d0f8, ma_lookup = 0x3dbdc7ea70
     <lookdict_string>, ma_smalltable = {{me_hash = 7065186196740147912,
     me_key = '__builtins__', me_value = <module at remote 0x7ffff7fb1868>},
     {me_hash = -368181376027291943, me_key = '__name__',
     me_value ='__main__'}, {me_hash = 0, me_key = 0x0, me_value = 0x0},
     {me_hash = 0, me_key = 0x0, me_value = 0x0},
     {me_hash = -9177857982131165996, me_key = 'ctypes',
     me_value = <module at remote 0x7ffff7f14360>},
     {me_hash = -8518757509529533123, me_key = '__doc__', me_value = None},
     {me_hash = 0, me_key = 0x0, me_value = 0x0}, {
       me_hash = 6614918939584953775, me_key = '__package__', me_value = None}}}

請注意，漂亮列印器其實並不呼叫 ‘repr()’。對於基本型別，他們嘗試緊密匹配
其結果。

一個可能令人困惑的地方是，某些型別的自訂列印器看起來很像 GDB 標準類型的
內建列印器。例如，Python ‘int’ (*note PyLongObject: 52e.*) 的漂亮列印器
給出的表示法無法與常規機器層級整數之其一區分：

     (gdb) p some_machine_integer
     $3 = 42

     (gdb) p some_python_integer
     $4 = 42

可以透過轉換 (cast) 為 *note PyLongObject: 52e.* 來揭示內部結構：

     (gdb) p '(PyLongObject')some_python_integer $5 = {ob_base =
     {ob_base = {ob_refcnt = 8, ob_type = 0x3dad39f5e0}, ob_size = 1},
     ob_digit = {42}}

使用 ‘str’ 型別時也可能會出現類似的困惑，其中的輸出看起來很像對於 ‘char
*’ 的 gdb 內建列印器 ：

     (gdb) p ptr_to_python_str
     $6 = '__builtins__'

‘str’ 實例的漂亮列印器預設使用單引號（Python 的 ‘repr’ 對於字串也是如此
），而 ‘char *’ 值的標準列印器使用雙引號並包含十六進位位址：

     (gdb) p ptr_to_char_star
     $7 = 0x6d72c0 "hello world"

同樣，可以透過轉換為 *note PyUnicodeObject: 738.* 來揭示實作細節：

     (gdb) p *(PyUnicodeObject*)$6
     $8 = {ob_base = {ob_refcnt = 33, ob_type = 0x3dad3a95a0}, length = 12,
     str = 0x7ffff2128500, hash = 7065186196740147912, state = 1, defenc = 0x0}


File: python.info,  Node: py-list,  Next: py-up 和 py-down,  Prev: 漂亮列印器,  Up: 使用 python-gdb 擴充功能

9.4.3.2 ‘py-list’
.................

     該擴充功能新增了一個 ‘py-list’ 命令，該命令列出了所選執行緒中當前
     frame 的 Python 原始程式碼（如果有）。當前的列會標有 ">"：

          (gdb) py-list
           901        if options.profile:
           902            options.profile = False
           903            profile_me()
           904            return
           905
          >906        u = UI()
           907        if not u.quit:
           908            try:
           909                gtk.main()
           910            except KeyboardInterrupt:
           911                # properly quit on a keyboard interrupt...

     使用 ‘py-list START’ 列出 Python 原始碼中不同的列號，使用 ‘py-list
     START,END’ 列出 Python 原始碼中特定範圍的列。


File: python.info,  Node: py-up 和 py-down,  Next: py-bt,  Prev: py-list,  Up: 使用 python-gdb 擴充功能

9.4.3.3 ‘py-up’ 和 ‘py-down’
............................

     ‘py-up’ 和 ‘py-down’ 命令類似於 GDB 的常規 ‘up’ 和 ‘down’ 命令，但
     嘗試在 CPython frame 層級移動，而不是 C frame。

     GDB 並不總是能夠讀取相關的 frame 資訊，這取決於編譯 CPython 的最佳
     化等級。在內部，這些指令會尋找正在執行預設 frame 計算 (evaluation)
     函式（即 CPython 中迴圈的核心位元組碼直譯器）的 C frame，並尋找相關
     ‘PyFrameObject *’ 的值。

     它們在執行緒內發出（於 C 層級的）frame 編號。

     例如：

          (gdb) py-up
          #37 Frame 0x9420b04, for file /usr/lib/python2.6/site-packages/
          gnome_sudoku/main.py, line 906, in start_game ()
              u = UI()
          (gdb) py-up
          #40 Frame 0x948e82c, for file /usr/lib/python2.6/site-packages/
          gnome_sudoku/gnome_sudoku.py, line 22, in start_game(main=<module at remote 0xb771b7f4>)
              main.start_game()
          (gdb) py-up
          Unable to find an older python frame

     所以現在我們處於 Python 堆疊的頂端。

     frame 編號與 GDB 標準 ‘backtrace’ 指令顯示的 frame 編號相對應。此指
     令會跳過不執行 Python 程式碼的 C frame。

     回到下面：

          (gdb) py-down
          #37 Frame 0x9420b04, for file /usr/lib/python2.6/site-packages/gnome_sudoku/main.py, line 906, in start_game ()
              u = UI()
          (gdb) py-down
          #34 (unable to read python frame information)
          (gdb) py-down
          #23 (unable to read python frame information)
          (gdb) py-down
          #19 (unable to read python frame information)
          (gdb) py-down
          #14 Frame 0x99262ac, for file /usr/lib/python2.6/site-packages/gnome_sudoku/game_selector.py, line 201, in run_swallowed_dialog (self=<NewOrSavedGameSelector(new_game_model=<gtk.ListStore at remote 0x98fab44>, puzzle=None, saved_games=[{'gsd.auto_fills': 0, 'tracking': {}, 'trackers': {}, 'notes': [], 'saved_at': 1270084485, 'game': '7 8 0 0 0 0 0 5 6 0 0 9 0 8 0 1 0 0 0 4 6 0 0 0 0 7 0 6 5 0 0 0 4 7 9 2 0 0 0 9 0 1 0 0 0 3 9 7 6 0 0 0 1 8 0 6 0 0 0 0 2 8 0 0 0 5 0 4 0 6 0 0 2 1 0 0 0 0 0 4 5\n7 8 0 0 0 0 0 5 6 0 0 9 0 8 0 1 0 0 0 4 6 0 0 0 0 7 0 6 5 1 8 3 4 7 9 2 0 0 0 9 0 1 0 0 0 3 9 7 6 0 0 0 1 8 0 6 0 0 0 0 2 8 0 0 0 5 0 4 0 6 0 0 2 1 0 0 0 0 0 4 5', 'gsd.impossible_hints': 0, 'timer.__absolute_start_time__': <float at remote 0x984b474>, 'gsd.hints': 0, 'timer.active_time': <float at remote 0x984b494>, 'timer.total_time': <float at remote 0x984b464>}], dialog=<gtk.Dialog at remote 0x98faaa4>, saved_game_model=<gtk.ListStore at remote 0x98fad24>, sudoku_maker=<SudokuMaker(terminated=False, played=[], batch_siz...(truncated)
                      swallower.run_dialog(self.dialog)
          (gdb) py-down
          #11 Frame 0x9aead74, for file /usr/lib/python2.6/site-packages/gnome_sudoku/dialog_swallower.py, line 48, in run_dialog (self=<SwappableArea(running=<gtk.Dialog at remote 0x98faaa4>, main_page=0) at remote 0x98fa6e4>, d=<gtk.Dialog at remote 0x98faaa4>)
                      gtk.main()
          (gdb) py-down
          #8 (unable to read python frame information)
          (gdb) py-down
          Unable to find a newer python frame

     我們現在處於 Python 堆疊的底部。

     請注意，在 Python 3.12 及更高版本中，同一個 C 堆疊 frame 可用於多個
     Python 堆疊 frame。這意味著 ‘py-up’ 和 ‘py-down’ 可以一次移動多個
     Python frame。例如：

          (gdb) py-up
          #6 Frame 0x7ffff7fb62b0, for file /tmp/rec.py, line 5, in recursive_function (n=0)
             time.sleep(5)
          #6 Frame 0x7ffff7fb6240, for file /tmp/rec.py, line 7, in recursive_function (n=1)
             recursive_function(n-1)
          #6 Frame 0x7ffff7fb61d0, for file /tmp/rec.py, line 7, in recursive_function (n=2)
             recursive_function(n-1)
          #6 Frame 0x7ffff7fb6160, for file /tmp/rec.py, line 7, in recursive_function (n=3)
             recursive_function(n-1)
          #6 Frame 0x7ffff7fb60f0, for file /tmp/rec.py, line 7, in recursive_function (n=4)
             recursive_function(n-1)
          #6 Frame 0x7ffff7fb6080, for file /tmp/rec.py, line 7, in recursive_function (n=5)
             recursive_function(n-1)
          #6 Frame 0x7ffff7fb6020, for file /tmp/rec.py, line 9, in <module> ()
             recursive_function(5)
          (gdb) py-up
          Unable to find an older python frame


File: python.info,  Node: py-bt,  Next: py-print,  Prev: py-up 和 py-down,  Up: 使用 python-gdb 擴充功能

9.4.3.4 ‘py-bt’
...............

     ‘py-bt’ 指令嘗試顯示目前執行緒的 Python 層級回溯。

     例如：

          (gdb) py-bt
          #8 (unable to read python frame information)
          #11 Frame 0x9aead74, for file /usr/lib/python2.6/site-packages/gnome_sudoku/dialog_swallower.py, line 48, in run_dialog (self=<SwappableArea(running=<gtk.Dialog at remote 0x98faaa4>, main_page=0) at remote 0x98fa6e4>, d=<gtk.Dialog at remote 0x98faaa4>)
                      gtk.main()
          #14 Frame 0x99262ac, for file /usr/lib/python2.6/site-packages/gnome_sudoku/game_selector.py, line 201, in run_swallowed_dialog (self=<NewOrSavedGameSelector(new_game_model=<gtk.ListStore at remote 0x98fab44>, puzzle=None, saved_games=[{'gsd.auto_fills': 0, 'tracking': {}, 'trackers': {}, 'notes': [], 'saved_at': 1270084485, 'game': '7 8 0 0 0 0 0 5 6 0 0 9 0 8 0 1 0 0 0 4 6 0 0 0 0 7 0 6 5 0 0 0 4 7 9 2 0 0 0 9 0 1 0 0 0 3 9 7 6 0 0 0 1 8 0 6 0 0 0 0 2 8 0 0 0 5 0 4 0 6 0 0 2 1 0 0 0 0 0 4 5\n7 8 0 0 0 0 0 5 6 0 0 9 0 8 0 1 0 0 0 4 6 0 0 0 0 7 0 6 5 1 8 3 4 7 9 2 0 0 0 9 0 1 0 0 0 3 9 7 6 0 0 0 1 8 0 6 0 0 0 0 2 8 0 0 0 5 0 4 0 6 0 0 2 1 0 0 0 0 0 4 5', 'gsd.impossible_hints': 0, 'timer.__absolute_start_time__': <float at remote 0x984b474>, 'gsd.hints': 0, 'timer.active_time': <float at remote 0x984b494>, 'timer.total_time': <float at remote 0x984b464>}], dialog=<gtk.Dialog at remote 0x98faaa4>, saved_game_model=<gtk.ListStore at remote 0x98fad24>, sudoku_maker=<SudokuMaker(terminated=False, played=[], batch_siz...(truncated)
                      swallower.run_dialog(self.dialog)
          #19 (unable to read python frame information)
          #23 (unable to read python frame information)
          #34 (unable to read python frame information)
          #37 Frame 0x9420b04, for file /usr/lib/python2.6/site-packages/gnome_sudoku/main.py, line 906, in start_game ()
              u = UI()
          #40 Frame 0x948e82c, for file /usr/lib/python2.6/site-packages/gnome_sudoku/gnome_sudoku.py, line 22, in start_game (main=<module at remote 0xb771b7f4>)
              main.start_game()

     The frame numbers correspond to those displayed by GDB's standard
     ‘backtrace’ command.


File: python.info,  Node: py-print,  Next: py-locals,  Prev: py-bt,  Up: 使用 python-gdb 擴充功能

9.4.3.5 ‘py-print’
..................

     ‘py-print’ 命令查找 Python 名稱並嘗試列印它。它在當前執行緒中尋找局
     部變數，然後是全域變數，最後是內建變數：

          (gdb) py-print self
          local 'self' = <SwappableArea(running=<gtk.Dialog at remote 0x98faaa4>,
          main_page=0) at remote 0x98fa6e4>
          (gdb) py-print __name__
          global '__name__' = 'gnome_sudoku.dialog_swallower'
          (gdb) py-print len
          builtin 'len' = <built-in function len>
          (gdb) py-print scarlet_pimpernel
          'scarlet_pimpernel' not found

     如果目前 C frame 對應多個 Python frame，則 ‘py-print’ 僅考慮第一個
     。


File: python.info,  Node: py-locals,  Prev: py-print,  Up: 使用 python-gdb 擴充功能

9.4.3.6 ‘py-locals’
...................

     ‘py-locals’ 命令尋找所選執行緒中當前 Python frame 內的所有 Python 局
     部變數，並列印它們的表示：

          (gdb) py-locals
          self = <SwappableArea(running=<gtk.Dialog at remote 0x98faaa4>,
          main_page=0) at remote 0x98fa6e4>
          d = <gtk.Dialog at remote 0x98faaa4>

     如果目前 C frame 對應於多個 Python frame，則會顯示所有這些 frame 的
     局部變數：

          (gdb) py-locals
          Locals for recursive_function
          n = 0
          Locals for recursive_function
          n = 1
          Locals for recursive_function
          n = 2
          Locals for recursive_function
          n = 3
          Locals for recursive_function
          n = 4
          Locals for recursive_function
          n = 5
          Locals for <module>


File: python.info,  Node: 與 GDB 指令一起使用,  Prev: 使用 python-gdb 擴充功能,  Up: 使用 GDB 來為 C API 擴充功能和 CPython 內部偵錯

9.4.4 與 GDB 指令一起使用
-------------------------

擴充命令補充了 GDB 的內建命令。例如，你可以將 ‘py-bt’ 顯示的 frame 編號
與 ‘frame’ 命令一同使用來跳到所選執行緒中的特定 frame，如下所示：

     (gdb) py-bt
     (output snipped)
     #68 Frame 0xaa4560, for file Lib/test/regrtest.py, line 1548, in <module> ()
             main()
     (gdb) frame 68
     #68 0x00000000004cd1e6 in PyEval_EvalFrameEx (f=Frame 0xaa4560, for file Lib/test/regrtest.py, line 1548, in <module> (), throwflag=0) at Python/ceval.c:2665
     2665                            x = call_function(&sp, oparg);
     (gdb) py-list
     1543        # Run the tests in a context manager that temporary changes the CWD to a
     1544        # temporary and writable directory. If it's not possible to create or
     1545        # change the CWD, the original CWD will be used. The original CWD is
     1546        # available from test_support.SAVEDCWD.
     1547        with test_support.temp_cwd(TESTCWD, quiet=True):
     >1548            main()

‘info threads’ 命令將為你提供行程內的執行緒串列，你可以使用 ‘thread’ 命
令選擇不同的執行緒：

     (gdb) info threads
       105 Thread 0x7fffefa18710 (LWP 10260)  sem_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S:86
       104 Thread 0x7fffdf5fe710 (LWP 10259)  sem_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S:86
     * 1 Thread 0x7ffff7fe2700 (LWP 10145)  0x00000038e46d73e3 in select () at ../sysdeps/unix/syscall-template.S:82

你可以使用 ‘thread apply all COMMAND’（或簡短地用 ‘t a a COMMAND’）在所
有執行緒上執行命令。使用 ‘py-bt’ 你可以看到每個執行緒在 Python 層級正在
做什麼：

     (gdb) t a a py-bt

     Thread 105 (Thread 0x7fffefa18710 (LWP 10260)):
     #5 Frame 0x7fffd00019d0, for file /home/david/coding/python-svn/Lib/threading.py, line 155, in _acquire_restore (self=<_RLock(_Verbose__verbose=False, _RLock__owner=140737354016512, _RLock__block=<thread.lock at remote 0x858770>, _RLock__count=1) at remote 0xd7ff40>, count_owner=(1, 140737213728528), count=1, owner=140737213728528)
             self.__block.acquire()
     #8 Frame 0x7fffac001640, for file /home/david/coding/python-svn/Lib/threading.py, line 269, in wait (self=<_Condition(_Condition__lock=<_RLock(_Verbose__verbose=False, _RLock__owner=140737354016512, _RLock__block=<thread.lock at remote 0x858770>, _RLock__count=1) at remote 0xd7ff40>, acquire=<instancemethod at remote 0xd80260>, _is_owned=<instancemethod at remote 0xd80160>, _release_save=<instancemethod at remote 0xd803e0>, release=<instancemethod at remote 0xd802e0>, _acquire_restore=<instancemethod at remote 0xd7ee60>, _Verbose__verbose=False, _Condition__waiters=[]) at remote 0xd7fd10>, timeout=None, waiter=<thread.lock at remote 0x858a90>, saved_state=(1, 140737213728528))
                 self._acquire_restore(saved_state)
     #12 Frame 0x7fffb8001a10, for file /home/david/coding/python-svn/Lib/test/lock_tests.py, line 348, in f ()
                 cond.wait()
     #16 Frame 0x7fffb8001c40, for file /home/david/coding/python-svn/Lib/test/lock_tests.py, line 37, in task (tid=140737213728528)
                     f()

     Thread 104 (Thread 0x7fffdf5fe710 (LWP 10259)):
     #5 Frame 0x7fffe4001580, for file /home/david/coding/python-svn/Lib/threading.py, line 155, in _acquire_restore (self=<_RLock(_Verbose__verbose=False, _RLock__owner=140737354016512, _RLock__block=<thread.lock at remote 0x858770>, _RLock__count=1) at remote 0xd7ff40>, count_owner=(1, 140736940992272), count=1, owner=140736940992272)
             self.__block.acquire()
     #8 Frame 0x7fffc8002090, for file /home/david/coding/python-svn/Lib/threading.py, line 269, in wait (self=<_Condition(_Condition__lock=<_RLock(_Verbose__verbose=False, _RLock__owner=140737354016512, _RLock__block=<thread.lock at remote 0x858770>, _RLock__count=1) at remote 0xd7ff40>, acquire=<instancemethod at remote 0xd80260>, _is_owned=<instancemethod at remote 0xd80160>, _release_save=<instancemethod at remote 0xd803e0>, release=<instancemethod at remote 0xd802e0>, _acquire_restore=<instancemethod at remote 0xd7ee60>, _Verbose__verbose=False, _Condition__waiters=[]) at remote 0xd7fd10>, timeout=None, waiter=<thread.lock at remote 0x858860>, saved_state=(1, 140736940992272))
                 self._acquire_restore(saved_state)
     #12 Frame 0x7fffac001c90, for file /home/david/coding/python-svn/Lib/test/lock_tests.py, line 348, in f ()
                 cond.wait()
     #16 Frame 0x7fffac0011c0, for file /home/david/coding/python-svn/Lib/test/lock_tests.py, line 37, in task (tid=140736940992272)
                     f()

     Thread 1 (Thread 0x7ffff7fe2700 (LWP 10145)):
     #5 Frame 0xcb5380, for file /home/david/coding/python-svn/Lib/test/lock_tests.py, line 16, in _wait ()
         time.sleep(0.01)
     #8 Frame 0x7fffd00024a0, for file /home/david/coding/python-svn/Lib/test/lock_tests.py, line 378, in _check_notify (self=<ConditionTests(_testMethodName='test_notify', _resultForDoCleanups=<TestResult(_original_stdout=<cStringIO.StringO at remote 0xc191e0>, skipped=[], _mirrorOutput=False, testsRun=39, buffer=False, _original_stderr=<file at remote 0x7ffff7fc6340>, _stdout_buffer=<cStringIO.StringO at remote 0xc9c7f8>, _stderr_buffer=<cStringIO.StringO at remote 0xc9c790>, _moduleSetUpFailed=False, expectedFailures=[], errors=[], _previousTestClass=<type at remote 0x928310>, unexpectedSuccesses=[], failures=[], shouldStop=False, failfast=False) at remote 0xc185a0>, _threads=(0,), _cleanups=[], _type_equality_funcs={<type at remote 0x7eba00>: <instancemethod at remote 0xd750e0>, <type at remote 0x7e7820>: <instancemethod at remote 0xd75160>, <type at remote 0x7e30e0>: <instancemethod at remote 0xd75060>, <type at remote 0x7e7d20>: <instancemethod at remote 0xd751e0>, <type at remote 0x7f19e0...(truncated)
             _wait()


File: python.info,  Node: Enum HOWTO,  Next: 函式編程 HOWTO,  Prev: 使用 GDB 來為 C API 擴充功能和 CPython 內部偵錯,  Up: Python 如何達成任務

9.5 Enum HOWTO
==============

An *note Enum: 5d6. is a set of symbolic names bound to unique values.
They are similar to global variables, but they offer a more useful *note
repr(): 7a1, grouping, type-safety, and a few other features.

They are most useful when you have a variable that can take one of a
limited selection of values.  For example, the days of the week:

     >>> from enum import Enum
     >>> class Weekday(Enum):
     ...     MONDAY = 1
     ...     TUESDAY = 2
     ...     WEDNESDAY = 3
     ...     THURSDAY = 4
     ...     FRIDAY = 5
     ...     SATURDAY = 6
     ...     SUNDAY = 7

Or perhaps the RGB primary colors:

     >>> from enum import Enum
     >>> class Color(Enum):
     ...     RED = 1
     ...     GREEN = 2
     ...     BLUE = 3

As you can see, creating an *note Enum: 5d6. is as simple as writing a
class that inherits from *note Enum: 5d6. itself.

     備註: Case of Enum Members

     Because Enums are used to represent constants, and to help avoid
     issues with name clashes between mixin-class methods/attributes and
     enum names, we strongly recommend using UPPER_CASE names for
     members, and will be using that style in our examples.

Depending on the nature of the enum a member's value may or may not be
important, but either way that value can be used to get the
corresponding member:

     >>> Weekday(3)
     <Weekday.WEDNESDAY: 3>

As you can see, the ‘repr()’ of a member shows the enum name, the member
name, and the value.  The ‘str()’ of a member shows only the enum name
and member name:

     >>> print(Weekday.THURSDAY)
     Weekday.THURSDAY

The 'type' of an enumeration member is the enum it belongs to:

     >>> type(Weekday.MONDAY)
     <enum 'Weekday'>
     >>> isinstance(Weekday.FRIDAY, Weekday)
     True

Enum members have an attribute that contains just their ‘name’:

     >>> print(Weekday.TUESDAY.name)
     TUESDAY

Likewise, they have an attribute for their ‘value’:

     >>> Weekday.WEDNESDAY.value
     3

Unlike many languages that treat enumerations solely as name/value
pairs, Python Enums can have behavior added.  For example, *note
datetime.date: 1b1. has two methods for returning the weekday:
‘weekday()’ and ‘isoweekday()’.  The difference is that one of them
counts from 0-6 and the other from 1-7.  Rather than keep track of that
ourselves we can add a method to the ‘Weekday’ enum to extract the day
from the ‘date’ instance and return the matching enum member:

     @classmethod
     def from_date(cls, date):
         return cls(date.isoweekday())

The complete ‘Weekday’ enum now looks like this:

     >>> class Weekday(Enum):
     ...     MONDAY = 1
     ...     TUESDAY = 2
     ...     WEDNESDAY = 3
     ...     THURSDAY = 4
     ...     FRIDAY = 5
     ...     SATURDAY = 6
     ...     SUNDAY = 7
     ...     #
     ...     @classmethod
     ...     def from_date(cls, date):
     ...         return cls(date.isoweekday())

Now we can find out what today is!  Observe:

     >>> from datetime import date
     >>> Weekday.from_date(date.today())
     <Weekday.TUESDAY: 2>

Of course, if you're reading this on some other day, you'll see that day
instead.

This ‘Weekday’ enum is great if our variable only needs one day, but
what if we need several?  Maybe we're writing a function to plot chores
during a week, and don't want to use a *note list: 5b6. - we could use a
different type of *note Enum: 5d6.:

     >>> from enum import Flag
     >>> class Weekday(Flag):
     ...     MONDAY = 1
     ...     TUESDAY = 2
     ...     WEDNESDAY = 4
     ...     THURSDAY = 8
     ...     FRIDAY = 16
     ...     SATURDAY = 32
     ...     SUNDAY = 64

We've changed two things: we're inherited from *note Flag: 5c9, and the
values are all powers of 2.

Just like the original ‘Weekday’ enum above, we can have a single
selection:

     >>> first_week_day = Weekday.MONDAY
     >>> first_week_day
     <Weekday.MONDAY: 1>

But *note Flag: 5c9. also allows us to combine several members into a
single variable:

     >>> weekend = Weekday.SATURDAY | Weekday.SUNDAY
     >>> weekend
     <Weekday.SATURDAY|SUNDAY: 96>

You can even iterate over a *note Flag: 5c9. variable:

     >>> for day in weekend:
     ...     print(day)
     Weekday.SATURDAY
     Weekday.SUNDAY

Okay, let's get some chores set up:

     >>> chores_for_ethan = {
     ...     'feed the cat': Weekday.MONDAY | Weekday.WEDNESDAY | Weekday.FRIDAY,
     ...     'do the dishes': Weekday.TUESDAY | Weekday.THURSDAY,
     ...     'answer SO questions': Weekday.SATURDAY,
     ...     }

And a function to display the chores for a given day:

     >>> def show_chores(chores, day):
     ...     for chore, days in chores.items():
     ...         if day in days:
     ...             print(chore)
     ...
     >>> show_chores(chores_for_ethan, Weekday.SATURDAY)
     answer SO questions

In cases where the actual values of the members do not matter, you can
save yourself some work and use *note auto(): c43. for the values:

     >>> from enum import auto
     >>> class Weekday(Flag):
     ...     MONDAY = auto()
     ...     TUESDAY = auto()
     ...     WEDNESDAY = auto()
     ...     THURSDAY = auto()
     ...     FRIDAY = auto()
     ...     SATURDAY = auto()
     ...     SUNDAY = auto()
     ...     WEEKEND = SATURDAY | SUNDAY

* Menu:

* Programmatic access to enumeration members and their attributes::
* Duplicating enum members and values::
* Ensuring unique enumeration values::
* Using automatic values::
* Iteration: Iteration<2>.
* 比較::
* Allowed members and attributes of enumerations::
* Restricted Enum subclassing::
* Dataclass support::
* Pickling::
* Functional API: Functional API<3>.
* Derived Enumerations::
* When to use __new__() vs. __init__(): When to use __new__ vs __init__.
* How are Enums and Flags different?::
* Enum Cookbook::
* Subclassing EnumType::


File: python.info,  Node: Programmatic access to enumeration members and their attributes,  Next: Duplicating enum members and values,  Up: Enum HOWTO

9.5.1 Programmatic access to enumeration members and their attributes
---------------------------------------------------------------------

Sometimes it's useful to access members in enumerations programmatically
(i.e.  situations where ‘Color.RED’ won't do because the exact color is
not known at program-writing time).  ‘Enum’ allows such access:

     >>> Color(1)
     <Color.RED: 1>
     >>> Color(3)
     <Color.BLUE: 3>

If you want to access enum members by 'name', use item access:

     >>> Color['RED']
     <Color.RED: 1>
     >>> Color['GREEN']
     <Color.GREEN: 2>

If you have an enum member and need its ‘name’ or ‘value’:

     >>> member = Color.RED
     >>> member.name
     'RED'
     >>> member.value
     1


File: python.info,  Node: Duplicating enum members and values,  Next: Ensuring unique enumeration values,  Prev: Programmatic access to enumeration members and their attributes,  Up: Enum HOWTO

9.5.2 Duplicating enum members and values
-----------------------------------------

Having two enum members with the same name is invalid:

     >>> class Shape(Enum):
     ...     SQUARE = 2
     ...     SQUARE = 3
     ...
     Traceback (most recent call last):
     ...
     TypeError: 'SQUARE' already defined as 2

However, an enum member can have other names associated with it.  Given
two entries ‘A’ and ‘B’ with the same value (and ‘A’ defined first), ‘B’
is an alias for the member ‘A’.  By-value lookup of the value of ‘A’
will return the member ‘A’.  By-name lookup of ‘A’ will return the
member ‘A’.  By-name lookup of ‘B’ will also return the member ‘A’:

     >>> class Shape(Enum):
     ...     SQUARE = 2
     ...     DIAMOND = 1
     ...     CIRCLE = 3
     ...     ALIAS_FOR_SQUARE = 2
     ...
     >>> Shape.SQUARE
     <Shape.SQUARE: 2>
     >>> Shape.ALIAS_FOR_SQUARE
     <Shape.SQUARE: 2>
     >>> Shape(2)
     <Shape.SQUARE: 2>

     備註: Attempting to create a member with the same name as an
     already defined attribute (another member, a method, etc.)  or
     attempting to create an attribute with the same name as a member is
     not allowed.


File: python.info,  Node: Ensuring unique enumeration values,  Next: Using automatic values,  Prev: Duplicating enum members and values,  Up: Enum HOWTO

9.5.3 Ensuring unique enumeration values
----------------------------------------

By default, enumerations allow multiple names as aliases for the same
value.  When this behavior isn't desired, you can use the *note
unique(): 2496. decorator:

     >>> from enum import Enum, unique
     >>> @unique
     ... class Mistake(Enum):
     ...     ONE = 1
     ...     TWO = 2
     ...     THREE = 3
     ...     FOUR = 3
     ...
     Traceback (most recent call last):
     ...
     ValueError: duplicate values found in <enum 'Mistake'>: FOUR -> THREE


File: python.info,  Node: Using automatic values,  Next: Iteration<2>,  Prev: Ensuring unique enumeration values,  Up: Enum HOWTO

9.5.4 Using automatic values
----------------------------

If the exact value is unimportant you can use *note auto: c43.:

     >>> from enum import Enum, auto
     >>> class Color(Enum):
     ...     RED = auto()
     ...     BLUE = auto()
     ...     GREEN = auto()
     ...
     >>> [member.value for member in Color]
     [1, 2, 3]

The values are chosen by ‘_generate_next_value_()’, which can be
overridden:

     >>> class AutoName(Enum):
     ...     @staticmethod
     ...     def _generate_next_value_(name, start, count, last_values):
     ...         return name
     ...
     >>> class Ordinal(AutoName):
     ...     NORTH = auto()
     ...     SOUTH = auto()
     ...     EAST = auto()
     ...     WEST = auto()
     ...
     >>> [member.value for member in Ordinal]
     ['NORTH', 'SOUTH', 'EAST', 'WEST']

     備註: The ‘_generate_next_value_()’ method must be defined before
     any members.


File: python.info,  Node: Iteration<2>,  Next: 比較,  Prev: Using automatic values,  Up: Enum HOWTO

9.5.5 Iteration
---------------

Iterating over the members of an enum does not provide the aliases:

     >>> list(Shape)
     [<Shape.SQUARE: 2>, <Shape.DIAMOND: 1>, <Shape.CIRCLE: 3>]
     >>> list(Weekday)
     [<Weekday.MONDAY: 1>, <Weekday.TUESDAY: 2>, <Weekday.WEDNESDAY: 4>, <Weekday.THURSDAY: 8>, <Weekday.FRIDAY: 16>, <Weekday.SATURDAY: 32>, <Weekday.SUNDAY: 64>]

Note that the aliases ‘Shape.ALIAS_FOR_SQUARE’ and ‘Weekday.WEEKEND’
aren't shown.

The special attribute ‘__members__’ is a read-only ordered mapping of
names to members.  It includes all names defined in the enumeration,
including the aliases:

     >>> for name, member in Shape.__members__.items():
     ...     name, member
     ...
     ('SQUARE', <Shape.SQUARE: 2>)
     ('DIAMOND', <Shape.DIAMOND: 1>)
     ('CIRCLE', <Shape.CIRCLE: 3>)
     ('ALIAS_FOR_SQUARE', <Shape.SQUARE: 2>)

The ‘__members__’ attribute can be used for detailed programmatic access
to the enumeration members.  For example, finding all the aliases:

     >>> [name for name, member in Shape.__members__.items() if member.name != name]
     ['ALIAS_FOR_SQUARE']

     備註: Aliases for flags include values with multiple flags set,
     such as ‘3’, and no flags set, i.e.  ‘0’.


File: python.info,  Node: 比較,  Next: Allowed members and attributes of enumerations,  Prev: Iteration<2>,  Up: Enum HOWTO

9.5.6 比較
----------

Enumeration members are compared by identity:

     >>> Color.RED is Color.RED
     True
     >>> Color.RED is Color.BLUE
     False
     >>> Color.RED is not Color.BLUE
     True

Ordered comparisons between enumeration values are 'not' supported.
Enum members are not integers (but see *note IntEnum: 4ce6. below):

     >>> Color.RED < Color.BLUE
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: '<' not supported between instances of 'Color' and 'Color'

Equality comparisons are defined though:

     >>> Color.BLUE == Color.RED
     False
     >>> Color.BLUE != Color.RED
     True
     >>> Color.BLUE == Color.BLUE
     True

Comparisons against non-enumeration values will always compare not equal
(again, *note IntEnum: c86. was explicitly designed to behave
differently, see below):

     >>> Color.BLUE == 2
     False

     警告: It is possible to reload modules - if a reloaded module
     contains enums, they will be recreated, and the new members may not
     compare identical/equal to the original members.


File: python.info,  Node: Allowed members and attributes of enumerations,  Next: Restricted Enum subclassing,  Prev: 比較,  Up: Enum HOWTO

9.5.7 Allowed members and attributes of enumerations
----------------------------------------------------

Most of the examples above use integers for enumeration values.  Using
integers is short and handy (and provided by default by the *note
Functional API: 4ce8.), but not strictly enforced.  In the vast majority
of use-cases, one doesn't care what the actual value of an enumeration
is.  But if the value 'is' important, enumerations can have arbitrary
values.

Enumerations are Python classes, and can have methods and special
methods as usual.  If we have this enumeration:

     >>> class Mood(Enum):
     ...     FUNKY = 1
     ...     HAPPY = 3
     ...
     ...     def describe(self):
     ...         # self is the member here
     ...         return self.name, self.value
     ...
     ...     def __str__(self):
     ...         return 'my custom str! {0}'.format(self.value)
     ...
     ...     @classmethod
     ...     def favorite_mood(cls):
     ...         # cls here is the enumeration
     ...         return cls.HAPPY
     ...

Then:

     >>> Mood.favorite_mood()
     <Mood.HAPPY: 3>
     >>> Mood.HAPPY.describe()
     ('HAPPY', 3)
     >>> str(Mood.FUNKY)
     'my custom str! 1'

The rules for what is allowed are as follows: names that start and end
with a single underscore are reserved by enum and cannot be used; all
other attributes defined within an enumeration will become members of
this enumeration, with the exception of special methods (‘__str__()’,
‘__add__()’, etc.), descriptors (methods are also descriptors), and
variable names listed in ‘_ignore_’.

Note: if your enumeration defines ‘__new__()’ and/or ‘__init__()’, any
value(s) given to the enum member will be passed into those methods.
See *note Planet: 4ce9. for an example.

     備註: The ‘__new__()’ method, if defined, is used during creation
     of the Enum members; it is then replaced by Enum's ‘__new__()’
     which is used after class creation for lookup of existing members.
     See *note When to use __new__() vs.  __init__(): 4cea. for more
     details.


File: python.info,  Node: Restricted Enum subclassing,  Next: Dataclass support,  Prev: Allowed members and attributes of enumerations,  Up: Enum HOWTO

9.5.8 Restricted Enum subclassing
---------------------------------

A new *note Enum: 5d6. class must have one base enum class, up to one
concrete data type, and as many *note object: a2f.-based mixin classes
as needed.  The order of these base classes is:

     class EnumName([mix-in, ...,] [data-type,] base-enum):
         pass

Also, subclassing an enumeration is allowed only if the enumeration does
not define any members.  So this is forbidden:

     >>> class MoreColor(Color):
     ...     PINK = 17
     ...
     Traceback (most recent call last):
     ...
     TypeError: <enum 'MoreColor'> cannot extend <enum 'Color'>

但這是允許的：

     >>> class Foo(Enum):
     ...     def some_behavior(self):
     ...         pass
     ...
     >>> class Bar(Foo):
     ...     HAPPY = 1
     ...     SAD = 2
     ...

Allowing subclassing of enums that define members would lead to a
violation of some important invariants of types and instances.  On the
other hand, it makes sense to allow sharing some common behavior between
a group of enumerations.  (See *note OrderedEnum: 4cec. for an example.)


File: python.info,  Node: Dataclass support,  Next: Pickling,  Prev: Restricted Enum subclassing,  Up: Enum HOWTO

9.5.9 Dataclass support
-----------------------

When inheriting from a *note dataclass: 1af, the *note __repr__(): 1688.
omits the inherited class' name.  For example:

     >>> from dataclasses import dataclass, field
     >>> @dataclass
     ... class CreatureDataMixin:
     ...     size: str
     ...     legs: int
     ...     tail: bool = field(repr=False, default=True)
     ...
     >>> class Creature(CreatureDataMixin, Enum):
     ...     BEETLE = 'small', 6
     ...     DOG = 'medium', 4
     ...
     >>> Creature.DOG
     <Creature.DOG: size='medium', legs=4>

Use the *note dataclass(): 1af. argument ‘repr=False’ to use the
standard *note repr(): 7a1.

在 3.12 版的變更: Only the dataclass fields are shown in the value area,
not the dataclass' name.

     備註: Adding *note dataclass(): 1af. decorator to *note Enum: 5d6.
     and its subclasses is not supported.  It will not raise any errors,
     but it will produce very strange results at runtime, such as
     members being equal to each other:

          >>> @dataclass               # don't do this: it does not make any sense
          ... class Color(Enum):
          ...    RED = 1
          ...    BLUE = 2
          ...
          >>> Color.RED is Color.BLUE
          False
          >>> Color.RED == Color.BLUE  # problem is here: they should not be equal
          True


File: python.info,  Node: Pickling,  Next: Functional API<3>,  Prev: Dataclass support,  Up: Enum HOWTO

9.5.10 Pickling
---------------

Enumerations can be pickled and unpickled:

     >>> from test.test_enum import Fruit
     >>> from pickle import dumps, loads
     >>> Fruit.TOMATO is loads(dumps(Fruit.TOMATO))
     True

The usual restrictions for pickling apply: picklable enums must be
defined in the top level of a module, since unpickling requires them to
be importable from that module.

     備註: With pickle protocol version 4 it is possible to easily
     pickle enums nested in other classes.

It is possible to modify how enum members are pickled/unpickled by
defining ‘__reduce_ex__()’ in the enumeration class.  The default method
is by-value, but enums with complicated values may want to use by-name:

     >>> import enum
     >>> class MyEnum(enum.Enum):
     ...     __reduce_ex__ = enum.pickle_by_enum_name

     備註: Using by-name for flags is not recommended, as unnamed
     aliases will not unpickle.


File: python.info,  Node: Functional API<3>,  Next: Derived Enumerations,  Prev: Pickling,  Up: Enum HOWTO

9.5.11 Functional API
---------------------

The *note Enum: 5d6. class is callable, providing the following
functional API:

     >>> Animal = Enum('Animal', 'ANT BEE CAT DOG')
     >>> Animal
     <enum 'Animal'>
     >>> Animal.ANT
     <Animal.ANT: 1>
     >>> list(Animal)
     [<Animal.ANT: 1>, <Animal.BEE: 2>, <Animal.CAT: 3>, <Animal.DOG: 4>]

The semantics of this API resemble *note namedtuple: 1ae.  The first
argument of the call to *note Enum: 5d6. is the name of the enumeration.

The second argument is the 'source' of enumeration member names.  It can
be a whitespace-separated string of names, a sequence of names, a
sequence of 2-tuples with key/value pairs, or a mapping (e.g.
dictionary) of names to values.  The last two options enable assigning
arbitrary values to enumerations; the others auto-assign increasing
integers starting with 1 (use the ‘start’ parameter to specify a
different starting value).  A new class derived from *note Enum: 5d6. is
returned.  In other words, the above assignment to ‘Animal’ is
equivalent to:

     >>> class Animal(Enum):
     ...     ANT = 1
     ...     BEE = 2
     ...     CAT = 3
     ...     DOG = 4
     ...

The reason for defaulting to ‘1’ as the starting number and not ‘0’ is
that ‘0’ is ‘False’ in a boolean sense, but by default enum members all
evaluate to ‘True’.

Pickling enums created with the functional API can be tricky as frame
stack implementation details are used to try and figure out which module
the enumeration is being created in (e.g.  it will fail if you use a
utility function in a separate module, and also may not work on
IronPython or Jython).  The solution is to specify the module name
explicitly as follows:

     >>> Animal = Enum('Animal', 'ANT BEE CAT DOG', module=__name__)

     警告: If ‘module’ is not supplied, and Enum cannot determine what
     it is, the new Enum members will not be unpicklable; to keep errors
     closer to the source, pickling will be disabled.

The new pickle protocol 4 also, in some circumstances, relies on *note
__qualname__: 1dec. being set to the location where pickle will be able
to find the class.  For example, if the class was made available in
class SomeData in the global scope:

     >>> Animal = Enum('Animal', 'ANT BEE CAT DOG', qualname='SomeData.Animal')

The complete signature is:

     Enum(
         value='NewEnumName',
         names=<...>,
         *,
         module='...',
         qualname='...',
         type=<mixed-in class>,
         start=1,
         )

   * 'value': What the new enum class will record as its name.

   * 'names': The enum members.  This can be a whitespace- or
     comma-separated string (values will start at 1 unless otherwise
     specified):

          'RED GREEN BLUE' | 'RED,GREEN,BLUE' | 'RED, GREEN, BLUE'

     or an iterator of names:

          ['RED', 'GREEN', 'BLUE']

     or an iterator of (name, value) pairs:

          [('CYAN', 4), ('MAGENTA', 5), ('YELLOW', 6)]

     or a mapping:

          {'CHARTREUSE': 7, 'SEA_GREEN': 11, 'ROSEMARY': 42}

   * 'module': name of module where new enum class can be found.

   * 'qualname': where in module new enum class can be found.

   * 'type': type to mix in to new enum class.

   * 'start': number to start counting at if only names are passed in.

在 3.5 版的變更: The 'start' parameter was added.


File: python.info,  Node: Derived Enumerations,  Next: When to use __new__ vs __init__,  Prev: Functional API<3>,  Up: Enum HOWTO

9.5.12 Derived Enumerations
---------------------------

* Menu:

* IntEnum::
* StrEnum::
* IntFlag::
* Flag::
* 其他: 其他<2>.


File: python.info,  Node: IntEnum,  Next: StrEnum,  Up: Derived Enumerations

9.5.12.1 IntEnum
................

The first variation of *note Enum: 5d6. that is provided is also a
subclass of *note int: 23c.  Members of an *note IntEnum: c86. can be
compared to integers; by extension, integer enumerations of different
types can also be compared to each other:

     >>> from enum import IntEnum
     >>> class Shape(IntEnum):
     ...     CIRCLE = 1
     ...     SQUARE = 2
     ...
     >>> class Request(IntEnum):
     ...     POST = 1
     ...     GET = 2
     ...
     >>> Shape == 1
     False
     >>> Shape.CIRCLE == 1
     True
     >>> Shape.CIRCLE == Request.POST
     True

However, they still can't be compared to standard *note Enum: 5d6.
enumerations:

     >>> class Shape(IntEnum):
     ...     CIRCLE = 1
     ...     SQUARE = 2
     ...
     >>> class Color(Enum):
     ...     RED = 1
     ...     GREEN = 2
     ...
     >>> Shape.CIRCLE == Color.RED
     False

*note IntEnum: c86. values behave like integers in other ways you'd
expect:

     >>> int(Shape.CIRCLE)
     1
     >>> ['a', 'b', 'c'][Shape.CIRCLE]
     'b'
     >>> [i for i in range(Shape.SQUARE)]
     [0, 1]


File: python.info,  Node: StrEnum,  Next: IntFlag,  Prev: IntEnum,  Up: Derived Enumerations

9.5.12.2 StrEnum
................

The second variation of *note Enum: 5d6. that is provided is also a
subclass of *note str: 3f2.  Members of a *note StrEnum: 5c0. can be
compared to strings; by extension, string enumerations of different
types can also be compared to each other.

在 3.11 版被加入.


File: python.info,  Node: IntFlag,  Next: Flag,  Prev: StrEnum,  Up: Derived Enumerations

9.5.12.3 IntFlag
................

The next variation of *note Enum: 5d6. provided, *note IntFlag: 21d7, is
also based on *note int: 23c.  The difference being *note IntFlag: 21d7.
members can be combined using the bitwise operators (&, |, ^, ~) and the
result is still an *note IntFlag: 21d7. member, if possible.  Like *note
IntEnum: c86, *note IntFlag: 21d7. members are also integers and can be
used wherever an *note int: 23c. is used.

     備註: Any operation on an *note IntFlag: 21d7. member besides the
     bit-wise operations will lose the *note IntFlag: 21d7. membership.

     Bit-wise operations that result in invalid *note IntFlag: 21d7.
     values will lose the *note IntFlag: 21d7. membership.  See *note
     FlagBoundary: 5ca. for details.

在 3.6 版被加入.

在 3.11 版的變更.

Sample *note IntFlag: 21d7. class:

     >>> from enum import IntFlag
     >>> class Perm(IntFlag):
     ...     R = 4
     ...     W = 2
     ...     X = 1
     ...
     >>> Perm.R | Perm.W
     <Perm.R|W: 6>
     >>> Perm.R + Perm.W
     6
     >>> RW = Perm.R | Perm.W
     >>> Perm.R in RW
     True

It is also possible to name the combinations:

     >>> class Perm(IntFlag):
     ...     R = 4
     ...     W = 2
     ...     X = 1
     ...     RWX = 7
     ...
     >>> Perm.RWX
     <Perm.RWX: 7>
     >>> ~Perm.RWX
     <Perm: 0>
     >>> Perm(7)
     <Perm.RWX: 7>

     備註: Named combinations are considered aliases.  Aliases do not
     show up during iteration, but can be returned from by-value
     lookups.

在 3.11 版的變更.

Another important difference between *note IntFlag: 21d7. and *note
Enum: 5d6. is that if no flags are set (the value is 0), its boolean
evaluation is *note False: adb.:

     >>> Perm.R & Perm.X
     <Perm: 0>
     >>> bool(Perm.R & Perm.X)
     False

Because *note IntFlag: 21d7. members are also subclasses of *note int:
23c. they can be combined with them (but may lose *note IntFlag: 21d7.
membership:

     >>> Perm.X | 4
     <Perm.R|X: 5>

     >>> Perm.X + 8
     9

     備註: The negation operator, ‘~’, always returns an *note IntFlag:
     21d7. member with a positive value:

          >>> (~Perm.X).value == (Perm.R|Perm.W).value == 6
          True

*note IntFlag: 21d7. members can also be iterated over:

     >>> list(RW)
     [<Perm.R: 4>, <Perm.W: 2>]

在 3.11 版被加入.


File: python.info,  Node: Flag,  Next: 其他<2>,  Prev: IntFlag,  Up: Derived Enumerations

9.5.12.4 Flag
.............

The last variation is *note Flag: 5c9.  Like *note IntFlag: 21d7, *note
Flag: 5c9. members can be combined using the bitwise operators (&, |, ^,
~).  Unlike *note IntFlag: 21d7, they cannot be combined with, nor
compared against, any other *note Flag: 5c9. enumeration, nor *note int:
23c.  While it is possible to specify the values directly it is
recommended to use *note auto: c43. as the value and let *note Flag:
5c9. select an appropriate value.

在 3.6 版被加入.

Like *note IntFlag: 21d7, if a combination of *note Flag: 5c9. members
results in no flags being set, the boolean evaluation is *note False:
adb.:

     >>> from enum import Flag, auto
     >>> class Color(Flag):
     ...     RED = auto()
     ...     BLUE = auto()
     ...     GREEN = auto()
     ...
     >>> Color.RED & Color.GREEN
     <Color: 0>
     >>> bool(Color.RED & Color.GREEN)
     False

Individual flags should have values that are powers of two (1, 2, 4, 8,
...), while combinations of flags will not:

     >>> class Color(Flag):
     ...     RED = auto()
     ...     BLUE = auto()
     ...     GREEN = auto()
     ...     WHITE = RED | BLUE | GREEN
     ...
     >>> Color.WHITE
     <Color.WHITE: 7>

Giving a name to the "no flags set" condition does not change its
boolean value:

     >>> class Color(Flag):
     ...     BLACK = 0
     ...     RED = auto()
     ...     BLUE = auto()
     ...     GREEN = auto()
     ...
     >>> Color.BLACK
     <Color.BLACK: 0>
     >>> bool(Color.BLACK)
     False

*note Flag: 5c9. members can also be iterated over:

     >>> purple = Color.RED | Color.BLUE
     >>> list(purple)
     [<Color.RED: 1>, <Color.BLUE: 2>]

在 3.11 版被加入.

     備註: For the majority of new code, *note Enum: 5d6. and *note
     Flag: 5c9. are strongly recommended, since *note IntEnum: c86. and
     *note IntFlag: 21d7. break some semantic promises of an enumeration
     (by being comparable to integers, and thus by transitivity to other
     unrelated enumerations).  *note IntEnum: c86. and *note IntFlag:
     21d7. should be used only in cases where *note Enum: 5d6. and *note
     Flag: 5c9. will not do; for example, when integer constants are
     replaced with enumerations, or for interoperability with other
     systems.


File: python.info,  Node: 其他<2>,  Prev: Flag,  Up: Derived Enumerations

9.5.12.5 其他
.............

While *note IntEnum: c86. is part of the *note enum: 4c. module, it
would be very simple to implement independently:

     class IntEnum(int, ReprEnum):   # or Enum instead of ReprEnum
         pass

This demonstrates how similar derived enumerations can be defined; for
example a ‘FloatEnum’ that mixes in *note float: 2c8. instead of *note
int: 23c.

一些規則：

  1. When subclassing *note Enum: 5d6, mix-in types must appear before
     the *note Enum: 5d6. class itself in the sequence of bases, as in
     the *note IntEnum: c86. example above.

  2. Mix-in types must be subclassable.  For example, *note bool: 40e.
     and *note range: 8e7. are not subclassable and will throw an error
     during Enum creation if used as the mix-in type.

  3. While *note Enum: 5d6. can have members of any type, once you mix
     in an additional type, all the members must have values of that
     type, e.g.  *note int: 23c. above.  This restriction does not apply
     to mix-ins which only add methods and don't specify another type.

  4. When another data type is mixed in, the ‘value’ attribute is 'not
     the same' as the enum member itself, although it is equivalent and
     will compare equal.

  5. A ‘data type’ is a mixin that defines ‘__new__()’, or a *note
     dataclass: 1af.

  6. %-style formatting: ‘%s’ and ‘%r’ call the *note Enum: 5d6. class's
     ‘__str__()’ and ‘__repr__()’ respectively; other codes (such as
     ‘%i’ or ‘%h’ for IntEnum) treat the enum member as its mixed-in
     type.

  7. *note Formatted string literals: 94d, *note str.format(): 5c7, and
     *note format(): 5c3. will use the enum's ‘__str__()’ method.

     備註: Because *note IntEnum: c86, *note IntFlag: 21d7, and *note
     StrEnum: 5c0. are designed to be drop-in replacements for existing
     constants, their ‘__str__()’ method has been reset to their data
     types' ‘__str__()’ method.


File: python.info,  Node: When to use __new__ vs __init__,  Next: How are Enums and Flags different?,  Prev: Derived Enumerations,  Up: Enum HOWTO

9.5.13 When to use ‘__new__()’ vs. ‘__init__()’
-----------------------------------------------

‘__new__()’ must be used whenever you want to customize the actual value
of the *note Enum: 5d6. member.  Any other modifications may go in
either ‘__new__()’ or ‘__init__()’, with ‘__init__()’ being preferred.

For example, if you want to pass several items to the constructor, but
only want one of them to be the value:

     >>> class Coordinate(bytes, Enum):
     ...     """
     ...     Coordinate with binary codes that can be indexed by the int code.
     ...     """
     ...     def __new__(cls, value, label, unit):
     ...         obj = bytes.__new__(cls, [value])
     ...         obj._value_ = value
     ...         obj.label = label
     ...         obj.unit = unit
     ...         return obj
     ...     PX = (0, 'P.X', 'km')
     ...     PY = (1, 'P.Y', 'km')
     ...     VX = (2, 'V.X', 'km/s')
     ...     VY = (3, 'V.Y', 'km/s')
     ...

     >>> print(Coordinate['PY'])
     Coordinate.PY

     >>> print(Coordinate(3))
     Coordinate.VY

     警告: 'Do not' call ‘super().__new__()’, as the lookup-only
     ‘__new__’ is the one that is found; instead, use the data type
     directly.

* Menu:

* Finer Points::


File: python.info,  Node: Finer Points,  Up: When to use __new__ vs __init__

9.5.13.1 Finer Points
.....................

* Menu:

* Supported __dunder__ names::
* Supported _sunder_ names::
* _Private__names::
* Enum member type::
* Creating members that are mixed with other data types::
* Boolean value of Enum classes and members::
* Enum classes with methods::
* Combining members of Flag::
* Flag and IntFlag minutia::


File: python.info,  Node: Supported __dunder__ names,  Next: Supported _sunder_ names,  Up: Finer Points

9.5.13.2 Supported ‘__dunder__’ names
.....................................

‘__members__’ is a read-only ordered mapping of ‘member_name’:‘member’
items.  It is only available on the class.

‘__new__()’, if specified, must create and return the enum members; it
is also a very good idea to set the member's ‘_value_’ appropriately.
Once all the members are created it is no longer used.


File: python.info,  Node: Supported _sunder_ names,  Next: _Private__names,  Prev: Supported __dunder__ names,  Up: Finer Points

9.5.13.3 Supported ‘_sunder_’ names
...................................

   - *note _name_: 24a7. - name of the member

   - *note _value_: 24a8. - value of the member; can be set in ‘__new__’

   - *note _missing_(): 24af. - a lookup function used when a value is
     not found; may be overridden

   - *note _ignore_: 24aa. - a list of names, either as a *note list:
     5b6. or a *note str: 3f2, that will not be transformed into
     members, and will be removed from the final class

   - *note _generate_next_value_(): 24ac. - used to get an appropriate
     value for an enum member; may be overridden

   - ‘_add_alias_()’ - adds a new name as an alias to an existing
     member.

   - ‘_add_value_alias_()’ - adds a new value as an alias to an existing
     member.  See *note MultiValueEnum: 4cf8. for an example.

          備註: For standard *note Enum: 5d6. classes the next value
          chosen is the highest value seen incremented by one.

          For *note Flag: 5c9. classes the next value chosen will be the
          next highest power-of-two.

     在 3.13 版的變更: Prior versions would use the last seen value
     instead of the highest value.

在 3.6 版被加入: ‘_missing_’、‘_order_’、‘_generate_next_value_’

在 3.7 版被加入: ‘_ignore_’

在 3.13 版被加入: ‘_add_alias_’, ‘_add_value_alias_’

To help keep Python 2 / Python 3 code in sync an ‘_order_’ attribute can
be provided.  It will be checked against the actual order of the
enumeration and raise an error if the two do not match:

     >>> class Color(Enum):
     ...     _order_ = 'RED GREEN BLUE'
     ...     RED = 1
     ...     BLUE = 3
     ...     GREEN = 2
     ...
     Traceback (most recent call last):
     ...
     TypeError: member order does not match _order_:
       ['RED', 'BLUE', 'GREEN']
       ['RED', 'GREEN', 'BLUE']

     備註: In Python 2 code the ‘_order_’ attribute is necessary as
     definition order is lost before it can be recorded.


File: python.info,  Node: _Private__names,  Next: Enum member type,  Prev: Supported _sunder_ names,  Up: Finer Points

9.5.13.4 _Private__names
........................

*note Private names: 1bbd. are not converted to enum members, but remain
normal attributes.

在 3.11 版的變更.


File: python.info,  Node: Enum member type,  Next: Creating members that are mixed with other data types,  Prev: _Private__names,  Up: Finer Points

9.5.13.5 ‘Enum’ member type
...........................

Enum members are instances of their enum class, and are normally
accessed as ‘EnumClass.member’.  In certain situations, such as writing
custom enum behavior, being able to access one member directly from
another is useful, and is supported; however, in order to avoid name
clashes between member names and attributes/methods from mixed-in
classes, upper-case names are strongly recommended.

在 3.5 版的變更.


File: python.info,  Node: Creating members that are mixed with other data types,  Next: Boolean value of Enum classes and members,  Prev: Enum member type,  Up: Finer Points

9.5.13.6 Creating members that are mixed with other data types
..............................................................

When subclassing other data types, such as *note int: 23c. or *note str:
3f2, with an *note Enum: 5d6, all values after the ‘=’ are passed to
that data type's constructor.  For example:

     >>> class MyEnum(IntEnum):      # help(int) -> int(x, base=10) -> integer
     ...     example = '11', 16      # so x='11' and base=16
     ...
     >>> MyEnum.example.value        # and hex(11) is...
     17


File: python.info,  Node: Boolean value of Enum classes and members,  Next: Enum classes with methods,  Prev: Creating members that are mixed with other data types,  Up: Finer Points

9.5.13.7 Boolean value of ‘Enum’ classes and members
....................................................

Enum classes that are mixed with non-*note Enum: 5d6. types (such as
*note int: 23c, *note str: 3f2, etc.)  are evaluated according to the
mixed-in type's rules; otherwise, all members evaluate as *note True:
bb4.  To make your own enum's boolean evaluation depend on the member's
value add the following to your class:

     def __bool__(self):
         return bool(self.value)

Plain *note Enum: 5d6. classes always evaluate as *note True: bb4.


File: python.info,  Node: Enum classes with methods,  Next: Combining members of Flag,  Prev: Boolean value of Enum classes and members,  Up: Finer Points

9.5.13.8 ‘Enum’ classes with methods
....................................

If you give your enum subclass extra methods, like the *note Planet:
4ce9. class below, those methods will show up in a *note dir(): 5d8. of
the member, but not of the class:

     >>> dir(Planet)
     ['EARTH', 'JUPITER', 'MARS', 'MERCURY', 'NEPTUNE', 'SATURN', 'URANUS', 'VENUS', '__class__', '__doc__', '__members__', '__module__']
     >>> dir(Planet.EARTH)
     ['__class__', '__doc__', '__module__', 'mass', 'name', 'radius', 'surface_gravity', 'value']


File: python.info,  Node: Combining members of Flag,  Next: Flag and IntFlag minutia,  Prev: Enum classes with methods,  Up: Finer Points

9.5.13.9 Combining members of ‘Flag’
....................................

Iterating over a combination of *note Flag: 5c9. members will only
return the members that are comprised of a single bit:

     >>> class Color(Flag):
     ...     RED = auto()
     ...     GREEN = auto()
     ...     BLUE = auto()
     ...     MAGENTA = RED | BLUE
     ...     YELLOW = RED | GREEN
     ...     CYAN = GREEN | BLUE
     ...
     >>> Color(3)  # named combination
     <Color.YELLOW: 3>
     >>> Color(7)      # not named combination
     <Color.RED|GREEN|BLUE: 7>


File: python.info,  Node: Flag and IntFlag minutia,  Prev: Combining members of Flag,  Up: Finer Points

9.5.13.10 ‘Flag’ and ‘IntFlag’ minutia
......................................

Using the following snippet for our examples:

     >>> class Color(IntFlag):
     ...     BLACK = 0
     ...     RED = 1
     ...     GREEN = 2
     ...     BLUE = 4
     ...     PURPLE = RED | BLUE
     ...     WHITE = RED | GREEN | BLUE
     ...

the following are true:

   - single-bit flags are canonical

   - multi-bit and zero-bit flags are aliases

   - only canonical flags are returned during iteration:

          >>> list(Color.WHITE)
          [<Color.RED: 1>, <Color.GREEN: 2>, <Color.BLUE: 4>]

   - negating a flag or flag set returns a new flag/flag set with the
     corresponding positive integer value:

          >>> Color.BLUE
          <Color.BLUE: 4>

          >>> ~Color.BLUE
          <Color.RED|GREEN: 3>

   - names of pseudo-flags are constructed from their members' names:

          >>> (Color.RED | Color.GREEN).name
          'RED|GREEN'

          >>> class Perm(IntFlag):
          ...     R = 4
          ...     W = 2
          ...     X = 1
          ...
          >>> (Perm.R & Perm.W).name is None  # effectively Perm(0)
          True

   - multi-bit flags, aka aliases, can be returned from operations:

          >>> Color.RED | Color.BLUE
          <Color.PURPLE: 5>

          >>> Color(7)  # 或 Color(-1)
          <Color.WHITE: 7>

          >>> Color(0)
          <Color.BLACK: 0>

   - membership / containment checking: zero-valued flags are always
     considered to be contained:

          >>> Color.BLACK in Color.WHITE
          True

     otherwise, only if all bits of one flag are in the other flag will
     True be returned:

          >>> Color.PURPLE in Color.WHITE
          True

          >>> Color.GREEN in Color.PURPLE
          False

There is a new boundary mechanism that controls how out-of-range /
invalid bits are handled: ‘STRICT’, ‘CONFORM’, ‘EJECT’, and ‘KEEP’:

   * STRICT -> raises an exception when presented with invalid values

   * CONFORM -> discards any invalid bits

   * EJECT -> lose Flag status and become a normal int with the given
     value

   * KEEP -> keep the extra bits

        - keeps Flag status and extra bits

        - extra bits do not show up in iteration

        - extra bits do show up in repr() and str()

The default for Flag is ‘STRICT’, the default for ‘IntFlag’ is ‘EJECT’,
and the default for ‘_convert_’ is ‘KEEP’ (see ‘ssl.Options’ for an
example of when ‘KEEP’ is needed).


File: python.info,  Node: How are Enums and Flags different?,  Next: Enum Cookbook,  Prev: When to use __new__ vs __init__,  Up: Enum HOWTO

9.5.14 How are Enums and Flags different?
-----------------------------------------

Enums have a custom metaclass that affects many aspects of both derived
*note Enum: 5d6. classes and their instances (members).

* Menu:

* Enum Classes::
* Flag Classes::
* Enum Members (aka instances): Enum Members aka instances.
* Flag Members::


File: python.info,  Node: Enum Classes,  Next: Flag Classes,  Up: How are Enums and Flags different?

9.5.14.1 Enum Classes
.....................

The *note EnumType: 5bf. metaclass is responsible for providing the
‘__contains__()’, ‘__dir__()’, ‘__iter__()’ and other methods that allow
one to do things with an *note Enum: 5d6. class that fail on a typical
class, such as ‘list(Color)’ or ‘some_enum_var in Color’.  *note
EnumType: 5bf. is responsible for ensuring that various other methods on
the final *note Enum: 5d6. class are correct (such as ‘__new__()’,
‘__getnewargs__()’, ‘__str__()’ and ‘__repr__()’).


File: python.info,  Node: Flag Classes,  Next: Enum Members aka instances,  Prev: Enum Classes,  Up: How are Enums and Flags different?

9.5.14.2 Flag Classes
.....................

Flags have an expanded view of aliasing: to be canonical, the value of a
flag needs to be a power-of-two value, and not a duplicate name.  So, in
addition to the *note Enum: 5d6. definition of alias, a flag with no
value (a.k.a.  ‘0’) or with more than one power-of-two value (e.g.  ‘3’)
is considered an alias.


File: python.info,  Node: Enum Members aka instances,  Next: Flag Members,  Prev: Flag Classes,  Up: How are Enums and Flags different?

9.5.14.3 Enum Members (aka instances)
.....................................

The most interesting thing about enum members is that they are
singletons.  *note EnumType: 5bf. creates them all while it is creating
the enum class itself, and then puts a custom ‘__new__()’ in place to
ensure that no new ones are ever instantiated by returning only the
existing member instances.


File: python.info,  Node: Flag Members,  Prev: Enum Members aka instances,  Up: How are Enums and Flags different?

9.5.14.4 Flag Members
.....................

Flag members can be iterated over just like the *note Flag: 5c9. class,
and only the canonical members will be returned.  For example:

     >>> list(Color)
     [<Color.RED: 1>, <Color.GREEN: 2>, <Color.BLUE: 4>]

(Note that ‘BLACK’, ‘PURPLE’, and ‘WHITE’ do not show up.)

Inverting a flag member returns the corresponding positive value, rather
than a negative value -- for example:

     >>> ~Color.RED
     <Color.GREEN|BLUE: 6>

Flag members have a length corresponding to the number of power-of-two
values they contain.  For example:

     >>> len(Color.PURPLE)
     2


File: python.info,  Node: Enum Cookbook,  Next: Subclassing EnumType,  Prev: How are Enums and Flags different?,  Up: Enum HOWTO

9.5.15 Enum Cookbook
--------------------

While *note Enum: 5d6, *note IntEnum: c86, *note StrEnum: 5c0, *note
Flag: 5c9, and *note IntFlag: 21d7. are expected to cover the majority
of use-cases, they cannot cover them all.  Here are recipes for some
different types of enumerations that can be used directly, or as
examples for creating one's own.

* Menu:

* Omitting values::
* OrderedEnum::
* DuplicateFreeEnum::
* MultiValueEnum::
* Planet::
* TimePeriod::


File: python.info,  Node: Omitting values,  Next: OrderedEnum,  Up: Enum Cookbook

9.5.15.1 Omitting values
........................

In many use-cases, one doesn't care what the actual value of an
enumeration is.  There are several ways to define this type of simple
enumeration:

   - use instances of *note auto: c43. for the value

   - use instances of *note object: a2f. as the value

   - use a descriptive string as the value

   - use a tuple as the value and a custom ‘__new__()’ to replace the
     tuple with an *note int: 23c. value

Using any of these methods signifies to the user that these values are
not important, and also enables one to add, remove, or reorder members
without having to renumber the remaining members.

* Menu:

* 使用 auto::
* 使用 object::
* Using a descriptive string::
* Using a custom __new__(): Using a custom __new__.


File: python.info,  Node: 使用 auto,  Next: 使用 object,  Up: Omitting values

9.5.15.2 使用 ‘auto’
....................

Using *note auto: c43. would look like:

     >>> class Color(Enum):
     ...     RED = auto()
     ...     BLUE = auto()
     ...     GREEN = auto()
     ...
     >>> Color.GREEN
     <Color.GREEN: 3>


File: python.info,  Node: 使用 object,  Next: Using a descriptive string,  Prev: 使用 auto,  Up: Omitting values

9.5.15.3 使用 ‘object’
......................

Using *note object: a2f. would look like:

     >>> class Color(Enum):
     ...     RED = object()
     ...     GREEN = object()
     ...     BLUE = object()
     ...
     >>> Color.GREEN
     <Color.GREEN: <object object at 0x...>>

This is also a good example of why you might want to write your own
‘__repr__()’:

     >>> class Color(Enum):
     ...     RED = object()
     ...     GREEN = object()
     ...     BLUE = object()
     ...     def __repr__(self):
     ...         return "<%s.%s>" % (self.__class__.__name__, self._name_)
     ...
     >>> Color.GREEN
     <Color.GREEN>


File: python.info,  Node: Using a descriptive string,  Next: Using a custom __new__,  Prev: 使用 object,  Up: Omitting values

9.5.15.4 Using a descriptive string
...................................

Using a string as the value would look like:

     >>> class Color(Enum):
     ...     RED = 'stop'
     ...     GREEN = 'go'
     ...     BLUE = 'too fast!'
     ...
     >>> Color.GREEN
     <Color.GREEN: 'go'>


File: python.info,  Node: Using a custom __new__,  Prev: Using a descriptive string,  Up: Omitting values

9.5.15.5 Using a custom ‘__new__()’
...................................

Using an auto-numbering ‘__new__()’ would look like:

     >>> class AutoNumber(Enum):
     ...     def __new__(cls):
     ...         value = len(cls.__members__) + 1
     ...         obj = object.__new__(cls)
     ...         obj._value_ = value
     ...         return obj
     ...
     >>> class Color(AutoNumber):
     ...     RED = ()
     ...     GREEN = ()
     ...     BLUE = ()
     ...
     >>> Color.GREEN
     <Color.GREEN: 2>

To make a more general purpose ‘AutoNumber’, add ‘*args’ to the
signature:

     >>> class AutoNumber(Enum):
     ...     def __new__(cls, *args):      # this is the only change from above
     ...         value = len(cls.__members__) + 1
     ...         obj = object.__new__(cls)
     ...         obj._value_ = value
     ...         return obj
     ...

Then when you inherit from ‘AutoNumber’ you can write your own
‘__init__’ to handle any extra arguments:

     >>> class Swatch(AutoNumber):
     ...     def __init__(self, pantone='unknown'):
     ...         self.pantone = pantone
     ...     AUBURN = '3497'
     ...     SEA_GREEN = '1246'
     ...     BLEACHED_CORAL = () # New color, no Pantone code yet!
     ...
     >>> Swatch.SEA_GREEN
     <Swatch.SEA_GREEN: 2>
     >>> Swatch.SEA_GREEN.pantone
     '1246'
     >>> Swatch.BLEACHED_CORAL.pantone
     'unknown'

     備註: The ‘__new__()’ method, if defined, is used during creation
     of the Enum members; it is then replaced by Enum's ‘__new__()’
     which is used after class creation for lookup of existing members.

     警告: 'Do not' call ‘super().__new__()’, as the lookup-only
     ‘__new__’ is the one that is found; instead, use the data type
     directly - e.g.:

          obj = int.__new__(cls, value)


File: python.info,  Node: OrderedEnum,  Next: DuplicateFreeEnum,  Prev: Omitting values,  Up: Enum Cookbook

9.5.15.6 OrderedEnum
....................

An ordered enumeration that is not based on *note IntEnum: c86. and so
maintains the normal *note Enum: 5d6. invariants (such as not being
comparable to other enumerations):

     >>> class OrderedEnum(Enum):
     ...     def __ge__(self, other):
     ...         if self.__class__ is other.__class__:
     ...             return self.value >= other.value
     ...         return NotImplemented
     ...     def __gt__(self, other):
     ...         if self.__class__ is other.__class__:
     ...             return self.value > other.value
     ...         return NotImplemented
     ...     def __le__(self, other):
     ...         if self.__class__ is other.__class__:
     ...             return self.value <= other.value
     ...         return NotImplemented
     ...     def __lt__(self, other):
     ...         if self.__class__ is other.__class__:
     ...             return self.value < other.value
     ...         return NotImplemented
     ...
     >>> class Grade(OrderedEnum):
     ...     A = 5
     ...     B = 4
     ...     C = 3
     ...     D = 2
     ...     F = 1
     ...
     >>> Grade.C < Grade.A
     True


File: python.info,  Node: DuplicateFreeEnum,  Next: MultiValueEnum,  Prev: OrderedEnum,  Up: Enum Cookbook

9.5.15.7 DuplicateFreeEnum
..........................

Raises an error if a duplicate member value is found instead of creating
an alias:

     >>> class DuplicateFreeEnum(Enum):
     ...     def __init__(self, *args):
     ...         cls = self.__class__
     ...         if any(self.value == e.value for e in cls):
     ...             a = self.name
     ...             e = cls(self.value).name
     ...             raise ValueError(
     ...                 "aliases not allowed in DuplicateFreeEnum:  %r --> %r"
     ...                 % (a, e))
     ...
     >>> class Color(DuplicateFreeEnum):
     ...     RED = 1
     ...     GREEN = 2
     ...     BLUE = 3
     ...     GRENE = 2
     ...
     Traceback (most recent call last):
       ...
     ValueError: aliases not allowed in DuplicateFreeEnum:  'GRENE' --> 'GREEN'

     備註: This is a useful example for subclassing Enum to add or
     change other behaviors as well as disallowing aliases.  If the only
     desired change is disallowing aliases, the *note unique(): 2496.
     decorator can be used instead.


File: python.info,  Node: MultiValueEnum,  Next: Planet,  Prev: DuplicateFreeEnum,  Up: Enum Cookbook

9.5.15.8 MultiValueEnum
.......................

Supports having more than one value per member:

     >>> class MultiValueEnum(Enum):
     ...     def __new__(cls, value, *values):
     ...         self = object.__new__(cls)
     ...         self._value_ = value
     ...         for v in values:
     ...             self._add_value_alias_(v)
     ...         return self
     ...
     >>> class DType(MultiValueEnum):
     ...     float32 = 'f', 8
     ...     double64 = 'd', 9
     ...
     >>> DType('f')
     <DType.float32: 'f'>
     >>> DType(9)
     <DType.double64: 'd'>


File: python.info,  Node: Planet,  Next: TimePeriod,  Prev: MultiValueEnum,  Up: Enum Cookbook

9.5.15.9 Planet
...............

If ‘__new__()’ or ‘__init__()’ is defined, the value of the enum member
will be passed to those methods:

     >>> class Planet(Enum):
     ...     MERCURY = (3.303e+23, 2.4397e6)
     ...     VENUS   = (4.869e+24, 6.0518e6)
     ...     EARTH   = (5.976e+24, 6.37814e6)
     ...     MARS    = (6.421e+23, 3.3972e6)
     ...     JUPITER = (1.9e+27,   7.1492e7)
     ...     SATURN  = (5.688e+26, 6.0268e7)
     ...     URANUS  = (8.686e+25, 2.5559e7)
     ...     NEPTUNE = (1.024e+26, 2.4746e7)
     ...     def __init__(self, mass, radius):
     ...         self.mass = mass       # in kilograms
     ...         self.radius = radius   # in meters
     ...     @property
     ...     def surface_gravity(self):
     ...         # universal gravitational constant  (m3 kg-1 s-2)
     ...         G = 6.67300E-11
     ...         return G * self.mass / (self.radius * self.radius)
     ...
     >>> Planet.EARTH.value
     (5.976e+24, 6378140.0)
     >>> Planet.EARTH.surface_gravity
     9.802652743337129


File: python.info,  Node: TimePeriod,  Prev: Planet,  Up: Enum Cookbook

9.5.15.10 TimePeriod
....................

An example to show the ‘_ignore_’ attribute in use:

     >>> from datetime import timedelta
     >>> class Period(timedelta, Enum):
     ...     "different lengths of time"
     ...     _ignore_ = 'Period i'
     ...     Period = vars()
     ...     for i in range(367):
     ...         Period['day_%d' % i] = i
     ...
     >>> list(Period)[:2]
     [<Period.day_0: datetime.timedelta(0)>, <Period.day_1: datetime.timedelta(days=1)>]
     >>> list(Period)[-2:]
     [<Period.day_365: datetime.timedelta(days=365)>, <Period.day_366: datetime.timedelta(days=366)>]


File: python.info,  Node: Subclassing EnumType,  Prev: Enum Cookbook,  Up: Enum HOWTO

9.5.16 Subclassing EnumType
---------------------------

While most enum needs can be met by customizing *note Enum: 5d6.
subclasses, either with class decorators or custom functions, *note
EnumType: 5bf. can be subclassed to provide a different Enum experience.


File: python.info,  Node: 函式編程 HOWTO,  Next: 如何使用 Logging 模組,  Prev: Enum HOWTO,  Up: Python 如何達成任務

9.6 函式編程 HOWTO
==================


作者: A. M. Kuchling


發佈版本: 0.32

In this document, we'll take a tour of Python's features suitable for
implementing programs in a functional style.  After an introduction to
the concepts of functional programming, we'll look at language features
such as *note iterator: 192.s and *note generator: 1004.s and relevant
library modules such as *note itertools: 75. and *note functools: 55.

* Menu:

* 簡介: 簡介<11>.
* Iterators::
* Generator expressions and list comprehensions::
* Generators::
* 內建函式: 內建函式<2>.
* itertools 模組::
* functools 模組::
* Small functions and the lambda expression::
* Revision History and Acknowledgements::
* References: References<2>.


File: python.info,  Node: 簡介<11>,  Next: Iterators,  Up: 函式編程 HOWTO

9.6.1 簡介
----------

This section explains the basic concept of functional programming; if
you're just interested in learning about Python language features, skip
to the next section on *note Iterators: 4d12.

Programming languages support decomposing problems in several different
ways:

   * Most programming languages are 'procedural': programs are lists of
     instructions that tell the computer what to do with the program's
     input.  C, Pascal, and even Unix shells are procedural languages.

   * In 'declarative' languages, you write a specification that
     describes the problem to be solved, and the language implementation
     figures out how to perform the computation efficiently.  SQL is the
     declarative language you're most likely to be familiar with; a SQL
     query describes the data set you want to retrieve, and the SQL
     engine decides whether to scan tables or use indexes, which
     subclauses should be performed first, etc.

   * 'Object-oriented' programs manipulate collections of objects.
     Objects have internal state and support methods that query or
     modify this internal state in some way.  Smalltalk and Java are
     object-oriented languages.  C++ and Python are languages that
     support object-oriented programming, but don't force the use of
     object-oriented features.

   * 'Functional' programming decomposes a problem into a set of
     functions.  Ideally, functions only take inputs and produce
     outputs, and don't have any internal state that affects the output
     produced for a given input.  Well-known functional languages
     include the ML family (Standard ML, OCaml, and other variants) and
     Haskell.

The designers of some computer languages choose to emphasize one
particular approach to programming.  This often makes it difficult to
write programs that use a different approach.  Other languages are
multi-paradigm languages that support several different approaches.
Lisp, C++, and Python are multi-paradigm; you can write programs or
libraries that are largely procedural, object-oriented, or functional in
all of these languages.  In a large program, different sections might be
written using different approaches; the GUI might be object-oriented
while the processing logic is procedural or functional, for example.

In a functional program, input flows through a set of functions.  Each
function operates on its input and produces some output.  Functional
style discourages functions with side effects that modify internal state
or make other changes that aren't visible in the function's return
value.  Functions that have no side effects at all are called 'purely
functional'.  Avoiding side effects means not using data structures that
get updated as a program runs; every function's output must only depend
on its input.

Some languages are very strict about purity and don't even have
assignment statements such as ‘a=3’ or ‘c = a + b’, but it's difficult
to avoid all side effects, such as printing to the screen or writing to
a disk file.  Another example is a call to the *note print(): f18. or
*note time.sleep(): 642. function, neither of which returns a useful
value.  Both are called only for their side effects of sending some text
to the screen or pausing execution for a second.

Python programs written in functional style usually won't go to the
extreme of avoiding all I/O or all assignments; instead, they'll provide
a functional-appearing interface but will use non-functional features
internally.  For example, the implementation of a function will still
use assignments to local variables, but won't modify global variables or
have other side effects.

Functional programming can be considered the opposite of object-oriented
programming.  Objects are little capsules containing some internal state
along with a collection of method calls that let you modify this state,
and programs consist of making the right set of state changes.
Functional programming wants to avoid state changes as much as possible
and works with data flowing between functions.  In Python you might
combine the two approaches by writing functions that take and return
instances representing objects in your application (e-mail messages,
transactions, etc.).

Functional design may seem like an odd constraint to work under.  Why
should you avoid objects and side effects?  There are theoretical and
practical advantages to the functional style:

   * Formal provability.

   * Modularity.

   * Composability.

   * Ease of debugging and testing.

* Menu:

* Formal provability::
* Modularity::
* Ease of debugging and testing::
* Composability::


File: python.info,  Node: Formal provability,  Next: Modularity,  Up: 簡介<11>

9.6.1.1 Formal provability
..........................

A theoretical benefit is that it's easier to construct a mathematical
proof that a functional program is correct.

For a long time researchers have been interested in finding ways to
mathematically prove programs correct.  This is different from testing a
program on numerous inputs and concluding that its output is usually
correct, or reading a program's source code and concluding that the code
looks right; the goal is instead a rigorous proof that a program
produces the right result for all possible inputs.

The technique used to prove programs correct is to write down
'invariants', properties of the input data and of the program's
variables that are always true.  For each line of code, you then show
that if invariants X and Y are true 'before' the line is executed, the
slightly different invariants X' and Y' are true 'after' the line is
executed.  This continues until you reach the end of the program, at
which point the invariants should match the desired conditions on the
program's output.

Functional programming's avoidance of assignments arose because
assignments are difficult to handle with this technique; assignments can
break invariants that were true before the assignment without producing
any new invariants that can be propagated onward.

Unfortunately, proving programs correct is largely impractical and not
relevant to Python software.  Even trivial programs require proofs that
are several pages long; the proof of correctness for a moderately
complicated program would be enormous, and few or none of the programs
you use daily (the Python interpreter, your XML parser, your web
browser) could be proven correct.  Even if you wrote down or generated a
proof, there would then be the question of verifying the proof; maybe
there's an error in it, and you wrongly believe you've proved the
program correct.


File: python.info,  Node: Modularity,  Next: Ease of debugging and testing,  Prev: Formal provability,  Up: 簡介<11>

9.6.1.2 Modularity
..................

A more practical benefit of functional programming is that it forces you
to break apart your problem into small pieces.  Programs are more
modular as a result.  It's easier to specify and write a small function
that does one thing than a large function that performs a complicated
transformation.  Small functions are also easier to read and to check
for errors.


File: python.info,  Node: Ease of debugging and testing,  Next: Composability,  Prev: Modularity,  Up: 簡介<11>

9.6.1.3 Ease of debugging and testing
.....................................

Testing and debugging a functional-style program is easier.

Debugging is simplified because functions are generally small and
clearly specified.  When a program doesn't work, each function is an
interface point where you can check that the data are correct.  You can
look at the intermediate inputs and outputs to quickly isolate the
function that's responsible for a bug.

Testing is easier because each function is a potential subject for a
unit test.  Functions don't depend on system state that needs to be
replicated before running a test; instead you only have to synthesize
the right input and then check that the output matches expectations.


File: python.info,  Node: Composability,  Prev: Ease of debugging and testing,  Up: 簡介<11>

9.6.1.4 Composability
.....................

As you work on a functional-style program, you'll write a number of
functions with varying inputs and outputs.  Some of these functions will
be unavoidably specialized to a particular application, but others will
be useful in a wide variety of programs.  For example, a function that
takes a directory path and returns all the XML files in the directory,
or a function that takes a filename and returns its contents, can be
applied to many different situations.

Over time you'll form a personal library of utilities.  Often you'll
assemble new programs by arranging existing functions in a new
configuration and writing a few functions specialized for the current
task.


File: python.info,  Node: Iterators,  Next: Generator expressions and list comprehensions,  Prev: 簡介<11>,  Up: 函式編程 HOWTO

9.6.2 Iterators
---------------

I'll start by looking at a Python language feature that's an important
foundation for writing functional-style programs: iterators.

An iterator is an object representing a stream of data; this object
returns the data one element at a time.  A Python iterator must support
a method called *note __next__(): 1260. that takes no arguments and
always returns the next element of the stream.  If there are no more
elements in the stream, *note __next__(): 1260. must raise the *note
StopIteration: ba1. exception.  Iterators don't have to be finite,
though; it's perfectly reasonable to write an iterator that produces an
infinite stream of data.

The built-in *note iter(): 77b. function takes an arbitrary object and
tries to return an iterator that will return the object's contents or
elements, raising *note TypeError: 4dd. if the object doesn't support
iteration.  Several of Python's built-in data types support iteration,
the most common being lists and dictionaries.  An object is called *note
iterable: 11bf. if you can get an iterator for it.

You can experiment with the iteration interface manually:

     >>> L = [1, 2, 3]
     >>> it = iter(L)
     >>> it
     <...iterator object at ...>
     >>> it.__next__()  # same as next(it)
     1
     >>> next(it)
     2
     >>> next(it)
     3
     >>> next(it)
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     StopIteration
     >>>

Python expects iterable objects in several different contexts, the most
important being the *note for: 2c3. statement.  In the statement ‘for X
in Y’, Y must be an iterator or some object for which *note iter(): 77b.
can create an iterator.  These two statements are equivalent:

     for i in iter(obj):
         print(i)

     for i in obj:
         print(i)

Iterators can be materialized as lists or tuples by using the *note
list(): 5b6. or *note tuple(): 322. constructor functions:

     >>> L = [1, 2, 3]
     >>> iterator = iter(L)
     >>> t = tuple(iterator)
     >>> t
     (1, 2, 3)

Sequence unpacking also supports iterators: if you know an iterator will
return N elements, you can unpack them into an N-tuple:

     >>> L = [1, 2, 3]
     >>> iterator = iter(L)
     >>> a, b, c = iterator
     >>> a, b, c
     (1, 2, 3)

Built-in functions such as *note max(): ead. and *note min(): eac. can
take a single iterator argument and will return the largest or smallest
element.  The ‘"in"’ and ‘"not in"’ operators also support iterators: ‘X
in iterator’ is true if X is found in the stream returned by the
iterator.  You'll run into obvious problems if the iterator is infinite;
*note max(): ead, *note min(): eac. will never return, and if the
element X never appears in the stream, the ‘"in"’ and ‘"not in"’
operators won't return either.

Note that you can only go forward in an iterator; there's no way to get
the previous element, reset the iterator, or make a copy of it.
Iterator objects can optionally provide these additional capabilities,
but the iterator protocol only specifies the *note __next__(): 1260.
method.  Functions may therefore consume all of the iterator's output,
and if you need to do something different with the same stream, you'll
have to create a new iterator.

* Menu:

* Data Types That Support Iterators::


File: python.info,  Node: Data Types That Support Iterators,  Up: Iterators

9.6.2.1 Data Types That Support Iterators
.........................................

We've already seen how lists and tuples support iterators.  In fact, any
Python sequence type, such as strings, will automatically support
creation of an iterator.

Calling *note iter(): 77b. on a dictionary returns an iterator that will
loop over the dictionary's keys:

     >>> m = {'Jan': 1, 'Feb': 2, 'Mar': 3, 'Apr': 4, 'May': 5, 'Jun': 6,
     ...      'Jul': 7, 'Aug': 8, 'Sep': 9, 'Oct': 10, 'Nov': 11, 'Dec': 12}
     >>> for key in m:
     ...     print(key, m[key])
     Jan 1
     Feb 2
     Mar 3
     Apr 4
     May 5
     Jun 6
     Jul 7
     Aug 8
     Sep 9
     Oct 10
     Nov 11
     Dec 12

Note that starting with Python 3.7, dictionary iteration order is
guaranteed to be the same as the insertion order.  In earlier versions,
the behaviour was unspecified and could vary between implementations.

Applying *note iter(): 77b. to a dictionary always loops over the keys,
but dictionaries have methods that return other iterators.  If you want
to iterate over values or key/value pairs, you can explicitly call the
*note values(): 772. or *note items(): 773. methods to get an
appropriate iterator.

The *note dict(): 23b. constructor can accept an iterator that returns a
finite stream of ‘(key, value)’ tuples:

     >>> L = [('Italy', 'Rome'), ('France', 'Paris'), ('US', 'Washington DC')]
     >>> dict(iter(L))
     {'Italy': 'Rome', 'France': 'Paris', 'US': 'Washington DC'}

Files also support iteration by calling the *note readline(): 1bc0.
method until there are no more lines in the file.  This means you can
read each line of a file like this:

     for line in file:
         # do something for each line
         ...

Sets can take their contents from an iterable and let you iterate over
the set's elements:

     >>> S = {2, 3, 5, 7, 11, 13}
     >>> for i in S:
     ...     print(i)
     2
     3
     5
     7
     11
     13


File: python.info,  Node: Generator expressions and list comprehensions,  Next: Generators,  Prev: Iterators,  Up: 函式編程 HOWTO

9.6.3 Generator expressions and list comprehensions
---------------------------------------------------

Two common operations on an iterator's output are 1) performing some
operation for every element, 2) selecting a subset of elements that meet
some condition.  For example, given a list of strings, you might want to
strip off trailing whitespace from each line or extract all the strings
containing a given substring.

List comprehensions and generator expressions (short form: "listcomps"
and "genexps") are a concise notation for such operations, borrowed from
the functional programming language Haskell
(‘https://www.haskell.org/’).  You can strip all the whitespace from a
stream of strings with the following code:

     >>> line_list = ['  line 1\n', 'line 2  \n', ' \n', '']

     >>> # Generator expression -- returns iterator
     >>> stripped_iter = (line.strip() for line in line_list)

     >>> # List comprehension -- returns list
     >>> stripped_list = [line.strip() for line in line_list]

You can select only certain elements by adding an ‘"if"’ condition:

     >>> stripped_list = [line.strip() for line in line_list
     ...                  if line != ""]

With a list comprehension, you get back a Python list; ‘stripped_list’
is a list containing the resulting lines, not an iterator.  Generator
expressions return an iterator that computes the values as necessary,
not needing to materialize all the values at once.  This means that list
comprehensions aren't useful if you're working with iterators that
return an infinite stream or a very large amount of data.  Generator
expressions are preferable in these situations.

Generator expressions are surrounded by parentheses ("()") and list
comprehensions are surrounded by square brackets ("[]").  Generator
expressions have the form:

     ( expression for expr in sequence1
                  if condition1
                  for expr2 in sequence2
                  if condition2
                  for expr3 in sequence3
                  ...
                  if condition3
                  for exprN in sequenceN
                  if conditionN )

Again, for a list comprehension only the outside brackets are different
(square brackets instead of parentheses).

The elements of the generated output will be the successive values of
‘expression’.  The ‘if’ clauses are all optional; if present,
‘expression’ is only evaluated and added to the result when ‘condition’
is true.

Generator expressions always have to be written inside parentheses, but
the parentheses signalling a function call also count.  If you want to
create an iterator that will be immediately passed to a function you can
write:

     obj_total = sum(obj.count for obj in list_all_objects())

The ‘for...in’ clauses contain the sequences to be iterated over.  The
sequences do not have to be the same length, because they are iterated
over from left to right, 'not' in parallel.  For each element in
‘sequence1’, ‘sequence2’ is looped over from the beginning.  ‘sequence3’
is then looped over for each resulting pair of elements from ‘sequence1’
and ‘sequence2’.

To put it another way, a list comprehension or generator expression is
equivalent to the following Python code:

     for expr1 in sequence1:
         if not (condition1):
             continue   # Skip this element
         for expr2 in sequence2:
             if not (condition2):
                 continue   # Skip this element
             ...
             for exprN in sequenceN:
                 if not (conditionN):
                     continue   # Skip this element

                 # Output the value of
                 # the expression.

This means that when there are multiple ‘for...in’ clauses but no ‘if’
clauses, the length of the resulting output will be equal to the product
of the lengths of all the sequences.  If you have two lists of length 3,
the output list is 9 elements long:

     >>> seq1 = 'abc'
     >>> seq2 = (1, 2, 3)
     >>> [(x, y) for x in seq1 for y in seq2]
     [('a', 1), ('a', 2), ('a', 3),
      ('b', 1), ('b', 2), ('b', 3),
      ('c', 1), ('c', 2), ('c', 3)]

To avoid introducing an ambiguity into Python's grammar, if ‘expression’
is creating a tuple, it must be surrounded with parentheses.  The first
list comprehension below is a syntax error, while the second one is
correct:

     # 語法錯誤
     [x, y for x in seq1 for y in seq2]
     # 正確
     [(x, y) for x in seq1 for y in seq2]


File: python.info,  Node: Generators,  Next: 內建函式<2>,  Prev: Generator expressions and list comprehensions,  Up: 函式編程 HOWTO

9.6.4 Generators
----------------

Generators are a special class of functions that simplify the task of
writing iterators.  Regular functions compute a value and return it, but
generators return an iterator that returns a stream of values.

You're doubtless familiar with how regular function calls work in Python
or C. When you call a function, it gets a private namespace where its
local variables are created.  When the function reaches a ‘return’
statement, the local variables are destroyed and the value is returned
to the caller.  A later call to the same function creates a new private
namespace and a fresh set of local variables.  But, what if the local
variables weren't thrown away on exiting a function?  What if you could
later resume the function where it left off?  This is what generators
provide; they can be thought of as resumable functions.

Here's the simplest example of a generator function:

     >>> def generate_ints(N):
     ...    for i in range(N):
     ...        yield i

Any function containing a *note yield: 971. keyword is a generator
function; this is detected by Python's *note bytecode: 16d. compiler
which compiles the function specially as a result.

When you call a generator function, it doesn't return a single value;
instead it returns a generator object that supports the iterator
protocol.  On executing the ‘yield’ expression, the generator outputs
the value of ‘i’, similar to a ‘return’ statement.  The big difference
between ‘yield’ and a ‘return’ statement is that on reaching a ‘yield’
the generator's state of execution is suspended and local variables are
preserved.  On the next call to the generator's *note __next__(): 1bc8.
method, the function will resume executing.

Here's a sample usage of the ‘generate_ints()’ generator:

     >>> gen = generate_ints(3)
     >>> gen
     <generator object generate_ints at ...>
     >>> next(gen)
     0
     >>> next(gen)
     1
     >>> next(gen)
     2
     >>> next(gen)
     Traceback (most recent call last):
       File "stdin", line 1, in <module>
       File "stdin", line 2, in generate_ints
     StopIteration

You could equally write ‘for i in generate_ints(5)’, or ‘a, b, c =
generate_ints(3)’.

Inside a generator function, ‘return value’ causes
‘StopIteration(value)’ to be raised from the *note __next__(): 1bc8.
method.  Once this happens, or the bottom of the function is reached,
the procession of values ends and the generator cannot yield any further
values.

You could achieve the effect of generators manually by writing your own
class and storing all the local variables of the generator as instance
variables.  For example, returning a list of integers could be done by
setting ‘self.count’ to 0, and having the *note __next__(): 1260. method
increment ‘self.count’ and return it.  However, for a moderately
complicated generator, writing a corresponding class can be much
messier.

The test suite included with Python's library,
Lib/test/test_generators.py(1), contains a number of more interesting
examples.  Here's one generator that implements an in-order traversal of
a tree using generators recursively.

     # A recursive generator that generates Tree leaves in in-order.
     def inorder(t):
         if t:
             for x in inorder(t.left):
                 yield x

             yield t.label

             for x in inorder(t.right):
                 yield x

Two other examples in ‘test_generators.py’ produce solutions for the
N-Queens problem (placing N queens on an NxN chess board so that no
queen threatens another) and the Knight's Tour (finding a route that
takes a knight to every square of an NxN chessboard without visiting any
square twice).

* Menu:

* Passing values into a generator::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.13/Lib/test/test_generators.py


File: python.info,  Node: Passing values into a generator,  Up: Generators

9.6.4.1 Passing values into a generator
.......................................

In Python 2.4 and earlier, generators only produced output.  Once a
generator's code was invoked to create an iterator, there was no way to
pass any new information into the function when its execution is
resumed.  You could hack together this ability by making the generator
look at a global variable or by passing in some mutable object that
callers then modify, but these approaches are messy.

In Python 2.5 there's a simple way to pass values into a generator.
*note yield: 971. became an expression, returning a value that can be
assigned to a variable or otherwise operated on:

     val = (yield i)

I recommend that you 'always' put parentheses around a ‘yield’
expression when you're doing something with the returned value, as in
the above example.  The parentheses aren't always necessary, but it's
easier to always add them instead of having to remember when they're
needed.

( PEP 342(1) explains the exact rules, which are that a
‘yield’-expression must always be parenthesized except when it occurs at
the top-level expression on the right-hand side of an assignment.  This
means you can write ‘val = yield i’ but have to use parentheses when
there's an operation, as in ‘val = (yield i) + 12’.)

Values are sent into a generator by calling its *note send(value): 1ea2.
method.  This method resumes the generator's code and the ‘yield’
expression returns the specified value.  If the regular *note
__next__(): 1bc8. method is called, the ‘yield’ returns ‘None’.

Here's a simple counter that increments by 1 and allows changing the
value of the internal counter.

     def counter(maximum):
         i = 0
         while i < maximum:
             val = (yield i)
             # If value provided, change counter
             if val is not None:
                 i = val
             else:
                 i += 1

And here's an example of changing the counter:

     >>> it = counter(10)
     >>> next(it)
     0
     >>> next(it)
     1
     >>> it.send(8)
     8
     >>> next(it)
     9
     >>> next(it)
     Traceback (most recent call last):
       File "t.py", line 15, in <module>
         it.next()
     StopIteration

Because ‘yield’ will often be returning ‘None’, you should always check
for this case.  Don't just use its value in expressions unless you're
sure that the *note send(): 1ea2. method will be the only method used to
resume your generator function.

In addition to *note send(): 1ea2, there are two other methods on
generators:

   * *note throw(value): 4a0. is used to raise an exception inside the
     generator; the exception is raised by the ‘yield’ expression where
     the generator's execution is paused.

   * *note close(): 15ee. raises a *note GeneratorExit: 1335. exception
     inside the generator to terminate the iteration.  On receiving this
     exception, the generator's code must either raise *note
     GeneratorExit: 1335. or *note StopIteration: ba1.; catching the
     exception and doing anything else is illegal and will trigger a
     *note RuntimeError: 179.  *note close(): 15ee. will also be called
     by Python's garbage collector when the generator is
     garbage-collected.

     If you need to run cleanup code when a *note GeneratorExit: 1335.
     occurs, I suggest using a ‘try: ... finally:’ suite instead of
     catching *note GeneratorExit: 1335.

The cumulative effect of these changes is to turn generators from
one-way producers of information into both producers and consumers.

Generators also become 'coroutines', a more generalized form of
subroutines.  Subroutines are entered at one point and exited at another
point (the top of the function, and a ‘return’ statement), but
coroutines can be entered, exited, and resumed at many different points
(the ‘yield’ statements).

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0342/


File: python.info,  Node: 內建函式<2>,  Next: itertools 模組,  Prev: Generators,  Up: 函式編程 HOWTO

9.6.5 內建函式
--------------

Let's look in more detail at built-in functions often used with
iterators.

Two of Python's built-in functions, *note map(): 808. and *note
filter(): 809. duplicate the features of generator expressions:

*note map(f, iterA, iterB, ...): 808. returns an iterator over the sequence

     ‘f(iterA[0], iterB[0]), f(iterA[1], iterB[1]), f(iterA[2],
     iterB[2]), ...’.

          >>> def upper(s):
          ...     return s.upper()

          >>> list(map(upper, ['sentence', 'fragment']))
          ['SENTENCE', 'FRAGMENT']
          >>> [upper(s) for s in ['sentence', 'fragment']]
          ['SENTENCE', 'FRAGMENT']

You can of course achieve the same effect with a list comprehension.

*note filter(predicate, iter): 809. returns an iterator over all the
sequence elements that meet a certain condition, and is similarly
duplicated by list comprehensions.  A 'predicate' is a function that
returns the truth value of some condition; for use with *note filter():
809, the predicate must take a single value.

     >>> def is_even(x):
     ...     return (x % 2) == 0

     >>> list(filter(is_even, range(10)))
     [0, 2, 4, 6, 8]

This can also be written as a list comprehension:

     >>> list(x for x in range(10) if is_even(x))
     [0, 2, 4, 6, 8]

*note enumerate(iter, start=0): 13ea. counts off the elements in the
iterable returning 2-tuples containing the count (from 'start') and each
element.

     >>> for item in enumerate(['subject', 'verb', 'object']):
     ...     print(item)
     (0, 'subject')
     (1, 'verb')
     (2, 'object')

*note enumerate(): 13ea. is often used when looping through a list and
recording the indexes at which certain conditions are met:

     f = open('data.txt', 'r')
     for i, line in enumerate(f):
         if line.strip() == '':
             print('Blank line at line #%i' % i)

*note sorted(iterable, key=None, reverse=False): b75. collects all the
elements of the iterable into a list, sorts the list, and returns the
sorted result.  The 'key' and 'reverse' arguments are passed through to
the constructed list's *note sort(): b76. method.

     >>> import random
     >>> # Generate 8 random numbers between [0, 10000)
     >>> rand_list = random.sample(range(10000), 8)
     >>> rand_list
     [769, 7953, 9828, 6431, 8442, 9878, 6213, 2207]
     >>> sorted(rand_list)
     [769, 2207, 6213, 6431, 7953, 8442, 9828, 9878]
     >>> sorted(rand_list, reverse=True)
     [9878, 9828, 8442, 7953, 6431, 6213, 2207, 769]

(For a more detailed discussion of sorting, see the *note 排序技法:
205a.)

The *note any(iter): 138e. and *note all(iter): 138f. built-ins look at
the truth values of an iterable's contents.  *note any(): 138e. returns
‘True’ if any element in the iterable is a true value, and *note all():
138f. returns ‘True’ if all of the elements are true values:

     >>> any([0, 1, 0])
     True
     >>> any([0, 0, 0])
     False
     >>> any([1, 1, 1])
     True
     >>> all([0, 1, 0])
     False
     >>> all([0, 0, 0])
     False
     >>> all([1, 1, 1])
     True

*note zip(iterA, iterB, ...): 774. takes one element from each iterable
and returns them in a tuple:

     zip(['a', 'b', 'c'], (1, 2, 3)) =>
       ('a', 1), ('b', 2), ('c', 3)

It doesn't construct an in-memory list and exhaust all the input
iterators before returning; instead tuples are constructed and returned
only if they're requested.  (The technical term for this behaviour is
lazy evaluation(1).)

This iterator is intended to be used with iterables that are all of the
same length.  If the iterables are of different lengths, the resulting
stream will be the same length as the shortest iterable.

     zip(['a', 'b'], (1, 2, 3)) =>
       ('a', 1), ('b', 2)

You should avoid doing this, though, because an element may be taken
from the longer iterators and discarded.  This means you can't go on to
use the iterators further because you risk skipping a discarded element.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Lazy_evaluation


File: python.info,  Node: itertools 模組,  Next: functools 模組,  Prev: 內建函式<2>,  Up: 函式編程 HOWTO

9.6.6 itertools 模組
--------------------

The *note itertools: 75. module contains a number of commonly used
iterators as well as functions for combining several iterators.  This
section will introduce the module's contents by showing small examples.

The module's functions fall into a few broad classes:

   * Functions that create a new iterator based on an existing iterator.

   * Functions for treating an iterator's elements as function
     arguments.

   * Functions for selecting portions of an iterator's output.

   * A function for grouping an iterator's output.

* Menu:

* 建立新的疊代器::
* Calling functions on elements::
* Selecting elements::
* Combinatoric functions::
* Grouping elements::


File: python.info,  Node: 建立新的疊代器,  Next: Calling functions on elements,  Up: itertools 模組

9.6.6.1 建立新的疊代器
......................

*note itertools.count(start, step): 121b. returns an infinite stream of
evenly spaced values.  You can optionally supply the starting number,
which defaults to 0, and the interval between numbers, which defaults to
1:

     itertools.count() =>
       0, 1, 2, 3, 4, 5, 6, 7, 8, 9, ...
     itertools.count(10) =>
       10, 11, 12, 13, 14, 15, 16, 17, 18, 19, ...
     itertools.count(10, 5) =>
       10, 15, 20, 25, 30, 35, 40, 45, 50, 55, ...

*note itertools.cycle(iter): 2607. saves a copy of the contents of a
provided iterable and returns a new iterator that returns its elements
from first to last.  The new iterator will repeat these elements
infinitely.

     itertools.cycle([1, 2, 3, 4, 5]) =>
       1, 2, 3, 4, 5, 1, 2, 3, 4, 5, ...

*note itertools.repeat(elem, [n]): 2608. returns the provided element
'n' times, or returns the element endlessly if 'n' is not provided.

     itertools.repeat('abc') =>
       abc, abc, abc, abc, abc, abc, abc, abc, abc, abc, ...
     itertools.repeat('abc', 5) =>
       abc, abc, abc, abc, abc

*note itertools.chain(iterA, iterB, ...): 205b. takes an arbitrary
number of iterables as input, and returns all the elements of the first
iterator, then all the elements of the second, and so on, until all of
the iterables have been exhausted.

     itertools.chain(['a', 'b', 'c'], (1, 2, 3)) =>
       a, b, c, 1, 2, 3

*note itertools.islice(iter, [start], stop, [step]): af0. returns a
stream that's a slice of the iterator.  With a single 'stop' argument,
it will return the first 'stop' elements.  If you supply a starting
index, you'll get 'stop-start' elements, and if you supply a value for
'step', elements will be skipped accordingly.  Unlike Python's string
and list slicing, you can't use negative values for 'start', 'stop', or
'step'.

     itertools.islice(range(10), 8) =>
       0, 1, 2, 3, 4, 5, 6, 7
     itertools.islice(range(10), 2, 8) =>
       2, 3, 4, 5, 6, 7
     itertools.islice(range(10), 2, 8, 2) =>
       2, 4, 6

*note itertools.tee(iter, [n]): 260d. replicates an iterator; it returns
'n' independent iterators that will all return the contents of the
source iterator.  If you don't supply a value for 'n', the default is 2.
Replicating iterators requires saving some of the contents of the source
iterator, so this can consume significant memory if the iterator is
large and one of the new iterators is consumed more than the others.

     itertools.tee( itertools.count() ) =>
        iterA, iterB

     where iterA ->
        0, 1, 2, 3, 4, 5, 6, 7, 8, 9, ...

     and   iterB ->
        0, 1, 2, 3, 4, 5, 6, 7, 8, 9, ...


File: python.info,  Node: Calling functions on elements,  Next: Selecting elements,  Prev: 建立新的疊代器,  Up: itertools 模組

9.6.6.2 Calling functions on elements
.....................................

The *note operator: 8f. module contains a set of functions corresponding
to Python's operators.  Some examples are *note operator.add(a, b):
2630. (adds two values), *note operator.ne(a, b): 2620. (same as ‘a !=
b’), and *note operator.attrgetter('id'): dd9. (returns a callable that
fetches the ‘.id’ attribute).

*note itertools.starmap(func, iter): 107d. assumes that the iterable
will return a stream of tuples, and calls 'func' using these tuples as
the arguments:

     itertools.starmap(os.path.join,
                       [('/bin', 'python'), ('/usr', 'bin', 'java'),
                        ('/usr', 'bin', 'perl'), ('/usr', 'bin', 'ruby')])
     =>
       /bin/python, /usr/bin/java, /usr/bin/perl, /usr/bin/ruby


File: python.info,  Node: Selecting elements,  Next: Combinatoric functions,  Prev: Calling functions on elements,  Up: itertools 模組

9.6.6.3 Selecting elements
..........................

Another group of functions chooses a subset of an iterator's elements
based on a predicate.

*note itertools.filterfalse(predicate, iter): 2042. is the opposite of
*note filter(): 809, returning all elements for which the predicate
returns false:

     itertools.filterfalse(is_even, itertools.count()) =>
       1, 3, 5, 7, 9, 11, 13, 15, ...

*note itertools.takewhile(predicate, iter): 260c. returns elements for
as long as the predicate returns true.  Once the predicate returns
false, the iterator will signal the end of its results.

     def less_than_10(x):
         return x < 10

     itertools.takewhile(less_than_10, itertools.count()) =>
       0, 1, 2, 3, 4, 5, 6, 7, 8, 9

     itertools.takewhile(is_even, itertools.count()) =>
       0

*note itertools.dropwhile(predicate, iter): 260a. discards elements
while the predicate returns true, and then returns the rest of the
iterable's results.

     itertools.dropwhile(less_than_10, itertools.count()) =>
       10, 11, 12, 13, 14, 15, 16, 17, 18, 19, ...

     itertools.dropwhile(is_even, itertools.count()) =>
       1, 2, 3, 4, 5, 6, 7, 8, 9, 10, ...

*note itertools.compress(data, selectors): 121a. takes two iterators and
returns only those elements of 'data' for which the corresponding
element of 'selectors' is true, stopping whenever either one is
exhausted:

     itertools.compress([1, 2, 3, 4, 5], [True, True, False, False, True]) =>
        1, 2, 5


File: python.info,  Node: Combinatoric functions,  Next: Grouping elements,  Prev: Selecting elements,  Up: itertools 模組

9.6.6.4 Combinatoric functions
..............................

The *note itertools.combinations(iterable, r): 12a6. returns an iterator
giving all possible 'r'-tuple combinations of the elements contained in
'iterable'.

     itertools.combinations([1, 2, 3, 4, 5], 2) =>
       (1, 2), (1, 3), (1, 4), (1, 5),
       (2, 3), (2, 4), (2, 5),
       (3, 4), (3, 5),
       (4, 5)

     itertools.combinations([1, 2, 3, 4, 5], 3) =>
       (1, 2, 3), (1, 2, 4), (1, 2, 5), (1, 3, 4), (1, 3, 5), (1, 4, 5),
       (2, 3, 4), (2, 3, 5), (2, 4, 5),
       (3, 4, 5)

The elements within each tuple remain in the same order as 'iterable'
returned them.  For example, the number 1 is always before 2, 3, 4, or 5
in the examples above.  A similar function, *note
itertools.permutations(iterable, r=None): 181d, removes this constraint
on the order, returning all possible arrangements of length 'r':

     itertools.permutations([1, 2, 3, 4, 5], 2) =>
       (1, 2), (1, 3), (1, 4), (1, 5),
       (2, 1), (2, 3), (2, 4), (2, 5),
       (3, 1), (3, 2), (3, 4), (3, 5),
       (4, 1), (4, 2), (4, 3), (4, 5),
       (5, 1), (5, 2), (5, 3), (5, 4)

     itertools.permutations([1, 2, 3, 4, 5]) =>
       (1, 2, 3, 4, 5), (1, 2, 3, 5, 4), (1, 2, 4, 3, 5),
       ...
       (5, 4, 3, 2, 1)

If you don't supply a value for 'r' the length of the iterable is used,
meaning that all the elements are permuted.

Note that these functions produce all of the possible combinations by
position and don't require that the contents of 'iterable' are unique:

     itertools.permutations('aba', 3) =>
       ('a', 'b', 'a'), ('a', 'a', 'b'), ('b', 'a', 'a'),
       ('b', 'a', 'a'), ('a', 'a', 'b'), ('a', 'b', 'a')

The identical tuple ‘('a', 'a', 'b')’ occurs twice, but the two 'a'
strings came from different positions.

The *note itertools.combinations_with_replacement(iterable, r): 1219.
function relaxes a different constraint: elements can be repeated within
a single tuple.  Conceptually an element is selected for the first
position of each tuple and then is replaced before the second element is
selected.

     itertools.combinations_with_replacement([1, 2, 3, 4, 5], 2) =>
       (1, 1), (1, 2), (1, 3), (1, 4), (1, 5),
       (2, 2), (2, 3), (2, 4), (2, 5),
       (3, 3), (3, 4), (3, 5),
       (4, 4), (4, 5),
       (5, 5)


File: python.info,  Node: Grouping elements,  Prev: Combinatoric functions,  Up: itertools 模組

9.6.6.5 Grouping elements
.........................

The last function I'll discuss, *note itertools.groupby(iter,
key_func=None): 260b, is the most complicated.  ‘key_func(elem)’ is a
function that can compute a key value for each element returned by the
iterable.  If you don't supply a key function, the key is simply each
element itself.

*note groupby(): 260b. collects all the consecutive elements from the
underlying iterable that have the same key value, and returns a stream
of 2-tuples containing a key value and an iterator for the elements with
that key.

     city_list = [('Decatur', 'AL'), ('Huntsville', 'AL'), ('Selma', 'AL'),
                  ('Anchorage', 'AK'), ('Nome', 'AK'),
                  ('Flagstaff', 'AZ'), ('Phoenix', 'AZ'), ('Tucson', 'AZ'),
                  ...
                 ]

     def get_state(city_state):
         return city_state[1]

     itertools.groupby(city_list, get_state) =>
       ('AL', iterator-1),
       ('AK', iterator-2),
       ('AZ', iterator-3), ...

     where
     iterator-1 =>
       ('Decatur', 'AL'), ('Huntsville', 'AL'), ('Selma', 'AL')
     iterator-2 =>
       ('Anchorage', 'AK'), ('Nome', 'AK')
     iterator-3 =>
       ('Flagstaff', 'AZ'), ('Phoenix', 'AZ'), ('Tucson', 'AZ')

*note groupby(): 260b. assumes that the underlying iterable's contents
will already be sorted based on the key.  Note that the returned
iterators also use the underlying iterable, so you have to consume the
results of iterator-1 before requesting iterator-2 and its corresponding
key.


File: python.info,  Node: functools 模組,  Next: Small functions and the lambda expression,  Prev: itertools 模組,  Up: 函式編程 HOWTO

9.6.7 functools 模組
--------------------

The *note functools: 55. module contains some higher-order functions.  A
'higher-order function' takes one or more functions as input and returns
a new function.  The most useful tool in this module is the *note
functools.partial(): 356. function.

For programs written in a functional style, you'll sometimes want to
construct variants of existing functions that have some of the
parameters filled in.  Consider a Python function ‘f(a, b, c)’; you may
wish to create a new function ‘g(b, c)’ that's equivalent to ‘f(1, b,
c)’; you're filling in a value for one of ‘f()’'s parameters.  This is
called "partial function application".

The constructor for *note partial(): 356. takes the arguments
‘(function, arg1, arg2, ..., kwarg1=value1, kwarg2=value2)’.  The
resulting object is callable, so you can just call it to invoke
‘function’ with the filled-in arguments.

以下是個很小但實際的範例：

     import functools

     def log(message, subsystem):
         """Write the contents of 'message' to the specified subsystem."""
         print('%s: %s' % (subsystem, message))
         ...

     server_log = functools.partial(log, subsystem='server')
     server_log('Unable to open socket')

*note functools.reduce(func, iter, [initial_value]): 126f. cumulatively
performs an operation on all the iterable's elements and, therefore,
can't be applied to infinite iterables.  'func' must be a function that
takes two elements and returns a single value.  *note
functools.reduce(): 126f. takes the first two elements A and B returned
by the iterator and calculates ‘func(A, B)’.  It then requests the third
element, C, calculates ‘func(func(A, B), C)’, combines this result with
the fourth element returned, and continues until the iterable is
exhausted.  If the iterable returns no values at all, a *note TypeError:
4dd. exception is raised.  If the initial value is supplied, it's used
as a starting point and ‘func(initial_value, A)’ is the first
calculation.

     >>> import operator, functools
     >>> functools.reduce(operator.concat, ['A', 'BB', 'C'])
     'ABBC'
     >>> functools.reduce(operator.concat, [])
     Traceback (most recent call last):
       ...
     TypeError: reduce() of empty sequence with no initial value
     >>> functools.reduce(operator.mul, [1, 2, 3], 1)
     6
     >>> functools.reduce(operator.mul, [], 1)
     1

If you use *note operator.add(): 2630. with *note functools.reduce():
126f, you'll add up all the elements of the iterable.  This case is so
common that there's a special built-in called *note sum(): 411. to
compute it:

     >>> import functools, operator
     >>> functools.reduce(operator.add, [1, 2, 3, 4], 0)
     10
     >>> sum([1, 2, 3, 4])
     10
     >>> sum([])
     0

For many uses of *note functools.reduce(): 126f, though, it can be
clearer to just write the obvious *note for: 2c3. loop:

     import functools
     # Instead of:
     product = functools.reduce(operator.mul, [1, 2, 3], 1)

     # You can write:
     product = 1
     for i in [1, 2, 3]:
         product *= i

A related function is *note itertools.accumulate(iterable,
func=operator.add): 9a1.  It performs the same calculation, but instead
of returning only the final result, *note accumulate(): 9a1. returns an
iterator that also yields each partial result:

     itertools.accumulate([1, 2, 3, 4, 5]) =>
       1, 3, 6, 10, 15

     itertools.accumulate([1, 2, 3, 4, 5], operator.mul) =>
       1, 2, 6, 24, 120

* Menu:

* operator 模組::


File: python.info,  Node: operator 模組,  Up: functools 模組

9.6.7.1 operator 模組
.....................

The *note operator: 8f. module was mentioned earlier.  It contains a set
of functions corresponding to Python's operators.  These functions are
often useful in functional-style code because they save you from writing
trivial functions that perform a single operation.

Some of the functions in this module are:

   * 數學運算：‘add()’、‘sub()’、‘mul()’、‘floordiv()’、‘abs()’...

   * Logical operations: ‘not_()’, ‘truth()’.

   * Bitwise operations: ‘and_()’, ‘or_()’, ‘invert()’.

   * Comparisons: ‘eq()’, ‘ne()’, ‘lt()’, ‘le()’, ‘gt()’, and ‘ge()’.

   * Object identity: ‘is_()’, ‘is_not()’.

Consult the operator module's documentation for a complete list.


File: python.info,  Node: Small functions and the lambda expression,  Next: Revision History and Acknowledgements,  Prev: functools 模組,  Up: 函式編程 HOWTO

9.6.8 Small functions and the lambda expression
-----------------------------------------------

When writing functional-style programs, you'll often need little
functions that act as predicates or that combine elements in some way.

If there's a Python built-in or a module function that's suitable, you
don't need to define a new function at all:

     stripped_lines = [line.strip() for line in lines]
     existing_files = filter(os.path.exists, file_list)

If the function you need doesn't exist, you need to write it.  One way
to write small functions is to use the *note lambda: 1234. expression.
‘lambda’ takes a number of parameters and an expression combining these
parameters, and creates an anonymous function that returns the value of
the expression:

     adder = lambda x, y: x+y

     print_assign = lambda name, value: name + '=' + str(value)

An alternative is to just use the ‘def’ statement and define a function
in the usual way:

     def adder(x, y):
         return x + y

     def print_assign(name, value):
         return name + '=' + str(value)

Which alternative is preferable?  That's a style question; my usual
course is to avoid using ‘lambda’.

One reason for my preference is that ‘lambda’ is quite limited in the
functions it can define.  The result has to be computable as a single
expression, which means you can't have multiway ‘if... elif... else’
comparisons or ‘try... except’ statements.  If you try to do too much in
a ‘lambda’ statement, you'll end up with an overly complicated
expression that's hard to read.  Quick, what's the following code doing?

     import functools
     total = functools.reduce(lambda a, b: (0, a[1] + b[1]), items)[1]

You can figure it out, but it takes time to disentangle the expression
to figure out what's going on.  Using a short nested ‘def’ statements
makes things a little bit better:

     import functools
     def combine(a, b):
         return 0, a[1] + b[1]

     total = functools.reduce(combine, items)[1]

But it would be best of all if I had simply used a ‘for’ loop:

     total = 0
     for a, b in items:
         total += b

Or the *note sum(): 411. built-in and a generator expression:

     total = sum(b for a, b in items)

Many uses of *note functools.reduce(): 126f. are clearer when written as
‘for’ loops.

Fredrik Lundh once suggested the following set of rules for refactoring
uses of ‘lambda’:

  1. Write a lambda function.

  2. Write a comment explaining what the heck that lambda does.

  3. Study the comment for a while, and think of a name that captures
     the essence of the comment.

  4. Convert the lambda to a def statement, using that name.

  5. Remove the comment.

I really like these rules, but you're free to disagree about whether
this lambda-free style is better.


File: python.info,  Node: Revision History and Acknowledgements,  Next: References<2>,  Prev: Small functions and the lambda expression,  Up: 函式編程 HOWTO

9.6.9 Revision History and Acknowledgements
-------------------------------------------

The author would like to thank the following people for offering
suggestions, corrections and assistance with various drafts of this
article: Ian Bicking, Nick Coghlan, Nick Efford, Raymond Hettinger, Jim
Jewett, Mike Krell, Leandro Lameiro, Jussi Salmela, Collin Winter, Blake
Winton.

Version 0.1: posted June 30 2006.

Version 0.11: posted July 1 2006.  Typo fixes.

Version 0.2: posted July 10 2006.  Merged genexp and listcomp sections
into one.  Typo fixes.

Version 0.21: Added more references suggested on the tutor mailing list.

Version 0.30: Adds a section on the ‘functional’ module written by
Collin Winter; adds short section on the operator module; a few other
edits.


File: python.info,  Node: References<2>,  Prev: Revision History and Acknowledgements,  Up: 函式編程 HOWTO

9.6.10 References
-----------------

* Menu:

* General::
* Python-specific::
* Python 說明文件::


File: python.info,  Node: General,  Next: Python-specific,  Up: References<2>

9.6.10.1 General
................

'Structure and Interpretation of Computer Programs', by Harold Abelson
and Gerald Jay Sussman with Julie Sussman.  The book can be found at
‘https://mitpress.mit.edu/sicp’.  In this classic textbook of computer
science, chapters 2 and 3 discuss the use of sequences and streams to
organize the data flow inside a program.  The book uses Scheme for its
examples, but many of the design approaches described in these chapters
are applicable to functional-style Python code.

‘https://www.defmacro.org/ramblings/fp.html’: A general introduction to
functional programming that uses Java examples and has a lengthy
historical introduction.

‘https://en.wikipedia.org/wiki/Functional_programming’: General
Wikipedia entry describing functional programming.

‘https://en.wikipedia.org/wiki/Coroutine’: 協程 (coroutines) 的條目。

‘https://en.wikipedia.org/wiki/Partial_application’: 偏函式 (partial
application) 概念的條目。

‘https://en.wikipedia.org/wiki/Currying’: currying 概念的條目。


File: python.info,  Node: Python-specific,  Next: Python 說明文件,  Prev: General,  Up: References<2>

9.6.10.2 Python-specific
........................

‘https://gnosis.cx/TPiP/’: The first chapter of David Mertz's book ‘Text
Processing in Python’ discusses functional programming for text
processing, in the section titled "Utilizing Higher-Order Functions in
Text Processing".

Mertz also wrote a 3-part series of articles on functional programming
for IBM's DeveloperWorks site; see part 1(1), part 2(2), and part 3(3),

   ---------- Footnotes ----------

   (1) https://developer.ibm.com/articles/l-prog/

   (2) https://developer.ibm.com/tutorials/l-prog2/

   (3) https://developer.ibm.com/tutorials/l-prog3/


File: python.info,  Node: Python 說明文件,  Prev: Python-specific,  Up: References<2>

9.6.10.3 Python 說明文件
........................

*note itertools: 75. 模組的說明文件。

*note functools: 55. 模組的說明文件。

*note operator: 8f. 模組的說明文件。

PEP 289(1)：「產生器運算式 (Generator Expressions)」

PEP 342(2): "Coroutines via Enhanced Generators" describes the new
generator features in Python 2.5.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0289/

   (2) https://peps.python.org/pep-0342/


File: python.info,  Node: 如何使用 Logging 模組,  Next: Logging Cookbook,  Prev: 函式編程 HOWTO,  Up: Python 如何達成任務

9.7 如何使用 Logging 模組
=========================


作者: Vinay Sajip <vinay_sajip at red-dove dot com>

This page contains tutorial information.  For links to reference
information and a logging cookbook, please see *note 其他資源: 4d2e.

* Menu:

* 基礎 Logging 指南::
* Advanced Logging Tutorial::
* Logging Levels: Logging Levels<2>.
* Useful Handlers::
* Exceptions raised during logging::
* Using arbitrary objects as messages::
* 最佳化: 最佳化<17>.
* 其他資源: 其他資源<2>.


File: python.info,  Node: 基礎 Logging 指南,  Next: Advanced Logging Tutorial,  Up: 如何使用 Logging 模組

9.7.1 基礎 Logging 指南
-----------------------

軟體執行時，追蹤有什麼事件發生的動作稱為 Logging。軟體開發者會使用
Logging 這樣的機制是因為想知道在運行過程中是否有特定的事件發生。事件會被
一段訊息所描述。這段訊息可能包含一些因為此事件發生而改變的資料。開發者也
可以指派事件的重要程度，重要程度有時候也會被稱作 '程度' 或是 '嚴重性' 。

* Menu:

* 什麼時候使用 logging::
* 一個簡單範例: 一個簡單範例<2>.
* Logging to a file::
* Logging variable data::
* Changing the format of displayed messages::
* Displaying the date/time in messages::
* Next Steps::


File: python.info,  Node: 什麼時候使用 logging,  Next: 一個簡單範例<2>,  Up: 基礎 Logging 指南

9.7.1.1 什麼時候使用 logging
............................

You can access logging functionality by creating a logger via ‘logger =
getLogger(__name__)’, and then calling the logger's *note debug(): dd0,
*note info(): 2bb3, *note warning(): 1600, *note error(): 2bb5. and
*note critical(): dcf. methods.  To determine when to use logging, and
to see which logger methods to use when, see the table below.  It
states, for each of a set of common tasks, the best tool to use for that
task.

Task you want to perform                  The best tool for the task
                                          
-------------------------------------------------------------------------------------
                                          
Display console output for ordinary       *note print(): f18.
usage of a command line script or         
program

Report events that occur during normal    A logger's *note info(): 2bb3. (or
operation of a program (e.g.  for         *note debug(): dd0. method for very
status monitoring or fault                detailed output for diagnostic purposes)
investigation)                            

Issue a warning regarding a particular    *note warnings.warn(): 1488. in library
runtime event                             code if the issue is avoidable and the
                                          client application should be modified to
                                          eliminate the warning
                                          
                                          A logger's *note warning(): 1600. method
                                          if there is nothing the client
                                          application can do about the situation,
                                          but the event should still be noted
                                          
                                          
Report an error regarding a particular    Raise an exception
runtime event                             

Report suppression of an error without    A logger's *note error(): 2bb5,
raising an exception (e.g.  error         *note exception(): dce. or
handler in a long-running server          *note critical(): dcf. method as
process)                                  appropriate for the specific error and
                                          application domain
                                          

The logger methods are named after the level or severity of the events
they are used to track.  The standard levels and their applicability are
described below (in increasing order of severity):

Level              When it's used
                   
---------------------------------------------------------------------
                   
‘DEBUG’            Detailed information, typically of interest
                   only when diagnosing problems.
                   
                   
‘INFO’             Confirmation that things are working as
                   expected.
                   
                   
‘WARNING’          An indication that something unexpected
                   happened, or indicative of some problem in the
                   near future (e.g.  'disk space low').  The
                   software is still working as expected.
                   
                   
‘ERROR’            Due to a more serious problem, the software has
                   not been able to perform some function.
                   
                   
‘CRITICAL’         A serious error, indicating that the program
                   itself may be unable to continue running.
                   

The default level is ‘WARNING’, which means that only events of this
severity and higher will be tracked, unless the logging package is
configured to do otherwise.

Events that are tracked can be handled in different ways.  The simplest
way of handling tracked events is to print them to the console.  Another
common way is to write them to a disk file.


File: python.info,  Node: 一個簡單範例<2>,  Next: Logging to a file,  Prev: 什麼時候使用 logging,  Up: 基礎 Logging 指南

9.7.1.2 一個簡單範例
....................

一個非常簡單的例子是：

     import logging
     logging.warning('Watch out!')  # 將會印出訊息至控制台
     logging.info('I told you so')  # 不會印出任何東西

If you type these lines into a script and run it, you'll see:

     WARNING:root:Watch out!

printed out on the console.  The ‘INFO’ message doesn't appear because
the default level is ‘WARNING’.  The printed message includes the
indication of the level and the description of the event provided in the
logging call, i.e.  'Watch out!'.  The actual output can be formatted
quite flexibly if you need that; formatting options will also be
explained later.

Notice that in this example, we use functions directly on the ‘logging’
module, like ‘logging.debug’, rather than creating a logger and calling
functions on it.  These functions operation on the root logger, but can
be useful as they will call *note basicConfig(): 9a4. for you if it has
not been called yet, like in this example.  In larger programs you'll
usually want to control the logging configuration explicitly however -
so for that reason as well as others, it's better to create loggers and
call their methods.


File: python.info,  Node: Logging to a file,  Next: Logging variable data,  Prev: 一個簡單範例<2>,  Up: 基礎 Logging 指南

9.7.1.3 Logging to a file
.........................

A very common situation is that of recording logging events in a file,
so let's look at that next.  Be sure to try the following in a newly
started Python interpreter, and don't just continue from the session
described above:

     import logging
     logger = logging.getLogger(__name__)
     logging.basicConfig(filename='example.log', encoding='utf-8', level=logging.DEBUG)
     logger.debug('This message should go to the log file')
     logger.info('So should this')
     logger.warning('And this, too')
     logger.error('And non-ASCII stuff, too, like Øresund and Malmö')

在 3.9 版的變更: The 'encoding' argument was added.  In earlier Python
versions, or if not specified, the encoding used is the default value
used by *note open(): 4c0.  While not shown in the above example, an
'errors' argument can also now be passed, which determines how encoding
errors are handled.  For available values and the default, see the
documentation for *note open(): 4c0.

And now if we open the file and look at what we have, we should find the
log messages:

     DEBUG:__main__:This message should go to the log file
     INFO:__main__:So should this
     WARNING:__main__:And this, too
     ERROR:__main__:And non-ASCII stuff, too, like Øresund and Malmö

This example also shows how you can set the logging level which acts as
the threshold for tracking.  In this case, because we set the threshold
to ‘DEBUG’, all of the messages were printed.

If you want to set the logging level from a command-line option such as:

     --log=INFO

and you have the value of the parameter passed for ‘--log’ in some
variable 'loglevel', you can use:

     getattr(logging, loglevel.upper())

to get the value which you'll pass to *note basicConfig(): 9a4. via the
'level' argument.  You may want to error check any user input value,
perhaps as in the following example:

     # assuming loglevel is bound to the string value obtained from the
     # command line argument. Convert to upper case to allow the user to
     # specify --log=DEBUG or --log=debug
     numeric_level = getattr(logging, loglevel.upper(), None)
     if not isinstance(numeric_level, int):
         raise ValueError('Invalid log level: %s' % loglevel)
     logging.basicConfig(level=numeric_level, ...)

The call to *note basicConfig(): 9a4. should come 'before' any calls to
a logger's methods such as *note debug(): dd0, *note info(): 2bb3, etc.
Otherwise, that logging event may not be handled in the desired manner.

If you run the above script several times, the messages from successive
runs are appended to the file 'example.log'.  If you want each run to
start afresh, not remembering the messages from earlier runs, you can
specify the 'filemode' argument, by changing the call in the above
example to:

     logging.basicConfig(filename='example.log', filemode='w', level=logging.DEBUG)

The output will be the same as before, but the log file is no longer
appended to, so the messages from earlier runs are lost.


File: python.info,  Node: Logging variable data,  Next: Changing the format of displayed messages,  Prev: Logging to a file,  Up: 基礎 Logging 指南

9.7.1.4 Logging variable data
.............................

To log variable data, use a format string for the event description
message and append the variable data as arguments.  For example:

     import logging
     logging.warning('%s before you %s', 'Look', 'leap!')

will display:

     WARNING:root:Look before you leap!

As you can see, merging of variable data into the event description
message uses the old, %-style of string formatting.  This is for
backwards compatibility: the logging package pre-dates newer formatting
options such as *note str.format(): 5c7. and *note string.Template: 62d.
These newer formatting options 'are' supported, but exploring them is
outside the scope of this tutorial: see *note Using particular
formatting styles throughout your application: 2bd3. for more
information.


File: python.info,  Node: Changing the format of displayed messages,  Next: Displaying the date/time in messages,  Prev: Logging variable data,  Up: 基礎 Logging 指南

9.7.1.5 Changing the format of displayed messages
.................................................

To change the format which is used to display messages, you need to
specify the format you want to use:

     import logging
     logging.basicConfig(format='%(levelname)s:%(message)s', level=logging.DEBUG)
     logging.debug('This message should appear on the console')
     logging.info('So should this')
     logging.warning('And this, too')

which would print:

     DEBUG:This message should appear on the console
     INFO:So should this
     WARNING:And this, too

Notice that the 'root' which appeared in earlier examples has
disappeared.  For a full set of things that can appear in format
strings, you can refer to the documentation for *note LogRecord
attributes: 2bb2, but for simple usage, you just need the 'levelname'
(severity), 'message' (event description, including variable data) and
perhaps to display when the event occurred.  This is described in the
next section.


File: python.info,  Node: Displaying the date/time in messages,  Next: Next Steps,  Prev: Changing the format of displayed messages,  Up: 基礎 Logging 指南

9.7.1.6 Displaying the date/time in messages
............................................

To display the date and time of an event, you would place '%(asctime)s'
in your format string:

     import logging
     logging.basicConfig(format='%(asctime)s %(message)s')
     logging.warning('is when this event was logged.')

which should print something like this:

     2010-12-12 11:41:42,612 is when this event was logged.

The default format for date/time display (shown above) is like ISO8601
or RFC 3339(1).  If you need more control over the formatting of the
date/time, provide a 'datefmt' argument to ‘basicConfig’, as in this
example:

     import logging
     logging.basicConfig(format='%(asctime)s %(message)s', datefmt='%m/%d/%Y %I:%M:%S %p')
     logging.warning('is when this event was logged.')

which would display something like this:

     12/12/2010 11:46:36 AM is when this event was logged.

The format of the 'datefmt' argument is the same as supported by *note
time.strftime(): 1181.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc3339.html


File: python.info,  Node: Next Steps,  Prev: Displaying the date/time in messages,  Up: 基礎 Logging 指南

9.7.1.7 Next Steps
..................

That concludes the basic tutorial.  It should be enough to get you up
and running with logging.  There's a lot more that the logging package
offers, but to get the best out of it, you'll need to invest a little
more of your time in reading the following sections.  If you're ready
for that, grab some of your favourite beverage and carry on.

If your logging needs are simple, then use the above examples to
incorporate logging into your own scripts, and if you run into problems
or don't understand something, please post a question on the
comp.lang.python Usenet group (available at
‘https://groups.google.com/g/comp.lang.python’) and you should receive
help before too long.

Still here?  You can carry on reading the next few sections, which
provide a slightly more advanced/in-depth tutorial than the basic one
above.  After that, you can take a look at the *note Logging Cookbook:
118f.


File: python.info,  Node: Advanced Logging Tutorial,  Next: Logging Levels<2>,  Prev: 基礎 Logging 指南,  Up: 如何使用 Logging 模組

9.7.2 Advanced Logging Tutorial
-------------------------------

The logging library takes a modular approach and offers several
categories of components: loggers, handlers, filters, and formatters.

   * Loggers expose the interface that application code directly uses.

   * Handlers send the log records (created by loggers) to the
     appropriate destination.

   * Filters provide a finer grained facility for determining which log
     records to output.

   * Formatters specify the layout of log records in the final output.

Log event information is passed between loggers, handlers, filters and
formatters in a *note LogRecord: f89. instance.

Logging is performed by calling methods on instances of the *note
Logger: af3. class (hereafter called 'loggers').  Each instance has a
name, and they are conceptually arranged in a namespace hierarchy using
dots (periods) as separators.  For example, a logger named 'scan' is the
parent of loggers 'scan.text', 'scan.html' and 'scan.pdf'.  Logger names
can be anything you want, and indicate the area of an application in
which a logged message originates.

A good convention to use when naming loggers is to use a module-level
logger, in each module which uses logging, named as follows:

     logger = logging.getLogger(__name__)

This means that logger names track the package/module hierarchy, and
it's intuitively obvious where events are logged just from the logger
name.

The root of the hierarchy of loggers is called the root logger.  That's
the logger used by the functions *note debug(): 2bb4, *note info():
2bde, *note warning(): 2d0, *note error(): 2bf2. and *note critical():
2bf3, which just call the same-named method of the root logger.  The
functions and the methods have the same signatures.  The root logger's
name is printed as 'root' in the logged output.

It is, of course, possible to log messages to different destinations.
Support is included in the package for writing log messages to files,
HTTP GET/POST locations, email via SMTP, generic sockets, queues, or
OS-specific logging mechanisms such as syslog or the Windows NT event
log.  Destinations are served by 'handler' classes.  You can create your
own log destination class if you have special requirements not met by
any of the built-in handler classes.

By default, no destination is set for any logging messages.  You can
specify a destination (such as console or file) by using *note
basicConfig(): 9a4. as in the tutorial examples.  If you call the
functions *note debug(): 2bb4, *note info(): 2bde, *note warning(): 2d0,
*note error(): 2bf2. and *note critical(): 2bf3, they will check to see
if no destination is set; and if one is not set, they will set a
destination of the console (‘sys.stderr’) and a default format for the
displayed message before delegating to the root logger to do the actual
message output.

The default format set by *note basicConfig(): 9a4. for messages is:

     severity:logger name:message

You can change this by passing a format string to *note basicConfig():
9a4. with the 'format' keyword argument.  For all options regarding how
a format string is constructed, see *note Formatter Objects: 2bd0.

* Menu:

* Logging Flow::
* Loggers::
* Handlers::
* Formatters::
* Configuring Logging::
* What happens if no configuration is provided::
* Configuring Logging for a Library::


File: python.info,  Node: Logging Flow,  Next: Loggers,  Up: Advanced Logging Tutorial

9.7.2.1 Logging Flow
....................

The flow of log event information in loggers and handlers is illustrated
in the following diagram.

[image src="python-figures/logging_flow.png"]



File: python.info,  Node: Loggers,  Next: Handlers,  Prev: Logging Flow,  Up: Advanced Logging Tutorial

9.7.2.2 Loggers
...............

*note Logger: af3. objects have a threefold job.  First, they expose
several methods to application code so that applications can log
messages at runtime.  Second, logger objects determine which log
messages to act upon based upon severity (the default filtering
facility) or filter objects.  Third, logger objects pass along relevant
log messages to all interested log handlers.

The most widely used methods on logger objects fall into two categories:
configuration and message sending.

These are the most common configuration methods:

   * *note Logger.setLevel(): 13fc. specifies the lowest-severity log
     message a logger will handle, where debug is the lowest built-in
     severity level and critical is the highest built-in severity.  For
     example, if the severity level is INFO, the logger will handle only
     INFO, WARNING, ERROR, and CRITICAL messages and will ignore DEBUG
     messages.

   * *note Logger.addHandler(): 2bad. and *note Logger.removeHandler():
     2bae. add and remove handler objects from the logger object.
     Handlers are covered in more detail in *note Handlers: 4d3b.

   * *note Logger.addFilter(): 2bb6. and *note Logger.removeFilter():
     2bb7. add and remove filter objects from the logger object.
     Filters are covered in more detail in *note Filter Objects: 2bdb.

You don't need to always call these methods on every logger you create.
See the last two paragraphs in this section.

With the logger object configured, the following methods create log
messages:

   * *note Logger.debug(): dd0, *note Logger.info(): 2bb3, *note
     Logger.warning(): 1600, *note Logger.error(): 2bb5, and *note
     Logger.critical(): dcf. all create log records with a message and a
     level that corresponds to their respective method names.  The
     message is actually a format string, which may contain the standard
     string substitution syntax of ‘%s’, ‘%d’, ‘%f’, and so on.  The
     rest of their arguments is a list of objects that correspond with
     the substitution fields in the message.  With regard to ‘**kwargs’,
     the logging methods care only about a keyword of ‘exc_info’ and use
     it to determine whether to log exception information.

   * *note Logger.exception(): dce. creates a log message similar to
     *note Logger.error(): 2bb5.  The difference is that *note
     Logger.exception(): dce. dumps a stack trace along with it.  Call
     this method only from an exception handler.

   * *note Logger.log(): dcd. takes a log level as an explicit argument.
     This is a little more verbose for logging messages than using the
     log level convenience methods listed above, but this is how to log
     at custom log levels.

*note getLogger(): 904. returns a reference to a logger instance with
the specified name if it is provided, or ‘root’ if not.  The names are
period-separated hierarchical structures.  Multiple calls to *note
getLogger(): 904. with the same name will return a reference to the same
logger object.  Loggers that are further down in the hierarchical list
are children of loggers higher up in the list.  For example, given a
logger with a name of ‘foo’, loggers with names of ‘foo.bar’,
‘foo.bar.baz’, and ‘foo.bam’ are all descendants of ‘foo’.

Loggers have a concept of 'effective level'.  If a level is not
explicitly set on a logger, the level of its parent is used instead as
its effective level.  If the parent has no explicit level set, 'its'
parent is examined, and so on - all ancestors are searched until an
explicitly set level is found.  The root logger always has an explicit
level set (‘WARNING’ by default).  When deciding whether to process an
event, the effective level of the logger is used to determine whether
the event is passed to the logger's handlers.

Child loggers propagate messages up to the handlers associated with
their ancestor loggers.  Because of this, it is unnecessary to define
and configure handlers for all the loggers an application uses.  It is
sufficient to configure handlers for a top-level logger and create child
loggers as needed.  (You can, however, turn off propagation by setting
the 'propagate' attribute of a logger to ‘False’.)


File: python.info,  Node: Handlers,  Next: Formatters,  Prev: Loggers,  Up: Advanced Logging Tutorial

9.7.2.3 Handlers
................

*note Handler: 13ff. objects are responsible for dispatching the
appropriate log messages (based on the log messages' severity) to the
handler's specified destination.  *note Logger: af3. objects can add
zero or more handler objects to themselves with an *note addHandler():
2bad. method.  As an example scenario, an application may want to send
all log messages to a log file, all log messages of error or higher to
stdout, and all messages of critical to an email address.  This scenario
requires three individual handlers where each handler is responsible for
sending messages of a specific severity to a specific location.

The standard library includes quite a few handler types (see *note
Useful Handlers: 4d3d.); the tutorials use mainly *note StreamHandler:
1190. and *note FileHandler: 17a1. in its examples.

There are very few methods in a handler for application developers to
concern themselves with.  The only handler methods that seem relevant
for application developers who are using the built-in handler objects
(that is, not creating custom handlers) are the following configuration
methods:

   * The *note setLevel(): 2bc4. method, just as in logger objects,
     specifies the lowest severity that will be dispatched to the
     appropriate destination.  Why are there two *note setLevel(): 2bc4.
     methods?  The level set in the logger determines which severity of
     messages it will pass to its handlers.  The level set in each
     handler determines which messages that handler will send on.

   * *note setFormatter(): 2bc5. selects a Formatter object for this
     handler to use.

   * *note addFilter(): 2bc6. and *note removeFilter(): 2bc7.
     respectively configure and deconfigure filter objects on handlers.

Application code should not directly instantiate and use instances of
*note Handler: 13ff.  Instead, the *note Handler: 13ff. class is a base
class that defines the interface that all handlers should have and
establishes some default behavior that child classes can use (or
override).


File: python.info,  Node: Formatters,  Next: Configuring Logging,  Prev: Handlers,  Up: Advanced Logging Tutorial

9.7.2.4 Formatters
..................

Formatter objects configure the final order, structure, and contents of
the log message.  Unlike the base *note logging.Handler: 13ff. class,
application code may instantiate formatter classes, although you could
likely subclass the formatter if your application needs special
behavior.  The constructor takes three optional arguments - a message
format string, a date format string and a style indicator.

 -- 方法: logging.Formatter.__init__ (fmt=None, datefmt=None, style='%')

If there is no message format string, the default is to use the raw
message.  If there is no date format string, the default date format is:

     %Y-%m-%d %H:%M:%S

with the milliseconds tacked on at the end.  The ‘style’ is one of
‘'%'’, ‘'{'’, or ‘'$'’.  If one of these is not specified, then ‘'%'’
will be used.

If the ‘style’ is ‘'%'’, the message format string uses ‘%(<dictionary
key>)s’ styled string substitution; the possible keys are documented in
*note LogRecord attributes: 2bb2.  If the style is ‘'{'’, the message
format string is assumed to be compatible with *note str.format(): 5c7.
(using keyword arguments), while if the style is ‘'$'’ then the message
format string should conform to what is expected by *note
string.Template.substitute(): 1bed.

在 3.2 版的變更: 新增 ‘style’ 參數。

The following message format string will log the time in a
human-readable format, the severity of the message, and the contents of
the message, in that order:

     '%(asctime)s - %(levelname)s - %(message)s'

Formatters use a user-configurable function to convert the creation time
of a record to a tuple.  By default, *note time.localtime(): 1467. is
used; to change this for a particular formatter instance, set the
‘converter’ attribute of the instance to a function with the same
signature as *note time.localtime(): 1467. or *note time.gmtime(): 1158.
To change it for all formatters, for example if you want all logging
times to be shown in GMT, set the ‘converter’ attribute in the Formatter
class (to ‘time.gmtime’ for GMT display).


File: python.info,  Node: Configuring Logging,  Next: What happens if no configuration is provided,  Prev: Formatters,  Up: Advanced Logging Tutorial

9.7.2.5 Configuring Logging
...........................

Programmers can configure logging in three ways:

  1. Creating loggers, handlers, and formatters explicitly using Python
     code that calls the configuration methods listed above.

  2. Creating a logging config file and reading it using the *note
     fileConfig(): af5. function.

  3. Creating a dictionary of configuration information and passing it
     to the *note dictConfig(): 1147. function.

For the reference documentation on the last two options, see *note
Configuration functions: 1284.  The following example configures a very
simple logger, a console handler, and a simple formatter using Python
code:

     import logging

     # create logger
     logger = logging.getLogger('simple_example')
     logger.setLevel(logging.DEBUG)

     # create console handler and set level to debug
     ch = logging.StreamHandler()
     ch.setLevel(logging.DEBUG)

     # create formatter
     formatter = logging.Formatter('%(asctime)s - %(name)s - %(levelname)s - %(message)s')

     # add formatter to ch
     ch.setFormatter(formatter)

     # add ch to logger
     logger.addHandler(ch)

     # 'application' code
     logger.debug('debug message')
     logger.info('info message')
     logger.warning('warn message')
     logger.error('error message')
     logger.critical('critical message')

Running this module from the command line produces the following output:

     $ python simple_logging_module.py
     2005-03-19 15:10:26,618 - simple_example - DEBUG - debug message
     2005-03-19 15:10:26,620 - simple_example - INFO - info message
     2005-03-19 15:10:26,695 - simple_example - WARNING - warn message
     2005-03-19 15:10:26,697 - simple_example - ERROR - error message
     2005-03-19 15:10:26,773 - simple_example - CRITICAL - critical message

The following Python module creates a logger, handler, and formatter
nearly identical to those in the example listed above, with the only
difference being the names of the objects:

     import logging
     import logging.config

     logging.config.fileConfig('logging.conf')

     # create logger
     logger = logging.getLogger('simpleExample')

     # 'application' code
     logger.debug('debug message')
     logger.info('info message')
     logger.warning('warn message')
     logger.error('error message')
     logger.critical('critical message')

Here is the logging.conf file:

     [loggers]
     keys=root,simpleExample

     [handlers]
     keys=consoleHandler

     [formatters]
     keys=simpleFormatter

     [logger_root]
     level=DEBUG
     handlers=consoleHandler

     [logger_simpleExample]
     level=DEBUG
     handlers=consoleHandler
     qualname=simpleExample
     propagate=0

     [handler_consoleHandler]
     class=StreamHandler
     level=DEBUG
     formatter=simpleFormatter
     args=(sys.stdout,)

     [formatter_simpleFormatter]
     format=%(asctime)s - %(name)s - %(levelname)s - %(message)s

The output is nearly identical to that of the non-config-file-based
example:

     $ python simple_logging_config.py
     2005-03-19 15:38:55,977 - simpleExample - DEBUG - debug message
     2005-03-19 15:38:55,979 - simpleExample - INFO - info message
     2005-03-19 15:38:56,054 - simpleExample - WARNING - warn message
     2005-03-19 15:38:56,055 - simpleExample - ERROR - error message
     2005-03-19 15:38:56,130 - simpleExample - CRITICAL - critical message

You can see that the config file approach has a few advantages over the
Python code approach, mainly separation of configuration and code and
the ability of noncoders to easily modify the logging properties.

     警告: The *note fileConfig(): af5. function takes a default
     parameter, ‘disable_existing_loggers’, which defaults to ‘True’ for
     reasons of backward compatibility.  This may or may not be what you
     want, since it will cause any non-root loggers existing before the
     *note fileConfig(): af5. call to be disabled unless they (or an
     ancestor) are explicitly named in the configuration.  Please refer
     to the reference documentation for more information, and specify
     ‘False’ for this parameter if you wish.

     The dictionary passed to *note dictConfig(): 1147. can also specify
     a Boolean value with key ‘disable_existing_loggers’, which if not
     specified explicitly in the dictionary also defaults to being
     interpreted as ‘True’.  This leads to the logger-disabling
     behaviour described above, which may not be what you want - in
     which case, provide the key explicitly with a value of ‘False’.

Note that the class names referenced in config files need to be either
relative to the logging module, or absolute values which can be resolved
using normal import mechanisms.  Thus, you could use either *note
WatchedFileHandler: 2c2e. (relative to the logging module) or
‘mypackage.mymodule.MyHandler’ (for a class defined in package
‘mypackage’ and module ‘mymodule’, where ‘mypackage’ is available on the
Python import path).

In Python 3.2, a new means of configuring logging has been introduced,
using dictionaries to hold configuration information.  This provides a
superset of the functionality of the config-file-based approach outlined
above, and is the recommended configuration method for new applications
and deployments.  Because a Python dictionary is used to hold
configuration information, and since you can populate that dictionary
using different means, you have more options for configuration.  For
example, you can use a configuration file in JSON format, or, if you
have access to YAML processing functionality, a file in YAML format, to
populate the configuration dictionary.  Or, of course, you can construct
the dictionary in Python code, receive it in pickled form over a socket,
or use whatever approach makes sense for your application.

Here's an example of the same configuration as above, in YAML format for
the new dictionary-based approach:

     version: 1
     formatters:
       simple:
         format: '%(asctime)s - %(name)s - %(levelname)s - %(message)s'
     handlers:
       console:
         class: logging.StreamHandler
         level: DEBUG
         formatter: simple
         stream: ext://sys.stdout
     loggers:
       simpleExample:
         level: DEBUG
         handlers: [console]
         propagate: no
     root:
       level: DEBUG
       handlers: [console]

For more information about logging using a dictionary, see *note
Configuration functions: 1284.


File: python.info,  Node: What happens if no configuration is provided,  Next: Configuring Logging for a Library,  Prev: Configuring Logging,  Up: Advanced Logging Tutorial

9.7.2.6 What happens if no configuration is provided
....................................................

If no logging configuration is provided, it is possible to have a
situation where a logging event needs to be output, but no handlers can
be found to output the event.

The event is output using a 'handler of last resort', stored in *note
lastResort: 1192.  This internal handler is not associated with any
logger, and acts like a *note StreamHandler: 1190. which writes the
event description message to the current value of ‘sys.stderr’
(therefore respecting any redirections which may be in effect).  No
formatting is done on the message - just the bare event description
message is printed.  The handler's level is set to ‘WARNING’, so all
events at this and greater severities will be output.

在 3.2 版的變更: For versions of Python prior to 3.2, the behaviour is
as follows:

   * If *note raiseExceptions: 1191. is ‘False’ (production mode), the
     event is silently dropped.

   * If *note raiseExceptions: 1191. is ‘True’ (development mode), a
     message 'No handlers could be found for logger X.Y.Z' is printed
     once.

To obtain the pre-3.2 behaviour, *note lastResort: 1192. can be set to
‘None’.


File: python.info,  Node: Configuring Logging for a Library,  Prev: What happens if no configuration is provided,  Up: Advanced Logging Tutorial

9.7.2.7 Configuring Logging for a Library
.........................................

When developing a library which uses logging, you should take care to
document how the library uses logging - for example, the names of
loggers used.  Some consideration also needs to be given to its logging
configuration.  If the using application does not use logging, and
library code makes logging calls, then (as described in the previous
section) events of severity ‘WARNING’ and greater will be printed to
‘sys.stderr’.  This is regarded as the best default behaviour.

If for some reason you 'don't' want these messages printed in the
absence of any logging configuration, you can attach a do-nothing
handler to the top-level logger for your library.  This avoids the
message being printed, since a handler will always be found for the
library's events: it just doesn't produce any output.  If the library
user configures logging for application use, presumably that
configuration will add some handlers, and if levels are suitably
configured then logging calls made in library code will send output to
those handlers, as normal.

A do-nothing handler is included in the logging package: *note
NullHandler: 121c. (since Python 3.1).  An instance of this handler
could be added to the top-level logger of the logging namespace used by
the library ('if' you want to prevent your library's logged events being
output to ‘sys.stderr’ in the absence of logging configuration).  If all
logging by a library 'foo' is done using loggers with names matching
'foo.x', 'foo.x.y', etc.  then the code:

     import logging
     logging.getLogger('foo').addHandler(logging.NullHandler())

should have the desired effect.  If an organisation produces a number of
libraries, then the logger name specified can be 'orgname.foo' rather
than just 'foo'.

     備註: It is strongly advised that you 'do not log to the root
     logger' in your library.  Instead, use a logger with a unique and
     easily identifiable name, such as the ‘__name__’ for your library's
     top-level package or module.  Logging to the root logger will make
     it difficult or impossible for the application developer to
     configure the logging verbosity or handlers of your library as they
     wish.

     備註: It is strongly advised that you 'do not add any handlers
     other than' *note NullHandler: 121c. 'to your library's loggers'.
     This is because the configuration of handlers is the prerogative of
     the application developer who uses your library.  The application
     developer knows their target audience and what handlers are most
     appropriate for their application: if you add handlers 'under the
     hood', you might well interfere with their ability to carry out
     unit tests and deliver logs which suit their requirements.


File: python.info,  Node: Logging Levels<2>,  Next: Useful Handlers,  Prev: Advanced Logging Tutorial,  Up: 如何使用 Logging 模組

9.7.3 Logging Levels
--------------------

The numeric values of logging levels are given in the following table.
These are primarily of interest if you want to define your own levels,
and need them to have specific values relative to the predefined levels.
If you define a level with the same numeric value, it overwrites the
predefined value; the predefined name is lost.

Level              Numeric value
                   
---------------------------------------
                   
‘CRITICAL’         50
                   
                   
‘ERROR’            40
                   
                   
‘WARNING’          30
                   
                   
‘INFO’             20
                   
                   
‘DEBUG’            10
                   
                   
‘NOTSET’           0
                   

Levels can also be associated with loggers, being set either by the
developer or through loading a saved logging configuration.  When a
logging method is called on a logger, the logger compares its own level
with the level associated with the method call.  If the logger's level
is higher than the method call's, no logging message is actually
generated.  This is the basic mechanism controlling the verbosity of
logging output.

Logging messages are encoded as instances of the *note LogRecord: f89.
class.  When a logger decides to actually log an event, a *note
LogRecord: f89. instance is created from the logging message.

Logging messages are subjected to a dispatch mechanism through the use
of 'handlers', which are instances of subclasses of the *note Handler:
13ff. class.  Handlers are responsible for ensuring that a logged
message (in the form of a *note LogRecord: f89.) ends up in a particular
location (or set of locations) which is useful for the target audience
for that message (such as end users, support desk staff, system
administrators, developers).  Handlers are passed *note LogRecord: f89.
instances intended for particular destinations.  Each logger can have
zero, one or more handlers associated with it (via the *note
addHandler(): 2bad. method of *note Logger: af3.).  In addition to any
handlers directly associated with a logger, 'all handlers associated
with all ancestors of the logger' are called to dispatch the message
(unless the 'propagate' flag for a logger is set to a false value, at
which point the passing to ancestor handlers stops).

Just as for loggers, handlers can have levels associated with them.  A
handler's level acts as a filter in the same way as a logger's level
does.  If a handler decides to actually dispatch an event, the *note
emit(): 2bce. method is used to send the message to its destination.
Most user-defined subclasses of *note Handler: 13ff. will need to
override this *note emit(): 2bce.

* Menu:

* Custom Levels::


File: python.info,  Node: Custom Levels,  Up: Logging Levels<2>

9.7.3.1 Custom Levels
.....................

Defining your own levels is possible, but should not be necessary, as
the existing levels have been chosen on the basis of practical
experience.  However, if you are convinced that you need custom levels,
great care should be exercised when doing this, and it is possibly 'a
very bad idea to define custom levels if you are developing a library'.
That's because if multiple library authors all define their own custom
levels, there is a chance that the logging output from such multiple
libraries used together will be difficult for the using developer to
control and/or interpret, because a given numeric value might mean
different things for different libraries.


File: python.info,  Node: Useful Handlers,  Next: Exceptions raised during logging,  Prev: Logging Levels<2>,  Up: 如何使用 Logging 模組

9.7.4 Useful Handlers
---------------------

In addition to the base *note Handler: 13ff. class, many useful
subclasses are provided:

  1. *note StreamHandler: 1190. instances send messages to streams
     (file-like objects).

  2. *note FileHandler: 17a1. instances send messages to disk files.

  3. *note BaseRotatingHandler: 2c32. is the base class for handlers
     that rotate log files at a certain point.  It is not meant to be
     instantiated directly.  Instead, use *note RotatingFileHandler:
     14cb. or *note TimedRotatingFileHandler: f04.

  4. *note RotatingFileHandler: 14cb. instances send messages to disk
     files, with support for maximum log file sizes and log file
     rotation.

  5. *note TimedRotatingFileHandler: f04. instances send messages to
     disk files, rotating the log file at certain timed intervals.

  6. *note SocketHandler: f05. instances send messages to TCP/IP
     sockets.  Since 3.4, Unix domain sockets are also supported.

  7. *note DatagramHandler: f06. instances send messages to UDP sockets.
     Since 3.4, Unix domain sockets are also supported.

  8. *note SMTPHandler: 2c5e. instances send messages to a designated
     email address.

  9. *note SysLogHandler: 602. instances send messages to a Unix syslog
     daemon, possibly on a remote machine.

  10. *note NTEventLogHandler: 2c56. instances send messages to a
     Windows NT/2000/XP event log.

  11. *note MemoryHandler: 2c14. instances send messages to a buffer in
     memory, which is flushed whenever specific criteria are met.

  12. *note HTTPHandler: dd1. instances send messages to an HTTP server
     using either ‘GET’ or ‘POST’ semantics.

  13. *note WatchedFileHandler: 2c2e. instances watch the file they are
     logging to.  If the file changes, it is closed and reopened using
     the file name.  This handler is only useful on Unix-like systems;
     Windows does not support the underlying mechanism used.

  14. *note QueueHandler: 16dc. instances send messages to a queue, such
     as those implemented in the *note queue: a4. or *note
     multiprocessing: 86. modules.

  15. *note NullHandler: 121c. instances do nothing with error messages.
     They are used by library developers who want to use logging, but
     want to avoid the 'No handlers could be found for logger 'XXX"
     message which can be displayed if the library user has not
     configured logging.  See *note Configuring Logging for a Library:
     2c2b. for more information.

在 3.1 版被加入: The *note NullHandler: 121c. class.

在 3.2 版被加入: The *note QueueHandler: 16dc. class.

The *note NullHandler: 121c, *note StreamHandler: 1190. and *note
FileHandler: 17a1. classes are defined in the core logging package.  The
other handlers are defined in a sub-module, *note logging.handlers: 7d.
(There is also another sub-module, *note logging.config: 7c, for
configuration functionality.)

Logged messages are formatted for presentation through instances of the
*note Formatter: 1400. class.  They are initialized with a format string
suitable for use with the % operator and a dictionary.

For formatting multiple messages in a batch, instances of *note
BufferingFormatter: 2bd7. can be used.  In addition to the format string
(which is applied to each message in the batch), there is provision for
header and trailer format strings.

When filtering based on logger level and/or handler level is not enough,
instances of *note Filter: 1193. can be added to both *note Logger: af3.
and *note Handler: 13ff. instances (through their *note addFilter():
2bc6. method).  Before deciding to process a message further, both
loggers and handlers consult all their filters for permission.  If any
filter returns a false value, the message is not processed further.

The basic *note Filter: 1193. functionality allows filtering by specific
logger name.  If this feature is used, messages sent to the named logger
and its children are allowed through the filter, and all others dropped.


File: python.info,  Node: Exceptions raised during logging,  Next: Using arbitrary objects as messages,  Prev: Useful Handlers,  Up: 如何使用 Logging 模組

9.7.5 Exceptions raised during logging
--------------------------------------

The logging package is designed to swallow exceptions which occur while
logging in production.  This is so that errors which occur while
handling logging events - such as logging misconfiguration, network or
other similar errors - do not cause the application using logging to
terminate prematurely.

*note SystemExit: ce7. and *note KeyboardInterrupt: 975. exceptions are
never swallowed.  Other exceptions which occur during the *note emit():
2bce. method of a *note Handler: 13ff. subclass are passed to its *note
handleError(): 2bcd. method.

The default implementation of *note handleError(): 2bcd. in *note
Handler: 13ff. checks to see if a module-level variable, *note
raiseExceptions: 1191, is set.  If set, a traceback is printed to *note
sys.stderr: 8dd.  If not set, the exception is swallowed.

     備註: The default value of *note raiseExceptions: 1191. is ‘True’.
     This is because during development, you typically want to be
     notified of any exceptions that occur.  It's advised that you set
     *note raiseExceptions: 1191. to ‘False’ for production usage.


File: python.info,  Node: Using arbitrary objects as messages,  Next: 最佳化<17>,  Prev: Exceptions raised during logging,  Up: 如何使用 Logging 模組

9.7.6 Using arbitrary objects as messages
-----------------------------------------

In the preceding sections and examples, it has been assumed that the
message passed when logging the event is a string.  However, this is not
the only possibility.  You can pass an arbitrary object as a message,
and its *note __str__(): 5c4. method will be called when the logging
system needs to convert it to a string representation.  In fact, if you
want to, you can avoid computing a string representation altogether -
for example, the *note SocketHandler: f05. emits an event by pickling it
and sending it over the wire.


File: python.info,  Node: 最佳化<17>,  Next: 其他資源<2>,  Prev: Using arbitrary objects as messages,  Up: 如何使用 Logging 模組

9.7.7 最佳化
------------

Formatting of message arguments is deferred until it cannot be avoided.
However, computing the arguments passed to the logging method can also
be expensive, and you may want to avoid doing it if the logger will just
throw away your event.  To decide what to do, you can call the *note
isEnabledFor(): 1289. method which takes a level argument and returns
true if the event would be created by the Logger for that level of call.
You can write code like this:

     if logger.isEnabledFor(logging.DEBUG):
         logger.debug('Message with %s, %s', expensive_func1(),
                                             expensive_func2())

so that if the logger's threshold is set above ‘DEBUG’, the calls to
‘expensive_func1’ and ‘expensive_func2’ are never made.

     備註: In some cases, *note isEnabledFor(): 1289. can itself be more
     expensive than you'd like (e.g.  for deeply nested loggers where an
     explicit level is only set high up in the logger hierarchy).  In
     such cases (or if you want to avoid calling a method in tight
     loops), you can cache the result of a call to *note isEnabledFor():
     1289. in a local or instance variable, and use that instead of
     calling the method each time.  Such a cached value would only need
     to be recomputed when the logging configuration changes dynamically
     while the application is running (which is not all that common).

There are other optimizations which can be made for specific
applications which need more precise control over what logging
information is collected.  Here's a list of things you can do to avoid
processing during logging which you don't need:

What you don't want to collect                            How to avoid collecting it
                                                          
------------------------------------------------------------------------------------------------------------------
                                                          
Information about where calls were made from.             Set ‘logging._srcfile’ to ‘None’.  This avoids
                                                          calling *note sys._getframe(): 684, which may help to
                                                          speed up your code in environments like PyPy (which
                                                          can't speed up code that uses
                                                          *note sys._getframe(): 684.).
                                                          
                                                          
Threading information.                                    將 ‘logging.logThreads’ 設為 ‘False’。
                                                          
                                                          
當前的行程 ID (*note os.getpid(): 29eb.)                  將 ‘logging.logProcesses’ 設為 ‘False’。
                                                          
                                                          
Current process name when using ‘multiprocessing’ to      將 ‘logging.logMultiprocessing’ 設為 ‘False’。
manage multiple processes.                                

Current *note asyncio.Task: 480. name when using          將 ‘logging.logAsyncioTasks’ 設為 ‘False’。
‘asyncio’.                                                

Also note that the core logging module only includes the basic handlers.
If you don't import *note logging.handlers: 7d. and *note
logging.config: 7c, they won't take up any memory.


File: python.info,  Node: 其他資源<2>,  Prev: 最佳化<17>,  Up: 如何使用 Logging 模組

9.7.8 其他資源
--------------

也參考
......

*note logging: 7b. 模組

     API reference for the logging module.

*note logging.config: 7c. 模組

     Configuration API for the logging module.

*note logging.handlers: 7d. 模組

     Useful handlers included with the logging module.

*note A logging cookbook: 118f.


File: python.info,  Node: Logging Cookbook,  Next: 如何使用正規表示式,  Prev: 如何使用 Logging 模組,  Up: Python 如何達成任務

9.8 Logging Cookbook
====================


作者: Vinay Sajip <vinay_sajip at red-dove dot com>

This page contains a number of recipes related to logging, which have
been found useful in the past.  For links to tutorial and reference
information, please see *note Other resources: 4d4d.

* Menu:

* Using logging in multiple modules::
* Logging from multiple threads::
* Multiple handlers and formatters::
* Logging to multiple destinations::
* Custom handling of levels::
* Configuration server example::
* Dealing with handlers that block::
* Sending and receiving logging events across a network::
* Adding contextual information to your logging output::
* Use of contextvars::
* Imparting contextual information in handlers::
* Logging to a single file from multiple processes::
* Using file rotation::
* Use of alternative formatting styles::
* Customizing LogRecord::
* Subclassing QueueHandler and QueueListener- a ZeroMQ example::
* Subclassing QueueHandler and QueueListener- a pynng example::
* An example dictionary-based configuration::
* Using a rotator and namer to customize log rotation processing::
* A more elaborate multiprocessing example::
* Inserting a BOM into messages sent to a SysLogHandler::
* Implementing structured logging::
* Customizing handlers with dictConfig(): Customizing handlers with dictConfig.
* Using particular formatting styles throughout your application::
* Configuring filters with dictConfig(): Configuring filters with dictConfig.
* Customized exception formatting::
* Speaking logging messages::
* Buffering logging messages and outputting them conditionally::
* Sending logging messages to email, with buffering: Sending logging messages to email with buffering.
* Formatting times using UTC (GMT) via configuration: Formatting times using UTC GMT via configuration.
* Using a context manager for selective logging::
* A CLI application starter template::
* A Qt GUI for logging::
* Logging to syslog with RFC5424 support::
* How to treat a logger like an output stream::
* Patterns to avoid::
* Other resources::


File: python.info,  Node: Using logging in multiple modules,  Next: Logging from multiple threads,  Up: Logging Cookbook

9.8.1 Using logging in multiple modules
---------------------------------------

Multiple calls to ‘logging.getLogger('someLogger')’ return a reference
to the same logger object.  This is true not only within the same
module, but also across modules as long as it is in the same Python
interpreter process.  It is true for references to the same object;
additionally, application code can define and configure a parent logger
in one module and create (but not configure) a child logger in a
separate module, and all logger calls to the child will pass up to the
parent.  Here is a main module:

     import logging
     import auxiliary_module

     # create logger with 'spam_application'
     logger = logging.getLogger('spam_application')
     logger.setLevel(logging.DEBUG)
     # create file handler which logs even debug messages
     fh = logging.FileHandler('spam.log')
     fh.setLevel(logging.DEBUG)
     # create console handler with a higher log level
     ch = logging.StreamHandler()
     ch.setLevel(logging.ERROR)
     # create formatter and add it to the handlers
     formatter = logging.Formatter('%(asctime)s - %(name)s - %(levelname)s - %(message)s')
     fh.setFormatter(formatter)
     ch.setFormatter(formatter)
     # add the handlers to the logger
     logger.addHandler(fh)
     logger.addHandler(ch)

     logger.info('creating an instance of auxiliary_module.Auxiliary')
     a = auxiliary_module.Auxiliary()
     logger.info('created an instance of auxiliary_module.Auxiliary')
     logger.info('calling auxiliary_module.Auxiliary.do_something')
     a.do_something()
     logger.info('finished auxiliary_module.Auxiliary.do_something')
     logger.info('calling auxiliary_module.some_function()')
     auxiliary_module.some_function()
     logger.info('done with auxiliary_module.some_function()')

Here is the auxiliary module:

     import logging

     # create logger
     module_logger = logging.getLogger('spam_application.auxiliary')

     class Auxiliary:
         def __init__(self):
             self.logger = logging.getLogger('spam_application.auxiliary.Auxiliary')
             self.logger.info('creating an instance of Auxiliary')

         def do_something(self):
             self.logger.info('doing something')
             a = 1 + 1
             self.logger.info('done doing something')

     def some_function():
         module_logger.info('received a call to "some_function"')

The output looks like this:

     2005-03-23 23:47:11,663 - spam_application - INFO -
        creating an instance of auxiliary_module.Auxiliary
     2005-03-23 23:47:11,665 - spam_application.auxiliary.Auxiliary - INFO -
        creating an instance of Auxiliary
     2005-03-23 23:47:11,665 - spam_application - INFO -
        created an instance of auxiliary_module.Auxiliary
     2005-03-23 23:47:11,668 - spam_application - INFO -
        calling auxiliary_module.Auxiliary.do_something
     2005-03-23 23:47:11,668 - spam_application.auxiliary.Auxiliary - INFO -
        doing something
     2005-03-23 23:47:11,669 - spam_application.auxiliary.Auxiliary - INFO -
        done doing something
     2005-03-23 23:47:11,670 - spam_application - INFO -
        finished auxiliary_module.Auxiliary.do_something
     2005-03-23 23:47:11,671 - spam_application - INFO -
        calling auxiliary_module.some_function()
     2005-03-23 23:47:11,672 - spam_application.auxiliary - INFO -
        received a call to 'some_function'
     2005-03-23 23:47:11,673 - spam_application - INFO -
        done with auxiliary_module.some_function()


File: python.info,  Node: Logging from multiple threads,  Next: Multiple handlers and formatters,  Prev: Using logging in multiple modules,  Up: Logging Cookbook

9.8.2 Logging from multiple threads
-----------------------------------

Logging from multiple threads requires no special effort.  The following
example shows logging from the main (initial) thread and another thread:

     import logging
     import threading
     import time

     def worker(arg):
         while not arg['stop']:
             logging.debug('Hi from myfunc')
             time.sleep(0.5)

     def main():
         logging.basicConfig(level=logging.DEBUG, format='%(relativeCreated)6d %(threadName)s %(message)s')
         info = {'stop': False}
         thread = threading.Thread(target=worker, args=(info,))
         thread.start()
         while True:
             try:
                 logging.debug('Hello from main')
                 time.sleep(0.75)
             except KeyboardInterrupt:
                 info['stop'] = True
                 break
         thread.join()

     if __name__ == '__main__':
         main()

When run, the script should print something like the following:

        0 Thread-1 Hi from myfunc
        3 MainThread Hello from main
      505 Thread-1 Hi from myfunc
      755 MainThread Hello from main
     1007 Thread-1 Hi from myfunc
     1507 MainThread Hello from main
     1508 Thread-1 Hi from myfunc
     2010 Thread-1 Hi from myfunc
     2258 MainThread Hello from main
     2512 Thread-1 Hi from myfunc
     3009 MainThread Hello from main
     3013 Thread-1 Hi from myfunc
     3515 Thread-1 Hi from myfunc
     3761 MainThread Hello from main
     4017 Thread-1 Hi from myfunc
     4513 MainThread Hello from main
     4518 Thread-1 Hi from myfunc

This shows the logging output interspersed as one might expect.  This
approach works for more threads than shown here, of course.


File: python.info,  Node: Multiple handlers and formatters,  Next: Logging to multiple destinations,  Prev: Logging from multiple threads,  Up: Logging Cookbook

9.8.3 Multiple handlers and formatters
--------------------------------------

Loggers are plain Python objects.  The *note addHandler(): 2bad. method
has no minimum or maximum quota for the number of handlers you may add.
Sometimes it will be beneficial for an application to log all messages
of all severities to a text file while simultaneously logging errors or
above to the console.  To set this up, simply configure the appropriate
handlers.  The logging calls in the application code will remain
unchanged.  Here is a slight modification to the previous simple
module-based configuration example:

     import logging

     logger = logging.getLogger('simple_example')
     logger.setLevel(logging.DEBUG)
     # create file handler which logs even debug messages
     fh = logging.FileHandler('spam.log')
     fh.setLevel(logging.DEBUG)
     # create console handler with a higher log level
     ch = logging.StreamHandler()
     ch.setLevel(logging.ERROR)
     # create formatter and add it to the handlers
     formatter = logging.Formatter('%(asctime)s - %(name)s - %(levelname)s - %(message)s')
     ch.setFormatter(formatter)
     fh.setFormatter(formatter)
     # add the handlers to logger
     logger.addHandler(ch)
     logger.addHandler(fh)

     # 'application' code
     logger.debug('debug message')
     logger.info('info message')
     logger.warning('warn message')
     logger.error('error message')
     logger.critical('critical message')

Notice that the 'application' code does not care about multiple
handlers.  All that changed was the addition and configuration of a new
handler named 'fh'.

The ability to create new handlers with higher- or lower-severity
filters can be very helpful when writing and testing an application.
Instead of using many ‘print’ statements for debugging, use
‘logger.debug’: Unlike the print statements, which you will have to
delete or comment out later, the logger.debug statements can remain
intact in the source code and remain dormant until you need them again.
At that time, the only change that needs to happen is to modify the
severity level of the logger and/or handler to debug.


File: python.info,  Node: Logging to multiple destinations,  Next: Custom handling of levels,  Prev: Multiple handlers and formatters,  Up: Logging Cookbook

9.8.4 Logging to multiple destinations
--------------------------------------

Let's say you want to log to console and file with different message
formats and in differing circumstances.  Say you want to log messages
with levels of DEBUG and higher to file, and those messages at level
INFO and higher to the console.  Let's also assume that the file should
contain timestamps, but the console messages should not.  Here's how you
can achieve this:

     import logging

     # set up logging to file - see previous section for more details
     logging.basicConfig(level=logging.DEBUG,
                         format='%(asctime)s %(name)-12s %(levelname)-8s %(message)s',
                         datefmt='%m-%d %H:%M',
                         filename='/tmp/myapp.log',
                         filemode='w')
     # define a Handler which writes INFO messages or higher to the sys.stderr
     console = logging.StreamHandler()
     console.setLevel(logging.INFO)
     # set a format which is simpler for console use
     formatter = logging.Formatter('%(name)-12s: %(levelname)-8s %(message)s')
     # tell the handler to use this format
     console.setFormatter(formatter)
     # add the handler to the root logger
     logging.getLogger('').addHandler(console)

     # Now, we can log to the root logger, or any other logger. First the root...
     logging.info('Jackdaws love my big sphinx of quartz.')

     # Now, define a couple of other loggers which might represent areas in your
     # application:

     logger1 = logging.getLogger('myapp.area1')
     logger2 = logging.getLogger('myapp.area2')

     logger1.debug('Quick zephyrs blow, vexing daft Jim.')
     logger1.info('How quickly daft jumping zebras vex.')
     logger2.warning('Jail zesty vixen who grabbed pay from quack.')
     logger2.error('The five boxing wizards jump quickly.')

When you run this, on the console you will see

     root        : INFO     Jackdaws love my big sphinx of quartz.
     myapp.area1 : INFO     How quickly daft jumping zebras vex.
     myapp.area2 : WARNING  Jail zesty vixen who grabbed pay from quack.
     myapp.area2 : ERROR    The five boxing wizards jump quickly.

and in the file you will see something like

     10-22 22:19 root         INFO     Jackdaws love my big sphinx of quartz.
     10-22 22:19 myapp.area1  DEBUG    Quick zephyrs blow, vexing daft Jim.
     10-22 22:19 myapp.area1  INFO     How quickly daft jumping zebras vex.
     10-22 22:19 myapp.area2  WARNING  Jail zesty vixen who grabbed pay from quack.
     10-22 22:19 myapp.area2  ERROR    The five boxing wizards jump quickly.

As you can see, the DEBUG message only shows up in the file.  The other
messages are sent to both destinations.

This example uses console and file handlers, but you can use any number
and combination of handlers you choose.

Note that the above choice of log filename ‘/tmp/myapp.log’ implies use
of a standard location for temporary files on POSIX systems.  On
Windows, you may need to choose a different directory name for the log -
just ensure that the directory exists and that you have the permissions
to create and update files in it.


File: python.info,  Node: Custom handling of levels,  Next: Configuration server example,  Prev: Logging to multiple destinations,  Up: Logging Cookbook

9.8.5 Custom handling of levels
-------------------------------

Sometimes, you might want to do something slightly different from the
standard handling of levels in handlers, where all levels above a
threshold get processed by a handler.  To do this, you need to use
filters.  Let's look at a scenario where you want to arrange things as
follows:

   * Send messages of severity ‘INFO’ and ‘WARNING’ to ‘sys.stdout’

   * Send messages of severity ‘ERROR’ and above to ‘sys.stderr’

   * Send messages of severity ‘DEBUG’ and above to file ‘app.log’

Suppose you configure logging with the following JSON:

     {
         "version": 1,
         "disable_existing_loggers": false,
         "formatters": {
             "simple": {
                 "format": "%(levelname)-8s - %(message)s"
             }
         },
         "handlers": {
             "stdout": {
                 "class": "logging.StreamHandler",
                 "level": "INFO",
                 "formatter": "simple",
                 "stream": "ext://sys.stdout"
             },
             "stderr": {
                 "class": "logging.StreamHandler",
                 "level": "ERROR",
                 "formatter": "simple",
                 "stream": "ext://sys.stderr"
             },
             "file": {
                 "class": "logging.FileHandler",
                 "formatter": "simple",
                 "filename": "app.log",
                 "mode": "w"
             }
         },
         "root": {
             "level": "DEBUG",
             "handlers": [
                 "stderr",
                 "stdout",
                 "file"
             ]
         }
     }

This configuration does 'almost' what we want, except that ‘sys.stdout’
would show messages of severity ‘ERROR’ and only events of this severity
and higher will be tracked as well as ‘INFO’ and ‘WARNING’ messages.  To
prevent this, we can set up a filter which excludes those messages and
add it to the relevant handler.  This can be configured by adding a
‘filters’ section parallel to ‘formatters’ and ‘handlers’:

     {
         "filters": {
             "warnings_and_below": {
                 "()" : "__main__.filter_maker",
                 "level": "WARNING"
             }
         }
     }

and changing the section on the ‘stdout’ handler to add it:

     {
         "stdout": {
             "class": "logging.StreamHandler",
             "level": "INFO",
             "formatter": "simple",
             "stream": "ext://sys.stdout",
             "filters": ["warnings_and_below"]
         }
     }

A filter is just a function, so we can define the ‘filter_maker’ (a
factory function) as follows:

     def filter_maker(level):
         level = getattr(logging, level)

         def filter(record):
             return record.levelno <= level

         return filter

This converts the string argument passed in to a numeric level, and
returns a function which only returns ‘True’ if the level of the passed
in record is at or below the specified level.  Note that in this example
I have defined the ‘filter_maker’ in a test script ‘main.py’ that I run
from the command line, so its module will be ‘__main__’ - hence the
‘__main__.filter_maker’ in the filter configuration.  You will need to
change that if you define it in a different module.

With the filter added, we can run ‘main.py’, which in full is:

     import json
     import logging
     import logging.config

     CONFIG = '''
     {
         "version": 1,
         "disable_existing_loggers": false,
         "formatters": {
             "simple": {
                 "format": "%(levelname)-8s - %(message)s"
             }
         },
         "filters": {
             "warnings_and_below": {
                 "()" : "__main__.filter_maker",
                 "level": "WARNING"
             }
         },
         "handlers": {
             "stdout": {
                 "class": "logging.StreamHandler",
                 "level": "INFO",
                 "formatter": "simple",
                 "stream": "ext://sys.stdout",
                 "filters": ["warnings_and_below"]
             },
             "stderr": {
                 "class": "logging.StreamHandler",
                 "level": "ERROR",
                 "formatter": "simple",
                 "stream": "ext://sys.stderr"
             },
             "file": {
                 "class": "logging.FileHandler",
                 "formatter": "simple",
                 "filename": "app.log",
                 "mode": "w"
             }
         },
         "root": {
             "level": "DEBUG",
             "handlers": [
                 "stderr",
                 "stdout",
                 "file"
             ]
         }
     }
     '''

     def filter_maker(level):
         level = getattr(logging, level)

         def filter(record):
             return record.levelno <= level

         return filter

     logging.config.dictConfig(json.loads(CONFIG))
     logging.debug('A DEBUG message')
     logging.info('An INFO message')
     logging.warning('A WARNING message')
     logging.error('An ERROR message')
     logging.critical('A CRITICAL message')

And after running it like this:

     python main.py 2>stderr.log >stdout.log

We can see the results are as expected:

     $ more *.log
     ::::::::::::::
     app.log
     ::::::::::::::
     DEBUG    - A DEBUG message
     INFO     - An INFO message
     WARNING  - A WARNING message
     ERROR    - An ERROR message
     CRITICAL - A CRITICAL message
     ::::::::::::::
     stderr.log
     ::::::::::::::
     ERROR    - An ERROR message
     CRITICAL - A CRITICAL message
     ::::::::::::::
     stdout.log
     ::::::::::::::
     INFO     - An INFO message
     WARNING  - A WARNING message


File: python.info,  Node: Configuration server example,  Next: Dealing with handlers that block,  Prev: Custom handling of levels,  Up: Logging Cookbook

9.8.6 Configuration server example
----------------------------------

Here is an example of a module using the logging configuration server:

     import logging
     import logging.config
     import time
     import os

     # read initial config file
     logging.config.fileConfig('logging.conf')

     # create and start listener on port 9999
     t = logging.config.listen(9999)
     t.start()

     logger = logging.getLogger('simpleExample')

     try:
         # loop through logging calls to see the difference
         # new configurations make, until Ctrl+C is pressed
         while True:
             logger.debug('debug message')
             logger.info('info message')
             logger.warning('warn message')
             logger.error('error message')
             logger.critical('critical message')
             time.sleep(5)
     except KeyboardInterrupt:
         # cleanup
         logging.config.stopListening()
         t.join()

And here is a script that takes a filename and sends that file to the
server, properly preceded with the binary-encoded length, as the new
logging configuration:

     #!/usr/bin/env python
     import socket, sys, struct

     with open(sys.argv[1], 'rb') as f:
         data_to_send = f.read()

     HOST = 'localhost'
     PORT = 9999
     s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
     print('connecting...')
     s.connect((HOST, PORT))
     print('sending config...')
     s.send(struct.pack('>L', len(data_to_send)))
     s.send(data_to_send)
     s.close()
     print('complete')


File: python.info,  Node: Dealing with handlers that block,  Next: Sending and receiving logging events across a network,  Prev: Configuration server example,  Up: Logging Cookbook

9.8.7 Dealing with handlers that block
--------------------------------------

Sometimes you have to get your logging handlers to do their work without
blocking the thread you're logging from.  This is common in web
applications, though of course it also occurs in other scenarios.

A common culprit which demonstrates sluggish behaviour is the *note
SMTPHandler: 2c5e.: sending emails can take a long time, for a number of
reasons outside the developer's control (for example, a poorly
performing mail or network infrastructure).  But almost any
network-based handler can block: Even a *note SocketHandler: f05.
operation may do a DNS query under the hood which is too slow (and this
query can be deep in the socket library code, below the Python layer,
and outside your control).

One solution is to use a two-part approach.  For the first part, attach
only a *note QueueHandler: 16dc. to those loggers which are accessed
from performance-critical threads.  They simply write to their queue,
which can be sized to a large enough capacity or initialized with no
upper bound to their size.  The write to the queue will typically be
accepted quickly, though you will probably need to catch the *note
queue.Full: 2f8b. exception as a precaution in your code.  If you are a
library developer who has performance-critical threads in their code, be
sure to document this (together with a suggestion to attach only
‘QueueHandlers’ to your loggers) for the benefit of other developers who
will use your code.

The second part of the solution is *note QueueListener: dd2, which has
been designed as the counterpart to *note QueueHandler: 16dc.  A *note
QueueListener: dd2. is very simple: it's passed a queue and some
handlers, and it fires up an internal thread which listens to its queue
for LogRecords sent from ‘QueueHandlers’ (or any other source of
‘LogRecords’, for that matter).  The ‘LogRecords’ are removed from the
queue and passed to the handlers for processing.

The advantage of having a separate *note QueueListener: dd2. class is
that you can use the same instance to service multiple ‘QueueHandlers’.
This is more resource-friendly than, say, having threaded versions of
the existing handler classes, which would eat up one thread per handler
for no particular benefit.

An example of using these two classes follows (imports omitted):

     que = queue.Queue(-1)  # no limit on size
     queue_handler = QueueHandler(que)
     handler = logging.StreamHandler()
     listener = QueueListener(que, handler)
     root = logging.getLogger()
     root.addHandler(queue_handler)
     formatter = logging.Formatter('%(threadName)s: %(message)s')
     handler.setFormatter(formatter)
     listener.start()
     # The log output will display the thread which generated
     # the event (the main thread) rather than the internal
     # thread which monitors the internal queue. This is what
     # you want to happen.
     root.warning('Look out!')
     listener.stop()

which, when run, will produce:

     MainThread: Look out!

     備註: Although the earlier discussion wasn't specifically talking
     about async code, but rather about slow logging handlers, it should
     be noted that when logging from async code, network and even file
     handlers could lead to problems (blocking the event loop) because
     some logging is done from *note asyncio: 8. internals.  It might be
     best, if any async code is used in an application, to use the above
     approach for logging, so that any blocking code runs only in the
     ‘QueueListener’ thread.

在 3.5 版的變更: Prior to Python 3.5, the *note QueueListener: dd2.
always passed every message received from the queue to every handler it
was initialized with.  (This was because it was assumed that level
filtering was all done on the other side, where the queue is filled.)
From 3.5 onwards, this behaviour can be changed by passing a keyword
argument ‘respect_handler_level=True’ to the listener's constructor.
When this is done, the listener compares the level of each message with
the handler's level, and only passes a message to a handler if it's
appropriate to do so.


File: python.info,  Node: Sending and receiving logging events across a network,  Next: Adding contextual information to your logging output,  Prev: Dealing with handlers that block,  Up: Logging Cookbook

9.8.8 Sending and receiving logging events across a network
-----------------------------------------------------------

Let's say you want to send logging events across a network, and handle
them at the receiving end.  A simple way of doing this is attaching a
*note SocketHandler: f05. instance to the root logger at the sending
end:

     import logging, logging.handlers

     rootLogger = logging.getLogger('')
     rootLogger.setLevel(logging.DEBUG)
     socketHandler = logging.handlers.SocketHandler('localhost',
                         logging.handlers.DEFAULT_TCP_LOGGING_PORT)
     # don't bother with a formatter, since a socket handler sends the event as
     # an unformatted pickle
     rootLogger.addHandler(socketHandler)

     # Now, we can log to the root logger, or any other logger. First the root...
     logging.info('Jackdaws love my big sphinx of quartz.')

     # Now, define a couple of other loggers which might represent areas in your
     # application:

     logger1 = logging.getLogger('myapp.area1')
     logger2 = logging.getLogger('myapp.area2')

     logger1.debug('Quick zephyrs blow, vexing daft Jim.')
     logger1.info('How quickly daft jumping zebras vex.')
     logger2.warning('Jail zesty vixen who grabbed pay from quack.')
     logger2.error('The five boxing wizards jump quickly.')

At the receiving end, you can set up a receiver using the *note
socketserver: b9. module.  Here is a basic working example:

     import pickle
     import logging
     import logging.handlers
     import socketserver
     import struct


     class LogRecordStreamHandler(socketserver.StreamRequestHandler):
         """Handler for a streaming logging request.

         This basically logs the record using whatever logging policy is
         configured locally.
         """

         def handle(self):
             """
             Handle multiple requests - each expected to be a 4-byte length,
             followed by the LogRecord in pickle format. Logs the record
             according to whatever policy is configured locally.
             """
             while True:
                 chunk = self.connection.recv(4)
                 if len(chunk) < 4:
                     break
                 slen = struct.unpack('>L', chunk)[0]
                 chunk = self.connection.recv(slen)
                 while len(chunk) < slen:
                     chunk = chunk + self.connection.recv(slen - len(chunk))
                 obj = self.unPickle(chunk)
                 record = logging.makeLogRecord(obj)
                 self.handleLogRecord(record)

         def unPickle(self, data):
             return pickle.loads(data)

         def handleLogRecord(self, record):
             # if a name is specified, we use the named logger rather than the one
             # implied by the record.
             if self.server.logname is not None:
                 name = self.server.logname
             else:
                 name = record.name
             logger = logging.getLogger(name)
             # N.B. EVERY record gets logged. This is because Logger.handle
             # is normally called AFTER logger-level filtering. If you want
             # to do filtering, do it at the client end to save wasting
             # cycles and network bandwidth!
             logger.handle(record)

     class LogRecordSocketReceiver(socketserver.ThreadingTCPServer):
         """
         Simple TCP socket-based logging receiver suitable for testing.
         """

         allow_reuse_address = True

         def __init__(self, host='localhost',
                      port=logging.handlers.DEFAULT_TCP_LOGGING_PORT,
                      handler=LogRecordStreamHandler):
             socketserver.ThreadingTCPServer.__init__(self, (host, port), handler)
             self.abort = 0
             self.timeout = 1
             self.logname = None

         def serve_until_stopped(self):
             import select
             abort = 0
             while not abort:
                 rd, wr, ex = select.select([self.socket.fileno()],
                                            [], [],
                                            self.timeout)
                 if rd:
                     self.handle_request()
                 abort = self.abort

     def main():
         logging.basicConfig(
             format='%(relativeCreated)5d %(name)-15s %(levelname)-8s %(message)s')
         tcpserver = LogRecordSocketReceiver()
         print('About to start TCP server...')
         tcpserver.serve_until_stopped()

     if __name__ == '__main__':
         main()

First run the server, and then the client.  On the client side, nothing
is printed on the console; on the server side, you should see something
like:

     About to start TCP server...
        59 root            INFO     Jackdaws love my big sphinx of quartz.
        59 myapp.area1     DEBUG    Quick zephyrs blow, vexing daft Jim.
        69 myapp.area1     INFO     How quickly daft jumping zebras vex.
        69 myapp.area2     WARNING  Jail zesty vixen who grabbed pay from quack.
        69 myapp.area2     ERROR    The five boxing wizards jump quickly.

Note that there are some security issues with pickle in some scenarios.
If these affect you, you can use an alternative serialization scheme by
overriding the *note makePickle(): 2c47. method and implementing your
alternative there, as well as adapting the above script to use your
alternative serialization.

* Menu:

* Running a logging socket listener in production::


File: python.info,  Node: Running a logging socket listener in production,  Up: Sending and receiving logging events across a network

9.8.8.1 Running a logging socket listener in production
.......................................................

To run a logging listener in production, you may need to use a
process-management tool such as Supervisor(1).  Here is a Gist(2) which
provides the bare-bones files to run the above functionality using
Supervisor.  It consists of the following files:

檔案                          目的
                              
---------------------------------------------------------------------------------------
                              
‘prepare.sh’                  A Bash script to prepare the environment for testing
                              
                              
‘supervisor.conf’             The Supervisor configuration file, which has entries
                              for the listener and a multi-process web application
                              
                              
‘ensure_app.sh’               A Bash script to ensure that Supervisor is running
                              with the above configuration
                              
                              
‘log_listener.py’             The socket listener program which receives log events
                              and records them to a file
                              
                              
‘main.py’                     A simple web application which performs logging via a
                              socket connected to the listener
                              
                              
‘webapp.json’                 A JSON configuration file for the web application
                              
                              
‘client.py’                   A Python script to exercise the web application
                              

The web application uses Gunicorn(3), which is a popular web application
server that starts multiple worker processes to handle requests.  This
example setup shows how the workers can write to the same log file
without conflicting with one another -- they all go through the socket
listener.

To test these files, do the following in a POSIX environment:

  1. Download the Gist(4) as a ZIP archive using the Download ZIP
     button.

  2. Unzip the above files from the archive into a scratch directory.

  3. In the scratch directory, run ‘bash prepare.sh’ to get things
     ready.  This creates a ‘run’ subdirectory to contain
     Supervisor-related and log files, and a ‘venv’ subdirectory to
     contain a virtual environment into which ‘bottle’, ‘gunicorn’ and
     ‘supervisor’ are installed.

  4. Run ‘bash ensure_app.sh’ to ensure that Supervisor is running with
     the above configuration.

  5. Run ‘venv/bin/python client.py’ to exercise the web application,
     which will lead to records being written to the log.

  6. Inspect the log files in the ‘run’ subdirectory.  You should see
     the most recent log lines in files matching the pattern ‘app.log*’.
     They won't be in any particular order, since they have been handled
     concurrently by different worker processes in a non-deterministic
     way.

  7. You can shut down the listener and the web application by running
     ‘venv/bin/supervisorctl -c supervisor.conf shutdown’.

You may need to tweak the configuration files in the unlikely event that
the configured ports clash with something else in your test environment.

   ---------- Footnotes ----------

   (1) http://supervisord.org/

   (2) https://gist.github.com/vsajip/4b227eeec43817465ca835ca66f75e2b

   (3) https://gunicorn.org/

   (4) https://gist.github.com/vsajip/4b227eeec43817465ca835ca66f75e2b


File: python.info,  Node: Adding contextual information to your logging output,  Next: Use of contextvars,  Prev: Sending and receiving logging events across a network,  Up: Logging Cookbook

9.8.9 Adding contextual information to your logging output
----------------------------------------------------------

Sometimes you want logging output to contain contextual information in
addition to the parameters passed to the logging call.  For example, in
a networked application, it may be desirable to log client-specific
information in the log (e.g.  remote client's username, or IP address).
Although you could use the 'extra' parameter to achieve this, it's not
always convenient to pass the information in this way.  While it might
be tempting to create *note Logger: af3. instances on a per-connection
basis, this is not a good idea because these instances are not garbage
collected.  While this is not a problem in practice, when the number of
*note Logger: af3. instances is dependent on the level of granularity
you want to use in logging an application, it could be hard to manage if
the number of *note Logger: af3. instances becomes effectively
unbounded.

* Menu:

* Using LoggerAdapters to impart contextual information::
* Using Filters to impart contextual information::


File: python.info,  Node: Using LoggerAdapters to impart contextual information,  Next: Using Filters to impart contextual information,  Up: Adding contextual information to your logging output

9.8.9.1 Using LoggerAdapters to impart contextual information
.............................................................

An easy way in which you can pass contextual information to be output
along with logging event information is to use the *note LoggerAdapter:
1288. class.  This class is designed to look like a *note Logger: af3,
so that you can call *note debug(): 2bb4, *note info(): 2bde, *note
warning(): 2d0, *note error(): 2bf2, *note exception(): 13fd, *note
critical(): 2bf3. and *note log(): 2bf4.  These methods have the same
signatures as their counterparts in *note Logger: af3, so you can use
the two types of instances interchangeably.

When you create an instance of *note LoggerAdapter: 1288, you pass it a
*note Logger: af3. instance and a dict-like object which contains your
contextual information.  When you call one of the logging methods on an
instance of *note LoggerAdapter: 1288, it delegates the call to the
underlying instance of *note Logger: af3. passed to its constructor, and
arranges to pass the contextual information in the delegated call.
Here's a snippet from the code of *note LoggerAdapter: 1288.:

     def debug(self, msg, /, *args, **kwargs):
         """
         Delegate a debug call to the underlying logger, after adding
         contextual information from this adapter instance.
         """
         msg, kwargs = self.process(msg, kwargs)
         self.logger.debug(msg, *args, **kwargs)

The *note process(): 2beb. method of *note LoggerAdapter: 1288. is where
the contextual information is added to the logging output.  It's passed
the message and keyword arguments of the logging call, and it passes
back (potentially) modified versions of these to use in the call to the
underlying logger.  The default implementation of this method leaves the
message alone, but inserts an 'extra' key in the keyword argument whose
value is the dict-like object passed to the constructor.  Of course, if
you had passed an 'extra' keyword argument in the call to the adapter,
it will be silently overwritten.

The advantage of using 'extra' is that the values in the dict-like
object are merged into the *note LogRecord: f89. instance's __dict__,
allowing you to use customized strings with your *note Formatter: 1400.
instances which know about the keys of the dict-like object.  If you
need a different method, e.g.  if you want to prepend or append the
contextual information to the message string, you just need to subclass
*note LoggerAdapter: 1288. and override *note process(): 2beb. to do
what you need.  Here is a simple example:

     class CustomAdapter(logging.LoggerAdapter):
         """
         This example adapter expects the passed in dict-like object to have a
         'connid' key, whose value in brackets is prepended to the log message.
         """
         def process(self, msg, kwargs):
             return '[%s] %s' % (self.extra['connid'], msg), kwargs

which you can use like this:

     logger = logging.getLogger(__name__)
     adapter = CustomAdapter(logger, {'connid': some_conn_id})

Then any events that you log to the adapter will have the value of
‘some_conn_id’ prepended to the log messages.

* Menu:

* Using objects other than dicts to pass contextual information::


File: python.info,  Node: Using objects other than dicts to pass contextual information,  Up: Using LoggerAdapters to impart contextual information

9.8.9.2 Using objects other than dicts to pass contextual information
.....................................................................

You don't need to pass an actual dict to a *note LoggerAdapter: 1288. -
you could pass an instance of a class which implements ‘__getitem__’ and
‘__iter__’ so that it looks like a dict to logging.  This would be
useful if you want to generate values dynamically (whereas the values in
a dict would be constant).


File: python.info,  Node: Using Filters to impart contextual information,  Prev: Using LoggerAdapters to impart contextual information,  Up: Adding contextual information to your logging output

9.8.9.3 Using Filters to impart contextual information
......................................................

You can also add contextual information to log output using a
user-defined *note Filter: 1193.  ‘Filter’ instances are allowed to
modify the ‘LogRecords’ passed to them, including adding additional
attributes which can then be output using a suitable format string, or
if needed a custom *note Formatter: 1400.

For example in a web application, the request being processed (or at
least, the interesting parts of it) can be stored in a threadlocal
(*note threading.local: 166d.) variable, and then accessed from a
‘Filter’ to add, say, information from the request - say, the remote IP
address and remote user's username - to the ‘LogRecord’, using the
attribute names 'ip' and 'user' as in the ‘LoggerAdapter’ example above.
In that case, the same format string can be used to get similar output
to that shown above.  Here's an example script:

     import logging
     from random import choice

     class ContextFilter(logging.Filter):
         """
         This is a filter which injects contextual information into the log.

         Rather than use actual contextual information, we just use random
         data in this demo.
         """

         USERS = ['jim', 'fred', 'sheila']
         IPS = ['123.231.231.123', '127.0.0.1', '192.168.0.1']

         def filter(self, record):

             record.ip = choice(ContextFilter.IPS)
             record.user = choice(ContextFilter.USERS)
             return True

     if __name__ == '__main__':
         levels = (logging.DEBUG, logging.INFO, logging.WARNING, logging.ERROR, logging.CRITICAL)
         logging.basicConfig(level=logging.DEBUG,
                             format='%(asctime)-15s %(name)-5s %(levelname)-8s IP: %(ip)-15s User: %(user)-8s %(message)s')
         a1 = logging.getLogger('a.b.c')
         a2 = logging.getLogger('d.e.f')

         f = ContextFilter()
         a1.addFilter(f)
         a2.addFilter(f)
         a1.debug('A debug message')
         a1.info('An info message with %s', 'some parameters')
         for x in range(10):
             lvl = choice(levels)
             lvlname = logging.getLevelName(lvl)
             a2.log(lvl, 'A message at %s level with %d %s', lvlname, 2, 'parameters')

which, when run, produces something like:

     2010-09-06 22:38:15,292 a.b.c DEBUG    IP: 123.231.231.123 User: fred     A debug message
     2010-09-06 22:38:15,300 a.b.c INFO     IP: 192.168.0.1     User: sheila   An info message with some parameters
     2010-09-06 22:38:15,300 d.e.f CRITICAL IP: 127.0.0.1       User: sheila   A message at CRITICAL level with 2 parameters
     2010-09-06 22:38:15,300 d.e.f ERROR    IP: 127.0.0.1       User: jim      A message at ERROR level with 2 parameters
     2010-09-06 22:38:15,300 d.e.f DEBUG    IP: 127.0.0.1       User: sheila   A message at DEBUG level with 2 parameters
     2010-09-06 22:38:15,300 d.e.f ERROR    IP: 123.231.231.123 User: fred     A message at ERROR level with 2 parameters
     2010-09-06 22:38:15,300 d.e.f CRITICAL IP: 192.168.0.1     User: jim      A message at CRITICAL level with 2 parameters
     2010-09-06 22:38:15,300 d.e.f CRITICAL IP: 127.0.0.1       User: sheila   A message at CRITICAL level with 2 parameters
     2010-09-06 22:38:15,300 d.e.f DEBUG    IP: 192.168.0.1     User: jim      A message at DEBUG level with 2 parameters
     2010-09-06 22:38:15,301 d.e.f ERROR    IP: 127.0.0.1       User: sheila   A message at ERROR level with 2 parameters
     2010-09-06 22:38:15,301 d.e.f DEBUG    IP: 123.231.231.123 User: fred     A message at DEBUG level with 2 parameters
     2010-09-06 22:38:15,301 d.e.f INFO     IP: 123.231.231.123 User: fred     A message at INFO level with 2 parameters


File: python.info,  Node: Use of contextvars,  Next: Imparting contextual information in handlers,  Prev: Adding contextual information to your logging output,  Up: Logging Cookbook

9.8.10 Use of ‘contextvars’
---------------------------

Since Python 3.7, the *note contextvars: 1d. module has provided
context-local storage which works for both *note threading: d6. and
*note asyncio: 8. processing needs.  This type of storage may thus be
generally preferable to thread-locals.  The following example shows how,
in a multi-threaded environment, logs can populated with contextual
information such as, for example, request attributes handled by web
applications.

For the purposes of illustration, say that you have different web
applications, each independent of the other but running in the same
Python process and using a library common to them.  How can each of
these applications have their own log, where all logging messages from
the library (and other request processing code) are directed to the
appropriate application's log file, while including in the log
additional contextual information such as client IP, HTTP request method
and client username?

Let's assume that the library can be simulated by the following code:

     # webapplib.py
     import logging
     import time

     logger = logging.getLogger(__name__)

     def useful():
         # Just a representative event logged from the library
         logger.debug('Hello from webapplib!')
         # Just sleep for a bit so other threads get to run
         time.sleep(0.01)

We can simulate the multiple web applications by means of two simple
classes, ‘Request’ and ‘WebApp’.  These simulate how real threaded web
applications work - each request is handled by a thread:

     # main.py
     import argparse
     from contextvars import ContextVar
     import logging
     import os
     from random import choice
     import threading
     import webapplib

     logger = logging.getLogger(__name__)
     root = logging.getLogger()
     root.setLevel(logging.DEBUG)

     class Request:
         """
         A simple dummy request class which just holds dummy HTTP request method,
         client IP address and client username
         """
         def __init__(self, method, ip, user):
             self.method = method
             self.ip = ip
             self.user = user

     # A dummy set of requests which will be used in the simulation - we'll just pick
     # from this list randomly. Note that all GET requests are from 192.168.2.XXX
     # addresses, whereas POST requests are from 192.16.3.XXX addresses. Three users
     # are represented in the sample requests.

     REQUESTS = [
         Request('GET', '192.168.2.20', 'jim'),
         Request('POST', '192.168.3.20', 'fred'),
         Request('GET', '192.168.2.21', 'sheila'),
         Request('POST', '192.168.3.21', 'jim'),
         Request('GET', '192.168.2.22', 'fred'),
         Request('POST', '192.168.3.22', 'sheila'),
     ]

     # Note that the format string includes references to request context information
     # such as HTTP method, client IP and username

     formatter = logging.Formatter('%(threadName)-11s %(appName)s %(name)-9s %(user)-6s %(ip)s %(method)-4s %(message)s')

     # Create our context variables. These will be filled at the start of request
     # processing, and used in the logging that happens during that processing

     ctx_request = ContextVar('request')
     ctx_appname = ContextVar('appname')

     class InjectingFilter(logging.Filter):
         """
         A filter which injects context-specific information into logs and ensures
         that only information for a specific webapp is included in its log
         """
         def __init__(self, app):
             self.app = app

         def filter(self, record):
             request = ctx_request.get()
             record.method = request.method
             record.ip = request.ip
             record.user = request.user
             record.appName = appName = ctx_appname.get()
             return appName == self.app.name

     class WebApp:
         """
         A dummy web application class which has its own handler and filter for a
         webapp-specific log.
         """
         def __init__(self, name):
             self.name = name
             handler = logging.FileHandler(name + '.log', 'w')
             f = InjectingFilter(self)
             handler.setFormatter(formatter)
             handler.addFilter(f)
             root.addHandler(handler)
             self.num_requests = 0

         def process_request(self, request):
             """
             This is the dummy method for processing a request. It's called on a
             different thread for every request. We store the context information into
             the context vars before doing anything else.
             """
             ctx_request.set(request)
             ctx_appname.set(self.name)
             self.num_requests += 1
             logger.debug('Request processing started')
             webapplib.useful()
             logger.debug('Request processing finished')

     def main():
         fn = os.path.splitext(os.path.basename(__file__))[0]
         adhf = argparse.ArgumentDefaultsHelpFormatter
         ap = argparse.ArgumentParser(formatter_class=adhf, prog=fn,
                                      description='Simulate a couple of web '
                                                  'applications handling some '
                                                  'requests, showing how request '
                                                  'context can be used to '
                                                  'populate logs')
         aa = ap.add_argument
         aa('--count', '-c', type=int, default=100, help='How many requests to simulate')
         options = ap.parse_args()

         # Create the dummy webapps and put them in a list which we can use to select
         # from randomly
         app1 = WebApp('app1')
         app2 = WebApp('app2')
         apps = [app1, app2]
         threads = []
         # Add a common handler which will capture all events
         handler = logging.FileHandler('app.log', 'w')
         handler.setFormatter(formatter)
         root.addHandler(handler)

         # Generate calls to process requests
         for i in range(options.count):
             try:
                 # Pick an app at random and a request for it to process
                 app = choice(apps)
                 request = choice(REQUESTS)
                 # Process the request in its own thread
                 t = threading.Thread(target=app.process_request, args=(request,))
                 threads.append(t)
                 t.start()
             except KeyboardInterrupt:
                 break

         # Wait for the threads to terminate
         for t in threads:
             t.join()

         for app in apps:
             print('%s processed %s requests' % (app.name, app.num_requests))

     if __name__ == '__main__':
         main()

If you run the above, you should find that roughly half the requests go
into ‘app1.log’ and the rest into ‘app2.log’, and the all the requests
are logged to ‘app.log’.  Each webapp-specific log will contain only log
entries for only that webapp, and the request information will be
displayed consistently in the log (i.e.  the information in each dummy
request will always appear together in a log line).  This is illustrated
by the following shell output:

     ~/logging-contextual-webapp$ python main.py
     app1 processed 51 requests
     app2 processed 49 requests
     ~/logging-contextual-webapp$ wc -l *.log
       153 app1.log
       147 app2.log
       300 app.log
       600 total
     ~/logging-contextual-webapp$ head -3 app1.log
     Thread-3 (process_request) app1 __main__  jim    192.168.3.21 POST Request processing started
     Thread-3 (process_request) app1 webapplib jim    192.168.3.21 POST Hello from webapplib!
     Thread-5 (process_request) app1 __main__  jim    192.168.3.21 POST Request processing started
     ~/logging-contextual-webapp$ head -3 app2.log
     Thread-1 (process_request) app2 __main__  sheila 192.168.2.21 GET  Request processing started
     Thread-1 (process_request) app2 webapplib sheila 192.168.2.21 GET  Hello from webapplib!
     Thread-2 (process_request) app2 __main__  jim    192.168.2.20 GET  Request processing started
     ~/logging-contextual-webapp$ head app.log
     Thread-1 (process_request) app2 __main__  sheila 192.168.2.21 GET  Request processing started
     Thread-1 (process_request) app2 webapplib sheila 192.168.2.21 GET  Hello from webapplib!
     Thread-2 (process_request) app2 __main__  jim    192.168.2.20 GET  Request processing started
     Thread-3 (process_request) app1 __main__  jim    192.168.3.21 POST Request processing started
     Thread-2 (process_request) app2 webapplib jim    192.168.2.20 GET  Hello from webapplib!
     Thread-3 (process_request) app1 webapplib jim    192.168.3.21 POST Hello from webapplib!
     Thread-4 (process_request) app2 __main__  fred   192.168.2.22 GET  Request processing started
     Thread-5 (process_request) app1 __main__  jim    192.168.3.21 POST Request processing started
     Thread-4 (process_request) app2 webapplib fred   192.168.2.22 GET  Hello from webapplib!
     Thread-6 (process_request) app1 __main__  jim    192.168.3.21 POST Request processing started
     ~/logging-contextual-webapp$ grep app1 app1.log | wc -l
     153
     ~/logging-contextual-webapp$ grep app2 app2.log | wc -l
     147
     ~/logging-contextual-webapp$ grep app1 app.log | wc -l
     153
     ~/logging-contextual-webapp$ grep app2 app.log | wc -l
     147


File: python.info,  Node: Imparting contextual information in handlers,  Next: Logging to a single file from multiple processes,  Prev: Use of contextvars,  Up: Logging Cookbook

9.8.11 Imparting contextual information in handlers
---------------------------------------------------

Each *note Handler: 13ff. has its own chain of filters.  If you want to
add contextual information to a *note LogRecord: f89. without leaking it
to other handlers, you can use a filter that returns a new *note
LogRecord: f89. instead of modifying it in-place, as shown in the
following script:

     import copy
     import logging

     def filter(record: logging.LogRecord):
         record = copy.copy(record)
         record.user = 'jim'
         return record

     if __name__ == '__main__':
         logger = logging.getLogger()
         logger.setLevel(logging.INFO)
         handler = logging.StreamHandler()
         formatter = logging.Formatter('%(message)s from %(user)-8s')
         handler.setFormatter(formatter)
         handler.addFilter(filter)
         logger.addHandler(handler)

         logger.info('A log message')


File: python.info,  Node: Logging to a single file from multiple processes,  Next: Using file rotation,  Prev: Imparting contextual information in handlers,  Up: Logging Cookbook

9.8.12 Logging to a single file from multiple processes
-------------------------------------------------------

Although logging is thread-safe, and logging to a single file from
multiple threads in a single process 'is' supported, logging to a single
file from 'multiple processes' is 'not' supported, because there is no
standard way to serialize access to a single file across multiple
processes in Python.  If you need to log to a single file from multiple
processes, one way of doing this is to have all the processes log to a
*note SocketHandler: f05, and have a separate process which implements a
socket server which reads from the socket and logs to file.  (If you
prefer, you can dedicate one thread in one of the existing processes to
perform this function.)  *note This section: 4d57. documents this
approach in more detail and includes a working socket receiver which can
be used as a starting point for you to adapt in your own applications.

You could also write your own handler which uses the *note Lock: 2f6e.
class from the *note multiprocessing: 86. module to serialize access to
the file from your processes.  The existing *note FileHandler: 17a1. and
subclasses do not make use of *note multiprocessing: 86. at present,
though they may do so in the future.  Note that at present, the *note
multiprocessing: 86. module does not provide working lock functionality
on all platforms (see ‘https://bugs.python.org/issue3770’).

Alternatively, you can use a ‘Queue’ and a *note QueueHandler: 16dc. to
send all logging events to one of the processes in your multi-process
application.  The following example script demonstrates how you can do
this; in the example a separate listener process listens for events sent
by other processes and logs them according to its own logging
configuration.  Although the example only demonstrates one way of doing
it (for example, you may want to use a listener thread rather than a
separate listener process - the implementation would be analogous) it
does allow for completely different logging configurations for the
listener and the other processes in your application, and can be used as
the basis for code meeting your own specific requirements:

     # You'll need these imports in your own code
     import logging
     import logging.handlers
     import multiprocessing

     # Next two import lines for this demo only
     from random import choice, random
     import time

     #
     # Because you'll want to define the logging configurations for listener and workers, the
     # listener and worker process functions take a configurer parameter which is a callable
     # for configuring logging for that process. These functions are also passed the queue,
     # which they use for communication.
     #
     # In practice, you can configure the listener however you want, but note that in this
     # simple example, the listener does not apply level or filter logic to received records.
     # In practice, you would probably want to do this logic in the worker processes, to avoid
     # sending events which would be filtered out between processes.
     #
     # The size of the rotated files is made small so you can see the results easily.
     def listener_configurer():
         root = logging.getLogger()
         h = logging.handlers.RotatingFileHandler('mptest.log', 'a', 300, 10)
         f = logging.Formatter('%(asctime)s %(processName)-10s %(name)s %(levelname)-8s %(message)s')
         h.setFormatter(f)
         root.addHandler(h)

     # This is the listener process top-level loop: wait for logging events
     # (LogRecords)on the queue and handle them, quit when you get a None for a
     # LogRecord.
     def listener_process(queue, configurer):
         configurer()
         while True:
             try:
                 record = queue.get()
                 if record is None:  # We send this as a sentinel to tell the listener to quit.
                     break
                 logger = logging.getLogger(record.name)
                 logger.handle(record)  # No level or filter logic applied - just do it!
             except Exception:
                 import sys, traceback
                 print('Whoops! Problem:', file=sys.stderr)
                 traceback.print_exc(file=sys.stderr)

     # Arrays used for random selections in this demo

     LEVELS = [logging.DEBUG, logging.INFO, logging.WARNING,
               logging.ERROR, logging.CRITICAL]

     LOGGERS = ['a.b.c', 'd.e.f']

     MESSAGES = [
         'Random message #1',
         'Random message #2',
         'Random message #3',
     ]

     # The worker configuration is done at the start of the worker process run.
     # Note that on Windows you can't rely on fork semantics, so each process
     # will run the logging configuration code when it starts.
     def worker_configurer(queue):
         h = logging.handlers.QueueHandler(queue)  # Just the one handler needed
         root = logging.getLogger()
         root.addHandler(h)
         # send all messages, for demo; no other level or filter logic applied.
         root.setLevel(logging.DEBUG)

     # This is the worker process top-level loop, which just logs ten events with
     # random intervening delays before terminating.
     # The print messages are just so you know it's doing something!
     def worker_process(queue, configurer):
         configurer(queue)
         name = multiprocessing.current_process().name
         print('Worker started: %s' % name)
         for i in range(10):
             time.sleep(random())
             logger = logging.getLogger(choice(LOGGERS))
             level = choice(LEVELS)
             message = choice(MESSAGES)
             logger.log(level, message)
         print('Worker finished: %s' % name)

     # Here's where the demo gets orchestrated. Create the queue, create and start
     # the listener, create ten workers and start them, wait for them to finish,
     # then send a None to the queue to tell the listener to finish.
     def main():
         queue = multiprocessing.Queue(-1)
         listener = multiprocessing.Process(target=listener_process,
                                            args=(queue, listener_configurer))
         listener.start()
         workers = []
         for i in range(10):
             worker = multiprocessing.Process(target=worker_process,
                                              args=(queue, worker_configurer))
             workers.append(worker)
             worker.start()
         for w in workers:
             w.join()
         queue.put_nowait(None)
         listener.join()

     if __name__ == '__main__':
         main()

A variant of the above script keeps the logging in the main process, in
a separate thread:

     import logging
     import logging.config
     import logging.handlers
     from multiprocessing import Process, Queue
     import random
     import threading
     import time

     def logger_thread(q):
         while True:
             record = q.get()
             if record is None:
                 break
             logger = logging.getLogger(record.name)
             logger.handle(record)


     def worker_process(q):
         qh = logging.handlers.QueueHandler(q)
         root = logging.getLogger()
         root.setLevel(logging.DEBUG)
         root.addHandler(qh)
         levels = [logging.DEBUG, logging.INFO, logging.WARNING, logging.ERROR,
                   logging.CRITICAL]
         loggers = ['foo', 'foo.bar', 'foo.bar.baz',
                    'spam', 'spam.ham', 'spam.ham.eggs']
         for i in range(100):
             lvl = random.choice(levels)
             logger = logging.getLogger(random.choice(loggers))
             logger.log(lvl, 'Message no. %d', i)

     if __name__ == '__main__':
         q = Queue()
         d = {
             'version': 1,
             'formatters': {
                 'detailed': {
                     'class': 'logging.Formatter',
                     'format': '%(asctime)s %(name)-15s %(levelname)-8s %(processName)-10s %(message)s'
                 }
             },
             'handlers': {
                 'console': {
                     'class': 'logging.StreamHandler',
                     'level': 'INFO',
                 },
                 'file': {
                     'class': 'logging.FileHandler',
                     'filename': 'mplog.log',
                     'mode': 'w',
                     'formatter': 'detailed',
                 },
                 'foofile': {
                     'class': 'logging.FileHandler',
                     'filename': 'mplog-foo.log',
                     'mode': 'w',
                     'formatter': 'detailed',
                 },
                 'errors': {
                     'class': 'logging.FileHandler',
                     'filename': 'mplog-errors.log',
                     'mode': 'w',
                     'level': 'ERROR',
                     'formatter': 'detailed',
                 },
             },
             'loggers': {
                 'foo': {
                     'handlers': ['foofile']
                 }
             },
             'root': {
                 'level': 'DEBUG',
                 'handlers': ['console', 'file', 'errors']
             },
         }
         workers = []
         for i in range(5):
             wp = Process(target=worker_process, name='worker %d' % (i + 1), args=(q,))
             workers.append(wp)
             wp.start()
         logging.config.dictConfig(d)
         lp = threading.Thread(target=logger_thread, args=(q,))
         lp.start()
         # At this point, the main process could do some useful work of its own
         # Once it's done that, it can wait for the workers to terminate...
         for wp in workers:
             wp.join()
         # And now tell the logging thread to finish up, too
         q.put(None)
         lp.join()

This variant shows how you can e.g.  apply configuration for particular
loggers - e.g.  the ‘foo’ logger has a special handler which stores all
events in the ‘foo’ subsystem in a file ‘mplog-foo.log’.  This will be
used by the logging machinery in the main process (even though the
logging events are generated in the worker processes) to direct the
messages to the appropriate destinations.

* Menu:

* Using concurrent.futures.ProcessPoolExecutor: Using concurrent futures ProcessPoolExecutor.
* Deploying Web applications using Gunicorn and uWSGI::


File: python.info,  Node: Using concurrent futures ProcessPoolExecutor,  Next: Deploying Web applications using Gunicorn and uWSGI,  Up: Logging to a single file from multiple processes

9.8.12.1 Using concurrent.futures.ProcessPoolExecutor
.....................................................

If you want to use *note concurrent.futures.ProcessPoolExecutor: 893. to
start your worker processes, you need to create the queue slightly
differently.  Instead of

     queue = multiprocessing.Queue(-1)

you should use

     queue = multiprocessing.Manager().Queue(-1)  # also works with the examples above

and you can then replace the worker creation from this:

     workers = []
     for i in range(10):
         worker = multiprocessing.Process(target=worker_process,
                                          args=(queue, worker_configurer))
         workers.append(worker)
         worker.start()
     for w in workers:
         w.join()

to this (remembering to first import *note concurrent.futures: 1a.):

     with concurrent.futures.ProcessPoolExecutor(max_workers=10) as executor:
         for i in range(10):
             executor.submit(worker_process, queue, worker_configurer)


File: python.info,  Node: Deploying Web applications using Gunicorn and uWSGI,  Prev: Using concurrent futures ProcessPoolExecutor,  Up: Logging to a single file from multiple processes

9.8.12.2 Deploying Web applications using Gunicorn and uWSGI
............................................................

When deploying Web applications using Gunicorn(1) or uWSGI(2) (or
similar), multiple worker processes are created to handle client
requests.  In such environments, avoid creating file-based handlers
directly in your web application.  Instead, use a *note SocketHandler:
f05. to log from the web application to a listener in a separate
process.  This can be set up using a process management tool such as
Supervisor - see *note Running a logging socket listener in production:
4d59. for more details.

   ---------- Footnotes ----------

   (1) https://gunicorn.org/

   (2) https://uwsgi-docs.readthedocs.io/en/latest/


File: python.info,  Node: Using file rotation,  Next: Use of alternative formatting styles,  Prev: Logging to a single file from multiple processes,  Up: Logging Cookbook

9.8.13 Using file rotation
--------------------------

Sometimes you want to let a log file grow to a certain size, then open a
new file and log to that.  You may want to keep a certain number of
these files, and when that many files have been created, rotate the
files so that the number of files and the size of the files both remain
bounded.  For this usage pattern, the logging package provides a *note
RotatingFileHandler: 14cb.:

     import glob
     import logging
     import logging.handlers

     LOG_FILENAME = 'logging_rotatingfile_example.out'

     # Set up a specific logger with our desired output level
     my_logger = logging.getLogger('MyLogger')
     my_logger.setLevel(logging.DEBUG)

     # Add the log message handler to the logger
     handler = logging.handlers.RotatingFileHandler(
                   LOG_FILENAME, maxBytes=20, backupCount=5)

     my_logger.addHandler(handler)

     # Log some messages
     for i in range(20):
         my_logger.debug('i = %d' % i)

     # See what files are created
     logfiles = glob.glob('%s*' % LOG_FILENAME)

     for filename in logfiles:
         print(filename)

The result should be 6 separate files, each with part of the log history
for the application:

     logging_rotatingfile_example.out
     logging_rotatingfile_example.out.1
     logging_rotatingfile_example.out.2
     logging_rotatingfile_example.out.3
     logging_rotatingfile_example.out.4
     logging_rotatingfile_example.out.5

The most current file is always ‘logging_rotatingfile_example.out’, and
each time it reaches the size limit it is renamed with the suffix ‘.1’.
Each of the existing backup files is renamed to increment the suffix
(‘.1’ becomes ‘.2’, etc.)  and the ‘.6’ file is erased.

Obviously this example sets the log length much too small as an extreme
example.  You would want to set 'maxBytes' to an appropriate value.


File: python.info,  Node: Use of alternative formatting styles,  Next: Customizing LogRecord,  Prev: Using file rotation,  Up: Logging Cookbook

9.8.14 Use of alternative formatting styles
-------------------------------------------

When logging was added to the Python standard library, the only way of
formatting messages with variable content was to use the %-formatting
method.  Since then, Python has gained two new formatting approaches:
*note string.Template: 62d. (added in Python 2.4) and *note
str.format(): 5c7. (added in Python 2.6).

Logging (as of 3.2) provides improved support for these two additional
formatting styles.  The *note Formatter: 1400. class been enhanced to
take an additional, optional keyword parameter named ‘style’.  This
defaults to ‘'%'’, but other possible values are ‘'{'’ and ‘'$'’, which
correspond to the other two formatting styles.  Backwards compatibility
is maintained by default (as you would expect), but by explicitly
specifying a style parameter, you get the ability to specify format
strings which work with *note str.format(): 5c7. or *note
string.Template: 62d.  Here's an example console session to show the
possibilities:

     >>> import logging
     >>> root = logging.getLogger()
     >>> root.setLevel(logging.DEBUG)
     >>> handler = logging.StreamHandler()
     >>> bf = logging.Formatter('{asctime} {name} {levelname:8s} {message}',
     ...                        style='{')
     >>> handler.setFormatter(bf)
     >>> root.addHandler(handler)
     >>> logger = logging.getLogger('foo.bar')
     >>> logger.debug('This is a DEBUG message')
     2010-10-28 15:11:55,341 foo.bar DEBUG    This is a DEBUG message
     >>> logger.critical('This is a CRITICAL message')
     2010-10-28 15:12:11,526 foo.bar CRITICAL This is a CRITICAL message
     >>> df = logging.Formatter('$asctime $name ${levelname} $message',
     ...                        style='$')
     >>> handler.setFormatter(df)
     >>> logger.debug('This is a DEBUG message')
     2010-10-28 15:13:06,924 foo.bar DEBUG This is a DEBUG message
     >>> logger.critical('This is a CRITICAL message')
     2010-10-28 15:13:11,494 foo.bar CRITICAL This is a CRITICAL message
     >>>

Note that the formatting of logging messages for final output to logs is
completely independent of how an individual logging message is
constructed.  That can still use %-formatting, as shown here:

     >>> logger.error('This is an%s %s %s', 'other,', 'ERROR,', 'message')
     2010-10-28 15:19:29,833 foo.bar ERROR This is another, ERROR, message
     >>>

Logging calls (‘logger.debug()’, ‘logger.info()’ etc.)  only take
positional parameters for the actual logging message itself, with
keyword parameters used only for determining options for how to handle
the actual logging call (e.g.  the ‘exc_info’ keyword parameter to
indicate that traceback information should be logged, or the ‘extra’
keyword parameter to indicate additional contextual information to be
added to the log).  So you cannot directly make logging calls using
*note str.format(): 5c7. or *note string.Template: 62d. syntax, because
internally the logging package uses %-formatting to merge the format
string and the variable arguments.  There would be no changing this
while preserving backward compatibility, since all logging calls which
are out there in existing code will be using %-format strings.

There is, however, a way that you can use {}- and $- formatting to
construct your individual log messages.  Recall that for a message you
can use an arbitrary object as a message format string, and that the
logging package will call ‘str()’ on that object to get the actual
format string.  Consider the following two classes:

     class BraceMessage:
         def __init__(self, fmt, /, *args, **kwargs):
             self.fmt = fmt
             self.args = args
             self.kwargs = kwargs

         def __str__(self):
             return self.fmt.format(*self.args, **self.kwargs)

     class DollarMessage:
         def __init__(self, fmt, /, **kwargs):
             self.fmt = fmt
             self.kwargs = kwargs

         def __str__(self):
             from string import Template
             return Template(self.fmt).substitute(**self.kwargs)

Either of these can be used in place of a format string, to allow {}- or
$-formatting to be used to build the actual "message" part which appears
in the formatted log output in place of "%(message)s" or "{message}" or
"$message".  It's a little unwieldy to use the class names whenever you
want to log something, but it's quite palatable if you use an alias such
as __ (double underscore -- not to be confused with _, the single
underscore used as a synonym/alias for *note gettext.gettext(): 13d4. or
its brethren).

The above classes are not included in Python, though they're easy enough
to copy and paste into your own code.  They can be used as follows
(assuming that they're declared in a module called ‘wherever’):

     >>> from wherever import BraceMessage as __
     >>> print(__('Message with {0} {name}', 2, name='placeholders'))
     Message with 2 placeholders
     >>> class Point: pass
     ...
     >>> p = Point()
     >>> p.x = 0.5
     >>> p.y = 0.5
     >>> print(__('Message with coordinates: ({point.x:.2f}, {point.y:.2f})',
     ...       point=p))
     Message with coordinates: (0.50, 0.50)
     >>> from wherever import DollarMessage as __
     >>> print(__('Message with $num $what', num=2, what='placeholders'))
     Message with 2 placeholders
     >>>

While the above examples use ‘print()’ to show how the formatting works,
you would of course use ‘logger.debug()’ or similar to actually log
using this approach.

One thing to note is that you pay no significant performance penalty
with this approach: the actual formatting happens not when you make the
logging call, but when (and if) the logged message is actually about to
be output to a log by a handler.  So the only slightly unusual thing
which might trip you up is that the parentheses go around the format
string and the arguments, not just the format string.  That's because
the __ notation is just syntax sugar for a constructor call to one of
the ‘XXXMessage’ classes.

If you prefer, you can use a *note LoggerAdapter: 1288. to achieve a
similar effect to the above, as in the following example:

     import logging

     class Message:
         def __init__(self, fmt, args):
             self.fmt = fmt
             self.args = args

         def __str__(self):
             return self.fmt.format(*self.args)

     class StyleAdapter(logging.LoggerAdapter):
         def log(self, level, msg, /, *args, stacklevel=1, **kwargs):
             if self.isEnabledFor(level):
                 msg, kwargs = self.process(msg, kwargs)
                 self.logger.log(level, Message(msg, args), **kwargs,
                                 stacklevel=stacklevel+1)

     logger = StyleAdapter(logging.getLogger(__name__))

     def main():
         logger.debug('Hello, {}', 'world!')

     if __name__ == '__main__':
         logging.basicConfig(level=logging.DEBUG)
         main()

The above script should log the message ‘Hello, world!’ when run with
Python 3.8 or later.


File: python.info,  Node: Customizing LogRecord,  Next: Subclassing QueueHandler and QueueListener- a ZeroMQ example,  Prev: Use of alternative formatting styles,  Up: Logging Cookbook

9.8.15 Customizing ‘LogRecord’
------------------------------

Every logging event is represented by a *note LogRecord: f89. instance.
When an event is logged and not filtered out by a logger's level, a
*note LogRecord: f89. is created, populated with information about the
event and then passed to the handlers for that logger (and its
ancestors, up to and including the logger where further propagation up
the hierarchy is disabled).  Before Python 3.2, there were only two
places where this creation was done:

   * *note Logger.makeRecord(): 2bbb, which is called in the normal
     process of logging an event.  This invoked *note LogRecord: f89.
     directly to create an instance.

   * *note makeLogRecord(): 2be2, which is called with a dictionary
     containing attributes to be added to the LogRecord.  This is
     typically invoked when a suitable dictionary has been received over
     the network (e.g.  in pickle form via a *note SocketHandler: f05,
     or in JSON form via an *note HTTPHandler: dd1.).

This has usually meant that if you need to do anything special with a
*note LogRecord: f89, you've had to do one of the following.

   * Create your own *note Logger: af3. subclass, which overrides *note
     Logger.makeRecord(): 2bbb, and set it using *note setLoggerClass():
     2bf1. before any loggers that you care about are instantiated.

   * Add a *note Filter: 1193. to a logger or handler, which does the
     necessary special manipulation you need when its *note filter():
     2bdd. method is called.

The first approach would be a little unwieldy in the scenario where
(say) several different libraries wanted to do different things.  Each
would attempt to set its own *note Logger: af3. subclass, and the one
which did this last would win.

The second approach works reasonably well for many cases, but does not
allow you to e.g.  use a specialized subclass of *note LogRecord: f89.
Library developers can set a suitable filter on their loggers, but they
would have to remember to do this every time they introduced a new
logger (which they would do simply by adding new packages or modules and
doing

     logger = logging.getLogger(__name__)

at module level).  It's probably one too many things to think about.
Developers could also add the filter to a *note NullHandler: 121c.
attached to their top-level logger, but this would not be invoked if an
application developer attached a handler to a lower-level library logger
-- so output from that handler would not reflect the intentions of the
library developer.

In Python 3.2 and later, *note LogRecord: f89. creation is done through
a factory, which you can specify.  The factory is just a callable you
can set with *note setLogRecordFactory(): 2be6, and interrogate with
*note getLogRecordFactory(): 2be5.  The factory is invoked with the same
signature as the *note LogRecord: f89. constructor, as *note LogRecord:
f89. is the default setting for the factory.

This approach allows a custom factory to control all aspects of
LogRecord creation.  For example, you could return a subclass, or just
add some additional attributes to the record once created, using a
pattern similar to this:

     old_factory = logging.getLogRecordFactory()

     def record_factory(*args, **kwargs):
         record = old_factory(*args, **kwargs)
         record.custom_attribute = 0xdecafbad
         return record

     logging.setLogRecordFactory(record_factory)

This pattern allows different libraries to chain factories together, and
as long as they don't overwrite each other's attributes or
unintentionally overwrite the attributes provided as standard, there
should be no surprises.  However, it should be borne in mind that each
link in the chain adds run-time overhead to all logging operations, and
the technique should only be used when the use of a *note Filter: 1193.
does not provide the desired result.


File: python.info,  Node: Subclassing QueueHandler and QueueListener- a ZeroMQ example,  Next: Subclassing QueueHandler and QueueListener- a pynng example,  Prev: Customizing LogRecord,  Up: Logging Cookbook

9.8.16 Subclassing QueueHandler and QueueListener- a ZeroMQ example
-------------------------------------------------------------------

* Menu:

* Subclass QueueHandler::
* Subclass QueueListener::


File: python.info,  Node: Subclass QueueHandler,  Next: Subclass QueueListener,  Up: Subclassing QueueHandler and QueueListener- a ZeroMQ example

9.8.16.1 Subclass ‘QueueHandler’
................................

You can use a *note QueueHandler: 16dc. subclass to send messages to
other kinds of queues, for example a ZeroMQ 'publish' socket.  In the
example below,the socket is created separately and passed to the handler
(as its 'queue'):

     import zmq   # using pyzmq, the Python binding for ZeroMQ
     import json  # for serializing records portably

     ctx = zmq.Context()
     sock = zmq.Socket(ctx, zmq.PUB)  # or zmq.PUSH, or other suitable value
     sock.bind('tcp://*:5556')        # or wherever

     class ZeroMQSocketHandler(QueueHandler):
         def enqueue(self, record):
             self.queue.send_json(record.__dict__)


     handler = ZeroMQSocketHandler(sock)

Of course there are other ways of organizing this, for example passing
in the data needed by the handler to create the socket:

     class ZeroMQSocketHandler(QueueHandler):
         def __init__(self, uri, socktype=zmq.PUB, ctx=None):
             self.ctx = ctx or zmq.Context()
             socket = zmq.Socket(self.ctx, socktype)
             socket.bind(uri)
             super().__init__(socket)

         def enqueue(self, record):
             self.queue.send_json(record.__dict__)

         def close(self):
             self.queue.close()


File: python.info,  Node: Subclass QueueListener,  Prev: Subclass QueueHandler,  Up: Subclassing QueueHandler and QueueListener- a ZeroMQ example

9.8.16.2 Subclass ‘QueueListener’
.................................

You can also subclass *note QueueListener: dd2. to get messages from
other kinds of queues, for example a ZeroMQ 'subscribe' socket.  Here's
an example:

     class ZeroMQSocketListener(QueueListener):
         def __init__(self, uri, /, *handlers, **kwargs):
             self.ctx = kwargs.get('ctx') or zmq.Context()
             socket = zmq.Socket(self.ctx, zmq.SUB)
             socket.setsockopt_string(zmq.SUBSCRIBE, '')  # subscribe to everything
             socket.connect(uri)
             super().__init__(socket, *handlers, **kwargs)

         def dequeue(self):
             msg = self.queue.recv_json()
             return logging.makeLogRecord(msg)


File: python.info,  Node: Subclassing QueueHandler and QueueListener- a pynng example,  Next: An example dictionary-based configuration,  Prev: Subclassing QueueHandler and QueueListener- a ZeroMQ example,  Up: Logging Cookbook

9.8.17 Subclassing QueueHandler and QueueListener- a ‘pynng’ example
--------------------------------------------------------------------

In a similar way to the above section, we can implement a listener and
handler using pynng(1), which is a Python binding to NNG(2), billed as a
spiritual successor to ZeroMQ. The following snippets illustrate - you
can test them in an environment which has ‘pynng’ installed.  Just for
variety, we present the listener first.

* Menu:

* Subclass QueueListener: Subclass QueueListener<2>.
* Subclass QueueHandler: Subclass QueueHandler<2>.

   ---------- Footnotes ----------

   (1) https://pypi.org/project/pynng/

   (2) https://nng.nanomsg.org/


File: python.info,  Node: Subclass QueueListener<2>,  Next: Subclass QueueHandler<2>,  Up: Subclassing QueueHandler and QueueListener- a pynng example

9.8.17.1 Subclass ‘QueueListener’
.................................

     # listener.py
     import json
     import logging
     import logging.handlers

     import pynng

     DEFAULT_ADDR = "tcp://localhost:13232"

     interrupted = False

     class NNGSocketListener(logging.handlers.QueueListener):

         def __init__(self, uri, /, *handlers, **kwargs):
             # Have a timeout for interruptability, and open a
             # subscriber socket
             socket = pynng.Sub0(listen=uri, recv_timeout=500)
             # The b'' subscription matches all topics
             topics = kwargs.pop('topics', None) or b''
             socket.subscribe(topics)
             # We treat the socket as a queue
             super().__init__(socket, *handlers, **kwargs)

         def dequeue(self, block):
             data = None
             # Keep looping while not interrupted and no data received over the
             # socket
             while not interrupted:
                 try:
                     data = self.queue.recv(block=block)
                     break
                 except pynng.Timeout:
                     pass
                 except pynng.Closed:  # sometimes happens when you hit Ctrl-C
                     break
             if data is None:
                 return None
             # Get the logging event sent from a publisher
             event = json.loads(data.decode('utf-8'))
             return logging.makeLogRecord(event)

         def enqueue_sentinel(self):
             # Not used in this implementation, as the socket isn't really a
             # queue
             pass

     logging.getLogger('pynng').propagate = False
     listener = NNGSocketListener(DEFAULT_ADDR, logging.StreamHandler(), topics=b'')
     listener.start()
     print('Press Ctrl-C to stop.')
     try:
         while True:
             pass
     except KeyboardInterrupt:
         interrupted = True
     finally:
         listener.stop()


File: python.info,  Node: Subclass QueueHandler<2>,  Prev: Subclass QueueListener<2>,  Up: Subclassing QueueHandler and QueueListener- a pynng example

9.8.17.2 Subclass ‘QueueHandler’
................................

     # sender.py
     import json
     import logging
     import logging.handlers
     import time
     import random

     import pynng

     DEFAULT_ADDR = "tcp://localhost:13232"

     class NNGSocketHandler(logging.handlers.QueueHandler):

         def __init__(self, uri):
             socket = pynng.Pub0(dial=uri, send_timeout=500)
             super().__init__(socket)

         def enqueue(self, record):
             # Send the record as UTF-8 encoded JSON
             d = dict(record.__dict__)
             data = json.dumps(d)
             self.queue.send(data.encode('utf-8'))

         def close(self):
             self.queue.close()

     logging.getLogger('pynng').propagate = False
     handler = NNGSocketHandler(DEFAULT_ADDR)
     # Make sure the process ID is in the output
     logging.basicConfig(level=logging.DEBUG,
                         handlers=[logging.StreamHandler(), handler],
                         format='%(levelname)-8s %(name)10s %(process)6s %(message)s')
     levels = (logging.DEBUG, logging.INFO, logging.WARNING, logging.ERROR,
               logging.CRITICAL)
     logger_names = ('myapp', 'myapp.lib1', 'myapp.lib2')
     msgno = 1
     while True:
         # Just randomly select some loggers and levels and log away
         level = random.choice(levels)
         logger = logging.getLogger(random.choice(logger_names))
         logger.log(level, 'Message no. %5d' % msgno)
         msgno += 1
         delay = random.random() * 2 + 0.5
         time.sleep(delay)

You can run the above two snippets in separate command shells.  If we
run the listener in one shell and run the sender in two separate shells,
we should see something like the following.  In the first sender shell:

     $ python sender.py
     DEBUG         myapp    613 Message no.     1
     WARNING  myapp.lib2    613 Message no.     2
     CRITICAL myapp.lib2    613 Message no.     3
     WARNING  myapp.lib2    613 Message no.     4
     CRITICAL myapp.lib1    613 Message no.     5
     DEBUG         myapp    613 Message no.     6
     CRITICAL myapp.lib1    613 Message no.     7
     INFO     myapp.lib1    613 Message no.     8
     (and so on)

In the second sender shell:

     $ python sender.py
     INFO     myapp.lib2    657 Message no.     1
     CRITICAL myapp.lib2    657 Message no.     2
     CRITICAL      myapp    657 Message no.     3
     CRITICAL myapp.lib1    657 Message no.     4
     INFO     myapp.lib1    657 Message no.     5
     WARNING  myapp.lib2    657 Message no.     6
     CRITICAL      myapp    657 Message no.     7
     DEBUG    myapp.lib1    657 Message no.     8
     (and so on)

In the listener shell:

     $ python listener.py
     Press Ctrl-C to stop.
     DEBUG         myapp    613 Message no.     1
     WARNING  myapp.lib2    613 Message no.     2
     INFO     myapp.lib2    657 Message no.     1
     CRITICAL myapp.lib2    613 Message no.     3
     CRITICAL myapp.lib2    657 Message no.     2
     CRITICAL      myapp    657 Message no.     3
     WARNING  myapp.lib2    613 Message no.     4
     CRITICAL myapp.lib1    613 Message no.     5
     CRITICAL myapp.lib1    657 Message no.     4
     INFO     myapp.lib1    657 Message no.     5
     DEBUG         myapp    613 Message no.     6
     WARNING  myapp.lib2    657 Message no.     6
     CRITICAL      myapp    657 Message no.     7
     CRITICAL myapp.lib1    613 Message no.     7
     INFO     myapp.lib1    613 Message no.     8
     DEBUG    myapp.lib1    657 Message no.     8
     (and so on)

As you can see, the logging from the two sender processes is interleaved
in the listener's output.


File: python.info,  Node: An example dictionary-based configuration,  Next: Using a rotator and namer to customize log rotation processing,  Prev: Subclassing QueueHandler and QueueListener- a pynng example,  Up: Logging Cookbook

9.8.18 An example dictionary-based configuration
------------------------------------------------

Below is an example of a logging configuration dictionary - it's taken
from the documentation on the Django project(1).  This dictionary is
passed to *note dictConfig(): 1147. to put the configuration into
effect:

     LOGGING = {
         'version': 1,
         'disable_existing_loggers': False,
         'formatters': {
             'verbose': {
                 'format': '{levelname} {asctime} {module} {process:d} {thread:d} {message}',
                 'style': '{',
             },
             'simple': {
                 'format': '{levelname} {message}',
                 'style': '{',
             },
         },
         'filters': {
             'special': {
                 '()': 'project.logging.SpecialFilter',
                 'foo': 'bar',
             },
         },
         'handlers': {
             'console': {
                 'level': 'INFO',
                 'class': 'logging.StreamHandler',
                 'formatter': 'simple',
             },
             'mail_admins': {
                 'level': 'ERROR',
                 'class': 'django.utils.log.AdminEmailHandler',
                 'filters': ['special']
             }
         },
         'loggers': {
             'django': {
                 'handlers': ['console'],
                 'propagate': True,
             },
             'django.request': {
                 'handlers': ['mail_admins'],
                 'level': 'ERROR',
                 'propagate': False,
             },
             'myproject.custom': {
                 'handlers': ['console', 'mail_admins'],
                 'level': 'INFO',
                 'filters': ['special']
             }
         }
     }

For more information about this configuration, you can see the relevant
section(2) of the Django documentation.

   ---------- Footnotes ----------

   (1) 
https://docs.djangoproject.com/en/stable/topics/logging/#configuring-logging

   (2) 
https://docs.djangoproject.com/en/stable/topics/logging/#configuring-logging


File: python.info,  Node: Using a rotator and namer to customize log rotation processing,  Next: A more elaborate multiprocessing example,  Prev: An example dictionary-based configuration,  Up: Logging Cookbook

9.8.19 Using a rotator and namer to customize log rotation processing
---------------------------------------------------------------------

An example of how you can define a namer and rotator is given in the
following runnable script, which shows gzip compression of the log file:

     import gzip
     import logging
     import logging.handlers
     import os
     import shutil

     def namer(name):
         return name + ".gz"

     def rotator(source, dest):
         with open(source, 'rb') as f_in:
             with gzip.open(dest, 'wb') as f_out:
                 shutil.copyfileobj(f_in, f_out)
         os.remove(source)


     rh = logging.handlers.RotatingFileHandler('rotated.log', maxBytes=128, backupCount=5)
     rh.rotator = rotator
     rh.namer = namer

     root = logging.getLogger()
     root.setLevel(logging.INFO)
     root.addHandler(rh)
     f = logging.Formatter('%(asctime)s %(message)s')
     rh.setFormatter(f)
     for i in range(1000):
         root.info(f'Message no. {i + 1}')

After running this, you will see six new files, five of which are
compressed:

     $ ls rotated.log*
     rotated.log       rotated.log.2.gz  rotated.log.4.gz
     rotated.log.1.gz  rotated.log.3.gz  rotated.log.5.gz
     $ zcat rotated.log.1.gz
     2023-01-20 02:28:17,767 Message no. 996
     2023-01-20 02:28:17,767 Message no. 997
     2023-01-20 02:28:17,767 Message no. 998


File: python.info,  Node: A more elaborate multiprocessing example,  Next: Inserting a BOM into messages sent to a SysLogHandler,  Prev: Using a rotator and namer to customize log rotation processing,  Up: Logging Cookbook

9.8.20 A more elaborate multiprocessing example
-----------------------------------------------

The following working example shows how logging can be used with
multiprocessing using configuration files.  The configurations are
fairly simple, but serve to illustrate how more complex ones could be
implemented in a real multiprocessing scenario.

In the example, the main process spawns a listener process and some
worker processes.  Each of the main process, the listener and the
workers have three separate configurations (the workers all share the
same configuration).  We can see logging in the main process, how the
workers log to a QueueHandler and how the listener implements a
QueueListener and a more complex logging configuration, and arranges to
dispatch events received via the queue to the handlers specified in the
configuration.  Note that these configurations are purely illustrative,
but you should be able to adapt this example to your own scenario.

Here's the script - the docstrings and the comments hopefully explain
how it works:

     import logging
     import logging.config
     import logging.handlers
     from multiprocessing import Process, Queue, Event, current_process
     import os
     import random
     import time

     class MyHandler:
         """
         A simple handler for logging events. It runs in the listener process and
         dispatches events to loggers based on the name in the received record,
         which then get dispatched, by the logging system, to the handlers
         configured for those loggers.
         """

         def handle(self, record):
             if record.name == "root":
                 logger = logging.getLogger()
             else:
                 logger = logging.getLogger(record.name)

             if logger.isEnabledFor(record.levelno):
                 # The process name is transformed just to show that it's the listener
                 # doing the logging to files and console
                 record.processName = '%s (for %s)' % (current_process().name, record.processName)
                 logger.handle(record)

     def listener_process(q, stop_event, config):
         """
         This could be done in the main process, but is just done in a separate
         process for illustrative purposes.

         This initialises logging according to the specified configuration,
         starts the listener and waits for the main process to signal completion
         via the event. The listener is then stopped, and the process exits.
         """
         logging.config.dictConfig(config)
         listener = logging.handlers.QueueListener(q, MyHandler())
         listener.start()
         if os.name == 'posix':
             # On POSIX, the setup logger will have been configured in the
             # parent process, but should have been disabled following the
             # dictConfig call.
             # On Windows, since fork isn't used, the setup logger won't
             # exist in the child, so it would be created and the message
             # would appear - hence the "if posix" clause.
             logger = logging.getLogger('setup')
             logger.critical('Should not appear, because of disabled logger ...')
         stop_event.wait()
         listener.stop()

     def worker_process(config):
         """
         A number of these are spawned for the purpose of illustration. In
         practice, they could be a heterogeneous bunch of processes rather than
         ones which are identical to each other.

         This initialises logging according to the specified configuration,
         and logs a hundred messages with random levels to randomly selected
         loggers.

         A small sleep is added to allow other processes a chance to run. This
         is not strictly needed, but it mixes the output from the different
         processes a bit more than if it's left out.
         """
         logging.config.dictConfig(config)
         levels = [logging.DEBUG, logging.INFO, logging.WARNING, logging.ERROR,
                   logging.CRITICAL]
         loggers = ['foo', 'foo.bar', 'foo.bar.baz',
                    'spam', 'spam.ham', 'spam.ham.eggs']
         if os.name == 'posix':
             # On POSIX, the setup logger will have been configured in the
             # parent process, but should have been disabled following the
             # dictConfig call.
             # On Windows, since fork isn't used, the setup logger won't
             # exist in the child, so it would be created and the message
             # would appear - hence the "if posix" clause.
             logger = logging.getLogger('setup')
             logger.critical('Should not appear, because of disabled logger ...')
         for i in range(100):
             lvl = random.choice(levels)
             logger = logging.getLogger(random.choice(loggers))
             logger.log(lvl, 'Message no. %d', i)
             time.sleep(0.01)

     def main():
         q = Queue()
         # The main process gets a simple configuration which prints to the console.
         config_initial = {
             'version': 1,
             'handlers': {
                 'console': {
                     'class': 'logging.StreamHandler',
                     'level': 'INFO'
                 }
             },
             'root': {
                 'handlers': ['console'],
                 'level': 'DEBUG'
             }
         }
         # The worker process configuration is just a QueueHandler attached to the
         # root logger, which allows all messages to be sent to the queue.
         # We disable existing loggers to disable the "setup" logger used in the
         # parent process. This is needed on POSIX because the logger will
         # be there in the child following a fork().
         config_worker = {
             'version': 1,
             'disable_existing_loggers': True,
             'handlers': {
                 'queue': {
                     'class': 'logging.handlers.QueueHandler',
                     'queue': q
                 }
             },
             'root': {
                 'handlers': ['queue'],
                 'level': 'DEBUG'
             }
         }
         # The listener process configuration shows that the full flexibility of
         # logging configuration is available to dispatch events to handlers however
         # you want.
         # We disable existing loggers to disable the "setup" logger used in the
         # parent process. This is needed on POSIX because the logger will
         # be there in the child following a fork().
         config_listener = {
             'version': 1,
             'disable_existing_loggers': True,
             'formatters': {
                 'detailed': {
                     'class': 'logging.Formatter',
                     'format': '%(asctime)s %(name)-15s %(levelname)-8s %(processName)-10s %(message)s'
                 },
                 'simple': {
                     'class': 'logging.Formatter',
                     'format': '%(name)-15s %(levelname)-8s %(processName)-10s %(message)s'
                 }
             },
             'handlers': {
                 'console': {
                     'class': 'logging.StreamHandler',
                     'formatter': 'simple',
                     'level': 'INFO'
                 },
                 'file': {
                     'class': 'logging.FileHandler',
                     'filename': 'mplog.log',
                     'mode': 'w',
                     'formatter': 'detailed'
                 },
                 'foofile': {
                     'class': 'logging.FileHandler',
                     'filename': 'mplog-foo.log',
                     'mode': 'w',
                     'formatter': 'detailed'
                 },
                 'errors': {
                     'class': 'logging.FileHandler',
                     'filename': 'mplog-errors.log',
                     'mode': 'w',
                     'formatter': 'detailed',
                     'level': 'ERROR'
                 }
             },
             'loggers': {
                 'foo': {
                     'handlers': ['foofile']
                 }
             },
             'root': {
                 'handlers': ['console', 'file', 'errors'],
                 'level': 'DEBUG'
             }
         }
         # Log some initial events, just to show that logging in the parent works
         # normally.
         logging.config.dictConfig(config_initial)
         logger = logging.getLogger('setup')
         logger.info('About to create workers ...')
         workers = []
         for i in range(5):
             wp = Process(target=worker_process, name='worker %d' % (i + 1),
                          args=(config_worker,))
             workers.append(wp)
             wp.start()
             logger.info('Started worker: %s', wp.name)
         logger.info('About to create listener ...')
         stop_event = Event()
         lp = Process(target=listener_process, name='listener',
                      args=(q, stop_event, config_listener))
         lp.start()
         logger.info('Started listener')
         # We now hang around for the workers to finish their work.
         for wp in workers:
             wp.join()
         # Workers all done, listening can now stop.
         # Logging in the parent still works normally.
         logger.info('Telling listener to stop ...')
         stop_event.set()
         lp.join()
         logger.info('All done.')

     if __name__ == '__main__':
         main()


File: python.info,  Node: Inserting a BOM into messages sent to a SysLogHandler,  Next: Implementing structured logging,  Prev: A more elaborate multiprocessing example,  Up: Logging Cookbook

9.8.21 Inserting a BOM into messages sent to a SysLogHandler
------------------------------------------------------------

RFC 5424(1) requires that a Unicode message be sent to a syslog daemon
as a set of bytes which have the following structure: an optional
pure-ASCII component, followed by a UTF-8 Byte Order Mark (BOM),
followed by Unicode encoded using UTF-8.  (See the relevant section of
the specification(2).)

In Python 3.1, code was added to *note SysLogHandler: 602. to insert a
BOM into the message, but unfortunately, it was implemented incorrectly,
with the BOM appearing at the beginning of the message and hence not
allowing any pure-ASCII component to appear before it.

As this behaviour is broken, the incorrect BOM insertion code is being
removed from Python 3.2.4 and later.  However, it is not being replaced,
and if you want to produce RFC 5424(3)-compliant messages which include
a BOM, an optional pure-ASCII sequence before it and arbitrary Unicode
after it, encoded using UTF-8, then you need to do the following:

  1. Attach a *note Formatter: 1400. instance to your *note
     SysLogHandler: 602. instance, with a format string such as:

          'ASCII section\ufeffUnicode section'

     The Unicode code point U+FEFF, when encoded using UTF-8, will be
     encoded as a UTF-8 BOM - the byte-string ‘b'\xef\xbb\xbf'’.

  2. Replace the ASCII section with whatever placeholders you like, but
     make sure that the data that appears in there after substitution is
     always ASCII (that way, it will remain unchanged after UTF-8
     encoding).

  3. Replace the Unicode section with whatever placeholders you like; if
     the data which appears there after substitution contains characters
     outside the ASCII range, that's fine - it will be encoded using
     UTF-8.

The formatted message 'will' be encoded using UTF-8 encoding by
‘SysLogHandler’.  If you follow the above rules, you should be able to
produce RFC 5424(4)-compliant messages.  If you don't, logging may not
complain, but your messages will not be RFC 5424-compliant, and your
syslog daemon may complain.

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc5424.html

   (2) https://datatracker.ietf.org/doc/html/rfc5424.html#section-6

   (3) https://datatracker.ietf.org/doc/html/rfc5424.html

   (4) https://datatracker.ietf.org/doc/html/rfc5424.html


File: python.info,  Node: Implementing structured logging,  Next: Customizing handlers with dictConfig,  Prev: Inserting a BOM into messages sent to a SysLogHandler,  Up: Logging Cookbook

9.8.22 Implementing structured logging
--------------------------------------

Although most logging messages are intended for reading by humans, and
thus not readily machine-parseable, there might be circumstances where
you want to output messages in a structured format which 'is' capable of
being parsed by a program (without needing complex regular expressions
to parse the log message).  This is straightforward to achieve using the
logging package.  There are a number of ways in which this could be
achieved, but the following is a simple approach which uses JSON to
serialise the event in a machine-parseable manner:

     import json
     import logging

     class StructuredMessage:
         def __init__(self, message, /, **kwargs):
             self.message = message
             self.kwargs = kwargs

         def __str__(self):
             return '%s >>> %s' % (self.message, json.dumps(self.kwargs))

     _ = StructuredMessage   # optional, to improve readability

     logging.basicConfig(level=logging.INFO, format='%(message)s')
     logging.info(_('message 1', foo='bar', bar='baz', num=123, fnum=123.456))

If the above script is run, it prints:

     message 1 >>> {"fnum": 123.456, "num": 123, "bar": "baz", "foo": "bar"}

Note that the order of items might be different according to the version
of Python used.

If you need more specialised processing, you can use a custom JSON
encoder, as in the following complete example:

     import json
     import logging


     class Encoder(json.JSONEncoder):
         def default(self, o):
             if isinstance(o, set):
                 return tuple(o)
             elif isinstance(o, str):
                 return o.encode('unicode_escape').decode('ascii')
             return super().default(o)

     class StructuredMessage:
         def __init__(self, message, /, **kwargs):
             self.message = message
             self.kwargs = kwargs

         def __str__(self):
             s = Encoder().encode(self.kwargs)
             return '%s >>> %s' % (self.message, s)

     _ = StructuredMessage   # optional, to improve readability

     def main():
         logging.basicConfig(level=logging.INFO, format='%(message)s')
         logging.info(_('message 1', set_value={1, 2, 3}, snowman='\u2603'))

     if __name__ == '__main__':
         main()

When the above script is run, it prints:

     message 1 >>> {"snowman": "\u2603", "set_value": [1, 2, 3]}

Note that the order of items might be different according to the version
of Python used.


File: python.info,  Node: Customizing handlers with dictConfig,  Next: Using particular formatting styles throughout your application,  Prev: Implementing structured logging,  Up: Logging Cookbook

9.8.23 Customizing handlers with ‘dictConfig()’
-----------------------------------------------

There are times when you want to customize logging handlers in
particular ways, and if you use *note dictConfig(): 1147. you may be
able to do this without subclassing.  As an example, consider that you
may want to set the ownership of a log file.  On POSIX, this is easily
done using *note shutil.chown(): 225, but the file handlers in the
stdlib don't offer built-in support.  You can customize handler creation
using a plain function such as:

     def owned_file_handler(filename, mode='a', encoding=None, owner=None):
         if owner:
             if not os.path.exists(filename):
                 open(filename, 'a').close()
             shutil.chown(filename, *owner)
         return logging.FileHandler(filename, mode, encoding)

You can then specify, in a logging configuration passed to *note
dictConfig(): 1147, that a logging handler be created by calling this
function:

     LOGGING = {
         'version': 1,
         'disable_existing_loggers': False,
         'formatters': {
             'default': {
                 'format': '%(asctime)s %(levelname)s %(name)s %(message)s'
             },
         },
         'handlers': {
             'file':{
                 # The values below are popped from this dictionary and
                 # used to create the handler, set the handler's level and
                 # its formatter.
                 '()': owned_file_handler,
                 'level':'DEBUG',
                 'formatter': 'default',
                 # The values below are passed to the handler creator callable
                 # as keyword arguments.
                 'owner': ['pulse', 'pulse'],
                 'filename': 'chowntest.log',
                 'mode': 'w',
                 'encoding': 'utf-8',
             },
         },
         'root': {
             'handlers': ['file'],
             'level': 'DEBUG',
         },
     }

In this example I am setting the ownership using the ‘pulse’ user and
group, just for the purposes of illustration.  Putting it together into
a working script, ‘chowntest.py’:

     import logging, logging.config, os, shutil

     def owned_file_handler(filename, mode='a', encoding=None, owner=None):
         if owner:
             if not os.path.exists(filename):
                 open(filename, 'a').close()
             shutil.chown(filename, *owner)
         return logging.FileHandler(filename, mode, encoding)

     LOGGING = {
         'version': 1,
         'disable_existing_loggers': False,
         'formatters': {
             'default': {
                 'format': '%(asctime)s %(levelname)s %(name)s %(message)s'
             },
         },
         'handlers': {
             'file':{
                 # The values below are popped from this dictionary and
                 # used to create the handler, set the handler's level and
                 # its formatter.
                 '()': owned_file_handler,
                 'level':'DEBUG',
                 'formatter': 'default',
                 # The values below are passed to the handler creator callable
                 # as keyword arguments.
                 'owner': ['pulse', 'pulse'],
                 'filename': 'chowntest.log',
                 'mode': 'w',
                 'encoding': 'utf-8',
             },
         },
         'root': {
             'handlers': ['file'],
             'level': 'DEBUG',
         },
     }

     logging.config.dictConfig(LOGGING)
     logger = logging.getLogger('mylogger')
     logger.debug('A debug message')

To run this, you will probably need to run as ‘root’:

     $ sudo python3.3 chowntest.py
     $ cat chowntest.log
     2013-11-05 09:34:51,128 DEBUG mylogger A debug message
     $ ls -l chowntest.log
     -rw-r--r-- 1 pulse pulse 55 2013-11-05 09:34 chowntest.log

Note that this example uses Python 3.3 because that's where *note
shutil.chown(): 225. makes an appearance.  This approach should work
with any Python version that supports *note dictConfig(): 1147. -
namely, Python 2.7, 3.2 or later.  With pre-3.3 versions, you would need
to implement the actual ownership change using e.g.  *note os.chown():
1087.

In practice, the handler-creating function may be in a utility module
somewhere in your project.  Instead of the line in the configuration:

     '()': owned_file_handler,

you could use e.g.:

     '()': 'ext://project.util.owned_file_handler',

where ‘project.util’ can be replaced with the actual name of the package
where the function resides.  In the above working script, using
‘'ext://__main__.owned_file_handler'’ should work.  Here, the actual
callable is resolved by *note dictConfig(): 1147. from the ‘ext://’
specification.

This example hopefully also points the way to how you could implement
other types of file change - e.g.  setting specific POSIX permission
bits - in the same way, using *note os.chmod(): 200.

Of course, the approach could also be extended to types of handler other
than a *note FileHandler: 17a1. - for example, one of the rotating file
handlers, or a different type of handler altogether.


File: python.info,  Node: Using particular formatting styles throughout your application,  Next: Configuring filters with dictConfig,  Prev: Customizing handlers with dictConfig,  Up: Logging Cookbook

9.8.24 Using particular formatting styles throughout your application
---------------------------------------------------------------------

In Python 3.2, the *note Formatter: 1400. gained a ‘style’ keyword
parameter which, while defaulting to ‘%’ for backward compatibility,
allowed the specification of ‘{’ or ‘$’ to support the formatting
approaches supported by *note str.format(): 5c7. and *note
string.Template: 62d.  Note that this governs the formatting of logging
messages for final output to logs, and is completely orthogonal to how
an individual logging message is constructed.

Logging calls (*note debug(): dd0, *note info(): 2bb3. etc.)  only take
positional parameters for the actual logging message itself, with
keyword parameters used only for determining options for how to handle
the logging call (e.g.  the ‘exc_info’ keyword parameter to indicate
that traceback information should be logged, or the ‘extra’ keyword
parameter to indicate additional contextual information to be added to
the log).  So you cannot directly make logging calls using *note
str.format(): 5c7. or *note string.Template: 62d. syntax, because
internally the logging package uses %-formatting to merge the format
string and the variable arguments.  There would be no changing this
while preserving backward compatibility, since all logging calls which
are out there in existing code will be using %-format strings.

There have been suggestions to associate format styles with specific
loggers, but that approach also runs into backward compatibility
problems because any existing code could be using a given logger name
and using %-formatting.

For logging to work interoperably between any third-party libraries and
your code, decisions about formatting need to be made at the level of
the individual logging call.  This opens up a couple of ways in which
alternative formatting styles can be accommodated.

* Menu:

* Using LogRecord factories::
* Using custom message objects::


File: python.info,  Node: Using LogRecord factories,  Next: Using custom message objects,  Up: Using particular formatting styles throughout your application

9.8.24.1 Using LogRecord factories
..................................

In Python 3.2, along with the *note Formatter: 1400. changes mentioned
above, the logging package gained the ability to allow users to set
their own *note LogRecord: f89. subclasses, using the *note
setLogRecordFactory(): 2be6. function.  You can use this to set your own
subclass of *note LogRecord: f89, which does the Right Thing by
overriding the *note getMessage(): 2be4. method.  The base class
implementation of this method is where the ‘msg % args’ formatting
happens, and where you can substitute your alternate formatting;
however, you should be careful to support all formatting styles and
allow %-formatting as the default, to ensure interoperability with other
code.  Care should also be taken to call ‘str(self.msg)’, just as the
base implementation does.

Refer to the reference documentation on *note setLogRecordFactory():
2be6. and *note LogRecord: f89. for more information.


File: python.info,  Node: Using custom message objects,  Prev: Using LogRecord factories,  Up: Using particular formatting styles throughout your application

9.8.24.2 Using custom message objects
.....................................

There is another, perhaps simpler way that you can use {}- and $-
formatting to construct your individual log messages.  You may recall
(from *note Using arbitrary objects as messages: 2be3.) that when
logging you can use an arbitrary object as a message format string, and
that the logging package will call *note str(): 3f2. on that object to
get the actual format string.  Consider the following two classes:

     class BraceMessage:
         def __init__(self, fmt, /, *args, **kwargs):
             self.fmt = fmt
             self.args = args
             self.kwargs = kwargs

         def __str__(self):
             return self.fmt.format(*self.args, **self.kwargs)

     class DollarMessage:
         def __init__(self, fmt, /, **kwargs):
             self.fmt = fmt
             self.kwargs = kwargs

         def __str__(self):
             from string import Template
             return Template(self.fmt).substitute(**self.kwargs)

Either of these can be used in place of a format string, to allow {}- or
$-formatting to be used to build the actual "message" part which appears
in the formatted log output in place of “%(message)s” or “{message}” or
“$message”.  If you find it a little unwieldy to use the class names
whenever you want to log something, you can make it more palatable if
you use an alias such as ‘M’ or ‘_’ for the message (or perhaps ‘__’, if
you are using ‘_’ for localization).

Examples of this approach are given below.  Firstly, formatting with
*note str.format(): 5c7.:

     >>> __ = BraceMessage
     >>> print(__('Message with {0} {1}', 2, 'placeholders'))
     Message with 2 placeholders
     >>> class Point: pass
     ...
     >>> p = Point()
     >>> p.x = 0.5
     >>> p.y = 0.5
     >>> print(__('Message with coordinates: ({point.x:.2f}, {point.y:.2f})', point=p))
     Message with coordinates: (0.50, 0.50)

Secondly, formatting with *note string.Template: 62d.:

     >>> __ = DollarMessage
     >>> print(__('Message with $num $what', num=2, what='placeholders'))
     Message with 2 placeholders
     >>>

One thing to note is that you pay no significant performance penalty
with this approach: the actual formatting happens not when you make the
logging call, but when (and if) the logged message is actually about to
be output to a log by a handler.  So the only slightly unusual thing
which might trip you up is that the parentheses go around the format
string and the arguments, not just the format string.  That’s because
the __ notation is just syntax sugar for a constructor call to one of
the ‘XXXMessage’ classes shown above.


File: python.info,  Node: Configuring filters with dictConfig,  Next: Customized exception formatting,  Prev: Using particular formatting styles throughout your application,  Up: Logging Cookbook

9.8.25 Configuring filters with ‘dictConfig()’
----------------------------------------------

You 'can' configure filters using *note dictConfig(): 1147, though it
might not be obvious at first glance how to do it (hence this recipe).
Since *note Filter: 1193. is the only filter class included in the
standard library, and it is unlikely to cater to many requirements (it's
only there as a base class), you will typically need to define your own
*note Filter: 1193. subclass with an overridden *note filter(): 2bdd.
method.  To do this, specify the ‘()’ key in the configuration
dictionary for the filter, specifying a callable which will be used to
create the filter (a class is the most obvious, but you can provide any
callable which returns a *note Filter: 1193. instance).  Here is a
complete example:

     import logging
     import logging.config
     import sys

     class MyFilter(logging.Filter):
         def __init__(self, param=None):
             self.param = param

         def filter(self, record):
             if self.param is None:
                 allow = True
             else:
                 allow = self.param not in record.msg
             if allow:
                 record.msg = 'changed: ' + record.msg
             return allow

     LOGGING = {
         'version': 1,
         'filters': {
             'myfilter': {
                 '()': MyFilter,
                 'param': 'noshow',
             }
         },
         'handlers': {
             'console': {
                 'class': 'logging.StreamHandler',
                 'filters': ['myfilter']
             }
         },
         'root': {
             'level': 'DEBUG',
             'handlers': ['console']
         },
     }

     if __name__ == '__main__':
         logging.config.dictConfig(LOGGING)
         logging.debug('hello')
         logging.debug('hello - noshow')

This example shows how you can pass configuration data to the callable
which constructs the instance, in the form of keyword parameters.  When
run, the above script will print:

     changed: hello

which shows that the filter is working as configured.

A couple of extra points to note:

   * If you can't refer to the callable directly in the configuration
     (e.g.  if it lives in a different module, and you can't import it
     directly where the configuration dictionary is), you can use the
     form ‘ext://...’ as described in *note Access to external objects:
     2c11.  For example, you could have used the text
     ‘'ext://__main__.MyFilter'’ instead of ‘MyFilter’ in the above
     example.

   * As well as for filters, this technique can also be used to
     configure custom handlers and formatters.  See *note User-defined
     objects: 2c05. for more information on how logging supports using
     user-defined objects in its configuration, and see the other
     cookbook recipe *note Customizing handlers with dictConfig(): 4d76.
     above.


File: python.info,  Node: Customized exception formatting,  Next: Speaking logging messages,  Prev: Configuring filters with dictConfig,  Up: Logging Cookbook

9.8.26 Customized exception formatting
--------------------------------------

There might be times when you want to do customized exception formatting
- for argument's sake, let's say you want exactly one line per logged
event, even when exception information is present.  You can do this with
a custom formatter class, as shown in the following example:

     import logging

     class OneLineExceptionFormatter(logging.Formatter):
         def formatException(self, exc_info):
             """
             Format an exception so that it prints on a single line.
             """
             result = super().formatException(exc_info)
             return repr(result)  # or format into one line however you want to

         def format(self, record):
             s = super().format(record)
             if record.exc_text:
                 s = s.replace('\n', '') + '|'
             return s

     def configure_logging():
         fh = logging.FileHandler('output.txt', 'w')
         f = OneLineExceptionFormatter('%(asctime)s|%(levelname)s|%(message)s|',
                                       '%d/%m/%Y %H:%M:%S')
         fh.setFormatter(f)
         root = logging.getLogger()
         root.setLevel(logging.DEBUG)
         root.addHandler(fh)

     def main():
         configure_logging()
         logging.info('Sample message')
         try:
             x = 1 / 0
         except ZeroDivisionError as e:
             logging.exception('ZeroDivisionError: %s', e)

     if __name__ == '__main__':
         main()

When run, this produces a file with exactly two lines:

     28/01/2015 07:21:23|INFO|Sample message|
     28/01/2015 07:21:23|ERROR|ZeroDivisionError: integer division or modulo by zero|'Traceback (most recent call last):\n  File "logtest7.py", line 30, in main\n    x = 1 / 0\nZeroDivisionError: integer division or modulo by zero'|

While the above treatment is simplistic, it points the way to how
exception information can be formatted to your liking.  The *note
traceback: e7. module may be helpful for more specialized needs.


File: python.info,  Node: Speaking logging messages,  Next: Buffering logging messages and outputting them conditionally,  Prev: Customized exception formatting,  Up: Logging Cookbook

9.8.27 Speaking logging messages
--------------------------------

There might be situations when it is desirable to have logging messages
rendered in an audible rather than a visible format.  This is easy to do
if you have text-to-speech (TTS) functionality available in your system,
even if it doesn't have a Python binding.  Most TTS systems have a
command line program you can run, and this can be invoked from a handler
using *note subprocess: c1.  It's assumed here that TTS command line
programs won't expect to interact with users or take a long time to
complete, and that the frequency of logged messages will be not so high
as to swamp the user with messages, and that it's acceptable to have the
messages spoken one at a time rather than concurrently, The example
implementation below waits for one message to be spoken before the next
is processed, and this might cause other handlers to be kept waiting.
Here is a short example showing the approach, which assumes that the
‘espeak’ TTS package is available:

     import logging
     import subprocess
     import sys

     class TTSHandler(logging.Handler):
         def emit(self, record):
             msg = self.format(record)
             # Speak slowly in a female English voice
             cmd = ['espeak', '-s150', '-ven+f3', msg]
             p = subprocess.Popen(cmd, stdout=subprocess.PIPE,
                                  stderr=subprocess.STDOUT)
             # wait for the program to finish
             p.communicate()

     def configure_logging():
         h = TTSHandler()
         root = logging.getLogger()
         root.addHandler(h)
         # the default formatter just returns the message
         root.setLevel(logging.DEBUG)

     def main():
         logging.info('Hello')
         logging.debug('Goodbye')

     if __name__ == '__main__':
         configure_logging()
         sys.exit(main())

When run, this script should say "Hello" and then "Goodbye" in a female
voice.

The above approach can, of course, be adapted to other TTS systems and
even other systems altogether which can process messages via external
programs run from a command line.


File: python.info,  Node: Buffering logging messages and outputting them conditionally,  Next: Sending logging messages to email with buffering,  Prev: Speaking logging messages,  Up: Logging Cookbook

9.8.28 Buffering logging messages and outputting them conditionally
-------------------------------------------------------------------

There might be situations where you want to log messages in a temporary
area and only output them if a certain condition occurs.  For example,
you may want to start logging debug events in a function, and if the
function completes without errors, you don't want to clutter the log
with the collected debug information, but if there is an error, you want
all the debug information to be output as well as the error.

Here is an example which shows how you could do this using a decorator
for your functions where you want logging to behave this way.  It makes
use of the *note logging.handlers.MemoryHandler: 2c14, which allows
buffering of logged events until some condition occurs, at which point
the buffered events are ‘flushed’ - passed to another handler (the
‘target’ handler) for processing.  By default, the ‘MemoryHandler’
flushed when its buffer gets filled up or an event whose level is
greater than or equal to a specified threshold is seen.  You can use
this recipe with a more specialised subclass of ‘MemoryHandler’ if you
want custom flushing behavior.

The example script has a simple function, ‘foo’, which just cycles
through all the logging levels, writing to ‘sys.stderr’ to say what
level it's about to log at, and then actually logging a message at that
level.  You can pass a parameter to ‘foo’ which, if true, will log at
ERROR and CRITICAL levels - otherwise, it only logs at DEBUG, INFO and
WARNING levels.

The script just arranges to decorate ‘foo’ with a decorator which will
do the conditional logging that's required.  The decorator takes a
logger as a parameter and attaches a memory handler for the duration of
the call to the decorated function.  The decorator can be additionally
parameterised using a target handler, a level at which flushing should
occur, and a capacity for the buffer (number of records buffered).
These default to a *note StreamHandler: 1190. which writes to
‘sys.stderr’, ‘logging.ERROR’ and ‘100’ respectively.

Here's the script:

     import logging
     from logging.handlers import MemoryHandler
     import sys

     logger = logging.getLogger(__name__)
     logger.addHandler(logging.NullHandler())

     def log_if_errors(logger, target_handler=None, flush_level=None, capacity=None):
         if target_handler is None:
             target_handler = logging.StreamHandler()
         if flush_level is None:
             flush_level = logging.ERROR
         if capacity is None:
             capacity = 100
         handler = MemoryHandler(capacity, flushLevel=flush_level, target=target_handler)

         def decorator(fn):
             def wrapper(*args, **kwargs):
                 logger.addHandler(handler)
                 try:
                     return fn(*args, **kwargs)
                 except Exception:
                     logger.exception('call failed')
                     raise
                 finally:
                     super(MemoryHandler, handler).flush()
                     logger.removeHandler(handler)
             return wrapper

         return decorator

     def write_line(s):
         sys.stderr.write('%s\n' % s)

     def foo(fail=False):
         write_line('about to log at DEBUG ...')
         logger.debug('Actually logged at DEBUG')
         write_line('about to log at INFO ...')
         logger.info('Actually logged at INFO')
         write_line('about to log at WARNING ...')
         logger.warning('Actually logged at WARNING')
         if fail:
             write_line('about to log at ERROR ...')
             logger.error('Actually logged at ERROR')
             write_line('about to log at CRITICAL ...')
             logger.critical('Actually logged at CRITICAL')
         return fail

     decorated_foo = log_if_errors(logger)(foo)

     if __name__ == '__main__':
         logger.setLevel(logging.DEBUG)
         write_line('Calling undecorated foo with False')
         assert not foo(False)
         write_line('Calling undecorated foo with True')
         assert foo(True)
         write_line('Calling decorated foo with False')
         assert not decorated_foo(False)
         write_line('Calling decorated foo with True')
         assert decorated_foo(True)

When this script is run, the following output should be observed:

     Calling undecorated foo with False
     about to log at DEBUG ...
     about to log at INFO ...
     about to log at WARNING ...
     Calling undecorated foo with True
     about to log at DEBUG ...
     about to log at INFO ...
     about to log at WARNING ...
     about to log at ERROR ...
     about to log at CRITICAL ...
     Calling decorated foo with False
     about to log at DEBUG ...
     about to log at INFO ...
     about to log at WARNING ...
     Calling decorated foo with True
     about to log at DEBUG ...
     about to log at INFO ...
     about to log at WARNING ...
     about to log at ERROR ...
     Actually logged at DEBUG
     Actually logged at INFO
     Actually logged at WARNING
     Actually logged at ERROR
     about to log at CRITICAL ...
     Actually logged at CRITICAL

As you can see, actual logging output only occurs when an event is
logged whose severity is ERROR or greater, but in that case, any
previous events at lower severities are also logged.

You can of course use the conventional means of decoration:

     @log_if_errors(logger)
     def foo(fail=False):
         ...


File: python.info,  Node: Sending logging messages to email with buffering,  Next: Formatting times using UTC GMT via configuration,  Prev: Buffering logging messages and outputting them conditionally,  Up: Logging Cookbook

9.8.29 Sending logging messages to email, with buffering
--------------------------------------------------------

To illustrate how you can send log messages via email, so that a set
number of messages are sent per email, you can subclass *note
BufferingHandler: 2c63.  In the following example, which you can adapt
to suit your specific needs, a simple test harness is provided which
allows you to run the script with command line arguments specifying what
you typically need to send things via SMTP. (Run the downloaded script
with the ‘-h’ argument to see the required and optional arguments.)

     import logging
     import logging.handlers
     import smtplib

     class BufferingSMTPHandler(logging.handlers.BufferingHandler):
         def __init__(self, mailhost, port, username, password, fromaddr, toaddrs,
                      subject, capacity):
             logging.handlers.BufferingHandler.__init__(self, capacity)
             self.mailhost = mailhost
             self.mailport = port
             self.username = username
             self.password = password
             self.fromaddr = fromaddr
             if isinstance(toaddrs, str):
                 toaddrs = [toaddrs]
             self.toaddrs = toaddrs
             self.subject = subject
             self.setFormatter(logging.Formatter("%(asctime)s %(levelname)-5s %(message)s"))

         def flush(self):
             if len(self.buffer) > 0:
                 try:
                     smtp = smtplib.SMTP(self.mailhost, self.mailport)
                     smtp.starttls()
                     smtp.login(self.username, self.password)
                     msg = "From: %s\r\nTo: %s\r\nSubject: %s\r\n\r\n" % (self.fromaddr, ','.join(self.toaddrs), self.subject)
                     for record in self.buffer:
                         s = self.format(record)
                         msg = msg + s + "\r\n"
                     smtp.sendmail(self.fromaddr, self.toaddrs, msg)
                     smtp.quit()
                 except Exception:
                     if logging.raiseExceptions:
                         raise
                 self.buffer = []

     if __name__ == '__main__':
         import argparse

         ap = argparse.ArgumentParser()
         aa = ap.add_argument
         aa('host', metavar='HOST', help='SMTP server')
         aa('--port', '-p', type=int, default=587, help='SMTP port')
         aa('user', metavar='USER', help='SMTP username')
         aa('password', metavar='PASSWORD', help='SMTP password')
         aa('to', metavar='TO', help='Addressee for emails')
         aa('sender', metavar='SENDER', help='Sender email address')
         aa('--subject', '-s',
            default='Test Logging email from Python logging module (buffering)',
            help='Subject of email')
         options = ap.parse_args()
         logger = logging.getLogger()
         logger.setLevel(logging.DEBUG)
         h = BufferingSMTPHandler(options.host, options.port, options.user,
                                  options.password, options.sender,
                                  options.to, options.subject, 10)
         logger.addHandler(h)
         for i in range(102):
             logger.info("Info index = %d", i)
         h.flush()
         h.close()

If you run this script and your SMTP server is correctly set up, you
should find that it sends eleven emails to the addressee you specify.
The first ten emails will each have ten log messages, and the eleventh
will have two messages.  That makes up 102 messages as specified in the
script.


File: python.info,  Node: Formatting times using UTC GMT via configuration,  Next: Using a context manager for selective logging,  Prev: Sending logging messages to email with buffering,  Up: Logging Cookbook

9.8.30 Formatting times using UTC (GMT) via configuration
---------------------------------------------------------

Sometimes you want to format times using UTC, which can be done using a
class such as ‘UTCFormatter’, shown below:

     import logging
     import time

     class UTCFormatter(logging.Formatter):
         converter = time.gmtime

and you can then use the ‘UTCFormatter’ in your code instead of *note
Formatter: 1400.  If you want to do that via configuration, you can use
the *note dictConfig(): 1147. API with an approach illustrated by the
following complete example:

     import logging
     import logging.config
     import time

     class UTCFormatter(logging.Formatter):
         converter = time.gmtime

     LOGGING = {
         'version': 1,
         'disable_existing_loggers': False,
         'formatters': {
             'utc': {
                 '()': UTCFormatter,
                 'format': '%(asctime)s %(message)s',
             },
             'local': {
                 'format': '%(asctime)s %(message)s',
             }
         },
         'handlers': {
             'console1': {
                 'class': 'logging.StreamHandler',
                 'formatter': 'utc',
             },
             'console2': {
                 'class': 'logging.StreamHandler',
                 'formatter': 'local',
             },
         },
         'root': {
             'handlers': ['console1', 'console2'],
        }
     }

     if __name__ == '__main__':
         logging.config.dictConfig(LOGGING)
         logging.warning('The local time is %s', time.asctime())

When this script is run, it should print something like:

     2015-10-17 12:53:29,501 The local time is Sat Oct 17 13:53:29 2015
     2015-10-17 13:53:29,501 The local time is Sat Oct 17 13:53:29 2015

showing how the time is formatted both as local time and UTC, one for
each handler.


File: python.info,  Node: Using a context manager for selective logging,  Next: A CLI application starter template,  Prev: Formatting times using UTC GMT via configuration,  Up: Logging Cookbook

9.8.31 Using a context manager for selective logging
----------------------------------------------------

There are times when it would be useful to temporarily change the
logging configuration and revert it back after doing something.  For
this, a context manager is the most obvious way of saving and restoring
the logging context.  Here is a simple example of such a context
manager, which allows you to optionally change the logging level and add
a logging handler purely in the scope of the context manager:

     import logging
     import sys

     class LoggingContext:
         def __init__(self, logger, level=None, handler=None, close=True):
             self.logger = logger
             self.level = level
             self.handler = handler
             self.close = close

         def __enter__(self):
             if self.level is not None:
                 self.old_level = self.logger.level
                 self.logger.setLevel(self.level)
             if self.handler:
                 self.logger.addHandler(self.handler)

         def __exit__(self, et, ev, tb):
             if self.level is not None:
                 self.logger.setLevel(self.old_level)
             if self.handler:
                 self.logger.removeHandler(self.handler)
             if self.handler and self.close:
                 self.handler.close()
             # implicit return of None => don't swallow exceptions

If you specify a level value, the logger's level is set to that value in
the scope of the with block covered by the context manager.  If you
specify a handler, it is added to the logger on entry to the block and
removed on exit from the block.  You can also ask the manager to close
the handler for you on block exit - you could do this if you don't need
the handler any more.

To illustrate how it works, we can add the following block of code to
the above:

     if __name__ == '__main__':
         logger = logging.getLogger('foo')
         logger.addHandler(logging.StreamHandler())
         logger.setLevel(logging.INFO)
         logger.info('1. This should appear just once on stderr.')
         logger.debug('2. This should not appear.')
         with LoggingContext(logger, level=logging.DEBUG):
             logger.debug('3. This should appear once on stderr.')
         logger.debug('4. This should not appear.')
         h = logging.StreamHandler(sys.stdout)
         with LoggingContext(logger, level=logging.DEBUG, handler=h, close=True):
             logger.debug('5. This should appear twice - once on stderr and once on stdout.')
         logger.info('6. This should appear just once on stderr.')
         logger.debug('7. This should not appear.')

We initially set the logger's level to ‘INFO’, so message #1 appears and
message #2 doesn't.  We then change the level to ‘DEBUG’ temporarily in
the following ‘with’ block, and so message #3 appears.  After the block
exits, the logger's level is restored to ‘INFO’ and so message #4
doesn't appear.  In the next ‘with’ block, we set the level to ‘DEBUG’
again but also add a handler writing to ‘sys.stdout’.  Thus, message #5
appears twice on the console (once via ‘stderr’ and once via ‘stdout’).
After the ‘with’ statement's completion, the status is as it was before
so message #6 appears (like message #1) whereas message #7 doesn't (just
like message #2).

If we run the resulting script, the result is as follows:

     $ python logctx.py
     1. This should appear just once on stderr.
     3. This should appear once on stderr.
     5. This should appear twice - once on stderr and once on stdout.
     5. This should appear twice - once on stderr and once on stdout.
     6. This should appear just once on stderr.

If we run it again, but pipe ‘stderr’ to ‘/dev/null’, we see the
following, which is the only message written to ‘stdout’:

     $ python logctx.py 2>/dev/null
     5. This should appear twice - once on stderr and once on stdout.

Once again, but piping ‘stdout’ to ‘/dev/null’, we get:

     $ python logctx.py >/dev/null
     1. This should appear just once on stderr.
     3. This should appear once on stderr.
     5. This should appear twice - once on stderr and once on stdout.
     6. This should appear just once on stderr.

In this case, the message #5 printed to ‘stdout’ doesn't appear, as
expected.

Of course, the approach described here can be generalised, for example
to attach logging filters temporarily.  Note that the above code works
in Python 2 as well as Python 3.


File: python.info,  Node: A CLI application starter template,  Next: A Qt GUI for logging,  Prev: Using a context manager for selective logging,  Up: Logging Cookbook

9.8.32 A CLI application starter template
-----------------------------------------

Here's an example which shows how you can:

   * Use a logging level based on command-line arguments

   * Dispatch to multiple subcommands in separate files, all logging at
     the same level in a consistent way

   * Make use of simple, minimal configuration

Suppose we have a command-line application whose job is to stop, start
or restart some services.  This could be organised for the purposes of
illustration as a file ‘app.py’ that is the main script for the
application, with individual commands implemented in ‘start.py’,
‘stop.py’ and ‘restart.py’.  Suppose further that we want to control the
verbosity of the application via a command-line argument, defaulting to
‘logging.INFO’.  Here's one way that ‘app.py’ could be written:

     import argparse
     import importlib
     import logging
     import os
     import sys

     def main(args=None):
         scriptname = os.path.basename(__file__)
         parser = argparse.ArgumentParser(scriptname)
         levels = ('DEBUG', 'INFO', 'WARNING', 'ERROR', 'CRITICAL')
         parser.add_argument('--log-level', default='INFO', choices=levels)
         subparsers = parser.add_subparsers(dest='command',
                                            help='Available commands:')
         start_cmd = subparsers.add_parser('start', help='Start a service')
         start_cmd.add_argument('name', metavar='NAME',
                                help='Name of service to start')
         stop_cmd = subparsers.add_parser('stop',
                                          help='Stop one or more services')
         stop_cmd.add_argument('names', metavar='NAME', nargs='+',
                               help='Name of service to stop')
         restart_cmd = subparsers.add_parser('restart',
                                             help='Restart one or more services')
         restart_cmd.add_argument('names', metavar='NAME', nargs='+',
                                  help='Name of service to restart')
         options = parser.parse_args()
         # the code to dispatch commands could all be in this file. For the purposes
         # of illustration only, we implement each command in a separate module.
         try:
             mod = importlib.import_module(options.command)
             cmd = getattr(mod, 'command')
         except (ImportError, AttributeError):
             print('Unable to find the code for command \'%s\'' % options.command)
             return 1
         # Could get fancy here and load configuration from file or dictionary
         logging.basicConfig(level=options.log_level,
                             format='%(levelname)s %(name)s %(message)s')
         cmd(options)

     if __name__ == '__main__':
         sys.exit(main())

And the ‘start’, ‘stop’ and ‘restart’ commands can be implemented in
separate modules, like so for starting:

     # start.py
     import logging

     logger = logging.getLogger(__name__)

     def command(options):
         logger.debug('About to start %s', options.name)
         # actually do the command processing here ...
         logger.info('Started the \'%s\' service.', options.name)

and thus for stopping:

     # stop.py
     import logging

     logger = logging.getLogger(__name__)

     def command(options):
         n = len(options.names)
         if n == 1:
             plural = ''
             services = '\'%s\'' % options.names[0]
         else:
             plural = 's'
             services = ', '.join('\'%s\'' % name for name in options.names)
             i = services.rfind(', ')
             services = services[:i] + ' and ' + services[i + 2:]
         logger.debug('About to stop %s', services)
         # actually do the command processing here ...
         logger.info('Stopped the %s service%s.', services, plural)

and similarly for restarting:

     # restart.py
     import logging

     logger = logging.getLogger(__name__)

     def command(options):
         n = len(options.names)
         if n == 1:
             plural = ''
             services = '\'%s\'' % options.names[0]
         else:
             plural = 's'
             services = ', '.join('\'%s\'' % name for name in options.names)
             i = services.rfind(', ')
             services = services[:i] + ' and ' + services[i + 2:]
         logger.debug('About to restart %s', services)
         # actually do the command processing here ...
         logger.info('Restarted the %s service%s.', services, plural)

If we run this application with the default log level, we get output
like this:

     $ python app.py start foo
     INFO start Started the 'foo' service.

     $ python app.py stop foo bar
     INFO stop Stopped the 'foo' and 'bar' services.

     $ python app.py restart foo bar baz
     INFO restart Restarted the 'foo', 'bar' and 'baz' services.

The first word is the logging level, and the second word is the module
or package name of the place where the event was logged.

If we change the logging level, then we can change the information sent
to the log.  For example, if we want more information:

     $ python app.py --log-level DEBUG start foo
     DEBUG start About to start foo
     INFO start Started the 'foo' service.

     $ python app.py --log-level DEBUG stop foo bar
     DEBUG stop About to stop 'foo' and 'bar'
     INFO stop Stopped the 'foo' and 'bar' services.

     $ python app.py --log-level DEBUG restart foo bar baz
     DEBUG restart About to restart 'foo', 'bar' and 'baz'
     INFO restart Restarted the 'foo', 'bar' and 'baz' services.

And if we want less:

     $ python app.py --log-level WARNING start foo
     $ python app.py --log-level WARNING stop foo bar
     $ python app.py --log-level WARNING restart foo bar baz

In this case, the commands don't print anything to the console, since
nothing at ‘WARNING’ level or above is logged by them.


File: python.info,  Node: A Qt GUI for logging,  Next: Logging to syslog with RFC5424 support,  Prev: A CLI application starter template,  Up: Logging Cookbook

9.8.33 A Qt GUI for logging
---------------------------

A question that comes up from time to time is about how to log to a GUI
application.  The Qt(1) framework is a popular cross-platform UI
framework with Python bindings using PySide2(2) or PyQt5(3) libraries.

The following example shows how to log to a Qt GUI. This introduces a
simple ‘QtHandler’ class which takes a callable, which should be a slot
in the main thread that does GUI updates.  A worker thread is also
created to show how you can log to the GUI from both the UI itself (via
a button for manual logging) as well as a worker thread doing work in
the background (here, just logging messages at random levels with random
short delays in between).

The worker thread is implemented using Qt's ‘QThread’ class rather than
the *note threading: d6. module, as there are circumstances where one
has to use ‘QThread’, which offers better integration with other ‘Qt’
components.

The code should work with recent releases of any of ‘PySide6’, ‘PyQt6’,
‘PySide2’ or ‘PyQt5’.  You should be able to adapt the approach to
earlier versions of Qt.  Please refer to the comments in the code
snippet for more detailed information.

     import datetime
     import logging
     import random
     import sys
     import time

     # Deal with minor differences between different Qt packages
     try:
         from PySide6 import QtCore, QtGui, QtWidgets
         Signal = QtCore.Signal
         Slot = QtCore.Slot
     except ImportError:
         try:
             from PyQt6 import QtCore, QtGui, QtWidgets
             Signal = QtCore.pyqtSignal
             Slot = QtCore.pyqtSlot
         except ImportError:
             try:
                 from PySide2 import QtCore, QtGui, QtWidgets
                 Signal = QtCore.Signal
                 Slot = QtCore.Slot
             except ImportError:
                 from PyQt5 import QtCore, QtGui, QtWidgets
                 Signal = QtCore.pyqtSignal
                 Slot = QtCore.pyqtSlot

     logger = logging.getLogger(__name__)


     #
     # Signals need to be contained in a QObject or subclass in order to be correctly
     # initialized.
     #
     class Signaller(QtCore.QObject):
         signal = Signal(str, logging.LogRecord)

     #
     # Output to a Qt GUI is only supposed to happen on the main thread. So, this
     # handler is designed to take a slot function which is set up to run in the main
     # thread. In this example, the function takes a string argument which is a
     # formatted log message, and the log record which generated it. The formatted
     # string is just a convenience - you could format a string for output any way
     # you like in the slot function itself.
     #
     # You specify the slot function to do whatever GUI updates you want. The handler
     # doesn't know or care about specific UI elements.
     #
     class QtHandler(logging.Handler):
         def __init__(self, slotfunc, *args, **kwargs):
             super().__init__(*args, **kwargs)
             self.signaller = Signaller()
             self.signaller.signal.connect(slotfunc)

         def emit(self, record):
             s = self.format(record)
             self.signaller.signal.emit(s, record)

     #
     # This example uses QThreads, which means that the threads at the Python level
     # are named something like "Dummy-1". The function below gets the Qt name of the
     # current thread.
     #
     def ctname():
         return QtCore.QThread.currentThread().objectName()


     #
     # Used to generate random levels for logging.
     #
     LEVELS = (logging.DEBUG, logging.INFO, logging.WARNING, logging.ERROR,
               logging.CRITICAL)

     #
     # This worker class represents work that is done in a thread separate to the
     # main thread. The way the thread is kicked off to do work is via a button press
     # that connects to a slot in the worker.
     #
     # Because the default threadName value in the LogRecord isn't much use, we add
     # a qThreadName which contains the QThread name as computed above, and pass that
     # value in an "extra" dictionary which is used to update the LogRecord with the
     # QThread name.
     #
     # This example worker just outputs messages sequentially, interspersed with
     # random delays of the order of a few seconds.
     #
     class Worker(QtCore.QObject):
         @Slot()
         def start(self):
             extra = {'qThreadName': ctname() }
             logger.debug('Started work', extra=extra)
             i = 1
             # Let the thread run until interrupted. This allows reasonably clean
             # thread termination.
             while not QtCore.QThread.currentThread().isInterruptionRequested():
                 delay = 0.5 + random.random() * 2
                 time.sleep(delay)
                 try:
                     if random.random() < 0.1:
                         raise ValueError('Exception raised: %d' % i)
                     else:
                         level = random.choice(LEVELS)
                         logger.log(level, 'Message after delay of %3.1f: %d', delay, i, extra=extra)
                 except ValueError as e:
                     logger.exception('Failed: %s', e, extra=extra)
                 i += 1

     #
     # Implement a simple UI for this cookbook example. This contains:
     #
     # * A read-only text edit window which holds formatted log messages
     # * A button to start work and log stuff in a separate thread
     # * A button to log something from the main thread
     # * A button to clear the log window
     #
     class Window(QtWidgets.QWidget):

         COLORS = {
             logging.DEBUG: 'black',
             logging.INFO: 'blue',
             logging.WARNING: 'orange',
             logging.ERROR: 'red',
             logging.CRITICAL: 'purple',
         }

         def __init__(self, app):
             super().__init__()
             self.app = app
             self.textedit = te = QtWidgets.QPlainTextEdit(self)
             # Set whatever the default monospace font is for the platform
             f = QtGui.QFont('nosuchfont')
             if hasattr(f, 'Monospace'):
                 f.setStyleHint(f.Monospace)
             else:
                 f.setStyleHint(f.StyleHint.Monospace)  # for Qt6
             te.setFont(f)
             te.setReadOnly(True)
             PB = QtWidgets.QPushButton
             self.work_button = PB('Start background work', self)
             self.log_button = PB('Log a message at a random level', self)
             self.clear_button = PB('Clear log window', self)
             self.handler = h = QtHandler(self.update_status)
             # Remember to use qThreadName rather than threadName in the format string.
             fs = '%(asctime)s %(qThreadName)-12s %(levelname)-8s %(message)s'
             formatter = logging.Formatter(fs)
             h.setFormatter(formatter)
             logger.addHandler(h)
             # Set up to terminate the QThread when we exit
             app.aboutToQuit.connect(self.force_quit)

             # Lay out all the widgets
             layout = QtWidgets.QVBoxLayout(self)
             layout.addWidget(te)
             layout.addWidget(self.work_button)
             layout.addWidget(self.log_button)
             layout.addWidget(self.clear_button)
             self.setFixedSize(900, 400)

             # Connect the non-worker slots and signals
             self.log_button.clicked.connect(self.manual_update)
             self.clear_button.clicked.connect(self.clear_display)

             # Start a new worker thread and connect the slots for the worker
             self.start_thread()
             self.work_button.clicked.connect(self.worker.start)
             # Once started, the button should be disabled
             self.work_button.clicked.connect(lambda : self.work_button.setEnabled(False))

         def start_thread(self):
             self.worker = Worker()
             self.worker_thread = QtCore.QThread()
             self.worker.setObjectName('Worker')
             self.worker_thread.setObjectName('WorkerThread')  # for qThreadName
             self.worker.moveToThread(self.worker_thread)
             # This will start an event loop in the worker thread
             self.worker_thread.start()

         def kill_thread(self):
             # Just tell the worker to stop, then tell it to quit and wait for that
             # to happen
             self.worker_thread.requestInterruption()
             if self.worker_thread.isRunning():
                 self.worker_thread.quit()
                 self.worker_thread.wait()
             else:
                 print('worker has already exited.')

         def force_quit(self):
             # For use when the window is closed
             if self.worker_thread.isRunning():
                 self.kill_thread()

         # The functions below update the UI and run in the main thread because
         # that's where the slots are set up

         @Slot(str, logging.LogRecord)
         def update_status(self, status, record):
             color = self.COLORS.get(record.levelno, 'black')
             s = '<pre><font color="%s">%s</font></pre>' % (color, status)
             self.textedit.appendHtml(s)

         @Slot()
         def manual_update(self):
             # This function uses the formatted message passed in, but also uses
             # information from the record to format the message in an appropriate
             # color according to its severity (level).
             level = random.choice(LEVELS)
             extra = {'qThreadName': ctname() }
             logger.log(level, 'Manually logged!', extra=extra)

         @Slot()
         def clear_display(self):
             self.textedit.clear()


     def main():
         QtCore.QThread.currentThread().setObjectName('MainThread')
         logging.getLogger().setLevel(logging.DEBUG)
         app = QtWidgets.QApplication(sys.argv)
         example = Window(app)
         example.show()
         if hasattr(app, 'exec'):
             rc = app.exec()
         else:
             rc = app.exec_()
         sys.exit(rc)

     if __name__=='__main__':
         main()

   ---------- Footnotes ----------

   (1) https://www.qt.io/

   (2) https://pypi.org/project/PySide2/

   (3) https://pypi.org/project/PyQt5/


File: python.info,  Node: Logging to syslog with RFC5424 support,  Next: How to treat a logger like an output stream,  Prev: A Qt GUI for logging,  Up: Logging Cookbook

9.8.34 Logging to syslog with RFC5424 support
---------------------------------------------

Although RFC 5424(1) dates from 2009, most syslog servers are configured
by default to use the older RFC 3164(2), which hails from 2001.  When
‘logging’ was added to Python in 2003, it supported the earlier (and
only existing) protocol at the time.  Since RFC5424 came out, as there
has not been widespread deployment of it in syslog servers, the *note
SysLogHandler: 602. functionality has not been updated.

RFC 5424 contains some useful features such as support for structured
data, and if you need to be able to log to a syslog server with support
for it, you can do so with a subclassed handler which looks something
like this:

     import datetime
     import logging.handlers
     import re
     import socket
     import time

     class SysLogHandler5424(logging.handlers.SysLogHandler):

         tz_offset = re.compile(r'([+-]\d{2})(\d{2})$')
         escaped = re.compile(r'([\]"\\])')

         def __init__(self, *args, **kwargs):
             self.msgid = kwargs.pop('msgid', None)
             self.appname = kwargs.pop('appname', None)
             super().__init__(*args, **kwargs)

         def format(self, record):
             version = 1
             asctime = datetime.datetime.fromtimestamp(record.created).isoformat()
             m = self.tz_offset.match(time.strftime('%z'))
             has_offset = False
             if m and time.timezone:
                 hrs, mins = m.groups()
                 if int(hrs) or int(mins):
                     has_offset = True
             if not has_offset:
                 asctime += 'Z'
             else:
                 asctime += f'{hrs}:{mins}'
             try:
                 hostname = socket.gethostname()
             except Exception:
                 hostname = '-'
             appname = self.appname or '-'
             procid = record.process
             msgid = '-'
             msg = super().format(record)
             sdata = '-'
             if hasattr(record, 'structured_data'):
                 sd = record.structured_data
                 # This should be a dict where the keys are SD-ID and the value is a
                 # dict mapping PARAM-NAME to PARAM-VALUE (refer to the RFC for what these
                 # mean)
                 # There's no error checking here - it's purely for illustration, and you
                 # can adapt this code for use in production environments
                 parts = []

                 def replacer(m):
                     g = m.groups()
                     return '\\' + g[0]

                 for sdid, dv in sd.items():
                     part = f'[{sdid}'
                     for k, v in dv.items():
                         s = str(v)
                         s = self.escaped.sub(replacer, s)
                         part += f' {k}="{s}"'
                     part += ']'
                     parts.append(part)
                 sdata = ''.join(parts)
             return f'{version} {asctime} {hostname} {appname} {procid} {msgid} {sdata} {msg}'

You'll need to be familiar with RFC 5424 to fully understand the above
code, and it may be that you have slightly different needs (e.g.  for
how you pass structural data to the log).  Nevertheless, the above
should be adaptable to your speciric needs.  With the above handler,
you'd pass structured data using something like this:

     sd = {
         'foo@12345': {'bar': 'baz', 'baz': 'bozz', 'fizz': r'buzz'},
         'foo@54321': {'rab': 'baz', 'zab': 'bozz', 'zzif': r'buzz'}
     }
     extra = {'structured_data': sd}
     i = 1
     logger.debug('Message %d', i, extra=extra)

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc5424.html

   (2) https://datatracker.ietf.org/doc/html/rfc3164.html


File: python.info,  Node: How to treat a logger like an output stream,  Next: Patterns to avoid,  Prev: Logging to syslog with RFC5424 support,  Up: Logging Cookbook

9.8.35 How to treat a logger like an output stream
--------------------------------------------------

Sometimes, you need to interface to a third-party API which expects a
file-like object to write to, but you want to direct the API's output to
a logger.  You can do this using a class which wraps a logger with a
file-like API. Here's a short script illustrating such a class:

     import logging

     class LoggerWriter:
         def __init__(self, logger, level):
             self.logger = logger
             self.level = level

         def write(self, message):
             if message != '\n':  # avoid printing bare newlines, if you like
                 self.logger.log(self.level, message)

         def flush(self):
             # doesn't actually do anything, but might be expected of a file-like
             # object - so optional depending on your situation
             pass

         def close(self):
             # doesn't actually do anything, but might be expected of a file-like
             # object - so optional depending on your situation. You might want
             # to set a flag so that later calls to write raise an exception
             pass

     def main():
         logging.basicConfig(level=logging.DEBUG)
         logger = logging.getLogger('demo')
         info_fp = LoggerWriter(logger, logging.INFO)
         debug_fp = LoggerWriter(logger, logging.DEBUG)
         print('An INFO message', file=info_fp)
         print('A DEBUG message', file=debug_fp)

     if __name__ == "__main__":
         main()

When this script is run, it prints

     INFO:demo:An INFO message
     DEBUG:demo:A DEBUG message

You could also use ‘LoggerWriter’ to redirect ‘sys.stdout’ and
‘sys.stderr’ by doing something like this:

     import sys

     sys.stdout = LoggerWriter(logger, logging.INFO)
     sys.stderr = LoggerWriter(logger, logging.WARNING)

You should do this 'after' configuring logging for your needs.  In the
above example, the *note basicConfig(): 9a4. call does this (using the
‘sys.stderr’ value 'before' it is overwritten by a ‘LoggerWriter’
instance).  Then, you'd get this kind of result:

     >>> print('Foo')
     INFO:demo:Foo
     >>> print('Bar', file=sys.stderr)
     WARNING:demo:Bar
     >>>

Of course, the examples above show output according to the format used
by *note basicConfig(): 9a4, but you can use a different formatter when
you configure logging.

Note that with the above scheme, you are somewhat at the mercy of
buffering and the sequence of write calls which you are intercepting.
For example, with the definition of ‘LoggerWriter’ above, if you have
the snippet

     sys.stderr = LoggerWriter(logger, logging.WARNING)
     1 / 0

then running the script results in

     WARNING:demo:Traceback (most recent call last):

     WARNING:demo:  File "/home/runner/cookbook-loggerwriter/test.py", line 53, in <module>

     WARNING:demo:
     WARNING:demo:main()
     WARNING:demo:  File "/home/runner/cookbook-loggerwriter/test.py", line 49, in main

     WARNING:demo:
     WARNING:demo:1 / 0
     WARNING:demo:ZeroDivisionError
     WARNING:demo::
     WARNING:demo:division by zero

As you can see, this output isn't ideal.  That's because the underlying
code which writes to ‘sys.stderr’ makes multiple writes, each of which
results in a separate logged line (for example, the last three lines
above).  To get around this problem, you need to buffer things and only
output log lines when newlines are seen.  Let's use a slightly better
implementation of ‘LoggerWriter’:

     class BufferingLoggerWriter(LoggerWriter):
         def __init__(self, logger, level):
             super().__init__(logger, level)
             self.buffer = ''

         def write(self, message):
             if '\n' not in message:
                 self.buffer += message
             else:
                 parts = message.split('\n')
                 if self.buffer:
                     s = self.buffer + parts.pop(0)
                     self.logger.log(self.level, s)
                 self.buffer = parts.pop()
                 for part in parts:
                     self.logger.log(self.level, part)

This just buffers up stuff until a newline is seen, and then logs
complete lines.  With this approach, you get better output:

     WARNING:demo:Traceback (most recent call last):
     WARNING:demo:  File "/home/runner/cookbook-loggerwriter/main.py", line 55, in <module>
     WARNING:demo:    main()
     WARNING:demo:  File "/home/runner/cookbook-loggerwriter/main.py", line 52, in main
     WARNING:demo:    1/0
     WARNING:demo:ZeroDivisionError: division by zero


File: python.info,  Node: Patterns to avoid,  Next: Other resources,  Prev: How to treat a logger like an output stream,  Up: Logging Cookbook

9.8.36 Patterns to avoid
------------------------

Although the preceding sections have described ways of doing things you
might need to do or deal with, it is worth mentioning some usage
patterns which are 'unhelpful', and which should therefore be avoided in
most cases.  The following sections are in no particular order.

* Menu:

* Opening the same log file multiple times::
* Using loggers as attributes in a class or passing them as parameters::
* Adding handlers other than NullHandler to a logger in a library::
* Creating a lot of loggers::


File: python.info,  Node: Opening the same log file multiple times,  Next: Using loggers as attributes in a class or passing them as parameters,  Up: Patterns to avoid

9.8.36.1 Opening the same log file multiple times
.................................................

On Windows, you will generally not be able to open the same file
multiple times as this will lead to a "file is in use by another
process" error.  However, on POSIX platforms you'll not get any errors
if you open the same file multiple times.  This could be done
accidentally, for example by:

   * Adding a file handler more than once which references the same file
     (e.g.  by a copy/paste/forget-to-change error).

   * Opening two files that look different, as they have different
     names, but are the same because one is a symbolic link to the
     other.

   * Forking a process, following which both parent and child have a
     reference to the same file.  This might be through use of the *note
     multiprocessing: 86. module, for example.

Opening a file multiple times might 'appear' to work most of the time,
but can lead to a number of problems in practice:

   * Logging output can be garbled because multiple threads or processes
     try to write to the same file.  Although logging guards against
     concurrent use of the same handler instance by multiple threads,
     there is no such protection if concurrent writes are attempted by
     two different threads using two different handler instances which
     happen to point to the same file.

   * An attempt to delete a file (e.g.  during file rotation) silently
     fails, because there is another reference pointing to it.  This can
     lead to confusion and wasted debugging time - log entries end up in
     unexpected places, or are lost altogether.  Or a file that was
     supposed to be moved remains in place, and grows in size
     unexpectedly despite size-based rotation being supposedly in place.

Use the techniques outlined in *note Logging to a single file from
multiple processes: 4d61. to circumvent such issues.


File: python.info,  Node: Using loggers as attributes in a class or passing them as parameters,  Next: Adding handlers other than NullHandler to a logger in a library,  Prev: Opening the same log file multiple times,  Up: Patterns to avoid

9.8.36.2 Using loggers as attributes in a class or passing them as parameters
.............................................................................

While there might be unusual cases where you'll need to do this, in
general there is no point because loggers are singletons.  Code can
always access a given logger instance by name using
‘logging.getLogger(name)’, so passing instances around and holding them
as instance attributes is pointless.  Note that in other languages such
as Java and C#, loggers are often static class attributes.  However,
this pattern doesn't make sense in Python, where the module (and not the
class) is the unit of software decomposition.


File: python.info,  Node: Adding handlers other than NullHandler to a logger in a library,  Next: Creating a lot of loggers,  Prev: Using loggers as attributes in a class or passing them as parameters,  Up: Patterns to avoid

9.8.36.3 Adding handlers other than ‘NullHandler’ to a logger in a library
..........................................................................

Configuring logging by adding handlers, formatters and filters is the
responsibility of the application developer, not the library developer.
If you are maintaining a library, ensure that you don't add handlers to
any of your loggers other than a *note NullHandler: 121c. instance.


File: python.info,  Node: Creating a lot of loggers,  Prev: Adding handlers other than NullHandler to a logger in a library,  Up: Patterns to avoid

9.8.36.4 Creating a lot of loggers
..................................

Loggers are singletons that are never freed during a script execution,
and so creating lots of loggers will use up memory which can't then be
freed.  Rather than create a logger per e.g.  file processed or network
connection made, use the *note existing mechanisms: 2bea. for passing
contextual information into your logs and restrict the loggers created
to those describing areas within your application (generally modules,
but occasionally slightly more fine-grained than that).


File: python.info,  Node: Other resources,  Prev: Patterns to avoid,  Up: Logging Cookbook

9.8.37 Other resources
----------------------

也參考
......

*note logging: 7b. 模組

     API reference for the logging module.

*note logging.config: 7c. 模組

     Configuration API for the logging module.

*note logging.handlers: 7d. 模組

     Useful handlers included with the logging module.

*note 基礎教學: 118d.

*note 進階教學: 118e.


File: python.info,  Node: 如何使用正規表示式,  Next: Socket 程式設計指南,  Prev: Logging Cookbook,  Up: Python 如何達成任務

9.9 如何使用正規表示式
======================


作者: A.M. Kuchling <<amk@amk.ca>>

摘要
....

此文件為如何在 Python 中使用 *note re: a7. 模組來撰寫正規表示式的入門指
導。進階使用及參考文件請見函式庫參考一章。

* Menu:

* 簡介: 簡介<12>.
* Simple Patterns::
* Using Regular Expressions::
* More Pattern Power::
* Modifying Strings::
* Common Problems::
* Feedback::


File: python.info,  Node: 簡介<12>,  Next: Simple Patterns,  Up: 如何使用正規表示式

9.9.1 簡介
----------

正規表示式 (也稱為 REs、regexes 或 regex patterns) 是一個輕量且高專業化
的程式語言。在 Python 中可透過內建的 *note re: a7. 模組直接使用。你可以
使用此輕量化的語言針對想要匹配的一組字串撰寫規則，這組字串可能包含了英語
句子、e-mail 地址、TeX 命令或任何東西。你可以檢查如「這組字串是否匹配這
個規則？」或「這組字串中是否有任一處匹配這個規則？」。除此之外，你也可以
使用 REs 來修改或是切割字串。

Regular expression patterns are compiled into a series of bytecodes
which are then executed by a matching engine written in C. For advanced
use, it may be necessary to pay careful attention to how the engine will
execute a given RE, and write the RE in a certain way in order to
produce bytecode that runs faster.  Optimization isn't covered in this
document, because it requires that you have a good understanding of the
matching engine's internals.

The regular expression language is relatively small and restricted, so
not all possible string processing tasks can be done using regular
expressions.  There are also tasks that 'can' be done with regular
expressions, but the expressions turn out to be very complicated.  In
these cases, you may be better off writing Python code to do the
processing; while Python code will be slower than an elaborate regular
expression, it will also probably be more understandable.


File: python.info,  Node: Simple Patterns,  Next: Using Regular Expressions,  Prev: 簡介<12>,  Up: 如何使用正規表示式

9.9.2 Simple Patterns
---------------------

We'll start by learning about the simplest possible regular expressions.
Since regular expressions are used to operate on strings, we'll begin
with the most common task: matching characters.

For a detailed explanation of the computer science underlying regular
expressions (deterministic and non-deterministic finite automata), you
can refer to almost any textbook on writing compilers.

* Menu:

* Matching Characters::
* Repeating Things::


File: python.info,  Node: Matching Characters,  Next: Repeating Things,  Up: Simple Patterns

9.9.2.1 Matching Characters
...........................

Most letters and characters will simply match themselves.  For example,
the regular expression ‘test’ will match the string ‘test’ exactly.
(You can enable a case-insensitive mode that would let this RE match
‘Test’ or ‘TEST’ as well; more about this later.)

There are exceptions to this rule; some characters are special
'metacharacters', and don't match themselves.  Instead, they signal that
some out-of-the-ordinary thing should be matched, or they affect other
portions of the RE by repeating them or changing their meaning.  Much of
this document is devoted to discussing various metacharacters and what
they do.

Here's a complete list of the metacharacters; their meanings will be
discussed in the rest of this HOWTO.

     . ^ $ * + ? { } [ ] \ | ( )

The first metacharacters we'll look at are ‘[’ and ‘]’.  They're used
for specifying a character class, which is a set of characters that you
wish to match.  Characters can be listed individually, or a range of
characters can be indicated by giving two characters and separating them
by a ‘'-'’.  For example, ‘[abc]’ will match any of the characters ‘a’,
‘b’, or ‘c’; this is the same as ‘[a-c]’, which uses a range to express
the same set of characters.  If you wanted to match only lowercase
letters, your RE would be ‘[a-z]’.

Metacharacters (except ‘\’) are not active inside classes.  For example,
‘[akm$]’ will match any of the characters ‘'a'’, ‘'k'’, ‘'m'’, or ‘'$'’;
‘'$'’ is usually a metacharacter, but inside a character class it's
stripped of its special nature.

You can match the characters not listed within the class by
'complementing' the set.  This is indicated by including a ‘'^'’ as the
first character of the class.  For example, ‘[^5]’ will match any
character except ‘'5'’.  If the caret appears elsewhere in a character
class, it does not have special meaning.  For example: ‘[5^]’ will match
either a ‘'5'’ or a ‘'^'’.

Perhaps the most important metacharacter is the backslash, ‘\’.  As in
Python string literals, the backslash can be followed by various
characters to signal various special sequences.  It's also used to
escape all the metacharacters so you can still match them in patterns;
for example, if you need to match a ‘[’ or ‘\’, you can precede them
with a backslash to remove their special meaning: ‘\[’ or ‘\\’.

Some of the special sequences beginning with ‘'\'’ represent predefined
sets of characters that are often useful, such as the set of digits, the
set of letters, or the set of anything that isn't whitespace.

Let's take an example: ‘\w’ matches any alphanumeric character.  If the
regex pattern is expressed in bytes, this is equivalent to the class
‘[a-zA-Z0-9_]’.  If the regex pattern is a string, ‘\w’ will match all
the characters marked as letters in the Unicode database provided by the
*note unicodedata: ee. module.  You can use the more restricted
definition of ‘\w’ in a string pattern by supplying the *note re.ASCII:
5d3. flag when compiling the regular expression.

The following list of special sequences isn't complete.  For a complete
list of sequences and expanded class definitions for Unicode string
patterns, see the last part of *note Regular Expression Syntax: 6c8. in
the Standard Library reference.  In general, the Unicode versions match
any character that's in the appropriate category in the Unicode
database.

‘\d’

     Matches any decimal digit; this is equivalent to the class ‘[0-9]’.

‘\D’

     Matches any non-digit character; this is equivalent to the class
     ‘[^0-9]’.

‘\s’

     Matches any whitespace character; this is equivalent to the class
     ‘[ \t\n\r\f\v]’.

‘\S’

     Matches any non-whitespace character; this is equivalent to the
     class ‘[^ \t\n\r\f\v]’.

‘\w’

     Matches any alphanumeric character; this is equivalent to the class
     ‘[a-zA-Z0-9_]’.

‘\W’

     Matches any non-alphanumeric character; this is equivalent to the
     class ‘[^a-zA-Z0-9_]’.

These sequences can be included inside a character class.  For example,
‘[\s,.]’ is a character class that will match any whitespace character,
or ‘','’ or ‘'.'’.

The final metacharacter in this section is ‘.’.  It matches anything
except a newline character, and there's an alternate mode (*note
re.DOTALL: 21ca.) where it will match even a newline.  ‘.’ is often used
where you want to match "any character".


File: python.info,  Node: Repeating Things,  Prev: Matching Characters,  Up: Simple Patterns

9.9.2.2 Repeating Things
........................

Being able to match varying sets of characters is the first thing
regular expressions can do that isn't already possible with the methods
available on strings.  However, if that was the only additional
capability of regexes, they wouldn't be much of an advance.  Another
capability is that you can specify that portions of the RE must be
repeated a certain number of times.

The first metacharacter for repeating things that we'll look at is ‘*’.
‘*’ doesn't match the literal character ‘'*'’; instead, it specifies
that the previous character can be matched zero or more times, instead
of exactly once.

For example, ‘ca*t’ will match ‘'ct'’ (0 ‘'a'’ characters), ‘'cat'’ (1
‘'a'’), ‘'caaat'’ (3 ‘'a'’ characters), and so forth.

Repetitions such as ‘*’ are 'greedy'; when repeating a RE, the matching
engine will try to repeat it as many times as possible.  If later
portions of the pattern don't match, the matching engine will then back
up and try again with fewer repetitions.

A step-by-step example will make this more obvious.  Let's consider the
expression ‘a[bcd]*b’.  This matches the letter ‘'a'’, zero or more
letters from the class ‘[bcd]’, and finally ends with a ‘'b'’.  Now
imagine matching this RE against the string ‘'abcbd'’.

Step       Matched         Explanation
                           
-----------------------------------------------------------------
                           
1          ‘a’             The ‘a’ in the RE matches.
                           
                           
2          ‘abcbd’         The engine matches ‘[bcd]*’, going
                           as far as it can, which is to the
                           end of the string.
                           
                           
3          'Failure'       The engine tries to match ‘b’, but
                           the current position is at the end
                           of the string, so it fails.
                           
                           
4          ‘abcb’          Back up, so that ‘[bcd]*’ matches
                           one less character.
                           
                           
5          'Failure'       Try ‘b’ again, but the current
                           position is at the last character,
                           which is a ‘'d'’.
                           
                           
6          ‘abc’           Back up again, so that ‘[bcd]*’ is
                           only matching ‘bc’.
                           
                           
6          ‘abcb’          Try ‘b’ again.  This time the
                           character at the current position
                           is ‘'b'’, so it succeeds.
                           

The end of the RE has now been reached, and it has matched ‘'abcb'’.
This demonstrates how the matching engine goes as far as it can at
first, and if no match is found it will then progressively back up and
retry the rest of the RE again and again.  It will back up until it has
tried zero matches for ‘[bcd]*’, and if that subsequently fails, the
engine will conclude that the string doesn't match the RE at all.

Another repeating metacharacter is ‘+’, which matches one or more times.
Pay careful attention to the difference between ‘*’ and ‘+’; ‘*’ matches
'zero' or more times, so whatever's being repeated may not be present at
all, while ‘+’ requires at least 'one' occurrence.  To use a similar
example, ‘ca+t’ will match ‘'cat'’ (1 ‘'a'’), ‘'caaat'’ (3 ‘'a'’s), but
won't match ‘'ct'’.

There are two more repeating operators or quantifiers.  The question
mark character, ‘?’, matches either once or zero times; you can think of
it as marking something as being optional.  For example, ‘home-?brew’
matches either ‘'homebrew'’ or ‘'home-brew'’.

The most complicated quantifier is ‘{m,n}’, where 'm' and 'n' are
decimal integers.  This quantifier means there must be at least 'm'
repetitions, and at most 'n'.  For example, ‘a/{1,3}b’ will match
‘'a/b'’, ‘'a//b'’, and ‘'a///b'’.  It won't match ‘'ab'’, which has no
slashes, or ‘'a////b'’, which has four.

You can omit either 'm' or 'n'; in that case, a reasonable value is
assumed for the missing value.  Omitting 'm' is interpreted as a lower
limit of 0, while omitting 'n' results in an upper bound of infinity.

The simplest case ‘{m}’ matches the preceding item exactly 'm' times.
For example, ‘a/{2}b’ will only match ‘'a//b'’.

Readers of a reductionist bent may notice that the three other
quantifiers can all be expressed using this notation.  ‘{0,}’ is the
same as ‘*’, ‘{1,}’ is equivalent to ‘+’, and ‘{0,1}’ is the same as
‘?’.  It's better to use ‘*’, ‘+’, or ‘?’ when you can, simply because
they're shorter and easier to read.


File: python.info,  Node: Using Regular Expressions,  Next: More Pattern Power,  Prev: Simple Patterns,  Up: 如何使用正規表示式

9.9.3 Using Regular Expressions
-------------------------------

Now that we've looked at some simple regular expressions, how do we
actually use them in Python?  The *note re: a7. module provides an
interface to the regular expression engine, allowing you to compile REs
into objects and then perform matches with them.

* Menu:

* Compiling Regular Expressions::
* The Backslash Plague::
* Performing Matches::
* Module-Level Functions: Module-Level Functions<2>.
* Compilation Flags::


File: python.info,  Node: Compiling Regular Expressions,  Next: The Backslash Plague,  Up: Using Regular Expressions

9.9.3.1 Compiling Regular Expressions
.....................................

Regular expressions are compiled into pattern objects, which have
methods for various operations such as searching for pattern matches or
performing string substitutions.

     >>> import re
     >>> p = re.compile('ab*')
     >>> p
     re.compile('ab*')

*note re.compile(): b7a. also accepts an optional 'flags' argument, used
to enable various special features and syntax variations.  We'll go over
the available settings later, but for now a single example will do:

     >>> p = re.compile('ab*', re.IGNORECASE)

The RE is passed to *note re.compile(): b7a. as a string.  REs are
handled as strings because regular expressions aren't part of the core
Python language, and no special syntax was created for expressing them.
(There are applications that don't need REs at all, so there's no need
to bloat the language specification by including them.)  Instead, the
*note re: a7. module is simply a C extension module included with
Python, just like the *note socket: b8. or *note zlib: 119. modules.

Putting REs in strings keeps the Python language simpler, but has one
disadvantage which is the topic of the next section.


File: python.info,  Node: The Backslash Plague,  Next: Performing Matches,  Prev: Compiling Regular Expressions,  Up: Using Regular Expressions

9.9.3.2 The Backslash Plague
............................

As stated earlier, regular expressions use the backslash character
(‘'\'’) to indicate special forms or to allow special characters to be
used without invoking their special meaning.  This conflicts with
Python's usage of the same character for the same purpose in string
literals.

Let's say you want to write a RE that matches the string ‘\section’,
which might be found in a LaTeX file.  To figure out what to write in
the program code, start with the desired string to be matched.  Next,
you must escape any backslashes and other metacharacters by preceding
them with a backslash, resulting in the string ‘\\section’.  The
resulting string that must be passed to *note re.compile(): b7a. must be
‘\\section’.  However, to express this as a Python string literal, both
backslashes must be escaped 'again'.

Characters              Stage
                        
-----------------------------------------------------------------------
                        
‘\section’              Text string to be matched
                        
                        
‘\\section’             Escaped backslash for
                        *note re.compile(): b7a.
                        
                        
‘"\\\\section"’         Escaped backslashes for a string literal
                        

In short, to match a literal backslash, one has to write ‘'\\\\'’ as the
RE string, because the regular expression must be ‘\\’, and each
backslash must be expressed as ‘\\’ inside a regular Python string
literal.  In REs that feature backslashes repeatedly, this leads to lots
of repeated backslashes and makes the resulting strings difficult to
understand.

The solution is to use Python's raw string notation for regular
expressions; backslashes are not handled in any special way in a string
literal prefixed with ‘'r'’, so ‘r"\n"’ is a two-character string
containing ‘'\'’ and ‘'n'’, while ‘"\n"’ is a one-character string
containing a newline.  Regular expressions will often be written in
Python code using this raw string notation.

In addition, special escape sequences that are valid in regular
expressions, but not valid as Python string literals, now result in a
*note DeprecationWarning: 18b. and will eventually become a *note
SyntaxError: 173, which means the sequences will be invalid if raw
string notation or escaping the backslashes isn't used.

Regular String          Raw string
                        
-----------------------------------------------
                        
‘"ab*"’                 ‘r"ab*"’
                        
                        
‘"\\\\section"’         ‘r"\\section"’
                        
                        
‘"\\w+\\s+\\1"’         ‘r"\w+\s+\1"’
                        


File: python.info,  Node: Performing Matches,  Next: Module-Level Functions<2>,  Prev: The Backslash Plague,  Up: Using Regular Expressions

9.9.3.3 Performing Matches
..........................

Once you have an object representing a compiled regular expression, what
do you do with it?  Pattern objects have several methods and attributes.
Only the most significant ones will be covered here; consult the *note
re: a7. docs for a complete listing.

Method/Attribute       Purpose
                       
---------------------------------------------------------------------------
                       
‘match()’              Determine if the RE matches at the beginning of
                       the string.
                       
                       
‘search()’             Scan through a string, looking for any location
                       where this RE matches.
                       
                       
‘findall()’            Find all substrings where the RE matches, and
                       returns them as a list.
                       
                       
‘finditer()’           Find all substrings where the RE matches, and
                       returns them as an *note iterator: 192.
                       

*note match(): 21dc. and *note search(): 21dd. return ‘None’ if no match
can be found.  If they're successful, a *note match object: f2a.
instance is returned, containing information about the match: where it
starts and ends, the substring it matched, and more.

You can learn about this by interactively experimenting with the *note
re: a7. module.

This HOWTO uses the standard Python interpreter for its examples.
First, run the Python interpreter, import the *note re: a7. module, and
compile a RE:

     >>> import re
     >>> p = re.compile('[a-z]+')
     >>> p
     re.compile('[a-z]+')

Now, you can try matching various strings against the RE ‘[a-z]+’.  An
empty string shouldn't match at all, since ‘+’ means 'one or more
repetitions'.  *note match(): 21dc. should return ‘None’ in this case,
which will cause the interpreter to print no output.  You can explicitly
print the result of ‘match()’ to make this clear.

     >>> p.match("")
     >>> print(p.match(""))
     None

Now, let's try it on a string that it should match, such as ‘tempo’.  In
this case, *note match(): 21dc. will return a *note match object: f2a,
so you should store the result in a variable for later use.

     >>> m = p.match('tempo')
     >>> m
     <re.Match object; span=(0, 5), match='tempo'>

Now you can query the *note match object: f2a. for information about the
matching string.  Match object instances also have several methods and
attributes; the most important ones are:

Method/Attribute       Purpose
                       
------------------------------------------------------------------------
                       
‘group()’              Return the string matched by the RE
                       
                       
‘start()’              Return the starting position of the match
                       
                       
‘end()’                Return the ending position of the match
                       
                       
‘span()’               Return a tuple containing the (start, end)
                       positions of the match
                       

Trying these methods will soon clarify their meaning:

     >>> m.group()
     'tempo'
     >>> m.start(), m.end()
     (0, 5)
     >>> m.span()
     (0, 5)

*note group(): 21f2. returns the substring that was matched by the RE.
*note start(): 21f6. and *note end(): 21f7. return the starting and
ending index of the match.  *note span(): 21f8. returns both start and
end indexes in a single tuple.  Since the *note match(): 21dc. method
only checks if the RE matches at the start of a string, ‘start()’ will
always be zero.  However, the *note search(): 21dd. method of patterns
scans through the string, so the match may not start at zero in that
case.

     >>> print(p.match('::: message'))
     None
     >>> m = p.search('::: message'); print(m)
     <re.Match object; span=(4, 11), match='message'>
     >>> m.group()
     'message'
     >>> m.span()
     (4, 11)

In actual programs, the most common style is to store the *note match
object: f2a. in a variable, and then check if it was ‘None’.  This
usually looks like:

     p = re.compile( ... )
     m = p.match( 'string goes here' )
     if m:
         print('Match found: ', m.group())
     else:
         print('No match')

Two pattern methods return all of the matches for a pattern.  *note
findall(): 21e8. returns a list of matching strings:

     >>> p = re.compile(r'\d+')
     >>> p.findall('12 drummers drumming, 11 pipers piping, 10 lords a-leaping')
     ['12', '11', '10']

The ‘r’ prefix, making the literal a raw string literal, is needed in
this example because escape sequences in a normal "cooked" string
literal that are not recognized by Python, as opposed to regular
expressions, now result in a *note DeprecationWarning: 18b. and will
eventually become a *note SyntaxError: 173.  See *note The Backslash
Plague: 4d9e.

*note findall(): 21e8. has to create the entire list before it can be
returned as the result.  The *note finditer(): 21e9. method returns a
sequence of *note match object: f2a. instances as an *note iterator:
192.:

     >>> iterator = p.finditer('12 drummers drumming, 11 ... 10 ...')
     >>> iterator
     <callable_iterator object at 0x...>
     >>> for match in iterator:
     ...     print(match.span())
     ...
     (0, 2)
     (22, 24)
     (29, 31)


File: python.info,  Node: Module-Level Functions<2>,  Next: Compilation Flags,  Prev: Performing Matches,  Up: Using Regular Expressions

9.9.3.4 Module-Level Functions
..............................

You don't have to create a pattern object and call its methods; the
*note re: a7. module also provides top-level functions called *note
match(): 11c5, *note search(): 11c4, *note findall(): fcd, *note sub():
283, and so forth.  These functions take the same arguments as the
corresponding pattern method with the RE string added as the first
argument, and still return either ‘None’ or a *note match object: f2a.
instance.

     >>> print(re.match(r'From\s+', 'Fromage amk'))
     None
     >>> re.match(r'From\s+', 'From amk Thu May 14 19:12:10 1998')
     <re.Match object; span=(0, 5), match='From '>

Under the hood, these functions simply create a pattern object for you
and call the appropriate method on it.  They also store the compiled
object in a cache, so future calls using the same RE won't need to parse
the pattern again and again.

Should you use these module-level functions, or should you get the
pattern and call its methods yourself?  If you're accessing a regex
within a loop, pre-compiling it will save a few function calls.  Outside
of loops, there's not much difference thanks to the internal cache.


File: python.info,  Node: Compilation Flags,  Prev: Module-Level Functions<2>,  Up: Using Regular Expressions

9.9.3.5 Compilation Flags
.........................

Compilation flags let you modify some aspects of how regular expressions
work.  Flags are available in the *note re: a7. module under two names,
a long name such as *note IGNORECASE: 1623. and a short, one-letter form
such as *note I: 21ce.  (If you're familiar with Perl's pattern
modifiers, the one-letter forms use the same letters; the short form of
*note re.VERBOSE: 21da. is *note re.X: 21d3, for example.)  Multiple
flags can be specified by bitwise OR-ing them; ‘re.I | re.M’ sets both
the *note I: 21ce. and *note M: 21d0. flags, for example.

Here's a table of the available flags, followed by a more detailed
explanation of each one.

Flag                                  含義
                                      
---------------------------------------------------------------------------------------
                                      
*note ASCII: 5d3, *note A: 21cd.      Makes several escapes like ‘\w’, ‘\b’, ‘\s’
                                      and ‘\d’ match only on ASCII characters with
                                      the respective property.
                                      
                                      
*note DOTALL: 21ca, *note S: 21d1.    Make ‘.’ match any character, including
                                      newlines.
                                      
                                      
*note IGNORECASE: 1623,               Do case-insensitive matches.
*note I: 21ce.                        

*note LOCALE: b10, *note L: 21cf.     Do a locale-aware match.
                                      
                                      
*note MULTILINE: 21cb,                Multi-line matching, affecting ‘^’ and ‘$’.
*note M: 21d0.                        

*note VERBOSE: 21da, *note X: 21d3.   Enable verbose REs, which can be organized
(for 'extended')                      more cleanly and understandably.
                                      

 -- 資料: re.I

 -- 資料: re.IGNORECASE

     Perform case-insensitive matching; character class and literal
     strings will match letters by ignoring case.  For example, ‘[A-Z]’
     will match lowercase letters, too.  Full Unicode matching also
     works unless the *note ASCII: 5d3. flag is used to disable
     non-ASCII matches.  When the Unicode patterns ‘[a-z]’ or ‘[A-Z]’
     are used in combination with the *note IGNORECASE: 1623. flag, they
     will match the 52 ASCII letters and 4 additional non-ASCII letters:
     'İ' (U+0130, Latin capital letter I with dot above), 'ı' (U+0131,
     Latin small letter dotless i), 'ſ' (U+017F, Latin small letter long
     s) and 'K' (U+212A, Kelvin sign).  ‘Spam’ will match ‘'Spam'’,
     ‘'spam'’, ‘'spAM'’, or ‘'ſpam'’ (the latter is matched only in
     Unicode mode).  This lowercasing doesn't take the current locale
     into account; it will if you also set the *note LOCALE: b10. flag.

 -- 資料: re.L

 -- 資料: re.LOCALE

     Make ‘\w’, ‘\W’, ‘\b’, ‘\B’ and case-insensitive matching dependent
     on the current locale instead of the Unicode database.

     Locales are a feature of the C library intended to help in writing
     programs that take account of language differences.  For example,
     if you're processing encoded French text, you'd want to be able to
     write ‘\w+’ to match words, but ‘\w’ only matches the character
     class ‘[A-Za-z]’ in bytes patterns; it won't match bytes
     corresponding to ‘é’ or ‘ç’.  If your system is configured properly
     and a French locale is selected, certain C functions will tell the
     program that the byte corresponding to ‘é’ should also be
     considered a letter.  Setting the *note LOCALE: b10. flag when
     compiling a regular expression will cause the resulting compiled
     object to use these C functions for ‘\w’; this is slower, but also
     enables ‘\w+’ to match French words as you'd expect.  The use of
     this flag is discouraged in Python 3 as the locale mechanism is
     very unreliable, it only handles one "culture" at a time, and it
     only works with 8-bit locales.  Unicode matching is already enabled
     by default in Python 3 for Unicode (str) patterns, and it is able
     to handle different locales/languages.

 -- 資料: re.M

 -- 資料: re.MULTILINE

     (‘^’ and ‘$’ haven't been explained yet; they'll be introduced in
     section *note More Metacharacters: 4da2.)

     Usually ‘^’ matches only at the beginning of the string, and ‘$’
     matches only at the end of the string and immediately before the
     newline (if any) at the end of the string.  When this flag is
     specified, ‘^’ matches at the beginning of the string and at the
     beginning of each line within the string, immediately following
     each newline.  Similarly, the ‘$’ metacharacter matches either at
     the end of the string and at the end of each line (immediately
     preceding each newline).

 -- 資料: re.S

 -- 資料: re.DOTALL

     Makes the ‘'.'’ special character match any character at all,
     including a newline; without this flag, ‘'.'’ will match anything
     'except' a newline.

 -- 資料: re.A

 -- 資料: re.ASCII

     Make ‘\w’, ‘\W’, ‘\b’, ‘\B’, ‘\s’ and ‘\S’ perform ASCII-only
     matching instead of full Unicode matching.  This is only meaningful
     for Unicode patterns, and is ignored for byte patterns.

 -- 資料: re.X

 -- 資料: re.VERBOSE

     This flag allows you to write regular expressions that are more
     readable by granting you more flexibility in how you can format
     them.  When this flag has been specified, whitespace within the RE
     string is ignored, except when the whitespace is in a character
     class or preceded by an unescaped backslash; this lets you organize
     and indent the RE more clearly.  This flag also lets you put
     comments within a RE that will be ignored by the engine; comments
     are marked by a ‘'#'’ that's neither in a character class or
     preceded by an unescaped backslash.

     For example, here's a RE that uses *note re.VERBOSE: 21da.; see how
     much easier it is to read?

          charref = re.compile(r"""
           &[#]                # Start of a numeric entity reference
           (
               0[0-7]+         # Octal form
             | [0-9]+          # Decimal form
             | x[0-9a-fA-F]+   # Hexadecimal form
           )
           ;                   # Trailing semicolon
          """, re.VERBOSE)

     Without the verbose setting, the RE would look like this:

          charref = re.compile("&#(0[0-7]+"
                               "|[0-9]+"
                               "|x[0-9a-fA-F]+);")

     In the above example, Python's automatic concatenation of string
     literals has been used to break up the RE into smaller pieces, but
     it's still more difficult to understand than the version using
     *note re.VERBOSE: 21da.


File: python.info,  Node: More Pattern Power,  Next: Modifying Strings,  Prev: Using Regular Expressions,  Up: 如何使用正規表示式

9.9.4 More Pattern Power
------------------------

So far we've only covered a part of the features of regular expressions.
In this section, we'll cover some new metacharacters, and how to use
groups to retrieve portions of the text that was matched.

* Menu:

* More Metacharacters::
* Grouping::
* Non-capturing and Named Groups::
* Lookahead Assertions::


File: python.info,  Node: More Metacharacters,  Next: Grouping,  Up: More Pattern Power

9.9.4.1 More Metacharacters
...........................

There are some metacharacters that we haven't covered yet.  Most of them
will be covered in this section.

Some of the remaining metacharacters to be discussed are 'zero-width
assertions'.  They don't cause the engine to advance through the string;
instead, they consume no characters at all, and simply succeed or fail.
For example, ‘\b’ is an assertion that the current position is located
at a word boundary; the position isn't changed by the ‘\b’ at all.  This
means that zero-width assertions should never be repeated, because if
they match once at a given location, they can obviously be matched an
infinite number of times.

‘|’

     Alternation, or the "or" operator.  If 'A' and 'B' are regular
     expressions, ‘A|B’ will match any string that matches either 'A' or
     'B'. ‘|’ has very low precedence in order to make it work
     reasonably when you're alternating multi-character strings.
     ‘Crow|Servo’ will match either ‘'Crow'’ or ‘'Servo'’, not ‘'Cro'’,
     a ‘'w'’ or an ‘'S'’, and ‘'ervo'’.

     To match a literal ‘'|'’, use ‘\|’, or enclose it inside a
     character class, as in ‘[|]’.

‘^’

     Matches at the beginning of lines.  Unless the *note MULTILINE:
     21cb. flag has been set, this will only match at the beginning of
     the string.  In *note MULTILINE: 21cb. mode, this also matches
     immediately after each newline within the string.

     For example, if you wish to match the word ‘From’ only at the
     beginning of a line, the RE to use is ‘^From’.

          >>> print(re.search('^From', 'From Here to Eternity'))
          <re.Match object; span=(0, 4), match='From'>
          >>> print(re.search('^From', 'Reciting From Memory'))
          None

     To match a literal ‘'^'’, use ‘\^’.

‘$’

     Matches at the end of a line, which is defined as either the end of
     the string, or any location followed by a newline character.

          >>> print(re.search('}$', '{block}'))
          <re.Match object; span=(6, 7), match='}'>
          >>> print(re.search('}$', '{block} '))
          None
          >>> print(re.search('}$', '{block}\n'))
          <re.Match object; span=(6, 7), match='}'>

     To match a literal ‘'$'’, use ‘\$’ or enclose it inside a character
     class, as in ‘[$]’.

‘\A’

     Matches only at the start of the string.  When not in *note
     MULTILINE: 21cb. mode, ‘\A’ and ‘^’ are effectively the same.  In
     *note MULTILINE: 21cb. mode, they're different: ‘\A’ still matches
     only at the beginning of the string, but ‘^’ may match at any
     location inside the string that follows a newline character.

‘\Z’

     Matches only at the end of the string.

‘\b’

     Word boundary.  This is a zero-width assertion that matches only at
     the beginning or end of a word.  A word is defined as a sequence of
     alphanumeric characters, so the end of a word is indicated by
     whitespace or a non-alphanumeric character.

     The following example matches ‘class’ only when it's a complete
     word; it won't match when it's contained inside another word.

          >>> p = re.compile(r'\bclass\b')
          >>> print(p.search('no class at all'))
          <re.Match object; span=(3, 8), match='class'>
          >>> print(p.search('the declassified algorithm'))
          None
          >>> print(p.search('one subclass is'))
          None

     There are two subtleties you should remember when using this
     special sequence.  First, this is the worst collision between
     Python's string literals and regular expression sequences.  In
     Python's string literals, ‘\b’ is the backspace character, ASCII
     value 8.  If you're not using raw strings, then Python will convert
     the ‘\b’ to a backspace, and your RE won't match as you expect it
     to.  The following example looks the same as our previous RE, but
     omits the ‘'r'’ in front of the RE string.

          >>> p = re.compile('\bclass\b')
          >>> print(p.search('no class at all'))
          None
          >>> print(p.search('\b' + 'class' + '\b'))
          <re.Match object; span=(0, 7), match='\x08class\x08'>

     Second, inside a character class, where there's no use for this
     assertion, ‘\b’ represents the backspace character, for
     compatibility with Python's string literals.

‘\B’

     Another zero-width assertion, this is the opposite of ‘\b’, only
     matching when the current position is not at a word boundary.


File: python.info,  Node: Grouping,  Next: Non-capturing and Named Groups,  Prev: More Metacharacters,  Up: More Pattern Power

9.9.4.2 Grouping
................

Frequently you need to obtain more information than just whether the RE
matched or not.  Regular expressions are often used to dissect strings
by writing a RE divided into several subgroups which match different
components of interest.  For example, an RFC-822 header line is divided
into a header name and a value, separated by a ‘':'’, like this:

     From: author@example.com
     User-Agent: Thunderbird 1.5.0.9 (X11/20061227)
     MIME-Version: 1.0
     To: editor@example.com

This can be handled by writing a regular expression which matches an
entire header line, and has one group which matches the header name, and
another group which matches the header's value.

Groups are marked by the ‘'('’, ‘')'’ metacharacters.  ‘'('’ and ‘')'’
have much the same meaning as they do in mathematical expressions; they
group together the expressions contained inside them, and you can repeat
the contents of a group with a quantifier, such as ‘*’, ‘+’, ‘?’, or
‘{m,n}’.  For example, ‘(ab)*’ will match zero or more repetitions of
‘ab’.

     >>> p = re.compile('(ab)*')
     >>> print(p.match('ababababab').span())
     (0, 10)

Groups indicated with ‘'('’, ‘')'’ also capture the starting and ending
index of the text that they match; this can be retrieved by passing an
argument to *note group(): 21f2, *note start(): 21f6, *note end(): 21f7,
and *note span(): 21f8.  Groups are numbered starting with 0.  Group 0
is always present; it's the whole RE, so *note match object: f2a.
methods all have group 0 as their default argument.  Later we'll see how
to express groups that don't capture the span of text that they match.

     >>> p = re.compile('(a)b')
     >>> m = p.match('ab')
     >>> m.group()
     'ab'
     >>> m.group(0)
     'ab'

Subgroups are numbered from left to right, from 1 upward.  Groups can be
nested; to determine the number, just count the opening parenthesis
characters, going from left to right.

     >>> p = re.compile('(a(b)c)d')
     >>> m = p.match('abcd')
     >>> m.group(0)
     'abcd'
     >>> m.group(1)
     'abc'
     >>> m.group(2)
     'b'

*note group(): 21f2. can be passed multiple group numbers at a time, in
which case it will return a tuple containing the corresponding values
for those groups.

     >>> m.group(2,1,2)
     ('b', 'abc', 'b')

The *note groups(): 21f4. method returns a tuple containing the strings
for all the subgroups, from 1 up to however many there are.

     >>> m.groups()
     ('abc', 'b')

Backreferences in a pattern allow you to specify that the contents of an
earlier capturing group must also be found at the current location in
the string.  For example, ‘\1’ will succeed if the exact contents of
group 1 can be found at the current position, and fails otherwise.
Remember that Python's string literals also use a backslash followed by
numbers to allow including arbitrary characters in a string, so be sure
to use a raw string when incorporating backreferences in a RE.

For example, the following RE detects doubled words in a string.

     >>> p = re.compile(r'\b(\w+)\s+\1\b')
     >>> p.search('Paris in the the spring').group()
     'the the'

Backreferences like this aren't often useful for just searching through
a string -- there are few text formats which repeat data in this way --
but you'll soon find out that they're 'very' useful when performing
string substitutions.


File: python.info,  Node: Non-capturing and Named Groups,  Next: Lookahead Assertions,  Prev: Grouping,  Up: More Pattern Power

9.9.4.3 Non-capturing and Named Groups
......................................

Elaborate REs may use many groups, both to capture substrings of
interest, and to group and structure the RE itself.  In complex REs, it
becomes difficult to keep track of the group numbers.  There are two
features which help with this problem.  Both of them use a common syntax
for regular expression extensions, so we'll look at that first.

Perl 5 is well known for its powerful additions to standard regular
expressions.  For these new features the Perl developers couldn't choose
new single-keystroke metacharacters or new special sequences beginning
with ‘\’ without making Perl's regular expressions confusingly different
from standard REs.  If they chose ‘&’ as a new metacharacter, for
example, old expressions would be assuming that ‘&’ was a regular
character and wouldn't have escaped it by writing ‘\&’ or ‘[&]’.

The solution chosen by the Perl developers was to use ‘(?...)’ as the
extension syntax.  ‘?’ immediately after a parenthesis was a syntax
error because the ‘?’ would have nothing to repeat, so this didn't
introduce any compatibility problems.  The characters immediately after
the ‘?’ indicate what extension is being used, so ‘(?=foo)’ is one thing
(a positive lookahead assertion) and ‘(?:foo)’ is something else (a
non-capturing group containing the subexpression ‘foo’).

Python supports several of Perl's extensions and adds an extension
syntax to Perl's extension syntax.  If the first character after the
question mark is a ‘P’, you know that it's an extension that's specific
to Python.

Now that we've looked at the general extension syntax, we can return to
the features that simplify working with groups in complex REs.

Sometimes you'll want to use a group to denote a part of a regular
expression, but aren't interested in retrieving the group's contents.
You can make this fact explicit by using a non-capturing group:
‘(?:...)’, where you can replace the ‘...’ with any other regular
expression.

     >>> m = re.match("([abc])+", "abc")
     >>> m.groups()
     ('c',)
     >>> m = re.match("(?:[abc])+", "abc")
     >>> m.groups()
     ()

Except for the fact that you can't retrieve the contents of what the
group matched, a non-capturing group behaves exactly the same as a
capturing group; you can put anything inside it, repeat it with a
repetition metacharacter such as ‘*’, and nest it within other groups
(capturing or non-capturing).  ‘(?:...)’ is particularly useful when
modifying an existing pattern, since you can add new groups without
changing how all the other groups are numbered.  It should be mentioned
that there's no performance difference in searching between capturing
and non-capturing groups; neither form is any faster than the other.

A more significant feature is named groups: instead of referring to them
by numbers, groups can be referenced by a name.

The syntax for a named group is one of the Python-specific extensions:
‘(?P<name>...)’.  'name' is, obviously, the name of the group.  Named
groups behave exactly like capturing groups, and additionally associate
a name with a group.  The *note match object: f2a. methods that deal
with capturing groups all accept either integers that refer to the group
by number or strings that contain the desired group's name.  Named
groups are still given numbers, so you can retrieve information about a
group in two ways:

     >>> p = re.compile(r'(?P<word>\b\w+\b)')
     >>> m = p.search( '(((( Lots of punctuation )))' )
     >>> m.group('word')
     'Lots'
     >>> m.group(1)
     'Lots'

Additionally, you can retrieve named groups as a dictionary with *note
groupdict(): 21f5.:

     >>> m = re.match(r'(?P<first>\w+) (?P<last>\w+)', 'Jane Doe')
     >>> m.groupdict()
     {'first': 'Jane', 'last': 'Doe'}

Named groups are handy because they let you use easily remembered names,
instead of having to remember numbers.  Here's an example RE from the
*note imaplib: 6a. module:

     InternalDate = re.compile(r'INTERNALDATE "'
             r'(?P<day>[ 123][0-9])-(?P<mon>[A-Z][a-z][a-z])-'
             r'(?P<year>[0-9][0-9][0-9][0-9])'
             r' (?P<hour>[0-9][0-9]):(?P<min>[0-9][0-9]):(?P<sec>[0-9][0-9])'
             r' (?P<zonen>[-+])(?P<zoneh>[0-9][0-9])(?P<zonem>[0-9][0-9])'
             r'"')

It's obviously much easier to retrieve ‘m.group('zonem')’, instead of
having to remember to retrieve group 9.

The syntax for backreferences in an expression such as ‘(...)\1’ refers
to the number of the group.  There's naturally a variant that uses the
group name instead of the number.  This is another Python extension:
‘(?P=name)’ indicates that the contents of the group called 'name'
should again be matched at the current point.  The regular expression
for finding doubled words, ‘\b(\w+)\s+\1\b’ can also be written as
‘\b(?P<word>\w+)\s+(?P=word)\b’:

     >>> p = re.compile(r'\b(?P<word>\w+)\s+(?P=word)\b')
     >>> p.search('Paris in the the spring').group()
     'the the'


File: python.info,  Node: Lookahead Assertions,  Prev: Non-capturing and Named Groups,  Up: More Pattern Power

9.9.4.4 Lookahead Assertions
............................

Another zero-width assertion is the lookahead assertion.  Lookahead
assertions are available in both positive and negative form, and look
like this:

‘(?=...)’

     Positive lookahead assertion.  This succeeds if the contained
     regular expression, represented here by ‘...’, successfully matches
     at the current location, and fails otherwise.  But, once the
     contained expression has been tried, the matching engine doesn't
     advance at all; the rest of the pattern is tried right where the
     assertion started.

‘(?!...)’

     Negative lookahead assertion.  This is the opposite of the positive
     assertion; it succeeds if the contained expression 'doesn't' match
     at the current position in the string.

To make this concrete, let's look at a case where a lookahead is useful.
Consider a simple pattern to match a filename and split it apart into a
base name and an extension, separated by a ‘.’.  For example, in
‘news.rc’, ‘news’ is the base name, and ‘rc’ is the filename's
extension.

The pattern to match this is quite simple:

‘.*[.].*$’

Notice that the ‘.’ needs to be treated specially because it's a
metacharacter, so it's inside a character class to only match that
specific character.  Also notice the trailing ‘$’; this is added to
ensure that all the rest of the string must be included in the
extension.  This regular expression matches ‘foo.bar’ and ‘autoexec.bat’
and ‘sendmail.cf’ and ‘printers.conf’.

Now, consider complicating the problem a bit; what if you want to match
filenames where the extension is not ‘bat’?  Some incorrect attempts:

‘.*[.][^b].*$’ The first attempt above tries to exclude ‘bat’ by
requiring that the first character of the extension is not a ‘b’.  This
is wrong, because the pattern also doesn't match ‘foo.bar’.

‘.*[.]([^b]..|.[^a].|..[^t])$’

The expression gets messier when you try to patch up the first solution
by requiring one of the following cases to match: the first character of
the extension isn't ‘b’; the second character isn't ‘a’; or the third
character isn't ‘t’.  This accepts ‘foo.bar’ and rejects ‘autoexec.bat’,
but it requires a three-letter extension and won't accept a filename
with a two-letter extension such as ‘sendmail.cf’.  We'll complicate the
pattern again in an effort to fix it.

‘.*[.]([^b].?.?|.[^a]?.?|..?[^t]?)$’

In the third attempt, the second and third letters are all made optional
in order to allow matching extensions shorter than three characters,
such as ‘sendmail.cf’.

The pattern's getting really complicated now, which makes it hard to
read and understand.  Worse, if the problem changes and you want to
exclude both ‘bat’ and ‘exe’ as extensions, the pattern would get even
more complicated and confusing.

A negative lookahead cuts through all this confusion:

‘.*[.](?!bat$)[^.]*$’ The negative lookahead means: if the expression
‘bat’ doesn't match at this point, try the rest of the pattern; if
‘bat$’ does match, the whole pattern will fail.  The trailing ‘$’ is
required to ensure that something like ‘sample.batch’, where the
extension only starts with ‘bat’, will be allowed.  The ‘[^.]*’ makes
sure that the pattern works when there are multiple dots in the
filename.

Excluding another filename extension is now easy; simply add it as an
alternative inside the assertion.  The following pattern excludes
filenames that end in either ‘bat’ or ‘exe’:

‘.*[.](?!bat$|exe$)[^.]*$’


File: python.info,  Node: Modifying Strings,  Next: Common Problems,  Prev: More Pattern Power,  Up: 如何使用正規表示式

9.9.5 Modifying Strings
-----------------------

Up to this point, we've simply performed searches against a static
string.  Regular expressions are also commonly used to modify strings in
various ways, using the following pattern methods:

Method/Attribute       Purpose
                       
---------------------------------------------------------------------------
                       
‘split()’              Split the string into a list, splitting it
                       wherever the RE matches
                       
                       
‘sub()’                Find all substrings where the RE matches, and
                       replace them with a different string
                       
                       
‘subn()’               Does the same thing as ‘sub()’, but returns the
                       new string and the number of replacements
                       

* Menu:

* Splitting Strings::
* Search and Replace: Search and Replace<2>.


File: python.info,  Node: Splitting Strings,  Next: Search and Replace<2>,  Up: Modifying Strings

9.9.5.1 Splitting Strings
.........................

The *note split(): 21e7. method of a pattern splits a string apart
wherever the RE matches, returning a list of the pieces.  It's similar
to the *note split(): e4c. method of strings but provides much more
generality in the delimiters that you can split by; string ‘split()’
only supports splitting by whitespace or by a fixed string.  As you'd
expect, there's a module-level *note re.split(): 282. function, too.

 -- 方法: .split (string[, maxsplit=0])

     Split 'string' by the matches of the regular expression.  If
     capturing parentheses are used in the RE, then their contents will
     also be returned as part of the resulting list.  If 'maxsplit' is
     nonzero, at most 'maxsplit' splits are performed.

You can limit the number of splits made, by passing a value for
'maxsplit'.  When 'maxsplit' is nonzero, at most 'maxsplit' splits will
be made, and the remainder of the string is returned as the final
element of the list.  In the following example, the delimiter is any
sequence of non-alphanumeric characters.

     >>> p = re.compile(r'\W+')
     >>> p.split('This is a test, short and sweet, of split().')
     ['This', 'is', 'a', 'test', 'short', 'and', 'sweet', 'of', 'split', '']
     >>> p.split('This is a test, short and sweet, of split().', 3)
     ['This', 'is', 'a', 'test, short and sweet, of split().']

Sometimes you're not only interested in what the text between delimiters
is, but also need to know what the delimiter was.  If capturing
parentheses are used in the RE, then their values are also returned as
part of the list.  Compare the following calls:

     >>> p = re.compile(r'\W+')
     >>> p2 = re.compile(r'(\W+)')
     >>> p.split('This... is a test.')
     ['This', 'is', 'a', 'test', '']
     >>> p2.split('This... is a test.')
     ['This', '... ', 'is', ' ', 'a', ' ', 'test', '.', '']

The module-level function *note re.split(): 282. adds the RE to be used
as the first argument, but is otherwise the same.

     >>> re.split(r'[\W]+', 'Words, words, words.')
     ['Words', 'words', 'words', '']
     >>> re.split(r'([\W]+)', 'Words, words, words.')
     ['Words', ', ', 'words', ', ', 'words', '.', '']
     >>> re.split(r'[\W]+', 'Words, words, words.', 1)
     ['Words', 'words, words.']


File: python.info,  Node: Search and Replace<2>,  Prev: Splitting Strings,  Up: Modifying Strings

9.9.5.2 Search and Replace
..........................

Another common task is to find all the matches for a pattern, and
replace them with a different string.  The *note sub(): 21ea. method
takes a replacement value, which can be either a string or a function,
and the string to be processed.

 -- 方法: .sub (replacement, string[, count=0])

     Returns the string obtained by replacing the leftmost
     non-overlapping occurrences of the RE in 'string' by the
     replacement 'replacement'.  If the pattern isn't found, 'string' is
     returned unchanged.

     The optional argument 'count' is the maximum number of pattern
     occurrences to be replaced; 'count' must be a non-negative integer.
     The default value of 0 means to replace all occurrences.

Here's a simple example of using the *note sub(): 21ea. method.  It
replaces colour names with the word ‘colour’:

     >>> p = re.compile('(blue|white|red)')
     >>> p.sub('colour', 'blue socks and red shoes')
     'colour socks and colour shoes'
     >>> p.sub('colour', 'blue socks and red shoes', count=1)
     'colour socks and red shoes'

The *note subn(): 21eb. method does the same work, but returns a 2-tuple
containing the new string value and the number of replacements that were
performed:

     >>> p = re.compile('(blue|white|red)')
     >>> p.subn('colour', 'blue socks and red shoes')
     ('colour socks and colour shoes', 2)
     >>> p.subn('colour', 'no colours at all')
     ('no colours at all', 0)

Empty matches are replaced only when they're not adjacent to a previous
empty match.

     >>> p = re.compile('x*')
     >>> p.sub('-', 'abxd')
     '-a-b--d-'

If 'replacement' is a string, any backslash escapes in it are processed.
That is, ‘\n’ is converted to a single newline character, ‘\r’ is
converted to a carriage return, and so forth.  Unknown escapes such as
‘\&’ are left alone.  Backreferences, such as ‘\6’, are replaced with
the substring matched by the corresponding group in the RE. This lets
you incorporate portions of the original text in the resulting
replacement string.

This example matches the word ‘section’ followed by a string enclosed in
‘{’, ‘}’, and changes ‘section’ to ‘subsection’:

     >>> p = re.compile('section{ ( [^}]* ) }', re.VERBOSE)
     >>> p.sub(r'subsection{\1}','section{First} section{second}')
     'subsection{First} subsection{second}'

There's also a syntax for referring to named groups as defined by the
‘(?P<name>...)’ syntax.  ‘\g<name>’ will use the substring matched by
the group named ‘name’, and ‘\g<number>’ uses the corresponding group
number.  ‘\g<2>’ is therefore equivalent to ‘\2’, but isn't ambiguous in
a replacement string such as ‘\g<2>0’.  (‘\20’ would be interpreted as a
reference to group 20, not a reference to group 2 followed by the
literal character ‘'0'’.)  The following substitutions are all
equivalent, but use all three variations of the replacement string.

     >>> p = re.compile('section{ (?P<name> [^}]* ) }', re.VERBOSE)
     >>> p.sub(r'subsection{\1}','section{First}')
     'subsection{First}'
     >>> p.sub(r'subsection{\g<1>}','section{First}')
     'subsection{First}'
     >>> p.sub(r'subsection{\g<name>}','section{First}')
     'subsection{First}'

'replacement' can also be a function, which gives you even more control.
If 'replacement' is a function, the function is called for every
non-overlapping occurrence of 'pattern'.  On each call, the function is
passed a *note match object: f2a. argument for the match and can use
this information to compute the desired replacement string and return
it.

In the following example, the replacement function translates decimals
into hexadecimal:

     >>> def hexrepl(match):
     ...     "Return the hex string for a decimal number"
     ...     value = int(match.group())
     ...     return hex(value)
     ...
     >>> p = re.compile(r'\d+')
     >>> p.sub(hexrepl, 'Call 65490 for printing, 49152 for user code.')
     'Call 0xffd2 for printing, 0xc000 for user code.'

When using the module-level *note re.sub(): 283. function, the pattern
is passed as the first argument.  The pattern may be provided as an
object or as a string; if you need to specify regular expression flags,
you must either use a pattern object as the first parameter, or use
embedded modifiers in the pattern string, e.g.  ‘sub("(?i)b+", "x",
"bbbb BBBB")’ returns ‘'x x'’.


File: python.info,  Node: Common Problems,  Next: Feedback,  Prev: Modifying Strings,  Up: 如何使用正規表示式

9.9.6 Common Problems
---------------------

Regular expressions are a powerful tool for some applications, but in
some ways their behaviour isn't intuitive and at times they don't behave
the way you may expect them to.  This section will point out some of the
most common pitfalls.

* Menu:

* Use String Methods::
* match() versus search(): match versus search.
* Greedy versus Non-Greedy::
* Using re.VERBOSE: Using re VERBOSE.


File: python.info,  Node: Use String Methods,  Next: match versus search,  Up: Common Problems

9.9.6.1 Use String Methods
..........................

Sometimes using the *note re: a7. module is a mistake.  If you're
matching a fixed string, or a single character class, and you're not
using any *note re: a7. features such as the *note IGNORECASE: 1623.
flag, then the full power of regular expressions may not be required.
Strings have several methods for performing operations with fixed
strings and they're usually much faster, because the implementation is a
single small C loop that's been optimized for the purpose, instead of
the large, more generalized regular expression engine.

One example might be replacing a single fixed string with another one;
for example, you might replace ‘word’ with ‘deed’.  *note re.sub(): 283.
seems like the function to use for this, but consider the *note
replace(): 17e. method.  Note that ‘replace()’ will also replace ‘word’
inside words, turning ‘swordfish’ into ‘sdeedfish’, but the naive RE
‘word’ would have done that, too.  (To avoid performing the substitution
on parts of words, the pattern would have to be ‘\bword\b’, in order to
require that ‘word’ have a word boundary on either side.  This takes the
job beyond ‘replace()’'s abilities.)

Another common task is deleting every occurrence of a single character
from a string or replacing it with another single character.  You might
do this with something like ‘re.sub('\n', ' ', S)’, but *note
translate(): 20a5. is capable of doing both tasks and will be faster
than any regular expression operation can be.

In short, before turning to the *note re: a7. module, consider whether
your problem can be solved with a faster and simpler string method.


File: python.info,  Node: match versus search,  Next: Greedy versus Non-Greedy,  Prev: Use String Methods,  Up: Common Problems

9.9.6.2 match() versus search()
...............................

The *note match(): 11c5. function only checks if the RE matches at the
beginning of the string while *note search(): 11c4. will scan forward
through the string for a match.  It's important to keep this distinction
in mind.  Remember, ‘match()’ will only report a successful match which
will start at 0; if the match wouldn't start at zero, ‘match()’ will
'not' report it.

     >>> print(re.match('super', 'superstition').span())
     (0, 5)
     >>> print(re.match('super', 'insuperable'))
     None

On the other hand, *note search(): 11c4. will scan forward through the
string, reporting the first match it finds.

     >>> print(re.search('super', 'superstition').span())
     (0, 5)
     >>> print(re.search('super', 'insuperable').span())
     (2, 7)

Sometimes you'll be tempted to keep using *note re.match(): 11c5, and
just add ‘.*’ to the front of your RE. Resist this temptation and use
*note re.search(): 11c4. instead.  The regular expression compiler does
some analysis of REs in order to speed up the process of looking for a
match.  One such analysis figures out what the first character of a
match must be; for example, a pattern starting with ‘Crow’ must match
starting with a ‘'C'’.  The analysis lets the engine quickly scan
through the string looking for the starting character, only trying the
full match if a ‘'C'’ is found.

Adding ‘.*’ defeats this optimization, requiring scanning to the end of
the string and then backtracking to find a match for the rest of the RE.
Use *note re.search(): 11c4. instead.


File: python.info,  Node: Greedy versus Non-Greedy,  Next: Using re VERBOSE,  Prev: match versus search,  Up: Common Problems

9.9.6.3 Greedy versus Non-Greedy
................................

When repeating a regular expression, as in ‘a*’, the resulting action is
to consume as much of the pattern as possible.  This fact often bites
you when you're trying to match a pair of balanced delimiters, such as
the angle brackets surrounding an HTML tag.  The naive pattern for
matching a single HTML tag doesn't work because of the greedy nature of
‘.*’.

     >>> s = '<html><head><title>Title</title>'
     >>> len(s)
     32
     >>> print(re.match('<.*>', s).span())
     (0, 32)
     >>> print(re.match('<.*>', s).group())
     <html><head><title>Title</title>

The RE matches the ‘'<'’ in ‘'<html>'’, and the ‘.*’ consumes the rest
of the string.  There's still more left in the RE, though, and the ‘>’
can't match at the end of the string, so the regular expression engine
has to backtrack character by character until it finds a match for the
‘>’.  The final match extends from the ‘'<'’ in ‘'<html>'’ to the ‘'>'’
in ‘'</title>'’, which isn't what you want.

In this case, the solution is to use the non-greedy quantifiers ‘*?’,
‘+?’, ‘??’, or ‘{m,n}?’, which match as 'little' text as possible.  In
the above example, the ‘'>'’ is tried immediately after the first ‘'<'’
matches, and when it fails, the engine advances a character at a time,
retrying the ‘'>'’ at every step.  This produces just the right result:

     >>> print(re.match('<.*?>', s).group())
     <html>

(Note that parsing HTML or XML with regular expressions is painful.
Quick-and-dirty patterns will handle common cases, but HTML and XML have
special cases that will break the obvious regular expression; by the
time you've written a regular expression that handles all of the
possible cases, the patterns will be 'very' complicated.  Use an HTML or
XML parser module for such tasks.)


File: python.info,  Node: Using re VERBOSE,  Prev: Greedy versus Non-Greedy,  Up: Common Problems

9.9.6.4 Using re.VERBOSE
........................

By now you've probably noticed that regular expressions are a very
compact notation, but they're not terribly readable.  REs of moderate
complexity can become lengthy collections of backslashes, parentheses,
and metacharacters, making them difficult to read and understand.

For such REs, specifying the *note re.VERBOSE: 21da. flag when compiling
the regular expression can be helpful, because it allows you to format
the regular expression more clearly.

The ‘re.VERBOSE’ flag has several effects.  Whitespace in the regular
expression that 'isn't' inside a character class is ignored.  This means
that an expression such as ‘dog | cat’ is equivalent to the less
readable ‘dog|cat’, but ‘[a b]’ will still match the characters ‘'a'’,
‘'b'’, or a space.  In addition, you can also put comments inside a RE;
comments extend from a ‘#’ character to the next newline.  When used
with triple-quoted strings, this enables REs to be formatted more
neatly:

     pat = re.compile(r"""
      \s*                 # Skip leading whitespace
      (?P<header>[^:]+)   # Header name
      \s* :               # Whitespace, and a colon
      (?P<value>.*?)      # The header's value -- *? used to
                          # lose the following trailing whitespace
      \s*$                # Trailing whitespace to end-of-line
     """, re.VERBOSE)

This is far more readable than:

     pat = re.compile(r"\s*(?P<header>[^:]+)\s*:(?P<value>.*?)\s*$")


File: python.info,  Node: Feedback,  Prev: Common Problems,  Up: 如何使用正規表示式

9.9.7 Feedback
--------------

Regular expressions are a complicated topic.  Did this document help you
understand them?  Were there parts that were unclear, or Problems you
encountered that weren't covered here?  If so, please send suggestions
for improvements to the author.

The most complete book on regular expressions is almost certainly
Jeffrey Friedl's Mastering Regular Expressions, published by O'Reilly.
Unfortunately, it exclusively concentrates on Perl and Java's flavours
of regular expressions, and doesn't contain any Python material at all,
so it won't be useful as a reference for programming in Python.  (The
first edition covered Python's now-removed ‘regex’ module, which won't
help you much.)  Consider checking it out from your library.


File: python.info,  Node: Socket 程式設計指南,  Next: 排序技法,  Prev: 如何使用正規表示式,  Up: Python 如何達成任務

9.10 Socket 程式設計指南
========================


作者: Gordon McMillan

摘要
....

Sockets 在各處都被廣泛使用，但卻是一項被誤解最嚴重的技術之一。這是一篇對
sockets 的概論介紹。這並不是一個完整的教學指南 - 你還需要做許多準備才能
讓 sockets 正常運作。這篇文章也沒有包含細節（其中有非常多的細節），但我
希望這篇文章能夠讓你有足夠的背景知識，以便開始正確的使用 sockets 程式設
計。

* Menu:

* Sockets::
* 建立一個 Socket::
* 使用一個 Socket::
* 結束連線::
* 非阻塞的 Sockets::


File: python.info,  Node: Sockets,  Next: 建立一個 Socket,  Up: Socket 程式設計指南

9.10.1 Sockets
--------------

我只會討論關於 INET（例如：IPv4）的 sockets，但它們涵蓋了幾乎 99% 的
sockets 使用場景。而我也將僅討論關於 STREAM（比如：TCP）類型的 sockets -
除非你真的知道你在做什麼（在這種情況下，這份指南可能不適合你），使用
STREAM 類型的 socket 會獲得比其他 sockets 類型更好的表現和性能。我將會嘗
試解釋 socket 是什麼，以及如何使用阻塞 (blocking) 和非阻塞
(non-blocking) sockets 的一些建議。但首先我會先談論阻塞 sockets。在處理
非阻塞 sockets 之前，你需要了解它們的工作原理。

要理解這些東西的困難點之一在於 "scoket" 可以代表多種具有些微差異的東西，
這主要取決於上下文。所以首先，讓我們先區分「用戶端 (client)」socket 和「
伺服器端 (server)」socket 的差別，「用戶端」socket 表示通訊的一端，「伺
服器端」socket 更像是一個電話總機接線員。用戶端應用程式（例如：你的瀏覽
器）只能使用「用戶端」socket; 它所連接的網路伺服器則同時使用「伺服器端」
socket 和 「用戶端」socket 來進行通訊。

* Menu:

* 歷史::


File: python.info,  Node: 歷史,  Up: Sockets

9.10.1.1 歷史
.............

在各種形式的 IPC (Inter Process Communication) 中，sockets 是最受歡迎的
。在任何特定的平台上，可能會存在其他更快速的 IPC 形式，但對於跨平台通訊
來說，sockets 是唯一的選擇。

Sockets 作為 Unix 的 BSD 分支的一部分在 Berkeley 被發明出來。它們隨著網
際網路的普及而迅速蔓延開來。這是有很好的理由 — sockets 和 INET 的結合讓
世界各地任何的機器之間的通訊變得非常簡單（至少與其它方案相比是如此）。


File: python.info,  Node: 建立一個 Socket,  Next: 使用一個 Socket,  Prev: Sockets,  Up: Socket 程式設計指南

9.10.2 建立一個 Socket
----------------------

大致上來說，當你點擊了帶你來到這個頁面的連結時，你的瀏覽器做了以下的操作
：

     # create an INET, STREAMing socket
     s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
     # now connect to the web server on port 80 - the normal http port
     s.connect(("www.python.org", 80))

當 ‘connect’ 完成時，這個 socket ‘s’ 可以用來發送請求來取得頁面的文本。
同一個 socket 也會讀取回傳值，然後再被銷毀。是的，會被銷毀。用戶端
socket 通常只用來做一次交換（或是一小組連續交換）。

網路伺服器 (web server) 的運作就稍微複雜一點。首先，網路伺服器會建立一個
「伺服器端 socket」：

     # create an INET, STREAMing socket
     serversocket = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
     # bind the socket to a public host, and a well-known port
     serversocket.bind((socket.gethostname(), 80))
     # become a server socket
     serversocket.listen(5)

有幾件事需要注意：我們使用了 ‘socket.gethostname()’，這樣 socket 才能對
外部網路可見。如果我們使用了 ‘s.bind(('localhost', 80))’ 或
‘s.bind(('127.0.0.1', 80))’，我們會得到一個「伺服器端」socket，但是只能
在同一台機器內可見。‘s.bind(('', 80))’ 指定 socket 可以透過機器的任何地
址存取。

第二個要注意的是：數字小的連接埠 (port) 通常保留給「廣為人知的」服務（
HTTP、SNMP等）。如果你只是想執行程式，可以使用一個數字較大的連接埠（4 位
數字）。

最後，‘listen’ 引數告訴 socket 函式庫 (library)，我們希望在佇列 (queue)
中累積達 5 個（正常的最大值）連線請求後再拒絕外部連線。如果其餘的程式碼
編寫正確，這應該足夠了。

現在我們有一個監聽 80 連接埠的「伺服器端」socket 了，我們可以進入網路伺
服器的主迴圈了：

     while True:
         # accept connections from outside
         (clientsocket, address) = serversocket.accept()
         # now do something with the clientsocket
         # in this case, we'll pretend this is a threaded server
         ct = client_thread(clientsocket)
         ct.run()

事實上，有三種方法可以讓這個迴圈運作 - 分配一個執行緒 (thread) 來處理
‘clientsocket’ 、建立一個新行程 (process) 來處理 ‘clientsocket’，或者將
這個程式重新改寫成使用非阻塞 socket，並使用 ‘select’ 在我們的「伺服器端
」socket 和任何有效的 ‘clientsocket’ 之間進行多工處理。稍後將會更詳細的
介紹。現在最重要的是理解：這就是「伺服器端」socket 做的'所有' 事情。它不
會發送任何資料、也不接收任何資料，它只會建立「伺服器端」socket。每個
‘clientsocket’ 都是為了回應某些'其他' ‘connect()’ 到我們綁定的主機上的「
用戶端」socket。一但 ‘clientsocket’ 建立完成，就會繼續監聽更多的連線請求
。兩個「用戶端」可以隨意的通訊 - 它們使用的是一些動態分配的連接埠，會在
通訊結束的時候被回收並重新利用。

* Menu:

* IPC::


File: python.info,  Node: IPC,  Up: 建立一個 Socket

9.10.2.1 IPC
............

如果你需要在一台機器上的兩個行程間進行快速的行程間通訊 (IPC)，你應該考慮
使用管道 (pipes) 或共享記憶體 (shared memory)。如果你確定要使用 AF_INET
sockets，請將「伺服器端」socket 綁定到 ‘'localhost'’。在大多數平台上，這
樣將會繞過幾個網路程式碼層，並且速度會更快一些。

也參考
......

*note multiprocessing: 86. 將跨平台行程間通訊整合到更高層的 API 中。


File: python.info,  Node: 使用一個 Socket,  Next: 結束連線,  Prev: 建立一個 Socket,  Up: Socket 程式設計指南

9.10.3 使用一個 Socket
----------------------

首先需要注意，網頁瀏覽器的「用戶端」socket 和網路伺服器的「用戶端」
socket 是非常類似的。也就是說，這是一個「點對點 (peer to peer)」的通訊方
式，或者也可以說'作為設計者，你必須決定通訊的規則'。通常情況下，
‘connect’ 的 socket 會通過發送一個請求或者信號來開始一次通訊。但這屬於設
計決策，而不是 socket 的規則。

現在有兩組可供通訊使用的動詞。你可以使用 ‘send’ 和 ‘recv’，或者可以將用
戶端 socket 轉換成類似檔案的形式，並使用 ‘read’ 和 ‘write’。後者是 Java
中呈現 socket 的方式。我不打算在這裡討論它，只是提醒你需要在 socket 上使
用 ‘flush’。這些是緩衝的「檔案」，一個常見的錯誤是使用 ‘write’ 寫入某些
內容，然後直接 ‘read’ 回覆。如果不使用 ‘flush’，你可能會一直等待這個回覆
，因為請求可能還在你的輸出緩衝中。

現在我們來到 sockets 的主要障礙 - ‘send’ 和 ‘recv’ 操作的是網路緩衝區。
他們不一定會處理你提供給它們的所有位元組（或者是你期望它處理的位元組），
因為它們主要的重點是處理網路緩衝區。一般來說，它們會在關聯的網路衝區已滿
(‘send’) 或已清空 (‘recv’) 時回傳，然後告訴你它們處理了多少位元組。'你'
的責任是一直呼叫它們直到你所有的訊息處理完成。

當 ‘recv’ 回傳「零位元組 (0 bytes)」時，就表示另一端已經關閉（或著正在關
閉）連線。你再也不能從這個連線上取得任何資料了。你可能還是可以成功發送資
料；我稍後會對此進行更詳細的解釋。

像 HTTP 這樣的協議只使用一個 socket 進行一次傳輸，用戶端發送一個請求，然
後讀取一個回覆。就這樣，然後這個 socket 就會被銷毀。這表示者用戶端可以通
過接收「零位元組」來檢測回覆的結束。

但是如果你打算在之後的傳輸中重新利用 socket 的話，你需要明白'socket 中是
不存在' EOT （傳輸結束）。重申一次：如果一個 socket 的 ‘send’ 或 ‘recv’
處理了「零位元組」後回傳，表示連線已經斷開。如果連線'沒有' 斷開，你可能
會永遠處於等待 ‘recv’ 的狀態，因為（就目前來說）socket '不會' 告訴你沒有
更多資料可以讀取了。現在，如果你稍微思考一下，你就會意識到 socket 的一個
基本事實：'訊息要麼是一個固定的長度（不好的做法），要麼是可以被分隔的（
普通的做法），要麼是指定其長度（更好地做法），要麼通過關閉連線來結束。
'完全由你來決定要使用哪種方式（但有些方法比其他方法來的更好）。

假設你不想結束連線，最簡單的方式就是使用固定長度的訊息：

     class MySocket:
         """demonstration class only
           - coded for clarity, not efficiency
         """

         def __init__(self, sock=None):
             if sock is None:
                 self.sock = socket.socket(
                                 socket.AF_INET, socket.SOCK_STREAM)
             else:
                 self.sock = sock

         def connect(self, host, port):
             self.sock.connect((host, port))

         def mysend(self, msg):
             totalsent = 0
             while totalsent < MSGLEN:
                 sent = self.sock.send(msg[totalsent:])
                 if sent == 0:
                     raise RuntimeError("socket connection broken")
                 totalsent = totalsent + sent

         def myreceive(self):
             chunks = []
             bytes_recd = 0
             while bytes_recd < MSGLEN:
                 chunk = self.sock.recv(min(MSGLEN - bytes_recd, 2048))
                 if chunk == b'':
                     raise RuntimeError("socket connection broken")
                 chunks.append(chunk)
                 bytes_recd = bytes_recd + len(chunk)
             return b''.join(chunks)

發送部分的程式碼幾乎可用於任何訊息的傳送方式 - 在 Python 中你發送一個字
串，可以用 ‘len()’ 來確認他的長度（即使字串包含了 ‘\0’ 字元）。在這裡，
主要是接收的程式碼變得更複雜一些。（在 C 語言中，情況沒有變得更糟，只是
如果訊息中包含了 ‘\0’ 字元，你就不能使用 ‘strlen’ 函式。）

最簡單的改進方法是將訊息的第一個字元表示訊息的類型，並根據訊息的類型來決
定訊息的長度。現在你需要使用兩次 ‘recv’ - 第一次用於接收（至少）第一個字
元來得知長度，第二次用於在迴圈中接收剩下的訊息。如果你決定使用分隔符號的
方式，你將會以某個任意的區塊大小進行接收（4096 或 8192 通常是網路緩衝區
大小的良好選擇），並在收到的內容中掃描分隔符號。

需要注意的一個複雜情況是，如果你的通訊協議允許連續發送多個訊息（沒有任何
回應），並且你傳遞給 ‘recv’ 函式一個任意的區塊大小，最後有可能讀取到下一
條訊息的開頭。你需要將其放在一旁並保留下來，直到需要使用的時候。

使用長度作為訊息的前綴（例如，使用 5 個數字字元表示）會變得更複雜，因為
（信不信由你）你可能無法在一次 ‘recv’ 中獲得所有 5 個字元。在一般使用下
，可能不會有這個狀況，但在高負載的網路下，除非使用兩個 ‘recv’ （第一個用
於確定長度，第二個用於取得訊息的資料部分），否則你的程式碼很快就會出現錯
誤。這令人非常頭痛。同樣的情況也會讓你發現 ‘send’ 並不總能在一次傳輸中完
全清除所有內容。儘管已經閱讀了這篇文章，但最終還是無法解決！

為了節省篇幅、培養你的技能（並保持我的競爭優勢），這些改進方法留給讀者自
行練習。現在讓我們開始進行清理工作。

* Menu:

* 二進位資料::


File: python.info,  Node: 二進位資料,  Up: 使用一個 Socket

9.10.3.1 二進位資料
...................

使用 socket 傳輸二進位資料完全是可行的。最主要的問題在於不同機器使用不同
的二進位資料格式。例如，網路二進位順序(1) 採用的是「大端序 big-endian」
，所以一個值為 ‘1’ 的 16 位元整數會表示成兩個 16 進位的位元組 ‘00 01’。
然而大多數常見的處理器 (x86/AMD64，ARM，RISC-V) 採用的是「小端序
little-endian」，所以相同的 ‘1’ 會被表示成 ‘01 00’。（譯者注：將一個多位
數的低位放在較小的位址處，高位放在較大的位址處，則稱小端序；反之則稱大端
序。）

Socket 函式庫提供了用於轉換 16 位元和 32 位元整數的函式 - ‘ntohl, htonl,
ntohs, htons’，其中 "n" 表示 'network'，"h" 表示 'host'，"s" 表示
'short'，"l" 表示 'long'。當網路的位元組順序和主機位元組順序相同時，這些
函式不會做任何操作，但當主機的位元組順序相反時，這些函式會適當的交換位元
組順序。

在現今的 64 位元機器中，二進位資料的 ASCII 表示通常會比二進位表示要小，
這是因為在很多情況下，大多數整數的值為 0 或者 1。例如，字串形式的 ‘"0"’
是兩個位元組，而完整的 64 位元整數則是 8 個位元組。當然，這對固定長度的
訊息來說不太適合，需要自行決定。

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Endianness#Networking


File: python.info,  Node: 結束連線,  Next: 非阻塞的 Sockets,  Prev: 使用一個 Socket,  Up: Socket 程式設計指南

9.10.4 結束連線
---------------

嚴格來說，在關閉 socket 前，你應該使用 ‘shutdown’ 函式。‘shutdown’ 函式
是發送給 socket 另一端的一個提醒。根據你傳遞的引數，它可以表示「我不會再
發送任何訊息了，但我仍然會持續監聽」，或者是「我不會再繼續監聽了，真讚！
」。然而，大多數的 socket 函式庫或程式設計師都習慣忽略這種禮節，因為通常
情況下 ‘close’ 跟 ‘shutdown(); close()’ 是一樣的。所以在大多數情況下，不
需要再特地使用 ‘shutdown’ 了。

有效使用 ‘shutdown’ 的一種方式是在類似 HTTP 的交換中，用戶端發送請求後，
然後使用 ‘shutdown(1)’。這告訴伺服器「這個用戶端已經發送完成，但仍可以接
收」。伺服器可以通過接收「零位元組」來檢測 "EOF"。這樣它就可以確定已經接
收到完整的請求。伺服器發送回覆，如果 ‘send’ 成功完成，那麼用戶端確實在持
續接收。

Python 更進一步地採取自動關閉的步驟，並且當 socket 被垃圾回收機制回收時
，如果需要的話，他會自動執行 ‘close’。但依賴這個機制是一個非常不好的習慣
，如果你的 socket 在沒有 ‘close’ 的情況下消失了，那麼另一端的 socket 可
能會認為你只是慢了一步，而無期限的等待。'請務必' 在使用完畢後使用
‘close’ 關閉你的 sockets。

* Menu:

* Sockets 何時銷毀::


File: python.info,  Node: Sockets 何時銷毀,  Up: 結束連線

9.10.4.1 Sockets 何時銷毀
.........................

使用阻塞式 socket 最糟糕的地方可能是在另一端突然強制關閉（未執行
‘close’）的情況下會發生什麼？你的 socket 很可能會處於阻塞狀態。TCP 是一
種可靠的協議，它在放棄連線之前會等待很長很長的時間。如果你正在使用執行緒
，整個執行緒基本上已經無法使用。在這方面，你無法做太多事情。只要你不做一
些愚蠢的事情，比如在執行阻塞式讀取時持有一個鎖，那麼執行緒並不會消耗太多
資源。'不要'試圖終止執行緒 - 執行緒比行程更有效的部分原因是它們避免了與
自動回收資源相關的開銷。換句話說，如果你確實設法終止了執行緒，整個行程可
能會出現問題。


File: python.info,  Node: 非阻塞的 Sockets,  Prev: 結束連線,  Up: Socket 程式設計指南

9.10.5 非阻塞的 Sockets
-----------------------

如果你已經理解了前面的內容，你已經知道了大部分關於使用 sockets 的機制的
所需知識，你仍然會以非常相似的方式使用相同的函式。就這樣而已，如果你做的
對，你的程式就會是近乎完美的。

在 Python 中可以使用 ‘socket.setblocking(False)’ 來設定為非阻塞。在 C 的
作法更為複雜（例如，你需要在 BSD 風格的 ‘O_NONBLOCK’ 和幾乎沒有區別的
POSIX 風格的 ‘O_NDELAY’ 之間做出選擇，這與 ‘TCP_NODELAY’ 完全不同），但
基本思想是一樣的，你要在建立 socket 後但在使用它之前執行此操作。（實際上
，如果你願意的話，你甚至可以來回切換。）

主要的機制差異在於 ‘send’、‘recv’、‘connect’ 和 ‘accept’ 可能在沒有執行
任何操作的情況下就回傳了。你當然有多種選擇。你可以檢查回傳值和錯誤代碼，
但這些操作通常會讓自己抓狂。如果你不相信我，不妨試試看。你的應用程式會變
得臃腫、錯誤百出，並且占用 CPU。所以，讓我們跳過無腦的解決方案，使用正確
的方式。

使用 ‘select’。

在 C 中，編寫 ‘select’ 是非常複雜的，但在 Python 中，這很簡單，並與 C 的
版本非常類似，如果你理解了 Python 中的 ‘select’，在 C 中處理它時也不會有
太大的困難：

     ready_to_read, ready_to_write, in_error = \
                    select.select(
                       potential_readers,
                       potential_writers,
                       potential_errs,
                       timeout)

你傳遞給 ‘select’ 三個列表：第一個列表包含你可能想要嘗試讀取的所有
sockets；第二個包含所有你可能想要嘗試寫入的 sockets，最後一個（通常為空
）包含你想要檢查錯誤的 sockets。你應該注意，一個 socket 可以同時存在於多
個列表中。‘select’ 呼叫是阻塞的，但你可以設置超時。通常這是一個明智的做
法 - 除非有充分的理由，否則給它一個很長的超時（比如一分鐘）。

作為回傳，你將獲得三個列表。它們包含實際上可讀取、可寫入和出錯的
sockets。這些列表中的每一個都是你傳入的相應列表的子集（可能為空）。

如果一個 socket 在輸出的可讀列表中，你可以幾乎確定，在這個業務中我們能夠
得到的最接近確定的事情是，對該 socket 的 ‘recv’ 呼叫將會回傳一些'內容'。
對於可寫列表，也是同樣的想法。你將能夠發送一些 '內容'。也許不是全部，但
'一些內容'總比什麼都沒有好。（實際上，任何比較正常的 socket 都會以可寫的
方式回傳 - 這只是意味者「外送網路 (outbound network)」的緩衝空間是可用的
。）

如果你有一個「伺服器端」socket，請將其放在 potential_readers 列表中，如
果它在可讀列表中出現，你的 ‘accept’ 呼叫（幾乎可以確定）會成功。如果你建
立了一個新的 socket 去 ‘connect’ 到其他地方，請將它放在
potential_writers 列表中，如果它在可寫列表中出現，那麼他有可能已經連接上
了。

實際上，即使是使用阻塞式 socket 的情況下，‘select’ 也很方便。這是一種判
斷是否會被阻塞的方法之一 - 當緩衝區中有某些內容時， socket 會回傳為可讀
。然而，這仍然無法解決判斷另一端是否完成，或者只是忙於其他事情的問題。

'可移植性警告'：在 Unix 上，‘select’ 同時適用於 sockets 和文件。但請不要
在 Windows 上嘗試這麼做，在 Windows 上，‘select’ 只適用於 sockets。同時
，請注意，在 C 語言中，許多更進階的 socket 選項在 Windows 上有不同的實現
方式。實際上，在 Windows 上，我通常會使用執行緒（這非常，非常有效）與我
的 sockets 一起使用。


File: python.info,  Node: 排序技法,  Next: Unicode HOWTO,  Prev: Socket 程式設計指南,  Up: Python 如何達成任務

9.11 排序技法
=============


作者: Andrew Dalke 和 Raymond Hettinger

Python 的串列有一個內建的 *note list.sort(): b76. 方法可以原地
(in-place) 排序該串列，也有一個內建的 *note sorted(): b75. 函式可以排序
可疊代物件 (iterable) 並建立一個新的排序好的串列。

在這份文件裡，我們探索使用 Python 排序資料的各種方法。

* Menu:

* 基礎排序::
* 鍵函式 (key functions): 鍵函式 key functions.
* Operator Module Functions and Partial Function Evaluation::
* 升冪與降冪::
* 排序穩定性與複合排序::
* 裝飾-排序-移除裝飾 (decorate-sort-undecorate): 裝飾-排序-移除裝飾 decorate-sort-undecorate.
* 比較函式 (comparison functions): 比較函式 comparison functions.
* 雜項說明::
* Partial Sorts::


File: python.info,  Node: 基礎排序,  Next: 鍵函式 key functions,  Up: 排序技法

9.11.1 基礎排序
---------------

單純的升冪排序很容易做到：只要呼叫 *note sorted(): b75. 函式，它會回傳一
個新的串列：

     >>> sorted([5, 2, 3, 1, 4])
     [1, 2, 3, 4, 5]

你也可以使用 *note list.sort(): b76. 方法，它會原地排序串列（並回傳
‘None’ 以避免混淆）。它通常會比 *note sorted(): b75. 來得不方便——但如果
你不需要保留原始串列的話，它會稍微有效率一點。

     >>> a = [5, 2, 3, 1, 4]
     >>> a.sort()
     >>> a
     [1, 2, 3, 4, 5]

另一個差異是 *note list.sort(): b76. 方法只有定義在串列上，而 *note
sorted(): b75. 函式可以接受任何可疊代物件。

     >>> sorted({1: 'D', 2: 'B', 3: 'B', 4: 'E', 5: 'A'})
     [1, 2, 3, 4, 5]


File: python.info,  Node: 鍵函式 key functions,  Next: Operator Module Functions and Partial Function Evaluation,  Prev: 基礎排序,  Up: 排序技法

9.11.2 鍵函式 (key functions)
-----------------------------

*note list.sort(): b76. 和 *note sorted(): b75. 都有一個參數 'key' 可以
指定一個函式（或其它可呼叫物件 (callable)），這個函式會在每個串列元素做
比較前被呼叫。

例如這裡有一個不區分大小寫的字串比對：

     >>> sorted("This is a test string from Andrew".split(), key=str.casefold)
     ['a', 'Andrew', 'from', 'is', 'string', 'test', 'This']

參數 'key' 的值必須是一個函式（或其它可呼叫物件），且這個函式接受單一引
數並回傳一個用來排序的鍵。因為對每個輸入來說鍵函式只會被呼叫一次，所以這
個做法是快速的。

一個常見的模式是在排序複雜物件的時候使用一部分物件的索引值當作鍵，例如：

     >>> student_tuples = [
     ...     ('john', 'A', 15),
     ...     ('jane', 'B', 12),
     ...     ('dave', 'B', 10),
     ... ]
     >>> sorted(student_tuples, key=lambda student: student[2])   # sort by age
     [('dave', 'B', 10), ('jane', 'B', 12), ('john', 'A', 15)]

相同的做法也適用在有命名屬性的物件，例如：

     >>> class Student:
     ...     def __init__(self, name, grade, age):
     ...         self.name = name
     ...         self.grade = grade
     ...         self.age = age
     ...     def __repr__(self):
     ...         return repr((self.name, self.grade, self.age))

     >>> student_objects = [
     ...     Student('john', 'A', 15),
     ...     Student('jane', 'B', 12),
     ...     Student('dave', 'B', 10),
     ... ]
     >>> sorted(student_objects, key=lambda student: student.age)   # sort by age
     [('dave', 'B', 10), ('jane', 'B', 12), ('john', 'A', 15)]

Objects with named attributes can be made by a regular class as shown
above, or they can be instances of *note dataclass: 1af. or a *note
named tuple: 5f4.


File: python.info,  Node: Operator Module Functions and Partial Function Evaluation,  Next: 升冪與降冪,  Prev: 鍵函式 key functions,  Up: 排序技法

9.11.3 Operator Module Functions and Partial Function Evaluation
----------------------------------------------------------------

上述的*note 鍵函式: dab.模式非常常見，所以 Python 提供了方便的函式讓物件
存取更簡單且快速。*note operator: 8f. 模組裡有 *note itemgetter(): a05.、
*note attrgetter(): dd9. 及 *note methodcaller(): dda. 函式可以使用。

使用這些函式讓上面的範例變得更簡單且快速：

     >>> from operator import itemgetter, attrgetter

     >>> sorted(student_tuples, key=itemgetter(2))
     [('dave', 'B', 10), ('jane', 'B', 12), ('john', 'A', 15)]

     >>> sorted(student_objects, key=attrgetter('age'))
     [('dave', 'B', 10), ('jane', 'B', 12), ('john', 'A', 15)]

operator 模組的函式允許多層的排序，例如先用 'grade' 排序再用 'age' 排序
：

     >>> sorted(student_tuples, key=itemgetter(1,2))
     [('john', 'A', 15), ('dave', 'B', 10), ('jane', 'B', 12)]

     >>> sorted(student_objects, key=attrgetter('grade', 'age'))
     [('john', 'A', 15), ('dave', 'B', 10), ('jane', 'B', 12)]

The *note functools: 55. module provides another helpful tool for making
key-functions.  The *note partial(): 356. function can reduce the
arity(1) of a multi-argument function making it suitable for use as a
key-function.

     >>> from functools import partial
     >>> from unicodedata import normalize

     >>> names = 'Zoë Åbjørn Núñez Élana Zeke Abe Nubia Eloise'.split()

     >>> sorted(names, key=partial(normalize, 'NFD'))
     ['Abe', 'Åbjørn', 'Eloise', 'Élana', 'Nubia', 'Núñez', 'Zeke', 'Zoë']

     >>> sorted(names, key=partial(normalize, 'NFC'))
     ['Abe', 'Eloise', 'Nubia', 'Núñez', 'Zeke', 'Zoë', 'Åbjørn', 'Élana']

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Arity


File: python.info,  Node: 升冪與降冪,  Next: 排序穩定性與複合排序,  Prev: Operator Module Functions and Partial Function Evaluation,  Up: 排序技法

9.11.4 升冪與降冪
-----------------

*note list.sort(): b76. 和 *note sorted(): b75. 都有一個 boolean 參數
'reverse' 用來表示是否要降冪排序。例如將學生資料依據 'age' 做降冪排序：

     >>> sorted(student_tuples, key=itemgetter(2), reverse=True)
     [('john', 'A', 15), ('jane', 'B', 12), ('dave', 'B', 10)]

     >>> sorted(student_objects, key=attrgetter('age'), reverse=True)
     [('john', 'A', 15), ('jane', 'B', 12), ('dave', 'B', 10)]


File: python.info,  Node: 排序穩定性與複合排序,  Next: 裝飾-排序-移除裝飾 decorate-sort-undecorate,  Prev: 升冪與降冪,  Up: 排序技法

9.11.5 排序穩定性與複合排序
---------------------------

排序保證是穩定的(1)，意思是當有多筆資料有相同的鍵，它們會維持原來的順序
。

     >>> data = [('red', 1), ('blue', 1), ('red', 2), ('blue', 2)]
     >>> sorted(data, key=itemgetter(0))
     [('blue', 1), ('blue', 2), ('red', 1), ('red', 2)]

可以注意到有兩筆資料的鍵都是 'blue'，它們會維持本來的順序，即 ‘('blue',
1)’ 保證在 ‘('blue', 2)’ 前面。

這個美妙的特性讓你可以用一連串的排序來作出複合排序。例如對學生資料用
'grade' 做降冪排序再用 'age' 做升冪排序，你可以先用 'age' 排序一遍再用
'grade' 排序一遍：

     >>> s = sorted(student_objects, key=attrgetter('age'))     # sort on secondary key
     >>> sorted(s, key=attrgetter('grade'), reverse=True)       # now sort on primary key, descending
     [('dave', 'B', 10), ('jane', 'B', 12), ('john', 'A', 15)]

這可以抽出一個包裝函式 (wrapper function)，接受一個串列及多個欄位及升降
冪的元組為引數，來對這個串列排序多遍。

     >>> def multisort(xs, specs):
     ...     for key, reverse in reversed(specs):
     ...         xs.sort(key=attrgetter(key), reverse=reverse)
     ...     return xs

     >>> multisort(list(student_objects), (('grade', True), ('age', False)))
     [('dave', 'B', 10), ('jane', 'B', 12), ('john', 'A', 15)]

Python 裡使用的 Timsort(2) 演算法，因為能利用資料集裡已經有的順序，可以
有效率地做多次排序。

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Sorting_algorithm#Stability

   (2) https://en.wikipedia.org/wiki/Timsort


File: python.info,  Node: 裝飾-排序-移除裝飾 decorate-sort-undecorate,  Next: 比較函式 comparison functions,  Prev: 排序穩定性與複合排序,  Up: 排序技法

9.11.6 裝飾-排序-移除裝飾 (decorate-sort-undecorate)
----------------------------------------------------

這個用語的來源是因為它做了以下三件事情：

   * 首先，原始串列會裝飾 (decorated) 上新的值用來控制排序的順序。

   * 接下來，排序裝飾過的串列。

   * 最後，裝飾會被移除，並以新的順序產生一個只包含原始值的串列。

例如用上面說的方式來以 'grade' 排序學生資料：

     >>> decorated = [(student.grade, i, student) for i, student in enumerate(student_objects)]
     >>> decorated.sort()
     >>> [student for grade, i, student in decorated]               # undecorate
     [('john', 'A', 15), ('jane', 'B', 12), ('dave', 'B', 10)]

這個方式會有效是因為元組是依照字典順序 (lexicographically) 來比較，先比
較第一個項目，如果一樣再比較第二個項目，並依此類推。

在所有情況下都把索引 'i' 加入已裝飾的串列並不是絕對需要的，但這樣做會有
兩個好處：

   * 排序會是穩定的 - 如果兩個項目有相同的鍵，它們在排序好的串列中會保持
     原來的順序。

   * 原始項目不需要是可以比較的，因為最多只會用到前兩個項目就能決定裝飾
     過的元組的順序。例如原始串列可以包含不能直接用來排序的複數。

這個用語的另一個名字是 Schwartzian transform(1)，是由於 Randal L.
Schwartz 讓這個方法在 Perl 程式設計師間普及。

而因為 Python 的排序提供了鍵函式，已經不太需要用到這個方法了。

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Schwartzian_transform


File: python.info,  Node: 比較函式 comparison functions,  Next: 雜項說明,  Prev: 裝飾-排序-移除裝飾 decorate-sort-undecorate,  Up: 排序技法

9.11.7 比較函式 (comparison functions)
--------------------------------------

不像鍵函式回傳一個用來排序的值，比較函式計算兩個輸入間的相對順序。

例如天秤(1)比較兩邊樣本並給出相對的順序：較輕、相同或較重。同樣地，像是
‘cmp(a, b)’ 這樣的比較函式會回傳負數代表小於、0 代表輸入相同或正數代表大
於。

當從其它語言翻譯演算法的時候常看到比較函式。有些函式庫也會提供比較函式作
為其 API 的一部份，例如 *note locale.strcoll(): 3b62. 就是一個比較函式。

為了滿足這些情境，Python 提供 *note functools.cmp_to_key: 1172. 來包裝比
較函式，讓其可以當作鍵函式來使用：

     sorted(words, key=cmp_to_key(strcoll))  # locale-aware sort order

   ---------- Footnotes ----------

   (1) 
https://upload.wikimedia.org/wikipedia/commons/1/17/Balance_à_tabac_1850.JPG


File: python.info,  Node: 雜項說明,  Next: Partial Sorts,  Prev: 比較函式 comparison functions,  Up: 排序技法

9.11.8 雜項說明
---------------

   * 要處理能理解本地語系 (locale aware) 的排序可以使用 *note
     locale.strxfrm(): 3b64. 當作鍵函式，或 *note locale.strcoll():
     3b62. 當作比較函式。這樣做是必要的，因為在不同文化中就算是相同的字
     母，按「字母順序」排序的結果也各不相同。

   * 'reverse' 參數依然會維持排序穩定性（即有相同鍵的資料會保持原來順序
     ）。有趣的是，不加這個參數也可以模擬這個效果，只要使用內建的 *note
     reversed(): 80a. 函式兩次：

          >>> data = [('red', 1), ('blue', 1), ('red', 2), ('blue', 2)]
          >>> standard_way = sorted(data, key=itemgetter(0), reverse=True)
          >>> double_reversed = list(reversed(sorted(reversed(data), key=itemgetter(0))))
          >>> assert standard_way == double_reversed
          >>> standard_way
          [('red', 1), ('red', 2), ('blue', 1), ('blue', 2)]

   * 排序時會使用 ‘<’ 來比較兩個物件，因此要在類別裡面加入排序順序比較規
     則是簡單的，只要透過定義 *note __lt__(): 129e. 方法：

          >>> Student.__lt__ = lambda self, other: self.age < other.age
          >>> sorted(student_objects)
          [('dave', 'B', 10), ('jane', 'B', 12), ('john', 'A', 15)]

     However, note that ‘<’ can fall back to using *note __gt__(): 12a0.
     if *note __lt__(): 129e. is not implemented (see *note
     object.__lt__(): 129e. for details on the mechanics).  To avoid
     surprises, PEP 8(1) recommends that all six comparison methods be
     implemented.  The *note total_ordering(): ee6. decorator is
     provided to make that task easier.

   * 鍵函式不需要直接依賴用來排序的物件。鍵函式也可以存取外部資源，例如
     如果學生成績儲存在字典裡，它可以用來排序一個單獨的學生姓名串列：

          >>> students = ['dave', 'john', 'jane']
          >>> newgrades = {'john': 'F', 'jane':'A', 'dave': 'C'}
          >>> sorted(students, key=newgrades.__getitem__)
          ['jane', 'dave', 'john']

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0008/


File: python.info,  Node: Partial Sorts,  Prev: 雜項說明,  Up: 排序技法

9.11.9 Partial Sorts
--------------------

Some applications require only some of the data to be ordered.  The
standard library provides several tools that do less work than a full
sort:

   * *note min(): eac. and *note max(): ead. return the smallest and
     largest values, respectively.  These functions make a single pass
     over the input data and require almost no auxiliary memory.

   * *note heapq.nsmallest(): 240c. and *note heapq.nlargest(): 240b.
     return the 'n' smallest and largest values, respectively.  These
     functions make a single pass over the data keeping only 'n'
     elements in memory at a time.  For values of 'n' that are small
     relative to the number of inputs, these functions make far fewer
     comparisons than a full sort.

   * *note heapq.heappush(): 1427. and *note heapq.heappop(): 1428.
     create and maintain a partially sorted arrangement of data that
     keeps the smallest element at position ‘0’.  These functions are
     suitable for implementing priority queues which are commonly used
     for task scheduling.


File: python.info,  Node: Unicode HOWTO,  Next: 如何使用 urllib 套件取得網路資源,  Prev: 排序技法,  Up: Python 如何達成任務

9.12 Unicode HOWTO
==================


發佈版本: 1.12

This HOWTO discusses Python's support for the Unicode specification for
representing textual data, and explains various problems that people
commonly encounter when trying to work with Unicode.

* Menu:

* Introduction to Unicode::
* Python's Unicode Support::
* Reading and Writing Unicode Data::
* 致謝: 致謝<10>.


File: python.info,  Node: Introduction to Unicode,  Next: Python's Unicode Support,  Up: Unicode HOWTO

9.12.1 Introduction to Unicode
------------------------------

* Menu:

* 定義::
* Encodings::
* References: References<3>.


File: python.info,  Node: 定義,  Next: Encodings,  Up: Introduction to Unicode

9.12.1.1 定義
.............

Today's programs need to be able to handle a wide variety of characters.
Applications are often internationalized to display messages and output
in a variety of user-selectable languages; the same program might need
to output an error message in English, French, Japanese, Hebrew, or
Russian.  Web content can be written in any of these languages and can
also include a variety of emoji symbols.  Python's string type uses the
Unicode Standard for representing characters, which lets Python programs
work with all these different possible characters.

Unicode (‘https://www.unicode.org/’) is a specification that aims to
list every character used by human languages and give each character its
own unique code.  The Unicode specifications are continually revised and
updated to add new languages and symbols.

A 'character' is the smallest possible component of a text.  'A', 'B',
'C', etc., are all different characters.  So are 'È' and 'Í'. Characters
vary depending on the language or context you're talking about.  For
example, there's a character for "Roman Numeral One", 'Ⅰ', that's
separate from the uppercase letter 'I'. They'll usually look the same,
but these are two different characters that have different meanings.

The Unicode standard describes how characters are represented by 'code
points'.  A code point value is an integer in the range 0 to 0x10FFFF
(about 1.1 million values, the actual number assigned(1) is less than
that).  In the standard and in this document, a code point is written
using the notation ‘U+265E’ to mean the character with value ‘0x265e’
(9,822 in decimal).

The Unicode standard contains a lot of tables listing characters and
their corresponding code points:

     0061    'a'; LATIN SMALL LETTER A
     0062    'b'; LATIN SMALL LETTER B
     0063    'c'; LATIN SMALL LETTER C
     ...
     007B    '{'; LEFT CURLY BRACKET
     ...
     2167    'Ⅷ'; ROMAN NUMERAL EIGHT
     2168    'Ⅸ'; ROMAN NUMERAL NINE
     ...
     265E    '♞'; BLACK CHESS KNIGHT
     265F    '♟'; BLACK CHESS PAWN
     ...
     1F600   '😀'; GRINNING FACE
     1F609   '😉'; WINKING FACE
     ...

Strictly, these definitions imply that it's meaningless to say 'this is
character ‘U+265E’'.  ‘U+265E’ is a code point, which represents some
particular character; in this case, it represents the character 'BLACK
CHESS KNIGHT', '♞'.  In informal contexts, this distinction between code
points and characters will sometimes be forgotten.

A character is represented on a screen or on paper by a set of graphical
elements that's called a 'glyph'.  The glyph for an uppercase A, for
example, is two diagonal strokes and a horizontal stroke, though the
exact details will depend on the font being used.  Most Python code
doesn't need to worry about glyphs; figuring out the correct glyph to
display is generally the job of a GUI toolkit or a terminal's font
renderer.

   ---------- Footnotes ----------

   (1) https://www.unicode.org/versions/latest/#Summary


File: python.info,  Node: Encodings,  Next: References<3>,  Prev: 定義,  Up: Introduction to Unicode

9.12.1.2 Encodings
..................

To summarize the previous section: a Unicode string is a sequence of
code points, which are numbers from 0 through ‘0x10FFFF’ (1,114,111
decimal).  This sequence of code points needs to be represented in
memory as a set of 'code units', and 'code units' are then mapped to
8-bit bytes.  The rules for translating a Unicode string into a sequence
of bytes are called a 'character encoding', or just an 'encoding'.

The first encoding you might think of is using 32-bit integers as the
code unit, and then using the CPU's representation of 32-bit integers.
In this representation, the string "Python" might look like this:

        P           y           t           h           o           n
     0x50 00 00 00 79 00 00 00 74 00 00 00 68 00 00 00 6f 00 00 00 6e 00 00 00
        0  1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

This representation is straightforward but using it presents a number of
problems.

  1. It's not portable; different processors order the bytes
     differently.

  2. It's very wasteful of space.  In most texts, the majority of the
     code points are less than 127, or less than 255, so a lot of space
     is occupied by ‘0x00’ bytes.  The above string takes 24 bytes
     compared to the 6 bytes needed for an ASCII representation.
     Increased RAM usage doesn't matter too much (desktop computers have
     gigabytes of RAM, and strings aren't usually that large), but
     expanding our usage of disk and network bandwidth by a factor of 4
     is intolerable.

  3. It's not compatible with existing C functions such as ‘strlen()’,
     so a new family of wide string functions would need to be used.

Therefore this encoding isn't used very much, and people instead choose
other encodings that are more efficient and convenient, such as UTF-8.

UTF-8 is one of the most commonly used encodings, and Python often
defaults to using it.  UTF stands for "Unicode Transformation Format",
and the '8' means that 8-bit values are used in the encoding.  (There
are also UTF-16 and UTF-32 encodings, but they are less frequently used
than UTF-8.)  UTF-8 uses the following rules:

  1. If the code point is < 128, it's represented by the corresponding
     byte value.

  2. If the code point is >= 128, it's turned into a sequence of two,
     three, or four bytes, where each byte of the sequence is between
     128 and 255.

UTF-8 has several convenient properties:

  1. It can handle any Unicode code point.

  2. A Unicode string is turned into a sequence of bytes that contains
     embedded zero bytes only where they represent the null character
     (U+0000).  This means that UTF-8 strings can be processed by C
     functions such as ‘strcpy()’ and sent through protocols that can't
     handle zero bytes for anything other than end-of-string markers.

  3. A string of ASCII text is also valid UTF-8 text.

  4. UTF-8 is fairly compact; the majority of commonly used characters
     can be represented with one or two bytes.

  5. If bytes are corrupted or lost, it's possible to determine the
     start of the next UTF-8-encoded code point and resynchronize.  It's
     also unlikely that random 8-bit data will look like valid UTF-8.

  6. UTF-8 is a byte oriented encoding.  The encoding specifies that
     each character is represented by a specific sequence of one or more
     bytes.  This avoids the byte-ordering issues that can occur with
     integer and word oriented encodings, like UTF-16 and UTF-32, where
     the sequence of bytes varies depending on the hardware on which the
     string was encoded.


File: python.info,  Node: References<3>,  Prev: Encodings,  Up: Introduction to Unicode

9.12.1.3 References
...................

The Unicode Consortium site(1) has character charts, a glossary, and PDF
versions of the Unicode specification.  Be prepared for some difficult
reading.  A chronology(2) of the origin and development of Unicode is
also available on the site.

On the Computerphile Youtube channel, Tom Scott briefly discusses the
history of Unicode and UTF-8(3) (9 minutes 36 seconds).

To help understand the standard, Jukka Korpela has written an
introductory guide(4) to reading the Unicode character tables.

Another good introductory article(5) was written by Joel Spolsky.  If
this introduction didn't make things clear to you, you should try
reading this alternate article before continuing.

Wikipedia entries are often helpful; see the entries for "character
encoding(6)" and UTF-8(7), for example.

   ---------- Footnotes ----------

   (1) https://www.unicode.org

   (2) https://www.unicode.org/history/

   (3) https://www.youtube.com/watch?v=MijmeoH9LT4

   (4) https://jkorpela.fi/unicode/guide.html

   (5) 
https://www.joelonsoftware.com/2003/10/08/the-absolute-minimum-every-software-developer-absolutely-positively-must-know-about-unicode-and-character-sets-no-excuses/

   (6) https://en.wikipedia.org/wiki/Character_encoding

   (7) https://en.wikipedia.org/wiki/UTF-8


File: python.info,  Node: Python's Unicode Support,  Next: Reading and Writing Unicode Data,  Prev: Introduction to Unicode,  Up: Unicode HOWTO

9.12.2 Python's Unicode Support
-------------------------------

Now that you've learned the rudiments of Unicode, we can look at
Python's Unicode features.

* Menu:

* The String Type::
* Converting to Bytes::
* Unicode Literals in Python Source Code::
* Unicode Properties::
* Comparing Strings::
* Unicode Regular Expressions::
* References: References<4>.


File: python.info,  Node: The String Type,  Next: Converting to Bytes,  Up: Python's Unicode Support

9.12.2.1 The String Type
........................

Since Python 3.0, the language's *note str: 3f2. type contains Unicode
characters, meaning any string created using ‘"unicode rocks!"’,
‘'unicode rocks!'’, or the triple-quoted string syntax is stored as
Unicode.

The default encoding for Python source code is UTF-8, so you can simply
include a Unicode character in a string literal:

     try:
         with open('/tmp/input.txt', 'r') as f:
             ...
     except OSError:
         # 'File not found' error message.
         print("Fichier non trouvé")

Side note: Python 3 also supports using Unicode characters in
identifiers:

     répertoire = "/tmp/records.log"
     with open(répertoire, "w") as f:
         f.write("test\n")

If you can't enter a particular character in your editor or want to keep
the source code ASCII-only for some reason, you can also use escape
sequences in string literals.  (Depending on your system, you may see
the actual capital-delta glyph instead of a u escape.)

     >>> "\N{GREEK CAPITAL LETTER DELTA}"  # Using the character name
     '\u0394'
     >>> "\u0394"                          # Using a 16-bit hex value
     '\u0394'
     >>> "\U00000394"                      # Using a 32-bit hex value
     '\u0394'

In addition, one can create a string using the *note decode(): 87b.
method of *note bytes: 1a5.  This method takes an 'encoding' argument,
such as ‘UTF-8’, and optionally an 'errors' argument.

The 'errors' argument specifies the response when the input string can't
be converted according to the encoding's rules.  Legal values for this
argument are ‘'strict'’ (raise a *note UnicodeDecodeError: 9b7.
exception), ‘'replace'’ (use ‘U+FFFD’, ‘REPLACEMENT CHARACTER’),
‘'ignore'’ (just leave the character out of the Unicode result), or
‘'backslashreplace'’ (inserts a ‘\xNN’ escape sequence).  The following
examples show the differences:

     >>> b'\x80abc'.decode("utf-8", "strict")
     Traceback (most recent call last):
         ...
     UnicodeDecodeError: 'utf-8' codec can't decode byte 0x80 in position 0:
       invalid start byte
     >>> b'\x80abc'.decode("utf-8", "replace")
     '\ufffdabc'
     >>> b'\x80abc'.decode("utf-8", "backslashreplace")
     '\\x80abc'
     >>> b'\x80abc'.decode("utf-8", "ignore")
     'abc'

Encodings are specified as strings containing the encoding's name.
Python comes with roughly 100 different encodings; see the Python
Library Reference at *note Standard Encodings: d5f. for a list.  Some
encodings have multiple names; for example, ‘'latin-1'’, ‘'iso_8859_1'’
and ‘'8859’' are all synonyms for the same encoding.

One-character Unicode strings can also be created with the *note chr():
1568. built-in function, which takes integers and returns a Unicode
string of length 1 that contains the corresponding code point.  The
reverse operation is the built-in *note ord(): 1de1. function that takes
a one-character Unicode string and returns the code point value:

     >>> chr(57344)
     '\ue000'
     >>> ord('\ue000')
     57344


File: python.info,  Node: Converting to Bytes,  Next: Unicode Literals in Python Source Code,  Prev: The String Type,  Up: Python's Unicode Support

9.12.2.2 Converting to Bytes
............................

The opposite method of *note bytes.decode(): 87b. is *note str.encode():
87a, which returns a *note bytes: 1a5. representation of the Unicode
string, encoded in the requested 'encoding'.

The 'errors' parameter is the same as the parameter of the *note
decode(): 87b. method but supports a few more possible handlers.  As
well as ‘'strict'’, ‘'ignore'’, and ‘'replace'’ (which in this case
inserts a question mark instead of the unencodable character), there is
also ‘'xmlcharrefreplace'’ (inserts an XML character reference),
‘backslashreplace’ (inserts a ‘\uNNNN’ escape sequence) and
‘namereplace’ (inserts a ‘\N{...}’ escape sequence).

The following example shows the different results:

     >>> u = chr(40960) + 'abcd' + chr(1972)
     >>> u.encode('utf-8')
     b'\xea\x80\x80abcd\xde\xb4'
     >>> u.encode('ascii')
     Traceback (most recent call last):
         ...
     UnicodeEncodeError: 'ascii' codec can't encode character '\ua000' in
       position 0: ordinal not in range(128)
     >>> u.encode('ascii', 'ignore')
     b'abcd'
     >>> u.encode('ascii', 'replace')
     b'?abcd?'
     >>> u.encode('ascii', 'xmlcharrefreplace')
     b'&#40960;abcd&#1972;'
     >>> u.encode('ascii', 'backslashreplace')
     b'\\ua000abcd\\u07b4'
     >>> u.encode('ascii', 'namereplace')
     b'\\N{YI SYLLABLE IT}abcd\\u07b4'

The low-level routines for registering and accessing the available
encodings are found in the *note codecs: 14. module.  Implementing new
encodings also requires understanding the *note codecs: 14. module.
However, the encoding and decoding functions returned by this module are
usually more low-level than is comfortable, and writing new encodings is
a specialized task, so the module won't be covered in this HOWTO.


File: python.info,  Node: Unicode Literals in Python Source Code,  Next: Unicode Properties,  Prev: Converting to Bytes,  Up: Python's Unicode Support

9.12.2.3 Unicode Literals in Python Source Code
...............................................

In Python source code, specific Unicode code points can be written using
the ‘\u’ escape sequence, which is followed by four hex digits giving
the code point.  The ‘\U’ escape sequence is similar, but expects eight
hex digits, not four:

     >>> s = "a\xac\u1234\u20ac\U00008000"
     ... #     ^^^^ two-digit hex escape
     ... #         ^^^^^^ four-digit Unicode escape
     ... #                     ^^^^^^^^^^ eight-digit Unicode escape
     >>> [ord(c) for c in s]
     [97, 172, 4660, 8364, 32768]

Using escape sequences for code points greater than 127 is fine in small
doses, but becomes an annoyance if you're using many accented
characters, as you would in a program with messages in French or some
other accent-using language.  You can also assemble strings using the
*note chr(): 1568. built-in function, but this is even more tedious.

Ideally, you'd want to be able to write literals in your language's
natural encoding.  You could then edit Python source code with your
favorite editor which would display the accented characters naturally,
and have the right characters used at runtime.

Python supports writing source code in UTF-8 by default, but you can use
almost any encoding if you declare the encoding being used.  This is
done by including a special comment as either the first or second line
of the source file:

     #!/usr/bin/env python
     # -*- coding: latin-1 -*-

     u = 'abcdé'
     print(ord(u[-1]))

The syntax is inspired by Emacs's notation for specifying variables
local to a file.  Emacs supports many different variables, but Python
only supports 'coding'.  The ‘-*-’ symbols indicate to Emacs that the
comment is special; they have no significance to Python but are a
convention.  Python looks for ‘coding: name’ or ‘coding=name’ in the
comment.

If you don't include such a comment, the default encoding used will be
UTF-8 as already mentioned.  See also PEP 263(1) for more information.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0263/


File: python.info,  Node: Unicode Properties,  Next: Comparing Strings,  Prev: Unicode Literals in Python Source Code,  Up: Python's Unicode Support

9.12.2.4 Unicode Properties
...........................

The Unicode specification includes a database of information about code
points.  For each defined code point, the information includes the
character's name, its category, the numeric value if applicable (for
characters representing numeric concepts such as the Roman numerals,
fractions such as one-third and four-fifths, etc.).  There are also
display-related properties, such as how to use the code point in
bidirectional text.

The following program displays some information about several
characters, and prints the numeric value of one particular character:

     import unicodedata

     u = chr(233) + chr(0x0bf2) + chr(3972) + chr(6000) + chr(13231)

     for i, c in enumerate(u):
         print(i, '%04x' % ord(c), unicodedata.category(c), end=" ")
         print(unicodedata.name(c))

     # Get numeric value of second character
     print(unicodedata.numeric(u[1]))

When run, this prints:

     0 00e9 Ll LATIN SMALL LETTER E WITH ACUTE
     1 0bf2 No TAMIL NUMBER ONE THOUSAND
     2 0f84 Mn TIBETAN MARK HALANTA
     3 1770 Lo TAGBANWA LETTER SA
     4 33af So SQUARE RAD OVER S SQUARED
     1000.0

The category codes are abbreviations describing the nature of the
character.  These are grouped into categories such as "Letter",
"Number", "Punctuation", or "Symbol", which in turn are broken up into
subcategories.  To take the codes from the above output, ‘'Ll'’ means
'Letter, lowercase', ‘'No'’ means "Number, other", ‘'Mn'’ is "Mark,
nonspacing", and ‘'So'’ is "Symbol, other".  See the General Category
Values section of the Unicode Character Database documentation(1) for a
list of category codes.

   ---------- Footnotes ----------

   (1) https://www.unicode.org/reports/tr44/#General_Category_Values


File: python.info,  Node: Comparing Strings,  Next: Unicode Regular Expressions,  Prev: Unicode Properties,  Up: Python's Unicode Support

9.12.2.5 Comparing Strings
..........................

Unicode adds some complication to comparing strings, because the same
set of characters can be represented by different sequences of code
points.  For example, a letter like 'ê' can be represented as a single
code point U+00EA, or as U+0065 U+0302, which is the code point for 'e'
followed by a code point for 'COMBINING CIRCUMFLEX ACCENT'. These will
produce the same output when printed, but one is a string of length 1
and the other is of length 2.

One tool for a case-insensitive comparison is the *note casefold(): d7c.
string method that converts a string to a case-insensitive form
following an algorithm described by the Unicode Standard.  This
algorithm has special handling for characters such as the German letter
'ß' (code point U+00DF), which becomes the pair of lowercase letters
'ss'.

     >>> street = 'Gürzenichstraße'
     >>> street.casefold()
     'gürzenichstrasse'

A second tool is the *note unicodedata: ee. module's *note normalize():
679. function that converts strings to one of several normal forms,
where letters followed by a combining character are replaced with single
characters.  *note normalize(): 679. can be used to perform string
comparisons that won't falsely report inequality if two strings use
combining characters differently:

     import unicodedata

     def compare_strs(s1, s2):
         def NFD(s):
             return unicodedata.normalize('NFD', s)

         return NFD(s1) == NFD(s2)

     single_char = 'ê'
     multiple_chars = '\N{LATIN SMALL LETTER E}\N{COMBINING CIRCUMFLEX ACCENT}'
     print('length of first string=', len(single_char))
     print('length of second string=', len(multiple_chars))
     print(compare_strs(single_char, multiple_chars))

When run, this outputs:

     $ python compare-strs.py
     length of first string= 1
     length of second string= 2
     True

The first argument to the *note normalize(): 679. function is a string
giving the desired normalization form, which can be one of 'NFC',
'NFKC', 'NFD', and 'NFKD'.

The Unicode Standard also specifies how to do caseless comparisons:

     import unicodedata

     def compare_caseless(s1, s2):
         def NFD(s):
             return unicodedata.normalize('NFD', s)

         return NFD(NFD(s1).casefold()) == NFD(NFD(s2).casefold())

     # Example usage
     single_char = 'ê'
     multiple_chars = '\N{LATIN CAPITAL LETTER E}\N{COMBINING CIRCUMFLEX ACCENT}'

     print(compare_caseless(single_char, multiple_chars))

This will print ‘True’.  (Why is ‘NFD()’ invoked twice?  Because there
are a few characters that make *note casefold(): d7c. return a
non-normalized string, so the result needs to be normalized again.  See
section 3.13 of the Unicode Standard for a discussion and an example.)


File: python.info,  Node: Unicode Regular Expressions,  Next: References<4>,  Prev: Comparing Strings,  Up: Python's Unicode Support

9.12.2.6 Unicode Regular Expressions
....................................

The regular expressions supported by the *note re: a7. module can be
provided either as bytes or strings.  Some of the special character
sequences such as ‘\d’ and ‘\w’ have different meanings depending on
whether the pattern is supplied as bytes or a string.  For example, ‘\d’
will match the characters ‘[0-9]’ in bytes but in strings will match any
character that's in the ‘'Nd'’ category.

The string in this example has the number 57 written in both Thai and
Arabic numerals:

     import re
     p = re.compile(r'\d+')

     s = "Over \u0e55\u0e57 57 flavours"
     m = p.search(s)
     print(repr(m.group()))

When executed, ‘\d+’ will match the Thai numerals and print them out.
If you supply the *note re.ASCII: 5d3. flag to *note compile(): b7a,
‘\d+’ will match the substring "57" instead.

Similarly, ‘\w’ matches a wide variety of Unicode characters but only
‘[a-zA-Z0-9_]’ in bytes or if *note re.ASCII: 5d3. is supplied, and ‘\s’
will match either Unicode whitespace characters or ‘[ \t\n\r\f\v]’.


File: python.info,  Node: References<4>,  Prev: Unicode Regular Expressions,  Up: Python's Unicode Support

9.12.2.7 References
...................

Some good alternative discussions of Python's Unicode support are:

   * Processing Text Files in Python 3(1), by Nick Coghlan.

   * Pragmatic Unicode(2), a PyCon 2012 presentation by Ned Batchelder.

The *note str: 3f2. type is described in the Python library reference at
*note Text Sequence Type -- str: 1b03.

*note unicodedata: ee. 模組的文件。

*note codecs: 14. 模組的文件。

Marc-André Lemburg gave a presentation titled "Python and Unicode" (PDF
slides)(3) at EuroPython 2002.  The slides are an excellent overview of
the design of Python 2's Unicode features (where the Unicode string type
is called ‘unicode’ and literals start with ‘u’).

   ---------- Footnotes ----------

   (1) 
https://python-notes.curiousefficiency.org/en/latest/python3/text_file_processing.html

   (2) https://nedbatchelder.com/text/unipain.html

   (3) https://downloads.egenix.com/python/Unicode-EPC2002-Talk.pdf


File: python.info,  Node: Reading and Writing Unicode Data,  Next: 致謝<10>,  Prev: Python's Unicode Support,  Up: Unicode HOWTO

9.12.3 Reading and Writing Unicode Data
---------------------------------------

Once you've written some code that works with Unicode data, the next
problem is input/output.  How do you get Unicode strings into your
program, and how do you convert Unicode into a form suitable for storage
or transmission?

It's possible that you may not need to do anything depending on your
input sources and output destinations; you should check whether the
libraries used in your application support Unicode natively.  XML
parsers often return Unicode data, for example.  Many relational
databases also support Unicode-valued columns and can return Unicode
values from an SQL query.

Unicode data is usually converted to a particular encoding before it
gets written to disk or sent over a socket.  It's possible to do all the
work yourself: open a file, read an 8-bit bytes object from it, and
convert the bytes with ‘bytes.decode(encoding)’.  However, the manual
approach is not recommended.

One problem is the multi-byte nature of encodings; one Unicode character
can be represented by several bytes.  If you want to read the file in
arbitrary-sized chunks (say, 1024 or 4096 bytes), you need to write
error-handling code to catch the case where only part of the bytes
encoding a single Unicode character are read at the end of a chunk.  One
solution would be to read the entire file into memory and then perform
the decoding, but that prevents you from working with files that are
extremely large; if you need to read a 2 GiB file, you need 2 GiB of
RAM.  (More, really, since for at least a moment you'd need to have both
the encoded string and its Unicode version in memory.)

The solution would be to use the low-level decoding interface to catch
the case of partial coding sequences.  The work of implementing this has
already been done for you: the built-in *note open(): 4c0. function can
return a file-like object that assumes the file's contents are in a
specified encoding and accepts Unicode parameters for methods such as
*note read(): 1b89. and *note write(): 1b78.  This works through *note
open(): 4c0.'s 'encoding' and 'errors' parameters which are interpreted
just like those in *note str.encode(): 87a. and *note bytes.decode():
87b.

Reading Unicode from a file is therefore simple:

     with open('unicode.txt', encoding='utf-8') as f:
         for line in f:
             print(repr(line))

It's also possible to open files in update mode, allowing both reading
and writing:

     with open('test', encoding='utf-8', mode='w+') as f:
         f.write('\u4500 blah blah blah\n')
         f.seek(0)
         print(repr(f.readline()[:1]))

The Unicode character ‘U+FEFF’ is used as a byte-order mark (BOM), and
is often written as the first character of a file in order to assist
with autodetection of the file's byte ordering.  Some encodings, such as
UTF-16, expect a BOM to be present at the start of a file; when such an
encoding is used, the BOM will be automatically written as the first
character and will be silently dropped when the file is read.  There are
variants of these encodings, such as 'utf-16-le' and 'utf-16-be' for
little-endian and big-endian encodings, that specify one particular byte
ordering and don't skip the BOM.

In some areas, it is also convention to use a "BOM" at the start of
UTF-8 encoded files; the name is misleading since UTF-8 is not
byte-order dependent.  The mark simply announces that the file is
encoded in UTF-8.  For reading such files, use the 'utf-8-sig' codec to
automatically skip the mark if present.

* Menu:

* Unicode filenames::
* Tips for Writing Unicode-aware Programs::
* References: References<5>.


File: python.info,  Node: Unicode filenames,  Next: Tips for Writing Unicode-aware Programs,  Up: Reading and Writing Unicode Data

9.12.3.1 Unicode filenames
..........................

Most of the operating systems in common use today support filenames that
contain arbitrary Unicode characters.  Usually this is implemented by
converting the Unicode string into some encoding that varies depending
on the system.  Today Python is converging on using UTF-8: Python on
MacOS has used UTF-8 for several versions, and Python 3.6 switched to
using UTF-8 on Windows as well.  On Unix systems, there will only be a
*note filesystem encoding: 4e0.  if you've set the ‘LANG’ or ‘LC_CTYPE’
environment variables; if you haven't, the default encoding is again
UTF-8.

The *note sys.getfilesystemencoding(): c00. function returns the
encoding to use on your current system, in case you want to do the
encoding manually, but there's not much reason to bother.  When opening
a file for reading or writing, you can usually just provide the Unicode
string as the filename, and it will be automatically converted to the
right encoding for you:

     filename = 'filename\u4500abc'
     with open(filename, 'w') as f:
         f.write('blah\n')

Functions in the *note os: 91. module such as *note os.stat(): 448. will
also accept Unicode filenames.

The *note os.listdir(): 1092. function returns filenames, which raises
an issue: should it return the Unicode version of filenames, or should
it return bytes containing the encoded versions?  *note os.listdir():
1092. can do both, depending on whether you provided the directory path
as bytes or a Unicode string.  If you pass a Unicode string as the path,
filenames will be decoded using the filesystem's encoding and a list of
Unicode strings will be returned, while passing a byte path will return
the filenames as bytes.  For example, assuming the default *note
filesystem encoding: 4e0. is UTF-8, running the following program:

     fn = 'filename\u4500abc'
     f = open(fn, 'w')
     f.close()

     import os
     print(os.listdir(b'.'))
     print(os.listdir('.'))

will produce the following output:

     $ python listdir-test.py
     [b'filename\xe4\x94\x80abc', ...]
     ['filename\u4500abc', ...]

The first list contains UTF-8-encoded filenames, and the second list
contains the Unicode versions.

Note that on most occasions, you should can just stick with using
Unicode with these APIs.  The bytes APIs should only be used on systems
where undecodable file names can be present; that's pretty much only
Unix systems now.


File: python.info,  Node: Tips for Writing Unicode-aware Programs,  Next: References<5>,  Prev: Unicode filenames,  Up: Reading and Writing Unicode Data

9.12.3.2 Tips for Writing Unicode-aware Programs
................................................

This section provides some suggestions on writing software that deals
with Unicode.

The most important tip is:

     Software should only work with Unicode strings internally, decoding
     the input data as soon as possible and encoding the output only at
     the end.

If you attempt to write processing functions that accept both Unicode
and byte strings, you will find your program vulnerable to bugs wherever
you combine the two different kinds of strings.  There is no automatic
encoding or decoding: if you do e.g.  ‘str + bytes’, a *note TypeError:
4dd. will be raised.

When using data coming from a web browser or some other untrusted
source, a common technique is to check for illegal characters in a
string before using the string in a generated command line or storing it
in a database.  If you're doing this, be careful to check the decoded
string, not the encoded bytes data; some encodings may have interesting
properties, such as not being bijective or not being fully
ASCII-compatible.  This is especially true if the input data also
specifies the encoding, since the attacker can then choose a clever way
to hide malicious text in the encoded bytestream.

* Menu:

* Converting Between File Encodings::
* Files in an Unknown Encoding::


File: python.info,  Node: Converting Between File Encodings,  Next: Files in an Unknown Encoding,  Up: Tips for Writing Unicode-aware Programs

9.12.3.3 Converting Between File Encodings
..........................................

The *note StreamRecoder: 18f6. class can transparently convert between
encodings, taking a stream that returns data in encoding #1 and behaving
like a stream returning data in encoding #2.

For example, if you have an input file 'f' that's in Latin-1, you can
wrap it with a *note StreamRecoder: 18f6. to return bytes encoded in
UTF-8:

     new_f = codecs.StreamRecoder(f,
         # en/decoder: used by read() to encode its results and
         # by write() to decode its input.
         codecs.getencoder('utf-8'), codecs.getdecoder('utf-8'),

         # reader/writer: used to read and write to the stream.
         codecs.getreader('latin-1'), codecs.getwriter('latin-1') )


File: python.info,  Node: Files in an Unknown Encoding,  Prev: Converting Between File Encodings,  Up: Tips for Writing Unicode-aware Programs

9.12.3.4 Files in an Unknown Encoding
.....................................

What can you do if you need to make a change to a file, but don't know
the file's encoding?  If you know the encoding is ASCII-compatible and
only want to examine or modify the ASCII parts, you can open the file
with the ‘surrogateescape’ error handler:

     with open(fname, 'r', encoding="ascii", errors="surrogateescape") as f:
         data = f.read()

     # make changes to the string 'data'

     with open(fname + '.new', 'w',
               encoding="ascii", errors="surrogateescape") as f:
         f.write(data)

The ‘surrogateescape’ error handler will decode any non-ASCII bytes as
code points in a special range running from U+DC80 to U+DCFF. These code
points will then turn back into the same bytes when the
‘surrogateescape’ error handler is used to encode the data and write it
back out.


File: python.info,  Node: References<5>,  Prev: Tips for Writing Unicode-aware Programs,  Up: Reading and Writing Unicode Data

9.12.3.5 References
...................

One section of Mastering Python 3 Input/Output(1), a PyCon 2010 talk by
David Beazley, discusses text processing and binary data handling.

The PDF slides for Marc-André Lemburg's presentation "Writing
Unicode-aware Applications in Python"(2) discuss questions of character
encodings as well as how to internationalize and localize an
application.  These slides cover Python 2.x only.

The Guts of Unicode in Python(3) is a PyCon 2013 talk by Benjamin
Peterson that discusses the internal Unicode representation in Python
3.3.

   ---------- Footnotes ----------

   (1) https://pyvideo.org/video/289/pycon-2010-mastering-python-3-i-o

   (2) 
https://downloads.egenix.com/python/LSM2005-Developing-Unicode-aware-applications-in-Python.pdf

   (3) https://pyvideo.org/video/1768/the-guts-of-unicode-in-python


File: python.info,  Node: 致謝<10>,  Prev: Reading and Writing Unicode Data,  Up: Unicode HOWTO

9.12.4 致謝
-----------

The initial draft of this document was written by Andrew Kuchling.  It
has since been revised further by Alexander Belopolsky, Georg Brandl,
Andrew Kuchling, and Ezio Melotti.

Thanks to the following people who have noted errors or offered
suggestions on this article: Éric Araujo, Nicholas Bastin, Nick Coghlan,
Marius Gedminas, Kent Johnson, Ken Krugler, Marc-André Lemburg, Martin
von Löwis, Terry J. Reedy, Serhiy Storchaka, Eryk Sun, Chad Whitacre,
Graham Wideman.


File: python.info,  Node: 如何使用 urllib 套件取得網路資源,  Next: Argparse 教學,  Prev: Unicode HOWTO,  Up: Python 如何達成任務

9.13 如何使用 urllib 套件取得網路資源
=====================================


作者: Michael Foord(1)

* Menu:

* 簡介: 簡介<13>.
* 從 URL 取得資源::
* Handling Exceptions::
* info and geturl::
* Openers and Handlers::
* Basic Authentication::
* Proxies::
* Sockets and Layers::
* 註解: 註解<2>.

   ---------- Footnotes ----------

   (1) https://agileabstractions.com/


File: python.info,  Node: 簡介<13>,  Next: 從 URL 取得資源,  Up: 如何使用 urllib 套件取得網路資源

9.13.1 簡介
-----------

Related Articles
................

以下這些與 Python 有關的文章說不定能幫到你:

   * Basic Authentication(1)

          以 Python 為例的 'Basic Authentication' 教學。

'urllib.request' 是一個用來從 URLs (Uniform Resource Locators) 取得資料
的Python模組。它提供一個了非常簡單的介面能接受多種不同的協議，'urlopen'
函式。也提供了較複雜的介面用於處理一些常見的狀況，例如：基本的
authentication、cookies、proxies 等等，這些都可以由 handler 或 opener 物
件操作。

urllib.request supports fetching URLs for many "URL schemes" (identified
by the string before the ‘":"’ in URL - for example ‘"ftp"’ is the URL
scheme of ‘"ftp://python.org/"’) using their associated network
protocols (e.g.  FTP, HTTP). This tutorial focuses on the most common
case, HTTP.

一般情形下 'urlopen' 是非常容易使用的，但當你遇到錯誤或者較複雜的情況下
，你可能需要對超文本協議 HyperText Transfer Protocol 有一定的了解。最完
整且具參考價值的是 RFC 2616(2)，不過它是一份技術文件並不容易閱讀，以下的
教學會提供足夠的 HTTP 知識來幫助你使用 'urllib'。這份教學並非要取代
*note urllib.request: f4. 這份文件，你還是會需要它。

   ---------- Footnotes ----------

   (1) 
https://web.archive.org/web/20201215133350/http://www.voidspace.org.uk/python/articles/authentication.shtml

   (2) https://datatracker.ietf.org/doc/html/rfc2616.html


File: python.info,  Node: 從 URL 取得資源,  Next: Handling Exceptions,  Prev: 簡介<13>,  Up: 如何使用 urllib 套件取得網路資源

9.13.2 從 URL 取得資源
----------------------

以下是使用 urllib.request 最簡單的方法:

     import urllib.request
     with urllib.request.urlopen('http://python.org/') as response:
        html = response.read()

If you wish to retrieve a resource via URL and store it in a temporary
location, you can do so via the *note shutil.copyfileobj(): a00. and
*note tempfile.NamedTemporaryFile(): 46d. functions:

     import shutil
     import tempfile
     import urllib.request

     with urllib.request.urlopen('http://python.org/') as response:
         with tempfile.NamedTemporaryFile(delete=False) as tmp_file:
             shutil.copyfileobj(response, tmp_file)

     with open(tmp_file.name) as html:
         pass

Many uses of urllib will be that simple (note that instead of an 'http:'
URL we could have used a URL starting with 'ftp:', 'file:', etc.).
However, it's the purpose of this tutorial to explain the more
complicated cases, concentrating on HTTP.

HTTP is based on requests and responses - the client makes requests and
servers send responses.  urllib.request mirrors this with a ‘Request’
object which represents the HTTP request you are making.  In its
simplest form you create a Request object that specifies the URL you
want to fetch.  Calling ‘urlopen’ with this Request object returns a
response object for the URL requested.  This response is a file-like
object, which means you can for example call ‘.read()’ on the response:

     import urllib.request

     req = urllib.request.Request('http://python.org/')
     with urllib.request.urlopen(req) as response:
        the_page = response.read()

Note that urllib.request makes use of the same Request interface to
handle all URL schemes.  For example, you can make an FTP request like
so:

     req = urllib.request.Request('ftp://example.com/')

In the case of HTTP, there are two extra things that Request objects
allow you to do: First, you can pass data to be sent to the server.
Second, you can pass extra information ("metadata") 'about' the data or
about the request itself, to the server - this information is sent as
HTTP "headers".  Let's look at each of these in turn.

* Menu:

* Data::
* Headers::


File: python.info,  Node: Data,  Next: Headers,  Up: 從 URL 取得資源

9.13.2.1 Data
.............

Sometimes you want to send data to a URL (often the URL will refer to a
CGI (Common Gateway Interface) script or other web application).  With
HTTP, this is often done using what's known as a 'POST' request.  This
is often what your browser does when you submit a HTML form that you
filled in on the web.  Not all POSTs have to come from forms: you can
use a POST to transmit arbitrary data to your own application.  In the
common case of HTML forms, the data needs to be encoded in a standard
way, and then passed to the Request object as the ‘data’ argument.  The
encoding is done using a function from the *note urllib.parse: f3.
library.

     import urllib.parse
     import urllib.request

     url = 'http://www.someserver.com/cgi-bin/register.cgi'
     values = {'name' : 'Michael Foord',
               'location' : 'Northampton',
               'language' : 'Python' }

     data = urllib.parse.urlencode(values)
     data = data.encode('ascii') # data should be bytes
     req = urllib.request.Request(url, data)
     with urllib.request.urlopen(req) as response:
        the_page = response.read()

Note that other encodings are sometimes required (e.g.  for file upload
from HTML forms - see HTML Specification, Form Submission(1) for more
details).

If you do not pass the ‘data’ argument, urllib uses a 'GET' request.
One way in which GET and POST requests differ is that POST requests
often have "side-effects": they change the state of the system in some
way (for example by placing an order with the website for a
hundredweight of tinned spam to be delivered to your door).  Though the
HTTP standard makes it clear that POSTs are intended to 'always' cause
side-effects, and GET requests 'never' to cause side-effects, nothing
prevents a GET request from having side-effects, nor a POST requests
from having no side-effects.  Data can also be passed in an HTTP GET
request by encoding it in the URL itself.

This is done as follows:

     >>> import urllib.request
     >>> import urllib.parse
     >>> data = {}
     >>> data['name'] = 'Somebody Here'
     >>> data['location'] = 'Northampton'
     >>> data['language'] = 'Python'
     >>> url_values = urllib.parse.urlencode(data)
     >>> print(url_values)  # The order may differ from below.
     name=Somebody+Here&language=Python&location=Northampton
     >>> url = 'http://www.example.com/example.cgi'
     >>> full_url = url + '?' + url_values
     >>> data = urllib.request.urlopen(full_url)

Notice that the full URL is created by adding a ‘?’ to the URL, followed
by the encoded values.

   ---------- Footnotes ----------

   (1) https://www.w3.org/TR/REC-html40/interact/forms.html#h-17.13


File: python.info,  Node: Headers,  Prev: Data,  Up: 從 URL 取得資源

9.13.2.2 Headers
................

We'll discuss here one particular HTTP header, to illustrate how to add
headers to your HTTP request.

Some websites (1) dislike being browsed by programs, or send different
versions to different browsers (2).  By default urllib identifies itself
as ‘Python-urllib/x.y’ (where ‘x’ and ‘y’ are the major and minor
version numbers of the Python release, e.g.  ‘Python-urllib/2.5’), which
may confuse the site, or just plain not work.  The way a browser
identifies itself is through the ‘User-Agent’ header (3).  When you
create a Request object you can pass a dictionary of headers in.  The
following example makes the same request as above, but identifies itself
as a version of Internet Explorer (4).

     import urllib.parse
     import urllib.request

     url = 'http://www.someserver.com/cgi-bin/register.cgi'
     user_agent = 'Mozilla/5.0 (Windows NT 6.1; Win64; x64)'
     values = {'name': 'Michael Foord',
               'location': 'Northampton',
               'language': 'Python' }
     headers = {'User-Agent': user_agent}

     data = urllib.parse.urlencode(values)
     data = data.encode('ascii')
     req = urllib.request.Request(url, data, headers)
     with urllib.request.urlopen(req) as response:
        the_page = response.read()

The response also has two useful methods.  See the section on *note info
and geturl: 4de2. which comes after we have a look at what happens when
things go wrong.

   ---------- Footnotes ----------

   (1) Google for example.

   (2) Browser sniffing is a very bad practice for website design -
building sites using web standards is much more sensible.  Unfortunately
a lot of sites still send different versions to different browsers.

   (3) The user agent for MSIE 6 is ''Mozilla/4.0 (compatible; MSIE 6.0;
Windows NT 5.1; SV1; .NET CLR 1.1.4322)"

   (4) For details of more HTTP request headers, see Quick Reference to
HTTP Headers (https://jkorpela.fi/http.html).


File: python.info,  Node: Handling Exceptions,  Next: info and geturl,  Prev: 從 URL 取得資源,  Up: 如何使用 urllib 套件取得網路資源

9.13.3 Handling Exceptions
--------------------------

'urlopen' raises *note URLError: 37bf. when it cannot handle a response
(though as usual with Python APIs, built-in exceptions such as *note
ValueError: 1e7, *note TypeError: 4dd. etc.  may also be raised).

*note HTTPError: f81. is the subclass of *note URLError: 37bf. raised in
the specific case of HTTP URLs.

The exception classes are exported from the *note urllib.error: f2.
module.

* Menu:

* URLError::
* HTTPError::
* Wrapping it Up::


File: python.info,  Node: URLError,  Next: HTTPError,  Up: Handling Exceptions

9.13.3.1 URLError
.................

Often, URLError is raised because there is no network connection (no
route to the specified server), or the specified server doesn't exist.
In this case, the exception raised will have a 'reason' attribute, which
is a tuple containing an error code and a text error message.

例如：

     >>> req = urllib.request.Request('http://www.pretend_server.org')
     >>> try: urllib.request.urlopen(req)
     ... except urllib.error.URLError as e:
     ...     print(e.reason)
     ...
     (4, 'getaddrinfo failed')


File: python.info,  Node: HTTPError,  Next: Wrapping it Up,  Prev: URLError,  Up: Handling Exceptions

9.13.3.2 HTTPError
..................

Every HTTP response from the server contains a numeric "status code".
Sometimes the status code indicates that the server is unable to fulfil
the request.  The default handlers will handle some of these responses
for you (for example, if the response is a "redirection" that requests
the client fetch the document from a different URL, urllib will handle
that for you).  For those it can't handle, urlopen will raise an *note
HTTPError: f81.  Typical errors include '404' (page not found), '403'
(request forbidden), and '401' (authentication required).

See section 10 of RFC 2616(1) for a reference on all the HTTP error
codes.

The *note HTTPError: f81. instance raised will have an integer 'code'
attribute, which corresponds to the error sent by the server.

* Menu:

* Error Codes::

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2616.html


File: python.info,  Node: Error Codes,  Up: HTTPError

9.13.3.3 Error Codes
....................

Because the default handlers handle redirects (codes in the 300 range),
and codes in the 100-299 range indicate success, you will usually only
see error codes in the 400-599 range.

*note http.server.BaseHTTPRequestHandler.responses: 385f. is a useful
dictionary of response codes in that shows all the response codes used
by RFC 2616(1).  The dictionary is reproduced here for convenience

     # Table mapping response codes to messages; entries have the
     # form {code: (shortmessage, longmessage)}.
     responses = {
         100: ('Continue', 'Request received, please continue'),
         101: ('Switching Protocols',
               'Switching to new protocol; obey Upgrade header'),

         200: ('OK', 'Request fulfilled, document follows'),
         201: ('Created', 'Document created, URL follows'),
         202: ('Accepted',
               'Request accepted, processing continues off-line'),
         203: ('Non-Authoritative Information', 'Request fulfilled from cache'),
         204: ('No Content', 'Request fulfilled, nothing follows'),
         205: ('Reset Content', 'Clear input form for further input.'),
         206: ('Partial Content', 'Partial content follows.'),

         300: ('Multiple Choices',
               'Object has several resources -- see URI list'),
         301: ('Moved Permanently', 'Object moved permanently -- see URI list'),
         302: ('Found', 'Object moved temporarily -- see URI list'),
         303: ('See Other', 'Object moved -- see Method and URL list'),
         304: ('Not Modified',
               'Document has not changed since given time'),
         305: ('Use Proxy',
               'You must use proxy specified in Location to access this '
               'resource.'),
         307: ('Temporary Redirect',
               'Object moved temporarily -- see URI list'),

         400: ('Bad Request',
               'Bad request syntax or unsupported method'),
         401: ('Unauthorized',
               'No permission -- see authorization schemes'),
         402: ('Payment Required',
               'No payment -- see charging schemes'),
         403: ('Forbidden',
               'Request forbidden -- authorization will not help'),
         404: ('Not Found', 'Nothing matches the given URI'),
         405: ('Method Not Allowed',
               'Specified method is invalid for this server.'),
         406: ('Not Acceptable', 'URI not available in preferred format.'),
         407: ('Proxy Authentication Required', 'You must authenticate with '
               'this proxy before proceeding.'),
         408: ('Request Timeout', 'Request timed out; try again later.'),
         409: ('Conflict', 'Request conflict.'),
         410: ('Gone',
               'URI no longer exists and has been permanently removed.'),
         411: ('Length Required', 'Client must specify Content-Length.'),
         412: ('Precondition Failed', 'Precondition in headers is false.'),
         413: ('Request Entity Too Large', 'Entity is too large.'),
         414: ('Request-URI Too Long', 'URI is too long.'),
         415: ('Unsupported Media Type', 'Entity body in unsupported format.'),
         416: ('Requested Range Not Satisfiable',
               'Cannot satisfy request range.'),
         417: ('Expectation Failed',
               'Expect condition could not be satisfied.'),

         500: ('Internal Server Error', 'Server got itself in trouble'),
         501: ('Not Implemented',
               'Server does not support this operation'),
         502: ('Bad Gateway', 'Invalid responses from another server/proxy.'),
         503: ('Service Unavailable',
               'The server cannot process the request due to a high load'),
         504: ('Gateway Timeout',
               'The gateway server did not receive a timely response'),
         505: ('HTTP Version Not Supported', 'Cannot fulfill request.'),
         }

When an error is raised the server responds by returning an HTTP error
code 'and' an error page.  You can use the *note HTTPError: f81.
instance as a response on the page returned.  This means that as well as
the code attribute, it also has read, geturl, and info, methods as
returned by the ‘urllib.response’ module:

     >>> req = urllib.request.Request('http://www.python.org/fish.html')
     >>> try:
     ...     urllib.request.urlopen(req)
     ... except urllib.error.HTTPError as e:
     ...     print(e.code)
     ...     print(e.read())
     ...
     404
     b'<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
       "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">\n\n\n<html
       ...
       <title>Page Not Found</title>\n
       ...

   ---------- Footnotes ----------

   (1) https://datatracker.ietf.org/doc/html/rfc2616.html


File: python.info,  Node: Wrapping it Up,  Prev: HTTPError,  Up: Handling Exceptions

9.13.3.4 Wrapping it Up
.......................

So if you want to be prepared for *note HTTPError: f81. 'or' *note
URLError: 37bf. there are two basic approaches.  I prefer the second
approach.

* Menu:

* Number 1::
* Number 2::


File: python.info,  Node: Number 1,  Next: Number 2,  Up: Wrapping it Up

9.13.3.5 Number 1
.................

     from urllib.request import Request, urlopen
     from urllib.error import URLError, HTTPError
     req = Request(someurl)
     try:
         response = urlopen(req)
     except HTTPError as e:
         print('The server couldn\'t fulfill the request.')
         print('Error code: ', e.code)
     except URLError as e:
         print('We failed to reach a server.')
         print('Reason: ', e.reason)
     else:
         # everything is fine

     備註: The ‘except HTTPError’ 'must' come first, otherwise ‘except
     URLError’ will 'also' catch an *note HTTPError: f81.


File: python.info,  Node: Number 2,  Prev: Number 1,  Up: Wrapping it Up

9.13.3.6 Number 2
.................

     from urllib.request import Request, urlopen
     from urllib.error import URLError
     req = Request(someurl)
     try:
         response = urlopen(req)
     except URLError as e:
         if hasattr(e, 'reason'):
             print('We failed to reach a server.')
             print('Reason: ', e.reason)
         elif hasattr(e, 'code'):
             print('The server couldn\'t fulfill the request.')
             print('Error code: ', e.code)
     else:
         # everything is fine


File: python.info,  Node: info and geturl,  Next: Openers and Handlers,  Prev: Handling Exceptions,  Up: 如何使用 urllib 套件取得網路資源

9.13.4 info and geturl
----------------------

The response returned by urlopen (or the *note HTTPError: f81. instance)
has two useful methods ‘info()’ and ‘geturl()’ and is defined in the
module *note urllib.response: f5.

   * 'geturl' - this returns the real URL of the page fetched.  This is
     useful because ‘urlopen’ (or the opener object used) may have
     followed a redirect.  The URL of the page fetched may not be the
     same as the URL requested.

   * 'info' - this returns a dictionary-like object that describes the
     page fetched, particularly the headers sent by the server.  It is
     currently an *note http.client.HTTPMessage: 3876. instance.

Typical headers include 'Content-length', 'Content-type', and so on.
See the Quick Reference to HTTP Headers(1) for a useful listing of HTTP
headers with brief explanations of their meaning and use.

   ---------- Footnotes ----------

   (1) https://jkorpela.fi/http.html


File: python.info,  Node: Openers and Handlers,  Next: Basic Authentication,  Prev: info and geturl,  Up: 如何使用 urllib 套件取得網路資源

9.13.5 Openers and Handlers
---------------------------

When you fetch a URL you use an opener (an instance of the perhaps
confusingly named *note urllib.request.OpenerDirector: 37c0.).  Normally
we have been using the default opener - via ‘urlopen’ - but you can
create custom openers.  Openers use handlers.  All the "heavy lifting"
is done by the handlers.  Each handler knows how to open URLs for a
particular URL scheme (http, ftp, etc.), or how to handle an aspect of
URL opening, for example HTTP redirections or HTTP cookies.

You will want to create openers if you want to fetch URLs with specific
handlers installed, for example to get an opener that handles cookies,
or to get an opener that does not handle redirections.

To create an opener, instantiate an ‘OpenerDirector’, and then call
‘.add_handler(some_handler_instance)’ repeatedly.

Alternatively, you can use ‘build_opener’, which is a convenience
function for creating opener objects with a single function call.
‘build_opener’ adds several handlers by default, but provides a quick
way to add more and/or override the default handlers.

Other sorts of handlers you might want to can handle proxies,
authentication, and other common but slightly specialised situations.

‘install_opener’ can be used to make an ‘opener’ object the (global)
default opener.  This means that calls to ‘urlopen’ will use the opener
you have installed.

Opener objects have an ‘open’ method, which can be called directly to
fetch urls in the same way as the ‘urlopen’ function: there's no need to
call ‘install_opener’, except as a convenience.


File: python.info,  Node: Basic Authentication,  Next: Proxies,  Prev: Openers and Handlers,  Up: 如何使用 urllib 套件取得網路資源

9.13.6 Basic Authentication
---------------------------

To illustrate creating and installing a handler we will use the
‘HTTPBasicAuthHandler’.  For a more detailed discussion of this subject
- including an explanation of how Basic Authentication works - see the
Basic Authentication Tutorial(1).

When authentication is required, the server sends a header (as well as
the 401 error code) requesting authentication.  This specifies the
authentication scheme and a 'realm'.  The header looks like:
‘WWW-Authenticate: SCHEME realm="REALM"’.

例如

     WWW-Authenticate: Basic realm="cPanel Users"

The client should then retry the request with the appropriate name and
password for the realm included as a header in the request.  This is
'basic authentication'.  In order to simplify this process we can create
an instance of ‘HTTPBasicAuthHandler’ and an opener to use this handler.

The ‘HTTPBasicAuthHandler’ uses an object called a password manager to
handle the mapping of URLs and realms to passwords and usernames.  If
you know what the realm is (from the authentication header sent by the
server), then you can use a ‘HTTPPasswordMgr’.  Frequently one doesn't
care what the realm is.  In that case, it is convenient to use
‘HTTPPasswordMgrWithDefaultRealm’.  This allows you to specify a default
username and password for a URL. This will be supplied in the absence of
you providing an alternative combination for a specific realm.  We
indicate this by providing ‘None’ as the realm argument to the
‘add_password’ method.

The top-level URL is the first URL that requires authentication.  URLs
"deeper" than the URL you pass to .add_password() will also match.

     # create a password manager
     password_mgr = urllib.request.HTTPPasswordMgrWithDefaultRealm()

     # Add the username and password.
     # If we knew the realm, we could use it instead of None.
     top_level_url = "http://example.com/foo/"
     password_mgr.add_password(None, top_level_url, username, password)

     handler = urllib.request.HTTPBasicAuthHandler(password_mgr)

     # create "opener" (OpenerDirector instance)
     opener = urllib.request.build_opener(handler)

     # use the opener to fetch a URL
     opener.open(a_url)

     # Install the opener.
     # Now all calls to urllib.request.urlopen use our opener.
     urllib.request.install_opener(opener)

     備註: In the above example we only supplied our
     ‘HTTPBasicAuthHandler’ to ‘build_opener’.  By default openers have
     the handlers for normal situations - ‘ProxyHandler’ (if a proxy
     setting such as an ‘http_proxy’ environment variable is set),
     ‘UnknownHandler’, ‘HTTPHandler’, ‘HTTPDefaultErrorHandler’,
     ‘HTTPRedirectHandler’, ‘FTPHandler’, ‘FileHandler’, ‘DataHandler’,
     ‘HTTPErrorProcessor’.

‘top_level_url’ is in fact 'either' a full URL (including the 'http:'
scheme component and the hostname and optionally the port number) e.g.
‘"http://example.com/"’ 'or' an "authority" (i.e.  the hostname,
optionally including the port number) e.g.  ‘"example.com"’ or
‘"example.com:8080"’ (the latter example includes a port number).  The
authority, if present, must NOT contain the "userinfo" component - for
example ‘"joe:password@example.com"’ is not correct.

   ---------- Footnotes ----------

   (1) 
https://web.archive.org/web/20201215133350/http://www.voidspace.org.uk/python/articles/authentication.shtml


File: python.info,  Node: Proxies,  Next: Sockets and Layers,  Prev: Basic Authentication,  Up: 如何使用 urllib 套件取得網路資源

9.13.7 Proxies
--------------

'urllib' will auto-detect your proxy settings and use those.  This is
through the ‘ProxyHandler’, which is part of the normal handler chain
when a proxy setting is detected.  Normally that's a good thing, but
there are occasions when it may not be helpful (1).  One way to do this
is to setup our own ‘ProxyHandler’, with no proxies defined.  This is
done using similar steps to setting up a Basic Authentication(2)
handler:

     >>> proxy_support = urllib.request.ProxyHandler({})
     >>> opener = urllib.request.build_opener(proxy_support)
     >>> urllib.request.install_opener(opener)

     備註: Currently ‘urllib.request’ 'does not' support fetching of
     ‘https’ locations through a proxy.  However, this can be enabled by
     extending urllib.request as shown in the recipe (3).

     備註: ‘HTTP_PROXY’ will be ignored if a variable ‘REQUEST_METHOD’
     is set; see the documentation on *note getproxies(): 37bc.

   ---------- Footnotes ----------

   (1) In my case I have to use a proxy to access the internet at work.
If you attempt to fetch 'localhost' URLs through this proxy it blocks
them.  IE is set to use the proxy, which urllib picks up on.  In order
to test scripts with a localhost server, I have to prevent urllib from
using the proxy.

   (2) 
https://web.archive.org/web/20201215133350/http://www.voidspace.org.uk/python/articles/authentication.shtml

   (3) urllib opener for SSL proxy (CONNECT method): ASPN Cookbook
Recipe
(https://code.activestate.com/recipes/456195-urrlib2-opener-for-ssl-proxy-connect-method/).


File: python.info,  Node: Sockets and Layers,  Next: 註解<2>,  Prev: Proxies,  Up: 如何使用 urllib 套件取得網路資源

9.13.8 Sockets and Layers
-------------------------

The Python support for fetching resources from the web is layered.
urllib uses the *note http.client: 65. library, which in turn uses the
socket library.

As of Python 2.3 you can specify how long a socket should wait for a
response before timing out.  This can be useful in applications which
have to fetch web pages.  By default the socket module has 'no timeout'
and can hang.  Currently, the socket timeout is not exposed at the
http.client or urllib.request levels.  However, you can set the default
timeout globally for all sockets using

     import socket
     import urllib.request

     # timeout in seconds
     timeout = 10
     socket.setdefaulttimeout(timeout)

     # this call to urllib.request.urlopen now uses the default timeout
     # we have set in the socket module
     req = urllib.request.Request('http://www.voidspace.org.uk')
     response = urllib.request.urlopen(req)

__________________________________________________________________


File: python.info,  Node: 註解<2>,  Prev: Sockets and Layers,  Up: 如何使用 urllib 套件取得網路資源

9.13.9 註解
-----------

This document was reviewed and revised by John Lee.


File: python.info,  Node: Argparse 教學,  Next: ipaddress 模組介紹,  Prev: 如何使用 urllib 套件取得網路資源,  Up: Python 如何達成任務

9.14 Argparse 教學
==================


作者: Tshepang Mbambo

本教學旨在簡要介紹 *note argparse: 5. 這個 Python 標準函式庫中推薦的命令
列剖析模組。

     備註: 另外還有兩個模組可以完成相同的任務，即 *note getopt: 57.（相
     當於 C 語言中的 ‘getopt()’）和已棄用的 *note optparse: 90.。另請注
     意，*note argparse: 5. 是基於 *note optparse: 90. 的，因此在用法上
     非常相似。

* Menu:

* 概念::
* 基本用法: 基本用法<4>.
* 位置引數的介紹::
* 可選引數的介紹::
* 組合位置引數和可選引數::
* 更進階一點::
* 如何翻譯 argparse 輸出::
* 結論::


File: python.info,  Node: 概念,  Next: 基本用法<4>,  Up: Argparse 教學

9.14.1 概念
-----------

讓我們透過使用 ‘ls’ 指令來展示我們將在本介紹教學中探索的功能類型：

     $ ls
     cpython  devguide  prog.py  pypy  rm-unused-function.patch
     $ ls pypy
     ctypes_configure  demo  dotviewer  include  lib_pypy  lib-python ...
     $ ls -l
     total 20
     drwxr-xr-x 19 wena wena 4096 Feb 18 18:51 cpython
     drwxr-xr-x  4 wena wena 4096 Feb  8 12:04 devguide
     -rwxr-xr-x  1 wena wena  535 Feb 19 00:05 prog.py
     drwxr-xr-x 14 wena wena 4096 Feb  7 00:59 pypy
     -rw-r--r--  1 wena wena  741 Feb 18 01:01 rm-unused-function.patch
     $ ls --help
     Usage: ls [OPTION]... [FILE]...
     List information about the FILEs (the current directory by default).
     Sort entries alphabetically if none of -cftuvSUX nor --sort is specified.
     ...

我們可以從這四個命令中學到一些概念：

   * ‘ls’ 命令即便在沒有任何選項的情況下執行仍非常有用。它預設顯示目前目
     錄的內容。

   * 如果我們想要看到比它預設提供更多的內容，我們也需要多告訴它一點。在
     本例中，我們希望它顯示不同的目錄 ‘pypy’，我們做的是指定所謂的位置引
     數。之所以如此命名是因為程式應該只根據該值在命令列中出現的位置來知
     道如何處理該值。這個概念與 ‘cp’ 這樣的指令更相關，其最基本的用法是
     ‘cp SRC DEST’。第一個是'你想要複製的位置'，第二個是'你想要複製過去
     的位置'。

   * 現在假設我們想要改變程式的行為。在我們的範例中，我們顯示每個檔案的
     更多資訊，而不僅是顯示檔案名稱。在這種情況下，‘-l’ 被稱為可選引數。

   * 這是幫助文字的片段。它非常有用，因為當你遇到以前從未使用過的程式時
     ，只需閱讀其幫助文字即可了解它的工作原理。


File: python.info,  Node: 基本用法<4>,  Next: 位置引數的介紹,  Prev: 概念,  Up: Argparse 教學

9.14.2 基本用法
---------------

讓我們從一個非常簡單的例子開始，它（幾乎）什麼都不做：

     import argparse
     parser = argparse.ArgumentParser()
     parser.parse_args()

程式碼執行結果如下：

     $ python prog.py
     $ python prog.py --help
     usage: prog.py [-h]

     options:
       -h, --help  show this help message and exit
     $ python prog.py --verbose
     usage: prog.py [-h]
     prog.py: error: unrecognized arguments: --verbose
     $ python prog.py foo
     usage: prog.py [-h]
     prog.py: error: unrecognized arguments: foo

這是發生的事情：

   * 執行不帶任何選項的腳本不會在標準輸出中顯示任何內容。不太有用。

   * 第二個開始能夠顯現 *note argparse: 5. 模組的有用之處。我們幾乎什麼
     也沒做，但我們已經收到了一個很好的幫助訊息。

   * ‘--help’ 選項也可以縮寫為 ‘-h’，是我們能隨意獲得的唯一選項（即無需
     指定它）。指定任何其他內容都會導致錯誤。但即便如此，我們也還是輕鬆
     地獲得了有用的使用資訊。


File: python.info,  Node: 位置引數的介紹,  Next: 可選引數的介紹,  Prev: 基本用法<4>,  Up: Argparse 教學

9.14.3 位置引數的介紹
---------------------

例如：

     import argparse
     parser = argparse.ArgumentParser()
     parser.add_argument("echo")
     args = parser.parse_args()
     print(args.echo)

執行這段程式碼：

     $ python prog.py
     usage: prog.py [-h] echo
     prog.py: error: the following arguments are required: echo
     $ python prog.py --help
     usage: prog.py [-h] echo

     positional arguments:
       echo

     options:
       -h, --help  show this help message and exit
     $ python prog.py foo
     foo

這是會發生的事情：

   * 我們新增了 *note add_argument(): 184. 方法，我們用它來指定程式願意
     接受哪些命令列選項。在本例中，我將其命名為 ‘echo’，以便與其功能一致
     。

   * 現在呼叫我們的程式時需要指定一個選項。

   * *note parse_args(): 2b46. 方法實際上從指定的選項中回傳一些資料，在
     本例中為 ‘echo’。

   * 該變數是某種形式的「魔法」，*note argparse: 5. 可以自由執行（即無需
     指定該值儲存在哪個變數中）。你還會注意到，它的名稱與提供給方法
     ‘echo’ 的字串引數相符。

但請注意，儘管幫助顯示看起來不錯，但它目前還沒有發揮出應有的用處。例如，
我們看到 ‘echo’ 作為位置引數，但除了猜測或閱讀原始程式碼之外，我們不知道
它的作用。那麼，我們來讓它變得更有用一點：

     import argparse
     parser = argparse.ArgumentParser()
     parser.add_argument("echo", help="echo the string you use here")
     args = parser.parse_args()
     print(args.echo)

然後我們得到：

     $ python prog.py -h
     usage: prog.py [-h] echo

     positional arguments:
       echo        echo the string you use here

     options:
       -h, --help  show this help message and exit

現在來做一些更有用處的事情：

     import argparse
     parser = argparse.ArgumentParser()
     parser.add_argument("square", help="display a square of a given number")
     args = parser.parse_args()
     print(args.square**2)

程式碼執行結果如下：

     $ python prog.py 4
     Traceback (most recent call last):
       File "prog.py", line 5, in <module>
         print(args.square**2)
     TypeError: unsupported operand type(s) for ** or pow(): 'str' and 'int'

進展不太順利。這是因為，除非我們另有說明，*note argparse: 5. 會將我們給
它的選項視為字串。因此，讓我們告訴 *note argparse: 5. 將該輸入視為整數：

     import argparse
     parser = argparse.ArgumentParser()
     parser.add_argument("square", help="display a square of a given number",
                         type=int)
     args = parser.parse_args()
     print(args.square**2)

程式碼執行結果如下：

     $ python prog.py 4
     16
     $ python prog.py four
     usage: prog.py [-h] square
     prog.py: error: argument square: invalid int value: 'four'

順利進展。現在該程式甚至可以在繼續操作之前因錯誤的非法輸入而退出。


File: python.info,  Node: 可選引數的介紹,  Next: 組合位置引數和可選引數,  Prev: 位置引數的介紹,  Up: Argparse 教學

9.14.4 可選引數的介紹
---------------------

到目前為止，我們一直在討論位置引數。我們來看看如何新增可選引數：

     import argparse
     parser = argparse.ArgumentParser()
     parser.add_argument("--verbosity", help="increase output verbosity")
     args = parser.parse_args()
     if args.verbosity:
         print("verbosity turned on")

接者是結果：

     $ python prog.py --verbosity 1
     verbosity turned on
     $ python prog.py
     $ python prog.py --help
     usage: prog.py [-h] [--verbosity VERBOSITY]

     options:
       -h, --help            show this help message and exit
       --verbosity VERBOSITY
                             increase output verbosity
     $ python prog.py --verbosity
     usage: prog.py [-h] [--verbosity VERBOSITY]
     prog.py: error: argument --verbosity: expected one argument

這是發生的事情：

   * 程式被編寫為在指定 ‘--verbosity’ 時顯示一些內容，並在未指定時不顯示
     任何內容。

   * 為了表示該選項實際上是可選的，沒使用它來執行程式並不會出現錯誤。請
     注意，預設情況下，如果未使用可選引數，則相關變數（在本例中為
     ‘args.verbosity’）將被賦予 ‘None’ 作為值，這就是它未能通過 *note
     if: 2c4. 陳述式真值測試的原因。

   * 幫助訊息有點不同。

   * 當使用 ‘--verbosity’ 選項時必須要指定一些值，任何值都可以。

在上面的例子中，‘--verbosity’ 接受任意的整數，但對我們的程式來說只接受兩
個輸入值， ‘True’ 或 ‘False’。所以我們來修改一下程式碼使其符合：

     import argparse
     parser = argparse.ArgumentParser()
     parser.add_argument("--verbose", help="increase output verbosity",
                         action="store_true")
     args = parser.parse_args()
     if args.verbose:
         print("verbosity turned on")

接者是結果：

     $ python prog.py --verbose
     verbosity turned on
     $ python prog.py --verbose 1
     usage: prog.py [-h] [--verbose]
     prog.py: error: unrecognized arguments: 1
     $ python prog.py --help
     usage: prog.py [-h] [--verbose]

     options:
       -h, --help  show this help message and exit
       --verbose   increase output verbosity

這是發生的事情：

   * 這個選項現在更像是一個旗標，而不是需要值的東西。我們甚至更改了選項
     的名稱以符合這個想法。請注意，我們現在指定一個新的關鍵字 ‘action’，
     並為其指定值 ‘"store_true"’。這意味著，如果指定了該選項，則將值
     ‘True’ 指派給 ‘args.verbose’。不指定它代表為 ‘False’。

   * 當你指定一個值時，它會本著旗標的實際精神來抱怨。

   * 請注意不同的幫助文字。

* Menu:

* 短選項::


File: python.info,  Node: 短選項,  Up: 可選引數的介紹

9.14.4.1 短選項
...............

如果你熟悉命令列用法，你會注意到我尚未提及選項的簡短版本。這很簡單：

     import argparse
     parser = argparse.ArgumentParser()
     parser.add_argument("-v", "--verbose", help="increase output verbosity",
                         action="store_true")
     args = parser.parse_args()
     if args.verbose:
         print("verbosity turned on")

而這為：

     $ python prog.py -v
     verbosity turned on
     $ python prog.py --help
     usage: prog.py [-h] [-v]

     options:
       -h, --help     show this help message and exit
       -v, --verbose  increase output verbosity

請注意，新功能也反映在幫助文字中。


File: python.info,  Node: 組合位置引數和可選引數,  Next: 更進階一點,  Prev: 可選引數的介紹,  Up: Argparse 教學

9.14.5 組合位置引數和可選引數
-----------------------------

我們的程式的複雜性不斷增加：

     import argparse
     parser = argparse.ArgumentParser()
     parser.add_argument("square", type=int,
                         help="display a square of a given number")
     parser.add_argument("-v", "--verbose", action="store_true",
                         help="increase output verbosity")
     args = parser.parse_args()
     answer = args.square**2
     if args.verbose:
         print(f"the square of {args.square} equals {answer}")
     else:
         print(answer)

然後現在的輸出結果：

     $ python prog.py
     usage: prog.py [-h] [-v] square
     prog.py: error: the following arguments are required: square
     $ python prog.py 4
     16
     $ python prog.py 4 --verbose
     the square of 4 equals 16
     $ python prog.py --verbose 4
     the square of 4 equals 16

   * 我們帶回了位置引數，因而被抱怨。

   * 請注意，順序並不重要。

我們讓這個程式擁有多個訊息詳細級別 (verbosity) 之值的能力，並實際使用它
們：

     import argparse
     parser = argparse.ArgumentParser()
     parser.add_argument("square", type=int,
                         help="display a square of a given number")
     parser.add_argument("-v", "--verbosity", type=int,
                         help="increase output verbosity")
     args = parser.parse_args()
     answer = args.square**2
     if args.verbosity == 2:
         print(f"the square of {args.square} equals {answer}")
     elif args.verbosity == 1:
         print(f"{args.square}^2 == {answer}")
     else:
         print(answer)

接者是結果：

     $ python prog.py 4
     16
     $ python prog.py 4 -v
     usage: prog.py [-h] [-v VERBOSITY] square
     prog.py: error: argument -v/--verbosity: expected one argument
     $ python prog.py 4 -v 1
     4^2 == 16
     $ python prog.py 4 -v 2
     the square of 4 equals 16
     $ python prog.py 4 -v 3
     16

除了最後一個外都看起來正常，它透露了我們程式中的一個錯誤。我們可透過限制
‘--verbosity’ 選項可以接受的值來修復它：

     import argparse
     parser = argparse.ArgumentParser()
     parser.add_argument("square", type=int,
                         help="display a square of a given number")
     parser.add_argument("-v", "--verbosity", type=int, choices=[0, 1, 2],
                         help="increase output verbosity")
     args = parser.parse_args()
     answer = args.square**2
     if args.verbosity == 2:
         print(f"the square of {args.square} equals {answer}")
     elif args.verbosity == 1:
         print(f"{args.square}^2 == {answer}")
     else:
         print(answer)

接者是結果：

     $ python prog.py 4 -v 3
     usage: prog.py [-h] [-v {0,1,2}] square
     prog.py: error: argument -v/--verbosity: invalid choice: 3 (choose from 0, 1, 2)
     $ python prog.py 4 -h
     usage: prog.py [-h] [-v {0,1,2}] square

     positional arguments:
       square                display a square of a given number

     options:
       -h, --help            show this help message and exit
       -v {0,1,2}, --verbosity {0,1,2}
                             increase output verbosity

請注意，更改也會反映在錯誤訊息和幫助字串中。

現在，讓我們使用另一種常見方法來玩玩訊息詳細級別。它也與 CPython 執行檔
處理其自身訊息詳細級別引數的方式相符（請見 ‘python --help’ 的輸出）：

     import argparse
     parser = argparse.ArgumentParser()
     parser.add_argument("square", type=int,
                         help="display the square of a given number")
     parser.add_argument("-v", "--verbosity", action="count",
                         help="increase output verbosity")
     args = parser.parse_args()
     answer = args.square**2
     if args.verbosity == 2:
         print(f"the square of {args.square} equals {answer}")
     elif args.verbosity == 1:
         print(f"{args.square}^2 == {answer}")
     else:
         print(answer)

我們已經介紹過另一個操作 "count" 用來計算指定的選項出現的次數。

     $ python prog.py 4
     16
     $ python prog.py 4 -v
     4^2 == 16
     $ python prog.py 4 -vv
     the square of 4 equals 16
     $ python prog.py 4 --verbosity --verbosity
     the square of 4 equals 16
     $ python prog.py 4 -v 1
     usage: prog.py [-h] [-v] square
     prog.py: error: unrecognized arguments: 1
     $ python prog.py 4 -h
     usage: prog.py [-h] [-v] square

     positional arguments:
       square           display a square of a given number

     options:
       -h, --help       show this help message and exit
       -v, --verbosity  increase output verbosity
     $ python prog.py 4 -vvv
     16

   * 是的，現在它更像是我們上一版腳本中的旗標（類似於
     ‘action="store_true"’），這應該可以解釋抱怨的原因。

   * 它的行為也類似 "store_true" 操作。

   * 現在這裡示範了 "count" 動作的作用。你可能以前見過這種用法。

   * 如果你不指定 ‘-v’ 旗標，則該旗標被視為具有 ‘None’ 值。

   * 正如預期的那樣，指定長形式旗標，我們應該得到相同的輸出。

   * 遺憾的是，我們的幫助輸出對於我們腳本獲得的新功能並沒有提供太多資訊
     ，但我們都可以透過改進腳本的文件來解決這個問題（例如：透過 ‘help’ 關
     鍵字引數）。

   * 最後的輸出透露了我們程式中的一個錯誤。

讓我們來解決問題：

     import argparse
     parser = argparse.ArgumentParser()
     parser.add_argument("square", type=int,
                         help="display a square of a given number")
     parser.add_argument("-v", "--verbosity", action="count",
                         help="increase output verbosity")
     args = parser.parse_args()
     answer = args.square**2

     # bugfix: replace == with >=
     if args.verbosity >= 2:
         print(f"the square of {args.square} equals {answer}")
     elif args.verbosity >= 1:
         print(f"{args.square}^2 == {answer}")
     else:
         print(answer)

這就是它給出的：

     $ python prog.py 4 -vvv
     the square of 4 equals 16
     $ python prog.py 4 -vvvv
     the square of 4 equals 16
     $ python prog.py 4
     Traceback (most recent call last):
       File "prog.py", line 11, in <module>
         if args.verbosity >= 2:
     TypeError: '>=' not supported between instances of 'NoneType' and 'int'

   * 第一次輸出順利進行，並修復了我們之前遇到的錯誤。也就是說，我們希望
     任何 >= 2 的值都盡可能詳細。

   * 第三個輸出不太好。

我們來修復這個錯誤：

     import argparse
     parser = argparse.ArgumentParser()
     parser.add_argument("square", type=int,
                         help="display a square of a given number")
     parser.add_argument("-v", "--verbosity", action="count", default=0,
                         help="increase output verbosity")
     args = parser.parse_args()
     answer = args.square**2
     if args.verbosity >= 2:
         print(f"the square of {args.square} equals {answer}")
     elif args.verbosity >= 1:
         print(f"{args.square}^2 == {answer}")
     else:
         print(answer)

我們剛剛引入了另一個關鍵字 ‘default’。我們將其設為 ‘0’，以便使其與其他
int 值進行比較。請記住，預設情況下，如果未指定可選引數，它將獲得 ‘None’
值，並且不能與 int 值進行比較（因此會出現 *note TypeError: 4dd. 例外）。

而且：

     $ python prog.py 4
     16

僅憑我們迄今為止所學到的知識就可以做到很多事情了，不過其實這樣只有學到一
點皮毛而已。*note argparse: 5. 模組非常強大，在結束本教學之前我們會對它
進行更多探索。


File: python.info,  Node: 更進階一點,  Next: 如何翻譯 argparse 輸出,  Prev: 組合位置引數和可選引數,  Up: Argparse 教學

9.14.6 更進階一點
-----------------

如果我們想擴充我們的小程式來執行其他次方的運算，而不僅是平方：

     import argparse
     parser = argparse.ArgumentParser()
     parser.add_argument("x", type=int, help="the base")
     parser.add_argument("y", type=int, help="the exponent")
     parser.add_argument("-v", "--verbosity", action="count", default=0)
     args = parser.parse_args()
     answer = args.x**args.y
     if args.verbosity >= 2:
         print(f"{args.x} to the power {args.y} equals {answer}")
     elif args.verbosity >= 1:
         print(f"{args.x}^{args.y} == {answer}")
     else:
         print(answer)

結果：

     $ python prog.py
     usage: prog.py [-h] [-v] x y
     prog.py: error: the following arguments are required: x, y
     $ python prog.py -h
     usage: prog.py [-h] [-v] x y

     positional arguments:
       x                the base
       y                the exponent

     options:
       -h, --help       show this help message and exit
       -v, --verbosity
     $ python prog.py 4 2 -v
     4^2 == 16

請注意，到目前為止，我們一直在使用詳細級別來'更改'顯示的文字。以下範例使
用詳細級別來顯示'更多'文字：

     import argparse
     parser = argparse.ArgumentParser()
     parser.add_argument("x", type=int, help="the base")
     parser.add_argument("y", type=int, help="the exponent")
     parser.add_argument("-v", "--verbosity", action="count", default=0)
     args = parser.parse_args()
     answer = args.x**args.y
     if args.verbosity >= 2:
         print(f"Running '{__file__}'")
     if args.verbosity >= 1:
         print(f"{args.x}^{args.y} == ", end="")
     print(answer)

結果：

     $ python prog.py 4 2
     16
     $ python prog.py 4 2 -v
     4^2 == 16
     $ python prog.py 4 2 -vv
     Running 'prog.py'
     4^2 == 16

* Menu:

* 指定不明確的引數::
* 相互衝突的選項::


File: python.info,  Node: 指定不明確的引數,  Next: 相互衝突的選項,  Up: 更進階一點

9.14.6.1 指定不明確的引數
.........................

當決定一個引數是位置引數還是引數會有歧義，可以使用 ‘--’ 來告訴 *note
parse_args(): 2b46. 之後的所有內容都是位置引數：

     >>> parser = argparse.ArgumentParser(prog='PROG')
     >>> parser.add_argument('-n', nargs='+')
     >>> parser.add_argument('args', nargs='*')

     >>> # ambiguous, so parse_args assumes it's an option
     >>> parser.parse_args(['-f'])
     usage: PROG [-h] [-n N [N ...]] [args ...]
     PROG: error: unrecognized arguments: -f

     >>> parser.parse_args(['--', '-f'])
     Namespace(args=['-f'], n=None)

     >>> # ambiguous, so the -n option greedily accepts arguments
     >>> parser.parse_args(['-n', '1', '2', '3'])
     Namespace(args=[], n=['1', '2', '3'])

     >>> parser.parse_args(['-n', '1', '--', '2', '3'])
     Namespace(args=['2', '3'], n=['1'])


File: python.info,  Node: 相互衝突的選項,  Prev: 指定不明確的引數,  Up: 更進階一點

9.14.6.2 相互衝突的選項
.......................

到目前為止，我們一直在使用 *note argparse.ArgumentParser: 4de. 實例的兩
種方法。讓我們介紹第三個，*note add_mutually_exclusive_group(): 2b8e.，
它允許我們指定彼此衝突的選項。我們還可以更改程式的其餘部分，以使得新功能
更有意義：我們將引入 ‘--quiet’ 選項，該選項與 ‘--verbose’ 選項相反：

     import argparse

     parser = argparse.ArgumentParser()
     group = parser.add_mutually_exclusive_group()
     group.add_argument("-v", "--verbose", action="store_true")
     group.add_argument("-q", "--quiet", action="store_true")
     parser.add_argument("x", type=int, help="the base")
     parser.add_argument("y", type=int, help="the exponent")
     args = parser.parse_args()
     answer = args.x**args.y

     if args.quiet:
         print(answer)
     elif args.verbose:
         print(f"{args.x} to the power {args.y} equals {answer}")
     else:
         print(f"{args.x}^{args.y} == {answer}")

我們的程式現在更簡單了，我們因為功能展示失去了一些功能，但無論如何，以下
這是輸出：

     $ python prog.py 4 2
     4^2 == 16
     $ python prog.py 4 2 -q
     16
     $ python prog.py 4 2 -v
     4 to the power 2 equals 16
     $ python prog.py 4 2 -vq
     usage: prog.py [-h] [-v | -q] x y
     prog.py: error: argument -q/--quiet: not allowed with argument -v/--verbose
     $ python prog.py 4 2 -v --quiet
     usage: prog.py [-h] [-v | -q] x y
     prog.py: error: argument -q/--quiet: not allowed with argument -v/--verbose

這應該很容易理解。我新增了最後一個輸出，以便看到所獲得的靈活性，即可以混
合長形式與短形式選項。

在我們結束之前，你可能想告訴使用者你的程式的主要目的，以防他們不知道：

     import argparse

     parser = argparse.ArgumentParser(description="calculate X to the power of Y")
     group = parser.add_mutually_exclusive_group()
     group.add_argument("-v", "--verbose", action="store_true")
     group.add_argument("-q", "--quiet", action="store_true")
     parser.add_argument("x", type=int, help="the base")
     parser.add_argument("y", type=int, help="the exponent")
     args = parser.parse_args()
     answer = args.x**args.y

     if args.quiet:
         print(answer)
     elif args.verbose:
         print(f"{args.x} to the power {args.y} equals {answer}")
     else:
         print(f"{args.x}^{args.y} == {answer}")

請注意用法文字中的細微差別。注意 ‘[-v | -q]’，它告訴我們可以使用 ‘-v’ 或
‘-q’，但不能同時使用：

     $ python prog.py --help
     usage: prog.py [-h] [-v | -q] x y

     calculate X to the power of Y

     positional arguments:
       x              the base
       y              the exponent

     options:
       -h, --help     show this help message and exit
       -v, --verbose
       -q, --quiet


File: python.info,  Node: 如何翻譯 argparse 輸出,  Next: 結論,  Prev: 更進階一點,  Up: Argparse 教學

9.14.7 如何翻譯 argparse 輸出
-----------------------------

*note argparse: 5. 模組的輸出，例如幫助文字和錯誤訊息，都可以透過使用
*note gettext: 59. 模組進行翻譯。這允許應用程式能輕鬆本地化 *note
argparse: 5. 生成的訊息。另請參閱 *note Internationalizing your programs
and modules: 3b1b.。

例如，在此 *note argparse: 5. 輸出中：

     $ python prog.py --help
     usage: prog.py [-h] [-v | -q] x y

     calculate X to the power of Y

     positional arguments:
       x              the base
       y              the exponent

     options:
       -h, --help     show this help message and exit
       -v, --verbose
       -q, --quiet

字串 ‘usage:’、‘positional arguments:’、‘options:’ 和 ‘show this help
message and exit’ 都是可被翻譯的。

為了翻譯這些字串，必須先將它們提取到 ‘.po’ 檔案中。例如，使用 Babel(1) 並
執行下列命令：

     $ pybabel extract -o messages.po /usr/lib/python3.12/argparse.py

此命令將從 *note argparse: 5. 模組中提取出所有可翻譯的字串，並將它們輸出
到名為 ‘messages.po’ 的檔案中。這個指令假設你的 Python 是安裝在
‘/usr/lib’ 中。

你可以使用以下腳本找到 *note argparse: 5. 模組在系統上的位置：

     import argparse
     print(argparse.__file__)

一旦翻譯了 ‘.po’ 檔案中的訊息並使用 *note gettext: 59. 安裝了翻譯，*note
argparse: 5. 將能夠顯示翻譯後的訊息。

若要在 *note argparse: 5. 輸出中翻譯你自己的字串，請使用 *note gettext:
59.。

   ---------- Footnotes ----------

   (1) https://babel.pocoo.org/


File: python.info,  Node: 結論,  Prev: 如何翻譯 argparse 輸出,  Up: Argparse 教學

9.14.8 結論
-----------

*note argparse: 5. 模組提供的功能比此篇內容的要多得多。它的文件非常詳細
與透徹並有很多範例。讀完本教學後，你應該可以輕鬆消化它們，而不會感到不知
所措。


File: python.info,  Node: ipaddress 模組介紹,  Next: 使用 DTrace 和 SystemTap 檢測 CPython,  Prev: Argparse 教學,  Up: Python 如何達成任務

9.15 ipaddress 模組介紹
=======================


作者: Peter Moody


作者: Nick Coghlan

總攬
....

這份文件旨在為 *note ipaddress: 74. 模組提供一個初步介紹。文件主要針對那
些不熟悉 IP 網路術語的使用者，但對想要了解 *note ipaddress: 74. 模組如何
表示 IP 網址概念的網路工程師也可能有用。

* Menu:

* Creating Address/Network/Interface objects::
* Inspecting Address/Network/Interface Objects::
* Networks as lists of Addresses::
* Comparisons: Comparisons<2>.
* Using IP Addresses with other modules::
* Getting more detail when instance creation fails::


File: python.info,  Node: Creating Address/Network/Interface objects,  Next: Inspecting Address/Network/Interface Objects,  Up: ipaddress 模組介紹

9.15.1 Creating Address/Network/Interface objects
-------------------------------------------------

Since *note ipaddress: 74. is a module for inspecting and manipulating
IP addresses, the first thing you'll want to do is create some objects.
You can use *note ipaddress: 74. to create objects from strings and
integers.

* Menu:

* A Note on IP Versions::
* IP Host Addresses::
* 定義網路::
* Host Interfaces::


File: python.info,  Node: A Note on IP Versions,  Next: IP Host Addresses,  Up: Creating Address/Network/Interface objects

9.15.1.1 A Note on IP Versions
..............................

For readers that aren't particularly familiar with IP addressing, it's
important to know that the Internet Protocol (IP) is currently in the
process of moving from version 4 of the protocol to version 6.  This
transition is occurring largely because version 4 of the protocol
doesn't provide enough addresses to handle the needs of the whole world,
especially given the increasing number of devices with direct
connections to the internet.

Explaining the details of the differences between the two versions of
the protocol is beyond the scope of this introduction, but readers need
to at least be aware that these two versions exist, and it will
sometimes be necessary to force the use of one version or the other.


File: python.info,  Node: IP Host Addresses,  Next: 定義網路,  Prev: A Note on IP Versions,  Up: Creating Address/Network/Interface objects

9.15.1.2 IP Host Addresses
..........................

Addresses, often referred to as "host addresses" are the most basic unit
when working with IP addressing.  The simplest way to create addresses
is to use the *note ipaddress.ip_address(): 3a5e. factory function,
which automatically determines whether to create an IPv4 or IPv6 address
based on the passed in value:

     >>> ipaddress.ip_address('192.0.2.1')
     IPv4Address('192.0.2.1')
     >>> ipaddress.ip_address('2001:DB8::1')
     IPv6Address('2001:db8::1')

Addresses can also be created directly from integers.  Values that will
fit within 32 bits are assumed to be IPv4 addresses:

     >>> ipaddress.ip_address(3221225985)
     IPv4Address('192.0.2.1')
     >>> ipaddress.ip_address(42540766411282592856903984951653826561)
     IPv6Address('2001:db8::1')

To force the use of IPv4 or IPv6 addresses, the relevant classes can be
invoked directly.  This is particularly useful to force creation of IPv6
addresses for small integers:

     >>> ipaddress.ip_address(1)
     IPv4Address('0.0.0.1')
     >>> ipaddress.IPv4Address(1)
     IPv4Address('0.0.0.1')
     >>> ipaddress.IPv6Address(1)
     IPv6Address('::1')


File: python.info,  Node: 定義網路,  Next: Host Interfaces,  Prev: IP Host Addresses,  Up: Creating Address/Network/Interface objects

9.15.1.3 定義網路
.................

Host addresses are usually grouped together into IP networks, so *note
ipaddress: 74. provides a way to create, inspect and manipulate network
definitions.  IP network objects are constructed from strings that
define the range of host addresses that are part of that network.  The
simplest form for that information is a "network address/network prefix"
pair, where the prefix defines the number of leading bits that are
compared to determine whether or not an address is part of the network
and the network address defines the expected value of those bits.

As for addresses, a factory function is provided that determines the
correct IP version automatically:

     >>> ipaddress.ip_network('192.0.2.0/24')
     IPv4Network('192.0.2.0/24')
     >>> ipaddress.ip_network('2001:db8::0/96')
     IPv6Network('2001:db8::/96')

Network objects cannot have any host bits set.  The practical effect of
this is that ‘192.0.2.1/24’ does not describe a network.  Such
definitions are referred to as interface objects since the
ip-on-a-network notation is commonly used to describe network interfaces
of a computer on a given network and are described further in the next
section.

By default, attempting to create a network object with host bits set
will result in *note ValueError: 1e7. being raised.  To request that the
additional bits instead be coerced to zero, the flag ‘strict=False’ can
be passed to the constructor:

     >>> ipaddress.ip_network('192.0.2.1/24')
     Traceback (most recent call last):
        ...
     ValueError: 192.0.2.1/24 has host bits set
     >>> ipaddress.ip_network('192.0.2.1/24', strict=False)
     IPv4Network('192.0.2.0/24')

While the string form offers significantly more flexibility, networks
can also be defined with integers, just like host addresses.  In this
case, the network is considered to contain only the single address
identified by the integer, so the network prefix includes the entire
network address:

     >>> ipaddress.ip_network(3221225984)
     IPv4Network('192.0.2.0/32')
     >>> ipaddress.ip_network(42540766411282592856903984951653826560)
     IPv6Network('2001:db8::/128')

As with addresses, creation of a particular kind of network can be
forced by calling the class constructor directly instead of using the
factory function.


File: python.info,  Node: Host Interfaces,  Prev: 定義網路,  Up: Creating Address/Network/Interface objects

9.15.1.4 Host Interfaces
........................

As mentioned just above, if you need to describe an address on a
particular network, neither the address nor the network classes are
sufficient.  Notation like ‘192.0.2.1/24’ is commonly used by network
engineers and the people who write tools for firewalls and routers as
shorthand for "the host ‘192.0.2.1’ on the network ‘192.0.2.0/24’",
Accordingly, *note ipaddress: 74. provides a set of hybrid classes that
associate an address with a particular network.  The interface for
creation is identical to that for defining network objects, except that
the address portion isn't constrained to being a network address.

     >>> ipaddress.ip_interface('192.0.2.1/24')
     IPv4Interface('192.0.2.1/24')
     >>> ipaddress.ip_interface('2001:db8::1/96')
     IPv6Interface('2001:db8::1/96')

Integer inputs are accepted (as with networks), and use of a particular
IP version can be forced by calling the relevant constructor directly.


File: python.info,  Node: Inspecting Address/Network/Interface Objects,  Next: Networks as lists of Addresses,  Prev: Creating Address/Network/Interface objects,  Up: ipaddress 模組介紹

9.15.2 Inspecting Address/Network/Interface Objects
---------------------------------------------------

You've gone to the trouble of creating an
IPv(4|6)(Address|Network|Interface) object, so you probably want to get
information about it.  *note ipaddress: 74. tries to make doing this
easy and intuitive.

Extracting the IP version:

     >>> addr4 = ipaddress.ip_address('192.0.2.1')
     >>> addr6 = ipaddress.ip_address('2001:db8::1')
     >>> addr6.version
     6
     >>> addr4.version
     4

Obtaining the network from an interface:

     >>> host4 = ipaddress.ip_interface('192.0.2.1/24')
     >>> host4.network
     IPv4Network('192.0.2.0/24')
     >>> host6 = ipaddress.ip_interface('2001:db8::1/96')
     >>> host6.network
     IPv6Network('2001:db8::/96')

Finding out how many individual addresses are in a network:

     >>> net4 = ipaddress.ip_network('192.0.2.0/24')
     >>> net4.num_addresses
     256
     >>> net6 = ipaddress.ip_network('2001:db8::0/96')
     >>> net6.num_addresses
     4294967296

Iterating through the "usable" addresses on a network:

     >>> net4 = ipaddress.ip_network('192.0.2.0/24')
     >>> for x in net4.hosts():
     ...     print(x)
     192.0.2.1
     192.0.2.2
     192.0.2.3
     192.0.2.4
     ...
     192.0.2.252
     192.0.2.253
     192.0.2.254

Obtaining the netmask (i.e.  set bits corresponding to the network
prefix) or the hostmask (any bits that are not part of the netmask):

     >>> net4 = ipaddress.ip_network('192.0.2.0/24')
     >>> net4.netmask
     IPv4Address('255.255.255.0')
     >>> net4.hostmask
     IPv4Address('0.0.0.255')
     >>> net6 = ipaddress.ip_network('2001:db8::0/96')
     >>> net6.netmask
     IPv6Address('ffff:ffff:ffff:ffff:ffff:ffff::')
     >>> net6.hostmask
     IPv6Address('::ffff:ffff')

Exploding or compressing the address:

     >>> addr6.exploded
     '2001:0db8:0000:0000:0000:0000:0000:0001'
     >>> addr6.compressed
     '2001:db8::1'
     >>> net6.exploded
     '2001:0db8:0000:0000:0000:0000:0000:0000/96'
     >>> net6.compressed
     '2001:db8::/96'

While IPv4 doesn't support explosion or compression, the associated
objects still provide the relevant properties so that version neutral
code can easily ensure the most concise or most verbose form is used for
IPv6 addresses while still correctly handling IPv4 addresses.


File: python.info,  Node: Networks as lists of Addresses,  Next: Comparisons<2>,  Prev: Inspecting Address/Network/Interface Objects,  Up: ipaddress 模組介紹

9.15.3 Networks as lists of Addresses
-------------------------------------

It's sometimes useful to treat networks as lists.  This means it is
possible to index them like this:

     >>> net4[1]
     IPv4Address('192.0.2.1')
     >>> net4[-1]
     IPv4Address('192.0.2.255')
     >>> net6[1]
     IPv6Address('2001:db8::1')
     >>> net6[-1]
     IPv6Address('2001:db8::ffff:ffff')

It also means that network objects lend themselves to using the list
membership test syntax like this:

     if address in network:
         # do something

Containment testing is done efficiently based on the network prefix:

     >>> addr4 = ipaddress.ip_address('192.0.2.1')
     >>> addr4 in ipaddress.ip_network('192.0.2.0/24')
     True
     >>> addr4 in ipaddress.ip_network('192.0.3.0/24')
     False


File: python.info,  Node: Comparisons<2>,  Next: Using IP Addresses with other modules,  Prev: Networks as lists of Addresses,  Up: ipaddress 模組介紹

9.15.4 Comparisons
------------------

*note ipaddress: 74. provides some simple, hopefully intuitive ways to
compare objects, where it makes sense:

     >>> ipaddress.ip_address('192.0.2.1') < ipaddress.ip_address('192.0.2.2')
     True

A *note TypeError: 4dd. exception is raised if you try to compare
objects of different versions or different types.


File: python.info,  Node: Using IP Addresses with other modules,  Next: Getting more detail when instance creation fails,  Prev: Comparisons<2>,  Up: ipaddress 模組介紹

9.15.5 Using IP Addresses with other modules
--------------------------------------------

Other modules that use IP addresses (such as *note socket: b8.) usually
won't accept objects from this module directly.  Instead, they must be
coerced to an integer or string that the other module will accept:

     >>> addr4 = ipaddress.ip_address('192.0.2.1')
     >>> str(addr4)
     '192.0.2.1'
     >>> int(addr4)
     3221225985


File: python.info,  Node: Getting more detail when instance creation fails,  Prev: Using IP Addresses with other modules,  Up: ipaddress 模組介紹

9.15.6 Getting more detail when instance creation fails
-------------------------------------------------------

When creating address/network/interface objects using the
version-agnostic factory functions, any errors will be reported as *note
ValueError: 1e7. with a generic error message that simply says the
passed in value was not recognized as an object of that type.  The lack
of a specific error is because it's necessary to know whether the value
is 'supposed' to be IPv4 or IPv6 in order to provide more detail on why
it has been rejected.

To support use cases where it is useful to have access to this
additional detail, the individual class constructors actually raise the
*note ValueError: 1e7. subclasses *note ipaddress.AddressValueError:
3a63. and *note ipaddress.NetmaskValueError: 3a85. to indicate exactly
which part of the definition failed to parse correctly.

The error messages are significantly more detailed when using the class
constructors directly.  For example:

     >>> ipaddress.ip_address("192.168.0.256")
     Traceback (most recent call last):
       ...
     ValueError: '192.168.0.256' does not appear to be an IPv4 or IPv6 address
     >>> ipaddress.IPv4Address("192.168.0.256")
     Traceback (most recent call last):
       ...
     ipaddress.AddressValueError: Octet 256 (> 255) not permitted in '192.168.0.256'

     >>> ipaddress.ip_network("192.168.0.1/64")
     Traceback (most recent call last):
       ...
     ValueError: '192.168.0.1/64' does not appear to be an IPv4 or IPv6 network
     >>> ipaddress.IPv4Network("192.168.0.1/64")
     Traceback (most recent call last):
       ...
     ipaddress.NetmaskValueError: '64' is not a valid netmask

However, both of the module specific exceptions have *note ValueError:
1e7. as their parent class, so if you're not concerned with the
particular type of error, you can still write code like the following:

     try:
         network = ipaddress.IPv4Network(address)
     except ValueError:
         print('address/netmask is invalid for IPv4:', address)


File: python.info,  Node: 使用 DTrace 和 SystemTap 檢測 CPython,  Next: Python 對 Linux perf 分析器的支援,  Prev: ipaddress 模組介紹,  Up: Python 如何達成任務

9.16 使用 DTrace 和 SystemTap 檢測 CPython
==========================================


作者: David Malcolm


作者: Łukasz Langa

DTrace 和 SystemTap 都是監測工具，各自都提供了一種檢查電腦系統之行程
(process) 正在執行什麼操作的方法。它們都使用了領域限定 (domain-specific)
的語言，允許使用者編寫以下腳本：

   - 過濾要觀察的行程

   - 收集來自感興趣之行程的資料

   - 以這些資料產生報告

從 Python 3.6 開始，CPython 可以使用嵌入式「標記 (marker)」（也稱為「探
針 (probe)」）建置，可以透過 DTrace 或 SystemTap 腳本進行觀察，從而更輕
鬆地監視系統之 CPython 行程正在執行的操作。

'CPython 實作細節：' DTrace 標記是 CPython 直譯器的實作細節。不保證
CPython 版本之間的探針相容性。更改 CPython 版本時，DTrace 腳本可能會停止
運作或錯誤地運作，而不會發出警告。

* Menu:

* 啟用靜態標記::
* 靜態 DTrace 探針::
* 靜態 SystemTap 標記::
* 可用的靜態標記::
* SystemTap Tapsets::
* 範例: 範例<54>.


File: python.info,  Node: 啟用靜態標記,  Next: 靜態 DTrace 探針,  Up: 使用 DTrace 和 SystemTap 檢測 CPython

9.16.1 啟用靜態標記
-------------------

macOS 內建了對 DTrace 的支援。在 Linux 上，為了建置帶有 SystemTap 嵌入標
記的 CPython，必須安裝 SystemTap 開發工具。

在 Linux 機器上，這可以透過以下方式完成：

     $ yum install systemtap-sdt-devel

或是：

     $ sudo apt-get install systemtap-sdt-dev

然後 CPython 必須使用*note 配置 -with-dtrace 選項: 1cb6.：

     checking for --with-dtrace... yes

在 macOS 上，你可以透過在後台運行 Python 行程並列出 Python 發布者
(provider) 所提供的所有可用探針，以列出可用的 DTrace 探針：

     $ python3.6 -q &
     $ sudo dtrace -l -P python$!  # 或 dtrace -l -m python3.6

        ID   PROVIDER            MODULE                          FUNCTION NAME
     29564 python18035        python3.6          _PyEval_EvalFrameDefault function-entry
     29565 python18035        python3.6             dtrace_function_entry function-entry
     29566 python18035        python3.6          _PyEval_EvalFrameDefault function-return
     29567 python18035        python3.6            dtrace_function_return function-return
     29568 python18035        python3.6                           collect gc-done
     29569 python18035        python3.6                           collect gc-start
     29570 python18035        python3.6          _PyEval_EvalFrameDefault line
     29571 python18035        python3.6                 maybe_dtrace_line line

在 Linux 上，你可以透過查看二進位建置檔案中是否包含 ".note.stapsdt" 部分
來驗證 SystemTap 靜態標記是否存在。

     $ readelf -S ./python | grep .note.stapsdt
     [30] .note.stapsdt        NOTE         0000000000000000 00308d78

如果你已將 Python 建置為共享函式庫（使用 *note -enable-shared: 807. 配置
選項），則需要在共享函式庫中查找。例如：

     $ readelf -S libpython3.3dm.so.1.0 | grep .note.stapsdt
     [29] .note.stapsdt        NOTE         0000000000000000 00365b68

足夠現代化的 readelf 可以印出元資料 (metadata)：

     $ readelf -n ./python

     Displaying notes found at file offset 0x00000254 with length 0x00000020:
         Owner                 Data size          Description
         GNU                  0x00000010          NT_GNU_ABI_TAG (ABI version tag)
             OS: Linux, ABI: 2.6.32

     Displaying notes found at file offset 0x00000274 with length 0x00000024:
         Owner                 Data size          Description
         GNU                  0x00000014          NT_GNU_BUILD_ID (unique build ID bitstring)
             Build ID: df924a2b08a7e89f6e11251d4602022977af2670

     Displaying notes found at file offset 0x002d6c30 with length 0x00000144:
         Owner                 Data size          Description
         stapsdt              0x00000031          NT_STAPSDT (SystemTap probe descriptors)
             Provider: python
             Name: gc__start
             Location: 0x00000000004371c3, Base: 0x0000000000630ce2, Semaphore: 0x00000000008d6bf6
             Arguments: -4@%ebx
         stapsdt              0x00000030          NT_STAPSDT (SystemTap probe descriptors)
             Provider: python
             Name: gc__done
             Location: 0x00000000004374e1, Base: 0x0000000000630ce2, Semaphore: 0x00000000008d6bf8
             Arguments: -8@%rax
         stapsdt              0x00000045          NT_STAPSDT (SystemTap probe descriptors)
             Provider: python
             Name: function__entry
             Location: 0x000000000053db6c, Base: 0x0000000000630ce2, Semaphore: 0x00000000008d6be8
             Arguments: 8@%rbp 8@%r12 -4@%eax
         stapsdt              0x00000046          NT_STAPSDT (SystemTap probe descriptors)
             Provider: python
             Name: function__return
             Location: 0x000000000053dba8, Base: 0x0000000000630ce2, Semaphore: 0x00000000008d6bea
             Arguments: 8@%rbp 8@%r12 -4@%eax

上述元資料包含 SystemTap 的資訊，描述了它如何修補策略性放置的機器碼指令
以啟用 SystemTap 腳本使用的追蹤 hook。


File: python.info,  Node: 靜態 DTrace 探針,  Next: 靜態 SystemTap 標記,  Prev: 啟用靜態標記,  Up: 使用 DTrace 和 SystemTap 檢測 CPython

9.16.2 靜態 DTrace 探針
-----------------------

以下範例示範 DTrace 腳本可用於顯示 Python 腳本的呼叫/回傳階層結構，僅在
名為 "start" 的函式的呼叫內進行追蹤。換句話說，引入時的函式呼叫不會被列
出：

     self int indent;

     python$target:::function-entry
     /copyinstr(arg1) == "start"/
     {
             self->trace = 1;
     }

     python$target:::function-entry
     /self->trace/
     {
             printf("%d\t%*s:", timestamp, 15, probename);
             printf("%*s", self->indent, "");
             printf("%s:%s:%d\n", basename(copyinstr(arg0)), copyinstr(arg1), arg2);
             self->indent++;
     }

     python$target:::function-return
     /self->trace/
     {
             self->indent--;
             printf("%d\t%*s:", timestamp, 15, probename);
             printf("%*s", self->indent, "");
             printf("%s:%s:%d\n", basename(copyinstr(arg0)), copyinstr(arg1), arg2);
     }

     python$target:::function-return
     /copyinstr(arg1) == "start"/
     {
             self->trace = 0;
     }

可以這樣呼叫：

     $ sudo dtrace -q -s call_stack.d -c "python3.6 script.py"

輸出如下所示：

     156641360502280  function-entry:call_stack.py:start:23
     156641360518804  function-entry: call_stack.py:function_1:1
     156641360532797  function-entry:  call_stack.py:function_3:9
     156641360546807 function-return:  call_stack.py:function_3:10
     156641360563367 function-return: call_stack.py:function_1:2
     156641360578365  function-entry: call_stack.py:function_2:5
     156641360591757  function-entry:  call_stack.py:function_1:1
     156641360605556  function-entry:   call_stack.py:function_3:9
     156641360617482 function-return:   call_stack.py:function_3:10
     156641360629814 function-return:  call_stack.py:function_1:2
     156641360642285 function-return: call_stack.py:function_2:6
     156641360656770  function-entry: call_stack.py:function_3:9
     156641360669707 function-return: call_stack.py:function_3:10
     156641360687853  function-entry: call_stack.py:function_4:13
     156641360700719 function-return: call_stack.py:function_4:14
     156641360719640  function-entry: call_stack.py:function_5:18
     156641360732567 function-return: call_stack.py:function_5:21
     156641360747370 function-return:call_stack.py:start:28


File: python.info,  Node: 靜態 SystemTap 標記,  Next: 可用的靜態標記,  Prev: 靜態 DTrace 探針,  Up: 使用 DTrace 和 SystemTap 檢測 CPython

9.16.3 靜態 SystemTap 標記
--------------------------

使用 SystemTap 整合的低階方法是直接使用靜態標記。這會需要你明確聲明包含
它們的二進位檔案。

例如，此 SystemTap 腳本可用於顯示 Python 腳本的呼叫/回傳階層結構：

     probe process("python").mark("function__entry") {
          filename = user_string($arg1);
          funcname = user_string($arg2);
          lineno = $arg3;

          printf("%s => %s in %s:%d\\n",
                 thread_indent(1), funcname, filename, lineno);
     }

     probe process("python").mark("function__return") {
         filename = user_string($arg1);
         funcname = user_string($arg2);
         lineno = $arg3;

         printf("%s <= %s in %s:%d\\n",
                thread_indent(-1), funcname, filename, lineno);
     }

可以這樣呼叫：

     $ stap \
       show-call-hierarchy.stp \
       -c "./python test.py"

輸出如下所示：

     11408 python(8274):        => __contains__ in Lib/_abcoll.py:362
     11414 python(8274):         => __getitem__ in Lib/os.py:425
     11418 python(8274):          => encode in Lib/os.py:490
     11424 python(8274):          <= encode in Lib/os.py:493
     11428 python(8274):         <= __getitem__ in Lib/os.py:426
     11433 python(8274):        <= __contains__ in Lib/_abcoll.py:366

其中的行 (column) 是：

   - 自腳本開始以來的時間（以微秒為單位）

   - 可執行檔案的名稱

   - 行程的 PID

其餘部分表示腳本執行時的呼叫/回傳階層結構。

對於以 *note -enable-shared: 807. 建置的 CPython，標記被包含在 libpython
共享函式庫中，並且探針的帶點路徑 (dotted path) 需要反映這一點。例如，上
面範例中的這一列：

     probe process("python").mark("function__entry") {

應該改為讀取：

     probe process("python").library("libpython3.6dm.so.1.0").mark("function__entry") {

（假設 CPython 3.6 的*note 除錯建置版本: 1de.）


File: python.info,  Node: 可用的靜態標記,  Next: SystemTap Tapsets,  Prev: 靜態 SystemTap 標記,  Up: 使用 DTrace 和 SystemTap 檢測 CPython

9.16.4 可用的靜態標記
---------------------

 -- Object: function__entry(str filename, str funcname, int lineno)

     該標記表示 Python 函式的執行已經開始。它僅針對純 Python（位元組碼）
     函式觸發。

     檔案名稱、函式名稱和列號作為位置引數提供給追蹤腳本，必須使用
     ‘$arg1’、‘$arg2’、‘$arg3’ 來存取：

             * ‘$arg1’ : ‘(const char *)’ 檔案名稱，可使用
               ‘user_string($arg1)’ 存取

             * ‘$arg2’ ：‘(const char *)’ 函式名稱，可使用
               ‘user_string($arg2)’ 存取

             * ‘$arg3’ : ‘int’ 列號

 -- Object: function__return(str filename, str funcname, int lineno)

     該標記與 ‘function__entry()’ 相反，表示 Python 函式的執行已結束（透
     過 ‘return’ 或透過例外）。它僅針對純 Python（位元組碼）函式觸發。

     引數與 ‘function__entry()’ 相同

 -- Object: line(str filename, str funcname, int lineno)

     該標記表示一列 Python 即將被執行。它相當於使用 Python 分析器來逐行
     追蹤。它不在 C 函式內觸發。

     引數與 ‘function__entry()’ 相同。

 -- Object: gc__start(int generation)

     當 Python 直譯器開始垃圾回收 (garbage collection) 週期時觸發。
     ‘arg0’ 是要掃描的一代 (generation)，如 *note gc.collect(): 16b.。

 -- Object: gc__done(long collected)

     當 Python 直譯器完成垃圾回收週期時觸發。‘arg0’ 是收集到的物件數量。

 -- Object: import__find__load__start(str modulename)

     在 *note importlib: 6b. 嘗試查找並載入模組之前觸發。‘arg0’ 是模組名
     稱。

     在 3.7 版被加入.

 -- Object: import__find__load__done(str modulename, int found)

     在呼叫 *note importlib: 6b. 的 find_and_load 函式後觸發。 ‘arg0’ 是
     模組名稱，‘arg1’ 代表模組是否已成功載入。

     在 3.7 版被加入.

 -- Object: audit(str event, void *tuple)

     當呼叫 *note sys.audit(): 1873. 或 *note PySys_Audit(): 321. 時觸發
     。‘arg0’ 是 C 字串形式的事件名稱，‘arg1’ 是指向元組 (tuple) 物件的
     *note PyObject: 311. 指標。

     在 3.8 版被加入.


File: python.info,  Node: SystemTap Tapsets,  Next: 範例<54>,  Prev: 可用的靜態標記,  Up: 使用 DTrace 和 SystemTap 檢測 CPython

9.16.5 SystemTap Tapsets
------------------------

使用 SystemTap 整合的高階方法是使用 "tapset"：SystemTap 相當於一個函式庫
，它隱藏了靜態標記的一些低階詳細資訊。

這是一個 tapset 檔案，是基於 CPython 的非共享建置版本：

     /*
        Provide a higher-level wrapping around the function__entry and
        function__return markers:
      \*/
     probe python.function.entry = process("python").mark("function__entry")
     {
         filename = user_string($arg1);
         funcname = user_string($arg2);
         lineno = $arg3;
         frameptr = $arg4
     }
     probe python.function.return = process("python").mark("function__return")
     {
         filename = user_string($arg1);
         funcname = user_string($arg2);
         lineno = $arg3;
         frameptr = $arg4
     }

如果此檔案是安裝在 SystemTap 的 tapset 目錄中（例如
‘/usr/share/systemtap/tapset’），則這些額外的探測點將可被使用：

 -- Object: python.function.entry(str filename, str funcname, int
          lineno, frameptr)

     該探測點表示 Python 函式的執行已經開始。它僅針對純 Python（位元組碼
     ）函式觸發。

 -- Object: python.function.return(str filename, str funcname, int
          lineno, frameptr)

     這個探測點與 ‘python.function.return’ 相反，表示 Python 函式的執行
     已經結束（透過 ‘return’ 或者透過例外）。它僅針對純 Python（位元組碼
     ）函式觸發。


File: python.info,  Node: 範例<54>,  Prev: SystemTap Tapsets,  Up: 使用 DTrace 和 SystemTap 檢測 CPython

9.16.6 範例
-----------

此 SystemTap 腳本使用上面的 tapset 來更清晰地實作上面給出的追蹤 Python 函
式呼叫階層結構的範例，而無需直接命名靜態標記：

     probe python.function.entry
     {
       printf("%s => %s in %s:%d\n",
              thread_indent(1), funcname, filename, lineno);
     }

     probe python.function.return
     {
       printf("%s <= %s in %s:%d\n",
              thread_indent(-1), funcname, filename, lineno);
     }

以下腳本使用上面的 tapset 來提供所有正在運行之 CPython 程式碼的近乎最高
層視角，顯示整個系統中每秒最常被進入的 20 個位元組碼幀 (bytecode frame)：

     global fn_calls;

     probe python.function.entry
     {
         fn_calls[pid(), filename, funcname, lineno] += 1;
     }

     probe timer.ms(1000) {
         printf("\033[2J\033[1;1H") /* clear screen \*/
         printf("%6s %80s %6s %30s %6s\n",
                "PID", "FILENAME", "LINE", "FUNCTION", "CALLS")
         foreach ([pid, filename, funcname, lineno] in fn_calls- limit 20) {
             printf("%6d %80s %6d %30s %6d\n",
                 pid, filename, lineno, funcname,
                 fn_calls[pid, filename, funcname, lineno]);
         }
         delete fn_calls;
     }


File: python.info,  Node: Python 對 Linux perf 分析器的支援,  Next: 註釋 annotation 最佳實踐,  Prev: 使用 DTrace 和 SystemTap 檢測 CPython,  Up: Python 如何達成任務

9.17 Python 對 Linux ‘perf’ 分析器的支援
========================================


作者: Pablo Galindo

Linux 性能分析器 (Linux perf profiler)(1) 是一個非常強大的工具，可讓你分
析並獲取有關應用程式的性能資訊。‘perf’ 還擁有一個非常活躍的工具生態系統
，有助於分析其生成的資料。

在 Python 應用程式中使用 ‘perf’ 分析器的主要問題是 ‘perf’ 僅獲取有關原生
符號的資訊，即用 C 編寫的函式和程式的名稱。這表示程式碼中的 Python 函式
名稱和檔案名稱不會出現在 ‘perf’ 的輸出中。

從 Python 3.12 開始，直譯器可以在特殊模式下執行，該模式允許 Python 函式
出現在 ‘perf’ 分析器的輸出中。啟用此模式後，直譯器將在執行每個 Python 函
式之前插入 (interpose) 一小段動態編譯的程式碼，並使用 *note perf map
檔案: 4952.來告訴 ‘perf’ 這段程式碼與相關聯的 Python 函式間的關係。

     備註: 目前對 ‘perf’ 分析器的支援僅適用於 Linux 的特定架構上。檢查
     ‘configure’ 建構步驟的輸出或檢查 ‘python -m sysconfig | grep
     HAVE_PERF_TRAMPOLINE’ 的輸出來查看你的系統是否支援。

例如，參考以下腳本：

     def foo(n):
         result = 0
         for _ in range(n):
             result += 1
         return result

     def bar(n):
         foo(n)

     def baz(n):
         bar(n)

     if __name__ == "__main__":
         baz(1000000)

我們可以執行 ‘perf’ 以 9999 赫茲採樣 CPU 堆疊追蹤 (stack trace)：

     $ perf record -F 9999 -g -o perf.data python my_script.py

然後我們可以使用 ‘perf report’ 來分析資料：

     $ perf report --stdio -n -g

     # Children      Self       Samples  Command     Shared Object       Symbol
     # ........  ........  ............  ..........  ..................  ..........................................
     #
         91.08%     0.00%             0  python.exe  python.exe          [.] _start
                 |
                 ---_start
                 |
                     --90.71%--__libc_start_main
                             Py_BytesMain
                             |
                             |--56.88%--pymain_run_python.constprop.0
                             |          |
                             |          |--56.13%--_PyRun_AnyFileObject
                             |          |          _PyRun_SimpleFileObject
                             |          |          |
                             |          |          |--55.02%--run_mod
                             |          |          |          |
                             |          |          |           --54.65%--PyEval_EvalCode
                             |          |          |                     _PyEval_EvalFrameDefault
                             |          |          |                     PyObject_Vectorcall
                             |          |          |                     _PyEval_Vector
                             |          |          |                     _PyEval_EvalFrameDefault
                             |          |          |                     PyObject_Vectorcall
                             |          |          |                     _PyEval_Vector
                             |          |          |                     _PyEval_EvalFrameDefault
                             |          |          |                     PyObject_Vectorcall
                             |          |          |                     _PyEval_Vector
                             |          |          |                     |
                             |          |          |                     |--51.67%--_PyEval_EvalFrameDefault
                             |          |          |                     |          |
                             |          |          |                     |          |--11.52%--_PyLong_Add
                             |          |          |                     |          |          |
                             |          |          |                     |          |          |--2.97%--_PyObject_Malloc
     ...

如你所見，Python 函式未顯示在輸出中，僅顯示 ‘_Py_Eval_EvalFrameDefault’
（為 Python 位元組碼 (bytecode) 求值的函式）。不幸的是，這不是很有用，因
為所有 Python 函式都使用相同的 C 函式來替位元組碼求值，因此我們無法知道
哪個 Python 函式是對應於哪個位元組碼計算函式。

作為替代，如果我們在啟用 ‘perf’ 支援的情況下執行相同的實驗，我們會得到：

     $ perf report --stdio -n -g

     # Children      Self       Samples  Command     Shared Object       Symbol
     # ........  ........  ............  ..........  ..................  .....................................................................
     #
         90.58%     0.36%             1  python.exe  python.exe          [.] _start
                 |
                 ---_start
                 |
                     --89.86%--__libc_start_main
                             Py_BytesMain
                             |
                             |--55.43%--pymain_run_python.constprop.0
                             |          |
                             |          |--54.71%--_PyRun_AnyFileObject
                             |          |          _PyRun_SimpleFileObject
                             |          |          |
                             |          |          |--53.62%--run_mod
                             |          |          |          |
                             |          |          |           --53.26%--PyEval_EvalCode
                             |          |          |                     py::<module>:/src/script.py
                             |          |          |                     _PyEval_EvalFrameDefault
                             |          |          |                     PyObject_Vectorcall
                             |          |          |                     _PyEval_Vector
                             |          |          |                     py::baz:/src/script.py
                             |          |          |                     _PyEval_EvalFrameDefault
                             |          |          |                     PyObject_Vectorcall
                             |          |          |                     _PyEval_Vector
                             |          |          |                     py::bar:/src/script.py
                             |          |          |                     _PyEval_EvalFrameDefault
                             |          |          |                     PyObject_Vectorcall
                             |          |          |                     _PyEval_Vector
                             |          |          |                     py::foo:/src/script.py
                             |          |          |                     |
                             |          |          |                     |--51.81%--_PyEval_EvalFrameDefault
                             |          |          |                     |          |
                             |          |          |                     |          |--13.77%--_PyLong_Add
                             |          |          |                     |          |          |
                             |          |          |                     |          |          |--3.26%--_PyObject_Malloc

* Menu:

* 如何啟用 perf 分析支援::
* 如何獲得最佳結果::
* How to work without frame pointers::

   ---------- Footnotes ----------

   (1) https://perf.wiki.kernel.org


File: python.info,  Node: 如何啟用 perf 分析支援,  Next: 如何獲得最佳結果,  Up: Python 對 Linux perf 分析器的支援

9.17.1 如何啟用 ‘perf’ 分析支援
-------------------------------

要啟用 ‘perf’ 分析支援，可以在一開始就使用環境變數 *note
PYTHONPERFSUPPORT: 415. 或使用 *note -X perf: 15a. 選項，也可以使用
*note sys.activate_stack_trampoline(): 416. 和 *note
sys.deactivate_stack_trampoline(): 417. 來動態啟用。

‘sys’ 函式優先於 ‘-X’ 選項、‘-X’ 選項優先於環境變數。

例如，使用環境變數：

     $ PYTHONPERFSUPPORT=1 perf record -F 9999 -g -o perf.data python script.py
     $ perf report -g -i perf.data

例如，使用 ‘-X’ 選項：

     $ perf record -F 9999 -g -o perf.data python -X perf script.py
     $ perf report -g -i perf.data

例如，在 ‘example.py’ 檔案中使用 *note sys: c3. API：

     import sys

     sys.activate_stack_trampoline("perf")
     do_profiled_stuff()
     sys.deactivate_stack_trampoline()

     non_profiled_stuff()

...然後：

     $ perf record -F 9999 -g -o perf.data python ./example.py
     $ perf report -g -i perf.data


File: python.info,  Node: 如何獲得最佳結果,  Next: How to work without frame pointers,  Prev: 如何啟用 perf 分析支援,  Up: Python 對 Linux perf 分析器的支援

9.17.2 如何獲得最佳結果
-----------------------

為了獲得最佳結果，應使用 ‘CFLAGS="-fno-omit-frame-pointer
-mno-omit-leaf-frame-pointer"’ 來進行 Python 編譯，因為這能允許分析器僅
使用 frame 指標而不是 DWARF 除錯資訊來解析 (unwind)。這是因為，由於插入
以允許 ‘perf’ 支援的程式碼是動態生成的，因此它沒有任何可用的 DWARF 除錯
資訊。

你可以透過執行以下指令來檢查你的系統是否已使用此旗標進行編譯：

     $ python -m sysconfig | grep 'no-omit-frame-pointer'

如果你沒有看到任何輸出，則表示你的直譯器尚未使用 frame 指標進行編譯，因
此它可能無法在 ‘perf’ 的輸出中顯示 Python 函式。


File: python.info,  Node: How to work without frame pointers,  Prev: 如何獲得最佳結果,  Up: Python 對 Linux perf 分析器的支援

9.17.3 How to work without frame pointers
-----------------------------------------

If you are working with a Python interpreter that has been compiled
without frame pointers, you can still use the ‘perf’ profiler, but the
overhead will be a bit higher because Python needs to generate unwinding
information for every Python function call on the fly.  Additionally,
‘perf’ will take more time to process the data because it will need to
use the DWARF debugging information to unwind the stack and this is a
slow process.

To enable this mode, you can use the environment variable *note
PYTHON_PERF_JIT_SUPPORT: 176. or the *note -X perf_jit: 15a. option,
which will enable the JIT mode for the ‘perf’ profiler.

     備註: Due to a bug in the ‘perf’ tool, only ‘perf’ versions higher
     than v6.8 will work with the JIT mode.  The fix was also backported
     to the v6.7.2 version of the tool.

     Note that when checking the version of the ‘perf’ tool (which can
     be done by running ‘perf version’) you must take into account that
     some distros add some custom version numbers including a ‘-’
     character.  This means that ‘perf 6.7-3’ is not necessarily ‘perf
     6.7.3’.

When using the perf JIT mode, you need an extra step before you can run
‘perf report’.  You need to call the ‘perf inject’ command to inject the
JIT information into the ‘perf.data’ file.:

     $ perf record -F 9999 -g --call-graph dwarf -o perf.data python -Xperf_jit my_script.py
     $ perf inject -i perf.data --jit --output perf.jit.data
     $ perf report -g -i perf.jit.data

or using the environment variable:

     $ PYTHON_PERF_JIT_SUPPORT=1 perf record -F 9999 -g --call-graph dwarf -o perf.data python my_script.py
     $ perf inject -i perf.data --jit --output perf.jit.data
     $ perf report -g -i perf.jit.data

‘perf inject --jit’ command will read ‘perf.data’, automatically pick up
the perf dump file that Python creates (in ‘/tmp/perf-$PID.dump’), and
then create ‘perf.jit.data’ which merges all the JIT information
together.  It should also create a lot of ‘jitted-XXXX-N.so’ files in
the current directory which are ELF images for all the JIT trampolines
that were created by Python.

     警告: Notice that when using ‘--call-graph dwarf’ the ‘perf’ tool
     will take snapshots of the stack of the process being profiled and
     save the information in the ‘perf.data’ file.  By default the size
     of the stack dump is 8192 bytes but the user can change the size by
     passing the size after comma like ‘--call-graph dwarf,4096’.  The
     size of the stack dump is important because if the size is too
     small ‘perf’ will not be able to unwind the stack and the output
     will be incomplete.  On the other hand, if the size is too big,
     then ‘perf’ won't be able to sample the process as frequently as it
     would like as the overhead will be higher.


File: python.info,  Node: 註釋 annotation 最佳實踐,  Next: 隔離擴充模組,  Prev: Python 對 Linux perf 分析器的支援,  Up: Python 如何達成任務

9.18 註釋 (annotation) 最佳實踐
===============================


作者: Larry Hastings

摘要
....

本文件旨在封裝 (encapsulate) 使用註釋字典 (annotations dicts) 的最佳實踐
。如果你寫 Python 程式碼並在調查 Python 物件上的 ‘__annotations__’ ，我
們鼓勵你遵循下面描述的準則。

本文件分為四個部分：在 Python 3.10 及更高版本中存取物件註釋的最佳實踐、
在 Python 3.9 及更早版本中存取物件註釋的最佳實踐、適用於任何Python 版本
‘__annotations__’ 的最佳實踐，以及 ‘__annotations__’ 的奇異之處。

請注意，本文件是特別說明 ‘__annotations__’ 的使用，而非'如何使用'註釋。
如果你正在尋找如何在你的程式碼中使用「型別提示 (type hint)」的資訊，請查
閱模組 (module) *note typing: ed.。

* Menu:

* 在 Python 3.10 及更高版本中存取物件的註釋字典: 在 Python 3 10 及更高版本中存取物件的註釋字典.
* 在 Python 3.9 及更早版本中存取物件的註釋字典: 在 Python 3 9 及更早版本中存取物件的註釋字典.
* 手動取消字串化註釋::
* 任何 Python 版本中 __annotations__ 的最佳實踐::
* __annotations__ 奇異之處::


File: python.info,  Node: 在 Python 3 10 及更高版本中存取物件的註釋字典,  Next: 在 Python 3 9 及更早版本中存取物件的註釋字典,  Up: 註釋 annotation 最佳實踐

9.18.1 在 Python 3.10 及更高版本中存取物件的註釋字典
----------------------------------------------------

Python 3.10 在標準函式庫中新增了一個新函式：*note
inspect.get_annotations(): 7b7.。在 Python 3.10 及更高版本中，呼叫此函式
是存取任何支援註釋的物件的註釋字典的最佳實踐。此函式也可以為你「取消字串
化 (un-stringize)」字串化註釋。

若由於某種原因 *note inspect.get_annotations(): 7b7. 對你的場合不可行，
你可以手動存取 ‘__annotations__’ 資料成員。 Python 3.10 中的最佳實踐也已
經改變：從 Python 3.10 開始，保證 ‘o.__annotations__’ '始終'適用於
Python 函式、類別 (class) 和模組。如果你確定正在檢查的物件是這三個'特定
'物件之一，你可以簡單地使用 ‘o.__annotations__’ 來取得物件的註釋字典。

但是，其他型別的 callable（可呼叫物件）（例如，由 *note
functools.partial(): 356. 建立的 callable）可能沒有定義
‘__annotations__’ 屬性 (attribute)。當存取可能未知的物件的
‘__annotations__’ 時，Python 3.10 及更高版本中的最佳實踐是使用三個參數呼
叫 *note getattr(): b78.，例如 ‘getattr(o, '__annotations__', None)’。

在 Python 3.10 之前，存取未定義註釋但具有註釋的父類別的類別上的
‘__annotations__’ 將傳回父類別的 ‘__annotations__’。在 Python 3.10 及更
高版本中，子類別的註釋將會是一個空字典。


File: python.info,  Node: 在 Python 3 9 及更早版本中存取物件的註釋字典,  Next: 手動取消字串化註釋,  Prev: 在 Python 3 10 及更高版本中存取物件的註釋字典,  Up: 註釋 annotation 最佳實踐

9.18.2 在 Python 3.9 及更早版本中存取物件的註釋字典
---------------------------------------------------

在 Python 3.9 及更早版本中，存取物件的註釋字典比新版本複雜得多。問題出在
於這些舊版 Python 中有設計缺陷，特別是與類別註釋有關的設計缺陷。

存取其他物件（如函式、其他 callable 和模組）的註釋字典的最佳實踐與 3.10
的最佳實踐相同，假設你沒有呼叫 *note inspect.get_annotations(): 7b7.：你
應該使用三個：參數 *note getattr(): b78. 來存取物件的 ‘__annotations__’
屬性。

不幸的是，這不是類別的最佳實踐。問題是，由於 ‘__annotations__’ 在類別上
是選填的 (optional)，並且因為類別可以從其基底類別 (base class) 繼承屬性
，所以存取類別的 ‘__annotations__’ 屬性可能會無意中回傳'基底類別的註釋字
典。'舉例來說：

     class Base:
         a: int = 3
         b: str = 'abc'

     class Derived(Base):
         pass

     print(Derived.__annotations__)

這將印出 (print) 來自 ‘Base’ 的註釋字典，而不是 ‘Derived’。

如果你正在檢查的物件是一個類別 (‘isinstance(o, type)’)，你的程式碼將必須
有一個單獨的程式碼路徑。在這種情況下，最佳實踐依賴 Python 3.9 及之前版本
的實作細節 (implementation detail)：如果一個類別定義了註釋，它們將儲存在
該類別的 ‘__dict__’ 字典中。由於類別可能定義了註釋，也可能沒有定義，因此
最佳實踐是在類別字典上呼叫 ‘get’ 方法。

總而言之，以下是一些範例程式碼，可以安全地存取 Python 3.9 及先前版本中任
意物件上的 ‘__annotations__’ 屬性：

     if isinstance(o, type):
         ann = o.__dict__.get('__annotations__', None)
     else:
         ann = getattr(o, '__annotations__', None)

運行此程式碼後，‘ann’ 應該是字典或 ‘None’。我們鼓勵你在進一步檢查之前使
用 *note isinstance(): 3e8. 仔細檢查 ‘ann’ 的型別。

請注意，某些外來 (exotic) 或格式錯誤 (malform) 的型別物件可能沒有
‘__dict__’ 屬性，因此為了額外的安全，你可能還希望使用 *note getattr():
b78. 來存取 ‘__dict__’ 。


File: python.info,  Node: 手動取消字串化註釋,  Next: 任何 Python 版本中 __annotations__ 的最佳實踐,  Prev: 在 Python 3 9 及更早版本中存取物件的註釋字典,  Up: 註釋 annotation 最佳實踐

9.18.3 手動取消字串化註釋
-------------------------

在某些註釋可能被「字串化」的情況下，並且你希望評估這些字串以產生它們表示
的 Python 值，最好呼叫 *note inspect.get_annotations(): 7b7. 來為你完成
這項工作。

如果你使用的是 Python 3.9 或更早版本，或者由於某種原因你無法使用 *note
inspect.get_annotations(): 7b7.，則需要複製其邏輯。我們鼓勵你檢查目前
Python 版本中 *note inspect.get_annotations(): 7b7. 的實作並遵循類似的方
法。

簡而言之，如果你希望評估任意物件 ‘o’ 上的字串化註釋：

   * 如果 ‘o’ 是一個模組，則在呼叫 *note eval(): 163. 時使用
     ‘o.__dict__’ 作為‘全域變數’。

   * 如果 ‘o’ 是一個類別，當呼叫 *note eval(): 163. 時，則使用
     ‘sys.modules[o.__module__].__dict__’ 作為‘全域變數’，使用
     ‘dict(vars(o))’ 作為‘區域變數’。

   * 如果 ‘o’ 是使用 *note functools.update_wrapper(): fc5.、*note
     functools.wraps(): f00. 或 *note functools.partial(): 356. 包裝的
     callable ，請依據需求，透過存取 ‘o.__wrapped__’ 或 ‘o.func’ 來疊代
     解開它，直到找到根解包函式。

   * 如果 ‘o’ 是 callable（但不是類別），則在呼叫 *note eval(): 163. 時
     使用 *note o.__globals__: 1266. 作為全域變數。

然而，並非所有用作註釋的字串值都可以透過 *note eval(): 163. 成功轉換為
Python 值。理論上，字串值可以包含任何有效的字串，並且在實踐中，型別提示
存在有效的用例，需要使用特定「無法」評估的字串值進行註釋。例如：

   * 在 Python 3.10 支援 PEP 604(1) 聯合型別 (union type) ‘|’ 之前使用它
     。

   * Runtime 中不需要的定義，僅在 *note typing.TYPE_CHECKING: c9b. 為
     true 時匯入。

如果 *note eval(): 163. 嘗試計算這類型的值，它將失敗並引發例外。因此，在
設計使用註釋的函式庫 API 時，建議僅在呼叫者 (caller) 明確請求時嘗試評估
字串值。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0604/


File: python.info,  Node: 任何 Python 版本中 __annotations__ 的最佳實踐,  Next: __annotations__ 奇異之處,  Prev: 手動取消字串化註釋,  Up: 註釋 annotation 最佳實踐

9.18.4 任何 Python 版本中 ‘__annotations__’ 的最佳實踐
------------------------------------------------------

   * 你應該避免直接指派給物件的 ‘__annotations__’ 成員。讓 Python 管理設
     定 ‘__annotations__’。

   * 如果你直接指派給物件的 ‘__annotations__’ 成員，則應始終將其設為
     ‘dict’ 物件。

   * 如果直接存取物件的 ‘__annotations__’ 成員，則應在嘗試檢查其內容之前
     確保它是字典。

   * 你應該避免修改 ‘__annotations__’ 字典。

   * 你應該避免刪除物件的 ‘__annotations__’ 屬性。


File: python.info,  Node: __annotations__ 奇異之處,  Prev: 任何 Python 版本中 __annotations__ 的最佳實踐,  Up: 註釋 annotation 最佳實踐

9.18.5 ‘__annotations__’ 奇異之處
---------------------------------

在 Python 3 的所有版本中，如果沒有在該物件上定義註釋，則函式物件會延遲建
立 (lazy-create) 註釋字典。你可以使用 ‘del fn.__annotations__’ 刪除
‘__annotations__’ 屬性，但如果你隨後存取 ‘fn.__annotations__’，該物件將
建立一個新的空字典，它將作為註釋儲存並傳回。在函式延遲建立註釋字典之前刪
除函式上的註釋將拋出 ‘AttributeError’；連續兩次使用 ‘del
fn.__annotations__’ 保證總是拋出 ‘AttributeError’ 。

上一段的所有內容也適用於 Python 3.10 及更高版本中的類別和模組物件。

在 Python 3 的所有版本中，你可以將函式物件上的 ‘__annotations__’ 設定為
‘None’。但是，隨後使用 ‘fn.__annotations__’ 存取該物件上的註釋將根據本節
第一段的內容延遲建立一個空字典。對於任何 Python 版本中的模組和類別來說，
情況'並非如此'；這些物件允許將 ‘__annotations__’ 設定為任何 Python 值，
並且將保留設定的任何值。

如果 Python 為你字串化你的註釋（使用 ‘from __future__ import
annotations’），並且你指定一個字串作為註釋，則該字串本身將被引用。實際上
，註釋被引用了'兩次。'例如：

     from __future__ import annotations
     def foo(a: "str"): pass

     print(foo.__annotations__)

這會印出 ‘{'a': "'str'"}’。這不應該被認為是一個「奇異的事」，他在這裡被
簡單提及，因為他可能會讓人意想不到。


File: python.info,  Node: 隔離擴充模組,  Next: timer file descriptor HOWTO,  Prev: 註釋 annotation 最佳實踐,  Up: Python 如何達成任務

9.19 隔離擴充模組
=================

摘要
....

Traditionally, state belonging to Python extension modules was kept in C
‘static’ variables, which have process-wide scope.  This document
describes problems of such per-process state and shows a safer way:
per-module state.

The document also describes how to switch to per-module state where
possible.  This transition involves allocating space for that state,
potentially switching from static types to heap types, and—perhaps most
importantly—accessing per-module state from code.

* Menu:

* Who should read this::
* 背景: 背景<2>.
* Making Modules Safe with Multiple Interpreters::
* Heap Types: Heap Types<2>.
* Open Issues::


File: python.info,  Node: Who should read this,  Next: 背景<2>,  Up: 隔離擴充模組

9.19.1 Who should read this
---------------------------

This guide is written for maintainers of *note C-API: 1ae2. extensions
who would like to make that extension safer to use in applications where
Python itself is used as a library.


File: python.info,  Node: 背景<2>,  Next: Making Modules Safe with Multiple Interpreters,  Prev: Who should read this,  Up: 隔離擴充模組

9.19.2 背景
-----------

An 'interpreter' is the context in which Python code runs.  It contains
configuration (e.g.  the import path) and runtime state (e.g.  the set
of imported modules).

Python supports running multiple interpreters in one process.  There are
two cases to think about—users may run interpreters:

   - in sequence, with several *note Py_InitializeEx(): 48bc./*note
     Py_FinalizeEx(): cbc. cycles, and

   - in parallel, managing "sub-interpreters" using *note
     Py_NewInterpreter(): 16b9./*note Py_EndInterpreter(): 1762.

Both cases (and combinations of them) would be most useful when
embedding Python within a library.  Libraries generally shouldn't make
assumptions about the application that uses them, which include assuming
a process-wide "main Python interpreter".

Historically, Python extension modules don't handle this use case well.
Many extension modules (and even some stdlib modules) use 'per-process'
global state, because C ‘static’ variables are extremely easy to use.
Thus, data that should be specific to an interpreter ends up being
shared between interpreters.  Unless the extension developer is careful,
it is very easy to introduce edge cases that lead to crashes when a
module is loaded in more than one interpreter in the same process.

Unfortunately, 'per-interpreter' state is not easy to achieve.
Extension authors tend to not keep multiple interpreters in mind when
developing, and it is currently cumbersome to test the behavior.

* Menu:

* Enter Per-Module State::
* Isolated Module Objects::
* Surprising Edge Cases::


File: python.info,  Node: Enter Per-Module State,  Next: Isolated Module Objects,  Up: 背景<2>

9.19.2.1 Enter Per-Module State
...............................

Instead of focusing on per-interpreter state, Python's C API is evolving
to better support the more granular 'per-module' state.  This means that
C-level data should be attached to a 'module object'.  Each interpreter
creates its own module object, keeping the data separate.  For testing
the isolation, multiple module objects corresponding to a single
extension can even be loaded in a single interpreter.

Per-module state provides an easy way to think about lifetime and
resource ownership: the extension module will initialize when a module
object is created, and clean up when it's freed.  In this regard, a
module is just like any other *note PyObject: 311.*; there are no "on
interpreter shutdown" hooks to think—or forget—about.

Note that there are use cases for different kinds of "globals":
per-process, per-interpreter, per-thread or per-task state.  With
per-module state as the default, these are still possible, but you
should treat them as exceptional cases: if you need them, you should
give them additional care and testing.  (Note that this guide does not
cover them.)


File: python.info,  Node: Isolated Module Objects,  Next: Surprising Edge Cases,  Prev: Enter Per-Module State,  Up: 背景<2>

9.19.2.2 Isolated Module Objects
................................

The key point to keep in mind when developing an extension module is
that several module objects can be created from a single shared library.
For example:

     >>> import sys
     >>> import binascii
     >>> old_binascii = binascii
     >>> del sys.modules['binascii']
     >>> import binascii  # create a new module object
     >>> old_binascii == binascii
     False

As a rule of thumb, the two modules should be completely independent.
All objects and state specific to the module should be encapsulated
within the module object, not shared with other module objects, and
cleaned up when the module object is deallocated.  Since this just is a
rule of thumb, exceptions are possible (see *note Managing Global State:
4e21.), but they will need more thought and attention to edge cases.

While some modules could do with less stringent restrictions, isolated
modules make it easier to set clear expectations and guidelines that
work across a variety of use cases.


File: python.info,  Node: Surprising Edge Cases,  Prev: Isolated Module Objects,  Up: 背景<2>

9.19.2.3 Surprising Edge Cases
..............................

Note that isolated modules do create some surprising edge cases.  Most
notably, each module object will typically not share its classes and
exceptions with other similar modules.  Continuing from the *note
example above: 4e20, note that ‘old_binascii.Error’ and ‘binascii.Error’
are separate objects.  In the following code, the exception is 'not'
caught:

     >>> old_binascii.Error == binascii.Error
     False
     >>> try:
     ...     old_binascii.unhexlify(b'qwertyuiop')
     ... except binascii.Error:
     ...     print('boo')
     ...
     Traceback (most recent call last):
       File "<stdin>", line 2, in <module>
     binascii.Error: Non-hexadecimal digit found

This is expected.  Notice that pure-Python modules behave the same way:
it is a part of how Python works.

The goal is to make extension modules safe at the C level, not to make
hacks behave intuitively.  Mutating ‘sys.modules’ "manually" counts as a
hack.


File: python.info,  Node: Making Modules Safe with Multiple Interpreters,  Next: Heap Types<2>,  Prev: 背景<2>,  Up: 隔離擴充模組

9.19.3 Making Modules Safe with Multiple Interpreters
-----------------------------------------------------

* Menu:

* Managing Global State::
* Managing Per-Module State::
* Opt-Out; Limiting to One Module Object per Process: Opt-Out Limiting to One Module Object per Process.
* Module State Access from Functions::


File: python.info,  Node: Managing Global State,  Next: Managing Per-Module State,  Up: Making Modules Safe with Multiple Interpreters

9.19.3.1 Managing Global State
..............................

Sometimes, the state associated with a Python module is not specific to
that module, but to the entire process (or something else "more global"
than a module).  For example:

   - The ‘readline’ module manages 'the' terminal.

   - A module running on a circuit board wants to control 'the' on-board
     LED.

In these cases, the Python module should provide 'access' to the global
state, rather than 'own' it.  If possible, write the module so that
multiple copies of it can access the state independently (along with
other libraries, whether for Python or other languages).  If that is not
possible, consider explicit locking.

If it is necessary to use process-global state, the simplest way to
avoid issues with multiple interpreters is to explicitly prevent a
module from being loaded more than once per process—see *note Opt-Out;
Limiting to One Module Object per Process: 4e24.


File: python.info,  Node: Managing Per-Module State,  Next: Opt-Out Limiting to One Module Object per Process,  Prev: Managing Global State,  Up: Making Modules Safe with Multiple Interpreters

9.19.3.2 Managing Per-Module State
..................................

To use per-module state, use *note multi-phase extension module
initialization: 4732.  This signals that your module supports multiple
interpreters correctly.

Set ‘PyModuleDef.m_size’ to a positive number to request that many bytes
of storage local to the module.  Usually, this will be set to the size
of some module-specific ‘struct’, which can store all of the module's
C-level state.  In particular, it is where you should put pointers to
classes (including exceptions, but excluding static types) and settings
(e.g.  ‘csv’'s *note field_size_limit: 170b.) which the C code needs to
function.

     備註: Another option is to store state in the module's ‘__dict__’,
     but you must avoid crashing when users modify ‘__dict__’ from
     Python code.  This usually means error- and type-checking at the C
     level, which is easy to get wrong and hard to test sufficiently.

     However, if module state is not needed in C code, storing it in
     ‘__dict__’ only is a good idea.

If the module state includes ‘PyObject’ pointers, the module object must
hold references to those objects and implement the module-level hooks
‘m_traverse’, ‘m_clear’ and ‘m_free’.  These work like ‘tp_traverse’,
‘tp_clear’ and ‘tp_free’ of a class.  Adding them will require some work
and make the code longer; this is the price for modules which can be
unloaded cleanly.

An example of a module with per-module state is currently available as
xxlimited(1); example module initialization shown at the bottom of the
file.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/blob/master/Modules/xxlimited.c


File: python.info,  Node: Opt-Out Limiting to One Module Object per Process,  Next: Module State Access from Functions,  Prev: Managing Per-Module State,  Up: Making Modules Safe with Multiple Interpreters

9.19.3.3 Opt-Out: Limiting to One Module Object per Process
...........................................................

A non-negative ‘PyModuleDef.m_size’ signals that a module supports
multiple interpreters correctly.  If this is not yet the case for your
module, you can explicitly make your module loadable only once per
process.  For example:

     static int loaded = 0;

     static int
     exec_module(PyObject* module)
     {
         if (loaded) {
             PyErr_SetString(PyExc_ImportError,
                             "cannot load module more than once per process");
             return -1;
         }
         loaded = 1;
         // ... rest of initialization
     }


File: python.info,  Node: Module State Access from Functions,  Prev: Opt-Out Limiting to One Module Object per Process,  Up: Making Modules Safe with Multiple Interpreters

9.19.3.4 Module State Access from Functions
...........................................

Accessing the state from module-level functions is straightforward.
Functions get the module object as their first argument; for extracting
the state, you can use ‘PyModule_GetState’:

     static PyObject *
     func(PyObject *module, PyObject *args)
     {
         my_struct *state = (my_struct*)PyModule_GetState(module);
         if (state == NULL) {
             return NULL;
         }
         // ... rest of logic
     }

     備註: ‘PyModule_GetState’ may return ‘NULL’ without setting an
     exception if there is no module state, i.e.  ‘PyModuleDef.m_size’
     was zero.  In your own module, you're in control of ‘m_size’, so
     this is easy to prevent.


File: python.info,  Node: Heap Types<2>,  Next: Open Issues,  Prev: Making Modules Safe with Multiple Interpreters,  Up: 隔離擴充模組

9.19.4 Heap Types
-----------------

Traditionally, types defined in C code are 'static'; that is, ‘static
PyTypeObject’ structures defined directly in code and initialized using
‘PyType_Ready()’.

Such types are necessarily shared across the process.  Sharing them
between module objects requires paying attention to any state they own
or access.  To limit the possible issues, static types are immutable at
the Python level: for example, you can't set ‘str.myattribute = 123’.

'CPython 實作細節：' Sharing truly immutable objects between
interpreters is fine, as long as they don't provide access to mutable
objects.  However, in CPython, every Python object has a mutable
implementation detail: the reference count.  Changes to the refcount are
guarded by the GIL. Thus, code that shares any Python objects across
interpreters implicitly depends on CPython's current, process-wide GIL.

Because they are immutable and process-global, static types cannot
access "their" module state.  If any method of such a type requires
access to module state, the type must be converted to a 'heap-allocated
type', or 'heap type' for short.  These correspond more closely to
classes created by Python's ‘class’ statement.

For new modules, using heap types by default is a good rule of thumb.

* Menu:

* Changing Static Types to Heap Types::
* Defining Heap Types::
* Garbage-Collection Protocol::
* Module State Access from Classes::
* Module State Access from Regular Methods::
* Module State Access from Slot Methods, Getters and Setters: Module State Access from Slot Methods Getters and Setters.
* Lifetime of the Module State::


File: python.info,  Node: Changing Static Types to Heap Types,  Next: Defining Heap Types,  Up: Heap Types<2>

9.19.4.1 Changing Static Types to Heap Types
............................................

Static types can be converted to heap types, but note that the heap type
API was not designed for "lossless" conversion from static types—that
is, creating a type that works exactly like a given static type.  So,
when rewriting the class definition in a new API, you are likely to
unintentionally change a few details (e.g.  pickleability or inherited
slots).  Always test the details that are important to you.

Watch out for the following two points in particular (but note that this
is not a comprehensive list):

   * Unlike static types, heap type objects are mutable by default.  Use
     the *note Py_TPFLAGS_IMMUTABLETYPE: 38d. flag to prevent
     mutability.

   * Heap types inherit *note tp_new: 525. by default, so it may become
     possible to instantiate them from Python code.  You can prevent
     this with the *note Py_TPFLAGS_DISALLOW_INSTANTIATION: 528. flag.


File: python.info,  Node: Defining Heap Types,  Next: Garbage-Collection Protocol,  Prev: Changing Static Types to Heap Types,  Up: Heap Types<2>

9.19.4.2 Defining Heap Types
............................

Heap types can be created by filling a *note PyType_Spec: 1618.
structure, a description or "blueprint" of a class, and calling *note
PyType_FromModuleAndSpec(): 4f7. to construct a new class object.

     備註: Other functions, like *note PyType_FromSpec(): 523, can also
     create heap types, but *note PyType_FromModuleAndSpec(): 4f7.
     associates the module with the class, allowing access to the module
     state from methods.

The class should generally be stored in 'both' the module state (for
safe access from C) and the module's ‘__dict__’ (for access from Python
code).


File: python.info,  Node: Garbage-Collection Protocol,  Next: Module State Access from Classes,  Prev: Defining Heap Types,  Up: Heap Types<2>

9.19.4.3 Garbage-Collection Protocol
....................................

Instances of heap types hold a reference to their type.  This ensures
that the type isn't destroyed before all its instances are, but may
result in reference cycles that need to be broken by the garbage
collector.

To avoid memory leaks, instances of heap types must implement the
garbage collection protocol.  That is, heap types should:

   - Have the *note Py_TPFLAGS_HAVE_GC: 720. flag.

   - Define a traverse function using ‘Py_tp_traverse’, which visits the
     type (e.g.  using ‘Py_VISIT(Py_TYPE(self))’).

Please refer to the documentation of *note Py_TPFLAGS_HAVE_GC: 720. and
*note tp_traverse: 721. for additional considerations.

The API for defining heap types grew organically, leaving it somewhat
awkward to use in its current state.  The following sections will guide
you through common issues.

* Menu:

* tp_traverse in Python 3.8 and lower: tp_traverse in Python 3 8 and lower.
* Delegating tp_traverse::
* Defining tp_dealloc::
* Not overriding tp_free::
* Avoiding PyObject_New::


File: python.info,  Node: tp_traverse in Python 3 8 and lower,  Next: Delegating tp_traverse,  Up: Garbage-Collection Protocol

9.19.4.4 ‘tp_traverse’ in Python 3.8 and lower
..............................................

The requirement to visit the type from ‘tp_traverse’ was added in Python
3.9.  If you support Python 3.8 and lower, the traverse function must
'not' visit the type, so it must be more complicated:

     static int my_traverse(PyObject *self, visitproc visit, void *arg)
     {
         if (Py_Version >= 0x03090000) {
             Py_VISIT(Py_TYPE(self));
         }
         return 0;
     }

Unfortunately, *note Py_Version: 6fa. was only added in Python 3.11.  As
a replacement, use:

   * *note PY_VERSION_HEX: 6fb, if not using the stable ABI, or

   * *note sys.version_info: 645. (via *note PySys_GetObject(): 35d. and
     *note PyArg_ParseTuple(): 517.).


File: python.info,  Node: Delegating tp_traverse,  Next: Defining tp_dealloc,  Prev: tp_traverse in Python 3 8 and lower,  Up: Garbage-Collection Protocol

9.19.4.5 Delegating ‘tp_traverse’
.................................

If your traverse function delegates to the *note tp_traverse: 721. of
its base class (or another type), ensure that ‘Py_TYPE(self)’ is visited
only once.  Note that only heap type are expected to visit the type in
‘tp_traverse’.

For example, if your traverse function includes:

     base->tp_traverse(self, visit, arg)

...and ‘base’ may be a static type, then it should also include:

     if (base->tp_flags & Py_TPFLAGS_HEAPTYPE) {
         // a heap type's tp_traverse already visited Py_TYPE(self)
     } else {
         if (Py_Version >= 0x03090000) {
             Py_VISIT(Py_TYPE(self));
         }
     }

It is not necessary to handle the type's reference count in *note
tp_new: 525. and *note tp_clear: 4717.


File: python.info,  Node: Defining tp_dealloc,  Next: Not overriding tp_free,  Prev: Delegating tp_traverse,  Up: Garbage-Collection Protocol

9.19.4.6 Defining ‘tp_dealloc’
..............................

If your type has a custom *note tp_dealloc: 4704. function, it needs to:

   - call *note PyObject_GC_UnTrack(): 1475. before any fields are
     invalidated, and

   - decrement the reference count of the type.

To keep the type valid while ‘tp_free’ is called, the type's refcount
needs to be decremented 'after' the instance is deallocated.  For
example:

     static void my_dealloc(PyObject *self)
     {
         PyObject_GC_UnTrack(self);
         ...
         PyTypeObject *type = Py_TYPE(self);
         type->tp_free(self);
         Py_DECREF(type);
     }

The default ‘tp_dealloc’ function does this, so if your type does 'not'
override ‘tp_dealloc’ you don't need to add it.


File: python.info,  Node: Not overriding tp_free,  Next: Avoiding PyObject_New,  Prev: Defining tp_dealloc,  Up: Garbage-Collection Protocol

9.19.4.7 Not overriding ‘tp_free’
.................................

The *note tp_free: 4705. slot of a heap type must be set to *note
PyObject_GC_Del(): 1473.  This is the default; do not override it.


File: python.info,  Node: Avoiding PyObject_New,  Prev: Not overriding tp_free,  Up: Garbage-Collection Protocol

9.19.4.8 Avoiding ‘PyObject_New’
................................

GC-tracked objects need to be allocated using GC-aware functions.

If you use use *note PyObject_New(): 929. or *note PyObject_NewVar():
92a.:

   - Get and call type's *note tp_alloc: 4706. slot, if possible.  That
     is, replace ‘TYPE *o = PyObject_New(TYPE, typeobj)’ with:

          TYPE *o = typeobj->tp_alloc(typeobj, 0);

     Replace ‘o = PyObject_NewVar(TYPE, typeobj, size)’ with the same,
     but use size instead of the 0.

   - If the above is not possible (e.g.  inside a custom ‘tp_alloc’),
     call *note PyObject_GC_New(): a45. or *note PyObject_GC_NewVar():
     a46.:

          TYPE *o = PyObject_GC_New(TYPE, typeobj);

          TYPE *o = PyObject_GC_NewVar(TYPE, typeobj, size);


File: python.info,  Node: Module State Access from Classes,  Next: Module State Access from Regular Methods,  Prev: Garbage-Collection Protocol,  Up: Heap Types<2>

9.19.4.9 Module State Access from Classes
.........................................

If you have a type object defined with *note PyType_FromModuleAndSpec():
4f7, you can call *note PyType_GetModule(): 912. to get the associated
module, and then *note PyModule_GetState(): 924. to get the module's
state.

To save a some tedious error-handling boilerplate code, you can combine
these two steps with *note PyType_GetModuleState(): 913, resulting in:

     my_struct *state = (my_struct*)PyType_GetModuleState(type);
     if (state == NULL) {
         return NULL;
     }


File: python.info,  Node: Module State Access from Regular Methods,  Next: Module State Access from Slot Methods Getters and Setters,  Prev: Module State Access from Classes,  Up: Heap Types<2>

9.19.4.10 Module State Access from Regular Methods
..................................................

Accessing the module-level state from methods of a class is somewhat
more complicated, but is possible thanks to API introduced in Python
3.9.  To get the state, you need to first get the 'defining class', and
then get the module state from it.

The largest roadblock is getting 'the class a method was defined in', or
that method's "defining class" for short.  The defining class can have a
reference to the module it is part of.

Do not confuse the defining class with ‘Py_TYPE(self)’.  If the method
is called on a 'subclass' of your type, ‘Py_TYPE(self)’ will refer to
that subclass, which may be defined in different module than yours.

     備註: The following Python code can illustrate the concept.
     ‘Base.get_defining_class’ returns ‘Base’ even if ‘type(self) ==
     Sub’:

          class Base:
              def get_type_of_self(self):
                  return type(self)

              def get_defining_class(self):
                  return __class__

          class Sub(Base):
              pass

For a method to get its "defining class", it must use the *note
METH_METHOD | METH_FASTCALL | METH_KEYWORDS: 1584. *note calling
convention: 1446. and the corresponding *note PyCMethod: 708. signature:

     PyObject *PyCMethod(
         PyObject *self,               // object the method was called on
         PyTypeObject *defining_class, // defining class
         PyObject *const *args,        // C array of arguments
         Py_ssize_t nargs,             // length of "args"
         PyObject *kwnames)            // NULL, or dict of keyword arguments

Once you have the defining class, call *note PyType_GetModuleState():
913. to get the state of its associated module.

For example:

     static PyObject *
     example_method(PyObject *self,
             PyTypeObject *defining_class,
             PyObject *const *args,
             Py_ssize_t nargs,
             PyObject *kwnames)
     {
         my_struct *state = (my_struct*)PyType_GetModuleState(defining_class);
         if (state == NULL) {
             return NULL;
         }
         ... // rest of logic
     }

     PyDoc_STRVAR(example_method_doc, "...");

     static PyMethodDef my_methods[] = {
         {"example_method",
           (PyCFunction)(void(*)(void))example_method,
           METH_METHOD|METH_FASTCALL|METH_KEYWORDS,
           example_method_doc}
         {NULL},
     }


File: python.info,  Node: Module State Access from Slot Methods Getters and Setters,  Next: Lifetime of the Module State,  Prev: Module State Access from Regular Methods,  Up: Heap Types<2>

9.19.4.11 Module State Access from Slot Methods, Getters and Setters
....................................................................

     備註: This is new in Python 3.11.

Slot methods—the fast C equivalents for special methods, such as *note
nb_add: 49c8. for *note __add__: 1e62. or *note tp_new: 525. for
initialization—have a very simple API that doesn't allow passing in the
defining class, unlike with *note PyCMethod: 708.  The same goes for
getters and setters defined with *note PyGetSetDef: b5f.

To access the module state in these cases, use the *note
PyType_GetModuleByDef(): 342. function, and pass in the module
definition.  Once you have the module, call *note PyModule_GetState():
924. to get the state:

     PyObject *module = PyType_GetModuleByDef(Py_TYPE(self), &module_def);
     my_struct *state = (my_struct*)PyModule_GetState(module);
     if (state == NULL) {
         return NULL;
     }

‘PyType_GetModuleByDef()’ works by searching the *note method resolution
order: 205c. (i.e.  all superclasses) for the first superclass that has
a corresponding module.

     備註: In very exotic cases (inheritance chains spanning multiple
     modules created from the same definition),
     ‘PyType_GetModuleByDef()’ might not return the module of the true
     defining class.  However, it will always return a module with the
     same definition, ensuring a compatible C memory layout.


File: python.info,  Node: Lifetime of the Module State,  Prev: Module State Access from Slot Methods Getters and Setters,  Up: Heap Types<2>

9.19.4.12 Lifetime of the Module State
......................................

When a module object is garbage-collected, its module state is freed.
For each pointer to (a part of) the module state, you must hold a
reference to the module object.

Usually this is not an issue, because types created with *note
PyType_FromModuleAndSpec(): 4f7, and their instances, hold a reference
to the module.  However, you must be careful in reference counting when
you reference module state from other places, such as callbacks for
external libraries.


File: python.info,  Node: Open Issues,  Prev: Heap Types<2>,  Up: 隔離擴充模組

9.19.5 Open Issues
------------------

Several issues around per-module state and heap types are still open.

Discussions about improving the situation are best held on the capi-sig
mailing list(1).

* Menu:

* Per-Class Scope::
* Lossless Conversion to Heap Types::

   ---------- Footnotes ----------

   (1) https://mail.python.org/mailman3/lists/capi-sig.python.org/


File: python.info,  Node: Per-Class Scope,  Next: Lossless Conversion to Heap Types,  Up: Open Issues

9.19.5.1 Per-Class Scope
........................

It is currently (as of Python 3.11) not possible to attach state to
individual 'types' without relying on CPython implementation details
(which may change in the future—perhaps, ironically, to allow a proper
solution for per-class scope).


File: python.info,  Node: Lossless Conversion to Heap Types,  Prev: Per-Class Scope,  Up: Open Issues

9.19.5.2 Lossless Conversion to Heap Types
..........................................

The heap type API was not designed for "lossless" conversion from static
types; that is, creating a type that works exactly like a given static
type.


File: python.info,  Node: timer file descriptor HOWTO,  Next: The Python 2 3 Method Resolution Order,  Prev: 隔離擴充模組,  Up: Python 如何達成任務

9.20 timer file descriptor HOWTO
================================


Release: 1.13

This HOWTO discusses Python's support for the linux timer file
descriptor.

* Menu:

* Examples: Examples<2>.


File: python.info,  Node: Examples<2>,  Up: timer file descriptor HOWTO

9.20.1 Examples
---------------

The following example shows how to use a timer file descriptor to
execute a function twice a second:

     # Practical scripts should use really use a non-blocking timer,
     # we use a blocking timer here for simplicity.
     import os, time

     # Create the timer file descriptor
     fd = os.timerfd_create(time.CLOCK_REALTIME)

     # Start the timer in 1 second, with an interval of half a second
     os.timerfd_settime(fd, initial=1, interval=0.5)

     try:
         # Process timer events four times.
         for _ in range(4):
             # read() will block until the timer expires
             _ = os.read(fd, 8)
             print("Timer expired")
     finally:
         # Remember to close the timer file descriptor!
         os.close(fd)

To avoid the precision loss caused by the *note float: 2c8. type, timer
file descriptors allow specifying initial expiration and interval in
integer nanoseconds with ‘_ns’ variants of the functions.

This example shows how *note epoll(): f36. can be used with timer file
descriptors to wait until the file descriptor is ready for reading:

     import os, time, select, socket, sys

     # Create an epoll object
     ep = select.epoll()

     # In this example, use loopback address to send "stop" command to the server.
     #
     # $ telnet 127.0.0.1 1234
     # Trying 127.0.0.1...
     # Connected to 127.0.0.1.
     # Escape character is '^]'.
     # stop
     # Connection closed by foreign host.
     #
     sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
     sock.bind(("127.0.0.1", 1234))
     sock.setblocking(False)
     sock.listen(1)
     ep.register(sock, select.EPOLLIN)

     # Create timer file descriptors in non-blocking mode.
     num = 3
     fds = []
     for _ in range(num):
         fd = os.timerfd_create(time.CLOCK_REALTIME, flags=os.TFD_NONBLOCK)
         fds.append(fd)
         # Register the timer file descriptor for read events
         ep.register(fd, select.EPOLLIN)

     # Start the timer with os.timerfd_settime_ns() in nanoseconds.
     # Timer 1 fires every 0.25 seconds; timer 2 every 0.5 seconds; etc
     for i, fd in enumerate(fds, start=1):
         one_sec_in_nsec = 10**9
         i = i * one_sec_in_nsec
         os.timerfd_settime_ns(fd, initial=i//4, interval=i//4)

     timeout = 3
     try:
         conn = None
         is_active = True
         while is_active:
             # Wait for the timer to expire for 3 seconds.
             # epoll.poll() returns a list of (fd, event) pairs.
             # fd is a file descriptor.
             # sock and conn[=returned value of socket.accept()] are socket objects, not file descriptors.
             # So use sock.fileno() and conn.fileno() to get the file descriptors.
             events = ep.poll(timeout)

             # If more than one timer file descriptors are ready for reading at once,
             # epoll.poll() returns a list of (fd, event) pairs.
             #
             # In this example settings,
             #    1st timer fires every 0.25 seconds in 0.25 seconds. (0.25, 0.5, 0.75, 1.0, ...)
             #    2nd timer every 0.5 seconds in 0.5 seconds. (0.5, 1.0, 1.5, 2.0, ...)
             #    3rd timer every 0.75 seconds in 0.75 seconds. (0.75, 1.5, 2.25, 3.0, ...)
             #
             #    In 0.25 seconds, only 1st timer fires.
             #    In 0.5 seconds, 1st timer and 2nd timer fires at once.
             #    In 0.75 seconds, 1st timer and 3rd timer fires at once.
             #    In 1.5 seconds, 1st timer, 2nd timer and 3rd timer fires at once.
             #
             # If a timer file descriptor is signaled more than once since
             # the last os.read() call, os.read() returns the number of signaled
             # as host order of class bytes.
             print(f"Signaled events={events}")
             for fd, event in events:
                 if event & select.EPOLLIN:
                     if fd == sock.fileno():
                         # Check if there is a connection request.
                         print(f"Accepting connection {fd}")
                         conn, addr = sock.accept()
                         conn.setblocking(False)
                         print(f"Accepted connection {conn} from {addr}")
                         ep.register(conn, select.EPOLLIN)
                     elif conn and fd == conn.fileno():
                         # Check if there is data to read.
                         print(f"Reading data {fd}")
                         data = conn.recv(1024)
                         if data:
                             # You should catch UnicodeDecodeError exception for safety.
                             cmd = data.decode()
                             if cmd.startswith("stop"):
                                 print(f"Stopping server")
                                 is_active = False
                             else:
                                 print(f"Unknown command: {cmd}")
                         else:
                             # No more data, close connection
                             print(f"Closing connection {fd}")
                             ep.unregister(conn)
                             conn.close()
                             conn = None
                     elif fd in fds:
                         print(f"Reading timer {fd}")
                         count = int.from_bytes(os.read(fd, 8), byteorder=sys.byteorder)
                         print(f"Timer {fds.index(fd) + 1} expired {count} times")
                     else:
                         print(f"Unknown file descriptor {fd}")
     finally:
         for fd in fds:
             ep.unregister(fd)
             os.close(fd)
         ep.close()

This example shows how *note select(): d46. can be used with timer file
descriptors to wait until the file descriptor is ready for reading:

     import os, time, select, socket, sys

     # In this example, use loopback address to send "stop" command to the server.
     #
     # $ telnet 127.0.0.1 1234
     # Trying 127.0.0.1...
     # Connected to 127.0.0.1.
     # Escape character is '^]'.
     # stop
     # Connection closed by foreign host.
     #
     sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
     sock.bind(("127.0.0.1", 1234))
     sock.setblocking(False)
     sock.listen(1)

     # Create timer file descriptors in non-blocking mode.
     num = 3
     fds = [os.timerfd_create(time.CLOCK_REALTIME, flags=os.TFD_NONBLOCK)
            for _ in range(num)]
     select_fds = fds + [sock]

     # Start the timers with os.timerfd_settime() in seconds.
     # Timer 1 fires every 0.25 seconds; timer 2 every 0.5 seconds; etc
     for i, fd in enumerate(fds, start=1):
        os.timerfd_settime(fd, initial=i/4, interval=i/4)

     timeout = 3
     try:
         conn = None
         is_active = True
         while is_active:
            # Wait for the timer to expire for 3 seconds.
            # select.select() returns a list of file descriptors or objects.
            rfd, wfd, xfd = select.select(select_fds, select_fds, select_fds, timeout)
            for fd in rfd:
                if fd == sock:
                    # Check if there is a connection request.
                    print(f"Accepting connection {fd}")
                    conn, addr = sock.accept()
                    conn.setblocking(False)
                    print(f"Accepted connection {conn} from {addr}")
                    select_fds.append(conn)
                elif conn and fd == conn:
                    # Check if there is data to read.
                    print(f"Reading data {fd}")
                    data = conn.recv(1024)
                    if data:
                        # You should catch UnicodeDecodeError exception for safety.
                        cmd = data.decode()
                        if cmd.startswith("stop"):
                            print(f"Stopping server")
                            is_active = False
                        else:
                            print(f"Unknown command: {cmd}")
                    else:
                        # No more data, close connection
                        print(f"Closing connection {fd}")
                        select_fds.remove(conn)
                        conn.close()
                        conn = None
                elif fd in fds:
                    print(f"Reading timer {fd}")
                    count = int.from_bytes(os.read(fd, 8), byteorder=sys.byteorder)
                    print(f"Timer {fds.index(fd) + 1} expired {count} times")
                else:
                    print(f"Unknown file descriptor {fd}")
     finally:
         for fd in fds:
            os.close(fd)
         sock.close()
         sock = None


File: python.info,  Node: The Python 2 3 Method Resolution Order,  Next: C API Extension Support for Free Threading,  Prev: timer file descriptor HOWTO,  Up: Python 如何達成任務

9.21 The Python 2.3 Method Resolution Order
===========================================

     備註: This is a historical document, provided as an appendix to the
     official documentation.  The Method Resolution Order discussed here
     was 'introduced' in Python 2.3, but it is still used in later
     versions - including Python 3.

By Michele Simionato(1).


摘要: 'This document is intended for Python programmers who want to
understand the C3 Method Resolution Order used in Python 2.3.  Although
it is not intended for newbies, it is quite pedagogical with many worked
out examples.  I am not aware of other publicly available documents with
the same scope, therefore it should be useful.'

Disclaimer:

     'I donate this document to the Python Software Foundation, under
     the Python 2.3 license.  As usual in these circumstances, I warn
     the reader that what follows' should 'be correct, but I don't give
     any warranty.  Use it at your own risk and peril!'

致謝

     'All the people of the Python mailing list who sent me their
     support.  Paul Foley who pointed out various imprecisions and made
     me to add the part on local precedence ordering.  David Goodger for
     help with the formatting in reStructuredText.  David Mertz for help
     with the editing.  Finally, Guido van Rossum who enthusiastically
     added this document to the official Python 2.3 home-page.'

* Menu:

* The beginning::
* The C3 Method Resolution Order::
* 範例: 範例<55>.
* Bad Method Resolution Orders::
* The end::
* Resources::

   ---------- Footnotes ----------

   (1) https://www.phyast.pitt.edu/~micheles/


File: python.info,  Node: The beginning,  Next: The C3 Method Resolution Order,  Up: The Python 2 3 Method Resolution Order

9.21.1 The beginning
--------------------

     'Felix qui potuit rerum cognoscere causas' - Virgilius

Everything started with a post by Samuele Pedroni to the Python
development mailing list (1).  In his post, Samuele showed that the
Python 2.2 method resolution order is not monotonic and he proposed to
replace it with the C3 method resolution order.  Guido agreed with his
arguments and therefore now Python 2.3 uses C3.  The C3 method itself
has nothing to do with Python, since it was invented by people working
on Dylan and it is described in a paper intended for lispers (2).  The
present paper gives a (hopefully) readable discussion of the C3
algorithm for Pythonistas who want to understand the reasons for the
change.

First of all, let me point out that what I am going to say only applies
to the 'new style classes' introduced in Python 2.2: 'classic classes'
maintain their old method resolution order, depth first and then left to
right.  Therefore, there is no breaking of old code for classic classes;
and even if in principle there could be breaking of code for Python 2.2
new style classes, in practice the cases in which the C3 resolution
order differs from the Python 2.2 method resolution order are so rare
that no real breaking of code is expected.  Therefore:

     'Don't be scared!'

Moreover, unless you make strong use of multiple inheritance and you
have non-trivial hierarchies, you don't need to understand the C3
algorithm, and you can easily skip this paper.  On the other hand, if
you really want to know how multiple inheritance works, then this paper
is for you.  The good news is that things are not as complicated as you
might expect.

Let me begin with some basic definitions.

  1. Given a class C in a complicated multiple inheritance hierarchy, it
     is a non-trivial task to specify the order in which methods are
     overridden, i.e.  to specify the order of the ancestors of C.

  2. The list of the ancestors of a class C, including the class itself,
     ordered from the nearest ancestor to the furthest, is called the
     class precedence list or the 'linearization' of C.

  3. The 'Method Resolution Order' (MRO) is the set of rules that
     construct the linearization.  In the Python literature, the idiom
     "the MRO of C" is also used as a synonymous for the linearization
     of the class C.

  4. For instance, in the case of single inheritance hierarchy, if C is
     a subclass of C1, and C1 is a subclass of C2, then the
     linearization of C is simply the list [C, C1 , C2].  However, with
     multiple inheritance hierarchies, the construction of the
     linearization is more cumbersome, since it is more difficult to
     construct a linearization that respects 'local precedence ordering'
     and 'monotonicity'.

  5. I will discuss the local precedence ordering later, but I can give
     the definition of monotonicity here.  A MRO is monotonic when the
     following is true: 'if C1 precedes C2 in the linearization of C,
     then C1 precedes C2 in the linearization of any subclass of C'.
     Otherwise, the innocuous operation of deriving a new class could
     change the resolution order of methods, potentially introducing
     very subtle bugs.  Examples where this happens will be shown later.

  6. Not all classes admit a linearization.  There are cases, in
     complicated hierarchies, where it is not possible to derive a class
     such that its linearization respects all the desired properties.

Here I give an example of this situation.  Consider the hierarchy

     >>> O = object
     >>> class X(O): pass
     >>> class Y(O): pass
     >>> class A(X,Y): pass
     >>> class B(Y,X): pass

which can be represented with the following inheritance graph, where I
have denoted with O the ‘object’ class, which is the beginning of any
hierarchy for new style classes:

           -----------
          |           |
          |    O      |
          |  /   \    |
           - X    Y  /
             |  / | /
             | /  |/
             A    B
             \   /
               ?

In this case, it is not possible to derive a new class C from A and B,
since X precedes Y in A, but Y precedes X in B, therefore the method
resolution order would be ambiguous in C.

Python 2.3 raises an exception in this situation (TypeError: MRO
conflict among bases Y, X) forbidding the naive programmer from creating
ambiguous hierarchies.  Python 2.2 instead does not raise an exception,
but chooses an 'ad hoc' ordering (CABXYO in this case).

   ---------- Footnotes ----------

   (1) The thread on python-dev started by Samuele Pedroni:
‘https://mail.python.org/pipermail/python-dev/2002-October/029035.html’

   (2) The paper 'A Monotonic Superclass Linearization for Dylan':
‘https://doi.org/10.1145/236337.236343’


File: python.info,  Node: The C3 Method Resolution Order,  Next: 範例<55>,  Prev: The beginning,  Up: The Python 2 3 Method Resolution Order

9.21.2 The C3 Method Resolution Order
-------------------------------------

Let me introduce a few simple notations which will be useful for the
following discussion.  I will use the shortcut notation:

     C1 C2 ... CN

to indicate the list of classes [C1, C2, ...  , CN].

The 'head' of the list is its first element:

     head = C1

whereas the 'tail' is the rest of the list:

     tail = C2 ... CN.

I shall also use the notation:

     C + (C1 C2 ... CN) = C C1 C2 ... CN

to denote the sum of the lists [C] + [C1, C2, ...  ,CN].

Now I can explain how the MRO works in Python 2.3.

Consider a class C in a multiple inheritance hierarchy, with C
inheriting from the base classes B1, B2, ...  , BN. We want to compute
the linearization L[C] of the class C. The rule is the following:

     'the linearization of C is the sum of C plus the merge of the
     linearizations of the parents and the list of the parents.'

In symbolic notation:

     L[C(B1 ... BN)] = C + merge(L[B1] ... L[BN], B1 ... BN)

In particular, if C is the ‘object’ class, which has no parents, the
linearization is trivial:

     L[object] = object.

However, in general one has to compute the merge according to the
following prescription:

     'take the head of the first list, i.e L[B1][0]; if this head is not
     in the tail of any of the other lists, then add it to the
     linearization of C and remove it from the lists in the merge,
     otherwise look at the head of the next list and take it, if it is a
     good head.  Then repeat the operation until all the class are
     removed or it is impossible to find good heads.  In this case, it
     is impossible to construct the merge, Python 2.3 will refuse to
     create the class C and will raise an exception.'

This prescription ensures that the merge operation 'preserves' the
ordering, if the ordering can be preserved.  On the other hand, if the
order cannot be preserved (as in the example of serious order
disagreement discussed above) then the merge cannot be computed.

The computation of the merge is trivial if C has only one parent (single
inheritance); in this case:

     L[C(B)] = C + merge(L[B],B) = C + L[B]

However, in the case of multiple inheritance things are more cumbersome
and I don't expect you can understand the rule without a couple of
examples ;-)


File: python.info,  Node: 範例<55>,  Next: Bad Method Resolution Orders,  Prev: The C3 Method Resolution Order,  Up: The Python 2 3 Method Resolution Order

9.21.3 範例
-----------

First example.  Consider the following hierarchy:

     >>> O = object
     >>> class F(O): pass
     >>> class E(O): pass
     >>> class D(O): pass
     >>> class C(D,F): pass
     >>> class B(D,E): pass
     >>> class A(B,C): pass

In this case the inheritance graph can be drawn as:

                                    6
                                   ---
          Level 3                 | O |                  (more general)
                                /  ---  \
                               /    |    \                      |
                              /     |     \                     |
                             /      |      \                    |
                            ---    ---    ---                   |
          Level 2        3 | D | 4| E |  | F | 5                |
                            ---    ---    ---                   |
                             \  \ _ /       |                   |
                              \    / \ _    |                   |
                               \  /      \  |                   |
                                ---      ---                    |
          Level 1            1 | B |    | C | 2                 |
                                ---      ---                    |
                                  \      /                      |
                                   \    /                      \ /
                                     ---
          Level 0                 0 | A |                (more specialized)
                                     ---

The linearizations of O,D,E and F are trivial:

     L[O] = O
     L[D] = D O
     L[E] = E O
     L[F] = F O

The linearization of B can be computed as:

     L[B] = B + merge(DO, EO, DE)

We see that D is a good head, therefore we take it and we are reduced to
compute ‘merge(O,EO,E)’.  Now O is not a good head, since it is in the
tail of the sequence EO. In this case the rule says that we have to skip
to the next sequence.  Then we see that E is a good head; we take it and
we are reduced to compute ‘merge(O,O)’ which gives O. Therefore:

     L[B] =  B D E O

Using the same procedure one finds:

     L[C] = C + merge(DO,FO,DF)
          = C + D + merge(O,FO,F)
          = C + D + F + merge(O,O)
          = C D F O

Now we can compute:

     L[A] = A + merge(BDEO,CDFO,BC)
          = A + B + merge(DEO,CDFO,C)
          = A + B + C + merge(DEO,DFO)
          = A + B + C + D + merge(EO,FO)
          = A + B + C + D + E + merge(O,FO)
          = A + B + C + D + E + F + merge(O,O)
          = A B C D E F O

In this example, the linearization is ordered in a pretty nice way
according to the inheritance level, in the sense that lower levels (i.e.
more specialized classes) have higher precedence (see the inheritance
graph).  However, this is not the general case.

I leave as an exercise for the reader to compute the linearization for
my second example:

     >>> O = object
     >>> class F(O): pass
     >>> class E(O): pass
     >>> class D(O): pass
     >>> class C(D,F): pass
     >>> class B(E,D): pass
     >>> class A(B,C): pass

The only difference with the previous example is the change B(D,E) ->
B(E,D); however even such a little modification completely changes the
ordering of the hierarchy:

                                     6
                                    ---
          Level 3                  | O |
                                 /  ---  \
                                /    |    \
                               /     |     \
                              /      |      \
                            ---     ---    ---
          Level 2        2 | E | 4 | D |  | F | 5
                            ---     ---    ---
                             \      / \     /
                              \    /   \   /
                               \  /     \ /
                                ---     ---
          Level 1            1 | B |   | C | 3
                                ---     ---
                                 \       /
                                  \     /
                                    ---
          Level 0                0 | A |
                                    ---

Notice that the class E, which is in the second level of the hierarchy,
precedes the class C, which is in the first level of the hierarchy, i.e.
E is more specialized than C, even if it is in a higher level.

A lazy programmer can obtain the MRO directly from Python 2.2, since in
this case it coincides with the Python 2.3 linearization.  It is enough
to invoke the .mro() method of class A:

     >>> A.mro()
     [<class 'A'>, <class 'B'>, <class 'E'>,
     <class 'C'>, <class 'D'>, <class 'F'>,
     <class 'object'>]

Finally, let me consider the example discussed in the first section,
involving a serious order disagreement.  In this case, it is
straightforward to compute the linearizations of O, X, Y, A and B:

          L[O] = 0
          L[X] = X O
          L[Y] = Y O
          L[A] = A X Y O
          L[B] = B Y X O

However, it is impossible to compute the linearization for a class C
that inherits from A and B:

     L[C] = C + merge(AXYO, BYXO, AB)
          = C + A + merge(XYO, BYXO, B)
          = C + A + B + merge(XYO, YXO)

At this point we cannot merge the lists XYO and YXO, since X is in the
tail of YXO whereas Y is in the tail of XYO: therefore there are no good
heads and the C3 algorithm stops.  Python 2.3 raises an error and
refuses to create the class C.


File: python.info,  Node: Bad Method Resolution Orders,  Next: The end,  Prev: 範例<55>,  Up: The Python 2 3 Method Resolution Order

9.21.4 Bad Method Resolution Orders
-----------------------------------

A MRO is 'bad' when it breaks such fundamental properties as local
precedence ordering and monotonicity.  In this section, I will show that
both the MRO for classic classes and the MRO for new style classes in
Python 2.2 are bad.

It is easier to start with the local precedence ordering.  Consider the
following example:

     >>> F=type('Food',(),{'remember2buy':'spam'})
     >>> E=type('Eggs',(F,),{'remember2buy':'eggs'})
     >>> G=type('GoodFood',(F,E),{}) # under Python 2.3 this is an error!

with inheritance diagram

                       O
                       |
          (buy spam)   F
                       | \
                       | E   (buy eggs)
                       | /
                       G

                (buy eggs or spam ?)

We see that class G inherits from F and E, with F 'before' E: therefore
we would expect the attribute 'G.remember2buy' to be inherited by
'F.rembermer2buy' and not by 'E.remember2buy': nevertheless Python 2.2
gives

     >>> G.remember2buy
     'eggs'

This is a breaking of local precedence ordering since the order in the
local precedence list, i.e.  the list of the parents of G, is not
preserved in the Python 2.2 linearization of G:

     L[G,P22]= G E F object   # F *follows* E

One could argue that the reason why F follows E in the Python 2.2
linearization is that F is less specialized than E, since F is the
superclass of E; nevertheless the breaking of local precedence ordering
is quite non-intuitive and error prone.  This is particularly true since
it is a different from old style classes:

     >>> class F: remember2buy='spam'
     >>> class E(F): remember2buy='eggs'
     >>> class G(F,E): pass
     >>> G.remember2buy
     'spam'

In this case the MRO is GFEF and the local precedence ordering is
preserved.

As a general rule, hierarchies such as the previous one should be
avoided, since it is unclear if F should override E or vice-versa.
Python 2.3 solves the ambiguity by raising an exception in the creation
of class G, effectively stopping the programmer from generating
ambiguous hierarchies.  The reason for that is that the C3 algorithm
fails when the merge:

     merge(FO,EFO,FE)

cannot be computed, because F is in the tail of EFO and E is in the tail
of FE.

The real solution is to design a non-ambiguous hierarchy, i.e.  to
derive G from E and F (the more specific first) and not from F and E; in
this case the MRO is GEF without any doubt.

                     O
                     |
                     F (spam)
                   / |
          (eggs)   E |
                   \ |
                     G
                       (eggs, no doubt)

Python 2.3 forces the programmer to write good hierarchies (or, at
least, less error-prone ones).

On a related note, let me point out that the Python 2.3 algorithm is
smart enough to recognize obvious mistakes, as the duplication of
classes in the list of parents:

     >>> class A(object): pass
     >>> class C(A,A): pass # error
     Traceback (most recent call last):
       File "<stdin>", line 1, in ?
     TypeError: duplicate base class A

Python 2.2 (both for classic classes and new style classes) in this
situation, would not raise any exception.

Finally, I would like to point out two lessons we have learned from this
example:

  1. despite the name, the MRO determines the resolution order of
     attributes, not only of methods;

  2. the default food for Pythonistas is spam !  (but you already knew
     that ;-)

Having discussed the issue of local precedence ordering, let me now
consider the issue of monotonicity.  My goal is to show that neither the
MRO for classic classes nor that for Python 2.2 new style classes is
monotonic.

To prove that the MRO for classic classes is non-monotonic is rather
trivial, it is enough to look at the diamond diagram:

             C
            / \
           /   \
          A     B
           \   /
            \ /
             D

One easily discerns the inconsistency:

     L[B,P21] = B C        # B precedes C : B's methods win
     L[D,P21] = D A C B C  # B follows C  : C's methods win!

On the other hand, there are no problems with the Python 2.2 and 2.3
MROs, they give both:

     L[D] = D A B C

Guido points out in his essay (1) that the classic MRO is not so bad in
practice, since one can typically avoids diamonds for classic classes.
But all new style classes inherit from ‘object’, therefore diamonds are
unavoidable and inconsistencies shows up in every multiple inheritance
graph.

The MRO of Python 2.2 makes breaking monotonicity difficult, but not
impossible.  The following example, originally provided by Samuele
Pedroni, shows that the MRO of Python 2.2 is non-monotonic:

     >>> class A(object): pass
     >>> class B(object): pass
     >>> class C(object): pass
     >>> class D(object): pass
     >>> class E(object): pass
     >>> class K1(A,B,C): pass
     >>> class K2(D,B,E): pass
     >>> class K3(D,A):   pass
     >>> class Z(K1,K2,K3): pass

Here are the linearizations according to the C3 MRO (the reader should
verify these linearizations as an exercise and draw the inheritance
diagram ;-)

     L[A] = A O
     L[B] = B O
     L[C] = C O
     L[D] = D O
     L[E] = E O
     L[K1]= K1 A B C O
     L[K2]= K2 D B E O
     L[K3]= K3 D A O
     L[Z] = Z K1 K2 K3 D A B C E O

Python 2.2 gives exactly the same linearizations for A, B, C, D, E, K1,
K2 and K3, but a different linearization for Z:

     L[Z,P22] = Z K1 K3 A K2 D B C E O

It is clear that this linearization is 'wrong', since A comes before D
whereas in the linearization of K3 A comes 'after' D. In other words, in
K3 methods derived by D override methods derived by A, but in Z, which
still is a subclass of K3, methods derived by A override methods derived
by D! This is a violation of monotonicity.  Moreover, the Python 2.2
linearization of Z is also inconsistent with local precedence ordering,
since the local precedence list of the class Z is [K1, K2, K3] (K2
precedes K3), whereas in the linearization of Z K2 'follows' K3.  These
problems explain why the 2.2 rule has been dismissed in favor of the C3
rule.

   ---------- Footnotes ----------

   (1) Guido van Rossum's essay, 'Unifying types and classes in Python
2.2':
‘https://web.archive.org/web/20140210194412/http://www.python.org/download/releases/2.2.2/descrintro’


File: python.info,  Node: The end,  Next: Resources,  Prev: Bad Method Resolution Orders,  Up: The Python 2 3 Method Resolution Order

9.21.5 The end
--------------

This section is for the impatient reader, who skipped all the previous
sections and jumped immediately to the end.  This section is for the
lazy programmer too, who didn't want to exercise her/his brain.
Finally, it is for the programmer with some hubris, otherwise s/he would
not be reading a paper on the C3 method resolution order in multiple
inheritance hierarchies ;-) These three virtues taken all together (and
'not' separately) deserve a prize: the prize is a short Python 2.2
script that allows you to compute the 2.3 MRO without risk to your
brain.  Simply change the last line to play with the various examples I
have discussed in this paper.:

     #<mro.py>

     """C3 algorithm by Samuele Pedroni (with readability enhanced by me)."""

     class __metaclass__(type):
         "All classes are metamagically modified to be nicely printed"
         __repr__ = lambda cls: cls.__name__

     class ex_2:
         "Serious order disagreement" #From Guido
         class O: pass
         class X(O): pass
         class Y(O): pass
         class A(X,Y): pass
         class B(Y,X): pass
         try:
             class Z(A,B): pass #creates Z(A,B) in Python 2.2
         except TypeError:
             pass # Z(A,B) cannot be created in Python 2.3

     class ex_5:
         "My first example"
         class O: pass
         class F(O): pass
         class E(O): pass
         class D(O): pass
         class C(D,F): pass
         class B(D,E): pass
         class A(B,C): pass

     class ex_6:
         "My second example"
         class O: pass
         class F(O): pass
         class E(O): pass
         class D(O): pass
         class C(D,F): pass
         class B(E,D): pass
         class A(B,C): pass

     class ex_9:
         "Difference between Python 2.2 MRO and C3" #From Samuele
         class O: pass
         class A(O): pass
         class B(O): pass
         class C(O): pass
         class D(O): pass
         class E(O): pass
         class K1(A,B,C): pass
         class K2(D,B,E): pass
         class K3(D,A): pass
         class Z(K1,K2,K3): pass

     def merge(seqs):
         print '\n\nCPL[%s]=%s' % (seqs[0][0],seqs),
         res = []; i=0
         while 1:
           nonemptyseqs=[seq for seq in seqs if seq]
           if not nonemptyseqs: return res
           i+=1; print '\n',i,'round: candidates...',
           for seq in nonemptyseqs: # find merge candidates among seq heads
               cand = seq[0]; print ' ',cand,
               nothead=[s for s in nonemptyseqs if cand in s[1:]]
               if nothead: cand=None #reject candidate
               else: break
           if not cand: raise "Inconsistent hierarchy"
           res.append(cand)
           for seq in nonemptyseqs: # remove cand
               if seq[0] == cand: del seq[0]

     def mro(C):
         "Compute the class precedence list (mro) according to C3"
         return merge([[C]]+map(mro,C.__bases__)+[list(C.__bases__)])

     def print_mro(C):
         print '\nMRO[%s]=%s' % (C,mro(C))
         print '\nP22 MRO[%s]=%s' % (C,C.mro())

     print_mro(ex_9.Z)

     #</mro.py>

That's all folks,

     enjoy !


File: python.info,  Node: Resources,  Prev: The end,  Up: The Python 2 3 Method Resolution Order

9.21.6 Resources
----------------


File: python.info,  Node: C API Extension Support for Free Threading,  Prev: The Python 2 3 Method Resolution Order,  Up: Python 如何達成任務

9.22 C API Extension Support for Free Threading
===============================================

Starting with the 3.13 release, CPython has experimental support for
running with the *note global interpreter lock: 12e. (GIL) disabled in a
configuration called *note free threading: 42d1.  This document
describes how to adapt C API extensions to support free threading.

* Menu:

* Identifying the Free-Threaded Build in C::
* Module Initialization::
* General API Guidelines::
* Borrowed References::
* Memory Allocation APIs::
* Thread State and GIL APIs::
* Protecting Internal Extension State::
* Building Extensions for the Free-Threaded Build::


File: python.info,  Node: Identifying the Free-Threaded Build in C,  Next: Module Initialization,  Up: C API Extension Support for Free Threading

9.22.1 Identifying the Free-Threaded Build in C
-----------------------------------------------

The CPython C API exposes the ‘Py_GIL_DISABLED’ macro: in the
free-threaded build it's defined to ‘1’, and in the regular build it's
not defined.  You can use it to enable code that only runs under the
free-threaded build:

     #ifdef Py_GIL_DISABLED
     /* code that only runs in the free-threaded build */
     #endif


File: python.info,  Node: Module Initialization,  Next: General API Guidelines,  Prev: Identifying the Free-Threaded Build in C,  Up: C API Extension Support for Free Threading

9.22.2 Module Initialization
----------------------------

Extension modules need to explicitly indicate that they support running
with the GIL disabled; otherwise importing the extension will raise a
warning and enable the GIL at runtime.

There are two ways to indicate that an extension module supports running
with the GIL disabled depending on whether the extension uses
multi-phase or single-phase initialization.

* Menu:

* Multi-Phase Initialization::
* Single-Phase Initialization::


File: python.info,  Node: Multi-Phase Initialization,  Next: Single-Phase Initialization,  Up: Module Initialization

9.22.2.1 Multi-Phase Initialization
...................................

Extensions that use multi-phase initialization (i.e., *note
PyModuleDef_Init(): 4806.) should add a *note Py_mod_gil: 13d. slot in
the module definition.  If your extension supports older versions of
CPython, you should guard the slot with a *note PY_VERSION_HEX: 6fb.
check.

     static struct PyModuleDef_Slot module_slots[] = {
         ...
     #if PY_VERSION_HEX >= 0x030D0000
         {Py_mod_gil, Py_MOD_GIL_NOT_USED},
     #endif
         {0, NULL}
     };

     static struct PyModuleDef moduledef = {
         PyModuleDef_HEAD_INIT,
         .m_slots = module_slots,
         ...
     };


File: python.info,  Node: Single-Phase Initialization,  Prev: Multi-Phase Initialization,  Up: Module Initialization

9.22.2.2 Single-Phase Initialization
....................................

Extensions that use single-phase initialization (i.e., *note
PyModule_Create(): 46da.) should call *note PyUnstable_Module_SetGIL():
15d. to indicate that they support running with the GIL disabled.  The
function is only defined in the free-threaded build, so you should guard
the call with ‘#ifdef Py_GIL_DISABLED’ to avoid compilation errors in
the regular build.

     static struct PyModuleDef moduledef = {
         PyModuleDef_HEAD_INIT,
         ...
     };

     PyMODINIT_FUNC
     PyInit_mymodule(void)
     {
         PyObject *m = PyModule_Create(&moduledef);
         if (m == NULL) {
             return NULL;
         }
     #ifdef Py_GIL_DISABLED
         PyUnstable_Module_SetGIL(m, Py_MOD_GIL_NOT_USED);
     #endif
         return m;
     }


File: python.info,  Node: General API Guidelines,  Next: Borrowed References,  Prev: Module Initialization,  Up: C API Extension Support for Free Threading

9.22.3 General API Guidelines
-----------------------------

Most of the C API is thread-safe, but there are some exceptions.

   * 'Struct Fields': Accessing fields in Python C API objects or
     structs directly is not thread-safe if the field may be
     concurrently modified.

   * 'Macros': Accessor macros like *note PyList_GET_ITEM: 4779. and
     *note PyList_SET_ITEM: 306. do not perform any error checking or
     locking.  These macros are not thread-safe if the container object
     may be modified concurrently.

   * 'Borrowed References': C API functions that return *note borrowed
     references: 2ef. may not be thread-safe if the containing object is
     modified concurrently.  See the section on *note borrowed
     references: 4e4b. for more information.

* Menu:

* Container Thread Safety::


File: python.info,  Node: Container Thread Safety,  Up: General API Guidelines

9.22.3.1 Container Thread Safety
................................

Containers like *note PyListObject: 4983, *note PyDictObject: 38c, and
*note PySetObject: 4a71. perform internal locking in the free-threaded
build.  For example, the *note PyList_Append(): 47ee. will lock the list
before appending an item.

* Menu:

* PyDict_Next::


File: python.info,  Node: PyDict_Next,  Up: Container Thread Safety

9.22.3.2 ‘PyDict_Next’
......................

A notable exception is *note PyDict_Next(): 1505, which does not lock
the dictionary.  You should use *note Py_BEGIN_CRITICAL_SECTION: 4a69.
to protect the dictionary while iterating over it if the dictionary may
be concurrently modified:

     Py_BEGIN_CRITICAL_SECTION(dict);
     PyObject *key, *value;
     Py_ssize_t pos = 0;
     while (PyDict_Next(dict, &pos, &key, &value)) {
         ...
     }
     Py_END_CRITICAL_SECTION();


File: python.info,  Node: Borrowed References,  Next: Memory Allocation APIs,  Prev: General API Guidelines,  Up: C API Extension Support for Free Threading

9.22.4 Borrowed References
--------------------------

Some C API functions return *note borrowed references: 2ef.  These APIs
are not thread-safe if the containing object is modified concurrently.
For example, it's not safe to use *note PyList_GetItem(): 313. if the
list may be modified concurrently.

The following table lists some borrowed reference APIs and their
replacements that return *note strong references: 2ee.

Borrowed reference API                  Strong reference API
                                        
--------------------------------------------------------------------------------
                                        
*note PyList_GetItem(): 313.            *note PyList_GetItemRef(): 312.
                                        
                                        
*note PyDict_GetItem(): 35b.            *note PyDict_GetItemRef(): 30a.
                                        
                                        
*note PyDict_GetItemWithError(): 30c.   *note PyDict_GetItemRef(): 30a.
                                        
                                        
*note PyDict_GetItemString(): 35c.      *note PyDict_GetItemStringRef(): 30b.
                                        
                                        
*note PyDict_SetDefault(): 30e.         *note PyDict_SetDefaultRef(): 30d.
                                        
                                        
*note PyDict_Next(): 1505.              none (see *note PyDict_Next: 4e4e.)
                                        
                                        
*note PyWeakref_GetObject(): 2f1.       *note PyWeakref_GetRef(): 2f0.
                                        
                                        
*note PyWeakref_GET_OBJECT(): 38a.      *note PyWeakref_GetRef(): 2f0.
                                        
                                        
*note PyImport_AddModule(): 2ed.        *note PyImport_AddModuleRef(): 2ec.
                                        

Not all APIs that return borrowed references are problematic.  For
example, *note PyTuple_GetItem(): 46ed. is safe because tuples are
immutable.  Similarly, not all uses of the above APIs are problematic.
For example, *note PyDict_GetItem(): 35b. is often used for parsing
keyword argument dictionaries in function calls; those keyword argument
dictionaries are effectively private (not accessible by other threads),
so using borrowed references in that context is safe.

Some of these functions were added in Python 3.13.  You can use the
pythoncapi-compat(1) package to provide implementations of these
functions for older Python versions.

   ---------- Footnotes ----------

   (1) https://github.com/python/pythoncapi-compat


File: python.info,  Node: Memory Allocation APIs,  Next: Thread State and GIL APIs,  Prev: Borrowed References,  Up: C API Extension Support for Free Threading

9.22.5 Memory Allocation APIs
-----------------------------

Python's memory management C API provides functions in three different
*note allocation domains: 4bd0.: "raw", "mem", and "object".  For
thread-safety, the free-threaded build requires that only Python objects
are allocated using the object domain, and that all Python object are
allocated using that domain.  This differs from the prior Python
versions, where this was only a best practice and not a hard
requirement.

     備註: Search for uses of *note PyObject_Malloc(): c0f. in your
     extension and check that the allocated memory is used for Python
     objects.  Use *note PyMem_Malloc(): c0d. to allocate buffers
     instead of *note PyObject_Malloc(): c0f.


File: python.info,  Node: Thread State and GIL APIs,  Next: Protecting Internal Extension State,  Prev: Memory Allocation APIs,  Up: C API Extension Support for Free Threading

9.22.6 Thread State and GIL APIs
--------------------------------

Python provides a set of functions and macros to manage thread state and
the GIL, such as:

   * *note PyGILState_Ensure(): 376. and *note PyGILState_Release():
     377.

   * *note PyEval_SaveThread(): 373. and *note PyEval_RestoreThread():
     374.

   * *note Py_BEGIN_ALLOW_THREADS: 46f3. and *note Py_END_ALLOW_THREADS:
     a31.

These functions should still be used in the free-threaded build to
manage thread state even when the *note GIL: 13e. is disabled.  For
example, if you create a thread outside of Python, you must call *note
PyGILState_Ensure(): 376. before calling into the Python API to ensure
that the thread has a valid Python thread state.

You should continue to call *note PyEval_SaveThread(): 373. or *note
Py_BEGIN_ALLOW_THREADS: 46f3. around blocking operations, such as I/O or
lock acquisitions, to allow other threads to run the *note cyclic
garbage collector: 181c.


File: python.info,  Node: Protecting Internal Extension State,  Next: Building Extensions for the Free-Threaded Build,  Prev: Thread State and GIL APIs,  Up: C API Extension Support for Free Threading

9.22.7 Protecting Internal Extension State
------------------------------------------

Your extension may have internal state that was previously protected by
the GIL. You may need to add locking to protect this state.  The
approach will depend on your extension, but some common patterns
include:

   * 'Caches': global caches are a common source of shared state.
     Consider using a lock to protect the cache or disabling it in the
     free-threaded build if the cache is not critical for performance.

   * 'Global State': global state may need to be protected by a lock or
     moved to thread local storage.  C11 and C++11 provide the
     ‘thread_local’ or ‘_Thread_local’ for thread-local storage(1).

   ---------- Footnotes ----------

   (1) https://en.cppreference.com/w/c/language/storage_duration


File: python.info,  Node: Building Extensions for the Free-Threaded Build,  Prev: Protecting Internal Extension State,  Up: C API Extension Support for Free Threading

9.22.8 Building Extensions for the Free-Threaded Build
------------------------------------------------------

C API extensions need to be built specifically for the free-threaded
build.  The wheels, shared libraries, and binaries are indicated by a
‘t’ suffix.

   * pypa/manylinux(1) supports the free-threaded build, with the ‘t’
     suffix, such as ‘python3.13t’.

   * pypa/cibuildwheel(2) supports the free-threaded build if you set
     CIBW_FREE_THREADED_SUPPORT(3).

* Menu:

* Limited C API and Stable ABI::
* Windows: Windows<73>.

   ---------- Footnotes ----------

   (1) https://github.com/pypa/manylinux

   (2) https://github.com/pypa/cibuildwheel

   (3) 
https://cibuildwheel.pypa.io/en/stable/options/#free-threaded-support


File: python.info,  Node: Limited C API and Stable ABI,  Next: Windows<73>,  Up: Building Extensions for the Free-Threaded Build

9.22.8.1 Limited C API and Stable ABI
.....................................

The free-threaded build does not currently support the *note Limited C
API: 318. or the stable ABI. If you use setuptools(1) to build your
extension and currently set ‘py_limited_api=True’ you can use
‘py_limited_api=not sysconfig.get_config_var("Py_GIL_DISABLED")’ to opt
out of the limited API when building with the free-threaded build.

     備註: You will need to build separate wheels specifically for the
     free-threaded build.  If you currently use the stable ABI, you can
     continue to build a single wheel for multiple non-free-threaded
     Python versions.

   ---------- Footnotes ----------

   (1) https://setuptools.pypa.io/en/latest/setuptools.html


File: python.info,  Node: Windows<73>,  Prev: Limited C API and Stable ABI,  Up: Building Extensions for the Free-Threaded Build

9.22.8.2 Windows
................

Due to a limitation of the official Windows installer, you will need to
manually define ‘Py_GIL_DISABLED=1’ when building extensions from
source.

也參考
......

Porting Extension Modules to Support Free-Threading(1): A
community-maintained porting guide for extension authors.

General:

   * *note 註釋 (annotation) 最佳實踐: 77d.

   * *note Argparse 教學: 2b44.

   * *note 描述器 (Descriptor) 指南: 145a.

   * *note Enum HOWTO: 4cde.

   * *note 函式編程 HOWTO: 4d0f.

   * *note ipaddress 模組介紹: 3a5c.

   * *note 如何使用 Logging 模組: 4d2d.

   * *note Logging Cookbook: 118f.

   * *note 如何使用正規表示式: 21c9.

   * *note 排序技法: 205a.

   * *note Unicode HOWTO: 123b.

   * *note 如何使用 urllib 套件取得網路資源: 3836.

Advanced development:

   * *note Curses Programming with Python: 2c82.

   * *note C API Extension Support for Free Threading: 4e45.

   * *note 隔離擴充模組: 4ad1.

   * *note The Python 2.3 Method Resolution Order: 1415.

   * *note Socket 程式設計指南: 327d.

   * *note timer file descriptor HOWTO: 4e39.

   * *note 遷移延伸模組到 Python 3: 1274.

Debugging and profiling:

   * *note 使用 GDB 來為 C API 擴充功能和 CPython 內部偵錯: 4cd0.

   * *note 使用 DTrace 和 SystemTap 檢測 CPython: c13.

   * *note Python 對 Linux perf 分析器的支援: 175.

   ---------- Footnotes ----------

   (1) https://py-free-threading.github.io/porting/


File: python.info,  Node: Python 常見問題,  Next: 已棄用項目,  Prev: Python 如何達成任務,  Up: Top

10 Python 常見問題
******************

* Menu:

* 一般的 Python 常見問答集::
* 程式開發常見問答集::
* 設計和歷史常見問答集::
* 函式庫和擴充功能的常見問題::
* 擴充/嵌入常見問題集::
* 在 Windows 使用 Python 的常見問答集::
* 圖形使用者介面常見問答集::
* 「為什麼 Python 被安裝在我的機器上？」常見問答集::


File: python.info,  Node: 一般的 Python 常見問答集,  Next: 程式開發常見問答集,  Up: Python 常見問題

10.1 一般的 Python 常見問答集
=============================

* Menu:

* 一般資訊::
* 在真實世界中的 Python::


File: python.info,  Node: 一般資訊,  Next: 在真實世界中的 Python,  Up: 一般的 Python 常見問答集

10.1.1 一般資訊
---------------

* Menu:

* 什麼是 Python？::
* 什麼是 Python 軟體基金會？::
* 使用 Python 時有任何版權限制嗎？::
* 當初為什麼 Python 會被創造出來？::
* 什麼是 Python 擅長的事情？::
* Python 的版本編號系統是如何運作的？::
* 我要如何得到 Python 的原始碼複本？::
* 我要如何取得 Python 的說明文件？::
* 我從來沒有寫過程式，有沒有 Python 的教學？::
* 有沒有 Python 專屬的新聞群組或郵件討論群？::
* 如何取得 Python 的 beta 測試版本？::
* 如何提交 Python 的錯誤報告和修補程式？::
* 是否有關於 Python 的任何已出版文章可供參考？::
* 有沒有關於 Python 的書？::
* www.python.org 的真實位置在哪裡？: www python org 的真實位置在哪裡？.
* 為什麼要取名為 Python？::
* 我需要喜歡「Monty Python 的飛行馬戲團」嗎？::


File: python.info,  Node: 什麼是 Python？,  Next: 什麼是 Python 軟體基金會？,  Up: 一般資訊

10.1.1.1 什麼是 Python？
........................

Python 是一種直譯的、互動的、物件導向的程式設計語言。它結合了模組、例外
、動態型別 (dynamic typing)、非常高階的動態資料型別，以及 class（類別）
。它能支援物件導向程式設計之外的多種程式設計典範，例如程序式
(procedural) 和函式語言 (functional) 程式設計。Python 結合了卓越的功能與
非常清晰的語法。它有許多系統呼叫和函式庫的介面，以及各種視窗系統的介面，
並且在 C 或 C++ 中可以擴充。它還可以作為一種擴充語言，使用於需要可程式化
介面 (programmable interface) 的應用程式。最後，Python 是可攜的
(portable)：它能運行在許多 Unix 的變體上，包括 Linux 和 macOS，也能運行
在 Windows 上。

要尋找更多內容，請從 *note Python 教學: 1ae0.開始。Python 初學者指南
(1)可連結到其他介紹式教學以及學習 Python 的資源。

   ---------- Footnotes ----------

   (1) https://wiki.python.org/moin/BeginnersGuide


File: python.info,  Node: 什麼是 Python 軟體基金會？,  Next: 使用 Python 時有任何版權限制嗎？,  Prev: 什麼是 Python？,  Up: 一般資訊

10.1.1.2 什麼是 Python 軟體基金會？
...................................

Python 軟體基金會 (Python Software Foundation) 是一個獨立的非營利性組織
，它擁有 Python 2.1 版與之後各版本的版權。PSF 的使命在於推展 Python 程式
設計語言相關的開放原始碼技術，以及宣傳 Python 的使用。PSF 首頁的網址是
‘https://www.python.org/psf/’。

在美國捐款給 PSF 是免稅的。如果你使用了 Python 且發現它很有用，請至 PSF
捐款頁面(1)為它做出貢獻。

   ---------- Footnotes ----------

   (1) https://www.python.org/psf/donations/


File: python.info,  Node: 使用 Python 時有任何版權限制嗎？,  Next: 當初為什麼 Python 會被創造出來？,  Prev: 什麼是 Python 軟體基金會？,  Up: 一般資訊

10.1.1.3 使用 Python 時有任何版權限制嗎？
.........................................

你可以對原始碼做任何你想做的事情，只要你保留版權，並且在你製作的任何關於
Python 的說明文件中顯示這些版權即可。如果你遵守版權規則，就可以將 Python
用於商業用途，以原始碼或二進制形式（修改或未修改）銷售 Python 的複本，或
者以某種形式銷售內含 Python 的產品。當然，我們仍然會想要知道所有的
Python 商業用途。

請參閱 授權頁面(1)，查詢更深入的說明和 PSF 授權全文的連結。

Python 標誌是註冊商標，在某些情況下需要許可才能使用它。請參閱商標使用政
策(2)以取得更多資訊。

   ---------- Footnotes ----------

   (1) https://docs.python.org/3/license.html

   (2) https://www.python.org/psf/trademarks/


File: python.info,  Node: 當初為什麼 Python 會被創造出來？,  Next: 什麼是 Python 擅長的事情？,  Prev: 使用 Python 時有任何版權限制嗎？,  Up: 一般資訊

10.1.1.4 當初為什麼 Python 會被創造出來？
.........................................

以下是由 Guido van Rossum 所撰寫，關於這一切如何開始的'非常'簡短的摘要：

     我在 CWI 的 ABC 小組中擁有實作直譯語言方面的豐富經驗，而透過與該小
     組的合作，我學到了很多關於語言設計的知識。這是許多 Python 功能的起
     源，包括使用縮排進行陳述式分組以及納入非常高階的資料型別（儘管在
     Python 中的細節都已經不同）。

     我對 ABC 語言有一些牢騷，但我也喜歡它的許多功能。想要擴充 ABC 語言
     （或其實作）來去除我的抱怨是不可能的。事實上，缺乏可擴充性就是它最
     大的問題之一。我有一些使用 Modula-2+ 的經驗，也與 Modula-3 的設計者
     交談過，並閱讀了 Modula-3 的報告。Modula-3 就是用於例外及另外一些
     Python 功能的語法和語義的起源。

     我當時正在 CWI 的 Amoeba 分散式作業系統小組工作。我們需要一種比編寫
     C 程式或 Bourne shell 腳本更好的方法來進行系統管理，因為 Amoeba 有
     自己的系統呼叫介面，而它無法簡單地從 Bourne shell 進行存取。我在
     Amoeba 中處理錯誤的經驗，使我深切地意識到例外作為程式設計語言功能的
     重要性。

     我突然想到，一種具有類似 ABC 的語法但可以存取 Amoeba 系統呼叫的腳本
     語言將能滿足該需求。我了解編寫 Amoeba 專用語言是愚蠢的，所以我決定
     ，我需要一種可以廣泛擴充的語言。

     在 1989 年的聖誕節假期，我有很多自由時間，所以我決定來嘗試一下。在
     接下來的一年裡，雖然我大部分時間仍然在為此而努力，但 Python 在
     Amoeba 專案中的使用得到了越來越多的成功，且同事們的回饋也使我為它增
     加了許多早期的改進。

     在 1991 年 2月，經過一年多的發展，我決定將它發表到 USENET。其他的記
     錄都在 ‘Misc/HISTORY’ 檔案中。


File: python.info,  Node: 什麼是 Python 擅長的事情？,  Next: Python 的版本編號系統是如何運作的？,  Prev: 當初為什麼 Python 會被創造出來？,  Up: 一般資訊

10.1.1.5 什麼是 Python 擅長的事情？
...................................

Python 是一種高階的、用途廣泛的程式設計語言，可以用來解決許多不同類型的
問題。

這個語言提供了一個大型的標準函式庫，涵蓋了字串處理（正規表示式、
Unicode、檔案之間的差異計算）、網際網路協定（HTTP、FTP、SMTP、XML-RPC、
POP、IMAP）、軟體工程（單元測試、日誌記錄、效能分析、剖析 Python 程式碼
）以及作業系統介面（系統呼叫、檔案系統、TCP/IP 插座 (socket)）等領域。請
查看 *note Python 標準函式庫 (Standard Library): 12a. 的目錄，以了解可用
的函式。此外，還有各式各樣的第三方擴充。請查詢 Python 套件索引 (Python
Package Index)(1) 來尋找你有興趣的套件。

   ---------- Footnotes ----------

   (1) https://pypi.org


File: python.info,  Node: Python 的版本編號系統是如何運作的？,  Next: 我要如何得到 Python 的原始碼複本？,  Prev: 什麼是 Python 擅長的事情？,  Up: 一般資訊

10.1.1.6 Python 的版本編號系統是如何運作的？
............................................

Python 各版本會被編號為 "A.B.C" 或 "A.B"：

   * 'A' 為主要版本編號 - 它只會在語言中有真正重大的變更時才會增加。

   * 'B' 為次要版本編號 - 只有在影響範圍較小的變更出現時增加。

   * 'C' 為微小版本編號 —- 會在每個錯誤修正發布 (bugfix release) 增加。

並非所有的發布版本都是錯誤修正發布版本。在一個新功能發布版本的準備階段，
會發布一系列開發版本，標示為 alpha、beta 或候選發布版本 (release
candidate)。Alpha 是介面尚未最終化的早期發布版本；看到兩個 alpha 發布版
本之間的介面變更並不會令人意外。Beta 則更為穩定，保留了現有的介面，但可
能會增加新的模組，而候選發布版本會被凍結，除了需要修正關鍵錯誤之外，不會
再進行任何變更。

Alpha、beta 和候選發布版本都有一個額外的後綴：

   * Alpha 版本的後綴是 "aN"，其中 'N' 是某個較小的數字。

   * Beta 版本的後綴是 "bN"，其中 'N' 是某個較小的數字。

   * 候選發布版本的後綴是 "rcN"，其中 'N' 是某個較小的數字。

換句話說，所有標記為 '2.0aN' 的版本都在標記為 '2.0bN' 的版本之前，而
'2.0bN' 版本都在標記為 '2.0rcN' 的版本之前，而'它們'都是在 2.0 版之前。

你還可以找到帶有「+」後綴的版本編號，例如「2.2+」。這些是未發布的版本，
直接從 CPython 的開發儲存庫被建置。實際上，在每一次的最終次要版本發布完
成之後，版本編號將會被增加到下一個次要版本，並成為「a0」版，例如「
2.4a0」。

See the Developer's Guide(1) for more information about the development
cycle, and PEP 387(2) to learn more about Python's backward
compatibility policy.  See also the documentation for *note sys.version:
15c, *note sys.hexversion: 4199, and *note sys.version_info: 645.

   ---------- Footnotes ----------

   (1) https://devguide.python.org/developer-workflow/development-cycle/

   (2) https://peps.python.org/pep-0387/


File: python.info,  Node: 我要如何得到 Python 的原始碼複本？,  Next: 我要如何取得 Python 的說明文件？,  Prev: Python 的版本編號系統是如何運作的？,  Up: 一般資訊

10.1.1.7 我要如何得到 Python 的原始碼複本？
...........................................

最新的 Python 原始碼發行版永遠可以從 python.org 取得，在
‘https://www.python.org/downloads/’。最新的開發中原始碼可以在
‘https://github.com/python/cpython/’ 取得。

原始碼發行版是一個以 gzip 壓縮的 tar 檔，它包含完整的 C 原始碼、Sphinx 格
式的說明文件、Python 函式庫模組、範例程式，以及幾個好用的可自由發行軟體
。該原始碼在大多數 UNIX 平台上，都是可以立即編譯及運行的。

關於取得和編譯原始碼的詳細資訊，請參閱 Python 開發人員指南中的 "Getting
Started" 段落(1)。

   ---------- Footnotes ----------

   (1) https://devguide.python.org/setup/


File: python.info,  Node: 我要如何取得 Python 的說明文件？,  Next: 我從來沒有寫過程式，有沒有 Python 的教學？,  Prev: 我要如何得到 Python 的原始碼複本？,  Up: 一般資訊

10.1.1.8 我要如何取得 Python 的說明文件？
.........................................

Python 目前穩定版本的標準說明文件可在 ‘https://docs.python.org/3/’ 找到
。PDF、純文字和可下載的 HTML 版本也可在
‘https://docs.python.org/3/download.html’ 找到。

說明文件是以 reStructuredText 格式編寫，並由 Sphinx 說明文件工具(1)處理
。說明文件的 reStructuredText 原始碼是 Python 原始碼發行版的一部分。

   ---------- Footnotes ----------

   (1) https://sphinx-doc.org/


File: python.info,  Node: 我從來沒有寫過程式，有沒有 Python 的教學？,  Next: 有沒有 Python 專屬的新聞群組或郵件討論群？,  Prev: 我要如何取得 Python 的說明文件？,  Up: 一般資訊

10.1.1.9 我從來沒有寫過程式，有沒有 Python 的教學？
...................................................

有許多可用的教學和書籍。標準說明文件包括 *note Python 教學: 1ae0.。

要尋找 Python 程式設計初學者的資訊，包括教學資源列表，請參閱初學者指南
(1)。

   ---------- Footnotes ----------

   (1) https://wiki.python.org/moin/BeginnersGuide


File: python.info,  Node: 有沒有 Python 專屬的新聞群組或郵件討論群？,  Next: 如何取得 Python 的 beta 測試版本？,  Prev: 我從來沒有寫過程式，有沒有 Python 的教學？,  Up: 一般資訊

10.1.1.10 有沒有 Python 專屬的新聞群組或郵件討論群？
....................................................

有一個新聞群組 (newsgroup)，‘comp.lang.python’，也有一個郵件討論群
(mailing list)，python-list(1)。新聞群組和郵件討論群是彼此相通的——如果你
能閱讀新聞，則無需加入郵件討論群。‘comp.lang.python’ 的流量很高，每天會
收到數百篇文章，而 Usenet 的讀者通常較能夠處理這樣的文章數量。

新的軟體發布版本及事件的通知，可以在 comp.lang.python.announce 中找到，
這是一個低流量的精選討論群，每天收到大約五篇文章。它也能從
python-announce 郵件討論群(2)的頁面中訂閱。

關於其他郵件討論群和新聞群組的更多資訊，可以在
‘https://www.python.org/community/lists/’ 中找到。

   ---------- Footnotes ----------

   (1) https://mail.python.org/mailman/listinfo/python-list

   (2) 
https://mail.python.org/mailman3/lists/python-announce-list.python.org/


File: python.info,  Node: 如何取得 Python 的 beta 測試版本？,  Next: 如何提交 Python 的錯誤報告和修補程式？,  Prev: 有沒有 Python 專屬的新聞群組或郵件討論群？,  Up: 一般資訊

10.1.1.11 如何取得 Python 的 beta 測試版本？
............................................

Alpha 和 beta 發布版本可以從 ‘https://www.python.org/downloads/’ 取得。
所有的發布版本都會在 comp.lang.python 和 comp.lang.python.announce 新聞
群組上宣布，也會在 Python 首頁 ‘https://www.python.org/’ 中宣布；RSS 新
聞摘要也是可使用的。

你也可以藉由 Git 來存取 Python 的開發版本。更多詳細資訊，請參閱 Python 開
發人員指南(1)。

   ---------- Footnotes ----------

   (1) https://devguide.python.org/


File: python.info,  Node: 如何提交 Python 的錯誤報告和修補程式？,  Next: 是否有關於 Python 的任何已出版文章可供參考？,  Prev: 如何取得 Python 的 beta 測試版本？,  Up: 一般資訊

10.1.1.12 如何提交 Python 的錯誤報告和修補程式？
................................................

要回報一個錯誤 (bug) 或提交一個修補程式 (patch)，請使用於
‘https://github.com/python/cpython/issues’ 的問題追蹤系統。

關於如何開發 Python 的更多資訊，請參閱 Python 開發人員指南(1)。

   ---------- Footnotes ----------

   (1) https://devguide.python.org/


File: python.info,  Node: 是否有關於 Python 的任何已出版文章可供參考？,  Next: 有沒有關於 Python 的書？,  Prev: 如何提交 Python 的錯誤報告和修補程式？,  Up: 一般資訊

10.1.1.13 是否有關於 Python 的任何已出版文章可供參考？
......................................................

也許最好是引用你最喜歡的關於 Python 的書。

最早討論 Python 的文章(1)是在 1991 年寫的，但現在來看已經過時了。

     Guido van Rossum 和 Jelke de Boer，「使用 Python 程式設計語言互動式
     測試遠端伺服器」，CWI 季刊，第 4 卷，第 4 期（1991 年 12 月），阿姆
     斯特丹，第 283–303 頁。

   ---------- Footnotes ----------

   (1) https://ir.cwi.nl/pub/18204


File: python.info,  Node: 有沒有關於 Python 的書？,  Next: www python org 的真實位置在哪裡？,  Prev: 是否有關於 Python 的任何已出版文章可供參考？,  Up: 一般資訊

10.1.1.14 有沒有關於 Python 的書？
..................................

有，很多書已經出版，也有更多正在出版中的書。請參閱 python.org 的 wiki 在
‘https://wiki.python.org/moin/PythonBooks’ 頁面中的書目清單。

你也可以在網路書店搜尋關鍵字「Python」，並過濾掉 Monty Python 的結果；或
者可以搜尋「Python」和「語言」。


File: python.info,  Node: www python org 的真實位置在哪裡？,  Next: 為什麼要取名為 Python？,  Prev: 有沒有關於 Python 的書？,  Up: 一般資訊

10.1.1.15 www.python.org 的真實位置在哪裡？
...........................................

Python 專案的基礎建設遍佈世界各地，由 Python 基礎建設團隊管理。詳細資訊
在此(1)。

   ---------- Footnotes ----------

   (1) https://infra.psf.io


File: python.info,  Node: 為什麼要取名為 Python？,  Next: 我需要喜歡「Monty Python 的飛行馬戲團」嗎？,  Prev: www python org 的真實位置在哪裡？,  Up: 一般資訊

10.1.1.16 為什麼要取名為 Python？
.................................

當 Guido van Rossum 開始實作 Python 時，他也正在閱讀 1970 年代 BBC 喜劇
節目「Monty Python 的飛行馬戲團」(1)的出版劇本。Van Rossum 認為他需要一
個簡短、獨特且略帶神秘的名字，因此他決定將該語言稱為 Python。

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Monty_Python


File: python.info,  Node: 我需要喜歡「Monty Python 的飛行馬戲團」嗎？,  Prev: 為什麼要取名為 Python？,  Up: 一般資訊

10.1.1.17 我需要喜歡「Monty Python 的飛行馬戲團」嗎？
.....................................................

不需要，但它有幫助。:)


File: python.info,  Node: 在真實世界中的 Python,  Prev: 一般資訊,  Up: 一般的 Python 常見問答集

10.1.2 在真實世界中的 Python
----------------------------

* Menu:

* Python 的穩定性如何？::
* 有多少人在使用 Python？::
* 有沒有任何重要的專案使用 Python 完成開發？::
* Python 未來預期會有哪些新的開發？::
* 對 Python 提出不相容的變更建議是否適當？::
* Python 對於入門的程式設計師而言是否為好的語言？::


File: python.info,  Node: Python 的穩定性如何？,  Next: 有多少人在使用 Python？,  Up: 在真實世界中的 Python

10.1.2.1 Python 的穩定性如何？
..............................

非常穩定。自從 1991 年開始，大約每隔 6 到 18 個月都會發布新的穩定版本，
而且這看起來會繼續進行。從 3.9 版開始，Python 每隔 12 個月將會釋出一個新
功能發行版本 ( PEP 602(1))。

開發人員會釋出針對先前版本的錯誤修正發布版本，因此現有發布版本的穩定性會
逐漸提高。錯誤修正發布版本是由版本編號的第三個部分表示（例如 3.5.3，
3.6.2），這些版本會被用於改善穩定性；在錯誤修正發布版本中，只會包含針對
已知問題的修正，並且會保證介面在一系列的錯誤修正發布版本中維持不變。

最新的穩定發布版本隨時都可以在 Python 下載頁面(2)上找到。Python 有兩個生
產就緒 (production-ready) 的版本：2.x 和 3.x。推薦的版本是 3.x，此版本能
被那些最為廣泛使用的函式庫所支援。雖然 2.x 仍然被廣泛使用，但它已不再被
維護(3)。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0602/

   (2) https://www.python.org/downloads/

   (3) https://peps.python.org/pep-0373/


File: python.info,  Node: 有多少人在使用 Python？,  Next: 有沒有任何重要的專案使用 Python 完成開發？,  Prev: Python 的穩定性如何？,  Up: 在真實世界中的 Python

10.1.2.2 有多少人在使用 Python？
................................

可能有幾百萬個使用者，但實際的數量是難以確定的。

Python 是可以免費下載的，所以不會有銷售數據，而且它可以從許多不同的網站
取得，並與許多 Linux 發行版套裝在一起，所以下載次數的統計也無法反映完整
的情況。

comp.lang.python 新聞群組非常活躍，但並非所有 Python 使用者都會在該群組
發表文章或甚至閱讀它。


File: python.info,  Node: 有沒有任何重要的專案使用 Python 完成開發？,  Next: Python 未來預期會有哪些新的開發？,  Prev: 有多少人在使用 Python？,  Up: 在真實世界中的 Python

10.1.2.3 有沒有任何重要的專案使用 Python 完成開發？
...................................................

要查看使用 Python 的專案清單，請參閱
‘https://www.python.org/about/success’。藉由查詢過去的 Python 會議記錄
(1)可以看見來自許多不同公司和組織的貢獻。

備受矚目的 Python 專案包括 Mailman 郵件討論群管理員(2)和 Zope 應用程式伺
服器(3)。有一些 Linux 發行版，最著名的是 Red Hat(4)，已經用 Python 編寫
了部分或全部的安裝程式及系統管理軟體。內部使用 Python 的公司包括 Google、
Yahoo 和 Lucasfilm Ltd。

   ---------- Footnotes ----------

   (1) https://www.python.org/community/workshops/

   (2) https://www.list.org

   (3) https://www.zope.dev

   (4) https://www.redhat.com


File: python.info,  Node: Python 未來預期會有哪些新的開發？,  Next: 對 Python 提出不相容的變更建議是否適當？,  Prev: 有沒有任何重要的專案使用 Python 完成開發？,  Up: 在真實世界中的 Python

10.1.2.4 Python 未來預期會有哪些新的開發？
..........................................

請至 ‘https://peps.python.org/’ 參閱 Python 增強提案 (Python Enhancement
Proposal, PEP)。PEP 是用來描述一項被建議的 Python 新功能的設計文件，它提
供了簡潔的技術規範及基本原理。請尋找一篇名為「Python X.Y Release
Schedule（發布時程表）」的 PEP，其中 X.Y 是一個尚未公開發布的版本。

新的開發會在 python-dev 郵件討論群(1)中討論。

   ---------- Footnotes ----------

   (1) https://mail.python.org/mailman3/lists/python-dev.python.org/


File: python.info,  Node: 對 Python 提出不相容的變更建議是否適當？,  Next: Python 對於入門的程式設計師而言是否為好的語言？,  Prev: Python 未來預期會有哪些新的開發？,  Up: 在真實世界中的 Python

10.1.2.5 對 Python 提出不相容的變更建議是否適當？
.................................................

一般來說，不適當。全世界已經有數百萬行 Python 程式碼，因此在語言中的任何
變更，若會使現有程式的一小部分成為無效，它都是不被允許的。即使你可以提供
轉換程式，仍然會有需要更新全部說明文件的問題；市面上已經有很多介紹
Python 的書，而我們不想一下子就把它們都變為無效。

如果一項功能必須被變更，那麼一定要提供逐步升級的路徑。 PEP 5(1) 描述了要
引進反向不相容 (backward-incompatible) 的變更，同時也要對使用者的擾亂最
小化，所需遵循的程序。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0005/


File: python.info,  Node: Python 對於入門的程式設計師而言是否為好的語言？,  Prev: 對 Python 提出不相容的變更建議是否適當？,  Up: 在真實世界中的 Python

10.1.2.6 Python 對於入門的程式設計師而言是否為好的語言？
........................................................

是的。

學生們仍然普遍地會從一種程序語言和靜態型別語言 (statically typed
language) 開始入門，這些語言像是 Pascal、C，或是 C++ 或 Java 的某個子集
。透過學習 Python 作為他們的第一個語言，學生們可能會學得更好。Python 具
有非常簡單且一致的語法和一個大型的標準函式庫，最重要的是，在入門程式設計
課程中使用 Python 可以讓學生專注於重要的程式設計技巧，例如問題的分解和資
料型別的設計。使用 Python，可以快速地向學生介紹基本觀念，例如迴圈和程序
。他們甚至可能在第一堂課中就學到使用者自訂的物件。

對於以前從未進行過程式設計的學生來說，使用靜態型別語言似乎是不自然的。它
使學生必須掌握額外的複雜性，並減慢了課程的節奏。學生們正在試圖學著像電腦
一樣思考、分解問題、設計一致的介面，並封裝資料。雖然從長遠來看，學習使用
靜態型別語言很重要，但在學生的第一堂程式設計課程中，它不一定是最好的課程
主題。

Python 的許多其他面向使它成為一種很好的第一語言。像 Java 一樣，Python 有
一個大型的標準函式庫，因此學生可以在課程的早期就被指派程式設計的專案，且
這些專案能夠'做'一些事情。指派的內容不會侷限於標準的四功能計算機和平衡檢
驗程式。透過使用標準函式庫，學生可以在學習程式設計基礎知識的同時，獲得處
理真實應用程式的滿足感。使用標準函式庫還可以教導學生程式碼再使用 (code
reuse) 的課題。像是 PyGame 等第三方模組也有助於延伸學生的學習領域。

Python 的互動式直譯器使學生能夠在程式設計時測試語言的功能。他們可以開著
一個運行直譯器的視窗，同時在另一個視窗中輸入他們的程式原始碼。如果他們不
記得 list（串列）的 method（方法），他們可以像這樣做：

     >>> L = []
     >>> dir(L)
     ['__add__', '__class__', '__contains__', '__delattr__', '__delitem__',
     '__dir__', '__doc__', '__eq__', '__format__', '__ge__',
     '__getattribute__', '__getitem__', '__gt__', '__hash__', '__iadd__',
     '__imul__', '__init__', '__iter__', '__le__', '__len__', '__lt__',
     '__mul__', '__ne__', '__new__', '__reduce__', '__reduce_ex__',
     '__repr__', '__reversed__', '__rmul__', '__setattr__', '__setitem__',
     '__sizeof__', '__str__', '__subclasshook__', 'append', 'clear',
     'copy', 'count', 'extend', 'index', 'insert', 'pop', 'remove',
     'reverse', 'sort']
     >>> [d for d in dir(L) if '__' not in d]
     ['append', 'clear', 'copy', 'count', 'extend', 'index', 'insert', 'pop', 'remove', 'reverse', 'sort']

     >>> help(L.append)
     Help on built-in function append:

     append(...)
         L.append(object) -> None -- append object to end

     >>> L.append(1)
     >>> L
     [1]

有了直譯器，當學生正在程式設計時，說明文件永遠都不會遠離他們。

Python 也有很好的 IDE。IDLE 是 Python 的一個跨平臺 IDE，它以 Python 編寫
並使用 Tkinter。Emacs 使用者會很高興知道 Emacs 有一個非常好的 Python 模
式。這些程式設計環境全部都能提供語法突顯 (syntax highlighting)、自動縮排
，以及在編寫程式時存取互動式直譯器。要查看 Python 編輯環境的完整清單，請
參閱 Python wiki(1)。

如果你想討論 Python 在教育領域中的使用，你可能會有興趣加入 edu-sig 郵件
討論群(2)。

   ---------- Footnotes ----------

   (1) https://wiki.python.org/moin/PythonEditors

   (2) https://www.python.org/community/sigs/current/edu-sig


File: python.info,  Node: 程式開發常見問答集,  Next: 設計和歷史常見問答集,  Prev: 一般的 Python 常見問答集,  Up: Python 常見問題

10.2 程式開發常見問答集
=======================

* Menu:

* 常見問題::
* 核心語言::
* 數字和字串::
* Performance: Performance<4>.
* Sequences (Tuples/Lists): Sequences Tuples/Lists.
* 物件::
* 模組: 模組<5>.


File: python.info,  Node: 常見問題,  Next: 核心語言,  Up: 程式開發常見問答集

10.2.1 常見問題
---------------

* Menu:

* 是否有可以使用在程式碼階段,具有中斷點,步驟執行等功能的除錯器？: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？.
* 有沒有工具能夠幫忙找 bug 或執行靜態分析？::
* 如何從 Python 腳本建立獨立的二進位檔案？::
* Python 程式碼是否有編碼標準或風格指南？::


File: python.info,  Node: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？,  Next: 有沒有工具能夠幫忙找 bug 或執行靜態分析？,  Up: 常見問題

10.2.1.1 是否有可以使用在程式碼階段,具有中斷點,步驟執行等功能的除錯器？
.......................................................................

有的。

下面描述了幾個 Python 除錯器，內建函式 *note breakpoint(): 219. 允許你進
入其中任何一個。

pdb 模組是一個簡單但足夠的 Python 控制台模式除錯器。它是標準 Python 函式
庫的一部分，並*note 記錄在函式庫參考手冊: 94.中。你也可以參考 pdb 的程式
碼作為範例來編寫自己的除錯器。

IDLE 交互式開發環境，它是標準 Python 發行版的一部分（通常作為
Tools/scripts/idle3(1) 提供），包括一個圖形除錯器。

PythonWin 是一個 Python IDE，它包含一個基於 pdb 的 GUI 除錯器。
PythonWin 除錯器為斷點著色並具有許多很酷的功能，例如除錯非 PythonWin 程
式。 PythonWin 作為 pywin32(2) 專案的一部分和作為 ActivePython(3) 的一部
分發佈。

Eric(4) 是一個基於 PyQt 和 Scintilla 編輯元件所建構的 IDE。

trepan3k(5) 是一個類似 gdb 的除錯器。

Visual Studio Code(6) 是一個整合了版本控制軟體與除錯工具的 IDE。

有數個商業化Python整合化開發工具包含圖形除錯功能。這些包含：

   * Wing IDE(7)

   * Komodo IDE(8)

   * PyCharm(9)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/blob/main/Tools/scripts/idle3

   (2) https://github.com/mhammond/pywin32

   (3) https://www.activestate.com/products/python/

   (4) https://eric-ide.python-projects.org/

   (5) https://github.com/rocky/python3-trepan/

   (6) https://code.visualstudio.com/

   (7) https://wingware.com/

   (8) https://www.activestate.com/products/komodo-ide/

   (9) https://www.jetbrains.com/pycharm/


File: python.info,  Node: 有沒有工具能夠幫忙找 bug 或執行靜態分析？,  Next: 如何從 Python 腳本建立獨立的二進位檔案？,  Prev: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？,  Up: 常見問題

10.2.1.2 有沒有工具能夠幫忙找 bug 或執行靜態分析？
..................................................

有的。

Pylint(1) 和 Pyflakes(2) 進行基本檢查以幫助你儘早抓出錯誤。

靜態型別檢查器，例如 Mypy(3)、Pyre(4) 和 Pytype(5) 可以檢查 Python 原始
碼中的型別提示。

   ---------- Footnotes ----------

   (1) https://pylint.pycqa.org/en/latest/index.html

   (2) https://github.com/PyCQA/pyflakes

   (3) https://mypy-lang.org/

   (4) https://pyre-check.org/

   (5) https://github.com/google/pytype


File: python.info,  Node: 如何從 Python 腳本建立獨立的二進位檔案？,  Next: Python 程式碼是否有編碼標準或風格指南？,  Prev: 有沒有工具能夠幫忙找 bug 或執行靜態分析？,  Up: 常見問題

10.2.1.3 如何從 Python 腳本建立獨立的二進位檔案？
.................................................

You don't need the ability to compile Python to C code if all you want
is a stand-alone program that users can download and run without having
to install the Python distribution first.  There are a number of tools
that determine the set of modules required by a program and bind these
modules together with a Python binary to produce a single executable.

One is to use the freeze tool, which is included in the Python source
tree as Tools/freeze(1).  It converts Python byte code to C arrays; with
a C compiler you can embed all your modules into a new program, which is
then linked with the standard Python modules.

It works by scanning your source recursively for import statements (in
both forms) and looking for the modules in the standard Python path as
well as in the source directory (for built-in modules).  It then turns
the bytecode for modules written in Python into C code (array
initializers that can be turned into code objects using the marshal
module) and creates a custom-made config file that only contains those
built-in modules which are actually used in the program.  It then
compiles the generated C code and links it with the rest of the Python
interpreter to form a self-contained binary which acts exactly like your
script.

以下套件可以幫助建立 console 和 GUI 可執行檔案：

   * Nuitka(2)（跨平台）

   * PyInstaller(3)（跨平台）

   * PyOxidizer(4)（跨平台）

   * cx_Freeze(5)（跨平台）

   * py2app(6)（僅限 macOS）

   * py2exe(7)（僅限 Windows）

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/main/Tools/freeze

   (2) https://nuitka.net/

   (3) https://pyinstaller.org/

   (4) https://pyoxidizer.readthedocs.io/en/stable/

   (5) https://marcelotduarte.github.io/cx_Freeze/

   (6) https://github.com/ronaldoussoren/py2app

   (7) https://www.py2exe.org/


File: python.info,  Node: Python 程式碼是否有編碼標準或風格指南？,  Prev: 如何從 Python 腳本建立獨立的二進位檔案？,  Up: 常見問題

10.2.1.4 Python 程式碼是否有編碼標準或風格指南？
................................................

是的。標準函式庫模組所需的編碼風格稱為 PEP 8(1)。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0008/


File: python.info,  Node: 核心語言,  Next: 數字和字串,  Prev: 常見問題,  Up: 程式開發常見問答集

10.2.2 核心語言
---------------

* Menu:

* 為什麼當變數有值時，我仍得到錯誤訊息 UnboundLocalError？::
* Python 的區域變數和全域變數有什麼規則？::
* Why do lambdas defined in a loop with different values all return the same result?::
* 如何跨模組共享全域變數？::
* What are the "best practices" for using import in a module?::
* Why are default values shared between objects?::
* How can I pass optional or keyword parameters from one function to another?::
* 引數 (arguments) 和參數 (parameters) 有什麼區別？: 引數 arguments 和參數 parameters 有什麼區別？.
* 為什麼更改 list 'y' 也會更改 list 'x'？::
* How do I write a function with output parameters (call by reference)?: How do I write a function with output parameters call by reference ?.
* How do you make a higher order function in Python?::
* 如何在 Python 中複製物件？::
* 如何找到物件的方法或屬性？::
* 我的程式碼如何發現物件的名稱？::
* What's up with the comma operator's precedence?::
* 是否有等效於 C 的 "?;" 三元運算子？: 是否有等效於 C 的 "? " 三元運算子？.
* Is it possible to write obfuscated one-liners in Python?::
* What does the slash(/) in the parameter list of a function mean?: What does the slash / in the parameter list of a function mean?.


File: python.info,  Node: 為什麼當變數有值時，我仍得到錯誤訊息 UnboundLocalError？,  Next: Python 的區域變數和全域變數有什麼規則？,  Up: 核心語言

10.2.2.1 為什麼當變數有值時，我仍得到錯誤訊息 UnboundLocalError？
.................................................................

It can be a surprise to get the *note UnboundLocalError: 14a4. in
previously working code when it is modified by adding an assignment
statement somewhere in the body of a function.

這段程式碼:

     >>> x = 10
     >>> def bar():
     ...     print(x)
     ...
     >>> bar()
     10

可以執行,但是這段程式:

     >>> x = 10
     >>> def foo():
     ...     print(x)
     ...     x += 1

導致 ‘UnboundLocalError’：

     >>> foo()
     Traceback (most recent call last):
       ...
     UnboundLocalError: local variable 'x' referenced before assignment

This is because when you make an assignment to a variable in a scope,
that variable becomes local to that scope and shadows any similarly
named variable in the outer scope.  Since the last statement in foo
assigns a new value to ‘x’, the compiler recognizes it as a local
variable.  Consequently when the earlier ‘print(x)’ attempts to print
the uninitialized local variable and an error results.

在上面的示例中，你可以透過將其聲明為全域變數來存取外部範圍變數：

     >>> x = 10
     >>> def foobar():
     ...     global x
     ...     print(x)
     ...     x += 1
     ...
     >>> foobar()
     10

This explicit declaration is required in order to remind you that
(unlike the superficially analogous situation with class and instance
variables) you are actually modifying the value of the variable in the
outer scope:

     >>> print(x)
     11

You can do a similar thing in a nested scope using the *note nonlocal:
123e. keyword:

     >>> def foo():
     ...    x = 10
     ...    def bar():
     ...        nonlocal x
     ...        print(x)
     ...        x += 1
     ...    bar()
     ...    print(x)
     ...
     >>> foo()
     10
     11


File: python.info,  Node: Python 的區域變數和全域變數有什麼規則？,  Next: Why do lambdas defined in a loop with different values all return the same result?,  Prev: 為什麼當變數有值時，我仍得到錯誤訊息 UnboundLocalError？,  Up: 核心語言

10.2.2.2 Python 的區域變數和全域變數有什麼規則？
................................................

In Python, variables that are only referenced inside a function are
implicitly global.  If a variable is assigned a value anywhere within
the function's body, it's assumed to be a local unless explicitly
declared as global.

Though a bit surprising at first, a moment's consideration explains
this.  On one hand, requiring *note global: 170. for assigned variables
provides a bar against unintended side-effects.  On the other hand, if
‘global’ was required for all global references, you'd be using ‘global’
all the time.  You'd have to declare as global every reference to a
built-in function or to a component of an imported module.  This clutter
would defeat the usefulness of the ‘global’ declaration for identifying
side-effects.


File: python.info,  Node: Why do lambdas defined in a loop with different values all return the same result?,  Next: 如何跨模組共享全域變數？,  Prev: Python 的區域變數和全域變數有什麼規則？,  Up: 核心語言

10.2.2.3 Why do lambdas defined in a loop with different values all return the same result?
...........................................................................................

假設你使用 for 循環來定義幾個不同的 lambda（甚至是普通函式），例如：

     >>> squares = []
     >>> for x in range(5):
     ...     squares.append(lambda: x**2)

This gives you a list that contains 5 lambdas that calculate ‘x**2’.
You might expect that, when called, they would return, respectively,
‘0’, ‘1’, ‘4’, ‘9’, and ‘16’.  However, when you actually try you will
see that they all return ‘16’:

     >>> squares[2]()
     16
     >>> squares[4]()
     16

This happens because ‘x’ is not local to the lambdas, but is defined in
the outer scope, and it is accessed when the lambda is called -- not
when it is defined.  At the end of the loop, the value of ‘x’ is ‘4’, so
all the functions now return ‘4**2’, i.e.  ‘16’.  You can also verify
this by changing the value of ‘x’ and see how the results of the lambdas
change:

     >>> x = 8
     >>> squares[2]()
     64

In order to avoid this, you need to save the values in variables local
to the lambdas, so that they don't rely on the value of the global ‘x’:

     >>> squares = []
     >>> for x in range(5):
     ...     squares.append(lambda n=x: n**2)

Here, ‘n=x’ creates a new variable ‘n’ local to the lambda and computed
when the lambda is defined so that it has the same value that ‘x’ had at
that point in the loop.  This means that the value of ‘n’ will be ‘0’ in
the first lambda, ‘1’ in the second, ‘2’ in the third, and so on.
Therefore each lambda will now return the correct result:

     >>> squares[2]()
     4
     >>> squares[4]()
     16

請注意，此行為並非 lambda 所特有，也適用於常規函式。


File: python.info,  Node: 如何跨模組共享全域變數？,  Next: What are the "best practices" for using import in a module?,  Prev: Why do lambdas defined in a loop with different values all return the same result?,  Up: 核心語言

10.2.2.4 如何跨模組共享全域變數？
.................................

The canonical way to share information across modules within a single
program is to create a special module (often called config or cfg).
Just import the config module in all modules of your application; the
module then becomes available as a global name.  Because there is only
one instance of each module, any changes made to the module object get
reflected everywhere.  For example:

config.py：

     x = 0   # Default value of the 'x' configuration setting

mod.py：

     import config
     config.x = 1

main.py：

     import config
     import mod
     print(config.x)

Note that using a module is also the basis for implementing the
singleton design pattern, for the same reason.


File: python.info,  Node: What are the "best practices" for using import in a module?,  Next: Why are default values shared between objects?,  Prev: 如何跨模組共享全域變數？,  Up: 核心語言

10.2.2.5 What are the "best practices" for using import in a module?
....................................................................

In general, don't use ‘from modulename import *’.  Doing so clutters the
importer's namespace, and makes it much harder for linters to detect
undefined names.

Import modules at the top of a file.  Doing so makes it clear what other
modules your code requires and avoids questions of whether the module
name is in scope.  Using one import per line makes it easy to add and
delete module imports, but using multiple imports per line uses less
screen space.

It's good practice if you import modules in the following order:

  1. 標準函式庫模組 —— 例如 *note sys: c3.、*note os: 91.、*note
     argparse: 5.、*note re: a7.

  2. third-party library modules (anything installed in Python's
     site-packages directory) - e.g.  ‘dateutil’, ‘requests’,
     ‘PIL.Image’

  3. locally developed modules

It is sometimes necessary to move imports to a function or class to
avoid problems with circular imports.  Gordon McMillan says:

     Circular imports are fine where both modules use the "import
     <module>" form of import.  They fail when the 2nd module wants to
     grab a name out of the first ("from module import name") and the
     import is at the top level.  That's because names in the 1st are
     not yet available, because the first module is busy importing the
     2nd.

In this case, if the second module is only used in one function, then
the import can easily be moved into that function.  By the time the
import is called, the first module will have finished initializing, and
the second module can do its import.

It may also be necessary to move imports out of the top level of code if
some of the modules are platform-specific.  In that case, it may not
even be possible to import all of the modules at the top of the file.
In this case, importing the correct modules in the corresponding
platform-specific code is a good option.

Only move imports into a local scope, such as inside a function
definition, if it's necessary to solve a problem such as avoiding a
circular import or are trying to reduce the initialization time of a
module.  This technique is especially helpful if many of the imports are
unnecessary depending on how the program executes.  You may also want to
move imports into a function if the modules are only ever used in that
function.  Note that loading a module the first time may be expensive
because of the one time initialization of the module, but loading a
module multiple times is virtually free, costing only a couple of
dictionary lookups.  Even if the module name has gone out of scope, the
module is probably available in *note sys.modules: 186e.


File: python.info,  Node: Why are default values shared between objects?,  Next: How can I pass optional or keyword parameters from one function to another?,  Prev: What are the "best practices" for using import in a module?,  Up: 核心語言

10.2.2.6 Why are default values shared between objects?
.......................................................

This type of bug commonly bites neophyte programmers.  Consider this
function:

     def foo(mydict={}):  # Danger: shared reference to one dict for all calls
         ... compute something ...
         mydict[key] = value
         return mydict

The first time you call this function, ‘mydict’ contains a single item.
The second time, ‘mydict’ contains two items because when ‘foo()’ begins
executing, ‘mydict’ starts out with an item already in it.

It is often expected that a function call creates new objects for
default values.  This is not what happens.  Default values are created
exactly once, when the function is defined.  If that object is changed,
like the dictionary in this example, subsequent calls to the function
will refer to this changed object.

By definition, immutable objects such as numbers, strings, tuples, and
‘None’, are safe from change.  Changes to mutable objects such as
dictionaries, lists, and class instances can lead to confusion.

Because of this feature, it is good programming practice to not use
mutable objects as default values.  Instead, use ‘None’ as the default
value and inside the function, check if the parameter is ‘None’ and
create a new list/dictionary/whatever if it is.  For example, don't
write:

     def foo(mydict={}):
         ...

但是：

     def foo(mydict=None):
         if mydict is None:
             mydict = {}  # create a new dict for local namespace

This feature can be useful.  When you have a function that's
time-consuming to compute, a common technique is to cache the parameters
and the resulting value of each call to the function, and return the
cached value if the same value is requested again.  This is called
"memoizing", and can be implemented like this:

     # Callers can only provide two parameters and optionally pass _cache by keyword
     def expensive(arg1, arg2, *, _cache={}):
         if (arg1, arg2) in _cache:
             return _cache[(arg1, arg2)]

         # Calculate the value
         result = ... expensive computation ...
         _cache[(arg1, arg2)] = result           # Store result in the cache
         return result

You could use a global variable containing a dictionary instead of the
default value; it's a matter of taste.


File: python.info,  Node: How can I pass optional or keyword parameters from one function to another?,  Next: 引數 arguments 和參數 parameters 有什麼區別？,  Prev: Why are default values shared between objects?,  Up: 核心語言

10.2.2.7 How can I pass optional or keyword parameters from one function to another?
....................................................................................

Collect the arguments using the ‘*’ and ‘**’ specifiers in the
function's parameter list; this gives you the positional arguments as a
tuple and the keyword arguments as a dictionary.  You can then pass
these arguments when calling another function by using ‘*’ and ‘**’:

     def f(x, *args, **kwargs):
         ...
         kwargs['width'] = '14.3c'
         ...
         g(x, *args, **kwargs)


File: python.info,  Node: 引數 arguments 和參數 parameters 有什麼區別？,  Next: 為什麼更改 list 'y' 也會更改 list 'x'？,  Prev: How can I pass optional or keyword parameters from one function to another?,  Up: 核心語言

10.2.2.8 引數 (arguments) 和參數 (parameters) 有什麼區別？
..........................................................

*note Parameters: 1dee. are defined by the names that appear in a
function definition, whereas *note arguments: 3ef. are the values
actually passed to a function when calling it.  Parameters define what
*note kind of arguments: 1dee. a function can accept.  For example,
given the function definition:

     def func(foo, bar=None, **kwargs):
         pass

'foo'、'bar' 和 'kwargs' 是 ‘func’ 的參數。然而，當呼叫 ‘func’ 時，例如
：

     func(42, bar=314, extra=somevar)

‘42’ 、 ‘314’ 和 ‘somevar’ 是引數。


File: python.info,  Node: 為什麼更改 list 'y' 也會更改 list 'x'？,  Next: How do I write a function with output parameters call by reference ?,  Prev: 引數 arguments 和參數 parameters 有什麼區別？,  Up: 核心語言

10.2.2.9 為什麼更改 list 'y' 也會更改 list 'x'？
................................................

如果你寫了像這樣的程式碼：

     >>> x = []
     >>> y = x
     >>> y.append(10)
     >>> y
     [10]
     >>> x
     [10]

你可能想知道為什麼將一個元素附加到 ‘y’ 時也會改變 ‘x’。

產生這個結果的原因有兩個：

  1. Variables are simply names that refer to objects.  Doing ‘y = x’
     doesn't create a copy of the list - it creates a new variable ‘y’
     that refers to the same object ‘x’ refers to.  This means that
     there is only one object (the list), and both ‘x’ and ‘y’ refer to
     it.

  2. list 是 *note mutable: 1b07.，這意味著你可以變更它們的內容。

After the call to ‘append()’, the content of the mutable object has
changed from ‘[]’ to ‘[10]’.  Since both the variables refer to the same
object, using either name accesses the modified value ‘[10]’.

If we instead assign an immutable object to ‘x’:

     >>> x = 5  # ints are immutable
     >>> y = x
     >>> x = x + 1  # 5 can't be mutated, we are creating a new object here
     >>> x
     6
     >>> y
     5

we can see that in this case ‘x’ and ‘y’ are not equal anymore.  This is
because integers are *note immutable: 1b02, and when we do ‘x = x + 1’
we are not mutating the int ‘5’ by incrementing its value; instead, we
are creating a new object (the int ‘6’) and assigning it to ‘x’ (that
is, changing which object ‘x’ refers to).  After this assignment we have
two objects (the ints ‘6’ and ‘5’) and two variables that refer to them
(‘x’ now refers to ‘6’ but ‘y’ still refers to ‘5’).

Some operations (for example ‘y.append(10)’ and ‘y.sort()’) mutate the
object, whereas superficially similar operations (for example ‘y = y +
[10]’ and *note sorted(y): b75.) create a new object.  In general in
Python (and in all cases in the standard library) a method that mutates
an object will return ‘None’ to help avoid getting the two types of
operations confused.  So if you mistakenly write ‘y.sort()’ thinking it
will give you a sorted copy of ‘y’, you'll instead end up with ‘None’,
which will likely cause your program to generate an easily diagnosed
error.

However, there is one class of operations where the same operation
sometimes has different behaviors with different types: the augmented
assignment operators.  For example, ‘+=’ mutates lists but not tuples or
ints (‘a_list += [1, 2, 3]’ is equivalent to ‘a_list.extend([1, 2, 3])’
and mutates ‘a_list’, whereas ‘some_tuple += (1, 2, 3)’ and ‘some_int +=
1’ create new objects).

換句話說：

   * If we have a mutable object (*note list: 5b6, *note dict: 23b,
     *note set: 57d, etc.), we can use some specific operations to
     mutate it and all the variables that refer to it will see the
     change.

   * If we have an immutable object (*note str: 3f2, *note int: 23c,
     *note tuple: 322, etc.), all the variables that refer to it will
     always see the same value, but operations that transform that value
     into a new value always return a new object.

If you want to know if two variables refer to the same object or not,
you can use the *note is: 2c6. operator, or the built-in function *note
id(): 1390.


File: python.info,  Node: How do I write a function with output parameters call by reference ?,  Next: How do you make a higher order function in Python?,  Prev: 為什麼更改 list 'y' 也會更改 list 'x'？,  Up: 核心語言

10.2.2.10 How do I write a function with output parameters (call by reference)?
...............................................................................

Remember that arguments are passed by assignment in Python.  Since
assignment just creates references to objects, there's no alias between
an argument name in the caller and callee, and so no call-by-reference
per se.  You can achieve the desired effect in a number of ways.

  1. 透過回傳結果的元組：

          >>> def func1(a, b):
          ...     a = 'new-value'        # a and b are local names
          ...     b = b + 1              # assigned to new objects
          ...     return a, b            # return new values
          ...
          >>> x, y = 'old-value', 99
          >>> func1(x, y)
          ('new-value', 100)

     This is almost always the clearest solution.

  2. By using global variables.  This isn't thread-safe, and is not
     recommended.

  3. By passing a mutable (changeable in-place) object:

          >>> def func2(a):
          ...     a[0] = 'new-value'     # 'a' references a mutable list
          ...     a[1] = a[1] + 1        # changes a shared object
          ...
          >>> args = ['old-value', 99]
          >>> func2(args)
          >>> args
          ['new-value', 100]

  4. By passing in a dictionary that gets mutated:

          >>> def func3(args):
          ...     args['a'] = 'new-value'     # args is a mutable dictionary
          ...     args['b'] = args['b'] + 1   # change it in-place
          ...
          >>> args = {'a': 'old-value', 'b': 99}
          >>> func3(args)
          >>> args
          {'a': 'new-value', 'b': 100}

  5. Or bundle up values in a class instance:

          >>> class Namespace:
          ...     def __init__(self, /, **args):
          ...         for key, value in args.items():
          ...             setattr(self, key, value)
          ...
          >>> def func4(args):
          ...     args.a = 'new-value'        # args is a mutable Namespace
          ...     args.b = args.b + 1         # change object in-place
          ...
          >>> args = Namespace(a='old-value', b=99)
          >>> func4(args)
          >>> vars(args)
          {'a': 'new-value', 'b': 100}

     There's almost never a good reason to get this complicated.

Your best choice is to return a tuple containing the multiple results.


File: python.info,  Node: How do you make a higher order function in Python?,  Next: 如何在 Python 中複製物件？,  Prev: How do I write a function with output parameters call by reference ?,  Up: 核心語言

10.2.2.11 How do you make a higher order function in Python?
............................................................

You have two choices: you can use nested scopes or you can use callable
objects.  For example, suppose you wanted to define ‘linear(a,b)’ which
returns a function ‘f(x)’ that computes the value ‘a*x+b’.  Using nested
scopes:

     def linear(a, b):
         def result(x):
             return a * x + b
         return result

或者使用可呼叫物件：

     class linear:

         def __init__(self, a, b):
             self.a, self.b = a, b

         def __call__(self, x):
             return self.a * x + self.b

In both cases,

     taxes = linear(0.3, 2)

gives a callable object where ‘taxes(10e6) == 0.3 * 10e6 + 2’.

The callable object approach has the disadvantage that it is a bit
slower and results in slightly longer code.  However, note that a
collection of callables can share their signature via inheritance:

     class exponential(linear):
         # __init__ inherited
         def __call__(self, x):
             return self.a * (x ** self.b)

物件可以封裝多個方法的狀態：

     class counter:

         value = 0

         def set(self, x):
             self.value = x

         def up(self):
             self.value = self.value + 1

         def down(self):
             self.value = self.value - 1

     count = counter()
     inc, dec, reset = count.up, count.down, count.set

這裡的 ‘inc()’、‘dec()’ 和 ‘reset()’ 就像共享相同計數變數的函式一樣。


File: python.info,  Node: 如何在 Python 中複製物件？,  Next: 如何找到物件的方法或屬性？,  Prev: How do you make a higher order function in Python?,  Up: 核心語言

10.2.2.12 如何在 Python 中複製物件？
....................................

In general, try *note copy.copy(): 4d8. or *note copy.deepcopy(): b12.
for the general case.  Not all objects can be copied, but most can.

Some objects can be copied more easily.  Dictionaries have a *note
copy(): b77. method:

     newdict = olddict.copy()

序列可以透過切片 (slicing) 複製：

     new_l = l[:]


File: python.info,  Node: 如何找到物件的方法或屬性？,  Next: 我的程式碼如何發現物件的名稱？,  Prev: 如何在 Python 中複製物件？,  Up: 核心語言

10.2.2.13 如何找到物件的方法或屬性？
....................................

For an instance ‘x’ of a user-defined class, *note dir(x): 5d8. returns
an alphabetized list of the names containing the instance attributes and
methods and attributes defined by its class.


File: python.info,  Node: 我的程式碼如何發現物件的名稱？,  Next: What's up with the comma operator's precedence?,  Prev: 如何找到物件的方法或屬性？,  Up: 核心語言

10.2.2.14 我的程式碼如何發現物件的名稱？
........................................

Generally speaking, it can't, because objects don't really have names.
Essentially, assignment always binds a name to a value; the same is true
of ‘def’ and ‘class’ statements, but in that case the value is a
callable.  Consider the following code:

     >>> class A:
     ...     pass
     ...
     >>> B = A
     >>> a = B()
     >>> b = a
     >>> print(b)
     <__main__.A object at 0x16D07CC>
     >>> print(a)
     <__main__.A object at 0x16D07CC>

Arguably the class has a name: even though it is bound to two names and
invoked through the name ‘B’ the created instance is still reported as
an instance of class ‘A’.  However, it is impossible to say whether the
instance's name is ‘a’ or ‘b’, since both names are bound to the same
value.

Generally speaking it should not be necessary for your code to "know the
names" of particular values.  Unless you are deliberately writing
introspective programs, this is usually an indication that a change of
approach might be beneficial.

在 comp.lang.python 中，Fredrik Lundh 曾針對這個問題給出了一個極好的比喻
：

     就像你在門廊上發現的那隻貓的名字一樣：貓（物件）本身不能告訴你它的
     名字，它也不關心 - 所以找出它叫什麼的唯一方法是詢問所有鄰居（命名空
     間）是否是他們的貓（物件）...

     ....如果你發現它有很多名字，或者根本沒有名字，請不要感到驚訝！


File: python.info,  Node: What's up with the comma operator's precedence?,  Next: 是否有等效於 C 的 "? " 三元運算子？,  Prev: 我的程式碼如何發現物件的名稱？,  Up: 核心語言

10.2.2.15 What's up with the comma operator's precedence?
.........................................................

Comma is not an operator in Python.  Consider this session:

     >>> "a" in "b", "a"
     (False, 'a')

Since the comma is not an operator, but a separator between expressions
the above is evaluated as if you had entered:

     ("a" in "b"), "a"

而不是：

     "a" in ("b", "a")

The same is true of the various assignment operators (‘=’, ‘+=’ etc).
They are not truly operators but syntactic delimiters in assignment
statements.


File: python.info,  Node: 是否有等效於 C 的 "? " 三元運算子？,  Next: Is it possible to write obfuscated one-liners in Python?,  Prev: What's up with the comma operator's precedence?,  Up: 核心語言

10.2.2.16 是否有等效於 C 的 "?:" 三元運算子？
.............................................

有的，語法如下：

     [on_true] if [expression] else [on_false]

     x, y = 50, 25
     small = x if x < y else y

Before this syntax was introduced in Python 2.5, a common idiom was to
use logical operators:

     [expression] and [on_true] or [on_false]

However, this idiom is unsafe, as it can give wrong results when
'on_true' has a false boolean value.  Therefore, it is always better to
use the ‘... if ... else ...’ form.


File: python.info,  Node: Is it possible to write obfuscated one-liners in Python?,  Next: What does the slash / in the parameter list of a function mean?,  Prev: 是否有等效於 C 的 "? " 三元運算子？,  Up: 核心語言

10.2.2.17 Is it possible to write obfuscated one-liners in Python?
..................................................................

Yes.  Usually this is done by nesting *note lambda: 1234. within
‘lambda’.  See the following three examples, slightly adapted from Ulf
Bartelt:

     from functools import reduce

     # Primes < 1000
     print(list(filter(None,map(lambda y:y*reduce(lambda x,y:x*y!=0,
     map(lambda x,y=y:y%x,range(2,int(pow(y,0.5)+1))),1),range(2,1000)))))

     # First 10 Fibonacci numbers
     print(list(map(lambda x,f=lambda x,f:(f(x-1,f)+f(x-2,f)) if x>1 else 1:
     f(x,f), range(10))))

     # Mandelbrot set
     print((lambda Ru,Ro,Iu,Io,IM,Sx,Sy:reduce(lambda x,y:x+'\n'+y,map(lambda y,
     Iu=Iu,Io=Io,Ru=Ru,Ro=Ro,Sy=Sy,L=lambda yc,Iu=Iu,Io=Io,Ru=Ru,Ro=Ro,i=IM,
     Sx=Sx,Sy=Sy:reduce(lambda x,y:x+y,map(lambda x,xc=Ru,yc=yc,Ru=Ru,Ro=Ro,
     i=i,Sx=Sx,F=lambda xc,yc,x,y,k,f=lambda xc,yc,x,y,k,f:(k<=0)or (x*x+y*y
     >=4.0) or 1+f(xc,yc,x*x-y*y+xc,2.0*x*y+yc,k-1,f):f(xc,yc,x,y,k,f):chr(
     64+F(Ru+x*(Ro-Ru)/Sx,yc,0,0,i)),range(Sx))):L(Iu+y*(Io-Iu)/Sy),range(Sy
     ))))(-2.1, 0.7, -1.2, 1.2, 30, 80, 24))
     #    \___ ___/  \___ ___/  |   |   |__ lines on screen
     #        V          V      |   |______ columns on screen
     #        |          |      |__________ maximum of "iterations"
     #        |          |_________________ range on y axis
     #        |____________________________ range on x axis

孩子們，不要在家裡嘗試這個！


File: python.info,  Node: What does the slash / in the parameter list of a function mean?,  Prev: Is it possible to write obfuscated one-liners in Python?,  Up: 核心語言

10.2.2.18 What does the slash(/) in the parameter list of a function mean?
..........................................................................

A slash in the argument list of a function denotes that the parameters
prior to it are positional-only.  Positional-only parameters are the
ones without an externally usable name.  Upon calling a function that
accepts positional-only parameters, arguments are mapped to parameters
based solely on their position.  For example, *note divmod(): 945. is a
function that accepts positional-only parameters.  Its documentation
looks like this:

     >>> help(divmod)
     Help on built-in function divmod in module builtins:

     divmod(x, y, /)
         Return the tuple (x//y, x%y).  Invariant: div*y + mod == x.

The slash at the end of the parameter list means that both parameters
are positional-only.  Thus, calling *note divmod(): 945. with keyword
arguments would lead to an error:

     >>> divmod(x=3, y=4)
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: divmod() takes no keyword arguments


File: python.info,  Node: 數字和字串,  Next: Performance<4>,  Prev: 核心語言,  Up: 程式開發常見問答集

10.2.3 數字和字串
-----------------

* Menu:

* 如何指定十六進位和八進位整數？::
* 為什麼 -22 // 10 回傳 -3？::
* How do I get int literal attribute instead of SyntaxError?::
* 如何將字串轉換為數字？::
* 如何將數字轉換為字串？::
* How do I modify a string in place?::
* How do I use strings to call functions/methods?::
* Is there an equivalent to Perl's chomp() for removing trailing newlines from strings?: Is there an equivalent to Perl's chomp for removing trailing newlines from strings?.
* Is there a scanf() or sscanf() equivalent?: Is there a scanf or sscanf equivalent?.
* 'UnicodeDecodeError' 或 'UnicodeEncodeErro' 錯誤是什麼意思？::
* Can I end a raw string with an odd number of backslashes?::


File: python.info,  Node: 如何指定十六進位和八進位整數？,  Next: 為什麼 -22 // 10 回傳 -3？,  Up: 數字和字串

10.2.3.1 如何指定十六進位和八進位整數？
.......................................

To specify an octal digit, precede the octal value with a zero, and then
a lower or uppercase "o".  For example, to set the variable "a" to the
octal value "10" (8 in decimal), type:

     >>> a = 0o10
     >>> a
     8

Hexadecimal is just as easy.  Simply precede the hexadecimal number with
a zero, and then a lower or uppercase "x".  Hexadecimal digits can be
specified in lower or uppercase.  For example, in the Python
interpreter:

     >>> a = 0xa5
     >>> a
     165
     >>> b = 0XB2
     >>> b
     178


File: python.info,  Node: 為什麼 -22 // 10 回傳 -3？,  Next: How do I get int literal attribute instead of SyntaxError?,  Prev: 如何指定十六進位和八進位整數？,  Up: 數字和字串

10.2.3.2 為什麼 -22 // 10 回傳 -3？
...................................

It's primarily driven by the desire that ‘i % j’ have the same sign as
‘j’.  If you want that, and also want:

     i == (i // j) * j + (i % j)

那麼整數除法必須回傳向下取整的結果。 C 還要求保留​​該識別性，然後截斷 ‘i
// j’ 的編譯器需要使 ‘i % j’ 具有與 ‘i’ 相同的符號。

There are few real use cases for ‘i % j’ when ‘j’ is negative.  When ‘j’
is positive, there are many, and in virtually all of them it's more
useful for ‘i % j’ to be ‘>= 0’.  If the clock says 10 now, what did it
say 200 hours ago?  ‘-190 % 12 == 2’ is useful; ‘-190 % 12 == -10’ is a
bug waiting to bite.


File: python.info,  Node: How do I get int literal attribute instead of SyntaxError?,  Next: 如何將字串轉換為數字？,  Prev: 為什麼 -22 // 10 回傳 -3？,  Up: 數字和字串

10.2.3.3 How do I get int literal attribute instead of SyntaxError?
...................................................................

Trying to lookup an ‘int’ literal attribute in the normal manner gives a
*note SyntaxError: 173. because the period is seen as a decimal point:

     >>> 1.__class__
       File "<stdin>", line 1
       1.__class__
        ^
     SyntaxError: invalid decimal literal

The solution is to separate the literal from the period with either a
space or parentheses.

     >>> 1 .__class__
     <class 'int'>
     >>> (1).__class__
     <class 'int'>


File: python.info,  Node: 如何將字串轉換為數字？,  Next: 如何將數字轉換為字串？,  Prev: How do I get int literal attribute instead of SyntaxError?,  Up: 數字和字串

10.2.3.4 如何將字串轉換為數字？
...............................

For integers, use the built-in *note int(): 23c. type constructor, e.g.
‘int('144') == 144’.  Similarly, *note float(): 2c8. converts to a
floating-point number, e.g.  ‘float('144') == 144.0’.

By default, these interpret the number as decimal, so that ‘int('0144')
== 144’ holds true, and ‘int('0x144')’ raises *note ValueError: 1e7.
‘int(string, base)’ takes the base to convert from as a second optional
argument, so ‘int( '0x144', 16) == 324’.  If the base is specified as 0,
the number is interpreted using Python's rules: a leading '0o' indicates
octal, and '0x' indicates a hex number.

Do not use the built-in function *note eval(): 163. if all you need is
to convert strings to numbers.  *note eval(): 163. will be significantly
slower and it presents a security risk: someone could pass you a Python
expression that might have unwanted side effects.  For example, someone
could pass ‘__import__('os').system("rm -rf $HOME")’ which would erase
your home directory.

*note eval(): 163. also has the effect of interpreting numbers as Python
expressions, so that e.g.  ‘eval('09')’ gives a syntax error because
Python does not allow leading '0' in a decimal number (except '0').


File: python.info,  Node: 如何將數字轉換為字串？,  Next: How do I modify a string in place?,  Prev: 如何將字串轉換為數字？,  Up: 數字和字串

10.2.3.5 如何將數字轉換為字串？
...............................

To convert, e.g., the number ‘144’ to the string ‘'144'’, use the
built-in type constructor *note str(): 3f2.  If you want a hexadecimal
or octal representation, use the built-in functions *note hex(): 1262.
or *note oct(): 1261.  For fancy formatting, see the *note f-string（f
字串）: 94d. and *note 格式化文字語法: 131e. sections, e.g.
‘"{:04d}".format(144)’ yields ‘'0144'’ and ‘"{:.3f}".format(1.0/3.0)’
yields ‘'0.333'’.


File: python.info,  Node: How do I modify a string in place?,  Next: How do I use strings to call functions/methods?,  Prev: 如何將數字轉換為字串？,  Up: 數字和字串

10.2.3.6 How do I modify a string in place?
...........................................

You can't, because strings are immutable.  In most situations, you
should simply construct a new string from the various parts you want to
assemble it from.  However, if you need an object with the ability to
modify in-place unicode data, try using an *note io.StringIO: ecb.
object or the *note array: 6. module:

     >>> import io
     >>> s = "Hello, world"
     >>> sio = io.StringIO(s)
     >>> sio.getvalue()
     'Hello, world'
     >>> sio.seek(7)
     7
     >>> sio.write("there!")
     6
     >>> sio.getvalue()
     'Hello, there!'

     >>> import array
     >>> a = array.array('w', s)
     >>> print(a)
     array('w', 'Hello, world')
     >>> a[0] = 'y'
     >>> print(a)
     array('w', 'yello, world')
     >>> a.tounicode()
     'yello, world'


File: python.info,  Node: How do I use strings to call functions/methods?,  Next: Is there an equivalent to Perl's chomp for removing trailing newlines from strings?,  Prev: How do I modify a string in place?,  Up: 數字和字串

10.2.3.7 How do I use strings to call functions/methods?
........................................................

There are various techniques.

   * The best is to use a dictionary that maps strings to functions.
     The primary advantage of this technique is that the strings do not
     need to match the names of the functions.  This is also the primary
     technique used to emulate a case construct:

          def a():
              pass

          def b():
              pass

          dispatch = {'go': a, 'stop': b}  # Note lack of parens for funcs

          dispatch[get_input()]()  # Note trailing parens to call function

   * 使用內建函式 *note getattr(): b78.：

          import foo
          getattr(foo, 'bar')()

     Note that *note getattr(): b78. works on any object, including
     classes, class instances, modules, and so on.

     This is used in several places in the standard library, like this:

          class Foo:
              def do_foo(self):
                  ...

              def do_bar(self):
                  ...

          f = getattr(foo_instance, 'do_' + opname)
          f()

   * 使用 *note locals(): 127. 解析函式名稱：

          def myFunc():
              print("hello")

          fname = "myFunc"

          f = locals()[fname]
          f()


File: python.info,  Node: Is there an equivalent to Perl's chomp for removing trailing newlines from strings?,  Next: Is there a scanf or sscanf equivalent?,  Prev: How do I use strings to call functions/methods?,  Up: 數字和字串

10.2.3.8 Is there an equivalent to Perl's chomp() for removing trailing newlines from strings?
..............................................................................................

You can use ‘S.rstrip("\r\n")’ to remove all occurrences of any line
terminator from the end of the string ‘S’ without removing other
trailing whitespace.  If the string ‘S’ represents more than one line,
with several empty lines at the end, the line terminators for all the
blank lines will be removed:

     >>> lines = ("line 1 \r\n"
     ...          "\r\n"
     ...          "\r\n")
     >>> lines.rstrip("\n\r")
     'line 1 '

Since this is typically only desired when reading text one line at a
time, using ‘S.rstrip()’ this way works well.


File: python.info,  Node: Is there a scanf or sscanf equivalent?,  Next: 'UnicodeDecodeError' 或 'UnicodeEncodeErro' 錯誤是什麼意思？,  Prev: Is there an equivalent to Perl's chomp for removing trailing newlines from strings?,  Up: 數字和字串

10.2.3.9 Is there a scanf() or sscanf() equivalent?
...................................................

Not as such.

For simple input parsing, the easiest approach is usually to split the
line into whitespace-delimited words using the *note split(): e4c.
method of string objects and then convert decimal strings to numeric
values using *note int(): 23c. or *note float(): 2c8.  ‘split()’
supports an optional "sep" parameter which is useful if the line uses
something other than whitespace as a separator.

For more complicated input parsing, regular expressions are more
powerful than C's ‘sscanf’ and better suited for the task.


File: python.info,  Node: 'UnicodeDecodeError' 或 'UnicodeEncodeErro' 錯誤是什麼意思？,  Next: Can I end a raw string with an odd number of backslashes?,  Prev: Is there a scanf or sscanf equivalent?,  Up: 數字和字串

10.2.3.10 'UnicodeDecodeError' 或 'UnicodeEncodeErro' 錯誤是什麼意思？
......................................................................

請參閱 *note Unicode HOWTO: 123b.。


File: python.info,  Node: Can I end a raw string with an odd number of backslashes?,  Prev: 'UnicodeDecodeError' 或 'UnicodeEncodeErro' 錯誤是什麼意思？,  Up: 數字和字串

10.2.3.11 Can I end a raw string with an odd number of backslashes?
...................................................................

A raw string ending with an odd number of backslashes will escape the
string's quote:

     >>> r'C:\this\will\not\work\'
       File "<stdin>", line 1
         r'C:\this\will\not\work\'
              ^
     SyntaxError: unterminated string literal (detected at line 1)

There are several workarounds for this.  One is to use regular strings
and double the backslashes:

     >>> 'C:\\this\\will\\work\\'
     'C:\\this\\will\\work\\'

Another is to concatenate a regular string containing an escaped
backslash to the raw string:

     >>> r'C:\this\will\work' '\\'
     'C:\\this\\will\\work\\'

It is also possible to use *note os.path.join(): 1527. to append a
backslash on Windows:

     >>> os.path.join(r'C:\this\will\work', '')
     'C:\\this\\will\\work\\'

Note that while a backslash will "escape" a quote for the purposes of
determining where the raw string ends, no escaping occurs when
interpreting the value of the raw string.  That is, the backslash
remains present in the value of the raw string:

     >>> r'backslash\'preserved'
     "backslash\\'preserved"

Also see the specification in the *note language reference: 1d96.


File: python.info,  Node: Performance<4>,  Next: Sequences Tuples/Lists,  Prev: 數字和字串,  Up: 程式開發常見問答集

10.2.4 Performance
------------------

* Menu:

* 我的程式太慢了。我該如何加快速度？::
* What is the most efficient way to concatenate many strings together?::


File: python.info,  Node: 我的程式太慢了。我該如何加快速度？,  Next: What is the most efficient way to concatenate many strings together?,  Up: Performance<4>

10.2.4.1 我的程式太慢了。我該如何加快速度？
...........................................

That's a tough one, in general.  First, here are a list of things to
remember before diving further:

   * Performance characteristics vary across Python implementations.
     This FAQ focuses on *note CPython: 699.

   * Behaviour can vary across operating systems, especially when
     talking about I/O or multi-threading.

   * You should always find the hot spots in your program 'before'
     attempting to optimize any code (see the *note profile: 9d.
     module).

   * Writing benchmark scripts will allow you to iterate quickly when
     searching for improvements (see the *note timeit: d8. module).

   * It is highly recommended to have good code coverage (through unit
     testing or any other technique) before potentially introducing
     regressions hidden in sophisticated optimizations.

That being said, there are many tricks to speed up Python code.  Here
are some general principles which go a long way towards reaching
acceptable performance levels:

   * Making your algorithms faster (or changing to faster ones) can
     yield much larger benefits than trying to sprinkle
     micro-optimization tricks all over your code.

   * Use the right data structures.  Study documentation for the *note
     內建型別: 206b. and the *note collections: 16. module.

   * When the standard library provides a primitive for doing something,
     it is likely (although not guaranteed) to be faster than any
     alternative you may come up with.  This is doubly true for
     primitives written in C, such as builtins and some extension types.
     For example, be sure to use either the *note list.sort(): b76.
     built-in method or the related *note sorted(): b75. function to do
     sorting (and see the *note 排序技法: 205a. for examples of
     moderately advanced usage).

   * Abstractions tend to create indirections and force the interpreter
     to work more.  If the levels of indirection outweigh the amount of
     useful work done, your program will be slower.  You should avoid
     excessive abstraction, especially under the form of tiny functions
     or methods (which are also often detrimental to readability).

If you have reached the limit of what pure Python can allow, there are
tools to take you further away.  For example, Cython(1) can compile a
slightly modified version of Python code into a C extension, and can be
used on many different platforms.  Cython can take advantage of
compilation (and optional type annotations) to make your code
significantly faster than when interpreted.  If you are confident in
your C programming skills, you can also *note write a C extension
module: 1ae1. yourself.

也參考
......

有個 wiki 頁面專門介紹效能改進小提示(2)。

   ---------- Footnotes ----------

   (1) https://cython.org

   (2) https://wiki.python.org/moin/PythonSpeed/PerformanceTips


File: python.info,  Node: What is the most efficient way to concatenate many strings together?,  Prev: 我的程式太慢了。我該如何加快速度？,  Up: Performance<4>

10.2.4.2 What is the most efficient way to concatenate many strings together?
.............................................................................

*note str: 3f2. and *note bytes: 1a5. objects are immutable, therefore
concatenating many strings together is inefficient as each concatenation
creates a new object.  In the general case, the total runtime cost is
quadratic in the total string length.

To accumulate many *note str: 3f2. objects, the recommended idiom is to
place them into a list and call *note str.join(): 2088. at the end:

     chunks = []
     for s in my_strings:
         chunks.append(s)
     result = ''.join(chunks)

(another reasonably efficient idiom is to use *note io.StringIO: ecb.)

To accumulate many *note bytes: 1a5. objects, the recommended idiom is
to extend a *note bytearray: 4e3. object using in-place concatenation
(the ‘+=’ operator):

     result = bytearray()
     for b in my_bytes_objects:
         result += b


File: python.info,  Node: Sequences Tuples/Lists,  Next: 物件,  Prev: Performance<4>,  Up: 程式開發常見問答集

10.2.5 Sequences (Tuples/Lists)
-------------------------------

* Menu:

* How do I convert between tuples and lists?::
* What's a negative index?::
* How do I iterate over a sequence in reverse order?::
* How do you remove duplicates from a list?::
* How do you remove multiple items from a list::
* How do you make an array in Python?::
* How do I create a multidimensional list?::
* How do I apply a method or function to a sequence of objects?::
* Why does a_tuple[i] += ['item'] raise an exception when the addition works?::
* I want to do a complicated sort; can you do a Schwartzian Transform in Python?: I want to do a complicated sort can you do a Schwartzian Transform in Python?.
* How can I sort one list by values from another list?::


File: python.info,  Node: How do I convert between tuples and lists?,  Next: What's a negative index?,  Up: Sequences Tuples/Lists

10.2.5.1 How do I convert between tuples and lists?
...................................................

The type constructor ‘tuple(seq)’ converts any sequence (actually, any
iterable) into a tuple with the same items in the same order.

For example, ‘tuple([1, 2, 3])’ yields ‘(1, 2, 3)’ and ‘tuple('abc')’
yields ‘('a', 'b', 'c')’.  If the argument is a tuple, it does not make
a copy but returns the same object, so it is cheap to call *note
tuple(): 322. when you aren't sure that an object is already a tuple.

The type constructor ‘list(seq)’ converts any sequence or iterable into
a list with the same items in the same order.  For example, ‘list((1, 2,
3))’ yields ‘[1, 2, 3]’ and ‘list('abc')’ yields ‘['a', 'b', 'c']’.  If
the argument is a list, it makes a copy just like ‘seq[:]’ would.


File: python.info,  Node: What's a negative index?,  Next: How do I iterate over a sequence in reverse order?,  Prev: How do I convert between tuples and lists?,  Up: Sequences Tuples/Lists

10.2.5.2 What's a negative index?
.................................

Python sequences are indexed with positive numbers and negative numbers.
For positive numbers 0 is the first index 1 is the second index and so
forth.  For negative indices -1 is the last index and -2 is the
penultimate (next to last) index and so forth.  Think of ‘seq[-n]’ as
the same as ‘seq[len(seq)-n]’.

Using negative indices can be very convenient.  For example ‘S[:-1]’ is
all of the string except for its last character, which is useful for
removing the trailing newline from a string.


File: python.info,  Node: How do I iterate over a sequence in reverse order?,  Next: How do you remove duplicates from a list?,  Prev: What's a negative index?,  Up: Sequences Tuples/Lists

10.2.5.3 How do I iterate over a sequence in reverse order?
...........................................................

Use the *note reversed(): 80a. built-in function:

     for x in reversed(sequence):
         ...  # do something with x ...

This won't touch your original sequence, but build a new copy with
reversed order to iterate over.


File: python.info,  Node: How do you remove duplicates from a list?,  Next: How do you remove multiple items from a list,  Prev: How do I iterate over a sequence in reverse order?,  Up: Sequences Tuples/Lists

10.2.5.4 How do you remove duplicates from a list?
..................................................

See the Python Cookbook for a long discussion of many ways to do this:

     ‘https://code.activestate.com/recipes/52560/’

If you don't mind reordering the list, sort it and then scan from the
end of the list, deleting duplicates as you go:

     if mylist:
         mylist.sort()
         last = mylist[-1]
         for i in range(len(mylist)-2, -1, -1):
             if last == mylist[i]:
                 del mylist[i]
             else:
                 last = mylist[i]

If all elements of the list may be used as set keys (i.e.  they are all
*note hashable: 5b5.) this is often faster

     mylist = list(set(mylist))

This converts the list into a set, thereby removing duplicates, and then
back into a list.


File: python.info,  Node: How do you remove multiple items from a list,  Next: How do you make an array in Python?,  Prev: How do you remove duplicates from a list?,  Up: Sequences Tuples/Lists

10.2.5.5 How do you remove multiple items from a list
.....................................................

As with removing duplicates, explicitly iterating in reverse with a
delete condition is one possibility.  However, it is easier and faster
to use slice replacement with an implicit or explicit forward iteration.
Here are three variations.:

     mylist[:] = filter(keep_function, mylist)
     mylist[:] = (x for x in mylist if keep_condition)
     mylist[:] = [x for x in mylist if keep_condition]

The list comprehension may be fastest.


File: python.info,  Node: How do you make an array in Python?,  Next: How do I create a multidimensional list?,  Prev: How do you remove multiple items from a list,  Up: Sequences Tuples/Lists

10.2.5.6 How do you make an array in Python?
............................................

Use a list:

     ["this", 1, "is", "an", "array"]

Lists are equivalent to C or Pascal arrays in their time complexity; the
primary difference is that a Python list can contain objects of many
different types.

The ‘array’ module also provides methods for creating arrays of fixed
types with compact representations, but they are slower to index than
lists.  Also note that NumPy(1) and other third party packages define
array-like structures with various characteristics as well.

To get Lisp-style linked lists, you can emulate 'cons cells' using
tuples:

     lisp_list = ("like",  ("this",  ("example", None) ) )

If mutability is desired, you could use lists instead of tuples.  Here
the analogue of a Lisp 'car' is ‘lisp_list[0]’ and the analogue of 'cdr'
is ‘lisp_list[1]’.  Only do this if you're sure you really need to,
because it's usually a lot slower than using Python lists.

   ---------- Footnotes ----------

   (1) https://numpy.org/


File: python.info,  Node: How do I create a multidimensional list?,  Next: How do I apply a method or function to a sequence of objects?,  Prev: How do you make an array in Python?,  Up: Sequences Tuples/Lists

10.2.5.7 How do I create a multidimensional list?
.................................................

You probably tried to make a multidimensional array like this:

     >>> A = [[None] * 2] * 3

如果你印出它，這看起來是正確的：

     >>> A
     [[None, None], [None, None], [None, None]]

But when you assign a value, it shows up in multiple places:

     >>> A[0][0] = 5
     >>> A
     [[5, None], [5, None], [5, None]]

The reason is that replicating a list with ‘*’ doesn't create copies, it
only creates references to the existing objects.  The ‘*3’ creates a
list containing 3 references to the same list of length two.  Changes to
one row will show in all rows, which is almost certainly not what you
want.

The suggested approach is to create a list of the desired length first
and then fill in each element with a newly created list:

     A = [None] * 3
     for i in range(3):
         A[i] = [None] * 2

This generates a list containing 3 different lists of length two.  You
can also use a list comprehension:

     w, h = 2, 3
     A = [[None] * w for i in range(h)]

Or, you can use an extension that provides a matrix datatype; NumPy(1)
is the best known.

   ---------- Footnotes ----------

   (1) https://numpy.org/


File: python.info,  Node: How do I apply a method or function to a sequence of objects?,  Next: Why does a_tuple[i] += ['item'] raise an exception when the addition works?,  Prev: How do I create a multidimensional list?,  Up: Sequences Tuples/Lists

10.2.5.8 How do I apply a method or function to a sequence of objects?
......................................................................

To call a method or function and accumulate the return values is a list,
a *note list comprehension: 672. is an elegant solution:

     result = [obj.method() for obj in mylist]

     result = [function(obj) for obj in mylist]

To just run the method or function without saving the return values, a
plain *note for: 2c3. loop will suffice:

     for obj in mylist:
         obj.method()

     for obj in mylist:
         function(obj)


File: python.info,  Node: Why does a_tuple[i] += ['item'] raise an exception when the addition works?,  Next: I want to do a complicated sort can you do a Schwartzian Transform in Python?,  Prev: How do I apply a method or function to a sequence of objects?,  Up: Sequences Tuples/Lists

10.2.5.9 Why does a_tuple[i] += ['item'] raise an exception when the addition works?
....................................................................................

This is because of a combination of the fact that augmented assignment
operators are 'assignment' operators, and the difference between mutable
and immutable objects in Python.

This discussion applies in general when augmented assignment operators
are applied to elements of a tuple that point to mutable objects, but
we'll use a ‘list’ and ‘+=’ as our exemplar.

If you wrote:

     >>> a_tuple = (1, 2)
     >>> a_tuple[0] += 1
     Traceback (most recent call last):
        ...
     TypeError: 'tuple' object does not support item assignment

The reason for the exception should be immediately clear: ‘1’ is added
to the object ‘a_tuple[0]’ points to (‘1’), producing the result object,
‘2’, but when we attempt to assign the result of the computation, ‘2’,
to element ‘0’ of the tuple, we get an error because we can't change
what an element of a tuple points to.

Under the covers, what this augmented assignment statement is doing is
approximately this:

     >>> result = a_tuple[0] + 1
     >>> a_tuple[0] = result
     Traceback (most recent call last):
       ...
     TypeError: 'tuple' object does not support item assignment

It is the assignment part of the operation that produces the error,
since a tuple is immutable.

When you write something like:

     >>> a_tuple = (['foo'], 'bar')
     >>> a_tuple[0] += ['item']
     Traceback (most recent call last):
       ...
     TypeError: 'tuple' object does not support item assignment

The exception is a bit more surprising, and even more surprising is the
fact that even though there was an error, the append worked:

     >>> a_tuple[0]
     ['foo', 'item']

To see why this happens, you need to know that (a) if an object
implements an *note __iadd__(): 1e64. magic method, it gets called when
the ‘+=’ augmented assignment is executed, and its return value is what
gets used in the assignment statement; and (b) for lists, ‘__iadd__()’
is equivalent to calling ‘extend()’ on the list and returning the list.
That's why we say that for lists, ‘+=’ is a "shorthand" for
‘list.extend()’:

     >>> a_list = []
     >>> a_list += [1]
     >>> a_list
     [1]

這等價於：

     >>> result = a_list.__iadd__([1])
     >>> a_list = result

The object pointed to by a_list has been mutated, and the pointer to the
mutated object is assigned back to ‘a_list’.  The end result of the
assignment is a no-op, since it is a pointer to the same object that
‘a_list’ was previously pointing to, but the assignment still happens.

Thus, in our tuple example what is happening is equivalent to:

     >>> result = a_tuple[0].__iadd__(['item'])
     >>> a_tuple[0] = result
     Traceback (most recent call last):
       ...
     TypeError: 'tuple' object does not support item assignment

The ‘__iadd__()’ succeeds, and thus the list is extended, but even
though ‘result’ points to the same object that ‘a_tuple[0]’ already
points to, that final assignment still results in an error, because
tuples are immutable.


File: python.info,  Node: I want to do a complicated sort can you do a Schwartzian Transform in Python?,  Next: How can I sort one list by values from another list?,  Prev: Why does a_tuple[i] += ['item'] raise an exception when the addition works?,  Up: Sequences Tuples/Lists

10.2.5.10 I want to do a complicated sort: can you do a Schwartzian Transform in Python?
........................................................................................

The technique, attributed to Randal Schwartz of the Perl community,
sorts the elements of a list by a metric which maps each element to its
"sort value".  In Python, use the ‘key’ argument for the *note
list.sort(): b76. method:

     Isorted = L[:]
     Isorted.sort(key=lambda s: int(s[10:15]))


File: python.info,  Node: How can I sort one list by values from another list?,  Prev: I want to do a complicated sort can you do a Schwartzian Transform in Python?,  Up: Sequences Tuples/Lists

10.2.5.11 How can I sort one list by values from another list?
..............................................................

Merge them into an iterator of tuples, sort the resulting list, and then
pick out the element you want.

     >>> list1 = ["what", "I'm", "sorting", "by"]
     >>> list2 = ["something", "else", "to", "sort"]
     >>> pairs = zip(list1, list2)
     >>> pairs = sorted(pairs)
     >>> pairs
     [("I'm", 'else'), ('by', 'sort'), ('sorting', 'to'), ('what', 'something')]
     >>> result = [x[1] for x in pairs]
     >>> result
     ['else', 'sort', 'to', 'something']


File: python.info,  Node: 物件,  Next: 模組<5>,  Prev: Sequences Tuples/Lists,  Up: 程式開發常見問答集

10.2.6 物件
-----------

* Menu:

* 什麼是類別 (class)？: 什麼是類別 class ？.
* 什麼是方法 (method)？: 什麼是方法 method ？.
* What is self?::
* How do I check if an object is an instance of a given class or of a subclass of it?::
* What is delegation?::
* How do I call a method defined in a base class from a derived class that extends it?::
* How can I organize my code to make it easier to change the base class?::
* How do I create static class data and static class methods?::
* How can I overload constructors (or methods) in Python?: How can I overload constructors or methods in Python?.
* I try to use __spam and I get an error about _SomeClassName__spam.: I try to use __spam and I get an error about _SomeClassName__spam.
* My class defines __del__ but it is not called when I delete the object.: My class defines __del__ but it is not called when I delete the object.
* How do I get a list of all instances of a given class?::
* Why does the result of id() appear to be not unique?: Why does the result of id appear to be not unique?.
* 我什麼時候可以依靠 is 運算子進行識別性測試？::
* 子類別如何控制不可變實例中存儲的資料？::
* 如何快取方法呼叫？::


File: python.info,  Node: 什麼是類別 class ？,  Next: 什麼是方法 method ？,  Up: 物件

10.2.6.1 什麼是類別 (class)？
.............................

A class is the particular object type created by executing a class
statement.  Class objects are used as templates to create instance
objects, which embody both the data (attributes) and code (methods)
specific to a datatype.

A class can be based on one or more other classes, called its base
class(es).  It then inherits the attributes and methods of its base
classes.  This allows an object model to be successively refined by
inheritance.  You might have a generic ‘Mailbox’ class that provides
basic accessor methods for a mailbox, and subclasses such as
‘MboxMailbox’, ‘MaildirMailbox’, ‘OutlookMailbox’ that handle various
specific mailbox formats.


File: python.info,  Node: 什麼是方法 method ？,  Next: What is self?,  Prev: 什麼是類別 class ？,  Up: 物件

10.2.6.2 什麼是方法 (method)？
..............................

A method is a function on some object ‘x’ that you normally call as
‘x.name(arguments...)’.  Methods are defined as functions inside the
class definition:

     class C:
         def meth(self, arg):
             return arg * 2 + self.attribute


File: python.info,  Node: What is self?,  Next: How do I check if an object is an instance of a given class or of a subclass of it?,  Prev: 什麼是方法 method ？,  Up: 物件

10.2.6.3 What is self?
......................

Self is merely a conventional name for the first argument of a method.
A method defined as ‘meth(self, a, b, c)’ should be called as ‘x.meth(a,
b, c)’ for some instance ‘x’ of the class in which the definition
occurs; the called method will think it is called as ‘meth(x, a, b, c)’.

另請參閱 *note 為何「self」在方法 (method) 定義和呼叫時一定要明確使用？:
4eb0.。


File: python.info,  Node: How do I check if an object is an instance of a given class or of a subclass of it?,  Next: What is delegation?,  Prev: What is self?,  Up: 物件

10.2.6.4 How do I check if an object is an instance of a given class or of a subclass of it?
............................................................................................

Use the built-in function *note isinstance(obj, cls): 3e8.  You can
check if an object is an instance of any of a number of classes by
providing a tuple instead of a single class, e.g.  ‘isinstance(obj,
(class1, class2, ...))’, and can also check whether an object is one of
Python's built-in types, e.g.  ‘isinstance(obj, str)’ or
‘isinstance(obj, (int, float, complex))’.

Note that *note isinstance(): 3e8. also checks for virtual inheritance
from an *note abstract base class: 114e.  So, the test will return
‘True’ for a registered class even if hasn't directly or indirectly
inherited from it.  To test for "true inheritance", scan the *note MRO:
3434. of the class:

     from collections.abc import Mapping

     class P:
          pass

     class C(P):
         pass

     Mapping.register(P)

     >>> c = C()
     >>> isinstance(c, C)        # direct
     True
     >>> isinstance(c, P)        # indirect
     True
     >>> isinstance(c, Mapping)  # virtual
     True

     # Actual inheritance chain
     >>> type(c).__mro__
     (<class 'C'>, <class 'P'>, <class 'object'>)

     # Test for "true inheritance"
     >>> Mapping in type(c).__mro__
     False

Note that most programs do not use *note isinstance(): 3e8. on
user-defined classes very often.  If you are developing the classes
yourself, a more proper object-oriented style is to define methods on
the classes that encapsulate a particular behaviour, instead of checking
the object's class and doing a different thing based on what class it
is.  For example, if you have a function that does something:

     def search(obj):
         if isinstance(obj, Mailbox):
             ...  # code to search a mailbox
         elif isinstance(obj, Document):
             ...  # code to search a document
         elif ...

A better approach is to define a ‘search()’ method on all the classes
and just call it:

     class Mailbox:
         def search(self):
             ...  # code to search a mailbox

     class Document:
         def search(self):
             ...  # code to search a document

     obj.search()


File: python.info,  Node: What is delegation?,  Next: How do I call a method defined in a base class from a derived class that extends it?,  Prev: How do I check if an object is an instance of a given class or of a subclass of it?,  Up: 物件

10.2.6.5 What is delegation?
............................

Delegation is an object oriented technique (also called a design
pattern).  Let's say you have an object ‘x’ and want to change the
behaviour of just one of its methods.  You can create a new class that
provides a new implementation of the method you're interested in
changing and delegates all other methods to the corresponding method of
‘x’.

Python programmers can easily implement delegation.  For example, the
following class implements a class that behaves like a file but converts
all written data to uppercase:

     class UpperOut:

         def __init__(self, outfile):
             self._outfile = outfile

         def write(self, s):
             self._outfile.write(s.upper())

         def __getattr__(self, name):
             return getattr(self._outfile, name)

Here the ‘UpperOut’ class redefines the ‘write()’ method to convert the
argument string to uppercase before calling the underlying
‘self._outfile.write()’ method.  All other methods are delegated to the
underlying ‘self._outfile’ object.  The delegation is accomplished via
the *note __getattr__(): 47a. method; consult *note the language
reference: 1e39. for more information about controlling attribute
access.

Note that for more general cases delegation can get trickier.  When
attributes must be set as well as retrieved, the class must define a
*note __setattr__(): 1e05. method too, and it must do so carefully.  The
basic implementation of ‘__setattr__()’ is roughly equivalent to the
following:

     class X:
         ...
         def __setattr__(self, name, value):
             self.__dict__[name] = value
         ...

Most ‘__setattr__()’ implementations must modify *note self.__dict__:
c04. to store local state for self without causing an infinite
recursion.


File: python.info,  Node: How do I call a method defined in a base class from a derived class that extends it?,  Next: How can I organize my code to make it easier to change the base class?,  Prev: What is delegation?,  Up: 物件

10.2.6.6 How do I call a method defined in a base class from a derived class that extends it?
.............................................................................................

使用內建的 *note super(): 483. 函式：

     class Derived(Base):
         def meth(self):
             super().meth()  # calls Base.meth

In the example, *note super(): 483. will automatically determine the
instance from which it was called (the ‘self’ value), look up the *note
method resolution order: 205c. (MRO) with ‘type(self).__mro__’, and
return the next in line after ‘Derived’ in the MRO: ‘Base’.


File: python.info,  Node: How can I organize my code to make it easier to change the base class?,  Next: How do I create static class data and static class methods?,  Prev: How do I call a method defined in a base class from a derived class that extends it?,  Up: 物件

10.2.6.7 How can I organize my code to make it easier to change the base class?
...............................................................................

You could assign the base class to an alias and derive from the alias.
Then all you have to change is the value assigned to the alias.
Incidentally, this trick is also handy if you want to decide dynamically
(e.g.  depending on availability of resources) which base class to use.
Example:

     class Base:
         ...

     BaseAlias = Base

     class Derived(BaseAlias):
         ...


File: python.info,  Node: How do I create static class data and static class methods?,  Next: How can I overload constructors or methods in Python?,  Prev: How can I organize my code to make it easier to change the base class?,  Up: 物件

10.2.6.8 How do I create static class data and static class methods?
....................................................................

Both static data and static methods (in the sense of C++ or Java) are
supported in Python.

For static data, simply define a class attribute.  To assign a new value
to the attribute, you have to explicitly use the class name in the
assignment:

     class C:
         count = 0   # number of times C.__init__ called

         def __init__(self):
             C.count = C.count + 1

         def getcount(self):
             return C.count  # or return self.count

‘c.count’ also refers to ‘C.count’ for any ‘c’ such that ‘isinstance(c,
C)’ holds, unless overridden by ‘c’ itself or by some class on the
base-class search path from ‘c.__class__’ back to ‘C’.

Caution: within a method of C, an assignment like ‘self.count = 42’
creates a new and unrelated instance named "count" in ‘self’'s own dict.
Rebinding of a class-static data name must always specify the class
whether inside a method or not:

     C.count = 314

靜態方法是可能的：

     class C:
         @staticmethod
         def static(arg1, arg2, arg3):
             # 沒有 'self' 參數！
             ...

However, a far more straightforward way to get the effect of a static
method is via a simple module-level function:

     def getcount():
         return C.count

If your code is structured so as to define one class (or tightly related
class hierarchy) per module, this supplies the desired encapsulation.


File: python.info,  Node: How can I overload constructors or methods in Python?,  Next: I try to use __spam and I get an error about _SomeClassName__spam,  Prev: How do I create static class data and static class methods?,  Up: 物件

10.2.6.9 How can I overload constructors (or methods) in Python?
................................................................

This answer actually applies to all methods, but the question usually
comes up first in the context of constructors.

在 C++ 中你會寫成

     class C {
         C() { cout << "No arguments\n"; }
         C(int i) { cout << "Argument is " << i << "\n"; }
     }

In Python you have to write a single constructor that catches all cases
using default arguments.  For example:

     class C:
         def __init__(self, i=None):
             if i is None:
                 print("No arguments")
             else:
                 print("Argument is", i)

This is not entirely equivalent, but close enough in practice.

You could also try a variable-length argument list, e.g.

     def __init__(self, *args):
         ...

The same approach works for all method definitions.


File: python.info,  Node: I try to use __spam and I get an error about _SomeClassName__spam,  Next: My class defines __del__ but it is not called when I delete the object,  Prev: How can I overload constructors or methods in Python?,  Up: 物件

10.2.6.10 I try to use __spam and I get an error about _SomeClassName__spam.
............................................................................

Variable names with double leading underscores are "mangled" to provide
a simple but effective way to define class private variables.  Any
identifier of the form ‘__spam’ (at least two leading underscores, at
most one trailing underscore) is textually replaced with
‘_classname__spam’, where ‘classname’ is the current class name with any
leading underscores stripped.

The identifier can be used unchanged within the class, but to access it
outside the class, the mangled name must be used:

     class A:
         def __one(self):
             return 1
         def two(self):
             return 2 * self.__one()

     class B(A):
         def three(self):
             return 3 * self._A__one()

     four = 4 * A()._A__one()

In particular, this does not guarantee privacy since an outside user can
still deliberately access the private attribute; many Python programmers
never bother to use private variable names at all.

也參考
......

The *note private name mangling specifications: 1bbd. for details and
special cases.


File: python.info,  Node: My class defines __del__ but it is not called when I delete the object,  Next: How do I get a list of all instances of a given class?,  Prev: I try to use __spam and I get an error about _SomeClassName__spam,  Up: 物件

10.2.6.11 My class defines __del__ but it is not called when I delete the object.
.................................................................................

There are several possible reasons for this.

The *note del: 16a9. statement does not necessarily call *note
__del__(): 1e36. - it simply decrements the object's reference count,
and if this reaches zero ‘__del__()’ is called.

If your data structures contain circular links (e.g.  a tree where each
child has a parent reference and each parent has a list of children) the
reference counts will never go back to zero.  Once in a while Python
runs an algorithm to detect such cycles, but the garbage collector might
run some time after the last reference to your data structure vanishes,
so your ‘__del__()’ method may be called at an inconvenient and random
time.  This is inconvenient if you're trying to reproduce a problem.
Worse, the order in which object's ‘__del__()’ methods are executed is
arbitrary.  You can run *note gc.collect(): 16b. to force a collection,
but there 'are' pathological cases where objects will never be
collected.

Despite the cycle collector, it's still a good idea to define an
explicit ‘close()’ method on objects to be called whenever you're done
with them.  The ‘close()’ method can then remove attributes that refer
to subobjects.  Don't call ‘__del__()’ directly - ‘__del__()’ should
call ‘close()’ and ‘close()’ should make sure that it can be called more
than once for the same object.

Another way to avoid cyclical references is to use the *note weakref:
fc. module, which allows you to point to objects without incrementing
their reference count.  Tree data structures, for instance, should use
weak references for their parent and sibling references (if they need
them!).

Finally, if your ‘__del__()’ method raises an exception, a warning
message is printed to *note sys.stderr: 8dd.


File: python.info,  Node: How do I get a list of all instances of a given class?,  Next: Why does the result of id appear to be not unique?,  Prev: My class defines __del__ but it is not called when I delete the object,  Up: 物件

10.2.6.12 How do I get a list of all instances of a given class?
................................................................

Python does not keep track of all instances of a class (or of a built-in
type).  You can program the class's constructor to keep track of all
instances by keeping a list of weak references to each instance.


File: python.info,  Node: Why does the result of id appear to be not unique?,  Next: 我什麼時候可以依靠 is 運算子進行識別性測試？,  Prev: How do I get a list of all instances of a given class?,  Up: 物件

10.2.6.13 Why does the result of ‘id()’ appear to be not unique?
................................................................

The *note id(): 1390. builtin returns an integer that is guaranteed to
be unique during the lifetime of the object.  Since in CPython, this is
the object's memory address, it happens frequently that after an object
is deleted from memory, the next freshly created object is allocated at
the same position in memory.  This is illustrated by this example:

     >>> id(1000)
     13901272
     >>> id(2000)
     13901272

The two ids belong to different integer objects that are created before,
and deleted immediately after execution of the ‘id()’ call.  To be sure
that objects whose id you want to examine are still alive, create
another reference to the object:

     >>> a = 1000; b = 2000
     >>> id(a)
     13901272
     >>> id(b)
     13891296


File: python.info,  Node: 我什麼時候可以依靠 is 運算子進行識別性測試？,  Next: 子類別如何控制不可變實例中存儲的資料？,  Prev: Why does the result of id appear to be not unique?,  Up: 物件

10.2.6.14 我什麼時候可以依靠 'is' 運算子進行識別性測試？
........................................................

‘is’ 運算子測試物件識別性。測試 ‘a is b’ 等同於 ‘id(a) == id(b)’ 。

識別性測試最重要的屬性是物件始終與自身相同， ‘a is a’ 總是回傳 ‘True’ 。
識別性測試通常比相等性測試更快。與相等性測試不同，識別性測試保證回傳布林
值 ‘True’ 或 ‘False’ 。

然而，'只有'當物件識別性得到保證時，識別性測試才能代替相等性測試。一般來
說，保證識別性的情況有以下三種：

1) Assignments create new names but do not change object identity.
After the assignment ‘new = old’, it is guaranteed that ‘new is old’.

2) Putting an object in a container that stores object references does
not change object identity.  After the list assignment ‘s[0] = x’, it is
guaranteed that ‘s[0] is x’.

3) If an object is a singleton, it means that only one instance of that
object can exist.  After the assignments ‘a = None’ and ‘b = None’, it
is guaranteed that ‘a is b’ because ‘None’ is a singleton.

在大多數其他情況下，識別性測試是不可取的，相等性測試是首選。特別是，識別
性測試不應用於檢查常數，例如不能保證是單例的 *note int: 23c. 和 *note
str: 3f2.：

     >>> a = 1000
     >>> b = 500
     >>> c = b + 500
     >>> a is c
     False

     >>> a = 'Python'
     >>> b = 'Py'
     >>> c = b + 'thon'
     >>> a is c
     False

Likewise, new instances of mutable containers are never identical:

     >>> a = []
     >>> b = []
     >>> a is b
     False

在標準函式庫程式碼中，你將看到幾種正確使用識別性測試的常見模式：

1) As recommended by PEP 8(1), an identity test is the preferred way to
check for ‘None’.  This reads like plain English in code and avoids
confusion with other objects that may have boolean values that evaluate
to false.

2) Detecting optional arguments can be tricky when ‘None’ is a valid
input value.  In those situations, you can create a singleton sentinel
object guaranteed to be distinct from other objects.  For example, here
is how to implement a method that behaves like *note dict.pop(): 32d.:

     _sentinel = object()

     def pop(self, key, default=_sentinel):
         if key in self:
             value = self[key]
             del self[key]
             return value
         if default is _sentinel:
             raise KeyError(key)
         return default

3) Container implementations sometimes need to augment equality tests
with identity tests.  This prevents the code from being confused by
objects such as ‘float('NaN')’ that are not equal to themselves.

例如，以下是 ‘collections.abc.Sequence.__contains__()’ 的實作：

     def __contains__(self, value):
         for v in self:
             if v is value or v == value:
                 return True
         return False

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0008/


File: python.info,  Node: 子類別如何控制不可變實例中存儲的資料？,  Next: 如何快取方法呼叫？,  Prev: 我什麼時候可以依靠 is 運算子進行識別性測試？,  Up: 物件

10.2.6.15 子類別如何控制不可變實例中存儲的資料？
................................................

When subclassing an immutable type, override the *note __new__(): 526.
method instead of the *note __init__(): 655. method.  The latter only
runs 'after' an instance is created, which is too late to alter data in
an immutable instance.

All of these immutable classes have a different signature than their
parent class:

     from datetime import date

     class FirstOfMonthDate(date):
         "Always choose the first day of the month"
         def __new__(cls, year, month, day):
             return super().__new__(cls, year, month, 1)

     class NamedInt(int):
         "Allow text names for some numbers"
         xlat = {'zero': 0, 'one': 1, 'ten': 10}
         def __new__(cls, value):
             value = cls.xlat.get(value, value)
             return super().__new__(cls, value)

     class TitleStr(str):
         "Convert str to name suitable for a URL path"
         def __new__(cls, s):
             s = s.lower().replace(' ', '-')
             s = ''.join([c for c in s if c.isalnum() or c == '-'])
             return super().__new__(cls, s)

這些類別可以像這樣使用：

     >>> FirstOfMonthDate(2012, 2, 14)
     FirstOfMonthDate(2012, 2, 1)
     >>> NamedInt('ten')
     10
     >>> NamedInt(20)
     20
     >>> TitleStr('Blog: Why Python Rocks')
     'blog-why-python-rocks'


File: python.info,  Node: 如何快取方法呼叫？,  Prev: 子類別如何控制不可變實例中存儲的資料？,  Up: 物件

10.2.6.16 如何快取方法呼叫？
............................

The two principal tools for caching methods are *note
functools.cached_property(): 4e7. and *note functools.lru_cache(): 993.
The former stores results at the instance level and the latter at the
class level.

The 'cached_property' approach only works with methods that do not take
any arguments.  It does not create a reference to the instance.  The
cached method result will be kept only as long as the instance is alive.

The advantage is that when an instance is no longer used, the cached
method result will be released right away.  The disadvantage is that if
instances accumulate, so too will the accumulated method results.  They
can grow without bound.

'lru_cache' 方法適用於具有*note 可雜湊: 5b5.引數的方法。除非特別努力傳遞
弱參照，否則它會建立對實例的參照。

The advantage of the least recently used algorithm is that the cache is
bounded by the specified 'maxsize'.  The disadvantage is that instances
are kept alive until they age out of the cache or until the cache is
cleared.

這個例子展示了各種技術：

     class Weather:
         "Lookup weather information on a government website"

         def __init__(self, station_id):
             self._station_id = station_id
             # The _station_id is private and immutable

         def current_temperature(self):
             "Latest hourly observation"
             # Do not cache this because old results
             # can be out of date.

         @cached_property
         def location(self):
             "Return the longitude/latitude coordinates of the station"
             # Result only depends on the station_id

         @lru_cache(maxsize=20)
         def historic_rainfall(self, date, units='mm'):
             "Rainfall on a given date"
             # Depends on the station_id, date, and units.

The above example assumes that the 'station_id' never changes.  If the
relevant instance attributes are mutable, the 'cached_property' approach
can't be made to work because it cannot detect changes to the
attributes.

To make the 'lru_cache' approach work when the 'station_id' is mutable,
the class needs to define the *note __eq__(): a9d. and *note __hash__():
a9e. methods so that the cache can detect relevant attribute updates:

     class Weather:
         "Example with a mutable station identifier"

         def __init__(self, station_id):
             self.station_id = station_id

         def change_station(self, station_id):
             self.station_id = station_id

         def __eq__(self, other):
             return self.station_id == other.station_id

         def __hash__(self):
             return hash(self.station_id)

         @lru_cache(maxsize=20)
         def historic_rainfall(self, date, units='cm'):
             'Rainfall on a given date'
             # Depends on the station_id, date, and units.


File: python.info,  Node: 模組<5>,  Prev: 物件,  Up: 程式開發常見問答集

10.2.7 模組
-----------

* Menu:

* 如何建立 .pyc 檔案？: 如何建立 pyc 檔案？.
* 如何找到當前模組名稱？::
* How can I have modules that mutually import each other?::
* __import__('x.y.z') 回傳 <module 'x'>，那我怎麼得到 z？: __import__ 'x y z' 回傳 <module 'x'>，那我怎麼得到 z？.
* 當我編輯需要引入的模組並重新引入它時，更動沒有反應出來。為什麼會這樣？::


File: python.info,  Node: 如何建立 pyc 檔案？,  Next: 如何找到當前模組名稱？,  Up: 模組<5>

10.2.7.1 如何建立 .pyc 檔案？
.............................

When a module is imported for the first time (or when the source file
has changed since the current compiled file was created) a ‘.pyc’ file
containing the compiled code should be created in a ‘__pycache__’
subdirectory of the directory containing the ‘.py’ file.  The ‘.pyc’
file will have a filename that starts with the same name as the ‘.py’
file, and ends with ‘.pyc’, with a middle component that depends on the
particular ‘python’ binary that created it.  (See PEP 3147(1) for
details.)

One reason that a ‘.pyc’ file may not be created is a permissions
problem with the directory containing the source file, meaning that the
‘__pycache__’ subdirectory cannot be created.  This can happen, for
example, if you develop as one user but run as another, such as if you
are testing with a web server.

Unless the *note PYTHONDONTWRITEBYTECODE: 133c. environment variable is
set, creation of a .pyc file is automatic if you're importing a module
and Python has the ability (permissions, free space, etc...)  to create
a ‘__pycache__’ subdirectory and write the compiled module to that
subdirectory.

Running Python on a top level script is not considered an import and no
‘.pyc’ will be created.  For example, if you have a top-level module
‘foo.py’ that imports another module ‘xyz.py’, when you run ‘foo’ (by
typing ‘python foo.py’ as a shell command), a ‘.pyc’ will be created for
‘xyz’ because ‘xyz’ is imported, but no ‘.pyc’ file will be created for
‘foo’ since ‘foo.py’ isn't being imported.

If you need to create a ‘.pyc’ file for ‘foo’ - that is, to create a
‘.pyc’ file for a module that is not imported - you can, using the *note
py_compile: a1. and *note compileall: 19. modules.

The *note py_compile: a1. module can manually compile any module.  One
way is to use the ‘compile()’ function in that module interactively:

     >>> import py_compile
     >>> py_compile.compile('foo.py')

This will write the ‘.pyc’ to a ‘__pycache__’ subdirectory in the same
location as ‘foo.py’ (or you can override that with the optional
parameter ‘cfile’).

You can also automatically compile all files in a directory or
directories using the *note compileall: 19. module.  You can do it from
the shell prompt by running ‘compileall.py’ and providing the path of a
directory containing Python files to compile:

     python -m compileall .

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-3147/


File: python.info,  Node: 如何找到當前模組名稱？,  Next: How can I have modules that mutually import each other?,  Prev: 如何建立 pyc 檔案？,  Up: 模組<5>

10.2.7.2 如何找到當前模組名稱？
...............................

A module can find out its own module name by looking at the predefined
global variable ‘__name__’.  If this has the value ‘'__main__'’, the
program is running as a script.  Many modules that are usually used by
importing them also provide a command-line interface or a self-test, and
only execute this code after checking ‘__name__’:

     def main():
         print('Running test...')
         ...

     if __name__ == '__main__':
         main()


File: python.info,  Node: How can I have modules that mutually import each other?,  Next: __import__ 'x y z' 回傳 <module 'x'>，那我怎麼得到 z？,  Prev: 如何找到當前模組名稱？,  Up: 模組<5>

10.2.7.3 How can I have modules that mutually import each other?
................................................................

假設你有以下模組：

‘foo.py’：

     from bar import bar_var
     foo_var = 1

‘bar.py’：

     from foo import foo_var
     bar_var = 2

The problem is that the interpreter will perform the following steps:

   * main imports ‘foo’

   * Empty globals for ‘foo’ are created

   * ‘foo’ 被編譯並開始執行

   * ‘foo’ 引入 ‘bar’

   * Empty globals for ‘bar’ are created

   * ‘bar’ 已被編譯並開始執行

   * ‘bar’ imports ‘foo’ (which is a no-op since there already is a
     module named ‘foo’)

   * The import mechanism tries to read ‘foo_var’ from ‘foo’ globals, to
     set ‘bar.foo_var = foo.foo_var’

The last step fails, because Python isn't done with interpreting ‘foo’
yet and the global symbol dictionary for ‘foo’ is still empty.

The same thing happens when you use ‘import foo’, and then try to access
‘foo.foo_var’ in global code.

此問題有（至少）三種可能的解決方法。

Guido van Rossum recommends avoiding all uses of ‘from <module> import
...’, and placing all code inside functions.  Initializations of global
variables and class variables should use constants or built-in functions
only.  This means everything from an imported module is referenced as
‘<module>.<name>’.

Jim Roskind 建議在每個模組中按以下順序執行各個步驟：

   * exports (globals, functions, and classes that don't need imported
     base classes)

   * ‘import’ 陳述式

   * 活躍程式碼（包括從引入值初始化的全域變數）。

Van Rossum doesn't like this approach much because the imports appear in
a strange place, but it does work.

Matthias Urlichs 建議重構你的程式碼，以便打從一開始就不需要遞迴引入。

這些方案並不衝突。


File: python.info,  Node: __import__ 'x y z' 回傳 <module 'x'>，那我怎麼得到 z？,  Next: 當我編輯需要引入的模組並重新引入它時，更動沒有反應出來。為什麼會這樣？,  Prev: How can I have modules that mutually import each other?,  Up: 模組<5>

10.2.7.4 __import__('x.y.z') 回傳 <module 'x'>，那我怎麼得到 z？
................................................................

Consider using the convenience function *note import_module(): 4bc. from
*note importlib: 6b. instead:

     z = importlib.import_module('x.y.z')


File: python.info,  Node: 當我編輯需要引入的模組並重新引入它時，更動沒有反應出來。為什麼會這樣？,  Prev: __import__ 'x y z' 回傳 <module 'x'>，那我怎麼得到 z？,  Up: 模組<5>

10.2.7.5 當我編輯需要引入的模組並重新引入它時，更動沒有反應出來。為什麼會這樣？
...............................................................................

For reasons of efficiency as well as consistency, Python only reads the
module file on the first time a module is imported.  If it didn't, in a
program consisting of many modules where each one imports the same basic
module, the basic module would be parsed and re-parsed many times.  To
force re-reading of a changed module, do this:

     import importlib
     import modname
     importlib.reload(modname)

Warning: this technique is not 100% fool-proof.  In particular, modules
containing statements like

     from modname import some_objects

will continue to work with the old version of the imported objects.  If
the module contains class definitions, existing class instances will
'not' be updated to use the new class definition.  This can result in
the following paradoxical behaviour:

     >>> import importlib
     >>> import cls
     >>> c = cls.C()                # Create an instance of C
     >>> importlib.reload(cls)
     <module 'cls' from 'cls.py'>
     >>> isinstance(c, cls.C)       # isinstance is false?!?
     False

如果印出類別物件的「識別性」，問題的本質就很清楚了：

     >>> hex(id(c.__class__))
     '0x7352a0'
     >>> hex(id(cls.C))
     '0x4198d0'


File: python.info,  Node: 設計和歷史常見問答集,  Next: 函式庫和擴充功能的常見問題,  Prev: 程式開發常見問答集,  Up: Python 常見問題

10.3 設計和歷史常見問答集
=========================

* Menu:

* 為什麼 Python 使用縮排將陳述式進行分組？::
* 為什麼我會從簡單的數學運算得到奇怪的結果？::
* 為何浮點數運算如此不精確？::
* 為什麼 Python 字串不可變動？::
* 為何「self」在方法 (method) 定義和呼叫時一定要明確使用？: 為何「self」在方法 method 定義和呼叫時一定要明確使用？.
* 為何我不能在運算式 (expression) 中使用指派運算？: 為何我不能在運算式 expression 中使用指派運算？.
* 為何 Python 對於一些功能實作使用方法（像是 list.index()），另一些使用函式（像是 len(list)）？: 為何 Python 對於一些功能實作使用方法（像是 list index ），另一些使用函式（像是 len list ）？.
* 為何 join() 是字串方法而非串列 (list) 或元組 (tuple) 方法？: 為何 join 是字串方法而非串列 list 或元組 tuple 方法？.
* 例外處理有多快？::
* 為什麼 Python 內沒有 switch 或 case 陳述式？::
* 為何不能在直譯器上模擬執行緒，而要使用作業系統的特定實作方式？::
* 為何 lambda 運算式不能包含陳述式？::
* Python 可以被編譯成機器語言、C 語言或其他種語言嗎？::
* Python 如何管理記憶體？::
* 為何 CPython 不使用更多傳統的垃圾回收機制？::
* 當 CPython 結束時，為何所有的記憶體不會被釋放？::
* 為何要把元組 (tuple) 和串列 (list) 分成兩個資料型態？: 為何要把元組 tuple 和串列 list 分成兩個資料型態？.
* 串列 (list) 在 CPython 中是怎麼實作的？: 串列 list 在 CPython 中是怎麼實作的？.
* 字典 (dictionaries) 在 CPython 中是怎麼實作的？: 字典 dictionaries 在 CPython 中是怎麼實作的？.
* 為何字典的鍵一定是不可變的？::
* 為何 list.sort() 不是回傳排序過的串列？: 為何 list sort 不是回傳排序過的串列？.
* 如何在 Python 中指定和強制使用一個介面規範 (interface spec)？: 如何在 Python 中指定和強制使用一個介面規範 interface spec ？.
* 為何沒有 goto 語法？::
* 為何純字串 (r-string) 不能以反斜線結尾？: 為何純字串 r-string 不能以反斜線結尾？.
* 為何 Python 沒有屬性賦值的 with 陳述式？::
* 為何產生器 (generator) 不支援 with 陳述式？: 為何產生器 generator 不支援 with 陳述式？.
* 為何 if、while、def、class 陳述式裡需要冒號？::
* 為何 Python 允許在串列和元組末端加上逗號？::


File: python.info,  Node: 為什麼 Python 使用縮排將陳述式進行分組？,  Next: 為什麼我會從簡單的數學運算得到奇怪的結果？,  Up: 設計和歷史常見問答集

10.3.1 為什麼 Python 使用縮排將陳述式進行分組？
-----------------------------------------------

Guido van Rossum 相信使用縮排來分組超級優雅，並且對提高一般 Python 程式
的清晰度有許多貢獻。許多人在學習一段時間之後就愛上了這個功能。

因為沒有開始/結束括號，因此剖析器和人類讀者感知到的分組就不存在分歧。偶
爾 C 語言的程式設計師會遇到這樣的程式碼片段：

     if (x <= y)
             x++;
             y--;
     z++;

如果條件為真，只有 ‘x++’ 陳述式會被執行，但縮排會讓很多人對他有不同的理
解。即使是資深的 C 語言開發者有時也會盯著他許久，思考為何即便 ‘x > y’，
但 ‘y’ 還是減少了。

因為沒有開頭與結尾的括號，Python 比起其他語言會更不容易遇到程式碼風格的
衝突。在 C 語言中，有多種不同的方法來放置花括號。在習慣讀寫特定風格後，
去讀（或是必須去寫）另一種風格會覺得不太舒服。

很多程式碼風格會把 begin/end 獨立放在一行。這會讓程式碼很長且浪費珍貴的
螢幕空間，要概覽程式時也變得較為困難。理想上來說，一個函式應該要佔一個螢
幕（大概 20 至 30 行）。20 行的 Python 程式碼比起 20 行的 C 程式碼可以做
更多事。雖然沒有開頭與結尾的括號並非單一原因（沒有變數宣告及高階的資料型
別同樣有關），但縮排式的語法確實給了幫助。


File: python.info,  Node: 為什麼我會從簡單的數學運算得到奇怪的結果？,  Next: 為何浮點數運算如此不精確？,  Prev: 為什麼 Python 使用縮排將陳述式進行分組？,  Up: 設計和歷史常見問答集

10.3.2 為什麼我會從簡單的數學運算得到奇怪的結果？
-------------------------------------------------

請見下一個問題。


File: python.info,  Node: 為何浮點數運算如此不精確？,  Next: 為什麼 Python 字串不可變動？,  Prev: 為什麼我會從簡單的數學運算得到奇怪的結果？,  Up: 設計和歷史常見問答集

10.3.3 為何浮點數運算如此不精確？
---------------------------------

使用者時常對這樣的結果感到驚訝：

     >>> 1.2 - 1.0
     0.19999999999999996

然後認為這是 Python 的 bug，但這並不是。這跟 Python 幾乎沒有關係，而是和
底層如何處理浮點數有關係。

CPython 的 *note float: 2c8. 型別使用了 C 的 ‘double’ 型別來儲存。一個
*note float: 2c8. 物件的值會以固定的精度（通常為 53 位元）存為二進制浮點
數，Python 使用 C 來運算浮點數，而他的結果會依處理器中的硬體實作方式來決
定。這表示就浮點數運算來說，Python 和 C、Java 等很多受歡迎的語言有一樣的
行為。

很多數字可以簡單地寫成十進位表示，但卻無法簡單地以二進制浮點數表示。比方
說，在以下程式碼執行後：

     >>> x = 1.2

‘x’ 裡的值是一個（很接近）1.2 的估計值，但並非精確地等於 1.2。以一般的電
腦來說，他實際儲存的值是：

     1.0011001100110011001100110011001100110011001100110011 (binary)

而這個值正是：

     1.1999999999999999555910790149937383830547332763671875 (decimal)

53 位元的精度讓 Python 可以有 15 至 16 小數位的準確度。

要更完全的解釋可以查閱在 Python 教學的*note 浮點運算: 1c13.一章。


File: python.info,  Node: 為什麼 Python 字串不可變動？,  Next: 為何「self」在方法 method 定義和呼叫時一定要明確使用？,  Prev: 為何浮點數運算如此不精確？,  Up: 設計和歷史常見問答集

10.3.4 為什麼 Python 字串不可變動？
-----------------------------------

有許多優點。

其一是效能：知道字串不可變動後，我們就可以在創造他的時候就分配好空間，而
後他的儲存空間需求就是固定不變的。這也是元組 (tuple) 和串列 (list) 相異
的其中一個原因。

另一個優點是在 Python 中，字串和數字一樣「基本」。沒有任何行為會把 8 這
個數值改成其他數值；同理，在 Python 中也沒有任何行為會修改字串「eight」
。


File: python.info,  Node: 為何「self」在方法 method 定義和呼叫時一定要明確使用？,  Next: 為何我不能在運算式 expression 中使用指派運算？,  Prev: 為什麼 Python 字串不可變動？,  Up: 設計和歷史常見問答集

10.3.5 為何「self」在方法 (method) 定義和呼叫時一定要明確使用？
---------------------------------------------------------------

此構想從 Modula-3 而來。因為許多原因，他可以說是非常實用。

第一，這樣可以更明顯表現出你在用方法 (method) 或是實例 (instance) 的屬性
，而非一個區域變數。即使不知道類別 (class) 的定義，當看到 ‘self.x’ 或
‘self.meth()’，就會很清楚地知道是正在使用實例的變數或是方法。在 C++ 裡，
你可以藉由沒有區域變數宣告來判斷這件事 ── 但在 Python 裡沒有區域變數宣告
，所以你必須去看類別的定義來確定。有些 C++ 和 Java 的程式碼規格要求要在
實例屬性的名稱加上前綴 ‘m_’，所以這種明確性在那些語言也是很好用的。

第二，當你想明確地使用或呼叫在某個類別裡的方法的時候，你不需要特殊的語法
。在 C++ 裡，如果你想用一個在繼承類別時被覆寫的基底類別方法，必須要用
‘::’ 運算子 - 但在 Python 裡，你可以直接寫成 ‘baseclass.methodname(self,
<argument list>)’。這在 *note __init__(): 655. 方法很好用，特別是在一個
繼承的類別要擴充基底類別的方法而要呼叫他時。

最後，他解決了關於實例變數指派的語法問題：因為區域變數在 Python 是（定義
為）在函式內被指派值的變數（且沒有被明確宣告成全域），所以會需要一個方法
來告訴直譯器這個指派運算是針對實例變數，而非針對區域變數，這在語法層面處
理較好（為了效率）。C++ 用宣告解決了這件事，但 Python 沒有，而為了這個原
因而引入變數宣告機制又略嫌浪費。但使用明確的 ‘self.var’ 就可以把這個問題
圓滿解決。同理，在用實例變數的時候必須寫成 ‘self.var’ 即代表對於在方法中
不特定的名稱不需要去看實例的內容。換句話說，區域變數和實例變數存在於兩個
不同的命名空間 (namespace)，而你需要告訴 Python 要使用哪一個。


File: python.info,  Node: 為何我不能在運算式 expression 中使用指派運算？,  Next: 為何 Python 對於一些功能實作使用方法（像是 list index ），另一些使用函式（像是 len list ）？,  Prev: 為何「self」在方法 method 定義和呼叫時一定要明確使用？,  Up: 設計和歷史常見問答集

10.3.6 為何我不能在運算式 (expression) 中使用指派運算？
-------------------------------------------------------

從 Python 3.8 開始，你可以這麼做了！

指派運算式使用海象運算子 ‘:=’ 來在運算式中指派變數值：

     while chunk := fp.read(200):
        print(chunk)

更多資訊請見 PEP 572(1)。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0572/


File: python.info,  Node: 為何 Python 對於一些功能實作使用方法（像是 list index ），另一些使用函式（像是 len list ）？,  Next: 為何 join 是字串方法而非串列 list 或元組 tuple 方法？,  Prev: 為何我不能在運算式 expression 中使用指派運算？,  Up: 設計和歷史常見問答集

10.3.7 為何 Python 對於一些功能實作使用方法（像是 list.index()），另一些使用函式（像是 len(list)）？
----------------------------------------------------------------------------------------------------

如 Guido 所說：

     （一） 對一些運算來說，前綴寫法看起來會比後綴寫法好 ── 前綴（和中綴
     ！）運算在數學上有更久遠的傳統，這些符號在視覺上幫助數學家們更容易
     思考問題。想想把 x*(a+b) 這種式子展開成 x*a + x*b 的簡單，再比較一
     下古老的圈圈符號記法的笨拙就知道了。

     （二） 當我看到一段程式碼寫著 len(x)，我'知道'他要找某個東西的長度
     。這告訴了我兩件事：結果是一個整數、參數是某種容器。相對地，當我看
     到 x.len()，我必須先知道 x 是某種容器，並實作了一個介面或是繼承了一
     個有標準 len() 的類別。遇到一個沒有實作映射 (mapping) 的類別卻有
     get() 或 keys() 方法，或是不是檔案但卻有 write() 方法時，我們偶爾會
     覺得困惑。

-- ‘https://mail.python.org/pipermail/python-3000/2006-November/004643.html’


File: python.info,  Node: 為何 join 是字串方法而非串列 list 或元組 tuple 方法？,  Next: 例外處理有多快？,  Prev: 為何 Python 對於一些功能實作使用方法（像是 list index ），另一些使用函式（像是 len list ）？,  Up: 設計和歷史常見問答集

10.3.8 為何 join() 是字串方法而非串列 (list) 或元組 (tuple) 方法？
------------------------------------------------------------------

自 Python 1.6 之後，字串變得很像其他標準的型別，也在此時，一些可以和字串
模組的函式有相同功能的方法也被加入。大多數的新方法都被廣泛接受，但有一個
方法似乎讓一些程式人員不舒服：

     ", ".join(['1', '2', '4', '8', '16'])

結果是：

     "1, 2, 4, 8, 16"

通常有兩個反對這個用法的論點。

第一項這麼說：「用字串文本 (string literal) （字串常數）看起來真的很醜」
，也許真的如此，但字串文本就只是一個固定值。如果方法可以用在值為字串的變
數上，那沒道理字串文本不能被使用。

第二個反對意見通常是：「我是在叫一個序列把它的成員用一個字串常數連接起來
」。但很遺憾地，你並不是在這樣做。因為某種原因，把 *note split(): e4c. 當
成字串方法比較簡單，因為這樣我們可以輕易地看到：

     "1, 2, 4, 8, 16".split(", ")

這是在叫一個字串文本回傳由指定的分隔符號（或是預設為空白）分出的子字串的
指令。

*note join(): 2088. 是一個字串方法，因為在用他的時候，你是告訴分隔字串去
走遍整個字串序列，並將自己插入到相鄰的兩項之間。這個方法的參數可以是任何
符合序列規則的物件，包括自定義的新類別。在 bytes 和 bytearray 物件也有類
似的方法可用。


File: python.info,  Node: 例外處理有多快？,  Next: 為什麼 Python 內沒有 switch 或 case 陳述式？,  Prev: 為何 join 是字串方法而非串列 list 或元組 tuple 方法？,  Up: 設計和歷史常見問答集

10.3.9 例外處理有多快？
-----------------------

如果沒有例外被丟出，一個 *note try: 68c./*note except: 171. 區塊是非常有
效率的。事實上，抓捕例外要付出昂貴的代價。在 Python 2.0 以前，這樣使用是
相當常見的：

     try:
         value = mydict[key]
     except KeyError:
         mydict[key] = getvalue(key)
         value = mydict[key]

這只有在你預料這個字典大多數時候都有鍵的時候才合理。如果並非如此，你應該
寫成：

     if key in mydict:
         value = mydict[key]
     else:
         value = mydict[key] = getvalue(key)

單就這個情況來說，你也可以用 ‘value = dict.setdefault(key,
getvalue(key))’，不過只有在 ‘getvalue()’ 代價不大的時候才能用，畢竟他每
次都會被執行。


File: python.info,  Node: 為什麼 Python 內沒有 switch 或 case 陳述式？,  Next: 為何不能在直譯器上模擬執行緒，而要使用作業系統的特定實作方式？,  Prev: 例外處理有多快？,  Up: 設計和歷史常見問答集

10.3.10 為什麼 Python 內沒有 switch 或 case 陳述式？
----------------------------------------------------

In general, structured switch statements execute one block of code when
an expression has a particular value or set of values.  Since Python
3.10 one can easily match literal values, or constants within a
namespace, with a ‘match ... case’ statement.  An older alternative is a
sequence of ‘if... elif... elif... else’.

如果可能性很多，你可以用字典去映射要呼叫的函式。舉例來說：

     if key in mydict:
         value = mydict[key]
     else:
         value = mydict[key] = getvalue(key)

對於呼叫物件裡的方法，你可以利用內建用來找尋特定方法的函式 *note
getattr(): b78. 來做進一步的簡化：

     class MyVisitor:
         def visit_a(self):
             ...

         def dispatch(self, value):
             method_name = 'visit_' + str(value)
             method = getattr(self, method_name)
             method()

我們建議在方法名稱加上前綴，以這個例子來說是 像是 ‘visit_’。沒有前綴的話
，一旦收到從不信任來源的值，攻擊者便可以隨意呼叫在你的專案內的方法。

Imitating switch with fallthrough, as with C's switch-case-default, is
possible, much harder, and less needed.


File: python.info,  Node: 為何不能在直譯器上模擬執行緒，而要使用作業系統的特定實作方式？,  Next: 為何 lambda 運算式不能包含陳述式？,  Prev: 為什麼 Python 內沒有 switch 或 case 陳述式？,  Up: 設計和歷史常見問答集

10.3.11 為何不能在直譯器上模擬執行緒，而要使用作業系統的特定實作方式？
----------------------------------------------------------------------

答案一：很不幸地，直譯器對每個 Python 的堆疊框 (stack frame) 會推至少一
個 C 的堆疊框。同時，擴充套件可以隨時呼叫 Python，因此完整的實作必須要支
援 C 的執行緒。

答案二：幸運地，無堆疊 (Stackless) Python(1) 完全重新設計了直譯器迴圈，
並避免了 C 堆疊。

   ---------- Footnotes ----------

   (1) https://github.com/stackless-dev/stackless/wiki


File: python.info,  Node: 為何 lambda 運算式不能包含陳述式？,  Next: Python 可以被編譯成機器語言、C 語言或其他種語言嗎？,  Prev: 為何不能在直譯器上模擬執行緒，而要使用作業系統的特定實作方式？,  Up: 設計和歷史常見問答集

10.3.12 為何 lambda 運算式不能包含陳述式？
------------------------------------------

Python 的 lambda 運算式不能包含陳述式是因為 Python 的語法框架無法處理包
在運算式中的陳述式。然而，在 Python 裡這並不是一個嚴重的問題。不像在其他
語言中有獨立功能的 lambda，Python 的 lambda 只是一個在你懶得定義函式時可
用的一個簡寫表達法。

函式已經是 Python 裡的一級物件 (first class objects)，而且可以在區域範圍
內被宣告。因此唯一用 lambda 而非區域性的函式的優點就是你不需要多想一個函
式名稱 — 但這樣就會是一個區域變數被指定成函式物件（和 lambda 運算式的結
果同類）！


File: python.info,  Node: Python 可以被編譯成機器語言、C 語言或其他種語言嗎？,  Next: Python 如何管理記憶體？,  Prev: 為何 lambda 運算式不能包含陳述式？,  Up: 設計和歷史常見問答集

10.3.13 Python 可以被編譯成機器語言、C 語言或其他種語言嗎？
-----------------------------------------------------------

Cython(1) 可以編譯一個調整過有選擇性註解的 Python 版本。 Nuitka(2) 是一
個有潛力編譯器，可以把 Python 編譯成 C++，他的目標是支援完整的 Python 語
言。

   ---------- Footnotes ----------

   (1) https://cython.org/

   (2) https://www.nuitka.net/


File: python.info,  Node: Python 如何管理記憶體？,  Next: 為何 CPython 不使用更多傳統的垃圾回收機制？,  Prev: Python 可以被編譯成機器語言、C 語言或其他種語言嗎？,  Up: 設計和歷史常見問答集

10.3.14 Python 如何管理記憶體？
-------------------------------

Python 記憶體管理的細節取決於實作。Python 的標準實作 *note CPython: 699.
使用參照計次 (reference counting) 來偵測不再被存取的物件，並用另一個機制
來收集參照循環 (reference cycle)、定期執行循環偵測演算法來找不再使用的循
環並刪除相關物件。 *note gc: 56. 模組提供了可以執行垃圾收集、抓取除錯統
計數據和調整收集器參數的函式。

然而，在其他實作（像是 Jython(1) 或 PyPy(2)）中，會使用像是成熟的垃圾收
集器等不同機制。如果你的 Python 程式碼的表現取決於參照計次的實作，這個相
異處會導致一些微小的移植問題。

在一些 Python 實作中，下面這段程式碼（在 CPython 可以正常運作）可能會把
檔案描述子 (file descriptor) 用盡：

     for file in very_long_list_of_files:
         f = open(file)
         c = f.read(1)

實際上，使用 CPython 的參照計次和解構方案 (destructor scheme)，每個對
‘f’ 的新指派都會關閉前面打開的檔案。然而用傳統的垃圾回收 (GC) 的話，這些
檔案物件只會在不固定且有可能很長的時間後被收集（並關閉）。

如果你希望你的程式碼在任何 Python 實作版本中都可以運作，那你應該清楚地關
閉檔案或是使用 *note with: 577. 陳述式，如此一來，不用管記憶體管理的方法
，他也會正常運作：

     for file in very_long_list_of_files:
         with open(file) as f:
             c = f.read(1)

   ---------- Footnotes ----------

   (1) https://www.jython.org

   (2) https://www.pypy.org


File: python.info,  Node: 為何 CPython 不使用更多傳統的垃圾回收機制？,  Next: 當 CPython 結束時，為何所有的記憶體不會被釋放？,  Prev: Python 如何管理記憶體？,  Up: 設計和歷史常見問答集

10.3.15 為何 CPython 不使用更多傳統的垃圾回收機制？
---------------------------------------------------

第一，這並不是 C 的標準功能，因此他的可攜性低。（對，我們知道 Boehm GC 函
式庫。他有可相容於'大多數'平台的組合語言程式碼，但依然不是全部，而即便它
大多數是通透的，也並不完全，要讓它跟 Python 相容還是需要做一些修補。）

傳統的垃圾收集 (GC) 在 Python 被嵌入其他應用程式時也成了一個問題。在獨立
的 Python 程式裡當然可以把標準的 ‘malloc()’ 和 ‘free()’ 換成 GC 函式庫提
供的其他版本；但一個嵌著 Python 的應用程式可能想用'自己'的 malloc() 和
free() 替代品，而不是用 Python 的。以現在來說，CPython 和實作 malloc() 和
free() 的程式相處融洽。


File: python.info,  Node: 當 CPython 結束時，為何所有的記憶體不會被釋放？,  Next: 為何要把元組 tuple 和串列 list 分成兩個資料型態？,  Prev: 為何 CPython 不使用更多傳統的垃圾回收機制？,  Up: 設計和歷史常見問答集

10.3.16 當 CPython 結束時，為何所有的記憶體不會被釋放？
-------------------------------------------------------

當離開 Python 時，從 Python 模組的全域命名空間來的物件並非總是會被釋放。
在有循環引用的時候，這可能會發生。有些記憶體是被 C 函式庫取用的，他們不
可能被釋放（例如：像是 Purify 之類的工具會抱怨）。然而，Python 在關閉的
時候會積極清理記憶體並嘗試刪除每個物件。

如果你想要強迫 Python 在釋放記憶體時刪除特定的東西，你可以用 *note
atexit: 9. 模組來執行會強制刪除的函式。


File: python.info,  Node: 為何要把元組 tuple 和串列 list 分成兩個資料型態？,  Next: 串列 list 在 CPython 中是怎麼實作的？,  Prev: 當 CPython 結束時，為何所有的記憶體不會被釋放？,  Up: 設計和歷史常見問答集

10.3.17 為何要把元組 (tuple) 和串列 (list) 分成兩個資料型態？
-------------------------------------------------------------

串列和元組在很多方面相當相似，但通常用在完全不同的地方。元組可以想成
Pascal 的 ‘record’ 或是 C 的 ‘struct’，是一小群相關聯但可能是不同型別的
資料集合，以一組為單位進行操作。舉例來說，一個笛卡兒坐標系可以適當地表示
成一個有二或三個值的元組。

另一方面，串列更像是其他語言的陣列 (array)。他可以有不固定個同類別物件，
且為逐項操作。舉例來說，*note os.listdir('.'): 1092. 回傳當下目錄裡的檔
案，以包含字串的串列表示。如果你新增了幾個檔案到這個目錄，一般來說操作結
果的函式也會正常運作。

元組則是不可變的，代表一旦元組被建立，你就不能夠改變裡面的任何一個值。而
串列可變，所以你可以改變裡面的元素。只有不可變的元素可以成為字典的鍵，所
以只能把元組當成鍵，而串列則不行。


File: python.info,  Node: 串列 list 在 CPython 中是怎麼實作的？,  Next: 字典 dictionaries 在 CPython 中是怎麼實作的？,  Prev: 為何要把元組 tuple 和串列 list 分成兩個資料型態？,  Up: 設計和歷史常見問答集

10.3.18 串列 (list) 在 CPython 中是怎麼實作的？
-----------------------------------------------

CPython 的串列 (list) 事實上是可變長度的陣列 (array)，而不是像 Lisp 語言
的鏈接串列 (linked list)。實作上，他是一個連續的物件參照 (reference) 陣
列，並把指向此陣列的指標 (pointer) 和陣列長度存在串列的標頭結構內。

因此，用索引來找串列特定項 ‘a[i]’ 的代價和串列大小或是索引值無關。

當新物件被新增或插入時，陣列會被調整大小。為了改善多次加入物件的效率，我
們有用一些巧妙的方法，當陣列必須變大時，會多收集一些額外的空間，接下來幾
次新增時就不需要再調整大小了。


File: python.info,  Node: 字典 dictionaries 在 CPython 中是怎麼實作的？,  Next: 為何字典的鍵一定是不可變的？,  Prev: 串列 list 在 CPython 中是怎麼實作的？,  Up: 設計和歷史常見問答集

10.3.19 字典 (dictionaries) 在 CPython 中是怎麼實作的？
-------------------------------------------------------

CPython 的字典是用可調整大小的雜湊表 (hash table) 實作的。比起 B 樹
(B-tree)，在搜尋（目前為止最常見的操作）方面有更好的表現，實作上也較為簡
單。

字典利用內建 *note hash(): 58f. 函式，對每個鍵做雜湊計算。雜湊結果依據鍵
的值和個別執行緒 (processes) 的種子而有相當大的差距。例如，‘'Python'’ 的
雜湊是 ‘-539294296’，而只差一個字的 ‘'python'’ 則是 ‘1142331976’。雜湊結
果接著被用來計算值在內部陣列儲存的位置。假設你存的鍵都有不同的雜湊值，那
字典只需要常數時間 — 用大 O 表示法 (Big-O notation) 就是 'O'(1) — 來找任
意一個鍵。


File: python.info,  Node: 為何字典的鍵一定是不可變的？,  Next: 為何 list sort 不是回傳排序過的串列？,  Prev: 字典 dictionaries 在 CPython 中是怎麼實作的？,  Up: 設計和歷史常見問答集

10.3.20 為何字典的鍵一定是不可變的？
------------------------------------

實作字典用的雜湊表是根據鍵的值做計算從而找到鍵的。如果鍵可變的話，他的值
就可以改變，則雜湊的結果也會一起變動。但改變鍵的物件的人無從得知他被用來
當成字典的鍵，所以無法修改字典的內容。然後，當你嘗試在字典中尋找這個物件
時，因為雜湊值不同的緣故，你找不到他。而如果你嘗試用舊的值去尋找，也一樣
找不到，因為他的雜湊結果和原先物件不同。

如果你想要用串列作為字典的索引，把他轉換成元組即可。‘tuple(L)’ 函式會建
立一個和串列 ‘L’ 一樣內容的元組。而元組是不可變的，所以可以用來當成字典
的鍵。

也有人提出一些不能接受的方法：

   - 用串列的記憶體位址（物件 id）來雜湊。這不會成功，因為你如果用同樣的
     值建立一個新的串列，是找不到的。舉例來說：

          mydict = {[1, 2]: '12'}
          print(mydict[[1, 2]])

     這將會導致 *note KeyError: 2fb. 例外，因為 ‘[1, 2]’ 的 id 在第一行
     和第二行是不同的。換句話說，字典的鍵應該要用 ‘==’ 來做比較，而不是
     用 *note is: 2c6.。

   - 複製一個串列作為鍵。這一樣不會成功，因為串列是可變的，他可以包含自
     己的參照，所以複製會形成一個無窮迴圈。

   - 允許串列作為鍵，但告訴使用者不要更動他。當你不小心忘記或是更動了這
     個串列，會產生一種難以追蹤的 bug。他同時也違背了一項字典的重要定則
     ：在 ‘d.keys()’ 的每個值都可以當成字典的鍵。

   - 一旦串列被當成鍵，把他標記成只能讀取。問題是，這不只要避免最上層的
     物件改變值，就像用元組包含串列來做為鍵。把一個物件當成鍵，需要將從
     他開始可以接觸到的所有物件都標記成只能讀取 — 所以再一次，自己參照自
     己的物件會導致無窮迴圈。

如果你需要的話，這裡有個小技巧可以幫你，但請自己承擔風險：你可以把一個可
變物件包裝進一個有 *note __eq__(): a9d. 和 *note __hash__(): a9e. 方法的
類別實例。只要這種包裝物件還存在於字典（或其他類似結構）中，你就必須確定
在字典（或其他用雜湊為基底的結構）中他們的雜湊值會保持恆定。

     class ListWrapper:
         def __init__(self, the_list):
             self.the_list = the_list

         def __eq__(self, other):
             return self.the_list == other.the_list

         def __hash__(self):
             l = self.the_list
             result = 98767 - len(l)*555
             for i, el in enumerate(l):
                 try:
                     result = result + (hash(el) % 9999999) * 1001 + i
                 except Exception:
                     result = (result % 7777777) + i * 333
             return result

請注意，雜湊的計算可能變得複雜，因為有串列成員不可雜湊 (unhashable) 和算
術溢位的可能性。

此外，不管物件是否在字典中，如果 ‘o1 == o2’（即 ‘o1.__eq__(o2) is True’）
，則 ‘hash(o1) == hash(o2)’（即 ‘o1.__hash__() == o2.__hash__()’），這個
事實必須要成立。如果無法滿足這項限制，那字典和其他用雜湊為基底的結構會出
現不正常的行為。

至於 ‘ListWrapper’，只要這個包裝過的物件在字典中，裡面的串列就不能改變以
避免不正常的事情發生。除非你已經謹慎思考過你的需求和無法滿足條件的後果，
不然請不要這麼做。請自行注意。


File: python.info,  Node: 為何 list sort 不是回傳排序過的串列？,  Next: 如何在 Python 中指定和強制使用一個介面規範 interface spec ？,  Prev: 為何字典的鍵一定是不可變的？,  Up: 設計和歷史常見問答集

10.3.21 為何 list.sort() 不是回傳排序過的串列？
-----------------------------------------------

在重視效能的情況下，把串列複製一份有些浪費。因此，*note list.sort():
b76. 直接在串列裡做排序。為了提醒你這件事，他不會回傳排序過的串列。這樣
一來，當你需要排序過和未排序過的串列時，你就不會被誤導而不小心覆蓋掉串列
。

如果你想要他回傳新的串列，那可以改用內建的 *note sorted(): b75.。他會用
提供的可疊代物件 (iterable) 來排序建立新串列，並回傳之。例如，以下這個範
例會說明如何有序地疊代字典的鍵：

     for key in sorted(mydict):
         ...  # do whatever with mydict[key]...


File: python.info,  Node: 如何在 Python 中指定和強制使用一個介面規範 interface spec ？,  Next: 為何沒有 goto 語法？,  Prev: 為何 list sort 不是回傳排序過的串列？,  Up: 設計和歷史常見問答集

10.3.22 如何在 Python 中指定和強制使用一個介面規範 (interface spec)？
---------------------------------------------------------------------

像是 C++ 和 Java 等語言提供了模組的介面規範，他描述了該模組的方法和函式
的原型。很多人認為這種在編譯時強制執行的介面規範在建構大型程式時十分有幫
助。

Python 2.6 加入了 *note abc: 4. 模組，讓你可以定義抽象基底類別 (Abstract
Base Class, ABC)。你可以使用 *note isinstance(): 3e8. 和 *note
issubclass(): 765. 來確認一個實例或是類別是否實作了某個抽象基底類別。而
*note collections.abc: 17. 模組定義了一系列好用的抽象基底類別，像是
*note Iterable: 212a.、*note Container: 212c. 和 *note MutableMapping:
1048.。

對 Python 來說，很多介面規範的優點可以用對元件適當的測試規則來達到。

一個針對模組的好測試套件提供了回歸測試 (regression testing)，並作為模組
介面規範和一組範例。許多 Python 模組可以直接當成腳本執行，並提供簡單的「
自我測試」。即便模組使用了複雜的外部介面，他依然可以用外部介面的簡單的「
樁」(stub) 模擬來獨立測試。*note doctest: 31. 和 *note unittest: ef. 模
組或第三方的測試框架可以用來建構詳盡徹底的測試套件來測試模組裡的每一行程
式碼。

就像介面規範一樣，一個適當的測試規則在建造大型又複雜的 Python 應用程式時
可以幫上忙。事實上，他可能可以有更好的表現，因為介面規範無法測試程式的特
定屬性。舉例來說，‘list.append()’ 方法應該要在某個內部的串列最後面加上新
的元素，而介面規範沒辦法測試你的 ‘list.append()’ 是不是真的有正確的實作
，但這在測試套件裡是件很簡單的事。

撰寫測試套件相當有幫助，而你會像要把程式碼設計成好測試的樣子。測試驅動開
發 (test-driven development) 是一個越來越受歡迎的設計方法，他要求先完成
部分的測試套件，再去撰寫真的要用的程式碼。當然 Python 也允許你草率地不寫
任何測試。


File: python.info,  Node: 為何沒有 goto 語法？,  Next: 為何純字串 r-string 不能以反斜線結尾？,  Prev: 如何在 Python 中指定和強制使用一個介面規範 interface spec ？,  Up: 設計和歷史常見問答集

10.3.23 為何沒有 goto 語法？
----------------------------

在 1970 年代，人們了解到沒有限制的 goto 會導致混亂、難以理解和修改的「義
大利麵」程式碼 ("spaghetti" code)。在高階語言裡，這也是不需要的，因為有
方法可以做邏輯分支（以 Python 來說，用 *note if: 2c4. 陳述式和 *note or:
2c7.、*note and: 2c2. 及 *note if: 2c4./*note else: 172. 運算式）和迴圈
（用 *note while: 1b0b. 和 *note for: 2c3. 陳述式，可能會有 *note
continue: 96d. 和 *note break: a4c.）。

我們也可以用例外來做「結構化的 goto」，這甚至可以跨函式呼叫。很多人覺得
例外可以方便地模擬在 C、Fortran 和其他語言裡各種合理使用的 ‘go’ 和
‘goto’。例如：

     class label(Exception): pass  # declare a label

     try:
         ...
         if condition: raise label()  # goto label
         ...
     except label:  # where to goto
         pass
     ...

這依然不能讓你跳進迴圈內，這通常被認為是對 ‘goto’ 的濫用。請小心使用。


File: python.info,  Node: 為何純字串 r-string 不能以反斜線結尾？,  Next: 為何 Python 沒有屬性賦值的 with 陳述式？,  Prev: 為何沒有 goto 語法？,  Up: 設計和歷史常見問答集

10.3.24 為何純字串 (r-string) 不能以反斜線結尾？
------------------------------------------------

更精確地來說，他不能以奇數個反斜線結尾：尾端未配對的反斜線會使結尾的引號
被轉義 (escapes)，變成一個未結束的字串。

設計出純字串是為了提供有自己反斜線轉義處理的處理器（主要是正規表示式）一
個方便的輸入方式。這種處理器會把未配對的結尾反斜線當成錯誤，所以純字串不
允許如此。相對地，他讓你用一個反斜線轉義引號。這些規則在他們預想的目的上
正常地運作。

如果你嘗試建立 Windows 的路徑名稱，請注意 Windows 系統指令也接受一般斜線
：

     f = open("/mydir/file.txt")  # works fine!

如果你嘗試建立 DOS 指令的路徑名稱，試試看使用以下的範例：

     dir = r"\this\is\my\dos\dir" "\\"
     dir = r"\this\is\my\dos\dir\ "[:-1]
     dir = "\\this\\is\\my\\dos\\dir\\"


File: python.info,  Node: 為何 Python 沒有屬性賦值的 with 陳述式？,  Next: 為何產生器 generator 不支援 with 陳述式？,  Prev: 為何純字串 r-string 不能以反斜線結尾？,  Up: 設計和歷史常見問答集

10.3.25 為何 Python 沒有屬性賦值的 with 陳述式？
------------------------------------------------

Python 的 *note with: 577. 陳述式包裝了一區塊程式的執行，在進入和離開該
區塊時執行程式碼。一些語言會有像如下的結構：

     with obj:
         a = 1               # equivalent to obj.a = 1
         total = total + 1   # obj.total = obj.total + 1

但在 Python，這種結構是模糊的。

在其他語言裡，像是 Object Pascal、Delphi 和 C++，使用的是靜態型別，所以
我們可以清楚地知道是哪一個成員被指派值。這是靜態型別的重點 — 在編譯的時
候，編譯器'永遠'都知道每個變數的作用域 (scope)。

Python 使用的是動態型別。所以我們不可能提前知道在執行時哪個屬性會被使用
到。成員屬性可能在執行時從物件中被新增或移除。這使得如果簡單來看的話，我
們無法得知以下哪個屬性會被使用：區域的、全域的、或是成員屬性？

以下列不完整的程式碼為例：

     def foo(a):
         with a:
             print(x)

這段程式碼假設 ‘a’ 有一個叫做 ‘x’ 的成員屬性。然後，Python 裡並沒有任何
跡象告訴直譯器這件事。在假設「a」是一個整數的話，那會發生什麼事？如果有
一個全域變數稱為 ‘x’，那在這個 *note with: 577. 區塊會被使用嗎？如你所見
，Python 動態的天性使得這種選擇更加困難。

然而 *note with: 577. 陳述式或類似的語言特性（減少程式碼量）的主要好處可
以透過賦值來達成。相較於這樣寫：

     function(args).mydict[index][index].a = 21
     function(args).mydict[index][index].b = 42
     function(args).mydict[index][index].c = 63

應該寫成這樣：

     ref = function(args).mydict[index][index]
     ref.a = 21
     ref.b = 42
     ref.c = 63

這也有提升執行速度的副作用，因為 Python 的名稱綁定解析會在執行的時候發生
，而第二版只需要執行解析一次即可。

類似的提案包括引入語法以進一步減少程式碼量，例如使用「前導點 (leading
dot)」，但這些提案已被捨棄，以維持程式的明確性（參閱
‘https://mail.python.org/pipermail/python-ideas/2016-May/040070.html’）
。


File: python.info,  Node: 為何產生器 generator 不支援 with 陳述式？,  Next: 為何 if、while、def、class 陳述式裡需要冒號？,  Prev: 為何 Python 沒有屬性賦值的 with 陳述式？,  Up: 設計和歷史常見問答集

10.3.26 為何產生器 (generator) 不支援 with 陳述式？
---------------------------------------------------

出於技術原因，把產生器直接用作情境 (context) 管理器會無法正常運作。因為
通常來說，產生器是被當成疊代器 (iterator)，到最後完成時不需要被手動關閉
。但如果你需要的話，你可以在 *note with: 577. 陳述式裡用 *note
contextlib.closing(generator): 282a. 來包裝他。


File: python.info,  Node: 為何 if、while、def、class 陳述式裡需要冒號？,  Next: 為何 Python 允許在串列和元組末端加上逗號？,  Prev: 為何產生器 generator 不支援 with 陳述式？,  Up: 設計和歷史常見問答集

10.3.27 為何 if、while、def、class 陳述式裡需要冒號？
-----------------------------------------------------

需要冒號主要是為了增加可讀性（由 ABC 語言的實驗得知）。試想如下範例：

     if a == b
         print(a)

以及：

     if a == b:
         print(a)

注意第二個例子稍微易讀一些的原因。可以更進一步觀察，一個冒號是如何放在這
個 FAQ 答案的例子裡的，這是標準的英文用法。

另一個小原因是冒號會使編輯器更容易做語法突顯，他們只需要看冒號的位置就可
以決定是否需要更多縮排，而不用做更多繁複精密的程式碼剖析。


File: python.info,  Node: 為何 Python 允許在串列和元組末端加上逗號？,  Prev: 為何 if、while、def、class 陳述式裡需要冒號？,  Up: 設計和歷史常見問答集

10.3.28 為何 Python 允許在串列和元組末端加上逗號？
--------------------------------------------------

Python 允許你在串列、元組和字典的結尾加上逗號：

     [1, 2, 3,]
     ('a', 'b', 'c',)
     d = {
         "A": [1, 5],
         "B": [6, 7],  # last trailing comma is optional but good style
     }

這有許多原因可被允許。

當你要把串列、元組或字典的值寫成多行時，這樣做會讓你新增元素時較為方便，
因為你不需要在前一行加上逗號。這幾行的值也可以被重新排序，而不會導致語法
錯誤。

不小心遺漏了逗號會導致難以發現的錯誤，例如：

     x = [
       "fee",
       "fie"
       "foo",
       "fum"
     ]

這個串列看起來有四個元素，但他其實只有三個：「fee」、「fiefoo」、「fum」
。永遠記得加上逗號以避免這種錯誤。

允許結尾逗號也讓生成的程式碼更容易產生。


File: python.info,  Node: 函式庫和擴充功能的常見問題,  Next: 擴充/嵌入常見問題集,  Prev: 設計和歷史常見問答集,  Up: Python 常見問題

10.4 函式庫和擴充功能的常見問題
===============================

* Menu:

* 常見函式問題::
* 常見課題::
* 執行緒::
* 輸入與輸出::
* 網路 (Network)/網際網路 (Internet) 程式: 網路 Network /網際網路 Internet 程式.
* 資料庫::
* 數學和數值::


File: python.info,  Node: 常見函式問題,  Next: 常見課題,  Up: 函式庫和擴充功能的常見問題

10.4.1 常見函式問題
-------------------

* Menu:

* 我如何找到執行任務 X 的模組或應用程式？::
* 哪裡可以找到 math.py (socket.py, regex.py, 等...) 來源檔案？: 哪裡可以找到 math py socket py regex py 等 來源檔案？.
* 我如何使 Python script 執行在 Unix？::
* 是否有適用於 Python 的 curses/termcap 套件？::
* Python 中是否有等同於 C 的 onexit() 的函式？: Python 中是否有等同於 C 的 onexit 的函式？.
* 為什麼我的信號處理程式不起作用？::


File: python.info,  Node: 我如何找到執行任務 X 的模組或應用程式？,  Next: 哪裡可以找到 math py socket py regex py 等 來源檔案？,  Up: 常見函式問題

10.4.1.1 我如何找到執行任務 X 的模組或應用程式？
................................................

Check *note the Library Reference: 12a. to see if there's a relevant
standard library module.  (Eventually you'll learn what's in the
standard library and will be able to skip this step.)

For third-party packages, search the Python Package Index(1) or try
Google(2) or another web search engine.  Searching for "Python" plus a
keyword or two for your topic of interest will usually find something
helpful.

   ---------- Footnotes ----------

   (1) https://pypi.org

   (2) https://www.google.com


File: python.info,  Node: 哪裡可以找到 math py socket py regex py 等 來源檔案？,  Next: 我如何使 Python script 執行在 Unix？,  Prev: 我如何找到執行任務 X 的模組或應用程式？,  Up: 常見函式問題

10.4.1.2 哪裡可以找到 math.py (socket.py, regex.py, 等...) 來源檔案？
.....................................................................

If you can't find a source file for a module it may be a built-in or
dynamically loaded module implemented in C, C++ or other compiled
language.  In this case you may not have the source file or it may be
something like ‘mathmodule.c’, somewhere in a C source directory (not on
the Python Path).

有（至少）三種 Python 模組：

  1. 以 Python 編寫的模組 (.py)；

  2. 用 C 編寫並動態載入的模組（.dll、.pyd、.so、.sl 等）；

  3. 用 C 編寫並與直譯器鏈接的模組；要獲得這些 list，請輸入：

          import sys
          print(sys.builtin_module_names)


File: python.info,  Node: 我如何使 Python script 執行在 Unix？,  Next: 是否有適用於 Python 的 curses/termcap 套件？,  Prev: 哪裡可以找到 math py socket py regex py 等 來源檔案？,  Up: 常見函式問題

10.4.1.3 我如何使 Python script 執行在 Unix？
.............................................

You need to do two things: the script file's mode must be executable and
the first line must begin with ‘#!’ followed by the path of the Python
interpreter.

The first is done by executing ‘chmod +x scriptfile’ or perhaps ‘chmod
755 scriptfile’.

The second can be done in a number of ways.  The most straightforward
way is to write

     #!/usr/local/bin/python

as the very first line of your file, using the pathname for where the
Python interpreter is installed on your platform.

If you would like the script to be independent of where the Python
interpreter lives, you can use the ‘env’ program.  Almost all Unix
variants support the following, assuming the Python interpreter is in a
directory on the user's ‘PATH’:

     #!/usr/bin/env python

'Don't' do this for CGI scripts.  The ‘PATH’ variable for CGI scripts is
often very minimal, so you need to use the actual absolute pathname of
the interpreter.

Occasionally, a user's environment is so full that the ‘/usr/bin/env’
program fails; or there's no env program at all.  In that case, you can
try the following hack (due to Alex Rezinsky):

     #! /bin/sh
     """:"
     exec python $0 ${1+"$@"}
     """

The minor disadvantage is that this defines the script's __doc__ string.
However, you can fix that by adding

     __doc__ = """...Whatever..."""


File: python.info,  Node: 是否有適用於 Python 的 curses/termcap 套件？,  Next: Python 中是否有等同於 C 的 onexit 的函式？,  Prev: 我如何使 Python script 執行在 Unix？,  Up: 常見函式問題

10.4.1.4 是否有適用於 Python 的 curses/termcap 套件？
.....................................................

For Unix variants: The standard Python source distribution comes with a
curses module in the Modules(1) subdirectory, though it's not compiled
by default.  (Note that this is not available in the Windows
distribution - there is no curses module for Windows.)

The *note curses: 23. module supports basic curses features as well as
many additional functions from ncurses and SYSV curses such as colour,
alternative character set support, pads, and mouse support.  This means
the module isn't compatible with operating systems that only have BSD
curses, but there don't seem to be any currently maintained OSes that
fall into this category.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Modules


File: python.info,  Node: Python 中是否有等同於 C 的 onexit 的函式？,  Next: 為什麼我的信號處理程式不起作用？,  Prev: 是否有適用於 Python 的 curses/termcap 套件？,  Up: 常見函式問題

10.4.1.5 Python 中是否有等同於 C 的 onexit() 的函式？
.....................................................

The *note atexit: 9. module provides a register function that is similar
to C's ‘onexit()’.


File: python.info,  Node: 為什麼我的信號處理程式不起作用？,  Prev: Python 中是否有等同於 C 的 onexit 的函式？,  Up: 常見函式問題

10.4.1.6 為什麼我的信號處理程式不起作用？
.........................................

The most common problem is that the signal handler is declared with the
wrong argument list.  It is called as

     handler(signum, frame)

所以它應該用兩個參數聲明：

     def handler(signum, frame):
         ...


File: python.info,  Node: 常見課題,  Next: 執行緒,  Prev: 常見函式問題,  Up: 函式庫和擴充功能的常見問題

10.4.2 常見課題
---------------

* Menu:

* 如何測試 Python 程式或元件？::
* How do I create documentation from doc strings?::
* How do I get a single keypress at a time?::


File: python.info,  Node: 如何測試 Python 程式或元件？,  Next: How do I create documentation from doc strings?,  Up: 常見課題

10.4.2.1 如何測試 Python 程式或元件？
.....................................

Python comes with two testing frameworks.  The *note doctest: 31. module
finds examples in the docstrings for a module and runs them, comparing
the output with the expected output given in the docstring.

The *note unittest: ef. module is a fancier testing framework modelled
on Java and Smalltalk testing frameworks.

To make testing easier, you should use good modular design in your
program.  Your program should have almost all functionality encapsulated
in either functions or class methods - and this sometimes has the
surprising and delightful effect of making the program run faster
(because local variable accesses are faster than global accesses).
Furthermore the program should avoid depending on mutating global
variables, since this makes testing much more difficult to do.

The "global main logic" of your program may be as simple as

     if __name__ == "__main__":
         main_logic()

at the bottom of the main module of your program.

Once your program is organized as a tractable collection of function and
class behaviours, you should write test functions that exercise the
behaviours.  A test suite that automates a sequence of tests can be
associated with each module.  This sounds like a lot of work, but since
Python is so terse and flexible it's surprisingly easy.  You can make
coding much more pleasant and fun by writing your test functions in
parallel with the "production code", since this makes it easy to find
bugs and even design flaws earlier.

"Support modules" that are not intended to be the main module of a
program may include a self-test of the module.

     if __name__ == "__main__":
         self_test()

Even programs that interact with complex external interfaces may be
tested when the external interfaces are unavailable by using "fake"
interfaces implemented in Python.


File: python.info,  Node: How do I create documentation from doc strings?,  Next: How do I get a single keypress at a time?,  Prev: 如何測試 Python 程式或元件？,  Up: 常見課題

10.4.2.2 How do I create documentation from doc strings?
........................................................

The *note pydoc: a3. module can create HTML from the doc strings in your
Python source code.  An alternative for creating API documentation
purely from docstrings is epydoc(1).  Sphinx(2) can also include
docstring content.

   ---------- Footnotes ----------

   (1) https://epydoc.sourceforge.net/

   (2) https://www.sphinx-doc.org


File: python.info,  Node: How do I get a single keypress at a time?,  Prev: How do I create documentation from doc strings?,  Up: 常見課題

10.4.2.3 How do I get a single keypress at a time?
..................................................

For Unix variants there are several solutions.  It's straightforward to
do this using curses, but curses is a fairly large module to learn.


File: python.info,  Node: 執行緒,  Next: 輸入與輸出,  Prev: 常見課題,  Up: 函式庫和擴充功能的常見問題

10.4.3 執行緒
-------------

* Menu:

* 如何使用執行緒編寫程式？::
* 我的執行緒似乎都沒有運行：為什麼？::
* How do I parcel out work among a bunch of worker threads?::
* What kinds of global value mutation are thread-safe?::
* 不能擺脫全局直譯器鎖嗎？::


File: python.info,  Node: 如何使用執行緒編寫程式？,  Next: 我的執行緒似乎都沒有運行：為什麼？,  Up: 執行緒

10.4.3.1 如何使用執行緒編寫程式？
.................................

Be sure to use the *note threading: d6. module and not the *note
_thread: 2. module.  The *note threading: d6. module builds convenient
abstractions on top of the low-level primitives provided by the *note
_thread: 2. module.


File: python.info,  Node: 我的執行緒似乎都沒有運行：為什麼？,  Next: How do I parcel out work among a bunch of worker threads?,  Prev: 如何使用執行緒編寫程式？,  Up: 執行緒

10.4.3.2 我的執行緒似乎都沒有運行：為什麼？
...........................................

As soon as the main thread exits, all threads are killed.  Your main
thread is running too quickly, giving the threads no time to do any
work.

A simple fix is to add a sleep to the end of the program that's long
enough for all the threads to finish:

     import threading, time

     def thread_task(name, n):
         for i in range(n):
             print(name, i)

     for i in range(10):
         T = threading.Thread(target=thread_task, args=(str(i), i))
         T.start()

     time.sleep(10)  # <---------------------------!

But now (on many platforms) the threads don't run in parallel, but
appear to run sequentially, one at a time!  The reason is that the OS
thread scheduler doesn't start a new thread until the previous thread is
blocked.

A simple fix is to add a tiny sleep to the start of the run function:

     def thread_task(name, n):
         time.sleep(0.001)  # <--------------------!
         for i in range(n):
             print(name, i)

     for i in range(10):
         T = threading.Thread(target=thread_task, args=(str(i), i))
         T.start()

     time.sleep(10)

Instead of trying to guess a good delay value for *note time.sleep():
642, it's better to use some kind of semaphore mechanism.  One idea is
to use the *note queue: a4. module to create a queue object, let each
thread append a token to the queue when it finishes, and let the main
thread read as many tokens from the queue as there are threads.


File: python.info,  Node: How do I parcel out work among a bunch of worker threads?,  Next: What kinds of global value mutation are thread-safe?,  Prev: 我的執行緒似乎都沒有運行：為什麼？,  Up: 執行緒

10.4.3.3 How do I parcel out work among a bunch of worker threads?
..................................................................

The easiest way is to use the *note concurrent.futures: 1a. module,
especially the *note ThreadPoolExecutor: 6e6. class.

Or, if you want fine control over the dispatching algorithm, you can
write your own logic manually.  Use the *note queue: a4. module to
create a queue containing a list of jobs.  The *note Queue: 131c. class
maintains a list of objects and has a ‘.put(obj)’ method that adds items
to the queue and a ‘.get()’ method to return them.  The class will take
care of the locking necessary to ensure that each job is handed out
exactly once.

Here's a trivial example:

     import threading, queue, time

     # The worker thread gets jobs off the queue.  When the queue is empty, it
     # assumes there will be no more work and exits.
     # (Realistically workers will run until terminated.)
     def worker():
         print('Running worker')
         time.sleep(0.1)
         while True:
             try:
                 arg = q.get(block=False)
             except queue.Empty:
                 print('Worker', threading.current_thread(), end=' ')
                 print('queue empty')
                 break
             else:
                 print('Worker', threading.current_thread(), end=' ')
                 print('running with argument', arg)
                 time.sleep(0.5)

     # Create queue
     q = queue.Queue()

     # Start a pool of 5 workers
     for i in range(5):
         t = threading.Thread(target=worker, name='worker %i' % (i+1))
         t.start()

     # Begin adding work to the queue
     for i in range(50):
         q.put(i)

     # Give threads time to run
     print('Main thread sleeping')
     time.sleep(5)

When run, this will produce the following output:

     Running worker
     Running worker
     Running worker
     Running worker
     Running worker
     Main thread sleeping
     Worker <Thread(worker 1, started 130283832797456)> running with argument 0
     Worker <Thread(worker 2, started 130283824404752)> running with argument 1
     Worker <Thread(worker 3, started 130283816012048)> running with argument 2
     Worker <Thread(worker 4, started 130283807619344)> running with argument 3
     Worker <Thread(worker 5, started 130283799226640)> running with argument 4
     Worker <Thread(worker 1, started 130283832797456)> running with argument 5
     ...

Consult the module's documentation for more details; the *note Queue:
131c. class provides a featureful interface.


File: python.info,  Node: What kinds of global value mutation are thread-safe?,  Next: 不能擺脫全局直譯器鎖嗎？,  Prev: How do I parcel out work among a bunch of worker threads?,  Up: 執行緒

10.4.3.4 What kinds of global value mutation are thread-safe?
.............................................................

A *note global interpreter lock: 12e. (GIL) is used internally to ensure
that only one thread runs in the Python VM at a time.  In general,
Python offers to switch among threads only between bytecode
instructions; how frequently it switches can be set via *note
sys.setswitchinterval(): 8ee.  Each bytecode instruction and therefore
all the C implementation code reached from each instruction is therefore
atomic from the point of view of a Python program.

In theory, this means an exact accounting requires an exact
understanding of the PVM bytecode implementation.  In practice, it means
that operations on shared variables of built-in data types (ints, lists,
dicts, etc) that "look atomic" really are.

For example, the following operations are all atomic (L, L1, L2 are
lists, D, D1, D2 are dicts, x, y are objects, i, j are ints):

     L.append(x)
     L1.extend(L2)
     x = L[i]
     x = L.pop()
     L1[i:j] = L2
     L.sort()
     x = y
     x.field = y
     D[x] = y
     D1.update(D2)
     D.keys()

這些不是：

     i = i+1
     L.append(L[-1])
     L[i] = L[j]
     D[x] = D[x] + 1

Operations that replace other objects may invoke those other objects'
*note __del__(): 1e36. method when their reference count reaches zero,
and that can affect things.  This is especially true for the mass
updates to dictionaries and lists.  When in doubt, use a mutex!


File: python.info,  Node: 不能擺脫全局直譯器鎖嗎？,  Prev: What kinds of global value mutation are thread-safe?,  Up: 執行緒

10.4.3.5 不能擺脫全局直譯器鎖嗎？
.................................

The *note global interpreter lock: 12e. (GIL) is often seen as a
hindrance to Python's deployment on high-end multiprocessor server
machines, because a multi-threaded Python program effectively only uses
one CPU, due to the insistence that (almost) all Python code can only
run while the GIL is held.

With the approval of PEP 703(1) work is now underway to remove the GIL
from the CPython implementation of Python.  Initially it will be
implemented as an optional compiler flag when building the interpreter,
and so separate builds will be available with and without the GIL.
Long-term, the hope is to settle on a single build, once the performance
implications of removing the GIL are fully understood.  Python 3.13 is
likely to be the first release containing this work, although it may not
be completely functional in this release.

The current work to remove the GIL is based on a fork of Python 3.9 with
the GIL removed(2) by Sam Gross.  Prior to that, in the days of Python
1.5, Greg Stein actually implemented a comprehensive patch set (the
"free threading" patches) that removed the GIL and replaced it with
fine-grained locking.  Adam Olsen did a similar experiment in his
python-safethread(3) project.  Unfortunately, both of these earlier
experiments exhibited a sharp drop in single-thread performance (at
least 30% slower), due to the amount of fine-grained locking necessary
to compensate for the removal of the GIL. The Python 3.9 fork is the
first attempt at removing the GIL with an acceptable performance impact.

The presence of the GIL in current Python releases doesn't mean that you
can't make good use of Python on multi-CPU machines!  You just have to
be creative with dividing the work up between multiple 'processes'
rather than multiple 'threads'.  The *note ProcessPoolExecutor: 893.
class in the new *note concurrent.futures: 1a. module provides an easy
way of doing so; the *note multiprocessing: 86. module provides a
lower-level API in case you want more control over dispatching of tasks.

Judicious use of C extensions will also help; if you use a C extension
to perform a time-consuming task, the extension can release the GIL
while the thread of execution is in the C code and allow other threads
to get some work done.  Some standard library modules such as *note
zlib: 119. and *note hashlib: 5e. already do this.

An alternative approach to reducing the impact of the GIL is to make the
GIL a per-interpreter-state lock rather than truly global.  This was
*note first implemented in Python 3.12: 3e2. and is available in the C
API. A Python interface to it is expected in Python 3.13.  The main
limitation to it at the moment is likely to be 3rd party extension
modules, since these must be written with multiple interpreters in mind
in order to be usable, so many older extension modules will not be
usable.

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0703/

   (2) https://github.com/colesbury/nogil

   (3) https://code.google.com/archive/p/python-safethread


File: python.info,  Node: 輸入與輸出,  Next: 網路 Network /網際網路 Internet 程式,  Prev: 執行緒,  Up: 函式庫和擴充功能的常見問題

10.4.4 輸入與輸出
-----------------

* Menu:

* 如何刪除檔案？（以及其他檔案問題...）: 如何刪除檔案？（以及其他檔案問題 ）.
* 如何複製檔案？::
* 如何讀取（或寫入）二進位制資料？::
* I can't seem to use os.read() on a pipe created with os.popen(); why?: I can't seem to use os read on a pipe created with os popen ; why?.
* 如何存取序列 (RS232) 連接埠？: 如何存取序列 RS232 連接埠？.
* 為什麼關閉 sys.stdout (stdin, stderr) 並沒有真正關閉它？: 為什麼關閉 sys stdout stdin stderr 並沒有真正關閉它？.


File: python.info,  Node: 如何刪除檔案？（以及其他檔案問題 ）,  Next: 如何複製檔案？,  Up: 輸入與輸出

10.4.4.1 如何刪除檔案？（以及其他檔案問題...）
..............................................

Use ‘os.remove(filename)’ or ‘os.unlink(filename)’; for documentation,
see the *note os: 91. module.  The two functions are identical; *note
unlink(): 108e. is simply the name of the Unix system call for this
function.

To remove a directory, use *note os.rmdir(): 108c.; use *note
os.mkdir(): 202. to create one.  ‘os.makedirs(path)’ will create any
intermediate directories in ‘path’ that don't exist.
‘os.removedirs(path)’ will remove intermediate directories as long as
they're empty; if you want to delete an entire directory tree and its
contents, use *note shutil.rmtree(): 2d2.

要重新命名檔案，請使用 ‘os.rename(old_path, new_path)’。

To truncate a file, open it using ‘f = open(filename, "rb+")’, and use
‘f.truncate(offset)’; offset defaults to the current seek position.
There's also ‘os.ftruncate(fd, offset)’ for files opened with *note
os.open(): d38, where 'fd' is the file descriptor (a small integer).

The *note shutil: b3. module also contains a number of functions to work
on files including *note copyfile(): 9fc, *note copytree(): 9cd, and
*note rmtree(): 2d2.


File: python.info,  Node: 如何複製檔案？,  Next: 如何讀取（或寫入）二進位制資料？,  Prev: 如何刪除檔案？（以及其他檔案問題 ）,  Up: 輸入與輸出

10.4.4.2 如何複製檔案？
.......................

The *note shutil: b3. module contains a *note copyfile(): 9fc. function.
Note that on Windows NTFS volumes, it does not copy alternate data
streams(1) nor resource forks(2) on macOS HFS+ volumes, though both are
now rarely used.  It also doesn't copy file permissions and metadata,
though using *note shutil.copy2(): 9fe. instead will preserve most
(though not all) of it.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/NTFS#Alternate_data_stream_(ADS)

   (2) https://en.wikipedia.org/wiki/Resource_fork


File: python.info,  Node: 如何讀取（或寫入）二進位制資料？,  Next: I can't seem to use os read on a pipe created with os popen ; why?,  Prev: 如何複製檔案？,  Up: 輸入與輸出

10.4.4.3 如何讀取（或寫入）二進位制資料？
.........................................

To read or write complex binary data formats, it's best to use the *note
struct: c0. module.  It allows you to take a string containing binary
data (usually numbers) and convert it to Python objects; and vice versa.

For example, the following code reads two 2-byte integers and one 4-byte
integer in big-endian format from a file:

     import struct

     with open(filename, "rb") as f:
         s = f.read(8)
         x, y, z = struct.unpack(">hhl", s)

The '>' in the format string forces big-endian data; the letter 'h'
reads one "short integer" (2 bytes), and 'l' reads one "long integer" (4
bytes) from the string.

For data that is more regular (e.g.  a homogeneous list of ints or
floats), you can also use the *note array: 6. module.

     備註: To read and write binary data, it is mandatory to open the
     file in binary mode (here, passing ‘"rb"’ to *note open(): 4c0.).
     If you use ‘"r"’ instead (the default), the file will be open in
     text mode and ‘f.read()’ will return *note str: 3f2. objects rather
     than *note bytes: 1a5. objects.


File: python.info,  Node: I can't seem to use os read on a pipe created with os popen ; why?,  Next: 如何存取序列 RS232 連接埠？,  Prev: 如何讀取（或寫入）二進位制資料？,  Up: 輸入與輸出

10.4.4.4 I can't seem to use os.read() on a pipe created with os.popen(); why?
..............................................................................

*note os.read(): d3b. is a low-level function which takes a file
descriptor, a small integer representing the opened file.  *note
os.popen(): a2a. creates a high-level file object, the same type
returned by the built-in *note open(): 4c0. function.  Thus, to read 'n'
bytes from a pipe 'p' created with *note os.popen(): a2a, you need to
use ‘p.read(n)’.


File: python.info,  Node: 如何存取序列 RS232 連接埠？,  Next: 為什麼關閉 sys stdout stdin stderr 並沒有真正關閉它？,  Prev: I can't seem to use os read on a pipe created with os popen ; why?,  Up: 輸入與輸出

10.4.4.5 如何存取序列 (RS232) 連接埠？
......................................

對於 Win32、OSX、Linux、BSD、Jython、IronPython：

     pyserial(1)

對於 Unix，請參閱 Mitch Chapman 的 Usenet 貼文：

     ‘https://groups.google.com/groups?selm=34A04430.CF9@ohioee.com’

   ---------- Footnotes ----------

   (1) https://pypi.org/project/pyserial/


File: python.info,  Node: 為什麼關閉 sys stdout stdin stderr 並沒有真正關閉它？,  Prev: 如何存取序列 RS232 連接埠？,  Up: 輸入與輸出

10.4.4.6 為什麼關閉 sys.stdout (stdin, stderr) 並沒有真正關閉它？
.................................................................

Python *note 檔案物件: 115b.是低階 C 檔案描述器的高階抽象層。

For most file objects you create in Python via the built-in *note
open(): 4c0. function, ‘f.close()’ marks the Python file object as being
closed from Python's point of view, and also arranges to close the
underlying C file descriptor.  This also happens automatically in ‘f’'s
destructor, when ‘f’ becomes garbage.

But stdin, stdout and stderr are treated specially by Python, because of
the special status also given to them by C. Running ‘sys.stdout.close()’
marks the Python-level file object as being closed, but does 'not' close
the associated C file descriptor.

To close the underlying C file descriptor for one of these three, you
should first be sure that's what you really want to do (e.g., you may
confuse extension modules trying to do I/O). If it is, use *note
os.close(): b18.:

     os.close(stdin.fileno())
     os.close(stdout.fileno())
     os.close(stderr.fileno())

或者你可以分別使用數字常數 0、1 和 2。


File: python.info,  Node: 網路 Network /網際網路 Internet 程式,  Next: 資料庫,  Prev: 輸入與輸出,  Up: 函式庫和擴充功能的常見問題

10.4.5 網路 (Network)/網際網路 (Internet) 程式
----------------------------------------------

* Menu:

* Python 有哪些 WWW 工具？::
* 我應該使用什麼模組來輔助產生 HTML？::
* 如何從 Python 腳本發送郵件？::
* How do I avoid blocking in the connect() method of a socket?: How do I avoid blocking in the connect method of a socket?.


File: python.info,  Node: Python 有哪些 WWW 工具？,  Next: 我應該使用什麼模組來輔助產生 HTML？,  Up: 網路 Network /網際網路 Internet 程式

10.4.5.1 Python 有哪些 WWW 工具？
.................................

See the chapters titled *note 網路協定 (Internet protocols) 及支援:
376d. and *note 網際網路資料處理: 3386. in the Library Reference Manual.
Python has many modules that will help you build server-side and
client-side web systems.

A summary of available frameworks is maintained by Paul Boddie at
‘https://wiki.python.org/moin/WebProgramming’.


File: python.info,  Node: 我應該使用什麼模組來輔助產生 HTML？,  Next: 如何從 Python 腳本發送郵件？,  Prev: Python 有哪些 WWW 工具？,  Up: 網路 Network /網際網路 Internet 程式

10.4.5.2 我應該使用什麼模組來輔助產生 HTML？
............................................

You can find a collection of useful links on the Web Programming wiki
page(1).

   ---------- Footnotes ----------

   (1) https://wiki.python.org/moin/WebProgramming


File: python.info,  Node: 如何從 Python 腳本發送郵件？,  Next: How do I avoid blocking in the connect method of a socket?,  Prev: 我應該使用什麼模組來輔助產生 HTML？,  Up: 網路 Network /網際網路 Internet 程式

10.4.5.3 如何從 Python 腳本發送郵件？
.....................................

使用標準函式庫模組 *note smtplib: b7.。

Here's a very simple interactive mail sender that uses it.  This method
will work on any host that supports an SMTP listener.

     import sys, smtplib

     fromaddr = input("From: ")
     toaddrs  = input("To: ").split(',')
     print("Enter message, end with ^D:")
     msg = ''
     while True:
         line = sys.stdin.readline()
         if not line:
             break
         msg += line

     # The actual mail send
     server = smtplib.SMTP('localhost')
     server.sendmail(fromaddr, toaddrs, msg)
     server.quit()

A Unix-only alternative uses sendmail.  The location of the sendmail
program varies between systems; sometimes it is ‘/usr/lib/sendmail’,
sometimes ‘/usr/sbin/sendmail’.  The sendmail manual page will help you
out.  Here's some sample code:

     import os

     SENDMAIL = "/usr/sbin/sendmail"  # sendmail location
     p = os.popen("%s -t -i" % SENDMAIL, "w")
     p.write("To: receiver@example.com\n")
     p.write("Subject: test\n")
     p.write("\n")  # blank line separating headers from body
     p.write("Some text\n")
     p.write("some more text\n")
     sts = p.close()
     if sts != 0:
         print("Sendmail exit status", sts)


File: python.info,  Node: How do I avoid blocking in the connect method of a socket?,  Prev: 如何從 Python 腳本發送郵件？,  Up: 網路 Network /網際網路 Internet 程式

10.4.5.4 How do I avoid blocking in the connect() method of a socket?
.....................................................................

*note select: af. 模組通常用於幫助處理 socket 上的非同步 I/O。

To prevent the TCP connect from blocking, you can set the socket to
non-blocking mode.  Then when you do the *note connect(): d49, you will
either connect immediately (unlikely) or get an exception that contains
the error number as ‘.errno’.  ‘errno.EINPROGRESS’ indicates that the
connection is in progress, but hasn't finished yet.  Different OSes will
return different values, so you're going to have to check what's
returned on your system.

You can use the *note connect_ex(): 14a7. method to avoid creating an
exception.  It will just return the errno value.  To poll, you can call
*note connect_ex(): 14a7. again later - ‘0’ or ‘errno.EISCONN’ indicate
that you're connected - or you can pass this socket to *note
select.select(): d46. to check if it's writable.

     備註: *note asyncio: 8. 模組提供了一個通用的單執行緒並發非同步函式
     庫，可用於編寫非阻塞網路程式碼。第三方 Twisted(1) 函式庫是一種流行
     且功能豐富的替代方案。

   ---------- Footnotes ----------

   (1) https://twisted.org/


File: python.info,  Node: 資料庫,  Next: 數學和數值,  Prev: 網路 Network /網際網路 Internet 程式,  Up: 函式庫和擴充功能的常見問題

10.4.6 資料庫
-------------

* Menu:

* Python 中是否有任何資料庫套件的介面？::
* How do you implement persistent objects in Python?::


File: python.info,  Node: Python 中是否有任何資料庫套件的介面？,  Next: How do you implement persistent objects in Python?,  Up: 資料庫

10.4.6.1 Python 中是否有任何資料庫套件的介面？
..............................................

有的。

Interfaces to disk-based hashes such as *note DBM: 2c. and *note GDBM:
2b. are also included with standard Python.  There is also the *note
sqlite3: ba. module, which provides a lightweight disk-based relational
database.

Support for most relational databases is available.  See the
DatabaseProgramming wiki page(1) for details.

   ---------- Footnotes ----------

   (1) https://wiki.python.org/moin/DatabaseProgramming


File: python.info,  Node: How do you implement persistent objects in Python?,  Prev: Python 中是否有任何資料庫套件的介面？,  Up: 資料庫

10.4.6.2 How do you implement persistent objects in Python?
...........................................................

The *note pickle: 95. library module solves this in a very general way
(though you still can't store things like open files, sockets or
windows), and the *note shelve: b1. library module uses pickle and
(g)dbm to create persistent mappings containing arbitrary Python
objects.


File: python.info,  Node: 數學和數值,  Prev: 資料庫,  Up: 函式庫和擴充功能的常見問題

10.4.7 數學和數值
-----------------

* Menu:

* 如何在 Python 中生成隨機數？::


File: python.info,  Node: 如何在 Python 中生成隨機數？,  Up: 數學和數值

10.4.7.1 如何在 Python 中生成隨機數？
.....................................

標準模組 *note random: a6. 實作了一個隨機數生成器。用法很簡單：

     import random
     random.random()

這將回傳 [0, 1) 範圍內的隨機浮點數。

該模組中還有許多其他專用生成器，例如：

   * ‘randrange(a, b)’ 會選擇 [a, b) 範圍內的一個整數。

   * ‘uniform(a, b)’ 會選擇 [a, b) 範圍內的浮點數。

   * ‘normalvariate(mean, sdev)’ 對常態（高斯）分佈進行採樣 (sample)。

一些更高階的函式會直接對序列進行操作，例如：

   * ‘choice(S)’ 會從給定序列中選擇一個隨機元素。

   * ‘shuffle(L)’ 會原地 (in-place) 打亂 list，即隨機排列它。

還有一個 ‘Random’ 類別，你可以將它實例化以建立多個獨立的隨機數生成器。


File: python.info,  Node: 擴充/嵌入常見問題集,  Next: 在 Windows 使用 Python 的常見問答集,  Prev: 函式庫和擴充功能的常見問題,  Up: Python 常見問題

10.5 擴充/嵌入常見問題集
========================

* Menu:

* 我可以在 C 中建立自己的函式嗎？::
* 我可以在 C++ 中建立自己的函式嗎？::
* 寫 C 很難；還有其他選擇嗎？::
* 如何從 C 執行任意 Python 陳述式？::
* How can I evaluate an arbitrary Python expression from C?::
* 如何從 Python 物件中提取 C 值？::
* 如何使用 Py_BuildValue() 建立任意長度的元組？: 如何使用 Py_BuildValue 建立任意長度的元組？.
* 如何從 C 呼叫物件的方法？::
* 我如何捕捉 PyErr_Print() 的輸出（或任何印出到 stdout/stderr 的東西）？: 我如何捕捉 PyErr_Print 的輸出（或任何印出到 stdout/stderr 的東西）？.
* 如何從 C 存取用 Python 編寫的模組？::
* How do I interface to C++ objects from Python?::
* 我使用安裝檔案新增了一個模組，但 make 失敗了；為什麼？::
* 如何為擴充套件除錯？::
* 我想在我的 Linux 系統上編譯一個 Python 模組，但是缺少一些檔案。為什麼？::
* 如何從「無效輸入」區分出「不完整輸入」？::
* 如何找到未定義的 g++ 符號 __builtin_new 或 __pure_virtual？::
* Can I create an object class with some methods implemented in C and others in Python (e.g. through inheritance)?: Can I create an object class with some methods implemented in C and others in Python e g through inheritance ?.


File: python.info,  Node: 我可以在 C 中建立自己的函式嗎？,  Next: 我可以在 C++ 中建立自己的函式嗎？,  Up: 擴充/嵌入常見問題集

10.5.1 我可以在 C 中建立自己的函式嗎？
--------------------------------------

是的，你可以在 C 中建立包含函式、變數、例外甚至新型別的內建模組，*note
擴充和嵌入 Python 直譯器: 1ae1. 文件中有相關說明。

大多數中級或進階 Python 書籍也會涵蓋這個主題。


File: python.info,  Node: 我可以在 C++ 中建立自己的函式嗎？,  Next: 寫 C 很難；還有其他選擇嗎？,  Prev: 我可以在 C 中建立自己的函式嗎？,  Up: 擴充/嵌入常見問題集

10.5.2 我可以在 C++ 中建立自己的函式嗎？
----------------------------------------

Yes, using the C compatibility features found in C++.  Place ‘extern "C"
{ ... }’ around the Python include files and put ‘extern "C"’ before
each function that is going to be called by the Python interpreter.
Global or static C++ objects with constructors are probably not a good
idea.


File: python.info,  Node: 寫 C 很難；還有其他選擇嗎？,  Next: 如何從 C 執行任意 Python 陳述式？,  Prev: 我可以在 C++ 中建立自己的函式嗎？,  Up: 擴充/嵌入常見問題集

10.5.3 寫 C 很難；還有其他選擇嗎？
----------------------------------

要編寫你自己的 C 擴充有許多替代方法，取決於你要執行的具體操作為何。

Cython(1) and its relative Pyrex(2) are compilers that accept a slightly
modified form of Python and generate the corresponding C code.  Cython
and Pyrex make it possible to write an extension without having to learn
Python's C API.

If you need to interface to some C or C++ library for which no Python
extension currently exists, you can try wrapping the library's data
types and functions with a tool such as SWIG(3). SIP(4), CXX(5)
Boost(6), or Weave(7) are also alternatives for wrapping C++ libraries.

   ---------- Footnotes ----------

   (1) https://cython.org

   (2) https://www.csse.canterbury.ac.nz/greg.ewing/python/Pyrex/

   (3) https://www.swig.org

   (4) https://github.com/Python-SIP/sip

   (5) https://cxx.sourceforge.net/

   (6) https://www.boost.org/libs/python/doc/index.html

   (7) https://github.com/scipy/weave


File: python.info,  Node: 如何從 C 執行任意 Python 陳述式？,  Next: How can I evaluate an arbitrary Python expression from C?,  Prev: 寫 C 很難；還有其他選擇嗎？,  Up: 擴充/嵌入常見問題集

10.5.4 如何從 C 執行任意 Python 陳述式？
----------------------------------------

The highest-level function to do this is *note PyRun_SimpleString():
473f. which takes a single string argument to be executed in the context
of the module ‘__main__’ and returns ‘0’ for success and ‘-1’ when an
exception occurred (including *note SyntaxError: 173.).  If you want
more control, use *note PyRun_String(): 18e0.; see the source for *note
PyRun_SimpleString(): 473f. in ‘Python/pythonrun.c’.


File: python.info,  Node: How can I evaluate an arbitrary Python expression from C?,  Next: 如何從 Python 物件中提取 C 值？,  Prev: 如何從 C 執行任意 Python 陳述式？,  Up: 擴充/嵌入常見問題集

10.5.5 How can I evaluate an arbitrary Python expression from C?
----------------------------------------------------------------

Call the function *note PyRun_String(): 18e0. from the previous question
with the start symbol *note Py_eval_input: 48e2.; it parses an
expression, evaluates it and returns its value.


File: python.info,  Node: 如何從 Python 物件中提取 C 值？,  Next: 如何使用 Py_BuildValue 建立任意長度的元組？,  Prev: How can I evaluate an arbitrary Python expression from C?,  Up: 擴充/嵌入常見問題集

10.5.6 如何從 Python 物件中提取 C 值？
--------------------------------------

That depends on the object's type.  If it's a tuple, *note
PyTuple_Size(): 4871. returns its length and *note PyTuple_GetItem():
46ed. returns the item at a specified index.  Lists have similar
functions, *note PyList_Size(): 1387. and *note PyList_GetItem(): 313.

For bytes, *note PyBytes_Size(): 478d. returns its length and *note
PyBytes_AsStringAndSize(): 4787. provides a pointer to its value and its
length.  Note that Python bytes objects may contain null bytes so C's
‘strlen()’ should not be used.

要測試物件的型別，首先確保它不是 ‘NULL’，然後再使用 *note
PyBytes_Check(): 1322.、*note PyTuple_Check(): 4a50.、*note
PyList_Check(): 4a60. 等函式。

There is also a high-level API to Python objects which is provided by
the so-called 'abstract' interface - read ‘Include/abstract.h’ for
further details.  It allows interfacing with any kind of Python sequence
using calls like *note PySequence_Length(): 4852, *note
PySequence_GetItem(): 1959, etc.  as well as many other useful protocols
such as numbers (*note PyNumber_Index(): 837. et al.)  and mappings in
the PyMapping APIs.


File: python.info,  Node: 如何使用 Py_BuildValue 建立任意長度的元組？,  Next: 如何從 C 呼叫物件的方法？,  Prev: 如何從 Python 物件中提取 C 值？,  Up: 擴充/嵌入常見問題集

10.5.7 如何使用 Py_BuildValue() 建立任意長度的元組？
----------------------------------------------------

這無法做到。請改用 *note PyTuple_Pack(): 4870.。


File: python.info,  Node: 如何從 C 呼叫物件的方法？,  Next: 我如何捕捉 PyErr_Print 的輸出（或任何印出到 stdout/stderr 的東西）？,  Prev: 如何使用 Py_BuildValue 建立任意長度的元組？,  Up: 擴充/嵌入常見問題集

10.5.8 如何從 C 呼叫物件的方法？
--------------------------------

The *note PyObject_CallMethod(): 366. function can be used to call an
arbitrary method of an object.  The parameters are the object, the name
of the method to call, a format string like that used with *note
Py_BuildValue(): 84c, and the argument values:

     PyObject *
     PyObject_CallMethod(PyObject *object, const char *method_name,
                         const char *arg_format, ...);

This works for any object that has methods - whether built-in or
user-defined.  You are responsible for eventually *note Py_DECREF():
515.'ing the return value.

例如，使用引數 10、0 呼叫檔案物件的 "seek" 方法（假設檔案物件指標為 "f"）
：

     res = PyObject_CallMethod(f, "seek", "(ii)", 10, 0);
     if (res == NULL) {
             ... an exception occurred ...
     }
     else {
             Py_DECREF(res);
     }

Note that since *note PyObject_CallObject(): 46e2. 'always' wants a
tuple for the argument list, to call a function without arguments, pass
"()" for the format, and to call a function with one argument, surround
the argument in parentheses, e.g.  "(i)".


File: python.info,  Node: 我如何捕捉 PyErr_Print 的輸出（或任何印出到 stdout/stderr 的東西）？,  Next: 如何從 C 存取用 Python 編寫的模組？,  Prev: 如何從 C 呼叫物件的方法？,  Up: 擴充/嵌入常見問題集

10.5.9 我如何捕捉 PyErr_Print() 的輸出（或任何印出到 stdout/stderr 的東西）？
-----------------------------------------------------------------------------

In Python code, define an object that supports the ‘write()’ method.
Assign this object to *note sys.stdout: a79. and *note sys.stderr: 8dd.
Call print_error, or just allow the standard traceback mechanism to
work.  Then, the output will go wherever your ‘write()’ method sends it.

最簡單的方法是使用 *note io.StringIO: ecb. 類別：

     >>> import io, sys
     >>> sys.stdout = io.StringIO()
     >>> print('foo')
     >>> print('hello world!')
     >>> sys.stderr.write(sys.stdout.getvalue())
     foo
     hello world!

A custom object to do the same would look like this:

     >>> import io, sys
     >>> class StdoutCatcher(io.TextIOBase):
     ...     def __init__(self):
     ...         self.data = []
     ...     def write(self, stuff):
     ...         self.data.append(stuff)
     ...
     >>> import sys
     >>> sys.stdout = StdoutCatcher()
     >>> print('foo')
     >>> print('hello world!')
     >>> sys.stderr.write(''.join(sys.stdout.data))
     foo
     hello world!


File: python.info,  Node: 如何從 C 存取用 Python 編寫的模組？,  Next: How do I interface to C++ objects from Python?,  Prev: 我如何捕捉 PyErr_Print 的輸出（或任何印出到 stdout/stderr 的東西）？,  Up: 擴充/嵌入常見問題集

10.5.10 如何從 C 存取用 Python 編寫的模組？
-------------------------------------------

You can get a pointer to the module object as follows:

     module = PyImport_ImportModule("<modulename>");

If the module hasn't been imported yet (i.e.  it is not yet present in
*note sys.modules: 186e.), this initializes the module; otherwise it
simply returns the value of ‘sys.modules["<modulename>"]’.  Note that it
doesn't enter the module into any namespace - it only ensures it has
been initialized and is stored in *note sys.modules: 186e.

You can then access the module's attributes (i.e.  any name defined in
the module) as follows:

     attr = PyObject_GetAttrString(module, "<attrname>");

Calling *note PyObject_SetAttrString(): 14f4. to assign to variables in
the module also works.


File: python.info,  Node: How do I interface to C++ objects from Python?,  Next: 我使用安裝檔案新增了一個模組，但 make 失敗了；為什麼？,  Prev: 如何從 C 存取用 Python 編寫的模組？,  Up: 擴充/嵌入常見問題集

10.5.11 How do I interface to C++ objects from Python?
------------------------------------------------------

Depending on your requirements, there are many approaches.  To do this
manually, begin by reading *note the "Extending and Embedding" document:
1ae1.  Realize that for the Python run-time system, there isn't a whole
lot of difference between C and C++ - so the strategy of building a new
Python type around a C structure (pointer) type will also work for C++
objects.

對於 C++ 函式庫，請參閱 *note 寫 C 很難；還有其他選擇嗎？: 4f0a.。


File: python.info,  Node: 我使用安裝檔案新增了一個模組，但 make 失敗了；為什麼？,  Next: 如何為擴充套件除錯？,  Prev: How do I interface to C++ objects from Python?,  Up: 擴充/嵌入常見問題集

10.5.12 我使用安裝檔案新增了一個模組，但 make 失敗了；為什麼？
--------------------------------------------------------------

Setup must end in a newline, if there is no newline there, the build
process fails.  (Fixing this requires some ugly shell script hackery,
and this bug is so minor that it doesn't seem worth the effort.)


File: python.info,  Node: 如何為擴充套件除錯？,  Next: 我想在我的 Linux 系統上編譯一個 Python 模組，但是缺少一些檔案。為什麼？,  Prev: 我使用安裝檔案新增了一個模組，但 make 失敗了；為什麼？,  Up: 擴充/嵌入常見問題集

10.5.13 如何為擴充套件除錯？
----------------------------

When using GDB with dynamically loaded extensions, you can't set a
breakpoint in your extension until your extension is loaded.

In your ‘.gdbinit’ file (or interactively), add the command:

     br _PyImport_LoadDynamicModule

然後，當你運行 GDB 時：

     $ gdb /local/bin/python
     gdb) run myscript.py
     gdb) continue # repeat until your extension is loaded
     gdb) finish   # so that your extension is loaded
     gdb) br myfunction.c:50
     gdb) continue


File: python.info,  Node: 我想在我的 Linux 系統上編譯一個 Python 模組，但是缺少一些檔案。為什麼？,  Next: 如何從「無效輸入」區分出「不完整輸入」？,  Prev: 如何為擴充套件除錯？,  Up: 擴充/嵌入常見問題集

10.5.14 我想在我的 Linux 系統上編譯一個 Python 模組，但是缺少一些檔案。為什麼？
-------------------------------------------------------------------------------

Most packaged versions of Python don't include the
‘/usr/lib/python2.`x'/config/’ directory, which contains various files
required for compiling Python extensions.

在 Red Hat 上，請安裝 python-devel RPM 來取得必要的檔案。

對於 Debian，運行 ‘apt-get install python-dev’。


File: python.info,  Node: 如何從「無效輸入」區分出「不完整輸入」？,  Next: 如何找到未定義的 g++ 符號 __builtin_new 或 __pure_virtual？,  Prev: 我想在我的 Linux 系統上編譯一個 Python 模組，但是缺少一些檔案。為什麼？,  Up: 擴充/嵌入常見問題集

10.5.15 如何從「無效輸入」區分出「不完整輸入」？
------------------------------------------------

Sometimes you want to emulate the Python interactive interpreter's
behavior, where it gives you a continuation prompt when the input is
incomplete (e.g.  you typed the start of an "if" statement or you didn't
close your parentheses or triple string quotes), but it gives you a
syntax error message immediately when the input is invalid.

在 Python 中，你可以使用 *note codeop: 15. 模組，它充分模擬了剖析器
(parser) 的行為。像是 IDLE 就有使用它。

The easiest way to do it in C is to call *note PyRun_InteractiveLoop():
48e9. (perhaps in a separate thread) and let the Python interpreter
handle the input for you.  You can also set the *note
PyOS_ReadlineFunctionPointer(): 52c. to point at your custom input
function.  See ‘Modules/readline.c’ and ‘Parser/myreadline.c’ for more
hints.


File: python.info,  Node: 如何找到未定義的 g++ 符號 __builtin_new 或 __pure_virtual？,  Next: Can I create an object class with some methods implemented in C and others in Python e g through inheritance ?,  Prev: 如何從「無效輸入」區分出「不完整輸入」？,  Up: 擴充/嵌入常見問題集

10.5.16 如何找到未定義的 g++ 符號 __builtin_new 或 __pure_virtual？
-------------------------------------------------------------------

To dynamically load g++ extension modules, you must recompile Python,
relink it using g++ (change LINKCC in the Python Modules Makefile), and
link your extension module using g++ (e.g., ‘g++ -shared -o mymodule.so
mymodule.o’).


File: python.info,  Node: Can I create an object class with some methods implemented in C and others in Python e g through inheritance ?,  Prev: 如何找到未定義的 g++ 符號 __builtin_new 或 __pure_virtual？,  Up: 擴充/嵌入常見問題集

10.5.17 Can I create an object class with some methods implemented in C and others in Python (e.g. through inheritance)?
------------------------------------------------------------------------------------------------------------------------

是的，你可以繼承內建類別，例如 *note int: 23c.、*note list: 5b6.、*note
dict: 23b. 等。

Boost Python 函式庫（BPL，
‘https://www.boost.org/libs/python/doc/index.html’）提供了一種從 C++ 執
行此操作的方法（即你可以使用 BPL 來繼承用 C++ 編寫的擴充類別）。


File: python.info,  Node: 在 Windows 使用 Python 的常見問答集,  Next: 圖形使用者介面常見問答集,  Prev: 擴充/嵌入常見問題集,  Up: Python 常見問題

10.6 在 Windows 使用 Python 的常見問答集
========================================

* Menu:

* 如何在 Windows 作業系統裡運行 Python 程式？::
* 如何使 Python 腳本可以執行？::
* 為什麼 Python 有時需要這麼長的時間才能開始？::
* 如何從 Python 腳本製作可執行檔？::
* *.pyd 檔是否與 DLL 相同？: * pyd 檔是否與 DLL 相同？.
* 如何將 Python 嵌入 Windows 應用程式中？::
* 如何防止編輯器在我的 Python 原始碼中插入 tab？::
* 如何在不阻塞的情況下檢查 keypress？::
* 如何解決遺漏 api-ms-win-crt-runtime-l1-1-0.dll 的錯誤？: 如何解決遺漏 api-ms-win-crt-runtime-l1-1-0 dll 的錯誤？.


File: python.info,  Node: 如何在 Windows 作業系統裡運行 Python 程式？,  Next: 如何使 Python 腳本可以執行？,  Up: 在 Windows 使用 Python 的常見問答集

10.6.1 如何在 Windows 作業系統裡運行 Python 程式？
--------------------------------------------------

這個問題的答案可能有點複雜。如果你經常使用「命令提示字元」執行程式，那這
對你來說不會是什麼難事。如果不然，那就需要更仔細的說明了。

除非你使用某種整合開發環境，否則你最終將會在所謂的「命令提示字元視窗」中
'打字輸入' Windows 命令。通常，你可以透過從搜尋欄中搜尋 ‘cmd’ 來建立這樣
的視窗。你應該能夠認出何時已啟動這樣的視窗，因為你將看到 Windows「命令提
示字元」，它通常看起來像這樣：

     C:\>

第一個字母可能不一樣，且後面也可能還有其他內容，因此你可能會很容易看到類
似以下的文字：

     D:\YourName\Projects\Python>

取決於你的電腦如何被設置，以及你最近對它所做的其他操作。一旦你啟動了這樣
一個視窗，你就即將可以運行 Python 程式了。

你需要了解，你的 Python 腳本必須被另一個稱為 Python '直譯器'的程序來處理
。直譯器會讀取你的腳本，將其編譯為位元組碼，然後執行該位元組碼以運行你的
程式。那麼，你要如何安排直譯器來處理你的 Python 呢？

首先，你需要確保你的命令視窗會將單字 "py" 識別為啟動直譯器的指令。如果你
已經開啟一個命令視窗，則你應該試試輸入命令 ‘py’ 並按下 return 鍵：

     C:\Users\YourName> py

然後，你應該看到類似下面的內容：

     Python 3.6.4 (v3.6.4:d48eceb, Dec 19 2017, 06:04:45) [MSC v.1900 32 bit (Intel)] on win32
     Type "help", "copyright", "credits" or "license" for more information.
     >>>

你已經啟動直譯器中的「互動模式」。這表示你能夠以互動方式輸入 Python 陳述
式或運算式，並在等待時執行或計算它們。這是 Python 最強大的功能之一。輸入
你所選的幾個運算式並查看結果，可以檢驗此功能：

     >>> print("Hello")
     Hello
     >>> "Hello" * 3
     'HelloHelloHello'

許多人將互動模式作為方便但可高度程式化的計算機。如果你要結束互動式
Python 對話，請呼叫 *note exit(): 2066. 函式或是按住 ‘Ctrl’ 鍵再輸入
‘Z’，然後按下 "‘Enter’" 鍵以返回 Windows 命令提示字元。

你可能還會發現你有一個開始功能表項目，像是：開始 ‣ 所有程式 ‣ Python 3.x
‣ Python（命令行），它會讓你在一個新視窗中看到 ‘>>>’ 提示字元。如果是這
樣，該視窗將在你呼叫 *note exit(): 2066. 函式或輸入 ‘Ctrl-Z’ 字元後消失
；Windows 正在該視窗中運行單一個「python」命令，並在你終止直譯器時將其關
閉。

現在我們知道 ‘py’ 命令已被識別，而你可以將你的 Python 腳本提供給它。你必
須為 Python 腳本給定絕對路徑或相對路徑。假設你的 Python 腳本位於桌面上，
並被命名為 ‘hello.py’，且你的命令提示字元在你的家目錄 (home directory) 中
順利地被開啟，那麼你就會看到類似以下的內容：

     C:\Users\YourName>

因此，現在你將透過鍵入 ‘py’ 加上腳本路徑，來使用 ‘py’ 命令將你的腳本提供
給 Python：

     C:\Users\YourName> py Desktop\hello.py
     hello


File: python.info,  Node: 如何使 Python 腳本可以執行？,  Next: 為什麼 Python 有時需要這麼長的時間才能開始？,  Prev: 如何在 Windows 作業系統裡運行 Python 程式？,  Up: 在 Windows 使用 Python 的常見問答集

10.6.2 如何使 Python 腳本可以執行？
-----------------------------------

在 Windows 上，標準的 Python 安裝程式已將 .py 副檔名與一種檔案類型
(Python.File) 進行關聯，並為該檔案類型提供一個開啟命令來運行直譯器
(‘D:\Program Files\Python\python.exe "%1" %*’)。這足以使腳本能以類似
'foo.py' 的形式從命令提示字元被執行。如果你希望能夠簡單地輸入 'foo' 來執
行腳本，而不用加上副檔名，則需要將 .py 新增至 PATHEXT 環境變數中。


File: python.info,  Node: 為什麼 Python 有時需要這麼長的時間才能開始？,  Next: 如何從 Python 腳本製作可執行檔？,  Prev: 如何使 Python 腳本可以執行？,  Up: 在 Windows 使用 Python 的常見問答集

10.6.3 為什麼 Python 有時需要這麼長的時間才能開始？
---------------------------------------------------

通常 Python 在 Windows 上啟動得非常快，但偶爾會有一些錯誤報告，內容是
Python 突然開始需要很長的時間才能啟動。這種情形更令人費解，因為 Python 在
其他 Windows 系統上可以正常工作，而那些系統似乎也有相同的配置。

這個問題可能是由發生此問題的電腦上的病毒檢查軟體配置錯誤所引起的。目前已
知某些病毒掃描程式，在它們被配置為監視來自檔案系統的所有讀取時，會引入兩
個數量級的啟動負擔。請試著檢查你系統上的病毒掃描軟體配置，以確保它們的配
置確實相同。當 McAfee 被配置為掃描所有檔案系統的讀取活動時，它是一個特定
的違規者。


File: python.info,  Node: 如何從 Python 腳本製作可執行檔？,  Next: * pyd 檔是否與 DLL 相同？,  Prev: 為什麼 Python 有時需要這麼長的時間才能開始？,  Up: 在 Windows 使用 Python 的常見問答集

10.6.4 如何從 Python 腳本製作可執行檔？
---------------------------------------

請參閱*note 如何從 Python 腳本建立獨立的二進位檔案？: 4e79.該章節列出了
用於製作可執行檔的工具清單。


File: python.info,  Node: * pyd 檔是否與 DLL 相同？,  Next: 如何將 Python 嵌入 Windows 應用程式中？,  Prev: 如何從 Python 腳本製作可執行檔？,  Up: 在 Windows 使用 Python 的常見問答集

10.6.5 ‘*.pyd’ 檔是否與 DLL 相同？
----------------------------------

是的，.pyd 檔類似於 dll，但也有一些區別。如果你有一個名為 ‘foo.pyd’ 的
DLL，則它必須具有函式 ‘PyInit_foo()’。接著你可以將 "import foo" 寫入
Python 腳本，Python 將會搜尋 foo.pyd（以及 foo.py、foo.pyc），如果
Python 找到它，將會嘗試呼叫 ‘PyInit_foo()’ 來將它初始化。你並不會將你的
.exe 與 foo.lib 連結 (link)，因為這會導致 Windows 要求 DLL 的存在。

請注意，foo.pyd 的搜尋路徑是 PYTHONPATH，與 Windows 用於搜尋 foo.dll 的
路徑不同。此外，foo.pyd 不需存在即可運行你的程式，然而如果你將程式連結了
一個 dll，則該 dll 會是必要的。當然，如果你想要 ‘import foo’，foo.pyd 就
是必要的。在 DLL 中，連結是以 ‘__declspec(dllexport)’ 在原始碼中被宣告。
在 .pyd 中，連結是在一個可用函式的 list（串列）中被定義。


File: python.info,  Node: 如何將 Python 嵌入 Windows 應用程式中？,  Next: 如何防止編輯器在我的 Python 原始碼中插入 tab？,  Prev: * pyd 檔是否與 DLL 相同？,  Up: 在 Windows 使用 Python 的常見問答集

10.6.6 如何將 Python 嵌入 Windows 應用程式中？
----------------------------------------------

在 Windows 應用程式中嵌入 Python 直譯器的過程可以總結如下：

  1. '不要'直接將 Python 建置到你的 .exe 檔中。在 Windows 上，Python 必
     須是一個 DLL 來處理模組的 import，而那些模組本身也是 DLL。（這是第
     一個未正式記載的關鍵事實。）請改為連結到 ‘python`NN'.dll’；它通常被
     安裝在 ‘C:\Windows\System’ 中。'NN' 是 Python 版本，例如 "33" 就是
     指 Python 3.3。

     你可以透過兩種不同的方式連結到 Python。載入時連結 (load-time
     linking) 表示要連結到 ‘python`NN'.lib’，而執行環境連結 (run-time
     linking) 表示要連結到 ‘python`NN'.dll’。（一般註解：
     ‘python`NN'.lib’ 是 ‘python`NN'.dll’ 相對應的所謂 "import lib"。它
     只會為鏈接器定義符號。）

     執行環境連結大大簡化了連結選項；所有事情都會發生在執行環境。你的程
     式碼必須使用 Windows ‘LoadLibraryEx()’ 常式 (routine) 來載入
     ‘python`NN'.dll’。該程式碼也必須用 Windows ‘GetProcAddress()’ 常式
     所取得的指標，來使用 ‘python`NN'.dll’ 中的（即為 Python C API 的）
     存取常式和資料。對於任何呼叫 Python C API 常式的 C 程式碼，巨集可以
     讓使用這些指標的過程透明化。

  2. 如果你使用 SWIG，則可輕鬆地建立一個 Python 「擴充模組」，該模組將使
     應用程式的資料和 method（方法）可供 Python 使用。SWIG 會為你處理幾
     乎所有的繁瑣細節。結果就是，你會將 C 程式碼連結'到'你的 .exe 檔裡（
     ！）你'不必'建立 DLL 檔，而這也簡化了連結。

  3. SWIG 將建立一個 init 函式（一個 C 函式），其名稱取決於擴充模組的名
     稱。例如，如果模組的名稱是 leo，則該 init 函式會命名為 initleo()。
     如果你使用 SWIG shadow class（類別），則 init 函式會命名為
     initleoc()。這會初始化被 shadow class 所用的大多數隱藏的 helper
     class。

     你可以將步驟 2 中的 C 程式碼連結到 .exe 檔中的原因是，呼叫初始化函
     式就等效於 import 模組進 Python！（這是第二個未正式記載的關鍵事實。
     ）

  4. 簡而言之，你可以使用以下程式碼，以你的擴充模組初始化 Python 直譯器
     。

          #include <Python.h>
          ...
          Py_Initialize();  // Initialize Python.
          initmyAppc();  // Initialize (import) the helper class.
          PyRun_SimpleString("import myApp");  // Import the shadow class.

  5. Python 的 C API 有兩個問題，如果你使用 MSVC（用於建置 pythonNN.dll
     的編譯器）以外的編譯器，這些問題將會變得明顯。

     問題 1：使用 ‘FILE *’ 引數的所謂「非常高階」的函式，在多編譯器
     (multi-compiler) 的環境中會無法作用，因為每個編譯器對 ‘struct FILE’
     的概念不同。從實作的觀點來看，這些都是非常_低階_的函式。

     問題 2：SWIG 在為 void 函式產生包裝函式 (wrapper) 時會產生以下程式
     碼：

          Py_INCREF(Py_None);
          _resultobj = Py_None;
          return _resultobj;

     唉，Py_None 是一個巨集，它會延伸到一個參照，指向 pythonNN.dll 內部
     的一種稱為 _Py_NoneStruct 的複雜資料結構。同樣的，此程式碼在多編譯
     器環境中將會失效。請將此類程式碼替換為：

          return Py_BuildValue("");

     有可能可以使用 SWIG 的 ‘%typemap’ 命令以自動進行程式碼變更，雖然我
     未曾這樣正常運作過（我是一個完全的 SWIG 新手）。

  6. 使用 Python shell 腳本從你的 Windows 應用程式內部建造一個 Python 直
     譯器視窗不是一個好主意；該視窗將會獨立於你的應用程式視窗系統。與其
     如此，你（或 wxPythonWindow class）應該要建立一個「本機」直譯器視窗
     。將該視窗連接到 Python 直譯器是很容易的。你可以將 Python 的 i/o 重
     定向 (redirect) 到可支援讀取和寫入的任何物件，因此你只需要一個包含
     read() 和 write() method 的 Python 物件（在你的擴充模組中被定義）就
     可以了。


File: python.info,  Node: 如何防止編輯器在我的 Python 原始碼中插入 tab？,  Next: 如何在不阻塞的情況下檢查 keypress？,  Prev: 如何將 Python 嵌入 Windows 應用程式中？,  Up: 在 Windows 使用 Python 的常見問答集

10.6.7 如何防止編輯器在我的 Python 原始碼中插入 tab？
-----------------------------------------------------

FAQ 不建議使用 tab，且 Python 風格指南 PEP 8(1) 建議在分散式 Python 程式
碼使用 4 個空格；這也是 Emacs 的 python 模式預設值。

在任何編輯器下，將 tab 和空格混合都是一個壞主意。MSVC 在這方面也是一樣，
且可以輕鬆配置為使用空格：選擇工具 ‣ 選項 ‣ Tabs，然後對於「預設」檔案類
型，將「Tab 大小」和「縮排大小」設定為 4，然後選擇「插入空格」單選鈕。

如果混合 tab 和空格造成前導空白字元出現問題，則 Python 會引發 *note
IndentationError: 74c. 或 *note TabError: 4e9.。你也可以運行 *note
tabnanny: c7. 模組，在批次模式下檢查目錄樹。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0008/


File: python.info,  Node: 如何在不阻塞的情況下檢查 keypress？,  Next: 如何解決遺漏 api-ms-win-crt-runtime-l1-1-0 dll 的錯誤？,  Prev: 如何防止編輯器在我的 Python 原始碼中插入 tab？,  Up: 在 Windows 使用 Python 的常見問答集

10.6.8 如何在不阻塞的情況下檢查 keypress？
------------------------------------------

使用 *note msvcrt: 85. 模組。這是一個標準的 Windows 專用擴充模組。它定義
了一個函式 ‘kbhit()’，該函式會檢查是否出現鍵盤打擊 (keyboard hit)，以及
函式 ‘getch()’，該函式會取得一個字元且不會將其印出。


File: python.info,  Node: 如何解決遺漏 api-ms-win-crt-runtime-l1-1-0 dll 的錯誤？,  Prev: 如何在不阻塞的情況下檢查 keypress？,  Up: 在 Windows 使用 Python 的常見問答集

10.6.9 如何解決遺漏 api-ms-win-crt-runtime-l1-1-0.dll 的錯誤？
--------------------------------------------------------------

使用 Windows 8.1 或更早版本時，若尚未安裝所有的更新，則可能會在 Python
3.5 以上的版本發生這種情況。首先要確保你的作業系統仍受支援並且是最新的，
如果這無法解決問題，請造訪 Microsoft 支援頁面(1)以取得關於手動安裝 C
Runtime 更新的指南。

   ---------- Footnotes ----------

   (1) https://support.microsoft.com/en-us/help/3118401/


File: python.info,  Node: 圖形使用者介面常見問答集,  Next: 「為什麼 Python 被安裝在我的機器上？」常見問答集,  Prev: 在 Windows 使用 Python 的常見問答集,  Up: Python 常見問題

10.7 圖形使用者介面常見問答集
=============================

* Menu:

* 圖形使用者介面 (GUI) 的常見問題: 圖形使用者介面 GUI 的常見問題.
* Python 有哪些 GUI 套件？::
* Tkinter 的問答::


File: python.info,  Node: 圖形使用者介面 GUI 的常見問題,  Next: Python 有哪些 GUI 套件？,  Up: 圖形使用者介面常見問答集

10.7.1 圖形使用者介面 (GUI) 的常見問題
--------------------------------------


File: python.info,  Node: Python 有哪些 GUI 套件？,  Next: Tkinter 的問答,  Prev: 圖形使用者介面 GUI 的常見問題,  Up: 圖形使用者介面常見問答集

10.7.2 Python 有哪些 GUI 套件？
-------------------------------

Python 的標準版本會包含一個 Tcl/Tk 小工具集 (widget set) 的物件導向介面
，稱為 *note tkinter: 3c5d.。這可能是最容易安裝（因為它已包含在 Python 的
大多數二進制發行版本(1)中）和使用的。有關 Tk 的詳細資訊（包含指向原始碼
的指標），請參閱 Tcl/Tk 首頁(2)。Tcl/Tk 在 macOS、Windows 和 Unix 平台上
是完全可攜 (portable) 的。

根據你要使用的平台，還有其他幾種選擇。在 python wiki 上可以找到一份跨平
台的(3)以及各平台專屬的(4) GUI 框架清單。

   ---------- Footnotes ----------

   (1) https://www.python.org/downloads/

   (2) https://www.tcl.tk

   (3) 
https://wiki.python.org/moin/GuiProgramming#Cross-Platform_Frameworks

   (4) 
https://wiki.python.org/moin/GuiProgramming#Platform-specific_Frameworks


File: python.info,  Node: Tkinter 的問答,  Prev: Python 有哪些 GUI 套件？,  Up: 圖形使用者介面常見問答集

10.7.3 Tkinter 的問答
---------------------

* Menu:

* 如何凍結 Tkinter 應用程式？::
* 是否可以在等待 I/O 時處理 Tk 事件？::
* 我無法讓鍵繫結 (key binding) 在 Tkinter 中作用：為什麼？: 我無法讓鍵繫結 key binding 在 Tkinter 中作用：為什麼？.


File: python.info,  Node: 如何凍結 Tkinter 應用程式？,  Next: 是否可以在等待 I/O 時處理 Tk 事件？,  Up: Tkinter 的問答

10.7.3.1 如何凍結 Tkinter 應用程式？
....................................

凍結 (freeze) 是一個能建立獨立應用程式的工具。在凍結 Tkinter 應用程式時
，該應用程式不是真正的獨立，因為該應用程式仍然需要 Tcl 和 Tk 函式庫。

將應用程式與 Tcl 和 Tk 函式庫一併發送是一種解決方法，並在執行環境
(run-time) 使用 ‘TCL_LIBRARY’ 和 ‘TK_LIBRARY’ 環境變數來指向該函式庫。

Various third-party freeze libraries such as py2exe and cx_Freeze have
handling for Tkinter applications built-in.


File: python.info,  Node: 是否可以在等待 I/O 時處理 Tk 事件？,  Next: 我無法讓鍵繫結 key binding 在 Tkinter 中作用：為什麼？,  Prev: 如何凍結 Tkinter 應用程式？,  Up: Tkinter 的問答

10.7.3.2 是否可以在等待 I/O 時處理 Tk 事件？
............................................

在 Windows 以外的平台上是可以的，你甚至不需要執行緒！但是，你必須稍微調
整你的 I/O 程式碼。Tk 具有等效於 Xt 的 ‘XtAddInput()’ 的函式呼叫，它能讓
你記錄一個回呼 (callback) 函式，當 I/O 在一個檔案描述符 (file
descriptor) 上可進行時，該函式將會從 Tk mainloop 被呼叫。請參閱*note
File Handlers: 3c7a.。


File: python.info,  Node: 我無法讓鍵繫結 key binding 在 Tkinter 中作用：為什麼？,  Prev: 是否可以在等待 I/O 時處理 Tk 事件？,  Up: Tkinter 的問答

10.7.3.3 我無法讓鍵繫結 (key binding) 在 Tkinter 中作用：為什麼？
.................................................................

一個經常聽到的抱怨是，儘管事件處理程式 (event handler) 已經*note 繫結:
3c75.到帶有 ‘bind()’ method 的事件，但在按下相應的鍵時，該事件也沒有被處
理。

最常見的原因是，繫結到的小工具並沒有「鍵盤焦點 (keyboard focus)」。請查
看 Tk 說明文件中關於焦點命令的敘述。通常，點擊一個小工具，會讓它得到鍵盤
焦點（但不適用於標籤；請參閱 takefocus 選項）。


File: python.info,  Node: 「為什麼 Python 被安裝在我的機器上？」常見問答集,  Prev: 圖形使用者介面常見問答集,  Up: Python 常見問題

10.8 「為什麼 Python 被安裝在我的機器上？」常見問答集
=====================================================

* Menu:

* 什麼是 Python？: 什麼是 Python？<2>.
* 為什麼 Python 被安裝在我的機器上?::
* 我能夠自行刪除 Python 嗎？::


File: python.info,  Node: 什麼是 Python？<2>,  Next: 為什麼 Python 被安裝在我的機器上?,  Up: 「為什麼 Python 被安裝在我的機器上？」常見問答集

10.8.1 什麼是 Python？
----------------------

Python 是一種程式語言。它被使用於不同種類的應用程式中。因為 Python 屬於
容易學習的語言，它在一些高中和大學課程中被用作介紹程式語言的工具；但它也
被專業的軟體開發人員所使用，例如 Google、美國太空總署與盧卡斯電影公司。

若你想學習更多關於 Python 的知識，可以先從 Python 初學者指引(1)開始閱讀
。

   ---------- Footnotes ----------

   (1) https://wiki.python.org/moin/BeginnersGuide


File: python.info,  Node: 為什麼 Python 被安裝在我的機器上?,  Next: 我能夠自行刪除 Python 嗎？,  Prev: 什麼是 Python？<2>,  Up: 「為什麼 Python 被安裝在我的機器上？」常見問答集

10.8.2 為什麼 Python 被安裝在我的機器上?
----------------------------------------

若你發現曾安裝 Python 於系統中，但不記得何時安裝過，那有可能是透過以下幾
種途徑安裝的。

   * 也許其他使用此電腦的使用者想要學習撰寫程式並且安裝了 Python；你需要
     回想一下誰曾經使用此機器且可能進行安裝。

   * 安裝於機器的第三方應用程式可能以 Python 語言撰寫並且安裝了 Python。
     這樣的應用程式並不少，從 GUI 程式到網路伺服器和管理者腳本都有。

   * 一些安裝 Windows 的機器也被安裝 Python。截至撰寫此文件的當下，我們
     得知 HP 與 Compaq 出廠的機器都預設安裝 Python。顯然的 HP 與 Compaq
     部分的管理工具程式是透過 Python 語言所撰寫。

   * 許多相容於 Unix 系統，例如 macOS 和一些 Linux 發行版本預設安裝
     Python；它被包含在基礎安裝內。


File: python.info,  Node: 我能夠自行刪除 Python 嗎？,  Prev: 為什麼 Python 被安裝在我的機器上?,  Up: 「為什麼 Python 被安裝在我的機器上？」常見問答集

10.8.3 我能夠自行刪除 Python 嗎？
---------------------------------

需要依據 Python 的安裝方式決定。

若有人是有意地安裝 Python，你可自行移除移除它，這不會造成其他影響。
Windows 作業系統中，請於控制台 (Control Panel) 中尋找新增/移除程式來解除
安裝。

若 Python 是透過第三方應用程式安裝時，你也可自行移除，不過該應用程式將無
法正常執行。你應該使用應用程式解除安裝功能而非直接刪除 Python。

當作業系統預設安裝 Python，不建議移除它。對你而言某些工具程式是重要不可
或缺的，若自行移除它，透過 Python 撰寫的工具程式將無法正常執行。重新安裝
整個系統，才能再次解決這些問題。


File: python.info,  Node: 已棄用項目,  Next: 術語表,  Prev: Python 常見問題,  Up: Top

11 已棄用項目
*************

* Menu:

* Python 3.14 中待移除的項目: Python 3 14 中待移除的項目<3>.
* Python 3.15 中待移除的項目: Python 3 15 中待移除的項目<3>.
* Python 3.16 中待移除的項目: Python 3 16 中待移除的項目<2>.
* 未來版本中的待移除項目: 未來版本中的待移除項目<3>.
* C API 的棄用項目::


File: python.info,  Node: Python 3 14 中待移除的項目<3>,  Next: Python 3 15 中待移除的項目<3>,  Up: 已棄用項目

11.1 Python 3.14 中待移除的項目
===============================

   * *note argparse: 5.：‘argparse.BooleanOptionalAction’ 的 'type'、
     'choices' 和 'metavar' 參數已被棄用，將在 3.14 中移除。 (由 Nikita
     Sobolev 於 gh-92248(1) 貢獻。)

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

        * ‘ast.Num’

        * ‘ast.Str’

        * ‘ast.Bytes’

        * ‘ast.NameConstant’

        * ‘ast.Ellipsis’

     請改用 *note ast.Constant: 29a.。（由 Serhiy Storchaka 於
     gh-90953(2) 貢獻。）

   * *note asyncio: 8.：

        * 已棄用並將在 Python 3.14 中移除的 child watcher 類別：*note
          MultiLoopChildWatcher: 29b.、*note FastChildWatcher: 29c.、
          *note AbstractChildWatcher: 29d. 和 *note SafeChildWatcher:
          29e.。 (由 Kumar Aditya 於 gh-94597(3) 貢獻。)

        * *note asyncio.set_child_watcher(): 29f.、*note
          asyncio.get_child_watcher(): 2a0.、*note
          asyncio.AbstractEventLoopPolicy.set_child_watcher(): 2a1. 和
          *note asyncio.AbstractEventLoopPolicy.get_child_watcher():
          2a2. 已被棄用並將在 Python 3.14 中移除。（由 Kumar Aditya 於
          gh-94597(4) 貢獻。）

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

   * *note collections.abc: 17.：已棄用 *note ByteString: 2a4.。請改用
     ‘Sequence’ 或 *note Buffer: 2a5.。在 typing 中使用時，請改用聯集，
     如 ‘bytes | bytearray’，或 *note collections.abc.Buffer: 2a5.。（由
     Shantanu Jain 於 gh-91896(6) 貢獻。）

   * *note email: 32.：已棄用 *note email.utils.localtime(): 2a6. 中的
     'isdst' 參數。（由 Alan Williams 於 gh-72346(7) 貢獻。）

   * *note importlib: 6b.：‘__package__’ 和 ‘__cached__’ 將不再被設定或
     被 import 系統考慮。 (gh-97879(8))

   * *note importlib.abc: 6c. 的已棄用類別：

        * ‘importlib.abc.ResourceReader’

        * ‘importlib.abc.Traversable’

        * ‘importlib.abc.TraversableResources’

     請改用 *note importlib.resources.abc: 70. 類別：

        * *note importlib.resources.abc.Traversable: 1d8.

        * *note importlib.resources.abc.TraversableResources: 2a7.

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

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

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

   * *note pathlib: 93.：已棄用 *note is_relative_to(): 2ab. 和 *note
     relative_to(): 2ac.：額外引數的傳遞已被棄用。

   * *note pkgutil: 97.：*note find_loader(): 2ad. 和 *note
     get_loader(): 2ae. 現在會引發 *note DeprecationWarning: 18b.；請改
     用 *note importlib.util.find_spec(): 2af.。 (由 Nikita Sobolev 於
     gh-97850(12) 貢獻。)

   * *note pty: 9f.：

        * ‘master_open()’：請用 *note pty.openpty(): 2b0.。

        * ‘slave_open()’：請用 *note pty.openpty(): 2b0.。

   * *note sqlite3: ba.：

        * *note version: 2b1. 和 *note version_info: 2b2.。

        * *note execute(): 2b3. 和 *note executemany(): 2b4.，如果使用
          *note named placeholders: 2b5. 且 'parameters' 是序列而不是
          *note dict: 23b.。

        * date 和 datetime 的適配器 (adapter)、date 和 timestamp 轉換器
          (converter)：請參閱 *note sqlite3: ba. 文件以獲得建議的替代方
          案。

   * *note types.CodeType: 2b6.：自 3.10 起，存取 *note co_lnotab: 2b7.
     已在 PEP 626(13) 中被棄用，並計劃在 3.12 中移除，但只在 3.12 中於適
     當時發出 *note DeprecationWarning: 18b.。可能在 3.14 中移除。（由
     Nikita Sobolev 於 gh-101866(14) 貢獻。）

   * *note typing: ed.：自 Python 3.9 起已被棄用的 *note ByteString:
     2b8. 現在在使用時會發出 *note DeprecationWarning: 18b.。

   * *note urllib: f1.：‘urllib.parse.Quoter’ 已被棄用：它並非預期的公開
     API。(由 Gregory P. Smith 於 gh-88168(15) 貢獻。)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/92248

   (2) https://github.com/python/cpython/issues/90953

   (3) https://github.com/python/cpython/issues/94597

   (4) https://github.com/python/cpython/issues/94597

   (5) https://github.com/python/cpython/issues/100160

   (6) https://github.com/python/cpython/issues/91896

   (7) https://github.com/python/cpython/issues/72346

   (8) https://github.com/python/cpython/issues/97879

   (9) https://github.com/python/cpython/issues/93963

   (10) https://github.com/python/cpython/issues/101588

   (11) https://github.com/python/cpython/issues/84559

   (12) https://github.com/python/cpython/issues/97850

   (13) https://peps.python.org/pep-0626/

   (14) https://github.com/python/cpython/issues/101866

   (15) https://github.com/python/cpython/issues/88168


File: python.info,  Node: Python 3 15 中待移除的項目<3>,  Next: Python 3 16 中待移除的項目<2>,  Prev: Python 3 14 中待移除的項目<3>,  Up: 已棄用項目

11.2 Python 3.15 中待移除的項目
===============================

   * *note http.server.CGIHTTPRequestHandler: 281. 將會被移除，連同其相
     關的 ‘--cgi’ 旗標到 ‘python -m http.server’。它已經過時且很少被使用
     。沒有直接的替代方案。'任何東西'都比 CGI 更好的來介接一個帶有請求處
     理器的網頁伺服器。

   * *note locale: 7a.：*note locale.getdefaultlocale(): 2ba. 已在
     Python 3.11 中被棄用，原本計劃在 Python 3.13 中移除 (gh-90817(1))，
     但被延後至 Python 3.15。請改用 *note locale.setlocale(): 2bb.、
     *note locale.getencoding(): 2bc. 和 *note locale.getlocale(): 2bd.。
     (由 Hugo van Kemenade 於 gh-111187(2) 貢獻。)

   * *note pathlib: 93.: *note pathlib.PurePath.is_reserved(): 286. is
     deprecated and scheduled for removal in Python 3.15.  Use *note
     os.path.isreserved(): 208. to detect reserved paths on Windows.

   * *note platform: 98.：*note java_ver(): 287. 已被棄用並將在 3.15 中
     移除。它幾乎沒有被測試過，API 令人困惑並且只對 Jython 支援有用。 (由
     Nikita Sobolev 於 gh-116349(3) 貢獻。)

   * *note threading: d6.：對 *note threading.RLock(): 2be. 傳遞任何引數
     現在已被棄用。C 版本允許任意數量的引數和關鍵字引數，但它們會被忽略
     。Python 版本不允許任何引數。所有引數將在 Python 3.15 中從 *note
     threading.RLock(): 2be. 中移除。 (由 Nikita Sobolev 於 gh-102029(4)
     貢獻。)

   * *note typing.NamedTuple: 291.：

        * 用於建立 ‘NamedTuple’ 類別的未以文件記錄之關鍵字引數語法 (‘NT
          = NamedTuple("NT", x=int)’) 已棄用，並將在 3.15 中被禁止。請改
          用基於類別的語法或函式語法 (functional syntax)。

        * 當使用函式語法來建立 ‘NamedTuple’ 類別時，沒將值傳遞給
          'fields' 參數的方式 (‘NT = NamedTuple("NT")’) 已被棄用，將
          ‘None’ 傳遞給 'fields' 參數（‘NT = NamedTuple("NT", None)’）也
          已被棄用。這兩者將在 Python 3.15 中會被禁止。要建立一個沒有欄
          位的 ‘NamedTuple’ 類別，請使用 ‘class NT(NamedTuple): pass’ 或
          ‘NT = NamedTuple("NT", [])’。

   * *note typing.TypedDict: 146.：當使用函式語法來建立 ‘TypedDict’ 類別
     時，沒將值傳遞給 'fields' 參數的方式（‘TD = TypedDict("TD")’）已被
     棄用，將 ‘None’ 傳遞給 'fields' 參數（‘TD = TypedDict("TD", None)’）
     也已被棄用。這兩者將在 Python 3.15 中會被禁止。要建立一個沒有欄位的
     ‘TypedDict’ 類別，請使用 ‘class TD(TypedDict): pass’ 或 ‘TD =
     TypedDict("TD", {})’。

   * *note wave: fb.：已棄用 *note wave.Wave_read: 297. 和 *note
     wave.Wave_write: 298. 類別的 ‘getmark()’、‘setmark()’ 和
     ‘getmarkers()’ 方法。它們將在 Python 3.15 中被移除。 (由 Victor
     Stinner 於 gh-105096(5) 貢獻。)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/90817

   (2) https://github.com/python/cpython/issues/111187

   (3) https://github.com/python/cpython/issues/116349

   (4) https://github.com/python/cpython/issues/102029

   (5) https://github.com/python/cpython/issues/105096


File: python.info,  Node: Python 3 16 中待移除的項目<2>,  Next: 未來版本中的待移除項目<3>,  Prev: Python 3 15 中待移除的項目<3>,  Up: 已棄用項目

11.3 Python 3.16 中待移除的項目
===============================

   * *note array: 6.：*note array.array: 186. ‘'u'’ 型別 (‘wchar_t’)：請
     改用 ‘'w'’ 型別 (‘Py_UCS4’)。

   * *note builtins: e.：‘~bool’，對 bool 進行位元反轉。

   * *note symtable: c2.：由於並沒有太多關注，已棄用 *note
     symtable.Class.get_methods(): 2c0.。 (由 Bénédikt Tran 於
     gh-119698(1) 貢獻。)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/119698


File: python.info,  Node: 未來版本中的待移除項目<3>,  Next: C API 的棄用項目,  Prev: Python 3 16 中待移除的項目<2>,  Up: 已棄用項目

11.4 未來版本中的待移除項目
===========================

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

   * *note argparse: 5.：已棄用巢狀引數群組和巢狀互斥群組。

   * *note array: 6. 的 ‘'u'’ 格式碼 (gh-57281(1))

   * *note builtins: e.：

        * ‘bool(NotImplemented)’。

        * 產生器：‘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]’）。如
          果數值字面值後立即接 *note and: 2c2.、*note else: 172.、*note
          for: 2c3.、*note if: 2c4.、*note in: 2c5.、*note is: 2c6. 和
          *note or: 2c7. 之一的關鍵字，則會引發語法警告。在未來版本中，
          它將被更改為語法錯誤。(gh-87999(2))

        * ‘__index__()’ 和 ‘__int__()’ 方法回傳非 int 型別的支援：這些方
          法將需要回傳 *note int: 23c. 的嚴格子類別實例。

        * 回傳 *note float: 2c8. 嚴格子類別 ‘__float__()’ 方法的支援：這
          些方法將需要回傳 *note float: 2c8. 的實例。

        * 回傳 *note complex: 2c9. 嚴格子類別 ‘__complex__()’ 方法的支援
          ：這些方法將需要回傳 *note complex: 2c9. 的實例。

        * 將 ‘int()’ 委派給 ‘__trunc__()’ 方法。

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

   * *note calendar: 10.：‘calendar.January’ 和 ‘calendar.February’ 常數
     已被棄用並被 *note calendar.JANUARY: 2ca. 和 *note
     calendar.FEBRUARY: 2cb. 取代。 (由 Prince Roshan 於 gh-103636(4) 貢
     獻。)

   * *note codeobject.co_lnotab: 2b7.：請改用 *note
     codeobject.co_lines(): 2cc. 方法。

   * *note datetime: 28.：

        * *note utcnow(): 2cd.：請改用
          ‘datetime.datetime.now(tz=datetime.UTC)’。

        * *note utcfromtimestamp(): 2ce.：請改用
          ‘datetime.datetime.fromtimestamp(timestamp, tz=datetime.UTC)’。

   * *note gettext: 59.：複數值必須是整數。

   * *note importlib: 6b.：

        * ‘load_module()’ method：請改用 ‘exec_module()’。

        * *note cache_from_source(): 2cf. 'debug_override' 參數已被棄用
          ：請改用 'optimization' 參數。

   * *note importlib.metadata: 6e.：

        * ‘EntryPoints’ 元組介面。

        * 回傳值上的隱式 ‘None’。

   * *note logging: 7b.: the ‘warn()’ method has been deprecated since
     Python 3.3, use *note warning(): 2d0. instead.

   * *note mailbox: 7f.：已棄用 StringIO 輸入和文本模式，請改用 BytesIO
     和二進位模式。

   * *note os: 91.：在多執行緒行程中呼叫 *note os.register_at_fork():
     2d1.。

   * ‘pydoc.ErrorDuringImport’：'exc_info' 參數的元組值已被棄用，請用例
     外實例。

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

   * ‘sre_compile’、‘sre_constants’ 和 ‘sre_parse’ 模組。

   * *note shutil: b3.：*note rmtree(): 2d2. 的 'onerror' 參數在 Python
     3.12 中已被棄用；請改用 'onexc' 參數。

   * *note ssl: bb. 選項和協定：

        * 不帶協定引數的 *note ssl.SSLContext: 276. 已被棄用。

        * *note ssl.SSLContext: 276.：*note set_npn_protocols(): 2d3. 和
          ‘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’

   * *note sysconfig.is_python_build(): 2d4. 的 'check_home' 參數已被棄
     用並被忽略。

   * *note threading: d6. 方法：

        * ‘threading.Condition.notifyAll()’：請用 *note notify_all():
          2d5.。

        * ‘threading.Event.isSet()’：請用 *note is_set(): 2d6.。

        * ‘threading.Thread.isDaemon()’、*note
          threading.Thread.setDaemon(): 2d7.：請用 *note
          threading.Thread.daemon: 2d8. 屬性。

        * ‘threading.Thread.getName()’、*note
          threading.Thread.setName(): 2d9.：請用 *note
          threading.Thread.name: 2da. 屬性。

        * ‘threading.currentThread()’：請用 *note
          threading.current_thread(): 2db.。

        * ‘threading.activeCount()’：請用 *note
          threading.active_count(): 2dc.。

   * *note typing.Text: 2dd. (gh-92332(6))。

   * *note unittest.IsolatedAsyncioTestCase: 2de.：從測試案例中回傳非
     ‘None’ 的值已被棄用。

   * *note urllib.parse: f3. 已棄用函式：請改用 *note urlparse(): 2df.。

        * ‘splitattr()’

        * ‘splithost()’

        * ‘splitnport()’

        * ‘splitpasswd()’

        * ‘splitport()’

        * ‘splitquery()’

        * ‘splittag()’

        * ‘splittype()’

        * ‘splituser()’

        * ‘splitvalue()’

        * ‘to_bytes()’

   * *note urllib.request: f4.：呼叫請求的 *note URLopener: 2e0. 和
     *note FancyURLopener: 2e1. 風格已被棄用。請改用更新的 *note
     urlopen(): 275. 函式和方法。

   * *note wsgiref: 100.：‘SimpleHandler.stdout.write()’ 不應該進行部分
     寫入。

   * *note xml.etree.ElementTree: 10c.：已棄用對 *note Element: 2e2. 的
     真值測試。在未來版本中，它將始終回傳 ‘True’。請改用明確的
     ‘len(elem)’ 或 ‘elem is not None’ 測試。

   * *note zipimport.zipimporter.load_module(): 2e3. 已被棄用：請改用
     *note exec_module(): 2e4.。

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/issues/57281

   (2) https://github.com/python/cpython/issues/87999

   (3) https://github.com/python/cpython/issues/109218

   (4) https://github.com/python/cpython/issues/103636

   (5) https://github.com/python/cpython/issues/91760

   (6) https://github.com/python/cpython/issues/92332


File: python.info,  Node: C API 的棄用項目,  Prev: 未來版本中的待移除項目<3>,  Up: 已棄用項目

11.5 C API 的棄用項目
=====================

* Menu:

* Python 3.14 中待移除的項目: Python 3 14 中待移除的項目<4>.
* Python 3.15 中待移除的項目: Python 3 15 中待移除的項目<4>.
* 未來版本中的待移除項目: 未來版本中的待移除項目<4>.


File: python.info,  Node: Python 3 14 中待移除的項目<4>,  Next: Python 3 15 中待移除的項目<4>,  Up: C API 的棄用項目

11.5.1 Python 3.14 中待移除的項目
---------------------------------

   * *note PyDictObject: 38c. 中的 ‘ma_version_tag’ 欄位，用於擴充模組 (
     PEP 699(1)；gh-101193(2))。

   * 使用可變基底建立*note 不可變型別: 38d. (gh-95388(3))。

   * 設定 Python 初始化的函式，Python 3.11 中已被棄用：

        * ‘PySys_SetArgvEx()’：請改以 *note PyConfig.argv: 38e. 設定。

        * ‘PySys_SetArgv()’：請改以 *note PyConfig.argv: 38e. 設定。

        * ‘Py_SetProgramName()’：請改以 *note PyConfig.program_name:
          38f. 設定。

        * ‘Py_SetPythonHome()’：請改以 *note PyConfig.home: 386. 設定。

     *note Py_InitializeFromConfig(): 390. API 應該與 *note PyConfig:
     371. 一起使用。

   * 全域設定變數：

        * *note Py_DebugFlag: 391.：請改用 *note PyConfig.parser_debug:
          392.。

        * *note Py_VerboseFlag: 393.：請改用 *note PyConfig.verbose:
          394.。

        * *note Py_QuietFlag: 395.：請改用 *note PyConfig.quiet: 396.。

        * *note Py_InteractiveFlag: 397.：請改用 *note
          PyConfig.interactive: 398.。

        * *note Py_InspectFlag: 399.：請改用 *note PyConfig.inspect:
          39a.。

        * *note Py_OptimizeFlag: 39b.：請改用 *note
          PyConfig.optimization_level: 39c.。

        * *note Py_NoSiteFlag: 39d.：請改用 *note PyConfig.site_import:
          39e.。

        * *note Py_BytesWarningFlag: 39f.：請改用 *note
          PyConfig.bytes_warning: 3a0.。

        * *note Py_FrozenFlag: 3a1.：請改用 *note
          PyConfig.pathconfig_warnings: 3a2.。

        * *note Py_IgnoreEnvironmentFlag: 3a3.：請改用 *note
          PyConfig.use_environment: 3a4.。

        * *note Py_DontWriteBytecodeFlag: 3a5.：請改用 *note
          PyConfig.write_bytecode: 3a6.。

        * *note Py_NoUserSiteDirectory: 3a7.：請改用 *note
          PyConfig.user_site_directory: 3a8.。

        * *note Py_UnbufferedStdioFlag: 3a9.：請改用 *note
          PyConfig.buffered_stdio: 3aa.。

        * *note Py_HashRandomizationFlag: 3ab.：請改用 *note
          PyConfig.use_hash_seed: 3ac. 和 *note PyConfig.hash_seed:
          3ad.。

        * *note Py_IsolatedFlag: 3ae.：請改用 *note PyConfig.isolated:
          3af.。

        * *note Py_LegacyWindowsFSEncodingFlag: 3b0.：請改用 *note
          PyPreConfig.legacy_windows_fs_encoding: 3b1.。

        * *note Py_LegacyWindowsStdioFlag: 3b2.：請改用 *note
          PyConfig.legacy_windows_stdio: 36f.。

        * ‘Py_FileSystemDefaultEncoding’：請改用 *note
          PyConfig.filesystem_encoding: 3b3.。

        * ‘Py_HasFileSystemDefaultEncoding’：請改用 *note
          PyConfig.filesystem_encoding: 3b3.。

        * ‘Py_FileSystemDefaultEncodeErrors’：請改用 *note
          PyConfig.filesystem_errors: 3b4.。

        * ‘Py_UTF8Mode’：請改用 *note PyPreConfig.utf8_mode: 3b5.。（請
          見 *note Py_PreInitialize(): 3b6.）

     *note Py_InitializeFromConfig(): 390. API 應該與 *note PyConfig:
     371. 一起使用。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0699/

   (2) https://github.com/python/cpython/issues/101193

   (3) https://github.com/python/cpython/issues/95388


File: python.info,  Node: Python 3 15 中待移除的項目<4>,  Next: 未來版本中的待移除項目<4>,  Prev: Python 3 14 中待移除的項目<4>,  Up: C API 的棄用項目

11.5.2 Python 3.15 中待移除的項目
---------------------------------

   * ‘libmpdecimal’ 的打包副本 (bundled copy)。

   * *note PyImport_ImportModuleNoBlock(): 388.：請改用 *note
     PyImport_ImportModule(): 389.。

   * *note PyWeakref_GET_OBJECT(): 38a.: use *note PyWeakref_GetRef():
     2f0. instead.

   * *note PyWeakref_GetObject(): 2f1.: use *note PyWeakref_GetRef():
     2f0. instead.

   * ‘Py_UNICODE_WIDE’ type：請改用 ‘wchar_t’。

   * *note Py_UNICODE: 3b8. type：請改用 ‘wchar_t’。

   * Python 初始化函式：

        * *note PySys_ResetWarnOptions(): 37a.：請改為清除 *note
          sys.warnoptions: 37b. 和 ‘warnings.filters’。

        * *note Py_GetExecPrefix(): 37c.：請改用 *note sys.exec_prefix:
          37d.。

        * *note Py_GetPath(): 37e.：請改用 *note sys.path: 37f.。

        * *note Py_GetPrefix(): 380.：請改用 *note sys.prefix: 381.。

        * *note Py_GetProgramFullPath(): 382.：請改用 *note
          sys.executable: 383.。

        * *note Py_GetProgramName(): 384.：請改用 *note sys.executable:
          383.。

        * *note Py_GetPythonHome(): 385.：請改用 *note PyConfig.home:
          386. 或 *note PYTHONHOME: 387. 環境變數。


File: python.info,  Node: 未來版本中的待移除項目<4>,  Prev: Python 3 15 中待移除的項目<4>,  Up: C API 的棄用項目

11.5.3 未來版本中的待移除項目
-----------------------------

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

   * *note Py_TPFLAGS_HAVE_FINALIZE: 3ba.：自 Python 3.8 起不再需要

   * *note PyErr_Fetch(): 3bb.：請改用 *note PyErr_GetRaisedException():
     3bc.。

   * *note PyErr_NormalizeException(): 3bd.：請改用 *note
     PyErr_GetRaisedException(): 3bc.。

   * *note PyErr_Restore(): 3be.：請改用 *note
     PyErr_SetRaisedException(): 3bf.。

   * *note PyModule_GetFilename(): 3c0.：請改用 *note
     PyModule_GetFilenameObject(): 3c1.。

   * *note PyOS_AfterFork(): 3c2.：請改用 *note PyOS_AfterFork_Child():
     3c3.。

   * *note PySlice_GetIndicesEx(): 3c4.：請改用 *note PySlice_Unpack():
     3c5. 和 *note PySlice_AdjustIndices(): 3c6.。

   * ‘PyUnicode_AsDecodedObject()’：請改用 *note PyCodec_Decode(): 3c7.。

   * ‘PyUnicode_AsDecodedUnicode()’：請改用 *note PyCodec_Decode():
     3c7.。

   * ‘PyUnicode_AsEncodedObject()’：請改用 *note PyCodec_Encode(): 3c8.。

   * ‘PyUnicode_AsEncodedUnicode()’：請改用 *note PyCodec_Encode():
     3c8.。

   * *note PyUnicode_READY(): 3c9.：自 Python 3.12 起不再需要

   * ‘PyErr_Display()’：請改用 *note PyErr_DisplayException(): 3ca.。

   * ‘_PyErr_ChainExceptions()’：請改用 ‘_PyErr_ChainExceptions1’。

   * ‘PyBytesObject.ob_shash’ 成員：請改為呼叫 *note PyObject_Hash():
     3cb.。

   * ‘PyDictObject.ma_version_tag’ 成員。

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

        * *note PyThread_create_key(): 3cc.：請改用 *note
          PyThread_tss_alloc(): 3cd.。

        * *note PyThread_delete_key(): 3ce.：請改用 *note
          PyThread_tss_free(): 3cf.。

        * *note PyThread_set_key_value(): 3d0.：請改用 *note
          PyThread_tss_set(): 3d1.。

        * *note PyThread_get_key_value(): 3d2.：請改用 *note
          PyThread_tss_get(): 3d3.。

        * *note PyThread_delete_key_value(): 3d4.：請改用 *note
          PyThread_tss_delete(): 3d5.。

        * *note PyThread_ReInitTLS(): 3d6.：自 Python 3.7 起不再需要。


File: python.info,  Node: 術語表,  Next: 關於這些說明文件,  Prev: 已棄用項目,  Up: Top

12 術語表
*********

‘>>>’

     The default Python prompt of the *note interactive: 14d. shell.
     Often seen for code examples which can be executed interactively in
     the interpreter.

‘...’

     可以表示：

        * The default Python prompt of the *note interactive: 14d. shell
          when entering the code for an indented code block, when within
          a pair of matching left and right delimiters (parentheses,
          square brackets, curly braces or triple quotes), or after
          specifying a decorator.

        * 內建常數 *note Ellipsis: 2062.。

abstract base class（抽象基底類別）

     抽象基底類別（又稱為 ABC）提供了一種定義介面的方法，作為 *note
     duck-typing: 4f40.（鴨子型別）的補充。其他類似的技術，像是 *note
     hasattr(): 479.，則顯得笨拙或是帶有細微的錯誤（例如使用*note
     魔術方法 (magic method): 1e3b.）。ABC 採用虛擬的 subclass（子類別）
     ，它們並不繼承自另一個 class（類別），但仍可被 *note isinstance():
     3e8. 及 *note issubclass(): 765. 辨識；請參閱 *note abc: 4. 模組的
     說明文件。Python 有許多內建的 ABC，用於資料結構（在 *note
     collections.abc: 17. 模組）、數字（在 *note numbers: 8e. 模組）、串
     流（在 *note io: 73. 模組）及 import 尋檢器和載入器（在 *note
     importlib.abc: 6c. 模組）。你可以使用 *note abc: 4. 模組建立自己的
     ABC。

annotation（註釋）

     一個與變數、class 屬性、函式的參數或回傳值相關聯的標籤。照慣例，它
     被用來作為 *note type hint: 1e58.（型別提示）。

     在執行環境 (runtime)，區域變數的註釋無法被存取，但全域變數、class 屬
     性和函式的註解，會分別被儲存在模組、class 和函式的
     ‘__annotations__’ 特殊屬性中。

     請參閱 *note variable annotation: cfc.、*note function annotation:
     1b3b.、 PEP 484(1) 和 PEP 526(2)，這些章節皆有此功能的說明。關於註
     釋的最佳實踐方法也請參閱 *note 註釋 (annotation) 最佳實踐: 77d.。

argument（引數）

     呼叫函式時被傳遞給 *note function: 1f2f.（或 *note method: 4f41.）
     的值。引數有兩種：

        * '關鍵字引數 (keyword argument)'：在函式呼叫中，以識別字（
          identifier，例如 ‘name=’）開頭的引數，或是以 ‘**’ 後面
          dictionary（字典）內的值被傳遞的引數。例如，‘3’ 和 ‘5’ 都是以
          下 *note complex(): 2c9. 呼叫中的關鍵字引數：

               complex(real=3, imag=5)
               complex(**{'real': 3, 'imag': 5})

        * '位置引數 (positional argument)'：不是關鍵字引數的引數。位置引
          數可在一個引數列表的起始處出現，和（或）作為 ‘*’ 之後的 *note
          iterable: 11bf.（可疊代物件）中的元素被傳遞。例如，‘3’ 和 ‘5’
          都是以下呼叫中的位置引數：

               complex(3, 5)
               complex(*(3, 5))

     引數會被指定給函式主體中的附名區域變數。關於支配這個指定過程的規則
     ，請參閱*note Calls: d23.章節。在語法上，任何運算式都可以被用來表示
     一個引數；其評估值會被指定給區域變數。

     另請參閱術語表的 *note parameter: 1dee.（參數）條目、常見問題中的
     *note 引數和參數之間的差異: 4e84.，以及 PEP 362(3)。

asynchronous context manager（非同步情境管理器）

     一個可以控制 *note async with: 57a. 陳述式中所見環境的物件，而它是
     透過定義 *note __aenter__(): 1ea6. 和 *note __aexit__(): 151e.
     method（方法）來控制的。由 PEP 492(4) 引入。

asynchronous generator（非同步產生器）

     一個會回傳 *note asynchronous generator iterator: 4191.（非同步產生
     器疊代器）的函式。它看起來像一個以 *note async def: 575. 定義的協程
     函式 (coroutine function)，但不同的是它包含了 *note yield: 971. 運
     算式，能生成一系列可用於 *note async for: a4e. 迴圈的值。

     這個術語通常用來表示一個非同步產生器函式，但在某些情境中，也可能是
     表示'非同步產生器疊代器 (asynchronous generator iterator)'。萬一想
     表達的意思不夠清楚，那就使用完整的術語，以避免歧義。

     一個非同步產生器函式可能包含 *note await: 19f. 運算式，以及 *note
     async for: a4e. 和 *note async with: 57a. 陳述式。

asynchronous generator iterator（非同步產生器疊代器）

     一個由 *note asynchronous generator: 1f14.（非同步產生器）函式所建
     立的物件。

     這是一個 *note asynchronous iterator: 191.（非同步疊代器），當它以
     *note __anext__(): 1dfa. method 被呼叫時，會回傳一個可等待物件
     (awaitable object)，該物件將執行非同步產生器的函式主體，直到遇到下
     一個 *note yield: 971. 運算式。

     每個 *note yield: 971. 會暫停處理程序，並記住位置執行狀態（包括區域
     變數及擱置中的 try 陳述式）。當'非同步產生器疊代器'以另一個被 *note
     __anext__(): 1dfa. 回傳的可等待物件有效地回復時，它會從停止的地方繼
     續執行。請參閱 PEP 492(5) 和 PEP 525(6)。

asynchronous iterable（非同步可疊代物件）

     一個物件，它可以在 *note async for: a4e. 陳述式中被使用。必須從它的
     *note __aiter__(): ba2. method 回傳一個 *note asynchronous
     iterator: 191.（非同步疊代器）。由 PEP 492(7) 引入。

asynchronous iterator（非同步疊代器）

     一個實作 *note __aiter__(): ba2. 和 *note __anext__(): 1dfa. method
     的物件。*note __anext__(): 1dfa. 必須回傳一個 *note awaitable:
     193.（可等待物件）。*note async for: a4e. 會解析非同步疊代器的
     *note __anext__(): 1dfa. method 所回傳的可等待物件，直到它引發
     *note StopAsyncIteration: 1933. 例外。由 PEP 492(8) 引入。

attribute（屬性）

     一個與某物件相關聯的值，該值大多能透過使用點分隔運算式 (dotted
     expression) 的名稱被參照。例如，如果物件 'o' 有一個屬性 'a'，則該屬
     性能以 'o.a' 被參照。

     如果一個物件允許，給予該物件一個名稱不是由*note Identifiers and
     keywords: 1d86.所定義之識別符 (identifier) 的屬性是有可能的，例如使
     用 *note setattr(): 2032.。像這樣的屬性將無法使用點分隔運算式來存取
     ，而是需要使用 *note getattr(): b78. 來取得它。

awaitable（可等待物件）

     一個可以在 *note await: 19f. 運算式中被使用的物件。它可以是一個
     *note coroutine: 438.（協程），或是一個有 *note __await__(): 1e9d.
     method 的物件。另請參閱 PEP 492(9)。

BDFL

     Benevolent Dictator For Life（終身仁慈獨裁者），又名 Guido van
     Rossum(10)，Python 的創造者。

binary file（二進位檔案）

     一個能夠讀取和寫入 *note bytes-like objects: cd4.（類位元組串物件）
     的 *note file object: 115b.（檔案物件）。二進位檔案的例子有：以二進
     位模式（‘'rb'’、‘'wb'’ 或 ‘'rb+'’）開啟的檔案、*note
     sys.stdin.buffer: 4e2.、*note sys.stdout.buffer: a79.，以及 *note
     io.BytesIO: e46. 和 *note gzip.GzipFile: 354. 實例。

     另請參閱 *note text file: 1b8a.（文字檔案），它是一個能夠讀取和寫入
     *note str: 3f2. 物件的檔案物件。

borrowed reference（借用參照）

     在 Python 的 C API 中，借用參照是一個對物件的參照，其中使用該物件的
     程式碼並不擁有這個參照。如果該物件被銷毀，它會成為一個迷途指標
     (dangling pointer)。例如，一次垃圾回收 (garbage collection) 可以移
     除對物件的最後一個 *note strong reference: 2ee.（強參照），而將該物
     件銷毀。

     對 *note borrowed reference: 2ef. 呼叫 *note Py_INCREF(): 514. 以將
     它原地 (in-place) 轉換為 *note strong reference: 2ee. 是被建議的做
     法，除非該物件不能在最後一次使用借用參照之前被銷毀。*note
     Py_NewRef(): 83e. 函式可用於建立一個新的 *note strong reference:
     2ee.。

bytes-like object（類位元組串物件）

     一個支援*note 緩衝協定 (Buffer Protocol): 367.且能夠匯出 C-*note
     contiguous: 2103. 緩衝區的物件。這包括所有的 *note bytes: 1a5.、
     *note bytearray: 4e3. 和 *note array.array: 186. 物件，以及許多常見
     的 *note memoryview: 40f. 物件。類位元組串物件可用於處理二進位資料
     的各種運算；這些運算包括壓縮、儲存至二進位檔案和透過 socket（插座）
     發送。

     有些運算需要二進位資料是可變的。說明文件通常會將這些物件稱為「可讀
     寫的類位元組串物件」。可變緩衝區的物件包括 *note bytearray: 4e3.，
     以及 *note bytearray: 4e3. 的 *note memoryview: 40f.。其他的運算需
     要讓二進位資料被儲存在不可變物件（「唯讀的類位元組串物件」）中；這
     些物件包括 *note bytes: 1a5.，以及 *note bytes: 1a5. 物件的 *note
     memoryview: 40f.。

bytecode（位元組碼）

     Python 的原始碼會被編譯成位元組碼，它是 Python 程式在 CPython 直譯
     器中的內部表示法。該位元組碼也會被暫存在 ‘.pyc’ 檔案中，以便第二次
     執行同一個檔案時能夠更快速（可以不用從原始碼重新編譯為位元組碼）。
     這種「中間語言 (intermediate language)」據說是運行在一個 *note
     virtual machine: 3334.（虛擬機器）上，該虛擬機器會執行與每個位元組
     碼對應的機器碼 (machine code)。要注意的是，位元組碼理論上是無法在不
     同的 Python 虛擬機器之間運作的，也不能在不同版本的 Python 之間保持
     穩定。

     位元組碼的指令列表可以在 *note dis 模組: 556.的說明文件中找到。

callable（可呼叫物件）

     一個 callable 是可以被呼叫的物件，呼叫時可能以下列形式帶有一組引數
     （請見 *note argument: 3ef.）：

          callable(argument1, argument2, argumentN)

     一個 *note function: 1f2f. 與其延伸的 *note method: 4f41. 都是
     callable。一個有實作 *note __call__(): 4fe. 方法的 class 之實例也是
     個 callable。

callback（回呼）

     作為引數被傳遞的一個副程式 (subroutine) 函式，會在未來的某個時間點
     被執行。

class（類別）

     一個用於建立使用者定義物件的模板。Class 的定義通常會包含 method 的
     定義，這些 method 可以在 class 的實例上進行操作。

class variable（類別變數）

     一個在 class 中被定義，且應該只能在 class 層次（意即不是在 class 的
     實例中）被修改的變數。

complex number（複數）

     一個我們熟悉的實數系統的擴充，在此所有數字都會被表示為一個實部和一
     個虛部之和。虛數就是虛數單位（‘-1’ 的平方根）的實數倍，此單位通常在
     數學中被寫為 ‘i’，在工程學中被寫為 ‘j’。Python 內建了對複數的支援，
     它是用後者的記法來表示複數；虛部會帶著一個後綴的 ‘j’ 被編寫，例如
     ‘3+1j’。若要將 *note math: 81. 模組內的工具等效地用於複數，請使用
     *note cmath: 11. 模組。複數的使用是一個相當進階的數學功能。如果你沒
     有察覺到對它們的需求，那麼幾乎能確定你可以安全地忽略它們。

context manager（情境管理器）

     一個可以控制 *note with: 577. 陳述式中所見環境的物件，而它是透過定
     義 *note __enter__(): 56c. 和 *note __exit__(): 1293. method 來控制
     的。請參閱 PEP 343(11)。

context variable（情境變數）

     一個變數，其值可以根據上下文的情境而有所不同。這類似執行緒區域儲存
     區 (Thread-Local Storage)，在其中，一個變數在每個執行緒可能具有不同
     的值。然而，關於情境變數，在一個執行緒中可能會有多個情境，而情境變
     數的主要用途，是在並行的非同步任務 (concurrent asynchronous task) 中
     ，對於變數狀態的追蹤。請參閱 *note contextvars: 1d.。

contiguous（連續的）

     如果一個緩衝區是 'C-contiguous' 或是 'Fortran contiguous'，則它會確
     切地被視為是連續的。零維 (zero-dimensional) 的緩衝區都是 C 及
     Fortran contiguous。在一維 (one-dimensional) 陣列中，各項目必須在記
     憶體中彼此相鄰地排列，而其索引順序是從零開始遞增。在多維的
     (multidimensional) C-contiguous 陣列中，按記憶體位址的順序訪問各個
     項目時，最後一個索引的變化最快。然而，在 Fortran contiguous 陣列中
     ，第一個索引的變化最快。

coroutine（協程）

     協程是副程式 (subroutine) 的一種更為廣義的形式。副程式是在某個時間
     點被進入並在另一個時間點被退出。協程可以在許多不同的時間點被進入、
     退出和回復。它們能夠以 *note async def: 575. 陳述式被實作。另請參閱
     PEP 492(12)。

coroutine function（協程函式）

     一個回傳 *note coroutine: 438.（協程）物件的函式。一個協程函式能以
     *note async def: 575. 陳述式被定義，並可能會包含 *note await: 19f.、
     *note async for: a4e. 和 *note async with: 57a. 關鍵字。這些關鍵字
     由 PEP 492(13) 引入。

CPython

     Python 程式語言的標準實作 (canonical implementation)，被發布在
     python.org(14) 上。「CPython」這個術語在必要時被使用，以區分此實作
     與其它語言的實作，例如 Jython 或 IronPython。

decorator（裝飾器）

     一個函式，它會回傳另一個函式，通常它會使用 ‘@wrapper’ 語法，被應用
     為一種函式的變換 (function transformation)。裝飾器的常見範例是
     *note classmethod(): 14a. 和 *note staticmethod(): 358.。

     裝飾器語法只是語法糖。以下兩個函式定義在語義上是等效的：

          def f(arg):
              ...
          f = staticmethod(f)

          @staticmethod
          def f(arg):
              ...

     Class 也存在相同的概念，但在那裡比較不常用。關於裝飾器的更多內容，
     請參閱*note 函式定義: 1b3a.和 *note class 定義: 126a.的說明文件。

descriptor（描述器）

     任何定義了 *note __get__(): 16c3.、*note __set__(): 1e3f. 或 *note
     __delete__(): 14fc. method 的物件。當一個 class 屬性是一個描述器時
     ，它的特殊連結行為會在屬性查找時被觸發。通常，使用 'a.b' 來取得、設
     定或刪除某個屬性時，會在 'a' 的 class 字典中查找名稱為 'b' 的物件，
     但如果 'b' 是一個描述器，則相對應的描述器 method 會被呼叫。對描述器
     的理解是深入理解 Python 的關鍵，因為它們是許多功能的基礎，這些功能
     包括函式、method、屬性 (property)、class method、靜態 method，以及
     對 super class（父類別）的參照。

     關於描述器 method 的更多資訊，請參閱*note Implementing Descriptors:
     bf6.或*note 描述器使用指南: 145a.。

dictionary（字典）

     一個關聯陣列 (associative array)，其中任意的鍵會被映射到值。鍵可以
     是任何帶有 *note __hash__(): a9e. 和 *note __eq__(): a9d. method 的
     物件。在 Perl 中被稱為雜湊 (hash)。

dictionary comprehension（字典綜合運算）

     一種緊密的方法，用來處理一個可疊代物件中的全部或部分元素，並將處理
     結果以一個字典回傳。‘results = {n: n ** 2 for n in range(10)}’ 會產
     生一個字典，它包含了鍵 ‘n’ 映射到值 ‘n ** 2’。請參閱*note Displays
     for lists, sets and dictionaries: 574.。

dictionary view（字典檢視）

     從 *note dict.keys(): 771.、*note dict.values(): 772. 及 *note
     dict.items(): 773. 回傳的物件被稱為字典檢視。它們提供了字典中項目的
     動態檢視，這表示當字典有變動時，該檢視會反映這些變動。若要強制將字
     典檢視轉為完整的 list（串列），須使用 ‘list(dictview)’。請參閱*note
     字典視圖物件: 2120.。

docstring（說明字串）

     一個在 class、函式或模組中，作為第一個運算式出現的字串文本。雖然它
     在套件執行時會被忽略，但它會被編譯器辨識，並被放入所屬 class、函式
     或模組的 ‘__doc__’ 屬性中。由於說明字串可以透過內省 (introspection)
     來瀏覽，因此它是物件的說明文件存放的標準位置。

duck-typing（鴨子型別）

     一種程式設計風格，它不是藉由檢查一個物件的型別來確定它是否具有正確
     的介面；取而代之的是，method 或屬性會單純地被呼叫或使用。（「如果它
     看起來像一隻鴨子而且叫起來像一隻鴨子，那麼它一定是一隻鴨子。」）因
     為強調介面而非特定型別，精心設計的程式碼能讓多形替代 (polymorphic
     substitution) 來增進它的靈活性。鴨子型別要避免使用 *note type():
     cef. 或 *note isinstance(): 3e8. 進行測試。（但是請注意，鴨子型別可
     以用*note 抽象基底類別 (abstract base class): 114e. 來補充。）然而
     ，它通常會採用 *note hasattr(): 479. 測試，或是 *note EAFP: 2a66. 程
     式設計風格。

EAFP

     Easier to ask for forgiveness than permission.（請求寬恕比請求許可
     更容易。）這種常見的 Python 編碼風格會先假設有效的鍵或屬性的存在，
     並在該假設被推翻時再捕獲例外。這種乾淨且快速的風格，其特色是存在許
     多的 *note try: 68c. 和 *note except: 171. 陳述式。該技術與許多其他
     語言（例如 C）常見的 *note LBYL: 4f48. 風格形成了對比。

expression（運算式）

     一段可以被評估並求值的語法。換句話說，一個運算式就是文字、名稱、屬
     性存取、運算子或函式呼叫等運算式元件的累積，而這些元件都能回傳一個
     值。與許多其他語言不同的是，並非所有的 Python 語言構造都是運算式。
     另外有一些 *note statement: 265e.（陳述式）不能被用作運算式，例如
     *note while: 1b0b.。賦值 (assignment) 也是陳述式，而不是運算式。

extension module（擴充模組）

     一個以 C 或 C++ 編寫的模組，它使用 Python 的 C API 來與核心及使用者
     程式碼進行互動。

f-string（f 字串）

     以 ‘'f'’ 或 ‘'F'’ 為前綴的字串文本通常被稱為「f 字串」，它是*note
     格式化的字串文本: 94d.的縮寫。另請參閱 PEP 498(15)。

file object（檔案物件）

     一個讓使用者透過檔案導向 (file-oriented) API（如 ‘read()’ 或
     ‘write()’ 等 method）來操作底層資源的物件。根據檔案物件被建立的方式
     ，它能夠協調對真實磁碟檔案或是其他類型的儲存器或通訊裝置（例如標準
     輸入／輸出、記憶體內緩衝區、socket（插座）、管線 (pipe) 等）的存取
     。檔案物件也被稱為'類檔案物件 (file-like object)' 或'串流
     (stream)'。

     實際上，有三種檔案物件：原始的*note 二進位檔案: 1b8b.、緩衝的*note
     二進位檔案: 1b8b.和*note 文字檔案: 1b8a.。它們的介面在 *note io:
     73. 模組中被定義。建立檔案物件的標準方法是使用 *note open(): 4c0. 函
     式。

file-like object（類檔案物件）

     *note file object: 115b.（檔案物件）的同義字。

filesystem encoding and error handler（檔案系統編碼和錯誤處理函式）

     Python 所使用的一種編碼和錯誤處理函式，用來解碼來自作業系統的位元組
     ，以及將 Unicode 編碼到作業系統。

     檔案系統編碼必須保證能成功解碼所有小於 128 的位元組。如果檔案系統編
     碼無法提供此保證，則 API 函式會引發 *note UnicodeError: 123a.。

     *note sys.getfilesystemencoding(): c00. 和 *note
     sys.getfilesystemencodeerrors(): c8d. 函式可用於取得檔案系統編碼和
     錯誤處理函式。

     *note filesystem encoding and error handler: 4e0.（檔案系統編碼和錯
     誤處理函式）會在 Python 啟動時由 *note PyConfig_Read(): 734. 函式來
     配置：請參閱 *note filesystem_encoding: 3b3.，以及 *note PyConfig:
     371. 的成員 *note filesystem_errors: 3b4.。

     另請參閱 *note locale encoding: 227.（區域編碼）。

finder（尋檢器）

     一個物件，它會嘗試為正在被 import 的模組尋找 *note loader: 15a8.（
     載入器）。

     有兩種類型的尋檢器：*note 元路徑尋檢器 (meta path finder): 1011. 會
     使用 *note sys.meta_path: cd2.，而*note 路徑項目尋檢器 (path entry
     finder): 1012. 會使用 *note sys.path_hooks: fc7.。

     請參閱 *note 模組引入系統: 1e01. 和 *note importlib: 6b. 以了解更多
     細節。

floor division（向下取整除法）

     向下無條件捨去到最接近整數的數學除法。向下取整除法的運算子是 ‘//’。
     例如，運算式 ‘11 // 4’ 的計算結果為 ‘2’，與 float（浮點數）真除法所
     回傳的 ‘2.75’ 不同。請注意，‘(-11) // 4’ 的結果是 ‘-3’，因為是
     ‘-2.75’ 被'向下'無條件捨去。請參閱 PEP 238(16)。

free threading

     A threading model where multiple threads can run Python bytecode
     simultaneously within the same interpreter.  This is in contrast to
     the *note global interpreter lock: 12e. which allows only one
     thread to execute Python bytecode at a time.  See PEP 703(17).

function（函式）

     一連串的陳述式，它能夠向呼叫者回傳一些值。它也可以被傳遞零個或多個
     *note 引數: 3ef.，這些引數可被使用於函式本體的執行。另請參閱 *note
     parameter: 1dee.（參數）、*note method: 4f41.（方法），以及*note
     函式定義: 1b3a.章節。

function annotation（函式註釋）

     函式參數或回傳值的一個 *note annotation: 3fe.（註釋）。

     函式註釋通常被使用於*note 型別提示: 1e58.：例如，這個函式預期會得到
     兩個 *note int: 23c. 引數，並會有一個 *note int: 23c. 回傳值：

          def sum_two_numbers(a: int, b: int) -> int:
             return a + b

     函式註釋的語法在*note 函式定義: 1b3a.章節有詳細解釋。

     請參閱 *note variable annotation: cfc. 和 PEP 484(18)，皆有此功能的
     描述。關於註釋的最佳實踐方法，另請參閱 *note 註釋 (annotation)
     最佳實踐: 77d.。

__future__

     *note future 陳述式: 16f.：‘from __future__ import <feature>’，會指
     示編譯器使用那些在 Python 未來的發布版本中將成為標準的語法或語義，
     來編譯當前的模組。而 *note __future__: 0. 模組則記錄了 'feature（功
     能）'可能的值。透過 import 此模組並對其變數求值，你可以看見一個新的
     功能是何時首次被新增到此語言中，以及它何時將會（或已經）成為預設的
     功能：

          >>> import __future__
          >>> __future__.division
          _Feature((2, 2, 0, 'alpha', 2), (3, 0, 0, 'alpha', 0), 8192)

garbage collection（垃圾回收）

     當記憶體不再被使用時，將其釋放的過程。Python 執行垃圾回收，是透過參
     照計數 (reference counting)，以及一個能夠檢測和中斷參照循環
     (reference cycle) 的循環垃圾回收器 (cyclic garbage collector) 來完
     成。垃圾回收器可以使用 *note gc: 56. 模組對其進行控制。

generator（產生器）

     一個會回傳 *note generator iterator: b85.（產生器疊代器）的函式。它
     看起來像一個正常的函式，但不同的是它包含了 *note yield: 971. 運算式
     ，能產生一系列的值，這些值可用於 for 迴圈，或是以 *note next():
     77c. 函式，每次檢索其中的一個值。

     這個術語通常用來表示一個產生器函式，但在某些情境中，也可能是表示'產
     生器疊代器'。萬一想表達的意思不夠清楚，那就使用完整的術語，以避免歧
     義。

generator iterator（產生器疊代器）

     一個由 *note generator: 1004.（產生器）函式所建立的物件。

     每個 *note yield: 971. 會暫停處理程序，並記住位置執行狀態（包括區域
     變數及擱置中的 try 陳述式）。當'產生器疊代器'回復時，它會從停止的地
     方繼續執行（與那些每次調用時都要重新開始的函式有所不同）。

generator expression（產生器運算式）

     An *note expression: 1e5c. that returns an *note iterator: 192.  It
     looks like a normal expression followed by a ‘for’ clause defining
     a loop variable, range, and an optional ‘if’ clause.  The combined
     expression generates values for an enclosing function:

          >>> sum(i*i for i in range(10))         # sum of squares 0, 1, 4, ... 81
          285

generic function（泛型函式）

     一個由多個函式組成的函式，該函式會對不同的型別實作相同的運算。呼叫
     期間應該使用哪種實作，是由調度演算法 (dispatch algorithm) 來決定。

     另請參閱 *note single dispatch: 996.（單一調度）術語表條目、*note
     functools.singledispatch(): 5df. 裝飾器和 PEP 443(19)。

generic type（泛型型別）

     一個能夠被參數化 (parameterized) 的 *note type: 1835.（型別）；通常
     是一個 *note 容器型別: 1e61.，像是 *note list: 5b6. 和 *note dict:
     23b.。它被用於*note 型別提示: 1e58.和*note 註釋: 3fe.。

     詳情請參閱*note 泛型別名型別: 656.、 PEP 483(20)、 PEP 484(21)、
     PEP 585(22) 和 *note typing: ed. 模組。

GIL

     請參閱 *note global interpreter lock: 12e.（全域直譯器鎖）。

global interpreter lock（全域直譯器鎖）

     *note CPython: 699. 直譯器所使用的機制，用以確保每次都只有一個執行
     緒能執行 Python 的 *note bytecode: 16d.（位元組碼）。透過使物件模型
     （包括關鍵的內建型別，如 *note dict: 23b.）自動地避免並行存取
     (concurrent access) 的危險，此機制可以簡化 CPython 的實作。鎖定整個
     直譯器，會使直譯器更容易成為多執行緒 (multi-threaded)，但代價是會犧
     牲掉多處理器的機器能夠提供的一大部分平行性 (parallelism)。

     然而，有些擴充模組，無論是標準的或是第三方的，它們被設計成在執行壓
     縮或雜湊等計算密集 (computationally intensive) 的任務時，可以解除
     GIL。另外，在執行 I/O 時，GIL 總是會被解除。

     As of Python 3.13, the GIL can be disabled using the *note
     -disable-gil: 158. build configuration.  After building Python with
     this option, code must be run with *note -X gil 0: 15a. or after
     setting the *note PYTHON_GIL=0: 159. environment variable.  This
     feature enables improved performance for multi-threaded
     applications and makes it easier to use multi-core CPUs
     efficiently.  For more details, see PEP 703(23).

hash-based pyc（雜湊架構的 pyc）

     一個位元組碼 (bytecode) 暫存檔，它使用雜湊值而不是對應原始檔案的最
     後修改時間，來確定其有效性。請參閱*note Cached bytecode
     invalidation: 590.。

hashable（可雜湊的）

     如果一個物件有一個雜湊值，該值在其生命週期中永不改變（它需要一個
     *note __hash__(): a9e. method），且可與其他物件互相比較（它需要一個
     *note __eq__(): a9d. method），那麼它就是一個'可雜湊'物件。比較結果
     為相等的多個可雜湊物件，它們必須擁有相同的雜湊值。

     可雜湊性 (hashability) 使一個物件可用作 dictionary（字典）的鍵和
     set（集合）的成員，因為這些資料結構都在其內部使用了雜湊值。

     大多數的 Python 不可變內建物件都是可雜湊的；可變的容器（例如 list 或
     dictionary）並不是；而不可變的容器（例如 tuple（元組）和 frozenset）
     ，只有當它們的元素是可雜湊的，它們本身才是可雜湊的。若物件是使用者
     自定 class 的實例，則這些物件會被預設為可雜湊的。它們在互相比較時都
     是不相等的（除非它們與自己比較），而它們的雜湊值則是衍生自它們的
     *note id(): 1390.。

IDLE

     Python 的 Integrated Development and Learning Environment（整合開發
     與學習環境）。*note IDLE: fb6. 是一個基本的編輯器和直譯器環境，它和
     Python 的標準發行版本一起被提供。

immortal

     'Immortal objects' are a CPython implementation detail introduced
     in PEP 683(24).

     If an object is immortal, its *note reference count: 46fe. is never
     modified, and therefore it is never deallocated while the
     interpreter is running.  For example, *note True: bb4. and *note
     None: 61b. are immortal in CPython.

immutable（不可變物件）

     一個具有固定值的物件。不可變物件包括數字、字串和 tuple（元組）。這
     類物件是不能被改變的。如果一個不同的值必須被儲存，則必須建立一個新
     的物件。它們在需要恆定雜湊值的地方，扮演重要的角色，例如
     dictionary（字典）中的一個鍵。

import path（引入路徑）

     一個位置（或*note 路徑項目: 1edf.）的列表，而那些位置就是在 import
     模組時，會被 *note path based finder: 1ecf.（基於路徑的尋檢器）搜尋
     模組的位置。在 import 期間，此位置列表通常是來自 *note sys.path:
     37f.，但對於子套件 (subpackage) 而言，它也可能是來自父套件的
     ‘__path__’ 屬性。

importing（引入）

     一個過程。一個模組中的 Python 程式碼可以透過此過程，被另一個模組中
     的 Python 程式碼使用。

importer（引入器）

     一個能夠尋找及載入模組的物件；它既是 *note finder: 1eca.（尋檢器）
     也是 *note loader: 15a8.（載入器）物件。

interactive（互動的）

     Python has an interactive interpreter which means you can enter
     statements and expressions at the interpreter prompt, immediately
     execute them and see their results.  Just launch ‘python’ with no
     arguments (possibly by selecting it from your computer's main
     menu).  It is a very powerful way to test out new ideas or inspect
     modules and packages (remember ‘help(x)’).  For more on interactive
     mode, see *note 互動模式: 153.

interpreted（直譯的）

     Python 是一種直譯語言，而不是編譯語言，不過這個區分可能有些模糊，因
     為有位元組碼 (bytecode) 編譯器的存在。這表示原始檔案可以直接被運行
     ，而不需明確地建立另一個執行檔，然後再執行它。直譯語言通常比編譯語
     言有更短的開發／除錯週期，不過它們的程式通常也運行得較慢。另請參閱
     *note interactive: 14d.（互動的）。

interpreter shutdown（直譯器關閉）

     當 Python 直譯器被要求關閉時，它會進入一個特殊階段，在此它逐漸釋放
     所有被配置的資源，例如模組和各種關鍵內部結構。它也會多次呼叫*note
     垃圾回收器 (garbage collector): 181c.。這能夠觸發使用者自定的解構函
     式 (destructor) 或弱引用的回呼 (weakref callback)，並執行其中的程式
     碼。在關閉階段被執行的程式碼會遇到各種例外，因為它所依賴的資源可能
     不再有作用了（常見的例子是函式庫模組或是警告機制）。

     直譯器關閉的主要原因，是 ‘__main__’ 模組或正被運行的腳本已經執行完
     成。

iterable（可疊代物件）

     一種能夠一次回傳一個其中成員的物件。可疊代物件的例子包括所有的序列
     型別（像是 *note list: 5b6.、*note str: 3f2. 和 *note tuple: 322.）
     和某些非序列型別，像是 *note dict: 23b.、*note 檔案物件: 115b.，以
     及你所定義的任何 class 物件，只要那些 class 有 *note __iter__():
     1bc7. method 或是實作 *note sequence: 499.（序列）語意的 *note
     __getitem__(): 266. method，該物件就是可疊代物件。

     可疊代物件可用於 *note for: 2c3. 迴圈和許多其他需要一個序列的地方
     (*note zip(): 774.、*note map(): 808...)。當一個可疊代物件作為引數
     被傳遞給內建函式 *note iter(): 77b. 時，它會為該物件回傳一個疊代器
     。此疊代器適用於針對一組值進行一遍 (one pass) 運算。使用疊代器時，
     通常不一定要呼叫 *note iter(): 77b. 或自行處理疊代器物件。*note
     for: 2c3. 陳述式會自動地為你處理這些事，它會建立一個暫時性的未命名
     變數，用於在迴圈期間保有該疊代器。另請參閱 *note iterator: 192.（疊
     代器）、*note sequence: 499.（序列）和 *note generator: 1004.（產生
     器）。

iterator（疊代器）

     一個表示資料流的物件。重複地呼叫疊代器的 *note __next__(): 1260.
     method（或是將它傳遞給內建函式 *note next(): 77c.）會依序回傳資料流
     中的各項目。當不再有資料時，則會引發 *note StopIteration: ba1. 例外
     。此時，該疊代器物件已被用盡，而任何對其 ‘__next__()’ method 的進一
     步呼叫，都只會再次引發 *note StopIteration: ba1.。疊代器必須有一個
     *note __iter__(): 1bc7. method，它會回傳疊代器物件本身，所以每個疊
     代器也都是可疊代物件，且可以用於大多數適用其他可疊代物件的場合。一
     個明顯的例外，是嘗試多遍疊代 (multiple iteration passes) 的程式碼。
     一個容器物件（像是 *note list: 5b6.）在每次你將它傳遞給 *note
     iter(): 77b. 函式或在 *note for: 2c3. 迴圈中使用它時，都會產生一個
     全新的疊代器。使用疊代器嘗試此事（多遍疊代）時，只會回傳在前一遍疊
     代中被用過的、同一個已被用盡的疊代器物件，使其看起來就像一個空的容
     器。

     在*note 疊代器型別: 204f.文中可以找到更多資訊。

     'CPython 實作細節：' CPython does not consistently apply the
     requirement that an iterator define *note __iter__(): 1bc7.  And
     also please note that the free-threading CPython does not guarantee
     the thread-safety of iterator operations.

key function（鍵函式）

     鍵函式或理序函式 (collation function) 是一個可呼叫 (callable) 函式
     ，它會回傳一個用於排序 (sorting) 或定序 (ordering) 的值。例如，
     *note locale.strxfrm(): 3b64. 被用來產生一個了解區域特定排序慣例的
     排序鍵。

     Python 中的許多工具，都接受以鍵函式來控制元素被定序或分組的方式。它
     們包括 *note min(): eac.、*note max(): ead.、*note sorted(): b75.、
     *note list.sort(): b76.、*note heapq.merge(): daa.、*note
     heapq.nsmallest(): 240c.、*note heapq.nlargest(): 240b. 和 *note
     itertools.groupby(): 260b.。

     有幾種方法可以建立一個鍵函式。例如，*note str.lower(): 16f2. method
     可以作為不分大小寫排序的鍵函式。或者，一個鍵函式也可以從 *note
     lambda: 1234. 運算式被建造，例如 ‘lambda r: (r[0], r[2])’。另外，
     *note operator.attrgetter(): dd9.、*note operator.itemgetter():
     a05. 和 *note operator.methodcaller(): dda. 為三個鍵函式的建構函式
     (constructor)。關於如何建立和使用鍵函式的範例，請參閱*note
     如何排序: 205a.。

keyword argument（關鍵字引數）

     請參閱 *note argument: 3ef.（引數）。

lambda

     由單一 *note expression: 1e5c.（運算式）所組成的一個匿名行內函式
     (inline function)，於該函式被呼叫時求值。建立 lambda 函式的語法是
     ‘lambda [parameters]: expression’

LBYL

     Look before you leap.（三思而後行。）這種編碼風格會在進行呼叫或查找
     之前，明確地測試先決條件。這種風格與 *note EAFP: 2a66. 方式形成對比
     ，且它的特色是會有許多 *note if: 2c4. 陳述式的存在。

     在一個多執行緒環境中，LBYL 方式有在「三思」和「後行」之間引入了競爭
     條件 (race condition) 的風險。例如以下程式碼 ‘if key in mapping:
     return mapping[key]’，如果另一個執行緒在測試之後但在查找之前，從
     'mapping' 中移除了 'key'，則該程式碼就會失效。這個問題可以用鎖
     (lock) 或使用 EAFP 編碼方式來解決。

list（串列）

     一個 Python 內建的 *note sequence: 499. （序列）。儘管它的名字是
     list，它其實更類似其他語言中的一個陣列 (array) 而較不像一個鏈結串列
     (linked list)，因為存取元素的時間複雜度是 'O'(1)。

list comprehension（串列綜合運算）

     一種用來處理一個序列中的全部或部分元素，並將處理結果以一個 list 回
     傳的簡要方法。‘result = ['{:#04x}'.format(x) for x in range(256) if
     x % 2 == 0]’ 會產生一個字串 list，其中包含 0 到 255 範圍內，所有偶
     數的十六進位數 (0x..)。*note if: 2c4. 子句是選擇性的。如果省略它，
     則 ‘range(256)’ 中的所有元素都會被處理。

loader（載入器）

     一個能夠載入模組的物件。它必須定義一個名為 ‘load_module()’ 的
     method（方法）。載入器通常是被 *note finder: 1eca.（尋檢器）回傳。
     更多細節請參閱 PEP 302(25)，關於 *note abstract base class: 114e.（
     抽象基底類別），請參閱 *note importlib.abc.Loader: e69.。

locale encoding（區域編碼）

     在 Unix 上，它是 LC_CTYPE 區域設定的編碼。它可以用 *note
     locale.setlocale(locale.LC_CTYPE, new_locale): 2bb. 來設定。

     在 Windows 上，它是 ANSI 代碼頁（code page，例如 ‘"cp1252"’）。

     在 Android 和 VxWorks 上，Python 使用 ‘"utf-8"’ 作為區域編碼。

     *note locale.getencoding(): 2bc. 可以用來取得區域編碼。

     也請參考 *note filesystem encoding and error handler: 4e0.。

magic method（魔術方法）

     *note special method: 17ae.（特殊方法）的一個非正式同義詞。

mapping（對映）

     一個容器物件，它支援任意鍵的查找，且能實作 *note abstract base
     classes（抽象基底類別）: 81b.中，*note collections.abc.Mapping:
     86f. 或 *note collections.abc.MutableMapping: 1048. 所指定的
     method。範例包括 *note dict: 23b.、*note collections.defaultdict:
     1155.、*note collections.OrderedDict: 57f. 和 *note
     collections.Counter: 1033.。

meta path finder（元路徑尋檢器）

     一種經由搜尋 *note sys.meta_path: cd2. 而回傳的 *note finder:
     1eca.（尋檢器）。元路徑尋檢器與*note 路徑項目尋檢器 (path entry
     finder): 1012. 相關但是不同。

     關於元路徑尋檢器實作的 method，請參閱 *note
     importlib.abc.MetaPathFinder: 813.。

metaclass（元類別）

     一種 class 的 class。Class 定義過程會建立一個 class 名稱、一個
     class dictionary（字典），以及一個 base class（基底類別）的列表。
     Metaclass 負責接受這三個引數，並建立該 class。大多數的物件導向程式
     語言會提供一個預設的實作。Python 的特別之處在於它能夠建立自訂的
     metaclass。大部分的使用者從未需要此工具，但是當需要時，metaclass 可
     以提供強大且優雅的解決方案。它們已被用於記錄屬性存取、增加執行緒安
     全性、追蹤物件建立、實作單例模式 (singleton)，以及許多其他的任務。

     更多資訊可以在*note Metaclasses: 1e4a.章節中找到。

method（方法）

     一個在 class 本體內被定義的函式。如果 method 作為其 class 實例的一
     個屬性被呼叫，則它將會得到該實例物件成為它的第一個 *note argument:
     3ef.（引數）（此引數通常被稱為 ‘self’）。請參閱 *note function:
     1f2f.（函式）和 *note nested scope: 2041.（巢狀作用域）。

method resolution order（方法解析順序）

     方法解析順序是在查找某個成員的過程中，base class（基底類別）被搜尋
     的順序。關於 Python 自 2.3 版直譯器所使用的演算法細節，請參閱 *note
     The Python 2.3 Method Resolution Order: 1415.。

module（模組）

     一個擔任 Python 程式碼的組織單位 (organizational unit) 的物件。模組
     有一個命名空間，它包含任意的 Python 物件。模組是藉由 *note
     importing: 1ebe. 的過程，被載入至 Python。

     另請參閱 *note package: 1ec1.（套件）。

module spec（模組規格）

     一個命名空間，它包含用於載入模組的 import 相關資訊。它是 *note
     importlib.machinery.ModuleSpec: 1d5a. 的一個實例。

MRO

     請參閱 *note method resolution order: 205c.（方法解析順序）。

mutable（可變物件）

     可變物件可以改變它們的值，但維持它們的 *note id(): 1390.。另請參閱
     *note immutable: 1b02.（不可變物件）。

named tuple（附名元組）

     術語「named tuple（附名元組）」是指從 tuple 繼承的任何型別或 class，
     且它的可索引 (indexable) 元素也可以用附名屬性來存取。這些型別或
     class 也可以具有其他的特性。

     有些內建型別是 named tuple，包括由 *note time.localtime(): 1467. 和
     *note os.stat(): 448. 回傳的值。另一個例子是 *note sys.float_info:
     18f0.：

          >>> sys.float_info[1]                   # indexed access
          1024
          >>> sys.float_info.max_exp              # named field access
          1024
          >>> isinstance(sys.float_info, tuple)   # kind of tuple
          True

     有些 named tuple 是內建型別（如上例）。或者，一個 named tuple 也可
     以從一個正規的 class 定義來建立，只要該 class 是繼承自 *note tuple:
     322.，且定義了附名欄位 (named field) 即可。這類的 class 可以手工編
     寫、可以繼承自 *note typing.NamedTuple: 291. 來建立，也可以使用工廠
     函式 (factory function) *note collections.namedtuple(): 1ae. 來建立
     。後者技術也增加了一些額外的 method，這些 method 可能是在手寫或內建
     的 named tuple 中，無法找到的。

namespace（命名空間）

     變數被儲存的地方。命名空間是以 dictionary（字典）被實作。有區域的、
     全域的及內建的命名空間，而在物件中（在 method 中）也有巢狀的命名空
     間。命名空間藉由防止命名衝突，來支援模組化。例如，函式 *note
     builtins.open: 4c0. 和 *note os.open(): d38. 是透過它們的命名空間來
     區分彼此。命名空間也藉由明確地區分是哪個模組在實作一個函式，來增進
     可讀性及可維護性。例如，寫出 *note random.seed(): 120c. 或 *note
     itertools.islice(): af0. 明確地表示，這些函式分別是由 *note random:
     a6. 和 *note itertools: 75. 模組在實作。

namespace package（命名空間套件）

     一個 PEP 420(26) *note package: 1ec1.（套件），它只能作為子套件
     (subpackage) 的一個容器。命名空間套件可能沒有實體的表示法，而且具體
     來說它們不像是一個 *note regular package: 1ec3.（正規套件），因為它
     們並沒有 ‘__init__.py’ 這個檔案。

     另請參閱 *note module: 1555.（模組）。

nested scope（巢狀作用域）

     能夠參照外層定義 (enclosing definition) 中的變數的能力。舉例來說，
     一個函式如果是在另一個函式中被定義，則它便能夠參照外層函式中的變數
     。請注意，在預設情況下，巢狀作用域僅適用於參照，而無法用於賦值。區
     域變數能在最內層作用域中讀取及寫入。同樣地，全域變數是在全域命名空
     間中讀取及寫入。*note nonlocal: 123e. 容許對外層作用域進行寫入。

new-style class（新式類別）

     一個舊名，它是指現在所有的 class 物件所使用的 class 風格。在早期的
     Python 版本中，只有新式 class 才能使用 Python 較新的、多樣的功能，
     像是 *note __slots__: 1458.、描述器 (descriptor)、屬性 (property)、
     *note __getattribute__(): b79.、class method（類別方法）和 static
     method（靜態方法）。

object（物件）

     具有狀態（屬性或值）及被定義的行為（method）的任何資料。它也是任何
     *note new-style class: 276d.（新式類別）的最終 base class（基底類別
     ）。

optimized scope

     A scope where target local variable names are reliably known to the
     compiler when the code is compiled, allowing optimization of read
     and write access to these names.  The local namespaces for
     functions, generators, coroutines, comprehensions, and generator
     expressions are optimized in this fashion.  Note: most interpreter
     optimizations are applied to all scopes, only those relying on a
     known set of local and nonlocal variable names are restricted to
     optimized scopes.

package（套件）

     一個 Python 的 *note module: 1555.（模組），它可以包含子模組
     (submodule) 或是遞迴的子套件 (subpackage)。技術上而言，套件就是具有
     ‘__path__’ 屬性的一個 Python 模組。

     另請參閱 *note regular package: 1ec3.（正規套件）和 *note namespace
     package: 1b6c.（命名空間套件）。

parameter（參數）

     在 *note function: 1f2f.（函式）或 method 定義中的一個命名實體
     (named entity)，它指明該函式能夠接受的一個 *note argument: 3ef.（引
     數），或在某些情況下指示多個引數。共有有五種不同的參數類型：

        * 'positional-or-keyword'（位置或關鍵字）：指明一個可以*note
          按照位置: 3ef.或是作為*note 關鍵字引數: 3ef.被傳遞的引數。這是
          參數的預設類型，例如以下的 'foo' 和 'bar'：

               def func(foo, bar=None): ...

        * 'positional-only'（僅限位置）：指明一個只能按照位置被提供的引
          數。在函式定義的參數列表中包含一個 ‘/’ 字元，就可以在該字元前
          面定義僅限位置參數，例如以下的 'posonly1' 和 'posonly2'：

               def func(posonly1, posonly2, /, positional_or_keyword): ...

        * 'keyword-only'（僅限關鍵字）：指明一個只能以關鍵字被提供的引數
          。在函式定義的參數列表中，包含一個任意數量位置參數
          (var-positional parameter) 或是單純的 ‘*’ 字元，就可以在其後方
          定義僅限關鍵字參數，例如以下的 'kw_only1' 和 'kw_only2'：

               def func(arg, *, kw_only1, kw_only2): ...

        * 'var-positional'（任意數量位置）：指明一串能以任意序列被提供的
          位置引數（在已被其他參數接受的任何位置引數之外）。這類參數是透
          過在其參數名稱字首加上 ‘*’ 來定義的，例如以下的 'args'：

               def func(*args, **kwargs): ...

        * 'var-keyword'（任意數量關鍵字）：指明可被提供的任意數量關鍵字
          引數（在已被其他參數接受的任何關鍵字引數之外）。這類參數是透過
          在其參數名稱字首加上 ‘**’ 來定義的，例如上面範例中的 'kwargs'。

     參數可以指明引數是選擇性的或必需的，也可以為一些選擇性的引數指定預
     設值。

     另請參閱術語表的 *note argument: 3ef.（引數）條目、常見問題中的
     *note 引數和參數之間的差異: 4e84.、*note inspect.Parameter: 1b4.
     class、*note 函式定義: 1b3a.章節，以及 PEP 362(27)。

path entry（路徑項目）

     在 *note import path: 1ecc.（引入路徑）中的一個位置，而 *note path
     based finder: 1ecf. （基於路徑的尋檢器）會參考該位置來尋找要 import
     的模組。

path entry finder（路徑項目尋檢器）

     被 *note sys.path_hooks: fc7. 中的一個可呼叫物件 (callable)（意即一
     個 *note path entry hook: 1ee1.）所回傳的一種 *note finder: 1eca.，
     它知道如何以一個 *note path entry: 1edf.定位模組。

     關於路徑項目尋檢器實作的 method，請參閱 *note
     importlib.abc.PathEntryFinder: 814.。

path entry hook（路徑項目鉤）

     在 *note sys.path_hooks: fc7. 列表中的一個可呼叫物件 (callable)，若
     它知道如何在一個特定的 *note path entry: 1edf. 中尋找模組，則會回傳
     一個 *note path entry finder: 1012.（路徑項目尋檢器）。

path based finder（基於路徑的尋檢器）

     預設的*note 元路徑尋檢器 (meta path finder): 1011. 之一，它會在一個
     *note import path: 1ecc. 中搜尋模組。

path-like object（類路徑物件）

     一個表示檔案系統路徑的物件。類路徑物件可以是一個表示路徑的 *note
     str: 3f2. 或 *note bytes: 1a5. 物件，或是一個實作 *note
     os.PathLike: bf8. 協定的物件。透過呼叫 *note os.fspath(): bfa. 函式
     ，一個支援 *note os.PathLike: bf8. 協定的物件可以被轉換為 *note
     str: 3f2. 或 *note bytes: 1a5. 檔案系統路徑；而 *note
     os.fsdecode(): bfb. 及 *note os.fsencode(): bfc. 則分別可用於確保
     *note str: 3f2. 及 *note bytes: 1a5. 的結果。由 PEP 519(28) 引入。

PEP

     Python Enhancement Proposal（Python 增強提案）。PEP 是一份設計說明
     文件，它能為 Python 社群提供資訊，或是描述 Python 的一個新功能或該
     功能的程序和環境。PEP 應該要提供簡潔的技術規範以及被提案功能的運作
     原理。

     PEP 的存在目的，是要成為重大新功能的提案、社群中關於某個問題的意見
     收集，以及已納入 Python 的設計決策的記錄，這些過程的主要機制。PEP 的
     作者要負責在社群內建立共識並記錄反對意見。

     請參閱 PEP 1(29)。

portion（部分）

     在單一目錄中的一組檔案（也可能儲存在一個 zip 檔中），這些檔案能對一
     個命名空間套件 (namespace package) 有所貢獻，如同 PEP 420(30) 中的
     定義。

positional argument（位置引數）

     請參閱 *note argument: 3ef.（引數）。

provisional API（暫行 API）

     暫行 API 是指，從標準函式庫的向後相容性 (backwards compatibility) 保
     證中，故意被排除的 API。雖然此類介面，只要它們被標示為暫行的，理論
     上並不會有重大的變更，但如果核心開發人員認為有必要，也可能會出現向
     後不相容的變更（甚至包括移除該介面）。這種變更並不會無端地產生——只
     有 API 被納入之前未察覺的嚴重基本缺陷被揭露時，它們才會發生。

     即使對於暫行 API，向後不相容的變更也會被視為「最後的解決方案」——對
     於任何被發現的問題，仍然會盡可能找出一個向後相容的解決方案。

     這個過程使得標準函式庫能隨著時間不斷進化，而避免耗費過長的時間去鎖
     定有問題的設計錯誤。請參閱 PEP 411(31) 了解更多細節。

provisional package（暫行套件）

     請參閱 *note provisional API: aa6.（暫行 API）。

Python 3000

     Python 3.x 系列版本的暱稱（很久以前創造的，當時第 3 版的發布是在遙
     遠的未來。）也可以縮寫為「Py3k」。

Pythonic（Python 風格的）

     一個想法或一段程式碼，它應用了 Python 語言最常見的慣用語，而不是使
     用其他語言常見的概念來實作程式碼。例如，Python 中常見的一種習慣用法
     ，是使用一個 *note for: 2c3. 陳述式，對一個可疊代物件的所有元素進行
     迴圈。許多其他語言並沒有這種類型的架構，所以不熟悉 Python 的人有時
     會使用一個數值計數器來代替：

          for i in range(len(food)):
              print(food[i])

     相較之下，以下方法更簡潔、更具有 Python 風格：

          for piece in food:
              print(piece)

qualified name（限定名稱）

     一個「點分隔名稱」，它顯示從一個模組的全域作用域到該模組中定義的
     class、函式或 method 的「路徑」，如 PEP 3155(32) 中的定義。對於頂層
     的函式和 class 而言，限定名稱與其物件名稱相同：

          >>> class C:
          ...     class D:
          ...         def meth(self):
          ...             pass
          ...
          >>> C.__qualname__
          'C'
          >>> C.D.__qualname__
          'C.D'
          >>> C.D.meth.__qualname__
          'C.D.meth'

     當用於引用模組時，'完全限定名稱 (fully qualified name)' 是表示該模
     組的完整點分隔路徑，包括任何的父套件，例如 ‘email.mime.text’：

          >>> import email.mime.text
          >>> email.mime.text.__name__
          'email.mime.text'

reference count（參照計數）

     The number of references to an object.  When the reference count of
     an object drops to zero, it is deallocated.  Some objects are *note
     immortal: 4190. and have reference counts that are never modified,
     and therefore the objects are never deallocated.  Reference
     counting is generally not visible to Python code, but it is a key
     element of the *note CPython: 699. implementation.  Programmers can
     call the *note sys.getrefcount(): 418f. function to return the
     reference count for a particular object.

regular package（正規套件）

     一個傳統的 *note package: 1ec1.（套件），例如一個包含 ‘__init__.py’
     檔案的目錄。

     另請參閱 *note namespace package: 1b6c.（命名空間套件）。

REPL

     An acronym for the "read–eval–print loop", another name for the
     *note interactive: 14d. interpreter shell.

__slots__

     在 class 內部的一個宣告，它藉由預先宣告實例屬性的空間，以及消除實例
     dictionary（字典），來節省記憶體。雖然該技術很普遍，但它有點難以正
     確地使用，最好保留給那種在一個記憶體關鍵 (memory-critical) 的應用程
     式中存在大量實例的罕見情況。

sequence（序列）

     一個 *note iterable: 11bf.（可疊代物件），它透過 *note
     __getitem__(): 266. special method（特殊方法），使用整數索引來支援
     高效率的元素存取，並定義了一個 *note __len__(): 1e38. method 來回傳
     該序列的長度。一些內建序列型別包括 *note list: 5b6.、*note str:
     3f2.、*note tuple: 322. 和 *note bytes: 1a5.。請注意，雖然 *note
     dict: 23b. 也支援 *note __getitem__(): 266. 和 ‘__len__()’，但它被
     視為對映 (mapping) 而不是序列，因為其查找方式是使用任意的 *note
     immutable: 1b02. 鍵，而不是整數。

     抽象基底類別 (abstract base class) *note collections.abc.Sequence:
     115c. 定義了一個更加豐富的介面，並不僅止於 *note __getitem__():
     266. 和 *note __len__(): 1e38.，還增加了 ‘count()’、‘index()’、
     *note __contains__(): 1e33. 和 *note __reversed__(): 1e32.。實作此
     擴充介面的型別，可以使用 *note register(): 102a. 被明確地註冊。更多
     關於序列方法的文件，請見*note 常見序列操作: 2086.。

set comprehension（集合綜合運算）

     一種緊密的方法，用來處理一個可疊代物件中的全部或部分元素，並將處理
     結果以一個 set 回傳。‘results = {c for c in 'abracadabra' if c not
     in 'abc'}’ 會產生一個字串 set：‘{'r', 'd'}’。請參閱*note Displays
     for lists, sets and dictionaries: 574.。

single dispatch（單一調度）

     *note generic function: 995.（泛型函式）調度的一種形式，在此，實作
     的選擇是基於單一引數的型別。

slice（切片）

     一個物件，它通常包含一段 *note sequence: 499.（序列）的某一部分。建
     立一段切片的方法是使用下標符號 (subscript notation) ‘[]’，若要給出
     多個數字，則在數字之間使用冒號，例如 ‘variable_name[1:3:5]’。在括號
     （下標）符號的內部，會使用 *note slice: 410. 物件。

soft deprecated

     A soft deprecation can be used when using an API which should no
     longer be used to write new code, but it remains safe to continue
     using it in existing code.  The API remains documented and tested,
     but will not be developed further (no enhancement).

     The main difference between a "soft" and a (regular) "hard"
     deprecation is that the soft deprecation does not imply scheduling
     the removal of the deprecated API.

     Another difference is that a soft deprecation does not issue a
     warning.

     See PEP 387: Soft Deprecation(33).

special method（特殊方法）

     一種會被 Python 自動呼叫的 method，用於對某種型別執行某種運算，例如
     加法。這種 method 的名稱會在開頭和結尾有兩個下底線。Special method
     在*note Special method names: c15.中有詳細說明。

statement（陳述式）

     陳述式是一個套組（suite，一個程式碼「區塊」）中的一部分。陳述式可以
     是一個 *note expression: 1e5c.（運算式），或是含有關鍵字（例如
     *note if: 2c4.、*note while: 1b0b. 或 *note for: 2c3.）的多種結構之
     一。

static type checker（靜態型別檢查器）

     會讀取 Python 程式碼並分析的外部工具，能夠找出錯誤，像是使用了不正
     確的型別。另請參閱*note 型別提示 (type hints): 1e58. 以及 *note
     typing: ed. 模組。

strong reference（強參照）

     在 Python 的 C API 中，強參照是對物件的參照，該物件為持有該參照的程
     式碼所擁有。建立參照時透過呼叫 *note Py_INCREF(): 514. 來獲得強參照
     、刪除參照時透過 *note Py_DECREF(): 515. 釋放強參照。

     *note Py_NewRef(): 83e. 函式可用於建立一個對物件的強參照。通常，在
     退出強參照的作用域之前，必須在該強參照上呼叫 *note Py_DECREF():
     515. 函式，以避免洩漏一個參照。

     另請參閱 *note borrowed reference: 2ef.（借用參照）。

text encoding（文字編碼）

     Python 中的字串是一個 Unicode 碼點 (code point) 的序列（範圍在
     ‘U+0000’ - ‘U+10FFFF’ 之間）。若要儲存或傳送一個字串，它必須被序列
     化為一個位元組序列。

     將一個字串序列化為位元組序列，稱為「編碼」，而從位元組序列重新建立
     該字串則稱為「解碼 (decoding)」。

     有多種不同的文字序列化編解碼器 (*note codecs: d5f.)，它們被統稱為「
     文字編碼」。

text file（文字檔案）

     一個能夠讀取和寫入 *note str: 3f2. 物件的一個 *note file object:
     115b.（檔案物件）。通常，文字檔案實際上是存取位元組導向的資料流
     (byte-oriented datastream) 並會自動處理 *note text encoding: 2054.（
     文字編碼）。文字檔案的例子有：以文字模式（‘'r'’ 或 ‘'w'’）開啟的檔
     案、*note sys.stdin: 4e2.、*note sys.stdout: a79. 以及 *note
     io.StringIO: ecb. 的實例。

     另請參閱 *note binary file: 1b8b.（二進位檔案），它是一個能夠讀取和
     寫入*note 類位元組串物件 (bytes-like object): cd4. 的檔案物件。

triple-quoted string（三引號內字串）

     由三個雙引號 (") 或單引號 (') 的作為邊界的一個字串。雖然它們並沒有
     提供異於單引號字串的任何額外功能，但基於許多原因，它們仍是很有用的
     。它們讓你可以在字串中包含未跳脫 (unescaped) 的單引號和雙引號，而且
     它們不需使用連續字元 (continuation character) 就可以跨越多行，這使
     得它們在編寫說明字串時特別有用。

type（型別）

     一個 Python 物件的型別決定了它是什麼類型的物件；每個物件都有一個型
     別。一個物件的型別可以用它的 *note __class__: 1418. 屬性來存取，或
     以 ‘type(obj)’ 來檢索。

type alias（型別別名）

     一個型別的同義詞，透過將型別指定給一個識別符 (identifier) 來建立。

     型別別名對於簡化*note 型別提示 (type hint): 1e58. 很有用。例如：

          def remove_gray_shades(
                  colors: list[tuple[int, int, int]]) -> list[tuple[int, int, int]]:
              pass

     可以寫成這樣，更具有可讀性：

          Color = tuple[int, int, int]

          def remove_gray_shades(colors: list[Color]) -> list[Color]:
              pass

     請參閱 *note typing: ed. 和 PEP 484(34)，有此功能的描述。

type hint（型別提示）

     一種 *note annotation: 3fe.（註釋），它指定一個變數、一個 class 屬
     性或一個函式的參數或回傳值的預期型別。

     型別提示是選擇性的，而不是被 Python 強制的，但它們對*note
     靜態型別檢查器 (static type checkers): 252.很有用，並能協助 IDE 完
     成程式碼的補全 (completion) 和重構 (refactoring)。

     全域變數、class 屬性和函式（不含區域變數）的型別提示，都可以使用
     *note typing.get_type_hints(): 657. 來存取。

     請參閱 *note typing: ed. 和 PEP 484(35)，有此功能的描述。

universal newlines（通用換行字元）

     一種解譯文字流 (text stream) 的方式，會將以下所有的情況識別為一行的
     結束：Unix 行尾慣例 ‘'\n'’、Windows 慣例 ‘'\r\n'’ 和舊的 Macintosh
     慣例 ‘'\r'’。請參閱 PEP 278(36) 和 PEP 3116(37)，以及用於 *note
     bytes.splitlines(): 20f1. 的附加用途。

variable annotation（變數註釋）

     一個變數或 class 屬性的 *note annotation: 3fe.（註釋）。

     註釋變數或 class 屬性時，賦值是選擇性的：

          class C:
              field: 'annotation'

     變數註釋通常用於*note 型別提示 (type hint): 1e58.：例如，這個變數預
     期會取得 *note int: 23c.（整數）值：

          count: int = 0

     變數註釋的語法在*note Annotated assignment statements: 1f7b.章節有
     詳細的解釋。

     請參閱 *note function annotation: 1b3b.（函式註釋）、 PEP 484(38) 和
     PEP 526(39)，皆有此功能的描述。關於註釋的最佳實踐方法，另請參閱
     *note 註釋 (annotation) 最佳實踐: 77d.。

virtual environment（虛擬環境）

     一個協作隔離 (cooperatively isolated) 的執行環境，能讓 Python 的使
     用者和應用程式得以安裝和升級 Python 發佈套件，而不會對同一個系統上
     運行的其他 Python 應用程式的行為產生干擾。

     另請參閱 *note venv: f9.。

virtual machine（虛擬機器）

     一部完全由軟體所定義的電腦 (computer)。Python 的虛擬機器會執行由
     *note bytecode: 16d.（位元組碼）編譯器所發出的位元組碼。

Zen of Python（Python 之禪）

     Python 設計原則與哲學的列表，其內容有助於理解和使用此語言。此列表可
     以透過在互動式提式字元後輸入「‘import this’」來找到它。

   ---------- Footnotes ----------

   (1) https://peps.python.org/pep-0484/

   (2) https://peps.python.org/pep-0526/

   (3) https://peps.python.org/pep-0362/

   (4) https://peps.python.org/pep-0492/

   (5) https://peps.python.org/pep-0492/

   (6) https://peps.python.org/pep-0525/

   (7) https://peps.python.org/pep-0492/

   (8) https://peps.python.org/pep-0492/

   (9) https://peps.python.org/pep-0492/

   (10) https://gvanrossum.github.io/

   (11) https://peps.python.org/pep-0343/

   (12) https://peps.python.org/pep-0492/

   (13) https://peps.python.org/pep-0492/

   (14) https://www.python.org

   (15) https://peps.python.org/pep-0498/

   (16) https://peps.python.org/pep-0238/

   (17) https://peps.python.org/pep-0703/

   (18) https://peps.python.org/pep-0484/

   (19) https://peps.python.org/pep-0443/

   (20) https://peps.python.org/pep-0483/

   (21) https://peps.python.org/pep-0484/

   (22) https://peps.python.org/pep-0585/

   (23) https://peps.python.org/pep-0703/

   (24) https://peps.python.org/pep-0683/

   (25) https://peps.python.org/pep-0302/

   (26) https://peps.python.org/pep-0420/

   (27) https://peps.python.org/pep-0362/

   (28) https://peps.python.org/pep-0519/

   (29) https://peps.python.org/pep-0001/

   (30) https://peps.python.org/pep-0420/

   (31) https://peps.python.org/pep-0411/

   (32) https://peps.python.org/pep-3155/

   (33) https://peps.python.org/pep-0387/#soft-deprecation

   (34) https://peps.python.org/pep-0484/

   (35) https://peps.python.org/pep-0484/

   (36) https://peps.python.org/pep-0278/

   (37) https://peps.python.org/pep-3116/

   (38) https://peps.python.org/pep-0484/

   (39) https://peps.python.org/pep-0526/


File: python.info,  Node: 關於這些說明文件,  Next: 處理錯誤 Bug,  Prev: 術語表,  Up: Top

13 關於這些說明文件
*******************

這些說明文件是透過 Sphinx(1) （一個專為 Python 說明文件所撰寫的文件處理
器）將使用 reStructuredText(2) 撰寫的原始檔轉換而成。

如同 Python 自身，透過自願者的努力下產出文件與封裝後自動化執行工具。若想
要回報臭蟲，請見 *note 處理錯誤 (Bug): 474e. 頁面，內含相關資訊。我們永
遠歡迎新的自願者加入！

致謝：

   * Fred L. Drake, Jr.，原始 Python 文件工具集的創造者以及一大部份內容
     的作者；

   * 創造 reStructuredText 和 Docutils 工具組的 Docutils(3) 專案；

   * Fredrik Lundh 先生，Sphinx 從他的 Alternative Python Reference 計劃
     中獲得許多的好主意。

* Menu:

* Python 文件的貢獻者們::

   ---------- Footnotes ----------

   (1) https://www.sphinx-doc.org/

   (2) https://docutils.sourceforge.io/rst.html

   (3) https://docutils.sourceforge.io/


File: python.info,  Node: Python 文件的貢獻者們,  Up: 關於這些說明文件

13.1 Python 文件的貢獻者們
==========================

許多人都曾為 Python 這門語言、Python 標準函式庫和 Python 說明文件貢獻過
。Python 所發佈的原始碼中含有部份貢獻者的清單，請見 Misc/ACKS(1) 。

正因為 Python 社群的撰寫與貢獻才有這份這麼棒的說明文件 - 感謝所有貢獻過
的人們！

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.13/Misc/ACKS


File: python.info,  Node: 處理錯誤 Bug,  Next: 版權宣告,  Prev: 關於這些說明文件,  Up: Top

14 處理錯誤 (Bug)
*****************

Python 已經是一個以穩定著稱的成熟程式語言。為了維持「穩定」的信譽，開發
者們想知道任何你在 Python 中發現的缺失。

有時候自己直接修復錯誤並且送出一個修正給 Python 會比較快，因為這樣會加速
流程而且不會困擾到太多人。學習如何*note 貢獻給 Python: 4f5a.。

* Menu:

* 說明文件的錯誤::
* 使用 Python 問題追蹤系統::
* 開始讓自己貢獻 Python::


File: python.info,  Node: 說明文件的錯誤,  Next: 使用 Python 問題追蹤系統,  Up: 處理錯誤 Bug

14.1 說明文件的錯誤
===================

如果你在這份說明文件中發現了錯誤並想要幫助我們改進，請將錯誤報告提交到
*note 追蹤系統 (tracker): 233.。如果你有相應的修正建議，請一併提交。（譯
者註：如果是繁體中文說明文件翻譯相關的錯誤，請提交到
‘https://github.com/python/python-docs-zh-tw/issues’。）

你也可以在我們的說明文件 Discourse 討論區(1)中新增一個討論事項。

If you find a bug in the theme (HTML / CSS / JavaScript) of the
documentation, please submit a bug report on the python-doc-theme bug
tracker(2).

如果你的時間有限，也可以將說明文件的錯誤報告以電子郵件寄到
<docs@python.org>（程式碼執行的錯誤可以寄到 <python-list@python.org>）。
「docs@」是一個由志工們所運行的郵寄清單；你的請求會被注意到，但可能需要
一些時間才會被處理。

也參考
......

說明文件錯誤(3)

     一系列已被提交至 Python 問題追蹤系統的有關說明文件的錯誤。

問題追蹤系統(4)

     在追蹤系統上回報改進建議的過程簡介。

貢獻說明文件(5)

     給有意成為 Python 說明文件貢獻者的綜合指南。

說明文件翻譯(6)

     一份 GitHub 網頁的清單，裡面有各個說明文件翻譯團隊的連結，以及他們
     的主要聯絡人。

   ---------- Footnotes ----------

   (1) https://discuss.python.org/c/documentation/26

   (2) https://github.com/python/python-docs-theme

   (3) 
https://github.com/python/cpython/issues?q=is%3Aissue+is%3Aopen+label%3Adocs

   (4) https://devguide.python.org/tracker/

   (5) 
https://devguide.python.org/docquality/#helping-with-documentation

   (6) https://devguide.python.org/documentation/translating/


File: python.info,  Node: 使用 Python 問題追蹤系統,  Next: 開始讓自己貢獻 Python,  Prev: 說明文件的錯誤,  Up: 處理錯誤 Bug

14.2 使用 Python 問題追蹤系統
=============================

對於 Python 本身的問題報告，應該透過 GitHub 問題追蹤系統
(‘https://github.com/python/cpython/issues’) 提交。這個 GitHub 問題追蹤
系統提供了一個網頁表單，可以輸入並提交相關資訊給開發者。

填寫報告的第一步，是確認該問題是否已經被回報過了。這樣做的好處，除了可以
節省開發者的時間，也能讓你了解目前關於該問題的處理進度；有可能已經在下一
個發行版本中修正了這個問題，也有可能需要更詳細的資訊（在這種情況下，如果
可以，非常歡迎你提供資訊！）。要確認是否重複回報，請使用頁面頂端的搜尋框
來搜尋追蹤系統。

如果你想回報的問題還沒有在問題列表出現過，請登入 GitHub。如果你還沒有
GitHub 帳戶，請點選「Sign up」連結來建立一個新的帳戶。你無法以匿名方式提
交錯誤報告。

如果已經登入，那你就可以提交問題了。請點選列表頂端區域的「New issue」按
鈕，來回報一個新的問題。

提交的表單中有兩個欄位，「Title」及「Comment」。

在「Title」欄位，輸入對該問題'非常'簡短的描述；最好少於十個單字。

在「Comment」欄位，請詳細描述該問題，包括你預期發生的情況和實際發生的情
況。請確定說明中包含了涉及到的任何擴充模組，以及你當時所使用的硬體和軟體
平台（視情況而定，可以附上版本資訊）。

每一份問題報告都會被一位開發人員查核，並由他決定要做出什麼變更來修正這個
問題。每當該問題有修正動作時，你會收到更新回報。

也參考
......

如何有效地回報錯誤(1)

     這篇文章詳細說明如何建立一份有用的錯誤報告。它描述了什麼樣的資訊是
     有用的，以及這些資訊為什麼有用。

錯誤撰寫指南(2)

     撰寫一份優良錯誤報告的相關資訊。部分的文章內容是針對 Mozilla 專案，
     但它也描述了通用的好習慣。

   ---------- Footnotes ----------

   (1) https://www.chiark.greenend.org.uk/~sgtatham/bugs.html

   (2) https://bugzilla.mozilla.org/page.cgi?id=bug-writing.html


File: python.info,  Node: 開始讓自己貢獻 Python,  Prev: 使用 Python 問題追蹤系統,  Up: 處理錯誤 Bug

14.3 開始讓自己貢獻 Python
==========================

除了只是回報你所發現的錯誤之外，同樣也歡迎你提交修正它們的修補程式
(patch)。你可以在 Python 開發者指南(1)中找到如何開始修補 Python 的更多資
訊。如果你有任何問題，核心導師郵寄清單(2)是一個友善的地方，你可以在那裡
得到，關於 Python 修正錯誤的過程中，所有問題的答案。

   ---------- Footnotes ----------

   (1) https://devguide.python.org/

   (2) 
https://mail.python.org/mailman3/lists/core-mentorship.python.org/


File: python.info,  Node: 版權宣告,  Next: 沿革與授權,  Prev: 處理錯誤 Bug,  Up: Top

15 版權宣告
***********

Python 和這份說明文件的版權：

Copyright © 2001-2024 Python Software Foundation.  All rights reserved.

Copyright © 2000 BeOpen.com 保留一切權利。

Copyright © 1995-2000 Corporation for National Research Initiatives 保留
一切權利。

Copyright © 1991-1995 Stichting Mathematisch Centrum 保留一切權利。

__________________________________________________________________

完整的授權條款資訊請參見*note 沿革與授權: 4f60.。


File: python.info,  Node: 沿革與授權,  Next: Python 模組索引,  Prev: 版權宣告,  Up: Top

16 沿革與授權
*************

* Menu:

* 軟體沿革::
* 關於存取或以其他方式使用 Python 的合約條款::
* 被收錄軟體的授權與致謝::


File: python.info,  Node: 軟體沿革,  Next: 關於存取或以其他方式使用 Python 的合約條款,  Up: 沿革與授權

16.1 軟體沿革
=============

Python 是由荷蘭數學和計算機科學研究學會（CWI，見 ‘https://www.cwi.nl/’）
的 Guido van Rossum 於 1990 年代早期所創造，目的是作為一種稱為 ABC 語言
的後繼者。儘管 Python 包含了許多來自其他人的貢獻，Guido 仍是其主要作者。

1995 年，Guido 在維吉尼亞州雷斯頓的國家創新研究公司（CNRI，見
‘https://www.cnri.reston.va.us/’）繼續他在 Python 的工作，並在那裡發佈了
該軟體的多個版本。

2000 年五月，Guido 和 Python 核心開發團隊轉移到 BeOpen.com 並成立了
BeOpen PythonLabs 團隊。同年十月，PythonLabs 團隊轉移到 Digital
Creations（現為 Zope Corporation；見 ‘https://www.zope.org/’）。2001 年
，Python 軟體基金會（PSF，見 ‘https://www.python.org/psf/’）成立，這是一
個專為擁有 Python 相關的智慧財產權而創立的非營利組織。Zope Corporation 是
PSF 的一個贊助會員。

所有的 Python 版本都是開源的（有關開源的定義，參閱
‘https://opensource.org/’）。歷史上，大多數但非全部的 Python 版本，也是
GPL 相容的；以下表格總結各個版本的差異。

發佈版本             源自               年份             擁有者           GPL 相容性？
                                                                          
------------------------------------------------------------------------------------------------
                                                                          
0.9.0 至 1.2         不適用             1991-1995        CWI              是
                                                                          
                                                                          
1.3 至 1.5.2         1.2                1995-1999        CNRI             是
                                                                          
                                                                          
1.6                  1.5.2              2000             CNRI             否
                                                                          
                                                                          
2.0                  1.6                2000             BeOpen.com       否
                                                                          
                                                                          
1.6.1                1.6                2001             CNRI             否
                                                                          
                                                                          
2.1                  2.0+1.6.1          2001             PSF              否
                                                                          
                                                                          
2.0.1                2.0+1.6.1          2001             PSF              是
                                                                          
                                                                          
2.1.1                2.1+2.0.1          2001             PSF              是
                                                                          
                                                                          
2.1.2                2.1.1              2002             PSF              是
                                                                          
                                                                          
2.1.3                2.1.2              2002             PSF              是
                                                                          
                                                                          
2.2 以上             2.1.1              2001 至今        PSF              是
                                                                          

     備註: GPL 相容並不表示我們是在 GPL 下發佈 Python。不像 GPL，所有的
     Python 授權都可以讓你發佈修改後的版本，但不一定要使你的變更成為開源
     。GPL 相容的授權使得 Python 可以結合其他在 GPL 下發佈的軟體一起使用
     ；但其它的授權則不行。

感謝許多的外部志工，在 Guido 指導下的付出，使得這些版本的發佈成為可能。


File: python.info,  Node: 關於存取或以其他方式使用 Python 的合約條款,  Next: 被收錄軟體的授權與致謝,  Prev: 軟體沿革,  Up: 沿革與授權

16.2 關於存取或以其他方式使用 Python 的合約條款
===============================================

Python 軟體和說明文件的授權是基於 *note PSF 授權合約: 4f65.。

從 Python 3.8.6 開始，說明文件中的範例、程式庫和其他程式碼，是被雙重授權
(dual licensed) 於 PSF 授權合約以及 *note Zero-Clause BSD 授權: 4f66.。

有些被納入 Python 中的軟體是基於不同的授權。這些授權將會與其授權之程式碼
一起被列出。關於這些授權的不完整清單，請參閱*note
被收錄軟體的授權與致謝: 4f67.。

* Menu:

* 用於 PYTHON 3.13.0rc2 的 PSF 授權合約: 用於 PYTHON 3 13 0rc2 的 PSF 授權合約.
* 用於 PYTHON 2.0 的 BEOPEN.COM 授權合約: 用於 PYTHON 2 0 的 BEOPEN COM 授權合約.
* 用於 PYTHON 1.6.1 的 CNRI 授權合約: 用於 PYTHON 1 6 1 的 CNRI 授權合約.
* 用於 PYTHON 0.9.0 至 1.2 的 CWI 授權合約: 用於 PYTHON 0 9 0 至 1 2 的 CWI 授權合約.
* 用於 PYTHON 3.13.0rc2 說明文件內程式碼的 ZERO-CLAUSE BSD 授權: 用於 PYTHON 3 13 0rc2 說明文件內程式碼的 ZERO-CLAUSE BSD 授權.


File: python.info,  Node: 用於 PYTHON 3 13 0rc2 的 PSF 授權合約,  Next: 用於 PYTHON 2 0 的 BEOPEN COM 授權合約,  Up: 關於存取或以其他方式使用 Python 的合約條款

16.2.1 用於 PYTHON 3.13.0rc2 的 PSF 授權合約
--------------------------------------------

     1. This LICENSE AGREEMENT is between the Python Software Foundation ("PSF"), and
        the Individual or Organization ("Licensee") accessing and otherwise using Python
        3.13.0rc2 software in source or binary form and its associated documentation.

     2. Subject to the terms and conditions of this License Agreement, PSF hereby
        grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce,
        analyze, test, perform and/or display publicly, prepare derivative works,
        distribute, and otherwise use Python 3.13.0rc2 alone or in any derivative
        version, provided, however, that PSF's License Agreement and PSF's notice of
        copyright, i.e., "Copyright © 2001-2024 Python Software Foundation; All Rights
        Reserved" are retained in Python 3.13.0rc2 alone or in any derivative version
        prepared by Licensee.

     3. In the event Licensee prepares a derivative work that is based on or
        incorporates Python 3.13.0rc2 or any part thereof, and wants to make the
        derivative work available to others as provided herein, then Licensee hereby
        agrees to include in any such work a brief summary of the changes made to Python
        3.13.0rc2.

     4. PSF is making Python 3.13.0rc2 available to Licensee on an "AS IS" basis.
        PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED.  BY WAY OF
        EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND DISCLAIMS ANY REPRESENTATION OR
        WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE
        USE OF PYTHON 3.13.0rc2 WILL NOT INFRINGE ANY THIRD PARTY RIGHTS.

     5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON 3.13.0rc2
        FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF
        MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 3.13.0rc2, OR ANY DERIVATIVE
        THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.

     6. This License Agreement will automatically terminate upon a material breach of
        its terms and conditions.

     7. Nothing in this License Agreement shall be deemed to create any relationship
        of agency, partnership, or joint venture between PSF and Licensee.  This License
        Agreement does not grant permission to use PSF trademarks or trade name in a
        trademark sense to endorse or promote products or services of Licensee, or any
        third party.

     8. By copying, installing or otherwise using Python 3.13.0rc2, Licensee agrees
        to be bound by the terms and conditions of this License Agreement.


File: python.info,  Node: 用於 PYTHON 2 0 的 BEOPEN COM 授權合約,  Next: 用於 PYTHON 1 6 1 的 CNRI 授權合約,  Prev: 用於 PYTHON 3 13 0rc2 的 PSF 授權合約,  Up: 關於存取或以其他方式使用 Python 的合約條款

16.2.2 用於 PYTHON 2.0 的 BEOPEN.COM 授權合約
---------------------------------------------

BEOPEN PYTHON 開源授權合約第 1 版

     1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an office at
        160 Saratoga Avenue, Santa Clara, CA 95051, and the Individual or Organization
        ("Licensee") accessing and otherwise using this software in source or binary
        form and its associated documentation ("the Software").

     2. Subject to the terms and conditions of this BeOpen Python License Agreement,
        BeOpen hereby grants Licensee a non-exclusive, royalty-free, world-wide license
        to reproduce, analyze, test, perform and/or display publicly, prepare derivative
        works, distribute, and otherwise use the Software alone or in any derivative
        version, provided, however, that the BeOpen Python License is retained in the
        Software, alone or in any derivative version prepared by Licensee.

     3. BeOpen is making the Software available to Licensee on an "AS IS" basis.
        BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED.  BY WAY OF
        EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND DISCLAIMS ANY REPRESENTATION OR
        WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE
        USE OF THE SOFTWARE WILL NOT INFRINGE ANY THIRD PARTY RIGHTS.

     4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE SOFTWARE FOR
        ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF USING,
        MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY DERIVATIVE THEREOF, EVEN IF
        ADVISED OF THE POSSIBILITY THEREOF.

     5. This License Agreement will automatically terminate upon a material breach of
        its terms and conditions.

     6. This License Agreement shall be governed by and interpreted in all respects
        by the law of the State of California, excluding conflict of law provisions.
        Nothing in this License Agreement shall be deemed to create any relationship of
        agency, partnership, or joint venture between BeOpen and Licensee.  This License
        Agreement does not grant permission to use BeOpen trademarks or trade names in a
        trademark sense to endorse or promote products or services of Licensee, or any
        third party.  As an exception, the "BeOpen Python" logos available at
        ‘http://www.pythonlabs.com/logos.html’ may be used according to the permissions
        granted on that web page.

     7. By copying, installing or otherwise using the software, Licensee agrees to be
        bound by the terms and conditions of this License Agreement.


File: python.info,  Node: 用於 PYTHON 1 6 1 的 CNRI 授權合約,  Next: 用於 PYTHON 0 9 0 至 1 2 的 CWI 授權合約,  Prev: 用於 PYTHON 2 0 的 BEOPEN COM 授權合約,  Up: 關於存取或以其他方式使用 Python 的合約條款

16.2.3 用於 PYTHON 1.6.1 的 CNRI 授權合約
-----------------------------------------

     1. This LICENSE AGREEMENT is between the Corporation for National Research
        Initiatives, having an office at 1895 Preston White Drive, Reston, VA 20191
        ("CNRI"), and the Individual or Organization ("Licensee") accessing and
        otherwise using Python 1.6.1 software in source or binary form and its
        associated documentation.

     2. Subject to the terms and conditions of this License Agreement, CNRI hereby
        grants Licensee a nonexclusive, royalty-free, world-wide license to reproduce,
        analyze, test, perform and/or display publicly, prepare derivative works,
        distribute, and otherwise use Python 1.6.1 alone or in any derivative version,
        provided, however, that CNRI's License Agreement and CNRI's notice of copyright,
        i.e., "Copyright © 1995-2001 Corporation for National Research Initiatives; All
        Rights Reserved" are retained in Python 1.6.1 alone or in any derivative version
        prepared by Licensee.  Alternately, in lieu of CNRI's License Agreement,
        Licensee may substitute the following text (omitting the quotes): "Python 1.6.1
        is made available subject to the terms and conditions in CNRI's License
        Agreement.  This Agreement together with Python 1.6.1 may be located on the
        internet using the following unique, persistent identifier (known as a handle):
        1895.22/1013.  This Agreement may also be obtained from a proxy server on the
        internet using the following URL: ‘http://hdl.handle.net/1895.22/1013’."

     3. In the event Licensee prepares a derivative work that is based on or
        incorporates Python 1.6.1 or any part thereof, and wants to make the derivative
        work available to others as provided herein, then Licensee hereby agrees to
        include in any such work a brief summary of the changes made to Python 1.6.1.

     4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS" basis.  CNRI
        MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED.  BY WAY OF EXAMPLE,
        BUT NOT LIMITATION, CNRI MAKES NO AND DISCLAIMS ANY REPRESENTATION OR WARRANTY
        OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF
        PYTHON 1.6.1 WILL NOT INFRINGE ANY THIRD PARTY RIGHTS.

     5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON 1.6.1 FOR
        ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF
        MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1, OR ANY DERIVATIVE
        THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.

     6. This License Agreement will automatically terminate upon a material breach of
        its terms and conditions.

     7. This License Agreement shall be governed by the federal intellectual property
        law of the United States, including without limitation the federal copyright
        law, and, to the extent such U.S. federal law does not apply, by the law of the
        Commonwealth of Virginia, excluding Virginia's conflict of law provisions.
        Notwithstanding the foregoing, with regard to derivative works based on Python
        1.6.1 that incorporate non-separable material that was previously distributed
        under the GNU General Public License (GPL), the law of the Commonwealth of
        Virginia shall govern this License Agreement only as to issues arising under or
        with respect to Paragraphs 4, 5, and 7 of this License Agreement.  Nothing in
        this License Agreement shall be deemed to create any relationship of agency,
        partnership, or joint venture between CNRI and Licensee.  This License Agreement
        does not grant permission to use CNRI trademarks or trade name in a trademark
        sense to endorse or promote products or services of Licensee, or any third
        party.

     8. By clicking on the "ACCEPT" button where indicated, or by copying, installing
        or otherwise using Python 1.6.1, Licensee agrees to be bound by the terms and
        conditions of this License Agreement.


File: python.info,  Node: 用於 PYTHON 0 9 0 至 1 2 的 CWI 授權合約,  Next: 用於 PYTHON 3 13 0rc2 說明文件內程式碼的 ZERO-CLAUSE BSD 授權,  Prev: 用於 PYTHON 1 6 1 的 CNRI 授權合約,  Up: 關於存取或以其他方式使用 Python 的合約條款

16.2.4 用於 PYTHON 0.9.0 至 1.2 的 CWI 授權合約
-----------------------------------------------

     Copyright © 1991 - 1995, Stichting Mathematisch Centrum Amsterdam, The
     Netherlands.  All rights reserved.

     Permission to use, copy, modify, and distribute this software and its
     documentation for any purpose and without fee is hereby granted, provided that
     the above copyright notice appear in all copies and that both that copyright
     notice and this permission notice appear in supporting documentation, and that
     the name of Stichting Mathematisch Centrum or CWI not be used in advertising or
     publicity pertaining to distribution of the software without specific, written
     prior permission.

     STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS
     SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO
     EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT
     OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,
     DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
     ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
     SOFTWARE.


File: python.info,  Node: 用於 PYTHON 3 13 0rc2 說明文件內程式碼的 ZERO-CLAUSE BSD 授權,  Prev: 用於 PYTHON 0 9 0 至 1 2 的 CWI 授權合約,  Up: 關於存取或以其他方式使用 Python 的合約條款

16.2.5 用於 PYTHON 3.13.0rc2 說明文件內程式碼的 ZERO-CLAUSE BSD 授權
--------------------------------------------------------------------

     Permission to use, copy, modify, and/or distribute this software for any
     purpose with or without fee is hereby granted.

     THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH
     REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
     AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
     INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
     LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
     OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
     PERFORMANCE OF THIS SOFTWARE.


File: python.info,  Node: 被收錄軟體的授權與致謝,  Prev: 關於存取或以其他方式使用 Python 的合約條款,  Up: 沿革與授權

16.3 被收錄軟體的授權與致謝
===========================

本節是一個不完整但持續增加的授權與致謝清單，對象是在 Python 發佈版本中所
收錄的第三方軟體。

* Menu:

* Mersenne Twister::
* Sockets: Sockets<2>.
* 非同步 socket 服務::
* Cookie 管理::
* 執行追蹤::
* UUencode 與 UUdecode 函式::
* XML 遠端程序呼叫::
* test_epoll::
* Select kqueue::
* SipHash24::
* strtod 與 dtoa::
* OpenSSL: OpenSSL<2>.
* expat::
* libffi::
* zlib: zlib<3>.
* cfuhash::
* libmpdec::
* W3C C14N 測試套件::
* mimalloc::
* asyncio: asyncio<12>.
* Global Unbounded Sequences (GUS): Global Unbounded Sequences GUS.


File: python.info,  Node: Mersenne Twister,  Next: Sockets<2>,  Up: 被收錄軟體的授權與致謝

16.3.1 Mersenne Twister
-----------------------

*note random: a6. 模組底下的 ‘_random’ C 擴充程式包含了以
‘http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/MT2002/emt19937ar.html’
的下載內容為基礎的程式碼。以下是原始程式碼的完整聲明：

     A C-program for MT19937, with initialization improved 2002/1/26.
     Coded by Takuji Nishimura and Makoto Matsumoto.

     Before using, initialize the state by using init_genrand(seed)
     or init_by_array(init_key, key_length).

     Copyright (C) 1997 - 2002, Makoto Matsumoto and Takuji Nishimura,
     All rights reserved.

     Redistribution and use in source and binary forms, with or without
     modification, are permitted provided that the following conditions
     are met:

      1. Redistributions of source code must retain the above copyright
         notice, this list of conditions and the following disclaimer.

      2. Redistributions in binary form must reproduce the above copyright
         notice, this list of conditions and the following disclaimer in the
         documentation and/or other materials provided with the distribution.

      3. The names of its contributors may not be used to endorse or promote
         products derived from this software without specific prior written
         permission.

     THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
     "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
     LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
     A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT OWNER OR
     CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
     EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
     PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
     PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
     LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
     NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
     SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.


     Any feedback is very welcome.
     http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/emt.html
     email: m-mat @ math.sci.hiroshima-u.ac.jp (remove space)


File: python.info,  Node: Sockets<2>,  Next: 非同步 socket 服務,  Prev: Mersenne Twister,  Up: 被收錄軟體的授權與致謝

16.3.2 Sockets
--------------

*note socket: b8. 模組使用 ‘getaddrinfo()’ 和 ‘getnameinfo()’ 函式，它們
在 WIDE 專案（‘https://www.wide.ad.jp/’）內，於不同的原始檔案中被編碼：

     Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project.
     All rights reserved.

     Redistribution and use in source and binary forms, with or without
     modification, are permitted provided that the following conditions
     are met:
     1. Redistributions of source code must retain the above copyright
        notice, this list of conditions and the following disclaimer.
     2. Redistributions in binary form must reproduce the above copyright
        notice, this list of conditions and the following disclaimer in the
        documentation and/or other materials provided with the distribution.
     3. Neither the name of the project nor the names of its contributors
        may be used to endorse or promote products derived from this software
        without specific prior written permission.

     THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND
     ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
     IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
     ARE DISCLAIMED.  IN NO EVENT SHALL THE PROJECT OR CONTRIBUTORS BE LIABLE
     FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
     DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
     OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
     HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
     LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
     OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
     SUCH DAMAGE.


File: python.info,  Node: 非同步 socket 服務,  Next: Cookie 管理,  Prev: Sockets<2>,  Up: 被收錄軟體的授權與致謝

16.3.3 非同步 socket 服務
-------------------------

‘test.support.asynchat’ 和 ‘test.support.asyncore’ 模組包含以下聲明：

     Copyright 1996 by Sam Rushing

                             All Rights Reserved

     Permission to use, copy, modify, and distribute this software and
     its documentation for any purpose and without fee is hereby
     granted, provided that the above copyright notice appear in all
     copies and that both that copyright notice and this permission
     notice appear in supporting documentation, and that the name of Sam
     Rushing not be used in advertising or publicity pertaining to
     distribution of the software without specific, written prior
     permission.

     SAM RUSHING DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE,
     INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN
     NO EVENT SHALL SAM RUSHING BE LIABLE FOR ANY SPECIAL, INDIRECT OR
     CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS
     OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,
     NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
     CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.


File: python.info,  Node: Cookie 管理,  Next: 執行追蹤,  Prev: 非同步 socket 服務,  Up: 被收錄軟體的授權與致謝

16.3.4 Cookie 管理
------------------

*note http.cookies: 67. 模組包含以下聲明：

     Copyright 2000 by Timothy O'Malley <timo@alum.mit.edu>

                    All Rights Reserved

     Permission to use, copy, modify, and distribute this software
     and its documentation for any purpose and without fee is hereby
     granted, provided that the above copyright notice appear in all
     copies and that both that copyright notice and this permission
     notice appear in supporting documentation, and that the name of
     Timothy O'Malley  not be used in advertising or publicity
     pertaining to distribution of the software without specific, written
     prior permission.

     Timothy O'Malley DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS
     SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
     AND FITNESS, IN NO EVENT SHALL Timothy O'Malley BE LIABLE FOR
     ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
     WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
     WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
     ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
     PERFORMANCE OF THIS SOFTWARE.


File: python.info,  Node: 執行追蹤,  Next: UUencode 與 UUdecode 函式,  Prev: Cookie 管理,  Up: 被收錄軟體的授權與致謝

16.3.5 執行追蹤
---------------

*note trace: e6. 模組包含以下聲明：

     portions copyright 2001, Autonomous Zones Industries, Inc., all rights...
     err...  reserved and offered to the public under the terms of the
     Python 2.2 license.
     Author: Zooko O'Whielacronx
     http://zooko.com/
     mailto:zooko@zooko.com

     Copyright 2000, Mojam Media, Inc., all rights reserved.
     Author: Skip Montanaro

     Copyright 1999, Bioreason, Inc., all rights reserved.
     Author: Andrew Dalke

     Copyright 1995-1997, Automatrix, Inc., all rights reserved.
     Author: Skip Montanaro

     Copyright 1991-1995, Stichting Mathematisch Centrum, all rights reserved.


     Permission to use, copy, modify, and distribute this Python software and
     its associated documentation for any purpose without fee is hereby
     granted, provided that the above copyright notice appears in all copies,
     and that both that copyright notice and this permission notice appear in
     supporting documentation, and that the name of neither Automatrix,
     Bioreason or Mojam Media be used in advertising or publicity pertaining to
     distribution of the software without specific, written prior permission.


File: python.info,  Node: UUencode 與 UUdecode 函式,  Next: XML 遠端程序呼叫,  Prev: 執行追蹤,  Up: 被收錄軟體的授權與致謝

16.3.6 UUencode 與 UUdecode 函式
--------------------------------

The ‘uu’ codec contains the following notice:

     Copyright 1994 by Lance Ellinghouse
     Cathedral City, California Republic, United States of America.
                            All Rights Reserved
     Permission to use, copy, modify, and distribute this software and its
     documentation for any purpose and without fee is hereby granted,
     provided that the above copyright notice appear in all copies and that
     both that copyright notice and this permission notice appear in
     supporting documentation, and that the name of Lance Ellinghouse
     not be used in advertising or publicity pertaining to distribution
     of the software without specific, written prior permission.
     LANCE ELLINGHOUSE DISCLAIMS ALL WARRANTIES WITH REGARD TO
     THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
     FITNESS, IN NO EVENT SHALL LANCE ELLINGHOUSE CENTRUM BE LIABLE
     FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
     WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
     ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
     OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

     Modified by Jack Jansen, CWI, July 1995:
     - Use binascii module to do the actual line-by-line conversion
       between ascii and binary. This results in a 1000-fold speedup. The C
       version is still 5 times faster, though.
     - Arguments more compliant with Python standard


File: python.info,  Node: XML 遠端程序呼叫,  Next: test_epoll,  Prev: UUencode 與 UUdecode 函式,  Up: 被收錄軟體的授權與致謝

16.3.7 XML 遠端程序呼叫
-----------------------

*note xmlrpc.client: 114. 模組包含以下聲明：

         The XML-RPC client interface is

     Copyright (c) 1999-2002 by Secret Labs AB
     Copyright (c) 1999-2002 by Fredrik Lundh

     By obtaining, using, and/or copying this software and/or its
     associated documentation, you agree that you have read, understood,
     and will comply with the following terms and conditions:

     Permission to use, copy, modify, and distribute this software and
     its associated documentation for any purpose and without fee is
     hereby granted, provided that the above copyright notice appears in
     all copies, and that both that copyright notice and this permission
     notice appear in supporting documentation, and that the name of
     Secret Labs AB or the author not be used in advertising or publicity
     pertaining to distribution of the software without specific, written
     prior permission.

     SECRET LABS AB AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD
     TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANT-
     ABILITY AND FITNESS.  IN NO EVENT SHALL SECRET LABS AB OR THE AUTHOR
     BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY
     DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
     WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
     ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE
     OF THIS SOFTWARE.


File: python.info,  Node: test_epoll,  Next: Select kqueue,  Prev: XML 遠端程序呼叫,  Up: 被收錄軟體的授權與致謝

16.3.8 test_epoll
-----------------

‘test.test_epoll’ 模組包含以下聲明：

     Copyright (c) 2001-2006 Twisted Matrix Laboratories.

     Permission is hereby granted, free of charge, to any person obtaining
     a copy of this software and associated documentation files (the
     "Software"), to deal in the Software without restriction, including
     without limitation the rights to use, copy, modify, merge, publish,
     distribute, sublicense, and/or sell copies of the Software, and to
     permit persons to whom the Software is furnished to do so, subject to
     the following conditions:

     The above copyright notice and this permission notice shall be
     included in all copies or substantial portions of the Software.

     THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
     EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
     MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
     NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
     LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
     OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
     WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.


File: python.info,  Node: Select kqueue,  Next: SipHash24,  Prev: test_epoll,  Up: 被收錄軟體的授權與致謝

16.3.9 Select kqueue
--------------------

*note select: af. 模組對於 kqueue 介面包含以下聲明：

     Copyright (c) 2000 Doug White, 2006 James Knight, 2007 Christian Heimes
     All rights reserved.

     Redistribution and use in source and binary forms, with or without
     modification, are permitted provided that the following conditions
     are met:
     1. Redistributions of source code must retain the above copyright
        notice, this list of conditions and the following disclaimer.
     2. Redistributions in binary form must reproduce the above copyright
        notice, this list of conditions and the following disclaimer in the
        documentation and/or other materials provided with the distribution.

     THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
     ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
     IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
     ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
     FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
     DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
     OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
     HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
     LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
     OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
     SUCH DAMAGE.


File: python.info,  Node: SipHash24,  Next: strtod 與 dtoa,  Prev: Select kqueue,  Up: 被收錄軟體的授權與致謝

16.3.10 SipHash24
-----------------

‘Python/pyhash.c’ 檔案包含 Marek Majkowski' 基於 Dan Bernstein 的
SipHash24 演算法的實作。它包含以下聲明：

     <MIT License>
     Copyright (c) 2013  Marek Majkowski <marek@popcount.org>

     Permission is hereby granted, free of charge, to any person obtaining a copy
     of this software and associated documentation files (the "Software"), to deal
     in the Software without restriction, including without limitation the rights
     to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
     copies of the Software, and to permit persons to whom the Software is
     furnished to do so, subject to the following conditions:

     The above copyright notice and this permission notice shall be included in
     all copies or substantial portions of the Software.
     </MIT License>

     Original location:
        https://github.com/majek/csiphash/

     Solution inspired by code from:
        Samuel Neves (supercop/crypto_auth/siphash24/little)
        djb (supercop/crypto_auth/siphash24/little2)
        Jean-Philippe Aumasson (https://131002.net/siphash/siphash24.c)


File: python.info,  Node: strtod 與 dtoa,  Next: OpenSSL<2>,  Prev: SipHash24,  Up: 被收錄軟體的授權與致謝

16.3.11 strtod 與 dtoa
----------------------

‘Python/dtoa.c’ 檔案提供了 C 的 dtoa 和 strtod 函式，用於將 C 的雙精度浮
點數和字串互相轉換。該檔案是衍生自 David M. Gay 建立的同名檔案，後者現在
可以從
‘https://web.archive.org/web/20220517033456/http://www.netlib.org/fp/dtoa.c’
下載。於 2009 年 3 月 16 日所檢索的原始檔案包含以下版權與授權聲明：

     /****************************************************************
      *
      * The author of this software is David M. Gay.
      *
      * Copyright (c) 1991, 2000, 2001 by Lucent Technologies.
      *
      * Permission to use, copy, modify, and distribute this software for any
      * purpose without fee is hereby granted, provided that this entire notice
      * is included in all copies of any software which is or includes a copy
      * or modification of this software and in all copies of the supporting
      * documentation for such software.
      *
      * THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED
      * WARRANTY.  IN PARTICULAR, NEITHER THE AUTHOR NOR LUCENT MAKES ANY
      * REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY
      * OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE.
      *
      ***************************************************************/


File: python.info,  Node: OpenSSL<2>,  Next: expat,  Prev: strtod 與 dtoa,  Up: 被收錄軟體的授權與致謝

16.3.12 OpenSSL
---------------

The modules *note hashlib: 5e, *note posix: 9b. and *note ssl: bb. use
the OpenSSL library for added performance if made available by the
operating system.  Additionally, the Windows and macOS installers for
Python may include a copy of the OpenSSL libraries, so we include a copy
of the OpenSSL license here.  For the OpenSSL 3.0 release, and later
releases derived from that, the Apache License v2 applies:

                                   Apache License
                             Version 2.0, January 2004
                          https://www.apache.org/licenses/

     TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

     1. Definitions.

        "License" shall mean the terms and conditions for use, reproduction,
        and distribution as defined by Sections 1 through 9 of this document.

        "Licensor" shall mean the copyright owner or entity authorized by
        the copyright owner that is granting the License.

        "Legal Entity" shall mean the union of the acting entity and all
        other entities that control, are controlled by, or are under common
        control with that entity. For the purposes of this definition,
        "control" means (i) the power, direct or indirect, to cause the
        direction or management of such entity, whether by contract or
        otherwise, or (ii) ownership of fifty percent (50%) or more of the
        outstanding shares, or (iii) beneficial ownership of such entity.

        "You" (or "Your") shall mean an individual or Legal Entity
        exercising permissions granted by this License.

        "Source" form shall mean the preferred form for making modifications,
        including but not limited to software source code, documentation
        source, and configuration files.

        "Object" form shall mean any form resulting from mechanical
        transformation or translation of a Source form, including but
        not limited to compiled object code, generated documentation,
        and conversions to other media types.

        "Work" shall mean the work of authorship, whether in Source or
        Object form, made available under the License, as indicated by a
        copyright notice that is included in or attached to the work
        (an example is provided in the Appendix below).

        "Derivative Works" shall mean any work, whether in Source or Object
        form, that is based on (or derived from) the Work and for which the
        editorial revisions, annotations, elaborations, or other modifications
        represent, as a whole, an original work of authorship. For the purposes
        of this License, Derivative Works shall not include works that remain
        separable from, or merely link (or bind by name) to the interfaces of,
        the Work and Derivative Works thereof.

        "Contribution" shall mean any work of authorship, including
        the original version of the Work and any modifications or additions
        to that Work or Derivative Works thereof, that is intentionally
        submitted to Licensor for inclusion in the Work by the copyright owner
        or by an individual or Legal Entity authorized to submit on behalf of
        the copyright owner. For the purposes of this definition, "submitted"
        means any form of electronic, verbal, or written communication sent
        to the Licensor or its representatives, including but not limited to
        communication on electronic mailing lists, source code control systems,
        and issue tracking systems that are managed by, or on behalf of, the
        Licensor for the purpose of discussing and improving the Work, but
        excluding communication that is conspicuously marked or otherwise
        designated in writing by the copyright owner as "Not a Contribution."

        "Contributor" shall mean Licensor and any individual or Legal Entity
        on behalf of whom a Contribution has been received by Licensor and
        subsequently incorporated within the Work.

     2. Grant of Copyright License. Subject to the terms and conditions of
        this License, each Contributor hereby grants to You a perpetual,
        worldwide, non-exclusive, no-charge, royalty-free, irrevocable
        copyright license to reproduce, prepare Derivative Works of,
        publicly display, publicly perform, sublicense, and distribute the
        Work and such Derivative Works in Source or Object form.

     3. Grant of Patent License. Subject to the terms and conditions of
        this License, each Contributor hereby grants to You a perpetual,
        worldwide, non-exclusive, no-charge, royalty-free, irrevocable
        (except as stated in this section) patent license to make, have made,
        use, offer to sell, sell, import, and otherwise transfer the Work,
        where such license applies only to those patent claims licensable
        by such Contributor that are necessarily infringed by their
        Contribution(s) alone or by combination of their Contribution(s)
        with the Work to which such Contribution(s) was submitted. If You
        institute patent litigation against any entity (including a
        cross-claim or counterclaim in a lawsuit) alleging that the Work
        or a Contribution incorporated within the Work constitutes direct
        or contributory patent infringement, then any patent licenses
        granted to You under this License for that Work shall terminate
        as of the date such litigation is filed.

     4. Redistribution. You may reproduce and distribute copies of the
        Work or Derivative Works thereof in any medium, with or without
        modifications, and in Source or Object form, provided that You
        meet the following conditions:

        (a) You must give any other recipients of the Work or
            Derivative Works a copy of this License; and

        (b) You must cause any modified files to carry prominent notices
            stating that You changed the files; and

        (c) You must retain, in the Source form of any Derivative Works
            that You distribute, all copyright, patent, trademark, and
            attribution notices from the Source form of the Work,
            excluding those notices that do not pertain to any part of
            the Derivative Works; and

        (d) If the Work includes a "NOTICE" text file as part of its
            distribution, then any Derivative Works that You distribute must
            include a readable copy of the attribution notices contained
            within such NOTICE file, excluding those notices that do not
            pertain to any part of the Derivative Works, in at least one
            of the following places: within a NOTICE text file distributed
            as part of the Derivative Works; within the Source form or
            documentation, if provided along with the Derivative Works; or,
            within a display generated by the Derivative Works, if and
            wherever such third-party notices normally appear. The contents
            of the NOTICE file are for informational purposes only and
            do not modify the License. You may add Your own attribution
            notices within Derivative Works that You distribute, alongside
            or as an addendum to the NOTICE text from the Work, provided
            that such additional attribution notices cannot be construed
            as modifying the License.

        You may add Your own copyright statement to Your modifications and
        may provide additional or different license terms and conditions
        for use, reproduction, or distribution of Your modifications, or
        for any such Derivative Works as a whole, provided Your use,
        reproduction, and distribution of the Work otherwise complies with
        the conditions stated in this License.

     5. Submission of Contributions. Unless You explicitly state otherwise,
        any Contribution intentionally submitted for inclusion in the Work
        by You to the Licensor shall be under the terms and conditions of
        this License, without any additional terms or conditions.
        Notwithstanding the above, nothing herein shall supersede or modify
        the terms of any separate license agreement you may have executed
        with Licensor regarding such Contributions.

     6. Trademarks. This License does not grant permission to use the trade
        names, trademarks, service marks, or product names of the Licensor,
        except as required for reasonable and customary use in describing the
        origin of the Work and reproducing the content of the NOTICE file.

     7. Disclaimer of Warranty. Unless required by applicable law or
        agreed to in writing, Licensor provides the Work (and each
        Contributor provides its Contributions) on an "AS IS" BASIS,
        WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
        implied, including, without limitation, any warranties or conditions
        of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
        PARTICULAR PURPOSE. You are solely responsible for determining the
        appropriateness of using or redistributing the Work and assume any
        risks associated with Your exercise of permissions under this License.

     8. Limitation of Liability. In no event and under no legal theory,
        whether in tort (including negligence), contract, or otherwise,
        unless required by applicable law (such as deliberate and grossly
        negligent acts) or agreed to in writing, shall any Contributor be
        liable to You for damages, including any direct, indirect, special,
        incidental, or consequential damages of any character arising as a
        result of this License or out of the use or inability to use the
        Work (including but not limited to damages for loss of goodwill,
        work stoppage, computer failure or malfunction, or any and all
        other commercial damages or losses), even if such Contributor
        has been advised of the possibility of such damages.

     9. Accepting Warranty or Additional Liability. While redistributing
        the Work or Derivative Works thereof, You may choose to offer,
        and charge a fee for, acceptance of support, warranty, indemnity,
        or other liability obligations and/or rights consistent with this
        License. However, in accepting such obligations, You may act only
        on Your own behalf and on Your sole responsibility, not on behalf
        of any other Contributor, and only if You agree to indemnify,
        defend, and hold each Contributor harmless for any liability
        incurred by, or claims asserted against, such Contributor by reason
        of your accepting any such warranty or additional liability.

     END OF TERMS AND CONDITIONS


File: python.info,  Node: expat,  Next: libffi,  Prev: OpenSSL<2>,  Up: 被收錄軟體的授權與致謝

16.3.13 expat
-------------

除非在建置 *note pyexpat: 10d. 擴充時設定為 ‘--with-system-expat’，否則
該擴充會用一個內含 expat 原始碼的副本來建置：

     Copyright (c) 1998, 1999, 2000 Thai Open Source Software Center Ltd
                                    and Clark Cooper

     Permission is hereby granted, free of charge, to any person obtaining
     a copy of this software and associated documentation files (the
     "Software"), to deal in the Software without restriction, including
     without limitation the rights to use, copy, modify, merge, publish,
     distribute, sublicense, and/or sell copies of the Software, and to
     permit persons to whom the Software is furnished to do so, subject to
     the following conditions:

     The above copyright notice and this permission notice shall be included
     in all copies or substantial portions of the Software.

     THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
     EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
     MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
     IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
     CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
     TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
     SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.


File: python.info,  Node: libffi,  Next: zlib<3>,  Prev: expat,  Up: 被收錄軟體的授權與致謝

16.3.14 libffi
--------------

除非在建置 ‘_ctypes’ 模組底下 ‘_ctypes’ 擴充程式時設定為
‘--with-system-libffi’，否則該擴充會用一個內含 libffi 原始碼的副本來建置
：

     Copyright (c) 1996-2008  Red Hat, Inc and others.

     Permission is hereby granted, free of charge, to any person obtaining
     a copy of this software and associated documentation files (the
     ``Software''), to deal in the Software without restriction, including
     without limitation the rights to use, copy, modify, merge, publish,
     distribute, sublicense, and/or sell copies of the Software, and to
     permit persons to whom the Software is furnished to do so, subject to
     the following conditions:

     The above copyright notice and this permission notice shall be included
     in all copies or substantial portions of the Software.

     THE SOFTWARE IS PROVIDED ``AS IS'', WITHOUT WARRANTY OF ANY KIND,
     EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
     MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
     NONINFRINGEMENT.  IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
     HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
     WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
     OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
     DEALINGS IN THE SOFTWARE.


File: python.info,  Node: zlib<3>,  Next: cfuhash,  Prev: libffi,  Up: 被收錄軟體的授權與致謝

16.3.15 zlib
------------

如果在系統上找到的 zlib 版本太舊以致於無法用於建置 *note zlib: 119. 擴充
，則該擴充會用一個內含 zlib 原始碼的副本來建置：

     Copyright (C) 1995-2011 Jean-loup Gailly and Mark Adler

     This software is provided 'as-is', without any express or implied
     warranty.  In no event will the authors be held liable for any damages
     arising from the use of this software.

     Permission is granted to anyone to use this software for any purpose,
     including commercial applications, and to alter it and redistribute it
     freely, subject to the following restrictions:

     1. The origin of this software must not be misrepresented; you must not
        claim that you wrote the original software. If you use this software
        in a product, an acknowledgment in the product documentation would be
        appreciated but is not required.

     2. Altered source versions must be plainly marked as such, and must not be
        misrepresented as being the original software.

     3. This notice may not be removed or altered from any source distribution.

     Jean-loup Gailly        Mark Adler
     jloup@gzip.org          madler@alumni.caltech.edu


File: python.info,  Node: cfuhash,  Next: libmpdec,  Prev: zlib<3>,  Up: 被收錄軟體的授權與致謝

16.3.16 cfuhash
---------------

*note tracemalloc: e8. 使用的雜湊表 (hash table) 實作，是以 cfuhash 專案
為基礎：

     Copyright (c) 2005 Don Owens
     All rights reserved.

     This code is released under the BSD license:

     Redistribution and use in source and binary forms, with or without
     modification, are permitted provided that the following conditions
     are met:

       * Redistributions of source code must retain the above copyright
         notice, this list of conditions and the following disclaimer.

       * Redistributions in binary form must reproduce the above
         copyright notice, this list of conditions and the following
         disclaimer in the documentation and/or other materials provided
         with the distribution.

       * Neither the name of the author nor the names of its
         contributors may be used to endorse or promote products derived
         from this software without specific prior written permission.

     THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
     "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
     LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
     FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
     COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
     INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
     (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
     SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
     HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
     STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
     ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
     OF THE POSSIBILITY OF SUCH DAMAGE.


File: python.info,  Node: libmpdec,  Next: W3C C14N 測試套件,  Prev: cfuhash,  Up: 被收錄軟體的授權與致謝

16.3.17 libmpdec
----------------

除非在建置 *note decimal: 2e. 模組底下 ‘_decimal’ C 擴充程式時設定為
‘--with-system-libmpdec’，否則該模組會用一個內含 libmpdec 函式庫的副本來
建置：

     Copyright (c) 2008-2020 Stefan Krah. All rights reserved.

     Redistribution and use in source and binary forms, with or without
     modification, are permitted provided that the following conditions
     are met:

     1. Redistributions of source code must retain the above copyright
        notice, this list of conditions and the following disclaimer.

     2. Redistributions in binary form must reproduce the above copyright
        notice, this list of conditions and the following disclaimer in the
        documentation and/or other materials provided with the distribution.

     THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND
     ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
     IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
     ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
     FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
     DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
     OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
     HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
     LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
     OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
     SUCH DAMAGE.


File: python.info,  Node: W3C C14N 測試套件,  Next: mimalloc,  Prev: libmpdec,  Up: 被收錄軟體的授權與致謝

16.3.18 W3C C14N 測試套件
-------------------------

*note test: cb. 程式包中的 C14N 2.0 測試套件
(‘Lib/test/xmltestdata/c14n-20/’) 是從 W3C 網站
‘https://www.w3.org/TR/xml-c14n2-testcases/’ 被檢索，且是基於 3-clause
BSD 授權被發佈：

     Copyright (c) 2013 W3C(R) (MIT, ERCIM, Keio, Beihang),
     All Rights Reserved.

     Redistribution and use in source and binary forms, with or without
     modification, are permitted provided that the following conditions
     are met:

     * Redistributions of works must retain the original copyright notice,
       this list of conditions and the following disclaimer.
     * Redistributions in binary form must reproduce the original copyright
       notice, this list of conditions and the following disclaimer in the
       documentation and/or other materials provided with the distribution.
     * Neither the name of the W3C nor the names of its contributors may be
       used to endorse or promote products derived from this work without
       specific prior written permission.

     THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
     "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
     LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
     A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
     OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
     SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
     LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
     DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
     THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
     (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
     OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.


File: python.info,  Node: mimalloc,  Next: asyncio<12>,  Prev: W3C C14N 測試套件,  Up: 被收錄軟體的授權與致謝

16.3.19 mimalloc
----------------

MIT License:

     Copyright (c) 2018-2021 Microsoft Corporation, Daan Leijen

     Permission is hereby granted, free of charge, to any person obtaining a copy
     of this software and associated documentation files (the "Software"), to deal
     in the Software without restriction, including without limitation the rights
     to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
     copies of the Software, and to permit persons to whom the Software is
     furnished to do so, subject to the following conditions:

     The above copyright notice and this permission notice shall be included in all
     copies or substantial portions of the Software.

     THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
     IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
     FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
     AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
     LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
     OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
     SOFTWARE.


File: python.info,  Node: asyncio<12>,  Next: Global Unbounded Sequences GUS,  Prev: mimalloc,  Up: 被收錄軟體的授權與致謝

16.3.20 asyncio
---------------

*note asyncio: 8. 模組的部分內容是從 uvloop 0.16(1) 中收錄過來，其基於
MIT 授權來發佈：

     Copyright (c) 2015-2021 MagicStack Inc.  http://magic.io

     Permission is hereby granted, free of charge, to any person obtaining
     a copy of this software and associated documentation files (the
     "Software"), to deal in the Software without restriction, including
     without limitation the rights to use, copy, modify, merge, publish,
     distribute, sublicense, and/or sell copies of the Software, and to
     permit persons to whom the Software is furnished to do so, subject to
     the following conditions:

     The above copyright notice and this permission notice shall be
     included in all copies or substantial portions of the Software.

     THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
     EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
     MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
     NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
     LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
     OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
     WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

   ---------- Footnotes ----------

   (1) https://github.com/MagicStack/uvloop/tree/v0.16.0


File: python.info,  Node: Global Unbounded Sequences GUS,  Prev: asyncio<12>,  Up: 被收錄軟體的授權與致謝

16.3.21 Global Unbounded Sequences (GUS)
----------------------------------------

The file ‘Python/qsbr.c’ is adapted from FreeBSD's "Global Unbounded
Sequences" safe memory reclamation scheme in subr_smr.c(1).  The file is
distributed under the 2-Clause BSD License:

     Copyright (c) 2019,2020 Jeffrey Roberson <jeff@FreeBSD.org>

     Redistribution and use in source and binary forms, with or without
     modification, are permitted provided that the following conditions
     are met:
     1. Redistributions of source code must retain the above copyright
        notice unmodified, this list of conditions, and the following
        disclaimer.
     2. Redistributions in binary form must reproduce the above copyright
        notice, this list of conditions and the following disclaimer in the
        documentation and/or other materials provided with the distribution.

     THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
     IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
     OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
     IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
     INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
     NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
     DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
     THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
     (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
     THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

   ---------- Footnotes ----------

   (1) 
https://github.com/freebsd/freebsd-src/blob/main/sys/kern/subr_smr.c


File: python.info,  Node: Python 模組索引,  Next: 索引,  Prev: 沿革與授權,  Up: Top

Python 模組索引
***************

* Menu:

* __future__: 0. Future statement definitions
* __main__: 1. The environment where top-level code is run. Covers
                        command-line interfaces, import-time
                        behavior, and ''__name__ ==
                        '__main__'''.
* _thread: 2. Low-level threading API.
* _tkinter: 3. A binary module that contains the low-level interface
                        to Tcl/Tk.
* abc: 4. Abstract base classes according to :pep:'3119'.
* argparse: 5. Command-line option and argument parsing library.
* array: 6. Space efficient arrays of uniformly typed numeric
                        values.
* ast: 7. Abstract Syntax Tree classes and manipulation.
* asyncio: 8. Asynchronous I/O.
* atexit: 9. Register and execute cleanup functions.
* base64: a. RFC 4648: Base16, Base32, Base64 Data
                        Encodings; Base85 and Ascii85
* bdb: b. Debugger framework.
* binascii: c. Tools for converting between binary and various ASCII-
                        encoded binary representations.
* bisect: d. Array bisection algorithms for binary searching.
* builtins: e. The module that provides the built-in namespace.
* bz2: f. Interfaces for bzip2 compression and decompression.
* calendar: 10. Functions for working with calendars, including
                        some emulation of the Unix cal program.
* cmath: 11. Mathematical functions for complex numbers.
* cmd: 12. Build line-oriented command interpreters.
* code: 13. Facilities to implement read-eval-print loops.
* codecs: 14. Encode and decode data and streams.
* codeop: 15. Compile (possibly incomplete) Python code.
* collections: 16. Container datatypes
* collections.abc: 17. Abstract base classes for containers
* colorsys: 18. Conversion functions between RGB and other color
                        systems.
* compileall: 19. Tools for byte-compiling all Python source files in a
                        directory tree.
* concurrent.futures: 1a. Execute computations concurrently using threads or
                        processes.
* configparser: 1b. Configuration file parser.
* contextlib: 1c. Utilities for with-statement contexts.
* contextvars: 1d. Context Variables
* copy: 1e. Shallow and deep copy operations.
* copyreg: 1f. Register pickle support functions.
* cProfile: 20.
* csv: 21. Write and read tabular data to and from delimited
                        files.
* ctypes: 22. A foreign function library for Python.
* curses: 23. An interface to the curses library, providing
                        portable terminal handling.
* curses.ascii: 24. Constants and set-membership functions for ASCII
                        characters.
* curses.panel: 25. A panel stack extension that adds depth to curses
                        windows.
* curses.textpad: 26. Emacs-like input editing in a curses window.
* dataclasses: 27. Generate special methods on user-defined classes.
* datetime: 28. Basic date and time types.
* dbm: 29. Interfaces to various Unix "database" formats.
* dbm.dumb: 2a. Portable implementation of the simple DBM interface.
* dbm.gnu: 2b. GNU database manager
* dbm.ndbm: 2c. The New Database Manager
* dbm.sqlite3: 2d. SQLite backend for dbm
* decimal: 2e. Implementation of the General Decimal Arithmetic
                        Specification.
* difflib: 2f. Helpers for computing differences between objects.
* dis: 30. Disassembler for Python bytecode.
* doctest: 31. Test pieces of code within docstrings.
* email: 32. Package supporting the parsing,
                        manipulating, and generating email messages.
* email.charset: 33. Character Sets
* email.contentmanager: 34. Storing and Retrieving Content from MIME Parts
* email.encoders: 35. Encoders for email message payloads.
* email.errors: 36. The exception classes used by the email package.
* email.generator: 37. Generate flat text email messages from a message
                        structure.
* email.header: 38. Representing non-ASCII headers
* email.headerregistry: 39. Automatic Parsing of headers based on the field name
* email.iterators: 3a. Iterate over a message object tree.
* email.message: 3b. The base class representing email messages.
* email.mime: 3c. Build MIME messages.
* email.mime.application: 3d.
* email.mime.audio: 3e.
* email.mime.base: 3f.
* email.mime.image: 40.
* email.mime.message: 41.
* email.mime.multipart: 42.
* email.mime.nonmultipart: 43.
* email.mime.text: 44.
* email.parser: 45. Parse flat text email messages to produce a message
                        object structure.
* email.policy: 46. Controlling the parsing and generating of messages
* email.utils: 47. Miscellaneous email package utilities.
* encodings.idna: 48. Internationalized Domain Names implementation
* encodings.mbcs: 49. Windows ANSI codepage
* encodings.utf_8_sig: 4a. UTF-8 codec with BOM signature
* ensurepip: 4b. Bootstrapping the "pip" installer into an existing
                        Python installation or virtual environment.
* enum: 4c. Implementation of an enumeration class.
* errno: 4d. Standard errno system symbols.
* faulthandler: 4e. Dump the Python traceback.
* fcntl: 4f. The fcntl() and ioctl() system calls.
* filecmp: 50. Compare files efficiently.
* fileinput: 51. Loop over standard input or a list of files.
* fnmatch: 52. Unix shell style filename pattern matching.
* fractions: 53. Rational numbers.
* ftplib: 54. FTP protocol client (requires sockets).
* functools: 55. Higher-order functions and operations on callable
                        objects.
* gc: 56. Interface to the cycle-detecting garbage collector.
* getopt: 57. Portable parser for command line options; support both
                        short and long option names.
* getpass: 58. Portable reading of passwords and retrieval of the
                        userid.
* gettext: 59. Multilingual internationalization services.
* glob: 5a. Unix shell style pathname pattern expansion.
* graphlib: 5b. Functionality to operate with graph-like structures
* grp: 5c. The group database (getgrnam() and friends).
* gzip: 5d. Interfaces for gzip compression and decompression
                        using file objects.
* hashlib: 5e. Secure hash and message digest algorithms.
* heapq: 5f. Heap queue algorithm (a.k.a. priority queue).
* hmac: 60. Keyed-Hashing for Message Authentication (HMAC)
                        implementation
* html: 61. Helpers for manipulating HTML.
* html.entities: 62. Definitions of HTML general entities.
* html.parser: 63. A simple parser that can handle HTML and XHTML.
* http: 64. HTTP status codes and messages
* http.client: 65. HTTP and HTTPS protocol client (requires sockets).
* http.cookiejar: 66. Classes for automatic handling of HTTP cookies.
* http.cookies: 67. Support for HTTP state management (cookies).
* http.server: 68. HTTP server and request handlers.
* idlelib: 69. Implementation package for the IDLE shell/editor.
* imaplib: 6a. IMAP4 protocol client (requires sockets).
* importlib: 6b. The implementation of the import machinery.
* importlib.abc: 6c. Abstract base classes related to import
* importlib.machinery: 6d. Importers and path hooks
* importlib.metadata: 6e. Accessing package metadata
* importlib.resources: 6f. Package resource reading, opening, and
                        access
* importlib.resources.abc: 70. Abstract base classes for resources
* importlib.util: 71. Utility code for importers
* inspect: 72. Extract information and source code from live objects.
* io: 73. Core tools for working with streams.
* ipaddress: 74. IPv4/IPv6 manipulation library.
* itertools: 75. Functions creating iterators for efficient looping.
* json: 76. Encode and decode the JSON format.
* json.tool: 77. A command line to validate and pretty-print JSON.
* keyword: 78. Test whether a string is a keyword in Python.
* linecache: 79. Provides random access to individual lines from text
                        files.
* locale: 7a. Internationalization services.
* logging: 7b. Flexible event logging system for applications.
* logging.config: 7c. Configuration of the logging module.
* logging.handlers: 7d. Handlers for the logging module.
* lzma: 7e. A Python wrapper for the liblzma compression library.
* mailbox: 7f. Manipulate mailboxes in various formats
* marshal: 80. Convert Python objects to streams of bytes and back
                        (with different constraints).
* math: 81. Mathematical functions (sin() etc.).
* mimetypes: 82. Mapping of filename extensions to MIME types.
* mmap: 83. Interface to memory-mapped files for Unix and Windows.
* modulefinder: 84. Find modules used by a script.
* msvcrt: 85. Miscellaneous useful routines from the MS VC++
                        runtime.
* multiprocessing: 86. Process-based parallelism.
* multiprocessing.connection: 87. API for dealing with sockets.
* multiprocessing.dummy: 88. Dumb wrapper around threading.
* multiprocessing.managers: 89. Share data between process with shared objects.
* multiprocessing.pool: 8a. Create pools of processes.
* multiprocessing.shared_memory: 8b. Provides shared memory for direct access
                                 across processes.
* multiprocessing.sharedctypes: 8c. Allocate ctypes objects from shared memory.
* netrc: 8d. Loading of .netrc files.
* numbers: 8e. Numeric abstract base classes (Complex,
                        Real, Integral, etc.).
* operator: 8f. Functions corresponding to the standard operators.
* optparse: 90. Command-line option parsing library.
* os: 91. Miscellaneous operating system interfaces.
* os.path: 92. Operations on pathnames.
* pathlib: 93. Object-oriented filesystem paths
* pdb: 94. The Python debugger for interactive interpreters.
* pickle: 95. Convert Python objects to streams of bytes and back.
* pickletools: 96. Contains extensive comments about the pickle protocols
                        and pickle-machine opcodes, as well as some
                        useful functions.
* pkgutil: 97. Utilities for the import system.
* platform: 98. Retrieves as much platform identifying data as
                        possible.
* plistlib: 99. Generate and parse Apple plist files.
* poplib: 9a. POP3 protocol client (requires sockets).
* posix: 9b. The most common POSIX system calls (normally used via
                        module os).
* pprint: 9c. Data pretty printer.
* profile: 9d. Python source profiler.
* pstats: 9e. Statistics object for use with the profiler.
* pty: 9f. Pseudo-Terminal Handling for Unix.
* pwd: a0. The password database (getpwnam() and friends).
* py_compile: a1. Generate byte-code files from Python source files.
* pyclbr: a2. Supports information extraction for a Python module
                        browser.
* pydoc: a3. Documentation generator and online help system.
* queue: a4. A synchronized queue class.
* quopri: a5. Encode and decode files using the MIME quoted-
                        printable encoding.
* random: a6. Generate pseudo-random numbers with various common
                        distributions.
* re: a7. Regular expression operations.
* readline: a8. GNU readline support for Python.
* reprlib: a9. Alternate repr() implementation with size limits.
* resource: aa. An interface to provide resource usage information on
                        the current process.
* rlcompleter: ab. Python identifier completion, suitable for the
                        GNU readline library.
* runpy: ac. Locate and run Python modules without importing them
                        first.
* sched: ad. General purpose event scheduler.
* secrets: ae. Generate secure random numbers for managing secrets.
* select: af. Wait for I/O completion on multiple streams.
* selectors: b0. High-level I/O multiplexing.
* shelve: b1. Python object persistence.
* shlex: b2. Simple lexical analysis for Unix shell-like languages.
* shutil: b3. High-level file operations, including copying.
* signal: b4. Set handlers for asynchronous events.
* site: b5. Module responsible for site-specific configuration.
* sitecustomize: b6.
* smtplib: b7. SMTP protocol client (requires sockets).
* socket: b8. Low-level networking interface.
* socketserver: b9. A framework for network servers.
* sqlite3: ba. A DB-API 2.0 implementation using SQLite 3.x.
* ssl: bb. TLS/SSL wrapper for socket objects
* stat: bc. Utilities for interpreting the results of
                        os.stat(), os.lstat() and os.fstat().
* statistics: bd. Mathematical statistics functions
* string: be. Common string operations.
* stringprep: bf. String preparation, as per RFC 3453
* struct: c0. Interpret bytes as packed binary data.
* subprocess: c1. Subprocess management.
* symtable: c2. Interface to the compiler's internal symbol tables.
* sys: c3. Access system-specific parameters and functions.
* sys.monitoring: c4. Access and control event monitoring
* sysconfig: c5. Python's configuration information
* syslog: c6. An interface to the Unix syslog library routines.
* tabnanny: c7. Tool for detecting white space related problems in
                        Python source files in a directory tree.
* tarfile: c8. Read and write tar-format archive files.
* tempfile: c9. Generate temporary files and directories.
* termios: ca. POSIX style tty control.
* test: cb. Regression tests package containing the testing suite
                        for Python.
* test.regrtest: cc. Drives the regression test suite.
* test.support: cd. Support for Python's regression test suite.
* test.support.bytecode_helper: ce. Support tools for testing correct bytecode
                                generation.
* test.support.import_helper: cf. Support for import tests.
* test.support.os_helper: d0. Support for os tests.
* test.support.script_helper: d1. Support for Python's script execution tests.
* test.support.socket_helper: d2. Support for socket tests.
* test.support.threading_helper: d3. Support for threading tests.
* test.support.warnings_helper: d4. Support for warnings tests.
* textwrap: d5. Text wrapping and filling
* threading: d6. Thread-based parallelism.
* time: d7. Time access and conversions.
* timeit: d8. Measure the execution time of small code snippets.
* tkinter: d9. Interface to Tcl/Tk for graphical user interfaces
* tkinter.colorchooser: da. Color choosing dialog
* tkinter.commondialog: db. Tkinter base class for dialogs
* tkinter.dnd: dc. Tkinter drag-and-drop interface
* tkinter.filedialog: dd. Dialog classes for file selection
* tkinter.font: de. Tkinter font-wrapping class
* tkinter.messagebox: df. Various types of alert dialogs
* tkinter.scrolledtext: e0. Text widget with a vertical scroll bar.
* tkinter.simpledialog: e1. Simple dialog windows
* tkinter.ttk: e2. Tk themed widget set
* token: e3. Constants representing terminal nodes of the parse
                        tree.
* tokenize: e4. Lexical scanner for Python source code.
* tomllib: e5. Parse TOML files.
* trace: e6. Trace or track Python statement execution.
* traceback: e7. Print or retrieve a stack traceback.
* tracemalloc: e8. Trace memory allocations.
* tty: e9. Utility functions that perform common terminal control
                        operations.
* turtle: ea. An educational framework for simple graphics
                        applications
* turtledemo: eb. A viewer for example turtle scripts
* types: ec. Names for built-in types.
* typing: ed. Support for type hints (see :pep:'484').
* unicodedata: ee. Access the Unicode Database.
* unittest: ef. Unit testing framework for Python.
* unittest.mock: f0. Mock object library.
* urllib: f1.
* urllib.error: f2. Exception classes raised by urllib.request.
* urllib.parse: f3. Parse URLs into or assemble them from components.
* urllib.request: f4. Extensible library for opening URLs.
* urllib.response: f5. Response classes used by urllib.
* urllib.robotparser: f6. Load a robots.txt file and answer questions about
                        fetchability of other URLs.
* usercustomize: f7.
* uuid: f8. UUID objects (universally unique identifiers)
                        according to RFC 4122
* venv: f9. Creation of virtual environments.
* warnings: fa. Issue warning messages and control their disposition.
* wave: fb. Provide an interface to the WAV sound format.
* weakref: fc. Support for weak references and weak dictionaries.
* webbrowser: fd. Easy-to-use controller for web browsers.
* winreg: fe. Routines and objects for manipulating the Windows
                        registry.
* winsound: ff. Access to the sound-playing machinery for Windows.
* wsgiref: 100. WSGI Utilities and Reference Implementation.
* wsgiref.handlers: 101. WSGI server/gateway base classes.
* wsgiref.headers: 102. WSGI response header tools.
* wsgiref.simple_server: 103. A simple WSGI HTTP server.
* wsgiref.types: 104. WSGI types for static type checking
* wsgiref.util: 105. WSGI environment utilities.
* wsgiref.validate: 106. WSGI conformance checker.
* xml: 107. Package containing XML processing modules
* xml.dom: 108. Document Object Model API for Python.
* xml.dom.minidom: 109. Minimal Document Object Model (DOM) implementation.
* xml.dom.pulldom: 10a. Support for building partial DOM trees from SAX
                        events.
* xml.etree.ElementInclude: 10b.
* xml.etree.ElementTree: 10c. Implementation of the ElementTree API.
* xml.parsers.expat: 10d. An interface to the Expat non-validating XML parser.
* xml.parsers.expat.errors: 10e.
* xml.parsers.expat.model: 10f.
* xml.sax: 110. Package containing SAX2 base classes and convenience
                        functions.
* xml.sax.handler: 111. Base classes for SAX event handlers.
* xml.sax.saxutils: 112. Convenience functions and classes for use with SAX.
* xml.sax.xmlreader: 113. Interface which SAX-compliant XML parsers must
                        implement.
* xmlrpc.client: 114. XML-RPC client access.
* xmlrpc.server: 115. Basic XML-RPC server implementations.
* zipapp: 116. Manage executable Python zip archives
* zipfile: 117. Read and write ZIP-format archive files.
* zipimport: 118. Support for importing Python modules from ZIP
                        archives.
* zlib: 119. Low-level interface to compression and decompression
                        routines compatible with gzip.
* zoneinfo: 11a. IANA time zone support


File: python.info,  Node: 索引,  Prev: Python 模組索引,  Up: Top

索引
****

[index]
* Menu:

* _ （底線）;gettext:                    GNU gettext API.    (line   32)
* _ （底線）;於字串格式化:               格式規格 Format Specification 迷你語言.
                                                             (line   98)
* _ （底線）;於數值常數中:               Numeric literals.   (line   13)
* _ （底線）;於數值常數中 <1>:           Integer literals.   (line   39)
* __, identifiers（識別器）:             軟關鍵字.           (line   21)
* __abs__() (object 的方法):             Emulating numeric types.
                                                             (line  108)
* __abs__() (於 operator 模組中):        operator --- 標準運算子替代函式.
                                                             (line   65)
* __add__() (object 的方法):             Emulating numeric types.
                                                             (line   11)
* __add__() (於 operator 模組中):        operator --- 標準運算子替代函式.
                                                             (line   70)
* __aenter__() (object 的方法):          Asynchronous Context Managers.
                                                             (line   12)
* __aexit__() (object 的方法):           Asynchronous Context Managers.
                                                             (line   17)
* __aiter__() (object 的方法):           Asynchronous Iterators.
                                                             (line   12)
* __all__:                               從套件中 import *.  (line    6)
* __all__（可選模組屬性）:               import 陳述式.      (line   84)
* __all__（套件變數）:                   引入模組<2>.        (line    8)
* __and__() (enum.Flag 的方法):          資料型別<2>.        (line  454)
* __and__() (object 的方法):             Emulating numeric types.
                                                             (line   11)
* __and__() (於 operator 模組中):        operator --- 標準運算子替代函式.
                                                             (line   75)
* __anext__() (agen 的方法):             Asynchronous generator-iterator methods.
                                                             (line   10)
* __anext__() (object 的方法):           Asynchronous Iterators.
                                                             (line   16)
* __annotations__ (function 的屬性):     特殊可寫屬性.       (line   44)
* __annotations__ （函式屬性）:          特殊可寫屬性.       (line    6)
* __annotations__ （模組屬性）:          模組<2>.            (line   21)
* __annotations__ （類別屬性）:          Custom classes.     (line   34)
* __args__ (genericalias 的屬性):        GenericAlias 物件的特殊屬性.
                                                             (line   15)
* __await__() (object 的方法):           Awaitable Objects.  (line   14)
* __bases__ (class 的屬性):              特殊屬性.           (line   19)
* __bases__ （類別屬性）:                Custom classes.     (line   34)
* __bool__() (object 的方法):            Basic customization.
                                                             (line  307)
* __bool__() （物件方法）:               Emulating container types.
                                                             (line   40)
* __bound__ (typing.TypeVar 的屬性):     Building generic types and type aliases.
                                                             (line  175)
* __breakpointhook__ (於 sys 模組中):    sys --- 系統特定的參數與函式.
                                                             (line  415)
* __buffer__() (object 的方法):          Emulating buffer types.
                                                             (line   15)
* __bytes__() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  127)
* __bytes__() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  137)
* __bytes__() (object 的方法):           Basic customization.
                                                             (line  145)
* __cached__:                            Import-related module attributes.
                                                             (line   88)
* __call__() (email.headerregistry.HeaderRegistry 的方法): email headerregistry：自訂標頭物件.
                                                             (line  389)
* __call__() (enum.EnumType 的方法):     資料型別<2>.        (line   16)
* __call__() (object 的方法):            Emulating callable objects.
                                                             (line    6)
* __call__() (weakref.finalize 的方法):  weakref --- 弱參照. (line  238)
* __call__() (於 operator 模組中):       operator --- 標準運算子替代函式.
                                                             (line  206)
* __call__() （物件方法）:               Calls.              (line  155)
* __callback__ (weakref.ref 的屬性):     weakref --- 弱參照. (line   98)
* __cause__ (BaseException 的屬性):      例外的情境.         (line    8)
* __cause__ (traceback.TracebackException 的屬性): TracebackException 物件.
                                                             (line   39)
* __cause__（例外屬性）:                 raise 陳述式.       (line   30)
* __cause__（例外屬性） <1>:             例外的情境.         (line    6)
* __ceil__() (fractions.Fraction 的方法): fractions --- 有理數.
                                                             (line  187)
* __ceil__() (object 的方法):            Emulating numeric types.
                                                             (line  138)
* __class__ (instance 的屬性):           特殊屬性.           (line   15)
* __class__ (unittest.mock.Mock 的屬性): Mock 類別.          (line  494)
* __class__ （實例屬性）:                Class instances.    (line   30)
* __class__ （方法 cell）:               Creating the class object.
                                                             (line    6)
* __class__ （模組屬性）:                Customizing module attribute access.
                                                             (line    6)
* __class_getitem__() (object 的類別方法): Emulating generic types.
                                                             (line   32)
* __classcell__ （類別命名空間項目）:    Creating the class object.
                                                             (line    6)
* __closure__ (function 的屬性):         特殊唯讀屬性.       (line   16)
* __closure__ （函式屬性）:              特殊唯讀屬性.       (line    6)
* __code__ (function 的屬性):            特殊可寫屬性.       (line   36)
* __code__ （函式屬性）:                 特殊可寫屬性.       (line    6)
* __code__（函式物件屬性）:              Code Objects.       (line    6)
* __complex__() (object 的方法):         Emulating numeric types.
                                                             (line  116)
* __concat__() (於 operator 模組中):     operator --- 標準運算子替代函式.
                                                             (line  164)
* __constraints__ (typing.TypeVar 的屬性): Building generic types and type aliases.
                                                             (line  184)
* __contains__() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  177)
* __contains__() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  299)
* __contains__() (enum.EnumType 的方法): 資料型別<2>.        (line   58)
* __contains__() (enum.Flag 的方法):     資料型別<2>.        (line  392)
* __contains__() (mailbox.Mailbox 的方法): Mailbox 物件.     (line  203)
* __contains__() (object 的方法):        Emulating container types.
                                                             (line  149)
* __contains__() (於 operator 模組中):   operator --- 標準運算子替代函式.
                                                             (line  169)
* __context__ (BaseException 的屬性):    例外的情境.         (line    8)
* __context__ (traceback.TracebackException 的屬性): TracebackException 物件.
                                                             (line   43)
* __context__（例外屬性）:               raise 陳述式.       (line   30)
* __context__（例外屬性） <1>:           例外的情境.         (line    6)
* __contravariant__ (typing.TypeVar 的屬性): Building generic types and type aliases.
                                                             (line  163)
* __copy__() （複製協定）:               copy --- 淺層 shallow 和深層 deep 複製操作.
                                                             (line   70)
* __covariant__ (typing.TypeVar 的屬性): Building generic types and type aliases.
                                                             (line  159)
* __debug__:                             assert 陳述式.      (line   21)
* __debug__ (內建變數):                  內建常數.           (line   59)
* __deepcopy__() （複製協定）:           copy --- 淺層 shallow 和深層 deep 複製操作.
                                                             (line   70)
* __default__ (typing.ParamSpec 的屬性): Building generic types and type aliases.
                                                             (line  426)
* __default__ (typing.TypeVar 的屬性):   Building generic types and type aliases.
                                                             (line  194)
* __default__ (typing.TypeVarTuple 的屬性): Building generic types and type aliases.
                                                             (line  326)
* __defaults__ (function 的屬性):        特殊可寫屬性.       (line   30)
* __defaults__ （函式屬性）:             特殊可寫屬性.       (line    6)
* __del__() (io.IOBase 的方法):          I/O 基礎類別.       (line  145)
* __del__() (object 的方法):             Basic customization.
                                                             (line   53)
* __delattr__() (object 的方法):         Customizing attribute access.
                                                             (line   68)
* __delete__() (object 的方法):          Implementing Descriptors.
                                                             (line   40)
* __delitem__() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  224)
* __delitem__() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  333)
* __delitem__() (mailbox.Mailbox 的方法): Mailbox 物件.      (line   76)
* __delitem__() (mailbox.MH 的方法):     MH 物件.            (line   79)
* __delitem__() (object 的方法):         Emulating container types.
                                                             (line  107)
* __delitem__() (於 operator 模組中):    operator --- 標準運算子替代函式.
                                                             (line  178)
* __dict__ (function 的屬性):            特殊可寫屬性.       (line   39)
* __dict__ (object 的屬性):              特殊屬性.           (line   10)
* __dict__ （函式屬性）:                 特殊可寫屬性.       (line    6)
* __dict__ （實例屬性）:                 Class instances.    (line   30)
* __dict__ （模組屬性）:                 模組<2>.            (line   47)
* __dict__ （類別屬性）:                 Custom classes.     (line   34)
* __dict__（模組屬性）:                  模組物件.           (line   46)
* __dir__ （模組屬性）:                  Customizing module attribute access.
                                                             (line    6)
* __dir__() (enum.Enum 的方法):          資料型別<2>.        (line  179)
* __dir__() (enum.EnumType 的方法):      資料型別<2>.        (line   71)
* __dir__() (object 的方法):             Customizing attribute access.
                                                             (line   77)
* __dir__() (unittest.mock.Mock 的方法): Mock 類別.          (line  253)
* __displayhook__ (於 sys 模組中):       sys --- 系統特定的參數與函式.
                                                             (line  415)
* __divmod__() (object 的方法):          Emulating numeric types.
                                                             (line   11)
* __doc__ (function 的屬性):             特殊可寫屬性.       (line   12)
* __doc__ (method 的屬性):               Instance methods.   (line   18)
* __doc__ (types.ModuleType 的屬性):     Standard Interpreter Types.
                                                             (line  131)
* __doc__ （函式屬性）:                  特殊可寫屬性.       (line    6)
* __doc__ （方法屬性）:                  Instance methods.   (line    9)
* __doc__ （模組屬性）:                  模組<2>.            (line   21)
* __doc__ （類別屬性）:                  Custom classes.     (line   34)
* __doc__（模組屬性）:                   模組物件.           (line   25)
* __enter__() (contextmanager 的方法):   情境管理器型別.     (line   11)
* __enter__() (object 的方法):           With Statement Context Managers.
                                                             (line   21)
* __enter__() (winreg.PyHKEY 的方法):    Registry Handle Objects.
                                                             (line   56)
* __eq__() (email.charset.Charset 的方法): email charset：表示字元集合.
                                                             (line  148)
* __eq__() (email.header.Header 的方法): email header：國際化標頭.
                                                             (line  170)
* __eq__() (memoryview 的方法):          Memory Views.       (line  112)
* __eq__() (object 的方法):              Basic customization.
                                                             (line  174)
* __eq__() (於 operator 模組中):         operator --- 標準運算子替代函式.
                                                             (line   20)
* __eq__()（實例方法）:                  比較運算.           (line   46)
* __excepthook__ (於 sys 模組中):        sys --- 系統特定的參數與函式.
                                                             (line  415)
* __excepthook__ (於 threading 模組中):  threading --- 基於執行緒的平行性.
                                                             (line  109)
* __exit__() (contextmanager 的方法):    情境管理器型別.     (line   27)
* __exit__() (object 的方法):            With Statement Context Managers.
                                                             (line   27)
* __exit__() (winreg.PyHKEY 的方法):     Registry Handle Objects.
                                                             (line   56)
* __file__:                              Import-related module attributes.
                                                             (line   86)
* __file__ （模組屬性）:                 模組<2>.            (line   21)
* __file__（模組屬性）:                  模組物件.           (line   25)
* __file__（模組屬性） <1>:              模組物件.           (line   87)
* __firstlineno__ (class attribute):     Custom classes.     (line   34)
* __float__() (object 的方法):           Emulating numeric types.
                                                             (line  116)
* __floor__() (fractions.Fraction 的方法): fractions --- 有理數.
                                                             (line  177)
* __floor__() (object 的方法):           Emulating numeric types.
                                                             (line  138)
* __floordiv__() (object 的方法):        Emulating numeric types.
                                                             (line   11)
* __floordiv__() (於 operator 模組中):   operator --- 標準運算子替代函式.
                                                             (line   80)
* __format__:                            內建函式.           (line  700)
* __format__() (datetime.date 的方法):   date 物件.          (line  305)
* __format__() (datetime.datetime 的方法): datetime 物件.    (line  755)
* __format__() (datetime.time 的方法):   time 物件.          (line  228)
* __format__() (enum.Enum 的方法):       資料型別<2>.        (line  314)
* __format__() (fractions.Fraction 的方法): fractions --- 有理數.
                                                             (line  204)
* __format__() (ipaddress.IPv4Address 的方法): Address objects.
                                                             (line  184)
* __format__() (ipaddress.IPv6Address 的方法): Address objects.
                                                             (line  316)
* __format__() (object 的方法):          Basic customization.
                                                             (line  151)
* __fspath__() (os.PathLike 的方法):     行程參數.           (line  127)
* __func__ (method 的屬性):              Instance methods.   (line   15)
* __func__ （方法屬性）:                 Instance methods.   (line    9)
* __future__:                            術語表.             (line  467)
* __future__;future statement（future 陳述式）: Future statements.
                                                             (line    6)
* __ge__() (object 的方法):              Basic customization.
                                                             (line  174)
* __ge__() (於 operator 模組中):         operator --- 標準運算子替代函式.
                                                             (line   20)
* __ge__()（實例方法）:                  比較運算.           (line   46)
* __get__() (object 的方法):             Implementing Descriptors.
                                                             (line   13)
* __getattr__ （模組屬性）:              Customizing module attribute access.
                                                             (line    6)
* __getattr__() (object 的方法):         Customizing attribute access.
                                                             (line   10)
* __getattribute__() (object 的方法):    Customizing attribute access.
                                                             (line   32)
* __getitem__() (email.headerregistry.HeaderRegistry 的方法): email headerregistry：自訂標頭物件.
                                                             (line  384)
* __getitem__() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  187)
* __getitem__() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  308)
* __getitem__() (enum.EnumType 的方法):  資料型別<2>.        (line   79)
* __getitem__() (mailbox.Mailbox 的方法): Mailbox 物件.      (line  148)
* __getitem__() (object 的方法):         Emulating container types.
                                                             (line   77)
* __getitem__() (re.Match 的方法):       Match Objects.      (line   89)
* __getitem__() （對映物件方法）:        Special method names.
                                                             (line    6)
* __getitem__() (於 operator 模組中):    operator --- 標準運算子替代函式.
                                                             (line  183)
* __getnewargs__() (object 的方法):      Pickling Class Instances.
                                                             (line   47)
* __getnewargs_ex__() (object 的方法):   Pickling Class Instances.
                                                             (line   29)
* __getstate__() (object 的方法):        Pickling Class Instances.
                                                             (line   61)
* __getstate__()（copy 協定）:           Handling Stateful Objects.
                                                             (line    6)
* __globals__ (function 的屬性):         特殊唯讀屬性.       (line   10)
* __globals__ （函式屬性）:              特殊唯讀屬性.       (line    6)
* __gt__() (object 的方法):              Basic customization.
                                                             (line  174)
* __gt__() (於 operator 模組中):         operator --- 標準運算子替代函式.
                                                             (line   20)
* __gt__()（實例方法）:                  比較運算.           (line   46)
* __hash__() (object 的方法):            Basic customization.
                                                             (line  227)
* __iadd__() (object 的方法):            Emulating numeric types.
                                                             (line   77)
* __iadd__() (於 operator 模組中):       原地 in-place 運算子.
                                                             (line   33)
* __iand__() (object 的方法):            Emulating numeric types.
                                                             (line   77)
* __iand__() (於 operator 模組中):       原地 in-place 運算子.
                                                             (line   38)
* __iconcat__() (於 operator 模組中):    原地 in-place 運算子.
                                                             (line   43)
* __ifloordiv__() (object 的方法):       Emulating numeric types.
                                                             (line   77)
* __ifloordiv__() (於 operator 模組中):  原地 in-place 運算子.
                                                             (line   48)
* __ilshift__() (object 的方法):         Emulating numeric types.
                                                             (line   77)
* __ilshift__() (於 operator 模組中):    原地 in-place 運算子.
                                                             (line   53)
* __imatmul__() (object 的方法):         Emulating numeric types.
                                                             (line   77)
* __imatmul__() (於 operator 模組中):    原地 in-place 運算子.
                                                             (line   68)
* __imod__() (object 的方法):            Emulating numeric types.
                                                             (line   77)
* __imod__() (於 operator 模組中):       原地 in-place 運算子.
                                                             (line   58)
* __import__() (於 importlib 模組中):    函式<11>.           (line    6)
* __imul__() (object 的方法):            Emulating numeric types.
                                                             (line   77)
* __imul__() (於 operator 模組中):       原地 in-place 運算子.
                                                             (line   63)
* __index__() (object 的方法):           Emulating numeric types.
                                                             (line  124)
* __index__() (於 operator 模組中):      operator --- 標準運算子替代函式.
                                                             (line   85)
* __infer_variance__ (typing.TypeVar 的屬性): Building generic types and type aliases.
                                                             (line  168)
* __init__() (asyncio.Future 的方法):    Future and Task private constructors.
                                                             (line   17)
* __init__() (asyncio.Task 的方法):      Future and Task private constructors.
                                                             (line   23)
* __init__() (difflib.HtmlDiff 的方法):  difflib --- 計算差異的輔助工具.
                                                             (line   92)
* __init__() (enum.Enum 的方法):         資料型別<2>.        (line  228)
* __init__() (logging.Handler 的方法):   Handler Objects.    (line   13)
* __init__() (logging.logging.Formatter 的方法): Formatters. (line   13)
* __init__() (object 的方法):            Basic customization.
                                                             (line   37)
* __init_subclass__() (enum.Enum 的方法): 資料型別<2>.       (line  240)
* __init_subclass__() (object 的類別方法): Customizing class creation.
                                                             (line   13)
* __instancecheck__() (class 的方法):    Customizing instance and subclass checks.
                                                             (line   15)
* __int__() (object 的方法):             Emulating numeric types.
                                                             (line  116)
* __interactivehook__ (於 sys 模組中):   sys --- 系統特定的參數與函式.
                                                             (line 1131)
* __inv__() (於 operator 模組中):        operator --- 標準運算子替代函式.
                                                             (line   93)
* __invert__() (object 的方法):          Emulating numeric types.
                                                             (line  108)
* __invert__() (於 operator 模組中):     operator --- 標準運算子替代函式.
                                                             (line   93)
* __ior__() (object 的方法):             Emulating numeric types.
                                                             (line   77)
* __ior__() (於 operator 模組中):        原地 in-place 運算子.
                                                             (line   75)
* __ipow__() (object 的方法):            Emulating numeric types.
                                                             (line   77)
* __ipow__() (於 operator 模組中):       原地 in-place 運算子.
                                                             (line   80)
* __irshift__() (object 的方法):         Emulating numeric types.
                                                             (line   77)
* __irshift__() (於 operator 模組中):    原地 in-place 運算子.
                                                             (line   85)
* __isub__() (object 的方法):            Emulating numeric types.
                                                             (line   77)
* __isub__() (於 operator 模組中):       原地 in-place 運算子.
                                                             (line   90)
* __iter__() (container 的方法):         疊代器型別.         (line   12)
* __iter__() (enum.EnumType 的方法):     資料型別<2>.        (line   87)
* __iter__() (iterator 的方法):          疊代器型別.         (line   22)
* __iter__() (mailbox.Mailbox 的方法):   Mailbox 物件.       (line  116)
* __iter__() (object 的方法):            Emulating container types.
                                                             (line  121)
* __iter__() (unittest.TestSuite 的方法): Grouping tests.    (line   60)
* __itruediv__() (object 的方法):        Emulating numeric types.
                                                             (line   77)
* __itruediv__() (於 operator 模組中):   原地 in-place 運算子.
                                                             (line   95)
* __ixor__() (object 的方法):            Emulating numeric types.
                                                             (line   77)
* __ixor__() (於 operator 模組中):       原地 in-place 運算子.
                                                             (line  100)
* __kwdefaults__ (function 的屬性):      特殊可寫屬性.       (line   51)
* __kwdefaults__ （函式屬性）:           特殊可寫屬性.       (line    6)
* __le__() (object 的方法):              Basic customization.
                                                             (line  174)
* __le__() (於 operator 模組中):         operator --- 標準運算子替代函式.
                                                             (line   20)
* __le__()（實例方法）:                  比較運算.           (line   46)
* __len__() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  173)
* __len__() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  295)
* __len__() (enum.EnumType 的方法):      資料型別<2>.        (line   94)
* __len__() (mailbox.Mailbox 的方法):    Mailbox 物件.       (line  208)
* __len__() (object 的方法):             Emulating container types.
                                                             (line   38)
* __len__() （對映物件方法）:            Basic customization.
                                                             (line  309)
* __length_hint__() (object 的方法):     Emulating container types.
                                                             (line   53)
* __loader__:                            Import-related module attributes.
                                                             (line   20)
* __loader__ (types.ModuleType 的屬性):  Standard Interpreter Types.
                                                             (line  135)
* __loader__（模組屬性）:                模組物件.           (line   25)
* __lshift__() (object 的方法):          Emulating numeric types.
                                                             (line   11)
* __lshift__() (於 operator 模組中):     operator --- 標準運算子替代函式.
                                                             (line  100)
* __lt__() (object 的方法):              Basic customization.
                                                             (line  174)
* __lt__() (於 operator 模組中):         operator --- 標準運算子替代函式.
                                                             (line   20)
* __lt__()（實例方法）:                  比較運算.           (line   46)
* __matmul__() (object 的方法):          Emulating numeric types.
                                                             (line   11)
* __matmul__() (於 operator 模組中):     operator --- 標準運算子替代函式.
                                                             (line  115)
* __members__ (enum.EnumType 的屬性):    資料型別<2>.        (line  101)
* __missing__():                         Mapping Types --- dict.
                                                             (line   89)
* __missing__() (collections.defaultdict 的方法): defaultdict 物件.
                                                             (line   19)
* __missing__() (object 的方法):         Emulating container types.
                                                             (line  116)
* __mod__() (object 的方法):             Emulating numeric types.
                                                             (line   11)
* __mod__() (於 operator 模組中):        operator --- 標準運算子替代函式.
                                                             (line  105)
* __module__ (function 的屬性):          特殊可寫屬性.       (line   26)
* __module__ (method 的屬性):            Instance methods.   (line   28)
* __module__ (typing.NewType 的屬性):    Other special directives.
                                                             (line  113)
* __module__ (typing.TypeAliasType 的屬性): Building generic types and type aliases.
                                                             (line  511)
* __module__ （函式屬性）:               特殊可寫屬性.       (line    6)
* __module__ （方法屬性）:               Instance methods.   (line    9)
* __module__ （類別屬性）:               Custom classes.     (line   34)
* __mro__ (class 的屬性):                特殊屬性.           (line   42)
* __mro_entries__() (object 的方法):     Resolving MRO entries.
                                                             (line    6)
* __mul__() (object 的方法):             Emulating numeric types.
                                                             (line   11)
* __mul__() (於 operator 模組中):        operator --- 標準運算子替代函式.
                                                             (line  110)
* __mutable_keys__ (typing.TypedDict 的屬性): Other special directives.
                                                             (line  442)
* __name__:                              Import-related module attributes.
                                                             (line   14)
* __name__ (definition 的屬性):          特殊屬性.           (line   23)
* __name__ (function 的屬性):            特殊可寫屬性.       (line   16)
* __name__ (method 的屬性):              Instance methods.   (line   24)
* __name__ (property 的屬性):            內建函式.           (line 1485)
* __name__ (types.ModuleType 的屬性):    Standard Interpreter Types.
                                                             (line  153)
* __name__ (typing.NewType 的屬性):      Other special directives.
                                                             (line  117)
* __name__ (typing.ParamSpec 的屬性):    Building generic types and type aliases.
                                                             (line  422)
* __name__ (typing.TypeAliasType 的屬性): Building generic types and type aliases.
                                                             (line  503)
* __name__ (typing.TypeVar 的屬性):      Building generic types and type aliases.
                                                             (line  155)
* __name__ (typing.TypeVarTuple 的屬性): Building generic types and type aliases.
                                                             (line  322)
* __name__ （函式屬性）:                 特殊可寫屬性.       (line    6)
* __name__ （方法屬性）:                 Instance methods.   (line    9)
* __name__ （模組屬性）:                 模組<2>.            (line   21)
* __name__ （類別屬性）:                 Custom classes.     (line   34)
* __name__（模組屬性）:                  模組物件.           (line   25)
* __name__（模組屬性） <1>:              模組物件.           (line   61)
* __ne__() (email.charset.Charset 的方法): email charset：表示字元集合.
                                                             (line  153)
* __ne__() (email.header.Header 的方法): email header：國際化標頭.
                                                             (line  175)
* __ne__() (object 的方法):              Basic customization.
                                                             (line  174)
* __ne__() (於 operator 模組中):         operator --- 標準運算子替代函式.
                                                             (line   20)
* __ne__()（實例方法）:                  比較運算.           (line   46)
* __neg__() (object 的方法):             Emulating numeric types.
                                                             (line  108)
* __neg__() (於 operator 模組中):        operator --- 標準運算子替代函式.
                                                             (line  122)
* __new__() (enum.Enum 的方法):          資料型別<2>.        (line  267)
* __new__() (object 的方法):             Basic customization.
                                                             (line    6)
* __next__() (csv.csvreader 的方法):     讀取器物件.         (line    9)
* __next__() (generator 的方法):         Generator-iterator methods.
                                                             (line   12)
* __next__() (iterator 的方法):          疊代器型別.         (line   28)
* __not__() (於 operator 模組中):        operator --- 標準運算子替代函式.
                                                             (line   43)
* __notes__ (BaseException 的屬性):      基底類別 base classes.
                                                             (line   49)
* __notes__ (traceback.TracebackException 的屬性): TracebackException 物件.
                                                             (line   61)
* __objclass__ (object 的屬性):          Implementing Descriptors.
                                                             (line   48)
* __optional_keys__ (typing.TypedDict 的屬性): Other special directives.
                                                             (line  393)
* __or__() (enum.Flag 的方法):           資料型別<2>.        (line  447)
* __or__() (object 的方法):              Emulating numeric types.
                                                             (line   11)
* __or__() (於 operator 模組中):         operator --- 標準運算子替代函式.
                                                             (line  127)
* __origin__ (genericalias 的屬性):      GenericAlias 物件的特殊屬性.
                                                             (line    8)
* __package__:                           Import-related module attributes.
                                                             (line   34)
* __package__ (types.ModuleType 的屬性): Standard Interpreter Types.
                                                             (line  158)
* __package__（模組屬性）:               模組物件.           (line   25)
* __parameters__ (genericalias 的屬性):  GenericAlias 物件的特殊屬性.
                                                             (line   23)
* __path__:                              Import-related module attributes.
                                                             (line   75)
* __pos__() (object 的方法):             Emulating numeric types.
                                                             (line  108)
* __pos__() (於 operator 模組中):        operator --- 標準運算子替代函式.
                                                             (line  132)
* __post_init__() (於 dataclasses 模組中): Post-init processing.
                                                             (line    6)
* __pow__() (object 的方法):             Emulating numeric types.
                                                             (line   11)
* __pow__() (於 operator 模組中):        operator --- 標準運算子替代函式.
                                                             (line  137)
* __prepare__ （元類別方法）:            Preparing the class namespace.
                                                             (line    6)
* __PYVENV_LAUNCHER__:                   PyConfig.           (line  184)
* __PYVENV_LAUNCHER__ <1>:               PyConfig.           (line  702)
* __qualname__ (definition 的屬性):      特殊屬性.           (line   28)
* __qualname__ (function 的屬性):        特殊可寫屬性.       (line   20)
* __radd__() (object 的方法):            Emulating numeric types.
                                                             (line   41)
* __rand__() (object 的方法):            Emulating numeric types.
                                                             (line   41)
* __rdivmod__() (object 的方法):         Emulating numeric types.
                                                             (line   41)
* __readonly_keys__ (typing.TypedDict 的屬性): Other special directives.
                                                             (line  434)
* __reduce__() (object 的方法):          Pickling Class Instances.
                                                             (line  124)
* __reduce_ex__() (object 的方法):       Pickling Class Instances.
                                                             (line  179)
* __release_buffer__() (object 的方法):  Emulating buffer types.
                                                             (line   25)
* __replace__() (replace protocol):      copy --- 淺層 shallow 和深層 deep 複製操作.
                                                             (line   88)
* __repr__() (enum.Enum 的方法):         資料型別<2>.        (line  283)
* __repr__() (multiprocessing.managers.BaseProxy 的方法): Proxy Objects.
                                                             (line  145)
* __repr__() (netrc.netrc 的方法):       netrc 物件.         (line   14)
* __repr__() (object 的方法):            Basic customization.
                                                             (line  114)
* __required_keys__ (typing.TypedDict 的屬性): Other special directives.
                                                             (line  389)
* __reversed__() (enum.EnumType 的方法): 資料型別<2>.        (line  105)
* __reversed__() (object 的方法):        Emulating container types.
                                                             (line  128)
* __rfloordiv__() (object 的方法):       Emulating numeric types.
                                                             (line   41)
* __rlshift__() (object 的方法):         Emulating numeric types.
                                                             (line   41)
* __rmatmul__() (object 的方法):         Emulating numeric types.
                                                             (line   41)
* __rmod__() (object 的方法):            Emulating numeric types.
                                                             (line   41)
* __rmul__() (object 的方法):            Emulating numeric types.
                                                             (line   41)
* __ror__() (object 的方法):             Emulating numeric types.
                                                             (line   41)
* __round__() (fractions.Fraction 的方法): fractions --- 有理數.
                                                             (line  193)
* __round__() (object 的方法):           Emulating numeric types.
                                                             (line  138)
* __rpow__() (object 的方法):            Emulating numeric types.
                                                             (line   41)
* __rrshift__() (object 的方法):         Emulating numeric types.
                                                             (line   41)
* __rshift__() (object 的方法):          Emulating numeric types.
                                                             (line   11)
* __rshift__() (於 operator 模組中):     operator --- 標準運算子替代函式.
                                                             (line  142)
* __rsub__() (object 的方法):            Emulating numeric types.
                                                             (line   41)
* __rtruediv__() (object 的方法):        Emulating numeric types.
                                                             (line   41)
* __rxor__() (object 的方法):            Emulating numeric types.
                                                             (line   41)
* __self__ (method 的屬性):              Instance methods.   (line   11)
* __self__ （方法屬性）:                 Instance methods.   (line    9)
* __set__() (object 的方法):             Implementing Descriptors.
                                                             (line   31)
* __set_name__() (object 的方法):        Customizing class creation.
                                                             (line   47)
* __setattr__() (object 的方法):         Customizing attribute access.
                                                             (line   53)
* __setitem__() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  202)
* __setitem__() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  319)
* __setitem__() (mailbox.Mailbox 的方法): Mailbox 物件.      (line   90)
* __setitem__() (mailbox.Maildir 的方法): Mailbox 物件<2>.   (line  193)
* __setitem__() (object 的方法):         Emulating container types.
                                                             (line   98)
* __setitem__() (於 operator 模組中):    operator --- 標準運算子替代函式.
                                                             (line  192)
* __setstate__() (object 的方法):        Pickling Class Instances.
                                                             (line   88)
* __setstate__()（copy 協定）:           Handling Stateful Objects.
                                                             (line    6)
* __slots__:                             術語表.             (line 1115)
* __spec__:                              Import-related module attributes.
                                                             (line   59)
* __spec__ (types.ModuleType 的屬性):    Standard Interpreter Types.
                                                             (line  179)
* __static_attributes__ (class attribute): Custom classes.   (line   34)
* __static_attributes__ (class 的屬性):  特殊屬性.           (line   62)
* __stderr__ (於 sys 模組中):            sys --- 系統特定的參數與函式.
                                                             (line 1827)
* __stdin__ (於 sys 模組中):             sys --- 系統特定的參數與函式.
                                                             (line 1827)
* __stdout__ (於 sys 模組中):            sys --- 系統特定的參數與函式.
                                                             (line 1827)
* __str__() (datetime.date 的方法):      date 物件.          (line  278)
* __str__() (datetime.datetime 的方法):  datetime 物件.      (line  725)
* __str__() (datetime.time 的方法):      time 物件.          (line  218)
* __str__() (email.charset.Charset 的方法): email charset：表示字元集合.
                                                             (line  143)
* __str__() (email.header.Header 的方法): email header：國際化標頭.
                                                             (line  158)
* __str__() (email.headerregistry.Address 的方法): email headerregistry：自訂標頭物件.
                                                             (line  446)
* __str__() (email.headerregistry.Group 的方法): email headerregistry：自訂標頭物件.
                                                             (line  480)
* __str__() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line   94)
* __str__() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  100)
* __str__() (enum.Enum 的方法):          資料型別<2>.        (line  299)
* __str__() (multiprocessing.managers.BaseProxy 的方法): Proxy Objects.
                                                             (line  149)
* __str__() (object 的方法):             Basic customization.
                                                             (line  130)
* __sub__() (object 的方法):             Emulating numeric types.
                                                             (line   11)
* __sub__() (於 operator 模組中):        operator --- 標準運算子替代函式.
                                                             (line  147)
* __subclasscheck__() (class 的方法):    Customizing instance and subclass checks.
                                                             (line   21)
* __subclasses__() (class 的方法):       特殊屬性.           (line   53)
* __subclasshook__() (abc.ABCMeta 的方法): abc --- 抽象基底類別.
                                                             (line   81)
* __supertype__ (typing.NewType 的屬性): Other special directives.
                                                             (line  121)
* __suppress_context__ (BaseException 的屬性): 例外的情境.   (line    8)
* __suppress_context__ (traceback.TracebackException 的屬性): TracebackException 物件.
                                                             (line   56)
* __suppress_context__（例外屬性）:      例外的情境.         (line    6)
* __total__ (typing.TypedDict 的屬性):   Other special directives.
                                                             (line  364)
* __traceback__ (BaseException 的屬性):  基底類別 base classes.
                                                             (line   37)
* __traceback__（例外屬性）:             raise 陳述式.       (line    6)
* __truediv__() (importlib.abc.Traversable 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  566)
* __truediv__() (importlib.resources.abc.Traversable 的方法): importlib resources abc -- 資源的抽象基底類別.
                                                             (line  136)
* __truediv__() (object 的方法):         Emulating numeric types.
                                                             (line   11)
* __truediv__() (於 operator 模組中):    operator --- 標準運算子替代函式.
                                                             (line  152)
* __trunc__() (object 的方法):           Emulating numeric types.
                                                             (line  138)
* __type_params__ (definition 的屬性):   特殊屬性.           (line   35)
* __type_params__ (function 的屬性):     特殊可寫屬性.       (line   55)
* __type_params__ (typing.TypeAliasType 的屬性): Building generic types and type aliases.
                                                             (line  519)
* __type_params__ （函式屬性）:          特殊可寫屬性.       (line    6)
* __type_params__ （類別屬性）:          Custom classes.     (line   34)
* __unpacked__ (genericalias 的屬性):    GenericAlias 物件的特殊屬性.
                                                             (line   38)
* __unraisablehook__ (於 sys 模組中):    sys --- 系統特定的參數與函式.
                                                             (line  415)
* __value__ (typing.TypeAliasType 的屬性): Building generic types and type aliases.
                                                             (line  531)
* __version__ (於 curses 模組中):        Constants.          (line   20)
* __xor__() (enum.Flag 的方法):          資料型別<2>.        (line  463)
* __xor__() (object 的方法):             Emulating numeric types.
                                                             (line   11)
* __xor__() (於 operator 模組中):        operator --- 標準運算子替代函式.
                                                             (line  157)
* _, identifiers（識別器）:              軟關鍵字.           (line   22)
* _add_alias_() (enum.EnumType 的方法):  資料型別<2>.        (line  112)
* _add_value_alias_() (enum.EnumType 的方法): 資料型別<2>.   (line  118)
* _align_ (ctypes.Structure 的屬性):     Structured data types.
                                                             (line   87)
* _anonymous_ (ctypes.Structure 的屬性): Structured data types.
                                                             (line   94)
* _asdict() (collections.somenamedtuple 的方法): namedtuple 擁有具名欄位之 tuple 的工廠函式.
                                                             (line   98)
* _b_base_ (ctypes._CData 的屬性):       Data types.         (line   71)
* _b_needsfree_ (ctypes._CData 的屬性):  Data types.         (line   78)
* _callmethod() (multiprocessing.managers.BaseProxy 的方法): Proxy Objects.
                                                             (line   96)
* _CData (ctypes 中的類別):              Data types.         (line    6)
* _clear_internal_caches() (於 sys 模組中): sys --- 系統特定的參數與函式.
                                                             (line  191)
* _clear_type_cache() (於 sys 模組中):   sys --- 系統特定的參數與函式.
                                                             (line  179)
* _current_exceptions() (於 sys 模組中): sys --- 系統特定的參數與函式.
                                                             (line  218)
* _current_frames() (於 sys 模組中):     sys --- 系統特定的參數與函式.
                                                             (line  199)
* _debugmallocstats() (於 sys 模組中):   sys --- 系統特定的參數與函式.
                                                             (line  274)
* _emscripten_info (於 sys 模組中):      sys --- 系統特定的參數與函式.
                                                             (line  338)
* _enablelegacywindowsfsencoding() (於 sys 模組中): sys --- 系統特定的參數與函式.
                                                             (line 1733)
* _enter_task() (於 asyncio 模組中):     Task lifetime support.
                                                             (line   22)
* _exit() (於 os 模組中):                行程管理.           (line  122)
* _Feature (__future__ 中的類別):        模組內容<9>.        (line   48)
* _field_defaults (collections.somenamedtuple 的屬性): namedtuple 擁有具名欄位之 tuple 的工廠函式.
                                                             (line  144)
* _field_types (ast.AST 的屬性):         節點 Node 類別.     (line   32)
* _fields (ast.AST 的屬性):              節點 Node 類別.     (line   18)
* _fields (collections.somenamedtuple 的屬性): namedtuple 擁有具名欄位之 tuple 的工廠函式.
                                                             (line  131)
* _fields_ (ctypes.Structure 的屬性):    Structured data types.
                                                             (line   43)
* _flush() (wsgiref.handlers.BaseHandler 的方法): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line   99)
* _frozen (C struct):                    引入模組<2>.        (line  262)
* _FuncPtr (ctypes 中的類別):            Foreign functions.  (line   12)
* _generate_next_value_() (enum.Enum 的方法): 資料型別<2>.   (line  200)
* _get_child_mock() (unittest.mock.Mock 的方法): Mock 類別.  (line  261)
* _get_preferred_schemes() (於 sysconfig 模組中): 安裝路徑函式.
                                                             (line   41)
* _getframe() (於 sys 模組中):           sys --- 系統特定的參數與函式.
                                                             (line  871)
* _getframemodulename() (於 sys 模組中): sys --- 系統特定的參數與函式.
                                                             (line  885)
* _getvalue() (multiprocessing.managers.BaseProxy 的方法): Proxy Objects.
                                                             (line  138)
* _handle (ctypes.PyDLL 的屬性):         Loading shared libraries.
                                                             (line  154)
* _ignore_ (enum.Enum 的屬性):           資料型別<2>.        (line  172)
* _incompatible_extension_module_restrictions() (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line  168)
* _inittab (C struct):                   引入模組<2>.        (line  298)
* _inittab.initfunc (C member):          引入模組<2>.        (line  310)
* _inittab.name (C member):              引入模組<2>.        (line  306)
* _is_gil_enabled() (於 sys 模組中):     sys --- 系統特定的參數與函式.
                                                             (line 1161)
* _is_interned() (於 sys 模組中):        sys --- 系統特定的參數與函式.
                                                             (line 1190)
* _leave_task() (於 asyncio 模組中):     Task lifetime support.
                                                             (line   30)
* _length_ (ctypes.Array 的屬性):        Arrays and pointers.
                                                             (line   18)
* _log (logging.LoggerAdapter 的屬性):   LoggerAdapter 物件. (line   34)
* _make() (collections.somenamedtuple 的類別方法): namedtuple 擁有具名欄位之 tuple 的工廠函式.
                                                             (line   90)
* _makeResult() (unittest.TextTestRunner 的方法): Loading and running tests.
                                                             (line  491)
* _missing_() (enum.Enum 的方法):        資料型別<2>.        (line  245)
* _name (ctypes.PyDLL 的屬性):           Loading shared libraries.
                                                             (line  158)
* _name_ (enum.Enum 的屬性):             資料型別<2>.        (line  160)
* _numeric_repr_() (enum.Flag 的方法):   資料型別<2>.        (line  483)
* _objects (ctypes._CData 的屬性):       Data types.         (line   83)
* _order_ (enum.Enum 的屬性):            資料型別<2>.        (line  168)
* _pack_ (ctypes.Structure 的屬性):      Structured data types.
                                                             (line   79)
* _parse() (gettext.NullTranslations 的方法): The NullTranslations class.
                                                             (line   21)
* _Pointer (ctypes 中的類別):            Arrays and pointers.
                                                             (line   39)
* _Py_c_diff (C function):               作為 C 結構的複數.  (line   30)
* _Py_c_neg (C function):                作為 C 結構的複數.  (line   35)
* _Py_c_pow (C function):                作為 C 結構的複數.  (line   52)
* _Py_c_prod (C function):               作為 C 結構的複數.  (line   40)
* _Py_c_quot (C function):               作為 C 結構的複數.  (line   45)
* _Py_c_sum (C function):                作為 C 結構的複數.  (line   25)
* _Py_InitializeMain (C function):       Multi-Phase Initialization Private Provisional API.
                                                             (line   44)
* _Py_NoneStruct (C var):                在 heap 上分配物件. (line   51)
* _PyBytes_Resize (C function):          位元組物件 Bytes Objects.
                                                             (line  176)
* _PyCode_GetExtra（C 函式）:            Extra information.  (line   45)
* _PyCode_SetExtra（C 函式）:            Extra information.  (line   58)
* _PyEval_RequestCodeExtraIndex（C 函式）: Extra information.
                                                             (line   29)
* _PyFrameEvalFunction (C type):         低階 API.           (line  147)
* _PyInterpreterFrame (C struct):        Internal Frames.    (line    8)
* _PyInterpreterState_GetEvalFrameFunc (C function): 低階 API.
                                                             (line  161)
* _PyInterpreterState_SetEvalFrameFunc (C function): 低階 API.
                                                             (line  171)
* _PyObject_GetDictPtr (C function):     物件協定.           (line  283)
* _PyObject_New (C function):            在 heap 上分配物件. (line    6)
* _PyObject_NewVar (C function):         在 heap 上分配物件. (line    9)
* _PyTuple_Resize (C function):          Tuple（元組）物件.  (line   99)
* _register_task() (於 asyncio 模組中):  Task lifetime support.
                                                             (line   10)
* _replace() (collections.somenamedtuple 的方法): namedtuple 擁有具名欄位之 tuple 的工廠函式.
                                                             (line  114)
* _setroot() (xml.etree.ElementTree.ElementTree 的方法): ElementTree 物件.
                                                             (line   15)
* _SimpleCData (ctypes 中的類別):        Fundamental data types<2>.
                                                             (line    6)
* _structure() (於 email.iterators 模組中): email iterators：疊代器.
                                                             (line   44)
* _type_ (ctypes._Pointer 的屬性):       Arrays and pointers.
                                                             (line   54)
* _type_ (ctypes.Array 的屬性):          Arrays and pointers.
                                                             (line   24)
* _unregister_task() (於 asyncio 模組中): Task lifetime support.
                                                             (line   16)
* _value_ (enum.Enum 的屬性):            資料型別<2>.        (line  164)
* _write() (wsgiref.handlers.BaseHandler 的方法): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line   93)
* _xoptions (於 sys 模組中):             sys --- 系統特定的參數與函式.
                                                             (line 2010)
* - （減號）;binary operator（二元運算子）: Binary arithmetic operations.
                                                             (line   83)
* - （減號）;binary operator（二元運算子） <1>: 數值型別 --- int、float、complex.
                                                             (line   21)
* - （減號）;unary operator（一元運算子）: Unary arithmetic and bitwise operations.
                                                             (line   10)
* - （減號）;unary operator（一元運算子） <1>: 數值型別 --- int、float、complex.
                                                             (line   21)
* - （減號）;於 doctests 中:             可選旗標.           (line  171)
* - （減號）;於 glob 風格的萬用字元中:   glob --- Unix 風格的路徑名稱模式擴展.
                                                             (line   10)
* - （減號）;於 glob 風格的萬用字元中 <1>: fnmatch --- Unix 檔案名稱模式比對.
                                                             (line   15)
* - （減號）;於 printf 風格格式化:       printf-style String Formatting.
                                                             (line   69)
* - （減號）;於 printf 風格格式化 <1>:   printf-style Bytes Formatting.
                                                             (line   63)
* - （減號）;於字串格式化:               格式規格 Format Specification 迷你語言.
                                                             (line   60)
* - （減號）;於正規表示式中:             正規表示式語法.     (line  178)
* -=;augmented assignment（增強賦值）:   Augmented assignment statements.
                                                             (line    6)
* ->;function annotations（函式註釋）:   函式註釋 Function Annotations.
                                                             (line    6)
* ->;function annotations（函式註釋） <1>: 函式定義.         (line  106)
* , （逗號）:                            Parenthesized forms.
                                                             (line   20)
* , （逗號）;argument list（引數列表）:  Slicings.           (line   38)
* , （逗號）;expression list（表達式列表）: 類別定義.        (line    6)
* , （逗號）;expression list（運算式串列）: List displays.   (line    6)
* , （逗號）;expression list（運算式串列） <1>: Set displays.
                                                             (line    6)
* , （逗號）;expression list（運算式串列） <2>: Expression lists.
                                                             (line    6)
* , （逗號）;expression list（運算式列表）: assert 陳述式.   (line    6)
* , （逗號）;identifier list（識別符號清單）: global 陳述式. (line    6)
* , （逗號）;identifier list（識別符號清單） <1>: nonlocal 陳述式.
                                                             (line    6)
* , （逗號）;import statement（引入陳述式）: import 陳述式.  (line    6)
* , （逗號）;parameter list（參數列表）: 函式定義.           (line    6)
* , （逗號）;slicing（切片）:            Slicings.           (line    6)
* , （逗號）;with statement（with 陳述式）: The with statement.
                                                             (line    6)
* , （逗號）;於字串格式化:               格式規格 Format Specification 迷你語言.
                                                             (line   92)
* , （逗號）;於字典顯示:                 Dictionary displays.
                                                             (line    6)
* , （逗號）;於目標列表中:               Assignment statements.
                                                             (line   35)
* ; （冒號）;annotated variable（註釋變數）: Annotated assignment statements.
                                                             (line    6)
* ; （冒號）;compound statement（複合陳述式）: The if statement.
                                                             (line    6)
* ; （冒號）;compound statement（複合陳述式） <1>: The while statement.
                                                             (line    6)
* ; （冒號）;compound statement（複合陳述式） <2>: The for statement.
                                                             (line    6)
* ; （冒號）;compound statement（複合陳述式） <3>: The try statement.
                                                             (line    6)
* ; （冒號）;compound statement（複合陳述式） <4>: The with statement.
                                                             (line    6)
* ; （冒號）;compound statement（複合陳述式） <5>: The match statement.
                                                             (line    6)
* ; （冒號）;compound statement（複合陳述式） <6>: 函式定義. (line    6)
* ; （冒號）;compound statement（複合陳述式） <7>: 類別定義. (line    6)
* ; （冒號）;function annotations（函式註釋）: 函式註釋 Function Annotations.
                                                             (line    6)
* ; （冒號）;function annotations（函式註釋） <1>: 函式定義. (line  106)
* ; （冒號）;lambda expression（lambda 運算式）: Lambdas.    (line    6)
* ; （冒號）;path separator (POSIX)（路徑分隔器 (POSIX)）: Miscellaneous System Information.
                                                             (line  138)
* ; （冒號）;slicing（切片）:            Slicings.           (line    6)
* ; （冒號）;於 SQL 陳述式中:            Cursor 物件.        (line   24)
* ; （冒號）;於字串格式化:               格式化文字語法.     (line   13)
* ; （冒號）;於字典運算式:               Dictionary displays.
                                                             (line    6)
* ; （冒號）;於格式化字串常數中:         String literal concatenation.
                                                             (line   24)
* ; （分號）:                            複合陳述式.         (line   18)
* ; （分號） <1>:                        Miscellaneous System Information.
                                                             (line  138)
* ;= （冒號等於）:                       Boolean operations. (line   38)
* ! (pdb command):                       Debugger Commands.  (line  401)
* ! （驚嘆號）;於 command interpreter（指令直譯器）中: Cmd 物件.
                                                             (line   27)
* ! （驚嘆號）;於 curses 模組中:         curses ascii --- ASCII 字元的工具程式.
                                                             (line  229)
* ! （驚嘆號）;於 glob 風格的萬用字元中: glob --- Unix 風格的路徑名稱模式擴展.
                                                             (line   10)
* ! （驚嘆號）;於 glob 風格的萬用字元中 <1>: fnmatch --- Unix 檔案名稱模式比對.
                                                             (line   15)
* ! （驚嘆號）;於 struct format strings（結構格式字串）: Byte Order Size and Alignment.
                                                             (line   13)
* ! （驚嘆號）;於字串格式化:             格式化文字語法.     (line   13)
* ! （驚嘆號）;於格式化字串常數中:       String literal concatenation.
                                                             (line   24)
* ! patterns:                            Patterns.           (line    6)
* ? （問號）;replacement character（替代字元）: Error Handlers.
                                                             (line   15)
* ? （問號）;於 argparse 模組中:         nargs.              (line   24)
* ? （問號）;於 AST 文法中:              節點 Node 類別.     (line   18)
* ? （問號）;於 command interpreter（指令直譯器）中: Cmd 物件.
                                                             (line   27)
* ? （問號）;於 glob 風格的萬用字元中:   glob --- Unix 風格的路徑名稱模式擴展.
                                                             (line   10)
* ? （問號）;於 glob 風格的萬用字元中 <1>: fnmatch --- Unix 檔案名稱模式比對.
                                                             (line   15)
* ? （問號）;於 SQL 陳述式中:            Cursor 物件.        (line   24)
* ? （問號）;於 struct format strings（結構格式字串）: Format Characters.
                                                             (line   86)
* ? （問號）;於 struct format strings（結構格式字串） <1>: Format Characters.
                                                             (line  168)
* ? （問號）;於正規表示式中:             正規表示式語法.     (line   81)
* ??;於正規表示式中:                     正規表示式語法.     (line   86)
* ?+;於正規表示式中:                     正規表示式語法.     (line   96)
* . （點）;attribute reference（屬性參照）: Attribute references.
                                                             (line    6)
* . （點）;於 glob 風格的萬用字元中:     glob --- Unix 風格的路徑名稱模式擴展.
                                                             (line   10)
* . （點）;於 pathnames（路徑名稱）中:   Miscellaneous System Information.
                                                             (line  104)
* . （點）;於 pathnames（路徑名稱）中 <1>: Miscellaneous System Information.
                                                             (line  132)
* . （點）;於 printf 風格格式化:         printf-style String Formatting.
                                                             (line   29)
* . （點）;於 printf 風格格式化 <1>:     printf-style Bytes Formatting.
                                                             (line   23)
* . （點）;於字串格式化:                 格式化文字語法.     (line   13)
* . （點）;於數值常數中:                 Integer literals.   (line   40)
* . （點）;於正規表示式中:               正規表示式語法.     (line   46)
* ..;於 pathnames（路徑名稱）中:         Miscellaneous System Information.
                                                             (line  110)
* ...:                                   術語表.             (line   10)
* ...;ellipsis literal（刪節號）:        Ellipsis.           (line    6)
* ...;ellipsis literal（刪節號） <1>:    內建常數.           (line   53)
* ...;ellipsis literal（刪節號） <2>:    The Null Object.    (line   12)
* ...;interpreter prompt（直譯器提示）:  How are Docstring Examples Recognized?.
                                                             (line   26)
* ...;interpreter prompt（直譯器提示） <1>: sys --- 系統特定的參數與函式.
                                                             (line 1440)
* ...;placeholder（佔位符號）:           textwrap --- 文字包裝與填充.
                                                             (line  277)
* ...;placeholder（佔位符號） <1>:       PrettyPrinter 物件. (line    6)
* ...;placeholder（佔位符號） <2>:       reprlib --- repr 的替代實作.
                                                             (line   60)
* ...;於 doctests 中:                    可選旗標.           (line   49)
* .ini;file（檔案）:                     configparser --- 設定檔剖析器.
                                                             (line    8)
* .pdbrc;file（檔案）:                   Debugger Commands.  (line   59)
* ' （單引號）;string literal（字串常數）: Literals.         (line    8)
* ''';string literal（字串常數）:        String and Bytes literals.
                                                             (line   36)
* " （雙引號）;string literal（字串常數）: Literals.         (line    8)
* """;string literal（字串常數）:        String and Bytes literals.
                                                             (line   36)
* (?;;於正規表示式中:                    正規表示式語法.     (line  281)
* (?;於正規表示式中:                     正規表示式語法.     (line  242)
* (?!;於正規表示式中:                    正規表示式語法.     (line  398)
* (?(;於正規表示式中:                    正規表示式語法.     (line  441)
* (?#;於正規表示式中:                    正規表示式語法.     (line  387)
* (?<!;於正規表示式中:                   正規表示式語法.     (line  432)
* (?<=;於正規表示式中:                   正規表示式語法.     (line  404)
* (?=;於正規表示式中:                    正規表示式語法.     (line  391)
* (?P<;於正規表示式中:                   正規表示式語法.     (line  344)
* (?P=;於正規表示式中:                   正規表示式語法.     (line  382)
* () （圓括號）;call（呼叫）:            Slicings.           (line   38)
* () （圓括號）;class definition（類別定義）: 類別定義.      (line    6)
* () （圓括號）;function definition（函式定義）: 函式定義.   (line    6)
* () （圓括號）;generator expression（產生器運算式）: Generator expressions.
                                                             (line    6)
* () （圓括號）;tuple display:           Parenthesized forms.
                                                             (line    6)
* () （圓括號）;於 printf 風格格式化:    printf-style String Formatting.
                                                             (line   29)
* () （圓括號）;於 printf 風格格式化 <1>: printf-style Bytes Formatting.
                                                             (line   23)
* () （圓括號）;於正規表示式中:          正規表示式語法.     (line  233)
* () （圓括號）;於賦值目標列表中:        Assignment statements.
                                                             (line   35)
* [] （方括號）;list expression（串列運算式）: List displays.
                                                             (line    6)
* [] （方括號）;subscription（下標）:    Subscriptions.      (line    6)
* [] （方括號）;於 glob 風格的萬用字元中: glob --- Unix 風格的路徑名稱模式擴展.
                                                             (line   10)
* [] （方括號）;於 glob 風格的萬用字元中 <1>: fnmatch --- Unix 檔案名稱模式比對.
                                                             (line   15)
* [] （方括號）;於字串格式化:            格式化文字語法.     (line   13)
* [] （方括號）;於正規表示式中:          正規表示式語法.     (line  171)
* [] （方括號）;於賦值目標列表中:        Assignment statements.
                                                             (line   35)
* {} （花括號）;dictionary expression（字典運算式）: Dictionary displays.
                                                             (line    6)
* {} （花括號）;set expression（集合運算式）: Set displays.  (line    6)
* {} （花括號）;於字串格式化:            格式化文字語法.     (line   13)
* {} （花括號）;於格式化字串常數中:      String literal concatenation.
                                                             (line   24)
* {} （花括號）;於正規表示式中:          正規表示式語法.     (line  115)
* @ （在）;class definition（類別定義）: 類別定義.           (line   44)
* @ （在）;function definition（函式定義）: 函式定義.        (line   32)
* @ （在）;於 struct format strings（結構格式字串）: Byte Order Size and Alignment.
                                                             (line   13)
* * （星號）;function definition（函式定義）: 函式定義.      (line   90)
* * （星號）;import statement（引入陳述式）: import 陳述式.  (line   80)
* * （星號）;於 argparse 模組中:         nargs.              (line   57)
* * （星號）;於 AST 文法中:              節點 Node 類別.     (line   18)
* * （星號）;於 expression list（運算式串列）: Expression lists.
                                                             (line   16)
* * （星號）;於 glob 風格的萬用字元中:   glob --- Unix 風格的路徑名稱模式擴展.
                                                             (line   10)
* * （星號）;於 glob 風格的萬用字元中 <1>: fnmatch --- Unix 檔案名稱模式比對.
                                                             (line   15)
* * （星號）;於 printf 風格格式化:       printf-style String Formatting.
                                                             (line   29)
* * （星號）;於 printf 風格格式化 <1>:   printf-style Bytes Formatting.
                                                             (line   23)
* * （星號）;於函式呼叫中:               任意引數列表 Arbitrary Argument Lists.
                                                             (line    6)
* * （星號）;於函式呼叫中 <1>:           Calls.              (line   72)
* * （星號）;於正規表示式中:             正規表示式語法.     (line   69)
* * （星號）;於賦值目標列表中:           Assignment statements.
                                                             (line   35)
* *?;於正規表示式中:                     正規表示式語法.     (line   86)
* **;function definition（函式定義）:    函式定義.           (line   90)
* **;於 glob 風格的萬用字元中:           glob --- Unix 風格的路徑名稱模式擴展.
                                                             (line   45)
* **;於函式呼叫中:                       拆解引數列表（Unpacking Argument Lists）.
                                                             (line   17)
* **;於函式呼叫中 <1>:                   Calls.              (line   99)
* **;於字典顯示:                         Dictionary displays.
                                                             (line   23)
* **=;augmented assignment（增強賦值）:  Augmented assignment statements.
                                                             (line    6)
* *+;於正規表示式中:                     正規表示式語法.     (line   96)
* *=;augmented assignment（增強賦值）:   Augmented assignment statements.
                                                             (line    6)
* / （斜線）;function definition（函式定義）: 函式定義.      (line   90)
* / （斜線）;於 pathnames（路徑名稱）中: Miscellaneous System Information.
                                                             (line  116)
* / （斜線）;於 pathnames（路徑名稱）中 <1>: Miscellaneous System Information.
                                                             (line  125)
* //=;augmented assignment（增強賦值）:  Augmented assignment statements.
                                                             (line    6)
* /=;augmented assignment（增強賦值）:   Augmented assignment statements.
                                                             (line    6)
* \ （反斜線）;escape sequence（跳脫序列）: String and Bytes literals.
                                                             (line   74)
* \ （反斜線）;escape sequence（跳脫序列） <1>: Error Handlers.
                                                             (line   15)
* \ （反斜線）;in pathnames (Windows)（在路徑名稱中 (Windows)）: Miscellaneous System Information.
                                                             (line  116)
* \ （反斜線）;於正規表示式中:           正規表示式語法.     (line  156)
* \ （反斜線）;於正規表示式中 <1>:       正規表示式語法.     (line  190)
* \ （反斜線）;於正規表示式中 <2>:       正規表示式語法.     (line  460)
* \\;escape sequence（跳脫序列）:        String and Bytes literals.
                                                             (line   74)
* \\;於正規表示式中:                     正規表示式語法.     (line  582)
* \a;escape sequence（跳脫序列）:        String and Bytes literals.
                                                             (line   74)
* \A;於正規表示式中:                     正規表示式語法.     (line  472)
* \a;於正規表示式中:                     正規表示式語法.     (line  582)
* \b;escape sequence（跳脫序列）:        String and Bytes literals.
                                                             (line   74)
* \b;於正規表示式中:                     正規表示式語法.     (line  476)
* \B;於正規表示式中:                     正規表示式語法.     (line  494)
* \b;於正規表示式中 <1>:                 正規表示式語法.     (line  582)
* \d;於正規表示式中:                     正規表示式語法.     (line  505)
* \D;於正規表示式中:                     正規表示式語法.     (line  520)
* \f;escape sequence（跳脫序列）:        String and Bytes literals.
                                                             (line   74)
* \f;於正規表示式中:                     正規表示式語法.     (line  582)
* \g;於正規表示式中:                     Functions.          (line  212)
* \n;escape sequence（跳脫序列）:        String and Bytes literals.
                                                             (line   74)
* \N;escape sequence（跳脫序列）:        String and Bytes literals.
                                                             (line   74)
* \N;escape sequence（跳脫序列） <1>:    Error Handlers.     (line   54)
* \n;於正規表示式中:                     正規表示式語法.     (line  582)
* \N;於正規表示式中:                     正規表示式語法.     (line  582)
* \r;escape sequence（跳脫序列）:        String and Bytes literals.
                                                             (line   74)
* \r;於正規表示式中:                     正規表示式語法.     (line  582)
* \s;於正規表示式中:                     正規表示式語法.     (line  527)
* \S;於正規表示式中:                     正規表示式語法.     (line  543)
* \t;escape sequence（跳脫序列）:        String and Bytes literals.
                                                             (line   74)
* \t;於正規表示式中:                     正規表示式語法.     (line  582)
* \u;escape sequence（跳脫序列）:        String and Bytes literals.
                                                             (line   74)
* \U;escape sequence（跳脫序列）:        String and Bytes literals.
                                                             (line   74)
* \u;escape sequence（跳脫序列） <1>:    Error Handlers.     (line   15)
* \U;escape sequence（跳脫序列） <1>:    Error Handlers.     (line   15)
* \u;於正規表示式中:                     正規表示式語法.     (line  582)
* \U;於正規表示式中:                     正規表示式語法.     (line  582)
* \v;escape sequence（跳脫序列）:        String and Bytes literals.
                                                             (line   74)
* \v;於正規表示式中:                     正規表示式語法.     (line  582)
* \w;於正規表示式中:                     正規表示式語法.     (line  550)
* \W;於正規表示式中:                     正規表示式語法.     (line  567)
* \x;escape sequence（跳脫序列）:        String and Bytes literals.
                                                             (line   74)
* \x;escape sequence（跳脫序列） <1>:    Error Handlers.     (line   15)
* \x;於正規表示式中:                     正規表示式語法.     (line  582)
* \Z;於正規表示式中:                     正規表示式語法.     (line  578)
* &=;augmented assignment（增強賦值）:   Augmented assignment statements.
                                                             (line    6)
* # (hash);comment（註解）:              一個非正式的 Python 簡介.
                                                             (line   12)
* # （井字號）;comment（註解）:          Comments.           (line    6)
* # （井字號）;comment（註解） <1>:      site --- Site-specific configuration hook.
                                                             (line   52)
* # （井字號）;source encoding declaration（原始編碼宣告）: Encoding declarations.
                                                             (line    6)
* # （井字號）;於 doctests 中:           可選旗標.           (line  172)
* # （井字號）;於 printf 風格格式化:     printf-style String Formatting.
                                                             (line   69)
* # （井字號）;於 printf 風格格式化 <1>: printf-style Bytes Formatting.
                                                             (line   63)
* # （井字號）;於字串格式化:             格式規格 Format Specification 迷你語言.
                                                             (line   80)
* # （井字號）;於正規表示式中:           旗標.               (line  129)
* % （百分號）;datetime format（日期時間格式）: timezone 物件.
                                                             (line   71)
* % （百分號）;datetime format（日期時間格式） <1>: 函式<4>. (line  267)
* % （百分號）;datetime format（日期時間格式） <2>: 函式<4>. (line  399)
* % （百分號）;environment variables expansion (Windows) （環境變數展開 (Windows)）: 函式<12>.
                                                             (line  228)
* % （百分號）;environment variables expansion (Windows)（環境變數展開 (Windows)）: os path --- 常見的路徑名操作.
                                                             (line  140)
* % （百分號）;interpolation in configuration files（設定檔中的插值）: Interpolation of values.
                                                             (line   10)
* % （百分號）;printf 風格格式化:        printf-style String Formatting.
                                                             (line    6)
* % （百分號）;printf 風格格式化 <1>:    printf-style Bytes Formatting.
                                                             (line    6)
* %=;augmented assignment（增強賦值）:   Augmented assignment statements.
                                                             (line    6)
* %APPDATA%:                             Redirection of local data registry and temporary paths.
                                                             (line   13)
* ^ （插入符號）;marker（標記）:         What About Exceptions?.
                                                             (line   93)
* ^ （插入符號）;marker（標記） <1>:     traceback --- 列印或取得堆疊回溯 stack traceback.
                                                             (line   64)
* ^ （插入符號）;於 curses 模組中:       curses ascii --- ASCII 字元的工具程式.
                                                             (line  229)
* ^ （插入符號）;於字串格式化:           格式規格 Format Specification 迷你語言.
                                                             (line   35)
* ^ （插入符號）;於正規表示式中:         正規表示式語法.     (line   53)
* ^ （插入符號）;於正規表示式中 <1>:     正規表示式語法.     (line  194)
* ^=;augmented assignment（增強賦值）:   Augmented assignment statements.
                                                             (line    6)
* + （加號）;binary operator（二元運算子）: Binary arithmetic operations.
                                                             (line   74)
* + （加號）;binary operator（二元運算子） <1>: 數值型別 --- int、float、complex.
                                                             (line   21)
* + （加號）;unary operator（一元運算子）: Unary arithmetic and bitwise operations.
                                                             (line   14)
* + （加號）;unary operator（一元運算子） <1>: 數值型別 --- int、float、complex.
                                                             (line   21)
* + （加號）;於 argparse 模組中:         nargs.              (line   69)
* + （加號）;於 doctests 中:             可選旗標.           (line  172)
* + （加號）;於 printf 風格格式化:       printf-style String Formatting.
                                                             (line   69)
* + （加號）;於 printf 風格格式化 <1>:   printf-style Bytes Formatting.
                                                             (line   63)
* + （加號）;於字串格式化:               格式規格 Format Specification 迷你語言.
                                                             (line   60)
* + （加號）;於正規表示式中:             正規表示式語法.     (line   75)
* +?;於正規表示式中:                     正規表示式語法.     (line   86)
* ++;於正規表示式中:                     正規表示式語法.     (line   96)
* +=;augmented assignment（增強賦值）:   Augmented assignment statements.
                                                             (line    6)
* < （小於）;於 struct format strings（結構格式字串）: Byte Order Size and Alignment.
                                                             (line   13)
* < （小於）;於字串格式化:               格式規格 Format Specification 迷你語言.
                                                             (line   35)
* <<=;augmented assignment（增強賦值）:  Augmented assignment statements.
                                                             (line    6)
* <BLANKLINE>:                           可選旗標.           (line   30)
* = （等於）;assignment statement（賦值陳述式）: Assignment statements.
                                                             (line    6)
* = （等於）;class definition（類別定義）: Metaclasses.      (line    6)
* = （等於）;for help in debugging using string literals（使用字串常數進行除錯）: String literal concatenation.
                                                             (line   24)
* = （等於）;function definition（函式定義）: 函式定義.      (line   65)
* = （等於）;於 struct format strings（結構格式字串）: Byte Order Size and Alignment.
                                                             (line   13)
* = （等於）;於函式呼叫中:               Slicings.           (line   37)
* = （等於）;於字串格式化:               格式規格 Format Specification 迷你語言.
                                                             (line   35)
* > （大於）;於 struct format strings（結構格式字串）: Byte Order Size and Alignment.
                                                             (line   13)
* > （大於）;於字串格式化:               格式規格 Format Specification 迷你語言.
                                                             (line   35)
* >>=;augmented assignment（增強賦值）:  Augmented assignment statements.
                                                             (line    6)
* >>>:                                   術語表.             (line    6)
* >>>;interpreter prompt（直譯器提示）:  How are Docstring Examples Recognized?.
                                                             (line   26)
* >>>;interpreter prompt（直譯器提示） <1>: sys --- 系統特定的參數與函式.
                                                             (line 1440)
* | （垂直線）;於正規表示式中:           正規表示式語法.     (line  220)
* |=;augmented assignment（增強賦值）:   Augmented assignment statements.
                                                             (line    6)
* ~ （波浪號）;home directory expansion（家目錄展開）: os path --- 常見的路徑名操作.
                                                             (line  118)
* $ （金錢符號）;environment variables expansion（環境變數展開）: os path --- 常見的路徑名操作.
                                                             (line  140)
* $ （金錢符號）;interpolation in configuration files（設定檔中的插值）: Interpolation of values.
                                                             (line   41)
* $ （金錢符號）;於 template strings（模板字串）: 模板字串.  (line   11)
* $ （金錢符號）;於正規表示式中:         正規表示式語法.     (line   58)
* 0b;integer literal（整數常數）:        Numeric literals.   (line   14)
* 0o;integer literal（整數常數）:        Numeric literals.   (line   14)
* 0x;integer literal（整數常數）:        Numeric literals.   (line   14)
* 2-digit years（2 位數年份）:           time --- 時間存取與轉換.
                                                             (line   28)
* A (於 re 模組中):                      旗標.               (line   16)
* A_ALTCHARSET (於 curses 模組中):       Constants.          (line   67)
* A_ATTRIBUTES (於 curses 模組中):       Constants.          (line  128)
* A_BLINK (於 curses 模組中):            Constants.          (line   70)
* A_BOLD (於 curses 模組中):             Constants.          (line   73)
* A_CHARTEXT (於 curses 模組中):         Constants.          (line  131)
* A_COLOR (於 curses 模組中):            Constants.          (line  134)
* A_DIM (於 curses 模組中):              Constants.          (line   76)
* A_HORIZONTAL (於 curses 模組中):       Constants.          (line  101)
* A_INVIS (於 curses 模組中):            Constants.          (line   79)
* A_ITALIC (於 curses 模組中):           Constants.          (line   82)
* A_LEFT (於 curses 模組中):             Constants.          (line  104)
* A_LOW (於 curses 模組中):              Constants.          (line  107)
* A_NORMAL (於 curses 模組中):           Constants.          (line   85)
* A_PROTECT (於 curses 模組中):          Constants.          (line   88)
* A_REVERSE (於 curses 模組中):          Constants.          (line   91)
* A_RIGHT (於 curses 模組中):            Constants.          (line  110)
* A_STANDOUT (於 curses 模組中):         Constants.          (line   95)
* A_TOP (於 curses 模組中):              Constants.          (line  113)
* A_UNDERLINE (於 curses 模組中):        Constants.          (line   98)
* A_VERTICAL (於 curses 模組中):         Constants.          (line  116)
* a2b_base64() (於 binascii 模組中):     binascii --- 在二進位制和 ASCII 之間轉換.
                                                             (line   40)
* a2b_hex() (於 binascii 模組中):        binascii --- 在二進位制和 ASCII 之間轉換.
                                                             (line  143)
* a2b_qp() (於 binascii 模組中):         binascii --- 在二進位制和 ASCII 之間轉換.
                                                             (line   70)
* a2b_uu() (於 binascii 模組中):         binascii --- 在二進位制和 ASCII 之間轉換.
                                                             (line   25)
* a85decode() (於 base64 模組中):        base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  170)
* a85encode() (於 base64 模組中):        base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  149)
* ABC (abc 中的類別):                    abc --- 抽象基底類別.
                                                             (line   23)
* ABCMeta (abc 中的類別):                abc --- 抽象基底類別.
                                                             (line   46)
* ABDAY_1 (於 locale 模組中):            locale --- 國際化服務.
                                                             (line  226)
* ABDAY_2 (於 locale 模組中):            locale --- 國際化服務.
                                                             (line  226)
* ABDAY_3 (於 locale 模組中):            locale --- 國際化服務.
                                                             (line  226)
* ABDAY_4 (於 locale 模組中):            locale --- 國際化服務.
                                                             (line  226)
* ABDAY_5 (於 locale 模組中):            locale --- 國際化服務.
                                                             (line  226)
* ABDAY_6 (於 locale 模組中):            locale --- 國際化服務.
                                                             (line  226)
* ABDAY_7 (於 locale 模組中):            locale --- 國際化服務.
                                                             (line  226)
* abiflags (於 sys 模組中):              sys --- 系統特定的參數與函式.
                                                             (line   12)
* ABMON_1 (於 locale 模組中):            locale --- 國際化服務.
                                                             (line  251)
* ABMON_10 (於 locale 模組中):           locale --- 國際化服務.
                                                             (line  251)
* ABMON_11 (於 locale 模組中):           locale --- 國際化服務.
                                                             (line  251)
* ABMON_12 (於 locale 模組中):           locale --- 國際化服務.
                                                             (line  251)
* ABMON_2 (於 locale 模組中):            locale --- 國際化服務.
                                                             (line  251)
* ABMON_3 (於 locale 模組中):            locale --- 國際化服務.
                                                             (line  251)
* ABMON_4 (於 locale 模組中):            locale --- 國際化服務.
                                                             (line  251)
* ABMON_5 (於 locale 模組中):            locale --- 國際化服務.
                                                             (line  251)
* ABMON_6 (於 locale 模組中):            locale --- 國際化服務.
                                                             (line  251)
* ABMON_7 (於 locale 模組中):            locale --- 國際化服務.
                                                             (line  251)
* ABMON_8 (於 locale 模組中):            locale --- 國際化服務.
                                                             (line  251)
* ABMON_9 (於 locale 模組中):            locale --- 國際化服務.
                                                             (line  251)
* ABORT (於 tkinter.messagebox 模組中):  tkinter messagebox --- Tkinter 訊息提示.
                                                             (line  127)
* abort_clients() (asyncio.Server 的方法): Server 物件.      (line   52)
* abort() (asyncio.Barrier 的方法):      Barrier.            (line   87)
* abort() (asyncio.DatagramTransport 的方法): Datagram Transports.
                                                             (line   20)
* abort() (asyncio.WriteTransport 的方法): Write-only Transports.
                                                             (line    6)
* abort() (ftplib.FTP 的方法):           FTP 物件.           (line  134)
* abort() (threading.Barrier 的方法):    Barrier Objects.    (line   82)
* abort() (於 os 模組中):                行程管理.           (line   16)
* abort（C 函式）:                       行程控制.           (line    7)
* ABORTRETRYIGNORE (於 tkinter.messagebox 模組中): tkinter messagebox --- Tkinter 訊息提示.
                                                             (line  142)
* ABOVE_NORMAL_PRIORITY_CLASS (於 subprocess 模組中): Windows Constants.
                                                             (line   68)
* above() (curses.panel.Panel 的方法):   Panel Objects.      (line   13)
* abs() (decimal.Context 的方法):        Context objects.    (line  249)
* abs() (於 operator 模組中):            operator --- 標準運算子替代函式.
                                                             (line   65)
* absolute() (pathlib.Path 的方法):      Expanding and resolving paths.
                                                             (line   37)
* AbsoluteLinkError:                     tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  251)
* AbsolutePathError:                     tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  237)
* abspath() (於 os.path 模組中):         os path --- 常見的路徑名操作.
                                                             (line   43)
* abstract base class（抽象基底類別）:   術語表.             (line   23)
* AbstractAsyncContextManager (contextlib 中的類別): Utilities.
                                                             (line   19)
* AbstractBasicAuthHandler (urllib.request 中的類別): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  302)
* AbstractChildWatcher (asyncio 中的類別): Process Watchers. (line   43)
* abstractclassmethod() (於 abc 模組中): abc --- 抽象基底類別.
                                                             (line  210)
* AbstractContextManager (contextlib 中的類別): Utilities.   (line    8)
* AbstractDigestAuthHandler (urllib.request 中的類別): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  340)
* AbstractEventLoop (asyncio 中的類別):  事件迴圈實作.       (line   53)
* AbstractEventLoopPolicy (asyncio 中的類別): Policy Objects.
                                                             (line    8)
* abstractmethod() (於 abc 模組中):      abc --- 抽象基底類別.
                                                             (line  144)
* abstractproperty() (於 abc 模組中):    abc --- 抽象基底類別.
                                                             (line  248)
* AbstractSet (typing 中的類別):         collections abc 中容器 ABC 的別名.
                                                             (line    6)
* abstractstaticmethod() (於 abc 模組中): abc --- 抽象基底類別.
                                                             (line  229)
* accept() (multiprocessing.connection.Listener 的方法): Listeners and Clients.
                                                             (line   84)
* accept() (socket.socket 的方法):       Socket 物件.        (line   13)
* access() (於 os 模組中):               Files and Directories.
                                                             (line   51)
* accumulate() (於 itertools 模組中):    Itertool 函式.      (line    9)
* ACK (於 curses.ascii 模組中):          curses ascii --- ASCII 字元的工具程式.
                                                             (line   37)
* aclose() (agen 的方法):                Asynchronous generator-iterator methods.
                                                             (line   60)
* aclose() (contextlib.AsyncExitStack 的方法): Utilities.    (line  650)
* aclosing() (於 contextlib 模組中):     Utilities.          (line  188)
* acos() (於 cmath 模組中):              三角函數.           (line    6)
* acos() (於 math 模組中):               Trigonometric functions.
                                                             (line    6)
* acosh() (於 cmath 模組中):             雙曲函數.           (line    6)
* acosh() (於 math 模組中):              Hyperbolic functions.
                                                             (line    9)
* acquire() (_thread.lock 的方法):       _thread --- 低階執行緒 API.
                                                             (line  120)
* acquire() (asyncio.Condition 的方法):  Condition.          (line   41)
* acquire() (asyncio.Lock 的方法):       Lock.               (line   34)
* acquire() (asyncio.Semaphore 的方法):  Semaphore.          (line   39)
* acquire() (logging.Handler 的方法):    Handler Objects.    (line   26)
* acquire() (multiprocessing.Lock 的方法): Synchronization primitives.
                                                             (line   63)
* acquire() (multiprocessing.RLock 的方法): Synchronization primitives.
                                                             (line  117)
* acquire() (threading.Condition 的方法): Condition Objects. (line   85)
* acquire() (threading.Lock 的方法):     Lock Objects.       (line   43)
* acquire() (threading.RLock 的方法):    RLock 物件.         (line   44)
* acquire() (threading.Semaphore 的方法): Semaphore Objects. (line   34)
* ACS_BBSS (於 curses 模組中):           Constants.          (line  472)
* ACS_BLOCK (於 curses 模組中):          Constants.          (line  475)
* ACS_BOARD (於 curses 模組中):          Constants.          (line  478)
* ACS_BSBS (於 curses 模組中):           Constants.          (line  481)
* ACS_BSSB (於 curses 模組中):           Constants.          (line  484)
* ACS_BSSS (於 curses 模組中):           Constants.          (line  487)
* ACS_BTEE (於 curses 模組中):           Constants.          (line  490)
* ACS_BULLET (於 curses 模組中):         Constants.          (line  493)
* ACS_CKBOARD (於 curses 模組中):        Constants.          (line  496)
* ACS_DARROW (於 curses 模組中):         Constants.          (line  499)
* ACS_DEGREE (於 curses 模組中):         Constants.          (line  502)
* ACS_DIAMOND (於 curses 模組中):        Constants.          (line  505)
* ACS_GEQUAL (於 curses 模組中):         Constants.          (line  508)
* ACS_HLINE (於 curses 模組中):          Constants.          (line  511)
* ACS_LANTERN (於 curses 模組中):        Constants.          (line  514)
* ACS_LARROW (於 curses 模組中):         Constants.          (line  517)
* ACS_LEQUAL (於 curses 模組中):         Constants.          (line  520)
* ACS_LLCORNER (於 curses 模組中):       Constants.          (line  523)
* ACS_LRCORNER (於 curses 模組中):       Constants.          (line  526)
* ACS_LTEE (於 curses 模組中):           Constants.          (line  529)
* ACS_NEQUAL (於 curses 模組中):         Constants.          (line  532)
* ACS_PI (於 curses 模組中):             Constants.          (line  535)
* ACS_PLMINUS (於 curses 模組中):        Constants.          (line  538)
* ACS_PLUS (於 curses 模組中):           Constants.          (line  541)
* ACS_RARROW (於 curses 模組中):         Constants.          (line  544)
* ACS_RTEE (於 curses 模組中):           Constants.          (line  547)
* ACS_S1 (於 curses 模組中):             Constants.          (line  550)
* ACS_S3 (於 curses 模組中):             Constants.          (line  553)
* ACS_S7 (於 curses 模組中):             Constants.          (line  556)
* ACS_S9 (於 curses 模組中):             Constants.          (line  559)
* ACS_SBBS (於 curses 模組中):           Constants.          (line  562)
* ACS_SBSB (於 curses 模組中):           Constants.          (line  565)
* ACS_SBSS (於 curses 模組中):           Constants.          (line  568)
* ACS_SSBB (於 curses 模組中):           Constants.          (line  571)
* ACS_SSBS (於 curses 模組中):           Constants.          (line  574)
* ACS_SSSB (於 curses 模組中):           Constants.          (line  577)
* ACS_SSSS (於 curses 模組中):           Constants.          (line  580)
* ACS_STERLING (於 curses 模組中):       Constants.          (line  583)
* ACS_TTEE (於 curses 模組中):           Constants.          (line  586)
* ACS_UARROW (於 curses 模組中):         Constants.          (line  589)
* ACS_ULCORNER (於 curses 模組中):       Constants.          (line  592)
* ACS_URCORNER (於 curses 模組中):       Constants.          (line  595)
* ACS_VLINE (於 curses 模組中):          Constants.          (line  598)
* Action (argparse 中的類別):            Action classes.     (line   11)
* action (optparse.Option 的屬性):       Option attributes.  (line   19)
* ACTIONS (optparse.Option 的屬性):      Adding new actions. (line   31)
* activate_stack_trampoline() (於 sys 模組中): sys --- 系統特定的參數與函式.
                                                             (line 1699)
* active_children() (於 multiprocessing 模組中): Miscellaneous<2>.
                                                             (line    6)
* active_count() (於 threading 模組中):  threading --- 基於執行緒的平行性.
                                                             (line   52)
* actual() (tkinter.font.Font 的方法):   tkinter font --- Tkinter 字型包裝器.
                                                             (line   46)
* Add (ast 中的類別):                    運算式<2>.          (line   52)
* add_alias() (於 email.charset 模組中): email charset：表示字元集合.
                                                             (line  191)
* add_alternative() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  637)
* add_argument_group() (argparse.ArgumentParser 的方法): Argument groups.
                                                             (line    6)
* add_argument() (argparse.ArgumentParser 的方法): The add_argument method.
                                                             (line    6)
* add_attachment() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  649)
* add_cgi_vars() (wsgiref.handlers.BaseHandler 的方法): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  115)
* add_charset() (於 email.charset 模組中): email charset：表示字元集合.
                                                             (line  162)
* add_child_handler() (asyncio.AbstractChildWatcher 的方法): Process Watchers.
                                                             (line   45)
* add_codec() (於 email.charset 模組中): email charset：表示字元集合.
                                                             (line  200)
* add_cookie_header() (http.cookiejar.CookieJar 的方法): CookieJar 與 FileCookieJar 物件.
                                                             (line   11)
* add_dll_directory() (於 os 模組中):    行程管理.           (line   24)
* add_done_callback() (asyncio.Future 的方法): Future 物件<2>.
                                                             (line   75)
* add_done_callback() (asyncio.Task 的方法): Task Object.    (line  101)
* add_done_callback() (concurrent.futures.Future 的方法): Future 物件.
                                                             (line   55)
* add_fallback() (gettext.NullTranslations 的方法): The NullTranslations class.
                                                             (line   28)
* add_flag() (mailbox.Maildir 的方法):   Mailbox 物件<2>.    (line  129)
* add_flag() (mailbox.MaildirMessage 的方法): MaildirMessage 物件.
                                                             (line   76)
* add_flag() (mailbox.mboxMessage 的方法): mboxMessage 物件. (line   79)
* add_flag() (mailbox.MMDFMessage 的方法): MMDFMessage 物件. (line   78)
* add_folder() (mailbox.Maildir 的方法): Mailbox 物件<2>.    (line   75)
* add_folder() (mailbox.MH 的方法):      MH 物件.            (line   45)
* add_get_handler() (email.contentmanager.ContentManager 的方法): email contentmanager：管理 MIME 內容.
                                                             (line   75)
* add_handler() (urllib.request.OpenerDirector 的方法): OpenerDirector 物件.
                                                             (line    8)
* add_header() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  258)
* add_header() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  366)
* add_header() (urllib.request.Request 的方法): Request Objects.
                                                             (line   78)
* add_header() (wsgiref.headers.Headers 的方法): wsgiref headers -- WSGI 回應標頭工具.
                                                             (line   49)
* add_history() (於 readline 模組中):    History list.       (line   38)
* add_label() (mailbox.BabylMessage 的方法): BabylMessage 物件.
                                                             (line   55)
* add_mutually_exclusive_group() (argparse.ArgumentParser 的方法): Mutual exclusion.
                                                             (line    6)
* add_note() (BaseException 的方法):     基底類別 base classes.
                                                             (line   42)
* add_option() (optparse.OptionParser 的方法): Defining options.
                                                             (line   14)
* add_parent() (urllib.request.BaseHandler 的方法): BaseHandler 物件.
                                                             (line   10)
* add_password() (urllib.request.HTTPPasswordMgr 的方法): HTTPPasswordMgr 物件.
                                                             (line    9)
* add_password() (urllib.request.HTTPPasswordMgrWithPriorAuth 的方法): HTTPPasswordMgrWithPriorAuth 物件.
                                                             (line   10)
* add_reader() (asyncio.loop 的方法):    監視檔案描述器.     (line    6)
* add_related() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  624)
* add_section() (configparser.ConfigParser 的方法): ConfigParser 物件.
                                                             (line  113)
* add_section() (configparser.RawConfigParser 的方法): RawConfigParser 物件.
                                                             (line   26)
* add_sequence() (mailbox.MHMessage 的方法): MHMessage 物件. (line   41)
* add_set_handler() (email.contentmanager.ContentManager 的方法): email contentmanager：管理 MIME 內容.
                                                             (line   80)
* add_signal_handler() (asyncio.loop 的方法): Unix 訊號.     (line    6)
* add_subparsers() (argparse.ArgumentParser 的方法): Sub-commands.
                                                             (line    6)
* add_type() (mimetypes.MimeTypes 的方法): MimeTypes 物件.   (line  104)
* add_type() (於 mimetypes 模組中):      mimetypes --- 將檔案名稱對映到 MIME 類型.
                                                             (line  120)
* add_unredirected_header() (urllib.request.Request 的方法): Request Objects.
                                                             (line   90)
* add_writer() (asyncio.loop 的方法):    監視檔案描述器.     (line   16)
* add() (decimal.Context 的方法):        Context objects.    (line  253)
* add() (frozenset 的方法):              Set Types --- set frozenset.
                                                             (line  195)
* add() (graphlib.TopologicalSorter 的方法): graphlib —-- 使用類圖 graph-like 結構進行操作的功能.
                                                             (line   72)
* add() (mailbox.Mailbox 的方法):        Mailbox 物件.       (line   59)
* add() (mailbox.Maildir 的方法):        Mailbox 物件<2>.    (line  193)
* add() (pstats.Stats 的方法):           The Stats Class.    (line   49)
* add() (tarfile.TarFile 的方法):        TarFile 物件.       (line  270)
* add() (tkinter.ttk.Notebook 的方法):   ttk Notebook.       (line    8)
* add() (於 operator 模組中):            operator --- 標準運算子替代函式.
                                                             (line   70)
* addAsyncCleanup() (unittest.IsolatedAsyncioTestCase 的方法): Test cases.
                                                             (line  883)
* addaudithook() (於 sys 模組中):        sys --- 系統特定的參數與函式.
                                                             (line   25)
* addch() (curses.window 的方法):        Window Objects.     (line    9)
* addClassCleanup() (unittest.TestCase 的類別方法): Test cases.
                                                             (line  802)
* addCleanup() (unittest.TestCase 的方法): Test cases.       (line  762)
* addcomponent() (turtle.Shape 的方法):  Public classes.     (line   65)
* addDuration() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  438)
* addError() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  368)
* addExpectedFailure() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  404)
* addFailure() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  379)
* addfile() (tarfile.TarFile 的方法):    TarFile 物件.       (line  288)
* addFilter() (logging.Handler 的方法):  Handler Objects.    (line   52)
* addFilter() (logging.Logger 的方法):   Logger 物件.        (line  322)
* addHandler() (logging.Logger 的方法):  Logger 物件.        (line  339)
* addinfourl (urllib.response 中的類別): urllib response --- Response classes used by urllib.
                                                             (line   12)
* addition（加）:                        Binary arithmetic operations.
                                                             (line   74)
* addLevelName() (於 logging 模組中):    Module-Level Functions.
                                                             (line  128)
* addModuleCleanup() (於 unittest 模組中): setUpModule and tearDownModule.
                                                             (line   22)
* addnstr() (curses.window 的方法):      Window Objects.     (line   23)
* AddPackagePath() (於 modulefinder 模組中): modulefinder --- 搜尋腳本所使用的模組.
                                                             (line   14)
* addr_spec (email.headerregistry.Address 的屬性): email headerregistry：自訂標頭物件.
                                                             (line  440)
* Address (email.headerregistry 中的類別): email headerregistry：自訂標頭物件.
                                                             (line  402)
* address (email.headerregistry.SingleAddressHeader 的屬性): email headerregistry：自訂標頭物件.
                                                             (line  222)
* address (multiprocessing.connection.Listener 的屬性): Listeners and Clients.
                                                             (line   99)
* address (multiprocessing.managers.BaseManager 的屬性): Managers.
                                                             (line  137)
* address_exclude() (ipaddress.IPv4Network 的方法): Network objects.
                                                             (line  160)
* address_exclude() (ipaddress.IPv6Network 的方法): Network objects.
                                                             (line  342)
* address_family (socketserver.BaseServer 的屬性): Server Objects.
                                                             (line   65)
* address_string() (http.server.BaseHTTPRequestHandler 的方法): http server — HTTP 伺服器.
                                                             (line  331)
* addresses (email.headerregistry.AddressHeader 的屬性): email headerregistry：自訂標頭物件.
                                                             (line  195)
* addresses (email.headerregistry.Group 的屬性): email headerregistry：自訂標頭物件.
                                                             (line  475)
* AddressHeader (email.headerregistry 中的類別): email headerregistry：自訂標頭物件.
                                                             (line  180)
* addressof() (於 ctypes 模組中):        Utility functions.  (line    6)
* AddressValueError:                     Custom Exceptions.  (line    9)
* addshape() (於 turtle 模組中):         Settings and special methods.
                                                             (line   70)
* addsitedir() (於 site 模組中):         模組內容<10>.       (line   51)
* addSkip() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  396)
* addstr() (curses.window 的方法):       Window Objects.     (line   31)
* addSubTest() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  422)
* addSuccess() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  390)
* addTest() (unittest.TestSuite 的方法): Grouping tests.     (line   25)
* addTests() (unittest.TestSuite 的方法): Grouping tests.    (line   30)
* addTypeEqualityFunc() (unittest.TestCase 的方法): Test cases.
                                                             (line  579)
* addUnexpectedSuccess() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  414)
* adjust_int_max_str_digits() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  734)
* adjusted() (decimal.Decimal 的方法):   Decimal objects.    (line  113)
* adler32() (於 zlib 模組中):            zlib --- 相容於 gzip 的壓縮.
                                                             (line   25)
* AF_ALG (於 socket 模組中):             常數<7>.            (line  259)
* AF_CAN (於 socket 模組中):             常數<7>.            (line  125)
* AF_DIVERT (於 socket 模組中):          常數<7>.            (line  198)
* AF_HYPERV (於 socket 模組中):          常數<7>.            (line  341)
* AF_INET (於 socket 模組中):            常數<7>.            (line   11)
* AF_INET6 (於 socket 模組中):           常數<7>.            (line   11)
* AF_LINK (於 socket 模組中):            常數<7>.            (line  283)
* AF_PACKET (於 socket 模組中):          常數<7>.            (line  208)
* AF_QIPCRTR (於 socket 模組中):         常數<7>.            (line  311)
* AF_RDS (於 socket 模組中):             常數<7>.            (line  230)
* AF_UNIX (於 socket 模組中):            常數<7>.            (line   11)
* AF_UNSPEC (於 socket 模組中):          常數<7>.            (line   21)
* AF_VSOCK (於 socket 模組中):           常數<7>.            (line  270)
* alarm() (於 signal 模組中):            模組內容<5>.        (line  269)
* ALERT_DESCRIPTION_HANDSHAKE_FAILURE (於 ssl 模組中): 常數<8>.
                                                             (line  452)
* ALERT_DESCRIPTION_INTERNAL_ERROR (於 ssl 模組中): 常數<8>. (line  452)
* AlertDescription (ssl 中的類別):       常數<8>.            (line  465)
* algorithm (sys.hash_info 的屬性):      sys --- 系統特定的參數與函式.
                                                             (line 1017)
* algorithms_available (於 hashlib 模組中): 屬性.            (line   16)
* algorithms_guaranteed (於 hashlib 模組中): 屬性.           (line    8)
* alias (ast 中的類別):                  引入 imports.       (line   36)
* alias (pdb command):                   Debugger Commands.  (line  373)
* alignment() (於 ctypes 模組中):        Utility functions.  (line   13)
* alive (weakref.finalize 的屬性):       weakref --- 弱參照. (line  254)
* ALL_COMPLETED (於 asyncio 模組中):     Waiting Primitives. (line   45)
* ALL_COMPLETED (於 concurrent.futures 模組中): 模組函式.    (line   33)
* all_errors (於 ftplib 模組中):         模組變數.           (line   25)
* all_features (於 xml.sax.handler 模組中): xml sax handler --- SAX 處理函式的基本類別.
                                                             (line   95)
* all_frames (tracemalloc.Filter 的屬性): Filter.            (line   58)
* all_properties (於 xml.sax.handler 模組中): xml sax handler --- SAX 處理函式的基本類別.
                                                             (line  127)
* all_suffixes() (於 importlib.machinery 模組中): importlib machinery -- Importers and path hooks.
                                                             (line   54)
* all_tasks() (於 asyncio 模組中):       Introspection.      (line   16)
* allocate_lock() (於 _thread 模組中):   _thread --- 低階執行緒 API.
                                                             (line   70)
* allocfunc (C type):                    Slot Type typedefs. (line    6)
* allow_reuse_address (socketserver.BaseServer 的屬性): Server Objects.
                                                             (line   92)
* allowed_domains() (http.cookiejar.DefaultCookiePolicy 的方法): DefaultCookiePolicy 物件.
                                                             (line   65)
* ALT_DIGITS (於 locale 模組中):         locale --- 國際化服務.
                                                             (line  331)
* alt() (於 curses.ascii 模組中):        curses ascii --- ASCII 字元的工具程式.
                                                             (line  221)
* altsep (於 os 模組中):                 Miscellaneous System Information.
                                                             (line  125)
* altzone (於 time 模組中):              Timezone Constants. (line    6)
* ALWAYS_EQ (於 test.support 模組中):    test support --- Python 測試套件的工具.
                                                             (line  173)
* ALWAYS_TYPED_ACTIONS (optparse.Option 的屬性): Adding new actions.
                                                             (line   43)
* AmbiguousOptionError:                  例外<16>.           (line   25)
* AMPER (於 token 模組中):               token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  102)
* AMPEREQUAL (於 token 模組中):          token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  190)
* Anchor (importlib.resources 中的類別): importlib resources -- Package resource reading opening and access.
                                                             (line   45)
* anchor (pathlib.PurePath 的屬性):      方法與屬性.         (line   64)
* And (ast 中的類別):                    運算式<2>.          (line   84)
* and_() (於 operator 模組中):           operator --- 標準運算子替代函式.
                                                             (line   75)
* android_ver() (於 platform 模組中):    Android Platform.   (line    6)
* AnnAssign (ast 中的類別):              陳述式.             (line   39)
* Annotated (於 typing 模組中):          特別型式.           (line  241)
* annotated（註釋）;assignment（賦值）:  Annotated assignment statements.
                                                             (line    6)
* annotation (inspect.Parameter 的屬性): Introspecting callables with the Signature object.
                                                             (line  223)
* ANNOTATION (symtable.SymbolTableType 的屬性): 檢查符號表.  (line   26)
* annotation（註記）;type annotation（型別註記）；type hint（型別提示）: 型別註釋的型別 --- 泛型別名 Generic Alias 、聯合 Union.
                                                             (line    6)
* annotation（註釋）:                    術語表.             (line   36)
* anonymous（匿名）;function （函式）:   Lambdas.            (line    6)
* answer_challenge() (於 multiprocessing.connection 模組中): Listeners and Clients.
                                                             (line   25)
* anticipate_failure() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  448)
* Any (於 typing 模組中):                特別型別.           (line    8)
* ANY (於 unittest.mock 模組中):         ANY.                (line    6)
* ANY_CONTIGUOUS (inspect.BufferFlags 的屬性): Buffer flags. (line   29)
* AnyStr (於 typing 模組中):             特別型別.           (line   20)
* api_version (於 sys 模組中):           sys --- 系統特定的參數與函式.
                                                             (line 1968)
* apilevel (於 sqlite3 模組中):          Module constants.   (line   60)
* apop() (poplib.POP3 的方法):           POP3 物件.          (line   42)
* APPDATA:                               PEP 370 Per-user site-packages Directory.
                                                             (line   26)
* append_history_file() (於 readline 模組中): History file.  (line   20)
* append() (array.array 的方法):         array --- 高效率的數值型陣列.
                                                             (line  111)
* append() (collections.deque 的方法):   deque 物件.         (line   29)
* append() (email.header.Header 的方法): email header：國際化標頭.
                                                             (line   96)
* append() (imaplib.IMAP4 的方法):       IMAP4 物件.         (line   33)
* append() (xml.etree.ElementTree.Element 的方法): Element 物件.
                                                             (line   87)
* append()（序列方法）:                  Mutable Sequence Types.
                                                             (line   16)
* appendChild() (xml.dom.Node 的方法):   Node Objects.       (line  115)
* appendleft() (collections.deque 的方法): deque 物件.       (line   33)
* AppleFrameworkLoader (importlib.machinery 中的類別): importlib machinery -- Importers and path hooks.
                                                             (line  440)
* application_uri() (於 wsgiref.util 模組中): wsgiref util -- WSGI 環境工具.
                                                             (line   28)
* apply_async() (multiprocessing.pool.Pool 的方法): Process Pools.
                                                             (line   74)
* apply_defaults() (inspect.BoundArguments 的方法): Introspecting callables with the Signature object.
                                                             (line  367)
* apply() (multiprocessing.pool.Pool 的方法): Process Pools. (line   66)
* APRIL (於 calendar 模組中):            calendar --- 日曆相關函式.
                                                             (line  365)
* architecture() (於 platform 模組中):   跨平台.             (line    6)
* archive (zipimport.zipimporter 的屬性): zipimporter 物件.  (line   95)
* AREGTYPE (於 tarfile 模組中):          tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  267)
* aRepr (於 reprlib 模組中):             reprlib --- repr 的替代實作.
                                                             (line   43)
* arg (ast 中的類別):                    函式和類別定義.     (line   63)
* args (BaseException 的屬性):           基底類別 base classes.
                                                             (line   15)
* args (functools.partial 的屬性):       partial 物件.       (line   14)
* args (inspect.BoundArguments 的屬性):  Introspecting callables with the Signature object.
                                                             (line  353)
* args (pdb command):                    Debugger Commands.  (line  263)
* args (subprocess.CompletedProcess 的屬性): Using the subprocess Module.
                                                             (line  105)
* args (subprocess.Popen 的屬性):        Popen Objects.      (line  101)
* args (typing.ParamSpec 的屬性):        Building generic types and type aliases.
                                                             (line  407)
* args_from_interpreter_flags() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  315)
* argtypes (ctypes._FuncPtr 的屬性):     Foreign functions.  (line   36)
* argument（引數）:                      術語表.             (line   49)
* argument（引數）;call semantics（呼叫語意）: Slicings.     (line   38)
* argument（引數）;function definition（函式定義）: 函式定義.
                                                             (line   65)
* argument（引數）;與 parameter（參數）的差異: How can I pass optional or keyword parameters from one function to another?.
                                                             (line   17)
* ArgumentDefaultsHelpFormatter (argparse 中的類別): formatter_class.
                                                             (line   10)
* ArgumentError:                         Exceptions<3>.      (line    6)
* ArgumentError <1>:                     Foreign functions.  (line   84)
* ArgumentParser (argparse 中的類別):    ArgumentParser 物件.
                                                             (line    6)
* arguments (ast 中的類別):              函式和類別定義.     (line   46)
* arguments (inspect.BoundArguments 的屬性): Introspecting callables with the Signature object.
                                                             (line  334)
* ArgumentTypeError:                     Exceptions<3>.      (line   14)
* argv (in module sys):                  PyConfig.           (line  127)
* argv (於 sys 模組中):                  sys --- 系統特定的參數與函式.
                                                             (line   68)
* argv（sys 模組中）:                    Process-wide parameters.
                                                             (line  216)
* arithmetic;conversion:                 Arithmetic conversions.
                                                             (line    6)
* arithmetic（算術）:                    數值型別 --- int、float、complex.
                                                             (line   21)
* ArithmeticError:                       基底類別 base classes.
                                                             (line   61)
* array (array 中的類別):                array --- 高效率的數值型陣列.
                                                             (line   81)
* Array (ctypes 中的類別):               Arrays and pointers.
                                                             (line    6)
* Array() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  212)
* ARRAY() (於 ctypes 模組中):            Arrays and pointers.
                                                             (line   31)
* Array() (於 multiprocessing 模組中):   共享的 ctypes 物件. (line   42)
* Array() (於 multiprocessing.sharedctypes 模組中): multiprocessing sharedctypes 模組.
                                                             (line   51)
* arrays（陣列）:                        array --- 高效率的數值型陣列.
                                                             (line    6)
* arraysize (sqlite3.Cursor 的屬性):     Cursor 物件.        (line  170)
* AS pattern, OR pattern, capture pattern, wildcard pattern: Patterns.
                                                             (line    6)
* as_bytes() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  105)
* as_bytes() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  105)
* as_completed() (於 asyncio 模組中):    Waiting Primitives. (line   59)
* as_completed() (於 concurrent.futures 模組中): 模組函式.   (line   36)
* as_file() (於 importlib.resources 模組中): importlib resources -- Package resource reading opening and access.
                                                             (line   73)
* as_integer_ratio() (decimal.Decimal 的方法): Decimal objects.
                                                             (line  121)
* as_integer_ratio() (float 的方法):     浮點數的附加 methods.
                                                             (line    9)
* as_integer_ratio() (fractions.Fraction 的方法): fractions --- 有理數.
                                                             (line  121)
* as_integer_ratio() (int 的方法):       整數型別的附加 methods.
                                                             (line  148)
* as_posix() (pathlib.PurePath 的方法):  方法與屬性.         (line  168)
* as_string() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line   61)
* as_string() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line   60)
* as_tuple() (decimal.Decimal 的方法):   Decimal objects.    (line  135)
* as_uri() (pathlib.Path 的方法):        Parsing and generating URIs.
                                                             (line   42)
* as;except clause（例外子句）:          except clause.      (line   30)
* as;import statement（引入陳述式）:     import 陳述式.      (line   39)
* as;match statement（匹配陳述式）:      The match statement.
                                                             (line    6)
* as;with statement（with 陳述式）:      The with statement. (line    6)
* ASCII:                                 Notation.           (line   32)
* ASCII <1>:                             Literals.           (line    8)
* ASCII (於 re 模組中):                  旗標.               (line   16)
* ascii_letters (於 string 模組中):      字串常數.           (line    8)
* ascii_lowercase (於 string 模組中):    字串常數.           (line   13)
* ascii_uppercase (於 string 模組中):    字串常數.           (line   18)
* ascii() (於 curses.ascii 模組中):      curses ascii --- ASCII 字元的工具程式.
                                                             (line  212)
* asctime() (於 time 模組中):            函式<4>.            (line    6)
* asdict() (於 dataclasses 模組中):      模組內容<8>.        (line  329)
* asend() (agen 的方法):                 Asynchronous generator-iterator methods.
                                                             (line   28)
* asin() (於 cmath 模組中):              三角函數.           (line   11)
* asin() (於 math 模組中):               Trigonometric functions.
                                                             (line   11)
* asinh() (於 cmath 模組中):             雙曲函數.           (line   11)
* asinh() (於 math 模組中):              Hyperbolic functions.
                                                             (line   13)
* askcolor() (於 tkinter.colorchooser 模組中): tkinter colorchooser --- 顏色選擇對話框.
                                                             (line   16)
* askdirectory() (於 tkinter.filedialog 模組中): Native Load/Save Dialogs.
                                                             (line   54)
* askfloat() (於 tkinter.simpledialog 模組中): tkinter simpledialog --- 標準 Tkinter 輸入對話框.
                                                             (line   14)
* askinteger() (於 tkinter.simpledialog 模組中): tkinter simpledialog --- 標準 Tkinter 輸入對話框.
                                                             (line   14)
* askokcancel() (於 tkinter.messagebox 模組中): tkinter messagebox --- Tkinter 訊息提示.
                                                             (line  101)
* askopenfile() (於 tkinter.filedialog 模組中): Native Load/Save Dialogs.
                                                             (line   31)
* askopenfilename() (於 tkinter.filedialog 模組中): Native Load/Save Dialogs.
                                                             (line   42)
* askopenfilenames() (於 tkinter.filedialog 模組中): Native Load/Save Dialogs.
                                                             (line   42)
* askopenfiles() (於 tkinter.filedialog 模組中): Native Load/Save Dialogs.
                                                             (line   31)
* askquestion() (於 tkinter.messagebox 模組中): tkinter messagebox --- Tkinter 訊息提示.
                                                             (line   95)
* askretrycancel() (於 tkinter.messagebox 模組中): tkinter messagebox --- Tkinter 訊息提示.
                                                             (line  107)
* asksaveasfile() (於 tkinter.filedialog 模組中): Native Load/Save Dialogs.
                                                             (line   37)
* asksaveasfilename() (於 tkinter.filedialog 模組中): Native Load/Save Dialogs.
                                                             (line   49)
* askstring() (於 tkinter.simpledialog 模組中): tkinter simpledialog --- 標準 Tkinter 輸入對話框.
                                                             (line   14)
* askyesno() (於 tkinter.messagebox 模組中): tkinter messagebox --- Tkinter 訊息提示.
                                                             (line  113)
* askyesnocancel() (於 tkinter.messagebox 模組中): tkinter messagebox --- Tkinter 訊息提示.
                                                             (line  119)
* Assert (ast 中的類別):                 陳述式.             (line  121)
* assert_any_await() (unittest.mock.AsyncMock 的方法): Mock 類別.
                                                             (line  760)
* assert_any_call() (unittest.mock.Mock 的方法): Mock 類別.  (line  131)
* assert_awaited_once_with() (unittest.mock.AsyncMock 的方法): Mock 類別.
                                                             (line  744)
* assert_awaited_once() (unittest.mock.AsyncMock 的方法): Mock 類別.
                                                             (line  711)
* assert_awaited_with() (unittest.mock.AsyncMock 的方法): Mock 類別.
                                                             (line  727)
* assert_awaited() (unittest.mock.AsyncMock 的方法): Mock 類別.
                                                             (line  692)
* assert_called_once_with() (unittest.mock.Mock 的方法): Mock 類別.
                                                             (line  117)
* assert_called_once() (unittest.mock.Mock 的方法): Mock 類別.
                                                             (line   89)
* assert_called_with() (unittest.mock.Mock 的方法): Mock 類別.
                                                             (line  107)
* assert_called() (unittest.mock.Mock 的方法): Mock 類別.    (line   78)
* assert_has_awaits() (unittest.mock.AsyncMock 的方法): Mock 類別.
                                                             (line  776)
* assert_has_calls() (unittest.mock.Mock 的方法): Mock 類別. (line  146)
* assert_never() (於 typing 模組中):     函式與裝飾器.       (line   44)
* assert_not_awaited() (unittest.mock.AsyncMock 的方法): Mock 類別.
                                                             (line  802)
* assert_not_called() (unittest.mock.Mock 的方法): Mock 類別.
                                                             (line  167)
* assert_python_failure() (於 test.support.script_helper 模組中): test support script_helper --- 用於 Python 執行測試的工具.
                                                             (line   54)
* assert_python_ok() (於 test.support.script_helper 模組中): test support script_helper --- 用於 Python 執行測試的工具.
                                                             (line   38)
* assert_type() (於 typing 模組中):      函式與裝飾器.       (line   15)
* assertAlmostEqual() (unittest.TestCase 的方法): Test cases.
                                                             (line  504)
* assertCountEqual() (unittest.TestCase 的方法): Test cases. (line  558)
* assertDictEqual() (unittest.TestCase 的方法): Test cases.  (line  667)
* assertEqual() (unittest.TestCase 的方法): Test cases.      (line  177)
* assertFalse() (unittest.TestCase 的方法): Test cases.      (line  201)
* assertGreater() (unittest.TestCase 的方法): Test cases.    (line  528)
* assertGreaterEqual() (unittest.TestCase 的方法): Test cases.
                                                             (line  528)
* assertIn() (unittest.TestCase 的方法): Test cases.         (line  228)
* assertInBytecode() (test.support.bytecode_helper.BytecodeTestCase 的方法): test support bytecode_helper --- 用於測試位元組碼能正確產生的支援工具.
                                                             (line   22)
* AssertionError:                        實體例外.           (line    8)
* assertIs() (unittest.TestCase 的方法): Test cases.         (line  213)
* assertIsInstance() (unittest.TestCase 的方法): Test cases. (line  235)
* assertIsNone() (unittest.TestCase 的方法): Test cases.     (line  221)
* assertIsNot() (unittest.TestCase 的方法): Test cases.      (line  213)
* assertIsNotNone() (unittest.TestCase 的方法): Test cases.  (line  221)
* assertLess() (unittest.TestCase 的方法): Test cases.       (line  528)
* assertLessEqual() (unittest.TestCase 的方法): Test cases.  (line  528)
* assertListEqual() (unittest.TestCase 的方法): Test cases.  (line  644)
* assertLogs() (unittest.TestCase 的方法): Test cases.       (line  404)
* assertMultiLineEqual() (unittest.TestCase 的方法): Test cases.
                                                             (line  619)
* assertNoLogs() (unittest.TestCase 的方法): Test cases.     (line  448)
* assertNotAlmostEqual() (unittest.TestCase 的方法): Test cases.
                                                             (line  504)
* assertNotEqual() (unittest.TestCase 的方法): Test cases.   (line  196)
* assertNotIn() (unittest.TestCase 的方法): Test cases.      (line  228)
* assertNotInBytecode() (test.support.bytecode_helper.BytecodeTestCase 的方法): test support bytecode_helper --- 用於測試位元組碼能正確產生的支援工具.
                                                             (line   28)
* assertNotIsInstance() (unittest.TestCase 的方法): Test cases.
                                                             (line  235)
* assertNotRegex() (unittest.TestCase 的方法): Test cases.   (line  541)
* assertRaises() (unittest.TestCase 的方法): Test cases.     (line  275)
* assertRaisesRegex() (unittest.TestCase 的方法): Test cases.
                                                             (line  315)
* assertRegex() (unittest.TestCase 的方法): Test cases.      (line  541)
* assertSequenceEqual() (unittest.TestCase 的方法): Test cases.
                                                             (line  629)
* assertSetEqual() (unittest.TestCase 的方法): Test cases.   (line  655)
* assertTrue() (unittest.TestCase 的方法): Test cases.       (line  201)
* assertTupleEqual() (unittest.TestCase 的方法): Test cases. (line  644)
* assertWarns() (unittest.TestCase 的方法): Test cases.      (line  340)
* assertWarnsRegex() (unittest.TestCase 的方法): Test cases. (line  380)
* Assign (ast 中的類別):                 陳述式.             (line    6)
* assignment expression（賦值運算式）:   Boolean operations. (line   38)
* assignment（賦值）;statement（陳述式）: Mutable sequences. (line    6)
* assignment（賦值）;statement（陳述式） <1>: Assignment statements.
                                                             (line    6)
* AST (ast 中的類別):                    節點 Node 類別.     (line    6)
* ast 命令列選項; -a:                    命令列用法<3>.      (line   28)
* ast 命令列選項; -h:                    命令列用法<3>.      (line   14)
* ast 命令列選項; -help:                 命令列用法<3>.      (line   14)
* ast 命令列選項; -i:                    命令列用法<3>.      (line   32)
* ast 命令列選項; -include-attributes:   命令列用法<3>.      (line   28)
* ast 命令列選項; -indent:               命令列用法<3>.      (line   32)
* ast 命令列選項; -m:                    命令列用法<3>.      (line   18)
* ast 命令列選項; -mode:                 命令列用法<3>.      (line   18)
* ast 命令列選項; -no-type-comments:     命令列用法<3>.      (line   24)
* astimezone() (datetime.datetime 的方法): datetime 物件.    (line  473)
* astuple() (於 dataclasses 模組中):     模組內容<8>.        (line  361)
* async for;於 comprehensions（綜合運算）: Displays for lists sets and dictionaries.
                                                             (line   14)
* AsyncContextDecorator (contextlib 中的類別): Utilities.    (line  463)
* AsyncContextManager (typing 中的類別): contextlib ABC 的別名.
                                                             (line   24)
* asynccontextmanager() (於 contextlib 模組中): Utilities.   (line   94)
* AsyncExitStack (contextlib 中的類別):  Utilities.          (line  621)
* AsyncFor (ast 中的類別):               async 和 await.     (line   34)
* AsyncFunctionDef (ast 中的類別):       async 和 await.     (line    6)
* AsyncGenerator (collections.abc 中的類別): Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line  163)
* AsyncGenerator (typing 中的類別):      Aliases to asynchronous ABCs in collections abc.
                                                             (line   21)
* AsyncGeneratorType (於 types 模組中):  Standard Interpreter Types.
                                                             (line   48)
* asynchronous context manager（非同步情境管理器）: 術語表.  (line   77)
* asynchronous generator iterator（非同步產生器疊代器）: 術語表.
                                                             (line   97)
* asynchronous generator（非同步產生器）: 術語表.            (line   83)
* asynchronous generator（非同步產生器）;asynchronous iterator（非同步疊代器）: Asynchronous generator functions.
                                                             (line    6)
* asynchronous generator（非同步產生器）;function （函式）: Asynchronous generator functions.
                                                             (line    6)
* asynchronous iterable（非同步可疊代物件）: 術語表.         (line  112)
* asynchronous iterator（非同步疊代器）: 術語表.             (line  118)
* asyncio.subprocess.DEVNULL (內建變數): 常數<6>.            (line   23)
* asyncio.subprocess.PIPE (內建變數):    常數<6>.            (line    6)
* asyncio.subprocess.Process (內建類別): Interacting with Subprocesses.
                                                             (line   11)
* asyncio.subprocess.STDOUT (內建變數):  常數<6>.            (line   17)
* AsyncIterable (collections.abc 中的類別): Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line  149)
* AsyncIterable (typing 中的類別):       Aliases to asynchronous ABCs in collections abc.
                                                             (line   38)
* AsyncIterator (collections.abc 中的類別): Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line  156)
* AsyncIterator (typing 中的類別):       Aliases to asynchronous ABCs in collections abc.
                                                             (line   48)
* AsyncMock (unittest.mock 中的類別):    Mock 類別.          (line  628)
* AsyncResult (multiprocessing.pool 中的類別): Process Pools.
                                                             (line  194)
* asyncSetUp() (unittest.IsolatedAsyncioTestCase 的方法): Test cases.
                                                             (line  859)
* asyncTearDown() (unittest.IsolatedAsyncioTestCase 的方法): Test cases.
                                                             (line  868)
* AsyncWith (ast 中的類別):              async 和 await.     (line   34)
* AT (於 token 模組中):                  token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  222)
* at_eof() (asyncio.StreamReader 的方法): StreamReader.      (line   79)
* atan() (於 cmath 模組中):              三角函數.           (line   15)
* atan() (於 math 模組中):               Trigonometric functions.
                                                             (line   16)
* atan2() (於 math 模組中):              Trigonometric functions.
                                                             (line   21)
* atanh() (於 cmath 模組中):             雙曲函數.           (line   16)
* atanh() (於 math 模組中):              Hyperbolic functions.
                                                             (line   17)
* ATEQUAL (於 token 模組中):             token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  226)
* atexit (weakref.finalize 的屬性):      weakref --- 弱參照. (line  258)
* athrow() (agen 的方法):                Asynchronous generator-iterator methods.
                                                             (line   43)
* atof() (於 locale 模組中):             locale --- 國際化服務.
                                                             (line  497)
* atoi() (於 locale 模組中):             locale --- 國際化服務.
                                                             (line  503)
* atom:                                  Atoms.              (line    6)
* attach_loop() (asyncio.AbstractChildWatcher 的方法): Process Watchers.
                                                             (line   63)
* attach_mock() (unittest.mock.Mock 的方法): Mock 類別.      (line  214)
* attach() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  166)
* attempted (doctest.TestResults 的屬性): TestResults objects.
                                                             (line   12)
* AttlistDeclHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line  246)
* attrgetter() (於 operator 模組中):     operator --- 標準運算子替代函式.
                                                             (line  218)
* attrib (xml.etree.ElementTree.Element 的屬性): Element 物件.
                                                             (line   45)
* Attribute (ast 中的類別):              運算式<2>.          (line  164)
* attribute（屬性）:                     標準型別階層.       (line   13)
* attribute（屬性） <1>:                 術語表.             (line  126)
* attribute（屬性）;assignment（賦值）:  Assignment statements.
                                                             (line    6)
* attribute（屬性）;assignment（賦值） <1>: Assignment statements.
                                                             (line   76)
* attribute（屬性）;deletion（刪除）:    del 陳述式<2>.      (line   20)
* attribute（屬性）;reference（參照）:   Attribute references.
                                                             (line    6)
* AttributeError:                        實體例外.           (line   12)
* attributes (xml.dom.Node 的屬性):      Node Objects.       (line   26)
* AttributesImpl (xml.sax.xmlreader 中的類別): xml sax xmlreader --- XML 剖析器的介面.
                                                             (line   69)
* AttributesNSImpl (xml.sax.xmlreader 中的類別): xml sax xmlreader --- XML 剖析器的介面.
                                                             (line   80)
* attroff() (curses.window 的方法):      Window Objects.     (line   53)
* attron() (curses.window 的方法):       Window Objects.     (line   58)
* attrset() (curses.window 的方法):      Window Objects.     (line   63)
* audit events（稽核事件）:              除錯與效能分析.     (line   12)
* audit() (於 sys 模組中):               sys --- 系統特定的參數與函式.
                                                             (line   89)
* auditing:                              sys --- 系統特定的參數與函式.
                                                             (line   91)
* AugAssign (ast 中的類別):              陳述式.             (line   90)
* augmented（增強）;assignment（賦值）:  Augmented assignment statements.
                                                             (line    6)
* AUGUST (於 calendar 模組中):           calendar --- 日曆相關函式.
                                                             (line  365)
* auth() (ftplib.FTP_TLS 的方法):        FTP_TLS 物件.       (line   83)
* auth() (smtplib.SMTP 的方法):          SMTP 物件.          (line  141)
* authenticate() (imaplib.IMAP4 的方法): IMAP4 物件.         (line   37)
* AuthenticationError:                   Process 與例外.     (line  240)
* authenticators() (netrc.netrc 的方法): netrc 物件.         (line    8)
* authkey (multiprocessing.Process 的屬性): Process 與例外.  (line  141)
* auto (enum 中的類別):                  通用項目與裝飾器.   (line    6)
* autocommit (sqlite3.Connection 的屬性): Connection 物件.   (line  728)
* autorange() (timeit.Timer 的方法):     Python 介面.        (line   76)
* available_timezones() (於 zoneinfo 模組中): 函式<2>.       (line    6)
* avoids_symlink_attacks (shutil.rmtree 的屬性): Directory and files operations.
                                                             (line  317)
* Await (ast 中的類別):                  async 和 await.     (line   14)
* await_args (unittest.mock.AsyncMock 的屬性): Mock 類別.    (line  830)
* await_args_list (unittest.mock.AsyncMock 的屬性): Mock 類別.
                                                             (line  847)
* await_count (unittest.mock.AsyncMock 的屬性): Mock 類別.   (line  815)
* await;於 comprehensions（綜合運算）:   Displays for lists sets and dictionaries.
                                                             (line   45)
* Awaitable (collections.abc 中的類別):  Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line  109)
* Awaitable (typing 中的類別):           Aliases to asynchronous ABCs in collections abc.
                                                             (line   58)
* awaitable（可等待物件）:               術語表.             (line  137)
* b';bytes literal（位元組常數）:        String and Bytes literals.
                                                             (line   46)
* b";bytes literal（位元組常數）:        String and Bytes literals.
                                                             (line   46)
* b16decode() (於 base64 模組中):        base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  138)
* b16encode() (於 base64 模組中):        base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  133)
* b2a_base64() (於 binascii 模組中):     binascii --- 在二進位制和 ASCII 之間轉換.
                                                             (line   61)
* b2a_hex() (於 binascii 模組中):        binascii --- 在二進位制和 ASCII 之間轉換.
                                                             (line  114)
* b2a_qp() (於 binascii 模組中):         binascii --- 在二進位制和 ASCII 之間轉換.
                                                             (line   77)
* b2a_uu() (於 binascii 模組中):         binascii --- 在二進位制和 ASCII 之間轉換.
                                                             (line   31)
* b32decode() (於 base64 模組中):        base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   98)
* b32encode() (於 base64 模組中):        base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   93)
* b32hexdecode() (於 base64 模組中):     base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  122)
* b32hexencode() (於 base64 模組中):     base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  115)
* b64decode() (於 base64 模組中):        base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   49)
* b64encode() (於 base64 模組中):        base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   35)
* b85decode() (於 base64 模組中):        base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  198)
* b85encode() (於 base64 模組中):        base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  188)
* Babyl (mailbox 中的類別):              Babyl 物件.         (line    6)
* BabylMessage (mailbox 中的類別):       BabylMessage 物件.  (line    6)
* back() (於 turtle 模組中):             Turtle motion.      (line   24)
* backend (於 readline 模組中):          readline --- GNU readline 介面.
                                                             (line   51)
* backslash character（反斜線字元）:     Explicit line joining.
                                                             (line    6)
* backslashreplace_errors() (於 codecs 模組中): Error Handlers.
                                                             (line  161)
* backslashreplace;error handler's name（錯誤處理器名稱）: Error Handlers.
                                                             (line   15)
* backup() (sqlite3.Connection 的方法):  Connection 物件.    (line  526)
* backward() (於 turtle 模組中):         Turtle motion.      (line   24)
* BadGzipFile:                           gzip --- gzip 檔案的支援.
                                                             (line   62)
* BadOptionError:                        例外<16>.           (line   21)
* BadStatusLine:                         http client --- HTTP 協定用戶端.
                                                             (line  177)
* BadZipFile:                            zipfile --- 處理 ZIP 封存檔案.
                                                             (line   24)
* BadZipfile:                            zipfile --- 處理 ZIP 封存檔案.
                                                             (line   30)
* Barrier (asyncio 中的類別):            Barrier.            (line    6)
* Barrier (multiprocessing 中的類別):    Synchronization primitives.
                                                             (line   13)
* Barrier (threading 中的類別):          Barrier Objects.    (line   36)
* Barrier() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  160)
* base_exec_prefix (於 sys 模組中):      sys --- 系統特定的參數與函式.
                                                             (line  118)
* base_prefix (於 sys 模組中):           sys --- 系統特定的參數與函式.
                                                             (line  132)
* base64;encoding（編碼）:               base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line    8)
* BaseCGIHandler (wsgiref.handlers 中的類別): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line   47)
* BaseCookie (http.cookies 中的類別):    http cookies --- HTTP 狀態管理.
                                                             (line   39)
* BaseException:                         基底類別 base classes.
                                                             (line    8)
* BaseExceptionGroup:                    例外群組.           (line   12)
* BaseHandler (urllib.request 中的類別): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  242)
* BaseHandler (wsgiref.handlers 中的類別): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line   77)
* BaseHeader (email.headerregistry 中的類別): email headerregistry：自訂標頭物件.
                                                             (line   37)
* BaseHTTPRequestHandler (http.server 中的類別): http server — HTTP 伺服器.
                                                             (line   51)
* BaseManager (multiprocessing.managers 中的類別): Managers. (line   23)
* basename() (於 os.path 模組中):        os path --- 常見的路徑名操作.
                                                             (line   51)
* BaseProtocol (asyncio 中的類別):       Base Protocols.     (line    6)
* BaseProxy (multiprocessing.managers 中的類別): Proxy Objects.
                                                             (line   92)
* BaseRequestHandler (socketserver 中的類別): Request Handler Objects.
                                                             (line    6)
* BaseRotatingHandler (logging.handlers 中的類別): BaseRotatingHandler.
                                                             (line   12)
* BaseSelector (selectors 中的類別):     Classes<3>.         (line   53)
* BaseServer (socketserver 中的類別):    Server Objects.     (line    6)
* BaseTransport (asyncio 中的類別):      Transports Hierarchy.
                                                             (line    6)
* basicConfig() (於 logging 模組中):     Module-Level Functions.
                                                             (line  204)
* BasicContext (decimal 中的類別):       Context objects.    (line   65)
* BasicInterpolation (configparser 中的類別): Interpolation of values.
                                                             (line   10)
* batched() (於 itertools 模組中):       Itertool 函式.      (line   65)
* baudrate() (於 curses 模組中):         函式<5>.            (line   18)
* bbox() (tkinter.ttk.Treeview 的方法):  ttk Treeview.       (line    8)
* BDADDR_ANY (於 socket 模組中):         常數<7>.            (line  294)
* BDADDR_LOCAL (於 socket 模組中):       常數<7>.            (line  294)
* Bdb (bdb 中的類別):                    bdb --- 偵錯器框架. (line  128)
* BdbQuit:                               bdb --- 偵錯器框架. (line   15)
* BDFL:                                  術語表.             (line  143)
* beep() (於 curses 模組中):             函式<5>.            (line   26)
* Beep() (於 winsound 模組中):           winsound --- Windows 的聲音播放介面.
                                                             (line   12)
* BEFORE_ASYNC_WITH (opcode):            Python Bytecode Instructions.
                                                             (line  353)
* BEFORE_WITH (opcode):                  Python Bytecode Instructions.
                                                             (line  505)
* begin_fill() (於 turtle 模組中):       Filling.            (line   16)
* begin_poly() (於 turtle 模組中):       Special Turtle methods.
                                                             (line    6)
* BEL (於 curses.ascii 模組中):          curses ascii --- ASCII 字元的工具程式.
                                                             (line   40)
* BELOW_NORMAL_PRIORITY_CLASS (於 subprocess 模組中): Windows Constants.
                                                             (line   75)
* below() (curses.panel.Panel 的方法):   Panel Objects.      (line   17)
* benchmarking（基準測試）:              函式<4>.            (line  190)
* benchmarking（基準測試） <1>:          函式<4>.            (line  216)
* benchmarking（基準測試） <2>:          函式<4>.            (line  516)
* betavariate() (於 random 模組中):      實數分布.           (line   27)
* bgcolor() (於 turtle 模組中):          Window control.     (line    6)
* bgpic() (於 turtle 模組中):            Window control.     (line   21)
* bidirectional() (於 unicodedata 模組中): unicodedata --- Unicode 資料庫.
                                                             (line   54)
* bigaddrspacetest() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  563)
* BigEndianStructure (ctypes 中的類別):  Structured data types.
                                                             (line   22)
* BigEndianUnion (ctypes 中的類別):      Structured data types.
                                                             (line   10)
* bigmemtest() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  547)
* Binary (xmlrpc.client 中的類別):       Binary Objects.     (line    6)
* binary file（二進位檔案）:             術語表.             (line  148)
* binary literal（二進位常數）:          Numeric literals.   (line    6)
* binary semaphores（二進位號誌）:       _thread --- 低階執行緒 API.
                                                             (line    6)
* BINARY_OP (opcode):                    Python Bytecode Instructions.
                                                             (line  234)
* BINARY_SLICE (opcode):                 Python Bytecode Instructions.
                                                             (line  270)
* BINARY_SUBSCR (opcode):                Python Bytecode Instructions.
                                                             (line  245)
* binary（二進位）;arithmetic;operation（操作）: Binary arithmetic operations.
                                                             (line    6)
* binary（二進位）;bitwise（位元）;operation（操作）: Binary bitwise operations.
                                                             (line    6)
* binary（二進位）;literals（字面值）:   數值型別 --- int、float、complex.
                                                             (line   15)
* binaryfunc (C type):                   Slot Type typedefs. (line  112)
* BinaryIO (typing 中的類別):            ABCs for working with IO.
                                                             (line    6)
* bind (widgets):                        Bindings and Events.
                                                             (line    6)
* bind_partial() (inspect.Signature 的方法): Introspecting callables with the Signature object.
                                                             (line  129)
* bind_port() (於 test.support.socket_helper 模組中): test support socket_helper --- 用於 socket 測試的工具.
                                                             (line   37)
* bind_textdomain_codeset() (於 locale 模組中): Access to message catalogs.
                                                             (line   16)
* bind_unix_socket() (於 test.support.socket_helper 模組中): test support socket_helper --- 用於 socket 測試的工具.
                                                             (line   54)
* bind() (inspect.Signature 的方法):     Introspecting callables with the Signature object.
                                                             (line  122)
* bind() (socket.socket 的方法):         Socket 物件.        (line   30)
* binding（繫結）;name（名稱）:          Binding of names.   (line    6)
* binding（繫結）;name（名稱） <1>:      Assignment statements.
                                                             (line    6)
* bindtextdomain() (於 gettext 模組中):  GNU gettext API.    (line   14)
* bindtextdomain() (於 locale 模組中):   Access to message catalogs.
                                                             (line   14)
* binomialvariate() (於 random 模組中):  離散分布.           (line    8)
* BinOp (ast 中的類別):                  運算式<2>.          (line   40)
* bisect_left() (於 bisect 模組中):      bisect --- 陣列二分演算法 Array bisection algorithm.
                                                             (line   20)
* bisect_right() (於 bisect 模組中):     bisect --- 陣列二分演算法 Array bisection algorithm.
                                                             (line   40)
* bisect() (於 bisect 模組中):           bisect --- 陣列二分演算法 Array bisection algorithm.
                                                             (line   40)
* bit_count() (int 的方法):              整數型別的附加 methods.
                                                             (line   33)
* bit_length() (int 的方法):             整數型別的附加 methods.
                                                             (line    9)
* BitAnd (ast 中的類別):                 運算式<2>.          (line   52)
* BitOr (ast 中的類別):                  運算式<2>.          (line   52)
* bits_per_digit (sys.int_info 的屬性):  sys --- 系統特定的參數與函式.
                                                             (line 1105)
* bitwise（位元）;and:                   Binary bitwise operations.
                                                             (line   12)
* bitwise（位元）;operations（操作）:    整數型別的位元運算. (line    6)
* bitwise（位元）;or:                    Binary bitwise operations.
                                                             (line   20)
* bitwise（位元）;xor:                   Binary bitwise operations.
                                                             (line   16)
* BitXor (ast 中的類別):                 運算式<2>.          (line   52)
* bk() (於 turtle 模組中):               Turtle motion.      (line   24)
* bkgd() (curses.window 的方法):         Window Objects.     (line   68)
* bkgdset() (curses.window 的方法):      Window Objects.     (line   80)
* blake2b, blake2s:                      BLAKE2.             (line    6)
* blake2b.MAX_DIGEST_SIZE (於 hashlib 模組中): 常數<5>.      (line   24)
* blake2b.MAX_KEY_SIZE (於 hashlib 模組中): 常數<5>.         (line   18)
* blake2b.PERSON_SIZE (於 hashlib 模組中): 常數<5>.          (line   12)
* blake2b.SALT_SIZE (於 hashlib 模組中): 常數<5>.            (line    6)
* blake2b() (於 hashlib 模組中):         建立雜湊物件.       (line    8)
* blake2s.MAX_DIGEST_SIZE (於 hashlib 模組中): 常數<5>.      (line   26)
* blake2s.MAX_KEY_SIZE (於 hashlib 模組中): 常數<5>.         (line   20)
* blake2s.PERSON_SIZE (於 hashlib 模組中): 常數<5>.          (line   14)
* blake2s.SALT_SIZE (於 hashlib 模組中): 常數<5>.            (line    8)
* blake2s() (於 hashlib 模組中):         建立雜湊物件.       (line   13)
* blank line（空白列）:                  Blank lines.        (line    6)
* BLKTYPE (於 tarfile 模組中):           tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  284)
* Blob (sqlite3 中的類別):               Blob 物件.          (line    6)
* blobopen() (sqlite3.Connection 的方法): Connection 物件.   (line   34)
* block:                                 Structure of a program.
                                                             (line    6)
* block_on_close (socketserver.ThreadingMixIn 的屬性): Server Creation Notes.
                                                             (line   45)
* block_size (hmac.HMAC 的屬性):         hmac --- 基於金鑰雜湊的訊息驗證.
                                                             (line   82)
* blocked_domains() (http.cookiejar.DefaultCookiePolicy 的方法): DefaultCookiePolicy 物件.
                                                             (line   52)
* BlockingIOError:                       作業系統例外.       (line    8)
* BlockingIOError <1>:                   高階模組介面.       (line   62)
* blocksize (http.client.HTTPConnection 的屬性): HTTPConnection 物件.
                                                             (line  155)
* BNF:                                   Notation.           (line    6)
* BNF <1>:                               運算式.             (line    6)
* body_encode() (email.charset.Charset 的方法): email charset：表示字元集合.
                                                             (line  133)
* body_encoding (email.charset.Charset 的屬性): email charset：表示字元集合.
                                                             (line   65)
* body_line_iterator() (於 email.iterators 模組中): email iterators：疊代器.
                                                             (line   14)
* body() (tkinter.simpledialog.Dialog 的方法): tkinter simpledialog --- 標準 Tkinter 輸入對話框.
                                                             (line   25)
* BOLD (於 tkinter.font 模組中):         tkinter font --- Tkinter 字型包裝器.
                                                             (line   15)
* BOM (於 codecs 模組中):                codecs --- 編解碼器註冊表和基底類別.
                                                             (line  249)
* BOM_BE (於 codecs 模組中):             codecs --- 編解碼器註冊表和基底類別.
                                                             (line  249)
* BOM_LE (於 codecs 模組中):             codecs --- 編解碼器註冊表和基底類別.
                                                             (line  249)
* BOM_UTF16 (於 codecs 模組中):          codecs --- 編解碼器註冊表和基底類別.
                                                             (line  249)
* BOM_UTF16_BE (於 codecs 模組中):       codecs --- 編解碼器註冊表和基底類別.
                                                             (line  249)
* BOM_UTF16_LE (於 codecs 模組中):       codecs --- 編解碼器註冊表和基底類別.
                                                             (line  249)
* BOM_UTF32 (於 codecs 模組中):          codecs --- 編解碼器註冊表和基底類別.
                                                             (line  249)
* BOM_UTF32_BE (於 codecs 模組中):       codecs --- 編解碼器註冊表和基底類別.
                                                             (line  249)
* BOM_UTF32_LE (於 codecs 模組中):       codecs --- 編解碼器註冊表和基底類別.
                                                             (line  249)
* BOM_UTF8 (於 codecs 模組中):           codecs --- 編解碼器註冊表和基底類別.
                                                             (line  249)
* bool (內建類別):                       內建函式.           (line  122)
* BOOLEAN_STATES (configparser.ConfigParser 的屬性): Customizing Parser Behaviour.
                                                             (line  246)
* Boolean（布林）;operation（操作）:     Boolean operations. (line    6)
* Boolean（布林）;operations（操作）:    真值檢測.           (line    6)
* Boolean（布林）;operations（操作） <1>: Boolean（布林）運算 --- and or not.
                                                             (line    6)
* Boolean（布林）;values:                Boolean 型別 - bool.
                                                             (line    9)
* Boolean（布林值）;type（型別）:        內建函式.           (line  133)
* BoolOp (ast 中的類別):                 運算式<2>.          (line   68)
* bootstrap() (於 ensurepip 模組中):     模組 API.           (line   12)
* border() (curses.window 的方法):       Window Objects.     (line   91)
* borrowed reference（借用參照）:        術語表.             (line  159)
* bottom_panel() (於 curses.panel 模組中): 函式<6>.          (line    8)
* bottom() (curses.panel.Panel 的方法):  Panel Objects.      (line   21)
* BoundArguments (inspect 中的類別):     Introspecting callables with the Signature object.
                                                             (line  328)
* BoundaryError:                         email errors：例外和缺陷類別.
                                                             (line   38)
* BoundedSemaphore (asyncio 中的類別):   BoundedSemaphore.   (line    6)
* BoundedSemaphore (multiprocessing 中的類別): Synchronization primitives.
                                                             (line   19)
* BoundedSemaphore (threading 中的類別): Semaphore Objects.  (line   73)
* BoundedSemaphore() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  167)
* box() (curses.window 的方法):          Window Objects.     (line  129)
* bpbynumber (bdb.Breakpoint 的屬性):    bdb --- 偵錯器框架. (line  109)
* bpformat() (bdb.Breakpoint 的方法):    bdb --- 偵錯器框架. (line   55)
* bplist (bdb.Breakpoint 的屬性):        bdb --- 偵錯器框架. (line  114)
* bpprint() (bdb.Breakpoint 的方法):     bdb --- 偵錯器框架. (line   74)
* BRANCH (monitoring event):             事件.               (line    8)
* Break (ast 中的類別):                  流程控制.           (line   93)
* break (pdb command):                   Debugger Commands.  (line   97)
* break_anywhere() (bdb.Bdb 的方法):     bdb --- 偵錯器框架. (line  261)
* break_here() (bdb.Bdb 的方法):         bdb --- 偵錯器框架. (line  252)
* break_long_words (textwrap.TextWrapper 的屬性): textwrap --- 文字包裝與填充.
                                                             (line  249)
* break_on_hyphens (textwrap.TextWrapper 的屬性): textwrap --- 文字包裝與填充.
                                                             (line  259)
* Breakpoint (bdb 中的類別):             bdb --- 偵錯器框架. (line   21)
* breakpointhook() (於 sys 模組中):      sys --- 系統特定的參數與函式.
                                                             (line  237)
* breakpoints（中斷點）:                 Help menu Shell and Editor.
                                                             (line   29)
* broadcast_address (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line   91)
* broadcast_address (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  311)
* broken (asyncio.Barrier 的屬性):       Barrier.            (line  103)
* broken (threading.Barrier 的屬性):     Barrier Objects.    (line  101)
* BrokenBarrierError:                    Barrier Objects.    (line  106)
* BrokenBarrierError <1>:                Barrier.            (line  108)
* BrokenExecutor:                        例外類別.           (line   17)
* BrokenPipeError:                       作業系統例外.       (line   35)
* BrokenProcessPool:                     例外類別.           (line   37)
* BrokenThreadPool:                      例外類別.           (line   30)
* BROWSER:                               webbrowser --- 方便的網頁瀏覽器控制器.
                                                             (line   20)
* BROWSER <1>:                           webbrowser --- 方便的網頁瀏覽器控制器.
                                                             (line   34)
* BROWSER <2>:                           webbrowser --- 方便的網頁瀏覽器控制器.
                                                             (line  121)
* BS (於 curses.ascii 模組中):           curses ascii --- ASCII 字元的工具程式.
                                                             (line   43)
* BsdDbShelf (shelve 中的類別):          Restrictions.       (line   60)
* buf (multiprocessing.shared_memory.SharedMemory 的屬性): multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取.
                                                             (line  101)
* Buffer (collections.abc 中的類別):     Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line  173)
* buffer (io.TextIOBase 的屬性):         文字 I/O<2>.        (line   30)
* buffer (unittest.TestResult 的屬性):   Loading and running tests.
                                                             (line  293)
* buffer interface（緩衝介面）;(請見緩衝協定): 疊代器協議.   (line   73)
* buffer object（緩衝物件）;(請見緩衝協定): 疊代器協議.      (line   72)
* buffer protocol（緩衝區協定）;binary sequence types（二進位序列型別）: printf-style String Formatting.
                                                             (line  192)
* buffer protocol（緩衝區協定）;str（內建類別）: Text Sequence Type --- str.
                                                             (line   61)
* buffer protocol（緩衝協定）:           疊代器協議.         (line   73)
* buffer size, I/O（緩衝區大小、I/O）:   內建函式.           (line 1294)
* buffer_info() (array.array 的方法):    array --- 高效率的數值型陣列.
                                                             (line  115)
* buffer_size (xml.parsers.expat.xmlparser 的屬性): XMLParser 物件<2>.
                                                             (line  120)
* buffer_text (xml.parsers.expat.xmlparser 的屬性): XMLParser 物件<2>.
                                                             (line  127)
* buffer_updated() (asyncio.BufferedProtocol 的方法): Buffered Streaming Protocols.
                                                             (line   33)
* buffer_used (xml.parsers.expat.xmlparser 的屬性): XMLParser 物件<2>.
                                                             (line  138)
* BufferedIOBase (io 中的類別):          I/O 基礎類別.       (line  196)
* BufferedProtocol (asyncio 中的類別):   Base Protocols.     (line   15)
* BufferedRandom (io 中的類別):          Buffered Streams.   (line  138)
* BufferedReader (io 中的類別):          Buffered Streams.   (line   56)
* BufferedRWPair (io 中的類別):          Buffered Streams.   (line  153)
* BufferedWriter (io 中的類別):          Buffered Streams.   (line   97)
* BufferError:                           基底類別 base classes.
                                                             (line   67)
* BufferFlags (inspect 中的類別):        Buffer flags.       (line    6)
* BufferingFormatter (logging 中的類別): Formatter Objects.  (line  131)
* BufferingHandler (logging.handlers 中的類別): MemoryHandler.
                                                             (line   19)
* BufferTooShort:                        Process 與例外.     (line  232)
* BUILD_CONST_KEY_MAP (opcode):          Python Bytecode Instructions.
                                                             (line  683)
* BUILD_LIST (opcode):                   Python Bytecode Instructions.
                                                             (line  666)
* BUILD_MAP (opcode):                    Python Bytecode Instructions.
                                                             (line  674)
* build_opener() (於 urllib.request 模組中): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  114)
* BUILD_SET (opcode):                    Python Bytecode Instructions.
                                                             (line  670)
* BUILD_SLICE (opcode):                  Python Bytecode Instructions.
                                                             (line 1113)
* BUILD_STRING (opcode):                 Python Bytecode Instructions.
                                                             (line  692)
* BUILD_TUPLE (opcode):                  Python Bytecode Instructions.
                                                             (line  653)
* built-in function; __import__():       內建函式.           (line 1979)
* built-in function; abs():              內建函式.           (line   43)
* built-in function; aiter():            內建函式.           (line   48)
* built-in function; all():              內建函式.           (line   58)
* built-in function; anext():            內建函式.           (line   69)
* built-in function; any():              內建函式.           (line   84)
* built-in function; ascii():            內建函式.           (line   95)
* built-in function; bin():              內建函式.           (line  102)
* built-in function; breakpoint():       內建函式.           (line  135)
* built-in function; callable():         內建函式.           (line  210)
* built-in function; chr():              內建函式.           (line  221)
* built-in function; classmethod():      內建函式.           (line  230)
* built-in function; compile():          內建函式.           (line  263)
* built-in function; delattr():          內建函式.           (line  395)
* built-in function; dir():              內建函式.           (line  415)
* built-in function; divmod():           內建函式.           (line  465)
* built-in function; enumerate():        內建函式.           (line  474)
* built-in function; eval():             內建函式.           (line  496)
* built-in function; exec():             內建函式.           (line  565)
* built-in function; filter():           內建函式.           (line  627)
* built-in function; format():           內建函式.           (line  700)
* built-in function; getattr():          內建函式.           (line  729)
* built-in function; globals():          內建函式.           (line  743)
* built-in function; hasattr():          內建函式.           (line  748)
* built-in function; hash():             內建函式.           (line  754)
* built-in function; help():             內建函式.           (line  763)
* built-in function; hex():              內建函式.           (line  781)
* built-in function; id():               內建函式.           (line  810)
* built-in function; input():            內建函式.           (line  820)
* built-in function; isinstance():       內建函式.           (line  905)
* built-in function; issubclass():       內建函式.           (line  919)
* built-in function; iter():             內建函式.           (line  930)
* built-in function; len():              內建函式.           (line  955)
* built-in function; locals():           內建函式.           (line  972)
* built-in function; map():              內建函式.           (line 1027)
* built-in function; max():              內建函式.           (line 1036)
* built-in function; min():              內建函式.           (line 1066)
* built-in function; multiprocessing.Manager(): Managers.    (line   12)
* built-in function; next():             內建函式.           (line 1091)
* built-in function; oct():              內建函式.           (line 1107)
* built-in function; open():             內建函式.           (line 1130)
* built-in function; ord():              內建函式.           (line 1337)
* built-in function; pow():              內建函式.           (line 1343)
* built-in function; print():            內建函式.           (line 1380)
* built-in function; property.deleter(): 內建函式.           (line 1451)
* built-in function; property.getter():  內建函式.           (line 1447)
* built-in function; property.setter():  內建函式.           (line 1449)
* built-in function; repr():             內建函式.           (line 1500)
* built-in function; reversed():         內建函式.           (line 1523)
* built-in function; round():            內建函式.           (line 1530)
* built-in function; setattr():          內建函式.           (line 1568)
* built-in function; sorted():           內建函式.           (line 1617)
* built-in function; staticmethod():     內建函式.           (line 1652)
* built-in function; sum():              內建函式.           (line 1705)
* built-in function; vars():             內建函式.           (line 1856)
* built-in function; zip():              內建函式.           (line 1882)
* built-in function（內建函式）;__import__: 引入模組<2>.     (line   30)
* built-in function（內建函式）;abs:     Emulating numeric types.
                                                             (line  113)
* built-in function（內建函式）;abs <1>: 數字協定.           (line   91)
* built-in function（內建函式）;bytes（位元組）: Basic customization.
                                                             (line  147)
* built-in function（內建函式）;call（呼叫）: Calls.         (line  140)
* built-in function（內建函式）;chr:     Immutable sequences.
                                                             (line   15)
* built-in function（內建函式）;classmethod: 實作函式與方法. (line  197)
* built-in function（內建函式）;compile（編譯）: global 陳述式.
                                                             (line   28)
* built-in function（內建函式）;compile（編譯） <1>: Code Objects.
                                                             (line    6)
* built-in function（內建函式）;compile（編譯） <2>: Standard Interpreter Types.
                                                             (line   57)
* built-in function（內建函式）;compile（編譯） <3>: 引入模組<2>.
                                                             (line  126)
* built-in function（內建函式）;complex（複數）: Emulating numeric types.
                                                             (line  120)
* built-in function（內建函式）;complex（複數） <1>: 數值型別 --- int、float、complex.
                                                             (line   21)
* built-in function（內建函式）;divmod:  Emulating numeric types.
                                                             (line   26)
* built-in function（內建函式）;divmod <1>: Emulating numeric types.
                                                             (line   56)
* built-in function（內建函式）;divmod <2>: 數字協定.        (line   64)
* built-in function（內建函式）;eval:    global 陳述式.      (line   28)
* built-in function（內建函式）;eval <1>: 運算式輸入.        (line    6)
* built-in function（內建函式）;eval <2>: Code Objects.      (line   17)
* built-in function（內建函式）;eval <3>: 函式<3>.           (line   87)
* built-in function（內建函式）;eval <4>: PrettyPrinter 物件.
                                                             (line   68)
* built-in function（內建函式）;exec:    global 陳述式.      (line   28)
* built-in function（內建函式）;exec <1>: 內建函式.          (line  565)
* built-in function（內建函式）;exec <2>: Code Objects.      (line   17)
* built-in function（內建函式）;float:   Emulating numeric types.
                                                             (line  120)
* built-in function（內建函式）;float <1>: 數值型別 --- int、float、complex.
                                                             (line   21)
* built-in function（內建函式）;float <2>: 數字協定.         (line  246)
* built-in function（內建函式）;hash（雜湊）: Basic customization.
                                                             (line  229)
* built-in function（內建函式）;hash（雜湊） <1>: Immutable Sequence Types.
                                                             (line    6)
* built-in function（內建函式）;hash（雜湊） <2>: PyTypeObject Slots.
                                                             (line  316)
* built-in function（內建函式）;help（幫助）: 作業系統介面.  (line   18)
* built-in function（內建函式）;id:      Objects values and types.
                                                             (line   11)
* built-in function（內建函式）;int:     Emulating numeric types.
                                                             (line  120)
* built-in function（內建函式）;int <1>: 數值型別 --- int、float、complex.
                                                             (line   21)
* built-in function（內建函式）;int <2>: 數字協定.           (line  239)
* built-in function（內建函式）;len:     Sequences.          (line    6)
* built-in function（內建函式）;len <1>: Set types.          (line    6)
* built-in function（內建函式）;len <2>: Mappings.           (line    6)
* built-in function（內建函式）;len <3>: Emulating container types.
                                                             (line   40)
* built-in function（內建函式）;len <4>: Common Sequence Operations.
                                                             (line   21)
* built-in function（內建函式）;len <5>: Mapping Types --- dict.
                                                             (line    6)
* built-in function（內建函式）;len <6>: 對映協定.           (line   17)
* built-in function（內建函式）;len <7>: List（串列）物件.   (line   39)
* built-in function（內建函式）;len <8>: 字典物件.           (line  222)
* built-in function（內建函式）;len <9>: 集合物件.           (line   97)
* built-in function（內建函式）;max:     Common Sequence Operations.
                                                             (line   21)
* built-in function（內建函式）;min:     Common Sequence Operations.
                                                             (line   21)
* built-in function（內建函式）;open:    讀寫檔案.           (line    6)
* built-in function（內建函式）;open <1>: I/O objects also known as file objects.
                                                             (line    6)
* built-in function（內建函式）;ord:     Immutable sequences.
                                                             (line   15)
* built-in function（內建函式）;pow:     Emulating numeric types.
                                                             (line   26)
* built-in function（內建函式）;pow <1>: Emulating numeric types.
                                                             (line   26)
* built-in function（內建函式）;pow <2>: Emulating numeric types.
                                                             (line   56)
* built-in function（內建函式）;pow <3>: Emulating numeric types.
                                                             (line   67)
* built-in function（內建函式）;pow <4>: 數字協定.           (line   72)
* built-in function（內建函式）;pow <5>: 數字協定.           (line  193)
* built-in function（內建函式）;print:   Basic customization.
                                                             (line  151)
* built-in function（內建函式）;range:   The for statement.  (line   37)
* built-in function（內建函式）;repr:    Expression statements.
                                                             (line   17)
* built-in function（內建函式）;repr <1>: Finalization and De-allocation.
                                                             (line   90)
* built-in function（內建函式）;repr <2>: PyTypeObject Slots.
                                                             (line  254)
* built-in function（內建函式）;round:   Emulating numeric types.
                                                             (line  143)
* built-in function（內建函式）;slice（切片）: Slice objects.
                                                             (line    6)
* built-in function（內建函式）;slice（切片） <1>: Python Bytecode Instructions.
                                                             (line 1115)
* built-in function（內建函式）;staticmethod: 實作函式與方法.
                                                             (line  204)
* built-in function（內建函式）;tuple（元組）: List（串列）物件.
                                                             (line  148)
* built-in function（內建函式）;type（型別）: Objects values and types.
                                                             (line   11)
* built-in function（內建函式）;type（型別） <1>: Metaclasses.
                                                             (line    6)
* built-in function（內建函式）;type（型別） <2>: Type Objects.
                                                             (line    6)
* built-in function（内建函式）;len:     序列協定.           (line   16)
* built-in function（内建函式）;tuple（元组）: 序列協定.     (line  115)
* built-in method（內建方法）;call（呼叫）: Calls.           (line  140)
* built-in（內建）;method（方法）:       Built-in methods.   (line    6)
* built-in（內建）;type（型別）:         內建型別.           (line    8)
* builtin_module_names (於 sys 模組中):  sys --- 系統特定的參數與函式.
                                                             (line  153)
* BuiltinFunctionType (於 types 模組中): Standard Interpreter Types.
                                                             (line   80)
* BuiltinImporter (importlib.machinery 中的類別): importlib machinery -- Importers and path hooks.
                                                             (line   64)
* BuiltinMethodType (於 types 模組中):   Standard Interpreter Types.
                                                             (line   80)
* bulit-in function（內建函式）;ascii:   物件協定.           (line  337)
* bulit-in function（內建函式）;bytes（位元組）: 物件協定.   (line  358)
* bulit-in function（內建函式）;hash（雜湊）: 物件協定.      (line  407)
* bulit-in function（內建函式）;len:     物件協定.           (line  453)
* bulit-in function（內建函式）;repr:    物件協定.           (line  326)
* bulit-in function（內建函式）;type（型別）: 物件協定.      (line  435)
* busy_retry() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  195)
* BUTTON_ALT (於 curses 模組中):         Constants.          (line  629)
* BUTTON_CTRL (於 curses 模組中):        Constants.          (line  626)
* BUTTON_SHIFT (於 curses 模組中):       Constants.          (line  623)
* buttonbox() (tkinter.simpledialog.Dialog 的方法): tkinter simpledialog --- 標準 Tkinter 輸入對話框.
                                                             (line   30)
* BUTTONn_CLICKED (於 curses 模組中):    Constants.          (line  614)
* BUTTONn_DOUBLE_CLICKED (於 curses 模組中): Constants.      (line  617)
* BUTTONn_PRESSED (於 curses 模組中):    Constants.          (line  608)
* BUTTONn_RELEASED (於 curses 模組中):   Constants.          (line  611)
* BUTTONn_TRIPLE_CLICKED (於 curses 模組中): Constants.      (line  620)
* bye() (於 turtle 模組中):              Methods specific to Screen not inherited from TurtleScreen.
                                                             (line    6)
* byref() (於 ctypes 模組中):            Utility functions.  (line   18)
* byte（位元組）:                        Immutable sequences.
                                                             (line   39)
* bytearray (內建類別):                  Bytearray Objects.  (line    9)
* bytearray（位元組陣列）:               Mutable sequences.  (line   25)
* bytearray（位元組陣列）;formatting（格式化）: printf-style Bytes Formatting.
                                                             (line    6)
* bytearray（位元組陣列）;interpolation（插值）: printf-style Bytes Formatting.
                                                             (line    6)
* bytearray（位元組陣列）;methods（方法）: Bytes and Bytearray Operations.
                                                             (line    6)
* Bytecode (dis 中的類別):               Bytecode analysis.  (line   12)
* BYTECODE_SUFFIXES (於 importlib.machinery 模組中): importlib machinery -- Importers and path hooks.
                                                             (line   38)
* Bytecode.codeobj (於 dis 模組中):      Bytecode analysis.  (line   49)
* Bytecode.first_line (於 dis 模組中):   Bytecode analysis.  (line   53)
* bytecode（位元組碼）:                  Code objects.       (line    6)
* bytecode（位元組碼） <1>:              術語表.             (line  189)
* BytecodeTestCase (test.support.bytecode_helper 中的類別): test support bytecode_helper --- 用於測試位元組碼能正確產生的支援工具.
                                                             (line   13)
* byteorder (於 sys 模組中):             sys --- 系統特定的參數與函式.
                                                             (line  146)
* bytes (uuid.UUID 的屬性):              uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line   79)
* bytes (內建類別):                      Bytes Objects.      (line   12)
* bytes literal（位元組常數）:           Literals.           (line    8)
* bytes_le (uuid.UUID 的屬性):           uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line   84)
* bytes_warning (sys.flags 的屬性):      sys --- 系統特定的參數與函式.
                                                             (line  552)
* bytes-like object（類位元組串物件）:   術語表.             (line  173)
* bytes（位元組）:                       Immutable sequences.
                                                             (line   39)
* bytes（位元組）;formatting（格式化）:  printf-style Bytes Formatting.
                                                             (line    6)
* bytes（位元組）;interpolation（插值）: printf-style Bytes Formatting.
                                                             (line    6)
* bytes（位元組）;methods（方法）:       Bytes and Bytearray Operations.
                                                             (line    6)
* bytes（位元組）;str（內建類別）:       Text Sequence Type --- str.
                                                             (line   61)
* BytesFeedParser (email.parser 中的類別): FeedParser API.   (line   28)
* BytesGenerator (email.generator 中的類別): email generator：產生 MIME 文件.
                                                             (line   42)
* BytesHeaderParser (email.parser 中的類別): Parser API.     (line   67)
* BytesIO (io 中的類別):                 Buffered Streams.   (line    9)
* BytesParser (email.parser 中的類別):   Parser API.         (line   18)
* ByteString (collections.abc 中的類別): Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line   68)
* ByteString (typing 中的類別):          collections abc 中容器 ABC 的別名.
                                                             (line   13)
* byteswap() (array.array 的方法):       array --- 高效率的數值型陣列.
                                                             (line  130)
* BytesWarning:                          警告.               (line   72)
* BZ2Compressor (bz2 中的類別):          Incremental de compression.
                                                             (line    6)
* BZ2Decompressor (bz2 中的類別):        Incremental de compression.
                                                             (line   33)
* BZ2File (bz2 中的類別):                De compression of files.
                                                             (line   39)
* C:                                     String and Bytes literals.
                                                             (line   74)
* c_bool (ctypes 中的類別):              Fundamental data types<2>.
                                                             (line  207)
* c_byte (ctypes 中的類別):              Fundamental data types<2>.
                                                             (line   45)
* c_char (ctypes 中的類別):              Fundamental data types<2>.
                                                             (line   51)
* c_char_p (ctypes 中的類別):            Fundamental data types<2>.
                                                             (line   58)
* C_CONTIGUOUS (inspect.BufferFlags 的屬性): Buffer flags.   (line   25)
* c_contiguous (memoryview 的屬性):      Memory Views.       (line  472)
* c_double (ctypes 中的類別):            Fundamental data types<2>.
                                                             (line   65)
* c_float (ctypes 中的類別):             Fundamental data types<2>.
                                                             (line   76)
* c_int (ctypes 中的類別):               Fundamental data types<2>.
                                                             (line   81)
* c_int16 (ctypes 中的類別):             Fundamental data types<2>.
                                                             (line   93)
* c_int32 (ctypes 中的類別):             Fundamental data types<2>.
                                                             (line   98)
* c_int64 (ctypes 中的類別):             Fundamental data types<2>.
                                                             (line  103)
* c_int8 (ctypes 中的類別):              Fundamental data types<2>.
                                                             (line   88)
* c_long (ctypes 中的類別):              Fundamental data types<2>.
                                                             (line  108)
* c_longdouble (ctypes 中的類別):        Fundamental data types<2>.
                                                             (line   70)
* c_longlong (ctypes 中的類別):          Fundamental data types<2>.
                                                             (line  113)
* C_RAISE (monitoring event):            事件.               (line   16)
* C_RETURN (monitoring event):           事件.               (line   21)
* c_short (ctypes 中的類別):             Fundamental data types<2>.
                                                             (line  119)
* c_size_t (ctypes 中的類別):            Fundamental data types<2>.
                                                             (line  124)
* c_ssize_t (ctypes 中的類別):           Fundamental data types<2>.
                                                             (line  128)
* c_time_t (ctypes 中的類別):            Fundamental data types<2>.
                                                             (line  134)
* c_ubyte (ctypes 中的類別):             Fundamental data types<2>.
                                                             (line  140)
* c_uint (ctypes 中的類別):              Fundamental data types<2>.
                                                             (line  146)
* c_uint16 (ctypes 中的類別):            Fundamental data types<2>.
                                                             (line  158)
* c_uint32 (ctypes 中的類別):            Fundamental data types<2>.
                                                             (line  163)
* c_uint64 (ctypes 中的類別):            Fundamental data types<2>.
                                                             (line  168)
* c_uint8 (ctypes 中的類別):             Fundamental data types<2>.
                                                             (line  153)
* c_ulong (ctypes 中的類別):             Fundamental data types<2>.
                                                             (line  173)
* c_ulonglong (ctypes 中的類別):         Fundamental data types<2>.
                                                             (line  178)
* c_ushort (ctypes 中的類別):            Fundamental data types<2>.
                                                             (line  184)
* c_void_p (ctypes 中的類別):            Fundamental data types<2>.
                                                             (line  189)
* c_wchar (ctypes 中的類別):             Fundamental data types<2>.
                                                             (line  194)
* c_wchar_p (ctypes 中的類別):           Fundamental data types<2>.
                                                             (line  201)
* C-contiguous（C 連續的）:              shape strides suboffsets.
                                                             (line   26)
* C-contiguous（C 連續的） <1>:          術語表.             (line  256)
* C;language（語言）:                    標準型別階層.       (line    6)
* C;language（語言） <1>:                numbers Real float. (line    6)
* C;language（語言） <2>:                Built-in functions. (line    6)
* C;language（語言） <3>:                Comparisons.        (line    6)
* C;language（語言） <4>:                數值型別 --- int、float、complex.
                                                             (line    6)
* C;structures（結構）:                  struct --- 將位元組直譯為打包起來的二進位資料.
                                                             (line    8)
* C14NWriterTarget (xml.etree.ElementTree 中的類別): TreeBuilder 物件.
                                                             (line   94)
* CACHE (opcode):                        Python Bytecode Instructions.
                                                             (line  169)
* cache_from_source() (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line   21)
* cache() (於 functools 模組中):         functools --- 可呼叫物件上的高階函式與操作.
                                                             (line   15)
* cached (importlib.machinery.ModuleSpec 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  416)
* cached_property() (於 functools 模組中): functools --- 可呼叫物件上的高階函式與操作.
                                                             (line   45)
* CacheFTPHandler (urllib.request 中的類別): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  399)
* calcobjsize() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  431)
* calcsize() (於 struct 模組中):         函式與例外.         (line   55)
* calcvobjsize() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  437)
* Calendar (calendar 中的類別):          calendar --- 日曆相關函式.
                                                             (line   22)
* calendar 命令列選項; -c:               命令列用法.         (line  111)
* calendar 命令列選項; -css:             命令列用法.         (line  111)
* calendar 命令列選項; -e:               命令列用法.         (line   64)
* calendar 命令列選項; -encoding:        命令列用法.         (line   64)
* calendar 命令列選項; -f:               命令列用法.         (line   73)
* calendar 命令列選項; -first-weekday:   命令列用法.         (line   73)
* calendar 命令列選項; -h:               命令列用法.         (line   56)
* calendar 命令列選項; -help:            命令列用法.         (line   56)
* calendar 命令列選項; -L:               命令列用法.         (line   60)
* calendar 命令列選項; -l:               命令列用法.         (line   96)
* calendar 命令列選項; -lines:           命令列用法.         (line   96)
* calendar 命令列選項; -locale:          命令列用法.         (line   60)
* calendar 命令列選項; -m:               命令列用法.         (line  105)
* calendar 命令列選項; -months:          命令列用法.         (line  105)
* calendar 命令列選項; -s:               命令列用法.         (line  101)
* calendar 命令列選項; -spacing:         命令列用法.         (line  101)
* calendar 命令列選項; -t:               命令列用法.         (line   69)
* calendar 命令列選項; -type:            命令列用法.         (line   69)
* calendar 命令列選項; -w:               命令列用法.         (line   91)
* calendar 命令列選項; -width:           命令列用法.         (line   91)
* calendar 命令列選項; month:            命令列用法.         (line   84)
* calendar 命令列選項; year:             命令列用法.         (line   80)
* calendar() (於 calendar 模組中):       calendar --- 日曆相關函式.
                                                             (line  314)
* Call (ast 中的類別):                   運算式<2>.          (line  118)
* CALL (monitoring event):               事件.               (line   12)
* CALL (opcode):                         Python Bytecode Instructions.
                                                             (line 1007)
* call_args (unittest.mock.Mock 的屬性): Mock 類別.          (line  381)
* call_args_list (unittest.mock.Mock 的屬性): Mock 類別.     (line  421)
* call_at() (asyncio.loop 的方法):       排程延遲的回呼函式. (line   31)
* call_count (unittest.mock.Mock 的屬性): Mock 類別.         (line  281)
* call_exception_handler() (asyncio.loop 的方法): 錯誤處理 API.
                                                             (line   41)
* CALL_FUNCTION_EX (opcode):             Python Bytecode Instructions.
                                                             (line 1059)
* CALL_INTRINSIC_1 (opcode):             Python Bytecode Instructions.
                                                             (line 1263)
* CALL_INTRINSIC_2 (opcode):             Python Bytecode Instructions.
                                                             (line 1324)
* CALL_KW (opcode):                      Python Bytecode Instructions.
                                                             (line 1032)
* call_later() (asyncio.loop 的方法):    排程延遲的回呼函式. (line    9)
* call_list() (unittest.mock.call 的方法): call.             (line   19)
* call_soon_threadsafe() (asyncio.loop 的方法): 排程回呼函式.
                                                             (line   22)
* call_soon() (asyncio.loop 的方法):     排程回呼函式.       (line    6)
* call_tracing() (於 sys 模組中):        sys --- 系統特定的參數與函式.
                                                             (line  162)
* call() (於 operator 模組中):           operator --- 標準運算子替代函式.
                                                             (line  206)
* call() (於 subprocess 模組中):         Older high-level API.
                                                             (line   10)
* call() (於 unittest.mock 模組中):      call.               (line    6)
* call（呼叫）:                          Slicings.           (line   38)
* call（呼叫）;instance（實例）:         Emulating callable objects.
                                                             (line    8)
* Callable (collections.abc 中的類別):   Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line   19)
* Callable (於 typing 模組中):           Aliases to other ABCs in collections abc.
                                                             (line   22)
* callable（可呼叫物件）:                術語表.             (line  202)
* CallableProxyType (於 weakref 模組中): weakref --- 弱參照. (line  278)
* callback (optparse.Option 的屬性):     Option attributes.  (line   68)
* callback_args (optparse.Option 的屬性): Option attributes. (line   74)
* callback_kwargs (optparse.Option 的屬性): Option attributes.
                                                             (line   74)
* callback() (contextlib.ExitStack 的方法): Utilities.       (line  582)
* callback（回呼）:                      術語表.             (line  213)
* callbacks (於 gc 模組中):              gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line  253)
* called (unittest.mock.Mock 的屬性):    Mock 類別.          (line  270)
* CalledProcessError:                    Using the subprocess Module.
                                                             (line  205)
* calloc（C 函式）:                      總覽<2>.            (line   33)
* CAN (於 curses.ascii 模組中):          curses ascii --- ASCII 字元的工具程式.
                                                             (line   97)
* CAN_BCM (於 socket 模組中):            常數<7>.            (line  141)
* can_change_color() (於 curses 模組中): 函式<5>.            (line   30)
* can_fetch() (urllib.robotparser.RobotFileParser 的方法): urllib robotparser --- robots txt 的剖析器.
                                                             (line   32)
* CAN_ISOTP (於 socket 模組中):          常數<7>.            (line  180)
* CAN_J1939 (於 socket 模組中):          常數<7>.            (line  189)
* CAN_RAW_FD_FRAMES (於 socket 模組中):  常數<7>.            (line  156)
* CAN_RAW_JOIN_FILTERS (於 socket 模組中): 常數<7>.          (line  169)
* can_symlink() (於 test.support.os_helper 模組中): test support os_helper --- 用於 os 測試的工具.
                                                             (line   74)
* can_write_eof() (asyncio.StreamWriter 的方法): StreamWriter.
                                                             (line   43)
* can_write_eof() (asyncio.WriteTransport 的方法): Write-only Transports.
                                                             (line   14)
* can_xattr() (於 test.support.os_helper 模組中): test support os_helper --- 用於 os 測試的工具.
                                                             (line   78)
* CANCEL (於 tkinter.messagebox 模組中): tkinter messagebox --- Tkinter 訊息提示.
                                                             (line  135)
* cancel_command() (tkinter.filedialog.FileDialog 的方法): Native Load/Save Dialogs.
                                                             (line   82)
* cancel_dump_traceback_later() (於 faulthandler 模組中): Dumping the tracebacks after a timeout.
                                                             (line   29)
* cancel_join_thread() (multiprocessing.Queue 的方法): Pipes and Queues.
                                                             (line  192)
* cancel() (asyncio.Future 的方法):      Future 物件<2>.     (line  105)
* cancel() (asyncio.Handle 的方法):      回呼處理.           (line   17)
* cancel() (asyncio.Task 的方法):        Task Object.        (line  199)
* cancel() (concurrent.futures.Future 的方法): Future 物件.  (line   14)
* cancel() (sched.scheduler 的方法):     排程器物件.         (line   36)
* cancel() (threading.Timer 的方法):     Timer Objects.      (line   35)
* cancel() (tkinter.dnd.DndHandler 的方法): tkinter dnd --- 拖放支援.
                                                             (line   48)
* cancelled() (asyncio.Future 的方法):   Future 物件<2>.     (line   65)
* cancelled() (asyncio.Handle 的方法):   回呼處理.           (line   21)
* cancelled() (asyncio.Task 的方法):     Task Object.        (line  260)
* cancelled() (concurrent.futures.Future 的方法): Future 物件.
                                                             (line   19)
* CancelledError:                        例外類別.           (line    6)
* CancelledError <1>:                    例外<8>.            (line   17)
* cancelling() (asyncio.Task 的方法):    Task Object.        (line  317)
* CannotSendHeader:                      http client --- HTTP 協定用戶端.
                                                             (line  169)
* CannotSendRequest:                     http client --- HTTP 協定用戶端.
                                                             (line  165)
* canonic() (bdb.Bdb 的方法):            bdb --- 偵錯器框架. (line  148)
* canonical() (decimal.Context 的方法):  Context objects.    (line  257)
* canonical() (decimal.Decimal 的方法):  Decimal objects.    (line  140)
* canonicalize() (於 xml.etree.ElementTree 模組中): 函式<8>. (line    6)
* capa() (poplib.POP3 的方法):           POP3 物件.          (line   24)
* capitalize() (bytearray 的方法):       Bytes and Bytearray Operations.
                                                             (line  469)
* capitalize() (bytes 的方法):           Bytes and Bytearray Operations.
                                                             (line  469)
* capitalize() (str 的方法):             String Methods<2>.  (line   22)
* CapsuleType (types 中的類別):          Standard Interpreter Types.
                                                             (line  335)
* captured_stderr() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  325)
* captured_stdin() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  325)
* captured_stdout() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  325)
* captureWarnings() (於 logging 模組中): Integration with the warnings module.
                                                             (line    9)
* capwords() (於 string 模組中):         輔助函式.           (line    6)
* case block:                            Irrefutable Case Blocks.
                                                             (line    6)
* casefold() (str 的方法):               String Methods<2>.  (line   32)
* cast() (memoryview 的方法):            Memory Views.       (line  272)
* cast() (於 ctypes 模組中):             Utility functions.  (line   32)
* cast() (於 typing 模組中):             函式與裝飾器.       (line    6)
* catch_threading_exception() (於 test.support.threading_helper 模組中): test support threading_helper --- Utilities for threading tests.
                                                             (line   46)
* catch_unraisable_exception() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  593)
* catch_warnings (warnings 中的類別):    Available Context Managers.
                                                             (line    6)
* category() (於 unicodedata 模組中):    unicodedata --- Unicode 資料庫.
                                                             (line   49)
* cbreak() (於 curses 模組中):           函式<5>.            (line   35)
* cbrt() (於 math 模組中):               Power and logarithmic functions.
                                                             (line    6)
* CC:                                    New Improved and Deprecated Modules<4>.
                                                             (line   58)
* ccc() (ftplib.FTP_TLS 的方法):         FTP_TLS 物件.       (line   92)
* cdf() (statistics.NormalDist 的方法):  NormalDist 物件.    (line   73)
* CDLL (ctypes 中的類別):                Loading shared libraries.
                                                             (line    9)
* ceil() (於 math 模組中):               數論與表現函式.     (line    6)
* ceil()（於 math 模組）:                數值型別 --- int、float、complex.
                                                             (line   97)
* CellType (於 types 模組中):            Standard Interpreter Types.
                                                             (line   69)
* center() (bytearray 的方法):           Bytes and Bytearray Operations.
                                                             (line  288)
* center() (bytes 的方法):               Bytes and Bytearray Operations.
                                                             (line  288)
* center() (str 的方法):                 String Methods<2>.  (line   48)
* CERT_NONE (於 ssl 模組中):             常數<8>.            (line   11)
* CERT_OPTIONAL (於 ssl 模組中):         常數<8>.            (line   23)
* CERT_REQUIRED (於 ssl 模組中):         常數<8>.            (line   36)
* cert_store_stats() (ssl.SSLContext 的方法): SSL Contexts.  (line   91)
* cert_time_to_seconds() (於 ssl 模組中): 認證處理.          (line    6)
* CertificateError:                      例外<11>.           (line   85)
* certificates（憑證）:                  SSL Contexts.       (line  765)
* CFLAGS:                                New Improved and Deprecated Modules<4>.
                                                             (line   59)
* CFLAGS <1>:                            Performance options.
                                                             (line   28)
* CFLAGS <2>:                            編譯器旗標.         (line   26)
* CFLAGS <3>:                            編譯器旗標.         (line   28)
* CFLAGS <4>:                            編譯器旗標.         (line   32)
* CFLAGS <5>:                            編譯器旗標.         (line   54)
* CFLAGS <6>:                            Linker flags.       (line   18)
* CFLAGS_NODIST:                         編譯器旗標.         (line   24)
* CFLAGS_NODIST <1>:                     編譯器旗標.         (line   61)
* CFLAGS_NODIST <2>:                     Linker flags.       (line   26)
* cfmakecbreak() (於 tty 模組中):        tty --- 終端機控制函式.
                                                             (line   26)
* cfmakeraw() (於 tty 模組中):           tty --- 終端機控制函式.
                                                             (line   18)
* CFUNCTYPE() (於 ctypes 模組中):        Function prototypes.
                                                             (line   15)
* cget() (tkinter.font.Font 的方法):     tkinter font --- Tkinter 字型包裝器.
                                                             (line   50)
* cgi_directories (http.server.CGIHTTPRequestHandler 的屬性): http server — HTTP 伺服器.
                                                             (line  503)
* CGIHandler (wsgiref.handlers 中的類別): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line   10)
* CGIHTTPRequestHandler (http.server 中的類別): http server — HTTP 伺服器.
                                                             (line  477)
* CGIXMLRPCRequestHandler (xmlrpc.server 中的類別): xmlrpc server --- 基本 XML-RPC 伺服器.
                                                             (line   50)
* chain() (於 itertools 模組中):         Itertool 函式.      (line   98)
* chaining（鏈接）;comparisons（比較）:  Comparisons.        (line   19)
* chaining（鏈結）;comparisons（比較）:  比較運算.           (line    6)
* ChainMap (collections 中的類別):       ChainMap 物件.      (line   15)
* ChainMap (typing 中的類別):            collections 中型別的別名.
                                                             (line   28)
* change_cwd() (於 test.support.os_helper 模組中): test support os_helper --- 用於 os 測試的工具.
                                                             (line   82)
* CHANNEL_BINDING_TYPES (於 ssl 模組中): 常數<8>.            (line  416)
* CHAR_MAX (於 locale 模組中):           locale --- 國際化服務.
                                                             (line  565)
* character（字元）:                     Immutable sequences.
                                                             (line   15)
* character（字元） <1>:                 Subscriptions.      (line   55)
* character（字元） <2>:                 unicodedata --- Unicode 資料庫.
                                                             (line    6)
* CharacterDataHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line  278)
* characters_written (BlockingIOError 的屬性): 作業系統例外. (line   17)
* characters() (xml.sax.handler.ContentHandler 的方法): ContentHandler 物件.
                                                             (line  129)
* Charset (email.charset 中的類別):      email charset：表示字元集合.
                                                             (line   22)
* charset() (gettext.NullTranslations 的方法): The NullTranslations class.
                                                             (line   68)
* chdir() (於 contextlib 模組中):        Utilities.          (line  365)
* chdir() (於 os 模組中):                Files and Directories.
                                                             (line  116)
* check (lzma.LZMADecompressor 的屬性):  Compressing and decompressing data in memory.
                                                             (line  159)
* check__all__() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  672)
* check_call() (於 subprocess 模組中):   Older high-level API.
                                                             (line   43)
* check_disallow_instantiation() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  726)
* CHECK_EG_MATCH (opcode):               Python Bytecode Instructions.
                                                             (line  468)
* CHECK_EXC_MATCH (opcode):              Python Bytecode Instructions.
                                                             (line  460)
* check_free_after_iterating() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  660)
* check_hostname (ssl.SSLContext 的屬性): SSL Contexts.      (line  496)
* check_impl_detail() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  289)
* check_no_resource_warning() (於 test.support.warnings_helper 模組中): test support warnings_helper --- 用於 warnings 測試的工具.
                                                             (line   24)
* check_output() (doctest.OutputChecker 的方法): OutputChecker 物件.
                                                             (line   17)
* check_output() (於 subprocess 模組中): Older high-level API.
                                                             (line   80)
* check_returncode() (subprocess.CompletedProcess 的方法): Using the subprocess Module.
                                                             (line  134)
* check_syntax_error() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  567)
* check_syntax_warning() (於 test.support.warnings_helper 模組中): test support warnings_helper --- 用於 warnings 測試的工具.
                                                             (line   31)
* check_unused_args() (string.Formatter 的方法): 自訂字串格式.
                                                             (line   87)
* check_warnings() (於 test.support.warnings_helper 模組中): test support warnings_helper --- 用於 warnings 測試的工具.
                                                             (line   47)
* check() (imaplib.IMAP4 的方法):        IMAP4 物件.         (line   58)
* check() (於 tabnanny 模組中):          tabnanny --- 偵測不良縮排.
                                                             (line   16)
* checkcache() (於 linecache 模組中):    linecache --- 隨機存取文字列.
                                                             (line   43)
* CHECKED_HASH (py_compile.PycInvalidationMode 的屬性): py_compile — 編譯 Python 來源檔案.
                                                             (line  109)
* checkfuncname() (於 bdb 模組中):       bdb --- 偵錯器框架. (line  453)
* checksizeof() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  443)
* checksum（核對和）;Cyclic Redundancy Check（循環冗餘核對）: zlib --- 相容於 gzip 的壓縮.
                                                             (line   97)
* chflags() (於 os 模組中):              Files and Directories.
                                                             (line  134)
* chgat() (curses.window 的方法):        Window Objects.     (line  135)
* childNodes (xml.dom.Node 的屬性):      Node Objects.       (line   49)
* ChildProcessError:                     作業系統例外.       (line   22)
* children (pyclbr.Class 的屬性):        Class Objects.      (line   35)
* children (pyclbr.Function 的屬性):     函式物件.           (line   34)
* children (tkinter.Tk 的屬性):          Tkinter Modules.    (line   88)
* chksum (tarfile.TarInfo 的屬性):       TarInfo 物件.       (line  137)
* chmod() (pathlib.Path 的方法):         Permissions and ownership.
                                                             (line   36)
* chmod() (於 os 模組中):                Files and Directories.
                                                             (line  175)
* choice() (於 random 模組中):           回傳序列的函式.     (line    6)
* choice() (於 secrets 模組中):          亂數.               (line   14)
* choices (optparse.Option 的屬性):      Option attributes.  (line   63)
* choices() (於 random 模組中):          回傳序列的函式.     (line   11)
* Chooser (tkinter.colorchooser 中的類別): tkinter colorchooser --- 顏色選擇對話框.
                                                             (line   14)
* chown() (於 os 模組中):                Files and Directories.
                                                             (line  243)
* chown() (於 shutil 模組中):            Directory and files operations.
                                                             (line  388)
* chroot() (於 os 模組中):               Files and Directories.
                                                             (line  269)
* CHRTYPE (於 tarfile 模組中):           tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  280)
* cipher() (ssl.SSLSocket 的方法):       SSL Sockets.        (line  215)
* circle() (於 turtle 模組中):           Turtle motion.      (line  211)
* CIRCUMFLEX (於 token 模組中):          token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  154)
* CIRCUMFLEXEQUAL (於 token 模組中):     token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  198)
* Clamped (decimal 中的類別):            Signals.            (line   20)
* Class (pyclbr 中的類別):               Class Objects.      (line    6)
* Class (symtable 中的類別):             檢查符號表.         (line  140)
* CLASS (symtable.SymbolTableType 的屬性): 檢查符號表.       (line   19)
* class instance（類別實例）;attribute（屬性）: Class instances.
                                                             (line    6)
* class instance（類別實例）;attribute（屬性）;assignment（賦值）: Class instances.
                                                             (line   21)
* class instance（類別實例）;call（呼叫）: Calls.            (line  149)
* class object（類別物件）;call（呼叫）: Custom classes.     (line   19)
* class object（類別物件）;call（呼叫） <1>: Custom classes. (line   31)
* class object（類別物件）;call（呼叫） <2>: Calls.          (line  145)
* class variable（類別變數）:            術語表.             (line  223)
* class（類別）:                         術語表.             (line  218)
* class（類別）;attribute（屬性）:       Custom classes.     (line   19)
* class（類別）;attribute（屬性）;assignment（賦值）: Custom classes.
                                                             (line   28)
* class（類別）;body:                    Executing the class body.
                                                             (line    6)
* class（類別）;constructor（建構函式）: Basic customization.
                                                             (line   39)
* class（類別）;definition（定義）:      return 陳述式.      (line    6)
* class（類別）;definition（定義） <1>:  類別定義.           (line    6)
* class（類別）;instance（實例）:        Class instances.    (line    6)
* class（類別）;name（名稱）:            類別定義.           (line    6)
* ClassDef (ast 中的類別):               函式和類別定義.     (line  160)
* ClassMethodDescriptorType (於 types 模組中): Standard Interpreter Types.
                                                             (line  115)
* ClassVar (於 typing 模組中):           特別型式.           (line  148)
* clause（子句）:                        複合陳述式.         (line   18)
* CLD_CONTINUED (於 os 模組中):          行程管理.           (line 1041)
* CLD_DUMPED (於 os 模組中):             行程管理.           (line 1041)
* CLD_EXITED (於 os 模組中):             行程管理.           (line 1041)
* CLD_KILLED (於 os 模組中):             行程管理.           (line 1041)
* CLD_STOPPED (於 os 模組中):            行程管理.           (line 1041)
* CLD_TRAPPED (於 os 模組中):            行程管理.           (line 1041)
* clean() (mailbox.Maildir 的方法):      Mailbox 物件<2>.    (line   86)
* cleandoc() (於 inspect 模組中):        取得原始碼.         (line   71)
* CleanImport (test.support.import_helper 中的類別): test support import_helper --- 用於 import 測試的工具.
                                                             (line   85)
* cleanup functions（清理函式）:         行程控制.           (line   33)
* CLEANUP_THROW (opcode):                Python Bytecode Instructions.
                                                             (line  343)
* cleanup() (tempfile.TemporaryDirectory 的方法): tempfile --- 生成臨時檔案和目錄.
                                                             (line  171)
* clear (pdb command):                   Debugger Commands.  (line  126)
* Clear Breakpoint:                      Help menu Shell and Editor.
                                                             (line   30)
* clear_all_breaks() (bdb.Bdb 的方法):   bdb --- 偵錯器框架. (line  367)
* clear_all_file_breaks() (bdb.Bdb 的方法): bdb --- 偵錯器框架.
                                                             (line  362)
* clear_bpbynumber() (bdb.Bdb 的方法):   bdb --- 偵錯器框架. (line  356)
* clear_break() (bdb.Bdb 的方法):        bdb --- 偵錯器框架. (line  351)
* clear_cache() (zoneinfo.ZoneInfo 的類別方法): The ZoneInfo class.
                                                             (line   58)
* clear_cache() (於 filecmp 模組中):     filecmp --- 檔案與目錄比較.
                                                             (line   56)
* clear_content() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  669)
* clear_flags() (decimal.Context 的方法): Context objects.   (line  171)
* clear_frames() (於 traceback 模組中):  traceback --- 列印或取得堆疊回溯 stack traceback.
                                                             (line  197)
* clear_history() (於 readline 模組中):  History list.       (line    8)
* clear_overloads() (於 typing 模組中):  函式與裝飾器.       (line  303)
* clear_session_cookies() (http.cookiejar.CookieJar 的方法): CookieJar 與 FileCookieJar 物件.
                                                             (line   90)
* clear_traces() (於 tracemalloc 模組中): 函式<10>.          (line    6)
* clear_traps() (decimal.Context 的方法): Context objects.   (line  175)
* clear() (array.array 的方法):          array --- 高效率的數值型陣列.
                                                             (line  198)
* clear() (asyncio.Event 的方法):        Event.              (line   56)
* clear() (collections.deque 的方法):    deque 物件.         (line   37)
* clear() (curses.window 的方法):        Window Objects.     (line  151)
* clear() (dbm.gnu.gdbm 的方法):         dbm gnu --- GNU 資料庫管理器.
                                                             (line  114)
* clear() (dbm.ndbm.ndbm 的方法):        dbm ndbm --- 新資料庫管理器.
                                                             (line   70)
* clear() (dict 的方法):                 Mapping Types --- dict.
                                                             (line  135)
* clear() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  665)
* clear() (frame 的方法):                Frame object methods.
                                                             (line    8)
* clear() (frozenset 的方法):            Set Types --- set frozenset.
                                                             (line  213)
* clear() (http.cookiejar.CookieJar 的方法): CookieJar 與 FileCookieJar 物件.
                                                             (line   78)
* clear() (mailbox.Mailbox 的方法):      Mailbox 物件.       (line  212)
* clear() (threading.Event 的方法):      Event Objects.      (line   36)
* clear() (xml.etree.ElementTree.Element 的方法): Element 物件.
                                                             (line   58)
* clear() (於 turtle 模組中):            More drawing control.
                                                             (line   23)
* clear()（序列方法）:                   Mutable Sequence Types.
                                                             (line   16)
* clearcache() (於 linecache 模組中):    linecache --- 隨機存取文字列.
                                                             (line   38)
* clearok() (curses.window 的方法):      Window Objects.     (line  156)
* clearscreen() (於 turtle 模組中):      Window control.     (line   46)
* clearstamp() (於 turtle 模組中):       Turtle motion.      (line  282)
* clearstamps() (於 turtle 模組中):      Turtle motion.      (line  301)
* client_address (http.server.BaseHTTPRequestHandler 的屬性): http server — HTTP 伺服器.
                                                             (line   71)
* client_address (socketserver.BaseRequestHandler 的屬性): Request Handler Objects.
                                                             (line   47)
* Client() (於 multiprocessing.connection 模組中): Listeners and Clients.
                                                             (line   34)
* CLOCK_BOOTTIME (於 time 模組中):       Clock ID Constants. (line    9)
* clock_getres() (於 time 模組中):       函式<4>.            (line   35)
* clock_gettime_ns() (於 time 模組中):   函式<4>.            (line   56)
* clock_gettime() (於 time 模組中):      函式<4>.            (line   44)
* CLOCK_HIGHRES (於 time 模組中):        Clock ID Constants. (line   23)
* CLOCK_MONOTONIC (於 time 模組中):      Clock ID Constants. (line   34)
* CLOCK_MONOTONIC_RAW (於 time 模組中):  Clock ID Constants. (line   43)
* CLOCK_MONOTONIC_RAW_APPROX (於 time 模組中): Clock ID Constants.
                                                             (line   52)
* CLOCK_PROCESS_CPUTIME_ID (於 time 模組中): Clock ID Constants.
                                                             (line   61)
* CLOCK_PROF (於 time 模組中):           Clock ID Constants. (line   69)
* CLOCK_REALTIME (於 time 模組中):       Clock ID Constants. (line  129)
* clock_seq (uuid.UUID 的屬性):          uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  118)
* clock_seq_hi_variant (uuid.UUID 的屬性): uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  106)
* clock_seq_low (uuid.UUID 的屬性):      uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  109)
* clock_settime_ns() (於 time 模組中):   函式<4>.            (line   77)
* clock_settime() (於 time 模組中):      函式<4>.            (line   65)
* CLOCK_TAI (於 time 模組中):            Clock ID Constants. (line   77)
* CLOCK_THREAD_CPUTIME_ID (於 time 模組中): Clock ID Constants.
                                                             (line   89)
* CLOCK_UPTIME (於 time 模組中):         Clock ID Constants. (line   97)
* CLOCK_UPTIME_RAW (於 time 模組中):     Clock ID Constants. (line  107)
* CLOCK_UPTIME_RAW_APPROX (於 time 模組中): Clock ID Constants.
                                                             (line  117)
* CLONE_FILES (於 os 模組中):            行程參數.           (line  627)
* CLONE_FS (於 os 模組中):               行程參數.           (line  627)
* CLONE_NEWCGROUP (於 os 模組中):        行程參數.           (line  627)
* CLONE_NEWIPC (於 os 模組中):           行程參數.           (line  627)
* CLONE_NEWNET (於 os 模組中):           行程參數.           (line  627)
* CLONE_NEWNS (於 os 模組中):            行程參數.           (line  627)
* CLONE_NEWPID (於 os 模組中):           行程參數.           (line  627)
* CLONE_NEWTIME (於 os 模組中):          行程參數.           (line  627)
* CLONE_NEWUSER (於 os 模組中):          行程參數.           (line  627)
* CLONE_NEWUTS (於 os 模組中):           行程參數.           (line  627)
* CLONE_SIGHAND (於 os 模組中):          行程參數.           (line  627)
* CLONE_SYSVSEM (於 os 模組中):          行程參數.           (line  627)
* CLONE_THREAD (於 os 模組中):           行程參數.           (line  627)
* CLONE_VM (於 os 模組中):               行程參數.           (line  627)
* clone() (email.generator.BytesGenerator 的方法): email generator：產生 MIME 文件.
                                                             (line  111)
* clone() (email.generator.Generator 的方法): email generator：產生 MIME 文件.
                                                             (line  207)
* clone() (email.policy.Policy 的方法):  email policy Policy Objects.
                                                             (line  223)
* clone() (於 turtle 模組中):            Special Turtle methods.
                                                             (line   32)
* cloneNode() (xml.dom.Node 的方法):     Node Objects.       (line  147)
* close_clients() (asyncio.Server 的方法): Server 物件.      (line   40)
* close_connection (http.server.BaseHTTPRequestHandler 的屬性): http server — HTTP 伺服器.
                                                             (line   80)
* close() (asyncio.AbstractChildWatcher 的方法): Process Watchers.
                                                             (line   81)
* close() (asyncio.BaseTransport 的方法): Base Transport.    (line    6)
* close() (asyncio.loop 的方法):         啟動和停止迴圈.     (line   40)
* close() (asyncio.Runner 的方法):       Runner context manager.
                                                             (line   47)
* close() (asyncio.Server 的方法):       Server 物件.        (line   30)
* close() (asyncio.StreamWriter 的方法): StreamWriter.       (line   34)
* close() (asyncio.SubprocessTransport 的方法): Subprocess Transports.
                                                             (line   59)
* close() (contextlib.ExitStack 的方法): Utilities.          (line  614)
* close() (coroutine 的方法):            Coroutine Objects.  (line   49)
* close() (dbm.dumb.dumbdbm 的方法):     dbm dumb --- 可攜式 DBM 實作.
                                                             (line   83)
* close() (dbm.gnu.gdbm 的方法):         dbm gnu --- GNU 資料庫管理器.
                                                             (line  110)
* close() (dbm.ndbm.ndbm 的方法):        dbm ndbm --- 新資料庫管理器.
                                                             (line   66)
* close() (email.parser.BytesFeedParser 的方法): FeedParser API.
                                                             (line   65)
* close() (ftplib.FTP 的方法):           FTP 物件.           (line  322)
* close() (generator 的方法):            Generator-iterator methods.
                                                             (line   64)
* close() (html.parser.HTMLParser 的方法): HTMLParser 方法.  (line   14)
* close() (http.client.HTTPConnection 的方法): HTTPConnection 物件.
                                                             (line  151)
* close() (imaplib.IMAP4 的方法):        IMAP4 物件.         (line   62)
* close() (io.IOBase 的方法):            I/O 基礎類別.       (line   42)
* close() (logging.FileHandler 的方法):  FileHandler.        (line   27)
* close() (logging.Handler 的方法):      Handler Objects.    (line   73)
* close() (logging.handlers.MemoryHandler 的方法): MemoryHandler.
                                                             (line   56)
* close() (logging.handlers.NTEventLogHandler 的方法): NTEventLogHandler.
                                                             (line   29)
* close() (logging.handlers.SocketHandler 的方法): SocketHandler.
                                                             (line   20)
* close() (logging.handlers.SysLogHandler 的方法): SysLogHandler.
                                                             (line   46)
* close() (mailbox.Mailbox 的方法):      Mailbox 物件.       (line  269)
* close() (mailbox.Maildir 的方法):      Mailbox 物件<2>.    (line  215)
* close() (mailbox.MH 的方法):           MH 物件.            (line  107)
* close() (mmap.mmap 的方法):            mmap --- 記憶體映射檔案的支援.
                                                             (line  183)
* close() (multiprocessing.connection.Connection 的方法): Connection Objects.
                                                             (line   35)
* close() (multiprocessing.connection.Listener 的方法): Listeners and Clients.
                                                             (line   91)
* close() (multiprocessing.pool.Pool 的方法): Process Pools. (line  171)
* close() (multiprocessing.Process 的方法): Process 與例外.  (line  196)
* close() (multiprocessing.Queue 的方法): Pipes and Queues.  (line  173)
* close() (multiprocessing.shared_memory.SharedMemory 的方法): multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取.
                                                             (line   78)
* close() (multiprocessing.SimpleQueue 的方法): Pipes and Queues.
                                                             (line  219)
* close() (os.scandir 的方法):           Files and Directories.
                                                             (line  862)
* close() (select.devpoll 的方法):       /dev/poll Polling Objects.
                                                             (line   12)
* close() (select.epoll 的方法):         Edge and Level Trigger Polling epoll Objects.
                                                             (line   65)
* close() (select.kqueue 的方法):        Kqueue Objects.     (line    6)
* close() (selectors.BaseSelector 的方法): Classes<3>.       (line  137)
* close() (shelve.Shelf 的方法):         shelve --- Python object persistence.
                                                             (line   77)
* close() (socket.socket 的方法):        Socket 物件.        (line   41)
* close() (sqlite3.Blob 的方法):         Blob 物件.          (line   37)
* close() (sqlite3.Connection 的方法):   Connection 物件.    (line   88)
* close() (sqlite3.Cursor 的方法):       Cursor 物件.        (line  153)
* close() (tarfile.TarFile 的方法):      TarFile 物件.       (line  322)
* close() (urllib.request.BaseHandler 的方法): BaseHandler 物件.
                                                             (line   14)
* close() (wave.Wave_read 的方法):       Wave_read 物件.     (line   12)
* close() (wave.Wave_write 的方法):      Wave_write 物件.    (line   26)
* Close() (winreg.PyHKEY 的方法):        Registry Handle Objects.
                                                             (line   34)
* close() (xml.etree.ElementTree.TreeBuilder 的方法): TreeBuilder 物件.
                                                             (line   28)
* close() (xml.etree.ElementTree.XMLParser 的方法): XMLParser 物件.
                                                             (line   20)
* close() (xml.etree.ElementTree.XMLPullParser 的方法): XMLPullParser 物件.
                                                             (line   41)
* close() (xml.sax.xmlreader.IncrementalParser 的方法): IncrementalParser 物件.
                                                             (line   13)
* close() (zipfile.ZipFile 的方法):      ZipFile 物件.       (line  105)
* close() (於 fileinput 模組中):         fileinput --- 逐列疊代多個輸入串流.
                                                             (line  132)
* close() (於 os 模組中):                File Descriptor Operations.
                                                             (line   21)
* close() (於 socket 模組中):            其他函式<2>.        (line    9)
* close（os 模組中）:                    Sub-interpreter support.
                                                             (line  192)
* closed (http.client.HTTPResponse 的屬性): HTTPResponse 物件.
                                                             (line   75)
* closed (io.IOBase 的屬性):             I/O 基礎類別.       (line   51)
* closed (mmap.mmap 的屬性):             mmap --- 記憶體映射檔案的支援.
                                                             (line  189)
* closed (select.devpoll 的屬性):        /dev/poll Polling Objects.
                                                             (line   18)
* closed (select.epoll 的屬性):          Edge and Level Trigger Polling epoll Objects.
                                                             (line   69)
* closed (select.kqueue 的屬性):         Kqueue Objects.     (line   10)
* CloseKey() (於 winreg 模組中):         函式<12>.           (line    8)
* closelog() (於 syslog 模組中):         syslog --- Unix syslog 函式庫例程.
                                                             (line   78)
* closerange() (於 os 模組中):           File Descriptor Operations.
                                                             (line   32)
* closing() (於 contextlib 模組中):      Utilities.          (line  153)
* clrtobot() (curses.window 的方法):     Window Objects.     (line  161)
* clrtoeol() (curses.window 的方法):     Window Objects.     (line  167)
* Cmd (cmd 中的類別):                    cmd --- 以列為導向的指令直譯器支援.
                                                             (line   15)
* cmd (subprocess.CalledProcessError 的屬性): Using the subprocess Module.
                                                             (line  216)
* cmd (subprocess.TimeoutExpired 的屬性): Using the subprocess Module.
                                                             (line  173)
* cmdloop() (cmd.Cmd 的方法):            Cmd 物件.           (line    8)
* cmdqueue (cmd.Cmd 的屬性):             Cmd 物件.           (line  143)
* cmp_op (於 dis 模組中):                Opcode collections. (line   21)
* cmp_to_key() (於 functools 模組中):    functools --- 可呼叫物件上的高階函式與操作.
                                                             (line  103)
* cmp() (於 filecmp 模組中):             filecmp --- 檔案與目錄比較.
                                                             (line   16)
* cmpfiles() (於 filecmp 模組中):        filecmp --- 檔案與目錄比較.
                                                             (line   36)
* CMSG_LEN() (於 socket 模組中):         其他函式<2>.        (line  307)
* CMSG_SPACE() (於 socket 模組中):       其他函式<2>.        (line  324)
* co_argcount (codeobject 的屬性):       特殊唯讀屬性<2>.    (line   14)
* co_argcount （程式碼物件屬性）:        Code objects.       (line   16)
* CO_ASYNC_GENERATOR (於 inspect 模組中): Code Objects Bit Flags.
                                                             (line   52)
* co_cellvars (codeobject 的屬性):       特殊唯讀屬性<2>.    (line   39)
* co_cellvars （程式碼物件屬性）:        Code objects.       (line   16)
* co_code (codeobject 的屬性):           特殊唯讀屬性<2>.    (line   48)
* co_code （程式碼物件屬性）:            Code objects.       (line   16)
* co_consts (codeobject 的屬性):         特殊唯讀屬性<2>.    (line   52)
* co_consts （程式碼物件屬性）:          Code objects.       (line   16)
* CO_COROUTINE (於 inspect 模組中):      Code Objects Bit Flags.
                                                             (line   35)
* co_filename (codeobject 的屬性):       特殊唯讀屬性<2>.    (line   60)
* co_filename （程式碼物件屬性）:        Code objects.       (line   16)
* co_firstlineno (codeobject 的屬性):    特殊唯讀屬性<2>.    (line   64)
* co_firstlineno （程式碼物件屬性）:     Code objects.       (line   16)
* co_flags (codeobject 的屬性):          特殊唯讀屬性<2>.    (line   78)
* co_flags （程式碼物件屬性）:           Code objects.       (line   16)
* co_freevars (codeobject 的屬性):       特殊唯讀屬性<2>.    (line   44)
* co_freevars （程式碼物件屬性）:        Code objects.       (line   16)
* CO_FUTURE_DIVISION (C var):            The Very High Level Layer.
                                                             (line  368)
* CO_GENERATOR (於 inspect 模組中):      Code Objects Bit Flags.
                                                             (line   30)
* CO_ITERABLE_COROUTINE (於 inspect 模組中): Code Objects Bit Flags.
                                                             (line   43)
* co_kwonlyargcount (codeobject 的屬性): 特殊唯讀屬性<2>.    (line   25)
* co_kwonlyargcount （程式碼物件屬性）:  Code objects.       (line   16)
* co_lines() (codeobject 的方法):        用於程式碼物件的方法.
                                                             (line   43)
* co_lnotab (codeobject 的屬性):         特殊唯讀屬性<2>.    (line   67)
* co_lnotab （程式碼物件屬性）:          Code objects.       (line   16)
* co_name (codeobject 的屬性):           特殊唯讀屬性<2>.    (line    6)
* co_name （程式碼物件屬性）:            Code objects.       (line   16)
* co_names (codeobject 的屬性):          特殊唯讀屬性<2>.    (line   56)
* co_names （程式碼物件屬性）:           Code objects.       (line   16)
* CO_NESTED (於 inspect 模組中):         Code Objects Bit Flags.
                                                             (line   26)
* CO_NEWLOCALS (於 inspect 模組中):      Code Objects Bit Flags.
                                                             (line   13)
* co_nlocals (codeobject 的屬性):        特殊唯讀屬性<2>.    (line   30)
* co_nlocals （程式碼物件屬性）:         Code objects.       (line   16)
* CO_OPTIMIZED (於 inspect 模組中):      Code Objects Bit Flags.
                                                             (line    9)
* co_positions() (codeobject 的方法):    用於程式碼物件的方法.
                                                             (line    6)
* co_posonlyargcount (codeobject 的屬性): 特殊唯讀屬性<2>.   (line   20)
* co_posonlyargcount （程式碼物件屬性）: Code objects.       (line   16)
* co_qualname (codeobject 的屬性):       特殊唯讀屬性<2>.    (line    9)
* co_qualname （程式碼物件屬性）:        Code objects.       (line   16)
* co_stacksize (codeobject 的屬性):      特殊唯讀屬性<2>.    (line   75)
* co_stacksize （程式碼物件屬性）:       Code objects.       (line   16)
* CO_VARARGS (於 inspect 模組中):        Code Objects Bit Flags.
                                                             (line   18)
* CO_VARKEYWORDS (於 inspect 模組中):    Code Objects Bit Flags.
                                                             (line   22)
* co_varnames (codeobject 的屬性):       特殊唯讀屬性<2>.    (line   34)
* co_varnames （程式碼物件屬性）:        Code objects.       (line   16)
* code (SystemExit 的屬性):              實體例外.           (line  337)
* code (urllib.error.HTTPError 的屬性):  urllib error --- urllib request 引發的例外類別.
                                                             (line   39)
* code (urllib.response.addinfourl 的屬性): urllib response --- Response classes used by urllib.
                                                             (line   39)
* code (xml.etree.ElementTree.ParseError 的屬性): 例外<14>.  (line   14)
* code (xml.parsers.expat.ExpatError 的屬性): ExpatError 例外.
                                                             (line    9)
* code object（程式碼物件）:             Code objects.       (line    6)
* code object（程式碼物件） <1>:         Methods.            (line   43)
* code object（程式碼物件） <2>:         marshal --- 内部 Python 物件序列化.
                                                             (line   31)
* code object（程式碼物件） <3>:         Cell 物件.          (line   50)
* code_context (inspect.FrameInfo 的屬性): 直譯器堆疊.       (line   32)
* code_context (inspect.Traceback 的屬性): 直譯器堆疊.       (line   72)
* code_info() (於 dis 模組中):           Analysis functions. (line   11)
* code（程式碼）;block:                  執行模型.           (line    6)
* Codec (codecs 中的類別):               Stateless Encoding and Decoding.
                                                             (line    9)
* CodecInfo (codecs 中的類別):           codecs --- 編解碼器註冊表和基底類別.
                                                             (line   58)
* Codecs:                                codecs --- 編解碼器註冊表和基底類別.
                                                             (line    8)
* Codecs;decode（解碼）:                 codecs --- 編解碼器註冊表和基底類別.
                                                             (line    8)
* Codecs;encode（編碼）:                 codecs --- 編解碼器註冊表和基底類別.
                                                             (line    8)
* coded_value (http.cookies.Morsel 的屬性): Morsel 物件.     (line   49)
* codepoint2name (於 html.entities 模組中): html entities --- HTML 一般實體的定義.
                                                             (line   31)
* codes (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line   16)
* CODESET (於 locale 模組中):            locale --- 國際化服務.
                                                             (line  184)
* CodeType (types 中的類別):             Standard Interpreter Types.
                                                             (line   55)
* coding（程式編寫）;style（風格）:      間奏曲：程式碼風格 Coding Style.
                                                             (line    6)
* col_offset (ast.AST 的屬性):           節點 Node 類別.     (line   43)
* collapse_addresses() (於 ipaddress 模組中): Other Module Level Functions.
                                                             (line   43)
* collapse_rfc2231_value() (於 email.utils 模組中): email utils：雜項工具.
                                                             (line  199)
* collect() (於 gc 模組中):              gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line   31)
* collectedDurations (unittest.TestResult 的屬性): Loading and running tests.
                                                             (line  277)
* Collection (collections.abc 中的類別): Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line   37)
* Collection (typing 中的類別):          collections abc 中容器 ABC 的別名.
                                                             (line   22)
* colno (json.JSONDecodeError 的屬性):   例外<12>.           (line   26)
* colno (re.PatternError 的屬性):        Exceptions.         (line   32)
* colon (mailbox.Maildir 的屬性):        Mailbox 物件<2>.    (line   45)
* COLON (於 token 模組中):               token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   70)
* COLONEQUAL (於 token 模組中):          token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  238)
* COLOR_BLACK (於 curses 模組中):        Constants.          (line  641)
* COLOR_BLUE (於 curses 模組中):         Constants.          (line  644)
* color_content() (於 curses 模組中):    函式<5>.            (line   45)
* COLOR_CYAN (於 curses 模組中):         Constants.          (line  647)
* COLOR_GREEN (於 curses 模組中):        Constants.          (line  650)
* COLOR_MAGENTA (於 curses 模組中):      Constants.          (line  653)
* color_pair() (於 curses 模組中):       函式<5>.            (line   53)
* COLOR_PAIRS (於 curses 模組中):        Constants.          (line   41)
* COLOR_RED (於 curses 模組中):          Constants.          (line  656)
* COLOR_WHITE (於 curses 模組中):        Constants.          (line  659)
* COLOR_YELLOW (於 curses 模組中):       Constants.          (line  662)
* color() (於 turtle 模組中):            Color control.      (line  104)
* colormode() (於 turtle 模組中):        Settings and special methods.
                                                             (line   33)
* COLORS (於 curses 模組中):             Constants.          (line   36)
* COLS (於 curses 模組中):               Constants.          (line   46)
* column() (tkinter.ttk.Treeview 的方法): ttk Treeview.      (line   35)
* columnize() (cmd.Cmd 的方法):          Cmd 物件.           (line   88)
* COLUMNS:                               函式<5>.            (line  595)
* COLUMNS <1>:                           函式<5>.            (line  598)
* columns (os.terminal_size 的屬性):     Querying the size of a terminal.
                                                             (line   30)
* comb() (於 math 模組中):               數論與表現函式.     (line   12)
* combinations_with_replacement() (於 itertools 模組中): Itertool 函式.
                                                             (line  157)
* combinations() (於 itertools 模組中):  Itertool 函式.      (line  119)
* combine() (datetime.datetime 的類別方法): datetime 物件.   (line  175)
* combining() (於 unicodedata 模組中):   unicodedata --- Unicode 資料庫.
                                                             (line   59)
* Combobox (tkinter.ttk 中的類別):       ttk Combobox.       (line    6)
* comma:                                 Parenthesized forms.
                                                             (line   20)
* COMMA (於 token 模組中):               token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   74)
* command (http.server.BaseHTTPRequestHandler 的屬性): http server — HTTP 伺服器.
                                                             (line   93)
* command line（命令列）:                完整的 Python 程式. (line   19)
* CommandCompiler (codeop 中的類別):     codeop --- 編譯 Python 程式碼.
                                                             (line   65)
* commands (pdb command):                Debugger Commands.  (line  160)
* comment (http.cookiejar.Cookie 的屬性): Cookie 物件<2>.    (line   62)
* comment (http.cookies.Morsel 的屬性):  Morsel 物件.        (line   13)
* comment (zipfile.ZipFile 的屬性):      ZipFile 物件.       (line  358)
* comment (zipfile.ZipInfo 的屬性):      ZipInfo 物件.       (line   88)
* COMMENT (於 token 模組中):             token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  260)
* comment_url (http.cookiejar.Cookie 的屬性): Cookie 物件<2>.
                                                             (line   67)
* comment() (xml.etree.ElementTree.TreeBuilder 的方法): TreeBuilder 物件.
                                                             (line   49)
* comment() (xml.sax.handler.LexicalHandler 的方法): LexicalHandler 物件.
                                                             (line   18)
* Comment() (於 xml.etree.ElementTree 模組中): 函式<8>.      (line   72)
* comment（註解）:                       Comments.           (line    6)
* commenters (shlex.shlex 的屬性):       shlex 物件.         (line   85)
* CommentHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line  335)
* commit() (sqlite3.Connection 的方法):  Connection 物件.    (line   72)
* common (filecmp.dircmp 的屬性):        The dircmp class.   (line   62)
* common_dirs (filecmp.dircmp 的屬性):   The dircmp class.   (line   74)
* common_files (filecmp.dircmp 的屬性):  The dircmp class.   (line   78)
* common_funny (filecmp.dircmp 的屬性):  The dircmp class.   (line   82)
* common_types (於 mimetypes 模組中):    mimetypes --- 將檔案名稱對映到 MIME 類型.
                                                             (line  157)
* commonpath() (於 os.path 模組中):      os path --- 常見的路徑名操作.
                                                             (line   60)
* commonprefix() (於 os.path 模組中):    os path --- 常見的路徑名操作.
                                                             (line   75)
* communicate() (asyncio.subprocess.Process 的方法): Interacting with Subprocesses.
                                                             (line   50)
* communicate() (subprocess.Popen 的方法): Popen Objects.    (line   36)
* Compare (ast 中的類別):                運算式<2>.          (line   89)
* compare_digest() (於 hmac 模組中):     hmac --- 基於金鑰雜湊的訊息驗證.
                                                             (line   99)
* compare_digest() (於 secrets 模組中):  其他函式.           (line    6)
* compare_networks() (ipaddress.IPv4Network 的方法): Network objects.
                                                             (line  237)
* compare_networks() (ipaddress.IPv6Network 的方法): Network objects.
                                                             (line  352)
* COMPARE_OP (opcode):                   Python Bytecode Instructions.
                                                             (line  787)
* compare_signal() (decimal.Context 的方法): Context objects.
                                                             (line  265)
* compare_signal() (decimal.Decimal 的方法): Decimal objects.
                                                             (line  157)
* compare_to() (tracemalloc.Snapshot 的方法): Snapshot.      (line   13)
* compare_total_mag() (decimal.Context 的方法): Context objects.
                                                             (line  273)
* compare_total_mag() (decimal.Decimal 的方法): Decimal objects.
                                                             (line  189)
* compare_total() (decimal.Context 的方法): Context objects. (line  269)
* compare_total() (decimal.Decimal 的方法): Decimal objects. (line  164)
* compare() (decimal.Context 的方法):    Context objects.    (line  261)
* compare() (decimal.Decimal 的方法):    Decimal objects.    (line  146)
* compare() (difflib.Differ 的方法):     Differ Objects.     (line   38)
* COMPARISON_FLAGS (於 doctest 模組中):  可選旗標.           (line  104)
* comparison（比較）:                    Basic customization.
                                                             (line  181)
* comparison（比較） <1>:                Comparisons.        (line    6)
* Compat32 (email.policy 中的類別):      email policy Policy Objects.
                                                             (line  563)
* compat32 (於 email.policy 模組中):     email policy Policy Objects.
                                                             (line  618)
* Compile (codeop 中的類別):             codeop --- 編譯 Python 程式碼.
                                                             (line   56)
* compile_command() (於 code 模組中):    code --- 直譯器基底類別.
                                                             (line   55)
* compile_command() (於 codeop 模組中):  codeop --- 編譯 Python 程式碼.
                                                             (line   29)
* compile_dir() (於 compileall 模組中):  Public functions.   (line    6)
* compile_file() (於 compileall 模組中): Public functions.   (line   93)
* compile_path() (於 compileall 模組中): Public functions.   (line  156)
* compile() (於 py_compile 模組中):      py_compile — 編譯 Python 來源檔案.
                                                             (line   24)
* compile() (於 re 模組中):              Functions.          (line    6)
* compileall 命令列選項; -b:             Command-line use.   (line   59)
* compileall 命令列選項; -d:             Command-line use.   (line   32)
* compileall 命令列選項; -e:             Command-line use.   (line  100)
* compileall 命令列選項; -f:             Command-line use.   (line   22)
* compileall 命令列選項; -hardlink-dupes: Command-line use.  (line  104)
* compileall 命令列選項; -i:             Command-line use.   (line   53)
* compileall 命令列選項; -invalidation-mode: Command-line use.
                                                             (line   80)
* compileall 命令列選項; -j:             Command-line use.   (line   74)
* compileall 命令列選項; -l:             Command-line use.   (line   17)
* compileall 命令列選項; -o:             Command-line use.   (line   94)
* compileall 命令列選項; -p:             Command-line use.   (line   42)
* compileall 命令列選項; -q:             Command-line use.   (line   26)
* compileall 命令列選項; -r:             Command-line use.   (line   67)
* compileall 命令列選項; -s:             Command-line use.   (line   40)
* compileall 命令列選項; -x:             Command-line use.   (line   47)
* compileall 命令列選項; directory:      Command-line use.   (line    9)
* compileall 命令列選項; file:           Command-line use.   (line    9)
* compiler_flag (__future__._Feature 的屬性): 模組內容<9>.   (line   81)
* complete_statement() (於 sqlite3 模組中): Module functions.
                                                             (line  106)
* complete() (rlcompleter.Completer 的方法): rlcompleter --- GNU readline 的補全函式.
                                                             (line   43)
* completedefault() (cmd.Cmd 的方法):    Cmd 物件.           (line   82)
* CompletedProcess (subprocess 中的類別): Using the subprocess Module.
                                                             (line  100)
* Completer (rlcompleter 中的類別):      rlcompleter --- GNU readline 的補全函式.
                                                             (line   39)
* Complex (numbers 中的類別):            數值的階層.         (line    6)
* complex (內建類別):                    內建函式.           (line  323)
* complex literal（複數常數）:           Numeric literals.   (line    6)
* complex number（複數）:                術語表.             (line  228)
* complex number（複數）;literals（字面值）: 數值型別 --- int、float、complex.
                                                             (line   15)
* complex（複數）;number（數字）:        numbers Complex complex.
                                                             (line    6)
* compound（複合）;statement（陳述式）:  複合陳述式.         (line    6)
* comprehension (ast 中的類別):          綜合運算式 comprehensions.
                                                             (line   57)
* comprehensions:                        Displays for lists sets and dictionaries.
                                                             (line    6)
* compress_size (zipfile.ZipInfo 的屬性): ZipInfo 物件.      (line  139)
* compress_type (zipfile.ZipInfo 的屬性): ZipInfo 物件.      (line   84)
* compress() (bz2.BZ2Compressor 的方法): Incremental de compression.
                                                             (line   15)
* compress() (lzma.LZMACompressor 的方法): Compressing and decompressing data in memory.
                                                             (line   81)
* compress() (zlib.Compress 的方法):     zlib --- 相容於 gzip 的壓縮.
                                                             (line  161)
* compress() (於 bz2 模組中):            One-shot de compression.
                                                             (line    6)
* compress() (於 gzip 模組中):           gzip --- gzip 檔案的支援.
                                                             (line  189)
* compress() (於 itertools 模組中):      Itertool 函式.      (line  195)
* compress() (於 lzma 模組中):           Compressing and decompressing data in memory.
                                                             (line  183)
* compress() (於 zlib 模組中):           zlib --- 相容於 gzip 的壓縮.
                                                             (line   37)
* compressed (ipaddress.IPv4Address 的屬性): Address objects.
                                                             (line   58)
* compressed (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line  107)
* compressed (ipaddress.IPv6Address 的屬性): Address objects.
                                                             (line  240)
* compressed (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  319)
* compression() (ssl.SSLSocket 的方法):  SSL Sockets.        (line  233)
* CompressionError:                      tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  207)
* compressobj() (於 zlib 模組中):        zlib --- 相容於 gzip 的壓縮.
                                                             (line   65)
* COMSPEC:                               行程管理.           (line  772)
* COMSPEC <1>:                           Popen Constructor.  (line  112)
* concat() (於 operator 模組中):         operator --- 標準運算子替代函式.
                                                             (line  164)
* Concatenate (於 typing 模組中):        特別型式.           (line   64)
* concatenation（串接）;operation（操作）: Common Sequence Operations.
                                                             (line   21)
* cond (bdb.Breakpoint 的屬性):          bdb --- 偵錯器框架. (line   95)
* Condition (asyncio 中的類別):          Condition.          (line    6)
* Condition (multiprocessing 中的類別):  Synchronization primitives.
                                                             (line   32)
* condition (pdb command):               Debugger Commands.  (line  153)
* Condition (threading 中的類別):        Condition Objects.  (line   72)
* Condition() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  172)
* Conditional（條件式）;expression:      Boolean operations. (line    6)
* conditional（條件式）;expression:      Conditional expressions.
                                                             (line    6)
* config() (tkinter.font.Font 的方法):   tkinter font --- Tkinter 字型包裝器.
                                                             (line   54)
* ConfigParser (configparser 中的類別):  ConfigParser 物件.  (line    6)
* configuration information（設定資訊）: sysconfig --- 提供 Python 設定資訊的存取.
                                                             (line   10)
* configuration（設定）;file（檔案）:    configparser --- 設定檔剖析器.
                                                             (line    8)
* configure_mock() (unittest.mock.Mock 的方法): Mock 類別.   (line  220)
* configure() (tkinter.ttk.Style 的方法): Ttk Styling.       (line   24)
* CONFORM (enum.FlagBoundary 的屬性):    資料型別<2>.        (line  637)
* confstr_names (於 os 模組中):          Miscellaneous System Information.
                                                             (line   28)
* confstr() (於 os 模組中):              Miscellaneous System Information.
                                                             (line    6)
* conjugate() (decimal.Decimal 的方法):  Decimal objects.    (line  201)
* conjugate() (numbers.Complex 的方法):  數值的階層.         (line   22)
* conjugate()（複數方法）:               數值型別 --- int、float、complex.
                                                             (line   85)
* connect_accepted_socket() (asyncio.loop 的方法): 建立網路伺服器.
                                                             (line  128)
* connect_ex() (socket.socket 的方法):   Socket 物件.        (line   86)
* connect_read_pipe() (asyncio.loop 的方法): 使用管道.       (line    6)
* connect_write_pipe() (asyncio.loop 的方法): 使用管道.      (line   22)
* connect() (ftplib.FTP 的方法):         FTP 物件.           (line   80)
* connect() (http.client.HTTPConnection 的方法): HTTPConnection 物件.
                                                             (line  142)
* connect() (multiprocessing.managers.BaseManager 的方法): Managers.
                                                             (line   76)
* connect() (smtplib.SMTP 的方法):       SMTP 物件.          (line   33)
* connect() (socket.socket 的方法):      Socket 物件.        (line   62)
* connect() (於 sqlite3 模組中):         Module functions.   (line    6)
* Connection (multiprocessing.connection 中的類別): Connection Objects.
                                                             (line   13)
* Connection (sqlite3 中的類別):         Connection 物件.    (line    6)
* connection (sqlite3.Cursor 的屬性):    Cursor 物件.        (line  176)
* connection_lost() (asyncio.BaseProtocol 的方法): Base Protocol.
                                                             (line   23)
* connection_made() (asyncio.BaseProtocol 的方法): Base Protocol.
                                                             (line   15)
* ConnectionAbortedError:                作業系統例外.       (line   42)
* ConnectionError:                       作業系統例外.       (line   27)
* ConnectionRefusedError:                作業系統例外.       (line   48)
* ConnectionResetError:                  作業系統例外.       (line   53)
* ConnectRegistry() (於 winreg 模組中):  函式<12>.           (line   17)
* const (optparse.Option 的屬性):        Option attributes.  (line   58)
* Constant (ast 中的類別):               文本 Literals.      (line    6)
* constant（常數）:                      Literals.           (line    6)
* constructor() (於 copyreg 模組中):     copyreg --- 註冊 pickle 支援函式.
                                                             (line   15)
* consumed (asyncio.LimitOverrunError 的屬性): 例外<8>.      (line   61)
* Container (collections.abc 中的類別):  Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line    6)
* Container (typing 中的類別):           collections abc 中容器 ABC 的別名.
                                                             (line   32)
* container（容器）:                     Objects values and types.
                                                             (line   67)
* container（容器） <1>:                 Custom classes.     (line   19)
* container（容器）;iteration over（疊代於）: 疊代器型別.    (line    6)
* CONTAINS_OP (opcode):                  Python Bytecode Instructions.
                                                             (line  802)
* contains() (於 operator 模組中):       operator --- 標準運算子替代函式.
                                                             (line  169)
* content (urllib.error.ContentTooShortError 的屬性): urllib error --- urllib request 引發的例外類別.
                                                             (line   65)
* content_disposition (email.headerregistry.ContentDispositionHeader 的屬性): email headerregistry：自訂標頭物件.
                                                             (line  285)
* content_manager (email.policy.EmailPolicy 的屬性): email policy Policy Objects.
                                                             (line  419)
* content_type (email.headerregistry.ContentTypeHeader 的屬性): email headerregistry：自訂標頭物件.
                                                             (line  272)
* ContentDispositionHeader (email.headerregistry 中的類別): email headerregistry：自訂標頭物件.
                                                             (line  280)
* ContentHandler (xml.sax.handler 中的類別): xml sax handler --- SAX 處理函式的基本類別.
                                                             (line   18)
* ContentManager (email.contentmanager 中的類別): email contentmanager：管理 MIME 內容.
                                                             (line   12)
* contents (ctypes._Pointer 的屬性):     Arrays and pointers.
                                                             (line   58)
* contents() (importlib.abc.ResourceReader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  514)
* contents() (importlib.resources.abc.ResourceReader 的方法): importlib resources abc -- 資源的抽象基底類別.
                                                             (line   68)
* contents() (於 importlib.resources 模組中): Functional API.
                                                             (line  150)
* ContentTooShortError:                  urllib error --- urllib request 引發的例外類別.
                                                             (line   60)
* ContentTransferEncoding (email.headerregistry 中的類別): email headerregistry：自訂標頭物件.
                                                             (line  290)
* ContentTypeHeader (email.headerregistry 中的類別): email headerregistry：自訂標頭物件.
                                                             (line  267)
* Context (contextvars 中的類別):        Manual Context Management.
                                                             (line   20)
* Context (decimal 中的類別):            Context objects.    (line  115)
* context (ssl.SSLSocket 的屬性):        SSL Sockets.        (line  326)
* context management protocol（情境管理協定）: 情境管理器型別.
                                                             (line    6)
* context manager（情境管理器）:         With Statement Context Managers.
                                                             (line   14)
* context manager（情境管理器） <1>:     情境管理器型別.     (line    6)
* context manager（情境管理器） <2>:     術語表.             (line  238)
* context variable（情境變數）:          術語表.             (line  244)
* context_diff() (於 difflib 模組中):    difflib --- 計算差異的輔助工具.
                                                             (line  155)
* ContextDecorator (contextlib 中的類別): Utilities.         (line  383)
* ContextManager (typing 中的類別):      contextlib ABC 的別名.
                                                             (line    6)
* contextmanager() (於 contextlib 模組中): Utilities.        (line   31)
* ContextVar (contextvars 中的類別):     Context Variables.  (line    6)
* CONTIG (inspect.BufferFlags 的屬性):   Buffer flags.       (line   33)
* CONTIG_RO (inspect.BufferFlags 的屬性): Buffer flags.      (line   35)
* contiguous (memoryview 的屬性):        Memory Views.       (line  486)
* contiguous（連續的）:                  shape strides suboffsets.
                                                             (line   26)
* contiguous（連續的） <1>:              術語表.             (line  252)
* Continue (ast 中的類別):               流程控制.           (line   93)
* continue (pdb command):                Debugger Commands.  (line  226)
* CONTINUOUS (enum.EnumCheck 的屬性):    資料型別<2>.        (line  578)
* control() (select.kqueue 的方法):      Kqueue Objects.     (line   22)
* controlnames (於 curses.ascii 模組中): curses ascii --- ASCII 字元的工具程式.
                                                             (line  240)
* CONTTYPE (於 tarfile 模組中):          tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  296)
* convert_arg_line_to_args() (argparse.ArgumentParser 的方法): Customizing file parsing.
                                                             (line    6)
* convert_field() (string.Formatter 的方法): 自訂字串格式.   (line  104)
* CONVERT_VALUE (opcode):                Python Bytecode Instructions.
                                                             (line 1139)
* Cookie (http.cookiejar 中的類別):      http cookiejar --- HTTP 客戶端的 Cookie 處理.
                                                             (line  112)
* CookieError:                           http cookies --- HTTP 狀態管理.
                                                             (line   34)
* CookieJar (http.cookiejar 中的類別):   http cookiejar --- HTTP 客戶端的 Cookie 處理.
                                                             (line   45)
* cookiejar (urllib.request.HTTPCookieProcessor 的屬性): HTTPCookieProcessor 物件.
                                                             (line    8)
* CookiePolicy (http.cookiejar 中的類別): http cookiejar --- HTTP 客戶端的 Cookie 處理.
                                                             (line   76)
* Coordinated Universal Time（世界協調時間）: time --- 時間存取與轉換.
                                                             (line   32)
* COPY (opcode):                         Python Bytecode Instructions.
                                                             (line  151)
* copy_abs() (decimal.Context 的方法):   Context objects.    (line  278)
* copy_abs() (decimal.Decimal 的方法):   Decimal objects.    (line  206)
* copy_context() (於 contextvars 模組中): Manual Context Management.
                                                             (line    6)
* copy_decimal() (decimal.Context 的方法): Context objects.  (line  185)
* copy_file_range() (於 os 模組中):      File Descriptor Operations.
                                                             (line   44)
* COPY_FREE_VARS (opcode):               Python Bytecode Instructions.
                                                             (line  986)
* copy_location() (於 ast 模組中):       ast 輔助程式.       (line  139)
* copy_negate() (decimal.Context 的方法): Context objects.   (line  282)
* copy_negate() (decimal.Decimal 的方法): Decimal objects.   (line  212)
* copy_sign() (decimal.Context 的方法):  Context objects.    (line  286)
* copy_sign() (decimal.Decimal 的方法):  Decimal objects.    (line  218)
* copy() (collections.deque 的方法):     deque 物件.         (line   41)
* copy() (contextvars.Context 的方法):   Manual Context Management.
                                                             (line   75)
* copy() (decimal.Context 的方法):       Context objects.    (line  181)
* copy() (dict 的方法):                  Mapping Types --- dict.
                                                             (line  139)
* copy() (frozenset 的方法):             Set Types --- set frozenset.
                                                             (line  123)
* copy() (hashlib.hash 的方法):          雜湊物件.           (line   45)
* copy() (hmac.HMAC 的方法):             hmac --- 基於金鑰雜湊的訊息驗證.
                                                             (line   71)
* copy() (http.cookies.Morsel 的方法):   Morsel 物件.        (line   95)
* copy() (imaplib.IMAP4 的方法):         IMAP4 物件.         (line   68)
* copy() (tkinter.font.Font 的方法):     tkinter font --- Tkinter 字型包裝器.
                                                             (line   58)
* copy() (types.MappingProxyType 的方法): Standard Interpreter Types.
                                                             (line  298)
* copy() (zlib.Compress 的方法):         zlib --- 相容於 gzip 的壓縮.
                                                             (line  178)
* copy() (zlib.Decompress 的方法):       zlib --- 相容於 gzip 的壓縮.
                                                             (line  233)
* copy() (於 copy 模組中):               copy --- 淺層 shallow 和深層 deep 複製操作.
                                                             (line   17)
* copy() (於 multiprocessing.sharedctypes 模組中): multiprocessing sharedctypes 模組.
                                                             (line   83)
* copy() (於 shutil 模組中):             Directory and files operations.
                                                             (line  121)
* copy()（序列方法）:                    Mutable Sequence Types.
                                                             (line   16)
* Copy（複製）:                          Help menu Shell and Editor.
                                                             (line   30)
* copy（複製）;protocol（協定）:         Pickling Class Instances.
                                                             (line  111)
* copy2() (於 shutil 模組中):            Directory and files operations.
                                                             (line  153)
* copyfile() (於 shutil 模組中):         Directory and files operations.
                                                             (line   17)
* copyfileobj() (於 shutil 模組中):      Directory and files operations.
                                                             (line    6)
* copying files（複製檔案）:             shutil — 高階檔案操作.
                                                             (line    8)
* copymode() (於 shutil 模組中):         Directory and files operations.
                                                             (line   59)
* copyright (內建變數):                  由 site module（模組）所添增的常數.
                                                             (line   24)
* copyright (於 sys 模組中):             sys --- 系統特定的參數與函式.
                                                             (line  174)
* copyright（sys 模組中）:               Process-wide parameters.
                                                             (line  188)
* copysign() (於 math 模組中):           數論與表現函式.     (line   26)
* copystat() (於 shutil 模組中):         Directory and files operations.
                                                             (line   77)
* copytree() (於 shutil 模組中):         Directory and files operations.
                                                             (line  192)
* Coroutine (collections.abc 中的類別):  Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line  127)
* Coroutine (typing 中的類別):           Aliases to asynchronous ABCs in collections abc.
                                                             (line    6)
* coroutine function（協程函式）:        術語表.             (line  269)
* coroutine() (於 types 模組中):         Coroutine Utility Functions.
                                                             (line    6)
* coroutine（協程）:                     Special method lookup.
                                                             (line   74)
* coroutine（協程） <1>:                 Yield expressions.  (line   53)
* coroutine（協程） <2>:                 術語表.             (line  262)
* coroutine（協程）;function （函式）:   Coroutine functions.
                                                             (line    6)
* CoroutineType (於 types 模組中):       Standard Interpreter Types.
                                                             (line   41)
* correlation() (於 statistics 模組中):  函式細節.           (line  529)
* cos() (於 cmath 模組中):               三角函數.           (line   20)
* cos() (於 math 模組中):                Trigonometric functions.
                                                             (line   31)
* cosh() (於 cmath 模組中):              雙曲函數.           (line   21)
* cosh() (於 math 模組中):               Hyperbolic functions.
                                                             (line   21)
* count (tracemalloc.Statistic 的屬性):  Statistic.          (line   15)
* count (tracemalloc.StatisticDiff 的屬性): StatisticDiff.   (line   15)
* count_diff (tracemalloc.StatisticDiff 的屬性): StatisticDiff.
                                                             (line   20)
* count() (array.array 的方法):          array --- 高效率的數值型陣列.
                                                             (line  136)
* count() (bytearray 的方法):            Bytes and Bytearray Operations.
                                                             (line   36)
* count() (bytes 的方法):                Bytes and Bytearray Operations.
                                                             (line   36)
* count() (collections.deque 的方法):    deque 物件.         (line   47)
* count() (multiprocessing.shared_memory.ShareableList 的方法): multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取.
                                                             (line  300)
* count() (str 的方法):                  String Methods<2>.  (line   55)
* count() (於 itertools 模組中):         Itertool 函式.      (line  206)
* count()（序列方法）:                   Common Sequence Operations.
                                                             (line   21)
* Counter (collections 中的類別):        Counter 物件.       (line   23)
* Counter (typing 中的類別):             collections 中型別的別名.
                                                             (line   37)
* countOf() (於 operator 模組中):        operator --- 標準運算子替代函式.
                                                             (line  174)
* countTestCases() (unittest.TestCase 的方法): Test cases.   (line  728)
* countTestCases() (unittest.TestSuite 的方法): Grouping tests.
                                                             (line   55)
* covariance() (於 statistics 模組中):   函式細節.           (line  507)
* CoverageResults (trace 中的類別):      Programmatic Interface.
                                                             (line   47)
* CPPFLAGS:                              New Improved and Deprecated Modules<4>.
                                                             (line   59)
* CPPFLAGS <1>:                          Preprocessor flags. (line    8)
* CPPFLAGS <2>:                          Preprocessor flags. (line   18)
* CPPFLAGS <3>:                          Linker flags.       (line   50)
* CPU time（CPU 時間）:                  函式<4>.            (line  216)
* CPU time（CPU 時間） <1>:              函式<4>.            (line  516)
* cpu_count() (於 multiprocessing 模組中): Miscellaneous<2>. (line   13)
* cpu_count() (於 os 模組中):            Miscellaneous System Information.
                                                             (line   37)
* CPython:                               術語表.             (line  276)
* cpython_only() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  525)
* CR (於 curses.ascii 模組中):           curses ascii --- ASCII 字元的工具程式.
                                                             (line   64)
* crawl_delay() (urllib.robotparser.RobotFileParser 的方法): urllib robotparser --- robots txt 的剖析器.
                                                             (line   46)
* CRC (zipfile.ZipInfo 的屬性):          ZipInfo 物件.       (line  135)
* crc_hqx() (於 binascii 模組中):        binascii --- 在二進位制和 ASCII 之間轉換.
                                                             (line   91)
* crc32() (於 binascii 模組中):          binascii --- 在二進位制和 ASCII 之間轉換.
                                                             (line   98)
* crc32() (於 zlib 模組中):              zlib --- 相容於 gzip 的壓縮.
                                                             (line   95)
* create_aggregate() (sqlite3.Connection 的方法): Connection 物件.
                                                             (line  157)
* create_archive() (於 zipapp 模組中):   Python API.         (line    8)
* create_autospec() (於 unittest.mock 模組中): create_autospec.
                                                             (line    6)
* CREATE_BREAKAWAY_FROM_JOB (於 subprocess 模組中): Windows Constants.
                                                             (line  140)
* create_collation() (sqlite3.Connection 的方法): Connection 物件.
                                                             (line  301)
* create_configuration() (venv.EnvBuilder 的方法): API<2>.   (line  141)
* create_connection() (asyncio.loop 的方法): 打開網路連線.   (line    6)
* create_connection() (於 socket 模組中): 建立 sockets.      (line   82)
* create_datagram_endpoint() (asyncio.loop 的方法): 打開網路連線.
                                                             (line  127)
* create_decimal_from_float() (decimal.Context 的方法): Context objects.
                                                             (line  213)
* create_decimal() (decimal.Context 的方法): Context objects.
                                                             (line  189)
* create_default_context() (於 ssl 模組中): 語境建立.        (line    8)
* CREATE_DEFAULT_ERROR_MODE (於 subprocess 模組中): Windows Constants.
                                                             (line  130)
* create_eager_task_factory() (於 asyncio 模組中): Eager Task Factory.
                                                             (line   32)
* create_empty_file() (於 test.support.os_helper 模組中): test support os_helper --- 用於 os 測試的工具.
                                                             (line   91)
* create_function() (sqlite3.Connection 的方法): Connection 物件.
                                                             (line  115)
* create_future() (asyncio.loop 的方法): 建立 Futures 和 Tasks.
                                                             (line    6)
* create_git_ignore_file() (venv.EnvBuilder 的方法): API<2>. (line  219)
* create_module() (importlib.abc.Loader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  103)
* create_module() (importlib.machinery.ExtensionFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  308)
* create_module() (zipimport.zipimporter 的方法): zipimporter 物件.
                                                             (line   23)
* CREATE_NEW_CONSOLE (於 subprocess 模組中): Windows Constants.
                                                             (line   54)
* CREATE_NEW_PROCESS_GROUP (於 subprocess 模組中): Windows Constants.
                                                             (line   59)
* CREATE_NO_WINDOW (於 subprocess 模組中): Windows Constants.
                                                             (line  115)
* create_server() (asyncio.loop 的方法): 建立網路伺服器.     (line    6)
* create_server() (於 socket 模組中):    建立 sockets.       (line  113)
* create_stats() (profile.Profile 的方法): profile and cProfile Module Reference.
                                                             (line   86)
* create_string_buffer() (於 ctypes 模組中): Utility functions.
                                                             (line   39)
* create_subprocess_exec() (於 asyncio 模組中): 建立子行程.  (line    6)
* create_subprocess_shell() (於 asyncio 模組中): 建立子行程. (line   23)
* create_system (zipfile.ZipInfo 的屬性): ZipInfo 物件.      (line   99)
* create_task() (asyncio.loop 的方法):   建立 Futures 和 Tasks.
                                                             (line   15)
* create_task() (asyncio.TaskGroup 的方法): Task Groups.     (line   17)
* create_task() (於 asyncio 模組中):     Creating Tasks.     (line   10)
* create_unicode_buffer() (於 ctypes 模組中): Utility functions.
                                                             (line   57)
* create_unix_connection() (asyncio.loop 的方法): 打開網路連線.
                                                             (line  193)
* create_unix_server() (asyncio.loop 的方法): 建立網路伺服器.
                                                             (line  100)
* create_version (zipfile.ZipInfo 的屬性): ZipInfo 物件.     (line  103)
* create_window_function() (sqlite3.Connection 的方法): Connection 物件.
                                                             (line  212)
* create() (imaplib.IMAP4 的方法):       IMAP4 物件.         (line   72)
* create() (venv.EnvBuilder 的方法):     API<2>.             (line   59)
* create() (於 venv 模組中):             API<2>.             (line  229)
* createAttribute() (xml.dom.Document 的方法): Document Objects.
                                                             (line   46)
* createAttributeNS() (xml.dom.Document 的方法): Document Objects.
                                                             (line   53)
* createComment() (xml.dom.Document 的方法): Document Objects.
                                                             (line   34)
* createDocument() (xml.dom.DOMImplementation 的方法): DOMImplementation 物件.
                                                             (line   16)
* createDocumentType() (xml.dom.DOMImplementation 的方法): DOMImplementation 物件.
                                                             (line   26)
* createElement() (xml.dom.Document 的方法): Document Objects.
                                                             (line   14)
* createElementNS() (xml.dom.Document 的方法): Document Objects.
                                                             (line   21)
* createfilehandler() (_tkinter.Widget.tk 的方法): File Handlers.
                                                             (line   27)
* CreateKey() (於 winreg 模組中):        函式<12>.           (line   35)
* CreateKeyEx() (於 winreg 模組中):      函式<12>.           (line   63)
* createLock() (logging.Handler 的方法): Handler Objects.    (line   20)
* createLock() (logging.NullHandler 的方法): NullHandler.    (line   24)
* createProcessingInstruction() (xml.dom.Document 的方法): Document Objects.
                                                             (line   40)
* createSocket() (logging.handlers.SocketHandler 的方法): SocketHandler.
                                                             (line   72)
* createSocket() (logging.handlers.SysLogHandler 的方法): SysLogHandler.
                                                             (line   50)
* createTextNode() (xml.dom.Document 的方法): Document Objects.
                                                             (line   28)
* credits (內建變數):                    由 site module（模組）所添增的常數.
                                                             (line   24)
* CRITICAL (於 logging 模組中):          Logging Levels.     (line   45)
* critical() (logging.Logger 的方法):    Logger 物件.        (line  304)
* critical() (於 logging 模組中):        Module-Level Functions.
                                                             (line   86)
* CRNCYSTR (於 locale 模組中):           locale --- 國際化服務.
                                                             (line  292)
* CRT_ASSEMBLY_VERSION (於 msvcrt 模組中): Other Functions.  (line   89)
* CRT_ASSERT (於 msvcrt 模組中):         Other Functions.    (line   66)
* CRT_ERROR (於 msvcrt 模組中):          Other Functions.    (line   61)
* CRT_WARN (於 msvcrt 模組中):           Other Functions.    (line   56)
* CRTDBG_MODE_DEBUG (於 msvcrt 模組中):  Other Functions.    (line   70)
* CRTDBG_MODE_FILE (於 msvcrt 模組中):   Other Functions.    (line   74)
* CRTDBG_MODE_WNDW (於 msvcrt 模組中):   Other Functions.    (line   80)
* CRTDBG_REPORT_MODE (於 msvcrt 模組中): Other Functions.    (line   85)
* CrtSetReportFile() (於 msvcrt 模組中): Other Functions.    (line   48)
* CrtSetReportMode() (於 msvcrt 模組中): Other Functions.    (line   40)
* cryptography（密碼學）:                加密服務.           (line    6)
* cssclass_month (calendar.HTMLCalendar 的屬性): calendar --- 日曆相關函式.
                                                             (line  202)
* cssclass_month_head (calendar.HTMLCalendar 的屬性): calendar --- 日曆相關函式.
                                                             (line  195)
* cssclass_noday (calendar.HTMLCalendar 的屬性): calendar --- 日曆相關函式.
                                                             (line  182)
* cssclass_year (calendar.HTMLCalendar 的屬性): calendar --- 日曆相關函式.
                                                             (line  209)
* cssclass_year_head (calendar.HTMLCalendar 的屬性): calendar --- 日曆相關函式.
                                                             (line  216)
* cssclasses (calendar.HTMLCalendar 的屬性): calendar --- 日曆相關函式.
                                                             (line  170)
* cssclasses_weekday_head (calendar.HTMLCalendar 的屬性): calendar --- 日曆相關函式.
                                                             (line  188)
* csv:                                   csv --- CSV 檔案讀取及寫入.
                                                             (line    8)
* cte (email.headerregistry.ContentTransferEncoding 的屬性): email headerregistry：自訂標頭物件.
                                                             (line  294)
* cte_type (email.policy.Policy 的屬性): email policy Policy Objects.
                                                             (line  160)
* ctermid() (於 os 模組中):              行程參數.           (line    9)
* ctime() (datetime.date 的方法):        date 物件.          (line  282)
* ctime() (datetime.datetime 的方法):    datetime 物件.      (line  730)
* ctime() (於 time 模組中):              函式<4>.            (line   85)
* CTRL_BREAK_EVENT (於 signal 模組中):   模組內容<5>.        (line  199)
* CTRL_C_EVENT (於 signal 模組中):       模組內容<5>.        (line  190)
* ctrl() (於 curses.ascii 模組中):       curses ascii --- ASCII 字元的工具程式.
                                                             (line  216)
* curdir (於 os 模組中):                 Miscellaneous System Information.
                                                             (line  104)
* currency() (於 locale 模組中):         locale --- 國際化服務.
                                                             (line  462)
* current_process() (於 multiprocessing 模組中): Miscellaneous<2>.
                                                             (line   34)
* current_task() (於 asyncio 模組中):    Introspection.      (line    6)
* current_thread() (於 threading 模組中): threading --- 基於執行緒的平行性.
                                                             (line   60)
* current() (tkinter.ttk.Combobox 的方法): ttk Combobox.     (line    8)
* CurrentByteIndex (xml.parsers.expat.xmlparser 的屬性): XMLParser 物件<2>.
                                                             (line  195)
* CurrentColumnNumber (xml.parsers.expat.xmlparser 的屬性): XMLParser 物件<2>.
                                                             (line  199)
* currentframe() (於 inspect 模組中):    直譯器堆疊.         (line  159)
* CurrentLineNumber (xml.parsers.expat.xmlparser 的屬性): XMLParser 物件<2>.
                                                             (line  203)
* curs_set() (於 curses 模組中):         函式<5>.            (line   61)
* Cursor (sqlite3 中的類別):             Cursor 物件.        (line   19)
* cursor() (sqlite3.Connection 的方法):  Connection 物件.    (line   27)
* cursyncup() (curses.window 的方法):    Window Objects.     (line  171)
* Cut（剪下）:                           Help menu Shell and Editor.
                                                             (line   30)
* cwd() (ftplib.FTP 的方法):             FTP 物件.           (line  293)
* cwd() (pathlib.Path 的類別方法):       Expanding and resolving paths.
                                                             (line   29)
* cycle() (於 itertools 模組中):         Itertool 函式.      (line  225)
* CycleError:                            例外<2>.            (line    8)
* Cyclic Redundancy Check（循環冗餘核對）: zlib --- 相容於 gzip 的壓縮.
                                                             (line   97)
* D_FMT (於 locale 模組中):              locale --- 國際化服務.
                                                             (line  195)
* D_T_FMT (於 locale 模組中):            locale --- 國際化服務.
                                                             (line  189)
* daemon (multiprocessing.Process 的屬性): Process 與例外.   (line  101)
* daemon (threading.Thread 的屬性):      Thread Objects.     (line  202)
* daemon_threads (socketserver.ThreadingMixIn 的屬性): Server Creation Notes.
                                                             (line   55)
* dangling;else:                         複合陳述式.         (line   55)
* data (collections.UserDict 的屬性):    UserDict 物件.      (line   20)
* data (collections.UserList 的屬性):    UserList 物件.      (line   23)
* data (collections.UserString 的屬性):  UserString 物件.    (line   20)
* data (select.kevent 的屬性):           Kevent Objects.     (line  175)
* data (selectors.SelectorKey 的屬性):   Classes<3>.         (line   48)
* data (urllib.request.Request 的屬性):  Request Objects.    (line   39)
* data (xml.dom.Comment 的屬性):         Comment Objects.    (line    9)
* data (xml.dom.ProcessingInstruction 的屬性): ProcessingInstruction 物件.
                                                             (line   14)
* data (xml.dom.Text 的屬性):            Text and CDATASection Objects.
                                                             (line   15)
* data (xmlrpc.client.Binary 的屬性):    Binary Objects.     (line   12)
* data_filter() (於 tarfile 模組中):     Default named filters.
                                                             (line   36)
* data_open() (urllib.request.DataHandler 的方法): DataHandler 物件.
                                                             (line    6)
* data_received() (asyncio.Protocol 的方法): Streaming Protocols.
                                                             (line   13)
* data() (xml.etree.ElementTree.TreeBuilder 的方法): TreeBuilder 物件.
                                                             (line   33)
* data（資料）:                          Objects values and types.
                                                             (line    6)
* data（資料）;tabular（表格）:          csv --- CSV 檔案讀取及寫入.
                                                             (line    8)
* data（資料）;type（型別）:             標準型別階層.       (line    6)
* DatabaseError:                         例外<4>.            (line   44)
* databases（資料庫）:                   dbm dumb --- 可攜式 DBM 實作.
                                                             (line    8)
* dataclass_transform() (於 typing 模組中): 函式與裝飾器.    (line  114)
* dataclass() (於 dataclasses 模組中):   模組內容<8>.        (line    6)
* DataError:                             例外<4>.            (line   51)
* datagram_received() (asyncio.DatagramProtocol 的方法): Datagram Protocols.
                                                             (line    9)
* DatagramHandler (logging.handlers 中的類別): DatagramHandler.
                                                             (line   10)
* DatagramProtocol (asyncio 中的類別):   Base Protocols.     (line   20)
* DatagramRequestHandler (socketserver 中的類別): Request Handler Objects.
                                                             (line   56)
* DatagramTransport (asyncio 中的類別):  Transports Hierarchy.
                                                             (line   43)
* DataHandler (urllib.request 中的類別): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  389)
* date (datetime 中的類別):              date 物件.          (line   13)
* date_time (zipfile.ZipInfo 的屬性):    ZipInfo 物件.       (line   54)
* date_time_string() (http.server.BaseHTTPRequestHandler 的方法): http server — HTTP 伺服器.
                                                             (line  318)
* date() (datetime.datetime 的方法):     datetime 物件.      (line  435)
* DateHeader (email.headerregistry 中的類別): email headerregistry：自訂標頭物件.
                                                             (line  136)
* datetime (datetime 中的類別):          datetime 物件.      (line   17)
* datetime (email.headerregistry.DateHeader 的屬性): email headerregistry：自訂標頭物件.
                                                             (line  145)
* DateTime (xmlrpc.client 中的類別):     日期時間物件.       (line    6)
* Day (calendar 中的類別):               calendar --- 日曆相關函式.
                                                             (line  348)
* day (datetime.date 的屬性):            date 物件.          (line  124)
* day (datetime.datetime 的屬性):        datetime 物件.      (line  306)
* DAY_1 (於 locale 模組中):              locale --- 國際化服務.
                                                             (line  212)
* DAY_2 (於 locale 模組中):              locale --- 國際化服務.
                                                             (line  212)
* DAY_3 (於 locale 模組中):              locale --- 國際化服務.
                                                             (line  212)
* DAY_4 (於 locale 模組中):              locale --- 國際化服務.
                                                             (line  212)
* DAY_5 (於 locale 模組中):              locale --- 國際化服務.
                                                             (line  212)
* DAY_6 (於 locale 模組中):              locale --- 國際化服務.
                                                             (line  212)
* DAY_7 (於 locale 模組中):              locale --- 國際化服務.
                                                             (line  212)
* day_abbr (於 calendar 模組中):         calendar --- 日曆相關函式.
                                                             (line  332)
* day_name (於 calendar 模組中):         calendar --- 日曆相關函式.
                                                             (line  328)
* daylight (於 time 模組中):             Timezone Constants. (line   13)
* Daylight Saving Time（日光節約時間）:  time --- 時間存取與轉換.
                                                             (line   36)
* days (datetime.timedelta 的屬性):      timedelta 物件.     (line   95)
* DbfilenameShelf (shelve 中的類別):     Restrictions.       (line   73)
* DC1 (於 curses.ascii 模組中):          curses ascii --- ASCII 字元的工具程式.
                                                             (line   76)
* DC2 (於 curses.ascii 模組中):          curses ascii --- ASCII 字元的工具程式.
                                                             (line   79)
* DC3 (於 curses.ascii 模組中):          curses ascii --- ASCII 字元的工具程式.
                                                             (line   82)
* DC4 (於 curses.ascii 模組中):          curses ascii --- ASCII 字元的工具程式.
                                                             (line   85)
* dcgettext() (於 locale 模組中):        Access to message catalogs.
                                                             (line   10)
* ddocumentation strings（說明字串）:    定義函式 function.  (line   20)
* ddocumentation strings（說明字串） <1>: 說明文件字串 Documentation Strings.
                                                             (line    6)
* deactivate_stack_trampoline() (於 sys 模組中): sys --- 系統特定的參數與函式.
                                                             (line 1715)
* deallocation, object:                  Finalization and De-allocation.
                                                             (line    6)
* debug (imaplib.IMAP4 的屬性):          IMAP4 物件.         (line  398)
* debug (pdb command):                   Debugger Commands.  (line  429)
* debug (shlex.shlex 的屬性):            shlex 物件.         (line  161)
* debug (sys.flags 的屬性):              sys --- 系統特定的參數與函式.
                                                             (line  522)
* debug (zipfile.ZipFile 的屬性):        ZipFile 物件.       (line  352)
* DEBUG (於 logging 模組中):             Logging Levels.     (line   24)
* DEBUG (於 re 模組中):                  旗標.               (line   32)
* DEBUG_BYTECODE_SUFFIXES (於 importlib.machinery 模組中): importlib machinery -- Importers and path hooks.
                                                             (line   20)
* DEBUG_COLLECTABLE (於 gc 模組中):      gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line  290)
* DEBUG_LEAK (於 gc 模組中):             gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line  307)
* DEBUG_SAVEALL (於 gc 模組中):          gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line  302)
* debug_src() (於 doctest 模組中):       Debugging.          (line  147)
* DEBUG_STATS (於 gc 模組中):            gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line  286)
* DEBUG_UNCOLLECTABLE (於 gc 模組中):    gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line  294)
* debug() (logging.Logger 的方法):       Logger 物件.        (line  183)
* debug() (unittest.TestCase 的方法):    Test cases.         (line  120)
* debug() (unittest.TestSuite 的方法):   Grouping tests.     (line   48)
* debug() (於 doctest 模組中):           Debugging.          (line  124)
* debug() (於 logging 模組中):           Module-Level Functions.
                                                             (line   46)
* debugger（除錯器）:                    threading --- 基於執行緒的平行性.
                                                             (line  178)
* debugger（除錯器） <1>:                Debug menu Shell window only.
                                                             (line   15)
* debugger（除錯器） <2>:                sys --- 系統特定的參數與函式.
                                                             (line  906)
* debugger（除錯器） <3>:                sys --- 系統特定的參數與函式.
                                                             (line 1557)
* debugger（除錯器）;configuration（設定）;file（檔案）: Debugger Commands.
                                                             (line   59)
* debugging（除錯）:                     pdb --- The Python Debugger.
                                                             (line    8)
* debugging（除錯）;assertions（斷言）:  assert 陳述式.      (line    6)
* debuglevel (http.client.HTTPResponse 的屬性): HTTPResponse 物件.
                                                             (line   69)
* DebugRunner (doctest 中的類別):        Debugging.          (line  168)
* DECEMBER (於 calendar 模組中):         calendar --- 日曆相關函式.
                                                             (line  365)
* Decimal (decimal 中的類別):            Decimal objects.    (line    6)
* decimal literal（十進位常數）:         Numeric literals.   (line    6)
* decimal() (於 unicodedata 模組中):     unicodedata --- Unicode 資料庫.
                                                             (line   31)
* DecimalException (decimal 中的類別):   Signals.            (line   28)
* decode (codecs.CodecInfo 的屬性):      codecs --- 編解碼器註冊表和基底類別.
                                                             (line   69)
* decode_header() (於 email.header 模組中): email header：國際化標頭.
                                                             (line  183)
* decode_params() (於 email.utils 模組中): email utils：雜項工具.
                                                             (line  216)
* decode_rfc2231() (於 email.utils 模組中): email utils：雜項工具.
                                                             (line  187)
* decode_source() (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line   72)
* decode() (bytearray 的方法):           Bytes and Bytearray Operations.
                                                             (line   92)
* decode() (bytes 的方法):               Bytes and Bytearray Operations.
                                                             (line   92)
* decode() (codecs.Codec 的方法):        Stateless Encoding and Decoding.
                                                             (line   29)
* decode() (codecs.IncrementalDecoder 的方法): IncrementalDecoder 物件.
                                                             (line   28)
* decode() (json.JSONDecoder 的方法):    編碼器與解碼器.     (line   80)
* decode() (xmlrpc.client.Binary 的方法): Binary Objects.    (line   20)
* decode() (xmlrpc.client.DateTime 的方法): 日期時間物件.    (line   13)
* decode() (於 base64 模組中):           base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  223)
* decode() (於 codecs 模組中):           codecs --- 編解碼器註冊表和基底類別.
                                                             (line   34)
* decode() (於 quopri 模組中):           quopri --- 編碼和解碼 MIME 可列印字元資料.
                                                             (line   16)
* decodebytes() (於 base64 模組中):      base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  229)
* DecodedGenerator (email.generator 中的類別): email generator：產生 MIME 文件.
                                                             (line  231)
* decodestring() (於 quopri 模組中):     quopri --- 編碼和解碼 MIME 可列印字元資料.
                                                             (line   34)
* decomposition() (於 unicodedata 模組中): unicodedata --- Unicode 資料庫.
                                                             (line   75)
* decompress() (bz2.BZ2Decompressor 的方法): Incremental de compression.
                                                             (line   45)
* decompress() (lzma.LZMADecompressor 的方法): Compressing and decompressing data in memory.
                                                             (line  132)
* decompress() (zlib.Decompress 的方法): zlib --- 相容於 gzip 的壓縮.
                                                             (line  209)
* decompress() (於 bz2 模組中):          One-shot de compression.
                                                             (line   16)
* decompress() (於 gzip 模組中):         gzip --- gzip 檔案的支援.
                                                             (line  211)
* decompress() (於 lzma 模組中):         Compressing and decompressing data in memory.
                                                             (line  192)
* decompress() (於 zlib 模組中):         zlib --- 相容於 gzip 的壓縮.
                                                             (line  106)
* decompressobj() (於 zlib 模組中):      zlib --- 相容於 gzip 的壓縮.
                                                             (line  141)
* decorator（裝飾器）:                   術語表.             (line  282)
* DEDENT (於 token 模組中):              token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   52)
* DEDENT token（縮排標誌）:              Indentation.        (line   33)
* DEDENT token（縮排標誌） <1>:          複合陳述式.         (line   55)
* dedent() (於 textwrap 模組中):         textwrap --- 文字包裝與填充.
                                                             (line   76)
* deepcopy() (於 copy 模組中):           copy --- 淺層 shallow 和深層 deep 複製操作.
                                                             (line   21)
* def_prog_mode() (於 curses 模組中):    函式<5>.            (line   70)
* def_shell_mode() (於 curses 模組中):   函式<5>.            (line   77)
* default (inspect.Parameter 的屬性):    Introspecting callables with the Signature object.
                                                             (line  217)
* default (optparse.Option 的屬性):      Option attributes.  (line   44)
* default (於 email.policy 模組中):      email policy Policy Objects.
                                                             (line  504)
* DEFAULT (於 unittest.mock 模組中):     DEFAULT.            (line    6)
* DEFAULT_BUFFER_SIZE (於 io 模組中):    高階模組介面.       (line    6)
* default_bufsize (於 xml.dom.pulldom 模組中): xml dom pulldom --- 支援建置部分 DOM 樹.
                                                             (line  103)
* default_exception_handler() (asyncio.loop 的方法): 錯誤處理 API.
                                                             (line   31)
* default_factory (collections.defaultdict 的屬性): defaultdict 物件.
                                                             (line   41)
* DEFAULT_FORMAT (於 tarfile 模組中):    tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  328)
* DEFAULT_IGNORES (於 filecmp 模組中):   The dircmp class.   (line  114)
* default_loader() (於 xml.etree.ElementInclude 模組中): 函式<9>.
                                                             (line    6)
* default_max_str_digits (sys.int_info 的屬性): sys --- 系統特定的參數與函式.
                                                             (line 1114)
* default_open() (urllib.request.BaseHandler 的方法): BaseHandler 物件.
                                                             (line   30)
* DEFAULT_PROTOCOL (於 pickle 模組中):   模組介面.           (line   21)
* DEFAULT_TIMEOUT (unittest.mock.ThreadingMock 的屬性): Mock 類別.
                                                             (line  909)
* default_timer() (於 timeit 模組中):    Python 介面.        (line   29)
* default() (cmd.Cmd 的方法):            Cmd 物件.           (line   76)
* default() (json.JSONEncoder 的方法):   編碼器與解碼器.     (line  181)
* default（預設）;parameter（參數）;value（值）: 函式定義.   (line   65)
* DefaultContext (decimal 中的類別):     Context objects.    (line   90)
* DefaultCookiePolicy (http.cookiejar 中的類別): http cookiejar --- HTTP 客戶端的 Cookie 處理.
                                                             (line   81)
* defaultdict (collections 中的類別):    defaultdict 物件.   (line    6)
* DefaultDict (typing 中的類別):         collections 中型別的別名.
                                                             (line    6)
* DefaultEventLoopPolicy (asyncio 中的類別): Policy Objects. (line   54)
* DefaultHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line  350)
* DefaultHandlerExpand() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line  357)
* defaults() (configparser.ConfigParser 的方法): ConfigParser 物件.
                                                             (line  104)
* DefaultSelector (selectors 中的類別):  Classes<3>.         (line  161)
* defaultTestLoader (於 unittest 模組中): Loading and running tests.
                                                             (line  457)
* defaultTestResult() (unittest.TestCase 的方法): Test cases.
                                                             (line  733)
* defects (email.headerregistry.BaseHeader 的屬性): email headerregistry：自訂標頭物件.
                                                             (line   52)
* defects (email.message.EmailMessage 的屬性): email message：表示電子郵件訊息.
                                                             (line  709)
* defects (email.message.Message 的屬性): email message Message Representing an email message using the compat32 API.
                                                             (line  722)
* defpath (於 os 模組中):                Miscellaneous System Information.
                                                             (line  144)
* DefragResult (urllib.parse 中的類別):  Structured Parse Results.
                                                             (line   40)
* DefragResultBytes (urllib.parse 中的類別): Structured Parse Results.
                                                             (line   65)
* degrees() (於 math 模組中):            Angular conversion. (line    6)
* degrees() (於 turtle 模組中):          Settings for measurement.
                                                             (line    6)
* Del (ast 中的類別):                    變數.               (line   10)
* DEL (於 curses.ascii 模組中):          curses ascii --- ASCII 字元的工具程式.
                                                             (line  124)
* del_param() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  381)
* del_param() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  541)
* delay_output() (於 curses 模組中):     函式<5>.            (line   85)
* delay() (於 turtle 模組中):            Animation control.  (line    6)
* delayload (http.cookiejar.FileCookieJar 的屬性): CookieJar 與 FileCookieJar 物件.
                                                             (line  159)
* delch() (curses.window 的方法):        Window Objects.     (line  176)
* dele() (poplib.POP3 的方法):           POP3 物件.          (line   68)
* Delete (ast 中的類別):                 陳述式.             (line  133)
* DELETE_ATTR (opcode):                  Python Bytecode Instructions.
                                                             (line  606)
* DELETE_DEREF (opcode):                 Python Bytecode Instructions.
                                                             (line  976)
* DELETE_FAST (opcode):                  Python Bytecode Instructions.
                                                             (line  938)
* DELETE_GLOBAL (opcode):                Python Bytecode Instructions.
                                                             (line  620)
* DELETE_NAME (opcode):                  Python Bytecode Instructions.
                                                             (line  560)
* DELETE_SUBSCR (opcode):                Python Bytecode Instructions.
                                                             (line  262)
* delete() (ftplib.FTP 的方法):          FTP 物件.           (line  287)
* delete() (imaplib.IMAP4 的方法):       IMAP4 物件.         (line   76)
* delete() (tkinter.ttk.Treeview 的方法): ttk Treeview.      (line   73)
* deleteacl() (imaplib.IMAP4 的方法):    IMAP4 物件.         (line   80)
* deletefilehandler() (_tkinter.Widget.tk 的方法): File Handlers.
                                                             (line   37)
* DeleteKey() (於 winreg 模組中):        函式<12>.           (line  102)
* DeleteKeyEx() (於 winreg 模組中):      函式<12>.           (line  124)
* deleteln() (curses.window 的方法):     Window Objects.     (line  180)
* deleteMe() (bdb.Breakpoint 的方法):    bdb --- 偵錯器框架. (line   41)
* DeleteValue() (於 winreg 模組中):      函式<12>.           (line  160)
* deletion（刪除）;target:               del 陳述式<2>.      (line    6)
* deletion（刪除）;target;list（串列）:  del 陳述式<2>.      (line    6)
* delimiter (csv.Dialect 的屬性):        Dialect 與格式參數. (line   16)
* delimiters（分隔符號）:                Delimiters.         (line    6)
* delitem() (於 operator 模組中):        operator --- 標準運算子替代函式.
                                                             (line  178)
* deliver_challenge() (於 multiprocessing.connection 模組中): Listeners and Clients.
                                                             (line   15)
* delocalize() (於 locale 模組中):       locale --- 國際化服務.
                                                             (line  483)
* demo_app() (於 wsgiref.simple_server 模組中): wsgiref simple_server -- 一個簡單的 WSGI HTTP 伺服器.
                                                             (line   33)
* denominator (fractions.Fraction 的屬性): fractions --- 有理數.
                                                             (line  117)
* denominator (numbers.Rational 的屬性): 數值的階層.         (line   50)
* deprecated() (於 warnings 模組中):     Available Functions.
                                                             (line  135)
* DeprecationWarning:                    警告.               (line   17)
* deque (collections 中的類別):          deque 物件.         (line    6)
* Deque (typing 中的類別):               collections 中型別的別名.
                                                             (line   46)
* dequeue() (logging.handlers.QueueListener 的方法): QueueListener.
                                                             (line   49)
* DER_cert_to_PEM_cert() (於 ssl 模組中): 認證處理.          (line   48)
* derive() (BaseExceptionGroup 的方法):  例外群組.           (line   67)
* derwin() (curses.window 的方法):       Window Objects.     (line  185)
* descrgetfunc (C type):                 Slot Type typedefs. (line   69)
* description (inspect.Parameter.kind 的屬性): Introspecting callables with the Signature object.
                                                             (line  283)
* description (sqlite3.Cursor 的屬性):   Cursor 物件.        (line  189)
* descriptor（描述器）:                  術語表.             (line  301)
* descrsetfunc (C type):                 Slot Type typedefs. (line   74)
* deserialize() (sqlite3.Connection 的方法): Connection 物件.
                                                             (line  694)
* dest (optparse.Option 的屬性):         Option attributes.  (line   35)
* destructor (C type):                   Slot Type typedefs. (line   24)
* destructor（解構函式）:                Basic customization.
                                                             (line   55)
* destructor（解構函式） <1>:            Assignment statements.
                                                             (line   71)
* detach() (io.BufferedIOBase 的方法):   I/O 基礎類別.       (line  225)
* detach() (io.TextIOBase 的方法):       文字 I/O<2>.        (line   37)
* detach() (socket.socket 的方法):       Socket 物件.        (line  100)
* detach() (tkinter.ttk.Treeview 的方法): ttk Treeview.      (line   79)
* detach() (weakref.finalize 的方法):    weakref --- 弱參照. (line  244)
* Detach() (winreg.PyHKEY 的方法):       Registry Handle Objects.
                                                             (line   40)
* DETACHED_PROCESS (於 subprocess 模組中): Windows Constants.
                                                             (line  122)
* detect_api_mismatch() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  635)
* detect_encoding() (於 tokenize 模組中): Tokenizing Input.  (line   77)
* deterministic profiling:               Introduction to the profilers.
                                                             (line    6)
* dev_mode (sys.flags 的屬性):           sys --- 系統特定的參數與函式.
                                                             (line  561)
* device_encoding() (於 os 模組中):      File Descriptor Operations.
                                                             (line   81)
* devmajor (tarfile.TarInfo 的屬性):     TarInfo 物件.       (line  141)
* devminor (tarfile.TarInfo 的屬性):     TarInfo 物件.       (line  145)
* devnull (於 os 模組中):                Miscellaneous System Information.
                                                             (line  159)
* DEVNULL (於 subprocess 模組中):        Using the subprocess Module.
                                                             (line  141)
* devpoll() (於 select 模組中):          select --- 等待 I/O 完成.
                                                             (line   36)
* DevpollSelector (selectors 中的類別):  Classes<3>.         (line  184)
* dgettext() (於 gettext 模組中):        GNU gettext API.    (line   39)
* dgettext() (於 locale 模組中):         Access to message catalogs.
                                                             (line    8)
* Dialect (csv 中的類別):                模組內容<3>.        (line  167)
* dialect (csv.csvreader 的屬性):        讀取器物件.         (line   18)
* dialect (csv.csvwriter 的屬性):        寫入器物件.         (line   29)
* Dialog (tkinter.commondialog 中的類別): tkinter commondialog --- Dialog window templates.
                                                             (line   14)
* Dialog (tkinter.simpledialog 中的類別): tkinter simpledialog --- 標準 Tkinter 輸入對話框.
                                                             (line   21)
* Dict (ast 中的類別):                   文本 Literals.      (line   99)
* Dict (typing 中的類別):                內建型別的別名.     (line    6)
* dict (內建類別):                       Mapping Types --- dict.
                                                             (line   19)
* DICT_MERGE (opcode):                   Python Bytecode Instructions.
                                                             (line  732)
* DICT_UPDATE (opcode):                  Python Bytecode Instructions.
                                                             (line  721)
* dict() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  221)
* DictComp (ast 中的類別):               綜合運算式 comprehensions.
                                                             (line    6)
* dictConfig() (於 logging.config 模組中): Configuration functions.
                                                             (line   13)
* dictionary comprehension（字典綜合運算）: 術語表.          (line  321)
* dictionary view（字典檢視）:           術語表.             (line  328)
* dictionary（字典）:                    術語表.             (line  315)
* dictionary（字典）;comprehensions:     Dictionary displays.
                                                             (line    6)
* dictionary（字典）;display:            Dictionary displays.
                                                             (line    6)
* DictReader (csv 中的類別):             模組內容<3>.        (line   93)
* DictWriter (csv 中的類別):             模組內容<3>.        (line  134)
* diff_bytes() (於 difflib 模組中):      difflib --- 計算差異的輔助工具.
                                                             (line  337)
* diff_files (filecmp.dircmp 的屬性):    The dircmp class.   (line   93)
* Differ (difflib 中的類別):             difflib --- 計算差異的輔助工具.
                                                             (line   50)
* difference_update() (frozenset 的方法): Set Types --- set frozenset.
                                                             (line  182)
* difference() (frozenset 的方法):       Set Types --- set frozenset.
                                                             (line  109)
* dig (sys.float_info 的屬性):           sys --- 系統特定的參數與函式.
                                                             (line  619)
* digest_size (hmac.HMAC 的屬性):        hmac --- 基於金鑰雜湊的訊息驗證.
                                                             (line   78)
* digest() (hashlib.hash 的方法):        雜湊物件.           (line   33)
* digest() (hashlib.shake 的方法):       SHAKE 可變長度摘要. (line   14)
* digest() (hmac.HMAC 的方法):           hmac --- 基於金鑰雜湊的訊息驗證.
                                                             (line   49)
* digest() (於 hmac 模組中):             hmac --- 基於金鑰雜湊的訊息驗證.
                                                             (line   27)
* digit() (於 unicodedata 模組中):       unicodedata --- Unicode 資料庫.
                                                             (line   37)
* digits (於 string 模組中):             字串常數.           (line   23)
* dir() (ftplib.FTP 的方法):             FTP 物件.           (line  271)
* dircmp (filecmp 中的類別):             The dircmp class.   (line    6)
* Directory (tkinter.filedialog 中的類別): Native Load/Save Dialogs.
                                                             (line   71)
* directory（目錄）;changing（改變）:    Files and Directories.
                                                             (line  118)
* directory（目錄）;creating（建立）:    Files and Directories.
                                                             (line  535)
* directory（目錄）;deleting（刪除）:    Directory and files operations.
                                                             (line  266)
* directory（目錄）;deleting（刪除） <1>: Files and Directories.
                                                             (line  722)
* directory（目錄）;traversal（遍歷）:   Files and Directories.
                                                             (line 1626)
* directory（目錄）;traversal（遍歷） <1>: Files and Directories.
                                                             (line 1726)
* directory（目錄）;walking:             Files and Directories.
                                                             (line 1626)
* directory（目錄）;walking <1>:         Files and Directories.
                                                             (line 1726)
* DirEntry (os 中的類別):                Files and Directories.
                                                             (line  900)
* dirname() (於 os.path 模組中):         os path --- 常見的路徑名操作.
                                                             (line   91)
* dirs_double_event() (tkinter.filedialog.FileDialog 的方法): Native Load/Save Dialogs.
                                                             (line   86)
* dirs_select_event() (tkinter.filedialog.FileDialog 的方法): Native Load/Save Dialogs.
                                                             (line   90)
* DirsOnSysPath (test.support.import_helper 中的類別): test support import_helper --- 用於 import 測試的工具.
                                                             (line   95)
* DIRTYPE (於 tarfile 模組中):           tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  288)
* dis 命令列選項; -C:                    Command-line interface.
                                                             (line   17)
* dis 命令列選項; -h:                    Command-line interface.
                                                             (line   13)
* dis 命令列選項; -help:                 Command-line interface.
                                                             (line   13)
* dis 命令列選項; -O:                    Command-line interface.
                                                             (line   21)
* dis 命令列選項; -show-caches:          Command-line interface.
                                                             (line   17)
* dis 命令列選項; -show-offsets:         Command-line interface.
                                                             (line   21)
* dis() (dis.Bytecode 的方法):           Bytecode analysis.  (line   57)
* dis() (於 dis 模組中):                 Analysis functions. (line   40)
* dis() (於 pickletools 模組中):         程式化介面.         (line    6)
* disable (pdb command):                 Debugger Commands.  (line  133)
* DISABLE (於 sys.monitoring 模組中):    停用事件.           (line    6)
* disable_faulthandler() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  349)
* disable_gc() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  361)
* disable_interspersed_args() (optparse.OptionParser 的方法): Querying and manipulating your option parser.
                                                             (line   10)
* disable() (bdb.Breakpoint 的方法):     bdb --- 偵錯器框架. (line   51)
* disable() (profile.Profile 的方法):    profile and cProfile Module Reference.
                                                             (line   82)
* disable() (於 faulthandler 模組中):    Fault handler state.
                                                             (line   26)
* disable() (於 gc 模組中):              gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line   23)
* disable() (於 logging 模組中):         Module-Level Functions.
                                                             (line  105)
* disabled (logging.Logger 的屬性):      Logger 物件.        (line   95)
* DisableReflectionKey() (於 winreg 模組中): 函式<12>.       (line  481)
* disassemble() (於 dis 模組中):         Analysis functions. (line   97)
* discard (http.cookiejar.Cookie 的屬性): Cookie 物件<2>.    (line   58)
* discard() (frozenset 的方法):          Set Types --- set frozenset.
                                                             (line  204)
* discard() (mailbox.Mailbox 的方法):    Mailbox 物件.       (line   76)
* discard() (mailbox.MH 的方法):         MH 物件.            (line   79)
* discover() (unittest.TestLoader 的方法): Loading and running tests.
                                                             (line  117)
* disk_usage() (於 shutil 模組中):       Directory and files operations.
                                                             (line  370)
* dispatch_call() (bdb.Bdb 的方法):      bdb --- 偵錯器框架. (line  209)
* dispatch_exception() (bdb.Bdb 的方法): bdb --- 偵錯器框架. (line  229)
* dispatch_line() (bdb.Bdb 的方法):      bdb --- 偵錯器框架. (line  199)
* dispatch_return() (bdb.Bdb 的方法):    bdb --- 偵錯器框架. (line  219)
* dispatch_table (pickle.Pickler 的屬性): 模組介面.          (line  179)
* DISPLAY:                               Tkinter Modules.    (line   27)
* display (pdb command):                 Debugger Commands.  (line  291)
* display_name (email.headerregistry.Address 的屬性): email headerregistry：自訂標頭物件.
                                                             (line  425)
* display_name (email.headerregistry.Group 的屬性): email headerregistry：自訂標頭物件.
                                                             (line  469)
* displayhook() (於 sys 模組中):         sys --- 系統特定的參數與函式.
                                                             (line  294)
* dist() (於 math 模組中):               Trigonometric functions.
                                                             (line   35)
* distance() (於 turtle 模組中):         Tell Turtle's state.
                                                             (line   68)
* Div (ast 中的類別):                    運算式<2>.          (line   52)
* divide_int() (decimal.Context 的方法): Context objects.    (line  294)
* divide() (decimal.Context 的方法):     Context objects.    (line  290)
* division（除）:                        Binary arithmetic operations.
                                                             (line   34)
* DivisionByZero (decimal 中的類別):     Signals.            (line   33)
* divmod() (decimal.Context 的方法):     Context objects.    (line  298)
* DLE (於 curses.ascii 模組中):          curses ascii --- ASCII 字元的工具程式.
                                                             (line   73)
* DllCanUnloadNow() (於 ctypes 模組中):  Utility functions.  (line   75)
* DllGetClassObject() (於 ctypes 模組中): Utility functions. (line   81)
* dllhandle (於 sys 模組中):             sys --- 系統特定的參數與函式.
                                                             (line  288)
* dnd_start() (於 tkinter.dnd 模組中):   tkinter dnd --- 拖放支援.
                                                             (line   65)
* DndHandler (tkinter.dnd 中的類別):     tkinter dnd --- 拖放支援.
                                                             (line   43)
* dngettext() (於 gettext 模組中):       GNU gettext API.    (line   58)
* dnpgettext() (於 gettext 模組中):      GNU gettext API.    (line   69)
* do_clear() (bdb.Bdb 的方法):           bdb --- 偵錯器框架. (line  292)
* do_command() (curses.textpad.Textbox 的方法): Textbox objects.
                                                             (line   30)
* do_GET() (http.server.SimpleHTTPRequestHandler 的方法): http server — HTTP 伺服器.
                                                             (line  383)
* do_handshake() (ssl.SSLSocket 的方法): SSL Sockets.        (line  112)
* do_HEAD() (http.server.SimpleHTTPRequestHandler 的方法): http server — HTTP 伺服器.
                                                             (line  376)
* do_help() (cmd.Cmd 的方法):            Cmd 物件.           (line   49)
* do_POST() (http.server.CGIHTTPRequestHandler 的方法): http server — HTTP 伺服器.
                                                             (line  510)
* doc (json.JSONDecodeError 的屬性):     例外<12>.           (line   14)
* doc_header (cmd.Cmd 的屬性):           Cmd 物件.           (line  155)
* DocCGIXMLRPCRequestHandler (xmlrpc.server 中的類別): Documenting XMLRPC server.
                                                             (line   22)
* DocFileSuite() (於 doctest 模組中):    Unittest API.       (line   24)
* doClassCleanups() (unittest.TestCase 的類別方法): Test cases.
                                                             (line  827)
* doCleanups() (unittest.TestCase 的方法): Test cases.       (line  785)
* docmd() (smtplib.SMTP 的方法):         SMTP 物件.          (line   17)
* docstring (doctest.DocTest 的屬性):    DocTest 物件.       (line   49)
* docstring（說明字串）:                 類別定義.           (line    6)
* docstring（說明字串） <1>:             術語表.             (line  336)
* docstrings（說明字串）:                定義函式 function.  (line   20)
* docstrings（說明字串） <1>:            說明文件字串 Documentation Strings.
                                                             (line    6)
* DocTest (doctest 中的類別):            DocTest 物件.       (line    6)
* DocTestFailure:                        Debugging.          (line  186)
* DocTestFinder (doctest 中的類別):      DocTestFinder 物件. (line    6)
* DocTestParser (doctest 中的類別):      DocTestParser 物件. (line    6)
* DocTestRunner (doctest 中的類別):      DocTestRunner 物件. (line    6)
* DocTestSuite() (於 doctest 模組中):    Unittest API.       (line  100)
* doctype() (xml.etree.ElementTree.TreeBuilder 的方法): TreeBuilder 物件.
                                                             (line   67)
* documentation string（文件字串）:      特殊唯讀屬性<2>.    (line   98)
* documentation（文件）;generation（產生）: pydoc --- 文件產生器與線上幫助系統.
                                                             (line    8)
* documentation（文件）;online（線上）:  pydoc --- 文件產生器與線上幫助系統.
                                                             (line    8)
* documentElement (xml.dom.Document 的屬性): Document Objects.
                                                             (line   10)
* DocXMLRPCRequestHandler (xmlrpc.server 中的類別): Documenting XMLRPC server.
                                                             (line   27)
* DocXMLRPCServer (xmlrpc.server 中的類別): Documenting XMLRPC server.
                                                             (line   11)
* domain (email.headerregistry.Address 的屬性): email headerregistry：自訂標頭物件.
                                                             (line  436)
* domain (http.cookiejar.Cookie 的屬性): Cookie 物件<2>.     (line   41)
* domain (http.cookies.Morsel 的屬性):   Morsel 物件.        (line   13)
* domain (tracemalloc.DomainFilter 的屬性): DomainFilter.    (line   20)
* domain (tracemalloc.Filter 的屬性):    Filter.             (line   31)
* domain (tracemalloc.Trace 的屬性):     Trace.              (line   15)
* domain_initial_dot (http.cookiejar.Cookie 的屬性): Cookie 物件<2>.
                                                             (line   90)
* domain_return_ok() (http.cookiejar.CookiePolicy 的方法): CookiePolicy 物件.
                                                             (line   27)
* domain_specified (http.cookiejar.Cookie 的屬性): Cookie 物件<2>.
                                                             (line   86)
* DomainFilter (tracemalloc 中的類別):   DomainFilter.       (line    6)
* DomainLiberal (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy 物件.
                                                             (line  156)
* DomainRFC2965Match (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy 物件.
                                                             (line  149)
* DomainStrict (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy 物件.
                                                             (line  161)
* DomainStrictNoDots (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy 物件.
                                                             (line  136)
* DomainStrictNonDomain (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy 物件.
                                                             (line  142)
* DOMEventStream (xml.dom.pulldom 中的類別): DOMEventStream 物件.
                                                             (line    6)
* DOMException:                          例外<15>.           (line   18)
* doModuleCleanups() (於 unittest 模組中): setUpModule and tearDownModule.
                                                             (line   44)
* DomstringSizeErr:                      例外<15>.           (line   23)
* done() (asyncio.Future 的方法):        Future 物件<2>.     (line   57)
* done() (asyncio.Task 的方法):          Task Object.        (line   66)
* done() (concurrent.futures.Future 的方法): Future 物件.    (line   27)
* done() (graphlib.TopologicalSorter 的方法): graphlib —-- 使用類圖 graph-like 結構進行操作的功能.
                                                             (line  117)
* done() (於 turtle 模組中):             Using screen events.
                                                             (line  106)
* DONT_ACCEPT_BLANKLINE (於 doctest 模組中): 可選旗標.       (line   30)
* DONT_ACCEPT_TRUE_FOR_1 (於 doctest 模組中): 可選旗標.      (line   18)
* dont_write_bytecode (sys.flags 的屬性): sys --- 系統特定的參數與函式.
                                                             (line  537)
* dont_write_bytecode (於 sys 模組中):   sys --- 系統特定的參數與函式.
                                                             (line  330)
* doRollover() (logging.handlers.RotatingFileHandler 的方法): RotatingFileHandler.
                                                             (line   43)
* doRollover() (logging.handlers.TimedRotatingFileHandler 的方法): TimedRotatingFileHandler.
                                                             (line  106)
* DOT (於 token 模組中):                 token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  118)
* dot() (於 turtle 模組中):              Turtle motion.      (line  252)
* DOTALL (於 re 模組中):                 旗標.               (line  107)
* doublequote (csv.Dialect 的屬性):      Dialect 與格式參數. (line   20)
* DOUBLESLASH (於 token 模組中):         token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  214)
* DOUBLESLASHEQUAL (於 token 模組中):    token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  218)
* DOUBLESTAR (於 token 模組中):          token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  166)
* DOUBLESTAREQUAL (於 token 模組中):     token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  210)
* doupdate() (於 curses 模組中):         函式<5>.            (line   89)
* down (pdb command):                    Debugger Commands.  (line   87)
* down() (於 turtle 模組中):             Drawing state.      (line    6)
* dpgettext() (於 gettext 模組中):       GNU gettext API.    (line   65)
* drain() (asyncio.StreamWriter 的方法): StreamWriter.       (line   61)
* drive (pathlib.PurePath 的屬性):       方法與屬性.         (line   15)
* drop_whitespace (textwrap.TextWrapper 的屬性): textwrap --- 文字包裝與填充.
                                                             (line  201)
* dropwhile() (於 itertools 模組中):     Itertool 函式.      (line  243)
* dst() (datetime.datetime 的方法):      datetime 物件.      (line  532)
* dst() (datetime.time 的方法):          time 物件.          (line  246)
* dst() (datetime.timezone 的方法):      timezone 物件.      (line   57)
* dst() (datetime.tzinfo 的方法):        tzinfo 物件.        (line   65)
* DTDHandler (xml.sax.handler 中的類別): xml sax handler --- SAX 處理函式的基本類別.
                                                             (line   24)
* duck-typing（鴨子型別）:               術語表.             (line  343)
* dump_stats() (profile.Profile 的方法): profile and cProfile Module Reference.
                                                             (line  104)
* dump_stats() (pstats.Stats 的方法):    The Stats Class.    (line   59)
* dump_traceback_later() (於 faulthandler 模組中): Dumping the tracebacks after a timeout.
                                                             (line    6)
* dump_traceback() (於 faulthandler 模組中): Dumping the traceback.
                                                             (line    6)
* dump() (pickle.Pickler 的方法):        模組介面.           (line  155)
* dump() (tracemalloc.Snapshot 的方法):  Snapshot.           (line   29)
* dump() (於 ast 模組中):                ast 輔助程式.       (line  233)
* dump() (於 json 模組中):               基本用法<2>.        (line    6)
* dump() (於 marshal 模組中):            marshal --- 内部 Python 物件序列化.
                                                             (line   49)
* dump() (於 pickle 模組中):             模組介面.           (line   35)
* dump() (於 plistlib 模組中):           plistlib --- 產生和剖析 Apple plist 檔案.
                                                             (line   93)
* dump() (於 xml.etree.ElementTree 模組中): 函式<8>.         (line   86)
* dumps() (於 json 模組中):              基本用法<2>.        (line   70)
* dumps() (於 marshal 模組中):           marshal --- 内部 Python 物件序列化.
                                                             (line   88)
* dumps() (於 pickle 模組中):            模組介面.           (line   47)
* dumps() (於 plistlib 模組中):          plistlib --- 產生和剖析 Apple plist 檔案.
                                                             (line  130)
* dumps() (於 xmlrpc.client 模組中):     便捷的函式.         (line    6)
* dup() (socket.socket 的方法):          Socket 物件.        (line  108)
* dup() (於 os 模組中):                  File Descriptor Operations.
                                                             (line   93)
* dup2() (於 os 模組中):                 File Descriptor Operations.
                                                             (line  106)
* DuplicateOptionError:                  例外<5>.            (line   24)
* DuplicateSectionError:                 例外<5>.            (line   14)
* dwFlags (subprocess.STARTUPINFO 的屬性): Windows Popen Helpers.
                                                             (line   19)
* DynamicClassAttribute() (於 types 模組中): Additional Utility Classes and Functions.
                                                             (line   55)
* e (於 cmath 模組中):                   常數<3>.            (line   10)
* e (於 math 模組中):                    常數<2>.            (line   11)
* e;於數值常數中:                        Integer literals.   (line   40)
* E2BIG (於 errno 模組中):               errno --- 標準 errno 系統符號.
                                                             (line   54)
* EACCES (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line   80)
* EADDRINUSE (於 errno 模組中):          errno --- 標準 errno 系統符號.
                                                             (line  432)
* EADDRNOTAVAIL (於 errno 模組中):       errno --- 標準 errno 系統符號.
                                                             (line  436)
* EADV (於 errno 模組中):                errno --- 標準 errno 系統符號.
                                                             (line  306)
* EAFNOSUPPORT (於 errno 模組中):        errno --- 標準 errno 系統符號.
                                                             (line  428)
* EAFP:                                  術語表.             (line  355)
* EAGAIN (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line   71)
* eager_task_factory() (於 asyncio 模組中): Eager Task Factory.
                                                             (line    6)
* EALREADY (於 errno 模組中):            errno --- 標準 errno 系統符號.
                                                             (line  501)
* east_asian_width() (於 unicodedata 模組中): unicodedata --- Unicode 資料庫.
                                                             (line   64)
* EBADE (於 errno 模組中):               errno --- 標準 errno 系統符號.
                                                             (line  242)
* EBADF (於 errno 模組中):               errno --- 標準 errno 系統符號.
                                                             (line   62)
* EBADFD (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  342)
* EBADMSG (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line  330)
* EBADR (於 errno 模組中):               errno --- 標準 errno 系統符號.
                                                             (line  246)
* EBADRQC (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line  258)
* EBADSLT (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line  262)
* EBFONT (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  270)
* EBUSY (於 errno 模組中):               errno --- 標準 errno 系統符號.
                                                             (line   93)
* ECANCELED (於 errno 模組中):           errno --- 標準 errno 系統符號.
                                                             (line  554)
* ECHILD (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line   66)
* echo() (於 curses 模組中):             函式<5>.            (line  105)
* echochar() (curses.window 的方法):     Window Objects.     (line  195)
* ECHRNG (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  210)
* ECOMM (於 errno 模組中):               errno --- 標準 errno 系統符號.
                                                             (line  314)
* ECONNABORTED (於 errno 模組中):        errno --- 標準 errno 系統符號.
                                                             (line  452)
* ECONNREFUSED (於 errno 模組中):        errno --- 標準 errno 系統符號.
                                                             (line  488)
* ECONNRESET (於 errno 模組中):          errno --- 標準 errno 系統符號.
                                                             (line  457)
* EDEADLK (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line  173)
* EDEADLOCK (於 errno 模組中):           errno --- 標準 errno 系統符號.
                                                             (line  266)
* EDESTADDRREQ (於 errno 模組中):        errno --- 標準 errno 系統符號.
                                                             (line  390)
* edit() (curses.textpad.Textbox 的方法): Textbox objects.   (line   19)
* EDOM (於 errno 模組中):                errno --- 標準 errno 系統符號.
                                                             (line  165)
* EDOTDOT (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line  326)
* EDQUOT (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  535)
* EEXIST (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line   97)
* EFAULT (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line   85)
* EFBIG (於 errno 模組中):               errno --- 標準 errno 系統符號.
                                                             (line  140)
* EFD_CLOEXEC (於 os 模組中):            Files and Directories.
                                                             (line 1900)
* EFD_NONBLOCK (於 os 模組中):           Files and Directories.
                                                             (line 1909)
* EFD_SEMAPHORE (於 os 模組中):          Files and Directories.
                                                             (line 1918)
* effective() (於 bdb 模組中):           bdb --- 偵錯器框架. (line  464)
* ehlo_or_helo_if_needed() (smtplib.SMTP 的方法): SMTP 物件. (line   75)
* ehlo() (smtplib.SMTP 的方法):          SMTP 物件.          (line   58)
* EHOSTDOWN (於 errno 模組中):           errno --- 標準 errno 系統符號.
                                                             (line  493)
* EHOSTUNREACH (於 errno 模組中):        errno --- 標準 errno 系統符號.
                                                             (line  497)
* EIDRM (於 errno 模組中):               errno --- 標準 errno 系統符號.
                                                             (line  206)
* EILSEQ (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  370)
* EINPROGRESS (於 errno 模組中):         errno --- 標準 errno 系統符號.
                                                             (line  506)
* EINTR (於 errno 模組中):               errno --- 標準 errno 系統符號.
                                                             (line   41)
* EINVAL (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  120)
* EIO (於 errno 模組中):                 errno --- 標準 errno 系統符號.
                                                             (line   46)
* EISCONN (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line  466)
* EISDIR (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  115)
* EISNAM (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  527)
* EJECT (enum.FlagBoundary 的屬性):      資料型別<2>.        (line  651)
* EL2HLT (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  238)
* EL2NSYNC (於 errno 模組中):            errno --- 標準 errno 系統符號.
                                                             (line  214)
* EL3HLT (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  218)
* EL3RST (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  222)
* Element (xml.etree.ElementTree 中的類別): Element 物件.    (line    6)
* element_create() (tkinter.ttk.Style 的方法): Ttk Styling.  (line  131)
* element_names() (tkinter.ttk.Style 的方法): Ttk Styling.   (line  252)
* element_options() (tkinter.ttk.Style 的方法): Ttk Styling. (line  256)
* ElementDeclHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line  240)
* elements() (collections.Counter 的方法): Counter 物件.     (line   60)
* ElementTree (xml.etree.ElementTree 中的類別): ElementTree 物件.
                                                             (line    6)
* ELIBACC (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line  350)
* ELIBBAD (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line  354)
* ELIBEXEC (於 errno 模組中):            errno --- 標準 errno 系統符號.
                                                             (line  366)
* ELIBMAX (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line  362)
* ELIBSCN (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line  358)
* Ellipsis (內建變數):                   內建常數.           (line   53)
* ELLIPSIS (於 doctest 模組中):          可選旗標.           (line   49)
* ELLIPSIS (於 token 模組中):            token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  234)
* EllipsisType (於 types 模組中):        Standard Interpreter Types.
                                                             (line  187)
* ELNRNG (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  226)
* ELOOP (於 errno 模組中):               errno --- 標準 errno 系統符號.
                                                             (line  193)
* else;conditional expression（條件運算式）: Conditional expressions.
                                                             (line    6)
* EM (於 curses.ascii 模組中):           curses ascii --- ASCII 字元的工具程式.
                                                             (line  100)
* EmailMessage (email.message 中的類別): email message：表示電子郵件訊息.
                                                             (line   52)
* EmailPolicy (email.policy 中的類別):   email policy Policy Objects.
                                                             (line  360)
* EMFILE (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  128)
* emit() (logging.FileHandler 的方法):   FileHandler.        (line   31)
* emit() (logging.Handler 的方法):       Handler Objects.    (line  107)
* emit() (logging.handlers.BufferingHandler 的方法): MemoryHandler.
                                                             (line   24)
* emit() (logging.handlers.DatagramHandler 的方法): DatagramHandler.
                                                             (line   29)
* emit() (logging.handlers.HTTPHandler 的方法): HTTPHandler. (line   36)
* emit() (logging.handlers.NTEventLogHandler 的方法): NTEventLogHandler.
                                                             (line   38)
* emit() (logging.handlers.QueueHandler 的方法): QueueHandler.
                                                             (line   35)
* emit() (logging.handlers.RotatingFileHandler 的方法): RotatingFileHandler.
                                                             (line   47)
* emit() (logging.handlers.SMTPHandler 的方法): SMTPHandler. (line   35)
* emit() (logging.handlers.SocketHandler 的方法): SocketHandler.
                                                             (line   24)
* emit() (logging.handlers.SysLogHandler 的方法): SysLogHandler.
                                                             (line   61)
* emit() (logging.handlers.TimedRotatingFileHandler 的方法): TimedRotatingFileHandler.
                                                             (line  110)
* emit() (logging.handlers.WatchedFileHandler 的方法): WatchedFileHandler.
                                                             (line   50)
* emit() (logging.NullHandler 的方法):   NullHandler.        (line   16)
* emit() (logging.StreamHandler 的方法): StreamHandler.      (line   17)
* EMLINK (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  156)
* Empty:                                 queue --- 同步佇列 synchronized queue 類別.
                                                             (line   67)
* empty (inspect.Parameter 的屬性):      Introspecting callables with the Signature object.
                                                             (line  200)
* empty (inspect.Signature 的屬性):      Introspecting callables with the Signature object.
                                                             (line  100)
* EMPTY_NAMESPACE (於 xml.dom 模組中):   模組內容<6>.        (line   35)
* empty;list（串列）:                    List displays.      (line    6)
* empty;tuple:                           Parenthesized forms.
                                                             (line   16)
* empty() (asyncio.Queue 的方法):        Queue.              (line   25)
* empty() (multiprocessing.Queue 的方法): Pipes and Queues.  (line  116)
* empty() (multiprocessing.SimpleQueue 的方法): Pipes and Queues.
                                                             (line  229)
* empty() (queue.Queue 的方法):          佇列物件.           (line   14)
* empty() (queue.SimpleQueue 的方法):    SimpleQueue 物件.   (line   13)
* empty() (sched.scheduler 的方法):      排程器物件.         (line   41)
* empty（空的）;tuple（元組）:           Immutable sequences.
                                                             (line   29)
* emptyline() (cmd.Cmd 的方法):          Cmd 物件.           (line   70)
* emscripten_version (sys._emscripten_info 的屬性): sys --- 系統特定的參數與函式.
                                                             (line  344)
* EMSGSIZE (於 errno 模組中):            errno --- 標準 errno 系統符號.
                                                             (line  394)
* EMULTIHOP (於 errno 模組中):           errno --- 標準 errno 系統符號.
                                                             (line  322)
* enable (pdb command):                  Debugger Commands.  (line  140)
* enable_callback_tracebacks() (於 sqlite3 模組中): Module functions.
                                                             (line  127)
* enable_interspersed_args() (optparse.OptionParser 的方法): Querying and manipulating your option parser.
                                                             (line   31)
* enable_load_extension() (sqlite3.Connection 的方法): Connection 物件.
                                                             (line  424)
* enable_traversal() (tkinter.ttk.Notebook 的方法): ttk Notebook.
                                                             (line   73)
* ENABLE_USER_SITE (於 site 模組中):     模組內容<10>.       (line   10)
* enable() (bdb.Breakpoint 的方法):      bdb --- 偵錯器框架. (line   47)
* enable() (imaplib.IMAP4 的方法):       IMAP4 物件.         (line   84)
* enable() (profile.Profile 的方法):     profile and cProfile Module Reference.
                                                             (line   78)
* enable() (於 faulthandler 模組中):     Fault handler state.
                                                             (line    6)
* enable() (於 gc 模組中):               gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line   19)
* EnableControlFlowGuard:                Build<28>.          (line   47)
* enabled (bdb.Breakpoint 的屬性):       bdb --- 偵錯器框架. (line  105)
* EnableReflectionKey() (於 winreg 模組中): 函式<12>.        (line  499)
* ENAMETOOLONG (於 errno 模組中):        errno --- 標準 errno 系統符號.
                                                             (line  177)
* ENAVAIL (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line  523)
* enclose() (curses.window 的方法):      Window Objects.     (line  200)
* encode (codecs.CodecInfo 的屬性):      codecs --- 編解碼器註冊表和基底類別.
                                                             (line   69)
* encode_7or8bit() (於 email.encoders 模組中): email encoders：編碼器.
                                                             (line   49)
* encode_base64() (於 email.encoders 模組中): email encoders：編碼器.
                                                             (line   42)
* encode_noop() (於 email.encoders 模組中): email encoders：編碼器.
                                                             (line   54)
* encode_quopri() (於 email.encoders 模組中): email encoders：編碼器.
                                                             (line   35)
* encode_rfc2231() (於 email.utils 模組中): email utils：雜項工具.
                                                             (line  191)
* encode() (codecs.Codec 的方法):        Stateless Encoding and Decoding.
                                                             (line   11)
* encode() (codecs.IncrementalEncoder 的方法): IncrementalEncoder 物件.
                                                             (line   28)
* encode() (email.header.Header 的方法): email header：國際化標頭.
                                                             (line  125)
* encode() (json.JSONEncoder 的方法):    編碼器與解碼器.     (line  199)
* encode() (str 的方法):                 String Methods<2>.  (line   64)
* encode() (xmlrpc.client.Binary 的方法): Binary Objects.    (line   25)
* encode() (xmlrpc.client.DateTime 的方法): 日期時間物件.    (line   17)
* encode() (於 base64 模組中):           base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  236)
* encode() (於 codecs 模組中):           codecs --- 編解碼器註冊表和基底類別.
                                                             (line   23)
* encode() (於 quopri 模組中):           quopri --- 編碼和解碼 MIME 可列印字元資料.
                                                             (line   24)
* encodebytes() (於 base64 模組中):      base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  245)
* EncodedFile() (於 codecs 模組中):      codecs --- 編解碼器註冊表和基底類別.
                                                             (line  202)
* encodePriority() (logging.handlers.SysLogHandler 的方法): SysLogHandler.
                                                             (line   95)
* encodestring() (於 quopri 模組中):     quopri --- 編碼和解碼 MIME 可列印字元資料.
                                                             (line   39)
* encoding (curses.window 的屬性):       Window Objects.     (line  210)
* encoding (io.TextIOBase 的屬性):       文字 I/O<2>.        (line   15)
* encoding (UnicodeError 的屬性):        實體例外.           (line  368)
* ENCODING (於 tarfile 模組中):          tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  262)
* ENCODING (於 token 模組中):            token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  284)
* encoding declarations (source file)（編碼宣告（原始檔案））: Encoding declarations.
                                                             (line    6)
* encodings_map (mimetypes.MimeTypes 的屬性): MimeTypes 物件.
                                                             (line   33)
* encodings_map (於 mimetypes 模組中):   mimetypes --- 將檔案名稱對映到 MIME 類型.
                                                             (line  149)
* EncodingWarning:                       警告.               (line   64)
* end (UnicodeError 的屬性):             實體例外.           (line  384)
* END_ASYNC_FOR (opcode):                Python Bytecode Instructions.
                                                             (line  330)
* end_col_offset (ast.AST 的屬性):       節點 Node 類別.     (line   43)
* end_fill() (於 turtle 模組中):         Filling.            (line   20)
* END_FOR (opcode):                      Python Bytecode Instructions.
                                                             (line  137)
* end_headers() (http.server.BaseHTTPRequestHandler 的方法): http server — HTTP 伺服器.
                                                             (line  273)
* end_lineno (ast.AST 的屬性):           節點 Node 類別.     (line   43)
* end_lineno (SyntaxError 的屬性):       實體例外.           (line  281)
* end_lineno (traceback.TracebackException 的屬性): TracebackException 物件.
                                                             (line   94)
* end_ns() (xml.etree.ElementTree.TreeBuilder 的方法): TreeBuilder 物件.
                                                             (line   86)
* end_offset (SyntaxError 的屬性):       實體例外.           (line  286)
* end_offset (traceback.TracebackException 的屬性): TracebackException 物件.
                                                             (line  110)
* end_poly() (於 turtle 模組中):         Special Turtle methods.
                                                             (line   11)
* END_SEND (opcode):                     Python Bytecode Instructions.
                                                             (line  144)
* end() (re.Match 的方法):               Match Objects.      (line  146)
* end() (xml.etree.ElementTree.TreeBuilder 的方法): TreeBuilder 物件.
                                                             (line   38)
* endCDATA() (xml.sax.handler.LexicalHandler 的方法): LexicalHandler 物件.
                                                             (line   39)
* EndCdataSectionHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line  346)
* EndDoctypeDeclHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line  235)
* endDocument() (xml.sax.handler.ContentHandler 的方法): ContentHandler 物件.
                                                             (line   40)
* endDTD() (xml.sax.handler.LexicalHandler 的方法): LexicalHandler 物件.
                                                             (line   28)
* endElement() (xml.sax.handler.ContentHandler 的方法): ContentHandler 物件.
                                                             (line   95)
* EndElementHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line  270)
* endElementNS() (xml.sax.handler.ContentHandler 的方法): ContentHandler 物件.
                                                             (line  121)
* endheaders() (http.client.HTTPConnection 的方法): HTTPConnection 物件.
                                                             (line  183)
* ENDMARKER (於 token 模組中):           token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   40)
* EndNamespaceDeclHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line  325)
* endpos (re.Match 的屬性):              Match Objects.      (line  185)
* endPrefixMapping() (xml.sax.handler.ContentHandler 的方法): ContentHandler 物件.
                                                             (line   73)
* endswith() (bytearray 的方法):         Bytes and Bytearray Operations.
                                                             (line  120)
* endswith() (bytes 的方法):             Bytes and Bytearray Operations.
                                                             (line  120)
* endswith() (str 的方法):               String Methods<2>.  (line   87)
* endwin() (於 curses 模組中):           函式<5>.            (line  110)
* ENETDOWN (於 errno 模組中):            errno --- 標準 errno 系統符號.
                                                             (line  440)
* ENETRESET (於 errno 模組中):           errno --- 標準 errno 系統符號.
                                                             (line  448)
* ENETUNREACH (於 errno 模組中):         errno --- 標準 errno 系統符號.
                                                             (line  444)
* ENFILE (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  124)
* ENOANO (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  254)
* ENOBUFS (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line  462)
* ENOCSI (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  234)
* ENODATA (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line  278)
* ENODEV (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  106)
* ENOENT (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line   31)
* ENOEXEC (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line   58)
* ENOLCK (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  181)
* ENOLINK (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line  302)
* ENOMEM (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line   76)
* ENOMSG (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  202)
* ENONET (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  290)
* ENOPKG (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  294)
* ENOPROTOOPT (於 errno 模組中):         errno --- 標準 errno 系統符號.
                                                             (line  402)
* ENOSPC (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  144)
* ENOSR (於 errno 模組中):               errno --- 標準 errno 系統符號.
                                                             (line  286)
* ENOSTR (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  274)
* ENOSYS (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  185)
* ENOTBLK (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line   89)
* ENOTCAPABLE (於 errno 模組中):         errno --- 標準 errno 系統符號.
                                                             (line  545)
* ENOTCONN (於 errno 模組中):            errno --- 標準 errno 系統符號.
                                                             (line  470)
* ENOTDIR (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line  110)
* ENOTEMPTY (於 errno 模組中):           errno --- 標準 errno 系統符號.
                                                             (line  189)
* ENOTNAM (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line  519)
* ENOTRECOVERABLE (於 errno 模組中):     errno --- 標準 errno 系統符號.
                                                             (line  566)
* ENOTSOCK (於 errno 模組中):            errno --- 標準 errno 系統符號.
                                                             (line  386)
* ENOTSUP (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line  418)
* ENOTTY (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  132)
* ENOTUNIQ (於 errno 模組中):            errno --- 標準 errno 系統符號.
                                                             (line  338)
* ENQ (於 curses.ascii 模組中):          curses ascii --- ASCII 字元的工具程式.
                                                             (line   34)
* enqueue_sentinel() (logging.handlers.QueueListener 的方法): QueueListener.
                                                             (line   90)
* enqueue() (logging.handlers.QueueHandler 的方法): QueueHandler.
                                                             (line   78)
* ensure_directories() (venv.EnvBuilder 的方法): API<2>.     (line   85)
* ensure_future() (於 asyncio 模組中):   Future 函式.        (line   19)
* enter_async_context() (contextlib.AsyncExitStack 的方法): Utilities.
                                                             (line  631)
* enter_context() (contextlib.ExitStack 的方法): Utilities.  (line  547)
* enter() (sched.scheduler 的方法):      排程器物件.         (line   26)
* enterabs() (sched.scheduler 的方法):   排程器物件.         (line    8)
* enterAsyncContext() (unittest.IsolatedAsyncioTestCase 的方法): Test cases.
                                                             (line  888)
* enterClassContext() (unittest.TestCase 的類別方法): Test cases.
                                                             (line  818)
* enterContext() (unittest.TestCase 的方法): Test cases.     (line  776)
* enterModuleContext() (於 unittest 模組中): setUpModule and tearDownModule.
                                                             (line   35)
* entities (xml.dom.DocumentType 的屬性): DocumentType 物件. (line   38)
* EntityDeclHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line  299)
* entitydefs (於 html.entities 模組中):  html entities --- HTML 一般實體的定義.
                                                             (line   23)
* EntityResolver (xml.sax.handler 中的類別): xml sax handler --- SAX 處理函式的基本類別.
                                                             (line   31)
* Enum (enum 中的類別):                  資料型別<2>.        (line  127)
* enum_certificates() (於 ssl 模組中):   認證處理.           (line   78)
* enum_crls() (於 ssl 模組中):           認證處理.           (line   99)
* EnumCheck (enum 中的類別):             資料型別<2>.        (line  558)
* enumerate() (於 threading 模組中):     threading --- 基於執行緒的平行性.
                                                             (line  142)
* EnumKey() (於 winreg 模組中):          函式<12>.           (line  172)
* EnumType (enum 中的類別):              資料型別<2>.        (line    6)
* EnumValue() (於 winreg 模組中):        函式<12>.           (line  191)
* EnvBuilder (venv 中的類別):            API<2>.             (line   10)
* environ (於 os 模組中):                行程參數.           (line   16)
* environ (於 posix 模組中):             值得注意的模組內容. (line    9)
* environb (於 os 模組中):               行程參數.           (line   58)
* environment variables（環境變數）;deleting（刪除）: 行程參數.
                                                             (line  587)
* environment variables（環境變數）;setting（設定）: 行程參數.
                                                             (line  354)
* environment（環境）:                   Resolution of names.
                                                             (line   12)
* EnvironmentError:                      實體例外.           (line  416)
* Environments （環境）;virtual （虛擬）: venv --- 建立虛擬環境.
                                                             (line   10)
* EnvironmentVarGuard (test.support.os_helper 中的類別): test support os_helper --- 用於 os 測試的工具.
                                                             (line   48)
* ENXIO (於 errno 模組中):               errno --- 標準 errno 系統符號.
                                                             (line   50)
* eof (bz2.BZ2Decompressor 的屬性):      Incremental de compression.
                                                             (line   72)
* eof (lzma.LZMADecompressor 的屬性):    Compressing and decompressing data in memory.
                                                             (line  165)
* eof (shlex.shlex 的屬性):              shlex 物件.         (line  177)
* eof (ssl.MemoryBIO 的屬性):            Memory BIO Support<2>.
                                                             (line  143)
* eof (zlib.Decompress 的屬性):          zlib --- 相容於 gzip 的壓縮.
                                                             (line  201)
* eof_received() (asyncio.BufferedProtocol 的方法): Buffered Streaming Protocols.
                                                             (line   40)
* eof_received() (asyncio.Protocol 的方法): Streaming Protocols.
                                                             (line   30)
* EOFError:                              實體例外.           (line   24)
* EOFError（內建例外）:                  檔案物件 File Objects.
                                                             (line   37)
* EOPNOTSUPP (於 errno 模組中):          errno --- 標準 errno 系統符號.
                                                             (line  414)
* EOT (於 curses.ascii 模組中):          curses ascii --- ASCII 字元的工具程式.
                                                             (line   31)
* EOVERFLOW (於 errno 模組中):           errno --- 標準 errno 系統符號.
                                                             (line  334)
* EOWNERDEAD (於 errno 模組中):          errno --- 標準 errno 系統符號.
                                                             (line  560)
* EPERM (於 errno 模組中):               errno --- 標準 errno 系統符號.
                                                             (line   26)
* EPFNOSUPPORT (於 errno 模組中):        errno --- 標準 errno 系統符號.
                                                             (line  424)
* epilogue (email.message.EmailMessage 的屬性): email message：表示電子郵件訊息.
                                                             (line  701)
* epilogue (email.message.Message 的屬性): email message Message Representing an email message using the compat32 API.
                                                             (line  712)
* EPIPE (於 errno 模組中):               errno --- 標準 errno 系統符號.
                                                             (line  160)
* epoch（紀元）:                         time --- 時間存取與轉換.
                                                             (line   17)
* epoll() (於 select 模組中):            select --- 等待 I/O 完成.
                                                             (line   54)
* EpollSelector (selectors 中的類別):    Classes<3>.         (line  175)
* EPROTO (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  318)
* EPROTONOSUPPORT (於 errno 模組中):     errno --- 標準 errno 系統符號.
                                                             (line  406)
* EPROTOTYPE (於 errno 模組中):          errno --- 標準 errno 系統符號.
                                                             (line  398)
* epsilon (sys.float_info 的屬性):       sys --- 系統特定的參數與函式.
                                                             (line  612)
* Eq (ast 中的類別):                     運算式<2>.          (line  105)
* eq() (於 operator 模組中):             operator --- 標準運算子替代函式.
                                                             (line   20)
* EQEQUAL (於 token 模組中):             token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  134)
* EQFULL (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  539)
* EQUAL (於 token 模組中):               token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  114)
* ERA (於 locale 模組中):                locale --- 國際化服務.
                                                             (line  299)
* ERA_D_FMT (於 locale 模組中):          locale --- 國際化服務.
                                                             (line  321)
* ERA_D_T_FMT (於 locale 模組中):        locale --- 國際化服務.
                                                             (line  316)
* ERA_T_FMT (於 locale 模組中):          locale --- 國際化服務.
                                                             (line  326)
* ERANGE (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  169)
* erase() (curses.window 的方法):        Window Objects.     (line  220)
* erasechar() (於 curses 模組中):        函式<5>.            (line  114)
* EREMCHG (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line  346)
* EREMOTE (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line  298)
* EREMOTEIO (於 errno 模組中):           errno --- 標準 errno 系統符號.
                                                             (line  531)
* ERESTART (於 errno 模組中):            errno --- 標準 errno 系統符號.
                                                             (line  374)
* erf() (於 math 模組中):                Special functions.  (line    6)
* erfc() (於 math 模組中):               Special functions.  (line   20)
* EROFS (於 errno 模組中):               errno --- 標準 errno 系統符號.
                                                             (line  152)
* ERR (於 curses 模組中):                Constants.          (line    8)
* errcheck (ctypes._FuncPtr 的屬性):     Foreign functions.  (line   60)
* errcode (xmlrpc.client.ProtocolError 的屬性): ProtocolError 物件.
                                                             (line   17)
* errmsg (xmlrpc.client.ProtocolError 的屬性): ProtocolError 物件.
                                                             (line   21)
* errno (OSError 的屬性):                實體例外.           (line  138)
* error:                                 函式與例外.         (line    8)
* Error:                                 copy --- 淺層 shallow 和深層 deep 複製操作.
                                                             (line   32)
* Error <1>:                             Directory and files operations.
                                                             (line  462)
* error <1>:                             dbm --- Unix "databases" 的介面.
                                                             (line   29)
* error <2>:                             dbm gnu --- GNU 資料庫管理器.
                                                             (line   17)
* error <3>:                             dbm ndbm --- 新資料庫管理器.
                                                             (line   23)
* error <4>:                             dbm dumb --- 可攜式 DBM 實作.
                                                             (line   23)
* Error <2>:                             例外<4>.            (line   15)
* error <5>:                             zlib --- 相容於 gzip 的壓縮.
                                                             (line   21)
* Error <3>:                             模組內容<3>.        (line  289)
* Error <4>:                             例外<5>.            (line    6)
* error <6>:                             os --- 各種作業系統介面.
                                                             (line   44)
* error <7>:                             函式<5>.            (line    8)
* error <8>:                             _thread --- 低階執行緒 API.
                                                             (line   18)
* error <9>:                             例外<10>.           (line    6)
* error <10>:                            select --- 等待 I/O 完成.
                                                             (line   29)
* Error <5>:                             例外<13>.           (line    8)
* Error <6>:                             binascii --- 在二進位制和 ASCII 之間轉換.
                                                             (line  156)
* error <11>:                            xml parsers expat --- 使用 Expat 進行快速 XML 剖析.
                                                             (line   31)
* Error <7>:                             webbrowser --- 方便的網頁瀏覽器控制器.
                                                             (line   62)
* Error <8>:                             wave --- 讀寫 WAV 檔案.
                                                             (line   47)
* Error <9>:                             locale --- 國際化服務.
                                                             (line   22)
* error <12>:                            resource --- 資源使用資訊.
                                                             (line   19)
* error <13>:                            getopt --- 用於命令列選項的 C 風格剖析器.
                                                             (line   89)
* ERROR (於 logging 模組中):             Logging Levels.     (line   40)
* ERROR (於 tkinter.messagebox 模組中):  tkinter messagebox --- Tkinter 訊息提示.
                                                             (line  170)
* error handling（錯誤處理）:            例外.               (line    6)
* error_body (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  219)
* error_content_type (http.server.BaseHTTPRequestHandler 的屬性): http server — HTTP 伺服器.
                                                             (line  157)
* error_headers (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  213)
* error_leader() (shlex.shlex 的方法):   shlex 物件.         (line   69)
* error_message_format (http.server.BaseHTTPRequestHandler 的屬性): http server — HTTP 伺服器.
                                                             (line  149)
* error_output() (wsgiref.handlers.BaseHandler 的方法): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  191)
* error_perm:                            模組變數.           (line   15)
* error_proto:                           模組變數.           (line   20)
* error_proto <1>:                       poplib --- POP3 協定用戶端.
                                                             (line   87)
* error_received() (asyncio.DatagramProtocol 的方法): Datagram Protocols.
                                                             (line   15)
* error_reply:                           模組變數.           (line    6)
* error_status (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  208)
* error_temp:                            模組變數.           (line   10)
* error() (argparse.ArgumentParser 的方法): Exiting methods. (line   18)
* error() (logging.Logger 的方法):       Logger 物件.        (line  299)
* error() (urllib.request.OpenerDirector 的方法): OpenerDirector 物件.
                                                             (line   54)
* error() (xml.sax.handler.ErrorHandler 的方法): ErrorHandler 物件.
                                                             (line   16)
* error() (於 logging 模組中):           Module-Level Functions.
                                                             (line   80)
* ErrorByteIndex (xml.parsers.expat.xmlparser 的屬性): XMLParser 物件<2>.
                                                             (line  170)
* ErrorCode (xml.parsers.expat.xmlparser 的屬性): XMLParser 物件<2>.
                                                             (line  174)
* errorcode (於 errno 模組中):           errno --- 標準 errno 系統符號.
                                                             (line   13)
* ErrorColumnNumber (xml.parsers.expat.xmlparser 的屬性): XMLParser 物件<2>.
                                                             (line  180)
* ErrorHandler (xml.sax.handler 中的類別): xml sax handler --- SAX 處理函式的基本類別.
                                                             (line   38)
* errorlevel (tarfile.TarFile 的屬性):   TarFile 物件.       (line  221)
* ErrorLineNumber (xml.parsers.expat.xmlparser 的屬性): XMLParser 物件<2>.
                                                             (line  184)
* errors (io.TextIOBase 的屬性):         文字 I/O<2>.        (line   20)
* errors (unittest.TestLoader 的屬性):   Loading and running tests.
                                                             (line   17)
* errors (unittest.TestResult 的屬性):   Loading and running tests.
                                                             (line  246)
* errors（錯誤）:                        例外.               (line    6)
* Errors（錯誤）;logging（日誌）:        logging --- Python 的日誌記錄工具.
                                                             (line    8)
* ErrorStream (wsgiref.types 中的類別):  wsgiref types -- 用於靜態型別檢查的 WSGI 型別.
                                                             (line   27)
* ErrorString() (於 xml.parsers.expat 模組中): xml parsers expat --- 使用 Expat 進行快速 XML 剖析.
                                                             (line   42)
* ERRORTOKEN (於 token 模組中):          token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  264)
* ESC (於 curses.ascii 模組中):          curses ascii --- ASCII 字元的工具程式.
                                                             (line  106)
* escape (shlex.shlex 的屬性):           shlex 物件.         (line  110)
* escape sequence（跳脫序列）:           String and Bytes literals.
                                                             (line   74)
* escape() (於 glob 模組中):             glob --- Unix 風格的路徑名稱模式擴展.
                                                             (line   91)
* escape() (於 html 模組中):             html --- 超連結標記語言 HTML 支援.
                                                             (line   12)
* escape() (於 re 模組中):               Functions.          (line  255)
* escape() (於 xml.sax.saxutils 模組中): xml sax saxutils --- SAX 工具程式.
                                                             (line   14)
* escapechar (csv.Dialect 的屬性):       Dialect 與格式參數. (line   30)
* escapedquotes (shlex.shlex 的屬性):    shlex 物件.         (line  122)
* ESHUTDOWN (於 errno 模組中):           errno --- 標準 errno 系統符號.
                                                             (line  474)
* ESOCKTNOSUPPORT (於 errno 模組中):     errno --- 標準 errno 系統符號.
                                                             (line  410)
* ESPIPE (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  148)
* ESRCH (於 errno 模組中):               errno --- 標準 errno 系統符號.
                                                             (line   36)
* ESRMNT (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  310)
* ESTALE (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  511)
* ESTRPIPE (於 errno 模組中):            errno --- 標準 errno 系統符號.
                                                             (line  378)
* ETB (於 curses.ascii 模組中):          curses ascii --- ASCII 字元的工具程式.
                                                             (line   94)
* ETH_P_ALL (於 socket 模組中):          常數<7>.            (line  218)
* ETHERTYPE_ARP (於 socket 模組中):      常數<7>.            (line  361)
* ETHERTYPE_IP (於 socket 模組中):       常數<7>.            (line  361)
* ETHERTYPE_IPV6 (於 socket 模組中):     常數<7>.            (line  361)
* ETHERTYPE_VLAN (於 socket 模組中):     常數<7>.            (line  361)
* ETIME (於 errno 模組中):               errno --- 標準 errno 系統符號.
                                                             (line  282)
* ETIMEDOUT (於 errno 模組中):           errno --- 標準 errno 系統符號.
                                                             (line  483)
* Etiny() (decimal.Context 的方法):      Context objects.    (line  232)
* ETOOMANYREFS (於 errno 模組中):        errno --- 標準 errno 系統符號.
                                                             (line  479)
* Etop() (decimal.Context 的方法):       Context objects.    (line  238)
* ETX (於 curses.ascii 模組中):          curses ascii --- ASCII 字元的工具程式.
                                                             (line   28)
* ETXTBSY (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line  136)
* EUCLEAN (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line  515)
* EUNATCH (於 errno 模組中):             errno --- 標準 errno 系統符號.
                                                             (line  230)
* EUSERS (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  382)
* evaluation;order（順序）:              Evaluation order.   (line    6)
* Event (asyncio 中的類別):              Event.              (line    6)
* Event (multiprocessing 中的類別):      Synchronization primitives.
                                                             (line   41)
* Event (threading 中的類別):            Event Objects.      (line   14)
* event scheduling（事件排程）:          sched --- 事件排程器.
                                                             (line    8)
* EVENT_READ (於 selectors 模組中):      Classes<3>.         (line   23)
* EVENT_WRITE (於 selectors 模組中):     Classes<3>.         (line   26)
* Event() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  182)
* eventfd_read() (於 os 模組中):         Files and Directories.
                                                             (line 1880)
* eventfd_write() (於 os 模組中):        Files and Directories.
                                                             (line 1890)
* eventfd() (於 os 模組中):              Files and Directories.
                                                             (line 1827)
* EventLoop (asyncio 中的類別):          事件迴圈實作.       (line   43)
* events (selectors.SelectorKey 的屬性): Classes<3>.         (line   44)
* events (widgets):                      Bindings and Events.
                                                             (line    6)
* EWOULDBLOCK (於 errno 模組中):         errno --- 標準 errno 系統符號.
                                                             (line  197)
* EX_CANTCREAT (於 os 模組中):           行程管理.           (line  206)
* EX_CONFIG (於 os 模組中):              行程管理.           (line  242)
* EX_DATAERR (於 os 模組中):             行程管理.           (line  155)
* EX_IOERR (於 os 模組中):               行程管理.           (line  213)
* EX_NOHOST (於 os 模組中):              行程管理.           (line  174)
* EX_NOINPUT (於 os 模組中):             行程管理.           (line  161)
* EX_NOPERM (於 os 模組中):              行程管理.           (line  235)
* EX_NOTFOUND (於 os 模組中):            行程管理.           (line  249)
* EX_NOUSER (於 os 模組中):              行程管理.           (line  168)
* EX_OK (於 os 模組中):                  行程管理.           (line  140)
* EX_OSERR (於 os 模組中):               行程管理.           (line  192)
* EX_OSFILE (於 os 模組中):              行程管理.           (line  199)
* EX_PROTOCOL (於 os 模組中):            行程管理.           (line  228)
* EX_SOFTWARE (於 os 模組中):            行程管理.           (line  186)
* EX_TEMPFAIL (於 os 模組中):            行程管理.           (line  220)
* EX_UNAVAILABLE (於 os 模組中):         行程管理.           (line  180)
* EX_USAGE (於 os 模組中):               行程管理.           (line  148)
* Example (doctest 中的類別):            Example 物件.       (line    6)
* example (doctest.DocTestFailure 的屬性): Debugging.        (line  200)
* example (doctest.UnexpectedException 的屬性): Debugging.   (line  221)
* examples (doctest.DocTest 的屬性):     DocTest 物件.       (line   17)
* exc_info (doctest.UnexpectedException 的屬性): Debugging.  (line  225)
* exc_info （sys 模組中）:               Traceback objects.  (line    6)
* exc_info （sys 模組中） <1>:           例外<17>.           (line   33)
* exc_info() (於 sys 模組中):            sys --- 系統特定的參數與函式.
                                                             (line  443)
* exc_msg (doctest.Example 的屬性):      Example 物件.       (line   31)
* exc_type (traceback.TracebackException 的屬性): TracebackException 物件.
                                                             (line   74)
* exc_type_str (traceback.TracebackException 的屬性): TracebackException 物件.
                                                             (line   80)
* excel (csv 中的類別):                  模組內容<3>.        (line  185)
* excel_tab (csv 中的類別):              模組內容<3>.        (line  190)
* ExceptHandler (ast 中的類別):          流程控制.           (line  193)
* excepthook() (於 sys 模組中):          sys --- 系統特定的參數與函式.
                                                             (line  387)
* excepthook() (於 threading 模組中):    threading --- 基於執行緒的平行性.
                                                             (line   70)
* Exception:                             基底類別 base classes.
                                                             (line   56)
* EXCEPTION (於 _tkinter 模組中):        File Handlers.      (line   41)
* exception handler（例外處理器）:       例外.               (line    6)
* EXCEPTION_HANDLED (monitoring event):  事件.               (line   26)
* exception;AttributeError:              Attribute references.
                                                             (line   10)
* exception;GeneratorExit:               Generator-iterator methods.
                                                             (line   64)
* exception;GeneratorExit <1>:           Asynchronous generator-iterator methods.
                                                             (line   60)
* exception;NameError:                   Identifiers Names.  (line   10)
* exception;StopAsyncIteration:          Asynchronous generator-iterator methods.
                                                             (line   10)
* exception;StopIteration:               Generator-iterator methods.
                                                             (line   12)
* exception;TypeError:                   Unary arithmetic and bitwise operations.
                                                             (line   23)
* exception;ValueError:                  Shifting operations.
                                                             (line   20)
* exception;ZeroDivisionError:           Binary arithmetic operations.
                                                             (line   34)
* exception() (asyncio.Future 的方法):   Future 物件<2>.     (line  114)
* exception() (asyncio.Task 的方法):     Task Object.        (line   87)
* exception() (concurrent.futures.Future 的方法): Future 物件.
                                                             (line   43)
* exception() (logging.Logger 的方法):   Logger 物件.        (line  315)
* exception() (於 logging 模組中):       Module-Level Functions.
                                                             (line   92)
* exception() (於 sys 模組中):           sys --- 系統特定的參數與函式.
                                                             (line  431)
* exception（例外）:                     例外.               (line    6)
* exception（例外） <1>:                 raise 陳述式.       (line    6)
* exception（例外）;AssertionError:      assert 陳述式.      (line   21)
* exception（例外）;chaining:            例外的情境.         (line    6)
* exception（例外）;chaining（鏈結）:    raise 陳述式.       (line   30)
* exception（例外）;handler（處理器）:   Traceback objects.  (line    6)
* exception（例外）;ImportError:         import 陳述式.      (line    6)
* exception（例外）;StopIteration:       yield 陳述式.       (line    6)
* ExceptionGroup:                        例外群組.           (line   10)
* exceptions (BaseExceptionGroup 的屬性): 例外群組.          (line   32)
* exceptions (pdb command):              Debugger Commands.  (line  439)
* exceptions (traceback.TracebackException 的屬性): TracebackException 物件.
                                                             (line   48)
* EXCLAMATION (於 token 模組中):         token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  242)
* exclusive（排外）;or:                  Binary bitwise operations.
                                                             (line   16)
* EXDEV (於 errno 模組中):               errno --- 標準 errno 系統符號.
                                                             (line  102)
* exec_module() (importlib.abc.InspectLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  286)
* exec_module() (importlib.abc.Loader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  114)
* exec_module() (importlib.abc.SourceLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  431)
* exec_module() (importlib.machinery.ExtensionFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  315)
* exec_module() (zipimport.zipimporter 的方法): zipimporter 物件.
                                                             (line   31)
* exec_prefix (於 sys 模組中):           sys --- 系統特定的參數與函式.
                                                             (line  462)
* execl() (於 os 模組中):                行程管理.           (line   53)
* execle() (於 os 模組中):               行程管理.           (line   53)
* execlp() (於 os 模組中):               行程管理.           (line   53)
* execlpe() (於 os 模組中):              行程管理.           (line   53)
* executable (於 sys 模組中):            sys --- 系統特定的參數與函式.
                                                             (line  479)
* Executable Zip Files（可執行的 Zip 檔案）: zipapp —-- 管理可執行的 Python zip 封存檔案.
                                                             (line   10)
* executable（sys 模組中）:              Process-wide parameters.
                                                             (line  115)
* execute() (sqlite3.Connection 的方法): Connection 物件.    (line   97)
* execute() (sqlite3.Cursor 的方法):     Cursor 物件.        (line   24)
* executemany() (sqlite3.Connection 的方法): Connection 物件.
                                                             (line  103)
* executemany() (sqlite3.Cursor 的方法): Cursor 物件.        (line   59)
* executescript() (sqlite3.Connection 的方法): Connection 物件.
                                                             (line  109)
* executescript() (sqlite3.Cursor 的方法): Cursor 物件.      (line  100)
* execution model（執行模型）:           執行模型.           (line    6)
* execution（執行）;frame:               Structure of a program.
                                                             (line   18)
* execution（執行）;frame <1>:           類別定義.           (line    6)
* execution（執行）;stack（堆疊）:       Traceback objects.  (line    6)
* ExecutionLoader (importlib.abc 中的類別): importlib abc -- Abstract base classes related to import.
                                                             (line  298)
* Executor (concurrent.futures 中的類別): Executor 物件.     (line    6)
* execv() (於 os 模組中):                行程管理.           (line   53)
* execve() (於 os 模組中):               行程管理.           (line   53)
* execvp() (於 os 模組中):               行程管理.           (line   53)
* execvpe() (於 os 模組中):              行程管理.           (line   53)
* EXFULL (於 errno 模組中):              errno --- 標準 errno 系統符號.
                                                             (line  250)
* exists() (pathlib.Path 的方法):        Querying file type and status.
                                                             (line   33)
* exists() (tkinter.ttk.Treeview 的方法): ttk Treeview.      (line   89)
* exists() (zipfile.Path 的方法):        Path Objects.       (line   64)
* exists() (於 os.path 模組中):          os path --- 常見的路徑名操作.
                                                             (line   98)
* exit (內建變數):                       由 site module（模組）所添增的常數.
                                                             (line   11)
* exit() (argparse.ArgumentParser 的方法): Exiting methods.  (line    6)
* exit() (於 _thread 模組中):            _thread --- 低階執行緒 API.
                                                             (line   65)
* exit() (於 sys 模組中):                sys --- 系統特定的參數與函式.
                                                             (line  486)
* exit（C 函式）:                        行程控制.           (line   23)
* exitcode (multiprocessing.Process 的屬性): Process 與例外. (line  126)
* exitonclick() (於 turtle 模組中):      Methods specific to Screen not inherited from TurtleScreen.
                                                             (line   10)
* ExitStack (contextlib 中的類別):       Utilities.          (line  504)
* exp() (decimal.Context 的方法):        Context objects.    (line  303)
* exp() (decimal.Decimal 的方法):        Decimal objects.    (line  231)
* exp() (於 cmath 模組中):               冪函數和對數函數.   (line    6)
* exp() (於 math 模組中):                Power and logarithmic functions.
                                                             (line   12)
* exp2() (於 math 模組中):               Power and logarithmic functions.
                                                             (line   18)
* expand_tabs (textwrap.TextWrapper 的屬性): textwrap --- 文字包裝與填充.
                                                             (line  167)
* expand() (re.Match 的方法):            Match Objects.      (line   22)
* ExpandEnvironmentStrings() (於 winreg 模組中): 函式<12>.   (line  228)
* expandNode() (xml.dom.pulldom.DOMEventStream 的方法): DOMEventStream 物件.
                                                             (line   21)
* expandtabs() (bytearray 的方法):       Bytes and Bytearray Operations.
                                                             (line  480)
* expandtabs() (bytes 的方法):           Bytes and Bytearray Operations.
                                                             (line  480)
* expandtabs() (str 的方法):             String Methods<2>.  (line   94)
* expanduser() (pathlib.Path 的方法):    Expanding and resolving paths.
                                                             (line   17)
* expanduser() (於 os.path 模組中):      os path --- 常見的路徑名操作.
                                                             (line  118)
* expandvars() (於 os.path 模組中):      os path --- 常見的路徑名操作.
                                                             (line  140)
* Expat:                                 xml parsers expat --- 使用 Expat 進行快速 XML 剖析.
                                                             (line   12)
* ExpatError:                            xml parsers expat --- 使用 Expat 進行快速 XML 剖析.
                                                             (line   25)
* expected (asyncio.IncompleteReadError 的屬性): 例外<8>.    (line   47)
* expectedFailure() (於 unittest 模組中): Skipping tests and expected failures.
                                                             (line   98)
* expectedFailures (unittest.TestResult 的屬性): Loading and running tests.
                                                             (line  266)
* expired() (asyncio.Timeout 的方法):    Timeouts.           (line   72)
* expires (http.cookiejar.Cookie 的屬性): Cookie 物件<2>.    (line   53)
* expires (http.cookies.Morsel 的屬性):  Morsel 物件.        (line   13)
* exploded (ipaddress.IPv4Address 的屬性): Address objects.  (line   60)
* exploded (ipaddress.IPv4Network 的屬性): Network objects.  (line  109)
* exploded (ipaddress.IPv6Address 的屬性): Address objects.  (line  248)
* exploded (ipaddress.IPv6Network 的屬性): Network objects.  (line  321)
* expm1() (於 math 模組中):              Power and logarithmic functions.
                                                             (line   24)
* expovariate() (於 random 模組中):      實數分布.           (line   32)
* Expr (ast 中的類別):                   運算式<2>.          (line    6)
* expression:                            運算式.             (line    6)
* Expression (ast 中的類別):             根節點.             (line   24)
* expression;list（串列）:               Expression lists.   (line    6)
* expression;list（串列） <1>:           Expression statements.
                                                             (line    6)
* expression;list（串列） <2>:           Expression statements.
                                                             (line    6)
* expression;statement（陳述式）:        Expression statements.
                                                             (line    6)
* expression（運算式）:                  術語表.             (line  363)
* expunge() (imaplib.IMAP4 的方法):      IMAP4 物件.         (line   93)
* extend_path() (於 pkgutil 模組中):     pkgutil --- 套件擴充工具程式.
                                                             (line   18)
* extend() (array.array 的方法):         array --- 高效率的數值型陣列.
                                                             (line  140)
* extend() (collections.deque 的方法):   deque 物件.         (line   53)
* extend() (xml.etree.ElementTree.Element 的方法): Element 物件.
                                                             (line   93)
* extend()（序列方法）:                  Mutable Sequence Types.
                                                             (line   16)
* EXTENDED_ARG (opcode):                 Python Bytecode Instructions.
                                                             (line 1131)
* ExtendedContext (decimal 中的類別):    Context objects.    (line   76)
* ExtendedInterpolation (configparser 中的類別): Interpolation of values.
                                                             (line   41)
* extendleft() (collections.deque 的方法): deque 物件.       (line   57)
* extension module（擴充模組）:          術語表.             (line  371)
* EXTENSION_SUFFIXES (於 importlib.machinery 模組中): importlib machinery -- Importers and path hooks.
                                                             (line   47)
* extension（擴充）;module（模組）:      標準型別階層.       (line    6)
* ExtensionFileLoader (importlib.machinery 中的類別): importlib machinery -- Importers and path hooks.
                                                             (line  282)
* extensions_map (http.server.SimpleHTTPRequestHandler 的屬性): http server — HTTP 伺服器.
                                                             (line  363)
* External Data Representation（外部資料表示法）: Data stream format.
                                                             (line    6)
* external_attr (zipfile.ZipInfo 的屬性): ZipInfo 物件.      (line  127)
* ExternalClashError:                    例外<13>.           (line   24)
* ExternalEntityParserCreate() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line   44)
* ExternalEntityRefHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line  373)
* extra (zipfile.ZipInfo 的屬性):        ZipInfo 物件.       (line   93)
* extract_cookies() (http.cookiejar.CookieJar 的方法): CookieJar 與 FileCookieJar 物件.
                                                             (line   31)
* extract_stack() (於 traceback 模組中): traceback --- 列印或取得堆疊回溯 stack traceback.
                                                             (line  121)
* extract_tb() (於 traceback 模組中):    traceback --- 列印或取得堆疊回溯 stack traceback.
                                                             (line  109)
* extract_version (zipfile.ZipInfo 的屬性): ZipInfo 物件.    (line  107)
* extract() (tarfile.TarFile 的方法):    TarFile 物件.       (line  174)
* extract() (traceback.StackSummary 的類別方法): StackSummary 物件.
                                                             (line   12)
* extract() (zipfile.ZipFile 的方法):    ZipFile 物件.       (line  184)
* extractall() (tarfile.TarFile 的方法): TarFile 物件.       (line  137)
* extractall() (zipfile.ZipFile 的方法): ZipFile 物件.       (line  211)
* ExtractError:                          tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  217)
* extractfile() (tarfile.TarFile 的方法): TarFile 物件.      (line  207)
* extraction_filter (tarfile.TarFile 的屬性): TarFile 物件.  (line  241)
* extsep (於 os 模組中):                 Miscellaneous System Information.
                                                             (line  132)
* f_back （frame 屬性）:                 Frame objects.      (line   10)
* f_back (frame 的屬性):                 特殊唯讀屬性<3>.    (line    6)
* f_builtins （frame 屬性）:             Frame objects.      (line   10)
* f_builtins (frame 的屬性):             特殊唯讀屬性<3>.    (line   29)
* f_code （frame 屬性）:                 Frame objects.      (line   10)
* f_code (frame 的屬性):                 特殊唯讀屬性<3>.    (line   10)
* F_CONTIGUOUS (inspect.BufferFlags 的屬性): Buffer flags.   (line   27)
* f_contiguous (memoryview 的屬性):      Memory Views.       (line  479)
* f_globals （frame 屬性）:              Frame objects.      (line   10)
* f_globals (frame 的屬性):              特殊唯讀屬性<3>.    (line   25)
* f_lasti （frame 屬性）:                Frame objects.      (line   10)
* f_lasti (frame 的屬性):                特殊唯讀屬性<3>.    (line   33)
* f_lineno （frame 屬性）:               特殊唯讀屬性<3>.    (line   37)
* f_lineno (frame 的屬性):               特殊可寫屬性<2>.    (line   23)
* f_locals （frame 屬性）:               Frame objects.      (line   10)
* f_locals (frame 的屬性):               特殊唯讀屬性<3>.    (line   16)
* F_LOCK (於 os 模組中):                 File Descriptor Operations.
                                                             (line  279)
* F_OK (於 os 模組中):                   Files and Directories.
                                                             (line  107)
* F_TEST (於 os 模組中):                 File Descriptor Operations.
                                                             (line  279)
* F_TLOCK (於 os 模組中):                File Descriptor Operations.
                                                             (line  279)
* f_trace （frame 屬性）:                特殊唯讀屬性<3>.    (line   38)
* f_trace (frame 的屬性):                特殊可寫屬性<2>.    (line    6)
* f_trace_lines （frame 屬性）:          特殊唯讀屬性<3>.    (line   38)
* f_trace_lines (frame 的屬性):          特殊可寫屬性<2>.    (line   12)
* f_trace_opcodes （frame 屬性）:        特殊唯讀屬性<3>.    (line   38)
* f_trace_opcodes (frame 的屬性):        特殊可寫屬性<2>.    (line   16)
* F_ULOCK (於 os 模組中):                File Descriptor Operations.
                                                             (line  279)
* f-string（f 字串）:                    String literal concatenation.
                                                             (line   24)
* f-string（f 字串） <1>:                術語表.             (line  376)
* f';formatted string literal（格式化字串常數）: String and Bytes literals.
                                                             (line   64)
* f";formatted string literal（格式化字串常數）: String and Bytes literals.
                                                             (line   64)
* fabs() (於 math 模組中):               數論與表現函式.     (line   31)
* factorial() (於 math 模組中):          數論與表現函式.     (line   35)
* factory() (importlib.util.LazyLoader 的類別方法): importlib util -- Utility code for importers.
                                                             (line  222)
* FAIL_FAST (於 doctest 模組中):         可選旗標.           (line  140)
* fail() (unittest.TestCase 的方法):     Test cases.         (line  679)
* failed (doctest.TestResults 的屬性):   TestResults objects.
                                                             (line    8)
* failfast (unittest.TestResult 的屬性): Loading and running tests.
                                                             (line  304)
* failureException:                      Unittest API.       (line  142)
* failureException (unittest.TestCase 的屬性): Test cases.   (line  684)
* failures (doctest.DocTestRunner 的屬性): DocTestRunner 物件.
                                                             (line  138)
* failures (unittest.TestResult 的屬性): Loading and running tests.
                                                             (line  252)
* FakePath (test.support.os_helper 中的類別): test support os_helper --- 用於 os 測試的工具.
                                                             (line   59)
* False:                                 numbers Integral.   (line   27)
* false:                                 真值檢測.           (line    6)
* False <1>:                             真值檢測.           (line   20)
* False <2>:                             Boolean 型別 - bool.
                                                             (line    9)
* False (內建變數):                      內建常數.           (line    8)
* False（內建物件）:                     真值檢測.           (line   14)
* families() (於 tkinter.font 模組中):   tkinter font --- Tkinter 字型包裝器.
                                                             (line   85)
* family (socket.socket 的屬性):         Socket 物件.        (line  616)
* FancyURLopener (urllib.request 中的類別): Legacy interface.
                                                             (line  145)
* fast (pickle.Pickler 的屬性):          模組介面.           (line  218)
* FastChildWatcher (asyncio 中的類別):   Process Watchers.   (line  142)
* fatalError() (xml.sax.handler.ErrorHandler 的方法): ErrorHandler 物件.
                                                             (line   24)
* Fault (xmlrpc.client 中的類別):        Fault Objects.      (line    6)
* faultCode (xmlrpc.client.Fault 的屬性): Fault Objects.     (line   11)
* faultString (xmlrpc.client.Fault 的屬性): Fault Objects.   (line   15)
* fchdir() (於 os 模組中):               Files and Directories.
                                                             (line  277)
* fchmod() (於 os 模組中):               File Descriptor Operations.
                                                             (line  120)
* fchown() (於 os 模組中):               File Descriptor Operations.
                                                             (line  136)
* fcntl() (於 fcntl 模組中):             fcntl --- fcntl 和 ioctl 系統呼叫.
                                                             (line   67)
* fd (selectors.SelectorKey 的屬性):     Classes<3>.         (line   40)
* fd_count() (於 test.support.os_helper 模組中): test support os_helper --- 用於 os 測試的工具.
                                                             (line   96)
* fd() (於 turtle 模組中):               Turtle motion.      (line    6)
* fdatasync() (於 os 模組中):            File Descriptor Operations.
                                                             (line  151)
* fdopen() (於 os 模組中):               File Object Creation.
                                                             (line    9)
* feature_external_ges (於 xml.sax.handler 模組中): xml sax handler --- SAX 處理函式的基本類別.
                                                             (line   81)
* feature_external_pes (於 xml.sax.handler 模組中): xml sax handler --- SAX 處理函式的基本類別.
                                                             (line   88)
* feature_namespace_prefixes (於 xml.sax.handler 模組中): xml sax handler --- SAX 處理函式的基本類別.
                                                             (line   60)
* feature_namespaces (於 xml.sax.handler 模組中): xml sax handler --- SAX 處理函式的基本類別.
                                                             (line   53)
* feature_string_interning (於 xml.sax.handler 模組中): xml sax handler --- SAX 處理函式的基本類別.
                                                             (line   67)
* feature_validation (於 xml.sax.handler 模組中): xml sax handler --- SAX 處理函式的基本類別.
                                                             (line   74)
* FEBRUARY (於 calendar 模組中):         calendar --- 日曆相關函式.
                                                             (line  365)
* feed_eof() (asyncio.StreamReader 的方法): StreamReader.    (line   15)
* feed() (email.parser.BytesFeedParser 的方法): FeedParser API.
                                                             (line   56)
* feed() (html.parser.HTMLParser 的方法): HTMLParser 方法.   (line    8)
* feed() (xml.etree.ElementTree.XMLParser 的方法): XMLParser 物件.
                                                             (line   27)
* feed() (xml.etree.ElementTree.XMLPullParser 的方法): XMLPullParser 物件.
                                                             (line   18)
* feed() (xml.sax.xmlreader.IncrementalParser 的方法): IncrementalParser 物件.
                                                             (line    9)
* FeedParser (email.parser 中的類別):    FeedParser API.     (line   71)
* fetch() (imaplib.IMAP4 的方法):        IMAP4 物件.         (line   99)
* fetchall() (sqlite3.Cursor 的方法):    Cursor 物件.        (line  146)
* fetchmany() (sqlite3.Cursor 的方法):   Cursor 物件.        (line  129)
* fetchone() (sqlite3.Cursor 的方法):    Cursor 物件.        (line  122)
* FF (於 curses.ascii 模組中):           curses ascii --- ASCII 字元的工具程式.
                                                             (line   61)
* fflags (select.kevent 的屬性):         Kevent Objects.     (line   90)
* Field (dataclasses 中的類別):          模組內容<8>.        (line  302)
* field_size_limit() (於 csv 模組中):    模組內容<3>.        (line   86)
* field() (於 dataclasses 模組中):       模組內容<8>.        (line  208)
* fieldnames (csv.DictReader 的屬性):    讀取器物件.         (line   29)
* fields (uuid.UUID 的屬性):             uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line   89)
* fields() (於 dataclasses 模組中):      模組內容<8>.        (line  321)
* FIFOTYPE (於 tarfile 模組中):          tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  292)
* file (bdb.Breakpoint 的屬性):          bdb --- 偵錯器框架. (line   81)
* file (pyclbr.Class 的屬性):            Class Objects.      (line   12)
* file (pyclbr.Function 的屬性):         函式物件.           (line   11)
* file object（檔案物件）:               術語表.             (line  381)
* file object（檔案物件）;io 模組:       總覽.               (line    6)
* file object（檔案物件）;open() 內建函式: 內建函式.         (line 1130)
* FILE_ATTRIBUTE_ARCHIVE (於 stat 模組中): stat --- 直譯 stat 的結果.
                                                             (line  452)
* FILE_ATTRIBUTE_COMPRESSED (於 stat 模組中): stat --- 直譯 stat 的結果.
                                                             (line  452)
* FILE_ATTRIBUTE_DEVICE (於 stat 模組中): stat --- 直譯 stat 的結果.
                                                             (line  452)
* FILE_ATTRIBUTE_DIRECTORY (於 stat 模組中): stat --- 直譯 stat 的結果.
                                                             (line  452)
* FILE_ATTRIBUTE_ENCRYPTED (於 stat 模組中): stat --- 直譯 stat 的結果.
                                                             (line  452)
* FILE_ATTRIBUTE_HIDDEN (於 stat 模組中): stat --- 直譯 stat 的結果.
                                                             (line  452)
* FILE_ATTRIBUTE_INTEGRITY_STREAM (於 stat 模組中): stat --- 直譯 stat 的結果.
                                                             (line  452)
* FILE_ATTRIBUTE_NO_SCRUB_DATA (於 stat 模組中): stat --- 直譯 stat 的結果.
                                                             (line  452)
* FILE_ATTRIBUTE_NORMAL (於 stat 模組中): stat --- 直譯 stat 的結果.
                                                             (line  452)
* FILE_ATTRIBUTE_NOT_CONTENT_INDEXED (於 stat 模組中): stat --- 直譯 stat 的結果.
                                                             (line  452)
* FILE_ATTRIBUTE_OFFLINE (於 stat 模組中): stat --- 直譯 stat 的結果.
                                                             (line  452)
* FILE_ATTRIBUTE_READONLY (於 stat 模組中): stat --- 直譯 stat 的結果.
                                                             (line  452)
* FILE_ATTRIBUTE_REPARSE_POINT (於 stat 模組中): stat --- 直譯 stat 的結果.
                                                             (line  452)
* FILE_ATTRIBUTE_SPARSE_FILE (於 stat 模組中): stat --- 直譯 stat 的結果.
                                                             (line  452)
* FILE_ATTRIBUTE_SYSTEM (於 stat 模組中): stat --- 直譯 stat 的結果.
                                                             (line  452)
* FILE_ATTRIBUTE_TEMPORARY (於 stat 模組中): stat --- 直譯 stat 的結果.
                                                             (line  452)
* FILE_ATTRIBUTE_VIRTUAL (於 stat 模組中): stat --- 直譯 stat 的結果.
                                                             (line  452)
* file_digest() (於 hashlib 模組中):     檔案雜湊.           (line    9)
* file_open() (urllib.request.FileHandler 的方法): FileHandler 物件.
                                                             (line    6)
* file_size (zipfile.ZipInfo 的屬性):    ZipInfo 物件.       (line  143)
* file-like object（類檔案物件）:        術語表.             (line  395)
* file（檔案）;byte-code（位元組碼）:    py_compile — 編譯 Python 來源檔案.
                                                             (line    8)
* file（檔案）;copying（複製）:          shutil — 高階檔案操作.
                                                             (line    8)
* file（檔案）;large files（大型檔案）:  對大檔案 Large File 的支援.
                                                             (line    6)
* file（檔案）;mime.types:               mimetypes --- 將檔案名稱對映到 MIME 類型.
                                                             (line  137)
* file（檔案）;modes（模式）:            內建函式.           (line 1151)
* fileConfig() (於 logging.config 模組中): Configuration functions.
                                                             (line   61)
* FileCookieJar (http.cookiejar 中的類別): http cookiejar --- HTTP 客戶端的 Cookie 處理.
                                                             (line   56)
* FileDialog (tkinter.filedialog 中的類別): Native Load/Save Dialogs.
                                                             (line   78)
* FileExistsError:                       作業系統例外.       (line   58)
* FileFinder (importlib.machinery 中的類別): importlib machinery -- Importers and path hooks.
                                                             (line  147)
* FileHandler (logging 中的類別):        FileHandler.        (line   10)
* FileHandler (urllib.request 中的類別): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  385)
* FileInput (fileinput 中的類別):        fileinput --- 逐列疊代多個輸入串流.
                                                             (line  139)
* FileIO (io 中的類別):                  原始檔案 I/O.       (line    6)
* filelineno() (於 fileinput 模組中):    fileinput --- 逐列疊代多個輸入串流.
                                                             (line  104)
* FileLoader (importlib.abc 中的類別):   importlib abc -- Abstract base classes related to import.
                                                             (line  317)
* filemode() (於 stat 模組中):           stat --- 直譯 stat 的結果.
                                                             (line  121)
* filename (doctest.DocTest 的屬性):     DocTest 物件.       (line   36)
* filename (http.cookiejar.FileCookieJar 的屬性): CookieJar 與 FileCookieJar 物件.
                                                             (line  154)
* filename (inspect.FrameInfo 的屬性):   直譯器堆疊.         (line   17)
* filename (inspect.Traceback 的屬性):   直譯器堆疊.         (line   57)
* filename (netrc.NetrcParseError 的屬性): netrc --- netrc 檔案處理.
                                                             (line   45)
* filename (OSError 的屬性):             實體例外.           (line  158)
* filename (SyntaxError 的屬性):         實體例外.           (line  263)
* filename (traceback.FrameSummary 的屬性): FrameSummary 物件.
                                                             (line   27)
* filename (traceback.TracebackException 的屬性): TracebackException 物件.
                                                             (line   86)
* filename (tracemalloc.Frame 的屬性):   Frame.              (line   13)
* filename (zipfile.ZipFile 的屬性):     ZipFile 物件.       (line  348)
* filename (zipfile.ZipInfo 的屬性):     ZipInfo 物件.       (line   50)
* filename_only (於 tabnanny 模組中):    tabnanny --- 偵測不良縮排.
                                                             (line   29)
* filename_pattern (tracemalloc.Filter 的屬性): Filter.      (line   54)
* filename() (於 fileinput 模組中):      fileinput --- 逐列疊代多個輸入串流.
                                                             (line   86)
* filename2 (OSError 的屬性):            實體例外.           (line  158)
* filenames（檔案名稱）;pathname expansion（路徑名稱展開）: glob --- Unix 風格的路徑名稱模式擴展.
                                                             (line    8)
* filenames（檔案名稱）;wildcard expansion（萬用字元展開）: fnmatch --- Unix 檔案名稱模式比對.
                                                             (line    8)
* fileno() (bz2.BZ2File 的方法):         De compression of files.
                                                             (line   87)
* fileno() (http.client.HTTPResponse 的方法): HTTPResponse 物件.
                                                             (line   36)
* fileno() (io.IOBase 的方法):           I/O 基礎類別.       (line   55)
* fileno() (multiprocessing.connection.Connection 的方法): Connection Objects.
                                                             (line   31)
* fileno() (select.devpoll 的方法):      /dev/poll Polling Objects.
                                                             (line   24)
* fileno() (select.epoll 的方法):        Edge and Level Trigger Polling epoll Objects.
                                                             (line   73)
* fileno() (select.kqueue 的方法):       Kqueue Objects.     (line   14)
* fileno() (selectors.DevpollSelector 的方法): Classes<3>.   (line  188)
* fileno() (selectors.EpollSelector 的方法): Classes<3>.     (line  179)
* fileno() (selectors.KqueueSelector 的方法): Classes<3>.    (line  199)
* fileno() (socket.socket 的方法):       Socket 物件.        (line  118)
* fileno() (socketserver.BaseServer 的方法): Server Objects. (line   14)
* fileno() (於 fileinput 模組中):        fileinput --- 逐列疊代多個輸入串流.
                                                             (line   91)
* FileNotFoundError:                     作業系統例外.       (line   63)
* fileobj (selectors.SelectorKey 的屬性): Classes<3>.        (line   36)
* files_double_event() (tkinter.filedialog.FileDialog 的方法): Native Load/Save Dialogs.
                                                             (line   94)
* files_select_event() (tkinter.filedialog.FileDialog 的方法): Native Load/Save Dialogs.
                                                             (line   98)
* files() (importlib.abc.TraversableResources 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  606)
* files() (importlib.resources.abc.TraversableResources 的方法): importlib resources abc -- 資源的抽象基底類別.
                                                             (line  169)
* files() (於 importlib.resources 模組中): importlib resources -- Package resource reading opening and access.
                                                             (line   51)
* filesystem encoding and error handler（檔案系統編碼和錯誤處理函式）: 術語表.
                                                             (line  399)
* FileType (argparse 中的類別):          FileType 物件.      (line    6)
* FileWrapper (wsgiref.types 中的類別):  wsgiref types -- 用於靜態型別檢查的 WSGI 型別.
                                                             (line   31)
* FileWrapper (wsgiref.util 中的類別):   wsgiref util -- WSGI 環境工具.
                                                             (line   98)
* fill() (textwrap.TextWrapper 的方法):  textwrap --- 文字包裝與填充.
                                                             (line  296)
* fill() (於 textwrap 模組中):           textwrap --- 文字包裝與填充.
                                                             (line   33)
* fillcolor() (於 turtle 模組中):        Color control.      (line   58)
* filling() (於 turtle 模組中):          Filling.            (line    6)
* fillvalue (reprlib.Repr 的屬性):       Repr 物件.          (line   10)
* Filter (logging 中的類別):             Filter Objects.     (line   13)
* filter (select.kevent 的屬性):         Kevent Objects.     (line   15)
* Filter (tracemalloc 中的類別):         Filter.             (line    6)
* filter_command() (tkinter.filedialog.FileDialog 的方法): Native Load/Save Dialogs.
                                                             (line  102)
* FILTER_DIR (於 unittest.mock 模組中):  FILTER_DIR.         (line    6)
* filter_traces() (tracemalloc.Snapshot 的方法): Snapshot.   (line   35)
* filter() (logging.Filter 的方法):      Filter Objects.     (line   20)
* filter() (logging.Handler 的方法):     Handler Objects.    (line   60)
* filter() (logging.Logger 的方法):      Logger 物件.        (line  330)
* filter() (於 curses 模組中):           函式<5>.            (line  121)
* filter() (於 fnmatch 模組中):          fnmatch --- Unix 檔案名稱模式比對.
                                                             (line   70)
* FilterError:                           tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  228)
* filterfalse() (於 itertools 模組中):   Itertool 函式.      (line  263)
* filterwarnings() (於 warnings 模組中): Available Functions.
                                                             (line  106)
* Final (於 typing 模組中):              特別型式.           (line  177)
* final() (於 typing 模組中):            函式與裝飾器.       (line  311)
* finalization, of objects:              Finalization and De-allocation.
                                                             (line    6)
* finalize (weakref 中的類別):           weakref --- 弱參照. (line  217)
* finalizer（終結函式）:                 Basic customization.
                                                             (line   55)
* find_class() (pickle.Unpickler 的方法): 模組介面.          (line  293)
* find_class()（pickle 協定）:           Restricting Globals.
                                                             (line    6)
* find_library() (於 ctypes.util 模組中): Utility functions. (line   88)
* find_loader() (於 pkgutil 模組中):     pkgutil --- 套件擴充工具程式.
                                                             (line   45)
* find_longest_match() (difflib.SequenceMatcher 的方法): SequenceMatcher 物件.
                                                             (line   64)
* find_msvcrt() (於 ctypes.util 模組中): Utility functions.  (line   97)
* find_spec() (importlib.abc.MetaPathFinder 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line   35)
* find_spec() (importlib.abc.PathEntryFinder 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line   71)
* find_spec() (importlib.machinery.FileFinder 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  177)
* find_spec() (importlib.machinery.PathFinder 的類別方法): importlib machinery -- Importers and path hooks.
                                                             (line  112)
* find_spec() (zipimport.zipimporter 的方法): zipimporter 物件.
                                                             (line   38)
* find_spec() (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line  101)
* find_unused_port() (於 test.support.socket_helper 模組中): test support socket_helper --- 用於 socket 測試的工具.
                                                             (line   15)
* find_user_password() (urllib.request.HTTPPasswordMgr 的方法): HTTPPasswordMgr 物件.
                                                             (line   16)
* find_user_password() (urllib.request.HTTPPasswordMgrWithPriorAuth 的方法): HTTPPasswordMgrWithPriorAuth 物件.
                                                             (line   19)
* find() (bytearray 的方法):             Bytes and Bytearray Operations.
                                                             (line  131)
* find() (bytes 的方法):                 Bytes and Bytearray Operations.
                                                             (line  131)
* find() (doctest.DocTestFinder 的方法): DocTestFinder 物件. (line   32)
* find() (mmap.mmap 的方法):             mmap --- 記憶體映射檔案的支援.
                                                             (line  195)
* find() (str 的方法):                   String Methods<2>.  (line  115)
* find() (xml.etree.ElementTree.Element 的方法): Element 物件.
                                                             (line  101)
* find() (xml.etree.ElementTree.ElementTree 的方法): ElementTree 物件.
                                                             (line   21)
* find() (於 gettext 模組中):            Class-based API.    (line   14)
* findall() (re.Pattern 的方法):         Regular Expression Objects.
                                                             (line   84)
* findall() (xml.etree.ElementTree.Element 的方法): Element 物件.
                                                             (line  110)
* findall() (xml.etree.ElementTree.ElementTree 的方法): ElementTree 物件.
                                                             (line   26)
* findall() (於 re 模組中):              Functions.          (line  131)
* findCaller() (logging.Logger 的方法):  Logger 物件.        (line  347)
* finder（尋檢器）:                      術語表.             (line  418)
* finder（搜尋器）:                      Finders and loaders.
                                                             (line    6)
* finder（搜尋器）;find_spec:            The meta path.      (line    6)
* findfile() (於 test.support 模組中):   test support --- Python 測試套件的工具.
                                                             (line  268)
* finditer() (re.Pattern 的方法):        Regular Expression Objects.
                                                             (line   90)
* finditer() (於 re 模組中):             Functions.          (line  157)
* findlabels() (於 dis 模組中):          Analysis functions. (line  178)
* findlinestarts() (於 dis 模組中):      Analysis functions. (line  161)
* findtext() (xml.etree.ElementTree.Element 的方法): Element 物件.
                                                             (line  119)
* findtext() (xml.etree.ElementTree.ElementTree 的方法): ElementTree 物件.
                                                             (line   31)
* finish_request() (socketserver.BaseServer 的方法): Server Objects.
                                                             (line  125)
* finish() (socketserver.BaseRequestHandler 的方法): Request Handler Objects.
                                                             (line   35)
* finish() (tkinter.dnd.DndHandler 的方法): tkinter dnd --- 拖放支援.
                                                             (line   52)
* FIRST_COMPLETED (於 asyncio 模組中):   Waiting Primitives. (line   35)
* FIRST_COMPLETED (於 concurrent.futures 模組中): 模組函式.  (line   25)
* FIRST_EXCEPTION (於 asyncio 模組中):   Waiting Primitives. (line   39)
* FIRST_EXCEPTION (於 concurrent.futures 模組中): 模組函式.  (line   28)
* firstChild (xml.dom.Node 的屬性):      Node Objects.       (line   54)
* firstkey() (dbm.gnu.gdbm 的方法):      dbm gnu --- GNU 資料庫管理器.
                                                             (line   77)
* firstweekday() (於 calendar 模組中):   calendar --- 日曆相關函式.
                                                             (line  265)
* fix_missing_locations() (於 ast 模組中): ast 輔助程式.     (line  126)
* fix_sentence_endings (textwrap.TextWrapper 的屬性): textwrap --- 文字包裝與填充.
                                                             (line  222)
* Flag (enum 中的類別):                  資料型別<2>.        (line  386)
* flag_bits (zipfile.ZipInfo 的屬性):    ZipInfo 物件.       (line  115)
* FlagBoundary (enum 中的類別):          資料型別<2>.        (line  614)
* flags (re.Pattern 的屬性):             Regular Expression Objects.
                                                             (line  106)
* flags (select.kevent 的屬性):          Kevent Objects.     (line   52)
* flags (於 sys 模組中):                 sys --- 系統特定的參數與函式.
                                                             (line  517)
* flash() (於 curses 模組中):            函式<5>.            (line  132)
* flatten() (email.generator.BytesGenerator 的方法): email generator：產生 MIME 文件.
                                                             (line   79)
* flatten() (email.generator.Generator 的方法): email generator：產生 MIME 文件.
                                                             (line  174)
* flattening（攤平）;objects（物件）:    pickle --- Python 物件序列化.
                                                             (line    8)
* float (內建類別):                      內建函式.           (line  642)
* float_info (於 sys 模組中):            sys --- 系統特定的參數與函式.
                                                             (line  597)
* float_repr_style (於 sys 模組中):      sys --- 系統特定的參數與函式.
                                                             (line  705)
* floating-point literal（浮點數常數）:  Numeric literals.   (line    6)
* floating-point（浮點）;number（數字）: numbers Real float. (line    6)
* floating-point（浮點數）;literals（字面值）: 數值型別 --- int、float、complex.
                                                             (line   15)
* FloatingPointError:                    實體例外.           (line   30)
* FloatOperation (decimal 中的類別):     Signals.            (line  100)
* flock() (於 fcntl 模組中):             fcntl --- fcntl 和 ioctl 系統呼叫.
                                                             (line  148)
* floor division（向下取整除法）:        術語表.             (line  430)
* floor() (於 math 模組中):              數論與表現函式.     (line   43)
* floor()（於 math 模組）:               數值型別 --- int、float、complex.
                                                             (line   97)
* FloorDiv (ast 中的類別):               運算式<2>.          (line   52)
* floordiv() (於 operator 模組中):       operator --- 標準運算子替代函式.
                                                             (line   80)
* flush_headers() (http.server.BaseHTTPRequestHandler 的方法): http server — HTTP 伺服器.
                                                             (line  282)
* flush_std_streams() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  400)
* flush() (bz2.BZ2Compressor 的方法):    Incremental de compression.
                                                             (line   25)
* flush() (io.BufferedWriter 的方法):    Buffered Streams.   (line  125)
* flush() (io.IOBase 的方法):            I/O 基礎類別.       (line   60)
* flush() (logging.Handler 的方法):      Handler Objects.    (line   68)
* flush() (logging.handlers.BufferingHandler 的方法): MemoryHandler.
                                                             (line   30)
* flush() (logging.handlers.MemoryHandler 的方法): MemoryHandler.
                                                             (line   61)
* flush() (logging.StreamHandler 的方法): StreamHandler.     (line   25)
* flush() (lzma.LZMACompressor 的方法):  Compressing and decompressing data in memory.
                                                             (line   91)
* flush() (mailbox.Mailbox 的方法):      Mailbox 物件.       (line  249)
* flush() (mailbox.Maildir 的方法):      Mailbox 物件<2>.    (line  204)
* flush() (mailbox.MH 的方法):           MH 物件.            (line  102)
* flush() (mmap.mmap 的方法):            mmap --- 記憶體映射檔案的支援.
                                                             (line  205)
* flush() (xml.etree.ElementTree.XMLParser 的方法): XMLParser 物件.
                                                             (line   31)
* flush() (xml.etree.ElementTree.XMLPullParser 的方法): XMLPullParser 物件.
                                                             (line   22)
* flush() (zlib.Compress 的方法):        zlib --- 相容於 gzip 的壓縮.
                                                             (line  167)
* flush() (zlib.Decompress 的方法):      zlib --- 相容於 gzip 的壓縮.
                                                             (line  225)
* flushinp() (於 curses 模組中):         函式<5>.            (line  139)
* FlushKey() (於 winreg 模組中):         函式<12>.           (line  239)
* fma() (decimal.Context 的方法):        Context objects.    (line  307)
* fma() (decimal.Decimal 的方法):        Decimal objects.    (line  269)
* fma() (於 math 模組中):                數論與表現函式.     (line   49)
* fmean() (於 statistics 模組中):        函式細節.           (line   42)
* fmod() (於 math 模組中):               數論與表現函式.     (line   64)
* FMT_BINARY (於 plistlib 模組中):       plistlib --- 產生和剖析 Apple plist 檔案.
                                                             (line  160)
* FMT_XML (於 plistlib 模組中):          plistlib --- 產生和剖析 Apple plist 檔案.
                                                             (line  154)
* fnmatch() (於 fnmatch 模組中):         fnmatch --- Unix 檔案名稱模式比對.
                                                             (line   45)
* fnmatchcase() (於 fnmatch 模組中):     fnmatch --- Unix 檔案名稱模式比對.
                                                             (line   64)
* focus() (tkinter.ttk.Treeview 的方法): ttk Treeview.       (line   93)
* fold (datetime.datetime 的屬性):       datetime 物件.      (line  332)
* fold (datetime.time 的屬性):           time 物件.          (line   71)
* fold_binary() (email.policy.Compat32 的方法): email policy Policy Objects.
                                                             (line  608)
* fold_binary() (email.policy.EmailPolicy 的方法): email policy Policy Objects.
                                                             (line  487)
* fold_binary() (email.policy.Policy 的方法): email policy Policy Objects.
                                                             (line  351)
* fold() (email.headerregistry.BaseHeader 的方法): email headerregistry：自訂標頭物件.
                                                             (line   72)
* fold() (email.policy.Compat32 的方法): email policy Policy Objects.
                                                             (line  600)
* fold() (email.policy.EmailPolicy 的方法): email policy Policy Objects.
                                                             (line  467)
* fold() (email.policy.Policy 的方法):   email policy Policy Objects.
                                                             (line  336)
* Font (tkinter.font 中的類別):          tkinter font --- Tkinter 字型包裝器.
                                                             (line   20)
* For (ast 中的類別):                    流程控制.           (line   41)
* FOR_ITER (opcode):                     Python Bytecode Instructions.
                                                             (line  892)
* for;於 comprehensions（綜合運算）:     Displays for lists sets and dictionaries.
                                                             (line   14)
* forget() (tkinter.ttk.Notebook 的方法): ttk Notebook.      (line   17)
* forget() (於 test.support.import_helper 模組中): test support import_helper --- 用於 import 測試的工具.
                                                             (line   10)
* fork() (於 os 模組中):                 行程管理.           (line  255)
* fork() (於 pty 模組中):                pty --- 偽終端工具. (line   22)
* ForkingMixIn (socketserver 中的類別):  Server Creation Notes.
                                                             (line   27)
* ForkingTCPServer (socketserver 中的類別): Server Creation Notes.
                                                             (line   67)
* ForkingUDPServer (socketserver 中的類別): Server Creation Notes.
                                                             (line   67)
* ForkingUnixDatagramServer (socketserver 中的類別): Server Creation Notes.
                                                             (line   67)
* ForkingUnixStreamServer (socketserver 中的類別): Server Creation Notes.
                                                             (line   67)
* forkpty() (於 os 模組中):              行程管理.           (line  299)
* FORMAT (inspect.BufferFlags 的屬性):   Buffer flags.       (line   19)
* format (memoryview 的屬性):            Memory Views.       (line  420)
* format (multiprocessing.shared_memory.ShareableList 的屬性): multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取.
                                                             (line  309)
* format (struct.Struct 的屬性):         Classes<2>.         (line   54)
* format_datetime() (於 email.utils 模組中): email utils：雜項工具.
                                                             (line  173)
* format_exc() (於 traceback 模組中):    traceback --- 列印或取得堆疊回溯 stack traceback.
                                                             (line  184)
* format_exception_only() (traceback.TracebackException 的方法): TracebackException 物件.
                                                             (line  150)
* format_exception_only() (於 traceback 模組中): traceback --- 列印或取得堆疊回溯 stack traceback.
                                                             (line  138)
* format_exception() (於 traceback 模組中): traceback --- 列印或取得堆疊回溯 stack traceback.
                                                             (line  168)
* format_field() (string.Formatter 的方法): 自訂字串格式.    (line   98)
* format_frame_summary() (traceback.StackSummary 的方法): StackSummary 物件.
                                                             (line   53)
* format_help() (argparse.ArgumentParser 的方法): Printing help.
                                                             (line   30)
* format_list() (於 traceback 模組中):   traceback --- 列印或取得堆疊回溯 stack traceback.
                                                             (line  128)
* format_map() (str 的方法):             String Methods<2>.  (line  159)
* FORMAT_SIMPLE (opcode):                Python Bytecode Instructions.
                                                             (line 1157)
* FORMAT_SPEC (opcode):                  Python Bytecode Instructions.
                                                             (line 1169)
* format_stack_entry() (bdb.Bdb 的方法): bdb --- 偵錯器框架. (line  412)
* format_stack() (於 traceback 模組中):  traceback --- 列印或取得堆疊回溯 stack traceback.
                                                             (line  193)
* format_string() (於 locale 模組中):    locale --- 國際化服務.
                                                             (line  445)
* format_tb() (於 traceback 模組中):     traceback --- 列印或取得堆疊回溯 stack traceback.
                                                             (line  189)
* format_usage() (argparse.ArgumentParser 的方法): Printing help.
                                                             (line   25)
* format() (inspect.Signature 的方法):   Introspecting callables with the Signature object.
                                                             (line  157)
* format() (logging.BufferingFormatter 的方法): Formatter Objects.
                                                             (line  154)
* format() (logging.Formatter 的方法):   Formatter Objects.  (line   52)
* format() (logging.Handler 的方法):     Handler Objects.    (line  102)
* format() (pprint.PrettyPrinter 的方法): PrettyPrinter 物件.
                                                             (line   82)
* format() (str 的方法):                 String Methods<2>.  (line  129)
* format() (string.Formatter 的方法):    自訂字串格式.       (line   15)
* format() (traceback.StackSummary 的方法): StackSummary 物件.
                                                             (line   38)
* format() (traceback.TracebackException 的方法): TracebackException 物件.
                                                             (line  138)
* format() (tracemalloc.Traceback 的方法): Traceback.        (line   37)
* format() （內建函式）;__str__() （物件方法）: Basic customization.
                                                             (line  130)
* formataddr() (於 email.utils 模組中):  email utils：雜項工具.
                                                             (line   71)
* formatargvalues() (於 inspect 模組中): 類別與函式.         (line   73)
* formatdate() (於 email.utils 模組中):  email utils：雜項工具.
                                                             (line  152)
* FormatError:                           例外<13>.           (line   31)
* FormatError() (於 ctypes 模組中):      Utility functions.  (line  107)
* formatException() (logging.Formatter 的方法): Formatter Objects.
                                                             (line  116)
* formatFooter() (logging.BufferingFormatter 的方法): Formatter Objects.
                                                             (line  147)
* formatHeader() (logging.BufferingFormatter 的方法): Formatter Objects.
                                                             (line  140)
* formatmonth() (calendar.HTMLCalendar 的方法): calendar --- 日曆相關函式.
                                                             (line  145)
* formatmonth() (calendar.TextCalendar 的方法): calendar --- 日曆相關函式.
                                                             (line  114)
* formatmonthname() (calendar.HTMLCalendar 的方法): calendar --- 日曆相關函式.
                                                             (line  163)
* formatStack() (logging.Formatter 的方法): Formatter Objects.
                                                             (line  124)
* formatted string literal（格式化字串常數）: String literal concatenation.
                                                             (line   24)
* FormattedValue (ast 中的類別):         文本 Literals.      (line   17)
* Formatter (logging 中的類別):          Formatter Objects.  (line    6)
* Formatter (string 中的類別):           自訂字串格式.       (line   11)
* formatTime() (logging.Formatter 的方法): Formatter Objects.
                                                             (line   77)
* formatting（格式化）、字串 (%):        printf-style String Formatting.
                                                             (line    6)
* formatting（格式化）;bytearray (%):    printf-style Bytes Formatting.
                                                             (line    6)
* formatting（格式化）;bytes (%):        printf-style Bytes Formatting.
                                                             (line    6)
* formatwarning() (於 warnings 模組中):  Available Functions.
                                                             (line   97)
* formatyear() (calendar.HTMLCalendar 的方法): calendar --- 日曆相關函式.
                                                             (line  150)
* formatyear() (calendar.TextCalendar 的方法): calendar --- 日曆相關函式.
                                                             (line  126)
* formatyearpage() (calendar.HTMLCalendar 的方法): calendar --- 日曆相關函式.
                                                             (line  155)
* Fortran contiguous（Fortran 連續的）:  shape strides suboffsets.
                                                             (line   25)
* Fortran contiguous（Fortran 連續的） <1>: 術語表.          (line  256)
* forward() (於 turtle 模組中):          Turtle motion.      (line    6)
* ForwardRef (typing 中的類別):          Introspection helpers.
                                                             (line  146)
* fp (urllib.error.HTTPError 的屬性):    urllib error --- urllib request 引發的例外類別.
                                                             (line   56)
* fpathconf() (於 os 模組中):            File Descriptor Operations.
                                                             (line  160)
* Fraction (fractions 中的類別):         fractions --- 有理數.
                                                             (line   16)
* frame (inspect.FrameInfo 的屬性):      直譯器堆疊.         (line   13)
* frame (tkinter.scrolledtext.ScrolledText 的屬性): tkinter scrolledtext --- 捲動文字小工具.
                                                             (line   26)
* Frame (tracemalloc 中的類別):          Frame.              (line    6)
* FrameInfo (inspect 中的類別):          直譯器堆疊.         (line   11)
* FrameSummary (traceback 中的類別):     FrameSummary 物件.  (line   11)
* FrameType (於 types 模組中):           Standard Interpreter Types.
                                                             (line  238)
* free threading:                        術語表.             (line  437)
* free_tool_id() (於 sys.monitoring 模組中): Registering and using tools.
                                                             (line   13)
* free;variable（變數）:                 Binding of names.   (line   48)
* free（C 函式）:                        總覽<2>.            (line   33)
* freedesktop_os_release() (於 platform 模組中): Linux 平台. (line    6)
* freefunc (C type):                     Slot Type typedefs. (line   27)
* freeze utility（凍結工具）:            引入模組<2>.        (line  264)
* freeze_support() (於 multiprocessing 模組中): Miscellaneous<2>.
                                                             (line   49)
* freeze() (於 gc 模組中):               gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line  208)
* frexp() (於 math 模組中):              數論與表現函式.     (line   76)
* FRIDAY (於 calendar 模組中):           calendar --- 日曆相關函式.
                                                             (line  336)
* from_address() (ctypes._CData 的方法): Data types.         (line   42)
* from_buffer_copy() (ctypes._CData 的方法): Data types.     (line   31)
* from_buffer() (ctypes._CData 的方法):  Data types.         (line   19)
* from_bytes() (int 的類別方法):         整數型別的附加 methods.
                                                             (line  101)
* from_callable() (inspect.Signature 的類別方法): Introspecting callables with the Signature object.
                                                             (line  169)
* from_decimal() (fractions.Fraction 的類別方法): fractions --- 有理數.
                                                             (line  146)
* from_exception() (traceback.TracebackException 的類別方法): TracebackException 物件.
                                                             (line  121)
* from_file() (zipfile.ZipInfo 的類別方法): ZipInfo 物件.    (line   14)
* from_file() (zoneinfo.ZoneInfo 的類別方法): The ZoneInfo class.
                                                             (line   28)
* from_float() (decimal.Decimal 的類別方法): Decimal objects.
                                                             (line  242)
* from_float() (fractions.Fraction 的類別方法): fractions --- 有理數.
                                                             (line  135)
* from_iterable() (itertools.chain 的類別方法): Itertool 函式.
                                                             (line  109)
* from_list() (traceback.StackSummary 的類別方法): StackSummary 物件.
                                                             (line   31)
* from_param() (ctypes._CData 的方法):   Data types.         (line   51)
* from_samples() (statistics.NormalDist 的類別方法): NormalDist 物件.
                                                             (line   39)
* from_traceback() (dis.Bytecode 的類別方法): Bytecode analysis.
                                                             (line   43)
* from_uri() (pathlib.Path 的類別方法):  Parsing and generating URIs.
                                                             (line   12)
* from;import statement（引入陳述式）:   Binding of names.   (line    9)
* from;import statement（引入陳述式） <1>: import 陳述式.    (line   52)
* from;yield from expression（yield from 運算式）: Yield expressions.
                                                             (line   65)
* frombuf() (tarfile.TarInfo 的類別方法): TarInfo 物件.      (line   37)
* frombytes() (array.array 的方法):      array --- 高效率的數值型陣列.
                                                             (line  147)
* fromfd() (select.epoll 的方法):        Edge and Level Trigger Polling epoll Objects.
                                                             (line   77)
* fromfd() (select.kqueue 的方法):       Kqueue Objects.     (line   18)
* fromfd() (於 socket 模組中):           建立 sockets.       (line  157)
* fromfile() (array.array 的方法):       array --- 高效率的數值型陣列.
                                                             (line  156)
* fromhex() (bytearray 的類別方法):      Bytearray Objects.  (line   36)
* fromhex() (bytes 的類別方法):          Bytes Objects.      (line   62)
* fromhex() (float 的類別方法):          浮點數的附加 methods.
                                                             (line   35)
* fromisocalendar() (datetime.date 的類別方法): date 物件.   (line   91)
* fromisocalendar() (datetime.datetime 的類別方法): datetime 物件.
                                                             (line  240)
* fromisoformat() (datetime.date 的類別方法): date 物件.     (line   63)
* fromisoformat() (datetime.datetime 的類別方法): datetime 物件.
                                                             (line  191)
* fromisoformat() (datetime.time 的類別方法): time 物件.     (line  107)
* fromkeys() (collections.Counter 的方法): Counter 物件.     (line  107)
* fromkeys() (dict 的類別方法):          Mapping Types --- dict.
                                                             (line  143)
* fromlist() (array.array 的方法):       array --- 高效率的數值型陣列.
                                                             (line  163)
* fromordinal() (datetime.date 的類別方法): date 物件.       (line   54)
* fromordinal() (datetime.datetime 的類別方法): datetime 物件.
                                                             (line  166)
* fromshare() (於 socket 模組中):        建立 sockets.       (line  174)
* fromstring() (於 xml.etree.ElementTree 模組中): 函式<8>.   (line   99)
* fromstringlist() (於 xml.etree.ElementTree 模組中): 函式<8>.
                                                             (line  107)
* fromtarfile() (tarfile.TarInfo 的類別方法): TarInfo 物件.  (line   44)
* fromtimestamp() (datetime.date 的類別方法): date 物件.     (line   35)
* fromtimestamp() (datetime.datetime 的類別方法): datetime 物件.
                                                             (line   95)
* fromunicode() (array.array 的方法):    array --- 高效率的數值型陣列.
                                                             (line  168)
* fromutc() (datetime.timezone 的方法):  timezone 物件.      (line   61)
* fromutc() (datetime.tzinfo 的方法):    tzinfo 物件.        (line  163)
* FrozenImporter (importlib.machinery 中的類別): importlib machinery -- Importers and path hooks.
                                                             (line   77)
* FrozenInstanceError:                   模組內容<8>.        (line  497)
* FrozenSet (typing 中的類別):           內建型別的別名.     (line   39)
* frozenset (內建類別):                  Set Types --- set frozenset.
                                                             (line   33)
* FS (於 curses.ascii 模組中):           curses ascii --- ASCII 字元的工具程式.
                                                             (line  109)
* fs_is_case_insensitive() (於 test.support.os_helper 模組中): test support os_helper --- 用於 os 測試的工具.
                                                             (line  100)
* FS_NONASCII (於 test.support.os_helper 模組中): test support os_helper --- 用於 os 測試的工具.
                                                             (line   10)
* fsdecode() (於 os 模組中):             行程參數.           (line   95)
* fsencode() (於 os 模組中):             行程參數.           (line   82)
* fspath() (於 os 模組中):               行程參數.           (line  108)
* fstat() (於 os 模組中):                File Descriptor Operations.
                                                             (line  182)
* fstatvfs() (於 os 模組中):             File Descriptor Operations.
                                                             (line  194)
* FSTRING_END (於 token 模組中):         token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  258)
* FSTRING_MIDDLE (於 token 模組中):      token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  256)
* FSTRING_START (於 token 模組中):       token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  254)
* fstring（f 字串）:                     String literal concatenation.
                                                             (line   24)
* fsum() (於 math 模組中):               數論與表現函式.     (line   83)
* fsync() (於 os 模組中):                File Descriptor Operations.
                                                             (line  202)
* FTP:                                   urllib request Restrictions.
                                                             (line   37)
* FTP (ftplib 中的類別):                 FTP 物件.           (line    6)
* ftp_open() (urllib.request.FTPHandler 的方法): FTPHandler 物件.
                                                             (line    6)
* FTP_TLS (ftplib 中的類別):             FTP_TLS 物件.       (line    6)
* FTP;ftplib（標準模組）:                ftplib --- FTP 協定用戶端.
                                                             (line    8)
* FTP;protocol（協定）:                  urllib request Restrictions.
                                                             (line    6)
* FTP;protocol（協定） <1>:              ftplib --- FTP 協定用戶端.
                                                             (line    8)
* FTPHandler (urllib.request 中的類別):  urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  395)
* ftruncate() (於 os 模組中):            File Descriptor Operations.
                                                             (line  215)
* Full:                                  queue --- 同步佇列 synchronized queue 類別.
                                                             (line   72)
* FULL (inspect.BufferFlags 的屬性):     Buffer flags.       (line   45)
* full_match() (pathlib.PurePath 的方法): 方法與屬性.        (line  246)
* FULL_RO (inspect.BufferFlags 的屬性):  Buffer flags.       (line   47)
* full_url (urllib.request.Request 的屬性): Request Objects. (line   11)
* full() (asyncio.Queue 的方法):         Queue.              (line   29)
* full() (multiprocessing.Queue 的方法): Pipes and Queues.   (line  125)
* full() (queue.Queue 的方法):           佇列物件.           (line   20)
* fullmatch() (re.Pattern 的方法):       Regular Expression Objects.
                                                             (line   61)
* fullmatch() (於 re 模組中):            Functions.          (line   67)
* fully_trusted_filter() (於 tarfile 模組中): Default named filters.
                                                             (line    9)
* func (functools.partial 的屬性):       partial 物件.       (line    9)
* funcname (bdb.Breakpoint 的屬性):      bdb --- 偵錯器框架. (line  100)
* function (inspect.FrameInfo 的屬性):   直譯器堆疊.         (line   27)
* function (inspect.Traceback 的屬性):   直譯器堆疊.         (line   67)
* Function (pyclbr 中的類別):            函式物件.           (line    6)
* Function (symtable 中的類別):          檢查符號表.         (line  116)
* FUNCTION (symtable.SymbolTableType 的屬性): 檢查符號表.    (line   15)
* function （函式）;annotations（註釋）: 函式定義.           (line  106)
* function （函式）;argument（引數）:    Callable types.     (line    6)
* function （函式）;call（呼叫）:        Callable types.     (line    6)
* function （函式）;call（呼叫） <1>:    Calls.              (line  131)
* function （函式）;call（呼叫） <2>:    Calls.              (line  140)
* function （函式）;definition（定義）:  return 陳述式.      (line    6)
* function （函式）;definition（定義） <1>: 函式定義.        (line    6)
* function （函式）;generator（產生器）: yield 陳述式.       (line    6)
* function （函式）;name（名稱）:        函式定義.           (line    6)
* function （函式）;name（名稱） <1>:    函式定義.           (line    6)
* function annotation（函式註釋）:       術語表.             (line  451)
* function（函式）:                      術語表.             (line  444)
* function（函式）;annotations（註釋）:  函式註釋 Function Annotations.
                                                             (line    6)
* FunctionDef (ast 中的類別):            函式和類別定義.     (line    6)
* FunctionTestCase (unittest 中的類別):  Test cases.         (line  947)
* FunctionType (ast 中的類別):           根節點.             (line   55)
* FunctionType (於 types 模組中):        Standard Interpreter Types.
                                                             (line   25)
* funny_files (filecmp.dircmp 的屬性):   The dircmp class.   (line   98)
* Future (asyncio 中的類別):             Future 物件<2>.     (line    6)
* Future (concurrent.futures 中的類別):  Future 物件.        (line    9)
* future;statement（陳述式）:            Future statements.  (line    6)
* FutureWarning:                         警告.               (line   48)
* fwalk() (於 os 模組中):                Files and Directories.
                                                             (line 1723)
* gaierror:                              例外<10>.           (line   27)
* gamma() (於 math 模組中):              Special functions.  (line   29)
* gammavariate() (於 random 模組中):     實數分布.           (line   41)
* garbage (於 gc 模組中):                gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line  236)
* garbage collection（垃圾回收）:        Objects values and types.
                                                             (line   37)
* garbage collection（垃圾回收） <1>:    術語表.             (line  481)
* gather() (curses.textpad.Textbox 的方法): Textbox objects. (line  109)
* gather() (於 asyncio 模組中):          Running Tasks Concurrently.
                                                             (line    6)
* gauss() (於 random 模組中):            實數分布.           (line   53)
* gc_collect() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  353)
* gcd() (於 math 模組中):                數論與表現函式.     (line   96)
* gcvisitobjects_t (C type):             Querying Garbage Collector State.
                                                             (line   26)
* ge() (於 operator 模組中):             operator --- 標準運算子替代函式.
                                                             (line   20)
* generate_tokens() (於 tokenize 模組中): Tokenizing Input.  (line   38)
* Generator (collections.abc 中的類別):  Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line   56)
* Generator (email.generator 中的類別):  email generator：產生 MIME 文件.
                                                             (line  139)
* Generator (typing 中的類別):           Aliases to other ABCs in collections abc.
                                                             (line   37)
* generator expression（產生器運算式）:  術語表.             (line  508)
* generator expression（產生器運算式） <1>: 術語表.          (line  508)
* generator iterator（產生器疊代器）:    術語表.             (line  498)
* generator（產生器）:                   術語表.             (line  489)
* generator（產生器） <1>:               術語表.             (line  489)
* generator（產生器）;expression:        Generator expressions.
                                                             (line    6)
* generator（產生器）;function （函式）: Generator functions.
                                                             (line    6)
* generator（產生器）;function （函式） <1>: Yield expressions.
                                                             (line    6)
* generator（產生器）;function （函式） <2>: yield 陳述式.   (line    6)
* generator（產生器）;iterator（疊代器）: yield 陳述式.      (line    6)
* generator（產生器）;itorator（疊代器）: Generator functions.
                                                             (line    6)
* GeneratorExit:                         實體例外.           (line   34)
* GeneratorExp (ast 中的類別):           綜合運算式 comprehensions.
                                                             (line    6)
* GeneratorType (於 types 模組中):       Standard Interpreter Types.
                                                             (line   36)
* Generic (typing 中的類別):             Building generic types and type aliases.
                                                             (line   15)
* generic function（泛型函式）:          術語表.             (line  517)
* generic type（泛型型別）:              術語表.             (line  524)
* generic_visit() (ast.NodeVisitor 的方法): ast 輔助程式.    (line  173)
* Generic（泛型）;Alias（別名）:         泛型別名型別.       (line    6)
* generic（泛型）;special;attribute（屬性）: 標準型別階層.   (line   13)
* GenericAlias (types 中的類別):         Standard Interpreter Types.
                                                             (line  193)
* genops() (於 pickletools 模組中):      程式化介面.         (line   19)
* geometric_mean() (於 statistics 模組中): 函式細節.         (line   69)
* GET_AITER (opcode):                    Python Bytecode Instructions.
                                                             (line  314)
* get_all_breaks() (bdb.Bdb 的方法):     bdb --- 偵錯器框架. (line  396)
* get_all_start_methods() (於 multiprocessing 模組中): Miscellaneous<2>.
                                                             (line   76)
* get_all() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  252)
* get_all() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  360)
* get_all() (wsgiref.headers.Headers 的方法): wsgiref headers -- WSGI 回應標頭工具.
                                                             (line   40)
* GET_ANEXT (opcode):                    Python Bytecode Instructions.
                                                             (line  323)
* get_annotations() (於 inspect 模組中): 類別與函式.         (line  155)
* get_app() (wsgiref.simple_server.WSGIServer 的方法): wsgiref simple_server -- 一個簡單的 WSGI HTTP 伺服器.
                                                             (line   60)
* get_archive_formats() (於 shutil 模組中): Archiving operations.
                                                             (line   68)
* get_args() (於 typing 模組中):         Introspection helpers.
                                                             (line   79)
* get_asyncgen_hooks() (於 sys 模組中):  sys --- 系統特定的參數與函式.
                                                             (line  967)
* get_attribute() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  588)
* GET_AWAITABLE (opcode):                Python Bytecode Instructions.
                                                             (line  295)
* get_begidx() (於 readline 模組中):     Completion.         (line   40)
* get_blocking() (於 os 模組中):         File Descriptor Operations.
                                                             (line  228)
* get_body_encoding() (email.charset.Charset 的方法): email charset：表示字元集合.
                                                             (line   94)
* get_body() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  515)
* get_boundary() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  401)
* get_boundary() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  577)
* get_bpbynumber() (bdb.Bdb 的方法):     bdb --- 偵錯器框架. (line  372)
* get_break() (bdb.Bdb 的方法):          bdb --- 偵錯器框架. (line  381)
* get_breaks() (bdb.Bdb 的方法):         bdb --- 偵錯器框架. (line  386)
* get_buffer() (asyncio.BufferedProtocol 的方法): Buffered Streaming Protocols.
                                                             (line   21)
* get_bytes() (mailbox.Mailbox 的方法):  Mailbox 物件.       (line  167)
* get_ca_certs() (ssl.SSLContext 的方法): SSL Contexts.      (line  181)
* get_cache_token() (於 abc 模組中):     abc --- 抽象基底類別.
                                                             (line  289)
* get_channel_binding() (ssl.SSLSocket 的方法): SSL Sockets. (line  244)
* get_charset() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  264)
* get_charsets() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  429)
* get_charsets() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  611)
* get_child_watcher() (asyncio.AbstractEventLoopPolicy 的方法): Policy Objects.
                                                             (line   33)
* get_child_watcher() (於 asyncio 模組中): Process Watchers. (line   25)
* get_children() (symtable.SymbolTable 的方法): 檢查符號表.  (line  112)
* get_children() (tkinter.ttk.Treeview 的方法): ttk Treeview.
                                                             (line   19)
* get_ciphers() (ssl.SSLContext 的方法): SSL Contexts.       (line  195)
* get_clock_info() (於 time 模組中):     函式<4>.            (line   95)
* get_close_matches() (於 difflib 模組中): difflib --- 計算差異的輔助工具.
                                                             (line  205)
* get_code() (importlib.abc.InspectLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  234)
* get_code() (importlib.abc.SourceLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  426)
* get_code() (importlib.machinery.ExtensionFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  327)
* get_code() (importlib.machinery.SourcelessFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  263)
* get_code() (zipimport.zipimporter 的方法): zipimporter 物件.
                                                             (line   45)
* get_completer_delims() (於 readline 模組中): Completion.   (line   50)
* get_completer() (於 readline 模組中):  Completion.         (line   29)
* get_completion_type() (於 readline 模組中): Completion.    (line   34)
* get_config_h_filename() (於 sysconfig 模組中): 其他函式<3>.
                                                             (line   68)
* get_config_var() (於 sysconfig 模組中): Configuration variables.
                                                             (line   26)
* get_config_vars() (於 sysconfig 模組中): Configuration variables.
                                                             (line   16)
* get_content_charset() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  422)
* get_content_charset() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  600)
* get_content_disposition() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  452)
* get_content_disposition() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  625)
* get_content_maintype() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  322)
* get_content_maintype() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  430)
* get_content_subtype() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  328)
* get_content_subtype() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  436)
* get_content_type() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  306)
* get_content_type() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  414)
* get_content() (email.contentmanager.ContentManager 的方法): email contentmanager：管理 MIME 內容.
                                                             (line   19)
* get_content() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  579)
* get_content() (於 email.contentmanager 模組中): Content Manager Instances.
                                                             (line   24)
* get_context() (asyncio.Handle 的方法): 回呼處理.           (line   11)
* get_context() (asyncio.Task 的方法):   Task Object.        (line  170)
* get_context() (於 multiprocessing 模組中): Miscellaneous<2>.
                                                             (line   85)
* get_coro() (asyncio.Task 的方法):      Task Object.        (line  157)
* get_coroutine_origin_tracking_depth() (於 sys 模組中): sys --- 系統特定的參數與函式.
                                                             (line  981)
* get_count() (於 gc 模組中):            gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line  130)
* get_current_history_length() (於 readline 模組中): History list.
                                                             (line   14)
* get_data() (importlib.abc.FileLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  349)
* get_data() (importlib.abc.ResourceLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  215)
* get_data() (zipimport.zipimporter 的方法): zipimporter 物件.
                                                             (line   50)
* get_data() (於 pkgutil 模組中):        pkgutil --- 套件擴充工具程式.
                                                             (line  156)
* get_date() (mailbox.MaildirMessage 的方法): MaildirMessage 物件.
                                                             (line   92)
* get_debug() (asyncio.loop 的方法):     啟用除錯模式.       (line    6)
* get_debug() (於 gc 模組中):            gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line   64)
* get_default_scheme() (於 sysconfig 模組中): 安裝路徑函式.  (line   14)
* get_default_type() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  333)
* get_default_type() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  441)
* get_default_verify_paths() (於 ssl 模組中): 認證處理.      (line   58)
* get_default() (argparse.ArgumentParser 的方法): Parser defaults.
                                                             (line   33)
* get_dialect() (於 csv 模組中):         模組內容<3>.        (line   76)
* get_disassembly_as_string() (test.support.bytecode_helper.BytecodeTestCase 的方法): test support bytecode_helper --- 用於測試位元組碼能正確產生的支援工具.
                                                             (line   18)
* get_docstring() (於 ast 模組中):       ast 輔助程式.       (line  105)
* get_doctest() (doctest.DocTestParser 的方法): DocTestParser 物件.
                                                             (line   13)
* get_endidx() (於 readline 模組中):     Completion.         (line   40)
* get_environ() (wsgiref.simple_server.WSGIRequestHandler 的方法): wsgiref simple_server -- 一個簡單的 WSGI HTTP 伺服器.
                                                             (line   80)
* get_errno() (於 ctypes 模組中):        Utility functions.  (line  120)
* get_escdelay() (於 curses 模組中):     函式<5>.            (line  448)
* get_event_loop_policy() (於 asyncio 模組中): Getting and Setting the Policy.
                                                             (line    9)
* get_event_loop() (asyncio.AbstractEventLoopPolicy 的方法): Policy Objects.
                                                             (line   12)
* get_event_loop() (於 asyncio 模組中):  事件迴圈.           (line   35)
* get_events() (於 sys.monitoring 模組中): Setting events globally.
                                                             (line    9)
* get_examples() (doctest.DocTestParser 的方法): DocTestParser 物件.
                                                             (line   22)
* get_exception_handler() (asyncio.loop 的方法): 錯誤處理 API.
                                                             (line   24)
* get_exec_path() (於 os 模組中):        行程參數.           (line  167)
* get_extra_info() (asyncio.BaseTransport 的方法): Base Transport.
                                                             (line   21)
* get_extra_info() (asyncio.StreamWriter 的方法): StreamWriter.
                                                             (line   56)
* get_field() (string.Formatter 的方法): 自訂字串格式.       (line   51)
* get_file_breaks() (bdb.Bdb 的方法):    bdb --- 偵錯器框架. (line  391)
* get_file() (mailbox.Babyl 的方法):     Babyl 物件.         (line   49)
* get_file() (mailbox.Mailbox 的方法):   Mailbox 物件.       (line  183)
* get_file() (mailbox.Maildir 的方法):   Mailbox 物件<2>.    (line  221)
* get_file() (mailbox.mbox 的方法):      mbox 物件.          (line   32)
* get_file() (mailbox.MH 的方法):        MH 物件.            (line   96)
* get_file() (mailbox.MMDF 的方法):      MMDF 物件.          (line   29)
* get_filename() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  391)
* get_filename() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  567)
* get_filename() (importlib.abc.ExecutionLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  304)
* get_filename() (importlib.abc.FileLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  345)
* get_filename() (importlib.machinery.ExtensionFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  335)
* get_filename() (zipimport.zipimporter 的方法): zipimporter 物件.
                                                             (line   58)
* get_filter() (tkinter.filedialog.FileDialog 的方法): Native Load/Save Dialogs.
                                                             (line  106)
* get_flags() (mailbox.Maildir 的方法):  Mailbox 物件<2>.    (line   92)
* get_flags() (mailbox.MaildirMessage 的方法): MaildirMessage 物件.
                                                             (line   63)
* get_flags() (mailbox.mboxMessage 的方法): mboxMessage 物件.
                                                             (line   64)
* get_flags() (mailbox.MMDFMessage 的方法): MMDFMessage 物件.
                                                             (line   63)
* get_folder() (mailbox.Maildir 的方法): Mailbox 物件<2>.    (line   69)
* get_folder() (mailbox.MH 的方法):      MH 物件.            (line   39)
* get_frees() (symtable.Function 的方法): 檢查符號表.        (line  136)
* get_freeze_count() (於 gc 模組中):     gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line  228)
* get_from() (mailbox.mboxMessage 的方法): mboxMessage 物件. (line   47)
* get_from() (mailbox.MMDFMessage 的方法): MMDFMessage 物件. (line   46)
* get_full_url() (urllib.request.Request 的方法): Request Objects.
                                                             (line  106)
* get_globals() (symtable.Function 的方法): 檢查符號表.      (line  128)
* get_grouped_opcodes() (difflib.SequenceMatcher 的方法): SequenceMatcher 物件.
                                                             (line  168)
* get_handle_inheritable() (於 os 模組中): Inheritance of File Descriptors.
                                                             (line   34)
* get_header() (urllib.request.Request 的方法): Request Objects.
                                                             (line  120)
* get_history_item() (於 readline 模組中): History list.     (line   20)
* get_history_length() (於 readline 模組中): History file.   (line   30)
* get_id() (symtable.SymbolTable 的方法): 檢查符號表.        (line   69)
* get_ident() (於 _thread 模組中):       _thread --- 低階執行緒 API.
                                                             (line   74)
* get_ident() (於 threading 模組中):     threading --- 基於執行緒的平行性.
                                                             (line  117)
* get_identifiers() (string.Template 的方法): 模板字串.      (line   66)
* get_identifiers() (symtable.SymbolTable 的方法): 檢查符號表.
                                                             (line   99)
* get_importer() (於 pkgutil 模組中):    pkgutil --- 套件擴充工具程式.
                                                             (line   61)
* get_info() (mailbox.Maildir 的方法):   Mailbox 物件<2>.    (line  155)
* get_info() (mailbox.MaildirMessage 的方法): MaildirMessage 物件.
                                                             (line  102)
* get_inheritable() (socket.socket 的方法): Socket 物件.     (line  127)
* get_inheritable() (於 os 模組中):      Inheritance of File Descriptors.
                                                             (line   25)
* get_instructions() (於 dis 模組中):    Analysis functions. (line  135)
* get_int_max_str_digits() (於 sys 模組中): sys --- 系統特定的參數與函式.
                                                             (line  811)
* get_interpreter() (於 zipapp 模組中):  Python API.         (line   82)
* GET_ITER (opcode):                     Python Bytecode Instructions.
                                                             (line  206)
* get_key() (selectors.BaseSelector 的方法): Classes<3>.     (line  145)
* get_labels() (mailbox.Babyl 的方法):   Babyl 物件.         (line   35)
* get_labels() (mailbox.BabylMessage 的方法): BabylMessage 物件.
                                                             (line   47)
* get_last_error() (於 ctypes 模組中):   Utility functions.  (line  127)
* GET_LEN (opcode):                      Python Bytecode Instructions.
                                                             (line  516)
* get_line_buffer() (於 readline 模組中): Line buffer.       (line    8)
* get_lineno() (symtable.SymbolTable 的方法): 檢查符號表.    (line   82)
* get_loader() (於 pkgutil 模組中):      pkgutil --- 套件擴充工具程式.
                                                             (line   74)
* get_local_events() (於 sys.monitoring 模組中): Per code object events.
                                                             (line   11)
* get_locals() (symtable.Function 的方法): 檢查符號表.       (line  124)
* get_logger() (於 multiprocessing 模組中): Logging.         (line   11)
* get_loop() (asyncio.Future 的方法):    Future 物件<2>.     (line  127)
* get_loop() (asyncio.Runner 的方法):    Runner context manager.
                                                             (line   55)
* get_loop() (asyncio.Server 的方法):    Server 物件.        (line   65)
* get_makefile_filename() (於 sysconfig 模組中): 其他函式<3>.
                                                             (line   72)
* get_map() (selectors.BaseSelector 的方法): Classes<3>.     (line  153)
* get_matching_blocks() (difflib.SequenceMatcher 的方法): SequenceMatcher 物件.
                                                             (line  107)
* get_message() (mailbox.Mailbox 的方法): Mailbox 物件.      (line  160)
* get_method() (urllib.request.Request 的方法): Request Objects.
                                                             (line   68)
* get_methods() (symtable.Class 的方法): 檢查符號表.         (line  144)
* get_mixed_type_key() (於 ipaddress 模組中): Other Module Level Functions.
                                                             (line   56)
* get_name() (asyncio.Task 的方法):      Task Object.        (line  177)
* get_name() (symtable.Symbol 的方法):   檢查符號表.         (line  184)
* get_name() (symtable.SymbolTable 的方法): 檢查符號表.      (line   73)
* get_namespace() (symtable.Symbol 的方法): 檢查符號表.      (line  251)
* get_namespaces() (symtable.Symbol 的方法): 檢查符號表.     (line  247)
* get_native_id() (於 _thread 模組中):   _thread --- 低階執行緒 API.
                                                             (line   81)
* get_native_id() (於 threading 模組中): threading --- 基於執行緒的平行性.
                                                             (line  127)
* get_nonlocals() (symtable.Function 的方法): 檢查符號表.    (line  132)
* get_nonstandard_attr() (http.cookiejar.Cookie 的方法): Cookie 物件<2>.
                                                             (line  102)
* get_nowait() (asyncio.Queue 的方法):   Queue.              (line   45)
* get_nowait() (multiprocessing.Queue 的方法): Pipes and Queues.
                                                             (line  165)
* get_nowait() (queue.Queue 的方法):     佇列物件.           (line   58)
* get_nowait() (queue.SimpleQueue 的方法): SimpleQueue 物件. (line   44)
* get_object_traceback() (於 tracemalloc 模組中): 函式<10>.  (line   12)
* get_objects() (於 gc 模組中):          gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line   68)
* get_opcodes() (difflib.SequenceMatcher 的方法): SequenceMatcher 物件.
                                                             (line  125)
* get_option_group() (optparse.OptionParser 的方法): Grouping Options.
                                                             (line  103)
* get_option() (optparse.OptionParser 的方法): Querying and manipulating your option parser.
                                                             (line   37)
* get_origin() (於 typing 模組中):       Introspection helpers.
                                                             (line   57)
* get_original_bases() (於 types 模組中): Dynamic Type Creation.
                                                             (line   71)
* get_original_stdout() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  310)
* get_osfhandle() (於 msvcrt 模組中):    File Operations.    (line   58)
* get_output_charset() (email.charset.Charset 的方法): email charset：表示字元集合.
                                                             (line  109)
* get_overloads() (於 typing 模組中):    函式與裝飾器.       (line  286)
* get_pagesize() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  277)
* get_param() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  476)
* get_parameters() (symtable.Function 的方法): 檢查符號表.   (line  120)
* get_params() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  455)
* get_path_names() (於 sysconfig 模組中): 安裝路徑函式.      (line   57)
* get_path() (於 sysconfig 模組中):      安裝路徑函式.       (line   62)
* get_paths() (於 sysconfig 模組中):     安裝路徑函式.       (line   93)
* get_payload() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  179)
* get_pid() (asyncio.SubprocessTransport 的方法): Subprocess Transports.
                                                             (line    6)
* get_pipe_transport() (asyncio.SubprocessTransport 的方法): Subprocess Transports.
                                                             (line   10)
* get_platform() (於 sysconfig 模組中):  其他函式<3>.        (line   11)
* get_poly() (於 turtle 模組中):         Special Turtle methods.
                                                             (line   17)
* get_preferred_scheme() (於 sysconfig 模組中): 安裝路徑函式.
                                                             (line   24)
* get_protocol_members() (於 typing 模組中): Introspection helpers.
                                                             (line   97)
* get_protocol() (asyncio.BaseTransport 的方法): Base Transport.
                                                             (line   88)
* get_proxy_response_headers() (http.client.HTTPConnection 的方法): HTTPConnection 物件.
                                                             (line  133)
* get_python_version() (於 sysconfig 模組中): 其他函式<3>.   (line    6)
* get_ready() (graphlib.TopologicalSorter 的方法): graphlib —-- 使用類圖 graph-like 結構進行操作的功能.
                                                             (line  130)
* get_referents() (於 gc 模組中):        gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line  156)
* get_referrers() (於 gc 模組中):        gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line  139)
* get_request() (socketserver.BaseServer 的方法): Server Objects.
                                                             (line  131)
* get_returncode() (asyncio.SubprocessTransport 的方法): Subprocess Transports.
                                                             (line   29)
* get_running_loop() (於 asyncio 模組中): 事件迴圈.          (line   25)
* get_scheme_names() (於 sysconfig 模組中): 安裝路徑函式.    (line    9)
* get_scheme() (wsgiref.handlers.BaseHandler 的方法): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  161)
* get_selection() (tkinter.filedialog.FileDialog 的方法): Native Load/Save Dialogs.
                                                             (line  110)
* get_sequences() (mailbox.MH 的方法):   MH 物件.            (line   56)
* get_sequences() (mailbox.MHMessage 的方法): MHMessage 物件.
                                                             (line   32)
* get_server_certificate() (於 ssl 模組中): 認證處理.        (line   28)
* get_server() (multiprocessing.managers.BaseManager 的方法): Managers.
                                                             (line   63)
* get_shapepoly() (於 turtle 模組中):    Appearance.         (line  168)
* get_source_segment() (於 ast 模組中):  ast 輔助程式.       (line  115)
* get_source() (importlib.abc.InspectLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  248)
* get_source() (importlib.abc.SourceLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  443)
* get_source() (importlib.machinery.ExtensionFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  331)
* get_source() (importlib.machinery.SourcelessFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  268)
* get_source() (zipimport.zipimporter 的方法): zipimporter 物件.
                                                             (line   66)
* get_stack() (asyncio.Task 的方法):     Task Object.        (line  121)
* get_stack() (bdb.Bdb 的方法):          bdb --- 偵錯器框架. (line  403)
* get_start_method() (於 multiprocessing 模組中): Miscellaneous<2>.
                                                             (line   97)
* get_starttag_text() (html.parser.HTMLParser 的方法): HTMLParser 方法.
                                                             (line   28)
* get_stats_profile() (pstats.Stats 的方法): The Stats Class.
                                                             (line  225)
* get_stats() (於 gc 模組中):            gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line   87)
* get_stderr() (wsgiref.handlers.BaseHandler 的方法): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  110)
* get_stderr() (wsgiref.simple_server.WSGIRequestHandler 的方法): wsgiref simple_server -- 一個簡單的 WSGI HTTP 伺服器.
                                                             (line   88)
* get_stdin() (wsgiref.handlers.BaseHandler 的方法): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  105)
* get_string() (mailbox.Mailbox 的方法): Mailbox 物件.       (line  175)
* get_subdir() (mailbox.MaildirMessage 的方法): MaildirMessage 物件.
                                                             (line   47)
* get_symbols() (symtable.SymbolTable 的方法): 檢查符號表.   (line  108)
* get_tabsize() (於 curses 模組中):      函式<5>.            (line  463)
* get_task_factory() (asyncio.loop 的方法): 建立 Futures 和 Tasks.
                                                             (line   43)
* get_terminal_size() (於 os 模組中):    Querying the size of a terminal.
                                                             (line    8)
* get_terminal_size() (於 shutil 模組中): Querying the size of the output terminal.
                                                             (line    6)
* get_threshold() (於 gc 模組中):        gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line  134)
* get_token() (shlex.shlex 的方法):      shlex 物件.         (line    8)
* get_tool() (於 sys.monitoring 模組中): Registering and using tools.
                                                             (line   22)
* get_traceback_limit() (於 tracemalloc 模組中): 函式<10>.   (line   22)
* get_traced_memory() (於 tracemalloc 模組中): 函式<10>.     (line   32)
* get_tracemalloc_memory() (於 tracemalloc 模組中): 函式<10>.
                                                             (line   56)
* get_type_hints() (於 typing 模組中):   Introspection helpers.
                                                             (line    6)
* get_type() (symtable.SymbolTable 的方法): 檢查符號表.      (line   54)
* get_unixfrom() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  150)
* get_unixfrom() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  161)
* get_unpack_formats() (於 shutil 模組中): Archiving operations.
                                                             (line  190)
* get_unverified_chain() (ssl.SSLSocket 的方法): SSL Sockets.
                                                             (line  208)
* get_usage() (optparse.OptionParser 的方法): 其他方法.      (line   22)
* get_value() (string.Formatter 的方法): 自訂字串格式.       (line   61)
* get_verified_chain() (ssl.SSLSocket 的方法): SSL Sockets.  (line  199)
* get_version() (optparse.OptionParser 的方法): Printing a version string.
                                                             (line   34)
* get_visible() (mailbox.BabylMessage 的方法): BabylMessage 物件.
                                                             (line   63)
* get_wch() (curses.window 的方法):      Window Objects.     (line  240)
* get_write_buffer_limits() (asyncio.WriteTransport 的方法): Write-only Transports.
                                                             (line   23)
* get_write_buffer_size() (asyncio.WriteTransport 的方法): Write-only Transports.
                                                             (line   19)
* GET_YIELD_FROM_ITER (opcode):          Python Bytecode Instructions.
                                                             (line  210)
* get() (asyncio.Queue 的方法):          Queue.              (line   36)
* get() (configparser.ConfigParser 的方法): ConfigParser 物件.
                                                             (line  215)
* get() (contextvars.Context 的方法):    Manual Context Management.
                                                             (line   90)
* get() (contextvars.ContextVar 的方法): Context Variables.  (line   30)
* get() (dict 的方法):                   Mapping Types --- dict.
                                                             (line  155)
* get() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  243)
* get() (email.message.Message 的方法):  email message Message Representing an email message using the compat32 API.
                                                             (line  352)
* get() (mailbox.Mailbox 的方法):        Mailbox 物件.       (line  148)
* get() (multiprocessing.pool.AsyncResult 的方法): Process Pools.
                                                             (line  199)
* get() (multiprocessing.Queue 的方法):  Pipes and Queues.   (line  150)
* get() (multiprocessing.SimpleQueue 的方法): Pipes and Queues.
                                                             (line  236)
* get() (queue.Queue 的方法):            佇列物件.           (line   41)
* get() (queue.SimpleQueue 的方法):      SimpleQueue 物件.   (line   35)
* get() (tkinter.ttk.Combobox 的方法):   ttk Combobox.       (line   15)
* get() (tkinter.ttk.Spinbox 的方法):    ttk Spinbox.        (line    8)
* get() (types.MappingProxyType 的方法): Standard Interpreter Types.
                                                             (line  302)
* get() (xml.etree.ElementTree.Element 的方法): Element 物件.
                                                             (line   64)
* get() (於 webbrowser 模組中):          webbrowser --- 方便的網頁瀏覽器控制器.
                                                             (line  103)
* getacl() (imaplib.IMAP4 的方法):       IMAP4 物件.         (line  106)
* getaddresses() (於 email.utils 模組中): email utils：雜項工具.
                                                             (line   85)
* getaddrinfo() (asyncio.loop 的方法):   DNS.                (line    6)
* getaddrinfo() (於 socket 模組中):      其他函式<2>.        (line   17)
* getallocatedblocks() (於 sys 模組中):  sys --- 系統特定的參數與函式.
                                                             (line  717)
* getandroidapilevel() (於 sys 模組中):  sys --- 系統特定的參數與函式.
                                                             (line  738)
* getannotation() (imaplib.IMAP4 的方法): IMAP4 物件.        (line  111)
* getargvalues() (於 inspect 模組中):    類別與函式.         (line   62)
* getasyncgenlocals() (於 inspect 模組中): Current State of Generators Coroutines and Asynchronous Generators.
                                                             (line   99)
* getasyncgenstate() (於 inspect 模組中): Current State of Generators Coroutines and Asynchronous Generators.
                                                             (line   47)
* getatime() (於 os.path 模組中):        os path --- 常見的路徑名操作.
                                                             (line  151)
* getattr_static() (於 inspect 模組中):  Fetching attributes statically.
                                                             (line   16)
* getattrfunc (C type):                  Slot Type typedefs. (line   43)
* getAttribute() (xml.dom.Element 的方法): Element Objects.  (line   31)
* getAttributeNode() (xml.dom.Element 的方法): Element Objects.
                                                             (line   37)
* getAttributeNodeNS() (xml.dom.Element 的方法): Element Objects.
                                                             (line   47)
* getAttributeNS() (xml.dom.Element 的方法): Element Objects.
                                                             (line   41)
* getattrofunc (C type):                 Slot Type typedefs. (line   54)
* GetBase() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line   31)
* getbegyx() (curses.window 的方法):     Window Objects.     (line  224)
* getbkgd() (curses.window 的方法):      Window Objects.     (line  228)
* getblocking() (socket.socket 的方法):  Socket 物件.        (line  164)
* getboolean() (configparser.ConfigParser 的方法): ConfigParser 物件.
                                                             (line  249)
* getbuffer() (io.BytesIO 的方法):       Buffered Streams.   (line   21)
* getbufferproc (C type):                Slot Type typedefs. (line  100)
* getByteStream() (xml.sax.xmlreader.InputSource 的方法): InputSource 物件.
                                                             (line   48)
* getcallargs() (於 inspect 模組中):     類別與函式.         (line   92)
* getcanvas() (於 turtle 模組中):        Settings and special methods.
                                                             (line   54)
* getch() (curses.window 的方法):        Window Objects.     (line  233)
* getch() (於 msvcrt 模組中):            Console I/O.        (line   11)
* getCharacterStream() (xml.sax.xmlreader.InputSource 的方法): InputSource 物件.
                                                             (line   64)
* getche() (於 msvcrt 模組中):           Console I/O.        (line   26)
* getChild() (logging.Logger 的方法):    Logger 物件.        (line  159)
* getChildren() (logging.Logger 的方法): Logger 物件.        (line  171)
* getclasstree() (於 inspect 模組中):    類別與函式.         (line    6)
* getclosurevars() (於 inspect 模組中):  類別與函式.         (line  123)
* getcode() (http.client.HTTPResponse 的方法): HTTPResponse 物件.
                                                             (line   87)
* getcode() (urllib.response.addinfourl 的方法): urllib response --- Response classes used by urllib.
                                                             (line   44)
* getColumnNumber() (xml.sax.xmlreader.Locator 的方法): Locator Objects.
                                                             (line    8)
* getcomments() (於 inspect 模組中):     取得原始碼.         (line   18)
* getcompname() (wave.Wave_read 的方法): Wave_read 物件.     (line   37)
* getcomptype() (wave.Wave_read 的方法): Wave_read 物件.     (line   33)
* getconfig() (sqlite3.Connection 的方法): Connection 物件.  (line  644)
* getContentHandler() (xml.sax.xmlreader.XMLReader 的方法): XMLReader 物件.
                                                             (line   21)
* getcontext() (於 decimal 模組中):      Context objects.    (line   14)
* getcoroutinelocals() (於 inspect 模組中): Current State of Generators Coroutines and Asynchronous Generators.
                                                             (line   91)
* getcoroutinestate() (於 inspect 模組中): Current State of Generators Coroutines and Asynchronous Generators.
                                                             (line   28)
* getctime() (於 os.path 模組中):        os path --- 常見的路徑名操作.
                                                             (line  165)
* getcwd() (於 os 模組中):               Files and Directories.
                                                             (line  288)
* getcwdb() (於 os 模組中):              Files and Directories.
                                                             (line  292)
* getdecoder() (於 codecs 模組中):       codecs --- 編解碼器註冊表和基底類別.
                                                             (line  107)
* getdefaultencoding() (於 sys 模組中):  sys --- 系統特定的參數與函式.
                                                             (line  749)
* getdefaultlocale() (於 locale 模組中): locale --- 國際化服務.
                                                             (line  336)
* getdefaulttimeout() (於 socket 模組中): 其他函式<2>.       (line  346)
* getdlopenflags() (於 sys 模組中):      sys --- 系統特定的參數與函式.
                                                             (line  754)
* getdoc() (於 inspect 模組中):          取得原始碼.         (line    6)
* getDOMImplementation() (於 xml.dom 模組中): 模組內容<6>.   (line   17)
* getDTDHandler() (xml.sax.xmlreader.XMLReader 的方法): XMLReader 物件.
                                                             (line   30)
* getEffectiveLevel() (logging.Logger 的方法): Logger 物件.  (line  149)
* getegid() (於 os 模組中):              行程參數.           (line  177)
* getElementsByTagName() (xml.dom.Document 的方法): Document Objects.
                                                             (line   61)
* getElementsByTagName() (xml.dom.Element 的方法): Element Objects.
                                                             (line   14)
* getElementsByTagNameNS() (xml.dom.Document 的方法): Document Objects.
                                                             (line   66)
* getElementsByTagNameNS() (xml.dom.Element 的方法): Element Objects.
                                                             (line   18)
* getencoder() (於 codecs 模組中):       codecs --- 編解碼器註冊表和基底類別.
                                                             (line   99)
* getEncoding() (xml.sax.xmlreader.InputSource 的方法): InputSource 物件.
                                                             (line   32)
* getencoding() (於 locale 模組中):      locale --- 國際化服務.
                                                             (line  397)
* getEntityResolver() (xml.sax.xmlreader.XMLReader 的方法): XMLReader 物件.
                                                             (line   39)
* getenv() (於 os 模組中):               行程參數.           (line  135)
* getenvb() (於 os 模組中):              行程參數.           (line  151)
* getErrorHandler() (xml.sax.xmlreader.XMLReader 的方法): XMLReader 物件.
                                                             (line   50)
* geteuid() (於 os 模組中):              行程參數.           (line  185)
* getEvent() (xml.dom.pulldom.DOMEventStream 的方法): DOMEventStream 物件.
                                                             (line   11)
* getEventCategory() (logging.handlers.NTEventLogHandler 的方法): NTEventLogHandler.
                                                             (line   43)
* getEventType() (logging.handlers.NTEventLogHandler 的方法): NTEventLogHandler.
                                                             (line   49)
* getException() (xml.sax.SAXException 的方法): SAXException 物件.
                                                             (line   13)
* getFeature() (xml.sax.xmlreader.XMLReader 的方法): XMLReader 物件.
                                                             (line   69)
* getfile() (於 inspect 模組中):         取得原始碼.         (line   27)
* getFilesToDelete() (logging.handlers.TimedRotatingFileHandler 的方法): TimedRotatingFileHandler.
                                                             (line  115)
* getfilesystemencodeerrors() (於 sys 模組中): sys --- 系統特定的參數與函式.
                                                             (line  794)
* getfilesystemencoding() (於 sys 模組中): sys --- 系統特定的參數與函式.
                                                             (line  763)
* getfloat() (configparser.ConfigParser 的方法): ConfigParser 物件.
                                                             (line  242)
* getfqdn() (於 socket 模組中):          其他函式<2>.        (line   71)
* getframeinfo() (於 inspect 模組中):    直譯器堆疊.         (line  123)
* getframerate() (wave.Wave_read 的方法): Wave_read 物件.    (line   25)
* getfullargspec() (於 inspect 模組中):  類別與函式.         (line   17)
* getgeneratorlocals() (於 inspect 模組中): Current State of Generators Coroutines and Asynchronous Generators.
                                                             (line   72)
* getgeneratorstate() (於 inspect 模組中): Current State of Generators Coroutines and Asynchronous Generators.
                                                             (line   12)
* getgid() (於 os 模組中):               行程參數.           (line  191)
* getgrall() (於 grp 模組中):            grp --- 群組資料庫. (line   58)
* getgrgid() (於 grp 模組中):            grp --- 群組資料庫. (line   44)
* getgrnam() (於 grp 模組中):            grp --- 群組資料庫. (line   53)
* getgrouplist() (於 os 模組中):         行程參數.           (line  200)
* getgroups() (於 os 模組中):            行程參數.           (line  211)
* getHandlerByName() (於 logging 模組中): Module-Level Functions.
                                                             (line  183)
* getHandlerNames() (於 logging 模組中): Module-Level Functions.
                                                             (line  190)
* getheader() (http.client.HTTPResponse 的方法): HTTPResponse 物件.
                                                             (line   24)
* getheaders() (http.client.HTTPResponse 的方法): HTTPResponse 物件.
                                                             (line   32)
* gethostbyaddr() (於 socket 模組中):    其他函式<2>.        (line  127)
* gethostbyaddr()（於 socket 模組）:     行程參數.           (line  552)
* gethostbyname_ex() (於 socket 模組中): 其他函式<2>.        (line   98)
* gethostbyname() (於 socket 模組中):    其他函式<2>.        (line   83)
* gethostname() (於 socket 模組中):      其他函式<2>.        (line  115)
* gethostname()（於 socket 模組）:       行程參數.           (line  552)
* getincrementaldecoder() (於 codecs 模組中): codecs --- 編解碼器註冊表和基底類別.
                                                             (line  123)
* getincrementalencoder() (於 codecs 模組中): codecs --- 編解碼器註冊表和基底類別.
                                                             (line  115)
* getinfo() (zipfile.ZipFile 的方法):    ZipFile 物件.       (line  110)
* getinnerframes() (於 inspect 模組中):  直譯器堆疊.         (line  145)
* GetInputContext() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line   37)
* getint() (configparser.ConfigParser 的方法): ConfigParser 物件.
                                                             (line  235)
* getitem() (於 operator 模組中):        operator --- 標準運算子替代函式.
                                                             (line  183)
* getiterfunc (C type):                  Slot Type typedefs. (line   88)
* getitimer() (於 signal 模組中):        模組內容<5>.        (line  434)
* getkey() (curses.window 的方法):       Window Objects.     (line  248)
* GetLastError() (於 ctypes 模組中):     Utility functions.  (line  113)
* getLength() (xml.sax.xmlreader.Attributes 的方法): The Attributes Interface.
                                                             (line   11)
* getLevelName() (於 logging 模組中):    Module-Level Functions.
                                                             (line  150)
* getLevelNamesMapping() (於 logging 模組中): Module-Level Functions.
                                                             (line  141)
* getlimit() (sqlite3.Connection 的方法): Connection 物件.   (line  588)
* getline() (於 linecache 模組中):       linecache --- 隨機存取文字列.
                                                             (line   23)
* getLineNumber() (xml.sax.xmlreader.Locator 的方法): Locator Objects.
                                                             (line   12)
* getloadavg() (於 os 模組中):           Miscellaneous System Information.
                                                             (line   52)
* getlocale() (於 locale 模組中):        locale --- 國際化服務.
                                                             (line  362)
* getLogger() (於 logging 模組中):       Module-Level Functions.
                                                             (line    9)
* getLoggerClass() (於 logging 模組中):  Module-Level Functions.
                                                             (line   23)
* getlogin() (於 os 模組中):             行程參數.           (line  234)
* getLogRecordFactory() (於 logging 模組中): Module-Level Functions.
                                                             (line   34)
* getMandatoryRelease() (__future__._Feature 的方法): 模組內容<9>.
                                                             (line   69)
* getmark() (wave.Wave_read 的方法):     Wave_read 物件.     (line   67)
* getmarkers() (wave.Wave_read 的方法):  Wave_read 物件.     (line   59)
* getmaxyx() (curses.window 的方法):     Window Objects.     (line  255)
* getmember() (tarfile.TarFile 的方法):  TarFile 物件.       (line  102)
* getmembers_static() (於 inspect 模組中): Types and members.
                                                             (line  321)
* getmembers() (tarfile.TarFile 的方法): TarFile 物件.       (line  110)
* getmembers() (於 inspect 模組中):      Types and members.  (line  308)
* getMessage() (logging.LogRecord 的方法): LogRecord 物件.   (line   64)
* getMessage() (xml.sax.SAXException 的方法): SAXException 物件.
                                                             (line    9)
* getMessageID() (logging.handlers.NTEventLogHandler 的方法): NTEventLogHandler.
                                                             (line   60)
* getmodule() (於 inspect 模組中):       取得原始碼.         (line   33)
* getmodulename() (於 inspect 模組中):   Types and members.  (line  337)
* getmouse() (於 curses 模組中):         函式<5>.            (line  145)
* getmro() (於 inspect 模組中):          類別與函式.         (line   84)
* getmtime() (於 os.path 模組中):        os path --- 常見的路徑名操作.
                                                             (line  157)
* getName() (threading.Thread 的方法):   Thread Objects.     (line  159)
* getNameByQName() (xml.sax.xmlreader.AttributesNS 的方法): The AttributesNS Interface.
                                                             (line   16)
* getnameinfo() (asyncio.loop 的方法):   DNS.                (line   11)
* getnameinfo() (於 socket 模組中):      其他函式<2>.        (line  143)
* getnames() (tarfile.TarFile 的方法):   TarFile 物件.       (line  116)
* getNames() (xml.sax.xmlreader.Attributes 的方法): The Attributes Interface.
                                                             (line   15)
* getnchannels() (wave.Wave_read 的方法): Wave_read 物件.    (line   17)
* getnframes() (wave.Wave_read 的方法):  Wave_read 物件.     (line   29)
* getnode:                               uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  167)
* getnode() (於 uuid 模組中):            uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  153)
* getopt() (於 getopt 模組中):           getopt --- 用於命令列選項的 C 風格剖析器.
                                                             (line   29)
* GetoptError:                           getopt --- 用於命令列選項的 C 風格剖析器.
                                                             (line   78)
* getOptionalRelease() (__future__._Feature 的方法): 模組內容<9>.
                                                             (line   65)
* getouterframes() (於 inspect 模組中):  直譯器堆疊.         (line  131)
* getoutput() (於 subprocess 模組中):    Legacy Shell Invocation Functions.
                                                             (line   44)
* getpagesize() (於 resource 模組中):    Resource Usage.     (line  101)
* getparams() (wave.Wave_read 的方法):   Wave_read 物件.     (line   42)
* getparyx() (curses.window 的方法):     Window Objects.     (line  259)
* getpass() (於 getpass 模組中):         getpass --- 可攜式密碼輸入工具.
                                                             (line   17)
* GetPassWarning:                        getpass --- 可攜式密碼輸入工具.
                                                             (line   33)
* getpeercert() (ssl.SSLSocket 的方法):  SSL Sockets.        (line  130)
* getpeername() (socket.socket 的方法):  Socket 物件.        (line  135)
* getpen() (於 turtle 模組中):           Special Turtle methods.
                                                             (line   40)
* getpgid() (於 os 模組中):              行程參數.           (line  245)
* getpgrp() (於 os 模組中):              行程參數.           (line  253)
* getpid() (於 os 模組中):               行程參數.           (line  259)
* getpos() (html.parser.HTMLParser 的方法): HTMLParser 方法. (line   24)
* getppid() (於 os 模組中):              行程參數.           (line  266)
* getpreferredencoding() (於 locale 模組中): locale --- 國際化服務.
                                                             (line  373)
* getpriority() (於 os 模組中):          行程參數.           (line  277)
* getprofile() (於 sys 模組中):          sys --- 系統特定的參數與函式.
                                                             (line  900)
* getprofile() (於 threading 模組中):    threading --- 基於執行緒的平行性.
                                                             (line  200)
* getProperty() (xml.sax.xmlreader.XMLReader 的方法): XMLReader 物件.
                                                             (line   83)
* getprotobyname() (於 socket 模組中):   其他函式<2>.        (line  163)
* getproxies() (於 urllib.request 模組中): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  145)
* getPublicId() (xml.sax.xmlreader.InputSource 的方法): InputSource 物件.
                                                             (line   10)
* getPublicId() (xml.sax.xmlreader.Locator 的方法): Locator Objects.
                                                             (line   16)
* getpwall() (於 pwd 模組中):            pwd --- 密碼資料庫. (line   62)
* getpwnam() (於 pwd 模組中):            pwd --- 密碼資料庫. (line   58)
* getpwuid() (於 pwd 模組中):            pwd --- 密碼資料庫. (line   54)
* getQNameByName() (xml.sax.xmlreader.AttributesNS 的方法): The AttributesNS Interface.
                                                             (line   20)
* getQNames() (xml.sax.xmlreader.AttributesNS 的方法): The AttributesNS Interface.
                                                             (line   24)
* getquota() (imaplib.IMAP4 的方法):     IMAP4 物件.         (line  116)
* getquotaroot() (imaplib.IMAP4 的方法): IMAP4 物件.         (line  121)
* getrandbits() (random.Random 的方法):  替代產生器.         (line   39)
* getrandbits() (於 random 模組中):      回傳整數的函式.     (line   33)
* getrandom() (於 os 模組中):            Random numbers.     (line    6)
* getreader() (於 codecs 模組中):        codecs --- 編解碼器註冊表和基底類別.
                                                             (line  131)
* getrecursionlimit() (於 sys 模組中):   sys --- 系統特定的參數與函式.
                                                             (line  835)
* getrefcount() (於 sys 模組中):         sys --- 系統特定的參數與函式.
                                                             (line  819)
* GetReparseDeferralEnabled() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line  111)
* getresgid() (於 os 模組中):            行程參數.           (line  324)
* getresponse() (http.client.HTTPConnection 的方法): HTTPConnection 物件.
                                                             (line   74)
* getresuid() (於 os 模組中):            行程參數.           (line  315)
* getrlimit() (於 resource 模組中):      Resource Limits.    (line   24)
* getroot() (xml.etree.ElementTree.ElementTree 的方法): ElementTree 物件.
                                                             (line   36)
* getrusage() (於 resource 模組中):      Resource Usage.     (line    8)
* getsampwidth() (wave.Wave_read 的方法): Wave_read 物件.    (line   21)
* getscreen() (於 turtle 模組中):        Special Turtle methods.
                                                             (line   51)
* getservbyname() (於 socket 模組中):    其他函式<2>.        (line  174)
* getservbyport() (於 socket 模組中):    其他函式<2>.        (line  185)
* GetSetDescriptorType (於 types 模組中): Standard Interpreter Types.
                                                             (line  243)
* getshapes() (於 turtle 模組中):        Settings and special methods.
                                                             (line   63)
* getsid() (於 os 模組中):               行程參數.           (line  510)
* getsignal() (於 signal 模組中):        模組內容<5>.        (line  284)
* getsitepackages() (於 site 模組中):    模組內容<10>.       (line   57)
* getsize() (於 os.path 模組中):         os path --- 常見的路徑名操作.
                                                             (line  174)
* getsizeof() (於 sys 模組中):           sys --- 系統特定的參數與函式.
                                                             (line  842)
* getsockname() (socket.socket 的方法):  Socket 物件.        (line  143)
* getsockopt() (socket.socket 的方法):   Socket 物件.        (line  149)
* getsource() (於 inspect 模組中):       取得原始碼.         (line   59)
* getsourcefile() (於 inspect 模組中):   取得原始碼.         (line   38)
* getsourcelines() (於 inspect 模組中):  取得原始碼.         (line   45)
* getstate() (codecs.IncrementalDecoder 的方法): IncrementalDecoder 物件.
                                                             (line   44)
* getstate() (codecs.IncrementalEncoder 的方法): IncrementalEncoder 物件.
                                                             (line   42)
* getstate() (random.Random 的方法):     替代產生器.         (line   22)
* getstate() (於 random 模組中):         簿記函式 bookkeeping functions.
                                                             (line   28)
* getstatusoutput() (於 subprocess 模組中): Legacy Shell Invocation Functions.
                                                             (line   11)
* getstr() (curses.window 的方法):       Window Objects.     (line  265)
* getSubject() (logging.handlers.SMTPHandler 的方法): SMTPHandler.
                                                             (line   39)
* getswitchinterval() (於 sys 模組中):   sys --- 系統特定的參數與函式.
                                                             (line  864)
* getSystemId() (xml.sax.xmlreader.InputSource 的方法): InputSource 物件.
                                                             (line   18)
* getSystemId() (xml.sax.xmlreader.Locator 的方法): Locator Objects.
                                                             (line   20)
* getsyx() (於 curses 模組中):           函式<5>.            (line  163)
* gettarinfo() (tarfile.TarFile 的方法): TarFile 物件.       (line  300)
* gettempdir() (於 tempfile 模組中):     tempfile --- 生成臨時檔案和目錄.
                                                             (line  269)
* gettempdirb() (於 tempfile 模組中):    tempfile --- 生成臨時檔案和目錄.
                                                             (line  299)
* gettempprefix() (於 tempfile 模組中):  tempfile --- 生成臨時檔案和目錄.
                                                             (line  305)
* gettempprefixb() (於 tempfile 模組中): tempfile --- 生成臨時檔案和目錄.
                                                             (line  309)
* getter (C type):                       Defining Getters and Setters.
                                                             (line   33)
* getTestCaseNames() (unittest.TestLoader 的方法): Loading and running tests.
                                                             (line  111)
* gettext() (gettext.GNUTranslations 的方法): The GNUTranslations class.
                                                             (line   38)
* gettext() (gettext.NullTranslations 的方法): The NullTranslations class.
                                                             (line   35)
* gettext() (於 gettext 模組中):         GNU gettext API.    (line   32)
* gettext() (於 locale 模組中):          Access to message catalogs.
                                                             (line    6)
* gettimeout() (socket.socket 的方法):   Socket 物件.        (line  173)
* gettrace() (於 sys 模組中):            sys --- 系統特定的參數與函式.
                                                             (line  904)
* gettrace() (於 threading 模組中):      threading --- 基於執行緒的平行性.
                                                             (line  176)
* getturtle() (於 turtle 模組中):        Special Turtle methods.
                                                             (line   40)
* getType() (xml.sax.xmlreader.Attributes 的方法): The Attributes Interface.
                                                             (line   19)
* getuid() (於 os 模組中):               行程參數.           (line  333)
* getunicodeinternedsize() (於 sys 模組中): sys --- 系統特定的參數與函式.
                                                             (line  732)
* geturl() (http.client.HTTPResponse 的方法): HTTPResponse 物件.
                                                             (line   79)
* geturl() (urllib.parse.urllib.parse.SplitResult 的方法): Structured Parse Results.
                                                             (line   12)
* geturl() (urllib.response.addinfourl 的方法): urllib response --- Response classes used by urllib.
                                                             (line   30)
* getuser() (於 getpass 模組中):         getpass --- 可攜式密碼輸入工具.
                                                             (line   37)
* getuserbase() (於 site 模組中):        模組內容<10>.       (line   63)
* getusersitepackages() (於 site 模組中): 模組內容<10>.      (line   71)
* getvalue() (io.BytesIO 的方法):        Buffered Streams.   (line   38)
* getvalue() (io.StringIO 的方法):       文字 I/O<2>.        (line  263)
* getValue() (xml.sax.xmlreader.Attributes 的方法): The Attributes Interface.
                                                             (line   24)
* getValueByQName() (xml.sax.xmlreader.AttributesNS 的方法): The AttributesNS Interface.
                                                             (line   12)
* getwch() (於 msvcrt 模組中):           Console I/O.        (line   21)
* getwche() (於 msvcrt 模組中):          Console I/O.        (line   31)
* getweakrefcount() (於 weakref 模組中): weakref --- 弱參照. (line  120)
* getweakrefs() (於 weakref 模組中):     weakref --- 弱參照. (line  124)
* getwelcome() (ftplib.FTP 的方法):      FTP 物件.           (line  108)
* getwelcome() (poplib.POP3 的方法):     POP3 物件.          (line   20)
* getwin() (於 curses 模組中):           函式<5>.            (line  169)
* getwindowsversion() (於 sys 模組中):   sys --- 系統特定的參數與函式.
                                                             (line  914)
* getwriter() (於 codecs 模組中):        codecs --- 編解碼器註冊表和基底類別.
                                                             (line  139)
* getxattr() (於 os 模組中):             Linux extended attributes.
                                                             (line   10)
* getyx() (curses.window 的方法):        Window Objects.     (line  276)
* gid (tarfile.TarInfo 的屬性):          TarInfo 物件.       (line  113)
* GIL:                                   術語表.             (line  533)
* glob() (pathlib.Path 的方法):          讀取目錄.           (line   28)
* glob() (於 glob 模組中):               glob --- Unix 風格的路徑名稱模式擴展.
                                                             (line   26)
* Global (ast 中的類別):                 函式和類別定義.     (line  137)
* global interpreter lock（全域直譯器鎖）: Thread State and the Global Interpreter Lock.
                                                             (line    6)
* global interpreter lock（全域直譯器鎖） <1>: 術語表.       (line  537)
* global_enum() (於 enum 模組中):        通用項目與裝飾器.   (line   84)
* global;name（名稱）;binding（繫結）:   global 陳述式.      (line    6)
* global（全域）;namespace（命名空間）:  特殊唯讀屬性.       (line    6)
* globs (doctest.DocTest 的屬性):        DocTest 物件.       (line   22)
* gmtime() (於 time 模組中):             函式<4>.            (line  124)
* gname (tarfile.TarInfo 的屬性):        TarInfo 物件.       (line  129)
* GNOME:                                 The Catalog constructor.
                                                             (line    6)
* GNU_FORMAT (於 tarfile 模組中):        tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  320)
* gnu_getopt() (於 getopt 模組中):       getopt --- 用於命令列選項的 C 風格剖析器.
                                                             (line   66)
* GNUTranslations (gettext 中的類別):    The GNUTranslations class.
                                                             (line   33)
* GNUTYPE_LONGLINK (於 tarfile 模組中):  tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  304)
* GNUTYPE_LONGNAME (於 tarfile 模組中):  tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  300)
* GNUTYPE_SPARSE (於 tarfile 模組中):    tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  308)
* go() (tkinter.filedialog.FileDialog 的方法): Native Load/Save Dialogs.
                                                             (line  114)
* got (doctest.DocTestFailure 的屬性):   Debugging.          (line  204)
* goto() (於 turtle 模組中):             Turtle motion.      (line   74)
* grammar（文法）:                       Notation.           (line    6)
* grantpt() (於 os 模組中):              File Descriptor Operations.
                                                             (line  247)
* Graphical User Interface（圖形使用者介面）: 以 Tk 打造圖形使用者介面 Graphical User Interfaces.
                                                             (line    6)
* GREATER (於 token 模組中):             token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  110)
* GREATEREQUAL (於 token 模組中):        token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  146)
* Greenwich Mean Time（格林威治標準時間）: time --- 時間存取與轉換.
                                                             (line   32)
* GRND_NONBLOCK (於 os 模組中):          Random numbers.     (line   76)
* GRND_RANDOM (於 os 模組中):            Random numbers.     (line   89)
* Group (email.headerregistry 中的類別): email headerregistry：自訂標頭物件.
                                                             (line  456)
* group() (pathlib.Path 的方法):         Permissions and ownership.
                                                             (line   21)
* group() (re.Match 的方法):             Match Objects.      (line   35)
* groupby() (於 itertools 模組中):       Itertool 函式.      (line  277)
* groupdict() (re.Match 的方法):         Match Objects.      (line  135)
* groupindex (re.Pattern 的屬性):        Regular Expression Objects.
                                                             (line  117)
* grouping（群組）:                      Indentation.        (line    6)
* groups (email.headerregistry.AddressHeader 的屬性): email headerregistry：自訂標頭物件.
                                                             (line  188)
* groups (re.Pattern 的屬性):            Regular Expression Objects.
                                                             (line  113)
* groups() (re.Match 的方法):            Match Objects.      (line  112)
* GS (於 curses.ascii 模組中):           curses ascii --- ASCII 字元的工具程式.
                                                             (line  112)
* Gt (ast 中的類別):                     運算式<2>.          (line  105)
* gt() (於 operator 模組中):             operator --- 標準運算子替代函式.
                                                             (line   20)
* GtE (ast 中的類別):                    運算式<2>.          (line  105)
* guard:                                 Guards.             (line    6)
* guess_all_extensions() (mimetypes.MimeTypes 的方法): MimeTypes 物件.
                                                             (line   72)
* guess_all_extensions() (於 mimetypes 模組中): mimetypes --- 將檔案名稱對映到 MIME 類型.
                                                             (line   63)
* guess_extension() (mimetypes.MimeTypes 的方法): MimeTypes 物件.
                                                             (line   55)
* guess_extension() (於 mimetypes 模組中): mimetypes --- 將檔案名稱對映到 MIME 類型.
                                                             (line   75)
* guess_file_type() (mimetypes.MimeTypes 的方法): MimeTypes 物件.
                                                             (line   65)
* guess_file_type() (於 mimetypes 模組中): mimetypes --- 將檔案名稱對映到 MIME 類型.
                                                             (line   54)
* guess_scheme() (於 wsgiref.util 模組中): wsgiref util -- WSGI 環境工具.
                                                             (line   11)
* guess_type() (mimetypes.MimeTypes 的方法): MimeTypes 物件. (line   60)
* guess_type() (於 mimetypes 模組中):    mimetypes --- 將檔案名稱對映到 MIME 類型.
                                                             (line   24)
* GUI:                                   以 Tk 打造圖形使用者介面 Graphical User Interfaces.
                                                             (line    6)
* gzip 命令列選項; -best:                命令列選項.         (line   14)
* gzip 命令列選項; -d:                   命令列選項.         (line   18)
* gzip 命令列選項; -decompress:          命令列選項.         (line   18)
* gzip 命令列選項; -fast:                命令列選項.         (line   10)
* gzip 命令列選項; -h:                   命令列選項.         (line   22)
* gzip 命令列選項; -help:                命令列選項.         (line   22)
* gzip 命令列選項; file:                 命令列選項.         (line    6)
* GzipFile (gzip 中的類別):              gzip --- gzip 檔案的支援.
                                                             (line   70)
* halfdelay() (於 curses 模組中):        函式<5>.            (line  211)
* Handle (asyncio 中的類別):             回呼處理.           (line    6)
* handle an exception（處理例外）:       例外.               (line    6)
* handle_charref() (html.parser.HTMLParser 的方法): HTMLParser 方法.
                                                             (line   75)
* handle_comment() (html.parser.HTMLParser 的方法): HTMLParser 方法.
                                                             (line   82)
* handle_data() (html.parser.HTMLParser 的方法): HTMLParser 方法.
                                                             (line   64)
* handle_decl() (html.parser.HTMLParser 的方法): HTMLParser 方法.
                                                             (line   94)
* handle_defect() (email.policy.Policy 的方法): email policy Policy Objects.
                                                             (line  235)
* handle_endtag() (html.parser.HTMLParser 的方法): HTMLParser 方法.
                                                             (line   51)
* handle_entityref() (html.parser.HTMLParser 的方法): HTMLParser 方法.
                                                             (line   69)
* handle_error() (socketserver.BaseServer 的方法): Server Objects.
                                                             (line  137)
* handle_expect_100() (http.server.BaseHTTPRequestHandler 的方法): http server — HTTP 伺服器.
                                                             (line  205)
* handle_one_request() (http.server.BaseHTTPRequestHandler 的方法): http server — HTTP 伺服器.
                                                             (line  199)
* handle_pi() (html.parser.HTMLParser 的方法): HTMLParser 方法.
                                                             (line  102)
* handle_request() (socketserver.BaseServer 的方法): Server Objects.
                                                             (line   21)
* handle_request() (xmlrpc.server.CGIXMLRPCRequestHandler 的方法): CGIXMLRPCRequestHandler.
                                                             (line   50)
* handle_startendtag() (html.parser.HTMLParser 的方法): HTMLParser 方法.
                                                             (line   57)
* handle_starttag() (html.parser.HTMLParser 的方法): HTMLParser 方法.
                                                             (line   37)
* handle_timeout() (socketserver.BaseServer 的方法): Server Objects.
                                                             (line  147)
* handle() (http.server.BaseHTTPRequestHandler 的方法): http server — HTTP 伺服器.
                                                             (line  192)
* handle() (logging.Handler 的方法):     Handler Objects.    (line   81)
* handle() (logging.handlers.QueueListener 的方法): QueueListener.
                                                             (line   66)
* handle() (logging.Logger 的方法):      Logger 物件.        (line  362)
* handle() (logging.NullHandler 的方法): NullHandler.        (line   20)
* handle() (socketserver.BaseRequestHandler 的方法): Request Handler Objects.
                                                             (line   20)
* handle() (wsgiref.simple_server.WSGIRequestHandler 的方法): wsgiref simple_server -- 一個簡單的 WSGI HTTP 伺服器.
                                                             (line   93)
* handleError() (logging.Handler 的方法): Handler Objects.   (line   88)
* handleError() (logging.handlers.SocketHandler 的方法): SocketHandler.
                                                             (line   33)
* Handler (logging 中的類別):            Handler Objects.    (line   11)
* handlers (logging.Logger 的屬性):      Logger 物件.        (line   85)
* Handlers (signal 中的類別):            模組內容<5>.        (line   24)
* hardlink_to() (pathlib.Path 的方法):   建立檔案與目錄.     (line   67)
* harmonic_mean() (於 statistics 模組中): 函式細節.          (line   87)
* HAS_ALPN (於 ssl 模組中):              常數<8>.            (line  337)
* has_children() (symtable.SymbolTable 的方法): 檢查符號表.  (line   94)
* has_colors() (於 curses 模組中):       函式<5>.            (line  176)
* has_default() (typing.ParamSpec 的方法): Building generic types and type aliases.
                                                             (line  433)
* has_default() (typing.TypeVar 的方法): Building generic types and type aliases.
                                                             (line  201)
* has_default() (typing.TypeVarTuple 的方法): Building generic types and type aliases.
                                                             (line  333)
* has_dualstack_ipv6() (於 socket 模組中): 建立 sockets.     (line  150)
* HAS_ECDH (於 ssl 模組中):              常數<8>.            (line  351)
* has_extended_color_support() (於 curses 模組中): 函式<5>.  (line  181)
* has_extn() (smtplib.SMTP 的方法):      SMTP 物件.          (line   85)
* has_header() (csv.Sniffer 的方法):     模組內容<3>.        (line  215)
* has_header() (urllib.request.Request 的方法): Request Objects.
                                                             (line   94)
* has_ic() (於 curses 模組中):           函式<5>.            (line  192)
* has_il() (於 curses 模組中):           函式<5>.            (line  199)
* has_ipv6 (於 socket 模組中):           常數<7>.            (line  289)
* has_key() (於 curses 模組中):          函式<5>.            (line  206)
* has_location (importlib.machinery.ModuleSpec 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  432)
* HAS_NEVER_CHECK_COMMON_NAME (於 ssl 模組中): 常數<8>.      (line  344)
* has_nonstandard_attr() (http.cookiejar.Cookie 的方法): Cookie 物件<2>.
                                                             (line   98)
* HAS_NPN (於 ssl 模組中):               常數<8>.            (line  366)
* has_option() (configparser.ConfigParser 的方法): ConfigParser 物件.
                                                             (line  133)
* has_option() (optparse.OptionParser 的方法): Querying and manipulating your option parser.
                                                             (line   42)
* HAS_PSK (於 ssl 模組中):               常數<8>.            (line  410)
* has_section() (configparser.ConfigParser 的方法): ConfigParser 物件.
                                                             (line  124)
* HAS_SNI (於 ssl 模組中):               常數<8>.            (line  359)
* HAS_SSLv2 (於 ssl 模組中):             常數<8>.            (line  374)
* HAS_SSLv3 (於 ssl 模組中):             常數<8>.            (line  380)
* has_ticket (ssl.SSLSession 的屬性):    SSL session.        (line   20)
* HAS_TLSv1 (於 ssl 模組中):             常數<8>.            (line  386)
* HAS_TLSv1_1 (於 ssl 模組中):           常數<8>.            (line  392)
* HAS_TLSv1_2 (於 ssl 模組中):           常數<8>.            (line  398)
* HAS_TLSv1_3 (於 ssl 模組中):           常數<8>.            (line  404)
* hasarg (於 dis 模組中):                Opcode collections. (line   25)
* hasAttribute() (xml.dom.Element 的方法): Element Objects.  (line   22)
* hasAttributeNS() (xml.dom.Element 的方法): Element Objects.
                                                             (line   26)
* hasAttributes() (xml.dom.Node 的方法): Node Objects.       (line   94)
* hasChildNodes() (xml.dom.Node 的方法): Node Objects.       (line   98)
* hascompare (於 dis 模組中):            Opcode collections. (line   58)
* hasconst (於 dis 模組中):              Opcode collections. (line   31)
* hasexc (於 dis 模組中):                Opcode collections. (line   62)
* hasFeature() (xml.dom.DOMImplementation 的方法): DOMImplementation 物件.
                                                             (line   11)
* hasfree (於 dis 模組中):               Opcode collections. (line   35)
* hash character（井字號）:              Comments.           (line    6)
* hash_bits (sys.hash_info 的屬性):      sys --- 系統特定的參數與函式.
                                                             (line 1022)
* hash_info (於 sys 模組中):             sys --- 系統特定的參數與函式.
                                                             (line  991)
* hash_randomization (sys.flags 的屬性): sys --- 系統特定的參數與函式.
                                                             (line  558)
* hash-based pyc（雜湊架構的 pyc）:      術語表.             (line  558)
* hash.block_size (於 hashlib 模組中):   雜湊物件.           (line   12)
* hash.digest_size (於 hashlib 模組中):  雜湊物件.           (line    8)
* Hashable (collections.abc 中的類別):   Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line   11)
* Hashable (typing 中的類別):            Aliases to other ABCs in collections abc.
                                                             (line   53)
* hashable（可雜湊）:                    Dictionary displays.
                                                             (line   37)
* hashable（可雜湊的）:                  術語表.             (line  564)
* hasHandlers() (logging.Logger 的方法): Logger 物件.        (line  377)
* hashfunc (C type):                     Slot Type typedefs. (line   79)
* hasjabs (於 dis 模組中):               Opcode collections. (line   75)
* hasjrel (於 dis 模組中):               Opcode collections. (line   68)
* hasjump (於 dis 模組中):               Opcode collections. (line   47)
* haslocal (於 dis 模組中):              Opcode collections. (line   54)
* hasname (於 dis 模組中):               Opcode collections. (line   43)
* HAVE_ARGUMENT (opcode):                Python Bytecode Instructions.
                                                             (line 1243)
* HAVE_CONTEXTVAR (於 decimal 模組中):   常數<4>.            (line   32)
* HAVE_DOCSTRINGS (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  161)
* HAVE_THREADS (於 decimal 模組中):      常數<4>.            (line   25)
* HCI_DATA_DIR (於 socket 模組中):       常數<7>.            (line  302)
* HCI_FILTER (於 socket 模組中):         常數<7>.            (line  302)
* HCI_TIME_STAMP (於 socket 模組中):     常數<7>.            (line  302)
* Header (email.header 中的類別):        email header：國際化標頭.
                                                             (line   60)
* header_encode_lines() (email.charset.Charset 的方法): email charset：表示字元集合.
                                                             (line  123)
* header_encode() (email.charset.Charset 的方法): email charset：表示字元集合.
                                                             (line  116)
* header_encoding (email.charset.Charset 的屬性): email charset：表示字元集合.
                                                             (line   57)
* header_factory (email.policy.EmailPolicy 的屬性): email policy Policy Objects.
                                                             (line  408)
* header_fetch_parse() (email.policy.Compat32 的方法): email policy Policy Objects.
                                                             (line  594)
* header_fetch_parse() (email.policy.EmailPolicy 的方法): email policy Policy Objects.
                                                             (line  458)
* header_fetch_parse() (email.policy.Policy 的方法): email policy Policy Objects.
                                                             (line  319)
* header_items() (urllib.request.Request 的方法): Request Objects.
                                                             (line  125)
* header_max_count() (email.policy.EmailPolicy 的方法): email policy Policy Objects.
                                                             (line  435)
* header_max_count() (email.policy.Policy 的方法): email policy Policy Objects.
                                                             (line  260)
* header_offset (zipfile.ZipInfo 的屬性): ZipInfo 物件.      (line  131)
* header_source_parse() (email.policy.Compat32 的方法): email policy Policy Objects.
                                                             (line  582)
* header_source_parse() (email.policy.EmailPolicy 的方法): email policy Policy Objects.
                                                             (line  441)
* header_source_parse() (email.policy.Policy 的方法): email policy Policy Objects.
                                                             (line  282)
* header_store_parse() (email.policy.Compat32 的方法): email policy Policy Objects.
                                                             (line  590)
* header_store_parse() (email.policy.EmailPolicy 的方法): email policy Policy Objects.
                                                             (line  449)
* header_store_parse() (email.policy.Policy 的方法): email policy Policy Objects.
                                                             (line  303)
* HeaderDefect:                          email errors：例外和缺陷類別.
                                                             (line   67)
* HeaderError:                           tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  223)
* HeaderParseError:                      email errors：例外和缺陷類別.
                                                             (line   26)
* HeaderParser (email.parser 中的類別):  Parser API.         (line  105)
* HeaderRegistry (email.headerregistry 中的類別): email headerregistry：自訂標頭物件.
                                                             (line  299)
* headers (http.client.HTTPResponse 的屬性): HTTPResponse 物件.
                                                             (line   56)
* headers (http.server.BaseHTTPRequestHandler 的屬性): http server — HTTP 伺服器.
                                                             (line  109)
* headers (urllib.error.HTTPError 的屬性): urllib error --- urllib request 引發的例外類別.
                                                             (line   49)
* headers (urllib.response.addinfourl 的屬性): urllib response --- Response classes used by urllib.
                                                             (line   19)
* Headers (wsgiref.headers 中的類別):    wsgiref headers -- WSGI 回應標頭工具.
                                                             (line    9)
* headers (xmlrpc.client.ProtocolError 的屬性): ProtocolError 物件.
                                                             (line   25)
* HeaderWriteError:                      email errors：例外和缺陷類別.
                                                             (line   57)
* heading() (tkinter.ttk.Treeview 的方法): ttk Treeview.     (line   99)
* heading() (於 turtle 模組中):          Tell Turtle's state.
                                                             (line   58)
* heapify() (於 heapq 模組中):           heapq --- 堆積佇列 heap queue 演算法.
                                                             (line   50)
* heapmin() (於 msvcrt 模組中):          Other Functions.    (line    6)
* heappop() (於 heapq 模組中):           heapq --- 堆積佇列 heap queue 演算法.
                                                             (line   38)
* heappush() (於 heapq 模組中):          heapq --- 堆積佇列 heap queue 演算法.
                                                             (line   34)
* heappushpop() (於 heapq 模組中):       heapq --- 堆積佇列 heap queue 演算法.
                                                             (line   44)
* heapreplace() (於 heapq 模組中):       heapq --- 堆積佇列 heap queue 演算法.
                                                             (line   54)
* helo() (smtplib.SMTP 的方法):          SMTP 物件.          (line   47)
* help (optparse.Option 的屬性):         Option attributes.  (line   80)
* help (pdb command):                    Debugger Commands.  (line   73)
* help（幫助）;online（線上）:           pydoc --- 文件產生器與線上幫助系統.
                                                             (line    8)
* herror:                                例外<10>.           (line   13)
* hex (uuid.UUID 的屬性):                uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  121)
* hex() (bytearray 的方法):              Bytearray Objects.  (line   52)
* hex() (bytes 的方法):                  Bytes Objects.      (line   78)
* hex() (float 的方法):                  浮點數的附加 methods.
                                                             (line   30)
* hex() (memoryview 的方法):             Memory Views.       (line  187)
* hexadecimal literal（十六進位常數）:   Numeric literals.   (line    6)
* hexadecimal（十六進位）;literals（字面值）: 數值型別 --- int、float、complex.
                                                             (line   15)
* hexdigest() (hashlib.hash 的方法):     雜湊物件.           (line   39)
* hexdigest() (hashlib.shake 的方法):    SHAKE 可變長度摘要. (line   20)
* hexdigest() (hmac.HMAC 的方法):        hmac --- 基於金鑰雜湊的訊息驗證.
                                                             (line   60)
* hexdigits (於 string 模組中):          字串常數.           (line   27)
* hexlify() (於 binascii 模組中):        binascii --- 在二進位制和 ASCII 之間轉換.
                                                             (line  114)
* hexversion (於 sys 模組中):            sys --- 系統特定的參數與函式.
                                                             (line 1034)
* hidden() (curses.panel.Panel 的方法):  Panel Objects.      (line   25)
* hide_cookie2 (http.cookiejar.CookiePolicy 的屬性): CookiePolicy 物件.
                                                             (line   76)
* hide() (curses.panel.Panel 的方法):    Panel Objects.      (line   30)
* hide() (tkinter.ttk.Notebook 的方法):  ttk Notebook.       (line   22)
* hideturtle() (於 turtle 模組中):       Visibility.         (line    6)
* HierarchyRequestErr:                   例外<15>.           (line   29)
* HIGH_PRIORITY_CLASS (於 subprocess 模組中): Windows Constants.
                                                             (line   82)
* HIGHEST_PROTOCOL (於 pickle 模組中):   模組介面.           (line   14)
* hits (bdb.Breakpoint 的屬性):          bdb --- 偵錯器框架. (line  123)
* HKEY_CLASSES_ROOT (於 winreg 模組中):  HKEY_* Constants.   (line    6)
* HKEY_CURRENT_CONFIG (於 winreg 模組中): HKEY_* Constants.  (line   38)
* HKEY_CURRENT_USER (於 winreg 模組中):  HKEY_* Constants.   (line   12)
* HKEY_DYN_DATA (於 winreg 模組中):      HKEY_* Constants.   (line   43)
* HKEY_LOCAL_MACHINE (於 winreg 模組中): HKEY_* Constants.   (line   19)
* HKEY_PERFORMANCE_DATA (於 winreg 模組中): HKEY_* Constants.
                                                             (line   31)
* HKEY_USERS (於 winreg 模組中):         HKEY_* Constants.   (line   25)
* hline() (curses.window 的方法):        Window Objects.     (line  281)
* hls_to_rgb() (於 colorsys 模組中):     colorsys --- 顏色系統間的轉換.
                                                             (line   37)
* HOME:                                  os path<4>.         (line   15)
* HOME <1>:                              Changes in the Python API<3>.
                                                             (line  117)
* HOME <2>:                              Windows<36>.        (line   15)
* HOME <3>:                              Windows<36>.        (line   18)
* HOME <4>:                              os path --- 常見的路徑名操作.
                                                             (line  123)
* HOME <5>:                              os path --- 常見的路徑名操作.
                                                             (line  138)
* HOME <6>:                              Tkinter Modules.    (line   66)
* home() (pathlib.Path 的類別方法):      Expanding and resolving paths.
                                                             (line    6)
* home() (於 turtle 模組中):             Turtle motion.      (line  195)
* HOMEDRIVE:                             os path --- 常見的路徑名操作.
                                                             (line  129)
* HOMEPATH:                              os path --- 常見的路徑名操作.
                                                             (line  129)
* hook_compressed() (於 fileinput 模組中): fileinput --- 逐列疊代多個輸入串流.
                                                             (line  196)
* hook_encoded() (於 fileinput 模組中):  fileinput --- 逐列疊代多個輸入串流.
                                                             (line  216)
* hooks;import（引入）:                  Import hooks.       (line    6)
* hooks;meta:                            Import hooks.       (line    6)
* hooks;path（路徑）:                    Import hooks.       (line    6)
* host (urllib.request.Request 的屬性):  Request Objects.    (line   25)
* hostmask (ipaddress.IPv4Network 的屬性): Network objects.  (line   97)
* hostmask (ipaddress.IPv6Network 的屬性): Network objects.  (line  313)
* hostname_checks_common_name (ssl.SSLContext 的屬性): SSL Contexts.
                                                             (line  617)
* hosts (netrc.netrc 的屬性):            netrc 物件.         (line   21)
* hosts() (ipaddress.IPv4Network 的方法): Network objects.   (line  136)
* hosts() (ipaddress.IPv6Network 的方法): Network objects.   (line  331)
* hour (datetime.datetime 的屬性):       datetime 物件.      (line  311)
* hour (datetime.time 的屬性):           time 物件.          (line   50)
* HRESULT (ctypes 中的類別):             Fundamental data types<2>.
                                                             (line  213)
* hStdError (subprocess.STARTUPINFO 的屬性): Windows Popen Helpers.
                                                             (line   42)
* hStdInput (subprocess.STARTUPINFO 的屬性): Windows Popen Helpers.
                                                             (line   27)
* hStdOutput (subprocess.STARTUPINFO 的屬性): Windows Popen Helpers.
                                                             (line   35)
* hsv_to_rgb() (於 colorsys 模組中):     colorsys --- 顏色系統間的轉換.
                                                             (line   45)
* HT (於 curses.ascii 模組中):           curses ascii --- ASCII 字元的工具程式.
                                                             (line   49)
* ht() (於 turtle 模組中):               Visibility.         (line    6)
* HTML:                                  html parser --- 簡單的 HTML 和 XHTML 剖析器.
                                                             (line    8)
* HTML <1>:                              urllib request Restrictions.
                                                             (line   29)
* html5 (於 html.entities 模組中):       html entities --- HTML 一般實體的定義.
                                                             (line   14)
* HTMLCalendar (calendar 中的類別):      calendar --- 日曆相關函式.
                                                             (line  139)
* HtmlDiff (difflib 中的類別):           difflib --- 計算差異的輔助工具.
                                                             (line   82)
* HTMLParser (html.parser 中的類別):     html parser --- 簡單的 HTML 和 XHTML 剖析器.
                                                             (line   14)
* htonl() (於 socket 模組中):            其他函式<2>.        (line  213)
* htons() (於 socket 模組中):            其他函式<2>.        (line  220)
* HTTP (於 email.policy 模組中):         email policy Policy Objects.
                                                             (line  525)
* http_error_301() (urllib.request.HTTPRedirectHandler 的方法): HTTPRedirectHandler 物件.
                                                             (line   35)
* http_error_302() (urllib.request.HTTPRedirectHandler 的方法): HTTPRedirectHandler 物件.
                                                             (line   41)
* http_error_303() (urllib.request.HTTPRedirectHandler 的方法): HTTPRedirectHandler 物件.
                                                             (line   46)
* http_error_307() (urllib.request.HTTPRedirectHandler 的方法): HTTPRedirectHandler 物件.
                                                             (line   51)
* http_error_308() (urllib.request.HTTPRedirectHandler 的方法): HTTPRedirectHandler 物件.
                                                             (line   57)
* http_error_401() (urllib.request.HTTPBasicAuthHandler 的方法): HTTPBasicAuthHandler 物件.
                                                             (line    6)
* http_error_401() (urllib.request.HTTPDigestAuthHandler 的方法): HTTPDigestAuthHandler 物件.
                                                             (line    6)
* http_error_407() (urllib.request.ProxyBasicAuthHandler 的方法): ProxyBasicAuthHandler 物件.
                                                             (line    6)
* http_error_407() (urllib.request.ProxyDigestAuthHandler 的方法): ProxyDigestAuthHandler 物件.
                                                             (line    6)
* http_error_auth_reqed() (urllib.request.AbstractBasicAuthHandler 的方法): AbstractBasicAuthHandler 物件.
                                                             (line    6)
* http_error_auth_reqed() (urllib.request.AbstractDigestAuthHandler 的方法): AbstractDigestAuthHandler 物件.
                                                             (line    6)
* http_error_default() (urllib.request.BaseHandler 的方法): BaseHandler 物件.
                                                             (line   66)
* http_open() (urllib.request.HTTPHandler 的方法): HTTPHandler 物件.
                                                             (line    6)
* HTTP_PORT (於 http.client 模組中):     http client --- HTTP 協定用戶端.
                                                             (line  200)
* http_response() (urllib.request.HTTPErrorProcessor 的方法): HTTPErrorProcessor 物件.
                                                             (line    6)
* http_version (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  254)
* HTTP;http.client（標準模組）:          http client --- HTTP 協定用戶端.
                                                             (line    8)
* HTTP;http（標準模組）:                 http --- HTTP 模組. (line    8)
* HTTP;protocol（協定）:                 urllib request Restrictions.
                                                             (line    6)
* HTTP;protocol（協定） <1>:             urllib request Restrictions.
                                                             (line   29)
* HTTP;protocol（協定） <2>:             http --- HTTP 模組. (line    8)
* HTTP;protocol（協定） <3>:             http client --- HTTP 協定用戶端.
                                                             (line    8)
* HTTP;protocol（協定） <4>:             http server — HTTP 伺服器.
                                                             (line    8)
* http.server;security（安全）:          安全性注意事項<3>.  (line    6)
* HTTPBasicAuthHandler (urllib.request 中的類別): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  324)
* HTTPConnection (http.client 中的類別): http client --- HTTP 協定用戶端.
                                                             (line   31)
* HTTPCookieProcessor (urllib.request 中的類別): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  256)
* httpd:                                 http server — HTTP 伺服器.
                                                             (line    8)
* HTTPDefaultErrorHandler (urllib.request 中的類別): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  247)
* HTTPDigestAuthHandler (urllib.request 中的類別): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  348)
* HTTPError:                             urllib error --- urllib request 引發的例外類別.
                                                             (line   28)
* HTTPErrorProcessor (urllib.request 中的類別): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  408)
* HTTPException:                         http client --- HTTP 協定用戶端.
                                                             (line  131)
* HTTPHandler (logging.handlers 中的類別): HTTPHandler.      (line   10)
* HTTPHandler (urllib.request 中的類別): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  372)
* HTTPMessage (http.client 中的類別):    HTTPMessage 物件.   (line    6)
* HTTPMethod (http 中的類別):            HTTP 狀態分類.      (line   38)
* httponly (http.cookies.Morsel 的屬性): Morsel 物件.        (line   13)
* HTTPPasswordMgr (urllib.request 中的類別): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  282)
* HTTPPasswordMgrWithDefaultRealm (urllib.request 中的類別): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  286)
* HTTPPasswordMgrWithPriorAuth (urllib.request 中的類別): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  292)
* HTTPRedirectHandler (urllib.request 中的類別): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  252)
* HTTPResponse (http.client 中的類別):   http client --- HTTP 協定用戶端.
                                                             (line   99)
* https_open() (urllib.request.HTTPSHandler 的方法): HTTPSHandler 物件.
                                                             (line    6)
* HTTPS_PORT (於 http.client 模組中):    http client --- HTTP 協定用戶端.
                                                             (line  204)
* https_response() (urllib.request.HTTPErrorProcessor 的方法): HTTPErrorProcessor 物件.
                                                             (line   18)
* HTTPSConnection (http.client 中的類別): http client --- HTTP 協定用戶端.
                                                             (line   62)
* HTTPServer (http.server 中的類別):     http server — HTTP 伺服器.
                                                             (line   30)
* HTTPSHandler (urllib.request 中的類別): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  376)
* HTTPStatus (http 中的類別):            http --- HTTP 模組. (line   27)
* HV_GUID_BROADCAST (於 socket 模組中):  常數<7>.            (line  341)
* HV_GUID_CHILDREN (於 socket 模組中):   常數<7>.            (line  341)
* HV_GUID_LOOPBACK (於 socket 模組中):   常數<7>.            (line  341)
* HV_GUID_PARENT (於 socket 模組中):     常數<7>.            (line  341)
* HV_GUID_WILDCARD (於 socket 模組中):   常數<7>.            (line  341)
* HV_GUID_ZERO (於 socket 模組中):       常數<7>.            (line  341)
* HV_PROTOCOL_RAW (於 socket 模組中):    常數<7>.            (line  341)
* HVSOCKET_ADDRESS_FLAG_PASSTHRU (於 socket 模組中): 常數<7>.
                                                             (line  341)
* HVSOCKET_CONNECT_TIMEOUT (於 socket 模組中): 常數<7>.      (line  341)
* HVSOCKET_CONNECT_TIMEOUT_MAX (於 socket 模組中): 常數<7>.  (line  341)
* HVSOCKET_CONNECTED_SUSPEND (於 socket 模組中): 常數<7>.    (line  341)
* hypot() (於 math 模組中):              Trigonometric functions.
                                                             (line   47)
* I (於 re 模組中):                      旗標.               (line   38)
* I/O control（I/O 控制）;buffering（緩衝）: 內建函式.       (line 1294)
* I/O control（I/O 控制）;buffering（緩衝） <1>: Socket 物件.
                                                             (line  212)
* iadd() (於 operator 模組中):           原地 in-place 運算子.
                                                             (line   33)
* iand() (於 operator 模組中):           原地 in-place 運算子.
                                                             (line   38)
* iconcat() (於 operator 模組中):        原地 in-place 運算子.
                                                             (line   43)
* id (ssl.SSLSession 的屬性):            SSL session.        (line   12)
* id() (unittest.TestCase 的方法):       Test cases.         (line  743)
* idcok() (curses.window 的方法):        Window Objects.     (line  288)
* ident (select.kevent 的屬性):          Kevent Objects.     (line    8)
* ident (threading.Thread 的屬性):       Thread Objects.     (line  167)
* identchars (cmd.Cmd 的屬性):           Cmd 物件.           (line  135)
* identifier:                            Identifiers Names.  (line    6)
* identifier（識別器）:                  Identifiers and keywords.
                                                             (line    6)
* identify_column() (tkinter.ttk.Treeview 的方法): ttk Treeview.
                                                             (line  143)
* identify_element() (tkinter.ttk.Treeview 的方法): ttk Treeview.
                                                             (line  172)
* identify_region() (tkinter.ttk.Treeview 的方法): ttk Treeview.
                                                             (line  150)
* identify_row() (tkinter.ttk.Treeview 的方法): ttk Treeview.
                                                             (line  139)
* identify() (tkinter.ttk.Notebook 的方法): ttk Notebook.    (line   31)
* identify() (tkinter.ttk.Treeview 的方法): ttk Treeview.    (line  133)
* identify() (tkinter.ttk.Widget 的方法): ttk Widget.        (line   11)
* identity of an object（物件的識別）:   Objects values and types.
                                                             (line   11)
* identity;test（測試）:                 Membership test operations.
                                                             (line   39)
* IDLE:                                  IDLE<62>.           (line    8)
* IDLE <1>:                              術語表.             (line  581)
* IDLE_PRIORITY_CLASS (於 subprocess 模組中): Windows Constants.
                                                             (line   89)
* IDLESTARTUP:                           IDLE<35>.           (line  176)
* IDLESTARTUP <1>:                       IDLE<39>.           (line    9)
* IDLESTARTUP <2>:                       IDLE<45>.           (line    9)
* IDLESTARTUP <3>:                       Startup and Code Execution.
                                                             (line    7)
* idlok() (curses.window 的方法):        Window Objects.     (line  296)
* If (ast 中的類別):                     流程控制.           (line    8)
* if_indextoname() (於 socket 模組中):   其他函式<2>.        (line  415)
* if_nameindex() (於 socket 模組中):     其他函式<2>.        (line  372)
* if_nametoindex() (於 socket 模組中):   其他函式<2>.        (line  397)
* if;conditional expression（條件運算式）: Conditional expressions.
                                                             (line    6)
* if;於 comprehensions（綜合運算）:      Displays for lists sets and dictionaries.
                                                             (line   14)
* IfExp (ast 中的類別):                  運算式<2>.          (line  152)
* ifloordiv() (於 operator 模組中):      原地 in-place 運算子.
                                                             (line   48)
* iglob() (於 glob 模組中):              glob --- Unix 風格的路徑名稱模式擴展.
                                                             (line   69)
* ignorableWhitespace() (xml.sax.handler.ContentHandler 的方法): ContentHandler 物件.
                                                             (line  150)
* ignore (bdb.Breakpoint 的屬性):        bdb --- 偵錯器框架. (line  119)
* ignore (pdb command):                  Debugger Commands.  (line  144)
* IGNORE (於 tkinter.messagebox 模組中): tkinter messagebox --- Tkinter 訊息提示.
                                                             (line  131)
* ignore_environment (sys.flags 的屬性): sys --- 系統特定的參數與函式.
                                                             (line  546)
* ignore_errors() (於 codecs 模組中):    Error Handlers.     (line  147)
* IGNORE_EXCEPTION_DETAIL (於 doctest 模組中): 可選旗標.     (line   58)
* ignore_patterns() (於 shutil 模組中):  Directory and files operations.
                                                             (line  185)
* ignore_warnings() (於 test.support.warnings_helper 模組中): test support warnings_helper --- 用於 warnings 測試的工具.
                                                             (line   10)
* ignore;error handler's name（錯誤處理器名稱）: Error Handlers.
                                                             (line   15)
* IGNORECASE (於 re 模組中):             旗標.               (line   38)
* IISCGIHandler (wsgiref.handlers 中的類別): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line   22)
* IllegalMonthError:                     calendar --- 日曆相關函式.
                                                             (line  391)
* IllegalWeekdayError:                   calendar --- 日曆相關函式.
                                                             (line  400)
* ilshift() (於 operator 模組中):        原地 in-place 運算子.
                                                             (line   53)
* imag (numbers.Complex 的屬性):         數值的階層.         (line   18)
* imag (sys.hash_info 的屬性):           sys --- 系統特定的參數與函式.
                                                             (line 1013)
* imaginary literal（虛數常數）:         Numeric literals.   (line    6)
* imap_unordered() (multiprocessing.pool.Pool 的方法): Process Pools.
                                                             (line  144)
* imap() (multiprocessing.pool.Pool 的方法): Process Pools.  (line  129)
* IMAP4 (imaplib 中的類別):              imaplib --- IMAP4 協定客戶端.
                                                             (line   25)
* IMAP4_SSL (imaplib 中的類別):          imaplib --- IMAP4 協定客戶端.
                                                             (line   74)
* IMAP4_SSL;protocol（協定）:            imaplib --- IMAP4 協定客戶端.
                                                             (line    8)
* IMAP4_stream (imaplib 中的類別):       imaplib --- IMAP4 協定客戶端.
                                                             (line  104)
* IMAP4_stream;protocol（協定）:         imaplib --- IMAP4 協定客戶端.
                                                             (line    8)
* IMAP4;protocol（協定）:                imaplib --- IMAP4 協定客戶端.
                                                             (line    8)
* IMAP4.abort:                           imaplib --- IMAP4 協定客戶端.
                                                             (line   58)
* IMAP4.error:                           imaplib --- IMAP4 協定客戶端.
                                                             (line   53)
* IMAP4.readonly:                        imaplib --- IMAP4 協定客戶端.
                                                             (line   65)
* imatmul() (於 operator 模組中):        原地 in-place 運算子.
                                                             (line   68)
* immedok() (curses.window 的方法):      Window Objects.     (line  302)
* immortal:                              術語表.             (line  587)
* immutable object（不可變物件）:        Objects values and types.
                                                             (line   11)
* immutable;data（資料）;type（型別）:   Literals<2>.        (line   17)
* immutable;object（物件）:              Literals<2>.        (line   17)
* immutable;object（物件） <1>:          Dictionary displays.
                                                             (line   37)
* immutable（不可變）;sequence（序列）;type（型別）: Immutable Sequence Types.
                                                             (line    6)
* immutable（不可變物件）:               術語表.             (line  597)
* imod() (於 operator 模組中):           原地 in-place 運算子.
                                                             (line   58)
* impl_detail() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  529)
* implementation (於 sys 模組中):        sys --- 系統特定的參數與函式.
                                                             (line 1057)
* Import (ast 中的類別):                 引入 imports.       (line    6)
* import hooks:                          Import hooks.       (line    6)
* import machinery（引入機制）:          模組引入系統.       (line    6)
* import path（引入路徑）:               術語表.             (line  604)
* import_fresh_module() (於 test.support.import_helper 模組中): test support import_helper --- 用於 import 測試的工具.
                                                             (line   15)
* IMPORT_FROM (opcode):                  Python Bytecode Instructions.
                                                             (line  817)
* import_module() (於 importlib 模組中): 函式<11>.           (line   15)
* import_module() (於 test.support.import_helper 模組中): test support import_helper --- 用於 import 測試的工具.
                                                             (line   50)
* IMPORT_NAME (opcode):                  Python Bytecode Instructions.
                                                             (line  808)
* importer（引入器）:                    術語表.             (line  617)
* ImportError:                           實體例外.           (line   41)
* ImportFrom (ast 中的類別):             引入 imports.       (line   19)
* importing（引入）:                     術語表.             (line  612)
* ImportWarning:                         警告.               (line   53)
* ImproperConnectionState:               http client --- HTTP 協定用戶端.
                                                             (line  161)
* imul() (於 operator 模組中):           原地 in-place 運算子.
                                                             (line   63)
* In (ast 中的類別):                     運算式<2>.          (line  105)
* in_dll() (ctypes._CData 的方法):       Data types.         (line   63)
* in_table_a1() (於 stringprep 模組中):  stringprep --- 網際網路字串準備.
                                                             (line   40)
* in_table_b1() (於 stringprep 模組中):  stringprep --- 網際網路字串準備.
                                                             (line   45)
* in_table_c11_c12() (於 stringprep 模組中): stringprep --- 網際網路字串準備.
                                                             (line   69)
* in_table_c11() (於 stringprep 模組中): stringprep --- 網際網路字串準備.
                                                             (line   60)
* in_table_c12() (於 stringprep 模組中): stringprep --- 網際網路字串準備.
                                                             (line   64)
* in_table_c21_c22() (於 stringprep 模組中): stringprep --- 網際網路字串準備.
                                                             (line   84)
* in_table_c21() (於 stringprep 模組中): stringprep --- 網際網路字串準備.
                                                             (line   74)
* in_table_c22() (於 stringprep 模組中): stringprep --- 網際網路字串準備.
                                                             (line   79)
* in_table_c3() (於 stringprep 模組中):  stringprep --- 網際網路字串準備.
                                                             (line   89)
* in_table_c4() (於 stringprep 模組中):  stringprep --- 網際網路字串準備.
                                                             (line   93)
* in_table_c5() (於 stringprep 模組中):  stringprep --- 網際網路字串準備.
                                                             (line   98)
* in_table_c6() (於 stringprep 模組中):  stringprep --- 網際網路字串準備.
                                                             (line  102)
* in_table_c7() (於 stringprep 模組中):  stringprep --- 網際網路字串準備.
                                                             (line  107)
* in_table_c8() (於 stringprep 模組中):  stringprep --- 網際網路字串準備.
                                                             (line  112)
* in_table_c9() (於 stringprep 模組中):  stringprep --- 網際網路字串準備.
                                                             (line  117)
* in_table_d1() (於 stringprep 模組中):  stringprep --- 網際網路字串準備.
                                                             (line  121)
* in_table_d2() (於 stringprep 模組中):  stringprep --- 網際網路字串準備.
                                                             (line  126)
* in_transaction (sqlite3.Connection 的屬性): Connection 物件.
                                                             (line  762)
* inch() (curses.window 的方法):         Window Objects.     (line  310)
* include() (於 xml.etree.ElementInclude 模組中): 函式<9>.   (line   17)
* inclusive (tracemalloc.DomainFilter 的屬性): DomainFilter. (line   12)
* inclusive (tracemalloc.Filter 的屬性): Filter.             (line   39)
* inclusive（包含）;or:                  Binary bitwise operations.
                                                             (line   20)
* Incomplete:                            binascii --- 在二進位制和 ASCII 之間轉換.
                                                             (line  160)
* IncompleteRead:                        http client --- HTTP 協定用戶端.
                                                             (line  157)
* IncompleteReadError:                   例外<8>.            (line   39)
* incr_item():                           例外<17>.           (line   58)
* incr_item() <1>:                       例外<17>.           (line  103)
* increment_lineno() (於 ast 模組中):    ast 輔助程式.       (line  134)
* IncrementalDecoder (codecs 中的類別):  IncrementalDecoder 物件.
                                                             (line   11)
* incrementaldecoder (codecs.CodecInfo 的屬性): codecs --- 編解碼器註冊表和基底類別.
                                                             (line   78)
* IncrementalEncoder (codecs 中的類別):  IncrementalEncoder 物件.
                                                             (line   11)
* incrementalencoder (codecs.CodecInfo 的屬性): codecs --- 編解碼器註冊表和基底類別.
                                                             (line   78)
* IncrementalNewlineDecoder (io 中的類別): 文字 I/O<2>.      (line  285)
* IncrementalParser (xml.sax.xmlreader 中的類別): xml sax xmlreader --- XML 剖析器的介面.
                                                             (line   20)
* indent (doctest.Example 的屬性):       Example 物件.       (line   47)
* indent (reprlib.Repr 的屬性):          Repr 物件.          (line   54)
* INDENT (於 token 模組中):              token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   50)
* INDENT token（縮排標誌）:              Indentation.        (line   33)
* indent() (於 textwrap 模組中):         textwrap --- 文字包裝與填充.
                                                             (line  102)
* indent() (於 xml.etree.ElementTree 模組中): 函式<8>.       (line  117)
* indentation（縮排）:                   Indentation.        (line    6)
* IndentationError:                      實體例外.           (line  299)
* index (inspect.FrameInfo 的屬性):      直譯器堆疊.         (line   37)
* index (inspect.Traceback 的屬性):      直譯器堆疊.         (line   77)
* index operation（索引操作）:           Sequences.          (line    6)
* index() (array.array 的方法):          array --- 高效率的數值型陣列.
                                                             (line  176)
* index() (bytearray 的方法):            Bytes and Bytearray Operations.
                                                             (line  152)
* index() (bytes 的方法):                Bytes and Bytearray Operations.
                                                             (line  152)
* index() (collections.deque 的方法):    deque 物件.         (line   62)
* index() (multiprocessing.shared_memory.ShareableList 的方法): multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取.
                                                             (line  304)
* index() (str 的方法):                  String Methods<2>.  (line  174)
* index() (tkinter.ttk.Notebook 的方法): ttk Notebook.       (line   36)
* index() (tkinter.ttk.Treeview 的方法): ttk Treeview.       (line  178)
* index() (於 operator 模組中):          operator --- 標準運算子替代函式.
                                                             (line   85)
* index()（序列方法）:                   Common Sequence Operations.
                                                             (line   21)
* IndexError:                            實體例外.           (line   66)
* indexOf() (於 operator 模組中):        operator --- 標準運算子替代函式.
                                                             (line  188)
* IndexSizeErr:                          例外<15>.           (line   34)
* indices() (slice 的方法):              Slice objects.      (line   16)
* INDIRECT (inspect.BufferFlags 的屬性): Buffer flags.       (line   31)
* inet_aton() (於 socket 模組中):        其他函式<2>.        (line  230)
* inet_ntoa() (於 socket 模組中):        其他函式<2>.        (line  250)
* inet_ntop() (於 socket 模組中):        其他函式<2>.        (line  285)
* inet_pton() (於 socket 模組中):        其他函式<2>.        (line  267)
* Inexact (decimal 中的類別):            Signals.            (line   42)
* inf (sys.hash_info 的屬性):            sys --- 系統特定的參數與函式.
                                                             (line 1005)
* inf (於 cmath 模組中):                 常數<3>.            (line   20)
* inf (於 math 模組中):                  常數<2>.            (line   26)
* infile (shlex.shlex 的屬性):           shlex 物件.         (line  139)
* Infinity（無窮）:                      內建函式.           (line  646)
* infj (於 cmath 模組中):                常數<3>.            (line   26)
* INFO (於 logging 模組中):              Logging Levels.     (line   29)
* INFO (於 tkinter.messagebox 模組中):   tkinter messagebox --- Tkinter 訊息提示.
                                                             (line  172)
* info() (dis.Bytecode 的方法):          Bytecode analysis.  (line   63)
* info() (gettext.NullTranslations 的方法): The NullTranslations class.
                                                             (line   63)
* info() (http.client.HTTPResponse 的方法): HTTPResponse 物件.
                                                             (line   83)
* info() (logging.Logger 的方法):        Logger 物件.        (line  285)
* info() (urllib.response.addinfourl 的方法): urllib response --- Response classes used by urllib.
                                                             (line   34)
* info() (於 logging 模組中):            Module-Level Functions.
                                                             (line   64)
* infolist() (zipfile.ZipFile 的方法):   ZipFile 物件.       (line  117)
* inheritance（繼承）:                   類別定義.           (line    6)
* ini file（ini 檔案）:                  configparser --- 設定檔剖析器.
                                                             (line    8)
* init_color() (於 curses 模組中):       函式<5>.            (line  220)
* init_pair() (於 curses 模組中):        函式<5>.            (line  232)
* init() (於 mimetypes 模組中):          mimetypes --- 將檔案名稱對映到 MIME 類型.
                                                             (line   91)
* inited (於 mimetypes 模組中):          mimetypes --- 將檔案名稱對映到 MIME 類型.
                                                             (line  130)
* initgroups() (於 os 模組中):           行程參數.           (line  342)
* initial_indent (textwrap.TextWrapper 的屬性): textwrap --- 文字包裝與填充.
                                                             (line  210)
* initproc (C type):                     Slot Type typedefs. (line   35)
* initscr() (於 curses 模組中):          函式<5>.            (line  245)
* inode() (os.DirEntry 的方法):          Files and Directories.
                                                             (line  951)
* input_charset (email.charset.Charset 的屬性): email charset：表示字元集合.
                                                             (line   51)
* input_codec (email.charset.Charset 的屬性): email charset：表示字元集合.
                                                             (line   80)
* input() (於 fileinput 模組中):         fileinput --- 逐列疊代多個輸入串流.
                                                             (line   56)
* input（輸入）:                         運算式輸入.         (line    6)
* InputSource (xml.sax.xmlreader 中的類別): xml sax xmlreader --- XML 剖析器的介面.
                                                             (line   51)
* InputStream (wsgiref.types 中的類別):  wsgiref types -- 用於靜態型別檢查的 WSGI 型別.
                                                             (line   23)
* inquiry (C type):                      循環垃圾回收的支援. (line  196)
* insch() (curses.window 的方法):        Window Objects.     (line  316)
* insdelln() (curses.window 的方法):     Window Objects.     (line  323)
* insert_text() (於 readline 模組中):    Line buffer.        (line   13)
* insert() (array.array 的方法):         array --- 高效率的數值型陣列.
                                                             (line  184)
* insert() (collections.deque 的方法):   deque 物件.         (line   70)
* insert() (tkinter.ttk.Notebook 的方法): ttk Notebook.      (line   41)
* insert() (tkinter.ttk.Treeview 的方法): ttk Treeview.      (line  183)
* insert() (xml.etree.ElementTree.Element 的方法): Element 物件.
                                                             (line  130)
* insert()（序列方法）:                  Mutable Sequence Types.
                                                             (line   16)
* insertBefore() (xml.dom.Node 的方法):  Node Objects.       (line  121)
* insertln() (curses.window 的方法):     Window Objects.     (line  331)
* insnstr() (curses.window 的方法):      Window Objects.     (line  336)
* insort_left() (於 bisect 模組中):      bisect --- 陣列二分演算法 Array bisection algorithm.
                                                             (line   52)
* insort_right() (於 bisect 模組中):     bisect --- 陣列二分演算法 Array bisection algorithm.
                                                             (line   66)
* insort() (於 bisect 模組中):           bisect --- 陣列二分演算法 Array bisection algorithm.
                                                             (line   66)
* inspect (sys.flags 的屬性):            sys --- 系統特定的參數與函式.
                                                             (line  525)
* inspect 命令列選項; -details:          命令列介面<6>.      (line   13)
* InspectLoader (importlib.abc 中的類別): importlib abc -- Abstract base classes related to import.
                                                             (line  229)
* insstr() (curses.window 的方法):       Window Objects.     (line  347)
* install_opener() (於 urllib.request 模組中): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  106)
* install_scripts() (venv.EnvBuilder 的方法): API<2>.        (line  191)
* install() (gettext.NullTranslations 的方法): The NullTranslations class.
                                                             (line   72)
* install() (於 gettext 模組中):         Class-based API.    (line   69)
* installHandler() (於 unittest 模組中): Signal Handling.    (line   29)
* instance（實例）;call（呼叫）:         Calls.              (line  155)
* instate() (tkinter.ttk.Widget 的方法): ttk Widget.         (line   18)
* instr() (curses.window 的方法):        Window Objects.     (line  357)
* instream (shlex.shlex 的屬性):         shlex 物件.         (line  145)
* Instruction (dis 中的類別):            Python Bytecode Instructions.
                                                             (line   10)
* INSTRUCTION (monitoring event):        事件.               (line   30)
* Instruction.arg (於 dis 模組中):       Python Bytecode Instructions.
                                                             (line   34)
* Instruction.argrepr (於 dis 模組中):   Python Bytecode Instructions.
                                                             (line   46)
* Instruction.argval (於 dis 模組中):    Python Bytecode Instructions.
                                                             (line   42)
* Instruction.baseopcode (於 dis 模組中): Python Bytecode Instructions.
                                                             (line   24)
* Instruction.baseopname (於 dis 模組中): Python Bytecode Instructions.
                                                             (line   29)
* Instruction.cache_offset (於 dis 模組中): Python Bytecode Instructions.
                                                             (line   61)
* Instruction.end_offset (於 dis 模組中): Python Bytecode Instructions.
                                                             (line   65)
* Instruction.is_jump_target (於 dis 模組中): Python Bytecode Instructions.
                                                             (line   78)
* Instruction.jump_target (於 dis 模組中): Python Bytecode Instructions.
                                                             (line   82)
* Instruction.line_number (於 dis 模組中): Python Bytecode Instructions.
                                                             (line   73)
* Instruction.offset (於 dis 模組中):    Python Bytecode Instructions.
                                                             (line   51)
* Instruction.oparg (於 dis 模組中):     Python Bytecode Instructions.
                                                             (line   38)
* Instruction.opcode (於 dis 模組中):    Python Bytecode Instructions.
                                                             (line   14)
* Instruction.opname (於 dis 模組中):    Python Bytecode Instructions.
                                                             (line   20)
* Instruction.positions (於 dis 模組中): Python Bytecode Instructions.
                                                             (line   87)
* Instruction.start_offset (於 dis 模組中): Python Bytecode Instructions.
                                                             (line   55)
* Instruction.starts_line (於 dis 模組中): Python Bytecode Instructions.
                                                             (line   69)
* int (uuid.UUID 的屬性):                uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  125)
* int (內建類別):                        內建函式.           (line  842)
* int_info (於 sys 模組中):              sys --- 系統特定的參數與函式.
                                                             (line 1100)
* int_max_str_digits (sys.flags 的屬性): sys --- 系統特定的參數與函式.
                                                             (line  570)
* Int2AP() (於 imaplib 模組中):          imaplib --- IMAP4 協定客戶端.
                                                             (line  118)
* integer literal（整數常數）:           Numeric literals.   (line    6)
* integer（整數）:                       Immutable sequences.
                                                             (line   15)
* integer（整數）;literals（字面值）:    數值型別 --- int、float、complex.
                                                             (line   15)
* integer（整數）;representation（表示）: numbers Integral.  (line    9)
* Integral (numbers 中的類別):           數值的階層.         (line   54)
* Integrated Development Environment（整合開發環境）: IDLE<62>.
                                                             (line    8)
* IntegrityError:                        例外<4>.            (line   65)
* IntEnum (enum 中的類別):               資料型別<2>.        (line  334)
* interact (pdb command):                Debugger Commands.  (line  352)
* interact() (code.InteractiveConsole 的方法): Interactive Console Objects.
                                                             (line   10)
* interact() (於 code 模組中):           code --- 直譯器基底類別.
                                                             (line   37)
* Interactive (ast 中的類別):            根節點.             (line   35)
* interactive (sys.flags 的屬性):        sys --- 系統特定的參數與函式.
                                                             (line  528)
* interactive mode（互動模式）:          完整的 Python 程式. (line   15)
* interactive（互動的）:                 術語表.             (line  622)
* InteractiveConsole (code 中的類別):    code --- 直譯器基底類別.
                                                             (line   25)
* InteractiveInterpreter (code 中的類別): code --- 直譯器基底類別.
                                                             (line   15)
* InterfaceError:                        例外<4>.            (line   37)
* intern() (於 sys 模組中):              sys --- 系統特定的參數與函式.
                                                             (line 1145)
* internal type（內部型別）:             Internal types.     (line    6)
* internal_attr (zipfile.ZipInfo 的屬性): ZipInfo 物件.      (line  123)
* Internaldate2tuple() (於 imaplib 模組中): imaplib --- IMAP4 協定客戶端.
                                                             (line  112)
* InternalError:                         例外<4>.            (line   71)
* internalSubset (xml.dom.DocumentType 的屬性): DocumentType 物件.
                                                             (line   27)
* INTERNET_TIMEOUT (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line   64)
* Internet（網際網路）:                  網路協定 Internet protocols 及支援.
                                                             (line    6)
* interpolated string literal（插值字串常數）: String literal concatenation.
                                                             (line   24)
* interpolation（插值）、字串 (%):       printf-style String Formatting.
                                                             (line    6)
* interpolation（插值）;bytearray (%):   printf-style Bytes Formatting.
                                                             (line    6)
* interpolation（插值）;bytes (%):       printf-style Bytes Formatting.
                                                             (line    6)
* InterpolationDepthError:               例外<5>.            (line   42)
* InterpolationError:                    例外<5>.            (line   37)
* InterpolationMissingOptionError:       例外<5>.            (line   49)
* InterpolationSyntaxError:              例外<5>.            (line   54)
* interpreted（直譯的）:                 術語表.             (line  632)
* interpreter lock（直譯器鎖）:          Thread State and the Global Interpreter Lock.
                                                             (line    6)
* interpreter prompts（直譯器提示）:     sys --- 系統特定的參數與函式.
                                                             (line 1440)
* interpreter shutdown（直譯器關閉）:    術語表.             (line  640)
* interpreter_requires_environment() (於 test.support.script_helper 模組中): test support script_helper --- 用於 Python 執行測試的工具.
                                                             (line    9)
* interpreter（直譯器）:                 最高層級元件.       (line    6)
* interrupt_main() (於 _thread 模組中):  _thread --- 低階執行緒 API.
                                                             (line   48)
* interrupt() (sqlite3.Connection 的方法): Connection 物件.  (line  338)
* InterruptedError:                      作業系統例外.       (line   68)
* intersection_update() (frozenset 的方法): Set Types --- set frozenset.
                                                             (line  175)
* intersection() (frozenset 的方法):     Set Types --- set frozenset.
                                                             (line  102)
* IntFlag (enum 中的類別):               資料型別<2>.        (line  496)
* intro (cmd.Cmd 的屬性):                Cmd 物件.           (line  150)
* InuseAttributeErr:                     例外<15>.           (line   39)
* inv_cdf() (statistics.NormalDist 的方法): NormalDist 物件. (line   79)
* inv() (於 operator 模組中):            operator --- 標準運算子替代函式.
                                                             (line   93)
* InvalidAccessErr:                      例外<15>.           (line   44)
* invalidate_caches() (importlib.abc.MetaPathFinder 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line   49)
* invalidate_caches() (importlib.abc.PathEntryFinder 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line   84)
* invalidate_caches() (importlib.machinery.FileFinder 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  184)
* invalidate_caches() (importlib.machinery.PathFinder 的類別方法): importlib machinery -- Importers and path hooks.
                                                             (line  134)
* invalidate_caches() (zipimport.zipimporter 的方法): zipimporter 物件.
                                                             (line   88)
* invalidate_caches() (於 importlib 模組中): 函式<11>.       (line   40)
* InvalidCharacterErr:                   例外<15>.           (line   49)
* InvalidModificationErr:                例外<15>.           (line   57)
* InvalidOperation (decimal 中的類別):   Signals.            (line   50)
* InvalidStateErr:                       例外<15>.           (line   61)
* InvalidStateError:                     例外類別.           (line   24)
* InvalidStateError <1>:                 例外<8>.            (line   27)
* InvalidTZPathWarning:                  Exceptions and warnings.
                                                             (line   12)
* InvalidURL:                            http client --- HTTP 協定用戶端.
                                                             (line  140)
* inversion（反轉）:                     Unary arithmetic and bitwise operations.
                                                             (line   18)
* Invert (ast 中的類別):                 運算式<2>.          (line   26)
* invert() (於 operator 模組中):         operator --- 標準運算子替代函式.
                                                             (line   93)
* invocation（調用）:                    Callable types.     (line    6)
* IO (typing 中的類別):                  ABCs for working with IO.
                                                             (line    6)
* IO_REPARSE_TAG_APPEXECLINK (於 stat 模組中): stat --- 直譯 stat 的結果.
                                                             (line  476)
* IO_REPARSE_TAG_MOUNT_POINT (於 stat 模組中): stat --- 直譯 stat 的結果.
                                                             (line  476)
* IO_REPARSE_TAG_SYMLINK (於 stat 模組中): stat --- 直譯 stat 的結果.
                                                             (line  476)
* IOBase (io 中的類別):                  I/O 基礎類別.       (line    6)
* IOCTL_VM_SOCKETS_GET_LOCAL_CID (於 socket 模組中): 常數<7>.
                                                             (line  270)
* ioctl() (socket.socket 的方法):        Socket 物件.        (line  179)
* ioctl() (於 fcntl 模組中):             fcntl --- fcntl 和 ioctl 系統呼叫.
                                                             (line   93)
* IOError:                               實體例外.           (line  418)
* ior() (於 operator 模組中):            原地 in-place 運算子.
                                                             (line   75)
* ios_ver() (於 platform 模組中):        iOS Platform.       (line    6)
* ip (ipaddress.IPv4Interface 的屬性):   Interface objects.  (line   19)
* ip (ipaddress.IPv6Interface 的屬性):   Interface objects.  (line   74)
* ip_address() (於 ipaddress 模組中):    Convenience factory functions.
                                                             (line    9)
* ip_interface() (於 ipaddress 模組中):  Convenience factory functions.
                                                             (line   37)
* ip_network() (於 ipaddress 模組中):    Convenience factory functions.
                                                             (line   23)
* ipow() (於 operator 模組中):           原地 in-place 運算子.
                                                             (line   80)
* ipv4_mapped (ipaddress.IPv6Address 的屬性): Address objects.
                                                             (line  288)
* IPv4Address (ipaddress 中的類別):      Address objects.    (line   13)
* IPv4Interface (ipaddress 中的類別):    Interface objects.  (line    9)
* IPv4Network (ipaddress 中的類別):      Network objects.    (line   13)
* IPV6_ENABLED (於 test.support.socket_helper 模組中): test support socket_helper --- 用於 socket 測試的工具.
                                                             (line   11)
* ipv6_mapped (ipaddress.IPv4Address 的屬性): Address objects.
                                                             (line  177)
* IPv6Address (ipaddress 中的類別):      Address objects.    (line  209)
* IPv6Interface (ipaddress 中的類別):    Interface objects.  (line   64)
* IPv6Network (ipaddress 中的類別):      Network objects.    (line  253)
* irrefutable case block:                Irrefutable Case Blocks.
                                                             (line    6)
* irshift() (於 operator 模組中):        原地 in-place 運算子.
                                                             (line   85)
* Is (ast 中的類別):                     運算式<2>.          (line  105)
* is_() (於 operator 模組中):            operator --- 標準運算子替代函式.
                                                             (line   55)
* is_absolute() (pathlib.PurePath 的方法): 方法與屬性.       (line  178)
* is_active() (asyncio.AbstractChildWatcher 的方法): Process Watchers.
                                                             (line   72)
* is_active() (graphlib.TopologicalSorter 的方法): graphlib —-- 使用類圖 graph-like 結構進行操作的功能.
                                                             (line   94)
* is_alive() (multiprocessing.Process 的方法): Process 與例外.
                                                             (line   93)
* is_alive() (threading.Thread 的方法):  Thread Objects.     (line  193)
* is_android (於 test.support 模組中):   test support --- Python 測試套件的工具.
                                                             (line   39)
* is_annotated() (symtable.Symbol 的方法): 檢查符號表.       (line  216)
* is_assigned() (symtable.Symbol 的方法): 檢查符號表.        (line  227)
* is_async (pyclbr.Function 的屬性):     函式物件.           (line   41)
* is_attachment() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  443)
* is_authenticated() (urllib.request.HTTPPasswordMgrWithPriorAuth 的方法): HTTPPasswordMgrWithPriorAuth 物件.
                                                             (line   30)
* is_block_device() (pathlib.Path 的方法): Querying file type and status.
                                                             (line  121)
* is_blocked() (http.cookiejar.DefaultCookiePolicy 的方法): DefaultCookiePolicy 物件.
                                                             (line   60)
* is_canonical() (decimal.Context 的方法): Context objects.  (line  311)
* is_canonical() (decimal.Decimal 的方法): Decimal objects.  (line  277)
* is_char_device() (pathlib.Path 的方法): Querying file type and status.
                                                             (line  129)
* IS_CHARACTER_JUNK() (於 difflib 模組中): difflib --- 計算差異的輔助工具.
                                                             (line  362)
* is_check_supported() (於 lzma 模組中): Miscellaneous.      (line    6)
* is_closed() (asyncio.loop 的方法):     啟動和停止迴圈.     (line   36)
* is_closing() (asyncio.BaseTransport 的方法): Base Transport.
                                                             (line   17)
* is_closing() (asyncio.StreamWriter 的方法): StreamWriter.  (line   98)
* is_dataclass() (於 dataclasses 模組中): 模組內容<8>.       (line  454)
* is_declared_global() (symtable.Symbol 的方法): 檢查符號表. (line  208)
* is_dir() (importlib.abc.Traversable 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  554)
* is_dir() (importlib.resources.abc.Traversable 的方法): importlib resources abc -- 資源的抽象基底類別.
                                                             (line  103)
* is_dir() (os.DirEntry 的方法):         Files and Directories.
                                                             (line  962)
* is_dir() (pathlib.Path 的方法):        Querying file type and status.
                                                             (line   64)
* is_dir() (zipfile.Path 的方法):        Path Objects.       (line   47)
* is_dir() (zipfile.ZipInfo 的方法):     ZipInfo 物件.       (line   42)
* is_enabled() (於 faulthandler 模組中): Fault handler state.
                                                             (line   31)
* is_expired() (http.cookiejar.Cookie 的方法): Cookie 物件<2>.
                                                             (line  113)
* is_fifo() (pathlib.Path 的方法):       Querying file type and status.
                                                             (line  113)
* is_file() (importlib.abc.Traversable 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  558)
* is_file() (importlib.resources.abc.Traversable 的方法): importlib resources abc -- 資源的抽象基底類別.
                                                             (line  107)
* is_file() (os.DirEntry 的方法):        Files and Directories.
                                                             (line  991)
* is_file() (pathlib.Path 的方法):       Querying file type and status.
                                                             (line   51)
* is_file() (zipfile.Path 的方法):       Path Objects.       (line   51)
* is_finalized() (於 gc 模組中):         gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line  189)
* is_finalizing() (於 sys 模組中):       sys --- 系統特定的參數與函式.
                                                             (line 1168)
* is_finite() (decimal.Context 的方法):  Context objects.    (line  315)
* is_finite() (decimal.Decimal 的方法):  Decimal objects.    (line  284)
* is_free() (symtable.Symbol 的方法):    檢查符號表.         (line  222)
* is_global (ipaddress.IPv4Address 的屬性): Address objects. (line  135)
* is_global (ipaddress.IPv6Address 的屬性): Address objects. (line  268)
* is_global() (symtable.Symbol 的方法):  檢查符號表.         (line  200)
* is_hop_by_hop() (於 wsgiref.util 模組中): wsgiref util -- WSGI 環境工具.
                                                             (line   93)
* is_imported() (symtable.Symbol 的方法): 檢查符號表.        (line  192)
* is_infinite() (decimal.Context 的方法): Context objects.   (line  319)
* is_infinite() (decimal.Decimal 的方法): Decimal objects.   (line  289)
* is_integer() (float 的方法):           浮點數的附加 methods.
                                                             (line   15)
* is_integer() (fractions.Fraction 的方法): fractions --- 有理數.
                                                             (line  129)
* is_integer() (int 的方法):             整數型別的附加 methods.
                                                             (line  155)
* is_junction() (os.DirEntry 的方法):    Files and Directories.
                                                             (line 1026)
* is_junction() (pathlib.Path 的方法):   Querying file type and status.
                                                             (line   84)
* is_jython (於 test.support 模組中):    test support --- Python 測試套件的工具.
                                                             (line   35)
* IS_LINE_JUNK() (於 difflib 模組中):    difflib --- 計算差異的輔助工具.
                                                             (line  355)
* is_linetouched() (curses.window 的方法): Window Objects.   (line  367)
* is_link_local (ipaddress.IPv4Address 的屬性): Address objects.
                                                             (line  172)
* is_link_local (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line   80)
* is_link_local (ipaddress.IPv6Address 的屬性): Address objects.
                                                             (line  278)
* is_link_local (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  307)
* is_local() (symtable.Symbol 的方法):   檢查符號表.         (line  212)
* is_loopback (ipaddress.IPv4Address 的屬性): Address objects.
                                                             (line  167)
* is_loopback (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line   78)
* is_loopback (ipaddress.IPv6Address 的屬性): Address objects.
                                                             (line  276)
* is_loopback (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  305)
* is_mount() (pathlib.Path 的方法):      Querying file type and status.
                                                             (line   91)
* is_multicast (ipaddress.IPv4Address 的屬性): Address objects.
                                                             (line   92)
* is_multicast (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line   70)
* is_multicast (ipaddress.IPv6Address 的屬性): Address objects.
                                                             (line  264)
* is_multicast (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  297)
* is_multipart() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  132)
* is_multipart() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  144)
* is_namespace() (symtable.Symbol 的方法): 檢查符號表.       (line  231)
* is_nan() (decimal.Context 的方法):     Context objects.    (line  323)
* is_nan() (decimal.Decimal 的方法):     Decimal objects.    (line  294)
* is_nested() (symtable.SymbolTable 的方法): 檢查符號表.     (line   90)
* is_nonlocal() (symtable.Symbol 的方法): 檢查符號表.        (line  204)
* is_normal() (decimal.Context 的方法):  Context objects.    (line  328)
* is_normal() (decimal.Decimal 的方法):  Decimal objects.    (line  299)
* is_normalized() (於 unicodedata 模組中): unicodedata --- Unicode 資料庫.
                                                             (line  117)
* is_not_allowed() (http.cookiejar.DefaultCookiePolicy 的方法): DefaultCookiePolicy 物件.
                                                             (line   74)
* is_not() (於 operator 模組中):         operator --- 標準運算子替代函式.
                                                             (line   59)
* IS_OP (opcode):                        Python Bytecode Instructions.
                                                             (line  796)
* is_optimized() (symtable.SymbolTable 的方法): 檢查符號表.  (line   86)
* is_package() (importlib.abc.InspectLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  260)
* is_package() (importlib.abc.SourceLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  448)
* is_package() (importlib.machinery.ExtensionFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  322)
* is_package() (importlib.machinery.SourceFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  214)
* is_package() (importlib.machinery.SourcelessFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  258)
* is_package() (zipimport.zipimporter 的方法): zipimporter 物件.
                                                             (line   73)
* is_parameter() (symtable.Symbol 的方法): 檢查符號表.       (line  196)
* is_private (ipaddress.IPv4Address 的屬性): Address objects.
                                                             (line   97)
* is_private (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line   72)
* is_private (ipaddress.IPv6Address 的屬性): Address objects.
                                                             (line  266)
* is_private (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  299)
* is_protocol() (於 typing 模組中):      Introspection helpers.
                                                             (line  112)
* is_python_build() (於 sysconfig 模組中): 其他函式<3>.      (line   50)
* is_qnan() (decimal.Context 的方法):    Context objects.    (line  333)
* is_qnan() (decimal.Decimal 的方法):    Decimal objects.    (line  305)
* is_reading() (asyncio.ReadTransport 的方法): Read-only Transports.
                                                             (line    6)
* is_referenced() (symtable.Symbol 的方法): 檢查符號表.      (line  188)
* is_relative_to() (pathlib.PurePath 的方法): 方法與屬性.    (line  197)
* is_reserved (ipaddress.IPv4Address 的屬性): Address objects.
                                                             (line  163)
* is_reserved (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line   76)
* is_reserved (ipaddress.IPv6Address 的屬性): Address objects.
                                                             (line  274)
* is_reserved (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  303)
* is_reserved() (pathlib.PurePath 的方法): 方法與屬性.       (line  219)
* is_resource_enabled() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  242)
* is_resource() (importlib.abc.ResourceReader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  508)
* is_resource() (importlib.resources.abc.ResourceReader 的方法): importlib resources abc -- 資源的抽象基底類別.
                                                             (line   62)
* is_resource() (於 importlib.resources 模組中): Functional API.
                                                             (line  136)
* is_running() (asyncio.loop 的方法):    啟動和停止迴圈.     (line   32)
* is_safe (uuid.UUID 的屬性):            uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  144)
* is_serving() (asyncio.Server 的方法):  Server 物件.        (line  109)
* is_set() (asyncio.Event 的方法):       Event.              (line   63)
* is_set() (threading.Event 的方法):     Event Objects.      (line   24)
* is_signed() (decimal.Context 的方法):  Context objects.    (line  338)
* is_signed() (decimal.Decimal 的方法):  Decimal objects.    (line  310)
* is_site_local (ipaddress.IPv6Address 的屬性): Address objects.
                                                             (line  280)
* is_site_local (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  357)
* is_skipped_line() (bdb.Bdb 的方法):    bdb --- 偵錯器框架. (line  243)
* is_snan() (decimal.Context 的方法):    Context objects.    (line  342)
* is_snan() (decimal.Decimal 的方法):    Decimal objects.    (line  316)
* is_socket() (pathlib.Path 的方法):     Querying file type and status.
                                                             (line  105)
* is_stack_trampoline_active() (於 sys 模組中): sys --- 系統特定的參數與函式.
                                                             (line 1725)
* is_subnormal() (decimal.Context 的方法): Context objects.  (line  347)
* is_subnormal() (decimal.Decimal 的方法): Decimal objects.  (line  321)
* is_symlink() (os.DirEntry 的方法):     Files and Directories.
                                                             (line 1007)
* is_symlink() (pathlib.Path 的方法):    Querying file type and status.
                                                             (line   77)
* is_symlink() (zipfile.Path 的方法):    Path Objects.       (line   55)
* is_tarfile() (於 tarfile 模組中):      tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  188)
* is_term_resized() (於 curses 模組中):  函式<5>.            (line  253)
* is_tracing() (於 tracemalloc 模組中):  函式<10>.           (line   61)
* is_tracked() (於 gc 模組中):           gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line  167)
* is_typeddict() (於 typing 模組中):     Introspection helpers.
                                                             (line  127)
* is_unspecified (ipaddress.IPv4Address 的屬性): Address objects.
                                                             (line  158)
* is_unspecified (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line   74)
* is_unspecified (ipaddress.IPv6Address 的屬性): Address objects.
                                                             (line  272)
* is_unspecified (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  301)
* is_valid() (string.Template 的方法):   模板字串.           (line   59)
* is_wintouched() (curses.window 的方法): Window Objects.    (line  374)
* is_zero() (decimal.Context 的方法):    Context objects.    (line  351)
* is_zero() (decimal.Decimal 的方法):    Decimal objects.    (line  326)
* is_zipfile() (於 zipfile 模組中):      zipfile --- 處理 ZIP 封存檔案.
                                                             (line   77)
* isabs() (於 os.path 模組中):           os path --- 常見的路徑名操作.
                                                             (line  181)
* isabstract() (於 inspect 模組中):      Types and members.  (line  510)
* IsADirectoryError:                     作業系統例外.       (line   77)
* isalnum() (bytearray 的方法):          Bytes and Bytearray Operations.
                                                             (line  507)
* isalnum() (bytes 的方法):              Bytes and Bytearray Operations.
                                                             (line  507)
* isalnum() (str 的方法):                String Methods<2>.  (line  179)
* isalnum() (於 curses.ascii 模組中):    curses ascii --- ASCII 字元的工具程式.
                                                             (line  134)
* isalpha() (bytearray 的方法):          Bytes and Bytearray Operations.
                                                             (line  525)
* isalpha() (bytes 的方法):              Bytes and Bytearray Operations.
                                                             (line  525)
* isalpha() (str 的方法):                String Methods<2>.  (line  186)
* isalpha() (於 curses.ascii 模組中):    curses ascii --- ASCII 字元的工具程式.
                                                             (line  139)
* isascii() (bytearray 的方法):          Bytes and Bytearray Operations.
                                                             (line  540)
* isascii() (bytes 的方法):              Bytes and Bytearray Operations.
                                                             (line  540)
* isascii() (str 的方法):                String Methods<2>.  (line  196)
* isascii() (於 curses.ascii 模組中):    curses ascii --- ASCII 字元的工具程式.
                                                             (line  144)
* isasyncgen() (於 inspect 模組中):      Types and members.  (line  471)
* isasyncgenfunction() (於 inspect 模組中): Types and members.
                                                             (line  450)
* isatty() (io.IOBase 的方法):           I/O 基礎類別.       (line   65)
* isatty() (於 os 模組中):               File Descriptor Operations.
                                                             (line  259)
* isawaitable() (於 inspect 模組中):     Types and members.  (line  429)
* isblank() (於 curses.ascii 模組中):    curses ascii --- ASCII 字元的工具程式.
                                                             (line  148)
* isblk() (tarfile.TarInfo 的方法):      TarInfo 物件.       (line  209)
* isbuiltin() (於 inspect 模組中):       Types and members.  (line  491)
* ischr() (tarfile.TarInfo 的方法):      TarInfo 物件.       (line  205)
* isclass() (於 inspect 模組中):         Types and members.  (line  356)
* isclose() (於 cmath 模組中):           分類函式.           (line   20)
* isclose() (於 math 模組中):            數論與表現函式.     (line  106)
* iscntrl() (於 curses.ascii 模組中):    curses ascii --- ASCII 字元的工具程式.
                                                             (line  152)
* iscode() (於 inspect 模組中):          Types and members.  (line  487)
* iscoroutine() (於 asyncio 模組中):     Introspection.      (line   26)
* iscoroutine() (於 inspect 模組中):     Types and members.  (line  422)
* iscoroutinefunction() (於 inspect 模組中): Types and members.
                                                             (line  386)
* isctrl() (於 curses.ascii 模組中):     curses ascii --- ASCII 字元的工具程式.
                                                             (line  193)
* isDaemon() (threading.Thread 的方法):  Thread Objects.     (line  215)
* isdatadescriptor() (於 inspect 模組中): Types and members. (line  537)
* isdecimal() (str 的方法):              String Methods<2>.  (line  204)
* isdev() (tarfile.TarInfo 的方法):      TarInfo 物件.       (line  217)
* isdevdrive() (於 os.path 模組中):      os path --- 常見的路徑名操作.
                                                             (line  238)
* isdigit() (bytearray 的方法):          Bytes and Bytearray Operations.
                                                             (line  548)
* isdigit() (bytes 的方法):              Bytes and Bytearray Operations.
                                                             (line  548)
* isdigit() (str 的方法):                String Methods<2>.  (line  212)
* isdigit() (於 curses.ascii 模組中):    curses ascii --- ASCII 字元的工具程式.
                                                             (line  157)
* isdir() (tarfile.TarInfo 的方法):      TarInfo 物件.       (line  193)
* isdir() (於 os.path 模組中):           os path --- 常見的路徑名操作.
                                                             (line  200)
* isdisjoint() (frozenset 的方法):       Set Types --- set frozenset.
                                                             (line   68)
* isdown() (於 turtle 模組中):           Drawing state.      (line   86)
* iselement() (於 xml.etree.ElementTree 模組中): 函式<8>.    (line  129)
* isenabled() (於 gc 模組中):            gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line   27)
* isEnabledFor() (logging.Logger 的方法): Logger 物件.       (line  141)
* isendwin() (於 curses 模組中):         函式<5>.            (line  258)
* ISEOF() (於 token 模組中):             token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   34)
* isfifo() (tarfile.TarInfo 的方法):     TarInfo 物件.       (line  213)
* isfile() (tarfile.TarInfo 的方法):     TarInfo 物件.       (line  184)
* isfile() (於 os.path 模組中):          os path --- 常見的路徑名操作.
                                                             (line  192)
* isfinite() (於 cmath 模組中):          分類函式.           (line    6)
* isfinite() (於 math 模組中):           數論與表現函式.     (line  134)
* isfirstline() (於 fileinput 模組中):   fileinput --- 逐列疊代多個輸入串流.
                                                             (line  111)
* isframe() (於 inspect 模組中):         Types and members.  (line  483)
* isfunction() (於 inspect 模組中):      Types and members.  (line  365)
* isfuture() (於 asyncio 模組中):        Future 函式.        (line    6)
* isgenerator() (於 inspect 模組中):     Types and members.  (line  382)
* isgeneratorfunction() (於 inspect 模組中): Types and members.
                                                             (line  370)
* isgetsetdescriptor() (於 inspect 模組中): Types and members.
                                                             (line  550)
* isgraph() (於 curses.ascii 模組中):    curses ascii --- ASCII 字元的工具程式.
                                                             (line  162)
* isidentifier() (str 的方法):           String Methods<2>.  (line  222)
* isinf() (於 cmath 模組中):             分類函式.           (line   12)
* isinf() (於 math 模組中):              數論與表現函式.     (line  141)
* isjunction() (於 os.path 模組中):      os path --- 常見的路徑名操作.
                                                             (line  208)
* iskeyword() (於 keyword 模組中):       keyword --- 檢驗 Python 關鍵字.
                                                             (line   13)
* isleap() (於 calendar 模組中):         calendar --- 日曆相關函式.
                                                             (line  269)
* islice() (於 itertools 模組中):        Itertool 函式.      (line  334)
* islink() (於 os.path 模組中):          os path --- 常見的路徑名操作.
                                                             (line  216)
* islnk() (tarfile.TarInfo 的方法):      TarInfo 物件.       (line  201)
* islower() (bytearray 的方法):          Bytes and Bytearray Operations.
                                                             (line  562)
* islower() (bytes 的方法):              Bytes and Bytearray Operations.
                                                             (line  562)
* islower() (str 的方法):                String Methods<2>.  (line  240)
* islower() (於 curses.ascii 模組中):    curses ascii --- ASCII 字元的工具程式.
                                                             (line  166)
* ismemberdescriptor() (於 inspect 模組中): Types and members.
                                                             (line  559)
* ismeta() (於 curses.ascii 模組中):     curses ascii --- ASCII 字元的工具程式.
                                                             (line  197)
* ismethod() (於 inspect 模組中):        Types and members.  (line  361)
* ismethoddescriptor() (於 inspect 模組中): Types and members.
                                                             (line  514)
* ismethodwrapper() (於 inspect 模組中): Types and members.  (line  496)
* ismodule() (於 inspect 模組中):        Types and members.  (line  352)
* ismount() (於 os.path 模組中):         os path --- 常見的路徑名操作.
                                                             (line  223)
* isnan() (於 cmath 模組中):             分類函式.           (line   16)
* isnan() (於 math 模組中):              數論與表現函式.     (line  145)
* ISNONTERMINAL() (於 token 模組中):     token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   30)
* IsNot (ast 中的類別):                  運算式<2>.          (line  105)
* isnumeric() (str 的方法):              String Methods<2>.  (line  246)
* isocalendar() (datetime.date 的方法):  date 物件.          (line  243)
* isocalendar() (datetime.datetime 的方法): datetime 物件.   (line  643)
* isoformat() (datetime.date 的方法):    date 物件.          (line  270)
* isoformat() (datetime.datetime 的方法): datetime 物件.     (line  648)
* isoformat() (datetime.time 的方法):    time 物件.          (line  164)
* isolated (sys.flags 的屬性):           sys --- 系統特定的參數與函式.
                                                             (line  531)
* IsolatedAsyncioTestCase (unittest 中的類別): Test cases.   (line  844)
* isolation_level (sqlite3.Connection 的屬性): Connection 物件.
                                                             (line  772)
* isoweekday() (datetime.date 的方法):   date 物件.          (line  236)
* isoweekday() (datetime.datetime 的方法): datetime 物件.    (line  637)
* isprint() (於 curses.ascii 模組中):    curses ascii --- ASCII 字元的工具程式.
                                                             (line  170)
* isprintable() (str 的方法):            String Methods<2>.  (line  256)
* ispunct() (於 curses.ascii 模組中):    curses ascii --- ASCII 字元的工具程式.
                                                             (line  174)
* isqrt() (於 math 模組中):              數論與表現函式.     (line  150)
* isreadable() (pprint.PrettyPrinter 的方法): PrettyPrinter 物件.
                                                             (line   66)
* isreadable() (於 pprint 模組中):       函式<3>.            (line   85)
* isrecursive() (pprint.PrettyPrinter 的方法): PrettyPrinter 物件.
                                                             (line   74)
* isrecursive() (於 pprint 模組中):      函式<3>.            (line   94)
* isreg() (tarfile.TarInfo 的方法):      TarInfo 物件.       (line  189)
* isreserved() (於 os.path 模組中):      os path --- 常見的路徑名操作.
                                                             (line  254)
* isReservedKey() (http.cookies.Morsel 的方法): Morsel 物件. (line   61)
* isroutine() (於 inspect 模組中):       Types and members.  (line  506)
* isSameNode() (xml.dom.Node 的方法):    Node Objects.       (line  102)
* issoftkeyword() (於 keyword 模組中):   keyword --- 檢驗 Python 關鍵字.
                                                             (line   23)
* isspace() (bytearray 的方法):          Bytes and Bytearray Operations.
                                                             (line  579)
* isspace() (bytes 的方法):              Bytes and Bytearray Operations.
                                                             (line  579)
* isspace() (str 的方法):                String Methods<2>.  (line  268)
* isspace() (於 curses.ascii 模組中):    curses ascii --- ASCII 字元的工具程式.
                                                             (line  179)
* isstdin() (於 fileinput 模組中):       fileinput --- 逐列疊代多個輸入串流.
                                                             (line  116)
* issubset() (frozenset 的方法):         Set Types --- set frozenset.
                                                             (line   74)
* issuperset() (frozenset 的方法):       Set Types --- set frozenset.
                                                             (line   85)
* issym() (tarfile.TarInfo 的方法):      TarInfo 物件.       (line  197)
* ISTERMINAL() (於 token 模組中):        token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   26)
* istitle() (bytearray 的方法):          Bytes and Bytearray Operations.
                                                             (line  587)
* istitle() (bytes 的方法):              Bytes and Bytearray Operations.
                                                             (line  587)
* istitle() (str 的方法):                String Methods<2>.  (line  278)
* istraceback() (於 inspect 模組中):     Types and members.  (line  479)
* isub() (於 operator 模組中):           原地 in-place 運算子.
                                                             (line   90)
* isupper() (bytearray 的方法):          Bytes and Bytearray Operations.
                                                             (line  601)
* isupper() (bytes 的方法):              Bytes and Bytearray Operations.
                                                             (line  601)
* isupper() (str 的方法):                String Methods<2>.  (line  285)
* isupper() (於 curses.ascii 模組中):    curses ascii --- ASCII 字元的工具程式.
                                                             (line  184)
* isvisible() (於 turtle 模組中):        Visibility.         (line   22)
* isxdigit() (於 curses.ascii 模組中):   curses ascii --- ASCII 字元的工具程式.
                                                             (line  188)
* ITALIC (於 tkinter.font 模組中):       tkinter font --- Tkinter 字型包裝器.
                                                             (line   15)
* item selection（項目選取）:            Sequences.          (line    6)
* item() (tkinter.ttk.Treeview 的方法):  ttk Treeview.       (line  201)
* item() (xml.dom.NamedNodeMap 的方法):  NamedNodeMap 物件.  (line   12)
* item() (xml.dom.NodeList 的方法):      NodeList 物件.      (line   15)
* itemgetter() (於 operator 模組中):     operator --- 標準運算子替代函式.
                                                             (line  253)
* items() (configparser.ConfigParser 的方法): ConfigParser 物件.
                                                             (line  262)
* items() (contextvars.Context 的方法):  Manual Context Management.
                                                             (line  113)
* items() (dict 的方法):                 Mapping Types --- dict.
                                                             (line  161)
* items() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  238)
* items() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  347)
* items() (mailbox.Mailbox 的方法):      Mailbox 物件.       (line  142)
* items() (types.MappingProxyType 的方法): Standard Interpreter Types.
                                                             (line  309)
* items() (xml.etree.ElementTree.Element 的方法): Element 物件.
                                                             (line   71)
* itemsize (array.array 的屬性):         array --- 高效率的數值型陣列.
                                                             (line  107)
* itemsize (memoryview 的屬性):          Memory Views.       (line  432)
* ItemsView (collections.abc 中的類別):  Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line  102)
* ItemsView (typing 中的類別):           collections abc 中容器 ABC 的別名.
                                                             (line   40)
* iter_attachments() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  557)
* iter_child_nodes() (於 ast 模組中):    ast 輔助程式.       (line  150)
* iter_fields() (於 ast 模組中):         ast 輔助程式.       (line  145)
* iter_importers() (於 pkgutil 模組中):  pkgutil --- 套件擴充工具程式.
                                                             (line   90)
* iter_modules() (於 pkgutil 模組中):    pkgutil --- 套件擴充工具程式.
                                                             (line  106)
* iter_parts() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  573)
* iter_unpack() (struct.Struct 的方法):  Classes<2>.         (line   46)
* iter_unpack() (於 struct 模組中):      函式與例外.         (line   42)
* iter() (xml.etree.ElementTree.Element 的方法): Element 物件.
                                                             (line  136)
* iter() (xml.etree.ElementTree.ElementTree 的方法): ElementTree 物件.
                                                             (line   40)
* Iterable (collections.abc 中的類別):   Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line   26)
* Iterable (typing 中的類別):            Aliases to other ABCs in collections abc.
                                                             (line    6)
* iterable（可疊代）;unpacking（解包）:  Expression lists.   (line   16)
* iterable（可疊代物件）:                術語表.             (line  652)
* Iterator (collections.abc 中的類別):   Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line   43)
* Iterator (typing 中的類別):            Aliases to other ABCs in collections abc.
                                                             (line   14)
* iterator protocol（疊代器協定）:       疊代器型別.         (line    6)
* iterator（疊代器）:                    術語表.             (line  671)
* iterdecode() (於 codecs 模組中):       codecs --- 編解碼器註冊表和基底類別.
                                                             (line  233)
* iterdir() (importlib.abc.Traversable 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  550)
* iterdir() (importlib.resources.abc.Traversable 的方法): importlib resources abc -- 資源的抽象基底類別.
                                                             (line   99)
* iterdir() (pathlib.Path 的方法):       讀取目錄.           (line    6)
* iterdir() (zipfile.Path 的方法):       Path Objects.       (line   43)
* iterdump() (sqlite3.Connection 的方法): Connection 物件.   (line  497)
* iterencode() (json.JSONEncoder 的方法): 編碼器與解碼器.    (line  206)
* iterencode() (於 codecs 模組中):       codecs --- 編解碼器註冊表和基底類別.
                                                             (line  221)
* iterfind() (xml.etree.ElementTree.Element 的方法): Element 物件.
                                                             (line  147)
* iterfind() (xml.etree.ElementTree.ElementTree 的方法): ElementTree 物件.
                                                             (line   47)
* iteritems() (mailbox.Mailbox 的方法):  Mailbox 物件.       (line  133)
* iterkeys() (mailbox.Mailbox 的方法):   Mailbox 物件.       (line  107)
* itermonthdates() (calendar.Calendar 的方法): calendar --- 日曆相關函式.
                                                             (line   38)
* itermonthdays() (calendar.Calendar 的方法): calendar --- 日曆相關函式.
                                                             (line   44)
* itermonthdays2() (calendar.Calendar 的方法): calendar --- 日曆相關函式.
                                                             (line   51)
* itermonthdays3() (calendar.Calendar 的方法): calendar --- 日曆相關函式.
                                                             (line   58)
* itermonthdays4() (calendar.Calendar 的方法): calendar --- 日曆相關函式.
                                                             (line   66)
* iternextfunc (C type):                 Slot Type typedefs. (line   92)
* iterparse() (於 xml.etree.ElementTree 模組中): 函式<8>.    (line  135)
* itertext() (xml.etree.ElementTree.Element 的方法): Element 物件.
                                                             (line  156)
* itervalues() (mailbox.Mailbox 的方法): Mailbox 物件.       (line  116)
* iterweekdays() (calendar.Calendar 的方法): calendar --- 日曆相關函式.
                                                             (line   33)
* ITIMER_PROF (於 signal 模組中):        模組內容<5>.        (line  223)
* ITIMER_REAL (於 signal 模組中):        模組內容<5>.        (line  213)
* ITIMER_VIRTUAL (於 signal 模組中):     模組內容<5>.        (line  218)
* ItimerError:                           模組內容<5>.        (line  256)
* itruediv() (於 operator 模組中):       原地 in-place 運算子.
                                                             (line   95)
* ixor() (於 operator 模組中):           原地 in-place 運算子.
                                                             (line  100)
* j;於數值常數中:                        浮點數常數 Floating-point literals.
                                                             (line   28)
* JANUARY (於 calendar 模組中):          calendar --- 日曆相關函式.
                                                             (line  365)
* java_ver() (於 platform 模組中):       Java 平台.          (line    6)
* Java;language（語言）:                 numbers Real float. (line    6)
* join_thread() (multiprocessing.Queue 的方法): Pipes and Queues.
                                                             (line  180)
* join_thread() (於 test.support.threading_helper 模組中): test support threading_helper --- Utilities for threading tests.
                                                             (line   11)
* join() (asyncio.Queue 的方法):         Queue.              (line   50)
* join() (bytearray 的方法):             Bytes and Bytearray Operations.
                                                             (line  164)
* join() (bytes 的方法):                 Bytes and Bytearray Operations.
                                                             (line  164)
* join() (multiprocessing.JoinableQueue 的方法): Pipes and Queues.
                                                             (line  265)
* join() (multiprocessing.pool.Pool 的方法): Process Pools.  (line  183)
* join() (multiprocessing.Process 的方法): Process 與例外.   (line   66)
* join() (queue.Queue 的方法):           佇列物件.           (line   81)
* join() (str 的方法):                   String Methods<2>.  (line  300)
* join() (threading.Thread 的方法):      Thread Objects.     (line  127)
* join() (於 os.path 模組中):            os path --- 常見的路徑名操作.
                                                             (line  276)
* join() (於 shlex 模組中):              shlex --- 簡單的語法分析.
                                                             (line   29)
* JoinableQueue (multiprocessing 中的類別): Pipes and Queues.
                                                             (line  244)
* JoinedStr (ast 中的類別):              文本 Literals.      (line   39)
* joinpath() (importlib.abc.Traversable 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  562)
* joinpath() (importlib.resources.abc.Traversable 的方法): importlib resources abc -- 資源的抽象基底類別.
                                                             (line  111)
* joinpath() (pathlib.PurePath 的方法):  方法與屬性.         (line  233)
* joinpath() (zipfile.Path 的方法):      Path Objects.       (line  104)
* js_output() (http.cookies.BaseCookie 的方法): Cookie 物件. (line   32)
* js_output() (http.cookies.Morsel 的方法): Morsel 物件.     (line   72)
* json.tool 命令列選項; -compact:        命令列選項<3>.      (line   48)
* json.tool 命令列選項; -h:              命令列選項<3>.      (line   54)
* json.tool 命令列選項; -help:           命令列選項<3>.      (line   54)
* json.tool 命令列選項; -indent:         命令列選項<3>.      (line   48)
* json.tool 命令列選項; -json-lines:     命令列選項<3>.      (line   42)
* json.tool 命令列選項; -no-ensure-ascii: 命令列選項<3>.     (line   35)
* json.tool 命令列選項; -no-indent:      命令列選項<3>.      (line   48)
* json.tool 命令列選項; -sort-keys:      命令列選項<3>.      (line   29)
* json.tool 命令列選項; -tab:            命令列選項<3>.      (line   48)
* json.tool 命令列選項; infile:          命令列選項<3>.      (line    6)
* json.tool 命令列選項; outfile:         命令列選項<3>.      (line   24)
* JSONDecodeError:                       例外<12>.           (line    6)
* JSONDecoder (json 中的類別):           編碼器與解碼器.     (line    6)
* JSONEncoder (json 中的類別):           編碼器與解碼器.     (line   96)
* JULY (於 calendar 模組中):             calendar --- 日曆相關函式.
                                                             (line  365)
* JUMP (monitoring event):               事件.               (line   34)
* JUMP (opcode):                         Python Bytecode Instructions.
                                                             (line 1398)
* jump (pdb command):                    Debugger Commands.  (line  230)
* JUMP_BACKWARD (opcode):                Python Bytecode Instructions.
                                                             (line  827)
* JUMP_BACKWARD_NO_INTERRUPT (opcode):   Python Bytecode Instructions.
                                                             (line  833)
* JUMP_FORWARD (opcode):                 Python Bytecode Instructions.
                                                             (line  823)
* JUMP_NO_INTERRUPT (opcode):            Python Bytecode Instructions.
                                                             (line 1400)
* JUNE (於 calendar 模組中):             calendar --- 日曆相關函式.
                                                             (line  365)
* kbhit() (於 msvcrt 模組中):            Console I/O.        (line    6)
* kde_random() (於 statistics 模組中):   函式細節.           (line  169)
* kde() (於 statistics 模組中):          函式細節.           (line  122)
* KEEP (enum.FlagBoundary 的屬性):       資料型別<2>.        (line  665)
* kevent() (於 select 模組中):           select --- 等待 I/O 完成.
                                                             (line  106)
* key (http.cookies.Morsel 的屬性):      Morsel 物件.        (line   53)
* key (zoneinfo.ZoneInfo 的屬性):        The ZoneInfo class. (line   75)
* key function（鍵函式）:                術語表.             (line  694)
* KEY_A1 (於 curses 模組中):             Constants.          (line  236)
* KEY_A3 (於 curses 模組中):             Constants.          (line  239)
* KEY_ALL_ACCESS (於 winreg 模組中):     Access Rights.      (line    8)
* KEY_B2 (於 curses 模組中):             Constants.          (line  242)
* KEY_BACKSPACE (於 curses 模組中):      Constants.          (line  166)
* KEY_BEG (於 curses 模組中):            Constants.          (line  254)
* KEY_BREAK (於 curses 模組中):          Constants.          (line  148)
* KEY_BTAB (於 curses 模組中):           Constants.          (line  251)
* KEY_C1 (於 curses 模組中):             Constants.          (line  245)
* KEY_C3 (於 curses 模組中):             Constants.          (line  248)
* KEY_CANCEL (於 curses 模組中):         Constants.          (line  257)
* KEY_CATAB (於 curses 模組中):          Constants.          (line  218)
* KEY_CLEAR (於 curses 模組中):          Constants.          (line  191)
* KEY_CLOSE (於 curses 模組中):          Constants.          (line  260)
* KEY_COMMAND (於 curses 模組中):        Constants.          (line  263)
* KEY_COPY (於 curses 模組中):           Constants.          (line  266)
* KEY_CREATE (於 curses 模組中):         Constants.          (line  269)
* KEY_CREATE_LINK (於 winreg 模組中):    Access Rights.      (line   51)
* KEY_CREATE_SUB_KEY (於 winreg 模組中): Access Rights.      (line   38)
* KEY_CTAB (於 curses 模組中):           Constants.          (line  215)
* KEY_DC (於 curses 模組中):             Constants.          (line  182)
* KEY_DL (於 curses 模組中):             Constants.          (line  176)
* KEY_DOWN (於 curses 模組中):           Constants.          (line  151)
* KEY_EIC (於 curses 模組中):            Constants.          (line  188)
* KEY_END (於 curses 模組中):            Constants.          (line  272)
* KEY_ENTER (於 curses 模組中):          Constants.          (line  221)
* KEY_ENUMERATE_SUB_KEYS (於 winreg 模組中): Access Rights.  (line   42)
* KEY_EOL (於 curses 模組中):            Constants.          (line  197)
* KEY_EOS (於 curses 模組中):            Constants.          (line  194)
* KEY_EXECUTE (於 winreg 模組中):        Access Rights.      (line   26)
* KEY_EXIT (於 curses 模組中):           Constants.          (line  275)
* KEY_F0 (於 curses 模組中):             Constants.          (line  169)
* KEY_FIND (於 curses 模組中):           Constants.          (line  278)
* KEY_Fn (於 curses 模組中):             Constants.          (line  173)
* KEY_HELP (於 curses 模組中):           Constants.          (line  281)
* KEY_HOME (於 curses 模組中):           Constants.          (line  163)
* KEY_IC (於 curses 模組中):             Constants.          (line  185)
* KEY_IL (於 curses 模組中):             Constants.          (line  179)
* KEY_LEFT (於 curses 模組中):           Constants.          (line  157)
* KEY_LL (於 curses 模組中):             Constants.          (line  233)
* KEY_MARK (於 curses 模組中):           Constants.          (line  284)
* KEY_MAX (於 curses 模組中):            Constants.          (line  425)
* KEY_MESSAGE (於 curses 模組中):        Constants.          (line  287)
* KEY_MIN (於 curses 模組中):            Constants.          (line  145)
* KEY_MOUSE (於 curses 模組中):          Constants.          (line  419)
* KEY_MOVE (於 curses 模組中):           Constants.          (line  290)
* KEY_NEXT (於 curses 模組中):           Constants.          (line  293)
* KEY_NOTIFY (於 winreg 模組中):         Access Rights.      (line   46)
* KEY_NPAGE (於 curses 模組中):          Constants.          (line  206)
* KEY_OPEN (於 curses 模組中):           Constants.          (line  296)
* KEY_OPTIONS (於 curses 模組中):        Constants.          (line  299)
* KEY_PPAGE (於 curses 模組中):          Constants.          (line  209)
* KEY_PREVIOUS (於 curses 模組中):       Constants.          (line  302)
* KEY_PRINT (於 curses 模組中):          Constants.          (line  230)
* KEY_QUERY_VALUE (於 winreg 模組中):    Access Rights.      (line   30)
* KEY_READ (於 winreg 模組中):           Access Rights.      (line   20)
* KEY_REDO (於 curses 模組中):           Constants.          (line  305)
* KEY_REFERENCE (於 curses 模組中):      Constants.          (line  308)
* KEY_REFRESH (於 curses 模組中):        Constants.          (line  311)
* KEY_REPLACE (於 curses 模組中):        Constants.          (line  314)
* KEY_RESET (於 curses 模組中):          Constants.          (line  227)
* KEY_RESIZE (於 curses 模組中):         Constants.          (line  422)
* KEY_RESTART (於 curses 模組中):        Constants.          (line  317)
* KEY_RESUME (於 curses 模組中):         Constants.          (line  320)
* KEY_RIGHT (於 curses 模組中):          Constants.          (line  160)
* KEY_SAVE (於 curses 模組中):           Constants.          (line  323)
* KEY_SBEG (於 curses 模組中):           Constants.          (line  326)
* KEY_SCANCEL (於 curses 模組中):        Constants.          (line  329)
* KEY_SCOMMAND (於 curses 模組中):       Constants.          (line  332)
* KEY_SCOPY (於 curses 模組中):          Constants.          (line  335)
* KEY_SCREATE (於 curses 模組中):        Constants.          (line  338)
* KEY_SDC (於 curses 模組中):            Constants.          (line  341)
* KEY_SDL (於 curses 模組中):            Constants.          (line  344)
* KEY_SELECT (於 curses 模組中):         Constants.          (line  347)
* KEY_SEND (於 curses 模組中):           Constants.          (line  350)
* KEY_SEOL (於 curses 模組中):           Constants.          (line  353)
* KEY_SET_VALUE (於 winreg 模組中):      Access Rights.      (line   34)
* KEY_SEXIT (於 curses 模組中):          Constants.          (line  356)
* KEY_SF (於 curses 模組中):             Constants.          (line  200)
* KEY_SFIND (於 curses 模組中):          Constants.          (line  359)
* KEY_SHELP (於 curses 模組中):          Constants.          (line  362)
* KEY_SHOME (於 curses 模組中):          Constants.          (line  365)
* KEY_SIC (於 curses 模組中):            Constants.          (line  368)
* KEY_SLEFT (於 curses 模組中):          Constants.          (line  371)
* KEY_SMESSAGE (於 curses 模組中):       Constants.          (line  374)
* KEY_SMOVE (於 curses 模組中):          Constants.          (line  377)
* KEY_SNEXT (於 curses 模組中):          Constants.          (line  380)
* KEY_SOPTIONS (於 curses 模組中):       Constants.          (line  383)
* KEY_SPREVIOUS (於 curses 模組中):      Constants.          (line  386)
* KEY_SPRINT (於 curses 模組中):         Constants.          (line  389)
* KEY_SR (於 curses 模組中):             Constants.          (line  203)
* KEY_SREDO (於 curses 模組中):          Constants.          (line  392)
* KEY_SREPLACE (於 curses 模組中):       Constants.          (line  395)
* KEY_SRESET (於 curses 模組中):         Constants.          (line  224)
* KEY_SRIGHT (於 curses 模組中):         Constants.          (line  398)
* KEY_SRSUME (於 curses 模組中):         Constants.          (line  401)
* KEY_SSAVE (於 curses 模組中):          Constants.          (line  404)
* KEY_SSUSPEND (於 curses 模組中):       Constants.          (line  407)
* KEY_STAB (於 curses 模組中):           Constants.          (line  212)
* KEY_SUNDO (於 curses 模組中):          Constants.          (line  410)
* KEY_SUSPEND (於 curses 模組中):        Constants.          (line  413)
* KEY_UNDO (於 curses 模組中):           Constants.          (line  416)
* KEY_UP (於 curses 模組中):             Constants.          (line  154)
* KEY_WOW64_32KEY (於 winreg 模組中):    64-bit Specific.    (line   14)
* KEY_WOW64_64KEY (於 winreg 模組中):    64-bit Specific.    (line    8)
* KEY_WRITE (於 winreg 模組中):          Access Rights.      (line   15)
* key（鍵）:                             Dictionary displays.
                                                             (line    6)
* key/value pair（鍵/值對）:             Dictionary displays.
                                                             (line    6)
* KeyboardInterrupt:                     實體例外.           (line   76)
* KeyboardInterrupt（內建例外）:         Signal Handling<2>. (line    7)
* KeyboardInterrupt（內建例外） <1>:     Signal Handling<2>. (line   34)
* KeyboardInterrupt（內建例外） <2>:     Signal Handling<2>. (line   43)
* KeyError:                              實體例外.           (line   72)
* keylog_filename (ssl.SSLContext 的屬性): SSL Contexts.     (line  531)
* keyname() (於 curses 模組中):          函式<5>.            (line  263)
* keypad() (curses.window 的方法):       Window Objects.     (line  379)
* keyrefs() (weakref.WeakKeyDictionary 的方法): weakref --- 弱參照.
                                                             (line  164)
* keys() (contextvars.Context 的方法):   Manual Context Management.
                                                             (line  105)
* keys() (dict 的方法):                  Mapping Types --- dict.
                                                             (line  166)
* keys() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  230)
* keys() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  339)
* keys() (mailbox.Mailbox 的方法):       Mailbox 物件.       (line  111)
* keys() (sqlite3.Row 的方法):           Row 物件.           (line   18)
* keys() (types.MappingProxyType 的方法): Standard Interpreter Types.
                                                             (line  314)
* keys() (xml.etree.ElementTree.Element 的方法): Element 物件.
                                                             (line   76)
* KeysView (collections.abc 中的類別):   Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line  102)
* KeysView (typing 中的類別):            collections abc 中容器 ABC 的別名.
                                                             (line   49)
* keyword (ast 中的類別):                運算式<2>.          (line  147)
* keyword argument（關鍵字引數）:        術語表.             (line  715)
* keyword（關鍵字）:                     關鍵字.             (line    6)
* keyword（關鍵字） <1>:                 軟關鍵字.           (line    6)
* keyword（關鍵字）;as:                  import 陳述式.      (line    6)
* keyword（關鍵字）;as <1>:              The try statement.  (line    6)
* keyword（關鍵字）;as <2>:              The with statement. (line    6)
* keyword（關鍵字）;as <3>:              The match statement.
                                                             (line    6)
* keyword（關鍵字）;async:               協程函式定義.       (line    9)
* keyword（關鍵字）;await:               Calls.              (line  157)
* keyword（關鍵字）;await <1>:           協程函式定義.       (line    9)
* keyword（關鍵字）;case:                The match statement.
                                                             (line    6)
* keyword（關鍵字）;elif:                The if statement.   (line    6)
* keyword（關鍵字）;else:                break 陳述式.       (line   12)
* keyword（關鍵字）;else <1>:            The if statement.   (line    6)
* keyword（關鍵字）;else <2>:            The while statement.
                                                             (line    6)
* keyword（關鍵字）;else <3>:            The for statement.  (line    6)
* keyword（關鍵字）;else <4>:            The try statement.  (line    6)
* keyword（關鍵字）;else <5>:            except* 子句.       (line   57)
* keyword（關鍵字）;except:              The try statement.  (line    6)
* keyword（關鍵字）;except_star:         except clause.      (line   82)
* keyword（關鍵字）;finally:             return 陳述式.      (line   17)
* keyword（關鍵字）;finally <1>:         break 陳述式.       (line   18)
* keyword（關鍵字）;finally <2>:         continue 陳述式.    (line    6)
* keyword（關鍵字）;finally <3>:         The try statement.  (line    6)
* keyword（關鍵字）;finally <4>:         else clause.        (line   11)
* keyword（關鍵字）;from:                Yield expressions.  (line    6)
* keyword（關鍵字）;from <1>:            import 陳述式.      (line    6)
* keyword（關鍵字）;if:                  The match statement.
                                                             (line    6)
* keyword（關鍵字）;in:                  The for statement.  (line    6)
* keyword（關鍵字）;yield:               Yield expressions.  (line    6)
* keywords (functools.partial 的屬性):   partial 物件.       (line   19)
* kill_python() (於 test.support.script_helper 模組中): test support script_helper --- 用於 Python 執行測試的工具.
                                                             (line   73)
* kill() (asyncio.subprocess.Process 的方法): Interacting with Subprocesses.
                                                             (line  105)
* kill() (asyncio.SubprocessTransport 的方法): Subprocess Transports.
                                                             (line   35)
* kill() (multiprocessing.Process 的方法): Process 與例外.   (line  189)
* kill() (subprocess.Popen 的方法):      Popen Objects.      (line   92)
* kill() (於 os 模組中):                 行程管理.           (line  323)
* killchar() (於 curses 模組中):         函式<5>.            (line  273)
* killpg() (於 os 模組中):               行程管理.           (line  346)
* kind (inspect.Parameter 的屬性):       Introspecting callables with the Signature object.
                                                             (line  229)
* knownfiles (於 mimetypes 模組中):      mimetypes --- 將檔案名稱對映到 MIME 類型.
                                                             (line  135)
* kqueue() (於 select 模組中):           select --- 等待 I/O 完成.
                                                             (line   96)
* KqueueSelector (selectors 中的類別):   Classes<3>.         (line  195)
* KW_ONLY (於 dataclasses 模組中):       模組內容<8>.        (line  470)
* kwargs (inspect.BoundArguments 的屬性): Introspecting callables with the Signature object.
                                                             (line  358)
* kwargs (typing.ParamSpec 的屬性):      Building generic types and type aliases.
                                                             (line  409)
* kwlist (於 keyword 模組中):            keyword --- 檢驗 Python 關鍵字.
                                                             (line   17)
* L (於 re 模組中):                      旗標.               (line   58)
* lambda:                                術語表.             (line  719)
* Lambda (ast 中的類別):                 函式和類別定義.     (line   30)
* lambda;expression:                     Lambdas.            (line    6)
* lambda;expression（運算式）:           函式定義.           (line  121)
* lambda;form:                           Lambdas.            (line    6)
* LambdaType (於 types 模組中):          Standard Interpreter Types.
                                                             (line   25)
* LANG:                                  GNU gettext API.    (line   21)
* LANG <1>:                              Class-based API.    (line   26)
* LANG <2>:                              locale --- 國際化服務.
                                                             (line   49)
* LANG <3>:                              locale --- 國際化服務.
                                                             (line  344)
* LANG <4>:                              locale --- 國際化服務.
                                                             (line  348)
* LANGUAGE:                              GNU gettext API.    (line   20)
* LANGUAGE <1>:                          Class-based API.    (line   25)
* large files（大型檔案）:               對大檔案 Large File 的支援.
                                                             (line    6)
* LARGEST (於 test.support 模組中):      test support --- Python 測試套件的工具.
                                                             (line  183)
* LargeZipFile:                          zipfile --- 處理 ZIP 封存檔案.
                                                             (line   37)
* last_accepted (multiprocessing.connection.Listener 的屬性): Listeners and Clients.
                                                             (line  103)
* last_exc (於 sys 模組中):              sys --- 系統特定的參數與函式.
                                                             (line 1177)
* last_traceback （sys 模組中）:         Traceback objects.  (line    6)
* last_traceback (於 sys 模組中):        sys --- 系統特定的參數與函式.
                                                             (line 1200)
* last_type (於 sys 模組中):             sys --- 系統特定的參數與函式.
                                                             (line 1200)
* last_value (於 sys 模組中):            sys --- 系統特定的參數與函式.
                                                             (line 1200)
* lastChild (xml.dom.Node 的屬性):       Node Objects.       (line   59)
* lastcmd (cmd.Cmd 的屬性):              Cmd 物件.           (line  139)
* lastgroup (re.Match 的屬性):           Match Objects.      (line  200)
* lastindex (re.Match 的屬性):           Match Objects.      (line  192)
* lastResort (於 logging 模組中):        Module-Level Attributes.
                                                             (line    6)
* lastrowid (sqlite3.Cursor 的屬性):     Cursor 物件.        (line  199)
* layout() (tkinter.ttk.Style 的方法):   Ttk Styling.        (line   96)
* lazycache() (於 linecache 模組中):     linecache --- 隨機存取文字列.
                                                             (line   50)
* LazyLoader (importlib.util 中的類別):  importlib util -- Utility code for importers.
                                                             (line  192)
* LBRACE (於 token 模組中):              token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  126)
* LBYL:                                  術語表.             (line  725)
* LC_ALL:                                GNU gettext API.    (line   20)
* LC_ALL <1>:                            Class-based API.    (line   25)
* LC_ALL (於 locale 模組中):             locale --- 國際化服務.
                                                             (line  556)
* LC_COLLATE (於 locale 模組中):         locale --- 國際化服務.
                                                             (line  522)
* LC_CTYPE (於 locale 模組中):           locale --- 國際化服務.
                                                             (line  508)
* LC_MESSAGES:                           GNU gettext API.    (line   20)
* LC_MESSAGES <1>:                       Class-based API.    (line   26)
* LC_MESSAGES (於 locale 模組中):        locale --- 國際化服務.
                                                             (line  538)
* LC_MONETARY (於 locale 模組中):        locale --- 國際化服務.
                                                             (line  533)
* LC_NUMERIC (於 locale 模組中):         locale --- 國際化服務.
                                                             (line  548)
* LC_TIME (於 locale 模組中):            locale --- 國際化服務.
                                                             (line  528)
* lchflags() (於 os 模組中):             Files and Directories.
                                                             (line  300)
* lchmod() (pathlib.Path 的方法):        Permissions and ownership.
                                                             (line   53)
* lchmod() (於 os 模組中):               Files and Directories.
                                                             (line  314)
* lchown() (於 os 模組中):               Files and Directories.
                                                             (line  335)
* lcm() (於 math 模組中):                數論與表現函式.     (line  161)
* LDCXXSHARED:                           Build and C API Changes<7>.
                                                             (line  153)
* ldexp() (於 math 模組中):              數論與表現函式.     (line  169)
* LDFLAGS:                               New Improved and Deprecated Modules<4>.
                                                             (line   59)
* LDFLAGS <1>:                           Preprocessor flags. (line   18)
* LDFLAGS <2>:                           Linker flags.       (line   15)
* LDFLAGS <3>:                           Linker flags.       (line   18)
* LDFLAGS <4>:                           Linker flags.       (line   28)
* LDFLAGS <5>:                           Linker flags.       (line   31)
* LDFLAGS <6>:                           Linker flags.       (line   35)
* LDFLAGS <7>:                           Linker flags.       (line   50)
* LDFLAGS_NODIST:                        Linker flags.       (line   26)
* LDFLAGS_NODIST <1>:                    Linker flags.       (line   40)
* le() (於 operator 模組中):             operator --- 標準運算子替代函式.
                                                             (line   20)
* leading whitespace（前置空白）:        Indentation.        (line    6)
* leapdays() (於 calendar 模組中):       calendar --- 日曆相關函式.
                                                             (line  274)
* leaveok() (curses.window 的方法):      Window Objects.     (line  386)
* left (filecmp.dircmp 的屬性):          The dircmp class.   (line   44)
* left_list (filecmp.dircmp 的屬性):     The dircmp class.   (line   52)
* left_only (filecmp.dircmp 的屬性):     The dircmp class.   (line   66)
* left() (於 turtle 模組中):             Turtle motion.      (line   57)
* LEFTSHIFT (於 token 模組中):           token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  158)
* LEFTSHIFTEQUAL (於 token 模組中):      token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  202)
* LEGACY_TRANSACTION_CONTROL (於 sqlite3 模組中): Module constants.
                                                             (line    6)
* lenfunc (C type):                      Slot Type typedefs. (line   96)
* length (xml.dom.NamedNodeMap 的屬性):  NamedNodeMap 物件.  (line    8)
* length (xml.dom.NodeList 的屬性):      NodeList 物件.      (line   21)
* length_hint() (於 operator 模組中):    operator --- 標準運算子替代函式.
                                                             (line  197)
* LESS (於 token 模組中):                token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  106)
* LESSEQUAL (於 token 模組中):           token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  142)
* level (logging.Logger 的屬性):         Logger 物件.        (line   33)
* lexical analysis（詞法分析）:          詞法分析.           (line    6)
* lexical definitions（詞法定義）:       Notation.           (line   32)
* LexicalHandler (xml.sax.handler 中的類別): xml sax handler --- SAX 處理函式的基本類別.
                                                             (line   45)
* lexists() (於 os.path 模組中):         os path --- 常見的路徑名操作.
                                                             (line  110)
* LF (於 curses.ascii 模組中):           curses ascii --- ASCII 字元的工具程式.
                                                             (line   52)
* lgamma() (於 math 模組中):             Special functions.  (line   35)
* libc_ver() (於 platform 模組中):       Unix 平台.          (line    6)
* LIBRARIES_ASSEMBLY_NAME_PREFIX (於 msvcrt 模組中): Other Functions.
                                                             (line   98)
* library (ssl.SSLError 的屬性):         例外<11>.           (line   16)
* library (於 dbm.ndbm 模組中):          dbm ndbm --- 新資料庫管理器.
                                                             (line   29)
* LibraryLoader (ctypes 中的類別):       Loading shared libraries.
                                                             (line  167)
* license (內建變數):                    由 site module（模組）所添增的常數.
                                                             (line   29)
* LifoQueue (asyncio 中的類別):          LIFO Queue.         (line    6)
* LifoQueue (queue 中的類別):            queue --- 同步佇列 synchronized queue 類別.
                                                             (line   34)
* light-weight processes（輕量級行程）:  _thread --- 低階執行緒 API.
                                                             (line    6)
* limit_denominator() (fractions.Fraction 的方法): fractions --- 有理數.
                                                             (line  155)
* LimitOverrunError:                     例外<8>.            (line   55)
* line (bdb.Breakpoint 的屬性):          bdb --- 偵錯器框架. (line   85)
* LINE (monitoring event):               事件.               (line   38)
* line (traceback.FrameSummary 的屬性):  FrameSummary 物件.  (line   42)
* line continuation（列延續）:           Explicit line joining.
                                                             (line    6)
* line joining（列連接）:                Logical lines.      (line    6)
* line joining（列連接） <1>:            Explicit line joining.
                                                             (line    6)
* line structure（列結構）:              Line structure.     (line    6)
* line_buffering (io.TextIOWrapper 的屬性): 文字 I/O<2>.     (line  169)
* line_num (csv.csvreader 的屬性):       讀取器物件.         (line   22)
* line-buffered I/O（行緩衝 I/O）:       內建函式.           (line 1294)
* linear_regression() (於 statistics 模組中): 函式細節.      (line  572)
* lineno (ast.AST 的屬性):               節點 Node 類別.     (line   43)
* lineno (doctest.DocTest 的屬性):       DocTest 物件.       (line   42)
* lineno (doctest.Example 的屬性):       Example 物件.       (line   41)
* lineno (inspect.FrameInfo 的屬性):     直譯器堆疊.         (line   22)
* lineno (inspect.Traceback 的屬性):     直譯器堆疊.         (line   62)
* lineno (json.JSONDecodeError 的屬性):  例外<12>.           (line   22)
* lineno (netrc.NetrcParseError 的屬性): netrc --- netrc 檔案處理.
                                                             (line   49)
* lineno (pyclbr.Class 的屬性):          Class Objects.      (line   24)
* lineno (pyclbr.Function 的屬性):       函式物件.           (line   23)
* lineno (re.PatternError 的屬性):       Exceptions.         (line   28)
* lineno (shlex.shlex 的屬性):           shlex 物件.         (line  168)
* lineno (SyntaxError 的屬性):           實體例外.           (line  267)
* lineno (traceback.FrameSummary 的屬性): FrameSummary 物件. (line   33)
* lineno (traceback.TracebackException 的屬性): TracebackException 物件.
                                                             (line   90)
* lineno (tracemalloc.Filter 的屬性):    Filter.             (line   49)
* lineno (tracemalloc.Frame 的屬性):     Frame.              (line   17)
* lineno (xml.parsers.expat.ExpatError 的屬性): ExpatError 例外.
                                                             (line   27)
* lineno() (於 fileinput 模組中):        fileinput --- 逐列疊代多個輸入串流.
                                                             (line   97)
* LINES:                                 函式<5>.            (line  125)
* LINES <1>:                             函式<5>.            (line  595)
* LINES <2>:                             函式<5>.            (line  597)
* lines (os.terminal_size 的屬性):       Querying the size of a terminal.
                                                             (line   34)
* LINES (於 curses 模組中):              Constants.          (line   53)
* linesep (email.policy.Policy 的屬性):  email policy Policy Objects.
                                                             (line  153)
* linesep (於 os 模組中):                Miscellaneous System Information.
                                                             (line  150)
* lineterminator (csv.Dialect 的屬性):   Dialect 與格式參數. (line   39)
* LineTooLong:                           http client --- HTTP 協定用戶端.
                                                             (line  182)
* link() (於 os 模組中):                 Files and Directories.
                                                             (line  349)
* linkname (tarfile.TarInfo 的屬性):     TarInfo 物件.       (line   95)
* LinkOutsideDestinationError:           tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  255)
* List (ast 中的類別):                   文本 Literals.      (line   63)
* list (pdb command):                    Debugger Commands.  (line  240)
* List (typing 中的類別):                內建型別的別名.     (line   17)
* list (內建類別):                       List（串列）<2>.    (line   10)
* list comprehension（串列綜合運算）:    術語表.             (line  743)
* LIST_APPEND (opcode):                  Python Bytecode Instructions.
                                                             (line  373)
* list_dialects() (於 csv 模組中):       模組內容<3>.        (line   82)
* LIST_EXTEND (opcode):                  Python Bytecode Instructions.
                                                             (line  699)
* list_folders() (mailbox.Maildir 的方法): Mailbox 物件<2>.  (line   65)
* list_folders() (mailbox.MH 的方法):    MH 物件.            (line   35)
* list() (imaplib.IMAP4 的方法):         IMAP4 物件.         (line  126)
* list() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  230)
* list() (poplib.POP3 的方法):           POP3 物件.          (line   57)
* list() (tarfile.TarFile 的方法):       TarFile 物件.       (line  121)
* list（串列）:                          術語表.             (line  737)
* list（串列）;comprehensions:           List displays.      (line    6)
* list（串列）;display:                  List displays.      (line    6)
* ListComp (ast 中的類別):               綜合運算式 comprehensions.
                                                             (line    6)
* listdir() (於 os 模組中):              Files and Directories.
                                                             (line  371)
* listdrives() (於 os 模組中):           Files and Directories.
                                                             (line  407)
* listen() (socket.socket 的方法):       Socket 物件.        (line  197)
* listen() (於 logging.config 模組中):   Configuration functions.
                                                             (line  118)
* listen() (於 turtle 模組中):           Using screen events.
                                                             (line    6)
* listener (logging.handlers.QueueHandler 的屬性): QueueHandler.
                                                             (line   84)
* Listener (multiprocessing.connection 中的類別): Listeners and Clients.
                                                             (line   50)
* listMethods() (xmlrpc.client.ServerProxy.system 的方法): ServerProxy 物件.
                                                             (line   17)
* listmounts() (於 os 模組中):           Files and Directories.
                                                             (line  425)
* listvolumes() (於 os 模組中):          Files and Directories.
                                                             (line  448)
* listxattr() (於 os 模組中):            Linux extended attributes.
                                                             (line   26)
* literal:                               Literals<2>.        (line    6)
* Literal (於 typing 模組中):            特別型式.           (line  118)
* literal_eval() (於 ast 模組中):        ast 輔助程式.       (line   75)
* literal（常數）:                       Literals.           (line    6)
* LiteralString (於 typing 模組中):      特別型別.           (line   64)
* LittleEndianStructure (ctypes 中的類別): Structured data types.
                                                             (line   26)
* LittleEndianUnion (ctypes 中的類別):   Structured data types.
                                                             (line   16)
* ljust() (bytearray 的方法):            Bytes and Bytearray Operations.
                                                             (line  300)
* ljust() (bytes 的方法):                Bytes and Bytearray Operations.
                                                             (line  300)
* ljust() (str 的方法):                  String Methods<2>.  (line  308)
* LK_LOCK (於 msvcrt 模組中):            File Operations.    (line   19)
* LK_NBLCK (於 msvcrt 模組中):           File Operations.    (line   27)
* LK_NBRLCK (於 msvcrt 模組中):          File Operations.    (line   27)
* LK_RLCK (於 msvcrt 模組中):            File Operations.    (line   19)
* LK_UNLCK (於 msvcrt 模組中):           File Operations.    (line   33)
* ll (pdb command):                      Debugger Commands.  (line  256)
* LMTP (smtplib 中的類別):               smtplib --- SMTP 協定用戶端.
                                                             (line  104)
* ln() (decimal.Context 的方法):         Context objects.    (line  355)
* ln() (decimal.Decimal 的方法):         Decimal objects.    (line  331)
* LNKTYPE (於 tarfile 模組中):           tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  272)
* Load (ast 中的類別):                   變數.               (line   10)
* LOAD_ASSERTION_ERROR (opcode):         Python Bytecode Instructions.
                                                             (line  493)
* LOAD_ATTR (opcode):                    Python Bytecode Instructions.
                                                             (line  739)
* LOAD_BUILD_CLASS (opcode):             Python Bytecode Instructions.
                                                             (line  500)
* load_cert_chain() (ssl.SSLContext 的方法): SSL Contexts.   (line  104)
* LOAD_CLOSURE (opcode):                 Python Bytecode Instructions.
                                                             (line 1405)
* LOAD_CONST (opcode):                   Python Bytecode Instructions.
                                                             (line  624)
* load_default_certs() (ssl.SSLContext 的方法): SSL Contexts.
                                                             (line  135)
* LOAD_DEREF (opcode):                   Python Bytecode Instructions.
                                                             (line  949)
* load_dh_params() (ssl.SSLContext 的方法): SSL Contexts.    (line  356)
* load_extension() (sqlite3.Connection 的方法): Connection 物件.
                                                             (line  471)
* LOAD_FAST (opcode):                    Python Bytecode Instructions.
                                                             (line  909)
* LOAD_FAST_AND_CLEAR (opcode):          Python Bytecode Instructions.
                                                             (line  926)
* LOAD_FAST_CHECK (opcode):              Python Bytecode Instructions.
                                                             (line  918)
* LOAD_FROM_DICT_OR_DEREF (opcode):      Python Bytecode Instructions.
                                                             (line  957)
* LOAD_FROM_DICT_OR_GLOBALS (opcode):    Python Bytecode Instructions.
                                                             (line  643)
* LOAD_GLOBAL (opcode):                  Python Bytecode Instructions.
                                                             (line  902)
* LOAD_LOCALS (opcode):                  Python Bytecode Instructions.
                                                             (line  634)
* LOAD_METHOD (opcode):                  Python Bytecode Instructions.
                                                             (line 1415)
* load_module() (importlib.abc.FileLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  338)
* load_module() (importlib.abc.InspectLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  292)
* load_module() (importlib.abc.Loader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  126)
* load_module() (importlib.abc.SourceLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  437)
* load_module() (importlib.machinery.SourceFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  229)
* load_module() (importlib.machinery.SourcelessFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  273)
* load_module() (zipimport.zipimporter 的方法): zipimporter 物件.
                                                             (line   79)
* LOAD_NAME (opcode):                    Python Bytecode Instructions.
                                                             (line  628)
* load_package_tests() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  620)
* LOAD_SUPER_ATTR (opcode):              Python Bytecode Instructions.
                                                             (line  757)
* load_verify_locations() (ssl.SSLContext 的方法): SSL Contexts.
                                                             (line  152)
* load() (http.cookiejar.FileCookieJar 的方法): CookieJar 與 FileCookieJar 物件.
                                                             (line  126)
* load() (http.cookies.BaseCookie 的方法): Cookie 物件.      (line   40)
* load() (pickle.Unpickler 的方法):      模組介面.           (line  271)
* load() (tracemalloc.Snapshot 的類別方法): Snapshot.        (line   50)
* load() (於 json 模組中):               基本用法<2>.        (line   83)
* load() (於 marshal 模組中):            marshal --- 内部 Python 物件序列化.
                                                             (line   68)
* load() (於 pickle 模組中):             模組介面.           (line   58)
* load() (於 plistlib 模組中):           plistlib --- 產生和剖析 Apple plist 檔案.
                                                             (line   46)
* load() (於 tomllib 模組中):            tomllib --- 剖析 TOML 檔案.
                                                             (line   31)
* Loader (importlib.abc 中的類別):       importlib abc -- Abstract base classes related to import.
                                                             (line   91)
* loader (importlib.machinery.ModuleSpec 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  381)
* loader_state (importlib.machinery.ModuleSpec 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  410)
* loader（載入器）:                      Finders and loaders.
                                                             (line    6)
* loader（載入器） <1>:                  術語表.             (line  751)
* LoadError:                             http cookiejar --- HTTP 客戶端的 Cookie 處理.
                                                             (line   34)
* LoadFileDialog (tkinter.filedialog 中的類別): Native Load/Save Dialogs.
                                                             (line  135)
* LoadKey() (於 winreg 模組中):          函式<12>.           (line  258)
* LoadLibrary() (ctypes.LibraryLoader 的方法): Loading shared libraries.
                                                             (line  178)
* loads() (於 json 模組中):              基本用法<2>.        (line  137)
* loads() (於 marshal 模組中):           marshal --- 内部 Python 物件序列化.
                                                             (line  103)
* loads() (於 pickle 模組中):            模組介面.           (line   76)
* loads() (於 plistlib 模組中):          plistlib --- 產生和剖析 Apple plist 檔案.
                                                             (line   82)
* loads() (於 tomllib 模組中):           tomllib --- 剖析 TOML 檔案.
                                                             (line   45)
* loads() (於 xmlrpc.client 模組中):     便捷的函式.         (line   19)
* loadTestsFromModule() (unittest.TestLoader 的方法): Loading and running tests.
                                                             (line   41)
* loadTestsFromName() (unittest.TestLoader 的方法): Loading and running tests.
                                                             (line   70)
* loadTestsFromNames() (unittest.TestLoader 的方法): Loading and running tests.
                                                             (line  104)
* loadTestsFromTestCase() (unittest.TestLoader 的方法): Loading and running tests.
                                                             (line   29)
* local (threading 中的類別):            Thread-Local Data.  (line   15)
* LOCAL_CREDS (於 socket 模組中):        常數<7>.            (line  318)
* LOCAL_CREDS_PERSISTENT (於 socket 模組中): 常數<7>.        (line  318)
* localcontext() (於 decimal 模組中):    Context objects.    (line   25)
* LOCALE (於 re 模組中):                 旗標.               (line   58)
* locale encoding（區域編碼）:           術語表.             (line  758)
* localeconv() (於 locale 模組中):       locale --- 國際化服務.
                                                             (line   53)
* LocaleHTMLCalendar (calendar 中的類別): calendar --- 日曆相關函式.
                                                             (line  243)
* LocaleTextCalendar (calendar 中的類別): calendar --- 日曆相關函式.
                                                             (line  238)
* localize() (於 locale 模組中):         locale --- 國際化服務.
                                                             (line  490)
* localName (xml.dom.Attr 的屬性):       Attr Objects.       (line   13)
* localName (xml.dom.Node 的屬性):       Node Objects.       (line   64)
* localtime() (於 email.utils 模組中):   email utils：雜項工具.
                                                             (line   13)
* localtime() (於 time 模組中):          函式<4>.            (line  132)
* Locator (xml.sax.xmlreader 中的類別):  xml sax xmlreader --- XML 剖析器的介面.
                                                             (line   43)
* Lock (asyncio 中的類別):               Lock.               (line    6)
* Lock (multiprocessing 中的類別):       Synchronization primitives.
                                                             (line   45)
* lock (sys.thread_info 的屬性):         sys --- 系統特定的參數與函式.
                                                             (line 1885)
* Lock (threading 中的類別):             Lock Objects.       (line   33)
* LOCK_EX (於 fcntl 模組中):             fcntl --- fcntl 和 ioctl 系統呼叫.
                                                             (line  176)
* LOCK_NB (於 fcntl 模組中):             fcntl --- fcntl 和 ioctl 系統呼叫.
                                                             (line  180)
* LOCK_SH (於 fcntl 模組中):             fcntl --- fcntl 和 ioctl 系統呼叫.
                                                             (line  172)
* LOCK_UN (於 fcntl 模組中):             fcntl --- fcntl 和 ioctl 系統呼叫.
                                                             (line  168)
* lock, interpreter（鎖、直譯器）:       Thread State and the Global Interpreter Lock.
                                                             (line    6)
* lock() (mailbox.Babyl 的方法):         Babyl 物件.         (line   59)
* lock() (mailbox.Mailbox 的方法):       Mailbox 物件.       (line  256)
* lock() (mailbox.Maildir 的方法):       Mailbox 物件<2>.    (line  209)
* lock() (mailbox.mbox 的方法):          mbox 物件.          (line   38)
* lock() (mailbox.MH 的方法):            MH 物件.            (line   87)
* lock() (mailbox.MMDF 的方法):          MMDF 物件.          (line   35)
* Lock() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  187)
* locked() (_thread.lock 的方法):        _thread --- 低階執行緒 API.
                                                             (line  143)
* locked() (asyncio.Condition 的方法):   Condition.          (line   56)
* locked() (asyncio.Lock 的方法):        Lock.               (line   56)
* locked() (asyncio.Semaphore 的方法):   Semaphore.          (line   46)
* locked() (threading.Lock 的方法):      Lock Objects.       (line   87)
* lockf() (於 fcntl 模組中):             fcntl --- fcntl 和 ioctl 系統呼叫.
                                                             (line  161)
* lockf() (於 os 模組中):                File Descriptor Operations.
                                                             (line  264)
* locking() (於 msvcrt 模組中):          File Operations.    (line    6)
* LockType (於 _thread 模組中):          _thread --- 低階執行緒 API.
                                                             (line   24)
* LOG_ALERT (於 syslog 模組中):          syslog --- Unix syslog 函式庫例程.
                                                             (line  111)
* LOG_AUTH (於 syslog 模組中):           syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* LOG_AUTHPRIV (於 syslog 模組中):       syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* LOG_CONS (於 syslog 模組中):           syslog --- Unix syslog 函式庫例程.
                                                             (line  157)
* LOG_CRIT (於 syslog 模組中):           syslog --- Unix syslog 函式庫例程.
                                                             (line  111)
* LOG_CRON (於 syslog 模組中):           syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* LOG_DAEMON (於 syslog 模組中):         syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* log_date_time_string() (http.server.BaseHTTPRequestHandler 的方法): http server — HTTP 伺服器.
                                                             (line  327)
* LOG_DEBUG (於 syslog 模組中):          syslog --- Unix syslog 函式庫例程.
                                                             (line  111)
* LOG_EMERG (於 syslog 模組中):          syslog --- Unix syslog 函式庫例程.
                                                             (line  111)
* LOG_ERR (於 syslog 模組中):            syslog --- Unix syslog 函式庫例程.
                                                             (line  111)
* log_error() (http.server.BaseHTTPRequestHandler 的方法): http server — HTTP 伺服器.
                                                             (line  296)
* log_exception() (wsgiref.handlers.BaseHandler 的方法): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  178)
* LOG_FTP (於 syslog 模組中):            syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* LOG_INFO (於 syslog 模組中):           syslog --- Unix syslog 函式庫例程.
                                                             (line  111)
* LOG_INSTALL (於 syslog 模組中):        syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* LOG_KERN (於 syslog 模組中):           syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* LOG_LAUNCHD (於 syslog 模組中):        syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* LOG_LOCAL0 (於 syslog 模組中):         syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* LOG_LOCAL1 (於 syslog 模組中):         syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* LOG_LOCAL2 (於 syslog 模組中):         syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* LOG_LOCAL3 (於 syslog 模組中):         syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* LOG_LOCAL4 (於 syslog 模組中):         syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* LOG_LOCAL5 (於 syslog 模組中):         syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* LOG_LOCAL6 (於 syslog 模組中):         syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* LOG_LOCAL7 (於 syslog 模組中):         syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* LOG_LPR (於 syslog 模組中):            syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* LOG_MAIL (於 syslog 模組中):           syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* log_message() (http.server.BaseHTTPRequestHandler 的方法): http server — HTTP 伺服器.
                                                             (line  302)
* LOG_NDELAY (於 syslog 模組中):         syslog --- Unix syslog 函式庫例程.
                                                             (line  157)
* LOG_NETINFO (於 syslog 模組中):        syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* LOG_NEWS (於 syslog 模組中):           syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* LOG_NOTICE (於 syslog 模組中):         syslog --- Unix syslog 函式庫例程.
                                                             (line  111)
* LOG_NOWAIT (於 syslog 模組中):         syslog --- Unix syslog 函式庫例程.
                                                             (line  157)
* LOG_ODELAY (於 syslog 模組中):         syslog --- Unix syslog 函式庫例程.
                                                             (line  157)
* LOG_PERROR (於 syslog 模組中):         syslog --- Unix syslog 函式庫例程.
                                                             (line  157)
* LOG_PID (於 syslog 模組中):            syslog --- Unix syslog 函式庫例程.
                                                             (line  157)
* LOG_RAS (於 syslog 模組中):            syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* LOG_REMOTEAUTH (於 syslog 模組中):     syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* log_request() (http.server.BaseHTTPRequestHandler 的方法): http server — HTTP 伺服器.
                                                             (line  289)
* LOG_SYSLOG (於 syslog 模組中):         syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* log_to_stderr() (於 multiprocessing 模組中): Logging.      (line   24)
* LOG_USER (於 syslog 模組中):           syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* LOG_UUCP (於 syslog 模組中):           syslog --- Unix syslog 函式庫例程.
                                                             (line  122)
* LOG_WARNING (於 syslog 模組中):        syslog --- Unix syslog 函式庫例程.
                                                             (line  111)
* log() (logging.Logger 的方法):         Logger 物件.        (line  310)
* log() (於 cmath 模組中):               冪函數和對數函數.   (line   10)
* log() (於 logging 模組中):             Module-Level Functions.
                                                             (line   99)
* log() (於 math 模組中):                Power and logarithmic functions.
                                                             (line   40)
* log10() (decimal.Context 的方法):      Context objects.    (line  359)
* log10() (decimal.Decimal 的方法):      Decimal objects.    (line  337)
* log10() (於 cmath 模組中):             冪函數和對數函數.   (line   15)
* log10() (於 math 模組中):              Power and logarithmic functions.
                                                             (line   67)
* log1p() (於 math 模組中):              Power and logarithmic functions.
                                                             (line   48)
* log2() (於 math 模組中):               Power and logarithmic functions.
                                                             (line   53)
* logb() (decimal.Context 的方法):       Context objects.    (line  363)
* logb() (decimal.Decimal 的方法):       Decimal objects.    (line  343)
* Logger (logging 中的類別):             Logger 物件.        (line   24)
* LoggerAdapter (logging 中的類別):      LoggerAdapter 物件. (line   11)
* logical line（邏輯列）:                Logical lines.      (line    6)
* logical_and() (decimal.Context 的方法): Context objects.   (line  367)
* logical_and() (decimal.Decimal 的方法): Decimal objects.   (line  351)
* logical_invert() (decimal.Context 的方法): Context objects.
                                                             (line  372)
* logical_invert() (decimal.Decimal 的方法): Decimal objects.
                                                             (line  357)
* logical_or() (decimal.Context 的方法): Context objects.    (line  376)
* logical_or() (decimal.Decimal 的方法): Decimal objects.    (line  362)
* logical_xor() (decimal.Context 的方法): Context objects.   (line  381)
* logical_xor() (decimal.Decimal 的方法): Decimal objects.   (line  368)
* login_cram_md5() (imaplib.IMAP4 的方法): IMAP4 物件.       (line  137)
* login_tty() (於 os 模組中):            File Descriptor Operations.
                                                             (line  290)
* login() (ftplib.FTP 的方法):           FTP 物件.           (line  113)
* login() (imaplib.IMAP4 的方法):        IMAP4 物件.         (line  132)
* login() (smtplib.SMTP 的方法):         SMTP 物件.          (line  102)
* LOGNAME:                               行程參數.           (line  239)
* LOGNAME <1>:                           getpass --- 可攜式密碼輸入工具.
                                                             (line   41)
* lognormvariate() (於 random 模組中):   實數分布.           (line   65)
* logout() (imaplib.IMAP4 的方法):       IMAP4 物件.         (line  143)
* LogRecord (logging 中的類別):          LogRecord 物件.     (line   11)
* LONG_MAX（C 巨集）:                    整數物件.           (line  141)
* LONG_TIMEOUT (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line   92)
* longMessage (unittest.TestCase 的屬性): Test cases.        (line  693)
* longname() (於 curses 模組中):         函式<5>.            (line  280)
* lookup_error() (於 codecs 模組中):     Error Handlers.     (line  130)
* lookup() (symtable.SymbolTable 的方法): 檢查符號表.        (line  104)
* lookup() (tkinter.ttk.Style 的方法):   Ttk Styling.        (line   81)
* lookup() (於 codecs 模組中):           codecs --- 編解碼器註冊表和基底類別.
                                                             (line   47)
* lookup() (於 unicodedata 模組中):      unicodedata --- Unicode 資料庫.
                                                             (line   16)
* LookupError:                           基底類別 base classes.
                                                             (line   71)
* loop control（迴圈控制）;target:       break 陳述式.       (line   12)
* loop_factory (unittest.IsolatedAsyncioTestCase 的屬性): Test cases.
                                                             (line  851)
* loop（迴圈）;over mutable sequence（於可變序列）: Common Sequence Operations.
                                                             (line   75)
* loop（迴圈）;statement（陳述式）:      break 陳述式.       (line    6)
* loop（迴圈）;statement（陳述式） <1>:  continue 陳述式.    (line    6)
* loop（迴圈）;statement（陳述式） <2>:  The while statement.
                                                             (line    6)
* loop（迴圈）;statement（陳述式） <3>:  The for statement.  (line    6)
* LOOPBACK_TIMEOUT (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line   47)
* lower() (bytearray 的方法):            Bytes and Bytearray Operations.
                                                             (line  619)
* lower() (bytes 的方法):                Bytes and Bytearray Operations.
                                                             (line  619)
* lower() (str 的方法):                  String Methods<2>.  (line  315)
* LPAR (於 token 模組中):                token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   54)
* lpAttributeList (subprocess.STARTUPINFO 的屬性): Windows Popen Helpers.
                                                             (line   60)
* lru_cache() (於 functools 模組中):     functools --- 可呼叫物件上的高階函式與操作.
                                                             (line  123)
* lseek() (於 os 模組中):                File Descriptor Operations.
                                                             (line  301)
* LShift (ast 中的類別):                 運算式<2>.          (line   52)
* lshift() (於 operator 模組中):         operator --- 標準運算子替代函式.
                                                             (line  100)
* LSQB (於 token 模組中):                token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   62)
* lstat() (pathlib.Path 的方法):         Querying file type and status.
                                                             (line   28)
* lstat() (於 os 模組中):                Files and Directories.
                                                             (line  468)
* lstrip() (bytearray 的方法):           Bytes and Bytearray Operations.
                                                             (line  312)
* lstrip() (bytes 的方法):               Bytes and Bytearray Operations.
                                                             (line  312)
* lstrip() (str 的方法):                 String Methods<2>.  (line  323)
* lsub() (imaplib.IMAP4 的方法):         IMAP4 物件.         (line  150)
* Lt (ast 中的類別):                     運算式<2>.          (line  105)
* lt() (於 operator 模組中):             operator --- 標準運算子替代函式.
                                                             (line   20)
* lt() (於 turtle 模組中):               Turtle motion.      (line   57)
* LtE (ast 中的類別):                    運算式<2>.          (line  105)
* LWPCookieJar (http.cookiejar 中的類別): FileCookieJar subclasses and co-operation with web browsers.
                                                             (line   28)
* LZMACompressor (lzma 中的類別):        Compressing and decompressing data in memory.
                                                             (line    6)
* LZMADecompressor (lzma 中的類別):      Compressing and decompressing data in memory.
                                                             (line  100)
* LZMAError:                             lzma --- 使用 LZMA 演算法進行壓縮.
                                                             (line   24)
* LZMAFile (lzma 中的類別):              Reading and writing compressed files.
                                                             (line   44)
* M (於 re 模組中):                      旗標.               (line   81)
* mac_ver() (於 platform 模組中):        macOS 平台.         (line    6)
* machine() (於 platform 模組中):        跨平台.             (line   31)
* macros (netrc.netrc 的屬性):           netrc 物件.         (line   26)
* MADV_AUTOSYNC (於 mmap 模組中):        MADV_* Constants.   (line    6)
* MADV_CORE (於 mmap 模組中):            MADV_* Constants.   (line    6)
* MADV_DODUMP (於 mmap 模組中):          MADV_* Constants.   (line    6)
* MADV_DOFORK (於 mmap 模組中):          MADV_* Constants.   (line    6)
* MADV_DONTDUMP (於 mmap 模組中):        MADV_* Constants.   (line    6)
* MADV_DONTFORK (於 mmap 模組中):        MADV_* Constants.   (line    6)
* MADV_DONTNEED (於 mmap 模組中):        MADV_* Constants.   (line    6)
* MADV_FREE (於 mmap 模組中):            MADV_* Constants.   (line    6)
* MADV_FREE_REUSABLE (於 mmap 模組中):   MADV_* Constants.   (line    6)
* MADV_FREE_REUSE (於 mmap 模組中):      MADV_* Constants.   (line    6)
* MADV_HUGEPAGE (於 mmap 模組中):        MADV_* Constants.   (line    6)
* MADV_HWPOISON (於 mmap 模組中):        MADV_* Constants.   (line    6)
* MADV_MERGEABLE (於 mmap 模組中):       MADV_* Constants.   (line    6)
* MADV_NOCORE (於 mmap 模組中):          MADV_* Constants.   (line    6)
* MADV_NOHUGEPAGE (於 mmap 模組中):      MADV_* Constants.   (line    6)
* MADV_NORMAL (於 mmap 模組中):          MADV_* Constants.   (line    6)
* MADV_NOSYNC (於 mmap 模組中):          MADV_* Constants.   (line    6)
* MADV_PROTECT (於 mmap 模組中):         MADV_* Constants.   (line    6)
* MADV_RANDOM (於 mmap 模組中):          MADV_* Constants.   (line    6)
* MADV_REMOVE (於 mmap 模組中):          MADV_* Constants.   (line    6)
* MADV_SEQUENTIAL (於 mmap 模組中):      MADV_* Constants.   (line    6)
* MADV_SOFT_OFFLINE (於 mmap 模組中):    MADV_* Constants.   (line    6)
* MADV_UNMERGEABLE (於 mmap 模組中):     MADV_* Constants.   (line    6)
* MADV_WILLNEED (於 mmap 模組中):        MADV_* Constants.   (line    6)
* madvise() (mmap.mmap 的方法):          mmap --- 記憶體映射檔案的支援.
                                                             (line  223)
* magic method（魔術方法）:              術語表.             (line  771)
* MAGIC_NUMBER (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line   13)
* magic;method（方法）:                  術語表.             (line  775)
* MagicMock (unittest.mock 中的類別):    Magic Mock.         (line    9)
* Mailbox (mailbox 中的類別):            Mailbox 物件.       (line    6)
* Maildir (mailbox 中的類別):            Mailbox 物件<2>.    (line    6)
* MaildirMessage (mailbox 中的類別):     MaildirMessage 物件.
                                                             (line    6)
* main_thread() (於 threading 模組中):   threading --- 基於執行緒的平行性.
                                                             (line  150)
* main():                                Process-wide parameters.
                                                             (line    7)
* main() <1>:                            Process-wide parameters.
                                                             (line  216)
* main() <2>:                            PyConfig.           (line  127)
* main() (於 site 模組中):               模組內容<10>.       (line   42)
* main() (於 unittest 模組中):           Loading and running tests.
                                                             (line  514)
* mainloop() (於 turtle 模組中):         Using screen events.
                                                             (line  106)
* maintype (email.headerregistry.ContentTypeHeader 的屬性): email headerregistry：自訂標頭物件.
                                                             (line  276)
* major (email.headerregistry.MIMEVersionHeader 的屬性): email headerregistry：自訂標頭物件.
                                                             (line  247)
* major() (於 os 模組中):                Files and Directories.
                                                             (line  612)
* make_alternative() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  604)
* make_archive() (於 shutil 模組中):     Archiving operations.
                                                             (line   14)
* make_bad_fd() (於 test.support.os_helper 模組中): test support os_helper --- 用於 os 測試的工具.
                                                             (line  105)
* MAKE_CELL (opcode):                    Python Bytecode Instructions.
                                                             (line  942)
* make_cookies() (http.cookiejar.CookieJar 的方法): CookieJar 與 FileCookieJar 物件.
                                                             (line   61)
* make_dataclass() (於 dataclasses 模組中): 模組內容<8>.     (line  381)
* make_file() (difflib.HtmlDiff 的方法): difflib --- 計算差異的輔助工具.
                                                             (line  112)
* MAKE_FUNCTION (opcode):                Python Bytecode Instructions.
                                                             (line 1080)
* make_header() (於 email.header 模組中): email header：國際化標頭.
                                                             (line  200)
* make_legacy_pyc() (於 test.support.import_helper 模組中): test support import_helper --- 用於 import 測試的工具.
                                                             (line   78)
* make_mixed() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  614)
* make_msgid() (於 email.utils 模組中):  email utils：雜項工具.
                                                             (line   27)
* make_parser() (於 xml.sax 模組中):     xml sax --- SAX2 剖析器支援.
                                                             (line   28)
* make_pkg() (於 test.support.script_helper 模組中): test support script_helper --- 用於 Python 執行測試的工具.
                                                             (line   93)
* make_related() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  595)
* make_script() (於 test.support.script_helper 模組中): test support script_helper --- 用於 Python 執行測試的工具.
                                                             (line   78)
* make_server() (於 wsgiref.simple_server 模組中): wsgiref simple_server -- 一個簡單的 WSGI HTTP 伺服器.
                                                             (line   12)
* make_table() (difflib.HtmlDiff 的方法): difflib --- 計算差異的輔助工具.
                                                             (line  144)
* make_zip_pkg() (於 test.support.script_helper 模組中): test support script_helper --- 用於 Python 執行測試的工具.
                                                             (line   98)
* make_zip_script() (於 test.support.script_helper 模組中): test support script_helper --- 用於 Python 執行測試的工具.
                                                             (line   85)
* makedev() (於 os 模組中):              Files and Directories.
                                                             (line  622)
* makedirs() (於 os 模組中):             Files and Directories.
                                                             (line  533)
* makeelement() (xml.etree.ElementTree.Element 的方法): Element 物件.
                                                             (line  164)
* makefile() （socket 方法）:            I/O objects also known as file objects.
                                                             (line    6)
* makefile() (socket.socket 的方法):     Socket 物件.        (line  209)
* makeLogRecord() (於 logging 模組中):   Module-Level Functions.
                                                             (line  196)
* makePickle() (logging.handlers.SocketHandler 的方法): SocketHandler.
                                                             (line   45)
* makeRecord() (logging.Logger 的方法):  Logger 物件.        (line  371)
* makeSocket() (logging.handlers.DatagramHandler 的方法): DatagramHandler.
                                                             (line   37)
* makeSocket() (logging.handlers.SocketHandler 的方法): SocketHandler.
                                                             (line   39)
* maketrans() (bytearray 的靜態方法):    Bytes and Bytearray Operations.
                                                             (line  174)
* maketrans() (bytes 的靜態方法):        Bytes and Bytearray Operations.
                                                             (line  174)
* maketrans() (str 的靜態方法):          String Methods<2>.  (line  345)
* malloc（C 函式）:                      總覽<2>.            (line   33)
* manager (logging.LoggerAdapter 的屬性): LoggerAdapter 物件.
                                                             (line   30)
* mangle_from_ (email.policy.Compat32 的屬性): email policy Policy Objects.
                                                             (line  575)
* mangle_from_ (email.policy.Policy 的屬性): email policy Policy Objects.
                                                             (line  187)
* mant_dig (sys.float_info 的屬性):      sys --- 系統特定的參數與函式.
                                                             (line  624)
* MAP_32BIT (於 mmap 模組中):            MAP_* 常數.         (line    6)
* MAP_ADD (opcode):                      Python Bytecode Instructions.
                                                             (line  382)
* MAP_ALIGNED_SUPER (於 mmap 模組中):    MAP_* 常數.         (line    6)
* MAP_ANON (於 mmap 模組中):             MAP_* 常數.         (line    6)
* MAP_ANONYMOUS (於 mmap 模組中):        MAP_* 常數.         (line    6)
* map_async() (multiprocessing.pool.Pool 的方法): Process Pools.
                                                             (line  110)
* MAP_CONCEAL (於 mmap 模組中):          MAP_* 常數.         (line    6)
* MAP_DENYWRITE (於 mmap 模組中):        MAP_* 常數.         (line    6)
* MAP_EXECUTABLE (於 mmap 模組中):       MAP_* 常數.         (line    6)
* MAP_HASSEMAPHORE (於 mmap 模組中):     MAP_* 常數.         (line    6)
* MAP_JIT (於 mmap 模組中):              MAP_* 常數.         (line    6)
* MAP_NOCACHE (於 mmap 模組中):          MAP_* 常數.         (line    6)
* MAP_NOEXTEND (於 mmap 模組中):         MAP_* 常數.         (line    6)
* MAP_NORESERVE (於 mmap 模組中):        MAP_* 常數.         (line    6)
* MAP_POPULATE (於 mmap 模組中):         MAP_* 常數.         (line    6)
* MAP_PRIVATE (於 mmap 模組中):          MAP_* 常數.         (line    6)
* MAP_RESILIENT_CODESIGN (於 mmap 模組中): MAP_* 常數.       (line    6)
* MAP_RESILIENT_MEDIA (於 mmap 模組中):  MAP_* 常數.         (line    6)
* MAP_SHARED (於 mmap 模組中):           MAP_* 常數.         (line    6)
* MAP_STACK (於 mmap 模組中):            MAP_* 常數.         (line    6)
* map_table_b2() (於 stringprep 模組中): stringprep --- 網際網路字串準備.
                                                             (line   50)
* map_table_b3() (於 stringprep 模組中): stringprep --- 網際網路字串準備.
                                                             (line   55)
* map_to_type() (email.headerregistry.HeaderRegistry 的方法): email headerregistry：自訂標頭物件.
                                                             (line  376)
* MAP_TPRO (於 mmap 模組中):             MAP_* 常數.         (line    6)
* MAP_TRANSLATED_ALLOW_EXECUTE (於 mmap 模組中): MAP_* 常數. (line    6)
* MAP_UNIX03 (於 mmap 模組中):           MAP_* 常數.         (line    6)
* map() (concurrent.futures.Executor 的方法): Executor 物件. (line   20)
* map() (multiprocessing.pool.Pool 的方法): Process Pools.   (line   93)
* map() (tkinter.ttk.Style 的方法):      Ttk Styling.        (line   48)
* mapLogRecord() (logging.handlers.HTTPHandler 的方法): HTTPHandler.
                                                             (line   27)
* Mapping (collections.abc 中的類別):    Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line   97)
* Mapping (typing 中的類別):             collections abc 中容器 ABC 的別名.
                                                             (line   57)
* mapping（對映）:                       術語表.             (line  775)
* MappingProxyType (types 中的類別):     Standard Interpreter Types.
                                                             (line  267)
* MappingView (collections.abc 中的類別): Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line  102)
* MappingView (typing 中的類別):         collections abc 中容器 ABC 的別名.
                                                             (line   65)
* mapPriority() (logging.handlers.SysLogHandler 的方法): SysLogHandler.
                                                             (line  201)
* maps (collections.ChainMap 的屬性):    ChainMap 物件.      (line   34)
* MARCH (於 calendar 模組中):            calendar --- 日曆相關函式.
                                                             (line  365)
* markcoroutinefunction() (於 inspect 模組中): Types and members.
                                                             (line  406)
* marshalling;objects（物件）:           pickle --- Python 物件序列化.
                                                             (line    8)
* masking（遮罩）;operations（操作）:    整數型別的位元運算. (line    6)
* master (tkinter.Tk 的屬性):            Tkinter Modules.    (line   77)
* Match (ast 中的類別):                  模式匹配 pattern matching.
                                                             (line    6)
* Match (re 中的類別):                   Match Objects.      (line   15)
* Match (typing 中的類別):               Aliases to other concrete types.
                                                             (line    6)
* match_case (ast 中的類別):             模式匹配 pattern matching.
                                                             (line   14)
* MATCH_CLASS (opcode):                  Python Bytecode Instructions.
                                                             (line 1182)
* MATCH_KEYS (opcode):                   Python Bytecode Instructions.
                                                             (line  541)
* MATCH_MAPPING (opcode):                Python Bytecode Instructions.
                                                             (line  522)
* MATCH_SEQUENCE (opcode):               Python Bytecode Instructions.
                                                             (line  531)
* match_value() (test.support.Matcher 的方法): test support --- Python 測試套件的工具.
                                                             (line  781)
* match;case:                            The match statement.
                                                             (line    6)
* match() (pathlib.PurePath 的方法):     方法與屬性.         (line  276)
* match() (re.Pattern 的方法):           Regular Expression Objects.
                                                             (line   42)
* match() (於 re 模組中):                Functions.          (line   48)
* MatchAs (ast 中的類別):                模式匹配 pattern matching.
                                                             (line  275)
* MatchClass (ast 中的類別):             模式匹配 pattern matching.
                                                             (line  217)
* Matcher (test.support 中的類別):       test support --- Python 測試套件的工具.
                                                             (line  775)
* matches() (test.support.Matcher 的方法): test support --- Python 測試套件的工具.
                                                             (line  777)
* MatchMapping (ast 中的類別):           模式匹配 pattern matching.
                                                             (line  176)
* MatchOr (ast 中的類別):                模式匹配 pattern matching.
                                                             (line  314)
* MatchSequence (ast 中的類別):          模式匹配 pattern matching.
                                                             (line  109)
* MatchSingleton (ast 中的類別):         模式匹配 pattern matching.
                                                             (line   85)
* MatchStar (ast 中的類別):              模式匹配 pattern matching.
                                                             (line  138)
* MatchValue (ast 中的類別):             模式匹配 pattern matching.
                                                             (line   60)
* matmul() (於 operator 模組中):         operator --- 標準運算子替代函式.
                                                             (line  115)
* MatMult (ast 中的類別):                運算式<2>.          (line   52)
* matrix multiplication（矩陣乘法）:     Binary arithmetic operations.
                                                             (line   26)
* max (datetime.date 的屬性):            date 物件.          (line  105)
* max (datetime.datetime 的屬性):        datetime 物件.      (line  286)
* max (datetime.time 的屬性):            time 物件.          (line   37)
* max (datetime.timedelta 的屬性):       timedelta 物件.     (line   78)
* max (sys.float_info 的屬性):           sys --- 系統特定的參數與函式.
                                                             (line  629)
* max_10_exp (sys.float_info 的屬性):    sys --- 系統特定的參數與函式.
                                                             (line  638)
* max_count (email.headerregistry.BaseHeader 的屬性): email headerregistry：自訂標頭物件.
                                                             (line   60)
* MAX_EMAX (於 decimal 模組中):          常數<4>.            (line   16)
* max_exp (sys.float_info 的屬性):       sys --- 系統特定的參數與函式.
                                                             (line  633)
* MAX_INTERPOLATION_DEPTH (於 configparser 模組中): ConfigParser 物件.
                                                             (line  337)
* max_line_length (email.policy.Policy 的屬性): email policy Policy Objects.
                                                             (line  146)
* max_lines (textwrap.TextWrapper 的屬性): textwrap --- 文字包裝與填充.
                                                             (line  269)
* max_mag() (decimal.Context 的方法):    Context objects.    (line  390)
* max_mag() (decimal.Decimal 的方法):    Decimal objects.    (line  381)
* max_memuse (於 test.support 模組中):   test support --- Python 測試套件的工具.
                                                             (line  143)
* MAX_PREC (於 decimal 模組中):          常數<4>.            (line   13)
* max_prefixlen (ipaddress.IPv4Address 的屬性): Address objects.
                                                             (line   49)
* max_prefixlen (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line   65)
* max_prefixlen (ipaddress.IPv6Address 的屬性): Address objects.
                                                             (line  262)
* max_prefixlen (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  295)
* MAX_Py_ssize_t (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  139)
* max() (decimal.Context 的方法):        Context objects.    (line  386)
* max() (decimal.Decimal 的方法):        Decimal objects.    (line  374)
* maxarray (reprlib.Repr 的屬性):        Repr 物件.          (line   22)
* maxdeque (reprlib.Repr 的屬性):        Repr 物件.          (line   22)
* maxdict (reprlib.Repr 的屬性):         Repr 物件.          (line   22)
* maxDiff (unittest.TestCase 的屬性):    Test cases.         (line  710)
* maxfrozenset (reprlib.Repr 的屬性):    Repr 物件.          (line   22)
* MAXIMUM_SUPPORTED (ssl.TLSVersion 的屬性): 常數<8>.        (line  503)
* maximum_version (ssl.SSLContext 的屬性): SSL Contexts.     (line  542)
* maxlen (collections.deque 的屬性):     deque 物件.         (line  109)
* maxlevel (reprlib.Repr 的屬性):        Repr 物件.          (line   17)
* maxlist (reprlib.Repr 的屬性):         Repr 物件.          (line   22)
* maxlong (reprlib.Repr 的屬性):         Repr 物件.          (line   34)
* maxother (reprlib.Repr 的屬性):        Repr 物件.          (line   47)
* maxset (reprlib.Repr 的屬性):          Repr 物件.          (line   22)
* maxsize (asyncio.Queue 的屬性):        Queue.              (line   21)
* maxsize (於 sys 模組中):               sys --- 系統特定的參數與函式.
                                                             (line 1208)
* maxstring (reprlib.Repr 的屬性):       Repr 物件.          (line   39)
* maxtuple (reprlib.Repr 的屬性):        Repr 物件.          (line   22)
* maxunicode (於 sys 模組中):            sys --- 系統特定的參數與函式.
                                                             (line 1214)
* MAXYEAR (於 datetime 模組中):          常數.               (line   13)
* MAY (於 calendar 模組中):              calendar --- 日曆相關函式.
                                                             (line  365)
* MB_ICONASTERISK (於 winsound 模組中):  winsound --- Windows 的聲音播放介面.
                                                             (line  128)
* MB_ICONEXCLAMATION (於 winsound 模組中): winsound --- Windows 的聲音播放介面.
                                                             (line  132)
* MB_ICONHAND (於 winsound 模組中):      winsound --- Windows 的聲音播放介面.
                                                             (line  136)
* MB_ICONQUESTION (於 winsound 模組中):  winsound --- Windows 的聲音播放介面.
                                                             (line  140)
* MB_OK (於 winsound 模組中):            winsound --- Windows 的聲音播放介面.
                                                             (line  144)
* mbox (mailbox 中的類別):               mbox 物件.          (line    6)
* mboxMessage (mailbox 中的類別):        mboxMessage 物件.   (line    6)
* md5() (於 hashlib 模組中):             建構函式.           (line   19)
* mean (statistics.NormalDist 的屬性):   NormalDist 物件.    (line   19)
* mean() (於 statistics 模組中):         函式細節.           (line    9)
* measure() (tkinter.font.Font 的方法):  tkinter font --- Tkinter 字型包裝器.
                                                             (line   62)
* median (statistics.NormalDist 的屬性): NormalDist 物件.    (line   23)
* median_grouped() (於 statistics 模組中): 函式細節.         (line  250)
* median_high() (於 statistics 模組中):  函式細節.           (line  234)
* median_low() (於 statistics 模組中):   函式細節.           (line  218)
* median() (於 statistics 模組中):       函式細節.           (line  194)
* member() (於 enum 模組中):             通用項目與裝飾器.   (line   72)
* MemberDescriptorType (於 types 模組中): Standard Interpreter Types.
                                                             (line  251)
* membership（成員）;test（測試）:       Membership test operations.
                                                             (line   36)
* memfd_create() (於 os 模組中):         Files and Directories.
                                                             (line 1783)
* memmove() (於 ctypes 模組中):          Utility functions.  (line  134)
* MemoryBIO (ssl 中的類別):              Memory BIO Support<2>.
                                                             (line  134)
* MemoryError:                           實體例外.           (line   89)
* MemoryHandler (logging.handlers 中的類別): MemoryHandler.  (line   41)
* memoryview (內建類別):                 Memory Views.       (line   10)
* memset() (於 ctypes 模組中):           Utility functions.  (line  140)
* merge() (於 heapq 模組中):             heapq --- 堆積佇列 heap queue 演算法.
                                                             (line   69)
* message (BaseExceptionGroup 的屬性):   例外群組.           (line   28)
* Message (email.message 中的類別):      email message Message Representing an email message using the compat32 API.
                                                             (line   49)
* Message (mailbox 中的類別):            Message 物件.       (line    6)
* Message (tkinter.messagebox 中的類別): tkinter messagebox --- Tkinter 訊息提示.
                                                             (line   20)
* message digest（訊息摘要）、MD5:       hashlib --- 安全雜湊與訊息摘要.
                                                             (line    8)
* message_factory (email.policy.Policy 的屬性): email policy Policy Objects.
                                                             (line  196)
* message_from_binary_file() (於 email 模組中): Parser API.  (line  128)
* message_from_bytes() (於 email 模組中): Parser API.        (line  115)
* message_from_file() (於 email 模組中): Parser API.         (line  151)
* message_from_string() (於 email 模組中): Parser API.       (line  141)
* MessageBeep() (於 winsound 模組中):    winsound --- Windows 的聲音播放介面.
                                                             (line   31)
* MessageClass (http.server.BaseHTTPRequestHandler 的屬性): http server — HTTP 伺服器.
                                                             (line  173)
* MessageDefect:                         email errors：例外和缺陷類別.
                                                             (line   62)
* MessageError:                          email errors：例外和缺陷類別.
                                                             (line   13)
* MessageParseError:                     email errors：例外和缺陷類別.
                                                             (line   19)
* messages (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line   22)
* meta hooks:                            Import hooks.       (line    6)
* meta path finder（元路徑尋檢器）:      術語表.             (line  784)
* meta_path (於 sys 模組中):             sys --- 系統特定的參數與函式.
                                                             (line 1224)
* meta() (於 curses 模組中):             函式<5>.            (line  287)
* metaclass hint（元類別提示）:          Determining the appropriate metaclass.
                                                             (line    6)
* metaclass（元類別）:                   Metaclasses.        (line    6)
* metaclass（元類別） <1>:               術語表.             (line  793)
* MetaPathFinder (importlib.abc 中的類別): importlib abc -- Abstract base classes related to import.
                                                             (line   27)
* metavar (optparse.Option 的屬性):      Option attributes.  (line   88)
* MetavarTypeHelpFormatter (argparse 中的類別): formatter_class.
                                                             (line   10)
* METH_CLASS (C macro):                  實作函式與方法.     (line  195)
* METH_COEXIST (C macro):                實作函式與方法.     (line  212)
* METH_FASTCALL (C macro):               實作函式與方法.     (line  124)
* METH_KEYWORDS (C macro):               實作函式與方法.     (line  108)
* METH_METHOD (C macro):                 實作函式與方法.     (line  151)
* METH_NOARGS (C macro):                 實作函式與方法.     (line  169)
* METH_O (C macro):                      實作函式與方法.     (line  182)
* METH_STATIC (C macro):                 實作函式與方法.     (line  202)
* METH_VARARGS (C macro):                實作函式與方法.     (line   98)
* method (urllib.request.Request 的屬性): Request Objects.   (line   52)
* method resolution order（方法解析順序）: 術語表.           (line  812)
* method_calls (unittest.mock.Mock 的屬性): Mock 類別.       (line  442)
* method（方法）:                        術語表.             (line  805)
* method（方法）;call（呼叫）:           Calls.              (line  140)
* methodcaller() (於 operator 模組中):   operator --- 標準運算子替代函式.
                                                             (line  301)
* MethodDescriptorType (於 types 模組中): Standard Interpreter Types.
                                                             (line  108)
* methodHelp() (xmlrpc.client.ServerProxy.system 的方法): ServerProxy 物件.
                                                             (line   43)
* methods (pyclbr.Class 的屬性):         Class Objects.      (line   50)
* methodSignature() (xmlrpc.client.ServerProxy.system 的方法): ServerProxy 物件.
                                                             (line   22)
* MethodType (於 types 模組中):          Standard Interpreter Types.
                                                             (line   76)
* MethodType（types 模組中）:            函式物件 Function Objects.
                                                             (line   14)
* MethodType（types 模組中） <1>:        方法物件 Method Objects.
                                                             (line   11)
* MethodType（types 模組中） <2>:        模組物件.           (line    7)
* MethodWrapperType (於 types 模組中):   Standard Interpreter Types.
                                                             (line   95)
* metrics() (tkinter.font.Font 的方法):  tkinter font --- Tkinter 字型包裝器.
                                                             (line   67)
* MFD_ALLOW_SEALING (於 os 模組中):      Files and Directories.
                                                             (line 1801)
* MFD_CLOEXEC (於 os 模組中):            Files and Directories.
                                                             (line 1801)
* MFD_HUGE_16GB (於 os 模組中):          Files and Directories.
                                                             (line 1801)
* MFD_HUGE_16MB (於 os 模組中):          Files and Directories.
                                                             (line 1801)
* MFD_HUGE_1GB (於 os 模組中):           Files and Directories.
                                                             (line 1801)
* MFD_HUGE_1MB (於 os 模組中):           Files and Directories.
                                                             (line 1801)
* MFD_HUGE_256MB (於 os 模組中):         Files and Directories.
                                                             (line 1801)
* MFD_HUGE_2GB (於 os 模組中):           Files and Directories.
                                                             (line 1801)
* MFD_HUGE_2MB (於 os 模組中):           Files and Directories.
                                                             (line 1801)
* MFD_HUGE_32MB (於 os 模組中):          Files and Directories.
                                                             (line 1801)
* MFD_HUGE_512KB (於 os 模組中):         Files and Directories.
                                                             (line 1801)
* MFD_HUGE_512MB (於 os 模組中):         Files and Directories.
                                                             (line 1801)
* MFD_HUGE_64KB (於 os 模組中):          Files and Directories.
                                                             (line 1801)
* MFD_HUGE_8MB (於 os 模組中):           Files and Directories.
                                                             (line 1801)
* MFD_HUGE_MASK (於 os 模組中):          Files and Directories.
                                                             (line 1801)
* MFD_HUGE_SHIFT (於 os 模組中):         Files and Directories.
                                                             (line 1801)
* MFD_HUGETLB (於 os 模組中):            Files and Directories.
                                                             (line 1801)
* MH (mailbox 中的類別):                 MH 物件.            (line    6)
* MHMessage (mailbox 中的類別):          MHMessage 物件.     (line    6)
* microsecond (datetime.datetime 的屬性): datetime 物件.     (line  323)
* microsecond (datetime.time 的屬性):    time 物件.          (line   62)
* microseconds (datetime.timedelta 的屬性): timedelta 物件.  (line  103)
* MIME;base64 encoding（base64 編碼）:   base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line    8)
* MIME;content type（內容類型）:         mimetypes --- 將檔案名稱對映到 MIME 類型.
                                                             (line    8)
* MIME;headers（標頭）:                  mimetypes --- 將檔案名稱對映到 MIME 類型.
                                                             (line   26)
* MIME;headers（標頭） <1>:              mimetypes --- 將檔案名稱對映到 MIME 類型.
                                                             (line   56)
* MIME;quoted-printable encoding（可列印字元編碼）: quopri --- 編碼和解碼 MIME 可列印字元資料.
                                                             (line    8)
* MIMEApplication (email.mime.application 中的類別): email mime：從頭開始建立電子郵件和 MIME 物件.
                                                             (line   95)
* MIMEAudio (email.mime.audio 中的類別): email mime：從頭開始建立電子郵件和 MIME 物件.
                                                             (line  125)
* MIMEBase (email.mime.base 中的類別):   email mime：從頭開始建立電子郵件和 MIME 物件.
                                                             (line   30)
* MIMEImage (email.mime.image 中的類別): email mime：從頭開始建立電子郵件和 MIME 物件.
                                                             (line  157)
* MIMEMessage (email.mime.message 中的類別): email mime：從頭開始建立電子郵件和 MIME 物件.
                                                             (line  190)
* MIMEMultipart (email.mime.multipart 中的類別): email mime：從頭開始建立電子郵件和 MIME 物件.
                                                             (line   66)
* MIMENonMultipart (email.mime.nonmultipart 中的類別): email mime：從頭開始建立電子郵件和 MIME 物件.
                                                             (line   55)
* MIMEPart (email.message 中的類別):     email message：表示電子郵件訊息.
                                                             (line  715)
* MIMEText (email.mime.text 中的類別):   email mime：從頭開始建立電子郵件和 MIME 物件.
                                                             (line  208)
* MimeTypes (mimetypes 中的類別):        MimeTypes 物件.     (line   10)
* MIMEVersionHeader (email.headerregistry 中的類別): email headerregistry：自訂標頭物件.
                                                             (line  234)
* min (datetime.date 的屬性):            date 物件.          (line  101)
* min (datetime.datetime 的屬性):        datetime 物件.      (line  281)
* min (datetime.time 的屬性):            time 物件.          (line   33)
* min (datetime.timedelta 的屬性):       timedelta 物件.     (line   73)
* min (sys.float_info 的屬性):           sys --- 系統特定的參數與函式.
                                                             (line  643)
* min_10_exp (sys.float_info 的屬性):    sys --- 系統特定的參數與函式.
                                                             (line  656)
* MIN_EMIN (於 decimal 模組中):          常數<4>.            (line   19)
* MIN_ETINY (於 decimal 模組中):         常數<4>.            (line   22)
* min_exp (sys.float_info 的屬性):       sys --- 系統特定的參數與函式.
                                                             (line  651)
* min_mag() (decimal.Context 的方法):    Context objects.    (line  398)
* min_mag() (decimal.Decimal 的方法):    Decimal objects.    (line  393)
* min() (decimal.Context 的方法):        Context objects.    (line  394)
* min() (decimal.Decimal 的方法):        Decimal objects.    (line  386)
* MINEQUAL (於 token 模組中):            token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  174)
* MINIMUM_SUPPORTED (ssl.TLSVersion 的屬性): 常數<8>.        (line  501)
* minimum_version (ssl.SSLContext 的屬性): SSL Contexts.     (line  560)
* minor (email.headerregistry.MIMEVersionHeader 的屬性): email headerregistry：自訂標頭物件.
                                                             (line  251)
* minor() (於 os 模組中):                Files and Directories.
                                                             (line  617)
* MINUS (於 token 模組中):               token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   86)
* minus() (decimal.Context 的方法):      Context objects.    (line  402)
* minus（減）:                           Unary arithmetic and bitwise operations.
                                                             (line   10)
* minute (datetime.datetime 的屬性):     datetime 物件.      (line  315)
* minute (datetime.time 的屬性):         time 物件.          (line   54)
* MINYEAR (於 datetime 模組中):          常數.               (line    8)
* mirrored() (於 unicodedata 模組中):    unicodedata --- Unicode 資料庫.
                                                             (line   69)
* misc_header (cmd.Cmd 的屬性):          Cmd 物件.           (line  160)
* MISSING (contextvars.Token 的屬性):    Context Variables.  (line   94)
* MISSING (於 dataclasses 模組中):       模組內容<8>.        (line  466)
* MISSING (於 sys.monitoring 模組中):    回呼函式引數.       (line    6)
* MISSING_C_DOCSTRINGS (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  153)
* missing_compiler_executable() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  665)
* MissingSectionHeaderError:             例外<5>.            (line   60)
* mkd() (ftplib.FTP 的方法):             FTP 物件.           (line  297)
* mkdir() (pathlib.Path 的方法):         建立檔案與目錄.     (line   19)
* mkdir() (zipfile.ZipFile 的方法):      ZipFile 物件.       (line  334)
* mkdir() (於 os 模組中):                Files and Directories.
                                                             (line  500)
* mkdtemp() (於 tempfile 模組中):        tempfile --- 生成臨時檔案和目錄.
                                                             (line  243)
* mkfifo() (於 os 模組中):               Files and Directories.
                                                             (line  571)
* mknod() (於 os 模組中):                Files and Directories.
                                                             (line  592)
* mkstemp() (於 tempfile 模組中):        tempfile --- 生成臨時檔案和目錄.
                                                             (line  194)
* mktemp() (於 tempfile 模組中):         已棄用的函式和變數. (line   12)
* mktime_tz() (於 email.utils 模組中):   email utils：雜項工具.
                                                             (line  146)
* mktime() (於 time 模組中):             函式<4>.            (line  143)
* mlsd() (ftplib.FTP 的方法):            FTP 物件.           (line  250)
* mmap (mmap 中的類別):                  mmap --- 記憶體映射檔案的支援.
                                                             (line   54)
* MMDF (mailbox 中的類別):               MMDF 物件.          (line    6)
* MMDFMessage (mailbox 中的類別):        MMDFMessage 物件.   (line    6)
* Mock (unittest.mock 中的類別):         Mock 類別.          (line   20)
* mock_add_spec() (unittest.mock.Mock 的方法): Mock 類別.    (line  206)
* mock_calls (unittest.mock.Mock 的屬性): Mock 類別.         (line  459)
* mock_open() (於 unittest.mock 模組中): mock_open.          (line    6)
* Mod (ast 中的類別):                    運算式<2>.          (line   52)
* mod() (於 operator 模組中):            operator --- 標準運算子替代函式.
                                                             (line  105)
* mode (bz2.BZ2File 的屬性):             De compression of files.
                                                             (line  129)
* mode (gzip.GzipFile 的屬性):           gzip --- gzip 檔案的支援.
                                                             (line  143)
* mode (io.FileIO 的屬性):               原始檔案 I/O.       (line   55)
* mode (lzma.LZMAFile 的屬性):           Reading and writing compressed files.
                                                             (line   98)
* mode (statistics.NormalDist 的屬性):   NormalDist 物件.    (line   27)
* mode (tarfile.TarInfo 的屬性):         TarInfo 物件.       (line   78)
* mode() (於 statistics 模組中):         函式細節.           (line  299)
* mode() (於 turtle 模組中):             Settings and special methods.
                                                             (line    6)
* modf() (於 math 模組中):               數論與表現函式.     (line  173)
* modified() (urllib.robotparser.RobotFileParser 的方法): urllib robotparser --- robots txt 的剖析器.
                                                             (line   42)
* modify() (select.devpoll 的方法):      /dev/poll Polling Objects.
                                                             (line   49)
* modify() (select.epoll 的方法):        Edge and Level Trigger Polling epoll Objects.
                                                             (line   85)
* modify() (select.poll 的方法):         Polling Objects.    (line   60)
* modify() (selectors.BaseSelector 的方法): Classes<3>.      (line   94)
* Module (ast 中的類別):                 根節點.             (line    6)
* module (pyclbr.Class 的屬性):          Class Objects.      (line   16)
* module (pyclbr.Function 的屬性):       函式物件.           (line   15)
* MODULE (symtable.SymbolTableType 的屬性): 檢查符號表.      (line   11)
* Module browser（模組瀏覽器）:          File menu Shell and Editor.
                                                             (line   22)
* module spec:                           Finders and loaders.
                                                             (line    6)
* module spec（模組規格）:               術語表.             (line  826)
* module_from_spec() (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line  121)
* module; __future__:                    __future__ --- Future 陳述式定義.
                                                             (line    6)
* module; __main__:                      __main__ --- 頂層程式碼環境.
                                                             (line    6)
* module; _thread:                       _thread --- 低階執行緒 API.
                                                             (line    6)
* module; _tkinter:                      Tkinter Modules.    (line  150)
* module; abc:                           abc --- 抽象基底類別.
                                                             (line    6)
* module; argparse:                      argparse --- Parser for command-line options arguments and sub-commands.
                                                             (line    6)
* module; array:                         array --- 高效率的數值型陣列.
                                                             (line    6)
* module; ast:                           ast --- 抽象語法樹 Abstract Syntax Trees.
                                                             (line    6)
* module; asyncio:                       asyncio --- 非同步 I/O.
                                                             (line    6)
* module; atexit:                        atexit --- 退出處理函式.
                                                             (line    6)
* module; base64:                        base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line    6)
* module; bdb:                           bdb --- 偵錯器框架. (line    6)
* module; binascii:                      binascii --- 在二進位制和 ASCII 之間轉換.
                                                             (line    6)
* module; bisect:                        bisect --- 陣列二分演算法 Array bisection algorithm.
                                                             (line    6)
* module; builtins:                      builtins --- 內建物件.
                                                             (line    6)
* module; bz2:                           bz2 --- bzip2 壓縮的支援.
                                                             (line    6)
* module; calendar:                      calendar --- 日曆相關函式.
                                                             (line    6)
* module; cmath:                         cmath --- 複數的數學函式.
                                                             (line    6)
* module; cmd:                           cmd --- 以列為導向的指令直譯器支援.
                                                             (line    6)
* module; code:                          code --- 直譯器基底類別.
                                                             (line    6)
* module; codecs:                        codecs --- 編解碼器註冊表和基底類別.
                                                             (line    6)
* module; codeop:                        codeop --- 編譯 Python 程式碼.
                                                             (line    6)
* module; collections:                   collections --- 容器資料型態.
                                                             (line    6)
* module; collections.abc:               collections abc --- 容器的抽象基底類別.
                                                             (line    6)
* module; colorsys:                      colorsys --- 顏色系統間的轉換.
                                                             (line    6)
* module; compileall:                    compileall --- 位元組編譯 Python 函式庫.
                                                             (line    6)
* module; concurrent.futures:            concurrent futures --- 啟動平行任務.
                                                             (line    6)
* module; configparser:                  configparser --- 設定檔剖析器.
                                                             (line    6)
* module; contextlib:                    contextlib --- Utilities for with-statement contexts.
                                                             (line    6)
* module; contextvars:                   contextvars --- 情境變數.
                                                             (line    6)
* module; copy:                          copy --- 淺層 shallow 和深層 deep 複製操作.
                                                             (line    6)
* module; copyreg:                       copyreg --- 註冊 pickle 支援函式.
                                                             (line    6)
* module; cProfile:                      profile and cProfile Module Reference.
                                                             (line    6)
* module; csv:                           csv --- CSV 檔案讀取及寫入.
                                                             (line    6)
* module; ctypes:                        ctypes --- 用於 Python 的外部函式庫.
                                                             (line    6)
* module; curses:                        curses --- 字元儲存格顯示的終端處理.
                                                             (line    6)
* module; curses.ascii:                  curses ascii --- ASCII 字元的工具程式.
                                                             (line    6)
* module; curses.panel:                  curses panel --- curses 的面板堆疊擴充.
                                                             (line    6)
* module; curses.textpad:                curses textpad --- Text input widget for curses programs.
                                                             (line    6)
* module; dataclasses:                   dataclasses --- Data Classes.
                                                             (line    6)
* module; datetime:                      datetime --- 日期與時間的基本型別.
                                                             (line    6)
* module; dbm:                           dbm --- Unix "databases" 的介面.
                                                             (line    6)
* module; dbm.dumb:                      dbm dumb --- 可攜式 DBM 實作.
                                                             (line    6)
* module; dbm.gnu:                       dbm gnu --- GNU 資料庫管理器.
                                                             (line    6)
* module; dbm.ndbm:                      dbm ndbm --- 新資料庫管理器.
                                                             (line    6)
* module; dbm.sqlite3:                   dbm sqlite3 --- SQLite backend for dbm.
                                                             (line    6)
* module; decimal:                       decimal --- 十進位固定點和浮點運算.
                                                             (line    6)
* module; difflib:                       difflib --- 計算差異的輔助工具.
                                                             (line    6)
* module; dis:                           dis --- Python bytecode 的反組譯器.
                                                             (line    6)
* module; doctest:                       doctest --- 測試互動式 Python 範例.
                                                             (line    6)
* module; email:                         email --- 郵件和 MIME 處理套件.
                                                             (line    6)
* module; email.charset:                 email charset：表示字元集合.
                                                             (line    6)
* module; email.contentmanager:          email contentmanager：管理 MIME 內容.
                                                             (line    6)
* module; email.encoders:                email encoders：編碼器.
                                                             (line    6)
* module; email.errors:                  email errors：例外和缺陷類別.
                                                             (line    6)
* module; email.generator:               email generator：產生 MIME 文件.
                                                             (line    6)
* module; email.header:                  email header：國際化標頭.
                                                             (line    6)
* module; email.headerregistry:          email headerregistry：自訂標頭物件.
                                                             (line    6)
* module; email.iterators:               email iterators：疊代器.
                                                             (line    6)
* module; email.message:                 email message：表示電子郵件訊息.
                                                             (line    6)
* module; email.mime:                    email mime：從頭開始建立電子郵件和 MIME 物件.
                                                             (line    6)
* module; email.mime.application:        email mime：從頭開始建立電子郵件和 MIME 物件.
                                                             (line   95)
* module; email.mime.audio:              email mime：從頭開始建立電子郵件和 MIME 物件.
                                                             (line  125)
* module; email.mime.base:               email mime：從頭開始建立電子郵件和 MIME 物件.
                                                             (line   30)
* module; email.mime.image:              email mime：從頭開始建立電子郵件和 MIME 物件.
                                                             (line  157)
* module; email.mime.message:            email mime：從頭開始建立電子郵件和 MIME 物件.
                                                             (line  190)
* module; email.mime.multipart:          email mime：從頭開始建立電子郵件和 MIME 物件.
                                                             (line   66)
* module; email.mime.nonmultipart:       email mime：從頭開始建立電子郵件和 MIME 物件.
                                                             (line   55)
* module; email.mime.text:               email mime：從頭開始建立電子郵件和 MIME 物件.
                                                             (line  208)
* module; email.parser:                  email parser：剖析電子郵件訊息.
                                                             (line    6)
* module; email.policy:                  email policy Policy Objects.
                                                             (line    6)
* module; email.utils:                   email utils：雜項工具.
                                                             (line    6)
* module; encodings.idna:                encodings idna --- Internationalized Domain Names in Applications.
                                                             (line    6)
* module; encodings.mbcs:                encodings mbcs --- Windows ANSI codepage.
                                                             (line    6)
* module; encodings.utf_8_sig:           encodings utf_8_sig --- UTF-8 codec with BOM signature.
                                                             (line    6)
* module; ensurepip:                     ensurepip --- pip 安裝器的初始建置 bootstrapping.
                                                             (line    6)
* module; enum:                          enum --- 對列舉的支援.
                                                             (line    6)
* module; errno:                         errno --- 標準 errno 系統符號.
                                                             (line    6)
* module; faulthandler:                  faulthandler --- 傾印 Python 回溯.
                                                             (line    6)
* module; fcntl:                         fcntl --- fcntl 和 ioctl 系統呼叫.
                                                             (line    6)
* module; filecmp:                       filecmp --- 檔案與目錄比較.
                                                             (line    6)
* module; fileinput:                     fileinput --- 逐列疊代多個輸入串流.
                                                             (line    6)
* module; fnmatch:                       fnmatch --- Unix 檔案名稱模式比對.
                                                             (line    6)
* module; fractions:                     fractions --- 有理數.
                                                             (line    6)
* module; ftplib:                        ftplib --- FTP 協定用戶端.
                                                             (line    6)
* module; functools:                     functools --- 可呼叫物件上的高階函式與操作.
                                                             (line    6)
* module; gc:                            gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line    6)
* module; getopt:                        getopt --- 用於命令列選項的 C 風格剖析器.
                                                             (line    6)
* module; getpass:                       getpass --- 可攜式密碼輸入工具.
                                                             (line    6)
* module; gettext:                       gettext --- 多語言國際化服務.
                                                             (line    6)
* module; glob:                          glob --- Unix 風格的路徑名稱模式擴展.
                                                             (line    6)
* module; graphlib:                      graphlib —-- 使用類圖 graph-like 結構進行操作的功能.
                                                             (line    6)
* module; grp:                           grp --- 群組資料庫. (line    6)
* module; gzip:                          gzip --- gzip 檔案的支援.
                                                             (line    6)
* module; hashlib:                       hashlib --- 安全雜湊與訊息摘要.
                                                             (line    6)
* module; heapq:                         heapq --- 堆積佇列 heap queue 演算法.
                                                             (line    6)
* module; hmac:                          hmac --- 基於金鑰雜湊的訊息驗證.
                                                             (line    6)
* module; html:                          html --- 超連結標記語言 HTML 支援.
                                                             (line    6)
* module; html.entities:                 html entities --- HTML 一般實體的定義.
                                                             (line    6)
* module; html.parser:                   html parser --- 簡單的 HTML 和 XHTML 剖析器.
                                                             (line    6)
* module; http:                          http --- HTTP 模組. (line    6)
* module; http.client:                   http client --- HTTP 協定用戶端.
                                                             (line    6)
* module; http.cookiejar:                http cookiejar --- HTTP 客戶端的 Cookie 處理.
                                                             (line    6)
* module; http.cookies:                  http cookies --- HTTP 狀態管理.
                                                             (line    6)
* module; http.server:                   http server — HTTP 伺服器.
                                                             (line    6)
* module; idlelib:                       idlelib.            (line    6)
* module; imaplib:                       imaplib --- IMAP4 協定客戶端.
                                                             (line    6)
* module; importlib:                     importlib --- import 的實作.
                                                             (line    6)
* module; importlib.abc:                 importlib abc -- Abstract base classes related to import.
                                                             (line    6)
* module; importlib.machinery:           importlib machinery -- Importers and path hooks.
                                                             (line    6)
* module; importlib.metadata:            importlib metadata -- 存取套件的元資料.
                                                             (line    6)
* module; importlib.resources:           importlib resources -- Package resource reading opening and access.
                                                             (line    6)
* module; importlib.resources.abc:       importlib resources abc -- 資源的抽象基底類別.
                                                             (line    6)
* module; importlib.util:                importlib util -- Utility code for importers.
                                                             (line    6)
* module; inspect:                       inspect --- 檢視活動物件.
                                                             (line    6)
* module; io:                            io — 處理資料串流的核心工具.
                                                             (line    6)
* module; ipaddress:                     ipaddress --- IPv4/IPv6 操作函式庫.
                                                             (line    6)
* module; itertools:                     itertools --- 建立產生高效率迴圈之疊代器的函式.
                                                             (line    6)
* module; json:                          json --- JSON 編碼器與解碼器.
                                                             (line    6)
* module; json.tool:                     命令列介面<3>.      (line    6)
* module; keyword:                       keyword --- 檢驗 Python 關鍵字.
                                                             (line    6)
* module; linecache:                     linecache --- 隨機存取文字列.
                                                             (line    6)
* module; locale:                        locale --- 國際化服務.
                                                             (line    6)
* module; logging:                       logging --- Python 的日誌記錄工具.
                                                             (line    6)
* module; logging.config:                logging config --- 日誌記錄配置.
                                                             (line    6)
* module; logging.handlers:              logging handlers --- 日誌紀錄處理器.
                                                             (line    6)
* module; lzma:                          lzma --- 使用 LZMA 演算法進行壓縮.
                                                             (line    6)
* module; mailbox:                       mailbox --- 以各種格式操作郵件信箱.
                                                             (line    6)
* module; marshal:                       marshal --- 内部 Python 物件序列化.
                                                             (line    6)
* module; math:                          math --- 數學函式.  (line    6)
* module; mimetypes:                     mimetypes --- 將檔案名稱對映到 MIME 類型.
                                                             (line    6)
* module; mmap:                          mmap --- 記憶體映射檔案的支援.
                                                             (line    6)
* module; modulefinder:                  modulefinder --- 搜尋腳本所使用的模組.
                                                             (line    6)
* module; msvcrt:                        msvcrt --- MS VC++ runtime 提供的有用例程.
                                                             (line    6)
* module; multiprocessing:               multiprocessing --- 以行程為基礎的平行性.
                                                             (line    6)
* module; multiprocessing.connection:    Listeners and Clients.
                                                             (line    6)
* module; multiprocessing.dummy:         multiprocessing dummy 模組.
                                                             (line    6)
* module; multiprocessing.managers:      Managers.           (line   19)
* module; multiprocessing.pool:          Process Pools.      (line    6)
* module; multiprocessing.shared_memory: multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取.
                                                             (line    6)
* module; multiprocessing.sharedctypes:  multiprocessing sharedctypes 模組.
                                                             (line    6)
* module; netrc:                         netrc --- netrc 檔案處理.
                                                             (line    6)
* module; numbers:                       numbers --- 數值的抽象基底類別.
                                                             (line    6)
* module; operator:                      operator --- 標準運算子替代函式.
                                                             (line    6)
* module; optparse:                      optparse --- 命令列選項剖析器.
                                                             (line    6)
* module; os:                            os --- 各種作業系統介面.
                                                             (line    6)
* module; os.path:                       os path --- 常見的路徑名操作.
                                                             (line    6)
* module; pathlib:                       pathlib --- 物件導向檔案系統路徑.
                                                             (line    6)
* module; pdb:                           pdb --- The Python Debugger.
                                                             (line    6)
* module; pickle:                        pickle --- Python 物件序列化.
                                                             (line    6)
* module; pickletools:                   pickletools --- pickle 開發者的工具.
                                                             (line    6)
* module; pkgutil:                       pkgutil --- 套件擴充工具程式.
                                                             (line    6)
* module; platform:                      platform --- 對底層平臺識別資料的存取.
                                                             (line    6)
* module; plistlib:                      plistlib --- 產生和剖析 Apple plist 檔案.
                                                             (line    6)
* module; poplib:                        poplib --- POP3 協定用戶端.
                                                             (line    6)
* module; posix:                         posix --- 最常見的 POSIX 系統呼叫.
                                                             (line    6)
* module; pprint:                        pprint --- 資料美化列印器.
                                                             (line    6)
* module; profile:                       profile and cProfile Module Reference.
                                                             (line    6)
* module; pstats:                        The Stats Class.    (line    9)
* module; pty:                           pty --- 偽終端工具. (line    6)
* module; pwd:                           pwd --- 密碼資料庫. (line    6)
* module; py_compile:                    py_compile — 編譯 Python 來源檔案.
                                                             (line    6)
* module; pyclbr:                        pyclbr --- Python 模組瀏覽器支援.
                                                             (line    6)
* module; pydoc:                         pydoc --- 文件產生器與線上幫助系統.
                                                             (line    6)
* module; queue:                         queue --- 同步佇列 synchronized queue 類別.
                                                             (line    6)
* module; quopri:                        quopri --- 編碼和解碼 MIME 可列印字元資料.
                                                             (line    6)
* module; random:                        random --- 生成偽隨機數.
                                                             (line    6)
* module; re:                            re --- 正規表示式 regular expression 操作.
                                                             (line    6)
* module; readline:                      readline --- GNU readline 介面.
                                                             (line    6)
* module; reprlib:                       reprlib --- repr 的替代實作.
                                                             (line    6)
* module; resource:                      resource --- 資源使用資訊.
                                                             (line    6)
* module; rlcompleter:                   rlcompleter --- GNU readline 的補全函式.
                                                             (line    6)
* module; runpy:                         runpy --- 定位並執行 Python 模組.
                                                             (line    6)
* module; sched:                         sched --- 事件排程器.
                                                             (line    6)
* module; secrets:                       secrets --- 產生用於管理機密的安全亂數.
                                                             (line    6)
* module; select:                        select --- 等待 I/O 完成.
                                                             (line    6)
* module; selectors:                     selectors --- 高階 I/O 多工.
                                                             (line    6)
* module; shelve:                        shelve --- Python object persistence.
                                                             (line    6)
* module; shlex:                         shlex --- 簡單的語法分析.
                                                             (line    6)
* module; shutil:                        shutil — 高階檔案操作.
                                                             (line    6)
* module; signal:                        signal --- 設定非同步事件的處理函式.
                                                             (line    6)
* module; site:                          site --- Site-specific configuration hook.
                                                             (line    6)
* module; sitecustomize:                 sitecustomize.      (line    6)
* module; smtplib:                       smtplib --- SMTP 協定用戶端.
                                                             (line    6)
* module; socket:                        socket --- 低階網路介面.
                                                             (line    6)
* module; socketserver:                  socketserver --- 用於網路伺服器的框架.
                                                             (line    6)
* module; sqlite3:                       sqlite3 --- SQLite 資料庫的 DB-API 2 0 介面.
                                                             (line    6)
* module; ssl:                           ssl --- socket 物件的 TLS/SSL 包裝器.
                                                             (line    6)
* module; stat:                          stat --- 直譯 stat 的結果.
                                                             (line    6)
* module; statistics:                    statistics --- 數學統計函式.
                                                             (line    6)
* module; string:                        string --- 常見的字串操作.
                                                             (line    6)
* module; stringprep:                    stringprep --- 網際網路字串準備.
                                                             (line    6)
* module; struct:                        struct --- 將位元組直譯為打包起來的二進位資料.
                                                             (line    6)
* module; subprocess:                    subprocess --- 子行程管理.
                                                             (line    6)
* module; symtable:                      symtable --- 存取編譯器的符號表.
                                                             (line    6)
* module; sys:                           sys --- 系統特定的參數與函式.
                                                             (line    6)
* module; sys.monitoring:                sys monitoring --- Execution event monitoring.
                                                             (line    6)
* module; sysconfig:                     sysconfig --- 提供 Python 設定資訊的存取.
                                                             (line    6)
* module; syslog:                        syslog --- Unix syslog 函式庫例程.
                                                             (line    6)
* module; tabnanny:                      tabnanny --- 偵測不良縮排.
                                                             (line    6)
* module; tarfile:                       tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line    6)
* module; tempfile:                      tempfile --- 生成臨時檔案和目錄.
                                                             (line    6)
* module; termios:                       termios --- POSIX 風格 tty 控制.
                                                             (line    6)
* module; test:                          test --- Python 的回歸測試 regression tests 套件.
                                                             (line    6)
* module; test.regrtest:                 使用命令列介面執行測試.
                                                             (line    6)
* module; test.support:                  test support --- Python 測試套件的工具.
                                                             (line    6)
* module; test.support.bytecode_helper:  test support bytecode_helper --- 用於測試位元組碼能正確產生的支援工具.
                                                             (line    6)
* module; test.support.import_helper:    test support import_helper --- 用於 import 測試的工具.
                                                             (line    6)
* module; test.support.os_helper:        test support os_helper --- 用於 os 測試的工具.
                                                             (line    6)
* module; test.support.script_helper:    test support script_helper --- 用於 Python 執行測試的工具.
                                                             (line    6)
* module; test.support.socket_helper:    test support socket_helper --- 用於 socket 測試的工具.
                                                             (line    6)
* module; test.support.threading_helper: test support threading_helper --- Utilities for threading tests.
                                                             (line    6)
* module; test.support.warnings_helper:  test support warnings_helper --- 用於 warnings 測試的工具.
                                                             (line    6)
* module; textwrap:                      textwrap --- 文字包裝與填充.
                                                             (line    6)
* module; threading:                     threading --- 基於執行緒的平行性.
                                                             (line    6)
* module; time:                          time --- 時間存取與轉換.
                                                             (line    6)
* module; timeit:                        timeit --- 測量小量程式片段的執行時間.
                                                             (line    6)
* module; tkinter:                       tkinter --- Tcl/Tk 的 Python 介面.
                                                             (line    6)
* module; tkinter.colorchooser:          tkinter colorchooser --- 顏色選擇對話框.
                                                             (line    6)
* module; tkinter.commondialog:          tkinter commondialog --- Dialog window templates.
                                                             (line    6)
* module; tkinter.dnd:                   tkinter dnd --- 拖放支援.
                                                             (line    6)
* module; tkinter.filedialog:            tkinter filedialog --- File selection dialogs.
                                                             (line    6)
* module; tkinter.font:                  tkinter font --- Tkinter 字型包裝器.
                                                             (line    6)
* module; tkinter.messagebox:            tkinter messagebox --- Tkinter 訊息提示.
                                                             (line    6)
* module; tkinter.scrolledtext:          tkinter scrolledtext --- 捲動文字小工具.
                                                             (line    6)
* module; tkinter.simpledialog:          tkinter simpledialog --- 標準 Tkinter 輸入對話框.
                                                             (line    6)
* module; tkinter.ttk:                   tkinter ttk --- Tk 主題化小工具.
                                                             (line    6)
* module; token:                         token --- 與 Python 剖析樹一起使用的常數.
                                                             (line    6)
* module; tokenize:                      tokenize --- Tokenizer for Python source.
                                                             (line    6)
* module; tomllib:                       tomllib --- 剖析 TOML 檔案.
                                                             (line    6)
* module; trace:                         trace --- 追蹤或追查 Python 陳述式執行.
                                                             (line    6)
* module; traceback:                     traceback --- 列印或取得堆疊回溯 stack traceback.
                                                             (line    6)
* module; tracemalloc:                   tracemalloc --- 追蹤記憶體配置.
                                                             (line    6)
* module; tty:                           tty --- 終端機控制函式.
                                                             (line    6)
* module; turtle:                        turtle --- 龜圖學 Turtle graphics.
                                                             (line    6)
* module; turtledemo:                    turtledemo --- Demo scripts.
                                                             (line    6)
* module; types:                         types --- 動態型別建立與內建型別名稱.
                                                             (line    6)
* module; typing:                        typing --- 支援型別提示.
                                                             (line    6)
* module; unicodedata:                   unicodedata --- Unicode 資料庫.
                                                             (line    6)
* module; unittest:                      unittest --- 單元測試框架.
                                                             (line    6)
* module; unittest.mock:                 unittest mock — mock 物件函式庫.
                                                             (line    6)
* module; urllib:                        urllib --- URL 處理模組.
                                                             (line    6)
* module; urllib.error:                  urllib error --- urllib request 引發的例外類別.
                                                             (line    6)
* module; urllib.parse:                  urllib parse --- 將 URL 剖析成元件.
                                                             (line    6)
* module; urllib.request:                urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line    6)
* module; urllib.response:               urllib response --- Response classes used by urllib.
                                                             (line    6)
* module; urllib.robotparser:            urllib robotparser --- robots txt 的剖析器.
                                                             (line    6)
* module; usercustomize:                 usercustomize.      (line    6)
* module; uuid:                          uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line    8)
* module; venv:                          venv --- 建立虛擬環境.
                                                             (line    6)
* module; warnings:                      warnings --- 警告控制.
                                                             (line    6)
* module; wave:                          wave --- 讀寫 WAV 檔案.
                                                             (line    6)
* module; weakref:                       weakref --- 弱參照. (line    6)
* module; webbrowser:                    webbrowser --- 方便的網頁瀏覽器控制器.
                                                             (line    6)
* module; winreg:                        winreg --- Windows 註冊表存取.
                                                             (line    6)
* module; winsound:                      winsound --- Windows 的聲音播放介面.
                                                             (line    6)
* module; wsgiref:                       wsgiref --- WSGI 工具與參考實作.
                                                             (line    6)
* module; wsgiref.handlers:              wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line    6)
* module; wsgiref.headers:               wsgiref headers -- WSGI 回應標頭工具.
                                                             (line    6)
* module; wsgiref.simple_server:         wsgiref simple_server -- 一個簡單的 WSGI HTTP 伺服器.
                                                             (line    6)
* module; wsgiref.types:                 wsgiref types -- 用於靜態型別檢查的 WSGI 型別.
                                                             (line    6)
* module; wsgiref.util:                  wsgiref util -- WSGI 環境工具.
                                                             (line    6)
* module; wsgiref.validate:              wsgiref validate --- WSGI 符合性檢查.
                                                             (line    6)
* module; xml:                           XML 處理模組.       (line    6)
* module; xml.dom:                       xml dom --- Document 物件模型 API.
                                                             (line    6)
* module; xml.dom.minidom:               xml dom minidom --- 最小的 DOM 實作.
                                                             (line    6)
* module; xml.dom.pulldom:               xml dom pulldom --- 支援建置部分 DOM 樹.
                                                             (line    6)
* module; xml.etree.ElementInclude:      函式<9>.            (line    6)
* module; xml.etree.ElementTree:         xml etree cElementTree --- ElementTree XML API.
                                                             (line    6)
* module; xml.parsers.expat:             xml parsers expat --- 使用 Expat 進行快速 XML 剖析.
                                                             (line    6)
* module; xml.parsers.expat.errors:      Expat error constants.
                                                             (line    6)
* module; xml.parsers.expat.model:       Content Model Descriptions.
                                                             (line    6)
* module; xml.sax:                       xml sax --- SAX2 剖析器支援.
                                                             (line    6)
* module; xml.sax.handler:               xml sax handler --- SAX 處理函式的基本類別.
                                                             (line    6)
* module; xml.sax.saxutils:              xml sax saxutils --- SAX 工具程式.
                                                             (line    6)
* module; xml.sax.xmlreader:             xml sax xmlreader --- XML 剖析器的介面.
                                                             (line    6)
* module; xmlrpc.client:                 xmlrpc client --- XML-RPC 客戶端存取.
                                                             (line    6)
* module; xmlrpc.server:                 xmlrpc server --- 基本 XML-RPC 伺服器.
                                                             (line    6)
* module; zipapp:                        zipapp —-- 管理可執行的 Python zip 封存檔案.
                                                             (line    6)
* module; zipfile:                       zipfile --- 處理 ZIP 封存檔案.
                                                             (line    6)
* module; zipimport:                     zipimport --- 從 Zip 封存檔案匯入模組.
                                                             (line    6)
* module; zlib:                          zlib --- 相容於 gzip 的壓縮.
                                                             (line    6)
* module; zoneinfo:                      zoneinfo --- IANA 時區支援.
                                                             (line    6)
* module（模組）:                        術語表.             (line  818)
* module（模組）;__main__:               Resolution of names.
                                                             (line   54)
* module（模組）;__main__ <1>:           完整的 Python 程式. (line    6)
* module（模組）;__main__ <2>:           完整的 Python 程式. (line   15)
* module（模組）;__main__ <3>:           runpy --- 定位並執行 Python 模組.
                                                             (line   30)
* module（模組）;__main__ <4>:           runpy --- 定位並執行 Python 模組.
                                                             (line  100)
* module（模組）;__main__ <5>:           嵌入式Python.       (line   10)
* module（模組）;_locale:                locale --- 國際化服務.
                                                             (line   16)
* module（模組）;array（陣列）:          Mutable sequences.  (line   10)
* module（模組）;base64:                 binascii --- 在二進位制和 ASCII 之間轉換.
                                                             (line    6)
* module（模組）;bdb:                    pdb --- The Python Debugger.
                                                             (line   17)
* module（模組）;builtins（內建）:       dir 函式.           (line   45)
* module（模組）;builtins（內建） <1>:   完整的 Python 程式. (line    6)
* module（模組）;builtins（內建） <2>:   內建函式.           (line 1982)
* module（模組）;builtins（內建） <3>:   嵌入式Python.       (line   10)
* module（模組）;cmd:                    pdb --- The Python Debugger.
                                                             (line   17)
* module（模組）;collections:            Mutable sequences.  (line   11)
* module（模組）;copy（複製）:           copyreg --- 註冊 pickle 支援函式.
                                                             (line    8)
* module（模組）;dbm.gnu:                字典.               (line   25)
* module（模組）;dbm.gnu <1>:            Restrictions.       (line    6)
* module（模組）;dbm.ndbm:               字典.               (line   25)
* module（模組）;dbm.ndbm <1>:           Restrictions.       (line    6)
* module（模組）;errno:                  實體例外.           (line  126)
* module（模組）;glob:                   fnmatch --- Unix 檔案名稱模式比對.
                                                             (line   34)
* module（模組）;importing（引入）:      import 陳述式.      (line    6)
* module（模組）;io:                     I/O objects also known as file objects.
                                                             (line    6)
* module（模組）;json:                   使用 json 儲存結構化資料.
                                                             (line    6)
* module（模組）;math（數學）:           常數<3>.            (line   44)
* module（模組）;namespace（命名空間）:  模組<2>.            (line   21)
* module（模組）;os:                     posix --- 最常見的 POSIX 系統呼叫.
                                                             (line   13)
* module（模組）;pickle:                 copy --- 淺層 shallow 和深層 deep 複製操作.
                                                             (line   66)
* module（模組）;pickle <1>:             copyreg --- 註冊 pickle 支援函式.
                                                             (line    8)
* module（模組）;pickle <2>:             shelve --- Python object persistence.
                                                             (line    8)
* module（模組）;pickle <3>:             marshal --- 内部 Python 物件序列化.
                                                             (line   14)
* module（模組）;pty:                    File Descriptor Operations.
                                                             (line  477)
* module（模組）;pwd:                    os path --- 常見的路徑名操作.
                                                             (line  123)
* module（模組）;pyexpat:                xml parsers expat --- 使用 Expat 進行快速 XML 剖析.
                                                             (line   20)
* module（模組）;re:                     fnmatch --- Unix 檔案名稱模式比對.
                                                             (line    8)
* module（模組）;search（搜尋）;path（路徑）: 模組的搜尋路徑.
                                                             (line    6)
* module（模組）;search（搜尋）;path（路徑） <1>: linecache --- 隨機存取文字列.
                                                             (line   30)
* module（模組）;search（搜尋）;path（路徑） <2>: sys --- 系統特定的參數與函式.
                                                             (line 1284)
* module（模組）;search（搜尋）;path（路徑） <3>: site --- Site-specific configuration hook.
                                                             (line   14)
* module（模組）;search（搜尋）;path（路徑） <4>: 嵌入式Python.
                                                             (line   10)
* module（模組）;shelve:                 marshal --- 内部 Python 物件序列化.
                                                             (line   14)
* module（模組）;signal（訊號）:         _thread --- 低階執行緒 API.
                                                             (line  159)
* module（模組）;signal（訊號） <1>:     Signal Handling<2>. (line    7)
* module（模組）;signal（訊號） <2>:     Signal Handling<2>. (line   34)
* module（模組）;signal（訊號） <3>:     Signal Handling<2>. (line   43)
* module（模組）;socket:                 網路協定 Internet protocols 及支援.
                                                             (line    6)
* module（模組）;stat:                   Files and Directories.
                                                             (line 1098)
* module（模組）;struct:                 Socket 物件.        (line  568)
* module（模組）;sys:                    標準模組.           (line    6)
* module（模組）;sys <1>:                except clause.      (line   59)
* module（模組）;sys <2>:                完整的 Python 程式. (line    6)
* module（模組）;sys <3>:                內建函式.           (line 1294)
* module（模組）;sys <4>:                嵌入式Python.       (line   10)
* module（模組）;urllib.request:         http client --- HTTP 協定用戶端.
                                                             (line    8)
* ModuleFinder (modulefinder 中的類別):  modulefinder --- 搜尋腳本所使用的模組.
                                                             (line   22)
* ModuleInfo (pkgutil 中的類別):         pkgutil --- 套件擴充工具程式.
                                                             (line   12)
* ModuleNotFoundError:                   實體例外.           (line   58)
* modules (modulefinder.ModuleFinder 的屬性): modulefinder --- 搜尋腳本所使用的模組.
                                                             (line   41)
* modules (於 sys 模組中):               sys --- 系統特定的參數與函式.
                                                             (line 1257)
* modules_cleanup() (於 test.support.import_helper 模組中): test support import_helper --- 用於 import 測試的工具.
                                                             (line   69)
* modules_setup() (於 test.support.import_helper 模組中): test support import_helper --- 用於 import 測試的工具.
                                                             (line   65)
* modules（sys 模組中）:                 引入模組<2>.        (line    8)
* modules（sys 模組中） <1>:             Initializing and finalizing the interpreter.
                                                             (line    7)
* ModuleSpec (importlib.machinery 中的類別): importlib machinery -- Importers and path hooks.
                                                             (line  358)
* ModuleType (types 中的類別):           Standard Interpreter Types.
                                                             (line  122)
* modulo（餘數）:                        Binary arithmetic operations.
                                                             (line   46)
* modulus (sys.hash_info 的屬性):        sys --- 系統特定的參數與函式.
                                                             (line 1001)
* MON_1 (於 locale 模組中):              locale --- 國際化服務.
                                                             (line  236)
* MON_10 (於 locale 模組中):             locale --- 國際化服務.
                                                             (line  236)
* MON_11 (於 locale 模組中):             locale --- 國際化服務.
                                                             (line  236)
* MON_12 (於 locale 模組中):             locale --- 國際化服務.
                                                             (line  236)
* MON_2 (於 locale 模組中):              locale --- 國際化服務.
                                                             (line  236)
* MON_3 (於 locale 模組中):              locale --- 國際化服務.
                                                             (line  236)
* MON_4 (於 locale 模組中):              locale --- 國際化服務.
                                                             (line  236)
* MON_5 (於 locale 模組中):              locale --- 國際化服務.
                                                             (line  236)
* MON_6 (於 locale 模組中):              locale --- 國際化服務.
                                                             (line  236)
* MON_7 (於 locale 模組中):              locale --- 國際化服務.
                                                             (line  236)
* MON_8 (於 locale 模組中):              locale --- 國際化服務.
                                                             (line  236)
* MON_9 (於 locale 模組中):              locale --- 國際化服務.
                                                             (line  236)
* MONDAY (於 calendar 模組中):           calendar --- 日曆相關函式.
                                                             (line  336)
* monotonic_ns() (於 time 模組中):       函式<4>.            (line  182)
* monotonic() (於 time 模組中):          函式<4>.            (line  153)
* Month (calendar 中的類別):             calendar --- 日曆相關函式.
                                                             (line  382)
* month (calendar.IllegalMonthError 的屬性): calendar --- 日曆相關函式.
                                                             (line  396)
* month (datetime.date 的屬性):          date 物件.          (line  120)
* month (datetime.datetime 的屬性):      datetime 物件.      (line  302)
* month_abbr (於 calendar 模組中):       calendar --- 日曆相關函式.
                                                             (line  360)
* month_name (於 calendar 模組中):       calendar --- 日曆相關函式.
                                                             (line  355)
* month() (於 calendar 模組中):          calendar --- 日曆相關函式.
                                                             (line  305)
* monthcalendar() (於 calendar 模組中):  calendar --- 日曆相關函式.
                                                             (line  295)
* monthdatescalendar() (calendar.Calendar 的方法): calendar --- 日曆相關函式.
                                                             (line   74)
* monthdays2calendar() (calendar.Calendar 的方法): calendar --- 日曆相關函式.
                                                             (line   79)
* monthdayscalendar() (calendar.Calendar 的方法): calendar --- 日曆相關函式.
                                                             (line   84)
* monthrange() (於 calendar 模組中):     calendar --- 日曆相關函式.
                                                             (line  290)
* Morsel (http.cookies 中的類別):        Morsel 物件.        (line    6)
* most_common() (collections.Counter 的方法): Counter 物件.  (line   70)
* mouseinterval() (於 curses 模組中):    函式<5>.            (line  292)
* mousemask() (於 curses 模組中):        函式<5>.            (line  299)
* move_to_end() (collections.OrderedDict 的方法): OrderedDict 物件.
                                                             (line   64)
* move() (curses.panel.Panel 的方法):    Panel Objects.      (line   35)
* move() (curses.window 的方法):         Window Objects.     (line  395)
* move() (mmap.mmap 的方法):             mmap --- 記憶體映射檔案的支援.
                                                             (line  236)
* move() (tkinter.ttk.Treeview 的方法):  ttk Treeview.       (line  210)
* move() (於 shutil 模組中):             Directory and files operations.
                                                             (line  326)
* MozillaCookieJar (http.cookiejar 中的類別): FileCookieJar subclasses and co-operation with web browsers.
                                                             (line    9)
* MRO:                                   術語表.             (line  831)
* mro() (class 的方法):                  特殊屬性.           (line   47)
* msg (http.client.HTTPResponse 的屬性): HTTPResponse 物件.  (line   40)
* msg (json.JSONDecodeError 的屬性):     例外<12>.           (line   10)
* msg (netrc.NetrcParseError 的屬性):    netrc --- netrc 檔案處理.
                                                             (line   41)
* msg (re.PatternError 的屬性):          Exceptions.         (line   15)
* msg (traceback.TracebackException 的屬性): TracebackException 物件.
                                                             (line  117)
* mtime (gzip.GzipFile 的屬性):          gzip --- gzip 檔案的支援.
                                                             (line  150)
* mtime (tarfile.TarInfo 的屬性):        TarInfo 物件.       (line   69)
* mtime() (urllib.robotparser.RobotFileParser 的方法): urllib robotparser --- robots txt 的剖析器.
                                                             (line   37)
* mul() (於 operator 模組中):            operator --- 標準運算子替代函式.
                                                             (line  110)
* Mult (ast 中的類別):                   運算式<2>.          (line   52)
* MultiCall (xmlrpc.client 中的類別):    MultiCall 物件.     (line    9)
* MULTILINE (於 re 模組中):              旗標.               (line   81)
* MultilineContinuationError:            例外<5>.            (line   73)
* MultiLoopChildWatcher (asyncio 中的類別): Process Watchers.
                                                             (line  106)
* multimode() (於 statistics 模組中):    函式細節.           (line  331)
* MultipartConversionError:              email errors：例外和缺陷類別.
                                                             (line   42)
* multiplication（乘）:                  Binary arithmetic operations.
                                                             (line   16)
* multiply() (decimal.Context 的方法):   Context objects.    (line  407)
* mutable object（可變物件）:            Objects values and types.
                                                             (line   11)
* mutable sequence（可變序列）;loop over（迴圈）: Common Sequence Operations.
                                                             (line   75)
* mutable（可變）;sequence（序列）;type（型別）: Mutable Sequence Types.
                                                             (line    6)
* mutable（可變物件）:                   術語表.             (line  835)
* MutableMapping (collections.abc 中的類別): Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line   97)
* MutableMapping (typing 中的類別):      collections abc 中容器 ABC 的別名.
                                                             (line   73)
* MutableSequence (collections.abc 中的類別): Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line   68)
* MutableSequence (typing 中的類別):     collections abc 中容器 ABC 的別名.
                                                             (line   81)
* MutableSet (collections.abc 中的類別): Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line   92)
* MutableSet (typing 中的類別):          collections abc 中容器 ABC 的別名.
                                                             (line   89)
* mvderwin() (curses.window 的方法):     Window Objects.     (line  399)
* mvwin() (curses.window 的方法):        Window Objects.     (line  406)
* myrights() (imaplib.IMAP4 的方法):     IMAP4 物件.         (line  157)
* N_TOKENS (於 token 模組中):            token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  266)
* n_waiting (asyncio.Barrier 的屬性):    Barrier.            (line   98)
* n_waiting (threading.Barrier 的屬性):  Barrier Objects.    (line   97)
* NAK (於 curses.ascii 模組中):          curses ascii --- ASCII 字元的工具程式.
                                                             (line   88)
* Name (ast 中的類別):                   變數.               (line    6)
* name (bz2.BZ2File 的屬性):             De compression of files.
                                                             (line  135)
* name (codecs.CodecInfo 的屬性):        codecs --- 編解碼器註冊表和基底類別.
                                                             (line   65)
* name (contextvars.ContextVar 的屬性):  Context Variables.  (line   24)
* name (doctest.DocTest 的屬性):         DocTest 物件.       (line   30)
* name (email.headerregistry.BaseHeader 的屬性): email headerregistry：自訂標頭物件.
                                                             (line   45)
* name (enum.Enum 的屬性):               資料型別<2>.        (line  131)
* name (gzip.GzipFile 的屬性):           gzip --- gzip 檔案的支援.
                                                             (line  158)
* name (hashlib.hash 的屬性):            雜湊物件.           (line   18)
* name (hmac.HMAC 的屬性):               hmac --- 基於金鑰雜湊的訊息驗證.
                                                             (line   88)
* name (http.cookiejar.Cookie 的屬性):   Cookie 物件<2>.     (line   28)
* name (ImportError 的屬性):             實體例外.           (line   48)
* name (importlib.abc.FileLoader 的屬性): importlib abc -- Abstract base classes related to import.
                                                             (line  330)
* name (importlib.abc.Traversable 的屬性): importlib abc -- Abstract base classes related to import.
                                                             (line  545)
* name (importlib.machinery.AppleFrameworkLoader 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  498)
* name (importlib.machinery.ExtensionFileLoader 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  300)
* name (importlib.machinery.ModuleSpec 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  374)
* name (importlib.machinery.SourceFileLoader 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  206)
* name (importlib.machinery.SourcelessFileLoader 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  250)
* name (importlib.resources.abc.Traversable 的屬性): importlib resources abc -- 資源的抽象基底類別.
                                                             (line   94)
* name (inspect.Parameter 的屬性):       Introspecting callables with the Signature object.
                                                             (line  205)
* name (io.FileIO 的屬性):               原始檔案 I/O.       (line   59)
* name (logging.Logger 的屬性):          Logger 物件.        (line   26)
* name (lzma.LZMAFile 的屬性):           Reading and writing compressed files.
                                                             (line  104)
* name (multiprocessing.Process 的屬性): Process 與例外.     (line   82)
* name (multiprocessing.shared_memory.SharedMemory 的屬性): multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取.
                                                             (line  105)
* name (os.DirEntry 的屬性):             Files and Directories.
                                                             (line  926)
* name (pathlib.PurePath 的屬性):        方法與屬性.         (line  118)
* name (pyclbr.Class 的屬性):            Class Objects.      (line   20)
* name (pyclbr.Function 的屬性):         函式物件.           (line   19)
* name (sys.thread_info 的屬性):         sys --- 系統特定的參數與函式.
                                                             (line 1872)
* name (tarfile.TarInfo 的屬性):         TarInfo 物件.       (line   61)
* name (tempfile.TemporaryDirectory 的屬性): tempfile --- 生成臨時檔案和目錄.
                                                             (line  165)
* name (threading.Thread 的屬性):        Thread Objects.     (line  153)
* name (traceback.FrameSummary 的屬性):  FrameSummary 物件.  (line   37)
* name (webbrowser.controller 的屬性):   Browser Controller Objects.
                                                             (line    9)
* name (xml.dom.Attr 的屬性):            Attr Objects.       (line    8)
* name (xml.dom.DocumentType 的屬性):    DocumentType 物件.  (line   33)
* name (zipfile.Path 的屬性):            Path Objects.       (line   21)
* name (於 os 模組中):                   os --- 各種作業系統介面.
                                                             (line   48)
* NAME (於 token 模組中):                token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   42)
* name() (於 unicodedata 模組中):        unicodedata --- Unicode 資料庫.
                                                             (line   25)
* name（名稱）:                          Identifiers and keywords.
                                                             (line    6)
* name（名稱） <1>:                      Binding of names.   (line    6)
* name（名稱） <2>:                      Identifiers Names.  (line    6)
* name（名稱）;binding（綁定）:          函式定義.           (line    6)
* name（名稱）;binding（綁定） <1>:      函式定義.           (line    6)
* name（名稱）;binding（綁定） <2>:      類別定義.           (line    6)
* name（名稱）;binding（繫結）:          import 陳述式.      (line    6)
* name（名稱）;binding（繫結） <1>:      import 陳述式.      (line   52)
* name（名稱）;mangling:                 Identifiers Names.  (line   14)
* name（名稱）;mangling（修飾）:         私有變數.           (line   12)
* name2codepoint (於 html.entities 模組中): html entities --- HTML 一般實體的定義.
                                                             (line   27)
* named expression（附名運算式）:        Boolean operations. (line   37)
* Named Shared Memory（附名共享記憶體）: multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取.
                                                             (line   10)
* named tuple（附名元組）:               術語表.             (line  840)
* NAMED_FLAGS (enum.EnumCheck 的屬性):   資料型別<2>.        (line  592)
* NamedExpr (ast 中的類別):              運算式<2>.          (line  177)
* NamedTemporaryFile() (於 tempfile 模組中): tempfile --- 生成臨時檔案和目錄.
                                                             (line   63)
* NamedTuple (typing 中的類別):          Other special directives.
                                                             (line   10)
* namedtuple() (於 collections 模組中):  namedtuple 擁有具名欄位之 tuple 的工廠函式.
                                                             (line   10)
* NameError:                             實體例外.           (line   97)
* NameError（內建例外）:                 Resolution of names.
                                                             (line   16)
* namelist() (zipfile.ZipFile 的方法):   ZipFile 物件.       (line  124)
* nameprep() (於 encodings.idna 模組中): encodings idna --- Internationalized Domain Names in Applications.
                                                             (line   50)
* namer (logging.handlers.BaseRotatingHandler 的屬性): BaseRotatingHandler.
                                                             (line   17)
* namereplace_errors() (於 codecs 模組中): Error Handlers.   (line  181)
* namereplace;error handler's name（錯誤處理器名稱）: Error Handlers.
                                                             (line   54)
* names() (於 tkinter.font 模組中):      tkinter font --- Tkinter 字型包裝器.
                                                             (line   89)
* Namespace (argparse 中的類別):         The Namespace object.
                                                             (line    6)
* Namespace (multiprocessing.managers 中的類別): Managers.   (line  242)
* namespace package（命名空間套件）:     術語表.             (line  876)
* NAMESPACE_DNS (於 uuid 模組中):        uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  191)
* NAMESPACE_OID (於 uuid 模組中):        uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  200)
* NAMESPACE_URL (於 uuid 模組中):        uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  196)
* NAMESPACE_X500 (於 uuid 模組中):       uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  204)
* namespace() (imaplib.IMAP4 的方法):    IMAP4 物件.         (line  162)
* Namespace() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  192)
* namespace（命名空間）:                 Naming and binding. (line    6)
* namespace（命名空間） <1>:             術語表.             (line  865)
* NamespaceErr:                          例外<15>.           (line   66)
* NamespaceLoader (importlib.machinery 中的類別): importlib machinery -- Importers and path hooks.
                                                             (line  341)
* namespaceURI (xml.dom.Node 的屬性):    Node Objects.       (line   74)
* nametofont() (於 tkinter.font 模組中): tkinter font --- Tkinter 字型包裝器.
                                                             (line   93)
* NaN:                                   內建函式.           (line  646)
* nan (sys.hash_info 的屬性):            sys --- 系統特定的參數與函式.
                                                             (line 1009)
* nan (於 cmath 模組中):                 常數<3>.            (line   32)
* nan (於 math 模組中):                  常數<2>.            (line   33)
* nanj (於 cmath 模組中):                常數<3>.            (line   38)
* NannyNag:                              tabnanny --- 偵測不良縮排.
                                                             (line   34)
* napms() (於 curses 模組中):            函式<5>.            (line  308)
* nargs (optparse.Option 的屬性):        Option attributes.  (line   50)
* native_id (threading.Thread 的屬性):   Thread Objects.     (line  175)
* nbytes (memoryview 的屬性):            Memory Views.       (line  379)
* ncurses_version (於 curses 模組中):    Constants.          (line   24)
* ND (inspect.BufferFlags 的屬性):       Buffer flags.       (line   21)
* ndiff() (於 difflib 模組中):           difflib --- 計算差異的輔助工具.
                                                             (line  233)
* ndim (memoryview 的屬性):              Memory Views.       (line  445)
* ne() (於 operator 模組中):             operator --- 標準運算子替代函式.
                                                             (line   20)
* needs_input (bz2.BZ2Decompressor 的屬性): Incremental de compression.
                                                             (line   85)
* needs_input (lzma.LZMADecompressor 的屬性): Compressing and decompressing data in memory.
                                                             (line  175)
* neg() (於 operator 模組中):            operator --- 標準運算子替代函式.
                                                             (line  122)
* negation（否定）:                      Unary arithmetic and bitwise operations.
                                                             (line   10)
* nested scope（巢狀作用域）:            術語表.             (line  885)
* netmask (ipaddress.IPv4Network 的屬性): Network objects.   (line  101)
* netmask (ipaddress.IPv6Network 的屬性): Network objects.   (line  315)
* NetmaskValueError:                     Custom Exceptions.  (line   13)
* netrc (netrc 中的類別):                netrc --- netrc 檔案處理.
                                                             (line   13)
* NetrcParseError:                       netrc --- netrc 檔案處理.
                                                             (line   36)
* netscape (http.cookiejar.CookiePolicy 的屬性): CookiePolicy 物件.
                                                             (line   68)
* network (ipaddress.IPv4Interface 的屬性): Interface objects.
                                                             (line   28)
* network (ipaddress.IPv6Interface 的屬性): Interface objects.
                                                             (line   76)
* network_address (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line   86)
* network_address (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  309)
* Never (於 typing 模組中):              特別型別.           (line   95)
* NEVER_EQ (於 test.support 模組中):     test support --- Python 測試套件的工具.
                                                             (line  178)
* new_child() (collections.ChainMap 的方法): ChainMap 物件.  (line   40)
* new_class() (於 types 模組中):         Dynamic Type Creation.
                                                             (line    6)
* new_event_loop() (asyncio.AbstractEventLoopPolicy 的方法): Policy Objects.
                                                             (line   27)
* new_event_loop() (於 asyncio 模組中):  事件迴圈.           (line   59)
* new_panel() (於 curses.panel 模組中):  函式<6>.            (line   12)
* new-style class（新式類別）:           術語表.             (line  893)
* new() (於 hashlib 模組中):             建構函式.           (line    6)
* new() (於 hmac 模組中):                hmac --- 基於金鑰雜湊的訊息驗證.
                                                             (line   12)
* newfunc (C type):                      Slot Type typedefs. (line   31)
* NEWLINE (於 token 模組中):             token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   48)
* NEWLINE token（換行標誌）:             Logical lines.      (line    6)
* NEWLINE token（換行標誌） <1>:         複合陳述式.         (line   55)
* newlines (io.TextIOBase 的屬性):       文字 I/O<2>.        (line   24)
* newpad() (於 curses 模組中):           函式<5>.            (line  312)
* NewType (typing 中的類別):             Other special directives.
                                                             (line  100)
* newwin() (於 curses 模組中):           函式<5>.            (line  332)
* next (pdb command):                    Debugger Commands.  (line  202)
* next_minus() (decimal.Context 的方法): Context objects.    (line  411)
* next_minus() (decimal.Decimal 的方法): Decimal objects.    (line  398)
* next_plus() (decimal.Context 的方法):  Context objects.    (line  415)
* next_plus() (decimal.Decimal 的方法):  Decimal objects.    (line  404)
* next_toward() (decimal.Context 的方法): Context objects.   (line  419)
* next_toward() (decimal.Decimal 的方法): Decimal objects.   (line  410)
* next() (tarfile.TarFile 的方法):       TarFile 物件.       (line  131)
* next() (tkinter.ttk.Treeview 的方法):  ttk Treeview.       (line  221)
* nextafter() (於 math 模組中):          數論與表現函式.     (line  178)
* nextfile() (於 fileinput 模組中):      fileinput --- 逐列疊代多個輸入串流.
                                                             (line  121)
* nextkey() (dbm.gnu.gdbm 的方法):       dbm gnu --- GNU 資料庫管理器.
                                                             (line   85)
* nextSibling (xml.dom.Node 的屬性):     Node Objects.       (line   42)
* ngettext() (gettext.GNUTranslations 的方法): The GNUTranslations class.
                                                             (line   47)
* ngettext() (gettext.NullTranslations 的方法): The NullTranslations class.
                                                             (line   41)
* ngettext() (於 gettext 模組中):        GNU gettext API.    (line   44)
* nice() (於 os 模組中):                 行程管理.           (line  354)
* NL (於 curses.ascii 模組中):           curses ascii --- ASCII 字元的工具程式.
                                                             (line   55)
* NL (於 token 模組中):                  token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  262)
* nl_langinfo() (於 locale 模組中):      locale --- 國際化服務.
                                                             (line  172)
* nl() (於 curses 模組中):               函式<5>.            (line  342)
* nlargest() (於 heapq 模組中):          heapq --- 堆積佇列 heap queue 演算法.
                                                             (line   90)
* nlst() (ftplib.FTP 的方法):            FTP 物件.           (line  262)
* NO (於 tkinter.messagebox 模組中):     tkinter messagebox --- Tkinter 訊息提示.
                                                             (line  139)
* no_cache() (zoneinfo.ZoneInfo 的類別方法): The ZoneInfo class.
                                                             (line   41)
* NO_EVENTS (monitoring event):          事件.               (line   94)
* no_proxy:                              urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  273)
* no_site (sys.flags 的屬性):            sys --- 系統特定的參數與函式.
                                                             (line  543)
* no_tracing() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  535)
* no_type_check_decorator() (於 typing 模組中): 函式與裝飾器.
                                                             (line  360)
* no_type_check() (於 typing 模組中):    函式與裝飾器.       (line  348)
* no_user_site (sys.flags 的屬性):       sys --- 系統特定的參數與函式.
                                                             (line  540)
* nocbreak() (於 curses 模組中):         函式<5>.            (line  348)
* NoDataAllowedErr:                      例外<15>.           (line   83)
* node (uuid.UUID 的屬性):               uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  112)
* node() (於 platform 模組中):           跨平台.             (line   35)
* NoDefault (於 typing 模組中):          Introspection helpers.
                                                             (line  162)
* nodelay() (curses.window 的方法):      Window Objects.     (line  410)
* nodeName (xml.dom.Node 的屬性):        Node Objects.       (line   79)
* NodeTransformer (ast 中的類別):        ast 輔助程式.       (line  193)
* nodeType (xml.dom.Node 的屬性):        Node Objects.       (line    8)
* nodeValue (xml.dom.Node 的屬性):       Node Objects.       (line   88)
* NodeVisitor (ast 中的類別):            ast 輔助程式.       (line  160)
* noecho() (於 curses 模組中):           函式<5>.            (line  353)
* NOEXPR (於 locale 模組中):             locale --- 國際化服務.
                                                             (line  281)
* NOFLAG (於 re 模組中):                 旗標.               (line   95)
* NoModificationAllowedErr:              例外<15>.           (line   88)
* NonCallableMagicMock (unittest.mock 中的類別): Magic Mock. (line   20)
* NonCallableMock (unittest.mock 中的類別): Mock 類別.       (line  513)
* None (內建變數):                       內建常數.           (line   18)
* None（內建物件）:                      真值檢測.           (line   14)
* NoneType (於 types 模組中):            Standard Interpreter Types.
                                                             (line   19)
* nonl() (於 curses 模組中):             函式<5>.            (line  357)
* Nonlocal (ast 中的類別):               函式和類別定義.     (line  137)
* nonmember() (於 enum 模組中):          通用項目與裝飾器.   (line   78)
* noop() (imaplib.IMAP4 的方法):         IMAP4 物件.         (line  166)
* noop() (poplib.POP3 的方法):           POP3 物件.          (line   79)
* NoOptionError:                         例外<5>.            (line   32)
* NOP (opcode):                          Python Bytecode Instructions.
                                                             (line  126)
* noqiflush() (於 curses 模組中):        函式<5>.            (line  367)
* noraw() (於 curses 模組中):            函式<5>.            (line  375)
* NoReturn (於 typing 模組中):           特別型別.           (line   95)
* NORMAL (於 tkinter.font 模組中):       tkinter font --- Tkinter 字型包裝器.
                                                             (line   15)
* NORMAL_PRIORITY_CLASS (於 subprocess 模組中): Windows Constants.
                                                             (line   96)
* NormalDist (statistics 中的類別):      NormalDist 物件.    (line   12)
* NORMALIZE_WHITESPACE (於 doctest 模組中): 可選旗標.        (line   39)
* normalize() (decimal.Context 的方法):  Context objects.    (line  423)
* normalize() (decimal.Decimal 的方法):  Decimal objects.    (line  418)
* normalize() (xml.dom.Node 的方法):     Node Objects.       (line  141)
* normalize() (於 locale 模組中):        locale --- 國際化服務.
                                                             (line  419)
* normalize() (於 unicodedata 模組中):   unicodedata --- Unicode 資料庫.
                                                             (line   81)
* normalvariate() (於 random 模組中):    實數分布.           (line   71)
* normcase() (於 os.path 模組中):        os path --- 常見的路徑名操作.
                                                             (line  293)
* normpath() (於 os.path 模組中):        os path --- 常見的路徑名操作.
                                                             (line  300)
* NoSectionError:                        例外<5>.            (line   10)
* NoSuchMailboxError:                    例外<13>.           (line   12)
* Not (ast 中的類別):                    運算式<2>.          (line   26)
* not_() (於 operator 模組中):           operator --- 標準運算子替代函式.
                                                             (line   43)
* NotADirectoryError:                    作業系統例外.       (line   82)
* notation（標記法）:                    Notation.           (line    6)
* notationDecl() (xml.sax.handler.DTDHandler 的方法): DTDHandler 物件.
                                                             (line    8)
* NotationDeclHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line  312)
* notations (xml.dom.DocumentType 的屬性): DocumentType 物件.
                                                             (line   46)
* NotConnected:                          http client --- HTTP 協定用戶端.
                                                             (line  136)
* Notebook (tkinter.ttk 中的類別):       ttk Notebook.       (line    6)
* NotEmptyError:                         例外<13>.           (line   19)
* NotEq (ast 中的類別):                  運算式<2>.          (line  105)
* NOTEQUAL (於 token 模組中):            token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  138)
* NotFoundErr:                           例外<15>.           (line   72)
* notify_all() (asyncio.Condition 的方法): Condition.        (line   60)
* notify_all() (threading.Condition 的方法): Condition Objects.
                                                             (line  172)
* notify() (asyncio.Condition 的方法):   Condition.          (line   48)
* notify() (threading.Condition 的方法): Condition Objects.  (line  152)
* notimeout() (curses.window 的方法):    Window Objects.     (line  414)
* NotImplemented (內建變數):             內建常數.           (line   25)
* NotImplementedError:                   實體例外.           (line  108)
* NotImplementedType (於 types 模組中):  Standard Interpreter Types.
                                                             (line  102)
* NotIn (ast 中的類別):                  運算式<2>.          (line  105)
* NotRequired (於 typing 模組中):        特別型式.           (line  212)
* NOTSET (於 logging 模組中):            Logging Levels.     (line   16)
* NotStandaloneHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line  363)
* NotSupportedErr:                       例外<15>.           (line   78)
* NotSupportedError:                     例外<4>.            (line   85)
* noutrefresh() (curses.window 的方法):  Window Objects.     (line  422)
* NOVEMBER (於 calendar 模組中):         calendar --- 日曆相關函式.
                                                             (line  365)
* now() (datetime.datetime 的類別方法):  datetime 物件.      (line   60)
* npgettext() (gettext.GNUTranslations 的方法): The GNUTranslations class.
                                                             (line   79)
* npgettext() (gettext.NullTranslations 的方法): The NullTranslations class.
                                                             (line   55)
* npgettext() (於 gettext 模組中):       GNU gettext API.    (line   67)
* NSIG (於 signal 模組中):               模組內容<5>.        (line  208)
* nsmallest() (於 heapq 模組中):         heapq --- 堆積佇列 heap queue 演算法.
                                                             (line   97)
* NT_OFFSET (於 token 模組中):           token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  268)
* NTEventLogHandler (logging.handlers 中的類別): NTEventLogHandler.
                                                             (line   11)
* ntohl() (於 socket 模組中):            其他函式<2>.        (line  196)
* ntohs() (於 socket 模組中):            其他函式<2>.        (line  203)
* ntransfercmd() (ftplib.FTP 的方法):    FTP 物件.           (line  244)
* NUL (於 curses.ascii 模組中):          curses ascii --- ASCII 字元的工具程式.
                                                             (line   19)
* null;operation（操作）:                pass 陳述式<2>.     (line    6)
* null;operation（操作） <1>:            pass 陳述式<2>.     (line    6)
* nullcontext() (於 contextlib 模組中):  Utilities.          (line  221)
* NullHandler (logging 中的類別):        NullHandler.        (line   12)
* NullTranslations (gettext 中的類別):   The NullTranslations class.
                                                             (line   13)
* num_addresses (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line  128)
* num_addresses (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  327)
* num_tickets (ssl.SSLContext 的屬性):   SSL Contexts.       (line  567)
* Number (numbers 中的類別):             numbers --- 數值的抽象基底類別.
                                                             (line   13)
* NUMBER (於 token 模組中):              token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   44)
* number_class() (decimal.Context 的方法): Context objects.  (line  427)
* number_class() (decimal.Decimal 的方法): Decimal objects.  (line  441)
* number（數字）:                        Numeric literals.   (line    6)
* numerator (fractions.Fraction 的屬性): fractions --- 有理數.
                                                             (line  113)
* numerator (numbers.Rational 的屬性):   數值的階層.         (line   46)
* numeric literal（數值常數）:           Numeric literals.   (line    6)
* numeric() (於 unicodedata 模組中):     unicodedata --- Unicode 資料庫.
                                                             (line   43)
* numeric（數值）;conversions（轉換）:   數值型別 --- int、float、complex.
                                                             (line   97)
* numeric（數值）;literals（字面值）:    數值型別 --- int、float、complex.
                                                             (line   15)
* numinput() (於 turtle 模組中):         Input methods.      (line   22)
* O_APPEND (於 os 模組中):               File Descriptor Operations.
                                                             (line  416)
* O_ASYNC (於 os 模組中):                File Descriptor Operations.
                                                             (line  458)
* O_BINARY (於 os 模組中):               File Descriptor Operations.
                                                             (line  438)
* O_CLOEXEC (於 os 模組中):              File Descriptor Operations.
                                                             (line  426)
* O_CREAT (於 os 模組中):                File Descriptor Operations.
                                                             (line  416)
* O_DIRECT (於 os 模組中):               File Descriptor Operations.
                                                             (line  458)
* O_DIRECTORY (於 os 模組中):            File Descriptor Operations.
                                                             (line  458)
* O_DSYNC (於 os 模組中):                File Descriptor Operations.
                                                             (line  426)
* O_EVTONLY (於 os 模組中):              File Descriptor Operations.
                                                             (line  448)
* O_EXCL (於 os 模組中):                 File Descriptor Operations.
                                                             (line  416)
* O_EXLOCK (於 os 模組中):               File Descriptor Operations.
                                                             (line  458)
* O_FSYNC (於 os 模組中):                File Descriptor Operations.
                                                             (line  448)
* O_NDELAY (於 os 模組中):               File Descriptor Operations.
                                                             (line  426)
* O_NOATIME (於 os 模組中):              File Descriptor Operations.
                                                             (line  458)
* O_NOCTTY (於 os 模組中):               File Descriptor Operations.
                                                             (line  426)
* O_NOFOLLOW (於 os 模組中):             File Descriptor Operations.
                                                             (line  458)
* O_NOFOLLOW_ANY (於 os 模組中):         File Descriptor Operations.
                                                             (line  448)
* O_NOINHERIT (於 os 模組中):            File Descriptor Operations.
                                                             (line  438)
* O_NONBLOCK (於 os 模組中):             File Descriptor Operations.
                                                             (line  426)
* O_PATH (於 os 模組中):                 File Descriptor Operations.
                                                             (line  458)
* O_RANDOM (於 os 模組中):               File Descriptor Operations.
                                                             (line  438)
* O_RDONLY (於 os 模組中):               File Descriptor Operations.
                                                             (line  416)
* O_RDWR (於 os 模組中):                 File Descriptor Operations.
                                                             (line  416)
* O_RSYNC (於 os 模組中):                File Descriptor Operations.
                                                             (line  426)
* O_SEQUENTIAL (於 os 模組中):           File Descriptor Operations.
                                                             (line  438)
* O_SHLOCK (於 os 模組中):               File Descriptor Operations.
                                                             (line  458)
* O_SHORT_LIVED (於 os 模組中):          File Descriptor Operations.
                                                             (line  438)
* O_SYMLINK (於 os 模組中):              File Descriptor Operations.
                                                             (line  448)
* O_SYNC (於 os 模組中):                 File Descriptor Operations.
                                                             (line  426)
* O_TEMPORARY (於 os 模組中):            File Descriptor Operations.
                                                             (line  438)
* O_TEXT (於 os 模組中):                 File Descriptor Operations.
                                                             (line  438)
* O_TMPFILE (於 os 模組中):              File Descriptor Operations.
                                                             (line  458)
* O_TRUNC (於 os 模組中):                File Descriptor Operations.
                                                             (line  416)
* O_WRONLY (於 os 模組中):               File Descriptor Operations.
                                                             (line  416)
* obj (memoryview 的屬性):               Memory Views.       (line  368)
* object (UnicodeError 的屬性):          實體例外.           (line  376)
* object (內建類別):                     內建函式.           (line 1099)
* object.__match_args__ (內建變數):      Customizing positional arguments in class pattern matching.
                                                             (line   12)
* object.__slots__ (內建變數):           __slots__<2>.       (line   14)
* object（模組）;module（模組）:         模組物件.           (line    6)
* object（物件）:                        Objects values and types.
                                                             (line    6)
* object（物件） <1>:                    術語表.             (line  901)
* object（物件）;asynchronous-generator（非同步產生器）: Asynchronous generator functions<2>.
                                                             (line   66)
* object（物件）;Boolean（布林）:        numbers Integral.   (line   27)
* object（物件）;Boolean（布林） <1>:    數值型別 --- int、float、complex.
                                                             (line    6)
* object（物件）;built-in function（內建函式）: Built-in functions.
                                                             (line    6)
* object（物件）;built-in function（內建函式） <1>: Calls.   (line  140)
* object（物件）;built-in method（內建方法）: Built-in methods.
                                                             (line    6)
* object（物件）;built-in method（內建方法） <1>: Calls.     (line  140)
* object（物件）;bytearray（位元組陣列）: Mutable Sequence Types.
                                                             (line    6)
* object（物件）;bytearray（位元組陣列） <1>: Binary Sequence Types --- bytes bytearray memoryview.
                                                             (line    6)
* object（物件）;bytearray（位元組陣列） <2>: Bytearray Objects.
                                                             (line    6)
* object（物件）;bytearray（位元組陣列） <3>: 位元組陣列物件 Byte Array Objects.
                                                             (line    6)
* object（物件）;bytes（位元組）:        Binary Sequence Types --- bytes bytearray memoryview.
                                                             (line    6)
* object（物件）;bytes（位元組） <1>:    Bytes Objects.      (line    6)
* object（物件）;bytes（位元組） <2>:    位元組物件 Bytes Objects.
                                                             (line    9)
* object（物件）;callable（可呼叫物件）: Callable types.     (line    6)
* object（物件）;callable（可呼叫物件） <1>: Slicings.       (line   38)
* object（物件）;Capsule:                Capsules<2>.        (line    6)
* object（物件）;class instance（類別實例）: Custom classes. (line   19)
* object（物件）;class instance（類別實例） <1>: Class instances.
                                                             (line    6)
* object（物件）;class instance（類別實例） <2>: Calls.      (line  149)
* object（物件）;class（類別）:          Custom classes.     (line   19)
* object（物件）;class（類別） <1>:      Calls.              (line  145)
* object（物件）;class（類別） <2>:      類別定義.           (line    6)
* object（物件）;code（程式碼）:         Code objects.       (line    6)
* object（物件）;code（程式碼） <1>:     Methods.            (line   44)
* object（物件）;code（程式碼） <2>:     marshal --- 内部 Python 物件序列化.
                                                             (line   31)
* object（物件）;code（程式碼） <3>:     Cell 物件.          (line   51)
* object（物件）;complex number（複數）: 數值型別 --- int、float、complex.
                                                             (line    6)
* object（物件）;complex number（複數） <1>: 複數物件.       (line    6)
* object（物件）;complex（複數）:        numbers Complex complex.
                                                             (line    6)
* object（物件）;deallocation:           Finalization and De-allocation.
                                                             (line    6)
* object（物件）;dictionary（字典）:     字典.               (line    6)
* object（物件）;dictionary（字典） <1>: Custom classes.     (line   19)
* object（物件）;dictionary（字典） <2>: Basic customization.
                                                             (line  229)
* object（物件）;dictionary（字典） <3>: Dictionary displays.
                                                             (line    6)
* object（物件）;dictionary（字典） <4>: Subscriptions.      (line    6)
* object（物件）;dictionary（字典） <5>: Assignment statements.
                                                             (line  115)
* object（物件）;dictionary（字典） <6>: Mapping Types --- dict.
                                                             (line    6)
* object（物件）;dictionary（字典） <7>: 字典物件.           (line    6)
* object（物件）;Ellipsis:               Ellipsis.           (line    6)
* object（物件）;file（檔案）:           讀寫檔案.           (line    6)
* object（物件）;file（檔案） <1>:       檔案物件 File Objects.
                                                             (line    6)
* object（物件）;finalization:           Finalization and De-allocation.
                                                             (line    6)
* object（物件）;floating-point（浮點）: numbers Real float. (line    6)
* object（物件）;floating-point（浮點） <1>: 浮點數（Floating-Point）物件.
                                                             (line    6)
* object（物件）;floating-point（浮點數）: 數值型別 --- int、float、complex.
                                                             (line    6)
* object（物件）;frame:                  Frame objects.      (line    6)
* object（物件）;frozenset（凍結集合）:  Set types.          (line   29)
* object（物件）;frozenset（凍結集合） <1>: 集合物件.        (line    6)
* object（物件）;function （函式）:      自訂函式.           (line    6)
* object（物件）;function （函式） <1>:  Built-in functions. (line    6)
* object（物件）;function （函式） <2>:  Calls.              (line  131)
* object（物件）;function （函式） <3>:  Calls.              (line  140)
* object（物件）;function （函式） <4>:  函式定義.           (line    6)
* object（物件）;function（函式）:       函式物件 Function Objects.
                                                             (line    6)
* object（物件）;generator（產生器）:    特殊唯讀屬性<2>.    (line   82)
* object（物件）;generator（產生器） <1>: Generator expressions.
                                                             (line    6)
* object（物件）;generator（產生器） <2>: Yield expressions. (line  109)
* object（物件）;GenericAlias（泛型別名）: 泛型別名型別.     (line    6)
* object（物件）;immutable sequence（不可變序列）: Immutable sequences.
                                                             (line    6)
* object（物件）;immutable（不可變）:    Immutable sequences.
                                                             (line    6)
* object（物件）;instance（實例）:       Custom classes.     (line   19)
* object（物件）;instance（實例） <1>:   Class instances.    (line    6)
* object（物件）;instance（實例） <2>:   Calls.              (line  149)
* object（物件）;instancemethod:         實例方法物件 Instance Method Objects.
                                                             (line    6)
* object（物件）;integer（整数）:        整數物件.           (line    6)
* object（物件）;integer（整數）:        numbers Integral.   (line    6)
* object（物件）;integer（整數） <1>:    數值型別 --- int、float、complex.
                                                             (line    6)
* object（物件）;io.StringIO:            Text Sequence Type --- str.
                                                             (line   36)
* object（物件）;list（串列）:           Mutable sequences.  (line   18)
* object（物件）;list（串列） <1>:       List displays.      (line    6)
* object（物件）;list（串列） <2>:       Attribute references.
                                                             (line   10)
* object（物件）;list（串列） <3>:       Subscriptions.      (line    6)
* object（物件）;list（串列） <4>:       Slicings.           (line    6)
* object（物件）;list（串列） <5>:       Assignment statements.
                                                             (line  106)
* object（物件）;list（串列） <6>:       Mutable Sequence Types.
                                                             (line    6)
* object（物件）;list（串列） <7>:       List（串列）<2>.    (line    6)
* object（物件）;list（串列） <8>:       List（串列）物件.   (line    6)
* object（物件）;long integer（長整数）: 整數物件.           (line    6)
* object（物件）;mapping（對映）:        Mappings.           (line    6)
* object（物件）;mapping（對映） <1>:    Class instances.    (line   26)
* object（物件）;mapping（對映） <2>:    Subscriptions.      (line    6)
* object（物件）;mapping（對映） <3>:    Assignment statements.
                                                             (line  115)
* object（物件）;mapping（對映） <4>:    Mapping Types --- dict.
                                                             (line    6)
* object（物件）;mapping（對映） <5>:    容器物件.           (line    6)
* object（物件）;memoryview（記憶體視圖）: Binary Sequence Types --- bytes bytearray memoryview.
                                                             (line    6)
* object（物件）;memoryview（記憶體視圖） <1>: Ellipsis Object.
                                                             (line   14)
* object（物件）;method（方法）:         實例物件.           (line   23)
* object（物件）;method（方法） <1>:     Instance methods.   (line    6)
* object（物件）;method（方法） <2>:     Built-in methods.   (line    6)
* object（物件）;method（方法） <3>:     Calls.              (line  140)
* object（物件）;method（方法） <4>:     Methods.            (line    6)
* object（物件）;method（方法） <5>:     方法物件 Method Objects.
                                                             (line    6)
* object（物件）;module（模組）:         模組<2>.            (line    6)
* object（物件）;module（模組） <1>:     Attribute references.
                                                             (line   10)
* object（物件）;mutable sequence（可變序列）: Mutable sequences.
                                                             (line    6)
* object（物件）;mutable（可變的）:      Mutable sequences.  (line    6)
* object（物件）;mutable（可變的） <1>:  Assignment statements.
                                                             (line    6)
* object（物件）;mutable（可變的） <2>:  Assignment statements.
                                                             (line  101)
* object（物件）;None:                   None.               (line    6)
* object（物件）;None <1>:               Expression statements.
                                                             (line   17)
* object（物件）;None <2>:               None 物件.          (line    6)
* object（物件）;NotImplemented:         NotImplemented.     (line    6)
* object（物件）;numeric（數值）:        numbers Number.     (line    6)
* object（物件）;numeric（數值） <1>:    Class instances.    (line   26)
* object（物件）;numeric（數值） <2>:    比較運算.           (line   41)
* object（物件）;numeric（數值） <3>:    數值型別 --- int、float、complex.
                                                             (line    6)
* object（物件）;numeric（數值） <4>:    數值物件.           (line    6)
* object（物件）;range:                  Ranges.             (line    6)
* object（物件）;sequence（序列）:       Sequences.          (line    6)
* object（物件）;sequence（序列） <1>:   Class instances.    (line   26)
* object（物件）;sequence（序列） <2>:   Subscriptions.      (line    6)
* object（物件）;sequence（序列） <3>:   Slicings.           (line    6)
* object（物件）;sequence（序列） <4>:   Membership test operations.
                                                             (line   36)
* object（物件）;sequence（序列） <5>:   Assignment statements.
                                                             (line  106)
* object（物件）;sequence（序列） <6>:   The for statement.  (line    6)
* object（物件）;sequence（序列） <7>:   Common Sequence Operations.
                                                             (line    6)
* object（物件）;sequence（序列） <8>:   序列物件.           (line    6)
* object（物件）;set type（集合型別）:   Set types.          (line    6)
* object（物件）;set（集合）:            Set types.          (line   23)
* object（物件）;set（集合） <1>:        Set displays.       (line    6)
* object（物件）;set（集合） <2>:        Set Types --- set frozenset.
                                                             (line    6)
* object（物件）;set（集合） <3>:        集合物件.           (line    6)
* object（物件）;slice（切片）:          Emulating container types.
                                                             (line   65)
* object（物件）;socket:                 socket --- 低階網路介面.
                                                             (line   22)
* object（物件）;string（字串）:         Subscriptions.      (line    6)
* object（物件）;string（字串） <1>:     Slicings.           (line    6)
* object（物件）;string（字串） <2>:     Ranges.             (line  125)
* object（物件）;traceback:              Traceback objects.  (line    6)
* object（物件）;traceback <1>:          raise 陳述式.       (line   21)
* object（物件）;traceback <2>:          except clause.      (line   59)
* object（物件）;traceback <3>:          sys --- 系統特定的參數與函式.
                                                             (line  454)
* object（物件）;traceback <4>:          traceback --- 列印或取得堆疊回溯 stack traceback.
                                                             (line   16)
* object（物件）;tuple:                  Subscriptions.      (line    6)
* object（物件）;tuple <1>:              Slicings.           (line    6)
* object（物件）;tuple <2>:              Expression lists.   (line   11)
* object（物件）;tuple（元組）:          Immutable sequences.
                                                             (line   29)
* object（物件）;tuple（元組） <1>:      Immutable Sequence Types.
                                                             (line    6)
* object（物件）;tuple（元組） <2>:      Tuples.             (line    6)
* object（物件）;tuple（元組） <3>:      Tuple（元組）物件.  (line    6)
* object（物件）;type（型別）:           內建函式.           (line 1819)
* object（物件）;type（型別） <1>:       物件、型別和參照計數.
                                                             (line    6)
* object（物件）;type（型別） <2>:       型別物件.           (line    6)
* object（物件）;Union（聯合）:          聯合型別 Union Type.
                                                             (line    6)
* object（物件）;user-defined function（使用者定義函式）: 自訂函式.
                                                             (line    6)
* object（物件）;user-defined function（使用者定義函式） <1>: Calls.
                                                             (line  131)
* object（物件）;user-defined function（使用者定義函式） <2>: 函式定義.
                                                             (line    6)
* object（物件）;user-defined method（使用者定義方法）: Instance methods.
                                                             (line    6)
* objects（物件）;comparing（比較）:     比較運算.           (line   41)
* objobjargproc (C type):                Slot Type typedefs. (line  138)
* objobjproc (C type):                   Slot Type typedefs. (line  134)
* octal literal（八進位常數）:           Numeric literals.   (line    6)
* octal（八進位）;literals（字面值）:    數值型別 --- int、float、complex.
                                                             (line   15)
* octdigits (於 string 模組中):          字串常數.           (line   31)
* OCTOBER (於 calendar 模組中):          calendar --- 日曆相關函式.
                                                             (line  365)
* offset (SyntaxError 的屬性):           實體例外.           (line  272)
* offset (tarfile.TarInfo 的屬性):       TarInfo 物件.       (line  149)
* offset (traceback.TracebackException 的屬性): TracebackException 物件.
                                                             (line  105)
* offset (xml.parsers.expat.ExpatError 的屬性): ExpatError 例外.
                                                             (line   32)
* offset_data (tarfile.TarInfo 的屬性):  TarInfo 物件.       (line  153)
* OK (於 curses 模組中):                 Constants.          (line   13)
* OK (於 tkinter.messagebox 模組中):     tkinter messagebox --- Tkinter 訊息提示.
                                                             (line  133)
* ok_command() (tkinter.filedialog.LoadFileDialog 的方法): Native Load/Save Dialogs.
                                                             (line  140)
* ok_command() (tkinter.filedialog.SaveFileDialog 的方法): Native Load/Save Dialogs.
                                                             (line  150)
* ok_event() (tkinter.filedialog.FileDialog 的方法): Native Load/Save Dialogs.
                                                             (line  119)
* OKCANCEL (於 tkinter.messagebox 模組中): tkinter messagebox --- Tkinter 訊息提示.
                                                             (line  151)
* old_value (contextvars.Token 的屬性):  Context Variables.  (line   87)
* OleDLL (ctypes 中的類別):              Loading shared libraries.
                                                             (line   35)
* on_motion() (tkinter.dnd.DndHandler 的方法): tkinter dnd --- 拖放支援.
                                                             (line   56)
* on_release() (tkinter.dnd.DndHandler 的方法): tkinter dnd --- 拖放支援.
                                                             (line   61)
* onclick() (於 turtle 模組中):          Using screen events.
                                                             (line   56)
* ondrag() (於 turtle 模組中):           Using events.       (line   57)
* onecmd() (cmd.Cmd 的方法):             Cmd 物件.           (line   59)
* onkey() (於 turtle 模組中):            Using screen events.
                                                             (line   12)
* onkeypress() (於 turtle 模組中):       Using screen events.
                                                             (line   35)
* onkeyrelease() (於 turtle 模組中):     Using screen events.
                                                             (line   12)
* onrelease() (於 turtle 模組中):        Using events.       (line   30)
* onscreenclick() (於 turtle 模組中):    Using screen events.
                                                             (line   56)
* ontimer() (於 turtle 模組中):          Using screen events.
                                                             (line   86)
* OP (於 token 模組中):                  token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  246)
* OP_ALL (於 ssl 模組中):                常數<8>.            (line  185)
* OP_CIPHER_SERVER_PREFERENCE (於 ssl 模組中): 常數<8>.      (line  262)
* OP_ENABLE_KTLS (於 ssl 模組中):        常數<8>.            (line  317)
* OP_ENABLE_MIDDLEBOX_COMPAT (於 ssl 模組中): 常數<8>.       (line  283)
* OP_IGNORE_UNEXPECTED_EOF (於 ssl 模組中): 常數<8>.         (line  309)
* OP_LEGACY_SERVER_CONNECT (於 ssl 模組中): 常數<8>.         (line  331)
* OP_NO_COMPRESSION (於 ssl 模組中):     常數<8>.            (line  292)
* OP_NO_RENEGOTIATION (於 ssl 模組中):   常數<8>.            (line  253)
* OP_NO_SSLv2 (於 ssl 模組中):           常數<8>.            (line  192)
* OP_NO_SSLv3 (於 ssl 模組中):           常數<8>.            (line  201)
* OP_NO_TICKET (於 ssl 模組中):          常數<8>.            (line  303)
* OP_NO_TLSv1 (於 ssl 模組中):           常數<8>.            (line  210)
* OP_NO_TLSv1_1 (於 ssl 模組中):         常數<8>.            (line  221)
* OP_NO_TLSv1_2 (於 ssl 模組中):         常數<8>.            (line  231)
* OP_NO_TLSv1_3 (於 ssl 模組中):         常數<8>.            (line  241)
* OP_SINGLE_DH_USE (於 ssl 模組中):      常數<8>.            (line  269)
* OP_SINGLE_ECDH_USE (於 ssl 模組中):    常數<8>.            (line  276)
* Open (tkinter.filedialog 中的類別):    Native Load/Save Dialogs.
                                                             (line   60)
* open_binary() (於 importlib.resources 模組中): Functional API.
                                                             (line   35)
* open_code() (於 io 模組中):            高階模組介面.       (line   21)
* open_connection() (於 asyncio 模組中): 串流.               (line   41)
* open_flags (於 dbm.gnu 模組中):        dbm gnu --- GNU 資料庫管理器.
                                                             (line   68)
* open_new_tab() (webbrowser.controller 的方法): Browser Controller Objects.
                                                             (line   25)
* open_new_tab() (於 webbrowser 模組中): webbrowser --- 方便的網頁瀏覽器控制器.
                                                             (line   95)
* open_new() (webbrowser.controller 的方法): Browser Controller Objects.
                                                             (line   19)
* open_new() (於 webbrowser 模組中):     webbrowser --- 方便的網頁瀏覽器控制器.
                                                             (line   87)
* open_osfhandle() (於 msvcrt 模組中):   File Operations.    (line   44)
* open_resource() (importlib.abc.ResourceReader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  493)
* open_resource() (importlib.resources.abc.ResourceReader 的方法): importlib resources abc -- 資源的抽象基底類別.
                                                             (line   47)
* open_text() (於 importlib.resources 模組中): Functional API.
                                                             (line   51)
* open_unix_connection() (於 asyncio 模組中): 串流.          (line  105)
* open_unknown() (urllib.request.URLopener 的方法): Legacy interface.
                                                             (line  108)
* open_urlresource() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  577)
* open() (imaplib.IMAP4 的方法):         IMAP4 物件.         (line  170)
* open() (importlib.abc.Traversable 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  570)
* open() (importlib.resources.abc.Traversable 的方法): importlib resources abc -- 資源的抽象基底類別.
                                                             (line  141)
* open() (pathlib.Path 的方法):          Reading and writing files.
                                                             (line    6)
* open() (tarfile.TarFile 的類別方法):   TarFile 物件.       (line   97)
* open() (urllib.request.OpenerDirector 的方法): OpenerDirector 物件.
                                                             (line   42)
* open() (urllib.request.URLopener 的方法): Legacy interface.
                                                             (line   97)
* open() (webbrowser.controller 的方法): Browser Controller Objects.
                                                             (line   13)
* open() (zipfile.Path 的方法):          Path Objects.       (line   25)
* open() (zipfile.ZipFile 的方法):       ZipFile 物件.       (line  128)
* open() (於 bz2 模組中):                De compression of files.
                                                             (line    6)
* open() (於 codecs 模組中):             codecs --- 編解碼器註冊表和基底類別.
                                                             (line  172)
* open() (於 dbm 模組中):                dbm --- Unix "databases" 的介面.
                                                             (line   55)
* open() (於 dbm.dumb 模組中):           dbm dumb --- 可攜式 DBM 實作.
                                                             (line   29)
* open() (於 dbm.gnu 模組中):            dbm gnu --- GNU 資料庫管理器.
                                                             (line   23)
* open() (於 dbm.ndbm 模組中):           dbm ndbm --- 新資料庫管理器.
                                                             (line   33)
* open() (於 dbm.sqlite3 模組中):        dbm sqlite3 --- SQLite backend for dbm.
                                                             (line   17)
* open() (於 gzip 模組中):               gzip --- gzip 檔案的支援.
                                                             (line   28)
* open() (於 io 模組中):                 高階模組介面.       (line   12)
* open() (於 lzma 模組中):               Reading and writing compressed files.
                                                             (line    6)
* open() (於 os 模組中):                 File Descriptor Operations.
                                                             (line  373)
* open() (於 shelve 模組中):             shelve --- Python object persistence.
                                                             (line   17)
* open() (於 tarfile 模組中):            tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line   41)
* open() (於 tokenize 模組中):           Tokenizing Input.   (line  100)
* open() (於 wave 模組中):               wave --- 讀寫 WAV 檔案.
                                                             (line   18)
* open() (於 webbrowser 模組中):         webbrowser --- 方便的網頁瀏覽器控制器.
                                                             (line   68)
* OpenerDirector (urllib.request 中的類別): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  236)
* OpenKey() (於 winreg 模組中):          函式<12>.           (line  286)
* OpenKeyEx() (於 winreg 模組中):        函式<12>.           (line  286)
* openlog() (於 syslog 模組中):          syslog --- Unix syslog 函式庫例程.
                                                             (line   51)
* openpty() (於 os 模組中):              File Descriptor Operations.
                                                             (line  475)
* openpty() (於 pty 模組中):             pty --- 偽終端工具. (line   35)
* OPENSSL_VERSION (於 ssl 模組中):       常數<8>.            (line  423)
* OPENSSL_VERSION_INFO (於 ssl 模組中):  常數<8>.            (line  432)
* OPENSSL_VERSION_NUMBER (於 ssl 模組中): 常數<8>.           (line  441)
* OpenSSL;（使用於 hashlib 模組中）:     雜湊演算法.         (line   17)
* OpenSSL;（用於 ssl 模組）:             ssl --- socket 物件的 TLS/SSL 包裝器.
                                                             (line    8)
* OperationalError:                      例外<4>.            (line   57)
* operations on（操作於）;dictionary（字典）;type（型別）: Mapping Types --- dict.
                                                             (line    6)
* operations on（操作於）;integer（整數）;type（型別）: 整數型別的位元運算.
                                                             (line    6)
* operations on（操作於）;list（串列）;type（型別）: Mutable Sequence Types.
                                                             (line   16)
* operations on（操作於）;mapping（對映）;type（型別）: Mapping Types --- dict.
                                                             (line    6)
* operations on（操作於）;numeric（數值）;type（型別）: 數值型別 --- int、float、complex.
                                                             (line   85)
* operations on（操作於）;sequence（序列）;type（型別）: Common Sequence Operations.
                                                             (line   21)
* operations on（操作於）;sequence（序列）;type（型別） <1>: Mutable Sequence Types.
                                                             (line   16)
* operator（運算子）;- （減號）:         Unary arithmetic and bitwise operations.
                                                             (line   10)
* operator（運算子）;- （減號） <1>:     Binary arithmetic operations.
                                                             (line   83)
* operator（運算子）;- （減號） <2>:     數值型別 --- int、float、complex.
                                                             (line   21)
* operator（運算子）;!=:                 Comparisons.        (line    6)
* operator（運算子）;!= <1>:             比較運算.           (line    6)
* operator（運算子）;@ （在）:           Binary arithmetic operations.
                                                             (line   26)
* operator（運算子）;* （星號）:         Binary arithmetic operations.
                                                             (line   16)
* operator（運算子）;* （星號） <1>:     數值型別 --- int、float、complex.
                                                             (line   21)
* operator（運算子）;**:                 The power operator. (line    6)
* operator（運算子）;** <1>:             數值型別 --- int、float、complex.
                                                             (line   21)
* operator（運算子）;/ （斜線）:         Binary arithmetic operations.
                                                             (line   34)
* operator（運算子）;/ （斜線） <1>:     數值型別 --- int、float、complex.
                                                             (line   21)
* operator（運算子）;//:                 Binary arithmetic operations.
                                                             (line   34)
* operator（運算子）;// <1>:             數值型別 --- int、float、complex.
                                                             (line   21)
* operator（運算子）;& （和號）:         Binary bitwise operations.
                                                             (line   12)
* operator（運算子）;& （和號） <1>:     整數型別的位元運算. (line    6)
* operator（運算子）;% （百分號）:       Binary arithmetic operations.
                                                             (line   46)
* operator（運算子）;% （百分號） <1>:   數值型別 --- int、float、complex.
                                                             (line   21)
* operator（運算子）;^ （插入符號）:     Binary bitwise operations.
                                                             (line   16)
* operator（運算子）;^ （插入符號） <1>: 整數型別的位元運算. (line    6)
* operator（運算子）;+ （加號）:         Unary arithmetic and bitwise operations.
                                                             (line   14)
* operator（運算子）;+ （加號） <1>:     Binary arithmetic operations.
                                                             (line   74)
* operator（運算子）;+ （加號） <2>:     數值型別 --- int、float、complex.
                                                             (line   21)
* operator（運算子）;< （小於）:         Comparisons.        (line    6)
* operator（運算子）;< （小於） <1>:     比較運算.           (line    6)
* operator（運算子）;<<:                 Shifting operations.
                                                             (line    6)
* operator（運算子）;<< <1>:             整數型別的位元運算. (line    6)
* operator（運算子）;<=:                 Comparisons.        (line    6)
* operator（運算子）;<= <1>:             比較運算.           (line    6)
* operator（運算子）;==:                 Comparisons.        (line    6)
* operator（運算子）;== <1>:             比較運算.           (line    6)
* operator（運算子）;> （大於）:         Comparisons.        (line    6)
* operator（運算子）;> （大於） <1>:     比較運算.           (line    6)
* operator（運算子）;>=:                 Comparisons.        (line    6)
* operator（運算子）;>= <1>:             比較運算.           (line    6)
* operator（運算子）;>>:                 Shifting operations.
                                                             (line    6)
* operator（運算子）;>> <1>:             整數型別的位元運算. (line    6)
* operator（運算子）;| （垂直線）:       Binary bitwise operations.
                                                             (line   20)
* operator（運算子）;| （垂直線） <1>:   整數型別的位元運算. (line    6)
* operator（運算子）;~ （波浪號）:       Unary arithmetic and bitwise operations.
                                                             (line   18)
* operator（運算子）;~ （波浪號） <1>:   整數型別的位元運算. (line    6)
* operator（運算子）;and:                Boolean operations. (line   21)
* operator（運算子）;and <1>:            真值檢測.           (line   20)
* operator（運算子）;and <2>:            Boolean（布林）運算 --- and or not.
                                                             (line   22)
* operator（運算子）;comparison（比較）: 比較運算.           (line    6)
* operator（運算子）;in:                 Membership test operations.
                                                             (line   36)
* operator（運算子）;in <1>:             比較運算.           (line   58)
* operator（運算子）;in <2>:             Common Sequence Operations.
                                                             (line   21)
* operator（運算子）;is:                 Membership test operations.
                                                             (line   39)
* operator（運算子）;is <1>:             比較運算.           (line    6)
* operator（運算子）;is not:             Membership test operations.
                                                             (line   39)
* operator（運算子）;is not <1>:         比較運算.           (line    6)
* operator（運算子）;not:                Boolean operations. (line   18)
* operator（運算子）;not <1>:            Boolean（布林）運算 --- and or not.
                                                             (line   22)
* operator（運算子）;not in:             Membership test operations.
                                                             (line   36)
* operator（運算子）;not in <1>:         比較運算.           (line   58)
* operator（運算子）;not in <2>:         Common Sequence Operations.
                                                             (line   21)
* operator（運算子）;or:                 Boolean operations. (line   25)
* operator（運算子）;or <1>:             真值檢測.           (line   20)
* operator（運算子）;or <2>:             Boolean（布林）運算 --- and or not.
                                                             (line   22)
* operator（運算子）;overloading（多載）: Special method names.
                                                             (line    6)
* operator（運算子）;precedence（優先順序）: Operator precedence.
                                                             (line    6)
* operators（運算子）:                   Operators.          (line    6)
* opmap (於 dis 模組中):                 Opcode collections. (line   17)
* opname (於 dis 模組中):                Opcode collections. (line   13)
* OPT:                                   Debug options.      (line   39)
* optim_args_from_interpreter_flags() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  320)
* optimize (sys.flags 的屬性):           sys --- 系統特定的參數與函式.
                                                             (line  534)
* optimize() (於 pickletools 模組中):    程式化介面.         (line   26)
* optimized scope:                       術語表.             (line  907)
* OPTIMIZED_BYTECODE_SUFFIXES (於 importlib.machinery 模組中): importlib machinery -- Importers and path hooks.
                                                             (line   29)
* Option (optparse 中的類別):            Option attributes.  (line    6)
* Optional (於 typing 模組中):           特別型式.           (line   44)
* OptionConflictError:                   例外<16>.           (line   11)
* OptionError:                           例外<16>.           (line    6)
* OptionGroup (optparse 中的類別):       Grouping Options.   (line   12)
* OptionParser (optparse 中的類別):      Creating the parser.
                                                             (line    9)
* options (doctest.Example 的屬性):      Example 物件.       (line   53)
* Options (ssl 中的類別):                常數<8>.            (line  299)
* options (ssl.SSLContext 的屬性):       SSL Contexts.       (line  575)
* options() (configparser.ConfigParser 的方法): ConfigParser 物件.
                                                             (line  129)
* OptionValueError:                      例外<16>.           (line   16)
* optionxform() (configparser.ConfigParser 的方法): ConfigParser 物件.
                                                             (line  311)
* Or (ast 中的類別):                     運算式<2>.          (line   84)
* or_() (於 operator 模組中):            operator --- 標準運算子替代函式.
                                                             (line  127)
* ordered_attributes (xml.parsers.expat.xmlparser 的屬性): XMLParser 物件<2>.
                                                             (line  145)
* OrderedDict (collections 中的類別):    OrderedDict 物件.   (line   50)
* OrderedDict (typing 中的類別):         collections 中型別的別名.
                                                             (line   17)
* orig_argv (於 sys 模組中):             sys --- 系統特定的參數與函式.
                                                             (line 1269)
* origin (importlib.machinery.ModuleSpec 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  388)
* origin_req_host (urllib.request.Request 的屬性): Request Objects.
                                                             (line   30)
* origin_server (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  243)
* os_environ (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  143)
* OSError:                               實體例外.           (line  122)
* OUT_TO_DEFAULT (於 msvcrt 模組中):     Other Functions.    (line   20)
* OUT_TO_MSGBOX (於 msvcrt 模組中):      Other Functions.    (line   30)
* OUT_TO_STDERR (於 msvcrt 模組中):      Other Functions.    (line   25)
* output:                                Expression statements.
                                                             (line   17)
* output (subprocess.CalledProcessError 的屬性): Using the subprocess Module.
                                                             (line  220)
* output (subprocess.TimeoutExpired 的屬性): Using the subprocess Module.
                                                             (line  181)
* output (unittest.TestCase 的屬性):     Test cases.         (line  433)
* output_charset (email.charset.Charset 的屬性): email charset：表示字元集合.
                                                             (line   72)
* output_codec (email.charset.Charset 的屬性): email charset：表示字元集合.
                                                             (line   86)
* output_difference() (doctest.OutputChecker 的方法): OutputChecker 物件.
                                                             (line   26)
* output() (http.cookies.BaseCookie 的方法): Cookie 物件.    (line   24)
* output() (http.cookies.Morsel 的方法): Morsel 物件.        (line   65)
* OutputChecker (doctest 中的類別):      OutputChecker 物件. (line    6)
* OutputString() (http.cookies.Morsel 的方法): Morsel 物件.  (line   80)
* OutsideDestinationError:               tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  241)
* Overflow (decimal 中的類別):           Signals.            (line   67)
* OverflowError:                         實體例外.           (line  176)
* OverflowError（内建例外）:             整數物件.           (line  141)
* OverflowError（内建例外） <1>:         整數物件.           (line  186)
* OverflowError（内建例外） <2>:         整數物件.           (line  227)
* OverflowError（内建例外） <3>:         整數物件.           (line  239)
* OverflowError（内建例外） <4>:         整數物件.           (line  251)
* OverflowError（内建例外） <5>:         整數物件.           (line  264)
* overlap() (statistics.NormalDist 的方法): NormalDist 物件. (line   88)
* overlaps() (ipaddress.IPv4Network 的方法): Network objects.
                                                             (line  155)
* overlaps() (ipaddress.IPv6Network 的方法): Network objects.
                                                             (line  340)
* overlay() (curses.window 的方法):      Window Objects.     (line  429)
* overload() (於 typing 模組中):         函式與裝飾器.       (line  247)
* override() (於 typing 模組中):         函式與裝飾器.       (line  372)
* overwrite() (curses.window 的方法):    Window Objects.     (line  442)
* owner() (pathlib.Path 的方法):         Permissions and ownership.
                                                             (line    6)
* p (pdb command):                       Debugger Commands.  (line  268)
* P_ALL (於 os 模組中):                  行程管理.           (line  954)
* P_DETACH (於 os 模組中):               行程管理.           (line  689)
* P_NOWAIT (於 os 模組中):               行程管理.           (line  669)
* P_NOWAITO (於 os 模組中):              行程管理.           (line  669)
* P_OVERLAY (於 os 模組中):              行程管理.           (line  689)
* P_PGID (於 os 模組中):                 行程管理.           (line  954)
* P_PID (於 os 模組中):                  行程管理.           (line  954)
* P_PIDFD (於 os 模組中):                行程管理.           (line  954)
* P_WAIT (於 os 模組中):                 行程管理.           (line  679)
* pack_into() (struct.Struct 的方法):    Classes<2>.         (line   29)
* pack_into() (於 struct 模組中):        函式與例外.         (line   19)
* pack() (mailbox.MH 的方法):            MH 物件.            (line   67)
* pack() (struct.Struct 的方法):         Classes<2>.         (line   24)
* pack() (於 struct 模組中):             函式與例外.         (line   13)
* package variable（套件變數）;__all__:  引入模組<2>.        (line    8)
* package（套件）:                       套件.               (line    6)
* package（套件） <1>:                   site --- Site-specific configuration hook.
                                                             (line   74)
* package（套件） <2>:                   術語表.             (line  918)
* package（套件）;namespace（命名空間）: Namespace packages. (line    6)
* package（套件）;portion（部分）:       Namespace packages. (line    6)
* package（套件）;regular（一般）:       Regular packages.   (line    6)
* packed (ipaddress.IPv4Address 的屬性): Address objects.    (line   71)
* packed (ipaddress.IPv6Address 的屬性): Address objects.    (line  256)
* packing (widgets):                     The Packer.         (line    6)
* packing（打包）;binary（二進位）;data（資料）: struct --- 將位元組直譯為打包起來的二進位資料.
                                                             (line    8)
* PAGER:                                 pydoc --- 文件產生器與線上幫助系統.
                                                             (line   46)
* pair_content() (於 curses 模組中):     函式<5>.            (line  380)
* pair_number() (於 curses 模組中):      函式<5>.            (line  386)
* pairwise() (於 itertools 模組中):      Itertool 函式.      (line  372)
* Parameter (inspect 中的類別):          Introspecting callables with the Signature object.
                                                             (line  190)
* parameter（參數）:                     術語表.             (line  927)
* parameter（參數）;call semantics（呼叫語意）: Calls.       (line   25)
* parameter（參數）;function definition（函式定義）: Class Patterns.
                                                             (line  140)
* parameter（參數）;與 argument（引數）的差異: How can I pass optional or keyword parameters from one function to another?.
                                                             (line   16)
* ParameterizedMIMEHeader (email.headerregistry 中的類別): email headerregistry：自訂標頭物件.
                                                             (line  255)
* parameters (inspect.Signature 的屬性): Introspecting callables with the Signature object.
                                                             (line  105)
* params (email.headerregistry.ParameterizedMIMEHeader 的屬性): email headerregistry：自訂標頭物件.
                                                             (line  263)
* ParamSpec (ast 中的類別):              型別參數 type parameters.
                                                             (line   35)
* ParamSpec (typing 中的類別):           Building generic types and type aliases.
                                                             (line  350)
* ParamSpecArgs (於 typing 模組中):      Building generic types and type aliases.
                                                             (line  469)
* ParamSpecKwargs (於 typing 模組中):    Building generic types and type aliases.
                                                             (line  469)
* paramstyle (於 sqlite3 模組中):        Module constants.   (line   65)
* pardir (於 os 模組中):                 Miscellaneous System Information.
                                                             (line  110)
* parent (importlib.machinery.ModuleSpec 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  424)
* parent (logging.Logger 的屬性):        Logger 物件.        (line   42)
* parent (pathlib.PurePath 的屬性):      方法與屬性.         (line   91)
* parent (pyclbr.Class 的屬性):          Class Objects.      (line   28)
* parent (pyclbr.Function 的屬性):       函式物件.           (line   27)
* parent (urllib.request.BaseHandler 的屬性): BaseHandler 物件.
                                                             (line   25)
* parent_process() (於 multiprocessing 模組中): Miscellaneous<2>.
                                                             (line   41)
* parent() (tkinter.ttk.Treeview 的方法): ttk Treeview.      (line  226)
* parenthesized form:                    Parenthesized forms.
                                                             (line    6)
* parentNode (xml.dom.Node 的屬性):      Node Objects.       (line   17)
* parents (collections.ChainMap 的屬性): ChainMap 物件.      (line   52)
* parents (pathlib.PurePath 的屬性):     方法與屬性.         (line   77)
* paretovariate() (於 random 模組中):    實數分布.           (line   83)
* parse_and_bind() (於 readline 模組中): Init file.          (line    8)
* parse_args() (argparse.ArgumentParser 的方法): The parse_args method.
                                                             (line    6)
* parse_args() (optparse.OptionParser 的方法): 剖析引數<2>.  (line    9)
* PARSE_COLNAMES (於 sqlite3 模組中):    Module constants.   (line   13)
* parse_config_h() (於 sysconfig 模組中): 其他函式<3>.       (line   57)
* PARSE_DECLTYPES (於 sqlite3 模組中):   Module constants.   (line   26)
* parse_headers() (於 http.client 模組中): http client --- HTTP 協定用戶端.
                                                             (line  110)
* parse_intermixed_args() (argparse.ArgumentParser 的方法): Intermixed parsing.
                                                             (line    6)
* parse_known_args() (argparse.ArgumentParser 的方法): Partial parsing.
                                                             (line    6)
* parse_known_intermixed_args() (argparse.ArgumentParser 的方法): Intermixed parsing.
                                                             (line    9)
* parse_qs() (於 urllib.parse 模組中):   URL Parsing.        (line  152)
* parse_qsl() (於 urllib.parse 模組中):  URL Parsing.        (line  198)
* parse() (doctest.DocTestParser 的方法): DocTestParser 物件.
                                                             (line   29)
* parse() (email.parser.BytesParser 的方法): Parser API.     (line   34)
* parse() (email.parser.Parser 的方法):  Parser API.         (line   85)
* parse() (string.Formatter 的方法):     自訂字串格式.       (line   36)
* parse() (urllib.robotparser.RobotFileParser 的方法): urllib robotparser --- robots txt 的剖析器.
                                                             (line   28)
* parse() (xml.etree.ElementTree.ElementTree 的方法): ElementTree 物件.
                                                             (line   54)
* Parse() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line    8)
* parse() (xml.sax.xmlreader.XMLReader 的方法): XMLReader 物件.
                                                             (line    8)
* parse() (於 ast 模組中):               ast 輔助程式.       (line    9)
* parse() (於 xml.dom.minidom 模組中):   xml dom minidom --- 最小的 DOM 實作.
                                                             (line   36)
* parse() (於 xml.dom.pulldom 模組中):   xml dom pulldom --- 支援建置部分 DOM 樹.
                                                             (line   85)
* parse() (於 xml.etree.ElementTree 模組中): 函式<8>.        (line  176)
* parse() (於 xml.sax 模組中):           xml sax --- SAX2 剖析器支援.
                                                             (line   39)
* parseaddr() (於 email.utils 模組中):   email utils：雜項工具.
                                                             (line   57)
* parsebytes() (email.parser.BytesParser 的方法): Parser API.
                                                             (line   54)
* parsedate_to_datetime() (於 email.utils 模組中): email utils：雜項工具.
                                                             (line  130)
* parsedate_tz() (於 email.utils 模組中): email utils：雜項工具.
                                                             (line  119)
* parsedate() (於 email.utils 模組中):   email utils：雜項工具.
                                                             (line  107)
* ParseError (xml.etree.ElementTree 中的類別): 例外<14>.     (line    6)
* ParseFile() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line   16)
* ParseFlags() (於 imaplib 模組中):      imaplib --- IMAP4 協定客戶端.
                                                             (line  123)
* Parser (email.parser 中的類別):        Parser API.         (line   75)
* parser (pathlib.PurePath 的屬性):      方法與屬性.         (line    8)
* parser（剖析器）:                      詞法分析.           (line    6)
* ParserCreate() (於 xml.parsers.expat 模組中): xml parsers expat --- 使用 Expat 進行快速 XML 剖析.
                                                             (line   46)
* ParseResult (urllib.parse 中的類別):   Structured Parse Results.
                                                             (line   48)
* ParseResultBytes (urllib.parse 中的類別): Structured Parse Results.
                                                             (line   73)
* parsestr() (email.parser.Parser 的方法): Parser API.       (line   95)
* parseString() (於 xml.dom.minidom 模組中): xml dom minidom --- 最小的 DOM 實作.
                                                             (line   49)
* parseString() (於 xml.dom.pulldom 模組中): xml dom pulldom --- 支援建置部分 DOM 樹.
                                                             (line   98)
* parseString() (於 xml.sax 模組中):     xml sax --- SAX2 剖析器支援.
                                                             (line   50)
* ParsingError:                          例外<5>.            (line   65)
* partial (asyncio.IncompleteReadError 的屬性): 例外<8>.     (line   51)
* partial() (imaplib.IMAP4 的方法):      IMAP4 物件.         (line  189)
* partial() (於 functools 模組中):       functools --- 可呼叫物件上的高階函式與操作.
                                                             (line  278)
* partialmethod (functools 中的類別):    functools --- 可呼叫物件上的高階函式與操作.
                                                             (line  305)
* parties (asyncio.Barrier 的屬性):      Barrier.            (line   94)
* parties (threading.Barrier 的屬性):    Barrier Objects.    (line   93)
* partition() (bytearray 的方法):        Bytes and Bytearray Operations.
                                                             (line  185)
* partition() (bytes 的方法):            Bytes and Bytearray Operations.
                                                             (line  185)
* partition() (str 的方法):              String Methods<2>.  (line  361)
* parts (pathlib.PurePath 的屬性):       對個別組成的存取.   (line    8)
* Pass (ast 中的類別):                   陳述式.             (line  147)
* pass_() (poplib.POP3 的方法):          POP3 物件.          (line   36)
* Paste（貼上）:                         Help menu Shell and Editor.
                                                             (line   30)
* patch.dict() (於 unittest.mock 模組中): patch dict.        (line    6)
* patch.multiple() (於 unittest.mock 模組中): patch multiple.
                                                             (line    6)
* patch.object() (於 unittest.mock 模組中): patch object.    (line    6)
* patch.stopall() (於 unittest.mock 模組中): patch 方法：啟動與停止.
                                                             (line   66)
* patch() (於 test.support 模組中):      test support --- Python 測試套件的工具.
                                                             (line  647)
* patch() (於 unittest.mock 模組中):     patch.              (line    9)
* PATH:                                  Changes in the Python API<3>.
                                                             (line  144)
* PATH <1>:                              Changes in 'python' Command Behavior<2>.
                                                             (line    6)
* PATH <2>:                              Changes in 'python' Command Behavior<2>.
                                                             (line   11)
* PATH <3>:                              Changes in 'python' Command Behavior<2>.
                                                             (line   12)
* PATH <4>:                              macOS<2>.           (line   14)
* PATH <5>:                              Windows<17>.        (line   56)
* PATH <6>:                              Windows<21>.        (line   14)
* PATH <7>:                              Security<31>.       (line   16)
* PATH <8>:                              Security<31>.       (line   20)
* PATH <9>:                              模組的搜尋路徑.     (line   13)
* PATH <10>:                             可執行的 Python 腳本.
                                                             (line   11)
* PATH <11>:                             環境變數.           (line   27)
* PATH <12>:                             雜項<2>.            (line   15)
* PATH <13>:                             安裝步驟.           (line   33)
* PATH <14>:                             安裝步驟.           (line   56)
* PATH <15>:                             安裝排除使用者介面. (line   76)
* PATH <16>:                             安裝排除使用者介面. (line   80)
* PATH <17>:                             Excursus Setting environment variables.
                                                             (line   23)
* PATH <18>:                             Excursus Setting environment variables.
                                                             (line   35)
* PATH <19>:                             Finding the Python executable.
                                                             (line   14)
* PATH <20>:                             Finding the Python executable.
                                                             (line   21)
* PATH <21>:                             Finding the Python executable.
                                                             (line   22)
* PATH <22>:                             Python Launcher for Windows.
                                                             (line   13)
* PATH <23>:                             From the command-line.
                                                             (line    9)
* PATH <24>:                             Shebang Lines.      (line   53)
* PATH <25>:                             Shebang Lines.      (line   59)
* PATH <26>:                             Shebang Lines.      (line   61)
* PATH <27>:                             Shebang Lines.      (line   66)
* PATH <28>:                             Comparison to the os and os path modules.
                                                             (line   41)
* PATH <29>:                             行程管理.           (line   45)
* PATH <30>:                             行程管理.           (line   86)
* PATH <31>:                             行程管理.           (line   89)
* PATH <32>:                             行程管理.           (line   92)
* PATH <33>:                             行程管理.           (line  540)
* PATH <34>:                             行程管理.           (line  627)
* PATH <35>:                             行程管理.           (line  631)
* PATH <36>:                             行程管理.           (line  633)
* PATH <37>:                             Miscellaneous System Information.
                                                             (line  141)
* PATH <38>:                             Popen Constructor.  (line   34)
* PATH <39>:                             webbrowser --- 方便的網頁瀏覽器控制器.
                                                             (line  239)
* PATH <40>:                             虛擬環境如何運作.   (line   13)
* PATH <41>:                             虛擬環境如何運作.   (line   54)
* PATH <42>:                             虛擬環境如何運作.   (line   58)
* PATH <43>:                             site --- Site-specific configuration hook.
                                                             (line   66)
* PATH <44>:                             嵌入式Python.       (line   22)
* PATH <45>:                             嵌入式Python.       (line   28)
* PATH <46>:                             我如何使 Python script 執行在 Unix？.
                                                             (line   24)
* PATH <47>:                             我如何使 Python script 執行在 Unix？.
                                                             (line   28)
* path (http.cookiejar.Cookie 的屬性):   Cookie 物件<2>.     (line   45)
* path (http.cookies.Morsel 的屬性):     Morsel 物件.        (line   13)
* path (http.server.BaseHTTPRequestHandler 的屬性): http server — HTTP 伺服器.
                                                             (line   97)
* path (ImportError 的屬性):             實體例外.           (line   52)
* path (importlib.abc.FileLoader 的屬性): importlib abc -- Abstract base classes related to import.
                                                             (line  334)
* path (importlib.machinery.AppleFrameworkLoader 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  502)
* path (importlib.machinery.ExtensionFileLoader 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  304)
* path (importlib.machinery.FileFinder 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  173)
* path (importlib.machinery.SourceFileLoader 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  210)
* path (importlib.machinery.SourcelessFileLoader 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  254)
* path (os.DirEntry 的屬性):             Files and Directories.
                                                             (line  936)
* Path (pathlib 中的類別):               實體路徑.           (line    9)
* Path (zipfile 中的類別):               Path Objects.       (line    6)
* path (於 sys 模組中):                  sys --- 系統特定的參數與函式.
                                                             (line 1282)
* path based finder（基於路徑的尋檢器）: 術語表.             (line  990)
* path based finder（基於路徑的搜尋器）: The Path Based Finder.
                                                             (line    6)
* Path browser（路徑瀏覽器）:            File menu Shell and Editor.
                                                             (line   22)
* path entry finder（路徑項目尋檢器）:   術語表.             (line  975)
* path entry hook（路徑項目鉤）:         術語表.             (line  984)
* path entry（路徑項目）:                術語表.             (line  969)
* path hooks:                            Import hooks.       (line    6)
* path_hook() (importlib.machinery.FileFinder 的類別方法): importlib machinery -- Importers and path hooks.
                                                             (line  188)
* path_hooks (於 sys 模組中):            sys --- 系統特定的參數與函式.
                                                             (line 1315)
* path_importer_cache (於 sys 模組中):   sys --- 系統特定的參數與函式.
                                                             (line 1324)
* path_mtime() (importlib.abc.SourceLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  400)
* path_return_ok() (http.cookiejar.CookiePolicy 的方法): CookiePolicy 物件.
                                                             (line   56)
* path_stats() (importlib.abc.SourceLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  378)
* path_stats() (importlib.machinery.SourceFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  219)
* path-like object（類路徑物件）:        術語表.             (line  995)
* Path.stem (於 zipfile 模組中):         Path Objects.       (line   76)
* Path.suffix (於 zipfile 模組中):       Path Objects.       (line   69)
* Path.suffixes (於 zipfile 模組中):     Path Objects.       (line   82)
* path() (於 importlib.resources 模組中): Functional API.    (line  110)
* path（sys 模組中）:                    嵌入式Python.       (line   10)
* path（sys 模組中） <1>:                Initializing and finalizing the interpreter.
                                                             (line    7)
* path（sys 模組中） <2>:                Process-wide parameters.
                                                             (line  134)
* path（路徑）;configuration（設定）;file（檔案）: site --- Site-specific configuration hook.
                                                             (line   74)
* path（路徑）;operations（操作）:       pathlib --- 物件導向檔案系統路徑.
                                                             (line   10)
* path（路徑）;operations（操作） <1>:   os path --- 常見的路徑名操作.
                                                             (line    9)
* pathconf_names (於 os 模組中):         Files and Directories.
                                                             (line  651)
* pathconf() (於 os 模組中):             Files and Directories.
                                                             (line  627)
* PathEntryFinder (importlib.abc 中的類別): importlib abc -- Abstract base classes related to import.
                                                             (line   59)
* PATHEXT:                               Other Improvements<2>.
                                                             (line   30)
* PATHEXT <1>:                           Library<35>.        (line  138)
* PATHEXT <2>:                           安裝排除使用者介面. (line   76)
* PATHEXT <3>:                           安裝排除使用者介面. (line   80)
* PathFinder (importlib.machinery 中的類別): importlib machinery -- Importers and path hooks.
                                                             (line  103)
* PathLike (os 中的類別):                行程參數.           (line  120)
* pathname2url() (於 urllib.request 模組中): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  133)
* pathsep (於 os 模組中):                Miscellaneous System Information.
                                                             (line  138)
* Pattern (re 中的類別):                 Regular Expression Objects.
                                                             (line    6)
* pattern (re.Pattern 的屬性):           Regular Expression Objects.
                                                             (line  123)
* pattern (re.PatternError 的屬性):      Exceptions.         (line   19)
* Pattern (typing 中的類別):             Aliases to other concrete types.
                                                             (line    6)
* pattern matching（模式匹配）:          The match statement.
                                                             (line    6)
* PatternError:                          Exceptions.         (line    6)
* pause_reading() (asyncio.ReadTransport 的方法): Read-only Transports.
                                                             (line   12)
* pause_writing() (asyncio.BaseProtocol 的方法): Base Protocol.
                                                             (line   40)
* pause() (於 signal 模組中):            模組內容<5>.        (line  312)
* PAX_FORMAT (於 tarfile 模組中):        tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  324)
* pax_headers (tarfile.TarFile 的屬性):  TarFile 物件.       (line  327)
* pax_headers (tarfile.TarInfo 的屬性):  TarInfo 物件.       (line  161)
* pbkdf2_hmac() (於 hashlib 模組中):     密鑰的生成.         (line   11)
* pd() (於 turtle 模組中):               Drawing state.      (line    6)
* Pdb (pdb 中的類別):                    pdb --- The Python Debugger.
                                                             (line  181)
* Pdb（pdb 中的類別）:                   pdb --- The Python Debugger.
                                                             (line   17)
* pdf() (statistics.NormalDist 的方法):  NormalDist 物件.    (line   63)
* peek() (bz2.BZ2File 的方法):           De compression of files.
                                                             (line   73)
* peek() (gzip.GzipFile 的方法):         gzip --- gzip 檔案的支援.
                                                             (line  128)
* peek() (io.BufferedReader 的方法):     Buffered Streams.   (line   75)
* peek() (lzma.LZMAFile 的方法):         Reading and writing compressed files.
                                                             (line   85)
* peek() (weakref.finalize 的方法):      weakref --- 弱參照. (line  249)
* PEM_cert_to_DER_cert() (於 ssl 模組中): 認證處理.          (line   53)
* pen() (於 turtle 模組中):              Drawing state.      (line   33)
* pencolor() (於 turtle 模組中):         Color control.      (line    6)
* pending (ssl.MemoryBIO 的屬性):        Memory BIO Support<2>.
                                                             (line  139)
* pending() (ssl.SSLSocket 的方法):      SSL Sockets.        (line  321)
* PendingDeprecationWarning:             警告.               (line   27)
* pendown() (於 turtle 模組中):          Drawing state.      (line    6)
* pensize() (於 turtle 模組中):          Drawing state.      (line   18)
* penup() (於 turtle 模組中):            Drawing state.      (line   12)
* PEP:                                   術語表.             (line 1005)
* PERCENT (於 token 模組中):             token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  122)
* PERCENTEQUAL (於 token 模組中):        token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  186)
* perf_counter_ns() (於 time 模組中):    函式<4>.            (line  208)
* perf_counter() (於 time 模組中):       函式<4>.            (line  188)
* perm() (於 math 模組中):               數論與表現函式.     (line  204)
* PermissionError:                       作業系統例外.       (line   89)
* permutations() (於 itertools 模組中):  Itertool 函式.      (line  391)
* persistence（持續性）:                 pickle --- Python 物件序列化.
                                                             (line    8)
* persistent_id() (pickle.Pickler 的方法): 模組介面.         (line  160)
* persistent_id（pickle 協定）:          Persistence of External Objects.
                                                             (line    6)
* persistent_load() (pickle.Unpickler 的方法): 模組介面.     (line  278)
* persistent_load（pickle 協定）:        Persistence of External Objects.
                                                             (line    6)
* persistent（持續）;objects（物件）:    pickle --- Python 物件序列化.
                                                             (line    8)
* PF_CAN (於 socket 模組中):             常數<7>.            (line  125)
* PF_DIVERT (於 socket 模組中):          常數<7>.            (line  198)
* PF_PACKET (於 socket 模組中):          常數<7>.            (line  208)
* PF_RDS (於 socket 模組中):             常數<7>.            (line  230)
* pformat() (pprint.PrettyPrinter 的方法): PrettyPrinter 物件.
                                                             (line   50)
* pformat() (於 pprint 模組中):          函式<3>.            (line   76)
* pgettext() (gettext.GNUTranslations 的方法): The GNUTranslations class.
                                                             (line   68)
* pgettext() (gettext.NullTranslations 的方法): The NullTranslations class.
                                                             (line   47)
* pgettext() (於 gettext 模組中):        GNU gettext API.    (line   63)
* PGO (於 test.support 模組中):          test support --- Python 測試套件的工具.
                                                             (line  106)
* phase() (於 cmath 模組中):             轉換到極座標和從極座標做轉換.
                                                             (line   16)
* Philbrick, Geoff:                      Keyword Parameters for Extension Functions.
                                                             (line   25)
* physical line（物理列）:               Logical lines.      (line    6)
* physical line（物理列） <1>:           Explicit line joining.
                                                             (line    6)
* physical line（物理列） <2>:           String and Bytes literals.
                                                             (line   74)
* pi (於 cmath 模組中):                  常數<3>.            (line    6)
* pi (於 math 模組中):                   常數<2>.            (line    6)
* pi() (xml.etree.ElementTree.TreeBuilder 的方法): TreeBuilder 物件.
                                                             (line   56)
* pickle() (於 copyreg 模組中):          copyreg --- 註冊 pickle 支援函式.
                                                             (line   20)
* PickleBuffer (pickle 中的類別):        模組介面.           (line  308)
* PickleError:                           模組介面.           (line   95)
* Pickler (pickle 中的類別):             模組介面.           (line  121)
* pickletools 命令列選項; -a:            命令列選項<4>.      (line    6)
* pickletools 命令列選項; -annotate:     命令列選項<4>.      (line    6)
* pickletools 命令列選項; -indentlevel:  命令列選項<4>.      (line   14)
* pickletools 命令列選項; -l:            命令列選項<4>.      (line   14)
* pickletools 命令列選項; -m:            命令列選項<4>.      (line   18)
* pickletools 命令列選項; -memo:         命令列選項<4>.      (line   18)
* pickletools 命令列選項; -o:            命令列選項<4>.      (line   10)
* pickletools 命令列選項; -output:       命令列選項<4>.      (line   10)
* pickletools 命令列選項; -p:            命令列選項<4>.      (line   22)
* pickletools 命令列選項; -preamble:     命令列選項<4>.      (line   22)
* pickling;objects（物件）:              pickle --- Python 物件序列化.
                                                             (line    8)
* PicklingError:                         模組介面.           (line  100)
* pid (asyncio.subprocess.Process 的屬性): Interacting with Subprocesses.
                                                             (line  137)
* pid (multiprocessing.Process 的屬性):  Process 與例外.     (line  121)
* pid (subprocess.Popen 的屬性):         Popen Objects.      (line  142)
* PIDFD_NONBLOCK (於 os 模組中):         行程管理.           (line  373)
* pidfd_open() (於 os 模組中):           行程管理.           (line  361)
* pidfd_send_signal() (於 signal 模組中): 模組內容<5>.       (line  330)
* PidfdChildWatcher (asyncio 中的類別):  Process Watchers.   (line  156)
* PIP_USER:                              Windows<38>.        (line  102)
* PIPE (於 subprocess 模組中):           Using the subprocess Module.
                                                             (line  149)
* PIPE_BUF (於 select 模組中):           select --- 等待 I/O 完成.
                                                             (line  160)
* pipe_connection_lost() (asyncio.SubprocessProtocol 的方法): Subprocess Protocols.
                                                             (line   19)
* pipe_data_received() (asyncio.SubprocessProtocol 的方法): Subprocess Protocols.
                                                             (line   10)
* PIPE_MAX_SIZE (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  110)
* Pipe() (於 multiprocessing 模組中):    Pipes and Queues.   (line   79)
* pipe() (於 os 模組中):                 File Descriptor Operations.
                                                             (line  486)
* pipe2() (於 os 模組中):                File Descriptor Operations.
                                                             (line  496)
* placeholder (textwrap.TextWrapper 的屬性): textwrap --- 文字包裝與填充.
                                                             (line  277)
* platform (於 sys 模組中):              sys --- 系統特定的參數與函式.
                                                             (line 1334)
* platform() (於 platform 模組中):       跨平台.             (line   40)
* platform（sys 模組中）:                Process-wide parameters.
                                                             (line  171)
* platlibdir (於 sys 模組中):            sys --- 系統特定的參數與函式.
                                                             (line 1399)
* PlaySound() (於 winsound 模組中):      winsound --- Windows 的聲音播放介面.
                                                             (line   20)
* plist;file（檔案）:                    plistlib --- 產生和剖析 Apple plist 檔案.
                                                             (line    8)
* plock() (於 os 模組中):                行程管理.           (line  385)
* PLUS (於 token 模組中):                token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   82)
* plus() (decimal.Context 的方法):       Context objects.    (line  431)
* plus（加）:                            Unary arithmetic and bitwise operations.
                                                             (line   14)
* PLUSEQUAL (於 token 模組中):           token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  170)
* pm() (於 pdb 模組中):                  pdb --- The Python Debugger.
                                                             (line  171)
* POINTER() (於 ctypes 模組中):          Utility functions.  (line  146)
* pointer() (於 ctypes 模組中):          Utility functions.  (line  152)
* polar() (於 cmath 模組中):             轉換到極座標和從極座標做轉換.
                                                             (line   31)
* Policy (email.policy 中的類別):        email policy Policy Objects.
                                                             (line  129)
* poll() (multiprocessing.connection.Connection 的方法): Connection Objects.
                                                             (line   42)
* poll() (select.devpoll 的方法):        /dev/poll Polling Objects.
                                                             (line   65)
* poll() (select.epoll 的方法):          Edge and Level Trigger Polling epoll Objects.
                                                             (line   96)
* poll() (select.poll 的方法):           Polling Objects.    (line   77)
* poll() (subprocess.Popen 的方法):      Popen Objects.      (line    8)
* poll() (於 select 模組中):             select --- 等待 I/O 完成.
                                                             (line   88)
* PollSelector (selectors 中的類別):     Classes<3>.         (line  171)
* Pool (multiprocessing.pool 中的類別):  Process Pools.      (line    9)
* pop_all() (contextlib.ExitStack 的方法): Utilities.        (line  594)
* POP_BLOCK (opcode):                    Python Bytecode Instructions.
                                                             (line 1393)
* POP_EXCEPT (opcode):                   Python Bytecode Instructions.
                                                             (line  433)
* POP_JUMP_IF_FALSE (opcode):            Python Bytecode Instructions.
                                                             (line  854)
* POP_JUMP_IF_NONE (opcode):             Python Bytecode Instructions.
                                                             (line  880)
* POP_JUMP_IF_NOT_NONE (opcode):         Python Bytecode Instructions.
                                                             (line  868)
* POP_JUMP_IF_TRUE (opcode):             Python Bytecode Instructions.
                                                             (line  840)
* pop_source() (shlex.shlex 的方法):     shlex 物件.         (line   63)
* POP_TOP (opcode):                      Python Bytecode Instructions.
                                                             (line  131)
* pop() (array.array 的方法):            array --- 高效率的數值型陣列.
                                                             (line  189)
* pop() (collections.deque 的方法):      deque 物件.         (line   79)
* pop() (dict 的方法):                   Mapping Types --- dict.
                                                             (line  171)
* pop() (frozenset 的方法):              Set Types --- set frozenset.
                                                             (line  208)
* pop() (mailbox.Mailbox 的方法):        Mailbox 物件.       (line  216)
* pop()（序列方法）:                     Mutable Sequence Types.
                                                             (line   16)
* POP3 (poplib 中的類別):                poplib --- POP3 協定用戶端.
                                                             (line   34)
* POP3_SSL (poplib 中的類別):            poplib --- POP3 協定用戶端.
                                                             (line   53)
* POP3;protocol（協定）:                 poplib --- POP3 協定用戶端.
                                                             (line    8)
* Popen (subprocess 中的類別):           Popen Constructor.  (line   11)
* popen() (於 os 模組):                  select --- 等待 I/O 完成.
                                                             (line  141)
* popen() (於 os 模組中):                行程管理.           (line  392)
* popen() （於 os 模組中）:              I/O objects also known as file objects.
                                                             (line    6)
* popitem() (collections.OrderedDict 的方法): OrderedDict 物件.
                                                             (line   57)
* popitem() (dict 的方法):               Mapping Types --- dict.
                                                             (line  177)
* popitem() (mailbox.Mailbox 的方法):    Mailbox 物件.       (line  225)
* popleft() (collections.deque 的方法):  deque 物件.         (line   84)
* port (http.cookiejar.Cookie 的屬性):   Cookie 物件<2>.     (line   36)
* port_specified (http.cookiejar.Cookie 的屬性): Cookie 物件<2>.
                                                             (line   81)
* portion（部分）:                       術語表.             (line 1018)
* pos (json.JSONDecodeError 的屬性):     例外<12>.           (line   18)
* pos (re.Match 的屬性):                 Match Objects.      (line  178)
* pos (re.PatternError 的屬性):          Exceptions.         (line   23)
* pos() (於 operator 模組中):            operator --- 標準運算子替代函式.
                                                             (line  132)
* pos() (於 turtle 模組中):              Tell Turtle's state.
                                                             (line    6)
* position (xml.etree.ElementTree.ParseError 的屬性): 例外<14>.
                                                             (line   20)
* position() (於 turtle 模組中):         Tell Turtle's state.
                                                             (line    6)
* positional argument（位置引數）:       術語表.             (line 1024)
* Positions (dis 中的類別):              Python Bytecode Instructions.
                                                             (line  102)
* positions (inspect.FrameInfo 的屬性):  直譯器堆疊.         (line   42)
* positions (inspect.Traceback 的屬性):  直譯器堆疊.         (line   82)
* Positions.col_offset (於 dis 模組中):  Python Bytecode Instructions.
                                                             (line  111)
* Positions.end_col_offset (於 dis 模組中): Python Bytecode Instructions.
                                                             (line  113)
* Positions.end_lineno (於 dis 模組中):  Python Bytecode Instructions.
                                                             (line  109)
* Positions.lineno (於 dis 模組中):      Python Bytecode Instructions.
                                                             (line  107)
* POSIX Shared Memory（POSIX 共享記憶體）: multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取.
                                                             (line   10)
* POSIX_FADV_DONTNEED (於 os 模組中):    File Descriptor Operations.
                                                             (line  530)
* POSIX_FADV_NOREUSE (於 os 模組中):     File Descriptor Operations.
                                                             (line  530)
* POSIX_FADV_NORMAL (於 os 模組中):      File Descriptor Operations.
                                                             (line  530)
* POSIX_FADV_RANDOM (於 os 模組中):      File Descriptor Operations.
                                                             (line  530)
* POSIX_FADV_SEQUENTIAL (於 os 模組中):  File Descriptor Operations.
                                                             (line  530)
* POSIX_FADV_WILLNEED (於 os 模組中):    File Descriptor Operations.
                                                             (line  530)
* posix_fadvise() (於 os 模組中):        File Descriptor Operations.
                                                             (line  516)
* posix_fallocate() (於 os 模組中):      File Descriptor Operations.
                                                             (line  507)
* posix_openpt() (於 os 模組中):         File Descriptor Operations.
                                                             (line  557)
* POSIX_SPAWN_CLOSE (於 os 模組中):      行程管理.           (line  459)
* POSIX_SPAWN_CLOSEFROM (於 os 模組中):  行程管理.           (line  471)
* POSIX_SPAWN_DUP2 (於 os 模組中):       行程管理.           (line  465)
* POSIX_SPAWN_OPEN (於 os 模組中):       行程管理.           (line  453)
* posix_spawn() (於 os 模組中):          行程管理.           (line  430)
* posix_spawnp() (於 os 模組中):         行程管理.           (line  532)
* POSIX;I/O control（I/O 控制）:         termios --- POSIX 風格 tty 控制.
                                                             (line    6)
* PosixPath (pathlib 中的類別):          實體路徑.           (line   20)
* post_handshake_auth (ssl.SSLContext 的屬性): SSL Contexts. (line  593)
* post_mortem() (於 pdb 模組中):         pdb --- The Python Debugger.
                                                             (line  164)
* post_setup() (venv.EnvBuilder 的方法): API<2>.             (line  170)
* postcmd() (cmd.Cmd 的方法):            Cmd 物件.           (line  104)
* postloop() (cmd.Cmd 的方法):           Cmd 物件.           (line  122)
* Pow (ast 中的類別):                    運算式<2>.          (line   52)
* pow() (於 math 模組中):                Power and logarithmic functions.
                                                             (line   72)
* pow() (於 operator 模組中):            operator --- 標準運算子替代函式.
                                                             (line  137)
* power() (decimal.Context 的方法):      Context objects.    (line  437)
* power（次方）;operation（操作）:       The power operator. (line    6)
* pp (pdb command):                      Debugger Commands.  (line  276)
* pp() (於 pprint 模組中):               函式<3>.            (line    6)
* pprint() (pprint.PrettyPrinter 的方法): PrettyPrinter 物件.
                                                             (line   56)
* pprint() (於 pprint 模組中):           函式<3>.            (line   67)
* prcal() (於 calendar 模組中):          calendar --- 日曆相關函式.
                                                             (line  310)
* pread() (於 os 模組中):                File Descriptor Operations.
                                                             (line  544)
* preadv() (於 os 模組中):               File Descriptor Operations.
                                                             (line  575)
* preamble (email.message.EmailMessage 的屬性): email message：表示電子郵件訊息.
                                                             (line  677)
* preamble (email.message.Message 的屬性): email message Message Representing an email message using the compat32 API.
                                                             (line  688)
* precmd() (cmd.Cmd 的方法):             Cmd 物件.           (line   94)
* prefix (xml.dom.Attr 的屬性):          Attr Objects.       (line   18)
* prefix (xml.dom.Node 的屬性):          Node Objects.       (line   69)
* prefix (zipimport.zipimporter 的屬性): zipimporter 物件.   (line  100)
* prefix (於 sys 模組中):                sys --- 系統特定的參數與函式.
                                                             (line 1424)
* PREFIXES (於 site 模組中):             模組內容<10>.       (line    6)
* prefixlen (ipaddress.IPv4Network 的屬性): Network objects. (line  132)
* prefixlen (ipaddress.IPv6Network 的屬性): Network objects. (line  329)
* preloop() (cmd.Cmd 的方法):            Cmd 物件.           (line  116)
* prepare_class() (於 types 模組中):     Dynamic Type Creation.
                                                             (line   22)
* prepare_input_source() (於 xml.sax.saxutils 模組中): xml sax saxutils --- SAX 工具程式.
                                                             (line   81)
* prepare() (graphlib.TopologicalSorter 的方法): graphlib —-- 使用類圖 graph-like 結構進行操作的功能.
                                                             (line   87)
* prepare() (logging.handlers.QueueHandler 的方法): QueueHandler.
                                                             (line   45)
* prepare() (logging.handlers.QueueListener 的方法): QueueListener.
                                                             (line   57)
* PrepareProtocol (sqlite3 中的類別):    PrepareProtocol 物件.
                                                             (line    6)
* PrettyPrinter (pprint 中的類別):       PrettyPrinter 物件. (line    6)
* prev() (tkinter.ttk.Treeview 的方法):  ttk Treeview.       (line  231)
* previousSibling (xml.dom.Node 的屬性): Node Objects.       (line   32)
* primary（主要）:                       Primaries.          (line    6)
* print_callees() (pstats.Stats 的方法): The Stats Class.    (line  217)
* print_callers() (pstats.Stats 的方法): The Stats Class.    (line  196)
* print_exc() (timeit.Timer 的方法):     Python 介面.        (line  108)
* print_exc() (於 traceback 模組中):     traceback --- 列印或取得堆疊回溯 stack traceback.
                                                             (line   86)
* print_exception() (於 traceback 模組中): traceback --- 列印或取得堆疊回溯 stack traceback.
                                                             (line   52)
* print_help() (argparse.ArgumentParser 的方法): Printing help.
                                                             (line   16)
* print_last() (於 traceback 模組中):    traceback --- 列印或取得堆疊回溯 stack traceback.
                                                             (line   91)
* print_stack() (asyncio.Task 的方法):   Task Object.        (line  143)
* print_stack() (於 traceback 模組中):   traceback --- 列印或取得堆疊回溯 stack traceback.
                                                             (line   97)
* print_stats() (profile.Profile 的方法): profile and cProfile Module Reference.
                                                             (line   91)
* print_stats() (pstats.Stats 的方法):   The Stats Class.    (line  164)
* print_tb() (於 traceback 模組中):      traceback --- 列印或取得堆疊回溯 stack traceback.
                                                             (line   34)
* print_usage() (argparse.ArgumentParser 的方法): Printing help.
                                                             (line   10)
* print_usage() (optparse.OptionParser 的方法): 其他方法.    (line   15)
* print_version() (optparse.OptionParser 的方法): Printing a version string.
                                                             (line   26)
* print_warning() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  408)
* print() (traceback.TracebackException 的方法): TracebackException 物件.
                                                             (line  131)
* print() （內建函式）;__str__() （物件方法）: Basic customization.
                                                             (line  130)
* printable (於 string 模組中):          字串常數.           (line   40)
* printdir() (zipfile.ZipFile 的方法):   ZipFile 物件.       (line  233)
* printf 風格格式化:                     printf-style String Formatting.
                                                             (line    6)
* printf 風格格式化 <1>:                 printf-style Bytes Formatting.
                                                             (line    6)
* PRIO_DARWIN_BG (於 os 模組中):         行程參數.           (line  303)
* PRIO_DARWIN_NONUI (於 os 模組中):      行程參數.           (line  303)
* PRIO_DARWIN_PROCESS (於 os 模組中):    行程參數.           (line  303)
* PRIO_DARWIN_THREAD (於 os 模組中):     行程參數.           (line  303)
* PRIO_PGRP (於 os 模組中):              行程參數.           (line  292)
* PRIO_PROCESS (於 os 模組中):           行程參數.           (line  292)
* PRIO_USER (於 os 模組中):              行程參數.           (line  292)
* PriorityQueue (asyncio 中的類別):      Priority Queue（優先佇列）.
                                                             (line    6)
* PriorityQueue (queue 中的類別):        queue --- 同步佇列 synchronized queue 類別.
                                                             (line   40)
* private;names:                         Identifiers Names.  (line   14)
* prlimit() (於 resource 模組中):        Resource Limits.    (line   56)
* prmonth() (calendar.TextCalendar 的方法): calendar --- 日曆相關函式.
                                                             (line  121)
* prmonth() (於 calendar 模組中):        calendar --- 日曆相關函式.
                                                             (line  301)
* ProactorEventLoop (asyncio 中的類別):  事件迴圈實作.       (line   31)
* procedure;call:                        Expression statements.
                                                             (line   17)
* Process (multiprocessing 中的類別):    Process 與例外.     (line    6)
* process_cpu_count() (於 os 模組中):    Miscellaneous System Information.
                                                             (line   60)
* process_exited() (asyncio.SubprocessProtocol 的方法): Subprocess Protocols.
                                                             (line   26)
* process_request() (socketserver.BaseServer 的方法): Server Objects.
                                                             (line  156)
* process_time_ns() (於 time 模組中):    函式<4>.            (line  225)
* process_time() (於 time 模組中):       函式<4>.            (line  214)
* process_tokens() (於 tabnanny 模組中): tabnanny --- 偵測不良縮排.
                                                             (line   39)
* process;group（群組）:                 行程參數.           (line  193)
* process;group（群組） <1>:             行程參數.           (line  255)
* process;id:                            行程參數.           (line  261)
* process;id of parent:                  行程參數.           (line  268)
* process;killing:                       行程管理.           (line  325)
* process;killing <1>:                   行程管理.           (line  348)
* process;scheduling priority（排程優先權）: 行程參數.       (line  279)
* process;scheduling priority（排程優先權） <1>: 行程參數.   (line  467)
* process;signalling（信號）:            行程管理.           (line  325)
* process;signalling（信號） <1>:        行程管理.           (line  348)
* process() (logging.LoggerAdapter 的方法): LoggerAdapter 物件.
                                                             (line   21)
* ProcessError:                          Process 與例外.     (line  228)
* processes, light-weight（行程，輕量級）: _thread --- 低階執行緒 API.
                                                             (line    6)
* processingInstruction() (xml.sax.handler.ContentHandler 的方法): ContentHandler 物件.
                                                             (line  164)
* ProcessingInstruction() (於 xml.etree.ElementTree 模組中): 函式<8>.
                                                             (line  183)
* ProcessingInstructionHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line  274)
* ProcessLookupError:                    作業系統例外.       (line   98)
* processor time（處理器時間）:          函式<4>.            (line  216)
* processor time（處理器時間） <1>:      函式<4>.            (line  516)
* processor() (於 platform 模組中):      跨平台.             (line   57)
* ProcessPoolExecutor (concurrent.futures 中的類別): ProcessPoolExecutor.
                                                             (line   19)
* prod() (於 math 模組中):               數論與表現函式.     (line  220)
* product() (於 itertools 模組中):       Itertool 函式.      (line  438)
* Profile (profile 中的類別):            profile and cProfile Module Reference.
                                                             (line   35)
* profile function:                      threading --- 基於執行緒的平行性.
                                                             (line  184)
* profile function <1>:                  threading --- 基於執行緒的平行性.
                                                             (line  202)
* profile function <2>:                  sys --- 系統特定的參數與函式.
                                                             (line  902)
* profile function <3>:                  sys --- 系統特定的參數與函式.
                                                             (line 1471)
* PROFILE_TASK:                          Build<12>.          (line   13)
* PROFILE_TASK <1>:                      Performance options.
                                                             (line   12)
* profiler:                              sys --- 系統特定的參數與函式.
                                                             (line  902)
* profiler <1>:                          sys --- 系統特定的參數與函式.
                                                             (line 1471)
* profiling, deterministic:              Introduction to the profilers.
                                                             (line    6)
* program（程式）:                       完整的 Python 程式. (line    6)
* ProgrammingError:                      例外<4>.            (line   78)
* Progressbar (tkinter.ttk 中的類別):    ttk Progressbar.    (line    6)
* prompt (cmd.Cmd 的屬性):               Cmd 物件.           (line  131)
* prompt_user_passwd() (urllib.request.FancyURLopener 的方法): Legacy interface.
                                                             (line  182)
* prompts, interpreter（提示、直譯器）:  sys --- 系統特定的參數與函式.
                                                             (line 1440)
* propagate (logging.Logger 的屬性):     Logger 物件.        (line   50)
* property (內建類別):                   內建函式.           (line 1401)
* property list（屬性清單）:             plistlib --- 產生和剖析 Apple plist 檔案.
                                                             (line    8)
* property_declaration_handler (於 xml.sax.handler 模組中): xml sax handler --- SAX 處理函式的基本類別.
                                                             (line  106)
* property_dom_node (於 xml.sax.handler 模組中): xml sax handler --- SAX 處理函式的基本類別.
                                                             (line  113)
* property_lexical_handler (於 xml.sax.handler 模組中): xml sax handler --- SAX 處理函式的基本類別.
                                                             (line   99)
* property_xml_string (於 xml.sax.handler 模組中): xml sax handler --- SAX 處理函式的基本類別.
                                                             (line  120)
* property() (於 enum 模組中):           通用項目與裝飾器.   (line   36)
* PropertyMock (unittest.mock 中的類別): Mock 類別.          (line  578)
* prot_c() (ftplib.FTP_TLS 的方法):      FTP_TLS 物件.       (line  103)
* prot_p() (ftplib.FTP_TLS 的方法):      FTP_TLS 物件.       (line   99)
* proto (socket.socket 的屬性):          Socket 物件.        (line  624)
* Protocol (asyncio 中的類別):           Base Protocols.     (line   10)
* protocol (ssl.SSLContext 的屬性):      SSL Contexts.       (line  612)
* Protocol (typing 中的類別):            Other special directives.
                                                             (line  129)
* PROTOCOL_SSLv23 (於 ssl 模組中):       常數<8>.            (line  141)
* PROTOCOL_SSLv3 (於 ssl 模組中):        常數<8>.            (line  147)
* PROTOCOL_TLS (於 ssl 模組中):          常數<8>.            (line  116)
* PROTOCOL_TLS_CLIENT (於 ssl 模組中):   常數<8>.            (line  127)
* PROTOCOL_TLS_SERVER (於 ssl 模組中):   常數<8>.            (line  135)
* PROTOCOL_TLSv1 (於 ssl 模組中):        常數<8>.            (line  161)
* PROTOCOL_TLSv1_1 (於 ssl 模組中):      常數<8>.            (line  167)
* PROTOCOL_TLSv1_2 (於 ssl 模組中):      常數<8>.            (line  176)
* protocol_version (http.server.BaseHTTPRequestHandler 的屬性): http server — HTTP 伺服器.
                                                             (line  162)
* PROTOCOL_VERSION (imaplib.IMAP4 的屬性): IMAP4 物件.       (line  393)
* protocol（協定）;context management（情境管理）: 情境管理器型別.
                                                             (line    6)
* protocol（協定）;iterator（疊代器）:   疊代器型別.         (line    6)
* ProtocolError (xmlrpc.client 中的類別): ProtocolError 物件.
                                                             (line    6)
* provisional API（暫行 API）:           術語表.             (line 1028)
* provisional package（暫行套件）:       術語表.             (line 1042)
* proxy() (於 weakref 模組中):           weakref --- 弱參照. (line  105)
* proxyauth() (imaplib.IMAP4 的方法):    IMAP4 物件.         (line  194)
* ProxyBasicAuthHandler (urllib.request 中的類別): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  333)
* ProxyDigestAuthHandler (urllib.request 中的類別): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  365)
* ProxyHandler (urllib.request 中的類別): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  260)
* ProxyType (於 weakref 模組中):         weakref --- 弱參照. (line  274)
* ProxyTypes (於 weakref 模組中):        weakref --- 弱參照. (line  282)
* pryear() (calendar.TextCalendar 的方法): calendar --- 日曆相關函式.
                                                             (line  134)
* ps1 (於 sys 模組中):                   sys --- 系統特定的參數與函式.
                                                             (line 1437)
* ps2 (於 sys 模組中):                   sys --- 系統特定的參數與函式.
                                                             (line 1437)
* pstdev() (於 statistics 模組中):       函式細節.           (line  344)
* pthread_getcpuclockid() (於 time 模組中): 函式<4>.         (line   19)
* pthread_kill() (於 signal 模組中):     模組內容<5>.        (line  343)
* pthread_sigmask() (於 signal 模組中):  模組內容<5>.        (line  373)
* pthreads:                              _thread --- 低階執行緒 API.
                                                             (line   14)
* pthreads (sys._emscripten_info 的屬性): sys --- 系統特定的參數與函式.
                                                             (line  354)
* ptsname() (於 os 模組中):              File Descriptor Operations.
                                                             (line  634)
* pu() (於 turtle 模組中):               Drawing state.      (line   12)
* publicId (xml.dom.DocumentType 的屬性): DocumentType 物件. (line   17)
* PullDom (xml.dom.pulldom 中的類別):    xml dom pulldom --- 支援建置部分 DOM 樹.
                                                             (line   77)
* punctuation (於 string 模組中):        字串常數.           (line   35)
* punctuation_chars (shlex.shlex 的屬性): shlex 物件.        (line  182)
* PurePath (pathlib 中的類別):           純路徑.             (line    9)
* PurePosixPath (pathlib 中的類別):      純路徑.             (line   67)
* PureWindowsPath (pathlib 中的類別):    純路徑.             (line   77)
* purge() (於 re 模組中):                Functions.          (line  288)
* Purpose.CLIENT_AUTH (於 ssl 模組中):   常數<8>.            (line  479)
* Purpose.SERVER_AUTH (於 ssl 模組中):   常數<8>.            (line  471)
* push_async_callback() (contextlib.AsyncExitStack 的方法): Utilities.
                                                             (line  645)
* push_async_exit() (contextlib.AsyncExitStack 的方法): Utilities.
                                                             (line  640)
* PUSH_EXC_INFO (opcode):                Python Bytecode Instructions.
                                                             (line  452)
* PUSH_NULL (opcode):                    Python Bytecode Instructions.
                                                             (line 1073)
* push_source() (shlex.shlex 的方法):    shlex 物件.         (line   56)
* push_token() (shlex.shlex 的方法):     shlex 物件.         (line   16)
* push() (code.InteractiveConsole 的方法): Interactive Console Objects.
                                                             (line   28)
* push() (contextlib.ExitStack 的方法):  Utilities.          (line  561)
* put_nowait() (asyncio.Queue 的方法):   Queue.              (line   68)
* put_nowait() (multiprocessing.Queue 的方法): Pipes and Queues.
                                                             (line  146)
* put_nowait() (queue.Queue 的方法):     佇列物件.           (line   37)
* put_nowait() (queue.SimpleQueue 的方法): SimpleQueue 物件. (line   30)
* put() (asyncio.Queue 的方法):          Queue.              (line   60)
* put() (multiprocessing.Queue 的方法):  Pipes and Queues.   (line  131)
* put() (multiprocessing.SimpleQueue 的方法): Pipes and Queues.
                                                             (line  240)
* put() (queue.Queue 的方法):            佇列物件.           (line   26)
* put() (queue.SimpleQueue 的方法):      SimpleQueue 物件.   (line   18)
* putch() (於 msvcrt 模組中):            Console I/O.        (line   36)
* putenv() (於 os 模組中):               行程參數.           (line  352)
* putheader() (http.client.HTTPConnection 的方法): HTTPConnection 物件.
                                                             (line  176)
* putp() (於 curses 模組中):             函式<5>.            (line  392)
* putrequest() (http.client.HTTPConnection 的方法): HTTPConnection 物件.
                                                             (line  165)
* putwch() (於 msvcrt 模組中):           Console I/O.        (line   40)
* putwin() (curses.window 的方法):       Window Objects.     (line  455)
* pvariance() (於 statistics 模組中):    函式細節.           (line  352)
* pwd() (ftplib.FTP 的方法):             FTP 物件.           (line  301)
* pwrite() (於 os 模組中):               File Descriptor Operations.
                                                             (line  648)
* pwritev() (於 os 模組中):              File Descriptor Operations.
                                                             (line  659)
* Py_ABS (C macro):                      有用的巨集.         (line   33)
* Py_AddPendingCall (C function):        Asynchronous Notifications.
                                                             (line   10)
* Py_ALWAYS_INLINE (C macro):            有用的巨集.         (line   39)
* Py_AtExit (C function):                行程控制.           (line   32)
* Py_AUDIT_READ (C macro):               Member flags.       (line   12)
* Py_AuditHookFunction (C type):         系統函式.           (line  147)
* Py_BEGIN_ALLOW_THREADS (C macro):      高階 API.           (line  161)
* Py_BEGIN_ALLOW_THREADS（C 巨集）:      Releasing the GIL from extension code.
                                                             (line   21)
* Py_BEGIN_CRITICAL_SECTION (C macro):   Python Critical Section API.
                                                             (line   49)
* Py_BEGIN_CRITICAL_SECTION2 (C macro):  Python Critical Section API.
                                                             (line   77)
* Py_BLOCK_THREADS (C macro):            高階 API.           (line  175)
* Py_buffer (C type):                    Buffer structure.   (line   25)
* Py_buffer.buf (C member):              Buffer structure.   (line   27)
* Py_buffer.format (C member):           Buffer structure.   (line   89)
* Py_buffer.internal (C member):         Buffer structure.   (line  152)
* Py_buffer.itemsize (C member):         Buffer structure.   (line   69)
* Py_buffer.len (C member):              Buffer structure.   (line   52)
* Py_buffer.ndim (C member):             Buffer structure.   (line   98)
* Py_buffer.obj (C member):              Buffer structure.   (line   39)
* Py_buffer.readonly (C member):         Buffer structure.   (line   64)
* Py_buffer.shape (C member):            Buffer structure.   (line  107)
* Py_buffer.strides (C member):          Buffer structure.   (line  120)
* Py_buffer.suboffsets (C member):       Buffer structure.   (line  133)
* Py_BuildValue (C function):            Building values.    (line    6)
* Py_BytesMain (C function):             The Very High Level Layer.
                                                             (line   41)
* Py_BytesWarningFlag (C var):           Global configuration variables.
                                                             (line   15)
* Py_CHARMASK (C macro):                 有用的巨集.         (line   61)
* Py_CLEAR (C function):                 參照計數<2>.        (line  133)
* Py_CompileString (C function):         The Very High Level Layer.
                                                             (line  239)
* Py_CompileString（C 函式）:            The Very High Level Layer.
                                                             (line  326)
* Py_CompileString（C 函式） <1>:        The Very High Level Layer.
                                                             (line  331)
* Py_CompileString（C 函式） <2>:        The Very High Level Layer.
                                                             (line  338)
* Py_CompileStringExFlags (C function):  The Very High Level Layer.
                                                             (line  272)
* Py_CompileStringFlags (C function):    The Very High Level Layer.
                                                             (line  245)
* Py_CompileStringObject (C function):   The Very High Level Layer.
                                                             (line  251)
* Py_complex (C type):                   作為 C 結構的複數.  (line   10)
* Py_complex.imag (C member):            作為 C 結構的複數.  (line   15)
* Py_complex.real (C member):            作為 C 結構的複數.  (line   15)
* Py_CONSTANT_ELLIPSIS (C macro):        物件協定.           (line   28)
* Py_CONSTANT_EMPTY_BYTES (C macro):     物件協定.           (line   43)
* Py_CONSTANT_EMPTY_STR (C macro):       物件協定.           (line   40)
* Py_CONSTANT_EMPTY_TUPLE (C macro):     物件協定.           (line   46)
* Py_CONSTANT_FALSE (C macro):           物件協定.           (line   22)
* Py_CONSTANT_NONE (C macro):            物件協定.           (line   19)
* Py_CONSTANT_NOT_IMPLEMENTED (C macro): 物件協定.           (line   31)
* Py_CONSTANT_ONE (C macro):             物件協定.           (line   37)
* Py_CONSTANT_TRUE (C macro):            物件協定.           (line   25)
* Py_CONSTANT_ZERO (C macro):            物件協定.           (line   34)
* PY_CXX_CONST (C macro):                API 函式.           (line  113)
* Py_DEBUG (C macro):                    除錯建置.           (line   14)
* Py_DEBUG (於 test.support 模組中):     test support --- Python 測試套件的工具.
                                                             (line  115)
* Py_DebugFlag (C var):                  Global configuration variables.
                                                             (line   29)
* Py_DecodeLocale (C function):          作業系統工具.       (line  115)
* Py_DECREF (C function):                參照計數<2>.        (line  100)
* Py_DecRef (C function):                參照計數<2>.        (line  152)
* Py_DECREF（C 函式）:                   參照計數.           (line   15)
* Py_DEPRECATED (C macro):               有用的巨集.         (line   66)
* Py_DontWriteBytecodeFlag (C var):      Global configuration variables.
                                                             (line   42)
* Py_Ellipsis (C var):                   Ellipsis Object.    (line    6)
* Py_EncodeLocale (C function):          作業系統工具.       (line  168)
* Py_END_ALLOW_THREADS (C macro):        高階 API.           (line  168)
* Py_END_ALLOW_THREADS（C 巨集）:        Releasing the GIL from extension code.
                                                             (line   21)
* Py_END_CRITICAL_SECTION (C macro):     Python Critical Section API.
                                                             (line   64)
* Py_END_CRITICAL_SECTION2 (C macro):    Python Critical Section API.
                                                             (line   93)
* Py_EndInterpreter (C function):        Sub-interpreter support.
                                                             (line  202)
* Py_EnterRecursiveCall (C function):    Recursion Control.  (line   13)
* Py_EQ (C macro):                       PyTypeObject Slots. (line 1023)
* Py_eval_input (C var):                 The Very High Level Layer.
                                                             (line  324)
* Py_Exit (C function):                  行程控制.           (line   22)
* Py_ExitStatusException (C function):   PyStatus.           (line   65)
* Py_False (C var):                      Boolean（布林）物件.
                                                             (line   20)
* Py_FatalError (C function):            行程控制.           (line    6)
* Py_FatalError():                       Process-wide parameters.
                                                             (line  216)
* Py_FdIsInteractive (C function):       作業系統工具.       (line   18)
* Py_file_input (C var):                 The Very High Level Layer.
                                                             (line  329)
* Py_Finalize (C function):              Initializing and finalizing the interpreter.
                                                             (line   98)
* Py_FinalizeEx (C function):            Initializing and finalizing the interpreter.
                                                             (line   53)
* Py_FinalizeEx（C 函式）:               行程控制.           (line   23)
* Py_FinalizeEx（C 函式） <1>:           行程控制.           (line   33)
* Py_FinalizeEx（C 函式） <2>:           Initializing and finalizing the interpreter.
                                                             (line    7)
* Py_FinalizeEx（C 函式） <3>:           Sub-interpreter support.
                                                             (line  165)
* Py_FinalizeEx（C 函式） <4>:           Sub-interpreter support.
                                                             (line  203)
* Py_FrozenFlag (C var):                 Global configuration variables.
                                                             (line   56)
* Py_GE (C macro):                       PyTypeObject Slots. (line 1032)
* Py_GenericAlias (C function):          型別提示物件.       (line    9)
* Py_GenericAliasType (C var):           型別提示物件.       (line   40)
* Py_GetArgcArgv (C function):           Py_GetArgcArgv.     (line    6)
* Py_GetBuildInfo (C function):          Process-wide parameters.
                                                             (line  203)
* Py_GetCompiler (C function):           Process-wide parameters.
                                                             (line  192)
* Py_GetConstant (C function):           物件協定.           (line    6)
* Py_GetConstantBorrowed (C function):   物件協定.           (line   57)
* Py_GetCopyright (C function):          Process-wide parameters.
                                                             (line  182)
* Py_GETENV (C macro):                   有用的巨集.         (line   76)
* Py_GetExecPrefix (C function):         Process-wide parameters.
                                                             (line   67)
* Py_GetExecPrefix（C 函式）:            嵌入式Python.       (line   32)
* Py_GetPath (C function):               Process-wide parameters.
                                                             (line  133)
* Py_GetPath():                          Process-wide parameters.
                                                             (line    7)
* Py_GetPath（C 函式）:                  嵌入式Python.       (line   32)
* Py_GetPlatform (C function):           Process-wide parameters.
                                                             (line  170)
* Py_GetPrefix (C function):             Process-wide parameters.
                                                             (line   45)
* Py_GetPrefix（C 函式）:                嵌入式Python.       (line   32)
* Py_GetProgramFullPath (C function):    Process-wide parameters.
                                                             (line  114)
* Py_GetProgramFullPath（C 函式）:       嵌入式Python.       (line   32)
* Py_GetProgramName (C function):        Process-wide parameters.
                                                             (line   30)
* Py_GetPythonHome (C function):         Process-wide parameters.
                                                             (line  305)
* Py_GetVersion (C function):            Process-wide parameters.
                                                             (line  156)
* Py_GT (C macro):                       PyTypeObject Slots. (line 1029)
* Py_hash_t (C type):                    PyHash API.         (line    9)
* Py_HashPointer (C function):           PyHash API.         (line   81)
* Py_HashRandomizationFlag (C var):      Global configuration variables.
                                                             (line   69)
* Py_IgnoreEnvironmentFlag (C var):      Global configuration variables.
                                                             (line   84)
* Py_INCREF (C function):                參照計數<2>.        (line   39)
* Py_IncRef (C function):                參照計數<2>.        (line  147)
* Py_INCREF（C 函式）:                   參照計數.           (line   15)
* Py_Initialize (C function):            Initializing and finalizing the interpreter.
                                                             (line    6)
* Py_Initialize():                       Process-wide parameters.
                                                             (line    7)
* Py_Initialize（C 函式）:               嵌入式Python.       (line   10)
* Py_Initialize（C 函式） <1>:           Sub-interpreter support.
                                                             (line  165)
* Py_InitializeEx (C function):          Initializing and finalizing the interpreter.
                                                             (line   31)
* Py_InitializeFromConfig (C function):  Initialization with PyConfig.
                                                             (line    8)
* Py_InspectFlag (C var):                Global configuration variables.
                                                             (line   97)
* Py_InteractiveFlag (C var):            Global configuration variables.
                                                             (line  112)
* Py_Is (C function):                    Base object types and macros.
                                                             (line   55)
* Py_IS_TYPE (C function):               Base object types and macros.
                                                             (line   91)
* Py_IsFalse (C function):               Base object types and macros.
                                                             (line   73)
* Py_IsFinalizing (C function):          Initializing and finalizing the interpreter.
                                                             (line   46)
* Py_IsInitialized (C function):         Initializing and finalizing the interpreter.
                                                             (line   40)
* Py_IsInitialized（C 函式）:            嵌入式Python.       (line   41)
* Py_IsNone (C function):                Base object types and macros.
                                                             (line   61)
* Py_IsolatedFlag (C var):               Global configuration variables.
                                                             (line  122)
* Py_IsTrue (C function):                Base object types and macros.
                                                             (line   67)
* Py_LE (C macro):                       PyTypeObject Slots. (line 1020)
* Py_LeaveRecursiveCall (C function):    Recursion Control.  (line   33)
* Py_LegacyWindowsFSEncodingFlag (C var): Global configuration variables.
                                                             (line  138)
* Py_LegacyWindowsStdioFlag (C var):     Global configuration variables.
                                                             (line  158)
* Py_LIMITED_API (C macro):              受限 C API.         (line   10)
* Py_LT (C macro):                       PyTypeObject Slots. (line 1017)
* Py_Main (C function):                  The Very High Level Layer.
                                                             (line   24)
* PY_MAJOR_VERSION (C macro):            API 和 ABI 版本管理.
                                                             (line   11)
* Py_MAX (C macro):                      有用的巨集.         (line   81)
* Py_MEMBER_SIZE (C macro):              有用的巨集.         (line   87)
* PY_MICRO_VERSION (C macro):            API 和 ABI 版本管理.
                                                             (line   19)
* Py_MIN (C macro):                      有用的巨集.         (line   93)
* PY_MINOR_VERSION (C macro):            API 和 ABI 版本管理.
                                                             (line   15)
* Py_mod_create (C macro):               Multi-phase initialization.
                                                             (line   61)
* Py_mod_exec (C macro):                 Multi-phase initialization.
                                                             (line   95)
* Py_mod_gil (C macro):                  Multi-phase initialization.
                                                             (line  137)
* Py_mod_gil.Py_MOD_GIL_NOT_USED (C macro): Multi-phase initialization.
                                                             (line  147)
* Py_mod_gil.Py_MOD_GIL_USED (C macro):  Multi-phase initialization.
                                                             (line  141)
* Py_mod_multiple_interpreters (C macro): Multi-phase initialization.
                                                             (line  107)
* Py_MOD_MULTIPLE_INTERPRETERS_NOT_SUPPORTED (C macro): Multi-phase initialization.
                                                             (line  111)
* Py_MOD_MULTIPLE_INTERPRETERS_SUPPORTED (C macro): Multi-phase initialization.
                                                             (line  115)
* Py_MOD_PER_INTERPRETER_GIL_SUPPORTED (C macro): Multi-phase initialization.
                                                             (line  121)
* Py_NE (C macro):                       PyTypeObject Slots. (line 1026)
* Py_NewInterpreter (C function):        Sub-interpreter support.
                                                             (line  192)
* Py_NewInterpreterFromConfig (C function): Sub-interpreter support.
                                                             (line  109)
* Py_NewRef (C function):                參照計數<2>.        (line   68)
* Py_NO_INLINE (C macro):                有用的巨集.         (line   99)
* Py_None (C var):                       None 物件.          (line   11)
* Py_NoSiteFlag (C var):                 Global configuration variables.
                                                             (line  176)
* Py_NotImplemented (C var):             物件協定.           (line   71)
* Py_NoUserSiteDirectory (C var):        Global configuration variables.
                                                             (line  192)
* py_object (ctypes 中的類別):           Fundamental data types<2>.
                                                             (line  218)
* Py_OpenCodeHookFunction (C type):      檔案物件 File Objects.
                                                             (line   57)
* Py_OptimizeFlag (C var):               Global configuration variables.
                                                             (line  206)
* Py_PreInitialize (C function):         Preinitialize Python with PyPreConfig.
                                                             (line   21)
* Py_PreInitializeFromArgs (C function): Preinitialize Python with PyPreConfig.
                                                             (line   38)
* Py_PreInitializeFromBytesArgs (C function): Preinitialize Python with PyPreConfig.
                                                             (line   28)
* Py_PRINT_RAW (C macro):                物件協定.           (line   82)
* Py_PRINT_RAW（C 巨集）:                檔案物件 File Objects.
                                                             (line   85)
* PY_PYTHON:                             Customizing default Python versions.
                                                             (line   18)
* Py_QuietFlag (C var):                  Global configuration variables.
                                                             (line  216)
* Py_READONLY (C macro):                 Member flags.       (line    8)
* Py_REFCNT (C function):                參照計數<2>.        (line    8)
* Py_RELATIVE_OFFSET (C macro):          Member flags.       (line   17)
* PY_RELEASE_LEVEL (C macro):            API 和 ABI 版本管理.
                                                             (line   23)
* PY_RELEASE_SERIAL (C macro):           API 和 ABI 版本管理.
                                                             (line   28)
* Py_ReprEnter (C function):             Recursion Control.  (line   47)
* Py_ReprLeave (C function):             Recursion Control.  (line   64)
* PY_RESUME (monitoring event):          事件.               (line   43)
* PY_RETURN (monitoring event):          事件.               (line   48)
* Py_RETURN_FALSE (C macro):             Boolean（布林）物件.
                                                             (line   34)
* Py_RETURN_NONE (C macro):              None 物件.          (line   18)
* Py_RETURN_NOTIMPLEMENTED (C macro):    物件協定.           (line   76)
* Py_RETURN_RICHCOMPARE (C macro):       PyTypeObject Slots. (line 1038)
* Py_RETURN_TRUE (C macro):              Boolean（布林）物件.
                                                             (line   38)
* Py_RunMain (C function):               Py_RunMain.         (line    6)
* Py_SET_REFCNT (C function):            參照計數<2>.        (line   26)
* Py_SET_SIZE (C function):              Base object types and macros.
                                                             (line  114)
* Py_SET_TYPE (C function):              Base object types and macros.
                                                             (line   98)
* Py_SetProgramName (C function):        Process-wide parameters.
                                                             (line    6)
* Py_SetPythonHome (C function):         Process-wide parameters.
                                                             (line  286)
* Py_SETREF (C macro):                   參照計數<2>.        (line  157)
* Py_single_input (C var):               The Very High Level Layer.
                                                             (line  336)
* Py_SIZE (C function):                  Base object types and macros.
                                                             (line  104)
* Py_ssize_t (C type):                   型別.               (line   11)
* PY_SSIZE_T_MAX（C 巨集）:              整數物件.           (line  227)
* PY_START (monitoring event):           事件.               (line   53)
* Py_STRINGIFY (C macro):                有用的巨集.         (line  110)
* Py_T_BOOL (C macro):                   Member types.       (line   59)
* Py_T_BYTE (C macro):                   Member types.       (line   20)
* Py_T_CHAR (C macro):                   Member types.       (line   68)
* Py_T_DOUBLE (C macro):                 Member types.       (line   56)
* Py_T_FLOAT (C macro):                  Member types.       (line   53)
* Py_T_INT (C macro):                    Member types.       (line   26)
* Py_T_LONG (C macro):                   Member types.       (line   29)
* Py_T_LONGLONG (C macro):               Member types.       (line   32)
* Py_T_OBJECT_EX (C macro):              Member types.       (line   71)
* Py_T_PYSSIZET (C macro):               Member types.       (line   50)
* Py_T_SHORT (C macro):                  Member types.       (line   23)
* Py_T_STRING (C macro):                 Member types.       (line   62)
* Py_T_STRING_INPLACE (C macro):         Member types.       (line   65)
* Py_T_UBYTE (C macro):                  Member types.       (line   35)
* Py_T_UINT (C macro):                   Member types.       (line   38)
* Py_T_ULONG (C macro):                  Member types.       (line   44)
* Py_T_ULONGLONG (C macro):              Member types.       (line   47)
* Py_T_USHORT (C macro):                 Member types.       (line   41)
* PY_THROW (monitoring event):           事件.               (line   58)
* Py_TPFLAGS_BASE_EXC_SUBCLASS (C macro): PyTypeObject Slots.
                                                             (line  668)
* Py_TPFLAGS_BASETYPE (C macro):         PyTypeObject Slots. (line  518)
* Py_TPFLAGS_BYTES_SUBCLASS (C macro):   PyTypeObject Slots. (line  662)
* Py_TPFLAGS_DEFAULT (C macro):          PyTypeObject Slots. (line  568)
* Py_TPFLAGS_DICT_SUBCLASS (C macro):    PyTypeObject Slots. (line  666)
* Py_TPFLAGS_DISALLOW_INSTANTIATION (C macro): PyTypeObject Slots.
                                                             (line  724)
* Py_TPFLAGS_HAVE_FINALIZE (C macro):    PyTypeObject Slots. (line  681)
* Py_TPFLAGS_HAVE_GC (C macro):          PyTypeObject Slots. (line  546)
* Py_TPFLAGS_HAVE_VECTORCALL (C macro):  PyTypeObject Slots. (line  692)
* Py_TPFLAGS_HEAPTYPE (C macro):         PyTypeObject Slots. (line  500)
* Py_TPFLAGS_IMMUTABLETYPE (C macro):    PyTypeObject Slots. (line  710)
* Py_TPFLAGS_ITEMS_AT_END (C macro):     PyTypeObject Slots. (line  636)
* Py_TPFLAGS_LIST_SUBCLASS (C macro):    PyTypeObject Slots. (line  658)
* Py_TPFLAGS_LONG_SUBCLASS (C macro):    PyTypeObject Slots. (line  656)
* Py_TPFLAGS_MANAGED_DICT (C macro):     PyTypeObject Slots. (line  604)
* Py_TPFLAGS_MANAGED_WEAKREF (C macro):  PyTypeObject Slots. (line  624)
* Py_TPFLAGS_MAPPING (C macro):          PyTypeObject Slots. (line  752)
* Py_TPFLAGS_METHOD_DESCRIPTOR (C macro): PyTypeObject Slots.
                                                             (line  579)
* Py_TPFLAGS_READY (C macro):            PyTypeObject Slots. (line  528)
* Py_TPFLAGS_READYING (C macro):         PyTypeObject Slots. (line  537)
* Py_TPFLAGS_SEQUENCE (C macro):         PyTypeObject Slots. (line  776)
* Py_TPFLAGS_TUPLE_SUBCLASS (C macro):   PyTypeObject Slots. (line  660)
* Py_TPFLAGS_TYPE_SUBCLASS (C macro):    PyTypeObject Slots. (line  670)
* Py_TPFLAGS_UNICODE_SUBCLASS (C macro): PyTypeObject Slots. (line  664)
* Py_TPFLAGS_VALID_VERSION_TAG (C macro): PyTypeObject Slots.
                                                             (line  800)
* Py_tracefunc (C type):                 Profiling and Tracing.
                                                             (line   18)
* Py_True (C var):                       Boolean（布林）物件.
                                                             (line   27)
* Py_tss_NEEDS_INIT (C macro):           Thread Specific Storage TSS API.
                                                             (line   28)
* Py_tss_t (C type):                     Thread Specific Storage TSS API.
                                                             (line   17)
* Py_TYPE (C function):                  Base object types and macros.
                                                             (line   80)
* Py_UCS1 (C type):                      Unicode Type.       (line    9)
* Py_UCS2 (C type):                      Unicode Type.       (line    9)
* Py_UCS4 (C type):                      Unicode Type.       (line    9)
* Py_uhash_t (C type):                   PyHash API.         (line   15)
* Py_UNBLOCK_THREADS (C macro):          高階 API.           (line  180)
* Py_UnbufferedStdioFlag (C var):        Global configuration variables.
                                                             (line  231)
* Py_UNICODE (C type):                   Unicode Type.       (line   19)
* Py_UNICODE_IS_HIGH_SURROGATE (C function): Unicode Character Properties.
                                                             (line  105)
* Py_UNICODE_IS_LOW_SURROGATE (C function): Unicode Character Properties.
                                                             (line  109)
* Py_UNICODE_IS_SURROGATE (C function):  Unicode Character Properties.
                                                             (line  101)
* Py_UNICODE_ISALNUM (C function):       Unicode Character Properties.
                                                             (line   52)
* Py_UNICODE_ISALPHA (C function):       Unicode Character Properties.
                                                             (line   47)
* Py_UNICODE_ISDECIMAL (C function):     Unicode Character Properties.
                                                             (line   35)
* Py_UNICODE_ISDIGIT (C function):       Unicode Character Properties.
                                                             (line   39)
* Py_UNICODE_ISLINEBREAK (C function):   Unicode Character Properties.
                                                             (line   30)
* Py_UNICODE_ISLOWER (C function):       Unicode Character Properties.
                                                             (line   15)
* Py_UNICODE_ISNUMERIC (C function):     Unicode Character Properties.
                                                             (line   43)
* Py_UNICODE_ISPRINTABLE (C function):   Unicode Character Properties.
                                                             (line   57)
* Py_UNICODE_ISSPACE (C function):       Unicode Character Properties.
                                                             (line   10)
* Py_UNICODE_ISTITLE (C function):       Unicode Character Properties.
                                                             (line   25)
* Py_UNICODE_ISUPPER (C function):       Unicode Character Properties.
                                                             (line   20)
* Py_UNICODE_JOIN_SURROGATES (C function): Unicode Character Properties.
                                                             (line  113)
* Py_UNICODE_TODECIMAL (C function):     Unicode Character Properties.
                                                             (line   82)
* Py_UNICODE_TODIGIT (C function):       Unicode Character Properties.
                                                             (line   88)
* Py_UNICODE_TOLOWER (C function):       Unicode Character Properties.
                                                             (line   70)
* Py_UNICODE_TONUMERIC (C function):     Unicode Character Properties.
                                                             (line   94)
* Py_UNICODE_TOTITLE (C function):       Unicode Character Properties.
                                                             (line   78)
* Py_UNICODE_TOUPPER (C function):       Unicode Character Properties.
                                                             (line   74)
* Py_UNREACHABLE (C macro):              有用的巨集.         (line  116)
* Py_UNUSED (C macro):                   有用的巨集.         (line  136)
* PY_UNWIND (monitoring event):          事件.               (line   62)
* Py_VaBuildValue (C function):          Building values.    (line  201)
* PY_VECTORCALL_ARGUMENTS_OFFSET (C macro): Vectorcall 協定. (line   62)
* Py_VerboseFlag (C var):                Global configuration variables.
                                                             (line  244)
* Py_Version (C var):                    API 和 ABI 版本管理.
                                                             (line   65)
* PY_VERSION_HEX (C macro):              API 和 ABI 版本管理.
                                                             (line   32)
* Py_VISIT (C function):                 循環垃圾回收的支援. (line  179)
* Py_XDECREF (C function):               參照計數<2>.        (line  127)
* Py_XDECREF（C 函式）:                  例外<17>.           (line  103)
* Py_XINCREF (C function):               參照計數<2>.        (line   61)
* Py_XNewRef (C function):               參照計數<2>.        (line   92)
* Py_XSETREF (C macro):                  參照計數<2>.        (line  181)
* PY_YIELD (monitoring event):           事件.               (line   66)
* PyAIter_Check (C function):            疊代器協議.         (line   13)
* PyAnySet_Check (C function):           集合物件.           (line   54)
* PyAnySet_CheckExact (C function):      集合物件.           (line   67)
* PyArg_Parse (C function):              API 函式.           (line   54)
* PyArg_ParseTuple (C function):         API 函式.           (line    6)
* PyArg_ParseTuple（C 函式）:            Extracting Parameters in Extension Functions.
                                                             (line    6)
* PyArg_ParseTupleAndKeywords (C function): API 函式.        (line   19)
* PyArg_ParseTupleAndKeywords（C 函式）: Keyword Parameters for Extension Functions.
                                                             (line    6)
* PyArg_UnpackTuple (C function):        API 函式.           (line   73)
* PyArg_ValidateKeywordArguments (C function): API 函式.     (line   46)
* PyArg_VaParse (C function):            API 函式.           (line   13)
* PyArg_VaParseTupleAndKeywords (C function): API 函式.      (line   40)
* PyASCIIObject (C type):                Unicode Type.       (line   30)
* PyAsyncMethods (C type):               Async Object Structures.
                                                             (line    8)
* PyAsyncMethods.am_aiter (C member):    Async Object Structures.
                                                             (line   36)
* PyAsyncMethods.am_anext (C member):    Async Object Structures.
                                                             (line   49)
* PyAsyncMethods.am_await (C member):    Async Object Structures.
                                                             (line   23)
* PyAsyncMethods.am_send (C member):     Async Object Structures.
                                                             (line   59)
* PyBool_Check (C function):             Boolean（布林）物件.
                                                             (line   15)
* PyBool_FromLong (C function):          Boolean（布林）物件.
                                                             (line   42)
* PyBool_Type (C var):                   Boolean（布林）物件.
                                                             (line   10)
* PyBUF_ANY_CONTIGUOUS (C macro):        contiguity requests.
                                                             (line   20)
* PyBUF_C_CONTIGUOUS (C macro):          contiguity requests.
                                                             (line   14)
* PyBUF_CONTIG (C macro):                compound requests.  (line   36)
* PyBUF_CONTIG_RO (C macro):             compound requests.  (line   39)
* PyBUF_F_CONTIGUOUS (C macro):          contiguity requests.
                                                             (line   17)
* PyBUF_FORMAT (C macro):                readonly format.    (line   14)
* PyBUF_FULL (C macro):                  compound requests.  (line   18)
* PyBUF_FULL_RO (C macro):               compound requests.  (line   21)
* PyBUF_INDIRECT (C macro):              shape strides suboffsets.
                                                             (line   14)
* PyBUF_MAX_NDIM (C macro):              Buffer structure.   (line  162)
* PyBUF_ND (C macro):                    shape strides suboffsets.
                                                             (line   20)
* PyBUF_READ (C macro):                  MemoryView 物件.    (line   18)
* PyBUF_RECORDS (C macro):               compound requests.  (line   24)
* PyBUF_RECORDS_RO (C macro):            compound requests.  (line   27)
* PyBUF_SIMPLE (C macro):                shape strides suboffsets.
                                                             (line   23)
* PyBUF_STRIDED (C macro):               compound requests.  (line   30)
* PyBUF_STRIDED_RO (C macro):            compound requests.  (line   33)
* PyBUF_STRIDES (C macro):               shape strides suboffsets.
                                                             (line   17)
* PyBUF_WRITABLE (C macro):              readonly format.    (line    6)
* PyBUF_WRITE (C macro):                 MemoryView 物件.    (line   22)
* PyBuffer_FillContiguousStrides (C function): Buffer-related functions.
                                                             (line   87)
* PyBuffer_FillInfo (C function):        Buffer-related functions.
                                                             (line   95)
* PyBuffer_FromContiguous (C function):  Buffer-related functions.
                                                             (line   63)
* PyBuffer_GetPointer (C function):      Buffer-related functions.
                                                             (line   57)
* PyBuffer_IsContiguous (C function):    Buffer-related functions.
                                                             (line   49)
* PyBuffer_Release (C function):         Buffer-related functions.
                                                             (line   31)
* PyBuffer_SizeFromFormat (C function):  Buffer-related functions.
                                                             (line   41)
* PyBuffer_ToContiguous (C function):    Buffer-related functions.
                                                             (line   70)
* PyBufferProcs (C type):                Buffer Object Structures.
                                                             (line    6)
* PyBufferProcs.bf_getbuffer (C member): Buffer Object Structures.
                                                             (line   12)
* PyBufferProcs.bf_releasebuffer (C member): Buffer Object Structures.
                                                             (line   60)
* PyBufferProcs（C 型別）:               緩衝協定 Buffer Protocol.
                                                             (line   20)
* PyByteArray_AS_STRING (C function):    巨集.               (line    8)
* PyByteArray_AsString (C function):     直接 API 函式.      (line   32)
* PyByteArray_Check (C function):        型別檢查巨集.       (line    6)
* PyByteArray_CheckExact (C function):   型別檢查巨集.       (line   11)
* PyByteArray_Concat (C function):       直接 API 函式.      (line   20)
* PyByteArray_FromObject (C function):   直接 API 函式.      (line    6)
* PyByteArray_FromStringAndSize (C function): 直接 API 函式. (line   13)
* PyByteArray_GET_SIZE (C function):     巨集.               (line   12)
* PyByteArray_Resize (C function):       直接 API 函式.      (line   37)
* PyByteArray_Size (C function):         直接 API 函式.      (line   27)
* PyByteArray_Type (C var):              位元組陣列物件 Byte Array Objects.
                                                             (line   10)
* PyByteArrayObject (C type):            位元組陣列物件 Byte Array Objects.
                                                             (line    6)
* PyBytes_AS_STRING (C function):        位元組物件 Bytes Objects.
                                                             (line  134)
* PyBytes_AsString (C function):         位元組物件 Bytes Objects.
                                                             (line  123)
* PyBytes_AsStringAndSize (C function):  位元組物件 Bytes Objects.
                                                             (line  139)
* PyBytes_Check (C function):            位元組物件 Bytes Objects.
                                                             (line   19)
* PyBytes_CheckExact (C function):       位元組物件 Bytes Objects.
                                                             (line   24)
* PyBytes_Concat (C function):           位元組物件 Bytes Objects.
                                                             (line  160)
* PyBytes_ConcatAndDel (C function):     位元組物件 Bytes Objects.
                                                             (line  169)
* PyBytes_FromFormat (C function):       位元組物件 Bytes Objects.
                                                             (line   43)
* PyBytes_FromFormatV (C function):      位元組物件 Bytes Objects.
                                                             (line  104)
* PyBytes_FromObject (C function):       位元組物件 Bytes Objects.
                                                             (line  110)
* PyBytes_FromString (C function):       位元組物件 Bytes Objects.
                                                             (line   30)
* PyBytes_FromStringAndSize (C function): 位元組物件 Bytes Objects.
                                                             (line   36)
* PyBytes_GET_SIZE (C function):         位元組物件 Bytes Objects.
                                                             (line  119)
* PyBytes_Size (C function):             位元組物件 Bytes Objects.
                                                             (line  115)
* PyBytes_Type (C var):                  位元組物件 Bytes Objects.
                                                             (line   14)
* PyBytesObject (C type):                位元組物件 Bytes Objects.
                                                             (line    9)
* pycache_prefix (於 sys 模組中):        sys --- 系統特定的參數與函式.
                                                             (line  366)
* PyCallable_Check (C function):         呼叫支援 API.       (line    6)
* PyCallIter_Check (C function):         疊代器（Iterator）物件.
                                                             (line   32)
* PyCallIter_New (C function):           疊代器（Iterator）物件.
                                                             (line   37)
* PyCallIter_Type (C var):               疊代器（Iterator）物件.
                                                             (line   27)
* PyCapsule (C type):                    Capsules<2>.        (line   11)
* PyCapsule_CheckExact (C function):     Capsules<2>.        (line   29)
* PyCapsule_Destructor (C type):         Capsules<2>.        (line   20)
* PyCapsule_GetContext (C function):     Capsules<2>.        (line   75)
* PyCapsule_GetDestructor (C function):  Capsules<2>.        (line   64)
* PyCapsule_GetName (C function):        Capsules<2>.        (line   85)
* PyCapsule_GetPointer (C function):     Capsules<2>.        (line   54)
* PyCapsule_Import (C function):         Capsules<2>.        (line   94)
* PyCapsule_IsValid (C function):        Capsules<2>.        (line  105)
* PyCapsule_New (C function):            Capsules<2>.        (line   34)
* PyCapsule_SetContext (C function):     Capsules<2>.        (line  120)
* PyCapsule_SetDestructor (C function):  Capsules<2>.        (line  127)
* PyCapsule_SetName (C function):        Capsules<2>.        (line  135)
* PyCapsule_SetPointer (C function):     Capsules<2>.        (line  144)
* PyCell_Check (C function):             Cell 物件.          (line   21)
* PyCell_Get (C function):               Cell 物件.          (line   30)
* PyCell_GET (C function):               Cell 物件.          (line   34)
* PyCell_New (C function):               Cell 物件.          (line   26)
* PyCell_Set (C function):               Cell 物件.          (line   38)
* PyCell_SET (C function):               Cell 物件.          (line   46)
* PyCell_Type (C var):                   Cell 物件.          (line   17)
* PyCellObject (C type):                 Cell 物件.          (line   13)
* PyCF_ALLOW_TOP_LEVEL_AWAIT (於 ast 模組中): 編譯器旗標<2>. (line    8)
* PyCF_ONLY_AST (於 ast 模組中):         編譯器旗標<2>.      (line   15)
* PyCF_OPTIMIZED_AST (於 ast 模組中):    編譯器旗標<2>.      (line   19)
* PyCF_TYPE_COMMENTS (於 ast 模組中):    編譯器旗標<2>.      (line   26)
* PyCFunction (C type):                  實作函式與方法.     (line    6)
* PyCFunction_New (C function):          實作函式與方法.     (line  257)
* PyCFunction_NewEx (C function):        實作函式與方法.     (line  252)
* PyCFunctionFast (C type):              實作函式與方法.     (line   29)
* PyCFunctionFastWithKeywords (C type):  實作函式與方法.     (line   38)
* PyCFunctionWithKeywords (C type):      實作函式與方法.     (line   20)
* PycInvalidationMode (py_compile 中的類別): py_compile — 編譯 Python 來源檔案.
                                                             (line   92)
* PyCMethod (C type):                    實作函式與方法.     (line   49)
* PyCMethod_New (C function):            實作函式與方法.     (line  225)
* PyCode_Addr2Line (C function):         程式碼物件.         (line   91)
* PyCode_Addr2Location (C function):     程式碼物件.         (line  100)
* PyCode_AddWatcher (C function):        程式碼物件.         (line  154)
* PyCode_Check (C function):             程式碼物件.         (line   20)
* PyCode_ClearWatcher (C function):      程式碼物件.         (line  163)
* PyCode_GetCellvars (C function):       程式碼物件.         (line  135)
* PyCode_GetCode (C function):           程式碼物件.         (line  112)
* PyCode_GetFreevars (C function):       程式碼物件.         (line  145)
* PyCode_GetNumFree (C function):        程式碼物件.         (line   25)
* PyCode_GetVarnames (C function):       程式碼物件.         (line  126)
* PyCode_New（C 函式）:                  程式碼物件.         (line   60)
* PyCode_NewEmpty (C function):          程式碼物件.         (line   85)
* PyCode_NewWithPosOnlyArgs（C 函式）:   程式碼物件.         (line   77)
* PyCode_Type (C var):                   程式碼物件.         (line   15)
* PyCode_WatchCallback (C type):         程式碼物件.         (line  179)
* PyCodec_BackslashReplaceErrors (C function): 用於 Unicode 編碼錯誤處理程式的註冊 API.
                                                             (line   45)
* PyCodec_Decode (C function):           編解碼器註冊表和支援函式.
                                                             (line   33)
* PyCodec_Decoder (C function):          編解碼器查找 API.   (line   14)
* PyCodec_Encode (C function):           編解碼器註冊表和支援函式.
                                                             (line   23)
* PyCodec_Encoder (C function):          編解碼器查找 API.   (line   10)
* PyCodec_IgnoreErrors (C function):     用於 Unicode 編碼錯誤處理程式的註冊 API.
                                                             (line   32)
* PyCodec_IncrementalDecoder (C function): 編解碼器查找 API. (line   23)
* PyCodec_IncrementalEncoder (C function): 編解碼器查找 API. (line   18)
* PyCodec_KnownEncoding (C function):    編解碼器註冊表和支援函式.
                                                             (line   19)
* PyCodec_LookupError (C function):      用於 Unicode 編碼錯誤處理程式的註冊 API.
                                                             (line   23)
* PyCodec_NameReplaceErrors (C function): 用於 Unicode 編碼錯誤處理程式的註冊 API.
                                                             (line   50)
* PyCodec_Register (C function):         編解碼器註冊表和支援函式.
                                                             (line    6)
* PyCodec_RegisterError (C function):    用於 Unicode 編碼錯誤處理程式的註冊 API.
                                                             (line    6)
* PyCodec_ReplaceErrors (C function):    用於 Unicode 編碼錯誤處理程式的註冊 API.
                                                             (line   36)
* PyCodec_StreamReader (C function):     編解碼器查找 API.   (line   28)
* PyCodec_StreamWriter (C function):     編解碼器查找 API.   (line   33)
* PyCodec_StrictErrors (C function):     用於 Unicode 編碼錯誤處理程式的註冊 API.
                                                             (line   28)
* PyCodec_Unregister (C function):       編解碼器註冊表和支援函式.
                                                             (line   12)
* PyCodec_XMLCharRefReplaceErrors (C function): 用於 Unicode 編碼錯誤處理程式的註冊 API.
                                                             (line   40)
* PyCodeEvent (C type):                  程式碼物件.         (line  172)
* PyCodeObject (C type):                 程式碼物件.         (line   10)
* PyCompactUnicodeObject (C type):       Unicode Type.       (line   30)
* PyCompileError:                        py_compile — 編譯 Python 來源檔案.
                                                             (line   19)
* PyCompilerFlags (C struct):            The Very High Level Layer.
                                                             (line  342)
* PyCompilerFlags.cf_feature_version (C member): The Very High Level Layer.
                                                             (line  358)
* PyCompilerFlags.cf_flags (C member):   The Very High Level Layer.
                                                             (line  354)
* PyComplex_AsCComplex (C function):     作為 Python 物件的複數.
                                                             (line   65)
* PyComplex_Check (C function):          作為 Python 物件的複數.
                                                             (line   15)
* PyComplex_CheckExact (C function):     作為 Python 物件的複數.
                                                             (line   20)
* PyComplex_FromCComplex (C function):   作為 Python 物件的複數.
                                                             (line   25)
* PyComplex_FromDoubles (C function):    作為 Python 物件的複數.
                                                             (line   29)
* PyComplex_ImagAsDouble (C function):   作為 Python 物件的複數.
                                                             (line   50)
* PyComplex_RealAsDouble (C function):   作為 Python 物件的複數.
                                                             (line   35)
* PyComplex_Type (C var):                作為 Python 物件的複數.
                                                             (line   10)
* PyComplexObject (C type):              作為 Python 物件的複數.
                                                             (line    6)
* PyConfig (C type):                     PyConfig.           (line    6)
* PyConfig_Clear (C function):           PyConfig.           (line   94)
* PyConfig_InitIsolatedConfig (C function): PyConfig.        (line   20)
* PyConfig_InitPythonConfig (C function): PyConfig.          (line   15)
* PyConfig_Read (C function):            PyConfig.           (line   65)
* PyConfig_SetArgv (C function):         PyConfig.           (line   40)
* PyConfig_SetBytesArgv (C function):    PyConfig.           (line   48)
* PyConfig_SetBytesString (C function):  PyConfig.           (line   32)
* PyConfig_SetString (C function):       PyConfig.           (line   25)
* PyConfig_SetWideStringList (C function): PyConfig.         (line   57)
* PyConfig.argv (C member):              PyConfig.           (line  125)
* PyConfig.base_exec_prefix (C member):  PyConfig.           (line  170)
* PyConfig.base_executable (C member):   PyConfig.           (line  180)
* PyConfig.base_prefix (C member):       PyConfig.           (line  194)
* PyConfig.buffered_stdio (C member):    PyConfig.           (line  204)
* PyConfig.bytes_warning (C member):     PyConfig.           (line  217)
* PyConfig.check_hash_pycs_mode (C member): PyConfig.        (line  254)
* PyConfig.code_debug_ranges (C member): PyConfig.           (line  240)
* PyConfig.configure_c_stdio (C member): PyConfig.           (line  274)
* PyConfig.cpu_count (C member):         PyConfig.           (line  486)
* PyConfig.dev_mode (C member):          PyConfig.           (line  289)
* PyConfig.dump_refs (C member):         PyConfig.           (line  298)
* PyConfig.exec_prefix (C member):       PyConfig.           (line  312)
* PyConfig.executable (C member):        PyConfig.           (line  324)
* PyConfig.faulthandler (C member):      PyConfig.           (line  335)
* PyConfig.filesystem_encoding (C member): PyConfig.         (line  347)
* PyConfig.filesystem_errors (C member): PyConfig.           (line  380)
* PyConfig.hash_seed (C member):         PyConfig.           (line  402)
* PyConfig.home (C member):              PyConfig.           (line  417)
* PyConfig.import_time (C member):       PyConfig.           (line  428)
* PyConfig.inspect (C member):           PyConfig.           (line  437)
* PyConfig.install_signal_handlers (C member): PyConfig.     (line  452)
* PyConfig.int_max_str_digits (C member): PyConfig.          (line  466)
* PyConfig.interactive (C member):       PyConfig.           (line  458)
* PyConfig.isolated (C member):          PyConfig.           (line  500)
* PyConfig.legacy_windows_stdio (C member): PyConfig.        (line  525)
* PyConfig.malloc_stats (C member):      PyConfig.           (line  542)
* PyConfig.module_search_paths (C member): PyConfig.         (line  586)
* PyConfig.module_search_paths_set (C member): PyConfig.     (line  588)
* PyConfig.optimization_level (C member): PyConfig.          (line  602)
* PyConfig.orig_argv (C member):         PyConfig.           (line  618)
* PyConfig.parse_argv (C member):        PyConfig.           (line  636)
* PyConfig.parser_debug (C member):      PyConfig.           (line  657)
* PyConfig.pathconfig_warnings (C member): PyConfig.         (line  671)
* PyConfig.perf_profiling (C member):    PyConfig.           (line  864)
* PyConfig.platlibdir (C member):        PyConfig.           (line  555)
* PyConfig.prefix (C member):            PyConfig.           (line  683)
* PyConfig.program_name (C member):      PyConfig.           (line  694)
* PyConfig.pycache_prefix (C member):    PyConfig.           (line  715)
* PyConfig.pythonpath_env (C member):    PyConfig.           (line  575)
* PyConfig.quiet (C member):             PyConfig.           (line  728)
* PyConfig.run_command (C member):       PyConfig.           (line  737)
* PyConfig.run_filename (C member):      PyConfig.           (line  745)
* PyConfig.run_module (C member):        PyConfig.           (line  758)
* PyConfig.run_presite (C member):       PyConfig.           (line  766)
* PyConfig.safe_path (C member):         PyConfig.           (line  148)
* PyConfig.show_ref_count (C member):    PyConfig.           (line  780)
* PyConfig.site_import (C member):       PyConfig.           (line  792)
* PyConfig.skip_source_first_line (C member): PyConfig.      (line  811)
* PyConfig.stdio_encoding (C member):    PyConfig.           (line  823)
* PyConfig.stdio_errors (C member):      PyConfig.           (line  825)
* PyConfig.tracemalloc (C member):       PyConfig.           (line  853)
* PyConfig.use_environment (C member):   PyConfig.           (line  882)
* PyConfig.use_hash_seed (C member):     PyConfig.           (line  404)
* PyConfig.user_site_directory (C member): PyConfig.         (line  893)
* PyConfig.verbose (C member):           PyConfig.           (line  906)
* PyConfig.warn_default_encoding (C member): PyConfig.       (line  230)
* PyConfig.warnoptions (C member):       PyConfig.           (line  923)
* PyConfig.write_bytecode (C member):    PyConfig.           (line  943)
* PyConfig.xoptions (C member):          PyConfig.           (line  956)
* PyContext (C type):                    情境變數物件.       (line   26)
* PyContext_CheckExact (C function):     情境變數物件.       (line   55)
* PyContext_Copy (C function):           情境變數物件.       (line   76)
* PyContext_CopyCurrent (C function):    情境變數物件.       (line   80)
* PyContext_Enter (C function):          情境變數物件.       (line   84)
* PyContext_Exit (C function):           情境變數物件.       (line   89)
* PyContext_New (C function):            情境變數物件.       (line   72)
* PyContext_Type (C var):                情境變數物件.       (line   41)
* PyContextToken (C type):               情境變數物件.       (line   36)
* PyContextToken_CheckExact (C function): 情境變數物件.      (line   65)
* PyContextToken_Type (C var):           情境變數物件.       (line   49)
* PyContextVar (C type):                 情境變數物件.       (line   31)
* PyContextVar_CheckExact (C function):  情境變數物件.       (line   60)
* PyContextVar_Get (C function):         情境變數物件.       (line  105)
* PyContextVar_New (C function):         情境變數物件.       (line   97)
* PyContextVar_Reset (C function):       情境變數物件.       (line  129)
* PyContextVar_Set (C function):         情境變數物件.       (line  123)
* PyContextVar_Type (C var):             情境變數物件.       (line   45)
* PyCoro_CheckExact (C function):        Coroutine（協程）物件.
                                                             (line   18)
* PyCoro_New (C function):               Coroutine（協程）物件.
                                                             (line   23)
* PyCoro_Type (C var):                   Coroutine（協程）物件.
                                                             (line   14)
* PyCoroObject (C type):                 Coroutine（協程）物件.
                                                             (line   10)
* PyDate_Check (C function):             DateTime 物件.      (line   73)
* PyDate_CheckExact (C function):        DateTime 物件.      (line   79)
* PyDate_FromDate (C function):          DateTime 物件.      (line  130)
* PyDate_FromTimestamp (C function):     DateTime 物件.      (line  291)
* PyDateTime_Check (C function):         DateTime 物件.      (line   84)
* PyDateTime_CheckExact (C function):    DateTime 物件.      (line   90)
* PyDateTime_Date (C type):              DateTime 物件.      (line   12)
* PyDateTime_DATE_GET_FOLD (C function): DateTime 物件.      (line  217)
* PyDateTime_DATE_GET_HOUR (C function): DateTime 物件.      (line  201)
* PyDateTime_DATE_GET_MICROSECOND (C function): DateTime 物件.
                                                             (line  213)
* PyDateTime_DATE_GET_MINUTE (C function): DateTime 物件.    (line  205)
* PyDateTime_DATE_GET_SECOND (C function): DateTime 物件.    (line  209)
* PyDateTime_DATE_GET_TZINFO (C function): DateTime 物件.    (line  223)
* PyDateTime_DateTime (C type):          DateTime 物件.      (line   17)
* PyDateTime_DateTimeType (C var):       DateTime 物件.      (line   38)
* PyDateTime_DateType (C var):           DateTime 物件.      (line   32)
* PyDateTime_Delta (C type):             DateTime 物件.      (line   27)
* PyDateTime_DELTA_GET_DAYS (C function): DateTime 物件.     (line  265)
* PyDateTime_DELTA_GET_MICROSECONDS (C function): DateTime 物件.
                                                             (line  277)
* PyDateTime_DELTA_GET_SECONDS (C function): DateTime 物件.  (line  271)
* PyDateTime_DeltaType (C var):          DateTime 物件.      (line   50)
* PyDateTime_FromDateAndTime (C function): DateTime 物件.    (line  135)
* PyDateTime_FromDateAndTimeAndFold (C function): DateTime 物件.
                                                             (line  141)
* PyDateTime_FromTimestamp (C function): DateTime 物件.      (line  285)
* PyDateTime_GET_DAY (C function):       DateTime 物件.      (line  193)
* PyDateTime_GET_MONTH (C function):     DateTime 物件.      (line  189)
* PyDateTime_GET_YEAR (C function):      DateTime 物件.      (line  185)
* PyDateTime_Time (C type):              DateTime 物件.      (line   22)
* PyDateTime_TIME_GET_FOLD (C function): DateTime 物件.      (line  249)
* PyDateTime_TIME_GET_HOUR (C function): DateTime 物件.      (line  233)
* PyDateTime_TIME_GET_MICROSECOND (C function): DateTime 物件.
                                                             (line  245)
* PyDateTime_TIME_GET_MINUTE (C function): DateTime 物件.    (line  237)
* PyDateTime_TIME_GET_SECOND (C function): DateTime 物件.    (line  241)
* PyDateTime_TIME_GET_TZINFO (C function): DateTime 物件.    (line  255)
* PyDateTime_TimeType (C var):           DateTime 物件.      (line   44)
* PyDateTime_TimeZone_UTC (C var):       DateTime 物件.      (line   64)
* PyDateTime_TZInfoType (C var):         DateTime 物件.      (line   56)
* PyDelta_Check (C function):            DateTime 物件.      (line  106)
* PyDelta_CheckExact (C function):       DateTime 物件.      (line  112)
* PyDelta_FromDSU (C function):          DateTime 物件.      (line  161)
* PyDescr_IsData (C function):           Descriptor（描述器）物件.
                                                             (line   33)
* PyDescr_NewClassMethod (C function):   Descriptor（描述器）物件.
                                                             (line   29)
* PyDescr_NewGetSet (C function):        Descriptor（描述器）物件.
                                                             (line   13)
* PyDescr_NewMember (C function):        Descriptor（描述器）物件.
                                                             (line   17)
* PyDescr_NewMethod (C function):        Descriptor（描述器）物件.
                                                             (line   21)
* PyDescr_NewWrapper (C function):       Descriptor（描述器）物件.
                                                             (line   25)
* PyDict_AddWatcher (C function):        字典物件.           (line  318)
* PyDict_Check (C function):             字典物件.           (line   15)
* PyDict_CheckExact (C function):        字典物件.           (line   20)
* PyDict_Clear (C function):             字典物件.           (line   36)
* PyDict_ClearWatcher (C function):      字典物件.           (line  327)
* PyDict_Contains (C function):          字典物件.           (line   40)
* PyDict_ContainsString (C function):    字典物件.           (line   46)
* PyDict_Copy (C function):              字典物件.           (line   54)
* PyDict_DelItem (C function):           字典物件.           (line   72)
* PyDict_DelItemString (C function):     字典物件.           (line   79)
* PyDict_GetItem (C function):           字典物件.           (line  101)
* PyDict_GetItemRef (C function):        字典物件.           (line   84)
* PyDict_GetItemString (C function):     字典物件.           (line  123)
* PyDict_GetItemStringRef (C function):  字典物件.           (line  136)
* PyDict_GetItemWithError (C function):  字典物件.           (line  116)
* PyDict_Items (C function):             字典物件.           (line  206)
* PyDict_Keys (C function):              字典物件.           (line  211)
* PyDict_Merge (C function):             字典物件.           (line  286)
* PyDict_MergeFromSeq2 (C function):     字典物件.           (line  303)
* PyDict_New (C function):               字典物件.           (line   25)
* PyDict_Next (C function):              字典物件.           (line  227)
* PyDict_Pop (C function):               字典物件.           (line  178)
* PyDict_PopString (C function):         字典物件.           (line  197)
* PyDict_SetDefault (C function):        字典物件.           (line  145)
* PyDict_SetDefaultRef (C function):     字典物件.           (line  157)
* PyDict_SetItem (C function):           字典物件.           (line   58)
* PyDict_SetItemString (C function):     字典物件.           (line   66)
* PyDict_Size (C function):              字典物件.           (line  221)
* PyDict_Type (C var):                   字典物件.           (line   10)
* PyDict_Unwatch (C function):           字典物件.           (line  344)
* PyDict_Update (C function):            字典物件.           (line  295)
* PyDict_Values (C function):            字典物件.           (line  216)
* PyDict_Watch (C function):             字典物件.           (line  335)
* PyDict_WatchCallback (C type):         字典物件.           (line  363)
* PyDict_WatchEvent (C type):            字典物件.           (line  354)
* PyDictObject (C type):                 字典物件.           (line    6)
* PyDictProxy_New (C function):          字典物件.           (line   29)
* PyDLL (ctypes 中的類別):               Loading shared libraries.
                                                             (line   67)
* PyDoc_STR (C macro):                   有用的巨集.         (line  161)
* PyDoc_STRVAR (C macro):                有用的巨集.         (line  143)
* PyErr_BadArgument (C function):        Raising exceptions. (line   44)
* PyErr_BadInternalCall (C function):    Raising exceptions. (line  209)
* PyErr_CheckSignals (C function):       Signal Handling<2>. (line    6)
* PyErr_Clear (C function):              Printing and clearing.
                                                             (line    6)
* PyErr_Clear（C 函式）:                 例外<17>.           (line   18)
* PyErr_Clear（C 函式） <1>:             例外<17>.           (line  103)
* PyErr_DisplayException (C function):   Printing and clearing.
                                                             (line   66)
* PyErr_ExceptionMatches (C function):   Querying the error indicator.
                                                             (line   22)
* PyErr_ExceptionMatches（C 函式）:      例外<17>.           (line  103)
* PyErr_Fetch (C function):              Querying the error indicator.
                                                             (line   74)
* PyErr_Fetch（C 函式）:                 Finalization and De-allocation.
                                                             (line   33)
* PyErr_Format (C function):             Raising exceptions. (line   23)
* PyErr_FormatUnraisable (C function):   Printing and clearing.
                                                             (line   55)
* PyErr_FormatV (C function):            Raising exceptions. (line   32)
* PyErr_GetExcInfo (C function):         Querying the error indicator.
                                                             (line  177)
* PyErr_GetHandledException (C function): Querying the error indicator.
                                                             (line  148)
* PyErr_GetRaisedException (C function): Querying the error indicator.
                                                             (line   36)
* PyErr_GivenExceptionMatches (C function): Querying the error indicator.
                                                             (line   28)
* PyErr_NewException (C function):       例外類別<2>.        (line    6)
* PyErr_NewExceptionWithDoc (C function): 例外類別<2>.       (line   23)
* PyErr_NoMemory (C function):           Raising exceptions. (line   50)
* PyErr_NormalizeException (C function): Querying the error indicator.
                                                             (line  125)
* PyErr_Occurred (C function):           Querying the error indicator.
                                                             (line    6)
* PyErr_Occurred（C 函式）:              例外<17>.           (line   10)
* PyErr_Print (C function):              Printing and clearing.
                                                             (line   30)
* PyErr_PrintEx (C function):            Printing and clearing.
                                                             (line   10)
* PyErr_ResourceWarning (C function):    Issuing warnings.   (line   67)
* PyErr_Restore (C function):            Querying the error indicator.
                                                             (line  102)
* PyErr_Restore（C 函式）:               Finalization and De-allocation.
                                                             (line   33)
* PyErr_SetExcFromWindowsErr (C function): Raising exceptions.
                                                             (line  112)
* PyErr_SetExcFromWindowsErrWithFilename (C function): Raising exceptions.
                                                             (line  157)
* PyErr_SetExcFromWindowsErrWithFilenameObject (C function): Raising exceptions.
                                                             (line  133)
* PyErr_SetExcFromWindowsErrWithFilenameObjects (C function): Raising exceptions.
                                                             (line  145)
* PyErr_SetExcInfo (C function):         Querying the error indicator.
                                                             (line  196)
* PyErr_SetFromErrno (C function):       Raising exceptions. (line   56)
* PyErr_SetFromErrnoWithFilename (C function): Raising exceptions.
                                                             (line   90)
* PyErr_SetFromErrnoWithFilenameObject (C function): Raising exceptions.
                                                             (line   71)
* PyErr_SetFromErrnoWithFilenameObjects (C function): Raising exceptions.
                                                             (line   80)
* PyErr_SetFromWindowsErr (C function):  Raising exceptions. (line   97)
* PyErr_SetFromWindowsErrWithFilename (C function): Raising exceptions.
                                                             (line  121)
* PyErr_SetHandledException (C function): Querying the error indicator.
                                                             (line  164)
* PyErr_SetImportError (C function):     Raising exceptions. (line  166)
* PyErr_SetImportErrorSubclass (C function): Raising exceptions.
                                                             (line  177)
* PyErr_SetInterrupt (C function):       Signal Handling<2>. (line   33)
* PyErr_SetInterruptEx (C function):     Signal Handling<2>. (line   42)
* PyErr_SetNone (C function):            Raising exceptions. (line   40)
* PyErr_SetObject (C function):          Raising exceptions. (line   18)
* PyErr_SetRaisedException (C function): Querying the error indicator.
                                                             (line   64)
* PyErr_SetString (C function):          Raising exceptions. (line   10)
* PyErr_SetString（C 函式）:             例外<17>.           (line   18)
* PyErr_SyntaxLocation (C function):     Raising exceptions. (line  204)
* PyErr_SyntaxLocationEx (C function):   Raising exceptions. (line  196)
* PyErr_SyntaxLocationObject (C function): Raising exceptions.
                                                             (line  186)
* PyErr_WarnEx (C function):             Issuing warnings.   (line   19)
* PyErr_WarnExplicit (C function):       Issuing warnings.   (line   51)
* PyErr_WarnExplicitObject (C function): Issuing warnings.   (line   39)
* PyErr_WarnFormat (C function):         Issuing warnings.   (line   59)
* PyErr_WriteUnraisable (C function):    Printing and clearing.
                                                             (line   33)
* PyEval_AcquireThread (C function):     低階 API.           (line  204)
* PyEval_AcquireThread():                高階 API.           (line   31)
* PyEval_EvalCode (C function):          The Very High Level Layer.
                                                             (line  281)
* PyEval_EvalCodeEx (C function):        The Very High Level Layer.
                                                             (line  288)
* PyEval_EvalFrame (C function):         The Very High Level Layer.
                                                             (line  301)
* PyEval_EvalFrameEx (C function):       The Very High Level Layer.
                                                             (line  306)
* PyEval_GetBuiltins (C function):       Reflection.         (line    6)
* PyEval_GetFrame (C function):          Reflection.         (line   55)
* PyEval_GetFrameBuiltins (C function):  Reflection.         (line   62)
* PyEval_GetFrameGlobals (C function):   Reflection.         (line   83)
* PyEval_GetFrameLocals (C function):    Reflection.         (line   70)
* PyEval_GetFuncDesc (C function):       Reflection.         (line   96)
* PyEval_GetFuncName (C function):       Reflection.         (line   91)
* PyEval_GetGlobals (C function):        Reflection.         (line   46)
* PyEval_GetLocals (C function):         Reflection.         (line   16)
* PyEval_InitThreads (C function):       高階 API.           (line   30)
* PyEval_InitThreads():                  Initializing and finalizing the interpreter.
                                                             (line    7)
* PyEval_MergeCompilerFlags (C function): The Very High Level Layer.
                                                             (line  319)
* PyEval_ReleaseThread (C function):     低階 API.           (line  225)
* PyEval_ReleaseThread():                高階 API.           (line   31)
* PyEval_RestoreThread (C function):     高階 API.           (line   55)
* PyEval_RestoreThread():                高階 API.           (line   31)
* PyEval_RestoreThread（C 函式）:        Releasing the GIL from extension code.
                                                             (line   33)
* PyEval_SaveThread (C function):        高階 API.           (line   49)
* PyEval_SaveThread():                   高階 API.           (line   31)
* PyEval_SaveThread（C 函式）:           Releasing the GIL from extension code.
                                                             (line   33)
* PyEval_SetProfile (C function):        Profiling and Tracing.
                                                             (line  117)
* PyEval_SetProfileAllThreads (C function): Profiling and Tracing.
                                                             (line  131)
* PyEval_SetTrace (C function):          Profiling and Tracing.
                                                             (line  146)
* PyEval_SetTraceAllThreads (C function): Profiling and Tracing.
                                                             (line  161)
* PyExc_ArithmeticError（C 變數）:       Standard Exceptions.
                                                             (line   11)
* PyExc_AssertionError（C 變數）:        Standard Exceptions.
                                                             (line   11)
* PyExc_AttributeError（C 變數）:        Standard Exceptions.
                                                             (line   11)
* PyExc_BaseException（C 變數）:         Standard Exceptions.
                                                             (line   11)
* PyExc_BlockingIOError（C 變數）:       Standard Exceptions.
                                                             (line   11)
* PyExc_BrokenPipeError（C 變數）:       Standard Exceptions.
                                                             (line   11)
* PyExc_BufferError（C 變數）:           Standard Exceptions.
                                                             (line   11)
* PyExc_BytesWarning（C 變數）:          Standard Warning Categories.
                                                             (line   11)
* PyExc_ChildProcessError（C 變數）:     Standard Exceptions.
                                                             (line   11)
* PyExc_ConnectionAbortedError（C 變數）: Standard Exceptions.
                                                             (line   11)
* PyExc_ConnectionError（C 變數）:       Standard Exceptions.
                                                             (line   11)
* PyExc_ConnectionRefusedError（C 變數）: Standard Exceptions.
                                                             (line   11)
* PyExc_ConnectionResetError（C 變數）:  Standard Exceptions.
                                                             (line   11)
* PyExc_DeprecationWarning（C 變數）:    Standard Warning Categories.
                                                             (line   11)
* PyExc_EnvironmentError（C 變數）:      Standard Exceptions.
                                                             (line  189)
* PyExc_EOFError（C 變數）:              Standard Exceptions.
                                                             (line   11)
* PyExc_Exception（C 變數）:             Standard Exceptions.
                                                             (line   11)
* PyExc_FileExistsError（C 變數）:       Standard Exceptions.
                                                             (line   11)
* PyExc_FileNotFoundError（C 變數）:     Standard Exceptions.
                                                             (line   11)
* PyExc_FloatingPointError（C 變數）:    Standard Exceptions.
                                                             (line   11)
* PyExc_FutureWarning（C 變數）:         Standard Warning Categories.
                                                             (line   11)
* PyExc_GeneratorExit（C 變數）:         Standard Exceptions.
                                                             (line   11)
* PyExc_ImportError（C 變數）:           Standard Exceptions.
                                                             (line   11)
* PyExc_ImportWarning（C 變數）:         Standard Warning Categories.
                                                             (line   11)
* PyExc_IndentationError（C 變數）:      Standard Exceptions.
                                                             (line   11)
* PyExc_IndexError（C 變數）:            Standard Exceptions.
                                                             (line   11)
* PyExc_InterruptedError（C 變數）:      Standard Exceptions.
                                                             (line   11)
* PyExc_IOError（C 變數）:               Standard Exceptions.
                                                             (line  189)
* PyExc_IsADirectoryError（C 變數）:     Standard Exceptions.
                                                             (line   11)
* PyExc_KeyboardInterrupt（C 變數）:     Standard Exceptions.
                                                             (line   11)
* PyExc_KeyError（C 變數）:              Standard Exceptions.
                                                             (line   11)
* PyExc_LookupError（C 變數）:           Standard Exceptions.
                                                             (line   11)
* PyExc_MemoryError（C 變數）:           Standard Exceptions.
                                                             (line   11)
* PyExc_ModuleNotFoundError（C 變數）:   Standard Exceptions.
                                                             (line   11)
* PyExc_NameError（C 變數）:             Standard Exceptions.
                                                             (line   11)
* PyExc_NotADirectoryError（C 變數）:    Standard Exceptions.
                                                             (line   11)
* PyExc_NotImplementedError（C 變數）:   Standard Exceptions.
                                                             (line   11)
* PyExc_OSError（C 變數）:               Standard Exceptions.
                                                             (line   11)
* PyExc_OverflowError（C 變數）:         Standard Exceptions.
                                                             (line   11)
* PyExc_PendingDeprecationWarning（C 變數）: Standard Warning Categories.
                                                             (line   11)
* PyExc_PermissionError（C 變數）:       Standard Exceptions.
                                                             (line   11)
* PyExc_ProcessLookupError（C 變數）:    Standard Exceptions.
                                                             (line   11)
* PyExc_RecursionError（C 變數）:        Standard Exceptions.
                                                             (line   11)
* PyExc_ReferenceError（C 變數）:        Standard Exceptions.
                                                             (line   11)
* PyExc_ResourceWarning（C 變數）:       Standard Warning Categories.
                                                             (line   11)
* PyExc_RuntimeError（C 變數）:          Standard Exceptions.
                                                             (line   11)
* PyExc_RuntimeWarning（C 變數）:        Standard Warning Categories.
                                                             (line   11)
* PyExc_StopAsyncIteration（C 變數）:    Standard Exceptions.
                                                             (line   11)
* PyExc_StopIteration（C 變數）:         Standard Exceptions.
                                                             (line   11)
* PyExc_SyntaxError（C 變數）:           Standard Exceptions.
                                                             (line   11)
* PyExc_SyntaxWarning（C 變數）:         Standard Warning Categories.
                                                             (line   11)
* PyExc_SystemError（C 變數）:           Standard Exceptions.
                                                             (line   11)
* PyExc_SystemExit（C 變數）:            Standard Exceptions.
                                                             (line   11)
* PyExc_TabError（C 變數）:              Standard Exceptions.
                                                             (line   11)
* PyExc_TimeoutError（C 變數）:          Standard Exceptions.
                                                             (line   11)
* PyExc_TypeError（C 變數）:             Standard Exceptions.
                                                             (line   11)
* PyExc_UnboundLocalError（C 變數）:     Standard Exceptions.
                                                             (line   11)
* PyExc_UnicodeDecodeError（C 變數）:    Standard Exceptions.
                                                             (line   11)
* PyExc_UnicodeEncodeError（C 變數）:    Standard Exceptions.
                                                             (line   11)
* PyExc_UnicodeError（C 變數）:          Standard Exceptions.
                                                             (line   11)
* PyExc_UnicodeTranslateError（C 變數）: Standard Exceptions.
                                                             (line   11)
* PyExc_UnicodeWarning（C 變數）:        Standard Warning Categories.
                                                             (line   11)
* PyExc_UserWarning（C 變數）:           Standard Warning Categories.
                                                             (line   11)
* PyExc_ValueError（C 變數）:            Standard Exceptions.
                                                             (line   11)
* PyExc_Warning（C 變數）:               Standard Warning Categories.
                                                             (line   11)
* PyExc_WindowsError（C 變數）:          Standard Exceptions.
                                                             (line  189)
* PyExc_ZeroDivisionError（C 變數）:     Standard Exceptions.
                                                             (line   11)
* PyException_GetArgs (C function):      例外物件.           (line   47)
* PyException_GetCause (C function):     例外物件.           (line   31)
* PyException_GetContext (C function):   例外物件.           (line   18)
* PyException_GetTraceback (C function): 例外物件.           (line    6)
* PyException_SetArgs (C function):      例外物件.           (line   51)
* PyException_SetCause (C function):     例外物件.           (line   38)
* PyException_SetContext (C function):   例外物件.           (line   25)
* PyException_SetTraceback (C function): 例外物件.           (line   14)
* PyFile_FromFd (C function):            檔案物件 File Objects.
                                                             (line   13)
* PyFile_GetLine (C function):           檔案物件 File Objects.
                                                             (line   36)
* PyFile_SetOpenCodeHook (C function):   檔案物件 File Objects.
                                                             (line   50)
* PyFile_WriteObject (C function):       檔案物件 File Objects.
                                                             (line   83)
* PyFile_WriteString (C function):       檔案物件 File Objects.
                                                             (line   92)
* PyFloat_AS_DOUBLE (C function):        浮點數（Floating-Point）物件.
                                                             (line   49)
* PyFloat_AsDouble (C function):         浮點數（Floating-Point）物件.
                                                             (line   37)
* PyFloat_Check (C function):            浮點數（Floating-Point）物件.
                                                             (line   16)
* PyFloat_CheckExact (C function):       浮點數（Floating-Point）物件.
                                                             (line   22)
* PyFloat_FromDouble (C function):       浮點數（Floating-Point）物件.
                                                             (line   33)
* PyFloat_FromString (C function):       浮點數（Floating-Point）物件.
                                                             (line   28)
* PyFloat_GetInfo (C function):          浮點數（Floating-Point）物件.
                                                             (line   54)
* PyFloat_GetMax (C function):           浮點數（Floating-Point）物件.
                                                             (line   60)
* PyFloat_GetMin (C function):           浮點數（Floating-Point）物件.
                                                             (line   64)
* PyFloat_Pack2 (C function):            Pack functions.     (line   22)
* PyFloat_Pack4 (C function):            Pack functions.     (line   26)
* PyFloat_Pack8 (C function):            Pack functions.     (line   30)
* PyFloat_Type (C var):                  浮點數（Floating-Point）物件.
                                                             (line   11)
* PyFloat_Unpack2 (C function):          Unpack functions.   (line   20)
* PyFloat_Unpack4 (C function):          Unpack functions.   (line   24)
* PyFloat_Unpack8 (C function):          Unpack functions.   (line   28)
* PyFloatObject (C type):                浮點數（Floating-Point）物件.
                                                             (line    6)
* PyFrame_Check (C function):            Frame 物件.         (line   29)
* PyFrame_GetBack (C function):          Frame 物件.         (line   36)
* PyFrame_GetBuiltins (C function):      Frame 物件.         (line   45)
* PyFrame_GetCode (C function):          Frame 物件.         (line   53)
* PyFrame_GetGenerator (C function):     Frame 物件.         (line   64)
* PyFrame_GetGlobals (C function):       Frame 物件.         (line   75)
* PyFrame_GetLasti (C function):         Frame 物件.         (line   83)
* PyFrame_GetLineNumber (C function):    Frame 物件.         (line  128)
* PyFrame_GetLocals (C function):        Frame 物件.         (line  112)
* PyFrame_GetVar (C function):           Frame 物件.         (line   91)
* PyFrame_GetVarString (C function):     Frame 物件.         (line  105)
* PyFrame_Type (C var):                  Frame 物件.         (line   21)
* PyFrameObject (C type):                Frame 物件.         (line    6)
* PyFrozenSet_Check (C function):        集合物件.           (line   49)
* PyFrozenSet_CheckExact (C function):   集合物件.           (line   73)
* PyFrozenSet_New (C function):          集合物件.           (line   86)
* PyFrozenSet_Type (C var):              集合物件.           (line   35)
* PyFunction_AddWatcher (C function):    函式物件 Function Objects.
                                                             (line  100)
* PyFunction_Check (C function):         函式物件 Function Objects.
                                                             (line   17)
* PyFunction_ClearWatcher (C function):  函式物件 Function Objects.
                                                             (line  110)
* PyFunction_GetAnnotations (C function): 函式物件 Function Objects.
                                                             (line   88)
* PyFunction_GetClosure (C function):    函式物件 Function Objects.
                                                             (line   77)
* PyFunction_GetCode (C function):       函式物件 Function Objects.
                                                             (line   41)
* PyFunction_GetDefaults (C function):   函式物件 Function Objects.
                                                             (line   55)
* PyFunction_GetGlobals (C function):    函式物件 Function Objects.
                                                             (line   44)
* PyFunction_GetModule (C function):     函式物件 Function Objects.
                                                             (line   47)
* PyFunction_New (C function):           函式物件 Function Objects.
                                                             (line   22)
* PyFunction_NewWithQualName (C function): 函式物件 Function Objects.
                                                             (line   32)
* PyFunction_SetAnnotations (C function): 函式物件 Function Objects.
                                                             (line   93)
* PyFunction_SetClosure (C function):    函式物件 Function Objects.
                                                             (line   81)
* PyFunction_SetDefaults (C function):   函式物件 Function Objects.
                                                             (line   59)
* PyFunction_SetVectorcall (C function): 函式物件 Function Objects.
                                                             (line   67)
* PyFunction_Type (C var):               函式物件 Function Objects.
                                                             (line   12)
* PyFunction_WatchCallback (C type):     函式物件 Function Objects.
                                                             (line  128)
* PyFunction_WatchEvent (C type):        函式物件 Function Objects.
                                                             (line  119)
* PyFunctionObject (C type):             函式物件 Function Objects.
                                                             (line    8)
* PYFUNCTYPE() (於 ctypes 模組中):       Function prototypes.
                                                             (line   33)
* PyGC_Collect (C function):             Controlling the Garbage Collector State.
                                                             (line    9)
* PyGC_Disable (C function):             Controlling the Garbage Collector State.
                                                             (line   27)
* PyGC_Enable (C function):              Controlling the Garbage Collector State.
                                                             (line   20)
* PyGC_IsEnabled (C function):           Controlling the Garbage Collector State.
                                                             (line   34)
* PyGen_Check (C function):              產生器 Generator 物件.
                                                             (line   18)
* PyGen_CheckExact (C function):         產生器 Generator 物件.
                                                             (line   23)
* PyGen_New (C function):                產生器 Generator 物件.
                                                             (line   28)
* PyGen_NewWithQualName (C function):    產生器 Generator 物件.
                                                             (line   33)
* PyGen_Type (C var):                    產生器 Generator 物件.
                                                             (line   14)
* PyGenObject (C type):                  產生器 Generator 物件.
                                                             (line   10)
* PyGetSetDef (C type):                  Defining Getters and Setters.
                                                             (line    6)
* PyGetSetDef.closure (C member):        Defining Getters and Setters.
                                                             (line   28)
* PyGetSetDef.doc (C member):            Defining Getters and Setters.
                                                             (line   24)
* PyGetSetDef.get (C member):            Defining Getters and Setters.
                                                             (line   15)
* PyGetSetDef.name (C member):           Defining Getters and Setters.
                                                             (line   11)
* PyGetSetDef.set (C member):            Defining Getters and Setters.
                                                             (line   19)
* PyGILState_Check (C function):         高階 API.           (line  145)
* PyGILState_Ensure (C function):        高階 API.           (line   96)
* PyGILState_GetThisThreadState (C function): 高階 API.      (line  137)
* PyGILState_Release (C function):       高階 API.           (line  127)
* PyHASH_BITS (C macro):                 PyHash API.         (line   27)
* PyHash_FuncDef (C type):               PyHash API.         (line   51)
* PyHash_FuncDef.hash_bits (C member):   PyHash API.         (line   59)
* PyHash_FuncDef.name (C member):        PyHash API.         (line   55)
* PyHash_FuncDef.seed_bits (C member):   PyHash API.         (line   63)
* PyHash_GetFuncDef (C function):        PyHash API.         (line   69)
* PyHASH_IMAG (C macro):                 PyHash API.         (line   45)
* PyHASH_INF (C macro):                  PyHash API.         (line   39)
* PyHASH_MODULUS (C macro):              PyHash API.         (line   21)
* PyHASH_MULTIPLIER (C macro):           PyHash API.         (line   33)
* PyImport_AddModule (C function):       引入模組<2>.        (line  119)
* PyImport_AddModuleObject (C function): 引入模組<2>.        (line  110)
* PyImport_AddModuleRef (C function):    引入模組<2>.        (line   88)
* PyImport_AppendInittab (C function):   引入模組<2>.        (line  288)
* PyImport_ExecCodeModule (C function):  引入模組<2>.        (line  124)
* PyImport_ExecCodeModuleEx (C function): 引入模組<2>.       (line  163)
* PyImport_ExecCodeModuleObject (C function): 引入模組<2>.   (line  172)
* PyImport_ExecCodeModuleWithPathnames (C function): 引入模組<2>.
                                                             (line  186)
* PyImport_ExtendInittab (C function):   引入模組<2>.        (line  315)
* PyImport_FrozenModules (C var):        引入模組<2>.        (line  280)
* PyImport_GetImporter (C function):     引入模組<2>.        (line  232)
* PyImport_GetMagicNumber (C function):  引入模組<2>.        (line  202)
* PyImport_GetMagicTag (C function):     引入模組<2>.        (line  210)
* PyImport_GetModule (C function):       引入模組<2>.        (line  223)
* PyImport_GetModuleDict (C function):   引入模組<2>.        (line  218)
* PyImport_Import (C function):          引入模組<2>.        (line   71)
* PyImport_ImportFrozenModule (C function): 引入模組<2>.     (line  257)
* PyImport_ImportFrozenModuleObject (C function): 引入模組<2>.
                                                             (line  244)
* PyImport_ImportModule (C function):    引入模組<2>.        (line    6)
* PyImport_ImportModuleEx (C function):  引入模組<2>.        (line   27)
* PyImport_ImportModuleLevel (C function): 引入模組<2>.      (line   61)
* PyImport_ImportModuleLevelObject (C function): 引入模組<2>.
                                                             (line   44)
* PyImport_ImportModuleNoBlock (C function): 引入模組<2>.    (line   13)
* PyImport_ReloadModule (C function):    引入模組<2>.        (line   82)
* PyIndex_Check (C function):            數字協定.           (line  285)
* PyInit_modulename (C function):        建立 C 與 C++ 擴充套件.
                                                             (line   16)
* PyInstanceMethod_Check (C function):   實例方法物件 Instance Method Objects.
                                                             (line   15)
* PyInstanceMethod_Function (C function): 實例方法物件 Instance Method Objects.
                                                             (line   24)
* PyInstanceMethod_GET_FUNCTION (C function): 實例方法物件 Instance Method Objects.
                                                             (line   28)
* PyInstanceMethod_New (C function):     實例方法物件 Instance Method Objects.
                                                             (line   20)
* PyInstanceMethod_Type (C var):         實例方法物件 Instance Method Objects.
                                                             (line   10)
* PyInterpreterConfig (C type):          Sub-interpreter support.
                                                             (line   24)
* PyInterpreterConfig_DEFAULT_GIL (C macro): Sub-interpreter support.
                                                             (line   93)
* PyInterpreterConfig_OWN_GIL (C macro): Sub-interpreter support.
                                                             (line  102)
* PyInterpreterConfig_SHARED_GIL (C macro): Sub-interpreter support.
                                                             (line   98)
* PyInterpreterConfig.allow_daemon_threads (C member): Sub-interpreter support.
                                                             (line   69)
* PyInterpreterConfig.allow_exec (C member): Sub-interpreter support.
                                                             (line   54)
* PyInterpreterConfig.allow_fork (C member): Sub-interpreter support.
                                                             (line   45)
* PyInterpreterConfig.allow_threads (C member): Sub-interpreter support.
                                                             (line   64)
* PyInterpreterConfig.check_multi_interp_extensions (C member): Sub-interpreter support.
                                                             (line   76)
* PyInterpreterConfig.gil (C member):    Sub-interpreter support.
                                                             (line   88)
* PyInterpreterConfig.use_main_obmalloc (C member): Sub-interpreter support.
                                                             (line   35)
* PyInterpreterState (C type):           高階 API.           (line    9)
* PyInterpreterState_Clear (C function): 低階 API.           (line   20)
* PyInterpreterState_Delete (C function): 低階 API.          (line   28)
* PyInterpreterState_Get (C function):   低階 API.           (line  112)
* PyInterpreterState_GetDict (C function): 低階 API.         (line  134)
* PyInterpreterState_GetID (C function): 低階 API.           (line  124)
* PyInterpreterState_Head (C function):  Advanced Debugger Support.
                                                             (line    9)
* PyInterpreterState_Main (C function):  Advanced Debugger Support.
                                                             (line   14)
* PyInterpreterState_New (C function):   低階 API.           (line   12)
* PyInterpreterState_Next (C function):  Advanced Debugger Support.
                                                             (line   18)
* PyInterpreterState_ThreadHead (C function): Advanced Debugger Support.
                                                             (line   24)
* PyIter_Check (C function):             疊代器協議.         (line    8)
* PyIter_Next (C function):              疊代器協議.         (line   20)
* PyIter_Send (C function):              疊代器協議.         (line   57)
* PYLAUNCHER_ALLOW_INSTALL:              Windows<5>.         (line   24)
* PYLAUNCHER_ALLOW_INSTALL <1>:          Windows<19>.        (line   15)
* PYLAUNCHER_ALLOW_INSTALL <2>:          安裝隨選.           (line    6)
* PYLAUNCHER_ALWAYS_INSTALL:             安裝隨選.           (line   12)
* PYLAUNCHER_DEBUG:                      Diagnostics.        (line    6)
* PYLAUNCHER_DRYRUN:                     Dry Run.            (line    6)
* PYLAUNCHER_DRYRUN <1>:                 安裝隨選.           (line   14)
* PYLAUNCHER_NO_SEARCH_PATH:             Shebang Lines.      (line   64)
* PyList_Append (C function):            List（串列）物件.   (line   97)
* PyList_AsTuple (C function):           List（串列）物件.   (line  147)
* PyList_Check (C function):             List（串列）物件.   (line   15)
* PyList_CheckExact (C function):        List（串列）物件.   (line   20)
* PyList_Clear (C function):             List（串列）物件.   (line  127)
* PyList_Extend (C function):            List（串列）物件.   (line  116)
* PyList_GET_ITEM (C function):          List（串列）物件.   (line   64)
* PyList_GET_SIZE (C function):          List（串列）物件.   (line   43)
* PyList_GetItem (C function):           List（串列）物件.   (line   58)
* PyList_GetItem（C 函式）:              參照計數詳細資訊.   (line   96)
* PyList_GetItemRef (C function):        List（串列）物件.   (line   47)
* PyList_GetSlice (C function):          List（串列）物件.   (line  102)
* PyList_Insert (C function):            List（串列）物件.   (line   91)
* PyList_New (C function):               List（串列）物件.   (line   25)
* PyList_Reverse (C function):           List（串列）物件.   (line  143)
* PyList_SET_ITEM (C function):          List（串列）物件.   (line   78)
* PyList_SetItem (C function):           List（串列）物件.   (line   69)
* PyList_SetItem（C 函式）:              參照計數詳細資訊.   (line   19)
* PyList_SetSlice (C function):          List（串列）物件.   (line  109)
* PyList_Size (C function):              List（串列）物件.   (line   38)
* PyList_Sort (C function):              List（串列）物件.   (line  138)
* PyList_Type (C var):                   List（串列）物件.   (line   10)
* PyListObject (C type):                 List（串列）物件.   (line    6)
* PyLong_AsDouble (C function):          整數物件.           (line  313)
* PyLong_AsInt (C function):             整數物件.           (line  159)
* PyLong_AsLong (C function):            整數物件.           (line  140)
* PyLong_AsLongAndOverflow (C function): 整數物件.           (line  166)
* PyLong_AsLongLong (C function):        整數物件.           (line  185)
* PyLong_AsLongLongAndOverflow (C function): 整數物件.       (line  204)
* PyLong_AsNativeBytes (C function):     整數物件.           (line  334)
* PyLong_AsNativeBytes.Py_ASNATIVEBYTES_ALLOW_INDEX (C macro): 整數物件.
                                                             (line  449)
* PyLong_AsNativeBytes.Py_ASNATIVEBYTES_BIG_ENDIAN (C macro): 整數物件.
                                                             (line  434)
* PyLong_AsNativeBytes.Py_ASNATIVEBYTES_DEFAULTS (C macro): 整數物件.
                                                             (line  431)
* PyLong_AsNativeBytes.Py_ASNATIVEBYTES_LITTLE_ENDIAN (C macro): 整數物件.
                                                             (line  437)
* PyLong_AsNativeBytes.Py_ASNATIVEBYTES_NATIVE_ENDIAN (C macro): 整數物件.
                                                             (line  440)
* PyLong_AsNativeBytes.Py_ASNATIVEBYTES_REJECT_NEGATIVE (C macro): 整數物件.
                                                             (line  446)
* PyLong_AsNativeBytes.Py_ASNATIVEBYTES_UNSIGNED_BUFFER (C macro): 整數物件.
                                                             (line  443)
* PyLong_AsSize_t (C function):          整數物件.           (line  250)
* PyLong_AsSsize_t (C function):         整數物件.           (line  226)
* PyLong_AsUnsignedLong (C function):    整數物件.           (line  238)
* PyLong_AsUnsignedLongLong (C function): 整數物件.          (line  262)
* PyLong_AsUnsignedLongLongMask (C function): 整數物件.      (line  295)
* PyLong_AsUnsignedLongMask (C function): 整數物件.          (line  278)
* PyLong_AsVoidPtr (C function):         整數物件.           (line  324)
* PyLong_Check (C function):             整數物件.           (line   23)
* PyLong_CheckExact (C function):        整數物件.           (line   28)
* PyLong_FromDouble (C function):        整數物件.           (line   69)
* PyLong_FromLong (C function):          整數物件.           (line   33)
* PyLong_FromLongLong (C function):      整數物件.           (line   58)
* PyLong_FromNativeBytes (C function):   整數物件.           (line  111)
* PyLong_FromSize_t (C function):        整數物件.           (line   53)
* PyLong_FromSsize_t (C function):       整數物件.           (line   48)
* PyLong_FromString (C function):        整數物件.           (line   74)
* PyLong_FromUnicodeObject (C function): 整數物件.           (line   98)
* PyLong_FromUnsignedLong (C function):  整數物件.           (line   42)
* PyLong_FromUnsignedLongLong (C function): 整數物件.        (line   63)
* PyLong_FromUnsignedNativeBytes (C function): 整數物件.     (line  127)
* PyLong_FromVoidPtr (C function):       整數物件.           (line  105)
* PyLong_GetInfo (C function):           整數物件.           (line  487)
* PyLong_Type (C var):                   整數物件.           (line   18)
* PyLongObject (C type):                 整數物件.           (line   13)
* PyMapping_Check (C function):          對映協定.           (line    9)
* PyMapping_DelItem (C function):        對映協定.           (line   57)
* PyMapping_DelItemString (C function):  對映協定.           (line   61)
* PyMapping_GetItemString (C function):  對映協定.           (line   22)
* PyMapping_GetOptionalItem (C function): 對映協定.          (line   28)
* PyMapping_GetOptionalItemString (C function): 對映協定.    (line   42)
* PyMapping_HasKey (C function):         對映協定.           (line   83)
* PyMapping_HasKeyString (C function):   對映協定.           (line   94)
* PyMapping_HasKeyStringWithError (C function): 對映協定.    (line   74)
* PyMapping_HasKeyWithError (C function): 對映協定.          (line   66)
* PyMapping_Items (C function):          對映協定.           (line  118)
* PyMapping_Keys (C function):           對映協定.           (line  106)
* PyMapping_Length (C function):         對映協定.           (line   15)
* PyMapping_SetItemString (C function):  對映協定.           (line   51)
* PyMapping_Size (C function):           對映協定.           (line   15)
* PyMapping_Values (C function):         對映協定.           (line  112)
* PyMappingMethods (C type):             Mapping Object Structures.
                                                             (line    6)
* PyMappingMethods.mp_ass_subscript (C member): Mapping Object Structures.
                                                             (line   27)
* PyMappingMethods.mp_length (C member): Mapping Object Structures.
                                                             (line   11)
* PyMappingMethods.mp_subscript (C member): Mapping Object Structures.
                                                             (line   18)
* PyMarshal_ReadLastObjectFromFile (C function): 資料 marshal 的支援.
                                                             (line   74)
* PyMarshal_ReadLongFromFile (C function): 資料 marshal 的支援.
                                                             (line   47)
* PyMarshal_ReadObjectFromFile (C function): 資料 marshal 的支援.
                                                             (line   65)
* PyMarshal_ReadObjectFromString (C function): 資料 marshal 的支援.
                                                             (line   90)
* PyMarshal_ReadShortFromFile (C function): 資料 marshal 的支援.
                                                             (line   56)
* PyMarshal_WriteLongToFile (C function): 資料 marshal 的支援.
                                                             (line   20)
* PyMarshal_WriteObjectToFile (C function): 資料 marshal 的支援.
                                                             (line   30)
* PyMarshal_WriteObjectToString (C function): 資料 marshal 的支援.
                                                             (line   39)
* PyMem_Calloc (C function):             記憶體介面.         (line   27)
* PyMem_Del (C function):                記憶體介面.         (line   83)
* PYMEM_DOMAIN_MEM (C macro):            Customize Memory Allocators.
                                                             (line   52)
* PYMEM_DOMAIN_OBJ (C macro):            Customize Memory Allocators.
                                                             (line   64)
* PYMEM_DOMAIN_RAW (C macro):            Customize Memory Allocators.
                                                             (line   40)
* PyMem_Free (C function):               記憶體介面.         (line   55)
* PyMem_GetAllocator (C function):       Customize Memory Allocators.
                                                             (line   76)
* PyMem_Malloc (C function):             記憶體介面.         (line   18)
* PyMem_New (C macro):                   記憶體介面.         (line   67)
* PyMem_RawCalloc (C function):          Raw Memory Interface.
                                                             (line   24)
* PyMem_RawFree (C function):            Raw Memory Interface.
                                                             (line   52)
* PyMem_RawMalloc (C function):          Raw Memory Interface.
                                                             (line   15)
* PyMem_RawRealloc (C function):         Raw Memory Interface.
                                                             (line   36)
* PyMem_Realloc (C function):            記憶體介面.         (line   39)
* PyMem_Resize (C macro):                記憶體介面.         (line   73)
* PyMem_SetAllocator (C function):       Customize Memory Allocators.
                                                             (line   81)
* PyMem_SetupDebugHooks (C function):    Customize Memory Allocators.
                                                             (line  124)
* PyMemAllocatorDomain (C type):         Customize Memory Allocators.
                                                             (line   36)
* PyMemAllocatorEx (C type):             Customize Memory Allocators.
                                                             (line    8)
* PyMember_GetOne (C function):          Accessing attributes of extension types.
                                                             (line   71)
* PyMember_SetOne (C function):          Accessing attributes of extension types.
                                                             (line   80)
* PyMemberDef (C type):                  Accessing attributes of extension types.
                                                             (line    6)
* PyMemberDef.doc (C member):            Accessing attributes of extension types.
                                                             (line   36)
* PyMemberDef.flags (C member):          Accessing attributes of extension types.
                                                             (line   31)
* PyMemberDef.name (C member):           Accessing attributes of extension types.
                                                             (line   14)
* PyMemberDef.offset (C member):         Accessing attributes of extension types.
                                                             (line   26)
* PyMemberDef.type (C member):           Accessing attributes of extension types.
                                                             (line   21)
* PyMemoryView_Check (C function):       MemoryView 物件.    (line   54)
* PyMemoryView_FromBuffer (C function):  MemoryView 物件.    (line   35)
* PyMemoryView_FromMemory (C function):  MemoryView 物件.    (line   26)
* PyMemoryView_FromObject (C function):  MemoryView 物件.    (line   10)
* PyMemoryView_GET_BASE (C function):    MemoryView 物件.    (line   68)
* PyMemoryView_GET_BUFFER (C function):  MemoryView 物件.    (line   60)
* PyMemoryView_GetContiguous (C function): MemoryView 物件.  (line   42)
* PyMethod_Check (C function):           方法物件 Method Objects.
                                                             (line   14)
* PyMethod_Function (C function):        方法物件 Method Objects.
                                                             (line   25)
* PyMethod_GET_FUNCTION (C function):    方法物件 Method Objects.
                                                             (line   28)
* PyMethod_GET_SELF (C function):        方法物件 Method Objects.
                                                             (line   35)
* PyMethod_New (C function):             方法物件 Method Objects.
                                                             (line   19)
* PyMethod_Self (C function):            方法物件 Method Objects.
                                                             (line   32)
* PyMethod_Type (C var):                 方法物件 Method Objects.
                                                             (line    9)
* PyMethodDef (C type):                  實作函式與方法.     (line   63)
* PyMethodDef.ml_doc (C member):         實作函式與方法.     (line   80)
* PyMethodDef.ml_flags (C member):       實作函式與方法.     (line   76)
* PyMethodDef.ml_meth (C member):        實作函式與方法.     (line   72)
* PyMethodDef.ml_name (C member):        實作函式與方法.     (line   68)
* PyMODINIT_FUNC (C macro):              有用的巨集.         (line   10)
* PyModule_Add (C function):             支援的函式.         (line   62)
* PyModule_AddFunctions (C function):    Low-level module creation functions.
                                                             (line   52)
* PyModule_AddIntConstant (C function):  支援的函式.         (line  112)
* PyModule_AddIntMacro (C macro):        支援的函式.         (line  135)
* PyModule_AddObject (C function):       支援的函式.         (line   78)
* PyModule_AddObjectRef (C function):    支援的函式.         (line   11)
* PyModule_AddStringConstant (C function): 支援的函式.       (line  123)
* PyModule_AddStringMacro (C macro):     支援的函式.         (line  143)
* PyModule_AddType (C function):         支援的函式.         (line  147)
* PyModule_Check (C function):           模組物件.           (line   13)
* PyModule_CheckExact (C function):      模組物件.           (line   18)
* PyModule_Create (C function):          Single-phase initialization.
                                                             (line   10)
* PyModule_Create2 (C function):         Single-phase initialization.
                                                             (line   15)
* PyModule_ExecDef (C function):         Low-level module creation functions.
                                                             (line   37)
* PyModule_FromDefAndSpec (C function):  Low-level module creation functions.
                                                             (line   11)
* PyModule_FromDefAndSpec2 (C function): Low-level module creation functions.
                                                             (line   20)
* PyModule_GetDef (C function):          模組物件.           (line   80)
* PyModule_GetDict (C function):         模組物件.           (line   45)
* PyModule_GetFilename (C function):     模組物件.           (line   96)
* PyModule_GetFilenameObject (C function): 模組物件.         (line   85)
* PyModule_GetName (C function):         模組物件.           (line   69)
* PyModule_GetNameObject (C function):   模組物件.           (line   58)
* PyModule_GetState (C function):        模組物件.           (line   74)
* PyModule_New (C function):             模組物件.           (line   40)
* PyModule_NewObject (C function):       模組物件.           (line   23)
* PyModule_SetDocString (C function):    Low-level module creation functions.
                                                             (line   43)
* PyModule_Type (C var):                 模組物件.           (line    6)
* PyModuleDef (C type):                  初始化 C 模組.      (line   17)
* PyModuleDef_Init (C function):         Multi-phase initialization.
                                                             (line   33)
* PyModuleDef_Slot (C type):             Multi-phase initialization.
                                                             (line   45)
* PyModuleDef_Slot.slot (C member):      Multi-phase initialization.
                                                             (line   47)
* PyModuleDef_Slot.value (C member):     Multi-phase initialization.
                                                             (line   51)
* PyModuleDef.m_base (C member):         初始化 C 模組.      (line   23)
* PyModuleDef.m_clear (C member):        初始化 C 模組.      (line   91)
* PyModuleDef.m_doc (C member):          初始化 C 模組.      (line   31)
* PyModuleDef.m_free (C member):         初始化 C 模組.      (line  113)
* PyModuleDef.m_methods (C member):      初始化 C 模組.      (line   58)
* PyModuleDef.m_name (C member):         初始化 C 模組.      (line   27)
* PyModuleDef.m_size (C member):         初始化 C 模組.      (line   36)
* PyModuleDef.m_slots (C member):        初始化 C 模組.      (line   64)
* PyModuleDef.m_slots.m_reload (C member): 初始化 C 模組.    (line   73)
* PyModuleDef.m_traverse (C member):     初始化 C 模組.      (line   75)
* PyMonitoring_FireBranchEvent (C function): Generating Execution Events.
                                                             (line   69)
* PyMonitoring_FireCallEvent (C function): Generating Execution Events.
                                                             (line   53)
* PyMonitoring_FireCRaiseEvent (C function): Generating Execution Events.
                                                             (line   91)
* PyMonitoring_FireCReturnEvent (C function): Generating Execution Events.
                                                             (line   74)
* PyMonitoring_FireExceptionHandledEvent (C function): Generating Execution Events.
                                                             (line  103)
* PyMonitoring_FireJumpEvent (C function): Generating Execution Events.
                                                             (line   64)
* PyMonitoring_FireLineEvent (C function): Generating Execution Events.
                                                             (line   59)
* PyMonitoring_FirePyResumeEvent (C function): Generating Execution Events.
                                                             (line   38)
* PyMonitoring_FirePyReturnEvent (C function): Generating Execution Events.
                                                             (line   43)
* PyMonitoring_FirePyStartEvent (C function): Generating Execution Events.
                                                             (line   33)
* PyMonitoring_FirePyThrowEvent (C function): Generating Execution Events.
                                                             (line   79)
* PyMonitoring_FirePyUnwindEvent (C function): Generating Execution Events.
                                                             (line  109)
* PyMonitoring_FirePyYieldEvent (C function): Generating Execution Events.
                                                             (line   48)
* PyMonitoring_FireRaiseEvent (C function): Generating Execution Events.
                                                             (line   85)
* PyMonitoring_FireReraiseEvent (C function): Generating Execution Events.
                                                             (line   97)
* PyMonitoring_FireStopIterationEvent (C function): Generating Execution Events.
                                                             (line  115)
* PyMonitoringState (C type):            Generating Execution Events.
                                                             (line   22)
* PyMutex (C type):                      Synchronization Primitives.
                                                             (line    8)
* PyMutex_Lock (C function):             Synchronization Primitives.
                                                             (line   25)
* PyMutex_Unlock (C function):           Synchronization Primitives.
                                                             (line   34)
* PyNumber_Absolute (C function):        數字協定.           (line   90)
* PyNumber_Add (C function):             數字協定.           (line   13)
* PyNumber_And (C function):             數字協定.           (line  115)
* PyNumber_AsSsize_t (C function):       數字協定.           (line  270)
* PyNumber_Check (C function):           數字協定.           (line    6)
* PyNumber_Divmod (C function):          數字協定.           (line   62)
* PyNumber_Float (C function):           數字協定.           (line  245)
* PyNumber_FloorDivide (C function):     數字協定.           (line   40)
* PyNumber_Index (C function):           數字協定.           (line  252)
* PyNumber_InPlaceAdd (C function):      數字協定.           (line  135)
* PyNumber_InPlaceAnd (C function):      數字協定.           (line  217)
* PyNumber_InPlaceFloorDivide (C function): 數字協定.        (line  166)
* PyNumber_InPlaceLshift (C function):   數字協定.           (line  203)
* PyNumber_InPlaceMatrixMultiply (C function): 數字協定.     (line  156)
* PyNumber_InPlaceMultiply (C function): 數字協定.           (line  149)
* PyNumber_InPlaceOr (C function):       數字協定.           (line  231)
* PyNumber_InPlacePower (C function):    數字協定.           (line  191)
* PyNumber_InPlaceRemainder (C function): 數字協定.          (line  184)
* PyNumber_InPlaceRshift (C function):   數字協定.           (line  210)
* PyNumber_InPlaceSubtract (C function): 數字協定.           (line  142)
* PyNumber_InPlaceTrueDivide (C function): 數字協定.         (line  173)
* PyNumber_InPlaceXor (C function):      數字協定.           (line  224)
* PyNumber_Invert (C function):          數字協定.           (line   96)
* PyNumber_Long (C function):            數字協定.           (line  238)
* PyNumber_Lshift (C function):          數字協定.           (line  101)
* PyNumber_MatrixMultiply (C function):  數字協定.           (line   31)
* PyNumber_Multiply (C function):        數字協定.           (line   25)
* PyNumber_Negative (C function):        數字協定.           (line   80)
* PyNumber_Or (C function):              數字協定.           (line  129)
* PyNumber_Positive (C function):        數字協定.           (line   85)
* PyNumber_Power (C function):           數字協定.           (line   70)
* PyNumber_Remainder (C function):       數字協定.           (line   56)
* PyNumber_Rshift (C function):          數字協定.           (line  108)
* PyNumber_Subtract (C function):        數字協定.           (line   19)
* PyNumber_ToBase (C function):          數字協定.           (line  261)
* PyNumber_TrueDivide (C function):      數字協定.           (line   46)
* PyNumber_Xor (C function):             數字協定.           (line  122)
* PyNumberMethods (C type):              Number Object Structures.
                                                             (line    6)
* PyNumberMethods.nb_absolute (C member): Number Object Structures.
                                                             (line   94)
* PyNumberMethods.nb_add (C member):     Number Object Structures.
                                                             (line   70)
* PyNumberMethods.nb_and (C member):     Number Object Structures.
                                                             (line  108)
* PyNumberMethods.nb_bool (C member):    Number Object Structures.
                                                             (line   97)
* PyNumberMethods.nb_divmod (C member):  Number Object Structures.
                                                             (line   82)
* PyNumberMethods.nb_float (C member):   Number Object Structures.
                                                             (line  122)
* PyNumberMethods.nb_floor_divide (C member): Number Object Structures.
                                                             (line  155)
* PyNumberMethods.nb_index (C member):   Number Object Structures.
                                                             (line  167)
* PyNumberMethods.nb_inplace_add (C member): Number Object Structures.
                                                             (line  125)
* PyNumberMethods.nb_inplace_and (C member): Number Object Structures.
                                                             (line  146)
* PyNumberMethods.nb_inplace_floor_divide (C member): Number Object Structures.
                                                             (line  161)
* PyNumberMethods.nb_inplace_lshift (C member): Number Object Structures.
                                                             (line  140)
* PyNumberMethods.nb_inplace_matrix_multiply (C member): Number Object Structures.
                                                             (line  173)
* PyNumberMethods.nb_inplace_multiply (C member): Number Object Structures.
                                                             (line  131)
* PyNumberMethods.nb_inplace_or (C member): Number Object Structures.
                                                             (line  152)
* PyNumberMethods.nb_inplace_power (C member): Number Object Structures.
                                                             (line  137)
* PyNumberMethods.nb_inplace_remainder (C member): Number Object Structures.
                                                             (line  134)
* PyNumberMethods.nb_inplace_rshift (C member): Number Object Structures.
                                                             (line  143)
* PyNumberMethods.nb_inplace_subtract (C member): Number Object Structures.
                                                             (line  128)
* PyNumberMethods.nb_inplace_true_divide (C member): Number Object Structures.
                                                             (line  164)
* PyNumberMethods.nb_inplace_xor (C member): Number Object Structures.
                                                             (line  149)
* PyNumberMethods.nb_int (C member):     Number Object Structures.
                                                             (line  117)
* PyNumberMethods.nb_invert (C member):  Number Object Structures.
                                                             (line   99)
* PyNumberMethods.nb_lshift (C member):  Number Object Structures.
                                                             (line  102)
* PyNumberMethods.nb_matrix_multiply (C member): Number Object Structures.
                                                             (line  170)
* PyNumberMethods.nb_multiply (C member): Number Object Structures.
                                                             (line   76)
* PyNumberMethods.nb_negative (C member): Number Object Structures.
                                                             (line   88)
* PyNumberMethods.nb_or (C member):      Number Object Structures.
                                                             (line  114)
* PyNumberMethods.nb_positive (C member): Number Object Structures.
                                                             (line   91)
* PyNumberMethods.nb_power (C member):   Number Object Structures.
                                                             (line   85)
* PyNumberMethods.nb_remainder (C member): Number Object Structures.
                                                             (line   79)
* PyNumberMethods.nb_reserved (C member): Number Object Structures.
                                                             (line  120)
* PyNumberMethods.nb_rshift (C member):  Number Object Structures.
                                                             (line  105)
* PyNumberMethods.nb_subtract (C member): Number Object Structures.
                                                             (line   73)
* PyNumberMethods.nb_true_divide (C member): Number Object Structures.
                                                             (line  158)
* PyNumberMethods.nb_xor (C member):     Number Object Structures.
                                                             (line  111)
* PyObject (C type):                     Base object types and macros.
                                                             (line   14)
* PyObject_ASCII (C function):           物件協定.           (line  336)
* PyObject_AsFileDescriptor (C function): 檔案物件 File Objects.
                                                             (line   30)
* PyObject_Bytes (C function):           物件協定.           (line  357)
* PyObject_Call (C function):            物件呼叫 API.       (line   55)
* PyObject_CallFunction (C function):    物件呼叫 API.       (line   97)
* PyObject_CallFunctionObjArgs (C function): 物件呼叫 API.   (line  130)
* PyObject_CallMethod (C function):      物件呼叫 API.       (line  113)
* PyObject_CallMethodNoArgs (C function): 物件呼叫 API.      (line  149)
* PyObject_CallMethodObjArgs (C function): 物件呼叫 API.     (line  140)
* PyObject_CallMethodOneArg (C function): 物件呼叫 API.      (line  159)
* PyObject_CallNoArgs (C function):      物件呼叫 API.       (line   68)
* PyObject_CallObject (C function):      物件呼叫 API.       (line   87)
* PyObject_CallObject（C 函式）:         Calling Python Functions from C.
                                                             (line   64)
* PyObject_Calloc (C function):          Object allocators.  (line   29)
* PyObject_CallOneArg (C function):      物件呼叫 API.       (line   78)
* PyObject_CheckBuffer (C function):     Buffer-related functions.
                                                             (line    6)
* PyObject_ClearManagedDict (C function): 物件協定.          (line  565)
* PyObject_ClearWeakRefs (C function):   弱參照物件<2>.      (line   88)
* PyObject_CopyData (C function):        Buffer-related functions.
                                                             (line   80)
* PyObject_Del (C function):             在 heap 上分配物件. (line   44)
* PyObject_DelAttr (C function):         物件協定.           (line  238)
* PyObject_DelAttrString (C function):   物件協定.           (line  244)
* PyObject_DelItem (C function):         物件協定.           (line  484)
* PyObject_Dir (C function):             物件協定.           (line  489)
* PyObject_Format (C function):          物件協定.           (line  315)
* PyObject_Free (C function):            Object allocators.  (line   57)
* PyObject_GC_Del (C function):          循環垃圾回收的支援. (line  132)
* PyObject_GC_IsFinalized (C function):  循環垃圾回收的支援. (line  122)
* PyObject_GC_IsTracked (C function):    循環垃圾回收的支援. (line  112)
* PyObject_GC_New (C macro):             循環垃圾回收的支援. (line   56)
* PyObject_GC_NewVar (C macro):          循環垃圾回收的支援. (line   61)
* PyObject_GC_Resize (C macro):          循環垃圾回收的支援. (line   86)
* PyObject_GC_Track (C function):        循環垃圾回收的支援. (line   96)
* PyObject_GC_UnTrack (C function):      循環垃圾回收的支援. (line  137)
* PyObject_GenericGetAttr (C function):  物件協定.           (line  186)
* PyObject_GenericGetDict (C function):  物件協定.           (line  259)
* PyObject_GenericHash (C function):     PyHash API.         (line   90)
* PyObject_GenericSetAttr (C function):  物件協定.           (line  226)
* PyObject_GenericSetDict (C function):  物件協定.           (line  275)
* PyObject_GetAIter (C function):        物件協定.           (line  505)
* PyObject_GetArenaAllocator (C function): Customize pymalloc Arena Allocator.
                                                             (line   26)
* PyObject_GetAttr (C function):         物件協定.           (line  142)
* PyObject_GetAttrString (C function):   物件協定.           (line  152)
* PyObject_GetBuffer (C function):       Buffer-related functions.
                                                             (line   12)
* PyObject_GetItem (C function):         物件協定.           (line  471)
* PyObject_GetItemData (C function):     物件協定.           (line  544)
* PyObject_GetIter (C function):         物件協定.           (line  498)
* PyObject_GetOptionalAttr (C function): 物件協定.           (line  162)
* PyObject_GetOptionalAttrString (C function): 物件協定.     (line  177)
* PyObject_GetTypeData (C function):     物件協定.           (line  515)
* PyObject_HasAttr (C function):         物件協定.           (line  115)
* PyObject_HasAttrString (C function):   物件協定.           (line  127)
* PyObject_HasAttrStringWithError (C function): 物件協定.    (line  106)
* PyObject_HasAttrWithError (C function): 物件協定.          (line   97)
* PyObject_Hash (C function):            物件協定.           (line  406)
* PyObject_HashNotImplemented (C function): 物件協定.        (line  416)
* PyObject_HEAD (C macro):               Base object types and macros.
                                                             (line   35)
* PyObject_HEAD_INIT (C macro):          Base object types and macros.
                                                             (line  120)
* PyObject_Init (C function):            在 heap 上分配物件. (line   13)
* PyObject_InitVar (C function):         在 heap 上分配物件. (line   20)
* PyObject_IS_GC (C function):           循環垃圾回收的支援. (line  104)
* PyObject_IsInstance (C function):      物件協定.           (line  385)
* PyObject_IsSubclass (C function):      物件協定.           (line  366)
* PyObject_IsTrue (C function):          物件協定.           (line  424)
* PyObject_Length (C function):          物件協定.           (line  451)
* PyObject_LengthHint (C function):      物件協定.           (line  460)
* PyObject_Malloc (C function):          Object allocators.  (line   20)
* PyObject_New (C macro):                在 heap 上分配物件. (line   26)
* PyObject_NewVar (C macro):             在 heap 上分配物件. (line   34)
* PyObject_Not (C function):             物件協定.           (line  429)
* PyObject_Print (C function):           物件協定.           (line   89)
* PyObject_Realloc (C function):         Object allocators.  (line   41)
* PyObject_Repr (C function):            物件協定.           (line  325)
* PyObject_RichCompare (C function):     物件協定.           (line  292)
* PyObject_RichCompareBool (C function): 物件協定.           (line  304)
* PyObject_SetArenaAllocator (C function): Customize pymalloc Arena Allocator.
                                                             (line   31)
* PyObject_SetAttr (C function):         物件協定.           (line  197)
* PyObject_SetAttrString (C function):   物件協定.           (line  208)
* PyObject_SetItem (C function):         物件協定.           (line  477)
* PyObject_Size (C function):            物件協定.           (line  451)
* PyObject_Str (C function):             物件協定.           (line  346)
* PyObject_Type (C function):            物件協定.           (line  434)
* PyObject_TypeCheck (C function):       物件協定.           (line  446)
* PyObject_VAR_HEAD (C macro):           Base object types and macros.
                                                             (line   45)
* PyObject_Vectorcall (C function):      物件呼叫 API.       (line  169)
* PyObject_VectorcallDict (C function):  物件呼叫 API.       (line  181)
* PyObject_VectorcallMethod (C function): 物件呼叫 API.      (line  195)
* PyObject_VisitManagedDict (C function): 物件協定.          (line  555)
* PyObject.ob_refcnt (C member):         PyObject Slots.     (line   13)
* PyObject.ob_type (C member):           PyObject Slots.     (line   26)
* PyObjectArenaAllocator (C type):       Customize pymalloc Arena Allocator.
                                                             (line    8)
* PyOS_AfterFork (C function):           作業系統工具.       (line   79)
* PyOS_AfterFork_Child (C function):     作業系統工具.       (line   56)
* PyOS_AfterFork_Parent (C function):    作業系統工具.       (line   42)
* PyOS_BeforeFork (C function):          作業系統工具.       (line   29)
* PyOS_CheckStack (C function):          作業系統工具.       (line   89)
* PyOS_double_to_string (C function):    字串轉換與格式化.   (line  104)
* PyOS_FSPath (C function):              作業系統工具.       (line    6)
* PyOS_getsig (C function):              作業系統工具.       (line  103)
* PyOS_InputHook (C var):                The Very High Level Layer.
                                                             (line  157)
* PyOS_ReadlineFunctionPointer (C var):  The Very High Level Layer.
                                                             (line  169)
* PyOS_setsig (C function):              作業系統工具.       (line  108)
* PyOS_sighandler_t (C type):            作業系統工具.       (line  100)
* PyOS_snprintf (C function):            字串轉換與格式化.   (line    8)
* PyOS_stricmp (C function):             字串轉換與格式化.   (line  134)
* PyOS_string_to_double (C function):    字串轉換與格式化.   (line   78)
* PyOS_strnicmp (C function):            字串轉換與格式化.   (line  139)
* PyOS_strtol (C function):              字串轉換與格式化.   (line   65)
* PyOS_strtoul (C function):             字串轉換與格式化.   (line   43)
* PyOS_vsnprintf (C function):           字串轉換與格式化.   (line   14)
* PyPreConfig (C type):                  PyPreConfig.        (line    6)
* PyPreConfig_InitIsolatedConfig (C function): PyPreConfig.  (line   18)
* PyPreConfig_InitPythonConfig (C function): PyPreConfig.    (line   12)
* PyPreConfig.allocator (C member):      PyPreConfig.        (line   26)
* PyPreConfig.coerce_c_locale (C member): PyPreConfig.       (line   82)
* PyPreConfig.coerce_c_locale_warn (C member): PyPreConfig.  (line   93)
* PyPreConfig.configure_locale (C member): PyPreConfig.      (line   71)
* PyPreConfig.dev_mode (C member):       PyPreConfig.        (line   99)
* PyPreConfig.isolated (C member):       PyPreConfig.        (line  106)
* PyPreConfig.legacy_windows_fs_encoding (C member): PyPreConfig.
                                                             (line  112)
* PyPreConfig.parse_argv (C member):     PyPreConfig.        (line  132)
* PyPreConfig.use_environment (C member): PyPreConfig.       (line  141)
* PyPreConfig.utf8_mode (C member):      PyPreConfig.        (line  148)
* PyProperty_Type (C var):               Descriptor（描述器）物件.
                                                             (line    9)
* PyRefTracer (C type):                  Reference tracing.  (line    8)
* PyRefTracer_CREATE (C var):            Reference tracing.  (line   21)
* PyRefTracer_DESTROY (C var):           Reference tracing.  (line   26)
* PyRefTracer_GetTracer (C function):    Reference tracing.  (line   48)
* PyRefTracer_SetTracer (C function):    Reference tracing.  (line   31)
* PyRun_AnyFile (C function):            The Very High Level Layer.
                                                             (line   47)
* PyRun_AnyFileEx (C function):          The Very High Level Layer.
                                                             (line   59)
* PyRun_AnyFileExFlags (C function):     The Very High Level Layer.
                                                             (line   65)
* PyRun_AnyFileFlags (C function):       The Very High Level Layer.
                                                             (line   53)
* PyRun_File (C function):               The Very High Level Layer.
                                                             (line  211)
* PyRun_FileEx (C function):             The Very High Level Layer.
                                                             (line  217)
* PyRun_FileExFlags (C function):        The Very High Level Layer.
                                                             (line  229)
* PyRun_FileFlags (C function):          The Very High Level Layer.
                                                             (line  223)
* PyRun_InteractiveLoop (C function):    The Very High Level Layer.
                                                             (line  142)
* PyRun_InteractiveLoopFlags (C function): The Very High Level Layer.
                                                             (line  148)
* PyRun_InteractiveOne (C function):     The Very High Level Layer.
                                                             (line  122)
* PyRun_InteractiveOneFlags (C function): The Very High Level Layer.
                                                             (line  128)
* PyRun_SimpleFile (C function):         The Very High Level Layer.
                                                             (line   97)
* PyRun_SimpleFileEx (C function):       The Very High Level Layer.
                                                             (line  103)
* PyRun_SimpleFileExFlags (C function):  The Very High Level Layer.
                                                             (line  109)
* PyRun_SimpleString (C function):       The Very High Level Layer.
                                                             (line   77)
* PyRun_SimpleStringFlags (C function):  The Very High Level Layer.
                                                             (line   83)
* PyRun_String (C function):             The Very High Level Layer.
                                                             (line  193)
* PyRun_StringFlags (C function):        The Very High Level Layer.
                                                             (line  198)
* PySendResult (C type):                 疊代器協議.         (line   51)
* PySeqIter_Check (C function):          疊代器（Iterator）物件.
                                                             (line   16)
* PySeqIter_New (C function):            疊代器（Iterator）物件.
                                                             (line   21)
* PySeqIter_Type (C var):                疊代器（Iterator）物件.
                                                             (line   11)
* PySequence_Check (C function):         序列協定.           (line    6)
* PySequence_Concat (C function):        序列協定.           (line   21)
* PySequence_Contains (C function):      序列協定.           (line   96)
* PySequence_Count (C function):         序列協定.           (line   89)
* PySequence_DelItem (C function):       序列協定.           (line   72)
* PySequence_DelSlice (C function):      序列協定.           (line   83)
* PySequence_Fast (C function):          序列協定.           (line  123)
* PySequence_Fast_GET_ITEM (C function): 序列協定.           (line  147)
* PySequence_Fast_GET_SIZE (C function): 序列協定.           (line  138)
* PySequence_Fast_ITEMS (C function):    序列協定.           (line  153)
* PySequence_GetItem (C function):       序列協定.           (line   48)
* PySequence_GetItem（C 函式）:          參照計數詳細資訊.   (line   96)
* PySequence_GetSlice (C function):      序列協定.           (line   54)
* PySequence_Index (C function):         序列協定.           (line  102)
* PySequence_InPlaceConcat (C function): 序列協定.           (line   34)
* PySequence_InPlaceRepeat (C function): 序列協定.           (line   41)
* PySequence_ITEM (C function):          序列協定.           (line  163)
* PySequence_Length (C function):        序列協定.           (line   14)
* PySequence_List (C function):          序列協定.           (line  108)
* PySequence_Repeat (C function):        序列協定.           (line   27)
* PySequence_SetItem (C function):       序列協定.           (line   61)
* PySequence_SetSlice (C function):      序列協定.           (line   77)
* PySequence_Size (C function):          序列協定.           (line   14)
* PySequence_Tuple (C function):         序列協定.           (line  114)
* PySequenceMethods (C type):            Sequence Object Structures.
                                                             (line    6)
* PySequenceMethods.sq_ass_item (C member): Sequence Object Structures.
                                                             (line   50)
* PySequenceMethods.sq_concat (C member): Sequence Object Structures.
                                                             (line   19)
* PySequenceMethods.sq_contains (C member): Sequence Object Structures.
                                                             (line   60)
* PySequenceMethods.sq_inplace_concat (C member): Sequence Object Structures.
                                                             (line   68)
* PySequenceMethods.sq_inplace_repeat (C member): Sequence Object Structures.
                                                             (line   79)
* PySequenceMethods.sq_item (C member):  Sequence Object Structures.
                                                             (line   34)
* PySequenceMethods.sq_length (C member): Sequence Object Structures.
                                                             (line   11)
* PySequenceMethods.sq_repeat (C member): Sequence Object Structures.
                                                             (line   26)
* PySet_Add (C function):                集合物件.           (line  117)
* PySet_Check (C function):              集合物件.           (line   44)
* PySet_CheckExact (C function):         集合物件.           (line   60)
* PySet_Clear (C function):              集合物件.           (line  148)
* PySet_Contains (C function):           集合物件.           (line  108)
* PySet_Discard (C function):            集合物件.           (line  131)
* PySet_GET_SIZE (C function):           集合物件.           (line  104)
* PySet_New (C function):                集合物件.           (line   78)
* PySet_Pop (C function):                集合物件.           (line  141)
* PySet_Size (C function):               集合物件.           (line   96)
* PySet_Type (C var):                    集合物件.           (line   31)
* PySetObject (C type):                  集合物件.           (line   19)
* PySignal_SetWakeupFd (C function):     Signal Handling<2>. (line   67)
* PySlice_AdjustIndices (C function):    切片物件.           (line   97)
* PySlice_Check (C function):            切片物件.           (line   11)
* PySlice_GetIndices (C function):       切片物件.           (line   27)
* PySlice_GetIndicesEx (C function):     切片物件.           (line   43)
* PySlice_New (C function):              切片物件.           (line   16)
* PySlice_Type (C var):                  切片物件.           (line    6)
* PySlice_Unpack (C function):           切片物件.           (line   84)
* PyState_AddModule (C function):        模組查找.           (line   24)
* PyState_FindModule (C function):       模組查找.           (line   15)
* PyState_RemoveModule (C function):     模組查找.           (line   47)
* PyStatus (C type):                     PyStatus.           (line    6)
* PyStatus_Error (C function):           PyStatus.           (line   34)
* PyStatus_Exception (C function):       PyStatus.           (line   51)
* PyStatus_Exit (C function):            PyStatus.           (line   45)
* PyStatus_IsError (C function):         PyStatus.           (line   57)
* PyStatus_IsExit (C function):          PyStatus.           (line   61)
* PyStatus_NoMemory (C function):        PyStatus.           (line   41)
* PyStatus_Ok (C function):              PyStatus.           (line   30)
* PyStatus.err_msg (C member):           PyStatus.           (line   20)
* PyStatus.exitcode (C member):          PyStatus.           (line   16)
* PyStatus.func (C member):              PyStatus.           (line   24)
* PyStructSequence_Desc (C type):        Struct Sequence Objects.
                                                             (line   33)
* PyStructSequence_Desc.doc (C member):  Struct Sequence Objects.
                                                             (line   41)
* PyStructSequence_Desc.fields (C member): Struct Sequence Objects.
                                                             (line   45)
* PyStructSequence_Desc.n_in_sequence (C member): Struct Sequence Objects.
                                                             (line   50)
* PyStructSequence_Desc.name (C member): Struct Sequence Objects.
                                                             (line   37)
* PyStructSequence_Field (C type):       Struct Sequence Objects.
                                                             (line   55)
* PyStructSequence_Field.doc (C member): Struct Sequence Objects.
                                                             (line   68)
* PyStructSequence_Field.name (C member): Struct Sequence Objects.
                                                             (line   62)
* PyStructSequence_GET_ITEM (C function): Struct Sequence Objects.
                                                             (line   94)
* PyStructSequence_GetItem (C function): Struct Sequence Objects.
                                                             (line   86)
* PyStructSequence_InitType (C function): Struct Sequence Objects.
                                                             (line   20)
* PyStructSequence_InitType2 (C function): Struct Sequence Objects.
                                                             (line   25)
* PyStructSequence_New (C function):     Struct Sequence Objects.
                                                             (line   78)
* PyStructSequence_NewType (C function): Struct Sequence Objects.
                                                             (line   11)
* PyStructSequence_SET_ITEM (C function): Struct Sequence Objects.
                                                             (line  114)
* PyStructSequence_SetItem (C function): Struct Sequence Objects.
                                                             (line  102)
* PyStructSequence_UnnamedField (C var): Struct Sequence Objects.
                                                             (line   72)
* PySys_AddAuditHook (C function):       系統函式.           (line  113)
* PySys_Audit (C function):              系統函式.           (line   73)
* PySys_AuditTuple (C function):         系統函式.           (line  105)
* PySys_FormatStderr (C function):       系統函式.           (line   59)
* PySys_FormatStdout (C function):       系統函式.           (line   51)
* PySys_GetObject (C function):          系統函式.           (line   11)
* PySys_GetXOptions (C function):        系統函式.           (line   65)
* PySys_ResetWarnOptions (C function):   系統函式.           (line   22)
* PySys_SetArgv (C function):            Process-wide parameters.
                                                             (line  266)
* PySys_SetArgvEx (C function):          Process-wide parameters.
                                                             (line  214)
* PySys_SetObject (C function):          系統函式.           (line   16)
* PySys_WriteStderr (C function):        系統函式.           (line   47)
* PySys_WriteStdout (C function):        系統函式.           (line   30)
* Python 3000:                           術語表.             (line 1046)
* Python Editor（Python 編輯器）:        IDLE<62>.           (line    8)
* Python Enhancement Proposals; PEP 1:   New Development Process.
                                                             (line   67)
* Python Enhancement Proposals; PEP 1 <1>: New Development Process.
                                                             (line   82)
* Python Enhancement Proposals; PEP 1 <2>: 術語表.           (line 1018)
* Python Enhancement Proposals; PEP 100: Unicode<2>.         (line   15)
* Python Enhancement Proposals; PEP 11:  Support for mobile platforms.
                                                             (line    6)
* Python Enhancement Proposals; PEP 11 <1>: Build Changes.   (line   33)
* Python Enhancement Proposals; PEP 11 <2>: Build Changes.   (line   36)
* Python Enhancement Proposals; PEP 11 <3>: 建置變更<2>.     (line    6)
* Python Enhancement Proposals; PEP 11 <4>: PEP 538 Legacy C Locale Coercion.
                                                             (line   19)
* Python Enhancement Proposals; PEP 11 <5>: Unsupported Operating Systems.
                                                             (line    6)
* Python Enhancement Proposals; PEP 11 <6>: 函式庫變更.      (line   15)
* Python Enhancement Proposals; PEP 11 <7>: Build<20>.       (line   56)
* Python Enhancement Proposals; PEP 11 <8>: Build<20>.       (line  107)
* Python Enhancement Proposals; PEP 11 <9>: Build<56>.       (line   14)
* Python Enhancement Proposals; PEP 11 <10>: 建置需求.       (line   47)
* Python Enhancement Proposals; PEP 11 <11>: 在 Windows 上使用 Python.
                                                             (line   18)
* Python Enhancement Proposals; PEP 11 <12>: 其他平台.       (line    8)
* Python Enhancement Proposals; PEP 11#tier-2: Summary -- Release Highlights.
                                                             (line  133)
* Python Enhancement Proposals; PEP 11#tier-3: Summary -- Release Highlights.
                                                             (line  130)
* Python Enhancement Proposals; PEP 11#tier-3 <1>: 建置變更<2>.
                                                             (line    6)
* Python Enhancement Proposals; PEP 201: New Development Process.
                                                             (line   86)
* Python Enhancement Proposals; PEP 205: PEP 205 Weak References.
                                                             (line   82)
* Python Enhancement Proposals; PEP 205 <1>: weakref --- 弱參照.
                                                             (line  290)
* Python Enhancement Proposals; PEP 207: PEP 207 Rich Comparisons.
                                                             (line   71)
* Python Enhancement Proposals; PEP 207 <1>: PEP 207 Rich Comparisons.
                                                             (line   77)
* Python Enhancement Proposals; PEP 208: PEP 208 New Coercion Model.
                                                             (line   30)
* Python Enhancement Proposals; PEP 217: PEP 217 Interactive Display Hook.
                                                             (line   27)
* Python Enhancement Proposals; PEP 218: PEP 218 Built-In Set Objects.
                                                             (line   50)
* Python Enhancement Proposals; PEP 218 <1>: 其他語言更動<16>.
                                                             (line   12)
* Python Enhancement Proposals; PEP 218 <2>: PEP 218 A Standard Set Datatype.
                                                             (line   81)
* Python Enhancement Proposals; PEP 227: PEP 227 Nested Scopes.
                                                             (line   96)
* Python Enhancement Proposals; PEP 227 <1>: PEP 227 Nested Scopes<2>.
                                                             (line   96)
* Python Enhancement Proposals; PEP 227 <2>: 模組內容<9>.    (line   13)
* Python Enhancement Proposals; PEP 229: PEP 229 New Build System.
                                                             (line   39)
* Python Enhancement Proposals; PEP 230: PEP 230 Warning Framework.
                                                             (line   73)
* Python Enhancement Proposals; PEP 232: PEP 232 Function Attributes.
                                                             (line   36)
* Python Enhancement Proposals; PEP 234: PEP 234：疊代器.    (line  124)
* Python Enhancement Proposals; PEP 235: 簡介<9>.            (line   51)
* Python Enhancement Proposals; PEP 236: PEP 227 Nested Scopes<2>.
                                                             (line   87)
* Python Enhancement Proposals; PEP 236 <1>: PEP 227 Nested Scopes<2>.
                                                             (line   88)
* Python Enhancement Proposals; PEP 236 <2>: PEP 236 __future__ Directives.
                                                             (line   29)
* Python Enhancement Proposals; PEP 236 <3>: Future statements.
                                                             (line   85)
* Python Enhancement Proposals; PEP 236 <4>: 模組內容<9>.    (line   95)
* Python Enhancement Proposals; PEP 237: 整數.               (line    6)
* Python Enhancement Proposals; PEP 237 <1>: PEP 237 Unifying Long Integers and Integers.
                                                             (line   22)
* Python Enhancement Proposals; PEP 237 <2>: 其他語言更動<16>.
                                                             (line   18)
* Python Enhancement Proposals; PEP 237 <3>: PEP 237 Unifying Long Integers and Integers<2>.
                                                             (line   37)
* Python Enhancement Proposals; PEP 237 <4>: printf-style String Formatting.
                                                             (line  185)
* Python Enhancement Proposals; PEP 237 <5>: printf-style Bytes Formatting.
                                                             (line  189)
* Python Enhancement Proposals; PEP 238: 整數.               (line   10)
* Python Enhancement Proposals; PEP 238 <1>: PEP 238 Changing the Division Operator.
                                                             (line   21)
* Python Enhancement Proposals; PEP 238 <2>: PEP 238 Changing the Division Operator.
                                                             (line   27)
* Python Enhancement Proposals; PEP 238 <3>: PEP 238 Changing the Division Operator.
                                                             (line   68)
* Python Enhancement Proposals; PEP 238 <4>: 模組內容<9>.    (line   20)
* Python Enhancement Proposals; PEP 238 <5>: The Very High Level Layer.
                                                             (line  371)
* Python Enhancement Proposals; PEP 238 <6>: 術語表.         (line  437)
* Python Enhancement Proposals; PEP 241: PEP 241 Metadata in Python Packages.
                                                             (line   16)
* Python Enhancement Proposals; PEP 241 <1>: PEP 241 Metadata in Python Packages.
                                                             (line   29)
* Python Enhancement Proposals; PEP 241 <2>: PEP 241 Metadata in Python Packages.
                                                             (line   36)
* Python Enhancement Proposals; PEP 243: PEP 241 Metadata in Python Packages.
                                                             (line   40)
* Python Enhancement Proposals; PEP 246: Documentation<15>.  (line   48)
* Python Enhancement Proposals; PEP 246 <1>: PrepareProtocol 物件.
                                                             (line    8)
* Python Enhancement Proposals; PEP 247: hmac<3>.            (line   20)
* Python Enhancement Proposals; PEP 249: sqlite3<2>.         (line   11)
* Python Enhancement Proposals; PEP 249 <1>: sqlite3 套件.   (line   18)
* Python Enhancement Proposals; PEP 249 <2>: sqlite3 套件.   (line  110)
* Python Enhancement Proposals; PEP 249 <3>: Library<19>.    (line  121)
* Python Enhancement Proposals; PEP 249 <4>: Library<22>.    (line  296)
* Python Enhancement Proposals; PEP 249 <5>: sqlite3 --- SQLite 資料庫的 DB-API 2 0 介面.
                                                             (line   16)
* Python Enhancement Proposals; PEP 249 <6>: sqlite3 --- SQLite 資料庫的 DB-API 2 0 介面.
                                                             (line   41)
* Python Enhancement Proposals; PEP 249 <7>: Module functions.
                                                             (line   75)
* Python Enhancement Proposals; PEP 249 <8>: Connection 物件.
                                                             (line  730)
* Python Enhancement Proposals; PEP 249 <9>: Connection 物件.
                                                             (line  733)
* Python Enhancement Proposals; PEP 249 <10>: Connection 物件.
                                                             (line  745)
* Python Enhancement Proposals; PEP 249 <11>: 例外<4>.       (line    6)
* Python Enhancement Proposals; PEP 249 <12>: How to use placeholders to bind values in SQL queries.
                                                             (line   53)
* Python Enhancement Proposals; PEP 249 <13>: Transaction control via the autocommit attribute.
                                                             (line   10)
* Python Enhancement Proposals; PEP 249 <14>: Transaction control via the autocommit attribute.
                                                             (line   30)
* Python Enhancement Proposals; PEP 252: 相關連結.           (line   17)
* Python Enhancement Proposals; PEP 252 <1>: 相關連結.       (line   17)
* Python Enhancement Proposals; PEP 252 <2>: Implementing Descriptors.
                                                             (line   24)
* Python Enhancement Proposals; PEP 253: Old and New Classes.
                                                             (line   28)
* Python Enhancement Proposals; PEP 253 <1>: Multiple Inheritance The Diamond Rule.
                                                             (line    8)
* Python Enhancement Proposals; PEP 253 <2>: 相關連結.       (line   17)
* Python Enhancement Proposals; PEP 253 <3>: 相關連結.       (line   19)
* Python Enhancement Proposals; PEP 253 <4>: 相關連結.       (line   21)
* Python Enhancement Proposals; PEP 255: PEP 255 Simple Generators.
                                                             (line   45)
* Python Enhancement Proposals; PEP 255 <1>: PEP 255 Simple Generators.
                                                             (line  131)
* Python Enhancement Proposals; PEP 255 <2>: PEP 255 Simple Generators<2>.
                                                             (line   43)
* Python Enhancement Proposals; PEP 255 <3>: PEP 255 Simple Generators<2>.
                                                             (line  129)
* Python Enhancement Proposals; PEP 255 <4>: Yield expressions.
                                                             (line   89)
* Python Enhancement Proposals; PEP 255 <5>: 模組內容<9>.    (line   17)
* Python Enhancement Proposals; PEP 261: Unicode 變更.       (line   18)
* Python Enhancement Proposals; PEP 261 <1>: Unicode 變更.   (line   61)
* Python Enhancement Proposals; PEP 263: 其他語言更動<15>.   (line   99)
* Python Enhancement Proposals; PEP 263 <1>: PEP 263 Source Code Encodings.
                                                             (line   29)
* Python Enhancement Proposals; PEP 263 <2>: Core and Builtins<27>.
                                                             (line   84)
* Python Enhancement Proposals; PEP 263 <3>: 簡介<9>.        (line   55)
* Python Enhancement Proposals; PEP 263 <4>: Tokenizing Input.
                                                             (line   35)
* Python Enhancement Proposals; PEP 263 <5>: Tokenizing Input.
                                                             (line   89)
* Python Enhancement Proposals; PEP 263 <6>: Unicode Literals in Python Source Code.
                                                             (line   48)
* Python Enhancement Proposals; PEP 264: 其他改動與修正.     (line   55)
* Python Enhancement Proposals; PEP 273: PEP 273 Importing Modules from ZIP Archives.
                                                             (line   41)
* Python Enhancement Proposals; PEP 273 <1>: PEP 273 Importing Modules from ZIP Archives.
                                                             (line   44)
* Python Enhancement Proposals; PEP 273 <2>: zipimport --- 從 Zip 封存檔案匯入模組.
                                                             (line   44)
* Python Enhancement Proposals; PEP 273 <3>: zipimport --- 從 Zip 封存檔案匯入模組.
                                                             (line   47)
* Python Enhancement Proposals; PEP 274: New Syntax.         (line   38)
* Python Enhancement Proposals; PEP 277: PEP 277 Unicode file name support for Windows NT.
                                                             (line   32)
* Python Enhancement Proposals; PEP 278: PEP 278 Universal Newline Support.
                                                             (line   33)
* Python Enhancement Proposals; PEP 278 <1>: 術語表.         (line 1283)
* Python Enhancement Proposals; PEP 279: PEP 279：enumerate. (line   27)
* Python Enhancement Proposals; PEP 282: PEP 282 The logging Package.
                                                             (line  105)
* Python Enhancement Proposals; PEP 282 <1>: PEP 282 The logging Package.
                                                             (line  111)
* Python Enhancement Proposals; PEP 282 <2>: Archiving operations.
                                                             (line   47)
* Python Enhancement Proposals; PEP 282 <3>: Integration with the warnings module.
                                                             (line   36)
* Python Enhancement Proposals; PEP 285: PEP 285 A Boolean Type.
                                                             (line   47)
* Python Enhancement Proposals; PEP 285 <1>: PEP 285 A Boolean Type.
                                                             (line   70)
* Python Enhancement Proposals; PEP 288: PEP 342 New Generator Features.
                                                             (line  146)
* Python Enhancement Proposals; PEP 289: PEP 289 Generator Expressions.
                                                             (line   55)
* Python Enhancement Proposals; PEP 289 <1>: 其他語言更動<16>.
                                                             (line   15)
* Python Enhancement Proposals; PEP 289 <2>: Python 說明文件.
                                                             (line   12)
* Python Enhancement Proposals; PEP 292: PEP 292 Simpler String Substitutions.
                                                             (line   45)
* Python Enhancement Proposals; PEP 292 <1>: 模板字串.       (line    6)
* Python Enhancement Proposals; PEP 293: PEP 293 Codec Error Handling Callbacks.
                                                             (line   33)
* Python Enhancement Proposals; PEP 3000: Python 3 0.        (line   43)
* Python Enhancement Proposals; PEP 301: PEP 301 Package Index and Metadata for Distutils.
                                                             (line   45)
* Python Enhancement Proposals; PEP 302: 使用 importlib 作為 import 的實作.
                                                             (line   13)
* Python Enhancement Proposals; PEP 302 <1>: 明顯的變更.     (line   18)
* Python Enhancement Proposals; PEP 302 <2>: 移植 Python 程式碼.
                                                             (line   71)
* Python Enhancement Proposals; PEP 302 <3>: New Improved and Deprecated Modules<2>.
                                                             (line  106)
* Python Enhancement Proposals; PEP 302 <4>: New Improved and Removed Modules.
                                                             (line  288)
* Python Enhancement Proposals; PEP 302 <5>: PEP 273 Importing Modules from ZIP Archives.
                                                             (line   46)
* Python Enhancement Proposals; PEP 302 <6>: PEP 302 New Import Hooks.
                                                             (line   13)
* Python Enhancement Proposals; PEP 302 <7>: PEP 302 New Import Hooks.
                                                             (line   38)
* Python Enhancement Proposals; PEP 302 <8>: PEP 302 New Import Hooks.
                                                             (line   62)
* Python Enhancement Proposals; PEP 302 <9>: 模組引入系統.   (line   42)
* Python Enhancement Proposals; PEP 302 <10>: References.    (line   10)
* Python Enhancement Proposals; PEP 302 <11>: 內建函式.      (line 1990)
* Python Enhancement Proposals; PEP 302 <12>: linecache --- 隨機存取文字列.
                                                             (line   31)
* Python Enhancement Proposals; PEP 302 <13>: sys --- 系統特定的參數與函式.
                                                             (line 1322)
* Python Enhancement Proposals; PEP 302 <14>: sys --- 系統特定的參數與函式.
                                                             (line 1332)
* Python Enhancement Proposals; PEP 302 <15>: zipimport --- 從 Zip 封存檔案匯入模組.
                                                             (line   49)
* Python Enhancement Proposals; PEP 302 <16>: pkgutil --- 套件擴充工具程式.
                                                             (line   54)
* Python Enhancement Proposals; PEP 302 <17>: pkgutil --- 套件擴充工具程式.
                                                             (line   72)
* Python Enhancement Proposals; PEP 302 <18>: pkgutil --- 套件擴充工具程式.
                                                             (line   83)
* Python Enhancement Proposals; PEP 302 <19>: pkgutil --- 套件擴充工具程式.
                                                             (line  104)
* Python Enhancement Proposals; PEP 302 <20>: pkgutil --- 套件擴充工具程式.
                                                             (line  121)
* Python Enhancement Proposals; PEP 302 <21>: pkgutil --- 套件擴充工具程式.
                                                             (line  154)
* Python Enhancement Proposals; PEP 302 <22>: runpy --- 定位並執行 Python 模組.
                                                             (line   32)
* Python Enhancement Proposals; PEP 302 <23>: 簡介<9>.       (line   59)
* Python Enhancement Proposals; PEP 302 <24>: importlib abc -- Abstract base classes related to import.
                                                             (line   93)
* Python Enhancement Proposals; PEP 302 <25>: importlib abc -- Abstract base classes related to import.
                                                             (line  208)
* Python Enhancement Proposals; PEP 302 <26>: importlib abc -- Abstract base classes related to import.
                                                             (line  232)
* Python Enhancement Proposals; PEP 302 <27>: importlib abc -- Abstract base classes related to import.
                                                             (line  302)
* Python Enhancement Proposals; PEP 302 <28>: 術語表.        (line  757)
* Python Enhancement Proposals; PEP 305: PEP 305 Comma-separated Files.
                                                             (line   42)
* Python Enhancement Proposals; PEP 305 <1>: csv --- CSV 檔案讀取及寫入.
                                                             (line   31)
* Python Enhancement Proposals; PEP 307: PEP 307 Pickle Enhancements.
                                                             (line    8)
* Python Enhancement Proposals; PEP 307 <1>: PEP 307 Pickle Enhancements.
                                                             (line   30)
* Python Enhancement Proposals; PEP 307 <2>: PEP 307 Pickle Enhancements.
                                                             (line   42)
* Python Enhancement Proposals; PEP 307 <3>: Data stream format.
                                                             (line   32)
* Python Enhancement Proposals; PEP 308: PEP 308 Conditional Expressions.
                                                             (line   72)
* Python Enhancement Proposals; PEP 308 <1>: PEP 308 Conditional Expressions.
                                                             (line   78)
* Python Enhancement Proposals; PEP 308 <2>: Conditional expressions.
                                                             (line   16)
* Python Enhancement Proposals; PEP 309: PEP 309 Partial Function Application.
                                                             (line   73)
* Python Enhancement Proposals; PEP 3100: Python 3 0.        (line   44)
* Python Enhancement Proposals; PEP 3101: PEP 3101 A New Approach To String Formatting.
                                                             (line    3)
* Python Enhancement Proposals; PEP 3101 <1>: PEP 3101 A New Approach To String Formatting.
                                                             (line    8)
* Python Enhancement Proposals; PEP 3101 <2>: PEP 3101 Advanced String Formatting.
                                                             (line  161)
* Python Enhancement Proposals; PEP 3101 <3>: 自訂字串格式.  (line    6)
* Python Enhancement Proposals; PEP 3101 <4>: 自訂字串格式.  (line   56)
* Python Enhancement Proposals; PEP 3102: New Syntax.        (line   13)
* Python Enhancement Proposals; PEP 3104: New Syntax.        (line   24)
* Python Enhancement Proposals; PEP 3104 <1>: nonlocal 陳述式.
                                                             (line   24)
* Python Enhancement Proposals; PEP 3105: Print Is A Function.
                                                             (line    8)
* Python Enhancement Proposals; PEP 3105 <1>: PEP 3105 print As a Function.
                                                             (line   35)
* Python Enhancement Proposals; PEP 3105 <2>: 模組內容<9>.   (line   32)
* Python Enhancement Proposals; PEP 3106: PEP 3106 Dictionary Views.
                                                             (line   58)
* Python Enhancement Proposals; PEP 3107: PEP 563 Postponed Evaluation of Annotations.
                                                             (line    7)
* Python Enhancement Proposals; PEP 3107 <1>: PEP 484 - Type Hints.
                                                             (line    7)
* Python Enhancement Proposals; PEP 3107 <2>: New Syntax.    (line    6)
* Python Enhancement Proposals; PEP 3107 <3>: 函式註釋 Function Annotations.
                                                             (line    7)
* Python Enhancement Proposals; PEP 3107 <4>: 函式定義.      (line  140)
* Python Enhancement Proposals; PEP 3108: 函式庫變更.        (line    7)
* Python Enhancement Proposals; PEP 3108 <1>: 函式庫變更.    (line   17)
* Python Enhancement Proposals; PEP 3108 <2>: 函式庫變更.    (line   95)
* Python Enhancement Proposals; PEP 3109: 語法變更.          (line    6)
* Python Enhancement Proposals; PEP 3109 <1>: Changes To Exceptions.
                                                             (line   29)
* Python Enhancement Proposals; PEP 3110: 語法變更.          (line   16)
* Python Enhancement Proposals; PEP 3110 <1>: Changes To Exceptions.
                                                             (line   35)
* Python Enhancement Proposals; PEP 3110 <2>: PEP 3110 Exception-Handling Changes.
                                                             (line   48)
* Python Enhancement Proposals; PEP 3111: Builtins.          (line   12)
* Python Enhancement Proposals; PEP 3112: PEP 3112 Byte Literals.
                                                             (line   75)
* Python Enhancement Proposals; PEP 3112 <1>: 模組內容<9>.   (line   36)
* Python Enhancement Proposals; PEP 3113: 已被移除的語法.    (line    6)
* Python Enhancement Proposals; PEP 3114: Operators And Special Methods.
                                                             (line   19)
* Python Enhancement Proposals; PEP 3115: types<7>.          (line   10)
* Python Enhancement Proposals; PEP 3115 <1>: 語法變更.      (line   18)
* Python Enhancement Proposals; PEP 3115 <2>: Preparing the class namespace.
                                                             (line   21)
* Python Enhancement Proposals; PEP 3115 <3>: 類別定義.      (line   83)
* Python Enhancement Proposals; PEP 3115 <4>: Dynamic Type Creation.
                                                             (line   53)
* Python Enhancement Proposals; PEP 3116: 最佳化<11>.        (line    8)
* Python Enhancement Proposals; PEP 3116 <1>: PEP 3116 New I/O Library.
                                                             (line   69)
* Python Enhancement Proposals; PEP 3116 <2>: 術語表.        (line 1283)
* Python Enhancement Proposals; PEP 3118: Pickle protocol 5 with out-of-band data buffers.
                                                             (line   13)
* Python Enhancement Proposals; PEP 3118 <1>: PEP 3118 New memoryview implementation and buffer protocol documentation.
                                                             (line    6)
* Python Enhancement Proposals; PEP 3118 <2>: API 變更.      (line   29)
* Python Enhancement Proposals; PEP 3118 <3>: 建置和 C API 更改.
                                                             (line    8)
* Python Enhancement Proposals; PEP 3118 <4>: Build and C API Changes<6>.
                                                             (line   12)
* Python Enhancement Proposals; PEP 3118 <5>: PEP 3118：修訂緩衝協定.
                                                             (line   46)
* Python Enhancement Proposals; PEP 3118 <6>: Library<59>.   (line   99)
* Python Enhancement Proposals; PEP 3118 <7>: Library<64>.   (line   61)
* Python Enhancement Proposals; PEP 3118 <8>: Library<93>.   (line  958)
* Python Enhancement Proposals; PEP 3118 <9>: Memory Views.  (line  114)
* Python Enhancement Proposals; PEP 3119: PEP 3119 Abstract Base Classes.
                                                             (line  139)
* Python Enhancement Proposals; PEP 3119 <1>: Customizing instance and subclass checks.
                                                             (line   35)
* Python Enhancement Proposals; PEP 3119 <2>: Examples and Recipes.
                                                             (line   73)
* Python Enhancement Proposals; PEP 3119 <3>: abc --- 抽象基底類別.
                                                             (line   10)
* Python Enhancement Proposals; PEP 3119 <4>: 物件協定.      (line  376)
* Python Enhancement Proposals; PEP 3119 <5>: 物件協定.      (line  395)
* Python Enhancement Proposals; PEP 3120: Text Vs Data Instead Of Unicode Vs 8-bit.
                                                             (line  107)
* Python Enhancement Proposals; PEP 3120 <1>: 詞法分析.      (line   12)
* Python Enhancement Proposals; PEP 3120 <2>: 簡介<9>.       (line   91)
* Python Enhancement Proposals; PEP 3121: Build and C API Changes<6>.
                                                             (line   14)
* Python Enhancement Proposals; PEP 3121 <1>: Core and Builtins<37>.
                                                             (line  230)
* Python Enhancement Proposals; PEP 3121 <2>: 初始化 C 模組. (line   56)
* Python Enhancement Proposals; PEP 3123: Build and C API Changes<6>.
                                                             (line   16)
* Python Enhancement Proposals; PEP 3127: PEP 3127 Integer Literal Support and Syntax.
                                                             (line   47)
* Python Enhancement Proposals; PEP 3129: PEP 3129 Class Decorators.
                                                             (line   24)
* Python Enhancement Proposals; PEP 3129 <1>: 函式定義.      (line  162)
* Python Enhancement Proposals; PEP 3129 <2>: 類別定義.      (line   89)
* Python Enhancement Proposals; PEP 3131: Text Vs Data Instead Of Unicode Vs 8-bit.
                                                             (line  109)
* Python Enhancement Proposals; PEP 3131 <1>: Library<48>.   (line  599)
* Python Enhancement Proposals; PEP 3131 <2>: Identifiers and keywords.
                                                             (line   10)
* Python Enhancement Proposals; PEP 3131 <3>: Identifiers and keywords.
                                                             (line   19)
* Python Enhancement Proposals; PEP 3132: New Syntax.        (line   28)
* Python Enhancement Proposals; PEP 3132 <1>: Assignment statements.
                                                             (line  158)
* Python Enhancement Proposals; PEP 3134: 語法變更.          (line    6)
* Python Enhancement Proposals; PEP 3134 <1>: Changes To Exceptions.
                                                             (line   40)
* Python Enhancement Proposals; PEP 3134 <2>: Changes To Exceptions.
                                                             (line   61)
* Python Enhancement Proposals; PEP 3134 <3>: Library<22>.   (line   48)
* Python Enhancement Proposals; PEP 3134 <4>: 基底類別 base classes.
                                                             (line   24)
* Python Enhancement Proposals; PEP 3135: Builtins.          (line    6)
* Python Enhancement Proposals; PEP 3135 <1>: Creating the class object.
                                                             (line   52)
* Python Enhancement Proposals; PEP 3137: PEP 3137 The memoryview Object.
                                                             (line   49)
* Python Enhancement Proposals; PEP 3138: Text Vs Data Instead Of Unicode Vs 8-bit.
                                                             (line  103)
* Python Enhancement Proposals; PEP 314: PEP 314 Metadata for Python Software Packages v1 1.
                                                             (line   42)
* Python Enhancement Proposals; PEP 3141: PEP 3141 A Type Hierarchy for Numbers.
                                                             (line   43)
* Python Enhancement Proposals; PEP 3141 <1>: numbers --- 數值的抽象基底類別.
                                                             (line   10)
* Python Enhancement Proposals; PEP 3141 <2>: abc --- 抽象基底類別.
                                                             (line   12)
* Python Enhancement Proposals; PEP 3144: ipaddress<6>.      (line   10)
* Python Enhancement Proposals; PEP 3147: PEP 421：新增 sys implementation.
                                                             (line   21)
* Python Enhancement Proposals; PEP 3147 <1>: PEP 3147 PYC Repository Directories.
                                                             (line   69)
* Python Enhancement Proposals; PEP 3147 <2>: 「編譯」Python 檔案.
                                                             (line   35)
* Python Enhancement Proposals; PEP 3147 <3>: Import-related module attributes.
                                                             (line  103)
* Python Enhancement Proposals; PEP 3147 <4>: test support import_helper --- 用於 import 測試的工具.
                                                             (line   80)
* Python Enhancement Proposals; PEP 3147 <5>: runpy --- 定位並執行 Python 模組.
                                                             (line   86)
* Python Enhancement Proposals; PEP 3147 <6>: 簡介<9>.       (line   95)
* Python Enhancement Proposals; PEP 3147 <7>: importlib util -- Utility code for importers.
                                                             (line   24)
* Python Enhancement Proposals; PEP 3147 <8>: importlib util -- Utility code for importers.
                                                             (line   60)
* Python Enhancement Proposals; PEP 3147 <9>: importlib util -- Utility code for importers.
                                                             (line   64)
* Python Enhancement Proposals; PEP 3147 <10>: py_compile — 編譯 Python 來源檔案.
                                                             (line   30)
* Python Enhancement Proposals; PEP 3147 <11>: py_compile — 編譯 Python 來源檔案.
                                                             (line   70)
* Python Enhancement Proposals; PEP 3147 <12>: Command-line use.
                                                             (line   63)
* Python Enhancement Proposals; PEP 3147 <13>: Public functions.
                                                             (line   40)
* Python Enhancement Proposals; PEP 3147 <14>: Public functions.
                                                             (line  119)
* Python Enhancement Proposals; PEP 3147 <15>: 引入模組<2>.  (line  212)
* Python Enhancement Proposals; PEP 3147 <16>: 如何建立 pyc 檔案？.
                                                             (line   12)
* Python Enhancement Proposals; PEP 3148: PEP 3148：concurrent futures 模組.
                                                             (line   51)
* Python Enhancement Proposals; PEP 3148 <1>: 模組函式.      (line   50)
* Python Enhancement Proposals; PEP 3149: PEP 3149 ABI Version Tagged so Files.
                                                             (line   33)
* Python Enhancement Proposals; PEP 3149 <1>: Core and Builtins<91>.
                                                             (line    9)
* Python Enhancement Proposals; PEP 3149 <2>: sys --- 系統特定的參數與函式.
                                                             (line   15)
* Python Enhancement Proposals; PEP 3151: PEP 3151 Reworking the OS and IO exception hierarchy.
                                                             (line   84)
* Python Enhancement Proposals; PEP 3151 <1>: 作業系統例外.  (line  113)
* Python Enhancement Proposals; PEP 3151 <2>: 例外<10>.      (line   10)
* Python Enhancement Proposals; PEP 3151 <3>: select --- 等待 I/O 完成.
                                                             (line   33)
* Python Enhancement Proposals; PEP 3151 <4>: resource --- 資源使用資訊.
                                                             (line   23)
* Python Enhancement Proposals; PEP 3151 <5>: Standard Exceptions.
                                                             (line  181)
* Python Enhancement Proposals; PEP 3154: Summary -- Release Highlights<3>.
                                                             (line   57)
* Python Enhancement Proposals; PEP 3154 <1>: pickle<4>.     (line   16)
* Python Enhancement Proposals; PEP 3154 <2>: Library<48>.   (line 1279)
* Python Enhancement Proposals; PEP 3154 <3>: Data stream format.
                                                             (line   42)
* Python Enhancement Proposals; PEP 3155: PEP 3155 Qualified name for classes and functions.
                                                             (line   63)
* Python Enhancement Proposals; PEP 3155 <1>: 術語表.        (line 1072)
* Python Enhancement Proposals; PEP 3156: Summary -- Release Highlights<3>.
                                                             (line   31)
* Python Enhancement Proposals; PEP 3156 <1>: Summary -- Release Highlights<3>.
                                                             (line   44)
* Python Enhancement Proposals; PEP 3156 <2>: asyncio<11>.   (line    6)
* Python Enhancement Proposals; PEP 3156 <3>: asyncio<11>.   (line   17)
* Python Enhancement Proposals; PEP 3156 <4>: selectors<2>.  (line    6)
* Python Enhancement Proposals; PEP 318: PEP 318 Decorators for Functions and Methods.
                                                             (line  101)
* Python Enhancement Proposals; PEP 318 <1>: PEP 318 Decorators for Functions and Methods.
                                                             (line  125)
* Python Enhancement Proposals; PEP 318 <2>: 其他語言更動<16>.
                                                             (line    9)
* Python Enhancement Proposals; PEP 318 <3>: 函式定義.       (line  159)
* Python Enhancement Proposals; PEP 318 <4>: 類別定義.       (line   92)
* Python Enhancement Proposals; PEP 322: PEP 322 Reverse Iteration.
                                                             (line   35)
* Python Enhancement Proposals; PEP 322 <1>: 其他語言更動<16>.
                                                             (line   13)
* Python Enhancement Proposals; PEP 324: PEP 324 New subprocess Module.
                                                             (line   86)
* Python Enhancement Proposals; PEP 324 <1>: subprocess --- 子行程管理.
                                                             (line   25)
* Python Enhancement Proposals; PEP 325: PEP 342 New Generator Features.
                                                             (line  147)
* Python Enhancement Proposals; PEP 327: Context 型別.       (line   56)
* Python Enhancement Proposals; PEP 328: 移植 Python 程式碼. (line   36)
* Python Enhancement Proposals; PEP 328 <1>: 已被移除的語法. (line   29)
* Python Enhancement Proposals; PEP 328 <2>: PEP 328 Absolute and Relative Imports.
                                                             (line    6)
* Python Enhancement Proposals; PEP 328 <3>: PEP 328 Absolute and Relative Imports.
                                                             (line   82)
* Python Enhancement Proposals; PEP 328 <4>: PEP 328 Multi-line Imports.
                                                             (line   35)
* Python Enhancement Proposals; PEP 328 <5>: 其他語言更動<16>.
                                                             (line   21)
* Python Enhancement Proposals; PEP 328 <6>: References.     (line   20)
* Python Enhancement Proposals; PEP 328 <7>: 內建函式.       (line 2008)
* Python Enhancement Proposals; PEP 328 <8>: 模組內容<9>.    (line   24)
* Python Enhancement Proposals; PEP 328 <9>: 簡介<9>.        (line   63)
* Python Enhancement Proposals; PEP 331: PEP 331 Locale-Independent Float/String Conversions.
                                                             (line   38)
* Python Enhancement Proposals; PEP 333: wsgiref 套件.       (line    8)
* Python Enhancement Proposals; PEP 333 <1>: wsgiref 套件.   (line   31)
* Python Enhancement Proposals; PEP 3333: 新增模組<2>.       (line    9)
* Python Enhancement Proposals; PEP 3333 <1>: PEP 3333 Python Web Server Gateway Interface v1 0 1.
                                                             (line   50)
* Python Enhancement Proposals; PEP 3333 <2>: wsgiref --- WSGI 工具與參考實作.
                                                             (line   21)
* Python Enhancement Proposals; PEP 3333 <3>: wsgiref util -- WSGI 環境工具.
                                                             (line    7)
* Python Enhancement Proposals; PEP 3333 <4>: wsgiref util -- WSGI 環境工具.
                                                             (line    8)
* Python Enhancement Proposals; PEP 3333 <5>: wsgiref util -- WSGI 環境工具.
                                                             (line   24)
* Python Enhancement Proposals; PEP 3333 <6>: wsgiref util -- WSGI 環境工具.
                                                             (line   61)
* Python Enhancement Proposals; PEP 3333 <7>: wsgiref headers -- WSGI 回應標頭工具.
                                                             (line   11)
* Python Enhancement Proposals; PEP 3333 <8>: wsgiref simple_server -- 一個簡單的 WSGI HTTP 伺服器.
                                                             (line   17)
* Python Enhancement Proposals; PEP 3333 <9>: wsgiref simple_server -- 一個簡單的 WSGI HTTP 伺服器.
                                                             (line   85)
* Python Enhancement Proposals; PEP 3333 <10>: wsgiref validate --- WSGI 符合性檢查.
                                                             (line   11)
* Python Enhancement Proposals; PEP 3333 <11>: wsgiref validate --- WSGI 符合性檢查.
                                                             (line   31)
* Python Enhancement Proposals; PEP 3333 <12>: wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  196)
* Python Enhancement Proposals; PEP 3333 <13>: wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  210)
* Python Enhancement Proposals; PEP 3333 <14>: wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  216)
* Python Enhancement Proposals; PEP 3333 <15>: wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  225)
* Python Enhancement Proposals; PEP 3333 <16>: wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  261)
* Python Enhancement Proposals; PEP 3333 <17>: wsgiref types -- 用於靜態型別檢查的 WSGI 型別.
                                                             (line    6)
* Python Enhancement Proposals; PEP 3333 <18>: wsgiref types -- 用於靜態型別檢查的 WSGI 型別.
                                                             (line   13)
* Python Enhancement Proposals; PEP 338: PEP 338 Executing Modules as Scripts.
                                                             (line   21)
* Python Enhancement Proposals; PEP 338 <1>: 介面選項.       (line  100)
* Python Enhancement Proposals; PEP 338 <2>: References.     (line   24)
* Python Enhancement Proposals; PEP 338 <3>: runpy --- 定位並執行 Python 模組.
                                                             (line  176)
* Python Enhancement Proposals; PEP 339: Build and C API Changes<9>.
                                                             (line   46)
* Python Enhancement Proposals; PEP 341: PEP 341 Unified try/except/finally.
                                                             (line   44)
* Python Enhancement Proposals; PEP 342: PEP 342 New Generator Features.
                                                             (line   42)
* Python Enhancement Proposals; PEP 342 <1>: PEP 342 New Generator Features.
                                                             (line  140)
* Python Enhancement Proposals; PEP 342 <2>: Porting to Python 2 5.
                                                             (line   15)
* Python Enhancement Proposals; PEP 342 <3>: Yield expressions.
                                                             (line   94)
* Python Enhancement Proposals; PEP 342 <4>: Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line   59)
* Python Enhancement Proposals; PEP 342 <5>: Passing values into a generator.
                                                             (line   25)
* Python Enhancement Proposals; PEP 342 <6>: Python 說明文件.
                                                             (line   14)
* Python Enhancement Proposals; PEP 343: contextlib 模組.    (line   64)
* Python Enhancement Proposals; PEP 343 <1>: PEP 342 New Generator Features.
                                                             (line  129)
* Python Enhancement Proposals; PEP 343 <2>: contextlib 模組<2>.
                                                             (line   64)
* Python Enhancement Proposals; PEP 343 <3>: With Statement Context Managers.
                                                             (line   45)
* Python Enhancement Proposals; PEP 343 <4>: The with statement.
                                                             (line  111)
* Python Enhancement Proposals; PEP 343 <5>: Using a context manager as a function decorator.
                                                             (line   51)
* Python Enhancement Proposals; PEP 343 <6>: 模組內容<9>.    (line   28)
* Python Enhancement Proposals; PEP 343 <7>: 術語表.         (line  244)
* Python Enhancement Proposals; PEP 347: Build and C API Changes<9>.
                                                             (line   10)
* Python Enhancement Proposals; PEP 352: Changes To Exceptions.
                                                             (line    9)
* Python Enhancement Proposals; PEP 352 <1>: Deprecations and Removals.
                                                             (line    9)
* Python Enhancement Proposals; PEP 352 <2>: PEP 352 Exceptions as New-Style Classes.
                                                             (line   57)
* Python Enhancement Proposals; PEP 353: 移植到 Python 3 10<2>.
                                                             (line    9)
* Python Enhancement Proposals; PEP 353 <1>: PEP 353 Using ssize_t as the index type.
                                                             (line   49)
* Python Enhancement Proposals; PEP 353 <2>: PEP 353 Using ssize_t as the index type.
                                                             (line   55)
* Python Enhancement Proposals; PEP 353 <3>: Build and C API Changes<9>.
                                                             (line   20)
* Python Enhancement Proposals; PEP 353 <4>: C API<35>.      (line   78)
* Python Enhancement Proposals; PEP 353 <5>: 型別.           (line   14)
* Python Enhancement Proposals; PEP 356: Python 2 5 有什麼新功能.
                                                             (line   10)
* Python Enhancement Proposals; PEP 357: PEP 357 The '__index__' method.
                                                             (line   39)
* Python Enhancement Proposals; PEP 361: Python 2 6 有什麼新功能.
                                                             (line   10)
* Python Enhancement Proposals; PEP 362: PEP 362：函式簽名物件.
                                                             (line   19)
* Python Enhancement Proposals; PEP 362 <1>: Introspecting callables with the Signature object.
                                                             (line  398)
* Python Enhancement Proposals; PEP 362 <2>: 術語表.         (line   77)
* Python Enhancement Proposals; PEP 362 <3>: 術語表.         (line  969)
* Python Enhancement Proposals; PEP 366: 明顯的變更.         (line   24)
* Python Enhancement Proposals; PEP 366 <1>: Import-related module attributes.
                                                             (line   41)
* Python Enhancement Proposals; PEP 366 <2>: Import-related module attributes.
                                                             (line   45)
* Python Enhancement Proposals; PEP 366 <3>: References.     (line   17)
* Python Enhancement Proposals; PEP 366 <4>: References.     (line   21)
* Python Enhancement Proposals; PEP 366 <5>: runpy --- 定位並執行 Python 模組.
                                                             (line  180)
* Python Enhancement Proposals; PEP 366 <6>: 簡介<9>.        (line   67)
* Python Enhancement Proposals; PEP 370: PEP 370 Per-user site-packages Directory.
                                                             (line   36)
* Python Enhancement Proposals; PEP 370 <1>: Library<20>.    (line  605)
* Python Enhancement Proposals; PEP 370 <2>: Miscellaneous options.
                                                             (line  151)
* Python Enhancement Proposals; PEP 370 <3>: 環境變數.       (line  202)
* Python Enhancement Proposals; PEP 370 <4>: 環境變數.       (line  214)
* Python Enhancement Proposals; PEP 370 <5>: 命令列介面<7>.  (line   37)
* Python Enhancement Proposals; PEP 371: PEP 371 The multiprocessing Package.
                                                             (line  145)
* Python Enhancement Proposals; PEP 372: PEP 372：有序字典.  (line    3)
* Python Enhancement Proposals; PEP 372 <1>: PEP 372：有序字典.
                                                             (line   30)
* Python Enhancement Proposals; PEP 372 <2>: PEP 372 Adding an Ordered Dictionary to collections.
                                                             (line   97)
* Python Enhancement Proposals; PEP 373: Python 2 x 的未來.  (line   23)
* Python Enhancement Proposals; PEP 378: PEP 378 Format Specifier for Thousands Separator.
                                                             (line   32)
* Python Enhancement Proposals; PEP 378 <1>: PEP 378 Format Specifier for Thousands Separator<2>.
                                                             (line   37)
* Python Enhancement Proposals; PEP 378 <2>: 格式規格 Format Specification 迷你語言.
                                                             (line   96)
* Python Enhancement Proposals; PEP 380: PEP 380 Syntax for Delegating to a Subgenerator.
                                                             (line   66)
* Python Enhancement Proposals; PEP 380 <1>: Yield expressions.
                                                             (line   99)
* Python Enhancement Proposals; PEP 380#use-of-stopiteration-to-return-values: The STOP_ITERATION event.
                                                             (line    6)
* Python Enhancement Proposals; PEP 383: Documentation<16>.  (line   29)
* Python Enhancement Proposals; PEP 383 <1>: Error Handlers. (line   50)
* Python Enhancement Proposals; PEP 383 <2>: Socket 系列家族.
                                                             (line   15)
* Python Enhancement Proposals; PEP 383 <3>: Locale Encoding.
                                                             (line   14)
* Python Enhancement Proposals; PEP 383 <4>: Locale Encoding.
                                                             (line   50)
* Python Enhancement Proposals; PEP 383 <5>: File System Encoding.
                                                             (line    7)
* Python Enhancement Proposals; PEP 384: 已刪除<2>.          (line   52)
* Python Enhancement Proposals; PEP 384 <1>: PEP 384 Defining a Stable ABI.
                                                             (line   24)
* Python Enhancement Proposals; PEP 384 <2>: C API<29>.      (line  100)
* Python Enhancement Proposals; PEP 385: Code Repository.    (line   13)
* Python Enhancement Proposals; PEP 387: 警告.               (line   25)
* Python Enhancement Proposals; PEP 387 <1>: 警告.           (line   38)
* Python Enhancement Proposals; PEP 387 <2>: C API 穩定性.   (line    6)
* Python Enhancement Proposals; PEP 387 <3>: Python 的版本編號系統是如何運作的？.
                                                             (line   38)
* Python Enhancement Proposals; PEP 389: PEP 389 Argparse 命令列剖析模組.
                                                             (line   92)
* Python Enhancement Proposals; PEP 389 <1>: PEP 389 The argparse Module for Parsing Command Lines.
                                                             (line  100)
* Python Enhancement Proposals; PEP 391: PEP 391 Dictionary Based Configuration for Logging.
                                                             (line   52)
* Python Enhancement Proposals; PEP 391 <1>: PEP 391 Dictionary-Based Configuration For Logging.
                                                             (line   95)
* Python Enhancement Proposals; PEP 392: Python 3 2 有什麼新功能.
                                                             (line   17)
* Python Enhancement Proposals; PEP 393: 已刪除<2>.          (line   26)
* Python Enhancement Proposals; PEP 393 <1>: Porting to Python 3 9<2>.
                                                             (line   45)
* Python Enhancement Proposals; PEP 393 <2>: 已移除<6>.      (line  101)
* Python Enhancement Proposals; PEP 393 <3>: PEP 393 Flexible String Representation.
                                                             (line   16)
* Python Enhancement Proposals; PEP 393 <4>: 功能性.         (line    6)
* Python Enhancement Proposals; PEP 393 <5>: 性能和資源使用情況.
                                                             (line   29)
* Python Enhancement Proposals; PEP 393 <6>: 最佳化<9>.      (line    8)
* Python Enhancement Proposals; PEP 393 <7>: 建置和 C API 更改.
                                                             (line   12)
* Python Enhancement Proposals; PEP 393 <8>: 已棄用的 Python 模組、函式和方法.
                                                             (line   10)
* Python Enhancement Proposals; PEP 393 <9>: C API 中已棄用的函式和型別.
                                                             (line    6)
* Python Enhancement Proposals; PEP 393 <10>: Porting C code.
                                                             (line   17)
* Python Enhancement Proposals; PEP 393 <11>: C API<27>.     (line  142)
* Python Enhancement Proposals; PEP 393 <12>: Encodings and Unicode.
                                                             (line    7)
* Python Enhancement Proposals; PEP 393 <13>: sys --- 系統特定的參數與函式.
                                                             (line 1219)
* Python Enhancement Proposals; PEP 393 <14>: Unicode 物件.  (line    6)
* Python Enhancement Proposals; PEP 397: PEP 486 Make the Python Launcher aware of virtual environments.
                                                             (line    6)
* Python Enhancement Proposals; PEP 397 <1>: PEP 397：適用於 Windows 的 Python 啟動器.
                                                             (line   31)
* Python Enhancement Proposals; PEP 397 <2>: Python Launcher for Windows.
                                                             (line   18)
* Python Enhancement Proposals; PEP 398: Python 3 3 有什麼新功能.
                                                             (line   13)
* Python Enhancement Proposals; PEP 4:   函式庫變更.         (line   13)
* Python Enhancement Proposals; PEP 405: PEP 405：虛擬環境.  (line   22)
* Python Enhancement Proposals; PEP 405 <1>: venv --- 建立虛擬環境.
                                                             (line   45)
* Python Enhancement Proposals; PEP 409: PEP 409 Suppressing exception context.
                                                             (line   63)
* Python Enhancement Proposals; PEP 411: sys --- 系統特定的參數與函式.
                                                             (line  979)
* Python Enhancement Proposals; PEP 411 <1>: sys --- 系統特定的參數與函式.
                                                             (line  989)
* Python Enhancement Proposals; PEP 411 <2>: sys --- 系統特定的參數與函式.
                                                             (line 1677)
* Python Enhancement Proposals; PEP 411 <3>: sys --- 系統特定的參數與函式.
                                                             (line 1697)
* Python Enhancement Proposals; PEP 411 <4>: 術語表.         (line 1042)
* Python Enhancement Proposals; PEP 412: PEP 412 Key-Sharing Dictionary.
                                                             (line   15)
* Python Enhancement Proposals; PEP 412 <1>: functools --- 可呼叫物件上的高階函式與操作.
                                                             (line   80)
* Python Enhancement Proposals; PEP 414: PEP 414 Explicit Unicode literals.
                                                             (line   17)
* Python Enhancement Proposals; PEP 414 <1>: String and Bytes literals.
                                                             (line   61)
* Python Enhancement Proposals; PEP 418: time<8>.            (line    6)
* Python Enhancement Proposals; PEP 420: PEP 420 Implicit Namespace Packages.
                                                             (line    9)
* Python Enhancement Proposals; PEP 420 <1>: PEP 420 Implicit Namespace Packages.
                                                             (line   14)
* Python Enhancement Proposals; PEP 420 <2>: Core and Builtins<76>.
                                                             (line   56)
* Python Enhancement Proposals; PEP 420 <3>: Core and Builtins<81>.
                                                             (line  114)
* Python Enhancement Proposals; PEP 420 <4>: 模組引入系統.   (line   45)
* Python Enhancement Proposals; PEP 420 <5>: Namespace packages.
                                                             (line   27)
* Python Enhancement Proposals; PEP 420 <6>: module __path__.
                                                             (line   21)
* Python Enhancement Proposals; PEP 420 <7>: module __path__.
                                                             (line   21)
* Python Enhancement Proposals; PEP 420 <8>: References.     (line   11)
* Python Enhancement Proposals; PEP 420 <9>: References.     (line   13)
* Python Enhancement Proposals; PEP 420 <10>: References.    (line   13)
* Python Enhancement Proposals; PEP 420 <11>: 簡介<9>.       (line   71)
* Python Enhancement Proposals; PEP 420 <12>: 術語表.        (line  880)
* Python Enhancement Proposals; PEP 420 <13>: 術語表.        (line 1023)
* Python Enhancement Proposals; PEP 421: SimpleNamespace.    (line   16)
* Python Enhancement Proposals; PEP 421 <1>: sys --- 系統特定的參數與函式.
                                                             (line 1093)
* Python Enhancement Proposals; PEP 421 <2>: sys --- 系統特定的參數與函式.
                                                             (line 1098)
* Python Enhancement Proposals; PEP 424: 其他語言更動<9>.    (line   57)
* Python Enhancement Proposals; PEP 424 <1>: operator<3>.    (line    8)
* Python Enhancement Proposals; PEP 428: Summary -- Release Highlights<3>.
                                                             (line   39)
* Python Enhancement Proposals; PEP 428 <1>: pathlib<11>.    (line   17)
* Python Enhancement Proposals; PEP 428 <2>: pathlib --- 物件導向檔案系統路徑.
                                                             (line   37)
* Python Enhancement Proposals; PEP 429: Python 3 4 有什麼新功能<2>.
                                                             (line   16)
* Python Enhancement Proposals; PEP 432: Other CPython implementation changes.
                                                             (line    7)
* Python Enhancement Proposals; PEP 432 <1>: Core and Builtins<59>.
                                                             (line  312)
* Python Enhancement Proposals; PEP 432 <2>: Multi-Phase Initialization Private Provisional API.
                                                             (line    7)
* Python Enhancement Proposals; PEP 432 <3>: Multi-Phase Initialization Private Provisional API.
                                                             (line   57)
* Python Enhancement Proposals; PEP 434: PEP 434 IDLE Enhancement Exception for All Branches.
                                                             (line    6)
* Python Enhancement Proposals; PEP 434 <1>: idlelib.        (line   17)
* Python Enhancement Proposals; PEP 435: Summary -- Release Highlights<3>.
                                                             (line   36)
* Python Enhancement Proposals; PEP 435 <1>: enum<8>.        (line    6)
* Python Enhancement Proposals; PEP 435 <2>: enum<8>.        (line   15)
* Python Enhancement Proposals; PEP 436: Summary -- Release Highlights<3>.
                                                             (line  120)
* Python Enhancement Proposals; PEP 436 <1>: PEP 436 Argument Clinic.
                                                             (line    6)
* Python Enhancement Proposals; PEP 436 <2>: PEP 436 Argument Clinic.
                                                             (line   28)
* Python Enhancement Proposals; PEP 441: zipapp<2>.          (line    6)
* Python Enhancement Proposals; PEP 441 <1>: zipapp<2>.      (line   24)
* Python Enhancement Proposals; PEP 442: 已移除<5>.          (line   68)
* Python Enhancement Proposals; PEP 442 <1>: Summary -- Release Highlights<3>.
                                                             (line  113)
* Python Enhancement Proposals; PEP 442 <2>: Summary -- Release Highlights<3>.
                                                             (line  115)
* Python Enhancement Proposals; PEP 442 <3>: PEP 442 Safe Object Finalization.
                                                             (line    6)
* Python Enhancement Proposals; PEP 442 <4>: PEP 442 Safe Object Finalization.
                                                             (line   21)
* Python Enhancement Proposals; PEP 442 <5>: C API<42>.      (line   55)
* Python Enhancement Proposals; PEP 442 <6>: gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line  250)
* Python Enhancement Proposals; PEP 442 <7>: Finalization and De-allocation.
                                                             (line   89)
* Python Enhancement Proposals; PEP 442 <8>: PyTypeObject Slots.
                                                             (line 1630)
* Python Enhancement Proposals; PEP 443: Summary -- Release Highlights<3>.
                                                             (line   55)
* Python Enhancement Proposals; PEP 443 <1>: functools<5>.   (line   22)
* Python Enhancement Proposals; PEP 443 <2>: 術語表.         (line  524)
* Python Enhancement Proposals; PEP 445: Summary -- Release Highlights<3>.
                                                             (line  118)
* Python Enhancement Proposals; PEP 445 <1>: PEP 445 Customization of CPython Memory Allocators.
                                                             (line    6)
* Python Enhancement Proposals; PEP 445 <2>: PEP 445 Customization of CPython Memory Allocators.
                                                             (line   12)
* Python Enhancement Proposals; PEP 445 <3>: Other Improvements<2>.
                                                             (line   63)
* Python Enhancement Proposals; PEP 446: Summary -- Release Highlights<3>.
                                                             (line   14)
* Python Enhancement Proposals; PEP 446 <1>: Summary -- Release Highlights<3>.
                                                             (line   78)
* Python Enhancement Proposals; PEP 446 <2>: PEP 446 Newly Created File Descriptors Are Non-Inheritable.
                                                             (line    6)
* Python Enhancement Proposals; PEP 446 <3>: PEP 446 Newly Created File Descriptors Are Non-Inheritable.
                                                             (line   26)
* Python Enhancement Proposals; PEP 446 <4>: Core and Builtins<11>.
                                                             (line   20)
* Python Enhancement Proposals; PEP 448: PEP 448 - Additional Unpacking Generalizations.
                                                             (line    6)
* Python Enhancement Proposals; PEP 448 <1>: PEP 448 - Additional Unpacking Generalizations.
                                                             (line   39)
* Python Enhancement Proposals; PEP 448 <2>: Documentation<63>.
                                                             (line   10)
* Python Enhancement Proposals; PEP 448 <3>: Documentation<67>.
                                                             (line    9)
* Python Enhancement Proposals; PEP 448 <4>: Core and Builtins<84>.
                                                             (line   12)
* Python Enhancement Proposals; PEP 448 <5>: Core and Builtins<87>.
                                                             (line    9)
* Python Enhancement Proposals; PEP 448 <6>: Dictionary displays.
                                                             (line   29)
* Python Enhancement Proposals; PEP 448 <7>: Calls.          (line  121)
* Python Enhancement Proposals; PEP 448 <8>: Expression lists.
                                                             (line   22)
* Python Enhancement Proposals; PEP 450: Summary -- Release Highlights<3>.
                                                             (line   47)
* Python Enhancement Proposals; PEP 450 <1>: statistics<6>.  (line    6)
* Python Enhancement Proposals; PEP 450 <2>: statistics<6>.  (line   14)
* Python Enhancement Proposals; PEP 451: zipimport<2>.       (line    8)
* Python Enhancement Proposals; PEP 451 <1>: zipimport<3>.   (line    6)
* Python Enhancement Proposals; PEP 451 <2>: PEP 489 Multi-phase extension module initialization.
                                                             (line    7)
* Python Enhancement Proposals; PEP 451 <3>: Summary -- Release Highlights<3>.
                                                             (line   22)
* Python Enhancement Proposals; PEP 451 <4>: PEP 451 A ModuleSpec Type for the Import System.
                                                             (line    6)
* Python Enhancement Proposals; PEP 451 <5>: Library<20>.    (line  457)
* Python Enhancement Proposals; PEP 451 <6>: Core and Builtins<76>.
                                                             (line   75)
* Python Enhancement Proposals; PEP 451 <7>: References.     (line   26)
* Python Enhancement Proposals; PEP 451 <8>: sys --- 系統特定的參數與函式.
                                                             (line 1251)
* Python Enhancement Proposals; PEP 451 <9>: pkgutil --- 套件擴充工具程式.
                                                             (line   56)
* Python Enhancement Proposals; PEP 451 <10>: pkgutil --- 套件擴充工具程式.
                                                             (line   85)
* Python Enhancement Proposals; PEP 451 <11>: runpy --- 定位並執行 Python 模組.
                                                             (line   90)
* Python Enhancement Proposals; PEP 451 <12>: runpy --- 定位並執行 Python 模組.
                                                             (line  166)
* Python Enhancement Proposals; PEP 451 <13>: runpy --- 定位並執行 Python 模組.
                                                             (line  184)
* Python Enhancement Proposals; PEP 451 <14>: 簡介<9>.       (line   75)
* Python Enhancement Proposals; PEP 451 <15>: Multi-phase initialization.
                                                             (line   71)
* Python Enhancement Proposals; PEP 453: Summary -- Release Highlights<3>.
                                                             (line   12)
* Python Enhancement Proposals; PEP 453 <1>: Summary -- Release Highlights<3>.
                                                             (line   34)
* Python Enhancement Proposals; PEP 453 <2>: Bootstrapping pip By Default.
                                                             (line    6)
* Python Enhancement Proposals; PEP 453 <3>: Documentation Changes.
                                                             (line   21)
* Python Enhancement Proposals; PEP 453 <4>: ensurepip<2>.   (line    7)
* Python Enhancement Proposals; PEP 453 <5>: venv<7>.        (line   13)
* Python Enhancement Proposals; PEP 453 <6>: Other Improvements<2>.
                                                             (line   73)
* Python Enhancement Proposals; PEP 453 <7>: PEP 477 Backport ensurepip PEP 453 to Python 2 7.
                                                             (line    6)
* Python Enhancement Proposals; PEP 453 <8>: Bootstrapping pip By Default<2>.
                                                             (line    6)
* Python Enhancement Proposals; PEP 453 <9>: Documentation Changes<2>.
                                                             (line   21)
* Python Enhancement Proposals; PEP 453 <10>: ensurepip --- pip 安裝器的初始建置 bootstrapping.
                                                             (line   31)
* Python Enhancement Proposals; PEP 454: Summary -- Release Highlights<3>.
                                                             (line   50)
* Python Enhancement Proposals; PEP 454 <1>: tracemalloc<4>. (line    6)
* Python Enhancement Proposals; PEP 454 <2>: tracemalloc<4>. (line   22)
* Python Enhancement Proposals; PEP 456: Summary -- Release Highlights<3>.
                                                             (line   75)
* Python Enhancement Proposals; PEP 456 <1>: PEP 456 Secure and Interchangeable Hash Algorithm.
                                                             (line    6)
* Python Enhancement Proposals; PEP 456 <2>: PyHash API.     (line   76)
* Python Enhancement Proposals; PEP 461: PEP 461 - percent formatting support for bytes and bytearray.
                                                             (line    6)
* Python Enhancement Proposals; PEP 461 <1>: PEP 461 - percent formatting support for bytes and bytearray.
                                                             (line   41)
* Python Enhancement Proposals; PEP 461 <2>: printf-style Bytes Formatting.
                                                             (line  198)
* Python Enhancement Proposals; PEP 465: PEP 465 - A dedicated infix operator for matrix multiplication.
                                                             (line    6)
* Python Enhancement Proposals; PEP 465 <1>: PEP 465 - A dedicated infix operator for matrix multiplication.
                                                             (line   44)
* Python Enhancement Proposals; PEP 465 <2>: Build and C API Changes<3>.
                                                             (line   43)
* Python Enhancement Proposals; PEP 465 <3>: Tools/Demos<47>.
                                                             (line   39)
* Python Enhancement Proposals; PEP 466: PEP 466 Network Security Enhancements for Python 2 7.
                                                             (line    6)
* Python Enhancement Proposals; PEP 466 <1>: PEP 466 Network Security Enhancements for Python 2 7.
                                                             (line   11)
* Python Enhancement Proposals; PEP 466 <2>: PEP 466 Network Security Enhancements for Python 2 7.
                                                             (line   21)
* Python Enhancement Proposals; PEP 466 <3>: PEP 466 Network Security Enhancements for Python 2 7.
                                                             (line   32)
* Python Enhancement Proposals; PEP 468: PEP 468 Preserving Keyword Argument Order.
                                                             (line   12)
* Python Enhancement Proposals; PEP 468 <1>: Library<66>.    (line   87)
* Python Enhancement Proposals; PEP 468 <2>: OrderedDict 物件.
                                                             (line   92)
* Python Enhancement Proposals; PEP 471: PEP 471 - os scandir function -- a better and faster directory iterator.
                                                             (line    6)
* Python Enhancement Proposals; PEP 471 <1>: PEP 471 - os scandir function -- a better and faster directory iterator.
                                                             (line   29)
* Python Enhancement Proposals; PEP 471 <2>: Library<92>.    (line    6)
* Python Enhancement Proposals; PEP 475: PEP 475 Retry system calls failing with EINTR.
                                                             (line   32)
* Python Enhancement Proposals; PEP 475 <1>: PEP 475 Retry system calls failing with EINTR.
                                                             (line   77)
* Python Enhancement Proposals; PEP 475 <2>: Changes in the Python API<7>.
                                                             (line    6)
* Python Enhancement Proposals; PEP 475 <3>: Library<57>.    (line  228)
* Python Enhancement Proposals; PEP 475 <4>: Library<90>.    (line  143)
* Python Enhancement Proposals; PEP 475 <5>: 內建函式.       (line 1323)
* Python Enhancement Proposals; PEP 475 <6>: 作業系統例外.   (line   75)
* Python Enhancement Proposals; PEP 475 <7>: File Descriptor Operations.
                                                             (line  406)
* Python Enhancement Proposals; PEP 475 <8>: File Descriptor Operations.
                                                             (line  743)
* Python Enhancement Proposals; PEP 475 <9>: File Descriptor Operations.
                                                             (line  927)
* Python Enhancement Proposals; PEP 475 <10>: 行程管理.      (line  924)
* Python Enhancement Proposals; PEP 475 <11>: 函式<4>.       (line  259)
* Python Enhancement Proposals; PEP 475 <12>: Socket 物件.   (line   28)
* Python Enhancement Proposals; PEP 475 <13>: Socket 物件.   (line   82)
* Python Enhancement Proposals; PEP 475 <14>: Socket 物件.   (line  249)
* Python Enhancement Proposals; PEP 475 <15>: Socket 物件.   (line  263)
* Python Enhancement Proposals; PEP 475 <16>: Socket 物件.   (line  339)
* Python Enhancement Proposals; PEP 475 <17>: Socket 物件.   (line  413)
* Python Enhancement Proposals; PEP 475 <18>: Socket 物件.   (line  432)
* Python Enhancement Proposals; PEP 475 <19>: Socket 物件.   (line  451)
* Python Enhancement Proposals; PEP 475 <20>: Socket 物件.   (line  495)
* Python Enhancement Proposals; PEP 475 <21>: select --- 等待 I/O 完成.
                                                             (line  157)
* Python Enhancement Proposals; PEP 475 <22>: /dev/poll Polling Objects.
                                                             (line   82)
* Python Enhancement Proposals; PEP 475 <23>: Edge and Level Trigger Polling epoll Objects.
                                                             (line  102)
* Python Enhancement Proposals; PEP 475 <24>: Polling Objects.
                                                             (line   94)
* Python Enhancement Proposals; PEP 475 <25>: Kqueue Objects.
                                                             (line   36)
* Python Enhancement Proposals; PEP 475 <26>: Classes<3>.    (line  133)
* Python Enhancement Proposals; PEP 475 <27>: 模組內容<5>.   (line  586)
* Python Enhancement Proposals; PEP 475 <28>: 模組內容<5>.   (line  605)
* Python Enhancement Proposals; PEP 476: PEP 476 Enabling certificate verification by default for stdlib http clients<2>.
                                                             (line    6)
* Python Enhancement Proposals; PEP 477: PEP 477 Backport ensurepip PEP 453 to Python 2 7.
                                                             (line    6)
* Python Enhancement Proposals; PEP 478: Python 3 4 有什麼新功能.
                                                             (line   17)
* Python Enhancement Proposals; PEP 479: Changes in Python Behavior.
                                                             (line   11)
* Python Enhancement Proposals; PEP 479 <1>: PEP 479 Change StopIteration handling inside generators.
                                                             (line   12)
* Python Enhancement Proposals; PEP 479 <2>: PEP 479 Change StopIteration handling inside generators.
                                                             (line   47)
* Python Enhancement Proposals; PEP 479 <3>: Library<48>.    (line 1267)
* Python Enhancement Proposals; PEP 479 <4>: Library<52>.    (line   52)
* Python Enhancement Proposals; PEP 479 <5>: Core and Builtins<55>.
                                                             (line   34)
* Python Enhancement Proposals; PEP 479 <6>: Library<60>.    (line   95)
* Python Enhancement Proposals; PEP 479 <7>: Library<73>.    (line   80)
* Python Enhancement Proposals; PEP 479 <8>: Library<79>.    (line  326)
* Python Enhancement Proposals; PEP 479 <9>: 實體例外.       (line  241)
* Python Enhancement Proposals; PEP 479 <10>: 實體例外.      (line  243)
* Python Enhancement Proposals; PEP 479 <11>: 模組內容<9>.   (line   40)
* Python Enhancement Proposals; PEP 483: PEP 484 - Type Hints.
                                                             (line   47)
* Python Enhancement Proposals; PEP 483 <1>: 術語表.         (line  532)
* Python Enhancement Proposals; PEP 484: PEP 695：型別參數語法.
                                                             (line    6)
* Python Enhancement Proposals; PEP 484 <1>: New Features Related to Type Hints.
                                                             (line    6)
* Python Enhancement Proposals; PEP 484 <2>: PEP 692 Using TypedDict for more precise **kwargs typing.
                                                             (line    6)
* Python Enhancement Proposals; PEP 484 <3>: 型別提示相關的新特性.
                                                             (line    6)
* Python Enhancement Proposals; PEP 484 <4>: PEP 646：可變參數泛型 variadic generics.
                                                             (line    6)
* Python Enhancement Proposals; PEP 484 <5>: 與型別提示相關的新功能.
                                                             (line    6)
* Python Enhancement Proposals; PEP 484 <6>: PEP 612：參數規範變數.
                                                             (line    6)
* Python Enhancement Proposals; PEP 484 <7>: PEP 613：型別別名 TypeAlias.
                                                             (line    6)
* Python Enhancement Proposals; PEP 484 <8>: ast<3>.         (line   17)
* Python Enhancement Proposals; PEP 484 <9>: ast<3>.         (line   20)
* Python Enhancement Proposals; PEP 484 <10>: PEP 560 Core Support for typing module and Generic Types.
                                                             (line    6)
* Python Enhancement Proposals; PEP 484 <11>: PEP 526 Syntax for variable annotations.
                                                             (line    6)
* Python Enhancement Proposals; PEP 484 <12>: PEP 484 - Type Hints.
                                                             (line   16)
* Python Enhancement Proposals; PEP 484 <13>: PEP 484 - Type Hints.
                                                             (line   41)
* Python Enhancement Proposals; PEP 484 <14>: 函式註釋 Function Annotations.
                                                             (line    7)
* Python Enhancement Proposals; PEP 484 <15>: Emulating generic types.
                                                             (line   15)
* Python Enhancement Proposals; PEP 484 <16>: Annotated assignment statements.
                                                             (line   48)
* Python Enhancement Proposals; PEP 484 <17>: 函式定義.      (line  144)
* Python Enhancement Proposals; PEP 484 <18>: GenericAlias 物件的特殊屬性.
                                                             (line   48)
* Python Enhancement Proposals; PEP 484 <19>: NewType.       (line   59)
* Python Enhancement Proposals; PEP 484 <20>: 標稱 nominal 子型別 vs 結構子型別.
                                                             (line    6)
* Python Enhancement Proposals; PEP 484 <21>: 標稱 nominal 子型別 vs 結構子型別.
                                                             (line   11)
* Python Enhancement Proposals; PEP 484 <22>: Building generic types and type aliases.
                                                             (line  113)
* Python Enhancement Proposals; PEP 484 <23>: 函式與裝飾器.  (line  280)
* Python Enhancement Proposals; PEP 484 <24>: 根節點.        (line   57)
* Python Enhancement Proposals; PEP 484 <25>: ast 輔助程式.  (line   17)
* Python Enhancement Proposals; PEP 484 <26>: ast 輔助程式.  (line   25)
* Python Enhancement Proposals; PEP 484 <27>: 編譯器旗標<2>. (line   28)
* Python Enhancement Proposals; PEP 484 <28>: 術語表.        (line   48)
* Python Enhancement Proposals; PEP 484 <29>: 術語表.        (line  465)
* Python Enhancement Proposals; PEP 484 <30>: 術語表.        (line  532)
* Python Enhancement Proposals; PEP 484 <31>: 術語表.        (line 1263)
* Python Enhancement Proposals; PEP 484 <32>: 術語表.        (line 1277)
* Python Enhancement Proposals; PEP 484 <33>: 術語表.        (line 1303)
* Python Enhancement Proposals; PEP 484#annotating-instance-and-class-methods: PEP 673：Self 型別.
                                                             (line    7)
* Python Enhancement Proposals; PEP 485: PEP 485 A function for testing approximate equality.
                                                             (line    6)
* Python Enhancement Proposals; PEP 485 <1>: PEP 485 A function for testing approximate equality.
                                                             (line   36)
* Python Enhancement Proposals; PEP 485 <2>: Library<88>.    (line   10)
* Python Enhancement Proposals; PEP 485 <3>: 數論與表現函式. (line  132)
* Python Enhancement Proposals; PEP 485 <4>: 分類函式.       (line   47)
* Python Enhancement Proposals; PEP 486: PEP 486 Make the Python Launcher aware of virtual environments.
                                                             (line    6)
* Python Enhancement Proposals; PEP 486 <1>: PEP 486 Make the Python Launcher aware of virtual environments.
                                                             (line   14)
* Python Enhancement Proposals; PEP 486 <2>: Windows<70>.    (line    6)
* Python Enhancement Proposals; PEP 487: PEP 487 Simpler customization of class creation.
                                                             (line   32)
* Python Enhancement Proposals; PEP 487 <1>: PEP 487 Descriptor Protocol Enhancements.
                                                             (line    6)
* Python Enhancement Proposals; PEP 487 <2>: PEP 487 Descriptor Protocol Enhancements.
                                                             (line   33)
* Python Enhancement Proposals; PEP 487 <3>: Changes in the Python API<6>.
                                                             (line  103)
* Python Enhancement Proposals; PEP 487 <4>: Documentation<53>.
                                                             (line   52)
* Python Enhancement Proposals; PEP 487 <5>: Documentation<60>.
                                                             (line    8)
* Python Enhancement Proposals; PEP 487 <6>: Core and Builtins<73>.
                                                             (line   46)
* Python Enhancement Proposals; PEP 488: PEP 488 Elimination of PYO files.
                                                             (line    6)
* Python Enhancement Proposals; PEP 488 <1>: PEP 488 Elimination of PYO files.
                                                             (line   20)
* Python Enhancement Proposals; PEP 488 <2>: Changes in the Python API<7>.
                                                             (line   79)
* Python Enhancement Proposals; PEP 488 <3>: Core and Builtins<91>.
                                                             (line   15)
* Python Enhancement Proposals; PEP 488 <4>: Miscellaneous options.
                                                             (line   78)
* Python Enhancement Proposals; PEP 488 <5>: Miscellaneous options.
                                                             (line   80)
* Python Enhancement Proposals; PEP 488 <6>: Miscellaneous options.
                                                             (line   86)
* Python Enhancement Proposals; PEP 488 <7>: Miscellaneous options.
                                                             (line   88)
* Python Enhancement Proposals; PEP 488 <8>: test support import_helper --- 用於 import 測試的工具.
                                                             (line   80)
* Python Enhancement Proposals; PEP 488 <9>: 簡介<9>.        (line   79)
* Python Enhancement Proposals; PEP 488 <10>: importlib util -- Utility code for importers.
                                                             (line   24)
* Python Enhancement Proposals; PEP 488 <11>: importlib util -- Utility code for importers.
                                                             (line   64)
* Python Enhancement Proposals; PEP 488 <12>: py_compile — 編譯 Python 來源檔案.
                                                             (line   31)
* Python Enhancement Proposals; PEP 489: PEP 489 Multi-phase extension module initialization.
                                                             (line    6)
* Python Enhancement Proposals; PEP 489 <1>: PEP 489 Multi-phase extension module initialization.
                                                             (line   18)
* Python Enhancement Proposals; PEP 489 <2>: Build and C API Changes<3>.
                                                             (line   37)
* Python Enhancement Proposals; PEP 489 <3>: Library<6>.     (line  254)
* Python Enhancement Proposals; PEP 489 <4>: Library<16>.    (line   20)
* Python Enhancement Proposals; PEP 489 <5>: Library<32>.    (line   64)
* Python Enhancement Proposals; PEP 489 <6>: Library<32>.    (line   79)
* Python Enhancement Proposals; PEP 489 <7>: Core and Builtins<34>.
                                                             (line   70)
* Python Enhancement Proposals; PEP 489 <8>: Library<33>.    (line   68)
* Python Enhancement Proposals; PEP 489 <9>: Library<33>.    (line  177)
* Python Enhancement Proposals; PEP 489 <10>: Core and Builtins<35>.
                                                             (line   50)
* Python Enhancement Proposals; PEP 489 <11>: Library<34>.   (line  103)
* Python Enhancement Proposals; PEP 489 <12>: C API<33>.     (line   11)
* Python Enhancement Proposals; PEP 489 <13>: C API<33>.     (line   14)
* Python Enhancement Proposals; PEP 489 <14>: C API<33>.     (line   17)
* Python Enhancement Proposals; PEP 489 <15>: C API<33>.     (line   20)
* Python Enhancement Proposals; PEP 489 <16>: C API<33>.     (line   23)
* Python Enhancement Proposals; PEP 489 <17>: C API<33>.     (line   26)
* Python Enhancement Proposals; PEP 489 <18>: C API<33>.     (line   29)
* Python Enhancement Proposals; PEP 489 <19>: C API<33>.     (line   38)
* Python Enhancement Proposals; PEP 489 <20>: C API<33>.     (line   41)
* Python Enhancement Proposals; PEP 489 <21>: C API<33>.     (line   44)
* Python Enhancement Proposals; PEP 489 <22>: C API<33>.     (line   47)
* Python Enhancement Proposals; PEP 489 <23>: Library<35>.   (line   31)
* Python Enhancement Proposals; PEP 489 <24>: Core and Builtins<37>.
                                                             (line   20)
* Python Enhancement Proposals; PEP 489 <25>: Core and Builtins<37>.
                                                             (line   30)
* Python Enhancement Proposals; PEP 489 <26>: Core and Builtins<37>.
                                                             (line   33)
* Python Enhancement Proposals; PEP 489 <27>: Core and Builtins<37>.
                                                             (line   36)
* Python Enhancement Proposals; PEP 489 <28>: Core and Builtins<37>.
                                                             (line   39)
* Python Enhancement Proposals; PEP 489 <29>: Core and Builtins<37>.
                                                             (line   49)
* Python Enhancement Proposals; PEP 489 <30>: Core and Builtins<37>.
                                                             (line   52)
* Python Enhancement Proposals; PEP 489 <31>: Core and Builtins<37>.
                                                             (line   55)
* Python Enhancement Proposals; PEP 489 <32>: Core and Builtins<37>.
                                                             (line   74)
* Python Enhancement Proposals; PEP 489 <33>: Core and Builtins<37>.
                                                             (line   90)
* Python Enhancement Proposals; PEP 489 <34>: Core and Builtins<37>.
                                                             (line  102)
* Python Enhancement Proposals; PEP 489 <35>: Library<36>.   (line   75)
* Python Enhancement Proposals; PEP 489 <36>: Library<36>.   (line   78)
* Python Enhancement Proposals; PEP 489 <37>: Library<36>.   (line  423)
* Python Enhancement Proposals; PEP 489 <38>: Core and Builtins<38>.
                                                             (line   28)
* Python Enhancement Proposals; PEP 489 <39>: Core and Builtins<38>.
                                                             (line   35)
* Python Enhancement Proposals; PEP 489 <40>: Core and Builtins<38>.
                                                             (line   50)
* Python Enhancement Proposals; PEP 489 <41>: Core and Builtins<39>.
                                                             (line   46)
* Python Enhancement Proposals; PEP 489 <42>: Core and Builtins<39>.
                                                             (line   49)
* Python Enhancement Proposals; PEP 489 <43>: Core and Builtins<39>.
                                                             (line   51)
* Python Enhancement Proposals; PEP 489 <44>: Core and Builtins<39>.
                                                             (line   71)
* Python Enhancement Proposals; PEP 489 <45>: Core and Builtins<39>.
                                                             (line   75)
* Python Enhancement Proposals; PEP 489 <46>: Core and Builtins<40>.
                                                             (line   17)
* Python Enhancement Proposals; PEP 489 <47>: Core and Builtins<40>.
                                                             (line   20)
* Python Enhancement Proposals; PEP 489 <48>: Core and Builtins<40>.
                                                             (line   40)
* Python Enhancement Proposals; PEP 489 <49>: Core and Builtins<40>.
                                                             (line   54)
* Python Enhancement Proposals; PEP 489 <50>: Core and Builtins<40>.
                                                             (line  109)
* Python Enhancement Proposals; PEP 489 <51>: Core and Builtins<40>.
                                                             (line  118)
* Python Enhancement Proposals; PEP 489 <52>: Core and Builtins<41>.
                                                             (line   29)
* Python Enhancement Proposals; PEP 489 <53>: Core and Builtins<41>.
                                                             (line   32)
* Python Enhancement Proposals; PEP 489 <54>: Core and Builtins<41>.
                                                             (line   52)
* Python Enhancement Proposals; PEP 489 <55>: Core and Builtins<41>.
                                                             (line   55)
* Python Enhancement Proposals; PEP 489 <56>: Core and Builtins<41>.
                                                             (line   58)
* Python Enhancement Proposals; PEP 489 <57>: Core and Builtins<42>.
                                                             (line   62)
* Python Enhancement Proposals; PEP 489 <58>: 簡介<9>.       (line   83)
* Python Enhancement Proposals; PEP 489 <59>: importlib machinery -- Importers and path hooks.
                                                             (line   74)
* Python Enhancement Proposals; PEP 489 <60>: importlib machinery -- Importers and path hooks.
                                                             (line  292)
* Python Enhancement Proposals; PEP 489 <61>: importlib machinery -- Importers and path hooks.
                                                             (line  311)
* Python Enhancement Proposals; PEP 489 <62>: importlib machinery -- Importers and path hooks.
                                                             (line  317)
* Python Enhancement Proposals; PEP 489 <63>: importlib util -- Utility code for importers.
                                                             (line  183)
* Python Enhancement Proposals; PEP 489 <64>: The Module's Method Table and Initialization Function.
                                                             (line  140)
* Python Enhancement Proposals; PEP 489 <65>: 建立 C 與 C++ 擴充套件.
                                                             (line   40)
* Python Enhancement Proposals; PEP 489 <66>: Multi-phase initialization.
                                                             (line  164)
* Python Enhancement Proposals; PEP 489 <67>: Sub-interpreter support.
                                                             (line   81)
* Python Enhancement Proposals; PEP 492: PEP 525 Asynchronous Generators.
                                                             (line    6)
* Python Enhancement Proposals; PEP 492 <1>: 新關鍵字.       (line    7)
* Python Enhancement Proposals; PEP 492 <2>: PEP 492 - Coroutines with async and await syntax.
                                                             (line    6)
* Python Enhancement Proposals; PEP 492 <3>: PEP 492 - Coroutines with async and await syntax.
                                                             (line   97)
* Python Enhancement Proposals; PEP 492 <4>: New Keywords.   (line    7)
* Python Enhancement Proposals; PEP 492 <5>: C API 中的改動<6>.
                                                             (line   25)
* Python Enhancement Proposals; PEP 492 <6>: Core and Builtins<58>.
                                                             (line   98)
* Python Enhancement Proposals; PEP 492 <7>: Library<74>.    (line   51)
* Python Enhancement Proposals; PEP 492 <8>: Library<80>.    (line   16)
* Python Enhancement Proposals; PEP 492 <9>: Core and Builtins<88>.
                                                             (line   14)
* Python Enhancement Proposals; PEP 492 <10>: Awaitable Objects.
                                                             (line   32)
* Python Enhancement Proposals; PEP 492 <11>: Yield expressions.
                                                             (line  106)
* Python Enhancement Proposals; PEP 492 <12>: async with 陳述式.
                                                             (line   44)
* Python Enhancement Proposals; PEP 492 <13>: Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line  166)
* Python Enhancement Proposals; PEP 492 <14>: Code Objects Bit Flags.
                                                             (line   38)
* Python Enhancement Proposals; PEP 492 <15>: Code Objects Bit Flags.
                                                             (line   47)
* Python Enhancement Proposals; PEP 492 <16>: 術語表.        (line   83)
* Python Enhancement Proposals; PEP 492 <17>: 術語表.        (line  112)
* Python Enhancement Proposals; PEP 492 <18>: 術語表.        (line  118)
* Python Enhancement Proposals; PEP 492 <19>: 術語表.        (line  126)
* Python Enhancement Proposals; PEP 492 <20>: 術語表.        (line  143)
* Python Enhancement Proposals; PEP 492 <21>: 術語表.        (line  269)
* Python Enhancement Proposals; PEP 492 <22>: 術語表.        (line  276)
* Python Enhancement Proposals; PEP 493: PEP 493 HTTPS verification migration tools for Python 2 7.
                                                             (line    6)
* Python Enhancement Proposals; PEP 494: Python 3 6 有什麼新功能.
                                                             (line   17)
* Python Enhancement Proposals; PEP 495: PEP 495 Local Time Disambiguation.
                                                             (line   13)
* Python Enhancement Proposals; PEP 495 <1>: PEP 495 Local Time Disambiguation.
                                                             (line   36)
* Python Enhancement Proposals; PEP 495 <2>: Library<72>.    (line   96)
* Python Enhancement Proposals; PEP 495 <3>: Using ZoneInfo. (line   34)
* Python Enhancement Proposals; PEP 498: PEP 498 Formatted string literals.
                                                             (line    6)
* Python Enhancement Proposals; PEP 498 <1>: PEP 498 Formatted string literals.
                                                             (line   27)
* Python Enhancement Proposals; PEP 498 <2>: Core and Builtins<76>.
                                                             (line  283)
* Python Enhancement Proposals; PEP 498 <3>: f-string（f 字串）.
                                                             (line  154)
* Python Enhancement Proposals; PEP 498 <4>: 術語表.         (line  381)
* Python Enhancement Proposals; PEP 5:   PEP 230 Warning Framework.
                                                             (line   66)
* Python Enhancement Proposals; PEP 5 <1>: 對 Python 提出不相容的變更建議是否適當？.
                                                             (line   11)
* Python Enhancement Proposals; PEP 506: secrets.            (line   19)
* Python Enhancement Proposals; PEP 506 <1>: Library<75>.    (line   60)
* Python Enhancement Proposals; PEP 506 <2>: secrets --- 產生用於管理機密的安全亂數.
                                                             (line   23)
* Python Enhancement Proposals; PEP 511: Changes in the Python API<6>.
                                                             (line   33)
* Python Enhancement Proposals; PEP 514: Windows py exe 啟動程式 launcher 的改進.
                                                             (line    7)
* Python Enhancement Proposals; PEP 514 <1>: Windows<19>.    (line   13)
* Python Enhancement Proposals; PEP 514 <2>: Windows<62>.    (line    8)
* Python Enhancement Proposals; PEP 514 <3>: From the command-line.
                                                             (line   45)
* Python Enhancement Proposals; PEP 515: fractions<3>.       (line    6)
* Python Enhancement Proposals; PEP 515 <1>: PEP 515 Underscores in Numeric Literals.
                                                             (line    6)
* Python Enhancement Proposals; PEP 515 <2>: PEP 515 Underscores in Numeric Literals.
                                                             (line   32)
* Python Enhancement Proposals; PEP 515 <3>: Core and Builtins<72>.
                                                             (line   15)
* Python Enhancement Proposals; PEP 515 <4>: Core and Builtins<72>.
                                                             (line   43)
* Python Enhancement Proposals; PEP 515 <5>: 格式規格 Format Specification 迷你語言.
                                                             (line  102)
* Python Enhancement Proposals; PEP 515 <6>: fractions --- 有理數.
                                                             (line   96)
* Python Enhancement Proposals; PEP 519: PEP 519 Adding a file system path protocol.
                                                             (line   62)
* Python Enhancement Proposals; PEP 519 <1>: Library<72>.    (line    6)
* Python Enhancement Proposals; PEP 519 <2>: Core and Builtins<75>.
                                                             (line   19)
* Python Enhancement Proposals; PEP 519 <3>: Library<74>.    (line   31)
* Python Enhancement Proposals; PEP 519 <4>: Library<74>.    (line   42)
* Python Enhancement Proposals; PEP 519 <5>: Library<74>.    (line   44)
* Python Enhancement Proposals; PEP 519 <6>: C API<63>.      (line    6)
* Python Enhancement Proposals; PEP 519 <7>: 術語表.         (line 1005)
* Python Enhancement Proposals; PEP 520: PEP 520 Preserving Class Attribute Definition Order.
                                                             (line   17)
* Python Enhancement Proposals; PEP 523: 新增特性<2>.        (line   19)
* Python Enhancement Proposals; PEP 523 <1>: 移植至 Python 3 11<2>.
                                                             (line   27)
* Python Enhancement Proposals; PEP 523 <2>: Porting to Python 3 9<2>.
                                                             (line    6)
* Python Enhancement Proposals; PEP 523 <3>: PEP 523 Adding a frame evaluation API to CPython.
                                                             (line   12)
* Python Enhancement Proposals; PEP 523 <4>: PEP 523 Adding a frame evaluation API to CPython.
                                                             (line   26)
* Python Enhancement Proposals; PEP 523 <5>: Core and Builtins<14>.
                                                             (line   26)
* Python Enhancement Proposals; PEP 523 <6>: Tools/Demos<29>.
                                                             (line    7)
* Python Enhancement Proposals; PEP 523 <7>: Tools/Demos<33>.
                                                             (line    7)
* Python Enhancement Proposals; PEP 523 <8>: Core and Builtins<72>.
                                                             (line   83)
* Python Enhancement Proposals; PEP 523 <9>: Internal Frames.
                                                             (line    6)
* Python Enhancement Proposals; PEP 523 <10>: 低階 API.      (line  167)
* Python Enhancement Proposals; PEP 523 <11>: 低階 API.      (line  176)
* Python Enhancement Proposals; PEP 524: Summary -- Release highlights<3>.
                                                             (line   77)
* Python Enhancement Proposals; PEP 524 <1>: os<8>.          (line   20)
* Python Enhancement Proposals; PEP 524 <2>: os<8>.          (line   25)
* Python Enhancement Proposals; PEP 524 <3>: Library<71>.    (line  150)
* Python Enhancement Proposals; PEP 524 <4>: Library<71>.    (line  154)
* Python Enhancement Proposals; PEP 524 <5>: Random numbers. (line   42)
* Python Enhancement Proposals; PEP 525: PEP 525 Asynchronous Generators.
                                                             (line   23)
* Python Enhancement Proposals; PEP 525 <1>: Core and Builtins<72>.
                                                             (line   49)
* Python Enhancement Proposals; PEP 525 <2>: Yield expressions.
                                                             (line  104)
* Python Enhancement Proposals; PEP 525 <3>: Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line  166)
* Python Enhancement Proposals; PEP 525 <4>: sys --- 系統特定的參數與函式.
                                                             (line  976)
* Python Enhancement Proposals; PEP 525 <5>: sys --- 系統特定的參數與函式.
                                                             (line 1672)
* Python Enhancement Proposals; PEP 525 <6>: Code Objects Bit Flags.
                                                             (line   56)
* Python Enhancement Proposals; PEP 525 <7>: 術語表.         (line  112)
* Python Enhancement Proposals; PEP 526: 其他語言更動<3>.    (line   49)
* Python Enhancement Proposals; PEP 526 <1>: ast<3>.         (line   18)
* Python Enhancement Proposals; PEP 526 <2>: PEP 563 Postponed Evaluation of Annotations.
                                                             (line    8)
* Python Enhancement Proposals; PEP 526 <3>: PEP 526 Syntax for variable annotations.
                                                             (line   30)
* Python Enhancement Proposals; PEP 526 <4>: typing<9>.      (line   23)
* Python Enhancement Proposals; PEP 526 <5>: Core and Builtins<72>.
                                                             (line   51)
* Python Enhancement Proposals; PEP 526 <6>: Annotated assignment statements.
                                                             (line   42)
* Python Enhancement Proposals; PEP 526 <7>: 函式定義.       (line  148)
* Python Enhancement Proposals; PEP 526 <8>: 特別型式.       (line  152)
* Python Enhancement Proposals; PEP 526 <9>: Other special directives.
                                                             (line   69)
* Python Enhancement Proposals; PEP 526 <10>: dataclasses --- Data Classes.
                                                             (line   16)
* Python Enhancement Proposals; PEP 526 <11>: 類別變數.      (line    8)
* Python Enhancement Proposals; PEP 526 <12>: ast 輔助程式.  (line   18)
* Python Enhancement Proposals; PEP 526 <13>: 編譯器旗標<2>. (line   28)
* Python Enhancement Proposals; PEP 526 <14>: 術語表.        (line   48)
* Python Enhancement Proposals; PEP 526 <15>: 術語表.        (line 1304)
* Python Enhancement Proposals; PEP 528: PEP 528 Change Windows console encoding to UTF-8.
                                                             (line   17)
* Python Enhancement Proposals; PEP 528 <1>: UTF-8 模式.     (line   34)
* Python Enhancement Proposals; PEP 528 <2>: Global configuration variables.
                                                             (line  170)
* Python Enhancement Proposals; PEP 528 <3>: PyConfig.       (line  539)
* Python Enhancement Proposals; PEP 529: Changes in the Python API<3>.
                                                             (line    7)
* Python Enhancement Proposals; PEP 529 <1>: PEP 529 Change Windows filesystem encoding to UTF-8.
                                                             (line   22)
* Python Enhancement Proposals; PEP 529 <2>: Documentation<16>.
                                                             (line   29)
* Python Enhancement Proposals; PEP 529 <3>: Library<43>.    (line  619)
* Python Enhancement Proposals; PEP 529 <4>: Windows<57>.    (line   14)
* Python Enhancement Proposals; PEP 529 <5>: 環境變數.       (line  349)
* Python Enhancement Proposals; PEP 529 <6>: UTF-8 模式.     (line   37)
* Python Enhancement Proposals; PEP 529 <7>: Files and Directories.
                                                             (line  297)
* Python Enhancement Proposals; PEP 529 <8>: sys --- 系統特定的參數與函式.
                                                             (line  788)
* Python Enhancement Proposals; PEP 529 <9>: sys --- 系統特定的參數與函式.
                                                             (line 1753)
* Python Enhancement Proposals; PEP 529 <10>: File System Encoding.
                                                             (line    7)
* Python Enhancement Proposals; PEP 529 <11>: Global configuration variables.
                                                             (line  152)
* Python Enhancement Proposals; PEP 530: PEP 530 Asynchronous Comprehensions.
                                                             (line    6)
* Python Enhancement Proposals; PEP 530 <1>: PEP 530 Asynchronous Comprehensions.
                                                             (line   19)
* Python Enhancement Proposals; PEP 530 <2>: Core and Builtins<72>.
                                                             (line  145)
* Python Enhancement Proposals; PEP 530 <3>: Displays for lists sets and dictionaries.
                                                             (line   56)
* Python Enhancement Proposals; PEP 538: PEP 538 Legacy C Locale Coercion.
                                                             (line   11)
* Python Enhancement Proposals; PEP 538 <1>: PEP 538 Legacy C Locale Coercion.
                                                             (line   36)
* Python Enhancement Proposals; PEP 538 <2>: PEP 538 Legacy C Locale Coercion.
                                                             (line   48)
* Python Enhancement Proposals; PEP 538 <3>: PEP 540 Forced UTF-8 Runtime Mode.
                                                             (line   27)
* Python Enhancement Proposals; PEP 538 <4>: Documentation<43>.
                                                             (line   68)
* Python Enhancement Proposals; PEP 538 <5>: Documentation<44>.
                                                             (line    6)
* Python Enhancement Proposals; PEP 538 <6>: Core and Builtins<59>.
                                                             (line  134)
* Python Enhancement Proposals; PEP 538 <7>: 環境變數.       (line  418)
* Python Enhancement Proposals; PEP 538 <8>: 一般選項.       (line   87)
* Python Enhancement Proposals; PEP 538 <9>: locale --- 國際化服務.
                                                             (line  512)
* Python Enhancement Proposals; PEP 538 <10>: Python Configuration.
                                                             (line   13)
* Python Enhancement Proposals; PEP 539: PEP 539 New C API for Thread-Local Storage.
                                                             (line   12)
* Python Enhancement Proposals; PEP 539 <1>: PEP 539 New C API for Thread-Local Storage.
                                                             (line   30)
* Python Enhancement Proposals; PEP 539 <2>: C API<52>.      (line   13)
* Python Enhancement Proposals; PEP 539 <3>: Thread Specific Storage TSS API.
                                                             (line   15)
* Python Enhancement Proposals; PEP 540: PEP 540 Forced UTF-8 Runtime Mode.
                                                             (line   18)
* Python Enhancement Proposals; PEP 540 <1>: PEP 540 Forced UTF-8 Runtime Mode.
                                                             (line   35)
* Python Enhancement Proposals; PEP 540 <2>: Core and Builtins<56>.
                                                             (line   63)
* Python Enhancement Proposals; PEP 540 <3>: Python UTF-8 模式.
                                                             (line    6)
* Python Enhancement Proposals; PEP 540 <4>: locale --- 國際化服務.
                                                             (line  512)
* Python Enhancement Proposals; PEP 540 <5>: Python Configuration.
                                                             (line   14)
* Python Enhancement Proposals; PEP 544: typing<8>.          (line   32)
* Python Enhancement Proposals; PEP 544 <1>: 標稱 nominal 子型別 vs 結構子型別.
                                                             (line   21)
* Python Enhancement Proposals; PEP 544 <2>: Other special directives.
                                                             (line  151)
* Python Enhancement Proposals; PEP 545: PEP 545：Python 文件翻譯.
                                                             (line    6)
* Python Enhancement Proposals; PEP 545 <1>: PEP 545：Python 文件翻譯.
                                                             (line   20)
* Python Enhancement Proposals; PEP 552: 其他 CPython 實作更動.
                                                             (line   14)
* Python Enhancement Proposals; PEP 552 <1>: PEP 552 Hash-based pyc Files.
                                                             (line   15)
* Python Enhancement Proposals; PEP 552 <2>: PEP 552 Hash-based pyc Files.
                                                             (line   35)
* Python Enhancement Proposals; PEP 552 <3>: Library<48>.    (line  794)
* Python Enhancement Proposals; PEP 552 <4>: Core and Builtins<56>.
                                                             (line   75)
* Python Enhancement Proposals; PEP 552 <5>: 簡介<9>.        (line   87)
* Python Enhancement Proposals; PEP 552 <6>: py_compile — 編譯 Python 來源檔案.
                                                             (line   82)
* Python Enhancement Proposals; PEP 552 <7>: PyConfig.       (line  272)
* Python Enhancement Proposals; PEP 553: PEP 553 Built-in breakpoint.
                                                             (line   20)
* Python Enhancement Proposals; PEP 553 <1>: Core and Builtins<58>.
                                                             (line   72)
* Python Enhancement Proposals; PEP 554: PEP 684 A Per-Interpreter GIL.
                                                             (line   10)
* Python Enhancement Proposals; PEP 554 <1>: A Per-Interpreter GIL.
                                                             (line   13)
* Python Enhancement Proposals; PEP 557: dataclasses<3>.     (line   26)
* Python Enhancement Proposals; PEP 557 <1>: dataclasses --- Data Classes.
                                                             (line   13)
* Python Enhancement Proposals; PEP 560: PEP 560 Core Support for typing module and Generic Types.
                                                             (line   19)
* Python Enhancement Proposals; PEP 560 <1>: types<4>.       (line   12)
* Python Enhancement Proposals; PEP 560 <2>: Core and Builtins<56>.
                                                             (line   66)
* Python Enhancement Proposals; PEP 560 <3>: Resolving MRO entries.
                                                             (line   30)
* Python Enhancement Proposals; PEP 560 <4>: __class_getitem__ versus __getitem__.
                                                             (line   85)
* Python Enhancement Proposals; PEP 560 <5>: Dynamic Type Creation.
                                                             (line   59)
* Python Enhancement Proposals; PEP 560 <6>: Dynamic Type Creation.
                                                             (line   75)
* Python Enhancement Proposals; PEP 560 <7>: Dynamic Type Creation.
                                                             (line  113)
* Python Enhancement Proposals; PEP 562: PEP 562 Customization of Access to Module Attributes.
                                                             (line   16)
* Python Enhancement Proposals; PEP 562 <1>: Library<55>.    (line   63)
* Python Enhancement Proposals; PEP 562 <2>: Core and Builtins<56>.
                                                             (line   69)
* Python Enhancement Proposals; PEP 562 <3>: Customizing module attribute access.
                                                             (line   52)
* Python Enhancement Proposals; PEP 563: PEP 563 可能不是未來.
                                                             (line    6)
* Python Enhancement Proposals; PEP 563 <1>: PEP 563 Postponed Evaluation of Annotations.
                                                             (line   51)
* Python Enhancement Proposals; PEP 563 <2>: Library<29>.    (line  300)
* Python Enhancement Proposals; PEP 563 <3>: Core and Builtins<36>.
                                                             (line   83)
* Python Enhancement Proposals; PEP 563 <4>: Future statements.
                                                             (line   34)
* Python Enhancement Proposals; PEP 563 <5>: 函式定義.       (line  153)
* Python Enhancement Proposals; PEP 563 <6>: 常數<9>.        (line   29)
* Python Enhancement Proposals; PEP 563 <7>: 模組內容<9>.    (line  123)
* Python Enhancement Proposals; PEP 563 <8>: 模組內容<9>.    (line   44)
* Python Enhancement Proposals; PEP 564: PEP 564 New Time Functions With Nanosecond Resolution.
                                                             (line    8)
* Python Enhancement Proposals; PEP 564 <1>: PEP 564 New Time Functions With Nanosecond Resolution.
                                                             (line   33)
* Python Enhancement Proposals; PEP 564 <2>: time<5>.        (line    6)
* Python Enhancement Proposals; PEP 564 <3>: Library<57>.    (line  299)
* Python Enhancement Proposals; PEP 565: PEP 565 Show DeprecationWarning in __main__.
                                                             (line   41)
* Python Enhancement Proposals; PEP 565 <1>: 警告.           (line   22)
* Python Enhancement Proposals; PEP 566: Distribution metadata.
                                                             (line   19)
* Python Enhancement Proposals; PEP 567: contextvars.        (line   20)
* Python Enhancement Proposals; PEP 567 <1>: asyncio<7>.     (line   19)
* Python Enhancement Proposals; PEP 567 <2>: Documentation<43>.
                                                             (line   86)
* Python Enhancement Proposals; PEP 567 <3>: Documentation<45>.
                                                             (line    9)
* Python Enhancement Proposals; PEP 567 <4>: Core and Builtins<55>.
                                                             (line   63)
* Python Enhancement Proposals; PEP 567 <5>: contextvars --- 情境變數.
                                                             (line   18)
* Python Enhancement Proposals; PEP 567 <6>: 排程回呼函式.   (line   33)
* Python Enhancement Proposals; PEP 567 <7>: 排程延遲的回呼函式.
                                                             (line   25)
* Python Enhancement Proposals; PEP 567 <8>: 排程延遲的回呼函式.
                                                             (line   40)
* Python Enhancement Proposals; PEP 567 <9>: Future 物件<2>. (line   95)
* Python Enhancement Proposals; PEP 570: Positional-only parameters.
                                                             (line   70)
* Python Enhancement Proposals; PEP 570 <1>: Changes in the Python API<3>.
                                                             (line  160)
* Python Enhancement Proposals; PEP 570 <2>: Core and Builtins<46>.
                                                             (line   36)
* Python Enhancement Proposals; PEP 570 <3>: 函式定義.       (line  104)
* Python Enhancement Proposals; PEP 572: 其他語言更動.       (line   31)
* Python Enhancement Proposals; PEP 572 <1>: Assignment expressions.
                                                             (line   41)
* Python Enhancement Proposals; PEP 572 <2>: CPython 位元組碼變更<5>.
                                                             (line   27)
* Python Enhancement Proposals; PEP 572 <3>: Core and Builtins<18>.
                                                             (line   40)
* Python Enhancement Proposals; PEP 572 <4>: Documentation<34>.
                                                             (line    6)
* Python Enhancement Proposals; PEP 572 <5>: Core and Builtins<44>.
                                                             (line  184)
* Python Enhancement Proposals; PEP 572 <6>: Core and Builtins<49>.
                                                             (line   92)
* Python Enhancement Proposals; PEP 572 <7>: Dictionary displays.
                                                             (line   46)
* Python Enhancement Proposals; PEP 572 <8>: Assignment expressions<2>.
                                                             (line   29)
* Python Enhancement Proposals; PEP 572 <9>: Capture Patterns.
                                                             (line   17)
* Python Enhancement Proposals; PEP 572 <10>: 為何我不能在運算式 expression 中使用指派運算？.
                                                             (line   13)
* Python Enhancement Proposals; PEP 573: Summary -- Release highlights.
                                                             (line   27)
* Python Enhancement Proposals; PEP 573 <1>: New Features<4>.
                                                             (line    6)
* Python Enhancement Proposals; PEP 573 <2>: Core and Builtins<38>.
                                                             (line   19)
* Python Enhancement Proposals; PEP 573 <3>: C API<36>.      (line   57)
* Python Enhancement Proposals; PEP 574: Pickle protocol 5 with out-of-band data buffers.
                                                             (line   17)
* Python Enhancement Proposals; PEP 574 <1>: Data stream format.
                                                             (line   46)
* Python Enhancement Proposals; PEP 574 <2>: 範例<8>.        (line   63)
* Python Enhancement Proposals; PEP 578: PEP 578 Python Runtime Audit Hooks.
                                                             (line   12)
* Python Enhancement Proposals; PEP 578 <1>: 稽核事件表.     (line    8)
* Python Enhancement Proposals; PEP 578 <2>: sys --- 系統特定的參數與函式.
                                                             (line   56)
* Python Enhancement Proposals; PEP 578 <3>: 系統函式.       (line  135)
* Python Enhancement Proposals; PEP 584: Summary -- Release highlights.
                                                             (line    8)
* Python Enhancement Proposals; PEP 584 <1>: Dictionary Merge & Update Operators.
                                                             (line   19)
* Python Enhancement Proposals; PEP 584 <2>: Library<38>.    (line  192)
* Python Enhancement Proposals; PEP 584 <3>: Library<38>.    (line  195)
* Python Enhancement Proposals; PEP 584 <4>: Library<38>.    (line  209)
* Python Enhancement Proposals; PEP 584 <5>: Library<39>.    (line   49)
* Python Enhancement Proposals; PEP 584 <6>: Library<39>.    (line   62)
* Python Enhancement Proposals; PEP 584 <7>: Library<39>.    (line  120)
* Python Enhancement Proposals; PEP 584 <8>: Library<39>.    (line  142)
* Python Enhancement Proposals; PEP 584 <9>: ChainMap 物件.  (line   76)
* Python Enhancement Proposals; PEP 584 <10>: defaultdict 物件.
                                                             (line   47)
* Python Enhancement Proposals; PEP 584 <11>: OrderedDict 物件.
                                                             (line   95)
* Python Enhancement Proposals; PEP 584 <12>: weakref --- 弱參照.
                                                             (line  157)
* Python Enhancement Proposals; PEP 584 <13>: weakref --- 弱參照.
                                                             (line  173)
* Python Enhancement Proposals; PEP 584 <14>: Standard Interpreter Types.
                                                             (line  276)
* Python Enhancement Proposals; PEP 584 <15>: 行程參數.      (line   55)
* Python Enhancement Proposals; PEP 584 <16>: 行程參數.      (line   71)
* Python Enhancement Proposals; PEP 585: Summary -- Release highlights.
                                                             (line   10)
* Python Enhancement Proposals; PEP 585 <1>: Type Hinting Generics in Standard Collections.
                                                             (line   18)
* Python Enhancement Proposals; PEP 585 <2>: Library<17>.    (line  158)
* Python Enhancement Proposals; PEP 585 <3>: Library<26>.    (line  123)
* Python Enhancement Proposals; PEP 585 <4>: Documentation<22>.
                                                             (line   31)
* Python Enhancement Proposals; PEP 585 <5>: GenericAlias 物件的特殊屬性.
                                                             (line   52)
* Python Enhancement Proposals; PEP 585 <6>: collections abc --- 容器的抽象基底類別.
                                                             (line   86)
* Python Enhancement Proposals; PEP 585 <7>: Standard Interpreter Types.
                                                             (line  219)
* Python Enhancement Proposals; PEP 585 <8>: Introspection helpers.
                                                             (line  155)
* Python Enhancement Proposals; PEP 585 <9>: 棄用的別名.     (line   10)
* Python Enhancement Proposals; PEP 585 <10>: 內建型別的別名.
                                                             (line   15)
* Python Enhancement Proposals; PEP 585 <11>: 內建型別的別名.
                                                             (line   26)
* Python Enhancement Proposals; PEP 585 <12>: 內建型別的別名.
                                                             (line   37)
* Python Enhancement Proposals; PEP 585 <13>: 內建型別的別名.
                                                             (line   44)
* Python Enhancement Proposals; PEP 585 <14>: 內建型別的別名.
                                                             (line   54)
* Python Enhancement Proposals; PEP 585 <15>: 內建型別的別名.
                                                             (line   66)
* Python Enhancement Proposals; PEP 585 <16>: collections 中型別的別名.
                                                             (line   14)
* Python Enhancement Proposals; PEP 585 <17>: collections 中型別的別名.
                                                             (line   25)
* Python Enhancement Proposals; PEP 585 <18>: collections 中型別的別名.
                                                             (line   35)
* Python Enhancement Proposals; PEP 585 <19>: collections 中型別的別名.
                                                             (line   44)
* Python Enhancement Proposals; PEP 585 <20>: collections 中型別的別名.
                                                             (line   53)
* Python Enhancement Proposals; PEP 585 <21>: Aliases to other concrete types.
                                                             (line   18)
* Python Enhancement Proposals; PEP 585 <22>: collections abc 中容器 ABC 的別名.
                                                             (line   11)
* Python Enhancement Proposals; PEP 585 <23>: collections abc 中容器 ABC 的別名.
                                                             (line   29)
* Python Enhancement Proposals; PEP 585 <24>: collections abc 中容器 ABC 的別名.
                                                             (line   37)
* Python Enhancement Proposals; PEP 585 <25>: collections abc 中容器 ABC 的別名.
                                                             (line   46)
* Python Enhancement Proposals; PEP 585 <26>: collections abc 中容器 ABC 的別名.
                                                             (line   54)
* Python Enhancement Proposals; PEP 585 <27>: collections abc 中容器 ABC 的別名.
                                                             (line   62)
* Python Enhancement Proposals; PEP 585 <28>: collections abc 中容器 ABC 的別名.
                                                             (line   70)
* Python Enhancement Proposals; PEP 585 <29>: collections abc 中容器 ABC 的別名.
                                                             (line   78)
* Python Enhancement Proposals; PEP 585 <30>: collections abc 中容器 ABC 的別名.
                                                             (line   86)
* Python Enhancement Proposals; PEP 585 <31>: collections abc 中容器 ABC 的別名.
                                                             (line   94)
* Python Enhancement Proposals; PEP 585 <32>: collections abc 中容器 ABC 的別名.
                                                             (line  102)
* Python Enhancement Proposals; PEP 585 <33>: collections abc 中容器 ABC 的別名.
                                                             (line  110)
* Python Enhancement Proposals; PEP 585 <34>: Aliases to asynchronous ABCs in collections abc.
                                                             (line   18)
* Python Enhancement Proposals; PEP 585 <35>: Aliases to asynchronous ABCs in collections abc.
                                                             (line   33)
* Python Enhancement Proposals; PEP 585 <36>: Aliases to asynchronous ABCs in collections abc.
                                                             (line   45)
* Python Enhancement Proposals; PEP 585 <37>: Aliases to asynchronous ABCs in collections abc.
                                                             (line   55)
* Python Enhancement Proposals; PEP 585 <38>: Aliases to asynchronous ABCs in collections abc.
                                                             (line   65)
* Python Enhancement Proposals; PEP 585 <39>: Aliases to other ABCs in collections abc.
                                                             (line   11)
* Python Enhancement Proposals; PEP 585 <40>: Aliases to other ABCs in collections abc.
                                                             (line   19)
* Python Enhancement Proposals; PEP 585 <41>: Aliases to other ABCs in collections abc.
                                                             (line   31)
* Python Enhancement Proposals; PEP 585 <42>: Aliases to other ABCs in collections abc.
                                                             (line   47)
* Python Enhancement Proposals; PEP 585 <43>: Aliases to other ABCs in collections abc.
                                                             (line   65)
* Python Enhancement Proposals; PEP 585 <44>: contextlib ABC 的別名.
                                                             (line   18)
* Python Enhancement Proposals; PEP 585 <45>: contextlib ABC 的別名.
                                                             (line   37)
* Python Enhancement Proposals; PEP 585 <46>: Deprecation Timeline of Major Features.
                                                             (line   15)
* Python Enhancement Proposals; PEP 585 <47>: 術語表.        (line  532)
* Python Enhancement Proposals; PEP 586: typing<5>.          (line    8)
* Python Enhancement Proposals; PEP 586 <1>: typing<7>.      (line    6)
* Python Enhancement Proposals; PEP 586 <2>: typing<8>.      (line   18)
* Python Enhancement Proposals; PEP 586 <3>: 特別型式.       (line  139)
* Python Enhancement Proposals; PEP 587: Removed C APIs.     (line   99)
* Python Enhancement Proposals; PEP 587 <1>: PEP 587 Python Initialization Configuration.
                                                             (line    6)
* Python Enhancement Proposals; PEP 587 <2>: PEP 587 Python Initialization Configuration.
                                                             (line   83)
* Python Enhancement Proposals; PEP 587 <3>: C API<27>.      (line  124)
* Python Enhancement Proposals; PEP 587 <4>: Core and Builtins<44>.
                                                             (line   76)
* Python Enhancement Proposals; PEP 587 <5>: C API<43>.      (line    6)
* Python Enhancement Proposals; PEP 587 <6>: Python 初始化設定.
                                                             (line   32)
* Python Enhancement Proposals; PEP 589: typing<8>.          (line    8)
* Python Enhancement Proposals; PEP 589 <1>: Other special directives.
                                                             (line  450)
* Python Enhancement Proposals; PEP 590: Removed C APIs.     (line  124)
* Python Enhancement Proposals; PEP 590 <1>: 移植至 Python 3 11<2>.
                                                             (line   87)
* Python Enhancement Proposals; PEP 590 <2>: 最佳化<3>.      (line   50)
* Python Enhancement Proposals; PEP 590 <3>: Summary -- Release highlights.
                                                             (line   33)
* Python Enhancement Proposals; PEP 590 <4>: 最佳化<4>.      (line   37)
* Python Enhancement Proposals; PEP 590 <5>: PEP 590 Vectorcall a fast calling protocol for CPython.
                                                             (line   14)
* Python Enhancement Proposals; PEP 590 <6>: Core and Builtins<7>.
                                                             (line  170)
* Python Enhancement Proposals; PEP 590 <7>: Library<12>.    (line 1079)
* Python Enhancement Proposals; PEP 590 <8>: C API<12>.      (line  146)
* Python Enhancement Proposals; PEP 590 <9>: Core and Builtins<20>.
                                                             (line  113)
* Python Enhancement Proposals; PEP 590 <10>: Library<22>.   (line   69)
* Python Enhancement Proposals; PEP 590 <11>: Core and Builtins<25>.
                                                             (line   57)
* Python Enhancement Proposals; PEP 590 <12>: Core and Builtins<28>.
                                                             (line  118)
* Python Enhancement Proposals; PEP 590 <13>: Core and Builtins<29>.
                                                             (line  348)
* Python Enhancement Proposals; PEP 590 <14>: Core and Builtins<31>.
                                                             (line   27)
* Python Enhancement Proposals; PEP 590 <15>: Core and Builtins<31>.
                                                             (line   74)
* Python Enhancement Proposals; PEP 590 <16>: Core and Builtins<37>.
                                                             (line   10)
* Python Enhancement Proposals; PEP 590 <17>: Core and Builtins<37>.
                                                             (line   16)
* Python Enhancement Proposals; PEP 590 <18>: Core and Builtins<39>.
                                                             (line   39)
* Python Enhancement Proposals; PEP 590 <19>: Core and Builtins<39>.
                                                             (line   91)
* Python Enhancement Proposals; PEP 590 <20>: Core and Builtins<40>.
                                                             (line   42)
* Python Enhancement Proposals; PEP 590 <21>: Core and Builtins<40>.
                                                             (line   50)
* Python Enhancement Proposals; PEP 590 <22>: Core and Builtins<40>.
                                                             (line   67)
* Python Enhancement Proposals; PEP 590 <23>: C API<43>.     (line   17)
* Python Enhancement Proposals; PEP 590 <24>: Vectorcall 協定.
                                                             (line    8)
* Python Enhancement Proposals; PEP 591: typing<8>.          (line   25)
* Python Enhancement Proposals; PEP 591 <1>: 特別型式.       (line  195)
* Python Enhancement Proposals; PEP 591 <2>: 函式與裝飾器.   (line  335)
* Python Enhancement Proposals; PEP 593: Summary -- Release highlights.
                                                             (line   20)
* Python Enhancement Proposals; PEP 593 <1>: typing<6>.      (line    6)
* Python Enhancement Proposals; PEP 593 <2>: Library<40>.    (line   91)
* Python Enhancement Proposals; PEP 593 <3>: 特別型式.       (line  372)
* Python Enhancement Proposals; PEP 593 <4>: Introspection helpers.
                                                             (line   50)
* Python Enhancement Proposals; PEP 594: Summary -- Release Highlights.
                                                             (line   21)
* Python Enhancement Proposals; PEP 594 <1>: PEP 594 Remove "dead batteries" from the standard library.
                                                             (line    6)
* Python Enhancement Proposals; PEP 594 <2>: Python 3 13 中待移除的項目.
                                                             (line    6)
* Python Enhancement Proposals; PEP 594 <3>: asynchat 和 asyncore.
                                                             (line    6)
* Python Enhancement Proposals; PEP 594 <4>: smtpd.          (line    6)
* Python Enhancement Proposals; PEP 594 <5>: 發布重點摘要<2>.
                                                             (line   46)
* Python Enhancement Proposals; PEP 594 <6>: 模組.           (line    6)
* Python Enhancement Proposals; PEP 594 <7>: Library<12>.    (line  845)
* Python Enhancement Proposals; PEP 594 <8>: Library<12>.    (line  848)
* Python Enhancement Proposals; PEP 594 <9>: Library<12>.    (line  851)
* Python Enhancement Proposals; PEP 594 <10>: Library<12>.   (line  859)
* Python Enhancement Proposals; PEP 594 <11>: Library<12>.   (line  863)
* Python Enhancement Proposals; PEP 594 <12>: Library<12>.   (line  869)
* Python Enhancement Proposals; PEP 594 <13>: Library<12>.   (line  872)
* Python Enhancement Proposals; PEP 594 <14>: Library<12>.   (line  887)
* Python Enhancement Proposals; PEP 594 <15>: Library<12>.   (line  890)
* Python Enhancement Proposals; PEP 594 <16>: Library<12>.   (line  897)
* Python Enhancement Proposals; PEP 594 <17>: Library<12>.   (line  900)
* Python Enhancement Proposals; PEP 594 <18>: Library<12>.   (line  903)
* Python Enhancement Proposals; PEP 594 <19>: Library<12>.   (line  906)
* Python Enhancement Proposals; PEP 594 <20>: Library<12>.   (line  909)
* Python Enhancement Proposals; PEP 594 <21>: Library<12>.   (line  964)
* Python Enhancement Proposals; PEP 594 <22>: Library<12>.   (line  967)
* Python Enhancement Proposals; PEP 594 <23>: Library<12>.   (line  970)
* Python Enhancement Proposals; PEP 594 <24>: Library<12>.   (line  973)
* Python Enhancement Proposals; PEP 594 <25>: Library<19>.   (line  102)
* Python Enhancement Proposals; PEP 594 <26>: Library<20>.   (line  684)
* Python Enhancement Proposals; PEP 594 <27>: Library<21>.   (line   94)
* Python Enhancement Proposals; PEP 594 <28>: Library<22>.   (line  124)
* Python Enhancement Proposals; PEP 594 <29>: Library<22>.   (line  150)
* Python Enhancement Proposals; PEP 594 <30>: Tests<20>.     (line   25)
* Python Enhancement Proposals; PEP 596: Python 3 9 有什麼新功能.
                                                             (line   16)
* Python Enhancement Proposals; PEP 597: 摘要 -- 發布重點.   (line   44)
* Python Enhancement Proposals; PEP 597 <1>: Library<30>.    (line   44)
* Python Enhancement Proposals; PEP 597 <2>: 選擇性加入的編碼警告.
                                                             (line    6)
* Python Enhancement Proposals; PEP 602: Summary -- Release Highlights.
                                                             (line  158)
* Python Enhancement Proposals; PEP 602 <1>: Summary -- Release highlights.
                                                             (line   58)
* Python Enhancement Proposals; PEP 602 <2>: Python 的穩定性如何？.
                                                             (line    8)
* Python Enhancement Proposals; PEP 604: 摘要 -- 發布重點.   (line   26)
* Python Enhancement Proposals; PEP 604 <1>: PEP 604：新型聯集運算子.
                                                             (line   27)
* Python Enhancement Proposals; PEP 604 <2>: Library<33>.    (line   25)
* Python Enhancement Proposals; PEP 604 <3>: Documentation<31>.
                                                             (line    6)
* Python Enhancement Proposals; PEP 604 <4>: 聯合型別 Union Type.
                                                             (line   99)
* Python Enhancement Proposals; PEP 604 <5>: 手動取消字串化註釋.
                                                             (line   36)
* Python Enhancement Proposals; PEP 610: Distributions.      (line   28)
* Python Enhancement Proposals; PEP 612: 摘要 -- 發布重點.   (line   28)
* Python Enhancement Proposals; PEP 612 <1>: PEP 612：參數規範變數.
                                                             (line   20)
* Python Enhancement Proposals; PEP 612 <2>: Library<28>.    (line  691)
* Python Enhancement Proposals; PEP 612 <3>: Library<29>.    (line   95)
* Python Enhancement Proposals; PEP 612 <4>: Core and Builtins<34>.
                                                             (line   59)
* Python Enhancement Proposals; PEP 612 <5>: Library<33>.    (line   25)
* Python Enhancement Proposals; PEP 612 <6>: Library<33>.    (line  119)
* Python Enhancement Proposals; PEP 612 <7>: 註釋 callable 物件.
                                                             (line   72)
* Python Enhancement Proposals; PEP 612 <8>: 使用者定義泛型型別.
                                                             (line  166)
* Python Enhancement Proposals; PEP 612 <9>: 特別型式.       (line  112)
* Python Enhancement Proposals; PEP 612 <10>: Building generic types and type aliases.
                                                             (line  463)
* Python Enhancement Proposals; PEP 612 <11>: Aliases to other ABCs in collections abc.
                                                             (line   35)
* Python Enhancement Proposals; PEP 613: 摘要 -- 發布重點.   (line   30)
* Python Enhancement Proposals; PEP 613 <1>: PEP 613：型別別名 TypeAlias.
                                                             (line   20)
* Python Enhancement Proposals; PEP 613 <2>: Library<35>.    (line   98)
* Python Enhancement Proposals; PEP 613 <3>: 特別型別.       (line  216)
* Python Enhancement Proposals; PEP 614: Summary -- Release highlights.
                                                             (line   12)
* Python Enhancement Proposals; PEP 614 <1>: 其他語言更動<4>.
                                                             (line   38)
* Python Enhancement Proposals; PEP 614 <2>: Core and Builtins<40>.
                                                             (line  112)
* Python Enhancement Proposals; PEP 614 <3>: 函式定義.       (line   54)
* Python Enhancement Proposals; PEP 614 <4>: 類別定義.       (line   60)
* Python Enhancement Proposals; PEP 615: Summary -- Release highlights.
                                                             (line   50)
* Python Enhancement Proposals; PEP 615 <1>: zoneinfo.       (line   37)
* Python Enhancement Proposals; PEP 615 <2>: Library<37>.    (line   54)
* Python Enhancement Proposals; PEP 615 <3>: zoneinfo --- IANA 時區支援.
                                                             (line   14)
* Python Enhancement Proposals; PEP 616: Summary -- Release highlights.
                                                             (line   16)
* Python Enhancement Proposals; PEP 616 <1>: New String Methods to Remove Prefixes and Suffixes.
                                                             (line    9)
* Python Enhancement Proposals; PEP 616 <2>: Core and Builtins<39>.
                                                             (line   82)
* Python Enhancement Proposals; PEP 617: PEP 701 Syntactic formalization of f-strings.
                                                             (line   69)
* Python Enhancement Proposals; PEP 617 <1>: 模組.           (line   28)
* Python Enhancement Proposals; PEP 617 <2>: 帶括號的情境管理器.
                                                             (line   42)
* Python Enhancement Proposals; PEP 617 <3>: Summary -- Release highlights.
                                                             (line   30)
* Python Enhancement Proposals; PEP 617 <4>: New Parser.     (line   21)
* Python Enhancement Proposals; PEP 617 <5>: 已棄用<7>.      (line   95)
* Python Enhancement Proposals; PEP 617 <6>: Library<28>.    (line  178)
* Python Enhancement Proposals; PEP 617 <7>: Library<38>.    (line   34)
* Python Enhancement Proposals; PEP 617 <8>: 完整的語法規格書.
                                                             (line   16)
* Python Enhancement Proposals; PEP 618: 摘要 -- 發布重點.   (line   18)
* Python Enhancement Proposals; PEP 618 <1>: 其他語言更動<3>.
                                                             (line   15)
* Python Enhancement Proposals; PEP 618 <2>: Core and Builtins<37>.
                                                             (line  209)
* Python Enhancement Proposals; PEP 623: 發布重點摘要.       (line  104)
* Python Enhancement Proposals; PEP 623 <1>: 最佳化.         (line    7)
* Python Enhancement Proposals; PEP 623 <2>: 已移除<2>.      (line   11)
* Python Enhancement Proposals; PEP 623 <3>: 摘要 -- 發布重點.
                                                             (line   40)
* Python Enhancement Proposals; PEP 623 <4>: C API<20>.      (line   21)
* Python Enhancement Proposals; PEP 623 <5>: Core and Builtins<32>.
                                                             (line   10)
* Python Enhancement Proposals; PEP 623 <6>: Documentation<26>.
                                                             (line   10)
* Python Enhancement Proposals; PEP 623 <7>: Unicode 物件.   (line   17)
* Python Enhancement Proposals; PEP 624: 發布重點摘要<2>.    (line   49)
* Python Enhancement Proposals; PEP 624 <1>: 已移除<4>.      (line   94)
* Python Enhancement Proposals; PEP 624 <2>: 摘要 -- 發布重點.
                                                             (line   42)
* Python Enhancement Proposals; PEP 624 <3>: C API<27>.      (line  142)
* Python Enhancement Proposals; PEP 624#alternative-apis: 已移除<4>.
                                                             (line   94)
* Python Enhancement Proposals; PEP 626: Pending Removal in Python 3 14.
                                                             (line  121)
* Python Enhancement Proposals; PEP 626 <1>: 已棄用.         (line  211)
* Python Enhancement Proposals; PEP 626 <2>: Python 3 14 中待移除的項目.
                                                             (line  111)
* Python Enhancement Proposals; PEP 626 <3>: 摘要 -- 發布重點.
                                                             (line   22)
* Python Enhancement Proposals; PEP 626 <4>: Core and Builtins<21>.
                                                             (line  422)
* Python Enhancement Proposals; PEP 626 <5>: 用於程式碼物件的方法.
                                                             (line   81)
* Python Enhancement Proposals; PEP 626 <6>: Analysis functions.
                                                             (line  171)
* Python Enhancement Proposals; PEP 626 <7>: Python 3 14 中待移除的項目<3>.
                                                             (line  111)
* Python Enhancement Proposals; PEP 628: cmath.              (line    7)
* Python Enhancement Proposals; PEP 628 <1>: math<7>.        (line    7)
* Python Enhancement Proposals; PEP 628 <2>: Library<72>.    (line   32)
* Python Enhancement Proposals; PEP 632: 發布重點摘要.       (line  108)
* Python Enhancement Proposals; PEP 632 <1>: distutils.      (line    7)
* Python Enhancement Proposals; PEP 632 <2>: 摘要 -- 發布重點.
                                                             (line   38)
* Python Enhancement Proposals; PEP 632 <3>: distutils<2>.   (line   11)
* Python Enhancement Proposals; PEP 632 <4>: Library<19>.    (line   38)
* Python Enhancement Proposals; PEP 634: 摘要 -- 發布重點.   (line    8)
* Python Enhancement Proposals; PEP 634 <1>: 其他主要功能.   (line   49)
* Python Enhancement Proposals; PEP 634 <2>: Core and Builtins<22>.
                                                             (line   55)
* Python Enhancement Proposals; PEP 634 <3>: Core and Builtins<30>.
                                                             (line   54)
* Python Enhancement Proposals; PEP 634 <4>: Core and Builtins<32>.
                                                             (line   57)
* Python Enhancement Proposals; PEP 634 <5>: Customizing positional arguments in class pattern matching.
                                                             (line   32)
* Python Enhancement Proposals; PEP 634 <6>: The match statement.
                                                             (line   33)
* Python Enhancement Proposals; PEP 634 <7>: Class Patterns. (line  136)
* Python Enhancement Proposals; PEP 634 <8>: PyTypeObject Slots.
                                                             (line  772)
* Python Enhancement Proposals; PEP 634 <9>: PyTypeObject Slots.
                                                             (line  796)
* Python Enhancement Proposals; PEP 635: 摘要 -- 發布重點.   (line   10)
* Python Enhancement Proposals; PEP 635 <1>: 其他主要功能.   (line   49)
* Python Enhancement Proposals; PEP 636: 摘要 -- 發布重點.   (line   12)
* Python Enhancement Proposals; PEP 636 <1>: 其他主要功能.   (line   50)
* Python Enhancement Proposals; PEP 636 <2>: match 陳述式.   (line  169)
* Python Enhancement Proposals; PEP 636 <3>: The match statement.
                                                             (line   35)
* Python Enhancement Proposals; PEP 636 <4>: Class Patterns. (line  138)
* Python Enhancement Proposals; PEP 644: hashlib.            (line    8)
* Python Enhancement Proposals; PEP 644 <1>: 摘要 -- 發布重點.
                                                             (line   36)
* Python Enhancement Proposals; PEP 644 <2>: hashlib<3>.     (line    6)
* Python Enhancement Proposals; PEP 644 <3>: ssl<3>.         (line    6)
* Python Enhancement Proposals; PEP 644 <4>: 建置變更<3>.    (line    6)
* Python Enhancement Proposals; PEP 644 <5>: Core and Builtins<11>.
                                                             (line  167)
* Python Enhancement Proposals; PEP 644 <6>: Library<20>.    (line  525)
* Python Enhancement Proposals; PEP 644 <7>: Build<29>.      (line    9)
* Python Enhancement Proposals; PEP 644 <8>: ssl --- socket 物件的 TLS/SSL 包裝器.
                                                             (line   49)
* Python Enhancement Proposals; PEP 646: PEP 646：可變參數泛型 variadic generics.
                                                             (line    7)
* Python Enhancement Proposals; PEP 646 <1>: PEP 646：可變參數泛型 variadic generics.
                                                             (line   15)
* Python Enhancement Proposals; PEP 646 <2>: Building generic types and type aliases.
                                                             (line  320)
* Python Enhancement Proposals; PEP 647: 摘要 -- 發布重點.   (line   32)
* Python Enhancement Proposals; PEP 647 <1>: PEP 647：使用者定義的型別防護.
                                                             (line    8)
* Python Enhancement Proposals; PEP 647 <2>: Library<29>.    (line  182)
* Python Enhancement Proposals; PEP 647 <3>: 特別型式.       (line  486)
* Python Enhancement Proposals; PEP 649: Annotation scopes.  (line   10)
* Python Enhancement Proposals; PEP 649 <1>: 模組內容<9>.    (line  124)
* Python Enhancement Proposals; PEP 652: PEP 652：維護穩定 ABI.
                                                             (line   10)
* Python Enhancement Proposals; PEP 652 <1>: C API<28>.      (line   41)
* Python Enhancement Proposals; PEP 654: PEP 654：例外群組與 except*.
                                                             (line    6)
* Python Enhancement Proposals; PEP 654 <1>: PEP 654：例外群組與 except*.
                                                             (line   11)
* Python Enhancement Proposals; PEP 654 <2>: 新增 opcode.    (line   17)
* Python Enhancement Proposals; PEP 654 <3>: Core and Builtins<21>.
                                                             (line  174)
* Python Enhancement Proposals; PEP 654 <4>: Core and Builtins<26>.
                                                             (line  146)
* Python Enhancement Proposals; PEP 654 <5>: Core and Builtins<28>.
                                                             (line   88)
* Python Enhancement Proposals; PEP 655: PEP 655：標記獨立 TypedDict 項目為必要或不必要.
                                                             (line   28)
* Python Enhancement Proposals; PEP 655 <1>: Library<21>.    (line  266)
* Python Enhancement Proposals; PEP 655 <2>: 特別型式.       (line  208)
* Python Enhancement Proposals; PEP 655 <3>: 特別型式.       (line  216)
* Python Enhancement Proposals; PEP 655 <4>: Other special directives.
                                                             (line  456)
* Python Enhancement Proposals; PEP 657: PEP 657：回溯 traceback 中更細緻的錯誤位置.
                                                             (line   52)
* Python Enhancement Proposals; PEP 657 <1>: inspect<2>.     (line   16)
* Python Enhancement Proposals; PEP 657 <2>: Library<21>.    (line  223)
* Python Enhancement Proposals; PEP 657 <3>: Core and Builtins<29>.
                                                             (line  337)
* Python Enhancement Proposals; PEP 659: PEP 659：特化的適應性直譯器.
                                                             (line    6)
* Python Enhancement Proposals; PEP 659 <1>: PEP 659：特化的適應性直譯器.
                                                             (line   24)
* Python Enhancement Proposals; PEP 667: Summary -- Release Highlights.
                                                             (line   40)
* Python Enhancement Proposals; PEP 667 <1>: Defined mutation semantics for locals.
                                                             (line    8)
* Python Enhancement Proposals; PEP 667 <2>: Defined mutation semantics for locals.
                                                             (line   41)
* Python Enhancement Proposals; PEP 667 <3>: New Features<2>.
                                                             (line  240)
* Python Enhancement Proposals; PEP 667 <4>: Changes in the Python API.
                                                             (line   49)
* Python Enhancement Proposals; PEP 667 <5>: Changes in the Python API.
                                                             (line   57)
* Python Enhancement Proposals; PEP 667 <6>: Changes in the Python API.
                                                             (line   63)
* Python Enhancement Proposals; PEP 667 <7>: Changes in the C API.
                                                             (line   88)
* Python Enhancement Proposals; PEP 667 <8>: Changes in the C API.
                                                             (line   95)
* Python Enhancement Proposals; PEP 667 <9>: Changes in the C API.
                                                             (line  100)
* Python Enhancement Proposals; PEP 667 <10>: Changes in the C API.
                                                             (line  105)
* Python Enhancement Proposals; PEP 667 <11>: Deprecated C APIs.
                                                             (line   53)
* Python Enhancement Proposals; PEP 667 <12>: 內建函式.      (line 1021)
* Python Enhancement Proposals; PEP 667 <13>: pdb --- The Python Debugger.
                                                             (line  118)
* Python Enhancement Proposals; PEP 667 <14>: Reflection.    (line   41)
* Python Enhancement Proposals; PEP 667 <15>: Frame 物件.    (line  125)
* Python Enhancement Proposals; PEP 669: PEP 669 Low impact monitoring for CPython.
                                                             (line    6)
* Python Enhancement Proposals; PEP 669 <1>: Core and Builtins<14>.
                                                             (line  203)
* Python Enhancement Proposals; PEP 670: 發布重點摘要<2>.    (line   51)
* Python Enhancement Proposals; PEP 670 <1>: 移植至 Python 3 11<2>.
                                                             (line   10)
* Python Enhancement Proposals; PEP 673: PEP 673：Self 型別. (line   30)
* Python Enhancement Proposals; PEP 673 <1>: Library<23>.    (line  134)
* Python Enhancement Proposals; PEP 673 <2>: 特別型別.       (line  184)
* Python Enhancement Proposals; PEP 675: PEP 675：任意的文本字串型別 Arbitrary literal string type.
                                                             (line   30)
* Python Enhancement Proposals; PEP 675 <1>: Library<22>.    (line   59)
* Python Enhancement Proposals; PEP 675 <2>: 特別型別.       (line   91)
* Python Enhancement Proposals; PEP 676: Documentation<17>.  (line    8)
* Python Enhancement Proposals; PEP 678: 其他語言更動.       (line   36)
* Python Enhancement Proposals; PEP 678 <1>: PEP 678：運用例外註解使其更加詳盡.
                                                             (line   10)
* Python Enhancement Proposals; PEP 678 <2>: Core and Builtins<14>.
                                                             (line  183)
* Python Enhancement Proposals; PEP 678 <3>: Core and Builtins<15>.
                                                             (line   57)
* Python Enhancement Proposals; PEP 678 <4>: Core and Builtins<22>.
                                                             (line  118)
* Python Enhancement Proposals; PEP 680: 發布重點摘要<2>.    (line   20)
* Python Enhancement Proposals; PEP 680 <1>: 新增模組<2>.    (line    6)
* Python Enhancement Proposals; PEP 680 <2>: Library<22>.    (line  205)
* Python Enhancement Proposals; PEP 681: PEP 681：資料類別轉換 Data class transforms.
                                                             (line   29)
* Python Enhancement Proposals; PEP 681 <1>: Library<21>.    (line  110)
* Python Enhancement Proposals; PEP 681 <2>: 函式與裝飾器.   (line  243)
* Python Enhancement Proposals; PEP 682: 其他語言更動<2>.    (line   43)
* Python Enhancement Proposals; PEP 682 <1>: 格式規格 Format Specification 迷你語言.
                                                             (line   78)
* Python Enhancement Proposals; PEP 683: 新增特性<2>.        (line  145)
* Python Enhancement Proposals; PEP 683 <1>: Core and Builtins<14>.
                                                             (line   73)
* Python Enhancement Proposals; PEP 683 <2>: 術語表.         (line  592)
* Python Enhancement Proposals; PEP 684: PEP 684 A Per-Interpreter GIL.
                                                             (line    6)
* Python Enhancement Proposals; PEP 684 <1>: 新增特性<2>.    (line  180)
* Python Enhancement Proposals; PEP 686: Python UTF-8 模式.  (line   71)
* Python Enhancement Proposals; PEP 686 <1>: 文字編碼.       (line   29)
* Python Enhancement Proposals; PEP 687: Library<8>.         (line  137)
* Python Enhancement Proposals; PEP 687 <1>: Core and Builtins<13>.
                                                             (line  326)
* Python Enhancement Proposals; PEP 687 <2>: Library<13>.    (line  290)
* Python Enhancement Proposals; PEP 687 <3>: Library<13>.    (line  297)
* Python Enhancement Proposals; PEP 687 <4>: Library<13>.    (line  330)
* Python Enhancement Proposals; PEP 687 <5>: Library<13>.    (line  333)
* Python Enhancement Proposals; PEP 687 <6>: Library<13>.    (line  343)
* Python Enhancement Proposals; PEP 687 <7>: Library<13>.    (line  400)
* Python Enhancement Proposals; PEP 687 <8>: Core and Builtins<15>.
                                                             (line   78)
* Python Enhancement Proposals; PEP 687 <9>: Library<15>.    (line  111)
* Python Enhancement Proposals; PEP 687 <10>: Library<15>.   (line  118)
* Python Enhancement Proposals; PEP 688: PEP 688 Making the buffer protocol accessible in Python.
                                                             (line    6)
* Python Enhancement Proposals; PEP 688 <1>: Core and Builtins<14>.
                                                             (line  211)
* Python Enhancement Proposals; PEP 688 <2>: Emulating buffer types.
                                                             (line   39)
* Python Enhancement Proposals; PEP 688 <3>: Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line  176)
* Python Enhancement Proposals; PEP 689: C API<15>.          (line   26)
* Python Enhancement Proposals; PEP 692: PEP 692 Using TypedDict for more precise **kwargs typing.
                                                             (line   10)
* Python Enhancement Proposals; PEP 692 <1>: PEP 692 Using TypedDict for more precise **kwargs typing.
                                                             (line   21)
* Python Enhancement Proposals; PEP 692 <2>: Library<13>.    (line  117)
* Python Enhancement Proposals; PEP 692 <3>: Documentation<8>.
                                                             (line   11)
* Python Enhancement Proposals; PEP 692 <4>: 特別型式.       (line  566)
* Python Enhancement Proposals; PEP 693: Python 3 12 有什麼新功能.
                                                             (line   15)
* Python Enhancement Proposals; PEP 695: PEP 695：型別參數語法.
                                                             (line   10)
* Python Enhancement Proposals; PEP 695 <1>: PEP 695：型別參數語法.
                                                             (line   61)
* Python Enhancement Proposals; PEP 695 <2>: CPython 位元組碼變更.
                                                             (line   41)
* Python Enhancement Proposals; PEP 695 <3>: Library<4>.     (line   76)
* Python Enhancement Proposals; PEP 695 <4>: Library<6>.     (line  123)
* Python Enhancement Proposals; PEP 695 <5>: Library<12>.    (line   95)
* Python Enhancement Proposals; PEP 695 <6>: Library<12>.    (line  661)
* Python Enhancement Proposals; PEP 695 <7>: Library<12>.    (line  856)
* Python Enhancement Proposals; PEP 695 <8>: Library<12>.    (line  949)
* Python Enhancement Proposals; PEP 695 <9>: Core and Builtins<14>.
                                                             (line   13)
* Python Enhancement Proposals; PEP 695 <10>: Core and Builtins<14>.
                                                             (line  108)
* Python Enhancement Proposals; PEP 695 <11>: Library<13>.   (line    7)
* Python Enhancement Proposals; PEP 695 <12>: Annotation scopes.
                                                             (line   55)
* Python Enhancement Proposals; PEP 695 <13>: type 陳述式.   (line   40)
* Python Enhancement Proposals; PEP 695 <14>: 特別型別.      (line   57)
* Python Enhancement Proposals; PEP 695 <15>: Building generic types and type aliases.
                                                             (line  113)
* Python Enhancement Proposals; PEP 695 <16>: Building generic types and type aliases.
                                                             (line  212)
* Python Enhancement Proposals; PEP 695 <17>: Building generic types and type aliases.
                                                             (line  346)
* Python Enhancement Proposals; PEP 695 <18>: Building generic types and type aliases.
                                                             (line  452)
* Python Enhancement Proposals; PEP 695 <19>: Deprecation Timeline of Major Features.
                                                             (line   29)
* Python Enhancement Proposals; PEP 696: Summary -- Release Highlights.
                                                             (line  112)
* Python Enhancement Proposals; PEP 696 <1>: Core and Builtins<7>.
                                                             (line  190)
* Python Enhancement Proposals; PEP 696 <2>: Annotation scopes.
                                                             (line   58)
* Python Enhancement Proposals; PEP 696 <3>: Type parameter lists.
                                                             (line    8)
* Python Enhancement Proposals; PEP 697: 新增特性<2>.        (line    6)
* Python Enhancement Proposals; PEP 697 <1>: 新增特性<2>.    (line   32)
* Python Enhancement Proposals; PEP 697 <2>: C API<13>.      (line   37)
* Python Enhancement Proposals; PEP 698: PEP 698 Override Decorator for Static Typing.
                                                             (line   30)
* Python Enhancement Proposals; PEP 698 <1>: Library<15>.    (line  100)
* Python Enhancement Proposals; PEP 698 <2>: 函式與裝飾器.   (line  407)
* Python Enhancement Proposals; PEP 699: Pending Removal in Python 3 14<2>.
                                                             (line    7)
* Python Enhancement Proposals; PEP 699 <1>: 已棄用<2>.      (line    6)
* Python Enhancement Proposals; PEP 699 <2>: Python 3 14 中待移除的項目<2>.
                                                             (line    7)
* Python Enhancement Proposals; PEP 699 <3>: Build<16>.      (line   15)
* Python Enhancement Proposals; PEP 699 <4>: Python 3 14 中待移除的項目<4>.
                                                             (line    7)
* Python Enhancement Proposals; PEP 7:   Build and C API Changes<2>.
                                                             (line    9)
* Python Enhancement Proposals; PEP 7 <1>: 建置需求.         (line   47)
* Python Enhancement Proposals; PEP 7 <2>: 編寫標準.         (line    6)
* Python Enhancement Proposals; PEP 7 <3>: 有用的巨集.       (line  148)
* Python Enhancement Proposals; PEP 7 <4>: 有用的巨集.       (line  165)
* Python Enhancement Proposals; PEP 701: PEP 701 Syntactic formalization of f-strings.
                                                             (line    6)
* Python Enhancement Proposals; PEP 701 <1>: PEP 701 Syntactic formalization of f-strings.
                                                             (line   66)
* Python Enhancement Proposals; PEP 701 <2>: tokenize.       (line    6)
* Python Enhancement Proposals; PEP 701 <3>: 最佳化.         (line   26)
* Python Enhancement Proposals; PEP 701 <4>: Python API 的變更.
                                                             (line   76)
* Python Enhancement Proposals; PEP 701 <5>: Python API 的變更.
                                                             (line   78)
* Python Enhancement Proposals; PEP 701 <6>: Python API 的變更.
                                                             (line  100)
* Python Enhancement Proposals; PEP 702: Summary -- Release Highlights.
                                                             (line  116)
* Python Enhancement Proposals; PEP 702 <1>: warnings.       (line    6)
* Python Enhancement Proposals; PEP 702 <2>: Library<10>.    (line  469)
* Python Enhancement Proposals; PEP 702 <3>: Available Functions.
                                                             (line  181)
* Python Enhancement Proposals; PEP 703: Summary -- Release Highlights.
                                                             (line   10)
* Python Enhancement Proposals; PEP 703 <1>: Summary -- Release Highlights.
                                                             (line   46)
* Python Enhancement Proposals; PEP 703 <2>: Free-threaded CPython.
                                                             (line   45)
* Python Enhancement Proposals; PEP 703 <3>: Core and Builtins<9>.
                                                             (line   11)
* Python Enhancement Proposals; PEP 703 <4>: C API<11>.      (line  137)
* Python Enhancement Proposals; PEP 703 <5>: Installing Free-threaded Binaries.
                                                             (line   11)
* Python Enhancement Proposals; PEP 703 <6>: 不能擺脫全局直譯器鎖嗎？.
                                                             (line   12)
* Python Enhancement Proposals; PEP 703 <7>: 術語表.         (line  444)
* Python Enhancement Proposals; PEP 703 <8>: 術語表.         (line  558)
* Python Enhancement Proposals; PEP 705: Summary -- Release Highlights.
                                                             (line  119)
* Python Enhancement Proposals; PEP 705 <1>: typing.         (line    6)
* Python Enhancement Proposals; PEP 705 <2>: Library<8>.     (line   17)
* Python Enhancement Proposals; PEP 705 <3>: 特別型式.       (line  237)
* Python Enhancement Proposals; PEP 706: 其他語言更動.       (line   78)
* Python Enhancement Proposals; PEP 706 <1>: tarfile.        (line   13)
* Python Enhancement Proposals; PEP 706 <2>: tarfile<2>.     (line   13)
* Python Enhancement Proposals; PEP 706 <3>: tarfile<3>.     (line   13)
* Python Enhancement Proposals; PEP 706 <4>: tarfile<5>.     (line   13)
* Python Enhancement Proposals; PEP 706 <5>: Extraction filters.
                                                             (line   22)
* Python Enhancement Proposals; PEP 709: Changes in the Python API.
                                                             (line   56)
* Python Enhancement Proposals; PEP 709 <1>: PEP 709 Comprehension inlining.
                                                             (line    9)
* Python Enhancement Proposals; PEP 709 <2>: PEP 709 Comprehension inlining.
                                                             (line   35)
* Python Enhancement Proposals; PEP 709 <3>: CPython 位元組碼變更.
                                                             (line   33)
* Python Enhancement Proposals; PEP 709 <4>: Core and Builtins<14>.
                                                             (line  213)
* Python Enhancement Proposals; PEP 709 <5>: 內建函式.       (line 1019)
* Python Enhancement Proposals; PEP 719: What's New In Python 3 13.
                                                             (line   16)
* Python Enhancement Proposals; PEP 730: Summary -- Release Highlights.
                                                             (line  129)
* Python Enhancement Proposals; PEP 730 <1>: Support for mobile platforms.
                                                             (line    6)
* Python Enhancement Proposals; PEP 730 <2>: Support for mobile platforms.
                                                             (line   22)
* Python Enhancement Proposals; PEP 734: Library<6>.         (line  161)
* Python Enhancement Proposals; PEP 737: New Features<2>.    (line  218)
* Python Enhancement Proposals; PEP 737 <1>: C API<7>.       (line    6)
* Python Enhancement Proposals; PEP 737 <2>: C API<7>.       (line   49)
* Python Enhancement Proposals; PEP 738: Summary -- Release Highlights.
                                                             (line  130)
* Python Enhancement Proposals; PEP 738 <1>: Support for mobile platforms.
                                                             (line   15)
* Python Enhancement Proposals; PEP 738 <2>: Support for mobile platforms.
                                                             (line   22)
* Python Enhancement Proposals; PEP 738 <3>: Library<6>.     (line   54)
* Python Enhancement Proposals; PEP 742: Summary -- Release Highlights.
                                                             (line  123)
* Python Enhancement Proposals; PEP 742 <1>: typing.         (line    9)
* Python Enhancement Proposals; PEP 742 <2>: Library<6>.     (line  239)
* Python Enhancement Proposals; PEP 742 <3>: 特別型式.       (line  464)
* Python Enhancement Proposals; PEP 744: Summary -- Release Highlights.
                                                             (line   11)
* Python Enhancement Proposals; PEP 744 <1>: Summary -- Release Highlights.
                                                             (line   50)
* Python Enhancement Proposals; PEP 744 <2>: An experimental just-in-time JIT compiler.
                                                             (line   60)
* Python Enhancement Proposals; PEP 8:   函式庫變更.         (line   26)
* Python Enhancement Proposals; PEP 8 <1>: Library<57>.      (line  124)
* Python Enhancement Proposals; PEP 8 <2>: IDLE<61>.         (line   81)
* Python Enhancement Proposals; PEP 8 <3>: 間奏曲：程式碼風格 Coding Style.
                                                             (line   11)
* Python Enhancement Proposals; PEP 8 <4>: 編輯器與 IDE.     (line    7)
* Python Enhancement Proposals; PEP 8 <5>: Value comparisons.
                                                             (line   61)
* Python Enhancement Proposals; PEP 8 <6>: 內建函式.         (line 1641)
* Python Enhancement Proposals; PEP 8 <7>: 雜項說明.         (line   32)
* Python Enhancement Proposals; PEP 8 <8>: Python 程式碼是否有編碼標準或風格指南？.
                                                             (line    6)
* Python Enhancement Proposals; PEP 8 <9>: 我什麼時候可以依靠 is 運算子進行識別性測試？.
                                                             (line   51)
* Python Enhancement Proposals; PEP 8 <10>: 如何防止編輯器在我的 Python 原始碼中插入 tab？.
                                                             (line    6)
* PYTHON_BASIC_REPL:                     A better interactive interpreter.
                                                             (line   27)
* PYTHON_BASIC_REPL <1>:                 Core and Builtins<5>.
                                                             (line   55)
* PYTHON_BASIC_REPL <2>:                 互動模式<2>.        (line   23)
* python_branch() (於 platform 模組中):  跨平台.             (line   74)
* python_build() (於 platform 模組中):   跨平台.             (line   65)
* PYTHON_COLORS:                         Summary -- Release Highlights.
                                                             (line   57)
* PYTHON_COLORS <1>:                     Improved error messages.
                                                             (line    8)
* PYTHON_COLORS <2>:                     doctest.            (line    7)
* PYTHON_COLORS <3>:                     Controlling color.  (line   22)
* python_compiler() (於 platform 模組中): 跨平台.            (line   70)
* PYTHON_CPU_COUNT:                      os.                 (line   11)
* PYTHON_CPU_COUNT <1>:                  Miscellaneous options.
                                                             (line  363)
* PYTHON_CPU_COUNT <2>:                  Miscellaneous System Information.
                                                             (line   48)
* PYTHON_CPU_COUNT <3>:                  Miscellaneous System Information.
                                                             (line   69)
* PYTHON_CPU_COUNT <4>:                  Miscellaneous<2>.   (line   31)
* PYTHON_CPU_COUNT <5>:                  PyConfig.           (line  494)
* PYTHON_DOM:                            模組內容<6>.        (line   23)
* PYTHON_FROZEN_MODULES:                 Other Language Changes.
                                                             (line   46)
* PYTHON_FROZEN_MODULES <1>:             Core and Builtins<12>.
                                                             (line  105)
* PYTHON_FROZEN_MODULES <2>:             Miscellaneous options.
                                                             (line  334)
* PYTHON_GIL:                            Free-threaded CPython.
                                                             (line   22)
* PYTHON_GIL <1>:                        Free-threaded CPython.
                                                             (line   38)
* PYTHON_GIL <2>:                        Core and Builtins<2>.
                                                             (line   40)
* PYTHON_GIL <3>:                        Miscellaneous options.
                                                             (line  381)
* PYTHON_GIL <4>:                        術語表.             (line  555)
* PYTHON_HISTORY:                        Other Language Changes.
                                                             (line   57)
* PYTHON_HISTORY <1>:                    Library<10>.        (line  544)
* python_implementation() (於 platform 模組中): 跨平台.      (line   78)
* python_is_optimized() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  248)
* PYTHON_PERF_JIT_SUPPORT:               Other Language Changes.
                                                             (line   52)
* PYTHON_PERF_JIT_SUPPORT <1>:           Miscellaneous options.
                                                             (line  353)
* PYTHON_PERF_JIT_SUPPORT <2>:           PyConfig.           (line  871)
* PYTHON_PERF_JIT_SUPPORT <3>:           PyConfig.           (line  874)
* PYTHON_PERF_JIT_SUPPORT <4>:           How to work without frame pointers.
                                                             (line   14)
* PYTHON_PRESITE:                        Miscellaneous options.
                                                             (line  375)
* PYTHON_PRESITE <1>:                    PyConfig.           (line  772)
* PYTHON_PRESITE=package.module:         Core and Builtins<12>.
                                                             (line  154)
* python_revision() (於 platform 模組中): 跨平台.            (line   83)
* python_version_tuple() (於 platform 模組中): 跨平台.       (line   94)
* python_version() (於 platform 模組中): 跨平台.             (line   87)
* python-m-py_compile 命令列選項; -:     Command-Line Interface<3>.
                                                             (line   13)
* python-m-py_compile 命令列選項; -q:    Command-Line Interface<3>.
                                                             (line   19)
* python-m-py_compile 命令列選項; -quiet: Command-Line Interface<3>.
                                                             (line   19)
* python-m-py_compile 命令列選項; <file>: Command-Line Interface<3>.
                                                             (line   13)
* python-m-sqlite3-[-h]-[-v]-[filename]-[sql] 命令列選項; -h: 命令列介面.
                                                             (line   14)
* python-m-sqlite3-[-h]-[-v]-[filename]-[sql] 命令列選項; -help: 命令列介面.
                                                             (line   14)
* python-m-sqlite3-[-h]-[-v]-[filename]-[sql] 命令列選項; -v: 命令列介面.
                                                             (line   18)
* python-m-sqlite3-[-h]-[-v]-[filename]-[sql] 命令列選項; -version: 命令列介面.
                                                             (line   18)
* PYTHONASYNCIODEBUG:                    啟用除錯模式.       (line   10)
* PYTHONASYNCIODEBUG <1>:                除錯模式.           (line   11)
* PYTHONASYNCIODEBUG <2>:                Python 開發模式的影響.
                                                             (line   58)
* PYTHONBREAKPOINT:                      PEP 553 Built-in breakpoint.
                                                             (line   13)
* PYTHONBREAKPOINT <1>:                  內建函式.           (line  147)
* PYTHONBREAKPOINT <2>:                  sys --- 系統特定的參數與函式.
                                                             (line  252)
* PYTHONBREAKPOINT <3>:                  sys --- 系統特定的參數與函式.
                                                             (line  266)
* PYTHONBREAKPOINT <4>:                  sys --- 系統特定的參數與函式.
                                                             (line  270)
* PYTHONCASEOK:                          Changes in the Python API<2>.
                                                             (line   29)
* PYTHONCASEOK <1>:                      PEP 235 Importing Modules on Case-Insensitive Platforms.
                                                             (line   17)
* PYTHONCASEOK <2>:                      Library<39>.        (line  144)
* PYTHONCASEOK <3>:                      內建函式.           (line 2047)
* PYTHONCOERCECLOCALE:                   PEP 538 Legacy C Locale Coercion.
                                                             (line   13)
* PYTHONCOERCECLOCALE <1>:               一般選項.           (line   87)
* PYTHONCOERCECLOCALE <2>:               Python UTF-8 模式.  (line   57)
* PYTHONCOERCECLOCALE <3>:               Python Configuration.
                                                             (line   15)
* PYTHONDEBUG:                           Miscellaneous options.
                                                             (line   37)
* PYTHONDEBUG <1>:                       Python Debug Build. (line   20)
* PYTHONDEBUG <2>:                       Global configuration variables.
                                                             (line   38)
* PYTHONDEBUG <3>:                       PyConfig.           (line  664)
* PYTHONDEVMODE:                         Python Development Mode -X dev.
                                                             (line    6)
* PYTHONDEVMODE <1>:                     Miscellaneous options.
                                                             (line  293)
* PYTHONDEVMODE <2>:                     Python 開發模式.    (line   11)
* PYTHONDEVMODE <3>:                     PyConfig.           (line  293)
* PYTHONDONTWRITEBYTECODE:               Interpreter Changes<2>.
                                                             (line   16)
* PYTHONDONTWRITEBYTECODE <1>:           New and Improved Modules<2>.
                                                             (line  625)
* PYTHONDONTWRITEBYTECODE <2>:           Miscellaneous options.
                                                             (line   19)
* PYTHONDONTWRITEBYTECODE <3>:           sys --- 系統特定的參數與函式.
                                                             (line  335)
* PYTHONDONTWRITEBYTECODE <4>:           Global configuration variables.
                                                             (line   51)
* PYTHONDONTWRITEBYTECODE <5>:           PyConfig.           (line  948)
* PYTHONDONTWRITEBYTECODE <6>:           如何建立 pyc 檔案？.
                                                             (line   21)
* PYTHONDUMPREFS:                        Debug build uses the same ABI as release build.
                                                             (line   15)
* PYTHONDUMPREFS <1>:                    Build<45>.          (line   54)
* PYTHONDUMPREFS <2>:                    Debug options.      (line   22)
* PYTHONDUMPREFS <3>:                    Debug options.      (line   24)
* PYTHONDUMPREFS <4>:                    PyConfig.           (line  304)
* PYTHONDUMPREFSFILE:                    Core and Builtins<29>.
                                                             (line  154)
* PYTHONEXECUTABLE:                      PyConfig.           (line  699)
* PYTHONFAULTHANDLER:                    faulthandler<4>.    (line   11)
* PYTHONFAULTHANDLER <1>:                Miscellaneous options.
                                                             (line  255)
* PYTHONFAULTHANDLER <2>:                Python 開發模式的影響.
                                                             (line   52)
* PYTHONFAULTHANDLER <3>:                faulthandler --- 傾印 Python 回溯.
                                                             (line   15)
* PYTHONFAULTHANDLER <4>:                PyConfig.           (line  342)
* PythonFinalizationError:               實體例外.           (line  184)
* PYTHONHASHSEED:                        內建函式和型別.     (line   17)
* PYTHONHASHSEED <1>:                    移植 Python 程式碼. (line    6)
* PYTHONHASHSEED <2>:                    Core and Builtins<56>.
                                                             (line   30)
* PYTHONHASHSEED <3>:                    Miscellaneous options.
                                                             (line  118)
* PYTHONHASHSEED <4>:                    Miscellaneous options.
                                                             (line  134)
* PYTHONHASHSEED <5>:                    環境變數.           (line  155)
* PYTHONHASHSEED <6>:                    Basic customization.
                                                             (line  303)
* PYTHONHASHSEED <7>:                    Global configuration variables.
                                                             (line   76)
* PYTHONHASHSEED <8>:                    Global configuration variables.
                                                             (line   79)
* PYTHONHASHSEED <9>:                    PyConfig.           (line  412)
* PYTHONHOME:                            Deprecated C APIs.  (line   31)
* PYTHONHOME <1>:                        Pending Removal in Python 3 15<2>.
                                                             (line   41)
* PYTHONHOME <2>:                        Python 3 15 中待移除的項目<2>.
                                                             (line   40)
* PYTHONHOME <3>:                        Summary -- Release highlights<3>.
                                                             (line  107)
* PYTHONHOME <4>:                        Miscellaneous options.
                                                             (line   46)
* PYTHONHOME <5>:                        環境變數.           (line   19)
* PYTHONHOME <6>:                        環境變數.           (line   21)
* PYTHONHOME <7>:                        環境變數.           (line   38)
* PYTHONHOME <8>:                        找尋模組.           (line   29)
* PYTHONHOME <9>:                        找尋模組.           (line   47)
* PYTHONHOME <10>:                       找尋模組.           (line   81)
* PYTHONHOME <11>:                       test support script_helper --- 用於 Python 執行測試的工具.
                                                             (line   24)
* PYTHONHOME <12>:                       The initialization of the sys path module search path.
                                                             (line   30)
* PYTHONHOME <13>:                       Virtual environments.
                                                             (line   14)
* PYTHONHOME <14>:                       嵌入式Python.       (line   29)
* PYTHONHOME <15>:                       嵌入式Python.       (line   34)
* PYTHONHOME <16>:                       Global configuration variables.
                                                             (line   91)
* PYTHONHOME <17>:                       Process-wide parameters.
                                                             (line  292)
* PYTHONHOME <18>:                       Process-wide parameters.
                                                             (line  308)
* PYTHONHOME <19>:                       Process-wide parameters.
                                                             (line  317)
* PYTHONHOME <20>:                       PyConfig.           (line  420)
* PYTHONHOME <21>:                       PyConfig.           (line  422)
* PYTHONHOME <22>:                       Python 3 15 中待移除的項目<4>.
                                                             (line   40)
* Pythonic（Python 風格的）:             術語表.             (line 1051)
* PYTHONINSPECT:                         Other Changes and Fixes<2>.
                                                             (line   13)
* PYTHONINSPECT <1>:                     Miscellaneous options.
                                                             (line   58)
* PYTHONINSPECT <2>:                     Global configuration variables.
                                                             (line  108)
* PYTHONINSPECT <3>:                     PyConfig.           (line  447)
* PYTHONINTMAXSTRDIGITS:                 Core and Builtins<21>.
                                                             (line  106)
* PYTHONINTMAXSTRDIGITS <1>:             Miscellaneous options.
                                                             (line  277)
* PYTHONINTMAXSTRDIGITS <2>:             設定限制.           (line    9)
* PYTHONINTMAXSTRDIGITS <3>:             設定限制.           (line   16)
* PYTHONINTMAXSTRDIGITS <4>:             sys --- 系統特定的參數與函式.
                                                             (line 1122)
* PYTHONINTMAXSTRDIGITS <5>:             PyConfig.           (line  478)
* PYTHONIOENCODING:                      Other Improvements<2>.
                                                             (line   75)
* PYTHONIOENCODING <1>:                  Interpreter Changes<2>.
                                                             (line   23)
* PYTHONIOENCODING <2>:                  環境變數.           (line  401)
* PYTHONIOENCODING <3>:                  Python UTF-8 模式.  (line   29)
* PYTHONIOENCODING <4>:                  sys --- 系統特定的參數與函式.
                                                             (line 1799)
* PYTHONIOENCODING <5>:                  PyConfig.           (line  832)
* PYTHONLEGACYWINDOWSFSENCODING:         New Deprecations.   (line  107)
* PYTHONLEGACYWINDOWSFSENCODING <1>:     PEP 529 Change Windows filesystem encoding to UTF-8.
                                                             (line   18)
* PYTHONLEGACYWINDOWSFSENCODING <2>:     Windows<7>.         (line   37)
* PYTHONLEGACYWINDOWSFSENCODING <3>:     sys --- 系統特定的參數與函式.
                                                             (line 1739)
* PYTHONLEGACYWINDOWSFSENCODING <4>:     sys --- 系統特定的參數與函式.
                                                             (line 1750)
* PYTHONLEGACYWINDOWSFSENCODING <5>:     sys --- 系統特定的參數與函式.
                                                             (line 1756)
* PYTHONLEGACYWINDOWSFSENCODING <6>:     Global configuration variables.
                                                             (line  149)
* PYTHONLEGACYWINDOWSFSENCODING <7>:     PyPreConfig.        (line  124)
* PYTHONLEGACYWINDOWSSTDIO:              PEP 528 Change Windows console encoding to UTF-8.
                                                             (line   12)
* PYTHONLEGACYWINDOWSSTDIO <1>:          環境變數.           (line  190)
* PYTHONLEGACYWINDOWSSTDIO <2>:          sys --- 系統特定的參數與函式.
                                                             (line 1803)
* PYTHONLEGACYWINDOWSSTDIO <3>:          Global configuration variables.
                                                             (line  167)
* PYTHONLEGACYWINDOWSSTDIO <4>:          PyConfig.           (line  531)
* PYTHONMALLOC:                          PYTHONMALLOC environment variable.
                                                             (line    6)
* PYTHONMALLOC <1>:                      C API 中的改動<5>.  (line    9)
* PYTHONMALLOC <2>:                      Core and Builtins<76>.
                                                             (line   90)
* PYTHONMALLOC <3>:                      環境變數.           (line  328)
* PYTHONMALLOC <4>:                      Performance options.
                                                             (line  108)
* PYTHONMALLOC <5>:                      Performance options.
                                                             (line  115)
* PYTHONMALLOC <6>:                      Python 開發模式的影響.
                                                             (line   41)
* PYTHONMALLOC <7>:                      Python 開發模式的影響.
                                                             (line   44)
* PYTHONMALLOC <8>:                      總覽<2>.            (line   75)
* PYTHONMALLOC <9>:                      Default Memory Allocators.
                                                             (line   26)
* PYTHONMALLOC <10>:                     Debug hooks on the Python memory allocators.
                                                             (line   11)
* PYTHONMALLOC <11>:                     The pymalloc allocator.
                                                             (line   27)
* PYTHONMALLOCSTATS:                     Core and Builtins<76>.
                                                             (line   96)
* PYTHONMALLOCSTATS <1>:                 PyConfig.           (line  547)
* PYTHONMALLOCSTATS <2>:                 總覽<2>.            (line   78)
* PYTHONNODEBUGRANGES:                   PEP 657：回溯 traceback 中更細緻的錯誤位置.
                                                             (line   58)
* PYTHONNODEBUGRANGES <1>:               Miscellaneous options.
                                                             (line  322)
* PYTHONNODEBUGRANGES <2>:               用於程式碼物件的方法.
                                                             (line   40)
* PYTHONNODEBUGRANGES <3>:               PyConfig.           (line  246)
* PYTHONNOUSERSITE:                      PEP 370 Per-user site-packages Directory.
                                                             (line   30)
* PYTHONNOUSERSITE <1>:                  Miscellaneous options.
                                                             (line  146)
* PYTHONNOUSERSITE <2>:                  模組內容<10>.       (line   15)
* PYTHONNOUSERSITE <3>:                  Global configuration variables.
                                                             (line  201)
* PYTHONNOUSERSITE <4>:                  PyConfig.           (line  901)
* PYTHONOPTIMIZE:                        Miscellaneous options.
                                                             (line   78)
* PYTHONOPTIMIZE <1>:                    Global configuration variables.
                                                             (line  212)
* PYTHONOPTIMIZE <2>:                    PyConfig.           (line  614)
* PYTHONPATH:                            Changes in 'python' Command Behavior<2>.
                                                             (line    8)
* PYTHONPATH <1>:                        Changes in 'python' Command Behavior<2>.
                                                             (line    9)
* PYTHONPATH <2>:                        模組的搜尋路徑.     (line   13)
* PYTHONPATH <3>:                        標準模組.           (line   27)
* PYTHONPATH <4>:                        標準模組.           (line   27)
* PYTHONPATH <5>:                        Miscellaneous options.
                                                             (line   45)
* PYTHONPATH <6>:                        環境變數.           (line   32)
* PYTHONPATH <7>:                        環境變數.           (line   39)
* PYTHONPATH <8>:                        環境變數.           (line   42)
* PYTHONPATH <9>:                        Excursus Setting environment variables.
                                                             (line   38)
* PYTHONPATH <10>:                       找尋模組.           (line   15)
* PYTHONPATH <11>:                       找尋模組.           (line   38)
* PYTHONPATH <12>:                       找尋模組.           (line   81)
* PYTHONPATH <13>:                       設定.               (line    6)
* PYTHONPATH <14>:                       Path entry finders. (line    6)
* PYTHONPATH <15>:                       Path entry finders. (line   23)
* PYTHONPATH <16>:                       test support script_helper --- 用於 Python 執行測試的工具.
                                                             (line   25)
* PYTHONPATH <17>:                       sys --- 系統特定的參數與函式.
                                                             (line 1285)
* PYTHONPATH <18>:                       sys --- 系統特定的參數與函式.
                                                             (line 1290)
* PYTHONPATH <19>:                       The initialization of the sys path module search path.
                                                             (line   14)
* PYTHONPATH <20>:                       The initialization of the sys path module search path.
                                                             (line   18)
* PYTHONPATH <21>:                       建立 C 與 C++ 擴充套件.
                                                             (line    9)
* PYTHONPATH <22>:                       嵌入式Python.       (line   30)
* PYTHONPATH <23>:                       嵌入式Python.       (line   35)
* PYTHONPATH <24>:                       Global configuration variables.
                                                             (line   90)
* PYTHONPATH <25>:                       PyConfig.           (line  580)
* PYTHONPERFSUPPORT:                     其他語言更動.       (line   85)
* PYTHONPERFSUPPORT <1>:                 Miscellaneous options.
                                                             (line  342)
* PYTHONPERFSUPPORT <2>:                 如何啟用 perf 分析支援.
                                                             (line    6)
* PYTHONPLATLIBDIR:                      Core and Builtins<37>.
                                                             (line  274)
* PYTHONPLATLIBDIR <1>:                  The initialization of the sys path module search path.
                                                             (line   51)
* PYTHONPLATLIBDIR <2>:                  PyConfig.           (line  559)
* PYTHONPROFILEIMPORTTIME:               其他語言更動<6>.    (line   47)
* PYTHONPROFILEIMPORTTIME <1>:           Core and Builtins<58>.
                                                             (line   66)
* PYTHONPROFILEIMPORTTIME <2>:           Miscellaneous options.
                                                             (line  286)
* PYTHONPROFILEIMPORTTIME <3>:           PyConfig.           (line  432)
* PYTHONPYCACHEPREFIX:                   Parallel filesystem cache for compiled bytecode files.
                                                             (line    6)
* PYTHONPYCACHEPREFIX <1>:               Core and Builtins<49>.
                                                             (line  402)
* PYTHONPYCACHEPREFIX <2>:               Miscellaneous options.
                                                             (line  306)
* PYTHONPYCACHEPREFIX <3>:               sys --- 系統特定的參數與函式.
                                                             (line  381)
* PYTHONPYCACHEPREFIX <4>:               PyConfig.           (line  721)
* PYTHONREGRTEST_UNICODE_GUARD:          Tests<19>.          (line   13)
* PYTHONSAFEPATH:                        發布重點摘要<2>.    (line   27)
* PYTHONSAFEPATH <1>:                    其他語言更動<2>.    (line   35)
* PYTHONSAFEPATH <2>:                    Security<15>.       (line    6)
* PYTHONSAFEPATH <3>:                    Miscellaneous options.
                                                             (line  104)
* PYTHONSAFEPATH <4>:                    sys --- 系統特定的參數與函式.
                                                             (line 1302)
* PYTHONSAFEPATH <5>:                    安全性注意事項<4>.  (line   41)
* PYTHONSAFEPATH <6>:                    PyConfig.           (line  163)
* PYTHONSTARTUP:                         sys<11>.            (line   17)
* PYTHONSTARTUP <1>:                     sys<11>.            (line   21)
* PYTHONSTARTUP <2>:                     IDLE<35>.           (line  176)
* PYTHONSTARTUP <3>:                     IDLE<39>.           (line    9)
* PYTHONSTARTUP <4>:                     IDLE<45>.           (line    9)
* PYTHONSTARTUP <5>:                     互動式啟動檔案.     (line    7)
* PYTHONSTARTUP <6>:                     Miscellaneous options.
                                                             (line   55)
* PYTHONSTARTUP <7>:                     環境變數.           (line  116)
* PYTHONSTARTUP <8>:                     範例.               (line   10)
* PYTHONSTARTUP <9>:                     asyncio --- 非同步 I/O.
                                                             (line   77)
* PYTHONSTARTUP <10>:                    Startup and Code Execution.
                                                             (line    7)
* PYTHONSTARTUP <11>:                    sys --- 系統特定的參數與函式.
                                                             (line 1135)
* PYTHONSTARTUP <12>:                    Readline configuration.
                                                             (line   12)
* PYTHONTRACEMALLOC:                     Miscellaneous options.
                                                             (line  272)
* PYTHONTRACEMALLOC <1>:                 tracemalloc --- 追蹤記憶體配置.
                                                             (line   25)
* PYTHONTRACEMALLOC <2>:                 tracemalloc --- 追蹤記憶體配置.
                                                             (line   32)
* PYTHONTRACEMALLOC <3>:                 函式<10>.           (line   90)
* PYTHONTRACEMALLOC <4>:                 PyConfig.           (line  860)
* PYTHONTZPATH:                          Exceptions and warnings.
                                                             (line   14)
* PYTHONUNBUFFERED:                      Core and Builtins<42>.
                                                             (line  107)
* PYTHONUNBUFFERED <1>:                  Miscellaneous options.
                                                             (line  166)
* PYTHONUNBUFFERED <2>:                  sys --- 系統特定的參數與函式.
                                                             (line 1810)
* PYTHONUNBUFFERED <3>:                  Global configuration variables.
                                                             (line  239)
* PYTHONUNBUFFERED <4>:                  PyConfig.           (line  210)
* PYTHONUOPS:                            Core and Builtins<13>.
                                                             (line   27)
* PYTHONUOPS <1>:                        Core and Builtins<13>.
                                                             (line  179)
* PYTHONUOPS <2>:                        Core and Builtins<13>.
                                                             (line  258)
* PYTHONUOPS <3>:                        Core and Builtins<13>.
                                                             (line  317)
* PYTHONUOPS <4>:                        Core and Builtins<13>.
                                                             (line  382)
* PYTHONUSERBASE:                        PEP 370 Per-user site-packages Directory.
                                                             (line   23)
* PYTHONUSERBASE <1>:                    模組內容<10>.       (line   40)
* PYTHONUSERBASE <2>:                    模組內容<10>.       (line   67)
* PYTHONUSERSITE:                        test support script_helper --- 用於 Python 執行測試的工具.
                                                             (line   25)
* PYTHONUTF8:                            PEP 540 Forced UTF-8 Runtime Mode.
                                                             (line    6)
* PYTHONUTF8 <1>:                        Miscellaneous options.
                                                             (line  300)
* PYTHONUTF8 <2>:                        環境變數.           (line  411)
* PYTHONUTF8 <3>:                        UTF-8 模式.         (line   18)
* PYTHONUTF8 <4>:                        Python UTF-8 模式.  (line   52)
* PYTHONUTF8 <5>:                        Python UTF-8 模式.  (line   54)
* PYTHONUTF8 <6>:                        sys --- 系統特定的參數與函式.
                                                             (line 1801)
* PYTHONUTF8 <7>:                        PyPreConfig.        (line  153)
* PYTHONUTF8 <8>:                        Python Configuration.
                                                             (line   14)
* PYTHONVERBOSE:                         Miscellaneous options.
                                                             (line  182)
* PYTHONVERBOSE <1>:                     Global configuration variables.
                                                             (line  256)
* PYTHONVERBOSE <2>:                     PyConfig.           (line  918)
* PYTHONWARNDEFAULTENCODING:             可選的 EncodingWarning 和 encoding="locale" 選項.
                                                             (line   18)
* PYTHONWARNDEFAULTENCODING <1>:         Library<30>.        (line   45)
* PYTHONWARNDEFAULTENCODING <2>:         Miscellaneous options.
                                                             (line  312)
* PYTHONWARNDEFAULTENCODING <3>:         選擇性加入的編碼警告.
                                                             (line    9)
* PYTHONWARNINGS:                        warnings<3>.        (line   21)
* PYTHONWARNINGS <1>:                    其他語言更動<11>.   (line  160)
* PYTHONWARNINGS <2>:                    Changes to the Handling of Deprecation Warnings.
                                                             (line   25)
* PYTHONWARNINGS <3>:                    Interpreter Changes.
                                                             (line    6)
* PYTHONWARNINGS <4>:                    Documentation<15>.  (line   67)
* PYTHONWARNINGS <5>:                    Miscellaneous options.
                                                             (line  236)
* PYTHONWARNINGS <6>:                    Python 開發模式的影響.
                                                             (line   26)
* PYTHONWARNINGS <7>:                    The Warnings Filter.
                                                             (line   46)
* PYTHONWARNINGS <8>:                    The Warnings Filter.
                                                             (line   56)
* PYTHONWARNINGS <9>:                    Describing Warning Filters.
                                                             (line    7)
* PYTHONWARNINGS <10>:                   Describing Warning Filters.
                                                             (line   21)
* PYTHONWARNINGS <11>:                   Default Warning Filter.
                                                             (line    7)
* PYTHONWARNINGS <12>:                   PyConfig.           (line  937)
* PyThread_create_key (C function):      執行緒局部儲存 Thread Local Storage TLS API：.
                                                             (line   18)
* PyThread_delete_key (C function):      執行緒局部儲存 Thread Local Storage TLS API：.
                                                             (line   21)
* PyThread_delete_key_value (C function): 執行緒局部儲存 Thread Local Storage TLS API：.
                                                             (line   30)
* PyThread_get_key_value (C function):   執行緒局部儲存 Thread Local Storage TLS API：.
                                                             (line   27)
* PyThread_ReInitTLS (C function):       執行緒局部儲存 Thread Local Storage TLS API：.
                                                             (line   33)
* PyThread_set_key_value (C function):   執行緒局部儲存 Thread Local Storage TLS API：.
                                                             (line   24)
* PyThread_tss_alloc (C function):       Dynamic Allocation. (line   11)
* PyThread_tss_create (C function):      方法.               (line   16)
* PyThread_tss_delete (C function):      方法.               (line   24)
* PyThread_tss_free (C function):        Dynamic Allocation. (line   17)
* PyThread_tss_get (C function):         方法.               (line   39)
* PyThread_tss_is_created (C function):  方法.               (line   11)
* PyThread_tss_set (C function):         方法.               (line   33)
* PyThreadState (C type):                高階 API.           (line   21)
* PyThreadState_Clear (C function):      低階 API.           (line   41)
* PyThreadState_Delete (C function):     低階 API.           (line   49)
* PyThreadState_DeleteCurrent (C function): 低階 API.        (line   55)
* PyThreadState_EnterTracing (C function): 低階 API.         (line   93)
* PyThreadState_Get (C function):        高階 API.           (line   69)
* PyThreadState_GetDict (C function):    低階 API.           (line  180)
* PyThreadState_GetFrame (C function):   低階 API.           (line   62)
* PyThreadState_GetID (C function):      低階 API.           (line   76)
* PyThreadState_GetInterpreter (C function): 低階 API.       (line   84)
* PyThreadState_GetUnchecked (C function): 高階 API.         (line   77)
* PyThreadState_LeaveTracing (C function): 低階 API.         (line  102)
* PyThreadState_New (C function):        低階 API.           (line   34)
* PyThreadState_Next (C function):       Advanced Debugger Support.
                                                             (line   30)
* PyThreadState_SetAsyncExc (C function): 低階 API.          (line  189)
* PyThreadState_Swap (C function):       高階 API.           (line   86)
* PyThreadState.interp (C member):       高階 API.           (line   26)
* PyThreadState（C 型別）:               Thread State and the Global Interpreter Lock.
                                                             (line   23)
* PyTime_AsSecondsDouble (C function):   Conversion functions.
                                                             (line    6)
* PyTime_Check (C function):             DateTime 物件.      (line   95)
* PyTime_CheckExact (C function):        DateTime 物件.      (line  101)
* PyTime_FromTime (C function):          DateTime 物件.      (line  149)
* PyTime_FromTimeAndFold (C function):   DateTime 物件.      (line  154)
* PyTime_MAX (C var):                    Types.              (line   24)
* PyTime_MIN (C var):                    Types.              (line   20)
* PyTime_Monotonic (C function):         Clock Functions.    (line   21)
* PyTime_MonotonicRaw (C function):      Raw Clock Functions.
                                                             (line   16)
* PyTime_PerfCounter (C function):       Clock Functions.    (line   26)
* PyTime_PerfCounterRaw (C function):    Raw Clock Functions.
                                                             (line   21)
* PyTime_t (C type):                     Types.              (line    6)
* PyTime_Time (C function):              Clock Functions.    (line   31)
* PyTime_TimeRaw (C function):           Raw Clock Functions.
                                                             (line   26)
* PyTimeZone_FromOffset (C function):    DateTime 物件.      (line  167)
* PyTimeZone_FromOffsetAndName (C function): DateTime 物件.  (line  174)
* PyTrace_C_CALL (C var):                Profiling and Tracing.
                                                             (line   94)
* PyTrace_C_EXCEPTION (C var):           Profiling and Tracing.
                                                             (line   99)
* PyTrace_C_RETURN (C var):              Profiling and Tracing.
                                                             (line  104)
* PyTrace_CALL (C var):                  Profiling and Tracing.
                                                             (line   62)
* PyTrace_EXCEPTION (C var):             Profiling and Tracing.
                                                             (line   70)
* PyTrace_LINE (C var):                  Profiling and Tracing.
                                                             (line   82)
* PyTrace_OPCODE (C var):                Profiling and Tracing.
                                                             (line  109)
* PyTrace_RETURN (C var):                Profiling and Tracing.
                                                             (line   89)
* PyTraceMalloc_Track (C function):      tracemalloc C API.  (line    8)
* PyTraceMalloc_Untrack (C function):    tracemalloc C API.  (line   20)
* PyTuple_Check (C function):            Tuple（元組）物件.  (line   16)
* PyTuple_CheckExact (C function):       Tuple（元組）物件.  (line   21)
* PyTuple_GET_ITEM (C function):         Tuple（元組）物件.  (line   60)
* PyTuple_GET_SIZE (C function):         Tuple（元組）物件.  (line   43)
* PyTuple_GetItem (C function):          Tuple（元組）物件.  (line   47)
* PyTuple_GetSlice (C function):         Tuple（元組）物件.  (line   65)
* PyTuple_New (C function):              Tuple（元組）物件.  (line   26)
* PyTuple_Pack (C function):             Tuple（元組）物件.  (line   31)
* PyTuple_SET_ITEM (C function):         Tuple（元組）物件.  (line   85)
* PyTuple_SetItem (C function):          Tuple（元組）物件.  (line   74)
* PyTuple_SetItem（C 函式）:             參照計數詳細資訊.   (line   19)
* PyTuple_Size (C function):             Tuple（元組）物件.  (line   38)
* PyTuple_Type (C var):                  Tuple（元組）物件.  (line   11)
* PyTupleObject (C type):                Tuple（元組）物件.  (line    6)
* PyType_AddWatcher (C function):        型別物件.           (line   67)
* PyType_Check (C function):             型別物件.           (line   16)
* PyType_CheckExact (C function):        型別物件.           (line   22)
* PyType_ClearCache (C function):        型別物件.           (line   28)
* PyType_ClearWatcher (C function):      型別物件.           (line   76)
* PyType_FromMetaclass (C function):     Creating Heap-Allocated Types.
                                                             (line    9)
* PyType_FromModuleAndSpec (C function): Creating Heap-Allocated Types.
                                                             (line   59)
* PyType_FromSpec (C function):          Creating Heap-Allocated Types.
                                                             (line   94)
* PyType_FromSpecWithBases (C function): Creating Heap-Allocated Types.
                                                             (line   78)
* PyType_GenericAlloc (C function):      型別物件.           (line  134)
* PyType_GenericNew (C function):        型別物件.           (line  141)
* PyType_GetDict (C function):           型別物件.           (line   44)
* PyType_GetFlags (C function):          型別物件.           (line   32)
* PyType_GetFullyQualifiedName (C function): 型別物件.       (line  178)
* PyType_GetModule (C function):         型別物件.           (line  211)
* PyType_GetModuleByDef (C function):    型別物件.           (line  244)
* PyType_GetModuleName (C function):     型別物件.           (line  187)
* PyType_GetModuleState (C function):    型別物件.           (line  230)
* PyType_GetName (C function):           型別物件.           (line  163)
* PyType_GetQualName (C function):       型別物件.           (line  170)
* PyType_GetSlot (C function):           型別物件.           (line  195)
* PyType_GetTypeDataSize (C function):   物件協定.           (line  527)
* PyType_HasFeature (C function):        型別物件.           (line  115)
* PyType_IS_GC (C function):             型別物件.           (line  120)
* PyType_IsSubtype (C function):         型別物件.           (line  125)
* PyType_Modified (C function):          型別物件.           (line   61)
* PyType_Ready (C function):             型別物件.           (line  147)
* PyType_Slot (C type):                  Creating Heap-Allocated Types.
                                                             (line  172)
* PyType_Slot.pfunc (C member):          Creating Heap-Allocated Types.
                                                             (line  238)
* PyType_Slot.slot (C member):           Creating Heap-Allocated Types.
                                                             (line  177)
* PyType_Spec (C type):                  Creating Heap-Allocated Types.
                                                             (line  107)
* PyType_Spec.basicsize (C member):      Creating Heap-Allocated Types.
                                                             (line  116)
* PyType_Spec.flags (C member):          Creating Heap-Allocated Types.
                                                             (line  158)
* PyType_Spec.itemsize (C member):       Creating Heap-Allocated Types.
                                                             (line  132)
* PyType_Spec.name (C member):           Creating Heap-Allocated Types.
                                                             (line  111)
* PyType_Spec.slots (C member):          Creating Heap-Allocated Types.
                                                             (line  165)
* PyType_Type (C var):                   型別物件.           (line   11)
* PyType_Watch (C function):             型別物件.           (line   88)
* PyType_WatchCallback (C type):         型別物件.           (line  104)
* PyTypeObject (C type):                 型別物件.           (line    6)
* PyTypeObject.tp_alloc (C member):      PyTypeObject Slots. (line 1371)
* PyTypeObject.tp_as_async (C member):   PyTypeObject Slots. (line  237)
* PyTypeObject.tp_as_buffer (C member):  PyTypeObject Slots. (line  447)
* PyTypeObject.tp_as_mapping (C member): PyTypeObject Slots. (line  302)
* PyTypeObject.tp_as_number (C member):  PyTypeObject Slots. (line  278)
* PyTypeObject.tp_as_sequence (C member): PyTypeObject Slots.
                                                             (line  290)
* PyTypeObject.tp_base (C member):       PyTypeObject Slots. (line 1193)
* PyTypeObject.tp_bases (C member):      PyTypeObject Slots. (line 1486)
* PyTypeObject.tp_basicsize (C member):  PyTypeObject Slots. (line   47)
* PyTypeObject.tp_cache (C member):      PyTypeObject Slots. (line 1520)
* PyTypeObject.tp_call (C member):       PyTypeObject Slots. (line  355)
* PyTypeObject.tp_clear (C member):      PyTypeObject Slots. (line  911)
* PyTypeObject.tp_dealloc (C member):    PyTypeObject Slots. (line  101)
* PyTypeObject.tp_del (C member):        PyTypeObject Slots. (line 1560)
* PyTypeObject.tp_descr_get (C member):  PyTypeObject Slots. (line 1262)
* PyTypeObject.tp_descr_set (C member):  PyTypeObject Slots. (line 1275)
* PyTypeObject.tp_dict (C member):       PyTypeObject Slots. (line 1226)
* PyTypeObject.tp_dictoffset (C member): PyTypeObject Slots. (line 1291)
* PyTypeObject.tp_doc (C member):        PyTypeObject Slots. (line  808)
* PyTypeObject.tp_finalize (C member):   PyTypeObject Slots. (line 1572)
* PyTypeObject.tp_flags (C member):      PyTypeObject Slots. (line  459)
* PyTypeObject.tp_free (C member):       PyTypeObject Slots. (line 1433)
* PyTypeObject.tp_getattr (C member):    PyTypeObject Slots. (line  196)
* PyTypeObject.tp_getattro (C member):   PyTypeObject Slots. (line  393)
* PyTypeObject.tp_getset (C member):     PyTypeObject Slots. (line 1177)
* PyTypeObject.tp_hash (C member):       PyTypeObject Slots. (line  314)
* PyTypeObject.tp_init (C member):       PyTypeObject Slots. (line 1335)
* PyTypeObject.tp_is_gc (C member):      PyTypeObject Slots. (line 1457)
* PyTypeObject.tp_itemsize (C member):   PyTypeObject Slots. (line   47)
* PyTypeObject.tp_iter (C member):       PyTypeObject Slots. (line 1106)
* PyTypeObject.tp_iternext (C member):   PyTypeObject Slots. (line 1122)
* PyTypeObject.tp_members (C member):    PyTypeObject Slots. (line 1161)
* PyTypeObject.tp_methods (C member):    PyTypeObject Slots. (line 1145)
* PyTypeObject.tp_mro (C member):        PyTypeObject Slots. (line 1506)
* PyTypeObject.tp_name (C member):       PyTypeObject Slots. (line   12)
* PyTypeObject.tp_new (C member):        PyTypeObject Slots. (line 1394)
* PyTypeObject.tp_repr (C member):       PyTypeObject Slots. (line  252)
* PyTypeObject.tp_richcompare (C member): PyTypeObject Slots.
                                                             (line  993)
* PyTypeObject.tp_setattr (C member):    PyTypeObject Slots. (line  216)
* PyTypeObject.tp_setattro (C member):   PyTypeObject Slots. (line  419)
* PyTypeObject.tp_str (C member):        PyTypeObject Slots. (line  367)
* PyTypeObject.tp_subclasses (C member): PyTypeObject Slots. (line 1528)
* PyTypeObject.tp_traverse (C member):   PyTypeObject Slots. (line  818)
* PyTypeObject.tp_vectorcall (C member): PyTypeObject Slots. (line 1632)
* PyTypeObject.tp_vectorcall_offset (C member): PyTypeObject Slots.
                                                             (line  156)
* PyTypeObject.tp_version_tag (C member): PyTypeObject Slots.
                                                             (line 1564)
* PyTypeObject.tp_watched (C member):    PyTypeObject Slots. (line 1648)
* PyTypeObject.tp_weaklist (C member):   PyTypeObject Slots. (line 1544)
* PyTypeObject.tp_weaklistoffset (C member): PyTypeObject Slots.
                                                             (line 1070)
* PyTZInfo_Check (C function):           DateTime 物件.      (line  117)
* PyTZInfo_CheckExact (C function):      DateTime 物件.      (line  123)
* PyUnicode_1BYTE_DATA (C function):     Unicode Type.       (line   76)
* PyUnicode_1BYTE_KIND (C macro):        Unicode Type.       (line   91)
* PyUnicode_2BYTE_DATA (C function):     Unicode Type.       (line   76)
* PyUnicode_2BYTE_KIND (C macro):        Unicode Type.       (line   91)
* PyUnicode_4BYTE_DATA (C function):     Unicode Type.       (line   76)
* PyUnicode_4BYTE_KIND (C macro):        Unicode Type.       (line   91)
* PyUnicode_AsASCIIString (C function):  ASCII 編解碼器.     (line   15)
* PyUnicode_AsCharmapString (C function): Character Map Codecs.
                                                             (line   31)
* PyUnicode_AsEncodedString (C function): Generic Codecs.    (line   17)
* PyUnicode_AsLatin1String (C function): Latin-1 編解碼器.   (line   17)
* PyUnicode_AsMBCSString (C function):   MBCS codecs for Windows.
                                                             (line   29)
* PyUnicode_AsRawUnicodeEscapeString (C function): Raw-Unicode-Escape Codecs.
                                                             (line   15)
* PyUnicode_AsUCS4 (C function):         Creating and accessing Unicode strings.
                                                             (line  346)
* PyUnicode_AsUCS4Copy (C function):     Creating and accessing Unicode strings.
                                                             (line  356)
* PyUnicode_AsUnicodeEscapeString (C function): Unicode-Escape Codecs.
                                                             (line   15)
* PyUnicode_AsUTF16String (C function):  UTF-16 編解碼器.    (line   48)
* PyUnicode_AsUTF32String (C function):  UTF-32 編解碼器.    (line   47)
* PyUnicode_AsUTF8 (C function):         UTF-8 編解碼器.     (line   58)
* PyUnicode_AsUTF8AndSize (C function):  UTF-8 編解碼器.     (line   31)
* PyUnicode_AsUTF8String (C function):   UTF-8 編解碼器.     (line   24)
* PyUnicode_AsWideChar (C function):     wchar_t 支援.       (line   16)
* PyUnicode_AsWideCharString (C function): wchar_t 支援.     (line   34)
* PyUnicode_Check (C function):          Unicode Type.       (line   49)
* PyUnicode_CheckExact (C function):     Unicode Type.       (line   54)
* PyUnicode_Compare (C function):        Methods and Slot Functions.
                                                             (line   87)
* PyUnicode_CompareWithASCIIString (C function): Methods and Slot Functions.
                                                             (line  117)
* PyUnicode_Concat (C function):         Methods and Slot Functions.
                                                             (line   12)
* PyUnicode_Contains (C function):       Methods and Slot Functions.
                                                             (line  150)
* PyUnicode_CopyCharacters (C function): Creating and accessing Unicode strings.
                                                             (line  288)
* PyUnicode_Count (C function):          Methods and Slot Functions.
                                                             (line   74)
* PyUnicode_DATA (C function):           Unicode Type.       (line  110)
* PyUnicode_Decode (C function):         Generic Codecs.     (line    8)
* PyUnicode_DecodeASCII (C function):    ASCII 編解碼器.     (line    9)
* PyUnicode_DecodeCharmap (C function):  Character Map Codecs.
                                                             (line   15)
* PyUnicode_DecodeFSDefault (C function): File System Encoding.
                                                             (line   58)
* PyUnicode_DecodeFSDefaultAndSize (C function): File System Encoding.
                                                             (line   42)
* PyUnicode_DecodeLatin1 (C function):   Latin-1 編解碼器.   (line   10)
* PyUnicode_DecodeLocale (C function):   Locale Encoding.    (line   37)
* PyUnicode_DecodeLocaleAndSize (C function): Locale Encoding.
                                                             (line    9)
* PyUnicode_DecodeMBCS (C function):     MBCS codecs for Windows.
                                                             (line   12)
* PyUnicode_DecodeMBCSStateful (C function): MBCS codecs for Windows.
                                                             (line   19)
* PyUnicode_DecodeRawUnicodeEscape (C function): Raw-Unicode-Escape Codecs.
                                                             (line    8)
* PyUnicode_DecodeUnicodeEscape (C function): Unicode-Escape Codecs.
                                                             (line    8)
* PyUnicode_DecodeUTF16 (C function):    UTF-16 編解碼器.    (line    8)
* PyUnicode_DecodeUTF16Stateful (C function): UTF-16 編解碼器.
                                                             (line   36)
* PyUnicode_DecodeUTF32 (C function):    UTF-32 編解碼器.    (line    8)
* PyUnicode_DecodeUTF32Stateful (C function): UTF-32 編解碼器.
                                                             (line   35)
* PyUnicode_DecodeUTF7 (C function):     UTF-7 編解碼器.     (line    8)
* PyUnicode_DecodeUTF7Stateful (C function): UTF-7 編解碼器. (line   14)
* PyUnicode_DecodeUTF8 (C function):     UTF-8 編解碼器.     (line    8)
* PyUnicode_DecodeUTF8Stateful (C function): UTF-8 編解碼器. (line   14)
* PyUnicode_EncodeCodePage (C function): MBCS codecs for Windows.
                                                             (line   36)
* PyUnicode_EncodeFSDefault (C function): File System Encoding.
                                                             (line   70)
* PyUnicode_EncodeLocale (C function):   Locale Encoding.    (line   45)
* PyUnicode_EqualToUTF8 (C function):    Methods and Slot Functions.
                                                             (line  108)
* PyUnicode_EqualToUTF8AndSize (C function): Methods and Slot Functions.
                                                             (line   95)
* PyUnicode_Fill (C function):           Creating and accessing Unicode strings.
                                                             (line  299)
* PyUnicode_Find (C function):           Methods and Slot Functions.
                                                             (line   47)
* PyUnicode_FindChar (C function):       Methods and Slot Functions.
                                                             (line   58)
* PyUnicode_Format (C function):         Methods and Slot Functions.
                                                             (line  144)
* PyUnicode_FromEncodedObject (C function): Creating and accessing Unicode strings.
                                                             (line  264)
* PyUnicode_FromFormat (C function):     Creating and accessing Unicode strings.
                                                             (line   59)
* PyUnicode_FromFormatV (C function):    Creating and accessing Unicode strings.
                                                             (line  249)
* PyUnicode_FromKindAndData (C function): Creating and accessing Unicode strings.
                                                             (line   21)
* PyUnicode_FromObject (C function):     Creating and accessing Unicode strings.
                                                             (line  255)
* PyUnicode_FromString (C function):     Creating and accessing Unicode strings.
                                                             (line   54)
* PyUnicode_FromStringAndSize (C function): Creating and accessing Unicode strings.
                                                             (line   37)
* PyUnicode_FromWideChar (C function):   wchar_t 支援.       (line    8)
* PyUnicode_FSConverter (C function):    File System Encoding.
                                                             (line   13)
* PyUnicode_FSDecoder (C function):      File System Encoding.
                                                             (line   29)
* PyUnicode_GET_LENGTH (C function):     Unicode Type.       (line   67)
* PyUnicode_GetLength (C function):      Creating and accessing Unicode strings.
                                                             (line  281)
* PyUnicode_InternFromString (C function): Methods and Slot Functions.
                                                             (line  183)
* PyUnicode_InternInPlace (C function):  Methods and Slot Functions.
                                                             (line  157)
* PyUnicode_IsIdentifier (C function):   Unicode Type.       (line  159)
* PyUnicode_Join (C function):           Methods and Slot Functions.
                                                             (line   33)
* PyUnicode_KIND (C function):           Unicode Type.       (line  101)
* PyUnicode_MAX_CHAR_VALUE (C function): Unicode Type.       (line  149)
* PyUnicode_New (C function):            Creating and accessing Unicode strings.
                                                             (line    9)
* PyUnicode_READ (C function):           Unicode Type.       (line  131)
* PyUnicode_READ_CHAR (C function):      Unicode Type.       (line  140)
* PyUnicode_ReadChar (C function):       Creating and accessing Unicode strings.
                                                             (line  327)
* PyUnicode_READY (C function):          Unicode Type.       (line   59)
* PyUnicode_Replace (C function):        Methods and Slot Functions.
                                                             (line   80)
* PyUnicode_RichCompare (C function):    Methods and Slot Functions.
                                                             (line  127)
* PyUnicode_Split (C function):          Methods and Slot Functions.
                                                             (line   17)
* PyUnicode_Splitlines (C function):     Methods and Slot Functions.
                                                             (line   26)
* PyUnicode_Substring (C function):      Creating and accessing Unicode strings.
                                                             (line  337)
* PyUnicode_Tailmatch (C function):      Methods and Slot Functions.
                                                             (line   39)
* PyUnicode_Translate (C function):      Character Map Codecs.
                                                             (line   46)
* PyUnicode_Type (C var):                Unicode Type.       (line   41)
* PyUnicode_WRITE (C function):          Unicode Type.       (line  118)
* PyUnicode_WriteChar (C function):      Creating and accessing Unicode strings.
                                                             (line  313)
* PyUnicodeDecodeError_Create (C function): Unicode Exception Objects.
                                                             (line    9)
* PyUnicodeDecodeError_GetEncoding (C function): Unicode Exception Objects.
                                                             (line   17)
* PyUnicodeDecodeError_GetEnd (C function): Unicode Exception Objects.
                                                             (line   53)
* PyUnicodeDecodeError_GetObject (C function): Unicode Exception Objects.
                                                             (line   24)
* PyUnicodeDecodeError_GetReason (C function): Unicode Exception Objects.
                                                             (line   73)
* PyUnicodeDecodeError_GetStart (C function): Unicode Exception Objects.
                                                             (line   33)
* PyUnicodeDecodeError_SetEnd (C function): Unicode Exception Objects.
                                                             (line   63)
* PyUnicodeDecodeError_SetReason (C function): Unicode Exception Objects.
                                                             (line   82)
* PyUnicodeDecodeError_SetStart (C function): Unicode Exception Objects.
                                                             (line   43)
* PyUnicodeEncodeError_GetEncoding (C function): Unicode Exception Objects.
                                                             (line   17)
* PyUnicodeEncodeError_GetEnd (C function): Unicode Exception Objects.
                                                             (line   53)
* PyUnicodeEncodeError_GetObject (C function): Unicode Exception Objects.
                                                             (line   24)
* PyUnicodeEncodeError_GetReason (C function): Unicode Exception Objects.
                                                             (line   73)
* PyUnicodeEncodeError_GetStart (C function): Unicode Exception Objects.
                                                             (line   33)
* PyUnicodeEncodeError_SetEnd (C function): Unicode Exception Objects.
                                                             (line   63)
* PyUnicodeEncodeError_SetReason (C function): Unicode Exception Objects.
                                                             (line   82)
* PyUnicodeEncodeError_SetStart (C function): Unicode Exception Objects.
                                                             (line   43)
* PyUnicodeObject (C type):              Unicode Type.       (line   30)
* PyUnicodeTranslateError_GetEnd (C function): Unicode Exception Objects.
                                                             (line   53)
* PyUnicodeTranslateError_GetObject (C function): Unicode Exception Objects.
                                                             (line   24)
* PyUnicodeTranslateError_GetReason (C function): Unicode Exception Objects.
                                                             (line   73)
* PyUnicodeTranslateError_GetStart (C function): Unicode Exception Objects.
                                                             (line   33)
* PyUnicodeTranslateError_SetEnd (C function): Unicode Exception Objects.
                                                             (line   63)
* PyUnicodeTranslateError_SetReason (C function): Unicode Exception Objects.
                                                             (line   82)
* PyUnicodeTranslateError_SetStart (C function): Unicode Exception Objects.
                                                             (line   43)
* PyUnstable:                            不穩定的 C API.     (line    6)
* PyUnstable_Code_GetExtra (C function): Extra information.  (line   35)
* PyUnstable_Code_GetFirstFree (C function): 程式碼物件.     (line   29)
* PyUnstable_Code_New (C function):      程式碼物件.         (line   38)
* PyUnstable_Code_NewWithPosOnlyArgs (C function): 程式碼物件.
                                                             (line   64)
* PyUnstable_Code_SetExtra (C function): Extra information.  (line   51)
* PyUnstable_Eval_RequestCodeExtraIndex (C function): Extra information.
                                                             (line   14)
* PyUnstable_Exc_PrepReraiseStar (C function): 例外物件.     (line   55)
* PyUnstable_GC_VisitObjects (C function): Querying Garbage Collector State.
                                                             (line    9)
* PyUnstable_InterpreterFrame_GetCode (C function): Internal Frames.
                                                             (line   14)
* PyUnstable_InterpreterFrame_GetLasti (C function): Internal Frames.
                                                             (line   23)
* PyUnstable_InterpreterFrame_GetLine (C function): Internal Frames.
                                                             (line   31)
* PyUnstable_Long_CompactValue (C function): 整數物件.       (line  513)
* PyUnstable_Long_IsCompact (C function): 整數物件.          (line  497)
* PyUnstable_Module_SetGIL (C function): 支援的函式.         (line  156)
* PyUnstable_Object_ClearWeakRefsNoCallbacks (C function): 弱參照物件<2>.
                                                             (line   96)
* PyUnstable_Object_GC_NewWithExtraData (C function): 循環垃圾回收的支援.
                                                             (line   66)
* PyUnstable_PerfMapState_Fini (C function): 對 Perf Map 的支援.
                                                             (line   42)
* PyUnstable_PerfMapState_Init (C function): 對 Perf Map 的支援.
                                                             (line   16)
* PyUnstable_Type_AssignVersionTag (C function): 型別物件.   (line  261)
* PyUnstable_WritePerfMapEntry (C function): 對 Perf Map 的支援.
                                                             (line   28)
* PyVarObject (C type):                  Base object types and macros.
                                                             (line   26)
* PyVarObject_HEAD_INIT (C macro):       Base object types and macros.
                                                             (line  128)
* PyVarObject.ob_size (C member):        PyVarObject Slots.  (line    6)
* PyVectorcall_Call (C function):        Vectorcall 支援 API.
                                                             (line   28)
* PyVectorcall_Function (C function):    Vectorcall 支援 API.
                                                             (line   16)
* PyVectorcall_NARGS (C function):       Vectorcall 支援 API.
                                                             (line    6)
* PyWeakref_Check (C function):          弱參照物件<2>.      (line   11)
* PyWeakref_CheckProxy (C function):     弱參照物件<2>.      (line   21)
* PyWeakref_CheckRef (C function):       弱參照物件<2>.      (line   16)
* PyWeakref_GET_OBJECT (C function):     弱參照物件<2>.      (line   81)
* PyWeakref_GetObject (C function):      弱參照物件<2>.      (line   66)
* PyWeakref_GetRef (C function):         弱參照物件<2>.      (line   52)
* PyWeakref_NewProxy (C function):       弱參照物件<2>.      (line   39)
* PyWeakref_NewRef (C function):         弱參照物件<2>.      (line   26)
* PyWideStringList (C type):             PyWideStringList.   (line    6)
* PyWideStringList_Append (C function):  PyWideStringList.   (line   15)
* PyWideStringList_Insert (C function):  PyWideStringList.   (line   22)
* PyWideStringList.items (C member):     PyWideStringList.   (line   41)
* PyWideStringList.length (C member):    PyWideStringList.   (line   37)
* PyWrapper_New (C function):            Descriptor（描述器）物件.
                                                             (line   39)
* PyZipFile (zipfile 中的類別):          PyZipFile 物件.     (line   10)
* qiflush() (於 curses 模組中):          函式<5>.            (line  398)
* QName (xml.etree.ElementTree 中的類別): QName 物件.        (line    6)
* qsize() (asyncio.Queue 的方法):        Queue.              (line   74)
* qsize() (multiprocessing.Queue 的方法): Pipes and Queues.  (line  106)
* qsize() (queue.Queue 的方法):          佇列物件.           (line    9)
* qsize() (queue.SimpleQueue 的方法):    SimpleQueue 物件.   (line    8)
* qualified name（限定名稱）:            術語表.             (line 1068)
* quantiles() (statistics.NormalDist 的方法): NormalDist 物件.
                                                             (line   93)
* quantiles() (於 statistics 模組中):    函式細節.           (line  457)
* quantize() (decimal.Context 的方法):   Context objects.    (line  478)
* quantize() (decimal.Decimal 的方法):   Decimal objects.    (line  475)
* QueryInfoKey() (於 winreg 模組中):     函式<12>.           (line  318)
* QueryReflectionKey() (於 winreg 模組中): 函式<12>.         (line  515)
* QueryValue() (於 winreg 模組中):       函式<12>.           (line  347)
* QueryValueEx() (於 winreg 模組中):     函式<12>.           (line  367)
* QUESTION (於 tkinter.messagebox 模組中): tkinter messagebox --- Tkinter 訊息提示.
                                                             (line  174)
* Queue (asyncio 中的類別):              Queue.              (line    6)
* Queue (multiprocessing 中的類別):      Pipes and Queues.   (line   92)
* Queue (queue 中的類別):                queue --- 同步佇列 synchronized queue 類別.
                                                             (line   28)
* queue (sched.scheduler 的屬性):        排程器物件.         (line   64)
* Queue() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  197)
* QueueEmpty:                            例外<7>.            (line    6)
* QueueFull:                             例外<7>.            (line   11)
* QueueHandler (logging.handlers 中的類別): QueueHandler.    (line   21)
* QueueListener (logging.handlers 中的類別): QueueListener.  (line   25)
* QueueShutDown:                         例外<7>.            (line   16)
* quick_ratio() (difflib.SequenceMatcher 的方法): SequenceMatcher 物件.
                                                             (line  204)
* quiet (sys.flags 的屬性):              sys --- 系統特定的參數與函式.
                                                             (line  555)
* quit (pdb command):                    Debugger Commands.  (line  425)
* quit (內建變數):                       由 site module（模組）所添增的常數.
                                                             (line   11)
* quit() (ftplib.FTP 的方法):            FTP 物件.           (line  315)
* quit() (poplib.POP3 的方法):           POP3 物件.          (line   83)
* quit() (smtplib.SMTP 的方法):          SMTP 物件.          (line  340)
* quit() (tkinter.filedialog.FileDialog 的方法): Native Load/Save Dialogs.
                                                             (line  123)
* quitting (bdb.Bdb attribute):          bdb --- 偵錯器框架. (line  335)
* QUOTE_ALL (於 csv 模組中):             模組內容<3>.        (line  241)
* quote_from_bytes() (於 urllib.parse 模組中): URL Quoting.  (line   53)
* QUOTE_MINIMAL (於 csv 模組中):         模組內容<3>.        (line  245)
* QUOTE_NONE (於 csv 模組中):            模組內容<3>.        (line  256)
* QUOTE_NONNUMERIC (於 csv 模組中):      模組內容<3>.        (line  250)
* QUOTE_NOTNULL (於 csv 模組中):         模組內容<3>.        (line  265)
* quote_plus() (於 urllib.parse 模組中): URL Quoting.        (line   42)
* QUOTE_STRINGS (於 csv 模組中):         模組內容<3>.        (line  276)
* quote() (於 email.utils 模組中):       email utils：雜項工具.
                                                             (line   45)
* quote() (於 shlex 模組中):             shlex --- 簡單的語法分析.
                                                             (line   43)
* quote() (於 urllib.parse 模組中):      URL Quoting.        (line   13)
* quoteattr() (於 xml.sax.saxutils 模組中): xml sax saxutils --- SAX 工具程式.
                                                             (line   38)
* quotechar (csv.Dialect 的屬性):        Dialect 與格式參數. (line   47)
* quoted-printable（可列印字元）;encoding（編碼）: quopri --- 編碼和解碼 MIME 可列印字元資料.
                                                             (line    8)
* quotes (shlex.shlex 的屬性):           shlex 物件.         (line  115)
* quoting (csv.Dialect 的屬性):          Dialect 與格式參數. (line   54)
* R_OK (於 os 模組中):                   Files and Directories.
                                                             (line  107)
* r';raw string literal（原始字串常數）: String and Bytes literals.
                                                             (line   51)
* r";raw string literal（原始字串常數）: String and Bytes literals.
                                                             (line   51)
* radians() (於 math 模組中):            Angular conversion. (line   10)
* radians() (於 turtle 模組中):          Settings for measurement.
                                                             (line   28)
* radix (sys.float_info 的屬性):         sys --- 系統特定的參數與函式.
                                                             (line  660)
* radix() (decimal.Context 的方法):      Context objects.    (line  483)
* radix() (decimal.Decimal 的方法):      Decimal objects.    (line  503)
* RADIXCHAR (於 locale 模組中):          locale --- 國際化服務.
                                                             (line  266)
* Raise (ast 中的類別):                  陳述式.             (line  108)
* RAISE (monitoring event):              事件.               (line   71)
* raise an exception（引發例外）:        例外.               (line    6)
* raise_on_defect (email.policy.Policy 的屬性): email policy Policy Objects.
                                                             (line  181)
* raise_signal() (於 signal 模組中):     模組內容<5>.        (line  324)
* RAISE_VARARGS (opcode):                Python Bytecode Instructions.
                                                             (line  994)
* raiseExceptions (於 logging 模組中):   Module-Level Attributes.
                                                             (line   19)
* raiseing;exception（例外）:            raise 陳述式.       (line    6)
* RAND_add() (於 ssl 模組中):            隨機產生.           (line   27)
* RAND_bytes() (於 ssl 模組中):          隨機產生.           (line    6)
* RAND_status() (於 ssl 模組中):         隨機產生.           (line   21)
* randbelow() (於 secrets 模組中):       亂數.               (line   18)
* randbits() (於 secrets 模組中):        亂數.               (line   22)
* randbytes() (於 random 模組中):        回傳位元組的函式.   (line    6)
* randint() (於 random 模組中):          回傳整數的函式.     (line   28)
* Random (random 中的類別):              替代產生器.         (line    6)
* random 命令列選項; -c:                 Command-line usage. (line   18)
* random 命令列選項; -choice:            Command-line usage. (line   18)
* random 命令列選項; -f:                 Command-line usage. (line   29)
* random 命令列選項; -float:             Command-line usage. (line   29)
* random 命令列選項; -h:                 Command-line usage. (line   14)
* random 命令列選項; -help:              Command-line usage. (line   14)
* random 命令列選項; -i:                 Command-line usage. (line   23)
* random 命令列選項; -integer:           Command-line usage. (line   23)
* random() (random.Random 的方法):       替代產生器.         (line   32)
* random() (於 random 模組中):           實數分布.           (line    9)
* randrange() (於 random 模組中):        回傳整數的函式.     (line    6)
* range (內建類別):                      Ranges.             (line   10)
* RARROW (於 token 模組中):              token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  230)
* ratio() (difflib.SequenceMatcher 的方法): SequenceMatcher 物件.
                                                             (line  180)
* Rational (numbers 中的類別):           數值的階層.         (line   37)
* raw (io.BufferedIOBase 的屬性):        I/O 基礎類別.       (line  219)
* raw string（原始字串）:                String and Bytes literals.
                                                             (line   36)
* raw_data_manager (於 email.contentmanager 模組中): Content Manager Instances.
                                                             (line   11)
* raw_decode() (json.JSONDecoder 的方法): 編碼器與解碼器.    (line   88)
* raw_input() (code.InteractiveConsole 的方法): Interactive Console Objects.
                                                             (line   45)
* raw() (pickle.PickleBuffer 的方法):    模組介面.           (line  324)
* raw() (於 curses 模組中):              函式<5>.            (line  405)
* RawArray() (於 multiprocessing.sharedctypes 模組中): multiprocessing sharedctypes 模組.
                                                             (line   16)
* RawConfigParser (configparser 中的類別): RawConfigParser 物件.
                                                             (line    6)
* RawDescriptionHelpFormatter (argparse 中的類別): formatter_class.
                                                             (line   10)
* RawIOBase (io 中的類別):               I/O 基礎類別.       (line  150)
* RawPen (turtle 中的類別):              Public classes.     (line    6)
* RawTextHelpFormatter (argparse 中的類別): formatter_class. (line   10)
* RawTurtle (turtle 中的類別):           Public classes.     (line    6)
* RawValue() (於 multiprocessing.sharedctypes 模組中): multiprocessing sharedctypes 模組.
                                                             (line   33)
* RBRACE (於 token 模組中):              token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  130)
* re (re.Match 的屬性):                  Match Objects.      (line  205)
* READ (inspect.BufferFlags 的屬性):     Buffer flags.       (line   49)
* read_binary() (於 importlib.resources 模組中): Functional API.
                                                             (line   75)
* read_byte() (mmap.mmap 的方法):        mmap --- 記憶體映射檔案的支援.
                                                             (line  253)
* read_bytes() (importlib.abc.Traversable 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  579)
* read_bytes() (importlib.resources.abc.Traversable 的方法): importlib resources abc -- 資源的抽象基底類別.
                                                             (line  150)
* read_bytes() (pathlib.Path 的方法):    Reading and writing files.
                                                             (line   34)
* read_bytes() (zipfile.Path 的方法):    Path Objects.       (line  100)
* read_dict() (configparser.ConfigParser 的方法): ConfigParser 物件.
                                                             (line  199)
* read_environ() (於 wsgiref.handlers 模組中): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  259)
* read_events() (xml.etree.ElementTree.XMLPullParser 的方法): XMLPullParser 物件.
                                                             (line   48)
* read_file() (configparser.ConfigParser 的方法): ConfigParser 物件.
                                                             (line  177)
* read_history_file() (於 readline 模組中): History file.    (line    8)
* read_init_file() (於 readline 模組中): Init file.          (line   13)
* read_mime_types() (於 mimetypes 模組中): mimetypes --- 將檔案名稱對映到 MIME 類型.
                                                             (line  112)
* READ_RESTRICTED（C 巨集）:             Member flags.       (line   32)
* read_string() (configparser.ConfigParser 的方法): ConfigParser 物件.
                                                             (line  189)
* read_text() (importlib.abc.Traversable 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  583)
* read_text() (importlib.resources.abc.Traversable 的方法): importlib resources abc -- 資源的抽象基底類別.
                                                             (line  154)
* read_text() (pathlib.Path 的方法):     Reading and writing files.
                                                             (line   17)
* read_text() (zipfile.Path 的方法):     Path Objects.       (line   88)
* read_text() (於 importlib.resources 模組中): Functional API.
                                                             (line   89)
* read_token() (shlex.shlex 的方法):     shlex 物件.         (line   20)
* read_windows_registry() (mimetypes.MimeTypes 的方法): MimeTypes 物件.
                                                             (line   93)
* read() (asyncio.StreamReader 的方法):  StreamReader.       (line   19)
* read() (codecs.StreamReader 的方法):   StreamReader 物件.  (line   34)
* read() (configparser.ConfigParser 的方法): ConfigParser 物件.
                                                             (line  140)
* read() (http.client.HTTPResponse 的方法): HTTPResponse 物件.
                                                             (line   13)
* read() (imaplib.IMAP4 的方法):         IMAP4 物件.         (line  199)
* read() (io.BufferedIOBase 的方法):     I/O 基礎類別.       (line  236)
* read() (io.BufferedReader 的方法):     Buffered Streams.   (line   82)
* read() (io.RawIOBase 的方法):          I/O 基礎類別.       (line  161)
* read() (io.TextIOBase 的方法):         文字 I/O<2>.        (line   52)
* read() (mimetypes.MimeTypes 的方法):   MimeTypes 物件.     (line   77)
* read() (mmap.mmap 的方法):             mmap --- 記憶體映射檔案的支援.
                                                             (line  243)
* read() (sqlite3.Blob 的方法):          Blob 物件.          (line   45)
* read() (ssl.MemoryBIO 的方法):         Memory BIO Support<2>.
                                                             (line  148)
* read() (ssl.SSLSocket 的方法):         SSL Sockets.        (line   69)
* read() (urllib.robotparser.RobotFileParser 的方法): urllib robotparser --- robots txt 的剖析器.
                                                             (line   24)
* read() (zipfile.ZipFile 的方法):       ZipFile 物件.       (line  242)
* read() (於 os 模組中):                 File Descriptor Operations.
                                                             (line  725)
* read1() (bz2.BZ2File 的方法):          De compression of files.
                                                             (line  111)
* read1() (io.BufferedIOBase 的方法):    I/O 基礎類別.       (line  249)
* read1() (io.BufferedReader 的方法):    Buffered Streams.   (line   88)
* read1() (io.BytesIO 的方法):           Buffered Streams.   (line   43)
* READABLE (於 _tkinter 模組中):         File Handlers.      (line   41)
* readable() (bz2.BZ2File 的方法):       De compression of files.
                                                             (line   93)
* readable() (io.IOBase 的方法):         I/O 基礎類別.       (line   69)
* readall() (io.RawIOBase 的方法):       I/O 基礎類別.       (line  175)
* reader() (於 csv 模組中):              模組內容<3>.        (line    8)
* ReadError:                             tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  202)
* readexactly() (asyncio.StreamReader 的方法): StreamReader. (line   43)
* readfp() (mimetypes.MimeTypes 的方法): MimeTypes 物件.     (line   85)
* readframes() (wave.Wave_read 的方法):  Wave_read 物件.     (line   48)
* readinto() (bz2.BZ2File 的方法):       De compression of files.
                                                             (line  121)
* readinto() (http.client.HTTPResponse 的方法): HTTPResponse 物件.
                                                             (line   17)
* readinto() (io.BufferedIOBase 的方法): I/O 基礎類別.       (line  259)
* readinto() (io.RawIOBase 的方法):      I/O 基礎類別.       (line  180)
* readinto1() (io.BufferedIOBase 的方法): I/O 基礎類別.      (line  271)
* readinto1() (io.BytesIO 的方法):       Buffered Streams.   (line   49)
* readline() (asyncio.StreamReader 的方法): StreamReader.    (line   34)
* readline() (codecs.StreamReader 的方法): StreamReader 物件.
                                                             (line   60)
* readline() (imaplib.IMAP4 的方法):     IMAP4 物件.         (line  204)
* readline() (io.IOBase 的方法):         I/O 基礎類別.       (line   74)
* readline() (io.TextIOBase 的方法):     文字 I/O<2>.        (line   58)
* readline() (mmap.mmap 的方法):         mmap --- 記憶體映射檔案的支援.
                                                             (line  258)
* readlines() (codecs.StreamReader 的方法): StreamReader 物件.
                                                             (line   71)
* readlines() (io.IOBase 的方法):        I/O 基礎類別.       (line   83)
* readlink() (pathlib.Path 的方法):      Expanding and resolving paths.
                                                             (line   77)
* readlink() (於 os 模組中):             Files and Directories.
                                                             (line  660)
* readmodule_ex() (於 pyclbr 模組中):    pyclbr --- Python 模組瀏覽器支援.
                                                             (line   31)
* readmodule() (於 pyclbr 模組中):       pyclbr --- Python 模組瀏覽器支援.
                                                             (line   19)
* readonly (memoryview 的屬性):          Memory Views.       (line  416)
* ReadOnly (於 typing 模組中):           特別型式.           (line  220)
* READONLY（C 巨集）:                    Member flags.       (line   37)
* ReadTransport (asyncio 中的類別):      Transports Hierarchy.
                                                             (line   20)
* readuntil() (asyncio.StreamReader 的方法): StreamReader.   (line   52)
* readv() (於 os 模組中):                File Descriptor Operations.
                                                             (line  859)
* ready() (multiprocessing.pool.AsyncResult 的方法): Process Pools.
                                                             (line  212)
* Real (numbers 中的類別):               數值的階層.         (line   26)
* real (numbers.Complex 的屬性):         數值的階層.         (line   14)
* real_max_memuse (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  148)
* real_quick_ratio() (difflib.SequenceMatcher 的方法): SequenceMatcher 物件.
                                                             (line  209)
* realloc（C 函式）:                     總覽<2>.            (line   33)
* realpath() (於 os.path 模組中):        os path --- 常見的路徑名操作.
                                                             (line  314)
* REALTIME_PRIORITY_CLASS (於 subprocess 模組中): Windows Constants.
                                                             (line  103)
* reap_children() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  581)
* reap_threads() (於 test.support.threading_helper 模組中): test support threading_helper --- Utilities for threading tests.
                                                             (line   17)
* reason (http.client.HTTPResponse 的屬性): HTTPResponse 物件.
                                                             (line   65)
* reason (ssl.SSLError 的屬性):          例外<11>.           (line   24)
* reason (UnicodeError 的屬性):          實體例外.           (line  372)
* reason (urllib.error.HTTPError 的屬性): urllib error --- urllib request 引發的例外類別.
                                                             (line   45)
* reason (urllib.error.URLError 的屬性): urllib error --- urllib request 引發的例外類別.
                                                             (line   21)
* reattach() (tkinter.ttk.Treeview 的方法): ttk Treeview.    (line  236)
* rebinding（重新繫結）;name（名稱）:    Assignment statements.
                                                             (line    6)
* recent() (imaplib.IMAP4 的方法):       IMAP4 物件.         (line  209)
* reconfigure() (io.TextIOWrapper 的方法): 文字 I/O<2>.      (line  180)
* record_original_stdout() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  305)
* RECORDS (inspect.BufferFlags 的屬性):  Buffer flags.       (line   41)
* records (unittest.TestCase 的屬性):    Test cases.         (line  428)
* RECORDS_RO (inspect.BufferFlags 的屬性): Buffer flags.     (line   43)
* rect() (於 cmath 模組中):              轉換到極座標和從極座標做轉換.
                                                             (line   37)
* rectangle() (於 curses.textpad 模組中): curses textpad --- Text input widget for curses programs.
                                                             (line   15)
* RecursionError:                        實體例外.           (line  201)
* recursive_repr() (於 reprlib 模組中):  reprlib --- repr 的替代實作.
                                                             (line   60)
* recv_bytes_into() (multiprocessing.connection.Connection 的方法): Connection Objects.
                                                             (line   79)
* recv_bytes() (multiprocessing.connection.Connection 的方法): Connection Objects.
                                                             (line   65)
* recv_fds() (於 socket 模組中):         其他函式<2>.        (line  447)
* recv_into() (socket.socket 的方法):    Socket 物件.        (line  390)
* recv() (multiprocessing.connection.Connection 的方法): Connection Objects.
                                                             (line   24)
* recv() (socket.socket 的方法):         Socket 物件.        (line  233)
* recvfrom_into() (socket.socket 的方法): Socket 物件.       (line  380)
* recvfrom() (socket.socket 的方法):     Socket 物件.        (line  251)
* recvmsg_into() (socket.socket 的方法): Socket 物件.        (line  341)
* recvmsg() (socket.socket 的方法):      Socket 物件.        (line  269)
* redirect_request() (urllib.request.HTTPRedirectHandler 的方法): HTTPRedirectHandler 物件.
                                                             (line   15)
* redirect_stderr() (於 contextlib 模組中): Utilities.       (line  356)
* redirect_stdout() (於 contextlib 模組中): Utilities.       (line  316)
* redisplay() (於 readline 模組中):      Line buffer.        (line   19)
* redrawln() (curses.window 的方法):     Window Objects.     (line  461)
* redrawwin() (curses.window 的方法):    Window Objects.     (line  467)
* reduce() (於 functools 模組中):        functools --- 可呼叫物件上的高階函式與操作.
                                                             (line  348)
* reducer_override() (pickle.Pickler 的方法): 模組介面.      (line  203)
* ref (weakref 中的類別):                weakref --- 弱參照. (line   72)
* refcount_test() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  540)
* reference count（參照計數）:           術語表.             (line 1093)
* reference counting（參照計數）:        Objects values and types.
                                                             (line   37)
* ReferenceError:                        實體例外.           (line  208)
* ReferenceType (於 weakref 模組中):     weakref --- 弱參照. (line  270)
* refold_source (email.policy.EmailPolicy 的屬性): email policy Policy Objects.
                                                             (line  388)
* refresh() (curses.window 的方法):      Window Objects.     (line  472)
* REG_BINARY (於 winreg 模組中):         Value Types.        (line    8)
* REG_DWORD (於 winreg 模組中):          Value Types.        (line   12)
* REG_DWORD_BIG_ENDIAN (於 winreg 模組中): Value Types.      (line   21)
* REG_DWORD_LITTLE_ENDIAN (於 winreg 模組中): Value Types.   (line   16)
* REG_EXPAND_SZ (於 winreg 模組中):      Value Types.        (line   25)
* REG_FULL_RESOURCE_DESCRIPTOR (於 winreg 模組中): Value Types.
                                                             (line   60)
* REG_LINK (於 winreg 模組中):           Value Types.        (line   30)
* REG_MULTI_SZ (於 winreg 模組中):       Value Types.        (line   34)
* REG_NONE (於 winreg 模組中):           Value Types.        (line   39)
* REG_QWORD (於 winreg 模組中):          Value Types.        (line   43)
* REG_QWORD_LITTLE_ENDIAN (於 winreg 模組中): Value Types.   (line   49)
* REG_RESOURCE_LIST (於 winreg 模組中):  Value Types.        (line   56)
* REG_RESOURCE_REQUIREMENTS_LIST (於 winreg 模組中): Value Types.
                                                             (line   64)
* REG_SZ (於 winreg 模組中):             Value Types.        (line   68)
* RegexFlag (re 中的類別):               旗標.               (line    9)
* register_adapter() (於 sqlite3 模組中): Module functions.  (line  140)
* register_archive_format() (於 shutil 模組中): Archiving operations.
                                                             (line   92)
* register_at_fork() (於 os 模組中):     行程管理.           (line  552)
* register_callback() (於 sys.monitoring 模組中): 註冊回呼函式.
                                                             (line    8)
* register_converter() (於 sqlite3 模組中): Module functions.
                                                             (line  147)
* register_defect() (email.policy.Policy 的方法): email policy Policy Objects.
                                                             (line  246)
* register_dialect() (於 csv 模組中):    模組內容<3>.        (line   62)
* register_error() (於 codecs 模組中):   Error Handlers.     (line  101)
* register_function() (xmlrpc.server.CGIXMLRPCRequestHandler 的方法): CGIXMLRPCRequestHandler.
                                                             (line    9)
* register_function() (xmlrpc.server.SimpleXMLRPCServer 的方法): SimpleXMLRPCServer 物件.
                                                             (line   10)
* register_instance() (xmlrpc.server.CGIXMLRPCRequestHandler 的方法): CGIXMLRPCRequestHandler.
                                                             (line   26)
* register_instance() (xmlrpc.server.SimpleXMLRPCServer 的方法): SimpleXMLRPCServer 物件.
                                                             (line   27)
* register_introspection_functions() (xmlrpc.server.CGIXMLRPCRequestHandler 的方法): CGIXMLRPCRequestHandler.
                                                             (line   41)
* register_introspection_functions() (xmlrpc.server.SimpleXMLRPCServer 的方法): SimpleXMLRPCServer 物件.
                                                             (line   55)
* register_multicall_functions() (xmlrpc.server.CGIXMLRPCRequestHandler 的方法): CGIXMLRPCRequestHandler.
                                                             (line   46)
* register_multicall_functions() (xmlrpc.server.SimpleXMLRPCServer 的方法): SimpleXMLRPCServer 物件.
                                                             (line   60)
* register_namespace() (於 xml.etree.ElementTree 模組中): 函式<8>.
                                                             (line  198)
* register_optionflag() (於 doctest 模組中): 可選旗標.       (line  161)
* register_shape() (於 turtle 模組中):   Settings and special methods.
                                                             (line   70)
* register_unpack_format() (於 shutil 模組中): Archiving operations.
                                                             (line  162)
* register() (abc.ABCMeta 的方法):       abc --- 抽象基底類別.
                                                             (line   60)
* register() (multiprocessing.managers.BaseManager 的方法): Managers.
                                                             (line   92)
* register() (select.devpoll 的方法):    /dev/poll Polling Objects.
                                                             (line   30)
* register() (select.epoll 的方法):      Edge and Level Trigger Polling epoll Objects.
                                                             (line   81)
* register() (select.poll 的方法):       Polling Objects.    (line   15)
* register() (selectors.BaseSelector 的方法): Classes<3>.    (line   65)
* register() (於 atexit 模組中):         atexit --- 退出處理函式.
                                                             (line   22)
* register() (於 codecs 模組中):         codecs --- 編解碼器註冊表和基底類別.
                                                             (line  150)
* register() (於 faulthandler 模組中):   Dumping the traceback on a user signal.
                                                             (line    6)
* register() (於 webbrowser 模組中):     webbrowser --- 方便的網頁瀏覽器控制器.
                                                             (line  109)
* registerDOMImplementation() (於 xml.dom 模組中): 模組內容<6>.
                                                             (line    8)
* registerResult() (於 unittest 模組中): Signal Handling.    (line   35)
* REGTYPE (於 tarfile 模組中):           tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  267)
* regular package（正規套件）:           術語表.             (line 1103)
* relative_to() (pathlib.PurePath 的方法): 方法與屬性.       (line  300)
* relative（相對）;import（引入）:       import 陳述式.      (line   99)
* relative（相對）;URL（統一資源定位器）: urllib parse --- 將 URL 剖析成元件.
                                                             (line    8)
* release() (_thread.lock 的方法):       _thread --- 低階執行緒 API.
                                                             (line  139)
* release() (asyncio.Condition 的方法):  Condition.          (line   70)
* release() (asyncio.Lock 的方法):       Lock.               (line   47)
* release() (asyncio.Semaphore 的方法):  Semaphore.          (line   50)
* release() (logging.Handler 的方法):    Handler Objects.    (line   31)
* release() (memoryview 的方法):         Memory Views.       (line  238)
* release() (multiprocessing.Lock 的方法): Synchronization primitives.
                                                             (line   91)
* release() (multiprocessing.RLock 的方法): Synchronization primitives.
                                                             (line  147)
* release() (pickle.PickleBuffer 的方法): 模組介面.          (line  332)
* release() (threading.Condition 的方法): Condition Objects. (line   91)
* release() (threading.Lock 的方法):     Lock Objects.       (line   73)
* release() (threading.RLock 的方法):    RLock 物件.         (line   94)
* release() (threading.Semaphore 的方法): Semaphore Objects. (line   63)
* release() (於 platform 模組中):        跨平台.             (line  101)
* releasebufferproc (C type):            Slot Type typedefs. (line  104)
* reload() (於 importlib 模組中):        函式<11>.           (line   55)
* relpath() (於 os.path 模組中):         os path --- 常見的路徑名操作.
                                                             (line  339)
* remainder_near() (decimal.Context 的方法): Context objects.
                                                             (line  494)
* remainder_near() (decimal.Decimal 的方法): Decimal objects.
                                                             (line  509)
* remainder() (decimal.Context 的方法):  Context objects.    (line  487)
* remainder() (於 math 模組中):          數論與表現函式.     (line  231)
* RemoteDisconnected:                    http client --- HTTP 協定用戶端.
                                                             (line  187)
* remove_child_handler() (asyncio.AbstractChildWatcher 的方法): Process Watchers.
                                                             (line   56)
* remove_done_callback() (asyncio.Future 的方法): Future 物件<2>.
                                                             (line   98)
* remove_done_callback() (asyncio.Task 的方法): Task Object. (line  111)
* remove_flag() (mailbox.Maildir 的方法): Mailbox 物件<2>.   (line  142)
* remove_flag() (mailbox.MaildirMessage 的方法): MaildirMessage 物件.
                                                             (line   84)
* remove_flag() (mailbox.mboxMessage 的方法): mboxMessage 物件.
                                                             (line   85)
* remove_flag() (mailbox.MMDFMessage 的方法): MMDFMessage 物件.
                                                             (line   84)
* remove_folder() (mailbox.Maildir 的方法): Mailbox 物件<2>. (line   80)
* remove_folder() (mailbox.MH 的方法):   MH 物件.            (line   50)
* remove_header() (urllib.request.Request 的方法): Request Objects.
                                                             (line   99)
* remove_history_item() (於 readline 模組中): History list.  (line   26)
* remove_label() (mailbox.BabylMessage 的方法): BabylMessage 物件.
                                                             (line   59)
* remove_option() (configparser.ConfigParser 的方法): ConfigParser 物件.
                                                             (line  298)
* remove_option() (optparse.OptionParser 的方法): Querying and manipulating your option parser.
                                                             (line   47)
* remove_reader() (asyncio.loop 的方法): 監視檔案描述器.     (line   11)
* remove_section() (configparser.ConfigParser 的方法): ConfigParser 物件.
                                                             (line  305)
* remove_sequence() (mailbox.MHMessage 的方法): MHMessage 物件.
                                                             (line   46)
* remove_signal_handler() (asyncio.loop 的方法): Unix 訊號.  (line   22)
* remove_writer() (asyncio.loop 的方法): 監視檔案描述器.     (line   24)
* remove() (array.array 的方法):         array --- 高效率的數值型陣列.
                                                             (line  194)
* remove() (collections.deque 的方法):   deque 物件.         (line   89)
* remove() (frozenset 的方法):           Set Types --- set frozenset.
                                                             (line  199)
* remove() (mailbox.Mailbox 的方法):     Mailbox 物件.       (line   76)
* remove() (mailbox.MH 的方法):          MH 物件.            (line   79)
* remove() (xml.etree.ElementTree.Element 的方法): Element 物件.
                                                             (line  170)
* remove() (於 os 模組中):               Files and Directories.
                                                             (line  696)
* remove()（序列方法）:                  Mutable Sequence Types.
                                                             (line   16)
* removeAttribute() (xml.dom.Element 的方法): Element Objects.
                                                             (line   52)
* removeAttributeNode() (xml.dom.Element 的方法): Element Objects.
                                                             (line   57)
* removeAttributeNS() (xml.dom.Element 的方法): Element Objects.
                                                             (line   62)
* removeChild() (xml.dom.Node 的方法):   Node Objects.       (line  128)
* removedirs() (於 os 模組中):           Files and Directories.
                                                             (line  720)
* removeFilter() (logging.Handler 的方法): Handler Objects.  (line   56)
* removeFilter() (logging.Logger 的方法): Logger 物件.       (line  326)
* removeHandler() (logging.Logger 的方法): Logger 物件.      (line  343)
* removeHandler() (於 unittest 模組中):  Signal Handling.    (line   52)
* removeprefix() (bytearray 的方法):     Bytes and Bytearray Operations.
                                                             (line   52)
* removeprefix() (bytes 的方法):         Bytes and Bytearray Operations.
                                                             (line   52)
* removeprefix() (str 的方法):           String Methods<2>.  (line  369)
* removeResult() (於 unittest 模組中):   Signal Handling.    (line   46)
* removesuffix() (bytearray 的方法):     Bytes and Bytearray Operations.
                                                             (line   72)
* removesuffix() (bytes 的方法):         Bytes and Bytearray Operations.
                                                             (line   72)
* removesuffix() (str 的方法):           String Methods<2>.  (line  382)
* removexattr() (於 os 模組中):          Linux extended attributes.
                                                             (line   40)
* rename() (ftplib.FTP 的方法):          FTP 物件.           (line  283)
* rename() (imaplib.IMAP4 的方法):       IMAP4 物件.         (line  214)
* rename() (pathlib.Path 的方法):        Renaming and deleting.
                                                             (line    6)
* rename() (於 os 模組中):               Files and Directories.
                                                             (line  737)
* renames() (於 os 模組中):              Files and Directories.
                                                             (line  773)
* reopenIfNeeded() (logging.handlers.WatchedFileHandler 的方法): WatchedFileHandler.
                                                             (line   41)
* reorganize() (dbm.gnu.gdbm 的方法):    dbm gnu --- GNU 資料庫管理器.
                                                             (line   96)
* repeat() (timeit.Timer 的方法):        Python 介面.        (line   90)
* repeat() (於 itertools 模組中):        Itertool 函式.      (line  473)
* repeat() (於 timeit 模組中):           Python 介面.        (line   17)
* repetition（重複）;operation（操作）:  Common Sequence Operations.
                                                             (line   21)
* REPL:                                  術語表.             (line 1110)
* replace_errors() (於 codecs 模組中):   Error Handlers.     (line  154)
* replace_header() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  299)
* replace_header() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  407)
* replace_history_item() (於 readline 模組中): History list. (line   32)
* replace_whitespace (textwrap.TextWrapper 的屬性): textwrap --- 文字包裝與填充.
                                                             (line  182)
* replace;error handler's name（錯誤處理器名稱）: Error Handlers.
                                                             (line   15)
* replace() (bytearray 的方法):          Bytes and Bytearray Operations.
                                                             (line  198)
* replace() (bytes 的方法):              Bytes and Bytearray Operations.
                                                             (line  198)
* replace() (codeobject 的方法):         用於程式碼物件的方法.
                                                             (line   85)
* replace() (curses.panel.Panel 的方法): Panel Objects.      (line   39)
* replace() (datetime.date 的方法):      date 物件.          (line  194)
* replace() (datetime.datetime 的方法):  datetime 物件.      (line  457)
* replace() (datetime.time 的方法):      time 物件.          (line  149)
* replace() (inspect.Parameter 的方法):  Introspecting callables with the Signature object.
                                                             (line  302)
* replace() (inspect.Signature 的方法):  Introspecting callables with the Signature object.
                                                             (line  137)
* replace() (pathlib.Path 的方法):       Renaming and deleting.
                                                             (line   30)
* replace() (str 的方法):                String Methods<2>.  (line  395)
* replace() (tarfile.TarInfo 的方法):    TarInfo 物件.       (line  166)
* replace() (於 copy 模組中):            copy --- 淺層 shallow 和深層 deep 複製操作.
                                                             (line   25)
* replace() (於 dataclasses 模組中):     模組內容<8>.        (line  423)
* replace() (於 os 模組中):              Files and Directories.
                                                             (line  791)
* replaceChild() (xml.dom.Node 的方法):  Node Objects.       (line  135)
* ReplacePackage() (於 modulefinder 模組中): modulefinder --- 搜尋腳本所使用的模組.
                                                             (line   18)
* REPORT_CDIFF (於 doctest 模組中):      可選旗標.           (line  115)
* REPORT_ERRMODE (於 msvcrt 模組中):     Other Functions.    (line   35)
* report_failure() (doctest.DocTestRunner 的方法): DocTestRunner 物件.
                                                             (line   76)
* report_full_closure() (filecmp.dircmp 的方法): The dircmp class.
                                                             (line   31)
* REPORT_NDIFF (於 doctest 模組中):      可選旗標.           (line  120)
* REPORT_ONLY_FIRST_FAILURE (於 doctest 模組中): 可選旗標.   (line  129)
* report_partial_closure() (filecmp.dircmp 的方法): The dircmp class.
                                                             (line   26)
* report_start() (doctest.DocTestRunner 的方法): DocTestRunner 物件.
                                                             (line   54)
* report_success() (doctest.DocTestRunner 的方法): DocTestRunner 物件.
                                                             (line   65)
* REPORT_UDIFF (於 doctest 模組中):      可選旗標.           (line  110)
* report_unexpected_exception() (doctest.DocTestRunner 的方法): DocTestRunner 物件.
                                                             (line   87)
* report() (filecmp.dircmp 的方法):      The dircmp class.   (line   21)
* report() (modulefinder.ModuleFinder 的方法): modulefinder --- 搜尋腳本所使用的模組.
                                                             (line   32)
* REPORTING_FLAGS (於 doctest 模組中):   可選旗標.           (line  153)
* Repr (reprlib 中的類別):               reprlib --- repr 的替代實作.
                                                             (line   17)
* repr() (reprlib.Repr 的方法):          Repr 物件.          (line  107)
* repr() （內建函式）;__repr__() （物件方法）: Basic customization.
                                                             (line  114)
* repr() (於 reprlib 模組中):            reprlib --- repr 的替代實作.
                                                             (line   50)
* repr1() (reprlib.Repr 的方法):         Repr 物件.          (line  112)
* ReprEnum (enum 中的類別):              資料型別<2>.        (line  542)
* reprfunc (C type):                     Slot Type typedefs. (line   39)
* request (socketserver.BaseRequestHandler 的屬性): Request Handler Objects.
                                                             (line   42)
* Request (urllib.request 中的類別):     urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  163)
* request_queue_size (socketserver.BaseServer 的屬性): Server Objects.
                                                             (line   98)
* request_rate() (urllib.robotparser.RobotFileParser 的方法): urllib robotparser --- robots txt 的剖析器.
                                                             (line   54)
* request_uri() (於 wsgiref.util 模組中): wsgiref util -- WSGI 環境工具.
                                                             (line   22)
* request_version (http.server.BaseHTTPRequestHandler 的屬性): http server — HTTP 伺服器.
                                                             (line  104)
* request() (http.client.HTTPConnection 的方法): HTTPConnection 物件.
                                                             (line    8)
* RequestHandlerClass (socketserver.BaseServer 的屬性): Server Objects.
                                                             (line   71)
* requestline (http.server.BaseHTTPRequestHandler 的屬性): http server — HTTP 伺服器.
                                                             (line   86)
* Required (於 typing 模組中):           特別型式.           (line  203)
* requires_bz2() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  504)
* requires_docstrings() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  516)
* requires_freebsd_version() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  472)
* requires_gil_enabled() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  487)
* requires_gzip() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  500)
* requires_IEEE_754() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  492)
* requires_limited_api() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  520)
* requires_linux_version() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  477)
* requires_lzma() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  508)
* requires_mac_version() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  482)
* requires_resource() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  512)
* requires_zlib() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  496)
* requires() (於 test.support 模組中):   test support --- Python 測試套件的工具.
                                                             (line  256)
* RERAISE (monitoring event):            事件.               (line   76)
* RERAISE (opcode):                      Python Bytecode Instructions.
                                                             (line  441)
* reschedule() (asyncio.Timeout 的方法): Timeouts.           (line   68)
* reserved (zipfile.ZipInfo 的屬性):     ZipInfo 物件.       (line  111)
* reserved word（保留字）:               關鍵字.             (line    6)
* RESERVED_FUTURE (於 uuid 模組中):      uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  223)
* RESERVED_MICROSOFT (於 uuid 模組中):   uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  219)
* RESERVED_NCS (於 uuid 模組中):         uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  211)
* reset_mock() (unittest.mock.AsyncMock 的方法): Mock 類別.  (line  809)
* reset_mock() (unittest.mock.Mock 的方法): Mock 類別.       (line  182)
* reset_peak() (於 tracemalloc 模組中):  函式<10>.           (line   38)
* reset_prog_mode() (於 curses 模組中):  函式<5>.            (line  411)
* reset_shell_mode() (於 curses 模組中): 函式<5>.            (line  416)
* reset_tzpath() (於 zoneinfo 模組中):   函式<2>.            (line   27)
* reset() (asyncio.Barrier 的方法):      Barrier.            (line   78)
* reset() (bdb.Bdb 的方法):              bdb --- 偵錯器框架. (line  158)
* reset() (codecs.IncrementalDecoder 的方法): IncrementalDecoder 物件.
                                                             (line   40)
* reset() (codecs.IncrementalEncoder 的方法): IncrementalEncoder 物件.
                                                             (line   35)
* reset() (codecs.StreamReader 的方法):  StreamReader 物件.  (line   83)
* reset() (codecs.StreamWriter 的方法):  StreamWriter 物件.  (line   42)
* reset() (contextvars.ContextVar 的方法): Context Variables.
                                                             (line   58)
* reset() (html.parser.HTMLParser 的方法): HTMLParser 方法.  (line   20)
* reset() (threading.Barrier 的方法):    Barrier Objects.    (line   71)
* reset() (xml.dom.pulldom.DOMEventStream 的方法): DOMEventStream 物件.
                                                             (line   37)
* reset() (xml.sax.xmlreader.IncrementalParser 的方法): IncrementalParser 物件.
                                                             (line   19)
* reset() (於 turtle 模組中):            More drawing control.
                                                             (line    6)
* resetbuffer() (code.InteractiveConsole 的方法): Interactive Console Objects.
                                                             (line   41)
* resetscreen() (於 turtle 模組中):      Window control.     (line   59)
* resetty() (於 curses 模組中):          函式<5>.            (line  421)
* resetwarnings() (於 warnings 模組中):  Available Functions.
                                                             (line  128)
* resize_term() (於 curses 模組中):      函式<5>.            (line  426)
* resize() (curses.window 的方法):       Window Objects.     (line  491)
* resize() (mmap.mmap 的方法):           mmap --- 記憶體映射檔案的支援.
                                                             (line  264)
* resize() (於 ctypes 模組中):           Utility functions.  (line  160)
* resizemode() (於 turtle 模組中):       Appearance.         (line   24)
* resizeterm() (於 curses 模組中):       函式<5>.            (line  436)
* resolution (datetime.date 的屬性):     date 物件.          (line  109)
* resolution (datetime.datetime 的屬性): datetime 物件.      (line  291)
* resolution (datetime.time 的屬性):     time 物件.          (line   42)
* resolution (datetime.timedelta 的屬性): timedelta 物件.    (line   84)
* resolve_bases() (於 types 模組中):     Dynamic Type Creation.
                                                             (line   57)
* resolve_name() (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line   80)
* resolve_name() (於 pkgutil 模組中):    pkgutil --- 套件擴充工具程式.
                                                             (line  177)
* resolve() (pathlib.Path 的方法):       Expanding and resolving paths.
                                                             (line   48)
* resolveEntity() (xml.sax.handler.EntityResolver 的方法): EntityResolver 物件.
                                                             (line    6)
* resource_path() (importlib.abc.ResourceReader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  501)
* resource_path() (importlib.resources.abc.ResourceReader 的方法): importlib resources abc -- 資源的抽象基底類別.
                                                             (line   55)
* ResourceDenied:                        test support --- Python 測試套件的工具.
                                                             (line   21)
* ResourceLoader (importlib.abc 中的類別): importlib abc -- Abstract base classes related to import.
                                                             (line  205)
* ResourceReader (importlib.abc 中的類別): importlib abc -- Abstract base classes related to import.
                                                             (line  456)
* ResourceReader (importlib.resources.abc 中的類別): importlib resources abc -- 資源的抽象基底類別.
                                                             (line   12)
* ResourceWarning:                       警告.               (line   76)
* response() (imaplib.IMAP4 的方法):     IMAP4 物件.         (line  218)
* ResponseNotReady:                      http client --- HTTP 協定用戶端.
                                                             (line  173)
* responses (http.server.BaseHTTPRequestHandler 的屬性): http server — HTTP 伺服器.
                                                             (line  179)
* responses (於 http.client 模組中):     http client --- HTTP 協定用戶端.
                                                             (line  208)
* restart (pdb command):                 Debugger Commands.  (line  416)
* restart_events() (於 sys.monitoring 模組中): 停用事件.     (line   21)
* restore() (test.support.SaveSignals 的方法): test support --- Python 測試套件的工具.
                                                             (line  770)
* restore() (於 difflib 模組中):         difflib --- 計算差異的輔助工具.
                                                             (line  271)
* RESTRICTED（C 巨集）:                  Member flags.       (line   32)
* restricted（受限）;execution（執行）:  Builtins and restricted execution.
                                                             (line    6)
* restype (ctypes._FuncPtr 的屬性):      Foreign functions.  (line   22)
* result() (asyncio.Future 的方法):      Future 物件<2>.     (line   27)
* result() (asyncio.Task 的方法):        Task Object.        (line   73)
* result() (concurrent.futures.Future 的方法): Future 物件.  (line   31)
* results() (trace.Trace 的方法):        Programmatic Interface.
                                                             (line   40)
* RESUME (opcode):                       Python Bytecode Instructions.
                                                             (line 1198)
* resume_reading() (asyncio.ReadTransport 的方法): Read-only Transports.
                                                             (line   21)
* resume_writing() (asyncio.BaseProtocol 的方法): Base Protocol.
                                                             (line   44)
* retr() (poplib.POP3 的方法):           POP3 物件.          (line   63)
* retrbinary() (ftplib.FTP 的方法):      FTP 物件.           (line  154)
* retrieve() (urllib.request.URLopener 的方法): Legacy interface.
                                                             (line  112)
* retrlines() (ftplib.FTP 的方法):       FTP 物件.           (line  177)
* RETRY (於 tkinter.messagebox 模組中):  tkinter messagebox --- Tkinter 訊息提示.
                                                             (line  129)
* RETRYCANCEL (於 tkinter.messagebox 模組中): tkinter messagebox --- Tkinter 訊息提示.
                                                             (line  155)
* Return (ast 中的類別):                 函式和類別定義.     (line  107)
* return (pdb command):                  Debugger Commands.  (line  222)
* return_annotation (inspect.Signature 的屬性): Introspecting callables with the Signature object.
                                                             (line  116)
* RETURN_CONST (opcode):                 Python Bytecode Instructions.
                                                             (line  406)
* RETURN_GENERATOR (opcode):             Python Bytecode Instructions.
                                                             (line 1223)
* return_ok() (http.cookiejar.CookiePolicy 的方法): CookiePolicy 物件.
                                                             (line   18)
* RETURN_VALUE (opcode):                 Python Bytecode Instructions.
                                                             (line  402)
* return_value (unittest.mock.Mock 的屬性): Mock 類別.       (line  293)
* returncode (asyncio.subprocess.Process 的屬性): Interacting with Subprocesses.
                                                             (line  145)
* returncode (subprocess.CalledProcessError 的屬性): Using the subprocess Module.
                                                             (line  211)
* returncode (subprocess.CompletedProcess 的屬性): Using the subprocess Module.
                                                             (line  110)
* returncode (subprocess.Popen 的屬性):  Popen Objects.      (line  149)
* retval (pdb command):                  Debugger Commands.  (line  435)
* reveal_type() (於 typing 模組中):      函式與裝飾器.       (line   82)
* reverse_order() (pstats.Stats 的方法): The Stats Class.    (line  157)
* reverse_pointer (ipaddress.IPv4Address 的屬性): Address objects.
                                                             (line   77)
* reverse_pointer (ipaddress.IPv6Address 的屬性): Address objects.
                                                             (line  258)
* reverse() (array.array 的方法):        array --- 高效率的數值型陣列.
                                                             (line  204)
* reverse() (collections.deque 的方法):  deque 物件.         (line   94)
* reverse()（序列方法）:                 Mutable Sequence Types.
                                                             (line   16)
* Reversible (collections.abc 中的類別): Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line   49)
* Reversible (typing 中的類別):          Aliases to other ABCs in collections abc.
                                                             (line   60)
* revert() (http.cookiejar.FileCookieJar 的方法): CookieJar 與 FileCookieJar 物件.
                                                             (line  142)
* rewind() (wave.Wave_read 的方法):      Wave_read 物件.     (line   52)
* RFC_4122 (於 uuid 模組中):             uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  215)
* RFC; RFC 1123:                         函式<4>.            (line  650)
* RFC; RFC 1123 <1>:                     函式<4>.            (line  661)
* RFC; RFC 1123 <2>:                     函式<4>.            (line  676)
* RFC; RFC 1321:                         hashlib --- 安全雜湊與訊息摘要.
                                                             (line   13)
* RFC; RFC 1422:                         Certificates.       (line   38)
* RFC; RFC 1422 <1>:                     TLS 1 3.            (line   41)
* RFC; RFC 1521:                         安全性注意事項<2>.  (line   17)
* RFC; RFC 1521 <1>:                     quopri --- 編碼和解碼 MIME 可列印字元資料.
                                                             (line   10)
* RFC; RFC 1521 <2>:                     quopri --- 編碼和解碼 MIME 可列印字元資料.
                                                             (line   31)
* RFC; RFC 1522:                         binascii --- 在二進位制和 ASCII 之間轉換.
                                                             (line   86)
* RFC; RFC 1522 <1>:                     quopri --- 編碼和解碼 MIME 可列印字元資料.
                                                             (line   20)
* RFC; RFC 1522 <2>:                     quopri --- 編碼和解碼 MIME 可列印字元資料.
                                                             (line   32)
* RFC; RFC 1730:                         imaplib --- IMAP4 協定客戶端.
                                                             (line   14)
* RFC; RFC 1738:                         URL Quoting.        (line  187)
* RFC; RFC 1750:                         隨機產生.           (line   31)
* RFC; RFC 1766:                         locale --- 國際化服務.
                                                             (line  356)
* RFC; RFC 1766 <1>:                     locale --- 國際化服務.
                                                             (line  369)
* RFC; RFC 1808:                         urllib<2>.          (line   23)
* RFC; RFC 1808 <1>:                     urllib parse --- 將 URL 剖析成元件.
                                                             (line   33)
* RFC; RFC 1808 <2>:                     URL Parsing.        (line   42)
* RFC; RFC 1808 <3>:                     URL Quoting.        (line  181)
* RFC; RFC 1869:                         smtplib --- SMTP 協定用戶端.
                                                             (line   13)
* RFC; RFC 1869 <1>:                     smtplib --- SMTP 協定用戶端.
                                                             (line  190)
* RFC; RFC 1870:                         smtpd<4>.           (line    6)
* RFC; RFC 1939:                         poplib --- POP3 協定用戶端.
                                                             (line   11)
* RFC; RFC 1939 <1>:                     poplib --- POP3 協定用戶端.
                                                             (line   13)
* RFC; RFC 2014:                         hmac --- 基於金鑰雜湊的訊息驗證.
                                                             (line   10)
* RFC; RFC 2033:                         New and Improved Modules<2>.
                                                             (line  567)
* RFC; RFC 2045:                         email --- 郵件和 MIME 處理套件.
                                                             (line   15)
* RFC; RFC 2045 <1>:                     email message：表示電子郵件訊息.
                                                             (line  314)
* RFC; RFC 2045 <2>:                     email message：表示電子郵件訊息.
                                                             (line  316)
* RFC; RFC 2045 <3>:                     email message：表示電子郵件訊息.
                                                             (line  319)
* RFC; RFC 2045 <4>:                     email headerregistry：自訂標頭物件.
                                                             (line  239)
* RFC; RFC 2045 <5>:                     email headerregistry：自訂標頭物件.
                                                             (line  297)
* RFC; RFC 2045 <6>:                     email message Message Representing an email message using the compat32 API.
                                                             (line  420)
* RFC; RFC 2045 <7>:                     email message Message Representing an email message using the compat32 API.
                                                             (line  424)
* RFC; RFC 2045 <8>:                     email message Message Representing an email message using the compat32 API.
                                                             (line  427)
* RFC; RFC 2045 <9>:                     email message Message Representing an email message using the compat32 API.
                                                             (line  524)
* RFC; RFC 2045 <10>:                    email header：國際化標頭.
                                                             (line   31)
* RFC; RFC 2045 <11>:                    base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   24)
* RFC; RFC 2045 <12>:                    base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   25)
* RFC; RFC 2045 <13>:                    base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  242)
* RFC; RFC 2045 <14>:                    base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  249)
* RFC; RFC 2045#section-6.8:             Binary Objects.     (line   31)
* RFC; RFC 2046:                         email --- 郵件和 MIME 處理套件.
                                                             (line   15)
* RFC; RFC 2046 <1>:                     Content Manager Instances.
                                                             (line   83)
* RFC; RFC 2046 <2>:                     email header：國際化標頭.
                                                             (line   32)
* RFC; RFC 2047:                         PEP 3333 Python Web Server Gateway Interface v1 0 1.
                                                             (line   21)
* RFC; RFC 2047 <1>:                     email<6>.           (line   27)
* RFC; RFC 2047 <2>:                     email --- 郵件和 MIME 處理套件.
                                                             (line   16)
* RFC; RFC 2047 <3>:                     email policy Policy Objects.
                                                             (line  364)
* RFC; RFC 2047 <4>:                     email policy Policy Objects.
                                                             (line  370)
* RFC; RFC 2047 <5>:                     email headerregistry：自訂標頭物件.
                                                             (line   78)
* RFC; RFC 2047 <6>:                     email headerregistry：自訂標頭物件.
                                                             (line  123)
* RFC; RFC 2047 <7>:                     email headerregistry：自訂標頭物件.
                                                             (line  128)
* RFC; RFC 2047 <8>:                     email header：國際化標頭.
                                                             (line   32)
* RFC; RFC 2047 <9>:                     email header：國際化標頭.
                                                             (line   55)
* RFC; RFC 2047 <10>:                    email header：國際化標頭.
                                                             (line  117)
* RFC; RFC 2047 <11>:                    email header：國際化標頭.
                                                             (line  141)
* RFC; RFC 2047 <12>:                    email utils：雜項工具.
                                                             (line   78)
* RFC; RFC 2060:                         imaplib --- IMAP4 協定客戶端.
                                                             (line   13)
* RFC; RFC 2060 <1>:                     IMAP4 物件.         (line  317)
* RFC; RFC 2068:                         http cookies --- HTTP 狀態管理.
                                                             (line   16)
* RFC; RFC 2104:                         New and Improved Modules<3>.
                                                             (line   35)
* RFC; RFC 2109:                         http cookies --- HTTP 狀態管理.
                                                             (line   15)
* RFC; RFC 2109 <1>:                     http cookies --- HTTP 狀態管理.
                                                             (line   36)
* RFC; RFC 2109 <2>:                     http cookies --- HTTP 狀態管理.
                                                             (line   67)
* RFC; RFC 2109 <3>:                     Morsel 物件.        (line    8)
* RFC; RFC 2109 <4>:                     Morsel 物件.        (line   11)
* RFC; RFC 2109 <5>:                     Morsel 物件.        (line   91)
* RFC; RFC 2109 <6>:                     Morsel 物件.        (line  103)
* RFC; RFC 2109 <7>:                     http cookiejar --- HTTP 客戶端的 Cookie 處理.
                                                             (line   18)
* RFC; RFC 2109 <8>:                     http cookiejar --- HTTP 客戶端的 Cookie 處理.
                                                             (line  102)
* RFC; RFC 2109 <9>:                     http cookiejar --- HTTP 客戶端的 Cookie 處理.
                                                             (line  114)
* RFC; RFC 2109 <10>:                    http cookiejar --- HTTP 客戶端的 Cookie 處理.
                                                             (line  141)
* RFC; RFC 2109 <11>:                    DefaultCookiePolicy 物件.
                                                             (line   86)
* RFC; RFC 2109 <12>:                    Cookie 物件<2>.     (line   11)
* RFC; RFC 2109 <13>:                    Cookie 物件<2>.     (line   23)
* RFC; RFC 2109 <14>:                    Cookie 物件<2>.     (line   74)
* RFC; RFC 2183:                         email --- 郵件和 MIME 處理套件.
                                                             (line   16)
* RFC; RFC 2183 <1>:                     email message：表示電子郵件訊息.
                                                             (line  457)
* RFC; RFC 2183 <2>:                     email message Message Representing an email message using the compat32 API.
                                                             (line  630)
* RFC; RFC 2231:                         Library<6>.         (line  135)
* RFC; RFC 2231 <1>:                     email --- 郵件和 MIME 處理套件.
                                                             (line   16)
* RFC; RFC 2231 <2>:                     email message：表示電子郵件訊息.
                                                             (line  278)
* RFC; RFC 2231 <3>:                     email message：表示電子郵件訊息.
                                                             (line  281)
* RFC; RFC 2231 <4>:                     email message：表示電子郵件訊息.
                                                             (line  363)
* RFC; RFC 2231 <5>:                     email message Message Representing an email message using the compat32 API.
                                                             (line  383)
* RFC; RFC 2231 <6>:                     email message Message Representing an email message using the compat32 API.
                                                             (line  387)
* RFC; RFC 2231 <7>:                     email message Message Representing an email message using the compat32 API.
                                                             (line  489)
* RFC; RFC 2231 <8>:                     email message Message Representing an email message using the compat32 API.
                                                             (line  497)
* RFC; RFC 2231 <9>:                     email message Message Representing an email message using the compat32 API.
                                                             (line  531)
* RFC; RFC 2231 <10>:                    email header：國際化標頭.
                                                             (line   32)
* RFC; RFC 2231 <11>:                    email utils：雜項工具.
                                                             (line  189)
* RFC; RFC 2231 <12>:                    email utils：雜項工具.
                                                             (line  193)
* RFC; RFC 2231 <13>:                    email utils：雜項工具.
                                                             (line  202)
* RFC; RFC 2231 <14>:                    email utils：雜項工具.
                                                             (line  209)
* RFC; RFC 2231 <15>:                    email utils：雜項工具.
                                                             (line  218)
* RFC; RFC 2295:                         HTTP 狀態碼.        (line  184)
* RFC; RFC 2324:                         HTTP 狀態碼.        (line  133)
* RFC; RFC 2342:                         New and Improved Modules<3>.
                                                             (line   94)
* RFC; RFC 2342 <1>:                     IMAP4 物件.         (line  164)
* RFC; RFC 2368:                         URL Quoting.        (line  177)
* RFC; RFC 2373:                         Address objects.    (line   95)
* RFC; RFC 2373 <1>:                     Address objects.    (line  161)
* RFC; RFC 2373 <2>:                     Address objects.    (line  170)
* RFC; RFC 2396:                         urllib parse<5>.    (line    6)
* RFC; RFC 2396 <1>:                     urllib<2>.          (line   24)
* RFC; RFC 2396 <2>:                     URL Parsing.        (line  257)
* RFC; RFC 2396 <3>:                     URL Quoting.        (line   25)
* RFC; RFC 2396 <4>:                     URL Quoting.        (line  172)
* RFC; RFC 2397:                         DataHandler 物件.   (line    9)
* RFC; RFC 2449:                         POP3 物件.          (line   26)
* RFC; RFC 2487:                         New and Improved Modules<3>.
                                                             (line   86)
* RFC; RFC 2518:                         HTTP 狀態碼.        (line   19)
* RFC; RFC 2595:                         poplib --- POP3 協定用戶端.
                                                             (line   14)
* RFC; RFC 2595 <1>:                     POP3 物件.          (line  116)
* RFC; RFC 2616:                         PEP 3333 Python Web Server Gateway Interface v1 0 1.
                                                             (line   20)
* RFC; RFC 2616 <1>:                     wsgiref util -- WSGI 環境工具.
                                                             (line   95)
* RFC; RFC 2616 <2>:                     wsgiref validate --- WSGI 符合性檢查.
                                                             (line   21)
* RFC; RFC 2616 <3>:                     HTTPRedirectHandler 物件.
                                                             (line    8)
* RFC; RFC 2616 <4>:                     HTTPRedirectHandler 物件.
                                                             (line   28)
* RFC; RFC 2616 <5>:                     Legacy interface.   (line  162)
* RFC; RFC 2616 <6>:                     urllib error --- urllib request 引發的例外類別.
                                                             (line   41)
* RFC; RFC 2616 <7>:                     簡介<13>.           (line   29)
* RFC; RFC 2616 <8>:                     HTTPError.          (line   15)
* RFC; RFC 2616 <9>:                     Error Codes.        (line   12)
* RFC; RFC 2616#section-14.23:           HTTPConnection 物件.
                                                             (line   31)
* RFC; RFC 2616#section-5.1.2:           HTTPConnection 物件.
                                                             (line   13)
* RFC; RFC 2616#section-5.1.2 <1>:       HTTPConnection 物件.
                                                             (line   32)
* RFC; RFC 2640:                         Changes in the Python API<2>.
                                                             (line   36)
* RFC; RFC 2640 <1>:                     Tests<36>.          (line   22)
* RFC; RFC 2640 <2>:                     ftplib --- FTP 協定用戶端.
                                                             (line   16)
* RFC; RFC 2640 <3>:                     FTP 物件.           (line   60)
* RFC; RFC 2640 <4>:                     FTP_TLS 物件.       (line   62)
* RFC; RFC 2732:                         urllib parse<6>.    (line   10)
* RFC; RFC 2732 <1>:                     New and Improved Modules.
                                                             (line  643)
* RFC; RFC 2732 <2>:                     URL Quoting.        (line  168)
* RFC; RFC 2774:                         HTTP 狀態碼.        (line  194)
* RFC; RFC 2818:                         ssl<12>.            (line   16)
* RFC; RFC 2821:                         email --- 郵件和 MIME 處理套件.
                                                             (line   12)
* RFC; RFC 2822:                         New and Improved Modules<3>.
                                                             (line   98)
* RFC; RFC 2822 <1>:                     標準模組庫.         (line   13)
* RFC; RFC 2822 <2>:                     函式<4>.            (line  652)
* RFC; RFC 2822 <3>:                     函式<4>.            (line  663)
* RFC; RFC 2822 <4>:                     函式<4>.            (line  384)
* RFC; RFC 2822 <5>:                     函式<4>.            (line  678)
* RFC; RFC 2822 <6>:                     email message Message Representing an email message using the compat32 API.
                                                             (line  273)
* RFC; RFC 2822 <7>:                     email header：國際化標頭.
                                                             (line   20)
* RFC; RFC 2822 <8>:                     email header：國際化標頭.
                                                             (line   23)
* RFC; RFC 2822 <9>:                     email header：國際化標頭.
                                                             (line   31)
* RFC; RFC 2822 <10>:                    email header：國際化標頭.
                                                             (line   88)
* RFC; RFC 2822 <11>:                    email header：國際化標頭.
                                                             (line  116)
* RFC; RFC 2822 <12>:                    email header：國際化標頭.
                                                             (line  134)
* RFC; RFC 2822 <13>:                    email utils：雜項工具.
                                                             (line   29)
* RFC; RFC 2822 <14>:                    email utils：雜項工具.
                                                             (line  109)
* RFC; RFC 2822 <15>:                    email utils：雜項工具.
                                                             (line  112)
* RFC; RFC 2822 <16>:                    email utils：雜項工具.
                                                             (line  239)
* RFC; RFC 2822 <17>:                    email utils：雜項工具.
                                                             (line  155)
* RFC; RFC 2822 <18>:                    Message 物件.       (line   17)
* RFC; RFC 2822 <19>:                    http client --- HTTP 協定用戶端.
                                                             (line  114)
* RFC; RFC 2822 <20>:                    http server — HTTP 伺服器.
                                                             (line  116)
* RFC; RFC 2964:                         http cookiejar --- HTTP 客戶端的 Cookie 處理.
                                                             (line  154)
* RFC; RFC 2965:                         urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  204)
* RFC; RFC 2965 <1>:                     urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  209)
* RFC; RFC 2965 <2>:                     Request Objects.    (line   50)
* RFC; RFC 2965 <3>:                     http cookiejar --- HTTP 客戶端的 Cookie 處理.
                                                             (line   16)
* RFC; RFC 2965 <4>:                     http cookiejar --- HTTP 客戶端的 Cookie 處理.
                                                             (line  102)
* RFC; RFC 2965 <5>:                     http cookiejar --- HTTP 客戶端的 Cookie 處理.
                                                             (line  114)
* RFC; RFC 2965 <6>:                     http cookiejar --- HTTP 客戶端的 Cookie 處理.
                                                             (line  143)
* RFC; RFC 2965 <7>:                     http cookiejar --- HTTP 客戶端的 Cookie 處理.
                                                             (line  145)
* RFC; RFC 2965 <8>:                     http cookiejar --- HTTP 客戶端的 Cookie 處理.
                                                             (line  152)
* RFC; RFC 2965 <9>:                     FileCookieJar subclasses and co-operation with web browsers.
                                                             (line   16)
* RFC; RFC 2965 <10>:                    CookiePolicy 物件.  (line   74)
* RFC; RFC 2965 <11>:                    CookiePolicy 物件.  (line   79)
* RFC; RFC 2965 <12>:                    DefaultCookiePolicy 物件.
                                                             (line    8)
* RFC; RFC 2965 <13>:                    DefaultCookiePolicy 物件.
                                                             (line   90)
* RFC; RFC 2965 <14>:                    DefaultCookiePolicy 物件.
                                                             (line  101)
* RFC; RFC 2965 <15>:                    DefaultCookiePolicy 物件.
                                                             (line  105)
* RFC; RFC 2965 <16>:                    DefaultCookiePolicy 物件.
                                                             (line  114)
* RFC; RFC 2965 <17>:                    DefaultCookiePolicy 物件.
                                                             (line  151)
* RFC; RFC 2965 <18>:                    Cookie 物件<2>.     (line   23)
* RFC; RFC 2965 <19>:                    範例<40>.           (line   25)
* RFC; RFC 3056:                         Address objects.    (line  305)
* RFC; RFC 3164:                         Logging to syslog with RFC5424 support.
                                                             (line    7)
* RFC; RFC 3171:                         Address objects.    (line   94)
* RFC; RFC 3207:                         New and Improved Modules<2>.
                                                             (line  572)
* RFC; RFC 3229:                         HTTP 狀態碼.        (line   52)
* RFC; RFC 3280:                         SSL Sockets.        (line  143)
* RFC; RFC 3330:                         Address objects.    (line  169)
* RFC; RFC 3339:                         Displaying the date/time in messages.
                                                             (line   18)
* RFC; RFC 3454:                         Security<13>.       (line   19)
* RFC; RFC 3454 <1>:                     stringprep --- 網際網路字串準備.
                                                             (line   17)
* RFC; RFC 3454 <2>:                     stringprep --- 網際網路字串準備.
                                                             (line   26)
* RFC; RFC 3490:                         Text Encodings.     (line   14)
* RFC; RFC 3490 <1>:                     encodings idna --- Internationalized Domain Names in Applications.
                                                             (line    6)
* RFC; RFC 3490 <2>:                     encodings idna --- Internationalized Domain Names in Applications.
                                                             (line   57)
* RFC; RFC 3490 <3>:                     encodings idna --- Internationalized Domain Names in Applications.
                                                             (line   62)
* RFC; RFC 3490#section-3.1:             encodings idna --- Internationalized Domain Names in Applications.
                                                             (line   27)
* RFC; RFC 3491:                         Security<13>.       (line   21)
* RFC; RFC 3492:                         Text Encodings.     (line   36)
* RFC; RFC 3492 <1>:                     encodings idna --- Internationalized Domain Names in Applications.
                                                             (line    7)
* RFC; RFC 3493:                         範例<25>.           (line  227)
* RFC; RFC 3501:                         IMAP4 物件.         (line  328)
* RFC; RFC 3542:                         Library<48>.        (line  351)
* RFC; RFC 3542 <1>:                     其他函式<2>.        (line  312)
* RFC; RFC 3548:                         New Improved and Deprecated Modules<3>.
                                                             (line   16)
* RFC; RFC 3548 <1>:                     binascii --- 在二進位制和 ASCII 之間轉換.
                                                             (line   50)
* RFC; RFC 3548 <2>:                     binascii --- 在二進位制和 ASCII 之間轉換.
                                                             (line   65)
* RFC; RFC 3596#section-2.5:             Library.            (line   14)
* RFC; RFC 3659:                         FTP 物件.           (line  252)
* RFC; RFC 3879:                         Address objects.    (line  283)
* RFC; RFC 3927:                         Address objects.    (line  174)
* RFC; RFC 3986:                         urllib parse.       (line   17)
* RFC; RFC 3986 <1>:                     urllib parse<3>.    (line    7)
* RFC; RFC 3986 <2>:                     urllib parse<4>.    (line    7)
* RFC; RFC 3986 <3>:                     urllib parse<5>.    (line    6)
* RFC; RFC 3986 <4>:                     urllib<2>.          (line   22)
* RFC; RFC 3986 <5>:                     New and Improved Modules.
                                                             (line  622)
* RFC; RFC 3986 <6>:                     Porting to Python 2 7.
                                                             (line   80)
* RFC; RFC 3986 <7>:                     urllib parse --- 將 URL 剖析成元件.
                                                             (line   34)
* RFC; RFC 3986 <8>:                     URL Parsing.        (line  142)
* RFC; RFC 3986 <9>:                     URL Parsing.        (line  368)
* RFC; RFC 3986 <10>:                    URL parsing security.
                                                             (line   25)
* RFC; RFC 3986 <11>:                    URL Quoting.        (line   25)
* RFC; RFC 3986 <12>:                    URL Quoting.        (line  160)
* RFC; RFC 3986 <13>:                    http server — HTTP 伺服器.
                                                             (line  101)
* RFC; RFC 4007:                         Address objects.    (line  226)
* RFC; RFC 4007 <1>:                     Address objects.    (line  297)
* RFC; RFC 4086:                         TLS 1 3.            (line   45)
* RFC; RFC 4122:                         New Improved and Removed Modules.
                                                             (line  415)
* RFC; RFC 4122 <1>:                     New Improved and Removed Modules.
                                                             (line  420)
* RFC; RFC 4122 <2>:                     uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line    6)
* RFC; RFC 4122 <3>:                     uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line   14)
* RFC; RFC 4122 <4>:                     uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line   68)
* RFC; RFC 4122 <5>:                     uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  131)
* RFC; RFC 4122 <6>:                     uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  157)
* RFC; RFC 4122 <7>:                     uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  217)
* RFC; RFC 4122 <8>:                     uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  230)
* RFC; RFC 4180:                         csv --- CSV 檔案讀取及寫入.
                                                             (line   11)
* RFC; RFC 4193:                         Address objects.    (line  285)
* RFC; RFC 4217:                         FTP_TLS 物件.       (line   11)
* RFC; RFC 4291:                         Library<12>.        (line 1075)
* RFC; RFC 4291 <1>:                     Library<28>.        (line  653)
* RFC; RFC 4291 <2>:                     Address objects.    (line  180)
* RFC; RFC 4291 <3>:                     Address objects.    (line  220)
* RFC; RFC 4380:                         Address objects.    (line  312)
* RFC; RFC 4627:                         json --- JSON 編碼器與解碼器.
                                                             (line   11)
* RFC; RFC 4627 <1>:                     位於頂層的非物件及非列表值.
                                                             (line    6)
* RFC; RFC 4648:                         Documentation<23>.  (line   32)
* RFC; RFC 4648 <1>:                     base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   11)
* RFC; RFC 4648 <2>:                     base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   14)
* RFC; RFC 4648 <3>:                     base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   20)
* RFC; RFC 4648 <4>:                     base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  106)
* RFC; RFC 4648 <5>:                     base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  117)
* RFC; RFC 4648 <6>:                     base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  124)
* RFC; RFC 4648 <7>:                     安全性注意事項<2>.  (line    6)
* RFC; RFC 4648 <8>:                     安全性注意事項<4>.  (line    8)
* RFC; RFC 4918:                         HTTP 狀態碼.        (line   46)
* RFC; RFC 4918 <1>:                     HTTP 狀態碼.        (line  142)
* RFC; RFC 4918 <2>:                     HTTP 狀態碼.        (line  145)
* RFC; RFC 4918 <3>:                     HTTP 狀態碼.        (line  188)
* RFC; RFC 4954:                         SMTP 物件.          (line  135)
* RFC; RFC 4954 <1>:                     SMTP 物件.          (line  157)
* RFC; RFC 5161:                         imaplib<2>.         (line   11)
* RFC; RFC 5161 <1>:                     IMAP4 物件.         (line   86)
* RFC; RFC 5246:                         常數<8>.            (line  457)
* RFC; RFC 5246 <1>:                     TLS 1 3.            (line   53)
* RFC; RFC 5280:                         ssl.                (line   10)
* RFC; RFC 5280 <1>:                     Other Changes.      (line   20)
* RFC; RFC 5280 <2>:                     Changes in the Python API<7>.
                                                             (line   95)
* RFC; RFC 5280 <3>:                     語境建立.           (line   34)
* RFC; RFC 5280 <4>:                     語境建立.           (line   55)
* RFC; RFC 5280 <5>:                     認證處理.           (line   22)
* RFC; RFC 5280 <6>:                     TLS 1 3.            (line   49)
* RFC; RFC 5321:                         smtpd<4>.           (line    6)
* RFC; RFC 5321 <1>:                     email headerregistry：自訂標頭物件.
                                                             (line  452)
* RFC; RFC 5322:                         email --- 郵件和 MIME 處理套件.
                                                             (line   14)
* RFC; RFC 5322 <1>:                     email message：表示電子郵件訊息.
                                                             (line   20)
* RFC; RFC 5322 <2>:                     email message：表示電子郵件訊息.
                                                             (line   31)
* RFC; RFC 5322 <3>:                     Parser API.         (line   41)
* RFC; RFC 5322 <4>:                     email generator：產生 MIME 文件.
                                                             (line  101)
* RFC; RFC 5322 <5>:                     email generator：產生 MIME 文件.
                                                             (line  194)
* RFC; RFC 5322 <6>:                     email policy Policy Objects.
                                                             (line  149)
* RFC; RFC 5322 <7>:                     email policy Policy Objects.
                                                             (line  343)
* RFC; RFC 5322 <8>:                     email policy Policy Objects.
                                                             (line  364)
* RFC; RFC 5322 <9>:                     email policy Policy Objects.
                                                             (line  370)
* RFC; RFC 5322 <10>:                    email policy Policy Objects.
                                                             (line  382)
* RFC; RFC 5322 <11>:                    email policy Policy Objects.
                                                             (line  415)
* RFC; RFC 5322 <12>:                    email errors：例外和缺陷類別.
                                                             (line   28)
* RFC; RFC 5322 <13>:                    email headerregistry：自訂標頭物件.
                                                             (line   16)
* RFC; RFC 5322 <14>:                    email headerregistry：自訂標頭物件.
                                                             (line  117)
* RFC; RFC 5322 <15>:                    email headerregistry：自訂標頭物件.
                                                             (line  122)
* RFC; RFC 5322 <16>:                    email headerregistry：自訂標頭物件.
                                                             (line  123)
* RFC; RFC 5322 <17>:                    email headerregistry：自訂標頭物件.
                                                             (line  138)
* RFC; RFC 5322 <18>:                    email headerregistry：自訂標頭物件.
                                                             (line  159)
* RFC; RFC 5322 <19>:                    email headerregistry：自訂標頭物件.
                                                             (line  415)
* RFC; RFC 5322 <20>:                    email headerregistry：自訂標頭物件.
                                                             (line  449)
* RFC; RFC 5322 <21>:                    email headerregistry：自訂標頭物件.
                                                             (line  482)
* RFC; RFC 5322 <22>:                    email message Message Representing an email message using the compat32 API.
                                                             (line   21)
* RFC; RFC 5322 <23>:                    SMTP 物件.          (line  313)
* RFC; RFC 5424:                         SysLogHandler.      (line   71)
* RFC; RFC 5424 <1>:                     Inserting a BOM into messages sent to a SysLogHandler.
                                                             (line    6)
* RFC; RFC 5424 <2>:                     Inserting a BOM into messages sent to a SysLogHandler.
                                                             (line   19)
* RFC; RFC 5424 <3>:                     Inserting a BOM into messages sent to a SysLogHandler.
                                                             (line   43)
* RFC; RFC 5424 <4>:                     Logging to syslog with RFC5424 support.
                                                             (line    6)
* RFC; RFC 5424#section-6:               Inserting a BOM into messages sent to a SysLogHandler.
                                                             (line    9)
* RFC; RFC 5735:                         Address objects.    (line  160)
* RFC; RFC 5789:                         HTTP 方法.          (line   37)
* RFC; RFC 5842:                         HTTP 狀態碼.        (line   49)
* RFC; RFC 5842 <1>:                     HTTP 狀態碼.        (line  191)
* RFC; RFC 5891:                         encodings idna --- Internationalized Domain Names in Applications.
                                                             (line   11)
* RFC; RFC 5894:                         Security<13>.       (line   20)
* RFC; RFC 5895:                         encodings idna --- Internationalized Domain Names in Applications.
                                                             (line   11)
* RFC; RFC 5929:                         SSL Sockets.        (line  253)
* RFC; RFC 6066:                         常數<8>.            (line  361)
* RFC; RFC 6066 <1>:                     SSL Contexts.       (line  293)
* RFC; RFC 6066 <2>:                     TLS 1 3.            (line   57)
* RFC; RFC 6152:                         smtpd<2>.           (line   15)
* RFC; RFC 6531:                         email<3>.           (line   19)
* RFC; RFC 6531 <1>:                     smtpd<2>.           (line   21)
* RFC; RFC 6531 <2>:                     smtplib<2>.         (line   15)
* RFC; RFC 6531 <3>:                     email message：表示電子郵件訊息.
                                                             (line  102)
* RFC; RFC 6531 <4>:                     email policy Policy Objects.
                                                             (line  386)
* RFC; RFC 6531 <5>:                     smtplib --- SMTP 協定用戶端.
                                                             (line   67)
* RFC; RFC 6532:                         email<3>.           (line   18)
* RFC; RFC 6532 <1>:                     email --- 郵件和 MIME 處理套件.
                                                             (line   14)
* RFC; RFC 6532 <2>:                     email message：表示電子郵件訊息.
                                                             (line   20)
* RFC; RFC 6532 <3>:                     Parser API.         (line   42)
* RFC; RFC 6532 <4>:                     email policy Policy Objects.
                                                             (line  384)
* RFC; RFC 6585:                         HTTP 狀態碼.        (line  154)
* RFC; RFC 6585 <1>:                     HTTP 狀態碼.        (line  157)
* RFC; RFC 6585 <2>:                     HTTP 狀態碼.        (line  160)
* RFC; RFC 6585 <3>:                     HTTP 狀態碼.        (line  197)
* RFC; RFC 6855:                         imaplib<2>.         (line   12)
* RFC; RFC 6855 <1>:                     imaplib<2>.         (line   14)
* RFC; RFC 6855 <2>:                     IMAP4 物件.         (line   88)
* RFC; RFC 6855 <3>:                     IMAP4 物件.         (line   90)
* RFC; RFC 6856:                         poplib<2>.          (line    6)
* RFC; RFC 6856 <1>:                     POP3 物件.          (line  109)
* RFC; RFC 7159:                         json --- JSON 編碼器與解碼器.
                                                             (line   10)
* RFC; RFC 7159 <1>:                     合規性與互通性（Interoperability）.
                                                             (line    6)
* RFC; RFC 7159 <2>:                     位於頂層的非物件及非列表值.
                                                             (line    8)
* RFC; RFC 7230:                         urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  176)
* RFC; RFC 7230 <1>:                     HTTPConnection 物件.
                                                             (line  191)
* RFC; RFC 7301:                         Application-Layer Protocol Negotiation Support.
                                                             (line   10)
* RFC; RFC 7301 <1>:                     常數<8>.            (line  340)
* RFC; RFC 7301 <2>:                     SSL Contexts.       (line  261)
* RFC; RFC 7525:                         TLS 1 3.            (line   65)
* RFC; RFC 7538:                         Library<27>.        (line  171)
* RFC; RFC 7693:                         BLAKE2.             (line    6)
* RFC; RFC 7725:                         HTTP 狀態碼.        (line  163)
* RFC; RFC 7914:                         密鑰的生成.         (line   46)
* RFC; RFC 8089:                         Parsing and generating URIs.
                                                             (line    7)
* RFC; RFC 821:                          smtplib --- SMTP 協定用戶端.
                                                             (line   12)
* RFC; RFC 821 <1>:                      smtplib --- SMTP 協定用戶端.
                                                             (line  185)
* RFC; RFC 822:                          New and Improved Modules<3>.
                                                             (line   98)
* RFC; RFC 822 <1>:                      函式<4>.            (line  645)
* RFC; RFC 822 <2>:                      函式<4>.            (line  648)
* RFC; RFC 822 <3>:                      函式<4>.            (line  656)
* RFC; RFC 822 <4>:                      函式<4>.            (line  659)
* RFC; RFC 822 <5>:                      函式<4>.            (line  671)
* RFC; RFC 822 <6>:                      函式<4>.            (line  674)
* RFC; RFC 822 <7>:                      email：範例.        (line   36)
* RFC; RFC 822 <8>:                      email header：國際化標頭.
                                                             (line   21)
* RFC; RFC 822 <9>:                      HTTPConnection 物件.
                                                             (line  178)
* RFC; RFC 822 <10>:                     SMTP 物件.          (line   94)
* RFC; RFC 822 <11>:                     SMTP 物件.          (line  228)
* RFC; RFC 822 <12>:                     SMTP 物件.          (line  229)
* RFC; RFC 822 <13>:                     SMTP 範例.          (line   10)
* RFC; RFC 822 <14>:                     The GNUTranslations class.
                                                             (line   13)
* RFC; RFC 8297:                         HTTP 狀態碼.        (line   22)
* RFC; RFC 8305:                         打開網路連線.       (line   63)
* RFC; RFC 8305 <1>:                     打開網路連線.       (line   69)
* RFC; RFC 8470:                         HTTP 狀態碼.        (line  148)
* RFC; RFC 9110:                         HTTP 狀態碼.        (line   13)
* RFC; RFC 9110 <1>:                     HTTP 狀態碼.        (line   16)
* RFC; RFC 9110 <2>:                     HTTP 狀態碼.        (line   25)
* RFC; RFC 9110 <3>:                     HTTP 狀態碼.        (line   28)
* RFC; RFC 9110 <4>:                     HTTP 狀態碼.        (line   31)
* RFC; RFC 9110 <5>:                     HTTP 狀態碼.        (line   34)
* RFC; RFC 9110 <6>:                     HTTP 狀態碼.        (line   37)
* RFC; RFC 9110 <7>:                     HTTP 狀態碼.        (line   40)
* RFC; RFC 9110 <8>:                     HTTP 狀態碼.        (line   43)
* RFC; RFC 9110 <9>:                     HTTP 狀態碼.        (line   55)
* RFC; RFC 9110 <10>:                    HTTP 狀態碼.        (line   58)
* RFC; RFC 9110 <11>:                    HTTP 狀態碼.        (line   61)
* RFC; RFC 9110 <12>:                    HTTP 狀態碼.        (line   64)
* RFC; RFC 9110 <13>:                    HTTP 狀態碼.        (line   67)
* RFC; RFC 9110 <14>:                    HTTP 狀態碼.        (line   70)
* RFC; RFC 9110 <15>:                    HTTP 狀態碼.        (line   73)
* RFC; RFC 9110 <16>:                    HTTP 狀態碼.        (line   76)
* RFC; RFC 9110 <17>:                    HTTP 狀態碼.        (line   79)
* RFC; RFC 9110 <18>:                    HTTP 狀態碼.        (line   82)
* RFC; RFC 9110 <19>:                    HTTP 狀態碼.        (line   85)
* RFC; RFC 9110 <20>:                    HTTP 狀態碼.        (line   88)
* RFC; RFC 9110 <21>:                    HTTP 狀態碼.        (line   91)
* RFC; RFC 9110 <22>:                    HTTP 狀態碼.        (line   94)
* RFC; RFC 9110 <23>:                    HTTP 狀態碼.        (line   97)
* RFC; RFC 9110 <24>:                    HTTP 狀態碼.        (line  100)
* RFC; RFC 9110 <25>:                    HTTP 狀態碼.        (line  103)
* RFC; RFC 9110 <26>:                    HTTP 狀態碼.        (line  106)
* RFC; RFC 9110 <27>:                    HTTP 狀態碼.        (line  109)
* RFC; RFC 9110 <28>:                    HTTP 狀態碼.        (line  112)
* RFC; RFC 9110 <29>:                    HTTP 狀態碼.        (line  115)
* RFC; RFC 9110 <30>:                    HTTP 狀態碼.        (line  118)
* RFC; RFC 9110 <31>:                    HTTP 狀態碼.        (line  121)
* RFC; RFC 9110 <32>:                    HTTP 狀態碼.        (line  124)
* RFC; RFC 9110 <33>:                    HTTP 狀態碼.        (line  127)
* RFC; RFC 9110 <34>:                    HTTP 狀態碼.        (line  130)
* RFC; RFC 9110 <35>:                    HTTP 狀態碼.        (line  136)
* RFC; RFC 9110 <36>:                    HTTP 狀態碼.        (line  139)
* RFC; RFC 9110 <37>:                    HTTP 狀態碼.        (line  151)
* RFC; RFC 9110 <38>:                    HTTP 狀態碼.        (line  166)
* RFC; RFC 9110 <39>:                    HTTP 狀態碼.        (line  169)
* RFC; RFC 9110 <40>:                    HTTP 狀態碼.        (line  172)
* RFC; RFC 9110 <41>:                    HTTP 狀態碼.        (line  175)
* RFC; RFC 9110 <42>:                    HTTP 狀態碼.        (line  178)
* RFC; RFC 9110 <43>:                    HTTP 狀態碼.        (line  181)
* RFC; RFC 9110 <44>:                    HTTP 狀態分類.      (line   15)
* RFC; RFC 9110 <45>:                    HTTP 狀態分類.      (line   18)
* RFC; RFC 9110 <46>:                    HTTP 狀態分類.      (line   21)
* RFC; RFC 9110 <47>:                    HTTP 狀態分類.      (line   24)
* RFC; RFC 9110 <48>:                    HTTP 狀態分類.      (line   27)
* RFC; RFC 9110 <49>:                    HTTP 方法.          (line   13)
* RFC; RFC 9110 <50>:                    HTTP 方法.          (line   16)
* RFC; RFC 9110 <51>:                    HTTP 方法.          (line   19)
* RFC; RFC 9110 <52>:                    HTTP 方法.          (line   22)
* RFC; RFC 9110 <53>:                    HTTP 方法.          (line   25)
* RFC; RFC 9110 <54>:                    HTTP 方法.          (line   28)
* RFC; RFC 9110 <55>:                    HTTP 方法.          (line   31)
* RFC; RFC 9110 <56>:                    HTTP 方法.          (line   34)
* RFC; RFC 9239:                         Library<20>.        (line   76)
* RFC; RFC 959:                          ftplib --- FTP 協定用戶端.
                                                             (line   14)
* rfc2109 (http.cookiejar.Cookie 的屬性): Cookie 物件<2>.    (line   72)
* rfc2109_as_netscape (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy 物件.
                                                             (line   83)
* rfc2965 (http.cookiejar.CookiePolicy 的屬性): CookiePolicy 物件.
                                                             (line   72)
* rfile (http.server.BaseHTTPRequestHandler 的屬性): http server — HTTP 伺服器.
                                                             (line  118)
* rfile (socketserver.DatagramRequestHandler 的屬性): Request Handler Objects.
                                                             (line   63)
* rfind() (bytearray 的方法):            Bytes and Bytearray Operations.
                                                             (line  212)
* rfind() (bytes 的方法):                Bytes and Bytearray Operations.
                                                             (line  212)
* rfind() (mmap.mmap 的方法):            mmap --- 記憶體映射檔案的支援.
                                                             (line  283)
* rfind() (str 的方法):                  String Methods<2>.  (line  404)
* rgb_to_hls() (於 colorsys 模組中):     colorsys --- 顏色系統間的轉換.
                                                             (line   33)
* rgb_to_hsv() (於 colorsys 模組中):     colorsys --- 顏色系統間的轉換.
                                                             (line   41)
* rgb_to_yiq() (於 colorsys 模組中):     colorsys --- 顏色系統間的轉換.
                                                             (line   25)
* rglob() (pathlib.Path 的方法):         讀取目錄.           (line   74)
* richcmpfunc (C type):                  Slot Type typedefs. (line   83)
* right (filecmp.dircmp 的屬性):         The dircmp class.   (line   48)
* right_list (filecmp.dircmp 的屬性):    The dircmp class.   (line   57)
* right_only (filecmp.dircmp 的屬性):    The dircmp class.   (line   70)
* right() (於 turtle 模組中):            Turtle motion.      (line   40)
* RIGHTSHIFT (於 token 模組中):          token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  162)
* RIGHTSHIFTEQUAL (於 token 模組中):     token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  206)
* rindex() (bytearray 的方法):           Bytes and Bytearray Operations.
                                                             (line  226)
* rindex() (bytes 的方法):               Bytes and Bytearray Operations.
                                                             (line  226)
* rindex() (str 的方法):                 String Methods<2>.  (line  411)
* rjust() (bytearray 的方法):            Bytes and Bytearray Operations.
                                                             (line  342)
* rjust() (bytes 的方法):                Bytes and Bytearray Operations.
                                                             (line  342)
* rjust() (str 的方法):                  String Methods<2>.  (line  416)
* RLIM_INFINITY (於 resource 模組中):    Resource Limits.    (line   20)
* RLIMIT_AS (於 resource 模組中):        Resource Limits.    (line  148)
* RLIMIT_CORE (於 resource 模組中):      Resource Limits.    (line   91)
* RLIMIT_CPU (於 resource 模組中):       Resource Limits.    (line   98)
* RLIMIT_DATA (於 resource 模組中):      Resource Limits.    (line  110)
* RLIMIT_FSIZE (於 resource 模組中):     Resource Limits.    (line  106)
* RLIMIT_KQUEUES (於 resource 模組中):   Resource Limits.    (line  224)
* RLIMIT_MEMLOCK (於 resource 模組中):   Resource Limits.    (line  138)
* RLIMIT_MSGQUEUE (於 resource 模組中):  Resource Limits.    (line  153)
* RLIMIT_NICE (於 resource 模組中):      Resource Limits.    (line  161)
* RLIMIT_NOFILE (於 resource 模組中):    Resource Limits.    (line  129)
* RLIMIT_NPROC (於 resource 模組中):     Resource Limits.    (line  125)
* RLIMIT_NPTS (於 resource 模組中):      Resource Limits.    (line  216)
* RLIMIT_OFILE (於 resource 模組中):     Resource Limits.    (line  134)
* RLIMIT_RSS (於 resource 模組中):       Resource Limits.    (line  120)
* RLIMIT_RTPRIO (於 resource 模組中):    Resource Limits.    (line  170)
* RLIMIT_RTTIME (於 resource 模組中):    Resource Limits.    (line  178)
* RLIMIT_SBSIZE (於 resource 模組中):    Resource Limits.    (line  195)
* RLIMIT_SIGPENDING (於 resource 模組中): Resource Limits.   (line  187)
* RLIMIT_STACK (於 resource 模組中):     Resource Limits.    (line  114)
* RLIMIT_SWAP (於 resource 模組中):      Resource Limits.    (line  205)
* RLIMIT_VMEM (於 resource 模組中):      Resource Limits.    (line  142)
* RLock (multiprocessing 中的類別):      Synchronization primitives.
                                                             (line  101)
* RLock (threading 中的類別):            RLock 物件.         (line   32)
* RLock() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  202)
* rmd() (ftplib.FTP 的方法):             FTP 物件.           (line  305)
* rmdir() (pathlib.Path 的方法):         Renaming and deleting.
                                                             (line   54)
* rmdir() (於 os 模組中):                Files and Directories.
                                                             (line  812)
* rmdir() (於 test.support.os_helper 模組中): test support os_helper --- 用於 os 測試的工具.
                                                             (line  110)
* rmtree() (於 shutil 模組中):           Directory and files operations.
                                                             (line  263)
* rmtree() (於 test.support.os_helper 模組中): test support os_helper --- 用於 os 測試的工具.
                                                             (line  117)
* RobotFileParser (urllib.robotparser 中的類別): urllib robotparser --- robots txt 的剖析器.
                                                             (line   15)
* robots.txt:                            urllib robotparser --- robots txt 的剖析器.
                                                             (line    8)
* rollback() (sqlite3.Connection 的方法): Connection 物件.   (line   80)
* rollover() (tempfile.SpooledTemporaryFile 的方法): tempfile --- 生成臨時檔案和目錄.
                                                             (line  137)
* ROMAN (於 tkinter.font 模組中):        tkinter font --- Tkinter 字型包裝器.
                                                             (line   15)
* root (pathlib.PurePath 的屬性):        方法與屬性.         (line   32)
* rotate() (collections.deque 的方法):   deque 物件.         (line  100)
* rotate() (decimal.Context 的方法):     Context objects.    (line  500)
* rotate() (decimal.Decimal 的方法):     Decimal objects.    (line  528)
* rotate() (logging.handlers.BaseRotatingHandler 的方法): BaseRotatingHandler.
                                                             (line   74)
* RotatingFileHandler (logging.handlers 中的類別): RotatingFileHandler.
                                                             (line    9)
* rotation_filename() (logging.handlers.BaseRotatingHandler 的方法): BaseRotatingHandler.
                                                             (line   58)
* rotator (logging.handlers.BaseRotatingHandler 的屬性): BaseRotatingHandler.
                                                             (line   49)
* ROUND_05UP (於 decimal 模組中):        Rounding modes.     (line   34)
* ROUND_CEILING (於 decimal 模組中):     Rounding modes.     (line    6)
* ROUND_DOWN (於 decimal 模組中):        Rounding modes.     (line   10)
* ROUND_FLOOR (於 decimal 模組中):       Rounding modes.     (line   14)
* ROUND_HALF_DOWN (於 decimal 模組中):   Rounding modes.     (line   18)
* ROUND_HALF_EVEN (於 decimal 模組中):   Rounding modes.     (line   22)
* ROUND_HALF_UP (於 decimal 模組中):     Rounding modes.     (line   26)
* ROUND_UP (於 decimal 模組中):          Rounding modes.     (line   30)
* Rounded (decimal 中的類別):            Signals.            (line   77)
* rounds (sys.float_info 的屬性):        sys --- 系統特定的參數與函式.
                                                             (line  664)
* Row (sqlite3 中的類別):                Row 物件.           (line    6)
* row_factory (sqlite3.Connection 的屬性): Connection 物件.  (line  791)
* row_factory (sqlite3.Cursor 的屬性):   Cursor 物件.        (line  225)
* rowcount (sqlite3.Cursor 的屬性):      Cursor 物件.        (line  214)
* RPAR (於 token 模組中):                token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   58)
* rpartition() (bytearray 的方法):       Bytes and Bytearray Operations.
                                                             (line  238)
* rpartition() (bytes 的方法):           Bytes and Bytearray Operations.
                                                             (line  238)
* rpartition() (str 的方法):             String Methods<2>.  (line  423)
* rpc_paths (xmlrpc.server.SimpleXMLRPCRequestHandler 的屬性): SimpleXMLRPCServer 物件.
                                                             (line   64)
* rpop() (poplib.POP3 的方法):           POP3 物件.          (line   47)
* RS (於 curses.ascii 模組中):           curses ascii --- ASCII 字元的工具程式.
                                                             (line  115)
* rset() (poplib.POP3 的方法):           POP3 物件.          (line   75)
* RShift (ast 中的類別):                 運算式<2>.          (line   52)
* rshift() (於 operator 模組中):         operator --- 標準運算子替代函式.
                                                             (line  142)
* rsplit() (bytearray 的方法):           Bytes and Bytearray Operations.
                                                             (line  354)
* rsplit() (bytes 的方法):               Bytes and Bytearray Operations.
                                                             (line  354)
* rsplit() (str 的方法):                 String Methods<2>.  (line  431)
* RSQB (於 token 模組中):                token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   66)
* rstrip() (bytearray 的方法):           Bytes and Bytearray Operations.
                                                             (line  365)
* rstrip() (bytes 的方法):               Bytes and Bytearray Operations.
                                                             (line  365)
* rstrip() (str 的方法):                 String Methods<2>.  (line  440)
* rt() (於 turtle 模組中):               Turtle motion.      (line   40)
* RTLD_DEEPBIND (於 os 模組中):          Miscellaneous System Information.
                                                             (line  164)
* RTLD_GLOBAL (於 os 模組中):            Miscellaneous System Information.
                                                             (line  164)
* RTLD_LAZY (於 os 模組中):              Miscellaneous System Information.
                                                             (line  164)
* RTLD_LOCAL (於 os 模組中):             Miscellaneous System Information.
                                                             (line  164)
* RTLD_NODELETE (於 os 模組中):          Miscellaneous System Information.
                                                             (line  164)
* RTLD_NOLOAD (於 os 模組中):            Miscellaneous System Information.
                                                             (line  164)
* RTLD_NOW (於 os 模組中):               Miscellaneous System Information.
                                                             (line  164)
* ruler (cmd.Cmd 的屬性):                Cmd 物件.           (line  172)
* run (pdb command):                     Debugger Commands.  (line  416)
* Run script（執行腳本）:                Format menu Editor window only.
                                                             (line   53)
* run_coroutine_threadsafe() (於 asyncio 模組中): Scheduling From Other Threads.
                                                             (line    6)
* run_docstring_examples() (於 doctest 模組中): 基礎 API.    (line  127)
* run_forever() (asyncio.loop 的方法):   啟動和停止迴圈.     (line   15)
* run_in_executor() (asyncio.loop 的方法): 在執行緒池或行程池中執行程式碼.
                                                             (line    6)
* run_in_subinterp() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  655)
* run_module() (於 runpy 模組中):        runpy --- 定位並執行 Python 模組.
                                                             (line   27)
* run_path() (於 runpy 模組中):          runpy --- 定位並執行 Python 模組.
                                                             (line   98)
* run_python_until_end() (於 test.support.script_helper 模組中): test support script_helper --- 用於 Python 執行測試的工具.
                                                             (line   29)
* run_script() (modulefinder.ModuleFinder 的方法): modulefinder --- 搜尋腳本所使用的模組.
                                                             (line   37)
* run_until_complete() (asyncio.loop 的方法): 啟動和停止迴圈.
                                                             (line    6)
* run_with_locale() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  459)
* run_with_tz() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  467)
* run() (asyncio.Runner 的方法):         Runner context manager.
                                                             (line   35)
* run() (bdb.Bdb 的方法):                bdb --- 偵錯器框架. (line  430)
* run() (contextvars.Context 的方法):    Manual Context Management.
                                                             (line   36)
* run() (doctest.DocTestRunner 的方法):  DocTestRunner 物件. (line  101)
* run() (multiprocessing.Process 的方法): Process 與例外.    (line   35)
* run() (pdb.Pdb 的方法):                pdb --- The Python Debugger.
                                                             (line  215)
* run() (profile.Profile 的方法):        profile and cProfile Module Reference.
                                                             (line  108)
* run() (sched.scheduler 的方法):        排程器物件.         (line   45)
* run() (threading.Thread 的方法):       Thread Objects.     (line  104)
* run() (trace.Trace 的方法):            Programmatic Interface.
                                                             (line   22)
* run() (unittest.IsolatedAsyncioTestCase 的方法): Test cases.
                                                             (line  897)
* run() (unittest.TestCase 的方法):      Test cases.         (line   83)
* run() (unittest.TestSuite 的方法):     Grouping tests.     (line   41)
* run() (unittest.TextTestRunner 的方法): Loading and running tests.
                                                             (line  506)
* run() (wsgiref.handlers.BaseHandler 的方法): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line   84)
* run() (於 asyncio 模組中):             運行一個 asyncio 程式.
                                                             (line    6)
* run() (於 pdb 模組中):                 pdb --- The Python Debugger.
                                                             (line  125)
* run() (於 profile 模組中):             profile and cProfile Module Reference.
                                                             (line    9)
* run() (於 subprocess 模組中):          Using the subprocess Module.
                                                             (line   11)
* runcall() (bdb.Bdb 的方法):            bdb --- 偵錯器框架. (line  447)
* runcall() (pdb.Pdb 的方法):            pdb --- The Python Debugger.
                                                             (line  215)
* runcall() (profile.Profile 的方法):    profile and cProfile Module Reference.
                                                             (line  117)
* runcall() (於 pdb 模組中):             pdb --- The Python Debugger.
                                                             (line  144)
* runcode() (code.InteractiveInterpreter 的方法): Interactive Interpreter Objects.
                                                             (line   33)
* runctx() (bdb.Bdb 的方法):             bdb --- 偵錯器框架. (line  442)
* runctx() (profile.Profile 的方法):     profile and cProfile Module Reference.
                                                             (line  112)
* runctx() (trace.Trace 的方法):         Programmatic Interface.
                                                             (line   28)
* runctx() (於 profile 模組中):          profile and cProfile Module Reference.
                                                             (line   23)
* runeval() (bdb.Bdb 的方法):            bdb --- 偵錯器框架. (line  436)
* runeval() (pdb.Pdb 的方法):            pdb --- The Python Debugger.
                                                             (line  215)
* runeval() (於 pdb 模組中):             pdb --- The Python Debugger.
                                                             (line  137)
* runfunc() (trace.Trace 的方法):        Programmatic Interface.
                                                             (line   35)
* Runner (asyncio 中的類別):             Runner context manager.
                                                             (line    6)
* running() (concurrent.futures.Future 的方法): Future 物件. (line   23)
* runsource() (code.InteractiveInterpreter 的方法): Interactive Interpreter Objects.
                                                             (line    6)
* runtime (sys._emscripten_info 的屬性): sys --- 系統特定的參數與函式.
                                                             (line  349)
* runtime_checkable() (於 typing 模組中): Other special directives.
                                                             (line  173)
* RuntimeError:                          實體例外.           (line  215)
* RuntimeWarning:                        警告.               (line   44)
* RUSAGE_BOTH (於 resource 模組中):      Resource Usage.     (line  122)
* RUSAGE_CHILDREN (於 resource 模組中):  Resource Usage.     (line  116)
* RUSAGE_SELF (於 resource 模組中):      Resource Usage.     (line  110)
* RUSAGE_THREAD (於 resource 模組中):    Resource Usage.     (line  128)
* RWF_APPEND (於 os 模組中):             File Descriptor Operations.
                                                             (line  711)
* RWF_DSYNC (於 os 模組中):              File Descriptor Operations.
                                                             (line  691)
* RWF_HIPRI (於 os 模組中):              File Descriptor Operations.
                                                             (line  621)
* RWF_NOWAIT (於 os 模組中):             File Descriptor Operations.
                                                             (line  606)
* RWF_SYNC (於 os 模組中):               File Descriptor Operations.
                                                             (line  701)
* S (於 re 模組中):                      旗標.               (line  107)
* S_ENFMT (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  317)
* S_IEXEC (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  331)
* S_IFBLK (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  206)
* S_IFCHR (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  214)
* S_IFDIR (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  210)
* S_IFDOOR (於 stat 模組中):             stat --- 直譯 stat 的結果.
                                                             (line  222)
* S_IFIFO (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  218)
* S_IFLNK (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  198)
* S_IFMT() (於 stat 模組中):             stat --- 直譯 stat 的結果.
                                                             (line   78)
* S_IFPORT (於 stat 模組中):             stat --- 直譯 stat 的結果.
                                                             (line  228)
* S_IFREG (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  202)
* S_IFSOCK (於 stat 模組中):             stat --- 直譯 stat 的結果.
                                                             (line  194)
* S_IFWHT (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  234)
* S_IMODE() (於 stat 模組中):            stat --- 直譯 stat 的結果.
                                                             (line   71)
* S_IREAD (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  323)
* S_IRGRP (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  289)
* S_IROTH (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  305)
* S_IRUSR (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  273)
* S_IRWXG (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  285)
* S_IRWXO (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  301)
* S_IRWXU (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  269)
* S_ISBLK() (於 stat 模組中):            stat --- 直譯 stat 的結果.
                                                             (line   30)
* S_ISCHR() (於 stat 模組中):            stat --- 直譯 stat 的結果.
                                                             (line   25)
* S_ISDIR() (於 stat 模組中):            stat --- 直譯 stat 的結果.
                                                             (line   21)
* S_ISDOOR() (於 stat 模組中):           stat --- 直譯 stat 的結果.
                                                             (line   50)
* S_ISFIFO() (於 stat 模組中):           stat --- 直譯 stat 的結果.
                                                             (line   38)
* S_ISGID (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  251)
* S_ISLNK() (於 stat 模組中):            stat --- 直譯 stat 的結果.
                                                             (line   42)
* S_ISPORT() (於 stat 模組中):           stat --- 直譯 stat 的結果.
                                                             (line   56)
* S_ISREG() (於 stat 模組中):            stat --- 直譯 stat 的結果.
                                                             (line   34)
* S_ISSOCK() (於 stat 模組中):           stat --- 直譯 stat 的結果.
                                                             (line   46)
* S_ISUID (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  247)
* S_ISVTX (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  262)
* S_ISWHT() (於 stat 模組中):            stat --- 直譯 stat 的結果.
                                                             (line   62)
* S_IWGRP (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  293)
* S_IWOTH (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  309)
* S_IWRITE (於 stat 模組中):             stat --- 直譯 stat 的結果.
                                                             (line  327)
* S_IWUSR (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  277)
* S_IXGRP (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  297)
* S_IXOTH (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  313)
* S_IXUSR (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  281)
* safe (uuid.SafeUUID 的屬性):           uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line   31)
* safe_path (sys.flags 的屬性):          sys --- 系統特定的參數與函式.
                                                             (line  567)
* safe_substitute() (string.Template 的方法): 模板字串.      (line   45)
* SafeChildWatcher (asyncio 中的類別):   Process Watchers.   (line  126)
* saferepr() (於 pprint 模組中):         函式<3>.            (line  101)
* SafeUUID (uuid 中的類別):              uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line   27)
* same_files (filecmp.dircmp 的屬性):    The dircmp class.   (line   88)
* same_quantum() (decimal.Context 的方法): Context objects.  (line  504)
* same_quantum() (decimal.Decimal 的方法): Decimal objects.  (line  540)
* samefile() (pathlib.Path 的方法):      Querying file type and status.
                                                             (line  138)
* samefile() (於 os.path 模組中):        os path --- 常見的路徑名操作.
                                                             (line  350)
* SameFileError:                         Directory and files operations.
                                                             (line   52)
* sameopenfile() (於 os.path 模組中):    os path --- 常見的路徑名操作.
                                                             (line  363)
* samesite (http.cookies.Morsel 的屬性): Morsel 物件.        (line   13)
* samestat() (於 os.path 模組中):        os path --- 常見的路徑名操作.
                                                             (line  371)
* sample() (於 random 模組中):           回傳序列的函式.     (line   56)
* samples() (statistics.NormalDist 的方法): NormalDist 物件. (line   49)
* SATURDAY (於 calendar 模組中):         calendar --- 日曆相關函式.
                                                             (line  336)
* save() (http.cookiejar.FileCookieJar 的方法): CookieJar 與 FileCookieJar 物件.
                                                             (line  106)
* save() (test.support.SaveSignals 的方法): test support --- Python 測試套件的工具.
                                                             (line  765)
* SaveAs (tkinter.filedialog 中的類別):  Native Load/Save Dialogs.
                                                             (line   60)
* SAVEDCWD (於 test.support.os_helper 模組中): test support os_helper --- 用於 os 測試的工具.
                                                             (line   14)
* SaveFileDialog (tkinter.filedialog 中的類別): Native Load/Save Dialogs.
                                                             (line  145)
* SaveKey() (於 winreg 模組中):          函式<12>.           (line  394)
* SaveSignals (test.support 中的類別):   test support --- Python 測試套件的工具.
                                                             (line  760)
* savetty() (於 curses 模組中):          函式<5>.            (line  443)
* SAX2DOM (xml.dom.pulldom 中的類別):    xml dom pulldom --- 支援建置部分 DOM 樹.
                                                             (line   81)
* SAXException:                          xml sax --- SAX2 剖析器支援.
                                                             (line   86)
* SAXNotRecognizedException:             xml sax --- SAX2 剖析器支援.
                                                             (line  111)
* SAXNotSupportedException:              xml sax --- SAX2 剖析器支援.
                                                             (line  118)
* SAXParseException:                     xml sax --- SAX2 剖析器支援.
                                                             (line  103)
* scaleb() (decimal.Context 的方法):     Context objects.    (line  508)
* scaleb() (decimal.Decimal 的方法):     Decimal objects.    (line  550)
* scandir() (於 os 模組中):              Files and Directories.
                                                             (line  829)
* scanf（C 函式）:                       模擬 scanf.         (line    6)
* SCHED_BATCH (於 os 模組中):            Interface to the scheduler.
                                                             (line   19)
* SCHED_FIFO (於 os 模組中):             Interface to the scheduler.
                                                             (line   32)
* sched_get_priority_max() (於 os 模組中): Interface to the scheduler.
                                                             (line   63)
* sched_get_priority_min() (於 os 模組中): Interface to the scheduler.
                                                             (line   58)
* sched_getaffinity() (於 os 模組中):    Interface to the scheduler.
                                                             (line  109)
* sched_getparam() (於 os 模組中):       Interface to the scheduler.
                                                             (line   87)
* sched_getscheduler() (於 os 模組中):   Interface to the scheduler.
                                                             (line   75)
* SCHED_IDLE (於 os 模組中):             Interface to the scheduler.
                                                             (line   24)
* SCHED_OTHER (於 os 模組中):            Interface to the scheduler.
                                                             (line   15)
* sched_param (os 中的類別):             Interface to the scheduler.
                                                             (line   46)
* sched_priority (os.sched_param 的屬性): Interface to the scheduler.
                                                             (line   54)
* SCHED_RESET_ON_FORK (於 os 模組中):    Interface to the scheduler.
                                                             (line   40)
* SCHED_RR (於 os 模組中):               Interface to the scheduler.
                                                             (line   36)
* sched_rr_get_interval() (於 os 模組中): Interface to the scheduler.
                                                             (line   93)
* sched_setaffinity() (於 os 模組中):    Interface to the scheduler.
                                                             (line  102)
* sched_setparam() (於 os 模組中):       Interface to the scheduler.
                                                             (line   81)
* sched_setscheduler() (於 os 模組中):   Interface to the scheduler.
                                                             (line   68)
* SCHED_SPORADIC (於 os 模組中):         Interface to the scheduler.
                                                             (line   28)
* sched_yield() (於 os 模組中):          Interface to the scheduler.
                                                             (line   98)
* scheduler (sched 中的類別):            sched --- 事件排程器.
                                                             (line   12)
* SCM_CREDS2 (於 socket 模組中):         常數<7>.            (line  318)
* scope_id (ipaddress.IPv6Address 的屬性): Address objects.  (line  295)
* scope（作用域）:                       Naming and binding. (line    6)
* scope（作用域） <1>:                   Resolution of names.
                                                             (line    6)
* Screen (turtle 中的類別):              Public classes.     (line   30)
* screensize() (於 turtle 模組中):       Window control.     (line   63)
* script_from_examples() (於 doctest 模組中): Debugging.     (line   72)
* scroll() (curses.window 的方法):       Window Objects.     (line  499)
* ScrolledCanvas (turtle 中的類別):      Public classes.     (line   34)
* ScrolledText (tkinter.scrolledtext 中的類別): tkinter scrolledtext --- 捲動文字小工具.
                                                             (line   24)
* scrollok() (curses.window 的方法):     Window Objects.     (line  503)
* scrypt() (於 hashlib 模組中):          密鑰的生成.         (line   43)
* seal() (於 unittest.mock 模組中):      密封 mock.          (line    6)
* search() (imaplib.IMAP4 的方法):       IMAP4 物件.         (line  223)
* search() (re.Pattern 的方法):          Regular Expression Objects.
                                                             (line   14)
* search() (於 re 模組中):               Functions.          (line   36)
* second (datetime.datetime 的屬性):     datetime 物件.      (line  319)
* second (datetime.time 的屬性):         time 物件.          (line   58)
* seconds (datetime.timedelta 的屬性):   timedelta 物件.     (line   99)
* SECTCRE (configparser.ConfigParser 的屬性): Customizing Parser Behaviour.
                                                             (line  301)
* sections() (configparser.ConfigParser 的方法): ConfigParser 物件.
                                                             (line  108)
* secure (http.cookiejar.Cookie 的屬性): Cookie 物件<2>.     (line   49)
* secure (http.cookies.Morsel 的屬性):   Morsel 物件.        (line   13)
* Secure Sockets Layer（安全 socket 層）: ssl --- socket 物件的 TLS/SSL 包裝器.
                                                             (line    8)
* security considerations（安全性注意事項）: 例外<16>.       (line   29)
* security_level (ssl.SSLContext 的屬性): SSL Contexts.      (line  629)
* see() (tkinter.ttk.Treeview 的方法):   ttk Treeview.       (line  240)
* seed_bits (sys.hash_info 的屬性):      sys --- 系統特定的參數與函式.
                                                             (line 1026)
* seed() (random.Random 的方法):         替代產生器.         (line   17)
* seed() (於 random 模組中):             簿記函式 bookkeeping functions.
                                                             (line    6)
* SEEK_CUR (於 os 模組中):               File Descriptor Operations.
                                                             (line  324)
* SEEK_DATA (於 os 模組中):              File Descriptor Operations.
                                                             (line  348)
* SEEK_END (於 os 模組中):               File Descriptor Operations.
                                                             (line  324)
* SEEK_HOLE (於 os 模組中):              File Descriptor Operations.
                                                             (line  348)
* SEEK_SET (於 os 模組中):               File Descriptor Operations.
                                                             (line  324)
* seek() (io.IOBase 的方法):             I/O 基礎類別.       (line   94)
* seek() (io.TextIOBase 的方法):         文字 I/O<2>.        (line   66)
* seek() (io.TextIOWrapper 的方法):      文字 I/O<2>.        (line  203)
* seek() (mmap.mmap 的方法):             mmap --- 記憶體映射檔案的支援.
                                                             (line  293)
* seek() (sqlite3.Blob 的方法):          Blob 物件.          (line   63)
* seekable() (bz2.BZ2File 的方法):       De compression of files.
                                                             (line   99)
* seekable() (io.IOBase 的方法):         I/O 基礎類別.       (line  115)
* seekable() (mmap.mmap 的方法):         mmap --- 記憶體映射檔案的支援.
                                                             (line  304)
* select() (imaplib.IMAP4 的方法):       IMAP4 物件.         (line  240)
* select() (selectors.BaseSelector 的方法): Classes<3>.      (line  108)
* select() (tkinter.ttk.Notebook 的方法): ttk Notebook.      (line   51)
* select() (於 select 模組中):           select --- 等待 I/O 完成.
                                                             (line  113)
* selected_alpn_protocol() (ssl.SSLSocket 的方法): SSL Sockets.
                                                             (line  259)
* selected_npn_protocol() (ssl.SSLSocket 的方法): SSL Sockets.
                                                             (line  269)
* selection_add() (tkinter.ttk.Treeview 的方法): ttk Treeview.
                                                             (line  263)
* selection_remove() (tkinter.ttk.Treeview 的方法): ttk Treeview.
                                                             (line  270)
* selection_set() (tkinter.ttk.Treeview 的方法): ttk Treeview.
                                                             (line  256)
* selection_toggle() (tkinter.ttk.Treeview 的方法): ttk Treeview.
                                                             (line  277)
* selection() (tkinter.ttk.Treeview 的方法): ttk Treeview.   (line  248)
* selector (urllib.request.Request 的屬性): Request Objects. (line   34)
* SelectorEventLoop (asyncio 中的類別):  事件迴圈實作.       (line   11)
* SelectorKey (selectors 中的類別):      Classes<3>.         (line   29)
* SelectSelector (selectors 中的類別):   Classes<3>.         (line  167)
* Self (於 typing 模組中):               特別型別.           (line  133)
* Semaphore (asyncio 中的類別):          Semaphore.          (line    6)
* Semaphore (multiprocessing 中的類別):  Synchronization primitives.
                                                             (line  166)
* Semaphore (threading 中的類別):        Semaphore Objects.  (line   19)
* Semaphore() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  207)
* semaphores, binary（號誌，二進位）:    _thread --- 低階執行緒 API.
                                                             (line    6)
* SEMI (於 token 模組中):                token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   78)
* SEND (opcode):                         Python Bytecode Instructions.
                                                             (line 1232)
* send_bytes() (multiprocessing.connection.Connection 的方法): Connection Objects.
                                                             (line   54)
* send_error() (http.server.BaseHTTPRequestHandler 的方法): http server — HTTP 伺服器.
                                                             (line  216)
* send_fds() (於 socket 模組中):         其他函式<2>.        (line  433)
* send_header() (http.server.BaseHTTPRequestHandler 的方法): http server — HTTP 伺服器.
                                                             (line  251)
* send_message() (smtplib.SMTP 的方法):  SMTP 物件.          (line  303)
* send_response_only() (http.server.BaseHTTPRequestHandler 的方法): http server — HTTP 伺服器.
                                                             (line  263)
* send_response() (http.server.BaseHTTPRequestHandler 的方法): http server — HTTP 伺服器.
                                                             (line  236)
* send_signal() (asyncio.subprocess.Process 的方法): Interacting with Subprocesses.
                                                             (line   85)
* send_signal() (asyncio.SubprocessTransport 的方法): Subprocess Transports.
                                                             (line   44)
* send_signal() (subprocess.Popen 的方法): Popen Objects.    (line   75)
* send() (coroutine 的方法):             Coroutine Objects.  (line   23)
* send() (generator 的方法):             Generator-iterator methods.
                                                             (line   27)
* send() (http.client.HTTPConnection 的方法): HTTPConnection 物件.
                                                             (line  210)
* send() (imaplib.IMAP4 的方法):         IMAP4 物件.         (line  247)
* send() (logging.handlers.DatagramHandler 的方法): DatagramHandler.
                                                             (line   43)
* send() (logging.handlers.SocketHandler 的方法): SocketHandler.
                                                             (line   63)
* send() (multiprocessing.connection.Connection 的方法): Connection Objects.
                                                             (line   15)
* send() (socket.socket 的方法):         Socket 物件.        (line  399)
* sendall() (socket.socket 的方法):      Socket 物件.        (line  415)
* sendcmd() (ftplib.FTP 的方法):         FTP 物件.           (line  138)
* sendfile() (asyncio.loop 的方法):      傳輸檔案.           (line    6)
* sendfile() (socket.socket 的方法):     Socket 物件.        (line  507)
* sendfile() (wsgiref.handlers.BaseHandler 的方法): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  234)
* sendfile() (於 os 模組中):             File Descriptor Operations.
                                                             (line  745)
* SendfileNotAvailableError:             例外<8>.            (line   33)
* sendfunc (C type):                     Slot Type typedefs. (line  116)
* sendmail() (smtplib.SMTP 的方法):      SMTP 物件.          (line  225)
* sendmsg_afalg() (socket.socket 的方法): Socket 物件.       (line  497)
* sendmsg() (socket.socket 的方法):      Socket 物件.        (line  453)
* sendto() (asyncio.DatagramTransport 的方法): Datagram Transports.
                                                             (line    6)
* sendto() (socket.socket 的方法):       Socket 物件.        (line  434)
* sentinel (multiprocessing.Process 的屬性): Process 與例外. (line  156)
* sentinel (於 unittest.mock 模組中):    sentinel（哨兵）.   (line    6)
* sep (於 os 模組中):                    Miscellaneous System Information.
                                                             (line  116)
* SEPTEMBER (於 calendar 模組中):        calendar --- 日曆相關函式.
                                                             (line  365)
* Sequence (collections.abc 中的類別):   Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line   68)
* Sequence (typing 中的類別):            collections abc 中容器 ABC 的別名.
                                                             (line   97)
* sequence（序列）:                      術語表.             (line 1122)
* sequence（序列）;item（項目）:         Subscriptions.      (line    6)
* sequence（序列）;iteration（疊代）:    疊代器型別.         (line    6)
* SequenceMatcher (difflib 中的類別):    SequenceMatcher 物件.
                                                             (line    8)
* serialize() (sqlite3.Connection 的方法): Connection 物件.  (line  673)
* serializing（序列化）;objects（物件）: pickle --- Python 物件序列化.
                                                             (line    8)
* serve_forever() (asyncio.Server 的方法): Server 物件.      (line   85)
* serve_forever() (socketserver.BaseServer 的方法): Server Objects.
                                                             (line   32)
* Server (asyncio 中的類別):             Server 物件.        (line   12)
* server (http.server.BaseHTTPRequestHandler 的屬性): http server — HTTP 伺服器.
                                                             (line   76)
* server (socketserver.BaseRequestHandler 的屬性): Request Handler Objects.
                                                             (line   52)
* server_activate() (socketserver.BaseServer 的方法): Server Objects.
                                                             (line  164)
* server_address (socketserver.BaseServer 的屬性): Server Objects.
                                                             (line   76)
* server_bind() (socketserver.BaseServer 的方法): Server Objects.
                                                             (line  170)
* server_close() (socketserver.BaseServer 的方法): Server Objects.
                                                             (line   61)
* server_hostname (ssl.SSLSocket 的屬性): SSL Sockets.       (line  339)
* server_side (ssl.SSLSocket 的屬性):    SSL Sockets.        (line  332)
* server_software (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  150)
* server_version (http.server.BaseHTTPRequestHandler 的屬性): http server — HTTP 伺服器.
                                                             (line  135)
* server_version (http.server.SimpleHTTPRequestHandler 的屬性): http server — HTTP 伺服器.
                                                             (line  358)
* ServerProxy (xmlrpc.client 中的類別):  xmlrpc client --- XML-RPC 客戶端存取.
                                                             (line   29)
* service_actions() (socketserver.BaseServer 的方法): Server Objects.
                                                             (line   45)
* session (ssl.SSLSocket 的屬性):        SSL Sockets.        (line  352)
* session_reused (ssl.SSLSocket 的屬性): SSL Sockets.        (line  362)
* session_stats() (ssl.SSLContext 的方法): SSL Contexts.     (line  484)
* Set (ast 中的類別):                    文本 Literals.      (line   87)
* Set (collections.abc 中的類別):        Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line   92)
* Set (typing 中的類別):                 內建型別的別名.     (line   28)
* set (內建類別):                        Set Types --- set frozenset.
                                                             (line   33)
* Set Breakpoint:                        Help menu Shell and Editor.
                                                             (line   30)
* set comprehension（集合綜合運算）:     術語表.             (line 1140)
* SET_ADD (opcode):                      Python Bytecode Instructions.
                                                             (line  364)
* set_all():                             參照計數詳細資訊.   (line   83)
* set_allowed_domains() (http.cookiejar.DefaultCookiePolicy 的方法): DefaultCookiePolicy 物件.
                                                             (line   70)
* set_alpn_protocols() (ssl.SSLContext 的方法): SSL Contexts.
                                                             (line  255)
* set_app() (wsgiref.simple_server.WSGIServer 的方法): wsgiref simple_server -- 一個簡單的 WSGI HTTP 伺服器.
                                                             (line   56)
* set_asyncgen_hooks() (於 sys 模組中):  sys --- 系統特定的參數與函式.
                                                             (line 1654)
* set_authorizer() (sqlite3.Connection 的方法): Connection 物件.
                                                             (line  344)
* set_auto_history() (於 readline 模組中): History list.     (line   43)
* set_blocked_domains() (http.cookiejar.DefaultCookiePolicy 的方法): DefaultCookiePolicy 物件.
                                                             (line   56)
* set_blocking() (於 os 模組中):         File Descriptor Operations.
                                                             (line  806)
* set_boundary() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  409)
* set_boundary() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  585)
* set_break() (bdb.Bdb 的方法):          bdb --- 偵錯器框架. (line  343)
* set_charset() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  234)
* set_child_watcher() (asyncio.AbstractEventLoopPolicy 的方法): Policy Objects.
                                                             (line   44)
* set_child_watcher() (於 asyncio 模組中): Process Watchers. (line   31)
* set_children() (tkinter.ttk.Treeview 的方法): ttk Treeview.
                                                             (line   25)
* set_ciphers() (ssl.SSLContext 的方法): SSL Contexts.       (line  241)
* set_completer_delims() (於 readline 模組中): Completion.   (line   50)
* set_completer() (於 readline 模組中):  Completion.         (line   14)
* set_completion_display_matches_hook() (於 readline 模組中): Completion.
                                                             (line   59)
* set_content() (email.contentmanager.ContentManager 的方法): email contentmanager：管理 MIME 內容.
                                                             (line   40)
* set_content() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  587)
* set_content() (於 email.contentmanager 模組中): Content Manager Instances.
                                                             (line   34)
* set_continue() (bdb.Bdb 的方法):       bdb --- 偵錯器框架. (line  328)
* set_cookie_if_ok() (http.cookiejar.CookieJar 的方法): CookieJar 與 FileCookieJar 物件.
                                                             (line   69)
* set_cookie() (http.cookiejar.CookieJar 的方法): CookieJar 與 FileCookieJar 物件.
                                                             (line   73)
* set_coroutine_origin_tracking_depth() (於 sys 模組中): sys --- 系統特定的參數與函式.
                                                             (line 1679)
* set_data() (importlib.abc.SourceLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  413)
* set_data() (importlib.machinery.SourceFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  224)
* set_date() (mailbox.MaildirMessage 的方法): MaildirMessage 物件.
                                                             (line   97)
* set_debug() (asyncio.loop 的方法):     啟用除錯模式.       (line   13)
* set_debug() (於 gc 模組中):            gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line   58)
* set_debuglevel() (ftplib.FTP 的方法):  FTP 物件.           (line   68)
* set_debuglevel() (http.client.HTTPConnection 的方法): HTTPConnection 物件.
                                                             (line   86)
* set_debuglevel() (poplib.POP3 的方法): POP3 物件.          (line   11)
* set_debuglevel() (smtplib.SMTP 的方法): SMTP 物件.         (line    8)
* set_default_executor() (asyncio.loop 的方法): 在執行緒池或行程池中執行程式碼.
                                                             (line   73)
* set_default_type() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  340)
* set_default_type() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  448)
* set_default_verify_paths() (ssl.SSLContext 的方法): SSL Contexts.
                                                             (line  232)
* set_defaults() (argparse.ArgumentParser 的方法): Parser defaults.
                                                             (line    6)
* set_defaults() (optparse.OptionParser 的方法): 其他方法.   (line   27)
* set_ecdh_curve() (ssl.SSLContext 的方法): SSL Contexts.    (line  369)
* set_errno() (於 ctypes 模組中):        Utility functions.  (line  168)
* set_error_mode() (於 msvcrt 模組中):   Other Functions.    (line   12)
* set_escdelay() (於 curses 模組中):     函式<5>.            (line  454)
* set_event_loop_policy() (於 asyncio 模組中): Getting and Setting the Policy.
                                                             (line   13)
* set_event_loop() (asyncio.AbstractEventLoopPolicy 的方法): Policy Objects.
                                                             (line   23)
* set_event_loop() (於 asyncio 模組中):  事件迴圈.           (line   55)
* set_events() (於 sys.monitoring 模組中): Setting events globally.
                                                             (line   13)
* set_exception_handler() (asyncio.loop 的方法): 錯誤處理 API.
                                                             (line    8)
* set_exception() (asyncio.Future 的方法): Future 物件<2>.   (line   50)
* set_exception() (concurrent.futures.Future 的方法): Future 物件.
                                                             (line   96)
* set_executable() (於 multiprocessing 模組中): Miscellaneous<2>.
                                                             (line  115)
* set_filter() (tkinter.filedialog.FileDialog 的方法): Native Load/Save Dialogs.
                                                             (line  127)
* set_flags() (mailbox.Maildir 的方法):  Mailbox 物件<2>.    (line  110)
* set_flags() (mailbox.MaildirMessage 的方法): MaildirMessage 物件.
                                                             (line   72)
* set_flags() (mailbox.mboxMessage 的方法): mboxMessage 物件.
                                                             (line   72)
* set_flags() (mailbox.MMDFMessage 的方法): MMDFMessage 物件.
                                                             (line   71)
* set_forkserver_preload() (於 multiprocessing 模組中): Miscellaneous<2>.
                                                             (line  130)
* set_from() (mailbox.mboxMessage 的方法): mboxMessage 物件. (line   53)
* set_from() (mailbox.MMDFMessage 的方法): MMDFMessage 物件. (line   52)
* SET_FUNCTION_ATTRIBUTE (opcode):       Python Bytecode Instructions.
                                                             (line 1094)
* set_handle_inheritable() (於 os 模組中): Inheritance of File Descriptors.
                                                             (line   40)
* set_history_length() (於 readline 模組中): History file.   (line   30)
* set_info() (mailbox.Maildir 的方法):   Mailbox 物件<2>.    (line  172)
* set_info() (mailbox.MaildirMessage 的方法): MaildirMessage 物件.
                                                             (line  108)
* set_inheritable() (socket.socket 的方法): Socket 物件.     (line  524)
* set_inheritable() (於 os 模組中):      Inheritance of File Descriptors.
                                                             (line   30)
* set_int_max_str_digits() (於 sys 模組中): sys --- 系統特定的參數與函式.
                                                             (line 1461)
* set_labels() (mailbox.BabylMessage 的方法): BabylMessage 物件.
                                                             (line   51)
* set_last_error() (於 ctypes 模組中):   Utility functions.  (line  177)
* set_local_events() (於 sys.monitoring 模組中): Per code object events.
                                                             (line   16)
* set_memlimit() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  300)
* set_name() (asyncio.Task 的方法):      Task Object.        (line  187)
* set_next() (bdb.Bdb 的方法):           bdb --- 偵錯器框架. (line  306)
* set_nonstandard_attr() (http.cookiejar.Cookie 的方法): Cookie 物件<2>.
                                                             (line  107)
* set_npn_protocols() (ssl.SSLContext 的方法): SSL Contexts. (line  270)
* set_ok() (http.cookiejar.CookiePolicy 的方法): CookiePolicy 物件.
                                                             (line    9)
* set_param() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  349)
* set_param() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  516)
* set_pasv() (ftplib.FTP 的方法):        FTP 物件.           (line  187)
* set_payload() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  224)
* set_policy() (http.cookiejar.CookieJar 的方法): CookieJar 與 FileCookieJar 物件.
                                                             (line   57)
* set_pre_input_hook() (於 readline 模組中): Startup hooks.  (line   14)
* set_progress_handler() (sqlite3.Connection 的方法): Connection 物件.
                                                             (line  377)
* set_protocol() (asyncio.BaseTransport 的方法): Base Transport.
                                                             (line   81)
* set_proxy() (urllib.request.Request 的方法): Request Objects.
                                                             (line  114)
* set_psk_client_callback() (ssl.SSLContext 的方法): SSL Contexts.
                                                             (line  664)
* set_psk_server_callback() (ssl.SSLContext 的方法): SSL Contexts.
                                                             (line  716)
* set_quit() (bdb.Bdb 的方法):           bdb --- 偵錯器框架. (line  333)
* set_result() (asyncio.Future 的方法):  Future 物件<2>.     (line   43)
* set_result() (concurrent.futures.Future 的方法): Future 物件.
                                                             (line   87)
* set_return() (bdb.Bdb 的方法):         bdb --- 偵錯器框架. (line  310)
* set_running_or_notify_cancel() (concurrent.futures.Future 的方法): Future 物件.
                                                             (line   70)
* set_selection() (tkinter.filedialog.FileDialog 的方法): Native Load/Save Dialogs.
                                                             (line  131)
* set_seq1() (difflib.SequenceMatcher 的方法): SequenceMatcher 物件.
                                                             (line   54)
* set_seq2() (difflib.SequenceMatcher 的方法): SequenceMatcher 物件.
                                                             (line   59)
* set_seqs() (difflib.SequenceMatcher 的方法): SequenceMatcher 物件.
                                                             (line   44)
* set_sequences() (mailbox.MH 的方法):   MH 物件.            (line   61)
* set_sequences() (mailbox.MHMessage 的方法): MHMessage 物件.
                                                             (line   37)
* set_server_documentation() (xmlrpc.server.DocCGIXMLRPCRequestHandler 的方法): DocCGIXMLRPCRequestHandler.
                                                             (line   24)
* set_server_documentation() (xmlrpc.server.DocXMLRPCServer 的方法): DocXMLRPCServer 物件.
                                                             (line   24)
* set_server_name() (xmlrpc.server.DocCGIXMLRPCRequestHandler 的方法): DocCGIXMLRPCRequestHandler.
                                                             (line   18)
* set_server_name() (xmlrpc.server.DocXMLRPCServer 的方法): DocXMLRPCServer 物件.
                                                             (line   18)
* set_server_title() (xmlrpc.server.DocCGIXMLRPCRequestHandler 的方法): DocCGIXMLRPCRequestHandler.
                                                             (line   13)
* set_server_title() (xmlrpc.server.DocXMLRPCServer 的方法): DocXMLRPCServer 物件.
                                                             (line   13)
* set_servername_callback (ssl.SSLContext 的屬性): SSL Contexts.
                                                             (line  341)
* set_start_method() (於 multiprocessing 模組中): Miscellaneous<2>.
                                                             (line  147)
* set_startup_hook() (於 readline 模組中): Startup hooks.    (line    6)
* set_step() (bdb.Bdb 的方法):           bdb --- 偵錯器框架. (line  302)
* set_subdir() (mailbox.MaildirMessage 的方法): MaildirMessage 物件.
                                                             (line   58)
* set_tabsize() (於 curses 模組中):      函式<5>.            (line  469)
* set_task_factory() (asyncio.loop 的方法): 建立 Futures 和 Tasks.
                                                             (line   34)
* set_threshold() (於 gc 模組中):        gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line  102)
* set_trace_callback() (sqlite3.Connection 的方法): Connection 物件.
                                                             (line  395)
* set_trace() (bdb.Bdb 的方法):          bdb --- 偵錯器框架. (line  319)
* set_trace() (pdb.Pdb 的方法):          pdb --- The Python Debugger.
                                                             (line  215)
* set_trace() (於 bdb 模組中):           bdb --- 偵錯器框架. (line  480)
* set_trace() (於 pdb 模組中):           pdb --- The Python Debugger.
                                                             (line  151)
* set_tunnel() (http.client.HTTPConnection 的方法): HTTPConnection 物件.
                                                             (line   96)
* set_type() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  549)
* set_unittest_reportflags() (於 doctest 模組中): Unittest API.
                                                             (line  175)
* set_unixfrom() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  144)
* set_unixfrom() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  156)
* set_until() (bdb.Bdb 的方法):          bdb --- 偵錯器框架. (line  314)
* SET_UPDATE (opcode):                   Python Bytecode Instructions.
                                                             (line  710)
* set_url() (urllib.robotparser.RobotFileParser 的方法): urllib robotparser --- robots txt 的剖析器.
                                                             (line   20)
* set_usage() (optparse.OptionParser 的方法): 其他方法.      (line    8)
* set_userptr() (curses.panel.Panel 的方法): Panel Objects.  (line   43)
* set_visible() (mailbox.BabylMessage 的方法): BabylMessage 物件.
                                                             (line   68)
* set_wakeup_fd() (於 signal 模組中):    模組內容<5>.        (line  441)
* set_write_buffer_limits() (asyncio.WriteTransport 的方法): Write-only Transports.
                                                             (line   33)
* set() (asyncio.Event 的方法):          Event.              (line   50)
* set() (configparser.ConfigParser 的方法): ConfigParser 物件.
                                                             (line  277)
* set() (configparser.RawConfigParser 的方法): RawConfigParser 物件.
                                                             (line   37)
* set() (contextvars.ContextVar 的方法): Context Variables.  (line   46)
* set() (http.cookies.Morsel 的方法):    Morsel 物件.        (line   57)
* set() (test.support.os_helper.EnvironmentVarGuard 的方法): test support os_helper --- 用於 os 測試的工具.
                                                             (line   65)
* set() (threading.Event 的方法):        Event Objects.      (line   30)
* set() (tkinter.ttk.Combobox 的方法):   ttk Combobox.       (line   19)
* set() (tkinter.ttk.Spinbox 的方法):    ttk Spinbox.        (line   12)
* set() (tkinter.ttk.Treeview 的方法):   ttk Treeview.       (line  284)
* set() (xml.etree.ElementTree.Element 的方法): Element 物件.
                                                             (line   81)
* set（集合）;comprehensions:            Set displays.       (line    6)
* set（集合）;display:                   Set displays.       (line    6)
* setacl() (imaplib.IMAP4 的方法):       IMAP4 物件.         (line  254)
* setannotation() (imaplib.IMAP4 的方法): IMAP4 物件.        (line  259)
* setattrfunc (C type):                  Slot Type typedefs. (line   48)
* setAttribute() (xml.dom.Element 的方法): Element Objects.  (line   67)
* setAttributeNode() (xml.dom.Element 的方法): Element Objects.
                                                             (line   71)
* setAttributeNodeNS() (xml.dom.Element 的方法): Element Objects.
                                                             (line   79)
* setAttributeNS() (xml.dom.Element 的方法): Element Objects.
                                                             (line   87)
* setattrofunc (C type):                 Slot Type typedefs. (line   61)
* SetBase() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line   22)
* setblocking() (socket.socket 的方法):  Socket 物件.        (line  531)
* setByteStream() (xml.sax.xmlreader.InputSource 的方法): InputSource 物件.
                                                             (line   36)
* setcbreak() (於 tty 模組中):           tty --- 終端機控制函式.
                                                             (line   50)
* setCharacterStream() (xml.sax.xmlreader.InputSource 的方法): InputSource 物件.
                                                             (line   55)
* SetComp (ast 中的類別):                綜合運算式 comprehensions.
                                                             (line    6)
* setcomptype() (wave.Wave_write 的方法): Wave_write 物件.   (line   52)
* setconfig() (sqlite3.Connection 的方法): Connection 物件.  (line  657)
* setContentHandler() (xml.sax.xmlreader.XMLReader 的方法): XMLReader 物件.
                                                             (line   25)
* setcontext() (於 decimal 模組中):      Context objects.    (line   18)
* setDaemon() (threading.Thread 的方法): Thread Objects.     (line  215)
* setdefault() (dict 的方法):            Mapping Types --- dict.
                                                             (line  198)
* setdefault() (http.cookies.Morsel 的方法): Morsel 物件.    (line  101)
* setdefaulttimeout() (於 socket 模組中): 其他函式<2>.       (line  353)
* setdlopenflags() (於 sys 模組中):      sys --- 系統特定的參數與函式.
                                                             (line 1448)
* setDocumentLocator() (xml.sax.handler.ContentHandler 的方法): ContentHandler 物件.
                                                             (line   10)
* setDTDHandler() (xml.sax.xmlreader.XMLReader 的方法): XMLReader 物件.
                                                             (line   34)
* setegid() (於 os 模組中):              行程參數.           (line  377)
* setEncoding() (xml.sax.xmlreader.InputSource 的方法): InputSource 物件.
                                                             (line   22)
* setEntityResolver() (xml.sax.xmlreader.XMLReader 的方法): XMLReader 物件.
                                                             (line   43)
* setErrorHandler() (xml.sax.xmlreader.XMLReader 的方法): XMLReader 物件.
                                                             (line   54)
* seteuid() (於 os 模組中):              行程參數.           (line  383)
* setFeature() (xml.sax.xmlreader.XMLReader 的方法): XMLReader 物件.
                                                             (line   76)
* setfirstweekday() (於 calendar 模組中): calendar --- 日曆相關函式.
                                                             (line  255)
* setFormatter() (logging.Handler 的方法): Handler Objects.  (line   48)
* setframerate() (wave.Wave_write 的方法): Wave_write 物件.  (line   40)
* setgid() (於 os 模組中):               行程參數.           (line  389)
* setgroups() (於 os 模組中):            行程參數.           (line  395)
* seth() (於 turtle 模組中):             Turtle motion.      (line  166)
* setheading() (於 turtle 模組中):       Turtle motion.      (line  166)
* sethostname() (於 socket 模組中):      其他函式<2>.        (line  360)
* setinputsizes() (sqlite3.Cursor 的方法): Cursor 物件.      (line  162)
* setitem() (於 operator 模組中):        operator --- 標準運算子替代函式.
                                                             (line  192)
* setitimer() (於 signal 模組中):        模組內容<5>.        (line  412)
* setLevel() (logging.Handler 的方法):   Handler Objects.    (line   35)
* setLevel() (logging.Logger 的方法):    Logger 物件.        (line  103)
* setlimit() (sqlite3.Connection 的方法): Connection 物件.   (line  611)
* setLocale() (xml.sax.xmlreader.XMLReader 的方法): XMLReader 物件.
                                                             (line   60)
* setlocale() (於 locale 模組中):        locale --- 國際化服務.
                                                             (line   27)
* setLoggerClass() (於 logging 模組中):  Module-Level Functions.
                                                             (line  322)
* setlogmask() (於 syslog 模組中):       syslog --- Unix syslog 函式庫例程.
                                                             (line   97)
* setLogRecordFactory() (於 logging 模組中): Module-Level Functions.
                                                             (line  333)
* setMaxConns() (urllib.request.CacheFTPHandler 的方法): CacheFTPHandler 物件.
                                                             (line   13)
* setmode() (於 msvcrt 模組中):          File Operations.    (line   38)
* setName() (threading.Thread 的方法):   Thread Objects.     (line  159)
* setnchannels() (wave.Wave_write 的方法): Wave_write 物件.  (line   32)
* setnframes() (wave.Wave_write 的方法): Wave_write 物件.    (line   47)
* setns() (於 os 模組中):                行程參數.           (line  410)
* setoutputsize() (sqlite3.Cursor 的方法): Cursor 物件.      (line  166)
* SetParamEntityParsing() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line   54)
* setparams() (wave.Wave_write 的方法):  Wave_write 物件.    (line   56)
* setpassword() (zipfile.ZipFile 的方法): ZipFile 物件.      (line  237)
* setpgid() (於 os 模組中):              行程參數.           (line  457)
* setpgrp() (於 os 模組中):              行程參數.           (line  449)
* setpos() (wave.Wave_read 的方法):      Wave_read 物件.     (line   78)
* setpos() (於 turtle 模組中):           Turtle motion.      (line   74)
* setposition() (於 turtle 模組中):      Turtle motion.      (line   74)
* setpriority() (於 os 模組中):          行程參數.           (line  465)
* setprofile_all_threads() (於 threading 模組中): threading --- 基於執行緒的平行性.
                                                             (line  189)
* setprofile() (於 sys 模組中):          sys --- 系統特定的參數與函式.
                                                             (line 1469)
* setprofile() (於 threading 模組中):    threading --- 基於執行緒的平行性.
                                                             (line  182)
* setProperty() (xml.sax.xmlreader.XMLReader 的方法): XMLReader 物件.
                                                             (line   90)
* setPublicId() (xml.sax.xmlreader.InputSource 的方法): InputSource 物件.
                                                             (line    6)
* setquota() (imaplib.IMAP4 的方法):     IMAP4 物件.         (line  264)
* setraw() (於 tty 模組中):              tty --- 終端機控制函式.
                                                             (line   41)
* setrecursionlimit() (於 sys 模組中):   sys --- 系統特定的參數與函式.
                                                             (line 1525)
* setregid() (於 os 模組中):             行程參數.           (line  482)
* SetReparseDeferralEnabled() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line   82)
* setresgid() (於 os 模組中):            行程參數.           (line  488)
* setresuid() (於 os 模組中):            行程參數.           (line  496)
* setreuid() (於 os 模組中):             行程參數.           (line  504)
* setrlimit() (於 resource 模組中):      Resource Limits.    (line   31)
* setsampwidth() (wave.Wave_write 的方法): Wave_write 物件.  (line   36)
* setscrreg() (curses.window 的方法):    Window Objects.     (line  513)
* setsid() (於 os 模組中):               行程參數.           (line  517)
* setsockopt() (socket.socket 的方法):   Socket 物件.        (line  562)
* setstate() (codecs.IncrementalDecoder 的方法): IncrementalDecoder 物件.
                                                             (line   60)
* setstate() (codecs.IncrementalEncoder 的方法): IncrementalEncoder 物件.
                                                             (line   51)
* setstate() (random.Random 的方法):     替代產生器.         (line   27)
* setstate() (於 random 模組中):         簿記函式 bookkeeping functions.
                                                             (line   33)
* setStream() (logging.StreamHandler 的方法): StreamHandler. (line   32)
* setswitchinterval （sys 模組中）:      Thread State and the Global Interpreter Lock.
                                                             (line   15)
* setswitchinterval() (於 sys 模組中):   sys --- 系統特定的參數與函式.
                                                             (line 1542)
* setswitchinterval() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  283)
* setSystemId() (xml.sax.xmlreader.InputSource 的方法): InputSource 物件.
                                                             (line   14)
* setsyx() (於 curses 模組中):           函式<5>.            (line  477)
* setTarget() (logging.handlers.MemoryHandler 的方法): MemoryHandler.
                                                             (line   68)
* setter (C type):                       Defining Getters and Setters.
                                                             (line   42)
* settimeout() (socket.socket 的方法):   Socket 物件.        (line  546)
* setTimeout() (urllib.request.CacheFTPHandler 的方法): CacheFTPHandler 物件.
                                                             (line    9)
* settrace_all_threads() (於 threading 模組中): threading --- 基於執行緒的平行性.
                                                             (line  165)
* settrace() (於 sys 模組中):            sys --- 系統特定的參數與函式.
                                                             (line 1555)
* settrace() (於 threading 模組中):      threading --- 基於執行緒的平行性.
                                                             (line  158)
* setuid() (於 os 模組中):               行程參數.           (line  524)
* setundobuffer() (於 turtle 模組中):    Special Turtle methods.
                                                             (line   61)
* SETUP_ANNOTATIONS (opcode):            Python Bytecode Instructions.
                                                             (line  424)
* SETUP_CLEANUP (opcode):                Python Bytecode Instructions.
                                                             (line 1375)
* setup_environ() (wsgiref.handlers.BaseHandler 的方法): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  167)
* SETUP_FINALLY (opcode):                Python Bytecode Instructions.
                                                             (line 1368)
* setup_python() (venv.EnvBuilder 的方法): API<2>.           (line  146)
* setup_scripts() (venv.EnvBuilder 的方法): API<2>.          (line  154)
* setup_testing_defaults() (於 wsgiref.util 模組中): wsgiref util -- WSGI 環境工具.
                                                             (line   55)
* SETUP_WITH (opcode):                   Python Bytecode Instructions.
                                                             (line 1383)
* setup() (socketserver.BaseRequestHandler 的方法): Request Handler Objects.
                                                             (line   14)
* setUp() (unittest.TestCase 的方法):    Test cases.         (line   33)
* setup() (於 turtle 模組中):            Methods specific to Screen not inherited from TurtleScreen.
                                                             (line   20)
* setUpClass() (unittest.TestCase 的方法): Test cases.       (line   55)
* setupterm() (於 curses 模組中):        函式<5>.            (line  482)
* SetValue() (於 winreg 模組中):         函式<12>.           (line  418)
* SetValueEx() (於 winreg 模組中):       函式<12>.           (line  449)
* setworldcoordinates() (於 turtle 模組中): Window control.  (line   89)
* setx() (於 turtle 模組中):             Turtle motion.      (line  138)
* setxattr() (於 os 模組中):             Linux extended attributes.
                                                             (line   56)
* sety() (於 turtle 模組中):             Turtle motion.      (line  152)
* SF_APPEND (於 stat 模組中):            stat --- 直譯 stat 的結果.
                                                             (line  414)
* SF_ARCHIVED (於 stat 模組中):          stat --- 直譯 stat 的結果.
                                                             (line  406)
* SF_DATALESS (於 stat 模組中):          stat --- 直譯 stat 的結果.
                                                             (line  438)
* SF_FIRMLINK (於 stat 模組中):          stat --- 直譯 stat 的結果.
                                                             (line  432)
* SF_IMMUTABLE (於 stat 模組中):         stat --- 直譯 stat 的結果.
                                                             (line  410)
* SF_MNOWAIT (於 os 模組中):             File Descriptor Operations.
                                                             (line  785)
* SF_NOCACHE (於 os 模組中):             File Descriptor Operations.
                                                             (line  796)
* SF_NODISKIO (於 os 模組中):            File Descriptor Operations.
                                                             (line  785)
* SF_NOUNLINK (於 stat 模組中):          stat --- 直譯 stat 的結果.
                                                             (line  424)
* SF_RESTRICTED (於 stat 模組中):        stat --- 直譯 stat 的結果.
                                                             (line  418)
* SF_SETTABLE (於 stat 模組中):          stat --- 直譯 stat 的結果.
                                                             (line  384)
* SF_SNAPSHOT (於 stat 模組中):          stat --- 直譯 stat 的結果.
                                                             (line  428)
* SF_SUPPORTED (於 stat 模組中):         stat --- 直譯 stat 的結果.
                                                             (line  390)
* SF_SYNC (於 os 模組中):                File Descriptor Operations.
                                                             (line  785)
* SF_SYNTHETIC (於 stat 模組中):         stat --- 直譯 stat 的結果.
                                                             (line  398)
* sha1() (於 hashlib 模組中):            建構函式.           (line   21)
* sha224() (於 hashlib 模組中):          建構函式.           (line   23)
* sha256() (於 hashlib 模組中):          建構函式.           (line   25)
* sha3_224() (於 hashlib 模組中):        建構函式.           (line   31)
* sha3_256() (於 hashlib 模組中):        建構函式.           (line   33)
* sha3_384() (於 hashlib 模組中):        建構函式.           (line   35)
* sha3_512() (於 hashlib 模組中):        建構函式.           (line   37)
* sha384() (於 hashlib 模組中):          建構函式.           (line   27)
* sha512() (於 hashlib 模組中):          建構函式.           (line   29)
* shake_128() (於 hashlib 模組中):       SHAKE 可變長度摘要. (line    6)
* shake_256() (於 hashlib 模組中):       SHAKE 可變長度摘要. (line    8)
* shape (memoryview 的屬性):             Memory Views.       (line  450)
* Shape (turtle 中的類別):               Public classes.     (line   43)
* shape() (於 turtle 模組中):            Appearance.         (line    6)
* shapesize() (於 turtle 模組中):        Appearance.         (line   52)
* shapetransform() (於 turtle 模組中):   Appearance.         (line  137)
* share() (socket.socket 的方法):        Socket 物件.        (line  596)
* ShareableList (multiprocessing.shared_memory 中的類別): multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取.
                                                             (line  246)
* ShareableList() (multiprocessing.managers.SharedMemoryManager 的方法): multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取.
                                                             (line  208)
* Shared Memory（共享記憶體）:           multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取.
                                                             (line   10)
* shared_ciphers() (ssl.SSLSocket 的方法): SSL Sockets.      (line  222)
* shared_memory (sys._emscripten_info 的屬性): sys --- 系統特定的參數與函式.
                                                             (line  358)
* SharedMemory (multiprocessing.shared_memory 中的類別): multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取.
                                                             (line   27)
* SharedMemory() (multiprocessing.managers.SharedMemoryManager 的方法): multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取.
                                                             (line  203)
* SharedMemoryManager (multiprocessing.managers 中的類別): multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取.
                                                             (line  182)
* shearfactor() (於 turtle 模組中):      Appearance.         (line   83)
* Shelf (shelve 中的類別):               Restrictions.       (line   27)
* shield() (於 asyncio 模組中):          Shielding From Cancellation.
                                                             (line    6)
* shift_path_info() (於 wsgiref.util 模組中): wsgiref util -- WSGI 環境工具.
                                                             (line   33)
* shift() (decimal.Context 的方法):      Context objects.    (line  513)
* shift() (decimal.Decimal 的方法):      Decimal objects.    (line  556)
* shifting（移位）;operations（操作）:   整數型別的位元運算. (line    6)
* shifting（移動）;operation（操作）:    Shifting operations.
                                                             (line    6)
* shlex (shlex 中的類別):                shlex --- 簡單的語法分析.
                                                             (line   91)
* shm (multiprocessing.shared_memory.ShareableList 的屬性): multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取.
                                                             (line  314)
* SHORT_TIMEOUT (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line   79)
* shortDescription() (unittest.TestCase 的方法): Test cases. (line  749)
* shorten() (於 textwrap 模組中):        textwrap --- 文字包裝與填充.
                                                             (line   49)
* shouldFlush() (logging.handlers.BufferingHandler 的方法): MemoryHandler.
                                                             (line   36)
* shouldFlush() (logging.handlers.MemoryHandler 的方法): MemoryHandler.
                                                             (line   72)
* shouldStop (unittest.TestResult 的屬性): Loading and running tests.
                                                             (line  284)
* show_code() (於 dis 模組中):           Analysis functions. (line   26)
* show_flag_values() (於 enum 模組中):   通用項目與裝飾器.   (line   92)
* show() (curses.panel.Panel 的方法):    Panel Objects.      (line   49)
* show() (tkinter.commondialog.Dialog 的方法): tkinter commondialog --- Dialog window templates.
                                                             (line   16)
* show() (tkinter.messagebox.Message 的方法): tkinter messagebox --- Tkinter 訊息提示.
                                                             (line   69)
* showerror() (於 tkinter.messagebox 模組中): tkinter messagebox --- Tkinter 訊息提示.
                                                             (line   88)
* showinfo() (於 tkinter.messagebox 模組中): tkinter messagebox --- Tkinter 訊息提示.
                                                             (line   76)
* showsyntaxerror() (code.InteractiveInterpreter 的方法): Interactive Interpreter Objects.
                                                             (line   44)
* showtraceback() (code.InteractiveInterpreter 的方法): Interactive Interpreter Objects.
                                                             (line   53)
* showturtle() (於 turtle 模組中):       Visibility.         (line   15)
* showwarning() (於 tkinter.messagebox 模組中): tkinter messagebox --- Tkinter 訊息提示.
                                                             (line   83)
* showwarning() (於 warnings 模組中):    Available Functions.
                                                             (line   85)
* shuffle() (於 random 模組中):          回傳序列的函式.     (line   42)
* SHUT_RD (於 socket 模組中):            常數<7>.            (line  372)
* SHUT_RDWR (於 socket 模組中):          常數<7>.            (line  372)
* SHUT_WR (於 socket 模組中):            常數<7>.            (line  372)
* ShutDown:                              queue --- 同步佇列 synchronized queue 類別.
                                                             (line   77)
* shutdown_asyncgens() (asyncio.loop 的方法): 啟動和停止迴圈.
                                                             (line   50)
* shutdown_default_executor() (asyncio.loop 的方法): 啟動和停止迴圈.
                                                             (line   68)
* shutdown() (asyncio.Queue 的方法):     Queue.              (line   78)
* shutdown() (concurrent.futures.Executor 的方法): Executor 物件.
                                                             (line   46)
* shutdown() (imaplib.IMAP4 的方法):     IMAP4 物件.         (line  269)
* shutdown() (multiprocessing.managers.BaseManager 的方法): Managers.
                                                             (line   84)
* shutdown() (queue.Queue 的方法):       Terminating queues. (line    9)
* shutdown() (socket.socket 的方法):     Socket 物件.        (line  587)
* shutdown() (socketserver.BaseServer 的方法): Server Objects.
                                                             (line   54)
* shutdown() (於 logging 模組中):        Module-Level Functions.
                                                             (line  311)
* SI (於 curses.ascii 模組中):           curses ascii --- ASCII 字元的工具程式.
                                                             (line   70)
* side_effect (unittest.mock.Mock 的屬性): Mock 類別.        (line  318)
* SIG_BLOCK (於 signal 模組中):          模組內容<5>.        (line  231)
* SIG_DFL (於 signal 模組中):            模組內容<5>.        (line   45)
* SIG_IGN (於 signal 模組中):            模組內容<5>.        (line   53)
* SIG_SETMASK (於 signal 模組中):        模組內容<5>.        (line  246)
* SIG_UNBLOCK (於 signal 模組中):        模組內容<5>.        (line  238)
* SIGABRT (於 signal 模組中):            模組內容<5>.        (line   58)
* SIGALRM (於 signal 模組中):            模組內容<5>.        (line   62)
* SIGBREAK (於 signal 模組中):           模組內容<5>.        (line   68)
* SIGBUS (於 signal 模組中):             模組內容<5>.        (line   74)
* SIGCHLD (於 signal 模組中):            模組內容<5>.        (line   80)
* SIGCLD (於 signal 模組中):             模組內容<5>.        (line   86)
* SIGCONT (於 signal 模組中):            模組內容<5>.        (line   92)
* SIGFPE (於 signal 模組中):             模組內容<5>.        (line   98)
* SIGHUP (於 signal 模組中):             模組內容<5>.        (line  108)
* SIGILL (於 signal 模組中):             模組內容<5>.        (line  115)
* SIGINT (於 signal 模組中):             模組內容<5>.        (line  119)
* SIGINT（C 巨集）:                      Signal Handling<2>. (line    7)
* SIGINT（C 巨集） <1>:                  Signal Handling<2>. (line   34)
* siginterrupt() (於 signal 模組中):     模組內容<5>.        (line  484)
* SIGKILL (於 signal 模組中):            模組內容<5>.        (line  125)
* Sigmasks (signal 中的類別):            模組內容<5>.        (line   31)
* signal() (於 signal 模組中):           模組內容<5>.        (line  499)
* Signals (signal 中的類別):             模組內容<5>.        (line   17)
* Signature (inspect 中的類別):          Introspecting callables with the Signature object.
                                                             (line   74)
* signature (inspect.BoundArguments 的屬性): Introspecting callables with the Signature object.
                                                             (line  363)
* signature() (於 inspect 模組中):       Introspecting callables with the Signature object.
                                                             (line   12)
* sigpending() (於 signal 模組中):       模組內容<5>.        (line  527)
* SIGPIPE (於 signal 模組中):            模組內容<5>.        (line  133)
* SIGSEGV (於 signal 模組中):            模組內容<5>.        (line  141)
* SIGSTKFLT (於 signal 模組中):          模組內容<5>.        (line  145)
* SIGTERM (於 signal 模組中):            模組內容<5>.        (line  157)
* sigtimedwait() (於 signal 模組中):     模組內容<5>.        (line  588)
* SIGUSR1 (於 signal 模組中):            模組內容<5>.        (line  161)
* SIGUSR2 (於 signal 模組中):            模組內容<5>.        (line  167)
* sigwait() (於 signal 模組中):          模組內容<5>.        (line  542)
* sigwaitinfo() (於 signal 模組中):      模組內容<5>.        (line  559)
* SIGWINCH (於 signal 模組中):           模組內容<5>.        (line  173)
* SIMPLE (inspect.BufferFlags 的屬性):   Buffer flags.       (line   15)
* Simple Mail Transfer Protocol（簡單郵件傳輸協定）: smtplib --- SMTP 協定用戶端.
                                                             (line    8)
* simple;statement（陳述式）:            簡單陳述式.         (line    6)
* SimpleCookie (http.cookies 中的類別):  http cookies --- HTTP 狀態管理.
                                                             (line   49)
* simplefilter() (於 warnings 模組中):   Available Functions.
                                                             (line  119)
* SimpleHandler (wsgiref.handlers 中的類別): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line   61)
* SimpleHTTPRequestHandler (http.server 中的類別): http server — HTTP 伺服器.
                                                             (line  339)
* SimpleNamespace (types 中的類別):      Additional Utility Classes and Functions.
                                                             (line    6)
* SimpleQueue (multiprocessing 中的類別): Pipes and Queues.  (line  214)
* SimpleQueue (queue 中的類別):          queue --- 同步佇列 synchronized queue 類別.
                                                             (line   61)
* SimpleXMLRPCRequestHandler (xmlrpc.server 中的類別): xmlrpc server --- 基本 XML-RPC 伺服器.
                                                             (line   63)
* SimpleXMLRPCServer (xmlrpc.server 中的類別): xmlrpc server --- 基本 XML-RPC 伺服器.
                                                             (line   24)
* sin() (於 cmath 模組中):               三角函數.           (line   24)
* sin() (於 math 模組中):                Trigonometric functions.
                                                             (line   65)
* single dispatch（單一調度）:           術語表.             (line 1147)
* SingleAddressHeader (email.headerregistry 中的類別): email headerregistry：自訂標頭物件.
                                                             (line  217)
* singledispatch() (於 functools 模組中): functools --- 可呼叫物件上的高階函式與操作.
                                                             (line  378)
* singledispatchmethod (functools 中的類別): functools --- 可呼叫物件上的高階函式與操作.
                                                             (line  523)
* singleton（單例）;tuple（元組）:       Immutable sequences.
                                                             (line   29)
* sinh() (於 cmath 模組中):              雙曲函數.           (line   25)
* sinh() (於 math 模組中):               Hyperbolic functions.
                                                             (line   25)
* SIO_KEEPALIVE_VALS (於 socket 模組中): 常數<7>.            (line  243)
* SIO_LOOPBACK_FAST_PATH (於 socket 模組中): 常數<7>.        (line  243)
* SIO_RCVALL (於 socket 模組中):         常數<7>.            (line  243)
* site 命令列選項; -user-base:           命令列介面<7>.      (line   18)
* site 命令列選項; -user-site:           命令列介面<7>.      (line   22)
* site_maps() (urllib.robotparser.RobotFileParser 的方法): urllib robotparser --- robots txt 的剖析器.
                                                             (line   63)
* site-packages;directory（目錄）:       site --- Site-specific configuration hook.
                                                             (line   25)
* sitecustomize:                         客製化模組.         (line    6)
* sitecustomize <1>:                     客製化模組.         (line   18)
* sixtofour (ipaddress.IPv6Address 的屬性): Address objects. (line  302)
* size (multiprocessing.shared_memory.SharedMemory 的屬性): multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取.
                                                             (line  109)
* size (struct.Struct 的屬性):           Classes<2>.         (line   61)
* size (tarfile.TarInfo 的屬性):         TarInfo 物件.       (line   65)
* size (tracemalloc.Statistic 的屬性):   Statistic.          (line   19)
* size (tracemalloc.StatisticDiff 的屬性): StatisticDiff.    (line   26)
* size (tracemalloc.Trace 的屬性):       Trace.              (line   23)
* size_diff (tracemalloc.StatisticDiff 的屬性): StatisticDiff.
                                                             (line   32)
* SIZE_MAX（C 巨集）:                    整數物件.           (line  251)
* size() (ftplib.FTP 的方法):            FTP 物件.           (line  309)
* size() (mmap.mmap 的方法):             mmap --- 記憶體映射檔案的支援.
                                                             (line  311)
* Sized (collections.abc 中的類別):      Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line   15)
* Sized (typing 中的類別):               Aliases to other ABCs in collections abc.
                                                             (line   68)
* sizeof_digit (sys.int_info 的屬性):    sys --- 系統特定的參數與函式.
                                                             (line 1110)
* sizeof() (於 ctypes 模組中):           Utility functions.  (line  186)
* SKIP (於 doctest 模組中):              可選旗標.           (line   92)
* skip_if_broken_multiprocessing_synchronize() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  718)
* skip_unless_bind_unix_socket() (於 test.support.socket_helper 模組中): test support socket_helper --- 用於 socket 測試的工具.
                                                             (line   59)
* skip_unless_symlink() (於 test.support.os_helper 模組中): test support os_helper --- 用於 os 測試的工具.
                                                             (line  125)
* skip_unless_xattr() (於 test.support.os_helper 模組中): test support os_helper --- 用於 os 測試的工具.
                                                             (line  130)
* skip() (於 unittest 模組中):           Skipping tests and expected failures.
                                                             (line   85)
* skipIf() (於 unittest 模組中):         Skipping tests and expected failures.
                                                             (line   90)
* skipinitialspace (csv.Dialect 的屬性): Dialect 與格式參數. (line   59)
* skipped (doctest.TestResults 的屬性):  TestResults objects.
                                                             (line   16)
* skipped (unittest.TestResult 的屬性):  Loading and running tests.
                                                             (line  259)
* skippedEntity() (xml.sax.handler.ContentHandler 的方法): ContentHandler 物件.
                                                             (line  176)
* skips (doctest.DocTestRunner 的屬性):  DocTestRunner 物件. (line  142)
* SkipTest:                              Skipping tests and expected failures.
                                                             (line  105)
* skipTest() (unittest.TestCase 的方法): Test cases.         (line   97)
* skipUnless() (於 unittest 模組中):     Skipping tests and expected failures.
                                                             (line   94)
* SLASH (於 token 模組中):               token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   94)
* SLASHEQUAL (於 token 模組中):          token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  182)
* sleep() (於 asyncio 模組中):           Sleeping.           (line    6)
* sleep() (於 time 模組中):              函式<4>.            (line  231)
* sleeping_retry() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  217)
* Slice (ast 中的類別):                  下標 Subscripting.  (line   26)
* slice (內建類別):                      內建函式.           (line 1589)
* slice（切片）:                         Sequences.          (line   14)
* slice（切片） <1>:                     Mutable sequences.  (line    6)
* slice（切片） <2>:                     Slicings.           (line    6)
* slice（切片） <3>:                     術語表.             (line 1152)
* slice（切片）;assignment（賦值）:      Assignment statements.
                                                             (line  125)
* slice（切片）;assignment（賦值） <1>:  Mutable Sequence Types.
                                                             (line   16)
* slice（切片）;operation（操作）:       Common Sequence Operations.
                                                             (line   21)
* slicing（切片）:                       Slicings.           (line    6)
* slow_callback_duration (asyncio.loop 的屬性): 啟用除錯模式.
                                                             (line   20)
* SMALLEST (於 test.support 模組中):     test support --- Python 測試套件的工具.
                                                             (line  188)
* SMTP (smtplib 中的類別):               smtplib --- SMTP 協定用戶端.
                                                             (line   21)
* SMTP (於 email.policy 模組中):         email policy Policy Objects.
                                                             (line  510)
* SMTP_SSL (smtplib 中的類別):           smtplib --- SMTP 協定用戶端.
                                                             (line   74)
* SMTP;protocol（協定）:                 smtplib --- SMTP 協定用戶端.
                                                             (line    8)
* SMTPAuthenticationError:               smtplib --- SMTP 協定用戶端.
                                                             (line  177)
* SMTPConnectError:                      smtplib --- SMTP 協定用戶端.
                                                             (line  162)
* SMTPDataError:                         smtplib --- SMTP 協定用戶端.
                                                             (line  158)
* SMTPException:                         smtplib --- SMTP 協定用戶端.
                                                             (line  123)
* SMTPHandler (logging.handlers 中的類別): SMTPHandler.      (line   10)
* SMTPHeloError:                         smtplib --- SMTP 協定用戶端.
                                                             (line  167)
* SMTPNotSupportedError:                 smtplib --- SMTP 協定用戶端.
                                                             (line  171)
* SMTPRecipientsRefused:                 smtplib --- SMTP 協定用戶端.
                                                             (line  151)
* SMTPResponseException:                 smtplib --- SMTP 協定用戶端.
                                                             (line  137)
* SMTPSenderRefused:                     smtplib --- SMTP 協定用戶端.
                                                             (line  145)
* SMTPServerDisconnected:                smtplib --- SMTP 協定用戶端.
                                                             (line  131)
* SMTPUTF8 (於 email.policy 模組中):     email policy Policy Objects.
                                                             (line  516)
* Snapshot (tracemalloc 中的類別):       Snapshot.           (line    6)
* SND_ALIAS (於 winsound 模組中):        winsound --- Windows 的聲音播放介面.
                                                             (line   47)
* SND_ASYNC (於 winsound 模組中):        winsound --- Windows 的聲音播放介面.
                                                             (line  109)
* SND_FILENAME (於 winsound 模組中):     winsound --- Windows 的聲音播放介面.
                                                             (line   42)
* SND_LOOP (於 winsound 模組中):         winsound --- Windows 的聲音播放介面.
                                                             (line   88)
* SND_MEMORY (於 winsound 模組中):       winsound --- Windows 的聲音播放介面.
                                                             (line   94)
* SND_NODEFAULT (於 winsound 模組中):    winsound --- Windows 的聲音播放介面.
                                                             (line  113)
* SND_NOSTOP (於 winsound 模組中):       winsound --- Windows 的聲音播放介面.
                                                             (line  118)
* SND_NOWAIT (於 winsound 模組中):       winsound --- Windows 的聲音播放介面.
                                                             (line  122)
* SND_PURGE (於 winsound 模組中):        winsound --- Windows 的聲音播放介面.
                                                             (line  103)
* sni_callback (ssl.SSLContext 的屬性):  SSL Contexts.       (line  288)
* sniff() (csv.Sniffer 的方法):          模組內容<3>.        (line  209)
* Sniffer (csv 中的類別):                模組內容<3>.        (line  203)
* SO (於 curses.ascii 模組中):           curses ascii --- ASCII 字元的工具程式.
                                                             (line   67)
* SO_INCOMING_CPU (於 socket 模組中):    常數<7>.            (line  332)
* sock_accept() (asyncio.loop 的方法):   直接使用 socket 物件.
                                                             (line  101)
* SOCK_CLOEXEC (於 socket 模組中):       常數<7>.            (line   38)
* sock_connect() (asyncio.loop 的方法):  直接使用 socket 物件.
                                                             (line   83)
* SOCK_DGRAM (於 socket 模組中):         常數<7>.            (line   27)
* SOCK_MAX_SIZE (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  122)
* SOCK_NONBLOCK (於 socket 模組中):      常數<7>.            (line   38)
* SOCK_RAW (於 socket 模組中):           常數<7>.            (line   27)
* SOCK_RDM (於 socket 模組中):           常數<7>.            (line   27)
* sock_recv_into() (asyncio.loop 的方法): 直接使用 socket 物件.
                                                             (line   24)
* sock_recv() (asyncio.loop 的方法):     直接使用 socket 物件.
                                                             (line   11)
* sock_recvfrom_into() (asyncio.loop 的方法): 直接使用 socket 物件.
                                                             (line   46)
* sock_recvfrom() (asyncio.loop 的方法): 直接使用 socket 物件.
                                                             (line   35)
* sock_sendall() (asyncio.loop 的方法):  直接使用 socket 物件.
                                                             (line   57)
* sock_sendfile() (asyncio.loop 的方法): 直接使用 socket 物件.
                                                             (line  120)
* sock_sendto() (asyncio.loop 的方法):   直接使用 socket 物件.
                                                             (line   72)
* SOCK_SEQPACKET (於 socket 模組中):     常數<7>.            (line   27)
* SOCK_STREAM (於 socket 模組中):        常數<7>.            (line   27)
* socket (socket 中的類別):              建立 sockets.       (line    8)
* socket (socketserver.BaseServer 的屬性): Server Objects.   (line   85)
* socket_type (socketserver.BaseServer 的屬性): Server Objects.
                                                             (line  108)
* socket() (imaplib.IMAP4 的方法):       IMAP4 物件.         (line  275)
* socket() (於 socket 模組):             select --- 等待 I/O 完成.
                                                             (line  141)
* SocketHandler (logging.handlers 中的類別): SocketHandler.  (line   10)
* socketpair() (於 socket 模組中):       建立 sockets.       (line   64)
* sockets (asyncio.Server 的屬性):       Server 物件.        (line  119)
* SocketType (於 socket 模組中):         建立 sockets.       (line  184)
* soft deprecated:                       術語表.             (line 1159)
* soft keyword（軟關鍵字）:              軟關鍵字.           (line    6)
* SOFT_KEYWORD (於 token 模組中):        token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  252)
* softkwlist (於 keyword 模組中):        keyword --- 檢驗 Python 關鍵字.
                                                             (line   29)
* SOH (於 curses.ascii 模組中):          curses ascii --- ASCII 字元的工具程式.
                                                             (line   22)
* SOL_ALG (於 socket 模組中):            常數<7>.            (line  259)
* SOL_RDS (於 socket 模組中):            常數<7>.            (line  230)
* SOMAXCONN (於 socket 模組中):          常數<7>.            (line   54)
* sort_stats() (pstats.Stats 的方法):    The Stats Class.    (line   67)
* sort() (imaplib.IMAP4 的方法):         IMAP4 物件.         (line  279)
* sort() (list 的方法):                  List（串列）<2>.    (line   39)
* sortdict() (於 test.support 模組中):   test support --- Python 測試套件的工具.
                                                             (line  264)
* sortTestMethodsUsing (unittest.TestLoader 的屬性): Loading and running tests.
                                                             (line  195)
* source (doctest.Example 的屬性):       Example 物件.       (line   17)
* source (pdb command):                  Debugger Commands.  (line  285)
* source (shlex.shlex 的屬性):           shlex 物件.         (line  150)
* source character set（原始字元集合）:  Encoding declarations.
                                                             (line    6)
* SOURCE_DATE_EPOCH:                     py_compile<3>.      (line    7)
* SOURCE_DATE_EPOCH <1>:                 Library<48>.        (line  452)
* SOURCE_DATE_EPOCH <2>:                 Build<53>.          (line   15)
* SOURCE_DATE_EPOCH <3>:                 py_compile — 編譯 Python 來源檔案.
                                                             (line   66)
* SOURCE_DATE_EPOCH <4>:                 py_compile — 編譯 Python 來源檔案.
                                                             (line   82)
* SOURCE_DATE_EPOCH <5>:                 py_compile — 編譯 Python 來源檔案.
                                                             (line   86)
* SOURCE_DATE_EPOCH <6>:                 Command-line use.   (line   90)
* source_from_cache() (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line   58)
* source_hash() (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line  160)
* SOURCE_SUFFIXES (於 importlib.machinery 模組中): importlib machinery -- Importers and path hooks.
                                                             (line   13)
* source_to_code() (importlib.abc.InspectLoader 的靜態方法): importlib abc -- Abstract base classes related to import.
                                                             (line  269)
* SourceFileLoader (importlib.machinery 中的類別): importlib machinery -- Importers and path hooks.
                                                             (line  198)
* sourcehook() (shlex.shlex 的方法):     shlex 物件.         (line   26)
* SourcelessFileLoader (importlib.machinery 中的類別): importlib machinery -- Importers and path hooks.
                                                             (line  238)
* SourceLoader (importlib.abc 中的類別): importlib abc -- Abstract base classes related to import.
                                                             (line  353)
* SP (於 curses.ascii 模組中):           curses ascii --- ASCII 字元的工具程式.
                                                             (line  121)
* space;於字串格式化:                    格式規格 Format Specification 迷你語言.
                                                             (line   60)
* space（空白）:                         Indentation.        (line    6)
* space（空白）;於 printf 風格格式化:    printf-style String Formatting.
                                                             (line   69)
* space（空白）;於 printf 風格格式化 <1>: printf-style Bytes Formatting.
                                                             (line   63)
* span() (re.Match 的方法):              Match Objects.      (line  171)
* sparse (tarfile.TarInfo 的屬性):       TarInfo 物件.       (line  157)
* spawn_python() (於 test.support.script_helper 模組中): test support script_helper --- 用於 Python 執行測試的工具.
                                                             (line   65)
* spawn() (於 pty 模組中):               pty --- 偽終端工具. (line   42)
* spawnl() (於 os 模組中):               行程管理.           (line  588)
* spawnle() (於 os 模組中):              行程管理.           (line  588)
* spawnlp() (於 os 模組中):              行程管理.           (line  588)
* spawnlpe() (於 os 模組中):             行程管理.           (line  588)
* spawnv() (於 os 模組中):               行程管理.           (line  588)
* spawnve() (於 os 模組中):              行程管理.           (line  588)
* spawnvp() (於 os 模組中):              行程管理.           (line  588)
* spawnvpe() (於 os 模組中):             行程管理.           (line  588)
* spec_from_file_location() (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line  148)
* spec_from_loader() (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line  137)
* special method（特殊方法）:            術語表.             (line 1175)
* special;attribute（屬性）:             標準型別階層.       (line   13)
* special;method（方法）:                術語表.             (line 1179)
* SpecialFileError:                      tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  246)
* specified_attributes (xml.parsers.expat.xmlparser 的屬性): XMLParser 物件<2>.
                                                             (line  155)
* speed() (於 turtle 模組中):            Turtle motion.      (line  328)
* Spinbox (tkinter.ttk 中的類別):        ttk Spinbox.        (line    6)
* SPLICE_F_MORE (於 os 模組中):          File Descriptor Operations.
                                                             (line  853)
* SPLICE_F_MOVE (於 os 模組中):          File Descriptor Operations.
                                                             (line  853)
* SPLICE_F_NONBLOCK (於 os 模組中):      File Descriptor Operations.
                                                             (line  853)
* splice() (於 os 模組中):               File Descriptor Operations.
                                                             (line  826)
* split() (BaseExceptionGroup 的方法):   例外群組.           (line   61)
* split() (bytearray 的方法):            Bytes and Bytearray Operations.
                                                             (line  395)
* split() (bytes 的方法):                Bytes and Bytearray Operations.
                                                             (line  395)
* split() (re.Pattern 的方法):           Regular Expression Objects.
                                                             (line   79)
* split() (str 的方法):                  String Methods<2>.  (line  462)
* split() (於 os.path 模組中):           os path --- 常見的路徑名操作.
                                                             (line  382)
* split() (於 re 模組中):                Functions.          (line   80)
* split() (於 shlex 模組中):             shlex --- 簡單的語法分析.
                                                             (line   17)
* splitdrive() (於 os.path 模組中):      os path --- 常見的路徑名操作.
                                                             (line  395)
* splitext() (於 os.path 模組中):        os path --- 常見的路徑名操作.
                                                             (line  445)
* splitlines() (bytearray 的方法):       Bytes and Bytearray Operations.
                                                             (line  638)
* splitlines() (bytes 的方法):           Bytes and Bytearray Operations.
                                                             (line  638)
* splitlines() (str 的方法):             String Methods<2>.  (line  504)
* SplitResult (urllib.parse 中的類別):   Structured Parse Results.
                                                             (line   55)
* SplitResultBytes (urllib.parse 中的類別): Structured Parse Results.
                                                             (line   82)
* splitroot() (於 os.path 模組中):       os path --- 常見的路徑名操作.
                                                             (line  416)
* SpooledTemporaryFile (tempfile 中的類別): tempfile --- 生成臨時檔案和目錄.
                                                             (line  128)
* sprintf 風格格式化:                    printf-style String Formatting.
                                                             (line    6)
* sprintf 風格格式化 <1>:                printf-style Bytes Formatting.
                                                             (line    6)
* SQLITE_DBCONFIG_DEFENSIVE (於 sqlite3 模組中): Module constants.
                                                             (line  142)
* SQLITE_DBCONFIG_DQS_DDL (於 sqlite3 模組中): Module constants.
                                                             (line  142)
* SQLITE_DBCONFIG_DQS_DML (於 sqlite3 模組中): Module constants.
                                                             (line  142)
* SQLITE_DBCONFIG_ENABLE_FKEY (於 sqlite3 模組中): Module constants.
                                                             (line  142)
* SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER (於 sqlite3 模組中): Module constants.
                                                             (line  142)
* SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION (於 sqlite3 模組中): Module constants.
                                                             (line  142)
* SQLITE_DBCONFIG_ENABLE_QPSG (於 sqlite3 模組中): Module constants.
                                                             (line  142)
* SQLITE_DBCONFIG_ENABLE_TRIGGER (於 sqlite3 模組中): Module constants.
                                                             (line  142)
* SQLITE_DBCONFIG_ENABLE_VIEW (於 sqlite3 模組中): Module constants.
                                                             (line  142)
* SQLITE_DBCONFIG_LEGACY_ALTER_TABLE (於 sqlite3 模組中): Module constants.
                                                             (line  142)
* SQLITE_DBCONFIG_LEGACY_FILE_FORMAT (於 sqlite3 模組中): Module constants.
                                                             (line  142)
* SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE (於 sqlite3 模組中): Module constants.
                                                             (line  142)
* SQLITE_DBCONFIG_RESET_DATABASE (於 sqlite3 模組中): Module constants.
                                                             (line  142)
* SQLITE_DBCONFIG_TRIGGER_EQP (於 sqlite3 模組中): Module constants.
                                                             (line  142)
* SQLITE_DBCONFIG_TRUSTED_SCHEMA (於 sqlite3 模組中): Module constants.
                                                             (line  142)
* SQLITE_DBCONFIG_WRITABLE_SCHEMA (於 sqlite3 模組中): Module constants.
                                                             (line  142)
* SQLITE_DENY (於 sqlite3 模組中):       Module constants.   (line   44)
* sqlite_errorcode (sqlite3.Error 的屬性): 例外<4>.          (line   24)
* sqlite_errorname (sqlite3.Error 的屬性): 例外<4>.          (line   30)
* SQLITE_IGNORE (於 sqlite3 模組中):     Module constants.   (line   44)
* SQLITE_OK (於 sqlite3 模組中):         Module constants.   (line   44)
* sqlite_version (於 sqlite3 模組中):    Module constants.   (line   73)
* sqlite_version_info (於 sqlite3 模組中): Module constants. (line   78)
* sqrt() (decimal.Context 的方法):       Context objects.    (line  517)
* sqrt() (decimal.Decimal 的方法):       Decimal objects.    (line  567)
* sqrt() (於 cmath 模組中):              冪函數和對數函數.   (line   20)
* sqrt() (於 math 模組中):               Power and logarithmic functions.
                                                             (line   90)
* ssizeargfunc (C type):                 Slot Type typedefs. (line  126)
* ssizeobjargproc (C type):              Slot Type typedefs. (line  130)
* SSL:                                   ssl --- socket 物件的 TLS/SSL 包裝器.
                                                             (line    8)
* ssl_version (ftplib.FTP_TLS 的屬性):   FTP_TLS 物件.       (line   79)
* SSLCertVerificationError:              例外<11>.           (line   71)
* SSLContext (ssl 中的類別):             SSL Contexts.       (line   14)
* SSLEOFError:                           例外<11>.           (line   64)
* SSLError:                              例外<11>.           (line    6)
* SSLErrorNumber (ssl 中的類別):         常數<8>.            (line  487)
* SSLKEYLOGFILE:                         語境建立.           (line   27)
* SSLKEYLOGFILE <1>:                     語境建立.           (line   71)
* SSLObject (ssl 中的類別):              Memory BIO Support<2>.
                                                             (line   30)
* sslobject_class (ssl.SSLContext 的屬性): SSL Contexts.     (line  475)
* SSLSession (ssl 中的類別):             SSL session.        (line    8)
* SSLSocket (ssl 中的類別):              SSL Sockets.        (line    6)
* sslsocket_class (ssl.SSLContext 的屬性): SSL Contexts.     (line  449)
* SSLSyscallError:                       例外<11>.           (line   56)
* SSLv3 (ssl.TLSVersion 的屬性):         常數<8>.            (line  508)
* SSLWantReadError:                      例外<11>.           (line   40)
* SSLWantWriteError:                     例外<11>.           (line   48)
* SSLZeroReturnError:                    例外<11>.           (line   32)
* st_atime (os.stat_result 的屬性):      Files and Directories.
                                                             (line 1172)
* ST_ATIME (於 stat 模組中):             stat --- 直譯 stat 的結果.
                                                             (line  163)
* st_atime_ns (os.stat_result 的屬性):   Files and Directories.
                                                             (line 1189)
* st_birthtime (os.stat_result 的屬性):  Files and Directories.
                                                             (line 1215)
* st_birthtime_ns (os.stat_result 的屬性): Files and Directories.
                                                             (line 1222)
* st_blksize (os.stat_result 的屬性):    Files and Directories.
                                                             (line 1259)
* st_blocks (os.stat_result 的屬性):     Files and Directories.
                                                             (line 1254)
* st_creator (os.stat_result 的屬性):    Files and Directories.
                                                             (line 1295)
* st_ctime (os.stat_result 的屬性):      Files and Directories.
                                                             (line 1180)
* ST_CTIME (於 stat 模組中):             stat --- 直譯 stat 的結果.
                                                             (line  171)
* st_ctime_ns (os.stat_result 的屬性):   Files and Directories.
                                                             (line 1203)
* st_dev (os.stat_result 的屬性):        Files and Directories.
                                                             (line 1148)
* ST_DEV (於 stat 模組中):               stat --- 直譯 stat 的結果.
                                                             (line  142)
* st_file_attributes (os.stat_result 的屬性): Files and Directories.
                                                             (line 1305)
* st_flags (os.stat_result 的屬性):      Files and Directories.
                                                             (line 1269)
* st_fstype (os.stat_result 的屬性):     Files and Directories.
                                                             (line 1284)
* st_gen (os.stat_result 的屬性):        Files and Directories.
                                                             (line 1277)
* st_gid (os.stat_result 的屬性):        Files and Directories.
                                                             (line 1160)
* ST_GID (於 stat 模組中):               stat --- 直譯 stat 的結果.
                                                             (line  154)
* st_ino (os.stat_result 的屬性):        Files and Directories.
                                                             (line 1139)
* ST_INO (於 stat 模組中):               stat --- 直譯 stat 的結果.
                                                             (line  138)
* st_mode (os.stat_result 的屬性):       Files and Directories.
                                                             (line 1135)
* ST_MODE (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  134)
* st_mtime (os.stat_result 的屬性):      Files and Directories.
                                                             (line 1176)
* ST_MTIME (於 stat 模組中):             stat --- 直譯 stat 的結果.
                                                             (line  167)
* st_mtime_ns (os.stat_result 的屬性):   Files and Directories.
                                                             (line 1196)
* st_nlink (os.stat_result 的屬性):      Files and Directories.
                                                             (line 1152)
* ST_NLINK (於 stat 模組中):             stat --- 直譯 stat 的結果.
                                                             (line  146)
* st_rdev (os.stat_result 的屬性):       Files and Directories.
                                                             (line 1265)
* st_reparse_tag (os.stat_result 的屬性): Files and Directories.
                                                             (line 1315)
* st_rsize (os.stat_result 的屬性):      Files and Directories.
                                                             (line 1291)
* st_size (os.stat_result 的屬性):       Files and Directories.
                                                             (line 1164)
* ST_SIZE (於 stat 模組中):              stat --- 直譯 stat 的結果.
                                                             (line  158)
* st_type (os.stat_result 的屬性):       Files and Directories.
                                                             (line 1299)
* st_uid (os.stat_result 的屬性):        Files and Directories.
                                                             (line 1156)
* ST_UID (於 stat 模組中):               stat --- 直譯 stat 的結果.
                                                             (line  150)
* st() (於 turtle 模組中):               Visibility.         (line   15)
* stack (traceback.TracebackException 的屬性): TracebackException 物件.
                                                             (line   70)
* stack viewer（堆疊檢視器）:            Debug menu Shell window only.
                                                             (line   15)
* stack_effect() (於 dis 模組中):        Analysis functions. (line  183)
* stack_size() (於 _thread 模組中):      _thread --- 低階執行緒 API.
                                                             (line   94)
* stack_size() (於 threading 模組中):    threading --- 基於執行緒的平行性.
                                                             (line  206)
* stack() (於 inspect 模組中):           直譯器堆疊.         (line  168)
* stack（堆疊）;trace（追蹤）:           Traceback objects.  (line    6)
* stackable（可堆疊）;streams（串流）:   codecs --- 編解碼器註冊表和基底類別.
                                                             (line    8)
* StackSummary (traceback 中的類別):     StackSummary 物件.  (line   10)
* stamp() (於 turtle 模組中):            Turtle motion.      (line  272)
* Standard C（標準 C）:                  String and Bytes literals.
                                                             (line   74)
* standard input（標準輸入）:            完整的 Python 程式. (line   19)
* standard_b64decode() (於 base64 模組中): base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   76)
* standard_b64encode() (於 base64 模組中): base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   71)
* standard;output:                       Expression statements.
                                                             (line   17)
* standend() (curses.window 的方法):     Window Objects.     (line  518)
* standout() (curses.window 的方法):     Window Objects.     (line  523)
* STAR (於 token 模組中):                token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   90)
* STAREQUAL (於 token 模組中):           token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  178)
* starmap_async() (multiprocessing.pool.Pool 的方法): Process Pools.
                                                             (line  162)
* starmap() (multiprocessing.pool.Pool 的方法): Process Pools.
                                                             (line  151)
* starmap() (於 itertools 模組中):       Itertool 函式.      (line  494)
* Starred (ast 中的類別):                變數.               (line   38)
* start (range 的屬性):                  Ranges.             (line   61)
* start （slice 物件屬性）:              Slice objects.      (line   10)
* start (slice 的屬性):                  內建函式.           (line 1597)
* start (UnicodeError 的屬性):           實體例外.           (line  380)
* start_color() (於 curses 模組中):      函式<5>.            (line  490)
* start_new_thread() (於 _thread 模組中): _thread --- 低階執行緒 API.
                                                             (line   28)
* start_ns() (xml.etree.ElementTree.TreeBuilder 的方法): TreeBuilder 物件.
                                                             (line   76)
* start_server() (於 asyncio 模組中):    串流.               (line   69)
* start_serving() (asyncio.Server 的方法): Server 物件.      (line   71)
* start_threads() (於 test.support.threading_helper 模組中): test support threading_helper --- Utilities for threading tests.
                                                             (line   22)
* start_tls() (asyncio.loop 的方法):     TLS 升級.           (line    6)
* start_tls() (asyncio.StreamWriter 的方法): StreamWriter.   (line   73)
* start_unix_server() (於 asyncio 模組中): 串流.             (line  128)
* start() (logging.handlers.QueueListener 的方法): QueueListener.
                                                             (line   74)
* start() (multiprocessing.managers.BaseManager 的方法): Managers.
                                                             (line   57)
* start() (multiprocessing.Process 的方法): Process 與例外.  (line   58)
* start() (re.Match 的方法):             Match Objects.      (line  146)
* start() (threading.Thread 的方法):     Thread Objects.     (line   93)
* start() (tkinter.ttk.Progressbar 的方法): ttk Progressbar. (line    8)
* start() (xml.etree.ElementTree.TreeBuilder 的方法): TreeBuilder 物件.
                                                             (line   43)
* start() (於 tracemalloc 模組中):       函式<10>.           (line   68)
* start（切片物件屬性）:                 Slicings.           (line   26)
* startCDATA() (xml.sax.handler.LexicalHandler 的方法): LexicalHandler 物件.
                                                             (line   32)
* StartCdataSectionHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line  340)
* StartDoctypeDeclHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line  224)
* startDocument() (xml.sax.handler.ContentHandler 的方法): ContentHandler 物件.
                                                             (line   32)
* startDTD() (xml.sax.handler.LexicalHandler 的方法): LexicalHandler 物件.
                                                             (line   23)
* startElement() (xml.sax.handler.ContentHandler 的方法): ContentHandler 物件.
                                                             (line   82)
* StartElementHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line  262)
* startElementNS() (xml.sax.handler.ContentHandler 的方法): ContentHandler 物件.
                                                             (line  102)
* STARTF_FORCEOFFFEEDBACK (於 subprocess 模組中): Windows Constants.
                                                             (line   47)
* STARTF_FORCEONFEEDBACK (於 subprocess 模組中): Windows Constants.
                                                             (line   38)
* STARTF_USESHOWWINDOW (於 subprocess 模組中): Windows Constants.
                                                             (line   33)
* STARTF_USESTDHANDLES (於 subprocess 模組中): Windows Constants.
                                                             (line   27)
* startfile() (於 os 模組中):            行程管理.           (line  701)
* StartNamespaceDeclHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line  319)
* startPrefixMapping() (xml.sax.handler.ContentHandler 的方法): ContentHandler 物件.
                                                             (line   49)
* StartResponse (wsgiref.types 中的類別): wsgiref types -- 用於靜態型別檢查的 WSGI 型別.
                                                             (line   10)
* startswith() (bytearray 的方法):       Bytes and Bytearray Operations.
                                                             (line  251)
* startswith() (bytes 的方法):           Bytes and Bytearray Operations.
                                                             (line  251)
* startswith() (str 的方法):             String Methods<2>.  (line  576)
* startTest() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  347)
* startTestRun() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  356)
* starttls() (imaplib.IMAP4 的方法):     IMAP4 物件.         (line  297)
* starttls() (smtplib.SMTP 的方法):      SMTP 物件.          (line  184)
* STARTUPINFO (subprocess 中的類別):     Windows Popen Helpers.
                                                             (line    9)
* stat_result (os 中的類別):             Files and Directories.
                                                             (line 1127)
* stat() (os.DirEntry 的方法):           Files and Directories.
                                                             (line 1037)
* stat() (pathlib.Path 的方法):          Querying file type and status.
                                                             (line   12)
* stat() (poplib.POP3 的方法):           POP3 物件.          (line   52)
* stat() (於 os 模組中):                 Files and Directories.
                                                             (line 1072)
* state() (tkinter.ttk.Widget 的方法):   ttk Widget.         (line   25)
* statement grouping（陳述式群組）:      Indentation.        (line    6)
* statement（陳述式）:                   術語表.             (line 1181)
* statement（陳述式）;assert:            assert 陳述式.      (line    6)
* statement（陳述式）;assert <1>:        實體例外.           (line   10)
* statement（陳述式）;assignment（賦值）、annotated（註釋）: Annotated assignment statements.
                                                             (line    6)
* statement（陳述式）;assignment（賦值）、augmented（增強）: Augmented assignment statements.
                                                             (line    6)
* statement（陳述式）;async def:         協程<2>.            (line    8)
* statement（陳述式）;async for:         協程函式定義.       (line   28)
* statement（陳述式）;async with:        async for 陳述式.   (line   42)
* statement（陳述式）;break:             break 陳述式.       (line    6)
* statement（陳述式）;break <1>:         The while statement.
                                                             (line   17)
* statement（陳述式）;break <2>:         The for statement.  (line   21)
* statement（陳述式）;break <3>:         except* 子句.       (line   57)
* statement（陳述式）;break <4>:         finally clause.     (line   29)
* statement（陳述式）;class（類別）:     類別定義.           (line    6)
* statement（陳述式）;continue:          continue 陳述式.    (line    6)
* statement（陳述式）;continue <1>:      The while statement.
                                                             (line   17)
* statement（陳述式）;continue <2>:      The for statement.  (line   21)
* statement（陳述式）;continue <3>:      except* 子句.       (line   56)
* statement（陳述式）;continue <4>:      finally clause.     (line   29)
* statement（陳述式）;def:               函式定義.           (line    6)
* statement（陳述式）;del:               Basic customization.
                                                             (line   55)
* statement（陳述式）;del <1>:           del 陳述式<2>.      (line    6)
* statement（陳述式）;del <2>:           Mutable Sequence Types.
                                                             (line   16)
* statement（陳述式）;del <3>:           Mapping Types --- dict.
                                                             (line    6)
* statement（陳述式）;except:            內建的例外.         (line    6)
* statement（陳述式）;for:               for 陳述式.         (line    6)
* statement（陳述式）;for <1>:           break 陳述式.       (line    6)
* statement（陳述式）;for <2>:           continue 陳述式.    (line    6)
* statement（陳述式）;for <3>:           The for statement.  (line    6)
* statement（陳述式）;global:            del 陳述式<2>.      (line   15)
* statement（陳述式）;global <1>:        global 陳述式.      (line    6)
* statement（陳述式）;if:                The if statement.   (line    6)
* statement（陳述式）;if <1>:            真值檢測.           (line    6)
* statement（陳述式）;import（引入）:    模組<2>.            (line    6)
* statement（陳述式）;import（引入） <1>: import 陳述式.     (line    6)
* statement（陳述式）;import（引入） <2>: 內建函式.          (line 1982)
* statement（陳述式）;import（引入） <3>: site --- Site-specific configuration hook.
                                                             (line   52)
* statement（陳述式）;match:             The match statement.
                                                             (line    6)
* statement（陳述式）;nonlocal:          nonlocal 陳述式.    (line    6)
* statement（陳述式）;pass:              pass 陳述式<2>.     (line    6)
* statement（陳述式）;raise:             raise 陳述式.       (line    6)
* statement（陳述式）;raise <1>:         內建的例外.         (line   12)
* statement（陳述式）;return （回傳）:   return 陳述式.      (line    6)
* statement（陳述式）;return （回傳） <1>: except* 子句.     (line   57)
* statement（陳述式）;return （回傳） <2>: finally clause.   (line   29)
* statement（陳述式）;try:               Traceback objects.  (line   31)
* statement（陳述式）;try <1>:           The try statement.  (line    6)
* statement（陳述式）;try <2>:           內建的例外.         (line    6)
* statement（陳述式）;type:              type 陳述式.        (line    6)
* statement（陳述式）;while:             break 陳述式.       (line    6)
* statement（陳述式）;while <1>:         continue 陳述式.    (line    6)
* statement（陳述式）;while <2>:         The while statement.
                                                             (line    6)
* statement（陳述式）;while <3>:         真值檢測.           (line    6)
* statement（陳述式）;with:              With Statement Context Managers.
                                                             (line   14)
* statement（陳述式）;with <1>:          The with statement. (line    6)
* statement（陳述式）;yield:             yield 陳述式.       (line    6)
* static type checker（靜態型別檢查器）: 術語表.             (line 1188)
* static_order() (graphlib.TopologicalSorter 的方法): graphlib —-- 使用類圖 graph-like 結構進行操作的功能.
                                                             (line  140)
* Statistic (tracemalloc 中的類別):      Statistic.          (line    6)
* StatisticDiff (tracemalloc 中的類別):  StatisticDiff.      (line    6)
* statistics() (tracemalloc.Snapshot 的方法): Snapshot.      (line   56)
* StatisticsError:                       例外<3>.            (line    8)
* Stats (pstats 中的類別):               The Stats Class.    (line    9)
* status (http.client.HTTPResponse 的屬性): HTTPResponse 物件.
                                                             (line   61)
* status (urllib.response.addinfourl 的屬性): urllib response --- Response classes used by urllib.
                                                             (line   24)
* status() (imaplib.IMAP4 的方法):       IMAP4 物件.         (line  310)
* statvfs() (於 os 模組中):              Files and Directories.
                                                             (line 1367)
* STD_ERROR_HANDLE (於 subprocess 模組中): Windows Constants.
                                                             (line   18)
* STD_INPUT_HANDLE (於 subprocess 模組中): Windows Constants.
                                                             (line    8)
* STD_OUTPUT_HANDLE (於 subprocess 模組中): Windows Constants.
                                                             (line   13)
* stderr (asyncio.subprocess.Process 的屬性): Interacting with Subprocesses.
                                                             (line  125)
* stderr (subprocess.CalledProcessError 的屬性): Using the subprocess Module.
                                                             (line  229)
* stderr (subprocess.CompletedProcess 的屬性): Using the subprocess Module.
                                                             (line  128)
* stderr (subprocess.Popen 的屬性):      Popen Objects.      (line  127)
* stderr (subprocess.TimeoutExpired 的屬性): Using the subprocess Module.
                                                             (line  193)
* stderr （sys 模組中）:                 I/O objects also known as file objects.
                                                             (line    6)
* stderr (於 sys 模組中):                sys --- 系統特定的參數與函式.
                                                             (line 1758)
* stderr（sys 模組中）:                  Sub-interpreter support.
                                                             (line  112)
* stderr（sys 模組中） <1>:              Sub-interpreter support.
                                                             (line  193)
* stdev (statistics.NormalDist 的屬性):  NormalDist 物件.    (line   31)
* stdev() (於 statistics 模組中):        函式細節.           (line  400)
* stdin (asyncio.subprocess.Process 的屬性): Interacting with Subprocesses.
                                                             (line  115)
* stdin (subprocess.Popen 的屬性):       Popen Objects.      (line  108)
* stdin （sys 模組中）:                  I/O objects also known as file objects.
                                                             (line    6)
* stdin (於 sys 模組中):                 sys --- 系統特定的參數與函式.
                                                             (line 1758)
* stdin（sys 模組中）:                   Sub-interpreter support.
                                                             (line  112)
* stdin（sys 模組中） <1>:               Sub-interpreter support.
                                                             (line  193)
* stdio:                                 I/O objects also known as file objects.
                                                             (line    6)
* stdlib_module_names (於 sys 模組中):   sys --- 系統特定的參數與函式.
                                                             (line 1848)
* stdout (asyncio.subprocess.Process 的屬性): Interacting with Subprocesses.
                                                             (line  120)
* stdout (subprocess.CalledProcessError 的屬性): Using the subprocess Module.
                                                             (line  225)
* stdout (subprocess.CompletedProcess 的屬性): Using the subprocess Module.
                                                             (line  118)
* stdout (subprocess.Popen 的屬性):      Popen Objects.      (line  117)
* stdout (subprocess.TimeoutExpired 的屬性): Using the subprocess Module.
                                                             (line  189)
* stdout （sys 模組中）:                 I/O objects also known as file objects.
                                                             (line    6)
* STDOUT (於 subprocess 模組中):         Using the subprocess Module.
                                                             (line  156)
* stdout (於 sys 模組中):                sys --- 系統特定的參數與函式.
                                                             (line 1758)
* stdout（sys 模組中）:                  Sub-interpreter support.
                                                             (line  112)
* stdout（sys 模組中） <1>:              Sub-interpreter support.
                                                             (line  193)
* stem (pathlib.PurePath 的屬性):        方法與屬性.         (line  157)
* step (pdb command):                    Debugger Commands.  (line  196)
* step (range 的屬性):                   Ranges.             (line   70)
* step （slice 物件屬性）:               Slice objects.      (line   10)
* step (slice 的屬性):                   內建函式.           (line 1601)
* step() (tkinter.ttk.Progressbar 的方法): ttk Progressbar.  (line   15)
* step（切片物件屬性）:                  Slicings.           (line   26)
* stls() (poplib.POP3 的方法):           POP3 物件.          (line  114)
* stop (range 的屬性):                   Ranges.             (line   66)
* stop （slice 物件屬性）:               Slice objects.      (line   10)
* stop (slice 的屬性):                   內建函式.           (line 1599)
* stop_here() (bdb.Bdb 的方法):          bdb --- 偵錯器框架. (line  247)
* STOP_ITERATION (monitoring event):     事件.               (line   81)
* stop() (asyncio.loop 的方法):          啟動和停止迴圈.     (line   28)
* stop() (logging.handlers.QueueListener 的方法): QueueListener.
                                                             (line   81)
* stop() (tkinter.ttk.Progressbar 的方法): ttk Progressbar.  (line   21)
* stop() (unittest.TestResult 的方法):   Loading and running tests.
                                                             (line  327)
* stop() (於 tracemalloc 模組中):        函式<10>.           (line   98)
* stop（切片物件屬性）:                  Slicings.           (line   26)
* StopAsyncIteration:                    實體例外.           (line  246)
* StopIteration:                         實體例外.           (line  220)
* stopListening() (於 logging.config 模組中): Configuration functions.
                                                             (line  174)
* stopTest() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  351)
* stopTestRun() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  362)
* storbinary() (ftplib.FTP 的方法):      FTP 物件.           (line  192)
* Store (ast 中的類別):                  變數.               (line   10)
* STORE_ACTIONS (optparse.Option 的屬性): Adding new actions.
                                                             (line   35)
* STORE_ATTR (opcode):                   Python Bytecode Instructions.
                                                             (line  595)
* STORE_DEREF (opcode):                  Python Bytecode Instructions.
                                                             (line  968)
* STORE_FAST (opcode):                   Python Bytecode Instructions.
                                                             (line  934)
* STORE_GLOBAL (opcode):                 Python Bytecode Instructions.
                                                             (line  616)
* STORE_NAME (opcode):                   Python Bytecode Instructions.
                                                             (line  553)
* STORE_SLICE (opcode):                  Python Bytecode Instructions.
                                                             (line  281)
* STORE_SUBSCR (opcode):                 Python Bytecode Instructions.
                                                             (line  253)
* store() (imaplib.IMAP4 的方法):        IMAP4 物件.         (line  314)
* storlines() (ftplib.FTP 的方法):       FTP 物件.           (line  220)
* str (內建類別):                        Text Sequence Type --- str.
                                                             (line   45)
* str_digits_check_threshold (sys.int_info 的屬性): sys --- 系統特定的參數與函式.
                                                             (line 1119)
* str() (於 locale 模組中):              locale --- 國際化服務.
                                                             (line  477)
* str（內建類別）;（亦請見 string）:     Ranges.             (line  126)
* strcoll() (於 locale 模組中):          locale --- 國際化服務.
                                                             (line  430)
* StreamError:                           tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  212)
* StreamHandler (logging 中的類別):      StreamHandler.      (line   11)
* StreamReader (asyncio 中的類別):       StreamReader.       (line    6)
* StreamReader (codecs 中的類別):        StreamReader 物件.  (line   10)
* streamreader (codecs.CodecInfo 的屬性): codecs --- 編解碼器註冊表和基底類別.
                                                             (line   87)
* StreamReaderWriter (codecs 中的類別):  StreamReaderWriter 物件.
                                                             (line   12)
* StreamRecoder (codecs 中的類別):       StreamRecoder 物件. (line   13)
* StreamRequestHandler (socketserver 中的類別): Request Handler Objects.
                                                             (line   56)
* streams（串流）:                       codecs --- 編解碼器註冊表和基底類別.
                                                             (line    8)
* StreamWriter (asyncio 中的類別):       StreamWriter.       (line    6)
* StreamWriter (codecs 中的類別):        StreamWriter 物件.  (line   10)
* streamwriter (codecs.CodecInfo 的屬性): codecs --- 編解碼器註冊表和基底類別.
                                                             (line   87)
* StrEnum (enum 中的類別):               資料型別<2>.        (line  364)
* strerror (OSError 的屬性):             實體例外.           (line  153)
* strerror() (於 os 模組中):             行程參數.           (line  530)
* strerror（C 函式）:                    Raising exceptions. (line   57)
* strftime() (datetime.date 的方法):     date 物件.          (line  298)
* strftime() (datetime.datetime 的方法): datetime 物件.      (line  749)
* strftime() (datetime.time 的方法):     time 物件.          (line  222)
* strftime() (於 time 模組中):           函式<4>.            (line  267)
* strict (csv.Dialect 的屬性):           Dialect 與格式參數. (line   64)
* STRICT (enum.FlagBoundary 的屬性):     資料型別<2>.        (line  619)
* strict (於 email.policy 模組中):       email policy Policy Objects.
                                                             (line  531)
* strict_domain (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy 物件.
                                                             (line   95)
* strict_errors() (於 codecs 模組中):    Error Handlers.     (line  141)
* strict_ns_domain (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy 物件.
                                                             (line  117)
* strict_ns_set_initial_dollar (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy 物件.
                                                             (line  122)
* strict_ns_set_path (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy 物件.
                                                             (line  127)
* strict_ns_unverifiable (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy 物件.
                                                             (line  112)
* strict_rfc2965_unverifiable (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy 物件.
                                                             (line  103)
* strict;error handler's name（錯誤處理器名稱）: Error Handlers.
                                                             (line   15)
* STRIDED (inspect.BufferFlags 的屬性):  Buffer flags.       (line   37)
* STRIDED_RO (inspect.BufferFlags 的屬性): Buffer flags.     (line   39)
* STRIDES (inspect.BufferFlags 的屬性):  Buffer flags.       (line   23)
* strides (memoryview 的屬性):           Memory Views.       (line  458)
* string (re.Match 的屬性):              Match Objects.      (line  210)
* STRING (於 token 模組中):              token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   46)
* string literal（字串常數）:            Literals.           (line    8)
* string_at() (於 ctypes 模組中):        Utility functions.  (line  191)
* string（字串）;__format__() （物件方法）: Basic customization.
                                                             (line  151)
* string（字串）;__str__() （物件方法）: Basic customization.
                                                             (line  130)
* string（字串）;conversion:             Basic customization.
                                                             (line  151)
* string（字串）;conversion <1>:         Expression statements.
                                                             (line   17)
* string（字串）;format()（內建函式）:   內建函式.           (line  700)
* string（字串）;formatted literal（格式化常數）: String literal concatenation.
                                                             (line   24)
* string（字串）;formatting（格式化）、printf: printf-style String Formatting.
                                                             (line    6)
* string（字串）;immutable sequences（不可變序列）: Immutable sequences.
                                                             (line   13)
* string（字串）;interpolated literal（插值常數）: String literal concatenation.
                                                             (line   24)
* string（字串）;interpolation（插值）、printf: printf-style String Formatting.
                                                             (line    6)
* string（字串）;item（項目）:           Subscriptions.      (line   55)
* string（字串）;methods（方法）:        Text Sequence Type --- str.
                                                             (line   87)
* string（字串）;object representation（物件表示）: Finalization and De-allocation.
                                                             (line   91)
* string（字串）;PyObject_Str（C 函式）: 物件協定.           (line  346)
* string（字串）;str() （內建函式）:     內建函式.           (line 1694)
* string（字串）;str（內建類別）:        Text Sequence Type --- str.
                                                             (line   45)
* string（字串）;text sequence type（文字序列型別）: Ranges. (line  126)
* StringIO (io 中的類別):                文字 I/O<2>.        (line  238)
* strings（字串）, documentation（說明文件）: 定義函式 function.
                                                             (line   20)
* strings（字串）, documentation（說明文件） <1>: 說明文件字串 Documentation Strings.
                                                             (line    6)
* strip_dirs() (pstats.Stats 的方法):    The Stats Class.    (line   34)
* strip() (bytearray 的方法):            Bytes and Bytearray Operations.
                                                             (line  441)
* strip() (bytes 的方法):                Bytes and Bytearray Operations.
                                                             (line  441)
* strip() (str 的方法):                  String Methods<2>.  (line  583)
* stripspaces (curses.textpad.Textbox 的屬性): Textbox objects.
                                                             (line  115)
* strong reference（強參照）:            術語表.             (line 1194)
* strptime() (datetime.datetime 的類別方法): datetime 物件.  (line  249)
* strptime() (於 time 模組中):           函式<4>.            (line  399)
* strsignal() (於 signal 模組中):        模組內容<5>.        (line  295)
* Struct (struct 中的類別):              Classes<2>.         (line    8)
* struct_time (time 中的類別):           函式<4>.            (line  426)
* structmember.h:                        Member types.       (line   85)
* Structure (ctypes 中的類別):           Structured data types.
                                                             (line   33)
* strxfrm() (於 locale 模組中):          locale --- 國際化服務.
                                                             (line  437)
* STX (於 curses.ascii 模組中):          curses ascii --- ASCII 字元的工具程式.
                                                             (line   25)
* Style (tkinter.ttk 中的類別):          Ttk Styling.        (line   20)
* Sub (ast 中的類別):                    運算式<2>.          (line   52)
* SUB (於 curses.ascii 模組中):          curses ascii --- ASCII 字元的工具程式.
                                                             (line  103)
* sub() (re.Pattern 的方法):             Regular Expression Objects.
                                                             (line   96)
* sub() (於 operator 模組中):            operator --- 標準運算子替代函式.
                                                             (line  147)
* sub() (於 re 模組中):                  Functions.          (line  171)
* subclassing（子類別化）;immutable types（不可變型別）: Basic customization.
                                                             (line    8)
* subdirs (filecmp.dircmp 的屬性):       The dircmp class.   (line  103)
* SubElement() (於 xml.etree.ElementTree 模組中): 函式<8>.   (line  208)
* subgroup() (BaseExceptionGroup 的方法): 例外群組.          (line   37)
* submit() (concurrent.futures.Executor 的方法): Executor 物件.
                                                             (line   11)
* submodule_search_locations (importlib.machinery.ModuleSpec 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  399)
* subn() (re.Pattern 的方法):            Regular Expression Objects.
                                                             (line  101)
* subn() (於 re 模組中):                 Functions.          (line  246)
* subnet_of() (ipaddress.IPv4Network 的方法): Network objects.
                                                             (line  215)
* subnet_of() (ipaddress.IPv6Network 的方法): Network objects.
                                                             (line  348)
* subnets() (ipaddress.IPv4Network 的方法): Network objects. (line  173)
* subnets() (ipaddress.IPv6Network 的方法): Network objects. (line  344)
* Subnormal (decimal 中的類別):          Signals.            (line   86)
* suboffsets (memoryview 的屬性):        Memory Views.       (line  467)
* subpad() (curses.window 的方法):       Window Objects.     (line  527)
* subprocess_exec() (asyncio.loop 的方法): 運行子行程.       (line   14)
* subprocess_shell() (asyncio.loop 的方法): 運行子行程.      (line   99)
* SubprocessError:                       Using the subprocess Module.
                                                             (line  162)
* SubprocessProtocol (asyncio 中的類別): Base Protocols.     (line   24)
* SubprocessTransport (asyncio 中的類別): Transports Hierarchy.
                                                             (line   50)
* subscribe() (imaplib.IMAP4 的方法):    IMAP4 物件.         (line  338)
* Subscript (ast 中的類別):              下標 Subscripting.  (line    6)
* subscript（下標）;assignment（賦值）:  Mutable Sequence Types.
                                                             (line   16)
* subscript（下標）;operation（操作）:   Common Sequence Operations.
                                                             (line   21)
* subscription（下標）:                  Sequences.          (line    6)
* subscription（下標） <1>:              Mutable sequences.  (line    6)
* subscription（下標） <2>:              Mappings.           (line    6)
* subscription（下標） <3>:              Subscriptions.      (line    6)
* subscription（下標）;assignment（賦值）: Assignment statements.
                                                             (line  101)
* subsequent_indent (textwrap.TextWrapper 的屬性): textwrap --- 文字包裝與填充.
                                                             (line  216)
* substitute() (string.Template 的方法): 模板字串.           (line   38)
* subTest() (unittest.TestCase 的方法):  Test cases.         (line  105)
* subtract() (collections.Counter 的方法): Counter 物件.     (line   80)
* subtract() (decimal.Context 的方法):   Context objects.    (line  521)
* subtraction（減）:                     Binary arithmetic operations.
                                                             (line   83)
* subtype (email.headerregistry.ContentTypeHeader 的屬性): email headerregistry：自訂標頭物件.
                                                             (line  278)
* subwin() (curses.window 的方法):       Window Objects.     (line  534)
* successful() (multiprocessing.pool.AsyncResult 的方法): Process Pools.
                                                             (line  216)
* suffix (pathlib.PurePath 的屬性):      方法與屬性.         (line  133)
* suffix_map (mimetypes.MimeTypes 的屬性): MimeTypes 物件.   (line   23)
* suffix_map (於 mimetypes 模組中):      mimetypes --- 將檔案名稱對映到 MIME 類型.
                                                             (line  141)
* suffixes (pathlib.PurePath 的屬性):    方法與屬性.         (line  146)
* suite（套裝）:                         複合陳述式.         (line   18)
* suiteClass (unittest.TestLoader 的屬性): Loading and running tests.
                                                             (line  201)
* sum_list():                            參照計數詳細資訊.   (line  122)
* sum_sequence():                        參照計數詳細資訊.   (line  149)
* sum_sequence() <1>:                    例外<17>.           (line   46)
* summarize_address_range() (於 ipaddress 模組中): Other Module Level Functions.
                                                             (line   27)
* summarize() (doctest.DocTestRunner 的方法): DocTestRunner 物件.
                                                             (line  122)
* sumprod() (於 math 模組中):            數論與表現函式.     (line  253)
* SUNDAY (於 calendar 模組中):           calendar --- 日曆相關函式.
                                                             (line  336)
* super (pyclbr.Class 的屬性):           Class Objects.      (line   42)
* super (內建類別):                      內建函式.           (line 1723)
* supernet_of() (ipaddress.IPv4Network 的方法): Network objects.
                                                             (line  226)
* supernet_of() (ipaddress.IPv6Network 的方法): Network objects.
                                                             (line  350)
* supernet() (ipaddress.IPv4Network 的方法): Network objects.
                                                             (line  199)
* supernet() (ipaddress.IPv6Network 的方法): Network objects.
                                                             (line  346)
* supports_bytes_environ (於 os 模組中): 行程參數.           (line  536)
* supports_dir_fd (於 os 模組中):        Files and Directories.
                                                             (line 1409)
* supports_effective_ids (於 os 模組中): Files and Directories.
                                                             (line 1434)
* supports_fd (於 os 模組中):            Files and Directories.
                                                             (line 1453)
* supports_follow_symlinks (於 os 模組中): Files and Directories.
                                                             (line 1472)
* supports_unicode_filenames (於 os.path 模組中): os path --- 常見的路徑名操作.
                                                             (line  472)
* SupportsAbs (typing 中的類別):         協定<2>.            (line    9)
* SupportsBytes (typing 中的類別):       協定<2>.            (line   14)
* SupportsComplex (typing 中的類別):     協定<2>.            (line   18)
* SupportsFloat (typing 中的類別):       協定<2>.            (line   22)
* SupportsIndex (typing 中的類別):       協定<2>.            (line   26)
* SupportsInt (typing 中的類別):         協定<2>.            (line   32)
* SupportsRound (typing 中的類別):       協定<2>.            (line   36)
* suppress() (於 contextlib 模組中):     Utilities.          (line  269)
* SuppressCrashReport (test.support 中的類別): test support --- Python 測試套件的工具.
                                                             (line  746)
* surrogateescape;error handler's name（錯誤處理器名稱）: Error Handlers.
                                                             (line   15)
* surrogatepass;error handler's name（錯誤處理器名稱）: Error Handlers.
                                                             (line   73)
* SW_HIDE (於 subprocess 模組中):        Windows Constants.  (line   23)
* SWAP (opcode):                         Python Bytecode Instructions.
                                                             (line  161)
* swap_attr() (於 test.support 模組中):  test support --- Python 測試套件的工具.
                                                             (line  366)
* swap_item() (於 test.support 模組中):  test support --- Python 測試套件的工具.
                                                             (line  383)
* swapcase() (bytearray 的方法):         Bytes and Bytearray Operations.
                                                             (line  662)
* swapcase() (bytes 的方法):             Bytes and Bytearray Operations.
                                                             (line  662)
* swapcase() (str 的方法):               String Methods<2>.  (line  607)
* Symbol (symtable 中的類別):            檢查符號表.         (line  179)
* SymbolTable (symtable 中的類別):       檢查符號表.         (line   49)
* SymbolTableType (symtable 中的類別):   檢查符號表.         (line    6)
* symlink_to() (pathlib.Path 的方法):    建立檔案與目錄.     (line   41)
* symlink() (於 os 模組中):              Files and Directories.
                                                             (line 1495)
* symmetric_difference_update() (frozenset 的方法): Set Types --- set frozenset.
                                                             (line  188)
* symmetric_difference() (frozenset 的方法): Set Types --- set frozenset.
                                                             (line  116)
* symtable() (於 symtable 模組中):       產生符號表.         (line    6)
* SYMTYPE (於 tarfile 模組中):           tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  276)
* SYN (於 curses.ascii 模組中):          curses ascii --- ASCII 字元的工具程式.
                                                             (line   91)
* sync() (dbm.dumb.dumbdbm 的方法):      dbm dumb --- 可攜式 DBM 實作.
                                                             (line   78)
* sync() (dbm.gnu.gdbm 的方法):          dbm gnu --- GNU 資料庫管理器.
                                                             (line  105)
* sync() (shelve.Shelf 的方法):          shelve --- Python object persistence.
                                                             (line   69)
* sync() (於 os 模組中):                 Files and Directories.
                                                             (line 1540)
* syncdown() (curses.window 的方法):     Window Objects.     (line  544)
* synchronized() (於 multiprocessing.sharedctypes 模組中): multiprocessing sharedctypes 模組.
                                                             (line   88)
* SyncManager (multiprocessing.managers 中的類別): Managers. (line  150)
* syncok() (curses.window 的方法):       Window Objects.     (line  550)
* syncup() (curses.window 的方法):       Window Objects.     (line  555)
* syntax（語法）:                        Notation.           (line    6)
* SyntaxErr:                             例外<15>.           (line   93)
* SyntaxError:                           實體例外.           (line  253)
* SyntaxWarning:                         警告.               (line   40)
* sys_version (http.server.BaseHTTPRequestHandler 的屬性): http server — HTTP 伺服器.
                                                             (line  142)
* sys.exc_info:                          Traceback objects.  (line    6)
* sys.exception:                         Traceback objects.  (line    6)
* sys.last_traceback:                    Traceback objects.  (line    6)
* sys.meta_path:                         The meta path.      (line    6)
* sys.modules:                           The module cache.   (line    6)
* sys.path:                              Path entry finders. (line    6)
* sys.path_hooks:                        Path entry finders. (line    6)
* sys.path_importer_cache:               Path entry finders. (line    6)
* sys.stderr:                            I/O objects also known as file objects.
                                                             (line    6)
* sys.stdin:                             I/O objects also known as file objects.
                                                             (line    6)
* sys.stdout:                            I/O objects also known as file objects.
                                                             (line    6)
* sysconf_names (於 os 模組中):          Miscellaneous System Information.
                                                             (line   87)
* sysconf() (於 os 模組中):              Miscellaneous System Information.
                                                             (line   77)
* syslog() (於 syslog 模組中):           syslog --- Unix syslog 函式庫例程.
                                                             (line   20)
* SysLogHandler (logging.handlers 中的類別): SysLogHandler.  (line   10)
* system_alias() (於 platform 模組中):   跨平台.             (line  115)
* system_must_validate_cert() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  454)
* system() (於 os 模組中):               行程管理.           (line  756)
* system() (於 platform 模組中):         跨平台.             (line  106)
* SystemError:                           實體例外.           (line  309)
* SystemError（內建例外）:               模組物件.           (line   61)
* SystemError（內建例外） <1>:           模組物件.           (line   87)
* SystemExit:                            實體例外.           (line  320)
* SystemExit（內建例外）:                例外.               (line   26)
* systemId (xml.dom.DocumentType 的屬性): DocumentType 物件. (line   22)
* SystemRandom (random 中的類別):        替代產生器.         (line   44)
* SystemRandom (secrets 中的類別):       亂數.               (line    9)
* SystemRoot:                            Popen Constructor.  (line  307)
* T_BOOL（C 巨集）:                      Member types.       (line   85)
* T_BYTE（C 巨集）:                      Member types.       (line   85)
* T_CHAR（C 巨集）:                      Member types.       (line   85)
* T_DOUBLE（C 巨集）:                    Member types.       (line   85)
* T_FLOAT（C 巨集）:                     Member types.       (line   85)
* T_FMT (於 locale 模組中):              locale --- 國際化服務.
                                                             (line  201)
* T_FMT_AMPM (於 locale 模組中):         locale --- 國際化服務.
                                                             (line  207)
* T_INT（C 巨集）:                       Member types.       (line   85)
* T_LONG（C 巨集）:                      Member types.       (line   85)
* T_LONGLONG（C 巨集）:                  Member types.       (line   85)
* T_NONE (C macro):                      Member types.       (line   96)
* T_OBJECT (C macro):                    Member types.       (line   90)
* T_OBJECT_EX（C 巨集）:                 Member types.       (line   85)
* T_PYSSIZET（C 巨集）:                  Member types.       (line   85)
* T_SHORT（C 巨集）:                     Member types.       (line   85)
* T_STRING_INPLACE（C 巨集）:            Member types.       (line   85)
* T_STRING（C 巨集）:                    Member types.       (line   85)
* T_UBYTE（C 巨集）:                     Member types.       (line   85)
* T_UINT（C 巨集）:                      Member types.       (line   85)
* T_ULONG（C 巨集）:                     Member types.       (line   85)
* T_ULONGULONG（C 巨集）:                Member types.       (line   85)
* T_USHORT（C 巨集）:                    Member types.       (line   85)
* TAB (於 curses.ascii 模組中):          curses ascii --- ASCII 字元的工具程式.
                                                             (line   46)
* tab() (tkinter.ttk.Notebook 的方法):   ttk Notebook.       (line   60)
* tab（定位字元）:                       Indentation.        (line    6)
* TabError:                              實體例外.           (line  304)
* tabs() (tkinter.ttk.Notebook 的方法):  ttk Notebook.       (line   69)
* tabsize (textwrap.TextWrapper 的屬性): textwrap --- 文字包裝與填充.
                                                             (line  173)
* tag (xml.etree.ElementTree.Element 的屬性): Element 物件.  (line   16)
* tag_bind() (tkinter.ttk.Treeview 的方法): ttk Treeview.    (line  292)
* tag_configure() (tkinter.ttk.Treeview 的方法): ttk Treeview.
                                                             (line  298)
* tag_has() (tkinter.ttk.Treeview 的方法): ttk Treeview.     (line  308)
* tagName (xml.dom.Element 的屬性):      Element Objects.    (line    9)
* tail (xml.etree.ElementTree.Element 的屬性): Element 物件. (line   21)
* take_snapshot() (於 tracemalloc 模組中): 函式<10>.         (line  110)
* takewhile() (於 itertools 模組中):     Itertool 函式.      (line  508)
* tan() (於 cmath 模組中):               三角函數.           (line   28)
* tan() (於 math 模組中):                Trigonometric functions.
                                                             (line   69)
* tanh() (於 cmath 模組中):              雙曲函數.           (line   29)
* tanh() (於 math 模組中):               Hyperbolic functions.
                                                             (line   29)
* tar_filter() (於 tarfile 模組中):      Default named filters.
                                                             (line   15)
* TarError:                              tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  198)
* TarFile (tarfile 中的類別):            TarFile 物件.       (line   22)
* tarfile 命令列選項; -c:                命令列選項<2>.      (line   11)
* tarfile 命令列選項; -create:           命令列選項<2>.      (line   11)
* tarfile 命令列選項; -e:                命令列選項<2>.      (line   16)
* tarfile 命令列選項; -extract:          命令列選項<2>.      (line   16)
* tarfile 命令列選項; -filter:           命令列選項<2>.      (line   31)
* tarfile 命令列選項; -l:                命令列選項<2>.      (line    6)
* tarfile 命令列選項; -list:             命令列選項<2>.      (line    6)
* tarfile 命令列選項; -t:                命令列選項<2>.      (line   22)
* tarfile 命令列選項; -test:             命令列選項<2>.      (line   22)
* tarfile 命令列選項; -v:                命令列選項<2>.      (line   27)
* tarfile 命令列選項; -verbose:          命令列選項<2>.      (line   27)
* target:                                Assignment statements.
                                                             (line   27)
* target (xml.dom.ProcessingInstruction 的屬性): ProcessingInstruction 物件.
                                                             (line    9)
* target;list（串列）:                   Assignment statements.
                                                             (line   27)
* target;list（串列） <1>:               The for statement.  (line    6)
* target;list（串列）;assignment（賦值）: Assignment statements.
                                                             (line   35)
* TarInfo (tarfile 中的類別):            TarInfo 物件.       (line   33)
* tarinfo (tarfile.FilterError 的屬性):  tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  232)
* Task (asyncio 中的類別):               Task Object.        (line    6)
* task_done() (asyncio.Queue 的方法):    Queue.              (line   94)
* task_done() (multiprocessing.JoinableQueue 的方法): Pipes and Queues.
                                                             (line  250)
* task_done() (queue.Queue 的方法):      佇列物件.           (line   65)
* TaskGroup (asyncio 中的類別):          Task Groups.        (line    9)
* tau (於 cmath 模組中):                 常數<3>.            (line   14)
* tau (於 math 模組中):                  常數<2>.            (line   16)
* tb_frame （traceback 屬性）:           Traceback objects.  (line   31)
* tb_frame (traceback 的屬性):           Traceback objects.  (line   33)
* tb_lasti （traceback 屬性）:           Traceback objects.  (line   31)
* tb_lasti (traceback 的屬性):           Traceback objects.  (line   43)
* tb_lineno （traceback 屬性）:          Traceback objects.  (line   31)
* tb_lineno (traceback 的屬性):          Traceback objects.  (line   40)
* tb_locals (unittest.TestResult 的屬性): Loading and running tests.
                                                             (line  311)
* tb_next （traceback 屬性）:            Traceback objects.  (line   51)
* tb_next (traceback 的屬性):            Traceback objects.  (line   51)
* tbreak (pdb command):                  Debugger Commands.  (line  121)
* tcdrain() (於 termios 模組中):         termios --- POSIX 風格 tty 控制.
                                                             (line   65)
* tcflow() (於 termios 模組中):          termios --- POSIX 風格 tty 控制.
                                                             (line   76)
* tcflush() (於 termios 模組中):         termios --- POSIX 風格 tty 控制.
                                                             (line   70)
* tcgetattr() (於 termios 模組中):       termios --- POSIX 風格 tty 控制.
                                                             (line   28)
* tcgetpgrp() (於 os 模組中):            File Descriptor Operations.
                                                             (line  876)
* tcgetwinsize() (於 termios 模組中):    termios --- POSIX 風格 tty 控制.
                                                             (line   83)
* Tcl() (於 tkinter 模組中):             Tkinter Modules.    (line   94)
* TCPServer (socketserver 中的類別):     socketserver --- 用於網路伺服器的框架.
                                                             (line   20)
* TCSADRAIN (於 termios 模組中):         termios --- POSIX 風格 tty 控制.
                                                             (line   50)
* TCSAFLUSH (於 termios 模組中):         termios --- POSIX 風格 tty 控制.
                                                             (line   54)
* TCSANOW (於 termios 模組中):           termios --- POSIX 風格 tty 控制.
                                                             (line   46)
* tcsendbreak() (於 termios 模組中):     termios --- POSIX 風格 tty 控制.
                                                             (line   59)
* tcsetattr() (於 termios 模組中):       termios --- POSIX 風格 tty 控制.
                                                             (line   39)
* tcsetpgrp() (於 os 模組中):            File Descriptor Operations.
                                                             (line  883)
* tcsetwinsize() (於 termios 模組中):    termios --- POSIX 風格 tty 控制.
                                                             (line   91)
* tearDown() (unittest.TestCase 的方法): Test cases.         (line   41)
* tearDownClass() (unittest.TestCase 的方法): Test cases.    (line   69)
* tee() (於 itertools 模組中):           Itertool 函式.      (line  525)
* teleport() (於 turtle 模組中):         Turtle motion.      (line  104)
* tell() (io.IOBase 的方法):             I/O 基礎類別.       (line  121)
* tell() (io.TextIOBase 的方法):         文字 I/O<2>.        (line   88)
* tell() (io.TextIOWrapper 的方法):      文字 I/O<2>.        (line  232)
* tell() (mmap.mmap 的方法):             mmap --- 記憶體映射檔案的支援.
                                                             (line  316)
* tell() (sqlite3.Blob 的方法):          Blob 物件.          (line   59)
* tell() (wave.Wave_read 的方法):        Wave_read 物件.     (line   82)
* tell() (wave.Wave_write 的方法):       Wave_write 物件.    (line   62)
* TEMP:                                  Redirection of local data registry and temporary paths.
                                                             (line    7)
* TEMP <1>:                              tempfile --- 生成臨時檔案和目錄.
                                                             (line  279)
* temp_cwd() (於 test.support.os_helper 模組中): test support os_helper --- 用於 os 測試的工具.
                                                             (line  134)
* temp_dir() (於 test.support.os_helper 模組中): test support os_helper --- 用於 os 測試的工具.
                                                             (line  148)
* temp_umask() (於 test.support.os_helper 模組中): test support os_helper --- 用於 os 測試的工具.
                                                             (line  158)
* tempdir (於 tempfile 模組中):          tempfile --- 生成臨時檔案和目錄.
                                                             (line  321)
* Template (string 中的類別):            模板字串.           (line   33)
* template (string.Template 的屬性):     模板字串.           (line   75)
* temporary (bdb.Breakpoint 的屬性):     bdb --- 偵錯器框架. (line   90)
* temporary（臨時）;file name（檔案名稱）: tempfile --- 生成臨時檔案和目錄.
                                                             (line    8)
* temporary（臨時）;file（檔案）:        tempfile --- 生成臨時檔案和目錄.
                                                             (line    8)
* TemporaryDirectory (tempfile 中的類別): tempfile --- 生成臨時檔案和目錄.
                                                             (line  157)
* TemporaryFile() (於 tempfile 模組中):  tempfile --- 生成臨時檔案和目錄.
                                                             (line   24)
* teredo (ipaddress.IPv6Address 的屬性): Address objects.    (line  309)
* TERM:                                  函式<5>.            (line  485)
* TERM <1>:                              函式<5>.            (line  512)
* termattrs() (於 curses 模組中):        函式<5>.            (line  504)
* terminal_size (os 中的類別):           Querying the size of a terminal.
                                                             (line   25)
* terminate() (asyncio.subprocess.Process 的方法): Interacting with Subprocesses.
                                                             (line   95)
* terminate() (asyncio.SubprocessTransport 的方法): Subprocess Transports.
                                                             (line   49)
* terminate() (multiprocessing.pool.Pool 的方法): Process Pools.
                                                             (line  177)
* terminate() (multiprocessing.Process 的方法): Process 與例外.
                                                             (line  172)
* terminate() (subprocess.Popen 的方法): Popen Objects.      (line   86)
* termination model（終止模型）:         例外.               (line   20)
* terminator (logging.StreamHandler 的屬性): StreamHandler.  (line   47)
* termname() (於 curses 模組中):         函式<5>.            (line  510)
* ternary（三元）;operator（運算子）:    Conditional expressions.
                                                             (line    6)
* ternaryfunc (C type):                  Slot Type typedefs. (line  122)
* test (doctest.DocTestFailure 的屬性):  Debugging.          (line  195)
* test (doctest.UnexpectedException 的屬性): Debugging.      (line  216)
* TEST_DATA_DIR (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  135)
* TEST_HOME_DIR (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  131)
* TEST_HTTP_URL (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  169)
* TEST_SUPPORT_DIR (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  127)
* TestCase (unittest 中的類別):          Test cases.         (line    6)
* TestFailed:                            test support --- Python 測試套件的工具.
                                                             (line   15)
* testfile() (於 doctest 模組中):        基礎 API.           (line   12)
* TESTFN (於 test.support.os_helper 模組中): test support os_helper --- 用於 os 測試的工具.
                                                             (line   18)
* TESTFN_NONASCII (於 test.support.os_helper 模組中): test support os_helper --- 用於 os 測試的工具.
                                                             (line   24)
* TESTFN_UNDECODABLE (於 test.support.os_helper 模組中): test support os_helper --- 用於 os 測試的工具.
                                                             (line   38)
* TESTFN_UNENCODABLE (於 test.support.os_helper 模組中): test support os_helper --- 用於 os 測試的工具.
                                                             (line   32)
* TESTFN_UNICODE (於 test.support.os_helper 模組中): test support os_helper --- 用於 os 測試的工具.
                                                             (line   44)
* TestLoader (unittest 中的類別):        Loading and running tests.
                                                             (line    6)
* testMethodPrefix (unittest.TestLoader 的屬性): Loading and running tests.
                                                             (line  187)
* testmod() (於 doctest 模組中):         基礎 API.           (line   90)
* testNamePatterns (unittest.TestLoader 的屬性): Loading and running tests.
                                                             (line  209)
* TestResult (unittest 中的類別):        Loading and running tests.
                                                             (line  226)
* TestResults (doctest 中的類別):        TestResults objects.
                                                             (line    6)
* testsource() (於 doctest 模組中):      Debugging.          (line  106)
* testsRun (unittest.TestResult 的屬性): Loading and running tests.
                                                             (line  289)
* TestSuite (unittest 中的類別):         Grouping tests.     (line    6)
* testzip() (zipfile.ZipFile 的方法):    ZipFile 物件.       (line  259)
* text (SyntaxError 的屬性):             實體例外.           (line  277)
* text (traceback.TracebackException 的屬性): TracebackException 物件.
                                                             (line  101)
* Text (typing 中的類別):                Aliases to other concrete types.
                                                             (line   20)
* text (xml.etree.ElementTree.Element 的屬性): Element 物件. (line   21)
* text encoding（文字編碼）:             術語表.             (line 1206)
* text file（文字檔案）:                 術語表.             (line 1218)
* text mode（文字模式）:                 內建函式.           (line 1294)
* text_encoding() (於 io 模組中):        高階模組介面.       (line   35)
* text_factory (sqlite3.Connection 的屬性): Connection 物件. (line  802)
* Textbox (curses.textpad 中的類別):     Textbox objects.    (line    8)
* TextCalendar (calendar 中的類別):      calendar --- 日曆相關函式.
                                                             (line  108)
* textdomain() (於 gettext 模組中):      GNU gettext API.    (line   26)
* textdomain() (於 locale 模組中):       Access to message catalogs.
                                                             (line   12)
* textinput() (於 turtle 模組中):        Input methods.      (line    6)
* TextIO (typing 中的類別):              ABCs for working with IO.
                                                             (line    6)
* TextIOBase (io 中的類別):              文字 I/O<2>.        (line    6)
* TextIOWrapper (io 中的類別):           文字 I/O<2>.        (line   99)
* TextTestResult (unittest 中的類別):    Loading and running tests.
                                                             (line  446)
* TextTestRunner (unittest 中的類別):    Loading and running tests.
                                                             (line  463)
* TextWrapper (textwrap 中的類別):       textwrap --- 文字包裝與填充.
                                                             (line  140)
* TFD_CLOEXEC (於 os 模組中):            Timer File Descriptors.
                                                             (line  203)
* TFD_NONBLOCK (於 os 模組中):           Timer File Descriptors.
                                                             (line  192)
* TFD_TIMER_ABSTIME (於 os 模組中):      Timer File Descriptors.
                                                             (line  213)
* TFD_TIMER_CANCEL_ON_SET (於 os 模組中): Timer File Descriptors.
                                                             (line  224)
* theme_create() (tkinter.ttk.Style 的方法): Ttk Styling.    (line  260)
* theme_names() (tkinter.ttk.Style 的方法): Ttk Styling.     (line  308)
* theme_settings() (tkinter.ttk.Style 的方法): Ttk Styling.  (line  270)
* theme_use() (tkinter.ttk.Style 的方法): Ttk Styling.       (line  312)
* THOUSEP (於 locale 模組中):            locale --- 國際化服務.
                                                             (line  270)
* Thread (threading 中的類別):           Thread Objects.     (line   57)
* thread_info (於 sys 模組中):           sys --- 系統特定的參數與函式.
                                                             (line 1867)
* thread_time_ns() (於 time 模組中):     函式<4>.            (line  532)
* thread_time() (於 time 模組中):        函式<4>.            (line  514)
* thread() (imaplib.IMAP4 的方法):       IMAP4 物件.         (line  342)
* ThreadedChildWatcher (asyncio 中的類別): Process Watchers. (line   90)
* threading_cleanup() (於 test.support.threading_helper 模組中): test support threading_helper --- Utilities for threading tests.
                                                             (line   31)
* threading_setup() (於 test.support.threading_helper 模組中): test support threading_helper --- Utilities for threading tests.
                                                             (line   37)
* ThreadingHTTPServer (http.server 中的類別): http server — HTTP 伺服器.
                                                             (line   37)
* ThreadingMixIn (socketserver 中的類別): Server Creation Notes.
                                                             (line   27)
* ThreadingMock (unittest.mock 中的類別): Mock 類別.         (line  865)
* ThreadingTCPServer (socketserver 中的類別): Server Creation Notes.
                                                             (line   67)
* ThreadingUDPServer (socketserver 中的類別): Server Creation Notes.
                                                             (line   67)
* ThreadingUnixDatagramServer (socketserver 中的類別): Server Creation Notes.
                                                             (line   67)
* ThreadingUnixStreamServer (socketserver 中的類別): Server Creation Notes.
                                                             (line   67)
* ThreadPool (multiprocessing.pool 中的類別): multiprocessing dummy 模組.
                                                             (line   16)
* ThreadPoolExecutor (concurrent.futures 中的類別): ThreadPoolExecutor.
                                                             (line   39)
* threads（執行緒）;POSIX:               _thread --- 低階執行緒 API.
                                                             (line   14)
* threadsafety (於 sqlite3 模組中):      Module constants.   (line   83)
* throw() (coroutine 的方法):            Coroutine Objects.  (line   33)
* throw() (generator 的方法):            Generator-iterator methods.
                                                             (line   38)
* THURSDAY (於 calendar 模組中):         calendar --- 日曆相關函式.
                                                             (line  336)
* ticket_lifetime_hint (ssl.SSLSession 的屬性): SSL session. (line   18)
* tigetflag() (於 curses 模組中):        函式<5>.            (line  515)
* tigetnum() (於 curses 模組中):         函式<5>.            (line  522)
* tigetstr() (於 curses 模組中):         函式<5>.            (line  529)
* TILDE (於 token 模組中):               token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  150)
* tilt() (於 turtle 模組中):             Appearance.         (line  101)
* tiltangle() (於 turtle 模組中):        Appearance.         (line  117)
* time (datetime 中的類別):              time 物件.          (line   10)
* time (ssl.SSLSession 的屬性):          SSL session.        (line   14)
* time (uuid.UUID 的屬性):               uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  115)
* time_hi_version (uuid.UUID 的屬性):    uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  103)
* time_low (uuid.UUID 的屬性):           uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line   97)
* time_mid (uuid.UUID 的屬性):           uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  100)
* time_ns() (於 time 模組中):            函式<4>.            (line  507)
* time() (asyncio.loop 的方法):          排程延遲的回呼函式. (line   47)
* time() (datetime.datetime 的方法):     datetime 物件.      (line  439)
* time() (於 time 模組中):               函式<4>.            (line  479)
* Time2Internaldate() (於 imaplib 模組中): imaplib --- IMAP4 協定客戶端.
                                                             (line  127)
* timedelta (datetime 中的類別):         timedelta 物件.     (line    9)
* TimedRotatingFileHandler (logging.handlers 中的類別): TimedRotatingFileHandler.
                                                             (line   10)
* timegm() (於 calendar 模組中):         calendar --- 日曆相關函式.
                                                             (line  319)
* timeit 命令列選項; -h:                 命令列介面<4>.      (line   42)
* timeit 命令列選項; -help:              命令列介面<4>.      (line   42)
* timeit 命令列選項; -n:                 命令列介面<4>.      (line   12)
* timeit 命令列選項; -number:            命令列介面<4>.      (line   12)
* timeit 命令列選項; -p:                 命令列介面<4>.      (line   24)
* timeit 命令列選項; -process:           命令列介面<4>.      (line   24)
* timeit 命令列選項; -r:                 命令列介面<4>.      (line   16)
* timeit 命令列選項; -repeat:            命令列介面<4>.      (line   16)
* timeit 命令列選項; -s:                 命令列介面<4>.      (line   20)
* timeit 命令列選項; -setup:             命令列介面<4>.      (line   20)
* timeit 命令列選項; -u:                 命令列介面<4>.      (line   32)
* timeit 命令列選項; -unit:              命令列介面<4>.      (line   32)
* timeit 命令列選項; -v:                 命令列介面<4>.      (line   38)
* timeit 命令列選項; -verbose:           命令列介面<4>.      (line   38)
* timeit() (timeit.Timer 的方法):        Python 介面.        (line   61)
* timeit() (於 timeit 模組中):           Python 介面.        (line    8)
* timeout:                               例外<10>.           (line   40)
* Timeout (asyncio 中的類別):            Timeouts.           (line   50)
* timeout (socketserver.BaseServer 的屬性): Server Objects.  (line  114)
* timeout (ssl.SSLSession 的屬性):       SSL session.        (line   16)
* timeout (subprocess.TimeoutExpired 的屬性): Using the subprocess Module.
                                                             (line  177)
* timeout_at() (於 asyncio 模組中):      Timeouts.           (line   98)
* TIMEOUT_MAX (於 _thread 模組中):       _thread --- 低階執行緒 API.
                                                             (line  111)
* TIMEOUT_MAX (於 threading 模組中):     threading --- 基於執行緒的平行性.
                                                             (line  232)
* timeout() (curses.window 的方法):      Window Objects.     (line  560)
* timeout() (於 asyncio 模組中):         Timeouts.           (line    6)
* TimeoutError:                          作業系統例外.       (line  103)
* TimeoutError <1>:                      Process 與例外.     (line  244)
* TimeoutError <2>:                      例外類別.           (line   10)
* TimeoutError <3>:                      例外<8>.            (line   10)
* TimeoutExpired:                        Using the subprocess Module.
                                                             (line  168)
* Timer (threading 中的類別):            Timer Objects.      (line   25)
* Timer (timeit 中的類別):               Python 介面.        (line   36)
* timerfd_create() (於 os 模組中):       Timer File Descriptors.
                                                             (line   11)
* timerfd_gettime_ns() (於 os 模組中):   Timer File Descriptors.
                                                             (line  183)
* timerfd_gettime() (於 os 模組中):      Timer File Descriptors.
                                                             (line  163)
* timerfd_settime_ns() (於 os 模組中):   Timer File Descriptors.
                                                             (line  152)
* timerfd_settime() (於 os 模組中):      Timer File Descriptors.
                                                             (line   84)
* TimerHandle (asyncio 中的類別):        回呼處理.           (line   27)
* times() (於 os 模組中):                行程管理.           (line  791)
* TIMESTAMP (py_compile.PycInvalidationMode 的屬性): py_compile — 編譯 Python 來源檔案.
                                                             (line  102)
* timestamp() (datetime.datetime 的方法): datetime 物件.     (line  594)
* timetuple() (datetime.date 的方法):    date 物件.          (line  209)
* timetuple() (datetime.datetime 的方法): datetime 物件.     (line  548)
* timetz() (datetime.datetime 的方法):   datetime 物件.      (line  448)
* timezone (datetime 中的類別):          timezone 物件.      (line   14)
* timezone (於 time 模組中):             Timezone Constants. (line   17)
* title() (bytearray 的方法):            Bytes and Bytearray Operations.
                                                             (line  687)
* title() (bytes 的方法):                Bytes and Bytearray Operations.
                                                             (line  687)
* title() (str 的方法):                  String Methods<2>.  (line  613)
* title() (於 turtle 模組中):            Methods specific to Screen not inherited from TurtleScreen.
                                                             (line   49)
* Tk:                                    以 Tk 打造圖形使用者介面 Graphical User Interfaces.
                                                             (line    6)
* Tk (tkinter 中的類別):                 Tkinter Modules.    (line   14)
* tk (tkinter.Tk 的屬性):                Tkinter Modules.    (line   70)
* Tk Option Data Types:                  Tk Option Data Types.
                                                             (line    6)
* Tkinter:                               以 Tk 打造圖形使用者介面 Graphical User Interfaces.
                                                             (line    6)
* TLS:                                   ssl --- socket 物件的 TLS/SSL 包裝器.
                                                             (line    8)
* TLSv1 (ssl.TLSVersion 的屬性):         常數<8>.            (line  510)
* TLSv1_1 (ssl.TLSVersion 的屬性):       常數<8>.            (line  512)
* TLSv1_2 (ssl.TLSVersion 的屬性):       常數<8>.            (line  514)
* TLSv1_3 (ssl.TLSVersion 的屬性):       常數<8>.            (line  516)
* TLSVersion (ssl 中的類別):             常數<8>.            (line  493)
* tm_gmtoff (time.struct_time 的屬性):   函式<4>.            (line  467)
* tm_hour (time.struct_time 的屬性):     函式<4>.            (line  444)
* tm_isdst (time.struct_time 的屬性):    函式<4>.            (line  461)
* tm_mday (time.struct_time 的屬性):     函式<4>.            (line  441)
* tm_min (time.struct_time 的屬性):      函式<4>.            (line  447)
* tm_mon (time.struct_time 的屬性):      函式<4>.            (line  438)
* tm_sec (time.struct_time 的屬性):      函式<4>.            (line  450)
* tm_wday (time.struct_time 的屬性):     函式<4>.            (line  455)
* tm_yday (time.struct_time 的屬性):     函式<4>.            (line  458)
* tm_year (time.struct_time 的屬性):     函式<4>.            (line  435)
* tm_zone (time.struct_time 的屬性):     函式<4>.            (line  464)
* TMP:                                   tempfile --- 生成臨時檔案和目錄.
                                                             (line  281)
* TMPDIR:                                Tests<18>.          (line   68)
* TMPDIR <1>:                            tempfile --- 生成臨時檔案和目錄.
                                                             (line  277)
* TO_BOOL (opcode):                      Python Bytecode Instructions.
                                                             (line  218)
* to_bytes() (int 的方法):               整數型別的附加 methods.
                                                             (line   52)
* to_eng_string() (decimal.Context 的方法): Context objects. (line  525)
* to_eng_string() (decimal.Decimal 的方法): Decimal objects. (line  571)
* to_integral_exact() (decimal.Context 的方法): Context objects.
                                                             (line  535)
* to_integral_exact() (decimal.Decimal 的方法): Decimal objects.
                                                             (line  590)
* to_integral_value() (decimal.Decimal 的方法): Decimal objects.
                                                             (line  598)
* to_integral() (decimal.Decimal 的方法): Decimal objects.   (line  584)
* to_sci_string() (decimal.Context 的方法): Context objects. (line  539)
* to_thread() (於 asyncio 模組中):       Running in Threads. (line    6)
* ToASCII() (於 encodings.idna 模組中):  encodings idna --- Internationalized Domain Names in Applications.
                                                             (line   55)
* tobuf() (tarfile.TarInfo 的方法):      TarInfo 物件.       (line   49)
* tobytes() (array.array 的方法):        array --- 高效率的數值型陣列.
                                                             (line  208)
* tobytes() (memoryview 的方法):         Memory Views.       (line  162)
* today() (datetime.date 的類別方法):    date 物件.          (line   29)
* today() (datetime.datetime 的類別方法): datetime 物件.     (line   47)
* tofile() (array.array 的方法):         array --- 高效率的數值型陣列.
                                                             (line  216)
* tok_name (於 token 模組中):            token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   20)
* token:                                 詞法分析.           (line    6)
* Token (contextvars 中的類別):          Context Variables.  (line   75)
* token (shlex.shlex 的屬性):            shlex 物件.         (line  172)
* token_bytes() (於 secrets 模組中):     產生權杖（token）.  (line    9)
* token_hex() (於 secrets 模組中):       產生權杖（token）.  (line   17)
* token_urlsafe() (於 secrets 模組中):   產生權杖（token）.  (line   26)
* TokenError:                            Tokenizing Input.   (line  107)
* tokenize 命令列選項; -e:               Command-Line Usage<3>.
                                                             (line   19)
* tokenize 命令列選項; -exact:           Command-Line Usage<3>.
                                                             (line   19)
* tokenize 命令列選項; -h:               Command-Line Usage<3>.
                                                             (line   15)
* tokenize 命令列選項; -help:            Command-Line Usage<3>.
                                                             (line   15)
* tokenize() (於 tokenize 模組中):       Tokenizing Input.   (line    8)
* tolist() (array.array 的方法):         array --- 高效率的數值型陣列.
                                                             (line  220)
* tolist() (memoryview 的方法):          Memory Views.       (line  203)
* TOMLDecodeError:                       tomllib --- 剖析 TOML 檔案.
                                                             (line   55)
* toordinal() (datetime.date 的方法):    date 物件.          (line  224)
* toordinal() (datetime.datetime 的方法): datetime 物件.     (line  589)
* top_panel() (於 curses.panel 模組中):  函式<6>.            (line   19)
* top() (curses.panel.Panel 的方法):     Panel Objects.      (line   53)
* top() (poplib.POP3 的方法):            POP3 物件.          (line   87)
* TopologicalSorter (graphlib 中的類別): graphlib —-- 使用類圖 graph-like 結構進行操作的功能.
                                                             (line   10)
* toprettyxml() (xml.dom.minidom.Node 的方法): DOM 物件.     (line   72)
* toreadonly() (memoryview 的方法):      Memory Views.       (line  219)
* tostring() (於 xml.etree.ElementTree 模組中): 函式<8>.     (line  221)
* tostringlist() (於 xml.etree.ElementTree 模組中): 函式<8>. (line  243)
* total_changes (sqlite3.Connection 的屬性): Connection 物件.
                                                             (line  812)
* total_nframe (tracemalloc.Traceback 的屬性): Traceback.    (line   28)
* total_ordering() (於 functools 模組中): functools --- 可呼叫物件上的高階函式與操作.
                                                             (line  236)
* total_seconds() (datetime.timedelta 的方法): timedelta 物件.
                                                             (line  220)
* total() (collections.Counter 的方法):  Counter 物件.       (line   94)
* touch() (pathlib.Path 的方法):         建立檔案與目錄.     (line    6)
* touchline() (curses.window 的方法):    Window Objects.     (line  570)
* touchwin() (curses.window 的方法):     Window Objects.     (line  577)
* tounicode() (array.array 的方法):      array --- 高效率的數值型陣列.
                                                             (line  224)
* ToUnicode() (於 encodings.idna 模組中): encodings idna --- Internationalized Domain Names in Applications.
                                                             (line   60)
* towards() (於 turtle 模組中):          Tell Turtle's state.
                                                             (line   15)
* toxml() (xml.dom.minidom.Node 的方法): DOM 物件.           (line   52)
* tparm() (於 curses 模組中):            函式<5>.            (line  536)
* Trace (trace 中的類別):                Programmatic Interface.
                                                             (line    6)
* Trace (tracemalloc 中的類別):          Trace.              (line    6)
* trace function:                        threading --- 基於執行緒的平行性.
                                                             (line  160)
* trace function <1>:                    threading --- 基於執行緒的平行性.
                                                             (line  178)
* trace function <2>:                    sys --- 系統特定的參數與函式.
                                                             (line  906)
* trace function <3>:                    sys --- 系統特定的參數與函式.
                                                             (line 1557)
* trace 命令列選項; -c:                  Main options.       (line   12)
* trace 命令列選項; -C:                  Modifiers.          (line   11)
* trace 命令列選項; -count:              Main options.       (line   12)
* trace 命令列選項; -coverdir:           Modifiers.          (line   11)
* trace 命令列選項; -f:                  Modifiers.          (line    6)
* trace 命令列選項; -file:               Modifiers.          (line    6)
* trace 命令列選項; -g:                  Modifiers.          (line   33)
* trace 命令列選項; -help:               Command-Line Usage. (line   15)
* trace 命令列選項; -ignore-dir:         Filters.            (line   14)
* trace 命令列選項; -ignore-module:      Filters.            (line    8)
* trace 命令列選項; -l:                  Main options.       (line   23)
* trace 命令列選項; -listfuncs:          Main options.       (line   23)
* trace 命令列選項; -m:                  Modifiers.          (line   17)
* trace 命令列選項; -missing:            Modifiers.          (line   17)
* trace 命令列選項; -no-report:          Modifiers.          (line   27)
* trace 命令列選項; -r:                  Main options.       (line   27)
* trace 命令列選項; -R:                  Modifiers.          (line   27)
* trace 命令列選項; -report:             Main options.       (line   27)
* trace 命令列選項; -s:                  Modifiers.          (line   22)
* trace 命令列選項; -summary:            Modifiers.          (line   22)
* trace 命令列選項; -t:                  Main options.       (line   19)
* trace 命令列選項; -T:                  Main options.       (line   33)
* trace 命令列選項; -timing:             Modifiers.          (line   33)
* trace 命令列選項; -trace:              Main options.       (line   19)
* trace 命令列選項; -trackcalls:         Main options.       (line   33)
* trace 命令列選項; -version:            Command-Line Usage. (line   19)
* trace_dispatch() (bdb.Bdb 的方法):     bdb --- 偵錯器框架. (line  164)
* trace() (於 inspect 模組中):           直譯器堆疊.         (line  180)
* Traceback (inspect 中的類別):          直譯器堆疊.         (line   55)
* Traceback (tracemalloc 中的類別):      Traceback.          (line    6)
* traceback (tracemalloc.Statistic 的屬性): Statistic.       (line   23)
* traceback (tracemalloc.StatisticDiff 的屬性): StatisticDiff.
                                                             (line   38)
* traceback (tracemalloc.Trace 的屬性):  Trace.              (line   27)
* traceback_limit (tracemalloc.Snapshot 的屬性): Snapshot.   (line   83)
* traceback_limit (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  186)
* TracebackException (traceback 中的類別): TracebackException 物件.
                                                             (line   11)
* tracebacklimit (於 sys 模組中):        sys --- 系統特定的參數與函式.
                                                             (line 1903)
* TracebackType (types 中的類別):        Standard Interpreter Types.
                                                             (line  229)
* tracer() (於 turtle 模組中):           Animation control.  (line   23)
* traces (tracemalloc.Snapshot 的屬性):  Snapshot.           (line   89)
* trailing;comma:                        Expression lists.   (line   24)
* transfercmd() (ftplib.FTP 的方法):     FTP 物件.           (line  228)
* transient_internet() (於 test.support.socket_helper 模組中): test support socket_helper --- 用於 socket 測試的工具.
                                                             (line   64)
* translate() (bytearray 的方法):        Bytes and Bytearray Operations.
                                                             (line  263)
* translate() (bytes 的方法):            Bytes and Bytearray Operations.
                                                             (line  263)
* translate() (str 的方法):              String Methods<2>.  (line  647)
* translate() (於 fnmatch 模組中):       fnmatch --- Unix 檔案名稱模式比對.
                                                             (line   76)
* translate() (於 glob 模組中):          glob --- Unix 風格的路徑名稱模式擴展.
                                                             (line  101)
* translation() (於 gettext 模組中):     Class-based API.    (line   44)
* Transport (asyncio 中的類別):          Transports Hierarchy.
                                                             (line   29)
* transport (asyncio.StreamWriter 的屬性): StreamWriter.     (line   52)
* Transport Layer Security（傳輸層安全）: ssl --- socket 物件的 TLS/SSL 包裝器.
                                                             (line    8)
* Traversable (importlib.abc 中的類別):  importlib abc -- Abstract base classes related to import.
                                                             (line  532)
* Traversable (importlib.resources.abc 中的類別): importlib resources abc -- 資源的抽象基底類別.
                                                             (line   86)
* TraversableResources (importlib.abc 中的類別): importlib abc -- Abstract base classes related to import.
                                                             (line  587)
* TraversableResources (importlib.resources.abc 中的類別): importlib resources abc -- 資源的抽象基底類別.
                                                             (line  158)
* traverseproc (C type):                 循環垃圾回收的支援. (line  164)
* TreeBuilder (xml.etree.ElementTree 中的類別): TreeBuilder 物件.
                                                             (line    6)
* Treeview (tkinter.ttk 中的類別):       ttk Treeview.       (line    6)
* triangular() (於 random 模組中):       實數分布.           (line   21)
* tries (doctest.DocTestRunner 的屬性):  DocTestRunner 物件. (line  134)
* triple-quoted string（三引號內字串）:  術語表.             (line 1230)
* triple-quoted string（三引號字串）:    String and Bytes literals.
                                                             (line   36)
* True:                                  numbers Integral.   (line   27)
* true:                                  真值檢測.           (line   10)
* True <1>:                              真值檢測.           (line   20)
* True <2>:                              Boolean 型別 - bool.
                                                             (line    9)
* True (內建變數):                       內建常數.           (line   13)
* truediv() (於 operator 模組中):        operator --- 標準運算子替代函式.
                                                             (line  152)
* trunc() (於 math 模組中):              數論與表現函式.     (line  270)
* trunc()（於 math 模組）:               數值型別 --- int、float、complex.
                                                             (line   97)
* truncate() (io.IOBase 的方法):         I/O 基礎類別.       (line  125)
* truncate() (於 os 模組中):             Files and Directories.
                                                             (line 1548)
* truth() (於 operator 模組中):          operator --- 標準運算子替代函式.
                                                             (line   50)
* truth（真）;value:                     真值檢測.           (line    6)
* Try (ast 中的類別):                    流程控制.           (line  124)
* TryStar (ast 中的類別):                流程控制.           (line  166)
* ttk:                                   tkinter ttk --- Tk 主題化小工具.
                                                             (line    8)
* tty;I/O control（I/O 控制）:           termios --- POSIX 風格 tty 控制.
                                                             (line    6)
* ttyname() (於 os 模組中):              File Descriptor Operations.
                                                             (line  891)
* TUESDAY (於 calendar 模組中):          calendar --- 日曆相關函式.
                                                             (line  336)
* Tuple (ast 中的類別):                  文本 Literals.      (line   63)
* tuple (內建類別):                      Tuples.             (line   12)
* Tuple (於 typing 模組中):              內建型別的別名.     (line   46)
* Turtle (turtle 中的類別):              Public classes.     (line   16)
* turtles() (於 turtle 模組中):          Settings and special methods.
                                                             (line   96)
* TurtleScreen (turtle 中的類別):        Public classes.     (line   22)
* turtlesize() (於 turtle 模組中):       Appearance.         (line   52)
* type (optparse.Option 的屬性):         Option attributes.  (line   27)
* type (socket.socket 的屬性):           Socket 物件.        (line  620)
* type (tarfile.TarInfo 的屬性):         TarInfo 物件.       (line   86)
* Type (typing 中的類別):                內建型別的別名.     (line   56)
* type (urllib.request.Request 的屬性):  Request Objects.    (line   21)
* type (內建類別):                       內建函式.           (line 1815)
* type alias（型別別名）:                術語表.             (line 1244)
* type hint（型別提示）:                 術語表.             (line 1263)
* type of an object（物件的型別）:       Objects values and types.
                                                             (line   11)
* type parameter（型別參數）:            Type parameter lists.
                                                             (line   10)
* TYPE_ALIAS (symtable.SymbolTableType 的屬性): 檢查符號表.  (line   31)
* type_check_only() (於 typing 模組中):  函式與裝飾器.       (line  411)
* TYPE_CHECKER (optparse.Option 的屬性): Adding new types.   (line   16)
* TYPE_CHECKING (於 typing 模組中):      常數<9>.            (line    6)
* type_comment (ast.arg 的屬性):         函式和類別定義.     (line   68)
* type_comment (ast.Assign 的屬性):      陳述式.             (line   14)
* type_comment (ast.For 的屬性):         流程控制.           (line   49)
* type_comment (ast.FunctionDef 的屬性): 函式和類別定義.     (line   24)
* type_comment (ast.With 的屬性):        流程控制.           (line  226)
* TYPE_COMMENT (於 token 模組中):        token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  250)
* TYPE_IGNORE (於 token 模組中):         token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  248)
* TYPE_PARAMETERS (symtable.SymbolTableType 的屬性): 檢查符號表.
                                                             (line   35)
* TYPE_VARIABLE (symtable.SymbolTableType 的屬性): 檢查符號表.
                                                             (line   40)
* type（型別）:                          標準型別階層.       (line    6)
* type（型別） <1>:                      術語表.             (line 1238)
* type（型別）;hierarchy（階層）:        標準型別階層.       (line    6)
* typeahead() (於 curses 模組中):        函式<5>.            (line  544)
* TypeAlias (ast 中的類別):              陳述式.             (line  156)
* TypeAlias (於 typing 模組中):          特別型別.           (line  188)
* TypeAliasType (typing 中的類別):       Building generic types and type aliases.
                                                             (line  490)
* typecode (array.array 的屬性):         array --- 高效率的數值型陣列.
                                                             (line  103)
* typecodes (於 array 模組中):           array --- 高效率的數值型陣列.
                                                             (line   75)
* TYPED_ACTIONS (optparse.Option 的屬性): Adding new actions.
                                                             (line   39)
* typed_subpart_iterator() (於 email.iterators 模組中): email iterators：疊代器.
                                                             (line   26)
* TypedDict (typing 中的類別):           Other special directives.
                                                             (line  230)
* TypeError:                             實體例外.           (line  341)
* TypeGuard (於 typing 模組中):          特別型式.           (line  468)
* TypeIs (於 typing 模組中):             特別型式.           (line  378)
* TYPES (optparse.Option 的屬性):        Adding new types.   (line   11)
* types_map (mimetypes.MimeTypes 的屬性): MimeTypes 物件.    (line   39)
* types_map (於 mimetypes 模組中):       mimetypes --- 將檔案名稱對映到 MIME 類型.
                                                             (line  153)
* types_map_inv (mimetypes.MimeTypes 的屬性): MimeTypes 物件.
                                                             (line   47)
* types（型別）, internal（內部）:       Internal types.     (line    6)
* TypeVar (ast 中的類別):                型別參數 type parameters.
                                                             (line    8)
* TypeVar (typing 中的類別):             Building generic types and type aliases.
                                                             (line   54)
* TypeVarTuple (ast 中的類別):           型別參數 type parameters.
                                                             (line   67)
* TypeVarTuple (typing 中的類別):        Building generic types and type aliases.
                                                             (line  217)
* TZ:                                    函式<4>.            (line  542)
* TZ <1>:                                函式<4>.            (line  543)
* TZ <2>:                                函式<4>.            (line  551)
* TZ <3>:                                函式<4>.            (line  556)
* TZ <4>:                                函式<4>.            (line  558)
* TZ <5>:                                函式<4>.            (line  619)
* tzinfo (datetime 中的類別):            tzinfo 物件.        (line    6)
* tzinfo (datetime.datetime 的屬性):     datetime 物件.      (line  327)
* tzinfo (datetime.time 的屬性):         time 物件.          (line   66)
* tzname (於 time 模組中):               Timezone Constants. (line   23)
* tzname() (datetime.datetime 的方法):   datetime 物件.      (line  542)
* tzname() (datetime.time 的方法):       time 物件.          (line  256)
* tzname() (datetime.timezone 的方法):   timezone 物件.      (line   42)
* tzname() (datetime.tzinfo 的方法):     tzinfo 物件.        (line  123)
* TZPATH (於 zoneinfo 模組中):           Globals.            (line    6)
* tzset() (於 time 模組中):              函式<4>.            (line  539)
* U (於 re 模組中):                      旗標.               (line  116)
* u';string literal（字串常數）:         Literals.           (line    8)
* u";string literal（字串常數）:         Literals.           (line    8)
* UAdd (ast 中的類別):                   運算式<2>.          (line   26)
* ucd_3_2_0 (於 unicodedata 模組中):     unicodedata --- Unicode 資料庫.
                                                             (line  131)
* udata (select.kevent 的屬性):          Kevent Objects.     (line  179)
* UDPServer (socketserver 中的類別):     socketserver --- 用於網路伺服器的框架.
                                                             (line   30)
* UF_APPEND (於 stat 模組中):            stat --- 直譯 stat 的結果.
                                                             (line  352)
* UF_COMPRESSED (於 stat 模組中):        stat --- 直譯 stat 的結果.
                                                             (line  364)
* UF_DATAVAULT (於 stat 模組中):         stat --- 直譯 stat 的結果.
                                                             (line  374)
* UF_HIDDEN (於 stat 模組中):            stat --- 直譯 stat 的結果.
                                                             (line  380)
* UF_IMMUTABLE (於 stat 模組中):         stat --- 直譯 stat 的結果.
                                                             (line  348)
* UF_NODUMP (於 stat 模組中):            stat --- 直譯 stat 的結果.
                                                             (line  344)
* UF_NOUNLINK (於 stat 模組中):          stat --- 直譯 stat 的結果.
                                                             (line  360)
* UF_OPAQUE (於 stat 模組中):            stat --- 直譯 stat 的結果.
                                                             (line  356)
* UF_SETTABLE (於 stat 模組中):          stat --- 直譯 stat 的結果.
                                                             (line  338)
* UF_TRACKED (於 stat 模組中):           stat --- 直譯 stat 的結果.
                                                             (line  368)
* UID (plistlib 中的類別):               plistlib --- 產生和剖析 Apple plist 檔案.
                                                             (line  141)
* uid (tarfile.TarInfo 的屬性):          TarInfo 物件.       (line  105)
* uid() (imaplib.IMAP4 的方法):          IMAP4 物件.         (line  365)
* uidl() (poplib.POP3 的方法):           POP3 物件.          (line   99)
* ULONG_MAX（C 巨集）:                   整數物件.           (line  239)
* ulp() (於 math 模組中):                數論與表現函式.     (line  279)
* umask() (於 os 模組中):                行程參數.           (line  543)
* unalias (pdb command):                 Debugger Commands.  (line  397)
* uname (tarfile.TarInfo 的屬性):        TarInfo 物件.       (line  121)
* uname() (於 os 模組中):                行程參數.           (line  550)
* uname() (於 platform 模組中):          跨平台.             (line  128)
* UNARY_INVERT (opcode):                 Python Bytecode Instructions.
                                                             (line  202)
* UNARY_NEGATIVE (opcode):               Python Bytecode Instructions.
                                                             (line  191)
* UNARY_NOT (opcode):                    Python Bytecode Instructions.
                                                             (line  195)
* unary（一元）;arithmetic;operation（操作）: Unary arithmetic and bitwise operations.
                                                             (line    6)
* unary（一元）;bitwise（位元）;operation（操作）: Unary arithmetic and bitwise operations.
                                                             (line    6)
* unaryfunc (C type):                    Slot Type typedefs. (line  108)
* UnaryOp (ast 中的類別):                運算式<2>.          (line   21)
* unbinding（解除繫結）;name（名稱）:    del 陳述式<2>.      (line   15)
* UnboundLocalError:                     Resolution of names.
                                                             (line   16)
* UnboundLocalError <1>:                 實體例外.           (line  354)
* unbuffered I/O（非緩衝 I/O）:          內建函式.           (line 1294)
* UNC paths（UNC 路徑）;以及 os.makedirs(): Files and Directories.
                                                             (line  535)
* uncancel() (asyncio.Task 的方法):      Task Object.        (line  268)
* UNCHECKED_HASH (py_compile.PycInvalidationMode 的屬性): py_compile — 編譯 Python 來源檔案.
                                                             (line  115)
* unconsumed_tail (zlib.Decompress 的屬性): zlib --- 相容於 gzip 的壓縮.
                                                             (line  194)
* unctrl() (於 curses 模組中):           函式<5>.            (line  556)
* unctrl() (於 curses.ascii 模組中):     curses ascii --- ASCII 字元的工具程式.
                                                             (line  229)
* Underflow (decimal 中的類別):          Signals.            (line   93)
* undisplay (pdb command):               Debugger Commands.  (line  345)
* undo() (於 turtle 模組中):             Turtle motion.      (line  317)
* undobufferentries() (於 turtle 模組中): Special Turtle methods.
                                                             (line   74)
* undoc_header (cmd.Cmd 的屬性):         Cmd 物件.           (line  166)
* unescape() (於 html 模組中):           html --- 超連結標記語言 HTML 支援.
                                                             (line   22)
* unescape() (於 xml.sax.saxutils 模組中): xml sax saxutils --- SAX 工具程式.
                                                             (line   28)
* UnexpectedException:                   Debugging.          (line  208)
* unexpectedSuccesses (unittest.TestResult 的屬性): Loading and running tests.
                                                             (line  272)
* unfreeze() (於 gc 模組中):             gc --- 垃圾回收器介面 Garbage Collector interface.
                                                             (line  222)
* unget_wch() (於 curses 模組中):        函式<5>.            (line  576)
* ungetch() (於 curses 模組中):          函式<5>.            (line  563)
* ungetch() (於 msvcrt 模組中):          Console I/O.        (line   45)
* ungetmouse() (於 curses 模組中):       函式<5>.            (line  585)
* ungetwch() (於 msvcrt 模組中):         Console I/O.        (line   51)
* unhexlify() (於 binascii 模組中):      binascii --- 在二進位制和 ASCII 之間轉換.
                                                             (line  143)
* Unicode:                               Immutable sequences.
                                                             (line   15)
* Unicode <1>:                           unicodedata --- Unicode 資料庫.
                                                             (line    6)
* Unicode <2>:                           codecs --- 編解碼器註冊表和基底類別.
                                                             (line    8)
* UNICODE (於 re 模組中):                旗標.               (line  116)
* Unicode Consortium:                    String and Bytes literals.
                                                             (line   36)
* Unicode;database（資料庫）:            unicodedata --- Unicode 資料庫.
                                                             (line    6)
* UnicodeDecodeError:                    實體例外.           (line  393)
* UnicodeEncodeError:                    實體例外.           (line  388)
* UnicodeError:                          實體例外.           (line  359)
* UnicodeTranslateError:                 實體例外.           (line  398)
* UnicodeWarning:                        警告.               (line   60)
* unidata_version (於 unicodedata 模組中): unicodedata --- Unicode 資料庫.
                                                             (line  127)
* unified_diff() (於 difflib 模組中):    difflib --- 計算差異的輔助工具.
                                                             (line  293)
* uniform() (於 random 模組中):          實數分布.           (line   13)
* UnimplementedFileMode:                 http client --- HTTP 協定用戶端.
                                                             (line  153)
* Union (ctypes 中的類別):               Structured data types.
                                                             (line    6)
* Union (於 typing 模組中):              特別型式.           (line    9)
* union() (frozenset 的方法):            Set Types --- set frozenset.
                                                             (line   96)
* union（聯集）;type（型別）:            聯合型別 Union Type.
                                                             (line    6)
* UnionType (types 中的類別):            Standard Interpreter Types.
                                                             (line  223)
* UNIQUE (enum.EnumCheck 的屬性):        資料型別<2>.        (line  563)
* unique() (於 enum 模組中):             通用項目與裝飾器.   (line   47)
* unittest 命令列選項; -b:               命令列模式選項.     (line    8)
* unittest 命令列選項; -buffer:          命令列模式選項.     (line    8)
* unittest 命令列選項; -c:               命令列模式選項.     (line   14)
* unittest 命令列選項; -catch:           命令列模式選項.     (line   14)
* unittest 命令列選項; -durations:       命令列模式選項.     (line   47)
* unittest 命令列選項; -f:               命令列模式選項.     (line   22)
* unittest 命令列選項; -failfast:        命令列模式選項.     (line   22)
* unittest 命令列選項; -k:               命令列模式選項.     (line   26)
* unittest 命令列選項; -locals:          命令列模式選項.     (line   43)
* unittest-discover 命令列選項; -p:      Test Discovery（測試探索）.
                                                             (line   33)
* unittest-discover 命令列選項; -pattern: Test Discovery（測試探索）.
                                                             (line   33)
* unittest-discover 命令列選項; -s:      Test Discovery（測試探索）.
                                                             (line   29)
* unittest-discover 命令列選項; -start-directory: Test Discovery（測試探索）.
                                                             (line   29)
* unittest-discover 命令列選項; -t:      Test Discovery（測試探索）.
                                                             (line   37)
* unittest-discover 命令列選項; -top-level-directory: Test Discovery（測試探索）.
                                                             (line   37)
* unittest-discover 命令列選項; -v:      Test Discovery（測試探索）.
                                                             (line   25)
* unittest-discover 命令列選項; -verbose: Test Discovery（測試探索）.
                                                             (line   25)
* universal newlines;bytearray.splitlines 方法: Bytes and Bytearray Operations.
                                                             (line  638)
* universal newlines;bytes.splitlines 方法: Bytes and Bytearray Operations.
                                                             (line  638)
* universal newlines;csv.reader 函式:    模組內容<3>.        (line    8)
* universal newlines;importlib.abc.InspectLoader.get_source 方法: importlib abc -- Abstract base classes related to import.
                                                             (line  245)
* universal newlines;io.IncrementalNewlineDecoder 類別: 文字 I/O<2>.
                                                             (line  285)
* universal newlines;io.TextIOWrapper 類別: 文字 I/O<2>.     (line  126)
* universal newlines;open() 內建函式:    內建函式.           (line 1242)
* universal newlines;str.splitlines 方法: String Methods<2>. (line  504)
* universal newlines;subprocess 模組:    Frequently Used Arguments.
                                                             (line   33)
* universal newlines;What's new（有什麼新功能）: PEP 3116 New I/O Library.
                                                             (line   42)
* universal newlines;What's new（有什麼新功能） <1>: New Improved and Removed Modules.
                                                             (line  137)
* universal newlines;What's new（有什麼新功能） <2>: PEP 324 New subprocess Module.
                                                             (line   36)
* universal newlines;What's new（有什麼新功能） <3>: PEP 277 Unicode file name support for Windows NT.
                                                             (line   36)
* universal newlines（通用換行字元）:    術語表.             (line 1277)
* UNIX:                                  完整的 Python 程式. (line   19)
* unix_dialect (csv 中的類別):           模組內容<3>.        (line  195)
* unix_shell (於 test.support 模組中):   test support --- Python 測試套件的工具.
                                                             (line   43)
* UNIX;file control（檔案控制）:         fcntl --- fcntl 和 ioctl 系統呼叫.
                                                             (line    6)
* UNIX;I/O control（I/O 控制）:          fcntl --- fcntl 和 ioctl 系統呼叫.
                                                             (line    6)
* UnixDatagramServer (socketserver 中的類別): socketserver --- 用於網路伺服器的框架.
                                                             (line   37)
* UnixStreamServer (socketserver 中的類別): socketserver --- 用於網路伺服器的框架.
                                                             (line   37)
* unknown (uuid.SafeUUID 的屬性):        uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line   40)
* unknown_decl() (html.parser.HTMLParser 的方法): HTMLParser 方法.
                                                             (line  113)
* unknown_open() (urllib.request.BaseHandler 的方法): BaseHandler 物件.
                                                             (line   56)
* unknown_open() (urllib.request.UnknownHandler 的方法): UnknownHandler 物件.
                                                             (line    6)
* UnknownHandler (urllib.request 中的類別): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  404)
* UnknownProtocol:                       http client --- HTTP 協定用戶端.
                                                             (line  145)
* UnknownTransferEncoding:               http client --- HTTP 協定用戶端.
                                                             (line  149)
* unlink() (multiprocessing.shared_memory.SharedMemory 的方法): multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取.
                                                             (line   88)
* unlink() (pathlib.Path 的方法):        Renaming and deleting.
                                                             (line   41)
* unlink() (xml.dom.minidom.Node 的方法): DOM 物件.          (line   10)
* unlink() (於 os 模組中):               Files and Directories.
                                                             (line 1566)
* unlink() (於 test.support.os_helper 模組中): test support os_helper --- 用於 os 測試的工具.
                                                             (line  162)
* unload() (於 test.support.import_helper 模組中): test support import_helper --- 用於 import 測試的工具.
                                                             (line   74)
* unlock() (mailbox.Babyl 的方法):       Babyl 物件.         (line   59)
* unlock() (mailbox.Mailbox 的方法):     Mailbox 物件.       (line  265)
* unlock() (mailbox.Maildir 的方法):     Mailbox 物件<2>.    (line  209)
* unlock() (mailbox.mbox 的方法):        mbox 物件.          (line   38)
* unlock() (mailbox.MH 的方法):          MH 物件.            (line   87)
* unlock() (mailbox.MMDF 的方法):        MMDF 物件.          (line   35)
* unlockpt() (於 os 模組中):             File Descriptor Operations.
                                                             (line  899)
* UNNAMED_SECTION (於 configparser 模組中): ConfigParser 物件.
                                                             (line  332)
* Unpack (於 typing 模組中):             特別型式.           (line  525)
* unpack_archive() (於 shutil 模組中):   Archiving operations.
                                                             (line  125)
* UNPACK_EX (opcode):                    Python Bytecode Instructions.
                                                             (line  574)
* unpack_from() (struct.Struct 的方法):  Classes<2>.         (line   40)
* unpack_from() (於 struct 模組中):      函式與例外.         (line   34)
* UNPACK_SEQUENCE (opcode):              Python Bytecode Instructions.
                                                             (line  565)
* unpack() (struct.Struct 的方法):       Classes<2>.         (line   34)
* unpack() (於 struct 模組中):           函式與例外.         (line   26)
* unpacking（解包）;dictionary（字典）:  Dictionary displays.
                                                             (line   23)
* unpacking（解包）;於函式呼叫中:        Calls.              (line   72)
* unparse() (於 ast 模組中):             ast 輔助程式.       (line   61)
* unparsedEntityDecl() (xml.sax.handler.DTDHandler 的方法): DTDHandler 物件.
                                                             (line   12)
* UnparsedEntityDeclHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line  290)
* Unpickler (pickle 中的類別):           模組介面.           (line  230)
* UnpicklingError:                       模組介面.           (line  108)
* unquote_plus() (於 urllib.parse 模組中): URL Quoting.      (line   81)
* unquote_to_bytes() (於 urllib.parse 模組中): URL Quoting.  (line   91)
* unquote() (於 email.utils 模組中):     email utils：雜項工具.
                                                             (line   50)
* unquote() (於 urllib.parse 模組中):    URL Quoting.        (line   61)
* unraisablehook() (於 sys 模組中):      sys --- 系統特定的參數與函式.
                                                             (line 1911)
* unreachable object（不可達物件）:      Objects values and types.
                                                             (line   37)
* unrecognized escape sequence（無法辨識的跳脫序列）: 跳脫序列.
                                                             (line  106)
* unregister_archive_format() (於 shutil 模組中): Archiving operations.
                                                             (line  120)
* unregister_dialect() (於 csv 模組中):  模組內容<3>.        (line   70)
* unregister_unpack_format() (於 shutil 模組中): Archiving operations.
                                                             (line  186)
* unregister() (select.devpoll 的方法):  /dev/poll Polling Objects.
                                                             (line   55)
* unregister() (select.epoll 的方法):    Edge and Level Trigger Polling epoll Objects.
                                                             (line   89)
* unregister() (select.poll 的方法):     Polling Objects.    (line   67)
* unregister() (selectors.BaseSelector 的方法): Classes<3>.  (line   80)
* unregister() (於 atexit 模組中):       atexit --- 退出處理函式.
                                                             (line   48)
* unregister() (於 codecs 模組中):       codecs --- 編解碼器註冊表和基底類別.
                                                             (line  160)
* unregister() (於 faulthandler 模組中): Dumping the traceback on a user signal.
                                                             (line   23)
* unsafe (uuid.SafeUUID 的屬性):         uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line   36)
* unselect() (imaplib.IMAP4 的方法):     IMAP4 物件.         (line  376)
* unset() (test.support.os_helper.EnvironmentVarGuard 的方法): test support os_helper --- 用於 os 測試的工具.
                                                             (line   70)
* unsetenv() (於 os 模組中):             行程參數.           (line  585)
* unshare() (於 os 模組中):              行程參數.           (line  603)
* UnstructuredHeader (email.headerregistry 中的類別): email headerregistry：自訂標頭物件.
                                                             (line  115)
* unsubscribe() (imaplib.IMAP4 的方法):  IMAP4 物件.         (line  372)
* UnsupportedOperation:                  Exceptions<2>.      (line    6)
* UnsupportedOperation <1>:              高階模組介面.       (line   66)
* until (pdb command):                   Debugger Commands.  (line  211)
* untokenize() (於 tokenize 模組中):     Tokenizing Input.   (line   57)
* untouchwin() (curses.window 的方法):   Window Objects.     (line  582)
* unused_data (bz2.BZ2Decompressor 的屬性): Incremental de compression.
                                                             (line   78)
* unused_data (lzma.LZMADecompressor 的屬性): Compressing and decompressing data in memory.
                                                             (line  169)
* unused_data (zlib.Decompress 的屬性):  zlib --- 相容於 gzip 的壓縮.
                                                             (line  187)
* unverifiable (urllib.request.Request 的屬性): Request Objects.
                                                             (line   47)
* unwrap() (ssl.SSLSocket 的方法):       SSL Sockets.        (line  280)
* unwrap() (於 inspect 模組中):          類別與函式.         (line  138)
* unwrap() (於 urllib.parse 模組中):     URL Parsing.        (line  396)
* up (pdb command):                      Debugger Commands.  (line   92)
* up() (於 turtle 模組中):               Drawing state.      (line   12)
* update_abstractmethods() (於 abc 模組中): abc --- 抽象基底類別.
                                                             (line  299)
* update_authenticated() (urllib.request.HTTPPasswordMgrWithPriorAuth 的方法): HTTPPasswordMgrWithPriorAuth 物件.
                                                             (line   24)
* update_lines_cols() (於 curses 模組中): 函式<5>.           (line  569)
* update_panels() (於 curses.panel 模組中): 函式<6>.         (line   23)
* update_visible() (mailbox.BabylMessage 的方法): BabylMessage 物件.
                                                             (line   76)
* update_wrapper() (於 functools 模組中): functools --- 可呼叫物件上的高階函式與操作.
                                                             (line  570)
* update() (collections.Counter 的方法): Counter 物件.       (line  111)
* update() (dict 的方法):                Mapping Types --- dict.
                                                             (line  204)
* update() (frozenset 的方法):           Set Types --- set frozenset.
                                                             (line  169)
* update() (hashlib.hash 的方法):        雜湊物件.           (line   28)
* update() (hmac.HMAC 的方法):           hmac --- 基於金鑰雜湊的訊息驗證.
                                                             (line   41)
* update() (http.cookies.Morsel 的方法): Morsel 物件.        (line   87)
* update() (mailbox.Mailbox 的方法):     Mailbox 物件.       (line  235)
* update() (mailbox.Maildir 的方法):     Mailbox 物件<2>.    (line  193)
* update() (trace.CoverageResults 的方法): Programmatic Interface.
                                                             (line   52)
* update() (於 turtle 模組中):           Animation control.  (line   46)
* upgrade_dependencies() (venv.EnvBuilder 的方法): API<2>.   (line  159)
* upper() (bytearray 的方法):            Bytes and Bytearray Operations.
                                                             (line  730)
* upper() (bytes 的方法):                Bytes and Bytearray Operations.
                                                             (line  730)
* upper() (str 的方法):                  String Methods<2>.  (line  665)
* urandom() (於 os 模組中):              Random numbers.     (line   29)
* url (http.client.HTTPResponse 的屬性): HTTPResponse 物件.  (line   51)
* url (urllib.error.HTTPError 的屬性):   urllib error --- urllib request 引發的例外類別.
                                                             (line   35)
* url (urllib.response.addinfourl 的屬性): urllib response --- Response classes used by urllib.
                                                             (line   14)
* url (xmlrpc.client.ProtocolError 的屬性): ProtocolError 物件.
                                                             (line   13)
* URL（統一資源定位器）:                 urllib parse --- 將 URL 剖析成元件.
                                                             (line    8)
* URL（統一資源定位器） <1>:             urllib robotparser --- robots txt 的剖析器.
                                                             (line    8)
* URL（統一資源定位器） <2>:             http server — HTTP 伺服器.
                                                             (line    8)
* URL（統一資源定位器）;parsing（剖析）: urllib parse --- 將 URL 剖析成元件.
                                                             (line    8)
* url2pathname() (於 urllib.request 模組中): urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  139)
* urlcleanup() (於 urllib.request 模組中): Legacy interface. (line   62)
* urldefrag() (於 urllib.parse 模組中):  URL Parsing.        (line  370)
* urlencode() (於 urllib.parse 模組中):  URL Quoting.        (line  104)
* URLError:                              urllib error --- urllib request 引發的例外類別.
                                                             (line   16)
* urljoin() (於 urllib.parse 模組中):    URL Parsing.        (line  340)
* urlopen() (於 urllib.request 模組中):  urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line   32)
* URLopener (urllib.request 中的類別):   Legacy interface.   (line   67)
* urlparse() (於 urllib.parse 模組中):   URL Parsing.        (line    9)
* urlretrieve() (於 urllib.request 模組中): Legacy interface.
                                                             (line   10)
* urlsafe_b64decode() (於 base64 模組中): base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   87)
* urlsafe_b64encode() (於 base64 模組中): base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   81)
* urlsplit() (於 urllib.parse 模組中):   URL Parsing.        (line  250)
* urlunparse() (於 urllib.parse 模組中): URL Parsing.        (line  242)
* urlunsplit() (於 urllib.parse 模組中): URL Parsing.        (line  331)
* urn (uuid.UUID 的屬性):                uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  129)
* US (於 curses.ascii 模組中):           curses ascii --- ASCII 字元的工具程式.
                                                             (line  118)
* use_default_colors() (於 curses 模組中): 函式<5>.          (line  600)
* use_env() (於 curses 模組中):          函式<5>.            (line  590)
* use_rawinput (cmd.Cmd 的屬性):         Cmd 物件.           (line  177)
* USE_STACKCHECK（C 巨集）:              作業系統工具.       (line   91)
* use_tool_id() (於 sys.monitoring 模組中): Registering and using tools.
                                                             (line    6)
* UseForeignDTD() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line   63)
* USER:                                  getpass --- 可攜式密碼輸入工具.
                                                             (line   41)
* USER_BASE (於 site 模組中):            模組內容<10>.       (line   31)
* user_call() (bdb.Bdb 的方法):          bdb --- 偵錯器框架. (line  268)
* user_exception() (bdb.Bdb 的方法):     bdb --- 偵錯器框架. (line  287)
* user_line() (bdb.Bdb 的方法):          bdb --- 偵錯器框架. (line  276)
* user_return() (bdb.Bdb 的方法):        bdb --- 偵錯器框架. (line  282)
* USER_SITE (於 site 模組中):            模組內容<10>.       (line   19)
* user-defined（使用者定義）;function （函式）: 自訂函式.    (line    6)
* user-defined（使用者定義）;function （函式）;call（呼叫）: Calls.
                                                             (line  131)
* user-defined（使用者定義）;method（方法）: Instance methods.
                                                             (line    6)
* user() (poplib.POP3 的方法):           POP3 物件.          (line   31)
* user（使用者）;effective id:           行程參數.           (line  187)
* user（使用者）;id:                     行程參數.           (line  335)
* user（使用者）;id, setting（設定）:    行程參數.           (line  526)
* usercustomize:                         客製化模組.         (line    6)
* usercustomize <1>:                     客製化模組.         (line   19)
* UserDict (collections 中的類別):       UserDict 物件.      (line   10)
* UserList (collections 中的類別):       UserList 物件.      (line   13)
* USERNAME:                              os path --- 常見的路徑名操作.
                                                             (line  130)
* USERNAME <1>:                          行程參數.           (line  239)
* USERNAME <2>:                          getpass --- 可攜式密碼輸入工具.
                                                             (line   42)
* username (email.headerregistry.Address 的屬性): email headerregistry：自訂標頭物件.
                                                             (line  431)
* USERPROFILE:                           os path<4>.         (line   14)
* USERPROFILE <1>:                       Changes in the Python API<3>.
                                                             (line  116)
* USERPROFILE <2>:                       Windows<36>.        (line   15)
* USERPROFILE <3>:                       os path --- 常見的路徑名操作.
                                                             (line  128)
* userptr() (curses.panel.Panel 的方法): Panel Objects.      (line   57)
* UserString (collections 中的類別):     UserString 物件.    (line   10)
* UserWarning:                           警告.               (line   13)
* USTAR_FORMAT (於 tarfile 模組中):      tarfile --- 讀取與寫入 tar 封存檔案.
                                                             (line  316)
* USub (ast 中的類別):                   運算式<2>.          (line   26)
* UTC:                                   time --- 時間存取與轉換.
                                                             (line   32)
* utc (datetime.timezone 的屬性):        timezone 物件.      (line   68)
* UTC (於 datetime 模組中):              常數.               (line   18)
* utcfromtimestamp() (datetime.datetime 的類別方法): datetime 物件.
                                                             (line  126)
* utcnow() (datetime.datetime 的類別方法): datetime 物件.    (line   76)
* utcoffset() (datetime.datetime 的方法): datetime 物件.     (line  522)
* utcoffset() (datetime.time 的方法):    time 物件.          (line  236)
* utcoffset() (datetime.timezone 的方法): timezone 物件.     (line   30)
* utcoffset() (datetime.tzinfo 的方法):  tzinfo 物件.        (line   38)
* utctimetuple() (datetime.datetime 的方法): datetime 物件.  (line  567)
* utf8 (email.policy.EmailPolicy 的屬性): email policy Policy Objects.
                                                             (line  380)
* utf8_enabled (imaplib.IMAP4 的屬性):   IMAP4 物件.         (line  404)
* utf8_mode (sys.flags 的屬性):          sys --- 系統特定的參數與函式.
                                                             (line  564)
* utf8() (poplib.POP3 的方法):           POP3 物件.          (line  106)
* utime() (於 os 模組中):                Files and Directories.
                                                             (line 1580)
* UUID (uuid 中的類別):                  uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line   44)
* uuid 命令列選項; -h:                   命令列的用法.       (line   14)
* uuid 命令列選項; -help:                命令列的用法.       (line   14)
* uuid 命令列選項; -n:                   命令列的用法.       (line   23)
* uuid 命令列選項; -N:                   命令列的用法.       (line   30)
* uuid 命令列選項; -name:                命令列的用法.       (line   30)
* uuid 命令列選項; -namespace:           命令列的用法.       (line   23)
* uuid 命令列選項; -u:                   命令列的用法.       (line   18)
* uuid 命令列選項; -uuid:                命令列的用法.       (line   18)
* uuid1:                                 uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  173)
* uuid1() (於 uuid 模組中):              uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  167)
* uuid3:                                 uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  179)
* uuid3() (於 uuid 模組中):              uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  173)
* uuid4:                                 uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  183)
* uuid4() (於 uuid 模組中):              uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  179)
* uuid5:                                 uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  188)
* uuid5() (於 uuid 模組中):              uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  183)
* v4_int_to_packed() (於 ipaddress 模組中): Other Module Level Functions.
                                                             (line    8)
* v6_int_to_packed() (於 ipaddress 模組中): Other Module Level Functions.
                                                             (line   20)
* valid_signals() (於 signal 模組中):    模組內容<5>.        (line  304)
* validator() (於 wsgiref.validate 模組中): wsgiref validate --- WSGI 符合性檢查.
                                                             (line   17)
* value (ctypes._SimpleCData 的屬性):    Fundamental data types<2>.
                                                             (line   17)
* value (enum.Enum 的屬性):              資料型別<2>.        (line  138)
* value (http.cookiejar.Cookie 的屬性):  Cookie 物件<2>.     (line   32)
* value (http.cookies.Morsel 的屬性):    Morsel 物件.        (line   45)
* value (StopIteration 的屬性):          實體例外.           (line  225)
* value (xml.dom.Attr 的屬性):           Attr Objects.       (line   23)
* value of an object（物件的值）:        Objects values and types.
                                                             (line   11)
* value_decode() (http.cookies.BaseCookie 的方法): Cookie 物件.
                                                             (line    6)
* value_encode() (http.cookies.BaseCookie 的方法): Cookie 物件.
                                                             (line   13)
* Value() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  216)
* Value() (於 multiprocessing 模組中):   共享的 ctypes 物件. (line    9)
* Value() (於 multiprocessing.sharedctypes 模組中): multiprocessing sharedctypes 模組.
                                                             (line   67)
* value（值）:                           Dictionary displays.
                                                             (line    6)
* ValueError:                            實體例外.           (line  403)
* valuerefs() (weakref.WeakValueDictionary 的方法): weakref --- 弱參照.
                                                             (line  179)
* Values (optparse 中的類別):            Defining options.   (line   84)
* values() (contextvars.Context 的方法): Manual Context Management.
                                                             (line  109)
* values() (dict 的方法):                Mapping Types --- dict.
                                                             (line  215)
* values() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  234)
* values() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  343)
* values() (mailbox.Mailbox 的方法):     Mailbox 物件.       (line  128)
* values() (types.MappingProxyType 的方法): Standard Interpreter Types.
                                                             (line  318)
* ValuesView (collections.abc 中的類別): Collections Abstract Base Classes -- Detailed Descriptions.
                                                             (line  102)
* ValuesView (typing 中的類別):          collections abc 中容器 ABC 的別名.
                                                             (line  105)
* var (contextvars.Token 的屬性):        Context Variables.  (line   82)
* variable annotation（變數註釋）:       術語表.             (line 1284)
* variance (statistics.NormalDist 的屬性): NormalDist 物件.  (line   35)
* variance() (於 statistics 模組中):     函式細節.           (line  408)
* variant (uuid.UUID 的屬性):            uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  133)
* vbar (tkinter.scrolledtext.ScrolledText 的屬性): tkinter scrolledtext --- 捲動文字小工具.
                                                             (line   30)
* VBAR (於 token 模組中):                token --- 與 Python 剖析樹一起使用的常數.
                                                             (line   98)
* VBAREQUAL (於 token 模組中):           token --- 與 Python 剖析樹一起使用的常數.
                                                             (line  194)
* VC_ASSEMBLY_PUBLICKEYTOKEN (於 msvcrt 模組中): Other Functions.
                                                             (line   93)
* Vec2D (turtle 中的類別):               Public classes.     (line   85)
* vectorcallfunc (C type):               Vectorcall 協定.    (line   36)
* verbose (sys.flags 的屬性):            sys --- 系統特定的參數與函式.
                                                             (line  549)
* VERBOSE (於 re 模組中):                旗標.               (line  126)
* verbose (於 tabnanny 模組中):          tabnanny --- 偵測不良縮排.
                                                             (line   24)
* verbose (於 test.support 模組中):      test support --- Python 測試套件的工具.
                                                             (line   29)
* VERIFY_ALLOW_PROXY_CERTS (於 ssl 模組中): 常數<8>.         (line   88)
* verify_client_post_handshake() (ssl.SSLSocket 的方法): SSL Sockets.
                                                             (line  289)
* verify_code (ssl.SSLCertVerificationError 的屬性): 例外<11>.
                                                             (line   77)
* VERIFY_CRL_CHECK_CHAIN (於 ssl 模組中): 常數<8>.           (line   74)
* VERIFY_CRL_CHECK_LEAF (於 ssl 模組中): 常數<8>.            (line   64)
* VERIFY_DEFAULT (於 ssl 模組中):        常數<8>.            (line   57)
* verify_flags (ssl.SSLContext 的屬性):  SSL Contexts.       (line  636)
* verify_generated_headers (email.policy.Policy 的屬性): email policy Policy Objects.
                                                             (line  204)
* verify_message (ssl.SSLCertVerificationError 的屬性): 例外<11>.
                                                             (line   81)
* verify_mode (ssl.SSLContext 的屬性):   SSL Contexts.       (line  651)
* verify_request() (socketserver.BaseServer 的方法): Server Objects.
                                                             (line  175)
* VERIFY_X509_PARTIAL_CHAIN (於 ssl 模組中): 常數<8>.        (line  102)
* VERIFY_X509_STRICT (於 ssl 模組中):    常數<8>.            (line   81)
* VERIFY_X509_TRUSTED_FIRST (於 ssl 模組中): 常數<8>.        (line   95)
* verify() (smtplib.SMTP 的方法):        SMTP 物件.          (line   91)
* verify() (於 enum 模組中):             通用項目與裝飾器.   (line   65)
* VerifyFlags (ssl 中的類別):            常數<8>.            (line  110)
* VerifyMode (ssl 中的類別):             常數<8>.            (line   51)
* version (email.headerregistry.MIMEVersionHeader 的屬性): email headerregistry：自訂標頭物件.
                                                             (line  242)
* version (http.client.HTTPResponse 的屬性): HTTPResponse 物件.
                                                             (line   46)
* version (http.cookiejar.Cookie 的屬性): Cookie 物件<2>.    (line   20)
* version (http.cookies.Morsel 的屬性):  Morsel 物件.        (line   13)
* version (ipaddress.IPv4Address 的屬性): Address objects.   (line   45)
* version (ipaddress.IPv4Network 的屬性): Network objects.   (line   63)
* version (ipaddress.IPv6Address 的屬性): Address objects.   (line  260)
* version (ipaddress.IPv6Network 的屬性): Network objects.   (line  293)
* version (sys.thread_info 的屬性):      sys --- 系統特定的參數與函式.
                                                             (line 1896)
* version (urllib.request.URLopener 的屬性): Legacy interface.
                                                             (line  137)
* version (uuid.UUID 的屬性):            uuid --- RFC 4122 定義的 UUID 物件.
                                                             (line  139)
* version (於 curses 模組中):            Constants.          (line   18)
* version (於 marshal 模組中):           marshal --- 内部 Python 物件序列化.
                                                             (line  120)
* version (於 sqlite3 模組中):           Module constants.   (line  122)
* version (於 sys 模組中):               sys --- 系統特定的參數與函式.
                                                             (line 1959)
* version_info (於 sqlite3 模組中):      Module constants.   (line  132)
* version_info (於 sys 模組中):          sys --- 系統特定的參數與函式.
                                                             (line 1974)
* version_string() (http.server.BaseHTTPRequestHandler 的方法): http server — HTTP 伺服器.
                                                             (line  312)
* version() (ssl.SSLSocket 的方法):      SSL Sockets.        (line  311)
* version() (於 ensurepip 模組中):       模組 API.           (line    8)
* version() (於 platform 模組中):        跨平台.             (line  120)
* version（sys 模組中）:                 Process-wide parameters.
                                                             (line  162)
* version（sys 模組中） <1>:             Process-wide parameters.
                                                             (line  199)
* version（sys 模組中） <2>:             Process-wide parameters.
                                                             (line  210)
* vformat() (string.Formatter 的方法):   自訂字串格式.       (line   22)
* virtual environment（虛擬環境）:       術語表.             (line 1305)
* virtual machine（虛擬機器）:           術語表.             (line 1313)
* visit_Constant() (ast.NodeVisitor 的方法): ast 輔助程式.   (line  180)
* visit() (ast.NodeVisitor 的方法):      ast 輔助程式.       (line  167)
* visitproc (C type):                    循環垃圾回收的支援. (line  152)
* vline() (curses.window 的方法):        Window Objects.     (line  587)
* voidcmd() (ftplib.FTP 的方法):         FTP 物件.           (line  145)
* volume (zipfile.ZipInfo 的屬性):       ZipInfo 物件.       (line  119)
* vonmisesvariate() (於 random 模組中):  實數分布.           (line   77)
* VT (於 curses.ascii 模組中):           curses ascii --- ASCII 字元的工具程式.
                                                             (line   58)
* W_OK (於 os 模組中):                   Files and Directories.
                                                             (line  107)
* wait_closed() (asyncio.Server 的方法): Server 物件.        (line  115)
* wait_closed() (asyncio.StreamWriter 的方法): StreamWriter. (line  104)
* wait_for() (asyncio.Condition 的方法): Condition.          (line   93)
* wait_for() (threading.Condition 的方法): Condition Objects.
                                                             (line  128)
* wait_for() (於 asyncio 模組中):        Timeouts.           (line  118)
* wait_process() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  416)
* wait_threads_exit() (於 test.support.threading_helper 模組中): test support threading_helper --- Utilities for threading tests.
                                                             (line   41)
* wait_until_any_call_with() (unittest.mock.ThreadingMock 的方法): Mock 類別.
                                                             (line  895)
* wait_until_called() (unittest.mock.ThreadingMock 的方法): Mock 類別.
                                                             (line  880)
* wait() (asyncio.Barrier 的方法):       Barrier.            (line   52)
* wait() (asyncio.Condition 的方法):     Condition.          (line   77)
* wait() (asyncio.Event 的方法):         Event.              (line   43)
* wait() (asyncio.subprocess.Process 的方法): Interacting with Subprocesses.
                                                             (line   38)
* wait() (multiprocessing.pool.AsyncResult 的方法): Process Pools.
                                                             (line  207)
* wait() (subprocess.Popen 的方法):      Popen Objects.      (line   13)
* wait() (threading.Barrier 的方法):     Barrier Objects.    (line   43)
* wait() (threading.Condition 的方法):   Condition Objects.  (line   97)
* wait() (threading.Event 的方法):       Event Objects.      (line   42)
* wait() (於 asyncio 模組中):            Waiting Primitives. (line    6)
* wait() (於 concurrent.futures 模組中): 模組函式.           (line    6)
* wait() (於 multiprocessing.connection 模組中): Listeners and Clients.
                                                             (line  113)
* wait() (於 os 模組中):                 行程管理.           (line  819)
* wait3() (於 os 模組中):                行程管理.           (line  926)
* wait4() (於 os 模組中):                行程管理.           (line  940)
* waitid() (於 os 模組中):               行程管理.           (line  843)
* waitpid() (於 os 模組中):              行程管理.           (line  881)
* waitstatus_to_exitcode() (於 os 模組中): 行程管理.         (line 1058)
* walk_packages() (於 pkgutil 模組中):   pkgutil --- 套件擴充工具程式.
                                                             (line  123)
* walk_stack() (於 traceback 模組中):    traceback --- 列印或取得堆疊回溯 stack traceback.
                                                             (line  205)
* walk_tb() (於 traceback 模組中):       traceback --- 列印或取得堆疊回溯 stack traceback.
                                                             (line  214)
* walk() (email.message.EmailMessage 的方法): email message：表示電子郵件訊息.
                                                             (line  464)
* walk() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  634)
* walk() (pathlib.Path 的方法):          讀取目錄.           (line   97)
* walk() (於 ast 模組中):                ast 輔助程式.       (line  155)
* walk() (於 os 模組中):                 Files and Directories.
                                                             (line 1624)
* walrus operator（海象運算子）:         Boolean operations. (line   38)
* want (doctest.Example 的屬性):         Example 物件.       (line   23)
* warn_default_encoding (sys.flags 的屬性): sys --- 系統特定的參數與函式.
                                                             (line  574)
* warn_explicit() (於 warnings 模組中):  Available Functions.
                                                             (line   62)
* warn() (於 warnings 模組中):           Available Functions.
                                                             (line    6)
* Warning:                               警告.               (line    9)
* Warning <1>:                           例外<4>.            (line    8)
* WARNING (於 logging 模組中):           Logging Levels.     (line   33)
* WARNING (於 tkinter.messagebox 模組中): tkinter messagebox --- Tkinter 訊息提示.
                                                             (line  176)
* warning() (logging.Logger 的方法):     Logger 物件.        (line  290)
* warning() (xml.sax.handler.ErrorHandler 的方法): ErrorHandler 物件.
                                                             (line   29)
* warning() (於 logging 模組中):         Module-Level Functions.
                                                             (line   70)
* warnings （警告）:                     warnings --- 警告控制.
                                                             (line    8)
* WarningsRecorder (test.support.warnings_helper 中的類別): test support warnings_helper --- 用於 warnings 測試的工具.
                                                             (line  116)
* warnoptions (於 sys 模組中):           sys --- 系統特定的參數與函式.
                                                             (line 1987)
* wasSuccessful() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  318)
* WatchedFileHandler (logging.handlers 中的類別): WatchedFileHandler.
                                                             (line   24)
* Wave_read (wave 中的類別):             Wave_read 物件.     (line    6)
* Wave_write (wave 中的類別):            Wave_write 物件.    (line    6)
* WCONTINUED (於 os 模組中):             行程管理.           (line  980)
* WCOREDUMP() (於 os 模組中):            行程管理.           (line 1097)
* WeakKeyDictionary (weakref 中的類別):  weakref --- 弱參照. (line  128)
* WeakMethod (weakref 中的類別):         weakref --- 弱參照. (line  188)
* WeakSet (weakref 中的類別):            weakref --- 弱參照. (line  183)
* WeakValueDictionary (weakref 中的類別): weakref --- 弱參照.
                                                             (line  168)
* WEDNESDAY (於 calendar 模組中):        calendar --- 日曆相關函式.
                                                             (line  336)
* weekday (calendar.IllegalWeekdayError 的屬性): calendar --- 日曆相關函式.
                                                             (line  405)
* weekday() (datetime.date 的方法):      date 物件.          (line  230)
* weekday() (datetime.datetime 的方法):  datetime 物件.      (line  631)
* weekday() (於 calendar 模組中):        calendar --- 日曆相關函式.
                                                             (line  281)
* weekheader() (於 calendar 模組中):     calendar --- 日曆相關函式.
                                                             (line  286)
* weibullvariate() (於 random 模組中):   實數分布.           (line   87)
* WEXITED (於 os 模組中):                行程管理.           (line  989)
* WEXITSTATUS() (於 os 模組中):          行程管理.           (line 1143)
* wfile (http.server.BaseHTTPRequestHandler 的屬性): http server — HTTP 伺服器.
                                                             (line  123)
* wfile (socketserver.DatagramRequestHandler 的屬性): Request Handler Objects.
                                                             (line   68)
* whatis (pdb command):                  Debugger Commands.  (line  281)
* when() (asyncio.Timeout 的方法):       Timeouts.           (line   63)
* when() (asyncio.TimerHandle 的方法):   回呼處理.           (line   34)
* where (pdb command):                   Debugger Commands.  (line   81)
* which() (於 shutil 模組中):            Directory and files operations.
                                                             (line  407)
* whichdb() (於 dbm 模組中):             dbm --- Unix "databases" 的介面.
                                                             (line   36)
* While (ast 中的類別):                  流程控制.           (line   71)
* whitespace (shlex.shlex 的屬性):       shlex 物件.         (line  104)
* whitespace (於 string 模組中):         字串常數.           (line   46)
* whitespace_split (shlex.shlex 的屬性): shlex 物件.         (line  128)
* Widget (tkinter.ttk 中的類別):         ttk Widget.         (line    9)
* width (sys.hash_info 的屬性):          sys --- 系統特定的參數與函式.
                                                             (line  997)
* width (textwrap.TextWrapper 的屬性):   textwrap --- 文字包裝與填充.
                                                             (line  160)
* width() (於 turtle 模組中):            Drawing state.      (line   18)
* WIFCONTINUED() (於 os 模組中):         行程管理.           (line 1107)
* WIFEXITED() (於 os 模組中):            行程管理.           (line 1135)
* WIFSIGNALED() (於 os 模組中):          行程管理.           (line 1128)
* WIFSTOPPED() (於 os 模組中):           行程管理.           (line 1117)
* win32_edition() (於 platform 模組中):  Windows 平台.       (line   17)
* win32_is_iot() (於 platform 模組中):   Windows 平台.       (line   24)
* win32_ver() (於 platform 模組中):      Windows 平台.       (line    6)
* WinDLL (ctypes 中的類別):              Loading shared libraries.
                                                             (line   53)
* window manager (widgets):              The Window Manager. (line    6)
* window_height() (於 turtle 模組中):    Settings and special methods.
                                                             (line  103)
* window_width() (於 turtle 模組中):     Settings and special methods.
                                                             (line  110)
* window() (curses.panel.Panel 的方法):  Panel Objects.      (line   62)
* Windows:                               完整的 Python 程式. (line   19)
* Windows ini file（Windows ini 檔案）:  configparser --- 設定檔剖析器.
                                                             (line    8)
* WindowsError:                          實體例外.           (line  420)
* WindowsPath (pathlib 中的類別):        實體路徑.           (line   34)
* WindowsProactorEventLoopPolicy (asyncio 中的類別): Policy Objects.
                                                             (line   77)
* WindowsRegistryFinder (importlib.machinery 中的類別): importlib machinery -- Importers and path hooks.
                                                             (line   89)
* WindowsSelectorEventLoopPolicy (asyncio 中的類別): Policy Objects.
                                                             (line   70)
* winerror (OSError 的屬性):             實體例外.           (line  142)
* WinError() (於 ctypes 模組中):         Utility functions.  (line  200)
* WINFUNCTYPE() (於 ctypes 模組中):      Function prototypes.
                                                             (line   25)
* WinSock:                               select --- 等待 I/O 完成.
                                                             (line  149)
* winver (於 sys 模組中):                sys --- 系統特定的參數與函式.
                                                             (line 1993)
* With (ast 中的類別):                   流程控制.           (line  221)
* WITH_EXCEPT_START (opcode):            Python Bytecode Instructions.
                                                             (line  480)
* with_hostmask (ipaddress.IPv4Interface 的屬性): Interface objects.
                                                             (line   55)
* with_hostmask (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line  123)
* with_hostmask (ipaddress.IPv6Interface 的屬性): Interface objects.
                                                             (line   82)
* with_hostmask (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  325)
* with_name() (pathlib.PurePath 的方法): 方法與屬性.         (line  341)
* with_netmask (ipaddress.IPv4Interface 的屬性): Interface objects.
                                                             (line   46)
* with_netmask (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line  118)
* with_netmask (ipaddress.IPv6Interface 的屬性): Interface objects.
                                                             (line   80)
* with_netmask (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  323)
* with_prefixlen (ipaddress.IPv4Interface 的屬性): Interface objects.
                                                             (line   37)
* with_prefixlen (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line  105)
* with_prefixlen (ipaddress.IPv6Interface 的屬性): Interface objects.
                                                             (line   78)
* with_prefixlen (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  317)
* with_pymalloc() (於 test.support 模組中): test support --- Python 測試套件的工具.
                                                             (line  252)
* with_segments() (pathlib.PurePath 的方法): 方法與屬性.     (line  396)
* with_stem() (pathlib.PurePath 的方法): 方法與屬性.         (line  357)
* with_suffix() (pathlib.PurePath 的方法): 方法與屬性.       (line  380)
* with_traceback() (BaseException 的方法): 基底類別 base classes.
                                                             (line   22)
* withitem (ast 中的類別):               流程控制.           (line  230)
* WNOHANG (於 os 模組中):                行程管理.           (line 1023)
* WNOWAIT (於 os 模組中):                行程管理.           (line 1031)
* wordchars (shlex.shlex 的屬性):        shlex 物件.         (line   91)
* World Wide Web （全球資訊網）:         網路協定 Internet protocols 及支援.
                                                             (line    6)
* World Wide Web （全球資訊網） <1>:     urllib parse --- 將 URL 剖析成元件.
                                                             (line    8)
* World Wide Web （全球資訊網） <2>:     urllib robotparser --- robots txt 的剖析器.
                                                             (line    8)
* wrap_bio() (ssl.SSLContext 的方法):    SSL Contexts.       (line  458)
* wrap_future() (於 asyncio 模組中):     Future 函式.        (line   47)
* wrap_socket() (ssl.SSLContext 的方法): SSL Contexts.       (line  391)
* wrap() (textwrap.TextWrapper 的方法):  textwrap --- 文字包裝與填充.
                                                             (line  287)
* wrap() (於 textwrap 模組中):           textwrap --- 文字包裝與填充.
                                                             (line   16)
* wrapper() (於 curses 模組中):          函式<5>.            (line  609)
* WrapperDescriptorType (於 types 模組中): Standard Interpreter Types.
                                                             (line   87)
* wraps() (於 functools 模組中):         functools --- 可呼叫物件上的高階函式與操作.
                                                             (line  603)
* WRITABLE (inspect.BufferFlags 的屬性): Buffer flags.       (line   17)
* WRITABLE (於 _tkinter 模組中):         File Handlers.      (line   41)
* writable() (bz2.BZ2File 的方法):       De compression of files.
                                                             (line  105)
* writable() (io.IOBase 的方法):         I/O 基礎類別.       (line  135)
* WRITE (inspect.BufferFlags 的屬性):    Buffer flags.       (line   51)
* write_byte() (mmap.mmap 的方法):       mmap --- 記憶體映射檔案的支援.
                                                             (line  335)
* write_bytes() (pathlib.Path 的方法):   Reading and writing files.
                                                             (line   64)
* write_docstringdict() (於 turtle 模組中): Translation of docstrings into different languages.
                                                             (line   10)
* write_eof() (asyncio.StreamWriter 的方法): StreamWriter.   (line   48)
* write_eof() (asyncio.WriteTransport 的方法): Write-only Transports.
                                                             (line   74)
* write_eof() (ssl.MemoryBIO 的方法):    Memory BIO Support<2>.
                                                             (line  161)
* write_history_file() (於 readline 模組中): History file.   (line   14)
* WRITE_RESTRICTED（C 巨集）:            Member flags.       (line   32)
* write_results() (trace.CoverageResults 的方法): Programmatic Interface.
                                                             (line   57)
* write_text() (pathlib.Path 的方法):    Reading and writing files.
                                                             (line   46)
* write_through (io.TextIOWrapper 的屬性): 文字 I/O<2>.      (line  173)
* write() (asyncio.StreamWriter 的方法): StreamWriter.       (line   13)
* write() (asyncio.WriteTransport 的方法): Write-only Transports.
                                                             (line   60)
* write() (code.InteractiveInterpreter 的方法): Interactive Interpreter Objects.
                                                             (line   63)
* write() (codecs.StreamWriter 的方法):  StreamWriter 物件.  (line   31)
* write() (configparser.ConfigParser 的方法): ConfigParser 物件.
                                                             (line  284)
* write() (email.generator.BytesGenerator 的方法): email generator：產生 MIME 文件.
                                                             (line  117)
* write() (email.generator.Generator 的方法): email generator：產生 MIME 文件.
                                                             (line  213)
* write() (io.BufferedIOBase 的方法):    I/O 基礎類別.       (line  282)
* write() (io.BufferedWriter 的方法):    Buffered Streams.   (line  131)
* write() (io.RawIOBase 的方法):         I/O 基礎類別.       (line  187)
* write() (io.TextIOBase 的方法):        文字 I/O<2>.        (line   94)
* write() (mmap.mmap 的方法):            mmap --- 記憶體映射檔案的支援.
                                                             (line  320)
* write() (sqlite3.Blob 的方法):         Blob 物件.          (line   53)
* write() (ssl.MemoryBIO 的方法):        Memory BIO Support<2>.
                                                             (line  153)
* write() (ssl.SSLSocket 的方法):        SSL Sockets.        (line   86)
* write() (xml.etree.ElementTree.ElementTree 的方法): ElementTree 物件.
                                                             (line   62)
* write() (zipfile.ZipFile 的方法):      ZipFile 物件.       (line  269)
* write() (於 os 模組中):                File Descriptor Operations.
                                                             (line  911)
* write() (於 turtle 模組中):            More drawing control.
                                                             (line   29)
* writeframes() (wave.Wave_write 的方法): Wave_write 物件.   (line   73)
* writeframesraw() (wave.Wave_write 的方法): Wave_write 物件.
                                                             (line   67)
* writeheader() (csv.DictWriter 的方法): 寫入器物件.         (line   35)
* writelines() (asyncio.StreamWriter 的方法): StreamWriter.  (line   23)
* writelines() (asyncio.WriteTransport 的方法): Write-only Transports.
                                                             (line   67)
* writelines() (codecs.StreamWriter 的方法): StreamWriter 物件.
                                                             (line   35)
* writelines() (io.IOBase 的方法):       I/O 基礎類別.       (line  140)
* writepy() (zipfile.PyZipFile 的方法):  PyZipFile 物件.     (line   20)
* writer() (於 csv 模組中):              模組內容<3>.        (line   36)
* writerow() (csv.csvwriter 的方法):     寫入器物件.         (line   14)
* writerows() (csv.csvwriter 的方法):    寫入器物件.         (line   22)
* writestr() (zipfile.ZipFile 的方法):   ZipFile 物件.       (line  304)
* WriteTransport (asyncio 中的類別):     Transports Hierarchy.
                                                             (line   11)
* writev() (於 os 模組中):               File Descriptor Operations.
                                                             (line  929)
* writexml() (xml.dom.minidom.Node 的方法): DOM 物件.        (line   27)
* writing;values:                        Expression statements.
                                                             (line   17)
* WrongDocumentErr:                      例外<15>.           (line   97)
* wsgi_file_wrapper (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  228)
* wsgi_multiprocess (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  131)
* wsgi_multithread (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  125)
* wsgi_run_once (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- 伺服器 / 閘道基本類別.
                                                             (line  137)
* WSGIApplication (於 wsgiref.types 模組中): wsgiref types -- 用於靜態型別檢查的 WSGI 型別.
                                                             (line   19)
* WSGIEnvironment (於 wsgiref.types 模組中): wsgiref types -- 用於靜態型別檢查的 WSGI 型別.
                                                             (line   15)
* WSGIRequestHandler (wsgiref.simple_server 中的類別): wsgiref simple_server -- 一個簡單的 WSGI HTTP 伺服器.
                                                             (line   68)
* WSGIServer (wsgiref.simple_server 中的類別): wsgiref simple_server -- 一個簡單的 WSGI HTTP 伺服器.
                                                             (line   40)
* wShowWindow (subprocess.STARTUPINFO 的屬性): Windows Popen Helpers.
                                                             (line   49)
* WSTOPPED (於 os 模組中):               行程管理.           (line 1001)
* WSTOPSIG() (於 os 模組中):             行程管理.           (line 1152)
* wstring_at() (於 ctypes 模組中):       Utility functions.  (line  211)
* WTERMSIG() (於 os 模組中):             行程管理.           (line 1161)
* WUNTRACED (於 os 模組中):              行程管理.           (line 1012)
* WWW:                                   網路協定 Internet protocols 及支援.
                                                             (line    6)
* WWW <1>:                               urllib parse --- 將 URL 剖析成元件.
                                                             (line    8)
* WWW <2>:                               urllib robotparser --- robots txt 的剖析器.
                                                             (line    8)
* WWW;server（伺服器）:                  http server — HTTP 伺服器.
                                                             (line    8)
* X (於 re 模組中):                      旗標.               (line  126)
* X_OK (於 os 模組中):                   Files and Directories.
                                                             (line  107)
* X509 certificate（X509 憑證）:         SSL Contexts.       (line  764)
* xatom() (imaplib.IMAP4 的方法):        IMAP4 物件.         (line  386)
* XATTR_CREATE (於 os 模組中):           Linux extended attributes.
                                                             (line   87)
* XATTR_REPLACE (於 os 模組中):          Linux extended attributes.
                                                             (line   93)
* XATTR_SIZE_MAX (於 os 模組中):         Linux extended attributes.
                                                             (line   82)
* xcor() (於 turtle 模組中):             Tell Turtle's state.
                                                             (line   34)
* XHTML:                                 html parser --- 簡單的 HTML 和 XHTML 剖析器.
                                                             (line    8)
* XHTML_NAMESPACE (於 xml.dom 模組中):   模組內容<6>.        (line   53)
* XML_ERROR_ABORTED (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  180)
* XML_ERROR_AMPLIFICATION_LIMIT_BREACH (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  215)
* XML_ERROR_ASYNC_ENTITY (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line   29)
* XML_ERROR_ATTRIBUTE_EXTERNAL_ENTITY_REF (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line   31)
* XML_ERROR_BAD_CHAR_REF (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line   37)
* XML_ERROR_BINARY_ENTITY_REF (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line   42)
* XML_ERROR_CANT_CHANGE_FEATURE_ONCE_PARSING (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  135)
* XML_ERROR_DUPLICATE_ATTRIBUTE (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line   47)
* XML_ERROR_ENTITY_DECLARED_IN_PE (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  126)
* XML_ERROR_EXTERNAL_ENTITY_HANDLING (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  116)
* XML_ERROR_FEATURE_REQUIRES_XML_DTD (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  128)
* XML_ERROR_FINISHED (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  184)
* XML_ERROR_INCOMPLETE_PE (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  152)
* XML_ERROR_INCORRECT_ENCODING (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line   51)
* XML_ERROR_INVALID_ARGUMENT (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  207)
* XML_ERROR_INVALID_TOKEN (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line   53)
* XML_ERROR_JUNK_AFTER_DOC_ELEMENT (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line   59)
* XML_ERROR_MISPLACED_XML_PI (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line   64)
* XML_ERROR_NO_BUFFER (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  211)
* XML_ERROR_NO_ELEMENTS (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line   69)
* XML_ERROR_NO_MEMORY (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line   74)
* XML_ERROR_NOT_STANDALONE (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  118)
* XML_ERROR_NOT_SUSPENDED (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  175)
* XML_ERROR_PARAM_ENTITY_REF (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line   78)
* XML_ERROR_PARTIAL_CHAR (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line   82)
* XML_ERROR_PUBLICID (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  165)
* XML_ERROR_RECURSIVE_ENTITY_REF (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line   86)
* XML_ERROR_RESERVED_NAMESPACE_URI (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  202)
* XML_ERROR_RESERVED_PREFIX_XML (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  192)
* XML_ERROR_RESERVED_PREFIX_XMLNS (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  197)
* XML_ERROR_SUSPEND_PE (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  190)
* XML_ERROR_SUSPENDED (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  169)
* XML_ERROR_SYNTAX (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line   91)
* XML_ERROR_TAG_MISMATCH (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line   95)
* XML_ERROR_TEXT_DECL (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  160)
* XML_ERROR_UNBOUND_PREFIX (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  142)
* XML_ERROR_UNCLOSED_CDATA_SECTION (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  112)
* XML_ERROR_UNCLOSED_TOKEN (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line   99)
* XML_ERROR_UNDECLARING_PREFIX (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  147)
* XML_ERROR_UNDEFINED_ENTITY (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  104)
* XML_ERROR_UNEXPECTED_STATE (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  124)
* XML_ERROR_UNKNOWN_ENCODING (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  108)
* XML_ERROR_XML_DECL (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  156)
* XML_NAMESPACE (於 xml.dom 模組中):     模組內容<6>.        (line   42)
* XML() (於 xml.etree.ElementTree 模組中): 函式<8>.          (line  269)
* xmlcharrefreplace_errors() (於 codecs 模組中): Error Handlers.
                                                             (line  172)
* xmlcharrefreplace;error handler's name（錯誤處理器名稱）: Error Handlers.
                                                             (line   54)
* XmlDeclHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser 物件<2>.
                                                             (line  213)
* XMLFilterBase (xml.sax.saxutils 中的類別): xml sax saxutils --- SAX 工具程式.
                                                             (line   72)
* XMLGenerator (xml.sax.saxutils 中的類別): xml sax saxutils --- SAX 工具程式.
                                                             (line   56)
* XMLID() (於 xml.etree.ElementTree 模組中): 函式<8>.        (line  277)
* XMLNS_NAMESPACE (於 xml.dom 模組中):   模組內容<6>.        (line   47)
* XMLParser (xml.etree.ElementTree 中的類別): XMLParser 物件.
                                                             (line    6)
* XMLParserType (於 xml.parsers.expat 模組中): xml parsers expat --- 使用 Expat 進行快速 XML 剖析.
                                                             (line   35)
* XMLPullParser (xml.etree.ElementTree 中的類別): XMLPullParser 物件.
                                                             (line    6)
* XMLReader (xml.sax.xmlreader 中的類別): xml sax xmlreader --- XML 剖析器的介面.
                                                             (line   16)
* xor() (於 operator 模組中):            operator --- 標準運算子替代函式.
                                                             (line  157)
* xview() (tkinter.ttk.Treeview 的方法): ttk Treeview.       (line  316)
* ycor() (於 turtle 模組中):             Tell Turtle's state.
                                                             (line   46)
* year (datetime.date 的屬性):           date 物件.          (line  116)
* year (datetime.datetime 的屬性):       datetime 物件.      (line  298)
* Year 2038（2038 年問題）:              time --- 時間存取與轉換.
                                                             (line   24)
* yeardatescalendar() (calendar.Calendar 的方法): calendar --- 日曆相關函式.
                                                             (line   89)
* yeardays2calendar() (calendar.Calendar 的方法): calendar --- 日曆相關函式.
                                                             (line   96)
* yeardayscalendar() (calendar.Calendar 的方法): calendar --- 日曆相關函式.
                                                             (line  102)
* YES (於 tkinter.messagebox 模組中):    tkinter messagebox --- Tkinter 訊息提示.
                                                             (line  137)
* YESEXPR (於 locale 模組中):            locale --- 國際化服務.
                                                             (line  275)
* YESNO (於 tkinter.messagebox 模組中):  tkinter messagebox --- Tkinter 訊息提示.
                                                             (line  160)
* YESNOCANCEL (於 tkinter.messagebox 模組中): tkinter messagebox --- Tkinter 訊息提示.
                                                             (line  164)
* Yield (ast 中的類別):                  函式和類別定義.     (line  117)
* YIELD_VALUE (opcode):                  Python Bytecode Instructions.
                                                             (line  412)
* yield;expression:                      Yield expressions.  (line    6)
* yield;yield from（在有什麼新功能中）:  PEP 3151 Reworking the OS and IO exception hierarchy.
                                                             (line   87)
* yield;範例:                            Generator-iterator methods.
                                                             (line   80)
* YieldFrom (ast 中的類別):              函式和類別定義.     (line  117)
* yiq_to_rgb() (於 colorsys 模組中):     colorsys --- 顏色系統間的轉換.
                                                             (line   29)
* yview() (tkinter.ttk.Treeview 的方法): ttk Treeview.       (line  320)
* z;於字串格式化:                        格式規格 Format Specification 迷你語言.
                                                             (line   74)
* z85decode() (於 base64 模組中):        base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  213)
* z85encode() (於 base64 模組中):        base64 --- Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  205)
* Zen of Python（Python 之禪）:          術語表.             (line 1318)
* ZeroDivisionError:                     實體例外.           (line  408)
* zfill() (bytearray 的方法):            Bytes and Bytearray Operations.
                                                             (line  749)
* zfill() (bytes 的方法):                Bytes and Bytearray Operations.
                                                             (line  749)
* zfill() (str 的方法):                  String Methods<2>.  (line  676)
* ZIP_BZIP2 (於 zipfile 模組中):         zipfile --- 處理 ZIP 封存檔案.
                                                             (line   94)
* ZIP_DEFLATED (於 zipfile 模組中):      zipfile --- 處理 ZIP 封存檔案.
                                                             (line   89)
* zip_longest() (於 itertools 模組中):   Itertool 函式.      (line  558)
* ZIP_LZMA (於 zipfile 模組中):          zipfile --- 處理 ZIP 封存檔案.
                                                             (line  101)
* ZIP_STORED (於 zipfile 模組中):        zipfile --- 處理 ZIP 封存檔案.
                                                             (line   85)
* zipapp 命令列選項; -c:                 命令執行列介面.     (line   45)
* zipapp 命令列選項; -compress:          命令執行列介面.     (line   45)
* zipapp 命令列選項; -h:                 命令執行列介面.     (line   61)
* zipapp 命令列選項; -help:              命令執行列介面.     (line   61)
* zipapp 命令列選項; -info:              命令執行列介面.     (line   55)
* zipapp 命令列選項; -m:                 命令執行列介面.     (line   35)
* zipapp 命令列選項; -main:              命令執行列介面.     (line   35)
* zipapp 命令列選項; -o:                 命令執行列介面.     (line   18)
* zipapp 命令列選項; -output:            命令執行列介面.     (line   18)
* zipapp 命令列選項; -p:                 命令執行列介面.     (line   29)
* zipapp 命令列選項; -python:            命令執行列介面.     (line   29)
* ZipFile (zipfile 中的類別):            ZipFile 物件.       (line    6)
* zipfile 命令列選項; -c:                Command-line options.
                                                             (line   11)
* zipfile 命令列選項; -create:           Command-line options.
                                                             (line   11)
* zipfile 命令列選項; -e:                Command-line options.
                                                             (line   16)
* zipfile 命令列選項; -extract:          Command-line options.
                                                             (line   16)
* zipfile 命令列選項; -l:                Command-line options.
                                                             (line    6)
* zipfile 命令列選項; -list:             Command-line options.
                                                             (line    6)
* zipfile 命令列選項; -metadata-encoding: Command-line options.
                                                             (line   26)
* zipfile 命令列選項; -t:                Command-line options.
                                                             (line   21)
* zipfile 命令列選項; -test:             Command-line options.
                                                             (line   21)
* zipimporter (zipimport 中的類別):      zipimporter 物件.   (line    8)
* ZipImportError:                        zipimport --- 從 Zip 封存檔案匯入模組.
                                                             (line   58)
* ZipInfo (zipfile 中的類別):            zipfile --- 處理 ZIP 封存檔案.
                                                             (line   59)
* ZLIB_RUNTIME_VERSION (於 zlib 模組中): zlib --- 相容於 gzip 的壓縮.
                                                             (line  249)
* ZLIB_VERSION (於 zlib 模組中):         zlib --- 相容於 gzip 的壓縮.
                                                             (line  243)
* ZoneInfo (zoneinfo 中的類別):          The ZoneInfo class. (line    6)
* ZoneInfoNotFoundError:                 Exceptions and warnings.
                                                             (line    6)
* zscore() (statistics.NormalDist 的方法): NormalDist 物件.  (line  102)
* 二進制模式:                            內建函式.           (line 1294)
* 命令列選項; -?:                        Generic options.    (line    6)
* 命令列選項; -b:                        Miscellaneous options.
                                                             (line    6)
* 命令列選項; -B:                        Miscellaneous options.
                                                             (line   16)
* 命令列選項; -build:                    Cross Compiling Options.
                                                             (line   12)
* 命令列選項; -c:                        介面選項.           (line   37)
* 命令列選項; -check-hash-based-pycs:    Miscellaneous options.
                                                             (line   21)
* 命令列選項; -d:                        Miscellaneous options.
                                                             (line   35)
* 命令列選項; -disable-gil:              一般選項.           (line  223)
* 命令列選項; -disable-ipv6:             一般選項.           (line   16)
* 命令列選項; -disable-test-modules:     安裝選項.           (line   23)
* 命令列選項; -E:                        Miscellaneous options.
                                                             (line   43)
* 命令列選項; -enable-big-digits:        一般選項.           (line   21)
* 命令列選項; -enable-bolt:              Performance options.
                                                             (line   61)
* 命令列選項; -enable-framework:         macOS 選項.         (line   15)
* 命令列選項; -enable-framework <1>:     macOS 選項.         (line   17)
* 命令列選項; -enable-framework <2>:     iOS Options.        (line    8)
* 命令列選項; -enable-loadable-sqlite-extensions: 一般選項.  (line    6)
* 命令列選項; -enable-optimizations:     Performance options.
                                                             (line   10)
* 命令列選項; -enable-profiling:         Performance options.
                                                             (line  127)
* 命令列選項; -enable-pystats:           一般選項.           (line  130)
* 命令列選項; -enable-shared:            Linker options<2>.  (line    6)
* 命令列選項; -enable-universalsdk:      macOS 選項.         (line    8)
* 命令列選項; -enable-universalsdk <1>:  macOS 選項.         (line   10)
* 命令列選項; -enable-wasm-dynamic-linking: WebAssembly 選項.
                                                             (line   16)
* 命令列選項; -enable-wasm-pthreads:     WebAssembly 選項.   (line   26)
* 命令列選項; -exec-prefix:              安裝選項.           (line   16)
* 命令列選項; -h:                        Generic options.    (line    6)
* 命令列選項; -help:                     Generic options.    (line    6)
* 命令列選項; -help-all:                 Generic options.    (line   27)
* 命令列選項; -help-env:                 Generic options.    (line   13)
* 命令列選項; -help-xoptions:            Generic options.    (line   20)
* 命令列選項; -host:                     Cross Compiling Options.
                                                             (line   16)
* 命令列選項; -i:                        Miscellaneous options.
                                                             (line   50)
* 命令列選項; -I:                        Miscellaneous options.
                                                             (line   61)
* 命令列選項; -J:                        你不該使用的選項.   (line    6)
* 命令列選項; -m:                        介面選項.           (line   51)
* 命令列選項; -O:                        Miscellaneous options.
                                                             (line   73)
* 命令列選項; -OO:                       Miscellaneous options.
                                                             (line   82)
* 命令列選項; -P:                        Miscellaneous options.
                                                             (line   90)
* 命令列選項; -prefix:                   安裝選項.           (line    6)
* 命令列選項; -q:                        Miscellaneous options.
                                                             (line  109)
* 命令列選項; -R:                        Miscellaneous options.
                                                             (line  116)
* 命令列選項; -s:                        Miscellaneous options.
                                                             (line  141)
* 命令列選項; -S:                        Miscellaneous options.
                                                             (line  153)
* 命令列選項; -u:                        Miscellaneous options.
                                                             (line  161)
* 命令列選項; -V:                        Generic options.    (line   33)
* 命令列選項; -v:                        Miscellaneous options.
                                                             (line  171)
* 命令列選項; -version:                  Generic options.    (line   33)
* 命令列選項; -W:                        Miscellaneous options.
                                                             (line  184)
* 命令列選項; -with-address-sanitizer:   Debug options.      (line   59)
* 命令列選項; -with-app-store-compliance: macOS 選項.        (line   51)
* 命令列選項; -with-app-store-compliance <1>: macOS 選項.    (line   53)
* 命令列選項; -with-assertions:          Debug options.      (line   34)
* 命令列選項; -with-build-python:        Cross Compiling Options.
                                                             (line   20)
* 命令列選項; -with-builtin-hashlib-hashes: Security Options.
                                                             (line   20)
* 命令列選項; -with-computed-gotos:      Performance options.
                                                             (line   98)
* 命令列選項; -with-dbmliborder:         一般選項.           (line   67)
* 命令列選項; -with-dtrace:              Debug options.      (line   51)
* 命令列選項; -with-emscripten-target:   WebAssembly 選項.   (line    6)
* 命令列選項; -with-ensurepip:           安裝選項.           (line   31)
* 命令列選項; -with-framework-name:      macOS 選項.         (line   46)
* 命令列選項; -with-framework-name <1>:  iOS Options.        (line   13)
* 命令列選項; -with-hash-algorithm:      Security Options.   (line    6)
* 命令列選項; -with-libc:                函式庫選項.         (line   58)
* 命令列選項; -with-libm:                函式庫選項.         (line   53)
* 命令列選項; -with-libs:                函式庫選項.         (line    6)
* 命令列選項; -with-lto:                 Performance options.
                                                             (line   45)
* 命令列選項; -with-memory-sanitizer:    Debug options.      (line   66)
* 命令列選項; -with-openssl:             函式庫選項.         (line   63)
* 命令列選項; -with-openssl-rpath:       函式庫選項.         (line   69)
* 命令列選項; -with-pkg-config:          一般選項.           (line  117)
* 命令列選項; -with-platlibdir:          一般選項.           (line   95)
* 命令列選項; -with-pydebug:             Debug options.      (line    6)
* 命令列選項; -with-readline:            函式庫選項.         (line   35)
* 命令列選項; -with-ssl-default-suites:  Security Options.   (line   39)
* 命令列選項; -with-strict-overflow:     Performance options.
                                                             (line  131)
* 命令列選項; -with-suffix:              一般選項.           (line   32)
* 命令列選項; -with-system-expat:        函式庫選項.         (line   10)
* 命令列選項; -with-system-libmpdec:     函式庫選項.         (line   15)
* 命令列選項; -with-thread-sanitizer:    Debug options.      (line   80)
* 命令列選項; -with-trace-refs:          Debug options.      (line   11)
* 命令列選項; -with-tzpath:              一般選項.           (line   43)
* 命令列選項; -with-undefined-behavior-sanitizer: Debug options.
                                                             (line   73)
* 命令列選項; -with-universal-archs:     macOS 選項.         (line   23)
* 命令列選項; -with-valgrind:            Debug options.      (line   47)
* 命令列選項; -with-wheel-pkg-dir:       一般選項.           (line  105)
* 命令列選項; -without-c-locale-coercion: 一般選項.          (line   80)
* 命令列選項; -without-decimal-contextvar: 一般選項.         (line   56)
* 命令列選項; -without-doc-strings:      Performance options.
                                                             (line  117)
* 命令列選項; -without-freelists:        一般選項.           (line   89)
* 命令列選項; -without-mimalloc:         Performance options.
                                                             (line  103)
* 命令列選項; -without-pymalloc:         Performance options.
                                                             (line  110)
* 命令列選項; -without-readline:         函式庫選項.         (line   45)
* 命令列選項; -without-static-libpython: Linker options<2>.  (line   11)
* 命令列選項; -x:                        Miscellaneous options.
                                                             (line  245)
* 命令列選項; -X:                        Miscellaneous options.
                                                             (line  250)
* 命令列選項; BOLT_APPLY_FLAGS:          Performance options.
                                                             (line   86)
* 命令列選項; BOLT_INSTRUMENT_FLAGS:     Performance options.
                                                             (line   92)
* 命令列選項; BZIP2_CFLAGS:              Options for third-party dependencies.
                                                             (line    8)
* 命令列選項; BZIP2_LIBS:                Options for third-party dependencies.
                                                             (line   10)
* 命令列選項; CC:                        C compiler options. (line    6)
* 命令列選項; CFLAGS:                    C compiler options. (line   10)
* 命令列選項; CONFIG_SITE:               Cross Compiling Options.
                                                             (line   26)
* 命令列選項; CPP:                       C compiler options. (line   14)
* 命令列選項; CPPFLAGS:                  C compiler options. (line   18)
* 命令列選項; CURSES_CFLAGS:             Options for third-party dependencies.
                                                             (line   15)
* 命令列選項; CURSES_LIBS:               Options for third-party dependencies.
                                                             (line   17)
* 命令列選項; GDBM_CFLAGS:               Options for third-party dependencies.
                                                             (line   22)
* 命令列選項; GDBM_LIBS:                 Options for third-party dependencies.
                                                             (line   24)
* 命令列選項; HOSTRUNNER:                Cross Compiling Options.
                                                             (line   38)
* 命令列選項; LDFLAGS:                   Linker options.     (line    6)
* 命令列選項; LIBB2_CFLAGS:              Options for third-party dependencies.
                                                             (line   28)
* 命令列選項; LIBB2_LIBS:                Options for third-party dependencies.
                                                             (line   30)
* 命令列選項; LIBEDIT_CFLAGS:            Options for third-party dependencies.
                                                             (line   35)
* 命令列選項; LIBEDIT_LIBS:              Options for third-party dependencies.
                                                             (line   37)
* 命令列選項; LIBFFI_CFLAGS:             Options for third-party dependencies.
                                                             (line   42)
* 命令列選項; LIBFFI_LIBS:               Options for third-party dependencies.
                                                             (line   44)
* 命令列選項; LIBLZMA_CFLAGS:            Options for third-party dependencies.
                                                             (line   59)
* 命令列選項; LIBLZMA_LIBS:              Options for third-party dependencies.
                                                             (line   61)
* 命令列選項; LIBMPDEC_CFLAGS:           Options for third-party dependencies.
                                                             (line   49)
* 命令列選項; LIBMPDEC_LIBS:             Options for third-party dependencies.
                                                             (line   51)
* 命令列選項; LIBREADLINE_CFLAGS:        Options for third-party dependencies.
                                                             (line   66)
* 命令列選項; LIBREADLINE_LIBS:          Options for third-party dependencies.
                                                             (line   68)
* 命令列選項; LIBS:                      Linker options.     (line   10)
* 命令列選項; LIBSQLITE3_CFLAGS:         Options for third-party dependencies.
                                                             (line   73)
* 命令列選項; LIBSQLITE3_LIBS:           Options for third-party dependencies.
                                                             (line   75)
* 命令列選項; LIBUUID_CFLAGS:            Options for third-party dependencies.
                                                             (line   80)
* 命令列選項; LIBUUID_LIBS:              Options for third-party dependencies.
                                                             (line   82)
* 命令列選項; MACHDEP:                   Linker options.     (line   14)
* 命令列選項; PANEL_CFLAGS:              Options for third-party dependencies.
                                                             (line   87)
* 命令列選項; PANEL_LIBS:                Options for third-party dependencies.
                                                             (line   89)
* 命令列選項; PKG_CONFIG:                一般選項.           (line  235)
* 命令列選項; PKG_CONFIG_LIBDIR:         一般選項.           (line  239)
* 命令列選項; PKG_CONFIG_PATH:           一般選項.           (line  241)
* 命令列選項; TCLTK_CFLAGS:              Options for third-party dependencies.
                                                             (line   96)
* 命令列選項; TCLTK_LIBS:                Options for third-party dependencies.
                                                             (line   98)
* 命令列選項; ZLIB_CFLAGS:               Options for third-party dependencies.
                                                             (line  102)
* 命令列選項; ZLIB_LIBS:                 Options for third-party dependencies.
                                                             (line  104)
* 基準量測 (Benchmarking):               timeit --- 測量小量程式片段的執行時間.
                                                             (line    8)
* 安全雜湊演算法、SHA1、SHA2、SHA224、SHA256、SHA384、SHA512、SHA3、Shake、Blake2: hashlib --- 安全雜湊與訊息摘要.
                                                             (line    8)
* 性能表現:                              timeit --- 測量小量程式片段的執行時間.
                                                             (line    8)
* 模組;__main__:                         Initializing and finalizing the interpreter.
                                                             (line    7)
* 模組;__main__ <1>:                     Sub-interpreter support.
                                                             (line  112)
* 模組;__main__ <2>:                     Sub-interpreter support.
                                                             (line  193)
* 模組;_thread:                          高階 API.           (line   49)
* 模組;array（陣列）:                    Binary Sequence Types --- bytes bytearray memoryview.
                                                             (line    6)
* 模組;builtins（內建）:                 Initializing and finalizing the interpreter.
                                                             (line    7)
* 模組;builtins（內建） <1>:             Sub-interpreter support.
                                                             (line  112)
* 模組;builtins（內建） <2>:             Sub-interpreter support.
                                                             (line  193)
* 模組;math:                             數值型別 --- int、float、complex.
                                                             (line   97)
* 模組;re:                               String Methods<2>.  (line    6)
* 模組;search（搜尋）;path（路徑）:      Initializing and finalizing the interpreter.
                                                             (line    7)
* 模組;search（搜尋）;path（路徑） <1>:  Process-wide parameters.
                                                             (line  134)
* 模組;sys:                              Initializing and finalizing the interpreter.
                                                             (line    7)
* 模組;sys <1>:                          Sub-interpreter support.
                                                             (line  112)
* 模組;sys <2>:                          Sub-interpreter support.
                                                             (line  193)
* 模組;type（型別）:                     Type Objects.       (line    6)
* 環境變數; __PYVENV_LAUNCHER__:         PyConfig.           (line  184)
* 環境變數; __PYVENV_LAUNCHER__ <1>:     PyConfig.           (line  702)
* 環境變數; %APPDATA%:                   Redirection of local data registry and temporary paths.
                                                             (line   13)
* 環境變數; APPDATA:                     PEP 370 Per-user site-packages Directory.
                                                             (line   26)
* 環境變數; BASECFLAGS:                  編譯器旗標.         (line   66)
* 環境變數; BASECPPFLAGS:                Preprocessor flags. (line   22)
* 環境變數; BLDSHARED:                   Linker flags.       (line   67)
* 環境變數; BROWSER:                     webbrowser --- 方便的網頁瀏覽器控制器.
                                                             (line   20)
* 環境變數; BROWSER <1>:                 webbrowser --- 方便的網頁瀏覽器控制器.
                                                             (line   34)
* 環境變數; BROWSER <2>:                 webbrowser --- 方便的網頁瀏覽器控制器.
                                                             (line  121)
* 環境變數; CC:                          New Improved and Deprecated Modules<4>.
                                                             (line   58)
* 環境變數; CC <1>:                      編譯器旗標.         (line    6)
* 環境變數; CCSHARED:                    編譯器旗標.         (line   81)
* 環境變數; CFLAGS:                      New Improved and Deprecated Modules<4>.
                                                             (line   59)
* 環境變數; CFLAGS <1>:                  Performance options.
                                                             (line   28)
* 環境變數; CFLAGS <2>:                  編譯器旗標.         (line   18)
* 環境變數; CFLAGS <3>:                  編譯器旗標.         (line   26)
* 環境變數; CFLAGS <4>:                  編譯器旗標.         (line   28)
* 環境變數; CFLAGS <5>:                  編譯器旗標.         (line   32)
* 環境變數; CFLAGS <6>:                  編譯器旗標.         (line   54)
* 環境變數; CFLAGS <7>:                  Linker flags.       (line   18)
* 環境變數; CFLAGS_ALIASING:             編譯器旗標.         (line   74)
* 環境變數; CFLAGS_NODIST:               編譯器旗標.         (line   22)
* 環境變數; CFLAGS_NODIST <1>:           編譯器旗標.         (line   24)
* 環境變數; CFLAGS_NODIST <2>:           編譯器旗標.         (line   61)
* 環境變數; CFLAGS_NODIST <3>:           Linker flags.       (line   26)
* 環境變數; CFLAGSFORSHARED:             編譯器旗標.         (line   87)
* 環境變數; COLUMNS:                     函式<5>.            (line  595)
* 環境變數; COLUMNS <1>:                 函式<5>.            (line  598)
* 環境變數; COMPILEALL_OPTS:             編譯器旗標.         (line   41)
* 環境變數; COMSPEC:                     行程管理.           (line  772)
* 環境變數; COMSPEC <1>:                 Popen Constructor.  (line  112)
* 環境變數; CONFIGURE_CFLAGS:            編譯器旗標.         (line   52)
* 環境變數; CONFIGURE_CFLAGS_NODIST:     編譯器旗標.         (line   59)
* 環境變數; CONFIGURE_CPPFLAGS:          Preprocessor flags. (line    6)
* 環境變數; CONFIGURE_LDFLAGS:           Linker flags.       (line   13)
* 環境變數; CONFIGURE_LDFLAGS_NODIST:    Linker flags.       (line   38)
* 環境變數; CPPFLAGS:                    New Improved and Deprecated Modules<4>.
                                                             (line   59)
* 環境變數; CPPFLAGS <1>:                Preprocessor flags. (line    8)
* 環境變數; CPPFLAGS <2>:                Preprocessor flags. (line   13)
* 環境變數; CPPFLAGS <3>:                Preprocessor flags. (line   18)
* 環境變數; CPPFLAGS <4>:                Linker flags.       (line   50)
* 環境變數; CXX:                         編譯器旗標.         (line   12)
* 環境變數; DISPLAY:                     Tkinter Modules.    (line   27)
* 環境變數; EnableControlFlowGuard:      Build<28>.          (line   47)
* 環境變數; EXTRA_CFLAGS:                編譯器旗標.         (line   48)
* 環境變數; HOME:                        os path<4>.         (line   15)
* 環境變數; HOME <1>:                    Changes in the Python API<3>.
                                                             (line  117)
* 環境變數; HOME <2>:                    Windows<36>.        (line   15)
* 環境變數; HOME <3>:                    Windows<36>.        (line   18)
* 環境變數; HOME <4>:                    os path --- 常見的路徑名操作.
                                                             (line  123)
* 環境變數; HOME <5>:                    os path --- 常見的路徑名操作.
                                                             (line  138)
* 環境變數; HOME <6>:                    Tkinter Modules.    (line   66)
* 環境變數; HOMEDRIVE:                   os path --- 常見的路徑名操作.
                                                             (line  129)
* 環境變數; HOMEPATH:                    os path --- 常見的路徑名操作.
                                                             (line  129)
* 環境變數; IDLESTARTUP:                 IDLE<35>.           (line  176)
* 環境變數; IDLESTARTUP <1>:             IDLE<39>.           (line    9)
* 環境變數; IDLESTARTUP <2>:             IDLE<45>.           (line    9)
* 環境變數; IDLESTARTUP <3>:             Startup and Code Execution.
                                                             (line    7)
* 環境變數; LANG:                        GNU gettext API.    (line   21)
* 環境變數; LANG <1>:                    Class-based API.    (line   26)
* 環境變數; LANG <2>:                    locale --- 國際化服務.
                                                             (line   49)
* 環境變數; LANG <3>:                    locale --- 國際化服務.
                                                             (line  344)
* 環境變數; LANG <4>:                    locale --- 國際化服務.
                                                             (line  348)
* 環境變數; LANGUAGE:                    GNU gettext API.    (line   20)
* 環境變數; LANGUAGE <1>:                Class-based API.    (line   25)
* 環境變數; LC_ALL:                      GNU gettext API.    (line   20)
* 環境變數; LC_ALL <1>:                  Class-based API.    (line   25)
* 環境變數; LC_MESSAGES:                 GNU gettext API.    (line   20)
* 環境變數; LC_MESSAGES <1>:             Class-based API.    (line   26)
* 環境變數; LDCXXSHARED:                 Build and C API Changes<7>.
                                                             (line  153)
* 環境變數; LDFLAGS:                     New Improved and Deprecated Modules<4>.
                                                             (line   59)
* 環境變數; LDFLAGS <1>:                 Preprocessor flags. (line   18)
* 環境變數; LDFLAGS <2>:                 Linker flags.       (line   15)
* 環境變數; LDFLAGS <3>:                 Linker flags.       (line   18)
* 環境變數; LDFLAGS <4>:                 Linker flags.       (line   28)
* 環境變數; LDFLAGS <5>:                 Linker flags.       (line   31)
* 環境變數; LDFLAGS <6>:                 Linker flags.       (line   35)
* 環境變數; LDFLAGS <7>:                 Linker flags.       (line   45)
* 環境變數; LDFLAGS <8>:                 Linker flags.       (line   50)
* 環境變數; LDFLAGS_NODIST:              Linker flags.       (line   24)
* 環境變數; LDFLAGS_NODIST <1>:          Linker flags.       (line   26)
* 環境變數; LDFLAGS_NODIST <2>:          Linker flags.       (line   40)
* 環境變數; LDSHARED:                    Linker flags.       (line   61)
* 環境變數; LIBS:                        Linker flags.       (line   54)
* 環境變數; LINES:                       函式<5>.            (line  125)
* 環境變數; LINES <1>:                   函式<5>.            (line  595)
* 環境變數; LINES <2>:                   函式<5>.            (line  597)
* 環境變數; LINKCC:                      Linker flags.       (line    6)
* 環境變數; LOGNAME:                     行程參數.           (line  239)
* 環境變數; LOGNAME <1>:                 getpass --- 可攜式密碼輸入工具.
                                                             (line   41)
* 環境變數; no_proxy:                    urllib request --- 用來開啟 URLs 的可擴充函式庫.
                                                             (line  273)
* 環境變數; OPT:                         Debug options.      (line   39)
* 環境變數; OPT <1>:                     編譯器旗標.         (line   70)
* 環境變數; PAGER:                       pydoc --- 文件產生器與線上幫助系統.
                                                             (line   46)
* 環境變數; PATH:                        Changes in the Python API<3>.
                                                             (line  144)
* 環境變數; PATH <1>:                    Changes in 'python' Command Behavior<2>.
                                                             (line    6)
* 環境變數; PATH <2>:                    Changes in 'python' Command Behavior<2>.
                                                             (line   11)
* 環境變數; PATH <3>:                    Changes in 'python' Command Behavior<2>.
                                                             (line   12)
* 環境變數; PATH <4>:                    macOS<2>.           (line   14)
* 環境變數; PATH <5>:                    Windows<17>.        (line   56)
* 環境變數; PATH <6>:                    Windows<21>.        (line   14)
* 環境變數; PATH <7>:                    Security<31>.       (line   16)
* 環境變數; PATH <8>:                    Security<31>.       (line   20)
* 環境變數; PATH <9>:                    模組的搜尋路徑.     (line   13)
* 環境變數; PATH <10>:                   可執行的 Python 腳本.
                                                             (line   11)
* 環境變數; PATH <11>:                   環境變數.           (line   27)
* 環境變數; PATH <12>:                   雜項<2>.            (line   15)
* 環境變數; PATH <13>:                   安裝步驟.           (line   33)
* 環境變數; PATH <14>:                   安裝步驟.           (line   56)
* 環境變數; PATH <15>:                   安裝排除使用者介面. (line   76)
* 環境變數; PATH <16>:                   安裝排除使用者介面. (line   80)
* 環境變數; PATH <17>:                   Excursus Setting environment variables.
                                                             (line   23)
* 環境變數; PATH <18>:                   Excursus Setting environment variables.
                                                             (line   35)
* 環境變數; PATH <19>:                   Finding the Python executable.
                                                             (line   14)
* 環境變數; PATH <20>:                   Finding the Python executable.
                                                             (line   21)
* 環境變數; PATH <21>:                   Finding the Python executable.
                                                             (line   22)
* 環境變數; PATH <22>:                   Python Launcher for Windows.
                                                             (line   13)
* 環境變數; PATH <23>:                   From the command-line.
                                                             (line    9)
* 環境變數; PATH <24>:                   Shebang Lines.      (line   53)
* 環境變數; PATH <25>:                   Shebang Lines.      (line   59)
* 環境變數; PATH <26>:                   Shebang Lines.      (line   61)
* 環境變數; PATH <27>:                   Shebang Lines.      (line   66)
* 環境變數; PATH <28>:                   Comparison to the os and os path modules.
                                                             (line   41)
* 環境變數; PATH <29>:                   行程管理.           (line   45)
* 環境變數; PATH <30>:                   行程管理.           (line   86)
* 環境變數; PATH <31>:                   行程管理.           (line   89)
* 環境變數; PATH <32>:                   行程管理.           (line   92)
* 環境變數; PATH <33>:                   行程管理.           (line  540)
* 環境變數; PATH <34>:                   行程管理.           (line  627)
* 環境變數; PATH <35>:                   行程管理.           (line  631)
* 環境變數; PATH <36>:                   行程管理.           (line  633)
* 環境變數; PATH <37>:                   Miscellaneous System Information.
                                                             (line  141)
* 環境變數; PATH <38>:                   Popen Constructor.  (line   34)
* 環境變數; PATH <39>:                   webbrowser --- 方便的網頁瀏覽器控制器.
                                                             (line  239)
* 環境變數; PATH <40>:                   虛擬環境如何運作.   (line   13)
* 環境變數; PATH <41>:                   虛擬環境如何運作.   (line   54)
* 環境變數; PATH <42>:                   虛擬環境如何運作.   (line   58)
* 環境變數; PATH <43>:                   site --- Site-specific configuration hook.
                                                             (line   66)
* 環境變數; PATH <44>:                   嵌入式Python.       (line   22)
* 環境變數; PATH <45>:                   嵌入式Python.       (line   28)
* 環境變數; PATH <46>:                   我如何使 Python script 執行在 Unix？.
                                                             (line   24)
* 環境變數; PATH <47>:                   我如何使 Python script 執行在 Unix？.
                                                             (line   28)
* 環境變數; PATHEXT:                     Other Improvements<2>.
                                                             (line   30)
* 環境變數; PATHEXT <1>:                 Library<35>.        (line  138)
* 環境變數; PATHEXT <2>:                 安裝排除使用者介面. (line   76)
* 環境變數; PATHEXT <3>:                 安裝排除使用者介面. (line   80)
* 環境變數; PIP_USER:                    Windows<38>.        (line  102)
* 環境變數; PROFILE_TASK:                Build<12>.          (line   13)
* 環境變數; PROFILE_TASK <1>:            Performance options.
                                                             (line   12)
* 環境變數; PROFILE_TASK <2>:            Performance options.
                                                             (line   34)
* 環境變數; PURIFY:                      編譯器旗標.         (line  130)
* 環境變數; PY_BUILTIN_MODULE_CFLAGS:    編譯器旗標.         (line  121)
* 環境變數; PY_CFLAGS:                   編譯器旗標.         (line   94)
* 環境變數; PY_CFLAGS_NODIST:            編譯器旗標.         (line   99)
* 環境變數; PY_CORE_CFLAGS:              編譯器旗標.         (line  115)
* 環境變數; PY_CORE_LDFLAGS:             Linker flags.       (line   83)
* 環境變數; PY_CPPFLAGS:                 Preprocessor flags. (line   26)
* 環境變數; PY_LDFLAGS:                  Linker flags.       (line   73)
* 環境變數; PY_LDFLAGS_NODIST:           Linker flags.       (line   77)
* 環境變數; PY_PYTHON:                   Customizing default Python versions.
                                                             (line   18)
* 環境變數; PY_STDMODULE_CFLAGS:         編譯器旗標.         (line  106)
* 環境變數; PYLAUNCHER_ALLOW_INSTALL:    Windows<5>.         (line   24)
* 環境變數; PYLAUNCHER_ALLOW_INSTALL <1>: Windows<19>.       (line   15)
* 環境變數; PYLAUNCHER_ALLOW_INSTALL <2>: 安裝隨選.          (line    6)
* 環境變數; PYLAUNCHER_ALWAYS_INSTALL:   安裝隨選.           (line   12)
* 環境變數; PYLAUNCHER_DEBUG:            Diagnostics.        (line    6)
* 環境變數; PYLAUNCHER_DRYRUN:           Dry Run.            (line    6)
* 環境變數; PYLAUNCHER_DRYRUN <1>:       安裝隨選.           (line   14)
* 環境變數; PYLAUNCHER_NO_SEARCH_PATH:   Shebang Lines.      (line   64)
* 環境變數; PYTHON_BASIC_REPL:           A better interactive interpreter.
                                                             (line   27)
* 環境變數; PYTHON_BASIC_REPL <1>:       Core and Builtins<5>.
                                                             (line   55)
* 環境變數; PYTHON_BASIC_REPL <2>:       互動模式<2>.        (line   23)
* 環境變數; PYTHON_BASIC_REPL <3>:       環境變數.           (line  518)
* 環境變數; PYTHON_COLORS:               Summary -- Release Highlights.
                                                             (line   57)
* 環境變數; PYTHON_COLORS <1>:           Improved error messages.
                                                             (line    8)
* 環境變數; PYTHON_COLORS <2>:           doctest.            (line    7)
* 環境變數; PYTHON_COLORS <3>:           Controlling color.  (line   22)
* 環境變數; PYTHON_COLORS <4>:           環境變數.           (line  510)
* 環境變數; PYTHON_CPU_COUNT:            os.                 (line   11)
* 環境變數; PYTHON_CPU_COUNT <1>:        Miscellaneous options.
                                                             (line  363)
* 環境變數; PYTHON_CPU_COUNT <2>:        環境變數.           (line  486)
* 環境變數; PYTHON_CPU_COUNT <3>:        Miscellaneous System Information.
                                                             (line   48)
* 環境變數; PYTHON_CPU_COUNT <4>:        Miscellaneous System Information.
                                                             (line   69)
* 環境變數; PYTHON_CPU_COUNT <5>:        Miscellaneous<2>.   (line   31)
* 環境變數; PYTHON_CPU_COUNT <6>:        PyConfig.           (line  494)
* 環境變數; PYTHON_DOM:                  模組內容<6>.        (line   23)
* 環境變數; PYTHON_FROZEN_MODULES:       Other Language Changes.
                                                             (line   46)
* 環境變數; PYTHON_FROZEN_MODULES <1>:   Core and Builtins<12>.
                                                             (line  105)
* 環境變數; PYTHON_FROZEN_MODULES <2>:   Miscellaneous options.
                                                             (line  334)
* 環境變數; PYTHON_FROZEN_MODULES <3>:   環境變數.           (line  496)
* 環境變數; PYTHON_GIL:                  Free-threaded CPython.
                                                             (line   22)
* 環境變數; PYTHON_GIL <1>:              Free-threaded CPython.
                                                             (line   38)
* 環境變數; PYTHON_GIL <2>:              Core and Builtins<2>.
                                                             (line   40)
* 環境變數; PYTHON_GIL <3>:              Miscellaneous options.
                                                             (line  381)
* 環境變數; PYTHON_GIL <4>:              環境變數.           (line  535)
* 環境變數; PYTHON_GIL <5>:              術語表.             (line  555)
* 環境變數; PYTHON_HISTORY:              Other Language Changes.
                                                             (line   57)
* 環境變數; PYTHON_HISTORY <1>:          Library<10>.        (line  544)
* 環境變數; PYTHON_HISTORY <2>:          環境變數.           (line  527)
* 環境變數; PYTHON_PERF_JIT_SUPPORT:     Other Language Changes.
                                                             (line   52)
* 環境變數; PYTHON_PERF_JIT_SUPPORT <1>: Miscellaneous options.
                                                             (line  353)
* 環境變數; PYTHON_PERF_JIT_SUPPORT <2>: 環境變數.           (line  473)
* 環境變數; PYTHON_PERF_JIT_SUPPORT <3>: PyConfig.           (line  871)
* 環境變數; PYTHON_PERF_JIT_SUPPORT <4>: PyConfig.           (line  874)
* 環境變數; PYTHON_PERF_JIT_SUPPORT <5>: How to work without frame pointers.
                                                             (line   14)
* 環境變數; PYTHON_PRESITE:              Miscellaneous options.
                                                             (line  375)
* 環境變數; PYTHON_PRESITE <1>:          除錯模式變數.       (line   25)
* 環境變數; PYTHON_PRESITE <2>:          PyConfig.           (line  772)
* 環境變數; PYTHON_PRESITE=package.module: Core and Builtins<12>.
                                                             (line  154)
* 環境變數; PYTHONASYNCIODEBUG:          環境變數.           (line  276)
* 環境變數; PYTHONASYNCIODEBUG <1>:      啟用除錯模式.       (line   10)
* 環境變數; PYTHONASYNCIODEBUG <2>:      除錯模式.           (line   11)
* 環境變數; PYTHONASYNCIODEBUG <3>:      Python 開發模式的影響.
                                                             (line   58)
* 環境變數; PYTHONBREAKPOINT:            PEP 553 Built-in breakpoint.
                                                             (line   13)
* 環境變數; PYTHONBREAKPOINT <1>:        環境變數.           (line   81)
* 環境變數; PYTHONBREAKPOINT <2>:        內建函式.           (line  147)
* 環境變數; PYTHONBREAKPOINT <3>:        sys --- 系統特定的參數與函式.
                                                             (line  252)
* 環境變數; PYTHONBREAKPOINT <4>:        sys --- 系統特定的參數與函式.
                                                             (line  266)
* 環境變數; PYTHONBREAKPOINT <5>:        sys --- 系統特定的參數與函式.
                                                             (line  270)
* 環境變數; PYTHONCASEOK:                Changes in the Python API<2>.
                                                             (line   29)
* 環境變數; PYTHONCASEOK <1>:            PEP 235 Importing Modules on Case-Insensitive Platforms.
                                                             (line   17)
* 環境變數; PYTHONCASEOK <2>:            Library<39>.        (line  144)
* 環境變數; PYTHONCASEOK <3>:            環境變數.           (line  130)
* 環境變數; PYTHONCASEOK <4>:            內建函式.           (line 2047)
* 環境變數; PYTHONCOERCECLOCALE:         PEP 538 Legacy C Locale Coercion.
                                                             (line   13)
* 環境變數; PYTHONCOERCECLOCALE <1>:     環境變數.           (line  364)
* 環境變數; PYTHONCOERCECLOCALE <2>:     一般選項.           (line   87)
* 環境變數; PYTHONCOERCECLOCALE <3>:     Python UTF-8 模式.  (line   57)
* 環境變數; PYTHONCOERCECLOCALE <4>:     Python Configuration.
                                                             (line   15)
* 環境變數; PYTHONDEBUG:                 Miscellaneous options.
                                                             (line   37)
* 環境變數; PYTHONDEBUG <1>:             環境變數.           (line   94)
* 環境變數; PYTHONDEBUG <2>:             Python Debug Build. (line   20)
* 環境變數; PYTHONDEBUG <3>:             Global configuration variables.
                                                             (line   38)
* 環境變數; PYTHONDEBUG <4>:             PyConfig.           (line  664)
* 環境變數; PYTHONDEVMODE:               Python Development Mode -X dev.
                                                             (line    6)
* 環境變數; PYTHONDEVMODE <1>:           Miscellaneous options.
                                                             (line  293)
* 環境變數; PYTHONDEVMODE <2>:           環境變數.           (line  420)
* 環境變數; PYTHONDEVMODE <3>:           Python 開發模式.    (line   11)
* 環境變數; PYTHONDEVMODE <4>:           PyConfig.           (line  293)
* 環境變數; PYTHONDONTWRITEBYTECODE:     Interpreter Changes<2>.
                                                             (line   16)
* 環境變數; PYTHONDONTWRITEBYTECODE <1>: New and Improved Modules<2>.
                                                             (line  625)
* 環境變數; PYTHONDONTWRITEBYTECODE <2>: Miscellaneous options.
                                                             (line   19)
* 環境變數; PYTHONDONTWRITEBYTECODE <3>: 環境變數.           (line  135)
* 環境變數; PYTHONDONTWRITEBYTECODE <4>: sys --- 系統特定的參數與函式.
                                                             (line  335)
* 環境變數; PYTHONDONTWRITEBYTECODE <5>: Global configuration variables.
                                                             (line   51)
* 環境變數; PYTHONDONTWRITEBYTECODE <6>: PyConfig.           (line  948)
* 環境變數; PYTHONDONTWRITEBYTECODE <7>: 如何建立 pyc 檔案？.
                                                             (line   21)
* 環境變數; PYTHONDUMPREFS:              Debug build uses the same ABI as release build.
                                                             (line   15)
* 環境變數; PYTHONDUMPREFS <1>:          Build<45>.          (line   54)
* 環境變數; PYTHONDUMPREFS <2>:          除錯模式變數.       (line    6)
* 環境變數; PYTHONDUMPREFS <3>:          Debug options.      (line   22)
* 環境變數; PYTHONDUMPREFS <4>:          Debug options.      (line   24)
* 環境變數; PYTHONDUMPREFS <5>:          PyConfig.           (line  304)
* 環境變數; PYTHONDUMPREFSFILE:          Core and Builtins<29>.
                                                             (line  154)
* 環境變數; PYTHONDUMPREFSFILE <1>:      除錯模式變數.       (line   14)
* 環境變數; PYTHONEXECUTABLE:            環境變數.           (line  216)
* 環境變數; PYTHONEXECUTABLE <1>:        PyConfig.           (line  699)
* 環境變數; PYTHONFAULTHANDLER:          faulthandler<4>.    (line   11)
* 環境變數; PYTHONFAULTHANDLER <1>:      Miscellaneous options.
                                                             (line  255)
* 環境變數; PYTHONFAULTHANDLER <2>:      環境變數.           (line  244)
* 環境變數; PYTHONFAULTHANDLER <3>:      Python 開發模式的影響.
                                                             (line   52)
* 環境變數; PYTHONFAULTHANDLER <4>:      faulthandler --- 傾印 Python 回溯.
                                                             (line   15)
* 環境變數; PYTHONFAULTHANDLER <5>:      PyConfig.           (line  342)
* 環境變數; PYTHONHASHSEED:              內建函式和型別.     (line   17)
* 環境變數; PYTHONHASHSEED <1>:          移植 Python 程式碼. (line    6)
* 環境變數; PYTHONHASHSEED <2>:          Core and Builtins<56>.
                                                             (line   30)
* 環境變數; PYTHONHASHSEED <3>:          Miscellaneous options.
                                                             (line  118)
* 環境變數; PYTHONHASHSEED <4>:          Miscellaneous options.
                                                             (line  134)
* 環境變數; PYTHONHASHSEED <5>:          環境變數.           (line  150)
* 環境變數; PYTHONHASHSEED <6>:          環境變數.           (line  155)
* 環境變數; PYTHONHASHSEED <7>:          Basic customization.
                                                             (line  303)
* 環境變數; PYTHONHASHSEED <8>:          Global configuration variables.
                                                             (line   76)
* 環境變數; PYTHONHASHSEED <9>:          Global configuration variables.
                                                             (line   79)
* 環境變數; PYTHONHASHSEED <10>:         PyConfig.           (line  412)
* 環境變數; PYTHONHOME:                  Deprecated C APIs.  (line   31)
* 環境變數; PYTHONHOME <1>:              Pending Removal in Python 3 15<2>.
                                                             (line   41)
* 環境變數; PYTHONHOME <2>:              Python 3 15 中待移除的項目<2>.
                                                             (line   40)
* 環境變數; PYTHONHOME <3>:              Summary -- Release highlights<3>.
                                                             (line  107)
* 環境變數; PYTHONHOME <4>:              Miscellaneous options.
                                                             (line   46)
* 環境變數; PYTHONHOME <5>:              環境變數.           (line   11)
* 環境變數; PYTHONHOME <6>:              環境變數.           (line   19)
* 環境變數; PYTHONHOME <7>:              環境變數.           (line   21)
* 環境變數; PYTHONHOME <8>:              環境變數.           (line   38)
* 環境變數; PYTHONHOME <9>:              找尋模組.           (line   29)
* 環境變數; PYTHONHOME <10>:             找尋模組.           (line   47)
* 環境變數; PYTHONHOME <11>:             找尋模組.           (line   81)
* 環境變數; PYTHONHOME <12>:             test support script_helper --- 用於 Python 執行測試的工具.
                                                             (line   24)
* 環境變數; PYTHONHOME <13>:             The initialization of the sys path module search path.
                                                             (line   30)
* 環境變數; PYTHONHOME <14>:             Virtual environments.
                                                             (line   14)
* 環境變數; PYTHONHOME <15>:             嵌入式Python.       (line   29)
* 環境變數; PYTHONHOME <16>:             嵌入式Python.       (line   34)
* 環境變數; PYTHONHOME <17>:             Global configuration variables.
                                                             (line   91)
* 環境變數; PYTHONHOME <18>:             Process-wide parameters.
                                                             (line  292)
* 環境變數; PYTHONHOME <19>:             Process-wide parameters.
                                                             (line  308)
* 環境變數; PYTHONHOME <20>:             Process-wide parameters.
                                                             (line  317)
* 環境變數; PYTHONHOME <21>:             PyConfig.           (line  420)
* 環境變數; PYTHONHOME <22>:             PyConfig.           (line  422)
* 環境變數; PYTHONHOME <23>:             Python 3 15 中待移除的項目<4>.
                                                             (line   40)
* 環境變數; PYTHONINSPECT:               Other Changes and Fixes<2>.
                                                             (line   13)
* 環境變數; PYTHONINSPECT <1>:           Miscellaneous options.
                                                             (line   58)
* 環境變數; PYTHONINSPECT <2>:           環境變數.           (line  103)
* 環境變數; PYTHONINSPECT <3>:           Global configuration variables.
                                                             (line  108)
* 環境變數; PYTHONINSPECT <4>:           PyConfig.           (line  447)
* 環境變數; PYTHONINTMAXSTRDIGITS:       Core and Builtins<21>.
                                                             (line  106)
* 環境變數; PYTHONINTMAXSTRDIGITS <1>:   Miscellaneous options.
                                                             (line  277)
* 環境變數; PYTHONINTMAXSTRDIGITS <2>:   環境變數.           (line  168)
* 環境變數; PYTHONINTMAXSTRDIGITS <3>:   設定限制.           (line    9)
* 環境變數; PYTHONINTMAXSTRDIGITS <4>:   設定限制.           (line   16)
* 環境變數; PYTHONINTMAXSTRDIGITS <5>:   sys --- 系統特定的參數與函式.
                                                             (line 1122)
* 環境變數; PYTHONINTMAXSTRDIGITS <6>:   PyConfig.           (line  478)
* 環境變數; PYTHONIOENCODING:            Other Improvements<2>.
                                                             (line   75)
* 環境變數; PYTHONIOENCODING <1>:        Interpreter Changes<2>.
                                                             (line   23)
* 環境變數; PYTHONIOENCODING <2>:        環境變數.           (line  176)
* 環境變數; PYTHONIOENCODING <3>:        環境變數.           (line  401)
* 環境變數; PYTHONIOENCODING <4>:        Python UTF-8 模式.  (line   29)
* 環境變數; PYTHONIOENCODING <5>:        sys --- 系統特定的參數與函式.
                                                             (line 1799)
* 環境變數; PYTHONIOENCODING <6>:        PyConfig.           (line  832)
* 環境變數; PYTHONLEGACYWINDOWSFSENCODING: New Deprecations. (line  107)
* 環境變數; PYTHONLEGACYWINDOWSFSENCODING <1>: PEP 529 Change Windows filesystem encoding to UTF-8.
                                                             (line   18)
* 環境變數; PYTHONLEGACYWINDOWSFSENCODING <2>: Windows<7>.   (line   37)
* 環境變數; PYTHONLEGACYWINDOWSFSENCODING <3>: 環境變數.     (line  337)
* 環境變數; PYTHONLEGACYWINDOWSFSENCODING <4>: sys --- 系統特定的參數與函式.
                                                             (line 1739)
* 環境變數; PYTHONLEGACYWINDOWSFSENCODING <5>: sys --- 系統特定的參數與函式.
                                                             (line 1750)
* 環境變數; PYTHONLEGACYWINDOWSFSENCODING <6>: sys --- 系統特定的參數與函式.
                                                             (line 1756)
* 環境變數; PYTHONLEGACYWINDOWSFSENCODING <7>: Global configuration variables.
                                                             (line  149)
* 環境變數; PYTHONLEGACYWINDOWSFSENCODING <8>: PyPreConfig.  (line  124)
* 環境變數; PYTHONLEGACYWINDOWSSTDIO:    PEP 528 Change Windows console encoding to UTF-8.
                                                             (line   12)
* 環境變數; PYTHONLEGACYWINDOWSSTDIO <1>: 環境變數.          (line  190)
* 環境變數; PYTHONLEGACYWINDOWSSTDIO <2>: 環境變數.          (line  351)
* 環境變數; PYTHONLEGACYWINDOWSSTDIO <3>: sys --- 系統特定的參數與函式.
                                                             (line 1803)
* 環境變數; PYTHONLEGACYWINDOWSSTDIO <4>: Global configuration variables.
                                                             (line  167)
* 環境變數; PYTHONLEGACYWINDOWSSTDIO <5>: PyConfig.          (line  531)
* 環境變數; PYTHONMALLOC:                PYTHONMALLOC environment variable.
                                                             (line    6)
* 環境變數; PYTHONMALLOC <1>:            C API 中的改動<5>.  (line    9)
* 環境變數; PYTHONMALLOC <2>:            Core and Builtins<76>.
                                                             (line   90)
* 環境變數; PYTHONMALLOC <3>:            環境變數.           (line  283)
* 環境變數; PYTHONMALLOC <4>:            環境變數.           (line  328)
* 環境變數; PYTHONMALLOC <5>:            Performance options.
                                                             (line  108)
* 環境變數; PYTHONMALLOC <6>:            Performance options.
                                                             (line  115)
* 環境變數; PYTHONMALLOC <7>:            Python 開發模式的影響.
                                                             (line   41)
* 環境變數; PYTHONMALLOC <8>:            Python 開發模式的影響.
                                                             (line   44)
* 環境變數; PYTHONMALLOC <9>:            總覽<2>.            (line   75)
* 環境變數; PYTHONMALLOC <10>:           Default Memory Allocators.
                                                             (line   26)
* 環境變數; PYTHONMALLOC <11>:           Debug hooks on the Python memory allocators.
                                                             (line   11)
* 環境變數; PYTHONMALLOC <12>:           The pymalloc allocator.
                                                             (line   27)
* 環境變數; PYTHONMALLOCSTATS:           Core and Builtins<76>.
                                                             (line   96)
* 環境變數; PYTHONMALLOCSTATS <1>:       環境變數.           (line  322)
* 環境變數; PYTHONMALLOCSTATS <2>:       PyConfig.           (line  547)
* 環境變數; PYTHONMALLOCSTATS <3>:       總覽<2>.            (line   78)
* 環境變數; PYTHONNODEBUGRANGES:         PEP 657：回溯 traceback 中更細緻的錯誤位置.
                                                             (line   58)
* 環境變數; PYTHONNODEBUGRANGES <1>:     Miscellaneous options.
                                                             (line  322)
* 環境變數; PYTHONNODEBUGRANGES <2>:     環境變數.           (line  450)
* 環境變數; PYTHONNODEBUGRANGES <3>:     用於程式碼物件的方法.
                                                             (line   40)
* 環境變數; PYTHONNODEBUGRANGES <4>:     PyConfig.           (line  246)
* 環境變數; PYTHONNOUSERSITE:            PEP 370 Per-user site-packages Directory.
                                                             (line   30)
* 環境變數; PYTHONNOUSERSITE <1>:        Miscellaneous options.
                                                             (line  146)
* 環境變數; PYTHONNOUSERSITE <2>:        環境變數.           (line  194)
* 環境變數; PYTHONNOUSERSITE <3>:        模組內容<10>.       (line   15)
* 環境變數; PYTHONNOUSERSITE <4>:        Global configuration variables.
                                                             (line  201)
* 環境變數; PYTHONNOUSERSITE <5>:        PyConfig.           (line  901)
* 環境變數; PYTHONOPTIMIZE:              Miscellaneous options.
                                                             (line   78)
* 環境變數; PYTHONOPTIMIZE <1>:          環境變數.           (line   75)
* 環境變數; PYTHONOPTIMIZE <2>:          Global configuration variables.
                                                             (line  212)
* 環境變數; PYTHONOPTIMIZE <3>:          PyConfig.           (line  614)
* 環境變數; PYTHONPATH:                  Changes in 'python' Command Behavior<2>.
                                                             (line    8)
* 環境變數; PYTHONPATH <1>:              Changes in 'python' Command Behavior<2>.
                                                             (line    9)
* 環境變數; PYTHONPATH <2>:              模組的搜尋路徑.     (line   13)
* 環境變數; PYTHONPATH <3>:              標準模組.           (line   27)
* 環境變數; PYTHONPATH <4>:              標準模組.           (line   27)
* 環境變數; PYTHONPATH <5>:              Miscellaneous options.
                                                             (line   45)
* 環境變數; PYTHONPATH <6>:              環境變數.           (line   24)
* 環境變數; PYTHONPATH <7>:              環境變數.           (line   32)
* 環境變數; PYTHONPATH <8>:              環境變數.           (line   39)
* 環境變數; PYTHONPATH <9>:              環境變數.           (line   42)
* 環境變數; PYTHONPATH <10>:             Excursus Setting environment variables.
                                                             (line   38)
* 環境變數; PYTHONPATH <11>:             找尋模組.           (line   15)
* 環境變數; PYTHONPATH <12>:             找尋模組.           (line   38)
* 環境變數; PYTHONPATH <13>:             找尋模組.           (line   81)
* 環境變數; PYTHONPATH <14>:             設定.               (line    6)
* 環境變數; PYTHONPATH <15>:             Path entry finders. (line   23)
* 環境變數; PYTHONPATH <16>:             test support script_helper --- 用於 Python 執行測試的工具.
                                                             (line   25)
* 環境變數; PYTHONPATH <17>:             sys --- 系統特定的參數與函式.
                                                             (line 1285)
* 環境變數; PYTHONPATH <18>:             sys --- 系統特定的參數與函式.
                                                             (line 1290)
* 環境變數; PYTHONPATH <19>:             The initialization of the sys path module search path.
                                                             (line   14)
* 環境變數; PYTHONPATH <20>:             The initialization of the sys path module search path.
                                                             (line   18)
* 環境變數; PYTHONPATH <21>:             建立 C 與 C++ 擴充套件.
                                                             (line    9)
* 環境變數; PYTHONPATH <22>:             嵌入式Python.       (line   30)
* 環境變數; PYTHONPATH <23>:             嵌入式Python.       (line   35)
* 環境變數; PYTHONPATH <24>:             Global configuration variables.
                                                             (line   90)
* 環境變數; PYTHONPATH <25>:             PyConfig.           (line  580)
* 環境變數; PYTHONPERFSUPPORT:           其他語言更動.       (line   85)
* 環境變數; PYTHONPERFSUPPORT <1>:       Miscellaneous options.
                                                             (line  342)
* 環境變數; PYTHONPERFSUPPORT <2>:       環境變數.           (line  461)
* 環境變數; PYTHONPERFSUPPORT <3>:       如何啟用 perf 分析支援.
                                                             (line    6)
* 環境變數; PYTHONPLATLIBDIR:            Core and Builtins<37>.
                                                             (line  274)
* 環境變數; PYTHONPLATLIBDIR <1>:        環境變數.           (line   54)
* 環境變數; PYTHONPLATLIBDIR <2>:        The initialization of the sys path module search path.
                                                             (line   51)
* 環境變數; PYTHONPLATLIBDIR <3>:        PyConfig.           (line  559)
* 環境變數; PYTHONPROFILEIMPORTTIME:     其他語言更動<6>.    (line   47)
* 環境變數; PYTHONPROFILEIMPORTTIME <1>: Core and Builtins<58>.
                                                             (line   66)
* 環境變數; PYTHONPROFILEIMPORTTIME <2>: Miscellaneous options.
                                                             (line  286)
* 環境變數; PYTHONPROFILEIMPORTTIME <3>: 環境變數.           (line  268)
* 環境變數; PYTHONPROFILEIMPORTTIME <4>: PyConfig.           (line  432)
* 環境變數; PYTHONPYCACHEPREFIX:         Parallel filesystem cache for compiled bytecode files.
                                                             (line    6)
* 環境變數; PYTHONPYCACHEPREFIX <1>:     Core and Builtins<49>.
                                                             (line  402)
* 環境變數; PYTHONPYCACHEPREFIX <2>:     Miscellaneous options.
                                                             (line  306)
* 環境變數; PYTHONPYCACHEPREFIX <3>:     環境變數.           (line  141)
* 環境變數; PYTHONPYCACHEPREFIX <4>:     sys --- 系統特定的參數與函式.
                                                             (line  381)
* 環境變數; PYTHONPYCACHEPREFIX <5>:     PyConfig.           (line  721)
* 環境變數; PYTHONREGRTEST_UNICODE_GUARD: Tests<19>.         (line   13)
* 環境變數; PYTHONSAFEPATH:              發布重點摘要<2>.    (line   27)
* 環境變數; PYTHONSAFEPATH <1>:          其他語言更動<2>.    (line   35)
* 環境變數; PYTHONSAFEPATH <2>:          Security<15>.       (line    6)
* 環境變數; PYTHONSAFEPATH <3>:          Miscellaneous options.
                                                             (line  104)
* 環境變數; PYTHONSAFEPATH <4>:          環境變數.           (line   46)
* 環境變數; PYTHONSAFEPATH <5>:          sys --- 系統特定的參數與函式.
                                                             (line 1302)
* 環境變數; PYTHONSAFEPATH <6>:          安全性注意事項<4>.  (line   41)
* 環境變數; PYTHONSAFEPATH <7>:          PyConfig.           (line  163)
* 環境變數; PYTHONSTARTUP:               sys<11>.            (line   17)
* 環境變數; PYTHONSTARTUP <1>:           sys<11>.            (line   21)
* 環境變數; PYTHONSTARTUP <2>:           IDLE<35>.           (line  176)
* 環境變數; PYTHONSTARTUP <3>:           IDLE<39>.           (line    9)
* 環境變數; PYTHONSTARTUP <4>:           IDLE<45>.           (line    9)
* 環境變數; PYTHONSTARTUP <5>:           互動式啟動檔案.     (line    7)
* 環境變數; PYTHONSTARTUP <6>:           Miscellaneous options.
                                                             (line   55)
* 環境變數; PYTHONSTARTUP <7>:           環境變數.           (line   61)
* 環境變數; PYTHONSTARTUP <8>:           環境變數.           (line  116)
* 環境變數; PYTHONSTARTUP <9>:           範例.               (line   10)
* 環境變數; PYTHONSTARTUP <10>:          asyncio --- 非同步 I/O.
                                                             (line   77)
* 環境變數; PYTHONSTARTUP <11>:          Startup and Code Execution.
                                                             (line    7)
* 環境變數; PYTHONSTARTUP <12>:          sys --- 系統特定的參數與函式.
                                                             (line 1135)
* 環境變數; PYTHONSTARTUP <13>:          Readline configuration.
                                                             (line   12)
* 環境變數; PYTHONTRACEMALLOC:           Miscellaneous options.
                                                             (line  272)
* 環境變數; PYTHONTRACEMALLOC <1>:       環境變數.           (line  255)
* 環境變數; PYTHONTRACEMALLOC <2>:       tracemalloc --- 追蹤記憶體配置.
                                                             (line   25)
* 環境變數; PYTHONTRACEMALLOC <3>:       tracemalloc --- 追蹤記憶體配置.
                                                             (line   32)
* 環境變數; PYTHONTRACEMALLOC <4>:       函式<10>.           (line   90)
* 環境變數; PYTHONTRACEMALLOC <5>:       PyConfig.           (line  860)
* 環境變數; PYTHONTZPATH:                Environment configuration.
                                                             (line   11)
* 環境變數; PYTHONTZPATH <1>:            Exceptions and warnings.
                                                             (line   14)
* 環境變數; PYTHONUNBUFFERED:            Core and Builtins<42>.
                                                             (line  107)
* 環境變數; PYTHONUNBUFFERED <1>:        Miscellaneous options.
                                                             (line  166)
* 環境變數; PYTHONUNBUFFERED <2>:        環境變數.           (line  119)
* 環境變數; PYTHONUNBUFFERED <3>:        sys --- 系統特定的參數與函式.
                                                             (line 1810)
* 環境變數; PYTHONUNBUFFERED <4>:        Global configuration variables.
                                                             (line  239)
* 環境變數; PYTHONUNBUFFERED <5>:        PyConfig.           (line  210)
* 環境變數; PYTHONUOPS:                  Core and Builtins<13>.
                                                             (line   27)
* 環境變數; PYTHONUOPS <1>:              Core and Builtins<13>.
                                                             (line  179)
* 環境變數; PYTHONUOPS <2>:              Core and Builtins<13>.
                                                             (line  258)
* 環境變數; PYTHONUOPS <3>:              Core and Builtins<13>.
                                                             (line  317)
* 環境變數; PYTHONUOPS <4>:              Core and Builtins<13>.
                                                             (line  382)
* 環境變數; PYTHONUSERBASE:              PEP 370 Per-user site-packages Directory.
                                                             (line   23)
* 環境變數; PYTHONUSERBASE <1>:          環境變數.           (line  204)
* 環境變數; PYTHONUSERBASE <2>:          模組內容<10>.       (line   40)
* 環境變數; PYTHONUSERBASE <3>:          模組內容<10>.       (line   67)
* 環境變數; PYTHONUSERSITE:              test support script_helper --- 用於 Python 執行測試的工具.
                                                             (line   25)
* 環境變數; PYTHONUTF8:                  PEP 540 Forced UTF-8 Runtime Mode.
                                                             (line    6)
* 環境變數; PYTHONUTF8 <1>:              Miscellaneous options.
                                                             (line  300)
* 環境變數; PYTHONUTF8 <2>:              環境變數.           (line  411)
* 環境變數; PYTHONUTF8 <3>:              環境變數.           (line  429)
* 環境變數; PYTHONUTF8 <4>:              UTF-8 模式.         (line   18)
* 環境變數; PYTHONUTF8 <5>:              Python UTF-8 模式.  (line   52)
* 環境變數; PYTHONUTF8 <6>:              Python UTF-8 模式.  (line   54)
* 環境變數; PYTHONUTF8 <7>:              sys --- 系統特定的參數與函式.
                                                             (line 1801)
* 環境變數; PYTHONUTF8 <8>:              PyPreConfig.        (line  153)
* 環境變數; PYTHONUTF8 <9>:              Python Configuration.
                                                             (line   14)
* 環境變數; PYTHONVERBOSE:               Miscellaneous options.
                                                             (line  182)
* 環境變數; PYTHONVERBOSE <1>:           環境變數.           (line  124)
* 環境變數; PYTHONVERBOSE <2>:           Global configuration variables.
                                                             (line  256)
* 環境變數; PYTHONVERBOSE <3>:           PyConfig.           (line  918)
* 環境變數; PYTHONWARNDEFAULTENCODING:   可選的 EncodingWarning 和 encoding="locale" 選項.
                                                             (line   18)
* 環境變數; PYTHONWARNDEFAULTENCODING <1>: Library<30>.      (line   45)
* 環境變數; PYTHONWARNDEFAULTENCODING <2>: Miscellaneous options.
                                                             (line  312)
* 環境變數; PYTHONWARNDEFAULTENCODING <3>: 環境變數.         (line  440)
* 環境變數; PYTHONWARNDEFAULTENCODING <4>: 選擇性加入的編碼警告.
                                                             (line    9)
* 環境變數; PYTHONWARNINGS:              warnings<3>.        (line   21)
* 環境變數; PYTHONWARNINGS <1>:          其他語言更動<11>.   (line  160)
* 環境變數; PYTHONWARNINGS <2>:          Changes to the Handling of Deprecation Warnings.
                                                             (line   25)
* 環境變數; PYTHONWARNINGS <3>:          Interpreter Changes.
                                                             (line    6)
* 環境變數; PYTHONWARNINGS <4>:          Documentation<15>.  (line   67)
* 環境變數; PYTHONWARNINGS <5>:          Miscellaneous options.
                                                             (line  236)
* 環境變數; PYTHONWARNINGS <6>:          環境變數.           (line  222)
* 環境變數; PYTHONWARNINGS <7>:          Python 開發模式的影響.
                                                             (line   26)
* 環境變數; PYTHONWARNINGS <8>:          The Warnings Filter.
                                                             (line   46)
* 環境變數; PYTHONWARNINGS <9>:          The Warnings Filter.
                                                             (line   56)
* 環境變數; PYTHONWARNINGS <10>:         Describing Warning Filters.
                                                             (line    7)
* 環境變數; PYTHONWARNINGS <11>:         Describing Warning Filters.
                                                             (line   21)
* 環境變數; PYTHONWARNINGS <12>:         Default Warning Filter.
                                                             (line    7)
* 環境變數; PYTHONWARNINGS <13>:         PyConfig.           (line  937)
* 環境變數; SOURCE_DATE_EPOCH:           py_compile<3>.      (line    7)
* 環境變數; SOURCE_DATE_EPOCH <1>:       Library<48>.        (line  452)
* 環境變數; SOURCE_DATE_EPOCH <2>:       Build<53>.          (line   15)
* 環境變數; SOURCE_DATE_EPOCH <3>:       py_compile — 編譯 Python 來源檔案.
                                                             (line   66)
* 環境變數; SOURCE_DATE_EPOCH <4>:       py_compile — 編譯 Python 來源檔案.
                                                             (line   82)
* 環境變數; SOURCE_DATE_EPOCH <5>:       py_compile — 編譯 Python 來源檔案.
                                                             (line   86)
* 環境變數; SOURCE_DATE_EPOCH <6>:       Command-line use.   (line   90)
* 環境變數; SSLKEYLOGFILE:               語境建立.           (line   27)
* 環境變數; SSLKEYLOGFILE <1>:           語境建立.           (line   71)
* 環境變數; SystemRoot:                  Popen Constructor.  (line  307)
* 環境變數; TEMP:                        Redirection of local data registry and temporary paths.
                                                             (line    7)
* 環境變數; TEMP <1>:                    tempfile --- 生成臨時檔案和目錄.
                                                             (line  279)
* 環境變數; TERM:                        函式<5>.            (line  485)
* 環境變數; TERM <1>:                    函式<5>.            (line  512)
* 環境變數; TMP:                         tempfile --- 生成臨時檔案和目錄.
                                                             (line  281)
* 環境變數; TMPDIR:                      Tests<18>.          (line   68)
* 環境變數; TMPDIR <1>:                  tempfile --- 生成臨時檔案和目錄.
                                                             (line  277)
* 環境變數; TZ:                          函式<4>.            (line  542)
* 環境變數; TZ <1>:                      函式<4>.            (line  543)
* 環境變數; TZ <2>:                      函式<4>.            (line  551)
* 環境變數; TZ <3>:                      函式<4>.            (line  556)
* 環境變數; TZ <4>:                      函式<4>.            (line  558)
* 環境變數; TZ <5>:                      函式<4>.            (line  619)
* 環境變數; USER:                        getpass --- 可攜式密碼輸入工具.
                                                             (line   41)
* 環境變數; USERNAME:                    os path --- 常見的路徑名操作.
                                                             (line  130)
* 環境變數; USERNAME <1>:                行程參數.           (line  239)
* 環境變數; USERNAME <2>:                getpass --- 可攜式密碼輸入工具.
                                                             (line   42)
* 環境變數; USERPROFILE:                 os path<4>.         (line   14)
* 環境變數; USERPROFILE <1>:             Changes in the Python API<3>.
                                                             (line  116)
* 環境變數; USERPROFILE <2>:             Windows<36>.        (line   15)
* 環境變數; USERPROFILE <3>:             os path --- 常見的路徑名操作.
                                                             (line  128)
* 紀元秒數:                              time --- 時間存取與轉換.
                                                             (line   20)

                       



Tag Table:
Node: Top355
Ref: contents doc573
Ref: 11b573
Node: Python 有什麼新功能？223657
Ref: whatsnew/index doc223759
Ref: 11c223759
Ref: whatsnew/index python-documentation-contents223759
Ref: 11d223759
Ref: whatsnew/index what-s-new-in-python223759
Ref: 11e223759
Ref: whatsnew/index whatsnew-index223759
Ref: 11f223759
Node: What's New In Python 3 13225534
Ref: whatsnew/3 13 doc225663
Ref: 120225663
Ref: whatsnew/3 13 what-s-new-in-python-3-13225663
Ref: 121225663
Ref: What's New In Python 3 13-Footnote-1226627
Node: Summary -- Release Highlights226669
Ref: whatsnew/3 13 summary-release-highlights226781
Ref: 123226781
Ref: whatsnew/3 13 whatsnew313-better-interactive-interpreter227088
Ref: 124227088
Ref: whatsnew/3 13 whatsnew313-free-threaded-cpython227158
Ref: 125227158
Ref: whatsnew/3 13 whatsnew313-jit-compiler227212
Ref: 126227212
Ref: whatsnew/3 13 whatsnew313-pep594227686
Ref: 129227686
Ref: Summary -- Release Highlights-Footnote-1233367
Ref: Summary -- Release Highlights-Footnote-2233409
Ref: Summary -- Release Highlights-Footnote-3233451
Ref: Summary -- Release Highlights-Footnote-4233493
Ref: Summary -- Release Highlights-Footnote-5233535
Ref: Summary -- Release Highlights-Footnote-6233577
Ref: Summary -- Release Highlights-Footnote-7233619
Ref: Summary -- Release Highlights-Footnote-8233649
Ref: Summary -- Release Highlights-Footnote-9233689
Ref: Summary -- Release Highlights-Footnote-10233731
Ref: Summary -- Release Highlights-Footnote-11233774
Ref: Summary -- Release Highlights-Footnote-12233817
Ref: Summary -- Release Highlights-Footnote-13233860
Ref: Summary -- Release Highlights-Footnote-14233903
Ref: Summary -- Release Highlights-Footnote-15233953
Ref: Summary -- Release Highlights-Footnote-16233996
Ref: Summary -- Release Highlights-Footnote-17234046
Node: New Features234089
Ref: whatsnew/3 13 new-features234232
Ref: 14b234232
Node: A better interactive interpreter234612
Ref: whatsnew/3 13 a-better-interactive-interpreter234725
Ref: 14c234725
Ref: A better interactive interpreter-Footnote-1236035
Ref: A better interactive interpreter-Footnote-2236061
Node: Improved error messages236117
Ref: whatsnew/3 13 improved-error-messages236260
Ref: 154236260
Ref: whatsnew/3 13 whatsnew313-improved-error-messages236260
Ref: 12d236260
Ref: Improved error messages-Footnote-1238705
Ref: Improved error messages-Footnote-2238735
Ref: Improved error messages-Footnote-3238768
Ref: Improved error messages-Footnote-4238824
Ref: Improved error messages-Footnote-5238879
Node: Free-threaded CPython238935
Ref: whatsnew/3 13 free-threaded-cpython239087
Ref: 155239087
Ref: Free-threaded CPython-Footnote-1241555
Ref: Free-threaded CPython-Footnote-2241597
Node: An experimental just-in-time JIT compiler241650
Ref: whatsnew/3 13 an-experimental-just-in-time-jit-compiler241816
Ref: 15e241816
Ref: An experimental just-in-time JIT compiler-Footnote-1244420
Ref: An experimental just-in-time JIT compiler-Footnote-2244492
Node: Defined mutation semantics for locals244534
Ref: whatsnew/3 13 defined-mutation-semantics-for-locals244707
Ref: 160244707
Ref: whatsnew/3 13 whatsnew313-locals-semantics244707
Ref: 128244707
Ref: Defined mutation semantics for locals-Footnote-1247320
Ref: Defined mutation semantics for locals-Footnote-2247362
Ref: Defined mutation semantics for locals-Footnote-3247404
Node: Support for mobile platforms247459
Ref: whatsnew/3 13 support-for-mobile-platforms247621
Ref: 168247621
Ref: whatsnew/3 13 whatsnew313-platform-support247621
Ref: 149247621
Ref: Support for mobile platforms-Footnote-1248481
Ref: Support for mobile platforms-Footnote-2248523
Ref: Support for mobile platforms-Footnote-3248565
Ref: Support for mobile platforms-Footnote-4248621
Ref: Support for mobile platforms-Footnote-5248663
Ref: Support for mobile platforms-Footnote-6248719
Ref: Support for mobile platforms-Footnote-7248761
Node: Incremental garbage collection248803
Ref: whatsnew/3 13 incremental-garbage-collection248919
Ref: 169248919
Ref: whatsnew/3 13 whatsnew313-incremental-gc248919
Ref: 16a248919
Ref: Incremental garbage collection-Footnote-1249724
Node: Other Language Changes249780
Ref: whatsnew/3 13 other-language-changes249905
Ref: 16c249905
Ref: Other Language Changes-Footnote-1254735
Ref: Other Language Changes-Footnote-2254790
Ref: Other Language Changes-Footnote-3254846
Ref: Other Language Changes-Footnote-4254902
Ref: Other Language Changes-Footnote-5254958
Ref: Other Language Changes-Footnote-6255014
Ref: Other Language Changes-Footnote-7255070
Ref: Other Language Changes-Footnote-8255119
Ref: Other Language Changes-Footnote-9255175
Ref: Other Language Changes-Footnote-10255230
Ref: Other Language Changes-Footnote-11255287
Ref: Other Language Changes-Footnote-12255344
Ref: Other Language Changes-Footnote-13255401
Ref: Other Language Changes-Footnote-14255458
Ref: Other Language Changes-Footnote-15255515
Ref: Other Language Changes-Footnote-16255572
Ref: Other Language Changes-Footnote-17255628
Ref: Other Language Changes-Footnote-18255685
Node: New Modules255742
Ref: whatsnew/3 13 new-modules255871
Ref: 181255871
Ref: New Modules-Footnote-1256095
Node: Improved Modules256151
Ref: whatsnew/3 13 improved-modules256271
Ref: 182256271
Node: argparse256961
Ref: whatsnew/3 13 argparse257036
Ref: 183257036
Ref: argparse-Footnote-1257359
Node: array257414
Ref: whatsnew/3 13 array257501
Ref: 185257501
Ref: array-Footnote-1257937
Ref: array-Footnote-2257992
Node: ast258048
Ref: whatsnew/3 13 ast258134
Ref: 189258134
Ref: ast-Footnote-1259695
Ref: ast-Footnote-2259751
Ref: ast-Footnote-3259807
Ref: ast-Footnote-4259863
Node: asyncio259919
Ref: whatsnew/3 13 asyncio260006
Ref: 18f260006
Ref: asyncio-Footnote-1262912
Ref: asyncio-Footnote-2262967
Ref: asyncio-Footnote-3263023
Ref: asyncio-Footnote-4263079
Ref: asyncio-Footnote-5263135
Ref: asyncio-Footnote-6263191
Ref: asyncio-Footnote-7263246
Ref: asyncio-Footnote-8263302
Node: base64263358
Ref: whatsnew/3 13 base64263452
Ref: 1a4263452
Ref: base64-Footnote-1263747
Ref: base64-Footnote-2263787
Node: compileall263842
Ref: whatsnew/3 13 compileall263941
Ref: 1a6263941
Ref: compileall-Footnote-1264233
Node: configparser264289
Ref: whatsnew/3 13 configparser264400
Ref: 1a9264400
Ref: configparser-Footnote-1264662
Node: concurrent futures264717
Ref: whatsnew/3 13 concurrent-futures264833
Ref: 1ab264833
Ref: concurrent futures-Footnote-1265141
Node: configparser<2>265197
Ref: whatsnew/3 13 id2265305
Ref: 1ac265305
Ref: configparser<2>-Footnote-1265635
Node: copy265690
Ref: whatsnew/3 13 copy265783
Ref: 1ad265783
Ref: copy-Footnote-1266702
Node: dbm266758
Ref: whatsnew/3 13 dbm266839
Ref: 1b7266839
Ref: dbm-Footnote-1267295
Ref: dbm-Footnote-2267351
Node: dis267407
Ref: whatsnew/3 13 dis267491
Ref: 1ba267491
Ref: dis-Footnote-1268245
Ref: dis-Footnote-2268301
Node: doctest268357
Ref: whatsnew/3 13 doctest268443
Ref: 1be268443
Ref: whatsnew/3 13 whatsnew313-doctest268443
Ref: 12f268443
Ref: doctest-Footnote-1269090
Ref: doctest-Footnote-2269120
Ref: doctest-Footnote-3269153
Ref: doctest-Footnote-4269209
Node: email269265
Ref: whatsnew/3 13 email269357
Ref: 1c2269357
Ref: email-Footnote-1270490
Ref: email-Footnote-2270546
Ref: email-Footnote-3270602
Node: fractions270672
Ref: whatsnew/3 13 fractions270759
Ref: 1c6270759
Ref: fractions-Footnote-1271077
Node: gc271133
Ref: whatsnew/3 13 gc271219
Ref: 1c9271219
Node: glob272461
Ref: whatsnew/3 13 glob272547
Ref: 1ce272547
Ref: glob-Footnote-1272796
Node: importlib272851
Ref: whatsnew/3 13 importlib272937
Ref: 1d0272937
Ref: importlib-Footnote-1273838
Ref: importlib-Footnote-2273894
Node: io273950
Ref: whatsnew/3 13 io274041
Ref: 1d9274041
Ref: io-Footnote-1274467
Node: ipaddress274522
Ref: whatsnew/3 13 ipaddress274613
Ref: 1df274613
Ref: ipaddress-Footnote-1275072
Ref: ipaddress-Footnote-2275128
Node: itertools275184
Ref: whatsnew/3 13 itertools275280
Ref: 1e5275280
Ref: itertools-Footnote-1275580
Node: marshal275636
Ref: whatsnew/3 13 marshal275727
Ref: 1e8275727
Ref: marshal-Footnote-1276062
Node: math276118
Ref: whatsnew/3 13 math276209
Ref: 1e9276209
Ref: math-Footnote-1276700
Node: mimetypes276755
Ref: whatsnew/3 13 mimetypes276843
Ref: 1eb276843
Ref: mimetypes-Footnote-1277160
Node: mmap277215
Ref: whatsnew/3 13 mmap277314
Ref: 1ef277314
Ref: mmap-Footnote-1278127
Ref: mmap-Footnote-2278183
Ref: mmap-Footnote-3278239
Node: multiprocessing278294
Ref: whatsnew/3 13 multiprocessing278386
Ref: 1f3278386
Ref: multiprocessing-Footnote-1278690
Node: os278746
Ref: whatsnew/3 13 os278841
Ref: 1f4278841
Ref: os-Footnote-1281307
Ref: os-Footnote-2281363
Ref: os-Footnote-3281419
Ref: os-Footnote-4281473
Ref: os-Footnote-5281529
Ref: os-Footnote-6281584
Ref: os-Footnote-7281640
Ref: os-Footnote-8281709
Ref: os-Footnote-9281765
Ref: os-Footnote-10281821
Node: os path281878
Ref: whatsnew/3 13 os-path281965
Ref: 207281965
Ref: os path-Footnote-1282588
Ref: os path-Footnote-2282643
Ref: os path-Footnote-3282698
Node: pathlib282753
Ref: whatsnew/3 13 pathlib282841
Ref: 20b282841
Ref: pathlib-Footnote-1284355
Ref: pathlib-Footnote-2284410
Ref: pathlib-Footnote-3284466
Ref: pathlib-Footnote-4284521
Ref: pathlib-Footnote-5284576
Ref: pathlib-Footnote-6284631
Ref: pathlib-Footnote-7284687
Node: pdb284743
Ref: whatsnew/3 13 pdb284829
Ref: 218284829
Ref: pdb-Footnote-1285964
Ref: pdb-Footnote-2286020
Ref: pdb-Footnote-3286076
Ref: pdb-Footnote-4286132
Ref: pdb-Footnote-5286188
Node: queue286244
Ref: whatsnew/3 13 queue286329
Ref: 21e286329
Ref: queue-Footnote-1286564
Node: random286620
Ref: whatsnew/3 13 random286704
Ref: 221286704
Ref: random-Footnote-1286878
Node: re286934
Ref: whatsnew/3 13 re287019
Ref: 222287019
Node: shutil287178
Ref: whatsnew/3 13 shutil287261
Ref: 224287261
Ref: shutil-Footnote-1287489
Node: site287544
Ref: whatsnew/3 13 site287632
Ref: 226287632
Ref: site-Footnote-1287883
Node: sqlite3287939
Ref: whatsnew/3 13 sqlite3288024
Ref: 228288024
Ref: sqlite3-Footnote-1288465
Ref: sqlite3-Footnote-2288521
Node: ssl288576
Ref: whatsnew/3 13 ssl288667
Ref: 22d288667
Ref: ssl-Footnote-1289358
Ref: ssl-Footnote-2289417
Node: statistics289473
Ref: whatsnew/3 13 statistics289567
Ref: 22e289567
Ref: statistics-Footnote-1290076
Ref: statistics-Footnote-2290132
Node: subprocess290188
Ref: whatsnew/3 13 subprocess290282
Ref: 231290282
Ref: whatsnew/3 13 whatsnew313-subprocess290282
Ref: 232290282
Ref: subprocess-Footnote-1291222
Node: sys291278
Ref: whatsnew/3 13 sys291370
Ref: 234291370
Ref: sys-Footnote-1291659
Node: tempfile291714
Ref: whatsnew/3 13 tempfile291800
Ref: 236291800
Ref: tempfile-Footnote-1292145
Ref: tempfile-Footnote-2292214
Node: time292270
Ref: whatsnew/3 13 time292360
Ref: 237292360
Ref: time-Footnote-1293008
Ref: time-Footnote-2293063
Node: tkinter293118
Ref: whatsnew/3 13 tkinter293209
Ref: 23a293209
Ref: tkinter-Footnote-1295473
Ref: tkinter-Footnote-2295528
Ref: tkinter-Footnote-3295583
Ref: tkinter-Footnote-4295638
Ref: tkinter-Footnote-5295693
Ref: tkinter-Footnote-6295748
Ref: tkinter-Footnote-7295803
Ref: tkinter-Footnote-8295859
Ref: tkinter-Footnote-9295915
Node: traceback295971
Ref: whatsnew/3 13 traceback296063
Ref: 23f296063
Ref: traceback-Footnote-1296793
Ref: traceback-Footnote-2296849
Node: types296905
Ref: whatsnew/3 13 types296996
Ref: 245296996
Ref: types-Footnote-1297321
Node: typing297377
Ref: whatsnew/3 13 typing297470
Ref: 246297470
Ref: typing-Footnote-1298455
Ref: typing-Footnote-2298497
Ref: typing-Footnote-3298539
Ref: typing-Footnote-4298595
Ref: typing-Footnote-5298651
Ref: typing-Footnote-6298707
Node: unicodedata298762
Ref: whatsnew/3 13 unicodedata298854
Ref: 24d298854
Ref: unicodedata-Footnote-1299042
Ref: unicodedata-Footnote-2299098
Node: venv299154
Ref: whatsnew/3 13 venv299248
Ref: 24e299248
Ref: venv-Footnote-1299740
Node: warnings299796
Ref: whatsnew/3 13 warnings299882
Ref: 251299882
Ref: warnings-Footnote-1300346
Ref: warnings-Footnote-2300388
Node: xml300444
Ref: whatsnew/3 13 xml300535
Ref: 253300535
Ref: xml-Footnote-1301300
Ref: xml-Footnote-2301370
Ref: xml-Footnote-3301426
Node: zipimport301481
Ref: whatsnew/3 13 zipimport301555
Ref: 259301555
Ref: zipimport-Footnote-1301759
Ref: zipimport-Footnote-2301821
Node: Optimizations301876
Ref: whatsnew/3 13 optimizations302009
Ref: 25a302009
Ref: Optimizations-Footnote-1303423
Ref: Optimizations-Footnote-2303479
Ref: Optimizations-Footnote-3303535
Ref: Optimizations-Footnote-4303591
Node: Removed Modules And APIs303647
Ref: whatsnew/3 13 removed-modules-and-apis303780
Ref: 25c303780
Node: PEP 594 Remove "dead batteries" from the standard library304228
Ref: whatsnew/3 13 pep-594-remove-dead-batteries-from-the-standard-library304359
Ref: 25d304359
Ref: PEP 594 Remove "dead batteries" from the standard library-Footnote-1308145
Ref: PEP 594 Remove "dead batteries" from the standard library-Footnote-2308187
Ref: PEP 594 Remove "dead batteries" from the standard library-Footnote-3308231
Ref: PEP 594 Remove "dead batteries" from the standard library-Footnote-4308275
Ref: PEP 594 Remove "dead batteries" from the standard library-Footnote-5308316
Ref: PEP 594 Remove "dead batteries" from the standard library-Footnote-6308358
Ref: PEP 594 Remove "dead batteries" from the standard library-Footnote-7308404
Ref: PEP 594 Remove "dead batteries" from the standard library-Footnote-8308450
Ref: PEP 594 Remove "dead batteries" from the standard library-Footnote-9308492
Ref: PEP 594 Remove "dead batteries" from the standard library-Footnote-10308539
Ref: PEP 594 Remove "dead batteries" from the standard library-Footnote-11308583
Ref: PEP 594 Remove "dead batteries" from the standard library-Footnote-12308628
Ref: PEP 594 Remove "dead batteries" from the standard library-Footnote-13308676
Ref: PEP 594 Remove "dead batteries" from the standard library-Footnote-14308719
Ref: PEP 594 Remove "dead batteries" from the standard library-Footnote-15308761
Ref: PEP 594 Remove "dead batteries" from the standard library-Footnote-16308805
Ref: PEP 594 Remove "dead batteries" from the standard library-Footnote-17308850
Ref: PEP 594 Remove "dead batteries" from the standard library-Footnote-18308898
Ref: PEP 594 Remove "dead batteries" from the standard library-Footnote-19308944
Ref: PEP 594 Remove "dead batteries" from the standard library-Footnote-20308990
Ref: PEP 594 Remove "dead batteries" from the standard library-Footnote-21309034
Ref: PEP 594 Remove "dead batteries" from the standard library-Footnote-22309091
Node: 2to3309148
Ref: whatsnew/3 13 to3309296
Ref: 262309296
Ref: 2to3-Footnote-1309523
Node: builtins309579
Ref: whatsnew/3 13 builtins309685
Ref: 263309685
Ref: builtins-Footnote-1310216
Ref: builtins-Footnote-2310271
Node: configparser<3>310326
Ref: whatsnew/3 13 id4310446
Ref: 264310446
Ref: configparser<3>-Footnote-1310730
Node: importlib metadata310786
Ref: whatsnew/3 13 importlib-metadata310904
Ref: 265310904
Ref: importlib metadata-Footnote-1311161
Node: locale311217
Ref: whatsnew/3 13 locale311326
Ref: 268311326
Ref: locale-Footnote-1311589
Node: opcode311645
Ref: whatsnew/3 13 opcode311746
Ref: 269311746
Ref: opcode-Footnote-1312371
Ref: opcode-Footnote-2312427
Node: pathlib<2>312483
Ref: whatsnew/3 13 id5312583
Ref: 26a312583
Ref: pathlib<2>-Footnote-1312861
Node: re<2>312916
Ref: whatsnew/3 13 id6313021
Ref: 26b313021
Ref: re<2>-Footnote-1313285
Node: tkinter tix313341
Ref: whatsnew/3 13 tkinter-tix313442
Ref: 26c313442
Ref: tkinter tix-Footnote-1313717
Node: turtle313772
Ref: whatsnew/3 13 turtle313877
Ref: 26d313877
Ref: turtle-Footnote-1314147
Node: typing<2>314203
Ref: whatsnew/3 13 id7314305
Ref: 26e314305
Ref: typing<2>-Footnote-1314790
Ref: typing<2>-Footnote-2314845
Node: unittest314901
Ref: whatsnew/3 13 unittest315003
Ref: 26f315003
Ref: unittest-Footnote-1315704
Ref: unittest-Footnote-2315760
Node: urllib315816
Ref: whatsnew/3 13 urllib315919
Ref: 274315919
Ref: urllib-Footnote-1316524
Node: webbrowser316580
Ref: whatsnew/3 13 webbrowser316666
Ref: 278316666
Ref: webbrowser-Footnote-1317157
Ref: webbrowser-Footnote-2317213
Node: New Deprecations317269
Ref: whatsnew/3 13 new-deprecations317413
Ref: 27a317413
Ref: New Deprecations-Footnote-1325526
Ref: New Deprecations-Footnote-2325581
Ref: New Deprecations-Footnote-3325637
Ref: New Deprecations-Footnote-4325692
Ref: New Deprecations-Footnote-5325748
Ref: New Deprecations-Footnote-6325803
Ref: New Deprecations-Footnote-7325859
Ref: New Deprecations-Footnote-8325914
Ref: New Deprecations-Footnote-9325970
Ref: New Deprecations-Footnote-10326025
Ref: New Deprecations-Footnote-11326081
Ref: New Deprecations-Footnote-12326138
Ref: New Deprecations-Footnote-13326194
Ref: New Deprecations-Footnote-14326251
Ref: New Deprecations-Footnote-15326308
Ref: New Deprecations-Footnote-16326364
Ref: New Deprecations-Footnote-17326421
Ref: New Deprecations-Footnote-18326478
Ref: New Deprecations-Footnote-19326535
Ref: New Deprecations-Footnote-20326592
Ref: New Deprecations-Footnote-21326649
Ref: New Deprecations-Footnote-22326705
Node: Pending Removal in Python 3 14326762
Ref: whatsnew/3 13 pending-removal-in-python-3-14326884
Ref: 299326884
Ref: Pending Removal in Python 3 14-Footnote-1332208
Ref: Pending Removal in Python 3 14-Footnote-2332263
Ref: Pending Removal in Python 3 14-Footnote-3332318
Ref: Pending Removal in Python 3 14-Footnote-4332373
Ref: Pending Removal in Python 3 14-Footnote-5332428
Ref: Pending Removal in Python 3 14-Footnote-6332484
Ref: Pending Removal in Python 3 14-Footnote-7332539
Ref: Pending Removal in Python 3 14-Footnote-8332594
Ref: Pending Removal in Python 3 14-Footnote-9332649
Ref: Pending Removal in Python 3 14-Footnote-10332704
Ref: Pending Removal in Python 3 14-Footnote-11332761
Ref: Pending Removal in Python 3 14-Footnote-12332817
Ref: Pending Removal in Python 3 14-Footnote-13332873
Ref: Pending Removal in Python 3 14-Footnote-14332916
Ref: Pending Removal in Python 3 14-Footnote-15332973
Node: Pending Removal in Python 3 15333029
Ref: whatsnew/3 13 pending-removal-in-python-3-15333190
Ref: 2b9333190
Ref: Pending Removal in Python 3 15-Footnote-1336417
Ref: Pending Removal in Python 3 15-Footnote-2336472
Ref: Pending Removal in Python 3 15-Footnote-3336528
Ref: Pending Removal in Python 3 15-Footnote-4336584
Ref: Pending Removal in Python 3 15-Footnote-5336640
Node: Pending Removal in Python 3 16336696
Ref: whatsnew/3 13 pending-removal-in-python-3-16336861
Ref: 2bf336861
Ref: Pending Removal in Python 3 16-Footnote-1337342
Node: Pending Removal in Future Versions337398
Ref: whatsnew/3 13 pending-removal-in-future-versions337524
Ref: 2c1337524
Ref: Pending Removal in Future Versions-Footnote-1344595
Ref: Pending Removal in Future Versions-Footnote-2344650
Ref: Pending Removal in Future Versions-Footnote-3344705
Ref: Pending Removal in Future Versions-Footnote-4344761
Ref: Pending Removal in Future Versions-Footnote-5344817
Ref: Pending Removal in Future Versions-Footnote-6344872
Node: CPython Bytecode Changes344927
Ref: whatsnew/3 13 cpython-bytecode-changes345060
Ref: 2e5345060
Ref: CPython Bytecode Changes-Footnote-1345494
Node: C API Changes345550
Ref: whatsnew/3 13 c-api-changes345680
Ref: 2e6345680
Node: New Features<2>345766
Ref: whatsnew/3 13 id8345831
Ref: 2e7345831
Ref: New Features<2>-Footnote-1357329
Ref: New Features<2>-Footnote-2357385
Ref: New Features<2>-Footnote-3357440
Ref: New Features<2>-Footnote-4357496
Ref: New Features<2>-Footnote-5357552
Ref: New Features<2>-Footnote-6357608
Ref: New Features<2>-Footnote-7357664
Ref: New Features<2>-Footnote-8357720
Ref: New Features<2>-Footnote-9357776
Ref: New Features<2>-Footnote-10357831
Ref: New Features<2>-Footnote-11357888
Ref: New Features<2>-Footnote-12357945
Ref: New Features<2>-Footnote-13358002
Ref: New Features<2>-Footnote-14358059
Ref: New Features<2>-Footnote-15358116
Ref: New Features<2>-Footnote-16358173
Ref: New Features<2>-Footnote-17358227
Ref: New Features<2>-Footnote-18358284
Ref: New Features<2>-Footnote-19358341
Ref: New Features<2>-Footnote-20358398
Ref: New Features<2>-Footnote-21358454
Ref: New Features<2>-Footnote-22358511
Ref: New Features<2>-Footnote-23358567
Ref: New Features<2>-Footnote-24358623
Ref: New Features<2>-Footnote-25358680
Ref: New Features<2>-Footnote-26358737
Ref: New Features<2>-Footnote-27358794
Ref: New Features<2>-Footnote-28358851
Ref: New Features<2>-Footnote-29358908
Ref: New Features<2>-Footnote-30358965
Ref: New Features<2>-Footnote-31359022
Ref: New Features<2>-Footnote-32359079
Ref: New Features<2>-Footnote-33359136
Ref: New Features<2>-Footnote-34359179
Ref: New Features<2>-Footnote-35359236
Ref: New Features<2>-Footnote-36359293
Ref: New Features<2>-Footnote-37359350
Ref: New Features<2>-Footnote-38359406
Ref: New Features<2>-Footnote-39359449
Node: Build Changes359506
Ref: whatsnew/3 13 build-changes359634
Ref: 34c359634
Ref: Build Changes-Footnote-1361727
Ref: Build Changes-Footnote-2361782
Ref: Build Changes-Footnote-3361838
Ref: Build Changes-Footnote-4361894
Ref: Build Changes-Footnote-5361949
Ref: Build Changes-Footnote-6361991
Ref: Build Changes-Footnote-7362047
Ref: Build Changes-Footnote-8362089
Ref: Build Changes-Footnote-9362145
Ref: Build Changes-Footnote-10362191
Ref: Build Changes-Footnote-11362248
Node: Porting to Python 3 13362305
Ref: whatsnew/3 13 porting-to-python-3-13362443
Ref: 12c362443
Node: Changes in the Python API362717
Ref: whatsnew/3 13 changes-in-the-python-api362830
Ref: 34f362830
Ref: whatsnew/3 13 pep667-porting-notes-py364705
Ref: 166364705
Ref: Changes in the Python API-Footnote-1366170
Ref: Changes in the Python API-Footnote-2366226
Ref: Changes in the Python API-Footnote-3366281
Ref: Changes in the Python API-Footnote-4366337
Ref: Changes in the Python API-Footnote-5366393
Ref: Changes in the Python API-Footnote-6366435
Ref: Changes in the Python API-Footnote-7366477
Ref: Changes in the Python API-Footnote-8366519
Node: Changes in the C API366561
Ref: whatsnew/3 13 changes-in-the-c-api366697
Ref: 359366697
Ref: whatsnew/3 13 pep667-porting-notes-c370065
Ref: 167370065
Ref: Changes in the C API-Footnote-1371856
Ref: Changes in the C API-Footnote-2371912
Ref: Changes in the C API-Footnote-3371968
Ref: Changes in the C API-Footnote-4372024
Ref: Changes in the C API-Footnote-5372079
Ref: Changes in the C API-Footnote-6372135
Ref: Changes in the C API-Footnote-7372191
Ref: Changes in the C API-Footnote-8372247
Ref: Changes in the C API-Footnote-9372289
Ref: Changes in the C API-Footnote-10372331
Ref: Changes in the C API-Footnote-11372374
Node: Removed C APIs372417
Ref: whatsnew/3 13 removed-c-apis372545
Ref: 361372545
Ref: Removed C APIs-Footnote-1378749
Ref: Removed C APIs-Footnote-2378805
Ref: Removed C APIs-Footnote-3378861
Ref: Removed C APIs-Footnote-4378916
Ref: Removed C APIs-Footnote-5378958
Ref: Removed C APIs-Footnote-6379014
Ref: Removed C APIs-Footnote-7379070
Ref: Removed C APIs-Footnote-8379126
Ref: Removed C APIs-Footnote-9379168
Ref: Removed C APIs-Footnote-10379224
Ref: Removed C APIs-Footnote-11379281
Ref: Removed C APIs-Footnote-12379335
Ref: Removed C APIs-Footnote-13379392
Ref: Removed C APIs-Footnote-14379448
Node: Deprecated C APIs379505
Ref: whatsnew/3 13 deprecated-c-apis379604
Ref: 379379604
Ref: Deprecated C APIs-Footnote-1382097
Ref: Deprecated C APIs-Footnote-2382153
Ref: Deprecated C APIs-Footnote-3382209
Ref: Deprecated C APIs-Footnote-4382265
Ref: Deprecated C APIs-Footnote-5382318
Ref: Deprecated C APIs-Footnote-6382374
Node: Pending Removal in Python 3 14<2>382416
Ref: whatsnew/3 13 id9382545
Ref: 38b382545
Ref: Pending Removal in Python 3 14<2>-Footnote-1385770
Ref: Pending Removal in Python 3 14<2>-Footnote-2385812
Ref: Pending Removal in Python 3 14<2>-Footnote-3385868
Node: Pending Removal in Python 3 15<2>385923
Ref: whatsnew/3 13 id10386098
Ref: 3b7386098
Node: Pending Removal in Future Versions<2>387386
Ref: whatsnew/3 13 id11387519
Ref: 3b9387519
Node: Regression Test Changes389753
Ref: whatsnew/3 13 regression-test-changes389869
Ref: 3d7389869
Ref: Regression Test Changes-Footnote-1390310
Node: Python 3 12 有什麼新功能390366
Ref: whatsnew/3 12 doc390534
Ref: 3d9390534
Ref: whatsnew/3 12 what-s-new-in-python-3-12390534
Ref: 3da390534
Ref: Python 3 12 有什麼新功能-Footnote-1391193
Node: 發布重點摘要391235
Ref: whatsnew/3 12 summary-release-highlights391341
Ref: 3db391341
Ref: whatsnew/3 12 improved-error-messages393120
Ref: 3e4393120
Ref: 發布重點摘要-Footnote-1395871
Ref: 發布重點摘要-Footnote-2395919
Ref: 發布重點摘要-Footnote-3395961
Ref: 發布重點摘要-Footnote-4396003
Ref: 發布重點摘要-Footnote-5396062
Ref: 發布重點摘要-Footnote-6396141
Node: 新增特性396196
Ref: whatsnew/3 12 new-features396345
Ref: 3f6396345
Node: PEP 695：型別參數語法396884
Ref: whatsnew/3 12 pep-695-type-parameter-syntax397014
Ref: 3f7397014
Ref: whatsnew/3 12 whatsnew312-pep695397014
Ref: 3dd397014
Ref: PEP 695：型別參數語法-Footnote-1399530
Ref: PEP 695：型別參數語法-Footnote-2399572
Ref: PEP 695：型別參數語法-Footnote-3399614
Ref: PEP 695：型別參數語法-Footnote-4399656
Node: PEP 701 Syntactic formalization of f-strings399712
Ref: whatsnew/3 12 pep-701-syntactic-formalization-of-f-strings399880
Ref: 3ff399880
Ref: whatsnew/3 12 whatsnew312-pep701399880
Ref: 3e1399880
Ref: PEP 701 Syntactic formalization of f-strings-Footnote-1404170
Ref: PEP 701 Syntactic formalization of f-strings-Footnote-2404212
Ref: PEP 701 Syntactic formalization of f-strings-Footnote-3404254
Ref: PEP 701 Syntactic formalization of f-strings-Footnote-4404296
Node: PEP 684 A Per-Interpreter GIL404352
Ref: whatsnew/3 12 pep-684-a-per-interpreter-gil404533
Ref: 401404533
Ref: whatsnew/3 12 whatsnew312-pep684404533
Ref: 3e2404533
Ref: PEP 684 A Per-Interpreter GIL-Footnote-1405626
Ref: PEP 684 A Per-Interpreter GIL-Footnote-2405668
Ref: PEP 684 A Per-Interpreter GIL-Footnote-3405710
Ref: PEP 684 A Per-Interpreter GIL-Footnote-4405798
Node: PEP 669 Low impact monitoring for CPython405854
Ref: whatsnew/3 12 pep-669-low-impact-monitoring-for-cpython406046
Ref: 403406046
Ref: whatsnew/3 12 whatsnew312-pep669406046
Ref: 3e3406046
Ref: PEP 669 Low impact monitoring for CPython-Footnote-1406611
Ref: PEP 669 Low impact monitoring for CPython-Footnote-2406653
Node: PEP 688 Making the buffer protocol accessible in Python406709
Ref: whatsnew/3 12 pep-688-making-the-buffer-protocol-accessible-in-python406902
Ref: 404406902
Ref: whatsnew/3 12 whatsnew312-pep688406902
Ref: 3e6406902
Ref: PEP 688 Making the buffer protocol accessible in Python-Footnote-1407545
Ref: PEP 688 Making the buffer protocol accessible in Python-Footnote-2407587
Node: PEP 709 Comprehension inlining407643
Ref: whatsnew/3 12 pep-709-comprehension-inlining407818
Ref: 407407818
Ref: whatsnew/3 12 whatsnew312-pep709407818
Ref: 3ed407818
Ref: PEP 709 Comprehension inlining-Footnote-1409501
Ref: PEP 709 Comprehension inlining-Footnote-2409543
Node: Improved Error Messages409585
Ref: Improved Error Messages-Footnote-1412052
Ref: Improved Error Messages-Footnote-2412107
Ref: Improved Error Messages-Footnote-3412162
Ref: Improved Error Messages-Footnote-4412217
Node: New Features Related to Type Hints412272
Ref: whatsnew/3 12 new-features-related-to-type-hints412421
Ref: 408412421
Ref: New Features Related to Type Hints-Footnote-1412857
Node: PEP 692 Using TypedDict for more precise **kwargs typing412899
Ref: whatsnew/3 12 pep-692-using-typeddict-for-more-precise-kwargs-typing413079
Ref: 409413079
Ref: whatsnew/3 12 whatsnew312-pep692413079
Ref: 3ee413079
Ref: PEP 692 Using TypedDict for more precise **kwargs typing-Footnote-1413773
Ref: PEP 692 Using TypedDict for more precise **kwargs typing-Footnote-2413815
Ref: PEP 692 Using TypedDict for more precise **kwargs typing-Footnote-3413857
Ref: PEP 692 Using TypedDict for more precise **kwargs typing-Footnote-4413899
Node: PEP 698 Override Decorator for Static Typing413955
Ref: whatsnew/3 12 pep-698-override-decorator-for-static-typing414135
Ref: 40a414135
Ref: whatsnew/3 12 whatsnew312-pep698414135
Ref: 3f0414135
Ref: PEP 698 Override Decorator for Static Typing-Footnote-1415113
Ref: PEP 698 Override Decorator for Static Typing-Footnote-2415155
Node: 其他語言更動415211
Ref: whatsnew/3 12 other-language-changes415360
Ref: 40b415360
Ref: 其他語言更動-Footnote-1420032
Ref: 其他語言更動-Footnote-2420087
Ref: 其他語言更動-Footnote-3420142
Ref: 其他語言更動-Footnote-4420197
Ref: 其他語言更動-Footnote-5420239
Ref: 其他語言更動-Footnote-6420295
Ref: 其他語言更動-Footnote-7420337
Ref: 其他語言更動-Footnote-8420392
Ref: 其他語言更動-Footnote-9420448
Ref: 其他語言更動-Footnote-10420503
Ref: 其他語言更動-Footnote-11420559
Ref: 其他語言更動-Footnote-12420615
Ref: 其他語言更動-Footnote-13420672
Ref: 其他語言更動-Footnote-14420729
Ref: 其他語言更動-Footnote-15420785
Ref: 其他語言更動-Footnote-16420828
Ref: 其他語言更動-Footnote-17420884
Node: 新增模組420940
Ref: whatsnew/3 12 new-modules421070
Ref: 419421070
Node: 改進的模組421117
Ref: whatsnew/3 12 improved-modules421238
Ref: 41a421238
Node: array<2>421856
Ref: whatsnew/3 12 array421935
Ref: 41b421935
Ref: array<2>-Footnote-1422163
Node: asyncio<2>422218
Ref: whatsnew/3 12 asyncio422314
Ref: 41c422314
Ref: asyncio<2>-Footnote-1424299
Ref: asyncio<2>-Footnote-2424354
Ref: asyncio<2>-Footnote-3424410
Ref: asyncio<2>-Footnote-4424466
Ref: asyncio<2>-Footnote-5424522
Ref: asyncio<2>-Footnote-6424577
Ref: asyncio<2>-Footnote-7424632
Ref: asyncio<2>-Footnote-8424687
Ref: asyncio<2>-Footnote-9424743
Ref: asyncio<2>-Footnote-10424799
Node: calendar424855
Ref: whatsnew/3 12 calendar424946
Ref: 427424946
Ref: calendar-Footnote-1425198
Node: csv425254
Ref: whatsnew/3 12 csv425341
Ref: 42a425341
Node: dis<2>425575
Ref: whatsnew/3 12 dis425666
Ref: 42f425666
Ref: dis<2>-Footnote-1426276
Ref: dis<2>-Footnote-2426331
Node: fractions<2>426386
Ref: whatsnew/3 12 fractions426493
Ref: 432426493
Ref: fractions<2>-Footnote-1426715
Node: importlib resources426771
Ref: whatsnew/3 12 importlib-resources426879
Ref: 433426879
Ref: importlib resources-Footnote-1427251
Ref: importlib resources-Footnote-2427306
Node: inspect427362
Ref: whatsnew/3 12 inspect427470
Ref: 436427470
Ref: inspect-Footnote-1428240
Ref: inspect-Footnote-2428295
Ref: inspect-Footnote-3428350
Node: itertools<2>428406
Ref: whatsnew/3 12 itertools428502
Ref: 43d428502
Ref: itertools<2>-Footnote-1428767
Node: math<2>428822
Ref: whatsnew/3 12 math428916
Ref: 43e428916
Ref: math<2>-Footnote-1429334
Ref: math<2>-Footnote-2429390
Node: os<2>429445
Ref: whatsnew/3 12 os429537
Ref: 441429537
Ref: os<2>-Footnote-1430882
Ref: os<2>-Footnote-2430937
Ref: os<2>-Footnote-3430992
Ref: os<2>-Footnote-4431048
Node: os path<2>431103
Ref: whatsnew/3 12 os-path431198
Ref: 44a431198
Ref: os path<2>-Footnote-1431563
Ref: os path<2>-Footnote-2431618
Node: pathlib<3>431674
Ref: whatsnew/3 12 pathlib431770
Ref: 44d431770
Ref: pathlib<3>-Footnote-1433065
Ref: pathlib<3>-Footnote-2433120
Ref: pathlib<3>-Footnote-3433175
Node: pdb<2>433230
Ref: whatsnew/3 12 pdb433325
Ref: 455433325
Ref: pdb<2>-Footnote-1433598
Node: random<2>433654
Ref: whatsnew/3 12 random433748
Ref: 456433748
Ref: random<2>-Footnote-1434079
Ref: random<2>-Footnote-2434134
Node: shutil<2>434190
Ref: whatsnew/3 12 shutil434288
Ref: 459434288
Ref: shutil<2>-Footnote-1435718
Ref: shutil<2>-Footnote-2435773
Ref: shutil<2>-Footnote-3435829
Ref: shutil<2>-Footnote-4435885
Ref: shutil<2>-Footnote-5435941
Node: sqlite3<2>435997
Ref: whatsnew/3 12 sqlite3436099
Ref: 45c436099
Ref: sqlite3<2>-Footnote-1437047
Ref: sqlite3<2>-Footnote-2437102
Ref: sqlite3<2>-Footnote-3437144
Ref: sqlite3<2>-Footnote-4437199
Ref: sqlite3<2>-Footnote-5437255
Node: statistics<2>437311
Ref: whatsnew/3 12 statistics437410
Ref: 462437410
Ref: statistics<2>-Footnote-1437690
Node: sys<2>437745
Ref: whatsnew/3 12 sys437845
Ref: 464437845
Ref: sys<2>-Footnote-1439395
Ref: sys<2>-Footnote-2439451
Ref: sys<2>-Footnote-3439506
Ref: sys<2>-Footnote-4439562
Node: tempfile<2>439618
Ref: whatsnew/3 12 tempfile439714
Ref: 46c439714
Ref: tempfile<2>-Footnote-1440079
Node: threading440134
Ref: whatsnew/3 12 threading440234
Ref: 46e440234
Ref: threading-Footnote-1440583
Node: tkinter<2>440638
Ref: whatsnew/3 12 tkinter440735
Ref: 471440735
Ref: tkinter<2>-Footnote-1441231
Node: tokenize441286
Ref: whatsnew/3 12 tokenize441382
Ref: 472441382
Ref: tokenize-Footnote-1441739
Ref: tokenize-Footnote-2441781
Node: types<2>441837
Ref: whatsnew/3 12 types441932
Ref: 474441932
Ref: types<2>-Footnote-1442228
Node: typing<3>442284
Ref: whatsnew/3 12 typing442385
Ref: 477442385
Ref: whatsnew/3 12 whatsnew-typing-py312442385
Ref: 478442385
Ref: typing<3>-Footnote-1444958
Ref: typing<3>-Footnote-2445014
Ref: typing<3>-Footnote-3445069
Ref: typing<3>-Footnote-4445125
Ref: typing<3>-Footnote-5445181
Node: unicodedata<2>445236
Ref: whatsnew/3 12 unicodedata445340
Ref: 47c445340
Ref: unicodedata<2>-Footnote-1445538
Node: unittest<2>445593
Ref: whatsnew/3 12 unittest445692
Ref: 47d445692
Ref: unittest<2>-Footnote-1446484
Node: uuid446539
Ref: whatsnew/3 12 uuid446615
Ref: 47e446615
Ref: uuid-Footnote-1446785
Node: 最佳化446840
Ref: whatsnew/3 12 optimizations446975
Ref: 47f446975
Ref: 最佳化-Footnote-1448415
Ref: 最佳化-Footnote-2448457
Ref: 最佳化-Footnote-3448512
Ref: 最佳化-Footnote-4448567
Ref: 最佳化-Footnote-5448623
Ref: 最佳化-Footnote-6448678
Ref: 最佳化-Footnote-7448734
Ref: 最佳化-Footnote-8448776
Ref: 最佳化-Footnote-9448832
Node: CPython 位元組碼變更448888
Ref: whatsnew/3 12 cpython-bytecode-changes449023
Ref: 485449023
Ref: CPython 位元組碼變更-Footnote-1451062
Ref: CPython 位元組碼變更-Footnote-2451117
Ref: CPython 位元組碼變更-Footnote-3451173
Ref: CPython 位元組碼變更-Footnote-4451228
Ref: CPython 位元組碼變更-Footnote-5451283
Ref: CPython 位元組碼變更-Footnote-6451338
Ref: CPython 位元組碼變更-Footnote-7451394
Ref: CPython 位元組碼變更-Footnote-8451449
Ref: CPython 位元組碼變更-Footnote-9451505
Ref: CPython 位元組碼變更-Footnote-10451547
Ref: CPython 位元組碼變更-Footnote-11451604
Ref: CPython 位元組碼變更-Footnote-12451660
Ref: CPython 位元組碼變更-Footnote-13451703
Ref: CPython 位元組碼變更-Footnote-14451760
Ref: CPython 位元組碼變更-Footnote-15451817
Node: Demos and Tools451874
Ref: whatsnew/3 12 demos-and-tools452009
Ref: 492452009
Ref: Demos and Tools-Footnote-1452462
Ref: Demos and Tools-Footnote-2452510
Ref: Demos and Tools-Footnote-3452565
Ref: Demos and Tools-Footnote-4452613
Node: 已棄用452668
Ref: whatsnew/3 12 deprecated452786
Ref: 493452786
Ref: 已棄用-Footnote-1463162
Ref: 已棄用-Footnote-2463217
Ref: 已棄用-Footnote-3463272
Ref: 已棄用-Footnote-4463327
Ref: 已棄用-Footnote-5463382
Ref: 已棄用-Footnote-6463438
Ref: 已棄用-Footnote-7463494
Ref: 已棄用-Footnote-8463549
Ref: 已棄用-Footnote-9463605
Ref: 已棄用-Footnote-10463660
Ref: 已棄用-Footnote-11463716
Ref: 已棄用-Footnote-12463773
Ref: 已棄用-Footnote-13463829
Ref: 已棄用-Footnote-14463885
Ref: 已棄用-Footnote-15463941
Ref: 已棄用-Footnote-16463997
Ref: 已棄用-Footnote-17464041
Ref: 已棄用-Footnote-18464098
Ref: 已棄用-Footnote-19464154
Ref: 已棄用-Footnote-20464211
Ref: 已棄用-Footnote-21464268
Ref: 已棄用-Footnote-22464324
Ref: 已棄用-Footnote-23464380
Ref: 已棄用-Footnote-24464436
Ref: 已棄用-Footnote-25464492
Ref: 已棄用-Footnote-26464548
Ref: 已棄用-Footnote-27464604
Ref: 已棄用-Footnote-28464661
Ref: 已棄用-Footnote-29464704
Node: Python 3 13 中待移除的項目464761
Ref: whatsnew/3 12 pending-removal-in-python-3-13464882
Ref: 4a3464882
Ref: Python 3 13 中待移除的項目-Footnote-1466345
Ref: Python 3 13 中待移除的項目-Footnote-2466387
Ref: Python 3 13 中待移除的項目-Footnote-3466442
Ref: Python 3 13 中待移除的項目-Footnote-4466497
Ref: Python 3 13 中待移除的項目-Footnote-5466552
Ref: Python 3 13 中待移除的項目-Footnote-6466607
Ref: Python 3 13 中待移除的項目-Footnote-7466662
Ref: Python 3 13 中待移除的項目-Footnote-8466717
Ref: Python 3 13 中待移除的項目-Footnote-9466772
Ref: Python 3 13 中待移除的項目-Footnote-10466827
Ref: Python 3 13 中待移除的項目-Footnote-11466883
Ref: Python 3 13 中待移除的項目-Footnote-12466939
Ref: Python 3 13 中待移除的項目-Footnote-13467035
Node: Python 3 14 中待移除的項目467092
Ref: whatsnew/3 12 pending-removal-in-python-3-14467255
Ref: 4a4467255
Ref: Python 3 14 中待移除的項目-Footnote-1472443
Ref: Python 3 14 中待移除的項目-Footnote-2472498
Ref: Python 3 14 中待移除的項目-Footnote-3472553
Ref: Python 3 14 中待移除的項目-Footnote-4472608
Ref: Python 3 14 中待移除的項目-Footnote-5472663
Ref: Python 3 14 中待移除的項目-Footnote-6472719
Ref: Python 3 14 中待移除的項目-Footnote-7472774
Ref: Python 3 14 中待移除的項目-Footnote-8472829
Ref: Python 3 14 中待移除的項目-Footnote-9472884
Ref: Python 3 14 中待移除的項目-Footnote-10472939
Ref: Python 3 14 中待移除的項目-Footnote-11472996
Ref: Python 3 14 中待移除的項目-Footnote-12473052
Ref: Python 3 14 中待移除的項目-Footnote-13473108
Ref: Python 3 14 中待移除的項目-Footnote-14473151
Ref: Python 3 14 中待移除的項目-Footnote-15473208
Node: Python 3 15 中待移除的項目473264
Ref: whatsnew/3 12 pending-removal-in-python-3-15473427
Ref: 4a5473427
Ref: Python 3 15 中待移除的項目-Footnote-1476600
Ref: Python 3 15 中待移除的項目-Footnote-2476655
Ref: Python 3 15 中待移除的項目-Footnote-3476711
Ref: Python 3 15 中待移除的項目-Footnote-4476767
Ref: Python 3 15 中待移除的項目-Footnote-5476823
Node: Python 3 16 中待移除的項目476879
Ref: whatsnew/3 12 pending-removal-in-python-3-16477042
Ref: 4a6477042
Ref: Python 3 16 中待移除的項目-Footnote-1477536
Node: 未來版本中的待移除項目477592
Ref: whatsnew/3 12 pending-removal-in-future-versions477713
Ref: 4a7477713
Ref: 未來版本中的待移除項目-Footnote-1484393
Ref: 未來版本中的待移除項目-Footnote-2484448
Ref: 未來版本中的待移除項目-Footnote-3484503
Ref: 未來版本中的待移除項目-Footnote-4484559
Ref: 未來版本中的待移除項目-Footnote-5484615
Ref: 未來版本中的待移除項目-Footnote-6484670
Node: 已移除484725
Ref: whatsnew/3 12 removed484850
Ref: 4a8484850
Node: asynchat 和 asyncore485277
Ref: whatsnew/3 12 asynchat-and-asyncore485368
Ref: 4a9485368
Ref: asynchat 和 asyncore-Footnote-1485683
Ref: asynchat 和 asyncore-Footnote-2485725
Node: configparser<4>485780
Ref: whatsnew/3 12 configparser485889
Ref: 4aa485889
Ref: configparser<4>-Footnote-1486517
Node: distutils486572
Ref: whatsnew/3 12 distutils486669
Ref: 4ad486669
Ref: distutils-Footnote-1487098
Ref: distutils-Footnote-2487140
Node: ensurepip487195
Ref: whatsnew/3 12 ensurepip487281
Ref: 4ae487281
Ref: ensurepip-Footnote-1488307
Node: enum488362
Ref: whatsnew/3 12 enum488445
Ref: 4af488445
Ref: enum-Footnote-1488679
Node: ftplib488734
Ref: whatsnew/3 12 ftplib488812
Ref: 4b0488812
Ref: ftplib-Footnote-1489045
Node: gzip489100
Ref: whatsnew/3 12 gzip489181
Ref: 4b1489181
Ref: gzip-Footnote-1489577
Node: hashlib489632
Ref: whatsnew/3 12 hashlib489719
Ref: 4b3489719
Ref: hashlib-Footnote-1490144
Ref: hashlib-Footnote-2490186
Node: importlib<2>490241
Ref: whatsnew/3 12 importlib490327
Ref: 4b5490327
Ref: importlib<2>-Footnote-1491197
Ref: importlib<2>-Footnote-2491252
Ref: importlib<2>-Footnote-3491307
Ref: importlib<2>-Footnote-4491362
Ref: importlib<2>-Footnote-5491417
Node: imp491472
Ref: whatsnew/3 12 imp491556
Ref: 4b6491556
Ref: imp-Footnote-1495684
Node: io<2>495739
Ref: whatsnew/3 12 io495820
Ref: 4bf495820
Ref: io<2>-Footnote-1496239
Node: locale<2>496294
Ref: whatsnew/3 12 locale496377
Ref: 4c2496377
Ref: locale<2>-Footnote-1496645
Node: smtpd496700
Ref: whatsnew/3 12 smtpd496788
Ref: 4c4496788
Ref: smtpd-Footnote-1497142
Ref: smtpd-Footnote-2497184
Ref: smtpd-Footnote-3497227
Node: sqlite3<3>497282
Ref: whatsnew/3 12 id2497367
Ref: 4c5497367
Ref: sqlite3<3>-Footnote-1498107
Node: ssl<2>498162
Ref: whatsnew/3 12 ssl498253
Ref: 4c6498253
Ref: ssl<2>-Footnote-1499310
Ref: ssl<2>-Footnote-2499365
Ref: ssl<2>-Footnote-3499420
Ref: ssl<2>-Footnote-4499476
Node: unittest<3>499531
Ref: whatsnew/3 12 id3499625
Ref: 4ca499625
Ref: whatsnew/3 12 unittest-testcase-removed-aliases499732
Ref: 3f5499732
Ref: unittest<3>-Footnote-1504405
Node: webbrowser<2>504460
Ref: whatsnew/3 12 webbrowser504569
Ref: 4d6504569
Ref: webbrowser<2>-Footnote-1504875
Node: xml etree ElementTree504931
Ref: whatsnew/3 12 xml-etree-elementtree505041
Ref: 4d7505041
Ref: xml etree ElementTree-Footnote-1505504
Node: zipimport<2>505559
Ref: whatsnew/3 12 zipimport505662
Ref: 4d9505662
Ref: zipimport<2>-Footnote-1505997
Ref: zipimport<2>-Footnote-2506039
Node: 其他506094
Ref: whatsnew/3 12 others506167
Ref: 4da506167
Ref: 其他-Footnote-1507194
Ref: 其他-Footnote-2507248
Ref: 其他-Footnote-3507303
Ref: 其他-Footnote-4507358
Ref: 其他-Footnote-5507413
Node: Porting to Python 3 12507468
Ref: whatsnew/3 12 porting-to-python-3-12507596
Ref: 4db507596
Ref: whatsnew/3 12 whatsnew312-porting-to-python312507596
Ref: 473507596
Node: Python API 的變更507799
Ref: whatsnew/3 12 changes-in-the-python-api507878
Ref: 4dc507878
Ref: Python API 的變更-Footnote-1514168
Ref: Python API 的變更-Footnote-2514223
Ref: Python API 的變更-Footnote-3514278
Ref: Python API 的變更-Footnote-4514321
Ref: Python API 的變更-Footnote-5514376
Ref: Python API 的變更-Footnote-6514431
Ref: Python API 的變更-Footnote-7514486
Ref: Python API 的變更-Footnote-8514542
Ref: Python API 的變更-Footnote-9514584
Ref: Python API 的變更-Footnote-10514626
Ref: Python API 的變更-Footnote-11514669
Node: 建置變更514726
Ref: whatsnew/3 12 build-changes514857
Ref: 4ea514857
Ref: 建置變更-Footnote-1516542
Ref: 建置變更-Footnote-2516597
Ref: 建置變更-Footnote-3516652
Ref: 建置變更-Footnote-4516707
Ref: 建置變更-Footnote-5516762
Ref: 建置變更-Footnote-6516817
Node: C API 變更516872
Ref: whatsnew/3 12 c-api-changes516972
Ref: 4eb516972
Node: 新增特性<2>517161
Ref: whatsnew/3 12 id4517259
Ref: 4ec517259
Ref: whatsnew/3 12 whatsnew312-pep697517300
Ref: 3eb517300
Ref: whatsnew/3 12 whatsnew312-pep683523454
Ref: 3ec523454
Ref: 新增特性<2>-Footnote-1525176
Ref: 新增特性<2>-Footnote-2525218
Ref: 新增特性<2>-Footnote-3525260
Ref: 新增特性<2>-Footnote-4525316
Ref: 新增特性<2>-Footnote-5525358
Ref: 新增特性<2>-Footnote-6525414
Ref: 新增特性<2>-Footnote-7525469
Ref: 新增特性<2>-Footnote-8525524
Ref: 新增特性<2>-Footnote-9525579
Ref: 新增特性<2>-Footnote-10525634
Ref: 新增特性<2>-Footnote-11525690
Ref: 新增特性<2>-Footnote-12525746
Ref: 新增特性<2>-Footnote-13525802
Ref: 新增特性<2>-Footnote-14525858
Ref: 新增特性<2>-Footnote-15525914
Ref: 新增特性<2>-Footnote-16525971
Ref: 新增特性<2>-Footnote-17526028
Ref: 新增特性<2>-Footnote-18526085
Ref: 新增特性<2>-Footnote-19526142
Ref: 新增特性<2>-Footnote-20526185
Ref: 新增特性<2>-Footnote-21526241
Ref: 新增特性<2>-Footnote-22526284
Ref: 新增特性<2>-Footnote-23526341
Node: Porting to Python 3 12<2>526398
Ref: whatsnew/3 12 id5526517
Ref: 516526517
Ref: Porting to Python 3 12<2>-Footnote-1533976
Ref: Porting to Python 3 12<2>-Footnote-2534031
Ref: Porting to Python 3 12<2>-Footnote-3534086
Ref: Porting to Python 3 12<2>-Footnote-4534141
Ref: Porting to Python 3 12<2>-Footnote-5534196
Ref: Porting to Python 3 12<2>-Footnote-6534251
Ref: Porting to Python 3 12<2>-Footnote-7534306
Ref: Porting to Python 3 12<2>-Footnote-8534362
Node: 已棄用<2>534418
Ref: whatsnew/3 12 id6534534
Ref: 532534534
Ref: 已棄用<2>-Footnote-1539968
Ref: 已棄用<2>-Footnote-2540010
Ref: 已棄用<2>-Footnote-3540066
Ref: 已棄用<2>-Footnote-4540121
Ref: 已棄用<2>-Footnote-5540176
Ref: 已棄用<2>-Footnote-6540231
Ref: 已棄用<2>-Footnote-7540287
Ref: 已棄用<2>-Footnote-8540343
Node: Python 3 14 中待移除的項目<2>540399
Ref: whatsnew/3 12 id7540529
Ref: 53c540529
Ref: Python 3 14 中待移除的項目<2>-Footnote-1543761
Ref: Python 3 14 中待移除的項目<2>-Footnote-2543803
Ref: Python 3 14 中待移除的項目<2>-Footnote-3543859
Node: Python 3 15 中待移除的項目<2>543914
Ref: whatsnew/3 12 id8544089
Ref: 53d544089
Node: 未來版本中的待移除項目<2>545375
Ref: whatsnew/3 12 id9545505
Ref: 53e545505
Node: 已移除<2>547744
Ref: whatsnew/3 12 id10547826
Ref: 53f547826
Ref: 已移除<2>-Footnote-1548683
Ref: 已移除<2>-Footnote-2548738
Ref: 已移除<2>-Footnote-3548780
Node: Python 3 11 有什麼新功能548835
Ref: whatsnew/3 11 doc549008
Ref: 540549008
Ref: whatsnew/3 11 what-s-new-in-python-3-11549008
Ref: 541549008
Node: 發布重點摘要<2>550034
Ref: whatsnew/3 11 summary-release-highlights550146
Ref: 542550146
Ref: whatsnew/3 11 whatsnew311-summary550146
Ref: 543550146
Ref: 發布重點摘要<2>-Footnote-1551685
Ref: 發布重點摘要<2>-Footnote-2551727
Ref: 發布重點摘要<2>-Footnote-3551752
Ref: 發布重點摘要<2>-Footnote-4551794
Ref: 發布重點摘要<2>-Footnote-5551836
Node: 新增特性<3>551878
Ref: whatsnew/3 11 new-features552029
Ref: 553552029
Ref: whatsnew/3 11 whatsnew311-features552029
Ref: 554552029
Node: PEP 657：回溯 traceback 中更細緻的錯誤位置552379
Ref: whatsnew/3 11 pep-657-fine-grained-error-locations-in-tracebacks552527
Ref: 555552527
Ref: whatsnew/3 11 whatsnew311-pep657552527
Ref: 547552527
Ref: PEP 657：回溯 traceback 中更細緻的錯誤位置-Footnote-1555190
Ref: PEP 657：回溯 traceback 中更細緻的錯誤位置-Footnote-2555232
Node: PEP 654：例外群組與 except*555297
Ref: whatsnew/3 11 pep-654-exception-groups-and-except555500
Ref: 55b555500
Ref: whatsnew/3 11 whatsnew311-pep654555500
Ref: 545555500
Ref: PEP 654：例外群組與 except*-Footnote-1556132
Ref: PEP 654：例外群組與 except*-Footnote-2556174
Ref: PEP 654：例外群組與 except*-Footnote-3556216
Node: PEP 678：運用例外註解使其更加詳盡556281
Ref: whatsnew/3 11 pep-678-exceptions-can-be-enriched-with-notes556476
Ref: 55d556476
Ref: whatsnew/3 11 whatsnew311-pep678556476
Ref: 546556476
Ref: PEP 678：運用例外註解使其更加詳盡-Footnote-1556966
Ref: PEP 678：運用例外註解使其更加詳盡-Footnote-2557008
Node: Windows py exe 啟動程式 launcher 的改進557073
Ref: whatsnew/3 11 whatsnew311-windows-launcher557226
Ref: 560557226
Ref: whatsnew/3 11 windows-py-exe-launcher-improvements557226
Ref: 561557226
Ref: whatsnew/3 11 new-feat-related-type-hints-311558517
Ref: 563558517
Ref: Windows py exe 啟動程式 launcher 的改進-Footnote-1558555
Ref: Windows py exe 啟動程式 launcher 的改進-Footnote-2558597
Node: 型別提示相關的新特性558628
Ref: whatsnew/3 11 new-features-related-to-type-hints558779
Ref: 564558779
Ref: whatsnew/3 11 whatsnew311-typing-features558779
Ref: 565558779
Ref: 型別提示相關的新特性-Footnote-1559473
Node: PEP 646：可變參數泛型 variadic generics559515
Ref: whatsnew/3 11 pep-646-variadic-generics559697
Ref: 566559697
Ref: whatsnew/3 11 whatsnew311-pep646559697
Ref: 54b559697
Ref: PEP 646：可變參數泛型 variadic generics-Footnote-1560663
Ref: PEP 646：可變參數泛型 variadic generics-Footnote-2560705
Ref: PEP 646：可變參數泛型 variadic generics-Footnote-3560747
Ref: PEP 646：可變參數泛型 variadic generics-Footnote-4560789
Node: PEP 655：標記獨立 TypedDict 項目為必要或不必要560854
Ref: whatsnew/3 11 pep-655-marking-individual-typeddict-items-as-required-or-not-required561066
Ref: 567561066
Ref: whatsnew/3 11 whatsnew311-pep655561066
Ref: 54c561066
Ref: PEP 655：標記獨立 TypedDict 項目為必要或不必要-Footnote-1562207
Ref: PEP 655：標記獨立 TypedDict 項目為必要或不必要-Footnote-2562249
Node: PEP 673：Self 型別562314
Ref: whatsnew/3 11 pep-673-self-type562547
Ref: 56a562547
Ref: whatsnew/3 11 whatsnew311-pep673562547
Ref: 54d562547
Ref: PEP 673：Self 型別-Footnote-1563534
Ref: PEP 673：Self 型別-Footnote-2563615
Ref: PEP 673：Self 型別-Footnote-3563657
Node: PEP 675：任意的文本字串型別 Arbitrary literal string type563722
Ref: whatsnew/3 11 pep-675-arbitrary-literal-string-type563945
Ref: 56d563945
Ref: whatsnew/3 11 whatsnew311-pep675563945
Ref: 54e563945
Ref: PEP 675：任意的文本字串型別 Arbitrary literal string type-Footnote-1565354
Ref: PEP 675：任意的文本字串型別 Arbitrary literal string type-Footnote-2565396
Node: PEP 681：資料類別轉換 Data class transforms565461
Ref: whatsnew/3 11 pep-681-data-class-transforms565689
Ref: 56f565689
Ref: whatsnew/3 11 whatsnew311-pep681565689
Ref: 54f565689
Ref: PEP 681：資料類別轉換 Data class transforms-Footnote-1566778
Ref: PEP 681：資料類別轉換 Data class transforms-Footnote-2566820
Node: PEP 563 可能不是未來566875
Ref: whatsnew/3 11 pep-563-may-not-be-the-future567027
Ref: 570567027
Ref: whatsnew/3 11 whatsnew311-pep563-deferred567027
Ref: 571567027
Ref: PEP 563 可能不是未來-Footnote-1567428
Ref: PEP 563 可能不是未來-Footnote-2567470
Node: 其他語言更動<2>567581
Ref: whatsnew/3 11 other-language-changes567744
Ref: 572567744
Ref: whatsnew/3 11 whatsnew311-other-lang-changes567744
Ref: 573567744
Ref: whatsnew/3 11 whatsnew311-pythonsafepath569593
Ref: 54a569593
Ref: 其他語言更動<2>-Footnote-1570855
Ref: 其他語言更動<2>-Footnote-2570920
Ref: 其他語言更動<2>-Footnote-3570985
Ref: 其他語言更動<2>-Footnote-4571050
Ref: 其他語言更動<2>-Footnote-5571115
Ref: 其他語言更動<2>-Footnote-6571170
Ref: 其他語言更動<2>-Footnote-7571235
Ref: 其他語言更動<2>-Footnote-8571290
Ref: 其他語言更動<2>-Footnote-9571332
Ref: 其他語言更動<2>-Footnote-10571387
Node: 其他 CPython 實作更動571443
Ref: whatsnew/3 11 other-cpython-implementation-changes571591
Ref: 589571591
Ref: whatsnew/3 11 whatsnew311-other-implementation-changes571591
Ref: 58a571591
Ref: 其他 CPython 實作更動-Footnote-1574795
Ref: 其他 CPython 實作更動-Footnote-2574860
Ref: 其他 CPython 實作更動-Footnote-3574902
Ref: 其他 CPython 實作更動-Footnote-4574967
Ref: 其他 CPython 實作更動-Footnote-5575032
Ref: 其他 CPython 實作更動-Footnote-6575097
Ref: 其他 CPython 實作更動-Footnote-7575162
Ref: 其他 CPython 實作更動-Footnote-8575227
Node: 新增模組<2>575297
Ref: whatsnew/3 11 new-modules575442
Ref: 59a575442
Ref: whatsnew/3 11 whatsnew311-new-modules575442
Ref: 59b575442
Ref: 新增模組<2>-Footnote-1575800
Ref: 新增模組<2>-Footnote-2575825
Ref: 新增模組<2>-Footnote-3575867
Ref: 新增模組<2>-Footnote-4575932
Ref: 新增模組<2>-Footnote-5575974
Node: 改進的模組<2>576039
Ref: whatsnew/3 11 improved-modules576169
Ref: 59c576169
Ref: whatsnew/3 11 whatsnew311-improved-modules576169
Ref: 59d576169
Node: asyncio<3>576895
Ref: whatsnew/3 11 asyncio576979
Ref: 59e576979
Ref: whatsnew/3 11 whatsnew311-asyncio576979
Ref: 59f576979
Ref: asyncio<3>-Footnote-1578910
Ref: asyncio<3>-Footnote-2578965
Ref: asyncio<3>-Footnote-3579020
Ref: asyncio<3>-Footnote-4579075
Ref: asyncio<3>-Footnote-5579130
Ref: asyncio<3>-Footnote-6579195
Node: contextlib579260
Ref: whatsnew/3 11 contextlib579364
Ref: 5af579364
Ref: whatsnew/3 11 whatsnew311-contextlib579364
Ref: 5b0579364
Ref: contextlib-Footnote-1579671
Node: dataclasses579736
Ref: whatsnew/3 11 dataclasses579838
Ref: 5b3579838
Ref: whatsnew/3 11 whatsnew311-dataclasses579838
Ref: 5b4579838
Ref: dataclasses-Footnote-1580185
Node: datetime580250
Ref: whatsnew/3 11 datetime580349
Ref: 5b7580349
Ref: whatsnew/3 11 whatsnew311-datetime580349
Ref: 5b8580349
Ref: datetime-Footnote-1580902
Ref: datetime-Footnote-2580957
Node: enum<2>581012
Ref: whatsnew/3 11 enum581105
Ref: 5bd581105
Ref: whatsnew/3 11 whatsnew311-enum581105
Ref: 5be581105
Node: fcntl583662
Ref: whatsnew/3 11 fcntl583759
Ref: 5d9583759
Ref: whatsnew/3 11 whatsnew311-fcntl583759
Ref: 5da583759
Node: fractions<3>583965
Ref: whatsnew/3 11 fractions584064
Ref: 5db584064
Ref: whatsnew/3 11 whatsnew311-fractions584064
Ref: 5dc584064
Ref: fractions<3>-Footnote-1584500
Ref: fractions<3>-Footnote-2584542
Ref: fractions<3>-Footnote-3584607
Node: functools584672
Ref: whatsnew/3 11 functools584773
Ref: 5dd584773
Ref: whatsnew/3 11 whatsnew311-functools584773
Ref: 5de584773
Ref: functools-Footnote-1585855
Node: gzip<2>585920
Ref: whatsnew/3 11 gzip586019
Ref: 5e2586019
Ref: whatsnew/3 11 whatsnew311-gzip586019
Ref: 5e3586019
Ref: gzip<2>-Footnote-1586727
Node: hashlib<2>586783
Ref: whatsnew/3 11 hashlib586889
Ref: 5e6586889
Ref: whatsnew/3 11 whatsnew311-hashlib586889
Ref: 5e7586889
Ref: hashlib<2>-Footnote-1587744
Ref: hashlib<2>-Footnote-2587776
Ref: hashlib<2>-Footnote-3587841
Ref: hashlib<2>-Footnote-4587906
Node: IDLE 與 idlelib587961
Ref: whatsnew/3 11 idle-and-idlelib588070
Ref: 5eb588070
Ref: whatsnew/3 11 whatsnew311-idle588070
Ref: 5ec588070
Ref: IDLE 與 idlelib-Footnote-1588448
Ref: IDLE 與 idlelib-Footnote-2588513
Node: inspect<2>588568
Ref: whatsnew/3 11 inspect588676
Ref: 5ed588676
Ref: whatsnew/3 11 whatsnew311-inspect588676
Ref: 5ee588676
Ref: inspect<2>-Footnote-1589759
Ref: inspect<2>-Footnote-2589824
Ref: inspect<2>-Footnote-3589889
Ref: inspect<2>-Footnote-4589931
Node: locale<3>589986
Ref: whatsnew/3 11 locale590085
Ref: 5fa590085
Ref: whatsnew/3 11 whatsnew311-locale590085
Ref: 5fb590085
Node: logging590324
Ref: whatsnew/3 11 logging590420
Ref: 5fd590420
Ref: whatsnew/3 11 whatsnew311-logging590420
Ref: 5fe590420
Ref: logging-Footnote-1591090
Ref: logging-Footnote-2591145
Node: math<3>591200
Ref: whatsnew/3 11 math591295
Ref: 604591295
Ref: whatsnew/3 11 whatsnew311-math591295
Ref: 605591295
Ref: math<3>-Footnote-1592062
Ref: math<3>-Footnote-2592127
Ref: math<3>-Footnote-3592192
Ref: math<3>-Footnote-4592257
Node: operator592322
Ref: whatsnew/3 11 operator592415
Ref: 60a592415
Ref: whatsnew/3 11 whatsnew311-operator592415
Ref: 60b592415
Ref: operator-Footnote-1592669
Node: os<3>592734
Ref: whatsnew/3 11 os592830
Ref: 60c592830
Ref: whatsnew/3 11 whatsnew311-os592830
Ref: 60d592830
Ref: os<3>-Footnote-1593088
Node: pathlib<4>593153
Ref: whatsnew/3 11 pathlib593246
Ref: 60e593246
Ref: whatsnew/3 11 whatsnew311-pathlib593246
Ref: 60f593246
Ref: pathlib<4>-Footnote-1593576
Ref: pathlib<4>-Footnote-2593641
Node: re<3>593706
Ref: whatsnew/3 11 re593803
Ref: 612593803
Ref: whatsnew/3 11 whatsnew311-re593803
Ref: 613593803
Ref: re<3>-Footnote-1594164
Node: shutil<3>594230
Ref: whatsnew/3 11 shutil594323
Ref: 614594323
Ref: whatsnew/3 11 whatsnew311-shutil594323
Ref: 615594323
Ref: shutil<3>-Footnote-1594525
Node: socket594590
Ref: whatsnew/3 11 socket594688
Ref: 616594688
Ref: whatsnew/3 11 whatsnew311-socket594688
Ref: 617594688
Ref: socket-Footnote-1595112
Ref: socket-Footnote-2595177
Node: sqlite3<4>595242
Ref: whatsnew/3 11 sqlite3595337
Ref: 619595337
Ref: whatsnew/3 11 whatsnew311-sqlite3595337
Ref: 61a595337
Ref: sqlite3<4>-Footnote-1597871
Ref: sqlite3<4>-Footnote-2597936
Ref: sqlite3<4>-Footnote-3598001
Ref: sqlite3<4>-Footnote-4598066
Ref: sqlite3<4>-Footnote-5598131
Ref: sqlite3<4>-Footnote-6598196
Ref: sqlite3<4>-Footnote-7598261
Ref: sqlite3<4>-Footnote-8598326
Ref: sqlite3<4>-Footnote-9598391
Ref: sqlite3<4>-Footnote-10598456
Ref: sqlite3<4>-Footnote-11598522
Node: string598588
Ref: whatsnew/3 11 string598683
Ref: 629598683
Ref: whatsnew/3 11 whatsnew311-string598683
Ref: 62a598683
Ref: string-Footnote-1599031
Node: sys<3>599086
Ref: whatsnew/3 11 sys599180
Ref: 62e599180
Ref: whatsnew/3 11 whatsnew311-sys599180
Ref: 62f599180
Ref: sys<3>-Footnote-1599868
Ref: sys<3>-Footnote-2599933
Ref: sys<3>-Footnote-3599998
Node: sysconfig600053
Ref: whatsnew/3 11 sysconfig600152
Ref: 633600152
Ref: whatsnew/3 11 whatsnew311-sysconfig600152
Ref: 634600152
Ref: sysconfig-Footnote-1600900
Node: tempfile<3>600965
Ref: whatsnew/3 11 tempfile601070
Ref: 637601070
Ref: whatsnew/3 11 whatsnew311-tempfile601070
Ref: 638601070
Ref: tempfile<3>-Footnote-1601465
Node: threading<2>601520
Ref: whatsnew/3 11 threading601623
Ref: 63c601623
Ref: whatsnew/3 11 whatsnew311-threading601623
Ref: 63d601623
Ref: threading<2>-Footnote-1602135
Node: time<2>602200
Ref: whatsnew/3 11 time602302
Ref: 640602302
Ref: whatsnew/3 11 whatsnew311-time602302
Ref: 641602302
Ref: time<2>-Footnote-1603115
Ref: time<2>-Footnote-2603180
Ref: time<2>-Footnote-3603277
Ref: time<2>-Footnote-4603342
Node: tkinter<3>603407
Ref: whatsnew/3 11 tkinter603509
Ref: 643603509
Ref: whatsnew/3 11 whatsnew311-tkinter603509
Ref: 644603509
Ref: tkinter<3>-Footnote-1603803
Node: traceback<2>603858
Ref: whatsnew/3 11 traceback603962
Ref: 646603962
Ref: whatsnew/3 11 whatsnew311-traceback603962
Ref: 647603962
Ref: traceback<2>-Footnote-1604445
Ref: traceback<2>-Footnote-2604510
Node: typing<4>604575
Ref: whatsnew/3 11 typing604683
Ref: 64a604683
Ref: whatsnew/3 11 whatsnew311-typing604683
Ref: 64b604683
Ref: typing<4>-Footnote-1607962
Ref: typing<4>-Footnote-2608017
Ref: typing<4>-Footnote-3608072
Ref: typing<4>-Footnote-4608127
Ref: typing<4>-Footnote-5608182
Ref: typing<4>-Footnote-6608247
Ref: typing<4>-Footnote-7608302
Ref: typing<4>-Footnote-8608357
Ref: typing<4>-Footnote-9608412
Ref: typing<4>-Footnote-10608467
Ref: typing<4>-Footnote-11608523
Ref: typing<4>-Footnote-12608579
Ref: typing<4>-Footnote-13608635
Ref: typing<4>-Footnote-14608691
Ref: typing<4>-Footnote-15608747
Node: unicodedata<3>608803
Ref: whatsnew/3 11 unicodedata608910
Ref: 65a608910
Ref: whatsnew/3 11 whatsnew311-unicodedata608910
Ref: 65b608910
Ref: unicodedata<3>-Footnote-1609103
Node: unittest<4>609168
Ref: whatsnew/3 11 unittest609273
Ref: 65c609273
Ref: whatsnew/3 11 whatsnew311-unittest609273
Ref: 65d609273
Ref: unittest<4>-Footnote-1609676
Node: venv<2>609741
Ref: whatsnew/3 11 venv609843
Ref: 662609843
Ref: whatsnew/3 11 whatsnew311-venv609843
Ref: 663609843
Ref: venv<2>-Footnote-1610366
Node: warnings<2>610431
Ref: whatsnew/3 11 warnings610529
Ref: 664610529
Ref: whatsnew/3 11 whatsnew311-warnings610529
Ref: 665610529
Ref: warnings<2>-Footnote-1610872
Node: zipfile610937
Ref: whatsnew/3 11 whatsnew311-zipfile611019
Ref: 667611019
Ref: whatsnew/3 11 zipfile611019
Ref: 668611019
Ref: zipfile-Footnote-1611621
Ref: zipfile-Footnote-2611686
Ref: zipfile-Footnote-3611741
Node: 最佳化<2>611796
Ref: whatsnew/3 11 optimizations611928
Ref: 66f611928
Ref: whatsnew/3 11 whatsnew311-optimizations611928
Ref: 670611928
Ref: 最佳化<2>-Footnote-1614368
Ref: 最佳化<2>-Footnote-2614433
Ref: 最佳化<2>-Footnote-3614488
Ref: 最佳化<2>-Footnote-4614543
Ref: 最佳化<2>-Footnote-5614598
Ref: 最佳化<2>-Footnote-6614663
Ref: 最佳化<2>-Footnote-7614718
Ref: 最佳化<2>-Footnote-8614783
Ref: 最佳化<2>-Footnote-9614838
Node: 更快的 CPython614903
Ref: whatsnew/3 11 faster-cpython615046
Ref: 67a615046
Ref: whatsnew/3 11 whatsnew311-faster-cpython615046
Ref: 544615046
Ref: 更快的 CPython-Footnote-1615614
Ref: 更快的 CPython-Footnote-2615662
Node: 更快的啟動615728
Ref: whatsnew/3 11 faster-startup615827
Ref: 67d615827
Ref: whatsnew/3 11 whatsnew311-faster-startup615827
Ref: 67b615827
Node: 凍結引入 Frozen imports / 靜態程式碼物件 Static code objects616033
Ref: whatsnew/3 11 frozen-imports-static-code-objects616156
Ref: 67e616156
Ref: whatsnew/3 11 whatsnew311-faster-imports616156
Ref: 67f616156
Node: 更快的運行程式617065
Ref: whatsnew/3 11 faster-runtime617179
Ref: 681617179
Ref: whatsnew/3 11 whatsnew311-faster-runtime617179
Ref: 67c617179
Node: 所需資源更少 cheaper 且惰性的 lazy Python 幀 frame617451
Ref: whatsnew/3 11 cheaper-lazy-python-frames617605
Ref: 682617605
Ref: whatsnew/3 11 whatsnew311-lazy-python-frames617605
Ref: 683617605
Ref: whatsnew/3 11 inline-calls618574
Ref: 686618574
Ref: 所需資源更少 cheaper 且惰性的 lazy Python 幀 frame-Footnote-1618612
Node: 行內 Python 函式呼叫618677
Ref: whatsnew/3 11 inlined-python-function-calls618877
Ref: 687618877
Ref: whatsnew/3 11 whatsnew311-inline-calls618877
Ref: 688618877
Ref: 行內 Python 函式呼叫-Footnote-1619796
Node: PEP 659：特化的適應性直譯器619861
Ref: whatsnew/3 11 pep-659-specializing-adaptive-interpreter619991
Ref: 689619991
Ref: whatsnew/3 11 whatsnew311-pep659619991
Ref: 15f619991
Ref: PEP 659：特化的適應性直譯器-Footnote-1627054
Ref: PEP 659：特化的適應性直譯器-Footnote-2627096
Ref: PEP 659：特化的適應性直譯器-Footnote-3627138
Ref: PEP 659：特化的適應性直譯器-Footnote-4627263
Node: 雜項627472
Ref: whatsnew/3 11 misc627574
Ref: 68a627574
Ref: whatsnew/3 11 whatsnew311-faster-cpython-misc627574
Ref: 68b627574
Ref: 雜項-Footnote-1628597
Ref: 雜項-Footnote-2628662
Ref: 雜項-Footnote-3628727
Ref: 雜項-Footnote-4628792
Ref: 雜項-Footnote-5628857
Ref: 雜項-Footnote-6628928
Node: FAQ628983
Ref: whatsnew/3 11 faq629070
Ref: 68d629070
Ref: whatsnew/3 11 whatsnew311-faster-cpython-faq629070
Ref: 68e629070
Node: 我該如何在程式碼中獲取這些加速？629356
Ref: whatsnew/3 11 faster-cpython-faq-my-code629498
Ref: 68f629498
Ref: whatsnew/3 11 how-should-i-write-my-code-to-utilize-these-speedups629498
Ref: 690629498
Node: Python 3 11 會不會使用更多記憶體？629815
Ref: whatsnew/3 11 faster-cpython-faq-memory630029
Ref: 691630029
Ref: whatsnew/3 11 will-cpython-3-11-use-more-memory630029
Ref: 692630029
Node: 我在我的程式當中沒感覺到任何加速，為什麼？630292
Ref: whatsnew/3 11 faster-cpython-ymmv630487
Ref: 693630487
Ref: whatsnew/3 11 i-don-t-see-any-speedups-in-my-workload-why630487
Ref: 694630487
Node: 有用到 JIT 編譯器嗎？631069
Ref: whatsnew/3 11 faster-cpython-jit631210
Ref: 695631210
Ref: whatsnew/3 11 is-there-a-jit-compiler631210
Ref: 696631210
Node: 關於631334
Ref: whatsnew/3 11 about631406
Ref: 697631406
Ref: whatsnew/3 11 whatsnew311-faster-cpython-about631406
Ref: 698631406
Node: CPython 位元組碼變更<2>631738
Ref: whatsnew/3 11 cpython-bytecode-changes631881
Ref: 69a631881
Ref: whatsnew/3 11 whatsnew311-bytecode-changes631881
Ref: 69b631881
Node: 新增 opcode632446
Ref: whatsnew/3 11 new-opcodes632562
Ref: 69d632562
Ref: whatsnew/3 11 whatsnew311-added-opcodes632562
Ref: 69e632562
Ref: 新增 opcode-Footnote-1633369
Node: 被取代的操作碼 opcode633411
Ref: whatsnew/3 11 replaced-opcodes633565
Ref: 6a8633565
Ref: whatsnew/3 11 whatsnew311-replaced-opcodes633565
Ref: 6a9633565
Ref: whatsnew/3 11 whatsnew311-changed-opcodes636316
Ref: 6b2636316
Ref: whatsnew/3 11 whatsnew311-removed-opcodes636316
Ref: 6b3636316
Ref: 被取代的操作碼 opcode-Footnote-1636352
Node: 有更動/被移除的 opcode636577
Ref: whatsnew/3 11 changed-removed-opcodes636709
Ref: 6b4636709
Ref: whatsnew/3 11 whatsnew311-changed-removed-opcodes636709
Ref: 6b5636709
Ref: whatsnew/3 11 whatsnew311-deprecated637291
Ref: 6b8637291
Ref: 有更動/被移除的 opcode-Footnote-1637328
Node: 已棄用<3>637383
Ref: whatsnew/3 11 deprecated637548
Ref: 6b9637548
Ref: whatsnew/3 11 whatsnew311-python-api-deprecated637548
Ref: 6ba637548
Ref: whatsnew/3 11 whatsnew311-deprecated-language637694
Ref: 6bc637694
Node: 語言/內建637754
Ref: whatsnew/3 11 language-builtins637831
Ref: 6bd637831
Ref: whatsnew/3 11 whatsnew311-deprecated-builtins637831
Ref: 6be637831
Ref: 語言/內建-Footnote-1639098
Ref: 語言/內建-Footnote-2639163
Ref: 語言/內建-Footnote-3639218
Ref: 語言/內建-Footnote-4639273
Node: 模組639338
Ref: whatsnew/3 11 modules639439
Ref: 6c2639439
Ref: whatsnew/3 11 whatsnew311-deprecated-modules639439
Ref: 6c3639439
Ref: whatsnew/3 11 whatsnew311-pep594639470
Ref: 550639470
Ref: 模組-Footnote-1641660
Ref: 模組-Footnote-2641702
Ref: 模組-Footnote-3641767
Ref: 模組-Footnote-4641822
Ref: 模組-Footnote-5641887
Ref: 模組-Footnote-6641929
Ref: 模組-Footnote-7641994
Node: 標準函式庫642059
Ref: whatsnew/3 11 standard-library642138
Ref: 6c4642138
Ref: whatsnew/3 11 whatsnew311-deprecated-stdlib642138
Ref: 6c5642138
Ref: whatsnew/3 11 whatsnew311-pending-removal646780
Ref: 6ca646780
Ref: 標準函式庫-Footnote-1646817
Ref: 標準函式庫-Footnote-2646882
Ref: 標準函式庫-Footnote-3646947
Ref: 標準函式庫-Footnote-4647002
Ref: 標準函式庫-Footnote-5647057
Ref: 標準函式庫-Footnote-6647112
Ref: 標準函式庫-Footnote-7647167
Ref: 標準函式庫-Footnote-8647232
Ref: 標準函式庫-Footnote-9647287
Ref: 標準函式庫-Footnote-10647342
Ref: 標準函式庫-Footnote-11647408
Ref: 標準函式庫-Footnote-12647473
Node: Python 3 12 中待決議的移除項目647529
Ref: whatsnew/3 11 pending-removal-in-python-3-12647677
Ref: 6cb647677
Ref: whatsnew/3 11 whatsnew311-python-api-pending-removal647677
Ref: 6cc647677
Ref: whatsnew/3 11 whatsnew311-removed653277
Ref: 6d1653277
Node: 已移除<3>653277
Ref: whatsnew/3 11 removed653434
Ref: 6d2653434
Ref: whatsnew/3 11 whatsnew311-python-api-removed653434
Ref: 6d3653434
Ref: whatsnew/3 11 whatsnew311-porting657907
Ref: 6e0657907
Ref: 已移除<3>-Footnote-1657944
Ref: 已移除<3>-Footnote-2658009
Ref: 已移除<3>-Footnote-3658074
Ref: 已移除<3>-Footnote-4658139
Ref: 已移除<3>-Footnote-5658204
Ref: 已移除<3>-Footnote-6658269
Ref: 已移除<3>-Footnote-7658334
Ref: 已移除<3>-Footnote-8658399
Ref: 已移除<3>-Footnote-9658464
Ref: 已移除<3>-Footnote-10658529
Ref: 已移除<3>-Footnote-11658595
Ref: 已移除<3>-Footnote-12658661
Ref: 已移除<3>-Footnote-13658727
Ref: 已移除<3>-Footnote-14658793
Ref: 已移除<3>-Footnote-15658835
Node: 移植至 Python 3 11658889
Ref: whatsnew/3 11 porting-to-python-3-11659022
Ref: 6e1659022
Ref: whatsnew/3 11 whatsnew311-python-api-porting659022
Ref: 6e2659022
Ref: 移植至 Python 3 11-Footnote-1662020
Ref: 移植至 Python 3 11-Footnote-2662085
Ref: 移植至 Python 3 11-Footnote-3662140
Ref: 移植至 Python 3 11-Footnote-4662205
Ref: 移植至 Python 3 11-Footnote-5662270
Ref: 移植至 Python 3 11-Footnote-6662335
Ref: 移植至 Python 3 11-Footnote-7662400
Ref: 移植至 Python 3 11-Footnote-8662465
Node: 建置變更<2>662530
Ref: whatsnew/3 11 build-changes662666
Ref: 6ed662666
Ref: whatsnew/3 11 whatsnew311-build-changes662666
Ref: 6ee662666
Ref: 建置變更<2>-Footnote-1666779
Ref: 建置變更<2>-Footnote-2666821
Ref: 建置變更<2>-Footnote-3666870
Ref: 建置變更<2>-Footnote-4666903
Ref: 建置變更<2>-Footnote-5666935
Ref: 建置變更<2>-Footnote-6666961
Ref: 建置變更<2>-Footnote-7666990
Ref: 建置變更<2>-Footnote-8667045
Ref: 建置變更<2>-Footnote-9667100
Ref: 建置變更<2>-Footnote-10667155
Ref: 建置變更<2>-Footnote-11667199
Ref: 建置變更<2>-Footnote-12667283
Ref: 建置變更<2>-Footnote-13667349
Ref: 建置變更<2>-Footnote-14667415
Ref: 建置變更<2>-Footnote-15667481
Ref: 建置變更<2>-Footnote-16667529
Ref: 建置變更<2>-Footnote-17667595
Ref: 建置變更<2>-Footnote-18667661
Ref: 建置變更<2>-Footnote-19667689
Ref: 建置變更<2>-Footnote-20667755
Ref: 建置變更<2>-Footnote-21667818
Ref: 建置變更<2>-Footnote-22667846
Ref: 建置變更<2>-Footnote-23667912
Ref: 建置變更<2>-Footnote-24667978
Ref: 建置變更<2>-Footnote-25668044
Ref: 建置變更<2>-Footnote-26668110
Ref: 建置變更<2>-Footnote-27668160
Ref: 建置變更<2>-Footnote-28668226
Ref: 建置變更<2>-Footnote-29668292
Ref: 建置變更<2>-Footnote-30668358
Ref: 建置變更<2>-Footnote-31668424
Ref: 建置變更<2>-Footnote-32668490
Ref: 建置變更<2>-Footnote-33668556
Node: C API 變更<2>668622
Ref: whatsnew/3 11 c-api-changes668762
Ref: 6f2668762
Ref: whatsnew/3 11 whatsnew311-c-api668762
Ref: 6f3668762
Node: 新增特性<4>669036
Ref: whatsnew/3 11 id5669136
Ref: 6f4669136
Ref: whatsnew/3 11 whatsnew311-c-api-new-features669136
Ref: 6f5669136
Ref: 新增特性<4>-Footnote-1672075
Ref: 新增特性<4>-Footnote-2672140
Ref: 新增特性<4>-Footnote-3672205
Ref: 新增特性<4>-Footnote-4672270
Ref: 新增特性<4>-Footnote-5672335
Ref: 新增特性<4>-Footnote-6672400
Ref: 新增特性<4>-Footnote-7672465
Ref: 新增特性<4>-Footnote-8672530
Ref: 新增特性<4>-Footnote-9672595
Node: 移植至 Python 3 11<2>672650
Ref: whatsnew/3 11 id6672771
Ref: 718672771
Ref: whatsnew/3 11 whatsnew311-c-api-porting672771
Ref: 6e3672771
Ref: whatsnew/3 11 whatsnew311-pep670672831
Ref: 552672831
Ref: whatsnew/3 11 pyframeobject-3-11-hiding680173
Ref: 72c680173
Ref: 移植至 Python 3 11<2>-Footnote-1686049
Ref: 移植至 Python 3 11<2>-Footnote-2686112
Ref: 移植至 Python 3 11<2>-Footnote-3686154
Ref: 移植至 Python 3 11<2>-Footnote-4686209
Ref: 移植至 Python 3 11<2>-Footnote-5686274
Ref: 移植至 Python 3 11<2>-Footnote-6686339
Ref: 移植至 Python 3 11<2>-Footnote-7686404
Ref: 移植至 Python 3 11<2>-Footnote-8686446
Ref: 移植至 Python 3 11<2>-Footnote-9686511
Ref: 移植至 Python 3 11<2>-Footnote-10686566
Ref: 移植至 Python 3 11<2>-Footnote-11686622
Ref: 移植至 Python 3 11<2>-Footnote-12686688
Ref: 移植至 Python 3 11<2>-Footnote-13686731
Ref: 移植至 Python 3 11<2>-Footnote-14686797
Ref: 移植至 Python 3 11<2>-Footnote-15686863
Ref: 移植至 Python 3 11<2>-Footnote-16686929
Ref: 移植至 Python 3 11<2>-Footnote-17686995
Ref: 移植至 Python 3 11<2>-Footnote-18687061
Ref: 移植至 Python 3 11<2>-Footnote-19687127
Ref: 移植至 Python 3 11<2>-Footnote-20687183
Ref: 移植至 Python 3 11<2>-Footnote-21687236
Ref: 移植至 Python 3 11<2>-Footnote-22687302
Ref: 移植至 Python 3 11<2>-Footnote-23687368
Ref: 移植至 Python 3 11<2>-Footnote-24687421
Node: 已棄用<4>687454
Ref: whatsnew/3 11 id7687602
Ref: 735687602
Ref: whatsnew/3 11 whatsnew311-c-api-deprecated687602
Ref: 6bb687602
Ref: 已棄用<4>-Footnote-1688514
Ref: 已棄用<4>-Footnote-2688569
Node: Python 3 12 中待決議的移除項目<2>688634
Ref: whatsnew/3 11 id8688770
Ref: 737688770
Ref: whatsnew/3 11 whatsnew311-c-api-pending-removal688770
Ref: 6cd688770
Node: 已移除<4>689515
Ref: whatsnew/3 11 id9689630
Ref: 739689630
Ref: whatsnew/3 11 whatsnew311-c-api-removed689630
Ref: 6d4689630
Ref: whatsnew/3 11 whatsnew311-pep624691895
Ref: 551691895
Ref: 已移除<4>-Footnote-1692803
Ref: 已移除<4>-Footnote-2692868
Ref: 已移除<4>-Footnote-3692933
Ref: 已移除<4>-Footnote-4692998
Ref: 已移除<4>-Footnote-5693063
Ref: 已移除<4>-Footnote-6693128
Ref: 已移除<4>-Footnote-7693193
Ref: 已移除<4>-Footnote-8693258
Ref: 已移除<4>-Footnote-9693323
Ref: 已移除<4>-Footnote-10693388
Ref: 已移除<4>-Footnote-11693431
Ref: 已移除<4>-Footnote-12693491
Node: Notable changes in 3 11 4693557
Ref: whatsnew/3 11 notable-changes-in-3-11-4693707
Ref: 73f693707
Node: tarfile693796
Ref: whatsnew/3 11 tarfile693865
Ref: 740693865
Ref: tarfile-Footnote-1694469
Node: Notable changes in 3 11 5694511
Ref: whatsnew/3 11 notable-changes-in-3-11-5694637
Ref: 741694637
Node: OpenSSL694726
Ref: whatsnew/3 11 openssl694795
Ref: 742694795
Node: Python 3 10 有什麼新功能694914
Ref: whatsnew/3 10 doc695086
Ref: 743695086
Ref: whatsnew/3 10 what-s-new-in-python-3-10695086
Ref: 744695086
Node: 摘要 -- 發布重點696008
Ref: whatsnew/3 10 summary-release-highlights696115
Ref: 745696115
Ref: 摘要 -- 發布重點-Footnote-1697309
Ref: 摘要 -- 發布重點-Footnote-2697351
Ref: 摘要 -- 發布重點-Footnote-3697393
Ref: 摘要 -- 發布重點-Footnote-4697435
Ref: 摘要 -- 發布重點-Footnote-5697500
Ref: 摘要 -- 發布重點-Footnote-6697542
Ref: 摘要 -- 發布重點-Footnote-7697584
Ref: 摘要 -- 發布重點-Footnote-8697626
Ref: 摘要 -- 發布重點-Footnote-9697668
Ref: 摘要 -- 發布重點-Footnote-10697710
Ref: 摘要 -- 發布重點-Footnote-11697753
Ref: 摘要 -- 發布重點-Footnote-12697796
Ref: 摘要 -- 發布重點-Footnote-13697839
Ref: 摘要 -- 發布重點-Footnote-14697882
Ref: 摘要 -- 發布重點-Footnote-15697925
Node: 新功能697968
Ref: whatsnew/3 10 new-features698117
Ref: 746698117
Node: 帶括號的情境管理器698364
Ref: whatsnew/3 10 parenthesized-context-managers698467
Ref: 747698467
Ref: whatsnew/3 10 whatsnew310-pep563698467
Ref: 748698467
Ref: 帶括號的情境管理器-Footnote-1699617
Ref: 帶括號的情境管理器-Footnote-2699659
Ref: 帶括號的情境管理器-Footnote-3699724
Node: 更好的錯誤訊息699789
Ref: whatsnew/3 10 better-error-messages699953
Ref: 749699953
Node: SyntaxErrors700091
Ref: whatsnew/3 10 syntaxerrors700187
Ref: 74a700187
Ref: SyntaxErrors-Footnote-1705355
Ref: SyntaxErrors-Footnote-2705420
Ref: SyntaxErrors-Footnote-3705485
Ref: SyntaxErrors-Footnote-4705550
Ref: SyntaxErrors-Footnote-5705615
Ref: SyntaxErrors-Footnote-6705680
Ref: SyntaxErrors-Footnote-7705745
Ref: SyntaxErrors-Footnote-8705810
Ref: SyntaxErrors-Footnote-9705875
Ref: SyntaxErrors-Footnote-10705940
Ref: SyntaxErrors-Footnote-11706006
Node: IndentationErrors706072
Ref: whatsnew/3 10 indentationerrors706192
Ref: 74b706192
Node: AttributeErrors706573
Ref: whatsnew/3 10 attributeerrors706691
Ref: 74d706691
Ref: AttributeErrors-Footnote-1707412
Node: NameErrors707477
Ref: whatsnew/3 10 nameerrors707569
Ref: 74e707569
Ref: NameErrors-Footnote-1708363
Node: PEP 626：用於除錯和其他工具的精確列號708428
Ref: whatsnew/3 10 pep-626-precise-line-numbers-for-debugging-and-other-tools708593
Ref: 74f708593
Node: PEP 634：結構模式匹配709218
Ref: whatsnew/3 10 pep-634-structural-pattern-matching709416
Ref: 751709416
Node: 語法和操作710173
Ref: whatsnew/3 10 syntax-and-operations710298
Ref: 752710298
Node: 宣告式方法 Declarative approach711351
Ref: whatsnew/3 10 declarative-approach711518
Ref: 753711518
Node: 簡單模式：與字面值匹配712657
Ref: whatsnew/3 10 simple-pattern-match-to-a-literal712842
Ref: 754712842
Node: 沒有萬用字元 wildcard 的行為714163
Ref: whatsnew/3 10 behavior-without-the-wildcard714270
Ref: 755714270
Node: 具有字面值和變數的模式714908
Ref: whatsnew/3 10 patterns-with-a-literal-and-variable715072
Ref: 756715072
Node: 模式和類別715994
Ref: whatsnew/3 10 patterns-and-classes716137
Ref: 757716137
Node: 具有位置參數的模式716960
Ref: whatsnew/3 10 patterns-with-positional-parameters717039
Ref: 758717039
Node: 巢狀模式717541
Ref: whatsnew/3 10 nested-patterns717678
Ref: 759717678
Node: 複雜模式和萬用字元718306
Ref: whatsnew/3 10 complex-patterns-and-the-wildcard718433
Ref: 75a718433
Node: Guard718998
Ref: whatsnew/3 10 guard719131
Ref: 75b719131
Node: 其他主要功能719596
Ref: whatsnew/3 10 other-key-features719693
Ref: 75c719693
Ref: 其他主要功能-Footnote-1721853
Ref: 其他主要功能-Footnote-2721895
Ref: 其他主要功能-Footnote-3721937
Node: 可選的 EncodingWarning 和 encoding="locale" 選項721979
Ref: whatsnew/3 10 optional-encodingwarning-and-encoding-locale-option722116
Ref: 75d722116
Ref: whatsnew/3 10 whatsnew310-pep597722116
Ref: 75e722116
Node: 與型別提示相關的新功能723016
Ref: whatsnew/3 10 new-feat-related-type-hints723164
Ref: 762723164
Ref: whatsnew/3 10 new-features-related-to-type-hints723164
Ref: 763723164
Ref: 與型別提示相關的新功能-Footnote-1723556
Node: PEP 604：新型聯集運算子723598
Ref: whatsnew/3 10 pep-604-new-type-union-operator723736
Ref: 764723736
Ref: PEP 604：新型聯集運算子-Footnote-1724804
Ref: PEP 604：新型聯集運算子-Footnote-2724846
Ref: PEP 604：新型聯集運算子-Footnote-3724911
Node: PEP 612：參數規範變數724976
Ref: whatsnew/3 10 pep-612-parameter-specification-variables725155
Ref: 767725155
Ref: PEP 612：參數規範變數-Footnote-1726429
Ref: PEP 612：參數規範變數-Footnote-2726471
Ref: PEP 612：參數規範變數-Footnote-3726513
Ref: PEP 612：參數規範變數-Footnote-4726578
Node: PEP 613：型別別名 TypeAlias726643
Ref: whatsnew/3 10 pep-613-typealias726831
Ref: 76c726831
Ref: PEP 613：型別別名 TypeAlias-Footnote-1727684
Ref: PEP 613：型別別名 TypeAlias-Footnote-2727726
Ref: PEP 613：型別別名 TypeAlias-Footnote-3727768
Node: PEP 647：使用者定義的型別防護727833
Ref: whatsnew/3 10 pep-647-user-defined-type-guards727984
Ref: 76e727984
Ref: PEP 647：使用者定義的型別防護-Footnote-1728491
Ref: PEP 647：使用者定義的型別防護-Footnote-2728533
Node: 其他語言更動<3>728598
Ref: whatsnew/3 10 other-language-changes728746
Ref: 76f728746
Ref: 其他語言更動<3>-Footnote-1733459
Ref: 其他語言更動<3>-Footnote-2733524
Ref: 其他語言更動<3>-Footnote-3733589
Ref: 其他語言更動<3>-Footnote-4733631
Ref: 其他語言更動<3>-Footnote-5733696
Ref: 其他語言更動<3>-Footnote-6733761
Ref: 其他語言更動<3>-Footnote-7733826
Ref: 其他語言更動<3>-Footnote-8733891
Ref: 其他語言更動<3>-Footnote-9733956
Ref: 其他語言更動<3>-Footnote-10733998
Ref: 其他語言更動<3>-Footnote-11734064
Ref: 其他語言更動<3>-Footnote-12734130
Ref: 其他語言更動<3>-Footnote-13734196
Ref: 其他語言更動<3>-Footnote-14734262
Ref: 其他語言更動<3>-Footnote-15734328
Ref: 其他語言更動<3>-Footnote-16734394
Node: 新模組734460
Ref: whatsnew/3 10 new-modules734593
Ref: 77f734593
Node: 改進的模組<3>734636
Ref: whatsnew/3 10 improved-modules734760
Ref: 780734760
Node: asyncio<4>735836
Ref: whatsnew/3 10 asyncio735921
Ref: 781735921
Ref: asyncio<4>-Footnote-1736103
Node: argparse<2>736168
Ref: whatsnew/3 10 argparse736270
Ref: 782736270
Ref: argparse<2>-Footnote-1736584
Node: array<3>736648
Ref: whatsnew/3 10 array736763
Ref: 783736763
Ref: array<3>-Footnote-1737008
Node: asynchat asyncore smtpd737073
Ref: whatsnew/3 10 asynchat-asyncore-smtpd737186
Ref: 785737186
Node: base64<2>737409
Ref: whatsnew/3 10 base64737517
Ref: 786737517
Node: bdb737727
Ref: whatsnew/3 10 bdb737818
Ref: 789737818
Ref: bdb-Footnote-1737998
Node: bisect738063
Ref: whatsnew/3 10 bisect738151
Ref: 78a738151
Ref: bisect-Footnote-1738348
Node: codecs738412
Ref: whatsnew/3 10 codecs738512
Ref: 78b738512
Ref: codecs-Footnote-1738735
Node: collections abc738800
Ref: whatsnew/3 10 collections-abc738907
Ref: 78d738907
Ref: collections abc-Footnote-1739862
Node: contextlib<2>739927
Ref: whatsnew/3 10 contextlib740034
Ref: 790740034
Ref: contextlib<2>-Footnote-1740559
Ref: contextlib<2>-Footnote-2740624
Node: curses740689
Ref: whatsnew/3 10 curses740795
Ref: 794740795
Ref: curses-Footnote-1741464
Ref: curses-Footnote-2741529
Node: dataclasses<2>741594
Ref: whatsnew/3 10 dataclasses741699
Ref: 79a741699
Node: __slots__741856
Ref: whatsnew/3 10 slots741966
Ref: 79b741966
Ref: __slots__-Footnote-1742176
Node: 僅限關鍵字欄位 Keyword-only fields742241
Ref: whatsnew/3 10 keyword-only-fields742351
Ref: 79c742351
Ref: 僅限關鍵字欄位 Keyword-only fields-Footnote-1743865
Node: distutils<2>743930
Ref: whatsnew/3 10 distutils744039
Ref: 79d744039
Ref: whatsnew/3 10 distutils-deprecated744039
Ref: 6ce744039
Ref: distutils<2>-Footnote-1744905
Ref: distutils<2>-Footnote-2744947
Node: doctest<2>745012
Ref: whatsnew/3 10 doctest745116
Ref: 79e745116
Ref: doctest<2>-Footnote-1745318
Node: encodings745383
Ref: whatsnew/3 10 encodings745482
Ref: 79f745482
Ref: encodings-Footnote-1745673
Node: enum<3>745738
Ref: whatsnew/3 10 enum745836
Ref: 7a0745836
Ref: enum<3>-Footnote-1746335
Ref: enum<3>-Footnote-2746400
Node: fileinput746465
Ref: whatsnew/3 10 fileinput746566
Ref: 7a2746566
Ref: fileinput-Footnote-1747031
Ref: fileinput-Footnote-2747096
Node: faulthandler747160
Ref: whatsnew/3 10 faulthandler747259
Ref: 7a5747259
Ref: faulthandler-Footnote-1747523
Node: gc<2>747588
Ref: whatsnew/3 10 gc747685
Ref: 7a6747685
Ref: gc<2>-Footnote-1747937
Node: glob<2>748002
Ref: whatsnew/3 10 glob748097
Ref: 7aa748097
Ref: glob<2>-Footnote-1748343
Node: hashlib<3>748408
Ref: whatsnew/3 10 hashlib748502
Ref: 7ac748502
Ref: hashlib<3>-Footnote-1749018
Ref: hashlib<3>-Footnote-2749060
Ref: hashlib<3>-Footnote-3749125
Ref: hashlib<3>-Footnote-4749190
Node: hmac749255
Ref: whatsnew/3 10 hmac749358
Ref: 7ad749358
Ref: hmac-Footnote-1749540
Node: IDLE 和 idlelib749605
Ref: whatsnew/3 10 idle-and-idlelib749719
Ref: 7ae749719
Ref: IDLE 和 idlelib-Footnote-1751894
Ref: IDLE 和 idlelib-Footnote-2751959
Ref: IDLE 和 idlelib-Footnote-3752024
Ref: IDLE 和 idlelib-Footnote-4752089
Ref: IDLE 和 idlelib-Footnote-5752154
Ref: IDLE 和 idlelib-Footnote-6752219
Ref: IDLE 和 idlelib-Footnote-7752284
Ref: IDLE 和 idlelib-Footnote-8752349
Node: importlib metadata<2>752404
Ref: whatsnew/3 10 importlib-metadata752524
Ref: 7b3752524
Ref: importlib metadata<2>-Footnote-1753094
Node: inspect<3>753167
Ref: whatsnew/3 10 inspect753283
Ref: 7b6753283
Ref: inspect<3>-Footnote-1754462
Ref: inspect<3>-Footnote-2754527
Node: itertools<3>754592
Ref: whatsnew/3 10 itertools754696
Ref: 7b8754696
Ref: itertools<3>-Footnote-1754872
Node: linecache754937
Ref: whatsnew/3 10 linecache755036
Ref: 7ba755036
Ref: linecache-Footnote-1755242
Node: os<4>755307
Ref: whatsnew/3 10 os755404
Ref: 7bb755404
Ref: os<4>-Footnote-1756246
Ref: os<4>-Footnote-2756311
Ref: os<4>-Footnote-3756376
Ref: os<4>-Footnote-4756441
Node: os path<3>756506
Ref: whatsnew/3 10 os-path756604
Ref: 7c2756604
Ref: os path<3>-Footnote-1756944
Node: pathlib<5>757009
Ref: whatsnew/3 10 pathlib757110
Ref: 7c3757110
Ref: pathlib<5>-Footnote-1757831
Ref: pathlib<5>-Footnote-2757896
Ref: pathlib<5>-Footnote-3757961
Ref: pathlib<5>-Footnote-4758026
Node: platform758091
Ref: whatsnew/3 10 platform758188
Ref: 7c9758188
Ref: platform-Footnote-1758457
Ref: platform-Footnote-2758530
Node: pprint758595
Ref: whatsnew/3 10 pprint758692
Ref: 7cb758692
Ref: pprint-Footnote-1759044
Ref: pprint-Footnote-2759109
Node: py_compile759174
Ref: whatsnew/3 10 py-compile759269
Ref: 7cd759269
Ref: py_compile-Footnote-1759484
Node: pyclbr759549
Ref: whatsnew/3 10 pyclbr759644
Ref: 7ce759644
Ref: pyclbr-Footnote-1759991
Node: shelve760056
Ref: whatsnew/3 10 shelve760154
Ref: 7d1760154
Ref: shelve-Footnote-1760430
Node: statistics<3>760495
Ref: whatsnew/3 10 statistics760594
Ref: 7d3760594
Ref: statistics<3>-Footnote-1760852
Node: site<2>760917
Ref: whatsnew/3 10 site761019
Ref: 7d6761019
Ref: site<2>-Footnote-1761215
Node: socket<2>761280
Ref: whatsnew/3 10 socket761375
Ref: 7d7761375
Ref: socket<2>-Footnote-1761839
Ref: socket<2>-Footnote-2761904
Node: ssl<3>761969
Ref: whatsnew/3 10 ssl762067
Ref: 7da762067
Ref: ssl<3>-Footnote-1763834
Ref: ssl<3>-Footnote-2763876
Ref: ssl<3>-Footnote-3763941
Ref: ssl<3>-Footnote-4764006
Ref: ssl<3>-Footnote-5764071
Ref: ssl<3>-Footnote-6764136
Ref: ssl<3>-Footnote-7764201
Ref: ssl<3>-Footnote-8764266
Ref: ssl<3>-Footnote-9764331
Ref: ssl<3>-Footnote-10764396
Ref: ssl<3>-Footnote-11764462
Ref: ssl<3>-Footnote-12764528
Ref: ssl<3>-Footnote-13764594
Ref: ssl<3>-Footnote-14764660
Ref: ssl<3>-Footnote-15764726
Node: sqlite3<5>764792
Ref: whatsnew/3 10 sqlite3764887
Ref: 7e1764887
Ref: sqlite3<5>-Footnote-1765136
Node: sys<4>765201
Ref: whatsnew/3 10 sys765297
Ref: 7e3765297
Ref: sys<4>-Footnote-1765678
Ref: sys<4>-Footnote-2765743
Node: _thread765808
Ref: whatsnew/3 10 thread765906
Ref: 7e6765906
Ref: _thread-Footnote-1766178
Node: threading<3>766243
Ref: whatsnew/3 10 threading766347
Ref: 7e9766347
Ref: threading<3>-Footnote-1766872
Ref: threading<3>-Footnote-2766937
Node: traceback<3>767002
Ref: whatsnew/3 10 traceback767107
Ref: 7f0767107
Ref: traceback<3>-Footnote-1767425
Node: types<3>767490
Ref: whatsnew/3 10 types767592
Ref: 7f4767592
Ref: types<3>-Footnote-1767891
Node: typing<5>767956
Ref: whatsnew/3 10 typing768057
Ref: 7f8768057
Ref: typing<5>-Footnote-1770249
Ref: typing<5>-Footnote-2770291
Ref: typing<5>-Footnote-3770356
Ref: typing<5>-Footnote-4770421
Ref: typing<5>-Footnote-5770486
Node: unittest<5>770551
Ref: whatsnew/3 10 unittest770656
Ref: 7fb770656
Ref: unittest<5>-Footnote-1770869
Node: urllib parse770934
Ref: whatsnew/3 10 urllib-parse771036
Ref: 7fe771036
Ref: urllib parse-Footnote-1772184
Ref: urllib parse-Footnote-2772249
Ref: urllib parse-Footnote-3772308
Node: xml<2>772363
Ref: whatsnew/3 10 xml772466
Ref: 7ff772466
Ref: xml<2>-Footnote-1772687
Node: zipimport<3>772752
Ref: whatsnew/3 10 zipimport772834
Ref: 801772834
Ref: zipimport<3>-Footnote-1773236
Ref: zipimport<3>-Footnote-2773278
Ref: zipimport<3>-Footnote-3773343
Node: 最佳化<3>773408
Ref: whatsnew/3 10 optimizations773535
Ref: 805773535
Ref: 最佳化<3>-Footnote-1777030
Ref: 最佳化<3>-Footnote-2777095
Ref: 最佳化<3>-Footnote-3777160
Ref: 最佳化<3>-Footnote-4777225
Ref: 最佳化<3>-Footnote-5777290
Ref: 最佳化<3>-Footnote-6777355
Ref: 最佳化<3>-Footnote-7777476
Ref: 最佳化<3>-Footnote-8777541
Ref: 最佳化<3>-Footnote-9777606
Ref: 最佳化<3>-Footnote-10777671
Ref: 最佳化<3>-Footnote-11777737
Ref: 最佳化<3>-Footnote-12777803
Ref: 最佳化<3>-Footnote-13777846
Ref: 最佳化<3>-Footnote-14777912
Ref: 最佳化<3>-Footnote-15777978
Ref: 最佳化<3>-Footnote-16778044
Ref: 最佳化<3>-Footnote-17778110
Ref: 最佳化<3>-Footnote-18778176
Node: 已棄用<5>778242
Ref: whatsnew/3 10 deprecated778360
Ref: 80c778360
Ref: whatsnew/3 10 whatsnew310-deprecated778360
Ref: 7df778360
Ref: 已棄用<5>-Footnote-1787483
Ref: 已棄用<5>-Footnote-2787548
Ref: 已棄用<5>-Footnote-3787613
Ref: 已棄用<5>-Footnote-4787678
Ref: 已棄用<5>-Footnote-5787743
Ref: 已棄用<5>-Footnote-6787808
Ref: 已棄用<5>-Footnote-7787873
Ref: 已棄用<5>-Footnote-8787938
Ref: 已棄用<5>-Footnote-9788003
Ref: 已棄用<5>-Footnote-10788068
Ref: 已棄用<5>-Footnote-11788134
Ref: 已棄用<5>-Footnote-12788200
Ref: 已棄用<5>-Footnote-13788266
Ref: 已棄用<5>-Footnote-14788332
Ref: 已棄用<5>-Footnote-15788391
Ref: 已棄用<5>-Footnote-16788457
Ref: 已棄用<5>-Footnote-17788513
Ref: 已棄用<5>-Footnote-18788579
Ref: 已棄用<5>-Footnote-19788645
Ref: 已棄用<5>-Footnote-20788711
Node: 已刪除788777
Ref: whatsnew/3 10 removed788904
Ref: 818788904
Ref: whatsnew/3 10 whatsnew310-removed788904
Ref: 819788904
Ref: 已刪除-Footnote-1792022
Ref: 已刪除-Footnote-2792087
Ref: 已刪除-Footnote-3792152
Ref: 已刪除-Footnote-4792217
Ref: 已刪除-Footnote-5792282
Ref: 已刪除-Footnote-6792347
Ref: 已刪除-Footnote-7792412
Node: 移植到 Python 3 10792477
Ref: whatsnew/3 10 porting-to-python-3-10792621
Ref: 81e792621
Node: Python 語法的變化792857
Ref: whatsnew/3 10 changes-in-the-python-syntax792966
Ref: 81f792966
Ref: Python 語法的變化-Footnote-1793502
Node: Python API 的變化793567
Ref: whatsnew/3 10 changes-in-the-python-api793703
Ref: 820793703
Ref: whatsnew/3 10 changes-python-api793703
Ref: 81d793703
Ref: Python API 的變化-Footnote-1796541
Ref: Python API 的變化-Footnote-2796606
Ref: Python API 的變化-Footnote-3796671
Ref: Python API 的變化-Footnote-4796736
Ref: Python API 的變化-Footnote-5796801
Ref: Python API 的變化-Footnote-6796866
Node: C API 中的改動796931
Ref: whatsnew/3 10 changes-in-the-c-api797036
Ref: 828797036
Node: CPython 位元組碼變更<3>799410
Ref: whatsnew/3 10 cpython-bytecode-changes799560
Ref: 82e799560
Ref: CPython 位元組碼變更<3>-Footnote-1799823
Node: 建置變更<3>799888
Ref: whatsnew/3 10 build-changes800032
Ref: 82f800032
Ref: 建置變更<3>-Footnote-1802467
Ref: 建置變更<3>-Footnote-2802509
Ref: 建置變更<3>-Footnote-3802574
Ref: 建置變更<3>-Footnote-4802639
Ref: 建置變更<3>-Footnote-5802704
Ref: 建置變更<3>-Footnote-6802769
Ref: 建置變更<3>-Footnote-7802834
Ref: 建置變更<3>-Footnote-8802899
Ref: 建置變更<3>-Footnote-9802964
Ref: 建置變更<3>-Footnote-10803029
Ref: 建置變更<3>-Footnote-11803095
Node: C API 變更<3>803161
Ref: whatsnew/3 10 c-api-changes803310
Ref: 834803310
Node: PEP 652：維護穩定 ABI803522
Ref: whatsnew/3 10 pep-652-maintaining-the-stable-abi803621
Ref: 835803621
Ref: PEP 652：維護穩定 ABI-Footnote-1804008
Ref: PEP 652：維護穩定 ABI-Footnote-2804050
Node: 新功能<2>804115
Ref: whatsnew/3 10 id1804247
Ref: 836804247
Ref: 新功能<2>-Footnote-1808745
Ref: 新功能<2>-Footnote-2808810
Ref: 新功能<2>-Footnote-3808875
Ref: 新功能<2>-Footnote-4808940
Ref: 新功能<2>-Footnote-5809005
Ref: 新功能<2>-Footnote-6809070
Ref: 新功能<2>-Footnote-7809135
Ref: 新功能<2>-Footnote-8809202
Ref: 新功能<2>-Footnote-9809267
Ref: 新功能<2>-Footnote-10809332
Ref: 新功能<2>-Footnote-11809398
Ref: 新功能<2>-Footnote-12809464
Ref: 新功能<2>-Footnote-13809530
Ref: 新功能<2>-Footnote-14809596
Ref: 新功能<2>-Footnote-15809662
Ref: 新功能<2>-Footnote-16809728
Ref: 新功能<2>-Footnote-17809794
Node: 移植到 Python 3 10<2>809860
Ref: whatsnew/3 10 id2809978
Ref: 84b809978
Ref: 移植到 Python 3 10<2>-Footnote-1813736
Ref: 移植到 Python 3 10<2>-Footnote-2813778
Ref: 移植到 Python 3 10<2>-Footnote-3813843
Ref: 移植到 Python 3 10<2>-Footnote-4813908
Ref: 移植到 Python 3 10<2>-Footnote-5813973
Ref: 移植到 Python 3 10<2>-Footnote-6814038
Ref: 移植到 Python 3 10<2>-Footnote-7814103
Ref: 移植到 Python 3 10<2>-Footnote-8814168
Ref: 移植到 Python 3 10<2>-Footnote-9814233
Ref: 移植到 Python 3 10<2>-Footnote-10814298
Ref: 移植到 Python 3 10<2>-Footnote-11814364
Node: 已棄用<6>814430
Ref: whatsnew/3 10 id3814548
Ref: 855814548
Ref: 已棄用<6>-Footnote-1814830
Node: 已刪除<2>814895
Ref: whatsnew/3 10 id4814980
Ref: 857814980
Ref: 已刪除<2>-Footnote-1819945
Ref: 已刪除<2>-Footnote-2820010
Ref: 已刪除<2>-Footnote-3820052
Ref: 已刪除<2>-Footnote-4820117
Ref: 已刪除<2>-Footnote-5820182
Ref: 已刪除<2>-Footnote-6820247
Ref: 已刪除<2>-Footnote-7820312
Ref: 已刪除<2>-Footnote-8820377
Ref: 已刪除<2>-Footnote-9820442
Ref: 已刪除<2>-Footnote-10820484
Ref: 已刪除<2>-Footnote-11820550
Ref: 已刪除<2>-Footnote-12820616
Ref: 已刪除<2>-Footnote-13820682
Ref: 已刪除<2>-Footnote-14820748
Ref: 已刪除<2>-Footnote-15820814
Ref: 已刪除<2>-Footnote-16820880
Node: Notable security feature in 3 10 7820946
Ref: whatsnew/3 10 notable-security-feature-in-3-10-7821114
Ref: 864821114
Ref: Notable security feature in 3 10 7-Footnote-1821844
Node: Notable security feature in 3 10 8821914
Ref: whatsnew/3 10 notable-security-feature-in-3-10-8822093
Ref: 865822093
Ref: Notable security feature in 3 10 8-Footnote-1822515
Node: Notable changes in 3 10 12822570
Ref: whatsnew/3 10 notable-changes-in-3-10-12822706
Ref: 866822706
Node: tarfile<2>822808
Ref: whatsnew/3 10 tarfile822881
Ref: 867822881
Ref: tarfile<2>-Footnote-1823485
Node: Python 3 9 有什麼新功能823527
Ref: whatsnew/3 9 doc823698
Ref: 868823698
Ref: whatsnew/3 9 what-s-new-in-python-3-9823698
Ref: 869823698
Ref: Python 3 9 有什麼新功能-Footnote-1824918
Node: Summary -- Release highlights824960
Ref: whatsnew/3 9 summary-release-highlights825116
Ref: 86a825116
Ref: Summary -- Release highlights-Footnote-1827065
Ref: Summary -- Release highlights-Footnote-2827107
Ref: Summary -- Release highlights-Footnote-3827149
Ref: Summary -- Release highlights-Footnote-4827191
Ref: Summary -- Release highlights-Footnote-5827233
Ref: Summary -- Release highlights-Footnote-6827275
Ref: Summary -- Release highlights-Footnote-7827317
Ref: Summary -- Release highlights-Footnote-8827359
Ref: Summary -- Release highlights-Footnote-9827401
Ref: Summary -- Release highlights-Footnote-10827443
Node: You should check for DeprecationWarning in your code827486
Ref: whatsnew/3 9 you-should-check-for-deprecationwarning-in-your-code827666
Ref: 86b827666
Node: New Features<3>829358
Ref: whatsnew/3 9 new-features829530
Ref: 871829530
Node: Dictionary Merge & Update Operators829739
Ref: whatsnew/3 9 dictionary-merge-update-operators829885
Ref: 872829885
Ref: Dictionary Merge & Update Operators-Footnote-1830641
Ref: Dictionary Merge & Update Operators-Footnote-2830683
Node: New String Methods to Remove Prefixes and Suffixes830748
Ref: whatsnew/3 9 new-string-methods-to-remove-prefixes-and-suffixes830948
Ref: 873830948
Ref: New String Methods to Remove Prefixes and Suffixes-Footnote-1831459
Ref: New String Methods to Remove Prefixes and Suffixes-Footnote-2831501
Node: Type Hinting Generics in Standard Collections831566
Ref: whatsnew/3 9 type-hinting-generics-in-standard-collections831741
Ref: 876831741
Ref: Type Hinting Generics in Standard Collections-Footnote-1832444
Ref: Type Hinting Generics in Standard Collections-Footnote-2832486
Node: New Parser832551
Ref: whatsnew/3 9 new-parser832667
Ref: 877832667
Ref: New Parser-Footnote-1833598
Ref: New Parser-Footnote-2833663
Ref: New Parser-Footnote-3833711
Ref: New Parser-Footnote-4833753
Node: 其他語言更動<4>833818
Ref: whatsnew/3 9 other-language-changes833950
Ref: 878833950
Ref: 其他語言更動<4>-Footnote-1837041
Ref: 其他語言更動<4>-Footnote-2837106
Ref: 其他語言更動<4>-Footnote-3837171
Ref: 其他語言更動<4>-Footnote-4837236
Ref: 其他語言更動<4>-Footnote-5837301
Ref: 其他語言更動<4>-Footnote-6837343
Ref: 其他語言更動<4>-Footnote-7837408
Ref: 其他語言更動<4>-Footnote-8837473
Ref: 其他語言更動<4>-Footnote-9837538
Ref: 其他語言更動<4>-Footnote-10837603
Ref: 其他語言更動<4>-Footnote-11837669
Node: 新模組<2>837735
Ref: whatsnew/3 9 new-modules837870
Ref: 882837870
Node: zoneinfo837936
Ref: whatsnew/3 9 zoneinfo838010
Ref: 883838010
Ref: zoneinfo-Footnote-1839104
Ref: zoneinfo-Footnote-2839145
Node: graphlib839187
Ref: whatsnew/3 9 graphlib839261
Ref: 885839261
Ref: graphlib-Footnote-1839585
Node: 改進的模組<4>839650
Ref: whatsnew/3 9 improved-modules839776
Ref: 887839776
Node: ast<2>840564
Ref: whatsnew/3 9 ast840644
Ref: 888840644
Ref: ast<2>-Footnote-1841312
Ref: ast<2>-Footnote-2841377
Ref: ast<2>-Footnote-3841442
Node: asyncio<5>841507
Ref: whatsnew/3 9 asyncio841609
Ref: 88b841609
Ref: asyncio<5>-Footnote-1843336
Ref: asyncio<5>-Footnote-2843401
Ref: asyncio<5>-Footnote-3843466
Ref: asyncio<5>-Footnote-4843531
Ref: asyncio<5>-Footnote-5843596
Ref: asyncio<5>-Footnote-6843661
Node: compileall<2>843726
Ref: whatsnew/3 9 compileall843843
Ref: 890843843
Ref: compileall<2>-Footnote-1844423
Ref: compileall<2>-Footnote-2844488
Node: concurrent futures<2>844553
Ref: whatsnew/3 9 concurrent-futures844669
Ref: 891844669
Ref: concurrent futures<2>-Footnote-1845548
Ref: concurrent futures<2>-Footnote-2845613
Ref: concurrent futures<2>-Footnote-3845678
Node: curses<2>845743
Ref: whatsnew/3 9 curses845857
Ref: 894845857
Ref: curses<2>-Footnote-1846131
Node: datetime<2>846196
Ref: whatsnew/3 9 datetime846301
Ref: 899846301
Ref: datetime<2>-Footnote-1846619
Node: distutils<3>846684
Ref: whatsnew/3 9 distutils846788
Ref: 89c846788
Ref: distutils<3>-Footnote-1847039
Node: fcntl<2>847104
Ref: whatsnew/3 9 fcntl847206
Ref: 89d847206
Ref: fcntl<2>-Footnote-1847394
Node: ftplib<2>847459
Ref: whatsnew/3 9 ftplib847554
Ref: 89e847554
Ref: ftplib<2>-Footnote-1847844
Node: gc<3>847909
Ref: whatsnew/3 9 gc848006
Ref: 8a1848006
Ref: gc<3>-Footnote-1848544
Ref: gc<3>-Footnote-2848609
Node: hashlib<4>848674
Ref: whatsnew/3 9 hashlib848766
Ref: 8a3848766
Ref: hashlib<4>-Footnote-1849275
Ref: hashlib<4>-Footnote-2849340
Node: http849405
Ref: whatsnew/3 9 http849508
Ref: 8a4849508
Ref: http-Footnote-1849780
Ref: http-Footnote-2849845
Node: IDLE and idlelib849910
Ref: whatsnew/3 9 idle-and-idlelib850010
Ref: 8a6850010
Ref: IDLE and idlelib-Footnote-1851218
Ref: IDLE and idlelib-Footnote-2851282
Ref: IDLE and idlelib-Footnote-3851347
Ref: IDLE and idlelib-Footnote-4851412
Ref: IDLE and idlelib-Footnote-5851477
Ref: IDLE and idlelib-Footnote-6851542
Ref: IDLE and idlelib-Footnote-7851607
Node: imaplib851672
Ref: whatsnew/3 9 imaplib851780
Ref: 8a7851780
Ref: imaplib-Footnote-1852614
Ref: imaplib-Footnote-2852679
Node: importlib<3>852744
Ref: whatsnew/3 9 importlib852846
Ref: 8ae852846
Ref: importlib<3>-Footnote-1853638
Ref: importlib<3>-Footnote-2853703
Ref: importlib<3>-Footnote-3853768
Node: inspect<4>853833
Ref: whatsnew/3 9 inspect853940
Ref: 8b0853940
Ref: inspect<4>-Footnote-1854172
Ref: inspect<4>-Footnote-2854237
Node: ipaddress<2>854302
Ref: whatsnew/3 9 ipaddress854404
Ref: 8b2854404
Ref: ipaddress<2>-Footnote-1854969
Ref: ipaddress<2>-Footnote-2855034
Node: math<4>855099
Ref: whatsnew/3 9 math855209
Ref: 8b4855209
Ref: math<4>-Footnote-1855925
Ref: math<4>-Footnote-2855990
Ref: math<4>-Footnote-3856055
Ref: math<4>-Footnote-4856120
Ref: math<4>-Footnote-5856185
Node: multiprocessing<2>856250
Ref: whatsnew/3 9 multiprocessing856355
Ref: 8b8856355
Ref: multiprocessing<2>-Footnote-1856611
Node: nntplib856676
Ref: whatsnew/3 9 nntplib856779
Ref: 8bb856779
Ref: nntplib-Footnote-1857063
Node: os<5>857128
Ref: whatsnew/3 9 os857223
Ref: 8bc857223
Ref: os<5>-Footnote-1857979
Ref: os<5>-Footnote-2858044
Ref: os<5>-Footnote-3858109
Ref: os<5>-Footnote-4858174
Ref: os<5>-Footnote-5858239
Ref: os<5>-Footnote-6858304
Node: pathlib<6>858369
Ref: whatsnew/3 9 pathlib858463
Ref: 8c3858463
Ref: pathlib<6>-Footnote-1858677
Node: pdb<3>858742
Ref: whatsnew/3 9 pdb858837
Ref: 8c6858837
Ref: pdb<3>-Footnote-1859025
Node: poplib859090
Ref: whatsnew/3 9 poplib859184
Ref: 8c8859184
Ref: poplib-Footnote-1859478
Node: pprint<2>859543
Ref: whatsnew/3 9 pprint859636
Ref: 8cb859636
Ref: pprint<2>-Footnote-1859832
Node: pydoc859897
Ref: whatsnew/3 9 pydoc859993
Ref: 8cc859993
Ref: pydoc-Footnote-1860253
Node: random<3>860318
Ref: whatsnew/3 9 random860411
Ref: 8cd860411
Ref: random<3>-Footnote-1860603
Node: signal860668
Ref: whatsnew/3 9 signal860763
Ref: 8ce860763
Ref: signal-Footnote-1860993
Node: smtplib861058
Ref: whatsnew/3 9 smtplib861153
Ref: 8d0861153
Ref: smtplib-Footnote-1861565
Ref: smtplib-Footnote-2861630
Node: socket<3>861695
Ref: whatsnew/3 9 socket861791
Ref: 8d4861791
Ref: socket<3>-Footnote-1862377
Ref: socket<3>-Footnote-2862442
Ref: socket<3>-Footnote-3862507
Node: time<3>862572
Ref: whatsnew/3 9 time862667
Ref: 8d9862667
Ref: time<3>-Footnote-1862997
Node: sys<5>863062
Ref: whatsnew/3 9 sys863159
Ref: 8db863159
Ref: sys<5>-Footnote-1863824
Ref: sys<5>-Footnote-2863891
Node: tracemalloc863956
Ref: whatsnew/3 9 tracemalloc864055
Ref: 8de864055
Ref: tracemalloc-Footnote-1864339
Node: typing<6>864404
Ref: whatsnew/3 9 typing864511
Ref: 8e0864511
Ref: typing<6>-Footnote-1864867
Node: unicodedata<4>864909
Ref: whatsnew/3 9 unicodedata865012
Ref: 8e2865012
Ref: unicodedata<4>-Footnote-1865165
Node: venv<3>865230
Ref: whatsnew/3 9 venv865330
Ref: 8e3865330
Ref: venv<3>-Footnote-1865791
Node: xml<3>865856
Ref: whatsnew/3 9 xml865933
Ref: 8e4865933
Ref: xml<3>-Footnote-1866291
Node: 最佳化<4>866356
Ref: whatsnew/3 9 optimizations866482
Ref: 8e5866482
Ref: 最佳化<4>-Footnote-1872234
Ref: 最佳化<4>-Footnote-2872299
Ref: 最佳化<4>-Footnote-3872364
Ref: 最佳化<4>-Footnote-4872429
Ref: 最佳化<4>-Footnote-5872494
Ref: 最佳化<4>-Footnote-6872536
Ref: 最佳化<4>-Footnote-7872601
Ref: 最佳化<4>-Footnote-8872665
Ref: 最佳化<4>-Footnote-9872730
Ref: 最佳化<4>-Footnote-10872795
Ref: 最佳化<4>-Footnote-11872861
Ref: 最佳化<4>-Footnote-12872990
Node: 已棄用<7>873039
Ref: whatsnew/3 9 deprecated873159
Ref: 8ea873159
Ref: 已棄用<7>-Footnote-1878191
Ref: 已棄用<7>-Footnote-2878256
Ref: 已棄用<7>-Footnote-3878321
Ref: 已棄用<7>-Footnote-4878386
Ref: 已棄用<7>-Footnote-5878451
Ref: 已棄用<7>-Footnote-6878516
Ref: 已棄用<7>-Footnote-7878581
Ref: 已棄用<7>-Footnote-8878646
Ref: 已棄用<7>-Footnote-9878711
Ref: 已棄用<7>-Footnote-10878776
Ref: 已棄用<7>-Footnote-11878842
Ref: 已棄用<7>-Footnote-12878908
Ref: 已棄用<7>-Footnote-13878974
Ref: 已棄用<7>-Footnote-14879040
Ref: 已棄用<7>-Footnote-15879106
Ref: 已棄用<7>-Footnote-16879149
Ref: 已棄用<7>-Footnote-17879189
Ref: 已棄用<7>-Footnote-18879228
Ref: 已棄用<7>-Footnote-19879294
Node: 已移除<5>879360
Ref: whatsnew/3 9 removed879489
Ref: 8ec879489
Ref: whatsnew/3 9 removed-in-python-39879489
Ref: 870879489
Ref: 已移除<5>-Footnote-1885634
Ref: 已移除<5>-Footnote-2885699
Ref: 已移除<5>-Footnote-3885764
Ref: 已移除<5>-Footnote-4885829
Ref: 已移除<5>-Footnote-5885894
Ref: 已移除<5>-Footnote-6885959
Ref: 已移除<5>-Footnote-7886024
Ref: 已移除<5>-Footnote-8886089
Ref: 已移除<5>-Footnote-9886154
Ref: 已移除<5>-Footnote-10886219
Ref: 已移除<5>-Footnote-11886285
Ref: 已移除<5>-Footnote-12886328
Ref: 已移除<5>-Footnote-13886394
Ref: 已移除<5>-Footnote-14886460
Ref: 已移除<5>-Footnote-15886526
Ref: 已移除<5>-Footnote-16886592
Ref: 已移除<5>-Footnote-17886658
Ref: 已移除<5>-Footnote-18886724
Ref: 已移除<5>-Footnote-19886790
Ref: 已移除<5>-Footnote-20886856
Ref: 已移除<5>-Footnote-21886922
Ref: 已移除<5>-Footnote-22886988
Node: Porting to Python 3 9887054
Ref: whatsnew/3 9 porting-to-python-3-9887186
Ref: 8fc887186
Node: Changes in the Python API<2>887527
Ref: whatsnew/3 9 changes-in-the-python-api887643
Ref: 8fd887643
Ref: Changes in the Python API<2>-Footnote-1891830
Ref: Changes in the Python API<2>-Footnote-2891895
Ref: Changes in the Python API<2>-Footnote-3891960
Ref: Changes in the Python API<2>-Footnote-4892025
Ref: Changes in the Python API<2>-Footnote-5892084
Ref: Changes in the Python API<2>-Footnote-6892149
Ref: Changes in the Python API<2>-Footnote-7892214
Ref: Changes in the Python API<2>-Footnote-8892279
Ref: Changes in the Python API<2>-Footnote-9892344
Ref: Changes in the Python API<2>-Footnote-10892409
Ref: Changes in the Python API<2>-Footnote-11892475
Node: C API 中的改動<2>892541
Ref: whatsnew/3 9 changes-in-the-c-api892695
Ref: 908892695
Ref: C API 中的改動<2>-Footnote-1894806
Ref: C API 中的改動<2>-Footnote-2894871
Ref: C API 中的改動<2>-Footnote-3894936
Node: CPython 位元組碼變更<4>895001
Ref: whatsnew/3 9 cpython-bytecode-changes895118
Ref: 90a895118
Ref: CPython 位元組碼變更<4>-Footnote-1895925
Ref: CPython 位元組碼變更<4>-Footnote-2895990
Node: 建置變更<4>896055
Ref: whatsnew/3 9 build-changes896190
Ref: 90e896190
Ref: 建置變更<4>-Footnote-1898598
Ref: 建置變更<4>-Footnote-2898665
Ref: 建置變更<4>-Footnote-3898730
Ref: 建置變更<4>-Footnote-4898795
Ref: 建置變更<4>-Footnote-5898860
Ref: 建置變更<4>-Footnote-6898925
Ref: 建置變更<4>-Footnote-7898990
Ref: 建置變更<4>-Footnote-8899055
Node: C API 變更<4>899120
Ref: whatsnew/3 9 c-api-changes899265
Ref: 910899265
Node: New Features<4>899425
Ref: whatsnew/3 9 id1899525
Ref: 911899525
Ref: New Features<4>-Footnote-1902532
Ref: New Features<4>-Footnote-2902574
Ref: New Features<4>-Footnote-3902639
Ref: New Features<4>-Footnote-4902704
Ref: New Features<4>-Footnote-5902769
Ref: New Features<4>-Footnote-6902834
Ref: New Features<4>-Footnote-7902899
Ref: New Features<4>-Footnote-8902964
Ref: New Features<4>-Footnote-9903029
Ref: New Features<4>-Footnote-10903094
Node: Porting to Python 3 9<2>903160
Ref: whatsnew/3 9 id2903281
Ref: 91d903281
Ref: Porting to Python 3 9<2>-Footnote-1907108
Ref: Porting to Python 3 9<2>-Footnote-2907150
Ref: Porting to Python 3 9<2>-Footnote-3907215
Ref: Porting to Python 3 9<2>-Footnote-4907280
Ref: Porting to Python 3 9<2>-Footnote-5907344
Ref: Porting to Python 3 9<2>-Footnote-6907409
Ref: Porting to Python 3 9<2>-Footnote-7907474
Ref: Porting to Python 3 9<2>-Footnote-8907516
Ref: Porting to Python 3 9<2>-Footnote-9907581
Ref: Porting to Python 3 9<2>-Footnote-10907646
Ref: Porting to Python 3 9<2>-Footnote-11907712
Node: 已移除<6>907778
Ref: whatsnew/3 9 id3907875
Ref: 930907875
Ref: 已移除<6>-Footnote-1911807
Ref: 已移除<6>-Footnote-2911872
Ref: 已移除<6>-Footnote-3911937
Ref: 已移除<6>-Footnote-4912002
Ref: 已移除<6>-Footnote-5912067
Ref: 已移除<6>-Footnote-6912132
Ref: 已移除<6>-Footnote-7912197
Ref: 已移除<6>-Footnote-8912262
Ref: 已移除<6>-Footnote-9912327
Ref: 已移除<6>-Footnote-10912369
Ref: 已移除<6>-Footnote-11912435
Node: Python 3 9 1 中顯著的變更912501
Ref: whatsnew/3 9 notable-changes-in-python-3-9-1912662
Ref: 933912662
Node: typing<7>912870
Ref: whatsnew/3 9 id4913004
Ref: 934913004
Ref: typing<7>-Footnote-1914202
Ref: typing<7>-Footnote-2914244
Node: macOS 11 0 Big Sur and Apple Silicon Mac support914309
Ref: whatsnew/3 9 macos-11-0-big-sur-and-apple-silicon-mac-support914443
Ref: 935914443
Ref: macOS 11 0 Big Sur and Apple Silicon Mac support-Footnote-1915253
Node: Python 3 9 2 中顯著的變更915318
Ref: whatsnew/3 9 notable-changes-in-python-3-9-2915495
Ref: 936915495
Node: collections abc<2>915650
Ref: whatsnew/3 9 collections-abc915760
Ref: 937915760
Ref: collections abc<2>-Footnote-1916739
Node: urllib parse<2>916804
Ref: whatsnew/3 9 urllib-parse916914
Ref: 938916914
Ref: urllib parse<2>-Footnote-1917598
Node: Python 3 9 3 中顯著的變更917663
Ref: whatsnew/3 9 notable-changes-in-python-3-9-3917840
Ref: 939917840
Ref: Python 3 9 3 中顯著的變更-Footnote-1918305
Node: Python 3 9 5 中顯著的變更918360
Ref: whatsnew/3 9 notable-changes-in-python-3-9-5918540
Ref: 93a918540
Node: urllib parse<3>918656
Ref: whatsnew/3 9 id5918739
Ref: 93b918739
Ref: urllib parse<3>-Footnote-1919267
Ref: urllib parse<3>-Footnote-2919326
Node: Notable security feature in 3 9 14919381
Ref: whatsnew/3 9 notable-security-feature-in-3-9-14919555
Ref: 93c919555
Ref: Notable security feature in 3 9 14-Footnote-1920285
Node: Notable changes in 3 9 17920355
Ref: whatsnew/3 9 notable-changes-in-3-9-17920489
Ref: 93d920489
Node: tarfile<3>920589
Ref: whatsnew/3 9 tarfile920661
Ref: 93e920661
Ref: tarfile<3>-Footnote-1921265
Node: Python 3 8 有什麼新功能921307
Ref: whatsnew/3 8 doc921477
Ref: 93f921477
Ref: whatsnew/3 8 what-s-new-in-python-3-8921477
Ref: 940921477
Node: Summary -- Release highlights<2>922803
Ref: whatsnew/3 8 summary-release-highlights922925
Ref: 941922925
Node: New Features<5>922996
Ref: whatsnew/3 8 new-features923148
Ref: 942923148
Node: Assignment expressions923771
Ref: whatsnew/3 8 assignment-expressions923880
Ref: 943923880
Ref: Assignment expressions-Footnote-1925382
Ref: Assignment expressions-Footnote-2925479
Ref: Assignment expressions-Footnote-3925521
Node: Positional-only parameters925586
Ref: whatsnew/3 8 positional-only-parameters925757
Ref: 944925757
Ref: Positional-only parameters-Footnote-1928437
Ref: Positional-only parameters-Footnote-2928499
Ref: Positional-only parameters-Footnote-3928541
Node: Parallel filesystem cache for compiled bytecode files928606
Ref: whatsnew/3 8 parallel-filesystem-cache-for-compiled-bytecode-files928801
Ref: 946928801
Ref: Parallel filesystem cache for compiled bytecode files-Footnote-1929449
Node: Debug build uses the same ABI as release build929514
Ref: whatsnew/3 8 debug-build-uses-the-same-abi-as-release-build929749
Ref: 949929749
Ref: Debug build uses the same ABI as release build-Footnote-1932098
Ref: Debug build uses the same ABI as release build-Footnote-2932163
Ref: Debug build uses the same ABI as release build-Footnote-3932228
Ref: Debug build uses the same ABI as release build-Footnote-4932293
Node: f-strings support = for self-documenting expressions and debugging932358
Ref: whatsnew/3 8 bpo-36817-whatsnew932574
Ref: 94b932574
Ref: whatsnew/3 8 f-strings-support-for-self-documenting-expressions-and-debugging932574
Ref: 94c932574
Ref: f-strings support = for self-documenting expressions and debugging-Footnote-1933669
Node: PEP 578 Python Runtime Audit Hooks933734
Ref: whatsnew/3 8 pep-578-python-runtime-audit-hooks933947
Ref: 94e933947
Ref: PEP 578 Python Runtime Audit Hooks-Footnote-1934430
Node: PEP 587 Python Initialization Configuration934472
Ref: whatsnew/3 8 pep-587-python-initialization-configuration934673
Ref: 94f934673
Ref: PEP 587 Python Initialization Configuration-Footnote-1936660
Ref: PEP 587 Python Initialization Configuration-Footnote-2936702
Ref: PEP 587 Python Initialization Configuration-Footnote-3936744
Node: PEP 590 Vectorcall a fast calling protocol for CPython936809
Ref: whatsnew/3 8 pep-590-vectorcall-a-fast-calling-protocol-for-cpython937023
Ref: 96a937023
Ref: PEP 590 Vectorcall a fast calling protocol for CPython-Footnote-1937627
Ref: PEP 590 Vectorcall a fast calling protocol for CPython-Footnote-2937669
Node: Pickle protocol 5 with out-of-band data buffers937734
Ref: whatsnew/3 8 pickle-protocol-5-with-out-of-band-data-buffers937896
Ref: 96b937896
Ref: Pickle protocol 5 with out-of-band data buffers-Footnote-1938648
Ref: Pickle protocol 5 with out-of-band data buffers-Footnote-2938690
Ref: Pickle protocol 5 with out-of-band data buffers-Footnote-3938732
Node: 其他語言更動<5>938797
Ref: whatsnew/3 8 other-language-changes938932
Ref: 96c938932
Ref: 其他語言更動<5>-Footnote-1946312
Ref: 其他語言更動<5>-Footnote-2946377
Ref: 其他語言更動<5>-Footnote-3946442
Ref: 其他語言更動<5>-Footnote-4946507
Ref: 其他語言更動<5>-Footnote-5946572
Ref: 其他語言更動<5>-Footnote-6946637
Ref: 其他語言更動<5>-Footnote-7946702
Ref: 其他語言更動<5>-Footnote-8946767
Ref: 其他語言更動<5>-Footnote-9946832
Ref: 其他語言更動<5>-Footnote-10946897
Ref: 其他語言更動<5>-Footnote-11946963
Ref: 其他語言更動<5>-Footnote-12947031
Ref: 其他語言更動<5>-Footnote-13947097
Ref: 其他語言更動<5>-Footnote-14947167
Ref: 其他語言更動<5>-Footnote-15947227
Ref: 其他語言更動<5>-Footnote-16947293
Ref: 其他語言更動<5>-Footnote-17947359
Node: 新增模組<3>947425
Ref: whatsnew/3 8 new-modules947563
Ref: 978947563
Ref: 新增模組<3>-Footnote-1948643
Node: 改進的模組<5>948708
Ref: whatsnew/3 8 improved-modules948837
Ref: 979948837
Node: ast<3>949835
Ref: whatsnew/3 8 ast949915
Ref: 97a949915
Ref: ast<3>-Footnote-1950955
Ref: ast<3>-Footnote-2951020
Ref: ast<3>-Footnote-3951062
Ref: ast<3>-Footnote-4951104
Ref: ast<3>-Footnote-5951146
Node: asyncio<6>951211
Ref: whatsnew/3 8 asyncio951320
Ref: 97c951320
Ref: asyncio<6>-Footnote-1954474
Ref: asyncio<6>-Footnote-2954539
Ref: asyncio<6>-Footnote-3954604
Ref: asyncio<6>-Footnote-4954669
Ref: asyncio<6>-Footnote-5954734
Ref: asyncio<6>-Footnote-6954799
Ref: asyncio<6>-Footnote-7954864
Ref: asyncio<6>-Footnote-8954929
Ref: asyncio<6>-Footnote-9954994
Ref: asyncio<6>-Footnote-10955047
Node: builtins（內建）955113
Ref: whatsnew/3 8 builtins955227
Ref: 983955227
Ref: builtins（內建）-Footnote-1955746
Node: collections955811
Ref: whatsnew/3 8 collections955923
Ref: 984955923
Ref: collections-Footnote-1956445
Node: cProfile956510
Ref: whatsnew/3 8 cprofile956608
Ref: 986956608
Ref: cProfile-Footnote-1956964
Node: csv<2>957029
Ref: whatsnew/3 8 csv957125
Ref: 988957125
Ref: csv<2>-Footnote-1957442
Node: curses<3>957507
Ref: whatsnew/3 8 curses957601
Ref: 98a957601
Ref: curses<3>-Footnote-1957845
Node: ctypes957910
Ref: whatsnew/3 8 ctypes958009
Ref: 98c958009
Ref: ctypes-Footnote-1958498
Node: datetime<3>958563
Ref: whatsnew/3 8 datetime958665
Ref: 98f958665
Ref: datetime<3>-Footnote-1959098
Node: functools<2>959163
Ref: whatsnew/3 8 functools959264
Ref: 992959264
Ref: functools<2>-Footnote-1960820
Ref: functools<2>-Footnote-2960885
Ref: functools<2>-Footnote-3960950
Node: gc<4>961015
Ref: whatsnew/3 8 gc961112
Ref: 997961112
Ref: gc<4>-Footnote-1961345
Node: gettext961410
Ref: whatsnew/3 8 gettext961502
Ref: 998961502
Ref: gettext-Footnote-1961703
Node: gzip<3>961767
Ref: whatsnew/3 8 gzip961873
Ref: 99a961873
Ref: gzip<3>-Footnote-1962290
Ref: gzip<3>-Footnote-2962355
Node: IDLE and idlelib<2>962419
Ref: whatsnew/3 8 idle-and-idlelib962528
Ref: 99c962528
Ref: IDLE and idlelib<2>-Footnote-1964493
Ref: IDLE and idlelib<2>-Footnote-2964560
Ref: IDLE and idlelib<2>-Footnote-3964624
Ref: IDLE and idlelib<2>-Footnote-4964689
Ref: IDLE and idlelib<2>-Footnote-5964754
Ref: IDLE and idlelib<2>-Footnote-6964819
Ref: IDLE and idlelib<2>-Footnote-7964883
Ref: IDLE and idlelib<2>-Footnote-8964948
Node: inspect<5>965013
Ref: whatsnew/3 8 inspect965120
Ref: 99d965120
Ref: inspect<5>-Footnote-1965892
Node: io<3>965957
Ref: whatsnew/3 8 io966057
Ref: 99f966057
Ref: io<3>-Footnote-1966405
Node: itertools<4>966470
Ref: whatsnew/3 8 itertools966569
Ref: 9a0966569
Ref: itertools<4>-Footnote-1966953
Node: json tool967018
Ref: whatsnew/3 8 json-tool967122
Ref: 9a2967122
Ref: json tool-Footnote-1967329
Node: logging<2>967394
Ref: whatsnew/3 8 logging967493
Ref: 9a3967493
Ref: logging<2>-Footnote-1968208
Node: math<5>968273
Ref: whatsnew/3 8 math968370
Ref: 9a5968370
Ref: math<5>-Footnote-1970134
Ref: math<5>-Footnote-2970199
Ref: math<5>-Footnote-3970264
Ref: math<5>-Footnote-4970329
Ref: math<5>-Footnote-5970394
Ref: math<5>-Footnote-6970459
Ref: math<5>-Footnote-7970524
Ref: math<5>-Footnote-8970589
Node: mmap<2>970654
Ref: whatsnew/3 8 mmap970759
Ref: 9ab970759
Ref: mmap<2>-Footnote-1970989
Node: multiprocessing<3>971054
Ref: whatsnew/3 8 multiprocessing971157
Ref: 9ad971157
Ref: multiprocessing<3>-Footnote-1971461
Ref: multiprocessing<3>-Footnote-2971526
Node: os<6>971591
Ref: whatsnew/3 8 os971697
Ref: 9ae971697
Ref: os<6>-Footnote-1973207
Ref: os<6>-Footnote-2973272
Ref: os<6>-Footnote-3973337
Node: os path<4>973402
Ref: whatsnew/3 8 os-path973500
Ref: 9b1973500
Ref: os path<4>-Footnote-1974529
Ref: os path<4>-Footnote-2974594
Ref: os path<4>-Footnote-3974659
Node: pathlib<7>974724
Ref: whatsnew/3 8 pathlib974823
Ref: 9b9974823
Ref: pathlib<7>-Footnote-1975732
Ref: pathlib<7>-Footnote-2975797
Node: pickle975862
Ref: whatsnew/3 8 pickle975959
Ref: 9c1975959
Ref: pickle-Footnote-1976297
Node: plistlib976362
Ref: whatsnew/3 8 plistlib976458
Ref: 9c4976458
Ref: plistlib-Footnote-1976696
Node: pprint<3>976761
Ref: whatsnew/3 8 pprint976864
Ref: 9c6976864
Ref: pprint<3>-Footnote-1977935
Node: py_compile<2>978000
Ref: whatsnew/3 8 py-compile978100
Ref: 9c8978100
Ref: py_compile<2>-Footnote-1978289
Node: shlex978354
Ref: whatsnew/3 8 shlex978454
Ref: 9ca978454
Ref: shlex-Footnote-1978658
Node: shutil<4>978723
Ref: whatsnew/3 8 shutil978819
Ref: 9cc978819
Ref: shutil<4>-Footnote-1979472
Ref: shutil<4>-Footnote-2979537
Ref: shutil<4>-Footnote-3979602
Node: socket<4>979667
Ref: whatsnew/3 8 socket979764
Ref: 9ce979764
Ref: socket<4>-Footnote-1980339
Ref: socket<4>-Footnote-2980404
Node: ssl<4>980469
Ref: whatsnew/3 8 ssl980570
Ref: 9d4980570
Ref: ssl<4>-Footnote-1980832
Node: statistics<4>980897
Ref: whatsnew/3 8 statistics980995
Ref: 9d7980995
Ref: statistics<4>-Footnote-1982730
Ref: statistics<4>-Footnote-2982795
Ref: statistics<4>-Footnote-3982860
Ref: statistics<4>-Footnote-4982925
Ref: statistics<4>-Footnote-5982990
Node: sys<6>983055
Ref: whatsnew/3 8 sys983157
Ref: 9dd983157
Ref: sys<6>-Footnote-1983596
Node: tarfile<4>983661
Ref: whatsnew/3 8 tarfile983762
Ref: 9de983762
Ref: tarfile<4>-Footnote-1984180
Node: threading<4>984245
Ref: whatsnew/3 8 threading984351
Ref: 9df984351
Ref: threading<4>-Footnote-1985087
Ref: threading<4>-Footnote-2985154
Node: tokenize<2>985219
Ref: whatsnew/3 8 tokenize985325
Ref: 9e3985325
Ref: tokenize<2>-Footnote-1985650
Node: tkinter<4>985715
Ref: whatsnew/3 8 tkinter985816
Ref: 9e4985816
Ref: tkinter<4>-Footnote-1986359
Ref: tkinter<4>-Footnote-2986424
Ref: tkinter<4>-Footnote-3986489
Node: time<4>986554
Ref: whatsnew/3 8 time986653
Ref: 9e5986653
Ref: time<4>-Footnote-1986832
Node: typing<8>986897
Ref: whatsnew/3 8 typing987000
Ref: 9e7987000
Ref: typing<8>-Footnote-1988465
Ref: typing<8>-Footnote-2988507
Ref: typing<8>-Footnote-3988549
Ref: typing<8>-Footnote-4988591
Node: unicodedata<5>988633
Ref: whatsnew/3 8 unicodedata988740
Ref: 9eb988740
Ref: unicodedata<5>-Footnote-1989168
Ref: unicodedata<5>-Footnote-2989230
Ref: unicodedata<5>-Footnote-3989295
Node: unittest<6>989360
Ref: whatsnew/3 8 unittest989465
Ref: 9ed989465
Ref: unittest<6>-Footnote-1990755
Ref: unittest<6>-Footnote-2990820
Ref: unittest<6>-Footnote-3990885
Ref: unittest<6>-Footnote-4990950
Node: venv<4>991015
Ref: whatsnew/3 8 venv991113
Ref: 9f3991113
Ref: venv<4>-Footnote-1991364
Node: weakref991429
Ref: whatsnew/3 8 weakref991522
Ref: 9f4991522
Ref: weakref-Footnote-1991815
Node: xml<4>991880
Ref: whatsnew/3 8 xml991972
Ref: 9f6991972
Ref: xml<4>-Footnote-1993146
Ref: xml<4>-Footnote-2993211
Ref: xml<4>-Footnote-3993276
Ref: xml<4>-Footnote-4993341
Ref: xml<4>-Footnote-5993406
Node: xmlrpc993471
Ref: whatsnew/3 8 xmlrpc993547
Ref: 9f9993547
Ref: xmlrpc-Footnote-1993939
Node: 最佳化<5>994004
Ref: whatsnew/3 8 optimizations994141
Ref: 9fb994141
Ref: 最佳化<5>-Footnote-1998487
Ref: 最佳化<5>-Footnote-2998552
Ref: 最佳化<5>-Footnote-3998617
Ref: 最佳化<5>-Footnote-4998682
Ref: 最佳化<5>-Footnote-5998747
Ref: 最佳化<5>-Footnote-6998812
Ref: 最佳化<5>-Footnote-7998877
Ref: 最佳化<5>-Footnote-8998942
Ref: 最佳化<5>-Footnote-9999007
Ref: 最佳化<5>-Footnote-10999072
Ref: 最佳化<5>-Footnote-11999138
Ref: 最佳化<5>-Footnote-12999204
Ref: 最佳化<5>-Footnote-13999270
Node: Build and C API Changes999336
Ref: whatsnew/3 8 build-and-c-api-changes999467
Ref: a06999467
Ref: Build and C API Changes-Footnote-11005066
Ref: Build and C API Changes-Footnote-21005131
Ref: Build and C API Changes-Footnote-31005196
Ref: Build and C API Changes-Footnote-41005261
Ref: Build and C API Changes-Footnote-51005326
Ref: Build and C API Changes-Footnote-61005391
Ref: Build and C API Changes-Footnote-71005456
Ref: Build and C API Changes-Footnote-81005521
Ref: Build and C API Changes-Footnote-91005586
Ref: Build and C API Changes-Footnote-101005651
Ref: Build and C API Changes-Footnote-111005717
Ref: Build and C API Changes-Footnote-121005783
Node: 已棄用<8>1005849
Ref: whatsnew/3 8 deprecated1005992
Ref: a0f1005992
Ref: 已棄用<8>-Footnote-11011806
Ref: 已棄用<8>-Footnote-21011871
Ref: 已棄用<8>-Footnote-31011936
Ref: 已棄用<8>-Footnote-41012001
Ref: 已棄用<8>-Footnote-51012065
Ref: 已棄用<8>-Footnote-61012130
Ref: 已棄用<8>-Footnote-71012195
Ref: 已棄用<8>-Footnote-81012260
Ref: 已棄用<8>-Footnote-91012325
Ref: 已棄用<8>-Footnote-101012390
Ref: 已棄用<8>-Footnote-111012456
Ref: 已棄用<8>-Footnote-121012522
Ref: 已棄用<8>-Footnote-131012588
Node: API and Feature Removals1012654
Ref: whatsnew/3 8 api-and-feature-removals1012795
Ref: a291012795
Ref: API and Feature Removals-Footnote-11015614
Ref: API and Feature Removals-Footnote-21015679
Ref: API and Feature Removals-Footnote-31015744
Ref: API and Feature Removals-Footnote-41015809
Ref: API and Feature Removals-Footnote-51015874
Ref: API and Feature Removals-Footnote-61015939
Ref: API and Feature Removals-Footnote-71016004
Ref: API and Feature Removals-Footnote-81016069
Ref: API and Feature Removals-Footnote-91016134
Ref: API and Feature Removals-Footnote-101016199
Ref: API and Feature Removals-Footnote-111016265
Node: Porting to Python 3 81016331
Ref: whatsnew/3 8 porting-to-python-3-81016491
Ref: a2d1016491
Node: Changes in Python behavior1016902
Ref: whatsnew/3 8 changes-in-python-behavior1017023
Ref: a2e1017023
Ref: Changes in Python behavior-Footnote-11019388
Ref: Changes in Python behavior-Footnote-21019453
Ref: Changes in Python behavior-Footnote-31019518
Ref: Changes in Python behavior-Footnote-41019583
Ref: Changes in Python behavior-Footnote-51019648
Ref: Changes in Python behavior-Footnote-61019713
Node: Changes in the Python API<3>1019778
Ref: whatsnew/3 8 changes-in-the-python-api1019929
Ref: a331019929
Ref: whatsnew/3 8 bpo-36085-whatsnew1026882
Ref: a411026882
Ref: Changes in the Python API<3>-Footnote-11028542
Ref: Changes in the Python API<3>-Footnote-21028584
Ref: Changes in the Python API<3>-Footnote-31028649
Ref: Changes in the Python API<3>-Footnote-41028714
Ref: Changes in the Python API<3>-Footnote-51028779
Ref: Changes in the Python API<3>-Footnote-61028844
Ref: Changes in the Python API<3>-Footnote-71028909
Ref: Changes in the Python API<3>-Footnote-81028974
Ref: Changes in the Python API<3>-Footnote-91029039
Ref: Changes in the Python API<3>-Footnote-101029104
Ref: Changes in the Python API<3>-Footnote-111029170
Ref: Changes in the Python API<3>-Footnote-121029236
Ref: Changes in the Python API<3>-Footnote-131029302
Ref: Changes in the Python API<3>-Footnote-141029368
Ref: Changes in the Python API<3>-Footnote-151029434
Ref: Changes in the Python API<3>-Footnote-161029500
Ref: Changes in the Python API<3>-Footnote-171029566
Ref: Changes in the Python API<3>-Footnote-181029631
Ref: Changes in the Python API<3>-Footnote-191029697
Ref: Changes in the Python API<3>-Footnote-201029763
Ref: Changes in the Python API<3>-Footnote-211029829
Ref: Changes in the Python API<3>-Footnote-221029895
Ref: Changes in the Python API<3>-Footnote-231029961
Ref: Changes in the Python API<3>-Footnote-241030027
Ref: Changes in the Python API<3>-Footnote-251030093
Ref: Changes in the Python API<3>-Footnote-261030159
Ref: Changes in the Python API<3>-Footnote-271030225
Node: C API 中的改動<3>1030268
Ref: whatsnew/3 8 changes-in-the-c-api1030422
Ref: a431030422
Ref: C API 中的改動<3>-Footnote-11036275
Ref: C API 中的改動<3>-Footnote-21036340
Ref: C API 中的改動<3>-Footnote-31036405
Ref: C API 中的改動<3>-Footnote-41036470
Ref: C API 中的改動<3>-Footnote-51036535
Ref: C API 中的改動<3>-Footnote-61036600
Ref: C API 中的改動<3>-Footnote-71036665
Ref: C API 中的改動<3>-Footnote-81036730
Node: CPython 位元組碼變更<5>1036795
Ref: whatsnew/3 8 cpython-bytecode-changes1036939
Ref: a4b1036939
Ref: CPython 位元組碼變更<5>-Footnote-11038269
Ref: CPython 位元組碼變更<5>-Footnote-21038334
Ref: CPython 位元組碼變更<5>-Footnote-31038399
Ref: CPython 位元組碼變更<5>-Footnote-41038441
Node: Demos and Tools<2>1038506
Ref: whatsnew/3 8 demos-and-tools1038620
Ref: a501038620
Ref: Demos and Tools<2>-Footnote-11041915
Ref: Demos and Tools<2>-Footnote-21041980
Ref: Demos and Tools<2>-Footnote-31042108
Node: Python 3 8 1 中顯著的變更1042156
Ref: whatsnew/3 8 notable-changes-in-python-3-8-11042323
Ref: a511042323
Ref: Python 3 8 1 中顯著的變更-Footnote-11042828
Node: Python 3 8 2 中顯著的變更1042893
Ref: whatsnew/3 8 notable-changes-in-python-3-8-21043070
Ref: a521043070
Ref: Python 3 8 2 中顯著的變更-Footnote-11043386
Node: Python 3 8 3 中顯著的變更1043441
Ref: whatsnew/3 8 notable-changes-in-python-3-8-31043618
Ref: a531043618
Ref: Python 3 8 3 中顯著的變更-Footnote-11043999
Node: Python 3 8 8 中顯著的變更1044054
Ref: whatsnew/3 8 notable-changes-in-python-3-8-81044231
Ref: a541044231
Ref: Python 3 8 8 中顯著的變更-Footnote-11044943
Node: Python 3 8 9 中顯著的變更1045008
Ref: whatsnew/3 8 notable-changes-in-python-3-8-91045186
Ref: a551045186
Ref: Python 3 8 9 中顯著的變更-Footnote-11045651
Node: Python 3 8 10 中顯著的變更1045706
Ref: whatsnew/3 8 notable-changes-in-python-3-8-101045888
Ref: a561045888
Node: macOS 11 0 Big Sur and Apple Silicon Mac support<2>1046080
Ref: whatsnew/3 8 macos-11-0-big-sur-and-apple-silicon-mac-support1046200
Ref: a571046200
Ref: macOS 11 0 Big Sur and Apple Silicon Mac support<2>-Footnote-11047171
Node: Python 3 8 10 中顯著的變更<2>1047226
Ref: whatsnew/3 8 id11047409
Ref: a581047409
Node: urllib parse<4>1047527
Ref: whatsnew/3 8 urllib-parse1047614
Ref: a591047614
Ref: urllib parse<4>-Footnote-11048143
Ref: urllib parse<4>-Footnote-21048202
Node: Python 3 8 12 中顯著的變更1048267
Ref: whatsnew/3 8 notable-changes-in-python-3-8-121048452
Ref: a5a1048452
Node: Changes in the Python API<4>1048596
Ref: whatsnew/3 8 id21048693
Ref: a5b1048693
Ref: Changes in the Python API<4>-Footnote-11049304
Node: Notable security feature in 3 8 141049369
Ref: whatsnew/3 8 notable-security-feature-in-3-8-141049544
Ref: a5c1049544
Ref: Notable security feature in 3 8 14-Footnote-11050274
Node: Notable changes in 3 8 171050344
Ref: whatsnew/3 8 notable-changes-in-3-8-171050478
Ref: a5d1050478
Node: tarfile<5>1050578
Ref: whatsnew/3 8 id31050650
Ref: a5e1050650
Ref: tarfile<5>-Footnote-11051254
Node: Python 3 7 有什麼新功能1051296
Ref: whatsnew/3 7 doc1051466
Ref: a5f1051466
Ref: whatsnew/3 7 what-s-new-in-python-3-71051466
Ref: a601051466
Node: Summary -- Release Highlights<2>1052874
Ref: whatsnew/3 7 summary-release-highlights1052996
Ref: a611052996
Ref: Summary -- Release Highlights<2>-Footnote-11055127
Ref: Summary -- Release Highlights<2>-Footnote-21055207
Ref: Summary -- Release Highlights<2>-Footnote-31055243
Ref: Summary -- Release Highlights<2>-Footnote-41055279
Node: New Features<6>1055315
Ref: whatsnew/3 7 new-features1055467
Ref: a751055467
Node: PEP 563 Postponed Evaluation of Annotations1056509
Ref: whatsnew/3 7 pep-563-postponed-evaluation-of-annotations1056645
Ref: a761056645
Ref: whatsnew/3 7 whatsnew37-pep5631056645
Ref: a621056645
Ref: PEP 563 Postponed Evaluation of Annotations-Footnote-11058404
Ref: PEP 563 Postponed Evaluation of Annotations-Footnote-21058446
Ref: PEP 563 Postponed Evaluation of Annotations-Footnote-31058488
Node: PEP 538 Legacy C Locale Coercion1058530
Ref: whatsnew/3 7 pep-538-legacy-c-locale-coercion1058708
Ref: a771058708
Ref: whatsnew/3 7 whatsnew37-pep5381058708
Ref: a6c1058708
Ref: PEP 538 Legacy C Locale Coercion-Footnote-11061082
Ref: PEP 538 Legacy C Locale Coercion-Footnote-21061124
Ref: PEP 538 Legacy C Locale Coercion-Footnote-31061166
Ref: PEP 538 Legacy C Locale Coercion-Footnote-41061208
Node: PEP 540 Forced UTF-8 Runtime Mode1061250
Ref: whatsnew/3 7 pep-540-forced-utf-8-runtime-mode1061412
Ref: a7a1061412
Ref: whatsnew/3 7 whatsnew37-pep5401061412
Ref: a6d1061412
Ref: PEP 540 Forced UTF-8 Runtime Mode-Footnote-11062965
Ref: PEP 540 Forced UTF-8 Runtime Mode-Footnote-21063007
Ref: PEP 540 Forced UTF-8 Runtime Mode-Footnote-31063049
Node: PEP 553 Built-in breakpoint1063091
Ref: whatsnew/3 7 pep-553-built-in-breakpoint1063263
Ref: a7c1063263
Ref: whatsnew/3 7 whatsnew37-pep5531063263
Ref: a661063263
Ref: PEP 553 Built-in breakpoint-Footnote-11064093
Node: PEP 539 New C API for Thread-Local Storage1064135
Ref: whatsnew/3 7 pep-539-new-c-api-for-thread-local-storage1064326
Ref: a7f1064326
Ref: whatsnew/3 7 whatsnew37-pep5391064326
Ref: a711064326
Ref: PEP 539 New C API for Thread-Local Storage-Footnote-11065812
Ref: PEP 539 New C API for Thread-Local Storage-Footnote-21065854
Node: PEP 562 Customization of Access to Module Attributes1065896
Ref: whatsnew/3 7 pep-562-customization-of-access-to-module-attributes1066113
Ref: a831066113
Ref: whatsnew/3 7 whatsnew37-pep5621066113
Ref: a671066113
Ref: PEP 562 Customization of Access to Module Attributes-Footnote-11066679
Node: PEP 564 New Time Functions With Nanosecond Resolution1066721
Ref: whatsnew/3 7 pep-564-new-time-functions-with-nanosecond-resolution1066939
Ref: a841066939
Ref: whatsnew/3 7 whatsnew37-pep5641066939
Ref: a6b1066939
Ref: PEP 564 New Time Functions With Nanosecond Resolution-Footnote-11068011
Ref: PEP 564 New Time Functions With Nanosecond Resolution-Footnote-21068053
Ref: PEP 564 New Time Functions With Nanosecond Resolution-Footnote-31068130
Node: PEP 565 Show DeprecationWarning in __main__1068172
Ref: whatsnew/3 7 pep-565-show-deprecationwarning-in-main1068394
Ref: a8b1068394
Ref: whatsnew/3 7 whatsnew37-pep5651068394
Ref: a701068394
Ref: PEP 565 Show DeprecationWarning in __main__-Footnote-11070317
Node: PEP 560 Core Support for typing module and Generic Types1070359
Ref: whatsnew/3 7 pep-560-core-support-for-typing-module-and-generic-types1070556
Ref: a8c1070556
Ref: whatsnew/3 7 whatsnew37-pep5601070556
Ref: a681070556
Ref: PEP 560 Core Support for typing module and Generic Types-Footnote-11071494
Ref: PEP 560 Core Support for typing module and Generic Types-Footnote-21071536
Node: PEP 552 Hash-based pyc Files1071578
Ref: whatsnew/3 7 pep-552-hash-based-pyc-files1071761
Ref: a8d1071761
Ref: whatsnew/3 7 whatsnew37-pep5521071761
Ref: a6e1071761
Ref: PEP 552 Hash-based pyc Files-Footnote-11073416
Ref: PEP 552 Hash-based pyc Files-Footnote-21073457
Ref: PEP 552 Hash-based pyc Files-Footnote-31073499
Node: PEP 545：Python 文件翻譯1073541
Ref: whatsnew/3 7 pep-545-python-documentation-translations1073698
Ref: a8e1073698
Ref: whatsnew/3 7 whatsnew37-pep5451073698
Ref: a721073698
Ref: PEP 545：Python 文件翻譯-Footnote-11074216
Ref: PEP 545：Python 文件翻譯-Footnote-21074258
Node: Python Development Mode -X dev1074300
Ref: whatsnew/3 7 python-development-mode-x-dev1074420
Ref: a8f1074420
Ref: whatsnew/3 7 whatsnew37-devmode1074420
Ref: a6f1074420
Node: 其他語言更動<6>1074874
Ref: whatsnew/3 7 other-language-changes1075006
Ref: a911075006
Ref: 其他語言更動<6>-Footnote-11077384
Ref: 其他語言更動<6>-Footnote-21077449
Ref: 其他語言更動<6>-Footnote-31077514
Ref: 其他語言更動<6>-Footnote-41077579
Ref: 其他語言更動<6>-Footnote-51077644
Ref: 其他語言更動<6>-Footnote-61077709
Ref: 其他語言更動<6>-Footnote-71077774
Ref: 其他語言更動<6>-Footnote-81077839
Ref: 其他語言更動<6>-Footnote-91077904
Ref: 其他語言更動<6>-Footnote-101077969
Node: 新模組<3>1078035
Ref: whatsnew/3 7 new-modules1078170
Ref: a991078170
Node: contextvars1078304
Ref: whatsnew/3 7 contextvars1078387
Ref: a9a1078387
Ref: whatsnew/3 7 whatsnew37-pep5671078387
Ref: a631078387
Ref: contextvars-Footnote-11079107
Node: dataclasses<3>1079149
Ref: whatsnew/3 7 dataclasses1079263
Ref: a9c1079263
Ref: whatsnew/3 7 whatsnew37-pep5571079263
Ref: a641079263
Ref: dataclasses<3>-Footnote-11079926
Node: importlib resources<2>1079968
Ref: whatsnew/3 7 importlib-resources1080062
Ref: a9f1080062
Ref: whatsnew/3 7 whatsnew37-importlib-resources1080062
Ref: a651080062
Ref: importlib resources<2>-Footnote-11080805
Ref: importlib resources<2>-Footnote-21080870
Node: 改進的模組<6>1080932
Ref: whatsnew/3 7 improved-modules1081061
Ref: aa11081061
Node: argparse<3>1082501
Ref: whatsnew/3 7 argparse1082586
Ref: aa21082586
Ref: argparse<3>-Footnote-11082820
Node: asyncio<7>1082885
Ref: whatsnew/3 7 asyncio1082987
Ref: aa41082987
Ref: whatsnew/3 7 whatsnew37-asyncio1082987
Ref: a6a1082987
Ref: asyncio<7>-Footnote-11089284
Ref: asyncio<7>-Footnote-21089349
Ref: asyncio<7>-Footnote-31089391
Ref: asyncio<7>-Footnote-41089456
Ref: asyncio<7>-Footnote-51089521
Ref: asyncio<7>-Footnote-61089586
Ref: asyncio<7>-Footnote-71089651
Ref: asyncio<7>-Footnote-81089716
Ref: asyncio<7>-Footnote-91089781
Ref: asyncio<7>-Footnote-101089846
Ref: asyncio<7>-Footnote-111089912
Ref: asyncio<7>-Footnote-121089978
Ref: asyncio<7>-Footnote-131090044
Ref: asyncio<7>-Footnote-141090110
Ref: asyncio<7>-Footnote-151090176
Ref: asyncio<7>-Footnote-161090242
Ref: asyncio<7>-Footnote-171090308
Ref: asyncio<7>-Footnote-181090374
Ref: asyncio<7>-Footnote-191090440
Ref: asyncio<7>-Footnote-201090506
Ref: asyncio<7>-Footnote-211090572
Ref: asyncio<7>-Footnote-221090638
Ref: asyncio<7>-Footnote-231090704
Ref: asyncio<7>-Footnote-241090770
Node: binascii1090836
Ref: whatsnew/3 7 binascii1090938
Ref: ac41090938
Ref: binascii-Footnote-11091215
Node: calendar<2>1091280
Ref: whatsnew/3 7 calendar1091386
Ref: ac61091386
Ref: calendar<2>-Footnote-11091636
Node: collections<2>1091701
Ref: whatsnew/3 7 collections1091812
Ref: ac81091812
Ref: collections<2>-Footnote-11092003
Node: compileall<3>1092068
Ref: whatsnew/3 7 compileall1092189
Ref: ac91092189
Ref: compileall<3>-Footnote-11092586
Node: concurrent futures<3>1092651
Ref: whatsnew/3 7 concurrent-futures1092771
Ref: acb1092771
Ref: concurrent futures<3>-Footnote-11093213
Ref: concurrent futures<3>-Footnote-21093278
Node: contextlib<3>1093343
Ref: whatsnew/3 7 contextlib1093461
Ref: acc1093461
Ref: contextlib<3>-Footnote-11093991
Ref: contextlib<3>-Footnote-21094056
Ref: contextlib<3>-Footnote-31094121
Ref: contextlib<3>-Footnote-41094186
Node: cProfile<2>1094251
Ref: whatsnew/3 7 cprofile1094353
Ref: ad11094353
Ref: cProfile<2>-Footnote-11094579
Node: crypt1094644
Ref: whatsnew/3 7 crypt1094744
Ref: ad21094744
Ref: crypt-Footnote-11095065
Ref: crypt-Footnote-21095130
Node: datetime<4>1095195
Ref: whatsnew/3 7 datetime1095290
Ref: ad31095290
Ref: datetime<4>-Footnote-11095701
Ref: datetime<4>-Footnote-21095766
Node: dbm<2>1095830
Ref: whatsnew/3 7 dbm1095927
Ref: ad51095927
Node: decimal1096072
Ref: whatsnew/3 7 decimal1096164
Ref: ad61096164
Ref: decimal-Footnote-11096385
Node: dis<3>1096450
Ref: whatsnew/3 7 dis1096548
Ref: ad71096548
Ref: dis<3>-Footnote-11096951
Node: distutils<4>1097016
Ref: whatsnew/3 7 distutils1097114
Ref: ad91097114
Ref: distutils<4>-Footnote-11097362
Node: enum<4>1097427
Ref: whatsnew/3 7 enum1097531
Ref: ada1097531
Ref: enum<4>-Footnote-11098199
Ref: enum<4>-Footnote-21098264
Node: functools<3>1098329
Ref: whatsnew/3 7 functools1098426
Ref: adc1098426
Ref: functools<3>-Footnote-11098655
Node: gc<5>1098720
Ref: whatsnew/3 7 gc1098817
Ref: add1098817
Ref: gc<5>-Footnote-11099356
Node: hmac<2>1099421
Ref: whatsnew/3 7 hmac1099517
Ref: ae11099517
Ref: hmac<2>-Footnote-11099775
Node: http client1099840
Ref: whatsnew/3 7 http-client1099942
Ref: ae31099942
Ref: http client-Footnote-11100199
Node: http server1100264
Ref: whatsnew/3 7 http-server1100375
Ref: ae61100375
Ref: http server-Footnote-11101253
Ref: http server-Footnote-21101318
Ref: http server-Footnote-31101383
Node: idlelib and IDLE1101448
Ref: whatsnew/3 7 idlelib-and-idle1101560
Ref: ae91101560
Ref: idlelib and IDLE-Footnote-11104565
Ref: idlelib and IDLE-Footnote-21104630
Ref: idlelib and IDLE-Footnote-31104697
Ref: idlelib and IDLE-Footnote-41104762
Ref: idlelib and IDLE-Footnote-51104827
Ref: idlelib and IDLE-Footnote-61104892
Ref: idlelib and IDLE-Footnote-71104957
Ref: idlelib and IDLE-Footnote-81105022
Ref: idlelib and IDLE-Footnote-91105087
Ref: idlelib and IDLE-Footnote-101105152
Ref: idlelib and IDLE-Footnote-111105220
Ref: idlelib and IDLE-Footnote-121105285
Ref: idlelib and IDLE-Footnote-131105351
Node: importlib<4>1105417
Ref: whatsnew/3 7 importlib1105523
Ref: aea1105523
Ref: importlib<4>-Footnote-11106394
Ref: importlib<4>-Footnote-21106459
Ref: importlib<4>-Footnote-31106524
Node: io<4>1106589
Ref: whatsnew/3 7 io1106691
Ref: aec1106691
Ref: io<4>-Footnote-11106956
Ref: io<4>-Footnote-21107021
Node: ipaddress<3>1107086
Ref: whatsnew/3 7 ipaddress1107188
Ref: aee1107188
Ref: ipaddress<3>-Footnote-11107508
Node: itertools<5>1107573
Ref: whatsnew/3 7 itertools1107679
Ref: aef1107679
Ref: itertools<5>-Footnote-11107916
Node: locale<4>1107981
Ref: whatsnew/3 7 locale1108085
Ref: af11108085
Ref: locale<4>-Footnote-11108499
Node: logging<3>1108564
Ref: whatsnew/3 7 logging1108663
Ref: af21108663
Ref: logging<3>-Footnote-11109187
Ref: logging<3>-Footnote-21109252
Ref: logging<3>-Footnote-31109317
Node: math<6>1109382
Ref: whatsnew/3 7 math1109484
Ref: af61109484
Ref: math<6>-Footnote-11109697
Node: mimetypes<2>1109762
Ref: whatsnew/3 7 mimetypes1109860
Ref: af81109860
Ref: mimetypes<2>-Footnote-11110075
Node: msilib1110140
Ref: whatsnew/3 7 msilib1110249
Ref: af91110249
Ref: msilib-Footnote-11110444
Node: multiprocessing<4>1110509
Ref: whatsnew/3 7 multiprocessing1110611
Ref: afa1110611
Ref: multiprocessing<4>-Footnote-11111258
Ref: multiprocessing<4>-Footnote-21111323
Ref: multiprocessing<4>-Footnote-31111388
Node: os<7>1111453
Ref: whatsnew/3 7 os1111559
Ref: afe1111559
Ref: os<7>-Footnote-11112857
Ref: os<7>-Footnote-21112922
Ref: os<7>-Footnote-31112987
Ref: os<7>-Footnote-41113052
Ref: os<7>-Footnote-51113117
Ref: os<7>-Footnote-61113182
Ref: os<7>-Footnote-71113247
Node: pathlib<8>1113312
Ref: whatsnew/3 7 pathlib1113406
Ref: b091113406
Ref: pathlib<8>-Footnote-11113666
Node: pdb<4>1113731
Ref: whatsnew/3 7 pdb1113833
Ref: b0a1113833
Ref: pdb<4>-Footnote-11114243
Ref: pdb<4>-Footnote-21114308
Node: py_compile<3>1114373
Ref: whatsnew/3 7 py-compile1114473
Ref: b0b1114473
Ref: py_compile<3>-Footnote-11114923
Ref: py_compile<3>-Footnote-21114964
Node: pydoc<2>1115029
Ref: whatsnew/3 7 pydoc1115131
Ref: b0c1115131
Ref: pydoc<2>-Footnote-11115355
Node: queue<2>1115420
Ref: whatsnew/3 7 queue1115514
Ref: b0d1115514
Ref: queue<2>-Footnote-11115697
Node: re<4>1115762
Ref: whatsnew/3 7 re1115857
Ref: b0f1115857
Ref: re<4>-Footnote-11116939
Ref: re<4>-Footnote-21117004
Ref: re<4>-Footnote-31117069
Ref: re<4>-Footnote-41117134
Ref: re<4>-Footnote-51117199
Node: signal<2>1117264
Ref: whatsnew/3 7 signal1117360
Ref: b131117360
Ref: signal<2>-Footnote-11117679
Node: socket<5>1117744
Ref: whatsnew/3 7 socket1117847
Ref: b151117847
Ref: socket<5>-Footnote-11118935
Ref: socket<5>-Footnote-21119000
Ref: socket<5>-Footnote-31119065
Ref: socket<5>-Footnote-41119130
Ref: socket<5>-Footnote-51119195
Ref: socket<5>-Footnote-61119260
Node: socketserver1119325
Ref: whatsnew/3 7 socketserver1119429
Ref: b1a1119429
Node: sqlite3<6>1119905
Ref: whatsnew/3 7 sqlite31120006
Ref: b1d1120006
Ref: sqlite3<6>-Footnote-11120448
Ref: sqlite3<6>-Footnote-21120513
Node: ssl<5>1120578
Ref: whatsnew/3 7 ssl1120676
Ref: b1f1120676
Ref: ssl<5>-Footnote-11123940
Ref: ssl<5>-Footnote-21124005
Ref: ssl<5>-Footnote-31124070
Ref: ssl<5>-Footnote-41124135
Ref: ssl<5>-Footnote-51124200
Ref: ssl<5>-Footnote-61124265
Ref: ssl<5>-Footnote-71124330
Ref: ssl<5>-Footnote-81124395
Ref: ssl<5>-Footnote-91124460
Ref: ssl<5>-Footnote-101124525
Ref: ssl<5>-Footnote-111124591
Ref: ssl<5>-Footnote-121124657
Ref: ssl<5>-Footnote-131124723
Ref: ssl<5>-Footnote-141124789
Node: string<2>1124845
Ref: whatsnew/3 7 string1124946
Ref: b2a1124946
Ref: string<2>-Footnote-11125223
Node: subprocess<2>1125290
Ref: whatsnew/3 7 subprocess1125391
Ref: b2b1125391
Ref: subprocess<2>-Footnote-11126711
Ref: subprocess<2>-Footnote-21126776
Ref: subprocess<2>-Footnote-31126841
Ref: subprocess<2>-Footnote-41126906
Node: sys<7>1126971
Ref: whatsnew/3 7 sys1127070
Ref: b2f1127070
Ref: sys<7>-Footnote-11127810
Ref: sys<7>-Footnote-21127875
Ref: sys<7>-Footnote-31127940
Node: time<5>1128005
Ref: whatsnew/3 7 time1128101
Ref: b331128101
Ref: time<5>-Footnote-11129310
Ref: time<5>-Footnote-21129352
Node: tkinter<5>1129417
Ref: whatsnew/3 7 tkinter1129521
Ref: b3a1129521
Ref: tkinter<5>-Footnote-11129702
Node: tracemalloc<2>1129767
Ref: whatsnew/3 7 tracemalloc1129872
Ref: b3c1129872
Ref: tracemalloc<2>-Footnote-11130338
Node: types<4>1130403
Ref: whatsnew/3 7 types1130512
Ref: b3f1130512
Ref: types<4>-Footnote-11131027
Ref: types<4>-Footnote-21131092
Ref: types<4>-Footnote-31131157
Ref: types<4>-Footnote-41131199
Node: unicodedata<6>1131264
Ref: whatsnew/3 7 unicodedata1131370
Ref: b441131370
Ref: unicodedata<6>-Footnote-11131572
Node: unittest<7>1131628
Ref: whatsnew/3 7 unittest1131739
Ref: b451131739
Ref: unittest<7>-Footnote-11132144
Node: unittest mock1132209
Ref: whatsnew/3 7 unittest-mock1132321
Ref: b461132321
Ref: unittest mock-Footnote-11132839
Ref: unittest mock-Footnote-21132904
Node: urllib parse<5>1132969
Ref: whatsnew/3 7 urllib-parse1133072
Ref: b491133072
Ref: urllib parse<5>-Footnote-11133385
Ref: urllib parse<5>-Footnote-21133444
Ref: urllib parse<5>-Footnote-31133503
Node: uu1133568
Ref: whatsnew/3 7 uu1133665
Ref: b4b1133665
Ref: uu-Footnote-11133929
Node: uuid<2>1133994
Ref: whatsnew/3 7 uuid1134087
Ref: b4c1134087
Ref: uuid<2>-Footnote-11134727
Ref: uuid<2>-Footnote-21134792
Node: warnings<3>1134857
Ref: whatsnew/3 7 warnings1134954
Ref: b501134954
Ref: warnings<3>-Footnote-11136385
Ref: warnings<3>-Footnote-21136450
Ref: warnings<3>-Footnote-31136515
Ref: warnings<3>-Footnote-41136580
Node: xml<5>1136645
Ref: whatsnew/3 7 xml1136744
Ref: b521136744
Ref: xml<5>-Footnote-11137028
Node: xml etree1137083
Ref: whatsnew/3 7 xml-etree1137184
Ref: b531137184
Ref: xml etree-Footnote-11137525
Node: xmlrpc server1137590
Ref: whatsnew/3 7 xmlrpc-server1137691
Ref: b551137691
Ref: xmlrpc server-Footnote-11137900
Node: zipapp1137964
Ref: whatsnew/3 7 zipapp1138066
Ref: b561138066
Ref: zipapp-Footnote-11138590
Ref: zipapp-Footnote-21138655
Node: zipfile<2>1138720
Ref: whatsnew/3 7 zipfile1138800
Ref: b581138800
Ref: zipfile<2>-Footnote-11139165
Ref: zipfile<2>-Footnote-21139230
Node: C API 變更<5>1139295
Ref: whatsnew/3 7 c-api-changes1139427
Ref: b591139427
Ref: C API 變更<5>-Footnote-11143909
Ref: C API 變更<5>-Footnote-21143974
Ref: C API 變更<5>-Footnote-31144039
Ref: C API 變更<5>-Footnote-41144104
Ref: C API 變更<5>-Footnote-51144169
Ref: C API 變更<5>-Footnote-61144234
Ref: C API 變更<5>-Footnote-71144299
Ref: C API 變更<5>-Footnote-81144364
Ref: C API 變更<5>-Footnote-91144429
Ref: C API 變更<5>-Footnote-101144494
Ref: C API 變更<5>-Footnote-111144560
Ref: C API 變更<5>-Footnote-121144626
Ref: C API 變更<5>-Footnote-131144692
Ref: C API 變更<5>-Footnote-141144758
Ref: C API 變更<5>-Footnote-151144824
Ref: C API 變更<5>-Footnote-161144889
Ref: C API 變更<5>-Footnote-171144955
Ref: C API 變更<5>-Footnote-181145021
Ref: C API 變更<5>-Footnote-191145087
Ref: C API 變更<5>-Footnote-201145153
Node: 建置變更<5>1145219
Ref: whatsnew/3 7 build-changes1145345
Ref: b721145345
Ref: 建置變更<5>-Footnote-11146472
Ref: 建置變更<5>-Footnote-21146537
Ref: 建置變更<5>-Footnote-31146602
Node: 最佳化<6>1146667
Ref: whatsnew/3 7 optimizations1146814
Ref: b731146814
Ref: whatsnew/3 7 whatsnew37-perf1146814
Ref: a731146814
Ref: whatsnew/3 7 whatsnew37-asyncio-perf1147497
Ref: aa51147497
Ref: 最佳化<6>-Footnote-11152042
Ref: 最佳化<6>-Footnote-21152107
Ref: 最佳化<6>-Footnote-31152172
Ref: 最佳化<6>-Footnote-41152237
Ref: 最佳化<6>-Footnote-51152302
Ref: 最佳化<6>-Footnote-61152367
Ref: 最佳化<6>-Footnote-71152432
Ref: 最佳化<6>-Footnote-81152497
Ref: 最佳化<6>-Footnote-91152562
Ref: 最佳化<6>-Footnote-101152627
Ref: 最佳化<6>-Footnote-111152693
Ref: 最佳化<6>-Footnote-121152759
Ref: 最佳化<6>-Footnote-131152825
Ref: 最佳化<6>-Footnote-141152891
Ref: 最佳化<6>-Footnote-151152957
Ref: 最佳化<6>-Footnote-161153023
Ref: 最佳化<6>-Footnote-171153089
Ref: 最佳化<6>-Footnote-181153155
Ref: 最佳化<6>-Footnote-191153221
Ref: 最佳化<6>-Footnote-201153287
Ref: 最佳化<6>-Footnote-211153353
Ref: 最佳化<6>-Footnote-221153419
Ref: 最佳化<6>-Footnote-231153485
Ref: 最佳化<6>-Footnote-241153551
Ref: 最佳化<6>-Footnote-251153617
Ref: 最佳化<6>-Footnote-261153683
Ref: 最佳化<6>-Footnote-271153749
Ref: 最佳化<6>-Footnote-281153815
Ref: 最佳化<6>-Footnote-291153881
Ref: 最佳化<6>-Footnote-301153947
Node: Other CPython Implementation Changes1154013
Ref: whatsnew/3 7 other-cpython-implementation-changes1154171
Ref: b811154171
Ref: Other CPython Implementation Changes-Footnote-11155576
Ref: Other CPython Implementation Changes-Footnote-21155641
Ref: Other CPython Implementation Changes-Footnote-31155706
Ref: Other CPython Implementation Changes-Footnote-41155771
Ref: Other CPython Implementation Changes-Footnote-51155836
Node: Deprecated Python Behavior1155901
Ref: whatsnew/3 7 deprecated-python-behavior1156094
Ref: b841156094
Ref: Deprecated Python Behavior-Footnote-11157201
Ref: Deprecated Python Behavior-Footnote-21157266
Node: Deprecated Python modules functions and methods1157331
Ref: whatsnew/3 7 deprecated-python-modules-functions-and-methods1157531
Ref: b861157531
Node: aifc1157929
Ref: whatsnew/3 7 aifc1158036
Ref: b871158036
Ref: aifc-Footnote-11158256
Node: asyncio<8>1158321
Ref: whatsnew/3 7 id21158451
Ref: b881158451
Ref: whatsnew/3 7 whatsnew37-asyncio-deprecated1158451
Ref: ac31158451
Ref: asyncio<8>-Footnote-11158976
Ref: asyncio<8>-Footnote-21159041
Node: collections<3>1159106
Ref: whatsnew/3 7 id31159238
Ref: b891159238
Ref: collections<3>-Footnote-11159617
Node: dbm<3>1159682
Ref: whatsnew/3 7 id41159811
Ref: b8a1159811
Ref: dbm<3>-Footnote-11160212
Node: enum<5>1160277
Ref: whatsnew/3 7 id51160402
Ref: b8b1160402
Ref: enum<5>-Footnote-11160852
Node: gettext<2>1160917
Ref: whatsnew/3 7 gettext1161048
Ref: b8c1161048
Ref: gettext<2>-Footnote-11161293
Node: importlib<5>1161358
Ref: whatsnew/3 7 id61161491
Ref: b8d1161491
Ref: importlib<5>-Footnote-11162006
Node: locale<5>1162071
Ref: whatsnew/3 7 id71162201
Ref: b8f1162201
Ref: locale<5>-Footnote-11162404
Node: macpath1162469
Ref: whatsnew/3 7 macpath1162599
Ref: b901162599
Ref: macpath-Footnote-11162789
Node: threading<5>1162853
Ref: whatsnew/3 7 threading1162983
Ref: b911162983
Ref: threading<5>-Footnote-11163281
Node: socket<6>1163346
Ref: whatsnew/3 7 id81163475
Ref: b921163475
Ref: socket<6>-Footnote-11163820
Node: ssl<6>1163885
Ref: whatsnew/3 7 id91164007
Ref: b931164007
Ref: ssl<6>-Footnote-11164219
Node: sunau1164284
Ref: whatsnew/3 7 sunau1164403
Ref: b941164403
Ref: sunau-Footnote-11164629
Node: sys<8>1164694
Ref: whatsnew/3 7 id101164811
Ref: b951164811
Ref: sys<8>-Footnote-11165128
Node: wave1165193
Ref: whatsnew/3 7 wave1165296
Ref: b961165296
Ref: wave-Footnote-11165524
Node: Deprecated functions and types of the C API1165589
Ref: whatsnew/3 7 deprecated-functions-and-types-of-the-c-api1165788
Ref: b971165788
Ref: Deprecated functions and types of the C API-Footnote-11166446
Ref: Deprecated functions and types of the C API-Footnote-21166511
Node: Platform Support Removals1166576
Ref: whatsnew/3 7 id111166755
Ref: b981166755
Ref: whatsnew/3 7 platform-support-removals1166755
Ref: b221166755
Ref: Platform Support Removals-Footnote-11168147
Ref: Platform Support Removals-Footnote-21168214
Node: API and Feature Removals<2>1168294
Ref: whatsnew/3 7 api-and-feature-removals1168445
Ref: b991168445
Ref: API and Feature Removals<2>-Footnote-11171352
Ref: API and Feature Removals<2>-Footnote-21171417
Ref: API and Feature Removals<2>-Footnote-31171482
Node: Module Removals1171547
Ref: whatsnew/3 7 module-removals1171693
Ref: b9d1171693
Ref: Module Removals-Footnote-11172028
Node: Windows-only Changes1172093
Ref: whatsnew/3 7 windows-only-changes1172233
Ref: b9e1172233
Ref: Windows-only Changes-Footnote-11173110
Ref: Windows-only Changes-Footnote-21173175
Node: Porting to Python 3 71173240
Ref: whatsnew/3 7 porting-to-python-3-71173396
Ref: b9f1173396
Ref: whatsnew/3 7 porting-to-python-371173396
Ref: a741173396
Node: Changes in Python Behavior1173858
Ref: whatsnew/3 7 changes-in-python-behavior1173979
Ref: ba01173979
Ref: Changes in Python Behavior-Footnote-11175845
Ref: Changes in Python Behavior-Footnote-21175910
Ref: Changes in Python Behavior-Footnote-31175952
Ref: Changes in Python Behavior-Footnote-41176017
Ref: Changes in Python Behavior-Footnote-51176082
Ref: Changes in Python Behavior-Footnote-61176147
Node: Changes in the Python API<5>1176212
Ref: whatsnew/3 7 changes-in-the-python-api1176363
Ref: ba31176363
Ref: Changes in the Python API<5>-Footnote-11185892
Ref: Changes in the Python API<5>-Footnote-21185957
Ref: Changes in the Python API<5>-Footnote-31186022
Ref: Changes in the Python API<5>-Footnote-41186087
Ref: Changes in the Python API<5>-Footnote-51186152
Ref: Changes in the Python API<5>-Footnote-61186217
Ref: Changes in the Python API<5>-Footnote-71186282
Ref: Changes in the Python API<5>-Footnote-81186347
Ref: Changes in the Python API<5>-Footnote-91186412
Ref: Changes in the Python API<5>-Footnote-101186477
Ref: Changes in the Python API<5>-Footnote-111186543
Ref: Changes in the Python API<5>-Footnote-121186609
Ref: Changes in the Python API<5>-Footnote-131186675
Ref: Changes in the Python API<5>-Footnote-141186741
Ref: Changes in the Python API<5>-Footnote-151186784
Ref: Changes in the Python API<5>-Footnote-161186850
Ref: Changes in the Python API<5>-Footnote-171186916
Ref: Changes in the Python API<5>-Footnote-181186982
Ref: Changes in the Python API<5>-Footnote-191187048
Ref: Changes in the Python API<5>-Footnote-201187114
Ref: Changes in the Python API<5>-Footnote-211187180
Ref: Changes in the Python API<5>-Footnote-221187246
Ref: Changes in the Python API<5>-Footnote-231187312
Ref: Changes in the Python API<5>-Footnote-241187378
Ref: Changes in the Python API<5>-Footnote-251187444
Ref: Changes in the Python API<5>-Footnote-261187510
Ref: Changes in the Python API<5>-Footnote-271187576
Ref: Changes in the Python API<5>-Footnote-281187642
Ref: Changes in the Python API<5>-Footnote-291187708
Ref: Changes in the Python API<5>-Footnote-301187774
Node: C API 中的改動<4>1187840
Ref: whatsnew/3 7 changes-in-the-c-api1187994
Ref: bc41187994
Ref: C API 中的改動<4>-Footnote-11188622
Node: CPython 位元組碼變更<6>1188687
Ref: whatsnew/3 7 cpython-bytecode-changes1188836
Ref: bc51188836
Ref: CPython 位元組碼變更<6>-Footnote-11189180
Ref: CPython 位元組碼變更<6>-Footnote-21189245
Node: Windows-only Changes<2>1189310
Ref: whatsnew/3 7 id121189474
Ref: bc71189474
Ref: Windows-only Changes<2>-Footnote-11189792
Node: Other CPython implementation changes1189857
Ref: whatsnew/3 7 id131189983
Ref: bc91189983
Ref: Other CPython implementation changes-Footnote-11192307
Ref: Other CPython implementation changes-Footnote-21192349
Ref: Other CPython implementation changes-Footnote-31192414
Node: Python 3 7 1 中顯著的變更1192479
Ref: whatsnew/3 7 notable-changes-in-python-3-7-11192646
Ref: bcb1192646
Ref: Python 3 7 1 中顯著的變更-Footnote-11193575
Ref: Python 3 7 1 中顯著的變更-Footnote-21193640
Ref: Python 3 7 1 中顯著的變更-Footnote-31193705
Node: Python 3 7 2 中顯著的變更1193770
Ref: whatsnew/3 7 notable-changes-in-python-3-7-21193947
Ref: bce1193947
Node: Python 3 7 6 中顯著的變更1194435
Ref: whatsnew/3 7 notable-changes-in-python-3-7-61194613
Ref: bcf1194613
Ref: Python 3 7 6 中顯著的變更-Footnote-11195118
Node: Python 3 7 10 中顯著的變更1195183
Ref: whatsnew/3 7 notable-changes-in-python-3-7-101195362
Ref: bd01195362
Ref: Python 3 7 10 中顯著的變更-Footnote-11196076
Node: Python 3 7 11 中顯著的變更1196141
Ref: whatsnew/3 7 notable-changes-in-python-3-7-111196323
Ref: bd11196323
Ref: Python 3 7 11 中顯著的變更-Footnote-11197233
Ref: Python 3 7 11 中顯著的變更-Footnote-21197288
Node: Notable security feature in 3 7 141197343
Ref: whatsnew/3 7 notable-security-feature-in-3-7-141197484
Ref: bd21197484
Ref: Notable security feature in 3 7 14-Footnote-11198214
Node: Python 3 6 有什麼新功能1198284
Ref: whatsnew/3 6 doc1198454
Ref: bd31198454
Ref: whatsnew/3 6 what-s-new-in-python-3-61198454
Ref: bd41198454
Ref: Python 3 6 有什麼新功能-Footnote-11199776
Ref: Python 3 6 有什麼新功能-Footnote-21199836
Node: Summary -- Release highlights<3>1199878
Ref: whatsnew/3 6 summary-release-highlights1200000
Ref: bd51200000
Ref: Summary -- Release highlights<3>-Footnote-11204226
Ref: Summary -- Release highlights<3>-Footnote-21204306
Ref: Summary -- Release highlights<3>-Footnote-31204396
Node: New Features<7>1204438
Ref: whatsnew/3 6 new-features1204590
Ref: be91204590
Ref: whatsnew/3 6 pypy-dict-implementation1204590
Ref: bea1204590
Node: PEP 498 Formatted string literals1206000
Ref: whatsnew/3 6 pep-498-formatted-string-literals1206133
Ref: beb1206133
Ref: whatsnew/3 6 whatsnew36-pep4981206133
Ref: bd61206133
Ref: PEP 498 Formatted string literals-Footnote-11207110
Ref: PEP 498 Formatted string literals-Footnote-21207152
Node: PEP 526 Syntax for variable annotations1207194
Ref: whatsnew/3 6 pep-526-syntax-for-variable-annotations1207375
Ref: bec1207375
Ref: whatsnew/3 6 whatsnew36-pep5261207375
Ref: bd81207375
Ref: PEP 526 Syntax for variable annotations-Footnote-11208616
Ref: PEP 526 Syntax for variable annotations-Footnote-21208658
Ref: PEP 526 Syntax for variable annotations-Footnote-31208700
Ref: PEP 526 Syntax for variable annotations-Footnote-41208735
Node: PEP 515 Underscores in Numeric Literals1208776
Ref: whatsnew/3 6 pep-515-underscores-in-numeric-literals1208955
Ref: bed1208955
Ref: whatsnew/3 6 whatsnew36-pep5151208955
Ref: bd71208955
Ref: PEP 515 Underscores in Numeric Literals-Footnote-11210023
Ref: PEP 515 Underscores in Numeric Literals-Footnote-21210065
Node: PEP 525 Asynchronous Generators1210107
Ref: whatsnew/3 6 pep-525-asynchronous-generators1210282
Ref: bee1210282
Ref: whatsnew/3 6 whatsnew36-pep5251210282
Ref: bd91210282
Ref: PEP 525 Asynchronous Generators-Footnote-11211110
Ref: PEP 525 Asynchronous Generators-Footnote-21211152
Node: PEP 530 Asynchronous Comprehensions1211194
Ref: whatsnew/3 6 pep-530-asynchronous-comprehensions1211377
Ref: bef1211377
Ref: whatsnew/3 6 whatsnew36-pep5301211377
Ref: bda1211377
Ref: PEP 530 Asynchronous Comprehensions-Footnote-11211928
Ref: PEP 530 Asynchronous Comprehensions-Footnote-21211970
Node: PEP 487 Simpler customization of class creation1212012
Ref: whatsnew/3 6 pep-487-simpler-customization-of-class-creation1212204
Ref: bf01212204
Ref: whatsnew/3 6 whatsnew36-pep4871212204
Ref: bdd1212204
Ref: PEP 487 Simpler customization of class creation-Footnote-11213289
Node: PEP 487 Descriptor Protocol Enhancements1213331
Ref: whatsnew/3 6 pep-487-descriptor-protocol-enhancements1213530
Ref: bf31213530
Ref: whatsnew/3 6 whatsnew36-pep487-descriptors1213530
Ref: bf41213530
Ref: PEP 487 Descriptor Protocol Enhancements-Footnote-11214774
Ref: PEP 487 Descriptor Protocol Enhancements-Footnote-21214816
Node: PEP 519 Adding a file system path protocol1214858
Ref: whatsnew/3 6 pep-519-adding-a-file-system-path-protocol1215043
Ref: bf71215043
Ref: whatsnew/3 6 whatsnew36-pep5191215043
Ref: be21215043
Ref: PEP 519 Adding a file system path protocol-Footnote-11217867
Node: PEP 495 Local Time Disambiguation1217909
Ref: whatsnew/3 6 pep-495-local-time-disambiguation1218105
Ref: bfd1218105
Ref: whatsnew/3 6 whatsnew36-pep4951218105
Ref: be31218105
Ref: PEP 495 Local Time Disambiguation-Footnote-11219515
Ref: PEP 495 Local Time Disambiguation-Footnote-21219557
Node: PEP 529 Change Windows filesystem encoding to UTF-81219599
Ref: whatsnew/3 6 pep-529-change-windows-filesystem-encoding-to-utf-81219801
Ref: bff1219801
Ref: whatsnew/3 6 whatsnew36-pep5291219801
Ref: be71219801
Ref: PEP 529 Change Windows filesystem encoding to UTF-8-Footnote-11220831
Node: PEP 528 Change Windows console encoding to UTF-81220873
Ref: whatsnew/3 6 pep-528-change-windows-console-encoding-to-utf-81221093
Ref: c011221093
Ref: whatsnew/3 6 whatsnew36-pep5281221093
Ref: be61221093
Ref: PEP 528 Change Windows console encoding to UTF-8-Footnote-11221789
Node: PEP 520 Preserving Class Attribute Definition Order1221831
Ref: whatsnew/3 6 pep-520-preserving-class-attribute-definition-order1222041
Ref: c031222041
Ref: whatsnew/3 6 whatsnew36-pep5201222041
Ref: bde1222041
Ref: PEP 520 Preserving Class Attribute Definition Order-Footnote-11222672
Node: PEP 468 Preserving Keyword Argument Order1222714
Ref: whatsnew/3 6 pep-468-preserving-keyword-argument-order1222899
Ref: c061222899
Ref: whatsnew/3 6 whatsnew36-pep4681222899
Ref: bdf1222899
Ref: PEP 468 Preserving Keyword Argument Order-Footnote-11223253
Node: New dict implementation1223295
Ref: whatsnew/3 6 new-dict-implementation1223477
Ref: c071223477
Ref: whatsnew/3 6 whatsnew36-compactdict1223477
Ref: bdc1223477
Ref: New dict implementation-Footnote-11224451
Ref: New dict implementation-Footnote-21224531
Ref: New dict implementation-Footnote-31224621
Ref: New dict implementation-Footnote-41224686
Node: PEP 523 Adding a frame evaluation API to CPython1224766
Ref: whatsnew/3 6 pep-523-adding-a-frame-evaluation-api-to-cpython1224940
Ref: c081224940
Ref: whatsnew/3 6 whatsnew36-pep5231224940
Ref: c091224940
Ref: PEP 523 Adding a frame evaluation API to CPython-Footnote-11226108
Ref: PEP 523 Adding a frame evaluation API to CPython-Footnote-21226150
Node: PYTHONMALLOC environment variable1226192
Ref: whatsnew/3 6 pythonmalloc-environment-variable1226379
Ref: c0a1226379
Ref: whatsnew/3 6 whatsnew36-pythonmalloc1226379
Ref: be11226379
Ref: PYTHONMALLOC environment variable-Footnote-11229567
Ref: PYTHONMALLOC environment variable-Footnote-21229632
Node: DTrace and SystemTap probing support1229697
Ref: whatsnew/3 6 dtrace-and-systemtap-probing-support1229827
Ref: c121229827
Ref: whatsnew/3 6 whatsnew36-tracing1229827
Ref: be01229827
Ref: DTrace and SystemTap probing support-Footnote-11230665
Node: 其他語言更動<7>1230730
Ref: whatsnew/3 6 other-language-changes1230862
Ref: c141230862
Ref: 其他語言更動<7>-Footnote-11232227
Ref: 其他語言更動<7>-Footnote-21232292
Ref: 其他語言更動<7>-Footnote-31232357
Ref: 其他語言更動<7>-Footnote-41232422
Node: 新模組<4>1232487
Ref: whatsnew/3 6 new-modules1232622
Ref: c171232622
Node: secrets1232674
Ref: whatsnew/3 6 secrets1232730
Ref: c181232730
Ref: whatsnew/3 6 whatsnew36-pep5061232730
Ref: secrets-Footnote-11233403
Node: 改進的模組<7>1233445
Ref: whatsnew/3 6 improved-modules1233571
Ref: c191233571
Node: array<4>1235047
Ref: whatsnew/3 6 array1235125
Ref: c1a1235125
Ref: array<4>-Footnote-11235418
Node: ast<4>1235483
Ref: whatsnew/3 6 ast1235580
Ref: c1b1235580
Ref: ast<4>-Footnote-11235829
Node: asyncio<9>1235894
Ref: whatsnew/3 6 asyncio1235994
Ref: c1c1235994
Ref: asyncio<9>-Footnote-11239334
Ref: asyncio<9>-Footnote-21239399
Ref: asyncio<9>-Footnote-31239444
Ref: asyncio<9>-Footnote-41239509
Ref: asyncio<9>-Footnote-51239574
Ref: asyncio<9>-Footnote-61239639
Ref: asyncio<9>-Footnote-71239704
Ref: asyncio<9>-Footnote-81239769
Ref: asyncio<9>-Footnote-91239834
Ref: asyncio<9>-Footnote-101239899
Ref: asyncio<9>-Footnote-111239965
Ref: asyncio<9>-Footnote-121240031
Node: binascii<2>1240097
Ref: whatsnew/3 6 binascii1240196
Ref: c251240196
Ref: binascii<2>-Footnote-11240481
Node: cmath1240546
Ref: whatsnew/3 6 cmath1240649
Ref: c271240649
Ref: cmath-Footnote-11241120
Ref: cmath-Footnote-21241185
Ref: cmath-Footnote-31241227
Node: collections<4>1241292
Ref: whatsnew/3 6 collections1241405
Ref: c2e1241405
Ref: collections<4>-Footnote-11242501
Ref: collections<4>-Footnote-21242566
Ref: collections<4>-Footnote-31242631
Ref: collections<4>-Footnote-41242696
Ref: collections<4>-Footnote-51242761
Ref: collections<4>-Footnote-61242826
Node: concurrent futures<4>1242891
Ref: whatsnew/3 6 concurrent-futures1243012
Ref: c321243012
Ref: concurrent futures<4>-Footnote-11243343
Node: contextlib<4>1243408
Ref: whatsnew/3 6 contextlib1243526
Ref: c331243526
Ref: contextlib<4>-Footnote-11244021
Node: datetime<5>1244086
Ref: whatsnew/3 6 datetime1244193
Ref: c361244193
Ref: datetime<5>-Footnote-11245210
Ref: datetime<5>-Footnote-21245275
Ref: datetime<5>-Footnote-31245340
Ref: datetime<5>-Footnote-41245405
Node: decimal<2>1245470
Ref: whatsnew/3 6 decimal1245576
Ref: c3a1245576
Ref: decimal<2>-Footnote-11245995
Node: distutils<5>1246060
Ref: whatsnew/3 6 distutils1246163
Ref: c3c1246163
Ref: distutils<5>-Footnote-11246537
Node: email<2>1246602
Ref: whatsnew/3 6 email1246707
Ref: c3d1246707
Ref: email<2>-Footnote-11247623
Ref: email<2>-Footnote-21247688
Ref: email<2>-Footnote-31247753
Node: encodings<2>1247818
Ref: whatsnew/3 6 encodings1247918
Ref: c411247918
Ref: encodings<2>-Footnote-11248213
Node: enum<6>1248278
Ref: whatsnew/3 6 enum1248385
Ref: c421248385
Ref: enum<6>-Footnote-11249133
Node: faulthandler<2>1249198
Ref: whatsnew/3 6 faulthandler1249305
Ref: c441249305
Ref: faulthandler<2>-Footnote-11249568
Node: fileinput<2>1249633
Ref: whatsnew/3 6 fileinput1249743
Ref: c461249743
Ref: fileinput<2>-Footnote-11249931
Node: hashlib<5>1249996
Ref: whatsnew/3 6 hashlib1250105
Ref: c481250105
Ref: hashlib<5>-Footnote-11251154
Ref: hashlib<5>-Footnote-21251219
Ref: hashlib<5>-Footnote-31251284
Ref: hashlib<5>-Footnote-41251349
Node: http client<2>1251414
Ref: whatsnew/3 6 http-client1251530
Ref: c4f1251530
Ref: http client<2>-Footnote-11251790
Node: idlelib and IDLE<2>1251855
Ref: whatsnew/3 6 idlelib-and-idle1251973
Ref: c521251973
Ref: idlelib and IDLE<2>-Footnote-11255443
Ref: idlelib and IDLE<2>-Footnote-21255508
Ref: idlelib and IDLE<2>-Footnote-31255573
Ref: idlelib and IDLE<2>-Footnote-41255640
Ref: idlelib and IDLE<2>-Footnote-51255705
Ref: idlelib and IDLE<2>-Footnote-61255770
Ref: idlelib and IDLE<2>-Footnote-71255835
Ref: idlelib and IDLE<2>-Footnote-81255900
Ref: idlelib and IDLE<2>-Footnote-91255965
Ref: idlelib and IDLE<2>-Footnote-101256030
Ref: idlelib and IDLE<2>-Footnote-111256096
Node: importlib<6>1256164
Ref: whatsnew/3 6 importlib1256278
Ref: c531256278
Ref: importlib<6>-Footnote-11257103
Node: inspect<6>1257168
Ref: whatsnew/3 6 inspect1257267
Ref: c591257267
Ref: inspect<6>-Footnote-11258042
Ref: inspect<6>-Footnote-21258107
Node: json1258172
Ref: whatsnew/3 6 json1258269
Ref: c5a1258269
Ref: json-Footnote-11258541
Node: logging<4>1258606
Ref: whatsnew/3 6 logging1258700
Ref: c5c1258700
Ref: logging<4>-Footnote-11258964
Node: math<7>1259029
Ref: whatsnew/3 6 math1259137
Ref: c5e1259137
Ref: math<7>-Footnote-11259369
Ref: math<7>-Footnote-21259434
Node: multiprocessing<5>1259476
Ref: whatsnew/3 6 multiprocessing1259579
Ref: c5f1259579
Ref: multiprocessing<5>-Footnote-11259808
Node: os<8>1259872
Ref: whatsnew/3 6 os1259978
Ref: c621259978
Ref: os<8>-Footnote-11260978
Ref: os<8>-Footnote-21261043
Ref: os<8>-Footnote-31261085
Node: pathlib<9>1261127
Ref: whatsnew/3 6 pathlib1261221
Ref: c651261221
Ref: pathlib<9>-Footnote-11261452
Node: pdb<5>1261517
Ref: whatsnew/3 6 pdb1261615
Ref: c661261615
Node: pickle<2>1261772
Ref: whatsnew/3 6 pickle1261871
Ref: c671261871
Ref: pickle<2>-Footnote-11262188
Node: pickletools1262253
Ref: whatsnew/3 6 pickletools1262354
Ref: c691262354
Ref: pickletools-Footnote-11262582
Node: pydoc<3>1262647
Ref: whatsnew/3 6 pydoc1262748
Ref: c6b1262748
Ref: pydoc<3>-Footnote-11263142
Ref: pydoc<3>-Footnote-21263206
Node: random<4>1263271
Ref: whatsnew/3 6 random1263366
Ref: c6c1263366
Ref: random<4>-Footnote-11263621
Node: re<5>1263686
Ref: whatsnew/3 6 re1263781
Ref: c6e1263781
Ref: re<5>-Footnote-11264492
Ref: re<5>-Footnote-21264558
Ref: re<5>-Footnote-31264623
Node: readline1264688
Ref: whatsnew/3 6 readline1264785
Ref: c701264785
Ref: readline-Footnote-11265016
Node: rlcompleter1265081
Ref: whatsnew/3 6 rlcompleter1265181
Ref: c721265181
Ref: rlcompleter-Footnote-11265485
Ref: rlcompleter-Footnote-21265550
Node: shlex<2>1265615
Ref: whatsnew/3 6 shlex1265714
Ref: c731265714
Ref: shlex<2>-Footnote-11266004
Node: site<3>1266071
Ref: whatsnew/3 6 site1266169
Ref: c761266169
Ref: site<3>-Footnote-11266433
Node: sqlite3<7>1266498
Ref: whatsnew/3 6 sqlite31266597
Ref: c771266597
Ref: sqlite3<7>-Footnote-11266800
Node: socket<7>1266865
Ref: whatsnew/3 6 socket1266972
Ref: c791266972
Ref: socket<7>-Footnote-11267929
Ref: socket<7>-Footnote-21267994
Ref: socket<7>-Footnote-31268059
Ref: socket<7>-Footnote-41268124
Ref: socket<7>-Footnote-51268189
Node: socketserver<2>1268254
Ref: whatsnew/3 6 socketserver1268357
Ref: c801268357
Ref: socketserver<2>-Footnote-11268986
Ref: socketserver<2>-Footnote-21269051
Node: ssl<7>1269116
Ref: whatsnew/3 6 ssl1269223
Ref: c831269223
Ref: ssl<7>-Footnote-11270646
Ref: ssl<7>-Footnote-21270711
Ref: ssl<7>-Footnote-31270776
Ref: ssl<7>-Footnote-41270841
Ref: ssl<7>-Footnote-51270906
Ref: ssl<7>-Footnote-61270971
Ref: ssl<7>-Footnote-71271036
Ref: ssl<7>-Footnote-81271101
Node: statistics<5>1271156
Ref: whatsnew/3 6 statistics1271254
Ref: c871271254
Ref: statistics<5>-Footnote-11271442
Node: struct1271507
Ref: whatsnew/3 6 struct1271612
Ref: c891271612
Ref: struct-Footnote-11271843
Node: subprocess<3>1271908
Ref: whatsnew/3 6 subprocess1272006
Ref: c8a1272006
Ref: subprocess<3>-Footnote-11272699
Ref: subprocess<3>-Footnote-21272764
Node: sys<9>1272828
Ref: whatsnew/3 6 sys1272929
Ref: c8c1272929
Ref: sys<9>-Footnote-11273530
Ref: sys<9>-Footnote-21273595
Node: telnetlib1273660
Ref: whatsnew/3 6 telnetlib1273755
Ref: c8f1273755
Ref: telnetlib-Footnote-11273930
Node: time<6>1273995
Ref: whatsnew/3 6 time1274090
Ref: c901274090
Node: timeit1274229
Ref: whatsnew/3 6 timeit1274325
Ref: c921274325
Ref: timeit-Footnote-11274782
Ref: timeit-Footnote-21274846
Node: tkinter<6>1274911
Ref: whatsnew/3 6 tkinter1275012
Ref: c951275012
Ref: tkinter<6>-Footnote-11275438
Node: traceback<4>1275503
Ref: whatsnew/3 6 traceback1275612
Ref: c961275612
Ref: whatsnew/3 6 whatsnew36-traceback1275612
Ref: c161275612
Ref: traceback<4>-Footnote-11276251
Node: tracemalloc<3>1276316
Ref: whatsnew/3 6 tracemalloc1276424
Ref: c971276424
Ref: tracemalloc<3>-Footnote-11276790
Node: typing<9>1276855
Ref: whatsnew/3 6 typing1276965
Ref: c991276965
Ref: whatsnew/3 6 whatsnew36-typing1276965
Ref: be41276965
Ref: typing<9>-Footnote-11278615
Ref: typing<9>-Footnote-21278665
Ref: typing<9>-Footnote-31278730
Ref: typing<9>-Footnote-41278795
Ref: typing<9>-Footnote-51278837
Ref: typing<9>-Footnote-61278887
Ref: typing<9>-Footnote-71278939
Node: unicodedata<7>1278991
Ref: whatsnew/3 6 unicodedata1279103
Ref: c9d1279103
Ref: unicodedata<7>-Footnote-11279290
Node: unittest mock<2>1279341
Ref: whatsnew/3 6 unittest-mock1279458
Ref: c9e1279458
Ref: unittest mock<2>-Footnote-11279975
Ref: unittest mock<2>-Footnote-21280040
Node: urllib request1280105
Ref: whatsnew/3 6 urllib-request1280226
Ref: ca21280226
Ref: urllib request-Footnote-11280591
Node: urllib robotparser1280656
Ref: whatsnew/3 6 urllib-robotparser1280768
Ref: ca31280768
Ref: urllib robotparser-Footnote-11281013
Node: venv<5>1281078
Ref: whatsnew/3 6 venv1281187
Ref: ca51281187
Ref: venv<5>-Footnote-11281473
Node: warnings<4>1281538
Ref: whatsnew/3 6 warnings1281635
Ref: ca61281635
Ref: warnings<4>-Footnote-11282903
Ref: warnings<4>-Footnote-21282968
Node: winreg1283033
Ref: whatsnew/3 6 winreg1283131
Ref: ca81283131
Ref: winreg-Footnote-11283304
Node: winsound1283369
Ref: whatsnew/3 6 winsound1283469
Ref: caa1283469
Ref: winsound-Footnote-11283668
Node: xmlrpc client1283733
Ref: whatsnew/3 6 xmlrpc-client1283837
Ref: cae1283837
Ref: xmlrpc client-Footnote-11284130
Node: zipfile<3>1284195
Ref: whatsnew/3 6 zipfile1284295
Ref: caf1284295
Ref: zipfile<3>-Footnote-11284829
Ref: zipfile<3>-Footnote-21284894
Node: zlib1284959
Ref: whatsnew/3 6 zlib1285037
Ref: cb31285037
Ref: zlib-Footnote-11285293
Ref: zlib-Footnote-21285358
Node: 最佳化<7>1285423
Ref: whatsnew/3 6 optimizations1285563
Ref: cb51285563
Ref: 最佳化<7>-Footnote-11289416
Ref: 最佳化<7>-Footnote-21289481
Ref: 最佳化<7>-Footnote-31289546
Ref: 最佳化<7>-Footnote-41289611
Ref: 最佳化<7>-Footnote-51289676
Ref: 最佳化<7>-Footnote-61289741
Ref: 最佳化<7>-Footnote-71289806
Ref: 最佳化<7>-Footnote-81289871
Ref: 最佳化<7>-Footnote-91289936
Ref: 最佳化<7>-Footnote-101290001
Ref: 最佳化<7>-Footnote-111290067
Ref: 最佳化<7>-Footnote-121290133
Ref: 最佳化<7>-Footnote-131290199
Ref: 最佳化<7>-Footnote-141290265
Ref: 最佳化<7>-Footnote-151290331
Ref: 最佳化<7>-Footnote-161290397
Ref: 最佳化<7>-Footnote-171290463
Ref: 最佳化<7>-Footnote-181290529
Ref: 最佳化<7>-Footnote-191290595
Ref: 最佳化<7>-Footnote-201290661
Ref: 最佳化<7>-Footnote-211290727
Node: Build and C API Changes<2>1290793
Ref: whatsnew/3 6 build-and-c-api-changes1290933
Ref: cbb1290933
Ref: Build and C API Changes<2>-Footnote-11293386
Ref: Build and C API Changes<2>-Footnote-21293428
Ref: Build and C API Changes<2>-Footnote-31293493
Ref: Build and C API Changes<2>-Footnote-41293558
Ref: Build and C API Changes<2>-Footnote-51293623
Ref: Build and C API Changes<2>-Footnote-61293687
Ref: Build and C API Changes<2>-Footnote-71293752
Ref: Build and C API Changes<2>-Footnote-81293817
Ref: Build and C API Changes<2>-Footnote-91293882
Ref: Build and C API Changes<2>-Footnote-101293947
Node: Other Improvements1294013
Ref: whatsnew/3 6 other-improvements1294153
Ref: cc11294153
Node: 已棄用<9>1294522
Ref: whatsnew/3 6 deprecated1294648
Ref: cc31294648
Node: 新關鍵字1294979
Ref: whatsnew/3 6 new-keywords1295075
Ref: cc41295075
Ref: 新關鍵字-Footnote-11295464
Node: Deprecated Python behavior1295506
Ref: whatsnew/3 6 deprecated-python-behavior1295661
Ref: cc51295661
Ref: Deprecated Python behavior-Footnote-11296862
Ref: Deprecated Python behavior-Footnote-21296927
Ref: Deprecated Python behavior-Footnote-31296992
Node: Deprecated Python modules functions and methods<2>1297057
Ref: whatsnew/3 6 deprecated-python-modules-functions-and-methods1297206
Ref: cc71297206
Node: asynchat1297515
Ref: whatsnew/3 6 asynchat1297627
Ref: cc81297627
Ref: asynchat-Footnote-11297811
Node: asyncore1297876
Ref: whatsnew/3 6 asyncore1298003
Ref: cc91298003
Ref: asyncore-Footnote-11298187
Node: dbm<4>1298252
Ref: whatsnew/3 6 dbm1298383
Ref: cca1298383
Ref: dbm<4>-Footnote-11298743
Node: distutils<6>1298808
Ref: whatsnew/3 6 id21298934
Ref: ccb1298934
Ref: distutils<6>-Footnote-11299264
Node: grp1299329
Ref: whatsnew/3 6 grp1299461
Ref: ccc1299461
Ref: grp-Footnote-11299659
Node: importlib<7>1299724
Ref: whatsnew/3 6 id31299849
Ref: cce1299849
Node: os<9>1300503
Ref: whatsnew/3 6 id41300630
Ref: cd31300630
Ref: os<9>-Footnote-11300924
Ref: os<9>-Footnote-21300989
Node: re<6>1301054
Ref: whatsnew/3 6 id51301175
Ref: cd51301175
Ref: re<6>-Footnote-11301501
Node: ssl<8>1301566
Ref: whatsnew/3 6 id61301692
Ref: cd61301692
Ref: ssl<8>-Footnote-11302487
Ref: ssl<8>-Footnote-21302552
Ref: ssl<8>-Footnote-31302617
Node: tkinter<7>1302682
Ref: whatsnew/3 6 id71302810
Ref: cd71302810
Node: venv<6>1302963
Ref: whatsnew/3 6 id81303076
Ref: cd81303076
Ref: whatsnew/3 6 whatsnew36-venv1303076
Ref: cd91303076
Ref: venv<6>-Footnote-11303427
Node: xml<6>1303492
Ref: whatsnew/3 6 xml1303661
Ref: cda1303661
Ref: xml<6>-Footnote-11303965
Node: Deprecated functions and types of the C API<2>1304020
Ref: whatsnew/3 6 deprecated-functions-and-types-of-the-c-api1304163
Ref: cdb1304163
Node: Deprecated Build Options1304512
Ref: whatsnew/3 6 deprecated-build-options1304640
Ref: cdd1304640
Node: 已移除<7>1305081
Ref: whatsnew/3 6 removed1305210
Ref: cde1305210
Node: API and Feature Removals<3>1305309
Ref: whatsnew/3 6 api-and-feature-removals1305385
Ref: cdf1305385
Ref: API and Feature Removals<3>-Footnote-11307475
Ref: API and Feature Removals<3>-Footnote-21307540
Node: Porting to Python 3 61307618
Ref: whatsnew/3 6 porting-to-python-3-61307766
Ref: ce21307766
Node: Changes in 'python' Command Behavior1308148
Ref: whatsnew/3 6 changes-in-python-command-behavior1308279
Ref: ce31308279
Ref: Changes in 'python' Command Behavior-Footnote-11308755
Node: Changes in the Python API<6>1308820
Ref: whatsnew/3 6 changes-in-the-python-api1308981
Ref: ce41308981
Ref: Changes in the Python API<6>-Footnote-11319051
Ref: Changes in the Python API<6>-Footnote-21319115
Ref: Changes in the Python API<6>-Footnote-31319157
Ref: Changes in the Python API<6>-Footnote-41319222
Ref: Changes in the Python API<6>-Footnote-51319287
Ref: Changes in the Python API<6>-Footnote-61319352
Ref: Changes in the Python API<6>-Footnote-71319417
Ref: Changes in the Python API<6>-Footnote-81319482
Ref: Changes in the Python API<6>-Footnote-91319547
Ref: Changes in the Python API<6>-Footnote-101319612
Ref: Changes in the Python API<6>-Footnote-111319678
Ref: Changes in the Python API<6>-Footnote-121319721
Ref: Changes in the Python API<6>-Footnote-131319787
Ref: Changes in the Python API<6>-Footnote-141319853
Ref: Changes in the Python API<6>-Footnote-151319919
Ref: Changes in the Python API<6>-Footnote-161319985
Ref: Changes in the Python API<6>-Footnote-171320050
Ref: Changes in the Python API<6>-Footnote-181320116
Ref: Changes in the Python API<6>-Footnote-191320182
Ref: Changes in the Python API<6>-Footnote-201320248
Node: C API 中的改動<5>1320314
Ref: whatsnew/3 6 changes-in-the-c-api1320468
Ref: cf41320468
Ref: C API 中的改動<5>-Footnote-11321114
Ref: C API 中的改動<5>-Footnote-21321179
Node: CPython 位元組碼變更<7>1321243
Ref: whatsnew/3 6 cpython-bytecode-changes1321360
Ref: cf61321360
Ref: CPython 位元組碼變更<7>-Footnote-11322984
Ref: CPython 位元組碼變更<7>-Footnote-21323049
Ref: CPython 位元組碼變更<7>-Footnote-31323114
Ref: CPython 位元組碼變更<7>-Footnote-41323179
Ref: CPython 位元組碼變更<7>-Footnote-51323244
Ref: CPython 位元組碼變更<7>-Footnote-61323309
Ref: CPython 位元組碼變更<7>-Footnote-71323374
Ref: CPython 位元組碼變更<7>-Footnote-81323439
Ref: CPython 位元組碼變更<7>-Footnote-91323504
Node: Python 3 6 2 中顯著的變更1323569
Ref: whatsnew/3 6 notable-changes-in-python-3-6-21323736
Ref: cfd1323736
Node: New make regen-all build target1323894
Ref: whatsnew/3 6 new-make-regen-all-build-target1324036
Ref: cfe1324036
Ref: New make regen-all build target-Footnote-11324831
Ref: New make regen-all build target-Footnote-21324899
Node: Removal of make touch build target1324964
Ref: whatsnew/3 6 removal-of-make-touch-build-target1325106
Ref: cff1325106
Ref: Removal of make touch build target-Footnote-11325540
Node: Python 3 6 4 中顯著的變更1325605
Ref: whatsnew/3 6 notable-changes-in-python-3-6-41325782
Ref: d001325782
Ref: Python 3 6 4 中顯著的變更-Footnote-11326149
Ref: Python 3 6 4 中顯著的變更-Footnote-21326214
Node: Python 3 6 5 中顯著的變更1326279
Ref: whatsnew/3 6 notable-changes-in-python-3-6-51326456
Ref: d011326456
Ref: Python 3 6 5 中顯著的變更-Footnote-11326753
Node: Python 3 6 7 中顯著的變更1326818
Ref: whatsnew/3 6 notable-changes-in-python-3-6-71326996
Ref: d021326996
Ref: Python 3 6 7 中顯著的變更-Footnote-11327496
Ref: Python 3 6 7 中顯著的變更-Footnote-21327551
Node: Python 3 6 10 中顯著的變更1327616
Ref: whatsnew/3 6 notable-changes-in-python-3-6-101327795
Ref: d031327795
Ref: Python 3 6 10 中顯著的變更-Footnote-11328302
Node: Python 3 6 13 中顯著的變更1328367
Ref: whatsnew/3 6 notable-changes-in-python-3-6-131328547
Ref: d041328547
Ref: Python 3 6 13 中顯著的變更-Footnote-11329261
Node: Python 3 6 14 中顯著的變更1329326
Ref: whatsnew/3 6 notable-changes-in-python-3-6-141329465
Ref: d051329465
Ref: Python 3 6 14 中顯著的變更-Footnote-11330375
Ref: Python 3 6 14 中顯著的變更-Footnote-21330430
Node: Python 3 4 有什麼新功能1330485
Ref: whatsnew/3 5 doc1330658
Ref: d061330658
Ref: whatsnew/3 5 what-s-new-in-python-3-51330658
Ref: d071330658
Ref: Python 3 4 有什麼新功能-Footnote-11331582
Ref: Python 3 4 有什麼新功能-Footnote-21331642
Node: Summary -- Release highlights<4>1331684
Ref: whatsnew/3 5 summary-release-highlights1331806
Ref: d081331806
Ref: Summary -- Release highlights<4>-Footnote-11335512
Ref: Summary -- Release highlights<4>-Footnote-21335576
Ref: Summary -- Release highlights<4>-Footnote-31335641
Ref: Summary -- Release highlights<4>-Footnote-41335706
Ref: Summary -- Release highlights<4>-Footnote-51335771
Ref: Summary -- Release highlights<4>-Footnote-61335836
Ref: Summary -- Release highlights<4>-Footnote-71335901
Node: New Features<8>1335966
Ref: whatsnew/3 5 new-features1336118
Ref: d1b1336118
Node: PEP 492 - Coroutines with async and await syntax1337209
Ref: whatsnew/3 5 pep-492-coroutines-with-async-and-await-syntax1337380
Ref: d1c1337380
Ref: whatsnew/3 5 whatsnew-pep-4921337380
Ref: d091337380
Ref: PEP 492 - Coroutines with async and await syntax-Footnote-11340446
Ref: PEP 492 - Coroutines with async and await syntax-Footnote-21340488
Node: PEP 465 - A dedicated infix operator for matrix multiplication1340530
Ref: whatsnew/3 5 pep-465-a-dedicated-infix-operator-for-matrix-multiplication1340756
Ref: d211340756
Ref: whatsnew/3 5 whatsnew-pep-4651340756
Ref: d0a1340756
Ref: PEP 465 - A dedicated infix operator for matrix multiplication-Footnote-11342134
Ref: PEP 465 - A dedicated infix operator for matrix multiplication-Footnote-21342176
Node: PEP 448 - Additional Unpacking Generalizations1342218
Ref: whatsnew/3 5 pep-448-additional-unpacking-generalizations1342456
Ref: d221342456
Ref: whatsnew/3 5 whatsnew-pep-4481342456
Ref: d0b1342456
Ref: PEP 448 - Additional Unpacking Generalizations-Footnote-11343546
Ref: PEP 448 - Additional Unpacking Generalizations-Footnote-21343588
Node: PEP 461 - percent formatting support for bytes and bytearray1343630
Ref: whatsnew/3 5 pep-461-percent-formatting-support-for-bytes-and-bytearray1343826
Ref: d261343826
Ref: whatsnew/3 5 whatsnew-pep-4611343826
Ref: d0e1343826
Ref: PEP 461 - percent formatting support for bytes and bytearray-Footnote-11345359
Ref: PEP 461 - percent formatting support for bytes and bytearray-Footnote-21345401
Node: PEP 484 - Type Hints1345443
Ref: whatsnew/3 5 pep-484-type-hints1345664
Ref: d281345664
Ref: whatsnew/3 5 whatsnew-pep-4841345664
Ref: d0c1345664
Ref: PEP 484 - Type Hints-Footnote-11347297
Ref: PEP 484 - Type Hints-Footnote-21347339
Ref: PEP 484 - Type Hints-Footnote-31347381
Ref: PEP 484 - Type Hints-Footnote-41347411
Ref: PEP 484 - Type Hints-Footnote-51347453
Node: PEP 471 - os scandir function -- a better and faster directory iterator1347495
Ref: whatsnew/3 5 pep-471-os-scandir-function-a-better-and-faster-directory-iterator1347701
Ref: d291347701
Ref: whatsnew/3 5 whatsnew-pep-4711347701
Ref: d171347701
Ref: PEP 471 - os scandir function -- a better and faster directory iterator-Footnote-11349035
Ref: PEP 471 - os scandir function -- a better and faster directory iterator-Footnote-21349077
Node: PEP 475 Retry system calls failing with EINTR1349119
Ref: whatsnew/3 5 pep-475-retry-system-calls-failing-with-eintr1349360
Ref: d2b1349360
Ref: whatsnew/3 5 whatsnew-pep-4751349360
Ref: d2c1349360
Ref: PEP 475 Retry system calls failing with EINTR-Footnote-11352424
Ref: PEP 475 Retry system calls failing with EINTR-Footnote-21352466
Node: PEP 479 Change StopIteration handling inside generators1352508
Ref: whatsnew/3 5 pep-479-change-stopiteration-handling-inside-generators1352729
Ref: d521352729
Ref: whatsnew/3 5 whatsnew-pep-4791352729
Ref: cc61352729
Ref: PEP 479 Change StopIteration handling inside generators-Footnote-11354656
Ref: PEP 479 Change StopIteration handling inside generators-Footnote-21354698
Node: PEP 485 A function for testing approximate equality1354740
Ref: whatsnew/3 5 pep-485-a-function-for-testing-approximate-equality1354978
Ref: d541354978
Ref: whatsnew/3 5 whatsnew-pep-4851354978
Ref: d551354978
Ref: PEP 485 A function for testing approximate equality-Footnote-11356154
Ref: PEP 485 A function for testing approximate equality-Footnote-21356196
Node: PEP 486 Make the Python Launcher aware of virtual environments1356238
Ref: whatsnew/3 5 pep-486-make-the-python-launcher-aware-of-virtual-environments1356453
Ref: d581356453
Ref: whatsnew/3 5 whatsnew-pep-4861356453
Ref: d591356453
Ref: PEP 486 Make the Python Launcher aware of virtual environments-Footnote-11357020
Ref: PEP 486 Make the Python Launcher aware of virtual environments-Footnote-21357062
Ref: PEP 486 Make the Python Launcher aware of virtual environments-Footnote-31357104
Node: PEP 488 Elimination of PYO files1357146
Ref: whatsnew/3 5 pep-488-elimination-of-pyo-files1357361
Ref: d5a1357361
Ref: whatsnew/3 5 whatsnew-pep-4881357361
Ref: d131357361
Ref: PEP 488 Elimination of PYO files-Footnote-11358220
Ref: PEP 488 Elimination of PYO files-Footnote-21358262
Node: PEP 489 Multi-phase extension module initialization1358304
Ref: whatsnew/3 5 pep-489-multi-phase-extension-module-initialization1358448
Ref: d5d1358448
Ref: whatsnew/3 5 whatsnew-pep-4891358448
Ref: d141358448
Ref: PEP 489 Multi-phase extension module initialization-Footnote-11359208
Ref: PEP 489 Multi-phase extension module initialization-Footnote-21359250
Ref: PEP 489 Multi-phase extension module initialization-Footnote-31359292
Node: 其他語言更動<8>1359334
Ref: whatsnew/3 5 other-language-changes1359469
Ref: d5e1359469
Ref: 其他語言更動<8>-Footnote-11360453
Ref: 其他語言更動<8>-Footnote-21360518
Ref: 其他語言更動<8>-Footnote-31360583
Ref: 其他語言更動<8>-Footnote-41360648
Ref: 其他語言更動<8>-Footnote-51360713
Ref: 其他語言更動<8>-Footnote-61360778
Ref: 其他語言更動<8>-Footnote-71360843
Node: 新增模組<4>1360908
Ref: whatsnew/3 5 new-modules1361046
Ref: d601361046
Node: typing<10>1361134
Ref: whatsnew/3 5 typing1361214
Ref: d611361214
Node: zipapp<2>1361424
Ref: whatsnew/3 5 whatsnew-zipapp1361504
Ref: d0d1361504
Ref: whatsnew/3 5 zipapp1361504
Ref: d621361504
Ref: zipapp<2>-Footnote-11362211
Ref: zipapp<2>-Footnote-21362253
Ref: zipapp<2>-Footnote-31362320
Ref: zipapp<2>-Footnote-41362385
Node: 改進的模組<8>1362427
Ref: whatsnew/3 5 improved-modules1362570
Ref: d631362570
Node: argparse<4>1364266
Ref: whatsnew/3 5 argparse1364352
Ref: d641364352
Ref: argparse<4>-Footnote-11364675
Node: asyncio<10>1364740
Ref: whatsnew/3 5 asyncio1364838
Ref: d671364838
Ref: asyncio<10>-Footnote-11368316
Ref: asyncio<10>-Footnote-21368381
Ref: asyncio<10>-Footnote-31368446
Node: bz21368491
Ref: whatsnew/3 5 bz21368581
Ref: d711368581
Ref: bz2-Footnote-11368836
Node: cgi1368901
Ref: whatsnew/3 5 cgi1368988
Ref: d731368988
Ref: cgi-Footnote-11369183
Node: cmath<2>1369248
Ref: whatsnew/3 5 cmath1369336
Ref: d741369336
Ref: cmath<2>-Footnote-11369550
Node: code1369615
Ref: whatsnew/3 5 code1369714
Ref: d751369714
Ref: code-Footnote-11369965
Node: collections<5>1370030
Ref: whatsnew/3 5 collections1370139
Ref: d771370139
Ref: whatsnew/3 5 whatsnew-ordereddict1370180
Ref: d151370180
Ref: collections<5>-Footnote-11371456
Ref: collections<5>-Footnote-21371521
Ref: collections<5>-Footnote-31371586
Ref: collections<5>-Footnote-41371651
Ref: collections<5>-Footnote-51371716
Node: collections abc<3>1371781
Ref: whatsnew/3 5 collections-abc1371899
Ref: d801371899
Ref: collections abc<3>-Footnote-11372569
Ref: collections abc<3>-Footnote-21372634
Ref: collections abc<3>-Footnote-31372699
Ref: collections abc<3>-Footnote-41372764
Node: compileall<4>1372812
Ref: whatsnew/3 5 compileall1372937
Ref: d861372937
Ref: compileall<4>-Footnote-11373812
Ref: compileall<4>-Footnote-21373877
Ref: compileall<4>-Footnote-31373942
Node: concurrent futures<5>1374007
Ref: whatsnew/3 5 concurrent-futures1374129
Ref: d891374129
Ref: concurrent futures<5>-Footnote-11374629
Ref: concurrent futures<5>-Footnote-21374694
Node: configparser<5>1374759
Ref: whatsnew/3 5 configparser1374881
Ref: d8b1374881
Ref: configparser<5>-Footnote-11375839
Node: contextlib<5>1375904
Ref: whatsnew/3 5 contextlib1376011
Ref: d8c1376011
Ref: contextlib<5>-Footnote-11376625
Node: csv<3>1376690
Ref: whatsnew/3 5 csv1376791
Ref: d8f1376791
Ref: csv<3>-Footnote-11376995
Node: curses<4>1377060
Ref: whatsnew/3 5 curses1377154
Ref: d911377154
Ref: curses<4>-Footnote-11377430
Node: dbm<5>1377494
Ref: whatsnew/3 5 dbm1377589
Ref: d931377589
Ref: dbm<5>-Footnote-11377792
Node: difflib1377857
Ref: whatsnew/3 5 difflib1377955
Ref: d941377955
Ref: difflib-Footnote-11378491
Ref: difflib-Footnote-21378555
Node: distutils<7>1378620
Ref: whatsnew/3 5 distutils1378722
Ref: d971378722
Ref: distutils<7>-Footnote-11379173
Ref: distutils<7>-Footnote-21379237
Node: doctest<3>1379302
Ref: whatsnew/3 5 doctest1379405
Ref: d981379405
Ref: doctest<3>-Footnote-11379690
Node: email<3>1379755
Ref: whatsnew/3 5 email1379853
Ref: d9b1379853
Ref: email<3>-Footnote-11380964
Ref: email<3>-Footnote-21381029
Ref: email<3>-Footnote-31381094
Ref: email<3>-Footnote-41381153
Ref: email<3>-Footnote-51381212
Ref: email<3>-Footnote-61381277
Node: enum<7>1381342
Ref: whatsnew/3 5 enum1381445
Ref: da11381445
Ref: enum<7>-Footnote-11381842
Node: faulthandler<3>1381907
Ref: whatsnew/3 5 faulthandler1382014
Ref: da21382014
Ref: faulthandler<3>-Footnote-11382326
Node: functools<4>1382391
Ref: whatsnew/3 5 functools1382498
Ref: da61382498
Ref: whatsnew/3 5 whatsnew-lrucache1382537
Ref: d181382537
Ref: functools<4>-Footnote-11382763
Node: glob<3>1382828
Ref: whatsnew/3 5 glob1382927
Ref: da71382927
Ref: glob<3>-Footnote-11383179
Node: gzip<4>1383244
Ref: whatsnew/3 5 gzip1383336
Ref: da81383336
Ref: gzip<4>-Footnote-11383561
Node: heapq1383626
Ref: whatsnew/3 5 heapq1383718
Ref: da91383718
Ref: heapq-Footnote-11384364
Node: http<2>1384429
Ref: whatsnew/3 5 http1384528
Ref: dac1384528
Ref: http<2>-Footnote-11384774
Node: http client<3>1384839
Ref: whatsnew/3 5 http-client1384952
Ref: dad1384952
Ref: http client<3>-Footnote-11385702
Node: idlelib and IDLE<3>1385766
Ref: whatsnew/3 5 idlelib-and-idle1385882
Ref: db11385882
Node: imaplib<2>1386276
Ref: whatsnew/3 5 imaplib1386384
Ref: db21386384
Ref: imaplib<2>-Footnote-11387263
Ref: imaplib<2>-Footnote-21387327
Ref: imaplib<2>-Footnote-31387386
Ref: imaplib<2>-Footnote-41387445
Ref: imaplib<2>-Footnote-51387504
Ref: imaplib<2>-Footnote-61387569
Node: imghdr1387634
Ref: whatsnew/3 5 imghdr1387735
Ref: db51387735
Ref: imghdr-Footnote-11388023
Ref: imghdr-Footnote-21388055
Ref: imghdr-Footnote-31388120
Ref: imghdr-Footnote-41388163
Node: importlib<8>1388228
Ref: whatsnew/3 5 importlib1388329
Ref: db61388329
Ref: importlib<8>-Footnote-11389164
Ref: importlib<8>-Footnote-21389229
Ref: importlib<8>-Footnote-31389294
Node: inspect<7>1389359
Ref: whatsnew/3 5 inspect1389459
Ref: dba1389459
Ref: inspect<7>-Footnote-11391022
Ref: inspect<7>-Footnote-21391087
Ref: inspect<7>-Footnote-31391152
Ref: inspect<7>-Footnote-41391217
Ref: inspect<7>-Footnote-51391282
Ref: inspect<7>-Footnote-61391347
Ref: inspect<7>-Footnote-71391412
Ref: inspect<7>-Footnote-81391477
Node: io<5>1391542
Ref: whatsnew/3 5 io1391642
Ref: dc01391642
Ref: io<5>-Footnote-11391938
Node: ipaddress<4>1392003
Ref: whatsnew/3 5 ipaddress1392100
Ref: dc41392100
Ref: ipaddress<4>-Footnote-11393140
Ref: ipaddress<4>-Footnote-21393205
Node: json<2>1393270
Ref: whatsnew/3 5 json1393374
Ref: dc51393374
Ref: json<2>-Footnote-11393874
Ref: json<2>-Footnote-21393939
Node: linecache<2>1394004
Ref: whatsnew/3 5 linecache1394105
Ref: dc71394105
Ref: linecache<2>-Footnote-11394515
Node: locale<6>1394580
Ref: whatsnew/3 5 locale1394684
Ref: dca1394684
Ref: locale<6>-Footnote-11395255
Node: logging<5>1395320
Ref: whatsnew/3 5 logging1395416
Ref: dcc1395416
Ref: logging<5>-Footnote-11396392
Ref: logging<5>-Footnote-21396457
Node: lzma1396522
Ref: whatsnew/3 5 lzma1396616
Ref: dd31396616
Ref: lzma-Footnote-11396878
Node: math<8>1396943
Ref: whatsnew/3 5 math1397045
Ref: dd51397045
Ref: math<8>-Footnote-11397587
Ref: math<8>-Footnote-21397652
Ref: math<8>-Footnote-31397717
Node: multiprocessing<6>1397782
Ref: whatsnew/3 5 multiprocessing1397891
Ref: dd61397891
Ref: multiprocessing<6>-Footnote-11398141
Node: operator<2>1398206
Ref: whatsnew/3 5 operator1398314
Ref: dd81398314
Ref: operator<2>-Footnote-11398719
Ref: operator<2>-Footnote-21398784
Node: os<10>1398849
Ref: whatsnew/3 5 os1398950
Ref: ddd1398950
Ref: os<10>-Footnote-11400802
Ref: os<10>-Footnote-21400867
Ref: os<10>-Footnote-31400932
Ref: os<10>-Footnote-41400997
Ref: os<10>-Footnote-51401062
Ref: os<10>-Footnote-61401127
Node: pathlib<10>1401192
Ref: whatsnew/3 5 pathlib1401291
Ref: de51401291
Ref: pathlib<10>-Footnote-11402774
Ref: pathlib<10>-Footnote-21402839
Ref: pathlib<10>-Footnote-31402904
Ref: pathlib<10>-Footnote-41402969
Ref: pathlib<10>-Footnote-51403034
Node: pickle<3>1403099
Ref: whatsnew/3 5 pickle1403201
Ref: dee1403201
Ref: pickle<3>-Footnote-11403517
Node: poplib<2>1403582
Ref: whatsnew/3 5 poplib1403678
Ref: def1403678
Ref: poplib<2>-Footnote-11403920
Ref: poplib<2>-Footnote-21403979
Node: re<7>1404044
Ref: whatsnew/3 5 re1404142
Ref: df11404142
Ref: re<7>-Footnote-11405359
Ref: re<7>-Footnote-21405423
Ref: re<7>-Footnote-31405488
Ref: re<7>-Footnote-41405555
Node: readline<2>1405620
Ref: whatsnew/3 5 readline1405718
Ref: df21405718
Ref: readline<2>-Footnote-11405981
Node: selectors1406046
Ref: whatsnew/3 5 selectors1406148
Ref: df41406148
Ref: selectors-Footnote-11406368
Node: shutil<5>1406433
Ref: whatsnew/3 5 shutil1406533
Ref: df51406533
Ref: shutil<5>-Footnote-11407012
Ref: shutil<5>-Footnote-21407077
Node: signal<3>1407141
Ref: whatsnew/3 5 signal1407240
Ref: df61407240
Ref: signal<3>-Footnote-11407701
Ref: signal<3>-Footnote-21407766
Node: smtpd<2>1407831
Ref: whatsnew/3 5 smtpd1407931
Ref: df71407931
Ref: smtpd<2>-Footnote-11409567
Ref: smtpd<2>-Footnote-21409632
Ref: smtpd<2>-Footnote-31409691
Ref: smtpd<2>-Footnote-41409756
Ref: smtpd<2>-Footnote-51409815
Ref: smtpd<2>-Footnote-61409880
Node: smtplib<2>1409945
Ref: whatsnew/3 5 smtplib1410042
Ref: df81410042
Ref: smtplib<2>-Footnote-11410663
Ref: smtplib<2>-Footnote-21410728
Ref: smtplib<2>-Footnote-31410793
Ref: smtplib<2>-Footnote-41410852
Node: sndhdr1410917
Ref: whatsnew/3 5 sndhdr1411015
Ref: dfd1411015
Ref: sndhdr-Footnote-11411218
Node: socket<8>1411283
Ref: whatsnew/3 5 socket1411377
Ref: dfe1411377
Ref: socket<8>-Footnote-11412346
Ref: socket<8>-Footnote-21412411
Ref: socket<8>-Footnote-31412476
Ref: socket<8>-Footnote-41412541
Node: ssl<9>1412606
Ref: whatsnew/3 5 ssl1412704
Ref: e021412704
Node: Memory BIO Support1412833
Ref: whatsnew/3 5 memory-bio-support1412949
Ref: e031412949
Ref: whatsnew/3 5 whatsnew-sslmemorybio1412949
Ref: d161412949
Ref: Memory BIO Support-Footnote-11413832
Node: Application-Layer Protocol Negotiation Support1413897
Ref: whatsnew/3 5 application-layer-protocol-negotiation-support1414035
Ref: e051414035
Ref: Application-Layer Protocol Negotiation Support-Footnote-11414746
Ref: Application-Layer Protocol Negotiation Support-Footnote-21414811
Node: Other Changes1414870
Ref: whatsnew/3 5 other-changes1414981
Ref: e091414981
Ref: Other Changes-Footnote-11416565
Ref: Other Changes-Footnote-21416630
Ref: Other Changes-Footnote-31416695
Ref: Other Changes-Footnote-41416760
Ref: Other Changes-Footnote-51416819
Ref: Other Changes-Footnote-61416884
Ref: Other Changes-Footnote-71416949
Ref: Other Changes-Footnote-81417014
Node: sqlite3<8>1417079
Ref: whatsnew/3 5 sqlite31417181
Ref: e121417181
Ref: sqlite3<8>-Footnote-11417510
Ref: sqlite3<8>-Footnote-21417575
Node: subprocess<4>1417640
Ref: whatsnew/3 5 subprocess1417743
Ref: e141417743
Ref: whatsnew/3 5 whatsnew-subprocess1417743
Ref: d191417743
Ref: subprocess<4>-Footnote-11418756
Node: sys<10>1418821
Ref: whatsnew/3 5 sys1418926
Ref: e161418926
Ref: sys<10>-Footnote-11419576
Ref: sys<10>-Footnote-21419641
Node: sysconfig<2>1419706
Ref: whatsnew/3 5 sysconfig1419808
Ref: e171419808
Ref: sysconfig<2>-Footnote-11420041
Node: tarfile<6>1420106
Ref: whatsnew/3 5 tarfile1420213
Ref: e181420213
Ref: tarfile<6>-Footnote-11421124
Ref: tarfile<6>-Footnote-21421189
Ref: tarfile<6>-Footnote-31421254
Node: threading<6>1421319
Ref: whatsnew/3 5 threading1421421
Ref: e1e1421421
Ref: threading<6>-Footnote-11421673
Node: time<7>1421738
Ref: whatsnew/3 5 time1421839
Ref: e201421839
Ref: time<7>-Footnote-11422016
Node: timeit<2>1422081
Ref: whatsnew/3 5 timeit1422180
Ref: e211422180
Ref: timeit<2>-Footnote-11422645
Ref: timeit<2>-Footnote-21422710
Node: tkinter<8>1422774
Ref: whatsnew/3 5 tkinter1422878
Ref: e231422878
Ref: tkinter<8>-Footnote-11423210
Node: traceback<5>1423275
Ref: whatsnew/3 5 traceback1423378
Ref: e241423378
Ref: whatsnew/3 5 whatsnew-traceback1423378
Ref: d1a1423378
Ref: traceback<5>-Footnote-11423971
Ref: traceback<5>-Footnote-21424036
Ref: traceback<5>-Footnote-31424101
Node: types<5>1424166
Ref: whatsnew/3 5 types1424273
Ref: e2b1424273
Ref: types<5>-Footnote-11424717
Ref: types<5>-Footnote-21424782
Node: unicodedata<8>1424847
Ref: whatsnew/3 5 unicodedata1424953
Ref: e2e1424953
Ref: unicodedata<8>-Footnote-11425104
Node: unittest<8>1425155
Ref: whatsnew/3 5 unittest1425269
Ref: e2f1425269
Ref: unittest<8>-Footnote-11426063
Ref: unittest<8>-Footnote-21426128
Ref: unittest<8>-Footnote-31426193
Node: unittest mock<3>1426258
Ref: whatsnew/3 5 unittest-mock1426367
Ref: e311426367
Ref: unittest mock<3>-Footnote-11427292
Ref: unittest mock<3>-Footnote-21427357
Ref: unittest mock<3>-Footnote-31427422
Ref: unittest mock<3>-Footnote-41427487
Ref: unittest mock<3>-Footnote-51427552
Ref: unittest mock<3>-Footnote-61427617
Node: urllib<2>1427682
Ref: whatsnew/3 5 urllib1427787
Ref: e351427787
Ref: urllib<2>-Footnote-11428947
Ref: urllib<2>-Footnote-21429012
Ref: urllib<2>-Footnote-31429076
Ref: urllib<2>-Footnote-41429141
Ref: urllib<2>-Footnote-51429206
Ref: urllib<2>-Footnote-61429265
Ref: urllib<2>-Footnote-71429324
Ref: urllib<2>-Footnote-81429383
Node: wsgiref1429448
Ref: whatsnew/3 5 wsgiref1429546
Ref: e391429546
Ref: wsgiref-Footnote-11429784
Node: xmlrpc<2>1429848
Ref: whatsnew/3 5 xmlrpc1429944
Ref: e3b1429944
Ref: xmlrpc<2>-Footnote-11430314
Ref: xmlrpc<2>-Footnote-21430379
Node: xml sax1430444
Ref: whatsnew/3 5 xml-sax1430543
Ref: e3c1430543
Ref: xml sax-Footnote-11430876
Ref: xml sax-Footnote-21430940
Node: zipfile<4>1431005
Ref: whatsnew/3 5 zipfile1431086
Ref: e3f1431086
Ref: zipfile<4>-Footnote-11431426
Ref: zipfile<4>-Footnote-21431491
Node: Other module-level changes1431556
Ref: whatsnew/3 5 other-module-level-changes1431696
Ref: e401431696
Ref: Other module-level changes-Footnote-11432023
Node: 最佳化<8>1432088
Ref: whatsnew/3 5 optimizations1432236
Ref: e411432236
Ref: 最佳化<8>-Footnote-11435278
Ref: 最佳化<8>-Footnote-21435343
Ref: 最佳化<8>-Footnote-31435408
Ref: 最佳化<8>-Footnote-41435473
Ref: 最佳化<8>-Footnote-51435538
Ref: 最佳化<8>-Footnote-61435603
Ref: 最佳化<8>-Footnote-71435668
Ref: 最佳化<8>-Footnote-81435733
Ref: 最佳化<8>-Footnote-91435798
Ref: 最佳化<8>-Footnote-101435863
Ref: 最佳化<8>-Footnote-111435929
Ref: 最佳化<8>-Footnote-121435995
Ref: 最佳化<8>-Footnote-131436061
Ref: 最佳化<8>-Footnote-141436127
Ref: 最佳化<8>-Footnote-151436193
Ref: 最佳化<8>-Footnote-161436259
Ref: 最佳化<8>-Footnote-171436325
Ref: 最佳化<8>-Footnote-181436391
Ref: 最佳化<8>-Footnote-191436457
Ref: 最佳化<8>-Footnote-201436523
Node: Build and C API Changes<3>1436589
Ref: whatsnew/3 5 build-and-c-api-changes1436724
Ref: e4e1436724
Ref: Build and C API Changes<3>-Footnote-11440280
Ref: Build and C API Changes<3>-Footnote-21440345
Ref: Build and C API Changes<3>-Footnote-31440410
Ref: Build and C API Changes<3>-Footnote-41440475
Ref: Build and C API Changes<3>-Footnote-51440540
Ref: Build and C API Changes<3>-Footnote-61440605
Ref: Build and C API Changes<3>-Footnote-71440647
Ref: Build and C API Changes<3>-Footnote-81440712
Ref: Build and C API Changes<3>-Footnote-91440777
Ref: Build and C API Changes<3>-Footnote-101440819
Node: 已棄用<10>1440925
Ref: whatsnew/3 5 deprecated1441060
Ref: e591441060
Node: New Keywords1441316
Ref: whatsnew/3 5 new-keywords1441416
Ref: e5a1441416
Ref: New Keywords-Footnote-11441690
Node: Deprecated Python Behavior<2>1441732
Ref: whatsnew/3 5 deprecated-python-behavior1441870
Ref: e5b1441870
Node: Unsupported Operating Systems1442285
Ref: whatsnew/3 5 unsupported-operating-systems1442461
Ref: e5c1442461
Ref: Unsupported Operating Systems-Footnote-11442702
Node: Deprecated Python modules functions and methods<3>1442744
Ref: whatsnew/3 5 deprecated-python-modules-functions-and-methods1442882
Ref: e5d1442882
Ref: Deprecated Python modules functions and methods<3>-Footnote-11445794
Ref: Deprecated Python modules functions and methods<3>-Footnote-21445859
Ref: Deprecated Python modules functions and methods<3>-Footnote-31445923
Ref: Deprecated Python modules functions and methods<3>-Footnote-41445988
Ref: Deprecated Python modules functions and methods<3>-Footnote-51446053
Ref: Deprecated Python modules functions and methods<3>-Footnote-61446118
Ref: Deprecated Python modules functions and methods<3>-Footnote-71446183
Ref: Deprecated Python modules functions and methods<3>-Footnote-81446248
Node: 已移除<8>1446313
Ref: whatsnew/3 5 removed1446443
Ref: e621446443
Node: API and Feature Removals<4>1446542
Ref: whatsnew/3 5 api-and-feature-removals1446618
Ref: e631446618
Ref: API and Feature Removals<4>-Footnote-11447473
Ref: API and Feature Removals<4>-Footnote-21447537
Node: Porting to Python 3 51447602
Ref: whatsnew/3 5 porting-to-python-3-51447750
Ref: e641447750
Node: Changes in Python behavior<2>1448091
Ref: whatsnew/3 5 changes-in-python-behavior1448215
Ref: e651448215
Node: Changes in the Python API<7>1448625
Ref: whatsnew/3 5 changes-in-the-python-api1448779
Ref: e661448779
Ref: Changes in the Python API<7>-Footnote-11455685
Ref: Changes in the Python API<7>-Footnote-21455727
Ref: Changes in the Python API<7>-Footnote-31455792
Ref: Changes in the Python API<7>-Footnote-41455857
Ref: Changes in the Python API<7>-Footnote-51455922
Ref: Changes in the Python API<7>-Footnote-61455987
Ref: Changes in the Python API<7>-Footnote-71456052
Ref: Changes in the Python API<7>-Footnote-81456117
Ref: Changes in the Python API<7>-Footnote-91456182
Ref: Changes in the Python API<7>-Footnote-101456247
Ref: Changes in the Python API<7>-Footnote-111456313
Ref: Changes in the Python API<7>-Footnote-121456379
Ref: Changes in the Python API<7>-Footnote-131456444
Ref: Changes in the Python API<7>-Footnote-141456487
Ref: Changes in the Python API<7>-Footnote-151456547
Ref: Changes in the Python API<7>-Footnote-161456613
Ref: Changes in the Python API<7>-Footnote-171456679
Ref: Changes in the Python API<7>-Footnote-181456745
Node: C API 中的改動<6>1456810
Ref: whatsnew/3 5 changes-in-the-c-api1456926
Ref: e6f1456926
Ref: C API 中的改動<6>-Footnote-11458209
Ref: C API 中的改動<6>-Footnote-21458274
Ref: C API 中的改動<6>-Footnote-31458339
Node: Python 3 5 4 中顯著的變更1458381
Ref: whatsnew/3 5 notable-changes-in-python-3-5-41458508
Ref: e731458508
Node: New make regen-all build target<2>1458739
Ref: whatsnew/3 5 new-make-regen-all-build-target1458887
Ref: e741458887
Ref: New make regen-all build target<2>-Footnote-11459682
Ref: New make regen-all build target<2>-Footnote-21459750
Node: Removal of make touch build target<2>1459815
Ref: whatsnew/3 5 removal-of-make-touch-build-target1459963
Ref: e751459963
Ref: Removal of make touch build target<2>-Footnote-11460397
Node: Python 3 4 有什麼新功能<2>1460462
Ref: whatsnew/3 4 doc1460635
Ref: e761460635
Ref: whatsnew/3 4 what-s-new-in-python-3-41460635
Ref: e771460635
Ref: Python 3 4 有什麼新功能<2>-Footnote-11461363
Ref: Python 3 4 有什麼新功能<2>-Footnote-21461423
Node: Summary -- Release Highlights<3>1461465
Ref: whatsnew/3 4 summary-release-highlights1461590
Ref: e781461590
Ref: Summary -- Release Highlights<3>-Footnote-11465874
Ref: Summary -- Release Highlights<3>-Footnote-21465916
Ref: Summary -- Release Highlights<3>-Footnote-31465958
Ref: Summary -- Release Highlights<3>-Footnote-41466023
Ref: Summary -- Release Highlights<3>-Footnote-51466065
Ref: Summary -- Release Highlights<3>-Footnote-61466130
Ref: Summary -- Release Highlights<3>-Footnote-71466172
Ref: Summary -- Release Highlights<3>-Footnote-81466214
Ref: Summary -- Release Highlights<3>-Footnote-91466256
Ref: Summary -- Release Highlights<3>-Footnote-101466298
Ref: Summary -- Release Highlights<3>-Footnote-111466341
Ref: Summary -- Release Highlights<3>-Footnote-121466384
Ref: Summary -- Release Highlights<3>-Footnote-131466427
Ref: Summary -- Release Highlights<3>-Footnote-141466470
Ref: Summary -- Release Highlights<3>-Footnote-151466513
Ref: Summary -- Release Highlights<3>-Footnote-161466578
Ref: Summary -- Release Highlights<3>-Footnote-171466644
Ref: Summary -- Release Highlights<3>-Footnote-181466687
Ref: Summary -- Release Highlights<3>-Footnote-191466730
Ref: Summary -- Release Highlights<3>-Footnote-201466796
Ref: Summary -- Release Highlights<3>-Footnote-211466842
Ref: Summary -- Release Highlights<3>-Footnote-221466885
Ref: Summary -- Release Highlights<3>-Footnote-231466928
Ref: Summary -- Release Highlights<3>-Footnote-241466994
Ref: Summary -- Release Highlights<3>-Footnote-251467037
Node: New Features<9>1467080
Ref: whatsnew/3 4 new-features1467226
Ref: e931467226
Node: PEP 453 Explicit Bootstrapping of PIP in Python Installations1467710
Ref: whatsnew/3 4 pep-453-explicit-bootstrapping-of-pip-in-python-installations1467890
Ref: e941467890
Ref: whatsnew/3 4 whatsnew-pep-4531467890
Ref: e791467890
Node: Bootstrapping pip By Default1468104
Ref: whatsnew/3 4 bootstrapping-pip-by-default1468260
Ref: e951468260
Ref: Bootstrapping pip By Default-Footnote-11471162
Ref: Bootstrapping pip By Default-Footnote-21471204
Node: Documentation Changes1471291
Ref: whatsnew/3 4 documentation-changes1471447
Ref: e981471447
Ref: Documentation Changes-Footnote-11472375
Ref: Documentation Changes-Footnote-21472412
Node: PEP 446 Newly Created File Descriptors Are Non-Inheritable1472454
Ref: whatsnew/3 4 pep-446-newly-created-file-descriptors-are-non-inheritable1472673
Ref: e9c1472673
Ref: whatsnew/3 4 whatsnew-pep-4461472673
Ref: e7a1472673
Ref: PEP 446 Newly Created File Descriptors Are Non-Inheritable-Footnote-11473686
Ref: PEP 446 Newly Created File Descriptors Are Non-Inheritable-Footnote-21473728
Node: Improvements to Codec Handling1473770
Ref: whatsnew/3 4 codec-handling-improvements1473975
Ref: e7c1473975
Ref: whatsnew/3 4 improvements-to-codec-handling1473975
Ref: ea41473975
Ref: Improvements to Codec Handling-Footnote-11478191
Ref: Improvements to Codec Handling-Footnote-21478255
Ref: Improvements to Codec Handling-Footnote-31478320
Ref: Improvements to Codec Handling-Footnote-41478385
Node: PEP 451 A ModuleSpec Type for the Import System1478450
Ref: whatsnew/3 4 pep-451-a-modulespec-type-for-the-import-system1478618
Ref: ea91478618
Ref: whatsnew/3 4 whatsnew-pep-4511478618
Ref: e7d1478618
Ref: PEP 451 A ModuleSpec Type for the Import System-Footnote-11479570
Ref: PEP 451 A ModuleSpec Type for the Import System-Footnote-21479612
Node: 其他語言更動<9>1479692
Ref: whatsnew/3 4 other-language-changes1479821
Ref: eab1479821
Ref: 其他語言更動<9>-Footnote-11482451
Ref: 其他語言更動<9>-Footnote-21482516
Ref: 其他語言更動<9>-Footnote-31482581
Ref: 其他語言更動<9>-Footnote-41482646
Ref: 其他語言更動<9>-Footnote-51482713
Ref: 其他語言更動<9>-Footnote-61482778
Ref: 其他語言更動<9>-Footnote-71482843
Ref: 其他語言更動<9>-Footnote-81482908
Ref: 其他語言更動<9>-Footnote-91482973
Ref: 其他語言更動<9>-Footnote-101483038
Ref: 其他語言更動<9>-Footnote-111483104
Ref: 其他語言更動<9>-Footnote-121483147
Node: 新模組<5>1483213
Ref: whatsnew/3 4 new-modules1483345
Ref: eb01483345
Node: asyncio<11>1483566
Ref: whatsnew/3 4 asyncio1483647
Ref: eb11483647
Ref: whatsnew/3 4 whatsnew-asyncio1483647
Ref: e7f1483647
Ref: asyncio<11>-Footnote-11484235
Ref: asyncio<11>-Footnote-21484277
Node: ensurepip<2>1484319
Ref: whatsnew/3 4 ensurepip1484416
Ref: eb21484416
Ref: whatsnew/3 4 whatsnew-ensurepip1484416
Ref: e801484416
Ref: ensurepip<2>-Footnote-11485690
Node: enum<8>1485732
Ref: whatsnew/3 4 enum1485829
Ref: eb31485829
Ref: whatsnew/3 4 whatsnew-enum1485829
Ref: e811485829
Ref: enum<8>-Footnote-11486398
Ref: enum<8>-Footnote-21486440
Node: pathlib<11>1486482
Ref: whatsnew/3 4 pathlib1486579
Ref: eb41486579
Ref: whatsnew/3 4 whatsnew-pathlib1486579
Ref: e821486579
Ref: pathlib<11>-Footnote-11487190
Node: selectors<2>1487232
Ref: whatsnew/3 4 selectors1487335
Ref: eb51487335
Ref: whatsnew/3 4 whatsnew-selectors1487335
Ref: e831487335
Ref: selectors<2>-Footnote-11487595
Node: statistics<6>1487637
Ref: whatsnew/3 4 statistics1487743
Ref: eb61487743
Ref: whatsnew/3 4 whatsnew-statistics1487743
Ref: e841487743
Ref: statistics<6>-Footnote-11488199
Ref: statistics<6>-Footnote-21488241
Node: tracemalloc<4>1488283
Ref: whatsnew/3 4 tracemalloc1488368
Ref: eb71488368
Ref: whatsnew/3 4 whatsnew-tracemalloc1488368
Ref: e851488368
Ref: tracemalloc<4>-Footnote-11489025
Ref: tracemalloc<4>-Footnote-21489067
Node: 改進的模組<9>1489109
Ref: whatsnew/3 4 improved-modules1489246
Ref: eb81489246
Node: abc1490567
Ref: whatsnew/3 4 abc1490641
Ref: eb91490641
Ref: abc-Footnote-11491164
Ref: abc-Footnote-21491229
Node: aifc<2>1491294
Ref: whatsnew/3 4 aifc1491388
Ref: ebd1491388
Ref: aifc<2>-Footnote-11491998
Ref: aifc<2>-Footnote-21492063
Ref: aifc<2>-Footnote-31492128
Node: argparse<5>1492192
Ref: whatsnew/3 4 argparse1492290
Ref: ebe1492290
Ref: argparse<5>-Footnote-11492538
Node: audioop1492603
Ref: whatsnew/3 4 audioop1492703
Ref: ec01492703
Ref: audioop-Footnote-11493227
Ref: audioop-Footnote-21493292
Ref: audioop-Footnote-31493357
Node: base64<3>1493422
Ref: whatsnew/3 4 base641493525
Ref: ec11493525
Ref: base64<3>-Footnote-11494358
Ref: base64<3>-Footnote-21494423
Node: collections<6>1494488
Ref: whatsnew/3 4 collections1494592
Ref: ec61494592
Ref: collections<6>-Footnote-11494924
Node: colorsys1494989
Ref: whatsnew/3 4 colorsys1495097
Ref: ec81495097
Ref: colorsys-Footnote-11495466
Node: contextlib<6>1495531
Ref: whatsnew/3 4 contextlib1495631
Ref: ec91495631
Ref: contextlib<6>-Footnote-11496816
Ref: contextlib<6>-Footnote-21496881
Ref: contextlib<6>-Footnote-31496946
Node: dbm<6>1497011
Ref: whatsnew/3 4 dbm1497109
Ref: ecd1497109
Ref: dbm<6>-Footnote-11497458
Node: dis<4>1497523
Ref: whatsnew/3 4 dis1497618
Ref: ecf1497618
Ref: dis<4>-Footnote-11500228
Ref: dis<4>-Footnote-21500293
Ref: dis<4>-Footnote-31500358
Node: doctest<4>1500423
Ref: whatsnew/3 4 doctest1500520
Ref: ed61500520
Ref: doctest<4>-Footnote-11501289
Ref: doctest<4>-Footnote-21501354
Ref: doctest<4>-Footnote-31501419
Node: email<4>1501483
Ref: whatsnew/3 4 email1501581
Ref: ed91501581
Ref: whatsnew/3 4 whatsnew-email-contentmanager1502831
Ref: e891502831
Ref: email<4>-Footnote-11503757
Ref: email<4>-Footnote-21503822
Ref: email<4>-Footnote-31503887
Ref: email<4>-Footnote-41503952
Node: filecmp1504017
Ref: whatsnew/3 4 filecmp1504117
Ref: ee11504117
Ref: filecmp-Footnote-11504863
Ref: filecmp-Footnote-21504928
Node: functools<5>1504993
Ref: whatsnew/3 4 functools1505090
Ref: ee51505090
Ref: whatsnew/3 4 whatsnew-singledispatch1505539
Ref: e861505539
Ref: functools<5>-Footnote-11506491
Ref: functools<5>-Footnote-21506555
Ref: functools<5>-Footnote-31506597
Ref: functools<5>-Footnote-41506662
Node: gc<6>1506727
Ref: whatsnew/3 4 gc1506824
Ref: ee71506824
Ref: gc<6>-Footnote-11507092
Node: glob<4>1507157
Ref: whatsnew/3 4 glob1507252
Ref: ee81507252
Ref: glob<4>-Footnote-11507558
Node: hashlib<6>1507622
Ref: whatsnew/3 4 hashlib1507719
Ref: eea1507719
Ref: hashlib<6>-Footnote-11508352
Ref: hashlib<6>-Footnote-21508397
Ref: hashlib<6>-Footnote-31508462
Node: hmac<3>1508527
Ref: whatsnew/3 4 hmac1508621
Ref: eec1508621
Ref: hmac<3>-Footnote-11509649
Ref: hmac<3>-Footnote-21509714
Ref: hmac<3>-Footnote-31509779
Ref: hmac<3>-Footnote-41509821
Node: html1509886
Ref: whatsnew/3 4 html1509977
Ref: ef11509977
Ref: html-Footnote-11510736
Ref: html-Footnote-21510800
Ref: html-Footnote-31510865
Node: http<3>1510930
Ref: whatsnew/3 4 http1511030
Ref: ef21511030
Ref: http<3>-Footnote-11511673
Ref: http<3>-Footnote-21511738
Node: idlelib 與 IDLE1511803
Ref: whatsnew/3 4 idlelib-and-idle1511911
Ref: ef51511911
Node: importlib<9>1512306
Ref: whatsnew/3 4 importlib1512417
Ref: ef61512417
Ref: importlib<9>-Footnote-11514401
Ref: importlib<9>-Footnote-21514466
Ref: importlib<9>-Footnote-31514531
Ref: importlib<9>-Footnote-41514596
Ref: importlib<9>-Footnote-51514661
Ref: importlib<9>-Footnote-61514726
Ref: importlib<9>-Footnote-71514791
Node: inspect<8>1514856
Ref: whatsnew/3 4 inspect1514963
Ref: efd1514963
Ref: inspect<8>-Footnote-11516673
Ref: inspect<8>-Footnote-21516738
Ref: inspect<8>-Footnote-31516803
Ref: inspect<8>-Footnote-41516868
Ref: inspect<8>-Footnote-51516933
Ref: inspect<8>-Footnote-61516998
Node: ipaddress<5>1517063
Ref: whatsnew/3 4 ipaddress1517168
Ref: f011517168
Ref: ipaddress<5>-Footnote-11517696
Node: logging<6>1517761
Ref: whatsnew/3 4 logging1517866
Ref: f031517866
Ref: logging<6>-Footnote-11518998
Ref: logging<6>-Footnote-21519062
Ref: logging<6>-Footnote-31519127
Node: marshal<2>1519192
Ref: whatsnew/3 4 marshal1519292
Ref: f091519292
Ref: whatsnew/3 4 whatsnew-marshal-31519292
Ref: e7e1519292
Ref: marshal<2>-Footnote-11519969
Ref: marshal<2>-Footnote-21520034
Node: mmap<3>1520099
Ref: whatsnew/3 4 mmap1520207
Ref: f0a1520207
Ref: mmap<3>-Footnote-11520379
Node: multiprocessing<7>1520443
Ref: whatsnew/3 4 multiprocessing1520552
Ref: f0b1520552
Ref: whatsnew/3 4 whatsnew-multiprocessing-no-fork1520605
Ref: e881520605
Ref: multiprocessing<7>-Footnote-11522417
Ref: multiprocessing<7>-Footnote-21522481
Ref: multiprocessing<7>-Footnote-31522546
Ref: multiprocessing<7>-Footnote-41522610
Node: operator<3>1522675
Ref: whatsnew/3 4 operator1522783
Ref: f0f1522783
Ref: operator<3>-Footnote-11523336
Ref: operator<3>-Footnote-21523378
Ref: operator<3>-Footnote-31523443
Node: os<11>1523508
Ref: whatsnew/3 4 os1523604
Ref: f111523604
Ref: os<11>-Footnote-11525049
Ref: os<11>-Footnote-21525114
Ref: os<11>-Footnote-31525179
Ref: os<11>-Footnote-41525243
Node: pdb<6>1525308
Ref: whatsnew/3 4 pdb1525402
Ref: f171525402
Ref: pdb<6>-Footnote-11526396
Ref: pdb<6>-Footnote-21526461
Node: pickle<4>1526526
Ref: whatsnew/3 4 pickle1526625
Ref: f1a1526625
Ref: whatsnew/3 4 whatsnew-protocol-41526625
Ref: e871526625
Ref: pickle<4>-Footnote-11527201
Node: plistlib<2>1527243
Ref: whatsnew/3 4 plistlib1527345
Ref: f1b1527345
Ref: plistlib<2>-Footnote-11527881
Node: poplib<3>1527946
Ref: whatsnew/3 4 poplib1528048
Ref: f1e1528048
Ref: poplib<3>-Footnote-11528438
Node: pprint<4>1528502
Ref: whatsnew/3 4 pprint1528596
Ref: f211528596
Ref: pprint<4>-Footnote-11529212
Ref: pprint<4>-Footnote-21529277
Node: pty1529342
Ref: whatsnew/3 4 pty1529435
Ref: f241529435
Node: pydoc<4>1529628
Ref: whatsnew/3 4 pydoc1529717
Ref: f261529717
Ref: pydoc<4>-Footnote-11530774
Ref: pydoc<4>-Footnote-21530839
Node: re<8>1530904
Ref: whatsnew/3 4 re1530998
Ref: f271530998
Ref: re<8>-Footnote-11531741
Ref: re<8>-Footnote-21531806
Ref: re<8>-Footnote-31531871
Node: resource1531936
Ref: whatsnew/3 4 resource1532028
Ref: f2b1532028
Ref: resource-Footnote-11532881
Ref: resource-Footnote-21532946
Ref: resource-Footnote-31533011
Node: select1533076
Ref: whatsnew/3 4 select1533172
Ref: f351533172
Ref: select-Footnote-11533681
Ref: select-Footnote-21533746
Node: shelve<2>1533811
Ref: whatsnew/3 4 shelve1533908
Ref: f3c1533908
Ref: shelve<2>-Footnote-11534180
Node: shutil<6>1534245
Ref: whatsnew/3 4 shutil1534344
Ref: f3e1534344
Ref: shutil<6>-Footnote-11534717
Node: smtpd<3>1534784
Ref: whatsnew/3 4 smtpd1534884
Ref: f411534884
Ref: smtpd<3>-Footnote-11535244
Node: smtplib<3>1535309
Ref: whatsnew/3 4 smtplib1535409
Ref: f421535409
Ref: smtplib<3>-Footnote-11535771
Node: socket<9>1535835
Ref: whatsnew/3 4 socket1535937
Ref: f441535937
Ref: socket<9>-Footnote-11536716
Ref: socket<9>-Footnote-21536781
Node: sqlite3<9>1536845
Ref: whatsnew/3 4 sqlite31536944
Ref: f481536944
Ref: sqlite3<9>-Footnote-11537235
Ref: sqlite3<9>-Footnote-21537275
Node: ssl<10>1537340
Ref: whatsnew/3 4 ssl1537434
Ref: f491537434
Ref: whatsnew/3 4 whatsnew-tls-11-121537463
Ref: e8b1537463
Ref: whatsnew/3 4 whatsnew34-sslcontext1537733
Ref: e8e1537733
Ref: whatsnew/3 4 whatsnew34-win-cert-store1540401
Ref: e8c1540401
Ref: whatsnew/3 4 whatsnew34-sni1540655
Ref: e8d1540655
Ref: ssl<10>-Footnote-11541104
Ref: ssl<10>-Footnote-21541169
Ref: ssl<10>-Footnote-31541234
Ref: ssl<10>-Footnote-41541299
Ref: ssl<10>-Footnote-51541364
Ref: ssl<10>-Footnote-61541429
Ref: ssl<10>-Footnote-71541493
Ref: ssl<10>-Footnote-81541558
Ref: ssl<10>-Footnote-91541623
Ref: ssl<10>-Footnote-101541687
Node: stat1541753
Ref: whatsnew/3 4 stat1541846
Ref: f5b1541846
Ref: stat-Footnote-11542317
Ref: stat-Footnote-21542382
Node: struct<2>1542447
Ref: whatsnew/3 4 struct1542546
Ref: f601542546
Ref: struct<2>-Footnote-11542878
Node: subprocess<5>1542943
Ref: whatsnew/3 4 subprocess1543046
Ref: f631543046
Ref: subprocess<5>-Footnote-11543492
Ref: subprocess<5>-Footnote-21543557
Node: sunau<2>1543622
Ref: whatsnew/3 4 sunau1543723
Ref: f661543723
Ref: sunau<2>-Footnote-11544507
Ref: sunau<2>-Footnote-21544572
Ref: sunau<2>-Footnote-31544637
Ref: sunau<2>-Footnote-41544702
Node: sys<11>1544766
Ref: whatsnew/3 4 sys1544864
Ref: f671544864
Ref: sys<11>-Footnote-11546152
Ref: sys<11>-Footnote-21546217
Node: tarfile<7>1546281
Ref: whatsnew/3 4 tarfile1546379
Ref: f6d1546379
Ref: tarfile<7>-Footnote-11546697
Node: textwrap1546762
Ref: whatsnew/3 4 textwrap1546865
Ref: f6f1546865
Ref: textwrap-Footnote-11547566
Ref: textwrap-Footnote-21547631
Node: threading<7>1547696
Ref: whatsnew/3 4 threading1547801
Ref: f741547801
Ref: threading<7>-Footnote-11548146
Node: traceback<6>1548211
Ref: whatsnew/3 4 traceback1548316
Ref: f761548316
Ref: traceback<6>-Footnote-11548631
Node: types<6>1548698
Ref: whatsnew/3 4 types1548800
Ref: f781548800
Ref: types<6>-Footnote-11549306
Node: urllib<3>1549371
Ref: whatsnew/3 4 urllib1549472
Ref: f791549472
Ref: urllib<3>-Footnote-11550785
Ref: urllib<3>-Footnote-21550850
Ref: urllib<3>-Footnote-31550915
Ref: urllib<3>-Footnote-41550980
Ref: urllib<3>-Footnote-51551045
Ref: urllib<3>-Footnote-61551110
Node: unittest<9>1551175
Ref: whatsnew/3 4 unittest1551275
Ref: f831551275
Ref: unittest<9>-Footnote-11554426
Ref: unittest<9>-Footnote-21554491
Ref: unittest<9>-Footnote-31554556
Ref: unittest<9>-Footnote-41554621
Ref: unittest<9>-Footnote-51554686
Ref: unittest<9>-Footnote-61554751
Ref: unittest<9>-Footnote-71554816
Ref: unittest<9>-Footnote-81554881
Ref: unittest<9>-Footnote-91554946
Node: venv<7>1555011
Ref: whatsnew/3 4 venv1555109
Ref: f8a1555109
Ref: venv<7>-Footnote-11555666
Ref: venv<7>-Footnote-21555731
Ref: venv<7>-Footnote-31555796
Node: wave<2>1555838
Ref: whatsnew/3 4 wave1555935
Ref: f8b1555935
Ref: wave<2>-Footnote-11556571
Ref: wave<2>-Footnote-21556636
Ref: wave<2>-Footnote-31556701
Ref: wave<2>-Footnote-41556765
Node: weakref<2>1556829
Ref: whatsnew/3 4 weakref1556931
Ref: f8f1556931
Ref: weakref<2>-Footnote-11557552
Ref: weakref<2>-Footnote-21557617
Ref: weakref<2>-Footnote-31557682
Node: xml etree<2>1557747
Ref: whatsnew/3 4 xml-etree1557852
Ref: f931557852
Ref: xml etree<2>-Footnote-11558591
Ref: xml etree<2>-Footnote-21558656
Node: zipfile<5>1558721
Ref: whatsnew/3 4 zipfile1558807
Ref: f991558807
Ref: zipfile<5>-Footnote-11559338
Ref: zipfile<5>-Footnote-21559403
Node: CPython 實作變更1559468
Ref: whatsnew/3 4 cpython-implementation-changes1559606
Ref: f9c1559606
Node: PEP 445 Customization of CPython Memory Allocators1560104
Ref: whatsnew/3 4 pep-445-customization-of-cpython-memory-allocators1560252
Ref: f9d1560252
Ref: whatsnew/3 4 whatsnew-pep-4451560252
Ref: e911560252
Ref: PEP 445 Customization of CPython Memory Allocators-Footnote-11560642
Ref: PEP 445 Customization of CPython Memory Allocators-Footnote-21560684
Node: PEP 442 Safe Object Finalization1560726
Ref: whatsnew/3 4 pep-442-safe-object-finalization1560932
Ref: f9e1560932
Ref: whatsnew/3 4 whatsnew-pep-4421560932
Ref: e901560932
Ref: PEP 442 Safe Object Finalization-Footnote-11561788
Ref: PEP 442 Safe Object Finalization-Footnote-21561830
Node: PEP 456 Secure and Interchangeable Hash Algorithm1561872
Ref: whatsnew/3 4 pep-456-secure-and-interchangeable-hash-algorithm1562051
Ref: f9f1562051
Ref: whatsnew/3 4 whatsnew-pep-4561562051
Ref: e8a1562051
Ref: PEP 456 Secure and Interchangeable Hash Algorithm-Footnote-11562993
Ref: PEP 456 Secure and Interchangeable Hash Algorithm-Footnote-21563035
Node: PEP 436 Argument Clinic1563100
Ref: whatsnew/3 4 pep-436-argument-clinic1563276
Ref: fa11563276
Ref: whatsnew/3 4 whatsnew-pep-4361563276
Ref: e921563276
Ref: PEP 436 Argument Clinic-Footnote-11564375
Ref: PEP 436 Argument Clinic-Footnote-21564417
Node: Other Build and C API Changes1564459
Ref: whatsnew/3 4 other-build-and-c-api-changes1564607
Ref: fa21564607
Ref: Other Build and C API Changes-Footnote-11566685
Ref: Other Build and C API Changes-Footnote-21566750
Ref: Other Build and C API Changes-Footnote-31566815
Ref: Other Build and C API Changes-Footnote-41566882
Ref: Other Build and C API Changes-Footnote-51566946
Ref: Other Build and C API Changes-Footnote-61567011
Ref: Other Build and C API Changes-Footnote-71567084
Ref: Other Build and C API Changes-Footnote-81567148
Ref: Other Build and C API Changes-Footnote-91567213
Node: Other Improvements<2>1567278
Ref: whatsnew/3 4 other-improvements1567418
Ref: fa61567418
Ref: whatsnew/3 4 other-improvements-3-41567418
Ref: fa71567418
Ref: whatsnew/3 4 whatsnew-isolated-mode1567475
Ref: e7b1567475
Ref: Other Improvements<2>-Footnote-11571585
Ref: Other Improvements<2>-Footnote-21571650
Ref: Other Improvements<2>-Footnote-31571714
Ref: Other Improvements<2>-Footnote-41571779
Ref: Other Improvements<2>-Footnote-51571844
Ref: Other Improvements<2>-Footnote-61571909
Ref: Other Improvements<2>-Footnote-71571974
Ref: Other Improvements<2>-Footnote-81572069
Ref: Other Improvements<2>-Footnote-91572123
Ref: Other Improvements<2>-Footnote-101572188
Ref: Other Improvements<2>-Footnote-111572254
Ref: Other Improvements<2>-Footnote-121572320
Ref: Other Improvements<2>-Footnote-131572363
Ref: Other Improvements<2>-Footnote-141572429
Ref: Other Improvements<2>-Footnote-151572495
Ref: Other Improvements<2>-Footnote-161572561
Ref: Other Improvements<2>-Footnote-171572627
Ref: Other Improvements<2>-Footnote-181572670
Ref: Other Improvements<2>-Footnote-191572736
Ref: Other Improvements<2>-Footnote-201572802
Ref: Other Improvements<2>-Footnote-211572868
Node: 顯著最佳化1572934
Ref: whatsnew/3 4 significant-optimizations1573036
Ref: fac1573036
Ref: 顯著最佳化-Footnote-11575816
Ref: 顯著最佳化-Footnote-21575881
Ref: 顯著最佳化-Footnote-31575946
Ref: 顯著最佳化-Footnote-41576011
Ref: 顯著最佳化-Footnote-51576076
Ref: 顯著最佳化-Footnote-61576141
Ref: 顯著最佳化-Footnote-71576206
Ref: 顯著最佳化-Footnote-81576270
Ref: 顯著最佳化-Footnote-91576335
Ref: 顯著最佳化-Footnote-101576400
Ref: 顯著最佳化-Footnote-111576466
Ref: 顯著最佳化-Footnote-121576532
Ref: 顯著最佳化-Footnote-131576598
Node: 已棄用<11>1576664
Ref: whatsnew/3 4 deprecated1576796
Ref: fb01576796
Ref: whatsnew/3 4 deprecated-3-41576796
Ref: eaa1576796
Node: Deprecations in the Python API1577229
Ref: whatsnew/3 4 deprecations-in-the-python-api1577333
Ref: fb11577333
Node: 已棄用功能1580976
Ref: whatsnew/3 4 deprecated-features1581080
Ref: fb51581080
Ref: 已棄用功能-Footnote-11581448
Ref: 已棄用功能-Footnote-21581513
Node: 已移除<9>1581578
Ref: whatsnew/3 4 removed1581711
Ref: fb71581711
Node: Operating Systems No Longer Supported1581845
Ref: whatsnew/3 4 operating-systems-no-longer-supported1581962
Ref: fb81581962
Ref: Operating Systems No Longer Supported-Footnote-11582381
Ref: Operating Systems No Longer Supported-Footnote-21582446
Ref: Operating Systems No Longer Supported-Footnote-31582511
Node: API 與功能的移除1582576
Ref: whatsnew/3 4 api-and-feature-removals1582720
Ref: fb91582720
Ref: API 與功能的移除-Footnote-11585158
Ref: API 與功能的移除-Footnote-21585194
Ref: API 與功能的移除-Footnote-31585259
Ref: API 與功能的移除-Footnote-41585324
Ref: API 與功能的移除-Footnote-51585389
Ref: API 與功能的移除-Footnote-61585454
Ref: API 與功能的移除-Footnote-71585518
Node: 程式碼的清除1585583
Ref: whatsnew/3 4 code-cleanups1585681
Ref: fbb1585681
Ref: 程式碼的清除-Footnote-11586349
Node: Porting to Python 3 41586414
Ref: whatsnew/3 4 porting-to-python-3-41586552
Ref: fbc1586552
Node: Changes in 'python' Command Behavior<2>1586903
Ref: whatsnew/3 4 changes-in-python-command-behavior1587032
Ref: fbd1587032
Ref: Changes in 'python' Command Behavior<2>-Footnote-11588141
Node: Python API 的變更<2>1588206
Ref: whatsnew/3 4 changes-in-the-python-api1588365
Ref: fbf1588365
Ref: Python API 的變更<2>-Footnote-11601709
Ref: Python API 的變更<2>-Footnote-21601774
Ref: Python API 的變更<2>-Footnote-31601839
Ref: Python API 的變更<2>-Footnote-41601904
Ref: Python API 的變更<2>-Footnote-51601969
Ref: Python API 的變更<2>-Footnote-61602034
Ref: Python API 的變更<2>-Footnote-71602099
Ref: Python API 的變更<2>-Footnote-81602164
Ref: Python API 的變更<2>-Footnote-91602228
Ref: Python API 的變更<2>-Footnote-101602293
Ref: Python API 的變更<2>-Footnote-111602359
Ref: Python API 的變更<2>-Footnote-121602425
Ref: Python API 的變更<2>-Footnote-131602491
Ref: Python API 的變更<2>-Footnote-141602557
Ref: Python API 的變更<2>-Footnote-151602623
Ref: Python API 的變更<2>-Footnote-161602689
Ref: Python API 的變更<2>-Footnote-171602755
Ref: Python API 的變更<2>-Footnote-181602821
Ref: Python API 的變更<2>-Footnote-191602887
Ref: Python API 的變更<2>-Footnote-201602953
Ref: Python API 的變更<2>-Footnote-211603019
Ref: Python API 的變更<2>-Footnote-221603085
Ref: Python API 的變更<2>-Footnote-231603151
Ref: Python API 的變更<2>-Footnote-241603216
Node: C API 中的改動<7>1603282
Ref: whatsnew/3 4 changes-in-the-c-api1603393
Ref: fd01603393
Ref: C API 中的改動<7>-Footnote-11605147
Ref: C API 中的改動<7>-Footnote-21605212
Node: 3 4 3 中的變更1605277
Ref: whatsnew/3 4 changed-in-3-4-31605394
Ref: fd61605394
Node: PEP 476 Enabling certificate verification by default for stdlib http clients1605612
Ref: whatsnew/3 4 pep-4761605743
Ref: fd71605743
Ref: whatsnew/3 4 pep-476-enabling-certificate-verification-by-default-for-stdlib-http-clients1605743
Ref: fd81605743
Node: Python 3 3 有什麼新功能1606743
Ref: whatsnew/3 3 doc1606916
Ref: fd91606916
Ref: whatsnew/3 3 what-s-new-in-python-3-31606916
Ref: fda1606916
Ref: Python 3 3 有什麼新功能-Footnote-11608692
Ref: Python 3 3 有什麼新功能-Footnote-21608752
Node: Summary -- Release highlights<5>1608794
Ref: whatsnew/3 3 summary-release-highlights1608923
Ref: fdb1608923
Node: PEP 405：虛擬環境1610234
Ref: whatsnew/3 3 pep-4051610407
Ref: fdd1610407
Ref: whatsnew/3 3 pep-405-virtual-environments1610407
Ref: fe51610407
Ref: PEP 405：虛擬環境-Footnote-11611355
Node: PEP 420 Implicit Namespace Packages1611397
Ref: whatsnew/3 3 pep-420-implicit-namespace-packages1611610
Ref: fe61611610
Ref: PEP 420 Implicit Namespace Packages-Footnote-11612109
Ref: PEP 420 Implicit Namespace Packages-Footnote-21612151
Node: PEP 3118 New memoryview implementation and buffer protocol documentation1612193
Ref: whatsnew/3 3 pep-3118-new-memoryview-implementation-and-buffer-protocol-documentation1612422
Ref: fe71612422
Ref: whatsnew/3 3 pep-3118-update1612422
Ref: fe81612422
Ref: PEP 3118 New memoryview implementation and buffer protocol documentation-Footnote-11613549
Node: 功能1613591
Ref: whatsnew/3 3 features1613725
Ref: fe91613725
Ref: 功能-Footnote-11614519
Node: API 變更1614584
Ref: whatsnew/3 3 api-changes1614718
Ref: fea1614718
Ref: API 變更-Footnote-11615718
Ref: API 變更-Footnote-21615783
Node: PEP 393 Flexible String Representation1615825
Ref: whatsnew/3 3 pep-3931616067
Ref: fe01616067
Ref: whatsnew/3 3 pep-393-flexible-string-representation1616067
Ref: fed1616067
Ref: PEP 393 Flexible String Representation-Footnote-11617121
Node: 功能性1617163
Ref: whatsnew/3 3 functionality1617283
Ref: fee1617283
Ref: 功能性-Footnote-11618701
Ref: 功能性-Footnote-21618743
Node: 性能和資源使用情況1618808
Ref: whatsnew/3 3 performance-and-resource-usage1618928
Ref: ff01618928
Ref: 性能和資源使用情況-Footnote-11620141
Node: PEP 397：適用於 Windows 的 Python 啟動器1620183
Ref: whatsnew/3 3 pep-3971620405
Ref: ff11620405
Ref: whatsnew/3 3 pep-397-python-launcher-for-windows1620405
Ref: ff21620405
Ref: PEP 397：適用於 Windows 的 Python 啟動器-Footnote-11621956
Ref: PEP 397：適用於 Windows 的 Python 啟動器-Footnote-21622020
Node: PEP 3151 Reworking the OS and IO exception hierarchy1622062
Ref: whatsnew/3 3 pep-31511622293
Ref: fde1622293
Ref: whatsnew/3 3 pep-3151-reworking-the-os-and-io-exception-hierarchy1622293
Ref: ff41622293
Ref: PEP 3151 Reworking the OS and IO exception hierarchy-Footnote-11624858
Node: PEP 380 Syntax for Delegating to a Subgenerator1624900
Ref: whatsnew/3 3 pep-3801625120
Ref: fdc1625120
Ref: whatsnew/3 3 pep-380-syntax-for-delegating-to-a-subgenerator1625120
Ref: 10031625120
Ref: PEP 380 Syntax for Delegating to a Subgenerator-Footnote-11627565
Node: PEP 409 Suppressing exception context1627607
Ref: whatsnew/3 3 pep-409-suppressing-exception-context1627808
Ref: 10051627808
Ref: PEP 409 Suppressing exception context-Footnote-11629897
Node: PEP 414 Explicit Unicode literals1629939
Ref: whatsnew/3 3 pep-414-explicit-unicode-literals1630142
Ref: 10061630142
Ref: PEP 414 Explicit Unicode literals-Footnote-11630854
Node: PEP 3155 Qualified name for classes and functions1630896
Ref: whatsnew/3 3 pep-3155-qualified-name-for-classes-and-functions1631092
Ref: 10071631092
Ref: PEP 3155 Qualified name for classes and functions-Footnote-11632670
Node: PEP 412 Key-Sharing Dictionary1632712
Ref: whatsnew/3 3 pep-4121632903
Ref: fe11632903
Ref: whatsnew/3 3 pep-412-key-sharing-dictionary1632903
Ref: 10081632903
Ref: PEP 412 Key-Sharing Dictionary-Footnote-11633413
Node: PEP 362：函式簽名物件1633455
Ref: whatsnew/3 3 pep-362-function-signature-object1633632
Ref: 10091633632
Ref: PEP 362：函式簽名物件-Footnote-11634505
Node: PEP 421：新增 sys implementation1634547
Ref: whatsnew/3 3 pep-421-adding-sys-implementation1634734
Ref: 100b1634734
Ref: PEP 421：新增 sys implementation-Footnote-11635949
Node: SimpleNamespace1635991
Ref: whatsnew/3 3 simplenamespace1636078
Ref: 100c1636078
Ref: SimpleNamespace-Footnote-11636693
Node: 使用 importlib 作為 import 的實作1636735
Ref: whatsnew/3 3 importlib1636916
Ref: fdf1636916
Ref: whatsnew/3 3 using-importlib-as-the-implementation-of-import1636916
Ref: 100d1636916
Ref: 使用 importlib 作為 import 的實作-Footnote-11638170
Ref: 使用 importlib 作為 import 的實作-Footnote-21638234
Ref: 使用 importlib 作為 import 的實作-Footnote-31638299
Ref: 使用 importlib 作為 import 的實作-Footnote-41638364
Ref: 使用 importlib 作為 import 的實作-Footnote-51638429
Node: 新 API1638471
Ref: whatsnew/3 3 new-apis1638579
Ref: 10101638579
Node: 明顯的變更1640416
Ref: whatsnew/3 3 visible-changes1640524
Ref: 10171640524
Ref: 明顯的變更-Footnote-11642366
Ref: 明顯的變更-Footnote-21642408
Node: 其他語言更動<10>1642450
Ref: whatsnew/3 3 other-language-changes1642623
Ref: 10181642623
Ref: 其他語言更動<10>-Footnote-11644602
Ref: 其他語言更動<10>-Footnote-21644667
Ref: 其他語言更動<10>-Footnote-31644732
Ref: 其他語言更動<10>-Footnote-41644797
Ref: 其他語言更動<10>-Footnote-51644862
Ref: 其他語言更動<10>-Footnote-61644927
Ref: 其他語言更動<10>-Footnote-71644992
Ref: 其他語言更動<10>-Footnote-81645057
Node: A Finer-Grained Import Lock1645122
Ref: whatsnew/3 3 a-finer-grained-import-lock1645276
Ref: 101b1645276
Ref: A Finer-Grained Import Lock-Footnote-11646027
Node: 內建函式和型別1646091
Ref: whatsnew/3 3 builtin-functions-and-types1646235
Ref: 101c1646235
Ref: 內建函式和型別-Footnote-11647453
Node: 新模組<6>1647517
Ref: whatsnew/3 3 new-modules1647653
Ref: 101f1647653
Node: faulthandler<4>1647774
Ref: whatsnew/3 3 faulthandler1647859
Ref: 10201647859
Node: ipaddress<6>1648787
Ref: whatsnew/3 3 ipaddress1648888
Ref: 10221648888
Ref: ipaddress<6>-Footnote-11649240
Node: lzma<2>1649282
Ref: whatsnew/3 3 lzma1649359
Ref: 10231649359
Ref: lzma<2>-Footnote-11649679
Node: 改進的模組<10>1649743
Ref: whatsnew/3 3 improved-modules1649870
Ref: 10241649870
Node: abc<2>1651198
Ref: whatsnew/3 3 abc1651277
Ref: 10251651277
Ref: abc<2>-Footnote-11652240
Ref: abc<2>-Footnote-21652305
Node: array<5>1652370
Ref: whatsnew/3 3 array1652467
Ref: 102b1652467
Ref: array<5>-Footnote-11652707
Node: base64<4>1652774
Ref: whatsnew/3 3 base641652876
Ref: 102c1652876
Ref: base64<4>-Footnote-11653176
Node: binascii<3>1653241
Ref: whatsnew/3 3 binascii1653341
Ref: 102d1653341
Ref: binascii<3>-Footnote-11653597
Node: bz2<2>1653662
Ref: whatsnew/3 3 bz21653762
Ref: 102e1653762
Ref: bz2<2>-Footnote-11654746
Ref: bz2<2>-Footnote-21654810
Node: codecs<2>1654874
Ref: whatsnew/3 3 codecs1654977
Ref: 10311654977
Ref: codecs<2>-Footnote-11656296
Ref: codecs<2>-Footnote-21656361
Ref: codecs<2>-Footnote-31656426
Node: collections<7>1656491
Ref: whatsnew/3 3 collections1656601
Ref: 10321656601
Ref: collections<7>-Footnote-11657369
Ref: collections<7>-Footnote-21657434
Ref: collections<7>-Footnote-31657499
Ref: collections<7>-Footnote-41657564
Node: contextlib<7>1657629
Ref: whatsnew/3 3 contextlib1657738
Ref: 10341657738
Ref: contextlib<7>-Footnote-11658333
Node: crypt<2>1658398
Ref: whatsnew/3 3 crypt1658502
Ref: 10351658502
Ref: crypt<2>-Footnote-11658706
Node: curses<5>1658771
Ref: whatsnew/3 3 curses1658873
Ref: 10361658873
Ref: curses<5>-Footnote-11659680
Node: datetime<6>1659744
Ref: whatsnew/3 3 datetime1659848
Ref: 103a1659848
Ref: datetime<6>-Footnote-11660509
Node: decimal<3>1660574
Ref: whatsnew/3 3 decimal1660677
Ref: 103c1660677
Ref: whatsnew/3 3 new-decimal1660677
Ref: fe21660677
Ref: decimal<3>-Footnote-11662379
Node: 功能<2>1662443
Ref: whatsnew/3 3 id11662521
Ref: 103d1662521
Node: API 變更<2>1662891
Ref: whatsnew/3 3 id21662969
Ref: 10401662969
Node: email<5>1665682
Ref: whatsnew/3 3 email1665783
Ref: 104b1665783
Ref: whatsnew/3 3 new-email1665783
Ref: fe31665783
Node: Policy Framework1665914
Ref: whatsnew/3 3 policy-framework1666022
Ref: 104c1666022
Node: Provisional Policy with New Header API1668938
Ref: whatsnew/3 3 provisional-policy-with-new-header-api1669072
Ref: 10501669072
Node: 其他 API 變更1673650
Ref: whatsnew/3 3 other-api-changes1673759
Ref: 10541673759
Node: ftplib<3>1674600
Ref: whatsnew/3 3 ftplib1674703
Ref: 105a1674703
Ref: ftplib<3>-Footnote-11675616
Ref: ftplib<3>-Footnote-21675680
Ref: ftplib<3>-Footnote-31675745
Node: functools<6>1675810
Ref: whatsnew/3 3 functools1675910
Ref: 105f1675910
Ref: functools<6>-Footnote-11676258
Node: gc<7>1676323
Ref: whatsnew/3 3 gc1676421
Ref: 10601676421
Node: hmac<4>1676596
Ref: whatsnew/3 3 hmac1676689
Ref: 10621676689
Ref: hmac<4>-Footnote-11676956
Node: http<4>1677021
Ref: whatsnew/3 3 http1677116
Ref: 10641677116
Ref: http<4>-Footnote-11677802
Ref: http<4>-Footnote-21677866
Ref: http<4>-Footnote-31677931
Node: html<2>1677996
Ref: whatsnew/3 3 html1678094
Ref: 106b1678094
Ref: html<2>-Footnote-11679095
Ref: html<2>-Footnote-21679160
Ref: html<2>-Footnote-31679225
Ref: html<2>-Footnote-41679290
Ref: html<2>-Footnote-51679355
Ref: html<2>-Footnote-61679420
Ref: html<2>-Footnote-71679487
Ref: html<2>-Footnote-81679553
Ref: html<2>-Footnote-91679618
Ref: html<2>-Footnote-101679683
Ref: html<2>-Footnote-111679751
Ref: html<2>-Footnote-121679818
Ref: html<2>-Footnote-131679884
Ref: html<2>-Footnote-141679950
Ref: html<2>-Footnote-151680015
Ref: html<2>-Footnote-161680081
Node: imaplib<3>1680147
Ref: whatsnew/3 3 imaplib1680248
Ref: 106d1680248
Ref: imaplib<3>-Footnote-11680496
Node: inspect<9>1680560
Ref: whatsnew/3 3 inspect1680659
Ref: 106e1680659
Ref: inspect<9>-Footnote-11681383
Ref: inspect<9>-Footnote-21681448
Node: io<6>1681513
Ref: whatsnew/3 3 io1681614
Ref: 10711681614
Ref: io<6>-Footnote-11682265
Node: itertools<6>1682330
Ref: whatsnew/3 3 itertools1682431
Ref: 10721682431
Node: logging<7>1682589
Ref: whatsnew/3 3 logging1682692
Ref: 10731682692
Node: math<9>1683145
Ref: whatsnew/3 3 math1683243
Ref: 10741683243
Ref: math<9>-Footnote-11683476
Node: mmap<4>1683541
Ref: whatsnew/3 3 mmap1683647
Ref: 10761683647
Ref: mmap<4>-Footnote-11683985
Node: multiprocessing<8>1684050
Ref: whatsnew/3 3 multiprocessing1684159
Ref: 10781684159
Ref: multiprocessing<8>-Footnote-11685318
Ref: multiprocessing<8>-Footnote-21685383
Ref: multiprocessing<8>-Footnote-31685447
Ref: multiprocessing<8>-Footnote-41685511
Node: nntplib<2>1685576
Ref: whatsnew/3 3 nntplib1685684
Ref: 10801685684
Ref: nntplib<2>-Footnote-11686249
Node: os<12>1686313
Ref: whatsnew/3 3 os1686409
Ref: 10811686409
Ref: os<12>-Footnote-11693847
Ref: os<12>-Footnote-21693912
Ref: os<12>-Footnote-31693976
Ref: os<12>-Footnote-41694041
Ref: os<12>-Footnote-51694106
Ref: os<12>-Footnote-61694171
Ref: os<12>-Footnote-71694235
Ref: os<12>-Footnote-81694300
Ref: os<12>-Footnote-91694365
Ref: os<12>-Footnote-101694430
Ref: os<12>-Footnote-111694495
Node: pdb<7>1694561
Ref: whatsnew/3 3 pdb1694656
Ref: 10b81694656
Ref: pdb<7>-Footnote-11694943
Node: pickle<5>1695008
Ref: whatsnew/3 3 pickle1695105
Ref: 10b91695105
Ref: pickle<5>-Footnote-11695382
Node: pydoc<5>1695447
Ref: whatsnew/3 3 pydoc1695543
Ref: 10bb1695543
Node: re<9>1695742
Ref: whatsnew/3 3 re1695834
Ref: 10bc1695834
Ref: re<9>-Footnote-11696036
Node: sched1696100
Ref: whatsnew/3 3 sched1696193
Ref: 10bd1696193
Ref: sched-Footnote-11697345
Ref: sched-Footnote-21697410
Ref: sched-Footnote-31697474
Ref: sched-Footnote-41697539
Ref: sched-Footnote-51697604
Node: select<2>1697669
Ref: whatsnew/3 3 select1697765
Ref: 10c21697765
Ref: select<2>-Footnote-11698030
Node: shlex<3>1698094
Ref: whatsnew/3 3 shlex1698194
Ref: 10c31698194
Node: shutil<7>1698502
Ref: whatsnew/3 3 shutil1698602
Ref: 10c51698602
Ref: shutil<7>-Footnote-11700470
Ref: shutil<7>-Footnote-21700535
Ref: shutil<7>-Footnote-31700600
Ref: shutil<7>-Footnote-41700665
Ref: shutil<7>-Footnote-51700730
Ref: shutil<7>-Footnote-61700795
Ref: shutil<7>-Footnote-71700860
Ref: shutil<7>-Footnote-81700924
Node: signal<4>1700988
Ref: whatsnew/3 3 signal1701088
Ref: 10c81701088
Ref: signal<4>-Footnote-11702159
Node: smtpd<4>1702223
Ref: whatsnew/3 3 smtpd1702324
Ref: 10cf1702324
Ref: smtpd<4>-Footnote-11702807
Ref: smtpd<4>-Footnote-21702866
Ref: smtpd<4>-Footnote-31702925
Node: smtplib<4>1702989
Ref: whatsnew/3 3 smtplib1703091
Ref: 10d01703091
Ref: smtplib<4>-Footnote-11703807
Ref: smtplib<4>-Footnote-21703872
Ref: smtplib<4>-Footnote-31703937
Node: socket<10>1704001
Ref: whatsnew/3 3 socket1704110
Ref: 10d21704110
Ref: socket<10>-Footnote-11705327
Ref: socket<10>-Footnote-21705391
Ref: socket<10>-Footnote-31705456
Ref: socket<10>-Footnote-41705545
Ref: socket<10>-Footnote-51705610
Node: socketserver<3>1705675
Ref: whatsnew/3 3 socketserver1705785
Ref: 10d51705785
Ref: socketserver<3>-Footnote-11706163
Node: sqlite3<10>1706228
Ref: whatsnew/3 3 sqlite31706335
Ref: 10d91706335
Ref: sqlite3<10>-Footnote-11706612
Node: ssl<11>1706677
Ref: whatsnew/3 3 ssl1706776
Ref: 10da1706776
Ref: ssl<11>-Footnote-11708965
Ref: ssl<11>-Footnote-21709030
Ref: ssl<11>-Footnote-31709095
Ref: ssl<11>-Footnote-41709160
Ref: ssl<11>-Footnote-51709225
Ref: ssl<11>-Footnote-61709290
Ref: ssl<11>-Footnote-71709355
Ref: ssl<11>-Footnote-81709420
Ref: ssl<11>-Footnote-91709485
Ref: ssl<11>-Footnote-101709550
Ref: ssl<11>-Footnote-111709616
Node: stat<2>1709682
Ref: whatsnew/3 3 stat1709779
Ref: 10e31709779
Ref: stat<2>-Footnote-11710077
Node: struct<3>1710142
Ref: whatsnew/3 3 struct1710245
Ref: 10e51710245
Ref: struct<3>-Footnote-11710494
Node: subprocess<6>1710558
Ref: whatsnew/3 3 subprocess1710661
Ref: 10e61710661
Ref: subprocess<6>-Footnote-11710999
Ref: subprocess<6>-Footnote-21711063
Node: sys<12>1711127
Ref: whatsnew/3 3 sys1711231
Ref: 10e81711231
Ref: sys<12>-Footnote-11711452
Node: tarfile<8>1711517
Ref: whatsnew/3 3 tarfile1711619
Ref: 10ea1711619
Ref: tarfile<8>-Footnote-11711830
Node: tempfile<4>1711894
Ref: whatsnew/3 3 tempfile1712000
Ref: 10eb1712000
Ref: tempfile<4>-Footnote-11712227
Node: textwrap<2>1712291
Ref: whatsnew/3 3 textwrap1712399
Ref: 10ec1712399
Ref: textwrap<2>-Footnote-11712645
Node: threading<8>1712710
Ref: whatsnew/3 3 threading1712814
Ref: 10ed1712814
Ref: threading<8>-Footnote-11713753
Ref: threading<8>-Footnote-21713818
Node: time<8>1713882
Ref: whatsnew/3 3 time1713983
Ref: 10f41713983
Ref: time<8>-Footnote-11714931
Ref: time<8>-Footnote-21714973
Node: types<7>1715038
Ref: whatsnew/3 3 types1715139
Ref: 10f91715139
Ref: types<7>-Footnote-11715479
Ref: types<7>-Footnote-21715544
Ref: types<7>-Footnote-31715586
Node: unittest<10>1715651
Ref: whatsnew/3 3 unittest1715754
Ref: 10fc1715754
Ref: unittest<10>-Footnote-11716173
Node: urllib<4>1716238
Ref: whatsnew/3 3 urllib1716346
Ref: 11011716346
Ref: urllib<4>-Footnote-11716701
Node: webbrowser<3>1716768
Ref: whatsnew/3 3 webbrowser1716888
Ref: 11031716888
Ref: webbrowser<3>-Footnote-11717427
Ref: webbrowser<3>-Footnote-21717492
Node: xml etree ElementTree<2>1717557
Ref: whatsnew/3 3 xml-etree-elementtree1717675
Ref: 11041717675
Node: zlib<2>1718194
Ref: whatsnew/3 3 zlib1718290
Ref: 11051718290
Ref: zlib<2>-Footnote-11718766
Ref: zlib<2>-Footnote-21718831
Node: 最佳化<9>1718896
Ref: whatsnew/3 3 optimizations1719033
Ref: 11081719033
Ref: 最佳化<9>-Footnote-11719839
Ref: 最佳化<9>-Footnote-21719881
Ref: 最佳化<9>-Footnote-31719946
Ref: 最佳化<9>-Footnote-41720011
Node: 建置和 C API 更改1720076
Ref: whatsnew/3 3 build-and-c-api-changes1720207
Ref: feb1720207
Ref: 建置和 C API 更改-Footnote-11722074
Ref: 建置和 C API 更改-Footnote-21722116
Ref: 建置和 C API 更改-Footnote-31722158
Node: 已棄用<12>1722223
Ref: whatsnew/3 3 deprecated1722362
Ref: 111f1722362
Node: 不支援的作業系統1722548
Ref: whatsnew/3 3 unsupported-operating-systems1722675
Ref: 11201722675
Node: 已棄用的 Python 模組、函式和方法1722983
Ref: whatsnew/3 3 deprecated-python-modules-functions-and-methods1723155
Ref: 11211723155
Ref: 已棄用的 Python 模組、函式和方法-Footnote-11725429
Ref: 已棄用的 Python 模組、函式和方法-Footnote-21725493
Ref: 已棄用的 Python 模組、函式和方法-Footnote-31725535
Ref: 已棄用的 Python 模組、函式和方法-Footnote-41725600
Ref: 已棄用的 Python 模組、函式和方法-Footnote-51725665
Node: C API 中已棄用的函式和型別1725730
Ref: whatsnew/3 3 deprecated-functions-and-types-of-the-c-api1725896
Ref: 11251725896
Ref: C API 中已棄用的函式和型別-Footnote-11728992
Node: 已棄用的功能1729034
Ref: whatsnew/3 3 deprecated-features1729147
Ref: 112f1729147
Node: 移植到 Python 3 31729362
Ref: whatsnew/3 3 porting-to-python-3-31729470
Ref: 11301729470
Node: 移植 Python 程式碼1729733
Ref: whatsnew/3 3 porting-python-code1729836
Ref: 100f1729836
Ref: whatsnew/3 3 portingpythoncode1729836
Ref: 11311729836
Ref: 移植 Python 程式碼-Footnote-11736810
Ref: 移植 Python 程式碼-Footnote-21736875
Ref: 移植 Python 程式碼-Footnote-31736940
Ref: 移植 Python 程式碼-Footnote-41737005
Ref: 移植 Python 程式碼-Footnote-51737047
Ref: 移植 Python 程式碼-Footnote-61737089
Ref: 移植 Python 程式碼-Footnote-71737153
Ref: 移植 Python 程式碼-Footnote-81737220
Ref: 移植 Python 程式碼-Footnote-91737285
Ref: 移植 Python 程式碼-Footnote-101737349
Node: Porting C code1737415
Ref: whatsnew/3 3 porting-c-code1737548
Ref: fec1737548
Ref: Porting C code-Footnote-11739045
Node: Building C extensions1739087
Ref: whatsnew/3 3 building-c-extensions1739218
Ref: 113e1739218
Ref: Building C extensions-Footnote-11739823
Node: 命令列開關更改1739888
Ref: whatsnew/3 3 command-line-switch-changes1739996
Ref: 113f1739996
Ref: 命令列開關更改-Footnote-11740547
Ref: 命令列開關更改-Footnote-21740612
Node: Python 3 2 有什麼新功能1740677
Ref: whatsnew/3 2 doc1740847
Ref: 11411740847
Ref: whatsnew/3 2 what-s-new-in-python-3-21740847
Ref: 11421740847
Ref: Python 3 2 有什麼新功能-Footnote-11742213
Ref: Python 3 2 有什麼新功能-Footnote-21742312
Node: PEP 384 Defining a Stable ABI1742354
Ref: whatsnew/3 2 pep-384-defining-a-stable-abi1742496
Ref: 11431742496
Ref: PEP 384 Defining a Stable ABI-Footnote-11743591
Node: PEP 389 Argparse 命令列剖析模組1743633
Ref: whatsnew/3 2 pep-389-argparse-command-line-parsing-module1743834
Ref: 11441743834
Ref: PEP 389 Argparse 命令列剖析模組-Footnote-11747934
Node: PEP 391 Dictionary Based Configuration for Logging1747976
Ref: whatsnew/3 2 pep-391-dictionary-based-configuration-for-logging1748184
Ref: 11461748184
Ref: PEP 391 Dictionary Based Configuration for Logging-Footnote-11750482
Node: PEP 3148：concurrent futures 模組1750524
Ref: whatsnew/3 2 pep-3148-the-concurrent-futures-module1750729
Ref: 11481750729
Ref: PEP 3148：concurrent futures 模組-Footnote-11753423
Node: PEP 3147 PYC Repository Directories1753465
Ref: whatsnew/3 2 pep-3147-pyc-repository-directories1753656
Ref: 114c1753656
Ref: PEP 3147 PYC Repository Directories-Footnote-11756693
Node: PEP 3149 ABI Version Tagged so Files1756735
Ref: whatsnew/3 2 pep-3149-abi-version-tagged-so-files1756941
Ref: 114f1756941
Ref: PEP 3149 ABI Version Tagged so Files-Footnote-11758182
Node: PEP 3333 Python Web Server Gateway Interface v1 0 11758224
Ref: whatsnew/3 2 pep-3333-python-web-server-gateway-interface-v1-0-11758417
Ref: 11501758417
Ref: PEP 3333 Python Web Server Gateway Interface v1 0 1-Footnote-11760784
Ref: PEP 3333 Python Web Server Gateway Interface v1 0 1-Footnote-21760843
Ref: PEP 3333 Python Web Server Gateway Interface v1 0 1-Footnote-31760902
Node: 其他語言更動<11>1760944
Ref: whatsnew/3 2 other-language-changes1761136
Ref: 11531761136
Ref: 其他語言更動<11>-Footnote-11770659
Ref: 其他語言更動<11>-Footnote-21770723
Ref: 其他語言更動<11>-Footnote-31770787
Ref: 其他語言更動<11>-Footnote-41770854
Ref: 其他語言更動<11>-Footnote-51770918
Ref: 其他語言更動<11>-Footnote-61770982
Ref: 其他語言更動<11>-Footnote-71771046
Ref: 其他語言更動<11>-Footnote-81771110
Ref: 其他語言更動<11>-Footnote-91771174
Ref: 其他語言更動<11>-Footnote-101771238
Ref: 其他語言更動<11>-Footnote-111771304
Ref: 其他語言更動<11>-Footnote-121771371
Ref: 其他語言更動<11>-Footnote-131771436
Ref: 其他語言更動<11>-Footnote-141771501
Ref: 其他語言更動<11>-Footnote-151771567
Ref: 其他語言更動<11>-Footnote-161771633
Node: New Improved and Deprecated Modules1771698
Ref: whatsnew/3 2 new-improved-and-deprecated-modules1771854
Ref: 115f1771854
Node: email<6>1773882
Ref: whatsnew/3 2 email1773982
Ref: 11601773982
Ref: email<6>-Footnote-11775965
Ref: email<6>-Footnote-21776024
Ref: email<6>-Footnote-31776088
Node: elementtree1776153
Ref: whatsnew/3 2 elementtree1776274
Ref: 11681776274
Ref: elementtree-Footnote-11777758
Ref: elementtree-Footnote-21777858
Node: functools<7>1777922
Ref: whatsnew/3 2 functools1778047
Ref: 116f1778047
Ref: functools<7>-Footnote-11781523
Ref: functools<7>-Footnote-21781606
Ref: functools<7>-Footnote-31781685
Ref: functools<7>-Footnote-41781750
Ref: functools<7>-Footnote-51781815
Ref: functools<7>-Footnote-61781879
Ref: functools<7>-Footnote-71781943
Ref: functools<7>-Footnote-81782007
Node: itertools<7>1782059
Ref: whatsnew/3 2 itertools1782187
Ref: 11731782187
Node: collections<8>1782862
Ref: whatsnew/3 2 collections1782990
Ref: 11751782990
Ref: collections<8>-Footnote-11785245
Ref: collections<8>-Footnote-21785305
Node: threading<9>1785352
Ref: whatsnew/3 2 threading1785485
Ref: 117a1785485
Ref: threading<9>-Footnote-11788255
Ref: threading<9>-Footnote-21788316
Ref: threading<9>-Footnote-31788415
Ref: threading<9>-Footnote-41788487
Node: datetime 和 time1788551
Ref: whatsnew/3 2 datetime-and-time1788678
Ref: 117e1788678
Ref: datetime 和 time-Footnote-11791482
Ref: datetime 和 time-Footnote-21791549
Ref: datetime 和 time-Footnote-31791613
Ref: datetime 和 time-Footnote-41791677
Ref: datetime 和 time-Footnote-51791741
Ref: datetime 和 time-Footnote-61791808
Ref: datetime 和 time-Footnote-71791872
Node: math<10>1791937
Ref: whatsnew/3 2 math1792058
Ref: 11821792058
Ref: math<10>-Footnote-11793943
Node: abc<3>1793996
Ref: whatsnew/3 2 abc1794105
Ref: 11871794105
Ref: abc<3>-Footnote-11794732
Node: io<7>1794796
Ref: whatsnew/3 2 io1794904
Ref: 11881794904
Ref: io<7>-Footnote-11796076
Node: reprlib1796140
Ref: whatsnew/3 2 reprlib1796252
Ref: 118a1796252
Ref: reprlib-Footnote-11797238
Ref: reprlib-Footnote-21797302
Node: logging<8>1797366
Ref: whatsnew/3 2 logging1797479
Ref: 118c1797479
Node: csv<4>1799332
Ref: whatsnew/3 2 csv1799451
Ref: 11941799451
Ref: csv<4>-Footnote-11800317
Ref: csv<4>-Footnote-21800381
Node: contextlib<8>1800448
Ref: whatsnew/3 2 contextlib1800578
Ref: 11981800578
Ref: contextlib<8>-Footnote-11802802
Node: decimal and fractions1802866
Ref: whatsnew/3 2 decimal-and-fractions1802993
Ref: 119b1802993
Ref: decimal and fractions-Footnote-11805421
Ref: decimal and fractions-Footnote-21805485
Ref: decimal and fractions-Footnote-31805549
Ref: decimal and fractions-Footnote-41805613
Ref: decimal and fractions-Footnote-51805677
Ref: decimal and fractions-Footnote-61805741
Node: ftp1805805
Ref: whatsnew/3 2 ftp1805924
Ref: 119f1805924
Ref: ftp-Footnote-11807286
Ref: ftp-Footnote-21807350
Ref: ftp-Footnote-31807414
Ref: ftp-Footnote-41807478
Node: popen1807542
Ref: whatsnew/3 2 popen1807649
Ref: 11a01807649
Ref: popen-Footnote-11807963
Ref: popen-Footnote-21808027
Node: select<3>1808092
Ref: whatsnew/3 2 select1808212
Ref: 11a11808212
Ref: select<3>-Footnote-11808646
Node: gzip 和 zipfile1808710
Ref: whatsnew/3 2 gzip-and-zipfile1808835
Ref: 11a31808835
Ref: gzip 和 zipfile-Footnote-11810419
Ref: gzip 和 zipfile-Footnote-21810483
Ref: gzip 和 zipfile-Footnote-31810547
Ref: gzip 和 zipfile-Footnote-41810614
Ref: gzip 和 zipfile-Footnote-51810678
Ref: gzip 和 zipfile-Footnote-61810742
Node: tarfile<9>1810806
Ref: whatsnew/3 2 tarfile1810932
Ref: 11a71810932
Ref: tarfile<9>-Footnote-11812506
Node: hashlib<7>1812570
Ref: whatsnew/3 2 hashlib1812686
Ref: 11a91812686
Ref: hashlib<7>-Footnote-11813451
Node: ast<5>1813515
Ref: whatsnew/3 2 ast1813627
Ref: 11aa1813627
Node: os<13>1814568
Ref: whatsnew/3 2 os1814679
Ref: 11ab1814679
Node: shutil<8>1815456
Ref: whatsnew/3 2 shutil1815572
Ref: 11af1815572
Node: sqlite3<11>1817744
Ref: whatsnew/3 2 sqlite31817861
Ref: 11b11817861
Ref: sqlite3<11>-Footnote-11818511
Node: html<3>1818575
Ref: whatsnew/3 2 html1818693
Ref: 11b21818693
Node: socket<11>1818981
Ref: whatsnew/3 2 socket1819095
Ref: 11b31819095
Ref: socket<11>-Footnote-11819740
Ref: socket<11>-Footnote-21819804
Node: ssl<12>1819868
Ref: whatsnew/3 2 ssl1819979
Ref: 11b51819979
Ref: ssl<12>-Footnote-11822084
Ref: ssl<12>-Footnote-21822143
Ref: ssl<12>-Footnote-31822227
Ref: ssl<12>-Footnote-41822291
Ref: ssl<12>-Footnote-51822355
Ref: ssl<12>-Footnote-61822419
Ref: ssl<12>-Footnote-71822483
Ref: ssl<12>-Footnote-81822547
Ref: ssl<12>-Footnote-91822611
Node: nntp1822675
Ref: whatsnew/3 2 nntp1822788
Ref: 11b91822788
Ref: nntp-Footnote-11823354
Ref: nntp-Footnote-21823418
Node: certificates1823482
Ref: whatsnew/3 2 certificates1823598
Ref: 11ba1823598
Ref: certificates-Footnote-11823996
Node: imaplib<4>1824060
Ref: whatsnew/3 2 imaplib1824186
Ref: 11bc1824186
Ref: imaplib<4>-Footnote-11824465
Node: http client<4>1824529
Ref: whatsnew/3 2 http-client1824655
Ref: 11be1824655
Ref: http client<4>-Footnote-11826082
Node: unittest<11>1826147
Ref: whatsnew/3 2 unittest1826272
Ref: 11c11826272
Ref: unittest<11>-Footnote-11830958
Ref: unittest<11>-Footnote-21831023
Ref: unittest<11>-Footnote-31831087
Node: random<5>1831151
Ref: whatsnew/3 2 random1831271
Ref: 11c61831271
Ref: random<5>-Footnote-11831940
Node: poplib<4>1832004
Ref: whatsnew/3 2 poplib1832123
Ref: 11c91832123
Ref: poplib<4>-Footnote-11832480
Node: asyncore<2>1832544
Ref: whatsnew/3 2 asyncore1832665
Ref: 11ca1832665
Ref: asyncore<2>-Footnote-11833123
Node: tempfile<5>1833187
Ref: whatsnew/3 2 tempfile1833310
Ref: 11cb1833310
Ref: tempfile<5>-Footnote-11833724
Node: inspect<10>1833788
Ref: whatsnew/3 2 inspect1833908
Ref: 11cd1833908
Ref: inspect<10>-Footnote-11835289
Node: pydoc<6>1835354
Ref: whatsnew/3 2 pydoc1835469
Ref: 11cf1835469
Ref: pydoc<6>-Footnote-11835791
Node: dis<5>1835855
Ref: whatsnew/3 2 dis1835965
Ref: 11d01835965
Ref: dis<5>-Footnote-11838122
Node: dbm<7>1838186
Ref: whatsnew/3 2 dbm1838297
Ref: 11d21838297
Ref: dbm<7>-Footnote-11838494
Node: ctypes<2>1838558
Ref: whatsnew/3 2 ctypes1838670
Ref: 11d31838670
Node: site<4>1838789
Ref: whatsnew/3 2 site1838907
Ref: 11d51838907
Ref: site<4>-Footnote-11840143
Node: sysconfig<3>1840207
Ref: whatsnew/3 2 sysconfig1840322
Ref: 11d91840322
Node: pdb<8>1842548
Ref: whatsnew/3 2 pdb1842671
Ref: 11dd1842671
Node: configparser<6>1843576
Ref: whatsnew/3 2 configparser1843702
Ref: 11de1843702
Node: urllib parse<6>1846568
Ref: whatsnew/3 2 urllib-parse1846695
Ref: 11df1846695
Ref: urllib parse<6>-Footnote-11848706
Ref: urllib parse<6>-Footnote-21848749
Ref: urllib parse<6>-Footnote-31848808
Ref: urllib parse<6>-Footnote-41848872
Ref: urllib parse<6>-Footnote-51848936
Node: mailbox1849000
Ref: whatsnew/3 2 mailbox1849122
Ref: 11e31849122
Ref: mailbox-Footnote-11850698
Node: turtledemo1850762
Ref: whatsnew/3 2 turtledemo1850860
Ref: 11ea1850860
Ref: turtledemo-Footnote-11851296
Node: Multi-threading1851361
Ref: whatsnew/3 2 multi-threading1851508
Ref: 11eb1851508
Ref: Multi-threading-Footnote-11853142
Ref: Multi-threading-Footnote-21853221
Ref: Multi-threading-Footnote-31853285
Ref: Multi-threading-Footnote-41853351
Node: 最佳化<10>1853415
Ref: whatsnew/3 2 optimizations1853534
Ref: 11ed1853534
Ref: 最佳化<10>-Footnote-11857047
Ref: 最佳化<10>-Footnote-21857111
Ref: 最佳化<10>-Footnote-31857175
Ref: 最佳化<10>-Footnote-41857239
Ref: 最佳化<10>-Footnote-51857285
Ref: 最佳化<10>-Footnote-61857349
Ref: 最佳化<10>-Footnote-71857413
Ref: 最佳化<10>-Footnote-81857478
Ref: 最佳化<10>-Footnote-91857542
Ref: 最佳化<10>-Footnote-101857606
Ref: 最佳化<10>-Footnote-111857671
Ref: 最佳化<10>-Footnote-121857736
Ref: 最佳化<10>-Footnote-131857801
Ref: 最佳化<10>-Footnote-141857869
Ref: 最佳化<10>-Footnote-151857934
Ref: 最佳化<10>-Footnote-161858000
Node: Unicode1858065
Ref: whatsnew/3 2 unicode1858181
Ref: 11f21858181
Ref: Unicode-Footnote-11858733
Ref: Unicode-Footnote-21858784
Ref: Unicode-Footnote-31858828
Node: 編解碼器1858900
Ref: whatsnew/3 2 codecs1859009
Ref: 11f31859009
Ref: 編解碼器-Footnote-11859947
Node: 文件1860014
Ref: whatsnew/3 2 documentation1860120
Ref: 11f41860120
Ref: 文件-Footnote-11861764
Ref: 文件-Footnote-21861833
Ref: 文件-Footnote-31861909
Ref: 文件-Footnote-41861973
Node: IDLE1862037
Ref: whatsnew/3 2 idle1862146
Ref: 11f81862146
Ref: IDLE-Footnote-11862539
Ref: IDLE-Footnote-21862603
Node: Code Repository1862667
Ref: whatsnew/3 2 code-repository1862796
Ref: 11f91862796
Ref: Code Repository-Footnote-11863405
Ref: Code Repository-Footnote-21863444
Ref: Code Repository-Footnote-31863486
Ref: Code Repository-Footnote-41863540
Node: Build and C API Changes<4>1863584
Ref: whatsnew/3 2 build-and-c-api-changes1863730
Ref: 11fa1863730
Ref: Build and C API Changes<4>-Footnote-11867874
Ref: Build and C API Changes<4>-Footnote-21867939
Ref: Build and C API Changes<4>-Footnote-31868003
Ref: Build and C API Changes<4>-Footnote-41868067
Ref: Build and C API Changes<4>-Footnote-51868131
Ref: Build and C API Changes<4>-Footnote-61868195
Ref: Build and C API Changes<4>-Footnote-71868259
Ref: Build and C API Changes<4>-Footnote-81868323
Ref: Build and C API Changes<4>-Footnote-91868387
Ref: Build and C API Changes<4>-Footnote-101868451
Ref: Build and C API Changes<4>-Footnote-111868516
Ref: Build and C API Changes<4>-Footnote-121868581
Ref: Build and C API Changes<4>-Footnote-131868646
Ref: Build and C API Changes<4>-Footnote-141868711
Ref: Build and C API Changes<4>-Footnote-151868794
Node: Porting to Python 3 21868895
Ref: whatsnew/3 2 porting-to-python-3-21869017
Ref: 12031869017
Ref: Porting to Python 3 2-Footnote-11875870
Ref: Porting to Python 3 2-Footnote-21875934
Ref: Porting to Python 3 2-Footnote-31875998
Ref: Porting to Python 3 2-Footnote-41876043
Ref: Porting to Python 3 2-Footnote-51876108
Ref: Porting to Python 3 2-Footnote-61876173
Ref: Porting to Python 3 2-Footnote-71876238
Node: Python 3 1 有什麼新功能1876302
Ref: whatsnew/3 1 doc1876472
Ref: 12131876472
Ref: whatsnew/3 1 what-s-new-in-python-3-11876472
Ref: 12141876472
Node: PEP 372：有序字典1877095
Ref: whatsnew/3 1 pep-372-ordered-dictionaries1877240
Ref: 12151877240
Ref: PEP 372：有序字典-Footnote-11879690
Ref: PEP 372：有序字典-Footnote-21879718
Node: PEP 378 Format Specifier for Thousands Separator1879760
Ref: whatsnew/3 1 pep-378-format-specifier-for-thousands-separator1879936
Ref: 12161879936
Ref: PEP 378 Format Specifier for Thousands Separator-Footnote-11881174
Node: 其他語言更動<12>1881216
Ref: whatsnew/3 1 other-language-changes1881408
Ref: 12171881408
Ref: 其他語言更動<12>-Footnote-11886209
Ref: 其他語言更動<12>-Footnote-21886276
Ref: 其他語言更動<12>-Footnote-31886340
Ref: 其他語言更動<12>-Footnote-41886404
Ref: 其他語言更動<12>-Footnote-51886468
Ref: 其他語言更動<12>-Footnote-61886513
Ref: 其他語言更動<12>-Footnote-71886577
Node: New Improved and Deprecated Modules<2>1886641
Ref: whatsnew/3 1 new-improved-and-deprecated-modules1886798
Ref: 12181886798
Ref: New Improved and Deprecated Modules<2>-Footnote-11895428
Ref: New Improved and Deprecated Modules<2>-Footnote-21895495
Ref: New Improved and Deprecated Modules<2>-Footnote-31895559
Ref: New Improved and Deprecated Modules<2>-Footnote-41895623
Ref: New Improved and Deprecated Modules<2>-Footnote-51895687
Ref: New Improved and Deprecated Modules<2>-Footnote-61895751
Ref: New Improved and Deprecated Modules<2>-Footnote-71895793
Ref: New Improved and Deprecated Modules<2>-Footnote-81895857
Ref: New Improved and Deprecated Modules<2>-Footnote-91895921
Ref: New Improved and Deprecated Modules<2>-Footnote-101895985
Ref: New Improved and Deprecated Modules<2>-Footnote-111896050
Ref: New Improved and Deprecated Modules<2>-Footnote-121896115
Ref: New Improved and Deprecated Modules<2>-Footnote-131896180
Node: 最佳化<11>1896245
Ref: whatsnew/3 1 optimizations1896387
Ref: 12281896387
Ref: 最佳化<11>-Footnote-11898543
Ref: 最佳化<11>-Footnote-21898585
Ref: 最佳化<11>-Footnote-31898649
Ref: 最佳化<11>-Footnote-41898713
Ref: 最佳化<11>-Footnote-51898777
Ref: 最佳化<11>-Footnote-61898803
Ref: 最佳化<11>-Footnote-71898867
Node: IDLE<2>1898931
Ref: whatsnew/3 1 idle1899061
Ref: 12291899061
Ref: IDLE<2>-Footnote-11899279
Node: Build and C API Changes<5>1899343
Ref: whatsnew/3 1 build-and-c-api-changes1899481
Ref: 122a1899481
Ref: Build and C API Changes<5>-Footnote-11901757
Ref: Build and C API Changes<5>-Footnote-21901821
Ref: Build and C API Changes<5>-Footnote-31901885
Ref: Build and C API Changes<5>-Footnote-41901949
Ref: Build and C API Changes<5>-Footnote-51902013
Node: Porting to Python 3 11902077
Ref: whatsnew/3 1 porting-to-python-3-11902199
Ref: 122e1902199
Node: Python 3 0 有什麼新功能1903331
Ref: whatsnew/3 0 doc1903501
Ref: 122f1903501
Ref: whatsnew/3 0 what-s-new-in-python-3-01903501
Ref: 12301903501
Node: Common Stumbling Blocks1905335
Ref: whatsnew/3 0 common-stumbling-blocks1905451
Ref: 12311905451
Node: Print Is A Function1905817
Ref: whatsnew/3 0 print-is-a-function1905941
Ref: 12321905941
Ref: Print Is A Function-Footnote-11907619
Node: Views And Iterators Instead Of Lists1907661
Ref: whatsnew/3 0 views-and-iterators-instead-of-lists1907814
Ref: 12331907814
Node: Ordering Comparisons1909652
Ref: whatsnew/3 0 ordering-comparisons1909792
Ref: 12361909792
Node: 整數1911214
Ref: whatsnew/3 0 integers1911358
Ref: 12371911358
Ref: 整數-Footnote-11912569
Ref: 整數-Footnote-21912611
Node: Text Vs Data Instead Of Unicode Vs 8-bit1912653
Ref: whatsnew/3 0 text-vs-data-instead-of-unicode-vs-8-bit1912768
Ref: 12381912768
Ref: Text Vs Data Instead Of Unicode Vs 8-bit-Footnote-11919345
Ref: Text Vs Data Instead Of Unicode Vs 8-bit-Footnote-21919387
Ref: Text Vs Data Instead Of Unicode Vs 8-bit-Footnote-31919429
Node: 語法變更概要1919471
Ref: whatsnew/3 0 overview-of-syntax-changes1919633
Ref: 123c1919633
Node: New Syntax1919828
Ref: whatsnew/3 0 new-syntax1919914
Ref: 123d1919914
Ref: New Syntax-Footnote-11922460
Ref: New Syntax-Footnote-21922502
Ref: New Syntax-Footnote-31922544
Ref: New Syntax-Footnote-41922586
Ref: New Syntax-Footnote-51922628
Node: 語法變更1922670
Ref: whatsnew/3 0 changed-syntax1922786
Ref: 12401922786
Ref: 語法變更-Footnote-11924457
Ref: 語法變更-Footnote-21924499
Ref: 語法變更-Footnote-31924541
Ref: 語法變更-Footnote-41924583
Node: 已被移除的語法1924625
Ref: whatsnew/3 0 removed-syntax1924722
Ref: 12411924722
Ref: 已被移除的語法-Footnote-11925911
Ref: 已被移除的語法-Footnote-21925953
Node: Changes Already Present In Python 2 61925995
Ref: whatsnew/3 0 changes-already-present-in-python-2-61926149
Ref: 12431926149
Node: 函式庫變更1929995
Ref: whatsnew/3 0 library-changes1930175
Ref: 12561930175
Ref: 函式庫變更-Footnote-11936404
Ref: 函式庫變更-Footnote-21936446
Ref: 函式庫變更-Footnote-31936488
Ref: 函式庫變更-Footnote-41936530
Ref: 函式庫變更-Footnote-51936572
Ref: 函式庫變更-Footnote-61936614
Node: PEP 3101 A New Approach To String Formatting1936656
Ref: whatsnew/3 0 pep-3101-a-new-approach-to-string-formatting1936820
Ref: 12591936820
Ref: PEP 3101 A New Approach To String Formatting-Footnote-11937212
Node: Changes To Exceptions1937254
Ref: whatsnew/3 0 changes-to-exceptions1937430
Ref: 125a1937430
Ref: Changes To Exceptions-Footnote-11940961
Ref: Changes To Exceptions-Footnote-21941003
Ref: Changes To Exceptions-Footnote-31941045
Ref: Changes To Exceptions-Footnote-41941087
Ref: Changes To Exceptions-Footnote-51941129
Node: Miscellaneous Other Changes1941171
Ref: whatsnew/3 0 miscellaneous-other-changes1941329
Ref: 125e1941329
Node: Operators And Special Methods1941457
Ref: whatsnew/3 0 operators-and-special-methods1941567
Ref: 125f1941567
Ref: Operators And Special Methods-Footnote-11943234
Node: Builtins1943276
Ref: whatsnew/3 0 builtins1943386
Ref: 12691943386
Ref: Builtins-Footnote-11945868
Ref: Builtins-Footnote-21945910
Node: Build and C API Changes<6>1945952
Ref: whatsnew/3 0 build-and-c-api-changes1946100
Ref: 12701946100
Ref: Build and C API Changes<6>-Footnote-11947138
Ref: Build and C API Changes<6>-Footnote-21947180
Ref: Build and C API Changes<6>-Footnote-31947222
Node: Performance1947264
Ref: whatsnew/3 0 performance1947406
Ref: 12721947406
Node: Porting To Python 3 01947725
Ref: whatsnew/3 0 porting-to-python-3-01947832
Ref: 12731947832
Node: Python 2 7 有什麼新功能1949331
Ref: whatsnew/2 7 doc1949501
Ref: 12751949501
Ref: whatsnew/2 7 what-s-new-in-python-2-71949501
Ref: 12761949501
Node: Python 2 x 的未來1951931
Ref: whatsnew/2 7 the-future-for-python-2-x1952073
Ref: 12771952073
Ref: whatsnew/2 7 whatsnew27-python311952073
Ref: 12781952073
Ref: Python 2 x 的未來-Footnote-11955374
Ref: Python 2 x 的未來-Footnote-21955416
Node: Changes to the Handling of Deprecation Warnings1955453
Ref: whatsnew/2 7 changes-to-the-handling-of-deprecation-warnings1955623
Ref: 127a1955623
Ref: Changes to the Handling of Deprecation Warnings-Footnote-11957196
Node: Python 3 1 Features1957260
Ref: whatsnew/2 7 python-3-1-features1957461
Ref: 127b1957461
Node: PEP 372 Adding an Ordered Dictionary to collections1959374
Ref: whatsnew/2 7 pep-03721959579
Ref: 127c1959579
Ref: whatsnew/2 7 pep-372-adding-an-ordered-dictionary-to-collections1959579
Ref: 127f1959579
Ref: PEP 372 Adding an Ordered Dictionary to collections-Footnote-11963182
Ref: PEP 372 Adding an Ordered Dictionary to collections-Footnote-21963210
Node: PEP 378 Format Specifier for Thousands Separator<2>1963252
Ref: whatsnew/2 7 pep-03781963491
Ref: 127d1963491
Ref: whatsnew/2 7 pep-378-format-specifier-for-thousands-separator1963491
Ref: 12811963491
Ref: PEP 378 Format Specifier for Thousands Separator<2>-Footnote-11964994
Node: PEP 389 The argparse Module for Parsing Command Lines1965036
Ref: whatsnew/2 7 pep-389-the-argparse-module-for-parsing-command-lines1965274
Ref: 12821965274
Ref: PEP 389 The argparse Module for Parsing Command Lines-Footnote-11969261
Node: PEP 391 Dictionary-Based Configuration For Logging1969303
Ref: whatsnew/2 7 pep-391-dictionary-based-configuration-for-logging1969515
Ref: 12831969515
Ref: PEP 391 Dictionary-Based Configuration For Logging-Footnote-11973395
Node: PEP 3106 Dictionary Views1973437
Ref: whatsnew/2 7 pep-3106-dictionary-views1973626
Ref: 128a1973626
Ref: PEP 3106 Dictionary Views-Footnote-11975736
Ref: PEP 3106 Dictionary Views-Footnote-21975778
Node: PEP 3137 The memoryview Object1975842
Ref: whatsnew/2 7 pep-3137-the-memoryview-object1976003
Ref: 128b1976003
Ref: PEP 3137 The memoryview Object-Footnote-11977661
Ref: PEP 3137 The memoryview Object-Footnote-21977703
Node: 其他語言更動<13>1977767
Ref: whatsnew/2 7 other-language-changes1977927
Ref: 128c1977927
Ref: 其他語言更動<13>-Footnote-11987827
Ref: 其他語言更動<13>-Footnote-21987891
Ref: 其他語言更動<13>-Footnote-31987955
Ref: 其他語言更動<13>-Footnote-41988019
Ref: 其他語言更動<13>-Footnote-51988083
Ref: 其他語言更動<13>-Footnote-61988147
Ref: 其他語言更動<13>-Footnote-71988211
Ref: 其他語言更動<13>-Footnote-81988275
Ref: 其他語言更動<13>-Footnote-91988339
Ref: 其他語言更動<13>-Footnote-101988403
Ref: 其他語言更動<13>-Footnote-111988468
Ref: 其他語言更動<13>-Footnote-121988533
Ref: 其他語言更動<13>-Footnote-131988598
Ref: 其他語言更動<13>-Footnote-141988663
Ref: 其他語言更動<13>-Footnote-151988731
Ref: 其他語言更動<13>-Footnote-161988796
Ref: 其他語言更動<13>-Footnote-171988861
Ref: 其他語言更動<13>-Footnote-181988926
Ref: 其他語言更動<13>-Footnote-191988994
Ref: 其他語言更動<13>-Footnote-201989059
Ref: 其他語言更動<13>-Footnote-211989124
Ref: 其他語言更動<13>-Footnote-221989189
Ref: 其他語言更動<13>-Footnote-231989254
Ref: 其他語言更動<13>-Footnote-241989319
Node: Interpreter Changes1989384
Ref: whatsnew/2 7 interpreter-changes1989484
Ref: 12901989484
Ref: whatsnew/2 7 new-27-interpreter1989484
Ref: 12911989484
Ref: Interpreter Changes-Footnote-11990143
Node: 最佳化<12>1990207
Ref: whatsnew/2 7 optimizations1990307
Ref: 12921990307
Ref: 最佳化<12>-Footnote-11995176
Ref: 最佳化<12>-Footnote-21995240
Ref: 最佳化<12>-Footnote-31995304
Ref: 最佳化<12>-Footnote-41995368
Ref: 最佳化<12>-Footnote-51995432
Ref: 最佳化<12>-Footnote-61995496
Ref: 最佳化<12>-Footnote-71995563
Ref: 最佳化<12>-Footnote-81995627
Ref: 最佳化<12>-Footnote-91995691
Ref: 最佳化<12>-Footnote-101995755
Ref: 最佳化<12>-Footnote-111995820
Ref: 最佳化<12>-Footnote-121995885
Ref: 最佳化<12>-Footnote-131995950
Node: New and Improved Modules1996015
Ref: whatsnew/2 7 new-and-improved-modules1996171
Ref: 12941996171
Ref: New and Improved Modules-Footnote-12031493
Ref: New and Improved Modules-Footnote-22031557
Ref: New and Improved Modules-Footnote-32031621
Ref: New and Improved Modules-Footnote-42031674
Ref: New and Improved Modules-Footnote-52031738
Ref: New and Improved Modules-Footnote-62031802
Ref: New and Improved Modules-Footnote-72031869
Ref: New and Improved Modules-Footnote-82031933
Ref: New and Improved Modules-Footnote-92031997
Ref: New and Improved Modules-Footnote-102032061
Ref: New and Improved Modules-Footnote-112032126
Ref: New and Improved Modules-Footnote-122032191
Ref: New and Improved Modules-Footnote-132032256
Ref: New and Improved Modules-Footnote-142032296
Ref: New and Improved Modules-Footnote-152032361
Ref: New and Improved Modules-Footnote-162032426
Ref: New and Improved Modules-Footnote-172032491
Ref: New and Improved Modules-Footnote-182032556
Ref: New and Improved Modules-Footnote-192032621
Ref: New and Improved Modules-Footnote-202032686
Ref: New and Improved Modules-Footnote-212032751
Ref: New and Improved Modules-Footnote-222032816
Ref: New and Improved Modules-Footnote-232032881
Ref: New and Improved Modules-Footnote-242032946
Ref: New and Improved Modules-Footnote-252033011
Ref: New and Improved Modules-Footnote-262033076
Ref: New and Improved Modules-Footnote-272033144
Ref: New and Improved Modules-Footnote-282033209
Ref: New and Improved Modules-Footnote-292033274
Ref: New and Improved Modules-Footnote-302033339
Ref: New and Improved Modules-Footnote-312033404
Ref: New and Improved Modules-Footnote-322033469
Ref: New and Improved Modules-Footnote-332033534
Ref: New and Improved Modules-Footnote-342033599
Ref: New and Improved Modules-Footnote-352033664
Ref: New and Improved Modules-Footnote-362033729
Ref: New and Improved Modules-Footnote-372033794
Ref: New and Improved Modules-Footnote-382033859
Ref: New and Improved Modules-Footnote-392033924
Ref: New and Improved Modules-Footnote-402033989
Ref: New and Improved Modules-Footnote-412034054
Ref: New and Improved Modules-Footnote-422034119
Ref: New and Improved Modules-Footnote-432034184
Ref: New and Improved Modules-Footnote-442034249
Ref: New and Improved Modules-Footnote-452034314
Ref: New and Improved Modules-Footnote-462034379
Ref: New and Improved Modules-Footnote-472034444
Ref: New and Improved Modules-Footnote-482034509
Ref: New and Improved Modules-Footnote-492034577
Ref: New and Improved Modules-Footnote-502034642
Ref: New and Improved Modules-Footnote-512034707
Ref: New and Improved Modules-Footnote-522034772
Ref: New and Improved Modules-Footnote-532034837
Ref: New and Improved Modules-Footnote-542034902
Ref: New and Improved Modules-Footnote-552034967
Ref: New and Improved Modules-Footnote-562035032
Ref: New and Improved Modules-Footnote-572035097
Ref: New and Improved Modules-Footnote-582035162
Ref: New and Improved Modules-Footnote-592035227
Ref: New and Improved Modules-Footnote-602035292
Ref: New and Improved Modules-Footnote-612035357
Ref: New and Improved Modules-Footnote-622035422
Ref: New and Improved Modules-Footnote-632035487
Ref: New and Improved Modules-Footnote-642035552
Ref: New and Improved Modules-Footnote-652035617
Ref: New and Improved Modules-Footnote-662035682
Ref: New and Improved Modules-Footnote-672035747
Ref: New and Improved Modules-Footnote-682035812
Ref: New and Improved Modules-Footnote-692035877
Ref: New and Improved Modules-Footnote-702035923
Ref: New and Improved Modules-Footnote-712035988
Ref: New and Improved Modules-Footnote-722036053
Ref: New and Improved Modules-Footnote-732036118
Ref: New and Improved Modules-Footnote-742036183
Ref: New and Improved Modules-Footnote-752036248
Ref: New and Improved Modules-Footnote-762036313
Ref: New and Improved Modules-Footnote-772036378
Ref: New and Improved Modules-Footnote-782036443
Ref: New and Improved Modules-Footnote-792036511
Ref: New and Improved Modules-Footnote-802036576
Ref: New and Improved Modules-Footnote-812036641
Ref: New and Improved Modules-Footnote-822036706
Ref: New and Improved Modules-Footnote-832036771
Ref: New and Improved Modules-Footnote-842036836
Ref: New and Improved Modules-Footnote-852036901
Ref: New and Improved Modules-Footnote-862036969
Ref: New and Improved Modules-Footnote-872037037
Ref: New and Improved Modules-Footnote-882037102
Ref: New and Improved Modules-Footnote-892037162
Ref: New and Improved Modules-Footnote-902037222
Ref: New and Improved Modules-Footnote-912037287
Ref: New and Improved Modules-Footnote-922037352
Ref: New and Improved Modules-Footnote-932037417
Ref: New and Improved Modules-Footnote-942037482
Ref: New and Improved Modules-Footnote-952037547
Ref: New and Improved Modules-Footnote-962037612
Ref: New and Improved Modules-Footnote-972037677
Node: New module importlib2037742
Ref: whatsnew/2 7 importlib-section2037852
Ref: 127e2037852
Ref: whatsnew/2 7 new-module-importlib2037852
Ref: 12c02037852
Node: New module sysconfig2039385
Ref: whatsnew/2 7 new-module-sysconfig2039529
Ref: 12c12039529
Node: ttk Themed Widgets for Tk2040850
Ref: whatsnew/2 7 ttk-themed-widgets-for-tk2040997
Ref: 12c32040997
Ref: ttk Themed Widgets for Tk-Footnote-12042081
Ref: ttk Themed Widgets for Tk-Footnote-22042145
Node: Updated module unittest2042209
Ref: whatsnew/2 7 unittest-section2042366
Ref: 12c42042366
Ref: whatsnew/2 7 updated-module-unittest2042366
Ref: 12c52042366
Ref: Updated module unittest-Footnote-12051274
Ref: Updated module unittest-Footnote-22051318
Ref: Updated module unittest-Footnote-32051345
Ref: Updated module unittest-Footnote-42051382
Ref: Updated module unittest-Footnote-52051446
Ref: Updated module unittest-Footnote-62051510
Ref: Updated module unittest-Footnote-72051577
Ref: Updated module unittest-Footnote-82051641
Ref: Updated module unittest-Footnote-92051705
Ref: Updated module unittest-Footnote-102051769
Ref: Updated module unittest-Footnote-112051834
Ref: Updated module unittest-Footnote-122051899
Ref: Updated module unittest-Footnote-132051964
Ref: Updated module unittest-Footnote-142052029
Ref: Updated module unittest-Footnote-152052094
Node: Updated module ElementTree 1 32052159
Ref: whatsnew/2 7 elementtree-section2052282
Ref: 12e02052282
Ref: whatsnew/2 7 updated-module-elementtree-1-32052282
Ref: 12e12052282
Ref: Updated module ElementTree 1 3-Footnote-12056277
Node: Build and C API Changes<7>2056341
Ref: whatsnew/2 7 build-and-c-api-changes2056498
Ref: 12e42056498
Ref: Build and C API Changes<7>-Footnote-12065111
Ref: Build and C API Changes<7>-Footnote-22065224
Ref: Build and C API Changes<7>-Footnote-32065288
Ref: Build and C API Changes<7>-Footnote-42065352
Ref: Build and C API Changes<7>-Footnote-52065416
Ref: Build and C API Changes<7>-Footnote-62065480
Ref: Build and C API Changes<7>-Footnote-72065544
Ref: Build and C API Changes<7>-Footnote-82065608
Ref: Build and C API Changes<7>-Footnote-92065677
Ref: Build and C API Changes<7>-Footnote-102065741
Ref: Build and C API Changes<7>-Footnote-112065806
Ref: Build and C API Changes<7>-Footnote-122065871
Ref: Build and C API Changes<7>-Footnote-132065936
Ref: Build and C API Changes<7>-Footnote-142066004
Ref: Build and C API Changes<7>-Footnote-152066072
Ref: Build and C API Changes<7>-Footnote-162066137
Ref: Build and C API Changes<7>-Footnote-172066202
Ref: Build and C API Changes<7>-Footnote-182066267
Ref: Build and C API Changes<7>-Footnote-192066332
Ref: Build and C API Changes<7>-Footnote-202066397
Ref: Build and C API Changes<7>-Footnote-212066465
Ref: Build and C API Changes<7>-Footnote-222066530
Node: Capsules2066595
Ref: whatsnew/2 7 capsules2066704
Ref: 12e72066704
Ref: whatsnew/2 7 whatsnew27-capsules2066704
Ref: 12e82066704
Ref: Capsules-Footnote-12068699
Node: Port-Specific Changes Windows2068763
Ref: whatsnew/2 7 port-specific-changes-windows2068911
Ref: 12eb2068911
Ref: Port-Specific Changes Windows-Footnote-12070694
Ref: Port-Specific Changes Windows-Footnote-22070758
Ref: Port-Specific Changes Windows-Footnote-32070822
Ref: Port-Specific Changes Windows-Footnote-42070886
Ref: Port-Specific Changes Windows-Footnote-52070953
Ref: Port-Specific Changes Windows-Footnote-62071017
Node: Port-Specific Changes Mac OS X2071081
Ref: whatsnew/2 7 port-specific-changes-mac-os-x2071250
Ref: 12f72071250
Ref: Port-Specific Changes Mac OS X-Footnote-12072238
Ref: Port-Specific Changes Mac OS X-Footnote-22072302
Node: Port-Specific Changes FreeBSD2072367
Ref: whatsnew/2 7 port-specific-changes-freebsd2072498
Ref: 12f82072498
Ref: Port-Specific Changes FreeBSD-Footnote-12072901
Node: Other Changes and Fixes2072965
Ref: whatsnew/2 7 other-changes-and-fixes2073119
Ref: 12f92073119
Ref: Other Changes and Fixes-Footnote-12075314
Ref: Other Changes and Fixes-Footnote-22075378
Ref: Other Changes and Fixes-Footnote-32075445
Ref: Other Changes and Fixes-Footnote-42075509
Ref: Other Changes and Fixes-Footnote-52075573
Node: Porting to Python 2 72075637
Ref: whatsnew/2 7 porting-to-python-2-72075818
Ref: 12fb2075818
Ref: Porting to Python 2 7-Footnote-12081355
Ref: Porting to Python 2 7-Footnote-22081419
Ref: Porting to Python 2 7-Footnote-32081483
Ref: Porting to Python 2 7-Footnote-42081547
Ref: Porting to Python 2 7-Footnote-52081611
Ref: Porting to Python 2 7-Footnote-62081675
Ref: Porting to Python 2 7-Footnote-72081739
Ref: Porting to Python 2 7-Footnote-82081803
Ref: Porting to Python 2 7-Footnote-92081867
Ref: Porting to Python 2 7-Footnote-102081931
Ref: Porting to Python 2 7-Footnote-112081996
Ref: Porting to Python 2 7-Footnote-122082061
Ref: Porting to Python 2 7-Footnote-132082126
Ref: Porting to Python 2 7-Footnote-142082186
Node: New Features Added to Python 2 7 Maintenance Releases2082251
Ref: whatsnew/2 7 new-features-added-to-python-2-7-maintenance-releases2082415
Ref: 12fc2082415
Ref: whatsnew/2 7 py27-maintenance-enhancements2082415
Ref: 12792082415
Node: Two new environment variables for debug mode2083878
Ref: whatsnew/2 7 two-new-environment-variables-for-debug-mode2084072
Ref: 12fd2084072
Ref: Two new environment variables for debug mode-Footnote-12084753
Ref: Two new environment variables for debug mode-Footnote-22084818
Node: PEP 434 IDLE Enhancement Exception for All Branches2084883
Ref: whatsnew/2 7 pep-434-idle-enhancement-exception-for-all-branches2085138
Ref: 12fe2085138
Ref: PEP 434 IDLE Enhancement Exception for All Branches-Footnote-12085658
Node: PEP 466 Network Security Enhancements for Python 2 72085700
Ref: whatsnew/2 7 pep-466-network-security-enhancements-for-python-2-72085959
Ref: 12ff2085959
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-12088190
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-22088232
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-32088274
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-42088339
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-52088404
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-62088446
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-72088511
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-82088576
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-92088645
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-102088687
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-112088753
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-122088819
Node: PEP 477 Backport ensurepip PEP 453 to Python 2 72088885
Ref: whatsnew/2 7 pep-477-backport-ensurepip-pep-453-to-python-2-72089172
Ref: 13022089172
Ref: PEP 477 Backport ensurepip PEP 453 to Python 2 7-Footnote-12089668
Ref: PEP 477 Backport ensurepip PEP 453 to Python 2 7-Footnote-22089710
Node: Bootstrapping pip By Default<2>2089752
Ref: whatsnew/2 7 bootstrapping-pip-by-default2089901
Ref: 13032089901
Ref: Bootstrapping pip By Default<2>-Footnote-12091569
Ref: Bootstrapping pip By Default<2>-Footnote-22091611
Node: Documentation Changes<2>2091701
Ref: whatsnew/2 7 documentation-changes2091850
Ref: 13042091850
Ref: whatsnew/2 7 id12091850
Ref: 13052091850
Ref: Documentation Changes<2>-Footnote-12092780
Ref: Documentation Changes<2>-Footnote-22092817
Node: PEP 476 Enabling certificate verification by default for stdlib http clients<2>2092859
Ref: whatsnew/2 7 pep-476-enabling-certificate-verification-by-default-for-stdlib-http-clients2093151
Ref: 13062093151
Ref: PEP 476 Enabling certificate verification by default for stdlib http clients<2>-Footnote-12094247
Node: PEP 493 HTTPS verification migration tools for Python 2 72094289
Ref: whatsnew/2 7 pep-493-https-verification-migration-tools-for-python-2-72094567
Ref: 13072094567
Ref: PEP 493 HTTPS verification migration tools for Python 2 7-Footnote-12095725
Node: New make regen-all build target<3>2095767
Ref: whatsnew/2 7 new-make-regen-all-build-target2096003
Ref: 13082096003
Ref: New make regen-all build target<3>-Footnote-12096801
Ref: New make regen-all build target<3>-Footnote-22096869
Node: Removal of make touch build target<3>2096934
Ref: whatsnew/2 7 removal-of-make-touch-build-target2097104
Ref: 13092097104
Ref: Removal of make touch build target<3>-Footnote-12097543
Node: 致謝2097608
Ref: whatsnew/2 7 acknowledgements2097742
Ref: 130a2097742
Ref: whatsnew/2 7 acks272097742
Ref: 130b2097742
Node: Python 2 6 有什麼新功能2097993
Ref: whatsnew/2 6 doc2098163
Ref: 130c2098163
Ref: whatsnew/2 6 what-s-new-in-python-2-62098163
Ref: 130d2098163
Ref: whatsnew/2 6 whats-new-in-2-62098163
Ref: 12442098163
Ref: Python 2 6 有什麼新功能-Footnote-12101142
Node: Python 3 02101184
Ref: whatsnew/2 6 python-3-02101303
Ref: 130e2101303
Ref: Python 3 0-Footnote-12103408
Ref: Python 3 0-Footnote-22103450
Node: Changes to the Development Process2103492
Ref: whatsnew/2 6 changes-to-the-development-process2103648
Ref: 130f2103648
Node: New Issue Tracker Roundup2104164
Ref: whatsnew/2 6 new-issue-tracker-roundup2104323
Ref: 13102104323
Ref: New Issue Tracker Roundup-Footnote-12106356
Ref: New Issue Tracker Roundup-Footnote-22106405
Ref: New Issue Tracker Roundup-Footnote-32106436
Ref: New Issue Tracker Roundup-Footnote-42106476
Ref: New Issue Tracker Roundup-Footnote-52106511
Node: New Documentation Format reStructuredText Using Sphinx2106549
Ref: whatsnew/2 6 new-documentation-format-restructuredtext-using-sphinx2106708
Ref: 13112106708
Ref: New Documentation Format reStructuredText Using Sphinx-Footnote-12108821
Ref: New Documentation Format reStructuredText Using Sphinx-Footnote-22108880
Ref: New Documentation Format reStructuredText Using Sphinx-Footnote-32108929
Ref: New Documentation Format reStructuredText Using Sphinx-Footnote-42108965
Node: PEP 343 The 'with' statement2109005
Ref: whatsnew/2 6 pep-03432109203
Ref: 12452109203
Ref: whatsnew/2 6 pep-343-the-with-statement2109203
Ref: 13122109203
Node: Writing Context Managers2112433
Ref: whatsnew/2 6 new-26-context-managers2112548
Ref: 12462112548
Ref: whatsnew/2 6 writing-context-managers2112548
Ref: 13132112548
Node: contextlib 模組2117017
Ref: whatsnew/2 6 new-module-contextlib2117132
Ref: 12472117132
Ref: whatsnew/2 6 the-contextlib-module2117132
Ref: 13142117132
Ref: contextlib 模組-Footnote-12119577
Node: PEP 366 Explicit Relative Imports From a Main Module2119619
Ref: whatsnew/2 6 pep-03662119823
Ref: 12482119823
Ref: whatsnew/2 6 pep-366-explicit-relative-imports-from-a-main-module2119823
Ref: 13152119823
Node: PEP 370 Per-user site-packages Directory2120583
Ref: whatsnew/2 6 pep-03702120794
Ref: 12492120794
Ref: whatsnew/2 6 pep-370-per-user-site-packages-directory2120794
Ref: 13172120794
Ref: PEP 370 Per-user site-packages Directory-Footnote-12122249
Node: PEP 371 The multiprocessing Package2122291
Ref: whatsnew/2 6 pep-03712122485
Ref: 124a2122485
Ref: whatsnew/2 6 pep-371-the-multiprocessing-package2122485
Ref: 131b2122485
Ref: PEP 371 The multiprocessing Package-Footnote-12127600
Node: PEP 3101 Advanced String Formatting2127642
Ref: whatsnew/2 6 pep-31012127824
Ref: 124b2127824
Ref: whatsnew/2 6 pep-3101-advanced-string-formatting2127824
Ref: 131d2127824
Ref: PEP 3101 Advanced String Formatting-Footnote-12133491
Node: PEP 3105 print As a Function2133533
Ref: whatsnew/2 6 pep-31052133715
Ref: 124c2133715
Ref: whatsnew/2 6 pep-3105-print-as-a-function2133715
Ref: 131f2133715
Ref: PEP 3105 print As a Function-Footnote-12134845
Node: PEP 3110 Exception-Handling Changes2134887
Ref: whatsnew/2 6 pep-31102135056
Ref: 124d2135056
Ref: whatsnew/2 6 pep-3110-exception-handling-changes2135056
Ref: 13202135056
Ref: PEP 3110 Exception-Handling Changes-Footnote-12136634
Node: PEP 3112 Byte Literals2136676
Ref: whatsnew/2 6 pep-31122136841
Ref: 124e2136841
Ref: whatsnew/2 6 pep-3112-byte-literals2136841
Ref: 13212136841
Ref: PEP 3112 Byte Literals-Footnote-12139848
Node: PEP 3116 New I/O Library2139890
Ref: whatsnew/2 6 pep-31162140049
Ref: 124f2140049
Ref: whatsnew/2 6 pep-3116-new-i-o-library2140049
Ref: 13262140049
Ref: PEP 3116 New I/O Library-Footnote-12143658
Node: PEP 3118：修訂緩衝協定2143700
Ref: whatsnew/2 6 pep-31182143867
Ref: 12502143867
Ref: whatsnew/2 6 pep-3118-revised-buffer-protocol2143867
Ref: 13272143867
Ref: PEP 3118：修訂緩衝協定-Footnote-12145972
Node: PEP 3119 Abstract Base Classes2146014
Ref: whatsnew/2 6 pep-31192146200
Ref: 12512146200
Ref: whatsnew/2 6 pep-3119-abstract-base-classes2146200
Ref: 132b2146200
Ref: PEP 3119 Abstract Base Classes-Footnote-12151525
Node: PEP 3127 Integer Literal Support and Syntax2151567
Ref: whatsnew/2 6 pep-31272151749
Ref: 12522151749
Ref: whatsnew/2 6 pep-3127-integer-literal-support-and-syntax2151749
Ref: 132c2151749
Ref: PEP 3127 Integer Literal Support and Syntax-Footnote-12153081
Node: PEP 3129 Class Decorators2153123
Ref: whatsnew/2 6 pep-31292153312
Ref: 12532153312
Ref: whatsnew/2 6 pep-3129-class-decorators2153312
Ref: 132d2153312
Ref: PEP 3129 Class Decorators-Footnote-12153711
Node: PEP 3141 A Type Hierarchy for Numbers2153753
Ref: whatsnew/2 6 pep-31412153921
Ref: 12542153921
Ref: whatsnew/2 6 pep-3141-a-type-hierarchy-for-numbers2153921
Ref: 132e2153921
Ref: PEP 3141 A Type Hierarchy for Numbers-Footnote-12156111
Ref: PEP 3141 A Type Hierarchy for Numbers-Footnote-22156153
Ref: PEP 3141 A Type Hierarchy for Numbers-Footnote-32156251
Node: The fractions Module2156357
Ref: whatsnew/2 6 the-fractions-module2156451
Ref: 13322156451
Node: 其他語言更動<14>2158056
Ref: whatsnew/2 6 other-language-changes2158226
Ref: 13332158226
Ref: 其他語言更動<14>-Footnote-12167015
Ref: 其他語言更動<14>-Footnote-22167082
Ref: 其他語言更動<14>-Footnote-32167146
Ref: 其他語言更動<14>-Footnote-42167213
Ref: 其他語言更動<14>-Footnote-52167277
Ref: 其他語言更動<14>-Footnote-62167341
Ref: 其他語言更動<14>-Footnote-72167405
Ref: 其他語言更動<14>-Footnote-82167469
Ref: 其他語言更動<14>-Footnote-92167533
Ref: 其他語言更動<14>-Footnote-102167597
Ref: 其他語言更動<14>-Footnote-112167662
Ref: 其他語言更動<14>-Footnote-122167727
Ref: 其他語言更動<14>-Footnote-132167795
Ref: 其他語言更動<14>-Footnote-142167863
Ref: 其他語言更動<14>-Footnote-152167931
Ref: 其他語言更動<14>-Footnote-162167999
Node: 最佳化<13>2168067
Ref: whatsnew/2 6 optimizations2168170
Ref: 13372168170
Ref: 最佳化<13>-Footnote-12170999
Ref: 最佳化<13>-Footnote-22171066
Ref: 最佳化<13>-Footnote-32171133
Ref: 最佳化<13>-Footnote-42171197
Node: Interpreter Changes<2>2171261
Ref: whatsnew/2 6 interpreter-changes2171364
Ref: 13382171364
Ref: whatsnew/2 6 new-26-interpreter2171364
Ref: 13392171364
Node: New and Improved Modules<2>2172933
Ref: whatsnew/2 6 new-and-improved-modules2173091
Ref: 133d2173091
Ref: New and Improved Modules<2>-Footnote-12215496
Ref: New and Improved Modules<2>-Footnote-22215563
Ref: New and Improved Modules<2>-Footnote-32215616
Ref: New and Improved Modules<2>-Footnote-42215680
Ref: New and Improved Modules<2>-Footnote-52215746
Ref: New and Improved Modules<2>-Footnote-62215810
Ref: New and Improved Modules<2>-Footnote-72215877
Ref: New and Improved Modules<2>-Footnote-82215941
Ref: New and Improved Modules<2>-Footnote-92215995
Ref: New and Improved Modules<2>-Footnote-102216062
Ref: New and Improved Modules<2>-Footnote-112216130
Ref: New and Improved Modules<2>-Footnote-122216198
Ref: New and Improved Modules<2>-Footnote-132216263
Ref: New and Improved Modules<2>-Footnote-142216328
Ref: New and Improved Modules<2>-Footnote-152216395
Ref: New and Improved Modules<2>-Footnote-162216460
Ref: New and Improved Modules<2>-Footnote-172216528
Ref: New and Improved Modules<2>-Footnote-182216593
Ref: New and Improved Modules<2>-Footnote-192216661
Ref: New and Improved Modules<2>-Footnote-202216729
Ref: New and Improved Modules<2>-Footnote-212216797
Ref: New and Improved Modules<2>-Footnote-222216864
Ref: New and Improved Modules<2>-Footnote-232216932
Ref: New and Improved Modules<2>-Footnote-242217000
Ref: New and Improved Modules<2>-Footnote-252217065
Ref: New and Improved Modules<2>-Footnote-262217130
Ref: New and Improved Modules<2>-Footnote-272217198
Ref: New and Improved Modules<2>-Footnote-282217266
Ref: New and Improved Modules<2>-Footnote-292217333
Ref: New and Improved Modules<2>-Footnote-302217398
Ref: New and Improved Modules<2>-Footnote-312217463
Ref: New and Improved Modules<2>-Footnote-322217528
Ref: New and Improved Modules<2>-Footnote-332217593
Ref: New and Improved Modules<2>-Footnote-342217658
Ref: New and Improved Modules<2>-Footnote-352217723
Ref: New and Improved Modules<2>-Footnote-362217788
Ref: New and Improved Modules<2>-Footnote-372217848
Ref: New and Improved Modules<2>-Footnote-382217915
Ref: New and Improved Modules<2>-Footnote-392217975
Ref: New and Improved Modules<2>-Footnote-402218042
Ref: New and Improved Modules<2>-Footnote-412218107
Ref: New and Improved Modules<2>-Footnote-422218174
Ref: New and Improved Modules<2>-Footnote-432218242
Ref: New and Improved Modules<2>-Footnote-442218307
Ref: New and Improved Modules<2>-Footnote-452218372
Ref: New and Improved Modules<2>-Footnote-462218437
Ref: New and Improved Modules<2>-Footnote-472218505
Ref: New and Improved Modules<2>-Footnote-482218570
Ref: New and Improved Modules<2>-Footnote-492218635
Ref: New and Improved Modules<2>-Footnote-502218703
Ref: New and Improved Modules<2>-Footnote-512218768
Ref: New and Improved Modules<2>-Footnote-522218836
Ref: New and Improved Modules<2>-Footnote-532218901
Ref: New and Improved Modules<2>-Footnote-542218969
Ref: New and Improved Modules<2>-Footnote-552219034
Ref: New and Improved Modules<2>-Footnote-562219102
Ref: New and Improved Modules<2>-Footnote-572219167
Ref: New and Improved Modules<2>-Footnote-582219235
Ref: New and Improved Modules<2>-Footnote-592219303
Ref: New and Improved Modules<2>-Footnote-602219368
Ref: New and Improved Modules<2>-Footnote-612219433
Ref: New and Improved Modules<2>-Footnote-622219500
Ref: New and Improved Modules<2>-Footnote-632219568
Node: ast 模組2219636
Ref: whatsnew/2 6 the-ast-module2219741
Ref: 13522219741
Node: future_builtins 模組2222392
Ref: whatsnew/2 6 the-future-builtins-module2222548
Ref: 13532222548
Node: The json module JavaScript Object Notation2223642
Ref: whatsnew/2 6 the-json-module-javascript-object-notation2223830
Ref: 13552223830
Node: The plistlib module A Property-List Parser2224840
Ref: whatsnew/2 6 the-plistlib-module-a-property-list-parser2225025
Ref: 13562225025
Node: ctypes Enhancements2226396
Ref: whatsnew/2 6 ctypes-enhancements2226559
Ref: 13572226559
Ref: ctypes Enhancements-Footnote-12228326
Ref: ctypes Enhancements-Footnote-22228393
Node: Improved SSL Support2228457
Ref: whatsnew/2 6 improved-ssl-support2228569
Ref: 13582228569
Ref: Improved SSL Support-Footnote-12229507
Node: Deprecations and Removals2229540
Ref: whatsnew/2 6 deprecations-and-removals2229702
Ref: 13592229702
Ref: Deprecations and Removals-Footnote-12231562
Node: Build and C API Changes<8>2231604
Ref: whatsnew/2 6 build-and-c-api-changes2231760
Ref: 135b2231760
Ref: Build and C API Changes<8>-Footnote-12239278
Ref: Build and C API Changes<8>-Footnote-22239347
Ref: Build and C API Changes<8>-Footnote-32239402
Ref: Build and C API Changes<8>-Footnote-42239466
Ref: Build and C API Changes<8>-Footnote-52239533
Ref: Build and C API Changes<8>-Footnote-62239597
Ref: Build and C API Changes<8>-Footnote-72239661
Node: Port-Specific Changes Windows<2>2239728
Ref: whatsnew/2 6 port-specific-changes-windows2239865
Ref: 13622239865
Ref: Port-Specific Changes Windows<2>-Footnote-12242317
Ref: Port-Specific Changes Windows<2>-Footnote-22242383
Ref: Port-Specific Changes Windows<2>-Footnote-32242450
Node: Port-Specific Changes Mac OS X<2>2242514
Ref: whatsnew/2 6 port-specific-changes-mac-os-x2242686
Ref: 13672242686
Ref: Port-Specific Changes Mac OS X<2>-Footnote-12243957
Node: Port-Specific Changes IRIX2244024
Ref: whatsnew/2 6 port-specific-changes-irix2244155
Ref: 13682244155
Node: Porting to Python 2 62244674
Ref: whatsnew/2 6 porting-to-python-2-62244814
Ref: 13692244814
Ref: Porting to Python 2 6-Footnote-12248622
Ref: Porting to Python 2 6-Footnote-22248689
Ref: Porting to Python 2 6-Footnote-32248756
Node: 致謝<2>2248823
Ref: whatsnew/2 6 acknowledgements2248928
Ref: 136b2248928
Ref: whatsnew/2 6 acks2248928
Ref: 136c2248928
Node: Python 2 5 有什麼新功能2249248
Ref: whatsnew/2 5 doc2249418
Ref: 136d2249418
Ref: whatsnew/2 5 what-s-new-in-python-2-52249418
Ref: 136e2249418
Ref: Python 2 5 有什麼新功能-Footnote-12252973
Node: PEP 308 Conditional Expressions2253015
Ref: whatsnew/2 5 pep-3082253157
Ref: 136f2253157
Ref: whatsnew/2 5 pep-308-conditional-expressions2253157
Ref: 13742253157
Ref: PEP 308 Conditional Expressions-Footnote-12256603
Ref: PEP 308 Conditional Expressions-Footnote-22256645
Node: PEP 309 Partial Function Application2256687
Ref: whatsnew/2 5 pep-3092256888
Ref: 13752256888
Ref: whatsnew/2 5 pep-309-partial-function-application2256888
Ref: 13762256888
Ref: PEP 309 Partial Function Application-Footnote-12259722
Node: PEP 314 Metadata for Python Software Packages v1 12259764
Ref: whatsnew/2 5 pep-3142259971
Ref: 13772259971
Ref: whatsnew/2 5 pep-314-metadata-for-python-software-packages-v1-12259971
Ref: 13782259971
Ref: PEP 314 Metadata for Python Software Packages v1 1-Footnote-12261800
Node: PEP 328 Absolute and Relative Imports2261842
Ref: whatsnew/2 5 pep-3282262049
Ref: 13722262049
Ref: whatsnew/2 5 pep-328-absolute-and-relative-imports2262049
Ref: 13792262049
Ref: PEP 328 Absolute and Relative Imports-Footnote-12265826
Ref: PEP 328 Absolute and Relative Imports-Footnote-22265868
Node: PEP 338 Executing Modules as Scripts2265910
Ref: whatsnew/2 5 pep-3382266101
Ref: 137a2266101
Ref: whatsnew/2 5 pep-338-executing-modules-as-scripts2266101
Ref: 137b2266101
Ref: PEP 338 Executing Modules as Scripts-Footnote-12266987
Node: PEP 341 Unified try/except/finally2267029
Ref: whatsnew/2 5 pep-3412267213
Ref: 13732267213
Ref: whatsnew/2 5 pep-341-unified-try-except-finally2267213
Ref: 137c2267213
Ref: PEP 341 Unified try/except/finally-Footnote-12268967
Node: PEP 342 New Generator Features2269009
Ref: whatsnew/2 5 pep-3422269183
Ref: 13712269183
Ref: whatsnew/2 5 pep-342-new-generator-features2269183
Ref: 137d2269183
Ref: PEP 342 New Generator Features-Footnote-12275795
Ref: PEP 342 New Generator Features-Footnote-22275837
Ref: PEP 342 New Generator Features-Footnote-32275879
Ref: PEP 342 New Generator Features-Footnote-42275921
Ref: PEP 342 New Generator Features-Footnote-52275963
Node: PEP 343：'with' 陳述式2276005
Ref: whatsnew/2 5 pep-3432276184
Ref: 13702276184
Ref: whatsnew/2 5 pep-343-the-with-statement2276184
Ref: 137e2276184
Node: Writing Context Managers<2>2279160
Ref: whatsnew/2 5 new-25-context-managers2279279
Ref: 137f2279279
Ref: whatsnew/2 5 writing-context-managers2279279
Ref: 13802279279
Node: contextlib 模組<2>2283632
Ref: whatsnew/2 5 contextlibmod2283751
Ref: 13812283751
Ref: whatsnew/2 5 the-contextlib-module2283751
Ref: 13822283751
Ref: contextlib 模組<2>-Footnote-12286189
Node: PEP 352 Exceptions as New-Style Classes2286231
Ref: whatsnew/2 5 pep-3522286419
Ref: 13832286419
Ref: whatsnew/2 5 pep-352-exceptions-as-new-style-classes2286419
Ref: 13842286419
Ref: PEP 352 Exceptions as New-Style Classes-Footnote-12288895
Node: PEP 353 Using ssize_t as the index type2288937
Ref: whatsnew/2 5 pep-3532289129
Ref: 13852289129
Ref: whatsnew/2 5 pep-353-using-ssize-t-as-the-index-type2289129
Ref: 13862289129
Ref: PEP 353 Using ssize_t as the index type-Footnote-12292000
Ref: PEP 353 Using ssize_t as the index type-Footnote-22292042
Node: PEP 357 The '__index__' method2292084
Ref: whatsnew/2 5 pep-3572292259
Ref: 13882292259
Ref: whatsnew/2 5 pep-357-the-index-method2292259
Ref: 13892292259
Ref: PEP 357 The '__index__' method-Footnote-12293953
Node: 其他語言更動<15>2293995
Ref: whatsnew/2 5 other-lang2294163
Ref: 138c2294163
Ref: whatsnew/2 5 other-language-changes2294163
Ref: 138d2294163
Ref: 其他語言更動<15>-Footnote-12301080
Node: Interactive Interpreter Changes2301122
Ref: whatsnew/2 5 interactive2301234
Ref: 13932301234
Ref: whatsnew/2 5 interactive-interpreter-changes2301234
Ref: 13942301234
Node: 最佳化<14>2302011
Ref: whatsnew/2 5 optimizations2302123
Ref: 13962302123
Ref: whatsnew/2 5 opts2302123
Ref: 13972302123
Node: New Improved and Removed Modules2305906
Ref: whatsnew/2 5 modules2306070
Ref: 13982306070
Ref: whatsnew/2 5 new-improved-and-removed-modules2306070
Ref: 13992306070
Ref: New Improved and Removed Modules-Footnote-12330497
Ref: New Improved and Removed Modules-Footnote-22330539
Ref: New Improved and Removed Modules-Footnote-32330598
Node: ctypes 套件2330657
Ref: whatsnew/2 5 module-ctypes2330766
Ref: 13a32330766
Ref: whatsnew/2 5 the-ctypes-package2330766
Ref: 13a42330766
Node: ElementTree 套件2334003
Ref: whatsnew/2 5 module-etree2334135
Ref: 13a62334135
Ref: whatsnew/2 5 the-elementtree-package2334135
Ref: 13a72334135
Node: hashlib 套件2339400
Ref: whatsnew/2 5 module-hashlib2339533
Ref: 13a82339533
Ref: whatsnew/2 5 the-hashlib-package2339533
Ref: 13a92339533
Node: sqlite3 套件2341088
Ref: whatsnew/2 5 module-sqlite2341217
Ref: 13aa2341217
Ref: whatsnew/2 5 the-sqlite3-package2341217
Ref: 13ab2341217
Ref: sqlite3 套件-Footnote-12345182
Ref: sqlite3 套件-Footnote-22345224
Node: wsgiref 套件2345266
Ref: whatsnew/2 5 module-wsgiref2345372
Ref: 13ac2345372
Ref: whatsnew/2 5 the-wsgiref-package2345372
Ref: 13ad2345372
Ref: wsgiref 套件-Footnote-12346342
Ref: wsgiref 套件-Footnote-22346384
Node: Build and C API Changes<9>2346426
Ref: whatsnew/2 5 build-and-c-api-changes2346589
Ref: 13ae2346589
Ref: whatsnew/2 5 build-api2346589
Ref: 13af2346589
Ref: Build and C API Changes<9>-Footnote-12353594
Ref: Build and C API Changes<9>-Footnote-22353636
Ref: Build and C API Changes<9>-Footnote-32353678
Node: Port-Specific Changes2353720
Ref: whatsnew/2 5 port-specific-changes2353804
Ref: 13b92353804
Ref: whatsnew/2 5 ports2353804
Ref: 13ba2353804
Ref: Port-Specific Changes-Footnote-12354481
Node: Porting to Python 2 52354545
Ref: whatsnew/2 5 porting2354685
Ref: 13bb2354685
Ref: whatsnew/2 5 porting-to-python-2-52354685
Ref: 13bc2354685
Ref: Porting to Python 2 5-Footnote-12357498
Node: 致謝<3>2357540
Ref: whatsnew/2 5 acknowledgements2357645
Ref: 13bd2357645
Node: Python 2 4 有什麼新功能2358117
Ref: whatsnew/2 4 doc2358287
Ref: 13be2358287
Ref: whatsnew/2 4 what-s-new-in-python-2-42358287
Ref: 13bf2358287
Node: PEP 218 Built-In Set Objects2360362
Ref: whatsnew/2 4 pep-218-built-in-set-objects2360508
Ref: 13c02360508
Ref: PEP 218 Built-In Set Objects-Footnote-12362743
Node: PEP 237 Unifying Long Integers and Integers2362785
Ref: whatsnew/2 4 pep-237-unifying-long-integers-and-integers2362969
Ref: 13c12362969
Ref: PEP 237 Unifying Long Integers and Integers-Footnote-12364007
Node: PEP 289 Generator Expressions2364049
Ref: whatsnew/2 4 pep-289-generator-expressions2364241
Ref: 13c22364241
Ref: PEP 289 Generator Expressions-Footnote-12366504
Node: PEP 292 Simpler String Substitutions2366546
Ref: whatsnew/2 4 pep-292-simpler-string-substitutions2366739
Ref: 13c32366739
Ref: PEP 292 Simpler String Substitutions-Footnote-12368523
Node: PEP 318 Decorators for Functions and Methods2368565
Ref: whatsnew/2 4 pep-318-decorators-for-functions-and-methods2368754
Ref: 13c42368754
Ref: PEP 318 Decorators for Functions and Methods-Footnote-12373254
Ref: PEP 318 Decorators for Functions and Methods-Footnote-22373296
Node: PEP 322 Reverse Iteration2373338
Ref: whatsnew/2 4 pep-322-reverse-iteration2373520
Ref: 13c62373520
Ref: PEP 322 Reverse Iteration-Footnote-12374481
Node: PEP 324 New subprocess Module2374523
Ref: whatsnew/2 4 pep-324-new-subprocess-module2374686
Ref: 13c72374686
Ref: PEP 324 New subprocess Module-Footnote-12378448
Node: PEP 327 Decimal Data Type2378490
Ref: whatsnew/2 4 pep-327-decimal-data-type2378654
Ref: 13c92378654
Node: Why is Decimal needed?2379220
Ref: whatsnew/2 4 why-is-decimal-needed2379327
Ref: 13ca2379327
Node: Decimal 型別2381895
Ref: whatsnew/2 4 the-decimal-type2382025
Ref: 13cb2382025
Node: Context 型別2385179
Ref: whatsnew/2 4 the-context-type2385278
Ref: 13cc2385278
Ref: Context 型別-Footnote-12387878
Node: PEP 328 Multi-line Imports2387920
Ref: whatsnew/2 4 pep-328-multi-line-imports2388106
Ref: 13cd2388106
Ref: PEP 328 Multi-line Imports-Footnote-12389599
Node: PEP 331 Locale-Independent Float/String Conversions2389641
Ref: whatsnew/2 4 pep-331-locale-independent-float-string-conversions2389824
Ref: 13ce2389824
Ref: PEP 331 Locale-Independent Float/String Conversions-Footnote-12391545
Node: 其他語言更動<16>2391587
Ref: whatsnew/2 4 other-language-changes2391782
Ref: 13cf2391782
Ref: 其他語言更動<16>-Footnote-12398754
Ref: 其他語言更動<16>-Footnote-22398796
Ref: 其他語言更動<16>-Footnote-32398838
Ref: 其他語言更動<16>-Footnote-42398880
Ref: 其他語言更動<16>-Footnote-52398922
Ref: 其他語言更動<16>-Footnote-62398964
Node: 最佳化<15>2399006
Ref: whatsnew/2 4 optimizations2399078
Ref: 13d12399078
Node: New Improved and Deprecated Modules<3>2401807
Ref: whatsnew/2 4 new-improved-and-deprecated-modules2401978
Ref: 13d22401978
Ref: New Improved and Deprecated Modules<3>-Footnote-12419263
Node: cookielib2419322
Ref: whatsnew/2 4 cookielib2419425
Ref: 13d62419425
Node: doctest<5>2420362
Ref: whatsnew/2 4 doctest2420465
Ref: 13d72420465
Node: Build and C API Changes<10>2423199
Ref: whatsnew/2 4 build-and-c-api-changes2423369
Ref: 13dd2423369
Node: Port-Specific Changes<2>2425981
Ref: whatsnew/2 4 port-specific-changes2426069
Ref: 13e32426069
Node: Porting to Python 2 42426248
Ref: whatsnew/2 4 porting-to-python-2-42426389
Ref: 13e42426389
Node: 致謝<4>2428357
Ref: whatsnew/2 4 acknowledgements2428462
Ref: 13e62428462
Ref: whatsnew/2 4 acks2428462
Ref: 13e72428462
Node: Python 2 3 有什麼新功能2428773
Ref: whatsnew/2 3 doc2428943
Ref: 13e82428943
Ref: whatsnew/2 3 what-s-new-in-python-2-32428943
Ref: 13e92428943
Node: PEP 218 A Standard Set Datatype2431938
Ref: whatsnew/2 3 pep-218-a-standard-set-datatype2432069
Ref: 13eb2432069
Ref: PEP 218 A Standard Set Datatype-Footnote-12434578
Node: PEP 255 Simple Generators2434620
Ref: whatsnew/2 3 pep-255-simple-generators2434789
Ref: 13f02434789
Ref: whatsnew/2 3 section-generators2434789
Ref: 13f12434789
Ref: PEP 255 Simple Generators-Footnote-12440924
Ref: PEP 255 Simple Generators-Footnote-22440966
Node: PEP 263 Source Code Encodings2441008
Ref: whatsnew/2 3 pep-263-source-code-encodings2441189
Ref: 13f22441189
Ref: whatsnew/2 3 section-encodings2441189
Ref: 13f32441189
Ref: PEP 263 Source Code Encodings-Footnote-12442398
Node: PEP 273 Importing Modules from ZIP Archives2442440
Ref: whatsnew/2 3 pep-273-importing-modules-from-zip-archives2442644
Ref: 13f42442644
Ref: PEP 273 Importing Modules from ZIP Archives-Footnote-12444671
Ref: PEP 273 Importing Modules from ZIP Archives-Footnote-22444713
Ref: PEP 273 Importing Modules from ZIP Archives-Footnote-32444755
Node: PEP 277 Unicode file name support for Windows NT2444797
Ref: whatsnew/2 3 pep-277-unicode-file-name-support-for-windows-nt2445005
Ref: 13f62445005
Ref: PEP 277 Unicode file name support for Windows NT-Footnote-12446486
Node: PEP 278 Universal Newline Support2446528
Ref: whatsnew/2 3 pep-278-universal-newline-support2446712
Ref: 13f82446712
Ref: PEP 278 Universal Newline Support-Footnote-12448216
Node: PEP 279：enumerate2448258
Ref: whatsnew/2 3 pep-279-enumerate2448421
Ref: 13f92448421
Ref: whatsnew/2 3 section-enumerate2448421
Ref: 13fa2448421
Ref: PEP 279：enumerate-Footnote-12449279
Node: PEP 282 The logging Package2449321
Ref: whatsnew/2 3 pep-282-the-logging-package2449473
Ref: 13fb2449473
Ref: PEP 282 The logging Package-Footnote-12454250
Ref: PEP 282 The logging Package-Footnote-22454292
Node: PEP 285 A Boolean Type2454334
Ref: whatsnew/2 3 pep-285-a-boolean-type2454505
Ref: 14012454505
Ref: whatsnew/2 3 section-bool2454505
Ref: 14022454505
Ref: PEP 285 A Boolean Type-Footnote-12456943
Ref: PEP 285 A Boolean Type-Footnote-22456985
Node: PEP 293 Codec Error Handling Callbacks2457027
Ref: whatsnew/2 3 pep-293-codec-error-handling-callbacks2457219
Ref: 14032457219
Ref: PEP 293 Codec Error Handling Callbacks-Footnote-12458747
Node: PEP 301 Package Index and Metadata for Distutils2458789
Ref: whatsnew/2 3 pep-301-package-index-and-metadata-for-distutils2458983
Ref: 14062458983
Ref: whatsnew/2 3 section-pep3012458983
Ref: 14072458983
Ref: PEP 301 Package Index and Metadata for Distutils-Footnote-12460624
Ref: PEP 301 Package Index and Metadata for Distutils-Footnote-22460660
Node: PEP 302 New Import Hooks2460702
Ref: whatsnew/2 3 pep-302-new-import-hooks2460887
Ref: 14082460887
Ref: whatsnew/2 3 section-pep3022460887
Ref: 13f52460887
Ref: PEP 302 New Import Hooks-Footnote-12463483
Ref: PEP 302 New Import Hooks-Footnote-22463525
Ref: PEP 302 New Import Hooks-Footnote-32463567
Node: PEP 305 Comma-separated Files2463609
Ref: whatsnew/2 3 pep-305-comma-separated-files2463773
Ref: 14092463773
Ref: whatsnew/2 3 section-pep3052463773
Ref: 140a2463773
Ref: PEP 305 Comma-separated Files-Footnote-12465253
Node: PEP 307 Pickle Enhancements2465295
Ref: whatsnew/2 3 pep-307-pickle-enhancements2465450
Ref: 140b2465450
Ref: whatsnew/2 3 section-pep3072465450
Ref: 140c2465450
Ref: PEP 307 Pickle Enhancements-Footnote-12467414
Ref: PEP 307 Pickle Enhancements-Footnote-22467456
Ref: PEP 307 Pickle Enhancements-Footnote-32467498
Node: Extended Slices2467540
Ref: whatsnew/2 3 extended-slices2467688
Ref: 14112467688
Ref: whatsnew/2 3 section-slices2467688
Ref: 14122467688
Node: 其他語言更動<17>2471068
Ref: whatsnew/2 3 other-language-changes2471227
Ref: 14132471227
Ref: 其他語言更動<17>-Footnote-12478985
Node: String Changes2479058
Ref: whatsnew/2 3 string-changes2479153
Ref: 14192479153
Node: 最佳化<16>2481672
Ref: whatsnew/2 3 optimizations2481767
Ref: 141e2481767
Node: New Improved and Deprecated Modules<4>2483215
Ref: whatsnew/2 3 new-improved-and-deprecated-modules2483398
Ref: 14202483398
Ref: New Improved and Deprecated Modules<4>-Footnote-12508140
Node: Date/Time Type2508180
Ref: whatsnew/2 3 date-time-type2508297
Ref: 14382508297
Node: The optparse Module2510621
Ref: whatsnew/2 3 the-optparse-module2510738
Ref: 143b2510738
Node: Pymalloc A Specialized Object Allocator2512793
Ref: whatsnew/2 3 pymalloc-a-specialized-object-allocator2512981
Ref: 143e2512981
Ref: whatsnew/2 3 section-pymalloc2512981
Ref: 143f2512981
Node: Build and C API Changes<11>2516847
Ref: whatsnew/2 3 build-and-c-api-changes2517023
Ref: 14412517023
Node: Port-Specific Changes<3>2520420
Ref: whatsnew/2 3 port-specific-changes2520508
Ref: 14472520508
Node: Other Changes and Fixes<2>2521739
Ref: whatsnew/2 3 other-changes-and-fixes2521897
Ref: 14482521897
Ref: whatsnew/2 3 section-other2521897
Ref: 141f2521897
Node: Porting to Python 2 32524382
Ref: whatsnew/2 3 porting-to-python-2-32524522
Ref: 144b2524522
Node: 致謝<5>2527319
Ref: whatsnew/2 3 acknowledgements2527424
Ref: 144c2527424
Ref: whatsnew/2 3 acks2527424
Ref: 144d2527424
Node: Python 2 2 有什麼新功能2528023
Ref: whatsnew/2 2 doc2528193
Ref: 144e2528193
Ref: whatsnew/2 2 what-s-new-in-python-2-22528193
Ref: 144f2528193
Node: 簡介2528855
Ref: whatsnew/2 2 introduction2528975
Ref: 14502528975
Ref: 簡介-Footnote-12529927
Ref: 簡介-Footnote-22529976
Node: PEPs 252 and 253 Type and Class Changes2530025
Ref: whatsnew/2 2 peps-252-and-253-type-and-class-changes2530173
Ref: 14512530173
Node: Old and New Classes2533569
Ref: whatsnew/2 2 old-and-new-classes2533684
Ref: 14542533684
Ref: Old and New Classes-Footnote-12536072
Node: Descriptors2536114
Ref: whatsnew/2 2 descriptors2536275
Ref: 14552536275
Node: Multiple Inheritance The Diamond Rule2540117
Ref: whatsnew/2 2 multiple-inheritance-the-diamond-rule2540275
Ref: 14562540275
Ref: Multiple Inheritance The Diamond Rule-Footnote-12543144
Node: Attribute Access2543186
Ref: whatsnew/2 2 attribute-access2543345
Ref: 14572543345
Node: 相關連結2547129
Ref: whatsnew/2 2 related-links2547242
Ref: 14592547242
Ref: whatsnew/2 2 sect-rellinks2547242
Ref: 14532547242
Ref: 相關連結-Footnote-12548717
Ref: 相關連結-Footnote-22548759
Ref: 相關連結-Footnote-32548801
Ref: 相關連結-Footnote-42548843
Ref: 相關連結-Footnote-52548885
Node: PEP 234：疊代器2548927
Ref: whatsnew/2 2 pep-234-iterators2549097
Ref: 145b2549097
Ref: PEP 234：疊代器-Footnote-12553962
Node: PEP 255 Simple Generators<2>2554004
Ref: whatsnew/2 2 pep-255-simple-generators2554181
Ref: 145e2554181
Ref: PEP 255 Simple Generators<2>-Footnote-12560194
Ref: PEP 255 Simple Generators<2>-Footnote-22560236
Node: PEP 237 Unifying Long Integers and Integers<2>2560278
Ref: whatsnew/2 2 pep-237-unifying-long-integers-and-integers2560474
Ref: 145f2560474
Ref: PEP 237 Unifying Long Integers and Integers<2>-Footnote-12562184
Node: PEP 238 Changing the Division Operator2562226
Ref: whatsnew/2 2 pep-238-changing-the-division-operator2562408
Ref: 14602562408
Ref: PEP 238 Changing the Division Operator-Footnote-12566020
Ref: PEP 238 Changing the Division Operator-Footnote-22566062
Ref: PEP 238 Changing the Division Operator-Footnote-32566104
Node: Unicode 變更2566146
Ref: whatsnew/2 2 unicode-changes2566303
Ref: 14632566303
Ref: Unicode 變更-Footnote-12568897
Ref: Unicode 變更-Footnote-22568939
Node: PEP 227 Nested Scopes2568981
Ref: whatsnew/2 2 pep-227-nested-scopes2569127
Ref: 14642569127
Ref: PEP 227 Nested Scopes-Footnote-12573450
Node: New and Improved Modules<3>2573492
Ref: whatsnew/2 2 new-and-improved-modules2573651
Ref: 14652573651
Ref: New and Improved Modules<3>-Footnote-12580327
Ref: New and Improved Modules<3>-Footnote-22580386
Ref: New and Improved Modules<3>-Footnote-32580445
Ref: New and Improved Modules<3>-Footnote-42580504
Ref: New and Improved Modules<3>-Footnote-52580563
Node: 直譯器的變更與修正2580621
Ref: whatsnew/2 2 interpreter-changes-and-fixes2580780
Ref: 146a2580780
Node: 其他改動與修正2585543
Ref: whatsnew/2 2 other-changes-and-fixes2585684
Ref: 147c2585684
Ref: 其他改動與修正-Footnote-12592301
Node: 致謝<6>2592343
Ref: whatsnew/2 2 acknowledgements2592448
Ref: 147f2592448
Node: Python 2 1 有什麼新功能2593025
Ref: whatsnew/2 1 doc2593195
Ref: 14802593195
Ref: whatsnew/2 1 what-s-new-in-python-2-12593195
Ref: 14812593195
Node: 簡介<2>2594170
Ref: whatsnew/2 1 introduction2594278
Ref: 14822594278
Node: PEP 227 Nested Scopes<2>2595356
Ref: whatsnew/2 1 pep-227-nested-scopes2595502
Ref: 14832595502
Ref: PEP 227 Nested Scopes<2>-Footnote-12599847
Ref: PEP 227 Nested Scopes<2>-Footnote-22599889
Ref: PEP 227 Nested Scopes<2>-Footnote-32599931
Node: PEP 236 __future__ Directives2599973
Ref: whatsnew/2 1 pep-236-future-directives2600134
Ref: 14842600134
Ref: PEP 236 __future__ Directives-Footnote-12601368
Node: PEP 207 Rich Comparisons2601410
Ref: whatsnew/2 1 pep-207-rich-comparisons2601572
Ref: 14852601572
Ref: PEP 207 Rich Comparisons-Footnote-12604970
Ref: PEP 207 Rich Comparisons-Footnote-22605012
Node: PEP 230 Warning Framework2605054
Ref: whatsnew/2 1 pep-230-warning-framework2605211
Ref: 14872605211
Ref: PEP 230 Warning Framework-Footnote-12608473
Ref: PEP 230 Warning Framework-Footnote-22608515
Node: PEP 229 New Build System2608557
Ref: whatsnew/2 1 pep-229-new-build-system2608713
Ref: 14892608713
Ref: PEP 229 New Build System-Footnote-12610622
Node: PEP 205 Weak References2610664
Ref: whatsnew/2 1 pep-205-weak-references2610822
Ref: 148a2610822
Ref: PEP 205 Weak References-Footnote-12613917
Node: PEP 232 Function Attributes2613959
Ref: whatsnew/2 1 pep-232-function-attributes2614148
Ref: 148b2614148
Ref: PEP 232 Function Attributes-Footnote-12615655
Node: PEP 235 Importing Modules on Case-Insensitive Platforms2615697
Ref: whatsnew/2 1 pep-235-importing-modules-on-case-insensitive-platforms2615895
Ref: 148c2615895
Node: PEP 217 Interactive Display Hook2616792
Ref: whatsnew/2 1 pep-217-interactive-display-hook2616989
Ref: 148d2616989
Ref: PEP 217 Interactive Display Hook-Footnote-12617917
Node: PEP 208 New Coercion Model2617959
Ref: whatsnew/2 1 pep-208-new-coercion-model2618136
Ref: 148f2618136
Ref: PEP 208 New Coercion Model-Footnote-12619751
Node: PEP 241 Metadata in Python Packages2619793
Ref: whatsnew/2 1 pep-241-metadata-in-python-packages2619965
Ref: 14902619965
Ref: PEP 241 Metadata in Python Packages-Footnote-12622073
Ref: PEP 241 Metadata in Python Packages-Footnote-22622155
Ref: PEP 241 Metadata in Python Packages-Footnote-32622197
Ref: PEP 241 Metadata in Python Packages-Footnote-42622239
Ref: PEP 241 Metadata in Python Packages-Footnote-52622281
Node: New and Improved Modules<4>2622323
Ref: whatsnew/2 1 new-and-improved-modules2622495
Ref: 14912622495
Node: Other Changes and Fixes<3>2628338
Ref: whatsnew/2 1 other-changes-and-fixes2628484
Ref: 14922628484
Node: 致謝<7>2634413
Ref: whatsnew/2 1 acknowledgements2634523
Ref: 14962634523
Node: Python 2 0 有什麼新功能2634792
Ref: whatsnew/2 0 doc2634960
Ref: 14972634960
Ref: whatsnew/2 0 what-s-new-in-python-2-02634960
Ref: 14982634960
Node: 簡介<3>2635640
Ref: whatsnew/2 0 introduction2635746
Ref: 14992635746
Node: What About Python 1 6?2636612
Ref: whatsnew/2 0 what-about-python-1-62636750
Ref: 149a2636750
Node: New Development Process2637985
Ref: whatsnew/2 0 new-development-process2638124
Ref: 149b2638124
Ref: New Development Process-Footnote-12643234
Ref: New Development Process-Footnote-22643276
Ref: New Development Process-Footnote-32643318
Node: Unicode<2>2643360
Ref: whatsnew/2 0 unicode2643519
Ref: 149c2643519
Ref: Unicode<2>-Footnote-12649656
Node: 串列綜合運算（List Comprehension）2649698
Ref: whatsnew/2 0 list-comprehensions2649854
Ref: 149d2649854
Node: Augmented Assignment2653613
Ref: whatsnew/2 0 augmented-assignment2653773
Ref: 149e2653773
Node: String Methods2655303
Ref: whatsnew/2 0 string-methods2655449
Ref: 149f2655449
Node: Garbage Collection of Cycles2657298
Ref: whatsnew/2 0 garbage-collection-of-cycles2657442
Ref: 14a02657442
Node: Other Core Changes2660769
Ref: whatsnew/2 0 other-core-changes2660913
Ref: 14a12660913
Node: Minor Language Changes2661194
Ref: whatsnew/2 0 minor-language-changes2661309
Ref: 14a22661309
Node: Changes to Built-in Functions2666362
Ref: whatsnew/2 0 changes-to-built-in-functions2666477
Ref: 14a52666477
Node: Porting to 2 02668755
Ref: whatsnew/2 0 porting-to-2-02668898
Ref: 14a62668898
Node: Extending/Embedding Changes2674188
Ref: whatsnew/2 0 extending-embedding-changes2674353
Ref: 14a92674353
Node: Distutils Making Modules Easy to Install2678175
Ref: whatsnew/2 0 distutils-making-modules-easy-to-install2678336
Ref: 14ae2678336
Node: XML 模組2681664
Ref: whatsnew/2 0 xml-modules2681810
Ref: 14af2681810
Node: SAX2 支援2682701
Ref: whatsnew/2 0 sax2-support2682778
Ref: 14b02682778
Node: DOM 支援2684430
Ref: whatsnew/2 0 dom-support2684537
Ref: 14b42684537
Node: Relationship to PyXML2687359
Ref: whatsnew/2 0 relationship-to-pyxml2687446
Ref: 14b52687446
Node: 模組變更2688726
Ref: whatsnew/2 0 module-changes2688847
Ref: 14b62688847
Node: 新增模組<5>2691315
Ref: whatsnew/2 0 new-modules2691443
Ref: 14b72691443
Node: IDLE Improvements2695432
Ref: whatsnew/2 0 idle-improvements2695578
Ref: 14b82695578
Node: Deleted and Deprecated Modules2696701
Ref: whatsnew/2 0 deleted-and-deprecated-modules2696841
Ref: 14b92696841
Node: 致謝<8>2697585
Ref: whatsnew/2 0 acknowledgements2697699
Ref: 14ba2697699
Ref: 致謝<8>-Footnote-12698259
Ref: 致謝<8>-Footnote-22698323
Node: Changelog（更動日誌）2698363
Ref: whatsnew/changelog doc2698493
Ref: 14bb2698493
Ref: whatsnew/changelog changelog2698493
Ref: 1222698493
Ref: whatsnew/changelog id12698493
Ref: 14bc2698493
Node: Python next2703932
Ref: whatsnew/changelog python-next2704049
Ref: 14bd2704049
Node: Core and Builtins2704148
Ref: whatsnew/changelog core-and-builtins2704213
Ref: 14be2704213
Ref: Core and Builtins-Footnote-12704456
Node: Python 3 13 0 release candidate 22704512
Ref: whatsnew/changelog python-3-13-0-release-candidate-22704671
Ref: 14bf2704671
Node: macOS2704945
Ref: whatsnew/changelog macos2705036
Ref: 14c02705036
Ref: macOS-Footnote-12705176
Node: Windows2705232
Ref: whatsnew/changelog windows2705343
Ref: 14c12705343
Ref: Windows-Footnote-12705798
Ref: Windows-Footnote-22705854
Ref: Windows-Footnote-32705910
Ref: Windows-Footnote-42705966
Node: Tools/Demos2706021
Ref: whatsnew/changelog tools-demos2706132
Ref: 14c22706132
Ref: Tools/Demos-Footnote-12706336
Node: Tests2706392
Ref: whatsnew/changelog tests2706504
Ref: 14c32706504
Ref: Tests-Footnote-12706805
Ref: Tests-Footnote-22706861
Node: Security2706917
Ref: whatsnew/changelog security2707025
Ref: 14c42707025
Ref: Security-Footnote-12707268
Ref: Security-Footnote-22707324
Node: Library2707380
Ref: whatsnew/changelog library2707490
Ref: 14c52707490
Ref: Library-Footnote-12712551
Ref: Library-Footnote-22712607
Ref: Library-Footnote-32712663
Ref: Library-Footnote-42712719
Ref: Library-Footnote-52712790
Ref: Library-Footnote-62712846
Ref: Library-Footnote-72712902
Ref: Library-Footnote-82712958
Ref: Library-Footnote-92713014
Ref: Library-Footnote-102713070
Ref: Library-Footnote-112713127
Ref: Library-Footnote-122713184
Ref: Library-Footnote-132713240
Ref: Library-Footnote-142713297
Ref: Library-Footnote-152713354
Ref: Library-Footnote-162713411
Ref: Library-Footnote-172713468
Ref: Library-Footnote-182713525
Ref: Library-Footnote-192713582
Ref: Library-Footnote-202713639
Ref: Library-Footnote-212713696
Ref: Library-Footnote-222713753
Ref: Library-Footnote-232713810
Ref: Library-Footnote-242713867
Ref: Library-Footnote-252713923
Ref: Library-Footnote-262713980
Ref: Library-Footnote-272714036
Ref: Library-Footnote-282714093
Ref: Library-Footnote-292714150
Ref: Library-Footnote-302714207
Ref: Library-Footnote-312714264
Ref: Library-Footnote-322714321
Ref: Library-Footnote-332714378
Ref: Library-Footnote-342714435
Node: IDLE<3>2714492
Ref: whatsnew/changelog idle2714614
Ref: 14d12714614
Ref: IDLE<3>-Footnote-12714862
Node: Core and Builtins<2>2714918
Ref: whatsnew/changelog id22715038
Ref: 14d22715038
Ref: Core and Builtins<2>-Footnote-12718701
Ref: Core and Builtins<2>-Footnote-22718757
Ref: Core and Builtins<2>-Footnote-32718813
Ref: Core and Builtins<2>-Footnote-42718869
Ref: Core and Builtins<2>-Footnote-52718925
Ref: Core and Builtins<2>-Footnote-62718981
Ref: Core and Builtins<2>-Footnote-72719037
Ref: Core and Builtins<2>-Footnote-82719093
Ref: Core and Builtins<2>-Footnote-92719149
Ref: Core and Builtins<2>-Footnote-102719205
Ref: Core and Builtins<2>-Footnote-112719262
Ref: Core and Builtins<2>-Footnote-122719319
Ref: Core and Builtins<2>-Footnote-132719376
Ref: Core and Builtins<2>-Footnote-142719433
Ref: Core and Builtins<2>-Footnote-152719490
Ref: Core and Builtins<2>-Footnote-162719547
Ref: Core and Builtins<2>-Footnote-172719604
Ref: Core and Builtins<2>-Footnote-182719661
Ref: Core and Builtins<2>-Footnote-192719718
Ref: Core and Builtins<2>-Footnote-202719775
Ref: Core and Builtins<2>-Footnote-212719832
Ref: Core and Builtins<2>-Footnote-222719889
Ref: Core and Builtins<2>-Footnote-232719946
Ref: Core and Builtins<2>-Footnote-242720003
Ref: Core and Builtins<2>-Footnote-252720060
Ref: Core and Builtins<2>-Footnote-262720116
Ref: Core and Builtins<2>-Footnote-272720172
Node: C API2720229
Ref: whatsnew/changelog c-api2720347
Ref: 14d42720347
Ref: C API-Footnote-12720577
Node: Build2720633
Ref: whatsnew/changelog build2720722
Ref: 14d52720722
Ref: Build-Footnote-12721615
Ref: Build-Footnote-22721671
Ref: Build-Footnote-32721727
Ref: Build-Footnote-42721783
Ref: Build-Footnote-52721839
Node: Python 3 13 0 release candidate 12721895
Ref: whatsnew/changelog python-3-13-0-release-candidate-12722063
Ref: 14d62722063
Node: Tests<2>2722349
Ref: whatsnew/changelog id32722447
Ref: 14d72722447
Ref: Tests<2>-Footnote-12722857
Ref: Tests<2>-Footnote-22722912
Node: Security<2>2722967
Ref: whatsnew/changelog id42723084
Ref: 14da2723084
Ref: Security<2>-Footnote-12723726
Ref: Security<2>-Footnote-22723782
Node: Library<2>2723838
Ref: whatsnew/changelog id52723954
Ref: 14db2723954
Ref: Library<2>-Footnote-12725959
Ref: Library<2>-Footnote-22726015
Ref: Library<2>-Footnote-32726071
Ref: Library<2>-Footnote-42726127
Ref: Library<2>-Footnote-52726183
Ref: Library<2>-Footnote-62726239
Ref: Library<2>-Footnote-72726295
Ref: Library<2>-Footnote-82726350
Ref: Library<2>-Footnote-92726406
Ref: Library<2>-Footnote-102726462
Ref: Library<2>-Footnote-112726519
Ref: Library<2>-Footnote-122726575
Ref: Library<2>-Footnote-132726632
Node: IDLE<4>2726689
Ref: whatsnew/changelog id62726814
Ref: 14e02726814
Ref: IDLE<4>-Footnote-12727024
Node: Core and Builtins<3>2727080
Ref: whatsnew/changelog id72727203
Ref: 14e12727203
Ref: Core and Builtins<3>-Footnote-12728230
Ref: Core and Builtins<3>-Footnote-22728286
Ref: Core and Builtins<3>-Footnote-32728342
Ref: Core and Builtins<3>-Footnote-42728398
Ref: Core and Builtins<3>-Footnote-52728454
Ref: Core and Builtins<3>-Footnote-62728510
Ref: Core and Builtins<3>-Footnote-72728566
Node: C API<2>2728622
Ref: whatsnew/changelog id82728746
Ref: 14e32728746
Ref: C API<2>-Footnote-12729071
Ref: C API<2>-Footnote-22729127
Node: Build<2>2729183
Ref: whatsnew/changelog id92729278
Ref: 14e52729278
Ref: Build<2>-Footnote-12729499
Node: Python 3 13 0 beta 42729555
Ref: whatsnew/changelog python-3-13-0-beta-42729710
Ref: 14e72729710
Node: Tests<3>2729963
Ref: whatsnew/changelog id102730047
Ref: 14e82730047
Ref: Tests<3>-Footnote-12730938
Ref: Tests<3>-Footnote-22730994
Ref: Tests<3>-Footnote-32731050
Ref: Tests<3>-Footnote-42731106
Node: Library<3>2731162
Ref: whatsnew/changelog id112731262
Ref: 14ea2731262
Ref: Library<3>-Footnote-12733736
Ref: Library<3>-Footnote-22733791
Ref: Library<3>-Footnote-32733847
Ref: Library<3>-Footnote-42733903
Ref: Library<3>-Footnote-52733959
Ref: Library<3>-Footnote-62734015
Ref: Library<3>-Footnote-72734070
Ref: Library<3>-Footnote-82734126
Ref: Library<3>-Footnote-92734182
Ref: Library<3>-Footnote-102734238
Ref: Library<3>-Footnote-112734295
Ref: Library<3>-Footnote-122734352
Ref: Library<3>-Footnote-132734409
Ref: Library<3>-Footnote-142734466
Node: IDLE<5>2734523
Ref: whatsnew/changelog id122734628
Ref: 14ec2734628
Ref: IDLE<5>-Footnote-12734826
Node: Documentation2734881
Ref: whatsnew/changelog documentation2734996
Ref: 14ed2734996
Ref: Documentation-Footnote-12735364
Ref: Documentation-Footnote-22735420
Node: Core and Builtins<4>2735476
Ref: whatsnew/changelog id132735592
Ref: 14f02735592
Ref: Core and Builtins<4>-Footnote-12737583
Ref: Core and Builtins<4>-Footnote-22737639
Ref: Core and Builtins<4>-Footnote-32737695
Ref: Core and Builtins<4>-Footnote-42737751
Ref: Core and Builtins<4>-Footnote-52737807
Ref: Core and Builtins<4>-Footnote-62737863
Ref: Core and Builtins<4>-Footnote-72737919
Ref: Core and Builtins<4>-Footnote-82737975
Ref: Core and Builtins<4>-Footnote-92738031
Ref: Core and Builtins<4>-Footnote-102738087
Ref: Core and Builtins<4>-Footnote-112738144
Ref: Core and Builtins<4>-Footnote-122738201
Ref: Core and Builtins<4>-Footnote-132738258
Ref: Core and Builtins<4>-Footnote-142738315
Node: C API<3>2738372
Ref: whatsnew/changelog id142738483
Ref: 14f12738483
Ref: C API<3>-Footnote-12739677
Ref: C API<3>-Footnote-22739732
Ref: C API<3>-Footnote-32739788
Ref: C API<3>-Footnote-42739844
Node: Build<3>2739900
Ref: whatsnew/changelog id152739982
Ref: 14f62739982
Ref: Build<3>-Footnote-12740828
Ref: Build<3>-Footnote-22740884
Ref: Build<3>-Footnote-32740940
Ref: Build<3>-Footnote-42740996
Ref: Build<3>-Footnote-52741052
Ref: Build<3>-Footnote-62741108
Ref: Build<3>-Footnote-72741164
Node: Python 3 13 0 beta 32741220
Ref: whatsnew/changelog python-3-13-0-beta-32741362
Ref: 14f72741362
Node: Core and Builtins<5>2741561
Ref: whatsnew/changelog id162741657
Ref: 14f82741657
Ref: Core and Builtins<5>-Footnote-12745032
Ref: Core and Builtins<5>-Footnote-22745088
Ref: Core and Builtins<5>-Footnote-32745144
Ref: Core and Builtins<5>-Footnote-42745200
Ref: Core and Builtins<5>-Footnote-52745256
Ref: Core and Builtins<5>-Footnote-62745312
Ref: Core and Builtins<5>-Footnote-72745368
Ref: Core and Builtins<5>-Footnote-82745424
Ref: Core and Builtins<5>-Footnote-92745480
Ref: Core and Builtins<5>-Footnote-102745536
Ref: Core and Builtins<5>-Footnote-112745593
Ref: Core and Builtins<5>-Footnote-122745650
Ref: Core and Builtins<5>-Footnote-132745707
Ref: Core and Builtins<5>-Footnote-142745764
Ref: Core and Builtins<5>-Footnote-152745821
Ref: Core and Builtins<5>-Footnote-162745877
Ref: Core and Builtins<5>-Footnote-172745934
Ref: Core and Builtins<5>-Footnote-182745991
Ref: Core and Builtins<5>-Footnote-192746048
Ref: Core and Builtins<5>-Footnote-202746105
Ref: Core and Builtins<5>-Footnote-212746162
Node: Library<4>2746228
Ref: whatsnew/changelog id172746341
Ref: 14f92746341
Ref: Library<4>-Footnote-12751845
Ref: Library<4>-Footnote-22751901
Ref: Library<4>-Footnote-32751957
Ref: Library<4>-Footnote-42752013
Ref: Library<4>-Footnote-52752069
Ref: Library<4>-Footnote-62752125
Ref: Library<4>-Footnote-72752181
Ref: Library<4>-Footnote-82752237
Ref: Library<4>-Footnote-92752293
Ref: Library<4>-Footnote-102752349
Ref: Library<4>-Footnote-112752406
Ref: Library<4>-Footnote-122752463
Ref: Library<4>-Footnote-132752520
Ref: Library<4>-Footnote-142752577
Ref: Library<4>-Footnote-152752634
Ref: Library<4>-Footnote-162752691
Ref: Library<4>-Footnote-172752747
Ref: Library<4>-Footnote-182752804
Ref: Library<4>-Footnote-192752861
Ref: Library<4>-Footnote-202752918
Ref: Library<4>-Footnote-212752975
Ref: Library<4>-Footnote-222753018
Ref: Library<4>-Footnote-232753075
Ref: Library<4>-Footnote-242753132
Ref: Library<4>-Footnote-252753189
Ref: Library<4>-Footnote-262753245
Ref: Library<4>-Footnote-272753302
Ref: Library<4>-Footnote-282753359
Ref: Library<4>-Footnote-292753416
Ref: Library<4>-Footnote-302753473
Ref: Library<4>-Footnote-312753530
Ref: Library<4>-Footnote-322753587
Ref: Library<4>-Footnote-332753643
Ref: Library<4>-Footnote-342753699
Ref: Library<4>-Footnote-352753756
Ref: Library<4>-Footnote-362753813
Node: Build<4>2753870
Ref: whatsnew/changelog id182753971
Ref: 15032753971
Ref: Build<4>-Footnote-12754513
Ref: Build<4>-Footnote-22754569
Ref: Build<4>-Footnote-32754625
Ref: Build<4>-Footnote-42754681
Node: C API<4>2754737
Ref: whatsnew/changelog id192754819
Ref: 15042754819
Ref: C API<4>-Footnote-12755994
Ref: C API<4>-Footnote-22756050
Ref: C API<4>-Footnote-32756106
Ref: C API<4>-Footnote-42756162
Ref: C API<4>-Footnote-52756218
Ref: C API<4>-Footnote-62756274
Node: Python 3 13 0 beta 22756330
Ref: whatsnew/changelog python-3-13-0-beta-22756472
Ref: 15072756472
Node: Security<3>2756738
Ref: whatsnew/changelog id202756835
Ref: 15082756835
Ref: Security<3>-Footnote-12757350
Ref: Security<3>-Footnote-22757406
Ref: Security<3>-Footnote-32757462
Node: Core and Builtins<6>2757531
Ref: whatsnew/changelog id212757647
Ref: 15092757647
Ref: Core and Builtins<6>-Footnote-12760442
Ref: Core and Builtins<6>-Footnote-22760498
Ref: Core and Builtins<6>-Footnote-32760554
Ref: Core and Builtins<6>-Footnote-42760610
Ref: Core and Builtins<6>-Footnote-52760666
Ref: Core and Builtins<6>-Footnote-62760722
Ref: Core and Builtins<6>-Footnote-72760778
Ref: Core and Builtins<6>-Footnote-82760834
Ref: Core and Builtins<6>-Footnote-92760890
Ref: Core and Builtins<6>-Footnote-102760946
Ref: Core and Builtins<6>-Footnote-112761003
Ref: Core and Builtins<6>-Footnote-122761060
Ref: Core and Builtins<6>-Footnote-132761117
Ref: Core and Builtins<6>-Footnote-142761174
Ref: Core and Builtins<6>-Footnote-152761231
Ref: Core and Builtins<6>-Footnote-162761288
Ref: Core and Builtins<6>-Footnote-172761345
Ref: Core and Builtins<6>-Footnote-182761402
Ref: Core and Builtins<6>-Footnote-192761459
Node: Library<5>2761516
Ref: whatsnew/changelog id222761629
Ref: 150a2761629
Ref: Library<5>-Footnote-12768226
Ref: Library<5>-Footnote-22768282
Ref: Library<5>-Footnote-32768338
Ref: Library<5>-Footnote-42768394
Ref: Library<5>-Footnote-52768450
Ref: Library<5>-Footnote-62768505
Ref: Library<5>-Footnote-72768560
Ref: Library<5>-Footnote-82768616
Ref: Library<5>-Footnote-92768671
Ref: Library<5>-Footnote-102768727
Ref: Library<5>-Footnote-112768784
Ref: Library<5>-Footnote-122768841
Ref: Library<5>-Footnote-132768898
Ref: Library<5>-Footnote-142768955
Ref: Library<5>-Footnote-152769012
Ref: Library<5>-Footnote-162769069
Ref: Library<5>-Footnote-172769126
Ref: Library<5>-Footnote-182769183
Ref: Library<5>-Footnote-192769240
Ref: Library<5>-Footnote-202769297
Ref: Library<5>-Footnote-212769354
Ref: Library<5>-Footnote-222769410
Ref: Library<5>-Footnote-232769467
Ref: Library<5>-Footnote-242769524
Ref: Library<5>-Footnote-252769581
Ref: Library<5>-Footnote-262769638
Ref: Library<5>-Footnote-272769695
Ref: Library<5>-Footnote-282769752
Ref: Library<5>-Footnote-292769809
Ref: Library<5>-Footnote-302769866
Ref: Library<5>-Footnote-312769923
Ref: Library<5>-Footnote-322769980
Ref: Library<5>-Footnote-332770037
Ref: Library<5>-Footnote-342770120
Ref: Library<5>-Footnote-352770177
Ref: Library<5>-Footnote-362770234
Ref: Library<5>-Footnote-372770290
Ref: Library<5>-Footnote-382770347
Ref: Library<5>-Footnote-392770403
Ref: Library<5>-Footnote-402770469
Node: Tests<4>2770525
Ref: whatsnew/changelog id232770626
Ref: 15112770626
Ref: Tests<4>-Footnote-12770818
Node: Build<5>2770874
Ref: whatsnew/changelog id242770975
Ref: 15122770975
Ref: Build<5>-Footnote-12772011
Ref: Build<5>-Footnote-22772067
Ref: Build<5>-Footnote-32772123
Ref: Build<5>-Footnote-42772179
Ref: Build<5>-Footnote-52772235
Node: Windows<2>2772291
Ref: whatsnew/changelog id252772392
Ref: 15132772392
Ref: Windows<2>-Footnote-12773325
Ref: Windows<2>-Footnote-22773381
Ref: Windows<2>-Footnote-32773437
Ref: Windows<2>-Footnote-42773493
Ref: Windows<2>-Footnote-52773549
Ref: Windows<2>-Footnote-62773605
Ref: Windows<2>-Footnote-72773661
Node: C API<5>2773717
Ref: whatsnew/changelog id262773801
Ref: 15142773801
Ref: C API<5>-Footnote-12775196
Ref: C API<5>-Footnote-22775252
Ref: C API<5>-Footnote-32775308
Ref: C API<5>-Footnote-42775364
Ref: C API<5>-Footnote-52775420
Ref: C API<5>-Footnote-62775476
Node: Python 3 13 0 beta 12775532
Ref: whatsnew/changelog python-3-13-0-beta-12775675
Ref: 15172775675
Node: Security<4>2775993
Ref: whatsnew/changelog id272776090
Ref: 15182776090
Ref: Security<4>-Footnote-12776483
Ref: Security<4>-Footnote-22776539
Node: Core and Builtins<7>2776595
Ref: whatsnew/changelog id282776711
Ref: 15192776711
Ref: Core and Builtins<7>-Footnote-12786076
Ref: Core and Builtins<7>-Footnote-22786132
Ref: Core and Builtins<7>-Footnote-32786188
Ref: Core and Builtins<7>-Footnote-42786244
Ref: Core and Builtins<7>-Footnote-52786299
Ref: Core and Builtins<7>-Footnote-62786355
Ref: Core and Builtins<7>-Footnote-72786411
Ref: Core and Builtins<7>-Footnote-82786467
Ref: Core and Builtins<7>-Footnote-92786523
Ref: Core and Builtins<7>-Footnote-102786579
Ref: Core and Builtins<7>-Footnote-112786636
Ref: Core and Builtins<7>-Footnote-122786693
Ref: Core and Builtins<7>-Footnote-132786750
Ref: Core and Builtins<7>-Footnote-142786807
Ref: Core and Builtins<7>-Footnote-152786864
Ref: Core and Builtins<7>-Footnote-162786920
Ref: Core and Builtins<7>-Footnote-172786977
Ref: Core and Builtins<7>-Footnote-182787034
Ref: Core and Builtins<7>-Footnote-192787091
Ref: Core and Builtins<7>-Footnote-202787148
Ref: Core and Builtins<7>-Footnote-212787205
Ref: Core and Builtins<7>-Footnote-222787262
Ref: Core and Builtins<7>-Footnote-232787319
Ref: Core and Builtins<7>-Footnote-242787376
Ref: Core and Builtins<7>-Footnote-252787433
Ref: Core and Builtins<7>-Footnote-262787490
Ref: Core and Builtins<7>-Footnote-272787547
Ref: Core and Builtins<7>-Footnote-282787604
Ref: Core and Builtins<7>-Footnote-292787661
Ref: Core and Builtins<7>-Footnote-302787718
Ref: Core and Builtins<7>-Footnote-312787775
Ref: Core and Builtins<7>-Footnote-322787832
Ref: Core and Builtins<7>-Footnote-332787889
Ref: Core and Builtins<7>-Footnote-342787946
Ref: Core and Builtins<7>-Footnote-352788003
Ref: Core and Builtins<7>-Footnote-362788060
Ref: Core and Builtins<7>-Footnote-372788117
Ref: Core and Builtins<7>-Footnote-382788160
Ref: Core and Builtins<7>-Footnote-392788217
Ref: Core and Builtins<7>-Footnote-402788274
Ref: Core and Builtins<7>-Footnote-412788331
Ref: Core and Builtins<7>-Footnote-422788388
Ref: Core and Builtins<7>-Footnote-432788445
Ref: Core and Builtins<7>-Footnote-442788488
Ref: Core and Builtins<7>-Footnote-452788544
Ref: Core and Builtins<7>-Footnote-462788601
Ref: Core and Builtins<7>-Footnote-472788657
Ref: Core and Builtins<7>-Footnote-482788713
Node: Library<6>2788770
Ref: whatsnew/changelog id292788891
Ref: 151c2788891
Ref: Library<6>-Footnote-12805148
Ref: Library<6>-Footnote-22805204
Ref: Library<6>-Footnote-32805260
Ref: Library<6>-Footnote-42805316
Ref: Library<6>-Footnote-52805372
Ref: Library<6>-Footnote-62805428
Ref: Library<6>-Footnote-72805484
Ref: Library<6>-Footnote-82805540
Ref: Library<6>-Footnote-92805596
Ref: Library<6>-Footnote-102805652
Ref: Library<6>-Footnote-112805709
Ref: Library<6>-Footnote-122805766
Ref: Library<6>-Footnote-132805823
Ref: Library<6>-Footnote-142805880
Ref: Library<6>-Footnote-152805923
Ref: Library<6>-Footnote-162805980
Ref: Library<6>-Footnote-172806037
Ref: Library<6>-Footnote-182806094
Ref: Library<6>-Footnote-192806151
Ref: Library<6>-Footnote-202806208
Ref: Library<6>-Footnote-212806265
Ref: Library<6>-Footnote-222806322
Ref: Library<6>-Footnote-232806379
Ref: Library<6>-Footnote-242806436
Ref: Library<6>-Footnote-252806492
Ref: Library<6>-Footnote-262806549
Ref: Library<6>-Footnote-272806606
Ref: Library<6>-Footnote-282806663
Ref: Library<6>-Footnote-292806720
Ref: Library<6>-Footnote-302806777
Ref: Library<6>-Footnote-312806834
Ref: Library<6>-Footnote-322806877
Ref: Library<6>-Footnote-332806934
Ref: Library<6>-Footnote-342806991
Ref: Library<6>-Footnote-352807048
Ref: Library<6>-Footnote-362807104
Ref: Library<6>-Footnote-372807164
Ref: Library<6>-Footnote-382807220
Ref: Library<6>-Footnote-392807277
Ref: Library<6>-Footnote-402807334
Ref: Library<6>-Footnote-412807391
Ref: Library<6>-Footnote-422807447
Ref: Library<6>-Footnote-432807503
Ref: Library<6>-Footnote-442807546
Ref: Library<6>-Footnote-452807603
Ref: Library<6>-Footnote-462807660
Ref: Library<6>-Footnote-472807717
Ref: Library<6>-Footnote-482807774
Ref: Library<6>-Footnote-492807831
Ref: Library<6>-Footnote-502807888
Ref: Library<6>-Footnote-512807945
Ref: Library<6>-Footnote-522808002
Ref: Library<6>-Footnote-532808059
Ref: Library<6>-Footnote-542808116
Ref: Library<6>-Footnote-552808173
Ref: Library<6>-Footnote-562808230
Ref: Library<6>-Footnote-572808287
Ref: Library<6>-Footnote-582808344
Ref: Library<6>-Footnote-592808401
Ref: Library<6>-Footnote-602808458
Ref: Library<6>-Footnote-612808515
Ref: Library<6>-Footnote-622808572
Ref: Library<6>-Footnote-632808615
Ref: Library<6>-Footnote-642808672
Ref: Library<6>-Footnote-652808729
Ref: Library<6>-Footnote-662808786
Ref: Library<6>-Footnote-672808843
Ref: Library<6>-Footnote-682808886
Ref: Library<6>-Footnote-692808942
Ref: Library<6>-Footnote-702808998
Ref: Library<6>-Footnote-712809055
Ref: Library<6>-Footnote-722809112
Ref: Library<6>-Footnote-732809169
Ref: Library<6>-Footnote-742809225
Ref: Library<6>-Footnote-752809281
Ref: Library<6>-Footnote-762809338
Ref: Library<6>-Footnote-772809395
Ref: Library<6>-Footnote-782809452
Ref: Library<6>-Footnote-792809509
Ref: Library<6>-Footnote-802809565
Ref: Library<6>-Footnote-812809622
Ref: Library<6>-Footnote-822809679
Ref: Library<6>-Footnote-832809735
Ref: Library<6>-Footnote-842809792
Ref: Library<6>-Footnote-852809849
Ref: Library<6>-Footnote-862809905
Ref: Library<6>-Footnote-872809961
Ref: Library<6>-Footnote-882810027
Ref: Library<6>-Footnote-892810093
Ref: Library<6>-Footnote-902810159
Ref: Library<6>-Footnote-912810225
Node: Documentation<2>2810291
Ref: whatsnew/changelog id302810400
Ref: 152b2810400
Ref: Documentation<2>-Footnote-12810580
Node: Build<6>2810636
Ref: whatsnew/changelog id312810745
Ref: 152c2810745
Ref: Build<6>-Footnote-12811692
Ref: Build<6>-Footnote-22811748
Ref: Build<6>-Footnote-32811804
Ref: Build<6>-Footnote-42811860
Ref: Build<6>-Footnote-52811916
Ref: Build<6>-Footnote-62811972
Node: Windows<3>2812028
Ref: whatsnew/changelog id322812129
Ref: 152d2812129
Ref: Windows<3>-Footnote-12813166
Ref: Windows<3>-Footnote-22813222
Ref: Windows<3>-Footnote-32813278
Ref: Windows<3>-Footnote-42813334
Ref: Windows<3>-Footnote-52813390
Ref: Windows<3>-Footnote-62813446
Ref: Windows<3>-Footnote-72813501
Node: macOS<2>2813557
Ref: whatsnew/changelog id332813657
Ref: 152e2813657
Ref: macOS<2>-Footnote-12814099
Ref: macOS<2>-Footnote-22814155
Ref: macOS<2>-Footnote-32814211
Ref: macOS<2>-Footnote-42814267
Node: IDLE<6>2814322
Ref: whatsnew/changelog id342814420
Ref: 152f2814420
Ref: IDLE<6>-Footnote-12814557
Node: C API<6>2814622
Ref: whatsnew/changelog id352814703
Ref: 15302814703
Ref: C API<6>-Footnote-12815963
Ref: C API<6>-Footnote-22816019
Ref: C API<6>-Footnote-32816075
Ref: C API<6>-Footnote-42816131
Ref: C API<6>-Footnote-52816187
Ref: C API<6>-Footnote-62816243
Ref: C API<6>-Footnote-72816298
Node: Python 3 13 0 alpha 62816354
Ref: whatsnew/changelog python-3-13-0-alpha-62816498
Ref: 15362816498
Node: Core and Builtins<8>2816776
Ref: whatsnew/changelog id362816873
Ref: 15372816873
Ref: Core and Builtins<8>-Footnote-12821940
Ref: Core and Builtins<8>-Footnote-22821996
Ref: Core and Builtins<8>-Footnote-32822052
Ref: Core and Builtins<8>-Footnote-42822108
Ref: Core and Builtins<8>-Footnote-52822164
Ref: Core and Builtins<8>-Footnote-62822220
Ref: Core and Builtins<8>-Footnote-72822276
Ref: Core and Builtins<8>-Footnote-82822332
Ref: Core and Builtins<8>-Footnote-92822387
Ref: Core and Builtins<8>-Footnote-102822434
Ref: Core and Builtins<8>-Footnote-112822491
Ref: Core and Builtins<8>-Footnote-122822548
Ref: Core and Builtins<8>-Footnote-132822605
Ref: Core and Builtins<8>-Footnote-142822662
Ref: Core and Builtins<8>-Footnote-152822719
Ref: Core and Builtins<8>-Footnote-162822776
Ref: Core and Builtins<8>-Footnote-172822833
Ref: Core and Builtins<8>-Footnote-182822890
Ref: Core and Builtins<8>-Footnote-192822947
Ref: Core and Builtins<8>-Footnote-202823004
Ref: Core and Builtins<8>-Footnote-212823061
Ref: Core and Builtins<8>-Footnote-222823117
Node: Library<7>2823183
Ref: whatsnew/changelog id372823305
Ref: 153b2823305
Ref: Library<7>-Footnote-12834067
Ref: Library<7>-Footnote-22834123
Ref: Library<7>-Footnote-32834179
Ref: Library<7>-Footnote-42834235
Ref: Library<7>-Footnote-52834291
Ref: Library<7>-Footnote-62834347
Ref: Library<7>-Footnote-72834403
Ref: Library<7>-Footnote-82834459
Ref: Library<7>-Footnote-92834515
Ref: Library<7>-Footnote-102834571
Ref: Library<7>-Footnote-112834628
Ref: Library<7>-Footnote-122834684
Ref: Library<7>-Footnote-132834740
Ref: Library<7>-Footnote-142834797
Ref: Library<7>-Footnote-152834854
Ref: Library<7>-Footnote-162834910
Ref: Library<7>-Footnote-172834967
Ref: Library<7>-Footnote-182835024
Ref: Library<7>-Footnote-192835081
Ref: Library<7>-Footnote-202835138
Ref: Library<7>-Footnote-212835195
Ref: Library<7>-Footnote-222835252
Ref: Library<7>-Footnote-232835309
Ref: Library<7>-Footnote-242835366
Ref: Library<7>-Footnote-252835423
Ref: Library<7>-Footnote-262835480
Ref: Library<7>-Footnote-272835536
Ref: Library<7>-Footnote-282835593
Ref: Library<7>-Footnote-292835650
Ref: Library<7>-Footnote-302835706
Ref: Library<7>-Footnote-312835763
Ref: Library<7>-Footnote-322835820
Ref: Library<7>-Footnote-332835876
Ref: Library<7>-Footnote-342835933
Ref: Library<7>-Footnote-352836001
Ref: Library<7>-Footnote-362836057
Ref: Library<7>-Footnote-372836114
Ref: Library<7>-Footnote-382836171
Ref: Library<7>-Footnote-392836228
Ref: Library<7>-Footnote-402836285
Ref: Library<7>-Footnote-412836341
Ref: Library<7>-Footnote-422836397
Ref: Library<7>-Footnote-432836453
Ref: Library<7>-Footnote-442836510
Ref: Library<7>-Footnote-452836567
Ref: Library<7>-Footnote-462836624
Ref: Library<7>-Footnote-472836681
Ref: Library<7>-Footnote-482836737
Ref: Library<7>-Footnote-492836793
Ref: Library<7>-Footnote-502836850
Ref: Library<7>-Footnote-512836907
Ref: Library<7>-Footnote-522836964
Ref: Library<7>-Footnote-532837021
Ref: Library<7>-Footnote-542837078
Ref: Library<7>-Footnote-552837134
Ref: Library<7>-Footnote-562837191
Ref: Library<7>-Footnote-572837248
Ref: Library<7>-Footnote-582837305
Ref: Library<7>-Footnote-592837361
Ref: Library<7>-Footnote-602837417
Ref: Library<7>-Footnote-612837483
Ref: Library<7>-Footnote-622837549
Ref: Library<7>-Footnote-632837615
Ref: Library<7>-Footnote-642837671
Node: Documentation<3>2837737
Ref: whatsnew/changelog id382837847
Ref: 15422837847
Ref: Documentation<3>-Footnote-12838258
Ref: Documentation<3>-Footnote-22838314
Ref: Documentation<3>-Footnote-32838370
Node: Tests<5>2838425
Ref: whatsnew/changelog id392838533
Ref: 15432838533
Ref: Tests<5>-Footnote-12839637
Ref: Tests<5>-Footnote-22839692
Ref: Tests<5>-Footnote-32839748
Ref: Tests<5>-Footnote-42839804
Ref: Tests<5>-Footnote-52839860
Ref: Tests<5>-Footnote-62839916
Ref: Tests<5>-Footnote-72839972
Node: Build<7>2840028
Ref: whatsnew/changelog id402840130
Ref: 15442840130
Ref: Build<7>-Footnote-12840406
Ref: Build<7>-Footnote-22840462
Ref: Build<7>-Footnote-32840518
Node: Windows<4>2840573
Ref: whatsnew/changelog id412840675
Ref: 15452840675
Ref: Windows<4>-Footnote-12842133
Ref: Windows<4>-Footnote-22842189
Ref: Windows<4>-Footnote-32842245
Ref: Windows<4>-Footnote-42842300
Ref: Windows<4>-Footnote-52842356
Ref: Windows<4>-Footnote-62842411
Node: C API<7>2842467
Ref: whatsnew/changelog id422842552
Ref: 15472842552
Ref: C API<7>-Footnote-12845807
Ref: C API<7>-Footnote-22845863
Ref: C API<7>-Footnote-32845905
Ref: C API<7>-Footnote-42845960
Ref: C API<7>-Footnote-52846016
Ref: C API<7>-Footnote-62846072
Ref: C API<7>-Footnote-72846128
Ref: C API<7>-Footnote-82846184
Ref: C API<7>-Footnote-92846240
Ref: C API<7>-Footnote-102846296
Ref: C API<7>-Footnote-112846353
Ref: C API<7>-Footnote-122846410
Ref: C API<7>-Footnote-132846467
Ref: C API<7>-Footnote-142846524
Ref: C API<7>-Footnote-152846567
Ref: C API<7>-Footnote-162846624
Ref: C API<7>-Footnote-172846681
Ref: C API<7>-Footnote-182846737
Ref: C API<7>-Footnote-192846794
Node: Python 3 13 0 alpha 52846851
Ref: whatsnew/changelog python-3-13-0-alpha-52846996
Ref: 15492846996
Node: Security<5>2847366
Ref: whatsnew/changelog id432847464
Ref: 154a2847464
Ref: Security<5>-Footnote-12848274
Ref: Security<5>-Footnote-22848330
Ref: Security<5>-Footnote-32848400
Node: Core and Builtins<9>2848456
Ref: whatsnew/changelog id442848573
Ref: 154b2848573
Ref: Core and Builtins<9>-Footnote-12851193
Ref: Core and Builtins<9>-Footnote-22851249
Ref: Core and Builtins<9>-Footnote-32851305
Ref: Core and Builtins<9>-Footnote-42851347
Ref: Core and Builtins<9>-Footnote-52851403
Ref: Core and Builtins<9>-Footnote-62851459
Ref: Core and Builtins<9>-Footnote-72851515
Ref: Core and Builtins<9>-Footnote-82851571
Ref: Core and Builtins<9>-Footnote-92851627
Ref: Core and Builtins<9>-Footnote-102851683
Ref: Core and Builtins<9>-Footnote-112851740
Ref: Core and Builtins<9>-Footnote-122851797
Ref: Core and Builtins<9>-Footnote-132851854
Ref: Core and Builtins<9>-Footnote-142851911
Ref: Core and Builtins<9>-Footnote-152851968
Ref: Core and Builtins<9>-Footnote-162852025
Ref: Core and Builtins<9>-Footnote-172852082
Ref: Core and Builtins<9>-Footnote-182852139
Node: Library<8>2852195
Ref: whatsnew/changelog id452852317
Ref: 154e2852317
Ref: Library<8>-Footnote-12864085
Ref: Library<8>-Footnote-22864141
Ref: Library<8>-Footnote-32864197
Ref: Library<8>-Footnote-42864253
Ref: Library<8>-Footnote-52864309
Ref: Library<8>-Footnote-62864351
Ref: Library<8>-Footnote-72864407
Ref: Library<8>-Footnote-82864463
Ref: Library<8>-Footnote-92864519
Ref: Library<8>-Footnote-102864574
Ref: Library<8>-Footnote-112864630
Ref: Library<8>-Footnote-122864686
Ref: Library<8>-Footnote-132864742
Ref: Library<8>-Footnote-142864798
Ref: Library<8>-Footnote-152864855
Ref: Library<8>-Footnote-162864912
Ref: Library<8>-Footnote-172864968
Ref: Library<8>-Footnote-182865024
Ref: Library<8>-Footnote-192865081
Ref: Library<8>-Footnote-202865137
Ref: Library<8>-Footnote-212865194
Ref: Library<8>-Footnote-222865251
Ref: Library<8>-Footnote-232865308
Ref: Library<8>-Footnote-242865365
Ref: Library<8>-Footnote-252865421
Ref: Library<8>-Footnote-262865477
Ref: Library<8>-Footnote-272865534
Ref: Library<8>-Footnote-282865591
Ref: Library<8>-Footnote-292865648
Ref: Library<8>-Footnote-302865705
Ref: Library<8>-Footnote-312865762
Ref: Library<8>-Footnote-322865819
Ref: Library<8>-Footnote-332865876
Ref: Library<8>-Footnote-342865933
Ref: Library<8>-Footnote-352865990
Ref: Library<8>-Footnote-362866047
Ref: Library<8>-Footnote-372866090
Ref: Library<8>-Footnote-382866147
Ref: Library<8>-Footnote-392866204
Ref: Library<8>-Footnote-402866261
Ref: Library<8>-Footnote-412866318
Ref: Library<8>-Footnote-422866375
Ref: Library<8>-Footnote-432866432
Ref: Library<8>-Footnote-442866489
Ref: Library<8>-Footnote-452866546
Ref: Library<8>-Footnote-462866603
Ref: Library<8>-Footnote-472866660
Ref: Library<8>-Footnote-482866716
Ref: Library<8>-Footnote-492866773
Ref: Library<8>-Footnote-502866830
Ref: Library<8>-Footnote-512866886
Ref: Library<8>-Footnote-522866942
Ref: Library<8>-Footnote-532866999
Ref: Library<8>-Footnote-542867055
Ref: Library<8>-Footnote-552867112
Ref: Library<8>-Footnote-562867168
Ref: Library<8>-Footnote-572867225
Ref: Library<8>-Footnote-582867282
Ref: Library<8>-Footnote-592867338
Ref: Library<8>-Footnote-602867394
Ref: Library<8>-Footnote-612867450
Ref: Library<8>-Footnote-622867516
Ref: Library<8>-Footnote-632867582
Ref: Library<8>-Footnote-642867648
Ref: Library<8>-Footnote-652867714
Ref: Library<8>-Footnote-662867780
Ref: Library<8>-Footnote-672867846
Node: Documentation<4>2867912
Ref: whatsnew/changelog id462868022
Ref: 15572868022
Ref: Documentation<4>-Footnote-12868271
Ref: Documentation<4>-Footnote-22868327
Ref: Documentation<4>-Footnote-32868397
Node: Tests<6>2868453
Ref: whatsnew/changelog id472868561
Ref: 15582868561
Ref: Tests<6>-Footnote-12869750
Ref: Tests<6>-Footnote-22869805
Ref: Tests<6>-Footnote-32869860
Ref: Tests<6>-Footnote-42869916
Ref: Tests<6>-Footnote-52869972
Ref: Tests<6>-Footnote-62870028
Ref: Tests<6>-Footnote-72870084
Ref: Tests<6>-Footnote-82870140
Ref: Tests<6>-Footnote-92870196
Node: Build<8>2870252
Ref: whatsnew/changelog id482870354
Ref: 15592870354
Ref: Build<8>-Footnote-12871258
Ref: Build<8>-Footnote-22871314
Ref: Build<8>-Footnote-32871369
Ref: Build<8>-Footnote-42871425
Ref: Build<8>-Footnote-52871480
Ref: Build<8>-Footnote-62871536
Ref: Build<8>-Footnote-72871592
Ref: Build<8>-Footnote-82871648
Ref: Build<8>-Footnote-92871704
Node: Windows<5>2871760
Ref: whatsnew/changelog id492871862
Ref: 155a2871862
Ref: Windows<5>-Footnote-12872952
Ref: Windows<5>-Footnote-22873008
Ref: Windows<5>-Footnote-32873064
Ref: Windows<5>-Footnote-42873120
Node: macOS<3>2873176
Ref: whatsnew/changelog id502873277
Ref: 155b2873277
Ref: macOS<3>-Footnote-12873405
Node: IDLE<7>2873461
Ref: whatsnew/changelog id512873566
Ref: 155c2873566
Ref: IDLE<7>-Footnote-12873746
Node: Tools/Demos<2>2873801
Ref: whatsnew/changelog id522873906
Ref: 155d2873906
Ref: Tools/Demos<2>-Footnote-12874147
Ref: Tools/Demos<2>-Footnote-22874203
Node: C API<8>2874268
Ref: whatsnew/changelog id532874357
Ref: 155e2874357
Ref: C API<8>-Footnote-12874926
Ref: C API<8>-Footnote-22874982
Node: Python 3 13 0 alpha 42875038
Ref: whatsnew/changelog python-3-13-0-alpha-42875183
Ref: 15632875183
Node: Security<6>2875556
Ref: whatsnew/changelog id542875655
Ref: 15642875655
Ref: Security<6>-Footnote-12875916
Ref: Security<6>-Footnote-22875972
Node: Core and Builtins<10>2876028
Ref: whatsnew/changelog id552876146
Ref: 15652876146
Ref: Core and Builtins<10>-Footnote-12881456
Ref: Core and Builtins<10>-Footnote-22881512
Ref: Core and Builtins<10>-Footnote-32881568
Ref: Core and Builtins<10>-Footnote-42881624
Ref: Core and Builtins<10>-Footnote-52881680
Ref: Core and Builtins<10>-Footnote-62881736
Ref: Core and Builtins<10>-Footnote-72881792
Ref: Core and Builtins<10>-Footnote-82881848
Ref: Core and Builtins<10>-Footnote-92881904
Ref: Core and Builtins<10>-Footnote-102881960
Ref: Core and Builtins<10>-Footnote-112882016
Ref: Core and Builtins<10>-Footnote-122882073
Ref: Core and Builtins<10>-Footnote-132882130
Ref: Core and Builtins<10>-Footnote-142882187
Ref: Core and Builtins<10>-Footnote-152882244
Ref: Core and Builtins<10>-Footnote-162882301
Ref: Core and Builtins<10>-Footnote-172882358
Ref: Core and Builtins<10>-Footnote-182882415
Ref: Core and Builtins<10>-Footnote-192882472
Ref: Core and Builtins<10>-Footnote-202882529
Ref: Core and Builtins<10>-Footnote-212882586
Ref: Core and Builtins<10>-Footnote-222882643
Ref: Core and Builtins<10>-Footnote-232882700
Ref: Core and Builtins<10>-Footnote-242882757
Ref: Core and Builtins<10>-Footnote-252882814
Ref: Core and Builtins<10>-Footnote-262882871
Ref: Core and Builtins<10>-Footnote-272882928
Ref: Core and Builtins<10>-Footnote-282882991
Ref: Core and Builtins<10>-Footnote-292883048
Ref: Core and Builtins<10>-Footnote-302883104
Node: Library<9>2883161
Ref: whatsnew/changelog id562883284
Ref: 156a2883284
Ref: Library<9>-Footnote-12897218
Ref: Library<9>-Footnote-22897274
Ref: Library<9>-Footnote-32897330
Ref: Library<9>-Footnote-42897386
Ref: Library<9>-Footnote-52897442
Ref: Library<9>-Footnote-62897498
Ref: Library<9>-Footnote-72897554
Ref: Library<9>-Footnote-82897610
Ref: Library<9>-Footnote-92897665
Ref: Library<9>-Footnote-102897720
Ref: Library<9>-Footnote-112897777
Ref: Library<9>-Footnote-122897833
Ref: Library<9>-Footnote-132897890
Ref: Library<9>-Footnote-142897946
Ref: Library<9>-Footnote-152898003
Ref: Library<9>-Footnote-162898060
Ref: Library<9>-Footnote-172898117
Ref: Library<9>-Footnote-182898174
Ref: Library<9>-Footnote-192898231
Ref: Library<9>-Footnote-202898287
Ref: Library<9>-Footnote-212898344
Ref: Library<9>-Footnote-222898401
Ref: Library<9>-Footnote-232898457
Ref: Library<9>-Footnote-242898514
Ref: Library<9>-Footnote-252898571
Ref: Library<9>-Footnote-262898627
Ref: Library<9>-Footnote-272898683
Ref: Library<9>-Footnote-282898739
Ref: Library<9>-Footnote-292898796
Ref: Library<9>-Footnote-302898852
Ref: Library<9>-Footnote-312898909
Ref: Library<9>-Footnote-322898966
Ref: Library<9>-Footnote-332899023
Ref: Library<9>-Footnote-342899080
Ref: Library<9>-Footnote-352899137
Ref: Library<9>-Footnote-362899194
Ref: Library<9>-Footnote-372899250
Ref: Library<9>-Footnote-382899307
Ref: Library<9>-Footnote-392899364
Ref: Library<9>-Footnote-402899421
Ref: Library<9>-Footnote-412899478
Ref: Library<9>-Footnote-422899535
Ref: Library<9>-Footnote-432899579
Ref: Library<9>-Footnote-442899636
Ref: Library<9>-Footnote-452899693
Ref: Library<9>-Footnote-462899750
Ref: Library<9>-Footnote-472899807
Ref: Library<9>-Footnote-482899863
Ref: Library<9>-Footnote-492899920
Ref: Library<9>-Footnote-502899977
Ref: Library<9>-Footnote-512900033
Ref: Library<9>-Footnote-522900090
Ref: Library<9>-Footnote-532900147
Ref: Library<9>-Footnote-542900203
Ref: Library<9>-Footnote-552900260
Ref: Library<9>-Footnote-562900317
Ref: Library<9>-Footnote-572900374
Ref: Library<9>-Footnote-582900430
Ref: Library<9>-Footnote-592900487
Ref: Library<9>-Footnote-602900543
Ref: Library<9>-Footnote-612900600
Ref: Library<9>-Footnote-622900657
Ref: Library<9>-Footnote-632900714
Ref: Library<9>-Footnote-642900770
Ref: Library<9>-Footnote-652900826
Ref: Library<9>-Footnote-662900883
Ref: Library<9>-Footnote-672900940
Ref: Library<9>-Footnote-682900996
Ref: Library<9>-Footnote-692901052
Ref: Library<9>-Footnote-702901109
Ref: Library<9>-Footnote-712901166
Ref: Library<9>-Footnote-722901223
Ref: Library<9>-Footnote-732901279
Ref: Library<9>-Footnote-742901336
Ref: Library<9>-Footnote-752901392
Ref: Library<9>-Footnote-762901449
Ref: Library<9>-Footnote-772901505
Node: Documentation<5>2901571
Ref: whatsnew/changelog id572901681
Ref: 157c2901681
Ref: Documentation<5>-Footnote-12902252
Ref: Documentation<5>-Footnote-22902308
Node: Tests<7>2902364
Ref: whatsnew/changelog id582902472
Ref: 157d2902472
Ref: Tests<7>-Footnote-12902864
Ref: Tests<7>-Footnote-22902920
Node: Build<9>2902976
Ref: whatsnew/changelog id592903078
Ref: 157e2903078
Ref: Build<9>-Footnote-12903616
Ref: Build<9>-Footnote-22903672
Ref: Build<9>-Footnote-32903728
Ref: Build<9>-Footnote-42903784
Node: Windows<6>2903840
Ref: whatsnew/changelog id602903942
Ref: 157f2903942
Ref: Windows<6>-Footnote-12904695
Ref: Windows<6>-Footnote-22904751
Ref: Windows<6>-Footnote-32904807
Ref: Windows<6>-Footnote-42904863
Ref: Windows<6>-Footnote-52904919
Ref: Windows<6>-Footnote-62904975
Ref: Windows<6>-Footnote-72905031
Node: macOS<4>2905086
Ref: whatsnew/changelog id612905187
Ref: 15802905187
Ref: macOS<4>-Footnote-12905726
Ref: macOS<4>-Footnote-22905782
Ref: macOS<4>-Footnote-32905838
Ref: macOS<4>-Footnote-42905894
Node: IDLE<8>2905949
Ref: whatsnew/changelog id622906054
Ref: 15822906054
Ref: IDLE<8>-Footnote-12906381
Ref: IDLE<8>-Footnote-22906436
Node: Tools/Demos<3>2906492
Ref: whatsnew/changelog id632906597
Ref: 15832906597
Ref: Tools/Demos<3>-Footnote-12907208
Ref: Tools/Demos<3>-Footnote-22907264
Ref: Tools/Demos<3>-Footnote-32907320
Node: C API<9>2907376
Ref: whatsnew/changelog id642907465
Ref: 15852907465
Ref: C API<9>-Footnote-12909409
Ref: C API<9>-Footnote-22909465
Ref: C API<9>-Footnote-32909521
Ref: C API<9>-Footnote-42909577
Ref: C API<9>-Footnote-52909633
Ref: C API<9>-Footnote-62909689
Ref: C API<9>-Footnote-72909745
Node: Python 3 13 0 alpha 32909801
Ref: whatsnew/changelog python-3-13-0-alpha-32909946
Ref: 15882909946
Node: Security<7>2910291
Ref: whatsnew/changelog id652910390
Ref: 15892910390
Ref: Security<7>-Footnote-12910679
Ref: Security<7>-Footnote-22910735
Node: Core and Builtins<11>2910791
Ref: whatsnew/changelog id662910910
Ref: 158a2910910
Ref: Core and Builtins<11>-Footnote-12918285
Ref: Core and Builtins<11>-Footnote-22918341
Ref: Core and Builtins<11>-Footnote-32918397
Ref: Core and Builtins<11>-Footnote-42918453
Ref: Core and Builtins<11>-Footnote-52918509
Ref: Core and Builtins<11>-Footnote-62918564
Ref: Core and Builtins<11>-Footnote-72918606
Ref: Core and Builtins<11>-Footnote-82918662
Ref: Core and Builtins<11>-Footnote-92918718
Ref: Core and Builtins<11>-Footnote-102918774
Ref: Core and Builtins<11>-Footnote-112918831
Ref: Core and Builtins<11>-Footnote-122918887
Ref: Core and Builtins<11>-Footnote-132918944
Ref: Core and Builtins<11>-Footnote-142919001
Ref: Core and Builtins<11>-Footnote-152919058
Ref: Core and Builtins<11>-Footnote-162919115
Ref: Core and Builtins<11>-Footnote-172919172
Ref: Core and Builtins<11>-Footnote-182919229
Ref: Core and Builtins<11>-Footnote-192919286
Ref: Core and Builtins<11>-Footnote-202919343
Ref: Core and Builtins<11>-Footnote-212919400
Ref: Core and Builtins<11>-Footnote-222919457
Ref: Core and Builtins<11>-Footnote-232919514
Ref: Core and Builtins<11>-Footnote-242919571
Ref: Core and Builtins<11>-Footnote-252919627
Ref: Core and Builtins<11>-Footnote-262919684
Ref: Core and Builtins<11>-Footnote-272919741
Ref: Core and Builtins<11>-Footnote-282919797
Ref: Core and Builtins<11>-Footnote-292919854
Ref: Core and Builtins<11>-Footnote-302919911
Ref: Core and Builtins<11>-Footnote-312919968
Ref: Core and Builtins<11>-Footnote-322920025
Ref: Core and Builtins<11>-Footnote-332920082
Ref: Core and Builtins<11>-Footnote-342920138
Ref: Core and Builtins<11>-Footnote-352920195
Ref: Core and Builtins<11>-Footnote-362920252
Ref: Core and Builtins<11>-Footnote-372920309
Ref: Core and Builtins<11>-Footnote-382920366
Ref: Core and Builtins<11>-Footnote-392920422
Ref: Core and Builtins<11>-Footnote-402920479
Ref: Core and Builtins<11>-Footnote-412920536
Ref: Core and Builtins<11>-Footnote-422920593
Ref: Core and Builtins<11>-Footnote-432920649
Ref: Core and Builtins<11>-Footnote-442920715
Ref: Core and Builtins<11>-Footnote-452920781
Ref: Core and Builtins<11>-Footnote-462920824
Node: Library<10>2920890
Ref: whatsnew/changelog id672921014
Ref: 158f2921014
Ref: Library<10>-Footnote-12946202
Ref: Library<10>-Footnote-22946258
Ref: Library<10>-Footnote-32946314
Ref: Library<10>-Footnote-42946370
Ref: Library<10>-Footnote-52946426
Ref: Library<10>-Footnote-62946482
Ref: Library<10>-Footnote-72946538
Ref: Library<10>-Footnote-82946594
Ref: Library<10>-Footnote-92946650
Ref: Library<10>-Footnote-102946706
Ref: Library<10>-Footnote-112946762
Ref: Library<10>-Footnote-122946819
Ref: Library<10>-Footnote-132946876
Ref: Library<10>-Footnote-142946933
Ref: Library<10>-Footnote-152946990
Ref: Library<10>-Footnote-162947047
Ref: Library<10>-Footnote-172947104
Ref: Library<10>-Footnote-182947161
Ref: Library<10>-Footnote-192947218
Ref: Library<10>-Footnote-202947275
Ref: Library<10>-Footnote-212947331
Ref: Library<10>-Footnote-222947388
Ref: Library<10>-Footnote-232947444
Ref: Library<10>-Footnote-242947501
Ref: Library<10>-Footnote-252947558
Ref: Library<10>-Footnote-262947615
Ref: Library<10>-Footnote-272947672
Ref: Library<10>-Footnote-282947729
Ref: Library<10>-Footnote-292947786
Ref: Library<10>-Footnote-302947843
Ref: Library<10>-Footnote-312947900
Ref: Library<10>-Footnote-322947957
Ref: Library<10>-Footnote-332948013
Ref: Library<10>-Footnote-342948070
Ref: Library<10>-Footnote-352948127
Ref: Library<10>-Footnote-362948184
Ref: Library<10>-Footnote-372948240
Ref: Library<10>-Footnote-382948297
Ref: Library<10>-Footnote-392948354
Ref: Library<10>-Footnote-402948411
Ref: Library<10>-Footnote-412948468
Ref: Library<10>-Footnote-422948525
Ref: Library<10>-Footnote-432948582
Ref: Library<10>-Footnote-442948639
Ref: Library<10>-Footnote-452948696
Ref: Library<10>-Footnote-462948753
Ref: Library<10>-Footnote-472948809
Ref: Library<10>-Footnote-482948866
Ref: Library<10>-Footnote-492948922
Ref: Library<10>-Footnote-502948979
Ref: Library<10>-Footnote-512949036
Ref: Library<10>-Footnote-522949093
Ref: Library<10>-Footnote-532949150
Ref: Library<10>-Footnote-542949207
Ref: Library<10>-Footnote-552949264
Ref: Library<10>-Footnote-562949320
Ref: Library<10>-Footnote-572949377
Ref: Library<10>-Footnote-582949433
Ref: Library<10>-Footnote-592949489
Ref: Library<10>-Footnote-602949545
Ref: Library<10>-Footnote-612949602
Ref: Library<10>-Footnote-622949659
Ref: Library<10>-Footnote-632949715
Ref: Library<10>-Footnote-642949771
Ref: Library<10>-Footnote-652949828
Ref: Library<10>-Footnote-662949885
Ref: Library<10>-Footnote-672949942
Ref: Library<10>-Footnote-682949999
Ref: Library<10>-Footnote-692950056
Ref: Library<10>-Footnote-702950113
Ref: Library<10>-Footnote-712950169
Ref: Library<10>-Footnote-722950226
Ref: Library<10>-Footnote-732950283
Ref: Library<10>-Footnote-742950340
Ref: Library<10>-Footnote-752950397
Ref: Library<10>-Footnote-762950454
Ref: Library<10>-Footnote-772950511
Ref: Library<10>-Footnote-782950567
Ref: Library<10>-Footnote-792950624
Ref: Library<10>-Footnote-802950681
Ref: Library<10>-Footnote-812950738
Ref: Library<10>-Footnote-822950794
Ref: Library<10>-Footnote-832950851
Ref: Library<10>-Footnote-842950908
Ref: Library<10>-Footnote-852950965
Ref: Library<10>-Footnote-862951022
Ref: Library<10>-Footnote-872951078
Ref: Library<10>-Footnote-882951135
Ref: Library<10>-Footnote-892951191
Ref: Library<10>-Footnote-902951248
Ref: Library<10>-Footnote-912951305
Ref: Library<10>-Footnote-922951362
Ref: Library<10>-Footnote-932951419
Ref: Library<10>-Footnote-942951476
Ref: Library<10>-Footnote-952951532
Ref: Library<10>-Footnote-962951589
Ref: Library<10>-Footnote-972951645
Ref: Library<10>-Footnote-982951702
Ref: Library<10>-Footnote-992951758
Ref: Library<10>-Footnote-1002951814
Ref: Library<10>-Footnote-1012951871
Ref: Library<10>-Footnote-1022951929
Ref: Library<10>-Footnote-1032951987
Ref: Library<10>-Footnote-1042952045
Ref: Library<10>-Footnote-1052952117
Ref: Library<10>-Footnote-1062952174
Ref: Library<10>-Footnote-1072952231
Ref: Library<10>-Footnote-1082952289
Ref: Library<10>-Footnote-1092952347
Ref: Library<10>-Footnote-1102952405
Ref: Library<10>-Footnote-1112952462
Ref: Library<10>-Footnote-1122952520
Ref: Library<10>-Footnote-1132952578
Ref: Library<10>-Footnote-1142952635
Ref: Library<10>-Footnote-1152952693
Ref: Library<10>-Footnote-1162952737
Ref: Library<10>-Footnote-1172952795
Ref: Library<10>-Footnote-1182952852
Ref: Library<10>-Footnote-1192952909
Ref: Library<10>-Footnote-1202952966
Ref: Library<10>-Footnote-1212953033
Ref: Library<10>-Footnote-1222953100
Ref: Library<10>-Footnote-1232953167
Ref: Library<10>-Footnote-1242953234
Ref: Library<10>-Footnote-1252953301
Ref: Library<10>-Footnote-1262953368
Ref: Library<10>-Footnote-1272953435
Ref: Library<10>-Footnote-1282953502
Ref: Library<10>-Footnote-1292953569
Ref: Library<10>-Footnote-1302953636
Ref: Library<10>-Footnote-1312953703
Ref: Library<10>-Footnote-1322953770
Ref: Library<10>-Footnote-1332953837
Ref: Library<10>-Footnote-1342953904
Node: Documentation<6>2953971
Ref: whatsnew/changelog id682954082
Ref: 15af2954082
Ref: Documentation<6>-Footnote-12954648
Ref: Documentation<6>-Footnote-22954704
Ref: Documentation<6>-Footnote-32954760
Ref: Documentation<6>-Footnote-42954815
Node: Tests<8>2954873
Ref: whatsnew/changelog id692954982
Ref: 15b02954982
Ref: Tests<8>-Footnote-12956927
Ref: Tests<8>-Footnote-22956983
Ref: Tests<8>-Footnote-32957039
Ref: Tests<8>-Footnote-42957095
Ref: Tests<8>-Footnote-52957150
Ref: Tests<8>-Footnote-62957206
Ref: Tests<8>-Footnote-72957262
Ref: Tests<8>-Footnote-82957318
Ref: Tests<8>-Footnote-92957374
Ref: Tests<8>-Footnote-102957430
Node: Build<10>2957496
Ref: whatsnew/changelog id702957599
Ref: 15b12957599
Ref: Build<10>-Footnote-12958843
Ref: Build<10>-Footnote-22958899
Ref: Build<10>-Footnote-32958955
Ref: Build<10>-Footnote-42959011
Ref: Build<10>-Footnote-52959067
Ref: Build<10>-Footnote-62959123
Ref: Build<10>-Footnote-72959179
Ref: Build<10>-Footnote-82959244
Node: Windows<7>2959309
Ref: whatsnew/changelog id712959412
Ref: 15b22959412
Ref: Windows<7>-Footnote-12961253
Ref: Windows<7>-Footnote-22961309
Ref: Windows<7>-Footnote-32961365
Ref: Windows<7>-Footnote-42961421
Ref: Windows<7>-Footnote-52961477
Ref: Windows<7>-Footnote-62961532
Ref: Windows<7>-Footnote-72961587
Ref: Windows<7>-Footnote-82961643
Ref: Windows<7>-Footnote-92961699
Ref: Windows<7>-Footnote-102961754
Ref: Windows<7>-Footnote-112961810
Node: macOS<5>2961876
Ref: whatsnew/changelog id722961977
Ref: 15b32961977
Ref: macOS<5>-Footnote-12964373
Ref: macOS<5>-Footnote-22964429
Ref: macOS<5>-Footnote-32964485
Ref: macOS<5>-Footnote-42964541
Ref: macOS<5>-Footnote-52964596
Ref: macOS<5>-Footnote-62964651
Ref: macOS<5>-Footnote-72964706
Ref: macOS<5>-Footnote-82964762
Ref: macOS<5>-Footnote-92964818
Ref: macOS<5>-Footnote-102964874
Ref: macOS<5>-Footnote-112964931
Ref: macOS<5>-Footnote-122964988
Node: IDLE<9>2965045
Ref: whatsnew/changelog id732965145
Ref: 15b42965145
Ref: IDLE<9>-Footnote-12965721
Ref: IDLE<9>-Footnote-22965776
Ref: IDLE<9>-Footnote-32965832
Ref: IDLE<9>-Footnote-42965888
Ref: IDLE<9>-Footnote-52965944
Ref: IDLE<9>-Footnote-62966000
Node: C API<10>2966065
Ref: whatsnew/changelog id742966148
Ref: 15b52966148
Ref: C API<10>-Footnote-12966863
Ref: C API<10>-Footnote-22966919
Ref: C API<10>-Footnote-32966975
Ref: C API<10>-Footnote-42967031
Node: Python 3 13 0 alpha 22967086
Ref: whatsnew/changelog python-3-13-0-alpha-22967231
Ref: 15b62967231
Node: Core and Builtins<12>2967548
Ref: whatsnew/changelog id752967647
Ref: 15b72967647
Ref: Core and Builtins<12>-Footnote-12975474
Ref: Core and Builtins<12>-Footnote-22975530
Ref: Core and Builtins<12>-Footnote-32975586
Ref: Core and Builtins<12>-Footnote-42975642
Ref: Core and Builtins<12>-Footnote-52975698
Ref: Core and Builtins<12>-Footnote-62975754
Ref: Core and Builtins<12>-Footnote-72975810
Ref: Core and Builtins<12>-Footnote-82975866
Ref: Core and Builtins<12>-Footnote-92975921
Ref: Core and Builtins<12>-Footnote-102975976
Ref: Core and Builtins<12>-Footnote-112976032
Ref: Core and Builtins<12>-Footnote-122976089
Ref: Core and Builtins<12>-Footnote-132976146
Ref: Core and Builtins<12>-Footnote-142976203
Ref: Core and Builtins<12>-Footnote-152976260
Ref: Core and Builtins<12>-Footnote-162976317
Ref: Core and Builtins<12>-Footnote-172976374
Ref: Core and Builtins<12>-Footnote-182976431
Ref: Core and Builtins<12>-Footnote-192976488
Ref: Core and Builtins<12>-Footnote-202976545
Ref: Core and Builtins<12>-Footnote-212976602
Ref: Core and Builtins<12>-Footnote-222976659
Ref: Core and Builtins<12>-Footnote-232976716
Ref: Core and Builtins<12>-Footnote-242976773
Ref: Core and Builtins<12>-Footnote-252976830
Ref: Core and Builtins<12>-Footnote-262976887
Ref: Core and Builtins<12>-Footnote-272976944
Ref: Core and Builtins<12>-Footnote-282977001
Ref: Core and Builtins<12>-Footnote-292977058
Ref: Core and Builtins<12>-Footnote-302977114
Ref: Core and Builtins<12>-Footnote-312977170
Ref: Core and Builtins<12>-Footnote-322977227
Ref: Core and Builtins<12>-Footnote-332977284
Ref: Core and Builtins<12>-Footnote-342977341
Ref: Core and Builtins<12>-Footnote-352977398
Ref: Core and Builtins<12>-Footnote-362977455
Ref: Core and Builtins<12>-Footnote-372977512
Ref: Core and Builtins<12>-Footnote-382977569
Ref: Core and Builtins<12>-Footnote-392977626
Ref: Core and Builtins<12>-Footnote-402977683
Ref: Core and Builtins<12>-Footnote-412977740
Ref: Core and Builtins<12>-Footnote-422977797
Ref: Core and Builtins<12>-Footnote-432977854
Ref: Core and Builtins<12>-Footnote-442977910
Ref: Core and Builtins<12>-Footnote-452977976
Ref: Core and Builtins<12>-Footnote-462978033
Ref: Core and Builtins<12>-Footnote-472978099
Ref: Core and Builtins<12>-Footnote-482978156
Ref: Core and Builtins<12>-Footnote-492978213
Ref: Core and Builtins<12>-Footnote-502978270
Node: Library<11>2978336
Ref: whatsnew/changelog id762978452
Ref: 15bd2978452
Ref: Library<11>-Footnote-12989011
Ref: Library<11>-Footnote-22989067
Ref: Library<11>-Footnote-32989123
Ref: Library<11>-Footnote-42989179
Ref: Library<11>-Footnote-52989235
Ref: Library<11>-Footnote-62989291
Ref: Library<11>-Footnote-72989347
Ref: Library<11>-Footnote-82989403
Ref: Library<11>-Footnote-92989459
Ref: Library<11>-Footnote-102989515
Ref: Library<11>-Footnote-112989572
Ref: Library<11>-Footnote-122989628
Ref: Library<11>-Footnote-132989685
Ref: Library<11>-Footnote-142989742
Ref: Library<11>-Footnote-152989799
Ref: Library<11>-Footnote-162989856
Ref: Library<11>-Footnote-172989913
Ref: Library<11>-Footnote-182989970
Ref: Library<11>-Footnote-192990027
Ref: Library<11>-Footnote-202990083
Ref: Library<11>-Footnote-212990140
Ref: Library<11>-Footnote-222990197
Ref: Library<11>-Footnote-232990253
Ref: Library<11>-Footnote-242990310
Ref: Library<11>-Footnote-252990366
Ref: Library<11>-Footnote-262990423
Ref: Library<11>-Footnote-272990480
Ref: Library<11>-Footnote-282990537
Ref: Library<11>-Footnote-292990594
Ref: Library<11>-Footnote-302990651
Ref: Library<11>-Footnote-312990708
Ref: Library<11>-Footnote-322990765
Ref: Library<11>-Footnote-332990822
Ref: Library<11>-Footnote-342990879
Ref: Library<11>-Footnote-352990936
Ref: Library<11>-Footnote-362990993
Ref: Library<11>-Footnote-372991050
Ref: Library<11>-Footnote-382991107
Ref: Library<11>-Footnote-392991163
Ref: Library<11>-Footnote-402991219
Ref: Library<11>-Footnote-412991276
Ref: Library<11>-Footnote-422991333
Ref: Library<11>-Footnote-432991390
Ref: Library<11>-Footnote-442991446
Ref: Library<11>-Footnote-452991502
Ref: Library<11>-Footnote-462991559
Ref: Library<11>-Footnote-472991616
Ref: Library<11>-Footnote-482991673
Ref: Library<11>-Footnote-492991730
Ref: Library<11>-Footnote-502991786
Ref: Library<11>-Footnote-512991843
Ref: Library<11>-Footnote-522991900
Ref: Library<11>-Footnote-532991957
Ref: Library<11>-Footnote-542992013
Ref: Library<11>-Footnote-552992069
Ref: Library<11>-Footnote-562992125
Ref: Library<11>-Footnote-572992182
Ref: Library<11>-Footnote-582992239
Ref: Library<11>-Footnote-592992295
Ref: Library<11>-Footnote-602992351
Ref: Library<11>-Footnote-612992436
Ref: Library<11>-Footnote-622992492
Node: Tests<9>2992548
Ref: whatsnew/changelog id772992652
Ref: 15d12992652
Ref: Tests<9>-Footnote-12994238
Ref: Tests<9>-Footnote-22994294
Ref: Tests<9>-Footnote-32994350
Ref: Tests<9>-Footnote-42994406
Ref: Tests<9>-Footnote-52994462
Ref: Tests<9>-Footnote-62994518
Ref: Tests<9>-Footnote-72994574
Ref: Tests<9>-Footnote-82994630
Node: Build<11>2994686
Ref: whatsnew/changelog id782994789
Ref: 15d22994789
Ref: Build<11>-Footnote-12995775
Ref: Build<11>-Footnote-22995830
Ref: Build<11>-Footnote-32995886
Ref: Build<11>-Footnote-42995936
Ref: Build<11>-Footnote-52995992
Ref: Build<11>-Footnote-62996048
Node: Windows<8>2996103
Ref: whatsnew/changelog id792996206
Ref: 15d32996206
Ref: Windows<8>-Footnote-12996660
Ref: Windows<8>-Footnote-22996716
Ref: Windows<8>-Footnote-32996772
Node: macOS<6>2996828
Ref: whatsnew/changelog id802996930
Ref: 15d52996930
Ref: macOS<6>-Footnote-12997861
Ref: macOS<6>-Footnote-22997916
Ref: macOS<6>-Footnote-32997972
Ref: macOS<6>-Footnote-42998028
Ref: macOS<6>-Footnote-52998083
Node: IDLE<10>2998138
Ref: whatsnew/changelog id812998244
Ref: 15d62998244
Ref: IDLE<10>-Footnote-12998582
Node: Tools/Demos<4>2998647
Ref: whatsnew/changelog id822998754
Ref: 15d72998754
Ref: Tools/Demos<4>-Footnote-12999111
Node: C API<11>2999167
Ref: whatsnew/changelog id832999257
Ref: 15d82999257
Ref: C API<11>-Footnote-13004622
Ref: C API<11>-Footnote-23004678
Ref: C API<11>-Footnote-33004734
Ref: C API<11>-Footnote-43004790
Ref: C API<11>-Footnote-53004846
Ref: C API<11>-Footnote-63004902
Ref: C API<11>-Footnote-73004958
Ref: C API<11>-Footnote-83005014
Ref: C API<11>-Footnote-93005070
Ref: C API<11>-Footnote-103005126
Ref: C API<11>-Footnote-113005183
Ref: C API<11>-Footnote-123005226
Ref: C API<11>-Footnote-133005283
Ref: C API<11>-Footnote-143005340
Ref: C API<11>-Footnote-153005397
Ref: C API<11>-Footnote-163005454
Ref: C API<11>-Footnote-173005511
Ref: C API<11>-Footnote-183005567
Ref: C API<11>-Footnote-193005623
Ref: C API<11>-Footnote-203005680
Node: Python 3 13 0 alpha 13005736
Ref: whatsnew/changelog python-3-13-0-alpha-13005880
Ref: 15d93005880
Node: Security<8>3006258
Ref: whatsnew/changelog id843006357
Ref: 15da3006357
Ref: Security<8>-Footnote-13007625
Ref: Security<8>-Footnote-23007681
Ref: Security<8>-Footnote-33007751
Ref: Security<8>-Footnote-43007807
Ref: Security<8>-Footnote-53007863
Ref: Security<8>-Footnote-63007919
Ref: Security<8>-Footnote-73007974
Node: Core and Builtins<13>3008030
Ref: whatsnew/changelog id853008149
Ref: 15db3008149
Ref: Core and Builtins<13>-Footnote-13038896
Ref: Core and Builtins<13>-Footnote-23038952
Ref: Core and Builtins<13>-Footnote-33039008
Ref: Core and Builtins<13>-Footnote-43039064
Ref: Core and Builtins<13>-Footnote-53039120
Ref: Core and Builtins<13>-Footnote-63039176
Ref: Core and Builtins<13>-Footnote-73039232
Ref: Core and Builtins<13>-Footnote-83039288
Ref: Core and Builtins<13>-Footnote-93039344
Ref: Core and Builtins<13>-Footnote-103039400
Ref: Core and Builtins<13>-Footnote-113039457
Ref: Core and Builtins<13>-Footnote-123039514
Ref: Core and Builtins<13>-Footnote-133039571
Ref: Core and Builtins<13>-Footnote-143039628
Ref: Core and Builtins<13>-Footnote-153039685
Ref: Core and Builtins<13>-Footnote-163039742
Ref: Core and Builtins<13>-Footnote-173039799
Ref: Core and Builtins<13>-Footnote-183039856
Ref: Core and Builtins<13>-Footnote-193039913
Ref: Core and Builtins<13>-Footnote-203039970
Ref: Core and Builtins<13>-Footnote-213040027
Ref: Core and Builtins<13>-Footnote-223040084
Ref: Core and Builtins<13>-Footnote-233040141
Ref: Core and Builtins<13>-Footnote-243040198
Ref: Core and Builtins<13>-Footnote-253040255
Ref: Core and Builtins<13>-Footnote-263040312
Ref: Core and Builtins<13>-Footnote-273040369
Ref: Core and Builtins<13>-Footnote-283040426
Ref: Core and Builtins<13>-Footnote-293040483
Ref: Core and Builtins<13>-Footnote-303040540
Ref: Core and Builtins<13>-Footnote-313040597
Ref: Core and Builtins<13>-Footnote-323040654
Ref: Core and Builtins<13>-Footnote-333040711
Ref: Core and Builtins<13>-Footnote-343040768
Ref: Core and Builtins<13>-Footnote-353040825
Ref: Core and Builtins<13>-Footnote-363040882
Ref: Core and Builtins<13>-Footnote-373040939
Ref: Core and Builtins<13>-Footnote-383040996
Ref: Core and Builtins<13>-Footnote-393041053
Ref: Core and Builtins<13>-Footnote-403041110
Ref: Core and Builtins<13>-Footnote-413041167
Ref: Core and Builtins<13>-Footnote-423041224
Ref: Core and Builtins<13>-Footnote-433041281
Ref: Core and Builtins<13>-Footnote-443041338
Ref: Core and Builtins<13>-Footnote-453041394
Ref: Core and Builtins<13>-Footnote-463041451
Ref: Core and Builtins<13>-Footnote-473041508
Ref: Core and Builtins<13>-Footnote-483041565
Ref: Core and Builtins<13>-Footnote-493041622
Ref: Core and Builtins<13>-Footnote-503041679
Ref: Core and Builtins<13>-Footnote-513041736
Ref: Core and Builtins<13>-Footnote-523041793
Ref: Core and Builtins<13>-Footnote-533041850
Ref: Core and Builtins<13>-Footnote-543041907
Ref: Core and Builtins<13>-Footnote-553041964
Ref: Core and Builtins<13>-Footnote-563042021
Ref: Core and Builtins<13>-Footnote-573042078
Ref: Core and Builtins<13>-Footnote-583042135
Ref: Core and Builtins<13>-Footnote-593042192
Ref: Core and Builtins<13>-Footnote-603042249
Ref: Core and Builtins<13>-Footnote-613042306
Ref: Core and Builtins<13>-Footnote-623042363
Ref: Core and Builtins<13>-Footnote-633042420
Ref: Core and Builtins<13>-Footnote-643042477
Ref: Core and Builtins<13>-Footnote-653042533
Ref: Core and Builtins<13>-Footnote-663042590
Ref: Core and Builtins<13>-Footnote-673042647
Ref: Core and Builtins<13>-Footnote-683042703
Ref: Core and Builtins<13>-Footnote-693042760
Ref: Core and Builtins<13>-Footnote-703042817
Ref: Core and Builtins<13>-Footnote-713042874
Ref: Core and Builtins<13>-Footnote-723042931
Ref: Core and Builtins<13>-Footnote-733042988
Ref: Core and Builtins<13>-Footnote-743043044
Ref: Core and Builtins<13>-Footnote-753043101
Ref: Core and Builtins<13>-Footnote-763043158
Ref: Core and Builtins<13>-Footnote-773043215
Ref: Core and Builtins<13>-Footnote-783043272
Ref: Core and Builtins<13>-Footnote-793043329
Ref: Core and Builtins<13>-Footnote-803043386
Ref: Core and Builtins<13>-Footnote-813043443
Ref: Core and Builtins<13>-Footnote-823043500
Ref: Core and Builtins<13>-Footnote-833043557
Ref: Core and Builtins<13>-Footnote-843043614
Ref: Core and Builtins<13>-Footnote-853043657
Ref: Core and Builtins<13>-Footnote-863043714
Ref: Core and Builtins<13>-Footnote-873043771
Ref: Core and Builtins<13>-Footnote-883043828
Ref: Core and Builtins<13>-Footnote-893043884
Ref: Core and Builtins<13>-Footnote-903043941
Ref: Core and Builtins<13>-Footnote-913043998
Ref: Core and Builtins<13>-Footnote-923044055
Ref: Core and Builtins<13>-Footnote-933044112
Ref: Core and Builtins<13>-Footnote-943044169
Ref: Core and Builtins<13>-Footnote-953044226
Ref: Core and Builtins<13>-Footnote-963044283
Ref: Core and Builtins<13>-Footnote-973044340
Ref: Core and Builtins<13>-Footnote-983044397
Ref: Core and Builtins<13>-Footnote-993044454
Ref: Core and Builtins<13>-Footnote-1003044511
Ref: Core and Builtins<13>-Footnote-1013044569
Ref: Core and Builtins<13>-Footnote-1023044627
Ref: Core and Builtins<13>-Footnote-1033044685
Ref: Core and Builtins<13>-Footnote-1043044743
Ref: Core and Builtins<13>-Footnote-1053044801
Ref: Core and Builtins<13>-Footnote-1063044859
Ref: Core and Builtins<13>-Footnote-1073044916
Ref: Core and Builtins<13>-Footnote-1083044973
Ref: Core and Builtins<13>-Footnote-1093045031
Ref: Core and Builtins<13>-Footnote-1103045089
Ref: Core and Builtins<13>-Footnote-1113045147
Ref: Core and Builtins<13>-Footnote-1123045205
Ref: Core and Builtins<13>-Footnote-1133045263
Ref: Core and Builtins<13>-Footnote-1143045321
Ref: Core and Builtins<13>-Footnote-1153045379
Ref: Core and Builtins<13>-Footnote-1163045437
Ref: Core and Builtins<13>-Footnote-1173045495
Ref: Core and Builtins<13>-Footnote-1183045553
Ref: Core and Builtins<13>-Footnote-1193045611
Ref: Core and Builtins<13>-Footnote-1203045669
Ref: Core and Builtins<13>-Footnote-1213045726
Ref: Core and Builtins<13>-Footnote-1223045784
Ref: Core and Builtins<13>-Footnote-1233045842
Ref: Core and Builtins<13>-Footnote-1243045899
Ref: Core and Builtins<13>-Footnote-1253045957
Ref: Core and Builtins<13>-Footnote-1263046015
Ref: Core and Builtins<13>-Footnote-1273046073
Ref: Core and Builtins<13>-Footnote-1283046131
Ref: Core and Builtins<13>-Footnote-1293046189
Ref: Core and Builtins<13>-Footnote-1303046247
Ref: Core and Builtins<13>-Footnote-1313046305
Ref: Core and Builtins<13>-Footnote-1323046363
Ref: Core and Builtins<13>-Footnote-1333046421
Ref: Core and Builtins<13>-Footnote-1343046479
Ref: Core and Builtins<13>-Footnote-1353046537
Ref: Core and Builtins<13>-Footnote-1363046595
Ref: Core and Builtins<13>-Footnote-1373046653
Ref: Core and Builtins<13>-Footnote-1383046711
Ref: Core and Builtins<13>-Footnote-1393046769
Ref: Core and Builtins<13>-Footnote-1403046827
Ref: Core and Builtins<13>-Footnote-1413046885
Ref: Core and Builtins<13>-Footnote-1423046943
Ref: Core and Builtins<13>-Footnote-1433047001
Ref: Core and Builtins<13>-Footnote-1443047059
Ref: Core and Builtins<13>-Footnote-1453047116
Ref: Core and Builtins<13>-Footnote-1463047174
Ref: Core and Builtins<13>-Footnote-1473047232
Ref: Core and Builtins<13>-Footnote-1483047289
Ref: Core and Builtins<13>-Footnote-1493047347
Ref: Core and Builtins<13>-Footnote-1503047405
Ref: Core and Builtins<13>-Footnote-1513047463
Ref: Core and Builtins<13>-Footnote-1523047521
Ref: Core and Builtins<13>-Footnote-1533047579
Ref: Core and Builtins<13>-Footnote-1543047637
Ref: Core and Builtins<13>-Footnote-1553047695
Ref: Core and Builtins<13>-Footnote-1563047753
Ref: Core and Builtins<13>-Footnote-1573047811
Ref: Core and Builtins<13>-Footnote-1583047869
Ref: Core and Builtins<13>-Footnote-1593047927
Ref: Core and Builtins<13>-Footnote-1603047985
Ref: Core and Builtins<13>-Footnote-1613048043
Ref: Core and Builtins<13>-Footnote-1623048101
Ref: Core and Builtins<13>-Footnote-1633048159
Ref: Core and Builtins<13>-Footnote-1643048217
Ref: Core and Builtins<13>-Footnote-1653048275
Ref: Core and Builtins<13>-Footnote-1663048333
Ref: Core and Builtins<13>-Footnote-1673048391
Ref: Core and Builtins<13>-Footnote-1683048448
Ref: Core and Builtins<13>-Footnote-1693048505
Ref: Core and Builtins<13>-Footnote-1703048562
Ref: Core and Builtins<13>-Footnote-1713048620
Node: Library<12>3048677
Ref: whatsnew/changelog id863048801
Ref: 15f03048801
Ref: Library<12>-Footnote-13097152
Ref: Library<12>-Footnote-23097208
Ref: Library<12>-Footnote-33097264
Ref: Library<12>-Footnote-43097320
Ref: Library<12>-Footnote-53097375
Ref: Library<12>-Footnote-63097431
Ref: Library<12>-Footnote-73097487
Ref: Library<12>-Footnote-83097543
Ref: Library<12>-Footnote-93097598
Ref: Library<12>-Footnote-103097654
Ref: Library<12>-Footnote-113097710
Ref: Library<12>-Footnote-123097767
Ref: Library<12>-Footnote-133097824
Ref: Library<12>-Footnote-143097881
Ref: Library<12>-Footnote-153097938
Ref: Library<12>-Footnote-163097995
Ref: Library<12>-Footnote-173098052
Ref: Library<12>-Footnote-183098109
Ref: Library<12>-Footnote-193098166
Ref: Library<12>-Footnote-203098223
Ref: Library<12>-Footnote-213098280
Ref: Library<12>-Footnote-223098337
Ref: Library<12>-Footnote-233098394
Ref: Library<12>-Footnote-243098451
Ref: Library<12>-Footnote-253098494
Ref: Library<12>-Footnote-263098550
Ref: Library<12>-Footnote-273098607
Ref: Library<12>-Footnote-283098664
Ref: Library<12>-Footnote-293098721
Ref: Library<12>-Footnote-303098778
Ref: Library<12>-Footnote-313098835
Ref: Library<12>-Footnote-323098892
Ref: Library<12>-Footnote-333098949
Ref: Library<12>-Footnote-343099006
Ref: Library<12>-Footnote-353099063
Ref: Library<12>-Footnote-363099120
Ref: Library<12>-Footnote-373099177
Ref: Library<12>-Footnote-383099233
Ref: Library<12>-Footnote-393099290
Ref: Library<12>-Footnote-403099347
Ref: Library<12>-Footnote-413099404
Ref: Library<12>-Footnote-423099461
Ref: Library<12>-Footnote-433099518
Ref: Library<12>-Footnote-443099575
Ref: Library<12>-Footnote-453099632
Ref: Library<12>-Footnote-463099689
Ref: Library<12>-Footnote-473099746
Ref: Library<12>-Footnote-483099803
Ref: Library<12>-Footnote-493099860
Ref: Library<12>-Footnote-503099917
Ref: Library<12>-Footnote-513099973
Ref: Library<12>-Footnote-523100030
Ref: Library<12>-Footnote-533100086
Ref: Library<12>-Footnote-543100143
Ref: Library<12>-Footnote-553100200
Ref: Library<12>-Footnote-563100257
Ref: Library<12>-Footnote-573100314
Ref: Library<12>-Footnote-583100371
Ref: Library<12>-Footnote-593100428
Ref: Library<12>-Footnote-603100485
Ref: Library<12>-Footnote-613100542
Ref: Library<12>-Footnote-623100599
Ref: Library<12>-Footnote-633100656
Ref: Library<12>-Footnote-643100713
Ref: Library<12>-Footnote-653100770
Ref: Library<12>-Footnote-663100827
Ref: Library<12>-Footnote-673100884
Ref: Library<12>-Footnote-683100941
Ref: Library<12>-Footnote-693100998
Ref: Library<12>-Footnote-703101054
Ref: Library<12>-Footnote-713101111
Ref: Library<12>-Footnote-723101168
Ref: Library<12>-Footnote-733101225
Ref: Library<12>-Footnote-743101282
Ref: Library<12>-Footnote-753101339
Ref: Library<12>-Footnote-763101395
Ref: Library<12>-Footnote-773101452
Ref: Library<12>-Footnote-783101509
Ref: Library<12>-Footnote-793101566
Ref: Library<12>-Footnote-803101623
Ref: Library<12>-Footnote-813101680
Ref: Library<12>-Footnote-823101737
Ref: Library<12>-Footnote-833101794
Ref: Library<12>-Footnote-843101850
Ref: Library<12>-Footnote-853101906
Ref: Library<12>-Footnote-863101962
Ref: Library<12>-Footnote-873102018
Ref: Library<12>-Footnote-883102075
Ref: Library<12>-Footnote-893102132
Ref: Library<12>-Footnote-903102189
Ref: Library<12>-Footnote-913102246
Ref: Library<12>-Footnote-923102303
Ref: Library<12>-Footnote-933102359
Ref: Library<12>-Footnote-943102416
Ref: Library<12>-Footnote-953102473
Ref: Library<12>-Footnote-963102530
Ref: Library<12>-Footnote-973102586
Ref: Library<12>-Footnote-983102643
Ref: Library<12>-Footnote-993102700
Ref: Library<12>-Footnote-1003102757
Ref: Library<12>-Footnote-1013102815
Ref: Library<12>-Footnote-1023102873
Ref: Library<12>-Footnote-1033102931
Ref: Library<12>-Footnote-1043102989
Ref: Library<12>-Footnote-1053103047
Ref: Library<12>-Footnote-1063103105
Ref: Library<12>-Footnote-1073103163
Ref: Library<12>-Footnote-1083103220
Ref: Library<12>-Footnote-1093103278
Ref: Library<12>-Footnote-1103103335
Ref: Library<12>-Footnote-1113103393
Ref: Library<12>-Footnote-1123103450
Ref: Library<12>-Footnote-1133103507
Ref: Library<12>-Footnote-1143103564
Ref: Library<12>-Footnote-1153103622
Ref: Library<12>-Footnote-1163103680
Ref: Library<12>-Footnote-1173103738
Ref: Library<12>-Footnote-1183103796
Ref: Library<12>-Footnote-1193103854
Ref: Library<12>-Footnote-1203103912
Ref: Library<12>-Footnote-1213103970
Ref: Library<12>-Footnote-1223104028
Ref: Library<12>-Footnote-1233104086
Ref: Library<12>-Footnote-1243104144
Ref: Library<12>-Footnote-1253104202
Ref: Library<12>-Footnote-1263104260
Ref: Library<12>-Footnote-1273104318
Ref: Library<12>-Footnote-1283104376
Ref: Library<12>-Footnote-1293104434
Ref: Library<12>-Footnote-1303104492
Ref: Library<12>-Footnote-1313104550
Ref: Library<12>-Footnote-1323104608
Ref: Library<12>-Footnote-1333104666
Ref: Library<12>-Footnote-1343104724
Ref: Library<12>-Footnote-1353104782
Ref: Library<12>-Footnote-1363104839
Ref: Library<12>-Footnote-1373104897
Ref: Library<12>-Footnote-1383104955
Ref: Library<12>-Footnote-1393105013
Ref: Library<12>-Footnote-1403105071
Ref: Library<12>-Footnote-1413105129
Ref: Library<12>-Footnote-1423105187
Ref: Library<12>-Footnote-1433105245
Ref: Library<12>-Footnote-1443105303
Ref: Library<12>-Footnote-1453105361
Ref: Library<12>-Footnote-1463105419
Ref: Library<12>-Footnote-1473105477
Ref: Library<12>-Footnote-1483105535
Ref: Library<12>-Footnote-1493105593
Ref: Library<12>-Footnote-1503105650
Ref: Library<12>-Footnote-1513105708
Ref: Library<12>-Footnote-1523105765
Ref: Library<12>-Footnote-1533105823
Ref: Library<12>-Footnote-1543105881
Ref: Library<12>-Footnote-1553105939
Ref: Library<12>-Footnote-1563105997
Ref: Library<12>-Footnote-1573106055
Ref: Library<12>-Footnote-1583106113
Ref: Library<12>-Footnote-1593106171
Ref: Library<12>-Footnote-1603106229
Ref: Library<12>-Footnote-1613106287
Ref: Library<12>-Footnote-1623106345
Ref: Library<12>-Footnote-1633106403
Ref: Library<12>-Footnote-1643106461
Ref: Library<12>-Footnote-1653106519
Ref: Library<12>-Footnote-1663106577
Ref: Library<12>-Footnote-1673106634
Ref: Library<12>-Footnote-1683106691
Ref: Library<12>-Footnote-1693106749
Ref: Library<12>-Footnote-1703106807
Ref: Library<12>-Footnote-1713106865
Ref: Library<12>-Footnote-1723106923
Ref: Library<12>-Footnote-1733106967
Ref: Library<12>-Footnote-1743107025
Ref: Library<12>-Footnote-1753107083
Ref: Library<12>-Footnote-1763107141
Ref: Library<12>-Footnote-1773107199
Ref: Library<12>-Footnote-1783107257
Ref: Library<12>-Footnote-1793107315
Ref: Library<12>-Footnote-1803107373
Ref: Library<12>-Footnote-1813107431
Ref: Library<12>-Footnote-1823107489
Ref: Library<12>-Footnote-1833107547
Ref: Library<12>-Footnote-1843107605
Ref: Library<12>-Footnote-1853107663
Ref: Library<12>-Footnote-1863107721
Ref: Library<12>-Footnote-1873107779
Ref: Library<12>-Footnote-1883107837
Ref: Library<12>-Footnote-1893107895
Ref: Library<12>-Footnote-1903107953
Ref: Library<12>-Footnote-1913108011
Ref: Library<12>-Footnote-1923108069
Ref: Library<12>-Footnote-1933108127
Ref: Library<12>-Footnote-1943108185
Ref: Library<12>-Footnote-1953108243
Ref: Library<12>-Footnote-1963108301
Ref: Library<12>-Footnote-1973108359
Ref: Library<12>-Footnote-1983108416
Ref: Library<12>-Footnote-1993108474
Ref: Library<12>-Footnote-2003108532
Ref: Library<12>-Footnote-2013108590
Ref: Library<12>-Footnote-2023108648
Ref: Library<12>-Footnote-2033108706
Ref: Library<12>-Footnote-2043108764
Ref: Library<12>-Footnote-2053108822
Ref: Library<12>-Footnote-2063108879
Ref: Library<12>-Footnote-2073108937
Ref: Library<12>-Footnote-2083108995
Ref: Library<12>-Footnote-2093109053
Ref: Library<12>-Footnote-2103109111
Ref: Library<12>-Footnote-2113109168
Ref: Library<12>-Footnote-2123109226
Ref: Library<12>-Footnote-2133109284
Ref: Library<12>-Footnote-2143109342
Ref: Library<12>-Footnote-2153109400
Ref: Library<12>-Footnote-2163109458
Ref: Library<12>-Footnote-2173109516
Ref: Library<12>-Footnote-2183109574
Ref: Library<12>-Footnote-2193109618
Ref: Library<12>-Footnote-2203109676
Ref: Library<12>-Footnote-2213109720
Ref: Library<12>-Footnote-2223109778
Ref: Library<12>-Footnote-2233109822
Ref: Library<12>-Footnote-2243109880
Ref: Library<12>-Footnote-2253109924
Ref: Library<12>-Footnote-2263109982
Ref: Library<12>-Footnote-2273110026
Ref: Library<12>-Footnote-2283110084
Ref: Library<12>-Footnote-2293110128
Ref: Library<12>-Footnote-2303110186
Ref: Library<12>-Footnote-2313110244
Ref: Library<12>-Footnote-2323110288
Ref: Library<12>-Footnote-2333110346
Ref: Library<12>-Footnote-2343110390
Ref: Library<12>-Footnote-2353110448
Ref: Library<12>-Footnote-2363110506
Ref: Library<12>-Footnote-2373110564
Ref: Library<12>-Footnote-2383110622
Ref: Library<12>-Footnote-2393110666
Ref: Library<12>-Footnote-2403110724
Ref: Library<12>-Footnote-2413110768
Ref: Library<12>-Footnote-2423110815
Ref: Library<12>-Footnote-2433110872
Ref: Library<12>-Footnote-2443110930
Ref: Library<12>-Footnote-2453110974
Ref: Library<12>-Footnote-2463111032
Ref: Library<12>-Footnote-2473111076
Ref: Library<12>-Footnote-2483111134
Ref: Library<12>-Footnote-2493111178
Ref: Library<12>-Footnote-2503111236
Ref: Library<12>-Footnote-2513111280
Ref: Library<12>-Footnote-2523111338
Ref: Library<12>-Footnote-2533111382
Ref: Library<12>-Footnote-2543111440
Ref: Library<12>-Footnote-2553111498
Ref: Library<12>-Footnote-2563111556
Ref: Library<12>-Footnote-2573111614
Ref: Library<12>-Footnote-2583111671
Ref: Library<12>-Footnote-2593111729
Ref: Library<12>-Footnote-2603111773
Ref: Library<12>-Footnote-2613111831
Ref: Library<12>-Footnote-2623111889
Ref: Library<12>-Footnote-2633111947
Ref: Library<12>-Footnote-2643112005
Ref: Library<12>-Footnote-2653112049
Ref: Library<12>-Footnote-2663112107
Ref: Library<12>-Footnote-2673112151
Ref: Library<12>-Footnote-2683112209
Ref: Library<12>-Footnote-2693112253
Ref: Library<12>-Footnote-2703112311
Ref: Library<12>-Footnote-2713112355
Ref: Library<12>-Footnote-2723112413
Ref: Library<12>-Footnote-2733112470
Ref: Library<12>-Footnote-2743112528
Ref: Library<12>-Footnote-2753112586
Ref: Library<12>-Footnote-2763112644
Ref: Library<12>-Footnote-2773112702
Ref: Library<12>-Footnote-2783112760
Ref: Library<12>-Footnote-2793112818
Ref: Library<12>-Footnote-2803112876
Ref: Library<12>-Footnote-2813112934
Ref: Library<12>-Footnote-2823112992
Ref: Library<12>-Footnote-2833113050
Ref: Library<12>-Footnote-2843113107
Ref: Library<12>-Footnote-2853113165
Ref: Library<12>-Footnote-2863113223
Ref: Library<12>-Footnote-2873113281
Ref: Library<12>-Footnote-2883113338
Ref: Library<12>-Footnote-2893113396
Ref: Library<12>-Footnote-2903113453
Ref: Library<12>-Footnote-2913113510
Ref: Library<12>-Footnote-2923113567
Ref: Library<12>-Footnote-2933113624
Ref: Library<12>-Footnote-2943113681
Ref: Library<12>-Footnote-2953113738
Ref: Library<12>-Footnote-2963113795
Ref: Library<12>-Footnote-2973113862
Ref: Library<12>-Footnote-2983113923
Ref: Library<12>-Footnote-2993113990
Ref: Library<12>-Footnote-3003114034
Ref: Library<12>-Footnote-3013114101
Ref: Library<12>-Footnote-3023114168
Ref: Library<12>-Footnote-3033114235
Ref: Library<12>-Footnote-3043114302
Node: Documentation<7>3114369
Ref: whatsnew/changelog id873114481
Ref: 16073114481
Ref: Documentation<7>-Footnote-13116433
Ref: Documentation<7>-Footnote-23116489
Ref: Documentation<7>-Footnote-33116545
Ref: Documentation<7>-Footnote-43116601
Ref: Documentation<7>-Footnote-53116657
Ref: Documentation<7>-Footnote-63116713
Ref: Documentation<7>-Footnote-73116769
Ref: Documentation<7>-Footnote-83116825
Ref: Documentation<7>-Footnote-93116881
Ref: Documentation<7>-Footnote-103116936
Ref: Documentation<7>-Footnote-113116992
Ref: Documentation<7>-Footnote-123117049
Ref: Documentation<7>-Footnote-133117105
Ref: Documentation<7>-Footnote-143117162
Node: Tests<10>3117219
Ref: whatsnew/changelog id883117329
Ref: 160a3117329
Ref: Tests<10>-Footnote-13130459
Ref: Tests<10>-Footnote-23130515
Ref: Tests<10>-Footnote-33130571
Ref: Tests<10>-Footnote-43130627
Ref: Tests<10>-Footnote-53130683
Ref: Tests<10>-Footnote-63130738
Ref: Tests<10>-Footnote-73130794
Ref: Tests<10>-Footnote-83130850
Ref: Tests<10>-Footnote-93130906
Ref: Tests<10>-Footnote-103130962
Ref: Tests<10>-Footnote-113131019
Ref: Tests<10>-Footnote-123131076
Ref: Tests<10>-Footnote-133131133
Ref: Tests<10>-Footnote-143131190
Ref: Tests<10>-Footnote-153131247
Ref: Tests<10>-Footnote-163131304
Ref: Tests<10>-Footnote-173131361
Ref: Tests<10>-Footnote-183131418
Ref: Tests<10>-Footnote-193131475
Ref: Tests<10>-Footnote-203131532
Ref: Tests<10>-Footnote-213131589
Ref: Tests<10>-Footnote-223131646
Ref: Tests<10>-Footnote-233131703
Ref: Tests<10>-Footnote-243131760
Ref: Tests<10>-Footnote-253131817
Ref: Tests<10>-Footnote-263131874
Ref: Tests<10>-Footnote-273131931
Ref: Tests<10>-Footnote-283131988
Ref: Tests<10>-Footnote-293132045
Ref: Tests<10>-Footnote-303132102
Ref: Tests<10>-Footnote-313132159
Ref: Tests<10>-Footnote-323132216
Ref: Tests<10>-Footnote-333132273
Ref: Tests<10>-Footnote-343132317
Ref: Tests<10>-Footnote-353132373
Ref: Tests<10>-Footnote-363132430
Ref: Tests<10>-Footnote-373132486
Ref: Tests<10>-Footnote-383132542
Ref: Tests<10>-Footnote-393132599
Ref: Tests<10>-Footnote-403132656
Ref: Tests<10>-Footnote-413132713
Ref: Tests<10>-Footnote-423132770
Ref: Tests<10>-Footnote-433132827
Ref: Tests<10>-Footnote-443132884
Ref: Tests<10>-Footnote-453132941
Ref: Tests<10>-Footnote-463132998
Ref: Tests<10>-Footnote-473133055
Ref: Tests<10>-Footnote-483133112
Ref: Tests<10>-Footnote-493133169
Ref: Tests<10>-Footnote-503133226
Ref: Tests<10>-Footnote-513133283
Ref: Tests<10>-Footnote-523133340
Ref: Tests<10>-Footnote-533133397
Ref: Tests<10>-Footnote-543133454
Ref: Tests<10>-Footnote-553133511
Ref: Tests<10>-Footnote-563133568
Ref: Tests<10>-Footnote-573133625
Ref: Tests<10>-Footnote-583133681
Ref: Tests<10>-Footnote-593133738
Node: Build<12>3133794
Ref: whatsnew/changelog id893133898
Ref: 160c3133898
Ref: Build<12>-Footnote-13137885
Ref: Build<12>-Footnote-23137941
Ref: Build<12>-Footnote-33137997
Ref: Build<12>-Footnote-43138053
Ref: Build<12>-Footnote-53138109
Ref: Build<12>-Footnote-63138165
Ref: Build<12>-Footnote-73138221
Ref: Build<12>-Footnote-83138276
Ref: Build<12>-Footnote-93138332
Ref: Build<12>-Footnote-103138388
Ref: Build<12>-Footnote-113138444
Ref: Build<12>-Footnote-123138501
Ref: Build<12>-Footnote-133138558
Ref: Build<12>-Footnote-143138615
Ref: Build<12>-Footnote-153138672
Ref: Build<12>-Footnote-163138728
Ref: Build<12>-Footnote-173138785
Ref: Build<12>-Footnote-183138842
Ref: Build<12>-Footnote-193138899
Ref: Build<12>-Footnote-203138956
Ref: Build<12>-Footnote-213139012
Ref: Build<12>-Footnote-223139069
Ref: Build<12>-Footnote-233139125
Ref: Build<12>-Footnote-243139182
Node: Windows<9>3139239
Ref: whatsnew/changelog id903139342
Ref: 160e3139342
Ref: Windows<9>-Footnote-13141852
Ref: Windows<9>-Footnote-23141908
Ref: Windows<9>-Footnote-33141964
Ref: Windows<9>-Footnote-43142019
Ref: Windows<9>-Footnote-53142075
Ref: Windows<9>-Footnote-63142131
Ref: Windows<9>-Footnote-73142186
Ref: Windows<9>-Footnote-83142242
Ref: Windows<9>-Footnote-93142298
Ref: Windows<9>-Footnote-103142354
Ref: Windows<9>-Footnote-113142411
Ref: Windows<9>-Footnote-123142467
Ref: Windows<9>-Footnote-133142524
Node: macOS<7>3142581
Ref: whatsnew/changelog id913142683
Ref: 160f3142683
Ref: macOS<7>-Footnote-13142947
Ref: macOS<7>-Footnote-23143003
Ref: macOS<7>-Footnote-33143059
Node: IDLE<11>3143114
Ref: whatsnew/changelog id923143220
Ref: 16103143220
Ref: IDLE<11>-Footnote-13143409
Node: Tools/Demos<5>3143465
Ref: whatsnew/changelog id933143572
Ref: 16113143572
Ref: Tools/Demos<5>-Footnote-13146086
Ref: Tools/Demos<5>-Footnote-23146142
Ref: Tools/Demos<5>-Footnote-33146198
Ref: Tools/Demos<5>-Footnote-43146260
Ref: Tools/Demos<5>-Footnote-53146349
Ref: Tools/Demos<5>-Footnote-63146405
Ref: Tools/Demos<5>-Footnote-73146499
Ref: Tools/Demos<5>-Footnote-83146555
Ref: Tools/Demos<5>-Footnote-93146611
Ref: Tools/Demos<5>-Footnote-103146666
Ref: Tools/Demos<5>-Footnote-113146762
Ref: Tools/Demos<5>-Footnote-123146819
Ref: Tools/Demos<5>-Footnote-133146876
Ref: Tools/Demos<5>-Footnote-143146933
Ref: Tools/Demos<5>-Footnote-153146990
Ref: Tools/Demos<5>-Footnote-163147047
Ref: Tools/Demos<5>-Footnote-173147104
Ref: Tools/Demos<5>-Footnote-183147160
Node: C API<12>3147258
Ref: whatsnew/changelog id943147348
Ref: 16123147348
Ref: C API<12>-Footnote-13162260
Ref: C API<12>-Footnote-23162315
Ref: C API<12>-Footnote-33162371
Ref: C API<12>-Footnote-43162427
Ref: C API<12>-Footnote-53162483
Ref: C API<12>-Footnote-63162539
Ref: C API<12>-Footnote-73162595
Ref: C API<12>-Footnote-83162650
Ref: C API<12>-Footnote-93162706
Ref: C API<12>-Footnote-103162762
Ref: C API<12>-Footnote-113162819
Ref: C API<12>-Footnote-123162876
Ref: C API<12>-Footnote-133162933
Ref: C API<12>-Footnote-143162990
Ref: C API<12>-Footnote-153163047
Ref: C API<12>-Footnote-163163104
Ref: C API<12>-Footnote-173163161
Ref: C API<12>-Footnote-183163218
Ref: C API<12>-Footnote-193163275
Ref: C API<12>-Footnote-203163332
Ref: C API<12>-Footnote-213163389
Ref: C API<12>-Footnote-223163446
Ref: C API<12>-Footnote-233163503
Ref: C API<12>-Footnote-243163560
Ref: C API<12>-Footnote-253163617
Ref: C API<12>-Footnote-263163674
Ref: C API<12>-Footnote-273163731
Ref: C API<12>-Footnote-283163788
Ref: C API<12>-Footnote-293163845
Ref: C API<12>-Footnote-303163902
Ref: C API<12>-Footnote-313163959
Ref: C API<12>-Footnote-323164016
Ref: C API<12>-Footnote-333164059
Ref: C API<12>-Footnote-343164116
Ref: C API<12>-Footnote-353164173
Ref: C API<12>-Footnote-363164230
Ref: C API<12>-Footnote-373164287
Ref: C API<12>-Footnote-383164344
Ref: C API<12>-Footnote-393164401
Ref: C API<12>-Footnote-403164458
Ref: C API<12>-Footnote-413164515
Ref: C API<12>-Footnote-423164572
Ref: C API<12>-Footnote-433164629
Ref: C API<12>-Footnote-443164686
Ref: C API<12>-Footnote-453164743
Ref: C API<12>-Footnote-463164800
Ref: C API<12>-Footnote-473164857
Ref: C API<12>-Footnote-483164914
Ref: C API<12>-Footnote-493164971
Ref: C API<12>-Footnote-503165027
Ref: C API<12>-Footnote-513165084
Ref: C API<12>-Footnote-523165141
Ref: C API<12>-Footnote-533165198
Ref: C API<12>-Footnote-543165255
Ref: C API<12>-Footnote-553165312
Ref: C API<12>-Footnote-563165369
Ref: C API<12>-Footnote-573165426
Ref: C API<12>-Footnote-583165483
Ref: C API<12>-Footnote-593165549
Node: Python 3 12 0 beta 13165615
Ref: whatsnew/changelog python-3-12-0-beta-13165759
Ref: 161e3165759
Node: Security<9>3166136
Ref: whatsnew/changelog id953166234
Ref: 161f3166234
Ref: Security<9>-Footnote-13167053
Ref: Security<9>-Footnote-23167108
Ref: Security<9>-Footnote-33167164
Ref: Security<9>-Footnote-43167219
Ref: Security<9>-Footnote-53167275
Node: Core and Builtins<14>3167345
Ref: whatsnew/changelog id963167463
Ref: 16203167463
Ref: Core and Builtins<14>-Footnote-13178440
Ref: Core and Builtins<14>-Footnote-23178496
Ref: Core and Builtins<14>-Footnote-33178552
Ref: Core and Builtins<14>-Footnote-43178608
Ref: Core and Builtins<14>-Footnote-53178650
Ref: Core and Builtins<14>-Footnote-63178706
Ref: Core and Builtins<14>-Footnote-73178762
Ref: Core and Builtins<14>-Footnote-83178818
Ref: Core and Builtins<14>-Footnote-93178860
Ref: Core and Builtins<14>-Footnote-103178916
Ref: Core and Builtins<14>-Footnote-113178973
Ref: Core and Builtins<14>-Footnote-123179029
Ref: Core and Builtins<14>-Footnote-133179085
Ref: Core and Builtins<14>-Footnote-143179142
Ref: Core and Builtins<14>-Footnote-153179199
Ref: Core and Builtins<14>-Footnote-163179242
Ref: Core and Builtins<14>-Footnote-173179299
Ref: Core and Builtins<14>-Footnote-183179356
Ref: Core and Builtins<14>-Footnote-193179413
Ref: Core and Builtins<14>-Footnote-203179470
Ref: Core and Builtins<14>-Footnote-213179527
Ref: Core and Builtins<14>-Footnote-223179584
Ref: Core and Builtins<14>-Footnote-233179641
Ref: Core and Builtins<14>-Footnote-243179698
Ref: Core and Builtins<14>-Footnote-253179755
Ref: Core and Builtins<14>-Footnote-263179812
Ref: Core and Builtins<14>-Footnote-273179855
Ref: Core and Builtins<14>-Footnote-283179912
Ref: Core and Builtins<14>-Footnote-293179969
Ref: Core and Builtins<14>-Footnote-303180026
Ref: Core and Builtins<14>-Footnote-313180083
Ref: Core and Builtins<14>-Footnote-323180140
Ref: Core and Builtins<14>-Footnote-333180197
Ref: Core and Builtins<14>-Footnote-343180254
Ref: Core and Builtins<14>-Footnote-353180311
Ref: Core and Builtins<14>-Footnote-363180368
Ref: Core and Builtins<14>-Footnote-373180424
Ref: Core and Builtins<14>-Footnote-383180481
Ref: Core and Builtins<14>-Footnote-393180537
Ref: Core and Builtins<14>-Footnote-403180593
Ref: Core and Builtins<14>-Footnote-413180636
Ref: Core and Builtins<14>-Footnote-423180693
Ref: Core and Builtins<14>-Footnote-433180750
Ref: Core and Builtins<14>-Footnote-443180807
Ref: Core and Builtins<14>-Footnote-453180863
Ref: Core and Builtins<14>-Footnote-463180920
Ref: Core and Builtins<14>-Footnote-473180977
Ref: Core and Builtins<14>-Footnote-483181020
Ref: Core and Builtins<14>-Footnote-493181076
Ref: Core and Builtins<14>-Footnote-503181133
Ref: Core and Builtins<14>-Footnote-513181176
Ref: Core and Builtins<14>-Footnote-523181232
Ref: Core and Builtins<14>-Footnote-533181275
Ref: Core and Builtins<14>-Footnote-543181331
Ref: Core and Builtins<14>-Footnote-553181387
Ref: Core and Builtins<14>-Footnote-563181453
Node: Library<13>3181519
Ref: whatsnew/changelog id973181642
Ref: 16213181642
Ref: Library<13>-Footnote-13205111
Ref: Library<13>-Footnote-23205167
Ref: Library<13>-Footnote-33205209
Ref: Library<13>-Footnote-43205265
Ref: Library<13>-Footnote-53205321
Ref: Library<13>-Footnote-63205377
Ref: Library<13>-Footnote-73205433
Ref: Library<13>-Footnote-83205488
Ref: Library<13>-Footnote-93205544
Ref: Library<13>-Footnote-103205600
Ref: Library<13>-Footnote-113205657
Ref: Library<13>-Footnote-123205714
Ref: Library<13>-Footnote-133205771
Ref: Library<13>-Footnote-143205828
Ref: Library<13>-Footnote-153205885
Ref: Library<13>-Footnote-163205942
Ref: Library<13>-Footnote-173206018
Ref: Library<13>-Footnote-183206075
Ref: Library<13>-Footnote-193206132
Ref: Library<13>-Footnote-203206188
Ref: Library<13>-Footnote-213206245
Ref: Library<13>-Footnote-223206311
Ref: Library<13>-Footnote-233206368
Ref: Library<13>-Footnote-243206424
Ref: Library<13>-Footnote-253206480
Ref: Library<13>-Footnote-263206537
Ref: Library<13>-Footnote-273206594
Ref: Library<13>-Footnote-283206651
Ref: Library<13>-Footnote-293206708
Ref: Library<13>-Footnote-303206765
Ref: Library<13>-Footnote-313206822
Ref: Library<13>-Footnote-323206879
Ref: Library<13>-Footnote-333206922
Ref: Library<13>-Footnote-343206979
Ref: Library<13>-Footnote-353207036
Ref: Library<13>-Footnote-363207093
Ref: Library<13>-Footnote-373207150
Ref: Library<13>-Footnote-383207206
Ref: Library<13>-Footnote-393207263
Ref: Library<13>-Footnote-403207319
Ref: Library<13>-Footnote-413207376
Ref: Library<13>-Footnote-423207433
Ref: Library<13>-Footnote-433207490
Ref: Library<13>-Footnote-443207547
Ref: Library<13>-Footnote-453207604
Ref: Library<13>-Footnote-463207661
Ref: Library<13>-Footnote-473207717
Ref: Library<13>-Footnote-483207773
Ref: Library<13>-Footnote-493207830
Ref: Library<13>-Footnote-503207887
Ref: Library<13>-Footnote-513207944
Ref: Library<13>-Footnote-523208001
Ref: Library<13>-Footnote-533208057
Ref: Library<13>-Footnote-543208114
Ref: Library<13>-Footnote-553208170
Ref: Library<13>-Footnote-563208227
Ref: Library<13>-Footnote-573208284
Ref: Library<13>-Footnote-583208340
Ref: Library<13>-Footnote-593208396
Ref: Library<13>-Footnote-603208453
Ref: Library<13>-Footnote-613208510
Ref: Library<13>-Footnote-623208566
Ref: Library<13>-Footnote-633208623
Ref: Library<13>-Footnote-643208680
Ref: Library<13>-Footnote-653208737
Ref: Library<13>-Footnote-663208794
Ref: Library<13>-Footnote-673208851
Ref: Library<13>-Footnote-683208908
Ref: Library<13>-Footnote-693208965
Ref: Library<13>-Footnote-703209022
Ref: Library<13>-Footnote-713209079
Ref: Library<13>-Footnote-723209136
Ref: Library<13>-Footnote-733209193
Ref: Library<13>-Footnote-743209250
Ref: Library<13>-Footnote-753209307
Ref: Library<13>-Footnote-763209364
Ref: Library<13>-Footnote-773209421
Ref: Library<13>-Footnote-783209464
Ref: Library<13>-Footnote-793209521
Ref: Library<13>-Footnote-803209578
Ref: Library<13>-Footnote-813209621
Ref: Library<13>-Footnote-823209677
Ref: Library<13>-Footnote-833209733
Ref: Library<13>-Footnote-843209790
Ref: Library<13>-Footnote-853209847
Ref: Library<13>-Footnote-863209904
Ref: Library<13>-Footnote-873209961
Ref: Library<13>-Footnote-883210018
Ref: Library<13>-Footnote-893210061
Ref: Library<13>-Footnote-903210118
Ref: Library<13>-Footnote-913210161
Ref: Library<13>-Footnote-923210217
Ref: Library<13>-Footnote-933210274
Ref: Library<13>-Footnote-943210331
Ref: Library<13>-Footnote-953210374
Ref: Library<13>-Footnote-963210431
Ref: Library<13>-Footnote-973210488
Ref: Library<13>-Footnote-983210545
Ref: Library<13>-Footnote-993210601
Ref: Library<13>-Footnote-1003210658
Ref: Library<13>-Footnote-1013210716
Ref: Library<13>-Footnote-1023210774
Ref: Library<13>-Footnote-1033210832
Ref: Library<13>-Footnote-1043210890
Ref: Library<13>-Footnote-1053210948
Ref: Library<13>-Footnote-1063211005
Ref: Library<13>-Footnote-1073211062
Ref: Library<13>-Footnote-1083211120
Ref: Library<13>-Footnote-1093211164
Ref: Library<13>-Footnote-1103211221
Ref: Library<13>-Footnote-1113211279
Ref: Library<13>-Footnote-1123211337
Ref: Library<13>-Footnote-1133211394
Ref: Library<13>-Footnote-1143211451
Ref: Library<13>-Footnote-1153211508
Ref: Library<13>-Footnote-1163211566
Ref: Library<13>-Footnote-1173211624
Ref: Library<13>-Footnote-1183211681
Ref: Library<13>-Footnote-1193211738
Ref: Library<13>-Footnote-1203211795
Ref: Library<13>-Footnote-1213211852
Ref: Library<13>-Footnote-1223211909
Ref: Library<13>-Footnote-1233211966
Ref: Library<13>-Footnote-1243212023
Ref: Library<13>-Footnote-1253212080
Ref: Library<13>-Footnote-1263212137
Ref: Library<13>-Footnote-1273212194
Ref: Library<13>-Footnote-1283212251
Ref: Library<13>-Footnote-1293212308
Ref: Library<13>-Footnote-1303212365
Ref: Library<13>-Footnote-1313212422
Ref: Library<13>-Footnote-1323212479
Ref: Library<13>-Footnote-1333212546
Ref: Library<13>-Footnote-1343212613
Ref: Library<13>-Footnote-1353212680
Ref: Library<13>-Footnote-1363212747
Ref: Library<13>-Footnote-1373212814
Ref: Library<13>-Footnote-1383212881
Ref: Library<13>-Footnote-1393212948
Node: Documentation<8>3213015
Ref: whatsnew/changelog id983213126
Ref: 162e3213126
Ref: Documentation<8>-Footnote-13213899
Ref: Documentation<8>-Footnote-23213954
Ref: Documentation<8>-Footnote-33214010
Ref: Documentation<8>-Footnote-43214052
Ref: Documentation<8>-Footnote-53214107
Ref: Documentation<8>-Footnote-63214162
Node: Tests<11>3214217
Ref: whatsnew/changelog id993214326
Ref: 162f3214326
Ref: Tests<11>-Footnote-13215239
Ref: Tests<11>-Footnote-23215295
Ref: Tests<11>-Footnote-33215351
Ref: Tests<11>-Footnote-43215406
Ref: Tests<11>-Footnote-53215462
Ref: Tests<11>-Footnote-63215518
Node: Build<13>3215573
Ref: whatsnew/changelog id1003215677
Ref: 16313215677
Ref: Build<13>-Footnote-13217261
Ref: Build<13>-Footnote-23217317
Ref: Build<13>-Footnote-33217372
Ref: Build<13>-Footnote-43217428
Ref: Build<13>-Footnote-53217484
Ref: Build<13>-Footnote-63217540
Ref: Build<13>-Footnote-73217595
Ref: Build<13>-Footnote-83217650
Ref: Build<13>-Footnote-93217706
Node: Windows<10>3217761
Ref: whatsnew/changelog id1013217864
Ref: 16323217864
Ref: Windows<10>-Footnote-13218717
Ref: Windows<10>-Footnote-23218773
Ref: Windows<10>-Footnote-33218828
Ref: Windows<10>-Footnote-43218884
Ref: Windows<10>-Footnote-53218940
Ref: Windows<10>-Footnote-63218996
Node: macOS<8>3219051
Ref: whatsnew/changelog id1023219153
Ref: 16333219153
Ref: macOS<8>-Footnote-13219955
Ref: macOS<8>-Footnote-23220010
Ref: macOS<8>-Footnote-33220066
Ref: macOS<8>-Footnote-43220122
Ref: macOS<8>-Footnote-53220178
Ref: macOS<8>-Footnote-63220233
Node: IDLE<12>3220289
Ref: whatsnew/changelog id1033220394
Ref: 16343220394
Ref: IDLE<12>-Footnote-13220676
Ref: IDLE<12>-Footnote-23220732
Ref: IDLE<12>-Footnote-33220788
Node: Tools/Demos<6>3220843
Ref: whatsnew/changelog id1043220949
Ref: 16353220949
Ref: Tools/Demos<6>-Footnote-13221209
Node: C API<13>3221265
Ref: whatsnew/changelog id1053221354
Ref: 16363221354
Ref: C API<13>-Footnote-13224325
Ref: C API<13>-Footnote-23224381
Ref: C API<13>-Footnote-33224437
Ref: C API<13>-Footnote-43224493
Ref: C API<13>-Footnote-53224549
Ref: C API<13>-Footnote-63224605
Ref: C API<13>-Footnote-73224661
Ref: C API<13>-Footnote-83224703
Ref: C API<13>-Footnote-93224759
Ref: C API<13>-Footnote-103224815
Ref: C API<13>-Footnote-113224871
Node: Python 3 12 0 alpha 73224927
Ref: whatsnew/changelog python-3-12-0-alpha-73225071
Ref: 163d3225071
Node: Core and Builtins<15>3225388
Ref: whatsnew/changelog id1063225487
Ref: 163e3225487
Ref: Core and Builtins<15>-Footnote-13228620
Ref: Core and Builtins<15>-Footnote-23228676
Ref: Core and Builtins<15>-Footnote-33228731
Ref: Core and Builtins<15>-Footnote-43228787
Ref: Core and Builtins<15>-Footnote-53228843
Ref: Core and Builtins<15>-Footnote-63228899
Ref: Core and Builtins<15>-Footnote-73228955
Ref: Core and Builtins<15>-Footnote-83229011
Ref: Core and Builtins<15>-Footnote-93229067
Ref: Core and Builtins<15>-Footnote-103229123
Ref: Core and Builtins<15>-Footnote-113229179
Ref: Core and Builtins<15>-Footnote-123229236
Ref: Core and Builtins<15>-Footnote-133229293
Ref: Core and Builtins<15>-Footnote-143229350
Ref: Core and Builtins<15>-Footnote-153229407
Ref: Core and Builtins<15>-Footnote-163229450
Ref: Core and Builtins<15>-Footnote-173229507
Ref: Core and Builtins<15>-Footnote-183229564
Ref: Core and Builtins<15>-Footnote-193229621
Ref: Core and Builtins<15>-Footnote-203229678
Ref: Core and Builtins<15>-Footnote-213229735
Ref: Core and Builtins<15>-Footnote-223229792
Ref: Core and Builtins<15>-Footnote-233229860
Node: Library<14>3229903
Ref: whatsnew/changelog id1073230027
Ref: 16403230027
Ref: Library<14>-Footnote-13237846
Ref: Library<14>-Footnote-23237902
Ref: Library<14>-Footnote-33237958
Ref: Library<14>-Footnote-43238014
Ref: Library<14>-Footnote-53238070
Ref: Library<14>-Footnote-63238126
Ref: Library<14>-Footnote-73238182
Ref: Library<14>-Footnote-83238238
Ref: Library<14>-Footnote-93238294
Ref: Library<14>-Footnote-103238350
Ref: Library<14>-Footnote-113238407
Ref: Library<14>-Footnote-123238464
Ref: Library<14>-Footnote-133238521
Ref: Library<14>-Footnote-143238577
Ref: Library<14>-Footnote-153238633
Ref: Library<14>-Footnote-163238689
Ref: Library<14>-Footnote-173238746
Ref: Library<14>-Footnote-183238803
Ref: Library<14>-Footnote-193238860
Ref: Library<14>-Footnote-203238917
Ref: Library<14>-Footnote-213238974
Ref: Library<14>-Footnote-223239031
Ref: Library<14>-Footnote-233239087
Ref: Library<14>-Footnote-243239144
Ref: Library<14>-Footnote-253239200
Ref: Library<14>-Footnote-263239257
Ref: Library<14>-Footnote-273239314
Ref: Library<14>-Footnote-283239371
Ref: Library<14>-Footnote-293239427
Ref: Library<14>-Footnote-303239484
Ref: Library<14>-Footnote-313239541
Ref: Library<14>-Footnote-323239598
Ref: Library<14>-Footnote-333239654
Ref: Library<14>-Footnote-343239711
Ref: Library<14>-Footnote-353239767
Ref: Library<14>-Footnote-363239823
Ref: Library<14>-Footnote-373239879
Ref: Library<14>-Footnote-383239935
Ref: Library<14>-Footnote-393239991
Ref: Library<14>-Footnote-403240047
Ref: Library<14>-Footnote-413240103
Node: Documentation<9>3240169
Ref: whatsnew/changelog id1083240281
Ref: 16493240281
Ref: Documentation<9>-Footnote-13240480
Node: Tests<12>3240536
Ref: whatsnew/changelog id1093240646
Ref: 164b3240646
Ref: Tests<12>-Footnote-13241003
Ref: Tests<12>-Footnote-23241059
Ref: Tests<12>-Footnote-33241115
Node: Build<14>3241171
Ref: whatsnew/changelog id1103241276
Ref: 164c3241276
Ref: Build<14>-Footnote-13241522
Ref: Build<14>-Footnote-23241578
Node: Windows<11>3241634
Ref: whatsnew/changelog id1113241744
Ref: 164d3241744
Ref: Windows<11>-Footnote-13242041
Ref: Windows<11>-Footnote-23242097
Node: Tools/Demos<7>3242152
Ref: whatsnew/changelog id1123242262
Ref: 164e3242262
Ref: Tools/Demos<7>-Footnote-13242395
Node: C API<14>3242451
Ref: whatsnew/changelog id1133242541
Ref: 164f3242541
Ref: C API<14>-Footnote-13242755
Node: Python 3 12 0 alpha 63242811
Ref: whatsnew/changelog python-3-12-0-alpha-63242956
Ref: 16503242956
Node: Security<10>3243288
Ref: whatsnew/changelog id1143243388
Ref: 16513243388
Ref: Security<10>-Footnote-13244326
Ref: Security<10>-Footnote-23244381
Ref: Security<10>-Footnote-33244437
Ref: Security<10>-Footnote-43244506
Ref: Security<10>-Footnote-53244575
Ref: Security<10>-Footnote-63244644
Ref: Security<10>-Footnote-73244701
Ref: Security<10>-Footnote-83244756
Ref: Security<10>-Footnote-93244804
Node: Core and Builtins<16>3244860
Ref: whatsnew/changelog id1153244980
Ref: 16523244980
Ref: Core and Builtins<16>-Footnote-13248614
Ref: Core and Builtins<16>-Footnote-23248670
Ref: Core and Builtins<16>-Footnote-33248726
Ref: Core and Builtins<16>-Footnote-43248782
Ref: Core and Builtins<16>-Footnote-53248838
Ref: Core and Builtins<16>-Footnote-63248894
Ref: Core and Builtins<16>-Footnote-73248950
Ref: Core and Builtins<16>-Footnote-83249006
Ref: Core and Builtins<16>-Footnote-93249062
Ref: Core and Builtins<16>-Footnote-103249118
Ref: Core and Builtins<16>-Footnote-113249175
Ref: Core and Builtins<16>-Footnote-123249232
Ref: Core and Builtins<16>-Footnote-133249288
Ref: Core and Builtins<16>-Footnote-143249345
Ref: Core and Builtins<16>-Footnote-153249402
Ref: Core and Builtins<16>-Footnote-163249458
Ref: Core and Builtins<16>-Footnote-173249514
Ref: Core and Builtins<16>-Footnote-183249571
Ref: Core and Builtins<16>-Footnote-193249628
Ref: Core and Builtins<16>-Footnote-203249685
Ref: Core and Builtins<16>-Footnote-213249742
Ref: Core and Builtins<16>-Footnote-223249799
Node: Library<15>3249855
Ref: whatsnew/changelog id1163249980
Ref: 16563249980
Ref: Library<15>-Footnote-13255804
Ref: Library<15>-Footnote-23255860
Ref: Library<15>-Footnote-33255916
Ref: Library<15>-Footnote-43255971
Ref: Library<15>-Footnote-53256026
Ref: Library<15>-Footnote-63256082
Ref: Library<15>-Footnote-73256138
Ref: Library<15>-Footnote-83256194
Ref: Library<15>-Footnote-93256250
Ref: Library<15>-Footnote-103256317
Ref: Library<15>-Footnote-113256373
Ref: Library<15>-Footnote-123256457
Ref: Library<15>-Footnote-133256514
Ref: Library<15>-Footnote-143256570
Ref: Library<15>-Footnote-153256627
Ref: Library<15>-Footnote-163256683
Ref: Library<15>-Footnote-173256739
Ref: Library<15>-Footnote-183256796
Ref: Library<15>-Footnote-193256853
Ref: Library<15>-Footnote-203256910
Ref: Library<15>-Footnote-213256967
Ref: Library<15>-Footnote-223257024
Ref: Library<15>-Footnote-233257081
Ref: Library<15>-Footnote-243257138
Ref: Library<15>-Footnote-253257194
Ref: Library<15>-Footnote-263257251
Ref: Library<15>-Footnote-273257294
Ref: Library<15>-Footnote-283257350
Ref: Library<15>-Footnote-293257407
Ref: Library<15>-Footnote-303257464
Ref: Library<15>-Footnote-313257507
Ref: Library<15>-Footnote-323257564
Ref: Library<15>-Footnote-333257620
Ref: Library<15>-Footnote-343257663
Ref: Library<15>-Footnote-353257719
Ref: Library<15>-Footnote-363257775
Node: Documentation<10>3257841
Ref: whatsnew/changelog id1173257954
Ref: 16603257954
Ref: Documentation<10>-Footnote-13258263
Ref: Documentation<10>-Footnote-23258318
Node: Tests<13>3258373
Ref: whatsnew/changelog id1183258484
Ref: 16623258484
Ref: Tests<13>-Footnote-13259056
Ref: Tests<13>-Footnote-23259112
Ref: Tests<13>-Footnote-33259167
Node: Build<15>3259222
Ref: whatsnew/changelog id1193259327
Ref: 16633259327
Ref: Build<15>-Footnote-13260006
Ref: Build<15>-Footnote-23260061
Ref: Build<15>-Footnote-33260116
Ref: Build<15>-Footnote-43260172
Node: Windows<12>3260227
Ref: whatsnew/changelog id1203260331
Ref: 16653260331
Ref: Windows<12>-Footnote-13261350
Ref: Windows<12>-Footnote-23261406
Ref: Windows<12>-Footnote-33261462
Ref: Windows<12>-Footnote-43261518
Ref: Windows<12>-Footnote-53261574
Ref: Windows<12>-Footnote-63261630
Ref: Windows<12>-Footnote-73261686
Ref: Windows<12>-Footnote-83261742
Node: macOS<9>3261798
Ref: whatsnew/changelog id1213261902
Ref: 16663261902
Ref: macOS<9>-Footnote-13262032
Node: C API<15>3262088
Ref: whatsnew/changelog id1223262172
Ref: 16673262172
Ref: C API<15>-Footnote-13263267
Ref: C API<15>-Footnote-23263323
Ref: C API<15>-Footnote-33263378
Ref: C API<15>-Footnote-43263434
Ref: C API<15>-Footnote-53263489
Node: Python 3 12 0 alpha 53263531
Ref: whatsnew/changelog python-3-12-0-alpha-53263676
Ref: 16683263676
Node: Security<11>3263969
Ref: whatsnew/changelog id1233264069
Ref: 16693264069
Ref: Security<11>-Footnote-13264447
Ref: Security<11>-Footnote-23264502
Node: Core and Builtins<17>3264550
Ref: whatsnew/changelog id1253264670
Ref: 166a3264670
Ref: Core and Builtins<17>-Footnote-13267768
Ref: Core and Builtins<17>-Footnote-23267823
Ref: Core and Builtins<17>-Footnote-33267878
Ref: Core and Builtins<17>-Footnote-43267934
Ref: Core and Builtins<17>-Footnote-53267990
Ref: Core and Builtins<17>-Footnote-63268046
Ref: Core and Builtins<17>-Footnote-73268102
Ref: Core and Builtins<17>-Footnote-83268158
Ref: Core and Builtins<17>-Footnote-93268214
Ref: Core and Builtins<17>-Footnote-103268270
Ref: Core and Builtins<17>-Footnote-113268327
Ref: Core and Builtins<17>-Footnote-123268384
Ref: Core and Builtins<17>-Footnote-133268441
Ref: Core and Builtins<17>-Footnote-143268498
Ref: Core and Builtins<17>-Footnote-153268554
Ref: Core and Builtins<17>-Footnote-163268611
Ref: Core and Builtins<17>-Footnote-173268668
Node: Library<16>3268734
Ref: whatsnew/changelog id1263268859
Ref: 166e3268859
Ref: Library<16>-Footnote-13273912
Ref: Library<16>-Footnote-23273968
Ref: Library<16>-Footnote-33274024
Ref: Library<16>-Footnote-43274080
Ref: Library<16>-Footnote-53274136
Ref: Library<16>-Footnote-63274192
Ref: Library<16>-Footnote-73274247
Ref: Library<16>-Footnote-83274289
Ref: Library<16>-Footnote-93274345
Ref: Library<16>-Footnote-103274401
Ref: Library<16>-Footnote-113274458
Ref: Library<16>-Footnote-123274514
Ref: Library<16>-Footnote-133274571
Ref: Library<16>-Footnote-143274628
Ref: Library<16>-Footnote-153274685
Ref: Library<16>-Footnote-163274741
Ref: Library<16>-Footnote-173274798
Ref: Library<16>-Footnote-183274855
Ref: Library<16>-Footnote-193274911
Ref: Library<16>-Footnote-203274967
Ref: Library<16>-Footnote-213275023
Ref: Library<16>-Footnote-223275079
Ref: Library<16>-Footnote-233275135
Ref: Library<16>-Footnote-243275191
Ref: Library<16>-Footnote-253275247
Ref: Library<16>-Footnote-263275303
Ref: Library<16>-Footnote-273275369
Ref: Library<16>-Footnote-283275435
Ref: Library<16>-Footnote-293275501
Node: Documentation<11>3275557
Ref: whatsnew/changelog id1273275670
Ref: 16783275670
Ref: Documentation<11>-Footnote-13275955
Node: Tests<14>3276010
Ref: whatsnew/changelog id1283276121
Ref: 16793276121
Ref: Tests<14>-Footnote-13276283
Node: Build<16>3276339
Ref: whatsnew/changelog id1293276444
Ref: 167a3276444
Ref: Build<16>-Footnote-13277883
Ref: Build<16>-Footnote-23277939
Ref: Build<16>-Footnote-33277995
Ref: Build<16>-Footnote-43278050
Ref: Build<16>-Footnote-53278106
Ref: Build<16>-Footnote-63278148
Ref: Build<16>-Footnote-73278204
Ref: Build<16>-Footnote-83278260
Ref: Build<16>-Footnote-93278315
Ref: Build<16>-Footnote-103278370
Node: Windows<13>3278426
Ref: whatsnew/changelog id1303278513
Ref: 167b3278513
Ref: Windows<13>-Footnote-13279763
Ref: Windows<13>-Footnote-23279819
Ref: Windows<13>-Footnote-33279875
Ref: Windows<13>-Footnote-43279930
Ref: Windows<13>-Footnote-53279986
Ref: Windows<13>-Footnote-63280041
Ref: Windows<13>-Footnote-73280097
Node: Python 3 12 0 alpha 43280153
Ref: whatsnew/changelog python-3-12-0-alpha-43280298
Ref: 167c3280298
Node: Core and Builtins<18>3280636
Ref: whatsnew/changelog id1313280735
Ref: 167d3280735
Ref: Core and Builtins<18>-Footnote-13285646
Ref: Core and Builtins<18>-Footnote-23285702
Ref: Core and Builtins<18>-Footnote-33285757
Ref: Core and Builtins<18>-Footnote-43285812
Ref: Core and Builtins<18>-Footnote-53285868
Ref: Core and Builtins<18>-Footnote-63285924
Ref: Core and Builtins<18>-Footnote-73285980
Ref: Core and Builtins<18>-Footnote-83286036
Ref: Core and Builtins<18>-Footnote-93286092
Ref: Core and Builtins<18>-Footnote-103286148
Ref: Core and Builtins<18>-Footnote-113286204
Ref: Core and Builtins<18>-Footnote-123286247
Ref: Core and Builtins<18>-Footnote-133286304
Ref: Core and Builtins<18>-Footnote-143286361
Ref: Core and Builtins<18>-Footnote-153286418
Ref: Core and Builtins<18>-Footnote-163286475
Ref: Core and Builtins<18>-Footnote-173286532
Ref: Core and Builtins<18>-Footnote-183286588
Ref: Core and Builtins<18>-Footnote-193286645
Ref: Core and Builtins<18>-Footnote-203286701
Ref: Core and Builtins<18>-Footnote-213286758
Ref: Core and Builtins<18>-Footnote-223286814
Ref: Core and Builtins<18>-Footnote-233286870
Ref: Core and Builtins<18>-Footnote-243286926
Ref: Core and Builtins<18>-Footnote-253286983
Ref: Core and Builtins<18>-Footnote-263287040
Ref: Core and Builtins<18>-Footnote-273287097
Ref: Core and Builtins<18>-Footnote-283287154
Ref: Core and Builtins<18>-Footnote-293287210
Ref: Core and Builtins<18>-Footnote-303287266
Ref: Core and Builtins<18>-Footnote-313287322
Ref: Core and Builtins<18>-Footnote-323287378
Ref: Core and Builtins<18>-Footnote-333287434
Ref: Core and Builtins<18>-Footnote-343287490
Node: Library<17>3287556
Ref: whatsnew/changelog id1323287681
Ref: 16813287681
Ref: Library<17>-Footnote-13297972
Ref: Library<17>-Footnote-23298028
Ref: Library<17>-Footnote-33298084
Ref: Library<17>-Footnote-43298140
Ref: Library<17>-Footnote-53298196
Ref: Library<17>-Footnote-63298251
Ref: Library<17>-Footnote-73298306
Ref: Library<17>-Footnote-83298362
Ref: Library<17>-Footnote-93298418
Ref: Library<17>-Footnote-103298473
Ref: Library<17>-Footnote-113298530
Ref: Library<17>-Footnote-123298586
Ref: Library<17>-Footnote-133298643
Ref: Library<17>-Footnote-143298699
Ref: Library<17>-Footnote-153298755
Ref: Library<17>-Footnote-163298812
Ref: Library<17>-Footnote-173298869
Ref: Library<17>-Footnote-183298926
Ref: Library<17>-Footnote-193298983
Ref: Library<17>-Footnote-203299040
Ref: Library<17>-Footnote-213299097
Ref: Library<17>-Footnote-223299154
Ref: Library<17>-Footnote-233299210
Ref: Library<17>-Footnote-243299267
Ref: Library<17>-Footnote-253299324
Ref: Library<17>-Footnote-263299381
Ref: Library<17>-Footnote-273299437
Ref: Library<17>-Footnote-283299494
Ref: Library<17>-Footnote-293299551
Ref: Library<17>-Footnote-303299608
Ref: Library<17>-Footnote-313299665
Ref: Library<17>-Footnote-323299731
Ref: Library<17>-Footnote-333299788
Ref: Library<17>-Footnote-343299844
Ref: Library<17>-Footnote-353299900
Ref: Library<17>-Footnote-363299956
Ref: Library<17>-Footnote-373300012
Ref: Library<17>-Footnote-383300068
Ref: Library<17>-Footnote-393300124
Ref: Library<17>-Footnote-403300180
Ref: Library<17>-Footnote-413300236
Ref: Library<17>-Footnote-423300292
Ref: Library<17>-Footnote-433300335
Ref: Library<17>-Footnote-443300391
Ref: Library<17>-Footnote-453300447
Ref: Library<17>-Footnote-463300503
Ref: Library<17>-Footnote-473300559
Ref: Library<17>-Footnote-483300615
Ref: Library<17>-Footnote-493300671
Ref: Library<17>-Footnote-503300727
Ref: Library<17>-Footnote-513300783
Ref: Library<17>-Footnote-523300839
Ref: Library<17>-Footnote-533300895
Ref: Library<17>-Footnote-543300951
Ref: Library<17>-Footnote-553301017
Ref: Library<17>-Footnote-563301083
Node: Documentation<12>3301149
Ref: whatsnew/changelog id1333301262
Ref: 168b3301262
Ref: Documentation<12>-Footnote-13301845
Ref: Documentation<12>-Footnote-23301901
Ref: Documentation<12>-Footnote-33301957
Node: Tests<15>3302022
Ref: whatsnew/changelog id1343302133
Ref: 168d3302133
Ref: Tests<15>-Footnote-13302580
Ref: Tests<15>-Footnote-23302636
Ref: Tests<15>-Footnote-33302692
Node: Build<17>3302747
Ref: whatsnew/changelog id1353302852
Ref: 168e3302852
Ref: Build<17>-Footnote-13303739
Ref: Build<17>-Footnote-23303795
Ref: Build<17>-Footnote-33303850
Node: Windows<14>3303915
Ref: whatsnew/changelog id1363304020
Ref: 168f3304020
Ref: Windows<14>-Footnote-13304945
Ref: Windows<14>-Footnote-23305001
Ref: Windows<14>-Footnote-33305056
Ref: Windows<14>-Footnote-43305111
Ref: Windows<14>-Footnote-53305166
Ref: Windows<14>-Footnote-63305231
Node: macOS<10>3305296
Ref: whatsnew/changelog id1373305406
Ref: 16923305406
Ref: macOS<10>-Footnote-13305688
Ref: macOS<10>-Footnote-23305744
Node: Tools/Demos<8>3305800
Ref: whatsnew/changelog id1383305908
Ref: 16933305908
Ref: Tools/Demos<8>-Footnote-13306282
Ref: Tools/Demos<8>-Footnote-23306347
Node: C API<16>3306403
Ref: whatsnew/changelog id1393306493
Ref: 16943306493
Ref: C API<16>-Footnote-13307060
Ref: C API<16>-Footnote-23307115
Ref: C API<16>-Footnote-33307170
Node: Python 3 12 0 alpha 33307225
Ref: whatsnew/changelog python-3-12-0-alpha-33307370
Ref: 16953307370
Node: Security<12>3307734
Ref: whatsnew/changelog id1403307834
Ref: 16963307834
Ref: Security<12>-Footnote-13308394
Ref: Security<12>-Footnote-23308450
Node: Core and Builtins<19>3308505
Ref: whatsnew/changelog id1413308625
Ref: 16973308625
Ref: Core and Builtins<19>-Footnote-13311928
Ref: Core and Builtins<19>-Footnote-23311983
Ref: Core and Builtins<19>-Footnote-33312038
Ref: Core and Builtins<19>-Footnote-43312093
Ref: Core and Builtins<19>-Footnote-53312148
Ref: Core and Builtins<19>-Footnote-63312203
Ref: Core and Builtins<19>-Footnote-73312258
Ref: Core and Builtins<19>-Footnote-83312313
Ref: Core and Builtins<19>-Footnote-93312368
Ref: Core and Builtins<19>-Footnote-103312423
Ref: Core and Builtins<19>-Footnote-113312479
Ref: Core and Builtins<19>-Footnote-123312535
Ref: Core and Builtins<19>-Footnote-133312591
Ref: Core and Builtins<19>-Footnote-143312647
Ref: Core and Builtins<19>-Footnote-153312703
Ref: Core and Builtins<19>-Footnote-163312759
Ref: Core and Builtins<19>-Footnote-173312825
Ref: Core and Builtins<19>-Footnote-183312891
Node: Library<18>3312957
Ref: whatsnew/changelog id1423313082
Ref: 16983313082
Ref: Library<18>-Footnote-13319311
Ref: Library<18>-Footnote-23319367
Ref: Library<18>-Footnote-33319422
Ref: Library<18>-Footnote-43319477
Ref: Library<18>-Footnote-53319532
Ref: Library<18>-Footnote-63319587
Ref: Library<18>-Footnote-73319642
Ref: Library<18>-Footnote-83319697
Ref: Library<18>-Footnote-93319752
Ref: Library<18>-Footnote-103319807
Ref: Library<18>-Footnote-113319863
Ref: Library<18>-Footnote-123319919
Ref: Library<18>-Footnote-133319975
Ref: Library<18>-Footnote-143320031
Ref: Library<18>-Footnote-153320087
Ref: Library<18>-Footnote-163320143
Ref: Library<18>-Footnote-173320199
Ref: Library<18>-Footnote-183320255
Ref: Library<18>-Footnote-193320311
Ref: Library<18>-Footnote-203320367
Ref: Library<18>-Footnote-213320423
Ref: Library<18>-Footnote-223320479
Ref: Library<18>-Footnote-233320535
Ref: Library<18>-Footnote-243320591
Ref: Library<18>-Footnote-253320647
Ref: Library<18>-Footnote-263320703
Ref: Library<18>-Footnote-273320759
Ref: Library<18>-Footnote-283320815
Ref: Library<18>-Footnote-293320871
Ref: Library<18>-Footnote-303320927
Ref: Library<18>-Footnote-313320983
Ref: Library<18>-Footnote-323321049
Ref: Library<18>-Footnote-333321115
Ref: Library<18>-Footnote-343321181
Node: Documentation<13>3321247
Ref: whatsnew/changelog id1433321360
Ref: 169b3321360
Ref: Documentation<13>-Footnote-13322129
Ref: Documentation<13>-Footnote-23322184
Ref: Documentation<13>-Footnote-33322236
Ref: Documentation<13>-Footnote-43322260
Ref: Documentation<13>-Footnote-53322315
Ref: Documentation<13>-Footnote-63322370
Ref: Documentation<13>-Footnote-73322425
Node: Tests<16>3322490
Ref: whatsnew/changelog id1443322601
Ref: 169c3322601
Ref: Tests<16>-Footnote-13323376
Ref: Tests<16>-Footnote-23323431
Ref: Tests<16>-Footnote-33323486
Ref: Tests<16>-Footnote-43323541
Ref: Tests<16>-Footnote-53323596
Ref: Tests<16>-Footnote-63323651
Node: Build<18>3323706
Ref: whatsnew/changelog id1453323811
Ref: 169d3323811
Ref: Build<18>-Footnote-13324775
Ref: Build<18>-Footnote-23324830
Ref: Build<18>-Footnote-33324885
Ref: Build<18>-Footnote-43324940
Ref: Build<18>-Footnote-53324995
Node: Windows<15>3325050
Ref: whatsnew/changelog id1463325155
Ref: 169e3325155
Ref: Windows<15>-Footnote-13325689
Ref: Windows<15>-Footnote-23325744
Ref: Windows<15>-Footnote-33325799
Ref: Windows<15>-Footnote-43325854
Node: macOS<11>3325919
Ref: whatsnew/changelog id1473326029
Ref: 169f3326029
Ref: macOS<11>-Footnote-13326297
Ref: macOS<11>-Footnote-23326352
Node: Tools/Demos<9>3326407
Ref: whatsnew/changelog id1483326515
Ref: 16a03326515
Ref: Tools/Demos<9>-Footnote-13327005
Node: C API<17>3327060
Ref: whatsnew/changelog id1493327150
Ref: 16a13327150
Ref: C API<17>-Footnote-13327971
Ref: C API<17>-Footnote-23328026
Ref: C API<17>-Footnote-33328081
Node: Python 3 12 0 alpha 23328136
Ref: whatsnew/changelog python-3-12-0-alpha-23328281
Ref: 16a33328281
Node: Security<13>3328614
Ref: whatsnew/changelog id1503328714
Ref: 16a43328714
Ref: Security<13>-Footnote-13329842
Ref: Security<13>-Footnote-23329897
Ref: Security<13>-Footnote-33329956
Ref: Security<13>-Footnote-43330015
Ref: Security<13>-Footnote-53330074
Node: Core and Builtins<20>3330129
Ref: whatsnew/changelog id1513330249
Ref: 16a53330249
Ref: Core and Builtins<20>-Footnote-13338246
Ref: Core and Builtins<20>-Footnote-23338301
Ref: Core and Builtins<20>-Footnote-33338356
Ref: Core and Builtins<20>-Footnote-43338411
Ref: Core and Builtins<20>-Footnote-53338466
Ref: Core and Builtins<20>-Footnote-63338521
Ref: Core and Builtins<20>-Footnote-73338576
Ref: Core and Builtins<20>-Footnote-83338631
Ref: Core and Builtins<20>-Footnote-93338686
Ref: Core and Builtins<20>-Footnote-103338741
Ref: Core and Builtins<20>-Footnote-113338797
Ref: Core and Builtins<20>-Footnote-123338853
Ref: Core and Builtins<20>-Footnote-133338909
Ref: Core and Builtins<20>-Footnote-143338965
Ref: Core and Builtins<20>-Footnote-153339021
Ref: Core and Builtins<20>-Footnote-163339077
Ref: Core and Builtins<20>-Footnote-173339133
Ref: Core and Builtins<20>-Footnote-183339189
Ref: Core and Builtins<20>-Footnote-193339245
Ref: Core and Builtins<20>-Footnote-203339301
Ref: Core and Builtins<20>-Footnote-213339357
Ref: Core and Builtins<20>-Footnote-223339413
Ref: Core and Builtins<20>-Footnote-233339469
Ref: Core and Builtins<20>-Footnote-243339525
Ref: Core and Builtins<20>-Footnote-253339568
Ref: Core and Builtins<20>-Footnote-263339624
Ref: Core and Builtins<20>-Footnote-273339680
Ref: Core and Builtins<20>-Footnote-283339736
Ref: Core and Builtins<20>-Footnote-293339792
Ref: Core and Builtins<20>-Footnote-303339848
Ref: Core and Builtins<20>-Footnote-313339904
Ref: Core and Builtins<20>-Footnote-323339960
Ref: Core and Builtins<20>-Footnote-333340016
Ref: Core and Builtins<20>-Footnote-343340072
Ref: Core and Builtins<20>-Footnote-353340128
Node: Library<19>3340184
Ref: whatsnew/changelog id1523340309
Ref: 16ad3340309
Ref: Library<19>-Footnote-13346108
Ref: Library<19>-Footnote-23346163
Ref: Library<19>-Footnote-33346218
Ref: Library<19>-Footnote-43346273
Ref: Library<19>-Footnote-53346328
Ref: Library<19>-Footnote-63346383
Ref: Library<19>-Footnote-73346438
Ref: Library<19>-Footnote-83346493
Ref: Library<19>-Footnote-93346548
Ref: Library<19>-Footnote-103346603
Ref: Library<19>-Footnote-113346659
Ref: Library<19>-Footnote-123346715
Ref: Library<19>-Footnote-133346758
Ref: Library<19>-Footnote-143346814
Ref: Library<19>-Footnote-153346870
Ref: Library<19>-Footnote-163346926
Ref: Library<19>-Footnote-173346982
Ref: Library<19>-Footnote-183347038
Ref: Library<19>-Footnote-193347094
Ref: Library<19>-Footnote-203347150
Ref: Library<19>-Footnote-213347206
Ref: Library<19>-Footnote-223347262
Ref: Library<19>-Footnote-233347318
Ref: Library<19>-Footnote-243347374
Ref: Library<19>-Footnote-253347430
Ref: Library<19>-Footnote-263347486
Ref: Library<19>-Footnote-273347542
Ref: Library<19>-Footnote-283347598
Ref: Library<19>-Footnote-293347654
Ref: Library<19>-Footnote-303347710
Ref: Library<19>-Footnote-313347766
Ref: Library<19>-Footnote-323347809
Ref: Library<19>-Footnote-333347865
Ref: Library<19>-Footnote-343347921
Ref: Library<19>-Footnote-353347977
Ref: Library<19>-Footnote-363348033
Ref: Library<19>-Footnote-373348076
Ref: Library<19>-Footnote-383348132
Ref: Library<19>-Footnote-393348188
Ref: Library<19>-Footnote-403348254
Ref: Library<19>-Footnote-413348320
Node: Documentation<14>3348386
Ref: whatsnew/changelog id1533348499
Ref: 16b23348499
Ref: Documentation<14>-Footnote-13348818
Ref: Documentation<14>-Footnote-23348873
Node: Tests<17>3348928
Ref: whatsnew/changelog id1543349039
Ref: 16b33349039
Ref: Tests<17>-Footnote-13349926
Ref: Tests<17>-Footnote-23349981
Ref: Tests<17>-Footnote-33350036
Ref: Tests<17>-Footnote-43350091
Ref: Tests<17>-Footnote-53350146
Node: Build<19>3350211
Ref: whatsnew/changelog id1553350316
Ref: 16b43350316
Ref: Build<19>-Footnote-13352001
Ref: Build<19>-Footnote-23352056
Ref: Build<19>-Footnote-33352111
Ref: Build<19>-Footnote-43352166
Ref: Build<19>-Footnote-53352221
Ref: Build<19>-Footnote-63352276
Ref: Build<19>-Footnote-73352331
Ref: Build<19>-Footnote-83352421
Ref: Build<19>-Footnote-93352476
Ref: Build<19>-Footnote-103352531
Node: Windows<16>3352587
Ref: whatsnew/changelog id1563352692
Ref: 16b63352692
Ref: Windows<16>-Footnote-13353395
Ref: Windows<16>-Footnote-23353450
Ref: Windows<16>-Footnote-33353520
Ref: Windows<16>-Footnote-43353575
Ref: Windows<16>-Footnote-53353630
Ref: Windows<16>-Footnote-63353685
Node: macOS<12>3353740
Ref: whatsnew/changelog id1573353845
Ref: 16b73353845
Ref: macOS<12>-Footnote-13353974
Node: C API<18>3354029
Ref: whatsnew/changelog id1583354114
Ref: 16b83354114
Ref: C API<18>-Footnote-13356177
Ref: C API<18>-Footnote-23356232
Ref: C API<18>-Footnote-33356287
Ref: C API<18>-Footnote-43356342
Ref: C API<18>-Footnote-53356397
Ref: C API<18>-Footnote-63356452
Ref: C API<18>-Footnote-73356507
Node: Python 3 12 0 alpha 13356562
Ref: whatsnew/changelog python-3-12-0-alpha-13356706
Ref: 16ba3356706
Node: Security<14>3357089
Ref: whatsnew/changelog id1593357189
Ref: 16bb3357189
Ref: Security<14>-Footnote-13359022
Ref: Security<14>-Footnote-23359077
Ref: Security<14>-Footnote-33359132
Ref: Security<14>-Footnote-43359204
Ref: Security<14>-Footnote-53359274
Ref: Security<14>-Footnote-63359329
Ref: Security<14>-Footnote-73359384
Ref: Security<14>-Footnote-83359439
Node: Core and Builtins<21>3359494
Ref: whatsnew/changelog id1603359614
Ref: 16bc3359614
Ref: Core and Builtins<21>-Footnote-13388924
Ref: Core and Builtins<21>-Footnote-23388979
Ref: Core and Builtins<21>-Footnote-33389034
Ref: Core and Builtins<21>-Footnote-43389089
Ref: Core and Builtins<21>-Footnote-53389144
Ref: Core and Builtins<21>-Footnote-63389199
Ref: Core and Builtins<21>-Footnote-73389254
Ref: Core and Builtins<21>-Footnote-83389309
Ref: Core and Builtins<21>-Footnote-93389364
Ref: Core and Builtins<21>-Footnote-103389419
Ref: Core and Builtins<21>-Footnote-113389475
Ref: Core and Builtins<21>-Footnote-123389531
Ref: Core and Builtins<21>-Footnote-133389587
Ref: Core and Builtins<21>-Footnote-143389643
Ref: Core and Builtins<21>-Footnote-153389699
Ref: Core and Builtins<21>-Footnote-163389755
Ref: Core and Builtins<21>-Footnote-173389811
Ref: Core and Builtins<21>-Footnote-183389867
Ref: Core and Builtins<21>-Footnote-193389923
Ref: Core and Builtins<21>-Footnote-203389979
Ref: Core and Builtins<21>-Footnote-213390035
Ref: Core and Builtins<21>-Footnote-223390091
Ref: Core and Builtins<21>-Footnote-233390147
Ref: Core and Builtins<21>-Footnote-243390203
Ref: Core and Builtins<21>-Footnote-253390259
Ref: Core and Builtins<21>-Footnote-263390315
Ref: Core and Builtins<21>-Footnote-273390371
Ref: Core and Builtins<21>-Footnote-283390427
Ref: Core and Builtins<21>-Footnote-293390483
Ref: Core and Builtins<21>-Footnote-303390539
Ref: Core and Builtins<21>-Footnote-313390595
Ref: Core and Builtins<21>-Footnote-323390651
Ref: Core and Builtins<21>-Footnote-333390707
Ref: Core and Builtins<21>-Footnote-343390763
Ref: Core and Builtins<21>-Footnote-353390819
Ref: Core and Builtins<21>-Footnote-363390875
Ref: Core and Builtins<21>-Footnote-373390931
Ref: Core and Builtins<21>-Footnote-383390987
Ref: Core and Builtins<21>-Footnote-393391043
Ref: Core and Builtins<21>-Footnote-403391099
Ref: Core and Builtins<21>-Footnote-413391155
Ref: Core and Builtins<21>-Footnote-423391211
Ref: Core and Builtins<21>-Footnote-433391267
Ref: Core and Builtins<21>-Footnote-443391323
Ref: Core and Builtins<21>-Footnote-453391379
Ref: Core and Builtins<21>-Footnote-463391435
Ref: Core and Builtins<21>-Footnote-473391491
Ref: Core and Builtins<21>-Footnote-483391547
Ref: Core and Builtins<21>-Footnote-493391590
Ref: Core and Builtins<21>-Footnote-503391646
Ref: Core and Builtins<21>-Footnote-513391702
Ref: Core and Builtins<21>-Footnote-523391758
Ref: Core and Builtins<21>-Footnote-533391814
Ref: Core and Builtins<21>-Footnote-543391870
Ref: Core and Builtins<21>-Footnote-553391926
Ref: Core and Builtins<21>-Footnote-563391982
Ref: Core and Builtins<21>-Footnote-573392038
Ref: Core and Builtins<21>-Footnote-583392094
Ref: Core and Builtins<21>-Footnote-593392150
Ref: Core and Builtins<21>-Footnote-603392206
Ref: Core and Builtins<21>-Footnote-613392262
Ref: Core and Builtins<21>-Footnote-623392318
Ref: Core and Builtins<21>-Footnote-633392374
Ref: Core and Builtins<21>-Footnote-643392430
Ref: Core and Builtins<21>-Footnote-653392486
Ref: Core and Builtins<21>-Footnote-663392542
Ref: Core and Builtins<21>-Footnote-673392598
Ref: Core and Builtins<21>-Footnote-683392654
Ref: Core and Builtins<21>-Footnote-693392710
Ref: Core and Builtins<21>-Footnote-703392766
Ref: Core and Builtins<21>-Footnote-713392822
Ref: Core and Builtins<21>-Footnote-723392878
Ref: Core and Builtins<21>-Footnote-733392934
Ref: Core and Builtins<21>-Footnote-743392990
Ref: Core and Builtins<21>-Footnote-753393046
Ref: Core and Builtins<21>-Footnote-763393102
Ref: Core and Builtins<21>-Footnote-773393158
Ref: Core and Builtins<21>-Footnote-783393214
Ref: Core and Builtins<21>-Footnote-793393270
Ref: Core and Builtins<21>-Footnote-803393326
Ref: Core and Builtins<21>-Footnote-813393382
Ref: Core and Builtins<21>-Footnote-823393438
Ref: Core and Builtins<21>-Footnote-833393494
Ref: Core and Builtins<21>-Footnote-843393550
Ref: Core and Builtins<21>-Footnote-853393606
Ref: Core and Builtins<21>-Footnote-863393662
Ref: Core and Builtins<21>-Footnote-873393718
Ref: Core and Builtins<21>-Footnote-883393774
Ref: Core and Builtins<21>-Footnote-893393830
Ref: Core and Builtins<21>-Footnote-903393886
Ref: Core and Builtins<21>-Footnote-913393942
Ref: Core and Builtins<21>-Footnote-923393998
Ref: Core and Builtins<21>-Footnote-933394054
Ref: Core and Builtins<21>-Footnote-943394110
Ref: Core and Builtins<21>-Footnote-953394166
Ref: Core and Builtins<21>-Footnote-963394222
Ref: Core and Builtins<21>-Footnote-973394278
Ref: Core and Builtins<21>-Footnote-983394334
Ref: Core and Builtins<21>-Footnote-993394390
Ref: Core and Builtins<21>-Footnote-1003394446
Ref: Core and Builtins<21>-Footnote-1013394503
Ref: Core and Builtins<21>-Footnote-1023394560
Ref: Core and Builtins<21>-Footnote-1033394617
Ref: Core and Builtins<21>-Footnote-1043394674
Ref: Core and Builtins<21>-Footnote-1053394731
Ref: Core and Builtins<21>-Footnote-1063394788
Ref: Core and Builtins<21>-Footnote-1073394832
Ref: Core and Builtins<21>-Footnote-1083394889
Ref: Core and Builtins<21>-Footnote-1093394946
Ref: Core and Builtins<21>-Footnote-1103395003
Ref: Core and Builtins<21>-Footnote-1113395060
Ref: Core and Builtins<21>-Footnote-1123395117
Ref: Core and Builtins<21>-Footnote-1133395174
Ref: Core and Builtins<21>-Footnote-1143395231
Ref: Core and Builtins<21>-Footnote-1153395288
Ref: Core and Builtins<21>-Footnote-1163395345
Ref: Core and Builtins<21>-Footnote-1173395402
Ref: Core and Builtins<21>-Footnote-1183395459
Ref: Core and Builtins<21>-Footnote-1193395516
Ref: Core and Builtins<21>-Footnote-1203395573
Ref: Core and Builtins<21>-Footnote-1213395630
Ref: Core and Builtins<21>-Footnote-1223395687
Ref: Core and Builtins<21>-Footnote-1233395744
Ref: Core and Builtins<21>-Footnote-1243395801
Ref: Core and Builtins<21>-Footnote-1253395858
Ref: Core and Builtins<21>-Footnote-1263395915
Ref: Core and Builtins<21>-Footnote-1273395972
Ref: Core and Builtins<21>-Footnote-1283396029
Ref: Core and Builtins<21>-Footnote-1293396086
Ref: Core and Builtins<21>-Footnote-1303396143
Ref: Core and Builtins<21>-Footnote-1313396200
Ref: Core and Builtins<21>-Footnote-1323396257
Ref: Core and Builtins<21>-Footnote-1333396314
Ref: Core and Builtins<21>-Footnote-1343396371
Ref: Core and Builtins<21>-Footnote-1353396428
Ref: Core and Builtins<21>-Footnote-1363396485
Ref: Core and Builtins<21>-Footnote-1373396542
Ref: Core and Builtins<21>-Footnote-1383396599
Ref: Core and Builtins<21>-Footnote-1393396656
Ref: Core and Builtins<21>-Footnote-1403396713
Ref: Core and Builtins<21>-Footnote-1413396770
Ref: Core and Builtins<21>-Footnote-1423396827
Ref: Core and Builtins<21>-Footnote-1433396884
Ref: Core and Builtins<21>-Footnote-1443396941
Ref: Core and Builtins<21>-Footnote-1453396998
Ref: Core and Builtins<21>-Footnote-1463397055
Ref: Core and Builtins<21>-Footnote-1473397112
Ref: Core and Builtins<21>-Footnote-1483397169
Ref: Core and Builtins<21>-Footnote-1493397230
Ref: Core and Builtins<21>-Footnote-1503397287
Ref: Core and Builtins<21>-Footnote-1513397344
Ref: Core and Builtins<21>-Footnote-1523397401
Ref: Core and Builtins<21>-Footnote-1533397458
Ref: Core and Builtins<21>-Footnote-1543397515
Ref: Core and Builtins<21>-Footnote-1553397572
Ref: Core and Builtins<21>-Footnote-1563397629
Ref: Core and Builtins<21>-Footnote-1573397686
Ref: Core and Builtins<21>-Footnote-1583397743
Ref: Core and Builtins<21>-Footnote-1593397800
Ref: Core and Builtins<21>-Footnote-1603397857
Ref: Core and Builtins<21>-Footnote-1613397914
Ref: Core and Builtins<21>-Footnote-1623397971
Ref: Core and Builtins<21>-Footnote-1633398028
Ref: Core and Builtins<21>-Footnote-1643398085
Ref: Core and Builtins<21>-Footnote-1653398142
Ref: Core and Builtins<21>-Footnote-1663398199
Ref: Core and Builtins<21>-Footnote-1673398256
Ref: Core and Builtins<21>-Footnote-1683398313
Ref: Core and Builtins<21>-Footnote-1693398370
Ref: Core and Builtins<21>-Footnote-1703398437
Ref: Core and Builtins<21>-Footnote-1713398504
Node: Library<20>3398571
Ref: whatsnew/changelog id1613398696
Ref: 16c63398696
Ref: Library<20>-Footnote-13441967
Ref: Library<20>-Footnote-23442022
Ref: Library<20>-Footnote-33442077
Ref: Library<20>-Footnote-43442132
Ref: Library<20>-Footnote-53442187
Ref: Library<20>-Footnote-63442242
Ref: Library<20>-Footnote-73442297
Ref: Library<20>-Footnote-83442352
Ref: Library<20>-Footnote-93442407
Ref: Library<20>-Footnote-103442462
Ref: Library<20>-Footnote-113442518
Ref: Library<20>-Footnote-123442574
Ref: Library<20>-Footnote-133442630
Ref: Library<20>-Footnote-143442686
Ref: Library<20>-Footnote-153442742
Ref: Library<20>-Footnote-163442798
Ref: Library<20>-Footnote-173442854
Ref: Library<20>-Footnote-183442910
Ref: Library<20>-Footnote-193442966
Ref: Library<20>-Footnote-203443026
Ref: Library<20>-Footnote-213443082
Ref: Library<20>-Footnote-223443138
Ref: Library<20>-Footnote-233443194
Ref: Library<20>-Footnote-243443250
Ref: Library<20>-Footnote-253443306
Ref: Library<20>-Footnote-263443362
Ref: Library<20>-Footnote-273443418
Ref: Library<20>-Footnote-283443474
Ref: Library<20>-Footnote-293443530
Ref: Library<20>-Footnote-303443586
Ref: Library<20>-Footnote-313443642
Ref: Library<20>-Footnote-323443698
Ref: Library<20>-Footnote-333443754
Ref: Library<20>-Footnote-343443810
Ref: Library<20>-Footnote-353443866
Ref: Library<20>-Footnote-363443922
Ref: Library<20>-Footnote-373443978
Ref: Library<20>-Footnote-383444034
Ref: Library<20>-Footnote-393444090
Ref: Library<20>-Footnote-403444146
Ref: Library<20>-Footnote-413444202
Ref: Library<20>-Footnote-423444258
Ref: Library<20>-Footnote-433444314
Ref: Library<20>-Footnote-443444370
Ref: Library<20>-Footnote-453444426
Ref: Library<20>-Footnote-463444482
Ref: Library<20>-Footnote-473444538
Ref: Library<20>-Footnote-483444594
Ref: Library<20>-Footnote-493444650
Ref: Library<20>-Footnote-503444706
Ref: Library<20>-Footnote-513444762
Ref: Library<20>-Footnote-523444818
Ref: Library<20>-Footnote-533444874
Ref: Library<20>-Footnote-543444930
Ref: Library<20>-Footnote-553444986
Ref: Library<20>-Footnote-563445042
Ref: Library<20>-Footnote-573445098
Ref: Library<20>-Footnote-583445154
Ref: Library<20>-Footnote-593445210
Ref: Library<20>-Footnote-603445266
Ref: Library<20>-Footnote-613445322
Ref: Library<20>-Footnote-623445378
Ref: Library<20>-Footnote-633445434
Ref: Library<20>-Footnote-643445490
Ref: Library<20>-Footnote-653445546
Ref: Library<20>-Footnote-663445602
Ref: Library<20>-Footnote-673445658
Ref: Library<20>-Footnote-683445724
Ref: Library<20>-Footnote-693445780
Ref: Library<20>-Footnote-703445836
Ref: Library<20>-Footnote-713445892
Ref: Library<20>-Footnote-723445948
Ref: Library<20>-Footnote-733446004
Ref: Library<20>-Footnote-743446060
Ref: Library<20>-Footnote-753446116
Ref: Library<20>-Footnote-763446172
Ref: Library<20>-Footnote-773446228
Ref: Library<20>-Footnote-783446284
Ref: Library<20>-Footnote-793446340
Ref: Library<20>-Footnote-803446396
Ref: Library<20>-Footnote-813446452
Ref: Library<20>-Footnote-823446508
Ref: Library<20>-Footnote-833446564
Ref: Library<20>-Footnote-843446620
Ref: Library<20>-Footnote-853446676
Ref: Library<20>-Footnote-863446732
Ref: Library<20>-Footnote-873446788
Ref: Library<20>-Footnote-883446844
Ref: Library<20>-Footnote-893446900
Ref: Library<20>-Footnote-903446956
Ref: Library<20>-Footnote-913447012
Ref: Library<20>-Footnote-923447068
Ref: Library<20>-Footnote-933447124
Ref: Library<20>-Footnote-943447180
Ref: Library<20>-Footnote-953447236
Ref: Library<20>-Footnote-963447292
Ref: Library<20>-Footnote-973447348
Ref: Library<20>-Footnote-983447404
Ref: Library<20>-Footnote-993447460
Ref: Library<20>-Footnote-1003447516
Ref: Library<20>-Footnote-1013447573
Ref: Library<20>-Footnote-1023447630
Ref: Library<20>-Footnote-1033447687
Ref: Library<20>-Footnote-1043447744
Ref: Library<20>-Footnote-1053447801
Ref: Library<20>-Footnote-1063447858
Ref: Library<20>-Footnote-1073447915
Ref: Library<20>-Footnote-1083447972
Ref: Library<20>-Footnote-1093448029
Ref: Library<20>-Footnote-1103448086
Ref: Library<20>-Footnote-1113448143
Ref: Library<20>-Footnote-1123448200
Ref: Library<20>-Footnote-1133448257
Ref: Library<20>-Footnote-1143448314
Ref: Library<20>-Footnote-1153448371
Ref: Library<20>-Footnote-1163448428
Ref: Library<20>-Footnote-1173448485
Ref: Library<20>-Footnote-1183448542
Ref: Library<20>-Footnote-1193448599
Ref: Library<20>-Footnote-1203448656
Ref: Library<20>-Footnote-1213448713
Ref: Library<20>-Footnote-1223448770
Ref: Library<20>-Footnote-1233448827
Ref: Library<20>-Footnote-1243448871
Ref: Library<20>-Footnote-1253448928
Ref: Library<20>-Footnote-1263448985
Ref: Library<20>-Footnote-1273449042
Ref: Library<20>-Footnote-1283449099
Ref: Library<20>-Footnote-1293449156
Ref: Library<20>-Footnote-1303449213
Ref: Library<20>-Footnote-1313449270
Ref: Library<20>-Footnote-1323449327
Ref: Library<20>-Footnote-1333449384
Ref: Library<20>-Footnote-1343449441
Ref: Library<20>-Footnote-1353449498
Ref: Library<20>-Footnote-1363449555
Ref: Library<20>-Footnote-1373449612
Ref: Library<20>-Footnote-1383449669
Ref: Library<20>-Footnote-1393449726
Ref: Library<20>-Footnote-1403449784
Ref: Library<20>-Footnote-1413449841
Ref: Library<20>-Footnote-1423449898
Ref: Library<20>-Footnote-1433449942
Ref: Library<20>-Footnote-1443449999
Ref: Library<20>-Footnote-1453450056
Ref: Library<20>-Footnote-1463450113
Ref: Library<20>-Footnote-1473450170
Ref: Library<20>-Footnote-1483450227
Ref: Library<20>-Footnote-1493450284
Ref: Library<20>-Footnote-1503450341
Ref: Library<20>-Footnote-1513450398
Ref: Library<20>-Footnote-1523450455
Ref: Library<20>-Footnote-1533450512
Ref: Library<20>-Footnote-1543450569
Ref: Library<20>-Footnote-1553450626
Ref: Library<20>-Footnote-1563450683
Ref: Library<20>-Footnote-1573450740
Ref: Library<20>-Footnote-1583450797
Ref: Library<20>-Footnote-1593450854
Ref: Library<20>-Footnote-1603450911
Ref: Library<20>-Footnote-1613450968
Ref: Library<20>-Footnote-1623451025
Ref: Library<20>-Footnote-1633451069
Ref: Library<20>-Footnote-1643451126
Ref: Library<20>-Footnote-1653451183
Ref: Library<20>-Footnote-1663451240
Ref: Library<20>-Footnote-1673451297
Ref: Library<20>-Footnote-1683451354
Ref: Library<20>-Footnote-1693451411
Ref: Library<20>-Footnote-1703451468
Ref: Library<20>-Footnote-1713451525
Ref: Library<20>-Footnote-1723451582
Ref: Library<20>-Footnote-1733451639
Ref: Library<20>-Footnote-1743451696
Ref: Library<20>-Footnote-1753451753
Ref: Library<20>-Footnote-1763451810
Ref: Library<20>-Footnote-1773451867
Ref: Library<20>-Footnote-1783451924
Ref: Library<20>-Footnote-1793451981
Ref: Library<20>-Footnote-1803452038
Ref: Library<20>-Footnote-1813452095
Ref: Library<20>-Footnote-1823452139
Ref: Library<20>-Footnote-1833452196
Ref: Library<20>-Footnote-1843452253
Ref: Library<20>-Footnote-1853452310
Ref: Library<20>-Footnote-1863452367
Ref: Library<20>-Footnote-1873452424
Ref: Library<20>-Footnote-1883452481
Ref: Library<20>-Footnote-1893452538
Ref: Library<20>-Footnote-1903452595
Ref: Library<20>-Footnote-1913452652
Ref: Library<20>-Footnote-1923452709
Ref: Library<20>-Footnote-1933452766
Ref: Library<20>-Footnote-1943452823
Ref: Library<20>-Footnote-1953452880
Ref: Library<20>-Footnote-1963452937
Ref: Library<20>-Footnote-1973452994
Ref: Library<20>-Footnote-1983453051
Ref: Library<20>-Footnote-1993453108
Ref: Library<20>-Footnote-2003453165
Ref: Library<20>-Footnote-2013453222
Ref: Library<20>-Footnote-2023453279
Ref: Library<20>-Footnote-2033453336
Ref: Library<20>-Footnote-2043453393
Ref: Library<20>-Footnote-2053453450
Ref: Library<20>-Footnote-2063453507
Ref: Library<20>-Footnote-2073453564
Ref: Library<20>-Footnote-2083453621
Ref: Library<20>-Footnote-2093453678
Ref: Library<20>-Footnote-2103453735
Ref: Library<20>-Footnote-2113453792
Ref: Library<20>-Footnote-2123453849
Ref: Library<20>-Footnote-2133453906
Ref: Library<20>-Footnote-2143453963
Ref: Library<20>-Footnote-2153454020
Ref: Library<20>-Footnote-2163454077
Ref: Library<20>-Footnote-2173454134
Ref: Library<20>-Footnote-2183454191
Ref: Library<20>-Footnote-2193454248
Ref: Library<20>-Footnote-2203454305
Ref: Library<20>-Footnote-2213454362
Ref: Library<20>-Footnote-2223454419
Ref: Library<20>-Footnote-2233454476
Ref: Library<20>-Footnote-2243454533
Ref: Library<20>-Footnote-2253454590
Ref: Library<20>-Footnote-2263454647
Ref: Library<20>-Footnote-2273454714
Ref: Library<20>-Footnote-2283454781
Ref: Library<20>-Footnote-2293454848
Ref: Library<20>-Footnote-2303454905
Ref: Library<20>-Footnote-2313454972
Ref: Library<20>-Footnote-2323455039
Ref: Library<20>-Footnote-2333455106
Ref: Library<20>-Footnote-2343455173
Ref: Library<20>-Footnote-2353455240
Ref: Library<20>-Footnote-2363455307
Ref: Library<20>-Footnote-2373455374
Ref: Library<20>-Footnote-2383455441
Ref: Library<20>-Footnote-2393455508
Ref: Library<20>-Footnote-2403455575
Ref: Library<20>-Footnote-2413455642
Ref: Library<20>-Footnote-2423455709
Ref: Library<20>-Footnote-2433455776
Ref: Library<20>-Footnote-2443455843
Ref: Library<20>-Footnote-2453455910
Ref: Library<20>-Footnote-2463455977
Ref: Library<20>-Footnote-2473456044
Ref: Library<20>-Footnote-2483456111
Ref: Library<20>-Footnote-2493456178
Ref: Library<20>-Footnote-2503456245
Ref: Library<20>-Footnote-2513456312
Ref: Library<20>-Footnote-2523456379
Ref: Library<20>-Footnote-2533456446
Ref: Library<20>-Footnote-2543456513
Node: Documentation<15>3456580
Ref: whatsnew/changelog id1623456693
Ref: 16e53456693
Ref: Documentation<15>-Footnote-13460420
Ref: Documentation<15>-Footnote-23460475
Ref: Documentation<15>-Footnote-33460530
Ref: Documentation<15>-Footnote-43460576
Ref: Documentation<15>-Footnote-53460631
Ref: Documentation<15>-Footnote-63460686
Ref: Documentation<15>-Footnote-73460741
Ref: Documentation<15>-Footnote-83460796
Ref: Documentation<15>-Footnote-93460851
Ref: Documentation<15>-Footnote-103460906
Ref: Documentation<15>-Footnote-113460962
Ref: Documentation<15>-Footnote-123461018
Ref: Documentation<15>-Footnote-133461074
Ref: Documentation<15>-Footnote-143461130
Ref: Documentation<15>-Footnote-153461173
Ref: Documentation<15>-Footnote-163461229
Ref: Documentation<15>-Footnote-173461285
Ref: Documentation<15>-Footnote-183461341
Ref: Documentation<15>-Footnote-193461397
Ref: Documentation<15>-Footnote-203461453
Ref: Documentation<15>-Footnote-213461509
Ref: Documentation<15>-Footnote-223461565
Ref: Documentation<15>-Footnote-233461621
Ref: Documentation<15>-Footnote-243461687
Ref: Documentation<15>-Footnote-253461753
Ref: Documentation<15>-Footnote-263461819
Ref: Documentation<15>-Footnote-273461885
Node: Tests<18>3461951
Ref: whatsnew/changelog id1633462062
Ref: 16ec3462062
Ref: Tests<18>-Footnote-13467441
Ref: Tests<18>-Footnote-23467496
Ref: Tests<18>-Footnote-33467551
Ref: Tests<18>-Footnote-43467606
Ref: Tests<18>-Footnote-53467661
Ref: Tests<18>-Footnote-63467748
Ref: Tests<18>-Footnote-73467803
Ref: Tests<18>-Footnote-83467858
Ref: Tests<18>-Footnote-93467913
Ref: Tests<18>-Footnote-103467968
Ref: Tests<18>-Footnote-113468024
Ref: Tests<18>-Footnote-123468080
Ref: Tests<18>-Footnote-133468136
Ref: Tests<18>-Footnote-143468192
Ref: Tests<18>-Footnote-153468248
Ref: Tests<18>-Footnote-163468304
Ref: Tests<18>-Footnote-173468360
Ref: Tests<18>-Footnote-183468416
Ref: Tests<18>-Footnote-193468472
Ref: Tests<18>-Footnote-203468528
Ref: Tests<18>-Footnote-213468584
Ref: Tests<18>-Footnote-223468640
Ref: Tests<18>-Footnote-233468696
Ref: Tests<18>-Footnote-243468752
Ref: Tests<18>-Footnote-253468808
Ref: Tests<18>-Footnote-263468864
Ref: Tests<18>-Footnote-273468920
Ref: Tests<18>-Footnote-283468976
Ref: Tests<18>-Footnote-293469032
Ref: Tests<18>-Footnote-303469088
Ref: Tests<18>-Footnote-313469144
Ref: Tests<18>-Footnote-323469200
Ref: Tests<18>-Footnote-333469256
Ref: Tests<18>-Footnote-343469312
Ref: Tests<18>-Footnote-353469368
Ref: Tests<18>-Footnote-363469424
Node: Build<20>3469490
Ref: whatsnew/changelog id1643469595
Ref: 16f03469595
Ref: Build<20>-Footnote-13475073
Ref: Build<20>-Footnote-23475128
Ref: Build<20>-Footnote-33475183
Ref: Build<20>-Footnote-43475238
Ref: Build<20>-Footnote-53475293
Ref: Build<20>-Footnote-63475348
Ref: Build<20>-Footnote-73475403
Ref: Build<20>-Footnote-83475458
Ref: Build<20>-Footnote-93475513
Ref: Build<20>-Footnote-103475568
Ref: Build<20>-Footnote-113475624
Ref: Build<20>-Footnote-123475680
Ref: Build<20>-Footnote-133475736
Ref: Build<20>-Footnote-143475792
Ref: Build<20>-Footnote-153475848
Ref: Build<20>-Footnote-163475904
Ref: Build<20>-Footnote-173475947
Ref: Build<20>-Footnote-183476003
Ref: Build<20>-Footnote-193476059
Ref: Build<20>-Footnote-203476115
Ref: Build<20>-Footnote-213476171
Ref: Build<20>-Footnote-223476227
Ref: Build<20>-Footnote-233476283
Ref: Build<20>-Footnote-243476339
Ref: Build<20>-Footnote-253476395
Ref: Build<20>-Footnote-263476451
Ref: Build<20>-Footnote-273476507
Ref: Build<20>-Footnote-283476563
Ref: Build<20>-Footnote-293476619
Ref: Build<20>-Footnote-303476675
Ref: Build<20>-Footnote-313476731
Ref: Build<20>-Footnote-323476774
Ref: Build<20>-Footnote-333476830
Ref: Build<20>-Footnote-343476886
Ref: Build<20>-Footnote-353476942
Ref: Build<20>-Footnote-363476998
Node: Windows<17>3477064
Ref: whatsnew/changelog id1653477169
Ref: 16f13477169
Ref: Windows<17>-Footnote-13481600
Ref: Windows<17>-Footnote-23481655
Ref: Windows<17>-Footnote-33481710
Ref: Windows<17>-Footnote-43481765
Ref: Windows<17>-Footnote-53481820
Ref: Windows<17>-Footnote-63481875
Ref: Windows<17>-Footnote-73481930
Ref: Windows<17>-Footnote-83481985
Ref: Windows<17>-Footnote-93482040
Ref: Windows<17>-Footnote-103482095
Ref: Windows<17>-Footnote-113482151
Ref: Windows<17>-Footnote-123482207
Ref: Windows<17>-Footnote-133482263
Ref: Windows<17>-Footnote-143482319
Ref: Windows<17>-Footnote-153482375
Ref: Windows<17>-Footnote-163482431
Ref: Windows<17>-Footnote-173482487
Ref: Windows<17>-Footnote-183482543
Ref: Windows<17>-Footnote-193482599
Ref: Windows<17>-Footnote-203482655
Ref: Windows<17>-Footnote-213482711
Ref: Windows<17>-Footnote-223482767
Ref: Windows<17>-Footnote-233482823
Ref: Windows<17>-Footnote-243482879
Ref: Windows<17>-Footnote-253482935
Ref: Windows<17>-Footnote-263482991
Ref: Windows<17>-Footnote-273483057
Ref: Windows<17>-Footnote-283483113
Ref: Windows<17>-Footnote-293483179
Node: macOS<13>3483245
Ref: whatsnew/changelog id1663483349
Ref: 16f33483349
Ref: macOS<13>-Footnote-13483895
Node: IDLE<13>3483950
Ref: whatsnew/changelog id1673484058
Ref: 16f43484058
Ref: IDLE<13>-Footnote-13484969
Ref: IDLE<13>-Footnote-23485024
Ref: IDLE<13>-Footnote-33485079
Ref: IDLE<13>-Footnote-43485134
Ref: IDLE<13>-Footnote-53485189
Ref: IDLE<13>-Footnote-63485244
Ref: IDLE<13>-Footnote-73485299
Node: Tools/Demos<10>3485354
Ref: whatsnew/changelog id1683485462
Ref: 16f53485462
Ref: Tools/Demos<10>-Footnote-13486973
Ref: Tools/Demos<10>-Footnote-23487028
Ref: Tools/Demos<10>-Footnote-33487083
Ref: Tools/Demos<10>-Footnote-43487131
Ref: Tools/Demos<10>-Footnote-53487186
Ref: Tools/Demos<10>-Footnote-63487234
Ref: Tools/Demos<10>-Footnote-73487289
Ref: Tools/Demos<10>-Footnote-83487344
Ref: Tools/Demos<10>-Footnote-93487399
Ref: Tools/Demos<10>-Footnote-103487454
Ref: Tools/Demos<10>-Footnote-113487510
Ref: Tools/Demos<10>-Footnote-123487566
Node: C API<19>3487622
Ref: whatsnew/changelog id1703487713
Ref: 16f63487713
Ref: C API<19>-Footnote-13495245
Ref: C API<19>-Footnote-23495300
Ref: C API<19>-Footnote-33495355
Ref: C API<19>-Footnote-43495410
Ref: C API<19>-Footnote-53495465
Ref: C API<19>-Footnote-63495520
Ref: C API<19>-Footnote-73495575
Ref: C API<19>-Footnote-83495630
Ref: C API<19>-Footnote-93495685
Ref: C API<19>-Footnote-103495740
Ref: C API<19>-Footnote-113495796
Ref: C API<19>-Footnote-123495852
Ref: C API<19>-Footnote-133495908
Ref: C API<19>-Footnote-143495964
Ref: C API<19>-Footnote-153496020
Ref: C API<19>-Footnote-163496076
Ref: C API<19>-Footnote-173496132
Ref: C API<19>-Footnote-183496188
Ref: C API<19>-Footnote-193496244
Ref: C API<19>-Footnote-203496300
Ref: C API<19>-Footnote-213496356
Ref: C API<19>-Footnote-223496412
Ref: C API<19>-Footnote-233496468
Ref: C API<19>-Footnote-243496524
Ref: C API<19>-Footnote-253496580
Ref: C API<19>-Footnote-263496636
Ref: C API<19>-Footnote-273496692
Ref: C API<19>-Footnote-283496748
Ref: C API<19>-Footnote-293496804
Ref: C API<19>-Footnote-303496860
Ref: C API<19>-Footnote-313496916
Ref: C API<19>-Footnote-323496972
Ref: C API<19>-Footnote-333497028
Ref: C API<19>-Footnote-343497084
Node: Python 3 11 0 beta 13497150
Ref: whatsnew/changelog python-3-11-0-beta-13497294
Ref: 16f83497294
Node: Security<15>3497657
Ref: whatsnew/changelog id1713497756
Ref: 16f93497756
Ref: Security<15>-Footnote-13498055
Node: Core and Builtins<22>3498110
Ref: whatsnew/changelog id1723498229
Ref: 16fa3498229
Ref: Core and Builtins<22>-Footnote-13507739
Ref: Core and Builtins<22>-Footnote-23507794
Ref: Core and Builtins<22>-Footnote-33507859
Ref: Core and Builtins<22>-Footnote-43507914
Ref: Core and Builtins<22>-Footnote-53507979
Ref: Core and Builtins<22>-Footnote-63508034
Ref: Core and Builtins<22>-Footnote-73508089
Ref: Core and Builtins<22>-Footnote-83508144
Ref: Core and Builtins<22>-Footnote-93508199
Ref: Core and Builtins<22>-Footnote-103508254
Ref: Core and Builtins<22>-Footnote-113508310
Ref: Core and Builtins<22>-Footnote-123508366
Ref: Core and Builtins<22>-Footnote-133508422
Ref: Core and Builtins<22>-Footnote-143508478
Ref: Core and Builtins<22>-Footnote-153508521
Ref: Core and Builtins<22>-Footnote-163508577
Ref: Core and Builtins<22>-Footnote-173508633
Ref: Core and Builtins<22>-Footnote-183508689
Ref: Core and Builtins<22>-Footnote-193508745
Ref: Core and Builtins<22>-Footnote-203508801
Ref: Core and Builtins<22>-Footnote-213508857
Ref: Core and Builtins<22>-Footnote-223508923
Ref: Core and Builtins<22>-Footnote-233508979
Ref: Core and Builtins<22>-Footnote-243509035
Ref: Core and Builtins<22>-Footnote-253509091
Ref: Core and Builtins<22>-Footnote-263509147
Ref: Core and Builtins<22>-Footnote-273509203
Ref: Core and Builtins<22>-Footnote-283509259
Ref: Core and Builtins<22>-Footnote-293509315
Ref: Core and Builtins<22>-Footnote-303509371
Ref: Core and Builtins<22>-Footnote-313509427
Ref: Core and Builtins<22>-Footnote-323509483
Ref: Core and Builtins<22>-Footnote-333509526
Ref: Core and Builtins<22>-Footnote-343509582
Ref: Core and Builtins<22>-Footnote-353509638
Ref: Core and Builtins<22>-Footnote-363509694
Ref: Core and Builtins<22>-Footnote-373509760
Ref: Core and Builtins<22>-Footnote-383509816
Ref: Core and Builtins<22>-Footnote-393509872
Ref: Core and Builtins<22>-Footnote-403509938
Ref: Core and Builtins<22>-Footnote-413510004
Ref: Core and Builtins<22>-Footnote-423510070
Ref: Core and Builtins<22>-Footnote-433510136
Ref: Core and Builtins<22>-Footnote-443510202
Ref: Core and Builtins<22>-Footnote-453510268
Ref: Core and Builtins<22>-Footnote-463510334
Ref: Core and Builtins<22>-Footnote-473510400
Ref: Core and Builtins<22>-Footnote-483510466
Ref: Core and Builtins<22>-Footnote-493510532
Ref: Core and Builtins<22>-Footnote-503510598
Ref: Core and Builtins<22>-Footnote-513510664
Ref: Core and Builtins<22>-Footnote-523510730
Ref: Core and Builtins<22>-Footnote-533510796
Ref: Core and Builtins<22>-Footnote-543510862
Node: Library<21>3510928
Ref: whatsnew/changelog id1733511052
Ref: 16ff3511052
Ref: Library<21>-Footnote-13528540
Ref: Library<21>-Footnote-23528595
Ref: Library<21>-Footnote-33528650
Ref: Library<21>-Footnote-43528705
Ref: Library<21>-Footnote-53528760
Ref: Library<21>-Footnote-63528815
Ref: Library<21>-Footnote-73528870
Ref: Library<21>-Footnote-83528925
Ref: Library<21>-Footnote-93528980
Ref: Library<21>-Footnote-103529035
Ref: Library<21>-Footnote-113529091
Ref: Library<21>-Footnote-123529147
Ref: Library<21>-Footnote-133529203
Ref: Library<21>-Footnote-143529259
Ref: Library<21>-Footnote-153529315
Ref: Library<21>-Footnote-163529371
Ref: Library<21>-Footnote-173529427
Ref: Library<21>-Footnote-183529483
Ref: Library<21>-Footnote-193529539
Ref: Library<21>-Footnote-203529595
Ref: Library<21>-Footnote-213529651
Ref: Library<21>-Footnote-223529707
Ref: Library<21>-Footnote-233529763
Ref: Library<21>-Footnote-243529829
Ref: Library<21>-Footnote-253529885
Ref: Library<21>-Footnote-263529941
Ref: Library<21>-Footnote-273529984
Ref: Library<21>-Footnote-283530040
Ref: Library<21>-Footnote-293530096
Ref: Library<21>-Footnote-303530152
Ref: Library<21>-Footnote-313530208
Ref: Library<21>-Footnote-323530251
Ref: Library<21>-Footnote-333530307
Ref: Library<21>-Footnote-343530363
Ref: Library<21>-Footnote-353530419
Ref: Library<21>-Footnote-363530475
Ref: Library<21>-Footnote-373530531
Ref: Library<21>-Footnote-383530587
Ref: Library<21>-Footnote-393530643
Ref: Library<21>-Footnote-403530699
Ref: Library<21>-Footnote-413530755
Ref: Library<21>-Footnote-423530811
Ref: Library<21>-Footnote-433530867
Ref: Library<21>-Footnote-443530923
Ref: Library<21>-Footnote-453530979
Ref: Library<21>-Footnote-463531035
Ref: Library<21>-Footnote-473531091
Ref: Library<21>-Footnote-483531147
Ref: Library<21>-Footnote-493531203
Ref: Library<21>-Footnote-503531259
Ref: Library<21>-Footnote-513531315
Ref: Library<21>-Footnote-523531371
Ref: Library<21>-Footnote-533531427
Ref: Library<21>-Footnote-543531483
Ref: Library<21>-Footnote-553531539
Ref: Library<21>-Footnote-563531605
Ref: Library<21>-Footnote-573531661
Ref: Library<21>-Footnote-583531717
Ref: Library<21>-Footnote-593531773
Ref: Library<21>-Footnote-603531829
Ref: Library<21>-Footnote-613531885
Ref: Library<21>-Footnote-623531941
Ref: Library<21>-Footnote-633531997
Ref: Library<21>-Footnote-643532053
Ref: Library<21>-Footnote-653532109
Ref: Library<21>-Footnote-663532152
Ref: Library<21>-Footnote-673532208
Ref: Library<21>-Footnote-683532264
Ref: Library<21>-Footnote-693532320
Ref: Library<21>-Footnote-703532376
Ref: Library<21>-Footnote-713532432
Ref: Library<21>-Footnote-723532488
Ref: Library<21>-Footnote-733532544
Ref: Library<21>-Footnote-743532600
Ref: Library<21>-Footnote-753532666
Ref: Library<21>-Footnote-763532722
Ref: Library<21>-Footnote-773532778
Ref: Library<21>-Footnote-783532844
Ref: Library<21>-Footnote-793532910
Ref: Library<21>-Footnote-803532953
Ref: Library<21>-Footnote-813533019
Ref: Library<21>-Footnote-823533085
Ref: Library<21>-Footnote-833533151
Ref: Library<21>-Footnote-843533217
Ref: Library<21>-Footnote-853533283
Ref: Library<21>-Footnote-863533349
Ref: Library<21>-Footnote-873533415
Ref: Library<21>-Footnote-883533481
Ref: Library<21>-Footnote-893533547
Ref: Library<21>-Footnote-903533613
Ref: Library<21>-Footnote-913533679
Ref: Library<21>-Footnote-923533745
Ref: Library<21>-Footnote-933533811
Ref: Library<21>-Footnote-943533877
Ref: Library<21>-Footnote-953533943
Ref: Library<21>-Footnote-963534009
Ref: Library<21>-Footnote-973534075
Ref: Library<21>-Footnote-983534141
Ref: Library<21>-Footnote-993534207
Ref: Library<21>-Footnote-1003534273
Ref: Library<21>-Footnote-1013534340
Ref: Library<21>-Footnote-1023534407
Ref: Library<21>-Footnote-1033534474
Ref: Library<21>-Footnote-1043534541
Ref: Library<21>-Footnote-1053534608
Ref: Library<21>-Footnote-1063534675
Ref: Library<21>-Footnote-1073534742
Ref: Library<21>-Footnote-1083534809
Ref: Library<21>-Footnote-1093534876
Ref: Library<21>-Footnote-1103534943
Ref: Library<21>-Footnote-1113535010
Ref: Library<21>-Footnote-1123535077
Ref: Library<21>-Footnote-1133535144
Ref: Library<21>-Footnote-1143535211
Ref: Library<21>-Footnote-1153535278
Ref: Library<21>-Footnote-1163535345
Ref: Library<21>-Footnote-1173535412
Ref: Library<21>-Footnote-1183535479
Node: Documentation<16>3535546
Ref: whatsnew/changelog id1743535658
Ref: 170f3535658
Ref: Documentation<16>-Footnote-13537200
Ref: Documentation<16>-Footnote-23537255
Ref: Documentation<16>-Footnote-33537310
Ref: Documentation<16>-Footnote-43537365
Ref: Documentation<16>-Footnote-53537420
Ref: Documentation<16>-Footnote-63537485
Ref: Documentation<16>-Footnote-73537550
Ref: Documentation<16>-Footnote-83537615
Ref: Documentation<16>-Footnote-93537680
Ref: Documentation<16>-Footnote-103537722
Ref: Documentation<16>-Footnote-113537765
Ref: Documentation<16>-Footnote-123537831
Ref: Documentation<16>-Footnote-133537897
Ref: Documentation<16>-Footnote-143537970
Node: Tests<19>3538036
Ref: whatsnew/changelog id1753538146
Ref: 17123538146
Ref: Tests<19>-Footnote-13539487
Ref: Tests<19>-Footnote-23539542
Ref: Tests<19>-Footnote-33539597
Ref: Tests<19>-Footnote-43539652
Ref: Tests<19>-Footnote-53539707
Ref: Tests<19>-Footnote-63539762
Ref: Tests<19>-Footnote-73539827
Ref: Tests<19>-Footnote-83539892
Node: Build<21>3539957
Ref: whatsnew/changelog id1763540061
Ref: 17153540061
Ref: Build<21>-Footnote-13540688
Ref: Build<21>-Footnote-23540743
Ref: Build<21>-Footnote-33540798
Ref: Build<21>-Footnote-43540863
Node: Windows<18>3540928
Ref: whatsnew/changelog id1773541032
Ref: 17163541032
Ref: Windows<18>-Footnote-13541662
Ref: Windows<18>-Footnote-23541727
Ref: Windows<18>-Footnote-33541792
Ref: Windows<18>-Footnote-43541857
Ref: Windows<18>-Footnote-53541922
Node: macOS<14>3541987
Ref: whatsnew/changelog id1783542097
Ref: 17173542097
Ref: macOS<14>-Footnote-13542227
Node: Tools/Demos<11>3542292
Ref: whatsnew/changelog id1793542400
Ref: 17183542400
Ref: Tools/Demos<11>-Footnote-13542957
Ref: Tools/Demos<11>-Footnote-23543012
Ref: Tools/Demos<11>-Footnote-33543067
Node: C API<20>3543122
Ref: whatsnew/changelog id1803543212
Ref: 17193543212
Ref: C API<20>-Footnote-13545355
Ref: C API<20>-Footnote-23545410
Ref: C API<20>-Footnote-33545465
Ref: C API<20>-Footnote-43545520
Ref: C API<20>-Footnote-53545575
Ref: C API<20>-Footnote-63545630
Ref: C API<20>-Footnote-73545672
Ref: C API<20>-Footnote-83545727
Ref: C API<20>-Footnote-93545782
Ref: C API<20>-Footnote-103545847
Ref: C API<20>-Footnote-113545913
Ref: C API<20>-Footnote-123545979
Ref: C API<20>-Footnote-133546045
Node: Python 3 11 0 alpha 73546111
Ref: whatsnew/changelog python-3-11-0-alpha-73546255
Ref: 171c3546255
Node: Core and Builtins<23>3546594
Ref: whatsnew/changelog id1813546693
Ref: 171d3546693
Ref: Core and Builtins<23>-Footnote-13552256
Ref: Core and Builtins<23>-Footnote-23552321
Ref: Core and Builtins<23>-Footnote-33552386
Ref: Core and Builtins<23>-Footnote-43552451
Ref: Core and Builtins<23>-Footnote-53552516
Ref: Core and Builtins<23>-Footnote-63552581
Ref: Core and Builtins<23>-Footnote-73552646
Ref: Core and Builtins<23>-Footnote-83552711
Ref: Core and Builtins<23>-Footnote-93552776
Ref: Core and Builtins<23>-Footnote-103552841
Ref: Core and Builtins<23>-Footnote-113552907
Ref: Core and Builtins<23>-Footnote-123552973
Ref: Core and Builtins<23>-Footnote-133553039
Ref: Core and Builtins<23>-Footnote-143553105
Ref: Core and Builtins<23>-Footnote-153553171
Ref: Core and Builtins<23>-Footnote-163553237
Ref: Core and Builtins<23>-Footnote-173553303
Ref: Core and Builtins<23>-Footnote-183553369
Ref: Core and Builtins<23>-Footnote-193553435
Ref: Core and Builtins<23>-Footnote-203553501
Ref: Core and Builtins<23>-Footnote-213553567
Ref: Core and Builtins<23>-Footnote-223553633
Ref: Core and Builtins<23>-Footnote-233553699
Ref: Core and Builtins<23>-Footnote-243553765
Ref: Core and Builtins<23>-Footnote-253553831
Ref: Core and Builtins<23>-Footnote-263553897
Ref: Core and Builtins<23>-Footnote-273553963
Ref: Core and Builtins<23>-Footnote-283554029
Ref: Core and Builtins<23>-Footnote-293554095
Ref: Core and Builtins<23>-Footnote-303554161
Ref: Core and Builtins<23>-Footnote-313554227
Ref: Core and Builtins<23>-Footnote-323554293
Ref: Core and Builtins<23>-Footnote-333554359
Node: Library<22>3554425
Ref: whatsnew/changelog id1823554550
Ref: 17213554550
Ref: Library<22>-Footnote-13568718
Ref: Library<22>-Footnote-23568783
Ref: Library<22>-Footnote-33568848
Ref: Library<22>-Footnote-43568913
Ref: Library<22>-Footnote-53568978
Ref: Library<22>-Footnote-63569043
Ref: Library<22>-Footnote-73569107
Ref: Library<22>-Footnote-83569172
Ref: Library<22>-Footnote-93569237
Ref: Library<22>-Footnote-103569302
Ref: Library<22>-Footnote-113569368
Ref: Library<22>-Footnote-123569434
Ref: Library<22>-Footnote-133569500
Ref: Library<22>-Footnote-143569566
Ref: Library<22>-Footnote-153569609
Ref: Library<22>-Footnote-163569675
Ref: Library<22>-Footnote-173569741
Ref: Library<22>-Footnote-183569807
Ref: Library<22>-Footnote-193569850
Ref: Library<22>-Footnote-203569916
Ref: Library<22>-Footnote-213569982
Ref: Library<22>-Footnote-223570048
Ref: Library<22>-Footnote-233570091
Ref: Library<22>-Footnote-243570157
Ref: Library<22>-Footnote-253570223
Ref: Library<22>-Footnote-263570289
Ref: Library<22>-Footnote-273570355
Ref: Library<22>-Footnote-283570421
Ref: Library<22>-Footnote-293570487
Ref: Library<22>-Footnote-303570554
Ref: Library<22>-Footnote-313570620
Ref: Library<22>-Footnote-323570686
Ref: Library<22>-Footnote-333570752
Ref: Library<22>-Footnote-343570818
Ref: Library<22>-Footnote-353570861
Ref: Library<22>-Footnote-363570927
Ref: Library<22>-Footnote-373570993
Ref: Library<22>-Footnote-383571058
Ref: Library<22>-Footnote-393571124
Ref: Library<22>-Footnote-403571190
Ref: Library<22>-Footnote-413571256
Ref: Library<22>-Footnote-423571322
Ref: Library<22>-Footnote-433571365
Ref: Library<22>-Footnote-443571431
Ref: Library<22>-Footnote-453571497
Ref: Library<22>-Footnote-463571563
Ref: Library<22>-Footnote-473571629
Ref: Library<22>-Footnote-483571695
Ref: Library<22>-Footnote-493571761
Ref: Library<22>-Footnote-503571827
Ref: Library<22>-Footnote-513571893
Ref: Library<22>-Footnote-523571959
Ref: Library<22>-Footnote-533572025
Ref: Library<22>-Footnote-543572091
Ref: Library<22>-Footnote-553572157
Ref: Library<22>-Footnote-563572223
Ref: Library<22>-Footnote-573572289
Ref: Library<22>-Footnote-583572355
Ref: Library<22>-Footnote-593572421
Ref: Library<22>-Footnote-603572464
Ref: Library<22>-Footnote-613572531
Ref: Library<22>-Footnote-623572597
Ref: Library<22>-Footnote-633572663
Ref: Library<22>-Footnote-643572729
Ref: Library<22>-Footnote-653572795
Ref: Library<22>-Footnote-663572861
Ref: Library<22>-Footnote-673572927
Ref: Library<22>-Footnote-683572993
Ref: Library<22>-Footnote-693573059
Ref: Library<22>-Footnote-703573125
Ref: Library<22>-Footnote-713573191
Ref: Library<22>-Footnote-723573257
Ref: Library<22>-Footnote-733573323
Ref: Library<22>-Footnote-743573389
Ref: Library<22>-Footnote-753573455
Ref: Library<22>-Footnote-763573521
Ref: Library<22>-Footnote-773573587
Ref: Library<22>-Footnote-783573653
Ref: Library<22>-Footnote-793573719
Ref: Library<22>-Footnote-803573785
Ref: Library<22>-Footnote-813573851
Ref: Library<22>-Footnote-823573917
Ref: Library<22>-Footnote-833573983
Ref: Library<22>-Footnote-843574026
Ref: Library<22>-Footnote-853574092
Ref: Library<22>-Footnote-863574158
Ref: Library<22>-Footnote-873574224
Ref: Library<22>-Footnote-883574290
Node: Documentation<17>3574356
Ref: whatsnew/changelog id1833574469
Ref: 172d3574469
Ref: Documentation<17>-Footnote-13575601
Ref: Documentation<17>-Footnote-23575666
Ref: Documentation<17>-Footnote-33575731
Ref: Documentation<17>-Footnote-43575773
Ref: Documentation<17>-Footnote-53575838
Ref: Documentation<17>-Footnote-63575903
Ref: Documentation<17>-Footnote-73575968
Ref: Documentation<17>-Footnote-83576033
Node: Tests<20>3576098
Ref: whatsnew/changelog id1843576209
Ref: 17303576209
Ref: Tests<20>-Footnote-13577172
Ref: Tests<20>-Footnote-23577237
Ref: Tests<20>-Footnote-33577302
Ref: Tests<20>-Footnote-43577367
Ref: Tests<20>-Footnote-53577432
Ref: Tests<20>-Footnote-63577497
Ref: Tests<20>-Footnote-73577562
Ref: Tests<20>-Footnote-83577627
Node: Build<22>3577669
Ref: whatsnew/changelog id1853577774
Ref: 17313577774
Ref: Build<22>-Footnote-13579060
Ref: Build<22>-Footnote-23579125
Ref: Build<22>-Footnote-33579190
Ref: Build<22>-Footnote-43579255
Ref: Build<22>-Footnote-53579320
Ref: Build<22>-Footnote-63579385
Ref: Build<22>-Footnote-73579450
Ref: Build<22>-Footnote-83579515
Ref: Build<22>-Footnote-93579580
Node: Windows<19>3579645
Ref: whatsnew/changelog id1863579750
Ref: 17333579750
Ref: Windows<19>-Footnote-13580941
Ref: Windows<19>-Footnote-23581006
Ref: Windows<19>-Footnote-33581076
Ref: Windows<19>-Footnote-43581141
Ref: Windows<19>-Footnote-53581206
Ref: Windows<19>-Footnote-63581248
Ref: Windows<19>-Footnote-73581313
Ref: Windows<19>-Footnote-83581378
Ref: Windows<19>-Footnote-93581443
Ref: Windows<19>-Footnote-103581512
Ref: Windows<19>-Footnote-113581583
Ref: Windows<19>-Footnote-123581649
Node: macOS<15>3581720
Ref: whatsnew/changelog id1873581831
Ref: 17343581831
Ref: macOS<15>-Footnote-13582166
Ref: macOS<15>-Footnote-23582231
Node: Tools/Demos<12>3582296
Ref: whatsnew/changelog id1883582405
Ref: 17353582405
Ref: Tools/Demos<12>-Footnote-13582606
Node: C API<21>3582671
Ref: whatsnew/changelog id1893582762
Ref: 17363582762
Ref: C API<21>-Footnote-13585019
Ref: C API<21>-Footnote-23585084
Ref: C API<21>-Footnote-33585149
Ref: C API<21>-Footnote-43585214
Ref: C API<21>-Footnote-53585279
Ref: C API<21>-Footnote-63585344
Ref: C API<21>-Footnote-73585409
Ref: C API<21>-Footnote-83585474
Node: Python 3 11 0 alpha 63585539
Ref: whatsnew/changelog python-3-11-0-alpha-63585684
Ref: 17393585684
Node: Core and Builtins<24>3585989
Ref: whatsnew/changelog id1903586088
Ref: 173a3586088
Ref: Core and Builtins<24>-Footnote-13593063
Ref: Core and Builtins<24>-Footnote-23593128
Ref: Core and Builtins<24>-Footnote-33593193
Ref: Core and Builtins<24>-Footnote-43593258
Ref: Core and Builtins<24>-Footnote-53593323
Ref: Core and Builtins<24>-Footnote-63593388
Ref: Core and Builtins<24>-Footnote-73593453
Ref: Core and Builtins<24>-Footnote-83593518
Ref: Core and Builtins<24>-Footnote-93593583
Ref: Core and Builtins<24>-Footnote-103593648
Ref: Core and Builtins<24>-Footnote-113593714
Ref: Core and Builtins<24>-Footnote-123593780
Ref: Core and Builtins<24>-Footnote-133593846
Ref: Core and Builtins<24>-Footnote-143593912
Ref: Core and Builtins<24>-Footnote-153593978
Ref: Core and Builtins<24>-Footnote-163594044
Ref: Core and Builtins<24>-Footnote-173594110
Ref: Core and Builtins<24>-Footnote-183594176
Ref: Core and Builtins<24>-Footnote-193594242
Ref: Core and Builtins<24>-Footnote-203594308
Ref: Core and Builtins<24>-Footnote-213594374
Ref: Core and Builtins<24>-Footnote-223594440
Ref: Core and Builtins<24>-Footnote-233594506
Ref: Core and Builtins<24>-Footnote-243594572
Ref: Core and Builtins<24>-Footnote-253594638
Ref: Core and Builtins<24>-Footnote-263594704
Ref: Core and Builtins<24>-Footnote-273594770
Ref: Core and Builtins<24>-Footnote-283594836
Ref: Core and Builtins<24>-Footnote-293594902
Ref: Core and Builtins<24>-Footnote-303594968
Ref: Core and Builtins<24>-Footnote-313595034
Ref: Core and Builtins<24>-Footnote-323595100
Ref: Core and Builtins<24>-Footnote-333595166
Ref: Core and Builtins<24>-Footnote-343595232
Ref: Core and Builtins<24>-Footnote-353595298
Ref: Core and Builtins<24>-Footnote-363595364
Ref: Core and Builtins<24>-Footnote-373595430
Ref: Core and Builtins<24>-Footnote-383595496
Ref: Core and Builtins<24>-Footnote-393595562
Ref: Core and Builtins<24>-Footnote-403595628
Ref: Core and Builtins<24>-Footnote-413595694
Ref: Core and Builtins<24>-Footnote-423595760
Ref: Core and Builtins<24>-Footnote-433595826
Ref: Core and Builtins<24>-Footnote-443595892
Ref: Core and Builtins<24>-Footnote-453595958
Ref: Core and Builtins<24>-Footnote-463596024
Ref: Core and Builtins<24>-Footnote-473596090
Ref: Core and Builtins<24>-Footnote-483596156
Node: Library<23>3596222
Ref: whatsnew/changelog id1913596347
Ref: 17403596347
Ref: Library<23>-Footnote-13604545
Ref: Library<23>-Footnote-23604610
Ref: Library<23>-Footnote-33604675
Ref: Library<23>-Footnote-43604740
Ref: Library<23>-Footnote-53604805
Ref: Library<23>-Footnote-63604870
Ref: Library<23>-Footnote-73604935
Ref: Library<23>-Footnote-83605000
Ref: Library<23>-Footnote-93605065
Ref: Library<23>-Footnote-103605130
Ref: Library<23>-Footnote-113605196
Ref: Library<23>-Footnote-123605262
Ref: Library<23>-Footnote-133605328
Ref: Library<23>-Footnote-143605394
Ref: Library<23>-Footnote-153605460
Ref: Library<23>-Footnote-163605526
Ref: Library<23>-Footnote-173605592
Ref: Library<23>-Footnote-183605658
Ref: Library<23>-Footnote-193605724
Ref: Library<23>-Footnote-203605790
Ref: Library<23>-Footnote-213605856
Ref: Library<23>-Footnote-223605922
Ref: Library<23>-Footnote-233605988
Ref: Library<23>-Footnote-243606054
Ref: Library<23>-Footnote-253606120
Ref: Library<23>-Footnote-263606186
Ref: Library<23>-Footnote-273606252
Ref: Library<23>-Footnote-283606318
Ref: Library<23>-Footnote-293606384
Ref: Library<23>-Footnote-303606450
Ref: Library<23>-Footnote-313606516
Ref: Library<23>-Footnote-323606582
Ref: Library<23>-Footnote-333606648
Ref: Library<23>-Footnote-343606714
Ref: Library<23>-Footnote-353606757
Ref: Library<23>-Footnote-363606823
Ref: Library<23>-Footnote-373606889
Ref: Library<23>-Footnote-383606955
Ref: Library<23>-Footnote-393607021
Ref: Library<23>-Footnote-403607087
Ref: Library<23>-Footnote-413607153
Ref: Library<23>-Footnote-423607219
Ref: Library<23>-Footnote-433607285
Ref: Library<23>-Footnote-443607351
Ref: Library<23>-Footnote-453607417
Ref: Library<23>-Footnote-463607483
Ref: Library<23>-Footnote-473607549
Ref: Library<23>-Footnote-483607615
Node: Documentation<18>3607681
Ref: whatsnew/changelog id1923607794
Ref: 174b3607794
Ref: Documentation<18>-Footnote-13608013
Node: Tests<21>3608078
Ref: whatsnew/changelog id1933608189
Ref: 174c3608189
Ref: Tests<21>-Footnote-13609158
Ref: Tests<21>-Footnote-23609223
Ref: Tests<21>-Footnote-33609288
Ref: Tests<21>-Footnote-43609353
Ref: Tests<21>-Footnote-53609418
Node: Build<23>3609483
Ref: whatsnew/changelog id1943609588
Ref: 174d3609588
Ref: Build<23>-Footnote-13611014
Ref: Build<23>-Footnote-23611079
Ref: Build<23>-Footnote-33611144
Ref: Build<23>-Footnote-43611209
Ref: Build<23>-Footnote-53611274
Ref: Build<23>-Footnote-63611339
Ref: Build<23>-Footnote-73611404
Node: Windows<20>3611469
Ref: whatsnew/changelog id1953611573
Ref: 174e3611573
Ref: Windows<20>-Footnote-13612231
Ref: Windows<20>-Footnote-23612296
Ref: Windows<20>-Footnote-33612361
Node: IDLE<14>3612426
Ref: whatsnew/changelog id1963612530
Ref: 174f3612530
Ref: IDLE<14>-Footnote-13612810
Ref: IDLE<14>-Footnote-23612875
Node: C API<22>3612940
Ref: whatsnew/changelog id1973613024
Ref: 17503613024
Ref: C API<22>-Footnote-13613967
Ref: C API<22>-Footnote-23614032
Ref: C API<22>-Footnote-33614097
Ref: C API<22>-Footnote-43614162
Ref: C API<22>-Footnote-53614227
Node: Python 3 11 0 alpha 53614292
Ref: whatsnew/changelog python-3-11-0-alpha-53614437
Ref: 17513614437
Node: Core and Builtins<25>3614762
Ref: whatsnew/changelog id1983614861
Ref: 17523614861
Ref: Core and Builtins<25>-Footnote-13619906
Ref: Core and Builtins<25>-Footnote-23619971
Ref: Core and Builtins<25>-Footnote-33620036
Ref: Core and Builtins<25>-Footnote-43620101
Ref: Core and Builtins<25>-Footnote-53620166
Ref: Core and Builtins<25>-Footnote-63620231
Ref: Core and Builtins<25>-Footnote-73620296
Ref: Core and Builtins<25>-Footnote-83620361
Ref: Core and Builtins<25>-Footnote-93620426
Ref: Core and Builtins<25>-Footnote-103620491
Ref: Core and Builtins<25>-Footnote-113620557
Ref: Core and Builtins<25>-Footnote-123620623
Ref: Core and Builtins<25>-Footnote-133620689
Ref: Core and Builtins<25>-Footnote-143620732
Ref: Core and Builtins<25>-Footnote-153620798
Ref: Core and Builtins<25>-Footnote-163620864
Ref: Core and Builtins<25>-Footnote-173620930
Ref: Core and Builtins<25>-Footnote-183620996
Ref: Core and Builtins<25>-Footnote-193621062
Ref: Core and Builtins<25>-Footnote-203621128
Ref: Core and Builtins<25>-Footnote-213621194
Ref: Core and Builtins<25>-Footnote-223621260
Ref: Core and Builtins<25>-Footnote-233621326
Ref: Core and Builtins<25>-Footnote-243621392
Ref: Core and Builtins<25>-Footnote-253621458
Ref: Core and Builtins<25>-Footnote-263621524
Ref: Core and Builtins<25>-Footnote-273621590
Node: Library<24>3621656
Ref: whatsnew/changelog id1993621781
Ref: 17553621781
Ref: Library<24>-Footnote-13627705
Ref: Library<24>-Footnote-23627770
Ref: Library<24>-Footnote-33627835
Ref: Library<24>-Footnote-43627900
Ref: Library<24>-Footnote-53627965
Ref: Library<24>-Footnote-63628030
Ref: Library<24>-Footnote-73628095
Ref: Library<24>-Footnote-83628160
Ref: Library<24>-Footnote-93628225
Ref: Library<24>-Footnote-103628290
Ref: Library<24>-Footnote-113628356
Ref: Library<24>-Footnote-123628422
Ref: Library<24>-Footnote-133628488
Ref: Library<24>-Footnote-143628554
Ref: Library<24>-Footnote-153628620
Ref: Library<24>-Footnote-163628686
Ref: Library<24>-Footnote-173628752
Ref: Library<24>-Footnote-183628818
Ref: Library<24>-Footnote-193628884
Ref: Library<24>-Footnote-203628950
Ref: Library<24>-Footnote-213629016
Ref: Library<24>-Footnote-223629082
Ref: Library<24>-Footnote-233629148
Ref: Library<24>-Footnote-243629214
Ref: Library<24>-Footnote-253629280
Ref: Library<24>-Footnote-263629346
Ref: Library<24>-Footnote-273629412
Ref: Library<24>-Footnote-283629478
Ref: Library<24>-Footnote-293629544
Ref: Library<24>-Footnote-303629610
Ref: Library<24>-Footnote-313629676
Ref: Library<24>-Footnote-323629742
Ref: Library<24>-Footnote-333629808
Ref: Library<24>-Footnote-343629874
Ref: Library<24>-Footnote-353629940
Ref: Library<24>-Footnote-363630006
Ref: Library<24>-Footnote-373630072
Node: Documentation<19>3630138
Ref: whatsnew/changelog id2003630251
Ref: 17593630251
Ref: Documentation<19>-Footnote-13630440
Node: Tests<22>3630505
Ref: whatsnew/changelog id2013630616
Ref: 175a3630616
Ref: Tests<22>-Footnote-13632761
Ref: Tests<22>-Footnote-23632826
Ref: Tests<22>-Footnote-33632891
Ref: Tests<22>-Footnote-43632956
Ref: Tests<22>-Footnote-53633021
Ref: Tests<22>-Footnote-63633086
Ref: Tests<22>-Footnote-73633151
Ref: Tests<22>-Footnote-83633216
Ref: Tests<22>-Footnote-93633281
Ref: Tests<22>-Footnote-103633346
Ref: Tests<22>-Footnote-113633412
Node: Build<24>3633478
Ref: whatsnew/changelog id2023633583
Ref: 175b3633583
Ref: Build<24>-Footnote-13635313
Ref: Build<24>-Footnote-23635378
Ref: Build<24>-Footnote-33635443
Ref: Build<24>-Footnote-43635508
Ref: Build<24>-Footnote-53635573
Ref: Build<24>-Footnote-63635638
Ref: Build<24>-Footnote-73635703
Ref: Build<24>-Footnote-83635768
Ref: Build<24>-Footnote-93635833
Ref: Build<24>-Footnote-103635898
Node: Windows<21>3635964
Ref: whatsnew/changelog id2033636069
Ref: 175c3636069
Ref: Windows<21>-Footnote-13636597
Ref: Windows<21>-Footnote-23636662
Ref: Windows<21>-Footnote-33636727
Node: macOS<16>3636792
Ref: whatsnew/changelog id2043636896
Ref: 175d3636896
Ref: macOS<16>-Footnote-13637026
Node: IDLE<15>3637091
Ref: whatsnew/changelog id2053637193
Ref: 175e3637193
Ref: IDLE<15>-Footnote-13637580
Node: C API<23>3637645
Ref: whatsnew/changelog id2063637729
Ref: 175f3637729
Ref: C API<23>-Footnote-13638620
Ref: C API<23>-Footnote-23638685
Ref: C API<23>-Footnote-33638750
Ref: C API<23>-Footnote-43638815
Ref: C API<23>-Footnote-53638880
Node: Python 3 11 0 alpha 43638945
Ref: whatsnew/changelog python-3-11-0-alpha-43639090
Ref: 17603639090
Node: Core and Builtins<26>3639397
Ref: whatsnew/changelog id2073639496
Ref: 17613639496
Ref: Core and Builtins<26>-Footnote-13646264
Ref: Core and Builtins<26>-Footnote-23646329
Ref: Core and Builtins<26>-Footnote-33646394
Ref: Core and Builtins<26>-Footnote-43646459
Ref: Core and Builtins<26>-Footnote-53646524
Ref: Core and Builtins<26>-Footnote-63646589
Ref: Core and Builtins<26>-Footnote-73646654
Ref: Core and Builtins<26>-Footnote-83646719
Ref: Core and Builtins<26>-Footnote-93646784
Ref: Core and Builtins<26>-Footnote-103646849
Ref: Core and Builtins<26>-Footnote-113646915
Ref: Core and Builtins<26>-Footnote-123646981
Ref: Core and Builtins<26>-Footnote-133647047
Ref: Core and Builtins<26>-Footnote-143647113
Ref: Core and Builtins<26>-Footnote-153647179
Ref: Core and Builtins<26>-Footnote-163647245
Ref: Core and Builtins<26>-Footnote-173647311
Ref: Core and Builtins<26>-Footnote-183647377
Ref: Core and Builtins<26>-Footnote-193647443
Ref: Core and Builtins<26>-Footnote-203647509
Ref: Core and Builtins<26>-Footnote-213647575
Ref: Core and Builtins<26>-Footnote-223647641
Ref: Core and Builtins<26>-Footnote-233647707
Ref: Core and Builtins<26>-Footnote-243647773
Ref: Core and Builtins<26>-Footnote-253647839
Ref: Core and Builtins<26>-Footnote-263647905
Ref: Core and Builtins<26>-Footnote-273647971
Ref: Core and Builtins<26>-Footnote-283648037
Ref: Core and Builtins<26>-Footnote-293648103
Ref: Core and Builtins<26>-Footnote-303648169
Ref: Core and Builtins<26>-Footnote-313648235
Ref: Core and Builtins<26>-Footnote-323648301
Ref: Core and Builtins<26>-Footnote-333648367
Ref: Core and Builtins<26>-Footnote-343648433
Ref: Core and Builtins<26>-Footnote-353648499
Ref: Core and Builtins<26>-Footnote-363648565
Ref: Core and Builtins<26>-Footnote-373648631
Ref: Core and Builtins<26>-Footnote-383648697
Ref: Core and Builtins<26>-Footnote-393648763
Ref: Core and Builtins<26>-Footnote-403648806
Ref: Core and Builtins<26>-Footnote-413648872
Node: Library<25>3648938
Ref: whatsnew/changelog id2083649063
Ref: 17633649063
Ref: Library<25>-Footnote-13656314
Ref: Library<25>-Footnote-23656379
Ref: Library<25>-Footnote-33656444
Ref: Library<25>-Footnote-43656509
Ref: Library<25>-Footnote-53656574
Ref: Library<25>-Footnote-63656639
Ref: Library<25>-Footnote-73656704
Ref: Library<25>-Footnote-83656769
Ref: Library<25>-Footnote-93656834
Ref: Library<25>-Footnote-103656899
Ref: Library<25>-Footnote-113656965
Ref: Library<25>-Footnote-123657031
Ref: Library<25>-Footnote-133657097
Ref: Library<25>-Footnote-143657163
Ref: Library<25>-Footnote-153657229
Ref: Library<25>-Footnote-163657295
Ref: Library<25>-Footnote-173657361
Ref: Library<25>-Footnote-183657427
Ref: Library<25>-Footnote-193657493
Ref: Library<25>-Footnote-203657559
Ref: Library<25>-Footnote-213657625
Ref: Library<25>-Footnote-223657691
Ref: Library<25>-Footnote-233657757
Ref: Library<25>-Footnote-243657823
Ref: Library<25>-Footnote-253657889
Ref: Library<25>-Footnote-263657955
Ref: Library<25>-Footnote-273658021
Ref: Library<25>-Footnote-283658087
Ref: Library<25>-Footnote-293658153
Ref: Library<25>-Footnote-303658219
Ref: Library<25>-Footnote-313658285
Ref: Library<25>-Footnote-323658351
Ref: Library<25>-Footnote-333658417
Ref: Library<25>-Footnote-343658483
Ref: Library<25>-Footnote-353658549
Ref: Library<25>-Footnote-363658615
Ref: Library<25>-Footnote-373658681
Ref: Library<25>-Footnote-383658747
Ref: Library<25>-Footnote-393658813
Ref: Library<25>-Footnote-403658879
Ref: Library<25>-Footnote-413658945
Ref: Library<25>-Footnote-423659011
Ref: Library<25>-Footnote-433659077
Ref: Library<25>-Footnote-443659143
Node: Documentation<20>3659209
Ref: whatsnew/changelog id2093659322
Ref: 17683659322
Ref: Documentation<20>-Footnote-13659818
Ref: Documentation<20>-Footnote-23659883
Ref: Documentation<20>-Footnote-33659948
Ref: Documentation<20>-Footnote-43660013
Node: Tests<23>3660078
Ref: whatsnew/changelog id2103660189
Ref: 176b3660189
Ref: Tests<23>-Footnote-13661117
Ref: Tests<23>-Footnote-23661182
Ref: Tests<23>-Footnote-33661247
Ref: Tests<23>-Footnote-43661312
Ref: Tests<23>-Footnote-53661377
Ref: Tests<23>-Footnote-63661442
Ref: Tests<23>-Footnote-73661507
Ref: Tests<23>-Footnote-83661572
Node: Build<25>3661637
Ref: whatsnew/changelog id2113661742
Ref: 176c3661742
Ref: Build<25>-Footnote-13663802
Ref: Build<25>-Footnote-23663867
Ref: Build<25>-Footnote-33663932
Ref: Build<25>-Footnote-43663997
Ref: Build<25>-Footnote-53664062
Ref: Build<25>-Footnote-63664127
Ref: Build<25>-Footnote-73664192
Ref: Build<25>-Footnote-83664257
Ref: Build<25>-Footnote-93664322
Ref: Build<25>-Footnote-103664387
Ref: Build<25>-Footnote-113664453
Ref: Build<25>-Footnote-123664519
Node: Windows<22>3664585
Ref: whatsnew/changelog id2123664690
Ref: 176d3664690
Ref: Windows<22>-Footnote-13664909
Node: macOS<17>3664974
Ref: whatsnew/changelog id2133665079
Ref: 176e3665079
Ref: macOS<17>-Footnote-13665317
Node: C API<24>3665382
Ref: whatsnew/changelog id2143665467
Ref: 176f3665467
Ref: C API<24>-Footnote-13666743
Ref: C API<24>-Footnote-23666808
Ref: C API<24>-Footnote-33666873
Ref: C API<24>-Footnote-43666938
Ref: C API<24>-Footnote-53667003
Node: Python 3 11 0 alpha 33667068
Ref: whatsnew/changelog python-3-11-0-alpha-33667213
Ref: 17713667213
Node: Core and Builtins<27>3667520
Ref: whatsnew/changelog id2153667619
Ref: 17723667619
Ref: Core and Builtins<27>-Footnote-13673241
Ref: Core and Builtins<27>-Footnote-23673306
Ref: Core and Builtins<27>-Footnote-33673371
Ref: Core and Builtins<27>-Footnote-43673436
Ref: Core and Builtins<27>-Footnote-53673501
Ref: Core and Builtins<27>-Footnote-63673566
Ref: Core and Builtins<27>-Footnote-73673631
Ref: Core and Builtins<27>-Footnote-83673696
Ref: Core and Builtins<27>-Footnote-93673761
Ref: Core and Builtins<27>-Footnote-103673826
Ref: Core and Builtins<27>-Footnote-113673892
Ref: Core and Builtins<27>-Footnote-123673958
Ref: Core and Builtins<27>-Footnote-133674024
Ref: Core and Builtins<27>-Footnote-143674090
Ref: Core and Builtins<27>-Footnote-153674156
Ref: Core and Builtins<27>-Footnote-163674222
Ref: Core and Builtins<27>-Footnote-173674288
Ref: Core and Builtins<27>-Footnote-183674354
Ref: Core and Builtins<27>-Footnote-193674420
Ref: Core and Builtins<27>-Footnote-203674486
Ref: Core and Builtins<27>-Footnote-213674552
Ref: Core and Builtins<27>-Footnote-223674618
Ref: Core and Builtins<27>-Footnote-233674661
Ref: Core and Builtins<27>-Footnote-243674727
Ref: Core and Builtins<27>-Footnote-253674793
Ref: Core and Builtins<27>-Footnote-263674859
Ref: Core and Builtins<27>-Footnote-273674925
Ref: Core and Builtins<27>-Footnote-283674991
Ref: Core and Builtins<27>-Footnote-293675057
Ref: Core and Builtins<27>-Footnote-303675123
Ref: Core and Builtins<27>-Footnote-313675189
Ref: Core and Builtins<27>-Footnote-323675255
Ref: Core and Builtins<27>-Footnote-333675321
Ref: Core and Builtins<27>-Footnote-343675387
Node: Library<26>3675453
Ref: whatsnew/changelog id2163675578
Ref: 17743675578
Ref: Library<26>-Footnote-13681536
Ref: Library<26>-Footnote-23681601
Ref: Library<26>-Footnote-33681666
Ref: Library<26>-Footnote-43681731
Ref: Library<26>-Footnote-53681796
Ref: Library<26>-Footnote-63681861
Ref: Library<26>-Footnote-73681926
Ref: Library<26>-Footnote-83681991
Ref: Library<26>-Footnote-93682056
Ref: Library<26>-Footnote-103682121
Ref: Library<26>-Footnote-113682187
Ref: Library<26>-Footnote-123682253
Ref: Library<26>-Footnote-133682319
Ref: Library<26>-Footnote-143682385
Ref: Library<26>-Footnote-153682451
Ref: Library<26>-Footnote-163682517
Ref: Library<26>-Footnote-173682583
Ref: Library<26>-Footnote-183682649
Ref: Library<26>-Footnote-193682715
Ref: Library<26>-Footnote-203682781
Ref: Library<26>-Footnote-213682847
Ref: Library<26>-Footnote-223682913
Ref: Library<26>-Footnote-233682979
Ref: Library<26>-Footnote-243683045
Ref: Library<26>-Footnote-253683111
Ref: Library<26>-Footnote-263683177
Ref: Library<26>-Footnote-273683243
Ref: Library<26>-Footnote-283683309
Ref: Library<26>-Footnote-293683375
Ref: Library<26>-Footnote-303683441
Ref: Library<26>-Footnote-313683507
Ref: Library<26>-Footnote-323683550
Ref: Library<26>-Footnote-333683616
Ref: Library<26>-Footnote-343683682
Ref: Library<26>-Footnote-353683748
Ref: Library<26>-Footnote-363683814
Node: Documentation<21>3683880
Ref: whatsnew/changelog id2173683993
Ref: 17763683993
Ref: Documentation<21>-Footnote-13685301
Ref: Documentation<21>-Footnote-23685366
Ref: Documentation<21>-Footnote-33685431
Ref: Documentation<21>-Footnote-43685496
Ref: Documentation<21>-Footnote-53685561
Ref: Documentation<21>-Footnote-63685626
Ref: Documentation<21>-Footnote-73685691
Ref: Documentation<21>-Footnote-83685756
Ref: Documentation<21>-Footnote-93685821
Node: Tests<24>3685886
Ref: whatsnew/changelog id2183685997
Ref: 17773685997
Ref: Tests<24>-Footnote-13686804
Ref: Tests<24>-Footnote-23686869
Ref: Tests<24>-Footnote-33686934
Ref: Tests<24>-Footnote-43686999
Ref: Tests<24>-Footnote-53687064
Ref: Tests<24>-Footnote-63687129
Node: Build<26>3687194
Ref: whatsnew/changelog id2193687299
Ref: 17783687299
Ref: Build<26>-Footnote-13693093
Ref: Build<26>-Footnote-23693158
Ref: Build<26>-Footnote-33693223
Ref: Build<26>-Footnote-43693288
Ref: Build<26>-Footnote-53693353
Ref: Build<26>-Footnote-63693418
Ref: Build<26>-Footnote-73693483
Ref: Build<26>-Footnote-83693548
Ref: Build<26>-Footnote-93693613
Ref: Build<26>-Footnote-103693678
Ref: Build<26>-Footnote-113693744
Ref: Build<26>-Footnote-123693810
Ref: Build<26>-Footnote-133693876
Ref: Build<26>-Footnote-143693942
Ref: Build<26>-Footnote-153694008
Ref: Build<26>-Footnote-163694074
Ref: Build<26>-Footnote-173694140
Ref: Build<26>-Footnote-183694206
Ref: Build<26>-Footnote-193694272
Ref: Build<26>-Footnote-203694338
Ref: Build<26>-Footnote-213694404
Ref: Build<26>-Footnote-223694470
Ref: Build<26>-Footnote-233694536
Ref: Build<26>-Footnote-243694602
Ref: Build<26>-Footnote-253694668
Ref: Build<26>-Footnote-263694734
Ref: Build<26>-Footnote-273694800
Ref: Build<26>-Footnote-283694866
Ref: Build<26>-Footnote-293694932
Ref: Build<26>-Footnote-303694998
Ref: Build<26>-Footnote-313695064
Ref: Build<26>-Footnote-323695130
Ref: Build<26>-Footnote-333695196
Node: Windows<23>3695262
Ref: whatsnew/changelog id2203695367
Ref: 17793695367
Ref: Windows<23>-Footnote-13696548
Ref: Windows<23>-Footnote-23696613
Ref: Windows<23>-Footnote-33696678
Ref: Windows<23>-Footnote-43696743
Ref: Windows<23>-Footnote-53696808
Ref: Windows<23>-Footnote-63696873
Node: macOS<18>3696938
Ref: whatsnew/changelog id2213697043
Ref: 177a3697043
Ref: macOS<18>-Footnote-13697193
Node: C API<25>3697258
Ref: whatsnew/changelog id2223697343
Ref: 177b3697343
Ref: C API<25>-Footnote-13697548
Node: Python 3 11 0 alpha 23697613
Ref: whatsnew/changelog python-3-11-0-alpha-23697758
Ref: 177c3697758
Node: Core and Builtins<28>3698083
Ref: whatsnew/changelog id2233698182
Ref: 177d3698182
Ref: Core and Builtins<28>-Footnote-13703547
Ref: Core and Builtins<28>-Footnote-23703612
Ref: Core and Builtins<28>-Footnote-33703677
Ref: Core and Builtins<28>-Footnote-43703742
Ref: Core and Builtins<28>-Footnote-53703807
Ref: Core and Builtins<28>-Footnote-63703872
Ref: Core and Builtins<28>-Footnote-73703937
Ref: Core and Builtins<28>-Footnote-83704002
Ref: Core and Builtins<28>-Footnote-93704067
Ref: Core and Builtins<28>-Footnote-103704132
Ref: Core and Builtins<28>-Footnote-113704198
Ref: Core and Builtins<28>-Footnote-123704264
Ref: Core and Builtins<28>-Footnote-133704330
Ref: Core and Builtins<28>-Footnote-143704396
Ref: Core and Builtins<28>-Footnote-153704462
Ref: Core and Builtins<28>-Footnote-163704528
Ref: Core and Builtins<28>-Footnote-173704594
Ref: Core and Builtins<28>-Footnote-183704660
Ref: Core and Builtins<28>-Footnote-193704726
Ref: Core and Builtins<28>-Footnote-203704792
Ref: Core and Builtins<28>-Footnote-213704835
Ref: Core and Builtins<28>-Footnote-223704901
Ref: Core and Builtins<28>-Footnote-233704967
Ref: Core and Builtins<28>-Footnote-243705033
Ref: Core and Builtins<28>-Footnote-253705099
Ref: Core and Builtins<28>-Footnote-263705165
Node: Library<27>3705208
Ref: whatsnew/changelog id2243705333
Ref: 177f3705333
Ref: Library<27>-Footnote-13712878
Ref: Library<27>-Footnote-23712943
Ref: Library<27>-Footnote-33713008
Ref: Library<27>-Footnote-43713073
Ref: Library<27>-Footnote-53713138
Ref: Library<27>-Footnote-63713203
Ref: Library<27>-Footnote-73713268
Ref: Library<27>-Footnote-83713333
Ref: Library<27>-Footnote-93713398
Ref: Library<27>-Footnote-103713463
Ref: Library<27>-Footnote-113713529
Ref: Library<27>-Footnote-123713595
Ref: Library<27>-Footnote-133713661
Ref: Library<27>-Footnote-143713727
Ref: Library<27>-Footnote-153713793
Ref: Library<27>-Footnote-163713859
Ref: Library<27>-Footnote-173713925
Ref: Library<27>-Footnote-183713991
Ref: Library<27>-Footnote-193714057
Ref: Library<27>-Footnote-203714123
Ref: Library<27>-Footnote-213714189
Ref: Library<27>-Footnote-223714255
Ref: Library<27>-Footnote-233714321
Ref: Library<27>-Footnote-243714387
Ref: Library<27>-Footnote-253714453
Ref: Library<27>-Footnote-263714519
Ref: Library<27>-Footnote-273714585
Ref: Library<27>-Footnote-283714651
Ref: Library<27>-Footnote-293714717
Ref: Library<27>-Footnote-303714783
Ref: Library<27>-Footnote-313714849
Ref: Library<27>-Footnote-323714915
Ref: Library<27>-Footnote-333714981
Ref: Library<27>-Footnote-343715047
Ref: Library<27>-Footnote-353715113
Ref: Library<27>-Footnote-363715179
Ref: Library<27>-Footnote-373715245
Ref: Library<27>-Footnote-383715311
Ref: Library<27>-Footnote-393715377
Ref: Library<27>-Footnote-403715443
Ref: Library<27>-Footnote-413715509
Ref: Library<27>-Footnote-423715575
Ref: Library<27>-Footnote-433715641
Ref: Library<27>-Footnote-443715701
Ref: Library<27>-Footnote-453715767
Node: Documentation<22>3715833
Ref: whatsnew/changelog id2253715946
Ref: 17843715946
Ref: Documentation<22>-Footnote-13717438
Ref: Documentation<22>-Footnote-23717503
Ref: Documentation<22>-Footnote-33717568
Ref: Documentation<22>-Footnote-43717633
Ref: Documentation<22>-Footnote-53717698
Ref: Documentation<22>-Footnote-63717763
Ref: Documentation<22>-Footnote-73717828
Ref: Documentation<22>-Footnote-83717893
Ref: Documentation<22>-Footnote-93717958
Ref: Documentation<22>-Footnote-103718000
Ref: Documentation<22>-Footnote-113718066
Node: Tests<25>3718132
Ref: whatsnew/changelog id2263718243
Ref: 17883718243
Ref: Tests<25>-Footnote-13720503
Ref: Tests<25>-Footnote-23720568
Ref: Tests<25>-Footnote-33720633
Ref: Tests<25>-Footnote-43720698
Ref: Tests<25>-Footnote-53720763
Ref: Tests<25>-Footnote-63720828
Ref: Tests<25>-Footnote-73720893
Ref: Tests<25>-Footnote-83720958
Ref: Tests<25>-Footnote-93721023
Ref: Tests<25>-Footnote-103721088
Ref: Tests<25>-Footnote-113721154
Ref: Tests<25>-Footnote-123721220
Ref: Tests<25>-Footnote-133721286
Node: Build<27>3721352
Ref: whatsnew/changelog id2273721457
Ref: 17893721457
Ref: Build<27>-Footnote-13724132
Ref: Build<27>-Footnote-23724197
Ref: Build<27>-Footnote-33724262
Ref: Build<27>-Footnote-43724327
Ref: Build<27>-Footnote-53724392
Ref: Build<27>-Footnote-63724457
Ref: Build<27>-Footnote-73724522
Ref: Build<27>-Footnote-83724587
Ref: Build<27>-Footnote-93724652
Ref: Build<27>-Footnote-103724717
Ref: Build<27>-Footnote-113724783
Ref: Build<27>-Footnote-123724849
Ref: Build<27>-Footnote-133724915
Ref: Build<27>-Footnote-143724981
Ref: Build<27>-Footnote-153725047
Node: Windows<24>3725113
Ref: whatsnew/changelog id2283725218
Ref: 178a3725218
Ref: Windows<24>-Footnote-13725773
Ref: Windows<24>-Footnote-23725838
Ref: Windows<24>-Footnote-33725903
Node: macOS<19>3725968
Ref: whatsnew/changelog id2293726072
Ref: 178b3726072
Ref: macOS<19>-Footnote-13726333
Node: IDLE<16>3726398
Ref: whatsnew/changelog id2303726500
Ref: 178c3726500
Ref: IDLE<16>-Footnote-13726653
Node: C API<26>3726718
Ref: whatsnew/changelog id2313726802
Ref: 178d3726802
Ref: C API<26>-Footnote-13730528
Ref: C API<26>-Footnote-23730593
Ref: C API<26>-Footnote-33730658
Ref: C API<26>-Footnote-43730723
Ref: C API<26>-Footnote-53730788
Ref: C API<26>-Footnote-63730853
Ref: C API<26>-Footnote-73730918
Ref: C API<26>-Footnote-83730983
Ref: C API<26>-Footnote-93731048
Ref: C API<26>-Footnote-103731113
Ref: C API<26>-Footnote-113731179
Ref: C API<26>-Footnote-123731245
Ref: C API<26>-Footnote-133731311
Ref: C API<26>-Footnote-143731377
Node: Python 3 11 0 alpha 13731443
Ref: whatsnew/changelog python-3-11-0-alpha-13731587
Ref: 178e3731587
Node: Security<16>3731970
Ref: whatsnew/changelog id2323732070
Ref: 178f3732070
Ref: Security<16>-Footnote-13733425
Ref: Security<16>-Footnote-23733490
Ref: Security<16>-Footnote-33733555
Ref: Security<16>-Footnote-43733620
Ref: Security<16>-Footnote-53733685
Ref: Security<16>-Footnote-63733754
Ref: Security<16>-Footnote-73733819
Node: Core and Builtins<29>3733884
Ref: whatsnew/changelog id2333734004
Ref: 17913734004
Ref: Core and Builtins<29>-Footnote-13757701
Ref: Core and Builtins<29>-Footnote-23757766
Ref: Core and Builtins<29>-Footnote-33757831
Ref: Core and Builtins<29>-Footnote-43757896
Ref: Core and Builtins<29>-Footnote-53757961
Ref: Core and Builtins<29>-Footnote-63758026
Ref: Core and Builtins<29>-Footnote-73758091
Ref: Core and Builtins<29>-Footnote-83758156
Ref: Core and Builtins<29>-Footnote-93758221
Ref: Core and Builtins<29>-Footnote-103758286
Ref: Core and Builtins<29>-Footnote-113758352
Ref: Core and Builtins<29>-Footnote-123758418
Ref: Core and Builtins<29>-Footnote-133758484
Ref: Core and Builtins<29>-Footnote-143758552
Ref: Core and Builtins<29>-Footnote-153758618
Ref: Core and Builtins<29>-Footnote-163758684
Ref: Core and Builtins<29>-Footnote-173758750
Ref: Core and Builtins<29>-Footnote-183758816
Ref: Core and Builtins<29>-Footnote-193758882
Ref: Core and Builtins<29>-Footnote-203758948
Ref: Core and Builtins<29>-Footnote-213759014
Ref: Core and Builtins<29>-Footnote-223759080
Ref: Core and Builtins<29>-Footnote-233759146
Ref: Core and Builtins<29>-Footnote-243759212
Ref: Core and Builtins<29>-Footnote-253759278
Ref: Core and Builtins<29>-Footnote-263759344
Ref: Core and Builtins<29>-Footnote-273759410
Ref: Core and Builtins<29>-Footnote-283759476
Ref: Core and Builtins<29>-Footnote-293759542
Ref: Core and Builtins<29>-Footnote-303759608
Ref: Core and Builtins<29>-Footnote-313759674
Ref: Core and Builtins<29>-Footnote-323759740
Ref: Core and Builtins<29>-Footnote-333759806
Ref: Core and Builtins<29>-Footnote-343759872
Ref: Core and Builtins<29>-Footnote-353759938
Ref: Core and Builtins<29>-Footnote-363760004
Ref: Core and Builtins<29>-Footnote-373760070
Ref: Core and Builtins<29>-Footnote-383760136
Ref: Core and Builtins<29>-Footnote-393760202
Ref: Core and Builtins<29>-Footnote-403760268
Ref: Core and Builtins<29>-Footnote-413760334
Ref: Core and Builtins<29>-Footnote-423760400
Ref: Core and Builtins<29>-Footnote-433760466
Ref: Core and Builtins<29>-Footnote-443760532
Ref: Core and Builtins<29>-Footnote-453760598
Ref: Core and Builtins<29>-Footnote-463760664
Ref: Core and Builtins<29>-Footnote-473760730
Ref: Core and Builtins<29>-Footnote-483760796
Ref: Core and Builtins<29>-Footnote-493760862
Ref: Core and Builtins<29>-Footnote-503760928
Ref: Core and Builtins<29>-Footnote-513760994
Ref: Core and Builtins<29>-Footnote-523761060
Ref: Core and Builtins<29>-Footnote-533761126
Ref: Core and Builtins<29>-Footnote-543761192
Ref: Core and Builtins<29>-Footnote-553761258
Ref: Core and Builtins<29>-Footnote-563761324
Ref: Core and Builtins<29>-Footnote-573761390
Ref: Core and Builtins<29>-Footnote-583761456
Ref: Core and Builtins<29>-Footnote-593761522
Ref: Core and Builtins<29>-Footnote-603761588
Ref: Core and Builtins<29>-Footnote-613761654
Ref: Core and Builtins<29>-Footnote-623761720
Ref: Core and Builtins<29>-Footnote-633761786
Ref: Core and Builtins<29>-Footnote-643761852
Ref: Core and Builtins<29>-Footnote-653761918
Ref: Core and Builtins<29>-Footnote-663761984
Ref: Core and Builtins<29>-Footnote-673762050
Ref: Core and Builtins<29>-Footnote-683762116
Ref: Core and Builtins<29>-Footnote-693762182
Ref: Core and Builtins<29>-Footnote-703762248
Ref: Core and Builtins<29>-Footnote-713762314
Ref: Core and Builtins<29>-Footnote-723762380
Ref: Core and Builtins<29>-Footnote-733762446
Ref: Core and Builtins<29>-Footnote-743762512
Ref: Core and Builtins<29>-Footnote-753762578
Ref: Core and Builtins<29>-Footnote-763762621
Ref: Core and Builtins<29>-Footnote-773762687
Ref: Core and Builtins<29>-Footnote-783762753
Ref: Core and Builtins<29>-Footnote-793762819
Ref: Core and Builtins<29>-Footnote-803762862
Ref: Core and Builtins<29>-Footnote-813762928
Ref: Core and Builtins<29>-Footnote-823762994
Ref: Core and Builtins<29>-Footnote-833763060
Ref: Core and Builtins<29>-Footnote-843763126
Ref: Core and Builtins<29>-Footnote-853763192
Ref: Core and Builtins<29>-Footnote-863763258
Ref: Core and Builtins<29>-Footnote-873763324
Ref: Core and Builtins<29>-Footnote-883763390
Ref: Core and Builtins<29>-Footnote-893763456
Ref: Core and Builtins<29>-Footnote-903763522
Ref: Core and Builtins<29>-Footnote-913763588
Ref: Core and Builtins<29>-Footnote-923763654
Ref: Core and Builtins<29>-Footnote-933763720
Ref: Core and Builtins<29>-Footnote-943763786
Ref: Core and Builtins<29>-Footnote-953763852
Ref: Core and Builtins<29>-Footnote-963763918
Ref: Core and Builtins<29>-Footnote-973763984
Ref: Core and Builtins<29>-Footnote-983764050
Ref: Core and Builtins<29>-Footnote-993764116
Ref: Core and Builtins<29>-Footnote-1003764182
Ref: Core and Builtins<29>-Footnote-1013764249
Ref: Core and Builtins<29>-Footnote-1023764316
Ref: Core and Builtins<29>-Footnote-1033764383
Ref: Core and Builtins<29>-Footnote-1043764450
Ref: Core and Builtins<29>-Footnote-1053764517
Ref: Core and Builtins<29>-Footnote-1063764584
Ref: Core and Builtins<29>-Footnote-1073764651
Ref: Core and Builtins<29>-Footnote-1083764718
Ref: Core and Builtins<29>-Footnote-1093764785
Ref: Core and Builtins<29>-Footnote-1103764852
Ref: Core and Builtins<29>-Footnote-1113764919
Ref: Core and Builtins<29>-Footnote-1123764986
Ref: Core and Builtins<29>-Footnote-1133765053
Ref: Core and Builtins<29>-Footnote-1143765120
Ref: Core and Builtins<29>-Footnote-1153765187
Ref: Core and Builtins<29>-Footnote-1163765254
Ref: Core and Builtins<29>-Footnote-1173765321
Ref: Core and Builtins<29>-Footnote-1183765388
Ref: Core and Builtins<29>-Footnote-1193765455
Ref: Core and Builtins<29>-Footnote-1203765522
Ref: Core and Builtins<29>-Footnote-1213765589
Ref: Core and Builtins<29>-Footnote-1223765656
Ref: Core and Builtins<29>-Footnote-1233765723
Ref: Core and Builtins<29>-Footnote-1243765790
Ref: Core and Builtins<29>-Footnote-1253765857
Ref: Core and Builtins<29>-Footnote-1263765924
Ref: Core and Builtins<29>-Footnote-1273765991
Ref: Core and Builtins<29>-Footnote-1283766058
Ref: Core and Builtins<29>-Footnote-1293766125
Ref: Core and Builtins<29>-Footnote-1303766192
Node: Library<28>3766259
Ref: whatsnew/changelog id2343766384
Ref: 17963766384
Ref: Library<28>-Footnote-13806117
Ref: Library<28>-Footnote-23806182
Ref: Library<28>-Footnote-33806247
Ref: Library<28>-Footnote-43806312
Ref: Library<28>-Footnote-53806379
Ref: Library<28>-Footnote-63806444
Ref: Library<28>-Footnote-73806509
Ref: Library<28>-Footnote-83806574
Ref: Library<28>-Footnote-93806639
Ref: Library<28>-Footnote-103806704
Ref: Library<28>-Footnote-113806770
Ref: Library<28>-Footnote-123806836
Ref: Library<28>-Footnote-133806902
Ref: Library<28>-Footnote-143806968
Ref: Library<28>-Footnote-153807034
Ref: Library<28>-Footnote-163807100
Ref: Library<28>-Footnote-173807166
Ref: Library<28>-Footnote-183807232
Ref: Library<28>-Footnote-193807298
Ref: Library<28>-Footnote-203807364
Ref: Library<28>-Footnote-213807430
Ref: Library<28>-Footnote-223807496
Ref: Library<28>-Footnote-233807562
Ref: Library<28>-Footnote-243807628
Ref: Library<28>-Footnote-253807694
Ref: Library<28>-Footnote-263807760
Ref: Library<28>-Footnote-273807826
Ref: Library<28>-Footnote-283807892
Ref: Library<28>-Footnote-293807958
Ref: Library<28>-Footnote-303808024
Ref: Library<28>-Footnote-313808090
Ref: Library<28>-Footnote-323808156
Ref: Library<28>-Footnote-333808222
Ref: Library<28>-Footnote-343808288
Ref: Library<28>-Footnote-353808354
Ref: Library<28>-Footnote-363808397
Ref: Library<28>-Footnote-373808463
Ref: Library<28>-Footnote-383808529
Ref: Library<28>-Footnote-393808595
Ref: Library<28>-Footnote-403808661
Ref: Library<28>-Footnote-413808727
Ref: Library<28>-Footnote-423808793
Ref: Library<28>-Footnote-433808859
Ref: Library<28>-Footnote-443808925
Ref: Library<28>-Footnote-453808991
Ref: Library<28>-Footnote-463809057
Ref: Library<28>-Footnote-473809123
Ref: Library<28>-Footnote-483809189
Ref: Library<28>-Footnote-493809255
Ref: Library<28>-Footnote-503809321
Ref: Library<28>-Footnote-513809387
Ref: Library<28>-Footnote-523809453
Ref: Library<28>-Footnote-533809519
Ref: Library<28>-Footnote-543809585
Ref: Library<28>-Footnote-553809651
Ref: Library<28>-Footnote-563809717
Ref: Library<28>-Footnote-573809783
Ref: Library<28>-Footnote-583809849
Ref: Library<28>-Footnote-593809915
Ref: Library<28>-Footnote-603809981
Ref: Library<28>-Footnote-613810047
Ref: Library<28>-Footnote-623810113
Ref: Library<28>-Footnote-633810179
Ref: Library<28>-Footnote-643810245
Ref: Library<28>-Footnote-653810311
Ref: Library<28>-Footnote-663810377
Ref: Library<28>-Footnote-673810443
Ref: Library<28>-Footnote-683810509
Ref: Library<28>-Footnote-693810575
Ref: Library<28>-Footnote-703810641
Ref: Library<28>-Footnote-713810707
Ref: Library<28>-Footnote-723810773
Ref: Library<28>-Footnote-733810839
Ref: Library<28>-Footnote-743810905
Ref: Library<28>-Footnote-753810971
Ref: Library<28>-Footnote-763811037
Ref: Library<28>-Footnote-773811103
Ref: Library<28>-Footnote-783811169
Ref: Library<28>-Footnote-793811235
Ref: Library<28>-Footnote-803811301
Ref: Library<28>-Footnote-813811367
Ref: Library<28>-Footnote-823811433
Ref: Library<28>-Footnote-833811499
Ref: Library<28>-Footnote-843811565
Ref: Library<28>-Footnote-853811631
Ref: Library<28>-Footnote-863811697
Ref: Library<28>-Footnote-873811763
Ref: Library<28>-Footnote-883811829
Ref: Library<28>-Footnote-893811895
Ref: Library<28>-Footnote-903811961
Ref: Library<28>-Footnote-913812027
Ref: Library<28>-Footnote-923812093
Ref: Library<28>-Footnote-933812159
Ref: Library<28>-Footnote-943812225
Ref: Library<28>-Footnote-953812291
Ref: Library<28>-Footnote-963812357
Ref: Library<28>-Footnote-973812423
Ref: Library<28>-Footnote-983812489
Ref: Library<28>-Footnote-993812555
Ref: Library<28>-Footnote-1003812621
Ref: Library<28>-Footnote-1013812688
Ref: Library<28>-Footnote-1023812755
Ref: Library<28>-Footnote-1033812822
Ref: Library<28>-Footnote-1043812889
Ref: Library<28>-Footnote-1053812956
Ref: Library<28>-Footnote-1063813023
Ref: Library<28>-Footnote-1073813090
Ref: Library<28>-Footnote-1083813157
Ref: Library<28>-Footnote-1093813224
Ref: Library<28>-Footnote-1103813291
Ref: Library<28>-Footnote-1113813358
Ref: Library<28>-Footnote-1123813425
Ref: Library<28>-Footnote-1133813492
Ref: Library<28>-Footnote-1143813559
Ref: Library<28>-Footnote-1153813626
Ref: Library<28>-Footnote-1163813693
Ref: Library<28>-Footnote-1173813760
Ref: Library<28>-Footnote-1183813827
Ref: Library<28>-Footnote-1193813894
Ref: Library<28>-Footnote-1203813961
Ref: Library<28>-Footnote-1213814028
Ref: Library<28>-Footnote-1223814095
Ref: Library<28>-Footnote-1233814162
Ref: Library<28>-Footnote-1243814229
Ref: Library<28>-Footnote-1253814296
Ref: Library<28>-Footnote-1263814363
Ref: Library<28>-Footnote-1273814430
Ref: Library<28>-Footnote-1283814497
Ref: Library<28>-Footnote-1293814564
Ref: Library<28>-Footnote-1303814631
Ref: Library<28>-Footnote-1313814698
Ref: Library<28>-Footnote-1323814765
Ref: Library<28>-Footnote-1333814832
Ref: Library<28>-Footnote-1343814899
Ref: Library<28>-Footnote-1353814966
Ref: Library<28>-Footnote-1363815033
Ref: Library<28>-Footnote-1373815100
Ref: Library<28>-Footnote-1383815167
Ref: Library<28>-Footnote-1393815234
Ref: Library<28>-Footnote-1403815301
Ref: Library<28>-Footnote-1413815368
Ref: Library<28>-Footnote-1423815435
Ref: Library<28>-Footnote-1433815502
Ref: Library<28>-Footnote-1443815569
Ref: Library<28>-Footnote-1453815636
Ref: Library<28>-Footnote-1463815703
Ref: Library<28>-Footnote-1473815770
Ref: Library<28>-Footnote-1483815836
Ref: Library<28>-Footnote-1493815903
Ref: Library<28>-Footnote-1503815970
Ref: Library<28>-Footnote-1513816031
Ref: Library<28>-Footnote-1523816098
Ref: Library<28>-Footnote-1533816165
Ref: Library<28>-Footnote-1543816232
Ref: Library<28>-Footnote-1553816299
Ref: Library<28>-Footnote-1563816366
Ref: Library<28>-Footnote-1573816433
Ref: Library<28>-Footnote-1583816500
Ref: Library<28>-Footnote-1593816567
Ref: Library<28>-Footnote-1603816611
Ref: Library<28>-Footnote-1613816678
Ref: Library<28>-Footnote-1623816745
Ref: Library<28>-Footnote-1633816812
Ref: Library<28>-Footnote-1643816879
Ref: Library<28>-Footnote-1653816946
Ref: Library<28>-Footnote-1663817013
Ref: Library<28>-Footnote-1673817080
Ref: Library<28>-Footnote-1683817147
Ref: Library<28>-Footnote-1693817214
Ref: Library<28>-Footnote-1703817281
Ref: Library<28>-Footnote-1713817348
Ref: Library<28>-Footnote-1723817415
Ref: Library<28>-Footnote-1733817482
Ref: Library<28>-Footnote-1743817549
Ref: Library<28>-Footnote-1753817616
Ref: Library<28>-Footnote-1763817683
Ref: Library<28>-Footnote-1773817750
Ref: Library<28>-Footnote-1783817817
Ref: Library<28>-Footnote-1793817884
Ref: Library<28>-Footnote-1803817951
Ref: Library<28>-Footnote-1813818018
Ref: Library<28>-Footnote-1823818085
Ref: Library<28>-Footnote-1833818152
Ref: Library<28>-Footnote-1843818219
Ref: Library<28>-Footnote-1853818286
Ref: Library<28>-Footnote-1863818353
Ref: Library<28>-Footnote-1873818420
Ref: Library<28>-Footnote-1883818487
Ref: Library<28>-Footnote-1893818554
Ref: Library<28>-Footnote-1903818621
Ref: Library<28>-Footnote-1913818688
Ref: Library<28>-Footnote-1923818755
Ref: Library<28>-Footnote-1933818822
Ref: Library<28>-Footnote-1943818889
Ref: Library<28>-Footnote-1953818956
Ref: Library<28>-Footnote-1963819022
Ref: Library<28>-Footnote-1973819089
Ref: Library<28>-Footnote-1983819156
Ref: Library<28>-Footnote-1993819223
Ref: Library<28>-Footnote-2003819290
Ref: Library<28>-Footnote-2013819357
Ref: Library<28>-Footnote-2023819424
Ref: Library<28>-Footnote-2033819491
Ref: Library<28>-Footnote-2043819558
Ref: Library<28>-Footnote-2053819625
Ref: Library<28>-Footnote-2063819692
Ref: Library<28>-Footnote-2073819759
Ref: Library<28>-Footnote-2083819826
Ref: Library<28>-Footnote-2093819893
Node: Documentation<23>3819960
Ref: whatsnew/changelog id2353820073
Ref: 17ad3820073
Ref: Documentation<23>-Footnote-13826358
Ref: Documentation<23>-Footnote-23826423
Ref: Documentation<23>-Footnote-33826488
Ref: Documentation<23>-Footnote-43826553
Ref: Documentation<23>-Footnote-53826618
Ref: Documentation<23>-Footnote-63826683
Ref: Documentation<23>-Footnote-73826735
Ref: Documentation<23>-Footnote-83826800
Ref: Documentation<23>-Footnote-93826865
Ref: Documentation<23>-Footnote-103826924
Ref: Documentation<23>-Footnote-113826990
Ref: Documentation<23>-Footnote-123827056
Ref: Documentation<23>-Footnote-133827122
Ref: Documentation<23>-Footnote-143827188
Ref: Documentation<23>-Footnote-153827254
Ref: Documentation<23>-Footnote-163827320
Ref: Documentation<23>-Footnote-173827386
Ref: Documentation<23>-Footnote-183827452
Ref: Documentation<23>-Footnote-193827518
Ref: Documentation<23>-Footnote-203827584
Ref: Documentation<23>-Footnote-213827650
Ref: Documentation<23>-Footnote-223827716
Ref: Documentation<23>-Footnote-233827782
Ref: Documentation<23>-Footnote-243827848
Ref: Documentation<23>-Footnote-253827914
Ref: Documentation<23>-Footnote-263827980
Ref: Documentation<23>-Footnote-273828046
Ref: Documentation<23>-Footnote-283828112
Ref: Documentation<23>-Footnote-293828178
Ref: Documentation<23>-Footnote-303828244
Ref: Documentation<23>-Footnote-313828310
Ref: Documentation<23>-Footnote-323828376
Ref: Documentation<23>-Footnote-333828442
Ref: Documentation<23>-Footnote-343828508
Ref: Documentation<23>-Footnote-353828574
Ref: Documentation<23>-Footnote-363828640
Ref: Documentation<23>-Footnote-373828706
Ref: Documentation<23>-Footnote-383828772
Ref: Documentation<23>-Footnote-393828838
Ref: Documentation<23>-Footnote-403828904
Ref: Documentation<23>-Footnote-413828970
Ref: Documentation<23>-Footnote-423829036
Node: Tests<26>3829102
Ref: whatsnew/changelog id2363829213
Ref: 17af3829213
Ref: Tests<26>-Footnote-13835059
Ref: Tests<26>-Footnote-23835124
Ref: Tests<26>-Footnote-33835189
Ref: Tests<26>-Footnote-43835254
Ref: Tests<26>-Footnote-53835319
Ref: Tests<26>-Footnote-63835384
Ref: Tests<26>-Footnote-73835449
Ref: Tests<26>-Footnote-83835514
Ref: Tests<26>-Footnote-93835579
Ref: Tests<26>-Footnote-103835644
Ref: Tests<26>-Footnote-113835710
Ref: Tests<26>-Footnote-123835776
Ref: Tests<26>-Footnote-133835842
Ref: Tests<26>-Footnote-143835908
Ref: Tests<26>-Footnote-153835974
Ref: Tests<26>-Footnote-163836040
Ref: Tests<26>-Footnote-173836106
Ref: Tests<26>-Footnote-183836172
Ref: Tests<26>-Footnote-193836238
Ref: Tests<26>-Footnote-203836304
Ref: Tests<26>-Footnote-213836370
Ref: Tests<26>-Footnote-223836436
Ref: Tests<26>-Footnote-233836502
Ref: Tests<26>-Footnote-243836568
Ref: Tests<26>-Footnote-253836634
Ref: Tests<26>-Footnote-263836700
Ref: Tests<26>-Footnote-273836766
Ref: Tests<26>-Footnote-283836832
Ref: Tests<26>-Footnote-293836898
Ref: Tests<26>-Footnote-303836964
Ref: Tests<26>-Footnote-313837030
Ref: Tests<26>-Footnote-323837096
Ref: Tests<26>-Footnote-333837162
Ref: Tests<26>-Footnote-343837228
Ref: Tests<26>-Footnote-353837294
Node: Build<28>3837360
Ref: whatsnew/changelog id2373837465
Ref: 17b23837465
Ref: Build<28>-Footnote-13839536
Ref: Build<28>-Footnote-23839601
Ref: Build<28>-Footnote-33839666
Ref: Build<28>-Footnote-43839731
Ref: Build<28>-Footnote-53839796
Ref: Build<28>-Footnote-63839861
Ref: Build<28>-Footnote-73839926
Ref: Build<28>-Footnote-83839991
Ref: Build<28>-Footnote-93840056
Ref: Build<28>-Footnote-103840121
Ref: Build<28>-Footnote-113840187
Node: Windows<25>3840253
Ref: whatsnew/changelog id2383840358
Ref: 17b33840358
Ref: Windows<25>-Footnote-13841466
Ref: Windows<25>-Footnote-23841531
Ref: Windows<25>-Footnote-33841596
Ref: Windows<25>-Footnote-43841661
Ref: Windows<25>-Footnote-53841726
Ref: Windows<25>-Footnote-63841791
Ref: Windows<25>-Footnote-73841856
Ref: Windows<25>-Footnote-83841921
Ref: Windows<25>-Footnote-93841986
Node: macOS<20>3842051
Ref: whatsnew/changelog id2393842155
Ref: 17b53842155
Ref: macOS<20>-Footnote-13843300
Ref: macOS<20>-Footnote-23843365
Ref: macOS<20>-Footnote-33843430
Ref: macOS<20>-Footnote-43843495
Ref: macOS<20>-Footnote-53843560
Ref: macOS<20>-Footnote-63843625
Ref: macOS<20>-Footnote-73843690
Node: IDLE<17>3843755
Ref: whatsnew/changelog id2403843863
Ref: 17b63843863
Ref: IDLE<17>-Footnote-13845388
Ref: IDLE<17>-Footnote-23845453
Ref: IDLE<17>-Footnote-33845518
Ref: IDLE<17>-Footnote-43845583
Ref: IDLE<17>-Footnote-53845648
Ref: IDLE<17>-Footnote-63845713
Ref: IDLE<17>-Footnote-73845778
Ref: IDLE<17>-Footnote-83845843
Ref: IDLE<17>-Footnote-93845908
Node: Tools/Demos<13>3845973
Ref: whatsnew/changelog id2413846081
Ref: 17b73846081
Ref: Tools/Demos<13>-Footnote-13846877
Ref: Tools/Demos<13>-Footnote-23846942
Ref: Tools/Demos<13>-Footnote-33847007
Ref: Tools/Demos<13>-Footnote-43847072
Ref: Tools/Demos<13>-Footnote-53847137
Ref: Tools/Demos<13>-Footnote-63847202
Node: C API<27>3847267
Ref: whatsnew/changelog id2423847358
Ref: 17b83847358
Ref: C API<27>-Footnote-13853196
Ref: C API<27>-Footnote-23853261
Ref: C API<27>-Footnote-33853326
Ref: C API<27>-Footnote-43853391
Ref: C API<27>-Footnote-53853456
Ref: C API<27>-Footnote-63853521
Ref: C API<27>-Footnote-73853586
Ref: C API<27>-Footnote-83853651
Ref: C API<27>-Footnote-93853716
Ref: C API<27>-Footnote-103853781
Ref: C API<27>-Footnote-113853847
Ref: C API<27>-Footnote-123853913
Ref: C API<27>-Footnote-133853979
Ref: C API<27>-Footnote-143854045
Ref: C API<27>-Footnote-153854111
Ref: C API<27>-Footnote-163854177
Ref: C API<27>-Footnote-173854243
Ref: C API<27>-Footnote-183854309
Ref: C API<27>-Footnote-193854375
Ref: C API<27>-Footnote-203854441
Ref: C API<27>-Footnote-213854484
Ref: C API<27>-Footnote-223854550
Ref: C API<27>-Footnote-233854616
Ref: C API<27>-Footnote-243854682
Ref: C API<27>-Footnote-253854725
Ref: C API<27>-Footnote-263854768
Node: Python 3 10 0 beta 13854834
Ref: whatsnew/changelog python-3-10-0-beta-13854978
Ref: 17bb3854978
Node: Security<17>3855327
Ref: whatsnew/changelog id2433855426
Ref: 17bc3855426
Ref: Security<17>-Footnote-13858359
Ref: Security<17>-Footnote-23858424
Ref: Security<17>-Footnote-33858489
Ref: Security<17>-Footnote-43858554
Ref: Security<17>-Footnote-53858619
Ref: Security<17>-Footnote-63858684
Ref: Security<17>-Footnote-73858749
Ref: Security<17>-Footnote-83858814
Ref: Security<17>-Footnote-93858879
Ref: Security<17>-Footnote-103858944
Ref: Security<17>-Footnote-113859010
Node: Core and Builtins<30>3859076
Ref: whatsnew/changelog id2443859195
Ref: 17bf3859195
Ref: Core and Builtins<30>-Footnote-13865354
Ref: Core and Builtins<30>-Footnote-23865419
Ref: Core and Builtins<30>-Footnote-33865484
Ref: Core and Builtins<30>-Footnote-43865549
Ref: Core and Builtins<30>-Footnote-53865614
Ref: Core and Builtins<30>-Footnote-63865679
Ref: Core and Builtins<30>-Footnote-73865744
Ref: Core and Builtins<30>-Footnote-83865809
Ref: Core and Builtins<30>-Footnote-93865874
Ref: Core and Builtins<30>-Footnote-103865939
Ref: Core and Builtins<30>-Footnote-113866005
Ref: Core and Builtins<30>-Footnote-123866071
Ref: Core and Builtins<30>-Footnote-133866137
Ref: Core and Builtins<30>-Footnote-143866203
Ref: Core and Builtins<30>-Footnote-153866246
Ref: Core and Builtins<30>-Footnote-163866312
Ref: Core and Builtins<30>-Footnote-173866378
Ref: Core and Builtins<30>-Footnote-183866444
Ref: Core and Builtins<30>-Footnote-193866510
Ref: Core and Builtins<30>-Footnote-203866576
Ref: Core and Builtins<30>-Footnote-213866642
Ref: Core and Builtins<30>-Footnote-223866708
Ref: Core and Builtins<30>-Footnote-233866774
Ref: Core and Builtins<30>-Footnote-243866840
Ref: Core and Builtins<30>-Footnote-253866906
Ref: Core and Builtins<30>-Footnote-263866972
Ref: Core and Builtins<30>-Footnote-273867038
Ref: Core and Builtins<30>-Footnote-283867104
Ref: Core and Builtins<30>-Footnote-293867170
Ref: Core and Builtins<30>-Footnote-303867236
Ref: Core and Builtins<30>-Footnote-313867302
Ref: Core and Builtins<30>-Footnote-323867368
Ref: Core and Builtins<30>-Footnote-333867434
Ref: Core and Builtins<30>-Footnote-343867500
Ref: Core and Builtins<30>-Footnote-353867566
Node: Library<29>3867632
Ref: whatsnew/changelog id2453867756
Ref: 17c33867756
Ref: Library<29>-Footnote-13884514
Ref: Library<29>-Footnote-23884579
Ref: Library<29>-Footnote-33884644
Ref: Library<29>-Footnote-43884709
Ref: Library<29>-Footnote-53884774
Ref: Library<29>-Footnote-63884839
Ref: Library<29>-Footnote-73884904
Ref: Library<29>-Footnote-83884969
Ref: Library<29>-Footnote-93885034
Ref: Library<29>-Footnote-103885099
Ref: Library<29>-Footnote-113885165
Ref: Library<29>-Footnote-123885231
Ref: Library<29>-Footnote-133885297
Ref: Library<29>-Footnote-143885363
Ref: Library<29>-Footnote-153885429
Ref: Library<29>-Footnote-163885495
Ref: Library<29>-Footnote-173885561
Ref: Library<29>-Footnote-183885627
Ref: Library<29>-Footnote-193885693
Ref: Library<29>-Footnote-203885759
Ref: Library<29>-Footnote-213885825
Ref: Library<29>-Footnote-223885891
Ref: Library<29>-Footnote-233885934
Ref: Library<29>-Footnote-243886000
Ref: Library<29>-Footnote-253886066
Ref: Library<29>-Footnote-263886132
Ref: Library<29>-Footnote-273886198
Ref: Library<29>-Footnote-283886264
Ref: Library<29>-Footnote-293886330
Ref: Library<29>-Footnote-303886396
Ref: Library<29>-Footnote-313886462
Ref: Library<29>-Footnote-323886528
Ref: Library<29>-Footnote-333886594
Ref: Library<29>-Footnote-343886660
Ref: Library<29>-Footnote-353886726
Ref: Library<29>-Footnote-363886792
Ref: Library<29>-Footnote-373886858
Ref: Library<29>-Footnote-383886924
Ref: Library<29>-Footnote-393886990
Ref: Library<29>-Footnote-403887056
Ref: Library<29>-Footnote-413887122
Ref: Library<29>-Footnote-423887188
Ref: Library<29>-Footnote-433887231
Ref: Library<29>-Footnote-443887297
Ref: Library<29>-Footnote-453887363
Ref: Library<29>-Footnote-463887429
Ref: Library<29>-Footnote-473887495
Ref: Library<29>-Footnote-483887561
Ref: Library<29>-Footnote-493887627
Ref: Library<29>-Footnote-503887693
Ref: Library<29>-Footnote-513887759
Ref: Library<29>-Footnote-523887825
Ref: Library<29>-Footnote-533887890
Ref: Library<29>-Footnote-543887956
Ref: Library<29>-Footnote-553888022
Ref: Library<29>-Footnote-563888088
Ref: Library<29>-Footnote-573888153
Ref: Library<29>-Footnote-583888219
Ref: Library<29>-Footnote-593888285
Ref: Library<29>-Footnote-603888351
Ref: Library<29>-Footnote-613888417
Ref: Library<29>-Footnote-623888483
Ref: Library<29>-Footnote-633888549
Ref: Library<29>-Footnote-643888615
Ref: Library<29>-Footnote-653888681
Ref: Library<29>-Footnote-663888747
Ref: Library<29>-Footnote-673888813
Ref: Library<29>-Footnote-683888856
Ref: Library<29>-Footnote-693888922
Ref: Library<29>-Footnote-703888988
Ref: Library<29>-Footnote-713889054
Ref: Library<29>-Footnote-723889120
Ref: Library<29>-Footnote-733889186
Ref: Library<29>-Footnote-743889252
Ref: Library<29>-Footnote-753889318
Ref: Library<29>-Footnote-763889384
Ref: Library<29>-Footnote-773889450
Ref: Library<29>-Footnote-783889516
Ref: Library<29>-Footnote-793889582
Ref: Library<29>-Footnote-803889648
Ref: Library<29>-Footnote-813889714
Ref: Library<29>-Footnote-823889780
Node: Documentation<24>3889846
Ref: whatsnew/changelog id2463889958
Ref: 17ca3889958
Ref: Documentation<24>-Footnote-13890966
Ref: Documentation<24>-Footnote-23891031
Ref: Documentation<24>-Footnote-33891096
Ref: Documentation<24>-Footnote-43891161
Ref: Documentation<24>-Footnote-53891226
Ref: Documentation<24>-Footnote-63891291
Ref: Documentation<24>-Footnote-73891356
Node: Tests<27>3891421
Ref: whatsnew/changelog id2473891531
Ref: 17cb3891531
Ref: Tests<27>-Footnote-13892608
Ref: Tests<27>-Footnote-23892673
Ref: Tests<27>-Footnote-33892738
Ref: Tests<27>-Footnote-43892803
Ref: Tests<27>-Footnote-53892868
Node: Build<29>3892933
Ref: whatsnew/changelog id2483893037
Ref: 17cc3893037
Ref: Build<29>-Footnote-13893297
Ref: Build<29>-Footnote-23893362
Ref: Build<29>-Footnote-33893427
Node: Windows<26>3893469
Ref: whatsnew/changelog id2493893573
Ref: 17cd3893573
Ref: Windows<26>-Footnote-13894914
Ref: Windows<26>-Footnote-23894979
Ref: Windows<26>-Footnote-33895044
Ref: Windows<26>-Footnote-43895109
Ref: Windows<26>-Footnote-53895174
Ref: Windows<26>-Footnote-63895239
Ref: Windows<26>-Footnote-73895304
Ref: Windows<26>-Footnote-83895369
Ref: Windows<26>-Footnote-93895434
Node: macOS<21>3895499
Ref: whatsnew/changelog id2503895602
Ref: 17d13895602
Ref: macOS<21>-Footnote-13896900
Ref: macOS<21>-Footnote-23896965
Ref: macOS<21>-Footnote-33897030
Ref: macOS<21>-Footnote-43897095
Ref: macOS<21>-Footnote-53897160
Ref: macOS<21>-Footnote-63897225
Node: IDLE<18>3897290
Ref: whatsnew/changelog id2513897391
Ref: 17d23897391
Ref: IDLE<18>-Footnote-13898185
Ref: IDLE<18>-Footnote-23898250
Ref: IDLE<18>-Footnote-33898315
Ref: IDLE<18>-Footnote-43898380
Ref: IDLE<18>-Footnote-53898445
Node: C API<28>3898510
Ref: whatsnew/changelog id2523898593
Ref: 17d33898593
Ref: C API<28>-Footnote-13900841
Ref: C API<28>-Footnote-23900906
Ref: C API<28>-Footnote-33900971
Ref: C API<28>-Footnote-43901036
Ref: C API<28>-Footnote-53901101
Ref: C API<28>-Footnote-63901166
Ref: C API<28>-Footnote-73901231
Ref: C API<28>-Footnote-83901296
Ref: C API<28>-Footnote-93901361
Ref: C API<28>-Footnote-103901403
Node: Python 3 10 0 alpha 73901469
Ref: whatsnew/changelog python-3-10-0-alpha-73901613
Ref: 17d43901613
Node: Security<18>3901944
Ref: whatsnew/changelog id2533902044
Ref: 17d53902044
Ref: Security<18>-Footnote-13903128
Ref: Security<18>-Footnote-23903193
Ref: Security<18>-Footnote-33903262
Ref: Security<18>-Footnote-43903327
Node: Core and Builtins<31>3903392
Ref: whatsnew/changelog id2543903512
Ref: 17d63903512
Ref: Core and Builtins<31>-Footnote-13908028
Ref: Core and Builtins<31>-Footnote-23908093
Ref: Core and Builtins<31>-Footnote-33908158
Ref: Core and Builtins<31>-Footnote-43908223
Ref: Core and Builtins<31>-Footnote-53908288
Ref: Core and Builtins<31>-Footnote-63908353
Ref: Core and Builtins<31>-Footnote-73908418
Ref: Core and Builtins<31>-Footnote-83908483
Ref: Core and Builtins<31>-Footnote-93908548
Ref: Core and Builtins<31>-Footnote-103908590
Ref: Core and Builtins<31>-Footnote-113908656
Ref: Core and Builtins<31>-Footnote-123908722
Ref: Core and Builtins<31>-Footnote-133908788
Ref: Core and Builtins<31>-Footnote-143908854
Ref: Core and Builtins<31>-Footnote-153908920
Ref: Core and Builtins<31>-Footnote-163908986
Ref: Core and Builtins<31>-Footnote-173909052
Ref: Core and Builtins<31>-Footnote-183909118
Ref: Core and Builtins<31>-Footnote-193909184
Ref: Core and Builtins<31>-Footnote-203909250
Ref: Core and Builtins<31>-Footnote-213909316
Ref: Core and Builtins<31>-Footnote-223909382
Ref: Core and Builtins<31>-Footnote-233909425
Ref: Core and Builtins<31>-Footnote-243909491
Node: Library<30>3909557
Ref: whatsnew/changelog id2553909682
Ref: 17d73909682
Ref: Library<30>-Footnote-13917362
Ref: Library<30>-Footnote-23917427
Ref: Library<30>-Footnote-33917492
Ref: Library<30>-Footnote-43917557
Ref: Library<30>-Footnote-53917622
Ref: Library<30>-Footnote-63917687
Ref: Library<30>-Footnote-73917752
Ref: Library<30>-Footnote-83917817
Ref: Library<30>-Footnote-93917882
Ref: Library<30>-Footnote-103917947
Ref: Library<30>-Footnote-113918013
Ref: Library<30>-Footnote-123918079
Ref: Library<30>-Footnote-133918145
Ref: Library<30>-Footnote-143918211
Ref: Library<30>-Footnote-153918277
Ref: Library<30>-Footnote-163918320
Ref: Library<30>-Footnote-173918386
Ref: Library<30>-Footnote-183918452
Ref: Library<30>-Footnote-193918518
Ref: Library<30>-Footnote-203918584
Ref: Library<30>-Footnote-213918650
Ref: Library<30>-Footnote-223918716
Ref: Library<30>-Footnote-233918782
Ref: Library<30>-Footnote-243918848
Ref: Library<30>-Footnote-253918914
Ref: Library<30>-Footnote-263918996
Ref: Library<30>-Footnote-273919062
Ref: Library<30>-Footnote-283919128
Ref: Library<30>-Footnote-293919194
Ref: Library<30>-Footnote-303919260
Ref: Library<30>-Footnote-313919326
Ref: Library<30>-Footnote-323919392
Ref: Library<30>-Footnote-333919458
Ref: Library<30>-Footnote-343919524
Ref: Library<30>-Footnote-353919590
Ref: Library<30>-Footnote-363919656
Ref: Library<30>-Footnote-373919722
Ref: Library<30>-Footnote-383919788
Ref: Library<30>-Footnote-393919854
Ref: Library<30>-Footnote-403919920
Ref: Library<30>-Footnote-413919986
Ref: Library<30>-Footnote-423920052
Ref: Library<30>-Footnote-433920118
Ref: Library<30>-Footnote-443920184
Ref: Library<30>-Footnote-453920250
Node: Documentation<25>3920316
Ref: whatsnew/changelog id2563920429
Ref: 17df3920429
Ref: Documentation<25>-Footnote-13921123
Ref: Documentation<25>-Footnote-23921188
Ref: Documentation<25>-Footnote-33921253
Ref: Documentation<25>-Footnote-43921318
Node: Tests<28>3921383
Ref: whatsnew/changelog id2573921494
Ref: 17e03921494
Ref: Tests<28>-Footnote-13921797
Ref: Tests<28>-Footnote-23921862
Node: Build<30>3921927
Ref: whatsnew/changelog id2583922032
Ref: 17e13922032
Ref: Build<30>-Footnote-13923003
Ref: Build<30>-Footnote-23923068
Ref: Build<30>-Footnote-33923133
Ref: Build<30>-Footnote-43923198
Ref: Build<30>-Footnote-53923263
Ref: Build<30>-Footnote-63923328
Node: Windows<27>3923393
Ref: whatsnew/changelog id2593923497
Ref: 17e23923497
Ref: Windows<27>-Footnote-13923687
Node: IDLE<19>3923752
Ref: whatsnew/changelog id2603923856
Ref: 17e33923856
Ref: IDLE<19>-Footnote-13924097
Node: C API<29>3924162
Ref: whatsnew/changelog id2613924246
Ref: 17e43924246
Ref: C API<29>-Footnote-13927710
Ref: C API<29>-Footnote-23927775
Ref: C API<29>-Footnote-33927840
Ref: C API<29>-Footnote-43927905
Ref: C API<29>-Footnote-53927970
Ref: C API<29>-Footnote-63928035
Ref: C API<29>-Footnote-73928100
Ref: C API<29>-Footnote-83928165
Ref: C API<29>-Footnote-93928230
Node: Python 3 10 0 alpha 63928272
Ref: whatsnew/changelog python-3-10-0-alpha-63928417
Ref: 17e53928417
Node: Security<19>3928768
Ref: whatsnew/changelog id2623928868
Ref: 17e63928868
Ref: Security<19>-Footnote-13929114
Node: Core and Builtins<32>3929179
Ref: whatsnew/changelog id2633929299
Ref: 17e73929299
Ref: Core and Builtins<32>-Footnote-13932728
Ref: Core and Builtins<32>-Footnote-23932793
Ref: Core and Builtins<32>-Footnote-33932858
Ref: Core and Builtins<32>-Footnote-43932900
Ref: Core and Builtins<32>-Footnote-53932965
Ref: Core and Builtins<32>-Footnote-63933030
Ref: Core and Builtins<32>-Footnote-73933095
Ref: Core and Builtins<32>-Footnote-83933160
Ref: Core and Builtins<32>-Footnote-93933225
Ref: Core and Builtins<32>-Footnote-103933290
Ref: Core and Builtins<32>-Footnote-113933356
Ref: Core and Builtins<32>-Footnote-123933422
Ref: Core and Builtins<32>-Footnote-133933488
Ref: Core and Builtins<32>-Footnote-143933554
Ref: Core and Builtins<32>-Footnote-153933597
Ref: Core and Builtins<32>-Footnote-163933663
Node: Library<31>3933729
Ref: whatsnew/changelog id2643933854
Ref: 17e83933854
Ref: Library<31>-Footnote-13936689
Ref: Library<31>-Footnote-23936754
Ref: Library<31>-Footnote-33936819
Ref: Library<31>-Footnote-43936884
Ref: Library<31>-Footnote-53936949
Ref: Library<31>-Footnote-63937014
Ref: Library<31>-Footnote-73937079
Ref: Library<31>-Footnote-83937144
Ref: Library<31>-Footnote-93937209
Ref: Library<31>-Footnote-103937274
Ref: Library<31>-Footnote-113937340
Ref: Library<31>-Footnote-123937406
Ref: Library<31>-Footnote-133937472
Ref: Library<31>-Footnote-143937538
Ref: Library<31>-Footnote-153937604
Ref: Library<31>-Footnote-163937670
Node: Documentation<26>3937736
Ref: whatsnew/changelog id2653937849
Ref: 17ec3937849
Ref: Documentation<26>-Footnote-13938191
Ref: Documentation<26>-Footnote-23938256
Ref: Documentation<26>-Footnote-33938321
Node: Tests<29>3938363
Ref: whatsnew/changelog id2663938474
Ref: 17ed3938474
Ref: Tests<29>-Footnote-13938665
Node: Build<31>3938730
Ref: whatsnew/changelog id2673938835
Ref: 17ee3938835
Ref: Build<31>-Footnote-13939900
Ref: Build<31>-Footnote-23939965
Ref: Build<31>-Footnote-33940030
Ref: Build<31>-Footnote-43940095
Ref: Build<31>-Footnote-53940160
Node: Windows<28>3940225
Ref: whatsnew/changelog id2683940330
Ref: 17ef3940330
Ref: Windows<28>-Footnote-13940494
Node: macOS<22>3940559
Ref: whatsnew/changelog id2693940663
Ref: 17f13940663
Ref: macOS<22>-Footnote-13940804
Node: IDLE<20>3940869
Ref: whatsnew/changelog id2703940971
Ref: 17f23940971
Ref: IDLE<20>-Footnote-13941239
Node: C API<30>3941304
Ref: whatsnew/changelog id2713941388
Ref: 17f33941388
Ref: C API<30>-Footnote-13943138
Ref: C API<30>-Footnote-23943203
Ref: C API<30>-Footnote-33943268
Ref: C API<30>-Footnote-43943333
Ref: C API<30>-Footnote-53943398
Ref: C API<30>-Footnote-63943463
Ref: C API<30>-Footnote-73943528
Ref: C API<30>-Footnote-83943593
Ref: C API<30>-Footnote-93943658
Node: Python 3 10 0 alpha 53943723
Ref: whatsnew/changelog python-3-10-0-alpha-53943868
Ref: 17fb3943868
Node: Security<20>3944219
Ref: whatsnew/changelog id2723944319
Ref: 17fc3944319
Ref: Security<20>-Footnote-13944541
Node: Core and Builtins<33>3944606
Ref: whatsnew/changelog id2733944726
Ref: 17ff3944726
Ref: Core and Builtins<33>-Footnote-13947242
Ref: Core and Builtins<33>-Footnote-23947307
Ref: Core and Builtins<33>-Footnote-33947372
Ref: Core and Builtins<33>-Footnote-43947437
Ref: Core and Builtins<33>-Footnote-53947502
Ref: Core and Builtins<33>-Footnote-63947567
Ref: Core and Builtins<33>-Footnote-73947632
Ref: Core and Builtins<33>-Footnote-83947697
Ref: Core and Builtins<33>-Footnote-93947762
Ref: Core and Builtins<33>-Footnote-103947827
Ref: Core and Builtins<33>-Footnote-113947893
Ref: Core and Builtins<33>-Footnote-123947959
Ref: Core and Builtins<33>-Footnote-133948025
Ref: Core and Builtins<33>-Footnote-143948091
Ref: Core and Builtins<33>-Footnote-153948157
Node: Library<32>3948223
Ref: whatsnew/changelog id2743948348
Ref: 18003948348
Ref: Library<32>-Footnote-13953279
Ref: Library<32>-Footnote-23953344
Ref: Library<32>-Footnote-33953409
Ref: Library<32>-Footnote-43953474
Ref: Library<32>-Footnote-53953539
Ref: Library<32>-Footnote-63953604
Ref: Library<32>-Footnote-73953669
Ref: Library<32>-Footnote-83953734
Ref: Library<32>-Footnote-93953799
Ref: Library<32>-Footnote-103953864
Ref: Library<32>-Footnote-113953930
Ref: Library<32>-Footnote-123953996
Ref: Library<32>-Footnote-133954062
Ref: Library<32>-Footnote-143954128
Ref: Library<32>-Footnote-153954194
Ref: Library<32>-Footnote-163954260
Ref: Library<32>-Footnote-173954326
Ref: Library<32>-Footnote-183954392
Ref: Library<32>-Footnote-193954435
Ref: Library<32>-Footnote-203954501
Ref: Library<32>-Footnote-213954567
Ref: Library<32>-Footnote-223954633
Ref: Library<32>-Footnote-233954699
Ref: Library<32>-Footnote-243954767
Ref: Library<32>-Footnote-253954810
Ref: Library<32>-Footnote-263954876
Ref: Library<32>-Footnote-273954942
Ref: Library<32>-Footnote-283955008
Ref: Library<32>-Footnote-293955074
Ref: Library<32>-Footnote-303955140
Ref: Library<32>-Footnote-313955206
Ref: Library<32>-Footnote-323955272
Ref: Library<32>-Footnote-333955338
Ref: Library<32>-Footnote-343955404
Node: Documentation<27>3955470
Ref: whatsnew/changelog id2753955583
Ref: 18013955583
Ref: Documentation<27>-Footnote-13955911
Ref: Documentation<27>-Footnote-23955976
Node: Tests<30>3956041
Ref: whatsnew/changelog id2763956152
Ref: 18023956152
Ref: Tests<30>-Footnote-13956508
Ref: Tests<30>-Footnote-23956573
Node: Build<32>3956638
Ref: whatsnew/changelog id2773956743
Ref: 18033956743
Ref: Build<32>-Footnote-13957936
Ref: Build<32>-Footnote-23958001
Ref: Build<32>-Footnote-33958066
Ref: Build<32>-Footnote-43958131
Ref: Build<32>-Footnote-53958196
Node: Windows<29>3958261
Ref: whatsnew/changelog id2783958366
Ref: 18043958366
Ref: Windows<29>-Footnote-13958579
Ref: Windows<29>-Footnote-23958644
Node: macOS<23>3958709
Ref: whatsnew/changelog id2793958813
Ref: 18053958813
Ref: macOS<23>-Footnote-13959060
Node: IDLE<21>3959125
Ref: whatsnew/changelog id2803959227
Ref: 18063959227
Ref: IDLE<21>-Footnote-13959789
Ref: IDLE<21>-Footnote-23959854
Ref: IDLE<21>-Footnote-33959919
Ref: IDLE<21>-Footnote-43959984
Node: C API<31>3960049
Ref: whatsnew/changelog id2813960133
Ref: 18073960133
Ref: C API<31>-Footnote-13960739
Ref: C API<31>-Footnote-23960804
Node: Python 3 10 0 alpha 43960869
Ref: whatsnew/changelog python-3-10-0-alpha-43961014
Ref: 18093961014
Node: Core and Builtins<34>3961329
Ref: whatsnew/changelog id2823961428
Ref: 180a3961428
Ref: Core and Builtins<34>-Footnote-13964842
Ref: Core and Builtins<34>-Footnote-23964907
Ref: Core and Builtins<34>-Footnote-33964972
Ref: Core and Builtins<34>-Footnote-43965037
Ref: Core and Builtins<34>-Footnote-53965102
Ref: Core and Builtins<34>-Footnote-63965167
Ref: Core and Builtins<34>-Footnote-73965232
Ref: Core and Builtins<34>-Footnote-83965297
Ref: Core and Builtins<34>-Footnote-93965362
Ref: Core and Builtins<34>-Footnote-103965427
Ref: Core and Builtins<34>-Footnote-113965493
Ref: Core and Builtins<34>-Footnote-123965559
Ref: Core and Builtins<34>-Footnote-133965625
Ref: Core and Builtins<34>-Footnote-143965691
Ref: Core and Builtins<34>-Footnote-153965734
Ref: Core and Builtins<34>-Footnote-163965800
Ref: Core and Builtins<34>-Footnote-173965866
Ref: Core and Builtins<34>-Footnote-183965932
Ref: Core and Builtins<34>-Footnote-193966000
Ref: Core and Builtins<34>-Footnote-203966043
Ref: Core and Builtins<34>-Footnote-213966109
Node: Library<33>3966175
Ref: whatsnew/changelog id2833966300
Ref: 180c3966300
Ref: Library<33>-Footnote-13975115
Ref: Library<33>-Footnote-23975180
Ref: Library<33>-Footnote-33975245
Ref: Library<33>-Footnote-43975310
Ref: Library<33>-Footnote-53975375
Ref: Library<33>-Footnote-63975440
Ref: Library<33>-Footnote-73975505
Ref: Library<33>-Footnote-83975547
Ref: Library<33>-Footnote-93975589
Ref: Library<33>-Footnote-103975654
Ref: Library<33>-Footnote-113975720
Ref: Library<33>-Footnote-123975786
Ref: Library<33>-Footnote-133975852
Ref: Library<33>-Footnote-143975918
Ref: Library<33>-Footnote-153975984
Ref: Library<33>-Footnote-163976050
Ref: Library<33>-Footnote-173976116
Ref: Library<33>-Footnote-183976182
Ref: Library<33>-Footnote-193976247
Ref: Library<33>-Footnote-203976315
Ref: Library<33>-Footnote-213976358
Ref: Library<33>-Footnote-223976424
Ref: Library<33>-Footnote-233976490
Ref: Library<33>-Footnote-243976556
Ref: Library<33>-Footnote-253976622
Ref: Library<33>-Footnote-263976688
Ref: Library<33>-Footnote-273976754
Ref: Library<33>-Footnote-283976820
Ref: Library<33>-Footnote-293976886
Ref: Library<33>-Footnote-303976952
Ref: Library<33>-Footnote-313977018
Ref: Library<33>-Footnote-323977084
Ref: Library<33>-Footnote-333977127
Ref: Library<33>-Footnote-343977193
Ref: Library<33>-Footnote-353977259
Ref: Library<33>-Footnote-363977325
Ref: Library<33>-Footnote-373977391
Ref: Library<33>-Footnote-383977457
Ref: Library<33>-Footnote-393977523
Ref: Library<33>-Footnote-403977589
Ref: Library<33>-Footnote-413977655
Ref: Library<33>-Footnote-423977721
Ref: Library<33>-Footnote-433977787
Ref: Library<33>-Footnote-443977853
Ref: Library<33>-Footnote-453977919
Ref: Library<33>-Footnote-463977985
Ref: Library<33>-Footnote-473978051
Ref: Library<33>-Footnote-483978119
Ref: Library<33>-Footnote-493978162
Ref: Library<33>-Footnote-503978228
Ref: Library<33>-Footnote-513978294
Ref: Library<33>-Footnote-523978360
Ref: Library<33>-Footnote-533978426
Ref: Library<33>-Footnote-543978492
Ref: Library<33>-Footnote-553978558
Ref: Library<33>-Footnote-563978624
Ref: Library<33>-Footnote-573978690
Ref: Library<33>-Footnote-583978756
Node: Documentation<28>3978822
Ref: whatsnew/changelog id2843978935
Ref: 18123978935
Ref: Documentation<28>-Footnote-13979251
Ref: Documentation<28>-Footnote-23979316
Node: Tests<31>3979381
Ref: whatsnew/changelog id2853979492
Ref: 18143979492
Ref: Tests<31>-Footnote-13980269
Ref: Tests<31>-Footnote-23980334
Ref: Tests<31>-Footnote-33980399
Ref: Tests<31>-Footnote-43980464
Ref: Tests<31>-Footnote-53980529
Ref: Tests<31>-Footnote-63980594
Ref: Tests<31>-Footnote-73980659
Ref: Tests<31>-Footnote-83980724
Node: Build<33>3980789
Ref: whatsnew/changelog id2863980892
Ref: 18153980892
Ref: Build<33>-Footnote-13981857
Ref: Build<33>-Footnote-23981922
Ref: Build<33>-Footnote-33981987
Ref: Build<33>-Footnote-43982052
Ref: Build<33>-Footnote-53982117
Ref: Build<33>-Footnote-63982182
Node: macOS<24>3982247
Ref: whatsnew/changelog id2873982356
Ref: 18163982356
Ref: macOS<24>-Footnote-13982674
Ref: macOS<24>-Footnote-23982739
Ref: macOS<24>-Footnote-33982804
Node: Tools/Demos<14>3982869
Ref: whatsnew/changelog id2883982978
Ref: 18173982978
Ref: Tools/Demos<14>-Footnote-13983302
Ref: Tools/Demos<14>-Footnote-23983367
Node: C API<32>3983432
Ref: whatsnew/changelog id2893983523
Ref: 18183983523
Ref: C API<32>-Footnote-13984364
Ref: C API<32>-Footnote-23984429
Ref: C API<32>-Footnote-33984494
Ref: C API<32>-Footnote-43984561
Ref: C API<32>-Footnote-53984626
Node: Python 3 10 0 alpha 33984691
Ref: whatsnew/changelog python-3-10-0-alpha-33984836
Ref: 18193984836
Node: Security<21>3985219
Ref: whatsnew/changelog id2903985319
Ref: 181a3985319
Ref: Security<21>-Footnote-13985559
Node: Core and Builtins<35>3985624
Ref: whatsnew/changelog id2913985744
Ref: 181b3985744
Ref: Core and Builtins<35>-Footnote-13990041
Ref: Core and Builtins<35>-Footnote-23990106
Ref: Core and Builtins<35>-Footnote-33990171
Ref: Core and Builtins<35>-Footnote-43990236
Ref: Core and Builtins<35>-Footnote-53990301
Ref: Core and Builtins<35>-Footnote-63990366
Ref: Core and Builtins<35>-Footnote-73990433
Ref: Core and Builtins<35>-Footnote-83990475
Ref: Core and Builtins<35>-Footnote-93990540
Ref: Core and Builtins<35>-Footnote-103990605
Ref: Core and Builtins<35>-Footnote-113990671
Ref: Core and Builtins<35>-Footnote-123990737
Ref: Core and Builtins<35>-Footnote-133990803
Ref: Core and Builtins<35>-Footnote-143990869
Ref: Core and Builtins<35>-Footnote-153990935
Ref: Core and Builtins<35>-Footnote-163991001
Ref: Core and Builtins<35>-Footnote-173991067
Ref: Core and Builtins<35>-Footnote-183991133
Ref: Core and Builtins<35>-Footnote-193991199
Ref: Core and Builtins<35>-Footnote-203991265
Ref: Core and Builtins<35>-Footnote-213991331
Ref: Core and Builtins<35>-Footnote-223991397
Ref: Core and Builtins<35>-Footnote-233991463
Node: Library<34>3991529
Ref: whatsnew/changelog id2923991654
Ref: 181e3991654
Ref: Library<34>-Footnote-14002713
Ref: Library<34>-Footnote-24002777
Ref: Library<34>-Footnote-34002842
Ref: Library<34>-Footnote-44002907
Ref: Library<34>-Footnote-54002972
Ref: Library<34>-Footnote-64003037
Ref: Library<34>-Footnote-74003102
Ref: Library<34>-Footnote-84003167
Ref: Library<34>-Footnote-94003232
Ref: Library<34>-Footnote-104003297
Ref: Library<34>-Footnote-114003363
Ref: Library<34>-Footnote-124003429
Ref: Library<34>-Footnote-134003495
Ref: Library<34>-Footnote-144003561
Ref: Library<34>-Footnote-154003627
Ref: Library<34>-Footnote-164003693
Ref: Library<34>-Footnote-174003759
Ref: Library<34>-Footnote-184003825
Ref: Library<34>-Footnote-194003891
Ref: Library<34>-Footnote-204003957
Ref: Library<34>-Footnote-214004023
Ref: Library<34>-Footnote-224004089
Ref: Library<34>-Footnote-234004155
Ref: Library<34>-Footnote-244004223
Ref: Library<34>-Footnote-254004289
Ref: Library<34>-Footnote-264004355
Ref: Library<34>-Footnote-274004398
Ref: Library<34>-Footnote-284004464
Ref: Library<34>-Footnote-294004530
Ref: Library<34>-Footnote-304004596
Ref: Library<34>-Footnote-314004662
Ref: Library<34>-Footnote-324004728
Ref: Library<34>-Footnote-334004794
Ref: Library<34>-Footnote-344004860
Ref: Library<34>-Footnote-354004926
Ref: Library<34>-Footnote-364004992
Ref: Library<34>-Footnote-374005058
Ref: Library<34>-Footnote-384005124
Ref: Library<34>-Footnote-394005190
Ref: Library<34>-Footnote-404005256
Ref: Library<34>-Footnote-414005322
Ref: Library<34>-Footnote-424005388
Ref: Library<34>-Footnote-434005454
Ref: Library<34>-Footnote-444005520
Ref: Library<34>-Footnote-454005586
Ref: Library<34>-Footnote-464005652
Ref: Library<34>-Footnote-474005718
Ref: Library<34>-Footnote-484005784
Ref: Library<34>-Footnote-494005850
Ref: Library<34>-Footnote-504005916
Ref: Library<34>-Footnote-514005982
Ref: Library<34>-Footnote-524006048
Ref: Library<34>-Footnote-534006114
Ref: Library<34>-Footnote-544006180
Ref: Library<34>-Footnote-554006246
Ref: Library<34>-Footnote-564006312
Ref: Library<34>-Footnote-574006378
Ref: Library<34>-Footnote-584006444
Ref: Library<34>-Footnote-594006510
Ref: Library<34>-Footnote-604006576
Ref: Library<34>-Footnote-614006642
Ref: Library<34>-Footnote-624006708
Ref: Library<34>-Footnote-634006774
Ref: Library<34>-Footnote-644006840
Ref: Library<34>-Footnote-654006906
Node: Documentation<29>4006972
Ref: whatsnew/changelog id2934007085
Ref: 18234007085
Ref: Documentation<29>-Footnote-14007551
Ref: Documentation<29>-Footnote-24007616
Ref: Documentation<29>-Footnote-34007681
Node: Tests<32>4007746
Ref: whatsnew/changelog id2944007857
Ref: 18244007857
Ref: Tests<32>-Footnote-14009063
Ref: Tests<32>-Footnote-24009128
Ref: Tests<32>-Footnote-34009193
Ref: Tests<32>-Footnote-44009258
Ref: Tests<32>-Footnote-54009323
Ref: Tests<32>-Footnote-64009388
Ref: Tests<32>-Footnote-74009453
Ref: Tests<32>-Footnote-84009518
Ref: Tests<32>-Footnote-94009583
Ref: Tests<32>-Footnote-104009648
Ref: Tests<32>-Footnote-114009714
Ref: Tests<32>-Footnote-124009780
Node: Build<34>4009846
Ref: whatsnew/changelog id2954009951
Ref: 18254009951
Ref: Build<34>-Footnote-14011088
Ref: Build<34>-Footnote-24011153
Ref: Build<34>-Footnote-34011218
Ref: Build<34>-Footnote-44011283
Ref: Build<34>-Footnote-54011348
Ref: Build<34>-Footnote-64011413
Ref: Build<34>-Footnote-74011478
Node: Windows<30>4011543
Ref: whatsnew/changelog id2964011648
Ref: 18264011648
Ref: Windows<30>-Footnote-14011940
Ref: Windows<30>-Footnote-24012005
Node: macOS<25>4012070
Ref: whatsnew/changelog id2974012174
Ref: 18274012174
Ref: macOS<25>-Footnote-14013110
Ref: macOS<25>-Footnote-24013175
Ref: macOS<25>-Footnote-34013240
Ref: macOS<25>-Footnote-44013305
Ref: macOS<25>-Footnote-54013370
Node: IDLE<22>4013435
Ref: whatsnew/changelog id2984013543
Ref: 18284013543
Ref: IDLE<22>-Footnote-14013963
Ref: IDLE<22>-Footnote-24014028
Ref: IDLE<22>-Footnote-34014093
Node: Tools/Demos<15>4014158
Ref: whatsnew/changelog id2994014266
Ref: 18294014266
Ref: Tools/Demos<15>-Footnote-14014668
Ref: Tools/Demos<15>-Footnote-24014733
Node: C API<33>4014798
Ref: whatsnew/changelog id3004014889
Ref: 182a4014889
Ref: C API<33>-Footnote-14019659
Ref: C API<33>-Footnote-24019724
Ref: C API<33>-Footnote-34019791
Ref: C API<33>-Footnote-44019833
Ref: C API<33>-Footnote-54019900
Ref: C API<33>-Footnote-64019942
Ref: C API<33>-Footnote-74020009
Ref: C API<33>-Footnote-84020051
Ref: C API<33>-Footnote-94020118
Ref: C API<33>-Footnote-104020160
Ref: C API<33>-Footnote-114020228
Ref: C API<33>-Footnote-124020271
Ref: C API<33>-Footnote-134020339
Ref: C API<33>-Footnote-144020382
Ref: C API<33>-Footnote-154020450
Ref: C API<33>-Footnote-164020493
Ref: C API<33>-Footnote-174020559
Ref: C API<33>-Footnote-184020627
Ref: C API<33>-Footnote-194020670
Ref: C API<33>-Footnote-204020738
Ref: C API<33>-Footnote-214020781
Ref: C API<33>-Footnote-224020849
Ref: C API<33>-Footnote-234020892
Ref: C API<33>-Footnote-244020960
Ref: C API<33>-Footnote-254021003
Ref: C API<33>-Footnote-264021069
Ref: C API<33>-Footnote-274021135
Ref: C API<33>-Footnote-284021201
Ref: C API<33>-Footnote-294021267
Ref: C API<33>-Footnote-304021333
Ref: C API<33>-Footnote-314021399
Ref: C API<33>-Footnote-324021465
Ref: C API<33>-Footnote-334021533
Ref: C API<33>-Footnote-344021599
Ref: C API<33>-Footnote-354021665
Ref: C API<33>-Footnote-364021731
Node: Python 3 10 0 alpha 24021797
Ref: whatsnew/changelog python-3-10-0-alpha-24021942
Ref: 182c4021942
Node: Security<22>4022293
Ref: whatsnew/changelog id3014022393
Ref: 182d4022393
Ref: Security<22>-Footnote-14022869
Ref: Security<22>-Footnote-24022934
Node: Core and Builtins<36>4022999
Ref: whatsnew/changelog id3024023119
Ref: 182e4023119
Ref: Core and Builtins<36>-Footnote-14026916
Ref: Core and Builtins<36>-Footnote-24026981
Ref: Core and Builtins<36>-Footnote-34027046
Ref: Core and Builtins<36>-Footnote-44027111
Ref: Core and Builtins<36>-Footnote-54027176
Ref: Core and Builtins<36>-Footnote-64027241
Ref: Core and Builtins<36>-Footnote-74027306
Ref: Core and Builtins<36>-Footnote-84027371
Ref: Core and Builtins<36>-Footnote-94027436
Ref: Core and Builtins<36>-Footnote-104027501
Ref: Core and Builtins<36>-Footnote-114027567
Ref: Core and Builtins<36>-Footnote-124027633
Ref: Core and Builtins<36>-Footnote-134027699
Ref: Core and Builtins<36>-Footnote-144027765
Ref: Core and Builtins<36>-Footnote-154027831
Ref: Core and Builtins<36>-Footnote-164027897
Ref: Core and Builtins<36>-Footnote-174027963
Ref: Core and Builtins<36>-Footnote-184028029
Ref: Core and Builtins<36>-Footnote-194028095
Ref: Core and Builtins<36>-Footnote-204028161
Ref: Core and Builtins<36>-Footnote-214028227
Node: Library<35>4028270
Ref: whatsnew/changelog id3034028395
Ref: 18314028395
Ref: Library<35>-Footnote-14035411
Ref: Library<35>-Footnote-24035476
Ref: Library<35>-Footnote-34035541
Ref: Library<35>-Footnote-44035606
Ref: Library<35>-Footnote-54035671
Ref: Library<35>-Footnote-64035736
Ref: Library<35>-Footnote-74035801
Ref: Library<35>-Footnote-84035843
Ref: Library<35>-Footnote-94035908
Ref: Library<35>-Footnote-104035973
Ref: Library<35>-Footnote-114036039
Ref: Library<35>-Footnote-124036105
Ref: Library<35>-Footnote-134036171
Ref: Library<35>-Footnote-144036237
Ref: Library<35>-Footnote-154036303
Ref: Library<35>-Footnote-164036369
Ref: Library<35>-Footnote-174036435
Ref: Library<35>-Footnote-184036501
Ref: Library<35>-Footnote-194036567
Ref: Library<35>-Footnote-204036633
Ref: Library<35>-Footnote-214036699
Ref: Library<35>-Footnote-224036765
Ref: Library<35>-Footnote-234036831
Ref: Library<35>-Footnote-244036897
Ref: Library<35>-Footnote-254036963
Ref: Library<35>-Footnote-264037006
Ref: Library<35>-Footnote-274037072
Ref: Library<35>-Footnote-284037138
Ref: Library<35>-Footnote-294037204
Ref: Library<35>-Footnote-304037270
Ref: Library<35>-Footnote-314037336
Ref: Library<35>-Footnote-324037402
Ref: Library<35>-Footnote-334037468
Ref: Library<35>-Footnote-344037534
Ref: Library<35>-Footnote-354037600
Ref: Library<35>-Footnote-364037666
Ref: Library<35>-Footnote-374037731
Ref: Library<35>-Footnote-384037797
Ref: Library<35>-Footnote-394037863
Ref: Library<35>-Footnote-404037929
Ref: Library<35>-Footnote-414037995
Node: Documentation<30>4038061
Ref: whatsnew/changelog id3044038174
Ref: 18334038174
Ref: Documentation<30>-Footnote-14039022
Ref: Documentation<30>-Footnote-24039087
Ref: Documentation<30>-Footnote-34039152
Ref: Documentation<30>-Footnote-44039217
Ref: Documentation<30>-Footnote-54039282
Ref: Documentation<30>-Footnote-64039347
Node: Tests<33>4039412
Ref: whatsnew/changelog id3054039523
Ref: 18364039523
Ref: Tests<33>-Footnote-14040160
Ref: Tests<33>-Footnote-24040225
Ref: Tests<33>-Footnote-34040290
Ref: Tests<33>-Footnote-44040355
Node: Build<35>4040420
Ref: whatsnew/changelog id3064040525
Ref: 18374040525
Ref: Build<35>-Footnote-14040789
Node: Windows<31>4040854
Ref: whatsnew/changelog id3074040959
Ref: 18384040959
Ref: Windows<31>-Footnote-14041435
Ref: Windows<31>-Footnote-24041500
Ref: Windows<31>-Footnote-34041565
Ref: Windows<31>-Footnote-44041630
Ref: Windows<31>-Footnote-54041695
Node: macOS<26>4041760
Ref: whatsnew/changelog id3084041864
Ref: 18394041864
Ref: macOS<26>-Footnote-14042014
Node: IDLE<23>4042079
Ref: whatsnew/changelog id3094042181
Ref: 183a4042181
Ref: IDLE<23>-Footnote-14042790
Ref: IDLE<23>-Footnote-24042855
Ref: IDLE<23>-Footnote-34042920
Node: C API<34>4042985
Ref: whatsnew/changelog id3104043069
Ref: 183b4043069
Ref: C API<34>-Footnote-14044402
Ref: C API<34>-Footnote-24044467
Ref: C API<34>-Footnote-34044532
Ref: C API<34>-Footnote-44044597
Ref: C API<34>-Footnote-54044662
Ref: C API<34>-Footnote-64044727
Ref: C API<34>-Footnote-74044792
Ref: C API<34>-Footnote-84044857
Node: Python 3 10 0 alpha 14044922
Ref: whatsnew/changelog python-3-10-0-alpha-14045065
Ref: 183d4045065
Node: Security<23>4045416
Ref: whatsnew/changelog id3114045516
Ref: 183e4045516
Ref: Security<23>-Footnote-14046417
Ref: Security<23>-Footnote-24046482
Ref: Security<23>-Footnote-34046547
Ref: Security<23>-Footnote-44046617
Ref: Security<23>-Footnote-54046682
Ref: Security<23>-Footnote-64046747
Ref: Security<23>-Footnote-74046817
Ref: Security<23>-Footnote-84046882
Node: Core and Builtins<37>4046947
Ref: whatsnew/changelog id3124047067
Ref: 183f4047067
Ref: Core and Builtins<37>-Footnote-14062563
Ref: Core and Builtins<37>-Footnote-24062628
Ref: Core and Builtins<37>-Footnote-34062693
Ref: Core and Builtins<37>-Footnote-44062735
Ref: Core and Builtins<37>-Footnote-54062800
Ref: Core and Builtins<37>-Footnote-64062865
Ref: Core and Builtins<37>-Footnote-74062907
Ref: Core and Builtins<37>-Footnote-84062974
Ref: Core and Builtins<37>-Footnote-94063016
Ref: Core and Builtins<37>-Footnote-104063081
Ref: Core and Builtins<37>-Footnote-114063147
Ref: Core and Builtins<37>-Footnote-124063215
Ref: Core and Builtins<37>-Footnote-134063258
Ref: Core and Builtins<37>-Footnote-144063326
Ref: Core and Builtins<37>-Footnote-154063369
Ref: Core and Builtins<37>-Footnote-164063437
Ref: Core and Builtins<37>-Footnote-174063480
Ref: Core and Builtins<37>-Footnote-184063548
Ref: Core and Builtins<37>-Footnote-194063591
Ref: Core and Builtins<37>-Footnote-204063659
Ref: Core and Builtins<37>-Footnote-214063725
Ref: Core and Builtins<37>-Footnote-224063793
Ref: Core and Builtins<37>-Footnote-234063836
Ref: Core and Builtins<37>-Footnote-244063904
Ref: Core and Builtins<37>-Footnote-254063947
Ref: Core and Builtins<37>-Footnote-264064015
Ref: Core and Builtins<37>-Footnote-274064058
Ref: Core and Builtins<37>-Footnote-284064124
Ref: Core and Builtins<37>-Footnote-294064190
Ref: Core and Builtins<37>-Footnote-304064256
Ref: Core and Builtins<37>-Footnote-314064322
Ref: Core and Builtins<37>-Footnote-324064390
Ref: Core and Builtins<37>-Footnote-334064433
Ref: Core and Builtins<37>-Footnote-344064499
Ref: Core and Builtins<37>-Footnote-354064565
Ref: Core and Builtins<37>-Footnote-364064633
Ref: Core and Builtins<37>-Footnote-374064701
Ref: Core and Builtins<37>-Footnote-384064744
Ref: Core and Builtins<37>-Footnote-394064810
Ref: Core and Builtins<37>-Footnote-404064876
Ref: Core and Builtins<37>-Footnote-414064942
Ref: Core and Builtins<37>-Footnote-424065010
Ref: Core and Builtins<37>-Footnote-434065053
Ref: Core and Builtins<37>-Footnote-444065119
Ref: Core and Builtins<37>-Footnote-454065185
Ref: Core and Builtins<37>-Footnote-464065251
Ref: Core and Builtins<37>-Footnote-474065317
Ref: Core and Builtins<37>-Footnote-484065383
Ref: Core and Builtins<37>-Footnote-494065449
Ref: Core and Builtins<37>-Footnote-504065515
Ref: Core and Builtins<37>-Footnote-514065581
Ref: Core and Builtins<37>-Footnote-524065647
Ref: Core and Builtins<37>-Footnote-534065713
Ref: Core and Builtins<37>-Footnote-544065781
Ref: Core and Builtins<37>-Footnote-554065849
Ref: Core and Builtins<37>-Footnote-564065915
Ref: Core and Builtins<37>-Footnote-574065981
Ref: Core and Builtins<37>-Footnote-584066049
Ref: Core and Builtins<37>-Footnote-594066117
Ref: Core and Builtins<37>-Footnote-604066183
Ref: Core and Builtins<37>-Footnote-614066249
Ref: Core and Builtins<37>-Footnote-624066315
Ref: Core and Builtins<37>-Footnote-634066381
Ref: Core and Builtins<37>-Footnote-644066447
Ref: Core and Builtins<37>-Footnote-654066513
Ref: Core and Builtins<37>-Footnote-664066579
Ref: Core and Builtins<37>-Footnote-674066645
Ref: Core and Builtins<37>-Footnote-684066711
Ref: Core and Builtins<37>-Footnote-694066777
Ref: Core and Builtins<37>-Footnote-704066843
Ref: Core and Builtins<37>-Footnote-714066909
Ref: Core and Builtins<37>-Footnote-724066975
Ref: Core and Builtins<37>-Footnote-734067041
Ref: Core and Builtins<37>-Footnote-744067107
Ref: Core and Builtins<37>-Footnote-754067173
Ref: Core and Builtins<37>-Footnote-764067216
Ref: Core and Builtins<37>-Footnote-774067284
Ref: Core and Builtins<37>-Footnote-784067350
Ref: Core and Builtins<37>-Footnote-794067416
Ref: Core and Builtins<37>-Footnote-804067484
Ref: Core and Builtins<37>-Footnote-814067550
Ref: Core and Builtins<37>-Footnote-824067616
Ref: Core and Builtins<37>-Footnote-834067659
Ref: Core and Builtins<37>-Footnote-844067725
Ref: Core and Builtins<37>-Footnote-854067791
Ref: Core and Builtins<37>-Footnote-864067857
Ref: Core and Builtins<37>-Footnote-874067923
Ref: Core and Builtins<37>-Footnote-884067989
Ref: Core and Builtins<37>-Footnote-894068055
Ref: Core and Builtins<37>-Footnote-904068121
Ref: Core and Builtins<37>-Footnote-914068187
Ref: Core and Builtins<37>-Footnote-924068253
Ref: Core and Builtins<37>-Footnote-934068319
Ref: Core and Builtins<37>-Footnote-944068385
Ref: Core and Builtins<37>-Footnote-954068451
Ref: Core and Builtins<37>-Footnote-964068519
Ref: Core and Builtins<37>-Footnote-974068585
Ref: Core and Builtins<37>-Footnote-984068651
Ref: Core and Builtins<37>-Footnote-994068717
Ref: Core and Builtins<37>-Footnote-1004068783
Ref: Core and Builtins<37>-Footnote-1014068850
Ref: Core and Builtins<37>-Footnote-1024068917
Ref: Core and Builtins<37>-Footnote-1034068984
Ref: Core and Builtins<37>-Footnote-1044069051
Ref: Core and Builtins<37>-Footnote-1054069118
Ref: Core and Builtins<37>-Footnote-1064069185
Ref: Core and Builtins<37>-Footnote-1074069252
Ref: Core and Builtins<37>-Footnote-1084069319
Ref: Core and Builtins<37>-Footnote-1094069385
Ref: Core and Builtins<37>-Footnote-1104069454
Ref: Core and Builtins<37>-Footnote-1114069523
Ref: Core and Builtins<37>-Footnote-1124069590
Ref: Core and Builtins<37>-Footnote-1134069657
Ref: Core and Builtins<37>-Footnote-1144069724
Ref: Core and Builtins<37>-Footnote-1154069791
Node: Library<36>4069858
Ref: whatsnew/changelog id3134069983
Ref: 18444069983
Ref: Library<36>-Footnote-14092122
Ref: Library<36>-Footnote-24092187
Ref: Library<36>-Footnote-34092252
Ref: Library<36>-Footnote-44092317
Ref: Library<36>-Footnote-54092382
Ref: Library<36>-Footnote-64092447
Ref: Library<36>-Footnote-74092512
Ref: Library<36>-Footnote-84092577
Ref: Library<36>-Footnote-94092642
Ref: Library<36>-Footnote-104092707
Ref: Library<36>-Footnote-114092773
Ref: Library<36>-Footnote-124092839
Ref: Library<36>-Footnote-134092905
Ref: Library<36>-Footnote-144092971
Ref: Library<36>-Footnote-154093037
Ref: Library<36>-Footnote-164093103
Ref: Library<36>-Footnote-174093156
Ref: Library<36>-Footnote-184093222
Ref: Library<36>-Footnote-194093288
Ref: Library<36>-Footnote-204093354
Ref: Library<36>-Footnote-214093422
Ref: Library<36>-Footnote-224093465
Ref: Library<36>-Footnote-234093533
Ref: Library<36>-Footnote-244093576
Ref: Library<36>-Footnote-254093642
Ref: Library<36>-Footnote-264093708
Ref: Library<36>-Footnote-274093774
Ref: Library<36>-Footnote-284093840
Ref: Library<36>-Footnote-294093906
Ref: Library<36>-Footnote-304093972
Ref: Library<36>-Footnote-314094038
Ref: Library<36>-Footnote-324094104
Ref: Library<36>-Footnote-334094170
Ref: Library<36>-Footnote-344094236
Ref: Library<36>-Footnote-354094302
Ref: Library<36>-Footnote-364094368
Ref: Library<36>-Footnote-374094434
Ref: Library<36>-Footnote-384094500
Ref: Library<36>-Footnote-394094566
Ref: Library<36>-Footnote-404094632
Ref: Library<36>-Footnote-414094698
Ref: Library<36>-Footnote-424094764
Ref: Library<36>-Footnote-434094830
Ref: Library<36>-Footnote-444094896
Ref: Library<36>-Footnote-454094962
Ref: Library<36>-Footnote-464095028
Ref: Library<36>-Footnote-474095094
Ref: Library<36>-Footnote-484095160
Ref: Library<36>-Footnote-494095226
Ref: Library<36>-Footnote-504095292
Ref: Library<36>-Footnote-514095358
Ref: Library<36>-Footnote-524095424
Ref: Library<36>-Footnote-534095490
Ref: Library<36>-Footnote-544095556
Ref: Library<36>-Footnote-554095622
Ref: Library<36>-Footnote-564095688
Ref: Library<36>-Footnote-574095754
Ref: Library<36>-Footnote-584095825
Ref: Library<36>-Footnote-594095891
Ref: Library<36>-Footnote-604095957
Ref: Library<36>-Footnote-614096023
Ref: Library<36>-Footnote-624096089
Ref: Library<36>-Footnote-634096155
Ref: Library<36>-Footnote-644096221
Ref: Library<36>-Footnote-654096287
Ref: Library<36>-Footnote-664096353
Ref: Library<36>-Footnote-674096419
Ref: Library<36>-Footnote-684096485
Ref: Library<36>-Footnote-694096551
Ref: Library<36>-Footnote-704096617
Ref: Library<36>-Footnote-714096683
Ref: Library<36>-Footnote-724096749
Ref: Library<36>-Footnote-734096815
Ref: Library<36>-Footnote-744096881
Ref: Library<36>-Footnote-754096947
Ref: Library<36>-Footnote-764097013
Ref: Library<36>-Footnote-774097079
Ref: Library<36>-Footnote-784097145
Ref: Library<36>-Footnote-794097211
Ref: Library<36>-Footnote-804097277
Ref: Library<36>-Footnote-814097343
Ref: Library<36>-Footnote-824097409
Ref: Library<36>-Footnote-834097475
Ref: Library<36>-Footnote-844097541
Ref: Library<36>-Footnote-854097607
Ref: Library<36>-Footnote-864097673
Ref: Library<36>-Footnote-874097739
Ref: Library<36>-Footnote-884097805
Ref: Library<36>-Footnote-894097871
Ref: Library<36>-Footnote-904097937
Ref: Library<36>-Footnote-914098003
Ref: Library<36>-Footnote-924098069
Ref: Library<36>-Footnote-934098135
Ref: Library<36>-Footnote-944098201
Ref: Library<36>-Footnote-954098267
Ref: Library<36>-Footnote-964098333
Ref: Library<36>-Footnote-974098399
Ref: Library<36>-Footnote-984098465
Ref: Library<36>-Footnote-994098531
Ref: Library<36>-Footnote-1004098597
Ref: Library<36>-Footnote-1014098664
Ref: Library<36>-Footnote-1024098731
Ref: Library<36>-Footnote-1034098798
Ref: Library<36>-Footnote-1044098865
Ref: Library<36>-Footnote-1054098932
Ref: Library<36>-Footnote-1064098999
Ref: Library<36>-Footnote-1074099066
Ref: Library<36>-Footnote-1084099133
Ref: Library<36>-Footnote-1094099200
Ref: Library<36>-Footnote-1104099267
Ref: Library<36>-Footnote-1114099334
Ref: Library<36>-Footnote-1124099401
Ref: Library<36>-Footnote-1134099468
Ref: Library<36>-Footnote-1144099535
Ref: Library<36>-Footnote-1154099602
Ref: Library<36>-Footnote-1164099669
Ref: Library<36>-Footnote-1174099736
Ref: Library<36>-Footnote-1184099803
Ref: Library<36>-Footnote-1194099870
Ref: Library<36>-Footnote-1204099937
Ref: Library<36>-Footnote-1214100003
Ref: Library<36>-Footnote-1224100070
Ref: Library<36>-Footnote-1234100137
Ref: Library<36>-Footnote-1244100204
Ref: Library<36>-Footnote-1254100271
Ref: Library<36>-Footnote-1264100315
Ref: Library<36>-Footnote-1274100382
Ref: Library<36>-Footnote-1284100449
Ref: Library<36>-Footnote-1294100516
Ref: Library<36>-Footnote-1304100583
Ref: Library<36>-Footnote-1314100650
Ref: Library<36>-Footnote-1324100717
Ref: Library<36>-Footnote-1334100784
Ref: Library<36>-Footnote-1344100851
Ref: Library<36>-Footnote-1354100918
Ref: Library<36>-Footnote-1364100985
Ref: Library<36>-Footnote-1374101052
Ref: Library<36>-Footnote-1384101119
Ref: Library<36>-Footnote-1394101186
Ref: Library<36>-Footnote-1404101253
Ref: Library<36>-Footnote-1414101320
Ref: Library<36>-Footnote-1424101387
Ref: Library<36>-Footnote-1434101454
Ref: Library<36>-Footnote-1444101521
Ref: Library<36>-Footnote-1454101588
Ref: Library<36>-Footnote-1464101655
Ref: Library<36>-Footnote-1474101722
Ref: Library<36>-Footnote-1484101789
Ref: Library<36>-Footnote-1494101856
Ref: Library<36>-Footnote-1504101923
Ref: Library<36>-Footnote-1514101990
Ref: Library<36>-Footnote-1524102057
Ref: Library<36>-Footnote-1534102124
Ref: Library<36>-Footnote-1544102191
Node: Documentation<31>4102258
Ref: whatsnew/changelog id3144102371
Ref: 184b4102371
Ref: Documentation<31>-Footnote-14104128
Ref: Documentation<31>-Footnote-24104193
Ref: Documentation<31>-Footnote-34104235
Ref: Documentation<31>-Footnote-44104300
Ref: Documentation<31>-Footnote-54104365
Ref: Documentation<31>-Footnote-64104430
Ref: Documentation<31>-Footnote-74104495
Ref: Documentation<31>-Footnote-84104560
Ref: Documentation<31>-Footnote-94104625
Ref: Documentation<31>-Footnote-104104690
Ref: Documentation<31>-Footnote-114104756
Ref: Documentation<31>-Footnote-124104822
Ref: Documentation<31>-Footnote-134104888
Ref: Documentation<31>-Footnote-144104954
Node: Tests<34>4105020
Ref: whatsnew/changelog id3154105131
Ref: 184d4105131
Ref: Tests<34>-Footnote-14107280
Ref: Tests<34>-Footnote-24107345
Ref: Tests<34>-Footnote-34107410
Ref: Tests<34>-Footnote-44107475
Ref: Tests<34>-Footnote-54107540
Ref: Tests<34>-Footnote-64107605
Ref: Tests<34>-Footnote-74107670
Ref: Tests<34>-Footnote-84107735
Ref: Tests<34>-Footnote-94107800
Ref: Tests<34>-Footnote-104107865
Ref: Tests<34>-Footnote-114107931
Ref: Tests<34>-Footnote-124107997
Ref: Tests<34>-Footnote-134108063
Ref: Tests<34>-Footnote-144108129
Ref: Tests<34>-Footnote-154108195
Ref: Tests<34>-Footnote-164108261
Node: Build<36>4108327
Ref: whatsnew/changelog id3164108432
Ref: 18504108432
Ref: Build<36>-Footnote-14109351
Ref: Build<36>-Footnote-24109416
Ref: Build<36>-Footnote-34109481
Ref: Build<36>-Footnote-44109546
Ref: Build<36>-Footnote-54109611
Ref: Build<36>-Footnote-64109676
Node: Windows<32>4109741
Ref: whatsnew/changelog id3174109846
Ref: 18514109846
Ref: Windows<32>-Footnote-14111609
Ref: Windows<32>-Footnote-24111674
Ref: Windows<32>-Footnote-34111739
Ref: Windows<32>-Footnote-44111804
Ref: Windows<32>-Footnote-54111869
Ref: Windows<32>-Footnote-64111934
Ref: Windows<32>-Footnote-74111999
Ref: Windows<32>-Footnote-84112064
Ref: Windows<32>-Footnote-94112129
Ref: Windows<32>-Footnote-104112194
Ref: Windows<32>-Footnote-114112260
Ref: Windows<32>-Footnote-124112326
Ref: Windows<32>-Footnote-134112392
Ref: Windows<32>-Footnote-144112458
Node: macOS<27>4112524
Ref: whatsnew/changelog id3184112628
Ref: 18524112628
Ref: macOS<27>-Footnote-14113517
Ref: macOS<27>-Footnote-24113582
Ref: macOS<27>-Footnote-34113647
Ref: macOS<27>-Footnote-44113712
Ref: macOS<27>-Footnote-54113777
Ref: macOS<27>-Footnote-64113842
Node: IDLE<24>4113907
Ref: whatsnew/changelog id3194114009
Ref: 18534114009
Ref: IDLE<24>-Footnote-14115164
Ref: IDLE<24>-Footnote-24115229
Ref: IDLE<24>-Footnote-34115294
Ref: IDLE<24>-Footnote-44115359
Ref: IDLE<24>-Footnote-54115424
Ref: IDLE<24>-Footnote-64115489
Ref: IDLE<24>-Footnote-74115554
Ref: IDLE<24>-Footnote-84115619
Ref: IDLE<24>-Footnote-94115684
Ref: IDLE<24>-Footnote-104115749
Ref: IDLE<24>-Footnote-114115815
Node: C API<35>4115881
Ref: whatsnew/changelog id3204115965
Ref: 18544115965
Ref: C API<35>-Footnote-14121074
Ref: C API<35>-Footnote-24121139
Ref: C API<35>-Footnote-34121204
Ref: C API<35>-Footnote-44121269
Ref: C API<35>-Footnote-54121334
Ref: C API<35>-Footnote-64121399
Ref: C API<35>-Footnote-74121464
Ref: C API<35>-Footnote-84121529
Ref: C API<35>-Footnote-94121594
Ref: C API<35>-Footnote-104121659
Ref: C API<35>-Footnote-114121725
Ref: C API<35>-Footnote-124121791
Ref: C API<35>-Footnote-134121857
Ref: C API<35>-Footnote-144121923
Ref: C API<35>-Footnote-154121989
Ref: C API<35>-Footnote-164122055
Ref: C API<35>-Footnote-174122121
Ref: C API<35>-Footnote-184122187
Ref: C API<35>-Footnote-194122253
Ref: C API<35>-Footnote-204122319
Ref: C API<35>-Footnote-214122362
Ref: C API<35>-Footnote-224122428
Ref: C API<35>-Footnote-234122494
Ref: C API<35>-Footnote-244122560
Ref: C API<35>-Footnote-254122626
Ref: C API<35>-Footnote-264122692
Ref: C API<35>-Footnote-274122758
Ref: C API<35>-Footnote-284122824
Ref: C API<35>-Footnote-294122890
Node: Python 3 9 0 beta 14122956
Ref: whatsnew/changelog python-3-9-0-beta-14123098
Ref: 18594123098
Node: Security<24>4123459
Ref: whatsnew/changelog id3214123557
Ref: 185a4123557
Ref: Security<24>-Footnote-14123760
Node: Core and Builtins<38>4123825
Ref: whatsnew/changelog id3224123943
Ref: 185b4123943
Ref: Core and Builtins<38>-Footnote-14126486
Ref: Core and Builtins<38>-Footnote-24126551
Ref: Core and Builtins<38>-Footnote-34126616
Ref: Core and Builtins<38>-Footnote-44126681
Ref: Core and Builtins<38>-Footnote-54126746
Ref: Core and Builtins<38>-Footnote-64126811
Ref: Core and Builtins<38>-Footnote-74126853
Ref: Core and Builtins<38>-Footnote-84126918
Ref: Core and Builtins<38>-Footnote-94126983
Ref: Core and Builtins<38>-Footnote-104127050
Ref: Core and Builtins<38>-Footnote-114127093
Ref: Core and Builtins<38>-Footnote-124127159
Ref: Core and Builtins<38>-Footnote-134127227
Ref: Core and Builtins<38>-Footnote-144127270
Ref: Core and Builtins<38>-Footnote-154127336
Ref: Core and Builtins<38>-Footnote-164127402
Ref: Core and Builtins<38>-Footnote-174127468
Ref: Core and Builtins<38>-Footnote-184127534
Ref: Core and Builtins<38>-Footnote-194127602
Ref: Core and Builtins<38>-Footnote-204127645
Ref: Core and Builtins<38>-Footnote-214127711
Ref: Core and Builtins<38>-Footnote-224127777
Ref: Core and Builtins<38>-Footnote-234127843
Ref: Core and Builtins<38>-Footnote-244127909
Node: Library<37>4127975
Ref: whatsnew/changelog id3234128098
Ref: 185d4128098
Ref: Library<37>-Footnote-14135472
Ref: Library<37>-Footnote-24135537
Ref: Library<37>-Footnote-34135602
Ref: Library<37>-Footnote-44135667
Ref: Library<37>-Footnote-54135732
Ref: Library<37>-Footnote-64135797
Ref: Library<37>-Footnote-74135862
Ref: Library<37>-Footnote-84135927
Ref: Library<37>-Footnote-94135992
Ref: Library<37>-Footnote-104136057
Ref: Library<37>-Footnote-114136123
Ref: Library<37>-Footnote-124136189
Ref: Library<37>-Footnote-134136255
Ref: Library<37>-Footnote-144136321
Ref: Library<37>-Footnote-154136387
Ref: Library<37>-Footnote-164136430
Ref: Library<37>-Footnote-174136496
Ref: Library<37>-Footnote-184136562
Ref: Library<37>-Footnote-194136628
Ref: Library<37>-Footnote-204136694
Ref: Library<37>-Footnote-214136760
Ref: Library<37>-Footnote-224136826
Ref: Library<37>-Footnote-234136892
Ref: Library<37>-Footnote-244136958
Ref: Library<37>-Footnote-254137024
Ref: Library<37>-Footnote-264137090
Ref: Library<37>-Footnote-274137156
Ref: Library<37>-Footnote-284137222
Ref: Library<37>-Footnote-294137288
Ref: Library<37>-Footnote-304137354
Ref: Library<37>-Footnote-314137420
Ref: Library<37>-Footnote-324137486
Ref: Library<37>-Footnote-334137552
Ref: Library<37>-Footnote-344137618
Ref: Library<37>-Footnote-354137684
Ref: Library<37>-Footnote-364137750
Ref: Library<37>-Footnote-374137816
Ref: Library<37>-Footnote-384137882
Ref: Library<37>-Footnote-394137948
Ref: Library<37>-Footnote-404138014
Ref: Library<37>-Footnote-414138080
Ref: Library<37>-Footnote-424138146
Ref: Library<37>-Footnote-434138212
Ref: Library<37>-Footnote-444138278
Ref: Library<37>-Footnote-454138344
Ref: Library<37>-Footnote-464138410
Ref: Library<37>-Footnote-474138476
Ref: Library<37>-Footnote-484138542
Ref: Library<37>-Footnote-494138608
Ref: Library<37>-Footnote-504138674
Node: Documentation<32>4138740
Ref: whatsnew/changelog id3244138851
Ref: 18624138851
Ref: Documentation<32>-Footnote-14139516
Ref: Documentation<32>-Footnote-24139581
Ref: Documentation<32>-Footnote-34139646
Ref: Documentation<32>-Footnote-44139711
Ref: Documentation<32>-Footnote-54139776
Node: Tests<35>4139841
Ref: whatsnew/changelog id3254139950
Ref: 18634139950
Ref: Tests<35>-Footnote-14140305
Ref: Tests<35>-Footnote-24140370
Node: Build<37>4140435
Ref: whatsnew/changelog id3264140538
Ref: 18644140538
Ref: Build<37>-Footnote-14140878
Ref: Build<37>-Footnote-24140943
Node: Windows<33>4141008
Ref: whatsnew/changelog id3274141111
Ref: 18654141111
Ref: Windows<33>-Footnote-14141564
Ref: Windows<33>-Footnote-24141629
Ref: Windows<33>-Footnote-34141694
Node: macOS<28>4141759
Ref: whatsnew/changelog id3284141868
Ref: 18664141868
Ref: macOS<28>-Footnote-14142491
Ref: macOS<28>-Footnote-24142556
Node: Tools/Demos<16>4142621
Ref: whatsnew/changelog id3294142728
Ref: 18674142728
Ref: Tools/Demos<16>-Footnote-14143213
Ref: Tools/Demos<16>-Footnote-24143278
Ref: Tools/Demos<16>-Footnote-34143343
Node: C API<36>4143408
Ref: whatsnew/changelog id3304143497
Ref: 18684143497
Ref: C API<36>-Footnote-14145523
Ref: C API<36>-Footnote-24145588
Ref: C API<36>-Footnote-34145653
Ref: C API<36>-Footnote-44145718
Ref: C API<36>-Footnote-54145783
Ref: C API<36>-Footnote-64145848
Ref: C API<36>-Footnote-74145913
Ref: C API<36>-Footnote-84145978
Ref: C API<36>-Footnote-94146043
Ref: C API<36>-Footnote-104146108
Ref: C API<36>-Footnote-114146174
Node: Python 3 9 0 alpha 64146217
Ref: whatsnew/changelog python-3-9-0-alpha-64146358
Ref: 18694146358
Node: Security<25>4146739
Ref: whatsnew/changelog id3314146838
Ref: 186a4146838
Ref: Security<25>-Footnote-14147485
Ref: Security<25>-Footnote-24147550
Ref: Security<25>-Footnote-34147615
Ref: Security<25>-Footnote-44147680
Node: Core and Builtins<39>4147749
Ref: whatsnew/changelog id3324147868
Ref: 186b4147868
Ref: Core and Builtins<39>-Footnote-14151642
Ref: Core and Builtins<39>-Footnote-24151707
Ref: Core and Builtins<39>-Footnote-34151772
Ref: Core and Builtins<39>-Footnote-44151837
Ref: Core and Builtins<39>-Footnote-54151902
Ref: Core and Builtins<39>-Footnote-64151967
Ref: Core and Builtins<39>-Footnote-74152032
Ref: Core and Builtins<39>-Footnote-84152097
Ref: Core and Builtins<39>-Footnote-94152162
Ref: Core and Builtins<39>-Footnote-104152227
Ref: Core and Builtins<39>-Footnote-114152270
Ref: Core and Builtins<39>-Footnote-124152336
Ref: Core and Builtins<39>-Footnote-134152404
Ref: Core and Builtins<39>-Footnote-144152447
Ref: Core and Builtins<39>-Footnote-154152515
Ref: Core and Builtins<39>-Footnote-164152558
Ref: Core and Builtins<39>-Footnote-174152626
Ref: Core and Builtins<39>-Footnote-184152669
Ref: Core and Builtins<39>-Footnote-194152735
Ref: Core and Builtins<39>-Footnote-204152801
Ref: Core and Builtins<39>-Footnote-214152869
Ref: Core and Builtins<39>-Footnote-224152937
Ref: Core and Builtins<39>-Footnote-234153003
Ref: Core and Builtins<39>-Footnote-244153071
Ref: Core and Builtins<39>-Footnote-254153114
Ref: Core and Builtins<39>-Footnote-264153182
Ref: Core and Builtins<39>-Footnote-274153225
Ref: Core and Builtins<39>-Footnote-284153291
Ref: Core and Builtins<39>-Footnote-294153357
Ref: Core and Builtins<39>-Footnote-304153400
Ref: Core and Builtins<39>-Footnote-314153466
Ref: Core and Builtins<39>-Footnote-324153532
Ref: Core and Builtins<39>-Footnote-334153598
Node: Library<38>4153641
Ref: whatsnew/changelog id3334153765
Ref: 186c4153765
Ref: Library<38>-Footnote-14163990
Ref: Library<38>-Footnote-24164055
Ref: Library<38>-Footnote-34164120
Ref: Library<38>-Footnote-44164185
Ref: Library<38>-Footnote-54164250
Ref: Library<38>-Footnote-64164315
Ref: Library<38>-Footnote-74164357
Ref: Library<38>-Footnote-84164422
Ref: Library<38>-Footnote-94164487
Ref: Library<38>-Footnote-104164552
Ref: Library<38>-Footnote-114164618
Ref: Library<38>-Footnote-124164684
Ref: Library<38>-Footnote-134164750
Ref: Library<38>-Footnote-144164816
Ref: Library<38>-Footnote-154164882
Ref: Library<38>-Footnote-164164948
Ref: Library<38>-Footnote-174165014
Ref: Library<38>-Footnote-184165080
Ref: Library<38>-Footnote-194165146
Ref: Library<38>-Footnote-204165212
Ref: Library<38>-Footnote-214165278
Ref: Library<38>-Footnote-224165344
Ref: Library<38>-Footnote-234165410
Ref: Library<38>-Footnote-244165476
Ref: Library<38>-Footnote-254165542
Ref: Library<38>-Footnote-264165608
Ref: Library<38>-Footnote-274165674
Ref: Library<38>-Footnote-284165740
Ref: Library<38>-Footnote-294165806
Ref: Library<38>-Footnote-304165872
Ref: Library<38>-Footnote-314165938
Ref: Library<38>-Footnote-324166004
Ref: Library<38>-Footnote-334166070
Ref: Library<38>-Footnote-344166136
Ref: Library<38>-Footnote-354166202
Ref: Library<38>-Footnote-364166268
Ref: Library<38>-Footnote-374166334
Ref: Library<38>-Footnote-384166400
Ref: Library<38>-Footnote-394166466
Ref: Library<38>-Footnote-404166532
Ref: Library<38>-Footnote-414166598
Ref: Library<38>-Footnote-424166664
Ref: Library<38>-Footnote-434166730
Ref: Library<38>-Footnote-444166796
Ref: Library<38>-Footnote-454166862
Ref: Library<38>-Footnote-464166928
Ref: Library<38>-Footnote-474166994
Ref: Library<38>-Footnote-484167060
Ref: Library<38>-Footnote-494167103
Ref: Library<38>-Footnote-504167169
Ref: Library<38>-Footnote-514167212
Ref: Library<38>-Footnote-524167278
Ref: Library<38>-Footnote-534167344
Ref: Library<38>-Footnote-544167410
Ref: Library<38>-Footnote-554167453
Ref: Library<38>-Footnote-564167519
Ref: Library<38>-Footnote-574167585
Ref: Library<38>-Footnote-584167651
Ref: Library<38>-Footnote-594167717
Ref: Library<38>-Footnote-604167783
Ref: Library<38>-Footnote-614167849
Node: Documentation<33>4167915
Ref: whatsnew/changelog id3344168027
Ref: 18744168027
Ref: Documentation<33>-Footnote-14168602
Ref: Documentation<33>-Footnote-24168667
Ref: Documentation<33>-Footnote-34168732
Ref: Documentation<33>-Footnote-44168797
Node: Tests<36>4168862
Ref: whatsnew/changelog id3354168972
Ref: 18774168972
Ref: Tests<36>-Footnote-14170053
Ref: Tests<36>-Footnote-24170118
Ref: Tests<36>-Footnote-34170183
Ref: Tests<36>-Footnote-44170248
Ref: Tests<36>-Footnote-54170313
Ref: Tests<36>-Footnote-64170378
Ref: Tests<36>-Footnote-74170443
Ref: Tests<36>-Footnote-84170502
Ref: Tests<36>-Footnote-94170567
Node: Build<38>4170631
Ref: whatsnew/changelog id3364170735
Ref: 18794170735
Ref: Build<38>-Footnote-14171148
Ref: Build<38>-Footnote-24171213
Ref: Build<38>-Footnote-34171278
Node: Windows<34>4171343
Ref: whatsnew/changelog id3374171447
Ref: 187a4171447
Ref: Windows<34>-Footnote-14171660
Ref: Windows<34>-Footnote-24171725
Node: macOS<29>4171789
Ref: whatsnew/changelog id3384171892
Ref: 187b4171892
Ref: macOS<29>-Footnote-14172348
Ref: macOS<29>-Footnote-24172413
Node: IDLE<25>4172478
Ref: whatsnew/changelog id3394172585
Ref: 187c4172585
Ref: IDLE<25>-Footnote-14172929
Ref: IDLE<25>-Footnote-24172994
Node: Tools/Demos<17>4173059
Ref: whatsnew/changelog id3404173166
Ref: 187d4173166
Ref: Tools/Demos<17>-Footnote-14173633
Ref: Tools/Demos<17>-Footnote-24173698
Ref: Tools/Demos<17>-Footnote-34173763
Node: C API<37>4173828
Ref: whatsnew/changelog id3414173918
Ref: 187e4173918
Ref: C API<37>-Footnote-14175893
Ref: C API<37>-Footnote-24175958
Ref: C API<37>-Footnote-34176023
Ref: C API<37>-Footnote-44176088
Ref: C API<37>-Footnote-54176153
Ref: C API<37>-Footnote-64176218
Ref: C API<37>-Footnote-74176283
Ref: C API<37>-Footnote-84176348
Ref: C API<37>-Footnote-94176413
Node: Python 3 9 0 alpha 54176478
Ref: whatsnew/changelog python-3-9-0-alpha-54176620
Ref: 187f4176620
Node: Security<26>4177001
Ref: whatsnew/changelog id3424177100
Ref: 18804177100
Ref: Security<26>-Footnote-14177384
Ref: Security<26>-Footnote-24177449
Node: Core and Builtins<40>4177519
Ref: whatsnew/changelog id3434177638
Ref: 18814177638
Ref: Core and Builtins<40>-Footnote-14183484
Ref: Core and Builtins<40>-Footnote-24183549
Ref: Core and Builtins<40>-Footnote-34183616
Ref: Core and Builtins<40>-Footnote-44183658
Ref: Core and Builtins<40>-Footnote-54183725
Ref: Core and Builtins<40>-Footnote-64183767
Ref: Core and Builtins<40>-Footnote-74183832
Ref: Core and Builtins<40>-Footnote-84183897
Ref: Core and Builtins<40>-Footnote-94183964
Ref: Core and Builtins<40>-Footnote-104184031
Ref: Core and Builtins<40>-Footnote-114184074
Ref: Core and Builtins<40>-Footnote-124184140
Ref: Core and Builtins<40>-Footnote-134184183
Ref: Core and Builtins<40>-Footnote-144184249
Ref: Core and Builtins<40>-Footnote-154184315
Ref: Core and Builtins<40>-Footnote-164184358
Ref: Core and Builtins<40>-Footnote-174184426
Ref: Core and Builtins<40>-Footnote-184184469
Ref: Core and Builtins<40>-Footnote-194184535
Ref: Core and Builtins<40>-Footnote-204184601
Ref: Core and Builtins<40>-Footnote-214184667
Ref: Core and Builtins<40>-Footnote-224184733
Ref: Core and Builtins<40>-Footnote-234184776
Ref: Core and Builtins<40>-Footnote-244184842
Ref: Core and Builtins<40>-Footnote-254184908
Ref: Core and Builtins<40>-Footnote-264184974
Ref: Core and Builtins<40>-Footnote-274185040
Ref: Core and Builtins<40>-Footnote-284185106
Ref: Core and Builtins<40>-Footnote-294185172
Ref: Core and Builtins<40>-Footnote-304185238
Ref: Core and Builtins<40>-Footnote-314185304
Ref: Core and Builtins<40>-Footnote-324185372
Ref: Core and Builtins<40>-Footnote-334185415
Ref: Core and Builtins<40>-Footnote-344185481
Ref: Core and Builtins<40>-Footnote-354185524
Ref: Core and Builtins<40>-Footnote-364185590
Ref: Core and Builtins<40>-Footnote-374185658
Ref: Core and Builtins<40>-Footnote-384185701
Ref: Core and Builtins<40>-Footnote-394185767
Ref: Core and Builtins<40>-Footnote-404185833
Ref: Core and Builtins<40>-Footnote-414185899
Ref: Core and Builtins<40>-Footnote-424185965
Node: Library<39>4186031
Ref: whatsnew/changelog id3444186155
Ref: 18824186155
Ref: Library<39>-Footnote-14195275
Ref: Library<39>-Footnote-24195340
Ref: Library<39>-Footnote-34195405
Ref: Library<39>-Footnote-44195470
Ref: Library<39>-Footnote-54195535
Ref: Library<39>-Footnote-64195600
Ref: Library<39>-Footnote-74195665
Ref: Library<39>-Footnote-84195730
Ref: Library<39>-Footnote-94195795
Ref: Library<39>-Footnote-104195860
Ref: Library<39>-Footnote-114195926
Ref: Library<39>-Footnote-124195992
Ref: Library<39>-Footnote-134196035
Ref: Library<39>-Footnote-144196101
Ref: Library<39>-Footnote-154196167
Ref: Library<39>-Footnote-164196233
Ref: Library<39>-Footnote-174196276
Ref: Library<39>-Footnote-184196342
Ref: Library<39>-Footnote-194196408
Ref: Library<39>-Footnote-204196474
Ref: Library<39>-Footnote-214196540
Ref: Library<39>-Footnote-224196606
Ref: Library<39>-Footnote-234196672
Ref: Library<39>-Footnote-244196738
Ref: Library<39>-Footnote-254196804
Ref: Library<39>-Footnote-264196870
Ref: Library<39>-Footnote-274196936
Ref: Library<39>-Footnote-284197002
Ref: Library<39>-Footnote-294197068
Ref: Library<39>-Footnote-304197134
Ref: Library<39>-Footnote-314197200
Ref: Library<39>-Footnote-324197266
Ref: Library<39>-Footnote-334197309
Ref: Library<39>-Footnote-344197375
Ref: Library<39>-Footnote-354197441
Ref: Library<39>-Footnote-364197507
Ref: Library<39>-Footnote-374197573
Ref: Library<39>-Footnote-384197639
Ref: Library<39>-Footnote-394197705
Ref: Library<39>-Footnote-404197748
Ref: Library<39>-Footnote-414197814
Ref: Library<39>-Footnote-424197880
Ref: Library<39>-Footnote-434197946
Ref: Library<39>-Footnote-444198012
Ref: Library<39>-Footnote-454198078
Ref: Library<39>-Footnote-464198144
Ref: Library<39>-Footnote-474198210
Ref: Library<39>-Footnote-484198276
Ref: Library<39>-Footnote-494198342
Ref: Library<39>-Footnote-504198408
Ref: Library<39>-Footnote-514198474
Ref: Library<39>-Footnote-524198540
Ref: Library<39>-Footnote-534198606
Ref: Library<39>-Footnote-544198672
Node: Documentation<34>4198738
Ref: whatsnew/changelog id3454198850
Ref: 18884198850
Ref: Documentation<34>-Footnote-14199484
Ref: Documentation<34>-Footnote-24199549
Ref: Documentation<34>-Footnote-34199591
Ref: Documentation<34>-Footnote-44199656
Ref: Documentation<34>-Footnote-54199721
Ref: Documentation<34>-Footnote-64199786
Ref: Documentation<34>-Footnote-74199851
Node: Tests<37>4199916
Ref: whatsnew/changelog id3464200026
Ref: 18894200026
Ref: Tests<37>-Footnote-14200704
Ref: Tests<37>-Footnote-24200769
Ref: Tests<37>-Footnote-34200834
Ref: Tests<37>-Footnote-44200899
Node: Build<39>4200964
Ref: whatsnew/changelog id3474201068
Ref: 188a4201068
Ref: Build<39>-Footnote-14201943
Ref: Build<39>-Footnote-24202008
Ref: Build<39>-Footnote-34202073
Node: Windows<35>4202140
Ref: whatsnew/changelog id3484202244
Ref: 188b4202244
Ref: Windows<35>-Footnote-14203126
Ref: Windows<35>-Footnote-24203191
Ref: Windows<35>-Footnote-34203256
Ref: Windows<35>-Footnote-44203321
Ref: Windows<35>-Footnote-54203386
Ref: Windows<35>-Footnote-64203451
Node: macOS<30>4203516
Ref: whatsnew/changelog id3494203619
Ref: 188c4203619
Ref: macOS<30>-Footnote-14203749
Node: IDLE<26>4203814
Ref: whatsnew/changelog id3504203921
Ref: 188d4203921
Ref: IDLE<26>-Footnote-14204475
Ref: IDLE<26>-Footnote-24204540
Ref: IDLE<26>-Footnote-34204605
Ref: IDLE<26>-Footnote-44204670
Node: Tools/Demos<18>4204735
Ref: whatsnew/changelog id3514204842
Ref: 188e4204842
Ref: Tools/Demos<18>-Footnote-14205371
Ref: Tools/Demos<18>-Footnote-24205436
Node: C API<38>4205501
Ref: whatsnew/changelog id3524205591
Ref: 188f4205591
Ref: C API<38>-Footnote-14209136
Ref: C API<38>-Footnote-24209201
Ref: C API<38>-Footnote-34209266
Ref: C API<38>-Footnote-44209331
Ref: C API<38>-Footnote-54209396
Ref: C API<38>-Footnote-64209461
Ref: C API<38>-Footnote-74209526
Ref: C API<38>-Footnote-84209591
Ref: C API<38>-Footnote-94209656
Ref: C API<38>-Footnote-104209721
Ref: C API<38>-Footnote-114209787
Ref: C API<38>-Footnote-124209853
Ref: C API<38>-Footnote-134209919
Ref: C API<38>-Footnote-144209985
Ref: C API<38>-Footnote-154210051
Ref: C API<38>-Footnote-164210117
Ref: C API<38>-Footnote-174210183
Node: Python 3 9 0 alpha 44210249
Ref: whatsnew/changelog python-3-9-0-alpha-44210391
Ref: 18944210391
Node: Security<27>4210720
Ref: whatsnew/changelog id3534210819
Ref: 18954210819
Ref: Security<27>-Footnote-14211230
Ref: Security<27>-Footnote-24211295
Ref: Security<27>-Footnote-34211360
Node: Core and Builtins<41>4211425
Ref: whatsnew/changelog id3544211544
Ref: 18964211544
Ref: Core and Builtins<41>-Footnote-14214947
Ref: Core and Builtins<41>-Footnote-24215012
Ref: Core and Builtins<41>-Footnote-34215077
Ref: Core and Builtins<41>-Footnote-44215142
Ref: Core and Builtins<41>-Footnote-54215207
Ref: Core and Builtins<41>-Footnote-64215272
Ref: Core and Builtins<41>-Footnote-74215337
Ref: Core and Builtins<41>-Footnote-84215402
Ref: Core and Builtins<41>-Footnote-94215469
Ref: Core and Builtins<41>-Footnote-104215511
Ref: Core and Builtins<41>-Footnote-114215579
Ref: Core and Builtins<41>-Footnote-124215622
Ref: Core and Builtins<41>-Footnote-134215688
Ref: Core and Builtins<41>-Footnote-144215754
Ref: Core and Builtins<41>-Footnote-154215820
Ref: Core and Builtins<41>-Footnote-164215886
Ref: Core and Builtins<41>-Footnote-174215952
Ref: Core and Builtins<41>-Footnote-184216020
Ref: Core and Builtins<41>-Footnote-194216063
Ref: Core and Builtins<41>-Footnote-204216131
Ref: Core and Builtins<41>-Footnote-214216174
Ref: Core and Builtins<41>-Footnote-224216242
Ref: Core and Builtins<41>-Footnote-234216285
Ref: Core and Builtins<41>-Footnote-244216351
Ref: Core and Builtins<41>-Footnote-254216417
Ref: Core and Builtins<41>-Footnote-264216483
Ref: Core and Builtins<41>-Footnote-274216549
Ref: Core and Builtins<41>-Footnote-284216615
Ref: Core and Builtins<41>-Footnote-294216681
Node: Library<40>4216747
Ref: whatsnew/changelog id3554216871
Ref: 18994216871
Ref: Library<40>-Footnote-14223051
Ref: Library<40>-Footnote-24223116
Ref: Library<40>-Footnote-34223181
Ref: Library<40>-Footnote-44223246
Ref: Library<40>-Footnote-54223311
Ref: Library<40>-Footnote-64223376
Ref: Library<40>-Footnote-74223441
Ref: Library<40>-Footnote-84223506
Ref: Library<40>-Footnote-94223571
Ref: Library<40>-Footnote-104223636
Ref: Library<40>-Footnote-114223702
Ref: Library<40>-Footnote-124223768
Ref: Library<40>-Footnote-134223834
Ref: Library<40>-Footnote-144223900
Ref: Library<40>-Footnote-154223966
Ref: Library<40>-Footnote-164224032
Ref: Library<40>-Footnote-174224114
Ref: Library<40>-Footnote-184224180
Ref: Library<40>-Footnote-194224246
Ref: Library<40>-Footnote-204224312
Ref: Library<40>-Footnote-214224378
Ref: Library<40>-Footnote-224224444
Ref: Library<40>-Footnote-234224510
Ref: Library<40>-Footnote-244224576
Ref: Library<40>-Footnote-254224642
Ref: Library<40>-Footnote-264224708
Ref: Library<40>-Footnote-274224774
Ref: Library<40>-Footnote-284224817
Ref: Library<40>-Footnote-294224883
Ref: Library<40>-Footnote-304224949
Ref: Library<40>-Footnote-314225015
Ref: Library<40>-Footnote-324225081
Ref: Library<40>-Footnote-334225147
Ref: Library<40>-Footnote-344225213
Ref: Library<40>-Footnote-354225279
Ref: Library<40>-Footnote-364225345
Ref: Library<40>-Footnote-374225411
Ref: Library<40>-Footnote-384225477
Ref: Library<40>-Footnote-394225543
Node: Documentation<35>4225609
Ref: whatsnew/changelog id3564225721
Ref: 189b4225721
Ref: Documentation<35>-Footnote-14226752
Ref: Documentation<35>-Footnote-24226817
Ref: Documentation<35>-Footnote-34226882
Ref: Documentation<35>-Footnote-44226947
Ref: Documentation<35>-Footnote-54227012
Ref: Documentation<35>-Footnote-64227077
Ref: Documentation<35>-Footnote-74227142
Node: Tests<38>4227206
Ref: whatsnew/changelog id3574227316
Ref: 189c4227316
Ref: Tests<38>-Footnote-14227650
Ref: Tests<38>-Footnote-24227715
Node: Build<40>4227780
Ref: whatsnew/changelog id3584227884
Ref: 189d4227884
Ref: Build<40>-Footnote-14228014
Node: Windows<36>4228079
Ref: whatsnew/changelog id3594228182
Ref: 189e4228182
Ref: Windows<36>-Footnote-14228988
Ref: Windows<36>-Footnote-24229053
Ref: Windows<36>-Footnote-34229118
Ref: Windows<36>-Footnote-44229183
Ref: Windows<36>-Footnote-54229248
Ref: Windows<36>-Footnote-64229313
Node: IDLE<27>4229378
Ref: whatsnew/changelog id3604229481
Ref: 189f4229481
Ref: IDLE<27>-Footnote-14230028
Ref: IDLE<27>-Footnote-24230093
Ref: IDLE<27>-Footnote-34230158
Ref: IDLE<27>-Footnote-44230223
Ref: IDLE<27>-Footnote-54230288
Node: C API<39>4230353
Ref: whatsnew/changelog id3614230436
Ref: 18a04230436
Ref: C API<39>-Footnote-14233095
Ref: C API<39>-Footnote-24233160
Ref: C API<39>-Footnote-34233225
Ref: C API<39>-Footnote-44233290
Ref: C API<39>-Footnote-54233355
Ref: C API<39>-Footnote-64233420
Ref: C API<39>-Footnote-74233485
Ref: C API<39>-Footnote-84233550
Ref: C API<39>-Footnote-94233615
Ref: C API<39>-Footnote-104233680
Ref: C API<39>-Footnote-114233746
Ref: C API<39>-Footnote-124233812
Node: Python 3 9 0 alpha 34233878
Ref: whatsnew/changelog python-3-9-0-alpha-34234020
Ref: 18a54234020
Node: Core and Builtins<42>4234279
Ref: whatsnew/changelog id3624234377
Ref: 18a64234377
Ref: Core and Builtins<42>-Footnote-14238461
Ref: Core and Builtins<42>-Footnote-24238526
Ref: Core and Builtins<42>-Footnote-34238591
Ref: Core and Builtins<42>-Footnote-44238656
Ref: Core and Builtins<42>-Footnote-54238721
Ref: Core and Builtins<42>-Footnote-64238786
Ref: Core and Builtins<42>-Footnote-74238851
Ref: Core and Builtins<42>-Footnote-84238916
Ref: Core and Builtins<42>-Footnote-94238981
Ref: Core and Builtins<42>-Footnote-104239046
Ref: Core and Builtins<42>-Footnote-114239112
Ref: Core and Builtins<42>-Footnote-124239180
Ref: Core and Builtins<42>-Footnote-134239223
Ref: Core and Builtins<42>-Footnote-144239289
Ref: Core and Builtins<42>-Footnote-154239355
Ref: Core and Builtins<42>-Footnote-164239421
Ref: Core and Builtins<42>-Footnote-174239487
Ref: Core and Builtins<42>-Footnote-184239553
Ref: Core and Builtins<42>-Footnote-194239619
Ref: Core and Builtins<42>-Footnote-204239685
Ref: Core and Builtins<42>-Footnote-214239751
Ref: Core and Builtins<42>-Footnote-224239817
Ref: Core and Builtins<42>-Footnote-234239883
Ref: Core and Builtins<42>-Footnote-244239949
Node: Library<41>4240015
Ref: whatsnew/changelog id3634240139
Ref: 18aa4240139
Ref: Library<41>-Footnote-14249743
Ref: Library<41>-Footnote-24249808
Ref: Library<41>-Footnote-34249873
Ref: Library<41>-Footnote-44249938
Ref: Library<41>-Footnote-54250003
Ref: Library<41>-Footnote-64250068
Ref: Library<41>-Footnote-74250133
Ref: Library<41>-Footnote-84250198
Ref: Library<41>-Footnote-94250263
Ref: Library<41>-Footnote-104250328
Ref: Library<41>-Footnote-114250394
Ref: Library<41>-Footnote-124250460
Ref: Library<41>-Footnote-134250526
Ref: Library<41>-Footnote-144250592
Ref: Library<41>-Footnote-154250658
Ref: Library<41>-Footnote-164250724
Ref: Library<41>-Footnote-174250790
Ref: Library<41>-Footnote-184250856
Ref: Library<41>-Footnote-194250922
Ref: Library<41>-Footnote-204250988
Ref: Library<41>-Footnote-214251054
Ref: Library<41>-Footnote-224251120
Ref: Library<41>-Footnote-234251186
Ref: Library<41>-Footnote-244251252
Ref: Library<41>-Footnote-254251318
Ref: Library<41>-Footnote-264251384
Ref: Library<41>-Footnote-274251450
Ref: Library<41>-Footnote-284251516
Ref: Library<41>-Footnote-294251582
Ref: Library<41>-Footnote-304251648
Ref: Library<41>-Footnote-314251714
Ref: Library<41>-Footnote-324251780
Ref: Library<41>-Footnote-334251846
Ref: Library<41>-Footnote-344251912
Ref: Library<41>-Footnote-354251978
Ref: Library<41>-Footnote-364252044
Ref: Library<41>-Footnote-374252110
Ref: Library<41>-Footnote-384252176
Ref: Library<41>-Footnote-394252242
Ref: Library<41>-Footnote-404252308
Ref: Library<41>-Footnote-414252374
Ref: Library<41>-Footnote-424252440
Ref: Library<41>-Footnote-434252506
Ref: Library<41>-Footnote-444252572
Ref: Library<41>-Footnote-454252638
Ref: Library<41>-Footnote-464252704
Ref: Library<41>-Footnote-474252770
Ref: Library<41>-Footnote-484252836
Ref: Library<41>-Footnote-494252902
Ref: Library<41>-Footnote-504252968
Ref: Library<41>-Footnote-514253034
Ref: Library<41>-Footnote-524253100
Ref: Library<41>-Footnote-534253166
Node: Documentation<36>4253232
Ref: whatsnew/changelog id3644253344
Ref: 18ad4253344
Ref: Documentation<36>-Footnote-14253951
Ref: Documentation<36>-Footnote-24254016
Ref: Documentation<36>-Footnote-34254081
Node: Build<41>4254145
Ref: whatsnew/changelog id3654254254
Ref: 18af4254254
Ref: Build<41>-Footnote-14254780
Ref: Build<41>-Footnote-24254845
Ref: Build<41>-Footnote-34254910
Node: IDLE<28>4254975
Ref: whatsnew/changelog id3664255076
Ref: 18b04255076
Ref: IDLE<28>-Footnote-14255497
Ref: IDLE<28>-Footnote-24255562
Ref: IDLE<28>-Footnote-34255627
Node: C API<40>4255692
Ref: whatsnew/changelog id3674255775
Ref: 18b14255775
Ref: C API<40>-Footnote-14256540
Ref: C API<40>-Footnote-24256605
Node: Python 3 9 0 alpha 24256670
Ref: whatsnew/changelog python-3-9-0-alpha-24256812
Ref: 18b24256812
Node: Security<28>4257161
Ref: whatsnew/changelog id3684257260
Ref: 18b34257260
Ref: Security<28>-Footnote-14258133
Ref: Security<28>-Footnote-24258198
Ref: Security<28>-Footnote-34258263
Ref: Security<28>-Footnote-44258328
Node: Core and Builtins<43>4258393
Ref: whatsnew/changelog id3694258512
Ref: 18b44258512
Ref: Core and Builtins<43>-Footnote-14262181
Ref: Core and Builtins<43>-Footnote-24262246
Ref: Core and Builtins<43>-Footnote-34262311
Ref: Core and Builtins<43>-Footnote-44262376
Ref: Core and Builtins<43>-Footnote-54262441
Ref: Core and Builtins<43>-Footnote-64262506
Ref: Core and Builtins<43>-Footnote-74262571
Ref: Core and Builtins<43>-Footnote-84262636
Ref: Core and Builtins<43>-Footnote-94262701
Ref: Core and Builtins<43>-Footnote-104262766
Ref: Core and Builtins<43>-Footnote-114262832
Ref: Core and Builtins<43>-Footnote-124262898
Ref: Core and Builtins<43>-Footnote-134262964
Ref: Core and Builtins<43>-Footnote-144263030
Ref: Core and Builtins<43>-Footnote-154263096
Ref: Core and Builtins<43>-Footnote-164263162
Ref: Core and Builtins<43>-Footnote-174263228
Ref: Core and Builtins<43>-Footnote-184263294
Ref: Core and Builtins<43>-Footnote-194263360
Ref: Core and Builtins<43>-Footnote-204263426
Node: Library<42>4263492
Ref: whatsnew/changelog id3704263616
Ref: 18b54263616
Ref: Library<42>-Footnote-14271398
Ref: Library<42>-Footnote-24271463
Ref: Library<42>-Footnote-34271528
Ref: Library<42>-Footnote-44271593
Ref: Library<42>-Footnote-54271658
Ref: Library<42>-Footnote-64271723
Ref: Library<42>-Footnote-74271788
Ref: Library<42>-Footnote-84271853
Ref: Library<42>-Footnote-94271918
Ref: Library<42>-Footnote-104271983
Ref: Library<42>-Footnote-114272049
Ref: Library<42>-Footnote-124272115
Ref: Library<42>-Footnote-134272181
Ref: Library<42>-Footnote-144272247
Ref: Library<42>-Footnote-154272313
Ref: Library<42>-Footnote-164272379
Ref: Library<42>-Footnote-174272445
Ref: Library<42>-Footnote-184272511
Ref: Library<42>-Footnote-194272577
Ref: Library<42>-Footnote-204272643
Ref: Library<42>-Footnote-214272709
Ref: Library<42>-Footnote-224272775
Ref: Library<42>-Footnote-234272841
Ref: Library<42>-Footnote-244272907
Ref: Library<42>-Footnote-254272973
Ref: Library<42>-Footnote-264273039
Ref: Library<42>-Footnote-274273105
Ref: Library<42>-Footnote-284273171
Ref: Library<42>-Footnote-294273237
Ref: Library<42>-Footnote-304273303
Ref: Library<42>-Footnote-314273369
Ref: Library<42>-Footnote-324273435
Ref: Library<42>-Footnote-334273501
Ref: Library<42>-Footnote-344273567
Ref: Library<42>-Footnote-354273633
Ref: Library<42>-Footnote-364273699
Ref: Library<42>-Footnote-374273765
Ref: Library<42>-Footnote-384273831
Ref: Library<42>-Footnote-394273897
Ref: Library<42>-Footnote-404273963
Node: Documentation<37>4274029
Ref: whatsnew/changelog id3714274141
Ref: 18b64274141
Ref: Documentation<37>-Footnote-14274726
Ref: Documentation<37>-Footnote-24274791
Ref: Documentation<37>-Footnote-34274856
Node: Tests<39>4274921
Ref: whatsnew/changelog id3724275031
Ref: 18b74275031
Ref: Tests<39>-Footnote-14277597
Ref: Tests<39>-Footnote-24277662
Ref: Tests<39>-Footnote-34277727
Ref: Tests<39>-Footnote-44277792
Ref: Tests<39>-Footnote-54277857
Ref: Tests<39>-Footnote-64277922
Ref: Tests<39>-Footnote-74277987
Ref: Tests<39>-Footnote-84278052
Ref: Tests<39>-Footnote-94278117
Ref: Tests<39>-Footnote-104278182
Ref: Tests<39>-Footnote-114278248
Ref: Tests<39>-Footnote-124278314
Ref: Tests<39>-Footnote-134278380
Node: Build<42>4278446
Ref: whatsnew/changelog id3734278550
Ref: 18bc4278550
Ref: Build<42>-Footnote-14278948
Ref: Build<42>-Footnote-24279013
Node: Windows<37>4279078
Ref: whatsnew/changelog id3744279182
Ref: 18bd4279182
Ref: Windows<37>-Footnote-14279417
Ref: Windows<37>-Footnote-24279482
Node: macOS<31>4279547
Ref: whatsnew/changelog id3754279650
Ref: 18be4279650
Ref: macOS<31>-Footnote-14279958
Node: IDLE<29>4280023
Ref: whatsnew/changelog id3764280124
Ref: 18bf4280124
Ref: IDLE<29>-Footnote-14280715
Ref: IDLE<29>-Footnote-24280780
Ref: IDLE<29>-Footnote-34280845
Ref: IDLE<29>-Footnote-44280910
Node: C API<41>4280975
Ref: whatsnew/changelog id3774281058
Ref: 18c04281058
Ref: C API<41>-Footnote-14281592
Ref: C API<41>-Footnote-24281657
Ref: C API<41>-Footnote-34281722
Node: Python 3 9 0 alpha 14281787
Ref: whatsnew/changelog python-3-9-0-alpha-14281928
Ref: 18c14281928
Node: Security<29>4282309
Ref: whatsnew/changelog id3784282408
Ref: 18c24282408
Ref: Security<29>-Footnote-14284716
Ref: Security<29>-Footnote-24284781
Ref: Security<29>-Footnote-34284846
Ref: Security<29>-Footnote-44284911
Ref: Security<29>-Footnote-54284976
Ref: Security<29>-Footnote-64285041
Ref: Security<29>-Footnote-74285106
Ref: Security<29>-Footnote-84285176
Ref: Security<29>-Footnote-94285241
Ref: Security<29>-Footnote-104285306
Ref: Security<29>-Footnote-114285372
Ref: Security<29>-Footnote-124285438
Ref: Security<29>-Footnote-134285504
Ref: Security<29>-Footnote-144285570
Ref: Security<29>-Footnote-154285636
Node: Core and Builtins<44>4285702
Ref: whatsnew/changelog id3794285821
Ref: 18c54285821
Ref: Core and Builtins<44>-Footnote-14301322
Ref: Core and Builtins<44>-Footnote-24301387
Ref: Core and Builtins<44>-Footnote-34301452
Ref: Core and Builtins<44>-Footnote-44301517
Ref: Core and Builtins<44>-Footnote-54301582
Ref: Core and Builtins<44>-Footnote-64301647
Ref: Core and Builtins<44>-Footnote-74301712
Ref: Core and Builtins<44>-Footnote-84301777
Ref: Core and Builtins<44>-Footnote-94301842
Ref: Core and Builtins<44>-Footnote-104301907
Ref: Core and Builtins<44>-Footnote-114301973
Ref: Core and Builtins<44>-Footnote-124302039
Ref: Core and Builtins<44>-Footnote-134302105
Ref: Core and Builtins<44>-Footnote-144302171
Ref: Core and Builtins<44>-Footnote-154302237
Ref: Core and Builtins<44>-Footnote-164302303
Ref: Core and Builtins<44>-Footnote-174302369
Ref: Core and Builtins<44>-Footnote-184302435
Ref: Core and Builtins<44>-Footnote-194302501
Ref: Core and Builtins<44>-Footnote-204302567
Ref: Core and Builtins<44>-Footnote-214302610
Ref: Core and Builtins<44>-Footnote-224302676
Ref: Core and Builtins<44>-Footnote-234302742
Ref: Core and Builtins<44>-Footnote-244302808
Ref: Core and Builtins<44>-Footnote-254302874
Ref: Core and Builtins<44>-Footnote-264302940
Ref: Core and Builtins<44>-Footnote-274303006
Ref: Core and Builtins<44>-Footnote-284303072
Ref: Core and Builtins<44>-Footnote-294303138
Ref: Core and Builtins<44>-Footnote-304303204
Ref: Core and Builtins<44>-Footnote-314303270
Ref: Core and Builtins<44>-Footnote-324303336
Ref: Core and Builtins<44>-Footnote-334303402
Ref: Core and Builtins<44>-Footnote-344303468
Ref: Core and Builtins<44>-Footnote-354303534
Ref: Core and Builtins<44>-Footnote-364303600
Ref: Core and Builtins<44>-Footnote-374303666
Ref: Core and Builtins<44>-Footnote-384303732
Ref: Core and Builtins<44>-Footnote-394303798
Ref: Core and Builtins<44>-Footnote-404303864
Ref: Core and Builtins<44>-Footnote-414303929
Ref: Core and Builtins<44>-Footnote-424303995
Ref: Core and Builtins<44>-Footnote-434304061
Ref: Core and Builtins<44>-Footnote-444304127
Ref: Core and Builtins<44>-Footnote-454304193
Ref: Core and Builtins<44>-Footnote-464304259
Ref: Core and Builtins<44>-Footnote-474304325
Ref: Core and Builtins<44>-Footnote-484304391
Ref: Core and Builtins<44>-Footnote-494304457
Ref: Core and Builtins<44>-Footnote-504304523
Ref: Core and Builtins<44>-Footnote-514304589
Ref: Core and Builtins<44>-Footnote-524304655
Ref: Core and Builtins<44>-Footnote-534304721
Ref: Core and Builtins<44>-Footnote-544304764
Ref: Core and Builtins<44>-Footnote-554304830
Ref: Core and Builtins<44>-Footnote-564304896
Ref: Core and Builtins<44>-Footnote-574304962
Ref: Core and Builtins<44>-Footnote-584305028
Ref: Core and Builtins<44>-Footnote-594305094
Ref: Core and Builtins<44>-Footnote-604305160
Ref: Core and Builtins<44>-Footnote-614305226
Ref: Core and Builtins<44>-Footnote-624305292
Ref: Core and Builtins<44>-Footnote-634305358
Ref: Core and Builtins<44>-Footnote-644305424
Ref: Core and Builtins<44>-Footnote-654305490
Ref: Core and Builtins<44>-Footnote-664305556
Ref: Core and Builtins<44>-Footnote-674305622
Ref: Core and Builtins<44>-Footnote-684305688
Ref: Core and Builtins<44>-Footnote-694305754
Ref: Core and Builtins<44>-Footnote-704305820
Ref: Core and Builtins<44>-Footnote-714305886
Ref: Core and Builtins<44>-Footnote-724305952
Ref: Core and Builtins<44>-Footnote-734306018
Ref: Core and Builtins<44>-Footnote-744306084
Ref: Core and Builtins<44>-Footnote-754306150
Ref: Core and Builtins<44>-Footnote-764306216
Ref: Core and Builtins<44>-Footnote-774306282
Ref: Core and Builtins<44>-Footnote-784306348
Ref: Core and Builtins<44>-Footnote-794306414
Ref: Core and Builtins<44>-Footnote-804306480
Ref: Core and Builtins<44>-Footnote-814306546
Ref: Core and Builtins<44>-Footnote-824306612
Ref: Core and Builtins<44>-Footnote-834306678
Ref: Core and Builtins<44>-Footnote-844306744
Ref: Core and Builtins<44>-Footnote-854306810
Ref: Core and Builtins<44>-Footnote-864306876
Ref: Core and Builtins<44>-Footnote-874306942
Ref: Core and Builtins<44>-Footnote-884307008
Ref: Core and Builtins<44>-Footnote-894307074
Ref: Core and Builtins<44>-Footnote-904307140
Ref: Core and Builtins<44>-Footnote-914307206
Ref: Core and Builtins<44>-Footnote-924307272
Ref: Core and Builtins<44>-Footnote-934307338
Ref: Core and Builtins<44>-Footnote-944307404
Node: Library<43>4307470
Ref: whatsnew/changelog id3804307594
Ref: 18ca4307594
Ref: Library<43>-Footnote-14346957
Ref: Library<43>-Footnote-24347022
Ref: Library<43>-Footnote-34347087
Ref: Library<43>-Footnote-44347152
Ref: Library<43>-Footnote-54347217
Ref: Library<43>-Footnote-64347282
Ref: Library<43>-Footnote-74347347
Ref: Library<43>-Footnote-84347412
Ref: Library<43>-Footnote-94347477
Ref: Library<43>-Footnote-104347542
Ref: Library<43>-Footnote-114347608
Ref: Library<43>-Footnote-124347674
Ref: Library<43>-Footnote-134347740
Ref: Library<43>-Footnote-144347806
Ref: Library<43>-Footnote-154347872
Ref: Library<43>-Footnote-164347938
Ref: Library<43>-Footnote-174348004
Ref: Library<43>-Footnote-184348070
Ref: Library<43>-Footnote-194348136
Ref: Library<43>-Footnote-204348202
Ref: Library<43>-Footnote-214348268
Ref: Library<43>-Footnote-224348334
Ref: Library<43>-Footnote-234348400
Ref: Library<43>-Footnote-244348466
Ref: Library<43>-Footnote-254348532
Ref: Library<43>-Footnote-264348598
Ref: Library<43>-Footnote-274348664
Ref: Library<43>-Footnote-284348730
Ref: Library<43>-Footnote-294348796
Ref: Library<43>-Footnote-304348862
Ref: Library<43>-Footnote-314348928
Ref: Library<43>-Footnote-324348994
Ref: Library<43>-Footnote-334349060
Ref: Library<43>-Footnote-344349126
Ref: Library<43>-Footnote-354349192
Ref: Library<43>-Footnote-364349258
Ref: Library<43>-Footnote-374349324
Ref: Library<43>-Footnote-384349390
Ref: Library<43>-Footnote-394349456
Ref: Library<43>-Footnote-404349522
Ref: Library<43>-Footnote-414349588
Ref: Library<43>-Footnote-424349654
Ref: Library<43>-Footnote-434349720
Ref: Library<43>-Footnote-444349786
Ref: Library<43>-Footnote-454349852
Ref: Library<43>-Footnote-464349918
Ref: Library<43>-Footnote-474349984
Ref: Library<43>-Footnote-484350050
Ref: Library<43>-Footnote-494350116
Ref: Library<43>-Footnote-504350182
Ref: Library<43>-Footnote-514350248
Ref: Library<43>-Footnote-524350314
Ref: Library<43>-Footnote-534350380
Ref: Library<43>-Footnote-544350446
Ref: Library<43>-Footnote-554350512
Ref: Library<43>-Footnote-564350578
Ref: Library<43>-Footnote-574350644
Ref: Library<43>-Footnote-584350710
Ref: Library<43>-Footnote-594350776
Ref: Library<43>-Footnote-604350842
Ref: Library<43>-Footnote-614350908
Ref: Library<43>-Footnote-624350974
Ref: Library<43>-Footnote-634351040
Ref: Library<43>-Footnote-644351105
Ref: Library<43>-Footnote-654351171
Ref: Library<43>-Footnote-664351237
Ref: Library<43>-Footnote-674351303
Ref: Library<43>-Footnote-684351369
Ref: Library<43>-Footnote-694351435
Ref: Library<43>-Footnote-704351501
Ref: Library<43>-Footnote-714351567
Ref: Library<43>-Footnote-724351633
Ref: Library<43>-Footnote-734351699
Ref: Library<43>-Footnote-744351765
Ref: Library<43>-Footnote-754351831
Ref: Library<43>-Footnote-764351897
Ref: Library<43>-Footnote-774352005
Ref: Library<43>-Footnote-784352071
Ref: Library<43>-Footnote-794352137
Ref: Library<43>-Footnote-804352203
Ref: Library<43>-Footnote-814352269
Ref: Library<43>-Footnote-824352335
Ref: Library<43>-Footnote-834352401
Ref: Library<43>-Footnote-844352467
Ref: Library<43>-Footnote-854352533
Ref: Library<43>-Footnote-864352599
Ref: Library<43>-Footnote-874352665
Ref: Library<43>-Footnote-884352731
Ref: Library<43>-Footnote-894352797
Ref: Library<43>-Footnote-904352863
Ref: Library<43>-Footnote-914352929
Ref: Library<43>-Footnote-924352995
Ref: Library<43>-Footnote-934353061
Ref: Library<43>-Footnote-944353127
Ref: Library<43>-Footnote-954353193
Ref: Library<43>-Footnote-964353259
Ref: Library<43>-Footnote-974353325
Ref: Library<43>-Footnote-984353391
Ref: Library<43>-Footnote-994353457
Ref: Library<43>-Footnote-1004353523
Ref: Library<43>-Footnote-1014353590
Ref: Library<43>-Footnote-1024353657
Ref: Library<43>-Footnote-1034353724
Ref: Library<43>-Footnote-1044353791
Ref: Library<43>-Footnote-1054353858
Ref: Library<43>-Footnote-1064353925
Ref: Library<43>-Footnote-1074353992
Ref: Library<43>-Footnote-1084354058
Ref: Library<43>-Footnote-1094354125
Ref: Library<43>-Footnote-1104354192
Ref: Library<43>-Footnote-1114354259
Ref: Library<43>-Footnote-1124354326
Ref: Library<43>-Footnote-1134354393
Ref: Library<43>-Footnote-1144354460
Ref: Library<43>-Footnote-1154354527
Ref: Library<43>-Footnote-1164354594
Ref: Library<43>-Footnote-1174354661
Ref: Library<43>-Footnote-1184354728
Ref: Library<43>-Footnote-1194354795
Ref: Library<43>-Footnote-1204354862
Ref: Library<43>-Footnote-1214354929
Ref: Library<43>-Footnote-1224354996
Ref: Library<43>-Footnote-1234355063
Ref: Library<43>-Footnote-1244355130
Ref: Library<43>-Footnote-1254355197
Ref: Library<43>-Footnote-1264355264
Ref: Library<43>-Footnote-1274355331
Ref: Library<43>-Footnote-1284355398
Ref: Library<43>-Footnote-1294355465
Ref: Library<43>-Footnote-1304355532
Ref: Library<43>-Footnote-1314355599
Ref: Library<43>-Footnote-1324355666
Ref: Library<43>-Footnote-1334355733
Ref: Library<43>-Footnote-1344355800
Ref: Library<43>-Footnote-1354355867
Ref: Library<43>-Footnote-1364355934
Ref: Library<43>-Footnote-1374356011
Ref: Library<43>-Footnote-1384356078
Ref: Library<43>-Footnote-1394356145
Ref: Library<43>-Footnote-1404356212
Ref: Library<43>-Footnote-1414356279
Ref: Library<43>-Footnote-1424356346
Ref: Library<43>-Footnote-1434356413
Ref: Library<43>-Footnote-1444356480
Ref: Library<43>-Footnote-1454356547
Ref: Library<43>-Footnote-1464356614
Ref: Library<43>-Footnote-1474356681
Ref: Library<43>-Footnote-1484356748
Ref: Library<43>-Footnote-1494356815
Ref: Library<43>-Footnote-1504356882
Ref: Library<43>-Footnote-1514356949
Ref: Library<43>-Footnote-1524357016
Ref: Library<43>-Footnote-1534357083
Ref: Library<43>-Footnote-1544357150
Ref: Library<43>-Footnote-1554357217
Ref: Library<43>-Footnote-1564357284
Ref: Library<43>-Footnote-1574357351
Ref: Library<43>-Footnote-1584357418
Ref: Library<43>-Footnote-1594357485
Ref: Library<43>-Footnote-1604357552
Ref: Library<43>-Footnote-1614357619
Ref: Library<43>-Footnote-1624357686
Ref: Library<43>-Footnote-1634357753
Ref: Library<43>-Footnote-1644357820
Ref: Library<43>-Footnote-1654357887
Ref: Library<43>-Footnote-1664357954
Ref: Library<43>-Footnote-1674358021
Ref: Library<43>-Footnote-1684358088
Ref: Library<43>-Footnote-1694358155
Ref: Library<43>-Footnote-1704358222
Ref: Library<43>-Footnote-1714358289
Ref: Library<43>-Footnote-1724358356
Ref: Library<43>-Footnote-1734358400
Ref: Library<43>-Footnote-1744358467
Ref: Library<43>-Footnote-1754358534
Ref: Library<43>-Footnote-1764358601
Ref: Library<43>-Footnote-1774358668
Ref: Library<43>-Footnote-1784358735
Ref: Library<43>-Footnote-1794358802
Ref: Library<43>-Footnote-1804358869
Ref: Library<43>-Footnote-1814358936
Ref: Library<43>-Footnote-1824359003
Ref: Library<43>-Footnote-1834359070
Ref: Library<43>-Footnote-1844359137
Ref: Library<43>-Footnote-1854359204
Ref: Library<43>-Footnote-1864359271
Ref: Library<43>-Footnote-1874359338
Ref: Library<43>-Footnote-1884359405
Ref: Library<43>-Footnote-1894359472
Ref: Library<43>-Footnote-1904359539
Ref: Library<43>-Footnote-1914359606
Ref: Library<43>-Footnote-1924359673
Ref: Library<43>-Footnote-1934359740
Ref: Library<43>-Footnote-1944359807
Ref: Library<43>-Footnote-1954359874
Ref: Library<43>-Footnote-1964359941
Ref: Library<43>-Footnote-1974360008
Ref: Library<43>-Footnote-1984360075
Ref: Library<43>-Footnote-1994360142
Ref: Library<43>-Footnote-2004360209
Ref: Library<43>-Footnote-2014360276
Ref: Library<43>-Footnote-2024360343
Ref: Library<43>-Footnote-2034360410
Ref: Library<43>-Footnote-2044360477
Ref: Library<43>-Footnote-2054360544
Ref: Library<43>-Footnote-2064360611
Ref: Library<43>-Footnote-2074360678
Ref: Library<43>-Footnote-2084360745
Ref: Library<43>-Footnote-2094360812
Ref: Library<43>-Footnote-2104360879
Ref: Library<43>-Footnote-2114360946
Ref: Library<43>-Footnote-2124361013
Ref: Library<43>-Footnote-2134361080
Ref: Library<43>-Footnote-2144361147
Ref: Library<43>-Footnote-2154361214
Ref: Library<43>-Footnote-2164361281
Ref: Library<43>-Footnote-2174361348
Ref: Library<43>-Footnote-2184361415
Ref: Library<43>-Footnote-2194361482
Ref: Library<43>-Footnote-2204361549
Ref: Library<43>-Footnote-2214361616
Ref: Library<43>-Footnote-2224361683
Ref: Library<43>-Footnote-2234361750
Ref: Library<43>-Footnote-2244361817
Ref: Library<43>-Footnote-2254361884
Ref: Library<43>-Footnote-2264361951
Ref: Library<43>-Footnote-2274362018
Ref: Library<43>-Footnote-2284362085
Ref: Library<43>-Footnote-2294362152
Ref: Library<43>-Footnote-2304362219
Ref: Library<43>-Footnote-2314362286
Ref: Library<43>-Footnote-2324362353
Ref: Library<43>-Footnote-2334362420
Ref: Library<43>-Footnote-2344362487
Ref: Library<43>-Footnote-2354362554
Ref: Library<43>-Footnote-2364362621
Ref: Library<43>-Footnote-2374362688
Ref: Library<43>-Footnote-2384362755
Ref: Library<43>-Footnote-2394362822
Ref: Library<43>-Footnote-2404362888
Ref: Library<43>-Footnote-2414362955
Ref: Library<43>-Footnote-2424363022
Ref: Library<43>-Footnote-2434363089
Ref: Library<43>-Footnote-2444363156
Ref: Library<43>-Footnote-2454363223
Ref: Library<43>-Footnote-2464363290
Ref: Library<43>-Footnote-2474363357
Ref: Library<43>-Footnote-2484363424
Ref: Library<43>-Footnote-2494363491
Ref: Library<43>-Footnote-2504363558
Ref: Library<43>-Footnote-2514363625
Ref: Library<43>-Footnote-2524363692
Ref: Library<43>-Footnote-2534363759
Node: Documentation<38>4363825
Ref: whatsnew/changelog id3814363937
Ref: 18d74363937
Ref: Documentation<38>-Footnote-14368389
Ref: Documentation<38>-Footnote-24368454
Ref: Documentation<38>-Footnote-34368519
Ref: Documentation<38>-Footnote-44368584
Ref: Documentation<38>-Footnote-54368649
Ref: Documentation<38>-Footnote-64368714
Ref: Documentation<38>-Footnote-74368779
Ref: Documentation<38>-Footnote-84368844
Ref: Documentation<38>-Footnote-94368909
Ref: Documentation<38>-Footnote-104368974
Ref: Documentation<38>-Footnote-114369040
Ref: Documentation<38>-Footnote-124369106
Ref: Documentation<38>-Footnote-134369172
Ref: Documentation<38>-Footnote-144369238
Ref: Documentation<38>-Footnote-154369304
Ref: Documentation<38>-Footnote-164369370
Ref: Documentation<38>-Footnote-174369436
Ref: Documentation<38>-Footnote-184369502
Ref: Documentation<38>-Footnote-194369568
Ref: Documentation<38>-Footnote-204369634
Ref: Documentation<38>-Footnote-214369700
Ref: Documentation<38>-Footnote-224369766
Ref: Documentation<38>-Footnote-234369832
Ref: Documentation<38>-Footnote-244369898
Ref: Documentation<38>-Footnote-254369964
Ref: Documentation<38>-Footnote-264370030
Ref: Documentation<38>-Footnote-274370096
Ref: Documentation<38>-Footnote-284370162
Ref: Documentation<38>-Footnote-294370228
Ref: Documentation<38>-Footnote-304370294
Ref: Documentation<38>-Footnote-314370360
Ref: Documentation<38>-Footnote-324370426
Ref: Documentation<38>-Footnote-334370492
Ref: Documentation<38>-Footnote-344370558
Ref: Documentation<38>-Footnote-354370624
Node: Tests<40>4370690
Ref: whatsnew/changelog id3824370800
Ref: 18d94370800
Ref: Tests<40>-Footnote-14378881
Ref: Tests<40>-Footnote-24378946
Ref: Tests<40>-Footnote-34379011
Ref: Tests<40>-Footnote-44379076
Ref: Tests<40>-Footnote-54379141
Ref: Tests<40>-Footnote-64379206
Ref: Tests<40>-Footnote-74379271
Ref: Tests<40>-Footnote-84379336
Ref: Tests<40>-Footnote-94379401
Ref: Tests<40>-Footnote-104379466
Ref: Tests<40>-Footnote-114379532
Ref: Tests<40>-Footnote-124379598
Ref: Tests<40>-Footnote-134379664
Ref: Tests<40>-Footnote-144379730
Ref: Tests<40>-Footnote-154379796
Ref: Tests<40>-Footnote-164379862
Ref: Tests<40>-Footnote-174379928
Ref: Tests<40>-Footnote-184379994
Ref: Tests<40>-Footnote-194380060
Ref: Tests<40>-Footnote-204380126
Ref: Tests<40>-Footnote-214380192
Ref: Tests<40>-Footnote-224380258
Ref: Tests<40>-Footnote-234380324
Ref: Tests<40>-Footnote-244380390
Ref: Tests<40>-Footnote-254380456
Ref: Tests<40>-Footnote-264380522
Ref: Tests<40>-Footnote-274380588
Ref: Tests<40>-Footnote-284380654
Ref: Tests<40>-Footnote-294380720
Ref: Tests<40>-Footnote-304380786
Ref: Tests<40>-Footnote-314380852
Ref: Tests<40>-Footnote-324380918
Ref: Tests<40>-Footnote-334380984
Ref: Tests<40>-Footnote-344381050
Ref: Tests<40>-Footnote-354381116
Ref: Tests<40>-Footnote-364381182
Ref: Tests<40>-Footnote-374381248
Ref: Tests<40>-Footnote-384381314
Ref: Tests<40>-Footnote-394381380
Ref: Tests<40>-Footnote-404381446
Ref: Tests<40>-Footnote-414381512
Ref: Tests<40>-Footnote-424381578
Ref: Tests<40>-Footnote-434381644
Ref: Tests<40>-Footnote-444381710
Ref: Tests<40>-Footnote-454381776
Ref: Tests<40>-Footnote-464381842
Ref: Tests<40>-Footnote-474381908
Ref: Tests<40>-Footnote-484381974
Node: Build<43>4382040
Ref: whatsnew/changelog id3834382144
Ref: 18df4382144
Ref: Build<43>-Footnote-14385944
Ref: Build<43>-Footnote-24386009
Ref: Build<43>-Footnote-34386074
Ref: Build<43>-Footnote-44386139
Ref: Build<43>-Footnote-54386204
Ref: Build<43>-Footnote-64386269
Ref: Build<43>-Footnote-74386334
Ref: Build<43>-Footnote-84386399
Ref: Build<43>-Footnote-94386464
Ref: Build<43>-Footnote-104386529
Ref: Build<43>-Footnote-114386595
Ref: Build<43>-Footnote-124386661
Ref: Build<43>-Footnote-134386727
Ref: Build<43>-Footnote-144386793
Ref: Build<43>-Footnote-154386859
Ref: Build<43>-Footnote-164386925
Node: Windows<38>4386991
Ref: whatsnew/changelog id3844387095
Ref: 18e14387095
Ref: Windows<38>-Footnote-14391997
Ref: Windows<38>-Footnote-24392062
Ref: Windows<38>-Footnote-34392127
Ref: Windows<38>-Footnote-44392192
Ref: Windows<38>-Footnote-54392257
Ref: Windows<38>-Footnote-64392322
Ref: Windows<38>-Footnote-74392387
Ref: Windows<38>-Footnote-84392452
Ref: Windows<38>-Footnote-94392517
Ref: Windows<38>-Footnote-104392582
Ref: Windows<38>-Footnote-114392648
Ref: Windows<38>-Footnote-124392714
Ref: Windows<38>-Footnote-134392780
Ref: Windows<38>-Footnote-144392846
Ref: Windows<38>-Footnote-154392912
Ref: Windows<38>-Footnote-164392978
Ref: Windows<38>-Footnote-174393044
Ref: Windows<38>-Footnote-184393110
Ref: Windows<38>-Footnote-194393176
Ref: Windows<38>-Footnote-204393242
Ref: Windows<38>-Footnote-214393308
Ref: Windows<38>-Footnote-224393374
Ref: Windows<38>-Footnote-234393440
Ref: Windows<38>-Footnote-244393505
Ref: Windows<38>-Footnote-254393570
Ref: Windows<38>-Footnote-264393636
Ref: Windows<38>-Footnote-274393702
Ref: Windows<38>-Footnote-284393768
Ref: Windows<38>-Footnote-294393834
Ref: Windows<38>-Footnote-304393900
Ref: Windows<38>-Footnote-314393966
Ref: Windows<38>-Footnote-324394032
Ref: Windows<38>-Footnote-334394098
Ref: Windows<38>-Footnote-344394164
Ref: Windows<38>-Footnote-354394230
Ref: Windows<38>-Footnote-364394296
Ref: Windows<38>-Footnote-374394362
Ref: Windows<38>-Footnote-384394428
Ref: Windows<38>-Footnote-394394494
Ref: Windows<38>-Footnote-404394560
Ref: Windows<38>-Footnote-414394626
Ref: Windows<38>-Footnote-424394692
Node: macOS<32>4394758
Ref: whatsnew/changelog id3854394861
Ref: 18e44394861
Ref: macOS<32>-Footnote-14395694
Ref: macOS<32>-Footnote-24395759
Ref: macOS<32>-Footnote-34395824
Ref: macOS<32>-Footnote-44395889
Ref: macOS<32>-Footnote-54395954
Ref: macOS<32>-Footnote-64396019
Node: IDLE<30>4396084
Ref: whatsnew/changelog id3864396191
Ref: 18e54396191
Ref: IDLE<30>-Footnote-14400893
Ref: IDLE<30>-Footnote-24400958
Ref: IDLE<30>-Footnote-34401022
Ref: IDLE<30>-Footnote-44401087
Ref: IDLE<30>-Footnote-54401152
Ref: IDLE<30>-Footnote-64401217
Ref: IDLE<30>-Footnote-74401282
Ref: IDLE<30>-Footnote-84401347
Ref: IDLE<30>-Footnote-94401412
Ref: IDLE<30>-Footnote-104401477
Ref: IDLE<30>-Footnote-114401543
Ref: IDLE<30>-Footnote-124401609
Ref: IDLE<30>-Footnote-134401675
Ref: IDLE<30>-Footnote-144401741
Ref: IDLE<30>-Footnote-154401807
Ref: IDLE<30>-Footnote-164401873
Ref: IDLE<30>-Footnote-174401939
Ref: IDLE<30>-Footnote-184402005
Ref: IDLE<30>-Footnote-194402071
Ref: IDLE<30>-Footnote-204402137
Ref: IDLE<30>-Footnote-214402203
Ref: IDLE<30>-Footnote-224402269
Ref: IDLE<30>-Footnote-234402335
Ref: IDLE<30>-Footnote-244402401
Ref: IDLE<30>-Footnote-254402467
Ref: IDLE<30>-Footnote-264402533
Ref: IDLE<30>-Footnote-274402599
Ref: IDLE<30>-Footnote-284402665
Ref: IDLE<30>-Footnote-294402731
Ref: IDLE<30>-Footnote-304402796
Node: Tools/Demos<19>4402862
Ref: whatsnew/changelog id3874402969
Ref: 18e64402969
Ref: Tools/Demos<19>-Footnote-14403964
Ref: Tools/Demos<19>-Footnote-24404029
Ref: Tools/Demos<19>-Footnote-34404094
Ref: Tools/Demos<19>-Footnote-44404159
Ref: Tools/Demos<19>-Footnote-54404224
Ref: Tools/Demos<19>-Footnote-64404289
Ref: Tools/Demos<19>-Footnote-74404354
Ref: Tools/Demos<19>-Footnote-84404419
Node: C API<42>4404484
Ref: whatsnew/changelog id3884404574
Ref: 18e84404574
Ref: C API<42>-Footnote-14409967
Ref: C API<42>-Footnote-24410032
Ref: C API<42>-Footnote-34410097
Ref: C API<42>-Footnote-44410162
Ref: C API<42>-Footnote-54410227
Ref: C API<42>-Footnote-64410292
Ref: C API<42>-Footnote-74410357
Ref: C API<42>-Footnote-84410422
Ref: C API<42>-Footnote-94410487
Ref: C API<42>-Footnote-104410552
Ref: C API<42>-Footnote-114410618
Ref: C API<42>-Footnote-124410684
Ref: C API<42>-Footnote-134410750
Ref: C API<42>-Footnote-144410816
Ref: C API<42>-Footnote-154410859
Ref: C API<42>-Footnote-164410925
Ref: C API<42>-Footnote-174410991
Ref: C API<42>-Footnote-184411057
Ref: C API<42>-Footnote-194411123
Ref: C API<42>-Footnote-204411189
Ref: C API<42>-Footnote-214411255
Ref: C API<42>-Footnote-224411321
Ref: C API<42>-Footnote-234411387
Ref: C API<42>-Footnote-244411453
Ref: C API<42>-Footnote-254411519
Ref: C API<42>-Footnote-264411585
Ref: C API<42>-Footnote-274411651
Ref: C API<42>-Footnote-284411717
Ref: C API<42>-Footnote-294411783
Ref: C API<42>-Footnote-304411849
Ref: C API<42>-Footnote-314411915
Ref: C API<42>-Footnote-324411981
Ref: C API<42>-Footnote-334412047
Ref: C API<42>-Footnote-344412113
Node: Python 3 8 0 beta 14412179
Ref: whatsnew/changelog python-3-8-0-beta-14412320
Ref: 18ec4412320
Node: Security<30>4412699
Ref: whatsnew/changelog id3894412797
Ref: 18ed4412797
Ref: Security<30>-Footnote-14413390
Ref: Security<30>-Footnote-24413455
Ref: Security<30>-Footnote-34413524
Ref: Security<30>-Footnote-44413589
Node: Core and Builtins<45>4413654
Ref: whatsnew/changelog id3904413772
Ref: 18ee4413772
Ref: Core and Builtins<45>-Footnote-14421812
Ref: Core and Builtins<45>-Footnote-24421877
Ref: Core and Builtins<45>-Footnote-34421942
Ref: Core and Builtins<45>-Footnote-44422007
Ref: Core and Builtins<45>-Footnote-54422072
Ref: Core and Builtins<45>-Footnote-64422137
Ref: Core and Builtins<45>-Footnote-74422202
Ref: Core and Builtins<45>-Footnote-84422267
Ref: Core and Builtins<45>-Footnote-94422332
Ref: Core and Builtins<45>-Footnote-104422397
Ref: Core and Builtins<45>-Footnote-114422463
Ref: Core and Builtins<45>-Footnote-124422529
Ref: Core and Builtins<45>-Footnote-134422595
Ref: Core and Builtins<45>-Footnote-144422661
Ref: Core and Builtins<45>-Footnote-154422727
Ref: Core and Builtins<45>-Footnote-164422793
Ref: Core and Builtins<45>-Footnote-174422859
Ref: Core and Builtins<45>-Footnote-184422925
Ref: Core and Builtins<45>-Footnote-194422990
Ref: Core and Builtins<45>-Footnote-204423056
Ref: Core and Builtins<45>-Footnote-214423122
Ref: Core and Builtins<45>-Footnote-224423188
Ref: Core and Builtins<45>-Footnote-234423253
Ref: Core and Builtins<45>-Footnote-244423319
Ref: Core and Builtins<45>-Footnote-254423385
Ref: Core and Builtins<45>-Footnote-264423451
Ref: Core and Builtins<45>-Footnote-274423517
Ref: Core and Builtins<45>-Footnote-284423583
Ref: Core and Builtins<45>-Footnote-294423649
Ref: Core and Builtins<45>-Footnote-304423715
Ref: Core and Builtins<45>-Footnote-314423781
Ref: Core and Builtins<45>-Footnote-324423847
Ref: Core and Builtins<45>-Footnote-334423913
Ref: Core and Builtins<45>-Footnote-344423979
Ref: Core and Builtins<45>-Footnote-354424045
Ref: Core and Builtins<45>-Footnote-364424111
Ref: Core and Builtins<45>-Footnote-374424177
Ref: Core and Builtins<45>-Footnote-384424243
Ref: Core and Builtins<45>-Footnote-394424309
Ref: Core and Builtins<45>-Footnote-404424375
Ref: Core and Builtins<45>-Footnote-414424441
Ref: Core and Builtins<45>-Footnote-424424507
Ref: Core and Builtins<45>-Footnote-434424573
Ref: Core and Builtins<45>-Footnote-444424639
Node: Library<44>4424705
Ref: whatsnew/changelog id3914424828
Ref: 18f14424828
Ref: Library<44>-Footnote-14443066
Ref: Library<44>-Footnote-24443131
Ref: Library<44>-Footnote-34443196
Ref: Library<44>-Footnote-44443261
Ref: Library<44>-Footnote-54443326
Ref: Library<44>-Footnote-64443391
Ref: Library<44>-Footnote-74443456
Ref: Library<44>-Footnote-84443521
Ref: Library<44>-Footnote-94443586
Ref: Library<44>-Footnote-104443651
Ref: Library<44>-Footnote-114443717
Ref: Library<44>-Footnote-124443783
Ref: Library<44>-Footnote-134443849
Ref: Library<44>-Footnote-144443915
Ref: Library<44>-Footnote-154443981
Ref: Library<44>-Footnote-164444047
Ref: Library<44>-Footnote-174444113
Ref: Library<44>-Footnote-184444179
Ref: Library<44>-Footnote-194444245
Ref: Library<44>-Footnote-204444311
Ref: Library<44>-Footnote-214444377
Ref: Library<44>-Footnote-224444443
Ref: Library<44>-Footnote-234444509
Ref: Library<44>-Footnote-244444575
Ref: Library<44>-Footnote-254444643
Ref: Library<44>-Footnote-264444709
Ref: Library<44>-Footnote-274444775
Ref: Library<44>-Footnote-284444841
Ref: Library<44>-Footnote-294444907
Ref: Library<44>-Footnote-304444973
Ref: Library<44>-Footnote-314445039
Ref: Library<44>-Footnote-324445105
Ref: Library<44>-Footnote-334445171
Ref: Library<44>-Footnote-344445237
Ref: Library<44>-Footnote-354445303
Ref: Library<44>-Footnote-364445369
Ref: Library<44>-Footnote-374445435
Ref: Library<44>-Footnote-384445501
Ref: Library<44>-Footnote-394445567
Ref: Library<44>-Footnote-404445633
Ref: Library<44>-Footnote-414445699
Ref: Library<44>-Footnote-424445765
Ref: Library<44>-Footnote-434445831
Ref: Library<44>-Footnote-444445897
Ref: Library<44>-Footnote-454445963
Ref: Library<44>-Footnote-464446029
Ref: Library<44>-Footnote-474446095
Ref: Library<44>-Footnote-484446161
Ref: Library<44>-Footnote-494446227
Ref: Library<44>-Footnote-504446293
Ref: Library<44>-Footnote-514446359
Ref: Library<44>-Footnote-524446425
Ref: Library<44>-Footnote-534446491
Ref: Library<44>-Footnote-544446557
Ref: Library<44>-Footnote-554446623
Ref: Library<44>-Footnote-564446689
Ref: Library<44>-Footnote-574446755
Ref: Library<44>-Footnote-584446821
Ref: Library<44>-Footnote-594446887
Ref: Library<44>-Footnote-604446953
Ref: Library<44>-Footnote-614447019
Ref: Library<44>-Footnote-624447085
Ref: Library<44>-Footnote-634447151
Ref: Library<44>-Footnote-644447217
Ref: Library<44>-Footnote-654447283
Ref: Library<44>-Footnote-664447349
Ref: Library<44>-Footnote-674447415
Ref: Library<44>-Footnote-684447481
Ref: Library<44>-Footnote-694447546
Ref: Library<44>-Footnote-704447612
Ref: Library<44>-Footnote-714447677
Ref: Library<44>-Footnote-724447743
Ref: Library<44>-Footnote-734447809
Ref: Library<44>-Footnote-744447875
Ref: Library<44>-Footnote-754447941
Ref: Library<44>-Footnote-764448007
Ref: Library<44>-Footnote-774448073
Ref: Library<44>-Footnote-784448139
Ref: Library<44>-Footnote-794448205
Ref: Library<44>-Footnote-804448271
Ref: Library<44>-Footnote-814448337
Ref: Library<44>-Footnote-824448403
Ref: Library<44>-Footnote-834448469
Ref: Library<44>-Footnote-844448535
Ref: Library<44>-Footnote-854448601
Ref: Library<44>-Footnote-864448667
Ref: Library<44>-Footnote-874448733
Ref: Library<44>-Footnote-884448799
Ref: Library<44>-Footnote-894448865
Ref: Library<44>-Footnote-904448931
Ref: Library<44>-Footnote-914448997
Ref: Library<44>-Footnote-924449063
Ref: Library<44>-Footnote-934449129
Ref: Library<44>-Footnote-944449195
Ref: Library<44>-Footnote-954449261
Ref: Library<44>-Footnote-964449327
Ref: Library<44>-Footnote-974449393
Ref: Library<44>-Footnote-984449459
Ref: Library<44>-Footnote-994449525
Ref: Library<44>-Footnote-1004449591
Ref: Library<44>-Footnote-1014449658
Ref: Library<44>-Footnote-1024449725
Ref: Library<44>-Footnote-1034449792
Ref: Library<44>-Footnote-1044449859
Ref: Library<44>-Footnote-1054449926
Ref: Library<44>-Footnote-1064449993
Ref: Library<44>-Footnote-1074450060
Node: Documentation<39>4450127
Ref: whatsnew/changelog id3924450238
Ref: 18f94450238
Ref: Documentation<39>-Footnote-14452314
Ref: Documentation<39>-Footnote-24452379
Ref: Documentation<39>-Footnote-34452444
Ref: Documentation<39>-Footnote-44452509
Ref: Documentation<39>-Footnote-54452574
Ref: Documentation<39>-Footnote-64452639
Ref: Documentation<39>-Footnote-74452704
Ref: Documentation<39>-Footnote-84452769
Ref: Documentation<39>-Footnote-94452834
Ref: Documentation<39>-Footnote-104452899
Ref: Documentation<39>-Footnote-114452965
Ref: Documentation<39>-Footnote-124453031
Ref: Documentation<39>-Footnote-134453097
Ref: Documentation<39>-Footnote-144453163
Node: Tests<41>4453229
Ref: whatsnew/changelog id3934453338
Ref: 18fa4453338
Ref: Tests<41>-Footnote-14454970
Ref: Tests<41>-Footnote-24455035
Ref: Tests<41>-Footnote-34455100
Ref: Tests<41>-Footnote-44455165
Ref: Tests<41>-Footnote-54455230
Ref: Tests<41>-Footnote-64455295
Ref: Tests<41>-Footnote-74455360
Ref: Tests<41>-Footnote-84455425
Ref: Tests<41>-Footnote-94455490
Ref: Tests<41>-Footnote-104455555
Node: Build<44>4455621
Ref: whatsnew/changelog id3944455724
Ref: 18fc4455724
Ref: Build<44>-Footnote-14456936
Ref: Build<44>-Footnote-24457001
Node: Windows<39>4457066
Ref: whatsnew/changelog id3954457169
Ref: 18fd4457169
Ref: Windows<39>-Footnote-14457601
Ref: Windows<39>-Footnote-24457666
Ref: Windows<39>-Footnote-34457731
Ref: Windows<39>-Footnote-44457796
Node: macOS<33>4457861
Ref: whatsnew/changelog id3964457963
Ref: 18fe4457963
Ref: macOS<33>-Footnote-14458265
Node: IDLE<31>4458330
Ref: whatsnew/changelog id3974458436
Ref: 18ff4458436
Ref: IDLE<31>-Footnote-14459038
Ref: IDLE<31>-Footnote-24459103
Ref: IDLE<31>-Footnote-34459168
Ref: IDLE<31>-Footnote-44459233
Ref: IDLE<31>-Footnote-54459298
Ref: IDLE<31>-Footnote-64459363
Node: Tools/Demos<20>4459428
Ref: whatsnew/changelog id3984459534
Ref: 19004459534
Ref: Tools/Demos<20>-Footnote-14459733
Node: C API<43>4459798
Ref: whatsnew/changelog id3994459887
Ref: 19014459887
Ref: C API<43>-Footnote-14461223
Ref: C API<43>-Footnote-24461288
Ref: C API<43>-Footnote-34461330
Ref: C API<43>-Footnote-44461395
Ref: C API<43>-Footnote-54461460
Ref: C API<43>-Footnote-64461525
Ref: C API<43>-Footnote-74461567
Ref: C API<43>-Footnote-84461632
Ref: C API<43>-Footnote-94461697
Node: Python 3 8 0 alpha 44461762
Ref: whatsnew/changelog python-3-8-0-alpha-44461903
Ref: 19034461903
Node: Security<31>4462284
Ref: whatsnew/changelog id4004462383
Ref: 19044462383
Ref: Security<31>-Footnote-14463268
Ref: Security<31>-Footnote-24463333
Ref: Security<31>-Footnote-34463398
Ref: Security<31>-Footnote-44463467
Node: Core and Builtins<46>4463532
Ref: whatsnew/changelog id4014463651
Ref: 19054463651
Ref: Core and Builtins<46>-Footnote-14466918
Ref: Core and Builtins<46>-Footnote-24466983
Ref: Core and Builtins<46>-Footnote-34467048
Ref: Core and Builtins<46>-Footnote-44467113
Ref: Core and Builtins<46>-Footnote-54467178
Ref: Core and Builtins<46>-Footnote-64467243
Ref: Core and Builtins<46>-Footnote-74467308
Ref: Core and Builtins<46>-Footnote-84467373
Ref: Core and Builtins<46>-Footnote-94467438
Ref: Core and Builtins<46>-Footnote-104467480
Ref: Core and Builtins<46>-Footnote-114467546
Ref: Core and Builtins<46>-Footnote-124467612
Ref: Core and Builtins<46>-Footnote-134467678
Ref: Core and Builtins<46>-Footnote-144467744
Ref: Core and Builtins<46>-Footnote-154467810
Ref: Core and Builtins<46>-Footnote-164467876
Ref: Core and Builtins<46>-Footnote-174467942
Ref: Core and Builtins<46>-Footnote-184468008
Ref: Core and Builtins<46>-Footnote-194468074
Ref: Core and Builtins<46>-Footnote-204468140
Node: Library<45>4468206
Ref: whatsnew/changelog id4024468330
Ref: 19064468330
Ref: Library<45>-Footnote-14477630
Ref: Library<45>-Footnote-24477695
Ref: Library<45>-Footnote-34477760
Ref: Library<45>-Footnote-44477825
Ref: Library<45>-Footnote-54477892
Ref: Library<45>-Footnote-64477957
Ref: Library<45>-Footnote-74478022
Ref: Library<45>-Footnote-84478087
Ref: Library<45>-Footnote-94478152
Ref: Library<45>-Footnote-104478217
Ref: Library<45>-Footnote-114478283
Ref: Library<45>-Footnote-124478349
Ref: Library<45>-Footnote-134478415
Ref: Library<45>-Footnote-144478481
Ref: Library<45>-Footnote-154478547
Ref: Library<45>-Footnote-164478613
Ref: Library<45>-Footnote-174478679
Ref: Library<45>-Footnote-184478745
Ref: Library<45>-Footnote-194478811
Ref: Library<45>-Footnote-204478877
Ref: Library<45>-Footnote-214478943
Ref: Library<45>-Footnote-224479009
Ref: Library<45>-Footnote-234479075
Ref: Library<45>-Footnote-244479141
Ref: Library<45>-Footnote-254479207
Ref: Library<45>-Footnote-264479273
Ref: Library<45>-Footnote-274479339
Ref: Library<45>-Footnote-284479405
Ref: Library<45>-Footnote-294479471
Ref: Library<45>-Footnote-304479537
Ref: Library<45>-Footnote-314479603
Ref: Library<45>-Footnote-324479669
Ref: Library<45>-Footnote-334479735
Ref: Library<45>-Footnote-344479801
Ref: Library<45>-Footnote-354479867
Ref: Library<45>-Footnote-364479933
Ref: Library<45>-Footnote-374479999
Ref: Library<45>-Footnote-384480065
Ref: Library<45>-Footnote-394480131
Ref: Library<45>-Footnote-404480197
Ref: Library<45>-Footnote-414480263
Ref: Library<45>-Footnote-424480329
Ref: Library<45>-Footnote-434480395
Ref: Library<45>-Footnote-444480461
Ref: Library<45>-Footnote-454480527
Ref: Library<45>-Footnote-464480593
Ref: Library<45>-Footnote-474480659
Ref: Library<45>-Footnote-484480725
Ref: Library<45>-Footnote-494480791
Ref: Library<45>-Footnote-504480857
Ref: Library<45>-Footnote-514480923
Ref: Library<45>-Footnote-524480989
Ref: Library<45>-Footnote-534481055
Ref: Library<45>-Footnote-544481121
Node: Documentation<40>4481187
Ref: whatsnew/changelog id4034481299
Ref: 190b4481299
Ref: Documentation<40>-Footnote-14482730
Ref: Documentation<40>-Footnote-24482795
Ref: Documentation<40>-Footnote-34482860
Ref: Documentation<40>-Footnote-44482925
Ref: Documentation<40>-Footnote-54482990
Ref: Documentation<40>-Footnote-64483029
Ref: Documentation<40>-Footnote-74483094
Ref: Documentation<40>-Footnote-84483159
Ref: Documentation<40>-Footnote-94483224
Ref: Documentation<40>-Footnote-104483289
Ref: Documentation<40>-Footnote-114483355
Ref: Documentation<40>-Footnote-124483421
Node: Tests<42>4483487
Ref: whatsnew/changelog id4044483597
Ref: 190c4483597
Ref: Tests<42>-Footnote-14485847
Ref: Tests<42>-Footnote-24485912
Ref: Tests<42>-Footnote-34485977
Ref: Tests<42>-Footnote-44486042
Ref: Tests<42>-Footnote-54486107
Ref: Tests<42>-Footnote-64486172
Ref: Tests<42>-Footnote-74486237
Ref: Tests<42>-Footnote-84486302
Ref: Tests<42>-Footnote-94486367
Ref: Tests<42>-Footnote-104486432
Ref: Tests<42>-Footnote-114486498
Ref: Tests<42>-Footnote-124486564
Ref: Tests<42>-Footnote-134486630
Ref: Tests<42>-Footnote-144486696
Ref: Tests<42>-Footnote-154486762
Node: Build<45>4486828
Ref: whatsnew/changelog id4054486932
Ref: 190e4486932
Ref: Build<45>-Footnote-14490085
Ref: Build<45>-Footnote-24490150
Ref: Build<45>-Footnote-34490215
Ref: Build<45>-Footnote-44490280
Ref: Build<45>-Footnote-54490345
Ref: Build<45>-Footnote-64490410
Ref: Build<45>-Footnote-74490475
Ref: Build<45>-Footnote-84490540
Ref: Build<45>-Footnote-94490605
Ref: Build<45>-Footnote-104490670
Ref: Build<45>-Footnote-114490736
Ref: Build<45>-Footnote-124490802
Ref: Build<45>-Footnote-134490868
Node: Windows<40>4490934
Ref: whatsnew/changelog id4064491038
Ref: 190f4491038
Ref: Windows<40>-Footnote-14493686
Ref: Windows<40>-Footnote-24493751
Ref: Windows<40>-Footnote-34493816
Ref: Windows<40>-Footnote-44493881
Ref: Windows<40>-Footnote-54493946
Ref: Windows<40>-Footnote-64494011
Ref: Windows<40>-Footnote-74494076
Ref: Windows<40>-Footnote-84494141
Ref: Windows<40>-Footnote-94494206
Ref: Windows<40>-Footnote-104494271
Ref: Windows<40>-Footnote-114494337
Ref: Windows<40>-Footnote-124494403
Node: macOS<34>4494469
Ref: whatsnew/changelog id4074494572
Ref: 19104494572
Ref: macOS<34>-Footnote-14494886
Ref: macOS<34>-Footnote-24494951
Node: IDLE<32>4495016
Ref: whatsnew/changelog id4084495123
Ref: 19114495123
Ref: IDLE<32>-Footnote-14495366
Node: Tools/Demos<21>4495431
Ref: whatsnew/changelog id4094495538
Ref: 19124495538
Ref: Tools/Demos<21>-Footnote-14495692
Node: C API<44>4495757
Ref: whatsnew/changelog id4104495847
Ref: 19134495847
Ref: C API<44>-Footnote-14497837
Ref: C API<44>-Footnote-24497902
Ref: C API<44>-Footnote-34497967
Ref: C API<44>-Footnote-44498032
Ref: C API<44>-Footnote-54498097
Ref: C API<44>-Footnote-64498162
Node: Python 3 8 0 alpha 34498227
Ref: whatsnew/changelog python-3-8-0-alpha-34498369
Ref: 19154498369
Node: Security<32>4498730
Ref: whatsnew/changelog id4114498829
Ref: 19164498829
Ref: Security<32>-Footnote-14499391
Ref: Security<32>-Footnote-24499456
Node: Core and Builtins<47>4499521
Ref: whatsnew/changelog id4124499640
Ref: 19184499640
Ref: Core and Builtins<47>-Footnote-14503220
Ref: Core and Builtins<47>-Footnote-24503285
Ref: Core and Builtins<47>-Footnote-34503350
Ref: Core and Builtins<47>-Footnote-44503415
Ref: Core and Builtins<47>-Footnote-54503480
Ref: Core and Builtins<47>-Footnote-64503545
Ref: Core and Builtins<47>-Footnote-74503610
Ref: Core and Builtins<47>-Footnote-84503675
Ref: Core and Builtins<47>-Footnote-94503740
Ref: Core and Builtins<47>-Footnote-104503805
Ref: Core and Builtins<47>-Footnote-114503871
Ref: Core and Builtins<47>-Footnote-124503937
Ref: Core and Builtins<47>-Footnote-134504003
Ref: Core and Builtins<47>-Footnote-144504069
Ref: Core and Builtins<47>-Footnote-154504135
Ref: Core and Builtins<47>-Footnote-164504201
Ref: Core and Builtins<47>-Footnote-174504267
Ref: Core and Builtins<47>-Footnote-184504333
Ref: Core and Builtins<47>-Footnote-194504399
Ref: Core and Builtins<47>-Footnote-204504465
Ref: Core and Builtins<47>-Footnote-214504531
Ref: Core and Builtins<47>-Footnote-224504597
Node: Library<46>4504663
Ref: whatsnew/changelog id4134504787
Ref: 191a4504787
Ref: Library<46>-Footnote-14510356
Ref: Library<46>-Footnote-24510421
Ref: Library<46>-Footnote-34510486
Ref: Library<46>-Footnote-44510551
Ref: Library<46>-Footnote-54510616
Ref: Library<46>-Footnote-64510681
Ref: Library<46>-Footnote-74510746
Ref: Library<46>-Footnote-84510811
Ref: Library<46>-Footnote-94510876
Ref: Library<46>-Footnote-104510941
Ref: Library<46>-Footnote-114511007
Ref: Library<46>-Footnote-124511073
Ref: Library<46>-Footnote-134511139
Ref: Library<46>-Footnote-144511205
Ref: Library<46>-Footnote-154511271
Ref: Library<46>-Footnote-164511337
Ref: Library<46>-Footnote-174511403
Ref: Library<46>-Footnote-184511469
Ref: Library<46>-Footnote-194511535
Ref: Library<46>-Footnote-204511601
Ref: Library<46>-Footnote-214511667
Ref: Library<46>-Footnote-224511733
Ref: Library<46>-Footnote-234511799
Ref: Library<46>-Footnote-244511865
Ref: Library<46>-Footnote-254511931
Ref: Library<46>-Footnote-264511997
Ref: Library<46>-Footnote-274512063
Ref: Library<46>-Footnote-284512129
Ref: Library<46>-Footnote-294512195
Ref: Library<46>-Footnote-304512261
Ref: Library<46>-Footnote-314512327
Ref: Library<46>-Footnote-324512393
Ref: Library<46>-Footnote-334512459
Ref: Library<46>-Footnote-344512525
Ref: Library<46>-Footnote-354512591
Ref: Library<46>-Footnote-364512657
Ref: Library<46>-Footnote-374512723
Node: Documentation<41>4512789
Ref: whatsnew/changelog id4144512901
Ref: 191c4512901
Ref: Documentation<41>-Footnote-14513472
Ref: Documentation<41>-Footnote-24513537
Ref: Documentation<41>-Footnote-34513602
Node: Tests<43>4513667
Ref: whatsnew/changelog id4154513777
Ref: 191d4513777
Ref: Tests<43>-Footnote-14514289
Ref: Tests<43>-Footnote-24514354
Ref: Tests<43>-Footnote-34514419
Node: Build<46>4514484
Ref: whatsnew/changelog id4164514588
Ref: 191e4514588
Ref: Build<46>-Footnote-14515108
Ref: Build<46>-Footnote-24515173
Ref: Build<46>-Footnote-34515238
Ref: Build<46>-Footnote-44515303
Node: Windows<41>4515368
Ref: whatsnew/changelog id4174515471
Ref: 191f4515471
Ref: Windows<41>-Footnote-14515920
Ref: Windows<41>-Footnote-24515985
Ref: Windows<41>-Footnote-34516050
Node: IDLE<33>4516115
Ref: whatsnew/changelog id4184516224
Ref: 19204516224
Ref: IDLE<33>-Footnote-14517333
Ref: IDLE<33>-Footnote-24517398
Ref: IDLE<33>-Footnote-34517463
Ref: IDLE<33>-Footnote-44517528
Ref: IDLE<33>-Footnote-54517593
Ref: IDLE<33>-Footnote-64517658
Ref: IDLE<33>-Footnote-74517723
Ref: IDLE<33>-Footnote-84517788
Ref: IDLE<33>-Footnote-94517853
Node: Tools/Demos<22>4517918
Ref: whatsnew/changelog id4194518025
Ref: 19214518025
Ref: Tools/Demos<22>-Footnote-14518238
Ref: Tools/Demos<22>-Footnote-24518303
Node: C API<45>4518368
Ref: whatsnew/changelog id4204518458
Ref: 19224518458
Ref: C API<45>-Footnote-14518846
Ref: C API<45>-Footnote-24518911
Node: Python 3 8 0 alpha 24518976
Ref: whatsnew/changelog python-3-8-0-alpha-24519118
Ref: 19234519118
Node: Core and Builtins<48>4519381
Ref: whatsnew/changelog id4214519479
Ref: 19244519479
Ref: Core and Builtins<48>-Footnote-14522618
Ref: Core and Builtins<48>-Footnote-24522683
Ref: Core and Builtins<48>-Footnote-34522748
Ref: Core and Builtins<48>-Footnote-44522813
Ref: Core and Builtins<48>-Footnote-54522878
Ref: Core and Builtins<48>-Footnote-64522945
Ref: Core and Builtins<48>-Footnote-74523010
Ref: Core and Builtins<48>-Footnote-84523075
Ref: Core and Builtins<48>-Footnote-94523140
Ref: Core and Builtins<48>-Footnote-104523205
Ref: Core and Builtins<48>-Footnote-114523271
Ref: Core and Builtins<48>-Footnote-124523337
Ref: Core and Builtins<48>-Footnote-134523403
Ref: Core and Builtins<48>-Footnote-144523469
Ref: Core and Builtins<48>-Footnote-154523535
Ref: Core and Builtins<48>-Footnote-164523601
Ref: Core and Builtins<48>-Footnote-174523667
Node: Library<47>4523733
Ref: whatsnew/changelog id4224523857
Ref: 19254523857
Ref: Library<47>-Footnote-14527564
Ref: Library<47>-Footnote-24527629
Ref: Library<47>-Footnote-34527694
Ref: Library<47>-Footnote-44527759
Ref: Library<47>-Footnote-54527824
Ref: Library<47>-Footnote-64527889
Ref: Library<47>-Footnote-74527954
Ref: Library<47>-Footnote-84528019
Ref: Library<47>-Footnote-94528084
Ref: Library<47>-Footnote-104528149
Ref: Library<47>-Footnote-114528215
Ref: Library<47>-Footnote-124528281
Ref: Library<47>-Footnote-134528347
Ref: Library<47>-Footnote-144528413
Ref: Library<47>-Footnote-154528479
Ref: Library<47>-Footnote-164528545
Ref: Library<47>-Footnote-174528611
Node: Documentation<42>4528677
Ref: whatsnew/changelog id4234528789
Ref: 19284528789
Ref: Documentation<42>-Footnote-14529165
Ref: Documentation<42>-Footnote-24529230
Ref: Documentation<42>-Footnote-34529295
Node: Tests<44>4529360
Ref: whatsnew/changelog id4244529472
Ref: 19294529472
Ref: Tests<44>-Footnote-14530837
Ref: Tests<44>-Footnote-24530902
Ref: Tests<44>-Footnote-34530967
Ref: Tests<44>-Footnote-44531032
Ref: Tests<44>-Footnote-54531097
Ref: Tests<44>-Footnote-64531162
Ref: Tests<44>-Footnote-74531227
Ref: Tests<44>-Footnote-84531292
Node: Windows<42>4531357
Ref: whatsnew/changelog id4254531460
Ref: 192a4531460
Ref: Windows<42>-Footnote-14532057
Ref: Windows<42>-Footnote-24532122
Ref: Windows<42>-Footnote-34532187
Ref: Windows<42>-Footnote-44532252
Ref: Windows<42>-Footnote-54532317
Node: IDLE<34>4532382
Ref: whatsnew/changelog id4264532467
Ref: 192b4532467
Ref: IDLE<34>-Footnote-14532771
Ref: IDLE<34>-Footnote-24532836
Ref: IDLE<34>-Footnote-34532901
Node: Python 3 8 0 alpha 14532966
Ref: whatsnew/changelog python-3-8-0-alpha-14533106
Ref: 192c4533106
Node: Security<33>4533487
Ref: whatsnew/changelog id4274533586
Ref: 192d4533586
Ref: Security<33>-Footnote-14535924
Ref: Security<33>-Footnote-24535989
Ref: Security<33>-Footnote-34536058
Ref: Security<33>-Footnote-44536123
Ref: Security<33>-Footnote-54536188
Ref: Security<33>-Footnote-64536253
Ref: Security<33>-Footnote-74536318
Ref: Security<33>-Footnote-84536388
Ref: Security<33>-Footnote-94536453
Ref: Security<33>-Footnote-104536518
Ref: Security<33>-Footnote-114536584
Ref: Security<33>-Footnote-124536650
Ref: Security<33>-Footnote-134536720
Ref: Security<33>-Footnote-144536786
Ref: Security<33>-Footnote-154536852
Ref: Security<33>-Footnote-164536922
Ref: Security<33>-Footnote-174536992
Node: Core and Builtins<49>4537058
Ref: whatsnew/changelog id4284537177
Ref: 192e4537177
Ref: Core and Builtins<49>-Footnote-14563215
Ref: Core and Builtins<49>-Footnote-24563280
Ref: Core and Builtins<49>-Footnote-34563345
Ref: Core and Builtins<49>-Footnote-44563410
Ref: Core and Builtins<49>-Footnote-54563475
Ref: Core and Builtins<49>-Footnote-64563540
Ref: Core and Builtins<49>-Footnote-74563605
Ref: Core and Builtins<49>-Footnote-84563670
Ref: Core and Builtins<49>-Footnote-94563735
Ref: Core and Builtins<49>-Footnote-104563800
Ref: Core and Builtins<49>-Footnote-114563866
Ref: Core and Builtins<49>-Footnote-124563932
Ref: Core and Builtins<49>-Footnote-134563998
Ref: Core and Builtins<49>-Footnote-144564064
Ref: Core and Builtins<49>-Footnote-154564130
Ref: Core and Builtins<49>-Footnote-164564196
Ref: Core and Builtins<49>-Footnote-174564262
Ref: Core and Builtins<49>-Footnote-184564328
Ref: Core and Builtins<49>-Footnote-194564394
Ref: Core and Builtins<49>-Footnote-204564460
Ref: Core and Builtins<49>-Footnote-214564526
Ref: Core and Builtins<49>-Footnote-224564592
Ref: Core and Builtins<49>-Footnote-234564658
Ref: Core and Builtins<49>-Footnote-244564724
Ref: Core and Builtins<49>-Footnote-254564790
Ref: Core and Builtins<49>-Footnote-264564833
Ref: Core and Builtins<49>-Footnote-274564899
Ref: Core and Builtins<49>-Footnote-284564965
Ref: Core and Builtins<49>-Footnote-294565031
Ref: Core and Builtins<49>-Footnote-304565097
Ref: Core and Builtins<49>-Footnote-314565163
Ref: Core and Builtins<49>-Footnote-324565229
Ref: Core and Builtins<49>-Footnote-334565295
Ref: Core and Builtins<49>-Footnote-344565361
Ref: Core and Builtins<49>-Footnote-354565427
Ref: Core and Builtins<49>-Footnote-364565493
Ref: Core and Builtins<49>-Footnote-374565559
Ref: Core and Builtins<49>-Footnote-384565625
Ref: Core and Builtins<49>-Footnote-394565691
Ref: Core and Builtins<49>-Footnote-404565757
Ref: Core and Builtins<49>-Footnote-414565823
Ref: Core and Builtins<49>-Footnote-424565889
Ref: Core and Builtins<49>-Footnote-434565955
Ref: Core and Builtins<49>-Footnote-444566021
Ref: Core and Builtins<49>-Footnote-454566087
Ref: Core and Builtins<49>-Footnote-464566153
Ref: Core and Builtins<49>-Footnote-474566219
Ref: Core and Builtins<49>-Footnote-484566285
Ref: Core and Builtins<49>-Footnote-494566351
Ref: Core and Builtins<49>-Footnote-504566417
Ref: Core and Builtins<49>-Footnote-514566483
Ref: Core and Builtins<49>-Footnote-524566549
Ref: Core and Builtins<49>-Footnote-534566615
Ref: Core and Builtins<49>-Footnote-544566681
Ref: Core and Builtins<49>-Footnote-554566747
Ref: Core and Builtins<49>-Footnote-564566813
Ref: Core and Builtins<49>-Footnote-574566879
Ref: Core and Builtins<49>-Footnote-584566945
Ref: Core and Builtins<49>-Footnote-594567011
Ref: Core and Builtins<49>-Footnote-604567076
Ref: Core and Builtins<49>-Footnote-614567142
Ref: Core and Builtins<49>-Footnote-624567208
Ref: Core and Builtins<49>-Footnote-634567274
Ref: Core and Builtins<49>-Footnote-644567340
Ref: Core and Builtins<49>-Footnote-654567406
Ref: Core and Builtins<49>-Footnote-664567472
Ref: Core and Builtins<49>-Footnote-674567538
Ref: Core and Builtins<49>-Footnote-684567604
Ref: Core and Builtins<49>-Footnote-694567670
Ref: Core and Builtins<49>-Footnote-704567736
Ref: Core and Builtins<49>-Footnote-714567802
Ref: Core and Builtins<49>-Footnote-724567868
Ref: Core and Builtins<49>-Footnote-734567934
Ref: Core and Builtins<49>-Footnote-744568000
Ref: Core and Builtins<49>-Footnote-754568066
Ref: Core and Builtins<49>-Footnote-764568132
Ref: Core and Builtins<49>-Footnote-774568198
Ref: Core and Builtins<49>-Footnote-784568264
Ref: Core and Builtins<49>-Footnote-794568330
Ref: Core and Builtins<49>-Footnote-804568396
Ref: Core and Builtins<49>-Footnote-814568462
Ref: Core and Builtins<49>-Footnote-824568528
Ref: Core and Builtins<49>-Footnote-834568594
Ref: Core and Builtins<49>-Footnote-844568660
Ref: Core and Builtins<49>-Footnote-854568726
Ref: Core and Builtins<49>-Footnote-864568792
Ref: Core and Builtins<49>-Footnote-874568858
Ref: Core and Builtins<49>-Footnote-884568924
Ref: Core and Builtins<49>-Footnote-894568990
Ref: Core and Builtins<49>-Footnote-904569056
Ref: Core and Builtins<49>-Footnote-914569122
Ref: Core and Builtins<49>-Footnote-924569188
Ref: Core and Builtins<49>-Footnote-934569254
Ref: Core and Builtins<49>-Footnote-944569320
Ref: Core and Builtins<49>-Footnote-954569386
Ref: Core and Builtins<49>-Footnote-964569452
Ref: Core and Builtins<49>-Footnote-974569520
Ref: Core and Builtins<49>-Footnote-984569586
Ref: Core and Builtins<49>-Footnote-994569652
Ref: Core and Builtins<49>-Footnote-1004569718
Ref: Core and Builtins<49>-Footnote-1014569785
Ref: Core and Builtins<49>-Footnote-1024569852
Ref: Core and Builtins<49>-Footnote-1034569919
Ref: Core and Builtins<49>-Footnote-1044569986
Ref: Core and Builtins<49>-Footnote-1054570053
Ref: Core and Builtins<49>-Footnote-1064570120
Ref: Core and Builtins<49>-Footnote-1074570187
Ref: Core and Builtins<49>-Footnote-1084570254
Ref: Core and Builtins<49>-Footnote-1094570321
Ref: Core and Builtins<49>-Footnote-1104570388
Ref: Core and Builtins<49>-Footnote-1114570455
Ref: Core and Builtins<49>-Footnote-1124570522
Ref: Core and Builtins<49>-Footnote-1134570589
Ref: Core and Builtins<49>-Footnote-1144570656
Ref: Core and Builtins<49>-Footnote-1154570723
Ref: Core and Builtins<49>-Footnote-1164570790
Ref: Core and Builtins<49>-Footnote-1174570857
Ref: Core and Builtins<49>-Footnote-1184570924
Ref: Core and Builtins<49>-Footnote-1194570991
Ref: Core and Builtins<49>-Footnote-1204571058
Ref: Core and Builtins<49>-Footnote-1214571125
Ref: Core and Builtins<49>-Footnote-1224571192
Ref: Core and Builtins<49>-Footnote-1234571259
Ref: Core and Builtins<49>-Footnote-1244571326
Ref: Core and Builtins<49>-Footnote-1254571393
Ref: Core and Builtins<49>-Footnote-1264571460
Ref: Core and Builtins<49>-Footnote-1274571527
Ref: Core and Builtins<49>-Footnote-1284571594
Ref: Core and Builtins<49>-Footnote-1294571661
Ref: Core and Builtins<49>-Footnote-1304571728
Ref: Core and Builtins<49>-Footnote-1314571795
Ref: Core and Builtins<49>-Footnote-1324571862
Ref: Core and Builtins<49>-Footnote-1334571929
Ref: Core and Builtins<49>-Footnote-1344571996
Ref: Core and Builtins<49>-Footnote-1354572063
Ref: Core and Builtins<49>-Footnote-1364572130
Ref: Core and Builtins<49>-Footnote-1374572197
Ref: Core and Builtins<49>-Footnote-1384572264
Ref: Core and Builtins<49>-Footnote-1394572331
Ref: Core and Builtins<49>-Footnote-1404572398
Ref: Core and Builtins<49>-Footnote-1414572465
Ref: Core and Builtins<49>-Footnote-1424572532
Ref: Core and Builtins<49>-Footnote-1434572599
Ref: Core and Builtins<49>-Footnote-1444572666
Ref: Core and Builtins<49>-Footnote-1454572733
Ref: Core and Builtins<49>-Footnote-1464572800
Ref: Core and Builtins<49>-Footnote-1474572867
Ref: Core and Builtins<49>-Footnote-1484572934
Ref: Core and Builtins<49>-Footnote-1494573001
Ref: Core and Builtins<49>-Footnote-1504573068
Ref: Core and Builtins<49>-Footnote-1514573135
Ref: Core and Builtins<49>-Footnote-1524573202
Ref: Core and Builtins<49>-Footnote-1534573269
Ref: Core and Builtins<49>-Footnote-1544573336
Ref: Core and Builtins<49>-Footnote-1554573403
Ref: Core and Builtins<49>-Footnote-1564573470
Ref: Core and Builtins<49>-Footnote-1574573537
Ref: Core and Builtins<49>-Footnote-1584573604
Ref: Core and Builtins<49>-Footnote-1594573671
Ref: Core and Builtins<49>-Footnote-1604573738
Ref: Core and Builtins<49>-Footnote-1614573805
Ref: Core and Builtins<49>-Footnote-1624573872
Node: Library<48>4573939
Ref: whatsnew/changelog id4294574063
Ref: 19344574063
Ref: Library<48>-Footnote-14644959
Ref: Library<48>-Footnote-24645024
Ref: Library<48>-Footnote-34645089
Ref: Library<48>-Footnote-44645154
Ref: Library<48>-Footnote-54645219
Ref: Library<48>-Footnote-64645284
Ref: Library<48>-Footnote-74645349
Ref: Library<48>-Footnote-84645414
Ref: Library<48>-Footnote-94645479
Ref: Library<48>-Footnote-104645544
Ref: Library<48>-Footnote-114645610
Ref: Library<48>-Footnote-124645676
Ref: Library<48>-Footnote-134645742
Ref: Library<48>-Footnote-144645808
Ref: Library<48>-Footnote-154645874
Ref: Library<48>-Footnote-164645940
Ref: Library<48>-Footnote-174646006
Ref: Library<48>-Footnote-184646072
Ref: Library<48>-Footnote-194646138
Ref: Library<48>-Footnote-204646204
Ref: Library<48>-Footnote-214646270
Ref: Library<48>-Footnote-224646336
Ref: Library<48>-Footnote-234646402
Ref: Library<48>-Footnote-244646468
Ref: Library<48>-Footnote-254646534
Ref: Library<48>-Footnote-264646600
Ref: Library<48>-Footnote-274646666
Ref: Library<48>-Footnote-284646732
Ref: Library<48>-Footnote-294646798
Ref: Library<48>-Footnote-304646864
Ref: Library<48>-Footnote-314646930
Ref: Library<48>-Footnote-324646996
Ref: Library<48>-Footnote-334647062
Ref: Library<48>-Footnote-344647128
Ref: Library<48>-Footnote-354647194
Ref: Library<48>-Footnote-364647260
Ref: Library<48>-Footnote-374647326
Ref: Library<48>-Footnote-384647392
Ref: Library<48>-Footnote-394647458
Ref: Library<48>-Footnote-404647524
Ref: Library<48>-Footnote-414647590
Ref: Library<48>-Footnote-424647656
Ref: Library<48>-Footnote-434647722
Ref: Library<48>-Footnote-444647788
Ref: Library<48>-Footnote-454647854
Ref: Library<48>-Footnote-464647920
Ref: Library<48>-Footnote-474647986
Ref: Library<48>-Footnote-484648052
Ref: Library<48>-Footnote-494648118
Ref: Library<48>-Footnote-504648184
Ref: Library<48>-Footnote-514648250
Ref: Library<48>-Footnote-524648316
Ref: Library<48>-Footnote-534648382
Ref: Library<48>-Footnote-544648448
Ref: Library<48>-Footnote-554648514
Ref: Library<48>-Footnote-564648580
Ref: Library<48>-Footnote-574648646
Ref: Library<48>-Footnote-584648712
Ref: Library<48>-Footnote-594648778
Ref: Library<48>-Footnote-604648844
Ref: Library<48>-Footnote-614648910
Ref: Library<48>-Footnote-624648976
Ref: Library<48>-Footnote-634649042
Ref: Library<48>-Footnote-644649108
Ref: Library<48>-Footnote-654649174
Ref: Library<48>-Footnote-664649240
Ref: Library<48>-Footnote-674649306
Ref: Library<48>-Footnote-684649372
Ref: Library<48>-Footnote-694649438
Ref: Library<48>-Footnote-704649504
Ref: Library<48>-Footnote-714649570
Ref: Library<48>-Footnote-724649636
Ref: Library<48>-Footnote-734649702
Ref: Library<48>-Footnote-744649768
Ref: Library<48>-Footnote-754649834
Ref: Library<48>-Footnote-764649900
Ref: Library<48>-Footnote-774649966
Ref: Library<48>-Footnote-784650032
Ref: Library<48>-Footnote-794650098
Ref: Library<48>-Footnote-804650164
Ref: Library<48>-Footnote-814650230
Ref: Library<48>-Footnote-824650296
Ref: Library<48>-Footnote-834650362
Ref: Library<48>-Footnote-844650428
Ref: Library<48>-Footnote-854650494
Ref: Library<48>-Footnote-864650560
Ref: Library<48>-Footnote-874650626
Ref: Library<48>-Footnote-884650692
Ref: Library<48>-Footnote-894650758
Ref: Library<48>-Footnote-904650824
Ref: Library<48>-Footnote-914650890
Ref: Library<48>-Footnote-924650956
Ref: Library<48>-Footnote-934651022
Ref: Library<48>-Footnote-944651082
Ref: Library<48>-Footnote-954651148
Ref: Library<48>-Footnote-964651214
Ref: Library<48>-Footnote-974651280
Ref: Library<48>-Footnote-984651346
Ref: Library<48>-Footnote-994651412
Ref: Library<48>-Footnote-1004651478
Ref: Library<48>-Footnote-1014651545
Ref: Library<48>-Footnote-1024651612
Ref: Library<48>-Footnote-1034651679
Ref: Library<48>-Footnote-1044651746
Ref: Library<48>-Footnote-1054651813
Ref: Library<48>-Footnote-1064651880
Ref: Library<48>-Footnote-1074651947
Ref: Library<48>-Footnote-1084652014
Ref: Library<48>-Footnote-1094652081
Ref: Library<48>-Footnote-1104652148
Ref: Library<48>-Footnote-1114652215
Ref: Library<48>-Footnote-1124652282
Ref: Library<48>-Footnote-1134652349
Ref: Library<48>-Footnote-1144652416
Ref: Library<48>-Footnote-1154652483
Ref: Library<48>-Footnote-1164652550
Ref: Library<48>-Footnote-1174652617
Ref: Library<48>-Footnote-1184652684
Ref: Library<48>-Footnote-1194652751
Ref: Library<48>-Footnote-1204652818
Ref: Library<48>-Footnote-1214652885
Ref: Library<48>-Footnote-1224652952
Ref: Library<48>-Footnote-1234653019
Ref: Library<48>-Footnote-1244653086
Ref: Library<48>-Footnote-1254653153
Ref: Library<48>-Footnote-1264653219
Ref: Library<48>-Footnote-1274653286
Ref: Library<48>-Footnote-1284653353
Ref: Library<48>-Footnote-1294653420
Ref: Library<48>-Footnote-1304653487
Ref: Library<48>-Footnote-1314653554
Ref: Library<48>-Footnote-1324653621
Ref: Library<48>-Footnote-1334653688
Ref: Library<48>-Footnote-1344653755
Ref: Library<48>-Footnote-1354653822
Ref: Library<48>-Footnote-1364653889
Ref: Library<48>-Footnote-1374653955
Ref: Library<48>-Footnote-1384654022
Ref: Library<48>-Footnote-1394654089
Ref: Library<48>-Footnote-1404654156
Ref: Library<48>-Footnote-1414654223
Ref: Library<48>-Footnote-1424654290
Ref: Library<48>-Footnote-1434654357
Ref: Library<48>-Footnote-1444654424
Ref: Library<48>-Footnote-1454654491
Ref: Library<48>-Footnote-1464654558
Ref: Library<48>-Footnote-1474654625
Ref: Library<48>-Footnote-1484654692
Ref: Library<48>-Footnote-1494654759
Ref: Library<48>-Footnote-1504654826
Ref: Library<48>-Footnote-1514654893
Ref: Library<48>-Footnote-1524654960
Ref: Library<48>-Footnote-1534655027
Ref: Library<48>-Footnote-1544655094
Ref: Library<48>-Footnote-1554655160
Ref: Library<48>-Footnote-1564655227
Ref: Library<48>-Footnote-1574655294
Ref: Library<48>-Footnote-1584655361
Ref: Library<48>-Footnote-1594655428
Ref: Library<48>-Footnote-1604655495
Ref: Library<48>-Footnote-1614655562
Ref: Library<48>-Footnote-1624655606
Ref: Library<48>-Footnote-1634655673
Ref: Library<48>-Footnote-1644655740
Ref: Library<48>-Footnote-1654655807
Ref: Library<48>-Footnote-1664655873
Ref: Library<48>-Footnote-1674655940
Ref: Library<48>-Footnote-1684656007
Ref: Library<48>-Footnote-1694656074
Ref: Library<48>-Footnote-1704656141
Ref: Library<48>-Footnote-1714656208
Ref: Library<48>-Footnote-1724656275
Ref: Library<48>-Footnote-1734656342
Ref: Library<48>-Footnote-1744656409
Ref: Library<48>-Footnote-1754656475
Ref: Library<48>-Footnote-1764656542
Ref: Library<48>-Footnote-1774656609
Ref: Library<48>-Footnote-1784656676
Ref: Library<48>-Footnote-1794656743
Ref: Library<48>-Footnote-1804656810
Ref: Library<48>-Footnote-1814656876
Ref: Library<48>-Footnote-1824656943
Ref: Library<48>-Footnote-1834657010
Ref: Library<48>-Footnote-1844657077
Ref: Library<48>-Footnote-1854657144
Ref: Library<48>-Footnote-1864657211
Ref: Library<48>-Footnote-1874657278
Ref: Library<48>-Footnote-1884657345
Ref: Library<48>-Footnote-1894657412
Ref: Library<48>-Footnote-1904657479
Ref: Library<48>-Footnote-1914657546
Ref: Library<48>-Footnote-1924657613
Ref: Library<48>-Footnote-1934657680
Ref: Library<48>-Footnote-1944657747
Ref: Library<48>-Footnote-1954657814
Ref: Library<48>-Footnote-1964657881
Ref: Library<48>-Footnote-1974657948
Ref: Library<48>-Footnote-1984658015
Ref: Library<48>-Footnote-1994658082
Ref: Library<48>-Footnote-2004658149
Ref: Library<48>-Footnote-2014658216
Ref: Library<48>-Footnote-2024658283
Ref: Library<48>-Footnote-2034658351
Ref: Library<48>-Footnote-2044658418
Ref: Library<48>-Footnote-2054658485
Ref: Library<48>-Footnote-2064658552
Ref: Library<48>-Footnote-2074658619
Ref: Library<48>-Footnote-2084658686
Ref: Library<48>-Footnote-2094658753
Ref: Library<48>-Footnote-2104658820
Ref: Library<48>-Footnote-2114658887
Ref: Library<48>-Footnote-2124658954
Ref: Library<48>-Footnote-2134659021
Ref: Library<48>-Footnote-2144659065
Ref: Library<48>-Footnote-2154659132
Ref: Library<48>-Footnote-2164659199
Ref: Library<48>-Footnote-2174659266
Ref: Library<48>-Footnote-2184659333
Ref: Library<48>-Footnote-2194659400
Ref: Library<48>-Footnote-2204659467
Ref: Library<48>-Footnote-2214659534
Ref: Library<48>-Footnote-2224659601
Ref: Library<48>-Footnote-2234659668
Ref: Library<48>-Footnote-2244659735
Ref: Library<48>-Footnote-2254659802
Ref: Library<48>-Footnote-2264659869
Ref: Library<48>-Footnote-2274659936
Ref: Library<48>-Footnote-2284660003
Ref: Library<48>-Footnote-2294660070
Ref: Library<48>-Footnote-2304660137
Ref: Library<48>-Footnote-2314660204
Ref: Library<48>-Footnote-2324660271
Ref: Library<48>-Footnote-2334660338
Ref: Library<48>-Footnote-2344660405
Ref: Library<48>-Footnote-2354660472
Ref: Library<48>-Footnote-2364660539
Ref: Library<48>-Footnote-2374660606
Ref: Library<48>-Footnote-2384660673
Ref: Library<48>-Footnote-2394660740
Ref: Library<48>-Footnote-2404660807
Ref: Library<48>-Footnote-2414660874
Ref: Library<48>-Footnote-2424660941
Ref: Library<48>-Footnote-2434661008
Ref: Library<48>-Footnote-2444661075
Ref: Library<48>-Footnote-2454661142
Ref: Library<48>-Footnote-2464661209
Ref: Library<48>-Footnote-2474661276
Ref: Library<48>-Footnote-2484661343
Ref: Library<48>-Footnote-2494661410
Ref: Library<48>-Footnote-2504661477
Ref: Library<48>-Footnote-2514661544
Ref: Library<48>-Footnote-2524661611
Ref: Library<48>-Footnote-2534661678
Ref: Library<48>-Footnote-2544661745
Ref: Library<48>-Footnote-2554661812
Ref: Library<48>-Footnote-2564661879
Ref: Library<48>-Footnote-2574661946
Ref: Library<48>-Footnote-2584662013
Ref: Library<48>-Footnote-2594662080
Ref: Library<48>-Footnote-2604662147
Ref: Library<48>-Footnote-2614662213
Ref: Library<48>-Footnote-2624662280
Ref: Library<48>-Footnote-2634662347
Ref: Library<48>-Footnote-2644662414
Ref: Library<48>-Footnote-2654662481
Ref: Library<48>-Footnote-2664662548
Ref: Library<48>-Footnote-2674662615
Ref: Library<48>-Footnote-2684662682
Ref: Library<48>-Footnote-2694662749
Ref: Library<48>-Footnote-2704662816
Ref: Library<48>-Footnote-2714662883
Ref: Library<48>-Footnote-2724662950
Ref: Library<48>-Footnote-2734663017
Ref: Library<48>-Footnote-2744663084
Ref: Library<48>-Footnote-2754663151
Ref: Library<48>-Footnote-2764663218
Ref: Library<48>-Footnote-2774663285
Ref: Library<48>-Footnote-2784663352
Ref: Library<48>-Footnote-2794663419
Ref: Library<48>-Footnote-2804663486
Ref: Library<48>-Footnote-2814663553
Ref: Library<48>-Footnote-2824663620
Ref: Library<48>-Footnote-2834663687
Ref: Library<48>-Footnote-2844663754
Ref: Library<48>-Footnote-2854663821
Ref: Library<48>-Footnote-2864663888
Ref: Library<48>-Footnote-2874663955
Ref: Library<48>-Footnote-2884664022
Ref: Library<48>-Footnote-2894664089
Ref: Library<48>-Footnote-2904664156
Ref: Library<48>-Footnote-2914664223
Ref: Library<48>-Footnote-2924664290
Ref: Library<48>-Footnote-2934664357
Ref: Library<48>-Footnote-2944664424
Ref: Library<48>-Footnote-2954664491
Ref: Library<48>-Footnote-2964664558
Ref: Library<48>-Footnote-2974664625
Ref: Library<48>-Footnote-2984664692
Ref: Library<48>-Footnote-2994664759
Ref: Library<48>-Footnote-3004664826
Ref: Library<48>-Footnote-3014664893
Ref: Library<48>-Footnote-3024664960
Ref: Library<48>-Footnote-3034665027
Ref: Library<48>-Footnote-3044665094
Ref: Library<48>-Footnote-3054665161
Ref: Library<48>-Footnote-3064665228
Ref: Library<48>-Footnote-3074665295
Ref: Library<48>-Footnote-3084665362
Ref: Library<48>-Footnote-3094665429
Ref: Library<48>-Footnote-3104665496
Ref: Library<48>-Footnote-3114665563
Ref: Library<48>-Footnote-3124665630
Ref: Library<48>-Footnote-3134665697
Ref: Library<48>-Footnote-3144665764
Ref: Library<48>-Footnote-3154665831
Ref: Library<48>-Footnote-3164665898
Ref: Library<48>-Footnote-3174665965
Ref: Library<48>-Footnote-3184666032
Ref: Library<48>-Footnote-3194666099
Ref: Library<48>-Footnote-3204666166
Ref: Library<48>-Footnote-3214666233
Ref: Library<48>-Footnote-3224666300
Ref: Library<48>-Footnote-3234666367
Ref: Library<48>-Footnote-3244666434
Ref: Library<48>-Footnote-3254666501
Ref: Library<48>-Footnote-3264666568
Ref: Library<48>-Footnote-3274666635
Ref: Library<48>-Footnote-3284666702
Ref: Library<48>-Footnote-3294666770
Ref: Library<48>-Footnote-3304666837
Ref: Library<48>-Footnote-3314666904
Ref: Library<48>-Footnote-3324666971
Ref: Library<48>-Footnote-3334667038
Ref: Library<48>-Footnote-3344667105
Ref: Library<48>-Footnote-3354667172
Ref: Library<48>-Footnote-3364667239
Ref: Library<48>-Footnote-3374667306
Ref: Library<48>-Footnote-3384667373
Ref: Library<48>-Footnote-3394667440
Ref: Library<48>-Footnote-3404667507
Ref: Library<48>-Footnote-3414667574
Ref: Library<48>-Footnote-3424667641
Ref: Library<48>-Footnote-3434667708
Ref: Library<48>-Footnote-3444667775
Ref: Library<48>-Footnote-3454667842
Ref: Library<48>-Footnote-3464667886
Ref: Library<48>-Footnote-3474667953
Ref: Library<48>-Footnote-3484668020
Ref: Library<48>-Footnote-3494668087
Ref: Library<48>-Footnote-3504668131
Ref: Library<48>-Footnote-3514668198
Ref: Library<48>-Footnote-3524668265
Ref: Library<48>-Footnote-3534668332
Ref: Library<48>-Footnote-3544668399
Ref: Library<48>-Footnote-3554668466
Ref: Library<48>-Footnote-3564668533
Ref: Library<48>-Footnote-3574668600
Ref: Library<48>-Footnote-3584668667
Ref: Library<48>-Footnote-3594668734
Ref: Library<48>-Footnote-3604668801
Ref: Library<48>-Footnote-3614668868
Ref: Library<48>-Footnote-3624668935
Ref: Library<48>-Footnote-3634669002
Ref: Library<48>-Footnote-3644669069
Ref: Library<48>-Footnote-3654669136
Ref: Library<48>-Footnote-3664669203
Ref: Library<48>-Footnote-3674669270
Ref: Library<48>-Footnote-3684669337
Ref: Library<48>-Footnote-3694669404
Ref: Library<48>-Footnote-3704669471
Ref: Library<48>-Footnote-3714669538
Ref: Library<48>-Footnote-3724669605
Ref: Library<48>-Footnote-3734669672
Ref: Library<48>-Footnote-3744669739
Ref: Library<48>-Footnote-3754669806
Ref: Library<48>-Footnote-3764669873
Ref: Library<48>-Footnote-3774669940
Ref: Library<48>-Footnote-3784670007
Ref: Library<48>-Footnote-3794670074
Ref: Library<48>-Footnote-3804670141
Ref: Library<48>-Footnote-3814670208
Ref: Library<48>-Footnote-3824670275
Ref: Library<48>-Footnote-3834670342
Ref: Library<48>-Footnote-3844670409
Ref: Library<48>-Footnote-3854670476
Ref: Library<48>-Footnote-3864670543
Ref: Library<48>-Footnote-3874670610
Ref: Library<48>-Footnote-3884670677
Ref: Library<48>-Footnote-3894670744
Ref: Library<48>-Footnote-3904670811
Ref: Library<48>-Footnote-3914670878
Ref: Library<48>-Footnote-3924670945
Ref: Library<48>-Footnote-3934671012
Ref: Library<48>-Footnote-3944671079
Ref: Library<48>-Footnote-3954671146
Ref: Library<48>-Footnote-3964671213
Ref: Library<48>-Footnote-3974671280
Ref: Library<48>-Footnote-3984671347
Ref: Library<48>-Footnote-3994671414
Ref: Library<48>-Footnote-4004671481
Ref: Library<48>-Footnote-4014671548
Ref: Library<48>-Footnote-4024671615
Ref: Library<48>-Footnote-4034671682
Ref: Library<48>-Footnote-4044671749
Ref: Library<48>-Footnote-4054671816
Ref: Library<48>-Footnote-4064671883
Ref: Library<48>-Footnote-4074671950
Ref: Library<48>-Footnote-4084672017
Ref: Library<48>-Footnote-4094672084
Ref: Library<48>-Footnote-4104672151
Ref: Library<48>-Footnote-4114672218
Ref: Library<48>-Footnote-4124672285
Ref: Library<48>-Footnote-4134672352
Ref: Library<48>-Footnote-4144672419
Ref: Library<48>-Footnote-4154672486
Ref: Library<48>-Footnote-4164672553
Ref: Library<48>-Footnote-4174672620
Ref: Library<48>-Footnote-4184672687
Ref: Library<48>-Footnote-4194672754
Ref: Library<48>-Footnote-4204672821
Ref: Library<48>-Footnote-4214672888
Ref: Library<48>-Footnote-4224672955
Ref: Library<48>-Footnote-4234673021
Ref: Library<48>-Footnote-4244673088
Ref: Library<48>-Footnote-4254673155
Ref: Library<48>-Footnote-4264673222
Ref: Library<48>-Footnote-4274673289
Ref: Library<48>-Footnote-4284673356
Ref: Library<48>-Footnote-4294673423
Ref: Library<48>-Footnote-4304673490
Ref: Library<48>-Footnote-4314673557
Ref: Library<48>-Footnote-4324673624
Ref: Library<48>-Footnote-4334673691
Ref: Library<48>-Footnote-4344673758
Ref: Library<48>-Footnote-4354673825
Ref: Library<48>-Footnote-4364673892
Ref: Library<48>-Footnote-4374673959
Node: Documentation<43>4674026
Ref: whatsnew/changelog id4304674138
Ref: 194e4674138
Ref: Documentation<43>-Footnote-14680819
Ref: Documentation<43>-Footnote-24680884
Ref: Documentation<43>-Footnote-34680949
Ref: Documentation<43>-Footnote-44681014
Ref: Documentation<43>-Footnote-54681079
Ref: Documentation<43>-Footnote-64681144
Ref: Documentation<43>-Footnote-74681209
Ref: Documentation<43>-Footnote-84681274
Ref: Documentation<43>-Footnote-94681339
Ref: Documentation<43>-Footnote-104681404
Ref: Documentation<43>-Footnote-114681470
Ref: Documentation<43>-Footnote-124681536
Ref: Documentation<43>-Footnote-134681602
Ref: Documentation<43>-Footnote-144681668
Ref: Documentation<43>-Footnote-154681734
Ref: Documentation<43>-Footnote-164681800
Ref: Documentation<43>-Footnote-174681866
Ref: Documentation<43>-Footnote-184681932
Ref: Documentation<43>-Footnote-194681998
Ref: Documentation<43>-Footnote-204682064
Ref: Documentation<43>-Footnote-214682130
Ref: Documentation<43>-Footnote-224682196
Ref: Documentation<43>-Footnote-234682262
Ref: Documentation<43>-Footnote-244682305
Ref: Documentation<43>-Footnote-254682371
Ref: Documentation<43>-Footnote-264682437
Ref: Documentation<43>-Footnote-274682503
Ref: Documentation<43>-Footnote-284682569
Ref: Documentation<43>-Footnote-294682635
Ref: Documentation<43>-Footnote-304682678
Ref: Documentation<43>-Footnote-314682744
Ref: Documentation<43>-Footnote-324682810
Ref: Documentation<43>-Footnote-334682876
Ref: Documentation<43>-Footnote-344682942
Ref: Documentation<43>-Footnote-354683008
Ref: Documentation<43>-Footnote-364683074
Ref: Documentation<43>-Footnote-374683140
Ref: Documentation<43>-Footnote-384683206
Ref: Documentation<43>-Footnote-394683272
Ref: Documentation<43>-Footnote-404683338
Ref: Documentation<43>-Footnote-414683404
Ref: Documentation<43>-Footnote-424683470
Ref: Documentation<43>-Footnote-434683536
Ref: Documentation<43>-Footnote-444683602
Ref: Documentation<43>-Footnote-454683668
Ref: Documentation<43>-Footnote-464683734
Ref: Documentation<43>-Footnote-474683800
Ref: Documentation<43>-Footnote-484683866
Ref: Documentation<43>-Footnote-494683932
Ref: Documentation<43>-Footnote-504683998
Ref: Documentation<43>-Footnote-514684063
Ref: Documentation<43>-Footnote-524684129
Ref: Documentation<43>-Footnote-534684195
Ref: Documentation<43>-Footnote-544684261
Ref: Documentation<43>-Footnote-554684327
Ref: Documentation<43>-Footnote-564684393
Ref: Documentation<43>-Footnote-574684458
Ref: Documentation<43>-Footnote-584684524
Ref: Documentation<43>-Footnote-594684590
Node: Tests<45>4684656
Ref: whatsnew/changelog id4314684766
Ref: 19504684766
Ref: Tests<45>-Footnote-14692357
Ref: Tests<45>-Footnote-24692422
Ref: Tests<45>-Footnote-34692487
Ref: Tests<45>-Footnote-44692552
Ref: Tests<45>-Footnote-54692617
Ref: Tests<45>-Footnote-64692682
Ref: Tests<45>-Footnote-74692747
Ref: Tests<45>-Footnote-84692812
Ref: Tests<45>-Footnote-94692877
Ref: Tests<45>-Footnote-104692942
Ref: Tests<45>-Footnote-114693008
Ref: Tests<45>-Footnote-124693074
Ref: Tests<45>-Footnote-134693140
Ref: Tests<45>-Footnote-144693206
Ref: Tests<45>-Footnote-154693272
Ref: Tests<45>-Footnote-164693338
Ref: Tests<45>-Footnote-174693404
Ref: Tests<45>-Footnote-184693470
Ref: Tests<45>-Footnote-194693536
Ref: Tests<45>-Footnote-204693602
Ref: Tests<45>-Footnote-214693668
Ref: Tests<45>-Footnote-224693734
Ref: Tests<45>-Footnote-234693800
Ref: Tests<45>-Footnote-244693866
Ref: Tests<45>-Footnote-254693932
Ref: Tests<45>-Footnote-264693998
Ref: Tests<45>-Footnote-274694064
Ref: Tests<45>-Footnote-284694130
Ref: Tests<45>-Footnote-294694196
Ref: Tests<45>-Footnote-304694262
Ref: Tests<45>-Footnote-314694328
Ref: Tests<45>-Footnote-324694394
Ref: Tests<45>-Footnote-334694460
Ref: Tests<45>-Footnote-344694526
Ref: Tests<45>-Footnote-354694592
Ref: Tests<45>-Footnote-364694658
Ref: Tests<45>-Footnote-374694724
Ref: Tests<45>-Footnote-384694790
Ref: Tests<45>-Footnote-394694856
Ref: Tests<45>-Footnote-404694922
Ref: Tests<45>-Footnote-414694988
Ref: Tests<45>-Footnote-424695054
Ref: Tests<45>-Footnote-434695120
Ref: Tests<45>-Footnote-444695186
Ref: Tests<45>-Footnote-454695252
Ref: Tests<45>-Footnote-464695318
Ref: Tests<45>-Footnote-474695384
Ref: Tests<45>-Footnote-484695450
Node: Build<47>4695516
Ref: whatsnew/changelog id4324695620
Ref: 19514695620
Ref: Build<47>-Footnote-14700723
Ref: Build<47>-Footnote-24700788
Ref: Build<47>-Footnote-34700853
Ref: Build<47>-Footnote-44700918
Ref: Build<47>-Footnote-54700983
Ref: Build<47>-Footnote-64701048
Ref: Build<47>-Footnote-74701113
Ref: Build<47>-Footnote-84701178
Ref: Build<47>-Footnote-94701243
Ref: Build<47>-Footnote-104701308
Ref: Build<47>-Footnote-114701374
Ref: Build<47>-Footnote-124701440
Ref: Build<47>-Footnote-134701506
Ref: Build<47>-Footnote-144701572
Ref: Build<47>-Footnote-154701638
Ref: Build<47>-Footnote-164701704
Ref: Build<47>-Footnote-174701770
Ref: Build<47>-Footnote-184701836
Ref: Build<47>-Footnote-194701902
Ref: Build<47>-Footnote-204701968
Ref: Build<47>-Footnote-214702034
Ref: Build<47>-Footnote-224702100
Ref: Build<47>-Footnote-234702166
Ref: Build<47>-Footnote-244702231
Ref: Build<47>-Footnote-254702297
Ref: Build<47>-Footnote-264702363
Ref: Build<47>-Footnote-274702429
Ref: Build<47>-Footnote-284702495
Ref: Build<47>-Footnote-294702561
Ref: Build<47>-Footnote-304702627
Ref: Build<47>-Footnote-314702693
Ref: Build<47>-Footnote-324702759
Ref: Build<47>-Footnote-334702825
Ref: Build<47>-Footnote-344702891
Ref: Build<47>-Footnote-354702957
Ref: Build<47>-Footnote-364703023
Ref: Build<47>-Footnote-374703089
Node: Windows<43>4703155
Ref: whatsnew/changelog id4334703259
Ref: 19524703259
Ref: Windows<43>-Footnote-14707668
Ref: Windows<43>-Footnote-24707733
Ref: Windows<43>-Footnote-34707798
Ref: Windows<43>-Footnote-44707863
Ref: Windows<43>-Footnote-54707928
Ref: Windows<43>-Footnote-64707993
Ref: Windows<43>-Footnote-74708058
Ref: Windows<43>-Footnote-84708123
Ref: Windows<43>-Footnote-94708188
Ref: Windows<43>-Footnote-104708253
Ref: Windows<43>-Footnote-114708319
Ref: Windows<43>-Footnote-124708385
Ref: Windows<43>-Footnote-134708451
Ref: Windows<43>-Footnote-144708517
Ref: Windows<43>-Footnote-154708583
Ref: Windows<43>-Footnote-164708649
Ref: Windows<43>-Footnote-174708715
Ref: Windows<43>-Footnote-184708781
Ref: Windows<43>-Footnote-194708847
Ref: Windows<43>-Footnote-204708913
Ref: Windows<43>-Footnote-214708979
Ref: Windows<43>-Footnote-224709045
Ref: Windows<43>-Footnote-234709111
Ref: Windows<43>-Footnote-244709177
Ref: Windows<43>-Footnote-254709243
Ref: Windows<43>-Footnote-264709309
Ref: Windows<43>-Footnote-274709375
Ref: Windows<43>-Footnote-284709441
Ref: Windows<43>-Footnote-294709507
Ref: Windows<43>-Footnote-304709573
Ref: Windows<43>-Footnote-314709639
Ref: Windows<43>-Footnote-324709705
Ref: Windows<43>-Footnote-334709771
Ref: Windows<43>-Footnote-344709837
Ref: Windows<43>-Footnote-354709903
Ref: Windows<43>-Footnote-364709969
Ref: Windows<43>-Footnote-374710035
Ref: Windows<43>-Footnote-384710101
Ref: Windows<43>-Footnote-394710167
Ref: Windows<43>-Footnote-404710233
Node: macOS<35>4710298
Ref: whatsnew/changelog id4344710401
Ref: 19534710401
Ref: macOS<35>-Footnote-14712006
Ref: macOS<35>-Footnote-24712071
Ref: macOS<35>-Footnote-34712136
Ref: macOS<35>-Footnote-44712201
Ref: macOS<35>-Footnote-54712266
Ref: macOS<35>-Footnote-64712331
Ref: macOS<35>-Footnote-74712396
Ref: macOS<35>-Footnote-84712461
Ref: macOS<35>-Footnote-94712526
Ref: macOS<35>-Footnote-104712591
Node: IDLE<35>4712657
Ref: whatsnew/changelog id4354712764
Ref: 19544712764
Ref: IDLE<35>-Footnote-14721126
Ref: IDLE<35>-Footnote-24721191
Ref: IDLE<35>-Footnote-34721256
Ref: IDLE<35>-Footnote-44721321
Ref: IDLE<35>-Footnote-54721386
Ref: IDLE<35>-Footnote-64721451
Ref: IDLE<35>-Footnote-74721516
Ref: IDLE<35>-Footnote-84721581
Ref: IDLE<35>-Footnote-94721646
Ref: IDLE<35>-Footnote-104721711
Ref: IDLE<35>-Footnote-114721777
Ref: IDLE<35>-Footnote-124721843
Ref: IDLE<35>-Footnote-134721909
Ref: IDLE<35>-Footnote-144721975
Ref: IDLE<35>-Footnote-154722041
Ref: IDLE<35>-Footnote-164722107
Ref: IDLE<35>-Footnote-174722173
Ref: IDLE<35>-Footnote-184722239
Ref: IDLE<35>-Footnote-194722305
Ref: IDLE<35>-Footnote-204722371
Ref: IDLE<35>-Footnote-214722437
Ref: IDLE<35>-Footnote-224722503
Ref: IDLE<35>-Footnote-234722569
Ref: IDLE<35>-Footnote-244722635
Ref: IDLE<35>-Footnote-254722701
Ref: IDLE<35>-Footnote-264722767
Ref: IDLE<35>-Footnote-274722833
Ref: IDLE<35>-Footnote-284722901
Ref: IDLE<35>-Footnote-294722967
Ref: IDLE<35>-Footnote-304723033
Ref: IDLE<35>-Footnote-314723099
Ref: IDLE<35>-Footnote-324723165
Ref: IDLE<35>-Footnote-334723231
Ref: IDLE<35>-Footnote-344723297
Ref: IDLE<35>-Footnote-354723363
Ref: IDLE<35>-Footnote-364723429
Ref: IDLE<35>-Footnote-374723495
Ref: IDLE<35>-Footnote-384723561
Ref: IDLE<35>-Footnote-394723627
Ref: IDLE<35>-Footnote-404723693
Ref: IDLE<35>-Footnote-414723759
Ref: IDLE<35>-Footnote-424723825
Ref: IDLE<35>-Footnote-434723891
Ref: IDLE<35>-Footnote-444723957
Ref: IDLE<35>-Footnote-454724023
Ref: IDLE<35>-Footnote-464724089
Ref: IDLE<35>-Footnote-474724155
Ref: IDLE<35>-Footnote-484724221
Ref: IDLE<35>-Footnote-494724287
Ref: IDLE<35>-Footnote-504724353
Ref: IDLE<35>-Footnote-514724419
Ref: IDLE<35>-Footnote-524724485
Ref: IDLE<35>-Footnote-534724551
Ref: IDLE<35>-Footnote-544724617
Ref: IDLE<35>-Footnote-554724683
Ref: IDLE<35>-Footnote-564724749
Ref: IDLE<35>-Footnote-574724815
Ref: IDLE<35>-Footnote-584724881
Ref: IDLE<35>-Footnote-594724947
Node: Tools/Demos<23>4725013
Ref: whatsnew/changelog id4364725120
Ref: 19554725120
Ref: Tools/Demos<23>-Footnote-14726765
Ref: Tools/Demos<23>-Footnote-24726830
Ref: Tools/Demos<23>-Footnote-34726895
Ref: Tools/Demos<23>-Footnote-44726960
Ref: Tools/Demos<23>-Footnote-54727025
Ref: Tools/Demos<23>-Footnote-64727090
Ref: Tools/Demos<23>-Footnote-74727155
Ref: Tools/Demos<23>-Footnote-84727220
Ref: Tools/Demos<23>-Footnote-94727285
Ref: Tools/Demos<23>-Footnote-104727350
Ref: Tools/Demos<23>-Footnote-114727416
Ref: Tools/Demos<23>-Footnote-124727482
Node: C API<46>4727548
Ref: whatsnew/changelog id4374727638
Ref: 19564727638
Ref: C API<46>-Footnote-14731026
Ref: C API<46>-Footnote-24731091
Ref: C API<46>-Footnote-34731156
Ref: C API<46>-Footnote-44731221
Ref: C API<46>-Footnote-54731286
Ref: C API<46>-Footnote-64731351
Ref: C API<46>-Footnote-74731416
Ref: C API<46>-Footnote-84731481
Ref: C API<46>-Footnote-94731546
Ref: C API<46>-Footnote-104731611
Ref: C API<46>-Footnote-114731677
Ref: C API<46>-Footnote-124731743
Ref: C API<46>-Footnote-134731809
Ref: C API<46>-Footnote-144731875
Ref: C API<46>-Footnote-154731941
Ref: C API<46>-Footnote-164732007
Ref: C API<46>-Footnote-174732073
Ref: C API<46>-Footnote-184732139
Ref: C API<46>-Footnote-194732205
Ref: C API<46>-Footnote-204732271
Ref: C API<46>-Footnote-214732337
Ref: C API<46>-Footnote-224732403
Node: Python 3 7 0 final4732469
Ref: whatsnew/changelog python-3-7-0-final4732621
Ref: 195e4732621
Node: Library<49>4732758
Ref: whatsnew/changelog id4384732842
Ref: 195f4732842
Ref: Library<49>-Footnote-14733012
Node: C API<47>4733077
Ref: whatsnew/changelog id4394733161
Ref: 19614733161
Ref: C API<47>-Footnote-14733372
Node: Python 3 7 0 release candidate 14733437
Ref: whatsnew/changelog python-3-7-0-release-candidate-14733588
Ref: 19624733588
Node: Core and Builtins<50>4733875
Ref: whatsnew/changelog id4404733985
Ref: 19634733985
Ref: Core and Builtins<50>-Footnote-14734627
Ref: Core and Builtins<50>-Footnote-24734692
Ref: Core and Builtins<50>-Footnote-34734757
Ref: Core and Builtins<50>-Footnote-44734822
Node: Library<50>4734887
Ref: whatsnew/changelog id4414735023
Ref: 19644735023
Ref: Library<50>-Footnote-14736719
Ref: Library<50>-Footnote-24736784
Ref: Library<50>-Footnote-34736849
Ref: Library<50>-Footnote-44736914
Ref: Library<50>-Footnote-54736979
Ref: Library<50>-Footnote-64737044
Ref: Library<50>-Footnote-74737109
Ref: Library<50>-Footnote-84737174
Ref: Library<50>-Footnote-94737239
Ref: Library<50>-Footnote-104737304
Ref: Library<50>-Footnote-114737370
Ref: Library<50>-Footnote-124737436
Ref: Library<50>-Footnote-134737502
Node: Documentation<44>4737568
Ref: whatsnew/changelog id4424737692
Ref: 19654737692
Ref: Documentation<44>-Footnote-14738195
Ref: Documentation<44>-Footnote-24738260
Ref: Documentation<44>-Footnote-34738302
Ref: Documentation<44>-Footnote-44738367
Node: Build<48>4738432
Ref: whatsnew/changelog id4434738556
Ref: 19664738556
Ref: Build<48>-Footnote-14738818
Node: Windows<44>4738882
Ref: whatsnew/changelog id4444738997
Ref: 19674738997
Ref: Windows<44>-Footnote-14739154
Node: IDLE<36>4739219
Ref: whatsnew/changelog id4454739316
Ref: 19684739316
Ref: IDLE<36>-Footnote-14740536
Ref: IDLE<36>-Footnote-24740601
Ref: IDLE<36>-Footnote-34740666
Ref: IDLE<36>-Footnote-44740731
Ref: IDLE<36>-Footnote-54740796
Ref: IDLE<36>-Footnote-64740861
Node: Python 3 7 0 beta 54740926
Ref: whatsnew/changelog python-3-7-0-beta-54741078
Ref: 19694741078
Node: Core and Builtins<51>4741355
Ref: whatsnew/changelog id4464741452
Ref: 196a4741452
Ref: Core and Builtins<51>-Footnote-14742964
Ref: Core and Builtins<51>-Footnote-24743029
Ref: Core and Builtins<51>-Footnote-34743094
Ref: Core and Builtins<51>-Footnote-44743159
Ref: Core and Builtins<51>-Footnote-54743224
Ref: Core and Builtins<51>-Footnote-64743289
Ref: Core and Builtins<51>-Footnote-74743354
Ref: Core and Builtins<51>-Footnote-84743419
Ref: Core and Builtins<51>-Footnote-94743484
Node: Library<51>4743549
Ref: whatsnew/changelog id4474743672
Ref: 196b4743672
Ref: Library<51>-Footnote-14749264
Ref: Library<51>-Footnote-24749329
Ref: Library<51>-Footnote-34749394
Ref: Library<51>-Footnote-44749459
Ref: Library<51>-Footnote-54749524
Ref: Library<51>-Footnote-64749589
Ref: Library<51>-Footnote-74749654
Ref: Library<51>-Footnote-84749719
Ref: Library<51>-Footnote-94749784
Ref: Library<51>-Footnote-104749849
Ref: Library<51>-Footnote-114749915
Ref: Library<51>-Footnote-124749981
Ref: Library<51>-Footnote-134750047
Ref: Library<51>-Footnote-144750113
Ref: Library<51>-Footnote-154750179
Ref: Library<51>-Footnote-164750245
Ref: Library<51>-Footnote-174750311
Ref: Library<51>-Footnote-184750377
Ref: Library<51>-Footnote-194750443
Ref: Library<51>-Footnote-204750509
Ref: Library<51>-Footnote-214750575
Ref: Library<51>-Footnote-224750641
Ref: Library<51>-Footnote-234750707
Ref: Library<51>-Footnote-244750773
Ref: Library<51>-Footnote-254750839
Ref: Library<51>-Footnote-264750905
Ref: Library<51>-Footnote-274750971
Ref: Library<51>-Footnote-284751037
Ref: Library<51>-Footnote-294751103
Ref: Library<51>-Footnote-304751169
Ref: Library<51>-Footnote-314751235
Ref: Library<51>-Footnote-324751301
Ref: Library<51>-Footnote-334751367
Ref: Library<51>-Footnote-344751433
Ref: Library<51>-Footnote-354751499
Ref: Library<51>-Footnote-364751565
Ref: Library<51>-Footnote-374751631
Ref: Library<51>-Footnote-384751697
Node: Documentation<45>4751763
Ref: whatsnew/changelog id4484751874
Ref: 196c4751874
Ref: Documentation<45>-Footnote-14752344
Ref: Documentation<45>-Footnote-24752409
Ref: Documentation<45>-Footnote-34752474
Ref: Documentation<45>-Footnote-44752516
Ref: Documentation<45>-Footnote-54752581
Ref: Documentation<45>-Footnote-64752646
Node: Tests<46>4752711
Ref: whatsnew/changelog id4494752820
Ref: 196d4752820
Ref: Tests<46>-Footnote-14753169
Ref: Tests<46>-Footnote-24753234
Node: Build<49>4753299
Ref: whatsnew/changelog id4504753400
Ref: 196e4753400
Ref: Build<49>-Footnote-14753879
Ref: Build<49>-Footnote-24753944
Ref: Build<49>-Footnote-34754009
Node: macOS<36>4754074
Ref: whatsnew/changelog id4514754174
Ref: 196f4754174
Ref: macOS<36>-Footnote-14754414
Node: IDLE<37>4754479
Ref: whatsnew/changelog id4524754561
Ref: 19704754561
Ref: IDLE<37>-Footnote-14754838
Ref: IDLE<37>-Footnote-24754903
Ref: IDLE<37>-Footnote-34754968
Node: Python 3 7 0 beta 44755033
Ref: whatsnew/changelog python-3-7-0-beta-44755172
Ref: 19714755172
Node: Core and Builtins<52>4755505
Ref: whatsnew/changelog id4534755602
Ref: 19724755602
Ref: Core and Builtins<52>-Footnote-14756732
Ref: Core and Builtins<52>-Footnote-24756797
Ref: Core and Builtins<52>-Footnote-34756862
Ref: Core and Builtins<52>-Footnote-44756927
Ref: Core and Builtins<52>-Footnote-54756992
Ref: Core and Builtins<52>-Footnote-64757057
Ref: Core and Builtins<52>-Footnote-74757122
Node: Library<52>4757187
Ref: whatsnew/changelog id4544757310
Ref: 19734757310
Ref: Library<52>-Footnote-14760147
Ref: Library<52>-Footnote-24760212
Ref: Library<52>-Footnote-34760277
Ref: Library<52>-Footnote-44760342
Ref: Library<52>-Footnote-54760408
Ref: Library<52>-Footnote-64760473
Ref: Library<52>-Footnote-74760538
Ref: Library<52>-Footnote-84760603
Ref: Library<52>-Footnote-94760668
Ref: Library<52>-Footnote-104760733
Ref: Library<52>-Footnote-114760799
Ref: Library<52>-Footnote-124760865
Ref: Library<52>-Footnote-134760931
Ref: Library<52>-Footnote-144760997
Ref: Library<52>-Footnote-154761063
Ref: Library<52>-Footnote-164761129
Ref: Library<52>-Footnote-174761195
Ref: Library<52>-Footnote-184761238
Ref: Library<52>-Footnote-194761304
Ref: Library<52>-Footnote-204761370
Ref: Library<52>-Footnote-214761436
Ref: Library<52>-Footnote-224761502
Node: Documentation<46>4761568
Ref: whatsnew/changelog id4554761679
Ref: 19744761679
Ref: Documentation<46>-Footnote-14762430
Ref: Documentation<46>-Footnote-24762495
Ref: Documentation<46>-Footnote-34762560
Ref: Documentation<46>-Footnote-44762625
Ref: Documentation<46>-Footnote-54762690
Ref: Documentation<46>-Footnote-64762754
Node: Tests<47>4762819
Ref: whatsnew/changelog id4564762928
Ref: 19754762928
Ref: Tests<47>-Footnote-14763144
Node: Build<50>4763209
Ref: whatsnew/changelog id4574763312
Ref: 19764763312
Ref: Build<50>-Footnote-14764002
Ref: Build<50>-Footnote-24764067
Ref: Build<50>-Footnote-34764132
Ref: Build<50>-Footnote-44764197
Ref: Build<50>-Footnote-54764262
Node: Windows<45>4764327
Ref: whatsnew/changelog id4584764430
Ref: 19774764430
Ref: Windows<45>-Footnote-14764571
Node: macOS<37>4764636
Ref: whatsnew/changelog id4594764738
Ref: 19784764738
Ref: macOS<37>-Footnote-14764879
Node: IDLE<38>4764944
Ref: whatsnew/changelog id4604765050
Ref: 19794765050
Ref: IDLE<38>-Footnote-14765628
Ref: IDLE<38>-Footnote-24765693
Node: Tools/Demos<24>4765758
Ref: whatsnew/changelog id4614765846
Ref: 197a4765846
Ref: Tools/Demos<24>-Footnote-14766450
Ref: Tools/Demos<24>-Footnote-24766515
Ref: Tools/Demos<24>-Footnote-34766580
Ref: Tools/Demos<24>-Footnote-44766645
Node: Python 3 7 0 beta 34766710
Ref: whatsnew/changelog python-3-7-0-beta-34766849
Ref: 197b4766849
Node: Security<34>4767228
Ref: whatsnew/changelog id4624767326
Ref: 197c4767326
Ref: Security<34>-Footnote-14767958
Ref: Security<34>-Footnote-24768023
Ref: Security<34>-Footnote-34768092
Ref: Security<34>-Footnote-44768157
Ref: Security<34>-Footnote-54768222
Ref: Security<34>-Footnote-64768291
Node: Core and Builtins<53>4768360
Ref: whatsnew/changelog id4634768478
Ref: 197d4768478
Ref: Core and Builtins<53>-Footnote-14769674
Ref: Core and Builtins<53>-Footnote-24769739
Ref: Core and Builtins<53>-Footnote-34769804
Ref: Core and Builtins<53>-Footnote-44769869
Ref: Core and Builtins<53>-Footnote-54769934
Ref: Core and Builtins<53>-Footnote-64769999
Ref: Core and Builtins<53>-Footnote-74770064
Node: Library<53>4770129
Ref: whatsnew/changelog id4644770252
Ref: 197e4770252
Ref: Library<53>-Footnote-14774294
Ref: Library<53>-Footnote-24774359
Ref: Library<53>-Footnote-34774424
Ref: Library<53>-Footnote-44774489
Ref: Library<53>-Footnote-54774554
Ref: Library<53>-Footnote-64774619
Ref: Library<53>-Footnote-74774684
Ref: Library<53>-Footnote-84774749
Ref: Library<53>-Footnote-94774814
Ref: Library<53>-Footnote-104774879
Ref: Library<53>-Footnote-114774945
Ref: Library<53>-Footnote-124775011
Ref: Library<53>-Footnote-134775077
Ref: Library<53>-Footnote-144775143
Ref: Library<53>-Footnote-154775209
Ref: Library<53>-Footnote-164775275
Ref: Library<53>-Footnote-174775341
Ref: Library<53>-Footnote-184775407
Ref: Library<53>-Footnote-194775473
Ref: Library<53>-Footnote-204775539
Ref: Library<53>-Footnote-214775605
Ref: Library<53>-Footnote-224775671
Ref: Library<53>-Footnote-234775737
Ref: Library<53>-Footnote-244775803
Ref: Library<53>-Footnote-254775869
Ref: Library<53>-Footnote-264775935
Ref: Library<53>-Footnote-274776001
Node: Documentation<47>4776067
Ref: whatsnew/changelog id4654776178
Ref: 197f4776178
Ref: Documentation<47>-Footnote-14776815
Ref: Documentation<47>-Footnote-24776880
Ref: Documentation<47>-Footnote-34776945
Ref: Documentation<47>-Footnote-44777010
Ref: Documentation<47>-Footnote-54777075
Node: Tests<48>4777140
Ref: whatsnew/changelog id4664777249
Ref: 19804777249
Ref: Tests<48>-Footnote-14777582
Ref: Tests<48>-Footnote-24777647
Ref: Tests<48>-Footnote-34777712
Node: Build<51>4777777
Ref: whatsnew/changelog id4674777880
Ref: 19814777880
Ref: Build<51>-Footnote-14778017
Node: Windows<46>4778082
Ref: whatsnew/changelog id4684778185
Ref: 19824778185
Ref: Windows<46>-Footnote-14778464
Ref: Windows<46>-Footnote-24778529
Node: macOS<38>4778594
Ref: whatsnew/changelog id4694778696
Ref: 19834778696
Ref: macOS<38>-Footnote-14779128
Node: IDLE<39>4779193
Ref: whatsnew/changelog id4704779299
Ref: 19844779299
Ref: IDLE<39>-Footnote-14780013
Ref: IDLE<39>-Footnote-24780078
Node: Tools/Demos<25>4780143
Ref: whatsnew/changelog id4714780249
Ref: 19854780249
Ref: Tools/Demos<25>-Footnote-14780479
Node: C API<48>4780544
Ref: whatsnew/changelog id4724780633
Ref: 19864780633
Ref: C API<48>-Footnote-14781017
Ref: C API<48>-Footnote-24781082
Node: Python 3 7 0 beta 24781147
Ref: whatsnew/changelog python-3-7-0-beta-24781286
Ref: 19874781286
Node: Security<35>4781645
Ref: whatsnew/changelog id4734781743
Ref: 19884781743
Ref: Security<35>-Footnote-14781928
Node: Core and Builtins<54>4781993
Ref: whatsnew/changelog id4744782111
Ref: 19894782111
Ref: Core and Builtins<54>-Footnote-14782942
Ref: Core and Builtins<54>-Footnote-24783007
Ref: Core and Builtins<54>-Footnote-34783072
Ref: Core and Builtins<54>-Footnote-44783137
Ref: Core and Builtins<54>-Footnote-54783202
Ref: Core and Builtins<54>-Footnote-64783267
Ref: Core and Builtins<54>-Footnote-74783332
Node: Library<54>4783397
Ref: whatsnew/changelog id4754783520
Ref: 198a4783520
Ref: Library<54>-Footnote-14789915
Ref: Library<54>-Footnote-24789980
Ref: Library<54>-Footnote-34790045
Ref: Library<54>-Footnote-44790110
Ref: Library<54>-Footnote-54790175
Ref: Library<54>-Footnote-64790240
Ref: Library<54>-Footnote-74790305
Ref: Library<54>-Footnote-84790370
Ref: Library<54>-Footnote-94790435
Ref: Library<54>-Footnote-104790500
Ref: Library<54>-Footnote-114790566
Ref: Library<54>-Footnote-124790632
Ref: Library<54>-Footnote-134790698
Ref: Library<54>-Footnote-144790764
Ref: Library<54>-Footnote-154790830
Ref: Library<54>-Footnote-164790896
Ref: Library<54>-Footnote-174790962
Ref: Library<54>-Footnote-184791028
Ref: Library<54>-Footnote-194791094
Ref: Library<54>-Footnote-204791160
Ref: Library<54>-Footnote-214791226
Ref: Library<54>-Footnote-224791292
Ref: Library<54>-Footnote-234791358
Ref: Library<54>-Footnote-244791424
Ref: Library<54>-Footnote-254791490
Ref: Library<54>-Footnote-264791556
Ref: Library<54>-Footnote-274791622
Ref: Library<54>-Footnote-284791688
Ref: Library<54>-Footnote-294791754
Ref: Library<54>-Footnote-304791820
Ref: Library<54>-Footnote-314791886
Ref: Library<54>-Footnote-324791952
Ref: Library<54>-Footnote-334792018
Ref: Library<54>-Footnote-344792084
Node: Documentation<48>4792150
Ref: whatsnew/changelog id4764792261
Ref: 198b4792261
Ref: Documentation<48>-Footnote-14793212
Ref: Documentation<48>-Footnote-24793277
Ref: Documentation<48>-Footnote-34793342
Ref: Documentation<48>-Footnote-44793407
Ref: Documentation<48>-Footnote-54793472
Ref: Documentation<48>-Footnote-64793537
Ref: Documentation<48>-Footnote-74793601
Ref: Documentation<48>-Footnote-84793666
Node: Tests<49>4793731
Ref: whatsnew/changelog id4774793840
Ref: 198c4793840
Ref: Tests<49>-Footnote-14793983
Node: Build<52>4794048
Ref: whatsnew/changelog id4784794151
Ref: 198d4794151
Ref: Build<52>-Footnote-14794292
Node: Windows<47>4794357
Ref: whatsnew/changelog id4794794460
Ref: 198e4794460
Ref: Windows<47>-Footnote-14795196
Ref: Windows<47>-Footnote-24795261
Ref: Windows<47>-Footnote-34795326
Ref: Windows<47>-Footnote-44795391
Ref: Windows<47>-Footnote-54795456
Ref: Windows<47>-Footnote-64795521
Node: macOS<39>4795586
Ref: whatsnew/changelog id4804795688
Ref: 198f4795688
Ref: macOS<39>-Footnote-14795823
Node: IDLE<40>4795888
Ref: whatsnew/changelog id4814795994
Ref: 19904795994
Ref: IDLE<40>-Footnote-14796829
Ref: IDLE<40>-Footnote-24796894
Ref: IDLE<40>-Footnote-34796959
Ref: IDLE<40>-Footnote-44797024
Ref: IDLE<40>-Footnote-54797089
Ref: IDLE<40>-Footnote-64797154
Node: Tools/Demos<26>4797219
Ref: whatsnew/changelog id4824797307
Ref: 19914797307
Ref: Tools/Demos<26>-Footnote-14797526
Node: Python 3 7 0 beta 14797591
Ref: whatsnew/changelog python-3-7-0-beta-14797731
Ref: 19924797731
Node: Core and Builtins<55>4798034
Ref: whatsnew/changelog id4834798131
Ref: 19934798131
Ref: Core and Builtins<55>-Footnote-14801545
Ref: Core and Builtins<55>-Footnote-24801610
Ref: Core and Builtins<55>-Footnote-34801675
Ref: Core and Builtins<55>-Footnote-44801740
Ref: Core and Builtins<55>-Footnote-54801805
Ref: Core and Builtins<55>-Footnote-64801870
Ref: Core and Builtins<55>-Footnote-74801935
Ref: Core and Builtins<55>-Footnote-84802000
Ref: Core and Builtins<55>-Footnote-94802065
Ref: Core and Builtins<55>-Footnote-104802107
Ref: Core and Builtins<55>-Footnote-114802173
Ref: Core and Builtins<55>-Footnote-124802239
Ref: Core and Builtins<55>-Footnote-134802305
Ref: Core and Builtins<55>-Footnote-144802371
Ref: Core and Builtins<55>-Footnote-154802437
Ref: Core and Builtins<55>-Footnote-164802503
Ref: Core and Builtins<55>-Footnote-174802569
Ref: Core and Builtins<55>-Footnote-184802635
Ref: Core and Builtins<55>-Footnote-194802678
Ref: Core and Builtins<55>-Footnote-204802744
Ref: Core and Builtins<55>-Footnote-214802810
Ref: Core and Builtins<55>-Footnote-224802876
Ref: Core and Builtins<55>-Footnote-234802942
Node: Library<55>4803008
Ref: whatsnew/changelog id4844803131
Ref: 19944803131
Ref: Library<55>-Footnote-14810503
Ref: Library<55>-Footnote-24810568
Ref: Library<55>-Footnote-34810633
Ref: Library<55>-Footnote-44810698
Ref: Library<55>-Footnote-54810763
Ref: Library<55>-Footnote-64810828
Ref: Library<55>-Footnote-74810893
Ref: Library<55>-Footnote-84810958
Ref: Library<55>-Footnote-94811023
Ref: Library<55>-Footnote-104811088
Ref: Library<55>-Footnote-114811154
Ref: Library<55>-Footnote-124811220
Ref: Library<55>-Footnote-134811286
Ref: Library<55>-Footnote-144811352
Ref: Library<55>-Footnote-154811418
Ref: Library<55>-Footnote-164811484
Ref: Library<55>-Footnote-174811550
Ref: Library<55>-Footnote-184811616
Ref: Library<55>-Footnote-194811659
Ref: Library<55>-Footnote-204811725
Ref: Library<55>-Footnote-214811791
Ref: Library<55>-Footnote-224811857
Ref: Library<55>-Footnote-234811923
Ref: Library<55>-Footnote-244811989
Ref: Library<55>-Footnote-254812055
Ref: Library<55>-Footnote-264812121
Ref: Library<55>-Footnote-274812187
Ref: Library<55>-Footnote-284812253
Ref: Library<55>-Footnote-294812319
Ref: Library<55>-Footnote-304812385
Ref: Library<55>-Footnote-314812451
Ref: Library<55>-Footnote-324812517
Ref: Library<55>-Footnote-334812583
Ref: Library<55>-Footnote-344812649
Ref: Library<55>-Footnote-354812715
Ref: Library<55>-Footnote-364812781
Ref: Library<55>-Footnote-374812847
Ref: Library<55>-Footnote-384812913
Ref: Library<55>-Footnote-394812979
Ref: Library<55>-Footnote-404813045
Ref: Library<55>-Footnote-414813111
Ref: Library<55>-Footnote-424813177
Ref: Library<55>-Footnote-434813243
Ref: Library<55>-Footnote-444813309
Ref: Library<55>-Footnote-454813375
Ref: Library<55>-Footnote-464813441
Ref: Library<55>-Footnote-474813507
Node: Documentation<49>4813573
Ref: whatsnew/changelog id4854813684
Ref: 19954813684
Ref: Documentation<49>-Footnote-14814225
Ref: Documentation<49>-Footnote-24814290
Ref: Documentation<49>-Footnote-34814355
Node: Tests<50>4814420
Ref: whatsnew/changelog id4864814529
Ref: 19964814529
Ref: Tests<50>-Footnote-14815437
Ref: Tests<50>-Footnote-24815502
Ref: Tests<50>-Footnote-34815567
Ref: Tests<50>-Footnote-44815632
Ref: Tests<50>-Footnote-54815697
Ref: Tests<50>-Footnote-64815762
Node: Build<53>4815827
Ref: whatsnew/changelog id4874815930
Ref: 19974815930
Ref: Build<53>-Footnote-14816533
Ref: Build<53>-Footnote-24816598
Ref: Build<53>-Footnote-34816663
Ref: Build<53>-Footnote-44816728
Node: Windows<48>4816793
Ref: whatsnew/changelog id4884816896
Ref: 19984816896
Ref: Windows<48>-Footnote-14817277
Ref: Windows<48>-Footnote-24817342
Ref: Windows<48>-Footnote-34817407
Node: macOS<40>4817472
Ref: whatsnew/changelog id4894817575
Ref: 19994817575
Ref: macOS<40>-Footnote-14818097
Ref: macOS<40>-Footnote-24818162
Node: C API<49>4818227
Ref: whatsnew/changelog id4904818310
Ref: 199a4818310
Ref: C API<49>-Footnote-14818627
Ref: C API<49>-Footnote-24818692
Node: Python 3 7 0 alpha 44818757
Ref: whatsnew/changelog python-3-7-0-alpha-44818898
Ref: 199b4818898
Node: Core and Builtins<56>4819195
Ref: whatsnew/changelog id4914819293
Ref: 199c4819293
Ref: Core and Builtins<56>-Footnote-14822794
Ref: Core and Builtins<56>-Footnote-24822859
Ref: Core and Builtins<56>-Footnote-34822924
Ref: Core and Builtins<56>-Footnote-44822989
Ref: Core and Builtins<56>-Footnote-54823054
Ref: Core and Builtins<56>-Footnote-64823119
Ref: Core and Builtins<56>-Footnote-74823184
Ref: Core and Builtins<56>-Footnote-84823249
Ref: Core and Builtins<56>-Footnote-94823314
Ref: Core and Builtins<56>-Footnote-104823379
Ref: Core and Builtins<56>-Footnote-114823445
Ref: Core and Builtins<56>-Footnote-124823511
Ref: Core and Builtins<56>-Footnote-134823577
Ref: Core and Builtins<56>-Footnote-144823643
Ref: Core and Builtins<56>-Footnote-154823709
Ref: Core and Builtins<56>-Footnote-164823775
Ref: Core and Builtins<56>-Footnote-174823841
Ref: Core and Builtins<56>-Footnote-184823907
Ref: Core and Builtins<56>-Footnote-194823973
Ref: Core and Builtins<56>-Footnote-204824016
Ref: Core and Builtins<56>-Footnote-214824082
Ref: Core and Builtins<56>-Footnote-224824125
Ref: Core and Builtins<56>-Footnote-234824191
Ref: Core and Builtins<56>-Footnote-244824234
Ref: Core and Builtins<56>-Footnote-254824300
Ref: Core and Builtins<56>-Footnote-264824366
Ref: Core and Builtins<56>-Footnote-274824409
Node: Library<56>4824475
Ref: whatsnew/changelog id4924824599
Ref: 199e4824599
Ref: Library<56>-Footnote-14832583
Ref: Library<56>-Footnote-24832648
Ref: Library<56>-Footnote-34832713
Ref: Library<56>-Footnote-44832778
Ref: Library<56>-Footnote-54832843
Ref: Library<56>-Footnote-64832908
Ref: Library<56>-Footnote-74832973
Ref: Library<56>-Footnote-84833038
Ref: Library<56>-Footnote-94833103
Ref: Library<56>-Footnote-104833168
Ref: Library<56>-Footnote-114833234
Ref: Library<56>-Footnote-124833300
Ref: Library<56>-Footnote-134833366
Ref: Library<56>-Footnote-144833432
Ref: Library<56>-Footnote-154833498
Ref: Library<56>-Footnote-164833564
Ref: Library<56>-Footnote-174833630
Ref: Library<56>-Footnote-184833696
Ref: Library<56>-Footnote-194833762
Ref: Library<56>-Footnote-204833828
Ref: Library<56>-Footnote-214833894
Ref: Library<56>-Footnote-224833960
Ref: Library<56>-Footnote-234834026
Ref: Library<56>-Footnote-244834092
Ref: Library<56>-Footnote-254834158
Ref: Library<56>-Footnote-264834224
Ref: Library<56>-Footnote-274834290
Ref: Library<56>-Footnote-284834356
Ref: Library<56>-Footnote-294834422
Ref: Library<56>-Footnote-304834488
Ref: Library<56>-Footnote-314834554
Ref: Library<56>-Footnote-324834620
Ref: Library<56>-Footnote-334834686
Ref: Library<56>-Footnote-344834752
Ref: Library<56>-Footnote-354834818
Ref: Library<56>-Footnote-364834884
Ref: Library<56>-Footnote-374834950
Ref: Library<56>-Footnote-384835016
Ref: Library<56>-Footnote-394835082
Ref: Library<56>-Footnote-404835148
Ref: Library<56>-Footnote-414835214
Ref: Library<56>-Footnote-424835280
Ref: Library<56>-Footnote-434835346
Ref: Library<56>-Footnote-444835412
Ref: Library<56>-Footnote-454835478
Ref: Library<56>-Footnote-464835544
Ref: Library<56>-Footnote-474835610
Ref: Library<56>-Footnote-484835676
Ref: Library<56>-Footnote-494835742
Ref: Library<56>-Footnote-504835808
Ref: Library<56>-Footnote-514835874
Ref: Library<56>-Footnote-524835940
Ref: Library<56>-Footnote-534836006
Ref: Library<56>-Footnote-544836072
Node: Documentation<50>4836138
Ref: whatsnew/changelog id4934836250
Ref: 199f4836250
Ref: Documentation<50>-Footnote-14836420
Node: Tests<51>4836485
Ref: whatsnew/changelog id4944836597
Ref: 19a04836597
Ref: Tests<51>-Footnote-14836992
Ref: Tests<51>-Footnote-24837057
Node: Windows<49>4837122
Ref: whatsnew/changelog id4954837232
Ref: 19a14837232
Ref: Windows<49>-Footnote-14837431
Node: Tools/Demos<27>4837496
Ref: whatsnew/changelog id4964837606
Ref: 19a24837606
Ref: Tools/Demos<27>-Footnote-14837888
Node: C API<50>4837953
Ref: whatsnew/changelog id4974838043
Ref: 19a34838043
Ref: C API<50>-Footnote-14838685
Ref: C API<50>-Footnote-24838750
Ref: C API<50>-Footnote-34838815
Ref: C API<50>-Footnote-44838880
Node: Python 3 7 0 alpha 34838945
Ref: whatsnew/changelog python-3-7-0-alpha-34839087
Ref: 19a44839087
Node: Core and Builtins<57>4839442
Ref: whatsnew/changelog id4984839540
Ref: 19a54839540
Ref: Core and Builtins<57>-Footnote-14844661
Ref: Core and Builtins<57>-Footnote-24844726
Ref: Core and Builtins<57>-Footnote-34844791
Ref: Core and Builtins<57>-Footnote-44844856
Ref: Core and Builtins<57>-Footnote-54844921
Ref: Core and Builtins<57>-Footnote-64844986
Ref: Core and Builtins<57>-Footnote-74845051
Ref: Core and Builtins<57>-Footnote-84845116
Ref: Core and Builtins<57>-Footnote-94845181
Ref: Core and Builtins<57>-Footnote-104845246
Ref: Core and Builtins<57>-Footnote-114845312
Ref: Core and Builtins<57>-Footnote-124845378
Ref: Core and Builtins<57>-Footnote-134845444
Ref: Core and Builtins<57>-Footnote-144845510
Ref: Core and Builtins<57>-Footnote-154845576
Ref: Core and Builtins<57>-Footnote-164845642
Ref: Core and Builtins<57>-Footnote-174845708
Ref: Core and Builtins<57>-Footnote-184845774
Ref: Core and Builtins<57>-Footnote-194845840
Ref: Core and Builtins<57>-Footnote-204845906
Ref: Core and Builtins<57>-Footnote-214845972
Ref: Core and Builtins<57>-Footnote-224846038
Node: Library<57>4846104
Ref: whatsnew/changelog id4994846228
Ref: 19a64846228
Ref: Library<57>-Footnote-14862238
Ref: Library<57>-Footnote-24862303
Ref: Library<57>-Footnote-34862368
Ref: Library<57>-Footnote-44862433
Ref: Library<57>-Footnote-54862498
Ref: Library<57>-Footnote-64862563
Ref: Library<57>-Footnote-74862628
Ref: Library<57>-Footnote-84862693
Ref: Library<57>-Footnote-94862758
Ref: Library<57>-Footnote-104862823
Ref: Library<57>-Footnote-114862889
Ref: Library<57>-Footnote-124862955
Ref: Library<57>-Footnote-134863021
Ref: Library<57>-Footnote-144863087
Ref: Library<57>-Footnote-154863153
Ref: Library<57>-Footnote-164863219
Ref: Library<57>-Footnote-174863285
Ref: Library<57>-Footnote-184863351
Ref: Library<57>-Footnote-194863417
Ref: Library<57>-Footnote-204863483
Ref: Library<57>-Footnote-214863549
Ref: Library<57>-Footnote-224863615
Ref: Library<57>-Footnote-234863681
Ref: Library<57>-Footnote-244863747
Ref: Library<57>-Footnote-254863813
Ref: Library<57>-Footnote-264863881
Ref: Library<57>-Footnote-274863947
Ref: Library<57>-Footnote-284864013
Ref: Library<57>-Footnote-294864079
Ref: Library<57>-Footnote-304864145
Ref: Library<57>-Footnote-314864211
Ref: Library<57>-Footnote-324864277
Ref: Library<57>-Footnote-334864320
Ref: Library<57>-Footnote-344864386
Ref: Library<57>-Footnote-354864452
Ref: Library<57>-Footnote-364864518
Ref: Library<57>-Footnote-374864584
Ref: Library<57>-Footnote-384864650
Ref: Library<57>-Footnote-394864716
Ref: Library<57>-Footnote-404864782
Ref: Library<57>-Footnote-414864848
Ref: Library<57>-Footnote-424864914
Ref: Library<57>-Footnote-434864980
Ref: Library<57>-Footnote-444865046
Ref: Library<57>-Footnote-454865112
Ref: Library<57>-Footnote-464865178
Ref: Library<57>-Footnote-474865243
Ref: Library<57>-Footnote-484865309
Ref: Library<57>-Footnote-494865375
Ref: Library<57>-Footnote-504865441
Ref: Library<57>-Footnote-514865507
Ref: Library<57>-Footnote-524865573
Ref: Library<57>-Footnote-534865639
Ref: Library<57>-Footnote-544865705
Ref: Library<57>-Footnote-554865771
Ref: Library<57>-Footnote-564865837
Ref: Library<57>-Footnote-574865903
Ref: Library<57>-Footnote-584865969
Ref: Library<57>-Footnote-594866035
Ref: Library<57>-Footnote-604866101
Ref: Library<57>-Footnote-614866167
Ref: Library<57>-Footnote-624866233
Ref: Library<57>-Footnote-634866276
Ref: Library<57>-Footnote-644866342
Ref: Library<57>-Footnote-654866408
Ref: Library<57>-Footnote-664866474
Ref: Library<57>-Footnote-674866540
Ref: Library<57>-Footnote-684866606
Ref: Library<57>-Footnote-694866672
Ref: Library<57>-Footnote-704866738
Ref: Library<57>-Footnote-714866804
Ref: Library<57>-Footnote-724866870
Ref: Library<57>-Footnote-734866936
Ref: Library<57>-Footnote-744867002
Ref: Library<57>-Footnote-754867068
Ref: Library<57>-Footnote-764867134
Ref: Library<57>-Footnote-774867200
Ref: Library<57>-Footnote-784867266
Ref: Library<57>-Footnote-794867332
Ref: Library<57>-Footnote-804867398
Ref: Library<57>-Footnote-814867464
Ref: Library<57>-Footnote-824867530
Ref: Library<57>-Footnote-834867573
Ref: Library<57>-Footnote-844867639
Ref: Library<57>-Footnote-854867705
Ref: Library<57>-Footnote-864867771
Ref: Library<57>-Footnote-874867837
Ref: Library<57>-Footnote-884867903
Ref: Library<57>-Footnote-894867969
Ref: Library<57>-Footnote-904868035
Ref: Library<57>-Footnote-914868101
Ref: Library<57>-Footnote-924868167
Ref: Library<57>-Footnote-934868233
Ref: Library<57>-Footnote-944868299
Ref: Library<57>-Footnote-954868365
Ref: Library<57>-Footnote-964868431
Ref: Library<57>-Footnote-974868497
Ref: Library<57>-Footnote-984868563
Node: Documentation<51>4868629
Ref: whatsnew/changelog id5004868741
Ref: 19ab4868741
Ref: Documentation<51>-Footnote-14868924
Node: Tests<52>4868989
Ref: whatsnew/changelog id5014869099
Ref: 19ac4869099
Ref: Tests<52>-Footnote-14870305
Ref: Tests<52>-Footnote-24870370
Ref: Tests<52>-Footnote-34870435
Ref: Tests<52>-Footnote-44870500
Ref: Tests<52>-Footnote-54870565
Ref: Tests<52>-Footnote-64870630
Ref: Tests<52>-Footnote-74870695
Node: Build<54>4870760
Ref: whatsnew/changelog id5024870864
Ref: 19ad4870864
Ref: Build<54>-Footnote-14872078
Ref: Build<54>-Footnote-24872143
Ref: Build<54>-Footnote-34872208
Ref: Build<54>-Footnote-44872273
Ref: Build<54>-Footnote-54872338
Ref: Build<54>-Footnote-64872403
Ref: Build<54>-Footnote-74872468
Ref: Build<54>-Footnote-84872533
Ref: Build<54>-Footnote-94872598
Ref: Build<54>-Footnote-104872663
Ref: Build<54>-Footnote-114872729
Ref: Build<54>-Footnote-124872795
Node: Windows<50>4872861
Ref: whatsnew/changelog id5034872965
Ref: 19ae4872965
Ref: Windows<50>-Footnote-14873498
Ref: Windows<50>-Footnote-24873562
Ref: Windows<50>-Footnote-34873627
Ref: Windows<50>-Footnote-44873692
Node: macOS<41>4873757
Ref: whatsnew/changelog id5044873860
Ref: 19af4873860
Ref: macOS<41>-Footnote-14873994
Node: IDLE<41>4874059
Ref: whatsnew/changelog id5054874166
Ref: 19b04874166
Ref: IDLE<41>-Footnote-14876247
Ref: IDLE<41>-Footnote-24876312
Ref: IDLE<41>-Footnote-34876377
Ref: IDLE<41>-Footnote-44876442
Ref: IDLE<41>-Footnote-54876507
Ref: IDLE<41>-Footnote-64876572
Ref: IDLE<41>-Footnote-74876637
Ref: IDLE<41>-Footnote-84876702
Node: Tools/Demos<28>4876767
Ref: whatsnew/changelog id5064876874
Ref: 19b14876874
Ref: Tools/Demos<28>-Footnote-14877404
Ref: Tools/Demos<28>-Footnote-24877469
Node: C API<51>4877534
Ref: whatsnew/changelog id5074877624
Ref: 19b24877624
Ref: C API<51>-Footnote-14878750
Ref: C API<51>-Footnote-24878815
Ref: C API<51>-Footnote-34878880
Ref: C API<51>-Footnote-44878945
Ref: C API<51>-Footnote-54879010
Ref: C API<51>-Footnote-64879075
Node: Python 3 7 0 alpha 24879140
Ref: whatsnew/changelog python-3-7-0-alpha-24879282
Ref: 19b34879282
Node: Core and Builtins<58>4879541
Ref: whatsnew/changelog id5084879639
Ref: 19b44879639
Ref: Core and Builtins<58>-Footnote-14883820
Ref: Core and Builtins<58>-Footnote-24883885
Ref: Core and Builtins<58>-Footnote-34883950
Ref: Core and Builtins<58>-Footnote-44884015
Ref: Core and Builtins<58>-Footnote-54884080
Ref: Core and Builtins<58>-Footnote-64884145
Ref: Core and Builtins<58>-Footnote-74884210
Ref: Core and Builtins<58>-Footnote-84884275
Ref: Core and Builtins<58>-Footnote-94884340
Ref: Core and Builtins<58>-Footnote-104884405
Ref: Core and Builtins<58>-Footnote-114884471
Ref: Core and Builtins<58>-Footnote-124884537
Ref: Core and Builtins<58>-Footnote-134884603
Ref: Core and Builtins<58>-Footnote-144884669
Ref: Core and Builtins<58>-Footnote-154884735
Ref: Core and Builtins<58>-Footnote-164884801
Ref: Core and Builtins<58>-Footnote-174884867
Ref: Core and Builtins<58>-Footnote-184884933
Ref: Core and Builtins<58>-Footnote-194884999
Ref: Core and Builtins<58>-Footnote-204885065
Ref: Core and Builtins<58>-Footnote-214885108
Ref: Core and Builtins<58>-Footnote-224885174
Ref: Core and Builtins<58>-Footnote-234885240
Ref: Core and Builtins<58>-Footnote-244885306
Ref: Core and Builtins<58>-Footnote-254885372
Ref: Core and Builtins<58>-Footnote-264885438
Ref: Core and Builtins<58>-Footnote-274885504
Node: Library<58>4885547
Ref: whatsnew/changelog id5094885671
Ref: 19b54885671
Ref: Library<58>-Footnote-14889710
Ref: Library<58>-Footnote-24889775
Ref: Library<58>-Footnote-34889840
Ref: Library<58>-Footnote-44889905
Ref: Library<58>-Footnote-54889970
Ref: Library<58>-Footnote-64890035
Ref: Library<58>-Footnote-74890100
Ref: Library<58>-Footnote-84890165
Ref: Library<58>-Footnote-94890230
Ref: Library<58>-Footnote-104890295
Ref: Library<58>-Footnote-114890361
Ref: Library<58>-Footnote-124890427
Ref: Library<58>-Footnote-134890493
Ref: Library<58>-Footnote-144890559
Ref: Library<58>-Footnote-154890625
Ref: Library<58>-Footnote-164890691
Ref: Library<58>-Footnote-174890757
Ref: Library<58>-Footnote-184890823
Ref: Library<58>-Footnote-194890889
Ref: Library<58>-Footnote-204890955
Ref: Library<58>-Footnote-214891021
Ref: Library<58>-Footnote-224891087
Ref: Library<58>-Footnote-234891153
Ref: Library<58>-Footnote-244891219
Ref: Library<58>-Footnote-254891285
Ref: Library<58>-Footnote-264891351
Node: Documentation<52>4891417
Ref: whatsnew/changelog id5104891529
Ref: 19b64891529
Ref: Documentation<52>-Footnote-14891920
Ref: Documentation<52>-Footnote-24891985
Node: Build<55>4892050
Ref: whatsnew/changelog id5114892159
Ref: 19b74892159
Ref: Build<55>-Footnote-14892782
Ref: Build<55>-Footnote-24892847
Ref: Build<55>-Footnote-34892912
Ref: Build<55>-Footnote-44892977
Ref: Build<55>-Footnote-54893042
Ref: Build<55>-Footnote-64893107
Node: IDLE<42>4893172
Ref: whatsnew/changelog id5124893273
Ref: 19b84893273
Ref: IDLE<42>-Footnote-14894575
Ref: IDLE<42>-Footnote-24894640
Ref: IDLE<42>-Footnote-34894705
Ref: IDLE<42>-Footnote-44894770
Ref: IDLE<42>-Footnote-54894835
Ref: IDLE<42>-Footnote-64894900
Node: C API<52>4894967
Ref: whatsnew/changelog id5134895050
Ref: 19b94895050
Ref: C API<52>-Footnote-14895774
Ref: C API<52>-Footnote-24895839
Ref: C API<52>-Footnote-34895904
Ref: C API<52>-Footnote-44895969
Node: Python 3 7 0 alpha 14896011
Ref: whatsnew/changelog python-3-7-0-alpha-14896151
Ref: 19ba4896151
Node: Security<36>4896512
Ref: whatsnew/changelog id5144896611
Ref: 19bb4896611
Ref: Security<36>-Footnote-14898261
Ref: Security<36>-Footnote-24898326
Ref: Security<36>-Footnote-34898391
Ref: Security<36>-Footnote-44898456
Ref: Security<36>-Footnote-54898521
Ref: Security<36>-Footnote-64898586
Ref: Security<36>-Footnote-74898655
Ref: Security<36>-Footnote-84898724
Ref: Security<36>-Footnote-94898793
Ref: Security<36>-Footnote-104898862
Ref: Security<36>-Footnote-114898932
Ref: Security<36>-Footnote-124899002
Ref: Security<36>-Footnote-134899068
Ref: Security<36>-Footnote-144899134
Ref: Security<36>-Footnote-154899204
Node: Core and Builtins<59>4899274
Ref: whatsnew/changelog id5154899393
Ref: 19bc4899393
Ref: Core and Builtins<59>-Footnote-14920209
Ref: Core and Builtins<59>-Footnote-24920274
Ref: Core and Builtins<59>-Footnote-34920339
Ref: Core and Builtins<59>-Footnote-44920404
Ref: Core and Builtins<59>-Footnote-54920469
Ref: Core and Builtins<59>-Footnote-64920534
Ref: Core and Builtins<59>-Footnote-74920599
Ref: Core and Builtins<59>-Footnote-84920664
Ref: Core and Builtins<59>-Footnote-94920729
Ref: Core and Builtins<59>-Footnote-104920794
Ref: Core and Builtins<59>-Footnote-114920860
Ref: Core and Builtins<59>-Footnote-124920926
Ref: Core and Builtins<59>-Footnote-134920992
Ref: Core and Builtins<59>-Footnote-144921058
Ref: Core and Builtins<59>-Footnote-154921124
Ref: Core and Builtins<59>-Footnote-164921190
Ref: Core and Builtins<59>-Footnote-174921256
Ref: Core and Builtins<59>-Footnote-184921322
Ref: Core and Builtins<59>-Footnote-194921388
Ref: Core and Builtins<59>-Footnote-204921454
Ref: Core and Builtins<59>-Footnote-214921520
Ref: Core and Builtins<59>-Footnote-224921586
Ref: Core and Builtins<59>-Footnote-234921652
Ref: Core and Builtins<59>-Footnote-244921718
Ref: Core and Builtins<59>-Footnote-254921784
Ref: Core and Builtins<59>-Footnote-264921850
Ref: Core and Builtins<59>-Footnote-274921916
Ref: Core and Builtins<59>-Footnote-284921982
Ref: Core and Builtins<59>-Footnote-294922048
Ref: Core and Builtins<59>-Footnote-304922114
Ref: Core and Builtins<59>-Footnote-314922180
Ref: Core and Builtins<59>-Footnote-324922246
Ref: Core and Builtins<59>-Footnote-334922312
Ref: Core and Builtins<59>-Footnote-344922378
Ref: Core and Builtins<59>-Footnote-354922444
Ref: Core and Builtins<59>-Footnote-364922487
Ref: Core and Builtins<59>-Footnote-374922553
Ref: Core and Builtins<59>-Footnote-384922619
Ref: Core and Builtins<59>-Footnote-394922685
Ref: Core and Builtins<59>-Footnote-404922751
Ref: Core and Builtins<59>-Footnote-414922817
Ref: Core and Builtins<59>-Footnote-424922883
Ref: Core and Builtins<59>-Footnote-434922949
Ref: Core and Builtins<59>-Footnote-444923015
Ref: Core and Builtins<59>-Footnote-454923081
Ref: Core and Builtins<59>-Footnote-464923147
Ref: Core and Builtins<59>-Footnote-474923213
Ref: Core and Builtins<59>-Footnote-484923279
Ref: Core and Builtins<59>-Footnote-494923345
Ref: Core and Builtins<59>-Footnote-504923411
Ref: Core and Builtins<59>-Footnote-514923477
Ref: Core and Builtins<59>-Footnote-524923543
Ref: Core and Builtins<59>-Footnote-534923609
Ref: Core and Builtins<59>-Footnote-544923675
Ref: Core and Builtins<59>-Footnote-554923741
Ref: Core and Builtins<59>-Footnote-564923807
Ref: Core and Builtins<59>-Footnote-574923873
Ref: Core and Builtins<59>-Footnote-584923939
Ref: Core and Builtins<59>-Footnote-594924005
Ref: Core and Builtins<59>-Footnote-604924071
Ref: Core and Builtins<59>-Footnote-614924137
Ref: Core and Builtins<59>-Footnote-624924203
Ref: Core and Builtins<59>-Footnote-634924269
Ref: Core and Builtins<59>-Footnote-644924335
Ref: Core and Builtins<59>-Footnote-654924401
Ref: Core and Builtins<59>-Footnote-664924467
Ref: Core and Builtins<59>-Footnote-674924533
Ref: Core and Builtins<59>-Footnote-684924599
Ref: Core and Builtins<59>-Footnote-694924665
Ref: Core and Builtins<59>-Footnote-704924731
Ref: Core and Builtins<59>-Footnote-714924797
Ref: Core and Builtins<59>-Footnote-724924863
Ref: Core and Builtins<59>-Footnote-734924929
Ref: Core and Builtins<59>-Footnote-744924995
Ref: Core and Builtins<59>-Footnote-754925061
Ref: Core and Builtins<59>-Footnote-764925127
Ref: Core and Builtins<59>-Footnote-774925193
Ref: Core and Builtins<59>-Footnote-784925259
Ref: Core and Builtins<59>-Footnote-794925325
Ref: Core and Builtins<59>-Footnote-804925391
Ref: Core and Builtins<59>-Footnote-814925457
Ref: Core and Builtins<59>-Footnote-824925523
Ref: Core and Builtins<59>-Footnote-834925589
Ref: Core and Builtins<59>-Footnote-844925655
Ref: Core and Builtins<59>-Footnote-854925721
Ref: Core and Builtins<59>-Footnote-864925787
Ref: Core and Builtins<59>-Footnote-874925853
Ref: Core and Builtins<59>-Footnote-884925919
Ref: Core and Builtins<59>-Footnote-894925985
Ref: Core and Builtins<59>-Footnote-904926051
Ref: Core and Builtins<59>-Footnote-914926094
Ref: Core and Builtins<59>-Footnote-924926160
Ref: Core and Builtins<59>-Footnote-934926226
Ref: Core and Builtins<59>-Footnote-944926292
Ref: Core and Builtins<59>-Footnote-954926358
Ref: Core and Builtins<59>-Footnote-964926424
Ref: Core and Builtins<59>-Footnote-974926490
Ref: Core and Builtins<59>-Footnote-984926556
Ref: Core and Builtins<59>-Footnote-994926622
Ref: Core and Builtins<59>-Footnote-1004926688
Ref: Core and Builtins<59>-Footnote-1014926755
Ref: Core and Builtins<59>-Footnote-1024926822
Ref: Core and Builtins<59>-Footnote-1034926889
Ref: Core and Builtins<59>-Footnote-1044926956
Ref: Core and Builtins<59>-Footnote-1054927023
Ref: Core and Builtins<59>-Footnote-1064927090
Ref: Core and Builtins<59>-Footnote-1074927157
Ref: Core and Builtins<59>-Footnote-1084927224
Ref: Core and Builtins<59>-Footnote-1094927291
Ref: Core and Builtins<59>-Footnote-1104927358
Ref: Core and Builtins<59>-Footnote-1114927425
Ref: Core and Builtins<59>-Footnote-1124927492
Ref: Core and Builtins<59>-Footnote-1134927559
Ref: Core and Builtins<59>-Footnote-1144927626
Ref: Core and Builtins<59>-Footnote-1154927693
Ref: Core and Builtins<59>-Footnote-1164927760
Ref: Core and Builtins<59>-Footnote-1174927827
Ref: Core and Builtins<59>-Footnote-1184927894
Ref: Core and Builtins<59>-Footnote-1194927961
Ref: Core and Builtins<59>-Footnote-1204928028
Ref: Core and Builtins<59>-Footnote-1214928095
Ref: Core and Builtins<59>-Footnote-1224928162
Ref: Core and Builtins<59>-Footnote-1234928229
Ref: Core and Builtins<59>-Footnote-1244928296
Ref: Core and Builtins<59>-Footnote-1254928363
Ref: Core and Builtins<59>-Footnote-1264928430
Ref: Core and Builtins<59>-Footnote-1274928497
Ref: Core and Builtins<59>-Footnote-1284928564
Ref: Core and Builtins<59>-Footnote-1294928631
Ref: Core and Builtins<59>-Footnote-1304928698
Ref: Core and Builtins<59>-Footnote-1314928765
Ref: Core and Builtins<59>-Footnote-1324928832
Ref: Core and Builtins<59>-Footnote-1334928899
Ref: Core and Builtins<59>-Footnote-1344928966
Ref: Core and Builtins<59>-Footnote-1354929033
Ref: Core and Builtins<59>-Footnote-1364929100
Ref: Core and Builtins<59>-Footnote-1374929167
Ref: Core and Builtins<59>-Footnote-1384929234
Ref: Core and Builtins<59>-Footnote-1394929301
Ref: Core and Builtins<59>-Footnote-1404929368
Ref: Core and Builtins<59>-Footnote-1414929435
Ref: Core and Builtins<59>-Footnote-1424929502
Ref: Core and Builtins<59>-Footnote-1434929569
Ref: Core and Builtins<59>-Footnote-1444929636
Ref: Core and Builtins<59>-Footnote-1454929703
Ref: Core and Builtins<59>-Footnote-1464929770
Ref: Core and Builtins<59>-Footnote-1474929837
Ref: Core and Builtins<59>-Footnote-1484929904
Node: Library<59>4929971
Ref: whatsnew/changelog id5164930095
Ref: 19bd4930095
Ref: Library<59>-Footnote-14976594
Ref: Library<59>-Footnote-24976659
Ref: Library<59>-Footnote-34976724
Ref: Library<59>-Footnote-44976789
Ref: Library<59>-Footnote-54976854
Ref: Library<59>-Footnote-64976919
Ref: Library<59>-Footnote-74976984
Ref: Library<59>-Footnote-84977049
Ref: Library<59>-Footnote-94977114
Ref: Library<59>-Footnote-104977179
Ref: Library<59>-Footnote-114977245
Ref: Library<59>-Footnote-124977311
Ref: Library<59>-Footnote-134977377
Ref: Library<59>-Footnote-144977443
Ref: Library<59>-Footnote-154977509
Ref: Library<59>-Footnote-164977575
Ref: Library<59>-Footnote-174977641
Ref: Library<59>-Footnote-184977707
Ref: Library<59>-Footnote-194977773
Ref: Library<59>-Footnote-204977839
Ref: Library<59>-Footnote-214977905
Ref: Library<59>-Footnote-224977973
Ref: Library<59>-Footnote-234978039
Ref: Library<59>-Footnote-244978105
Ref: Library<59>-Footnote-254978171
Ref: Library<59>-Footnote-264978237
Ref: Library<59>-Footnote-274978280
Ref: Library<59>-Footnote-284978346
Ref: Library<59>-Footnote-294978412
Ref: Library<59>-Footnote-304978478
Ref: Library<59>-Footnote-314978544
Ref: Library<59>-Footnote-324978610
Ref: Library<59>-Footnote-334978676
Ref: Library<59>-Footnote-344978742
Ref: Library<59>-Footnote-354978807
Ref: Library<59>-Footnote-364978873
Ref: Library<59>-Footnote-374978939
Ref: Library<59>-Footnote-384979005
Ref: Library<59>-Footnote-394979071
Ref: Library<59>-Footnote-404979136
Ref: Library<59>-Footnote-414979202
Ref: Library<59>-Footnote-424979268
Ref: Library<59>-Footnote-434979334
Ref: Library<59>-Footnote-444979400
Ref: Library<59>-Footnote-454979466
Ref: Library<59>-Footnote-464979532
Ref: Library<59>-Footnote-474979598
Ref: Library<59>-Footnote-484979664
Ref: Library<59>-Footnote-494979730
Ref: Library<59>-Footnote-504979796
Ref: Library<59>-Footnote-514979862
Ref: Library<59>-Footnote-524979928
Ref: Library<59>-Footnote-534979993
Ref: Library<59>-Footnote-544980059
Ref: Library<59>-Footnote-554980125
Ref: Library<59>-Footnote-564980191
Ref: Library<59>-Footnote-574980257
Ref: Library<59>-Footnote-584980323
Ref: Library<59>-Footnote-594980389
Ref: Library<59>-Footnote-604980455
Ref: Library<59>-Footnote-614980521
Ref: Library<59>-Footnote-624980587
Ref: Library<59>-Footnote-634980653
Ref: Library<59>-Footnote-644980719
Ref: Library<59>-Footnote-654980785
Ref: Library<59>-Footnote-664980851
Ref: Library<59>-Footnote-674980917
Ref: Library<59>-Footnote-684980983
Ref: Library<59>-Footnote-694981049
Ref: Library<59>-Footnote-704981115
Ref: Library<59>-Footnote-714981181
Ref: Library<59>-Footnote-724981247
Ref: Library<59>-Footnote-734981312
Ref: Library<59>-Footnote-744981378
Ref: Library<59>-Footnote-754981444
Ref: Library<59>-Footnote-764981510
Ref: Library<59>-Footnote-774981576
Ref: Library<59>-Footnote-784981642
Ref: Library<59>-Footnote-794981708
Ref: Library<59>-Footnote-804981774
Ref: Library<59>-Footnote-814981840
Ref: Library<59>-Footnote-824981906
Ref: Library<59>-Footnote-834981972
Ref: Library<59>-Footnote-844982038
Ref: Library<59>-Footnote-854982104
Ref: Library<59>-Footnote-864982170
Ref: Library<59>-Footnote-874982236
Ref: Library<59>-Footnote-884982302
Ref: Library<59>-Footnote-894982368
Ref: Library<59>-Footnote-904982434
Ref: Library<59>-Footnote-914982500
Ref: Library<59>-Footnote-924982566
Ref: Library<59>-Footnote-934982632
Ref: Library<59>-Footnote-944982698
Ref: Library<59>-Footnote-954982764
Ref: Library<59>-Footnote-964982830
Ref: Library<59>-Footnote-974982896
Ref: Library<59>-Footnote-984982962
Ref: Library<59>-Footnote-994983028
Ref: Library<59>-Footnote-1004983094
Ref: Library<59>-Footnote-1014983161
Ref: Library<59>-Footnote-1024983228
Ref: Library<59>-Footnote-1034983295
Ref: Library<59>-Footnote-1044983362
Ref: Library<59>-Footnote-1054983429
Ref: Library<59>-Footnote-1064983496
Ref: Library<59>-Footnote-1074983563
Ref: Library<59>-Footnote-1084983630
Ref: Library<59>-Footnote-1094983697
Ref: Library<59>-Footnote-1104983764
Ref: Library<59>-Footnote-1114983831
Ref: Library<59>-Footnote-1124983898
Ref: Library<59>-Footnote-1134983965
Ref: Library<59>-Footnote-1144984032
Ref: Library<59>-Footnote-1154984099
Ref: Library<59>-Footnote-1164984166
Ref: Library<59>-Footnote-1174984232
Ref: Library<59>-Footnote-1184984299
Ref: Library<59>-Footnote-1194984366
Ref: Library<59>-Footnote-1204984433
Ref: Library<59>-Footnote-1214984500
Ref: Library<59>-Footnote-1224984567
Ref: Library<59>-Footnote-1234984634
Ref: Library<59>-Footnote-1244984701
Ref: Library<59>-Footnote-1254984768
Ref: Library<59>-Footnote-1264984835
Ref: Library<59>-Footnote-1274984902
Ref: Library<59>-Footnote-1284984969
Ref: Library<59>-Footnote-1294985036
Ref: Library<59>-Footnote-1304985103
Ref: Library<59>-Footnote-1314985170
Ref: Library<59>-Footnote-1324985237
Ref: Library<59>-Footnote-1334985304
Ref: Library<59>-Footnote-1344985371
Ref: Library<59>-Footnote-1354985438
Ref: Library<59>-Footnote-1364985505
Ref: Library<59>-Footnote-1374985572
Ref: Library<59>-Footnote-1384985639
Ref: Library<59>-Footnote-1394985706
Ref: Library<59>-Footnote-1404985773
Ref: Library<59>-Footnote-1414985840
Ref: Library<59>-Footnote-1424985907
Ref: Library<59>-Footnote-1434985974
Ref: Library<59>-Footnote-1444986041
Ref: Library<59>-Footnote-1454986108
Ref: Library<59>-Footnote-1464986175
Ref: Library<59>-Footnote-1474986241
Ref: Library<59>-Footnote-1484986308
Ref: Library<59>-Footnote-1494986375
Ref: Library<59>-Footnote-1504986442
Ref: Library<59>-Footnote-1514986509
Ref: Library<59>-Footnote-1524986576
Ref: Library<59>-Footnote-1534986643
Ref: Library<59>-Footnote-1544986710
Ref: Library<59>-Footnote-1554986777
Ref: Library<59>-Footnote-1564986844
Ref: Library<59>-Footnote-1574986911
Ref: Library<59>-Footnote-1584986978
Ref: Library<59>-Footnote-1594987045
Ref: Library<59>-Footnote-1604987112
Ref: Library<59>-Footnote-1614987179
Ref: Library<59>-Footnote-1624987246
Ref: Library<59>-Footnote-1634987313
Ref: Library<59>-Footnote-1644987380
Ref: Library<59>-Footnote-1654987447
Ref: Library<59>-Footnote-1664987514
Ref: Library<59>-Footnote-1674987581
Ref: Library<59>-Footnote-1684987648
Ref: Library<59>-Footnote-1694987715
Ref: Library<59>-Footnote-1704987781
Ref: Library<59>-Footnote-1714987848
Ref: Library<59>-Footnote-1724987915
Ref: Library<59>-Footnote-1734987982
Ref: Library<59>-Footnote-1744988049
Ref: Library<59>-Footnote-1754988116
Ref: Library<59>-Footnote-1764988183
Ref: Library<59>-Footnote-1774988250
Ref: Library<59>-Footnote-1784988317
Ref: Library<59>-Footnote-1794988384
Ref: Library<59>-Footnote-1804988451
Ref: Library<59>-Footnote-1814988517
Ref: Library<59>-Footnote-1824988584
Ref: Library<59>-Footnote-1834988651
Ref: Library<59>-Footnote-1844988718
Ref: Library<59>-Footnote-1854988785
Ref: Library<59>-Footnote-1864988852
Ref: Library<59>-Footnote-1874988918
Ref: Library<59>-Footnote-1884988985
Ref: Library<59>-Footnote-1894989052
Ref: Library<59>-Footnote-1904989119
Ref: Library<59>-Footnote-1914989186
Ref: Library<59>-Footnote-1924989253
Ref: Library<59>-Footnote-1934989320
Ref: Library<59>-Footnote-1944989387
Ref: Library<59>-Footnote-1954989454
Ref: Library<59>-Footnote-1964989521
Ref: Library<59>-Footnote-1974989588
Ref: Library<59>-Footnote-1984989655
Ref: Library<59>-Footnote-1994989722
Ref: Library<59>-Footnote-2004989789
Ref: Library<59>-Footnote-2014989856
Ref: Library<59>-Footnote-2024989923
Ref: Library<59>-Footnote-2034989990
Ref: Library<59>-Footnote-2044990057
Ref: Library<59>-Footnote-2054990124
Ref: Library<59>-Footnote-2064990191
Ref: Library<59>-Footnote-2074990258
Ref: Library<59>-Footnote-2084990325
Ref: Library<59>-Footnote-2094990392
Ref: Library<59>-Footnote-2104990459
Ref: Library<59>-Footnote-2114990526
Ref: Library<59>-Footnote-2124990593
Ref: Library<59>-Footnote-2134990660
Ref: Library<59>-Footnote-2144990727
Ref: Library<59>-Footnote-2154990794
Ref: Library<59>-Footnote-2164990861
Ref: Library<59>-Footnote-2174990928
Ref: Library<59>-Footnote-2184990995
Ref: Library<59>-Footnote-2194991062
Ref: Library<59>-Footnote-2204991129
Ref: Library<59>-Footnote-2214991196
Ref: Library<59>-Footnote-2224991263
Ref: Library<59>-Footnote-2234991330
Ref: Library<59>-Footnote-2244991397
Ref: Library<59>-Footnote-2254991463
Ref: Library<59>-Footnote-2264991530
Ref: Library<59>-Footnote-2274991597
Ref: Library<59>-Footnote-2284991664
Ref: Library<59>-Footnote-2294991731
Ref: Library<59>-Footnote-2304991798
Ref: Library<59>-Footnote-2314991865
Ref: Library<59>-Footnote-2324991932
Ref: Library<59>-Footnote-2334991999
Ref: Library<59>-Footnote-2344992066
Ref: Library<59>-Footnote-2354992133
Ref: Library<59>-Footnote-2364992200
Ref: Library<59>-Footnote-2374992267
Ref: Library<59>-Footnote-2384992334
Ref: Library<59>-Footnote-2394992401
Ref: Library<59>-Footnote-2404992468
Ref: Library<59>-Footnote-2414992535
Ref: Library<59>-Footnote-2424992602
Ref: Library<59>-Footnote-2434992669
Ref: Library<59>-Footnote-2444992736
Ref: Library<59>-Footnote-2454992803
Ref: Library<59>-Footnote-2464992870
Ref: Library<59>-Footnote-2474992937
Ref: Library<59>-Footnote-2484993004
Ref: Library<59>-Footnote-2494993071
Ref: Library<59>-Footnote-2504993138
Ref: Library<59>-Footnote-2514993205
Ref: Library<59>-Footnote-2524993272
Ref: Library<59>-Footnote-2534993339
Ref: Library<59>-Footnote-2544993406
Ref: Library<59>-Footnote-2554993473
Ref: Library<59>-Footnote-2564993540
Ref: Library<59>-Footnote-2574993607
Ref: Library<59>-Footnote-2584993674
Ref: Library<59>-Footnote-2594993741
Ref: Library<59>-Footnote-2604993808
Ref: Library<59>-Footnote-2614993875
Ref: Library<59>-Footnote-2624993942
Ref: Library<59>-Footnote-2634994009
Ref: Library<59>-Footnote-2644994076
Ref: Library<59>-Footnote-2654994143
Ref: Library<59>-Footnote-2664994210
Ref: Library<59>-Footnote-2674994277
Ref: Library<59>-Footnote-2684994344
Ref: Library<59>-Footnote-2694994411
Ref: Library<59>-Footnote-2704994478
Ref: Library<59>-Footnote-2714994545
Ref: Library<59>-Footnote-2724994612
Ref: Library<59>-Footnote-2734994668
Ref: Library<59>-Footnote-2744994735
Ref: Library<59>-Footnote-2754994802
Ref: Library<59>-Footnote-2764994869
Ref: Library<59>-Footnote-2774994936
Ref: Library<59>-Footnote-2784995003
Ref: Library<59>-Footnote-2794995070
Ref: Library<59>-Footnote-2804995137
Ref: Library<59>-Footnote-2814995204
Ref: Library<59>-Footnote-2824995271
Ref: Library<59>-Footnote-2834995338
Ref: Library<59>-Footnote-2844995405
Ref: Library<59>-Footnote-2854995472
Ref: Library<59>-Footnote-2864995539
Ref: Library<59>-Footnote-2874995606
Ref: Library<59>-Footnote-2884995673
Ref: Library<59>-Footnote-2894995740
Ref: Library<59>-Footnote-2904995807
Ref: Library<59>-Footnote-2914995874
Ref: Library<59>-Footnote-2924995941
Ref: Library<59>-Footnote-2934996008
Ref: Library<59>-Footnote-2944996075
Ref: Library<59>-Footnote-2954996142
Ref: Library<59>-Footnote-2964996209
Ref: Library<59>-Footnote-2974996276
Ref: Library<59>-Footnote-2984996343
Ref: Library<59>-Footnote-2994996410
Ref: Library<59>-Footnote-3004996477
Ref: Library<59>-Footnote-3014996544
Ref: Library<59>-Footnote-3024996611
Ref: Library<59>-Footnote-3034996678
Ref: Library<59>-Footnote-3044996745
Ref: Library<59>-Footnote-3054996812
Ref: Library<59>-Footnote-3064996879
Ref: Library<59>-Footnote-3074996946
Ref: Library<59>-Footnote-3084997013
Ref: Library<59>-Footnote-3094997080
Ref: Library<59>-Footnote-3104997147
Ref: Library<59>-Footnote-3114997214
Ref: Library<59>-Footnote-3124997281
Ref: Library<59>-Footnote-3134997348
Ref: Library<59>-Footnote-3144997415
Ref: Library<59>-Footnote-3154997482
Ref: Library<59>-Footnote-3164997549
Ref: Library<59>-Footnote-3174997616
Ref: Library<59>-Footnote-3184997683
Ref: Library<59>-Footnote-3194997750
Ref: Library<59>-Footnote-3204997817
Ref: Library<59>-Footnote-3214997884
Ref: Library<59>-Footnote-3224997951
Ref: Library<59>-Footnote-3234998018
Ref: Library<59>-Footnote-3244998085
Ref: Library<59>-Footnote-3254998152
Ref: Library<59>-Footnote-3264998219
Node: Documentation<53>4998286
Ref: whatsnew/changelog id5174998398
Ref: 19be4998398
Ref: Documentation<53>-Footnote-15000562
Ref: Documentation<53>-Footnote-25000627
Ref: Documentation<53>-Footnote-35000692
Ref: Documentation<53>-Footnote-45000757
Ref: Documentation<53>-Footnote-55000822
Ref: Documentation<53>-Footnote-65000887
Ref: Documentation<53>-Footnote-75000952
Ref: Documentation<53>-Footnote-85001017
Ref: Documentation<53>-Footnote-95001082
Ref: Documentation<53>-Footnote-105001147
Ref: Documentation<53>-Footnote-115001213
Ref: Documentation<53>-Footnote-125001279
Ref: Documentation<53>-Footnote-135001345
Ref: Documentation<53>-Footnote-145001411
Ref: Documentation<53>-Footnote-155001477
Ref: Documentation<53>-Footnote-165001543
Ref: Documentation<53>-Footnote-175001586
Node: Tests<53>5001652
Ref: whatsnew/changelog id5185001762
Ref: 19c15001762
Ref: Tests<53>-Footnote-15004508
Ref: Tests<53>-Footnote-25004573
Ref: Tests<53>-Footnote-35004638
Ref: Tests<53>-Footnote-45004703
Ref: Tests<53>-Footnote-55004768
Ref: Tests<53>-Footnote-65004833
Ref: Tests<53>-Footnote-75004898
Ref: Tests<53>-Footnote-85004963
Ref: Tests<53>-Footnote-95005028
Ref: Tests<53>-Footnote-105005093
Ref: Tests<53>-Footnote-115005159
Ref: Tests<53>-Footnote-125005225
Ref: Tests<53>-Footnote-135005291
Ref: Tests<53>-Footnote-145005357
Ref: Tests<53>-Footnote-155005423
Ref: Tests<53>-Footnote-165005489
Ref: Tests<53>-Footnote-175005555
Ref: Tests<53>-Footnote-185005621
Ref: Tests<53>-Footnote-195005687
Node: Build<56>5005753
Ref: whatsnew/changelog id5195005857
Ref: 19c25005857
Ref: Build<56>-Footnote-15010610
Ref: Build<56>-Footnote-25010675
Ref: Build<56>-Footnote-35010740
Ref: Build<56>-Footnote-45010805
Ref: Build<56>-Footnote-55010847
Ref: Build<56>-Footnote-65010912
Ref: Build<56>-Footnote-75010977
Ref: Build<56>-Footnote-85011042
Ref: Build<56>-Footnote-95011107
Ref: Build<56>-Footnote-105011172
Ref: Build<56>-Footnote-115011238
Ref: Build<56>-Footnote-125011304
Ref: Build<56>-Footnote-135011370
Ref: Build<56>-Footnote-145011436
Ref: Build<56>-Footnote-155011502
Ref: Build<56>-Footnote-165011568
Ref: Build<56>-Footnote-175011634
Ref: Build<56>-Footnote-185011700
Ref: Build<56>-Footnote-195011766
Ref: Build<56>-Footnote-205011832
Ref: Build<56>-Footnote-215011898
Ref: Build<56>-Footnote-225011964
Ref: Build<56>-Footnote-235012030
Ref: Build<56>-Footnote-245012096
Ref: Build<56>-Footnote-255012162
Ref: Build<56>-Footnote-265012228
Ref: Build<56>-Footnote-275012294
Ref: Build<56>-Footnote-285012360
Ref: Build<56>-Footnote-295012426
Ref: Build<56>-Footnote-305012492
Ref: Build<56>-Footnote-315012558
Ref: Build<56>-Footnote-325012624
Ref: Build<56>-Footnote-335012690
Ref: Build<56>-Footnote-345012756
Ref: Build<56>-Footnote-355012822
Ref: Build<56>-Footnote-365012888
Ref: Build<56>-Footnote-375012954
Node: Windows<51>5013020
Ref: whatsnew/changelog id5205013123
Ref: 19c35013123
Ref: Windows<51>-Footnote-15015609
Ref: Windows<51>-Footnote-25015674
Ref: Windows<51>-Footnote-35015739
Ref: Windows<51>-Footnote-45015804
Ref: Windows<51>-Footnote-55015869
Ref: Windows<51>-Footnote-65015934
Ref: Windows<51>-Footnote-75015999
Ref: Windows<51>-Footnote-85016064
Ref: Windows<51>-Footnote-95016129
Ref: Windows<51>-Footnote-105016194
Ref: Windows<51>-Footnote-115016260
Ref: Windows<51>-Footnote-125016326
Ref: Windows<51>-Footnote-135016392
Ref: Windows<51>-Footnote-145016458
Ref: Windows<51>-Footnote-155016524
Ref: Windows<51>-Footnote-165016590
Ref: Windows<51>-Footnote-175016656
Ref: Windows<51>-Footnote-185016722
Ref: Windows<51>-Footnote-195016788
Ref: Windows<51>-Footnote-205016854
Ref: Windows<51>-Footnote-215016920
Ref: Windows<51>-Footnote-225016986
Ref: Windows<51>-Footnote-235017052
Ref: Windows<51>-Footnote-245017118
Ref: Windows<51>-Footnote-255017184
Node: IDLE<43>5017250
Ref: whatsnew/changelog id5215017359
Ref: 19c45017359
Ref: IDLE<43>-Footnote-15027268
Ref: IDLE<43>-Footnote-25027333
Ref: IDLE<43>-Footnote-35027398
Ref: IDLE<43>-Footnote-45027463
Ref: IDLE<43>-Footnote-55027528
Ref: IDLE<43>-Footnote-65027593
Ref: IDLE<43>-Footnote-75027658
Ref: IDLE<43>-Footnote-85027723
Ref: IDLE<43>-Footnote-95027788
Ref: IDLE<43>-Footnote-105027853
Ref: IDLE<43>-Footnote-115027919
Ref: IDLE<43>-Footnote-125027985
Ref: IDLE<43>-Footnote-135028051
Ref: IDLE<43>-Footnote-145028117
Ref: IDLE<43>-Footnote-155028183
Ref: IDLE<43>-Footnote-165028249
Ref: IDLE<43>-Footnote-175028315
Ref: IDLE<43>-Footnote-185028381
Ref: IDLE<43>-Footnote-195028447
Ref: IDLE<43>-Footnote-205028513
Ref: IDLE<43>-Footnote-215028579
Ref: IDLE<43>-Footnote-225028645
Ref: IDLE<43>-Footnote-235028711
Ref: IDLE<43>-Footnote-245028777
Ref: IDLE<43>-Footnote-255028843
Ref: IDLE<43>-Footnote-265028909
Ref: IDLE<43>-Footnote-275028975
Ref: IDLE<43>-Footnote-285029041
Ref: IDLE<43>-Footnote-295029107
Ref: IDLE<43>-Footnote-305029173
Ref: IDLE<43>-Footnote-315029239
Ref: IDLE<43>-Footnote-325029305
Ref: IDLE<43>-Footnote-335029371
Ref: IDLE<43>-Footnote-345029437
Ref: IDLE<43>-Footnote-355029502
Ref: IDLE<43>-Footnote-365029568
Ref: IDLE<43>-Footnote-375029634
Ref: IDLE<43>-Footnote-385029700
Ref: IDLE<43>-Footnote-395029766
Ref: IDLE<43>-Footnote-405029832
Ref: IDLE<43>-Footnote-415029898
Ref: IDLE<43>-Footnote-425029964
Ref: IDLE<43>-Footnote-435030030
Ref: IDLE<43>-Footnote-445030095
Ref: IDLE<43>-Footnote-455030161
Ref: IDLE<43>-Footnote-465030227
Ref: IDLE<43>-Footnote-475030293
Ref: IDLE<43>-Footnote-485030359
Ref: IDLE<43>-Footnote-495030425
Ref: IDLE<43>-Footnote-505030491
Ref: IDLE<43>-Footnote-515030557
Node: Tools/Demos<29>5030623
Ref: whatsnew/changelog id5225030730
Ref: 19c55030730
Ref: Tools/Demos<29>-Footnote-15032212
Ref: Tools/Demos<29>-Footnote-25032277
Ref: Tools/Demos<29>-Footnote-35032319
Ref: Tools/Demos<29>-Footnote-45032384
Ref: Tools/Demos<29>-Footnote-55032449
Ref: Tools/Demos<29>-Footnote-65032514
Ref: Tools/Demos<29>-Footnote-75032579
Ref: Tools/Demos<29>-Footnote-85032644
Node: C API<53>5032709
Ref: whatsnew/changelog id5235032799
Ref: 19c65032799
Ref: C API<53>-Footnote-15035853
Ref: C API<53>-Footnote-25035918
Ref: C API<53>-Footnote-35035983
Ref: C API<53>-Footnote-45036048
Ref: C API<53>-Footnote-55036113
Ref: C API<53>-Footnote-65036177
Ref: C API<53>-Footnote-75036242
Ref: C API<53>-Footnote-85036307
Ref: C API<53>-Footnote-95036372
Ref: C API<53>-Footnote-105036437
Ref: C API<53>-Footnote-115036503
Ref: C API<53>-Footnote-125036569
Ref: C API<53>-Footnote-135036635
Ref: C API<53>-Footnote-145036701
Ref: C API<53>-Footnote-155036767
Node: Python 3 6 6 final5036833
Ref: whatsnew/changelog python-3-6-6-final5036985
Ref: 19c75036985
Node: Python 3 6 6 release candidate 15037113
Ref: whatsnew/changelog python-3-6-6-release-candidate-15037263
Ref: 19c85037263
Node: Core and Builtins<60>5037642
Ref: whatsnew/changelog id5245037752
Ref: 19c95037752
Ref: Core and Builtins<60>-Footnote-15039330
Ref: Core and Builtins<60>-Footnote-25039395
Ref: Core and Builtins<60>-Footnote-35039460
Ref: Core and Builtins<60>-Footnote-45039525
Ref: Core and Builtins<60>-Footnote-55039590
Ref: Core and Builtins<60>-Footnote-65039655
Ref: Core and Builtins<60>-Footnote-75039720
Ref: Core and Builtins<60>-Footnote-85039785
Ref: Core and Builtins<60>-Footnote-95039850
Ref: Core and Builtins<60>-Footnote-105039915
Ref: Core and Builtins<60>-Footnote-115039981
Ref: Core and Builtins<60>-Footnote-125040047
Node: Library<60>5040113
Ref: whatsnew/changelog id5255040249
Ref: 19ca5040249
Ref: Library<60>-Footnote-15045716
Ref: Library<60>-Footnote-25045781
Ref: Library<60>-Footnote-35045846
Ref: Library<60>-Footnote-45045911
Ref: Library<60>-Footnote-55045976
Ref: Library<60>-Footnote-65046041
Ref: Library<60>-Footnote-75046106
Ref: Library<60>-Footnote-85046171
Ref: Library<60>-Footnote-95046236
Ref: Library<60>-Footnote-105046301
Ref: Library<60>-Footnote-115046367
Ref: Library<60>-Footnote-125046433
Ref: Library<60>-Footnote-135046499
Ref: Library<60>-Footnote-145046565
Ref: Library<60>-Footnote-155046631
Ref: Library<60>-Footnote-165046697
Ref: Library<60>-Footnote-175046763
Ref: Library<60>-Footnote-185046829
Ref: Library<60>-Footnote-195046895
Ref: Library<60>-Footnote-205046961
Ref: Library<60>-Footnote-215047027
Ref: Library<60>-Footnote-225047094
Ref: Library<60>-Footnote-235047160
Ref: Library<60>-Footnote-245047226
Ref: Library<60>-Footnote-255047292
Ref: Library<60>-Footnote-265047358
Ref: Library<60>-Footnote-275047424
Ref: Library<60>-Footnote-285047490
Ref: Library<60>-Footnote-295047533
Ref: Library<60>-Footnote-305047599
Ref: Library<60>-Footnote-315047665
Ref: Library<60>-Footnote-325047731
Ref: Library<60>-Footnote-335047797
Ref: Library<60>-Footnote-345047863
Ref: Library<60>-Footnote-355047929
Ref: Library<60>-Footnote-365047995
Ref: Library<60>-Footnote-375048061
Ref: Library<60>-Footnote-385048127
Ref: Library<60>-Footnote-395048193
Node: Documentation<54>5048259
Ref: whatsnew/changelog id5265048383
Ref: 19cb5048383
Ref: Documentation<54>-Footnote-15049874
Ref: Documentation<54>-Footnote-25049939
Ref: Documentation<54>-Footnote-35050004
Ref: Documentation<54>-Footnote-45050069
Ref: Documentation<54>-Footnote-55050134
Ref: Documentation<54>-Footnote-65050199
Ref: Documentation<54>-Footnote-75050264
Ref: Documentation<54>-Footnote-85050329
Ref: Documentation<54>-Footnote-95050394
Ref: Documentation<54>-Footnote-105050459
Ref: Documentation<54>-Footnote-115050525
Ref: Documentation<54>-Footnote-125050591
Ref: Documentation<54>-Footnote-135050656
Node: Tests<54>5050722
Ref: whatsnew/changelog id5275050844
Ref: 19cc5050844
Ref: Tests<54>-Footnote-15051066
Ref: Tests<54>-Footnote-25051131
Node: Build<57>5051196
Ref: whatsnew/changelog id5285051312
Ref: 19cd5051312
Ref: Build<57>-Footnote-15052109
Ref: Build<57>-Footnote-25052173
Ref: Build<57>-Footnote-35052238
Ref: Build<57>-Footnote-45052303
Ref: Build<57>-Footnote-55052368
Node: Windows<52>5052433
Ref: whatsnew/changelog id5295052549
Ref: 19ce5052549
Ref: Windows<52>-Footnote-15052686
Node: macOS<42>5052751
Ref: whatsnew/changelog id5305052866
Ref: 19cf5052866
Ref: macOS<42>-Footnote-15053007
Node: IDLE<44>5053072
Ref: whatsnew/changelog id5315053191
Ref: 19d05053191
Ref: IDLE<44>-Footnote-15055246
Ref: IDLE<44>-Footnote-25055311
Ref: IDLE<44>-Footnote-35055376
Ref: IDLE<44>-Footnote-45055441
Ref: IDLE<44>-Footnote-55055506
Ref: IDLE<44>-Footnote-65055571
Ref: IDLE<44>-Footnote-75055636
Ref: IDLE<44>-Footnote-85055701
Ref: IDLE<44>-Footnote-95055766
Ref: IDLE<44>-Footnote-105055831
Ref: IDLE<44>-Footnote-115055897
Ref: IDLE<44>-Footnote-125055963
Node: Tools/Demos<30>5056029
Ref: whatsnew/changelog id5325056148
Ref: 19d15056148
Ref: Tools/Demos<30>-Footnote-15056899
Ref: Tools/Demos<30>-Footnote-25056964
Ref: Tools/Demos<30>-Footnote-35057029
Ref: Tools/Demos<30>-Footnote-45057094
Ref: Tools/Demos<30>-Footnote-55057159
Node: C API<54>5057224
Ref: whatsnew/changelog id5335057326
Ref: 19d25057326
Ref: C API<54>-Footnote-15057539
Node: Python 3 6 5 final5057604
Ref: whatsnew/changelog python-3-6-5-final5057768
Ref: 19d35057768
Node: Tests<55>5057901
Ref: whatsnew/changelog id5345057983
Ref: 19d45057983
Ref: Tests<55>-Footnote-15058137
Node: Build<58>5058202
Ref: whatsnew/changelog id5355058284
Ref: 19d55058284
Ref: Build<58>-Footnote-15058421
Node: Python 3 6 5 release candidate 15058486
Ref: whatsnew/changelog python-3-6-5-release-candidate-15058636
Ref: 19d65058636
Node: Security<37>5059041
Ref: whatsnew/changelog id5365059152
Ref: 19d75059152
Ref: Security<37>-Footnote-15059583
Ref: Security<37>-Footnote-25059648
Ref: Security<37>-Footnote-35059713
Ref: Security<37>-Footnote-45059782
Node: Core and Builtins<61>5059851
Ref: whatsnew/changelog id5375059982
Ref: 19d85059982
Ref: Core and Builtins<61>-Footnote-15062144
Ref: Core and Builtins<61>-Footnote-25062209
Ref: Core and Builtins<61>-Footnote-35062274
Ref: Core and Builtins<61>-Footnote-45062339
Ref: Core and Builtins<61>-Footnote-55062404
Ref: Core and Builtins<61>-Footnote-65062469
Ref: Core and Builtins<61>-Footnote-75062534
Ref: Core and Builtins<61>-Footnote-85062599
Ref: Core and Builtins<61>-Footnote-95062664
Ref: Core and Builtins<61>-Footnote-105062729
Ref: Core and Builtins<61>-Footnote-115062795
Ref: Core and Builtins<61>-Footnote-125062861
Ref: Core and Builtins<61>-Footnote-135062927
Ref: Core and Builtins<61>-Footnote-145062993
Node: Library<61>5063059
Ref: whatsnew/changelog id5385063195
Ref: 19d95063195
Ref: Library<61>-Footnote-15069104
Ref: Library<61>-Footnote-25069169
Ref: Library<61>-Footnote-35069234
Ref: Library<61>-Footnote-45069299
Ref: Library<61>-Footnote-55069364
Ref: Library<61>-Footnote-65069429
Ref: Library<61>-Footnote-75069494
Ref: Library<61>-Footnote-85069559
Ref: Library<61>-Footnote-95069624
Ref: Library<61>-Footnote-105069689
Ref: Library<61>-Footnote-115069755
Ref: Library<61>-Footnote-125069821
Ref: Library<61>-Footnote-135069887
Ref: Library<61>-Footnote-145069953
Ref: Library<61>-Footnote-155070019
Ref: Library<61>-Footnote-165070085
Ref: Library<61>-Footnote-175070151
Ref: Library<61>-Footnote-185070217
Ref: Library<61>-Footnote-195070283
Ref: Library<61>-Footnote-205070349
Ref: Library<61>-Footnote-215070415
Ref: Library<61>-Footnote-225070481
Ref: Library<61>-Footnote-235070547
Ref: Library<61>-Footnote-245070613
Ref: Library<61>-Footnote-255070679
Ref: Library<61>-Footnote-265070745
Ref: Library<61>-Footnote-275070811
Ref: Library<61>-Footnote-285070877
Ref: Library<61>-Footnote-295070943
Ref: Library<61>-Footnote-305071009
Ref: Library<61>-Footnote-315071075
Ref: Library<61>-Footnote-325071141
Ref: Library<61>-Footnote-335071207
Ref: Library<61>-Footnote-345071273
Ref: Library<61>-Footnote-355071339
Ref: Library<61>-Footnote-365071405
Ref: Library<61>-Footnote-375071471
Ref: Library<61>-Footnote-385071537
Ref: Library<61>-Footnote-395071603
Ref: Library<61>-Footnote-405071669
Node: Documentation<55>5071735
Ref: whatsnew/changelog id5395071859
Ref: 19da5071859
Ref: Documentation<55>-Footnote-15072695
Ref: Documentation<55>-Footnote-25072760
Ref: Documentation<55>-Footnote-35072825
Ref: Documentation<55>-Footnote-45072889
Ref: Documentation<55>-Footnote-55072954
Ref: Documentation<55>-Footnote-65073019
Node: Tests<56>5073084
Ref: whatsnew/changelog id5405073206
Ref: 19db5073206
Ref: Tests<56>-Footnote-15073867
Ref: Tests<56>-Footnote-25073932
Ref: Tests<56>-Footnote-35073997
Ref: Tests<56>-Footnote-45074062
Node: Build<59>5074127
Ref: whatsnew/changelog id5415074243
Ref: 19dc5074243
Ref: Build<59>-Footnote-15074432
Node: Windows<53>5074497
Ref: whatsnew/changelog id5425074613
Ref: 19dd5074613
Ref: Windows<53>-Footnote-15075563
Ref: Windows<53>-Footnote-25075628
Ref: Windows<53>-Footnote-35075693
Ref: Windows<53>-Footnote-45075758
Ref: Windows<53>-Footnote-55075823
Ref: Windows<53>-Footnote-65075888
Ref: Windows<53>-Footnote-75075953
Ref: Windows<53>-Footnote-85076018
Node: macOS<43>5076083
Ref: whatsnew/changelog id5435076198
Ref: 19de5076198
Ref: macOS<43>-Footnote-15076591
Node: IDLE<45>5076656
Ref: whatsnew/changelog id5445076775
Ref: 19df5076775
Ref: IDLE<45>-Footnote-15078257
Ref: IDLE<45>-Footnote-25078322
Ref: IDLE<45>-Footnote-35078387
Ref: IDLE<45>-Footnote-45078452
Ref: IDLE<45>-Footnote-55078517
Ref: IDLE<45>-Footnote-65078582
Ref: IDLE<45>-Footnote-75078647
Ref: IDLE<45>-Footnote-85078712
Node: Tools/Demos<31>5078777
Ref: whatsnew/changelog id5455078896
Ref: 19e05078896
Ref: Tools/Demos<31>-Footnote-15079316
Ref: Tools/Demos<31>-Footnote-25079381
Node: C API<55>5079446
Ref: whatsnew/changelog id5465079548
Ref: 19e15079548
Ref: C API<55>-Footnote-15079798
Node: Python 3 6 4 final5079863
Ref: whatsnew/changelog python-3-6-4-final5080027
Ref: 19e25080027
Node: Python 3 6 4 release candidate 15080176
Ref: whatsnew/changelog python-3-6-4-release-candidate-15080326
Ref: 19e35080326
Node: Core and Builtins<62>5080705
Ref: whatsnew/changelog id5475080815
Ref: 19e45080815
Ref: Core and Builtins<62>-Footnote-15085533
Ref: Core and Builtins<62>-Footnote-25085598
Ref: Core and Builtins<62>-Footnote-35085663
Ref: Core and Builtins<62>-Footnote-45085728
Ref: Core and Builtins<62>-Footnote-55085793
Ref: Core and Builtins<62>-Footnote-65085858
Ref: Core and Builtins<62>-Footnote-75085923
Ref: Core and Builtins<62>-Footnote-85085988
Ref: Core and Builtins<62>-Footnote-95086053
Ref: Core and Builtins<62>-Footnote-105086118
Ref: Core and Builtins<62>-Footnote-115086184
Ref: Core and Builtins<62>-Footnote-125086250
Ref: Core and Builtins<62>-Footnote-135086316
Ref: Core and Builtins<62>-Footnote-145086382
Ref: Core and Builtins<62>-Footnote-155086448
Ref: Core and Builtins<62>-Footnote-165086514
Ref: Core and Builtins<62>-Footnote-175086580
Ref: Core and Builtins<62>-Footnote-185086646
Ref: Core and Builtins<62>-Footnote-195086712
Ref: Core and Builtins<62>-Footnote-205086778
Ref: Core and Builtins<62>-Footnote-215086844
Ref: Core and Builtins<62>-Footnote-225086910
Ref: Core and Builtins<62>-Footnote-235086976
Ref: Core and Builtins<62>-Footnote-245087042
Node: Library<62>5087108
Ref: whatsnew/changelog id5485087244
Ref: 19e55087244
Ref: Library<62>-Footnote-15094555
Ref: Library<62>-Footnote-25094620
Ref: Library<62>-Footnote-35094685
Ref: Library<62>-Footnote-45094750
Ref: Library<62>-Footnote-55094815
Ref: Library<62>-Footnote-65094880
Ref: Library<62>-Footnote-75094945
Ref: Library<62>-Footnote-85095010
Ref: Library<62>-Footnote-95095075
Ref: Library<62>-Footnote-105095140
Ref: Library<62>-Footnote-115095206
Ref: Library<62>-Footnote-125095272
Ref: Library<62>-Footnote-135095338
Ref: Library<62>-Footnote-145095404
Ref: Library<62>-Footnote-155095470
Ref: Library<62>-Footnote-165095536
Ref: Library<62>-Footnote-175095601
Ref: Library<62>-Footnote-185095667
Ref: Library<62>-Footnote-195095733
Ref: Library<62>-Footnote-205095799
Ref: Library<62>-Footnote-215095865
Ref: Library<62>-Footnote-225095931
Ref: Library<62>-Footnote-235095997
Ref: Library<62>-Footnote-245096063
Ref: Library<62>-Footnote-255096129
Ref: Library<62>-Footnote-265096195
Ref: Library<62>-Footnote-275096261
Ref: Library<62>-Footnote-285096327
Ref: Library<62>-Footnote-295096393
Ref: Library<62>-Footnote-305096459
Ref: Library<62>-Footnote-315096525
Ref: Library<62>-Footnote-325096591
Ref: Library<62>-Footnote-335096657
Ref: Library<62>-Footnote-345096723
Ref: Library<62>-Footnote-355096789
Ref: Library<62>-Footnote-365096855
Ref: Library<62>-Footnote-375096921
Ref: Library<62>-Footnote-385096987
Ref: Library<62>-Footnote-395097053
Ref: Library<62>-Footnote-405097119
Ref: Library<62>-Footnote-415097185
Ref: Library<62>-Footnote-425097251
Ref: Library<62>-Footnote-435097317
Ref: Library<62>-Footnote-445097383
Ref: Library<62>-Footnote-455097449
Ref: Library<62>-Footnote-465097515
Ref: Library<62>-Footnote-475097581
Ref: Library<62>-Footnote-485097647
Ref: Library<62>-Footnote-495097713
Ref: Library<62>-Footnote-505097779
Ref: Library<62>-Footnote-515097845
Ref: Library<62>-Footnote-525097911
Node: Documentation<56>5097977
Ref: whatsnew/changelog id5495098101
Ref: 19e65098101
Ref: Documentation<56>-Footnote-15098590
Ref: Documentation<56>-Footnote-25098655
Ref: Documentation<56>-Footnote-35098720
Node: Tests<57>5098785
Ref: whatsnew/changelog id5505098907
Ref: 19e75098907
Ref: Tests<57>-Footnote-15099585
Ref: Tests<57>-Footnote-25099650
Ref: Tests<57>-Footnote-35099715
Ref: Tests<57>-Footnote-45099780
Node: Build<60>5099845
Ref: whatsnew/changelog id5515099961
Ref: 19e85099961
Ref: Build<60>-Footnote-15100865
Ref: Build<60>-Footnote-25100930
Ref: Build<60>-Footnote-35100995
Ref: Build<60>-Footnote-45101060
Ref: Build<60>-Footnote-55101125
Ref: Build<60>-Footnote-65101190
Ref: Build<60>-Footnote-75101255
Ref: Build<60>-Footnote-85101320
Ref: Build<60>-Footnote-95101385
Node: Windows<54>5101450
Ref: whatsnew/changelog id5525101566
Ref: 19e95101566
Ref: Windows<54>-Footnote-15101884
Ref: Windows<54>-Footnote-25101948
Node: macOS<44>5102013
Ref: whatsnew/changelog id5535102128
Ref: 19ea5102128
Ref: macOS<44>-Footnote-15102262
Node: IDLE<46>5102327
Ref: whatsnew/changelog id5545102446
Ref: 19eb5102446
Ref: IDLE<46>-Footnote-15105767
Ref: IDLE<46>-Footnote-25105832
Ref: IDLE<46>-Footnote-35105897
Ref: IDLE<46>-Footnote-45105962
Ref: IDLE<46>-Footnote-55106027
Ref: IDLE<46>-Footnote-65106092
Ref: IDLE<46>-Footnote-75106157
Ref: IDLE<46>-Footnote-85106222
Ref: IDLE<46>-Footnote-95106287
Ref: IDLE<46>-Footnote-105106352
Ref: IDLE<46>-Footnote-115106418
Ref: IDLE<46>-Footnote-125106484
Ref: IDLE<46>-Footnote-135106550
Ref: IDLE<46>-Footnote-145106616
Node: Tools/Demos<32>5106684
Ref: whatsnew/changelog id5555106803
Ref: 19ec5106803
Ref: Tools/Demos<32>-Footnote-15107091
Node: C API<56>5107156
Ref: whatsnew/changelog id5565107258
Ref: 19ed5107258
Ref: C API<56>-Footnote-15107986
Ref: C API<56>-Footnote-25108051
Ref: C API<56>-Footnote-35108116
Ref: C API<56>-Footnote-45108181
Node: Python 3 6 3 final5108246
Ref: whatsnew/changelog python-3-6-3-final5108410
Ref: 19ee5108410
Node: Library<63>5108547
Ref: whatsnew/changelog id5575108631
Ref: 19ef5108631
Ref: Library<63>-Footnote-15108833
Node: Build<61>5108898
Ref: whatsnew/changelog id5585108982
Ref: 19f05108982
Ref: Build<61>-Footnote-15109273
Ref: Build<61>-Footnote-25109338
Node: Python 3 6 3 release candidate 15109403
Ref: whatsnew/changelog python-3-6-3-release-candidate-15109553
Ref: 19f15109553
Node: Security<38>5109918
Ref: whatsnew/changelog id5595110029
Ref: 19f25110029
Ref: Security<38>-Footnote-15110335
Ref: Security<38>-Footnote-25110400
Node: Core and Builtins<63>5110465
Ref: whatsnew/changelog id5605110596
Ref: 19f35110596
Ref: Core and Builtins<63>-Footnote-15114113
Ref: Core and Builtins<63>-Footnote-25114178
Ref: Core and Builtins<63>-Footnote-35114243
Ref: Core and Builtins<63>-Footnote-45114308
Ref: Core and Builtins<63>-Footnote-55114373
Ref: Core and Builtins<63>-Footnote-65114438
Ref: Core and Builtins<63>-Footnote-75114503
Ref: Core and Builtins<63>-Footnote-85114568
Ref: Core and Builtins<63>-Footnote-95114633
Ref: Core and Builtins<63>-Footnote-105114698
Ref: Core and Builtins<63>-Footnote-115114764
Ref: Core and Builtins<63>-Footnote-125114830
Ref: Core and Builtins<63>-Footnote-135114896
Ref: Core and Builtins<63>-Footnote-145114962
Ref: Core and Builtins<63>-Footnote-155115028
Ref: Core and Builtins<63>-Footnote-165115094
Ref: Core and Builtins<63>-Footnote-175115160
Ref: Core and Builtins<63>-Footnote-185115226
Ref: Core and Builtins<63>-Footnote-195115292
Ref: Core and Builtins<63>-Footnote-205115358
Ref: Core and Builtins<63>-Footnote-215115424
Ref: Core and Builtins<63>-Footnote-225115490
Node: Library<64>5115556
Ref: whatsnew/changelog id5615115692
Ref: 19f45115692
Ref: Library<64>-Footnote-15121679
Ref: Library<64>-Footnote-25121744
Ref: Library<64>-Footnote-35121809
Ref: Library<64>-Footnote-45121874
Ref: Library<64>-Footnote-55121939
Ref: Library<64>-Footnote-65122004
Ref: Library<64>-Footnote-75122069
Ref: Library<64>-Footnote-85122134
Ref: Library<64>-Footnote-95122199
Ref: Library<64>-Footnote-105122264
Ref: Library<64>-Footnote-115122330
Ref: Library<64>-Footnote-125122396
Ref: Library<64>-Footnote-135122462
Ref: Library<64>-Footnote-145122528
Ref: Library<64>-Footnote-155122594
Ref: Library<64>-Footnote-165122659
Ref: Library<64>-Footnote-175122725
Ref: Library<64>-Footnote-185122791
Ref: Library<64>-Footnote-195122834
Ref: Library<64>-Footnote-205122900
Ref: Library<64>-Footnote-215122966
Ref: Library<64>-Footnote-225123032
Ref: Library<64>-Footnote-235123098
Ref: Library<64>-Footnote-245123164
Ref: Library<64>-Footnote-255123230
Ref: Library<64>-Footnote-265123296
Ref: Library<64>-Footnote-275123362
Ref: Library<64>-Footnote-285123428
Ref: Library<64>-Footnote-295123494
Ref: Library<64>-Footnote-305123560
Ref: Library<64>-Footnote-315123626
Ref: Library<64>-Footnote-325123692
Ref: Library<64>-Footnote-335123758
Ref: Library<64>-Footnote-345123824
Ref: Library<64>-Footnote-355123890
Ref: Library<64>-Footnote-365123956
Ref: Library<64>-Footnote-375124022
Ref: Library<64>-Footnote-385124088
Ref: Library<64>-Footnote-395124154
Ref: Library<64>-Footnote-405124220
Ref: Library<64>-Footnote-415124286
Ref: Library<64>-Footnote-425124352
Node: Documentation<57>5124418
Ref: whatsnew/changelog id5625124542
Ref: 19f55124542
Ref: Documentation<57>-Footnote-15124965
Ref: Documentation<57>-Footnote-25125030
Ref: Documentation<57>-Footnote-35125095
Node: Tests<58>5125160
Ref: whatsnew/changelog id5635125282
Ref: 19f65125282
Ref: Tests<58>-Footnote-15125983
Ref: Tests<58>-Footnote-25126048
Ref: Tests<58>-Footnote-35126113
Ref: Tests<58>-Footnote-45126178
Node: Build<62>5126243
Ref: whatsnew/changelog id5645126359
Ref: 19f75126359
Ref: Build<62>-Footnote-15126532
Node: Windows<55>5126597
Ref: whatsnew/changelog id5655126712
Ref: 19f85126712
Ref: Windows<55>-Footnote-15127220
Ref: Windows<55>-Footnote-25127285
Ref: Windows<55>-Footnote-35127350
Ref: Windows<55>-Footnote-45127415
Node: IDLE<47>5127480
Ref: whatsnew/changelog id5665127601
Ref: 19f95127601
Ref: IDLE<47>-Footnote-15136346
Ref: IDLE<47>-Footnote-25136411
Ref: IDLE<47>-Footnote-35136476
Ref: IDLE<47>-Footnote-45136541
Ref: IDLE<47>-Footnote-55136606
Ref: IDLE<47>-Footnote-65136671
Ref: IDLE<47>-Footnote-75136736
Ref: IDLE<47>-Footnote-85136801
Ref: IDLE<47>-Footnote-95136866
Ref: IDLE<47>-Footnote-105136931
Ref: IDLE<47>-Footnote-115136997
Ref: IDLE<47>-Footnote-125137063
Ref: IDLE<47>-Footnote-135137129
Ref: IDLE<47>-Footnote-145137195
Ref: IDLE<47>-Footnote-155137261
Ref: IDLE<47>-Footnote-165137327
Ref: IDLE<47>-Footnote-175137393
Ref: IDLE<47>-Footnote-185137459
Ref: IDLE<47>-Footnote-195137525
Ref: IDLE<47>-Footnote-205137591
Ref: IDLE<47>-Footnote-215137657
Ref: IDLE<47>-Footnote-225137723
Ref: IDLE<47>-Footnote-235137789
Ref: IDLE<47>-Footnote-245137855
Ref: IDLE<47>-Footnote-255137921
Ref: IDLE<47>-Footnote-265137987
Ref: IDLE<47>-Footnote-275138053
Ref: IDLE<47>-Footnote-285138119
Ref: IDLE<47>-Footnote-295138185
Ref: IDLE<47>-Footnote-305138251
Ref: IDLE<47>-Footnote-315138317
Ref: IDLE<47>-Footnote-325138383
Ref: IDLE<47>-Footnote-335138449
Ref: IDLE<47>-Footnote-345138515
Ref: IDLE<47>-Footnote-355138580
Ref: IDLE<47>-Footnote-365138646
Ref: IDLE<47>-Footnote-375138712
Ref: IDLE<47>-Footnote-385138778
Ref: IDLE<47>-Footnote-395138844
Ref: IDLE<47>-Footnote-405138910
Ref: IDLE<47>-Footnote-415138976
Ref: IDLE<47>-Footnote-425139042
Ref: IDLE<47>-Footnote-435139108
Node: Tools/Demos<33>5139173
Ref: whatsnew/changelog id5675139274
Ref: 19fa5139274
Ref: Tools/Demos<33>-Footnote-15139832
Ref: Tools/Demos<33>-Footnote-25139897
Node: Python 3 6 2 final5139939
Ref: whatsnew/changelog python-3-6-2-final5140103
Ref: 19fb5140103
Node: Python 3 6 2 release candidate 25140224
Ref: whatsnew/changelog python-3-6-2-release-candidate-25140388
Ref: 19fc5140388
Node: Security<39>5140535
Ref: whatsnew/changelog id5685140616
Ref: 19fd5140616
Ref: Security<39>-Footnote-15141737
Ref: Security<39>-Footnote-25141802
Ref: Security<39>-Footnote-35141867
Ref: Security<39>-Footnote-45141936
Ref: Security<39>-Footnote-55142005
Ref: Security<39>-Footnote-65142074
Ref: Security<39>-Footnote-75142143
Ref: Security<39>-Footnote-85142212
Ref: Security<39>-Footnote-95142281
Node: Python 3 6 2 release candidate 15142346
Ref: whatsnew/changelog python-3-6-2-release-candidate-15142510
Ref: 19fe5142510
Node: Security<40>5142895
Ref: whatsnew/changelog id5695143006
Ref: 19ff5143006
Ref: Security<40>-Footnote-15143279
Ref: Security<40>-Footnote-25143344
Ref: Security<40>-Footnote-35143413
Node: Core and Builtins<64>5143482
Ref: whatsnew/changelog id5705143613
Ref: 1a005143613
Ref: Core and Builtins<64>-Footnote-15145587
Ref: Core and Builtins<64>-Footnote-25145652
Ref: Core and Builtins<64>-Footnote-35145717
Ref: Core and Builtins<64>-Footnote-45145782
Ref: Core and Builtins<64>-Footnote-55145847
Ref: Core and Builtins<64>-Footnote-65145912
Ref: Core and Builtins<64>-Footnote-75145977
Ref: Core and Builtins<64>-Footnote-85146042
Ref: Core and Builtins<64>-Footnote-95146107
Ref: Core and Builtins<64>-Footnote-105146172
Ref: Core and Builtins<64>-Footnote-115146238
Ref: Core and Builtins<64>-Footnote-125146304
Ref: Core and Builtins<64>-Footnote-135146370
Ref: Core and Builtins<64>-Footnote-145146436
Ref: Core and Builtins<64>-Footnote-155146502
Node: Library<65>5146568
Ref: whatsnew/changelog id5715146695
Ref: 1a015146695
Ref: Library<65>-Footnote-15155093
Ref: Library<65>-Footnote-25155158
Ref: Library<65>-Footnote-35155223
Ref: Library<65>-Footnote-45155288
Ref: Library<65>-Footnote-55155353
Ref: Library<65>-Footnote-65155418
Ref: Library<65>-Footnote-75155483
Ref: Library<65>-Footnote-85155548
Ref: Library<65>-Footnote-95155613
Ref: Library<65>-Footnote-105155678
Ref: Library<65>-Footnote-115155744
Ref: Library<65>-Footnote-125155810
Ref: Library<65>-Footnote-135155876
Ref: Library<65>-Footnote-145155942
Ref: Library<65>-Footnote-155156008
Ref: Library<65>-Footnote-165156074
Ref: Library<65>-Footnote-175156140
Ref: Library<65>-Footnote-185156206
Ref: Library<65>-Footnote-195156272
Ref: Library<65>-Footnote-205156338
Ref: Library<65>-Footnote-215156404
Ref: Library<65>-Footnote-225156470
Ref: Library<65>-Footnote-235156536
Ref: Library<65>-Footnote-245156602
Ref: Library<65>-Footnote-255156668
Ref: Library<65>-Footnote-265156734
Ref: Library<65>-Footnote-275156800
Ref: Library<65>-Footnote-285156866
Ref: Library<65>-Footnote-295156932
Ref: Library<65>-Footnote-305156998
Ref: Library<65>-Footnote-315157064
Ref: Library<65>-Footnote-325157130
Ref: Library<65>-Footnote-335157196
Ref: Library<65>-Footnote-345157262
Ref: Library<65>-Footnote-355157328
Ref: Library<65>-Footnote-365157394
Ref: Library<65>-Footnote-375157460
Ref: Library<65>-Footnote-385157526
Ref: Library<65>-Footnote-395157592
Ref: Library<65>-Footnote-405157658
Ref: Library<65>-Footnote-415157724
Ref: Library<65>-Footnote-425157790
Ref: Library<65>-Footnote-435157856
Ref: Library<65>-Footnote-445157922
Ref: Library<65>-Footnote-455157988
Ref: Library<65>-Footnote-465158054
Ref: Library<65>-Footnote-475158120
Ref: Library<65>-Footnote-485158186
Ref: Library<65>-Footnote-495158252
Ref: Library<65>-Footnote-505158318
Ref: Library<65>-Footnote-515158384
Ref: Library<65>-Footnote-525158450
Ref: Library<65>-Footnote-535158516
Ref: Library<65>-Footnote-545158582
Ref: Library<65>-Footnote-555158648
Ref: Library<65>-Footnote-565158713
Ref: Library<65>-Footnote-575158779
Ref: Library<65>-Footnote-585158845
Ref: Library<65>-Footnote-595158911
Ref: Library<65>-Footnote-605158977
Node: IDLE<48>5159043
Ref: whatsnew/changelog id5725159158
Ref: 1a025159158
Ref: IDLE<48>-Footnote-15160161
Ref: IDLE<48>-Footnote-25160226
Ref: IDLE<48>-Footnote-35160291
Ref: IDLE<48>-Footnote-45160356
Ref: IDLE<48>-Footnote-55160421
Ref: IDLE<48>-Footnote-65160486
Node: C API<57>5160551
Ref: whatsnew/changelog id5735160664
Ref: 1a035160664
Ref: C API<57>-Footnote-15160852
Node: Build<63>5160917
Ref: whatsnew/changelog id5745161039
Ref: 1a045161039
Ref: Build<63>-Footnote-15161844
Ref: Build<63>-Footnote-25161909
Ref: Build<63>-Footnote-35161974
Ref: Build<63>-Footnote-45162039
Ref: Build<63>-Footnote-55162104
Node: Documentation<58>5162169
Ref: whatsnew/changelog id5755162297
Ref: 1a055162297
Ref: Documentation<58>-Footnote-15163026
Ref: Documentation<58>-Footnote-25163091
Ref: Documentation<58>-Footnote-35163156
Node: Tools/Demos<34>5163221
Ref: whatsnew/changelog id5765163349
Ref: 1a065163349
Ref: Tools/Demos<34>-Footnote-15163539
Node: Tests<59>5163604
Ref: whatsnew/changelog id5775163726
Ref: 1a075163726
Ref: Tests<59>-Footnote-15164381
Ref: Tests<59>-Footnote-25164446
Node: Windows<56>5164511
Ref: whatsnew/changelog id5785164609
Ref: 1a085164609
Ref: Windows<56>-Footnote-15165053
Ref: Windows<56>-Footnote-25165118
Node: Python 3 6 1 final5165183
Ref: whatsnew/changelog python-3-6-1-final5165347
Ref: 1a095165347
Node: Core and Builtins<65>5165504
Ref: whatsnew/changelog id5795165598
Ref: 1a0a5165598
Ref: Core and Builtins<65>-Footnote-15166215
Ref: Core and Builtins<65>-Footnote-25166280
Node: Build<64>5166345
Ref: whatsnew/changelog id5805166439
Ref: 1a0b5166439
Ref: Build<64>-Footnote-15166621
Node: Python 3 6 1 release candidate 15166686
Ref: whatsnew/changelog python-3-6-1-release-candidate-15166836
Ref: 1a0c5166836
Node: Core and Builtins<66>5167163
Ref: whatsnew/changelog id5815167273
Ref: 1a0d5167273
Ref: Core and Builtins<66>-Footnote-15170105
Ref: Core and Builtins<66>-Footnote-25170170
Ref: Core and Builtins<66>-Footnote-35170235
Ref: Core and Builtins<66>-Footnote-45170300
Ref: Core and Builtins<66>-Footnote-55170365
Ref: Core and Builtins<66>-Footnote-65170430
Ref: Core and Builtins<66>-Footnote-75170495
Ref: Core and Builtins<66>-Footnote-85170560
Ref: Core and Builtins<66>-Footnote-95170625
Ref: Core and Builtins<66>-Footnote-105170690
Ref: Core and Builtins<66>-Footnote-115170756
Ref: Core and Builtins<66>-Footnote-125170822
Ref: Core and Builtins<66>-Footnote-135170888
Ref: Core and Builtins<66>-Footnote-145170954
Ref: Core and Builtins<66>-Footnote-155171020
Ref: Core and Builtins<66>-Footnote-165171086
Ref: Core and Builtins<66>-Footnote-175171152
Ref: Core and Builtins<66>-Footnote-185171218
Ref: Core and Builtins<66>-Footnote-195171284
Ref: Core and Builtins<66>-Footnote-205171350
Ref: Core and Builtins<66>-Footnote-215171416
Ref: Core and Builtins<66>-Footnote-225171482
Node: Library<66>5171548
Ref: whatsnew/changelog id5825171675
Ref: 1a0e5171675
Ref: Library<66>-Footnote-15177310
Ref: Library<66>-Footnote-25177375
Ref: Library<66>-Footnote-35177440
Ref: Library<66>-Footnote-45177505
Ref: Library<66>-Footnote-55177570
Ref: Library<66>-Footnote-65177635
Ref: Library<66>-Footnote-75177700
Ref: Library<66>-Footnote-85177765
Ref: Library<66>-Footnote-95177830
Ref: Library<66>-Footnote-105177895
Ref: Library<66>-Footnote-115177961
Ref: Library<66>-Footnote-125178027
Ref: Library<66>-Footnote-135178093
Ref: Library<66>-Footnote-145178159
Ref: Library<66>-Footnote-155178225
Ref: Library<66>-Footnote-165178291
Ref: Library<66>-Footnote-175178357
Ref: Library<66>-Footnote-185178423
Ref: Library<66>-Footnote-195178489
Ref: Library<66>-Footnote-205178555
Ref: Library<66>-Footnote-215178621
Ref: Library<66>-Footnote-225178687
Ref: Library<66>-Footnote-235178753
Ref: Library<66>-Footnote-245178819
Ref: Library<66>-Footnote-255178885
Ref: Library<66>-Footnote-265178951
Ref: Library<66>-Footnote-275179017
Ref: Library<66>-Footnote-285179060
Ref: Library<66>-Footnote-295179126
Ref: Library<66>-Footnote-305179192
Ref: Library<66>-Footnote-315179258
Ref: Library<66>-Footnote-325179324
Ref: Library<66>-Footnote-335179390
Ref: Library<66>-Footnote-345179456
Ref: Library<66>-Footnote-355179522
Ref: Library<66>-Footnote-365179587
Ref: Library<66>-Footnote-375179653
Ref: Library<66>-Footnote-385179719
Ref: Library<66>-Footnote-395179785
Ref: Library<66>-Footnote-405179851
Ref: Library<66>-Footnote-415179917
Ref: Library<66>-Footnote-425179983
Ref: Library<66>-Footnote-435180049
Ref: Library<66>-Footnote-445180115
Node: IDLE<49>5180181
Ref: whatsnew/changelog id5835180298
Ref: 1a0f5180298
Ref: IDLE<49>-Footnote-15180585
Ref: IDLE<49>-Footnote-25180650
Node: Windows<57>5180715
Ref: whatsnew/changelog id5845180830
Ref: 1a105180830
Ref: Windows<57>-Footnote-15181477
Ref: Windows<57>-Footnote-25181542
Ref: Windows<57>-Footnote-35181607
Ref: Windows<57>-Footnote-45181672
Ref: Windows<57>-Footnote-55181737
Ref: Windows<57>-Footnote-65181779
Ref: Windows<57>-Footnote-75181844
Ref: Windows<57>-Footnote-85181909
Node: C API<58>5181974
Ref: whatsnew/changelog id5855182098
Ref: 1a115182098
Ref: C API<58>-Footnote-15182924
Ref: C API<58>-Footnote-25182989
Ref: C API<58>-Footnote-35183054
Node: Documentation<59>5183119
Ref: whatsnew/changelog id5865183241
Ref: 1a125183241
Ref: Documentation<59>-Footnote-15183778
Ref: Documentation<59>-Footnote-25183843
Ref: Documentation<59>-Footnote-35183908
Ref: Documentation<59>-Footnote-45183973
Node: Tests<60>5184038
Ref: whatsnew/changelog id5875184160
Ref: 1a135184160
Ref: Tests<60>-Footnote-15185145
Ref: Tests<60>-Footnote-25185210
Ref: Tests<60>-Footnote-35185275
Ref: Tests<60>-Footnote-45185340
Ref: Tests<60>-Footnote-55185405
Node: Build<65>5185470
Ref: whatsnew/changelog id5885185566
Ref: 1a145185566
Ref: Build<65>-Footnote-15186827
Ref: Build<65>-Footnote-25186892
Ref: Build<65>-Footnote-35186957
Ref: Build<65>-Footnote-45187022
Ref: Build<65>-Footnote-55187087
Ref: Build<65>-Footnote-65187152
Ref: Build<65>-Footnote-75187217
Ref: Build<65>-Footnote-85187282
Ref: Build<65>-Footnote-95187347
Ref: Build<65>-Footnote-105187412
Node: Python 3 6 0 final5187478
Ref: whatsnew/changelog python-3-6-0-final5187642
Ref: 1a155187642
Node: Python 3 6 0 release candidate 25187763
Ref: whatsnew/changelog python-3-6-0-release-candidate-25187927
Ref: 1a165187927
Node: Core and Builtins<67>5188168
Ref: whatsnew/changelog id5895188282
Ref: 1a175188282
Ref: Core and Builtins<67>-Footnote-15188667
Ref: Core and Builtins<67>-Footnote-25188732
Node: Tools/Demos<35>5188797
Ref: whatsnew/changelog id5905188931
Ref: 1a185188931
Ref: Tools/Demos<35>-Footnote-15189065
Node: Windows<58>5189130
Ref: whatsnew/changelog id5915189252
Ref: 1a195189252
Ref: Windows<58>-Footnote-15189378
Node: Build<66>5189443
Ref: whatsnew/changelog id5925189541
Ref: 1a1a5189541
Ref: Build<66>-Footnote-15189696
Node: Python 3 6 0 release candidate 15189761
Ref: whatsnew/changelog python-3-6-0-release-candidate-15189926
Ref: 1a1b5189926
Node: Core and Builtins<68>5190203
Ref: whatsnew/changelog id5935190313
Ref: 1a1c5190313
Ref: Core and Builtins<68>-Footnote-15191120
Ref: Core and Builtins<68>-Footnote-25191185
Ref: Core and Builtins<68>-Footnote-35191250
Ref: Core and Builtins<68>-Footnote-45191315
Node: Library<67>5191380
Ref: whatsnew/changelog id5945191508
Ref: 1a1d5191508
Ref: Library<67>-Footnote-15192547
Ref: Library<67>-Footnote-25192612
Ref: Library<67>-Footnote-35192677
Ref: Library<67>-Footnote-45192742
Ref: Library<67>-Footnote-55192807
Ref: Library<67>-Footnote-65192872
Node: C API<59>5192937
Ref: whatsnew/changelog id5955193061
Ref: 1a1e5193061
Ref: C API<59>-Footnote-15193219
Node: Documentation<60>5193284
Ref: whatsnew/changelog id5965193412
Ref: 1a1f5193412
Ref: Documentation<60>-Footnote-15193750
Ref: Documentation<60>-Footnote-25193815
Node: Tools/Demos<36>5193857
Ref: whatsnew/changelog id5975193967
Ref: 1a205193967
Ref: Tools/Demos<36>-Footnote-15194131
Node: Python 3 6 0 beta 45194196
Ref: whatsnew/changelog python-3-6-0-beta-45194348
Ref: 1a215194348
Node: Core and Builtins<69>5194587
Ref: whatsnew/changelog id5985194684
Ref: 1a225194684
Ref: Core and Builtins<69>-Footnote-15196232
Ref: Core and Builtins<69>-Footnote-25196297
Ref: Core and Builtins<69>-Footnote-35196362
Ref: Core and Builtins<69>-Footnote-45196427
Ref: Core and Builtins<69>-Footnote-55196492
Ref: Core and Builtins<69>-Footnote-65196557
Ref: Core and Builtins<69>-Footnote-75196622
Ref: Core and Builtins<69>-Footnote-85196687
Ref: Core and Builtins<69>-Footnote-95196752
Ref: Core and Builtins<69>-Footnote-105196817
Ref: Core and Builtins<69>-Footnote-115196883
Node: Library<68>5196949
Ref: whatsnew/changelog id5995197072
Ref: 1a235197072
Ref: Library<68>-Footnote-15199070
Ref: Library<68>-Footnote-25199135
Ref: Library<68>-Footnote-35199200
Ref: Library<68>-Footnote-45199265
Ref: Library<68>-Footnote-55199330
Ref: Library<68>-Footnote-65199395
Ref: Library<68>-Footnote-75199460
Ref: Library<68>-Footnote-85199525
Ref: Library<68>-Footnote-95199590
Ref: Library<68>-Footnote-105199655
Ref: Library<68>-Footnote-115199721
Ref: Library<68>-Footnote-125199787
Ref: Library<68>-Footnote-135199853
Ref: Library<68>-Footnote-145199919
Ref: Library<68>-Footnote-155199985
Ref: Library<68>-Footnote-165200051
Ref: Library<68>-Footnote-175200117
Ref: Library<68>-Footnote-185200183
Node: Documentation<61>5200249
Ref: whatsnew/changelog id6005200360
Ref: 1a245200360
Ref: Documentation<61>-Footnote-15200511
Node: Tests<61>5200576
Ref: whatsnew/changelog id6015200685
Ref: 1a255200685
Ref: Tests<61>-Footnote-15200947
Ref: Tests<61>-Footnote-25201012
Node: Build<67>5201077
Ref: whatsnew/changelog id6025201160
Ref: 1a265201160
Ref: Build<67>-Footnote-15201515
Ref: Build<67>-Footnote-25201580
Ref: Build<67>-Footnote-35201645
Node: Python 3 6 0 beta 35201710
Ref: whatsnew/changelog python-3-6-0-beta-35201849
Ref: 1a275201849
Node: Core and Builtins<70>5202076
Ref: whatsnew/changelog id6035202173
Ref: 1a285202173
Ref: Core and Builtins<70>-Footnote-15203076
Ref: Core and Builtins<70>-Footnote-25203141
Ref: Core and Builtins<70>-Footnote-35203206
Ref: Core and Builtins<70>-Footnote-45203271
Ref: Core and Builtins<70>-Footnote-55203336
Ref: Core and Builtins<70>-Footnote-65203401
Ref: Core and Builtins<70>-Footnote-75203466
Node: Library<69>5203531
Ref: whatsnew/changelog id6045203648
Ref: 1a295203648
Ref: Library<69>-Footnote-15206670
Ref: Library<69>-Footnote-25206735
Ref: Library<69>-Footnote-35206800
Ref: Library<69>-Footnote-45206865
Ref: Library<69>-Footnote-55206930
Ref: Library<69>-Footnote-65206995
Ref: Library<69>-Footnote-75207060
Ref: Library<69>-Footnote-85207125
Ref: Library<69>-Footnote-95207190
Ref: Library<69>-Footnote-105207255
Ref: Library<69>-Footnote-115207321
Ref: Library<69>-Footnote-125207387
Ref: Library<69>-Footnote-135207453
Ref: Library<69>-Footnote-145207519
Ref: Library<69>-Footnote-155207585
Ref: Library<69>-Footnote-165207651
Ref: Library<69>-Footnote-175207717
Ref: Library<69>-Footnote-185207783
Ref: Library<69>-Footnote-195207849
Ref: Library<69>-Footnote-205207915
Ref: Library<69>-Footnote-215207981
Ref: Library<69>-Footnote-225208047
Ref: Library<69>-Footnote-235208113
Ref: Library<69>-Footnote-245208179
Node: Windows<59>5208245
Ref: whatsnew/changelog id6055208350
Ref: 1a2a5208350
Ref: Windows<59>-Footnote-15208494
Node: Build<68>5208559
Ref: whatsnew/changelog id6065208662
Ref: 1a2b5208662
Ref: Build<68>-Footnote-15208981
Ref: Build<68>-Footnote-25209046
Ref: Build<68>-Footnote-35209111
Node: Tests<62>5209176
Ref: whatsnew/changelog id6075209259
Ref: 1a2c5209259
Ref: Tests<62>-Footnote-15209514
Ref: Tests<62>-Footnote-25209579
Node: Python 3 6 0 beta 25209644
Ref: whatsnew/changelog python-3-6-0-beta-25209783
Ref: 1a2d5209783
Node: Core and Builtins<71>5210030
Ref: whatsnew/changelog id6085210127
Ref: 1a2e5210127
Ref: Core and Builtins<71>-Footnote-15212863
Ref: Core and Builtins<71>-Footnote-25212928
Ref: Core and Builtins<71>-Footnote-35212993
Ref: Core and Builtins<71>-Footnote-45213058
Ref: Core and Builtins<71>-Footnote-55213123
Ref: Core and Builtins<71>-Footnote-65213188
Ref: Core and Builtins<71>-Footnote-75213253
Ref: Core and Builtins<71>-Footnote-85213318
Ref: Core and Builtins<71>-Footnote-95213383
Ref: Core and Builtins<71>-Footnote-105213448
Ref: Core and Builtins<71>-Footnote-115213514
Ref: Core and Builtins<71>-Footnote-125213580
Ref: Core and Builtins<71>-Footnote-135213646
Ref: Core and Builtins<71>-Footnote-145213712
Ref: Core and Builtins<71>-Footnote-155213778
Ref: Core and Builtins<71>-Footnote-165213844
Ref: Core and Builtins<71>-Footnote-175213910
Ref: Core and Builtins<71>-Footnote-185213976
Ref: Core and Builtins<71>-Footnote-195214042
Ref: Core and Builtins<71>-Footnote-205214108
Ref: Core and Builtins<71>-Footnote-215214174
Ref: Core and Builtins<71>-Footnote-225214240
Ref: Core and Builtins<71>-Footnote-235214306
Node: Library<70>5214372
Ref: whatsnew/changelog id6095214489
Ref: 1a2f5214489
Ref: Library<70>-Footnote-15220269
Ref: Library<70>-Footnote-25220334
Ref: Library<70>-Footnote-35220399
Ref: Library<70>-Footnote-45220464
Ref: Library<70>-Footnote-55220529
Ref: Library<70>-Footnote-65220594
Ref: Library<70>-Footnote-75220659
Ref: Library<70>-Footnote-85220724
Ref: Library<70>-Footnote-95220789
Ref: Library<70>-Footnote-105220854
Ref: Library<70>-Footnote-115220920
Ref: Library<70>-Footnote-125220986
Ref: Library<70>-Footnote-135221052
Ref: Library<70>-Footnote-145221118
Ref: Library<70>-Footnote-155221184
Ref: Library<70>-Footnote-165221250
Ref: Library<70>-Footnote-175221316
Ref: Library<70>-Footnote-185221382
Ref: Library<70>-Footnote-195221448
Ref: Library<70>-Footnote-205221514
Ref: Library<70>-Footnote-215221580
Ref: Library<70>-Footnote-225221646
Ref: Library<70>-Footnote-235221712
Ref: Library<70>-Footnote-245221778
Ref: Library<70>-Footnote-255221844
Ref: Library<70>-Footnote-265221910
Ref: Library<70>-Footnote-275221976
Ref: Library<70>-Footnote-285222042
Ref: Library<70>-Footnote-295222108
Ref: Library<70>-Footnote-305222174
Ref: Library<70>-Footnote-315222240
Ref: Library<70>-Footnote-325222306
Ref: Library<70>-Footnote-335222372
Ref: Library<70>-Footnote-345222438
Ref: Library<70>-Footnote-355222504
Ref: Library<70>-Footnote-365222570
Ref: Library<70>-Footnote-375222636
Ref: Library<70>-Footnote-385222702
Ref: Library<70>-Footnote-395222768
Ref: Library<70>-Footnote-405222834
Ref: Library<70>-Footnote-415222900
Ref: Library<70>-Footnote-425222966
Ref: Library<70>-Footnote-435223032
Ref: Library<70>-Footnote-445223098
Ref: Library<70>-Footnote-455223164
Ref: Library<70>-Footnote-465223230
Ref: Library<70>-Footnote-475223296
Ref: Library<70>-Footnote-485223362
Node: Windows<60>5223428
Ref: whatsnew/changelog id6105223533
Ref: 1a305223533
Ref: Windows<60>-Footnote-15224344
Ref: Windows<60>-Footnote-25224409
Ref: Windows<60>-Footnote-35224474
Ref: Windows<60>-Footnote-45224539
Ref: Windows<60>-Footnote-55224604
Ref: Windows<60>-Footnote-65224669
Ref: Windows<60>-Footnote-75224734
Ref: Windows<60>-Footnote-85224799
Ref: Windows<60>-Footnote-95224864
Ref: Windows<60>-Footnote-105224929
Node: C API<60>5224995
Ref: whatsnew/changelog id6115225098
Ref: 1a315225098
Ref: C API<60>-Footnote-15225352
Node: Build<69>5225417
Ref: whatsnew/changelog id6125225518
Ref: 1a325225518
Ref: Build<69>-Footnote-15225944
Ref: Build<69>-Footnote-25226009
Ref: Build<69>-Footnote-35226074
Node: Tests<63>5226139
Ref: whatsnew/changelog id6135226222
Ref: 1a335226222
Ref: Tests<63>-Footnote-15226359
Node: Python 3 6 0 beta 15226424
Ref: whatsnew/changelog python-3-6-0-beta-15226564
Ref: 1a345226564
Node: Core and Builtins<72>5226861
Ref: whatsnew/changelog id6145226958
Ref: 1a355226958
Ref: Core and Builtins<72>-Footnote-15233125
Ref: Core and Builtins<72>-Footnote-25233190
Ref: Core and Builtins<72>-Footnote-35233255
Ref: Core and Builtins<72>-Footnote-45233320
Ref: Core and Builtins<72>-Footnote-55233362
Ref: Core and Builtins<72>-Footnote-65233427
Ref: Core and Builtins<72>-Footnote-75233492
Ref: Core and Builtins<72>-Footnote-85233557
Ref: Core and Builtins<72>-Footnote-95233622
Ref: Core and Builtins<72>-Footnote-105233687
Ref: Core and Builtins<72>-Footnote-115233753
Ref: Core and Builtins<72>-Footnote-125233819
Ref: Core and Builtins<72>-Footnote-135233885
Ref: Core and Builtins<72>-Footnote-145233928
Ref: Core and Builtins<72>-Footnote-155233994
Ref: Core and Builtins<72>-Footnote-165234060
Ref: Core and Builtins<72>-Footnote-175234103
Ref: Core and Builtins<72>-Footnote-185234169
Ref: Core and Builtins<72>-Footnote-195234212
Ref: Core and Builtins<72>-Footnote-205234278
Ref: Core and Builtins<72>-Footnote-215234344
Ref: Core and Builtins<72>-Footnote-225234410
Ref: Core and Builtins<72>-Footnote-235234476
Ref: Core and Builtins<72>-Footnote-245234542
Ref: Core and Builtins<72>-Footnote-255234608
Ref: Core and Builtins<72>-Footnote-265234674
Ref: Core and Builtins<72>-Footnote-275234740
Ref: Core and Builtins<72>-Footnote-285234783
Ref: Core and Builtins<72>-Footnote-295234849
Ref: Core and Builtins<72>-Footnote-305234915
Ref: Core and Builtins<72>-Footnote-315234981
Ref: Core and Builtins<72>-Footnote-325235047
Ref: Core and Builtins<72>-Footnote-335235113
Ref: Core and Builtins<72>-Footnote-345235179
Ref: Core and Builtins<72>-Footnote-355235245
Ref: Core and Builtins<72>-Footnote-365235311
Ref: Core and Builtins<72>-Footnote-375235377
Ref: Core and Builtins<72>-Footnote-385235443
Ref: Core and Builtins<72>-Footnote-395235509
Ref: Core and Builtins<72>-Footnote-405235575
Ref: Core and Builtins<72>-Footnote-415235641
Ref: Core and Builtins<72>-Footnote-425235707
Ref: Core and Builtins<72>-Footnote-435235773
Ref: Core and Builtins<72>-Footnote-445235839
Ref: Core and Builtins<72>-Footnote-455235905
Ref: Core and Builtins<72>-Footnote-465235971
Ref: Core and Builtins<72>-Footnote-475236014
Node: Library<71>5236080
Ref: whatsnew/changelog id6155236194
Ref: 1a365236194
Ref: Library<71>-Footnote-15247136
Ref: Library<71>-Footnote-25247201
Ref: Library<71>-Footnote-35247266
Ref: Library<71>-Footnote-45247331
Ref: Library<71>-Footnote-55247396
Ref: Library<71>-Footnote-65247461
Ref: Library<71>-Footnote-75247526
Ref: Library<71>-Footnote-85247591
Ref: Library<71>-Footnote-95247656
Ref: Library<71>-Footnote-105247721
Ref: Library<71>-Footnote-115247787
Ref: Library<71>-Footnote-125247853
Ref: Library<71>-Footnote-135247919
Ref: Library<71>-Footnote-145247985
Ref: Library<71>-Footnote-155248051
Ref: Library<71>-Footnote-165248117
Ref: Library<71>-Footnote-175248183
Ref: Library<71>-Footnote-185248251
Ref: Library<71>-Footnote-195248317
Ref: Library<71>-Footnote-205248383
Ref: Library<71>-Footnote-215248449
Ref: Library<71>-Footnote-225248515
Ref: Library<71>-Footnote-235248581
Ref: Library<71>-Footnote-245248647
Ref: Library<71>-Footnote-255248713
Ref: Library<71>-Footnote-265248780
Ref: Library<71>-Footnote-275248846
Ref: Library<71>-Footnote-285248912
Ref: Library<71>-Footnote-295248978
Ref: Library<71>-Footnote-305249044
Ref: Library<71>-Footnote-315249110
Ref: Library<71>-Footnote-325249176
Ref: Library<71>-Footnote-335249242
Ref: Library<71>-Footnote-345249308
Ref: Library<71>-Footnote-355249374
Ref: Library<71>-Footnote-365249440
Ref: Library<71>-Footnote-375249506
Ref: Library<71>-Footnote-385249572
Ref: Library<71>-Footnote-395249638
Ref: Library<71>-Footnote-405249704
Ref: Library<71>-Footnote-415249770
Ref: Library<71>-Footnote-425249836
Ref: Library<71>-Footnote-435249879
Ref: Library<71>-Footnote-445249945
Ref: Library<71>-Footnote-455249988
Ref: Library<71>-Footnote-465250054
Ref: Library<71>-Footnote-475250120
Ref: Library<71>-Footnote-485250186
Ref: Library<71>-Footnote-495250252
Ref: Library<71>-Footnote-505250318
Ref: Library<71>-Footnote-515250384
Ref: Library<71>-Footnote-525250450
Ref: Library<71>-Footnote-535250516
Ref: Library<71>-Footnote-545250586
Ref: Library<71>-Footnote-555250652
Ref: Library<71>-Footnote-565250718
Ref: Library<71>-Footnote-575250784
Ref: Library<71>-Footnote-585250850
Ref: Library<71>-Footnote-595250916
Ref: Library<71>-Footnote-605250982
Ref: Library<71>-Footnote-615251048
Ref: Library<71>-Footnote-625251114
Ref: Library<71>-Footnote-635251180
Ref: Library<71>-Footnote-645251246
Ref: Library<71>-Footnote-655251312
Ref: Library<71>-Footnote-665251378
Ref: Library<71>-Footnote-675251444
Ref: Library<71>-Footnote-685251510
Ref: Library<71>-Footnote-695251576
Ref: Library<71>-Footnote-705251642
Ref: Library<71>-Footnote-715251708
Ref: Library<71>-Footnote-725251774
Ref: Library<71>-Footnote-735251840
Ref: Library<71>-Footnote-745251906
Ref: Library<71>-Footnote-755251972
Ref: Library<71>-Footnote-765252038
Ref: Library<71>-Footnote-775252103
Ref: Library<71>-Footnote-785252168
Ref: Library<71>-Footnote-795252234
Ref: Library<71>-Footnote-805252300
Ref: Library<71>-Footnote-815252365
Ref: Library<71>-Footnote-825252431
Node: IDLE<50>5252497
Ref: whatsnew/changelog id6165252599
Ref: 1a375252599
Ref: IDLE<50>-Footnote-15253355
Ref: IDLE<50>-Footnote-25253420
Ref: IDLE<50>-Footnote-35253485
Ref: IDLE<50>-Footnote-45253550
Ref: IDLE<50>-Footnote-55253615
Ref: IDLE<50>-Footnote-65253680
Node: C API<61>5253745
Ref: whatsnew/changelog id6175253845
Ref: 1a385253845
Ref: C API<61>-Footnote-15254117
Ref: C API<61>-Footnote-25254182
Node: Tests<64>5254247
Ref: whatsnew/changelog id6185254348
Ref: 1a395254348
Ref: Tests<64>-Footnote-15254864
Ref: Tests<64>-Footnote-25254929
Ref: Tests<64>-Footnote-35254994
Ref: Tests<64>-Footnote-45255059
Node: Build<70>5255124
Ref: whatsnew/changelog id6195255231
Ref: 1a3a5255231
Ref: Build<70>-Footnote-15256614
Ref: Build<70>-Footnote-25256679
Ref: Build<70>-Footnote-35256744
Ref: Build<70>-Footnote-45256809
Ref: Build<70>-Footnote-55256874
Ref: Build<70>-Footnote-65256939
Ref: Build<70>-Footnote-75257004
Ref: Build<70>-Footnote-85257069
Ref: Build<70>-Footnote-95257134
Ref: Build<70>-Footnote-105257199
Ref: Build<70>-Footnote-115257265
Node: Tools/Demos<37>5257331
Ref: whatsnew/changelog id6205257440
Ref: 1a3b5257440
Ref: Tools/Demos<37>-Footnote-15257715
Node: Windows<61>5257780
Ref: whatsnew/changelog id6215257871
Ref: 1a3c5257871
Ref: Windows<61>-Footnote-15258838
Ref: Windows<61>-Footnote-25258903
Ref: Windows<61>-Footnote-35258968
Ref: Windows<61>-Footnote-45259032
Ref: Windows<61>-Footnote-55259097
Ref: Windows<61>-Footnote-65259162
Ref: Windows<61>-Footnote-75259226
Ref: Windows<61>-Footnote-85259291
Ref: Windows<61>-Footnote-95259356
Ref: Windows<61>-Footnote-105259421
Ref: Windows<61>-Footnote-115259487
Node: Python 3 6 0 alpha 45259553
Ref: whatsnew/changelog python-3-6-0-alpha-45259694
Ref: 1a3d5259694
Node: Core and Builtins<73>5259941
Ref: whatsnew/changelog id6225260039
Ref: 1a3e5260039
Ref: Core and Builtins<73>-Footnote-15261983
Ref: Core and Builtins<73>-Footnote-25262048
Ref: Core and Builtins<73>-Footnote-35262113
Ref: Core and Builtins<73>-Footnote-45262178
Ref: Core and Builtins<73>-Footnote-55262243
Ref: Core and Builtins<73>-Footnote-65262308
Ref: Core and Builtins<73>-Footnote-75262373
Ref: Core and Builtins<73>-Footnote-85262438
Ref: Core and Builtins<73>-Footnote-95262503
Ref: Core and Builtins<73>-Footnote-105262567
Ref: Core and Builtins<73>-Footnote-115262633
Ref: Core and Builtins<73>-Footnote-125262699
Ref: Core and Builtins<73>-Footnote-135262765
Ref: Core and Builtins<73>-Footnote-145262831
Node: Library<72>5262874
Ref: whatsnew/changelog id6235262989
Ref: 1a3f5262989
Ref: Library<72>-Footnote-15267479
Ref: Library<72>-Footnote-25267544
Ref: Library<72>-Footnote-35267586
Ref: Library<72>-Footnote-45267651
Ref: Library<72>-Footnote-55267716
Ref: Library<72>-Footnote-65267781
Ref: Library<72>-Footnote-75267846
Ref: Library<72>-Footnote-85267911
Ref: Library<72>-Footnote-95267976
Ref: Library<72>-Footnote-105268041
Ref: Library<72>-Footnote-115268107
Ref: Library<72>-Footnote-125268150
Ref: Library<72>-Footnote-135268216
Ref: Library<72>-Footnote-145268282
Ref: Library<72>-Footnote-155268348
Ref: Library<72>-Footnote-165268414
Ref: Library<72>-Footnote-175268479
Ref: Library<72>-Footnote-185268545
Ref: Library<72>-Footnote-195268611
Ref: Library<72>-Footnote-205268677
Ref: Library<72>-Footnote-215268743
Ref: Library<72>-Footnote-225268809
Ref: Library<72>-Footnote-235268875
Ref: Library<72>-Footnote-245268941
Ref: Library<72>-Footnote-255269007
Ref: Library<72>-Footnote-265269073
Ref: Library<72>-Footnote-275269139
Ref: Library<72>-Footnote-285269205
Ref: Library<72>-Footnote-295269278
Ref: Library<72>-Footnote-305269343
Ref: Library<72>-Footnote-315269409
Ref: Library<72>-Footnote-325269475
Ref: Library<72>-Footnote-335269541
Ref: Library<72>-Footnote-345269584
Ref: Library<72>-Footnote-355269650
Ref: Library<72>-Footnote-365269715
Ref: Library<72>-Footnote-375269781
Ref: Library<72>-Footnote-385269847
Ref: Library<72>-Footnote-395269913
Node: IDLE<51>5269979
Ref: whatsnew/changelog id6245270082
Ref: 1a405270082
Ref: IDLE<51>-Footnote-15271402
Ref: IDLE<51>-Footnote-25271467
Ref: IDLE<51>-Footnote-35271532
Ref: IDLE<51>-Footnote-45271597
Ref: IDLE<51>-Footnote-55271662
Ref: IDLE<51>-Footnote-65271727
Ref: IDLE<51>-Footnote-75271792
Ref: IDLE<51>-Footnote-85271857
Node: Tests<65>5271922
Ref: whatsnew/changelog id6255272025
Ref: 1a415272025
Ref: Tests<65>-Footnote-15272612
Ref: Tests<65>-Footnote-25272677
Ref: Tests<65>-Footnote-35272742
Ref: Tests<65>-Footnote-45272807
Node: Windows<62>5272872
Ref: whatsnew/changelog id6265272976
Ref: 1a425272976
Ref: Windows<62>-Footnote-15273352
Ref: Windows<62>-Footnote-25273417
Ref: Windows<62>-Footnote-35273482
Ref: Windows<62>-Footnote-45273524
Ref: Windows<62>-Footnote-55273589
Node: Build<71>5273654
Ref: whatsnew/changelog id6275273740
Ref: 1a435273740
Ref: Build<71>-Footnote-15274639
Ref: Build<71>-Footnote-25274704
Ref: Build<71>-Footnote-35274769
Ref: Build<71>-Footnote-45274834
Ref: Build<71>-Footnote-55274899
Ref: Build<71>-Footnote-65274964
Node: Python 3 6 0 alpha 35275029
Ref: whatsnew/changelog python-3-6-0-alpha-35275171
Ref: 1a445275171
Node: Security<41>5275508
Ref: whatsnew/changelog id6285275607
Ref: 1a455275607
Ref: Security<41>-Footnote-15275985
Ref: Security<41>-Footnote-25276050
Node: Core and Builtins<74>5276115
Ref: whatsnew/changelog id6295276234
Ref: 1a465276234
Ref: Core and Builtins<74>-Footnote-15276981
Ref: Core and Builtins<74>-Footnote-25277046
Ref: Core and Builtins<74>-Footnote-35277111
Ref: Core and Builtins<74>-Footnote-45277176
Node: Library<73>5277241
Ref: whatsnew/changelog id6305277356
Ref: 1a475277356
Ref: Library<73>-Footnote-15281439
Ref: Library<73>-Footnote-25281504
Ref: Library<73>-Footnote-35281569
Ref: Library<73>-Footnote-45281634
Ref: Library<73>-Footnote-55281699
Ref: Library<73>-Footnote-65281764
Ref: Library<73>-Footnote-75281829
Ref: Library<73>-Footnote-85281894
Ref: Library<73>-Footnote-95281959
Ref: Library<73>-Footnote-105282024
Ref: Library<73>-Footnote-115282090
Ref: Library<73>-Footnote-125282156
Ref: Library<73>-Footnote-135282222
Ref: Library<73>-Footnote-145282288
Ref: Library<73>-Footnote-155282354
Ref: Library<73>-Footnote-165282420
Ref: Library<73>-Footnote-175282486
Ref: Library<73>-Footnote-185282552
Ref: Library<73>-Footnote-195282618
Ref: Library<73>-Footnote-205282684
Ref: Library<73>-Footnote-215282750
Ref: Library<73>-Footnote-225282793
Ref: Library<73>-Footnote-235282859
Ref: Library<73>-Footnote-245282925
Ref: Library<73>-Footnote-255282990
Ref: Library<73>-Footnote-265283056
Node: IDLE<52>5283122
Ref: whatsnew/changelog id6315283225
Ref: 1a485283225
Ref: IDLE<52>-Footnote-15284881
Ref: IDLE<52>-Footnote-25284946
Ref: IDLE<52>-Footnote-35285011
Ref: IDLE<52>-Footnote-45285076
Ref: IDLE<52>-Footnote-55285141
Ref: IDLE<52>-Footnote-65285206
Ref: IDLE<52>-Footnote-75285271
Ref: IDLE<52>-Footnote-85285336
Ref: IDLE<52>-Footnote-95285401
Ref: IDLE<52>-Footnote-105285466
Node: C API<62>5285532
Ref: whatsnew/changelog id6325285633
Ref: 1a495285633
Ref: C API<62>-Footnote-15285873
Node: Build<72>5285938
Ref: whatsnew/changelog id6335286046
Ref: 1a4a5286046
Ref: Build<72>-Footnote-15287017
Ref: Build<72>-Footnote-25287082
Ref: Build<72>-Footnote-35287147
Ref: Build<72>-Footnote-45287212
Ref: Build<72>-Footnote-55287277
Node: Tools/Demos<38>5287342
Ref: whatsnew/changelog id6345287458
Ref: 1a4b5287458
Ref: Tools/Demos<38>-Footnote-15287742
Ref: Tools/Demos<38>-Footnote-25287807
Node: Documentation<62>5287872
Ref: whatsnew/changelog id6355287988
Ref: 1a4c5287988
Ref: Documentation<62>-Footnote-15288365
Ref: Documentation<62>-Footnote-25288430
Node: Tests<66>5288495
Ref: whatsnew/changelog id6365288587
Ref: 1a4d5288587
Ref: Tests<66>-Footnote-15288755
Node: Python 3 6 0 alpha 25288820
Ref: whatsnew/changelog python-3-6-0-alpha-25288962
Ref: 1a4e5288962
Node: Security<42>5289323
Ref: whatsnew/changelog id6375289422
Ref: 1a4f5289422
Ref: Security<42>-Footnote-15289913
Ref: Security<42>-Footnote-25289978
Ref: Security<42>-Footnote-35290047
Ref: Security<42>-Footnote-45290116
Node: Core and Builtins<75>5290181
Ref: whatsnew/changelog id6385290300
Ref: 1a505290300
Ref: Core and Builtins<75>-Footnote-15291932
Ref: Core and Builtins<75>-Footnote-25291997
Ref: Core and Builtins<75>-Footnote-35292062
Ref: Core and Builtins<75>-Footnote-45292127
Ref: Core and Builtins<75>-Footnote-55292192
Ref: Core and Builtins<75>-Footnote-65292257
Ref: Core and Builtins<75>-Footnote-75292299
Ref: Core and Builtins<75>-Footnote-85292364
Ref: Core and Builtins<75>-Footnote-95292429
Ref: Core and Builtins<75>-Footnote-105292494
Ref: Core and Builtins<75>-Footnote-115292560
Ref: Core and Builtins<75>-Footnote-125292626
Node: Library<74>5292692
Ref: whatsnew/changelog id6395292807
Ref: 1a515292807
Ref: Library<74>-Footnote-15298006
Ref: Library<74>-Footnote-25298071
Ref: Library<74>-Footnote-35298136
Ref: Library<74>-Footnote-45298201
Ref: Library<74>-Footnote-55298266
Ref: Library<74>-Footnote-65298331
Ref: Library<74>-Footnote-75298396
Ref: Library<74>-Footnote-85298461
Ref: Library<74>-Footnote-95298526
Ref: Library<74>-Footnote-105298568
Ref: Library<74>-Footnote-115298634
Ref: Library<74>-Footnote-125298700
Ref: Library<74>-Footnote-135298766
Ref: Library<74>-Footnote-145298809
Ref: Library<74>-Footnote-155298875
Ref: Library<74>-Footnote-165298918
Ref: Library<74>-Footnote-175298961
Ref: Library<74>-Footnote-185299027
Ref: Library<74>-Footnote-195299093
Ref: Library<74>-Footnote-205299159
Ref: Library<74>-Footnote-215299225
Ref: Library<74>-Footnote-225299291
Ref: Library<74>-Footnote-235299357
Ref: Library<74>-Footnote-245299423
Ref: Library<74>-Footnote-255299489
Ref: Library<74>-Footnote-265299555
Ref: Library<74>-Footnote-275299621
Ref: Library<74>-Footnote-285299687
Ref: Library<74>-Footnote-295299753
Ref: Library<74>-Footnote-305299819
Ref: Library<74>-Footnote-315299885
Ref: Library<74>-Footnote-325299951
Ref: Library<74>-Footnote-335300017
Ref: Library<74>-Footnote-345300083
Ref: Library<74>-Footnote-355300149
Node: IDLE<53>5300215
Ref: whatsnew/changelog id6405300326
Ref: 1a525300326
Ref: IDLE<53>-Footnote-15302965
Ref: IDLE<53>-Footnote-25303029
Ref: IDLE<53>-Footnote-35303094
Ref: IDLE<53>-Footnote-45303159
Ref: IDLE<53>-Footnote-55303224
Ref: IDLE<53>-Footnote-65303289
Ref: IDLE<53>-Footnote-75303354
Ref: IDLE<53>-Footnote-85303419
Ref: IDLE<53>-Footnote-95303484
Ref: IDLE<53>-Footnote-105303549
Ref: IDLE<53>-Footnote-115303615
Ref: IDLE<53>-Footnote-125303681
Ref: IDLE<53>-Footnote-135303747
Ref: IDLE<53>-Footnote-145303813
Ref: IDLE<53>-Footnote-155303879
Ref: IDLE<53>-Footnote-165303945
Ref: IDLE<53>-Footnote-175304011
Ref: IDLE<53>-Footnote-185304077
Ref: IDLE<53>-Footnote-195304143
Node: Documentation<63>5304209
Ref: whatsnew/changelog id6415304318
Ref: 1a535304318
Ref: Documentation<63>-Footnote-15304761
Ref: Documentation<63>-Footnote-25304826
Ref: Documentation<63>-Footnote-35304891
Ref: Documentation<63>-Footnote-45304933
Node: Tests<67>5304998
Ref: whatsnew/changelog id6425305110
Ref: 1a545305110
Ref: Tests<67>-Footnote-15305490
Ref: Tests<67>-Footnote-25305555
Node: Windows<63>5305620
Ref: whatsnew/changelog id6435305724
Ref: 1a555305724
Ref: Windows<63>-Footnote-15306134
Ref: Windows<63>-Footnote-25306199
Node: Build<73>5306264
Ref: whatsnew/changelog id6445306368
Ref: 1a565306368
Ref: Build<73>-Footnote-15306645
Ref: Build<73>-Footnote-25306710
Node: C API<63>5306775
Ref: whatsnew/changelog id6455306883
Ref: 1a575306883
Ref: C API<63>-Footnote-15307121
Ref: C API<63>-Footnote-25307186
Ref: C API<63>-Footnote-35307228
Node: Tools/Demos<39>5307293
Ref: whatsnew/changelog id6465307383
Ref: 1a585307383
Ref: Tools/Demos<39>-Footnote-15307581
Node: Python 3 6 0 alpha 15307646
Ref: whatsnew/changelog python-3-6-0-alpha-15307786
Ref: 1a595307786
Node: Security<43>5308147
Ref: whatsnew/changelog id6475308246
Ref: 1a5a5308246
Ref: Security<43>-Footnote-15308737
Ref: Security<43>-Footnote-25308802
Ref: Security<43>-Footnote-35308867
Node: Core and Builtins<76>5308932
Ref: whatsnew/changelog id6485309051
Ref: 1a5b5309051
Ref: Core and Builtins<76>-Footnote-15322197
Ref: Core and Builtins<76>-Footnote-25322262
Ref: Core and Builtins<76>-Footnote-35322327
Ref: Core and Builtins<76>-Footnote-45322392
Ref: Core and Builtins<76>-Footnote-55322457
Ref: Core and Builtins<76>-Footnote-65322522
Ref: Core and Builtins<76>-Footnote-75322587
Ref: Core and Builtins<76>-Footnote-85322652
Ref: Core and Builtins<76>-Footnote-95322717
Ref: Core and Builtins<76>-Footnote-105322782
Ref: Core and Builtins<76>-Footnote-115322848
Ref: Core and Builtins<76>-Footnote-125322914
Ref: Core and Builtins<76>-Footnote-135322980
Ref: Core and Builtins<76>-Footnote-145323046
Ref: Core and Builtins<76>-Footnote-155323112
Ref: Core and Builtins<76>-Footnote-165323178
Ref: Core and Builtins<76>-Footnote-175323221
Ref: Core and Builtins<76>-Footnote-185323287
Ref: Core and Builtins<76>-Footnote-195323353
Ref: Core and Builtins<76>-Footnote-205323419
Ref: Core and Builtins<76>-Footnote-215323485
Ref: Core and Builtins<76>-Footnote-225323551
Ref: Core and Builtins<76>-Footnote-235323617
Ref: Core and Builtins<76>-Footnote-245323660
Ref: Core and Builtins<76>-Footnote-255323726
Ref: Core and Builtins<76>-Footnote-265323792
Ref: Core and Builtins<76>-Footnote-275323858
Ref: Core and Builtins<76>-Footnote-285323924
Ref: Core and Builtins<76>-Footnote-295323990
Ref: Core and Builtins<76>-Footnote-305324056
Ref: Core and Builtins<76>-Footnote-315324122
Ref: Core and Builtins<76>-Footnote-325324188
Ref: Core and Builtins<76>-Footnote-335324254
Ref: Core and Builtins<76>-Footnote-345324320
Ref: Core and Builtins<76>-Footnote-355324386
Ref: Core and Builtins<76>-Footnote-365324452
Ref: Core and Builtins<76>-Footnote-375324517
Ref: Core and Builtins<76>-Footnote-385324583
Ref: Core and Builtins<76>-Footnote-395324649
Ref: Core and Builtins<76>-Footnote-405324715
Ref: Core and Builtins<76>-Footnote-415324781
Ref: Core and Builtins<76>-Footnote-425324847
Ref: Core and Builtins<76>-Footnote-435324913
Ref: Core and Builtins<76>-Footnote-445324979
Ref: Core and Builtins<76>-Footnote-455325045
Ref: Core and Builtins<76>-Footnote-465325111
Ref: Core and Builtins<76>-Footnote-475325177
Ref: Core and Builtins<76>-Footnote-485325243
Ref: Core and Builtins<76>-Footnote-495325309
Ref: Core and Builtins<76>-Footnote-505325375
Ref: Core and Builtins<76>-Footnote-515325441
Ref: Core and Builtins<76>-Footnote-525325507
Ref: Core and Builtins<76>-Footnote-535325572
Ref: Core and Builtins<76>-Footnote-545325638
Ref: Core and Builtins<76>-Footnote-555325704
Ref: Core and Builtins<76>-Footnote-565325770
Ref: Core and Builtins<76>-Footnote-575325836
Ref: Core and Builtins<76>-Footnote-585325902
Ref: Core and Builtins<76>-Footnote-595325968
Ref: Core and Builtins<76>-Footnote-605326034
Ref: Core and Builtins<76>-Footnote-615326100
Ref: Core and Builtins<76>-Footnote-625326166
Ref: Core and Builtins<76>-Footnote-635326232
Ref: Core and Builtins<76>-Footnote-645326298
Ref: Core and Builtins<76>-Footnote-655326364
Ref: Core and Builtins<76>-Footnote-665326430
Ref: Core and Builtins<76>-Footnote-675326496
Ref: Core and Builtins<76>-Footnote-685326562
Ref: Core and Builtins<76>-Footnote-695326628
Ref: Core and Builtins<76>-Footnote-705326694
Ref: Core and Builtins<76>-Footnote-715326760
Ref: Core and Builtins<76>-Footnote-725326826
Ref: Core and Builtins<76>-Footnote-735326892
Ref: Core and Builtins<76>-Footnote-745326958
Ref: Core and Builtins<76>-Footnote-755327024
Ref: Core and Builtins<76>-Footnote-765327090
Ref: Core and Builtins<76>-Footnote-775327156
Ref: Core and Builtins<76>-Footnote-785327222
Ref: Core and Builtins<76>-Footnote-795327287
Ref: Core and Builtins<76>-Footnote-805327353
Ref: Core and Builtins<76>-Footnote-815327396
Ref: Core and Builtins<76>-Footnote-825327462
Ref: Core and Builtins<76>-Footnote-835327528
Ref: Core and Builtins<76>-Footnote-845327594
Ref: Core and Builtins<76>-Footnote-855327660
Ref: Core and Builtins<76>-Footnote-865327726
Ref: Core and Builtins<76>-Footnote-875327792
Node: Library<75>5327858
Ref: whatsnew/changelog id6495327973
Ref: 1a5d5327973
Ref: Library<75>-Footnote-15358894
Ref: Library<75>-Footnote-25358959
Ref: Library<75>-Footnote-35359024
Ref: Library<75>-Footnote-45359089
Ref: Library<75>-Footnote-55359154
Ref: Library<75>-Footnote-65359219
Ref: Library<75>-Footnote-75359284
Ref: Library<75>-Footnote-85359349
Ref: Library<75>-Footnote-95359414
Ref: Library<75>-Footnote-105359479
Ref: Library<75>-Footnote-115359545
Ref: Library<75>-Footnote-125359611
Ref: Library<75>-Footnote-135359677
Ref: Library<75>-Footnote-145359743
Ref: Library<75>-Footnote-155359809
Ref: Library<75>-Footnote-165359875
Ref: Library<75>-Footnote-175359941
Ref: Library<75>-Footnote-185360007
Ref: Library<75>-Footnote-195360050
Ref: Library<75>-Footnote-205360116
Ref: Library<75>-Footnote-215360182
Ref: Library<75>-Footnote-225360248
Ref: Library<75>-Footnote-235360314
Ref: Library<75>-Footnote-245360380
Ref: Library<75>-Footnote-255360446
Ref: Library<75>-Footnote-265360512
Ref: Library<75>-Footnote-275360578
Ref: Library<75>-Footnote-285360644
Ref: Library<75>-Footnote-295360710
Ref: Library<75>-Footnote-305360776
Ref: Library<75>-Footnote-315360842
Ref: Library<75>-Footnote-325360908
Ref: Library<75>-Footnote-335360974
Ref: Library<75>-Footnote-345361040
Ref: Library<75>-Footnote-355361106
Ref: Library<75>-Footnote-365361172
Ref: Library<75>-Footnote-375361238
Ref: Library<75>-Footnote-385361304
Ref: Library<75>-Footnote-395361370
Ref: Library<75>-Footnote-405361436
Ref: Library<75>-Footnote-415361502
Ref: Library<75>-Footnote-425361568
Ref: Library<75>-Footnote-435361634
Ref: Library<75>-Footnote-445361700
Ref: Library<75>-Footnote-455361766
Ref: Library<75>-Footnote-465361832
Ref: Library<75>-Footnote-475361898
Ref: Library<75>-Footnote-485361964
Ref: Library<75>-Footnote-495362030
Ref: Library<75>-Footnote-505362096
Ref: Library<75>-Footnote-515362162
Ref: Library<75>-Footnote-525362228
Ref: Library<75>-Footnote-535362294
Ref: Library<75>-Footnote-545362360
Ref: Library<75>-Footnote-555362426
Ref: Library<75>-Footnote-565362492
Ref: Library<75>-Footnote-575362558
Ref: Library<75>-Footnote-585362624
Ref: Library<75>-Footnote-595362690
Ref: Library<75>-Footnote-605362756
Ref: Library<75>-Footnote-615362822
Ref: Library<75>-Footnote-625362888
Ref: Library<75>-Footnote-635362954
Ref: Library<75>-Footnote-645363020
Ref: Library<75>-Footnote-655363086
Ref: Library<75>-Footnote-665363152
Ref: Library<75>-Footnote-675363218
Ref: Library<75>-Footnote-685363284
Ref: Library<75>-Footnote-695363350
Ref: Library<75>-Footnote-705363416
Ref: Library<75>-Footnote-715363482
Ref: Library<75>-Footnote-725363548
Ref: Library<75>-Footnote-735363614
Ref: Library<75>-Footnote-745363680
Ref: Library<75>-Footnote-755363746
Ref: Library<75>-Footnote-765363812
Ref: Library<75>-Footnote-775363878
Ref: Library<75>-Footnote-785363944
Ref: Library<75>-Footnote-795364010
Ref: Library<75>-Footnote-805364076
Ref: Library<75>-Footnote-815364141
Ref: Library<75>-Footnote-825364207
Ref: Library<75>-Footnote-835364273
Ref: Library<75>-Footnote-845364339
Ref: Library<75>-Footnote-855364405
Ref: Library<75>-Footnote-865364471
Ref: Library<75>-Footnote-875364537
Ref: Library<75>-Footnote-885364603
Ref: Library<75>-Footnote-895364669
Ref: Library<75>-Footnote-905364735
Ref: Library<75>-Footnote-915364801
Ref: Library<75>-Footnote-925364867
Ref: Library<75>-Footnote-935364933
Ref: Library<75>-Footnote-945364999
Ref: Library<75>-Footnote-955365065
Ref: Library<75>-Footnote-965365131
Ref: Library<75>-Footnote-975365197
Ref: Library<75>-Footnote-985365263
Ref: Library<75>-Footnote-995365329
Ref: Library<75>-Footnote-1005365395
Ref: Library<75>-Footnote-1015365462
Ref: Library<75>-Footnote-1025365529
Ref: Library<75>-Footnote-1035365596
Ref: Library<75>-Footnote-1045365663
Ref: Library<75>-Footnote-1055365730
Ref: Library<75>-Footnote-1065365797
Ref: Library<75>-Footnote-1075365864
Ref: Library<75>-Footnote-1085365931
Ref: Library<75>-Footnote-1095365998
Ref: Library<75>-Footnote-1105366065
Ref: Library<75>-Footnote-1115366132
Ref: Library<75>-Footnote-1125366199
Ref: Library<75>-Footnote-1135366266
Ref: Library<75>-Footnote-1145366333
Ref: Library<75>-Footnote-1155366400
Ref: Library<75>-Footnote-1165366467
Ref: Library<75>-Footnote-1175366534
Ref: Library<75>-Footnote-1185366601
Ref: Library<75>-Footnote-1195366668
Ref: Library<75>-Footnote-1205366735
Ref: Library<75>-Footnote-1215366802
Ref: Library<75>-Footnote-1225366869
Ref: Library<75>-Footnote-1235366936
Ref: Library<75>-Footnote-1245367003
Ref: Library<75>-Footnote-1255367070
Ref: Library<75>-Footnote-1265367137
Ref: Library<75>-Footnote-1275367204
Ref: Library<75>-Footnote-1285367271
Ref: Library<75>-Footnote-1295367338
Ref: Library<75>-Footnote-1305367405
Ref: Library<75>-Footnote-1315367472
Ref: Library<75>-Footnote-1325367539
Ref: Library<75>-Footnote-1335367606
Ref: Library<75>-Footnote-1345367673
Ref: Library<75>-Footnote-1355367740
Ref: Library<75>-Footnote-1365367807
Ref: Library<75>-Footnote-1375367874
Ref: Library<75>-Footnote-1385367941
Ref: Library<75>-Footnote-1395368008
Ref: Library<75>-Footnote-1405368075
Ref: Library<75>-Footnote-1415368142
Ref: Library<75>-Footnote-1425368209
Ref: Library<75>-Footnote-1435368276
Ref: Library<75>-Footnote-1445368343
Ref: Library<75>-Footnote-1455368409
Ref: Library<75>-Footnote-1465368476
Ref: Library<75>-Footnote-1475368543
Ref: Library<75>-Footnote-1485368610
Ref: Library<75>-Footnote-1495368677
Ref: Library<75>-Footnote-1505368744
Ref: Library<75>-Footnote-1515368810
Ref: Library<75>-Footnote-1525368877
Ref: Library<75>-Footnote-1535368944
Ref: Library<75>-Footnote-1545369011
Ref: Library<75>-Footnote-1555369078
Ref: Library<75>-Footnote-1565369145
Ref: Library<75>-Footnote-1575369212
Ref: Library<75>-Footnote-1585369279
Ref: Library<75>-Footnote-1595369346
Ref: Library<75>-Footnote-1605369413
Ref: Library<75>-Footnote-1615369479
Ref: Library<75>-Footnote-1625369546
Ref: Library<75>-Footnote-1635369613
Ref: Library<75>-Footnote-1645369680
Ref: Library<75>-Footnote-1655369747
Ref: Library<75>-Footnote-1665369814
Ref: Library<75>-Footnote-1675369881
Ref: Library<75>-Footnote-1685369948
Ref: Library<75>-Footnote-1695370015
Ref: Library<75>-Footnote-1705370082
Ref: Library<75>-Footnote-1715370149
Ref: Library<75>-Footnote-1725370216
Ref: Library<75>-Footnote-1735370283
Ref: Library<75>-Footnote-1745370350
Ref: Library<75>-Footnote-1755370417
Ref: Library<75>-Footnote-1765370484
Ref: Library<75>-Footnote-1775370551
Ref: Library<75>-Footnote-1785370618
Ref: Library<75>-Footnote-1795370685
Ref: Library<75>-Footnote-1805370752
Ref: Library<75>-Footnote-1815370819
Ref: Library<75>-Footnote-1825370886
Ref: Library<75>-Footnote-1835370953
Ref: Library<75>-Footnote-1845371020
Ref: Library<75>-Footnote-1855371087
Ref: Library<75>-Footnote-1865371154
Ref: Library<75>-Footnote-1875371221
Ref: Library<75>-Footnote-1885371288
Ref: Library<75>-Footnote-1895371355
Ref: Library<75>-Footnote-1905371422
Ref: Library<75>-Footnote-1915371489
Ref: Library<75>-Footnote-1925371556
Ref: Library<75>-Footnote-1935371623
Ref: Library<75>-Footnote-1945371690
Ref: Library<75>-Footnote-1955371757
Ref: Library<75>-Footnote-1965371824
Ref: Library<75>-Footnote-1975371891
Ref: Library<75>-Footnote-1985371958
Ref: Library<75>-Footnote-1995372025
Ref: Library<75>-Footnote-2005372092
Ref: Library<75>-Footnote-2015372159
Ref: Library<75>-Footnote-2025372226
Ref: Library<75>-Footnote-2035372293
Ref: Library<75>-Footnote-2045372360
Ref: Library<75>-Footnote-2055372427
Ref: Library<75>-Footnote-2065372494
Ref: Library<75>-Footnote-2075372561
Ref: Library<75>-Footnote-2085372628
Ref: Library<75>-Footnote-2095372694
Ref: Library<75>-Footnote-2105372760
Ref: Library<75>-Footnote-2115372827
Ref: Library<75>-Footnote-2125372894
Ref: Library<75>-Footnote-2135372961
Ref: Library<75>-Footnote-2145373028
Ref: Library<75>-Footnote-2155373095
Ref: Library<75>-Footnote-2165373162
Ref: Library<75>-Footnote-2175373229
Ref: Library<75>-Footnote-2185373296
Ref: Library<75>-Footnote-2195373363
Ref: Library<75>-Footnote-2205373430
Ref: Library<75>-Footnote-2215373497
Ref: Library<75>-Footnote-2225373564
Ref: Library<75>-Footnote-2235373631
Ref: Library<75>-Footnote-2245373698
Node: IDLE<54>5373765
Ref: whatsnew/changelog id6505373876
Ref: 1a5f5373876
Ref: IDLE<54>-Footnote-15379407
Ref: IDLE<54>-Footnote-25379472
Ref: IDLE<54>-Footnote-35379537
Ref: IDLE<54>-Footnote-45379602
Ref: IDLE<54>-Footnote-55379667
Ref: IDLE<54>-Footnote-65379732
Ref: IDLE<54>-Footnote-75379797
Ref: IDLE<54>-Footnote-85379862
Ref: IDLE<54>-Footnote-95379927
Ref: IDLE<54>-Footnote-105379992
Ref: IDLE<54>-Footnote-115380058
Ref: IDLE<54>-Footnote-125380124
Ref: IDLE<54>-Footnote-135380190
Ref: IDLE<54>-Footnote-145380256
Ref: IDLE<54>-Footnote-155380322
Ref: IDLE<54>-Footnote-165380388
Ref: IDLE<54>-Footnote-175380454
Ref: IDLE<54>-Footnote-185380520
Ref: IDLE<54>-Footnote-195380586
Ref: IDLE<54>-Footnote-205380652
Ref: IDLE<54>-Footnote-215380718
Ref: IDLE<54>-Footnote-225380784
Ref: IDLE<54>-Footnote-235380850
Ref: IDLE<54>-Footnote-245380916
Ref: IDLE<54>-Footnote-255380982
Ref: IDLE<54>-Footnote-265381048
Ref: IDLE<54>-Footnote-275381114
Ref: IDLE<54>-Footnote-285381180
Node: Documentation<64>5381246
Ref: whatsnew/changelog id6515381355
Ref: 1a605381355
Ref: Documentation<64>-Footnote-15382139
Ref: Documentation<64>-Footnote-25382204
Ref: Documentation<64>-Footnote-35382268
Ref: Documentation<64>-Footnote-45382333
Ref: Documentation<64>-Footnote-55382398
Node: Tests<68>5382463
Ref: whatsnew/changelog id6525382573
Ref: 1a615382573
Ref: Tests<68>-Footnote-15384316
Ref: Tests<68>-Footnote-25384381
Ref: Tests<68>-Footnote-35384446
Ref: Tests<68>-Footnote-45384511
Ref: Tests<68>-Footnote-55384576
Ref: Tests<68>-Footnote-65384641
Ref: Tests<68>-Footnote-75384706
Ref: Tests<68>-Footnote-85384771
Ref: Tests<68>-Footnote-95384836
Ref: Tests<68>-Footnote-105384901
Ref: Tests<68>-Footnote-115384967
Ref: Tests<68>-Footnote-125385033
Ref: Tests<68>-Footnote-135385099
Node: Build<74>5385165
Ref: whatsnew/changelog id6535385269
Ref: 1a625385269
Ref: Build<74>-Footnote-15387993
Ref: Build<74>-Footnote-25388058
Ref: Build<74>-Footnote-35388123
Ref: Build<74>-Footnote-45388188
Ref: Build<74>-Footnote-55388253
Ref: Build<74>-Footnote-65388318
Ref: Build<74>-Footnote-75388383
Ref: Build<74>-Footnote-85388448
Ref: Build<74>-Footnote-95388513
Ref: Build<74>-Footnote-105388578
Ref: Build<74>-Footnote-115388644
Ref: Build<74>-Footnote-125388710
Ref: Build<74>-Footnote-135388776
Ref: Build<74>-Footnote-145388842
Ref: Build<74>-Footnote-155388908
Ref: Build<74>-Footnote-165388974
Ref: Build<74>-Footnote-175389040
Ref: Build<74>-Footnote-185389106
Ref: Build<74>-Footnote-195389172
Node: Windows<64>5389238
Ref: whatsnew/changelog id6545389348
Ref: 1a635389348
Ref: Windows<64>-Footnote-15389994
Ref: Windows<64>-Footnote-25390059
Ref: Windows<64>-Footnote-35390124
Ref: Windows<64>-Footnote-45390189
Ref: Windows<64>-Footnote-55390254
Ref: Windows<64>-Footnote-65390319
Node: Tools/Demos<40>5390384
Ref: whatsnew/changelog id6555390494
Ref: 1a645390494
Ref: Tools/Demos<40>-Footnote-15391280
Ref: Tools/Demos<40>-Footnote-25391345
Ref: Tools/Demos<40>-Footnote-35391410
Ref: Tools/Demos<40>-Footnote-45391475
Ref: Tools/Demos<40>-Footnote-55391540
Ref: Tools/Demos<40>-Footnote-65391605
Node: C API<64>5391670
Ref: whatsnew/changelog id6565391760
Ref: 1a655391760
Ref: C API<64>-Footnote-15392249
Ref: C API<64>-Footnote-25392314
Node: Python 3 5 5 final5392379
Ref: whatsnew/changelog python-3-5-5-final5392531
Ref: 1a665392531
Node: Python 3 5 5 release candidate 15392659
Ref: whatsnew/changelog python-3-5-5-release-candidate-15392809
Ref: 1a675392809
Node: Security<44>5393024
Ref: whatsnew/changelog id6575393135
Ref: 1a685393135
Ref: Security<44>-Footnote-15394404
Ref: Security<44>-Footnote-25394469
Ref: Security<44>-Footnote-35394534
Ref: Security<44>-Footnote-45394599
Ref: Security<44>-Footnote-55394664
Ref: Security<44>-Footnote-65394736
Node: Core and Builtins<77>5394801
Ref: whatsnew/changelog id6585394932
Ref: 1a695394932
Ref: Core and Builtins<77>-Footnote-15395155
Node: Library<76>5395220
Ref: whatsnew/changelog id6595395330
Ref: 1a6a5395330
Ref: Library<76>-Footnote-15395857
Ref: Library<76>-Footnote-25395922
Node: Python 3 5 4 final5395987
Ref: whatsnew/changelog python-3-5-4-final5396151
Ref: 1a6b5396151
Node: Library<77>5396268
Ref: whatsnew/changelog id6605396334
Ref: 1a6c5396334
Ref: Library<77>-Footnote-15396532
Node: Python 3 5 4 release candidate 15396597
Ref: whatsnew/changelog python-3-5-4-release-candidate-15396747
Ref: 1a6d5396747
Node: Security<45>5397082
Ref: whatsnew/changelog id6615397193
Ref: 1a6e5397193
Ref: Security<45>-Footnote-15398515
Ref: Security<45>-Footnote-25398580
Ref: Security<45>-Footnote-35398645
Ref: Security<45>-Footnote-45398714
Ref: Security<45>-Footnote-55398783
Ref: Security<45>-Footnote-65398852
Ref: Security<45>-Footnote-75398921
Ref: Security<45>-Footnote-85398990
Ref: Security<45>-Footnote-95399059
Ref: Security<45>-Footnote-105399124
Ref: Security<45>-Footnote-115399190
Ref: Security<45>-Footnote-125399260
Node: Core and Builtins<78>5399330
Ref: whatsnew/changelog id6625399461
Ref: 1a6f5399461
Ref: Core and Builtins<78>-Footnote-15401716
Ref: Core and Builtins<78>-Footnote-25401781
Ref: Core and Builtins<78>-Footnote-35401846
Ref: Core and Builtins<78>-Footnote-45401911
Ref: Core and Builtins<78>-Footnote-55401976
Ref: Core and Builtins<78>-Footnote-65402041
Ref: Core and Builtins<78>-Footnote-75402106
Ref: Core and Builtins<78>-Footnote-85402171
Ref: Core and Builtins<78>-Footnote-95402236
Ref: Core and Builtins<78>-Footnote-105402301
Ref: Core and Builtins<78>-Footnote-115402367
Ref: Core and Builtins<78>-Footnote-125402433
Ref: Core and Builtins<78>-Footnote-135402499
Ref: Core and Builtins<78>-Footnote-145402565
Ref: Core and Builtins<78>-Footnote-155402631
Node: Library<78>5402697
Ref: whatsnew/changelog id6635402833
Ref: 1a705402833
Ref: Library<78>-Footnote-15412994
Ref: Library<78>-Footnote-25413059
Ref: Library<78>-Footnote-35413124
Ref: Library<78>-Footnote-45413189
Ref: Library<78>-Footnote-55413254
Ref: Library<78>-Footnote-65413319
Ref: Library<78>-Footnote-75413384
Ref: Library<78>-Footnote-85413449
Ref: Library<78>-Footnote-95413514
Ref: Library<78>-Footnote-105413579
Ref: Library<78>-Footnote-115413645
Ref: Library<78>-Footnote-125413711
Ref: Library<78>-Footnote-135413777
Ref: Library<78>-Footnote-145413843
Ref: Library<78>-Footnote-155413909
Ref: Library<78>-Footnote-165413975
Ref: Library<78>-Footnote-175414041
Ref: Library<78>-Footnote-185414107
Ref: Library<78>-Footnote-195414173
Ref: Library<78>-Footnote-205414239
Ref: Library<78>-Footnote-215414305
Ref: Library<78>-Footnote-225414371
Ref: Library<78>-Footnote-235414437
Ref: Library<78>-Footnote-245414503
Ref: Library<78>-Footnote-255414569
Ref: Library<78>-Footnote-265414635
Ref: Library<78>-Footnote-275414701
Ref: Library<78>-Footnote-285414767
Ref: Library<78>-Footnote-295414833
Ref: Library<78>-Footnote-305414899
Ref: Library<78>-Footnote-315414965
Ref: Library<78>-Footnote-325415031
Ref: Library<78>-Footnote-335415097
Ref: Library<78>-Footnote-345415163
Ref: Library<78>-Footnote-355415229
Ref: Library<78>-Footnote-365415295
Ref: Library<78>-Footnote-375415361
Ref: Library<78>-Footnote-385415427
Ref: Library<78>-Footnote-395415493
Ref: Library<78>-Footnote-405415559
Ref: Library<78>-Footnote-415415625
Ref: Library<78>-Footnote-425415691
Ref: Library<78>-Footnote-435415757
Ref: Library<78>-Footnote-445415823
Ref: Library<78>-Footnote-455415889
Ref: Library<78>-Footnote-465415955
Ref: Library<78>-Footnote-475416021
Ref: Library<78>-Footnote-485416087
Ref: Library<78>-Footnote-495416153
Ref: Library<78>-Footnote-505416219
Ref: Library<78>-Footnote-515416285
Ref: Library<78>-Footnote-525416351
Ref: Library<78>-Footnote-535416417
Ref: Library<78>-Footnote-545416483
Ref: Library<78>-Footnote-555416548
Ref: Library<78>-Footnote-565416614
Ref: Library<78>-Footnote-575416680
Ref: Library<78>-Footnote-585416746
Ref: Library<78>-Footnote-595416812
Ref: Library<78>-Footnote-605416878
Ref: Library<78>-Footnote-615416944
Ref: Library<78>-Footnote-625417010
Ref: Library<78>-Footnote-635417076
Ref: Library<78>-Footnote-645417142
Ref: Library<78>-Footnote-655417208
Ref: Library<78>-Footnote-665417274
Ref: Library<78>-Footnote-675417340
Ref: Library<78>-Footnote-685417406
Ref: Library<78>-Footnote-695417472
Ref: Library<78>-Footnote-705417538
Ref: Library<78>-Footnote-715417604
Ref: Library<78>-Footnote-725417670
Ref: Library<78>-Footnote-735417736
Ref: Library<78>-Footnote-745417802
Node: Documentation<65>5417868
Ref: whatsnew/changelog id6645417992
Ref: 1a715417992
Ref: Documentation<65>-Footnote-15418702
Ref: Documentation<65>-Footnote-25418767
Ref: Documentation<65>-Footnote-35418832
Ref: Documentation<65>-Footnote-45418897
Ref: Documentation<65>-Footnote-55418962
Ref: Documentation<65>-Footnote-65419027
Node: Tests<69>5419092
Ref: whatsnew/changelog id6655419214
Ref: 1a725419214
Ref: Tests<69>-Footnote-15421291
Ref: Tests<69>-Footnote-25421356
Ref: Tests<69>-Footnote-35421421
Ref: Tests<69>-Footnote-45421486
Ref: Tests<69>-Footnote-55421551
Ref: Tests<69>-Footnote-65421616
Ref: Tests<69>-Footnote-75421681
Ref: Tests<69>-Footnote-85421746
Ref: Tests<69>-Footnote-95421811
Node: Build<75>5421876
Ref: whatsnew/changelog id6665421992
Ref: 1a735421992
Ref: Build<75>-Footnote-15422504
Ref: Build<75>-Footnote-25422569
Ref: Build<75>-Footnote-35422634
Node: Windows<65>5422699
Ref: whatsnew/changelog id6675422815
Ref: 1a745422815
Ref: Windows<65>-Footnote-15423073
Ref: Windows<65>-Footnote-25423138
Node: C API<65>5423203
Ref: whatsnew/changelog id6685423301
Ref: 1a755423301
Ref: C API<65>-Footnote-15423908
Ref: C API<65>-Footnote-25423973
Node: Python 3 5 3 final5424038
Ref: whatsnew/changelog python-3-5-3-final5424202
Ref: 1a765424202
Node: Python 3 5 3 release candidate 15424347
Ref: whatsnew/changelog python-3-5-3-release-candidate-15424497
Ref: 1a775424497
Node: Security<46>5424882
Ref: whatsnew/changelog id6695424993
Ref: 1a785424993
Ref: Security<46>-Footnote-15425371
Ref: Security<46>-Footnote-25425436
Node: Core and Builtins<79>5425501
Ref: whatsnew/changelog id6705425632
Ref: 1a795425632
Ref: Core and Builtins<79>-Footnote-15431062
Ref: Core and Builtins<79>-Footnote-25431127
Ref: Core and Builtins<79>-Footnote-35431192
Ref: Core and Builtins<79>-Footnote-45431257
Ref: Core and Builtins<79>-Footnote-55431322
Ref: Core and Builtins<79>-Footnote-65431387
Ref: Core and Builtins<79>-Footnote-75431452
Ref: Core and Builtins<79>-Footnote-85431517
Ref: Core and Builtins<79>-Footnote-95431582
Ref: Core and Builtins<79>-Footnote-105431647
Ref: Core and Builtins<79>-Footnote-115431713
Ref: Core and Builtins<79>-Footnote-125431779
Ref: Core and Builtins<79>-Footnote-135431845
Ref: Core and Builtins<79>-Footnote-145431911
Ref: Core and Builtins<79>-Footnote-155431977
Ref: Core and Builtins<79>-Footnote-165432043
Ref: Core and Builtins<79>-Footnote-175432109
Ref: Core and Builtins<79>-Footnote-185432175
Ref: Core and Builtins<79>-Footnote-195432241
Ref: Core and Builtins<79>-Footnote-205432307
Ref: Core and Builtins<79>-Footnote-215432373
Ref: Core and Builtins<79>-Footnote-225432439
Ref: Core and Builtins<79>-Footnote-235432505
Ref: Core and Builtins<79>-Footnote-245432571
Ref: Core and Builtins<79>-Footnote-255432637
Ref: Core and Builtins<79>-Footnote-265432703
Ref: Core and Builtins<79>-Footnote-275432769
Ref: Core and Builtins<79>-Footnote-285432835
Ref: Core and Builtins<79>-Footnote-295432901
Ref: Core and Builtins<79>-Footnote-305432967
Ref: Core and Builtins<79>-Footnote-315433033
Ref: Core and Builtins<79>-Footnote-325433099
Ref: Core and Builtins<79>-Footnote-335433165
Ref: Core and Builtins<79>-Footnote-345433231
Ref: Core and Builtins<79>-Footnote-355433297
Ref: Core and Builtins<79>-Footnote-365433363
Ref: Core and Builtins<79>-Footnote-375433429
Ref: Core and Builtins<79>-Footnote-385433495
Ref: Core and Builtins<79>-Footnote-395433561
Ref: Core and Builtins<79>-Footnote-405433627
Ref: Core and Builtins<79>-Footnote-415433693
Ref: Core and Builtins<79>-Footnote-425433759
Ref: Core and Builtins<79>-Footnote-435433825
Node: Library<79>5433891
Ref: whatsnew/changelog id6715434018
Ref: 1a7a5434018
Ref: Library<79>-Footnote-15449946
Ref: Library<79>-Footnote-25450011
Ref: Library<79>-Footnote-35450076
Ref: Library<79>-Footnote-45450141
Ref: Library<79>-Footnote-55450206
Ref: Library<79>-Footnote-65450270
Ref: Library<79>-Footnote-75450335
Ref: Library<79>-Footnote-85450400
Ref: Library<79>-Footnote-95450465
Ref: Library<79>-Footnote-105450530
Ref: Library<79>-Footnote-115450596
Ref: Library<79>-Footnote-125450662
Ref: Library<79>-Footnote-135450728
Ref: Library<79>-Footnote-145450794
Ref: Library<79>-Footnote-155450860
Ref: Library<79>-Footnote-165450926
Ref: Library<79>-Footnote-175450992
Ref: Library<79>-Footnote-185451058
Ref: Library<79>-Footnote-195451124
Ref: Library<79>-Footnote-205451190
Ref: Library<79>-Footnote-215451256
Ref: Library<79>-Footnote-225451322
Ref: Library<79>-Footnote-235451388
Ref: Library<79>-Footnote-245451454
Ref: Library<79>-Footnote-255451520
Ref: Library<79>-Footnote-265451586
Ref: Library<79>-Footnote-275451652
Ref: Library<79>-Footnote-285451718
Ref: Library<79>-Footnote-295451784
Ref: Library<79>-Footnote-305451850
Ref: Library<79>-Footnote-315451916
Ref: Library<79>-Footnote-325451982
Ref: Library<79>-Footnote-335452050
Ref: Library<79>-Footnote-345452116
Ref: Library<79>-Footnote-355452182
Ref: Library<79>-Footnote-365452248
Ref: Library<79>-Footnote-375452314
Ref: Library<79>-Footnote-385452380
Ref: Library<79>-Footnote-395452446
Ref: Library<79>-Footnote-405452512
Ref: Library<79>-Footnote-415452578
Ref: Library<79>-Footnote-425452644
Ref: Library<79>-Footnote-435452710
Ref: Library<79>-Footnote-445452776
Ref: Library<79>-Footnote-455452842
Ref: Library<79>-Footnote-465452908
Ref: Library<79>-Footnote-475452974
Ref: Library<79>-Footnote-485453040
Ref: Library<79>-Footnote-495453106
Ref: Library<79>-Footnote-505453172
Ref: Library<79>-Footnote-515453238
Ref: Library<79>-Footnote-525453304
Ref: Library<79>-Footnote-535453370
Ref: Library<79>-Footnote-545453436
Ref: Library<79>-Footnote-555453502
Ref: Library<79>-Footnote-565453568
Ref: Library<79>-Footnote-575453634
Ref: Library<79>-Footnote-585453700
Ref: Library<79>-Footnote-595453766
Ref: Library<79>-Footnote-605453832
Ref: Library<79>-Footnote-615453902
Ref: Library<79>-Footnote-625453968
Ref: Library<79>-Footnote-635454034
Ref: Library<79>-Footnote-645454100
Ref: Library<79>-Footnote-655454166
Ref: Library<79>-Footnote-665454232
Ref: Library<79>-Footnote-675454298
Ref: Library<79>-Footnote-685454364
Ref: Library<79>-Footnote-695454430
Ref: Library<79>-Footnote-705454496
Ref: Library<79>-Footnote-715454562
Ref: Library<79>-Footnote-725454628
Ref: Library<79>-Footnote-735454693
Ref: Library<79>-Footnote-745454759
Ref: Library<79>-Footnote-755454825
Ref: Library<79>-Footnote-765454891
Ref: Library<79>-Footnote-775454957
Ref: Library<79>-Footnote-785455023
Ref: Library<79>-Footnote-795455089
Ref: Library<79>-Footnote-805455155
Ref: Library<79>-Footnote-815455228
Ref: Library<79>-Footnote-825455294
Ref: Library<79>-Footnote-835455360
Ref: Library<79>-Footnote-845455426
Ref: Library<79>-Footnote-855455492
Ref: Library<79>-Footnote-865455558
Ref: Library<79>-Footnote-875455624
Ref: Library<79>-Footnote-885455690
Ref: Library<79>-Footnote-895455756
Ref: Library<79>-Footnote-905455822
Ref: Library<79>-Footnote-915455888
Ref: Library<79>-Footnote-925455954
Ref: Library<79>-Footnote-935456020
Ref: Library<79>-Footnote-945456086
Ref: Library<79>-Footnote-955456152
Ref: Library<79>-Footnote-965456218
Ref: Library<79>-Footnote-975456284
Ref: Library<79>-Footnote-985456327
Ref: Library<79>-Footnote-995456393
Ref: Library<79>-Footnote-1005456459
Ref: Library<79>-Footnote-1015456526
Ref: Library<79>-Footnote-1025456593
Ref: Library<79>-Footnote-1035456660
Ref: Library<79>-Footnote-1045456727
Ref: Library<79>-Footnote-1055456794
Ref: Library<79>-Footnote-1065456861
Ref: Library<79>-Footnote-1075456928
Ref: Library<79>-Footnote-1085456995
Ref: Library<79>-Footnote-1095457062
Ref: Library<79>-Footnote-1105457129
Ref: Library<79>-Footnote-1115457196
Ref: Library<79>-Footnote-1125457263
Ref: Library<79>-Footnote-1135457330
Ref: Library<79>-Footnote-1145457397
Ref: Library<79>-Footnote-1155457464
Ref: Library<79>-Footnote-1165457531
Ref: Library<79>-Footnote-1175457598
Ref: Library<79>-Footnote-1185457665
Ref: Library<79>-Footnote-1195457732
Ref: Library<79>-Footnote-1205457799
Ref: Library<79>-Footnote-1215457866
Ref: Library<79>-Footnote-1225457933
Ref: Library<79>-Footnote-1235458000
Ref: Library<79>-Footnote-1245458067
Ref: Library<79>-Footnote-1255458134
Ref: Library<79>-Footnote-1265458201
Node: IDLE<55>5458268
Ref: whatsnew/changelog id6725458383
Ref: 1a7b5458383
Ref: IDLE<55>-Footnote-15459622
Ref: IDLE<55>-Footnote-25459687
Ref: IDLE<55>-Footnote-35459752
Ref: IDLE<55>-Footnote-45459817
Ref: IDLE<55>-Footnote-55459882
Ref: IDLE<55>-Footnote-65459947
Ref: IDLE<55>-Footnote-75460012
Ref: IDLE<55>-Footnote-85460077
Node: C API<66>5460142
Ref: whatsnew/changelog id6735460263
Ref: 1a7c5460263
Ref: C API<66>-Footnote-15460593
Ref: C API<66>-Footnote-25460658
Node: Documentation<66>5460723
Ref: whatsnew/changelog id6745460845
Ref: 1a7d5460845
Ref: Documentation<66>-Footnote-15460996
Node: Tests<70>5461061
Ref: whatsnew/changelog id6755461189
Ref: 1a7e5461189
Ref: Tests<70>-Footnote-15461876
Ref: Tests<70>-Footnote-25461941
Ref: Tests<70>-Footnote-35462006
Ref: Tests<70>-Footnote-45462071
Ref: Tests<70>-Footnote-55462136
Ref: Tests<70>-Footnote-65462201
Node: Tools/Demos<41>5462266
Ref: whatsnew/changelog id6765462388
Ref: 1a7f5462388
Ref: Tools/Demos<41>-Footnote-15462866
Ref: Tools/Demos<41>-Footnote-25462931
Ref: Tools/Demos<41>-Footnote-35462996
Node: Windows<66>5463061
Ref: whatsnew/changelog id6775463183
Ref: 1a805463183
Ref: Windows<66>-Footnote-15463683
Ref: Windows<66>-Footnote-25463748
Ref: Windows<66>-Footnote-35463813
Ref: Windows<66>-Footnote-45463878
Ref: Windows<66>-Footnote-55463943
Node: Build<76>5464008
Ref: whatsnew/changelog id6785464106
Ref: 1a815464106
Ref: Build<76>-Footnote-15466799
Ref: Build<76>-Footnote-25466864
Ref: Build<76>-Footnote-35466929
Ref: Build<76>-Footnote-45466994
Ref: Build<76>-Footnote-55467059
Ref: Build<76>-Footnote-65467124
Ref: Build<76>-Footnote-75467189
Ref: Build<76>-Footnote-85467254
Ref: Build<76>-Footnote-95467319
Ref: Build<76>-Footnote-105467384
Ref: Build<76>-Footnote-115467450
Ref: Build<76>-Footnote-125467516
Ref: Build<76>-Footnote-135467582
Ref: Build<76>-Footnote-145467648
Ref: Build<76>-Footnote-155467714
Ref: Build<76>-Footnote-165467780
Ref: Build<76>-Footnote-175467846
Ref: Build<76>-Footnote-185467912
Ref: Build<76>-Footnote-195467978
Ref: Build<76>-Footnote-205468044
Ref: Build<76>-Footnote-215468110
Ref: Build<76>-Footnote-225468176
Node: Python 3 5 2 final5468242
Ref: whatsnew/changelog python-3-5-2-final5468406
Ref: 1a825468406
Node: Core and Builtins<80>5468581
Ref: whatsnew/changelog id6795468675
Ref: 1a835468675
Ref: Core and Builtins<80>-Footnote-15468833
Node: Tests<71>5468898
Ref: whatsnew/changelog id6805469009
Ref: 1a845469009
Ref: Tests<71>-Footnote-15469167
Node: IDLE<56>5469232
Ref: whatsnew/changelog id6815469313
Ref: 1a855469313
Ref: IDLE<56>-Footnote-15469467
Node: Python 3 5 2 release candidate 15469532
Ref: whatsnew/changelog python-3-5-2-release-candidate-15469682
Ref: 1a865469682
Node: Security<47>5470047
Ref: whatsnew/changelog id6825470158
Ref: 1a875470158
Ref: Security<47>-Footnote-15471065
Ref: Security<47>-Footnote-25471130
Ref: Security<47>-Footnote-35471199
Ref: Security<47>-Footnote-45471268
Ref: Security<47>-Footnote-55471333
Ref: Security<47>-Footnote-65471398
Ref: Security<47>-Footnote-75471463
Node: Core and Builtins<81>5471528
Ref: whatsnew/changelog id6835471659
Ref: 1a885471659
Ref: Core and Builtins<81>-Footnote-15477498
Ref: Core and Builtins<81>-Footnote-25477563
Ref: Core and Builtins<81>-Footnote-35477628
Ref: Core and Builtins<81>-Footnote-45477693
Ref: Core and Builtins<81>-Footnote-55477758
Ref: Core and Builtins<81>-Footnote-65477823
Ref: Core and Builtins<81>-Footnote-75477888
Ref: Core and Builtins<81>-Footnote-85477953
Ref: Core and Builtins<81>-Footnote-95478018
Ref: Core and Builtins<81>-Footnote-105478083
Ref: Core and Builtins<81>-Footnote-115478149
Ref: Core and Builtins<81>-Footnote-125478215
Ref: Core and Builtins<81>-Footnote-135478281
Ref: Core and Builtins<81>-Footnote-145478347
Ref: Core and Builtins<81>-Footnote-155478413
Ref: Core and Builtins<81>-Footnote-165478479
Ref: Core and Builtins<81>-Footnote-175478545
Ref: Core and Builtins<81>-Footnote-185478610
Ref: Core and Builtins<81>-Footnote-195478676
Ref: Core and Builtins<81>-Footnote-205478742
Ref: Core and Builtins<81>-Footnote-215478808
Ref: Core and Builtins<81>-Footnote-225478874
Ref: Core and Builtins<81>-Footnote-235478940
Ref: Core and Builtins<81>-Footnote-245479006
Ref: Core and Builtins<81>-Footnote-255479072
Ref: Core and Builtins<81>-Footnote-265479138
Ref: Core and Builtins<81>-Footnote-275479204
Ref: Core and Builtins<81>-Footnote-285479270
Ref: Core and Builtins<81>-Footnote-295479336
Ref: Core and Builtins<81>-Footnote-305479402
Ref: Core and Builtins<81>-Footnote-315479468
Ref: Core and Builtins<81>-Footnote-325479511
Ref: Core and Builtins<81>-Footnote-335479577
Ref: Core and Builtins<81>-Footnote-345479643
Ref: Core and Builtins<81>-Footnote-355479709
Ref: Core and Builtins<81>-Footnote-365479775
Ref: Core and Builtins<81>-Footnote-375479841
Ref: Core and Builtins<81>-Footnote-385479907
Node: Library<80>5479973
Ref: whatsnew/changelog id6845480100
Ref: 1a895480100
Ref: Library<80>-Footnote-15496848
Ref: Library<80>-Footnote-25496913
Ref: Library<80>-Footnote-35496978
Ref: Library<80>-Footnote-45497020
Ref: Library<80>-Footnote-55497085
Ref: Library<80>-Footnote-65497150
Ref: Library<80>-Footnote-75497215
Ref: Library<80>-Footnote-85497280
Ref: Library<80>-Footnote-95497345
Ref: Library<80>-Footnote-105497410
Ref: Library<80>-Footnote-115497476
Ref: Library<80>-Footnote-125497542
Ref: Library<80>-Footnote-135497608
Ref: Library<80>-Footnote-145497674
Ref: Library<80>-Footnote-155497740
Ref: Library<80>-Footnote-165497806
Ref: Library<80>-Footnote-175497872
Ref: Library<80>-Footnote-185497938
Ref: Library<80>-Footnote-195498004
Ref: Library<80>-Footnote-205498070
Ref: Library<80>-Footnote-215498136
Ref: Library<80>-Footnote-225498202
Ref: Library<80>-Footnote-235498268
Ref: Library<80>-Footnote-245498334
Ref: Library<80>-Footnote-255498400
Ref: Library<80>-Footnote-265498466
Ref: Library<80>-Footnote-275498532
Ref: Library<80>-Footnote-285498598
Ref: Library<80>-Footnote-295498664
Ref: Library<80>-Footnote-305498730
Ref: Library<80>-Footnote-315498796
Ref: Library<80>-Footnote-325498862
Ref: Library<80>-Footnote-335498928
Ref: Library<80>-Footnote-345498994
Ref: Library<80>-Footnote-355499060
Ref: Library<80>-Footnote-365499126
Ref: Library<80>-Footnote-375499192
Ref: Library<80>-Footnote-385499258
Ref: Library<80>-Footnote-395499324
Ref: Library<80>-Footnote-405499390
Ref: Library<80>-Footnote-415499456
Ref: Library<80>-Footnote-425499522
Ref: Library<80>-Footnote-435499588
Ref: Library<80>-Footnote-445499654
Ref: Library<80>-Footnote-455499720
Ref: Library<80>-Footnote-465499786
Ref: Library<80>-Footnote-475499852
Ref: Library<80>-Footnote-485499918
Ref: Library<80>-Footnote-495499984
Ref: Library<80>-Footnote-505500050
Ref: Library<80>-Footnote-515500116
Ref: Library<80>-Footnote-525500182
Ref: Library<80>-Footnote-535500248
Ref: Library<80>-Footnote-545500314
Ref: Library<80>-Footnote-555500380
Ref: Library<80>-Footnote-565500446
Ref: Library<80>-Footnote-575500512
Ref: Library<80>-Footnote-585500578
Ref: Library<80>-Footnote-595500644
Ref: Library<80>-Footnote-605500710
Ref: Library<80>-Footnote-615500776
Ref: Library<80>-Footnote-625500841
Ref: Library<80>-Footnote-635500907
Ref: Library<80>-Footnote-645500973
Ref: Library<80>-Footnote-655501039
Ref: Library<80>-Footnote-665501105
Ref: Library<80>-Footnote-675501171
Ref: Library<80>-Footnote-685501237
Ref: Library<80>-Footnote-695501303
Ref: Library<80>-Footnote-705501369
Ref: Library<80>-Footnote-715501435
Ref: Library<80>-Footnote-725501501
Ref: Library<80>-Footnote-735501567
Ref: Library<80>-Footnote-745501633
Ref: Library<80>-Footnote-755501699
Ref: Library<80>-Footnote-765501765
Ref: Library<80>-Footnote-775501831
Ref: Library<80>-Footnote-785501897
Ref: Library<80>-Footnote-795501963
Ref: Library<80>-Footnote-805502029
Ref: Library<80>-Footnote-815502095
Ref: Library<80>-Footnote-825502161
Ref: Library<80>-Footnote-835502227
Ref: Library<80>-Footnote-845502293
Ref: Library<80>-Footnote-855502359
Ref: Library<80>-Footnote-865502425
Ref: Library<80>-Footnote-875502491
Ref: Library<80>-Footnote-885502557
Ref: Library<80>-Footnote-895502623
Ref: Library<80>-Footnote-905502689
Ref: Library<80>-Footnote-915502755
Ref: Library<80>-Footnote-925502821
Ref: Library<80>-Footnote-935502887
Ref: Library<80>-Footnote-945502953
Ref: Library<80>-Footnote-955503019
Ref: Library<80>-Footnote-965503085
Ref: Library<80>-Footnote-975503151
Ref: Library<80>-Footnote-985503217
Ref: Library<80>-Footnote-995503283
Ref: Library<80>-Footnote-1005503349
Ref: Library<80>-Footnote-1015503416
Ref: Library<80>-Footnote-1025503482
Ref: Library<80>-Footnote-1035503549
Ref: Library<80>-Footnote-1045503616
Ref: Library<80>-Footnote-1055503683
Ref: Library<80>-Footnote-1065503750
Ref: Library<80>-Footnote-1075503817
Ref: Library<80>-Footnote-1085503884
Ref: Library<80>-Footnote-1095503951
Ref: Library<80>-Footnote-1105504018
Ref: Library<80>-Footnote-1115504085
Ref: Library<80>-Footnote-1125504152
Ref: Library<80>-Footnote-1135504219
Ref: Library<80>-Footnote-1145504286
Ref: Library<80>-Footnote-1155504353
Ref: Library<80>-Footnote-1165504420
Ref: Library<80>-Footnote-1175504487
Ref: Library<80>-Footnote-1185504554
Ref: Library<80>-Footnote-1195504621
Ref: Library<80>-Footnote-1205504688
Node: IDLE<57>5504755
Ref: whatsnew/changelog id6855504878
Ref: 1a8a5504878
Ref: IDLE<57>-Footnote-15507211
Ref: IDLE<57>-Footnote-25507275
Ref: IDLE<57>-Footnote-35507340
Ref: IDLE<57>-Footnote-45507405
Ref: IDLE<57>-Footnote-55507470
Ref: IDLE<57>-Footnote-65507535
Ref: IDLE<57>-Footnote-75507600
Ref: IDLE<57>-Footnote-85507665
Ref: IDLE<57>-Footnote-95507730
Ref: IDLE<57>-Footnote-105507795
Ref: IDLE<57>-Footnote-115507861
Ref: IDLE<57>-Footnote-125507927
Ref: IDLE<57>-Footnote-135507993
Ref: IDLE<57>-Footnote-145508059
Ref: IDLE<57>-Footnote-155508125
Node: Documentation<67>5508191
Ref: whatsnew/changelog id6865508312
Ref: 1a8b5508312
Ref: Documentation<67>-Footnote-15509266
Ref: Documentation<67>-Footnote-25509331
Ref: Documentation<67>-Footnote-35509396
Ref: Documentation<67>-Footnote-45509438
Ref: Documentation<67>-Footnote-55509503
Ref: Documentation<67>-Footnote-65509567
Ref: Documentation<67>-Footnote-75509632
Ref: Documentation<67>-Footnote-85509697
Node: Tests<72>5509762
Ref: whatsnew/changelog id6875509884
Ref: 1a8c5509884
Ref: Tests<72>-Footnote-15510757
Ref: Tests<72>-Footnote-25510822
Ref: Tests<72>-Footnote-35510887
Ref: Tests<72>-Footnote-45510952
Ref: Tests<72>-Footnote-55511017
Ref: Tests<72>-Footnote-65511082
Ref: Tests<72>-Footnote-75511147
Node: Build<77>5511212
Ref: whatsnew/changelog id6885511328
Ref: 1a8d5511328
Ref: Build<77>-Footnote-15513850
Ref: Build<77>-Footnote-25513915
Ref: Build<77>-Footnote-35513980
Ref: Build<77>-Footnote-45514045
Ref: Build<77>-Footnote-55514110
Ref: Build<77>-Footnote-65514175
Ref: Build<77>-Footnote-75514240
Ref: Build<77>-Footnote-85514305
Ref: Build<77>-Footnote-95514370
Ref: Build<77>-Footnote-105514435
Ref: Build<77>-Footnote-115514501
Ref: Build<77>-Footnote-125514567
Ref: Build<77>-Footnote-135514633
Ref: Build<77>-Footnote-145514699
Ref: Build<77>-Footnote-155514765
Ref: Build<77>-Footnote-165514831
Ref: Build<77>-Footnote-175514897
Node: Windows<67>5514963
Ref: whatsnew/changelog id6895515085
Ref: 1a8e5515085
Ref: Windows<67>-Footnote-15515791
Ref: Windows<67>-Footnote-25515856
Ref: Windows<67>-Footnote-35515921
Ref: Windows<67>-Footnote-45515986
Ref: Windows<67>-Footnote-55516051
Ref: Windows<67>-Footnote-65516116
Node: Tools/Demos<42>5516181
Ref: whatsnew/changelog id6905516285
Ref: 1a8f5516285
Ref: Tools/Demos<42>-Footnote-15516905
Ref: Tools/Demos<42>-Footnote-25516970
Ref: Tools/Demos<42>-Footnote-35517035
Ref: Tools/Demos<42>-Footnote-45517100
Node: Python 3 5 1 final5517165
Ref: whatsnew/changelog python-3-5-1-final5517329
Ref: 1a905517329
Node: Core and Builtins<82>5517490
Ref: whatsnew/changelog id6915517586
Ref: 1a915517586
Ref: Core and Builtins<82>-Footnote-15517770
Node: Windows<68>5517835
Ref: whatsnew/changelog id6925517931
Ref: 1a925517931
Ref: Windows<68>-Footnote-15518121
Node: Python 3 5 1 release candidate 15518186
Ref: whatsnew/changelog python-3-5-1-release-candidate-15518336
Ref: 1a935518336
Node: Core and Builtins<83>5518675
Ref: whatsnew/changelog id6935518785
Ref: 1a945518785
Ref: Core and Builtins<83>-Footnote-15521921
Ref: Core and Builtins<83>-Footnote-25521986
Ref: Core and Builtins<83>-Footnote-35522051
Ref: Core and Builtins<83>-Footnote-45522116
Ref: Core and Builtins<83>-Footnote-55522181
Ref: Core and Builtins<83>-Footnote-65522246
Ref: Core and Builtins<83>-Footnote-75522311
Ref: Core and Builtins<83>-Footnote-85522376
Ref: Core and Builtins<83>-Footnote-95522441
Ref: Core and Builtins<83>-Footnote-105522506
Ref: Core and Builtins<83>-Footnote-115522572
Ref: Core and Builtins<83>-Footnote-125522638
Ref: Core and Builtins<83>-Footnote-135522704
Ref: Core and Builtins<83>-Footnote-145522770
Ref: Core and Builtins<83>-Footnote-155522836
Ref: Core and Builtins<83>-Footnote-165522902
Ref: Core and Builtins<83>-Footnote-175522968
Ref: Core and Builtins<83>-Footnote-185523034
Ref: Core and Builtins<83>-Footnote-195523100
Node: Library<81>5523166
Ref: whatsnew/changelog id6945523293
Ref: 1a955523293
Ref: Library<81>-Footnote-15533631
Ref: Library<81>-Footnote-25533696
Ref: Library<81>-Footnote-35533761
Ref: Library<81>-Footnote-45533826
Ref: Library<81>-Footnote-55533890
Ref: Library<81>-Footnote-65533955
Ref: Library<81>-Footnote-75534020
Ref: Library<81>-Footnote-85534085
Ref: Library<81>-Footnote-95534150
Ref: Library<81>-Footnote-105534215
Ref: Library<81>-Footnote-115534281
Ref: Library<81>-Footnote-125534347
Ref: Library<81>-Footnote-135534413
Ref: Library<81>-Footnote-145534479
Ref: Library<81>-Footnote-155534545
Ref: Library<81>-Footnote-165534611
Ref: Library<81>-Footnote-175534677
Ref: Library<81>-Footnote-185534743
Ref: Library<81>-Footnote-195534809
Ref: Library<81>-Footnote-205534875
Ref: Library<81>-Footnote-215534941
Ref: Library<81>-Footnote-225535007
Ref: Library<81>-Footnote-235535073
Ref: Library<81>-Footnote-245535139
Ref: Library<81>-Footnote-255535205
Ref: Library<81>-Footnote-265535271
Ref: Library<81>-Footnote-275535337
Ref: Library<81>-Footnote-285535403
Ref: Library<81>-Footnote-295535469
Ref: Library<81>-Footnote-305535535
Ref: Library<81>-Footnote-315535601
Ref: Library<81>-Footnote-325535667
Ref: Library<81>-Footnote-335535733
Ref: Library<81>-Footnote-345535799
Ref: Library<81>-Footnote-355535865
Ref: Library<81>-Footnote-365535931
Ref: Library<81>-Footnote-375535997
Ref: Library<81>-Footnote-385536063
Ref: Library<81>-Footnote-395536129
Ref: Library<81>-Footnote-405536195
Ref: Library<81>-Footnote-415536261
Ref: Library<81>-Footnote-425536327
Ref: Library<81>-Footnote-435536393
Ref: Library<81>-Footnote-445536459
Ref: Library<81>-Footnote-455536525
Ref: Library<81>-Footnote-465536591
Ref: Library<81>-Footnote-475536657
Ref: Library<81>-Footnote-485536723
Ref: Library<81>-Footnote-495536789
Ref: Library<81>-Footnote-505536855
Ref: Library<81>-Footnote-515536921
Ref: Library<81>-Footnote-525536987
Ref: Library<81>-Footnote-535537053
Ref: Library<81>-Footnote-545537119
Ref: Library<81>-Footnote-555537185
Ref: Library<81>-Footnote-565537251
Ref: Library<81>-Footnote-575537317
Ref: Library<81>-Footnote-585537383
Ref: Library<81>-Footnote-595537449
Ref: Library<81>-Footnote-605537515
Ref: Library<81>-Footnote-615537581
Ref: Library<81>-Footnote-625537647
Ref: Library<81>-Footnote-635537713
Ref: Library<81>-Footnote-645537779
Ref: Library<81>-Footnote-655537845
Ref: Library<81>-Footnote-665537911
Ref: Library<81>-Footnote-675537977
Ref: Library<81>-Footnote-685538043
Ref: Library<81>-Footnote-695538109
Ref: Library<81>-Footnote-705538175
Node: IDLE<58>5538241
Ref: whatsnew/changelog id6955538364
Ref: 1a965538364
Ref: IDLE<58>-Footnote-15543281
Ref: IDLE<58>-Footnote-25543346
Ref: IDLE<58>-Footnote-35543411
Ref: IDLE<58>-Footnote-45543476
Ref: IDLE<58>-Footnote-55543541
Ref: IDLE<58>-Footnote-65543606
Ref: IDLE<58>-Footnote-75543671
Ref: IDLE<58>-Footnote-85543736
Ref: IDLE<58>-Footnote-95543801
Ref: IDLE<58>-Footnote-105543866
Ref: IDLE<58>-Footnote-115543932
Ref: IDLE<58>-Footnote-125543998
Ref: IDLE<58>-Footnote-135544064
Ref: IDLE<58>-Footnote-145544130
Ref: IDLE<58>-Footnote-155544196
Ref: IDLE<58>-Footnote-165544262
Ref: IDLE<58>-Footnote-175544328
Ref: IDLE<58>-Footnote-185544394
Ref: IDLE<58>-Footnote-195544460
Ref: IDLE<58>-Footnote-205544526
Ref: IDLE<58>-Footnote-215544592
Ref: IDLE<58>-Footnote-225544658
Ref: IDLE<58>-Footnote-235544724
Ref: IDLE<58>-Footnote-245544790
Ref: IDLE<58>-Footnote-255544856
Node: Documentation<68>5544922
Ref: whatsnew/changelog id6965545043
Ref: 1a975545043
Ref: Documentation<68>-Footnote-15546114
Ref: Documentation<68>-Footnote-25546179
Ref: Documentation<68>-Footnote-35546244
Ref: Documentation<68>-Footnote-45546309
Ref: Documentation<68>-Footnote-55546374
Ref: Documentation<68>-Footnote-65546439
Node: Tests<73>5546504
Ref: whatsnew/changelog id6975546626
Ref: 1a985546626
Ref: Tests<73>-Footnote-15547133
Ref: Tests<73>-Footnote-25547198
Ref: Tests<73>-Footnote-35547263
Node: Build<78>5547328
Ref: whatsnew/changelog id6985547444
Ref: 1a995547444
Ref: Build<78>-Footnote-15547869
Ref: Build<78>-Footnote-25547934
Ref: Build<78>-Footnote-35547999
Node: Windows<69>5548064
Ref: whatsnew/changelog id6995548186
Ref: 1a9a5548186
Ref: Windows<69>-Footnote-15549459
Ref: Windows<69>-Footnote-25549524
Ref: Windows<69>-Footnote-35549589
Ref: Windows<69>-Footnote-45549654
Ref: Windows<69>-Footnote-55549719
Ref: Windows<69>-Footnote-65549784
Ref: Windows<69>-Footnote-75549849
Ref: Windows<69>-Footnote-85549914
Ref: Windows<69>-Footnote-95549979
Ref: Windows<69>-Footnote-105550044
Ref: Windows<69>-Footnote-115550110
Ref: Windows<69>-Footnote-125550176
Ref: Windows<69>-Footnote-135550242
Ref: Windows<69>-Footnote-145550308
Node: Tools/Demos<43>5550374
Ref: whatsnew/changelog id7005550478
Ref: 1a9b5550478
Ref: Tools/Demos<43>-Footnote-15550626
Node: Python 3 5 0 final5550691
Ref: whatsnew/changelog python-3-5-0-final5550855
Ref: 1a9c5550855
Node: Build<79>5550968
Ref: whatsnew/changelog id7015551032
Ref: 1a9d5551032
Ref: Build<79>-Footnote-15551208
Node: Python 3 5 0 release candidate 45551273
Ref: whatsnew/changelog python-3-5-0-release-candidate-45551437
Ref: 1a9e5551437
Node: Library<82>5551602
Ref: whatsnew/changelog id7025551700
Ref: 1a9f5551700
Ref: Library<82>-Footnote-15551829
Node: Build<80>5551894
Ref: whatsnew/changelog id7035551992
Ref: 1aa05551992
Ref: Build<80>-Footnote-15552174
Node: Python 3 5 0 release candidate 35552239
Ref: whatsnew/changelog python-3-5-0-release-candidate-35552417
Ref: 1aa15552417
Node: Core and Builtins<84>5552606
Ref: whatsnew/changelog id7045552716
Ref: 1aa25552716
Ref: Core and Builtins<84>-Footnote-15553084
Ref: Core and Builtins<84>-Footnote-25553149
Ref: Core and Builtins<84>-Footnote-35553214
Ref: Core and Builtins<84>-Footnote-45553279
Node: Library<83>5553321
Ref: whatsnew/changelog id7055553431
Ref: 1aa35553431
Ref: Library<83>-Footnote-15554205
Ref: Library<83>-Footnote-25554270
Ref: Library<83>-Footnote-35554335
Ref: Library<83>-Footnote-45554400
Ref: Library<83>-Footnote-55554465
Node: Python 3 5 0 release candidate 25554530
Ref: whatsnew/changelog python-3-5-0-release-candidate-25554708
Ref: 1aa45554708
Node: Core and Builtins<85>5554897
Ref: whatsnew/changelog id7065555007
Ref: 1aa55555007
Ref: Core and Builtins<85>-Footnote-15555547
Ref: Core and Builtins<85>-Footnote-25555612
Ref: Core and Builtins<85>-Footnote-35555677
Node: Library<84>5555742
Ref: whatsnew/changelog id7075555852
Ref: 1aa65555852
Ref: Library<84>-Footnote-15556129
Ref: Library<84>-Footnote-25556194
Ref: Library<84>-Footnote-35556259
Node: Python 3 5 0 release candidate 15556324
Ref: whatsnew/changelog python-3-5-0-release-candidate-15556489
Ref: 1aa75556489
Node: Core and Builtins<86>5556752
Ref: whatsnew/changelog id7085556862
Ref: 1aa85556862
Ref: Core and Builtins<86>-Footnote-15557040
Node: Library<85>5557105
Ref: whatsnew/changelog id7095557232
Ref: 1aa95557232
Ref: Library<85>-Footnote-15558808
Ref: Library<85>-Footnote-25558873
Ref: Library<85>-Footnote-35558938
Ref: Library<85>-Footnote-45559003
Ref: Library<85>-Footnote-55559067
Ref: Library<85>-Footnote-65559132
Ref: Library<85>-Footnote-75559197
Ref: Library<85>-Footnote-85559262
Ref: Library<85>-Footnote-95559327
Ref: Library<85>-Footnote-105559392
Ref: Library<85>-Footnote-115559458
Ref: Library<85>-Footnote-125559524
Ref: Library<85>-Footnote-135559590
Ref: Library<85>-Footnote-145559656
Ref: Library<85>-Footnote-155559722
Node: IDLE<59>5559788
Ref: whatsnew/changelog id7105559911
Ref: 1aaa5559911
Ref: IDLE<59>-Footnote-15560658
Ref: IDLE<59>-Footnote-25560723
Ref: IDLE<59>-Footnote-35560788
Ref: IDLE<59>-Footnote-45560853
Node: Documentation<69>5560918
Ref: whatsnew/changelog id7115561039
Ref: 1aab5561039
Ref: Documentation<69>-Footnote-15561699
Ref: Documentation<69>-Footnote-25561764
Ref: Documentation<69>-Footnote-35561829
Ref: Documentation<69>-Footnote-45561894
Node: Tests<74>5561959
Ref: whatsnew/changelog id7125562063
Ref: 1aac5562063
Ref: Tests<74>-Footnote-15562301
Node: Python 3 5 0 beta 45562366
Ref: whatsnew/changelog python-3-5-0-beta-45562518
Ref: 1aad5562518
Node: Core and Builtins<87>5562703
Ref: whatsnew/changelog id7135562800
Ref: 1aae5562800
Ref: Core and Builtins<87>-Footnote-15563603
Ref: Core and Builtins<87>-Footnote-25563668
Ref: Core and Builtins<87>-Footnote-35563733
Ref: Core and Builtins<87>-Footnote-45563775
Ref: Core and Builtins<87>-Footnote-55563840
Ref: Core and Builtins<87>-Footnote-65563905
Ref: Core and Builtins<87>-Footnote-75563970
Ref: Core and Builtins<87>-Footnote-85564035
Node: Library<86>5564100
Ref: whatsnew/changelog id7145564215
Ref: 1aaf5564215
Ref: Library<86>-Footnote-15566486
Ref: Library<86>-Footnote-25566551
Ref: Library<86>-Footnote-35566616
Ref: Library<86>-Footnote-45566681
Ref: Library<86>-Footnote-55566746
Ref: Library<86>-Footnote-65566811
Ref: Library<86>-Footnote-75566876
Ref: Library<86>-Footnote-85566941
Ref: Library<86>-Footnote-95567006
Ref: Library<86>-Footnote-105567071
Ref: Library<86>-Footnote-115567137
Ref: Library<86>-Footnote-125567203
Ref: Library<86>-Footnote-135567269
Ref: Library<86>-Footnote-145567335
Ref: Library<86>-Footnote-155567401
Ref: Library<86>-Footnote-165567467
Ref: Library<86>-Footnote-175567533
Ref: Library<86>-Footnote-185567599
Ref: Library<86>-Footnote-195567665
Node: Build<81>5567731
Ref: whatsnew/changelog id7155567816
Ref: 1ab05567816
Ref: Build<81>-Footnote-15567981
Node: Python 3 5 0 beta 35568046
Ref: whatsnew/changelog python-3-5-0-beta-35568185
Ref: 1ab15568185
Node: Core and Builtins<88>5568426
Ref: whatsnew/changelog id7165568523
Ref: 1ab25568523
Ref: Core and Builtins<88>-Footnote-15569836
Ref: Core and Builtins<88>-Footnote-25569901
Ref: Core and Builtins<88>-Footnote-35569966
Ref: Core and Builtins<88>-Footnote-45570031
Ref: Core and Builtins<88>-Footnote-55570073
Ref: Core and Builtins<88>-Footnote-65570138
Node: Library<87>5570203
Ref: whatsnew/changelog id7175570318
Ref: 1ab35570318
Ref: Library<87>-Footnote-15572266
Ref: Library<87>-Footnote-25572331
Ref: Library<87>-Footnote-35572396
Ref: Library<87>-Footnote-45572461
Ref: Library<87>-Footnote-55572526
Ref: Library<87>-Footnote-65572591
Ref: Library<87>-Footnote-75572656
Ref: Library<87>-Footnote-85572721
Ref: Library<87>-Footnote-95572786
Ref: Library<87>-Footnote-105572851
Ref: Library<87>-Footnote-115572917
Ref: Library<87>-Footnote-125572983
Ref: Library<87>-Footnote-135573049
Ref: Library<87>-Footnote-145573115
Ref: Library<87>-Footnote-155573181
Ref: Library<87>-Footnote-165573247
Ref: Library<87>-Footnote-175573313
Ref: Library<87>-Footnote-185573379
Node: Tests<75>5573445
Ref: whatsnew/changelog id7185573556
Ref: 1ab45573556
Ref: Tests<75>-Footnote-15573838
Ref: Tests<75>-Footnote-25573903
Node: Documentation<70>5573968
Ref: whatsnew/changelog id7195574077
Ref: 1ab55574077
Ref: Documentation<70>-Footnote-15574417
Ref: Documentation<70>-Footnote-25574482
Node: Build<82>5574547
Ref: whatsnew/changelog id7205574638
Ref: 1ab65574638
Ref: Build<82>-Footnote-15574803
Node: Python 3 5 0 beta 25574868
Ref: whatsnew/changelog python-3-5-0-beta-25575007
Ref: 1ab75575007
Node: Core and Builtins<89>5575172
Ref: whatsnew/changelog id7215575269
Ref: 1ab85575269
Ref: Core and Builtins<89>-Footnote-15576022
Ref: Core and Builtins<89>-Footnote-25576087
Ref: Core and Builtins<89>-Footnote-35576152
Ref: Core and Builtins<89>-Footnote-45576217
Ref: Core and Builtins<89>-Footnote-55576282
Node: Library<88>5576347
Ref: whatsnew/changelog id7225576444
Ref: 1ab95576444
Ref: Library<88>-Footnote-15577151
Ref: Library<88>-Footnote-25577216
Ref: Library<88>-Footnote-35577281
Ref: Library<88>-Footnote-45577323
Ref: Library<88>-Footnote-55577387
Ref: Library<88>-Footnote-65577452
Ref: Library<88>-Footnote-75577517
Node: Python 3 5 0 beta 15577582
Ref: whatsnew/changelog python-3-5-0-beta-15577722
Ref: 1aba5577722
Node: Core and Builtins<90>5577993
Ref: whatsnew/changelog id7235578090
Ref: 1abb5578090
Ref: Core and Builtins<90>-Footnote-15579963
Ref: Core and Builtins<90>-Footnote-25580028
Ref: Core and Builtins<90>-Footnote-35580093
Ref: Core and Builtins<90>-Footnote-45580158
Ref: Core and Builtins<90>-Footnote-55580223
Ref: Core and Builtins<90>-Footnote-65580288
Ref: Core and Builtins<90>-Footnote-75580353
Ref: Core and Builtins<90>-Footnote-85580418
Ref: Core and Builtins<90>-Footnote-95580483
Ref: Core and Builtins<90>-Footnote-105580548
Ref: Core and Builtins<90>-Footnote-115580613
Ref: Core and Builtins<90>-Footnote-125580679
Ref: Core and Builtins<90>-Footnote-135580745
Ref: Core and Builtins<90>-Footnote-145580811
Ref: Core and Builtins<90>-Footnote-155580877
Ref: Core and Builtins<90>-Footnote-165580943
Ref: Core and Builtins<90>-Footnote-175581009
Ref: Core and Builtins<90>-Footnote-185581074
Ref: Core and Builtins<90>-Footnote-195581140
Node: Library<89>5581206
Ref: whatsnew/changelog id7245581320
Ref: 1abc5581320
Ref: Library<89>-Footnote-15588956
Ref: Library<89>-Footnote-25589021
Ref: Library<89>-Footnote-35589086
Ref: Library<89>-Footnote-45589151
Ref: Library<89>-Footnote-55589216
Ref: Library<89>-Footnote-65589281
Ref: Library<89>-Footnote-75589346
Ref: Library<89>-Footnote-85589411
Ref: Library<89>-Footnote-95589476
Ref: Library<89>-Footnote-105589541
Ref: Library<89>-Footnote-115589606
Ref: Library<89>-Footnote-125589672
Ref: Library<89>-Footnote-135589738
Ref: Library<89>-Footnote-145589804
Ref: Library<89>-Footnote-155589869
Ref: Library<89>-Footnote-165589935
Ref: Library<89>-Footnote-175590001
Ref: Library<89>-Footnote-185590067
Ref: Library<89>-Footnote-195590133
Ref: Library<89>-Footnote-205590199
Ref: Library<89>-Footnote-215590265
Ref: Library<89>-Footnote-225590331
Ref: Library<89>-Footnote-235590397
Ref: Library<89>-Footnote-245590463
Ref: Library<89>-Footnote-255590529
Ref: Library<89>-Footnote-265590594
Ref: Library<89>-Footnote-275590660
Ref: Library<89>-Footnote-285590726
Ref: Library<89>-Footnote-295590792
Ref: Library<89>-Footnote-305590858
Ref: Library<89>-Footnote-315590924
Ref: Library<89>-Footnote-325590990
Ref: Library<89>-Footnote-335591056
Ref: Library<89>-Footnote-345591122
Ref: Library<89>-Footnote-355591188
Ref: Library<89>-Footnote-365591254
Ref: Library<89>-Footnote-375591320
Ref: Library<89>-Footnote-385591386
Ref: Library<89>-Footnote-395591452
Ref: Library<89>-Footnote-405591518
Ref: Library<89>-Footnote-415591584
Ref: Library<89>-Footnote-425591649
Ref: Library<89>-Footnote-435591715
Ref: Library<89>-Footnote-445591781
Ref: Library<89>-Footnote-455591847
Ref: Library<89>-Footnote-465591913
Ref: Library<89>-Footnote-475591979
Ref: Library<89>-Footnote-485592045
Ref: Library<89>-Footnote-495592111
Ref: Library<89>-Footnote-505592177
Ref: Library<89>-Footnote-515592243
Ref: Library<89>-Footnote-525592309
Ref: Library<89>-Footnote-535592375
Ref: Library<89>-Footnote-545592441
Ref: Library<89>-Footnote-555592507
Ref: Library<89>-Footnote-565592573
Node: IDLE<60>5592639
Ref: whatsnew/changelog id7255592741
Ref: 1abd5592741
Ref: IDLE<60>-Footnote-15592910
Node: Tests<76>5592975
Ref: whatsnew/changelog id7265593083
Ref: 1abe5593083
Ref: Tests<76>-Footnote-15593377
Ref: Tests<76>-Footnote-25593442
Node: Documentation<71>5593506
Ref: whatsnew/changelog id7275593621
Ref: 1abf5593621
Ref: Documentation<71>-Footnote-15594028
Ref: Documentation<71>-Footnote-25594093
Ref: Documentation<71>-Footnote-35594158
Node: Tools/Demos<44>5594223
Ref: whatsnew/changelog id7285594320
Ref: 1ac05594320
Ref: Tools/Demos<44>-Footnote-15594829
Ref: Tools/Demos<44>-Footnote-25594894
Ref: Tools/Demos<44>-Footnote-35594959
Ref: Tools/Demos<44>-Footnote-45595024
Node: Python 3 5 0 alpha 45595089
Ref: whatsnew/changelog python-3-5-0-alpha-45595230
Ref: 1ac15595230
Node: Core and Builtins<91>5595489
Ref: whatsnew/changelog id7295595587
Ref: 1ac25595587
Ref: Core and Builtins<91>-Footnote-15596952
Ref: Core and Builtins<91>-Footnote-25597017
Ref: Core and Builtins<91>-Footnote-35597059
Ref: Core and Builtins<91>-Footnote-45597124
Ref: Core and Builtins<91>-Footnote-55597189
Ref: Core and Builtins<91>-Footnote-65597231
Ref: Core and Builtins<91>-Footnote-75597296
Ref: Core and Builtins<91>-Footnote-85597361
Ref: Core and Builtins<91>-Footnote-95597426
Ref: Core and Builtins<91>-Footnote-105597491
Ref: Core and Builtins<91>-Footnote-115597557
Node: Library<90>5597623
Ref: whatsnew/changelog id7305597739
Ref: 1ac35597739
Ref: Library<90>-Footnote-15604438
Ref: Library<90>-Footnote-25604503
Ref: Library<90>-Footnote-35604568
Ref: Library<90>-Footnote-45604632
Ref: Library<90>-Footnote-55604697
Ref: Library<90>-Footnote-65604762
Ref: Library<90>-Footnote-75604826
Ref: Library<90>-Footnote-85604891
Ref: Library<90>-Footnote-95604956
Ref: Library<90>-Footnote-105605021
Ref: Library<90>-Footnote-115605087
Ref: Library<90>-Footnote-125605153
Ref: Library<90>-Footnote-135605219
Ref: Library<90>-Footnote-145605285
Ref: Library<90>-Footnote-155605351
Ref: Library<90>-Footnote-165605417
Ref: Library<90>-Footnote-175605483
Ref: Library<90>-Footnote-185605549
Ref: Library<90>-Footnote-195605615
Ref: Library<90>-Footnote-205605681
Ref: Library<90>-Footnote-215605747
Ref: Library<90>-Footnote-225605813
Ref: Library<90>-Footnote-235605879
Ref: Library<90>-Footnote-245605945
Ref: Library<90>-Footnote-255606011
Ref: Library<90>-Footnote-265606077
Ref: Library<90>-Footnote-275606143
Ref: Library<90>-Footnote-285606209
Ref: Library<90>-Footnote-295606275
Ref: Library<90>-Footnote-305606341
Ref: Library<90>-Footnote-315606406
Ref: Library<90>-Footnote-325606472
Ref: Library<90>-Footnote-335606538
Ref: Library<90>-Footnote-345606604
Ref: Library<90>-Footnote-355606670
Ref: Library<90>-Footnote-365606736
Ref: Library<90>-Footnote-375606802
Ref: Library<90>-Footnote-385606868
Ref: Library<90>-Footnote-395606934
Ref: Library<90>-Footnote-405607000
Ref: Library<90>-Footnote-415607066
Ref: Library<90>-Footnote-425607132
Ref: Library<90>-Footnote-435607175
Ref: Library<90>-Footnote-445607241
Ref: Library<90>-Footnote-455607307
Ref: Library<90>-Footnote-465607373
Ref: Library<90>-Footnote-475607439
Ref: Library<90>-Footnote-485607505
Node: Build<83>5607571
Ref: whatsnew/changelog id7315607675
Ref: 1ac45607675
Ref: Build<83>-Footnote-15607952
Ref: Build<83>-Footnote-25608017
Node: Tests<77>5608082
Ref: whatsnew/changelog id7325608190
Ref: 1ac55608190
Ref: Tests<77>-Footnote-15608491
Ref: Tests<77>-Footnote-25608556
Node: Tools/Demos<45>5608621
Ref: whatsnew/changelog id7335608729
Ref: 1ac65608729
Ref: Tools/Demos<45>-Footnote-15609753
Ref: Tools/Demos<45>-Footnote-25609818
Ref: Tools/Demos<45>-Footnote-35609883
Ref: Tools/Demos<45>-Footnote-45609948
Ref: Tools/Demos<45>-Footnote-55610013
Ref: Tools/Demos<45>-Footnote-65610078
Node: C API<67>5610143
Ref: whatsnew/changelog id7345610233
Ref: 1ac75610233
Ref: C API<67>-Footnote-15610388
Node: Python 3 5 0 alpha 35610453
Ref: whatsnew/changelog python-3-5-0-alpha-35610595
Ref: 1ac85610595
Node: Core and Builtins<92>5610834
Ref: whatsnew/changelog id7355610932
Ref: 1ac95610932
Ref: Core and Builtins<92>-Footnote-15611726
Ref: Core and Builtins<92>-Footnote-25611791
Ref: Core and Builtins<92>-Footnote-35611856
Ref: Core and Builtins<92>-Footnote-45611921
Ref: Core and Builtins<92>-Footnote-55611986
Ref: Core and Builtins<92>-Footnote-65612051
Node: Library<91>5612116
Ref: whatsnew/changelog id7365612232
Ref: 1aca5612232
Ref: Library<91>-Footnote-15618642
Ref: Library<91>-Footnote-25618707
Ref: Library<91>-Footnote-35618772
Ref: Library<91>-Footnote-45618837
Ref: Library<91>-Footnote-55618902
Ref: Library<91>-Footnote-65618967
Ref: Library<91>-Footnote-75619032
Ref: Library<91>-Footnote-85619097
Ref: Library<91>-Footnote-95619162
Ref: Library<91>-Footnote-105619227
Ref: Library<91>-Footnote-115619293
Ref: Library<91>-Footnote-125619359
Ref: Library<91>-Footnote-135619425
Ref: Library<91>-Footnote-145619491
Ref: Library<91>-Footnote-155619556
Ref: Library<91>-Footnote-165619622
Ref: Library<91>-Footnote-175619688
Ref: Library<91>-Footnote-185619754
Ref: Library<91>-Footnote-195619820
Ref: Library<91>-Footnote-205619886
Ref: Library<91>-Footnote-215619952
Ref: Library<91>-Footnote-225620018
Ref: Library<91>-Footnote-235620084
Ref: Library<91>-Footnote-245620150
Ref: Library<91>-Footnote-255620216
Ref: Library<91>-Footnote-265620282
Ref: Library<91>-Footnote-275620348
Ref: Library<91>-Footnote-285620414
Ref: Library<91>-Footnote-295620480
Ref: Library<91>-Footnote-305620546
Ref: Library<91>-Footnote-315620611
Ref: Library<91>-Footnote-325620677
Ref: Library<91>-Footnote-335620743
Ref: Library<91>-Footnote-345620809
Ref: Library<91>-Footnote-355620874
Ref: Library<91>-Footnote-365620940
Ref: Library<91>-Footnote-375621006
Ref: Library<91>-Footnote-385621072
Ref: Library<91>-Footnote-395621138
Ref: Library<91>-Footnote-405621204
Ref: Library<91>-Footnote-415621270
Ref: Library<91>-Footnote-425621336
Node: Build<84>5621402
Ref: whatsnew/changelog id7375621506
Ref: 1acb5621506
Ref: Build<84>-Footnote-15621651
Node: Tests<78>5621716
Ref: whatsnew/changelog id7385621824
Ref: 1acc5621824
Ref: Tests<78>-Footnote-15622049
Ref: Tests<78>-Footnote-25622114
Node: Tools/Demos<46>5622179
Ref: whatsnew/changelog id7395622269
Ref: 1acd5622269
Ref: Tools/Demos<46>-Footnote-15622538
Node: Python 3 5 0 alpha 25622603
Ref: whatsnew/changelog python-3-5-0-alpha-25622745
Ref: 1ace5622745
Node: Core and Builtins<93>5622976
Ref: whatsnew/changelog id7405623074
Ref: 1acf5623074
Ref: Core and Builtins<93>-Footnote-15623372
Node: Library<92>5623437
Ref: whatsnew/changelog id7415623553
Ref: 1ad05623553
Ref: Library<92>-Footnote-15627846
Ref: Library<92>-Footnote-25627911
Ref: Library<92>-Footnote-35627953
Ref: Library<92>-Footnote-45628018
Ref: Library<92>-Footnote-55628083
Ref: Library<92>-Footnote-65628148
Ref: Library<92>-Footnote-75628213
Ref: Library<92>-Footnote-85628278
Ref: Library<92>-Footnote-95628343
Ref: Library<92>-Footnote-105628407
Ref: Library<92>-Footnote-115628473
Ref: Library<92>-Footnote-125628539
Ref: Library<92>-Footnote-135628605
Ref: Library<92>-Footnote-145628671
Ref: Library<92>-Footnote-155628737
Ref: Library<92>-Footnote-165628803
Ref: Library<92>-Footnote-175628868
Ref: Library<92>-Footnote-185628935
Ref: Library<92>-Footnote-195629000
Ref: Library<92>-Footnote-205629066
Ref: Library<92>-Footnote-215629131
Ref: Library<92>-Footnote-225629197
Ref: Library<92>-Footnote-235629263
Ref: Library<92>-Footnote-245629329
Ref: Library<92>-Footnote-255629395
Ref: Library<92>-Footnote-265629461
Ref: Library<92>-Footnote-275629527
Ref: Library<92>-Footnote-285629593
Ref: Library<92>-Footnote-295629659
Ref: Library<92>-Footnote-305629725
Ref: Library<92>-Footnote-315629791
Ref: Library<92>-Footnote-325629857
Ref: Library<92>-Footnote-335629923
Ref: Library<92>-Footnote-345629989
Ref: Library<92>-Footnote-355630055
Ref: Library<92>-Footnote-365630121
Ref: Library<92>-Footnote-375630187
Node: Build<85>5630253
Ref: whatsnew/changelog id7425630357
Ref: 1ad15630357
Ref: Build<85>-Footnote-15630624
Ref: Build<85>-Footnote-25630689
Node: C API<68>5630754
Ref: whatsnew/changelog id7435630858
Ref: 1ad25630858
Ref: C API<68>-Footnote-15631040
Node: Windows<70>5631105
Ref: whatsnew/changelog id7445631191
Ref: 1ad35631191
Ref: Windows<70>-Footnote-15631488
Ref: Windows<70>-Footnote-25631553
Ref: Windows<70>-Footnote-35631595
Node: Python 3 5 0 alpha 15631660
Ref: whatsnew/changelog python-3-5-0-alpha-15631773
Ref: 1ad45631773
Node: Core and Builtins<94>5632110
Ref: whatsnew/changelog id7455632208
Ref: 1ad55632208
Ref: Core and Builtins<94>-Footnote-15642051
Ref: Core and Builtins<94>-Footnote-25642116
Ref: Core and Builtins<94>-Footnote-35642181
Ref: Core and Builtins<94>-Footnote-45642246
Ref: Core and Builtins<94>-Footnote-55642311
Ref: Core and Builtins<94>-Footnote-65642376
Ref: Core and Builtins<94>-Footnote-75642441
Ref: Core and Builtins<94>-Footnote-85642506
Ref: Core and Builtins<94>-Footnote-95642571
Ref: Core and Builtins<94>-Footnote-105642636
Ref: Core and Builtins<94>-Footnote-115642702
Ref: Core and Builtins<94>-Footnote-125642768
Ref: Core and Builtins<94>-Footnote-135642834
Ref: Core and Builtins<94>-Footnote-145642900
Ref: Core and Builtins<94>-Footnote-155642966
Ref: Core and Builtins<94>-Footnote-165643032
Ref: Core and Builtins<94>-Footnote-175643098
Ref: Core and Builtins<94>-Footnote-185643164
Ref: Core and Builtins<94>-Footnote-195643230
Ref: Core and Builtins<94>-Footnote-205643296
Ref: Core and Builtins<94>-Footnote-215643362
Ref: Core and Builtins<94>-Footnote-225643428
Ref: Core and Builtins<94>-Footnote-235643494
Ref: Core and Builtins<94>-Footnote-245643560
Ref: Core and Builtins<94>-Footnote-255643626
Ref: Core and Builtins<94>-Footnote-265643692
Ref: Core and Builtins<94>-Footnote-275643758
Ref: Core and Builtins<94>-Footnote-285643824
Ref: Core and Builtins<94>-Footnote-295643890
Ref: Core and Builtins<94>-Footnote-305643956
Ref: Core and Builtins<94>-Footnote-315644022
Ref: Core and Builtins<94>-Footnote-325644088
Ref: Core and Builtins<94>-Footnote-335644154
Ref: Core and Builtins<94>-Footnote-345644222
Ref: Core and Builtins<94>-Footnote-355644288
Ref: Core and Builtins<94>-Footnote-365644354
Ref: Core and Builtins<94>-Footnote-375644420
Ref: Core and Builtins<94>-Footnote-385644486
Ref: Core and Builtins<94>-Footnote-395644552
Ref: Core and Builtins<94>-Footnote-405644618
Ref: Core and Builtins<94>-Footnote-415644684
Ref: Core and Builtins<94>-Footnote-425644750
Ref: Core and Builtins<94>-Footnote-435644816
Ref: Core and Builtins<94>-Footnote-445644882
Ref: Core and Builtins<94>-Footnote-455644948
Ref: Core and Builtins<94>-Footnote-465645014
Ref: Core and Builtins<94>-Footnote-475645080
Ref: Core and Builtins<94>-Footnote-485645146
Ref: Core and Builtins<94>-Footnote-495645212
Ref: Core and Builtins<94>-Footnote-505645278
Ref: Core and Builtins<94>-Footnote-515645344
Ref: Core and Builtins<94>-Footnote-525645410
Ref: Core and Builtins<94>-Footnote-535645476
Ref: Core and Builtins<94>-Footnote-545645542
Ref: Core and Builtins<94>-Footnote-555645608
Ref: Core and Builtins<94>-Footnote-565645674
Ref: Core and Builtins<94>-Footnote-575645740
Ref: Core and Builtins<94>-Footnote-585645806
Ref: Core and Builtins<94>-Footnote-595645872
Ref: Core and Builtins<94>-Footnote-605645938
Ref: Core and Builtins<94>-Footnote-615646004
Ref: Core and Builtins<94>-Footnote-625646070
Ref: Core and Builtins<94>-Footnote-635646136
Ref: Core and Builtins<94>-Footnote-645646202
Ref: Core and Builtins<94>-Footnote-655646268
Ref: Core and Builtins<94>-Footnote-665646334
Ref: Core and Builtins<94>-Footnote-675646399
Ref: Core and Builtins<94>-Footnote-685646465
Ref: Core and Builtins<94>-Footnote-695646531
Ref: Core and Builtins<94>-Footnote-705646597
Ref: Core and Builtins<94>-Footnote-715646663
Ref: Core and Builtins<94>-Footnote-725646729
Ref: Core and Builtins<94>-Footnote-735646794
Node: Library<93>5646860
Ref: whatsnew/changelog id7465646975
Ref: 1ad65646975
Ref: Library<93>-Footnote-15699278
Ref: Library<93>-Footnote-25699343
Ref: Library<93>-Footnote-35699408
Ref: Library<93>-Footnote-45699473
Ref: Library<93>-Footnote-55699538
Ref: Library<93>-Footnote-65699603
Ref: Library<93>-Footnote-75699668
Ref: Library<93>-Footnote-85699733
Ref: Library<93>-Footnote-95699798
Ref: Library<93>-Footnote-105699863
Ref: Library<93>-Footnote-115699929
Ref: Library<93>-Footnote-125699995
Ref: Library<93>-Footnote-135700061
Ref: Library<93>-Footnote-145700127
Ref: Library<93>-Footnote-155700193
Ref: Library<93>-Footnote-165700259
Ref: Library<93>-Footnote-175700325
Ref: Library<93>-Footnote-185700391
Ref: Library<93>-Footnote-195700457
Ref: Library<93>-Footnote-205700523
Ref: Library<93>-Footnote-215700589
Ref: Library<93>-Footnote-225700655
Ref: Library<93>-Footnote-235700721
Ref: Library<93>-Footnote-245700787
Ref: Library<93>-Footnote-255700853
Ref: Library<93>-Footnote-265700919
Ref: Library<93>-Footnote-275700985
Ref: Library<93>-Footnote-285701051
Ref: Library<93>-Footnote-295701117
Ref: Library<93>-Footnote-305701183
Ref: Library<93>-Footnote-315701249
Ref: Library<93>-Footnote-325701315
Ref: Library<93>-Footnote-335701381
Ref: Library<93>-Footnote-345701447
Ref: Library<93>-Footnote-355701513
Ref: Library<93>-Footnote-365701579
Ref: Library<93>-Footnote-375701645
Ref: Library<93>-Footnote-385701711
Ref: Library<93>-Footnote-395701777
Ref: Library<93>-Footnote-405701843
Ref: Library<93>-Footnote-415701909
Ref: Library<93>-Footnote-425701975
Ref: Library<93>-Footnote-435702041
Ref: Library<93>-Footnote-445702107
Ref: Library<93>-Footnote-455702173
Ref: Library<93>-Footnote-465702239
Ref: Library<93>-Footnote-475702305
Ref: Library<93>-Footnote-485702371
Ref: Library<93>-Footnote-495702437
Ref: Library<93>-Footnote-505702503
Ref: Library<93>-Footnote-515702569
Ref: Library<93>-Footnote-525702635
Ref: Library<93>-Footnote-535702701
Ref: Library<93>-Footnote-545702767
Ref: Library<93>-Footnote-555702833
Ref: Library<93>-Footnote-565702901
Ref: Library<93>-Footnote-575702967
Ref: Library<93>-Footnote-585703033
Ref: Library<93>-Footnote-595703099
Ref: Library<93>-Footnote-605703165
Ref: Library<93>-Footnote-615703231
Ref: Library<93>-Footnote-625703301
Ref: Library<93>-Footnote-635703367
Ref: Library<93>-Footnote-645703433
Ref: Library<93>-Footnote-655703499
Ref: Library<93>-Footnote-665703565
Ref: Library<93>-Footnote-675703631
Ref: Library<93>-Footnote-685703697
Ref: Library<93>-Footnote-695703763
Ref: Library<93>-Footnote-705703829
Ref: Library<93>-Footnote-715703895
Ref: Library<93>-Footnote-725703961
Ref: Library<93>-Footnote-735704027
Ref: Library<93>-Footnote-745704093
Ref: Library<93>-Footnote-755704159
Ref: Library<93>-Footnote-765704225
Ref: Library<93>-Footnote-775704291
Ref: Library<93>-Footnote-785704357
Ref: Library<93>-Footnote-795704423
Ref: Library<93>-Footnote-805704489
Ref: Library<93>-Footnote-815704555
Ref: Library<93>-Footnote-825704621
Ref: Library<93>-Footnote-835704687
Ref: Library<93>-Footnote-845704753
Ref: Library<93>-Footnote-855704819
Ref: Library<93>-Footnote-865704885
Ref: Library<93>-Footnote-875704951
Ref: Library<93>-Footnote-885705017
Ref: Library<93>-Footnote-895705083
Ref: Library<93>-Footnote-905705149
Ref: Library<93>-Footnote-915705215
Ref: Library<93>-Footnote-925705281
Ref: Library<93>-Footnote-935705347
Ref: Library<93>-Footnote-945705413
Ref: Library<93>-Footnote-955705479
Ref: Library<93>-Footnote-965705545
Ref: Library<93>-Footnote-975705610
Ref: Library<93>-Footnote-985705676
Ref: Library<93>-Footnote-995705742
Ref: Library<93>-Footnote-1005705808
Ref: Library<93>-Footnote-1015705874
Ref: Library<93>-Footnote-1025705941
Ref: Library<93>-Footnote-1035706008
Ref: Library<93>-Footnote-1045706075
Ref: Library<93>-Footnote-1055706142
Ref: Library<93>-Footnote-1065706209
Ref: Library<93>-Footnote-1075706276
Ref: Library<93>-Footnote-1085706342
Ref: Library<93>-Footnote-1095706408
Ref: Library<93>-Footnote-1105706475
Ref: Library<93>-Footnote-1115706542
Ref: Library<93>-Footnote-1125706609
Ref: Library<93>-Footnote-1135706676
Ref: Library<93>-Footnote-1145706743
Ref: Library<93>-Footnote-1155706810
Ref: Library<93>-Footnote-1165706877
Ref: Library<93>-Footnote-1175706944
Ref: Library<93>-Footnote-1185707011
Ref: Library<93>-Footnote-1195707078
Ref: Library<93>-Footnote-1205707145
Ref: Library<93>-Footnote-1215707212
Ref: Library<93>-Footnote-1225707281
Ref: Library<93>-Footnote-1235707348
Ref: Library<93>-Footnote-1245707415
Ref: Library<93>-Footnote-1255707482
Ref: Library<93>-Footnote-1265707549
Ref: Library<93>-Footnote-1275707616
Ref: Library<93>-Footnote-1285707683
Ref: Library<93>-Footnote-1295707750
Ref: Library<93>-Footnote-1305707817
Ref: Library<93>-Footnote-1315707884
Ref: Library<93>-Footnote-1325707951
Ref: Library<93>-Footnote-1335708018
Ref: Library<93>-Footnote-1345708085
Ref: Library<93>-Footnote-1355708152
Ref: Library<93>-Footnote-1365708219
Ref: Library<93>-Footnote-1375708286
Ref: Library<93>-Footnote-1385708353
Ref: Library<93>-Footnote-1395708420
Ref: Library<93>-Footnote-1405708487
Ref: Library<93>-Footnote-1415708554
Ref: Library<93>-Footnote-1425708621
Ref: Library<93>-Footnote-1435708687
Ref: Library<93>-Footnote-1445708753
Ref: Library<93>-Footnote-1455708820
Ref: Library<93>-Footnote-1465708887
Ref: Library<93>-Footnote-1475708954
Ref: Library<93>-Footnote-1485709021
Ref: Library<93>-Footnote-1495709088
Ref: Library<93>-Footnote-1505709155
Ref: Library<93>-Footnote-1515709222
Ref: Library<93>-Footnote-1525709289
Ref: Library<93>-Footnote-1535709356
Ref: Library<93>-Footnote-1545709423
Ref: Library<93>-Footnote-1555709490
Ref: Library<93>-Footnote-1565709557
Ref: Library<93>-Footnote-1575709624
Ref: Library<93>-Footnote-1585709690
Ref: Library<93>-Footnote-1595709757
Ref: Library<93>-Footnote-1605709824
Ref: Library<93>-Footnote-1615709891
Ref: Library<93>-Footnote-1625709958
Ref: Library<93>-Footnote-1635710025
Ref: Library<93>-Footnote-1645710092
Ref: Library<93>-Footnote-1655710159
Ref: Library<93>-Footnote-1665710226
Ref: Library<93>-Footnote-1675710293
Ref: Library<93>-Footnote-1685710360
Ref: Library<93>-Footnote-1695710427
Ref: Library<93>-Footnote-1705710494
Ref: Library<93>-Footnote-1715710561
Ref: Library<93>-Footnote-1725710628
Ref: Library<93>-Footnote-1735710695
Ref: Library<93>-Footnote-1745710762
Ref: Library<93>-Footnote-1755710829
Ref: Library<93>-Footnote-1765710896
Ref: Library<93>-Footnote-1775710963
Ref: Library<93>-Footnote-1785711030
Ref: Library<93>-Footnote-1795711097
Ref: Library<93>-Footnote-1805711164
Ref: Library<93>-Footnote-1815711231
Ref: Library<93>-Footnote-1825711298
Ref: Library<93>-Footnote-1835711365
Ref: Library<93>-Footnote-1845711432
Ref: Library<93>-Footnote-1855711499
Ref: Library<93>-Footnote-1865711566
Ref: Library<93>-Footnote-1875711633
Ref: Library<93>-Footnote-1885711700
Ref: Library<93>-Footnote-1895711766
Ref: Library<93>-Footnote-1905711833
Ref: Library<93>-Footnote-1915711900
Ref: Library<93>-Footnote-1925711967
Ref: Library<93>-Footnote-1935712034
Ref: Library<93>-Footnote-1945712101
Ref: Library<93>-Footnote-1955712168
Ref: Library<93>-Footnote-1965712235
Ref: Library<93>-Footnote-1975712301
Ref: Library<93>-Footnote-1985712368
Ref: Library<93>-Footnote-1995712435
Ref: Library<93>-Footnote-2005712502
Ref: Library<93>-Footnote-2015712569
Ref: Library<93>-Footnote-2025712636
Ref: Library<93>-Footnote-2035712703
Ref: Library<93>-Footnote-2045712769
Ref: Library<93>-Footnote-2055712836
Ref: Library<93>-Footnote-2065712903
Ref: Library<93>-Footnote-2075712970
Ref: Library<93>-Footnote-2085713037
Ref: Library<93>-Footnote-2095713104
Ref: Library<93>-Footnote-2105713171
Ref: Library<93>-Footnote-2115713238
Ref: Library<93>-Footnote-2125713305
Ref: Library<93>-Footnote-2135713372
Ref: Library<93>-Footnote-2145713439
Ref: Library<93>-Footnote-2155713506
Ref: Library<93>-Footnote-2165713573
Ref: Library<93>-Footnote-2175713640
Ref: Library<93>-Footnote-2185713707
Ref: Library<93>-Footnote-2195713774
Ref: Library<93>-Footnote-2205713841
Ref: Library<93>-Footnote-2215713908
Ref: Library<93>-Footnote-2225713975
Ref: Library<93>-Footnote-2235714042
Ref: Library<93>-Footnote-2245714109
Ref: Library<93>-Footnote-2255714175
Ref: Library<93>-Footnote-2265714241
Ref: Library<93>-Footnote-2275714308
Ref: Library<93>-Footnote-2285714375
Ref: Library<93>-Footnote-2295714442
Ref: Library<93>-Footnote-2305714509
Ref: Library<93>-Footnote-2315714576
Ref: Library<93>-Footnote-2325714643
Ref: Library<93>-Footnote-2335714710
Ref: Library<93>-Footnote-2345714777
Ref: Library<93>-Footnote-2355714844
Ref: Library<93>-Footnote-2365714911
Ref: Library<93>-Footnote-2375714978
Ref: Library<93>-Footnote-2385715045
Ref: Library<93>-Footnote-2395715112
Ref: Library<93>-Footnote-2405715179
Ref: Library<93>-Footnote-2415715246
Ref: Library<93>-Footnote-2425715313
Ref: Library<93>-Footnote-2435715380
Ref: Library<93>-Footnote-2445715447
Ref: Library<93>-Footnote-2455715514
Ref: Library<93>-Footnote-2465715580
Ref: Library<93>-Footnote-2475715647
Ref: Library<93>-Footnote-2485715714
Ref: Library<93>-Footnote-2495715781
Ref: Library<93>-Footnote-2505715848
Ref: Library<93>-Footnote-2515715915
Ref: Library<93>-Footnote-2525715982
Ref: Library<93>-Footnote-2535716049
Ref: Library<93>-Footnote-2545716116
Ref: Library<93>-Footnote-2555716183
Ref: Library<93>-Footnote-2565716250
Ref: Library<93>-Footnote-2575716317
Ref: Library<93>-Footnote-2585716384
Ref: Library<93>-Footnote-2595716451
Ref: Library<93>-Footnote-2605716518
Ref: Library<93>-Footnote-2615716585
Ref: Library<93>-Footnote-2625716652
Ref: Library<93>-Footnote-2635716719
Ref: Library<93>-Footnote-2645716786
Ref: Library<93>-Footnote-2655716853
Ref: Library<93>-Footnote-2665716920
Ref: Library<93>-Footnote-2675716987
Ref: Library<93>-Footnote-2685717054
Ref: Library<93>-Footnote-2695717121
Ref: Library<93>-Footnote-2705717188
Ref: Library<93>-Footnote-2715717255
Ref: Library<93>-Footnote-2725717322
Ref: Library<93>-Footnote-2735717389
Ref: Library<93>-Footnote-2745717456
Ref: Library<93>-Footnote-2755717523
Ref: Library<93>-Footnote-2765717590
Ref: Library<93>-Footnote-2775717657
Ref: Library<93>-Footnote-2785717723
Ref: Library<93>-Footnote-2795717790
Ref: Library<93>-Footnote-2805717857
Ref: Library<93>-Footnote-2815717924
Ref: Library<93>-Footnote-2825717991
Ref: Library<93>-Footnote-2835718058
Ref: Library<93>-Footnote-2845718125
Ref: Library<93>-Footnote-2855718192
Ref: Library<93>-Footnote-2865718259
Ref: Library<93>-Footnote-2875718326
Ref: Library<93>-Footnote-2885718393
Ref: Library<93>-Footnote-2895718460
Ref: Library<93>-Footnote-2905718504
Ref: Library<93>-Footnote-2915718571
Ref: Library<93>-Footnote-2925718638
Ref: Library<93>-Footnote-2935718705
Ref: Library<93>-Footnote-2945718772
Ref: Library<93>-Footnote-2955718839
Ref: Library<93>-Footnote-2965718906
Ref: Library<93>-Footnote-2975718973
Ref: Library<93>-Footnote-2985719040
Ref: Library<93>-Footnote-2995719107
Ref: Library<93>-Footnote-3005719174
Ref: Library<93>-Footnote-3015719241
Ref: Library<93>-Footnote-3025719308
Ref: Library<93>-Footnote-3035719375
Ref: Library<93>-Footnote-3045719442
Ref: Library<93>-Footnote-3055719509
Ref: Library<93>-Footnote-3065719576
Ref: Library<93>-Footnote-3075719643
Ref: Library<93>-Footnote-3085719710
Ref: Library<93>-Footnote-3095719777
Ref: Library<93>-Footnote-3105719844
Ref: Library<93>-Footnote-3115719911
Ref: Library<93>-Footnote-3125719978
Ref: Library<93>-Footnote-3135720045
Ref: Library<93>-Footnote-3145720112
Ref: Library<93>-Footnote-3155720179
Ref: Library<93>-Footnote-3165720245
Ref: Library<93>-Footnote-3175720312
Ref: Library<93>-Footnote-3185720379
Ref: Library<93>-Footnote-3195720446
Ref: Library<93>-Footnote-3205720513
Ref: Library<93>-Footnote-3215720580
Ref: Library<93>-Footnote-3225720647
Ref: Library<93>-Footnote-3235720714
Ref: Library<93>-Footnote-3245720781
Ref: Library<93>-Footnote-3255720848
Ref: Library<93>-Footnote-3265720915
Ref: Library<93>-Footnote-3275720982
Ref: Library<93>-Footnote-3285721049
Ref: Library<93>-Footnote-3295721116
Ref: Library<93>-Footnote-3305721183
Ref: Library<93>-Footnote-3315721250
Ref: Library<93>-Footnote-3325721317
Ref: Library<93>-Footnote-3335721384
Ref: Library<93>-Footnote-3345721451
Ref: Library<93>-Footnote-3355721518
Ref: Library<93>-Footnote-3365721584
Ref: Library<93>-Footnote-3375721651
Ref: Library<93>-Footnote-3385721718
Ref: Library<93>-Footnote-3395721789
Ref: Library<93>-Footnote-3405721856
Ref: Library<93>-Footnote-3415721923
Ref: Library<93>-Footnote-3425721990
Ref: Library<93>-Footnote-3435722057
Ref: Library<93>-Footnote-3445722124
Ref: Library<93>-Footnote-3455722191
Ref: Library<93>-Footnote-3465722258
Ref: Library<93>-Footnote-3475722325
Ref: Library<93>-Footnote-3485722392
Ref: Library<93>-Footnote-3495722459
Ref: Library<93>-Footnote-3505722526
Ref: Library<93>-Footnote-3515722593
Ref: Library<93>-Footnote-3525722660
Ref: Library<93>-Footnote-3535722727
Ref: Library<93>-Footnote-3545722794
Ref: Library<93>-Footnote-3555722861
Ref: Library<93>-Footnote-3565722928
Ref: Library<93>-Footnote-3575722995
Ref: Library<93>-Footnote-3585723062
Ref: Library<93>-Footnote-3595723129
Ref: Library<93>-Footnote-3605723196
Ref: Library<93>-Footnote-3615723263
Ref: Library<93>-Footnote-3625723330
Ref: Library<93>-Footnote-3635723397
Ref: Library<93>-Footnote-3645723464
Ref: Library<93>-Footnote-3655723531
Ref: Library<93>-Footnote-3665723598
Ref: Library<93>-Footnote-3675723665
Ref: Library<93>-Footnote-3685723732
Ref: Library<93>-Footnote-3695723799
Ref: Library<93>-Footnote-3705723866
Ref: Library<93>-Footnote-3715723933
Ref: Library<93>-Footnote-3725724000
Ref: Library<93>-Footnote-3735724066
Ref: Library<93>-Footnote-3745724133
Ref: Library<93>-Footnote-3755724200
Ref: Library<93>-Footnote-3765724267
Ref: Library<93>-Footnote-3775724334
Ref: Library<93>-Footnote-3785724401
Ref: Library<93>-Footnote-3795724468
Ref: Library<93>-Footnote-3805724535
Ref: Library<93>-Footnote-3815724602
Ref: Library<93>-Footnote-3825724669
Ref: Library<93>-Footnote-3835724736
Ref: Library<93>-Footnote-3845724803
Ref: Library<93>-Footnote-3855724870
Ref: Library<93>-Footnote-3865724936
Ref: Library<93>-Footnote-3875725003
Ref: Library<93>-Footnote-3885725070
Ref: Library<93>-Footnote-3895725137
Ref: Library<93>-Footnote-3905725204
Ref: Library<93>-Footnote-3915725269
Ref: Library<93>-Footnote-3925725336
Ref: Library<93>-Footnote-3935725403
Ref: Library<93>-Footnote-3945725470
Ref: Library<93>-Footnote-3955725537
Ref: Library<93>-Footnote-3965725604
Ref: Library<93>-Footnote-3975725671
Ref: Library<93>-Footnote-3985725738
Node: IDLE<61>5725805
Ref: whatsnew/changelog id7475725908
Ref: 1ad75725908
Ref: IDLE<61>-Footnote-15729390
Ref: IDLE<61>-Footnote-25729455
Ref: IDLE<61>-Footnote-35729520
Ref: IDLE<61>-Footnote-45729584
Ref: IDLE<61>-Footnote-55729649
Ref: IDLE<61>-Footnote-65729713
Ref: IDLE<61>-Footnote-75729778
Ref: IDLE<61>-Footnote-85729843
Ref: IDLE<61>-Footnote-95729908
Ref: IDLE<61>-Footnote-105729973
Ref: IDLE<61>-Footnote-115730039
Ref: IDLE<61>-Footnote-125730105
Ref: IDLE<61>-Footnote-135730171
Ref: IDLE<61>-Footnote-145730237
Ref: IDLE<61>-Footnote-155730303
Ref: IDLE<61>-Footnote-165730369
Ref: IDLE<61>-Footnote-175730435
Ref: IDLE<61>-Footnote-185730501
Ref: IDLE<61>-Footnote-195730567
Ref: IDLE<61>-Footnote-205730633
Ref: IDLE<61>-Footnote-215730699
Ref: IDLE<61>-Footnote-225730765
Ref: IDLE<61>-Footnote-235730831
Ref: IDLE<61>-Footnote-245730874
Ref: IDLE<61>-Footnote-255730940
Ref: IDLE<61>-Footnote-265731006
Node: Build<86>5731072
Ref: whatsnew/changelog id7485731173
Ref: 1ad85731173
Ref: Build<86>-Footnote-15734581
Ref: Build<86>-Footnote-25734646
Ref: Build<86>-Footnote-35734711
Ref: Build<86>-Footnote-45734776
Ref: Build<86>-Footnote-55734841
Ref: Build<86>-Footnote-65734906
Ref: Build<86>-Footnote-75734971
Ref: Build<86>-Footnote-85735036
Ref: Build<86>-Footnote-95735101
Ref: Build<86>-Footnote-105735166
Ref: Build<86>-Footnote-115735232
Ref: Build<86>-Footnote-125735298
Ref: Build<86>-Footnote-135735364
Ref: Build<86>-Footnote-145735430
Ref: Build<86>-Footnote-155735496
Ref: Build<86>-Footnote-165735562
Ref: Build<86>-Footnote-175735628
Ref: Build<86>-Footnote-185735694
Ref: Build<86>-Footnote-195735760
Ref: Build<86>-Footnote-205735826
Ref: Build<86>-Footnote-215735892
Ref: Build<86>-Footnote-225735958
Ref: Build<86>-Footnote-235736024
Ref: Build<86>-Footnote-245736090
Ref: Build<86>-Footnote-255736156
Ref: Build<86>-Footnote-265736222
Node: C API<69>5736288
Ref: whatsnew/changelog id7495736398
Ref: 1ad95736398
Ref: C API<69>-Footnote-15737763
Ref: C API<69>-Footnote-25737828
Ref: C API<69>-Footnote-35737893
Ref: C API<69>-Footnote-45737958
Ref: C API<69>-Footnote-55738023
Ref: C API<69>-Footnote-65738088
Ref: C API<69>-Footnote-75738153
Node: Documentation<72>5738218
Ref: whatsnew/changelog id7505738328
Ref: 1ada5738328
Ref: Documentation<72>-Footnote-15740135
Ref: Documentation<72>-Footnote-25740200
Ref: Documentation<72>-Footnote-35740265
Ref: Documentation<72>-Footnote-45740330
Ref: Documentation<72>-Footnote-55740395
Ref: Documentation<72>-Footnote-65740459
Ref: Documentation<72>-Footnote-75740524
Ref: Documentation<72>-Footnote-85740589
Ref: Documentation<72>-Footnote-95740654
Ref: Documentation<72>-Footnote-105740719
Ref: Documentation<72>-Footnote-115740785
Node: Tests<79>5740851
Ref: whatsnew/changelog id7515740967
Ref: 1adb5740967
Ref: Tests<79>-Footnote-15745158
Ref: Tests<79>-Footnote-25745223
Ref: Tests<79>-Footnote-35745288
Ref: Tests<79>-Footnote-45745353
Ref: Tests<79>-Footnote-55745418
Ref: Tests<79>-Footnote-65745483
Ref: Tests<79>-Footnote-75745548
Ref: Tests<79>-Footnote-85745613
Ref: Tests<79>-Footnote-95745678
Ref: Tests<79>-Footnote-105745743
Ref: Tests<79>-Footnote-115745809
Ref: Tests<79>-Footnote-125745875
Ref: Tests<79>-Footnote-135745941
Ref: Tests<79>-Footnote-145746007
Ref: Tests<79>-Footnote-155746072
Ref: Tests<79>-Footnote-165746138
Ref: Tests<79>-Footnote-175746204
Ref: Tests<79>-Footnote-185746270
Ref: Tests<79>-Footnote-195746336
Ref: Tests<79>-Footnote-205746402
Ref: Tests<79>-Footnote-215746468
Ref: Tests<79>-Footnote-225746534
Ref: Tests<79>-Footnote-235746600
Ref: Tests<79>-Footnote-245746666
Ref: Tests<79>-Footnote-255746732
Ref: Tests<79>-Footnote-265746798
Ref: Tests<79>-Footnote-275746864
Ref: Tests<79>-Footnote-285746930
Ref: Tests<79>-Footnote-295746996
Ref: Tests<79>-Footnote-305747062
Ref: Tests<79>-Footnote-315747128
Ref: Tests<79>-Footnote-325747194
Ref: Tests<79>-Footnote-335747260
Ref: Tests<79>-Footnote-345747326
Ref: Tests<79>-Footnote-355747392
Ref: Tests<79>-Footnote-365747458
Ref: Tests<79>-Footnote-375747524
Node: Tools/Demos<47>5747590
Ref: whatsnew/changelog id7525747700
Ref: 1adc5747700
Ref: Tools/Demos<47>-Footnote-15749362
Ref: Tools/Demos<47>-Footnote-25749427
Ref: Tools/Demos<47>-Footnote-35749492
Ref: Tools/Demos<47>-Footnote-45749557
Ref: Tools/Demos<47>-Footnote-55749622
Ref: Tools/Demos<47>-Footnote-65749687
Ref: Tools/Demos<47>-Footnote-75749752
Ref: Tools/Demos<47>-Footnote-85749817
Ref: Tools/Demos<47>-Footnote-95749882
Ref: Tools/Demos<47>-Footnote-105749947
Ref: Tools/Demos<47>-Footnote-115749990
Ref: Tools/Demos<47>-Footnote-125750056
Ref: Tools/Demos<47>-Footnote-135750122
Node: Windows<71>5750188
Ref: whatsnew/changelog id7535750280
Ref: 1add5750280
Ref: Windows<71>-Footnote-15751487
Ref: Windows<71>-Footnote-25751552
Ref: Windows<71>-Footnote-35751617
Ref: Windows<71>-Footnote-45751682
Ref: Windows<71>-Footnote-55751747
Ref: Windows<71>-Footnote-65751812
Ref: Windows<71>-Footnote-75751877
Node: Python 教學5751942
Ref: tutorial/index doc5752066
Ref: 1ade5752066
Ref: tutorial/index the-python-tutorial5752066
Ref: 1adf5752066
Ref: tutorial/index tutorial-index5752066
Ref: 1ae05752066
Node: 淺嘗滋味5754852
Ref: tutorial/appetite doc5754946
Ref: 1ae45754946
Ref: tutorial/appetite tut-intro5754946
Ref: 1ae55754946
Ref: tutorial/appetite whetting-your-appetite5754946
Ref: 1ae65754946
Node: 使用 Python 直譯器5759329
Ref: tutorial/interpreter doc5759464
Ref: 1ae75759464
Ref: tutorial/interpreter tut-using5759464
Ref: 1ae85759464
Ref: tutorial/interpreter using-the-python-interpreter5759464
Ref: 1ae95759464
Node: 啟動直譯器5759575
Ref: tutorial/interpreter invoking-the-interpreter5759683
Ref: 1aea5759683
Ref: tutorial/interpreter tut-invoking5759683
Ref: 1aeb5759683
Ref: 啟動直譯器-Footnote-15762456
Ref: 啟動直譯器-Footnote-25762617
Node: 傳遞引數5762678
Ref: tutorial/interpreter argument-passing5762763
Ref: 1aef5762763
Ref: tutorial/interpreter tut-argpassing5762763
Ref: 1af05762763
Node: 互動模式5763591
Ref: tutorial/interpreter interactive-mode5763676
Ref: 1af15763676
Ref: tutorial/interpreter tut-interactive5763676
Ref: f695763676
Node: 直譯器與它的環境5764677
Ref: tutorial/interpreter the-interpreter-and-its-environment5764785
Ref: 1af25764785
Ref: tutorial/interpreter tut-interp5764785
Ref: 1af35764785
Node: 原始碼的字元編碼 encoding5764924
Ref: tutorial/interpreter source-code-encoding5765018
Ref: 1af45765018
Ref: tutorial/interpreter tut-source-encoding5765018
Ref: 1af55765018
Node: 一個非正式的 Python 簡介5766142
Ref: tutorial/introduction doc5766289
Ref: 1af75766289
Ref: tutorial/introduction an-informal-introduction-to-python5766289
Ref: 1af85766289
Ref: tutorial/introduction tut-informal5766289
Ref: 1af95766289
Node: 把 Python 當作計算機使用5767571
Ref: tutorial/introduction tut-calculator5767711
Ref: 1afa5767711
Ref: tutorial/introduction using-python-as-a-calculator5767711
Ref: 1afb5767711
Node: 數字 Number5768005
Ref: tutorial/introduction numbers5768102
Ref: 1afc5768102
Ref: tutorial/introduction tut-numbers5768102
Ref: 1afd5768102
Ref: 數字 Number-Footnote-15771028
Node: 文字5771244
Ref: tutorial/introduction text5771366
Ref: 1aff5771366
Ref: tutorial/introduction tut-strings5771366
Ref: 1b005771366
Ref: 文字-Footnote-15779426
Node: List（串列）5779683
Ref: tutorial/introduction lists5779783
Ref: 1b055779783
Ref: tutorial/introduction tut-lists5779783
Ref: 1b065779783
Node: 初探程式設計的前幾步5782997
Ref: tutorial/introduction first-steps-towards-programming5783137
Ref: 1b095783137
Ref: tutorial/introduction tut-firststeps5783137
Ref: 1b0a5783137
Ref: 初探程式設計的前幾步-Footnote-15786056
Node: 深入了解流程控制5786151
Ref: tutorial/controlflow doc5786287
Ref: 1b0c5786287
Ref: tutorial/controlflow more-control-flow-tools5786287
Ref: 1b0d5786287
Ref: tutorial/controlflow tut-morecontrol5786287
Ref: 1b0e5786287
Node: if 陳述式5786784
Ref: tutorial/controlflow if-statements5786879
Ref: 1b0f5786879
Ref: tutorial/controlflow tut-if5786879
Ref: 1b105786879
Node: for 陳述式5787893
Ref: tutorial/controlflow for-statements5788009
Ref: 1b135788009
Ref: tutorial/controlflow tut-for5788009
Ref: 1b145788009
Node: range 函式5789270
Ref: tutorial/controlflow the-range-function5789430
Ref: 1b155789430
Ref: tutorial/controlflow tut-range5789430
Ref: 1b165789430
Node: 迴圈內的 break 和 continue 陳述式及 else 子句5791491
Ref: tutorial/controlflow break-and-continue-statements-and-else-clauses-on-loops5791652
Ref: 1b195791652
Ref: tutorial/controlflow tut-break5791652
Ref: 1b1a5791652
Node: pass 陳述式5793936
Ref: tutorial/controlflow pass-statements5794100
Ref: 1b1c5794100
Ref: tutorial/controlflow tut-pass5794100
Ref: 1b1d5794100
Node: match 陳述式5794782
Ref: tutorial/controlflow match-statements5794911
Ref: 1b1f5794911
Ref: tutorial/controlflow tut-match5794911
Ref: 1b125794911
Ref: match 陳述式-Footnote-15801941
Node: 定義函式 function5801983
Ref: tutorial/controlflow defining-functions5802122
Ref: 1b205802122
Ref: tutorial/controlflow tut-functions5802122
Ref: 1b215802122
Ref: 定義函式 function-Footnote-15806987
Node: 深入了解函式定義5807238
Ref: tutorial/controlflow more-on-defining-functions5807402
Ref: 1b245807402
Ref: tutorial/controlflow tut-defining5807402
Ref: 1b255807402
Node: 預設引數值5807965
Ref: tutorial/controlflow default-argument-values5808065
Ref: 1b265808065
Ref: tutorial/controlflow tut-defaultargs5808065
Ref: 1b275808065
Node: 關鍵字引數5809875
Ref: tutorial/controlflow keyword-arguments5809996
Ref: 1b285809996
Ref: tutorial/controlflow tut-keywordargs5809996
Ref: 1b295809996
Node: 特殊參數5813556
Ref: tutorial/controlflow special-parameters5813705
Ref: 1b2b5813705
Node: 位置或關鍵字引數 Positional-or-Keyword Arguments5814962
Ref: tutorial/controlflow positional-or-keyword-arguments5815121
Ref: 1b2c5815121
Node: 僅限位置參數 Positional-Only Parameters5815355
Ref: tutorial/controlflow positional-only-parameters5815567
Ref: 1b2d5815567
Node: 僅限關鍵字引數 Keyword-Only Arguments5816144
Ref: tutorial/controlflow keyword-only-arguments5816312
Ref: 1b2e5816312
Node: 函式範例5816581
Ref: tutorial/controlflow function-examples5816710
Ref: 1b2f5816710
Node: 回顧5819600
Ref: tutorial/controlflow recap5819676
Ref: 1b305819676
Node: 任意引數列表 Arbitrary Argument Lists5820405
Ref: tutorial/controlflow arbitrary-argument-lists5820587
Ref: 1b315820587
Ref: tutorial/controlflow tut-arbitraryargs5820587
Ref: 1b325820587
Node: 拆解引數列表（Unpacking Argument Lists）5821623
Ref: tutorial/controlflow tut-unpacking-arguments5821809
Ref: 1b335821809
Ref: tutorial/controlflow unpacking-argument-lists5821809
Ref: 1b345821809
Node: Lambda 運算式5823060
Ref: tutorial/controlflow lambda-expressions5823243
Ref: 1b355823243
Ref: tutorial/controlflow tut-lambda5823243
Ref: 1b365823243
Node: 說明文件字串 Documentation Strings5824168
Ref: tutorial/controlflow documentation-strings5824336
Ref: 1b375824336
Ref: tutorial/controlflow tut-docstrings5824336
Ref: 1b225824336
Node: 函式註釋 Function Annotations5826041
Ref: tutorial/controlflow function-annotations5826184
Ref: 1b385826184
Ref: tutorial/controlflow tut-annotations5826184
Ref: 1b395826184
Ref: 函式註釋 Function Annotations-Footnote-15827347
Ref: 函式註釋 Function Annotations-Footnote-25827389
Node: 間奏曲：程式碼風格 Coding Style5827431
Ref: tutorial/controlflow intermezzo-coding-style5827565
Ref: 1b3c5827565
Ref: tutorial/controlflow tut-codingstyle5827565
Ref: 1b3d5827565
Ref: 間奏曲：程式碼風格 Coding Style-Footnote-15829642
Node: 資料結構5829684
Ref: tutorial/datastructures doc5829801
Ref: 1b3f5829801
Ref: tutorial/datastructures data-structures5829801
Ref: 1b405829801
Ref: tutorial/datastructures tut-structures5829801
Ref: 1b185829801
Node: 進一步了解 List（串列）5830271
Ref: tutorial/datastructures more-on-lists5830374
Ref: 1b415830374
Ref: tutorial/datastructures tut-morelists5830374
Ref: 1b425830374
Ref: 進一步了解 List（串列）-Footnote-15834105
Node: 將 List 作為 Stack（堆疊）使用5834243
Ref: tutorial/datastructures tut-lists-as-stacks5834399
Ref: 1b435834399
Ref: tutorial/datastructures using-lists-as-stacks5834399
Ref: 1b445834399
Node: 將 List 作為 Queue（佇列）使用5835124
Ref: tutorial/datastructures tut-lists-as-queues5835332
Ref: 1b455835332
Ref: tutorial/datastructures using-lists-as-queues5835332
Ref: 1b465835332
Node: List Comprehensions（串列綜合運算）5836470
Ref: tutorial/datastructures list-comprehensions5836668
Ref: 1b475836668
Ref: tutorial/datastructures tut-listcomps5836668
Ref: 1b485836668
Node: 巢狀的 List Comprehensions5839989
Ref: tutorial/datastructures nested-list-comprehensions5840139
Ref: 1b495840139
Node: del 陳述式5841843
Ref: tutorial/datastructures the-del-statement5841981
Ref: 1b4a5841981
Ref: tutorial/datastructures tut-del5841981
Ref: 1b4b5841981
Node: Tuples 和序列 Sequences5842818
Ref: tutorial/datastructures tuples-and-sequences5842935
Ref: 1b4c5842935
Ref: tutorial/datastructures tut-tuples5842935
Ref: 1b2a5842935
Node: 集合 Sets5845971
Ref: tutorial/datastructures sets5846097
Ref: 1b4e5846097
Ref: tutorial/datastructures tut-sets5846097
Ref: 1b4f5846097
Node: 字典（Dictionary）5847846
Ref: tutorial/datastructures dictionaries5847958
Ref: 1b505847958
Ref: tutorial/datastructures tut-dictionaries5847958
Ref: 1b515847958
Node: 迴圈技巧5850770
Ref: tutorial/datastructures looping-techniques5850899
Ref: 1b525850899
Ref: tutorial/datastructures tut-loopidioms5850899
Ref: 1b175850899
Node: 深入了解條件 Condition5853378
Ref: tutorial/datastructures more-on-conditions5853521
Ref: 1b535853521
Ref: tutorial/datastructures tut-conditions5853521
Ref: 1b545853521
Node: 序列和其他資料類型之比較5855501
Ref: tutorial/datastructures comparing-sequences-and-other-types5855623
Ref: 1b565855623
Ref: tutorial/datastructures tut-comparing5855623
Ref: 1b575855623
Node: 模組 Module5857070
Ref: tutorial/modules doc5857178
Ref: 1b585857178
Ref: tutorial/modules modules5857178
Ref: 1b595857178
Ref: tutorial/modules tut-modules5857178
Ref: 1b5a5857178
Node: 深入了解模組5859696
Ref: tutorial/modules more-on-modules5859785
Ref: 1b5d5859785
Ref: tutorial/modules tut-moremodules5859785
Ref: 1b5e5859785
Ref: 深入了解模組-Footnote-15863018
Node: 把模組當作腳本執行5863190
Ref: tutorial/modules executing-modules-as-scripts5863302
Ref: 1b5f5863302
Ref: tutorial/modules tut-modulesasscripts5863302
Ref: 1b605863302
Node: 模組的搜尋路徑5864194
Ref: tutorial/modules the-module-search-path5864340
Ref: 1b615864340
Ref: tutorial/modules tut-searchpath5864340
Ref: 1b625864340
Node: 「編譯」Python 檔案5865866
Ref: tutorial/modules compiled-python-files5865976
Ref: 1b665865976
Ref: tutorial/modules tut-pycache5865976
Ref: 6805865976
Ref: 「編譯」Python 檔案-Footnote-15867997
Node: 標準模組5868039
Ref: tutorial/modules standard-modules5868147
Ref: 1b675868147
Ref: tutorial/modules tut-standardmodules5868147
Ref: 1b655868147
Node: dir 函式5869448
Ref: tutorial/modules the-dir-function5869552
Ref: 1b685869552
Ref: tutorial/modules tut-dir5869552
Ref: 1b695869552
Node: 套件 Package5874023
Ref: tutorial/modules packages5874106
Ref: 1b6a5874106
Ref: tutorial/modules tut-packages5874106
Ref: 1b6b5874106
Node: 從套件中 import *5878190
Ref: tutorial/modules importing-from-a-package5878286
Ref: 1b6d5878286
Ref: tutorial/modules tut-pkg-import-star5878286
Ref: 1b6e5878286
Node: 套件內引用5881553
Ref: tutorial/modules id25881679
Ref: 1b6f5881679
Ref: tutorial/modules intra-package-references5881679
Ref: 1b705881679
Node: 多目錄中的套件5882649
Ref: tutorial/modules packages-in-multiple-directories5882745
Ref: 1b715882745
Node: 輸入和輸出5883231
Ref: tutorial/inputoutput doc5883342
Ref: 1b735883342
Ref: tutorial/inputoutput input-and-output5883342
Ref: 1b745883342
Ref: tutorial/inputoutput tut-io5883342
Ref: 1b755883342
Node: 更華麗的輸出格式5883611
Ref: tutorial/inputoutput fancier-output-formatting5883708
Ref: 1b765883708
Ref: tutorial/inputoutput tut-formatting5883708
Ref: 1b775883708
Node: 格式化的字串文本 Formatted String Literals5887659
Ref: tutorial/inputoutput formatted-string-literals5887802
Ref: 1b7a5887802
Ref: tutorial/inputoutput tut-f-strings5887802
Ref: 1b795887802
Node: 字串的 format method5889810
Ref: tutorial/inputoutput the-string-format-method5889983
Ref: 1b7b5889983
Ref: tutorial/inputoutput tut-string-format5889983
Ref: 1b7c5889983
Node: 手動格式化字串5892758
Ref: tutorial/inputoutput manual-string-formatting5892908
Ref: 1b7d5892908
Node: 格式化字串的舊方法5894374
Ref: tutorial/inputoutput old-string-formatting5894492
Ref: 1b815894492
Node: 讀寫檔案5895051
Ref: tutorial/inputoutput reading-and-writing-files5895148
Ref: 1b825895148
Ref: tutorial/inputoutput tut-files5895148
Ref: 1b835895148
Node: 檔案物件的 method5898271
Ref: tutorial/inputoutput methods-of-file-objects5898384
Ref: 1b845898384
Ref: tutorial/inputoutput tut-filemethods5898384
Ref: 1b855898384
Node: 使用 json 儲存結構化資料5901991
Ref: tutorial/inputoutput saving-structured-data-with-json5902104
Ref: 1b875902104
Ref: tutorial/inputoutput tut-json5902104
Ref: 1b885902104
Ref: 使用 json 儲存結構化資料-Footnote-15904941
Node: 錯誤和例外5904966
Ref: tutorial/errors doc5905081
Ref: 1b8c5905081
Ref: tutorial/errors errors-and-exceptions5905081
Ref: 1b8d5905081
Ref: tutorial/errors tut-errors5905081
Ref: 1b8e5905081
Node: 語法錯誤 Syntax Error5905714
Ref: tutorial/errors syntax-errors5905816
Ref: 1b8f5905816
Ref: tutorial/errors tut-syntaxerrors5905816
Ref: 1b905905816
Node: 例外 Exception5906603
Ref: tutorial/errors exceptions5906726
Ref: 1b915906726
Ref: tutorial/errors tut-exceptions5906726
Ref: 1b925906726
Node: 處理例外5908561
Ref: tutorial/errors handling-exceptions5908671
Ref: 1b935908671
Ref: tutorial/errors tut-handling5908671
Ref: 1b1b5908671
Node: 引發例外5914938
Ref: tutorial/errors raising-exceptions5915063
Ref: 1b945915063
Ref: tutorial/errors tut-raising5915063
Ref: 1b955915063
Node: 例外鏈接 Exception Chaining5916204
Ref: tutorial/errors exception-chaining5916341
Ref: 1b965916341
Ref: tutorial/errors tut-exception-chaining5916341
Ref: 1b975916341
Node: 使用者自定的例外5918320
Ref: tutorial/errors tut-userexceptions5918463
Ref: 1b985918463
Ref: tutorial/errors user-defined-exceptions5918463
Ref: 1b995918463
Node: 定義清理動作5919157
Ref: tutorial/errors defining-clean-up-actions5919293
Ref: 1b9a5919293
Ref: tutorial/errors tut-cleanup5919293
Ref: 1b9b5919293
Node: 預定義的清理動作5922361
Ref: tutorial/errors predefined-clean-up-actions5922509
Ref: 1b9c5922509
Ref: tutorial/errors tut-cleanup-with5922509
Ref: 1b9d5922509
Node: 引發及處理多個無關的例外5923477
Ref: tutorial/errors raising-and-handling-multiple-unrelated-exceptions5923634
Ref: 1b9e5923634
Ref: tutorial/errors tut-exception-groups5923634
Ref: 1b9f5923634
Node: 用註解使例外更詳細5926915
Ref: tutorial/errors enriching-exceptions-with-notes5927039
Ref: 1ba05927039
Ref: tutorial/errors tut-exception-notes5927039
Ref: 1ba15927039
Node: Class（類別）5929531
Ref: tutorial/classes doc5929659
Ref: 1ba25929659
Ref: tutorial/classes classes5929659
Ref: 1ba35929659
Ref: tutorial/classes tut-classes5929659
Ref: 1b235929659
Node: 關於名稱與物件的一段話5932210
Ref: tutorial/classes a-word-about-names-and-objects5932354
Ref: 1ba55932354
Ref: tutorial/classes tut-object5932354
Ref: 1ba65932354
Node: Python 作用域 Scope 及命名空間 Namespace5933296
Ref: tutorial/classes python-scopes-and-namespaces5933461
Ref: 1ba75933461
Ref: tutorial/classes tut-scopes5933461
Ref: 1b5c5933461
Ref: Python 作用域 Scope 及命名空間 Namespace-Footnote-15939611
Node: 作用域和命名空間的範例5939987
Ref: tutorial/classes scopes-and-namespaces-example5940105
Ref: 1ba95940105
Ref: tutorial/classes tut-scopeexample5940105
Ref: 1baa5940105
Node: 初見 class5941413
Ref: tutorial/classes a-first-look-at-classes5941560
Ref: 1bab5941560
Ref: tutorial/classes tut-firstclasses5941560
Ref: 1b3e5941560
Node: Class definition（類別定義）語法5941819
Ref: tutorial/classes class-definition-syntax5941929
Ref: 1bac5941929
Ref: tutorial/classes tut-classdefinition5941929
Ref: 1bad5941929
Node: Class 物件5943422
Ref: tutorial/classes class-objects5943553
Ref: 1bae5943553
Ref: tutorial/classes tut-classobjects5943553
Ref: 1baf5943553
Node: 實例物件5945684
Ref: tutorial/classes instance-objects5945788
Ref: 1bb05945788
Ref: tutorial/classes tut-instanceobjects5945788
Ref: 1bb15945788
Node: Method 物件5947039
Ref: tutorial/classes method-objects5947152
Ref: 1bb25947152
Ref: tutorial/classes tut-methodobjects5947152
Ref: 1bb35947152
Node: Class 及實例變數5948856
Ref: tutorial/classes class-and-instance-variables5948948
Ref: 1bb45948948
Ref: tutorial/classes tut-class-and-instance-variables5948948
Ref: 1bb55948948
Node: 隨意的備註5950922
Ref: tutorial/classes random-remarks5951039
Ref: 1bb65951039
Ref: tutorial/classes tut-remarks5951039
Ref: 1bb75951039
Node: 繼承 Inheritance5954673
Ref: tutorial/classes inheritance5954790
Ref: 1bb85954790
Ref: tutorial/classes tut-inheritance5954790
Ref: 1bb95954790
Node: 多重繼承5957630
Ref: tutorial/classes multiple-inheritance5957697
Ref: 1bba5957697
Ref: tutorial/classes tut-multiple5957697
Ref: 1bbb5957697
Node: 私有變數5959655
Ref: tutorial/classes private-variables5959769
Ref: 1bbc5959769
Ref: tutorial/classes tut-private5959769
Ref: 1ba45959769
Node: 補充說明5962496
Ref: tutorial/classes odds-and-ends5962610
Ref: 1bbe5962610
Ref: tutorial/classes tut-odds5962610
Ref: 1bbf5962610
Node: 疊代器 Iterator5963791
Ref: tutorial/classes iterators5963912
Ref: 1bc25963912
Ref: tutorial/classes tut-iterators5963912
Ref: 1bc35963912
Node: 產生器 Generator5966210
Ref: tutorial/classes generators5966337
Ref: 1bc55966337
Ref: tutorial/classes tut-generators5966337
Ref: 1bc65966337
Node: 產生器運算式5967737
Ref: tutorial/classes generator-expressions5967837
Ref: 1bc95967837
Ref: tutorial/classes tut-genexps5967837
Ref: 1bca5967837
Node: Python 標準函式庫概覽5968828
Ref: tutorial/stdlib doc5968987
Ref: 1bcb5968987
Ref: tutorial/stdlib brief-tour-of-the-standard-library5968987
Ref: 1bcc5968987
Ref: tutorial/stdlib tut-brieftour5968987
Ref: 1bcd5968987
Node: 作業系統介面5969374
Ref: tutorial/stdlib operating-system-interface5969502
Ref: 1bce5969502
Ref: tutorial/stdlib tut-os-interface5969502
Ref: 1bcf5969502
Node: 檔案之萬用字元 File Wildcards5970657
Ref: tutorial/stdlib file-wildcards5970809
Ref: 1bd05970809
Ref: tutorial/stdlib tut-file-wildcards5970809
Ref: 1bd15970809
Node: 命令列引數5971090
Ref: tutorial/stdlib command-line-arguments5971263
Ref: 1bd25971263
Ref: tutorial/stdlib tut-command-line-arguments5971263
Ref: 1bd35971263
Node: 錯誤輸出重新導向與程式終止5972337
Ref: tutorial/stdlib error-output-redirection-and-program-termination5972492
Ref: 1bd45972492
Ref: tutorial/stdlib tut-stderr5972492
Ref: 1bd55972492
Node: 字串樣式比對5972934
Ref: tutorial/stdlib string-pattern-matching5973086
Ref: 1bd65973086
Ref: tutorial/stdlib tut-string-pattern-matching5973086
Ref: 1bd75973086
Node: 數學相關5973725
Ref: tutorial/stdlib mathematics5973850
Ref: 1bd85973850
Ref: tutorial/stdlib tut-mathematics5973850
Ref: 1bd95973850
Node: 網路存取5974988
Ref: tutorial/stdlib internet-access5975110
Ref: 1bda5975110
Ref: tutorial/stdlib tut-internet-access5975110
Ref: 1bdb5975110
Node: 日期與時間5976150
Ref: tutorial/stdlib dates-and-times5976272
Ref: 1bdc5976272
Ref: tutorial/stdlib tut-dates-and-times5976272
Ref: 1bdd5976272
Node: 資料壓縮5977039
Ref: tutorial/stdlib data-compression5977161
Ref: 1bde5977161
Ref: tutorial/stdlib tut-data-compression5977161
Ref: 1bdf5977161
Node: 效能量測5977670
Ref: tutorial/stdlib performance-measurement5977789
Ref: 1be05977789
Ref: tutorial/stdlib tut-performance-measurement5977789
Ref: 1be15977789
Node: 品質控管5978552
Ref: tutorial/stdlib quality-control5978674
Ref: 1be25978674
Ref: tutorial/stdlib tut-quality-control5978674
Ref: 1be35978674
Node: 標準模組庫5980119
Ref: tutorial/stdlib batteries-included5980220
Ref: 1be45980220
Ref: tutorial/stdlib tut-batteries-included5980220
Ref: 1be55980220
Ref: 標準模組庫-Footnote-15981881
Node: Python 標準函式庫概覽——第二部份5981940
Ref: tutorial/stdlib2 doc5982103
Ref: 1be65982103
Ref: tutorial/stdlib2 brief-tour-of-the-standard-library-part-ii5982103
Ref: 1be75982103
Ref: tutorial/stdlib2 tut-brieftourtwo5982103
Ref: 1be85982103
Node: 輸出格式化 Output Formatting5982884
Ref: tutorial/stdlib2 output-formatting5983029
Ref: 1be95983029
Ref: tutorial/stdlib2 tut-output-formatting5983029
Ref: 1bea5983029
Node: 模板化 Templating5985143
Ref: tutorial/stdlib2 templating5985351
Ref: 1beb5985351
Ref: tutorial/stdlib2 tut-templating5985351
Ref: 1bec5985351
Node: 二進制資料記錄編排 Binary Data Record Layouts5987980
Ref: tutorial/stdlib2 tut-binary-formats5988183
Ref: 1bef5988183
Ref: tutorial/stdlib2 working-with-binary-data-record-layouts5988183
Ref: 1bf05988183
Node: 多執行緒 Multi-threading5989433
Ref: tutorial/stdlib2 multi-threading5989636
Ref: 1bf15989636
Ref: tutorial/stdlib2 tut-multi-threading5989636
Ref: 1bf25989636
Node: 日誌記錄 Logging5991607
Ref: tutorial/stdlib2 logging5991781
Ref: 1bf35991781
Ref: tutorial/stdlib2 tut-logging5991781
Ref: 1bf45991781
Node: 弱引用 Weak References5993077
Ref: tutorial/stdlib2 tut-weak-references5993247
Ref: 1bfa5993247
Ref: tutorial/stdlib2 weak-references5993247
Ref: 1bfb5993247
Node: 使用於 List 的工具5995062
Ref: tutorial/stdlib2 tools-for-working-with-lists5995270
Ref: 1bfc5995270
Ref: tutorial/stdlib2 tut-list-tools5995270
Ref: 1bfd5995270
Node: 十進制浮點數運算 Decimal Floating-Point Arithmetic5997787
Ref: tutorial/stdlib2 decimal-floating-point-arithmetic5997961
Ref: 1bfe5997961
Ref: tutorial/stdlib2 tut-decimal-fp5997961
Ref: 1bff5997961
Node: 虛擬環境與套件5999883
Ref: tutorial/venv doc6000051
Ref: 1c006000051
Ref: tutorial/venv tut-venv6000051
Ref: 1c016000051
Ref: tutorial/venv virtual-environments-and-packages6000051
Ref: 1c026000051
Node: 簡介<4>6000178
Ref: tutorial/venv introduction6000272
Ref: 1c036000272
Node: 建立虛擬環境6001453
Ref: tutorial/venv creating-virtual-environments6001576
Ref: 1c056001576
Node: 用 pip 管理套件6003518
Ref: tutorial/venv managing-packages-with-pip6003623
Ref: 1c066003623
Ref: 用 pip 管理套件-Footnote-16007439
Ref: 用 pip 管理套件-Footnote-26007464
Node: 現在可以來學習些什麼？6007542
Ref: tutorial/whatnow doc6007706
Ref: 1c076007706
Ref: tutorial/whatnow tut-whatnow6007706
Ref: 1c086007706
Ref: tutorial/whatnow what-now6007706
Ref: 1c096007706
Ref: 現在可以來學習些什麼？-Footnote-16010887
Node: 互動式輸入編輯和歷史記錄替換6011054
Ref: tutorial/interactive doc6011230
Ref: 1c0b6011230
Ref: tutorial/interactive interactive-input-editing-and-history-substitution6011230
Ref: 1c0c6011230
Ref: tutorial/interactive tut-interacting6011230
Ref: 1aee6011230
Ref: 互動式輸入編輯和歷史記錄替換-Footnote-16011892
Node: Tab 鍵自動完成 Tab Completion 和歷史記錄編輯 History Editing6011953
Ref: tutorial/interactive tab-completion-and-history-editing6012146
Ref: 1c0d6012146
Ref: tutorial/interactive tut-keybindings6012146
Ref: 1c0e6012146
Node: 互動式直譯器的替代方案6013161
Ref: tutorial/interactive alternatives-to-the-interactive-interpreter6013354
Ref: 1c0f6013354
Ref: tutorial/interactive tut-commentary6013354
Ref: 1c106013354
Ref: 互動式直譯器的替代方案-Footnote-16014247
Ref: 互動式直譯器的替代方案-Footnote-26014276
Node: 浮點數運算：問題與限制6014317
Ref: tutorial/floatingpoint doc6014466
Ref: 1c116014466
Ref: tutorial/floatingpoint floating-point-arithmetic-issues-and-limitations6014466
Ref: 1c126014466
Ref: tutorial/floatingpoint tut-fp-issues6014466
Ref: 1c136014466
Ref: 浮點數運算：問題與限制-Footnote-16023720
Ref: 浮點數運算：問題與限制-Footnote-26023798
Node: 表示法誤差 Representation Error6023849
Ref: tutorial/floatingpoint representation-error6023955
Ref: 1c166023955
Ref: tutorial/floatingpoint tut-fp-error6023955
Ref: 1c176023955
Node: 附錄6027232
Ref: tutorial/appendix doc6027330
Ref: 1c186027330
Ref: tutorial/appendix appendix6027330
Ref: 1c196027330
Ref: tutorial/appendix tut-appendix6027330
Ref: 1c1a6027330
Node: 互動模式<2>6027396
Ref: tutorial/appendix interactive-mode6027454
Ref: 1c1b6027454
Ref: tutorial/appendix tut-interac6027454
Ref: 1536027454
Node: 錯誤處理6028655
Ref: tutorial/appendix error-handling6028754
Ref: 1c1c6028754
Ref: tutorial/appendix tut-error6028754
Ref: 1c1d6028754
Ref: 錯誤處理-Footnote-16029729
Node: 可執行的 Python 腳本6029799
Ref: tutorial/appendix executable-python-scripts6029928
Ref: 1c1e6029928
Ref: tutorial/appendix tut-scripts6029928
Ref: 1af66029928
Node: 互動式啟動檔案6030902
Ref: tutorial/appendix the-interactive-startup-file6031034
Ref: 1c1f6031034
Ref: tutorial/appendix tut-startup6031034
Ref: 1c206031034
Node: 客製化模組6032372
Ref: tutorial/appendix the-customization-modules6032469
Ref: 1c216032469
Ref: tutorial/appendix tut-customize6032469
Ref: 1c226032469
Node: Python 的設置與使用6033318
Ref: using/index doc6033439
Ref: 1c236033439
Ref: using/index python-setup-and-usage6033439
Ref: 1c246033439
Ref: using/index using-index6033439
Ref: 1c256033439
Node: 命令列與環境6033850
Ref: using/cmdline doc6033970
Ref: 1c266033970
Ref: using/cmdline command-line-and-environment6033970
Ref: 1c276033970
Ref: using/cmdline using-on-general6033970
Ref: 18c46033970
Node: 命令列6034292
Ref: using/cmdline command-line6034377
Ref: 1c296034377
Ref: using/cmdline using-on-cmdline6034377
Ref: fa86034377
Node: 介面選項6034778
Ref: using/cmdline interface-options6034860
Ref: 1c2a6034860
Ref: using/cmdline using-on-interface-options6034860
Ref: 1c2b6034860
Ref: using/cmdline cmdoption-c6036290
Ref: 5846036290
Ref: using/cmdline cmdoption-m6036863
Ref: 5856036863
Ref: using/cmdline cmdarg-dash6039250
Ref: 1c2c6039250
Ref: using/cmdline cmdarg-script6039667
Ref: 1c2d6039667
Ref: 介面選項-Footnote-16041507
Node: Generic options6041549
Ref: using/cmdline generic-options6041661
Ref: 1c2e6041661
Ref: using/cmdline using-on-generic-options6041661
Ref: 1c2f6041661
Ref: using/cmdline cmdoption-06041710
Ref: 13956041710
Ref: using/cmdline cmdoption-h6041725
Ref: 1c306041725
Ref: using/cmdline cmdoption-help6041740
Ref: 5946041740
Ref: using/cmdline cmdoption-help-env6041875
Ref: 5966041875
Ref: using/cmdline cmdoption-help-xoptions6042016
Ref: 5976042016
Ref: using/cmdline cmdoption-help-all6042165
Ref: 5986042165
Ref: using/cmdline cmdoption-V6042261
Ref: 15b6042261
Ref: using/cmdline cmdoption-version6042276
Ref: cc26042276
Node: Miscellaneous options6042613
Ref: using/cmdline miscellaneous-options6042730
Ref: 1c316042730
Ref: using/cmdline using-on-misc-options6042730
Ref: fa96042730
Ref: using/cmdline cmdoption-b6042791
Ref: 5876042791
Ref: using/cmdline cmdoption-B6043205
Ref: 133b6043205
Ref: using/cmdline cmdoption-check-hash-based-pycs6043365
Ref: 1c326043365
Ref: using/cmdline cmdoption-d6044059
Ref: 1c336044059
Ref: using/cmdline cmdoption-E6044290
Ref: 9016044290
Ref: using/cmdline cmdoption-i6044514
Ref: 144a6044514
Ref: using/cmdline cmdoption-I6044964
Ref: 9026044964
Ref: using/cmdline cmdoption-O6045412
Ref: d5b6045412
Ref: using/cmdline cmdoption-OO6045792
Ref: d5c6045792
Ref: using/cmdline cmdoption-P6046089
Ref: 5486046089
Ref: using/cmdline cmdoption-q6046750
Ref: 1c366046750
Ref: using/cmdline cmdoption-R6046880
Ref: 199d6046880
Ref: using/cmdline cmdoption-s6047930
Ref: 13196047930
Ref: using/cmdline cmdoption-S6048169
Ref: 11406048169
Ref: using/cmdline cmdoption-u6048486
Ref: 18a86048486
Ref: using/cmdline cmdoption-v6048767
Ref: 13926048767
Ref: using/cmdline using-on-warnings6049277
Ref: 1c3a6049277
Ref: using/cmdline cmdoption-W6049277
Ref: 86c6049277
Ref: using/cmdline cmdoption-x6051784
Ref: 1c3c6051784
Ref: using/cmdline cmdoption-X6051941
Ref: 15a6051941
Ref: Miscellaneous options-Footnote-16058506
Ref: Miscellaneous options-Footnote-26058548
Ref: Miscellaneous options-Footnote-36058590
Ref: Miscellaneous options-Footnote-46058632
Ref: Miscellaneous options-Footnote-56058674
Node: Controlling color6058716
Ref: using/cmdline controlling-color6058842
Ref: 1c426058842
Ref: using/cmdline using-on-controlling-color6058842
Ref: 14f6058842
Ref: Controlling color-Footnote-16059900
Ref: Controlling color-Footnote-26059933
Node: 你不該使用的選項6059963
Ref: using/cmdline no-color6060059
Ref: 1c436060059
Ref: using/cmdline options-you-shouldn-t-use6060059
Ref: 1c446060059
Ref: using/cmdline cmdoption-J6060118
Ref: 133a6060118
Ref: 你不該使用的選項-Footnote-16060207
Node: 環境變數6060239
Ref: using/cmdline environment-variables6060324
Ref: 1c456060324
Ref: using/cmdline using-on-envvars6060324
Ref: 5956060324
Ref: using/cmdline envvar-PYTHONHOME6060593
Ref: 3876060593
Ref: using/cmdline envvar-PYTHONPATH6061191
Ref: fbe6061191
Ref: using/cmdline envvar-PYTHONSAFEPATH6062239
Ref: 5496062239
Ref: using/cmdline envvar-PYTHONPLATLIBDIR6062464
Ref: 18426062464
Ref: using/cmdline envvar-PYTHONSTARTUP6062628
Ref: f6b6062628
Ref: using/cmdline envvar-PYTHONOPTIMIZE6063302
Ref: 1c356063302
Ref: using/cmdline envvar-PYTHONBREAKPOINT6063532
Ref: a7e6063532
Ref: using/cmdline envvar-PYTHONDEBUG6064141
Ref: 1c346064141
Ref: using/cmdline envvar-PYTHONINSPECT6064476
Ref: 14496064476
Ref: using/cmdline envvar-PYTHONUNBUFFERED6065080
Ref: 18a96065080
Ref: using/cmdline envvar-PYTHONVERBOSE6065223
Ref: 1c396065223
Ref: using/cmdline envvar-PYTHONCASEOK6065454
Ref: 9006065454
Ref: using/cmdline envvar-PYTHONDONTWRITEBYTECODE6065606
Ref: 133c6065606
Ref: using/cmdline envvar-PYTHONPYCACHEPREFIX6065841
Ref: 9476065841
Ref: using/cmdline envvar-PYTHONHASHSEED6066176
Ref: 101e6066176
Ref: using/cmdline envvar-PYTHONINTMAXSTRDIGITS6066854
Ref: 16c06066854
Ref: using/cmdline envvar-PYTHONIOENCODING6067084
Ref: fab6067084
Ref: using/cmdline envvar-PYTHONNOUSERSITE6067895
Ref: 131a6067895
Ref: using/cmdline envvar-PYTHONUSERBASE6068125
Ref: 13186068125
Ref: using/cmdline envvar-PYTHONEXECUTABLE6068464
Ref: 1c4a6068464
Ref: using/cmdline envvar-PYTHONWARNINGS6068666
Ref: b516068666
Ref: using/cmdline envvar-PYTHONFAULTHANDLER6069646
Ref: 10216069646
Ref: using/cmdline envvar-PYTHONTRACEMALLOC6070089
Ref: 1c3e6070089
Ref: using/cmdline envvar-PYTHONPROFILEIMPORTTIME6070651
Ref: a986070651
Ref: using/cmdline envvar-PYTHONASYNCIODEBUG6070917
Ref: 1c506070917
Ref: using/cmdline envvar-PYTHONMALLOC6071121
Ref: c0b6071121
Ref: using/cmdline envvar-PYTHONMALLOCSTATS6072571
Ref: 1a5c6072571
Ref: using/cmdline envvar-PYTHONLEGACYWINDOWSFSENCODING6073176
Ref: 28f6073176
Ref: using/cmdline envvar-PYTHONLEGACYWINDOWSSTDIO6073686
Ref: c026073686
Ref: using/cmdline envvar-PYTHONCOERCECLOCALE6074148
Ref: a786074148
Ref: using/cmdline envvar-PYTHONDEVMODE6076864
Ref: a906076864
Ref: using/cmdline envvar-PYTHONUTF86077203
Ref: a7b6077203
Ref: using/cmdline envvar-PYTHONWARNDEFAULTENCODING6077502
Ref: 7606077502
Ref: using/cmdline envvar-PYTHONNODEBUGRANGES6077805
Ref: 55a6077805
Ref: using/cmdline envvar-PYTHONPERFSUPPORT6078266
Ref: 4156078266
Ref: using/cmdline envvar-PYTHON_PERF_JIT_SUPPORT6078668
Ref: 1766078668
Ref: using/cmdline envvar-PYTHON_CPU_COUNT6079109
Ref: 1f56079109
Ref: using/cmdline envvar-PYTHON_FROZEN_MODULES6079402
Ref: 1746079402
Ref: using/cmdline envvar-PYTHON_COLORS6080039
Ref: 1306080039
Ref: using/cmdline envvar-PYTHON_BASIC_REPL6080298
Ref: 1526080298
Ref: using/cmdline envvar-PYTHON_HISTORY6080619
Ref: 1776080619
Ref: using/cmdline envvar-PYTHON_GIL6080860
Ref: 1596080860
Ref: 環境變數-Footnote-16081359
Ref: 環境變數-Footnote-26081401
Ref: 環境變數-Footnote-36081443
Ref: 環境變數-Footnote-46081485
Node: 除錯模式變數6081527
Ref: using/cmdline debug-mode-variables6081594
Ref: 1c586081594
Ref: using/cmdline envvar-PYTHONDUMPREFS6081643
Ref: 94a6081643
Ref: using/cmdline envvar-PYTHONDUMPREFSFILE6081878
Ref: 17956081878
Ref: using/cmdline envvar-PYTHON_PRESITE6082226
Ref: 1c406082226
Node: 在 Unix 平臺上使用 Python6082963
Ref: using/unix doc6083105
Ref: 1c596083105
Ref: using/unix using-on-unix6083105
Ref: 1c5a6083105
Ref: using/unix using-python-on-unix-platforms6083105
Ref: 1c5b6083105
Node: 獲得並安裝 Python 的最新版本6083326
Ref: using/unix getting-and-installing-the-latest-version-of-python6083454
Ref: 1c5c6083454
Node: 在 Linux 上6083595
Ref: using/unix on-linux6083719
Ref: 1c5d6083719
Node: 在 FreeBSD 和 OpenBSD 上6084629
Ref: using/unix on-freebsd-and-openbsd6084753
Ref: 1c5e6084753
Node: 建置 Python6085275
Ref: using/unix building-python6085447
Ref: 1c5f6085447
Ref: using/unix building-python-on-unix6085447
Ref: e976085447
Ref: 建置 Python-Footnote-16086263
Ref: 建置 Python-Footnote-26086312
Ref: 建置 Python-Footnote-36086379
Node: 與 Python 相關的路徑和檔案6086442
Ref: using/unix python-related-paths-and-files6086585
Ref: 1c616086585
Node: 雜項<2>6087795
Ref: using/unix miscellaneous6087942
Ref: 1c646087942
Node: 客製化 OpenSSL6088485
Ref: using/unix custom-openssl6088588
Ref: 1c656088588
Ref: using/unix unix-custom-openssl6088588
Ref: 1c666088588
Node: 配置 Python6090272
Ref: using/configure doc6090424
Ref: 1c676090424
Ref: using/configure configure-python6090424
Ref: 1c686090424
Node: 建置需求6090577
Ref: using/configure build-requirements6090663
Ref: 1c696090663
Ref: 建置需求-Footnote-16092299
Ref: 建置需求-Footnote-26092342
Ref: 建置需求-Footnote-36092425
Ref: 建置需求-Footnote-46092472
Ref: 建置需求-Footnote-56092529
Ref: 建置需求-Footnote-66092571
Node: 產生的檔案6092613
Ref: using/configure generated-files6092720
Ref: 1c6a6092720
Node: 設定腳本6093176
Ref: using/configure configure-script6093240
Ref: 1c6b6093240
Node: 設定選項6093766
Ref: using/configure configure-options6093880
Ref: 1c606093880
Ref: using/configure id16093880
Ref: 1c6c6093880
Node: 一般選項6094414
Ref: using/configure general-options6094502
Ref: 1c6d6094502
Ref: using/configure cmdoption-enable-loadable-sqlite-extensions6094541
Ref: 1c6e6094541
Ref: using/configure cmdoption-disable-ipv66094857
Ref: 1c6f6094857
Ref: using/configure cmdoption-enable-big-digits6094994
Ref: 6f16094994
Ref: using/configure cmdoption-with-suffix6095288
Ref: 1c706095288
Ref: using/configure cmdoption-with-tzpath6095789
Ref: 1c716095789
Ref: using/configure cmdoption-without-decimal-contextvar6096233
Ref: 1c746096233
Ref: using/configure cmdoption-with-dbmliborder6096566
Ref: 1c766096566
Ref: using/configure cmdoption-without-c-locale-coercion6096849
Ref: 1c776096849
Ref: using/configure cmdoption-without-freelists6097090
Ref: 6f06097090
Ref: using/configure cmdoption-with-platlibdir6097214
Ref: 1c786097214
Ref: using/configure cmdoption-with-wheel-pkg-dir6097454
Ref: 8316097454
Ref: using/configure cmdoption-with-pkg-config6097875
Ref: 1c796097875
Ref: using/configure cmdoption-enable-pystats6098232
Ref: 16be6098232
Ref: using/configure free-threading-build6100551
Ref: 1c7a6100551
Ref: using/configure cmdoption-disable-gil6100551
Ref: 1586100551
Ref: using/configure cmdoption-arg-PKG_CONFIG6100904
Ref: 1c7b6100904
Ref: using/configure cmdoption-arg-PKG_CONFIG_LIBDIR6100968
Ref: 1c7c6100968
Ref: using/configure cmdoption-arg-PKG_CONFIG_PATH6100999
Ref: 1c7d6100999
Ref: 一般選項-Footnote-16101096
Node: C compiler options6101138
Ref: using/configure c-compiler-options6101249
Ref: 1c7e6101249
Ref: using/configure cmdoption-arg-CC6101304
Ref: 1c7f6101304
Ref: using/configure cmdoption-arg-CFLAGS6101347
Ref: 1c806101347
Ref: using/configure cmdoption-arg-CPP6101394
Ref: 1c816101394
Ref: using/configure cmdoption-arg-CPPFLAGS6101441
Ref: 1c826101441
Node: Linker options6101518
Ref: using/configure linker-options6101653
Ref: 1c836101653
Ref: using/configure cmdoption-arg-LDFLAGS6101700
Ref: 1c846101700
Ref: using/configure cmdoption-arg-LIBS6101774
Ref: 1c856101774
Ref: using/configure cmdoption-arg-MACHDEP6101854
Ref: 1c866101854
Node: Options for third-party dependencies6101923
Ref: using/configure options-for-third-party-dependencies6102058
Ref: 1c876102058
Ref: using/configure cmdoption-arg-BZIP2_CFLAGS6102173
Ref: 1c886102173
Ref: using/configure cmdoption-arg-BZIP2_LIBS6102199
Ref: 1c896102199
Ref: using/configure cmdoption-arg-CURSES_CFLAGS6102353
Ref: 1c8a6102353
Ref: using/configure cmdoption-arg-CURSES_LIBS6102380
Ref: 1c8b6102380
Ref: using/configure cmdoption-arg-GDBM_CFLAGS6102550
Ref: 1c8c6102550
Ref: using/configure cmdoption-arg-GDBM_LIBS6102575
Ref: 1c8d6102575
Ref: using/configure cmdoption-arg-LIBB2_CFLAGS6102648
Ref: 1c8e6102648
Ref: using/configure cmdoption-arg-LIBB2_LIBS6102674
Ref: 1c8f6102674
Ref: using/configure cmdoption-arg-LIBEDIT_CFLAGS6102840
Ref: 1c916102840
Ref: using/configure cmdoption-arg-LIBEDIT_LIBS6102868
Ref: 1c926102868
Ref: using/configure cmdoption-arg-LIBFFI_CFLAGS6103017
Ref: 1c936103017
Ref: using/configure cmdoption-arg-LIBFFI_LIBS6103044
Ref: 1c946103044
Ref: using/configure cmdoption-arg-LIBMPDEC_CFLAGS6103189
Ref: 1c956103189
Ref: using/configure cmdoption-arg-LIBMPDEC_LIBS6103218
Ref: 1c966103218
Ref: using/configure cmdoption-arg-LIBLZMA_CFLAGS6103495
Ref: 1c976103495
Ref: using/configure cmdoption-arg-LIBLZMA_LIBS6103523
Ref: 1c986103523
Ref: using/configure cmdoption-arg-LIBREADLINE_CFLAGS6103668
Ref: 1c996103668
Ref: using/configure cmdoption-arg-LIBREADLINE_LIBS6103700
Ref: 1c9a6103700
Ref: using/configure cmdoption-arg-LIBSQLITE3_CFLAGS6103857
Ref: 1c9b6103857
Ref: using/configure cmdoption-arg-LIBSQLITE3_LIBS6103888
Ref: 1c9c6103888
Ref: using/configure cmdoption-arg-LIBUUID_CFLAGS6104042
Ref: 1c9d6104042
Ref: using/configure cmdoption-arg-LIBUUID_LIBS6104070
Ref: 1c9e6104070
Ref: using/configure cmdoption-arg-PANEL_CFLAGS6104215
Ref: 1c9f6104215
Ref: using/configure cmdoption-arg-PANEL_LIBS6104241
Ref: 1ca06104241
Ref: using/configure cmdoption-arg-TCLTK_CFLAGS6104486
Ref: 1ca16104486
Ref: using/configure cmdoption-arg-TCLTK_LIBS6104512
Ref: 1ca26104512
Ref: using/configure cmdoption-arg-ZLIB_CFLAGS6104610
Ref: 1ca36104610
Ref: using/configure cmdoption-arg-ZLIB_LIBS6104635
Ref: 1ca46104635
Node: WebAssembly 選項6104777
Ref: using/configure webassembly-options6104910
Ref: 1ca56104910
Ref: using/configure cmdoption-with-emscripten-target6104963
Ref: 1ca66104963
Ref: using/configure cmdoption-enable-wasm-dynamic-linking6105232
Ref: 17326105232
Ref: using/configure cmdoption-enable-wasm-pthreads6105507
Ref: 17056105507
Node: 安裝選項6105613
Ref: using/configure install-options6105729
Ref: 1ca76105729
Ref: using/configure cmdoption-prefix6105768
Ref: 1c626105768
Ref: using/configure cmdoption-exec-prefix6106085
Ref: 1c636106085
Ref: using/configure cmdoption-disable-test-modules6106288
Ref: 8306106288
Ref: using/configure cmdoption-with-ensurepip6106514
Ref: 1ca86106514
Node: Performance options6106913
Ref: using/configure performance-options6107029
Ref: 1ca96107029
Ref: using/configure cmdoption-enable-optimizations6107285
Ref: 8066107285
Ref: using/configure envvar-PROFILE_TASK6108292
Ref: 160d6108292
Ref: using/configure cmdoption-with-lto6108604
Ref: 6ef6108604
Ref: using/configure cmdoption-enable-bolt6109121
Ref: 1caa6109121
Ref: using/configure cmdoption-arg-BOLT_APPLY_FLAGS6110188
Ref: 1cab6110188
Ref: using/configure cmdoption-arg-BOLT_INSTRUMENT_FLAGS6110324
Ref: 1cac6110324
Ref: using/configure cmdoption-with-computed-gotos6110452
Ref: 1cad6110452
Ref: using/configure cmdoption-without-mimalloc6110584
Ref: 1cae6110584
Ref: using/configure cmdoption-without-pymalloc6110758
Ref: 1caf6110758
Ref: using/configure cmdoption-without-doc-strings6110952
Ref: 1cb06110952
Ref: using/configure cmdoption-enable-profiling6111248
Ref: 1cb16111248
Ref: using/configure cmdoption-with-strict-overflow6111356
Ref: 16646111356
Ref: Performance options-Footnote-16111547
Ref: Performance options-Footnote-26111607
Node: Python Debug Build6111655
Ref: using/configure debug-build6111772
Ref: 1de6111772
Ref: using/configure python-debug-build6111772
Ref: 1cb26111772
Node: Debug options6113962
Ref: using/configure debug-options6114077
Ref: 1cb36114077
Ref: using/configure cmdoption-with-pydebug6114122
Ref: 3d86114122
Ref: using/configure cmdoption-with-trace-refs6114256
Ref: 3176114256
Ref: using/configure cmdoption-with-assertions6114890
Ref: 3046114890
Ref: using/configure cmdoption-with-valgrind6115276
Ref: 1cb56115276
Ref: using/configure cmdoption-with-dtrace6115358
Ref: 1cb66115358
Ref: using/configure cmdoption-with-address-sanitizer6115534
Ref: 1cb76115534
Ref: using/configure cmdoption-with-memory-sanitizer6115686
Ref: 1cb86115686
Ref: using/configure cmdoption-with-undefined-behavior-sanitizer6115840
Ref: 1cb96115840
Ref: using/configure cmdoption-with-thread-sanitizer6116021
Ref: 1cba6116021
Node: Linker options<2>6116164
Ref: using/configure id26116276
Ref: 1cbb6116276
Ref: using/configure cmdoption-enable-shared6116325
Ref: 8076116325
Ref: using/configure cmdoption-without-static-libpython6116439
Ref: 8326116439
Node: 函式庫選項6116627
Ref: using/configure libraries-options6116742
Ref: 1cbc6116742
Ref: using/configure cmdoption-with-libs6116788
Ref: 1cbd6116788
Ref: using/configure cmdoption-with-system-expat6116881
Ref: 16b56116881
Ref: using/configure cmdoption-with-system-libmpdec6117012
Ref: 34d6117012
Ref: using/configure cmdoption-with-readline6117588
Ref: 1cbe6117588
Ref: using/configure cmdoption-without-readline6117834
Ref: 1cbf6117834
Ref: using/configure cmdoption-with-libm6118016
Ref: 1cc06118016
Ref: using/configure cmdoption-with-libc6118135
Ref: 1cc16118135
Ref: using/configure cmdoption-with-openssl6118251
Ref: 1cc26118251
Ref: using/configure cmdoption-with-openssl-rpath6118348
Ref: 8336118348
Node: Security Options6118686
Ref: using/configure security-options6118796
Ref: 1cc36118796
Ref: using/configure cmdoption-with-hash-algorithm6118849
Ref: 1cc46118849
Ref: using/configure cmdoption-with-builtin-hashlib-hashes6119173
Ref: 1cc56119173
Ref: using/configure cmdoption-with-ssl-default-suites6119483
Ref: 1cc66119483
Node: macOS 選項6119960
Ref: using/configure macos-options6120066
Ref: 1cc76120066
Ref: using/configure cmdoption-enable-universalsdk6120133
Ref: 90f6120133
Ref: using/configure cmdoption-06120168
Ref: 1cc86120168
Ref: using/configure cmdoption-enable-framework6120343
Ref: 1cc96120343
Ref: using/configure cmdoption-16120375
Ref: 1cca6120375
Ref: using/configure cmdoption-with-universal-archs6120571
Ref: 1ccb6120571
Ref: using/configure cmdoption-with-framework-name6120992
Ref: 1ccc6120992
Ref: using/configure cmdoption-with-app-store-compliance6121178
Ref: 14e66121178
Ref: using/configure cmdoption-26121219
Ref: 1ccd6121219
Ref: macOS 選項-Footnote-16121721
Node: iOS Options6121788
Ref: using/configure ios-options6121901
Ref: 1cce6121901
Ref: using/configure cmdoption-36121968
Ref: 1ccf6121968
Ref: using/configure cmdoption-46122137
Ref: 1cd06122137
Ref: iOS Options-Footnote-16122284
Node: Cross Compiling Options6122351
Ref: using/configure cross-compiling-options6122443
Ref: 1cd16122443
Ref: using/configure cmdoption-build6122790
Ref: 1cd26122790
Ref: using/configure cmdoption-host6122895
Ref: 1cd36122895
Ref: using/configure cmdoption-with-build-python6122991
Ref: 1cd46122991
Ref: using/configure cmdoption-arg-CONFIG_SITE6123128
Ref: 1cd56123128
Ref: using/configure cmdoption-arg-HOSTRUNNER6123413
Ref: 1cd66123413
Node: Python Build System6123748
Ref: using/configure python-build-system6123872
Ref: 1cd76123872
Node: Main files of the build system6124039
Ref: using/configure main-files-of-the-build-system6124152
Ref: 1cd86124152
Node: 主要建置步驟6124519
Ref: using/configure main-build-steps6124663
Ref: 1cd96124663
Node: 主要 Makefile 目標6125041
Ref: using/configure main-makefile-targets6125169
Ref: 1cda6125169
Node: make6125392
Ref: using/configure make6125477
Ref: 1cdb6125477
Node: make platform6126878
Ref: using/configure make-platform6126988
Ref: 1cdc6126988
Node: make profile-opt6127304
Ref: using/configure make-profile-opt6127420
Ref: 1cdd6127420
Node: make clean6127688
Ref: using/configure make-clean6127805
Ref: 1cde6127805
Node: make distclean6127865
Ref: using/configure make-distclean6127978
Ref: 1cdf6127978
Ref: make distclean-Footnote-16128223
Node: make install6128642
Ref: using/configure make-install6128754
Ref: 1ce06128754
Node: make test6128845
Ref: using/configure make-test6128960
Ref: 1ce16128960
Node: make buildbottest6129301
Ref: using/configure make-buildbottest6129418
Ref: 1ce26129418
Node: make regen-all6129616
Ref: using/configure make-regen-all6129715
Ref: 1ce36129715
Node: C 擴充模組6130016
Ref: using/configure c-extensions6130117
Ref: 1ce46130117
Node: Compiler and linker flags6131792
Ref: using/configure compiler-and-linker-flags6131895
Ref: 1ce56131895
Node: Preprocessor flags6132129
Ref: using/configure preprocessor-flags6132233
Ref: 1ce66132233
Ref: using/configure envvar-CONFIGURE_CPPFLAGS6132288
Ref: 1ce76132288
Ref: using/configure envvar-CPPFLAGS6132445
Ref: 14246132445
Ref: using/configure envvar-BASECPPFLAGS6132812
Ref: 1ce86132812
Ref: using/configure envvar-PY_CPPFLAGS6132872
Ref: 1ce96132872
Node: 編譯器旗標6133117
Ref: using/configure compiler-flags6133242
Ref: 1cea6133242
Ref: using/configure envvar-CC6133286
Ref: 14216133286
Ref: using/configure envvar-CXX6133370
Ref: 1ceb6133370
Ref: using/configure envvar-CFLAGS6133459
Ref: 14226133459
Ref: using/configure envvar-CFLAGS_NODIST6133512
Ref: 1cec6133512
Ref: using/configure envvar-COMPILEALL_OPTS6134310
Ref: 1ced6134310
Ref: using/configure envvar-EXTRA_CFLAGS6134510
Ref: 1cee6134510
Ref: using/configure envvar-CONFIGURE_CFLAGS6134579
Ref: 1cef6134579
Ref: using/configure envvar-CONFIGURE_CFLAGS_NODIST6134732
Ref: 1cf06134732
Ref: using/configure envvar-BASECFLAGS6134899
Ref: 1cf16134899
Ref: using/configure envvar-OPT6134960
Ref: 1cb46134960
Ref: using/configure envvar-CFLAGS_ALIASING6135008
Ref: 1cf26135008
Ref: using/configure envvar-CCSHARED6135155
Ref: 1cf36135155
Ref: using/configure envvar-CFLAGSFORSHARED6135298
Ref: 1cf46135298
Ref: using/configure envvar-PY_CFLAGS6135511
Ref: 1cf56135511
Ref: using/configure envvar-PY_CFLAGS_NODIST6135634
Ref: 1cf66135634
Ref: using/configure envvar-PY_STDMODULE_CFLAGS6135798
Ref: 1cf76135798
Ref: using/configure envvar-PY_CORE_CFLAGS6136021
Ref: 1cf86136021
Ref: using/configure envvar-PY_BUILTIN_MODULE_CFLAGS6136144
Ref: 1cf96136144
Ref: using/configure envvar-PURIFY6136412
Ref: 1cfa6136412
Ref: 編譯器旗標-Footnote-16136574
Node: Linker flags6136629
Ref: using/configure linker-flags6136727
Ref: 1cfb6136727
Ref: using/configure envvar-LINKCC6136770
Ref: 1cfc6136770
Ref: using/configure envvar-CONFIGURE_LDFLAGS6136923
Ref: 1cfd6136923
Ref: using/configure envvar-LDFLAGS_NODIST6137262
Ref: 1cfe6137262
Ref: using/configure envvar-CONFIGURE_LDFLAGS_NODIST6137851
Ref: 1cff6137851
Ref: using/configure envvar-LDFLAGS6138020
Ref: 14236138020
Ref: using/configure envvar-LIBS6138356
Ref: 1d006138356
Ref: using/configure envvar-LDSHARED6138501
Ref: 1d016138501
Ref: using/configure envvar-BLDSHARED6138622
Ref: 1d026138622
Ref: using/configure envvar-PY_LDFLAGS6138764
Ref: 1d036138764
Ref: using/configure envvar-PY_LDFLAGS_NODIST6138853
Ref: 1d046138853
Ref: using/configure envvar-PY_CORE_LDFLAGS6138991
Ref: 1d056138991
Ref: Linker flags-Footnote-16139157
Node: 在 Windows 上使用 Python6139212
Ref: using/windows doc6139360
Ref: 1d066139360
Ref: using/windows using-on-windows6139360
Ref: a4a6139360
Ref: using/windows using-python-on-windows6139360
Ref: 1d076139360
Ref: 在 Windows 上使用 Python-Footnote-16141612
Ref: 在 Windows 上使用 Python-Footnote-26141654
Node: The full installer6141696
Ref: using/windows the-full-installer6141815
Ref: 1d0b6141815
Ref: using/windows windows-full6141815
Ref: 1d086141815
Node: 安裝步驟6142051
Ref: using/windows installation-steps6142159
Ref: 1d0c6142159
Node: Removing the MAX_PATH Limitation6144245
Ref: using/windows max-path6144389
Ref: be86144389
Ref: using/windows removing-the-max-path-limitation6144389
Ref: 1d0e6144389
Node: 安裝排除使用者介面6145243
Ref: using/windows install-quiet-option6145396
Ref: 5926145396
Ref: using/windows installing-without-ui6145396
Ref: 1d0f6145396
Node: 當安裝時不下載6155913
Ref: using/windows install-layout-option6156054
Ref: 1d0d6156054
Ref: using/windows installing-without-downloading6156054
Ref: 1d106156054
Node: Modifying an install6157024
Ref: using/windows modifying-an-install6157171
Ref: 1d116157171
Node: Installing Free-threaded Binaries6158044
Ref: using/windows install-freethreaded-windows6158161
Ref: 1566158161
Ref: using/windows installing-free-threaded-binaries6158161
Ref: 1d126158161
Ref: Installing Free-threaded Binaries-Footnote-16160054
Node: The Microsoft Store package6160096
Ref: using/windows the-microsoft-store-package6160240
Ref: 1d136160240
Ref: using/windows windows-store6160240
Ref: 1aec6160240
Node: Known issues6162391
Ref: using/windows known-issues6162467
Ref: 1d146162467
Node: Redirection of local data registry and temporary paths6162636
Ref: using/windows redirection-of-local-data-registry-and-temporary-paths6162739
Ref: 1d156162739
Ref: Redirection of local data registry and temporary paths-Footnote-16164962
Node: nuget org 套件6165058
Ref: using/windows the-nuget-org-packages6165206
Ref: 1d166165206
Ref: using/windows windows-nuget6165206
Ref: 1d096165206
Ref: nuget org 套件-Footnote-16167572
Ref: nuget org 套件-Footnote-26167603
Ref: nuget org 套件-Footnote-36167649
Ref: nuget org 套件-Footnote-46167698
Node: Free-threaded packages6167749
Ref: using/windows free-threaded-packages6167824
Ref: 1d176167824
Ref: Free-threaded packages-Footnote-16168428
Ref: Free-threaded packages-Footnote-26168487
Ref: Free-threaded packages-Footnote-36168549
Node: The embeddable package6168613
Ref: using/windows the-embeddable-package6168753
Ref: 1d186168753
Ref: using/windows windows-embeddable6168753
Ref: 1d0a6168753
Ref: The embeddable package-Footnote-16170529
Node: Python Application6170648
Ref: using/windows python-application6170747
Ref: 1d196170747
Node: 嵌入 Python6172244
Ref: using/windows embedding-python6172343
Ref: 1d1a6172343
Node: Alternative bundles6173123
Ref: using/windows alternative-bundles6173260
Ref: 1d1b6173260
Ref: Alternative bundles-Footnote-16174203
Ref: Alternative bundles-Footnote-26174256
Ref: Alternative bundles-Footnote-36174299
Ref: Alternative bundles-Footnote-46174338
Ref: Alternative bundles-Footnote-56174505
Node: 設定 Python6174542
Ref: using/windows configuring-python6174669
Ref: 1d1c6174669
Node: Excursus Setting environment variables6175225
Ref: using/windows excursus-setting-environment-variables6175351
Ref: 1d1d6175351
Ref: using/windows setting-envvars6175351
Ref: 1aed6175351
Node: Finding the Python executable6177524
Ref: using/windows finding-the-python-executable6177650
Ref: 1d1e6177650
Ref: using/windows windows-path-mod6177650
Ref: ff36177650
Node: UTF-8 模式6178932
Ref: using/windows utf-8-mode6179067
Ref: 1d1f6179067
Ref: using/windows win-utf8-mode6179067
Ref: 1d206179067
Ref: UTF-8 模式-Footnote-16180590
Ref: UTF-8 模式-Footnote-26180632
Node: Python Launcher for Windows6180674
Ref: using/windows launcher6180808
Ref: 5626180808
Ref: using/windows python-launcher-for-windows6180808
Ref: 1d216180808
Ref: Python Launcher for Windows-Footnote-16181648
Node: 開始6181690
Ref: using/windows getting-started6181782
Ref: 1d226181782
Node: From the command-line6181927
Ref: using/windows from-the-command-line6182037
Ref: 1d236182037
Ref: From the command-line-Footnote-16184536
Node: 虛擬環境（Virtual environment）6184578
Ref: using/windows virtual-environments6184710
Ref: 1d246184710
Node: From a script6185233
Ref: using/windows from-a-script6185359
Ref: 1d256185359
Node: 從檔案關聯6186399
Ref: using/windows from-file-associations6186479
Ref: 1d266186479
Node: Shebang Lines6187037
Ref: using/windows shebang-lines6187164
Ref: 1d276187164
Node: Arguments in shebang lines6191186
Ref: using/windows arguments-in-shebang-lines6191320
Ref: 1d296191320
Node: Customization6191610
Ref: using/windows customization6191742
Ref: 1d2a6191742
Node: Customization via INI files6191869
Ref: using/windows customization-via-ini-files6191990
Ref: 1d2b6191990
Ref: using/windows launcher-ini6191990
Ref: 1d286191990
Node: Customizing default Python versions6192662
Ref: using/windows customizing-default-python-versions6192783
Ref: 1d2c6192783
Node: Diagnostics6196581
Ref: using/windows diagnostics6196694
Ref: 1d2d6196694
Node: Dry Run6197182
Ref: using/windows dry-run6197294
Ref: 1d2e6197294
Node: 安裝隨選6197726
Ref: using/windows install-on-demand6197839
Ref: 1d2f6197839
Node: Return codes6198406
Ref: using/windows return-codes6198503
Ref: 1d306198503
Node: 找尋模組6200255
Ref: using/windows finding-modules6200392
Ref: 1d316200392
Ref: using/windows windows-finding-modules6200392
Ref: bc86200392
Node: 額外的模組6205412
Ref: using/windows additional-modules6205547
Ref: 1d326205547
Node: PyWin326205934
Ref: using/windows pywin326206011
Ref: 1d346206011
Ref: PyWin32-Footnote-16206644
Ref: PyWin32-Footnote-26206686
Ref: PyWin32-Footnote-36206780
Ref: PyWin32-Footnote-46206854
Ref: PyWin32-Footnote-56206948
Ref: PyWin32-Footnote-66207006
Node: cx_Freeze6207056
Ref: using/windows cx-freeze6207133
Ref: 1d356207133
Ref: cx_Freeze-Footnote-16207409
Node: 編譯 Python 在 Windows6207461
Ref: using/windows compiling-python-on-windows6207596
Ref: 1d366207596
Ref: 編譯 Python 在 Windows-Footnote-16208240
Ref: 編譯 Python 在 Windows-Footnote-26208289
Node: 其他平台6208352
Ref: using/windows other-platforms6208463
Ref: 1d386208463
Ref: 其他平台-Footnote-16209016
Ref: 其他平台-Footnote-26209058
Ref: 其他平台-Footnote-36209100
Ref: 其他平台-Footnote-46209155
Ref: 其他平台-Footnote-56209183
Ref: 其他平台-Footnote-66209240
Node: 在 Mac 系統使用 Python6209290
Ref: using/mac doc6209444
Ref: 1d396209444
Ref: using/mac using-on-mac6209444
Ref: 1d3a6209444
Ref: using/mac using-python-on-a-mac6209444
Ref: 1d3b6209444
Ref: using/mac getting-osx6209750
Ref: 1d3c6209750
Node: 取得和安裝 Python6209950
Ref: using/mac getting-and-installing-macpython6210070
Ref: 1576210070
Ref: using/mac getting-and-installing-python6210070
Ref: 1d3d6210070
Ref: 取得和安裝 Python-Footnote-16212052
Ref: 取得和安裝 Python-Footnote-26212155
Node: 如何執行 Python 腳本6212203
Ref: using/mac how-to-run-a-python-script6212320
Ref: 1d3e6212320
Node: 透過 GUI 執行腳本6213720
Ref: using/mac osx-gui-scripts6213852
Ref: 1d406213852
Ref: using/mac running-scripts-with-a-gui6213852
Ref: 1d416213852
Node: 設定6214276
Ref: using/mac configuration6214373
Ref: 1d426214373
Ref: 設定-Footnote-16214916
Node: 整合化開發工具 IDE6214990
Ref: using/mac ide6215148
Ref: 1d3f6215148
Ref: using/mac the-ide6215148
Ref: 1d446215148
Node: 安裝額外的 Python 套件6215369
Ref: using/mac installing-additional-python-packages6215522
Ref: 1d456215522
Ref: using/mac mac-package-manager6215522
Ref: 1d436215522
Ref: 安裝額外的 Python 套件-Footnote-16215690
Node: 開發 GUI 程式6215769
Ref: using/mac gui-programming6215923
Ref: 1d466215923
Ref: using/mac gui-programming-on-the-mac6215923
Ref: 1d476215923
Ref: 開發 GUI 程式-Footnote-16216963
Ref: 開發 GUI 程式-Footnote-26217004
Ref: 開發 GUI 程式-Footnote-36217044
Ref: 開發 GUI 程式-Footnote-46217066
Ref: 開發 GUI 程式-Footnote-56217125
Ref: 開發 GUI 程式-Footnote-66217150
Ref: 開發 GUI 程式-Footnote-76217186
Ref: 開發 GUI 程式-Footnote-86217214
Node: 發行 Python 應用程式6217247
Ref: using/mac distributing-python-applications6217384
Ref: 1d486217384
Ref: using/mac distributing-python-applications-on-the-mac6217384
Ref: 1d496217384
Ref: 發行 Python 應用程式-Footnote-16218006
Ref: 發行 Python 應用程式-Footnote-26218047
Ref: 發行 Python 應用程式-Footnote-36218088
Ref: 發行 Python 應用程式-Footnote-46218116
Node: App Store Compliance6218149
Ref: using/mac app-store-compliance6218232
Ref: 1d4a6218232
Ref: App Store Compliance-Footnote-16219338
Node: 其他資源6219432
Ref: using/mac other-resources6219543
Ref: 1d4b6219543
Node: Using Python on iOS6219844
Ref: using/ios doc6219986
Ref: 1d4c6219986
Ref: using/ios using-ios6219986
Ref: 1d4d6219986
Ref: using/ios using-python-on-ios6219986
Ref: 1d4e6219986
Ref: Using Python on iOS-Footnote-16221513
Ref: Using Python on iOS-Footnote-26221541
Node: Python at runtime on iOS6221566
Ref: using/ios python-at-runtime-on-ios6221679
Ref: 1d506221679
Node: iOS version compatibility6221900
Ref: using/ios ios-version-compatibility6222018
Ref: 1d516222018
Node: Platform identification6222550
Ref: using/ios platform-identification6222706
Ref: 1d526222706
Node: Standard library availability6223348
Ref: using/ios standard-library-availability6223503
Ref: 1d556223503
Node: Binary extension modules6223726
Ref: using/ios binary-extension-modules6223880
Ref: 1d576223880
Node: Compiler stub binaries6226738
Ref: using/ios compiler-stub-binaries6226854
Ref: 1d5b6226854
Node: Installing Python on iOS6228242
Ref: using/ios installing-python-on-ios6228387
Ref: 1d5c6228387
Node: Tools for building iOS apps6228528
Ref: using/ios tools-for-building-ios-apps6228656
Ref: 1d5d6228656
Node: Adding Python to an iOS project6229435
Ref: using/ios adding-ios6229563
Ref: 1d586229563
Ref: using/ios adding-python-to-an-ios-project6229563
Ref: 1d5e6229563
Ref: Adding Python to an iOS project-Footnote-16238226
Ref: Adding Python to an iOS project-Footnote-26238271
Node: App Store Compliance<2>6238338
Ref: using/ios app-store-compliance6238450
Ref: 1d5f6238450
Ref: App Store Compliance<2>-Footnote-16239337
Node: 編輯器與 IDE6239431
Ref: using/editors doc6239537
Ref: 1d606239537
Ref: using/editors editors6239537
Ref: 1d616239537
Ref: using/editors editors-and-ides6239537
Ref: 1d626239537
Ref: 編輯器與 IDE-Footnote-16239872
Ref: 編輯器與 IDE-Footnote-26239914
Ref: 編輯器與 IDE-Footnote-36239965
Node: Python 語言參考手冊6240036
Ref: reference/index doc6240183
Ref: 1d636240183
Ref: reference/index reference-index6240183
Ref: 12b6240183
Ref: reference/index the-python-language-reference6240183
Ref: 1d646240183
Node: 簡介<5>6241080
Ref: reference/introduction doc6241172
Ref: 1d656241172
Ref: reference/introduction id16241172
Ref: 1d666241172
Ref: reference/introduction introduction6241172
Ref: 1d676241172
Node: Alternate Implementations6242959
Ref: reference/introduction alternate-implementations6243047
Ref: 1d686243047
Ref: reference/introduction implementations6243047
Ref: 1c286243047
Ref: Alternate Implementations-Footnote-16245223
Ref: Alternate Implementations-Footnote-26245255
Ref: Alternate Implementations-Footnote-36245292
Ref: Alternate Implementations-Footnote-46245324
Node: Notation6245354
Ref: reference/introduction id26245442
Ref: 1d696245442
Ref: reference/introduction notation6245442
Ref: 1d6a6245442
Ref: reference/introduction grammar-token-notation-name6245629
Ref: 1d6b6245629
Ref: reference/introduction grammar-token-notation-lc_letter6245677
Ref: 1d6c6245677
Ref: Notation-Footnote-16247739
Node: 詞法分析6247802
Ref: reference/lexical_analysis doc6247915
Ref: 1d6d6247915
Ref: reference/lexical_analysis lexical6247915
Ref: 1d6e6247915
Ref: reference/lexical_analysis lexical-analysis6247915
Ref: 1d6f6247915
Ref: 詞法分析-Footnote-16248548
Node: Line structure6248590
Ref: reference/lexical_analysis id16248674
Ref: 1d706248674
Ref: reference/lexical_analysis line-structure6248674
Ref: 1d716248674
Node: Logical lines6248980
Ref: reference/lexical_analysis id26249067
Ref: 1d726249067
Ref: reference/lexical_analysis logical-lines6249067
Ref: 1d736249067
Node: Physical lines6249445
Ref: reference/lexical_analysis id36249549
Ref: 1d746249549
Ref: reference/lexical_analysis physical-lines6249549
Ref: 1d756249549
Node: Comments6250320
Ref: reference/lexical_analysis comments6250432
Ref: 1d766250432
Ref: reference/lexical_analysis id46250432
Ref: 1d776250432
Node: Encoding declarations6250735
Ref: reference/lexical_analysis encoding-declarations6250854
Ref: 1d786250854
Ref: reference/lexical_analysis encodings6250854
Ref: 1d796250854
Node: Explicit line joining6251967
Ref: reference/lexical_analysis explicit-joining6252099
Ref: 1d7a6252099
Ref: reference/lexical_analysis explicit-line-joining6252099
Ref: 1d7b6252099
Node: Implicit line joining6253037
Ref: reference/lexical_analysis implicit-joining6253159
Ref: 1d7c6253159
Ref: reference/lexical_analysis implicit-line-joining6253159
Ref: 1d7d6253159
Node: Blank lines6253995
Ref: reference/lexical_analysis blank-lines6254107
Ref: 1d7e6254107
Ref: reference/lexical_analysis id56254107
Ref: 1d7f6254107
Node: Indentation6254582
Ref: reference/lexical_analysis id66254698
Ref: 1d806254698
Ref: reference/lexical_analysis indentation6254698
Ref: 1d816254698
Node: Whitespace between tokens6258079
Ref: reference/lexical_analysis whitespace6258175
Ref: 1d826258175
Ref: reference/lexical_analysis whitespace-between-tokens6258175
Ref: 1d836258175
Node: Other tokens6258577
Ref: reference/lexical_analysis id76258694
Ref: 1d846258694
Ref: reference/lexical_analysis other-tokens6258694
Ref: 1d856258694
Node: Identifiers and keywords6259126
Ref: reference/lexical_analysis identifiers6259237
Ref: 1d866259237
Ref: reference/lexical_analysis identifiers-and-keywords6259237
Ref: 1d876259237
Ref: reference/lexical_analysis grammar-token-python-grammar-identifier6260131
Ref: 1d886260131
Ref: reference/lexical_analysis grammar-token-python-grammar-id_start6260177
Ref: 1d896260177
Ref: reference/lexical_analysis grammar-token-python-grammar-id_continue6260326
Ref: 1d8a6260326
Ref: reference/lexical_analysis grammar-token-python-grammar-xid_start6260474
Ref: 1d8b6260474
Ref: reference/lexical_analysis grammar-token-python-grammar-xid_continue6260581
Ref: 1d8c6260581
Ref: Identifiers and keywords-Footnote-16261590
Ref: Identifiers and keywords-Footnote-26261632
Ref: Identifiers and keywords-Footnote-36261674
Node: 關鍵字6261737
Ref: reference/lexical_analysis id86261828
Ref: 1d8d6261828
Ref: reference/lexical_analysis keywords6261828
Ref: 1d8e6261828
Node: 軟關鍵字6262422
Ref: reference/lexical_analysis id96262553
Ref: 1d8f6262553
Ref: reference/lexical_analysis soft-keywords6262553
Ref: 7b06262553
Node: Reserved classes of identifiers6263257
Ref: reference/lexical_analysis id-classes6263370
Ref: 1d906263370
Ref: reference/lexical_analysis reserved-classes-of-identifiers6263370
Ref: 1d916263370
Node: Literals6265282
Ref: reference/lexical_analysis id106265390
Ref: 1d936265390
Ref: reference/lexical_analysis literals6265390
Ref: 1d946265390
Node: String and Bytes literals6265740
Ref: reference/lexical_analysis string-and-bytes-literals6265847
Ref: 1d956265847
Ref: reference/lexical_analysis strings6265847
Ref: 1d966265847
Ref: reference/lexical_analysis grammar-token-python-grammar-stringliteral6265985
Ref: 1d976265985
Ref: reference/lexical_analysis grammar-token-python-grammar-stringprefix6266051
Ref: 1d986266051
Ref: reference/lexical_analysis grammar-token-python-grammar-shortstring6266191
Ref: 1d996266191
Ref: reference/lexical_analysis grammar-token-python-grammar-longstring6266268
Ref: 1d9a6266268
Ref: reference/lexical_analysis grammar-token-python-grammar-shortstringitem6266351
Ref: 1d9b6266351
Ref: reference/lexical_analysis grammar-token-python-grammar-longstringitem6266410
Ref: 1d9c6266410
Ref: reference/lexical_analysis grammar-token-python-grammar-shortstringchar6266468
Ref: 1d9d6266468
Ref: reference/lexical_analysis grammar-token-python-grammar-longstringchar6266551
Ref: 1d9e6266551
Ref: reference/lexical_analysis grammar-token-python-grammar-stringescapeseq6266610
Ref: 1d9f6266610
Ref: reference/lexical_analysis grammar-token-python-grammar-bytesliteral6266663
Ref: 1da06266663
Ref: reference/lexical_analysis grammar-token-python-grammar-bytesprefix6266723
Ref: 1da16266723
Ref: reference/lexical_analysis grammar-token-python-grammar-shortbytes6266813
Ref: 1da26266813
Ref: reference/lexical_analysis grammar-token-python-grammar-longbytes6266887
Ref: 1da36266887
Ref: reference/lexical_analysis grammar-token-python-grammar-shortbytesitem6266967
Ref: 1da46266967
Ref: reference/lexical_analysis grammar-token-python-grammar-longbytesitem6267023
Ref: 1da56267023
Ref: reference/lexical_analysis grammar-token-python-grammar-shortbyteschar6267078
Ref: 1da66267078
Ref: reference/lexical_analysis grammar-token-python-grammar-longbyteschar6267159
Ref: 1da76267159
Ref: reference/lexical_analysis grammar-token-python-grammar-bytesescapeseq6267216
Ref: 1da86267216
Ref: String and Bytes literals-Footnote-16269757
Node: 跳脫序列6269799
Ref: reference/lexical_analysis escape-sequences6269873
Ref: 4006269873
Ref: reference/lexical_analysis id116269873
Ref: 1da96269873
Ref: 跳脫序列-Footnote-16276172
Node: String literal concatenation6276244
Ref: reference/lexical_analysis string-concatenation6276382
Ref: 1daa6276382
Ref: reference/lexical_analysis string-literal-concatenation6276382
Ref: 1dab6276382
Ref: reference/lexical_analysis f-strings6277421
Ref: 94d6277421
Node: f-string（f 字串）6277421
Ref: reference/lexical_analysis formatted-string-literals6277550
Ref: 1dac6277550
Ref: reference/lexical_analysis id136277550
Ref: 1dad6277550
Ref: reference/lexical_analysis grammar-token-python-grammar-f_string6278153
Ref: 1dae6278153
Ref: reference/lexical_analysis grammar-token-python-grammar-replacement_field6278230
Ref: 1daf6278230
Ref: reference/lexical_analysis grammar-token-python-grammar-f_expression6278319
Ref: 1db06278319
Ref: reference/lexical_analysis grammar-token-python-grammar-conversion6278514
Ref: 1db16278514
Ref: reference/lexical_analysis grammar-token-python-grammar-format_spec6278557
Ref: 1db26278557
Ref: reference/lexical_analysis grammar-token-python-grammar-literal_char6278620
Ref: 1db36278620
Ref: f-string（f 字串）-Footnote-16284136
Node: Numeric literals6284178
Ref: reference/lexical_analysis numbers6284295
Ref: 1db46284295
Ref: reference/lexical_analysis numeric-literals6284295
Ref: 1db56284295
Node: Integer literals6284725
Ref: reference/lexical_analysis integer-literals6284859
Ref: 1db66284859
Ref: reference/lexical_analysis integers6284859
Ref: 1db76284859
Ref: reference/lexical_analysis grammar-token-python-grammar-integer6284980
Ref: 1db86284980
Ref: reference/lexical_analysis grammar-token-python-grammar-decinteger6285052
Ref: 1db96285052
Ref: reference/lexical_analysis grammar-token-python-grammar-bininteger6285122
Ref: 1dba6285122
Ref: reference/lexical_analysis grammar-token-python-grammar-octinteger6285178
Ref: 1dbb6285178
Ref: reference/lexical_analysis grammar-token-python-grammar-hexinteger6285234
Ref: 1dbc6285234
Ref: reference/lexical_analysis grammar-token-python-grammar-nonzerodigit6285290
Ref: 1dbd6285290
Ref: reference/lexical_analysis grammar-token-python-grammar-digit6285322
Ref: 1dbe6285322
Ref: reference/lexical_analysis grammar-token-python-grammar-bindigit6285354
Ref: 1dbf6285354
Ref: reference/lexical_analysis grammar-token-python-grammar-octdigit6285386
Ref: 1dc06285386
Ref: reference/lexical_analysis grammar-token-python-grammar-hexdigit6285418
Ref: 1dc16285418
Node: 浮點數常數 Floating-point literals6286270
Ref: reference/lexical_analysis floating6286406
Ref: 1dc26286406
Ref: reference/lexical_analysis floating-point-literals6286406
Ref: 1dc36286406
Ref: reference/lexical_analysis grammar-token-python-grammar-floatnumber6286579
Ref: 1dc46286579
Ref: reference/lexical_analysis grammar-token-python-grammar-pointfloat6286629
Ref: 1dc56286629
Ref: reference/lexical_analysis grammar-token-python-grammar-exponentfloat6286689
Ref: 1dc66286689
Ref: reference/lexical_analysis grammar-token-python-grammar-digitpart6286746
Ref: 1dc76286746
Ref: reference/lexical_analysis grammar-token-python-grammar-fraction6286790
Ref: 1dc86286790
Ref: reference/lexical_analysis grammar-token-python-grammar-exponent6286827
Ref: 1dc96286827
Node: Imaginary literals6287383
Ref: reference/lexical_analysis imaginary6287494
Ref: 1dca6287494
Ref: reference/lexical_analysis imaginary-literals6287494
Ref: 1dcb6287494
Ref: reference/lexical_analysis grammar-token-python-grammar-imagnumber6287621
Ref: 1dcc6287621
Node: Operators6288084
Ref: reference/lexical_analysis id146288178
Ref: 1dcd6288178
Ref: reference/lexical_analysis operators6288178
Ref: 1dce6288178
Node: Delimiters6288415
Ref: reference/lexical_analysis delimiters6288492
Ref: 1dcf6288492
Ref: reference/lexical_analysis id156288492
Ref: 1dd06288492
Node: 資料模型6289428
Ref: reference/datamodel doc6289544
Ref: 1dd16289544
Ref: reference/datamodel data-model6289544
Ref: 1dd26289544
Ref: reference/datamodel datamodel6289544
Ref: 18756289544
Node: Objects values and types6289699
Ref: reference/datamodel objects6289799
Ref: 1dd36289799
Ref: reference/datamodel objects-values-and-types6289799
Ref: 1dd46289799
Ref: Objects values and types-Footnote-16294779
Node: 標準型別階層6295002
Ref: reference/datamodel the-standard-type-hierarchy6295131
Ref: 1dd56295131
Ref: reference/datamodel types6295131
Ref: 1dd66295131
Node: None6296112
Ref: reference/datamodel none6296194
Ref: 1dd76296194
Node: NotImplemented6296525
Ref: reference/datamodel notimplemented6296624
Ref: 1dd86296624
Node: Ellipsis6297423
Ref: reference/datamodel ellipsis6297532
Ref: 1dda6297532
Node: numbers Number6297758
Ref: reference/datamodel numbers-number6297862
Ref: 1ddb6297862
Node: numbers Integral6299093
Ref: reference/datamodel numbers-integral6299187
Ref: 1ddc6299187
Node: numbers Real float6300410
Ref: reference/datamodel numbers-real-float6300536
Ref: 1ddd6300536
Node: numbers Complex complex6301121
Ref: reference/datamodel numbers-complex-complex6301222
Ref: 1dde6301222
Node: Sequences6301602
Ref: reference/datamodel sequences6301707
Ref: 1ddf6301707
Node: Immutable sequences6302858
Ref: reference/datamodel immutable-sequences6302949
Ref: 1de06302949
Node: Mutable sequences6304922
Ref: reference/datamodel mutable-sequences6305013
Ref: 1de26305013
Node: Set types6306002
Ref: reference/datamodel set-types6306101
Ref: 1de36306101
Node: Mappings6307328
Ref: reference/datamodel mappings6307432
Ref: 1de46307432
Node: 字典6307892
Ref: reference/datamodel dictionaries6307943
Ref: 1de56307943
Node: Callable types6309364
Ref: reference/datamodel callable-types6309468
Ref: 1de66309468
Node: 自訂函式6309832
Ref: reference/datamodel user-defined-funcs6309920
Ref: 2956309920
Ref: reference/datamodel user-defined-functions6309920
Ref: 1de76309920
Node: 特殊唯讀屬性6310246
Ref: reference/datamodel special-read-only-attributes6310340
Ref: 1de86310340
Ref: reference/datamodel function __globals__6310710
Ref: 12666310710
Ref: reference/datamodel function __closure__6311214
Ref: 12636311214
Node: 特殊可寫屬性6311798
Ref: reference/datamodel special-writable-attributes6311892
Ref: 1dea6311892
Ref: reference/datamodel function __doc__6312322
Ref: 11716312322
Ref: reference/datamodel function __name__6312644
Ref: 12676312644
Ref: reference/datamodel function __qualname__6312937
Ref: 1deb6312937
Ref: reference/datamodel function __module__6313383
Ref: 1ded6313383
Ref: reference/datamodel function __defaults__6313691
Ref: 12646313691
Ref: reference/datamodel function __code__6314184
Ref: 2966314184
Ref: reference/datamodel function __dict__6314411
Ref: 12656314411
Ref: reference/datamodel function __annotations__6314796
Ref: 11706314796
Ref: reference/datamodel function __kwdefaults__6315427
Ref: fcb6315427
Ref: reference/datamodel function __type_params__6315738
Ref: 1def6315738
Node: Instance methods6316732
Ref: reference/datamodel id26316848
Ref: 1df16316848
Ref: reference/datamodel instance-methods6316848
Ref: 1bc16316848
Ref: reference/datamodel method __self__6317073
Ref: 13366317073
Ref: reference/datamodel method __func__6317375
Ref: 128f6317375
Ref: reference/datamodel method __doc__6317594
Ref: 1df36317594
Ref: reference/datamodel method __name__6318085
Ref: 1df46318085
Ref: reference/datamodel method __module__6318382
Ref: 1df56318382
Ref: reference/datamodel method-binding6318953
Ref: 1df26318953
Node: Generator functions6320421
Ref: reference/datamodel generator-functions6320544
Ref: 1df66320544
Node: Coroutine functions6321241
Ref: reference/datamodel coroutine-functions6321380
Ref: 1df76321380
Node: Asynchronous generator functions6321784
Ref: reference/datamodel asynchronous-generator-functions6321922
Ref: 1df96321922
Node: Built-in functions6322790
Ref: reference/datamodel built-in-functions6322925
Ref: 1dfb6322925
Ref: reference/datamodel builtin-functions6322925
Ref: 1df06322925
Node: Built-in methods6323702
Ref: reference/datamodel built-in-methods6323812
Ref: 1dfc6323812
Ref: reference/datamodel builtin-methods6323812
Ref: 1dfd6323812
Node: Classes6324301
Ref: reference/datamodel classes6324408
Ref: 1dfe6324408
Node: Class Instances6324761
Ref: reference/datamodel class-instances6324843
Ref: 1dff6324843
Node: 模組<2>6325007
Ref: reference/datamodel modules6325117
Ref: 1e006325117
Node: Custom classes6327314
Ref: reference/datamodel custom-classes6327425
Ref: 1e036327425
Node: Class instances6330193
Ref: reference/datamodel id36330333
Ref: 1e046330333
Node: I/O objects also known as file objects6331863
Ref: reference/datamodel i-o-objects-also-known-as-file-objects6332003
Ref: 1e076332003
Node: Internal types6332745
Ref: reference/datamodel internal-types6332861
Ref: 1e096332861
Node: Code objects6333235
Ref: reference/datamodel code-objects6333320
Ref: 1b66333320
Ref: reference/datamodel id46333320
Ref: 1e0a6333320
Node: 特殊唯讀屬性<2>6334038
Ref: reference/datamodel id56334147
Ref: 1e0b6334147
Ref: reference/datamodel codeobject co_name6334228
Ref: 1e0c6334228
Ref: reference/datamodel codeobject co_qualname6334414
Ref: 1e0d6334414
Ref: reference/datamodel codeobject co_argcount6334751
Ref: 1e0e6334751
Ref: reference/datamodel codeobject co_posonlyargcount6335243
Ref: 1e0f6335243
Ref: reference/datamodel codeobject co_kwonlyargcount6335639
Ref: 1e106335639
Ref: reference/datamodel codeobject co_nlocals6336026
Ref: 1e116336026
Ref: reference/datamodel codeobject co_varnames6336338
Ref: 1e126336338
Ref: reference/datamodel codeobject co_cellvars6336733
Ref: 1e136336733
Ref: reference/datamodel codeobject co_freevars6337145
Ref: 1e146337145
Ref: reference/datamodel codeobject co_code6337440
Ref: 1e156337440
Ref: reference/datamodel codeobject co_consts6337754
Ref: 1e166337754
Ref: reference/datamodel codeobject co_names6338070
Ref: 1e176338070
Ref: reference/datamodel codeobject co_filename6338387
Ref: 12fa6338387
Ref: reference/datamodel codeobject co_firstlineno6338668
Ref: 1e186338668
Ref: reference/datamodel codeobject co_lnotab6338882
Ref: 2b76338882
Ref: reference/datamodel codeobject co_stacksize6339575
Ref: 1e196339575
Ref: reference/datamodel codeobject co_flags6339783
Ref: 1e1a6339783
Node: 用於程式碼物件的方法6341023
Ref: reference/datamodel methods-on-code-objects6341132
Ref: 1e1c6341132
Ref: reference/datamodel codeobject co_positions6341203
Ref: 5576341203
Ref: reference/datamodel codeobject co_lines6342752
Ref: 2cc6342752
Ref: reference/datamodel codeobject replace6344382
Ref: 1e1d6344382
Ref: 用於程式碼物件的方法-Footnote-16344669
Node: Frame objects6344711
Ref: reference/datamodel frame-objects6344822
Ref: 27e6344822
Ref: reference/datamodel id66344822
Ref: 1e1e6344822
Node: 特殊唯讀屬性<3>6345137
Ref: reference/datamodel id76345238
Ref: 1e1f6345238
Ref: reference/datamodel frame f_back6345313
Ref: 7306345313
Ref: reference/datamodel frame f_code6345642
Ref: 1e206345642
Ref: reference/datamodel frame f_locals6346185
Ref: 1656346185
Ref: reference/datamodel frame f_globals6346917
Ref: 1e216346917
Ref: reference/datamodel frame f_builtins6347216
Ref: 1e226347216
Ref: reference/datamodel frame f_lasti6347521
Ref: 82c6347521
Node: 特殊可寫屬性<2>6347853
Ref: reference/datamodel id86347983
Ref: 1e236347983
Ref: reference/datamodel frame f_trace6348059
Ref: 1e246348059
Ref: reference/datamodel frame f_trace_lines6348604
Ref: b826348604
Ref: reference/datamodel frame f_trace_opcodes6348930
Ref: b836348930
Ref: reference/datamodel frame f_lineno6349535
Ref: 7506349535
Node: Frame object methods6350081
Ref: reference/datamodel frame-object-methods6350181
Ref: 1e256350181
Ref: reference/datamodel frame clear6350277
Ref: 27f6350277
Node: Traceback objects6350957
Ref: reference/datamodel id96351069
Ref: 1e266351069
Ref: reference/datamodel traceback-objects6351069
Ref: a976351069
Ref: reference/datamodel traceback tb_frame6352383
Ref: 1e276352383
Ref: reference/datamodel traceback tb_lineno6352970
Ref: 1e286352970
Ref: reference/datamodel traceback tb_lasti6353189
Ref: 1e296353189
Ref: reference/datamodel traceback tb_next6353555
Ref: a966353555
Node: Slice objects6353834
Ref: reference/datamodel slice-objects6353954
Ref: 1e2a6353954
Ref: reference/datamodel slice indices6354401
Ref: fca6354401
Node: Static method objects6354883
Ref: reference/datamodel static-method-objects6355006
Ref: 1e2e6355006
Node: Class method objects6355606
Ref: reference/datamodel class-method-objects6355707
Ref: 1e2f6355707
Node: Special method names6356150
Ref: reference/datamodel special-method-names6356261
Ref: 1e306356261
Ref: reference/datamodel specialnames6356261
Ref: c156356261
Ref: Special method names-Footnote-16358180
Node: Basic customization6358519
Ref: reference/datamodel basic-customization6358632
Ref: 1e346358632
Ref: reference/datamodel customization6358632
Ref: 1e356358632
Ref: reference/datamodel object __new__6358689
Ref: 5266358689
Ref: reference/datamodel object __init__6360242
Ref: 6556360242
Ref: reference/datamodel object __del__6361099
Ref: 1e366361099
Ref: reference/datamodel object __repr__6364376
Ref: 5c26364376
Ref: reference/datamodel object __str__6365214
Ref: 5c46365214
Ref: reference/datamodel object __bytes__6365862
Ref: 58e6365862
Ref: reference/datamodel object __format__6366046
Ref: 5c56366046
Ref: reference/datamodel richcmpfuncs6367158
Ref: 1e376367158
Ref: reference/datamodel object __lt__6367158
Ref: 129e6367158
Ref: reference/datamodel object __le__6367198
Ref: 129f6367198
Ref: reference/datamodel object __eq__6367238
Ref: a9d6367238
Ref: reference/datamodel object __ne__6367278
Ref: 14866367278
Ref: reference/datamodel object __gt__6367318
Ref: 12a06367318
Ref: reference/datamodel object __ge__6367358
Ref: 12a16367358
Ref: reference/datamodel object __hash__6370084
Ref: a9e6370084
Ref: reference/datamodel object __bool__6374308
Ref: 12686374308
Node: Customizing attribute access6374748
Ref: reference/datamodel attribute-access6374896
Ref: 1e396374896
Ref: reference/datamodel customizing-attribute-access6374896
Ref: 1e3a6374896
Ref: reference/datamodel object __getattr__6375128
Ref: 47a6375128
Ref: reference/datamodel object __getattribute__6376375
Ref: b796376375
Ref: reference/datamodel object __setattr__6377483
Ref: 1e056377483
Ref: reference/datamodel object __delattr__6378158
Ref: 1e066378158
Ref: reference/datamodel object __dir__6378544
Ref: 1e3c6378544
Node: Customizing module attribute access6378886
Ref: reference/datamodel customizing-module-attribute-access6379019
Ref: 1e3d6379019
Ref: Customizing module attribute access-Footnote-16381143
Node: Implementing Descriptors6381185
Ref: reference/datamodel descriptors6381347
Ref: bf66381347
Ref: reference/datamodel implementing-descriptors6381347
Ref: 1e3e6381347
Ref: reference/datamodel object __get__6381819
Ref: 16c36381819
Ref: reference/datamodel object __set__6382746
Ref: 1e3f6382746
Ref: reference/datamodel object __delete__6383100
Ref: 14fc6383100
Ref: reference/datamodel object __objclass__6383318
Ref: 1e416383318
Ref: Implementing Descriptors-Footnote-16383882
Node: Invoking Descriptors6383924
Ref: reference/datamodel descriptor-invocation6384063
Ref: 1e406384063
Ref: reference/datamodel invoking-descriptors6384063
Ref: 1e426384063
Node: __slots__<2>6387209
Ref: reference/datamodel id116387315
Ref: 1e436387315
Ref: reference/datamodel slots6387315
Ref: 1e446387315
Ref: reference/datamodel object __slots__6387692
Ref: 14586387692
Ref: reference/datamodel datamodel-note-slots6388017
Ref: 1e456388017
Node: Customizing class creation6391079
Ref: reference/datamodel class-customization6391248
Ref: bf26391248
Ref: reference/datamodel customizing-class-creation6391248
Ref: 1e486391248
Ref: reference/datamodel object __init_subclass__6391731
Ref: 5d76391731
Ref: reference/datamodel object __set_name__6393201
Ref: bf56393201
Node: Metaclasses6394160
Ref: reference/datamodel id126394264
Ref: 1e496394264
Ref: reference/datamodel metaclasses6394264
Ref: 1e4a6394264
Node: Resolving MRO entries6395319
Ref: reference/datamodel resolving-mro-entries6395469
Ref: 1e4b6395469
Ref: reference/datamodel object __mro_entries__6395530
Ref: 1e4c6395530
Ref: Resolving MRO entries-Footnote-16396539
Node: Determining the appropriate metaclass6396581
Ref: reference/datamodel determining-the-appropriate-metaclass6396749
Ref: 1e4d6396749
Node: Preparing the class namespace6397680
Ref: reference/datamodel prepare6397851
Ref: c056397851
Ref: reference/datamodel preparing-the-class-namespace6397851
Ref: 1e4e6397851
Ref: Preparing the class namespace-Footnote-16398753
Node: Executing the class body6398795
Ref: reference/datamodel executing-the-class-body6398954
Ref: 1e4f6398954
Node: Creating the class object6399689
Ref: reference/datamodel class-object-creation6399839
Ref: bf16399839
Ref: reference/datamodel creating-the-class-object6399839
Ref: 1e506399839
Ref: Creating the class object-Footnote-16402276
Node: Uses for metaclasses6402318
Ref: reference/datamodel uses-for-metaclasses6402435
Ref: 1e516402435
Node: Customizing instance and subclass checks6402746
Ref: reference/datamodel customizing-instance-and-subclass-checks6402910
Ref: 1e526402910
Ref: reference/datamodel class __instancecheck__6403396
Ref: 1e536403396
Ref: reference/datamodel class __subclasscheck__6403625
Ref: 1e546403625
Ref: Customizing instance and subclass checks-Footnote-16404577
Node: Emulating generic types6404619
Ref: reference/datamodel emulating-generic-types6404783
Ref: 1e556404783
Ref: reference/datamodel object __class_getitem__6405690
Ref: 6df6405690
Ref: Emulating generic types-Footnote-16406188
Node: The purpose of __class_getitem__6406230
Ref: reference/datamodel the-purpose-of-class-getitem6406367
Ref: 1e576406367
Node: __class_getitem__ versus __getitem__6407258
Ref: reference/datamodel class-getitem-versus-getitem6407395
Ref: 1e596407395
Ref: reference/datamodel classgetitem-versus-getitem6407395
Ref: 1e5a6407395
Ref: __class_getitem__ versus __getitem__-Footnote-16410721
Node: Emulating callable objects6410763
Ref: reference/datamodel emulating-callable-objects6410912
Ref: 1e5e6410912
Ref: reference/datamodel id136410912
Ref: 1e5f6410912
Ref: reference/datamodel object __call__6410985
Ref: 4fe6410985
Node: Emulating container types6411212
Ref: reference/datamodel emulating-container-types6411361
Ref: 1e606411361
Ref: reference/datamodel sequence-types6411361
Ref: 1e616411361
Ref: reference/datamodel object __len__6413675
Ref: 1e386413675
Ref: reference/datamodel object __length_hint__6414401
Ref: eaf6414401
Ref: reference/datamodel object __getitem__6415190
Ref: 2666415190
Ref: reference/datamodel object __setitem__6416318
Ref: 14346416318
Ref: reference/datamodel object __delitem__6416780
Ref: 14356416780
Ref: reference/datamodel object __missing__6417206
Ref: 1e686417206
Ref: reference/datamodel object __iter__6417397
Ref: 1e316417397
Ref: reference/datamodel object __reversed__6417704
Ref: 1e326417704
Ref: reference/datamodel object __contains__6418691
Ref: 1e336418691
Node: Emulating numeric types6419255
Ref: reference/datamodel emulating-numeric-types6419409
Ref: 1e6a6419409
Ref: reference/datamodel numeric-types6419409
Ref: 1e6b6419409
Ref: reference/datamodel object __add__6419724
Ref: 1e626419724
Ref: reference/datamodel object __sub__6419765
Ref: 1e6c6419765
Ref: reference/datamodel object __mul__6419806
Ref: 1e656419806
Ref: reference/datamodel object __matmul__6419847
Ref: 1e6d6419847
Ref: reference/datamodel object __truediv__6419891
Ref: 14616419891
Ref: reference/datamodel object __floordiv__6419936
Ref: 14626419936
Ref: reference/datamodel object __mod__6419982
Ref: 1e6e6419982
Ref: reference/datamodel object __divmod__6420023
Ref: 1e6f6420023
Ref: reference/datamodel object __pow__6420067
Ref: 7776420067
Ref: reference/datamodel object __lshift__6420118
Ref: 1e706420118
Ref: reference/datamodel object __rshift__6420162
Ref: 1e716420162
Ref: reference/datamodel object __and__6420206
Ref: 1e726420206
Ref: reference/datamodel object __xor__6420247
Ref: 1e736420247
Ref: reference/datamodel object __or__6420288
Ref: 1e746420288
Ref: reference/datamodel object __radd__6421287
Ref: 1e636421287
Ref: reference/datamodel object __rsub__6421329
Ref: 1e756421329
Ref: reference/datamodel object __rmul__6421371
Ref: 1e666421371
Ref: reference/datamodel object __rmatmul__6421413
Ref: 1e766421413
Ref: reference/datamodel object __rtruediv__6421458
Ref: 1e776421458
Ref: reference/datamodel object __rfloordiv__6421504
Ref: 1e786421504
Ref: reference/datamodel object __rmod__6421551
Ref: 1e796421551
Ref: reference/datamodel object __rdivmod__6421593
Ref: 1e7a6421593
Ref: reference/datamodel object __rpow__6421638
Ref: 7786421638
Ref: reference/datamodel object __rlshift__6421690
Ref: 1e7b6421690
Ref: reference/datamodel object __rrshift__6421735
Ref: 1e7c6421735
Ref: reference/datamodel object __rand__6421780
Ref: 1e7d6421780
Ref: reference/datamodel object __rxor__6421822
Ref: 1e7e6421822
Ref: reference/datamodel object __ror__6421864
Ref: 1e7f6421864
Ref: reference/datamodel object __iadd__6423138
Ref: 1e646423138
Ref: reference/datamodel object __isub__6423180
Ref: 1e806423180
Ref: reference/datamodel object __imul__6423222
Ref: 1e676423222
Ref: reference/datamodel object __imatmul__6423264
Ref: 1e816423264
Ref: reference/datamodel object __itruediv__6423309
Ref: 1e826423309
Ref: reference/datamodel object __ifloordiv__6423355
Ref: 1e836423355
Ref: reference/datamodel object __imod__6423402
Ref: 1e846423402
Ref: reference/datamodel object __ipow__6423444
Ref: 7756423444
Ref: reference/datamodel object __ilshift__6423496
Ref: 1e856423496
Ref: reference/datamodel object __irshift__6423541
Ref: 1e866423541
Ref: reference/datamodel object __iand__6423586
Ref: 1e876423586
Ref: reference/datamodel object __ixor__6423628
Ref: 1e886423628
Ref: reference/datamodel object __ior__6423670
Ref: 1e896423670
Ref: reference/datamodel object __neg__6424872
Ref: 1e8b6424872
Ref: reference/datamodel object __pos__6424906
Ref: 1e8c6424906
Ref: reference/datamodel object __abs__6424940
Ref: 1e8d6424940
Ref: reference/datamodel object __invert__6424974
Ref: 1e8e6424974
Ref: reference/datamodel object __complex__6425127
Ref: 58d6425127
Ref: reference/datamodel object __int__6425165
Ref: 6c06425165
Ref: reference/datamodel object __float__6425199
Ref: 9706425199
Ref: reference/datamodel object __index__6425407
Ref: 6c16425407
Ref: reference/datamodel object __round__6426084
Ref: 1e8f6426084
Ref: reference/datamodel object __trunc__6426131
Ref: 6bf6426131
Ref: reference/datamodel object __floor__6426167
Ref: 1e906426167
Ref: reference/datamodel object __ceil__6426203
Ref: 1e916426203
Ref: Emulating numeric types-Footnote-16426919
Ref: Emulating numeric types-Footnote-26427233
Node: With Statement Context Managers6427454
Ref: reference/datamodel context-managers6427641
Ref: 1e936427641
Ref: reference/datamodel with-statement-context-managers6427641
Ref: 1e946427641
Ref: reference/datamodel object __enter__6428404
Ref: 56c6428404
Ref: reference/datamodel object __exit__6428652
Ref: 12936428652
Ref: With Statement Context Managers-Footnote-16429530
Node: Customizing positional arguments in class pattern matching6429572
Ref: reference/datamodel class-pattern-matching6429758
Ref: 1e966429758
Ref: reference/datamodel customizing-positional-arguments-in-class-pattern-matching6429758
Ref: 1e976429758
Ref: reference/datamodel object __match_args__6430189
Ref: 17c26430189
Ref: Customizing positional arguments in class pattern matching-Footnote-16431148
Node: Emulating buffer types6431190
Ref: reference/datamodel emulating-buffer-types6431366
Ref: 1e986431366
Ref: reference/datamodel python-buffer-protocol6431366
Ref: 1e996431366
Ref: reference/datamodel object __buffer__6431823
Ref: 4056431823
Ref: reference/datamodel object __release_buffer__6432302
Ref: 15ed6432302
Ref: Emulating buffer types-Footnote-16433040
Node: Special method lookup6433082
Ref: reference/datamodel special-lookup6433191
Ref: 1e3b6433191
Ref: reference/datamodel special-method-lookup6433191
Ref: 1e9a6433191
Node: 協程6435902
Ref: reference/datamodel coroutines6435986
Ref: 1e9b6435986
Node: Awaitable Objects6436126
Ref: reference/datamodel awaitable-objects6436212
Ref: 1e9c6436212
Ref: reference/datamodel object __await__6436655
Ref: 1e9d6436655
Ref: Awaitable Objects-Footnote-16437426
Node: Coroutine Objects6437468
Ref: reference/datamodel coroutine-objects6437585
Ref: 1df86437585
Ref: reference/datamodel id166437585
Ref: 1e9e6437585
Ref: reference/datamodel coroutine send6438457
Ref: 1ea16438457
Ref: reference/datamodel coroutine throw6438986
Ref: 49f6438986
Ref: reference/datamodel coroutine close6439767
Ref: 1ea36439767
Node: Asynchronous Iterators6440390
Ref: reference/datamodel async-iterators6440519
Ref: d206440519
Ref: reference/datamodel asynchronous-iterators6440519
Ref: 1ea46440519
Ref: reference/datamodel object __aiter__6440743
Ref: ba26440743
Ref: reference/datamodel object __anext__6440833
Ref: 1dfa6440833
Node: Asynchronous Context Managers6441731
Ref: reference/datamodel async-context-managers6441834
Ref: 5a06441834
Ref: reference/datamodel asynchronous-context-managers6441834
Ref: 1ea56441834
Ref: reference/datamodel object __aenter__6442139
Ref: 1ea66442139
Ref: reference/datamodel object __aexit__6442298
Ref: 151e6442298
Node: 執行模型6442789
Ref: reference/executionmodel doc6442911
Ref: 1ea76442911
Ref: reference/executionmodel execmodel6442911
Ref: 1ea86442911
Ref: reference/executionmodel execution-model6442911
Ref: 1ea96442911
Node: Structure of a program6443013
Ref: reference/executionmodel prog-structure6443111
Ref: 1eaa6443111
Ref: reference/executionmodel structure-of-a-program6443111
Ref: 1eab6443111
Node: Naming and binding6444151
Ref: reference/executionmodel naming6444264
Ref: 1de96444264
Ref: reference/executionmodel naming-and-binding6444264
Ref: 1eac6444264
Node: Binding of names6444488
Ref: reference/executionmodel bind-names6444587
Ref: 1ead6444587
Ref: reference/executionmodel binding-of-names6444587
Ref: 1eae6444587
Node: Resolution of names6446351
Ref: reference/executionmodel resolution-of-names6446476
Ref: 1eb06446476
Ref: reference/executionmodel resolve-names6446476
Ref: 1eb16446476
Node: Annotation scopes6450354
Ref: reference/executionmodel annotation-scopes6450478
Ref: 16e6450478
Ref: reference/executionmodel id16450478
Ref: 1eb36450478
Ref: Annotation scopes-Footnote-16453119
Ref: Annotation scopes-Footnote-26453161
Ref: Annotation scopes-Footnote-36453203
Node: Lazy evaluation6453245
Ref: reference/executionmodel id26453383
Ref: 1eb56453383
Ref: reference/executionmodel lazy-evaluation6453383
Ref: 3fd6453383
Node: Builtins and restricted execution6455023
Ref: reference/executionmodel builtins-and-restricted-execution6455177
Ref: 1eb66455177
Ref: reference/executionmodel restrict-exec6455177
Ref: 1eb76455177
Node: Interaction with dynamic features6456010
Ref: reference/executionmodel dynamic-features6456140
Ref: 1eb86456140
Ref: reference/executionmodel interaction-with-dynamic-features6456140
Ref: 1eb96456140
Ref: Interaction with dynamic features-Footnote-16456933
Node: 例外6457071
Ref: reference/executionmodel exceptions6457153
Ref: 1eba6457153
Ref: reference/executionmodel id46457153
Ref: 1ebb6457153
Node: 模組引入系統6459334
Ref: reference/import doc6459453
Ref: 1ebc6459453
Ref: reference/import importsystem6459453
Ref: 1e016459453
Ref: reference/import the-import-system6459453
Ref: 1ebd6459453
Ref: 模組引入系統-Footnote-16462068
Ref: 模組引入系統-Footnote-26462115
Ref: 模組引入系統-Footnote-36462157
Node: importlib<10>6462199
Ref: reference/import importlib6462282
Ref: 1ebf6462282
Node: 套件6462657
Ref: reference/import packages6462758
Ref: 1ec06462758
Node: Regular packages6464151
Ref: reference/import regular-packages6464237
Ref: 1ec26464237
Node: Namespace packages6465447
Ref: reference/import namespace-packages6465533
Ref: 1ec46465533
Ref: Namespace packages-Footnote-16466910
Node: Searching6466952
Ref: reference/import searching6467047
Ref: 1ec66467047
Node: The module cache6467872
Ref: reference/import the-module-cache6467962
Ref: 1ec76467962
Node: Finders and loaders6469524
Ref: reference/import finders-and-loaders6469635
Ref: 1ec86469635
Ref: reference/import id26469635
Ref: 1ec96469635
Node: Import hooks6471384
Ref: reference/import import-hooks6471492
Ref: 1ecd6471492
Node: The meta path6472364
Ref: reference/import the-meta-path6472444
Ref: 1ece6472444
Node: Loading6475647
Ref: reference/import loading6475757
Ref: 1ed06475757
Ref: Loading-Footnote-16478875
Node: Loaders6479255
Ref: reference/import loaders6479324
Ref: 1ed26479324
Node: 子模組6482560
Ref: reference/import submodules6482649
Ref: 1ed36482649
Node: Module spec6483868
Ref: reference/import module-spec6483982
Ref: 1ed46483982
Node: Import-related module attributes6484819
Ref: reference/import import-mod-attrs6484939
Ref: 1ed16484939
Ref: reference/import import-related-module-attributes6484939
Ref: 1ed56484939
Ref: reference/import name__6485327
Ref: 13166485327
Ref: reference/import loader__6485522
Ref: fc16485522
Ref: reference/import package__6486145
Ref: fc06486145
Ref: reference/import spec__6487289
Ref: 1ed66487289
Ref: reference/import path__6487891
Ref: 1b726487891
Ref: reference/import file__6488378
Ref: 1e026488378
Ref: reference/import cached__6488400
Ref: 114d6488400
Ref: Import-related module attributes-Footnote-16489860
Ref: Import-related module attributes-Footnote-26489902
Ref: Import-related module attributes-Footnote-36489944
Node: module __path__6489986
Ref: reference/import module-path6490107
Ref: 1edb6490107
Ref: reference/import package-path-rules6490107
Ref: 1eda6490107
Ref: module __path__-Footnote-16491279
Ref: module __path__-Footnote-26491321
Node: Module reprs6491363
Ref: reference/import module-reprs6491480
Ref: 1edc6491480
Node: Cached bytecode invalidation6492864
Ref: reference/import cached-bytecode-invalidation6492957
Ref: 1edd6492957
Ref: reference/import pyc-invalidation6492957
Ref: 5906492957
Node: The Path Based Finder6494294
Ref: reference/import the-path-based-finder6494431
Ref: 1ede6494431
Node: Path entry finders6496934
Ref: reference/import path-entry-finders6497045
Ref: 1ee06497045
Node: Path entry finder protocol6501960
Ref: reference/import path-entry-finder-protocol6502071
Ref: 1ee26502071
Node: Replacing the standard import system6504438
Ref: reference/import replacing-the-standard-import-system6504592
Ref: 1ee36504592
Node: Package Relative Imports6505595
Ref: reference/import package-relative-imports6505763
Ref: 1ee46505763
Ref: reference/import relativeimports6505763
Ref: 1ee56505763
Node: Special considerations for __main__6506966
Ref: reference/import import-dunder-main6507108
Ref: 1ee66507108
Ref: reference/import special-considerations-for-main6507108
Ref: 1ee76507108
Node: __main__ __spec__6507706
Ref: reference/import id46507795
Ref: 1ee86507795
Ref: reference/import main-spec6507795
Ref: 1ed96507795
Node: References6509190
Ref: reference/import references6509299
Ref: 1ee96509299
Ref: References-Footnote-16510541
Ref: References-Footnote-26510593
Ref: References-Footnote-36510635
Ref: References-Footnote-46510677
Ref: References-Footnote-56510719
Ref: References-Footnote-66510761
Ref: References-Footnote-76510803
Ref: References-Footnote-86510845
Ref: References-Footnote-96510887
Ref: References-Footnote-106510929
Node: 運算式6510972
Ref: reference/expressions doc6511094
Ref: 1eea6511094
Ref: reference/expressions expressions6511094
Ref: 1eeb6511094
Ref: reference/expressions id16511094
Ref: 1eec6511094
Ref: reference/expressions grammar-token-python-grammar-name6511381
Ref: 1eed6511381
Node: Arithmetic conversions6511947
Ref: reference/expressions arithmetic-conversions6512029
Ref: 1eee6512029
Ref: reference/expressions conversions6512029
Ref: 1eef6512029
Node: Atoms6512724
Ref: reference/expressions atoms6512824
Ref: 1ef06512824
Ref: reference/expressions id26512824
Ref: 1ef16512824
Ref: reference/expressions grammar-token-python-grammar-atom6513071
Ref: 1ef26513071
Ref: reference/expressions grammar-token-python-grammar-enclosure6513123
Ref: 1ef36513123
Node: Identifiers Names6513550
Ref: reference/expressions atom-identifiers6513629
Ref: 1d926513629
Ref: reference/expressions identifiers-names6513629
Ref: 1ef46513629
Ref: reference/expressions private-name-mangling6514068
Ref: 1bbd6514068
Node: Private name mangling6514104
Ref: reference/expressions id36514179
Ref: 1ef56514179
Node: Literals<2>6515956
Ref: reference/expressions atom-literals6516063
Ref: 1ef66516063
Ref: reference/expressions literals6516063
Ref: 1ef76516063
Ref: reference/expressions grammar-token-python-grammar-literal6516171
Ref: 1ef86516171
Node: Parenthesized forms6516876
Ref: reference/expressions parenthesized6517006
Ref: 1ef96517006
Ref: reference/expressions parenthesized-forms6517006
Ref: 1efa6517006
Ref: reference/expressions grammar-token-python-grammar-parenth_form6517141
Ref: 1efb6517141
Node: Displays for lists sets and dictionaries6517891
Ref: reference/expressions comprehensions6518023
Ref: 5746518023
Ref: reference/expressions displays-for-lists-sets-and-dictionaries6518023
Ref: 1efc6518023
Ref: reference/expressions grammar-token-python-grammar-comprehension6518465
Ref: 1efd6518465
Ref: reference/expressions grammar-token-python-grammar-comp_for6518519
Ref: 1efe6518519
Ref: reference/expressions grammar-token-python-grammar-comp_iter6518595
Ref: 1eff6518595
Ref: reference/expressions grammar-token-python-grammar-comp_if6518637
Ref: 1f006518637
Ref: Displays for lists sets and dictionaries-Footnote-16521103
Node: List displays6521145
Ref: reference/expressions list-displays6521270
Ref: 1f016521270
Ref: reference/expressions lists6521270
Ref: 1f026521270
Ref: reference/expressions grammar-token-python-grammar-list_display6521402
Ref: 1f036521402
Node: Set displays6521848
Ref: reference/expressions set6521952
Ref: 1f046521952
Ref: reference/expressions set-displays6521952
Ref: 1f056521952
Ref: reference/expressions grammar-token-python-grammar-set_display6522132
Ref: 1f066522132
Node: Dictionary displays6522664
Ref: reference/expressions dict6522776
Ref: d256522776
Ref: reference/expressions dictionary-displays6522776
Ref: 1f076522776
Ref: reference/expressions grammar-token-python-grammar-dict_display6522940
Ref: 1f086522940
Ref: reference/expressions grammar-token-python-grammar-dict_item_list6523014
Ref: 1f096523014
Ref: reference/expressions grammar-token-python-grammar-dict_item6523075
Ref: 1f0a6523075
Ref: reference/expressions grammar-token-python-grammar-dict_comprehension6523144
Ref: 1f0b6523144
Ref: Dictionary displays-Footnote-16524930
Ref: Dictionary displays-Footnote-26524972
Node: Generator expressions6525014
Ref: reference/expressions generator-expressions6525131
Ref: 1f0c6525131
Ref: reference/expressions genexpr6525131
Ref: 1f0d6525131
Ref: reference/expressions grammar-token-python-grammar-generator_expression6525264
Ref: 1f0e6525264
Node: Yield expressions6527206
Ref: reference/expressions yield-expressions6527295
Ref: 1f0f6527295
Ref: reference/expressions yieldexpr6527295
Ref: 1f106527295
Ref: reference/expressions grammar-token-python-grammar-yield_atom6527350
Ref: 1f116527350
Ref: reference/expressions grammar-token-python-grammar-yield_from6527401
Ref: 1f126527401
Ref: reference/expressions grammar-token-python-grammar-yield_expression6527453
Ref: 1f136527453
Ref: Yield expressions-Footnote-16532430
Ref: Yield expressions-Footnote-26532472
Ref: Yield expressions-Footnote-36532514
Ref: Yield expressions-Footnote-46532556
Ref: Yield expressions-Footnote-56532598
Node: Generator-iterator methods6532640
Ref: reference/expressions generator-iterator-methods6532738
Ref: 1f176532738
Ref: reference/expressions generator-methods6532738
Ref: 1ea06532738
Ref: reference/expressions generator __next__6533080
Ref: 1bc86533080
Ref: reference/expressions generator send6533841
Ref: 1ea26533841
Ref: reference/expressions generator throw6534419
Ref: 4a06534419
Ref: reference/expressions generator close6535704
Ref: 15ee6535704
Node: 模組<3>6536587
Ref: reference/expressions examples6536729
Ref: 1f186536729
Node: Asynchronous generator functions<2>6537776
Ref: reference/expressions asynchronous-generator-functions6537931
Ref: 1f156537931
Ref: reference/expressions id46537931
Ref: 1f196537931
Ref: Asynchronous generator functions<2>-Footnote-16541597
Node: Asynchronous generator-iterator methods6541677
Ref: reference/expressions asynchronous-generator-iterator-methods6541814
Ref: 1f1b6541814
Ref: reference/expressions asynchronous-generator-methods6541814
Ref: 1f1c6541814
Ref: reference/expressions agen __anext__6542056
Ref: 1f1a6542056
Ref: reference/expressions agen asend6542987
Ref: 87e6542987
Ref: reference/expressions agen athrow6543846
Ref: 4a16543846
Ref: reference/expressions agen aclose6544725
Ref: 87d6544725
Node: Primaries6545741
Ref: reference/expressions id56545835
Ref: 1f1d6545835
Ref: reference/expressions primaries6545835
Ref: 1f1e6545835
Ref: reference/expressions grammar-token-python-grammar-primary6545957
Ref: 1f1f6545957
Node: Attribute references6546103
Ref: reference/expressions attribute-references6546191
Ref: 1f206546191
Ref: reference/expressions id66546191
Ref: 1f216546191
Ref: reference/expressions grammar-token-python-grammar-attributeref6546320
Ref: 1f226546320
Node: Subscriptions6547111
Ref: reference/expressions id76547216
Ref: 1f236547216
Ref: reference/expressions subscriptions6547216
Ref: 1e5b6547216
Ref: reference/expressions grammar-token-python-grammar-subscription6547487
Ref: 1f246547487
Node: Slicings6549924
Ref: reference/expressions id86550014
Ref: 1f256550014
Ref: reference/expressions slicings6550014
Ref: 1f266550014
Ref: reference/expressions grammar-token-python-grammar-slicing6550263
Ref: 1f276550263
Ref: reference/expressions grammar-token-python-grammar-slice_list6550312
Ref: 1f286550312
Ref: reference/expressions grammar-token-python-grammar-slice_item6550369
Ref: 1f296550369
Ref: reference/expressions grammar-token-python-grammar-proper_slice6550417
Ref: 1f2a6550417
Ref: reference/expressions grammar-token-python-grammar-lower_bound6550488
Ref: 1f2b6550488
Ref: reference/expressions grammar-token-python-grammar-upper_bound6550521
Ref: 1f2c6550521
Ref: reference/expressions grammar-token-python-grammar-stride6550554
Ref: 1f2d6550554
Node: Calls6551783
Ref: reference/expressions calls6551851
Ref: d236551851
Ref: reference/expressions id96551851
Ref: 1f2e6551851
Ref: reference/expressions grammar-token-python-grammar-call6551999
Ref: 1f306551999
Ref: reference/expressions grammar-token-python-grammar-argument_list6552083
Ref: 1f316552083
Ref: reference/expressions grammar-token-python-grammar-positional_arguments6552347
Ref: 1f326552347
Ref: reference/expressions grammar-token-python-grammar-positional_item6552416
Ref: 1f336552416
Ref: reference/expressions grammar-token-python-grammar-starred_and_keywords6552485
Ref: 1f346552485
Ref: reference/expressions grammar-token-python-grammar-keywords_arguments6552618
Ref: 1f356552618
Ref: reference/expressions grammar-token-python-grammar-keyword_item6552753
Ref: 1f366552753
Ref: Calls-Footnote-16559324
Node: Await expression6559366
Ref: reference/expressions await6559473
Ref: 19f6559473
Ref: reference/expressions await-expression6559473
Ref: 1f376559473
Ref: reference/expressions grammar-token-python-grammar-await_expr6559662
Ref: 1f386559662
Node: The power operator6559722
Ref: reference/expressions power6559859
Ref: 1f396559859
Ref: reference/expressions the-power-operator6559859
Ref: 1f3a6559859
Ref: reference/expressions grammar-token-python-grammar-power6560056
Ref: 1f3b6560056
Node: Unary arithmetic and bitwise operations6561215
Ref: reference/expressions unary6561364
Ref: 1f3c6561364
Ref: reference/expressions unary-arithmetic-and-bitwise-operations6561364
Ref: 1f3d6561364
Ref: reference/expressions grammar-token-python-grammar-u_expr6561526
Ref: 1f3e6561526
Node: Binary arithmetic operations6562286
Ref: reference/expressions binary6562436
Ref: 1f3f6562436
Ref: reference/expressions binary-arithmetic-operations6562436
Ref: 1f406562436
Ref: reference/expressions grammar-token-python-grammar-m_expr6562780
Ref: 1f416562780
Ref: reference/expressions grammar-token-python-grammar-a_expr6562936
Ref: 1f426562936
Ref: Binary arithmetic operations-Footnote-16566626
Ref: Binary arithmetic operations-Footnote-26567239
Node: Shifting operations6567520
Ref: reference/expressions shifting6567656
Ref: 1f446567656
Ref: reference/expressions shifting-operations6567656
Ref: 1f456567656
Ref: reference/expressions grammar-token-python-grammar-shift_expr6567786
Ref: 1f466567786
Node: Binary bitwise operations6568407
Ref: reference/expressions binary-bitwise-operations6568526
Ref: 1f476568526
Ref: reference/expressions bitwise6568526
Ref: 1f486568526
Ref: reference/expressions grammar-token-python-grammar-and_expr6568661
Ref: 1f496568661
Ref: reference/expressions grammar-token-python-grammar-xor_expr6568716
Ref: 1f4a6568716
Ref: reference/expressions grammar-token-python-grammar-or_expr6568767
Ref: 1f4b6568767
Node: Comparisons6569451
Ref: reference/expressions comparisons6569569
Ref: 1f4c6569569
Ref: reference/expressions id126569569
Ref: 1f4d6569569
Ref: reference/expressions grammar-token-python-grammar-comparison6569864
Ref: 1f4e6569864
Ref: reference/expressions grammar-token-python-grammar-comp_operator6569920
Ref: 1f4f6569920
Node: Value comparisons6571008
Ref: reference/expressions expressions-value-comparisons6571108
Ref: 177e6571108
Ref: reference/expressions value-comparisons6571108
Ref: 1f506571108
Ref: reference/expressions in6578966
Ref: 2c56578966
Ref: reference/expressions not-in6578966
Ref: 5d56578966
Ref: Value comparisons-Footnote-16579004
Ref: Value comparisons-Footnote-26579046
Node: Membership test operations6580143
Ref: reference/expressions membership-test-details6580272
Ref: 1e696580272
Ref: reference/expressions membership-test-operations6580272
Ref: 1f516580272
Ref: reference/expressions is6582166
Ref: 2c66582166
Node: Identity comparisons6582166
Ref: reference/expressions identity-comparisons6582269
Ref: 1f526582269
Ref: reference/expressions is-not6582269
Ref: 1f536582269
Ref: reference/expressions booleans6582611
Ref: 1f546582611
Ref: reference/expressions and6582611
Ref: 2c26582611
Ref: reference/expressions or6582611
Ref: 2c76582611
Ref: Identity comparisons-Footnote-16582649
Node: Boolean operations6582951
Ref: reference/expressions boolean-operations6583069
Ref: 1f556583069
Ref: reference/expressions not6583069
Ref: 1f566583069
Ref: reference/expressions grammar-token-python-grammar-or_test6583122
Ref: 1f576583122
Ref: reference/expressions grammar-token-python-grammar-and_test6583173
Ref: 1f586583173
Ref: reference/expressions grammar-token-python-grammar-not_test6583226
Ref: 1f596583226
Node: Assignment expressions<2>6584668
Ref: reference/expressions assignment-expressions6584798
Ref: 1f5a6584798
Ref: reference/expressions grammar-token-python-grammar-assignment_expression6584859
Ref: 1eb46584859
Ref: Assignment expressions<2>-Footnote-16585902
Node: Conditional expressions6585944
Ref: reference/expressions conditional-expressions6586063
Ref: 1f5c6586063
Ref: reference/expressions if-expr6586063
Ref: 1f5d6586063
Ref: reference/expressions grammar-token-python-grammar-conditional_expression6586126
Ref: 1f5e6586126
Ref: reference/expressions grammar-token-python-grammar-expression6586199
Ref: 1f5b6586199
Ref: reference/expressions lambdas6586651
Ref: 1f5f6586651
Ref: Conditional expressions-Footnote-16586689
Node: Lambdas6586731
Ref: reference/expressions id156586841
Ref: 1f606586841
Ref: reference/expressions lambda6586841
Ref: 12346586841
Ref: reference/expressions grammar-token-python-grammar-lambda_expr6586872
Ref: 1f616586872
Node: Expression lists6587397
Ref: reference/expressions expression-lists6587500
Ref: 1f626587500
Ref: reference/expressions exprlists6587500
Ref: d246587500
Ref: reference/expressions grammar-token-python-grammar-expression_list6587549
Ref: 1f166587549
Ref: reference/expressions grammar-token-python-grammar-starred_list6587612
Ref: 1f636587612
Ref: reference/expressions grammar-token-python-grammar-starred_expression6587679
Ref: 1f646587679
Ref: reference/expressions grammar-token-python-grammar-starred_item6587755
Ref: 1f656587755
Ref: Expression lists-Footnote-16588718
Node: Evaluation order6588760
Ref: reference/expressions evalorder6588875
Ref: 1f666588875
Ref: reference/expressions evaluation-order6588875
Ref: 1f676588875
Node: Operator precedence6589390
Ref: reference/expressions operator-precedence6589480
Ref: 1f686589480
Ref: reference/expressions operator-summary6589480
Ref: 1f696589480
Ref: Operator precedence-Footnote-16594004
Ref: Operator precedence-Footnote-26594153
Node: 簡單陳述式6594247
Ref: reference/simple_stmts doc6594366
Ref: 1f6a6594366
Ref: reference/simple_stmts simple6594366
Ref: 1f6b6594366
Ref: reference/simple_stmts simple-statements6594366
Ref: 1f6c6594366
Ref: reference/simple_stmts grammar-token-python-grammar-simple_stmt6594581
Ref: 1f6d6594581
Node: Expression statements6595548
Ref: reference/simple_stmts expression-statements6595651
Ref: 1f6e6595651
Ref: reference/simple_stmts exprstmts6595651
Ref: 1f6f6595651
Ref: reference/simple_stmts grammar-token-python-grammar-expression_stmt6596041
Ref: 1f706596041
Node: Assignment statements6596468
Ref: reference/simple_stmts assignment6596596
Ref: 1eaf6596596
Ref: reference/simple_stmts assignment-statements6596596
Ref: 1f716596596
Ref: reference/simple_stmts grammar-token-python-grammar-assignment_stmt6596767
Ref: 1f726596767
Ref: reference/simple_stmts grammar-token-python-grammar-target_list6596851
Ref: 1f736596851
Ref: reference/simple_stmts grammar-token-python-grammar-target6596903
Ref: 1f746596903
Ref: reference/simple_stmts attr-target-note6600342
Ref: 1f756600342
Ref: Assignment statements-Footnote-16604382
Node: Augmented assignment statements6604424
Ref: reference/simple_stmts augassign6604553
Ref: 1f766604553
Ref: reference/simple_stmts augmented-assignment-statements6604553
Ref: 1f776604553
Ref: reference/simple_stmts grammar-token-python-grammar-augmented_assignment_stmt6604750
Ref: 1f786604750
Ref: reference/simple_stmts grammar-token-python-grammar-augtarget6604838
Ref: 1f796604838
Ref: reference/simple_stmts grammar-token-python-grammar-augop6604924
Ref: 1f7a6604924
Node: Annotated assignment statements6606665
Ref: reference/simple_stmts annassign6606794
Ref: 1f7b6606794
Ref: reference/simple_stmts annotated-assignment-statements6606794
Ref: 1f7c6606794
Ref: reference/simple_stmts grammar-token-python-grammar-annotated_assignment_stmt6607029
Ref: 1f7d6607029
Ref: Annotated assignment statements-Footnote-16609135
Ref: Annotated assignment statements-Footnote-26609177
Node: assert 陳述式6609219
Ref: reference/simple_stmts assert6609343
Ref: 90c6609343
Ref: reference/simple_stmts the-assert-statement6609343
Ref: 1f7e6609343
Ref: reference/simple_stmts grammar-token-python-grammar-assert_stmt6609482
Ref: 1f7f6609482
Node: pass 陳述式<2>6610565
Ref: reference/simple_stmts pass6610684
Ref: 1b1e6610684
Ref: reference/simple_stmts the-pass-statement6610684
Ref: 1f806610684
Ref: reference/simple_stmts grammar-token-python-grammar-pass_stmt6610732
Ref: 1f816610732
Node: del 陳述式<2>6611082
Ref: reference/simple_stmts del6611201
Ref: 16a96611201
Ref: reference/simple_stmts the-del-statement6611201
Ref: 1f826611201
Ref: reference/simple_stmts grammar-token-python-grammar-del_stmt6611247
Ref: 1f836611247
Node: return 陳述式6612165
Ref: reference/simple_stmts return6612282
Ref: 9726612282
Ref: reference/simple_stmts the-return-statement6612282
Ref: 1f846612282
Ref: reference/simple_stmts grammar-token-python-grammar-return_stmt6612334
Ref: 1f856612334
Node: yield 陳述式6613466
Ref: reference/simple_stmts the-yield-statement6613582
Ref: 1f866613582
Ref: reference/simple_stmts yield6613582
Ref: 9716613582
Ref: reference/simple_stmts grammar-token-python-grammar-yield_stmt6613632
Ref: 1f876613632
Node: raise 陳述式6614468
Ref: reference/simple_stmts raise6614583
Ref: 5916614583
Ref: reference/simple_stmts the-raise-statement6614583
Ref: 1f886614583
Ref: reference/simple_stmts grammar-token-python-grammar-raise_stmt6614633
Ref: 1f896614633
Node: break 陳述式6618826
Ref: reference/simple_stmts break6618944
Ref: a4c6618944
Ref: reference/simple_stmts the-break-statement6618944
Ref: 1f8c6618944
Ref: reference/simple_stmts grammar-token-python-grammar-break_stmt6618994
Ref: 1f8d6618994
Node: continue 陳述式6619588
Ref: reference/simple_stmts continue6619707
Ref: 96d6619707
Ref: reference/simple_stmts the-continue-statement6619707
Ref: 1f8e6619707
Ref: reference/simple_stmts grammar-token-python-grammar-continue_stmt6619765
Ref: 1f8f6619765
Ref: reference/simple_stmts import6620231
Ref: 5866620231
Node: import 陳述式6620233
Ref: reference/simple_stmts from6620353
Ref: 12426620353
Ref: reference/simple_stmts the-import-statement6620353
Ref: 1f906620353
Ref: reference/simple_stmts grammar-token-python-grammar-import_stmt6620407
Ref: 1f916620407
Ref: reference/simple_stmts grammar-token-python-grammar-module6620873
Ref: 1f926620873
Ref: reference/simple_stmts grammar-token-python-grammar-relative_module6620927
Ref: 1f936620927
Node: Future statements6626252
Ref: reference/simple_stmts future6626322
Ref: 16f6626322
Ref: reference/simple_stmts future-statements6626322
Ref: 1f946626322
Ref: reference/simple_stmts grammar-token-python-grammar-future_stmt6626848
Ref: 1f956626848
Ref: reference/simple_stmts grammar-token-python-grammar-feature6627124
Ref: 1f966627124
Ref: Future statements-Footnote-16629838
Ref: Future statements-Footnote-26629880
Node: global 陳述式6629922
Ref: reference/simple_stmts global6630042
Ref: 1706630042
Ref: reference/simple_stmts the-global-statement6630042
Ref: 1f976630042
Ref: reference/simple_stmts grammar-token-python-grammar-global_stmt6630096
Ref: 1f986630096
Node: nonlocal 陳述式6631702
Ref: reference/simple_stmts nonlocal6631820
Ref: 123e6631820
Ref: reference/simple_stmts the-nonlocal-statement6631820
Ref: 1f996631820
Ref: reference/simple_stmts grammar-token-python-grammar-nonlocal_stmt6631878
Ref: 1f9a6631878
Ref: nonlocal 陳述式-Footnote-16633048
Node: type 陳述式6633090
Ref: reference/simple_stmts the-type-statement6633183
Ref: 1f9b6633183
Ref: reference/simple_stmts type6633183
Ref: 3de6633183
Ref: reference/simple_stmts grammar-token-python-grammar-type_stmt6633233
Ref: 1f9c6633233
Ref: type 陳述式-Footnote-16634521
Node: 複合陳述式6634563
Ref: reference/compound_stmts doc6634691
Ref: 1f9d6634691
Ref: reference/compound_stmts compound6634691
Ref: 1f9e6634691
Ref: reference/compound_stmts compound-statements6634691
Ref: 1f9f6634691
Ref: reference/compound_stmts grammar-token-python-grammar-compound_stmt6636437
Ref: 1fa06636437
Ref: reference/compound_stmts grammar-token-python-grammar-suite6636830
Ref: 1fa16636830
Ref: reference/compound_stmts grammar-token-python-grammar-statement6636906
Ref: 1fa26636906
Ref: reference/compound_stmts grammar-token-python-grammar-stmt_list6636963
Ref: 1fa36636963
Ref: reference/compound_stmts if6637484
Ref: 2c46637484
Ref: reference/compound_stmts elif6637484
Ref: 1b116637484
Node: The if statement6637711
Ref: reference/compound_stmts else6637807
Ref: 1726637807
Ref: reference/compound_stmts the-if-statement6637807
Ref: 1fa46637807
Ref: reference/compound_stmts grammar-token-python-grammar-if_stmt6637927
Ref: 1fa56637927
Node: The while statement6638474
Ref: reference/compound_stmts the-while-statement6638596
Ref: 1fa66638596
Ref: reference/compound_stmts while6638596
Ref: 1b0b6638596
Ref: reference/compound_stmts grammar-token-python-grammar-while_stmt6638756
Ref: 1fa76638756
Node: The for statement6639354
Ref: reference/compound_stmts for6639477
Ref: 2c36639477
Ref: reference/compound_stmts the-for-statement6639477
Ref: 1fa86639477
Ref: reference/compound_stmts grammar-token-python-grammar-for_stmt6639676
Ref: 1fa96639676
Node: The try statement6641426
Ref: reference/compound_stmts the-try-statement6641548
Ref: 1faa6641548
Ref: reference/compound_stmts try6641548
Ref: 68c6641548
Ref: reference/compound_stmts grammar-token-python-grammar-try_stmt6641706
Ref: 1fab6641706
Ref: reference/compound_stmts grammar-token-python-grammar-try1_stmt6641759
Ref: 1fac6641759
Ref: reference/compound_stmts grammar-token-python-grammar-try2_stmt6641945
Ref: 1fad6641945
Ref: reference/compound_stmts grammar-token-python-grammar-try3_stmt6642133
Ref: 1fae6642133
Node: except clause6642504
Ref: reference/compound_stmts except6642594
Ref: 1716642594
Ref: reference/compound_stmts except-clause6642594
Ref: 1faf6642594
Ref: except clause-Footnote-16645840
Node: except* 子句6646038
Ref: reference/compound_stmts except-star6646148
Ref: 55c6646148
Ref: reference/compound_stmts id26646148
Ref: 1fb06646148
Node: else clause6648554
Ref: reference/compound_stmts else-clause6648665
Ref: 1fb16648665
Ref: reference/compound_stmts except-else6648665
Ref: 1fb26648665
Node: finally clause6649026
Ref: reference/compound_stmts finally6649114
Ref: 96e6649114
Ref: reference/compound_stmts finally-clause6649114
Ref: 1fb36649114
Ref: reference/compound_stmts with6650863
Ref: 5776650863
Node: The with statement6650863
Ref: reference/compound_stmts as6650987
Ref: 1fb46650987
Ref: reference/compound_stmts the-with-statement6650987
Ref: 1fb56650987
Ref: reference/compound_stmts grammar-token-python-grammar-with_stmt6651354
Ref: 1fb66651354
Ref: reference/compound_stmts grammar-token-python-grammar-with_stmt_contents6651456
Ref: 1fb76651456
Ref: reference/compound_stmts grammar-token-python-grammar-with_item6651511
Ref: 1fb86651511
Ref: The with statement-Footnote-16654702
Node: The match statement6654744
Ref: reference/compound_stmts match6654863
Ref: 7b16654863
Ref: reference/compound_stmts the-match-statement6654863
Ref: 1fb96654863
Ref: reference/compound_stmts grammar-token-python-grammar-match_stmt6655008
Ref: 1fba6655008
Ref: reference/compound_stmts grammar-token-python-grammar-subject_expr6655089
Ref: 1fbb6655089
Ref: reference/compound_stmts grammar-token-python-grammar-case_block6655202
Ref: 1fbc6655202
Ref: The match statement-Footnote-16656074
Ref: The match statement-Footnote-26656116
Node: Overview6656158
Ref: reference/compound_stmts overview6656237
Ref: 1fbd6656237
Node: Guards6658711
Ref: reference/compound_stmts guards6658822
Ref: 1fbf6658822
Ref: reference/compound_stmts grammar-token-python-grammar-guard6658853
Ref: 1fc06658853
Node: Irrefutable Case Blocks6659982
Ref: reference/compound_stmts irrefutable-case6660093
Ref: 1fc16660093
Ref: reference/compound_stmts irrefutable-case-blocks6660093
Ref: 1fc26660093
Node: Patterns6660798
Ref: reference/compound_stmts patterns6660894
Ref: 1fc66660894
Ref: reference/compound_stmts grammar-token-python-grammar-patterns6661220
Ref: 1fc76661220
Ref: reference/compound_stmts grammar-token-python-grammar-pattern6661276
Ref: 1fc86661276
Ref: reference/compound_stmts grammar-token-python-grammar-closed_pattern6661324
Ref: 1fc96661324
Node: OR Patterns6662236
Ref: reference/compound_stmts id36662312
Ref: 1fca6662312
Ref: reference/compound_stmts or-patterns6662312
Ref: 1fc46662312
Ref: reference/compound_stmts grammar-token-python-grammar-or_pattern6662436
Ref: 1fcb6662436
Node: AS Patterns6662990
Ref: reference/compound_stmts as-patterns6663091
Ref: 1fc36663091
Ref: reference/compound_stmts id46663091
Ref: 1fcc6663091
Ref: reference/compound_stmts grammar-token-python-grammar-as_pattern6663240
Ref: 1fcd6663240
Node: Literal Patterns6663596
Ref: reference/compound_stmts id56663702
Ref: 1fce6663702
Ref: reference/compound_stmts literal-patterns6663702
Ref: 1fcf6663702
Ref: reference/compound_stmts grammar-token-python-grammar-literal_pattern6663833
Ref: 1fd06663833
Ref: reference/compound_stmts grammar-token-python-grammar-signed_number6664114
Ref: 1fd16664114
Node: Capture Patterns6664798
Ref: reference/compound_stmts capture-patterns6664910
Ref: 1fc56664910
Ref: reference/compound_stmts id66664910
Ref: 1fd36664910
Ref: reference/compound_stmts grammar-token-python-grammar-capture_pattern6665024
Ref: 1fd46665024
Ref: Capture Patterns-Footnote-16665765
Node: Wildcard Patterns6665807
Ref: reference/compound_stmts id76665917
Ref: 1fd66665917
Ref: reference/compound_stmts wildcard-patterns6665917
Ref: 7b26665917
Ref: reference/compound_stmts grammar-token-python-grammar-wildcard_pattern6666052
Ref: 1fd56666052
Node: Value Patterns6666329
Ref: reference/compound_stmts id86666437
Ref: 1fd76666437
Ref: reference/compound_stmts value-patterns6666437
Ref: 1fd86666437
Ref: reference/compound_stmts grammar-token-python-grammar-value_pattern6666548
Ref: 1fd96666548
Ref: reference/compound_stmts grammar-token-python-grammar-attr6666576
Ref: 1fda6666576
Ref: reference/compound_stmts grammar-token-python-grammar-name_or_attr6666621
Ref: 1fdb6666621
Node: Group Patterns6667236
Ref: reference/compound_stmts group-patterns6667344
Ref: 1fdc6667344
Ref: reference/compound_stmts id96667344
Ref: 1fdd6667344
Ref: reference/compound_stmts grammar-token-python-grammar-group_pattern6667544
Ref: 1fde6667544
Node: Sequence Patterns6667643
Ref: reference/compound_stmts id106667753
Ref: 1fdf6667753
Ref: reference/compound_stmts sequence-patterns6667753
Ref: 1fe06667753
Ref: reference/compound_stmts grammar-token-python-grammar-sequence_pattern6667958
Ref: 1fe16667958
Ref: reference/compound_stmts grammar-token-python-grammar-open_sequence_pattern6668089
Ref: 1fe26668089
Ref: reference/compound_stmts grammar-token-python-grammar-maybe_sequence_pattern6668169
Ref: 1fe36668169
Ref: reference/compound_stmts grammar-token-python-grammar-maybe_star_pattern6668230
Ref: 1fe46668230
Ref: reference/compound_stmts grammar-token-python-grammar-star_pattern6668285
Ref: 1fe56668285
Ref: Sequence Patterns-Footnote-16671282
Node: Mapping Patterns6672001
Ref: reference/compound_stmts id126672111
Ref: 1fe66672111
Ref: reference/compound_stmts mapping-patterns6672111
Ref: 1fe76672111
Ref: reference/compound_stmts grammar-token-python-grammar-mapping_pattern6672293
Ref: 1fe86672293
Ref: reference/compound_stmts grammar-token-python-grammar-items_pattern6672346
Ref: 1fe96672346
Ref: reference/compound_stmts grammar-token-python-grammar-key_value_pattern6672403
Ref: 1fea6672403
Ref: reference/compound_stmts grammar-token-python-grammar-double_star_pattern6672529
Ref: 1feb6672529
Ref: Mapping Patterns-Footnote-16674124
Node: Class Patterns6674598
Ref: reference/compound_stmts class-patterns6674682
Ref: 1fec6674682
Ref: reference/compound_stmts id146674682
Ref: 1fed6674682
Ref: reference/compound_stmts grammar-token-python-grammar-class_pattern6674827
Ref: 1fee6674827
Ref: reference/compound_stmts grammar-token-python-grammar-pattern_arguments6674902
Ref: 1fef6674902
Ref: reference/compound_stmts grammar-token-python-grammar-positional_patterns6675022
Ref: 1ff06675022
Ref: reference/compound_stmts grammar-token-python-grammar-keyword_patterns6675064
Ref: 1ff16675064
Ref: reference/compound_stmts grammar-token-python-grammar-keyword_pattern6675114
Ref: 1ff26675114
Ref: reference/compound_stmts function6679139
Ref: 1b3a6679139
Ref: Class Patterns-Footnote-16679175
Ref: Class Patterns-Footnote-26679217
Node: 函式定義6679259
Ref: reference/compound_stmts def6679372
Ref: 13c56679372
Ref: reference/compound_stmts function-definitions6679372
Ref: 1ff36679372
Ref: reference/compound_stmts grammar-token-python-grammar-funcdef6679516
Ref: 1ff46679516
Ref: reference/compound_stmts grammar-token-python-grammar-decorators6679681
Ref: 1ff56679681
Ref: reference/compound_stmts grammar-token-python-grammar-decorator6679727
Ref: 1ff66679727
Ref: reference/compound_stmts grammar-token-python-grammar-parameter_list6679796
Ref: 1ff76679796
Ref: reference/compound_stmts grammar-token-python-grammar-parameter_list_no_posonly6679971
Ref: 1ff86679971
Ref: reference/compound_stmts grammar-token-python-grammar-parameter_list_starargs6680132
Ref: 1ff96680132
Ref: reference/compound_stmts grammar-token-python-grammar-parameter6680290
Ref: 1ffa6680290
Ref: reference/compound_stmts grammar-token-python-grammar-defparameter6680353
Ref: 1ffb6680353
Ref: reference/compound_stmts grammar-token-python-grammar-funcname6680415
Ref: 1ffc6680415
Ref: 函式定義-Footnote-16687094
Ref: 函式定義-Footnote-26687291
Ref: 函式定義-Footnote-36687333
Ref: 函式定義-Footnote-46687375
Ref: 函式定義-Footnote-56687417
Ref: 函式定義-Footnote-66687459
Ref: 函式定義-Footnote-76687501
Ref: 函式定義-Footnote-86687543
Ref: 函式定義-Footnote-96687585
Node: 類別定義6687627
Ref: reference/compound_stmts class6687730
Ref: 126a6687730
Ref: reference/compound_stmts class-definitions6687730
Ref: 1ffe6687730
Ref: reference/compound_stmts grammar-token-python-grammar-classdef6687855
Ref: 1fff6687855
Ref: reference/compound_stmts grammar-token-python-grammar-inheritance6687945
Ref: 20006687945
Ref: reference/compound_stmts grammar-token-python-grammar-classname6687990
Ref: 20016687990
Ref: 類別定義-Footnote-16691252
Ref: 類別定義-Footnote-26691432
Ref: 類別定義-Footnote-36691474
Ref: 類別定義-Footnote-46691516
Ref: 類別定義-Footnote-56691558
Node: 協程<2>6691600
Ref: reference/compound_stmts async6691711
Ref: 6d66691711
Ref: reference/compound_stmts coroutines6691711
Ref: 20026691711
Node: 協程函式定義6691841
Ref: reference/compound_stmts async-def6691933
Ref: 5756691933
Ref: reference/compound_stmts coroutine-function-definition6691933
Ref: 20036691933
Ref: reference/compound_stmts grammar-token-python-grammar-async_funcdef6691982
Ref: 20046691982
Node: async for 陳述式6692884
Ref: reference/compound_stmts async-for6693005
Ref: a4e6693005
Ref: reference/compound_stmts the-async-for-statement6693005
Ref: 20056693005
Ref: reference/compound_stmts grammar-token-python-grammar-async_for_stmt6693067
Ref: 20066693067
Node: async with 陳述式6694002
Ref: reference/compound_stmts async-with6694096
Ref: 57a6694096
Ref: reference/compound_stmts the-async-with-statement6694096
Ref: 20076694096
Ref: reference/compound_stmts grammar-token-python-grammar-async_with_stmt6694160
Ref: 20086694160
Ref: async with 陳述式-Footnote-16695290
Node: Type parameter lists6695332
Ref: reference/compound_stmts type-parameter-lists6695422
Ref: 20096695422
Ref: reference/compound_stmts type-params6695422
Ref: 2946695422
Ref: reference/compound_stmts grammar-token-python-grammar-type_params6695582
Ref: 200a6695582
Ref: reference/compound_stmts grammar-token-python-grammar-type_param6695641
Ref: 200b6695641
Ref: reference/compound_stmts grammar-token-python-grammar-typevar6695698
Ref: 200c6695698
Ref: reference/compound_stmts grammar-token-python-grammar-typevartuple6695767
Ref: 200d6695767
Ref: reference/compound_stmts grammar-token-python-grammar-paramspec6695822
Ref: 200e6695822
Ref: Type parameter lists-Footnote-16700171
Node: Generic functions6700213
Ref: reference/compound_stmts generic-functions6700311
Ref: 3f96700311
Ref: reference/compound_stmts id176700311
Ref: 200f6700311
Node: Generic classes6702109
Ref: reference/compound_stmts generic-classes6702236
Ref: 3f86702236
Ref: reference/compound_stmts id186702236
Ref: 20106702236
Node: Generic type aliases6703360
Ref: reference/compound_stmts generic-type-aliases6703461
Ref: 3fc6703461
Ref: reference/compound_stmts id196703461
Ref: 20116703461
Node: 最高層級元件6704278
Ref: reference/toplevel_components doc6704415
Ref: 20126704415
Ref: reference/toplevel_components top-level6704415
Ref: 20136704415
Ref: reference/toplevel_components top-level-components6704415
Ref: 20146704415
Node: 完整的 Python 程式6704765
Ref: reference/toplevel_components complete-python-programs6704864
Ref: 20156704864
Ref: reference/toplevel_components programs6704864
Ref: 1ed86704864
Node: 檔案輸入6706183
Ref: reference/toplevel_components file-input6706306
Ref: 20166706306
Ref: reference/toplevel_components id16706306
Ref: 20176706306
Ref: reference/toplevel_components grammar-token-python-grammar-file_input6706412
Ref: 20186706412
Node: 互動式輸入6706663
Ref: reference/toplevel_components interactive6706778
Ref: 20196706778
Ref: reference/toplevel_components interactive-input6706778
Ref: 201a6706778
Ref: reference/toplevel_components grammar-token-python-grammar-interactive_input6706877
Ref: 201b6706877
Node: 運算式輸入6707102
Ref: reference/toplevel_components expression-input6707196
Ref: 201c6707196
Ref: reference/toplevel_components id26707196
Ref: 201d6707196
Ref: reference/toplevel_components grammar-token-python-grammar-eval_input6707385
Ref: 201e6707385
Node: 完整的語法規格書6707431
Ref: reference/grammar doc6707544
Ref: 1fd26707544
Ref: reference/grammar full-grammar-specification6707544
Ref: 201f6707544
Ref: reference/grammar id16707544
Ref: 20206707544
Ref: 完整的語法規格書-Footnote-16779641
Ref: 完整的語法規格書-Footnote-26779713
Ref: 完整的語法規格書-Footnote-36779785
Ref: 完整的語法規格書-Footnote-46779850
Node: Python 標準函式庫 Standard Library6779892
Ref: library/index doc6780046
Ref: 20216780046
Ref: library/index library-index6780046
Ref: 12a6780046
Ref: library/index the-python-standard-library6780046
Ref: 20226780046
Ref: Python 標準函式庫 Standard Library-Footnote-16782688
Node: 簡介<6>6782713
Ref: library/intro doc6782819
Ref: 20236782819
Ref: library/intro introduction6782819
Ref: 20246782819
Ref: library/intro library-intro6782819
Ref: 20256782819
Node: 可用性之註釋6785332
Ref: library/intro availability6785396
Ref: 1c566785396
Ref: library/intro notes-on-availability6785396
Ref: 20266785396
Node: WebAssembly 平台6786080
Ref: library/intro wasm-availability6786165
Ref: 16e66786165
Ref: library/intro webassembly-platforms6786165
Ref: 20276786165
Ref: WebAssembly 平台-Footnote-16788670
Ref: WebAssembly 平台-Footnote-26788703
Ref: WebAssembly 平台-Footnote-36788735
Ref: WebAssembly 平台-Footnote-46788761
Ref: WebAssembly 平台-Footnote-56788793
Ref: WebAssembly 平台-Footnote-66788819
Ref: WebAssembly 平台-Footnote-76788849
Ref: WebAssembly 平台-Footnote-86788878
Ref: WebAssembly 平台-Footnote-96788908
Node: iOS6788968
Ref: library/intro ios6789053
Ref: 20286789053
Ref: library/intro ios-availability6789053
Ref: 1d566789053
Node: 內建函式6791157
Ref: library/functions doc6791284
Ref: 20296791284
Ref: library/functions built-in-funcs6791284
Ref: 11f56791284
Ref: library/functions built-in-functions6791284
Ref: 202a6791284
Ref: library/functions abs6794663
Ref: 1ba86794663
Ref: library/functions aiter6794870
Ref: 7796794870
Ref: library/functions all6795168
Ref: 138f6795168
Ref: library/functions anext6795475
Ref: 77a6795475
Ref: library/functions any6796111
Ref: 138e6796111
Ref: library/functions ascii6796438
Ref: 13546796438
Ref: library/functions bin6796780
Ref: 123f6796780
Ref: library/functions bool6797432
Ref: 40e6797432
Ref: library/functions breakpoint6798059
Ref: 2196798059
Ref: library/functions func-bytearray6799305
Ref: 19c06799305
Ref: library/functions func-bytes6800739
Ref: 19bf6800739
Ref: library/functions callable6801485
Ref: 115e6801485
Ref: library/functions chr6802050
Ref: 15686802050
Ref: library/functions classmethod6802448
Ref: 14a6802448
Ref: library/functions compile6804010
Ref: 1786804010
Ref: library/functions complex6807678
Ref: 2c96807678
Ref: library/functions grammar-token-float-complexvalue6809271
Ref: 203f6809271
Ref: library/functions delattr6810799
Ref: 202b6810799
Ref: library/functions func-dict6811204
Ref: 202c6811204
Ref: library/functions dir6811662
Ref: 5d86811662
Ref: library/functions divmod6814158
Ref: 9456814158
Ref: library/functions enumerate6814733
Ref: 13ea6814733
Ref: library/functions func-eval6815623
Ref: 20406815623
Ref: library/functions eval6815623
Ref: 1636815623
Ref: library/functions exec6818587
Ref: 1626818587
Ref: library/functions filter6822004
Ref: 8096822004
Ref: library/functions float6822796
Ref: 2c86822796
Ref: library/functions grammar-token-float-sign6823606
Ref: 20446823606
Ref: library/functions grammar-token-float-infinity6823644
Ref: 20456823644
Ref: library/functions grammar-token-float-nan6823691
Ref: 20466823691
Ref: library/functions grammar-token-float-digit6823725
Ref: 20476823725
Ref: library/functions grammar-token-float-digitpart6823827
Ref: 20486823827
Ref: library/functions grammar-token-float-number6823876
Ref: 20496823876
Ref: library/functions grammar-token-float-exponent6823948
Ref: 204a6823948
Ref: library/functions grammar-token-float-floatnumber6824005
Ref: 204b6824005
Ref: library/functions grammar-token-float-absfloatvalue6824051
Ref: 204c6824051
Ref: library/functions grammar-token-float-floatvalue6824108
Ref: 20436824108
Ref: library/functions format6825100
Ref: 5c36825100
Ref: library/functions func-frozenset6826055
Ref: 202d6826055
Ref: library/functions getattr6826554
Ref: b786826554
Ref: library/functions globals6827342
Ref: 176a6827342
Ref: library/functions hasattr6827557
Ref: 4796827557
Ref: library/functions hash6827870
Ref: 58f6827870
Ref: library/functions help6828341
Ref: 87c6828341
Ref: library/functions hex6829322
Ref: 12626829322
Ref: library/functions id6830358
Ref: 13906830358
Ref: library/functions input6830760
Ref: 126b6830760
Ref: library/functions int6831596
Ref: 23c6831596
Ref: library/functions isinstance6834687
Ref: 3e86834687
Ref: library/functions issubclass6835577
Ref: 7656835577
Ref: library/functions iter6836134
Ref: 77b6836134
Ref: library/functions len6837458
Ref: 5d46837458
Ref: library/functions func-list6837842
Ref: 202e6837842
Ref: library/functions locals6838070
Ref: 1276838070
Ref: library/functions map6840856
Ref: 8086840856
Ref: library/functions max6841383
Ref: ead6841383
Ref: library/functions func-memoryview6842542
Ref: 202f6842542
Ref: library/functions min6842729
Ref: eac6842729
Ref: library/functions next6843868
Ref: 77c6843868
Ref: library/functions object6844171
Ref: a2f6844171
Ref: library/functions oct6844540
Ref: 12616844540
Ref: library/functions open6845301
Ref: 4c06845301
Ref: library/functions filemodes6846745
Ref: 20526846745
Ref: library/functions open-newline-parameter6851794
Ref: 6e56851794
Ref: library/functions ord6856720
Ref: 1de16856720
Ref: library/functions pow6856994
Ref: 9766856994
Ref: library/functions print6858992
Ref: f186858992
Ref: library/functions property6860180
Ref: 1806860180
Ref: library/functions property getter6861860
Ref: 15506861860
Ref: library/functions property setter6861886
Ref: 15516861886
Ref: library/functions property deleter6861912
Ref: 15526861912
Ref: library/functions property __name__6863118
Ref: 17f6863118
Ref: library/functions func-range6863297
Ref: 20306863297
Ref: library/functions repr6863559
Ref: 7a16863559
Ref: library/functions reversed6864570
Ref: 80a6864570
Ref: library/functions round6864884
Ref: 126d6864884
Ref: library/functions func-set6866181
Ref: 20316866181
Ref: library/functions setattr6866653
Ref: 20326866653
Ref: library/functions slice6867726
Ref: 4106867726
Ref: library/functions slice start6867981
Ref: 1e2b6867981
Ref: library/functions slice stop6868005
Ref: 1e2c6868005
Ref: library/functions slice step6868028
Ref: 1e2d6868028
Ref: library/functions sorted6868767
Ref: b756868767
Ref: library/functions staticmethod6870396
Ref: 3586870396
Ref: library/functions func-str6872106
Ref: 20336872106
Ref: library/functions sum6872444
Ref: 4116872444
Ref: library/functions super6873275
Ref: 4836873275
Ref: library/functions func-tuple6877529
Ref: 20346877529
Ref: library/functions type6877773
Ref: cef6877773
Ref: library/functions vars6879482
Ref: 19486879482
Ref: library/functions zip6880451
Ref: 7746880451
Ref: library/functions import__6884321
Ref: 8796884321
Ref: 內建函式-Footnote-16887688
Ref: 內建函式-Footnote-26887868
Ref: 內建函式-Footnote-36887910
Ref: 內建函式-Footnote-46887952
Ref: 內建函式-Footnote-56887994
Ref: 內建函式-Footnote-66888036
Ref: 內建函式-Footnote-76888113
Ref: 內建函式-Footnote-86888161
Ref: 內建函式-Footnote-96888203
Node: 內建常數6888245
Ref: library/constants doc6888375
Ref: 205f6888375
Ref: library/constants built-in-constants6888375
Ref: 20606888375
Ref: library/constants built-in-consts6888375
Ref: 20616888375
Ref: library/constants False6888477
Ref: adb6888477
Ref: library/constants True6888643
Ref: bb46888643
Ref: library/constants None6888806
Ref: 61b6888806
Ref: library/constants NotImplemented6889168
Ref: 7766889168
Ref: library/constants Ellipsis6890865
Ref: 20626890865
Ref: library/constants debug__6891132
Ref: 77e6891132
Node: 由 site module（模組）所添增的常數6891651
Ref: library/constants constants-added-by-the-site-module6891745
Ref: 20636891745
Ref: library/constants site-consts6891745
Ref: 20646891745
Ref: library/constants quit6892138
Ref: 20656892138
Ref: library/constants exit6892167
Ref: 20666892167
Ref: library/constants copyright6892622
Ref: 20676892622
Ref: library/constants credits6892644
Ref: 20686892644
Ref: library/constants license6892750
Ref: 20696892750
Node: 內建型別6892961
Ref: library/stdtypes doc6893094
Ref: 206a6893094
Ref: library/stdtypes bltin-types6893094
Ref: 206b6893094
Ref: library/stdtypes built-in-types6893094
Ref: 206c6893094
Node: 真值檢測6894662
Ref: library/stdtypes truth6894772
Ref: 20356894772
Ref: library/stdtypes truth-value-testing6894772
Ref: 206d6894772
Ref: 真值檢測-Footnote-16895839
Node: Boolean（布林）運算 --- and or not6895975
Ref: library/stdtypes boolean6896106
Ref: 206e6896106
Ref: library/stdtypes boolean-operations-and-or-not6896106
Ref: 206f6896106
Node: 比較運算6897482
Ref: library/stdtypes comparisons6897639
Ref: 20706897639
Ref: library/stdtypes stdcomparisons6897639
Ref: 20716897639
Node: 數值型別 --- int、float、complex6899960
Ref: library/stdtypes numeric-types-int-float-complex6900098
Ref: 20726900098
Ref: library/stdtypes typesnumeric6900098
Ref: 1afe6900098
Ref: 數值型別 --- int、float、complex-Footnote-16908013
Ref: 數值型別 --- int、float、complex-Footnote-26908128
Node: 整數型別的位元運算6908205
Ref: library/stdtypes bitstring-ops6908345
Ref: 20746908345
Ref: library/stdtypes bitwise-operations-on-integer-types6908345
Ref: 20756908345
Node: 整數型別的附加 methods6910506
Ref: library/stdtypes additional-methods-on-integer-types6910681
Ref: 20766910681
Ref: library/stdtypes int bit_length6910878
Ref: 20776910878
Ref: library/stdtypes int bit_count6911760
Ref: 7706911760
Ref: library/stdtypes int to_bytes6912164
Ref: 17926912164
Ref: library/stdtypes int from_bytes6914202
Ref: 17546914202
Ref: library/stdtypes int as_integer_ratio6916065
Ref: 96f6916065
Ref: library/stdtypes int is_integer6916314
Ref: 167e6916314
Node: 浮點數的附加 methods6916482
Ref: library/stdtypes additional-methods-on-float6916651
Ref: 207a6916651
Ref: library/stdtypes float as_integer_ratio6916842
Ref: 1c146916842
Ref: library/stdtypes float is_integer6917106
Ref: 20796917106
Ref: library/stdtypes float hex6917689
Ref: 1c156917689
Ref: library/stdtypes float fromhex6917882
Ref: 207b6917882
Node: 數值型別的雜湊6919377
Ref: library/stdtypes hashing-of-numeric-types6919508
Ref: 207c6919508
Ref: library/stdtypes numeric-hash6919508
Ref: 207d6919508
Ref: library/stdtypes bltin-boolean-values6923632
Ref: 207f6923632
Node: Boolean 型別 - bool6923633
Ref: library/stdtypes boolean-type-bool6923774
Ref: 20806923774
Ref: library/stdtypes typebool6923774
Ref: 20366923774
Node: 疊代器型別6924940
Ref: library/stdtypes iterator-types6925078
Ref: 20816925078
Ref: library/stdtypes typeiter6925078
Ref: 204f6925078
Ref: library/stdtypes container __iter__6925441
Ref: 1bc46925441
Ref: library/stdtypes iterator __iter__6926034
Ref: 1bc76926034
Ref: library/stdtypes iterator __next__6926335
Ref: 12606926335
Node: Generator Types6927020
Ref: library/stdtypes generator-types6927087
Ref: 20826927087
Ref: library/stdtypes id36927087
Ref: 20836927087
Node: Sequence Types --- list tuple range6927575
Ref: library/stdtypes sequence-types-list-tuple-range6927718
Ref: 20846927718
Ref: library/stdtypes typesseq6927718
Ref: 1b4d6927718
Node: Common Sequence Operations6928207
Ref: library/stdtypes common-sequence-operations6928338
Ref: 20856928338
Ref: library/stdtypes typesseq-common6928338
Ref: 20866928338
Ref: Common Sequence Operations-Footnote-16937089
Node: Immutable Sequence Types6937166
Ref: library/stdtypes immutable-sequence-types6937328
Ref: 208a6937328
Ref: library/stdtypes typesseq-immutable6937328
Ref: 208b6937328
Node: Mutable Sequence Types6937861
Ref: library/stdtypes mutable-sequence-types6938016
Ref: 208c6938016
Ref: library/stdtypes typesseq-mutable6938016
Ref: 20376938016
Node: List（串列）<2>6943730
Ref: library/stdtypes lists6943867
Ref: 208d6943867
Ref: library/stdtypes typesseq-list6943867
Ref: 20506943867
Ref: library/stdtypes list6944068
Ref: 5b66944068
Ref: library/stdtypes list sort6945253
Ref: b766945253
Node: Tuples6947561
Ref: library/stdtypes tuples6947682
Ref: 208e6947682
Ref: library/stdtypes typesseq-tuple6947682
Ref: 1fbe6947682
Ref: library/stdtypes tuple6948046
Ref: 3226948046
Node: Ranges6949599
Ref: library/stdtypes ranges6949692
Ref: 208f6949692
Ref: library/stdtypes typesseq-range6949692
Ref: 20586949692
Ref: library/stdtypes range6949881
Ref: 8e76949881
Ref: library/stdtypes range start6951867
Ref: 20906951867
Ref: library/stdtypes range stop6951994
Ref: 20916951994
Ref: library/stdtypes range step6952062
Ref: 20926952062
Ref: Ranges-Footnote-16954038
Node: Text Sequence Type --- str6954124
Ref: library/stdtypes text-sequence-type-str6954304
Ref: 20936954304
Ref: library/stdtypes textseq6954304
Ref: 1b036954304
Ref: library/stdtypes str6955971
Ref: 3f26955971
Node: String Methods<2>6958147
Ref: library/stdtypes id56958266
Ref: 20956958266
Ref: library/stdtypes string-methods6958266
Ref: 1b046958266
Ref: library/stdtypes str capitalize6959116
Ref: 20986959116
Ref: library/stdtypes str casefold6959480
Ref: d7c6959480
Ref: library/stdtypes str center6960128
Ref: 1b806960128
Ref: library/stdtypes str count6960400
Ref: 15386960400
Ref: library/stdtypes str encode6960765
Ref: 87a6960765
Ref: library/stdtypes str endswith6961800
Ref: e6e6961800
Ref: library/stdtypes str expandtabs6962135
Ref: 20996962135
Ref: library/stdtypes str find6963250
Ref: e4a6963250
Ref: library/stdtypes str format6963801
Ref: 5c76963801
Ref: library/stdtypes str format_map6965315
Ref: d7d6965315
Ref: library/stdtypes str index6965831
Ref: 15396965831
Ref: library/stdtypes str isalnum6965977
Ref: 209a6965977
Ref: library/stdtypes str isalpha6966317
Ref: 209b6966317
Ref: library/stdtypes str isascii6966847
Ref: a946966847
Ref: library/stdtypes str isdecimal6967089
Ref: 209c6967089
Ref: library/stdtypes str isdigit6967473
Ref: 209d6967473
Ref: library/stdtypes str isidentifier6967981
Ref: 185c6967981
Ref: library/stdtypes str islower6968548
Ref: 209f6968548
Ref: library/stdtypes str isnumeric6968732
Ref: 20a06968732
Ref: library/stdtypes str isprintable6969212
Ref: d7e6969212
Ref: library/stdtypes str isspace6969822
Ref: 20a16969822
Ref: library/stdtypes str istitle6970239
Ref: 20a26970239
Ref: library/stdtypes str isupper6970520
Ref: 20a36970520
Ref: library/stdtypes meth-str-join6970895
Ref: 20a46970895
Ref: library/stdtypes str join6970895
Ref: 20886970895
Ref: library/stdtypes str ljust6971223
Ref: 1b7f6971223
Ref: library/stdtypes str lower6971510
Ref: 16f26971510
Ref: library/stdtypes str lstrip6971755
Ref: 141b6971755
Ref: library/stdtypes str maketrans6972569
Ref: d7f6972569
Ref: library/stdtypes str partition6973298
Ref: e4d6973298
Ref: library/stdtypes str removeprefix6973637
Ref: 8746973637
Ref: library/stdtypes str removesuffix6973994
Ref: 8756973994
Ref: library/stdtypes str replace6974382
Ref: 17e6974382
Ref: library/stdtypes str rfind6974761
Ref: e4b6974761
Ref: library/stdtypes str rindex6975058
Ref: 11f06975058
Ref: library/stdtypes str rjust6975213
Ref: 1b7e6975213
Ref: library/stdtypes str rpartition6975501
Ref: 11f16975501
Ref: library/stdtypes str rsplit6975840
Ref: 11ee6975840
Ref: library/stdtypes str rstrip6976290
Ref: 141c6976290
Ref: library/stdtypes str split6977085
Ref: e4c6977085
Ref: library/stdtypes str splitlines6978829
Ref: 11ef6978829
Ref: library/stdtypes str startswith6981472
Ref: e6d6981472
Ref: library/stdtypes str strip6981809
Ref: 141a6981809
Ref: library/stdtypes str swapcase6982817
Ref: 20a66982817
Ref: library/stdtypes str title6983034
Ref: 20a76983034
Ref: library/stdtypes str translate6984223
Ref: 20a56984223
Ref: library/stdtypes str upper6985129
Ref: 20aa6985129
Ref: library/stdtypes str zfill6985612
Ref: 141d6985612
Ref: String Methods<2>-Footnote-16986136
Ref: String Methods<2>-Footnote-26986200
Ref: String Methods<2>-Footnote-36986264
Ref: String Methods<2>-Footnote-46986424
Ref: String Methods<2>-Footnote-56986584
Ref: String Methods<2>-Footnote-66986744
Ref: String Methods<2>-Footnote-76986808
Ref: String Methods<2>-Footnote-86986968
Node: printf-style String Formatting6987032
Ref: library/stdtypes old-string-formatting6987151
Ref: 6716987151
Ref: library/stdtypes printf-style-string-formatting6987151
Ref: 20ab6987151
Ref: printf-style String Formatting-Footnote-16996473
Ref: printf-style String Formatting-Footnote-26996600
Node: Binary Sequence Types --- bytes bytearray memoryview6996642
Ref: library/stdtypes binary-sequence-types-bytes-bytearray-memoryview6996814
Ref: 20ad6996814
Ref: library/stdtypes binaryseq6996814
Ref: 20396996814
Node: Bytes Objects6997505
Ref: library/stdtypes bytes-objects6997633
Ref: 20ae6997633
Ref: library/stdtypes typebytes6997633
Ref: 203b6997633
Ref: library/stdtypes bytes6997973
Ref: 1a56997973
Ref: library/stdtypes bytes fromhex7000228
Ref: a927000228
Ref: library/stdtypes bytes hex7000833
Ref: d0f7000833
Node: Bytearray Objects7002474
Ref: library/stdtypes bytearray-objects7002641
Ref: 20af7002641
Ref: library/stdtypes typebytearray7002641
Ref: 203a7002641
Ref: library/stdtypes bytearray7002781
Ref: 4e37002781
Ref: library/stdtypes bytearray fromhex7003820
Ref: a937003820
Ref: library/stdtypes bytearray hex7004454
Ref: d107004454
Node: Bytes and Bytearray Operations7005505
Ref: library/stdtypes bytes-and-bytearray-operations7005688
Ref: 20b07005688
Ref: library/stdtypes bytes-methods7005688
Ref: 20387005688
Ref: library/stdtypes bytes count7006908
Ref: 20b17006908
Ref: library/stdtypes bytearray count7006954
Ref: 20b27006954
Ref: library/stdtypes bytes removeprefix7007549
Ref: 20b37007549
Ref: library/stdtypes bytearray removeprefix7007592
Ref: 20b47007592
Ref: library/stdtypes bytes removesuffix7008199
Ref: 20b57008199
Ref: library/stdtypes bytearray removesuffix7008242
Ref: 20b67008242
Ref: library/stdtypes bytes decode7008880
Ref: 87b7008880
Ref: library/stdtypes bytearray decode7008941
Ref: 20b77008941
Ref: library/stdtypes bytes endswith7010158
Ref: 20b87010158
Ref: library/stdtypes bytearray endswith7010210
Ref: 20b97010210
Ref: library/stdtypes bytes find7010637
Ref: 17427010637
Ref: library/stdtypes bytearray find7010682
Ref: 20ba7010682
Ref: library/stdtypes bytes index7011488
Ref: 20bb7011488
Ref: library/stdtypes bytearray index7011534
Ref: 20bc7011534
Ref: library/stdtypes bytes join7011906
Ref: 20897011906
Ref: library/stdtypes bytearray join7011940
Ref: 20bd7011940
Ref: library/stdtypes bytes maketrans7012376
Ref: 120d7012376
Ref: library/stdtypes bytearray maketrans7012422
Ref: 120e7012422
Ref: library/stdtypes bytes partition7012790
Ref: 20bf7012790
Ref: library/stdtypes bytearray partition7012824
Ref: 20c07012824
Ref: library/stdtypes bytes replace7013311
Ref: 20c17013311
Ref: library/stdtypes bytearray replace7013357
Ref: 20c27013357
Ref: library/stdtypes bytes rfind7013879
Ref: 17437013879
Ref: library/stdtypes bytearray rfind7013925
Ref: 20c37013925
Ref: library/stdtypes bytes rindex7014453
Ref: 20c47014453
Ref: library/stdtypes bytearray rindex7014500
Ref: 20c57014500
Ref: library/stdtypes bytes rpartition7014881
Ref: 20c67014881
Ref: library/stdtypes bytearray rpartition7014916
Ref: 20c77014916
Ref: library/stdtypes bytes startswith7015403
Ref: 20c87015403
Ref: library/stdtypes bytearray startswith7015457
Ref: 20c97015457
Ref: library/stdtypes bytes translate7015893
Ref: 20be7015893
Ref: library/stdtypes bytearray translate7015944
Ref: 128e7015944
Ref: library/stdtypes bytes center7016959
Ref: 20ca7016959
Ref: library/stdtypes bytearray center7017004
Ref: 20cb7017004
Ref: library/stdtypes bytes ljust7017507
Ref: 20cc7017507
Ref: library/stdtypes bytearray ljust7017551
Ref: 20cd7017551
Ref: library/stdtypes bytes lstrip7018059
Ref: 20ce7018059
Ref: library/stdtypes bytearray lstrip7018094
Ref: 20cf7018094
Ref: library/stdtypes bytes rjust7019295
Ref: 20d07019295
Ref: library/stdtypes bytearray rjust7019339
Ref: 20d17019339
Ref: library/stdtypes bytes rsplit7019848
Ref: 20d27019848
Ref: library/stdtypes bytearray rsplit7019897
Ref: 20d37019897
Ref: library/stdtypes bytes rstrip7020411
Ref: 20d57020411
Ref: library/stdtypes bytearray rstrip7020446
Ref: 20d67020446
Ref: library/stdtypes bytes split7021628
Ref: 20d77021628
Ref: library/stdtypes bytearray split7021676
Ref: 20d47021676
Ref: library/stdtypes bytes strip7023615
Ref: 20d87023615
Ref: library/stdtypes bytearray strip7023649
Ref: 20d97023649
Ref: library/stdtypes bytes capitalize7024838
Ref: 20da7024838
Ref: library/stdtypes bytearray capitalize7024870
Ref: 20db7024870
Ref: library/stdtypes bytes expandtabs7025281
Ref: 20dc7025281
Ref: library/stdtypes bytearray expandtabs7025322
Ref: 20dd7025322
Ref: library/stdtypes bytes isalnum7026666
Ref: 20de7026666
Ref: library/stdtypes bytearray isalnum7026695
Ref: 20df7026695
Ref: library/stdtypes bytes isalpha7027260
Ref: 20e07027260
Ref: library/stdtypes bytearray isalpha7027289
Ref: 20e17027289
Ref: library/stdtypes bytes isascii7027729
Ref: 20e27027729
Ref: library/stdtypes bytearray isascii7027758
Ref: 20e37027758
Ref: library/stdtypes bytes isdigit7027975
Ref: 20e47027975
Ref: library/stdtypes bytearray isdigit7028004
Ref: 20e57028004
Ref: library/stdtypes bytes islower7028379
Ref: 20e67028379
Ref: library/stdtypes bytearray islower7028408
Ref: 20e77028408
Ref: library/stdtypes bytes isspace7028949
Ref: 20e87028949
Ref: library/stdtypes bytearray isspace7028978
Ref: 20e97028978
Ref: library/stdtypes bytes istitle7029310
Ref: 20ea7029310
Ref: library/stdtypes bytearray istitle7029339
Ref: 20eb7029339
Ref: library/stdtypes bytes isupper7029711
Ref: 20ed7029711
Ref: library/stdtypes bytearray isupper7029740
Ref: 20ee7029740
Ref: library/stdtypes bytes lower7030297
Ref: 20ef7030297
Ref: library/stdtypes bytearray lower7030324
Ref: 20f07030324
Ref: library/stdtypes bytes splitlines7030968
Ref: 20f17030968
Ref: library/stdtypes bytearray splitlines7031014
Ref: 20f27031014
Ref: library/stdtypes bytes swapcase7031966
Ref: 20f37031966
Ref: library/stdtypes bytearray swapcase7031996
Ref: 20f47031996
Ref: library/stdtypes bytes title7032931
Ref: 20ec7032931
Ref: library/stdtypes bytearray title7032958
Ref: 20f57032958
Ref: library/stdtypes bytes upper7034588
Ref: 20f67034588
Ref: library/stdtypes bytearray upper7034615
Ref: 20f77034615
Ref: library/stdtypes bytes zfill7035259
Ref: 20f87035259
Ref: library/stdtypes bytearray zfill7035291
Ref: 20f97035291
Node: printf-style Bytes Formatting7036006
Ref: library/stdtypes bytes-formatting7036184
Ref: d277036184
Ref: library/stdtypes printf-style-bytes-formatting7036184
Ref: 20fa7036184
Ref: printf-style Bytes Formatting-Footnote-17045680
Ref: printf-style Bytes Formatting-Footnote-27045807
Ref: printf-style Bytes Formatting-Footnote-37045849
Node: Memory Views7045891
Ref: library/stdtypes memory-views7046030
Ref: 20fb7046030
Ref: library/stdtypes typememoryview7046030
Ref: 20517046030
Ref: library/stdtypes memoryview7046227
Ref: 40f7046227
Ref: library/stdtypes memoryview __eq__7050022
Ref: 20ff7050022
Ref: library/stdtypes memoryview tobytes7052010
Ref: 21007052010
Ref: library/stdtypes memoryview hex7053085
Ref: d117053085
Ref: library/stdtypes memoryview tolist7053606
Ref: 20fc7053606
Ref: library/stdtypes memoryview toreadonly7054166
Ref: 21017054166
Ref: library/stdtypes memoryview release7054780
Ref: 11567054780
Ref: library/stdtypes memoryview cast7056149
Ref: 21027056149
Ref: library/stdtypes memoryview obj7059196
Ref: 21047059196
Ref: library/stdtypes memoryview nbytes7059433
Ref: 21057059433
Ref: library/stdtypes memoryview readonly7060558
Ref: 21067060558
Ref: library/stdtypes memoryview format7060647
Ref: 20fe7060647
Ref: library/stdtypes memoryview itemsize7061180
Ref: 20fd7061180
Ref: library/stdtypes memoryview ndim7061553
Ref: 21077061553
Ref: library/stdtypes memoryview shape7061691
Ref: 21087061691
Ref: library/stdtypes memoryview strides7061941
Ref: 21097061941
Ref: library/stdtypes memoryview suboffsets7062226
Ref: 210a7062226
Ref: library/stdtypes memoryview c_contiguous7062348
Ref: 210b7062348
Ref: library/stdtypes memoryview f_contiguous7062499
Ref: 210c7062499
Ref: library/stdtypes memoryview contiguous7062656
Ref: 210d7062656
Ref: Memory Views-Footnote-17062839
Node: Set Types --- set frozenset7062881
Ref: library/stdtypes set-types-set-frozenset7063049
Ref: 210e7063049
Ref: library/stdtypes types-set7063049
Ref: 204d7063049
Ref: library/stdtypes set7064597
Ref: 57d7064597
Ref: library/stdtypes frozenset7064626
Ref: 57e7064626
Ref: library/stdtypes frozenset isdisjoint7065663
Ref: 210f7065663
Ref: library/stdtypes frozenset issubset7065871
Ref: 21107065871
Ref: library/stdtypes frozenset issuperset7066150
Ref: 21117066150
Ref: library/stdtypes frozenset union7066433
Ref: 13ec7066433
Ref: library/stdtypes frozenset intersection7066574
Ref: 13ed7066574
Ref: library/stdtypes frozenset difference7066737
Ref: 21127066737
Ref: library/stdtypes frozenset symmetric_difference7066903
Ref: 21137066903
Ref: library/stdtypes frozenset copy7067075
Ref: 21147067075
Ref: library/stdtypes frozenset update7069311
Ref: 21157069311
Ref: library/stdtypes frozenset intersection_update7069443
Ref: 13ee7069443
Ref: library/stdtypes frozenset difference_update7069615
Ref: 21167069615
Ref: library/stdtypes frozenset symmetric_difference_update7069760
Ref: 13ef7069760
Ref: library/stdtypes frozenset add7069942
Ref: 21177069942
Ref: library/stdtypes frozenset remove7070013
Ref: 21187070013
Ref: library/stdtypes frozenset discard7070170
Ref: 21197070170
Ref: library/stdtypes frozenset pop7070267
Ref: 211a7070267
Ref: library/stdtypes frozenset clear7070416
Ref: 211b7070416
Node: Mapping Types --- dict7070977
Ref: library/stdtypes mapping-types-dict7071114
Ref: 211c7071114
Ref: library/stdtypes typesmapping7071114
Ref: a697071114
Ref: library/stdtypes dict7071897
Ref: 23b7071897
Ref: library/stdtypes dict clear7076267
Ref: 211d7076267
Ref: library/stdtypes dict copy7076343
Ref: b777076343
Ref: library/stdtypes dict fromkeys7076421
Ref: 211e7076421
Ref: library/stdtypes dict get7076967
Ref: 211f7076967
Ref: library/stdtypes dict items7077225
Ref: 7737077225
Ref: library/stdtypes dict keys7077397
Ref: 7717077397
Ref: library/stdtypes dict pop7077540
Ref: 32d7077540
Ref: library/stdtypes dict popitem7077793
Ref: 14957077793
Ref: library/stdtypes dict setdefault7078566
Ref: 101a7078566
Ref: library/stdtypes dict update7078799
Ref: 13d07078799
Ref: library/stdtypes dict values7079284
Ref: 7727079284
Node: 字典視圖物件7081963
Ref: library/stdtypes dict-views7082040
Ref: 21207082040
Ref: library/stdtypes dictionary-view-objects7082040
Ref: 21217082040
Node: 情境管理器型別7085611
Ref: library/stdtypes context-manager-types7085789
Ref: 21237085789
Ref: library/stdtypes typecontextmanager7085789
Ref: 1e957085789
Ref: library/stdtypes contextmanager __enter__7086144
Ref: 21247086144
Ref: library/stdtypes contextmanager __exit__7087042
Ref: 21257087042
Node: 型別註釋的型別 --- 泛型別名 Generic Alias 、聯合 Union7089017
Ref: library/stdtypes type-annotation-types-generic-alias-union7089193
Ref: 21267089193
Node: 泛型別名型別7089522
Ref: library/stdtypes generic-alias-type7089677
Ref: 21277089677
Ref: library/stdtypes types-genericalias7089677
Ref: 6567089677
Node: 標準泛型類別7094214
Ref: library/stdtypes standard-generic-classes7094330
Ref: 21297094330
Node: GenericAlias 物件的特殊屬性7096623
Ref: library/stdtypes special-attributes-of-genericalias-objects7096739
Ref: 21377096739
Ref: library/stdtypes genericalias __origin__7096888
Ref: 21387096888
Ref: library/stdtypes genericalias __args__7097035
Ref: 21287097035
Ref: library/stdtypes genericalias __parameters__7097299
Ref: 21397097299
Ref: library/stdtypes genericalias __unpacked__7097873
Ref: 213a7097873
Ref: GenericAlias 物件的特殊屬性-Footnote-17098654
Ref: GenericAlias 物件的特殊屬性-Footnote-27098696
Node: 聯合型別 Union Type7098738
Ref: library/stdtypes types-union7098893
Ref: 7667098893
Ref: library/stdtypes union-type7098893
Ref: 213b7098893
Ref: 聯合型別 Union Type-Footnote-17102283
Node: Other Built-in Types7102325
Ref: library/stdtypes other-built-in-types7102492
Ref: 213c7102492
Ref: library/stdtypes typesother7102492
Ref: 213d7102492
Node: 模組<4>7102869
Ref: library/stdtypes modules7102971
Ref: 213e7102971
Ref: library/stdtypes typesmodules7102971
Ref: 213f7102971
Node: Classes and Class Instances7104111
Ref: library/stdtypes classes-and-class-instances7104228
Ref: 21407104228
Ref: library/stdtypes typesobjects7104228
Ref: 21417104228
Node: 函式7104388
Ref: library/stdtypes functions7104503
Ref: 21427104503
Ref: library/stdtypes typesfunctions7104503
Ref: 21437104503
Node: Methods7104947
Ref: library/stdtypes methods7105047
Ref: 21447105047
Ref: library/stdtypes typesmethods7105047
Ref: 21457105047
Node: Code Objects7106870
Ref: library/stdtypes bltin-code-objects7106976
Ref: 21467106976
Ref: library/stdtypes code-objects7106976
Ref: 21477106976
Node: Type Objects7107815
Ref: library/stdtypes bltin-type-objects7107929
Ref: 205e7107929
Ref: library/stdtypes type-objects7107929
Ref: 21487107929
Node: The Null Object7108277
Ref: library/stdtypes bltin-null-object7108398
Ref: 21497108398
Ref: library/stdtypes the-null-object7108398
Ref: 214a7108398
Node: The Ellipsis Object7108709
Ref: library/stdtypes bltin-ellipsis-object7108839
Ref: 214b7108839
Ref: library/stdtypes the-ellipsis-object7108839
Ref: 214c7108839
Node: NotImplemented 物件7109206
Ref: library/stdtypes bltin-notimplemented-object7109337
Ref: 214d7109337
Ref: library/stdtypes the-notimplemented-object7109337
Ref: 214e7109337
Node: Internal Objects7109734
Ref: library/stdtypes internal-objects7109837
Ref: 214f7109837
Ref: library/stdtypes typesinternal7109837
Ref: 21507109837
Node: 特殊屬性7110046
Ref: library/stdtypes special-attributes7110188
Ref: 21517110188
Ref: library/stdtypes specialattrs7110188
Ref: 21527110188
Ref: library/stdtypes object __dict__7110411
Ref: c047110411
Ref: library/stdtypes instance __class__7110537
Ref: 14187110537
Ref: library/stdtypes class __bases__7110620
Ref: 14177110620
Ref: library/stdtypes definition __name__7110700
Ref: 14167110700
Ref: library/stdtypes definition __qualname__7110820
Ref: 1dec7110820
Ref: library/stdtypes definition __type_params__7110995
Ref: 21537110995
Ref: library/stdtypes class __mro__7111167
Ref: 205d7111167
Ref: library/stdtypes class mro7111318
Ref: 21547111318
Ref: library/stdtypes class __subclasses__7111552
Ref: 5197111552
Ref: library/stdtypes class __static_attributes__7111928
Ref: 1317111928
Node: Integer string conversion length limitation7112133
Ref: library/stdtypes int-max-str-digits7112246
Ref: 5997112246
Ref: library/stdtypes integer-string-conversion-length-limitation7112246
Ref: 21557112246
Ref: Integer string conversion length limitation-Footnote-17114963
Node: 受影響的 API7115033
Ref: library/stdtypes affected-apis7115150
Ref: 21567115150
Node: 設定限制7116114
Ref: library/stdtypes configuring-the-limit7116255
Ref: 21577116255
Node: 建議的配置7118704
Ref: library/stdtypes recommended-configuration7118820
Ref: 215b7118820
Node: 內建的例外7119666
Ref: library/exceptions doc7119822
Ref: 215c7119822
Ref: library/exceptions bltin-exceptions7119822
Ref: 17867119822
Ref: library/exceptions built-in-exceptions7119822
Ref: 215d7119822
Node: 例外的情境7121458
Ref: library/exceptions exception-context7121558
Ref: 215e7121558
Ref: library/exceptions BaseException __context__7121678
Ref: 125c7121678
Ref: library/exceptions BaseException __cause__7121716
Ref: 125d7121716
Ref: library/exceptions BaseException __suppress_context__7121752
Ref: 1f8b7121752
Node: 繼承自內建的例外7123377
Ref: library/exceptions inheriting-from-built-in-exceptions7123511
Ref: 215f7123511
Ref: 繼承自內建的例外-Footnote-17124258
Node: 基底類別 base classes7124331
Ref: library/exceptions base-classes7124462
Ref: 21607124462
Ref: library/exceptions BaseException7124598
Ref: 55f7124598
Ref: library/exceptions BaseException args7124926
Ref: 5127124926
Ref: library/exceptions BaseException with_traceback7125262
Ref: 1f8a7125262
Ref: library/exceptions BaseException __traceback__7126038
Ref: 125b7126038
Ref: library/exceptions BaseException add_note7126214
Ref: 55e7126214
Ref: library/exceptions BaseException __notes__7126477
Ref: 21617126477
Ref: library/exceptions Exception7126693
Ref: 97d7126693
Ref: library/exceptions ArithmeticError7126877
Ref: 21627126877
Ref: library/exceptions BufferError7127085
Ref: 17297127085
Ref: library/exceptions LookupError7127202
Ref: 20a97127202
Ref: 基底類別 base classes-Footnote-17127485
Node: 實體例外7127527
Ref: library/exceptions concrete-exceptions7127640
Ref: 21647127640
Ref: library/exceptions AssertionError7127725
Ref: 64e7127725
Ref: library/exceptions AttributeError7127819
Ref: 2f67127819
Ref: library/exceptions EOFError7128376
Ref: 126c7128376
Ref: library/exceptions FloatingPointError7128661
Ref: 21637128661
Ref: library/exceptions GeneratorExit7128724
Ref: 13357128724
Ref: library/exceptions ImportError7129062
Ref: 3527129062
Ref: library/exceptions ImportError name7129355
Ref: 21657129355
Ref: library/exceptions ImportError path7129430
Ref: 21667129430
Ref: library/exceptions ModuleNotFoundError7129592
Ref: aeb7129592
Ref: library/exceptions IndexError7129855
Ref: 14a37129855
Ref: library/exceptions KeyError7130107
Ref: 2fb7130107
Ref: library/exceptions KeyboardInterrupt7130226
Ref: 9757130226
Ref: library/exceptions MemoryError7131038
Ref: 15bc7131038
Ref: library/exceptions NameError7131557
Ref: 3e57131557
Ref: library/exceptions NotImplementedError7131993
Ref: 20d7131993
Ref: library/exceptions OSError7132765
Ref: 3507132765
Ref: library/exceptions OSError errno7133673
Ref: 21697133673
Ref: library/exceptions OSError winerror7133764
Ref: 216a7133764
Ref: library/exceptions OSError strerror7134302
Ref: 216b7134302
Ref: library/exceptions OSError filename7134507
Ref: 216c7134507
Ref: library/exceptions OSError filename27134533
Ref: 216d7134533
Ref: library/exceptions OverflowError7135460
Ref: 8257135460
Ref: library/exceptions PythonFinalizationError7135900
Ref: 1327135900
Ref: library/exceptions RecursionError7136479
Ref: d127136479
Ref: library/exceptions ReferenceError7136773
Ref: 147d7136773
Ref: library/exceptions RuntimeError7137083
Ref: 1797137083
Ref: library/exceptions StopIteration7137260
Ref: ba17137260
Ref: library/exceptions StopIteration value7137459
Ref: 1e9f7137459
Ref: library/exceptions StopAsyncIteration7138467
Ref: 19337138467
Ref: library/exceptions SyntaxError7138657
Ref: 1737138657
Ref: library/exceptions SyntaxError filename7139145
Ref: 216e7139145
Ref: library/exceptions SyntaxError lineno7139226
Ref: 216f7139226
Ref: library/exceptions SyntaxError offset7139379
Ref: 21707139379
Ref: library/exceptions SyntaxError text7139548
Ref: 21717139548
Ref: library/exceptions SyntaxError end_lineno7139625
Ref: 21727139625
Ref: library/exceptions SyntaxError end_offset7139788
Ref: 21737139788
Ref: library/exceptions IndentationError7140348
Ref: 74c7140348
Ref: library/exceptions TabError7140496
Ref: 4e97140496
Ref: library/exceptions SystemError7140666
Ref: 51b7140666
Ref: library/exceptions SystemExit7141249
Ref: ce77141249
Ref: library/exceptions SystemExit code7142404
Ref: 21757142404
Ref: library/exceptions TypeError7142520
Ref: 4dd7142520
Ref: library/exceptions UnboundLocalError7143259
Ref: 14a47143259
Ref: library/exceptions UnicodeError7143467
Ref: 123a7143467
Ref: library/exceptions UnicodeError encoding7143802
Ref: 21767143802
Ref: library/exceptions UnicodeError reason7143871
Ref: 21777143871
Ref: library/exceptions UnicodeError object7143950
Ref: 21787143950
Ref: library/exceptions UnicodeError start7144032
Ref: 21797144032
Ref: library/exceptions UnicodeError end7144124
Ref: 217a7144124
Ref: library/exceptions UnicodeEncodeError7144220
Ref: 61d7144220
Ref: library/exceptions UnicodeDecodeError7144378
Ref: 9b77144378
Ref: library/exceptions UnicodeTranslateError7144536
Ref: 217b7144536
Ref: library/exceptions ValueError7144697
Ref: 1e77144697
Ref: library/exceptions ZeroDivisionError7144912
Ref: 8e97144912
Ref: library/exceptions EnvironmentError7145239
Ref: ff67145239
Ref: library/exceptions IOError7145269
Ref: ff57145269
Ref: library/exceptions WindowsError7145290
Ref: ff77145290
Ref: 實體例外-Footnote-17145425
Ref: 實體例外-Footnote-27145467
Node: 作業系統例外7145509
Ref: library/exceptions os-exceptions7145576
Ref: 21687145576
Ref: library/exceptions BlockingIOError7145723
Ref: ffa7145723
Ref: library/exceptions BlockingIOError characters_written7146110
Ref: 21807146110
Ref: library/exceptions ChildProcessError7146327
Ref: ffb7146327
Ref: library/exceptions ConnectionError7146468
Ref: db07146468
Ref: library/exceptions BrokenPipeError7146714
Ref: fff7146714
Ref: library/exceptions ConnectionAbortedError7147028
Ref: 10007147028
Ref: library/exceptions ConnectionRefusedError7147251
Ref: 10017147251
Ref: library/exceptions ConnectionResetError7147462
Ref: 10027147462
Ref: library/exceptions FileExistsError7147660
Ref: fc37147660
Ref: library/exceptions FileNotFoundError7147811
Ref: e677147811
Ref: library/exceptions InterruptedError7147958
Ref: d2e7147958
Ref: library/exceptions IsADirectoryError7148326
Ref: ffc7148326
Ref: library/exceptions NotADirectoryError7148508
Ref: ffd7148508
Ref: library/exceptions PermissionError7148851
Ref: ce97148851
Ref: library/exceptions ProcessLookupError7149216
Ref: ffe7149216
Ref: library/exceptions TimeoutError7149354
Ref: 7d97149354
Ref: 作業系統例外-Footnote-17149683
Ref: 作業系統例外-Footnote-27149725
Node: 警告7149767
Ref: library/exceptions warning-categories-as-exceptions7149867
Ref: 218e7149867
Ref: library/exceptions warnings7149867
Ref: 218f7149867
Ref: library/exceptions Warning7150002
Ref: 21917150002
Ref: library/exceptions UserWarning7150060
Ref: 21927150060
Ref: library/exceptions DeprecationWarning7150143
Ref: 18b7150143
Ref: library/exceptions PendingDeprecationWarning7150497
Ref: 86d7150497
Ref: library/exceptions SyntaxWarning7150993
Ref: 40c7150993
Ref: library/exceptions RuntimeWarning7151072
Ref: 1a37151072
Ref: library/exceptions FutureWarning7151164
Ref: 3577151164
Ref: library/exceptions ImportWarning7151329
Ref: 4a27151329
Ref: library/exceptions UnicodeWarning7151537
Ref: 13917151537
Ref: library/exceptions EncodingWarning7151610
Ref: 1c3f7151610
Ref: library/exceptions BytesWarning7151776
Ref: bca7151776
Ref: library/exceptions ResourceWarning7151883
Ref: 2297151883
Ref: 警告-Footnote-17152136
Ref: 警告-Footnote-27152178
Ref: 警告-Footnote-37152220
Node: 例外群組7152262
Ref: library/exceptions exception-groups7152362
Ref: 21937152362
Ref: library/exceptions lib-exception-groups7152362
Ref: 21947152362
Ref: library/exceptions ExceptionGroup7152691
Ref: 19c7152691
Ref: library/exceptions BaseExceptionGroup7152731
Ref: 2447152731
Ref: library/exceptions BaseExceptionGroup message7153720
Ref: 21957153720
Ref: library/exceptions BaseExceptionGroup exceptions7153823
Ref: 21967153823
Ref: library/exceptions BaseExceptionGroup subgroup7153974
Ref: 15b97153974
Ref: library/exceptions BaseExceptionGroup split7155207
Ref: 15ba7155207
Ref: library/exceptions BaseExceptionGroup derive7155452
Ref: 15b87155452
Node: 例外階層7158365
Ref: library/exceptions exception-hierarchy7158450
Ref: 21977158450
Ref: library/text stringservices7161297
Ref: 20947161297
Node: 文本處理 Text Processing 服務7161298
Ref: library/text doc7161463
Ref: 21987161463
Ref: library/text text-processing-services7161463
Ref: 21997161463
Ref: library/text textservices7161463
Ref: 20977161463
Node: string --- 常見的字串操作7162489
Ref: library/string doc7162650
Ref: 219b7162650
Ref: library/string module-string7162650
Ref: be7162650
Ref: library/string string-common-string-operations7162650
Ref: 219c7162650
Ref: string --- 常見的字串操作-Footnote-17163061
Node: 字串常數7163127
Ref: library/string string-constants7163235
Ref: 219d7163235
Ref: library/string string ascii_letters7163309
Ref: 12587163309
Ref: library/string string ascii_lowercase7163484
Ref: 219e7163484
Ref: library/string string ascii_uppercase7163628
Ref: 219f7163628
Ref: library/string string digits7163777
Ref: 21a07163777
Ref: library/string string hexdigits7163843
Ref: 21a17163843
Ref: library/string string octdigits7163924
Ref: 21a27163924
Ref: library/string string punctuation7163987
Ref: 21a37163987
Ref: library/string string printable7164147
Ref: 21a47164147
Ref: library/string string whitespace7164366
Ref: 21a57164366
Node: 自訂字串格式7164641
Ref: library/string custom-string-formatting7164779
Ref: 21a67164779
Ref: library/string string-formatting7164779
Ref: 20967164779
Ref: library/string string Formatter7165161
Ref: e5e7165161
Ref: library/string string Formatter format7165253
Ref: ba77165253
Ref: library/string string Formatter vformat7165590
Ref: 21a77165590
Ref: library/string string Formatter parse7166301
Ref: 21a87166301
Ref: library/string string Formatter get_field7167058
Ref: 21a97167058
Ref: library/string string Formatter get_value7167599
Ref: 21aa7167599
Ref: library/string string Formatter check_unused_args7168832
Ref: 21ab7168832
Ref: library/string string Formatter format_field7169436
Ref: 21ac7169436
Ref: library/string string Formatter convert_field7169662
Ref: 21ad7169662
Ref: 自訂字串格式-Footnote-17170025
Ref: 自訂字串格式-Footnote-27170067
Node: 格式化文字語法7170109
Ref: library/string format-string-syntax7170247
Ref: 21ae7170247
Ref: library/string formatstrings7170247
Ref: 131e7170247
Ref: library/string grammar-token-format-string-replacement_field7171039
Ref: 21af7171039
Ref: library/string grammar-token-format-string-field_name7171122
Ref: 21b07171122
Ref: library/string grammar-token-format-string-arg_name7171204
Ref: 21b17171204
Ref: library/string grammar-token-format-string-attribute_name7171253
Ref: 21b27171253
Ref: library/string grammar-token-format-string-element_index7171291
Ref: 21b37171291
Ref: library/string grammar-token-format-string-index_string7171340
Ref: 21b47171340
Ref: library/string grammar-token-format-string-conversion7171403
Ref: 21b57171403
Ref: library/string grammar-token-format-string-format_spec7171446
Ref: 21b67171446
Node: 格式規格 Format Specification 迷你語言7175510
Ref: library/string format-specification-mini-language7175635
Ref: 21b87175635
Ref: library/string formatspec7175635
Ref: 1c87175635
Ref: library/string grammar-token-format-spec-format_spec7176452
Ref: 21b97176452
Ref: library/string grammar-token-format-spec-fill7176557
Ref: 21ba7176557
Ref: library/string grammar-token-format-spec-align7176598
Ref: 21bb7176598
Ref: library/string grammar-token-format-spec-sign7176645
Ref: 21bc7176645
Ref: library/string grammar-token-format-spec-width7176686
Ref: 21bd7176686
Ref: library/string grammar-token-format-spec-grouping_option7176718
Ref: 21be7176718
Ref: library/string grammar-token-format-spec-precision7176753
Ref: 21bf7176753
Ref: library/string grammar-token-format-spec-type7176785
Ref: 21c07176785
Ref: 格式規格 Format Specification 迷你語言-Footnote-17189290
Ref: 格式規格 Format Specification 迷你語言-Footnote-27189332
Ref: 格式規格 Format Specification 迷你語言-Footnote-37189374
Node: 格式範例7189416
Ref: library/string format-examples7189541
Ref: 21c17189541
Ref: library/string formatexamples7189541
Ref: 21b77189541
Node: 模板字串7193902
Ref: library/string id17194034
Ref: 21c27194034
Ref: library/string template-strings7194034
Ref: 20ac7194034
Ref: library/string string Template7195408
Ref: 62d7195408
Ref: library/string string Template substitute7195529
Ref: 1bed7195529
Ref: library/string string Template safe_substitute7195943
Ref: 1bee7195943
Ref: library/string string Template is_valid7196873
Ref: 62c7196873
Ref: library/string string Template get_identifiers7197085
Ref: 62b7197085
Ref: library/string string Template template7197366
Ref: 21c37197366
Ref: 模板字串-Footnote-17201126
Ref: 模板字串-Footnote-27201168
Node: 輔助函式7201220
Ref: library/string helper-functions7201322
Ref: 21c47201322
Ref: library/string string capwords7201361
Ref: 20a87201361
Node: re --- 正規表示式 regular expression 操作7201826
Ref: library/re doc7202035
Ref: 21c57202035
Ref: library/re module-re7202035
Ref: a77202035
Ref: library/re re-regular-expression-operations7202035
Ref: 21c67202035
Ref: re --- 正規表示式 regular expression 操作-Footnote-17204491
Ref: re --- 正規表示式 regular expression 操作-Footnote-27204551
Node: 正規表示式語法7204591
Ref: library/re re-syntax7204718
Ref: 6c87204718
Ref: library/re regular-expression-syntax7204718
Ref: 21c77204718
Ref: library/re re-conditional-expression7224961
Ref: 16b07224961
Ref: library/re re-special-sequences7225647
Ref: 21d57225647
Ref: 正規表示式語法-Footnote-17231801
Ref: 正規表示式語法-Footnote-27231843
Node: 模組內容7231915
Ref: library/re contents-of-module-re7232077
Ref: 21d47232077
Ref: library/re module-contents7232077
Ref: 21d67232077
Node: 旗標7232405
Ref: library/re flags7232478
Ref: 21cc7232478
Ref: library/re re RegexFlag7232637
Ref: 5d27232637
Ref: library/re re A7232806
Ref: 21cd7232806
Ref: library/re re ASCII7232823
Ref: 5d37232823
Ref: library/re re DEBUG7233498
Ref: 21d87233498
Ref: library/re re I7233615
Ref: 21ce7233615
Ref: library/re re IGNORECASE7233632
Ref: 16237233632
Ref: library/re re L7234590
Ref: 21cf7234590
Ref: library/re re LOCALE7234607
Ref: b107234607
Ref: library/re re M7235579
Ref: 21d07235579
Ref: library/re re MULTILINE7235596
Ref: 21cb7235596
Ref: library/re re NOFLAG7236188
Ref: 21d97236188
Ref: library/re re S7236581
Ref: 21d17236581
Ref: library/re re DOTALL7236598
Ref: 21ca7236598
Ref: library/re re U7236841
Ref: 21d27236841
Ref: library/re re UNICODE7236858
Ref: b117236858
Ref: library/re re X7237156
Ref: 21d37237156
Ref: library/re re VERBOSE7237173
Ref: 21da7237173
Node: Functions7238247
Ref: library/re functions7238339
Ref: 21db7238339
Ref: library/re re compile7238376
Ref: b7a7238376
Ref: library/re re search7239505
Ref: 11c47239505
Ref: library/re re match7240091
Ref: 11c57240091
Ref: library/re re fullmatch7240931
Ref: f287240931
Ref: library/re re split7241449
Ref: 2827241449
Ref: library/re re findall7243704
Ref: fcd7243704
Ref: library/re re finditer7244927
Ref: 14687244927
Ref: library/re re sub7245556
Ref: 2837245556
Ref: library/re re subn7249280
Ref: 2847249280
Ref: library/re re escape7249658
Ref: bb07249658
Ref: library/re re purge7251140
Ref: 21df7251140
Node: Exceptions7251207
Ref: library/re exceptions7251284
Ref: 21e07251284
Ref: library/re re PatternError7251323
Ref: 2237251323
Ref: library/re re PatternError msg7251773
Ref: 21e17251773
Ref: library/re re PatternError pattern7251837
Ref: 21e27251837
Ref: library/re re PatternError pos7251906
Ref: 21e37251906
Ref: library/re re PatternError lineno7252018
Ref: 21e47252018
Ref: library/re re PatternError colno7252107
Ref: 21e57252107
Node: Regular Expression Objects7252393
Ref: library/re re-objects7252547
Ref: f297252547
Ref: library/re regular-expression-objects7252547
Ref: 21e67252547
Ref: library/re re Pattern7252618
Ref: 16e27252618
Ref: library/re re Pattern search7252882
Ref: 21dd7252882
Ref: library/re re Pattern match7254339
Ref: 21dc7254339
Ref: library/re re Pattern fullmatch7255190
Ref: 17087255190
Ref: library/re re Pattern split7255982
Ref: 21e77255982
Ref: library/re re Pattern findall7256116
Ref: 21e87256116
Ref: library/re re Pattern finditer7256378
Ref: 21e97256378
Ref: library/re re Pattern sub7256643
Ref: 21ea7256643
Ref: library/re re Pattern subn7256776
Ref: 21eb7256776
Ref: library/re re Pattern flags7256911
Ref: 21ec7256911
Ref: library/re re Pattern groups7257181
Ref: 21ed7257181
Ref: library/re re Pattern groupindex7257262
Ref: 21ee7257262
Ref: library/re re Pattern pattern7257473
Ref: 21ef7257473
Node: Match Objects7257727
Ref: library/re id37257896
Ref: 21f07257896
Ref: library/re match-objects7257896
Ref: f2a7257896
Ref: library/re re Match7258248
Ref: c6f7258248
Ref: library/re re Match expand7258498
Ref: 21f17258498
Ref: library/re re Match group7259092
Ref: 21f27259092
Ref: library/re re Match __getitem__7261362
Ref: 21f37261362
Ref: library/re re Match groups7262064
Ref: 21f47262064
Ref: library/re re Match groupdict7262913
Ref: 21f57262913
Ref: library/re re Match start7263380
Ref: 21f67263380
Ref: library/re re Match end7263414
Ref: 21f77263414
Ref: library/re re Match span7264462
Ref: 21f87264462
Ref: library/re re Match pos7264715
Ref: 21f97264715
Ref: library/re re Match endpos7264972
Ref: 21fa7264972
Ref: library/re re Match lastindex7265223
Ref: 21fb7265223
Ref: library/re re Match lastgroup7265619
Ref: 21fc7265619
Ref: library/re re Match re7265787
Ref: 21fd7265787
Ref: library/re re Match string7265951
Ref: 21fe7265951
Node: Regular Expression Examples7266184
Ref: library/re re-examples7266318
Ref: 11f67266318
Ref: library/re regular-expression-examples7266318
Ref: 21ff7266318
Node: Checking for a Pair7266654
Ref: library/re checking-for-a-pair7266758
Ref: 22007266758
Node: 模擬 scanf7268823
Ref: library/re simulating-scanf7268951
Ref: 22017268951
Node: search vs match7271012
Ref: library/re id47271139
Ref: 22027271139
Ref: library/re search-vs-match7271139
Ref: 21de7271139
Node: Making a Phonebook7272596
Ref: library/re making-a-phonebook7272723
Ref: 22037272723
Node: Text Munging7274922
Ref: library/re text-munging7275053
Ref: 22047275053
Node: Finding all Adverbs7275882
Ref: library/re finding-all-adverbs7276034
Ref: 22057276034
Node: Finding all Adverbs and their Positions7276492
Ref: library/re finding-all-adverbs-and-their-positions7276651
Ref: 22067276651
Node: Raw String Notation7277355
Ref: library/re raw-string-notation7277514
Ref: 22077277514
Node: Writing a Tokenizer7278441
Ref: library/re writing-a-tokenizer7278552
Ref: 22087278552
Ref: library/re frie097281923
Ref: 21c87281923
Ref: Writing a Tokenizer-Footnote-17282201
Node: difflib --- 計算差異的輔助工具7282256
Ref: library/difflib doc7282467
Ref: 22097282467
Ref: library/difflib difflib-helpers-for-computing-deltas7282467
Ref: 220a7282467
Ref: library/difflib module-difflib7282467
Ref: 2f7282467
Ref: library/difflib difflib Differ7284933
Ref: 220b7284933
Ref: library/difflib difflib HtmlDiff7286105
Ref: 220c7286105
Ref: library/difflib difflib HtmlDiff __init__7286476
Ref: 220d7286476
Ref: library/difflib difflib HtmlDiff make_file7287289
Ref: d957287289
Ref: library/difflib difflib HtmlDiff make_table7288963
Ref: 220f7288963
Ref: library/difflib difflib context_diff7289424
Ref: 22107289424
Ref: library/difflib difflib get_close_matches7291469
Ref: 22147291469
Ref: library/difflib difflib ndiff7292625
Ref: 220e7292625
Ref: library/difflib difflib restore7294184
Ref: 22177294184
Ref: library/difflib difflib unified_diff7294926
Ref: 22197294926
Ref: library/difflib difflib diff_bytes7296850
Ref: d967296850
Ref: library/difflib difflib IS_LINE_JUNK7297742
Ref: 22157297742
Ref: library/difflib difflib IS_CHARACTER_JUNK7298042
Ref: 22167298042
Ref: difflib --- 計算差異的輔助工具-Footnote-17298714
Ref: difflib --- 計算差異的輔助工具-Footnote-27298781
Ref: difflib --- 計算差異的輔助工具-Footnote-37298871
Node: SequenceMatcher 物件7298904
Ref: library/difflib sequence-matcher7299033
Ref: 221a7299033
Ref: library/difflib sequencematcher-objects7299033
Ref: 221b7299033
Ref: library/difflib difflib SequenceMatcher7299155
Ref: fba7299155
Ref: library/difflib difflib SequenceMatcher set_seqs7300677
Ref: 221c7300677
Ref: library/difflib difflib SequenceMatcher set_seq17301095
Ref: 221e7301095
Ref: library/difflib difflib SequenceMatcher set_seq27301238
Ref: 221d7301238
Ref: library/difflib difflib SequenceMatcher find_longest_match7301381
Ref: 18617301381
Ref: library/difflib difflib SequenceMatcher get_matching_blocks7303531
Ref: 221f7303531
Ref: library/difflib difflib SequenceMatcher get_opcodes7304448
Ref: 22207304448
Ref: library/difflib difflib SequenceMatcher get_grouped_opcodes7306437
Ref: 22217306437
Ref: library/difflib difflib SequenceMatcher ratio7306870
Ref: 22227306870
Ref: library/difflib difflib SequenceMatcher quick_ratio7307891
Ref: 22237307891
Ref: library/difflib difflib SequenceMatcher real_quick_ratio7308011
Ref: 22247308011
Node: SequenceMatcher 範例7308543
Ref: library/difflib id17308695
Ref: 22257308695
Ref: library/difflib sequencematcher-examples7308695
Ref: 22267308695
Ref: SequenceMatcher 範例-Footnote-17310422
Node: Differ Objects7310499
Ref: library/difflib differ-objects7310643
Ref: 22277310643
Ref: library/difflib id27310643
Ref: 22287310643
Ref: library/difflib difflib Differ compare7312048
Ref: 22187312048
Node: Differ Example7312572
Ref: library/difflib differ-example7312729
Ref: 22297312729
Ref: library/difflib differ-examples7312729
Ref: 222a7312729
Node: A command-line interface to difflib7314989
Ref: library/difflib a-command-line-interface-to-difflib7315147
Ref: 222b7315147
Ref: library/difflib difflib-interface7315147
Ref: 22137315147
Node: ndiff 範例：7317786
Ref: library/difflib ndiff-example7317921
Ref: 222c7317921
Node: textwrap --- 文字包裝與填充7321572
Ref: library/textwrap doc7321768
Ref: 222d7321768
Ref: library/textwrap module-textwrap7321768
Ref: d57321768
Ref: library/textwrap textwrap-text-wrapping-and-filling7321768
Ref: 222e7321768
Ref: library/textwrap textwrap wrap7322281
Ref: 14327322281
Ref: library/textwrap textwrap fill7323016
Ref: 14317323016
Ref: library/textwrap textwrap shorten7323646
Ref: f737323646
Ref: library/textwrap textwrap dedent7324882
Ref: 22347324882
Ref: library/textwrap textwrap indent7325819
Ref: 25b7325819
Ref: library/textwrap textwrap TextWrapper7327158
Ref: f707327158
Ref: library/textwrap textwrap TextWrapper width7327834
Ref: 22367327834
Ref: library/textwrap textwrap TextWrapper expand_tabs7328153
Ref: 22317328153
Ref: library/textwrap textwrap TextWrapper tabsize7328360
Ref: 22307328360
Ref: library/textwrap textwrap TextWrapper replace_whitespace7328647
Ref: 22337328647
Ref: library/textwrap textwrap TextWrapper drop_whitespace7329611
Ref: 22327329611
Ref: library/textwrap textwrap TextWrapper initial_indent7330022
Ref: 22377330022
Ref: library/textwrap textwrap TextWrapper subsequent_indent7330254
Ref: 22387330254
Ref: library/textwrap textwrap TextWrapper fix_sentence_endings7330478
Ref: 22397330478
Ref: library/textwrap textwrap TextWrapper break_long_words7331682
Ref: 22357331682
Ref: library/textwrap textwrap TextWrapper break_on_hyphens7332169
Ref: 223a7332169
Ref: library/textwrap textwrap TextWrapper max_lines7332698
Ref: f717332698
Ref: library/textwrap textwrap TextWrapper placeholder7332942
Ref: f727332942
Ref: library/textwrap textwrap TextWrapper wrap7333255
Ref: 222f7333255
Ref: library/textwrap textwrap TextWrapper fill7333677
Ref: 223b7333677
Ref: textwrap --- 文字包裝與填充-Footnote-17333864
Node: unicodedata --- Unicode 資料庫7333932
Ref: library/unicodedata doc7334128
Ref: 223c7334128
Ref: library/unicodedata module-unicodedata7334128
Ref: ee7334128
Ref: library/unicodedata unicodedata-unicode-database7334128
Ref: 223d7334128
Ref: library/unicodedata unicodedata lookup7334649
Ref: 10197334649
Ref: library/unicodedata unicodedata name7334962
Ref: 223e7334962
Ref: library/unicodedata unicodedata decimal7335186
Ref: 223f7335186
Ref: library/unicodedata unicodedata digit7335427
Ref: 22407335427
Ref: library/unicodedata unicodedata numeric7335663
Ref: 11fb7335663
Ref: library/unicodedata unicodedata category7335901
Ref: 22417335901
Ref: library/unicodedata unicodedata bidirectional7336024
Ref: 22427336024
Ref: library/unicodedata unicodedata combining7336214
Ref: 22437336214
Ref: library/unicodedata unicodedata east_asian_width7336399
Ref: 22447336399
Ref: library/unicodedata unicodedata mirrored7336530
Ref: 22457336530
Ref: library/unicodedata unicodedata decomposition7336782
Ref: 22467336782
Ref: library/unicodedata unicodedata normalize7336995
Ref: 6797336995
Ref: library/unicodedata unicodedata is_normalized7338837
Ref: 9ec7338837
Ref: library/unicodedata unicodedata unidata_version7339128
Ref: 22477339128
Ref: library/unicodedata unicodedata ucd_3_2_07339232
Ref: 13a17339232
Ref: unicodedata --- Unicode 資料庫-Footnote-17340026
Ref: unicodedata --- Unicode 資料庫-Footnote-27340076
Ref: unicodedata --- Unicode 資料庫-Footnote-37340122
Ref: unicodedata --- Unicode 資料庫-Footnote-47340194
Node: stringprep --- 網際網路字串準備7340269
Ref: library/stringprep doc7340463
Ref: 22487340463
Ref: library/stringprep module-stringprep7340463
Ref: bf7340463
Ref: library/stringprep stringprep-internet-string-preparation7340463
Ref: 22497340463
Ref: library/stringprep stringprep in_table_a17342349
Ref: 224a7342349
Ref: library/stringprep stringprep in_table_b17342484
Ref: 224b7342484
Ref: library/stringprep stringprep map_table_b27342608
Ref: 224c7342608
Ref: library/stringprep stringprep map_table_b37342763
Ref: 224d7342763
Ref: library/stringprep stringprep in_table_c117342930
Ref: 224e7342930
Ref: library/stringprep stringprep in_table_c127343048
Ref: 224f7343048
Ref: library/stringprep stringprep in_table_c11_c127343175
Ref: 22507343175
Ref: library/stringprep stringprep in_table_c217343320
Ref: 22517343320
Ref: library/stringprep stringprep in_table_c227343445
Ref: 22527343445
Ref: library/stringprep stringprep in_table_c21_c227343574
Ref: 22537343574
Ref: library/stringprep stringprep in_table_c37343721
Ref: 22547343721
Ref: library/stringprep stringprep in_table_c47343825
Ref: 22557343825
Ref: library/stringprep stringprep in_table_c57343948
Ref: 22567343948
Ref: library/stringprep stringprep in_table_c67344056
Ref: 22577344056
Ref: library/stringprep stringprep in_table_c77344182
Ref: 22587344182
Ref: library/stringprep stringprep in_table_c87344322
Ref: 22597344322
Ref: library/stringprep stringprep in_table_c97344463
Ref: 225a7344463
Ref: library/stringprep stringprep in_table_d17344574
Ref: 225b7344574
Ref: library/stringprep stringprep in_table_d27344722
Ref: 225c7344722
Ref: stringprep --- 網際網路字串準備-Footnote-17344898
Ref: stringprep --- 網際網路字串準備-Footnote-27344968
Ref: stringprep --- 網際網路字串準備-Footnote-37345027
Node: readline --- GNU readline 介面7345086
Ref: library/readline doc7345291
Ref: 225d7345291
Ref: library/readline module-readline7345291
Ref: a87345291
Ref: library/readline readline-gnu-readline-interface7345291
Ref: 225e7345291
Ref: library/readline readline backend7347477
Ref: 15a77347477
Ref: readline --- GNU readline 介面-Footnote-17347802
Node: Init file7347887
Ref: library/readline init-file7347985
Ref: 225f7347985
Ref: library/readline readline parse_and_bind7348095
Ref: 22607348095
Ref: library/readline readline read_init_file7348274
Ref: 22617348274
Node: Line buffer7348494
Ref: library/readline line-buffer7348613
Ref: 22627348613
Ref: library/readline readline get_line_buffer7348707
Ref: 22637348707
Ref: library/readline readline insert_text7348856
Ref: 22647348856
Ref: library/readline readline redisplay7349064
Ref: 14307349064
Node: History file7349265
Ref: library/readline history-file7349387
Ref: 22657349387
Ref: library/readline readline read_history_file7349482
Ref: 22667349482
Ref: library/readline readline write_history_file7349718
Ref: 22677349718
Ref: library/readline readline append_history_file7349973
Ref: df37349973
Ref: library/readline readline get_history_length7350380
Ref: 22687350380
Ref: library/readline readline set_history_length7350423
Ref: 14e97350423
Node: History list7350784
Ref: library/readline history-list7350908
Ref: 22697350908
Ref: library/readline readline clear_history7351010
Ref: 226a7351010
Ref: library/readline readline get_current_history_length7351256
Ref: 142f7351256
Ref: library/readline readline get_history_item7351519
Ref: 142e7351519
Ref: library/readline readline remove_history_item7351727
Ref: 226b7351727
Ref: library/readline readline replace_history_item7351945
Ref: 226c7351945
Ref: library/readline readline add_history7352174
Ref: 226d7352174
Ref: library/readline readline set_auto_history7352356
Ref: c717352356
Node: Startup hooks7352810
Ref: library/readline startup-hooks7352932
Ref: 226e7352932
Ref: library/readline readline set_startup_hook7352977
Ref: 226f7352977
Ref: library/readline readline set_pre_input_hook7353379
Ref: 22707353379
Node: Completion7353949
Ref: library/readline completion7354065
Ref: 22717354065
Ref: library/readline readline-completion7354065
Ref: 22727354065
Ref: library/readline readline set_completer7354551
Ref: 22737354551
Ref: library/readline readline get_completer7355340
Ref: 22747355340
Ref: library/readline readline get_completion_type7355471
Ref: 22757355471
Ref: library/readline readline get_begidx7355669
Ref: 17e97355669
Ref: library/readline readline get_endidx7355704
Ref: 17ea7355704
Ref: library/readline readline set_completer_delims7356147
Ref: 15ab7356147
Ref: library/readline readline get_completer_delims7356198
Ref: 22767356198
Ref: library/readline readline set_completion_display_matches_hook7356517
Ref: 22777356517
Node: 範例7357104
Ref: library/readline example7357198
Ref: 22787357198
Ref: library/readline readline-example7357198
Ref: 22797357198
Node: rlcompleter --- GNU readline 的補全函式7359828
Ref: library/rlcompleter doc7359985
Ref: 227b7359985
Ref: library/rlcompleter module-rlcompleter7359985
Ref: ab7359985
Ref: library/rlcompleter rlcompleter-completion-function-for-gnu-readline7359985
Ref: 227c7359985
Ref: library/rlcompleter completer-objects7361450
Ref: 227e7361450
Ref: library/rlcompleter rlcompleter Completer7361450
Ref: 18467361450
Ref: library/rlcompleter rlcompleter Completer complete7361536
Ref: 227d7361536
Ref: rlcompleter --- GNU readline 的補全函式-Footnote-17362572
Node: 二進位資料服務7362643
Ref: library/binary doc7362805
Ref: 227f7362805
Ref: library/binary binary-data-services7362805
Ref: 22807362805
Ref: library/binary binaryservices7362805
Ref: 219a7362805
Node: struct --- 將位元組直譯為打包起來的二進位資料7363680
Ref: library/struct doc7363856
Ref: 22817363856
Ref: library/struct struct-interpret-bytes-as-packed-binary-data7363856
Ref: 22827363856
Ref: library/struct module-struct7363984
Ref: c07363984
Ref: struct --- 將位元組直譯為打包起來的二進位資料-Footnote-17365759
Node: 函式與例外7365825
Ref: library/struct functions-and-exceptions7365962
Ref: 22857365962
Ref: library/struct struct error7366065
Ref: 12b77366065
Ref: library/struct struct pack7366188
Ref: 120f7366188
Ref: library/struct struct pack_into7366429
Ref: 22867366429
Ref: library/struct struct unpack7366727
Ref: 16cb7366727
Ref: library/struct struct unpack_from7367090
Ref: 22877367090
Ref: library/struct struct iter_unpack7367482
Ref: f617367482
Ref: library/struct struct calcsize7368000
Ref: 18c97368000
Node: Format Strings7368197
Ref: library/struct format-strings7368355
Ref: 22887368355
Ref: library/struct struct-format-strings7368355
Ref: 22837368355
Node: Byte Order Size and Alignment7368989
Ref: library/struct byte-order-size-and-alignment7369095
Ref: 228a7369095
Ref: library/struct struct-alignment7369095
Ref: 22847369095
Ref: Byte Order Size and Alignment-Footnote-17372794
Node: Format Characters7372848
Ref: library/struct format-characters7372972
Ref: 22897372972
Ref: library/struct id17372972
Ref: 228c7372972
Ref: Format Characters-Footnote-17384461
Ref: Format Characters-Footnote-27384522
Node: 範例<2>7384598
Ref: library/struct examples7384684
Ref: 228d7384684
Ref: library/struct struct-examples7384684
Ref: 228b7384684
Node: Applications7387183
Ref: library/struct applications7387336
Ref: 228e7387336
Ref: library/struct id27387336
Ref: 228f7387336
Node: Native Formats7387837
Ref: library/struct native-formats7387925
Ref: 22927387925
Ref: library/struct struct-native-formats7387925
Ref: 22907387925
Node: Standard Formats7389073
Ref: library/struct standard-formats7389161
Ref: 22937389161
Ref: library/struct struct-standard-formats7389161
Ref: 22917389161
Node: Classes<2>7390600
Ref: library/struct classes7390730
Ref: 22947390730
Ref: library/struct struct-objects7390730
Ref: 22957390730
Ref: library/struct struct Struct7390826
Ref: 15a97390826
Ref: library/struct struct Struct pack7391523
Ref: 22967391523
Ref: library/struct struct Struct pack_into7391705
Ref: 22987391705
Ref: library/struct struct Struct unpack7391863
Ref: 22997391863
Ref: library/struct struct Struct unpack_from7392061
Ref: 229a7392061
Ref: library/struct struct Struct iter_unpack7392317
Ref: f627392317
Ref: library/struct struct Struct format7392568
Ref: bad7392568
Ref: library/struct struct Struct size7392778
Ref: 22977392778
Node: codecs --- 編解碼器註冊表和基底類別7393104
Ref: library/codecs doc7393280
Ref: 229b7393280
Ref: library/codecs codecs-codec-registry-and-base-classes7393280
Ref: 229c7393280
Ref: library/codecs module-codecs7393280
Ref: 147393280
Ref: library/codecs codecs encode7394169
Ref: ea57394169
Ref: library/codecs codecs decode7394662
Ref: ea67394662
Ref: library/codecs codecs lookup7395220
Ref: 9077395220
Ref: library/codecs codecs CodecInfo7395714
Ref: 15f67395714
Ref: library/codecs codecs CodecInfo name7396011
Ref: 229e7396011
Ref: library/codecs codecs CodecInfo encode7396071
Ref: 229f7396071
Ref: library/codecs codecs CodecInfo decode7396095
Ref: 22a07396095
Ref: library/codecs codecs CodecInfo incrementalencoder7396470
Ref: 22a47396470
Ref: library/codecs codecs CodecInfo incrementaldecoder7396506
Ref: 22a57396506
Ref: library/codecs codecs CodecInfo streamwriter7396842
Ref: 22a87396842
Ref: library/codecs codecs CodecInfo streamreader7396872
Ref: 22a97396872
Ref: library/codecs codecs getencoder7397322
Ref: 22ac7397322
Ref: library/codecs codecs getdecoder7397532
Ref: 22ad7397532
Ref: library/codecs codecs getincrementalencoder7397742
Ref: 22ae7397742
Ref: library/codecs codecs getincrementaldecoder7398044
Ref: 22af7398044
Ref: library/codecs codecs getreader7398346
Ref: 22b07398346
Ref: library/codecs codecs getwriter7398590
Ref: 22b17398590
Ref: library/codecs codecs register7398917
Ref: 22b27398917
Ref: library/codecs codecs unregister7399383
Ref: 78c7399383
Ref: library/codecs codecs open7399877
Ref: 6e47399877
Ref: library/codecs codecs EncodedFile7401248
Ref: 22b47401248
Ref: library/codecs codecs iterencode7402103
Ref: 22b57402103
Ref: library/codecs codecs iterdecode7402632
Ref: 22b67402632
Ref: library/codecs codecs BOM7403353
Ref: 22b77403353
Ref: library/codecs codecs BOM_BE7403376
Ref: 22b87403376
Ref: library/codecs codecs BOM_LE7403402
Ref: 22b97403402
Ref: library/codecs codecs BOM_UTF87403428
Ref: 22ba7403428
Ref: library/codecs codecs BOM_UTF167403456
Ref: 22bb7403456
Ref: library/codecs codecs BOM_UTF16_BE7403485
Ref: 22bc7403485
Ref: library/codecs codecs BOM_UTF16_LE7403517
Ref: 22bd7403517
Ref: library/codecs codecs BOM_UTF327403549
Ref: 22be7403549
Ref: library/codecs codecs BOM_UTF32_BE7403578
Ref: 22bf7403578
Ref: library/codecs codecs BOM_UTF32_LE7403610
Ref: 22c07403610
Ref: codecs --- 編解碼器註冊表和基底類別-Footnote-17404745
Node: Codec Base Classes7404811
Ref: library/codecs codec-base-classes7404943
Ref: 229d7404943
Ref: library/codecs id17404943
Ref: 22c17404943
Ref: library/codecs surrogateescape7405536
Ref: 22c27405536
Node: Error Handlers7405673
Ref: library/codecs error-handlers7405782
Ref: 16eb7405782
Ref: library/codecs id27405782
Ref: 22c37405782
Ref: library/codecs codecs register_error7410695
Ref: 14047410695
Ref: library/codecs codecs lookup_error7412235
Ref: 14057412235
Ref: library/codecs codecs strict_errors7412528
Ref: 22c47412528
Ref: library/codecs codecs ignore_errors7412699
Ref: 22c57412699
Ref: library/codecs codecs replace_errors7412893
Ref: 22c67412893
Ref: library/codecs codecs backslashreplace_errors7413141
Ref: 22c77413141
Ref: library/codecs codecs xmlcharrefreplace_errors7413599
Ref: 22c87413599
Ref: library/codecs codecs namereplace_errors7413961
Ref: 22c97413961
Ref: Error Handlers-Footnote-17414522
Node: Stateless Encoding and Decoding7414564
Ref: library/codecs codec-objects7414715
Ref: 22a37414715
Ref: library/codecs stateless-encoding-and-decoding7414715
Ref: 22ca7414715
Ref: library/codecs codecs Codec7414933
Ref: 22cb7414933
Ref: library/codecs codecs Codec encode7414959
Ref: 22a17414959
Ref: library/codecs codecs Codec decode7415779
Ref: 22a27415779
Node: Incremental Encoding and Decoding7416807
Ref: library/codecs incremental-encoding-and-decoding7416972
Ref: 22cc7416972
Node: IncrementalEncoder 物件7417808
Ref: library/codecs incremental-encoder-objects7417937
Ref: 22cf7417937
Ref: library/codecs incrementalencoder-objects7417937
Ref: 22d07417937
Ref: library/codecs codecs IncrementalEncoder7418232
Ref: 22a67418232
Ref: library/codecs codecs IncrementalEncoder encode7419018
Ref: 22cd7419018
Ref: library/codecs codecs IncrementalEncoder reset7419315
Ref: 22d17419315
Ref: library/codecs codecs IncrementalEncoder getstate7419584
Ref: 22d27419584
Ref: library/codecs codecs IncrementalEncoder setstate7419997
Ref: 22d37419997
Node: IncrementalDecoder 物件7420164
Ref: library/codecs incremental-decoder-objects7420293
Ref: 22d47420293
Ref: library/codecs incrementaldecoder-objects7420293
Ref: 22d57420293
Ref: library/codecs codecs IncrementalDecoder7420588
Ref: 22a77420588
Ref: library/codecs codecs IncrementalDecoder decode7421374
Ref: 22ce7421374
Ref: library/codecs codecs IncrementalDecoder reset7422005
Ref: 22d67422005
Ref: library/codecs codecs IncrementalDecoder getstate7422083
Ref: 22d77422083
Ref: library/codecs codecs IncrementalDecoder setstate7423030
Ref: 22d87423030
Node: Stream Encoding and Decoding7423196
Ref: library/codecs stream-encoding-and-decoding7423321
Ref: 22d97423321
Node: StreamWriter 物件7423744
Ref: library/codecs stream-writer-objects7423856
Ref: 22da7423856
Ref: library/codecs streamwriter-objects7423856
Ref: 22db7423856
Ref: library/codecs codecs StreamWriter7424114
Ref: 22aa7424114
Ref: library/codecs codecs StreamWriter write7425072
Ref: 22dc7425072
Ref: library/codecs codecs StreamWriter writelines7425168
Ref: 22dd7425168
Ref: library/codecs codecs StreamWriter reset7425474
Ref: 22de7425474
Node: StreamReader 物件7425943
Ref: library/codecs stream-reader-objects7426089
Ref: 22df7426089
Ref: library/codecs streamreader-objects7426089
Ref: 22e07426089
Ref: library/codecs codecs StreamReader7426347
Ref: 22ab7426347
Ref: library/codecs codecs StreamReader read7427419
Ref: 22e17427419
Ref: library/codecs codecs StreamReader readline7428677
Ref: 22e27428677
Ref: library/codecs codecs StreamReader readlines7429026
Ref: 22e37429026
Ref: library/codecs codecs StreamReader reset7429473
Ref: 22e47429473
Node: StreamReaderWriter 物件7429876
Ref: library/codecs stream-reader-writer7430023
Ref: 22e57430023
Ref: library/codecs streamreaderwriter-objects7430023
Ref: 22e67430023
Ref: library/codecs codecs StreamReaderWriter7430354
Ref: 22b37430354
Node: StreamRecoder 物件7431010
Ref: library/codecs stream-recoder-objects7431129
Ref: 22e77431129
Ref: library/codecs streamrecoder-objects7431129
Ref: 22e87431129
Ref: library/codecs codecs StreamRecoder7431475
Ref: 18f67431475
Node: Encodings and Unicode7432630
Ref: library/codecs encodings-and-unicode7432789
Ref: 22e97432789
Ref: library/codecs encodings-overview7432789
Ref: 22ea7432789
Ref: Encodings and Unicode-Footnote-17439435
Node: Standard Encodings7439477
Ref: library/codecs id37439643
Ref: 22eb7439643
Ref: library/codecs standard-encodings7439643
Ref: d5f7439643
Node: Python Specific Encodings7461763
Ref: library/codecs python-specific-encodings7461973
Ref: 22ec7461973
Node: Text Encodings7462561
Ref: library/codecs text-encodings7462663
Ref: 22ed7462663
Ref: Text Encodings-Footnote-17466030
Ref: Text Encodings-Footnote-27466089
Node: Binary Transforms7466148
Ref: library/codecs binary-transforms7466274
Ref: ea77466274
Ref: library/codecs id47466274
Ref: 22ee7466274
Ref: Binary Transforms-Footnote-17469908
Node: Text Transforms7470049
Ref: library/codecs id67470152
Ref: 22f47470152
Ref: library/codecs text-transforms7470152
Ref: ea87470152
Node: encodings idna --- Internationalized Domain Names in Applications7470895
Ref: library/codecs encodings-idna-internationalized-domain-names-in-applications7471127
Ref: 22f57471127
Ref: library/codecs module-encodings idna7471127
Ref: 487471127
Ref: library/codecs encodings idna nameprep7473742
Ref: 22f67473742
Ref: library/codecs encodings idna ToASCII7473928
Ref: 22f77473928
Ref: library/codecs encodings idna ToUnicode7474086
Ref: 22f87474086
Ref: encodings idna --- Internationalized Domain Names in Applications-Footnote-17474231
Ref: encodings idna --- Internationalized Domain Names in Applications-Footnote-27474290
Ref: encodings idna --- Internationalized Domain Names in Applications-Footnote-37474349
Ref: encodings idna --- Internationalized Domain Names in Applications-Footnote-47474408
Ref: encodings idna --- Internationalized Domain Names in Applications-Footnote-57474467
Ref: encodings idna --- Internationalized Domain Names in Applications-Footnote-67474506
Ref: encodings idna --- Internationalized Domain Names in Applications-Footnote-77474577
Ref: encodings idna --- Internationalized Domain Names in Applications-Footnote-87474636
Node: encodings mbcs --- Windows ANSI codepage7474695
Ref: library/codecs encodings-mbcs-windows-ansi-codepage7474956
Ref: 22f97474956
Ref: library/codecs module-encodings mbcs7474956
Ref: 497474956
Node: encodings utf_8_sig --- UTF-8 codec with BOM signature7475342
Ref: library/codecs encodings-utf-8-sig-utf-8-codec-with-bom-signature7475529
Ref: 22fa7475529
Ref: library/codecs module-encodings utf_8_sig7475529
Ref: 4a7475529
Node: 資料型別7475974
Ref: library/datatypes doc7476122
Ref: 22fb7476122
Ref: library/datatypes data-types7476122
Ref: 22fc7476122
Ref: library/datatypes datatypes7476122
Ref: 22fd7476122
Node: datetime --- 日期與時間的基本型別7477993
Ref: library/datetime doc7478124
Ref: 22fe7478124
Ref: library/datetime datetime-basic-date-and-time-types7478124
Ref: 22ff7478124
Ref: library/datetime module-datetime7478124
Ref: 287478124
Ref: datetime --- 日期與時間的基本型別-Footnote-17479415
Ref: datetime --- 日期與時間的基本型別-Footnote-27479483
Ref: datetime --- 日期與時間的基本型別-Footnote-37479534
Node: Aware and Naive Objects7479577
Ref: library/datetime aware-and-naive-objects7479695
Ref: 23017479695
Ref: library/datetime datetime-naive-aware7479695
Ref: 23027479695
Ref: Aware and Naive Objects-Footnote-17481609
Node: 常數7481666
Ref: library/datetime constants7481808
Ref: 23037481808
Ref: library/datetime datetime MINYEAR7481881
Ref: 23047481881
Ref: library/datetime datetime MAXYEAR7482037
Ref: 23057482037
Ref: library/datetime datetime UTC7482195
Ref: 4967482195
Node: Available Types7482333
Ref: library/datetime available-types7482468
Ref: 23067482468
Node: 常見屬性7484211
Ref: library/datetime common-properties7484326
Ref: 23177484326
Node: Determining if an Object is Aware or Naive7484734
Ref: library/datetime determining-if-an-object-is-aware-or-naive7484849
Ref: 23187484849
Node: timedelta 物件7485584
Ref: library/datetime datetime-timedelta7485724
Ref: 23197485724
Ref: library/datetime timedelta-objects7485724
Ref: 231a7485724
Ref: library/datetime datetime timedelta7485918
Ref: 9737485918
Ref: library/datetime datetime timedelta min7488147
Ref: 231b7488147
Ref: library/datetime datetime timedelta max7488262
Ref: 231c7488262
Ref: library/datetime datetime timedelta resolution7488441
Ref: 231d7488441
Ref: library/datetime datetime timedelta days7488809
Ref: 231e7488809
Ref: library/datetime datetime timedelta seconds7488892
Ref: 231f7488892
Ref: library/datetime datetime timedelta microseconds7488962
Ref: 23207488962
Ref: library/datetime datetime timedelta total_seconds7494880
Ref: 12997494880
Node: 用法範例：timedelta7495372
Ref: library/datetime examples-of-usage-timedelta7495449
Ref: 23217495449
Node: date 物件7496377
Ref: library/datetime date-objects7496517
Ref: 23227496517
Ref: library/datetime datetime-date7496517
Ref: 23237496517
Ref: library/datetime datetime date7496835
Ref: 1b17496835
Ref: library/datetime datetime date today7497255
Ref: 14397497255
Ref: library/datetime datetime date fromtimestamp7497391
Ref: 14fd7497391
Ref: library/datetime datetime date fromordinal7498325
Ref: 23247498325
Ref: library/datetime datetime date fromisoformat7498658
Ref: 5ba7498658
Ref: library/datetime datetime date fromisocalendar7499565
Ref: 9907499565
Ref: library/datetime datetime date min7499856
Ref: 23257499856
Ref: library/datetime datetime date max7499944
Ref: 23267499944
Ref: library/datetime datetime date resolution7500032
Ref: 23277500032
Ref: library/datetime datetime date year7500196
Ref: 23077500196
Ref: library/datetime datetime date month7500290
Ref: 23087500290
Ref: library/datetime datetime date day7500352
Ref: 23097500352
Ref: library/datetime datetime date replace7503181
Ref: 15737503181
Ref: library/datetime datetime date timetuple7503659
Ref: 23287503659
Ref: library/datetime datetime date toordinal7504149
Ref: 23297504149
Ref: library/datetime datetime date weekday7504371
Ref: 232a7504371
Ref: library/datetime datetime date isoweekday7504592
Ref: 232b7504592
Ref: library/datetime datetime date isocalendar7504851
Ref: 89a7504851
Ref: library/datetime datetime date isoformat7505924
Ref: 232c7505924
Ref: library/datetime datetime date __str__7506140
Ref: 232d7506140
Ref: library/datetime datetime date ctime7506242
Ref: 232e7506242
Ref: library/datetime datetime date strftime7506711
Ref: c387506711
Ref: library/datetime datetime date __format__7507013
Ref: 23307507013
Ref: date 物件-Footnote-17507438
Ref: date 物件-Footnote-27507739
Node: 用法範例：date7507953
Ref: library/datetime examples-of-usage-date7508020
Ref: 23317508020
Node: datetime 物件7509905
Ref: library/datetime datetime-datetime7510040
Ref: 23327510040
Ref: library/datetime datetime-objects7510040
Ref: 23337510040
Ref: library/datetime datetime datetime7510485
Ref: 1b07510485
Ref: library/datetime datetime datetime today7511344
Ref: 23347511344
Ref: library/datetime datetime datetime now7511712
Ref: 4947511712
Ref: library/datetime datetime datetime utcnow7512360
Ref: 2cd7512360
Ref: library/datetime datetime datetime fromtimestamp7513200
Ref: 4957513200
Ref: library/datetime datetime datetime utcfromtimestamp7514904
Ref: 2ce7514904
Ref: library/datetime datetime datetime fromordinal7516681
Ref: 23357516681
Ref: library/datetime datetime datetime combine7517086
Ref: c397517086
Ref: library/datetime datetime datetime fromisoformat7517871
Ref: 5bc7517871
Ref: library/datetime datetime datetime fromisocalendar7519969
Ref: 9917519969
Ref: library/datetime datetime datetime strptime7520349
Ref: 14fe7520349
Ref: library/datetime datetime datetime min7521796
Ref: 16e07521796
Ref: library/datetime datetime datetime max7521925
Ref: 23367521925
Ref: library/datetime datetime datetime resolution7522074
Ref: 23377522074
Ref: library/datetime datetime datetime year7522266
Ref: 230f7522266
Ref: library/datetime datetime datetime month7522364
Ref: 23107522364
Ref: library/datetime datetime datetime day7522430
Ref: 23117522430
Ref: library/datetime datetime datetime hour7522538
Ref: 23127522538
Ref: library/datetime datetime datetime minute7522591
Ref: 23137522591
Ref: library/datetime datetime datetime second7522646
Ref: 23147522646
Ref: library/datetime datetime datetime microsecond7522701
Ref: 23157522701
Ref: library/datetime datetime datetime tzinfo7522766
Ref: 23167522766
Ref: library/datetime datetime datetime fold7522924
Ref: bfe7522924
Ref: library/datetime datetime datetime date7527918
Ref: 23387527918
Ref: library/datetime datetime datetime time7528016
Ref: 23397528016
Ref: library/datetime datetime datetime timetz7528321
Ref: 233a7528321
Ref: library/datetime datetime datetime replace7528608
Ref: 143a7528608
Ref: library/datetime datetime datetime astimezone7529291
Ref: 9747529291
Ref: library/datetime datetime datetime utcoffset7531637
Ref: 233b7531637
Ref: library/datetime datetime datetime dst7532027
Ref: 233c7532027
Ref: library/datetime datetime datetime tzname7532405
Ref: 233e7532405
Ref: library/datetime datetime datetime timetuple7532636
Ref: 233f7532636
Ref: library/datetime datetime datetime utctimetuple7533480
Ref: 23417533480
Ref: library/datetime datetime datetime toordinal7534636
Ref: 23427534636
Ref: library/datetime datetime datetime timestamp7534778
Ref: 103b7534778
Ref: library/datetime datetime datetime weekday7536323
Ref: 23437536323
Ref: library/datetime datetime datetime isoweekday7536527
Ref: 23447536527
Ref: library/datetime datetime datetime isocalendar7536760
Ref: 89b7536760
Ref: library/datetime datetime datetime isoformat7536952
Ref: ad47536952
Ref: library/datetime datetime datetime __str__7539966
Ref: 23457539966
Ref: library/datetime datetime datetime ctime7540105
Ref: 23467540105
Ref: library/datetime datetime datetime strftime7540733
Ref: c377540733
Ref: library/datetime datetime datetime __format__7540974
Ref: 23477540974
Node: 用法範例：datetime7541382
Ref: library/datetime examples-of-usage-datetime7541457
Ref: 23487541457
Node: time 物件7545764
Ref: library/datetime datetime-time7545901
Ref: 23497545901
Ref: library/datetime time-objects7545901
Ref: 234a7545901
Ref: library/datetime datetime time7546105
Ref: 1b27546105
Ref: library/datetime datetime time min7546758
Ref: 234b7546758
Ref: library/datetime datetime time max7546854
Ref: 234c7546854
Ref: library/datetime datetime time resolution7546961
Ref: 234d7546961
Ref: library/datetime datetime time hour7547226
Ref: 230a7547226
Ref: library/datetime datetime time minute7547275
Ref: 230b7547275
Ref: library/datetime datetime time second7547326
Ref: 230c7547326
Ref: library/datetime datetime time microsecond7547377
Ref: 230d7547377
Ref: library/datetime datetime time tzinfo7547438
Ref: 230e7547438
Ref: library/datetime datetime time fold7547586
Ref: 234e7547586
Ref: library/datetime datetime time fromisoformat7549157
Ref: 5bb7549157
Ref: library/datetime datetime time replace7550742
Ref: 15747550742
Ref: library/datetime datetime time isoformat7551373
Ref: 234f7551373
Ref: library/datetime datetime time __str__7553386
Ref: 23517553386
Ref: library/datetime datetime time strftime7553488
Ref: 16867553488
Ref: library/datetime datetime time __format__7553713
Ref: 23527553713
Ref: library/datetime datetime time utcoffset7554069
Ref: 23507554069
Ref: library/datetime datetime time dst7554455
Ref: 23537554455
Ref: library/datetime datetime time tzname7554830
Ref: 23547554830
Ref: time 物件-Footnote-17555130
Node: 用法範例：time7555195
Ref: library/datetime examples-of-usage-time7555262
Ref: 23557555262
Node: tzinfo 物件7556131
Ref: library/datetime datetime-tzinfo7556268
Ref: 23567556268
Ref: library/datetime tzinfo-objects7556268
Ref: 23577556268
Ref: library/datetime datetime tzinfo7556321
Ref: 5827556321
Ref: library/datetime datetime tzinfo utcoffset7557956
Ref: 23587557956
Ref: library/datetime datetime tzinfo dst7559182
Ref: 23597559182
Ref: library/datetime datetime tzinfo tzname7561765
Ref: 235a7561765
Ref: library/datetime datetime tzinfo fromutc7563904
Ref: 233d7563904
Ref: tzinfo 物件-Footnote-17576404
Node: timezone 物件7576444
Ref: library/datetime datetime-timezone7576601
Ref: 235b7576601
Ref: library/datetime timezone-objects7576601
Ref: 235c7576601
Ref: library/datetime datetime timezone7577020
Ref: 10597577020
Ref: library/datetime datetime timezone utcoffset7577649
Ref: 235d7577649
Ref: library/datetime datetime timezone tzname7578038
Ref: 235e7578038
Ref: library/datetime datetime timezone dst7578711
Ref: 235f7578711
Ref: library/datetime datetime timezone fromutc7578775
Ref: 23607578775
Ref: library/datetime datetime timezone utc7578968
Ref: 5b97578968
Node: strftime 與 strptime 的行為7579045
Ref: library/datetime strftime-and-strptime-behavior7579180
Ref: 23617579180
Ref: library/datetime strftime-strptime-behavior7579180
Ref: 16ce7579180
Ref: library/datetime format-codes7581274
Ref: 23007581274
Node: strftime 與 strptime 格式碼7581373
Ref: library/datetime strftime-and-strptime-format-codes7581493
Ref: 23627581493
Ref: strftime 與 strptime 格式碼-Footnote-17592405
Node: 技術細節7592453
Ref: library/datetime technical-detail7592573
Ref: 23637592573
Ref: 技術細節-Footnote-17599467
Ref: 技術細節-Footnote-27599567
Node: zoneinfo --- IANA 時區支援7599622
Ref: library/zoneinfo doc7599793
Ref: 23647599793
Ref: library/zoneinfo module-zoneinfo7599793
Ref: 11a7599793
Ref: library/zoneinfo zoneinfo-iana-time-zone-support7599793
Ref: 23657599793
Ref: zoneinfo --- IANA 時區支援-Footnote-17600997
Ref: zoneinfo --- IANA 時區支援-Footnote-27601062
Ref: zoneinfo --- IANA 時區支援-Footnote-37601104
Ref: zoneinfo --- IANA 時區支援-Footnote-47601145
Node: Using ZoneInfo7601186
Ref: library/zoneinfo using-zoneinfo7601288
Ref: 23667601288
Ref: Using ZoneInfo-Footnote-17603236
Node: Data sources7603278
Ref: library/zoneinfo data-sources7603407
Ref: 23677603407
Ref: Data sources-Footnote-17604091
Node: Configuring the data sources7604132
Ref: library/zoneinfo configuring-the-data-sources7604209
Ref: 23697604209
Ref: library/zoneinfo zoneinfo-data-configuration7604209
Ref: 236a7604209
Node: Compile-time configuration7604962
Ref: library/zoneinfo compile-time-configuration7605087
Ref: 236e7605087
Ref: library/zoneinfo zoneinfo-data-compile-time-config7605087
Ref: 1c737605087
Node: Environment configuration7605817
Ref: library/zoneinfo environment-configuration7605972
Ref: 236f7605972
Ref: library/zoneinfo zoneinfo-data-environment-var7605972
Ref: 236b7605972
Ref: library/zoneinfo envvar-PYTHONTZPATH7606291
Ref: 23707606291
Node: Runtime configuration7606944
Ref: library/zoneinfo runtime-configuration7607064
Ref: 23727607064
Ref: library/zoneinfo zoneinfo-data-runtime-config7607064
Ref: 236c7607064
Node: The ZoneInfo class7607432
Ref: library/zoneinfo the-zoneinfo-class7607556
Ref: 23737607556
Ref: library/zoneinfo zoneinfo ZoneInfo7607619
Ref: 8847607619
Ref: library/zoneinfo zoneinfo ZoneInfo from_file7608500
Ref: 23757608500
Ref: library/zoneinfo zoneinfo ZoneInfo no_cache7609029
Ref: 23777609029
Ref: library/zoneinfo zoneinfo ZoneInfo clear_cache7609748
Ref: 23747609748
Ref: library/zoneinfo zoneinfo ZoneInfo key7610544
Ref: 23787610544
Node: String representations7611399
Ref: library/zoneinfo string-representations7611505
Ref: 237a7611505
Node: Pickle serialization7612312
Ref: library/zoneinfo pickle-serialization7612418
Ref: 237b7612418
Ref: library/zoneinfo pickling7612418
Ref: 23767612418
Node: 函式<2>7614824
Ref: library/zoneinfo functions7614943
Ref: 237c7614943
Ref: library/zoneinfo zoneinfo available_timezones7614974
Ref: 185e7614974
Ref: library/zoneinfo zoneinfo reset_tzpath7615941
Ref: 236d7615941
Node: Globals7616635
Ref: library/zoneinfo globals7616759
Ref: 237d7616759
Ref: library/zoneinfo zoneinfo TZPATH7616794
Ref: 1c727616794
Node: Exceptions and warnings7617569
Ref: library/zoneinfo exceptions-and-warnings7617675
Ref: 237e7617675
Ref: library/zoneinfo zoneinfo ZoneInfoNotFoundError7617742
Ref: 23687617742
Ref: library/zoneinfo zoneinfo InvalidTZPathWarning7617970
Ref: 23717617970
Node: calendar --- 日曆相關函式7618144
Ref: library/calendar doc7618306
Ref: 237f7618306
Ref: library/calendar calendar-general-calendar-related-functions7618306
Ref: 23807618306
Ref: library/calendar module-calendar7618306
Ref: 107618306
Ref: library/calendar calendar Calendar7619367
Ref: 23827619367
Ref: library/calendar calendar Calendar iterweekdays7619834
Ref: 23857619834
Ref: library/calendar calendar Calendar itermonthdates7620037
Ref: bc07620037
Ref: library/calendar calendar Calendar itermonthdays7620327
Ref: 23877620327
Ref: library/calendar calendar Calendar itermonthdays27620659
Ref: 23887620659
Ref: library/calendar calendar Calendar itermonthdays37620985
Ref: bc17620985
Ref: library/calendar calendar Calendar itermonthdays47621312
Ref: bc27621312
Ref: library/calendar calendar Calendar monthdatescalendar7621654
Ref: 23897621654
Ref: library/calendar calendar Calendar monthdays2calendar7621868
Ref: 238a7621868
Ref: library/calendar calendar Calendar monthdayscalendar7622109
Ref: 238b7622109
Ref: library/calendar calendar Calendar yeardatescalendar7622310
Ref: 238c7622310
Ref: library/calendar calendar Calendar yeardays2calendar7622675
Ref: 238d7622675
Ref: library/calendar calendar Calendar yeardayscalendar7622981
Ref: 238e7622981
Ref: library/calendar calendar TextCalendar7623247
Ref: 238f7623247
Ref: library/calendar calendar TextCalendar formatmonth7623408
Ref: 23907623408
Ref: library/calendar calendar TextCalendar prmonth7623819
Ref: 23917623819
Ref: library/calendar calendar TextCalendar formatyear7623983
Ref: 23927623983
Ref: library/calendar calendar TextCalendar pryear7624462
Ref: 23937624462
Ref: library/calendar calendar HTMLCalendar7624621
Ref: ac77624621
Ref: library/calendar calendar HTMLCalendar formatmonth7624769
Ref: 23947624769
Ref: library/calendar calendar HTMLCalendar formatyear7624994
Ref: 23957624994
Ref: library/calendar calendar HTMLCalendar formatyearpage7625167
Ref: 23967625167
Ref: library/calendar calendar HTMLCalendar formatmonthname7625613
Ref: 23977625613
Ref: library/calendar calendar HTMLCalendar cssclasses7625933
Ref: 23987625933
Ref: library/calendar calendar HTMLCalendar cssclass_noday7626334
Ref: 23997626334
Ref: library/calendar calendar HTMLCalendar cssclasses_weekday_head7626501
Ref: 239a7626501
Ref: library/calendar calendar HTMLCalendar cssclass_month_head7626709
Ref: 239b7626709
Ref: library/calendar calendar HTMLCalendar cssclass_month7626911
Ref: 239c7626911
Ref: library/calendar calendar HTMLCalendar cssclass_year7627110
Ref: 239d7627110
Ref: library/calendar calendar HTMLCalendar cssclass_year_head7627300
Ref: 239e7627300
Ref: library/calendar calendar LocaleTextCalendar7628147
Ref: 6e87628147
Ref: library/calendar calendar LocaleHTMLCalendar7628377
Ref: 6e97628377
Ref: library/calendar calendar setfirstweekday7628955
Ref: 23817628955
Ref: library/calendar calendar firstweekday7629406
Ref: 23867629406
Ref: library/calendar calendar isleap7629493
Ref: 23a47629493
Ref: library/calendar calendar leapdays7629623
Ref: 23a57629623
Ref: library/calendar calendar weekday7629829
Ref: 23a67629829
Ref: library/calendar calendar weekheader7630024
Ref: 23a77630024
Ref: library/calendar calendar monthrange7630159
Ref: 23a87630159
Ref: library/calendar calendar monthcalendar7630314
Ref: 23a97630314
Ref: library/calendar calendar prmonth7630571
Ref: 23aa7630571
Ref: library/calendar calendar month7630717
Ref: 23ab7630717
Ref: library/calendar calendar prcal7630911
Ref: 23ac7630911
Ref: library/calendar calendar calendar7631050
Ref: 23ad7631050
Ref: library/calendar calendar timegm7631245
Ref: 23ae7631245
Ref: library/calendar calendar day_name7631658
Ref: 23af7631658
Ref: library/calendar calendar day_abbr7631756
Ref: 23b07631756
Ref: library/calendar calendar MONDAY7631860
Ref: 23837631860
Ref: library/calendar calendar TUESDAY7631888
Ref: 239f7631888
Ref: library/calendar calendar WEDNESDAY7631917
Ref: 23a07631917
Ref: library/calendar calendar THURSDAY7631948
Ref: 23a17631948
Ref: library/calendar calendar FRIDAY7631978
Ref: 23a27631978
Ref: library/calendar calendar SATURDAY7632006
Ref: 23a37632006
Ref: library/calendar calendar SUNDAY7632036
Ref: 23847632036
Ref: library/calendar calendar Day7632191
Ref: 4297632191
Ref: library/calendar calendar month_name7632411
Ref: 23b17632411
Ref: library/calendar calendar month_abbr7632634
Ref: 23b27632634
Ref: library/calendar calendar JANUARY7632862
Ref: 2ca7632862
Ref: library/calendar calendar FEBRUARY7632891
Ref: 2cb7632891
Ref: library/calendar calendar MARCH7632921
Ref: 23b37632921
Ref: library/calendar calendar APRIL7632948
Ref: 23b47632948
Ref: library/calendar calendar MAY7632975
Ref: 23b57632975
Ref: library/calendar calendar JUNE7633000
Ref: 23b67633000
Ref: library/calendar calendar JULY7633026
Ref: 23b77633026
Ref: library/calendar calendar AUGUST7633052
Ref: 23b87633052
Ref: library/calendar calendar SEPTEMBER7633080
Ref: 23b97633080
Ref: library/calendar calendar OCTOBER7633111
Ref: 23ba7633111
Ref: library/calendar calendar NOVEMBER7633140
Ref: 23bb7633140
Ref: library/calendar calendar DECEMBER7633170
Ref: 23bc7633170
Ref: library/calendar calendar Month7633336
Ref: 4287633336
Ref: library/calendar calendar IllegalMonthError7633612
Ref: 23bd7633612
Ref: library/calendar calendar IllegalMonthError month7633774
Ref: 23be7633774
Ref: library/calendar calendar IllegalWeekdayError7633831
Ref: 23bf7633831
Ref: library/calendar calendar IllegalWeekdayError weekday7633998
Ref: 23c07633998
Ref: calendar --- 日曆相關函式-Footnote-17634326
Node: 命令列用法7634394
Ref: library/calendar calendar-cli7634477
Ref: 23c17634477
Ref: library/calendar command-line-usage7634477
Ref: 23c27634477
Ref: library/calendar cmdoption-calendar-help7637167
Ref: 23c37637167
Ref: library/calendar cmdoption-calendar-h7637167
Ref: 23c47637167
Ref: library/calendar cmdoption-calendar-locale7637228
Ref: 23c57637228
Ref: library/calendar cmdoption-calendar-L7637228
Ref: 23c67637228
Ref: library/calendar cmdoption-calendar-encoding7637332
Ref: 23c77637332
Ref: library/calendar cmdoption-calendar-e7637332
Ref: 23c87637332
Ref: library/calendar cmdoption-calendar-type7637489
Ref: 23c97637489
Ref: library/calendar cmdoption-calendar-t7637489
Ref: 23ca7637489
Ref: library/calendar cmdoption-calendar-first-weekday7637607
Ref: 23cb7637607
Ref: library/calendar cmdoption-calendar-f7637607
Ref: 23cc7637607
Ref: library/calendar cmdoption-calendar-arg-year7637809
Ref: 23cd7637809
Ref: library/calendar cmdoption-calendar-arg-month7637900
Ref: 23ce7637900
Ref: library/calendar cmdoption-calendar-width7638115
Ref: 23cf7638115
Ref: library/calendar cmdoption-calendar-w7638115
Ref: 23d07638115
Ref: library/calendar cmdoption-calendar-lines7638284
Ref: 23d17638284
Ref: library/calendar cmdoption-calendar-l7638284
Ref: 23d27638284
Ref: library/calendar cmdoption-calendar-spacing7638453
Ref: 23d37638453
Ref: library/calendar cmdoption-calendar-s7638453
Ref: 23d47638453
Ref: library/calendar cmdoption-calendar-months7638586
Ref: 23d57638586
Ref: library/calendar cmdoption-calendar-m7638586
Ref: 23d67638586
Ref: library/calendar cmdoption-calendar-css7638701
Ref: 23d77638701
Ref: library/calendar cmdoption-calendar-c7638701
Ref: 23d87638701
Node: collections --- 容器資料型態7638874
Ref: library/collections doc7639053
Ref: 23d97639053
Ref: library/collections collections-container-datatypes7639053
Ref: 23da7639053
Ref: library/collections module-collections7639053
Ref: 167639053
Ref: collections --- 容器資料型態-Footnote-17641199
Node: ChainMap 物件7641280
Ref: library/collections chainmap-objects7641389
Ref: 23db7641389
Ref: library/collections collections ChainMap7641819
Ref: bc37641819
Ref: library/collections collections ChainMap maps7642800
Ref: 23dc7642800
Ref: library/collections collections ChainMap new_child7643073
Ref: ec77643073
Ref: library/collections collections ChainMap parents7643695
Ref: 23dd7643695
Ref: ChainMap 物件-Footnote-17645425
Ref: ChainMap 物件-Footnote-27645467
Ref: ChainMap 物件-Footnote-37645514
Ref: ChainMap 物件-Footnote-47645609
Ref: ChainMap 物件-Footnote-57645688
Ref: ChainMap 物件-Footnote-67645785
Node: ChainMap 範例和用法7645838
Ref: library/collections chainmap-examples-and-recipes7645914
Ref: 23de7645914
Node: Counter 物件7648860
Ref: library/collections counter-objects7648990
Ref: 23df7648990
Ref: library/collections collections Counter7649688
Ref: 10337649688
Ref: library/collections collections Counter elements7651600
Ref: 12977651600
Ref: library/collections collections Counter most_common7652051
Ref: 12967652051
Ref: library/collections collections Counter subtract7652530
Ref: 11767652530
Ref: library/collections collections Counter total7653083
Ref: 23e07653083
Ref: library/collections collections Counter fromkeys7653406
Ref: 23e17653406
Ref: library/collections collections Counter update7653523
Ref: 23e27653523
Ref: Counter 物件-Footnote-17658386
Ref: Counter 物件-Footnote-27658465
Ref: Counter 物件-Footnote-37658512
Node: deque 物件7658605
Ref: library/collections deque-objects7658738
Ref: 23e37658738
Ref: library/collections collections deque7658787
Ref: 5807658787
Ref: library/collections collections deque append7660126
Ref: 23e47660126
Ref: library/collections collections deque appendleft7660203
Ref: 23e57660203
Ref: library/collections collections deque clear7660284
Ref: 23e67660284
Ref: library/collections collections deque copy7660380
Ref: d7a7660380
Ref: library/collections collections deque count7660500
Ref: 11787660500
Ref: library/collections collections deque extend7660615
Ref: 23e77660615
Ref: library/collections collections deque extendleft7660707
Ref: 23e87660707
Ref: library/collections collections deque index7660890
Ref: d787660890
Ref: library/collections collections deque insert7661182
Ref: d797661182
Ref: library/collections collections deque pop7661435
Ref: 23e97661435
Ref: library/collections collections deque popleft7661597
Ref: 23ea7661597
Ref: library/collections collections deque remove7661763
Ref: 180e7661763
Ref: library/collections collections deque reverse7661915
Ref: 11797661915
Ref: library/collections collections deque rotate7662064
Ref: 17d97662064
Ref: library/collections collections deque maxlen7662401
Ref: 12987662401
Node: deque 用法7665117
Ref: library/collections deque-recipes7665178
Ref: 23eb7665178
Ref: deque 用法-Footnote-17667496
Node: defaultdict 物件7667557
Ref: library/collections defaultdict-objects7667730
Ref: 23ec7667730
Ref: library/collections collections defaultdict7667791
Ref: 11557667791
Ref: library/collections collections defaultdict __missing__7668465
Ref: 23ee7668465
Ref: library/collections collections defaultdict default_factory7669640
Ref: 23ed7669640
Ref: defaultdict 物件-Footnote-17670082
Node: defaultdict 範例7670124
Ref: library/collections defaultdict-examples7670197
Ref: 23ef7670197
Node: namedtuple 擁有具名欄位之 tuple 的工廠函式7672757
Ref: library/collections namedtuple-factory-function-for-tuples-with-named-fields7672936
Ref: 23f07672936
Ref: library/collections collections namedtuple7673311
Ref: 1ae7673311
Ref: library/collections collections somenamedtuple _make7677134
Ref: 23f17677134
Ref: library/collections collections somenamedtuple _asdict7677361
Ref: 9857677361
Ref: library/collections collections somenamedtuple _replace7677984
Ref: 23f27677984
Ref: library/collections collections somenamedtuple _fields7678591
Ref: 23f37678591
Ref: library/collections collections somenamedtuple _field_defaults7679074
Ref: 23f47679074
Node: OrderedDict 物件7681879
Ref: library/collections ordereddict-objects7682055
Ref: 23f57682055
Ref: library/collections collections OrderedDict7684425
Ref: 57f7684425
Ref: library/collections collections OrderedDict popitem7684621
Ref: 12807684621
Ref: library/collections collections OrderedDict move_to_end7684959
Ref: 11777684959
Ref: OrderedDict 物件-Footnote-17686565
Ref: OrderedDict 物件-Footnote-27686607
Node: OrderedDict 範例與用法7686649
Ref: library/collections ordereddict-examples-and-recipes7686731
Ref: 23f77686731
Node: UserDict 物件7689711
Ref: library/collections userdict-objects7689848
Ref: 23f87689848
Ref: library/collections collections UserDict7690176
Ref: 18987690176
Ref: library/collections collections UserDict data7690677
Ref: 23f97690677
Node: UserList 物件7690806
Ref: library/collections userlist-objects7690942
Ref: 23fa7690942
Ref: library/collections collections UserList7691443
Ref: 14527691443
Ref: library/collections collections UserList data7691953
Ref: 23fb7691953
Node: UserString 物件7692665
Ref: library/collections userstring-objects7692777
Ref: 23fc7692777
Ref: library/collections collections UserString7693106
Ref: d7b7693106
Ref: library/collections collections UserString data7693573
Ref: 23fd7693573
Node: collections abc --- 容器的抽象基底類別7693886
Ref: library/collections abc doc7694077
Ref: 23fe7694077
Ref: library/collections abc collections-abc-abstract-base-classes-for-containers7694077
Ref: 23ff7694077
Ref: library/collections abc module-collections abc7694077
Ref: 177694077
Ref: collections abc --- 容器的抽象基底類別-Footnote-17697862
Ref: collections abc --- 容器的抽象基底類別-Footnote-27697939
Node: Collections Abstract Base Classes7697981
Ref: library/collections abc collections-abstract-base-classes7698165
Ref: 81b7698165
Ref: library/collections abc id17698165
Ref: 24007698165
Ref: Collections Abstract Base Classes-Footnote-17707871
Ref: Collections Abstract Base Classes-Footnote-27708160
Ref: Collections Abstract Base Classes-Footnote-37708449
Ref: Collections Abstract Base Classes-Footnote-47708738
Ref: Collections Abstract Base Classes-Footnote-57709090
Ref: Collections Abstract Base Classes-Footnote-67709379
Ref: Collections Abstract Base Classes-Footnote-77709668
Ref: Collections Abstract Base Classes-Footnote-87709957
Ref: Collections Abstract Base Classes-Footnote-97710246
Ref: Collections Abstract Base Classes-Footnote-107710535
Ref: Collections Abstract Base Classes-Footnote-117710825
Ref: Collections Abstract Base Classes-Footnote-127711115
Ref: Collections Abstract Base Classes-Footnote-137711405
Ref: Collections Abstract Base Classes-Footnote-147711695
Ref: Collections Abstract Base Classes-Footnote-157711985
Ref: Collections Abstract Base Classes-Footnote-167712275
Node: Collections Abstract Base Classes -- Detailed Descriptions7712565
Ref: library/collections abc collections-abstract-base-classes-detailed-descriptions7712778
Ref: 24027712778
Ref: library/collections abc collections abc Container7712911
Ref: 212c7712911
Ref: library/collections abc collections abc Hashable7713030
Ref: 49d7713030
Ref: library/collections abc collections abc Sized7713138
Ref: 49e7713138
Ref: library/collections abc collections abc Callable7713243
Ref: 78e7713243
Ref: library/collections abc collections abc Iterable7713464
Ref: 212a7713464
Ref: library/collections abc collections abc Collection7713948
Ref: c2f7713948
Ref: library/collections abc collections abc Iterator7714064
Ref: 212b7714064
Ref: library/collections abc collections abc Reversible7714261
Ref: c307714261
Ref: library/collections abc collections abc Generator7714423
Ref: d817714423
Ref: library/collections abc collections abc Sequence7714841
Ref: 115c7714841
Ref: library/collections abc collections abc MutableSequence7714878
Ref: 1877714878
Ref: library/collections abc collections abc ByteString7714922
Ref: 2a47714922
Ref: library/collections abc collections abc Set7715991
Ref: 21227715991
Ref: library/collections abc collections abc MutableSet7716023
Ref: 212d7716023
Ref: library/collections abc collections abc Mapping7716118
Ref: 86f7716118
Ref: library/collections abc collections abc MutableMapping7716154
Ref: 10487716154
Ref: library/collections abc collections abc MappingView7716257
Ref: 212e7716257
Ref: library/collections abc collections abc ItemsView7716297
Ref: 21307716297
Ref: library/collections abc collections abc KeysView7716335
Ref: 212f7716335
Ref: library/collections abc collections abc ValuesView7716372
Ref: 21317716372
Ref: library/collections abc collections abc Awaitable7716479
Ref: d827716479
Ref: library/collections abc collections abc Coroutine7717240
Ref: d837717240
Ref: library/collections abc collections abc AsyncIterable7718294
Ref: d857718294
Ref: library/collections abc collections abc AsyncIterator7718494
Ref: d847718494
Ref: library/collections abc collections abc AsyncGenerator7718711
Ref: c317718711
Ref: library/collections abc collections abc Buffer7719040
Ref: 2a57719040
Ref: Collections Abstract Base Classes -- Detailed Descriptions-Footnote-17719280
Ref: Collections Abstract Base Classes -- Detailed Descriptions-Footnote-27719322
Ref: Collections Abstract Base Classes -- Detailed Descriptions-Footnote-37719364
Ref: Collections Abstract Base Classes -- Detailed Descriptions-Footnote-47719406
Node: Examples and Recipes7719448
Ref: library/collections abc examples-and-recipes7719619
Ref: 24057719619
Ref: Examples and Recipes-Footnote-17722595
Ref: Examples and Recipes-Footnote-27722648
Node: heapq --- 堆積佇列 heap queue 演算法7722690
Ref: library/heapq doc7722905
Ref: 24067722905
Ref: library/heapq heapq-heap-queue-algorithm7722905
Ref: 24077722905
Ref: library/heapq module-heapq7722905
Ref: 5f7722905
Ref: library/heapq heapq heappush7724505
Ref: 14277724505
Ref: library/heapq heapq heappop7724610
Ref: 14287724610
Ref: library/heapq heapq heappushpop7724867
Ref: 24097724867
Ref: library/heapq heapq heapify7725108
Ref: 24087725108
Ref: library/heapq heapq heapreplace7725230
Ref: 240a7725230
Ref: library/heapq heapq merge7726072
Ref: daa7726072
Ref: library/heapq heapq nlargest7727190
Ref: 240b7727190
Ref: library/heapq heapq nsmallest7727582
Ref: 240c7727582
Ref: heapq --- 堆積佇列 heap queue 演算法-Footnote-17728408
Node: 基礎範例7728473
Ref: library/heapq basic-examples7728598
Ref: 240d7728598
Ref: 基礎範例-Footnote-17729581
Node: 優先佇列實作細節7729628
Ref: library/heapq priority-queue-implementation-notes7729768
Ref: 240e7729768
Ref: 優先佇列實作細節-Footnote-17732651
Node: 原理7732704
Ref: library/heapq theory7732823
Ref: 240f7732823
Ref: 原理-Footnote-17737045
Node: bisect --- 陣列二分演算法 Array bisection algorithm7737565
Ref: library/bisect doc7737770
Ref: 24107737770
Ref: library/bisect bisect-array-bisection-algorithm7737770
Ref: 24117737770
Ref: library/bisect module-bisect7737770
Ref: d7737770
Ref: library/bisect bisect-functions7738639
Ref: 24127738639
Ref: library/bisect bisect bisect_left7738675
Ref: 24137738675
Ref: library/bisect bisect bisect_right7739782
Ref: 24147739782
Ref: library/bisect bisect bisect7739851
Ref: 24157739851
Ref: library/bisect bisect insort_left7740335
Ref: 24167740335
Ref: library/bisect bisect insort_right7740883
Ref: 24177740883
Ref: library/bisect bisect insort7740952
Ref: 24187740952
Ref: bisect --- 陣列二分演算法 Array bisection algorithm-Footnote-17741678
Node: 效能考量7741744
Ref: library/bisect performance-notes7741889
Ref: 24197741889
Ref: 效能考量-Footnote-17743262
Ref: 效能考量-Footnote-27743317
Node: 搜尋一個已排序的 list7743387
Ref: library/bisect searching-sorted-lists7743550
Ref: 241b7743550
Node: 範例<3>7744763
Ref: library/bisect examples7744905
Ref: 241c7744905
Ref: library/bisect bisect-example7744934
Ref: 241d7744934
Node: array --- 高效率的數值型陣列7747465
Ref: library/array doc7747648
Ref: 241e7747648
Ref: library/array array-efficient-arrays-of-numeric-values7747648
Ref: 241f7747648
Ref: library/array module-array7747648
Ref: 67747648
Ref: library/array array typecodes7752459
Ref: 24217752459
Ref: library/array array array7752587
Ref: 1867752587
Ref: library/array array array typecode7753860
Ref: 24247753860
Ref: library/array array array itemsize7753941
Ref: 24207753941
Ref: library/array array array append7754043
Ref: 24257754043
Ref: library/array array array buffer_info7754131
Ref: 24267754131
Ref: library/array array array byteswap7755085
Ref: 24277755085
Ref: library/array array array count7755372
Ref: 24287755372
Ref: library/array array array extend7755453
Ref: 24237755453
Ref: library/array array array frombytes7755853
Ref: 120a7755853
Ref: library/array array array fromfile7756248
Ref: 24297756248
Ref: library/array array array fromlist7756578
Ref: 242a7756578
Ref: library/array array array fromunicode7756782
Ref: 24227756782
Ref: library/array array array index7757136
Ref: 7847757136
Ref: library/array array array insert7757537
Ref: 242b7757537
Ref: library/array array array pop7757685
Ref: 242c7757685
Ref: library/array array array remove7757878
Ref: 242d7757878
Ref: library/array array array clear7757962
Ref: 1887757962
Ref: library/array array array reverse7758070
Ref: 242e7758070
Ref: library/array array array tobytes7758144
Ref: 12097758144
Ref: library/array array array tofile7758483
Ref: 242f7758483
Ref: library/array array array tolist7758601
Ref: 24307758601
Ref: library/array array array tounicode7758691
Ref: 24317758691
Ref: array --- 高效率的數值型陣列-Footnote-17759953
Node: weakref --- 弱參照7759980
Ref: library/weakref doc7760154
Ref: 24327760154
Ref: library/weakref mod-weakref7760154
Ref: eae7760154
Ref: library/weakref module-weakref7760154
Ref: fc7760154
Ref: library/weakref weakref-weak-references7760154
Ref: 24337760154
Ref: library/weakref weakref ref7763907
Ref: f917763907
Ref: library/weakref weakref ref __callback__7765462
Ref: f927765462
Ref: library/weakref weakref proxy7765741
Ref: 9f57765741
Ref: library/weakref weakref getweakrefcount7766608
Ref: 24357766608
Ref: library/weakref weakref getweakrefs7766716
Ref: 24367766716
Ref: library/weakref weakref WeakKeyDictionary7766838
Ref: 18717766838
Ref: library/weakref weakref WeakKeyDictionary keyrefs7768426
Ref: 24377768426
Ref: library/weakref weakref WeakValueDictionary7768520
Ref: 18707768520
Ref: library/weakref weakref WeakValueDictionary valuerefs7768942
Ref: 24387768942
Ref: library/weakref weakref WeakSet7769040
Ref: 5817769040
Ref: library/weakref weakref WeakMethod7769215
Ref: f907769215
Ref: library/weakref weakref finalize7770216
Ref: a1f7770216
Ref: library/weakref weakref finalize __call__7771412
Ref: 24397771412
Ref: library/weakref weakref finalize detach7771635
Ref: 243a7771635
Ref: library/weakref weakref finalize peek7771840
Ref: 243b7771840
Ref: library/weakref weakref finalize alive7772020
Ref: 243c7772020
Ref: library/weakref weakref finalize atexit7772124
Ref: 243d7772124
Ref: library/weakref weakref ReferenceType7772647
Ref: 16d87772647
Ref: library/weakref weakref ProxyType7772722
Ref: 16d97772722
Ref: library/weakref weakref CallableProxyType7772805
Ref: 16da7772805
Ref: library/weakref weakref ProxyTypes7772893
Ref: 243e7772893
Ref: weakref --- 弱參照-Footnote-17773435
Ref: weakref --- 弱參照-Footnote-27773502
Ref: weakref --- 弱參照-Footnote-37773544
Ref: weakref --- 弱參照-Footnote-47773586
Node: 弱參照物件7773628
Ref: library/weakref weak-reference-objects7773719
Ref: 243f7773719
Ref: library/weakref weakref-objects7773719
Ref: 24407773719
Node: 範例<4>7776055
Ref: library/weakref example7776173
Ref: 24417776173
Ref: library/weakref weakref-example7776173
Ref: 24427776173
Node: 最終化器物件7776694
Ref: library/weakref finalize-examples7776836
Ref: 24437776836
Ref: library/weakref finalizer-objects7776836
Ref: 24447776836
Node: 最終化器與 __del__ 方法的比較7778628
Ref: library/weakref comparing-finalizers-with-del-methods7778752
Ref: 24457778752
Node: types --- 動態型別建立與內建型別名稱7781354
Ref: library/types doc7781542
Ref: 24467781542
Ref: library/types module-types7781542
Ref: ec7781542
Ref: library/types types-dynamic-type-creation-and-names-for-built-in-types7781542
Ref: 24477781542
Ref: types --- 動態型別建立與內建型別名稱-Footnote-17782309
Node: Dynamic Type Creation7782374
Ref: library/types dynamic-type-creation7782516
Ref: 24487782516
Ref: library/types types new_class7782579
Ref: 10fa7782579
Ref: library/types types prepare_class7783283
Ref: 10fb7783283
Ref: library/types types resolve_bases7784449
Ref: b437784449
Ref: library/types types get_original_bases7785016
Ref: 4757785016
Ref: Dynamic Type Creation-Footnote-17786574
Ref: Dynamic Type Creation-Footnote-27786616
Ref: Dynamic Type Creation-Footnote-37786658
Ref: Dynamic Type Creation-Footnote-47786700
Node: Standard Interpreter Types7786742
Ref: library/types standard-interpreter-types7786933
Ref: 24497786933
Ref: library/types types NoneType7787489
Ref: 7f67787489
Ref: library/types types FunctionType7787581
Ref: 8277787581
Ref: library/types types LambdaType7787612
Ref: 244a7787612
Ref: library/types types GeneratorType7787970
Ref: 15297787970
Ref: library/types types CoroutineType7788099
Ref: e2d7788099
Ref: library/types types AsyncGeneratorType7788258
Ref: 244b7788258
Ref: library/types types CodeType7788446
Ref: 2b67788446
Ref: library/types types CellType7789054
Ref: 244c7789054
Ref: library/types types MethodType7789217
Ref: 16fe7789217
Ref: library/types types BuiltinFunctionType7789306
Ref: 244d7789306
Ref: library/types types BuiltinMethodType7789344
Ref: 244e7789344
Ref: library/types types WrapperDescriptorType7789562
Ref: b407789562
Ref: library/types types MethodWrapperType7789782
Ref: 5f17789782
Ref: library/types types NotImplementedType7789987
Ref: 7f77789987
Ref: library/types types MethodDescriptorType7790099
Ref: b417790099
Ref: library/types types ClassMethodDescriptorType7790258
Ref: b427790258
Ref: library/types types ModuleType7790447
Ref: db97790447
Ref: library/types types ModuleType __doc__7790813
Ref: 244f7790813
Ref: library/types types ModuleType __loader__7790917
Ref: 24507790917
Ref: library/types types ModuleType __name__7791660
Ref: 24527791660
Ref: library/types types ModuleType __package__7791800
Ref: 24547791800
Ref: library/types types ModuleType __spec__7792812
Ref: 24557792812
Ref: library/types types EllipsisType7793031
Ref: 7f57793031
Ref: library/types types GenericAlias7793132
Ref: 78f7793132
Ref: library/types types UnionType7794044
Ref: 5e07794044
Ref: library/types types TracebackType7794155
Ref: a957794155
Ref: library/types types FrameType7794484
Ref: 17567794484
Ref: library/types types GetSetDescriptorType7794639
Ref: 24567794639
Ref: library/types types MemberDescriptorType7795008
Ref: 24577795008
Ref: library/types types MappingProxyType7795793
Ref: 4147795793
Ref: library/types types MappingProxyType copy7796779
Ref: 24587796779
Ref: library/types types MappingProxyType get7796865
Ref: 24597796865
Ref: library/types types MappingProxyType items7797138
Ref: 245a7797138
Ref: library/types types MappingProxyType keys7797266
Ref: 245b7797266
Ref: library/types types MappingProxyType values7797355
Ref: 245c7797355
Ref: library/types types CapsuleType7797723
Ref: 245d7797723
Ref: Standard Interpreter Types-Footnote-17797866
Ref: Standard Interpreter Types-Footnote-27797908
Node: Additional Utility Classes and Functions7797950
Ref: library/types additional-utility-classes-and-functions7798147
Ref: 245f7798147
Ref: library/types types SimpleNamespace7798248
Ref: 1b57798248
Ref: library/types types DynamicClassAttribute7800271
Ref: 5d07800271
Node: Coroutine Utility Functions7800943
Ref: library/types coroutine-utility-functions7801105
Ref: 24607801105
Ref: library/types types coroutine7801180
Ref: e2c7801180
Node: copy --- 淺層 shallow 和深層 deep 複製操作7802006
Ref: library/copy doc7802205
Ref: 24617802205
Ref: library/copy copy-shallow-and-deep-copy-operations7802205
Ref: 24627802205
Ref: library/copy module-copy7802205
Ref: 1e7802205
Ref: library/copy copy copy7802782
Ref: 4d87802782
Ref: library/copy copy deepcopy7802849
Ref: b127802849
Ref: library/copy copy replace7802925
Ref: 1367802925
Ref: library/copy copy Error7803104
Ref: 24637803104
Ref: library/copy shallow-vs-deep-copy7803170
Ref: 1b087803170
Ref: library/copy object __copy__7805101
Ref: 24647805101
Ref: library/copy object __deepcopy__7805232
Ref: 24657805232
Ref: library/copy object __replace__7805936
Ref: 1377805936
Ref: copy --- 淺層 shallow 和深層 deep 複製操作-Footnote-17806295
Node: pprint --- 資料美化列印器7806359
Ref: library/pprint doc7806541
Ref: 24667806541
Ref: library/pprint module-pprint7806541
Ref: 9c7806541
Ref: library/pprint pprint-data-pretty-printer7806541
Ref: 24677806541
Ref: pprint --- 資料美化列印器-Footnote-17807741
Node: 函式<3>7807807
Ref: library/pprint functions7807914
Ref: 24687807914
Ref: library/pprint pprint-functions7807914
Ref: 24697807914
Ref: library/pprint pprint pp7807945
Ref: 9c77807945
Ref: library/pprint pprint pprint7810517
Ref: 7cc7810517
Ref: library/pprint pprint pformat7810913
Ref: f237810913
Ref: library/pprint pprint isreadable7811362
Ref: 246b7811362
Ref: library/pprint pprint isrecursive7811664
Ref: 246c7811664
Ref: library/pprint pprint saferepr7811963
Ref: 246d7811963
Node: PrettyPrinter 物件7812609
Ref: library/pprint id17812734
Ref: 246e7812734
Ref: library/pprint prettyprinter-objects7812734
Ref: 246f7812734
Ref: library/pprint pprint PrettyPrinter7812793
Ref: f227812793
Ref: library/pprint pprint PrettyPrinter pformat7814443
Ref: 24707814443
Ref: library/pprint pprint PrettyPrinter pprint7814642
Ref: 24717814642
Ref: library/pprint pprint PrettyPrinter isreadable7815027
Ref: 24727815027
Ref: library/pprint pprint PrettyPrinter isrecursive7815425
Ref: 24737815425
Ref: library/pprint pprint PrettyPrinter format7815741
Ref: 18217815741
Node: 範例<5>7816901
Ref: library/pprint example7817008
Ref: 24747817008
Ref: library/pprint pprint-example7817008
Ref: 24757817008
Ref: 範例<5>-Footnote-17824294
Node: reprlib --- repr 的替代實作7824319
Ref: library/reprlib doc7824477
Ref: 24767824477
Ref: library/reprlib module-reprlib7824477
Ref: a97824477
Ref: library/reprlib reprlib-alternate-repr-implementation7824477
Ref: 24777824477
Ref: library/reprlib reprlib Repr7824944
Ref: 24787824944
Ref: library/reprlib reprlib aRepr7825927
Ref: 247a7825927
Ref: library/reprlib reprlib repr7826212
Ref: 247b7826212
Ref: library/reprlib reprlib recursive_repr7826612
Ref: 118b7826612
Ref: reprlib --- repr 的替代實作-Footnote-17827407
Node: Repr 物件7827474
Ref: library/reprlib id17827587
Ref: 24797827587
Ref: library/reprlib repr-objects7827587
Ref: 247d7827587
Ref: library/reprlib reprlib Repr fillvalue7827824
Ref: 247e7827824
Ref: library/reprlib reprlib Repr maxlevel7827970
Ref: 247f7827970
Ref: library/reprlib reprlib Repr maxdict7828091
Ref: 24807828091
Ref: library/reprlib reprlib Repr maxlist7828116
Ref: 24817828116
Ref: library/reprlib reprlib Repr maxtuple7828141
Ref: 24827828141
Ref: library/reprlib reprlib Repr maxset7828167
Ref: 24837828167
Ref: library/reprlib reprlib Repr maxfrozenset7828191
Ref: 24847828191
Ref: library/reprlib reprlib Repr maxdeque7828221
Ref: 24857828221
Ref: library/reprlib reprlib Repr maxarray7828247
Ref: 24867828247
Ref: library/reprlib reprlib Repr maxlong7828472
Ref: 24877828472
Ref: library/reprlib reprlib Repr maxstring7828638
Ref: 24887828638
Ref: library/reprlib reprlib Repr maxother7828988
Ref: 24897828988
Ref: library/reprlib reprlib Repr indent7829264
Ref: 248a7829264
Ref: library/reprlib reprlib Repr repr7830756
Ref: 247c7830756
Ref: library/reprlib reprlib Repr repr17830896
Ref: 248b7830896
Node: Subclassing Repr Objects7831714
Ref: library/reprlib subclassing-repr-objects7831827
Ref: 248c7831827
Ref: library/reprlib subclassing-reprs7831827
Ref: 248d7831827
Node: enum --- 對列舉的支援7832524
Ref: library/enum doc7832716
Ref: 248e7832716
Ref: library/enum enum-support-for-enumerations7832716
Ref: 248f7832716
Ref: library/enum module-enum7832716
Ref: 4c7832716
Ref: enum --- 對列舉的支援-Footnote-17834476
Node: 模組內容<2>7834540
Ref: library/enum module-contents7834643
Ref: 24947834643
Node: 資料型別<2>7837712
Ref: library/enum data-types7837848
Ref: 24987837848
Ref: library/enum enum EnumType7837889
Ref: 5bf7837889
Ref: library/enum enum EnumType __call__7838368
Ref: 249a7838368
Ref: library/enum enum EnumType __contains__7839476
Ref: 249b7839476
Ref: library/enum enum EnumType __dir__7839897
Ref: 249c7839897
Ref: library/enum enum EnumType __getitem__7840273
Ref: 249d7840273
Ref: library/enum enum EnumType __iter__7840483
Ref: 249e7840483
Ref: library/enum enum EnumType __len__7840682
Ref: 249f7840682
Ref: library/enum enum EnumType __members__7840805
Ref: 24a07840805
Ref: library/enum enum EnumType __reversed__7840907
Ref: 24a17840907
Ref: library/enum enum EnumType _add_alias_7841123
Ref: 24a27841123
Ref: library/enum enum EnumType _add_value_alias_7841325
Ref: 24a37841325
Ref: library/enum enum Enum7841662
Ref: 5d67841662
Ref: library/enum enum Enum name7841740
Ref: 24a47841740
Ref: library/enum enum Enum value7841875
Ref: 24a57841875
Ref: library/enum enum Enum _name_7842737
Ref: 24a77842737
Ref: library/enum enum Enum _value_7842789
Ref: 24a87842789
Ref: library/enum enum Enum _order_7842884
Ref: 24a97842884
Ref: library/enum enum Enum _ignore_7843015
Ref: 24aa7843015
Ref: library/enum enum Enum __dir__7843314
Ref: 17647843314
Ref: library/enum enum Enum _generate_next_value_7844147
Ref: 24ac7844147
Ref: library/enum enum Enum __init__7845009
Ref: 24ad7845009
Ref: library/enum enum Enum __init_subclass__7845447
Ref: 24ae7845447
Ref: library/enum enum Enum _missing_7845609
Ref: 24af7845609
Ref: library/enum enum Enum __new__7846460
Ref: 24a67846460
Ref: library/enum enum Enum __repr__7847110
Ref: 16887847110
Ref: library/enum enum Enum __str__7847816
Ref: 5c87847816
Ref: library/enum enum Enum __format__7848423
Ref: 5c67848423
Ref: library/enum enum IntEnum7849260
Ref: c867849260
Ref: library/enum enum StrEnum7850320
Ref: 5c07850320
Ref: library/enum enum Flag7851348
Ref: 5c97851348
Ref: library/enum enum Flag __contains__7851597
Ref: 24b07851597
Ref: library/enum enum Flag __or__7853052
Ref: 24b17853052
Ref: library/enum enum Flag __and__7853233
Ref: 24b27853233
Ref: library/enum enum Flag __xor__7853472
Ref: 24b37853472
Ref: library/enum enum Flag _numeric_repr_7854011
Ref: 24b47854011
Ref: library/enum enum IntFlag7854459
Ref: 21d77854459
Ref: library/enum enum ReprEnum7856051
Ref: 5c17856051
Ref: library/enum enum EnumCheck7856565
Ref: 5cc7856565
Ref: library/enum enum EnumCheck UNIQUE7856750
Ref: 24b57856750
Ref: library/enum enum EnumCheck CONTINUOUS7857229
Ref: 24b67857229
Ref: library/enum enum EnumCheck NAMED_FLAGS7857706
Ref: 24b77857706
Ref: library/enum enum FlagBoundary7858558
Ref: 5ca7858558
Ref: library/enum enum FlagBoundary STRICT7858704
Ref: 24b87858704
Ref: library/enum enum FlagBoundary CONFORM7859335
Ref: 24b97859335
Ref: library/enum enum FlagBoundary EJECT7859801
Ref: 24ba7859801
Ref: library/enum enum FlagBoundary KEEP7860238
Ref: 24bb7860238
Node: 支援 __dunder__ 名稱7860891
Ref: library/enum supported-dunder-names7860998
Ref: 24bc7860998
Node: 支援 _sunder_ 名稱7861413
Ref: library/enum supported-sunder-names7861520
Ref: 24bd7861520
Ref: 支援 _sunder_ 名稱-Footnote-17863241
Node: 通用項目與裝飾器7863328
Ref: library/enum ipython-s-rich-display7863455
Ref: 24be7863455
Ref: library/enum utilities-and-decorators7863455
Ref: 24bf7863455
Ref: library/enum enum auto7863516
Ref: c437863516
Ref: library/enum enum property7864943
Ref: 5cf7864943
Ref: library/enum enum unique7865365
Ref: 24967865365
Ref: library/enum enum verify7865980
Ref: 5cb7865980
Ref: library/enum enum member7866198
Ref: 5cd7866198
Ref: library/enum enum nonmember7866317
Ref: 5ce7866317
Ref: library/enum enum global_enum7866442
Ref: 5d17866442
Ref: library/enum enum show_flag_values7866768
Ref: 24977866768
Node: 備註7866983
Ref: library/enum notes7867086
Ref: 24957867086
Node: graphlib —-- 使用類圖 graph-like 結構進行操作的功能7867951
Ref: library/graphlib doc7868102
Ref: 24c07868102
Ref: library/graphlib graphlib-functionality-to-operate-with-graph-like-structures7868102
Ref: 24c17868102
Ref: library/graphlib module-graphlib7868102
Ref: 5b7868102
Ref: library/graphlib graphlib TopologicalSorter7868348
Ref: 8867868348
Ref: library/graphlib graphlib TopologicalSorter add7871496
Ref: 24c27871496
Ref: library/graphlib graphlib TopologicalSorter prepare7872186
Ref: 24c37872186
Ref: library/graphlib graphlib TopologicalSorter is_active7872581
Ref: 24c47872581
Ref: library/graphlib graphlib TopologicalSorter done7873421
Ref: 24c67873421
Ref: library/graphlib graphlib TopologicalSorter get_ready7874105
Ref: 24c57874105
Ref: library/graphlib graphlib TopologicalSorter static_order7874639
Ref: 24c77874639
Ref: graphlib —-- 使用類圖 graph-like 結構進行操作的功能-Footnote-17875992
Node: 例外<2>7876060
Ref: library/graphlib exceptions7876172
Ref: 24c97876172
Ref: library/graphlib graphlib CycleError7876261
Ref: 24c87876261
Node: 數值與數學模組7876906
Ref: library/numeric doc7877051
Ref: 24ca7877051
Ref: library/numeric numeric7877051
Ref: 24cb7877051
Ref: library/numeric numeric-and-mathematical-modules7877051
Ref: 24cc7877051
Node: numbers --- 數值的抽象基底類別7878044
Ref: library/numbers doc7878171
Ref: 24cd7878171
Ref: library/numbers module-numbers7878171
Ref: 8e7878171
Ref: library/numbers numbers-numeric-abstract-base-classes7878171
Ref: 24ce7878171
Ref: library/numbers numbers Number7878553
Ref: 24cf7878553
Ref: numbers --- 數值的抽象基底類別-Footnote-17878836
Ref: numbers --- 數值的抽象基底類別-Footnote-27878903
Node: 數值的階層7878945
Ref: library/numbers the-numeric-tower7879072
Ref: 24d07879072
Ref: library/numbers numbers Complex7879116
Ref: 24d17879116
Ref: library/numbers numbers Complex real7879575
Ref: 24d27879575
Ref: library/numbers numbers Complex imag7879658
Ref: 24d37879658
Ref: library/numbers numbers Complex conjugate7879741
Ref: 24d47879741
Ref: library/numbers numbers Real7879879
Ref: 20737879879
Ref: library/numbers numbers Rational7880402
Ref: 12557880402
Ref: library/numbers numbers Rational numerator7880771
Ref: 24d57880771
Ref: library/numbers numbers Rational denominator7880826
Ref: 24d67880826
Ref: library/numbers numbers Integral7880883
Ref: 1e927880883
Node: 給型別實作者的註記7881306
Ref: library/numbers notes-for-type-implementers7881433
Ref: 24d77881433
Node: 加入更多數值 ABC7882244
Ref: library/numbers adding-more-numeric-abcs7882357
Ref: 24d87882357
Node: 實作算術操作7882657
Ref: library/numbers id17882770
Ref: 24d97882770
Ref: library/numbers implementing-the-arithmetic-operations7882770
Ref: 1dd97882770
Node: math --- 數學函式7887344
Ref: library/math doc7887511
Ref: 24da7887511
Ref: library/math math-mathematical-functions7887511
Ref: 24db7887511
Ref: library/math module-math7887511
Ref: 817887511
Node: 數論與表現函式7888405
Ref: library/math number-theoretic-and-representation-functions7888524
Ref: 24dc7888524
Ref: library/math math ceil7888578
Ref: 13307888578
Ref: library/math math comb7888817
Ref: 6747888817
Ref: library/math math copysign7889337
Ref: 13417889337
Ref: library/math math fabs7889535
Ref: 24dd7889535
Ref: library/math math factorial7889595
Ref: 8eb7889595
Ref: library/math math floor7889847
Ref: 132f7889847
Ref: library/math math fma7890088
Ref: 1ea7890088
Ref: library/math math fmod7890770
Ref: 1f437890770
Ref: library/math math frexp7891657
Ref: 24de7891657
Ref: library/math math fsum7892007
Ref: 13427892007
Ref: library/math math gcd7892633
Ref: 8b57892633
Ref: library/math math isclose7893056
Ref: d567893056
Ref: library/math math isfinite7894283
Ref: 11837894283
Ref: library/math math isinf7894485
Ref: 133f7894485
Ref: library/math math isnan7894608
Ref: 13407894608
Ref: library/math math isqrt7894770
Ref: 9a97894770
Ref: library/math math lcm7895237
Ref: 8b67895237
Ref: library/math math ldexp7895568
Ref: 24df7895568
Ref: library/math math modf7895690
Ref: 24e07895690
Ref: library/math math nextafter7895828
Ref: 4407895828
Ref: library/math math perm7896496
Ref: 6757896496
Ref: library/math math prod7897023
Ref: 9a87897023
Ref: library/math math remainder7897399
Ref: af77897399
Ref: library/math math sumprod7898425
Ref: 43f7898425
Ref: library/math math trunc7898874
Ref: 13317898874
Ref: library/math math ulp7899266
Ref: 8b77899266
Ref: 數論與表現函式-Footnote-17901000
Ref: 數論與表現函式-Footnote-27901053
Node: Power and logarithmic functions7901095
Ref: library/math power-and-logarithmic-functions7901246
Ref: 24e17901246
Ref: library/math math cbrt7901327
Ref: 6077901327
Ref: library/math math exp7901418
Ref: 12a87901418
Ref: library/math math exp27901635
Ref: 6067901635
Ref: library/math math expm17901733
Ref: 11847901733
Ref: library/math math log7902347
Ref: 142b7902347
Ref: library/math math log1p7902580
Ref: 13467902580
Ref: library/math math log27902741
Ref: 10757902741
Ref: library/math math log107903080
Ref: 24e27903080
Ref: library/math math pow7903210
Ref: 6087903210
Ref: library/math math sqrt7904101
Ref: 9aa7904101
Ref: Power and logarithmic functions-Footnote-17904201
Node: Trigonometric functions7904260
Ref: library/math trigonometric-functions7904408
Ref: 24e37904408
Ref: library/math math acos7904473
Ref: 24e47904473
Ref: library/math math asin7904598
Ref: 24e57904598
Ref: library/math math atan7904727
Ref: 24e67904727
Ref: library/math math atan27904859
Ref: 24e77904859
Ref: library/math math cos7905369
Ref: 142a7905369
Ref: library/math math dist7905435
Ref: 9a67905435
Ref: library/math math hypot7905764
Ref: 9a77905764
Ref: library/math math sin7906513
Ref: 14297906513
Ref: library/math math tan7906577
Ref: 24e87906577
Node: Angular conversion7906644
Ref: library/math angular-conversion7906781
Ref: 24e97906781
Ref: library/math math degrees7906836
Ref: 24ea7906836
Ref: library/math math radians7906915
Ref: 24eb7906915
Node: Hyperbolic functions7906994
Ref: library/math hyperbolic-functions7907125
Ref: 24ec7907125
Ref: library/math math acosh7907297
Ref: 13437907297
Ref: library/math math asinh7907376
Ref: 13447907376
Ref: library/math math atanh7907453
Ref: 13457907453
Ref: library/math math cosh7907533
Ref: 24ed7907533
Ref: library/math math sinh7907603
Ref: 24ee7907603
Ref: library/math math tanh7907671
Ref: 24ef7907671
Ref: Hyperbolic functions-Footnote-17907778
Node: Special functions7907837
Ref: library/math special-functions7907959
Ref: 24f07907959
Ref: library/math math erf7908012
Ref: b7f7908012
Ref: library/math math erfc7908432
Ref: b807908432
Ref: library/math math gamma7908731
Ref: 11857908731
Ref: library/math math lgamma7908830
Ref: 11867908830
Ref: Special functions-Footnote-17909015
Ref: Special functions-Footnote-27909068
Ref: Special functions-Footnote-37909139
Ref: Special functions-Footnote-47909192
Ref: Special functions-Footnote-57909251
Node: 常數<2>7909304
Ref: library/math constants7909397
Ref: 24f17909397
Ref: library/math math pi7909426
Ref: 24f27909426
Ref: library/math math e7909528
Ref: 24f37909528
Ref: library/math math tau7909628
Ref: 24f47909628
Ref: library/math math inf7910007
Ref: c2b7910007
Ref: library/math math nan7910200
Ref: 6097910200
Ref: 常數<2>-Footnote-17912145
Ref: 常數<2>-Footnote-27912197
Ref: 常數<2>-Footnote-37912225
Node: cmath --- 複數的數學函式7912272
Ref: library/cmath doc7912445
Ref: 24f57912445
Ref: library/cmath cmath-mathematical-functions-for-complex-numbers7912445
Ref: 24f67912445
Ref: library/cmath module-cmath7912445
Ref: 117912445
Node: 轉換到極座標和從極座標做轉換7914054
Ref: library/cmath conversions-to-and-from-polar-coordinates7914197
Ref: 24f87914197
Ref: library/cmath cmath phase7914842
Ref: 24f97914842
Ref: library/cmath cmath polar7915517
Ref: 24fa7915517
Ref: library/cmath cmath rect7915754
Ref: 24fb7915754
Node: 冪函數和對數函數7915912
Ref: library/cmath power-and-logarithmic-functions7916076
Ref: 24fc7916076
Ref: library/cmath cmath exp7916135
Ref: 24fd7916135
Ref: library/cmath cmath log7916235
Ref: 24fe7916235
Ref: library/cmath cmath log107916436
Ref: 24ff7916436
Ref: library/cmath cmath sqrt7916570
Ref: 24f77916570
Node: 三角函數7916687
Ref: library/cmath trigonometric-functions7916821
Ref: 25007916821
Ref: library/cmath cmath acos7916860
Ref: 25017916860
Ref: library/cmath cmath asin7917060
Ref: 25027917060
Ref: library/cmath cmath atan7917181
Ref: 25037917181
Ref: library/cmath cmath cos7917390
Ref: 25047917390
Ref: library/cmath cmath sin7917450
Ref: 25057917450
Ref: library/cmath cmath tan7917510
Ref: 25067917510
Node: 雙曲函數7917570
Ref: library/cmath hyperbolic-functions7917692
Ref: 25077917692
Ref: library/cmath cmath acosh7917731
Ref: 25087917731
Ref: library/cmath cmath asinh7917875
Ref: 25097917875
Ref: library/cmath cmath atanh7918095
Ref: 250a7918095
Ref: library/cmath cmath cosh7918317
Ref: 250b7918317
Ref: library/cmath cmath sinh7918387
Ref: 250c7918387
Ref: library/cmath cmath tanh7918457
Ref: 250d7918457
Node: 分類函式7918527
Ref: library/cmath classification-functions7918646
Ref: 250e7918646
Ref: library/cmath cmath isfinite7918685
Ref: 250f7918685
Ref: library/cmath cmath isinf7918849
Ref: 25107918849
Ref: library/cmath cmath isnan7918979
Ref: 25117918979
Ref: library/cmath cmath isclose7919104
Ref: d577919104
Ref: 分類函式-Footnote-17920383
Node: 常數<3>7920425
Ref: library/cmath constants7920523
Ref: 25127920523
Ref: library/cmath cmath pi7920552
Ref: 25137920552
Ref: library/cmath cmath e7920625
Ref: 25147920625
Ref: library/cmath cmath tau7920696
Ref: c287920696
Ref: library/cmath cmath inf7920798
Ref: c297920798
Ref: library/cmath cmath infj7920914
Ref: c2c7920914
Ref: library/cmath cmath nan7921063
Ref: c2a7921063
Ref: library/cmath cmath nanj7921186
Ref: c2d7921186
Node: decimal --- 十進位固定點和浮點運算7922437
Ref: library/decimal doc7922612
Ref: 25157922612
Ref: library/decimal decimal-decimal-fixed-point-and-floating-point-arithmetic7922612
Ref: 25167922612
Ref: library/decimal module-decimal7922612
Ref: 2e7922612
Ref: decimal --- 十進位固定點和浮點運算-Footnote-17927668
Ref: decimal --- 十進位固定點和浮點運算-Footnote-27927735
Node: Quick-start Tutorial7927789
Ref: library/decimal decimal-tutorial7927915
Ref: 25267927915
Ref: library/decimal quick-start-tutorial7927915
Ref: 25277927915
Node: Decimal objects7935146
Ref: library/decimal decimal-decimal7935296
Ref: 252a7935296
Ref: library/decimal decimal-objects7935296
Ref: 252b7935296
Ref: library/decimal decimal Decimal7935345
Ref: 27c7935345
Ref: library/decimal decimal Decimal adjusted7940459
Ref: 252c7940459
Ref: library/decimal decimal Decimal as_integer_ratio7940808
Ref: c3b7940808
Ref: library/decimal decimal Decimal as_tuple7941249
Ref: 252d7941249
Ref: library/decimal decimal Decimal canonical7941407
Ref: 252e7941407
Ref: library/decimal decimal Decimal compare7941646
Ref: 252f7941646
Ref: library/decimal decimal Decimal compare_signal7942079
Ref: 25307942079
Ref: library/decimal decimal Decimal compare_total7942391
Ref: 25317942391
Ref: library/decimal decimal Decimal compare_total_mag7943668
Ref: 25327943668
Ref: library/decimal decimal Decimal conjugate7944273
Ref: 25337944273
Ref: library/decimal decimal Decimal copy_abs7944406
Ref: 25347944406
Ref: library/decimal decimal Decimal copy_negate7944620
Ref: 25357944620
Ref: library/decimal decimal Decimal copy_sign7944831
Ref: 25367944831
Ref: library/decimal decimal Decimal exp7945368
Ref: 10467945368
Ref: library/decimal decimal Decimal from_float7945802
Ref: 119c7945802
Ref: library/decimal decimal Decimal fma7946944
Ref: 25377946944
Ref: library/decimal decimal Decimal is_canonical7947188
Ref: 25387947188
Ref: library/decimal decimal Decimal is_finite7947463
Ref: 25397947463
Ref: library/decimal decimal Decimal is_infinite7947638
Ref: 253a7947638
Ref: library/decimal decimal Decimal is_nan7947805
Ref: 253b7947805
Ref: library/decimal decimal Decimal is_normal7947957
Ref: 253c7947957
Ref: library/decimal decimal Decimal is_qnan7948181
Ref: 253d7948181
Ref: library/decimal decimal Decimal is_signed7948320
Ref: 253e7948320
Ref: library/decimal decimal Decimal is_snan7948523
Ref: 253f7948523
Ref: library/decimal decimal Decimal is_subnormal7948665
Ref: 25407948665
Ref: library/decimal decimal Decimal is_zero7948819
Ref: 25417948819
Ref: library/decimal decimal Decimal ln7948975
Ref: 10477948975
Ref: library/decimal decimal Decimal log107949183
Ref: 25427949183
Ref: library/decimal decimal Decimal logb7949386
Ref: 25437949386
Ref: library/decimal decimal Decimal logical_and7949773
Ref: 25447949773
Ref: library/decimal decimal Decimal logical_invert7950038
Ref: 25467950038
Ref: library/decimal decimal Decimal logical_or7950217
Ref: 25477950217
Ref: library/decimal decimal Decimal logical_xor7950479
Ref: 25487950479
Ref: library/decimal decimal Decimal max7950747
Ref: 25497950747
Ref: library/decimal decimal Decimal max_mag7951051
Ref: 254a7951051
Ref: library/decimal decimal Decimal min7951232
Ref: 254b7951232
Ref: library/decimal decimal Decimal min_mag7951536
Ref: 254c7951536
Ref: library/decimal decimal Decimal next_minus7951717
Ref: 254d7951717
Ref: library/decimal decimal Decimal next_plus7951953
Ref: 254e7951953
Ref: library/decimal decimal Decimal next_toward7952188
Ref: 254f7952188
Ref: library/decimal decimal Decimal normalize7952555
Ref: 25507952555
Ref: library/decimal decimal Decimal number_class7953601
Ref: 25517953601
Ref: library/decimal decimal Decimal quantize7954771
Ref: 104a7954771
Ref: library/decimal decimal Decimal radix7956071
Ref: 25537956071
Ref: library/decimal decimal Decimal remainder_near7956288
Ref: 25547956288
Ref: library/decimal decimal Decimal rotate7957132
Ref: 25557957132
Ref: library/decimal decimal Decimal same_quantum7957805
Ref: 25567957805
Ref: library/decimal decimal Decimal scaleb7958217
Ref: 25577958217
Ref: library/decimal decimal Decimal shift7958468
Ref: 25587958468
Ref: library/decimal decimal Decimal sqrt7959074
Ref: 25597959074
Ref: library/decimal decimal Decimal to_eng_string7959181
Ref: 255a7959181
Ref: library/decimal decimal Decimal to_integral7959657
Ref: 255b7959657
Ref: library/decimal decimal Decimal to_integral_exact7959887
Ref: 255d7959887
Ref: library/decimal decimal Decimal to_integral_value7960317
Ref: 255c7960317
Node: Logical operands7962815
Ref: library/decimal logical-operands7962883
Ref: 255e7962883
Ref: library/decimal logical-operands-label7962883
Ref: 25457962883
Node: Context objects7963256
Ref: library/decimal context-objects7963395
Ref: 255f7963395
Ref: library/decimal decimal-context7963395
Ref: 25607963395
Ref: library/decimal decimal getcontext7963779
Ref: 14c67963779
Ref: library/decimal decimal setcontext7963870
Ref: 25287963870
Ref: library/decimal decimal localcontext7964102
Ref: 17097964102
Ref: library/decimal decimal BasicContext7965715
Ref: 10427965715
Ref: library/decimal decimal ExtendedContext7966168
Ref: 10437966168
Ref: library/decimal decimal DefaultContext7966802
Ref: 10417966802
Ref: library/decimal decimal Context7967930
Ref: 10497967930
Ref: library/decimal decimal Context clear_flags7970869
Ref: 25297970869
Ref: library/decimal decimal Context clear_traps7970949
Ref: 25657970949
Ref: library/decimal decimal Context copy7971062
Ref: 25667971062
Ref: library/decimal decimal Context copy_decimal7971134
Ref: 25677971134
Ref: library/decimal decimal Context create_decimal7971225
Ref: 10457971225
Ref: library/decimal decimal Context create_decimal_from_float7972329
Ref: 25687972329
Ref: library/decimal decimal Context Etiny7973095
Ref: 25527973095
Ref: library/decimal decimal Context Etop7973325
Ref: 25697973325
Ref: library/decimal decimal Context abs7973831
Ref: 256a7973831
Ref: library/decimal decimal Context add7973903
Ref: 256b7973903
Ref: library/decimal decimal Context canonical7973974
Ref: 129a7973974
Ref: library/decimal decimal Context compare7974054
Ref: 256c7974054
Ref: library/decimal decimal Context compare_signal7974132
Ref: 256d7974132
Ref: library/decimal decimal Context compare_total7974236
Ref: 256e7974236
Ref: library/decimal decimal Context compare_total_mag7974345
Ref: 256f7974345
Ref: library/decimal decimal Context copy_abs7974483
Ref: 25707974483
Ref: library/decimal decimal Context copy_negate7974571
Ref: 25717974571
Ref: library/decimal decimal Context copy_sign7974662
Ref: 25727974662
Ref: library/decimal decimal Context divide7974741
Ref: 25737974741
Ref: library/decimal decimal Context divide_int7974811
Ref: 25747974811
Ref: library/decimal decimal Context divmod7974910
Ref: 25757974910
Ref: library/decimal decimal Context exp7975027
Ref: 25767975027
Ref: library/decimal decimal Context fma7975086
Ref: 25777975086
Ref: library/decimal decimal Context is_canonical7975170
Ref: 129b7975170
Ref: library/decimal decimal Context is_finite7975287
Ref: 25787975287
Ref: library/decimal decimal Context is_infinite7975398
Ref: 25797975398
Ref: library/decimal decimal Context is_nan7975513
Ref: 257a7975513
Ref: library/decimal decimal Context is_normal7975639
Ref: 257b7975639
Ref: library/decimal decimal Context is_qnan7975769
Ref: 257c7975769
Ref: library/decimal decimal Context is_signed7975893
Ref: 257d7975893
Ref: library/decimal decimal Context is_snan7976006
Ref: 257e7976006
Ref: library/decimal decimal Context is_subnormal7976134
Ref: 257f7976134
Ref: library/decimal decimal Context is_zero7976251
Ref: 25807976251
Ref: library/decimal decimal Context ln7976360
Ref: 25817976360
Ref: library/decimal decimal Context log107976443
Ref: 25827976443
Ref: library/decimal decimal Context logb7976520
Ref: 25837976520
Ref: library/decimal decimal Context logical_and7976618
Ref: 25847976618
Ref: library/decimal decimal Context logical_invert7976743
Ref: 25857976743
Ref: library/decimal decimal Context logical_or7976821
Ref: 25867976821
Ref: library/decimal decimal Context logical_xor7976944
Ref: 25877976944
Ref: library/decimal decimal Context max7977069
Ref: 25887977069
Ref: library/decimal decimal Context max_mag7977166
Ref: 25897977166
Ref: library/decimal decimal Context min7977267
Ref: 258a7977267
Ref: library/decimal decimal Context min_mag7977364
Ref: 258b7977364
Ref: library/decimal decimal Context minus7977465
Ref: 258c7977465
Ref: library/decimal decimal Context multiply7977578
Ref: 258d7977578
Ref: library/decimal decimal Context next_minus7977658
Ref: 258e7977658
Ref: library/decimal decimal Context next_plus7977761
Ref: 258f7977761
Ref: library/decimal decimal Context next_toward7977863
Ref: 25907977863
Ref: library/decimal decimal Context normalize7977972
Ref: 25917977972
Ref: library/decimal decimal Context number_class7978049
Ref: 25927978049
Ref: library/decimal decimal Context plus7978138
Ref: 25937978138
Ref: library/decimal decimal Context power7978355
Ref: 25947978355
Ref: library/decimal decimal Context quantize7980151
Ref: 25957980151
Ref: library/decimal decimal Context radix7980274
Ref: 25967980274
Ref: library/decimal decimal Context remainder7980352
Ref: 25977980352
Ref: library/decimal decimal Context remainder_near7980547
Ref: 25987980547
Ref: library/decimal decimal Context rotate7980767
Ref: 25997980767
Ref: library/decimal decimal Context same_quantum7980852
Ref: 259a7980852
Ref: library/decimal decimal Context scaleb7980964
Ref: 259b7980964
Ref: library/decimal decimal Context shift7981082
Ref: 259c7981082
Ref: library/decimal decimal Context sqrt7981166
Ref: 259d7981166
Ref: library/decimal decimal Context subtract7981263
Ref: 259e7981263
Ref: library/decimal decimal Context to_eng_string7981351
Ref: 259f7981351
Ref: library/decimal decimal Context to_integral_exact7981715
Ref: 25a07981715
Ref: library/decimal decimal Context to_sci_string7981788
Ref: 25a17981788
Node: 常數<4>7981892
Ref: library/decimal constants7982030
Ref: 25a27982030
Ref: library/decimal decimal-rounding-modes7982030
Ref: 25a37982030
Ref: library/decimal decimal MAX_PREC7982466
Ref: 25617982466
Ref: library/decimal decimal MAX_EMAX7982603
Ref: 25647982603
Ref: library/decimal decimal MIN_EMIN7982740
Ref: 25637982740
Ref: library/decimal decimal MIN_ETINY7982878
Ref: 25a47982878
Ref: library/decimal decimal HAVE_THREADS7983006
Ref: 103f7983006
Ref: library/decimal decimal HAVE_CONTEXTVAR7983162
Ref: 1c757983162
Node: Rounding modes7983527
Ref: library/decimal rounding-modes7983657
Ref: 25627983657
Ref: library/decimal decimal ROUND_CEILING7983704
Ref: 25177983704
Ref: library/decimal decimal ROUND_DOWN7983775
Ref: 25187983775
Ref: library/decimal decimal ROUND_FLOOR7983833
Ref: 25197983833
Ref: library/decimal decimal ROUND_HALF_DOWN7983903
Ref: 251a7983903
Ref: library/decimal decimal ROUND_HALF_EVEN7983993
Ref: 251b7983993
Ref: library/decimal decimal ROUND_HALF_UP7984094
Ref: 251c7984094
Ref: library/decimal decimal ROUND_UP7984184
Ref: 251d7984184
Ref: library/decimal decimal ROUND_05UP7984242
Ref: 251e7984242
Node: Signals7984402
Ref: library/decimal decimal-signals7984543
Ref: 25a57984543
Ref: library/decimal signals7984543
Ref: 25a67984543
Ref: library/decimal decimal Clamped7985258
Ref: 251f7985258
Ref: library/decimal decimal DecimalException7985551
Ref: 25a77985551
Ref: library/decimal decimal DivisionByZero7985676
Ref: 25207985676
Ref: library/decimal decimal Inexact7986015
Ref: 25217986015
Ref: library/decimal decimal InvalidOperation7986291
Ref: 10447986291
Ref: library/decimal decimal Overflow7986733
Ref: 25247986733
Ref: library/decimal decimal Rounded7987145
Ref: 25227987145
Ref: library/decimal decimal Subnormal7987484
Ref: 25237987484
Ref: library/decimal decimal Underflow7987707
Ref: 25257987707
Ref: library/decimal decimal FloatOperation7987933
Ref: 103e7987933
Node: Floating-Point Notes7989210
Ref: library/decimal decimal-notes7989357
Ref: 25a87989357
Ref: library/decimal floating-point-notes7989357
Ref: 25a97989357
Node: Mitigating round-off error with increased precision7989496
Ref: library/decimal mitigating-round-off-error-with-increased-precision7989622
Ref: 25aa7989622
Node: 特殊值7991311
Ref: library/decimal special-values7991437
Ref: 25ab7991437
Node: Working with threads7994554
Ref: library/decimal decimal-threads7994701
Ref: 25ac7994701
Ref: library/decimal working-with-threads7994701
Ref: 25ad7994701
Node: Recipes7996073
Ref: library/decimal decimal-recipes7996211
Ref: 25ae7996211
Ref: library/decimal recipes7996211
Ref: 25af7996211
Node: Decimal FAQ8001056
Ref: library/decimal decimal-faq8001165
Ref: 25b08001165
Ref: library/decimal id18001165
Ref: 25b18001165
Ref: Decimal FAQ-Footnote-18010126
Ref: Decimal FAQ-Footnote-28010193
Ref: Decimal FAQ-Footnote-38010224
Ref: Decimal FAQ-Footnote-48010282
Ref: Decimal FAQ-Footnote-58010385
Node: fractions --- 有理數8010493
Ref: library/fractions doc8010666
Ref: 25b28010666
Ref: library/fractions fractions-rational-numbers8010666
Ref: 25b38010666
Ref: library/fractions module-fractions8010666
Ref: 538010666
Ref: library/fractions fractions Fraction8011028
Ref: 1c78011028
Ref: library/fractions fractions Fraction numerator8015349
Ref: 25b58015349
Ref: library/fractions fractions Fraction denominator8015430
Ref: 25b68015430
Ref: library/fractions fractions Fraction as_integer_ratio8015515
Ref: 25b78015515
Ref: library/fractions fractions Fraction is_integer8015758
Ref: 25b88015758
Ref: library/fractions fractions Fraction from_float8015884
Ref: 119d8015884
Ref: library/fractions fractions Fraction from_decimal8016339
Ref: 119e8016339
Ref: library/fractions fractions Fraction limit_denominator8016714
Ref: 25b48016714
Ref: library/fractions fractions Fraction __floor__8017586
Ref: 16858017586
Ref: library/fractions fractions Fraction __ceil__8017887
Ref: 16848017887
Ref: library/fractions fractions Fraction __round__8018078
Ref: 16838018078
Ref: library/fractions fractions Fraction __format__8018549
Ref: 25b98018549
Ref: fractions --- 有理數-Footnote-18020885
Ref: fractions --- 有理數-Footnote-28020954
Node: random --- 生成偽隨機數8020996
Ref: library/random doc8021157
Ref: 25ba8021157
Ref: library/random module-random8021157
Ref: a68021157
Ref: library/random random-generate-pseudo-random-numbers8021157
Ref: 25bb8021157
Ref: random --- 生成偽隨機數-Footnote-18024430
Ref: random --- 生成偽隨機數-Footnote-28024496
Node: 簿記函式 bookkeeping functions8024586
Ref: library/random bookkeeping-functions8024719
Ref: 25bd8024719
Ref: library/random random seed8024806
Ref: 120c8024806
Ref: library/random random getstate8025849
Ref: 25be8025849
Ref: library/random random setstate8026020
Ref: 25bf8026020
Node: 回傳位元組的函式8026265
Ref: library/random functions-for-bytes8026428
Ref: 25c08026428
Ref: library/random random randbytes8026487
Ref: 186d8026487
Node: 回傳整數的函式8026703
Ref: library/random functions-for-integers8026853
Ref: 25c28026853
Ref: library/random random randrange8026907
Ref: 8108026907
Ref: library/random random randint8027896
Ref: 11c78027896
Ref: library/random random getrandbits8028042
Ref: fae8028042
Node: 回傳序列的函式8028456
Ref: library/random functions-for-sequences8028594
Ref: 25c38028594
Ref: library/random random choice8028648
Ref: 11c88028648
Ref: library/random random choices8028800
Ref: c6d8028800
Ref: library/random random shuffle8030627
Ref: 6eb8030627
Ref: library/random random sample8031245
Ref: 6ea8031245
Node: 離散分布8032597
Ref: library/random discrete-distributions8032726
Ref: 25c48032726
Ref: library/random random binomialvariate8032800
Ref: 4578032800
Ref: 離散分布-Footnote-18033283
Node: 實數分布8033347
Ref: library/random id18033470
Ref: 25c58033470
Ref: library/random real-valued-distributions8033470
Ref: 25c68033470
Ref: library/random random random8033713
Ref: 6ec8033713
Ref: library/random random uniform8033814
Ref: 25c78033814
Ref: library/random random triangular8034154
Ref: 25c88034154
Ref: library/random random betavariate8034454
Ref: 25c98034454
Ref: library/random random expovariate8034636
Ref: 4588034636
Ref: library/random random gammavariate8035056
Ref: 25ca8035056
Ref: library/random random gauss8035591
Ref: 17468035591
Ref: library/random random lognormvariate8036223
Ref: 25cb8036223
Ref: library/random random normalvariate8036485
Ref: 17478036485
Ref: library/random random vonmisesvariate8036675
Ref: 25cc8036675
Ref: library/random random paretovariate8036963
Ref: 25cd8036963
Ref: library/random random weibullvariate8037081
Ref: 25ce8037081
Node: 替代產生器8037235
Ref: library/random alternative-generator8037398
Ref: 25cf8037398
Ref: library/random random Random8037442
Ref: 17aa8037442
Ref: library/random random Random seed8037918
Ref: 18858037918
Ref: library/random random Random getstate8038075
Ref: 25d08038075
Ref: library/random random Random setstate8038223
Ref: 25d18038223
Ref: library/random random Random random8038376
Ref: 25d28038376
Ref: library/random random Random getrandbits8038589
Ref: 25d38038589
Ref: library/random random SystemRandom8038743
Ref: 25bc8038743
Node: 關於 Reproducibility（復現性）的注意事項8039173
Ref: library/random notes-on-reproducibility8039333
Ref: 25d48039333
Node: 範例<6>8039995
Ref: library/random examples8040152
Ref: 25d58040152
Ref: library/random random-examples8040152
Ref: 11748040152
Ref: 範例<6>-Footnote-18045264
Ref: 範例<6>-Footnote-28045329
Ref: 範例<6>-Footnote-38045410
Ref: 範例<6>-Footnote-48045456
Ref: 範例<6>-Footnote-58045508
Ref: 範例<6>-Footnote-68045563
Ref: 範例<6>-Footnote-78045631
Ref: 範例<6>-Footnote-88045667
Ref: 範例<6>-Footnote-98045737
Node: 使用方案8045773
Ref: library/random recipes8045896
Ref: 25d68045896
Ref: 使用方案-Footnote-18048938
Node: Command-line usage8049006
Ref: library/random command-line-usage8049140
Ref: 25d78049140
Ref: library/random random-cli8049140
Ref: 1398049140
Ref: library/random cmdoption-random-h8049401
Ref: 25d88049401
Ref: library/random cmdoption-random-help8049401
Ref: 25d98049401
Ref: library/random cmdoption-random-c8049463
Ref: 25da8049463
Ref: library/random cmdoption-random-choice8049498
Ref: 25db8049498
Ref: library/random cmdoption-random-i8049597
Ref: 25dc8049597
Ref: library/random cmdoption-random-integer8049616
Ref: 25dd8049616
Ref: library/random cmdoption-random-f8049733
Ref: 25de8049733
Ref: library/random cmdoption-random-float8049752
Ref: 25df8049752
Node: Command-line example8050081
Ref: library/random command-line-example8050194
Ref: 25e08050194
Ref: library/random random-cli-example8050194
Ref: 25e18050194
Node: statistics --- 數學統計函式8051023
Ref: library/statistics doc8051152
Ref: 25e28051152
Ref: library/statistics module-statistics8051152
Ref: bd8051152
Ref: library/statistics statistics-mathematical-statistics-functions8051152
Ref: 25e38051152
Ref: statistics --- 數學統計函式-Footnote-18053508
Ref: statistics --- 數學統計函式-Footnote-28053578
Ref: statistics --- 數學統計函式-Footnote-38053604
Node: 平均值與中央位置量數8053631
Ref: library/statistics averages-and-measures-of-central-location8053763
Ref: 25e48053763
Node: 離度 spread 的測量8055709
Ref: library/statistics measures-of-spread8055883
Ref: 25e98055883
Node: 兩個輸入之間的關係統計8056437
Ref: library/statistics statistics-for-relations-between-two-inputs8056593
Ref: 25ec8056593
Node: 函式細節8057113
Ref: library/statistics function-details8057255
Ref: 25ed8057255
Ref: library/statistics statistics mean8057417
Ref: 6768057417
Ref: library/statistics statistics fmean8058864
Ref: 9d88058864
Ref: library/statistics statistics geometric_mean8059843
Ref: 9d98059843
Ref: library/statistics statistics harmonic_mean8060474
Ref: c888060474
Ref: library/statistics statistics kde8062071
Ref: 22f8062071
Ref: library/statistics statistics kde_random8063928
Ref: 2308063928
Ref: library/statistics statistics median8064971
Ref: 25e58064971
Ref: library/statistics statistics median_low8065941
Ref: 25e68065941
Ref: library/statistics statistics median_high8066563
Ref: 25e78066563
Ref: library/statistics statistics median_grouped8067189
Ref: 25e88067189
Ref: library/statistics statistics mode8069098
Ref: a358069098
Ref: library/statistics statistics multimode8070573
Ref: 9da8070573
Ref: library/statistics statistics pstdev8071001
Ref: 25ea8071001
Ref: library/statistics statistics pvariance8071276
Ref: 25eb8071276
Ref: library/statistics statistics stdev8073406
Ref: 6788073406
Ref: library/statistics statistics variance8073680
Ref: 6778073680
Ref: library/statistics statistics quantiles8075821
Ref: 9db8075821
Ref: library/statistics statistics covariance8078630
Ref: 7d48078630
Ref: library/statistics statistics correlation8079276
Ref: 4638079276
Ref: library/statistics statistics linear_regression8081274
Ref: 7d58081274
Ref: 函式細節-Footnote-18083670
Ref: 函式細節-Footnote-28083716
Ref: 函式細節-Footnote-38083771
Ref: 函式細節-Footnote-48083867
Ref: 函式細節-Footnote-58083925
Ref: 函式細節-Footnote-68083997
Ref: 函式細節-Footnote-78084048
Ref: 函式細節-Footnote-88084118
Ref: 函式細節-Footnote-98084199
Ref: 函式細節-Footnote-108084271
Ref: 函式細節-Footnote-118084335
Node: 例外<3>8084393
Ref: library/statistics exceptions8084519
Ref: 25ef8084519
Ref: library/statistics statistics StatisticsError8084583
Ref: 25ee8084583
Node: NormalDist 物件8084701
Ref: library/statistics normaldist-objects8084836
Ref: 25f08084836
Ref: library/statistics statistics NormalDist8085203
Ref: 9dc8085203
Ref: library/statistics statistics NormalDist mean8085461
Ref: 25f18085461
Ref: library/statistics statistics NormalDist median8085547
Ref: 25f28085547
Ref: library/statistics statistics NormalDist mode8085629
Ref: 25f38085629
Ref: library/statistics statistics NormalDist stdev8085706
Ref: 25f48085706
Ref: library/statistics statistics NormalDist variance8085787
Ref: 25f58085787
Ref: library/statistics statistics NormalDist from_samples8085871
Ref: 25f68085871
Ref: library/statistics statistics NormalDist samples8086422
Ref: 25f78086422
Ref: library/statistics statistics NormalDist pdf8087014
Ref: 25f88087014
Ref: library/statistics statistics NormalDist cdf8087535
Ref: 25f98087535
Ref: library/statistics statistics NormalDist inv_cdf8087758
Ref: 25fa8087758
Ref: library/statistics statistics NormalDist overlap8088159
Ref: 25fb8088159
Ref: library/statistics statistics NormalDist quantiles8088353
Ref: 25fc8088353
Ref: library/statistics statistics NormalDist zscore8088795
Ref: 25fd8088795
Ref: NormalDist 物件-Footnote-18090073
Ref: NormalDist 物件-Footnote-28090137
Ref: NormalDist 物件-Footnote-38090197
Ref: NormalDist 物件-Footnote-48090251
Ref: NormalDist 物件-Footnote-58090308
Ref: NormalDist 物件-Footnote-68090362
Ref: NormalDist 物件-Footnote-78090407
Ref: NormalDist 物件-Footnote-88090463
Ref: NormalDist 物件-Footnote-98090520
Ref: NormalDist 物件-Footnote-108090567
Ref: NormalDist 物件-Footnote-118090635
Ref: NormalDist 物件-Footnote-128090707
Ref: NormalDist 物件-Footnote-138090764
Ref: NormalDist 物件-Footnote-148090899
Ref: NormalDist 物件-Footnote-158090946
Ref: NormalDist 物件-Footnote-168091024
Node: 範例與錦囊妙計8091109
Ref: library/statistics examples-and-recipes8091226
Ref: 25fe8091226
Node: 經典機率問題8091538
Ref: library/statistics classic-probability-problems8091669
Ref: 25ff8091669
Ref: 經典機率問題-Footnote-18092422
Ref: 經典機率問題-Footnote-28092493
Ref: 經典機率問題-Footnote-38092540
Node: 用於模擬的蒙地卡羅 Monte Carlo 輸入8092585
Ref: library/statistics monte-carlo-inputs-for-simulations8092743
Ref: 26008092743
Ref: 用於模擬的蒙地卡羅 Monte Carlo 輸入-Footnote-18093433
Node: 近似二項分布8093490
Ref: library/statistics approximating-binomial-distributions8093677
Ref: 26018093677
Ref: 近似二項分布-Footnote-18095014
Node: 單純貝氏分類器 Naive bayesian classifier8095078
Ref: library/statistics naive-bayesian-classifier8095210
Ref: 26028095210
Ref: 單純貝氏分類器 Naive bayesian classifier-Footnote-18097127
Ref: 單純貝氏分類器 Naive bayesian classifier-Footnote-28097211
Ref: 單純貝氏分類器 Naive bayesian classifier-Footnote-38097267
Node: 函式編程模組8097337
Ref: library/functional doc8097491
Ref: 26038097491
Ref: library/functional functional-programming-modules8097491
Ref: 26048097491
Node: itertools --- 建立產生高效率迴圈之疊代器的函式8098049
Ref: library/itertools doc8098231
Ref: 26058098231
Ref: library/itertools itertools-functions-creating-iterators-for-efficient-looping8098231
Ref: 26068098231
Ref: library/itertools module-itertools8098231
Ref: 758098231
Node: Itertool 函式8109562
Ref: library/itertools itertool-functions8109707
Ref: 260e8109707
Ref: library/itertools itertools-functions8109707
Ref: 260f8109707
Ref: library/itertools itertools accumulate8109927
Ref: 9a18109927
Ref: library/itertools itertools batched8112262
Ref: 1e68112262
Ref: library/itertools itertools chain8113618
Ref: 205b8113618
Ref: library/itertools itertools chain from_iterable8114078
Ref: 26098114078
Ref: library/itertools itertools combinations8114485
Ref: 12a68114485
Ref: library/itertools itertools combinations_with_replacement8116017
Ref: 12198116017
Ref: library/itertools itertools compress8117493
Ref: 121a8117493
Ref: library/itertools itertools count8117941
Ref: 121b8117941
Ref: library/itertools itertools cycle8118703
Ref: 26078118703
Ref: library/itertools itertools dropwhile8119391
Ref: 260a8119391
Ref: library/itertools itertools filterfalse8120082
Ref: 20428120082
Ref: library/itertools itertools groupby8120632
Ref: 260b8120632
Ref: library/itertools itertools islice8123177
Ref: af08123177
Ref: library/itertools itertools pairwise8124764
Ref: 7b98124764
Ref: library/itertools itertools permutations8125337
Ref: 181d8125337
Ref: library/itertools itertools product8127289
Ref: 12a78127289
Ref: library/itertools itertools repeat8128812
Ref: 26088128812
Ref: library/itertools itertools starmap8129462
Ref: 107d8129462
Ref: library/itertools itertools takewhile8130073
Ref: 260c8130073
Ref: library/itertools itertools tee8130828
Ref: 260d8130828
Ref: library/itertools itertools zip_longest8132222
Ref: 12358132222
Ref: Itertool 函式-Footnote-18133695
Ref: Itertool 函式-Footnote-28133769
Ref: Itertool 函式-Footnote-38133824
Node: Itertools 應用技巧8133922
Ref: library/itertools id18134067
Ref: 26118134067
Ref: library/itertools itertools-recipes8134067
Ref: 11f78134067
Ref: Itertools 應用技巧-Footnote-18147510
Ref: Itertools 應用技巧-Footnote-28147559
Node: functools --- 可呼叫物件上的高階函式與操作8147630
Ref: library/functools doc8147861
Ref: 26128147861
Ref: library/functools functools-higher-order-functions-and-operations-on-callable-objects8147861
Ref: 26138147861
Ref: library/functools module-functools8147861
Ref: 558147861
Ref: library/functools functools cache8148312
Ref: 241a8148312
Ref: library/functools functools cached_property8149533
Ref: 4e78149533
Ref: library/functools functools cmp_to_key8152717
Ref: 11728152717
Ref: library/functools functools lru_cache8153650
Ref: 9938153650
Ref: library/functools functools total_ordering8158940
Ref: ee68158940
Ref: library/functools functools partial8161017
Ref: 3568161017
Ref: library/functools functools partialmethod8162313
Ref: a1e8162313
Ref: library/functools functools reduce8164105
Ref: 126f8164105
Ref: library/functools functools singledispatch8165380
Ref: 5df8165380
Ref: library/functools functools singledispatchmethod8170729
Ref: 9948170729
Ref: library/functools functools update_wrapper8172412
Ref: fc58172412
Ref: library/functools functools wraps8174525
Ref: f008174525
Ref: functools --- 可呼叫物件上的高階函式與操作-Footnote-18175783
Ref: functools --- 可呼叫物件上的高階函式與操作-Footnote-28175852
Ref: functools --- 可呼叫物件上的高階函式與操作-Footnote-38175902
Ref: functools --- 可呼叫物件上的高階函式與操作-Footnote-48175944
Ref: functools --- 可呼叫物件上的高階函式與操作-Footnote-58176036
Ref: functools --- 可呼叫物件上的高階函式與操作-Footnote-68176094
Ref: functools --- 可呼叫物件上的高階函式與操作-Footnote-78176149
Node: partial 物件8176214
Ref: library/functools id18176321
Ref: 26178176321
Ref: library/functools partial-objects8176321
Ref: 26158176321
Ref: library/functools functools partial func8176494
Ref: 26188176494
Ref: library/functools functools partial args8176674
Ref: 26198176674
Ref: library/functools functools partial keywords8176824
Ref: 261a8176824
Node: operator --- 標準運算子替代函式8177334
Ref: library/operator doc8177494
Ref: 261b8177494
Ref: library/operator module-operator8177494
Ref: 8f8177494
Ref: library/operator operator-standard-operators-as-functions8177494
Ref: 261c8177494
Ref: library/operator operator lt8178264
Ref: 261d8178264
Ref: library/operator operator le8178295
Ref: 261e8178295
Ref: library/operator operator eq8178326
Ref: 261f8178326
Ref: library/operator operator ne8178357
Ref: 26208178357
Ref: library/operator operator ge8178388
Ref: 26218178388
Ref: library/operator operator gt8178419
Ref: 26228178419
Ref: library/operator operator __lt__8178450
Ref: 26238178450
Ref: library/operator operator __le__8178485
Ref: 26248178485
Ref: library/operator operator __eq__8178520
Ref: 26258178520
Ref: library/operator operator __ne__8178555
Ref: 26268178555
Ref: library/operator operator __ge__8178590
Ref: 26278178590
Ref: library/operator operator __gt__8178625
Ref: 26288178625
Ref: library/operator operator not_8179280
Ref: 26298179280
Ref: library/operator operator __not__8179312
Ref: 262a8179312
Ref: library/operator operator truth8179600
Ref: 262b8179600
Ref: library/operator operator is_8179778
Ref: 262c8179778
Ref: library/operator operator is_not8179864
Ref: 262d8179864
Ref: library/operator operator abs8180004
Ref: 262e8180004
Ref: library/operator operator __abs__8180035
Ref: 262f8180035
Ref: library/operator operator add8180106
Ref: 26308180106
Ref: library/operator operator __add__8180138
Ref: 26318180138
Ref: library/operator operator and_8180230
Ref: 26328180230
Ref: library/operator operator __and__8180263
Ref: 26338180263
Ref: library/operator operator floordiv8180360
Ref: 26348180360
Ref: library/operator operator __floordiv__8180397
Ref: 26358180397
Ref: library/operator operator index8180468
Ref: 18118180468
Ref: library/operator operator __index__8180499
Ref: 26368180499
Ref: library/operator operator inv8180757
Ref: 26378180757
Ref: library/operator operator invert8180788
Ref: 26388180788
Ref: library/operator operator __inv__8180822
Ref: 26398180822
Ref: library/operator operator __invert__8180857
Ref: 263a8180857
Ref: library/operator operator lshift8180986
Ref: 263b8180986
Ref: library/operator operator __lshift__8181021
Ref: 263c8181021
Ref: library/operator operator mod8181105
Ref: 263d8181105
Ref: library/operator operator __mod__8181137
Ref: 263e8181137
Ref: library/operator operator mul8181202
Ref: 26108181202
Ref: library/operator operator __mul__8181234
Ref: 263f8181234
Ref: library/operator operator matmul8181326
Ref: ddb8181326
Ref: library/operator operator __matmul__8181361
Ref: 26408181361
Ref: library/operator operator neg8181457
Ref: 26418181457
Ref: library/operator operator __neg__8181488
Ref: 26428181488
Ref: library/operator operator or_8181578
Ref: 26438181578
Ref: library/operator operator __or__8181610
Ref: 26448181610
Ref: library/operator operator pos8181702
Ref: 26458181702
Ref: library/operator operator __pos__8181733
Ref: 26468181733
Ref: library/operator operator pow8181820
Ref: 26478181820
Ref: library/operator operator __pow__8181852
Ref: 26488181852
Ref: library/operator operator rshift8181945
Ref: 26498181945
Ref: library/operator operator __rshift__8181980
Ref: 264a8181980
Ref: library/operator operator sub8182064
Ref: 264b8182064
Ref: library/operator operator __sub__8182096
Ref: 264c8182096
Ref: library/operator operator truediv8182161
Ref: 264d8182161
Ref: library/operator operator __truediv__8182197
Ref: 264e8182197
Ref: library/operator operator xor8182338
Ref: 264f8182338
Ref: library/operator operator __xor__8182370
Ref: 26508182370
Ref: library/operator operator concat8182560
Ref: 26518182560
Ref: library/operator operator __concat__8182595
Ref: 26528182595
Ref: library/operator operator contains8182690
Ref: 87f8182690
Ref: library/operator operator __contains__8182727
Ref: 26538182727
Ref: library/operator operator countOf8182847
Ref: 8818182847
Ref: library/operator operator delitem8182931
Ref: 26548182931
Ref: library/operator operator __delitem__8182967
Ref: 26558182967
Ref: library/operator operator getitem8183052
Ref: 26568183052
Ref: library/operator operator __getitem__8183088
Ref: 26578183088
Ref: library/operator operator indexOf8183173
Ref: 8808183173
Ref: library/operator operator setitem8183269
Ref: 26588183269
Ref: library/operator operator __setitem__8183308
Ref: 26598183308
Ref: library/operator operator length_hint8183403
Ref: f108183403
Ref: library/operator operator call8183709
Ref: 17808183709
Ref: library/operator operator __call__8183761
Ref: 265a8183761
Ref: library/operator operator attrgetter8184167
Ref: dd98184167
Ref: library/operator operator itemgetter8185490
Ref: a058185490
Ref: library/operator operator methodcaller8187246
Ref: dda8187246
Ref: operator --- 標準運算子替代函式-Footnote-18188066
Node: 運算子與函式間的對映8188134
Ref: library/operator mapping-operators-to-functions8188275
Ref: 265b8188275
Ref: library/operator operator-map8188275
Ref: 265c8188275
Node: 原地 in-place 運算子8195738
Ref: library/operator in-place-operators8195879
Ref: 265d8195879
Ref: library/operator operator iadd8197088
Ref: 265f8197088
Ref: library/operator operator __iadd__8197121
Ref: 26608197121
Ref: library/operator operator iand8197212
Ref: 26618197212
Ref: library/operator operator __iand__8197245
Ref: 26628197245
Ref: library/operator operator iconcat8197336
Ref: 26638197336
Ref: library/operator operator __iconcat__8197372
Ref: 26648197372
Ref: library/operator operator ifloordiv8197500
Ref: 26658197500
Ref: library/operator operator __ifloordiv__8197538
Ref: 26668197538
Ref: library/operator operator ilshift8197640
Ref: 26678197640
Ref: library/operator operator __ilshift__8197676
Ref: 26688197676
Ref: library/operator operator imod8197774
Ref: 26698197774
Ref: library/operator operator __imod__8197807
Ref: 266a8197807
Ref: library/operator operator imul8197898
Ref: 266b8197898
Ref: library/operator operator __imul__8197931
Ref: 266c8197931
Ref: library/operator operator imatmul8198022
Ref: ddc8198022
Ref: library/operator operator __imatmul__8198058
Ref: 266d8198058
Ref: library/operator operator ior8198183
Ref: 266e8198183
Ref: library/operator operator __ior__8198215
Ref: 266f8198215
Ref: library/operator operator ipow8198304
Ref: 26708198304
Ref: library/operator operator __ipow__8198337
Ref: 26718198337
Ref: library/operator operator irshift8198429
Ref: 26728198429
Ref: library/operator operator __irshift__8198465
Ref: 26738198465
Ref: library/operator operator isub8198563
Ref: 26748198563
Ref: library/operator operator __isub__8198596
Ref: 26758198596
Ref: library/operator operator itruediv8198687
Ref: 26768198687
Ref: library/operator operator __itruediv__8198724
Ref: 26778198724
Ref: library/operator operator ixor8198823
Ref: 26788198823
Ref: library/operator operator __ixor__8198856
Ref: 26798198856
Node: 檔案與目錄存取8198947
Ref: library/filesys doc8199112
Ref: 267a8199112
Ref: library/filesys file-and-directory-access8199112
Ref: 267b8199112
Ref: library/filesys filesys8199112
Ref: 267c8199112
Node: pathlib --- 物件導向檔案系統路徑8200154
Ref: library/pathlib doc8200299
Ref: 267d8200299
Ref: library/pathlib module-pathlib8200299
Ref: 938200299
Ref: library/pathlib pathlib-object-oriented-filesystem-paths8200299
Ref: 267e8200299
Ref: pathlib --- 物件導向檔案系統路徑-Footnote-18202397
Ref: pathlib --- 物件導向檔案系統路徑-Footnote-28202462
Node: 基本用法8202504
Ref: library/pathlib basic-use8202617
Ref: 26828202617
Node: Exceptions<2>8203543
Ref: library/pathlib exceptions8203674
Ref: 26838203674
Ref: library/pathlib pathlib UnsupportedOperation8203715
Ref: 20c8203715
Node: 純路徑8203926
Ref: library/pathlib id18204057
Ref: 26848204057
Ref: library/pathlib pure-paths8204057
Ref: 267f8204057
Ref: library/pathlib pathlib PurePath8204259
Ref: 44e8204259
Ref: library/pathlib pathlib PurePosixPath8206683
Ref: 26858206683
Ref: library/pathlib pathlib PureWindowsPath8206998
Ref: 16018206998
Ref: 純路徑-Footnote-18207719
Node: 通用屬性8207778
Ref: library/pathlib general-properties8207854
Ref: 26868207854
Node: 運算子8208732
Ref: library/pathlib operators8208841
Ref: 26878208841
Node: 對個別組成的存取8210441
Ref: library/pathlib accessing-individual-parts8210553
Ref: 26888210553
Ref: library/pathlib pathlib PurePath parts8210698
Ref: 26898210698
Node: 方法與屬性8211110
Ref: library/pathlib methods-and-properties8211204
Ref: 268a8211204
Ref: library/pathlib pathlib PurePath parser8211291
Ref: 2118211291
Ref: library/pathlib pathlib PurePath drive8211497
Ref: 268b8211497
Ref: library/pathlib pathlib PurePath root8211966
Ref: 268c8211966
Ref: library/pathlib pathlib PurePath anchor8212972
Ref: 268d8212972
Ref: library/pathlib pathlib PurePath parents8213329
Ref: 7c48213329
Ref: library/pathlib pathlib PurePath parent8213797
Ref: 162b8213797
Ref: library/pathlib pathlib PurePath name8214602
Ref: 268e8214602
Ref: library/pathlib pathlib PurePath suffix8215015
Ref: 268f8215015
Ref: library/pathlib pathlib PurePath suffixes8215372
Ref: 26908215372
Ref: library/pathlib pathlib PurePath stem8215705
Ref: 26918215705
Ref: library/pathlib pathlib PurePath as_posix8216007
Ref: 26928216007
Ref: library/pathlib pathlib PurePath is_absolute8216258
Ref: 16298216258
Ref: library/pathlib pathlib PurePath is_relative_to8216880
Ref: 2ab8216880
Ref: library/pathlib pathlib PurePath is_reserved8217569
Ref: 2868217569
Ref: library/pathlib pathlib PurePath joinpath8218172
Ref: 26938218172
Ref: library/pathlib pathlib PurePath full_match8218731
Ref: 2108218731
Ref: library/pathlib pathlib PurePath match8219657
Ref: 4548219657
Ref: library/pathlib pathlib PurePath relative_to8220547
Ref: 2ac8220547
Ref: library/pathlib pathlib PurePath with_name8222682
Ref: 15f28222682
Ref: library/pathlib pathlib PurePath with_stem8223385
Ref: 15538223385
Ref: library/pathlib pathlib PurePath with_suffix8224392
Ref: 150b8224392
Ref: library/pathlib pathlib PurePath with_segments8225044
Ref: 44f8225044
Ref: 方法與屬性-Footnote-18225979
Node: 實體路徑8226071
Ref: library/pathlib concrete-paths8226205
Ref: 26808226205
Ref: library/pathlib id28226205
Ref: 26958226205
Ref: library/pathlib pathlib Path8226441
Ref: 20e8226441
Ref: library/pathlib pathlib PosixPath8226811
Ref: 26968226811
Ref: library/pathlib pathlib WindowsPath8227298
Ref: 26818227298
Node: Parsing and generating URIs8228765
Ref: library/pathlib parsing-and-generating-uris8228879
Ref: 26978228879
Ref: library/pathlib pathlib Path from_uri8229168
Ref: 20f8229168
Ref: library/pathlib pathlib Path as_uri8230192
Ref: 26998230192
Ref: Parsing and generating URIs-Footnote-18230742
Node: Expanding and resolving paths8230801
Ref: library/pathlib expanding-and-resolving-paths8230953
Ref: 269a8230953
Ref: library/pathlib pathlib Path home8231034
Ref: de98231034
Ref: library/pathlib pathlib Path expanduser8231387
Ref: de88231387
Ref: library/pathlib pathlib Path cwd8231785
Ref: 16288231785
Ref: library/pathlib pathlib Path absolute8232010
Ref: 15a68232010
Ref: library/pathlib pathlib Path resolve8232317
Ref: 15f78232317
Ref: library/pathlib pathlib Path readlink8233458
Ref: 8c48233458
Node: Querying file type and status8233932
Ref: library/pathlib querying-file-type-and-status8234082
Ref: 269b8234082
Ref: library/pathlib pathlib Path stat8234522
Ref: 7c78234522
Ref: library/pathlib pathlib Path lstat8235123
Ref: 269c8235123
Ref: library/pathlib pathlib Path exists8235301
Ref: 9ba8235301
Ref: library/pathlib pathlib Path is_file8235848
Ref: 2148235848
Ref: library/pathlib pathlib Path is_dir8236355
Ref: 2158236355
Ref: library/pathlib pathlib Path is_symlink8236873
Ref: 9bc8236873
Ref: library/pathlib pathlib Path is_junction8237122
Ref: 4538237122
Ref: library/pathlib pathlib Path is_mount8237355
Ref: 9bb8237355
Ref: library/pathlib pathlib Path is_socket8238072
Ref: 9c08238072
Ref: library/pathlib pathlib Path is_fifo8238450
Ref: 9bf8238450
Ref: library/pathlib pathlib Path is_block_device8238811
Ref: 9bd8238811
Ref: library/pathlib pathlib Path is_char_device8239209
Ref: 9be8239209
Ref: library/pathlib pathlib Path samefile8239615
Ref: de68239615
Node: Reading and writing files8240152
Ref: library/pathlib reading-and-writing-files8240285
Ref: 269d8240285
Ref: library/pathlib pathlib Path open8240358
Ref: 269e8240358
Ref: library/pathlib pathlib Path read_text8240703
Ref: deb8240703
Ref: library/pathlib pathlib Path read_bytes8241200
Ref: ded8241200
Ref: library/pathlib pathlib Path write_text8241513
Ref: dea8241513
Ref: library/pathlib pathlib Path write_bytes8242065
Ref: dec8242065
Node: 讀取目錄8242455
Ref: library/pathlib reading-directories8242580
Ref: 269f8242580
Ref: library/pathlib pathlib Path iterdir8242623
Ref: 15258242623
Ref: library/pathlib pathlib Path glob8243445
Ref: 2128243445
Ref: library/pathlib pathlib Path rglob8245387
Ref: 2138245387
Ref: library/pathlib pathlib Path walk8246103
Ref: 4508246103
Node: 建立檔案與目錄8250966
Ref: library/pathlib creating-files-and-directories8251087
Ref: 26a18251087
Ref: library/pathlib pathlib Path touch8251145
Ref: 26a28251145
Ref: library/pathlib pathlib Path mkdir8251697
Ref: de78251697
Ref: library/pathlib pathlib Path symlink_to8252746
Ref: 7c68252746
Ref: library/pathlib pathlib Path hardlink_to8253826
Ref: 7c58253826
Node: Renaming and deleting8254268
Ref: library/pathlib renaming-and-deleting8254402
Ref: 26a38254402
Ref: library/pathlib pathlib Path rename8254467
Ref: 26a48254467
Ref: library/pathlib pathlib Path replace8255524
Ref: 26a58255524
Ref: library/pathlib pathlib Path unlink8256044
Ref: 18f78256044
Ref: library/pathlib pathlib Path rmdir8256525
Ref: 26a08256525
Node: Permissions and ownership8256601
Ref: library/pathlib permissions-and-ownership8256705
Ref: 26a68256705
Ref: library/pathlib pathlib Path owner8256778
Ref: 2168256778
Ref: library/pathlib pathlib Path group8257378
Ref: 2178257378
Ref: library/pathlib pathlib Path chmod8257980
Ref: 7c88257980
Ref: library/pathlib pathlib Path lchmod8258564
Ref: 26a78258564
Node: Pattern language8258762
Ref: library/pathlib pathlib-pattern-language8258916
Ref: 26948258916
Ref: library/pathlib pattern-language8258916
Ref: 26a88258916
Node: Comparison to the glob module8261069
Ref: library/pathlib comparison-to-the-glob-module8261251
Ref: 26a98261251
Node: Comparison to the os and os path modules8262683
Ref: library/pathlib comparison-to-the-os-and-os-path-modules8262840
Ref: 26aa8262840
Node: Corresponding tools8265009
Ref: library/pathlib corresponding-tools8265105
Ref: 26ab8265105
Ref: Corresponding tools-Footnote-18270387
Ref: Corresponding tools-Footnote-28270695
Ref: Corresponding tools-Footnote-38270874
Ref: Corresponding tools-Footnote-48271096
Node: os path --- 常見的路徑名操作8271328
Ref: library/os path doc8271526
Ref: 26af8271526
Ref: library/os path module-os path8271526
Ref: 928271526
Ref: library/os path os-path-common-pathname-manipulations8271526
Ref: 26b08271526
Ref: library/os path os path abspath8273452
Ref: 12af8273452
Ref: library/os path os path basename8273762
Ref: 26ad8273762
Ref: library/os path os path commonpath8274230
Ref: de38274230
Ref: library/os path os path commonprefix8274784
Ref: de48274784
Ref: library/os path os path dirname8275413
Ref: 26ac8275413
Ref: library/os path os path exists8275677
Ref: 9b28275677
Ref: library/os path os path lexists8276273
Ref: 9b38276273
Ref: library/os path os path expanduser8276586
Ref: 9b88276586
Ref: library/os path os path expandvars8277662
Ref: 13478277662
Ref: library/os path os path getatime8278126
Ref: 26b28278126
Ref: library/os path os path getmtime8278387
Ref: 26b38278387
Ref: library/os path os path getctime8278721
Ref: 26b48278721
Ref: library/os path os path getsize8279210
Ref: 26b58279210
Ref: library/os path os path isabs8279456
Ref: 2098279456
Ref: library/os path os path isfile8279900
Ref: 9b58279900
Ref: library/os path os path isdir8280242
Ref: 9b48280242
Ref: library/os path os path isjunction8280577
Ref: 44b8280577
Ref: library/os path os path islink8280842
Ref: 9b08280842
Ref: library/os path os path ismount8281142
Ref: 9b68281142
Ref: library/os path os path isdevdrive8282063
Ref: 153c8282063
Ref: library/os path os path isreserved8282843
Ref: 2088282843
Ref: library/os path os path join8283695
Ref: 15278283695
Ref: library/os path os path normcase8284750
Ref: 26b68284750
Ref: library/os path os path normpath8285059
Ref: 12ae8285059
Ref: library/os path os path realpath8285888
Ref: 20a8285888
Ref: library/os path os path relpath8287030
Ref: 4528287030
Ref: library/os path os path samefile8287526
Ref: f148287526
Ref: library/os path os path sameopenfile8288053
Ref: 26b88288053
Ref: library/os path os path samestat8288322
Ref: f138288322
Ref: library/os path os path split8288808
Ref: 26b18288808
Ref: library/os path os path splitdrive8289608
Ref: b9b8289608
Ref: library/os path os path splitroot8290423
Ref: 44c8290423
Ref: library/os path os path splitext8291664
Ref: 26ae8291664
Ref: library/os path os path supports_unicode_filenames8292557
Ref: 13f78292557
Ref: os path --- 常見的路徑名操作-Footnote-18292785
Ref: os path --- 常見的路徑名操作-Footnote-28292856
Ref: os path --- 常見的路徑名操作-Footnote-38292925
Ref: os path --- 常見的路徑名操作-Footnote-48292991
Ref: os path --- 常見的路徑名操作-Footnote-58293046
Ref: os path --- 常見的路徑名操作-Footnote-68293138
Node: fileinput --- 逐列疊代多個輸入串流8293230
Ref: library/fileinput doc8293416
Ref: 26b98293416
Ref: library/fileinput fileinput-iterate-over-lines-from-multiple-input-streams8293416
Ref: 26ba8293416
Ref: library/fileinput module-fileinput8293416
Ref: 518293416
Ref: library/fileinput fileinput input8295690
Ref: 7a38295690
Ref: library/fileinput fileinput filename8296928
Ref: 26bb8296928
Ref: library/fileinput fileinput fileno8297082
Ref: 139b8297082
Ref: library/fileinput fileinput lineno8297275
Ref: 26bc8297275
Ref: library/fileinput fileinput filelineno8297546
Ref: 26bd8297546
Ref: library/fileinput fileinput isfirstline8297810
Ref: 26be8297810
Ref: library/fileinput fileinput isstdin8297960
Ref: 26bf8297960
Ref: library/fileinput fileinput nextfile8298101
Ref: 26c08298101
Ref: library/fileinput fileinput close8298639
Ref: 26c18298639
Ref: library/fileinput fileinput FileInput8298808
Ref: 6db8298808
Ref: library/fileinput fileinput hook_compressed8301518
Ref: 7a48301518
Ref: library/fileinput fileinput hook_encoded8302314
Ref: c478302314
Ref: fileinput --- 逐列疊代多個輸入串流-Footnote-18302902
Node: stat --- 直譯 stat 的結果8302971
Ref: library/stat doc8303154
Ref: 26c28303154
Ref: library/stat module-stat8303154
Ref: bc8303154
Ref: library/stat stat-interpreting-stat-results8303154
Ref: 26c38303154
Ref: library/stat stat S_ISDIR8303816
Ref: 26c48303816
Ref: library/stat stat S_ISCHR8303904
Ref: 26c58303904
Ref: library/stat stat S_ISBLK8304017
Ref: 26c68304017
Ref: library/stat stat S_ISREG8304121
Ref: 26c78304121
Ref: library/stat stat S_ISFIFO8304212
Ref: 26c88304212
Ref: library/stat stat S_ISLNK8304309
Ref: 26c98304309
Ref: library/stat stat S_ISSOCK8304401
Ref: 26ca8304401
Ref: library/stat stat S_ISDOOR8304487
Ref: 18cb8304487
Ref: library/stat stat S_ISPORT8304599
Ref: 18cc8304599
Ref: library/stat stat S_ISWHT8304718
Ref: 18cd8304718
Ref: library/stat stat S_IMODE8304921
Ref: 26cb8304921
Ref: library/stat stat S_IFMT8305181
Ref: 26cc8305181
Ref: library/stat stat filemode8306705
Ref: 10e48306705
Ref: library/stat stat ST_MODE8307108
Ref: f5c8307108
Ref: library/stat stat ST_INO8307163
Ref: 26cd8307163
Ref: library/stat stat ST_DEV8307208
Ref: 26ce8307208
Ref: library/stat stat ST_NLINK8307264
Ref: 26cf8307264
Ref: library/stat stat ST_UID8307327
Ref: 26d08307327
Ref: library/stat stat ST_GID8307380
Ref: 26d18307380
Ref: library/stat stat ST_SIZE8307434
Ref: 26d28307434
Ref: library/stat stat ST_ATIME8307548
Ref: 26d38307548
Ref: library/stat stat ST_MTIME8307602
Ref: 26d48307602
Ref: library/stat stat ST_CTIME8307662
Ref: 26d58307662
Ref: library/stat stat S_IFSOCK8308694
Ref: 26d68308694
Ref: library/stat stat S_IFLNK8308735
Ref: 26d78308735
Ref: library/stat stat S_IFREG8308782
Ref: 26d88308782
Ref: library/stat stat S_IFBLK8308828
Ref: 26d98308828
Ref: library/stat stat S_IFDIR8308874
Ref: 26da8308874
Ref: library/stat stat S_IFCHR8308917
Ref: 26db8308917
Ref: library/stat stat S_IFIFO8308967
Ref: 26dc8308967
Ref: library/stat stat S_IFDOOR8309005
Ref: f5d8309005
Ref: library/stat stat S_IFPORT8309072
Ref: f5e8309072
Ref: library/stat stat S_IFWHT8309145
Ref: f5f8309145
Ref: library/stat stat S_ISUID8309469
Ref: 26dd8309469
Ref: library/stat stat S_ISGID8309514
Ref: 26de8309514
Ref: library/stat stat S_ISVTX8310093
Ref: 26e18310093
Ref: library/stat stat S_IRWXU8310344
Ref: 26e28310344
Ref: library/stat stat S_IRUSR8310409
Ref: 26e38310409
Ref: library/stat stat S_IWUSR8310468
Ref: 26e48310468
Ref: library/stat stat S_IXUSR8310528
Ref: 26e58310528
Ref: library/stat stat S_IRWXG8310590
Ref: 26e68310590
Ref: library/stat stat S_IRGRP8310650
Ref: 26e78310650
Ref: library/stat stat S_IWGRP8310709
Ref: 26e88310709
Ref: library/stat stat S_IXGRP8310769
Ref: 26df8310769
Ref: library/stat stat S_IRWXO8310831
Ref: 26e98310831
Ref: library/stat stat S_IROTH8310911
Ref: 26ea8310911
Ref: library/stat stat S_IWOTH8310972
Ref: 26eb8310972
Ref: library/stat stat S_IXOTH8311034
Ref: 26ec8311034
Ref: library/stat stat S_ENFMT8311098
Ref: 26e08311098
Ref: library/stat stat S_IREAD8311333
Ref: 26ed8311333
Ref: library/stat stat S_IWRITE8311406
Ref: 26ee8311406
Ref: library/stat stat S_IEXEC8311480
Ref: 26ef8311480
Ref: library/stat stat UF_SETTABLE8311640
Ref: 26f08311640
Ref: library/stat stat UF_NODUMP8311730
Ref: 26f18311730
Ref: library/stat stat UF_IMMUTABLE8311786
Ref: 26f28311786
Ref: library/stat stat UF_APPEND8311852
Ref: 26f38311852
Ref: library/stat stat UF_OPAQUE8311920
Ref: 26f48311920
Ref: library/stat stat UF_NOUNLINK8312013
Ref: 26f58312013
Ref: library/stat stat UF_COMPRESSED8312089
Ref: 26f68312089
Ref: library/stat stat UF_TRACKED8312172
Ref: 26f78312172
Ref: library/stat stat UF_DATAVAULT8312275
Ref: 26f88312275
Ref: library/stat stat UF_HIDDEN8312409
Ref: 26f98312409
Ref: library/stat stat SF_SETTABLE8312500
Ref: 26fa8312500
Ref: library/stat stat SF_SUPPORTED8312597
Ref: 26fb8312597
Ref: library/stat stat SF_SYNTHETIC8312733
Ref: 26fc8312733
Ref: library/stat stat SF_ARCHIVED8312879
Ref: 26fd8312879
Ref: library/stat stat SF_IMMUTABLE8312941
Ref: 26fe8312941
Ref: library/stat stat SF_APPEND8313007
Ref: 26ff8313007
Ref: library/stat stat SF_RESTRICTED8313075
Ref: 27008313075
Ref: library/stat stat SF_NOUNLINK8313199
Ref: 27018313199
Ref: library/stat stat SF_SNAPSHOT8313275
Ref: 27028313275
Ref: library/stat stat SF_FIRMLINK8313340
Ref: 27038313340
Ref: library/stat stat SF_DATALESS8313443
Ref: 27048313443
Ref: library/stat stat FILE_ATTRIBUTE_ARCHIVE8313889
Ref: 27058313889
Ref: library/stat stat FILE_ATTRIBUTE_COMPRESSED8313929
Ref: 27068313929
Ref: library/stat stat FILE_ATTRIBUTE_DEVICE8313972
Ref: 27078313972
Ref: library/stat stat FILE_ATTRIBUTE_DIRECTORY8314011
Ref: 27088314011
Ref: library/stat stat FILE_ATTRIBUTE_ENCRYPTED8314053
Ref: 27098314053
Ref: library/stat stat FILE_ATTRIBUTE_HIDDEN8314095
Ref: 270a8314095
Ref: library/stat stat FILE_ATTRIBUTE_INTEGRITY_STREAM8314134
Ref: 270b8314134
Ref: library/stat stat FILE_ATTRIBUTE_NORMAL8314183
Ref: 270c8314183
Ref: library/stat stat FILE_ATTRIBUTE_NOT_CONTENT_INDEXED8314222
Ref: 270d8314222
Ref: library/stat stat FILE_ATTRIBUTE_NO_SCRUB_DATA8314274
Ref: 270e8314274
Ref: library/stat stat FILE_ATTRIBUTE_OFFLINE8314320
Ref: 270f8314320
Ref: library/stat stat FILE_ATTRIBUTE_READONLY8314360
Ref: 27108314360
Ref: library/stat stat FILE_ATTRIBUTE_REPARSE_POINT8314401
Ref: 27118314401
Ref: library/stat stat FILE_ATTRIBUTE_SPARSE_FILE8314447
Ref: 27128314447
Ref: library/stat stat FILE_ATTRIBUTE_SYSTEM8314491
Ref: 27138314491
Ref: library/stat stat FILE_ATTRIBUTE_TEMPORARY8314530
Ref: 27148314530
Ref: library/stat stat FILE_ATTRIBUTE_VIRTUAL8314572
Ref: 27158314572
Ref: library/stat stat IO_REPARSE_TAG_SYMLINK8314846
Ref: 27168314846
Ref: library/stat stat IO_REPARSE_TAG_MOUNT_POINT8314886
Ref: 27178314886
Ref: library/stat stat IO_REPARSE_TAG_APPEXECLINK8314930
Ref: 27188314930
Ref: stat --- 直譯 stat 的結果-Footnote-18315039
Ref: stat --- 直譯 stat 的結果-Footnote-28315103
Ref: stat --- 直譯 stat 的結果-Footnote-38315150
Node: filecmp --- 檔案與目錄比較8315230
Ref: library/filecmp doc8315409
Ref: 27198315409
Ref: library/filecmp filecmp-file-and-directory-comparisons8315409
Ref: 271a8315409
Ref: library/filecmp module-filecmp8315409
Ref: 508315409
Ref: library/filecmp filecmp cmp8315852
Ref: 15548315852
Ref: library/filecmp filecmp cmpfiles8316643
Ref: 14dc8316643
Ref: library/filecmp filecmp clear_cache8317582
Ref: ee28317582
Ref: filecmp --- 檔案與目錄比較-Footnote-18317897
Node: The dircmp class8317964
Ref: library/filecmp dircmp-objects8318050
Ref: 271b8318050
Ref: library/filecmp the-dircmp-class8318050
Ref: 271c8318050
Ref: library/filecmp filecmp dircmp8318111
Ref: ee48318111
Ref: library/filecmp filecmp dircmp report8318771
Ref: 271d8318771
Ref: library/filecmp filecmp dircmp report_partial_closure8318888
Ref: 271e8318888
Ref: library/filecmp filecmp dircmp report_full_closure8319029
Ref: 271f8319029
Ref: library/filecmp filecmp dircmp left8319548
Ref: 27208319548
Ref: library/filecmp filecmp dircmp right8319601
Ref: 27218319601
Ref: library/filecmp filecmp dircmp left_list8319655
Ref: 27228319655
Ref: library/filecmp filecmp dircmp right_list8319770
Ref: 27238319770
Ref: library/filecmp filecmp dircmp common8319886
Ref: 27248319886
Ref: library/filecmp filecmp dircmp left_only8319968
Ref: 27258319968
Ref: library/filecmp filecmp dircmp right_only8320045
Ref: 27268320045
Ref: library/filecmp filecmp dircmp common_dirs8320123
Ref: 27278320123
Ref: library/filecmp filecmp dircmp common_files8320200
Ref: 27288320200
Ref: library/filecmp filecmp dircmp common_funny8320269
Ref: 27298320269
Ref: library/filecmp filecmp dircmp same_files8320469
Ref: 272a8320469
Ref: library/filecmp filecmp dircmp diff_files8320610
Ref: 272b8320610
Ref: library/filecmp filecmp dircmp funny_files8320770
Ref: 272c8320770
Ref: library/filecmp filecmp dircmp subdirs8320885
Ref: 181f8320885
Ref: library/filecmp filecmp DEFAULT_IGNORES8321338
Ref: ee38321338
Node: tempfile --- 生成臨時檔案和目錄8322021
Ref: library/tempfile doc8322217
Ref: 272d8322217
Ref: library/tempfile module-tempfile8322217
Ref: c98322217
Ref: library/tempfile tempfile-generate-temporary-files-and-directories8322217
Ref: 272e8322217
Ref: library/tempfile tempfile TemporaryFile8323332
Ref: 272f8323332
Ref: library/tempfile tempfile NamedTemporaryFile8325403
Ref: 46d8325403
Ref: library/tempfile tempfile SpooledTemporaryFile8328987
Ref: 6398328987
Ref: library/tempfile tempfile SpooledTemporaryFile rollover8329510
Ref: 27338329510
Ref: library/tempfile tempfile TemporaryDirectory8330421
Ref: 11cc8330421
Ref: library/tempfile tempfile TemporaryDirectory name8330882
Ref: 27348330882
Ref: library/tempfile tempfile TemporaryDirectory cleanup8331180
Ref: 27358331180
Ref: library/tempfile tempfile mkstemp8332312
Ref: 27308332312
Ref: library/tempfile tempfile mkdtemp8335240
Ref: 2048335240
Ref: library/tempfile tempfile gettempdir8336409
Ref: 17dc8336409
Ref: library/tempfile tempfile gettempdirb8337471
Ref: 17dd8337471
Ref: library/tempfile tempfile gettempprefix8337618
Ref: 27378337618
Ref: library/tempfile tempfile gettempprefixb8337739
Ref: 27388337739
Ref: library/tempfile tempfile tempdir8338300
Ref: 17db8338300
Ref: tempfile --- 生成臨時檔案和目錄-Footnote-18339356
Node: 範例<7>8339424
Ref: library/tempfile examples8339546
Ref: 27398339546
Ref: library/tempfile tempfile-examples8339546
Ref: 27318339546
Node: 已棄用的函式和變數8340928
Ref: library/tempfile deprecated-functions-and-variables8341050
Ref: 273a8341050
Ref: library/tempfile tempfile-mktemp-deprecated8341050
Ref: 273b8341050
Ref: library/tempfile tempfile mktemp8341565
Ref: 17908341565
Node: glob --- Unix 風格的路徑名稱模式擴展8342624
Ref: library/glob doc8342828
Ref: 273c8342828
Ref: library/glob glob-unix-style-pathname-pattern-expansion8342828
Ref: 273d8342828
Ref: library/glob module-glob8342828
Ref: 5a8342828
Ref: library/glob glob glob8343927
Ref: 2808343927
Ref: library/glob glob iglob8346092
Ref: 7ab8346092
Ref: library/glob glob escape8346972
Ref: ee98346972
Ref: library/glob glob translate8347424
Ref: 1cf8347424
Ref: glob --- Unix 風格的路徑名稱模式擴展-Footnote-18348968
Node: Examples8349032
Ref: library/glob examples8349124
Ref: 273e8349124
Node: fnmatch --- Unix 檔案名稱模式比對8350214
Ref: library/fnmatch doc8350413
Ref: 273f8350413
Ref: library/fnmatch fnmatch-unix-filename-pattern-matching8350413
Ref: 27408350413
Ref: library/fnmatch module-fnmatch8350413
Ref: 528350413
Ref: library/fnmatch fnmatch fnmatch8351957
Ref: 17a28351957
Ref: library/fnmatch fnmatch fnmatchcase8352630
Ref: 17a38352630
Ref: library/fnmatch fnmatch filter8352886
Ref: 17a48352886
Ref: library/fnmatch fnmatch translate8353141
Ref: 194c8353141
Ref: fnmatch --- Unix 檔案名稱模式比對-Footnote-18353720
Node: linecache --- 隨機存取文字列8353787
Ref: library/linecache doc8353968
Ref: 27418353968
Ref: library/linecache linecache-random-access-to-text-lines8353968
Ref: 27428353968
Ref: library/linecache module-linecache8353968
Ref: 798353968
Ref: library/linecache linecache getline8354777
Ref: dc98354777
Ref: library/linecache linecache clearcache8355543
Ref: 27458355543
Ref: library/linecache linecache checkcache8355710
Ref: 27468355710
Ref: library/linecache linecache lazycache8355986
Ref: dc88355986
Ref: linecache --- 隨機存取文字列-Footnote-18356534
Ref: linecache --- 隨機存取文字列-Footnote-28356603
Node: shutil — 高階檔案操作8356645
Ref: library/shutil doc8356776
Ref: 27478356776
Ref: library/shutil module-shutil8356776
Ref: b38356776
Ref: library/shutil shutil-high-level-file-operations8356776
Ref: 27488356776
Ref: shutil — 高階檔案操作-Footnote-18357855
Node: Directory and files operations8357921
Ref: library/shutil directory-and-files-operations8358046
Ref: 27498358046
Ref: library/shutil file-operations8358046
Ref: 274a8358046
Ref: library/shutil shutil copyfileobj8358129
Ref: a008358129
Ref: library/shutil shutil copyfile8358724
Ref: 9fc8358724
Ref: library/shutil shutil SameFileError8360334
Ref: f408360334
Ref: library/shutil shutil copymode8360503
Ref: 15a38360503
Ref: library/shutil shutil copystat8361412
Ref: 10c78361412
Ref: library/shutil shutil copy8363530
Ref: 9fd8363530
Ref: library/shutil shutil copy28365035
Ref: 9fe8365035
Ref: library/shutil shutil ignore_patterns8366555
Ref: 274c8366555
Ref: library/shutil shutil copytree8366853
Ref: 9cd8366853
Ref: library/shutil shutil rmtree8370320
Ref: 2d28370320
Ref: library/shutil shutil rmtree avoids_symlink_attacks8372916
Ref: 274d8372916
Ref: library/shutil shutil move8373255
Ref: 9ff8373255
Ref: library/shutil shutil disk_usage8375290
Ref: 10c68375290
Ref: library/shutil shutil chown8375978
Ref: 2258375978
Ref: library/shutil shutil which8376594
Ref: 45b8376594
Ref: library/shutil shutil Error8379190
Ref: f3f8379190
Node: Platform-dependent efficient copy operations8379522
Ref: library/shutil platform-dependent-efficient-copy-operations8379658
Ref: 274e8379658
Ref: library/shutil shutil-platform-dependent-efficient-copy-operations8379658
Ref: a018379658
Ref: Platform-dependent efficient copy operations-Footnote-18380768
Ref: Platform-dependent efficient copy operations-Footnote-28380833
Node: copytree example8380881
Ref: library/shutil copytree-example8381039
Ref: 274f8381039
Ref: library/shutil shutil-copytree-example8381039
Ref: 27508381039
Node: rmtree 範例8381701
Ref: library/shutil rmtree-example8381806
Ref: 27518381806
Ref: library/shutil shutil-rmtree-example8381806
Ref: 27528381806
Node: Archiving operations8382345
Ref: library/shutil archiving-operations8382519
Ref: 11b08382519
Ref: library/shutil id18382519
Ref: 27538382519
Ref: library/shutil shutil make_archive8382822
Ref: 45a8382822
Ref: library/shutil shutil get_archive_formats8385241
Ref: 27568385241
Ref: library/shutil shutil register_archive_format8386074
Ref: 27558386074
Ref: library/shutil shutil unregister_archive_format8387371
Ref: 27578387371
Ref: library/shutil shutil unpack_archive8387504
Ref: 4128387504
Ref: library/shutil shutil register_unpack_format8389258
Ref: 27588389258
Ref: library/shutil shutil unregister_unpack_format8390175
Ref: 275a8390175
Ref: library/shutil shutil get_unpack_formats8390297
Ref: 27598390297
Ref: Archiving operations-Footnote-18391241
Node: Archiving example8391283
Ref: library/shutil archiving-example8391397
Ref: 275b8391397
Ref: library/shutil shutil-archiving-example8391397
Ref: 275c8391397
Node: Archiving example with base_dir8392488
Ref: library/shutil archiving-example-with-base-dir8392602
Ref: 275d8392602
Ref: library/shutil shutil-archiving-example-with-basedir8392602
Ref: 27548392602
Node: Querying the size of the output terminal8393706
Ref: library/shutil querying-the-size-of-the-output-terminal8393841
Ref: 275e8393841
Ref: library/shutil shutil get_terminal_size8393944
Ref: 109b8393944
Ref: Querying the size of the output terminal-Footnote-18395567
Node: 資料持久性 Data Persistence8395650
Ref: library/persistence doc8395818
Ref: 27618395818
Ref: library/persistence data-persistence8395818
Ref: 27628395818
Ref: library/persistence persistence8395818
Ref: 27638395818
Node: pickle --- Python 物件序列化8396798
Ref: library/pickle doc8396947
Ref: 27648396947
Ref: library/pickle module-pickle8396947
Ref: 958396947
Ref: library/pickle pickle-python-object-serialization8396947
Ref: 27658396947
Ref: pickle --- Python 物件序列化-Footnote-18398723
Ref: pickle --- Python 物件序列化-Footnote-28398789
Node: 和其他 Python 模組的關係8398851
Ref: library/pickle relationship-to-other-python-modules8398980
Ref: 27678398980
Node: 和 marshal 的比較8399116
Ref: library/pickle comparison-with-marshal8399233
Ref: 27688399233
Node: 和 json 的比較8401447
Ref: library/pickle comparison-with-json8401564
Ref: 27668401564
Ref: library/pickle id28401564
Ref: 27698401564
Ref: 和 json 的比較-Footnote-18402720
Node: Data stream format8402745
Ref: library/pickle data-stream-format8402895
Ref: 276b8402895
Ref: library/pickle pickle-protocols8402895
Ref: c688402895
Ref: Data stream format-Footnote-18405851
Ref: Data stream format-Footnote-28405893
Ref: Data stream format-Footnote-38405935
Node: 模組介面8405977
Ref: library/pickle module-interface8406129
Ref: 276e8406129
Ref: library/pickle pickle HIGHEST_PROTOCOL8406553
Ref: 140e8406553
Ref: library/pickle pickle DEFAULT_PROTOCOL8406828
Ref: 7d28406828
Ref: library/pickle pickle dump8407322
Ref: 276f8407322
Ref: library/pickle pickle dumps8407810
Ref: 140d8407810
Ref: library/pickle pickle load8408236
Ref: cb78408236
Ref: library/pickle pickle loads8408973
Ref: cb88408973
Ref: library/pickle pickle PickleError8409689
Ref: 27708409689
Ref: library/pickle pickle PicklingError8409825
Ref: 27718409825
Ref: library/pickle pickle UnpicklingError8410106
Ref: 27738410106
Ref: library/pickle pickle Pickler8410617
Ref: 9c28410617
Ref: library/pickle pickle Pickler dump8412194
Ref: 194b8412194
Ref: library/pickle pickle Pickler persistent_id8412336
Ref: 159d8412336
Ref: library/pickle pickle Pickler dispatch_table8413143
Ref: 10ba8413143
Ref: library/pickle pickle Pickler reducer_override8414311
Ref: 9c38414311
Ref: library/pickle pickle Pickler fast8414940
Ref: 27798414940
Ref: library/pickle pickle Unpickler8415422
Ref: 159f8415422
Ref: library/pickle pickle Unpickler load8417524
Ref: 277b8417524
Ref: library/pickle pickle Unpickler persistent_load8417819
Ref: 159e8417819
Ref: library/pickle pickle Unpickler find_class8418399
Ref: 277c8418399
Ref: library/pickle pickle PickleBuffer8419083
Ref: 16fd8419083
Ref: library/pickle pickle PickleBuffer raw8419703
Ref: 277e8419703
Ref: library/pickle pickle PickleBuffer release8420046
Ref: 277f8420046
Node: What can be pickled and unpickled?8420162
Ref: library/pickle pickle-picklable8420320
Ref: 27728420320
Ref: library/pickle what-can-be-pickled-and-unpickled8420320
Ref: 27808420320
Ref: What can be pickled and unpickled?-Footnote-18423060
Ref: What can be pickled and unpickled?-Footnote-28423193
Node: Pickling Class Instances8423329
Ref: library/pickle pickle-inst8423529
Ref: 276a8423529
Ref: library/pickle pickling-class-instances8423529
Ref: 27818423529
Ref: library/pickle object __getnewargs_ex__8424464
Ref: 27828424464
Ref: library/pickle object __getnewargs__8425295
Ref: 14108425295
Ref: library/pickle object __getstate__8425861
Ref: 57c8425861
Ref: library/pickle object __setstate__8427201
Ref: 140f8427201
Ref: library/pickle object __reduce__8429067
Ref: 9778429067
Ref: library/pickle object __reduce_ex__8431917
Ref: 15ef8431917
Ref: Pickling Class Instances-Footnote-18432578
Node: Persistence of External Objects8432673
Ref: library/pickle persistence-of-external-objects8432789
Ref: 27848432789
Ref: library/pickle pickle-persistent8432789
Ref: 27758432789
Ref: Persistence of External Objects-Footnote-18437457
Node: Dispatch Tables8437721
Ref: library/pickle dispatch-tables8437871
Ref: 27858437871
Ref: library/pickle pickle-dispatch8437871
Ref: 27778437871
Node: Handling Stateful Objects8439163
Ref: library/pickle handling-stateful-objects8439273
Ref: 27868439273
Ref: library/pickle pickle-state8439273
Ref: 27838439273
Node: Custom Reduction for Types Functions and Other Objects8441553
Ref: library/pickle custom-reduction-for-types-functions-and-other-objects8441738
Ref: 27878441738
Ref: library/pickle reducer-override8441738
Ref: 27788441738
Node: Out-of-band Buffers8443840
Ref: library/pickle out-of-band-buffers8444020
Ref: 27888444020
Ref: library/pickle pickle-oob8444020
Ref: 27748444020
Node: Provider API8444868
Ref: library/pickle provider-api8444957
Ref: 27898444957
Node: Consumer API8445564
Ref: library/pickle consumer-api8445671
Ref: 278a8445671
Node: 範例<8>8446974
Ref: library/pickle example8447060
Ref: 278b8447060
Ref: 範例<8>-Footnote-18449433
Node: Restricting Globals8449475
Ref: library/pickle pickle-restrict8449615
Ref: 277d8449615
Ref: library/pickle restricting-globals8449615
Ref: 278c8449615
Node: Performance<2>8452386
Ref: library/pickle performance8452516
Ref: 278d8452516
Node: 範例<9>8452792
Ref: library/pickle examples8452894
Ref: 278e8452894
Ref: library/pickle pickle-example8452894
Ref: 278f8452894
Node: copyreg --- 註冊 pickle 支援函式8454115
Ref: library/copyreg doc8454309
Ref: 27908454309
Ref: library/copyreg copyreg-register-pickle-support-functions8454309
Ref: 27918454309
Ref: library/copyreg module-copyreg8454309
Ref: 1f8454309
Ref: library/copyreg copyreg constructor8454863
Ref: 27928454863
Ref: library/copyreg copyreg pickle8455080
Ref: 27768455080
Ref: copyreg --- 註冊 pickle 支援函式-Footnote-18455769
Node: 範例<10>8455836
Ref: library/copyreg example8455921
Ref: 27938455921
Node: shelve --- Python object persistence8456440
Ref: library/shelve doc8456642
Ref: 27948456642
Ref: library/shelve module-shelve8456642
Ref: b18456642
Ref: library/shelve shelve-python-object-persistence8456642
Ref: 27958456642
Ref: library/shelve shelve open8457217
Ref: 15fd8457217
Ref: library/shelve shelve-security8459252
Ref: 27998459252
Ref: library/shelve shelve Shelf sync8459750
Ref: 27978459750
Ref: library/shelve shelve Shelf close8460071
Ref: 27988460071
Ref: shelve --- Python object persistence-Footnote-18460451
Ref: shelve --- Python object persistence-Footnote-28460517
Node: Restrictions8460622
Ref: library/shelve restrictions8460726
Ref: 279a8460726
Ref: library/shelve shelve Shelf8461914
Ref: f3d8461914
Ref: library/shelve shelve BsdDbShelf8463309
Ref: 21358463309
Ref: library/shelve shelve DbfilenameShelf8464032
Ref: 21368464032
Ref: Restrictions-Footnote-18464648
Node: 範例<11>8464701
Ref: library/shelve example8464805
Ref: 279b8464805
Ref: library/shelve shelve-example8464805
Ref: 27968464805
Node: marshal --- 内部 Python 物件序列化8466479
Ref: library/marshal doc8466677
Ref: 279c8466677
Ref: library/marshal marshal-internal-python-object-serialization8466677
Ref: 279d8466677
Ref: library/marshal module-marshal8466677
Ref: 808466677
Ref: library/marshal marshal dump8469284
Ref: 279e8469284
Ref: library/marshal marshal load8470123
Ref: 19198470123
Ref: library/marshal marshal dumps8471115
Ref: e478471115
Ref: library/marshal marshal loads8471801
Ref: 279f8471801
Ref: library/marshal marshal version8472545
Ref: 27a08472545
Ref: marshal --- 内部 Python 物件序列化-Footnote-18472892
Node: dbm --- Unix "databases" 的介面8473227
Ref: library/dbm doc8473438
Ref: 27a18473438
Ref: library/dbm dbm-interfaces-to-unix-databases8473438
Ref: 27a28473438
Ref: library/dbm module-dbm8473438
Ref: 298473438
Ref: library/dbm dbm error8474241
Ref: 27a38474241
Ref: library/dbm dbm whichdb8474509
Ref: 27a48474509
Ref: library/dbm dbm open8475186
Ref: ece8475186
Ref: dbm --- Unix "databases" 的介面-Footnote-18478762
Ref: dbm --- Unix "databases" 的介面-Footnote-28478834
Node: dbm sqlite3 --- SQLite backend for dbm8478887
Ref: library/dbm dbm-sqlite3-sqlite-backend-for-dbm8479039
Ref: 27a58479039
Ref: library/dbm module-dbm sqlite38479039
Ref: 2d8479039
Ref: library/dbm dbm sqlite3 open8479538
Ref: 27a68479538
Ref: dbm sqlite3 --- SQLite backend for dbm-Footnote-18480538
Node: dbm gnu --- GNU 資料庫管理器8480609
Ref: library/dbm dbm-gnu-gnu-database-manager8480804
Ref: 27a78480804
Ref: library/dbm module-dbm gnu8480804
Ref: 2b8480804
Ref: library/dbm dbm gnu error8481321
Ref: a3d8481321
Ref: library/dbm dbm gnu open8481522
Ref: 19458481522
Ref: library/dbm dbm gnu open_flags8483078
Ref: 27a88483078
Ref: library/dbm dbm gnu gdbm firstkey8483394
Ref: 27a98483394
Ref: library/dbm dbm gnu gdbm nextkey8483726
Ref: 27aa8483726
Ref: library/dbm dbm gnu gdbm reorganize8484111
Ref: 27ab8484111
Ref: library/dbm dbm gnu gdbm sync8484548
Ref: 27ac8484548
Ref: library/dbm dbm gnu gdbm close8484713
Ref: 27ad8484713
Ref: library/dbm dbm gnu gdbm clear8484781
Ref: 1b88484781
Ref: dbm gnu --- GNU 資料庫管理器-Footnote-18484935
Node: dbm ndbm --- 新資料庫管理器8485002
Ref: library/dbm dbm-ndbm-new-database-manager8485192
Ref: 27ae8485192
Ref: library/dbm module-dbm ndbm8485192
Ref: 2c8485192
Ref: library/dbm dbm ndbm error8486018
Ref: a3e8486018
Ref: library/dbm dbm ndbm library8486221
Ref: 27af8486221
Ref: library/dbm dbm ndbm open8486303
Ref: 19468486303
Ref: library/dbm dbm ndbm ndbm close8487457
Ref: 27b08487457
Ref: library/dbm dbm ndbm ndbm clear8487525
Ref: 1b98487525
Ref: dbm ndbm --- 新資料庫管理器-Footnote-18487679
Node: dbm dumb --- 可攜式 DBM 實作8487747
Ref: library/dbm dbm-dumb-portable-dbm-implementation8487894
Ref: 27b18487894
Ref: library/dbm module-dbm dumb8487894
Ref: 2a8487894
Ref: library/dbm dbm dumb error8488652
Ref: a3c8488652
Ref: library/dbm dbm dumb open8488855
Ref: a398488855
Ref: library/dbm dbm dumb dumbdbm sync8490652
Ref: 27b28490652
Ref: library/dbm dbm dumb dumbdbm close8490815
Ref: 27b38490815
Ref: dbm dumb --- 可攜式 DBM 實作-Footnote-18490916
Node: sqlite3 --- SQLite 資料庫的 DB-API 2 0 介面8490984
Ref: library/sqlite3 doc8491145
Ref: 27b48491145
Ref: library/sqlite3 module-sqlite38491145
Ref: ba8491145
Ref: library/sqlite3 sqlite3-db-api-2-0-interface-for-sqlite-databases8491145
Ref: 27b58491145
Ref: library/sqlite3 sqlite3-intro8491291
Ref: 27b68491291
Ref: sqlite3 --- SQLite 資料庫的 DB-API 2 0 介面-Footnote-18492682
Ref: sqlite3 --- SQLite 資料庫的 DB-API 2 0 介面-Footnote-28492747
Ref: sqlite3 --- SQLite 資料庫的 DB-API 2 0 介面-Footnote-38492789
Node: 教學8492831
Ref: library/sqlite3 sqlite3-tutorial8492941
Ref: 27b78492941
Ref: library/sqlite3 tutorial8492941
Ref: 27bb8492941
Ref: 教學-Footnote-18498875
Ref: 教學-Footnote-28498932
Ref: 教學-Footnote-38498991
Ref: 教學-Footnote-48499040
Ref: 教學-Footnote-58499086
Node: Reference8499138
Ref: library/sqlite3 reference8499270
Ref: 27c58499270
Ref: library/sqlite3 sqlite3-reference8499270
Ref: 27b88499270
Ref: library/sqlite3 sqlite3-module-contents8499309
Ref: 27c68499309
Node: Module functions8499620
Ref: library/sqlite3 module-functions8499707
Ref: 27c78499707
Ref: library/sqlite3 sqlite3-module-functions8499707
Ref: 27c88499707
Ref: library/sqlite3 sqlite3 connect8499760
Ref: 2888499760
Ref: library/sqlite3 sqlite3 complete_statement8504651
Ref: 27d18504651
Ref: library/sqlite3 sqlite3 enable_callback_tracebacks8505463
Ref: 27d28505463
Ref: library/sqlite3 sqlite3 register_adapter8506127
Ref: 27d38506127
Ref: library/sqlite3 sqlite3 register_converter8506463
Ref: 27ca8506463
Ref: Module functions-Footnote-18507110
Ref: Module functions-Footnote-28507153
Ref: Module functions-Footnote-38507195
Node: Module constants8507272
Ref: library/sqlite3 module-constants8507385
Ref: 27d58507385
Ref: library/sqlite3 sqlite3-module-constants8507385
Ref: 27d68507385
Ref: library/sqlite3 sqlite3 LEGACY_TRANSACTION_CONTROL8507438
Ref: 27cf8507438
Ref: library/sqlite3 sqlite3 PARSE_COLNAMES8507714
Ref: 27cc8507714
Ref: library/sqlite3 sqlite3 PARSE_DECLTYPES8508232
Ref: 27cb8508232
Ref: library/sqlite3 sqlite3 SQLITE_OK8509041
Ref: 27d78509041
Ref: library/sqlite3 sqlite3 SQLITE_DENY8509071
Ref: 27d88509071
Ref: library/sqlite3 sqlite3 SQLITE_IGNORE8509103
Ref: 27d98509103
Ref: library/sqlite3 sqlite3 apilevel8509539
Ref: 27da8509539
Ref: library/sqlite3 sqlite3 paramstyle8509684
Ref: 27db8509684
Ref: library/sqlite3 sqlite3 sqlite_version8509965
Ref: 27dc8509965
Ref: library/sqlite3 sqlite3 sqlite_version_info8510081
Ref: 27dd8510081
Ref: library/sqlite3 sqlite3 threadsafety8510225
Ref: 6228510225
Ref: library/sqlite3 sqlite3 version8512486
Ref: 2b18512486
Ref: library/sqlite3 sqlite3 version_info8512914
Ref: 2b28512914
Ref: library/sqlite3 sqlite3-dbconfig-constants8513370
Ref: 27de8513370
Ref: library/sqlite3 sqlite3 SQLITE_DBCONFIG_DEFENSIVE8513370
Ref: 27df8513370
Ref: library/sqlite3 sqlite3 SQLITE_DBCONFIG_DQS_DDL8513416
Ref: 27e08513416
Ref: library/sqlite3 sqlite3 SQLITE_DBCONFIG_DQS_DML8513460
Ref: 27e18513460
Ref: library/sqlite3 sqlite3 SQLITE_DBCONFIG_ENABLE_FKEY8513504
Ref: 27e28513504
Ref: library/sqlite3 sqlite3 SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER8513552
Ref: 27e38513552
Ref: library/sqlite3 sqlite3 SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION8513610
Ref: 27e48513610
Ref: library/sqlite3 sqlite3 SQLITE_DBCONFIG_ENABLE_QPSG8513668
Ref: 27e58513668
Ref: library/sqlite3 sqlite3 SQLITE_DBCONFIG_ENABLE_TRIGGER8513716
Ref: 27e68513716
Ref: library/sqlite3 sqlite3 SQLITE_DBCONFIG_ENABLE_VIEW8513767
Ref: 27e78513767
Ref: library/sqlite3 sqlite3 SQLITE_DBCONFIG_LEGACY_ALTER_TABLE8513815
Ref: 27e88513815
Ref: library/sqlite3 sqlite3 SQLITE_DBCONFIG_LEGACY_FILE_FORMAT8513870
Ref: 27e98513870
Ref: library/sqlite3 sqlite3 SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE8513925
Ref: 27ea8513925
Ref: library/sqlite3 sqlite3 SQLITE_DBCONFIG_RESET_DATABASE8513978
Ref: 27eb8513978
Ref: library/sqlite3 sqlite3 SQLITE_DBCONFIG_TRIGGER_EQP8514029
Ref: 27ec8514029
Ref: library/sqlite3 sqlite3 SQLITE_DBCONFIG_TRUSTED_SCHEMA8514077
Ref: 27ed8514077
Ref: library/sqlite3 sqlite3 SQLITE_DBCONFIG_WRITABLE_SCHEMA8514128
Ref: 27ee8514128
Ref: Module constants-Footnote-18514638
Ref: Module constants-Footnote-28514681
Ref: Module constants-Footnote-38514736
Node: Connection 物件8514787
Ref: library/sqlite3 connection-objects8514897
Ref: 27ef8514897
Ref: library/sqlite3 sqlite3-connection-objects8514897
Ref: 27f08514897
Ref: library/sqlite3 sqlite3 Connection8514950
Ref: 22a8514950
Ref: library/sqlite3 sqlite3 Connection cursor8515627
Ref: 27bc8515627
Ref: library/sqlite3 sqlite3 Connection blobopen8515939
Ref: 6278515939
Ref: library/sqlite3 sqlite3 Connection commit8517200
Ref: 27c08517200
Ref: library/sqlite3 sqlite3 Connection rollback8517559
Ref: 27f28517559
Ref: library/sqlite3 sqlite3 Connection close8517925
Ref: 22b8517925
Ref: library/sqlite3 sqlite3 Connection execute8518344
Ref: 27f38518344
Ref: library/sqlite3 sqlite3 Connection executemany8518571
Ref: 27f48518571
Ref: library/sqlite3 sqlite3 Connection executescript8518804
Ref: 27f58518804
Ref: library/sqlite3 sqlite3 Connection create_function8519026
Ref: 2898519026
Ref: library/sqlite3 sqlite3 Connection create_aggregate8520689
Ref: 28a8520689
Ref: library/sqlite3 sqlite3 Connection create_window_function8522616
Ref: 6268522616
Ref: library/sqlite3 sqlite3 Connection create_collation8525809
Ref: 61c8525809
Ref: library/sqlite3 sqlite3 Connection interrupt8527229
Ref: 27f98527229
Ref: library/sqlite3 sqlite3 Connection set_authorizer8527457
Ref: 28b8527457
Ref: library/sqlite3 sqlite3 Connection set_progress_handler8529085
Ref: 28c8529085
Ref: library/sqlite3 sqlite3 Connection set_trace_callback8529933
Ref: 28d8529933
Ref: library/sqlite3 sqlite3 Connection enable_load_extension8531234
Ref: 7e28531234
Ref: library/sqlite3 sqlite3 Connection load_extension8533566
Ref: 45f8533566
Ref: library/sqlite3 sqlite3 Connection iterdump8534518
Ref: 22c8534518
Ref: library/sqlite3 sqlite3 Connection backup8535530
Ref: b1e8535530
Ref: library/sqlite3 sqlite3 Connection getlimit8537887
Ref: 6218537887
Ref: library/sqlite3 sqlite3 Connection setlimit8538516
Ref: 6208538516
Ref: library/sqlite3 sqlite3 Connection getconfig8539605
Ref: 4608539605
Ref: library/sqlite3 sqlite3 Connection setconfig8539873
Ref: 4618539873
Ref: library/sqlite3 sqlite3 Connection serialize8540316
Ref: 6248540316
Ref: library/sqlite3 sqlite3 Connection deserialize8541063
Ref: 6258541063
Ref: library/sqlite3 sqlite3 Connection autocommit8542218
Ref: 45d8542218
Ref: library/sqlite3 sqlite3 Connection in_transaction8543644
Ref: 27fc8543644
Ref: library/sqlite3 sqlite3 Connection isolation_level8543927
Ref: 27cd8543927
Ref: library/sqlite3 sqlite3 Connection row_factory8544865
Ref: 15228544865
Ref: library/sqlite3 sqlite3 Connection text_factory8545348
Ref: 27fe8545348
Ref: library/sqlite3 sqlite3 Connection total_changes8545751
Ref: 27ff8545751
Ref: Connection 物件-Footnote-18545979
Ref: Connection 物件-Footnote-28546025
Ref: Connection 物件-Footnote-38546090
Ref: Connection 物件-Footnote-48546149
Ref: Connection 物件-Footnote-58546208
Ref: Connection 物件-Footnote-68546250
Ref: Connection 物件-Footnote-78546292
Ref: Connection 物件-Footnote-88546384
Ref: Connection 物件-Footnote-98546426
Ref: Connection 物件-Footnote-108546518
Node: Cursor 物件8546619
Ref: library/sqlite3 cursor-objects8546723
Ref: 28008546723
Ref: library/sqlite3 sqlite3-cursor-objects8546723
Ref: 28018546723
Ref: library/sqlite3 sqlite3 Cursor8547329
Ref: 27bd8547329
Ref: library/sqlite3 sqlite3 Cursor execute8547441
Ref: 2b38547441
Ref: library/sqlite3 sqlite3 Cursor executemany8548932
Ref: 2b48548932
Ref: library/sqlite3 sqlite3 Cursor executescript8550432
Ref: 27f68550432
Ref: library/sqlite3 sqlite3 Cursor fetchone8551283
Ref: 27be8551283
Ref: library/sqlite3 sqlite3 Cursor fetchmany8551563
Ref: 28028551563
Ref: library/sqlite3 sqlite3 Cursor fetchall8552402
Ref: 27c18552402
Ref: library/sqlite3 sqlite3 Cursor close8552683
Ref: 28048552683
Ref: library/sqlite3 sqlite3 Cursor setinputsizes8552987
Ref: 28058552987
Ref: library/sqlite3 sqlite3 Cursor setoutputsize8553096
Ref: 28068553096
Ref: library/sqlite3 sqlite3 Cursor arraysize8553217
Ref: 28038553217
Ref: library/sqlite3 sqlite3 Cursor connection8553443
Ref: 28078553443
Ref: library/sqlite3 sqlite3 Cursor description8553942
Ref: 28088553942
Ref: library/sqlite3 sqlite3 Cursor lastrowid8554315
Ref: c788554315
Ref: library/sqlite3 sqlite3 Cursor rowcount8554991
Ref: 16db8554991
Ref: library/sqlite3 sqlite3 Cursor row_factory8555546
Ref: 27fd8555546
Ref: library/sqlite3 sqlite3-columns-by-name8556318
Ref: 28098556318
Ref: Cursor 物件-Footnote-18556354
Ref: Cursor 物件-Footnote-28556411
Node: Row 物件8556462
Ref: library/sqlite3 row-objects8556560
Ref: 280a8556560
Ref: library/sqlite3 sqlite3-row-objects8556560
Ref: 280b8556560
Ref: library/sqlite3 sqlite3 Row8556599
Ref: e138556599
Ref: library/sqlite3 sqlite3 Row keys8557046
Ref: 280c8557046
Node: Blob 物件8557324
Ref: library/sqlite3 blob-objects8557431
Ref: 280d8557431
Ref: library/sqlite3 sqlite3-blob-objects8557431
Ref: 280e8557431
Ref: library/sqlite3 sqlite3 Blob8557472
Ref: 6288557472
Ref: library/sqlite3 sqlite3 Blob close8558643
Ref: 280f8558643
Ref: library/sqlite3 sqlite3 Blob read8558893
Ref: 28108558893
Ref: library/sqlite3 sqlite3 Blob write8559249
Ref: 28118559249
Ref: library/sqlite3 sqlite3 Blob tell8559478
Ref: 28128559478
Ref: library/sqlite3 sqlite3 Blob seek8559563
Ref: 28138559563
Node: PrepareProtocol 物件8559987
Ref: library/sqlite3 prepareprotocol-objects8560093
Ref: 28148560093
Ref: library/sqlite3 sqlite3 PrepareProtocol8560156
Ref: 16e78560156
Ref: PrepareProtocol 物件-Footnote-18560424
Node: 例外<4>8560466
Ref: library/sqlite3 exceptions8560584
Ref: 28168560584
Ref: library/sqlite3 sqlite3-exceptions8560584
Ref: 28178560584
Ref: library/sqlite3 sqlite3 Warning8560686
Ref: 172a8560686
Ref: library/sqlite3 sqlite3 Error8560984
Ref: 17838560984
Ref: library/sqlite3 sqlite3 Error sqlite_errorcode8561337
Ref: 61e8561337
Ref: library/sqlite3 sqlite3 Error sqlite_errorname8561463
Ref: 61f8561463
Ref: library/sqlite3 sqlite3 InterfaceError8561620
Ref: 6238561620
Ref: library/sqlite3 sqlite3 DatabaseError8561896
Ref: 27fa8561896
Ref: library/sqlite3 sqlite3 DataError8562208
Ref: 179f8562208
Ref: library/sqlite3 sqlite3 OperationalError8562454
Ref: 17a08562454
Ref: library/sqlite3 sqlite3 IntegrityError8562803
Ref: 28188562803
Ref: library/sqlite3 sqlite3 InternalError8563012
Ref: 28198563012
Ref: library/sqlite3 sqlite3 ProgrammingError8563285
Ref: 49a8563285
Ref: library/sqlite3 sqlite3 NotSupportedError8563590
Ref: 27f88563590
Ref: 例外<4>-Footnote-18564020
Ref: 例外<4>-Footnote-28564062
Ref: 例外<4>-Footnote-38564102
Node: SQLite and Python types8564142
Ref: library/sqlite3 sqlite-and-python-types8564280
Ref: 281a8564280
Ref: library/sqlite3 sqlite3-types8564280
Ref: 27c98564280
Node: Default adapters and converters deprecated8566192
Ref: library/sqlite3 default-adapters-and-converters-deprecated8566336
Ref: 281b8566336
Ref: library/sqlite3 sqlite3-default-converters8566336
Ref: 4978566336
Ref: Default adapters and converters deprecated-Footnote-18567553
Node: 命令列介面8567600
Ref: library/sqlite3 command-line-interface8567712
Ref: 281c8567712
Ref: library/sqlite3 sqlite3-cli8567712
Ref: 3e78567712
Ref: library/sqlite3 cmdoption-python-m-sqlite3-h-v-filename-sql-h8568041
Ref: 281d8568041
Ref: library/sqlite3 cmdoption-python-m-sqlite3-h-v-filename-sql-help8568041
Ref: 281e8568041
Ref: library/sqlite3 cmdoption-python-m-sqlite3-h-v-filename-sql-v8568087
Ref: 281f8568087
Ref: library/sqlite3 cmdoption-python-m-sqlite3-h-v-filename-sql-version8568087
Ref: 28208568087
Node: How-to guides8568185
Ref: library/sqlite3 how-to-guides8568317
Ref: 28218568317
Ref: library/sqlite3 sqlite3-howtos8568317
Ref: 27b98568317
Node: How to use placeholders to bind values in SQL queries8568783
Ref: library/sqlite3 how-to-use-placeholders-to-bind-values-in-sql-queries8568944
Ref: 28228568944
Ref: library/sqlite3 sqlite3-placeholders8568944
Ref: 2b58568944
Ref: How to use placeholders to bind values in SQL queries-Footnote-18571191
Ref: How to use placeholders to bind values in SQL queries-Footnote-28571243
Node: How to adapt custom Python types to SQLite values8571285
Ref: library/sqlite3 how-to-adapt-custom-python-types-to-sqlite-values8571506
Ref: 28238571506
Ref: library/sqlite3 sqlite3-adapters8571506
Ref: 27c28571506
Node: How to write adaptable objects8572295
Ref: library/sqlite3 how-to-write-adaptable-objects8572453
Ref: 28248572453
Ref: library/sqlite3 sqlite3-conform8572453
Ref: 28158572453
Node: How to register adapter callables8573364
Ref: library/sqlite3 how-to-register-adapter-callables8573522
Ref: 28258573522
Node: How to convert SQLite values to custom Python types8574166
Ref: library/sqlite3 how-to-convert-sqlite-values-to-custom-python-types8574363
Ref: 28268574363
Ref: library/sqlite3 sqlite3-converters8574363
Ref: 27c38574363
Node: Adapter and converter recipes8576932
Ref: library/sqlite3 adapter-and-converter-recipes8577118
Ref: 28278577118
Ref: library/sqlite3 sqlite3-adapter-converter-recipes8577118
Ref: 4988577118
Node: How to use connection shortcut methods8578554
Ref: library/sqlite3 how-to-use-connection-shortcut-methods8578730
Ref: 28288578730
Ref: library/sqlite3 sqlite3-connection-shortcuts8578730
Ref: 27f18578730
Node: How to use the connection context manager8580012
Ref: library/sqlite3 how-to-use-the-connection-context-manager8580187
Ref: 28298580187
Ref: library/sqlite3 sqlite3-connection-context-manager8580187
Ref: 16e88580187
Node: How to work with SQLite URIs8581940
Ref: library/sqlite3 how-to-work-with-sqlite-uris8582112
Ref: 282b8582112
Ref: library/sqlite3 sqlite3-uri-tricks8582112
Ref: 27d08582112
Ref: How to work with SQLite URIs-Footnote-18583394
Node: How to create and use row factories8583434
Ref: library/sqlite3 how-to-create-and-use-row-factories8583603
Ref: 282c8583603
Ref: library/sqlite3 sqlite3-howto-row-factory8583603
Ref: 27c48583603
Node: How to handle non-UTF-8 text encodings8586465
Ref: library/sqlite3 how-to-handle-non-utf-8-text-encodings8586597
Ref: 282d8586597
Ref: library/sqlite3 sqlite3-howto-encoding8586597
Ref: 27fb8586597
Ref: How to handle non-UTF-8 text encodings-Footnote-18587934
Node: 解釋8587983
Ref: library/sqlite3 explanation8588097
Ref: 282e8588097
Ref: library/sqlite3 sqlite3-explanation8588097
Ref: 27ba8588097
Ref: library/sqlite3 sqlite3-transaction-control8588130
Ref: 282f8588130
Node: Transaction control8588164
Ref: library/sqlite3 sqlite3-controlling-transactions8588226
Ref: 27bf8588226
Ref: library/sqlite3 transaction-control8588226
Ref: 28308588226
Node: Transaction control via the autocommit attribute8588719
Ref: library/sqlite3 sqlite3-transaction-control-autocommit8588885
Ref: 45e8588885
Ref: library/sqlite3 transaction-control-via-the-autocommit-attribute8588885
Ref: 28318588885
Ref: Transaction control via the autocommit attribute-Footnote-18590640
Ref: Transaction control via the autocommit attribute-Footnote-28590682
Ref: Transaction control via the autocommit attribute-Footnote-38590774
Node: Transaction control via the isolation_level attribute8590816
Ref: library/sqlite3 sqlite3-transaction-control-isolation-level8590982
Ref: 27ce8590982
Ref: library/sqlite3 transaction-control-via-the-isolation-level-attribute8590982
Ref: 28328590982
Ref: Transaction control via the isolation_level attribute-Footnote-18593061
Ref: Transaction control via the isolation_level attribute-Footnote-28593161
Node: 資料壓縮與保存8593253
Ref: library/archiving doc8593412
Ref: 276c8593412
Ref: library/archiving archiving8593412
Ref: 28338593412
Ref: library/archiving data-compression-and-archiving8593412
Ref: 28348593412
Node: zlib --- 相容於 gzip 的壓縮8594131
Ref: library/zlib doc8594260
Ref: 28358594260
Ref: library/zlib module-zlib8594260
Ref: 1198594260
Ref: library/zlib zlib-compression-compatible-with-gzip8594260
Ref: 28368594260
Ref: library/zlib zlib error8595111
Ref: 28378595111
Ref: library/zlib zlib adler328595196
Ref: 172e8595196
Ref: library/zlib zlib compress8595923
Ref: 5e58595923
Ref: library/zlib compress-wbits8596489
Ref: 28388596489
Ref: library/zlib zlib compressobj8597599
Ref: 28398597599
Ref: library/zlib zlib crc328599315
Ref: 158b8599315
Ref: library/zlib zlib decompress8599916
Ref: cb48599916
Ref: library/zlib decompress-wbits8600320
Ref: 283a8600320
Ref: library/zlib zlib decompressobj8601847
Ref: 283b8601847
Ref: library/zlib zlib Compress compress8602747
Ref: 283c8602747
Ref: library/zlib zlib Compress flush8603068
Ref: 283d8603068
Ref: library/zlib zlib Compress copy8603780
Ref: 283e8603780
Ref: library/zlib zlib Decompress unused_data8604071
Ref: 283f8604071
Ref: library/zlib zlib Decompress unconsumed_tail8604442
Ref: 28408604442
Ref: library/zlib zlib Decompress eof8604843
Ref: 11068604843
Ref: library/zlib zlib Decompress decompress8605069
Ref: 28418605069
Ref: library/zlib zlib Decompress flush8606000
Ref: 28428606000
Ref: library/zlib zlib Decompress copy8606349
Ref: 28438606349
Ref: library/zlib zlib ZLIB_VERSION8606761
Ref: 28448606761
Ref: library/zlib zlib ZLIB_RUNTIME_VERSION8606990
Ref: 11078606990
Ref: zlib --- 相容於 gzip 的壓縮-Footnote-18607407
Node: gzip --- gzip 檔案的支援8607452
Ref: library/gzip doc8607619
Ref: 28458607619
Ref: library/gzip gzip-support-for-gzip-files8607619
Ref: 28468607619
Ref: library/gzip module-gzip8607619
Ref: 5d8607619
Ref: library/gzip gzip open8608600
Ref: 28478608600
Ref: library/gzip gzip BadGzipFile8610115
Ref: 99b8610115
Ref: library/gzip gzip GzipFile8610365
Ref: 3548610365
Ref: library/gzip gzip GzipFile peek8613404
Ref: 11a48613404
Ref: library/gzip gzip GzipFile mode8614033
Ref: 284a8614033
Ref: library/gzip gzip GzipFile mtime8614221
Ref: 28488614221
Ref: library/gzip gzip GzipFile name8614558
Ref: 4b28614558
Ref: library/gzip gzip compress8615763
Ref: 5e48615763
Ref: library/gzip gzip decompress8616692
Ref: 11a58616692
Ref: gzip --- gzip 檔案的支援-Footnote-18617354
Node: 用法範例8617418
Ref: library/gzip examples-of-usage8617523
Ref: 284c8617523
Ref: library/gzip gzip-usage-examples8617523
Ref: 284d8617523
Node: 命令列介面<2>8618420
Ref: library/gzip command-line-interface8618525
Ref: 284e8618525
Ref: library/gzip gzip-cli8618525
Ref: 284f8618525
Node: 命令列選項8618920
Ref: library/gzip command-line-options8618990
Ref: 28508618990
Ref: library/gzip cmdoption-gzip-arg-file8619036
Ref: 28518619036
Ref: library/gzip cmdoption-gzip-fast8619124
Ref: 28528619124
Ref: library/gzip cmdoption-gzip-best8619211
Ref: 28538619211
Ref: library/gzip cmdoption-gzip-d8619298
Ref: 28548619298
Ref: library/gzip cmdoption-gzip-decompress8619298
Ref: 28558619298
Ref: library/gzip cmdoption-gzip-h8619362
Ref: 28568619362
Ref: library/gzip cmdoption-gzip-help8619362
Ref: 28578619362
Node: bz2 --- bzip2 壓縮的支援8619414
Ref: library/bz2 doc8619590
Ref: 28588619590
Ref: library/bz2 bz2-support-for-bzip2-compression8619590
Ref: 28598619590
Ref: library/bz2 module-bz28619590
Ref: f8619590
Ref: bz2 --- bzip2 壓縮的支援-Footnote-18620518
Node: De compression of files8620581
Ref: library/bz2 de-compression-of-files8620705
Ref: 285a8620705
Ref: library/bz2 bz2 open8620774
Ref: 102f8620774
Ref: library/bz2 bz2 BZ2File8622204
Ref: 80b8622204
Ref: library/bz2 bz2 BZ2File peek8623678
Ref: 285c8623678
Ref: library/bz2 bz2 BZ2File fileno8624268
Ref: 285d8624268
Ref: library/bz2 bz2 BZ2File readable8624392
Ref: 285e8624392
Ref: library/bz2 bz2 BZ2File seekable8624514
Ref: 285f8624514
Ref: library/bz2 bz2 BZ2File writable8624630
Ref: 28608624630
Ref: library/bz2 bz2 BZ2File read18624752
Ref: 28618624752
Ref: library/bz2 bz2 BZ2File readinto8625071
Ref: 28628625071
Ref: library/bz2 bz2 BZ2File mode8625224
Ref: 28638625224
Ref: library/bz2 bz2 BZ2File name8625343
Ref: 28648625343
Node: Incremental de compression8626562
Ref: library/bz2 incremental-de-compression8626718
Ref: 28668626718
Ref: library/bz2 bz2 BZ2Compressor8626793
Ref: 165f8626793
Ref: library/bz2 bz2 BZ2Compressor compress8627134
Ref: 28678627134
Ref: library/bz2 bz2 BZ2Compressor flush8627482
Ref: 28688627482
Ref: library/bz2 bz2 BZ2Decompressor8627711
Ref: 165d8627711
Ref: library/bz2 bz2 BZ2Decompressor decompress8628267
Ref: d728628267
Ref: library/bz2 bz2 BZ2Decompressor eof8629628
Ref: 286b8629628
Ref: library/bz2 bz2 BZ2Decompressor unused_data8629751
Ref: 286a8629751
Ref: library/bz2 bz2 BZ2Decompressor needs_input8629970
Ref: 28698629970
Node: One-shot de compression8630191
Ref: library/bz2 one-shot-de-compression8630339
Ref: 286c8630339
Ref: library/bz2 bz2 compress8630408
Ref: 22ef8630408
Ref: library/bz2 bz2 decompress8630705
Ref: 10308630705
Node: 用法範例<2>8631059
Ref: library/bz2 bz2-usage-examples8631172
Ref: 286d8631172
Ref: library/bz2 examples-of-usage8631172
Ref: 286e8631172
Node: lzma --- 使用 LZMA 演算法進行壓縮8634088
Ref: library/lzma doc8634270
Ref: 286f8634270
Ref: library/lzma lzma-compression-using-the-lzma-algorithm8634270
Ref: 28708634270
Ref: library/lzma module-lzma8634270
Ref: 7e8634270
Ref: library/lzma lzma LZMAError8635085
Ref: 28718635085
Ref: lzma --- 使用 LZMA 演算法進行壓縮-Footnote-18635481
Node: Reading and writing compressed files8635545
Ref: library/lzma reading-and-writing-compressed-files8635713
Ref: 28728635713
Ref: library/lzma lzma open8635806
Ref: 28738635806
Ref: library/lzma lzma LZMAFile8637561
Ref: fad8637561
Ref: library/lzma lzma LZMAFile peek8639475
Ref: 28748639475
Ref: library/lzma lzma LZMAFile mode8640095
Ref: 28758640095
Ref: library/lzma lzma LZMAFile name8640214
Ref: 28768640214
Node: Compressing and decompressing data in memory8640651
Ref: library/lzma compressing-and-decompressing-data-in-memory8640841
Ref: 28778640841
Ref: library/lzma lzma LZMACompressor8640950
Ref: 165e8640950
Ref: library/lzma lzma LZMACompressor compress8644029
Ref: 287a8644029
Ref: library/lzma lzma LZMACompressor flush8644502
Ref: 287b8644502
Ref: library/lzma lzma LZMADecompressor8644780
Ref: 165c8644780
Ref: library/lzma lzma LZMADecompressor decompress8646311
Ref: dd48646311
Ref: library/lzma lzma LZMADecompressor check8647672
Ref: 287f8647672
Ref: library/lzma lzma LZMADecompressor eof8647902
Ref: 28808647902
Ref: library/lzma lzma LZMADecompressor unused_data8647992
Ref: 287e8647992
Ref: library/lzma lzma LZMADecompressor needs_input8648160
Ref: 287d8648160
Ref: library/lzma lzma compress8648381
Ref: 28788648381
Ref: library/lzma lzma decompress8648725
Ref: 287c8648725
Node: Miscellaneous8649230
Ref: library/lzma miscellaneous8649415
Ref: 28818649415
Ref: library/lzma lzma is_check_supported8649462
Ref: 28828649462
Node: Specifying custom filter chains8649822
Ref: library/lzma filter-chain-specs8649973
Ref: 28798649973
Ref: library/lzma specifying-custom-filter-chains8649973
Ref: 28838649973
Node: 範例<12>8652652
Ref: library/lzma examples8652781
Ref: 28848652781
Node: zipfile --- 處理 ZIP 封存檔案8654143
Ref: library/zipfile doc8654340
Ref: 28858654340
Ref: library/zipfile module-zipfile8654340
Ref: 1178654340
Ref: library/zipfile zipfile-work-with-zip-archives8654340
Ref: 28868654340
Ref: library/zipfile zipfile BadZipFile8655196
Ref: 16e38655196
Ref: library/zipfile zipfile BadZipfile8655298
Ref: 28878655298
Ref: library/zipfile zipfile LargeZipFile8655454
Ref: 28888655454
Ref: library/zipfile zipfile ZipInfo8656079
Ref: cb18656079
Ref: library/zipfile zipfile is_zipfile8657018
Ref: 12be8657018
Ref: library/zipfile zipfile ZIP_STORED8657307
Ref: 288d8657307
Ref: library/zipfile zipfile ZIP_DEFLATED8657402
Ref: 288e8657402
Ref: library/zipfile zipfile ZIP_BZIP28657550
Ref: 288f8657550
Ref: library/zipfile zipfile ZIP_LZMA8657716
Ref: 28908657716
Ref: zipfile --- 處理 ZIP 封存檔案-Footnote-18658719
Ref: zipfile --- 處理 ZIP 封存檔案-Footnote-28658784
Ref: zipfile --- 處理 ZIP 封存檔案-Footnote-38658852
Ref: zipfile --- 處理 ZIP 封存檔案-Footnote-48658920
Node: ZipFile 物件8658961
Ref: library/zipfile id18659068
Ref: 28918659068
Ref: library/zipfile zipfile-objects8659068
Ref: 28898659068
Ref: library/zipfile zipfile ZipFile8659115
Ref: 6698659115
Ref: library/zipfile zipfile ZipFile close8664095
Ref: 28928664095
Ref: library/zipfile zipfile ZipFile getinfo8664266
Ref: 288a8664266
Ref: library/zipfile zipfile ZipFile infolist8664525
Ref: 288b8664525
Ref: library/zipfile zipfile ZipFile namelist8664783
Ref: 28938664783
Ref: library/zipfile zipfile ZipFile open8664864
Ref: 3558664864
Ref: library/zipfile zipfile ZipFile extract8667735
Ref: 28978667735
Ref: library/zipfile zipfile ZipFile extractall8669122
Ref: 28988669122
Ref: library/zipfile zipfile ZipFile printdir8670165
Ref: 28998670165
Ref: library/zipfile zipfile ZipFile setpassword8670267
Ref: 289a8670267
Ref: library/zipfile zipfile ZipFile read8670404
Ref: 28968670404
Ref: library/zipfile zipfile ZipFile testzip8671329
Ref: 289b8671329
Ref: library/zipfile zipfile ZipFile write8671695
Ref: cf38671695
Ref: library/zipfile zipfile ZipFile writestr8673501
Ref: 12bf8673501
Ref: library/zipfile zipfile ZipFile mkdir8675081
Ref: 66a8675081
Ref: library/zipfile zipfile ZipFile filename8675604
Ref: 289c8675604
Ref: library/zipfile zipfile ZipFile debug8675662
Ref: 289d8675662
Ref: library/zipfile zipfile ZipFile comment8675879
Ref: 289e8675879
Node: Path Objects8676199
Ref: library/zipfile id28676331
Ref: 289f8676331
Ref: library/zipfile path-objects8676331
Ref: 28a08676331
Ref: library/zipfile zipfile Path8676376
Ref: 66b8676376
Ref: library/zipfile zipfile Path name8676929
Ref: 28a18676929
Ref: library/zipfile zipfile Path open8676984
Ref: 16708676984
Ref: library/zipfile zipfile Path iterdir8677861
Ref: 28a28677861
Ref: library/zipfile zipfile Path is_dir8677945
Ref: 28a38677945
Ref: library/zipfile zipfile Path is_file8678044
Ref: 28a48678044
Ref: library/zipfile zipfile Path is_symlink8678139
Ref: 28a58678139
Ref: library/zipfile zipfile Path exists8678380
Ref: 28a68678380
Ref: library/zipfile zipfile Path suffix8678508
Ref: 66d8678508
Ref: library/zipfile zipfile Path stem8678721
Ref: 66c8678721
Ref: library/zipfile zipfile Path suffixes8678864
Ref: 66e8678864
Ref: library/zipfile zipfile Path read_text8679035
Ref: 16718679035
Ref: library/zipfile zipfile Path read_bytes8679610
Ref: 28a78679610
Ref: library/zipfile zipfile Path joinpath8679680
Ref: 28a88679680
Ref: Path Objects-Footnote-18680328
Node: PyZipFile 物件8680367
Ref: library/zipfile id38680499
Ref: 28a98680499
Ref: library/zipfile pyzipfile-objects8680499
Ref: 28aa8680499
Ref: library/zipfile zipfile PyZipFile8680697
Ref: f9b8680697
Ref: library/zipfile zipfile PyZipFile writepy8681024
Ref: f9a8681024
Node: ZipInfo 物件8683870
Ref: library/zipfile id48684012
Ref: 28ab8684012
Ref: library/zipfile zipinfo-objects8684012
Ref: 288c8684012
Ref: library/zipfile zipfile ZipInfo from_file8684376
Ref: cb08684376
Ref: library/zipfile zipfile ZipInfo is_dir8685451
Ref: cb28685451
Ref: library/zipfile zipfile ZipInfo filename8685651
Ref: 28ac8685651
Ref: library/zipfile zipfile ZipInfo date_time8685720
Ref: 28ad8685720
Ref: library/zipfile zipfile ZipInfo compress_type8686501
Ref: 28ae8686501
Ref: library/zipfile zipfile ZipInfo comment8686586
Ref: 28af8686586
Ref: library/zipfile zipfile ZipInfo extra8686699
Ref: 28b08686699
Ref: library/zipfile zipfile ZipInfo create_system8686900
Ref: 28b18686900
Ref: library/zipfile zipfile ZipInfo create_version8686975
Ref: 28b28686975
Ref: library/zipfile zipfile ZipInfo extract_version8687058
Ref: 28b38687058
Ref: library/zipfile zipfile ZipInfo reserved8687142
Ref: 28b48687142
Ref: library/zipfile zipfile ZipInfo flag_bits8687192
Ref: 28b58687192
Ref: library/zipfile zipfile ZipInfo volume8687244
Ref: 28b68687244
Ref: library/zipfile zipfile ZipInfo internal_attr8687308
Ref: 28b78687308
Ref: library/zipfile zipfile ZipInfo external_attr8687370
Ref: 28b88687370
Ref: library/zipfile zipfile ZipInfo header_offset8687437
Ref: 28b98687437
Ref: library/zipfile zipfile ZipInfo CRC8687510
Ref: 28ba8687510
Ref: library/zipfile zipfile ZipInfo compress_size8687574
Ref: 28bb8687574
Ref: library/zipfile zipfile ZipInfo file_size8687644
Ref: 28958687644
Ref: ZipInfo 物件-Footnote-18687748
Node: Command-Line Interface8687816
Ref: library/zipfile command-line-interface8687964
Ref: 28bc8687964
Ref: library/zipfile zipfile-commandline8687964
Ref: 28bd8687964
Node: Command-line options8688737
Ref: library/zipfile command-line-options8688816
Ref: 28c18688816
Ref: library/zipfile cmdoption-zipfile-l8688877
Ref: 28c08688877
Ref: library/zipfile cmdoption-zipfile-list8688902
Ref: 28c28688902
Ref: library/zipfile cmdoption-zipfile-c8688963
Ref: 28be8688963
Ref: library/zipfile cmdoption-zipfile-create8689012
Ref: 28c38689012
Ref: library/zipfile cmdoption-zipfile-e8689108
Ref: 28bf8689108
Ref: library/zipfile cmdoption-zipfile-extract8689146
Ref: 28c48689146
Ref: library/zipfile cmdoption-zipfile-t8689237
Ref: 28c58689237
Ref: library/zipfile cmdoption-zipfile-test8689262
Ref: 28c68689262
Ref: library/zipfile cmdoption-zipfile-metadata-encoding8689340
Ref: 28c78689340
Node: Decompression pitfalls8689513
Ref: library/zipfile decompression-pitfalls8689638
Ref: 28c88689638
Node: From file itself8689921
Ref: library/zipfile from-file-itself8690028
Ref: 28c98690028
Node: File System limitations8690207
Ref: library/zipfile file-system-limitations8690344
Ref: 28ca8690344
Node: Resources limitations8690646
Ref: library/zipfile resources-limitations8690779
Ref: 28cb8690779
Ref: library/zipfile zipfile-resources-limitations8690779
Ref: 28cc8690779
Ref: Resources limitations-Footnote-18691066
Node: Interruption8691113
Ref: library/zipfile interruption8691254
Ref: 28cd8691254
Node: Default behaviors of extraction8691460
Ref: library/zipfile default-behaviors-of-extraction8691571
Ref: 28ce8691571
Node: tarfile --- 讀取與寫入 tar 封存檔案8691836
Ref: library/tarfile doc8691982
Ref: 28cf8691982
Ref: library/tarfile module-tarfile8691982
Ref: c88691982
Ref: library/tarfile tarfile-read-and-write-tar-archive-files8691982
Ref: 28d08691982
Ref: library/tarfile tarfile open8693560
Ref: e198693560
Ref: library/tarfile tarfile is_tarfile8700145
Ref: 17498700145
Ref: library/tarfile tarfile TarError8700495
Ref: 28d58700495
Ref: library/tarfile tarfile ReadError8700581
Ref: 179d8700581
Ref: library/tarfile tarfile CompressionError8700749
Ref: 28d28700749
Ref: library/tarfile tarfile StreamError8700896
Ref: 28d68700896
Ref: library/tarfile tarfile ExtractError8701032
Ref: 28d78701032
Ref: library/tarfile tarfile HeaderError8701211
Ref: 28d98701211
Ref: library/tarfile tarfile FilterError8701333
Ref: 28db8701333
Ref: library/tarfile tarfile FilterError tarinfo8701428
Ref: 28dd8701428
Ref: library/tarfile tarfile AbsolutePathError8701564
Ref: 28df8701564
Ref: library/tarfile tarfile OutsideDestinationError8701669
Ref: 28e08701669
Ref: library/tarfile tarfile SpecialFileError8701797
Ref: 28e18701797
Ref: library/tarfile tarfile AbsoluteLinkError8701915
Ref: 28e28701915
Ref: library/tarfile tarfile LinkOutsideDestinationError8702027
Ref: 28e38702027
Ref: library/tarfile tarfile ENCODING8702235
Ref: 28e48702235
Ref: library/tarfile tarfile REGTYPE8702407
Ref: 28e58702407
Ref: library/tarfile tarfile AREGTYPE8702435
Ref: 28e68702435
Ref: library/tarfile tarfile LNKTYPE8702504
Ref: 28e88702504
Ref: library/tarfile tarfile SYMTYPE8702581
Ref: 28e98702581
Ref: library/tarfile tarfile CHRTYPE8702650
Ref: 28ea8702650
Ref: library/tarfile tarfile BLKTYPE8702730
Ref: 28eb8702730
Ref: library/tarfile tarfile DIRTYPE8702806
Ref: 28ec8702806
Ref: library/tarfile tarfile FIFOTYPE8702871
Ref: 28ed8702871
Ref: library/tarfile tarfile CONTTYPE8702947
Ref: 28ee8702947
Ref: library/tarfile tarfile GNUTYPE_LONGNAME8703019
Ref: 28ef8703019
Ref: library/tarfile tarfile GNUTYPE_LONGLINK8703100
Ref: 28f08703100
Ref: library/tarfile tarfile GNUTYPE_SPARSE8703181
Ref: 28f18703181
Ref: library/tarfile tarfile USTAR_FORMAT8703440
Ref: 28f38703440
Ref: library/tarfile tarfile GNU_FORMAT8703509
Ref: 28f48703509
Ref: library/tarfile tarfile PAX_FORMAT8703563
Ref: 28f58703563
Ref: library/tarfile tarfile DEFAULT_FORMAT8703628
Ref: 28f68703628
Ref: tarfile --- 讀取與寫入 tar 封存檔案-Footnote-18704496
Ref: tarfile --- 讀取與寫入 tar 封存檔案-Footnote-28704563
Node: TarFile 物件8704635
Ref: library/tarfile id18704753
Ref: 28f78704753
Ref: library/tarfile tarfile-objects8704753
Ref: 28d18704753
Ref: library/tarfile tarfile TarFile8705617
Ref: 2908705617
Ref: library/tarfile tarfile TarFile open8708943
Ref: 174a8708943
Ref: library/tarfile tarfile TarFile getmember8709108
Ref: 17578709108
Ref: library/tarfile tarfile TarFile getmembers8709434
Ref: e1d8709434
Ref: library/tarfile tarfile TarFile getnames8709622
Ref: 28f98709622
Ref: library/tarfile tarfile TarFile list8709783
Ref: e1c8709783
Ref: library/tarfile tarfile TarFile next8710227
Ref: 28fa8710227
Ref: library/tarfile tarfile TarFile extractall8710448
Ref: e1a8710448
Ref: library/tarfile tarfile TarFile extract8712242
Ref: e1b8712242
Ref: library/tarfile tarfile TarFile extractfile8713570
Ref: 28fb8713570
Ref: library/tarfile tarfile TarFile errorlevel8714221
Ref: 28d88714221
Ref: library/tarfile tarfile TarFile extraction_filter8715149
Ref: 28fc8715149
Ref: library/tarfile tarfile TarFile add8716456
Ref: b9a8716456
Ref: library/tarfile tarfile TarFile addfile8717355
Ref: 15248717355
Ref: library/tarfile tarfile TarFile gettarinfo8717873
Ref: 28fe8717873
Ref: library/tarfile tarfile TarFile close8719015
Ref: 29018719015
Ref: library/tarfile tarfile TarFile pax_headers8719157
Ref: 29028719157
Node: TarInfo 物件8719277
Ref: library/tarfile id28719422
Ref: 29038719422
Ref: library/tarfile tarinfo-objects8719422
Ref: 28de8719422
Ref: library/tarfile tarfile TarInfo8720621
Ref: 11a88720621
Ref: library/tarfile tarfile TarInfo frombuf8720704
Ref: 28da8720704
Ref: library/tarfile tarfile TarInfo fromtarfile8720918
Ref: 29058720918
Ref: library/tarfile tarfile TarInfo tobuf8721099
Ref: 29068721099
Ref: library/tarfile tarfile TarInfo name8721537
Ref: 29008721537
Ref: library/tarfile tarfile TarInfo size8721614
Ref: 28ff8721614
Ref: library/tarfile tarfile TarInfo mtime8721678
Ref: 29078721678
Ref: library/tarfile tarfile TarInfo mode8722033
Ref: 290a8722033
Ref: library/tarfile tarfile TarInfo type8722300
Ref: 28e78722300
Ref: library/tarfile tarfile TarInfo linkname8722741
Ref: 290b8722741
Ref: library/tarfile tarfile TarInfo uid8723150
Ref: 290c8723150
Ref: library/tarfile tarfile TarInfo gid8723424
Ref: 290d8723424
Ref: library/tarfile tarfile TarInfo uname8723699
Ref: 290e8723699
Ref: library/tarfile tarfile TarInfo gname8723931
Ref: 290f8723931
Ref: library/tarfile tarfile TarInfo chksum8724164
Ref: 29108724164
Ref: library/tarfile tarfile TarInfo devmajor8724232
Ref: 29118724232
Ref: library/tarfile tarfile TarInfo devminor8724306
Ref: 29128724306
Ref: library/tarfile tarfile TarInfo offset8724380
Ref: 29138724380
Ref: library/tarfile tarfile TarInfo offset_data8724459
Ref: 29148724459
Ref: library/tarfile tarfile TarInfo sparse8724544
Ref: 29158724544
Ref: library/tarfile tarfile TarInfo pax_headers8724605
Ref: 29168724605
Ref: library/tarfile tarfile TarInfo replace8724745
Ref: 29048724745
Ref: library/tarfile tarfile TarInfo isfile8725424
Ref: 29178725424
Ref: library/tarfile tarfile TarInfo isreg8725544
Ref: 29188725544
Ref: library/tarfile tarfile TarInfo isdir8725610
Ref: 29198725610
Ref: library/tarfile tarfile TarInfo issym8725692
Ref: 291a8725692
Ref: library/tarfile tarfile TarInfo islnk8725778
Ref: 291b8725778
Ref: library/tarfile tarfile TarInfo ischr8725860
Ref: 291c8725860
Ref: library/tarfile tarfile TarInfo isblk8725949
Ref: 291d8725949
Ref: library/tarfile tarfile TarInfo isfifo8726034
Ref: 291e8726034
Ref: library/tarfile tarfile TarInfo isdev8726112
Ref: 291f8726112
Node: Extraction filters8726233
Ref: library/tarfile extraction-filters8726389
Ref: 29208726389
Ref: library/tarfile tarfile-extraction-filter8726389
Ref: 4138726389
Ref: Extraction filters-Footnote-18729478
Node: Default named filters8729520
Ref: library/tarfile default-named-filters8729618
Ref: 29228729618
Ref: library/tarfile tarfile fully_trusted_filter8729782
Ref: 28fd8729782
Ref: library/tarfile tarfile tar_filter8729928
Ref: 29218729928
Ref: library/tarfile tarfile data_filter8730733
Ref: 15f98730733
Node: Filter errors8732065
Ref: library/tarfile filter-errors8732202
Ref: 29238732202
Ref: library/tarfile tarfile-extraction-refuse8732202
Ref: 28dc8732202
Node: Hints for further verification8732563
Ref: library/tarfile hints-for-further-verification8732711
Ref: 29248732711
Node: Supporting older Python versions8734372
Ref: library/tarfile supporting-older-python-versions8734541
Ref: 29258734541
Node: Stateful extraction filter example8736094
Ref: library/tarfile stateful-extraction-filter-example8736224
Ref: 29268736224
Node: Command-Line Interface<2>8737016
Ref: library/tarfile command-line-interface8737168
Ref: 29278737168
Ref: library/tarfile tarfile-commandline8737168
Ref: f6e8737168
Node: 命令列選項<2>8738111
Ref: library/tarfile command-line-options8738191
Ref: 292b8738191
Ref: library/tarfile cmdoption-tarfile-l8738239
Ref: 292a8738239
Ref: library/tarfile cmdoption-tarfile-list8738264
Ref: 292c8738264
Ref: library/tarfile cmdoption-tarfile-c8738325
Ref: 29288738325
Ref: library/tarfile cmdoption-tarfile-create8738374
Ref: 292d8738374
Ref: library/tarfile cmdoption-tarfile-e8738470
Ref: 29298738470
Ref: library/tarfile cmdoption-tarfile-extract8738510
Ref: 292e8738510
Ref: library/tarfile cmdoption-tarfile-t8738646
Ref: 292f8738646
Ref: library/tarfile cmdoption-tarfile-test8738671
Ref: 29308738671
Ref: library/tarfile cmdoption-tarfile-v8738749
Ref: 29318738749
Ref: library/tarfile cmdoption-tarfile-verbose8738749
Ref: 29328738749
Ref: library/tarfile cmdoption-tarfile-filter8738798
Ref: 29338738798
Node: 範例<13>8739033
Ref: library/tarfile examples8739188
Ref: 29348739188
Ref: library/tarfile tar-examples8739188
Ref: 28d48739188
Node: Supported tar formats8741070
Ref: library/tarfile supported-tar-formats8741214
Ref: 29358741214
Ref: library/tarfile tar-formats8741214
Ref: 28f28741214
Node: Unicode issues8743436
Ref: library/tarfile tar-unicode8743561
Ref: 28f88743561
Ref: library/tarfile unicode-issues8743561
Ref: 29368743561
Node: 檔案格式8745535
Ref: library/fileformats doc8745674
Ref: 29388745674
Ref: library/fileformats file-formats8745674
Ref: 29398745674
Ref: library/fileformats fileformats8745674
Ref: 293a8745674
Node: csv --- CSV 檔案讀取及寫入8746214
Ref: library/csv doc8746340
Ref: 293b8746340
Ref: library/csv csv-csv-file-reading-and-writing8746340
Ref: 293c8746340
Ref: library/csv module-csv8746340
Ref: 218746340
Ref: csv --- CSV 檔案讀取及寫入-Footnote-18748171
Ref: csv --- CSV 檔案讀取及寫入-Footnote-28748234
Ref: csv --- CSV 檔案讀取及寫入-Footnote-38748293
Node: 模組內容<3>8748335
Ref: library/csv csv-contents8748452
Ref: 293d8748452
Ref: library/csv module-contents8748452
Ref: 293e8748452
Ref: library/csv csv reader8748540
Ref: 42d8748540
Ref: library/csv csv writer8750195
Ref: 42e8750195
Ref: library/csv csv register_dialect8751920
Ref: 29418751920
Ref: library/csv csv unregister_dialect8752395
Ref: 170d8752395
Ref: library/csv csv get_dialect8752621
Ref: 170c8752621
Ref: library/csv csv list_dialects8752890
Ref: 170e8752890
Ref: library/csv csv field_size_limit8752973
Ref: 170b8752973
Ref: library/csv csv DictReader8753218
Ref: 9898753218
Ref: library/csv csv DictWriter8755038
Ref: 11968755038
Ref: library/csv csv Dialect8756790
Ref: 15718756790
Ref: library/csv csv excel8757617
Ref: 29438757617
Ref: library/csv csv excel_tab8757789
Ref: 29448757789
Ref: library/csv csv unix_dialect8757996
Ref: 11958757996
Ref: library/csv csv Sniffer8758313
Ref: 29458758313
Ref: library/csv csv Sniffer sniff8758471
Ref: 29468758471
Ref: library/csv csv Sniffer has_header8758777
Ref: 17a58758777
Ref: library/csv csv-constants8759858
Ref: 29478759858
Ref: library/csv csv QUOTE_ALL8759905
Ref: 29488759905
Ref: library/csv csv QUOTE_MINIMAL8759992
Ref: 29498759992
Ref: library/csv csv QUOTE_NONNUMERIC8760184
Ref: 14df8760184
Ref: library/csv csv QUOTE_NONE8760373
Ref: 294a8760373
Ref: library/csv csv QUOTE_NOTNULL8760786
Ref: 42b8760786
Ref: library/csv csv QUOTE_STRINGS8761236
Ref: 42c8761236
Ref: library/csv csv Error8761731
Ref: 29428761731
Ref: 模組內容<3>-Footnote-18761851
Ref: 模組內容<3>-Footnote-28762164
Node: Dialect 與格式參數8762477
Ref: library/csv csv-fmt-params8762618
Ref: 29408762618
Ref: library/csv dialects-and-formatting-parameters8762618
Ref: 294b8762618
Ref: library/csv csv Dialect delimiter8763292
Ref: 294c8763292
Ref: library/csv csv Dialect doublequote8763423
Ref: 294d8763423
Ref: library/csv csv Dialect escapechar8763938
Ref: 294e8763938
Ref: library/csv csv Dialect lineterminator8764387
Ref: 294f8764387
Ref: library/csv csv Dialect quotechar8764710
Ref: 29508764710
Ref: library/csv csv Dialect quoting8764971
Ref: 29518764971
Ref: library/csv csv Dialect skipinitialspace8765173
Ref: 29528765173
Ref: library/csv csv Dialect strict8765332
Ref: 29538765332
Node: 讀取器物件8765476
Ref: library/csv id38765617
Ref: 29548765617
Ref: library/csv reader-objects8765617
Ref: 293f8765617
Ref: library/csv csv csvreader __next__8765802
Ref: 29558765802
Ref: library/csv csv csvreader dialect8766206
Ref: 29568766206
Ref: library/csv csv csvreader line_num8766294
Ref: 29578766294
Ref: library/csv csv DictReader fieldnames8766484
Ref: 29588766484
Node: 寫入器物件8766686
Ref: library/csv writer-objects8766814
Ref: 29598766814
Ref: library/csv csv csvwriter writerow8767467
Ref: d908767467
Ref: library/csv csv csvwriter writerows8767784
Ref: 295a8767784
Ref: library/csv csv csvwriter dialect8768037
Ref: 295b8768037
Ref: library/csv csv DictWriter writeheader8768168
Ref: 11978768168
Node: 範例<14>8768619
Ref: library/csv csv-examples8768723
Ref: 295c8768723
Ref: library/csv examples8768723
Ref: 295d8768723
Node: configparser --- 設定檔剖析器8770683
Ref: library/configparser doc8770848
Ref: 295e8770848
Ref: library/configparser configparser-configuration-file-parser8770848
Ref: 295f8770848
Ref: library/configparser module-configparser8770848
Ref: 1b8770848
Ref: configparser --- 設定檔剖析器-Footnote-18772327
Node: Quick Start8772399
Ref: library/configparser quick-start8772510
Ref: 29608772510
Ref: Quick Start-Footnote-18776248
Ref: Quick Start-Footnote-28776450
Node: Supported Datatypes8776652
Ref: library/configparser supported-datatypes8776787
Ref: 29648776787
Ref: Supported Datatypes-Footnote-18778109
Ref: Supported Datatypes-Footnote-28778311
Node: Fallback Values8778513
Ref: library/configparser fallback-values8778665
Ref: 29688778665
Node: Supported INI File Structure8780179
Ref: library/configparser supported-ini-file-structure8780328
Ref: 29618780328
Ref: Supported INI File Structure-Footnote-18783044
Ref: Supported INI File Structure-Footnote-28783246
Ref: Supported INI File Structure-Footnote-38783448
Ref: Supported INI File Structure-Footnote-48783650
Ref: Supported INI File Structure-Footnote-58783852
Node: Unnamed Sections8784054
Ref: library/configparser id108784211
Ref: 296b8784211
Ref: library/configparser unnamed-sections8784211
Ref: 296c8784211
Node: Interpolation of values8784691
Ref: library/configparser interpolation-of-values8784843
Ref: 296d8784843
Ref: library/configparser configparser BasicInterpolation8785079
Ref: 6c68785079
Ref: library/configparser configparser ExtendedInterpolation8786372
Ref: 6c78786372
Ref: Interpolation of values-Footnote-18787864
Node: Mapping Protocol Access8788066
Ref: library/configparser mapping-protocol-access8788230
Ref: 29628788230
Ref: Mapping Protocol Access-Footnote-18791116
Node: Customizing Parser Behaviour8791318
Ref: library/configparser customizing-parser-behaviour8791478
Ref: 29638791478
Ref: library/configparser configparser ConfigParser BOOLEAN_STATES8802234
Ref: 29718802234
Ref: library/configparser configparser ConfigParser SECTCRE8804417
Ref: 29698804417
Node: Legacy API Examples8805654
Ref: library/configparser legacy-api-examples8805810
Ref: 29728805810
Node: ConfigParser 物件8809628
Ref: library/configparser configparser-objects8809778
Ref: 29738809778
Ref: library/configparser id138809778
Ref: 29748809778
Ref: library/configparser configparser ConfigParser8809837
Ref: 1aa8809837
Ref: library/configparser configparser ConfigParser defaults8814949
Ref: 29778814949
Ref: library/configparser configparser ConfigParser sections8815049
Ref: 29788815049
Ref: library/configparser configparser ConfigParser add_section8815192
Ref: 12068815192
Ref: library/configparser configparser ConfigParser has_section8815680
Ref: 29798815680
Ref: library/configparser configparser ConfigParser options8815856
Ref: 297a8815856
Ref: library/configparser configparser ConfigParser has_option8815966
Ref: 297b8815966
Ref: library/configparser configparser ConfigParser read8816266
Ref: 13d38816266
Ref: library/configparser configparser ConfigParser read_file8818000
Ref: 4ac8818000
Ref: library/configparser configparser ConfigParser read_string8818477
Ref: 29708818477
Ref: library/configparser configparser ConfigParser read_dict8818826
Ref: 296e8818826
Ref: library/configparser configparser ConfigParser get8819523
Ref: 12048819523
Ref: library/configparser configparser ConfigParser getint8820477
Ref: 29668820477
Ref: library/configparser configparser ConfigParser getfloat8820766
Ref: 29678820766
Ref: library/configparser configparser ConfigParser getboolean8821070
Ref: 29658821070
Ref: library/configparser configparser ConfigParser items8821801
Ref: 297c8821801
Ref: library/configparser configparser ConfigParser set8822438
Ref: 12058822438
Ref: library/configparser configparser ConfigParser write8822723
Ref: 296f8822723
Ref: library/configparser configparser ConfigParser remove_option8823422
Ref: 297e8823422
Ref: library/configparser configparser ConfigParser remove_section8823736
Ref: 297f8823736
Ref: library/configparser configparser ConfigParser optionxform8823948
Ref: 29758823948
Ref: library/configparser configparser UNNAMED_SECTION8824919
Ref: 296a8824919
Ref: library/configparser configparser MAX_INTERPOLATION_DEPTH8825092
Ref: 29808825092
Node: RawConfigParser 物件8825327
Ref: library/configparser id158825467
Ref: 29818825467
Ref: library/configparser rawconfigparser-objects8825467
Ref: 29828825467
Ref: library/configparser configparser RawConfigParser8825532
Ref: f078825532
Ref: library/configparser configparser RawConfigParser add_section8826513
Ref: 29838826513
Ref: library/configparser configparser RawConfigParser set8826988
Ref: 29848826988
Node: 例外<5>8827815
Ref: library/configparser exceptions8827927
Ref: 29858827927
Ref: library/configparser configparser Error8827960
Ref: 29868827960
Ref: library/configparser configparser NoSectionError8828059
Ref: 297d8828059
Ref: library/configparser configparser DuplicateSectionError8828162
Ref: 12078828162
Ref: library/configparser configparser DuplicateOptionError8828566
Ref: 12088828566
Ref: library/configparser configparser NoOptionError8828923
Ref: 29878828923
Ref: library/configparser configparser InterpolationError8829054
Ref: 29888829054
Ref: library/configparser configparser InterpolationDepthError8829196
Ref: 29898829196
Ref: library/configparser configparser InterpolationMissingOptionError8829453
Ref: 298a8829453
Ref: library/configparser configparser InterpolationSyntaxError8829639
Ref: 298b8829639
Ref: library/configparser configparser MissingSectionHeaderError8829864
Ref: 298c8829864
Ref: library/configparser configparser ParsingError8830006
Ref: 4ab8830006
Ref: library/configparser configparser MultilineContinuationError8830303
Ref: 29768830303
Node: tomllib --- 剖析 TOML 檔案8830503
Ref: library/tomllib doc8830663
Ref: 298d8830663
Ref: library/tomllib module-tomllib8830663
Ref: e58830663
Ref: library/tomllib tomllib-parse-toml-files8830663
Ref: 298e8830663
Ref: library/tomllib tomllib load8831435
Ref: 298f8831435
Ref: library/tomllib tomllib loads8832176
Ref: 29928832176
Ref: library/tomllib tomllib TOMLDecodeError8832567
Ref: 29918832567
Ref: tomllib --- 剖析 TOML 檔案-Footnote-18832731
Ref: tomllib --- 剖析 TOML 檔案-Footnote-28832795
Ref: tomllib --- 剖析 TOML 檔案-Footnote-38832823
Ref: tomllib --- 剖析 TOML 檔案-Footnote-48832865
Node: 範例<15>8832907
Ref: library/tomllib examples8833002
Ref: 29938833002
Node: 轉換表8833348
Ref: library/tomllib conversion-table8833443
Ref: 29948833443
Ref: library/tomllib toml-to-py-table8833479
Ref: 29908833479
Node: netrc --- netrc 檔案處理8834763
Ref: library/netrc doc8834935
Ref: 29958834935
Ref: library/netrc module-netrc8834935
Ref: 8d8834935
Ref: library/netrc netrc-netrc-file-processing8834935
Ref: 29968834935
Ref: library/netrc netrc netrc8835263
Ref: 17c48835263
Ref: library/netrc netrc NetrcParseError8836757
Ref: 29978836757
Ref: library/netrc netrc NetrcParseError msg8836941
Ref: 29988836941
Ref: library/netrc netrc NetrcParseError filename8836999
Ref: 29998836999
Ref: library/netrc netrc NetrcParseError lineno8837062
Ref: 299a8837062
Ref: netrc --- netrc 檔案處理-Footnote-18837186
Node: netrc 物件8837251
Ref: library/netrc id18837328
Ref: 299b8837328
Ref: library/netrc netrc-objects8837328
Ref: 299c8837328
Ref: library/netrc netrc netrc authenticators8837419
Ref: 299d8837419
Ref: library/netrc netrc netrc __repr__8837734
Ref: 299e8837734
Ref: library/netrc netrc netrc hosts8837964
Ref: 299f8837964
Ref: library/netrc netrc netrc macros8838165
Ref: 29a08838165
Node: plistlib --- 產生和剖析 Apple plist 檔案8838263
Ref: library/plistlib doc8838396
Ref: 29a18838396
Ref: library/plistlib module-plistlib8838396
Ref: 998838396
Ref: library/plistlib plistlib-generate-and-parse-apple-plist-files8838396
Ref: 29a28838396
Ref: library/plistlib plistlib load8839809
Ref: 8f38839809
Ref: library/plistlib plistlib loads8841064
Ref: 8f48841064
Ref: library/plistlib plistlib dump8841407
Ref: 8f58841407
Ref: library/plistlib plistlib dumps8842805
Ref: 8f68842805
Ref: library/plistlib plistlib UID8843161
Ref: 9c58843161
Ref: library/plistlib plistlib FMT_XML8843568
Ref: f1c8843568
Ref: library/plistlib plistlib FMT_BINARY8843664
Ref: f1d8843664
Ref: plistlib --- 產生和剖析 Apple plist 檔案-Footnote-18843833
Ref: plistlib --- 產生和剖析 Apple plist 檔案-Footnote-28843901
Node: 範例<16>8844000
Ref: library/plistlib examples8844094
Ref: 29a38844094
Node: 加密服務8844943
Ref: library/crypto doc8845085
Ref: 29a48845085
Ref: library/crypto crypto8845085
Ref: 29a58845085
Ref: library/crypto cryptographic-services8845085
Ref: 29a68845085
Node: hashlib --- 安全雜湊與訊息摘要8845573
Ref: library/hashlib doc8845712
Ref: 29a78845712
Ref: library/hashlib hashlib-secure-hashes-and-message-digests8845712
Ref: 29a88845712
Ref: library/hashlib module-hashlib8845712
Ref: 5e8845712
Ref: hashlib --- 安全雜湊與訊息摘要-Footnote-18846730
Ref: hashlib --- 安全雜湊與訊息摘要-Footnote-28846797
Ref: hashlib --- 安全雜湊與訊息摘要-Footnote-38846864
Ref: hashlib --- 安全雜湊與訊息摘要-Footnote-48846929
Node: 雜湊演算法8846988
Ref: library/hashlib hash-algorithms8847094
Ref: 29a98847094
Ref: library/hashlib id18847094
Ref: 29aa8847094
Ref: library/hashlib hashlib-usedforsecurity8849298
Ref: 29b58849298
Ref: 雜湊演算法-Footnote-18850001
Ref: 雜湊演算法-Footnote-28850109
Node: 用法8850156
Ref: library/hashlib usage8850283
Ref: 29b68850283
Node: 建構函式8850926
Ref: library/hashlib constructors8851044
Ref: 29b78851044
Ref: library/hashlib hashlib new8851085
Ref: 18498851085
Ref: library/hashlib hashlib md58851620
Ref: 29b38851620
Ref: library/hashlib hashlib sha18851679
Ref: 29af8851679
Ref: library/hashlib hashlib sha2248851739
Ref: 29b08851739
Ref: library/hashlib hashlib sha2568851801
Ref: 29ab8851801
Ref: library/hashlib hashlib sha3848851863
Ref: 29b18851863
Ref: library/hashlib hashlib sha5128851925
Ref: 29b28851925
Ref: library/hashlib hashlib sha3_2248851987
Ref: c498851987
Ref: library/hashlib hashlib sha3_2568852051
Ref: c4a8852051
Ref: library/hashlib hashlib sha3_3848852115
Ref: c4b8852115
Ref: library/hashlib hashlib sha3_5128852179
Ref: c4c8852179
Node: 屬性8852337
Ref: library/hashlib attributes8852461
Ref: 29b88852461
Ref: library/hashlib hashlib algorithms_guaranteed8852535
Ref: 13008852535
Ref: library/hashlib hashlib algorithms_available8852873
Ref: 13018852873
Node: 雜湊物件8853275
Ref: library/hashlib hash-objects8853411
Ref: 29b98853411
Ref: library/hashlib hashlib hash digest_size8853523
Ref: 29ba8853523
Ref: library/hashlib hashlib hash block_size8853611
Ref: 29bb8853611
Ref: library/hashlib hashlib hash name8853748
Ref: eeb8853748
Ref: library/hashlib hashlib hash update8854124
Ref: 29ac8854124
Ref: library/hashlib hashlib hash digest8854349
Ref: 29ad8854349
Ref: library/hashlib hashlib hash hexdigest8854600
Ref: 29ae8854600
Ref: library/hashlib hashlib hash copy8854856
Ref: 29bc8854856
Node: SHAKE 可變長度摘要8855032
Ref: library/hashlib shake-variable-length-digests8855174
Ref: 29bd8855174
Ref: library/hashlib hashlib shake_1288855237
Ref: c4d8855237
Ref: library/hashlib hashlib shake_2568855302
Ref: c4e8855302
Ref: library/hashlib hashlib shake digest8855615
Ref: 193f8855615
Ref: library/hashlib hashlib shake hexdigest8855854
Ref: 19408855854
Node: 檔案雜湊8856262
Ref: library/hashlib file-hashing8856407
Ref: 29be8856407
Ref: library/hashlib hashlib file_digest8856574
Ref: 5ea8856574
Node: 密鑰的生成8857947
Ref: library/hashlib key-derivation8858074
Ref: 29bf8858074
Ref: library/hashlib hashlib pbkdf2_hmac8858429
Ref: 4b48858429
Ref: library/hashlib hashlib scrypt8860099
Ref: be58860099
Ref: 密鑰的生成-Footnote-18860838
Ref: 密鑰的生成-Footnote-28860918
Ref: 密鑰的生成-Footnote-38861005
Ref: 密鑰的生成-Footnote-48861116
Node: BLAKE28861175
Ref: library/hashlib blake28861281
Ref: 29c08861281
Ref: library/hashlib hashlib-blake28861281
Ref: 1c908861281
Ref: BLAKE2-Footnote-18862026
Ref: BLAKE2-Footnote-28862057
Ref: BLAKE2-Footnote-38862116
Node: 建立雜湊物件8862194
Ref: library/hashlib creating-hash-objects8862273
Ref: 29c18862273
Ref: library/hashlib hashlib blake2b8862385
Ref: 5e88862385
Ref: library/hashlib hashlib blake2s8862619
Ref: 5e98862619
Ref: 建立雜湊物件-Footnote-18865667
Node: 常數<5>8865718
Ref: library/hashlib constants8865816
Ref: 29c28865816
Ref: library/hashlib hashlib blake2b SALT_SIZE8865849
Ref: 29c38865849
Ref: library/hashlib hashlib blake2s SALT_SIZE8865880
Ref: 29c48865880
Ref: library/hashlib hashlib blake2b PERSON_SIZE8865964
Ref: 29c58865964
Ref: library/hashlib hashlib blake2s PERSON_SIZE8865997
Ref: 29c68865997
Ref: library/hashlib hashlib blake2b MAX_KEY_SIZE8866095
Ref: 29c78866095
Ref: library/hashlib hashlib blake2s MAX_KEY_SIZE8866129
Ref: 29c88866129
Ref: library/hashlib hashlib blake2b MAX_DIGEST_SIZE8866186
Ref: 29c98866186
Ref: library/hashlib hashlib blake2s MAX_DIGEST_SIZE8866223
Ref: 29ca8866223
Node: 範例<17>8866310
Ref: library/hashlib examples8866402
Ref: 29cb8866402
Node: 簡單雜湊8866655
Ref: library/hashlib simple-hashing8866750
Ref: 29cc8866750
Node: 使用不同的摘要大小8868190
Ref: library/hashlib using-different-digest-sizes8868320
Ref: 29cd8868320
Node: 密鑰雜湊 Keyed hashing8869453
Ref: library/hashlib keyed-hashing8869602
Ref: 29ce8869602
Ref: 密鑰雜湊 Keyed hashing-Footnote-18871681
Node: 隨機雜湊 Randomized hashing8871725
Ref: library/hashlib randomized-hashing8871856
Ref: 29cf8871856
Ref: 隨機雜湊 Randomized hashing-Footnote-18874227
Ref: 隨機雜湊 Randomized hashing-Footnote-28874308
Node: 個人化8874343
Ref: library/hashlib personalization8874460
Ref: 29d08874460
Ref: 個人化-Footnote-18876369
Node: 樹狀模式8876439
Ref: library/hashlib tree-mode8876516
Ref: 29d18876516
Node: 製作人員8877769
Ref: library/hashlib credits8877843
Ref: 29d28877843
Ref: library/hashlib hashlib-seealso8879202
Ref: 29b48879202
Ref: 製作人員-Footnote-18880215
Ref: 製作人員-Footnote-28880246
Ref: 製作人員-Footnote-38880307
Ref: 製作人員-Footnote-48880385
Ref: 製作人員-Footnote-58880422
Ref: 製作人員-Footnote-68880465
Node: hmac --- 基於金鑰雜湊的訊息驗證8880508
Ref: library/hmac doc8880707
Ref: 29d38880707
Ref: library/hmac hmac-keyed-hashing-for-message-authentication8880707
Ref: 29d48880707
Ref: library/hmac module-hmac8880707
Ref: 608880707
Ref: library/hmac hmac new8880974
Ref: a428880974
Ref: library/hmac hmac digest8881823
Ref: ae28881823
Ref: library/hmac hmac HMAC update8882453
Ref: eed8882453
Ref: library/hmac hmac HMAC digest8882772
Ref: 29d58882772
Ref: library/hmac hmac HMAC hexdigest8883320
Ref: 29d68883320
Ref: library/hmac hmac HMAC copy8883873
Ref: 29d78883873
Ref: library/hmac hmac HMAC digest_size8884083
Ref: ef08884083
Ref: library/hmac hmac HMAC block_size8884166
Ref: eee8884166
Ref: library/hmac hmac HMAC name8884285
Ref: eef8884285
Ref: library/hmac hmac compare_digest8884586
Ref: 10638884586
Ref: hmac --- 基於金鑰雜湊的訊息驗證-Footnote-18885500
Ref: hmac --- 基於金鑰雜湊的訊息驗證-Footnote-28885564
Node: secrets --- 產生用於管理機密的安全亂數8885623
Ref: library/secrets doc8885774
Ref: 29d88885774
Ref: library/secrets module-secrets8885774
Ref: ae8885774
Ref: library/secrets secrets-generate-secure-random-numbers-for-managing-secrets8885774
Ref: 29d98885774
Ref: secrets --- 產生用於管理機密的安全亂數-Footnote-18886641
Ref: secrets --- 產生用於管理機密的安全亂數-Footnote-28886708
Node: 亂數8886750
Ref: library/secrets random-numbers8886876
Ref: 29da8886876
Ref: library/secrets secrets SystemRandom8887010
Ref: 29db8887010
Ref: library/secrets secrets choice8887211
Ref: 29dc8887211
Ref: library/secrets secrets randbelow8887312
Ref: 29dd8887312
Ref: library/secrets secrets randbits8887446
Ref: 29de8887446
Node: 產生權杖（token）8887522
Ref: library/secrets generating-tokens8887669
Ref: 29df8887669
Ref: library/secrets secrets token_bytes8887882
Ref: 25c18887882
Ref: library/secrets secrets token_hex8888190
Ref: 16ae8888190
Ref: library/secrets secrets token_urlsafe8888562
Ref: 29e08888562
Node: 權杖應當使用多少個位元組？8889022
Ref: library/secrets how-many-bytes-should-tokens-use8889121
Ref: 29e18889121
Ref: 權杖應當使用多少個位元組？-Footnote-18890118
Node: 其他函式8890175
Ref: library/secrets other-functions8890363
Ref: 29e28890363
Ref: library/secrets secrets compare_digest8890404
Ref: 29e38890404
Ref: 其他函式-Footnote-18890793
Node: 應用技巧和典範實務（best practices）8890850
Ref: library/secrets recipes-and-best-practices8891006
Ref: 29e48891006
Ref: 應用技巧和典範實務（best practices）-Footnote-18892744
Ref: 應用技巧和典範實務（best practices）-Footnote-28892800
Node: 通用作業系統服務8892830
Ref: library/allos doc8892993
Ref: 29e58892993
Ref: library/allos allos8892993
Ref: 29e68892993
Ref: library/allos generic-operating-system-services8892993
Ref: 29e78892993
Node: os --- 各種作業系統介面8894660
Ref: library/os doc8894801
Ref: 29e88894801
Ref: library/os module-os8894801
Ref: 918894801
Ref: library/os os-miscellaneous-operating-system-interfaces8894801
Ref: 29e98894801
Ref: library/os os error8896953
Ref: 29ec8896953
Ref: library/os os name8897027
Ref: 29ed8897027
Ref: library/os os-filenames8897470
Ref: 29378897470
Ref: os --- 各種作業系統介面-Footnote-18897869
Node: File Names Command Line Arguments and Environment Variables8897931
Ref: library/os file-names-command-line-arguments-and-environment-variables8898086
Ref: 29ee8898086
Ref: library/os filesystem-encoding8898086
Ref: 26988898086
Node: Python UTF-8 模式8899422
Ref: library/os python-utf-8-mode8899598
Ref: 29ef8899598
Ref: library/os utf8-mode8899598
Ref: 5fc8899598
Ref: Python UTF-8 模式-Footnote-18902444
Ref: Python UTF-8 模式-Footnote-28902486
Node: 行程參數8902528
Ref: library/os os-procinfo8902665
Ref: 29f08902665
Ref: library/os process-parameters8902665
Ref: 29f18902665
Ref: library/os os ctermid8902803
Ref: 29f28902803
Ref: library/os os environ8902966
Ref: 11528902966
Ref: library/os os environb8904950
Ref: 11ae8904950
Ref: library/os os fsencode8905713
Ref: bfc8905713
Ref: library/os os fsdecode8906098
Ref: bfb8906098
Ref: library/os os fspath8906487
Ref: bfa8906487
Ref: library/os os PathLike8906898
Ref: bf88906898
Ref: library/os os PathLike __fspath__8907078
Ref: bf98907078
Ref: library/os os getenv8907348
Ref: 29f48907348
Ref: library/os os getenvb8908021
Ref: 11ad8908021
Ref: library/os os get_exec_path8908597
Ref: 29f58908597
Ref: library/os os getegid8908977
Ref: 29f68908977
Ref: library/os os geteuid8909210
Ref: 16ee8909210
Ref: library/os os getgid8909338
Ref: 29f78909338
Ref: library/os os getgrouplist8909556
Ref: 10ac8909556
Ref: library/os os getgroups8909947
Ref: 29f88909947
Ref: library/os os getlogin8911178
Ref: 29fa8911178
Ref: library/os os getpgid8911667
Ref: 29fb8911667
Ref: library/os os getpgrp8911898
Ref: 29fc8911898
Ref: library/os os getpid8912022
Ref: 29eb8912022
Ref: library/os os getppid8912186
Ref: 15468912186
Ref: library/os os getpriority8912564
Ref: 10978912564
Ref: library/os os PRIO_PROCESS8913204
Ref: 29fd8913204
Ref: library/os os PRIO_PGRP8913232
Ref: 29fe8913232
Ref: library/os os PRIO_USER8913257
Ref: 29ff8913257
Ref: library/os os PRIO_DARWIN_THREAD8913457
Ref: 2a008913457
Ref: library/os os PRIO_DARWIN_PROCESS8913491
Ref: 2a018913491
Ref: library/os os PRIO_DARWIN_BG8913526
Ref: 2a028913526
Ref: library/os os PRIO_DARWIN_NONUI8913556
Ref: 2a038913556
Ref: library/os os getresuid8913752
Ref: 12aa8913752
Ref: library/os os getresgid8913969
Ref: 12a98913969
Ref: library/os os getuid8914187
Ref: 29ea8914187
Ref: library/os os initgroups8914399
Ref: 12ad8914399
Ref: library/os os putenv8914698
Ref: 8c18914698
Ref: library/os os setegid8915833
Ref: 2a058915833
Ref: library/os os seteuid8915966
Ref: 2a068915966
Ref: library/os os setgid8916098
Ref: 2a078916098
Ref: library/os os setgroups8916218
Ref: 29f98916218
Ref: library/os os setns8916874
Ref: 16c48916874
Ref: library/os os setpgrp8918394
Ref: 2a098918394
Ref: library/os os setpgid8918636
Ref: 2a0a8918636
Ref: library/os os setpriority8918909
Ref: 10988918909
Ref: library/os os setregid8919694
Ref: 2a0b8919694
Ref: library/os os setresgid8919844
Ref: 12ab8919844
Ref: library/os os setresuid8920037
Ref: 12ac8920037
Ref: library/os os setreuid8920229
Ref: 2a0c8920229
Ref: library/os os getsid8920378
Ref: 2a0d8920378
Ref: library/os os setsid8920545
Ref: 18da8920545
Ref: library/os os setuid8920706
Ref: 2a0e8920706
Ref: library/os os strerror8920826
Ref: 2a0f8920826
Ref: library/os os supports_bytes_environ8921070
Ref: 11ac8921070
Ref: library/os os umask8921239
Ref: 2a108921239
Ref: library/os os uname8921439
Ref: 10ae8921439
Ref: library/os os unsetenv8922734
Ref: 8c08922734
Ref: library/os os unshare8923497
Ref: 16c58923497
Ref: library/os os-unshare-clone-flags8924203
Ref: 2a088924203
Ref: library/os os CLONE_FILES8924373
Ref: 2a128924373
Ref: library/os os CLONE_FS8924400
Ref: 2a138924400
Ref: library/os os CLONE_NEWCGROUP8924424
Ref: 2a148924424
Ref: library/os os CLONE_NEWIPC8924455
Ref: 2a158924455
Ref: library/os os CLONE_NEWNET8924483
Ref: 2a168924483
Ref: library/os os CLONE_NEWNS8924511
Ref: 2a178924511
Ref: library/os os CLONE_NEWPID8924538
Ref: 2a188924538
Ref: library/os os CLONE_NEWTIME8924566
Ref: 2a198924566
Ref: library/os os CLONE_NEWUSER8924595
Ref: 2a1a8924595
Ref: library/os os CLONE_NEWUTS8924624
Ref: 2a1b8924624
Ref: library/os os CLONE_SIGHAND8924652
Ref: 2a1c8924652
Ref: library/os os CLONE_SYSVSEM8924681
Ref: 2a1d8924681
Ref: library/os os CLONE_THREAD8924710
Ref: 2a1e8924710
Ref: library/os os CLONE_VM8924738
Ref: 2a1f8924738
Ref: 行程參數-Footnote-18924799
Ref: 行程參數-Footnote-28924841
Ref: 行程參數-Footnote-38924883
Ref: 行程參數-Footnote-48924928
Ref: 行程參數-Footnote-58924978
Ref: 行程參數-Footnote-68925025
Node: File Object Creation8925072
Ref: library/os file-object-creation8925216
Ref: 2a208925216
Ref: library/os os-newstreams8925216
Ref: 2a218925216
Ref: library/os os fdopen8925392
Ref: 1e088925392
Node: File Descriptor Operations8925717
Ref: library/os file-descriptor-operations8925870
Ref: 2a228925870
Ref: library/os os-fd-ops8925870
Ref: 2a238925870
Ref: library/os os close8926708
Ref: b188926708
Ref: library/os os closerange8927149
Ref: 2a248927149
Ref: library/os os copy_file_range8927496
Ref: 2a258927496
Ref: library/os os device_encoding8929183
Ref: 17948929183
Ref: library/os os dup8929591
Ref: 18e28929591
Ref: library/os os dup28929994
Ref: b078929994
Ref: library/os os fchmod8930487
Ref: 2018930487
Ref: library/os os fchown8931061
Ref: d308931061
Ref: library/os os fdatasync8931626
Ref: d318931626
Ref: library/os os fpathconf8931854
Ref: 2a278931854
Ref: library/os os fstat8932882
Ref: d328932882
Ref: library/os os fstatvfs8933139
Ref: d338933139
Ref: library/os os fsync8933412
Ref: d348933412
Ref: library/os os ftruncate8933892
Ref: d358933892
Ref: library/os os get_blocking8934337
Ref: ddf8934337
Ref: library/os os grantpt8934918
Ref: 15798934918
Ref: library/os os isatty8935298
Ref: 17938935298
Ref: library/os os lockf8935450
Ref: 10ab8935450
Ref: library/os os F_LOCK8935972
Ref: 2a298935972
Ref: library/os os F_TLOCK8935994
Ref: 2a2a8935994
Ref: library/os os F_ULOCK8936017
Ref: 2a2b8936017
Ref: library/os os F_TEST8936040
Ref: 2a2c8936040
Ref: library/os os login_tty8936196
Ref: 165b8936196
Ref: library/os os lseek8936551
Ref: 10af8936551
Ref: library/os os SEEK_SET8937389
Ref: 12258937389
Ref: library/os os SEEK_CUR8937413
Ref: 12268937413
Ref: library/os os SEEK_END8937437
Ref: 12278937437
Ref: library/os os SEEK_HOLE8938018
Ref: 2a2d8938018
Ref: library/os os SEEK_DATA8938043
Ref: 2a2e8938043
Ref: library/os os open8938776
Ref: d388938776
Ref: library/os os O_RDONLY8940841
Ref: 2a2f8940841
Ref: library/os os O_WRONLY8940865
Ref: 2a308940865
Ref: library/os os O_RDWR8940889
Ref: 2a328940889
Ref: library/os os O_APPEND8940911
Ref: 2a338940911
Ref: library/os os O_CREAT8940935
Ref: 2a348940935
Ref: library/os os O_EXCL8940958
Ref: 27368940958
Ref: library/os os O_TRUNC8940980
Ref: 2a358940980
Ref: library/os os O_DSYNC8941065
Ref: 2a368941065
Ref: library/os os O_RSYNC8941088
Ref: 2a378941088
Ref: library/os os O_SYNC8941111
Ref: 2a388941111
Ref: library/os os O_NDELAY8941133
Ref: 2a398941133
Ref: library/os os O_NONBLOCK8941157
Ref: de18941157
Ref: library/os os O_NOCTTY8941183
Ref: 2a3a8941183
Ref: library/os os O_CLOEXEC8941207
Ref: 101d8941207
Ref: library/os os O_BINARY8941352
Ref: 2a318941352
Ref: library/os os O_NOINHERIT8941376
Ref: 2a3b8941376
Ref: library/os os O_SHORT_LIVED8941403
Ref: 2a3c8941403
Ref: library/os os O_TEMPORARY8941432
Ref: 2a3d8941432
Ref: library/os os O_RANDOM8941459
Ref: 2a3e8941459
Ref: library/os os O_SEQUENTIAL8941483
Ref: 2a3f8941483
Ref: library/os os O_TEXT8941511
Ref: 2a408941511
Ref: library/os os O_EVTONLY8941591
Ref: 7be8941591
Ref: library/os os O_FSYNC8941616
Ref: 7bf8941616
Ref: library/os os O_SYMLINK8941639
Ref: 7c08941639
Ref: library/os os O_NOFOLLOW_ANY8941664
Ref: 7c18941664
Ref: library/os os O_ASYNC8941894
Ref: 2a418941894
Ref: library/os os O_DIRECT8941917
Ref: 2a428941917
Ref: library/os os O_DIRECTORY8941941
Ref: 2a438941941
Ref: library/os os O_NOFOLLOW8941968
Ref: 2a448941968
Ref: library/os os O_NOATIME8941994
Ref: 2a458941994
Ref: library/os os O_PATH8942019
Ref: f158942019
Ref: library/os os O_TMPFILE8942041
Ref: f168942041
Ref: library/os os O_SHLOCK8942066
Ref: 139c8942066
Ref: library/os os O_EXLOCK8942090
Ref: 139d8942090
Ref: library/os os openpty8942380
Ref: 2a468942380
Ref: library/os os pipe8942813
Ref: 16df8942813
Ref: library/os os pipe28943142
Ref: 10828943142
Ref: library/os os posix_fallocate8943529
Ref: d3a8943529
Ref: library/os os posix_fadvise8943787
Ref: d398943787
Ref: library/os os POSIX_FADV_NORMAL8944389
Ref: 2a478944389
Ref: library/os os POSIX_FADV_SEQUENTIAL8944422
Ref: 2a488944422
Ref: library/os os POSIX_FADV_RANDOM8944459
Ref: 2a498944459
Ref: library/os os POSIX_FADV_NOREUSE8944492
Ref: 2a4a8944492
Ref: library/os os POSIX_FADV_WILLNEED8944526
Ref: 2a4b8944526
Ref: library/os os POSIX_FADV_DONTNEED8944561
Ref: 2a4c8944561
Ref: library/os os pread8944797
Ref: b038944797
Ref: library/os os posix_openpt8945184
Ref: 15788945184
Ref: library/os os preadv8945777
Ref: b018945777
Ref: library/os os RWF_NOWAIT8946836
Ref: 2a4e8946836
Ref: library/os os RWF_HIPRI8947343
Ref: 2a4d8947343
Ref: library/os os ptsname8947739
Ref: 157b8947739
Ref: library/os os pwrite8948277
Ref: b068948277
Ref: library/os os pwritev8948561
Ref: b048948561
Ref: library/os os RWF_DSYNC8949619
Ref: 2a508949619
Ref: library/os os RWF_SYNC8949901
Ref: 2a518949901
Ref: library/os os RWF_APPEND8950181
Ref: 18488950181
Ref: library/os os read8950741
Ref: d3b8950741
Ref: library/os os sendfile8951674
Ref: ab28951674
Ref: library/os os SF_NODISKIO8953175
Ref: 2a528953175
Ref: library/os os SF_MNOWAIT8953202
Ref: 2a538953202
Ref: library/os os SF_SYNC8953228
Ref: 2a548953228
Ref: library/os os SF_NOCACHE8953426
Ref: 2a558953426
Ref: library/os os set_blocking8953708
Ref: de08953708
Ref: library/os os splice8954315
Ref: 7bd8954315
Ref: library/os os SPLICE_F_MOVE8955730
Ref: 2a568955730
Ref: library/os os SPLICE_F_NONBLOCK8955759
Ref: 2a578955759
Ref: library/os os SPLICE_F_MORE8955792
Ref: 2a588955792
Ref: library/os os readv8955851
Ref: b028955851
Ref: library/os os tcgetpgrp8956467
Ref: 2a598956467
Ref: library/os os tcsetpgrp8956691
Ref: 2a5a8956691
Ref: library/os os ttyname8956929
Ref: 2a5b8956929
Ref: library/os os unlockpt8957178
Ref: 157a8957178
Ref: library/os os write8957550
Ref: d418957550
Ref: library/os os writev8958390
Ref: b058958390
Ref: File Descriptor Operations-Footnote-18959084
Ref: File Descriptor Operations-Footnote-28959126
Ref: File Descriptor Operations-Footnote-38959170
Ref: File Descriptor Operations-Footnote-48959233
Ref: File Descriptor Operations-Footnote-58959275
Node: Querying the size of a terminal8959317
Ref: library/os querying-the-size-of-a-terminal8959451
Ref: 2a5c8959451
Ref: library/os terminal-size8959451
Ref: 2a5d8959451
Ref: library/os os get_terminal_size8959557
Ref: 109a8959557
Ref: library/os os terminal_size8960194
Ref: 27608960194
Ref: library/os os terminal_size columns8960316
Ref: 2a5e8960316
Ref: library/os os terminal_size lines8960397
Ref: 2a5f8960397
Node: Inheritance of File Descriptors8960477
Ref: library/os fd-inheritance8960611
Ref: e9d8960611
Ref: library/os inheritance-of-file-descriptors8960611
Ref: 2a608960611
Ref: library/os os get_inheritable8961639
Ref: e9e8961639
Ref: library/os os set_inheritable8961763
Ref: e9f8961763
Ref: library/os os get_handle_inheritable8961883
Ref: ea08961883
Ref: library/os os set_handle_inheritable8962043
Ref: ea18962043
Node: Files and Directories8962204
Ref: library/os files-and-directories8962349
Ref: 2a618962349
Ref: library/os os-file-dir8962349
Ref: 29f38962349
Ref: library/os path-fd8962498
Ref: b008962498
Ref: library/os dir-fd8963441
Ref: 10838963441
Ref: library/os follow-symlinks8964155
Ref: 10848964155
Ref: library/os os access8964737
Ref: 10858964737
Ref: library/os os F_OK8967290
Ref: 2a628967290
Ref: library/os os R_OK8967310
Ref: 2a638967310
Ref: library/os os W_OK8967330
Ref: 2a648967330
Ref: library/os os X_OK8967350
Ref: 2a658967350
Ref: library/os os chdir8967542
Ref: 5b28967542
Ref: library/os os chflags8968212
Ref: 10868968212
Ref: library/os os chmod8969293
Ref: 2008969293
Ref: library/os os chown8971350
Ref: 10878971350
Ref: library/os os chroot8972349
Ref: 18978972349
Ref: library/os os fchdir8972559
Ref: d2f8972559
Ref: library/os os getcwd8972958
Ref: 19078972958
Ref: library/os os getcwdb8973050
Ref: a348973050
Ref: library/os os lchflags8973354
Ref: 2a678973354
Ref: library/os os lchmod8973843
Ref: 1ff8973843
Ref: library/os os lchown8974676
Ref: 2a688974676
Ref: library/os os link8975188
Ref: 10888975188
Ref: library/os os listdir8975964
Ref: 10928975964
Ref: library/os os listdrives8977437
Ref: 4458977437
Ref: library/os os listmounts8978063
Ref: 4478978063
Ref: library/os os listvolumes8978899
Ref: 4468978899
Ref: library/os os lstat8979612
Ref: 4498979612
Ref: library/os os mkdir8980708
Ref: 2028980708
Ref: library/os mkdir-modebits8981007
Ref: 2a698981007
Ref: library/os os makedirs8982162
Ref: 2038982162
Ref: library/os os mkfifo8983871
Ref: d368983871
Ref: library/os os mknod8984757
Ref: d378984757
Ref: library/os os major8985638
Ref: 150e8985638
Ref: library/os os minor8985807
Ref: 150f8985807
Ref: library/os os makedev8985976
Ref: 15108985976
Ref: library/os os pathconf8986098
Ref: 10938986098
Ref: library/os os pathconf_names8987189
Ref: 2a6b8987189
Ref: library/os os readlink8987512
Ref: 8c58987512
Ref: library/os os remove8988969
Ref: 10898988969
Ref: library/os os removedirs8989898
Ref: 2a6c8989898
Ref: library/os os rename8990742
Ref: 108a8990742
Ref: library/os os renames8992399
Ref: 2a6d8992399
Ref: library/os os replace8993192
Ref: 108b8993192
Ref: library/os os rmdir8994076
Ref: 108c8994076
Ref: library/os os scandir8994716
Ref: a028994716
Ref: library/os os scandir close8996491
Ref: c638996491
Ref: library/os os DirEntry8998017
Ref: 4438998017
Ref: library/os os DirEntry name8999203
Ref: 2a6f8999203
Ref: library/os os DirEntry path8999569
Ref: 15728999569
Ref: library/os os DirEntry inode9000299
Ref: 15d49000299
Ref: library/os os DirEntry is_dir9000658
Ref: 2a6e9000658
Ref: library/os os DirEntry is_file9002089
Ref: d2a9002089
Ref: library/os os DirEntry is_symlink9002808
Ref: 2a709002808
Ref: library/os os DirEntry is_junction9003657
Ref: 4449003657
Ref: library/os os DirEntry stat9004090
Ref: 15f59004090
Ref: library/os os stat9005828
Ref: 4489005828
Ref: library/os os stat_result9008393
Ref: 142c9008393
Ref: library/os os stat_result st_mode9008642
Ref: 2a719008642
Ref: library/os os stat_result st_ino9008734
Ref: 2a729008734
Ref: library/os os stat_result st_dev9008980
Ref: 2a739008980
Ref: library/os os stat_result st_nlink9009069
Ref: 2a749009069
Ref: library/os os stat_result st_uid9009129
Ref: 2a759009129
Ref: library/os os stat_result st_gid9009200
Ref: 2a769009200
Ref: library/os os stat_result st_size9009272
Ref: 2a779009272
Ref: library/os os stat_result st_atime9009523
Ref: 2a789009523
Ref: library/os os stat_result st_mtime9009610
Ref: 29099009610
Ref: library/os os stat_result st_ctime9009711
Ref: 2a799009711
Ref: library/os os stat_result st_atime_ns9010077
Ref: 2a7a9010077
Ref: library/os os stat_result st_mtime_ns9010228
Ref: 2a7b9010228
Ref: library/os os stat_result st_ctime_ns9010393
Ref: 2a7c9010393
Ref: library/os os stat_result st_birthtime9010829
Ref: 2a7d9010829
Ref: library/os os stat_result st_birthtime_ns9011089
Ref: 2a7e9011089
Ref: library/os os stat_result st_blocks9012674
Ref: 2a7f9012674
Ref: library/os os stat_result st_blksize9012845
Ref: 2a809012845
Ref: library/os os stat_result st_rdev9013040
Ref: 2a819013040
Ref: library/os os stat_result st_flags9013112
Ref: 2a829013112
Ref: library/os os stat_result st_gen9013334
Ref: 2a839013334
Ref: library/os os stat_result st_fstype9013481
Ref: b089013481
Ref: library/os os stat_result st_rsize9013685
Ref: 2a849013685
Ref: library/os os stat_result st_creator9013746
Ref: 2a859013746
Ref: library/os os stat_result st_type9013807
Ref: 2a869013807
Ref: library/os os stat_result st_file_attributes9013926
Ref: dde9013926
Ref: library/os os stat_result st_reparse_tag9014303
Ref: 2a879014303
Ref: library/os os statvfs9016675
Ref: 10949016675
Ref: library/os os supports_dir_fd9018685
Ref: 10909018685
Ref: library/os os supports_effective_ids9019844
Ref: 10969019844
Ref: library/os os supports_fd9020589
Ref: 10959020589
Ref: library/os os supports_follow_symlinks9021415
Ref: 274b9021415
Ref: library/os os symlink9022549
Ref: 108d9022549
Ref: library/os os sync9024306
Ref: 10aa9024306
Ref: library/os os truncate9024435
Ref: de29024435
Ref: library/os os unlink9024957
Ref: 108e9024957
Ref: library/os os utime9025488
Ref: 108f9025488
Ref: library/os os walk9027372
Ref: 4519027372
Ref: library/os os fwalk9032587
Ref: aff9032587
Ref: library/os os memfd_create9035188
Ref: 9af9035188
Ref: library/os os MFD_CLOEXEC9036054
Ref: 2a889036054
Ref: library/os os MFD_ALLOW_SEALING9036081
Ref: 2a899036081
Ref: library/os os MFD_HUGETLB9036114
Ref: 2a8a9036114
Ref: library/os os MFD_HUGE_SHIFT9036141
Ref: 2a8b9036141
Ref: library/os os MFD_HUGE_MASK9036171
Ref: 2a8c9036171
Ref: library/os os MFD_HUGE_64KB9036200
Ref: 2a8d9036200
Ref: library/os os MFD_HUGE_512KB9036229
Ref: 2a8e9036229
Ref: library/os os MFD_HUGE_1MB9036259
Ref: 2a8f9036259
Ref: library/os os MFD_HUGE_2MB9036287
Ref: 2a909036287
Ref: library/os os MFD_HUGE_8MB9036315
Ref: 2a919036315
Ref: library/os os MFD_HUGE_16MB9036343
Ref: 2a929036343
Ref: library/os os MFD_HUGE_32MB9036372
Ref: 2a939036372
Ref: library/os os MFD_HUGE_256MB9036401
Ref: 2a949036401
Ref: library/os os MFD_HUGE_512MB9036431
Ref: 2a959036431
Ref: library/os os MFD_HUGE_1GB9036461
Ref: 2a969036461
Ref: library/os os MFD_HUGE_2GB9036489
Ref: 2a979036489
Ref: library/os os MFD_HUGE_16GB9036517
Ref: 2a989036517
Ref: library/os os eventfd9036771
Ref: 7bc9036771
Ref: library/os os eventfd_read9038790
Ref: 2a9a9038790
Ref: library/os os eventfd_write9039076
Ref: 2a9b9039076
Ref: library/os os EFD_CLOEXEC9039374
Ref: 16d39039374
Ref: library/os os EFD_NONBLOCK9039560
Ref: 16d49039560
Ref: library/os os EFD_SEMAPHORE9039770
Ref: 16d59039770
Ref: Files and Directories-Footnote-19040139
Ref: Files and Directories-Footnote-29040185
Ref: Files and Directories-Footnote-39040227
Ref: Files and Directories-Footnote-49040292
Ref: Files and Directories-Footnote-59040372
Ref: Files and Directories-Footnote-69040454
Ref: Files and Directories-Footnote-79040543
Ref: Files and Directories-Footnote-89040632
Ref: Files and Directories-Footnote-99040690
Node: Timer File Descriptors9040737
Ref: library/os os-timerfd9040851
Ref: 1389040851
Ref: library/os timer-file-descriptors9040851
Ref: 2a9c9040851
Ref: library/os os timerfd_create9041063
Ref: 1f69041063
Ref: library/os os timerfd_settime9043745
Ref: 1f79043745
Ref: library/os os timerfd_settime_ns9046451
Ref: 1f89046451
Ref: library/os os timerfd_gettime9046809
Ref: 1f99046809
Ref: library/os os timerfd_gettime_ns9047403
Ref: 1fa9047403
Ref: library/os os TFD_NONBLOCK9047633
Ref: 1fb9047633
Ref: library/os os TFD_CLOEXEC9048003
Ref: 1fc9048003
Ref: library/os os TFD_TIMER_ABSTIME9048297
Ref: 1fd9048297
Ref: library/os os TFD_TIMER_CANCEL_ON_SET9048691
Ref: 1fe9048691
Ref: Timer File Descriptors-Footnote-19049111
Ref: Timer File Descriptors-Footnote-29049165
Ref: Timer File Descriptors-Footnote-39049219
Ref: Timer File Descriptors-Footnote-49049274
Ref: Timer File Descriptors-Footnote-59049326
Ref: Timer File Descriptors-Footnote-69049379
Ref: Timer File Descriptors-Footnote-79049423
Node: Linux extended attributes9049478
Ref: library/os linux-extended-attributes9049592
Ref: 2a9e9049592
Ref: library/os os getxattr9049738
Ref: 109c9049738
Ref: library/os os listxattr9050399
Ref: 109d9050399
Ref: library/os os removexattr9051004
Ref: 109e9051004
Ref: library/os os setxattr9051696
Ref: 109f9051696
Ref: library/os os XATTR_SIZE_MAX9052946
Ref: 2aa19052946
Ref: library/os os XATTR_CREATE9053084
Ref: 2aa09053084
Ref: library/os os XATTR_REPLACE9053258
Ref: 2a9f9053258
Node: 行程管理9053443
Ref: library/os os-process9053588
Ref: 2aa29053588
Ref: library/os process-management9053588
Ref: 2aa39053588
Ref: library/os os abort9054185
Ref: 2aa59054185
Ref: library/os os add_dll_directory9054559
Ref: 98e9054559
Ref: library/os os execl9055722
Ref: 2aa49055722
Ref: library/os os execle9055767
Ref: 2aa69055767
Ref: library/os os execlp9055818
Ref: 2aa79055818
Ref: library/os os execlpe9055864
Ref: 2aa89055864
Ref: library/os os execv9055916
Ref: 2a049055916
Ref: library/os os execve9055950
Ref: 10919055950
Ref: library/os os execvp9055990
Ref: 2aa99055990
Ref: library/os os execvpe9056025
Ref: 2aaa9056025
Ref: library/os os _exit9059360
Ref: 21749059360
Ref: library/os os EX_OK9060106
Ref: 2aab9060106
Ref: library/os os EX_USAGE9060340
Ref: 2aac9060340
Ref: library/os os EX_DATAERR9060532
Ref: 2aad9060532
Ref: library/os os EX_NOINPUT9060663
Ref: 2aae9060663
Ref: library/os os EX_NOUSER9060818
Ref: 2aaf9060818
Ref: library/os os EX_NOHOST9060950
Ref: 2ab09060950
Ref: library/os os EX_UNAVAILABLE9061082
Ref: 2ab19061082
Ref: library/os os EX_SOFTWARE9061227
Ref: 2ab29061227
Ref: library/os os EX_OSERR9061370
Ref: 2ab39061370
Ref: library/os os EX_OSFILE9061562
Ref: 2ab49061562
Ref: library/os os EX_CANTCREAT9061753
Ref: 2ab59061753
Ref: library/os os EX_IOERR9061912
Ref: 2ab69061912
Ref: library/os os EX_TEMPFAIL9062069
Ref: 2ab79062069
Ref: library/os os EX_PROTOCOL9062351
Ref: 2ab89062351
Ref: library/os os EX_NOPERM9062524
Ref: 2ab99062524
Ref: library/os os EX_CONFIG9062740
Ref: 2aba9062740
Ref: library/os os EX_NOTFOUND9062893
Ref: 2abb9062893
Ref: library/os os fork9063036
Ref: 17b9063036
Ref: library/os os forkpty9065018
Ref: 17c9065018
Ref: library/os os kill9066131
Ref: 12f49066131
Ref: library/os os killpg9067109
Ref: 18db9067109
Ref: library/os os nice9067364
Ref: 10999067364
Ref: library/os os pidfd_open9067529
Ref: 4219067529
Ref: library/os os PIDFD_NONBLOCK9067881
Ref: 4429067881
Ref: library/os os plock9068333
Ref: 2abc9068333
Ref: library/os os popen9068556
Ref: a2a9068556
Ref: library/os os posix_spawn9070479
Ref: 2059070479
Ref: library/os os POSIX_SPAWN_OPEN9071575
Ref: 2abd9071575
Ref: library/os os POSIX_SPAWN_CLOSE9071750
Ref: 2abe9071750
Ref: library/os os POSIX_SPAWN_DUP29071875
Ref: 2abf9071875
Ref: library/os os POSIX_SPAWN_CLOSEFROM9072015
Ref: 2069072015
Ref: library/os os posix_spawnp9074907
Ref: 19359074907
Ref: library/os os register_at_fork9075651
Ref: 2d19075651
Ref: library/os os spawnl9077085
Ref: 16309077085
Ref: library/os os spawnle9077125
Ref: 2ac19077125
Ref: library/os os spawnlp9077171
Ref: 2ac29077171
Ref: library/os os spawnlpe9077212
Ref: 2ac39077212
Ref: library/os os spawnv9077259
Ref: 2ac49077259
Ref: library/os os spawnve9077300
Ref: 2ac59077300
Ref: library/os os spawnvp9077347
Ref: 2ac69077347
Ref: library/os os spawnvpe9077389
Ref: 2ac79077389
Ref: library/os os P_NOWAIT9081257
Ref: 2ac89081257
Ref: library/os os P_NOWAITO9081281
Ref: 2aca9081281
Ref: library/os os P_WAIT9081632
Ref: 2ac99081632
Ref: library/os os P_DETACH9082054
Ref: 2acb9082054
Ref: library/os os P_OVERLAY9082078
Ref: 2acc9082078
Ref: library/os os startfile9082569
Ref: 17ce9082569
Ref: library/os os system9085159
Ref: 13c89085159
Ref: library/os os times9086893
Ref: 10ad9086893
Ref: library/os os wait9087899
Ref: d3e9087899
Ref: library/os os waitid9088792
Ref: d3f9088792
Ref: library/os os waitpid9090206
Ref: d409090206
Ref: library/os os wait39092544
Ref: d3c9092544
Ref: library/os os wait49093155
Ref: d3d9093155
Ref: library/os os P_PID9093729
Ref: 2acd9093729
Ref: library/os os P_PGID9093750
Ref: 2ace9093750
Ref: library/os os P_ALL9093772
Ref: 2acf9093772
Ref: library/os os P_PIDFD9093793
Ref: 8bf9093793
Ref: library/os os WCONTINUED9094517
Ref: 2ad29094517
Ref: library/os os WEXITED9094855
Ref: 2ad09094855
Ref: library/os os WSTOPPED9095211
Ref: 2ad19095211
Ref: library/os os WUNTRACED9095540
Ref: 2ad79095540
Ref: library/os os WNOHANG9095935
Ref: 2ad39095935
Ref: library/os os WNOWAIT9096221
Ref: 2ad49096221
Ref: library/os os CLD_EXITED9096574
Ref: 2ad69096574
Ref: library/os os CLD_KILLED9096600
Ref: 8bd9096600
Ref: library/os os CLD_DUMPED9096626
Ref: 2ad89096626
Ref: library/os os CLD_TRAPPED9096652
Ref: 2ad99096652
Ref: library/os os CLD_STOPPED9096679
Ref: 8be9096679
Ref: library/os os CLD_CONTINUED9096706
Ref: 2ada9096706
Ref: library/os os waitstatus_to_exitcode9097026
Ref: 8c29097026
Ref: library/os os WCOREDUMP9098511
Ref: 2ae19098511
Ref: library/os os WIFCONTINUED9098800
Ref: 2ae29098800
Ref: library/os os WIFSTOPPED9099140
Ref: 2adf9099140
Ref: library/os os WIFSIGNALED9099552
Ref: 2add9099552
Ref: library/os os WIFEXITED9099749
Ref: 2adb9099749
Ref: library/os os WEXITSTATUS9100035
Ref: 2adc9100035
Ref: library/os os WSTOPSIG9100254
Ref: 2ae09100254
Ref: library/os os WTERMSIG9100491
Ref: 2ade9100491
Ref: 行程管理-Footnote-19100788
Ref: 行程管理-Footnote-29100860
Ref: 行程管理-Footnote-39100903
Ref: 行程管理-Footnote-49100953
Ref: 行程管理-Footnote-59100999
Ref: 行程管理-Footnote-69101044
Ref: 行程管理-Footnote-79101096
Ref: 行程管理-Footnote-89101205
Ref: 行程管理-Footnote-99101247
Node: Interface to the scheduler9101293
Ref: library/os interface-to-the-scheduler9101449
Ref: 2ae49101449
Ref: library/os os SCHED_OTHER9101836
Ref: 2ae59101836
Ref: library/os os SCHED_BATCH9101901
Ref: 2ae69101901
Ref: library/os os SCHED_IDLE9102052
Ref: 2ae79102052
Ref: library/os os SCHED_SPORADIC9102148
Ref: 2ae89102148
Ref: library/os os SCHED_FIFO9102233
Ref: 2ae99102233
Ref: library/os os SCHED_RR9102306
Ref: 2aea9102306
Ref: library/os os SCHED_RESET_ON_FORK9102370
Ref: 2aeb9102370
Ref: library/os os sched_param9102590
Ref: 2ac09102590
Ref: library/os os sched_param sched_priority9102886
Ref: 2aec9102886
Ref: library/os os sched_get_priority_min9102979
Ref: 10a19102979
Ref: library/os os sched_get_priority_max9103142
Ref: 10a09103142
Ref: library/os os sched_setscheduler9103305
Ref: 10a89103305
Ref: library/os os sched_getscheduler9103592
Ref: 10a49103592
Ref: library/os os sched_setparam9103815
Ref: 10a79103815
Ref: library/os os sched_getparam9104030
Ref: 10a39104030
Ref: library/os os sched_rr_get_interval9104231
Ref: 10a59104231
Ref: library/os os sched_yield9104404
Ref: 10a99104404
Ref: library/os os sched_setaffinity9104473
Ref: 10a69104473
Ref: library/os os sched_getaffinity9104737
Ref: 10a29104737
Node: Miscellaneous System Information9105027
Ref: library/os miscellaneous-system-information9105185
Ref: 2aed9105185
Ref: library/os os-path9105185
Ref: 2aee9105185
Ref: library/os os confstr9105272
Ref: 2aef9105272
Ref: library/os os confstr_names9106304
Ref: 2af09106304
Ref: library/os os cpu_count9106596
Ref: 1a89106596
Ref: library/os os getloadavg9107088
Ref: 14d99107088
Ref: library/os os process_cpu_count9107337
Ref: 1a79107337
Ref: library/os os sysconf9107951
Ref: 2a4f9107951
Ref: library/os os sysconf_names9108368
Ref: 2af19108368
Ref: library/os os curdir9108921
Ref: 26b79108921
Ref: library/os os pardir9109124
Ref: 2a6a9109124
Ref: library/os os sep9109327
Ref: 6109109327
Ref: library/os os altsep9109739
Ref: 6119109739
Ref: library/os os extsep9110040
Ref: 2af29110040
Ref: library/os os pathsep9110229
Ref: 1c469110229
Ref: library/os os defpath9110475
Ref: 19089110475
Ref: library/os os linesep9110684
Ref: 20559110684
Ref: library/os os devnull9111099
Ref: 19399111099
Ref: library/os os RTLD_LAZY9111275
Ref: 10b09111275
Ref: library/os os RTLD_NOW9111300
Ref: 10b19111300
Ref: library/os os RTLD_GLOBAL9111324
Ref: 10b29111324
Ref: library/os os RTLD_LOCAL9111351
Ref: 10b39111351
Ref: library/os os RTLD_NODELETE9111377
Ref: 10b49111377
Ref: library/os os RTLD_NOLOAD9111406
Ref: 10b59111406
Ref: library/os os RTLD_DEEPBIND9111433
Ref: 10b69111433
Ref: Miscellaneous System Information-Footnote-19111721
Node: Random numbers9111767
Ref: library/os random-numbers9111890
Ref: 2af39111890
Ref: library/os os getrandom9111941
Ref: c649111941
Ref: library/os os urandom9112770
Ref: 4c79112770
Ref: library/os os GRND_NONBLOCK9114824
Ref: 2af59114824
Ref: library/os os GRND_RANDOM9115301
Ref: 2af49115301
Ref: Random numbers-Footnote-19115524
Ref: Random numbers-Footnote-29115587
Node: io — 處理資料串流的核心工具9115629
Ref: library/io doc9115809
Ref: 2af69115809
Ref: library/io io-core-tools-for-working-with-streams9115809
Ref: 2af79115809
Ref: library/io module-io9115809
Ref: 739115809
Ref: io — 處理資料串流的核心工具-Footnote-19116142
Node: 總覽9116204
Ref: library/io io-overview9116308
Ref: 20539116308
Ref: library/io overview9116308
Ref: 2af89116308
Node: 文字 I/O9117742
Ref: library/io text-i-o9117824
Ref: 2af99117824
Node: 二進位 Binary I/O9118495
Ref: library/io binary-i-o9118600
Ref: 2afa9118600
Node: 原始 Raw I/O9119521
Ref: library/io raw-i-o9119607
Ref: 2afb9119607
Node: 文字編碼9120097
Ref: library/io io-text-encoding9120228
Ref: 7619120228
Ref: library/io text-encoding9120228
Ref: 2afc9120228
Ref: 文字編碼-Footnote-19121412
Node: 選擇性加入的編碼警告9121454
Ref: library/io io-encoding-warning9121533
Ref: 1c579121533
Ref: library/io opt-in-encodingwarning9121533
Ref: 2afd9121533
Ref: 選擇性加入的編碼警告-Footnote-19122360
Node: 高階模組介面9122402
Ref: library/io high-level-module-interface9122539
Ref: 2afe9122539
Ref: library/io io DEFAULT_BUFFER_SIZE9122590
Ref: 15c29122590
Ref: library/io io open9122835
Ref: 4c19122835
Ref: library/io io open_code9123256
Ref: 16259123256
Ref: library/io io text_encoding9123864
Ref: 15c19123864
Ref: library/io io BlockingIOError9124992
Ref: 2aff9124992
Ref: library/io io UnsupportedOperation9125102
Ref: 189a9125102
Node: 類別階層9125439
Ref: library/io class-hierarchy9125578
Ref: 2b009125578
Node: I/O 基礎類別9130195
Ref: library/io i-o-base-classes9130285
Ref: 2b029130285
Ref: library/io io IOBase9130334
Ref: 1da9130334
Ref: library/io io IOBase close9132111
Ref: 1db9132111
Ref: library/io io IOBase closed9132491
Ref: 19329132491
Ref: library/io io IOBase fileno9132572
Ref: 27329132572
Ref: library/io io IOBase flush9132792
Ref: 2b039132792
Ref: library/io io IOBase isatty9132959
Ref: 1b869132959
Ref: library/io io IOBase readable9133090
Ref: 2b049133090
Ref: library/io io IOBase readline9133275
Ref: 12bd9133275
Ref: library/io io IOBase readlines9133639
Ref: 22119133639
Ref: library/io io IOBase seek9134199
Ref: 12249134199
Ref: library/io io IOBase seekable9135117
Ref: 2b059135117
Ref: library/io io IOBase tell9135365
Ref: 28949135365
Ref: library/io io IOBase truncate9135433
Ref: 12a59135433
Ref: library/io io IOBase writable9135992
Ref: 2b069135992
Ref: library/io io IOBase writelines9136195
Ref: 22129136195
Ref: library/io io IOBase __del__9136405
Ref: 2b079136405
Ref: library/io io RawIOBase9136599
Ref: 106a9136599
Ref: library/io io RawIOBase read9137089
Ref: dc29137089
Ref: library/io io RawIOBase readall9137791
Ref: 2b089137791
Ref: library/io io RawIOBase readinto9137948
Ref: dc39137948
Ref: library/io io RawIOBase write9138318
Ref: 28d39138318
Ref: library/io io BufferedIOBase9138900
Ref: 63a9138900
Ref: library/io io BufferedIOBase raw9140086
Ref: 2b0a9140086
Ref: library/io io BufferedIOBase detach9140343
Ref: 285b9140343
Ref: library/io io BufferedIOBase read9140745
Ref: 12bc9140745
Ref: library/io io BufferedIOBase read19141493
Ref: 284b9141493
Ref: library/io io BufferedIOBase readinto9141971
Ref: 2b099141971
Ref: library/io io BufferedIOBase readinto19142506
Ref: dc19142506
Ref: library/io io BufferedIOBase write9142984
Ref: c829142984
Node: 原始檔案 I/O9143716
Ref: library/io raw-file-i-o9143831
Ref: 2b0b9143831
Ref: library/io io FileIO9143882
Ref: 12a49143882
Ref: library/io io FileIO mode9146173
Ref: 2b0c9146173
Ref: library/io io FileIO name9146245
Ref: 28659146245
Node: Buffered Streams9146387
Ref: library/io buffered-streams9146499
Ref: 2b0d9146499
Ref: library/io io BytesIO9146645
Ref: e469146645
Ref: library/io io BytesIO getbuffer9147127
Ref: 11899147127
Ref: library/io io BytesIO getvalue9147698
Ref: 28499147698
Ref: library/io io BytesIO read19147820
Ref: 2b0e9147820
Ref: library/io io BytesIO readinto19148001
Ref: 2b0f9148001
Ref: library/io io BufferedReader9148157
Ref: 11a69148157
Ref: library/io io BufferedReader peek9148998
Ref: 2b109148998
Ref: library/io io BufferedReader read9149272
Ref: 2b119149272
Ref: library/io io BufferedReader read19149472
Ref: 2b129149472
Ref: library/io io BufferedWriter9149808
Ref: 20569149808
Ref: library/io io BufferedWriter flush9150929
Ref: 2b139150929
Ref: library/io io BufferedWriter write9151113
Ref: 2b149151113
Ref: library/io io BufferedRandom9151403
Ref: 20579151403
Ref: library/io io BufferedRWPair9152106
Ref: 2b019152106
Node: 文字 I/O<2>9153045
Ref: library/io id19153132
Ref: 2b159153132
Ref: library/io io TextIOBase9153173
Ref: 63b9153173
Ref: library/io io TextIOBase encoding9153490
Ref: 2b169153490
Ref: library/io io TextIOBase errors9153645
Ref: 12a39153645
Ref: library/io io TextIOBase newlines9153726
Ref: 2b179153726
Ref: library/io io TextIOBase buffer9153967
Ref: 12399153967
Ref: library/io io TextIOBase detach9154237
Ref: 2b189154237
Ref: library/io io TextIOBase read9154754
Ref: 1b899154754
Ref: library/io io TextIOBase readline9154962
Ref: 1bc09154962
Ref: library/io io TextIOBase seek9155232
Ref: 2b199155232
Ref: library/io io TextIOBase tell9156196
Ref: 2b1a9156196
Ref: library/io io TextIOBase write9156400
Ref: 1b789156400
Ref: library/io io TextIOWrapper9156532
Ref: 75f9156532
Ref: library/io io TextIOWrapper line_buffering9160308
Ref: 2b1b9160308
Ref: library/io io TextIOWrapper write_through9160387
Ref: 2b1c9160387
Ref: library/io io TextIOWrapper reconfigure9160544
Ref: aed9160544
Ref: library/io io TextIOWrapper seek9161432
Ref: 2b1d9161432
Ref: library/io io TextIOWrapper tell9162352
Ref: 2b1e9162352
Ref: library/io io StringIO9162575
Ref: ecb9162575
Ref: library/io io StringIO getvalue9163741
Ref: 2b1f9163741
Ref: library/io io IncrementalNewlineDecoder9164397
Ref: 15c39164397
Node: Performance<3>9164585
Ref: library/io performance9164697
Ref: 2b209164697
Node: 二進位 Binary I/O<2>9164972
Ref: library/io id29165068
Ref: 2b219165068
Node: 文字 I/O<3>9165739
Ref: library/io id39165862
Ref: 2b229165862
Node: Multi-threading<2>9166427
Ref: library/io multi-threading9166537
Ref: 2b239166537
Ref: Multi-threading<2>-Footnote-19167111
Node: Reentrancy9167155
Ref: library/io reentrancy9167243
Ref: 2b249167243
Node: time --- 時間存取與轉換9168034
Ref: library/time doc9168254
Ref: 2b259168254
Ref: library/time module-time9168254
Ref: d79168254
Ref: library/time time-time-access-and-conversions9168254
Ref: 2b269168254
Ref: library/time epoch9168889
Ref: 29089168889
Ref: time --- 時間存取與轉換-Footnote-19173121
Node: 函式<4>9173171
Ref: library/time functions9173274
Ref: 2b299173274
Ref: library/time time-functions9173274
Ref: 2b2a9173274
Ref: library/time time asctime9173305
Ref: 117f9173305
Ref: library/time time pthread_getcpuclockid9173935
Ref: b399173935
Ref: library/time time clock_getres9174530
Ref: 10f69174530
Ref: library/time time clock_gettime9174792
Ref: 10f79174792
Ref: library/time time clock_gettime_ns9175158
Ref: a859175158
Ref: library/time time clock_settime9175381
Ref: 10f89175381
Ref: library/time time clock_settime_ns9175739
Ref: a869175739
Ref: library/time time ctime9175945
Ref: 232f9175945
Ref: library/time time get_clock_info9176497
Ref: 10f59176497
Ref: library/time time gmtime9177550
Ref: 11589177550
Ref: library/time time localtime9178008
Ref: 14679178008
Ref: library/time time mktime9178634
Ref: 11809178634
Ref: library/time time monotonic9179247
Ref: 2389179247
Ref: library/time time monotonic_ns9180251
Ref: a879180251
Ref: library/time time perf_counter9180402
Ref: a2b9180402
Ref: library/time time perf_counter_ns9181241
Ref: a889181241
Ref: library/time time process_time9181398
Ref: a2c9181398
Ref: library/time time process_time_ns9181868
Ref: a899181868
Ref: library/time time sleep9182025
Ref: 6429182025
Ref: library/time time strftime9183636
Ref: 11819183636
Ref: library/time leap-second9190171
Ref: 2b2c9190171
Ref: library/time time strptime9191263
Ref: 139a9191263
Ref: library/time time struct_time9192725
Ref: c919192725
Ref: library/time time struct_time tm_year9193328
Ref: 14669193328
Ref: library/time time struct_time tm_mon9193592
Ref: 2b2d9193592
Ref: library/time time struct_time tm_mday9193855
Ref: 2b2e9193855
Ref: library/time time struct_time tm_hour9194117
Ref: 2b2f9194117
Ref: library/time time struct_time tm_min9194378
Ref: 2b309194378
Ref: library/time time struct_time tm_sec9194640
Ref: 2b319194640
Ref: library/time time struct_time tm_wday9195129
Ref: 2b329195129
Ref: library/time time struct_time tm_yday9195407
Ref: 2b339195407
Ref: library/time time struct_time tm_isdst9195671
Ref: 23409195671
Ref: library/time time struct_time tm_zone9195942
Ref: 2b289195942
Ref: library/time time struct_time tm_gmtoff9196213
Ref: 2b279196213
Ref: library/time time time9196870
Ref: 2399196870
Ref: library/time time time_ns9198166
Ref: a8a9198166
Ref: library/time time thread_time9198342
Ref: 8da9198342
Ref: library/time time thread_time_ns9199008
Ref: b389199008
Ref: library/time time tzset9199159
Ref: 2b349199159
Ref: 函式<4>-Footnote-19203041
Ref: 函式<4>-Footnote-29203102
Ref: 函式<4>-Footnote-39203199
Ref: 函式<4>-Footnote-49203241
Ref: 函式<4>-Footnote-59203926
Ref: 函式<4>-Footnote-69204611
Ref: 函式<4>-Footnote-79204661
Ref: 函式<4>-Footnote-89204720
Ref: 函式<4>-Footnote-99205405
Ref: 函式<4>-Footnote-109205453
Ref: 函式<4>-Footnote-119205504
Ref: 函式<4>-Footnote-129205553
Node: Clock ID Constants9205600
Ref: library/time clock-id-constants9205730
Ref: 2b359205730
Ref: library/time time-clock-id-constants9205730
Ref: 2a9d9205730
Ref: library/time time CLOCK_BOOTTIME9205892
Ref: b349205892
Ref: library/time time CLOCK_HIGHRES9206373
Ref: 2b369206373
Ref: library/time time CLOCK_MONOTONIC9206700
Ref: b359206700
Ref: library/time time CLOCK_MONOTONIC_RAW9206903
Ref: 2b379206903
Ref: library/time time CLOCK_MONOTONIC_RAW_APPROX9207180
Ref: 2b389207180
Ref: library/time time CLOCK_PROCESS_CPUTIME_ID9207445
Ref: 2b399207445
Ref: library/time time CLOCK_PROF9207606
Ref: b369207606
Ref: library/time time CLOCK_TAI9207784
Ref: 186f9207784
Ref: library/time time CLOCK_THREAD_CPUTIME_ID9208078
Ref: 2b3a9208078
Ref: library/time time CLOCK_UPTIME9208222
Ref: b379208222
Ref: library/time time CLOCK_UPTIME_RAW9208509
Ref: 9e69208509
Ref: library/time time CLOCK_UPTIME_RAW_APPROX9208811
Ref: 2b3b9208811
Ref: library/time time CLOCK_REALTIME9209163
Ref: 63f9209163
Ref: Clock ID Constants-Footnote-19209389
Node: Timezone Constants9209496
Ref: library/time time-timezone-constants9209608
Ref: 2b3c9209608
Ref: library/time timezone-constants9209608
Ref: 2b3d9209608
Ref: library/time time altzone9209665
Ref: 2b3e9209665
Ref: library/time time daylight9209955
Ref: 2b3f9209955
Ref: library/time time timezone9210043
Ref: 2b409210043
Ref: library/time time tzname9210243
Ref: 2b419210243
Node: argparse --- Parser for command-line options arguments and sub-commands9211461
Ref: library/argparse doc9211681
Ref: 2b429211681
Ref: library/argparse argparse-parser-for-command-line-options-arguments-and-sub-commands9211681
Ref: 2b439211681
Ref: library/argparse module-argparse9211681
Ref: 59211681
Ref: argparse --- Parser for command-line options arguments and sub-commands-Footnote-19212909
Node: Core Functionality9212977
Ref: library/argparse core-functionality9213140
Ref: 2b459213140
Node: Quick Links for add_argument9214313
Ref: library/argparse quick-links-for-add-argument9214495
Ref: 2b489214495
Node: 範例<18>9217997
Ref: library/argparse example9218182
Ref: 2b539218182
Node: 建立一個剖析器9219786
Ref: library/argparse creating-a-parser9219875
Ref: 2b549219875
Node: 增加引數9220239
Ref: library/argparse adding-arguments9220349
Ref: 2b559220349
Node: 剖析引數9221487
Ref: library/argparse parsing-arguments9221567
Ref: 2b569221567
Node: ArgumentParser 物件9222284
Ref: library/argparse argumentparser-objects9222464
Ref: 2b579222464
Ref: library/argparse argparse ArgumentParser9222525
Ref: 4de9222525
Node: prog9225263
Ref: library/argparse id19225339
Ref: 2b649225339
Ref: library/argparse prog9225339
Ref: 2b589225339
Node: usage9227157
Ref: library/argparse usage9227248
Ref: 2b599227248
Node: 描述9228396
Ref: library/argparse description9228489
Ref: 2b5a9228489
Ref: library/argparse id29228489
Ref: 2b659228489
Node: epilog9229231
Ref: library/argparse epilog9229326
Ref: 2b5b9229326
Node: parents9230096
Ref: library/argparse parents9230200
Ref: 2b5c9230200
Node: formatter_class9231656
Ref: library/argparse formatter-class9231766
Ref: 2b5d9231766
Ref: library/argparse id39231766
Ref: 2b669231766
Ref: library/argparse argparse RawDescriptionHelpFormatter9231984
Ref: 2b679231984
Ref: library/argparse argparse RawTextHelpFormatter9232033
Ref: 2b689232033
Ref: library/argparse argparse ArgumentDefaultsHelpFormatter9232075
Ref: 179e9232075
Ref: library/argparse argparse MetavarTypeHelpFormatter9232126
Ref: 2b699232126
Node: prefix_chars9235594
Ref: library/argparse prefix-chars9235718
Ref: 2b5e9235718
Node: fromfile_prefix_chars9236456
Ref: library/argparse fromfile-prefix-chars9236581
Ref: 2b5f9236581
Node: argument_default9238336
Ref: library/argparse argument-default9238461
Ref: 2b609238461
Node: allow_abbrev9239347
Ref: library/argparse allow-abbrev9239467
Ref: d669239467
Ref: library/argparse id49239467
Ref: 2b6d9239467
Node: conflict_handler9240120
Ref: library/argparse conflict-handler9240232
Ref: 2b619240232
Node: add_help9241779
Ref: library/argparse add-help9241892
Ref: 2b629241892
Node: exit_on_error9243435
Ref: library/argparse exit-on-error9243523
Ref: 2b639243523
Node: The add_argument method9244349
Ref: library/argparse the-add-argument-method9244540
Ref: 2b6e9244540
Ref: library/argparse argparse ArgumentParser add_argument9244613
Ref: 1849244613
Node: name or flags9246586
Ref: library/argparse id59246674
Ref: 2b6f9246674
Ref: library/argparse name-or-flags9246674
Ref: 2b719246674
Node: action9247821
Ref: library/argparse action9247923
Ref: 2b499247923
Ref: library/argparse id69247923
Ref: 2b729247923
Node: nargs9254205
Ref: library/argparse id79254299
Ref: 2b739254299
Ref: library/argparse nargs9254299
Ref: 2b509254299
Node: const9258379
Ref: library/argparse const9258474
Ref: 2b4b9258474
Ref: library/argparse id89258474
Ref: 2b759258474
Node: default9259765
Ref: library/argparse default9259859
Ref: 2b4c9259859
Ref: library/argparse id99259859
Ref: 2b769259859
Node: type9262065
Ref: library/argparse argparse-type9262161
Ref: 2b529262161
Ref: library/argparse type9262161
Ref: 2b6a9262161
Node: choices9265134
Ref: library/argparse choices9265231
Ref: 2b4a9265231
Ref: library/argparse id109265231
Ref: 2b789265231
Node: required9267143
Ref: library/argparse id119267242
Ref: 2b799267242
Ref: library/argparse required9267242
Ref: 2b519267242
Node: 幫助9268203
Ref: library/argparse help9268302
Ref: 2b4e9268302
Ref: library/argparse id129268302
Ref: 2b7a9268302
Node: metavar9270381
Ref: library/argparse id139270476
Ref: 2b7b9270476
Ref: library/argparse metavar9270476
Ref: 2b4f9270476
Node: dest9272681
Ref: library/argparse dest9272780
Ref: 2b4d9272780
Ref: library/argparse id149272780
Ref: 2b7c9272780
Node: deprecated9274413
Ref: library/argparse deprecated9274519
Ref: 2b709274519
Ref: library/argparse id159274519
Ref: 2b7d9274519
Node: Action classes9275423
Ref: library/argparse action-classes9275516
Ref: 2b7e9275516
Ref: library/argparse argparse Action9275803
Ref: 17049275803
Node: The parse_args method9277792
Ref: library/argparse the-parse-args-method9277977
Ref: 2b7f9277977
Ref: library/argparse argparse ArgumentParser parse_args9278046
Ref: 2b469278046
Node: Option value syntax9278921
Ref: library/argparse option-value-syntax9279024
Ref: 2b829279024
Node: Invalid arguments9280421
Ref: library/argparse invalid-arguments9280555
Ref: 2b839280555
Node: Arguments containing -9281540
Ref: library/argparse arguments-containing9281693
Ref: 2b849281693
Node: Argument abbreviations prefix matching9283779
Ref: library/argparse argument-abbreviations-prefix-matching9283930
Ref: 2b859283930
Ref: library/argparse prefix-matching9283930
Ref: d659283930
Node: Beyond sys argv9284858
Ref: library/argparse args9285007
Ref: 2b809285007
Ref: library/argparse beyond-sys-argv9285007
Ref: 2b869285007
Node: The Namespace object9285958
Ref: library/argparse namespace9286060
Ref: 2b819286060
Ref: library/argparse the-namespace-object9286060
Ref: 2b879286060
Ref: library/argparse argparse Namespace9286123
Ref: 2b479286123
Node: Other utilities9287149
Ref: library/argparse other-utilities9287334
Ref: 2b889287334
Node: Sub-commands9287605
Ref: library/argparse sub-commands9287693
Ref: 2b899287693
Ref: library/argparse argparse ArgumentParser add_subparsers9287740
Ref: bbe9287740
Node: FileType 物件9297132
Ref: library/argparse filetype-objects9297244
Ref: 2b8a9297244
Ref: library/argparse argparse FileType9297295
Ref: ebf9297295
Node: Argument groups9298758
Ref: library/argparse argument-groups9298874
Ref: 2b8b9298874
Ref: library/argparse argparse ArgumentParser add_argument_group9298927
Ref: 2b8c9298927
Node: Mutual exclusion9301295
Ref: library/argparse mutual-exclusion9301411
Ref: 2b8d9301411
Ref: library/argparse argparse ArgumentParser add_mutually_exclusive_group9301466
Ref: 2b8e9301466
Node: Parser defaults9304189
Ref: library/argparse parser-defaults9304303
Ref: 2b8f9304303
Ref: library/argparse argparse ArgumentParser set_defaults9304356
Ref: 2b6c9304356
Ref: library/argparse argparse ArgumentParser get_default9305480
Ref: 2b909305480
Node: Printing help9305836
Ref: library/argparse printing-help9305949
Ref: 2b919305949
Ref: library/argparse argparse ArgumentParser print_usage9306178
Ref: 2b929306178
Ref: library/argparse argparse ArgumentParser print_help9306410
Ref: 2b939306410
Ref: library/argparse argparse ArgumentParser format_usage9306764
Ref: 18d09306764
Ref: library/argparse argparse ArgumentParser format_help9306943
Ref: 2b949306943
Node: Partial parsing9307156
Ref: library/argparse partial-parsing9307278
Ref: 2b959307278
Ref: library/argparse argparse ArgumentParser parse_known_args9307331
Ref: 2b969307331
Node: Customizing file parsing9308373
Ref: library/argparse customizing-file-parsing9308497
Ref: 2b979308497
Ref: library/argparse argparse ArgumentParser convert_arg_line_to_args9308568
Ref: 2b6b9308568
Node: Exiting methods9309473
Ref: library/argparse exiting-methods9309600
Ref: 2b989309600
Ref: library/argparse argparse ArgumentParser exit9309653
Ref: 2b999309653
Ref: library/argparse argparse ArgumentParser error9310185
Ref: 2b9a9310185
Node: Intermixed parsing9310373
Ref: library/argparse intermixed-parsing9310467
Ref: 2b9b9310467
Ref: library/argparse argparse ArgumentParser parse_intermixed_args9310526
Ref: aa39310526
Ref: library/argparse argparse ArgumentParser parse_known_intermixed_args9310614
Ref: 2b9c9310614
Node: Upgrading optparse code9312123
Ref: library/argparse id169312300
Ref: 2b9d9312300
Ref: library/argparse upgrading-optparse-code9312300
Ref: 11459312300
Node: Exceptions<3>9314823
Ref: library/argparse exceptions9314976
Ref: 2ba49314976
Ref: library/argparse argparse ArgumentError9315019
Ref: 2ba39315019
Ref: library/argparse argparse ArgumentTypeError9315260
Ref: 2b779315260
Node: logging --- Python 的日誌記錄工具9315388
Ref: library/logging doc9315615
Ref: 2ba59315615
Ref: library/logging logging-logging-facility-for-python9315615
Ref: 2ba69315615
Ref: library/logging module-logging9315615
Ref: 7b9315615
Ref: logging --- Python 的日誌記錄工具-Footnote-19319015
Node: Logger 物件9319092
Ref: library/logging logger9319205
Ref: 2ba79319205
Ref: library/logging logger-objects9319205
Ref: 2ba89319205
Ref: library/logging logging Logger9320351
Ref: af39320351
Ref: library/logging logging Logger name9320379
Ref: 2ba99320379
Ref: library/logging logging Logger level9320603
Ref: 2baa9320603
Ref: library/logging logging Logger parent9320895
Ref: 2bab9320895
Ref: library/logging logging Logger propagate9321155
Ref: 13fe9321155
Ref: library/logging logging Logger handlers9323190
Ref: 2bac9323190
Ref: library/logging logging Logger disabled9323566
Ref: 2baf9323566
Ref: library/logging logging Logger setLevel9323837
Ref: 13fc9323837
Ref: library/logging logging Logger isEnabledFor9325815
Ref: 12899325815
Ref: library/logging logging Logger getEffectiveLevel9326156
Ref: 2bb19326156
Ref: library/logging logging Logger getChild9326664
Ref: 12879326664
Ref: library/logging logging Logger getChildren9327165
Ref: 16cc9327165
Ref: library/logging logging Logger debug9327731
Ref: dd09327731
Ref: library/logging logging Logger info9333147
Ref: 2bb39333147
Ref: library/logging logging Logger warning9333332
Ref: 16009333332
Ref: library/logging logging Logger error9333764
Ref: 2bb59333764
Ref: library/logging logging Logger critical9333951
Ref: dcf9333951
Ref: library/logging logging Logger log9334155
Ref: dcd9334155
Ref: library/logging logging Logger exception9334351
Ref: dce9334351
Ref: library/logging logging Logger addFilter9334672
Ref: 2bb69334672
Ref: library/logging logging Logger removeFilter9334772
Ref: 2bb79334772
Ref: library/logging logging Logger filter9334875
Ref: 2bb89334875
Ref: library/logging logging Logger addHandler9335310
Ref: 2bad9335310
Ref: library/logging logging Logger removeHandler9335407
Ref: 2bae9335407
Ref: library/logging logging Logger findCaller9335512
Ref: 2bb99335512
Ref: library/logging logging Logger handle9336312
Ref: 2bba9336312
Ref: library/logging logging Logger makeRecord9336711
Ref: 2bbb9336711
Ref: library/logging logging Logger hasHandlers9336973
Ref: 2bbc9336973
Node: Logging Levels9337588
Ref: library/logging levels9337725
Ref: 6009337725
Ref: library/logging logging-levels9337725
Ref: 2bbd9337725
Ref: library/logging logging NOTSET9338400
Ref: 2bb09338400
Ref: library/logging logging DEBUG9339012
Ref: 1bf59339012
Ref: library/logging logging INFO9339349
Ref: 1bf69339349
Ref: library/logging logging WARNING9339598
Ref: 1bf79339598
Ref: library/logging logging ERROR9340105
Ref: 1bf89340105
Ref: library/logging logging CRITICAL9340423
Ref: 1bf99340423
Node: Handler Objects9340695
Ref: library/logging handler9340836
Ref: 2bbe9340836
Ref: library/logging handler-objects9340836
Ref: 2bbf9340836
Ref: library/logging logging Handler9341156
Ref: 13ff9341156
Ref: library/logging logging Handler __init__9341185
Ref: 2bc09341185
Ref: library/logging logging Handler createLock9341480
Ref: 2bc19341480
Ref: library/logging logging Handler acquire9341668
Ref: 2bc29341668
Ref: library/logging logging Handler release9341782
Ref: 2bc39341782
Ref: library/logging logging Handler setLevel9341884
Ref: 2bc49341884
Ref: library/logging logging Handler setFormatter9342458
Ref: 2bc59342458
Ref: library/logging logging Handler addFilter9342565
Ref: 2bc69342565
Ref: library/logging logging Handler removeFilter9342665
Ref: 2bc79342665
Ref: library/logging logging Handler filter9342773
Ref: 2bc89342773
Ref: library/logging logging Handler flush9343170
Ref: 2bc99343170
Ref: library/logging logging Handler close9343338
Ref: 2bca9343338
Ref: library/logging logging Handler handle9343696
Ref: 2bcc9343696
Ref: library/logging logging Handler handleError9343974
Ref: 2bcd9343974
Ref: library/logging logging Handler format9344776
Ref: 2bcf9344776
Ref: library/logging logging Handler emit9344944
Ref: 2bce9344944
Node: Formatter Objects9346475
Ref: library/logging formatter-objects9346616
Ref: 2bd09346616
Ref: library/logging id19346616
Ref: 2bd19346616
Ref: library/logging logging Formatter9346671
Ref: 14009346671
Ref: library/logging logging Formatter format9348844
Ref: 2bd49348844
Ref: library/logging logging Formatter formatTime9350315
Ref: 2bd29350315
Ref: library/logging logging Formatter formatException9352690
Ref: 2bd59352690
Ref: library/logging logging Formatter formatStack9353028
Ref: 2bd69353028
Ref: library/logging logging BufferingFormatter9353320
Ref: 2bd79353320
Ref: library/logging logging BufferingFormatter formatHeader9353739
Ref: 2bd89353739
Ref: library/logging logging BufferingFormatter formatFooter9354053
Ref: 2bd99354053
Ref: library/logging logging BufferingFormatter format9354358
Ref: 2bda9354358
Node: Filter Objects9354689
Ref: library/logging filter9354831
Ref: 2bdb9354831
Ref: library/logging filter-objects9354831
Ref: 2bdc9354831
Ref: library/logging logging Filter9355317
Ref: 11939355317
Ref: library/logging logging Filter filter9355609
Ref: 2bdd9355609
Node: LogRecord 物件9357996
Ref: library/logging log-record9358141
Ref: 2be09358141
Ref: library/logging logrecord-objects9358141
Ref: 2be19358141
Ref: library/logging logging LogRecord9358430
Ref: f899358430
Ref: library/logging logging LogRecord getMessage9360970
Ref: 2be49360970
Node: LogRecord attributes9362460
Ref: library/logging id29362611
Ref: 2be79362611
Ref: library/logging logrecord-attributes9362611
Ref: 2bb29362611
Node: LoggerAdapter 物件9371042
Ref: library/logging logger-adapter9371190
Ref: 2be89371190
Ref: library/logging loggeradapter-objects9371190
Ref: 2be99371190
Ref: library/logging logging LoggerAdapter9371467
Ref: 12889371467
Ref: library/logging logging LoggerAdapter process9372018
Ref: 2beb9372018
Ref: library/logging logging LoggerAdapter manager9372469
Ref: 2bec9372469
Ref: library/logging logging LoggerAdapter _log9372562
Ref: 2bed9372562
Node: Thread Safety9373714
Ref: library/logging thread-safety9373864
Ref: 2bee9373864
Node: Module-Level Functions9374520
Ref: library/logging module-level-functions9374673
Ref: 2bef9374673
Ref: library/logging logging getLogger9374831
Ref: 9049374831
Ref: library/logging logging getLoggerClass9375544
Ref: 2bf09375544
Ref: library/logging logging getLogRecordFactory9376020
Ref: 2be59376020
Ref: library/logging logging debug9376479
Ref: 2bb49376479
Ref: library/logging logging info9377369
Ref: 2bde9377369
Ref: library/logging logging warning9377576
Ref: 2d09377576
Ref: library/logging logging error9377999
Ref: 2bf29377999
Ref: library/logging logging critical9378208
Ref: 2bf39378208
Ref: library/logging logging exception9378423
Ref: 13fd9378423
Ref: library/logging logging log9378753
Ref: 2bf49378753
Ref: library/logging logging disable9378957
Ref: 2bf59378957
Ref: library/logging logging addLevelName9380163
Ref: 2bf69380163
Ref: library/logging logging getLevelNamesMapping9380821
Ref: 5ff9380821
Ref: library/logging logging getLevelName9381144
Ref: 2bf89381144
Ref: library/logging logging getHandlerByName9382773
Ref: 16dd9382773
Ref: library/logging logging getHandlerNames9382956
Ref: 15fa9382956
Ref: library/logging logging makeLogRecord9383084
Ref: 2be29383084
Ref: library/logging logging basicConfig9383447
Ref: 9a49383447
Ref: library/logging logging shutdown9388815
Ref: 2bcb9388815
Ref: library/logging logging setLoggerClass9389253
Ref: 2bf19389253
Ref: library/logging logging setLogRecordFactory9389867
Ref: 2be69389867
Ref: Module-Level Functions-Footnote-19391192
Node: Module-Level Attributes9391257
Ref: library/logging module-level-attributes9391433
Ref: 2bf99391433
Ref: library/logging logging lastResort9391502
Ref: 11929391502
Ref: library/logging logging raiseExceptions9392103
Ref: 11919392103
Node: Integration with the warnings module9392502
Ref: library/logging integration-with-the-warnings-module9392647
Ref: 2bfa9392647
Ref: library/logging logging captureWarnings9392868
Ref: 2bfb9392868
Ref: Integration with the warnings module-Footnote-19394255
Ref: Integration with the warnings module-Footnote-29394297
Node: logging config --- 日誌記錄配置9394350
Ref: library/logging config doc9394548
Ref: 2bfc9394548
Ref: library/logging config logging-config-logging-configuration9394548
Ref: 2bfd9394548
Ref: library/logging config module-logging config9394548
Ref: 7c9394548
Ref: logging config --- 日誌記錄配置-Footnote-19395179
Node: Configuration functions9395253
Ref: library/logging config configuration-functions9395382
Ref: 2bfe9395382
Ref: library/logging config logging-config-api9395382
Ref: 12849395382
Ref: library/logging config logging config dictConfig9395823
Ref: 11479395823
Ref: library/logging config logging config fileConfig9397938
Ref: af59397938
Ref: library/logging config logging config listen9400632
Ref: f089400632
Ref: library/logging config logging-eval-security9402282
Ref: 2c039402282
Ref: library/logging config logging config stopListening9403954
Ref: 2c029403954
Node: Security considerations9404196
Ref: library/logging config security-considerations9404365
Ref: 2c049404365
Node: Configuration dictionary schema9405083
Ref: library/logging config configuration-dictionary-schema9405254
Ref: 2c069405254
Ref: library/logging config logging-config-dictschema9405254
Ref: 2bff9405254
Node: Dictionary Schema Details9406257
Ref: library/logging config dictionary-schema-details9406384
Ref: 2c089406384
Ref: library/logging config logging-config-dictschema-formatters9407187
Ref: 2c099407187
Node: Incremental Configuration9412051
Ref: library/logging config incremental-configuration9412205
Ref: 2c0b9412205
Ref: library/logging config logging-config-dict-incremental9412205
Ref: 2c0a9412205
Node: Object connections9413650
Ref: library/logging config logging-config-dict-connections9413799
Ref: 2c079413799
Ref: library/logging config object-connections9413799
Ref: 2c0c9413799
Node: User-defined objects9416190
Ref: library/logging config logging-config-dict-userdef9416341
Ref: 2c059416341
Ref: library/logging config user-defined-objects9416341
Ref: 2c0d9416341
Node: Handler configuration order9420943
Ref: library/logging config handler-config-dict-order9421102
Ref: 2c0e9421102
Ref: library/logging config handler-configuration-order9421102
Ref: 2c0f9421102
Node: Access to external objects9422415
Ref: library/logging config access-to-external-objects9422580
Ref: 2c109422580
Ref: library/logging config logging-config-dict-externalobj9422580
Ref: 2c119422580
Node: Access to internal objects9423879
Ref: library/logging config access-to-internal-objects9424055
Ref: 2c129424055
Ref: library/logging config logging-config-dict-internalobj9424055
Ref: 2c139424055
Node: Import resolution and custom importers9427493
Ref: library/logging config import-resolution-and-custom-importers9427685
Ref: 2c159427685
Ref: library/logging config logging-import-resolution9427685
Ref: 2c169427685
Node: Configuring QueueHandler and QueueListener9428661
Ref: library/logging config configure-queue9428818
Ref: 14ce9428818
Ref: library/logging config configuring-queuehandler-and-queuelistener9428818
Ref: 2c179428818
Node: Configuration file format9432011
Ref: library/logging config configuration-file-format9432150
Ref: 2c1a9432150
Ref: library/logging config logging-config-fileformat9432150
Ref: 2c009432150
Node: logging handlers --- 日誌紀錄處理器9439496
Ref: library/logging handlers doc9439693
Ref: 2c1b9439693
Ref: library/logging handlers logging-handlers-logging-handlers9439693
Ref: 2c1c9439693
Ref: library/logging handlers module-logging handlers9439693
Ref: 7d9439693
Ref: logging handlers --- 日誌紀錄處理器-Footnote-19440757
Node: StreamHandler9440834
Ref: library/logging handlers stream-handler9440946
Ref: 2c1d9440946
Ref: library/logging handlers streamhandler9440946
Ref: 2c1e9440946
Ref: library/logging handlers logging StreamHandler9441260
Ref: 11909441260
Ref: library/logging handlers logging StreamHandler emit9441499
Ref: 2c1f9441499
Ref: library/logging handlers logging StreamHandler flush9441849
Ref: 2c219441849
Ref: library/logging handlers logging StreamHandler setStream9442142
Ref: af49442142
Ref: library/logging handlers logging StreamHandler terminator9442547
Ref: 2c209442547
Node: FileHandler9442956
Ref: library/logging handlers file-handler9443088
Ref: 2c229443088
Ref: library/logging handlers filehandler9443088
Ref: 2c239443088
Ref: library/logging handlers logging FileHandler9443323
Ref: 17a19443323
Ref: library/logging handlers logging FileHandler close9444132
Ref: 2c259444132
Ref: library/logging handlers logging FileHandler emit9444187
Ref: 2c249444187
Ref: FileHandler-Footnote-19444471
Node: NullHandler9444536
Ref: library/logging handlers null-handler9444673
Ref: 2c269444673
Ref: library/logging handlers nullhandler9444673
Ref: 2c279444673
Ref: library/logging handlers logging NullHandler9444930
Ref: 121c9444930
Ref: library/logging handlers logging NullHandler emit9445031
Ref: 2c289445031
Ref: library/logging handlers logging NullHandler handle9445100
Ref: 2c299445100
Ref: library/logging handlers logging NullHandler createLock9445171
Ref: 2c2a9445171
Node: WatchedFileHandler9445454
Ref: library/logging handlers watched-file-handler9445599
Ref: 2c2c9445599
Ref: library/logging handlers watchedfilehandler9445599
Ref: 2c2d9445599
Ref: library/logging handlers logging handlers WatchedFileHandler9446614
Ref: 2c2e9446614
Ref: library/logging handlers logging handlers WatchedFileHandler reopenIfNeeded9447435
Ref: c5d9447435
Ref: library/logging handlers logging handlers WatchedFileHandler emit9447728
Ref: 2c2f9447728
Node: BaseRotatingHandler9447896
Ref: library/logging handlers base-rotating-handler9448049
Ref: 2c309448049
Ref: library/logging handlers baserotatinghandler9448049
Ref: 2c319448049
Ref: library/logging handlers logging handlers BaseRotatingHandler9448436
Ref: 2c329448436
Ref: library/logging handlers logging handlers BaseRotatingHandler namer9448626
Ref: 2c339448626
Ref: library/logging handlers logging handlers BaseRotatingHandler rotator9450356
Ref: 2c369450356
Ref: library/logging handlers logging handlers BaseRotatingHandler rotation_filename9450638
Ref: 2c349450638
Ref: library/logging handlers logging handlers BaseRotatingHandler rotate9451185
Ref: 2c379451185
Node: RotatingFileHandler9452473
Ref: library/logging handlers rotating-file-handler9452632
Ref: 2c399452632
Ref: library/logging handlers rotatingfilehandler9452632
Ref: 2c3a9452632
Ref: library/logging handlers logging handlers RotatingFileHandler9452824
Ref: 14cb9452824
Ref: library/logging handlers logging handlers RotatingFileHandler doRollover9454776
Ref: 2c3c9454776
Ref: library/logging handlers logging handlers RotatingFileHandler emit9454856
Ref: 2c3b9454856
Node: TimedRotatingFileHandler9454988
Ref: library/logging handlers timed-rotating-file-handler9455141
Ref: 2c3d9455141
Ref: library/logging handlers timedrotatingfilehandler9455141
Ref: 2c3e9455141
Ref: library/logging handlers logging handlers TimedRotatingFileHandler9455374
Ref: f049455374
Ref: library/logging handlers logging handlers TimedRotatingFileHandler doRollover9460483
Ref: 2c409460483
Ref: library/logging handlers logging handlers TimedRotatingFileHandler emit9460563
Ref: 2c3f9460563
Ref: library/logging handlers logging handlers TimedRotatingFileHandler getFilesToDelete9460690
Ref: 2c359460690
Node: SocketHandler9460917
Ref: library/logging handlers socket-handler9461066
Ref: 2c419461066
Ref: library/logging handlers sockethandler9461066
Ref: 2c429461066
Ref: library/logging handlers logging handlers SocketHandler9461278
Ref: f059461278
Ref: library/logging handlers logging handlers SocketHandler close9461684
Ref: 2c439461684
Ref: library/logging handlers logging handlers SocketHandler emit9461741
Ref: 2c449461741
Ref: library/logging handlers logging handlers SocketHandler handleError9462174
Ref: 2c459462174
Ref: library/logging handlers logging handlers SocketHandler makeSocket9462404
Ref: 2c469462404
Ref: library/logging handlers logging handlers SocketHandler makePickle9462648
Ref: 2c479462648
Ref: library/logging handlers logging handlers SocketHandler send9463454
Ref: 2c489463454
Ref: library/logging handlers logging handlers SocketHandler createSocket9463775
Ref: 6039463775
Node: DatagramHandler9464971
Ref: library/logging handlers datagram-handler9465109
Ref: 2c499465109
Ref: library/logging handlers datagramhandler9465109
Ref: 2c4a9465109
Ref: library/logging handlers logging handlers DatagramHandler9465345
Ref: f069465345
Ref: library/logging handlers logging handlers DatagramHandler emit9466260
Ref: 2c4b9466260
Ref: library/logging handlers logging handlers DatagramHandler makeSocket9466612
Ref: 2c4c9466612
Ref: library/logging handlers logging handlers DatagramHandler send9466799
Ref: 2c4d9466799
Node: SysLogHandler9467014
Ref: library/logging handlers syslog-handler9467156
Ref: 2c4e9467156
Ref: library/logging handlers sysloghandler9467156
Ref: 2c4f9467156
Ref: library/logging handlers logging handlers SysLogHandler9467362
Ref: 6029467362
Ref: library/logging handlers logging handlers SysLogHandler close9469307
Ref: 2c509469307
Ref: library/logging handlers logging handlers SysLogHandler createSocket9469383
Ref: 6019469383
Ref: library/logging handlers logging handlers SysLogHandler emit9469832
Ref: 2c519469832
Ref: library/logging handlers logging handlers SysLogHandler encodePriority9471696
Ref: 2c529471696
Ref: library/logging handlers logging handlers SysLogHandler mapPriority9475724
Ref: 2c539475724
Ref: SysLogHandler-Footnote-19476210
Ref: SysLogHandler-Footnote-29476265
Ref: SysLogHandler-Footnote-39476330
Ref: SysLogHandler-Footnote-49476389
Node: NTEventLogHandler9476454
Ref: library/logging handlers nt-eventlog-handler9476592
Ref: 2c549476592
Ref: library/logging handlers nteventloghandler9476592
Ref: 2c559476592
Ref: library/logging handlers logging handlers NTEventLogHandler9476925
Ref: 2c569476925
Ref: library/logging handlers logging handlers NTEventLogHandler close9477987
Ref: 2c579477987
Ref: library/logging handlers logging handlers NTEventLogHandler emit9478389
Ref: 2c589478389
Ref: library/logging handlers logging handlers NTEventLogHandler getEventCategory9478547
Ref: 2c599478547
Ref: library/logging handlers logging handlers NTEventLogHandler getEventType9478749
Ref: 2c5a9478749
Ref: library/logging handlers logging handlers NTEventLogHandler getMessageID9479332
Ref: 2c5b9479332
Node: SMTPHandler9479762
Ref: library/logging handlers smtp-handler9479900
Ref: 2c5c9479900
Ref: library/logging handlers smtphandler9479900
Ref: 2c5d9479900
Ref: library/logging handlers logging handlers SMTPHandler9480097
Ref: 2c5e9480097
Ref: library/logging handlers logging handlers SMTPHandler emit9481347
Ref: 2c5f9481347
Ref: library/logging handlers logging handlers SMTPHandler getSubject9481451
Ref: 2c609481451
Node: MemoryHandler9481597
Ref: library/logging handlers memory-handler9481729
Ref: 2c619481729
Ref: library/logging handlers memoryhandler9481729
Ref: 2c629481729
Ref: library/logging handlers logging handlers BufferingHandler9482432
Ref: 2c639482432
Ref: library/logging handlers logging handlers BufferingHandler emit9482629
Ref: 2c649482629
Ref: library/logging handlers logging handlers BufferingHandler flush9482819
Ref: 2c669482819
Ref: library/logging handlers logging handlers BufferingHandler shouldFlush9483056
Ref: 2c659483056
Ref: library/logging handlers logging handlers MemoryHandler9483239
Ref: 2c149483239
Ref: library/logging handlers logging handlers MemoryHandler close9484045
Ref: 2c689484045
Ref: library/logging handlers logging handlers MemoryHandler flush9484173
Ref: 2c699484173
Ref: library/logging handlers logging handlers MemoryHandler setTarget9484480
Ref: 2c679484480
Ref: library/logging handlers logging handlers MemoryHandler shouldFlush9484570
Ref: 2c6a9484570
Node: HTTPHandler9484696
Ref: library/logging handlers http-handler9484829
Ref: 2c6b9484829
Ref: library/logging handlers httphandler9484829
Ref: 2c6c9484829
Ref: library/logging handlers logging handlers HTTPHandler9485060
Ref: dd19485060
Ref: library/logging handlers logging handlers HTTPHandler mapLogRecord9486007
Ref: 2c6d9486007
Ref: library/logging handlers logging handlers HTTPHandler emit9486461
Ref: 2c6e9486461
Node: QueueHandler9487197
Ref: library/logging handlers queue-handler9487330
Ref: 2c6f9487330
Ref: library/logging handlers queuehandler9487330
Ref: 2c709487330
Ref: library/logging handlers logging handlers QueueHandler9488071
Ref: 16dc9488071
Ref: library/logging handlers logging handlers QueueHandler emit9488748
Ref: 2c729488748
Ref: library/logging handlers logging handlers QueueHandler prepare9489251
Ref: 2c739489251
Ref: library/logging handlers logging handlers QueueHandler enqueue9491186
Ref: 2c719491186
Ref: library/logging handlers logging handlers QueueHandler listener9491432
Ref: 2c189491432
Node: QueueListener9491724
Ref: library/logging handlers queue-listener9491837
Ref: 2c749491837
Ref: library/logging handlers queuelistener9491837
Ref: 2c759491837
Ref: library/logging handlers logging handlers QueueListener9492859
Ref: dd29492859
Ref: library/logging handlers logging handlers QueueListener dequeue9494073
Ref: 2c769494073
Ref: library/logging handlers logging handlers QueueListener prepare9494354
Ref: 2c779494354
Ref: library/logging handlers logging handlers QueueListener handle9494671
Ref: 2c789494671
Ref: library/logging handlers logging handlers QueueListener start9494933
Ref: 2c799494933
Ref: library/logging handlers logging handlers QueueListener stop9495096
Ref: 2c7a9495096
Ref: library/logging handlers logging handlers QueueListener enqueue_sentinel9495403
Ref: 2c7b9495403
Node: getpass --- 可攜式密碼輸入工具9495901
Ref: library/getpass doc9496108
Ref: 2c7c9496108
Ref: library/getpass getpass-portable-password-input9496108
Ref: 2c7d9496108
Ref: library/getpass module-getpass9496108
Ref: 589496108
Ref: library/getpass getpass getpass9496522
Ref: 2c7e9496522
Ref: library/getpass getpass GetPassWarning9497437
Ref: 2c7f9497437
Ref: library/getpass getpass getuser9497563
Ref: 3519497563
Ref: getpass --- 可攜式密碼輸入工具-Footnote-19498266
Node: curses --- 字元儲存格顯示的終端處理9498333
Ref: library/curses doc9498554
Ref: 2c809498554
Ref: library/curses curses-terminal-handling-for-character-cell-displays9498554
Ref: 2c819498554
Ref: library/curses module-curses9498554
Ref: 239498554
Ref: curses --- 字元儲存格顯示的終端處理-Footnote-19500325
Node: 函式<5>9500388
Ref: library/curses curses-functions9500504
Ref: 2c839500504
Ref: library/curses functions9500504
Ref: 2c849500504
Ref: library/curses curses error9500598
Ref: 2c859500598
Ref: library/curses curses baudrate9500965
Ref: 2c879500965
Ref: library/curses curses beep9501315
Ref: 2c889501315
Ref: library/curses curses can_change_color9501379
Ref: 2c899501379
Ref: library/curses curses cbreak9501549
Ref: 2c8a9501549
Ref: library/curses curses color_content9502021
Ref: 7959502021
Ref: library/curses curses color_pair9502402
Ref: 2c8c9502402
Ref: library/curses curses curs_set9502787
Ref: 2c909502787
Ref: library/curses curses def_prog_mode9503205
Ref: 2c919503205
Ref: library/curses curses def_shell_mode9503523
Ref: 2c939503523
Ref: library/curses curses delay_output9503859
Ref: 2c959503859
Ref: library/curses curses doupdate9503947
Ref: 2c969503947
Ref: library/curses curses echo9504770
Ref: 2c9a9504770
Ref: library/curses curses endwin9504904
Ref: 2c9b9504904
Ref: library/curses curses erasechar9505005
Ref: 2c9c9505005
Ref: library/curses curses filter9505269
Ref: 2c9d9505269
Ref: library/curses curses flash9505878
Ref: 2c9f9505878
Ref: library/curses curses flushinp9506135
Ref: 2ca09506135
Ref: library/curses curses getmouse9506319
Ref: 2ca19506319
Ref: library/curses curses getsyx9507314
Ref: 2cac9507314
Ref: library/curses curses getwin9507523
Ref: 2cae9507523
Ref: library/curses curses has_colors9507776
Ref: 2cb09507776
Ref: library/curses curses has_extended_color_support9507906
Ref: 7999507906
Ref: library/curses curses has_ic9508290
Ref: 2cb19508290
Ref: library/curses curses has_il9508544
Ref: 2cb29508544
Ref: library/curses curses has_key9508839
Ref: 2cb39508839
Ref: library/curses curses halfdelay9508991
Ref: 2cb49508991
Ref: library/curses curses init_color9509427
Ref: 7969509427
Ref: library/curses curses init_pair9510081
Ref: 7979510081
Ref: library/curses curses initscr9510800
Ref: 2c9e9510800
Ref: library/curses curses is_term_resized9511075
Ref: 2cb89511075
Ref: library/curses curses isendwin9511244
Ref: 2cba9511244
Ref: library/curses curses keyname9511400
Ref: 2cbb9511400
Ref: library/curses curses killchar9511925
Ref: 2cbc9511925
Ref: library/curses curses longname9512192
Ref: 2cbd9512192
Ref: library/curses curses meta9512465
Ref: 2cbe9512465
Ref: library/curses curses mouseinterval9512620
Ref: 2cbf9512620
Ref: library/curses curses mousemask9512925
Ref: 2cc09512925
Ref: library/curses curses napms9513341
Ref: 2cc19513341
Ref: library/curses curses newpad9513407
Ref: 2cc29513407
Ref: library/curses curses newwin9514493
Ref: 2cc39514493
Ref: library/curses curses nl9514856
Ref: 2cc49514856
Ref: library/curses curses nocbreak9515069
Ref: 2cb59515069
Ref: library/curses curses noecho9515184
Ref: 2cc59515184
Ref: library/curses curses nonl9515281
Ref: 2cc69515281
Ref: library/curses curses noqiflush9515772
Ref: 2cc79515772
Ref: library/curses curses noraw9516160
Ref: 2cc89516160
Ref: library/curses curses pair_content9516269
Ref: 7989516269
Ref: library/curses curses pair_number9516493
Ref: 2c8f9516493
Ref: library/curses curses putp9516683
Ref: 2cc99516683
Ref: library/curses curses qiflush9516927
Ref: 2cca9516927
Ref: library/curses curses raw9517191
Ref: 2c8b9517191
Ref: library/curses curses reset_prog_mode9517431
Ref: 2c929517431
Ref: library/curses curses reset_shell_mode9517573
Ref: 2c949517573
Ref: library/curses curses resetty9517715
Ref: 2ccb9517715
Ref: library/curses curses resize_term9517855
Ref: 2cb99517855
Ref: library/curses curses resizeterm9518392
Ref: 2ccd9518392
Ref: library/curses curses savetty9518663
Ref: 2ccc9518663
Ref: library/curses curses get_escdelay9518796
Ref: 8959518796
Ref: library/curses curses set_escdelay9518920
Ref: 8969518920
Ref: library/curses curses get_tabsize9519216
Ref: 8979519216
Ref: library/curses curses set_tabsize9519338
Ref: 8989519338
Ref: library/curses curses setsyx9519549
Ref: 2cce9519549
Ref: library/curses curses setupterm9519717
Ref: 2ccf9519717
Ref: library/curses curses start_color9520132
Ref: 2cd09520132
Ref: library/curses curses termattrs9520823
Ref: 2cd39520823
Ref: library/curses curses termname9521051
Ref: 2cd49521051
Ref: library/curses curses tigetflag9521198
Ref: 2cd59521198
Ref: library/curses curses tigetnum9521512
Ref: 2cd69521512
Ref: library/curses curses tigetstr9521826
Ref: 2cd79521826
Ref: library/curses curses tparm9522130
Ref: 2cd89522130
Ref: library/curses curses typeahead9522465
Ref: 2cd99522465
Ref: library/curses curses unctrl9523052
Ref: 2cda9523052
Ref: library/curses curses ungetch9523331
Ref: 2cdb9523331
Ref: library/curses curses update_lines_cols9523508
Ref: d929523508
Ref: library/curses curses unget_wch9523702
Ref: 10399523702
Ref: library/curses curses ungetmouse9523923
Ref: 2cdc9523923
Ref: library/curses curses use_env9524087
Ref: 2cdd9524087
Ref: library/curses curses use_default_colors9524595
Ref: 2cb69524595
Ref: library/curses curses wrapper9525026
Ref: a239525026
Node: Window Objects9525846
Ref: library/curses curses-window-objects9525980
Ref: 2cb79525980
Ref: library/curses window-objects9525980
Ref: 2cde9525980
Ref: library/curses curses window addch9526160
Ref: 2cdf9526160
Ref: library/curses curses window addnstr9526765
Ref: 2ce09526765
Ref: library/curses curses window addstr9527024
Ref: 2c989527024
Ref: library/curses curses window attroff9528026
Ref: 2ce19528026
Ref: library/curses curses window attron9528167
Ref: 2ce29528167
Ref: library/curses curses window attrset9528304
Ref: 2ce39528304
Ref: library/curses curses window bkgd9528448
Ref: 2ce49528448
Ref: library/curses curses window bkgdset9528893
Ref: 2ce59528893
Ref: library/curses curses window border9529453
Ref: 2ce69529453
Ref: library/curses curses window box9531457
Ref: 2ced9531457
Ref: library/curses curses window chgat9531685
Ref: 2cee9531685
Ref: library/curses curses window clear9532309
Ref: 2cf09532309
Ref: library/curses curses window clearok9532464
Ref: 2cf29532464
Ref: library/curses curses window clrtobot9532609
Ref: 2cf39532609
Ref: library/curses curses window clrtoeol9532806
Ref: 2cf49532806
Ref: library/curses curses window cursyncup9532886
Ref: 2cf59532886
Ref: library/curses curses window delch9533054
Ref: 2cf69533054
Ref: library/curses curses window deleteln9533133
Ref: 2cf79533133
Ref: library/curses curses window derwin9533257
Ref: 2cf89533257
Ref: library/curses curses window echochar9533663
Ref: 2cfa9533663
Ref: library/curses curses window enclose9533817
Ref: 17da9533817
Ref: library/curses curses window encoding9534235
Ref: 10379534235
Ref: library/curses curses window erase9534613
Ref: 2cf19534613
Ref: library/curses curses window getbegyx9534666
Ref: 2cfb9534666
Ref: library/curses curses window getbkgd9534769
Ref: 2cfc9534769
Ref: library/curses curses window getch9534882
Ref: 2ca29534882
Ref: library/curses curses window get_wch9535202
Ref: 10389535202
Ref: library/curses curses window getkey9535470
Ref: 2cfd9535470
Ref: library/curses curses window getmaxyx9535778
Ref: 2cfe9535778
Ref: library/curses curses window getparyx9535883
Ref: 2cff9535883
Ref: library/curses curses window getstr9536087
Ref: 2d009536087
Ref: library/curses curses window getyx9536303
Ref: 2d019536303
Ref: library/curses curses window hline9536442
Ref: 2d029536442
Ref: library/curses curses window idcok9536628
Ref: 2d039536628
Ref: library/curses curses window idlok9536974
Ref: 2d049536974
Ref: library/curses curses window immedok9537167
Ref: 2d059537167
Ref: library/curses curses window inch9537516
Ref: 2d069537516
Ref: library/curses curses window insch9537704
Ref: 2d079537704
Ref: library/curses curses window insdelln9537918
Ref: 2d089537918
Ref: library/curses curses window insertln9538297
Ref: 2d099538297
Ref: library/curses curses window insnstr9538427
Ref: 2d0a9538427
Ref: library/curses curses window insstr9538940
Ref: 2d0b9538940
Ref: library/curses curses window instr9539359
Ref: 2d0c9539359
Ref: library/curses curses window is_linetouched9539755
Ref: 2d0d9539755
Ref: library/curses curses window is_wintouched9540038
Ref: 2d0e9540038
Ref: library/curses curses window keypad9540218
Ref: 2d0f9540218
Ref: library/curses curses window leaveok9540486
Ref: 2cad9540486
Ref: library/curses curses window move9540830
Ref: 2d109540830
Ref: library/curses curses window mvderwin9540913
Ref: 2d119540913
Ref: library/curses curses window mvwin9541190
Ref: 2d129541190
Ref: library/curses curses window nodelay9541306
Ref: 2d139541306
Ref: library/curses curses window notimeout9541415
Ref: 2d149541415
Ref: library/curses curses window noutrefresh9541679
Ref: 2c979541679
Ref: library/curses curses window overlay9541953
Ref: 2d159541953
Ref: library/curses curses window overwrite9542602
Ref: 2d169542602
Ref: library/curses curses window putwin9543254
Ref: 2caf9543254
Ref: library/curses curses window redrawln9543460
Ref: 2d179543460
Ref: library/curses curses window redrawwin9543666
Ref: 2d189543666
Ref: library/curses curses window refresh9543812
Ref: 2c999543812
Ref: library/curses curses window resize9544833
Ref: 2d199544833
Ref: library/curses curses window scroll9545183
Ref: 2d1a9545183
Ref: library/curses curses window scrollok9545291
Ref: 2d1b9545291
Ref: library/curses curses window setscrreg9545827
Ref: 2d1c9545827
Ref: library/curses curses window standend9545996
Ref: 2d1d9545996
Ref: library/curses curses window standout9546147
Ref: 2d1e9546147
Ref: library/curses curses window subpad9546217
Ref: 2d1f9546217
Ref: library/curses curses window subwin9546456
Ref: 2cf99546456
Ref: library/curses curses window syncdown9546814
Ref: 2d209546814
Ref: library/curses curses window syncok9547060
Ref: 2d219547060
Ref: library/curses curses window syncup9547223
Ref: 2d229547223
Ref: library/curses curses window timeout9547349
Ref: 2d239547349
Ref: library/curses curses window touchline9547852
Ref: 2cef9547852
Ref: library/curses curses window touchwin9548160
Ref: 2d249548160
Ref: library/curses curses window untouchwin9548285
Ref: 2d259548285
Ref: library/curses curses window vline9548418
Ref: 168c9548418
Ref: Window Objects-Footnote-19548677
Node: Constants9548720
Ref: library/curses constants9548836
Ref: 2d269548836
Ref: library/curses curses ERR9548941
Ref: 2d279548941
Ref: library/curses curses OK9549088
Ref: 2d289549088
Ref: library/curses curses version9549233
Ref: 2d299549233
Ref: library/curses curses __version__9549261
Ref: 2d2a9549261
Ref: library/curses curses ncurses_version9549362
Ref: 98b9549362
Ref: library/curses curses COLORS9549783
Ref: 2cd19549783
Ref: library/curses curses COLOR_PAIRS9549941
Ref: 2cd29549941
Ref: library/curses curses COLS9550109
Ref: 16099550109
Ref: library/curses curses LINES9550371
Ref: 16089550371
Ref: library/curses curses A_ALTCHARSET9550927
Ref: 2d2b9550927
Ref: library/curses curses A_BLINK9551033
Ref: 2d2c9551033
Ref: library/curses curses A_BOLD9551134
Ref: 2d2d9551134
Ref: library/curses curses A_DIM9551234
Ref: 2d2e9551234
Ref: library/curses curses A_INVIS9551336
Ref: 2d2f9551336
Ref: library/curses curses A_ITALIC9551452
Ref: 2d309551452
Ref: library/curses curses A_NORMAL9551555
Ref: 2c869551555
Ref: library/curses curses A_PROTECT9551664
Ref: 2d319551664
Ref: library/curses curses A_REVERSE9551770
Ref: 2c8e9551770
Ref: library/curses curses A_STANDOUT9551914
Ref: 2c8d9551914
Ref: library/curses curses A_UNDERLINE9551990
Ref: 2d329551990
Ref: library/curses curses A_HORIZONTAL9552067
Ref: 2d339552067
Ref: library/curses curses A_LEFT9552164
Ref: 2d349552164
Ref: library/curses curses A_LOW9552269
Ref: 2d359552269
Ref: library/curses curses A_RIGHT9552376
Ref: 2d369552376
Ref: library/curses curses A_TOP9552481
Ref: 2d379552481
Ref: library/curses curses A_VERTICAL9552573
Ref: 2d389552573
Ref: library/curses curses A_ATTRIBUTES9552964
Ref: 2d399552964
Ref: library/curses curses A_CHARTEXT9553077
Ref: 2d3a9553077
Ref: library/curses curses A_COLOR9553200
Ref: 2d3b9553200
Ref: library/curses curses KEY_MIN9553650
Ref: 2d3c9553650
Ref: library/curses curses KEY_BREAK9553764
Ref: 2d3d9553764
Ref: library/curses curses KEY_DOWN9553880
Ref: 2d3e9553880
Ref: library/curses curses KEY_UP9553983
Ref: 2d3f9553983
Ref: library/curses curses KEY_LEFT9554088
Ref: 2d409554088
Ref: library/curses curses KEY_RIGHT9554194
Ref: 2d419554194
Ref: library/curses curses KEY_HOME9554299
Ref: 2d429554299
Ref: library/curses curses KEY_BACKSPACE9554406
Ref: 2d439554406
Ref: library/curses curses KEY_F09554507
Ref: 2d449554507
Ref: library/curses curses KEY_Fn9554685
Ref: 2d459554685
Ref: library/curses curses KEY_DL9554805
Ref: 2d469554805
Ref: library/curses curses KEY_IL9554911
Ref: 2d479554911
Ref: library/curses curses KEY_DC9555017
Ref: 2d489555017
Ref: library/curses curses KEY_IC9555128
Ref: 2d499555128
Ref: library/curses curses KEY_EIC9555256
Ref: 2d4a9555256
Ref: library/curses curses KEY_CLEAR9555374
Ref: 2d4b9555374
Ref: library/curses curses KEY_EOS9555479
Ref: 2d4c9555479
Ref: library/curses curses KEY_EOL9555596
Ref: 2d4d9555596
Ref: library/curses curses KEY_SF9555710
Ref: 2d4e9555710
Ref: library/curses curses KEY_SR9555826
Ref: 2d4f9555826
Ref: library/curses curses KEY_NPAGE9555956
Ref: 2d509555956
Ref: library/curses curses KEY_PPAGE9556060
Ref: 2d519556060
Ref: library/curses curses KEY_STAB9556167
Ref: 2d529556167
Ref: library/curses curses KEY_CTAB9556269
Ref: 2d539556269
Ref: library/curses curses KEY_CATAB9556374
Ref: 2d549556374
Ref: library/curses curses KEY_ENTER9556483
Ref: 2d559556483
Ref: library/curses curses KEY_SRESET9556605
Ref: 2d569556605
Ref: library/curses curses KEY_RESET9556732
Ref: 2d579556732
Ref: library/curses curses KEY_PRINT9556859
Ref: 2d589556859
Ref: library/curses curses KEY_LL9556956
Ref: 2d599556956
Ref: library/curses curses KEY_A19557083
Ref: 2d5a9557083
Ref: library/curses curses KEY_A39557198
Ref: 2d5b9557198
Ref: library/curses curses KEY_B29557314
Ref: 2d5c9557314
Ref: library/curses curses KEY_C19557425
Ref: 2d5d9557425
Ref: library/curses curses KEY_C39557540
Ref: 2d5e9557540
Ref: library/curses curses KEY_BTAB9557658
Ref: 2d5f9557658
Ref: library/curses curses KEY_BEG9557760
Ref: 2d609557760
Ref: library/curses curses KEY_CANCEL9557873
Ref: 2d619557873
Ref: library/curses curses KEY_CLOSE9557973
Ref: 2d629557973
Ref: library/curses curses KEY_COMMAND9558056
Ref: 2d639558056
Ref: library/curses curses KEY_COPY9558150
Ref: 2d649558150
Ref: library/curses curses KEY_CREATE9558251
Ref: 2d659558251
Ref: library/curses curses KEY_END9558349
Ref: 2d669558349
Ref: library/curses curses KEY_EXIT9558448
Ref: 2d679558448
Ref: library/curses curses KEY_FIND9558547
Ref: 2d689558547
Ref: library/curses curses KEY_HELP9558646
Ref: 2d699558646
Ref: library/curses curses KEY_MARK9558745
Ref: 2d6a9558745
Ref: library/curses curses KEY_MESSAGE9558828
Ref: 2d6b9558828
Ref: library/curses curses KEY_MOVE9558916
Ref: 2d6c9558916
Ref: library/curses curses KEY_NEXT9559015
Ref: 2d6d9559015
Ref: library/curses curses KEY_OPEN9559114
Ref: 2d6e9559114
Ref: library/curses curses KEY_OPTIONS9559197
Ref: 2d6f9559197
Ref: library/curses curses KEY_PREVIOUS9559269
Ref: 2d709559269
Ref: library/curses curses KEY_REDO9559365
Ref: 2d719559365
Ref: library/curses curses KEY_REFERENCE9559448
Ref: 2d729559448
Ref: library/curses curses KEY_REFRESH9559528
Ref: 2d739559528
Ref: library/curses curses KEY_REPLACE9559600
Ref: 2d749559600
Ref: library/curses curses KEY_RESTART9559672
Ref: 2d759559672
Ref: library/curses curses KEY_RESUME9559762
Ref: 2d769559762
Ref: library/curses curses KEY_SAVE9559861
Ref: 2d779559861
Ref: library/curses curses KEY_SBEG9559960
Ref: 2d789559960
Ref: library/curses curses KEY_SCANCEL9560062
Ref: 2d799560062
Ref: library/curses curses KEY_SCOMMAND9560141
Ref: 2d7a9560141
Ref: library/curses curses KEY_SCOPY9560238
Ref: 2d7b9560238
Ref: library/curses curses KEY_SCREATE9560328
Ref: 2d7c9560328
Ref: library/curses curses KEY_SDC9560422
Ref: 2d7d9560422
Ref: library/curses curses KEY_SDL9560536
Ref: 2d7e9560536
Ref: library/curses curses KEY_SELECT9560653
Ref: 2d7f9560653
Ref: library/curses curses KEY_SEND9560752
Ref: 2d809560752
Ref: library/curses curses KEY_SEOL9560858
Ref: 2d819560858
Ref: library/curses curses KEY_SEXIT9560972
Ref: 2d829560972
Ref: library/curses curses KEY_SFIND9561079
Ref: 2d839561079
Ref: library/curses curses KEY_SHELP9561186
Ref: 2d849561186
Ref: library/curses curses KEY_SHOME9561293
Ref: 2d859561293
Ref: library/curses curses KEY_SIC9561398
Ref: 2d869561398
Ref: library/curses curses KEY_SLEFT9561508
Ref: 2d879561508
Ref: library/curses curses KEY_SMESSAGE9561604
Ref: 2d889561604
Ref: library/curses curses KEY_SMOVE9561701
Ref: 2d899561701
Ref: library/curses curses KEY_SNEXT9561808
Ref: 2d8a9561808
Ref: library/curses curses KEY_SOPTIONS9561898
Ref: 2d8b9561898
Ref: library/curses curses KEY_SPREVIOUS9561978
Ref: 2d8c9561978
Ref: library/curses curses KEY_SPRINT9562073
Ref: 2d8d9562073
Ref: library/curses curses KEY_SREDO9562180
Ref: 2d8e9562180
Ref: library/curses curses KEY_SREPLACE9562270
Ref: 2d8f9562270
Ref: library/curses curses KEY_SRIGHT9562368
Ref: 2d909562368
Ref: library/curses curses KEY_SRSUME9562482
Ref: 2d919562482
Ref: library/curses curses KEY_SSAVE9562590
Ref: 2d929562590
Ref: library/curses curses KEY_SSUSPEND9562680
Ref: 2d939562680
Ref: library/curses curses KEY_SUNDO9562777
Ref: 2d949562777
Ref: library/curses curses KEY_SUSPEND9562867
Ref: 2d959562867
Ref: library/curses curses KEY_UNDO9562955
Ref: 2d969562955
Ref: library/curses curses KEY_MOUSE9563055
Ref: 2ca39563055
Ref: library/curses curses KEY_RESIZE9563175
Ref: 2d979563175
Ref: library/curses curses KEY_MAX9563288
Ref: 2d989563288
Ref: library/curses curses-acs-codes9564491
Ref: 2d999564491
Ref: library/curses curses ACS_BBSS9565071
Ref: 2d9a9565071
Ref: library/curses curses ACS_BLOCK9565201
Ref: 2d9b9565201
Ref: library/curses curses ACS_BOARD9565311
Ref: 2d9c9565311
Ref: library/curses curses ACS_BSBS9565418
Ref: 2d9d9565418
Ref: library/curses curses ACS_BSSB9565544
Ref: 2d9e9565544
Ref: library/curses curses ACS_BSSS9565672
Ref: 2d9f9565672
Ref: library/curses curses ACS_BTEE9565790
Ref: 2da09565790
Ref: library/curses curses ACS_BULLET9565876
Ref: 2da19565876
Ref: library/curses curses ACS_CKBOARD9565945
Ref: 2da29565945
Ref: library/curses curses ACS_DARROW9566031
Ref: 2da39566031
Ref: library/curses curses ACS_DEGREE9566113
Ref: 2da49566113
Ref: library/curses curses ACS_DIAMOND9566189
Ref: 2da59566189
Ref: library/curses curses ACS_GEQUAL9566259
Ref: 2da69566259
Ref: library/curses curses ACS_HLINE9566363
Ref: 2ce89566363
Ref: library/curses curses ACS_LANTERN9566453
Ref: 2da79566453
Ref: library/curses curses ACS_LARROW9566530
Ref: 2da89566530
Ref: library/curses curses ACS_LEQUAL9566603
Ref: 2da99566603
Ref: library/curses curses ACS_LLCORNER9566687
Ref: 2ceb9566687
Ref: library/curses curses ACS_LRCORNER9566772
Ref: 2cec9566772
Ref: library/curses curses ACS_LTEE9566874
Ref: 2daa9566874
Ref: library/curses curses ACS_NEQUAL9566958
Ref: 2dab9566958
Ref: library/curses curses ACS_PI9567049
Ref: 2dac9567049
Ref: library/curses curses ACS_PLMINUS9567136
Ref: 2dad9567136
Ref: library/curses curses ACS_PLUS9567233
Ref: 2dae9567233
Ref: library/curses curses ACS_RARROW9567322
Ref: 2daf9567322
Ref: library/curses curses ACS_RTEE9567412
Ref: 2db09567412
Ref: library/curses curses ACS_S19567511
Ref: 2db19567511
Ref: library/curses curses ACS_S39567614
Ref: 2db29567614
Ref: library/curses curses ACS_S79567717
Ref: 2db39567717
Ref: library/curses curses ACS_S99567820
Ref: 2db49567820
Ref: library/curses curses ACS_SBBS9567925
Ref: 2db59567925
Ref: library/curses curses ACS_SBSB9568054
Ref: 2db69568054
Ref: library/curses curses ACS_SBSS9568178
Ref: 2db79568178
Ref: library/curses curses ACS_SSBB9568298
Ref: 2db89568298
Ref: library/curses curses ACS_SSBS9568426
Ref: 2db99568426
Ref: library/curses curses ACS_SSSB9568547
Ref: 2dba9568547
Ref: library/curses curses ACS_SSSS9568666
Ref: 2dbb9568666
Ref: library/curses curses ACS_STERLING9568782
Ref: 2dbc9568782
Ref: library/curses curses ACS_TTEE9568875
Ref: 2dbd9568875
Ref: library/curses curses ACS_UARROW9568958
Ref: 2dbe9568958
Ref: library/curses curses ACS_ULCORNER9569029
Ref: 2ce99569029
Ref: library/curses curses ACS_URCORNER9569109
Ref: 2cea9569109
Ref: library/curses curses ACS_VLINE9569207
Ref: 2ce79569207
Ref: library/curses curses BUTTONn_PRESSED9569588
Ref: 2ca49569588
Ref: library/curses curses BUTTONn_RELEASED9569735
Ref: 2ca59569735
Ref: library/curses curses BUTTONn_CLICKED9569881
Ref: 2ca69569881
Ref: library/curses curses BUTTONn_DOUBLE_CLICKED9570004
Ref: 2ca79570004
Ref: library/curses curses BUTTONn_TRIPLE_CLICKED9570118
Ref: 2ca89570118
Ref: library/curses curses BUTTON_SHIFT9570252
Ref: 2ca99570252
Ref: library/curses curses BUTTON_CTRL9570414
Ref: 2caa9570414
Ref: library/curses curses BUTTON_ALT9570578
Ref: 2cab9570578
Ref: library/curses curses COLOR_BLACK9571024
Ref: 2dbf9571024
Ref: library/curses curses COLOR_BLUE9571110
Ref: 2dc09571110
Ref: library/curses curses COLOR_CYAN9571208
Ref: 2dc19571208
Ref: library/curses curses COLOR_GREEN9571311
Ref: 2dc29571311
Ref: library/curses curses COLOR_MAGENTA9571379
Ref: 2dc39571379
Ref: library/curses curses COLOR_RED9571483
Ref: 2dc49571483
Ref: library/curses curses COLOR_WHITE9571564
Ref: 2dc59571564
Ref: library/curses curses COLOR_YELLOW9571632
Ref: 2dc69571632
Node: curses textpad --- Text input widget for curses programs9571692
Ref: library/curses curses-textpad-text-input-widget-for-curses-programs9571918
Ref: 2dc79571918
Ref: library/curses module-curses textpad9571918
Ref: 269571918
Ref: library/curses curses textpad rectangle9572508
Ref: 2dc99572508
Node: Textbox objects9573229
Ref: library/curses curses-textpad-objects9573337
Ref: 2dca9573337
Ref: library/curses textbox-objects9573337
Ref: 2dcb9573337
Ref: library/curses curses textpad Textbox9573453
Ref: 2dc89573453
Ref: library/curses curses textpad Textbox edit9573931
Ref: 2dcd9573931
Ref: library/curses curses textpad Textbox do_command9574502
Ref: 2dce9574502
Ref: library/curses curses textpad Textbox gather9578150
Ref: 2dcf9578150
Ref: library/curses curses textpad Textbox stripspaces9578343
Ref: 2dcc9578343
Node: curses ascii --- ASCII 字元的工具程式9578751
Ref: library/curses ascii doc9578975
Ref: 2dd09578975
Ref: library/curses ascii curses-ascii-utilities-for-ascii-characters9578975
Ref: 2dd19578975
Ref: library/curses ascii module-curses ascii9578975
Ref: 249578975
Ref: library/curses ascii curses ascii NUL9579560
Ref: 2dd29579560
Ref: library/curses ascii curses ascii SOH9579600
Ref: 2dd39579600
Ref: library/curses ascii curses ascii STX9579686
Ref: 2dd49579686
Ref: library/curses ascii curses ascii ETX9579750
Ref: 2dd59579750
Ref: library/curses ascii curses ascii EOT9579812
Ref: 2dd69579812
Ref: library/curses ascii curses ascii ENQ9579882
Ref: 2dd79579882
Ref: library/curses ascii curses ascii ACK9579981
Ref: 2dd89579981
Ref: library/curses ascii curses ascii BEL9580047
Ref: 2dd99580047
Ref: library/curses ascii curses ascii BS9580102
Ref: 2dda9580102
Ref: library/curses ascii curses ascii TAB9580161
Ref: 2ddb9580161
Ref: library/curses ascii curses ascii HT9580215
Ref: 2ddc9580215
Ref: library/curses ascii curses ascii LF9580309
Ref: 2ddd9580309
Ref: library/curses ascii curses ascii NL9580368
Ref: 2dde9580368
Ref: library/curses ascii curses ascii VT9580455
Ref: 2ddf9580455
Ref: library/curses ascii curses ascii FF9580517
Ref: 2de09580517
Ref: library/curses ascii curses ascii CR9580576
Ref: 2de19580576
Ref: library/curses ascii curses ascii SO9580641
Ref: 2de29580641
Ref: library/curses ascii curses ascii SI9580731
Ref: 2de39580731
Ref: library/curses ascii curses ascii DLE9580819
Ref: 2de49580819
Ref: library/curses ascii curses ascii DC19580886
Ref: 2de59580886
Ref: library/curses ascii curses ascii DC29580958
Ref: 2de69580958
Ref: library/curses ascii curses ascii DC39581050
Ref: 2de79581050
Ref: library/curses ascii curses ascii DC49581123
Ref: 2de89581123
Ref: library/curses ascii curses ascii NAK9581190
Ref: 2de99581190
Ref: library/curses ascii curses ascii SYN9581265
Ref: 2dea9581265
Ref: library/curses ascii curses ascii ETB9581332
Ref: 2deb9581332
Ref: library/curses ascii curses ascii CAN9581405
Ref: 2dec9581405
Ref: library/curses ascii curses ascii EM9581462
Ref: 2ded9581462
Ref: library/curses ascii curses ascii SUB9581525
Ref: 2dee9581525
Ref: library/curses ascii curses ascii ESC9581586
Ref: 2def9581586
Ref: library/curses ascii curses ascii FS9581643
Ref: 2df09581643
Ref: library/curses ascii curses ascii GS9581707
Ref: 2df19581707
Ref: library/curses ascii curses ascii RS9581772
Ref: 2df29581772
Ref: library/curses ascii curses ascii US9581861
Ref: 2df39581861
Ref: library/curses ascii curses ascii SP9581925
Ref: 2df49581925
Ref: library/curses ascii curses ascii DEL9581980
Ref: 2df59581980
Ref: library/curses ascii curses ascii isalnum9582278
Ref: 2df69582278
Ref: library/curses ascii curses ascii isalpha9582423
Ref: 2df79582423
Ref: library/curses ascii curses ascii isascii9582566
Ref: 2df89582566
Ref: library/curses ascii curses ascii isblank9582673
Ref: 2df99582673
Ref: library/curses ascii curses ascii iscntrl9582784
Ref: 2dfa9582784
Ref: library/curses ascii curses ascii isdigit9582908
Ref: 2dfb9582908
Ref: library/curses ascii curses ascii isgraph9583070
Ref: 2dfc9583070
Ref: library/curses ascii curses ascii islower9583169
Ref: 2dfd9583169
Ref: library/curses ascii curses ascii isprint9583255
Ref: 2dfe9583255
Ref: library/curses ascii curses ascii ispunct9583357
Ref: 2dff9583357
Ref: library/curses ascii curses ascii isspace9583498
Ref: 2e009583498
Ref: library/curses ascii curses ascii isupper9583664
Ref: 2e019583664
Ref: library/curses ascii curses ascii isxdigit9583746
Ref: 2e029583746
Ref: library/curses ascii curses ascii isctrl9583887
Ref: 2e039583887
Ref: library/curses ascii curses ascii ismeta9583994
Ref: 2e049583994
Ref: library/curses ascii curses ascii ascii9584590
Ref: 2e059584590
Ref: library/curses ascii curses ascii ctrl9584695
Ref: 2e069584695
Ref: library/curses ascii curses ascii alt9584861
Ref: 2e079584861
Ref: library/curses ascii curses ascii unctrl9585131
Ref: 2e089585131
Ref: library/curses ascii curses ascii controlnames9585682
Ref: 2e099585682
Ref: curses ascii --- ASCII 字元的工具程式-Footnote-19585966
Node: curses panel --- curses 的面板堆疊擴充9586038
Ref: library/curses panel doc9586255
Ref: 2e0a9586255
Ref: library/curses panel curses-panel-a-panel-stack-extension-for-curses9586255
Ref: 2e0b9586255
Ref: library/curses panel module-curses panel9586255
Ref: 259586255
Node: 函式<6>9586708
Ref: library/curses panel cursespanel-functions9586821
Ref: 2e0c9586821
Ref: library/curses panel functions9586821
Ref: 2e0d9586821
Ref: library/curses panel curses panel bottom_panel9586923
Ref: 2e0e9586923
Ref: library/curses panel curses panel new_panel9587016
Ref: 2e0f9587016
Ref: library/curses panel curses panel top_panel9587314
Ref: 2e109587314
Ref: library/curses panel curses panel update_panels9587401
Ref: 2e119587401
Node: Panel Objects9587608
Ref: library/curses panel curses-panel-objects9587721
Ref: 2e129587721
Ref: library/curses panel panel-objects9587721
Ref: 2e139587721
Ref: library/curses panel curses panel Panel above9588073
Ref: 2e149588073
Ref: library/curses panel curses panel Panel below9588150
Ref: 2e159588150
Ref: library/curses panel curses panel Panel bottom9588227
Ref: 2e169588227
Ref: library/curses panel curses panel Panel hidden9588305
Ref: 2e179588305
Ref: library/curses panel curses panel Panel hide9588425
Ref: 2e189588425
Ref: library/curses panel curses panel Panel move9588559
Ref: 2e199588559
Ref: library/curses panel curses panel Panel replace9588651
Ref: 2e1a9588651
Ref: library/curses panel curses panel Panel set_userptr9588755
Ref: 2e1b9588755
Ref: library/curses panel curses panel Panel show9588947
Ref: 2e1c9588947
Ref: library/curses panel curses panel Panel top9589030
Ref: 2e1d9589030
Ref: library/curses panel curses panel Panel userptr9589098
Ref: 2e1e9589098
Ref: library/curses panel curses panel Panel window9589213
Ref: 2e1f9589213
Node: platform --- 對底層平臺識別資料的存取9589301
Ref: library/platform doc9589509
Ref: 2e209589509
Ref: library/platform module-platform9589509
Ref: 989589509
Ref: library/platform platform-access-to-underlying-platform-s-identifying-data9589509
Ref: 2e219589509
Ref: platform --- 對底層平臺識別資料的存取-Footnote-19590001
Node: 跨平台9590069
Ref: library/platform cross-platform9590184
Ref: 2e229590184
Ref: library/platform platform architecture9590222
Ref: 15819590222
Ref: library/platform platform machine9591492
Ref: 2e239591492
Ref: library/platform platform node9591630
Ref: 2e249591630
Ref: library/platform platform platform9591790
Ref: 16579591790
Ref: library/platform platform processor9592638
Ref: 2e269592638
Ref: library/platform platform python_build9592948
Ref: 2e279592948
Ref: library/platform platform python_compiler9593100
Ref: 2e289593100
Ref: library/platform platform python_branch9593210
Ref: 2e299593210
Ref: library/platform platform python_implementation9593311
Ref: 2e2a9593311
Ref: library/platform platform python_revision9593486
Ref: 2e2b9593486
Ref: library/platform platform python_version9593592
Ref: 2e2c9593592
Ref: library/platform platform python_version_tuple9593840
Ref: 2e2d9593840
Ref: library/platform platform release9594102
Ref: 2e2e9594102
Ref: library/platform platform system9594270
Ref: 1d549594270
Ref: library/platform platform system_alias9594684
Ref: 2e259594684
Ref: library/platform platform version9594938
Ref: 2e2f9594938
Ref: library/platform platform uname9595245
Ref: 19389595245
Node: Java 平台9595989
Ref: library/platform java-platform9596127
Ref: 2e309596127
Ref: library/platform platform java_ver9596170
Ref: 2879596170
Node: Windows 平台9596776
Ref: library/platform windows-platform9596917
Ref: 2e319596917
Ref: library/platform platform win32_ver9596966
Ref: 18609596966
Ref: library/platform platform win32_edition9597650
Ref: 2e329597650
Ref: library/platform platform win32_is_iot9597897
Ref: 2e339597897
Node: macOS 平台9598079
Ref: library/platform macos-platform9598221
Ref: 2e349598221
Ref: library/platform platform mac_ver9598266
Ref: 193a9598266
Node: iOS Platform9598638
Ref: library/platform ios-platform9598777
Ref: 2e359598777
Ref: library/platform platform ios_ver9598824
Ref: 1d539598824
Node: Unix 平台9599597
Ref: library/platform unix-platforms9599736
Ref: 2e369599736
Ref: library/platform platform libc_ver9599779
Ref: 19379599779
Node: Linux 平台9600379
Ref: library/platform linux-platforms9600522
Ref: 2e379600522
Ref: library/platform platform freedesktop_os_release9600567
Ref: 7ca9600567
Ref: Linux 平台-Footnote-19602009
Node: Android Platform9602082
Ref: library/platform android-platform9602205
Ref: 2e389602205
Ref: library/platform platform android_ver9602260
Ref: 15409602260
Ref: Android Platform-Footnote-19603394
Ref: Android Platform-Footnote-29603473
Ref: Android Platform-Footnote-39603544
Ref: Android Platform-Footnote-49603616
Node: errno --- 標準 errno 系統符號9603690
Ref: library/errno doc9603896
Ref: 2e399603896
Ref: library/errno errno-standard-errno-system-symbols9603896
Ref: 2e3a9603896
Ref: library/errno module-errno9603896
Ref: 4d9603896
Ref: library/errno errno errorcode9604287
Ref: 2e3b9604287
Ref: library/errno errno EPERM9604810
Ref: 16d19604810
Ref: library/errno errno ENOENT9604938
Ref: 21889604938
Ref: library/errno errno ESRCH9605071
Ref: 218c9605071
Ref: library/errno errno EINTR9605194
Ref: d2d9605194
Ref: library/errno errno EIO9605323
Ref: 2e3c9605323
Ref: library/errno errno ENXIO9605362
Ref: 2e3d9605362
Ref: library/errno errno E2BIG9605419
Ref: 2e3e9605419
Ref: library/errno errno ENOEXEC9605468
Ref: 2e3f9605468
Ref: library/errno errno EBADF9605519
Ref: 8ff9605519
Ref: library/errno errno ECHILD9605566
Ref: 21819605566
Ref: library/errno errno EAGAIN9605692
Ref: 217c9605692
Ref: library/errno errno ENOMEM9605807
Ref: 2e409605807
Ref: library/errno errno EACCES9605853
Ref: 218b9605853
Ref: library/errno errno EFAULT9605976
Ref: 2e419605976
Ref: library/errno errno ENOTBLK9606020
Ref: 2e429606020
Ref: library/errno errno EBUSY9606075
Ref: 2e439606075
Ref: library/errno errno EEXIST9606130
Ref: 21879606130
Ref: library/errno errno EXDEV9606247
Ref: 2a269606247
Ref: library/errno errno ENODEV9606296
Ref: 2e449606296
Ref: library/errno errno ENOTDIR9606343
Ref: 218a9606343
Ref: library/errno errno EISDIR9606468
Ref: 21899606468
Ref: library/errno errno EINVAL9606590
Ref: 18f49606590
Ref: library/errno errno ENFILE9606639
Ref: 2e459606639
Ref: library/errno errno EMFILE9606691
Ref: 2e469606691
Ref: library/errno errno ENOTTY9606743
Ref: 2e479606743
Ref: library/errno errno ETXTBSY9606792
Ref: 2e489606792
Ref: library/errno errno EFBIG9606840
Ref: 2e499606840
Ref: library/errno errno ENOSPC9606886
Ref: 2e4a9606886
Ref: library/errno errno ESPIPE9606942
Ref: 2e4b9606942
Ref: library/errno errno EROFS9606987
Ref: 2e4c9606987
Ref: library/errno errno EMLINK9607040
Ref: 2e4d9607040
Ref: library/errno errno EPIPE9607087
Ref: 21829607087
Ref: library/errno errno EDOM9607203
Ref: 2e4e9607203
Ref: library/errno errno ERANGE9607269
Ref: 2e4f9607269
Ref: library/errno errno EDEADLK9607331
Ref: 2e509607331
Ref: library/errno errno ENAMETOOLONG9607394
Ref: 2e519607394
Ref: library/errno errno ENOLCK9607451
Ref: 2e529607451
Ref: library/errno errno ENOSYS9607509
Ref: 16d29607509
Ref: library/errno errno ENOTEMPTY9607566
Ref: 2e539607566
Ref: library/errno errno ELOOP9607621
Ref: 2e549607621
Ref: library/errno errno EWOULDBLOCK9607688
Ref: 217e9607688
Ref: library/errno errno ENOMSG9607820
Ref: 2e559607820
Ref: library/errno errno EIDRM9607879
Ref: 2e569607879
Ref: library/errno errno ECHRNG9607929
Ref: 2e579607929
Ref: library/errno errno EL2NSYNC9607989
Ref: 2e589607989
Ref: library/errno errno EL3HLT9608048
Ref: 2e599608048
Ref: library/errno errno EL3RST9608095
Ref: 2e5a9608095
Ref: library/errno errno ELNRNG9608141
Ref: 2e5b9608141
Ref: library/errno errno EUNATCH9608198
Ref: 2e5c9608198
Ref: library/errno errno ENOCSI9608260
Ref: 2e5d9608260
Ref: library/errno errno EL2HLT9608319
Ref: 2e5e9608319
Ref: library/errno errno EBADE9608366
Ref: 2e5f9608366
Ref: library/errno errno EBADR9608414
Ref: 2e609608414
Ref: library/errno errno EXFULL9608472
Ref: 2e619608472
Ref: library/errno errno ENOANO9608518
Ref: 2e629608518
Ref: library/errno errno EBADRQC9608559
Ref: 2e639608559
Ref: library/errno errno EBADSLT9608613
Ref: 2e649608613
Ref: library/errno errno EDEADLOCK9608659
Ref: 2e659608659
Ref: library/errno errno EBFONT9608722
Ref: 2e669608722
Ref: library/errno errno ENOSTR9608775
Ref: 2e679608775
Ref: library/errno errno ENODATA9608827
Ref: 2e689608827
Ref: library/errno errno ETIME9608878
Ref: 2e699608878
Ref: library/errno errno ENOSR9608923
Ref: 2e6a9608923
Ref: library/errno errno ENONET9608979
Ref: 2e6b9608979
Ref: library/errno errno ENOPKG9609041
Ref: 2e6c9609041
Ref: library/errno errno EREMOTE9609095
Ref: 2e6d9609095
Ref: library/errno errno ENOLINK9609145
Ref: 2e6e9609145
Ref: library/errno errno EADV9609200
Ref: 2e6f9609200
Ref: library/errno errno ESRMNT9609246
Ref: 2e709609246
Ref: library/errno errno ECOMM9609292
Ref: 2e719609292
Ref: library/errno errno EPROTO9609351
Ref: 2e729609351
Ref: library/errno errno EMULTIHOP9609398
Ref: 2e739609398
Ref: library/errno errno EDOTDOT9609452
Ref: 2e749609452
Ref: library/errno errno EBADMSG9609504
Ref: 2e759609504
Ref: library/errno errno EOVERFLOW9609556
Ref: 2e769609556
Ref: library/errno errno ENOTUNIQ9609629
Ref: 2e779609629
Ref: library/errno errno EBADFD9609690
Ref: 2e789609690
Ref: library/errno errno EREMCHG9609751
Ref: 2e799609751
Ref: library/errno errno ELIBACC9609807
Ref: 2e7a9609807
Ref: library/errno errno ELIBBAD9609879
Ref: 2e7b9609879
Ref: library/errno errno ELIBSCN9609949
Ref: 2e7c9609949
Ref: library/errno errno ELIBMAX9610014
Ref: 2e7d9610014
Ref: library/errno errno ELIBEXEC9610095
Ref: 2e7e9610095
Ref: library/errno errno EILSEQ9610167
Ref: 2e7f9610167
Ref: library/errno errno ERESTART9610221
Ref: 2e809610221
Ref: library/errno errno ESTRPIPE9610299
Ref: 2e819610299
Ref: library/errno errno EUSERS9610352
Ref: 2e829610352
Ref: library/errno errno ENOTSOCK9610399
Ref: 2e839610399
Ref: library/errno errno EDESTADDRREQ9610464
Ref: 2e849610464
Ref: library/errno errno EMSGSIZE9610531
Ref: 2e859610531
Ref: library/errno errno EPROTOTYPE9610582
Ref: 2e869610582
Ref: library/errno errno ENOPROTOOPT9610649
Ref: 2e879610649
Ref: library/errno errno EPROTONOSUPPORT9610709
Ref: 2e889610709
Ref: library/errno errno ESOCKTNOSUPPORT9610773
Ref: 2e899610773
Ref: library/errno errno EOPNOTSUPP9610840
Ref: 2e8a9610840
Ref: library/errno errno ENOTSUP9610922
Ref: 2e8b9610922
Ref: library/errno errno EPFNOSUPPORT9611007
Ref: 2e8c9611007
Ref: library/errno errno EAFNOSUPPORT9611075
Ref: 2e8d9611075
Ref: library/errno errno EADDRINUSE9611154
Ref: 2e8e9611154
Ref: library/errno errno EADDRNOTAVAIL9611213
Ref: 2e8f9611213
Ref: library/errno errno ENETDOWN9611284
Ref: 2e909611284
Ref: library/errno errno ENETUNREACH9611334
Ref: 190d9611334
Ref: library/errno errno ENETRESET9611394
Ref: 2e919611394
Ref: library/errno errno ECONNABORTED9611473
Ref: 21849611473
Ref: library/errno errno ECONNRESET9611625
Ref: 21869611625
Ref: library/errno errno ENOBUFS9611765
Ref: 16ed9611765
Ref: library/errno errno EISCONN9611824
Ref: 2e929611824
Ref: library/errno errno ENOTCONN9611897
Ref: 2e939611897
Ref: library/errno errno ESHUTDOWN9611967
Ref: 21839611967
Ref: library/errno errno ETOOMANYREFS9612121
Ref: 2e949612121
Ref: library/errno errno ETIMEDOUT9612194
Ref: 218d9612194
Ref: library/errno errno ECONNREFUSED9612320
Ref: 21859612320
Ref: library/errno errno EHOSTDOWN9612458
Ref: 2e959612458
Ref: library/errno errno EHOSTUNREACH9612506
Ref: 2e969612506
Ref: library/errno errno EALREADY9612561
Ref: 217d9612561
Ref: library/errno errno EINPROGRESS9612698
Ref: 217f9612698
Ref: library/errno errno ESTALE9612834
Ref: 2e979612834
Ref: library/errno errno EUCLEAN9612888
Ref: 2e989612888
Ref: library/errno errno ENOTNAM9612946
Ref: 2e999612946
Ref: library/errno errno ENAVAIL9613007
Ref: 2e9a9613007
Ref: library/errno errno EISNAM9613070
Ref: 2e9b9613070
Ref: library/errno errno EREMOTEIO9613123
Ref: 2e9c9613123
Ref: library/errno errno EDQUOT9613175
Ref: 2e9d9613175
Ref: library/errno errno EQFULL9613222
Ref: 2e9e9613222
Ref: library/errno errno ENOTCAPABLE9613314
Ref: 16c29613314
Ref: library/errno errno ECANCELED9613523
Ref: 2e9f9613523
Ref: library/errno errno EOWNERDEAD9613605
Ref: 2ea09613605
Ref: library/errno errno ENOTRECOVERABLE9613680
Ref: 2ea19613680
Node: ctypes --- 用於 Python 的外部函式庫9613771
Ref: library/ctypes doc9613919
Ref: 2ea29613919
Ref: library/ctypes ctypes-a-foreign-function-library-for-python9613919
Ref: 2ea39613919
Ref: library/ctypes module-ctypes9613919
Ref: 229613919
Ref: ctypes --- 用於 Python 的外部函式庫-Footnote-19614417
Node: ctypes 教學9614480
Ref: library/ctypes ctypes-ctypes-tutorial9614598
Ref: 2ea49614598
Ref: library/ctypes ctypes-tutorial9614598
Ref: 2ea59614598
Node: Loading dynamic link libraries9615977
Ref: library/ctypes ctypes-loading-dynamic-link-libraries9616102
Ref: 2ea89616102
Ref: library/ctypes loading-dynamic-link-libraries9616102
Ref: 2ea99616102
Node: Accessing functions from loaded dlls9618155
Ref: library/ctypes accessing-functions-from-loaded-dlls9618301
Ref: 2eab9618301
Ref: library/ctypes ctypes-accessing-functions-from-loaded-dlls9618301
Ref: 2eac9618301
Node: 呼叫函式9620521
Ref: library/ctypes calling-functions9620659
Ref: 2ead9620659
Ref: library/ctypes ctypes-calling-functions9620659
Ref: 2eae9620659
Node: Fundamental data types9623081
Ref: library/ctypes ctypes-fundamental-data-types9623210
Ref: 2eaf9623210
Ref: library/ctypes fundamental-data-types9623210
Ref: 2eb09623210
Node: Calling functions continued9631347
Ref: library/ctypes calling-functions-continued9631490
Ref: 2ebd9631490
Ref: library/ctypes ctypes-calling-functions-continued9631490
Ref: 2ebe9631490
Node: Calling variadic functions9632570
Ref: library/ctypes calling-variadic-functions9632740
Ref: 2ebf9632740
Ref: library/ctypes ctypes-calling-variadic-functions9632740
Ref: 2ec09632740
Node: Calling functions with your own custom data types9633437
Ref: library/ctypes calling-functions-with-your-own-custom-data-types9633638
Ref: 2ec29633638
Ref: library/ctypes ctypes-calling-functions-with-own-custom-data-types9633638
Ref: 2ec39633638
Node: Specifying the required argument types function prototypes9634553
Ref: library/ctypes ctypes-specifying-required-argument-types9634740
Ref: 2ec49634740
Ref: library/ctypes specifying-the-required-argument-types-function-prototypes9634740
Ref: 2ec59634740
Node: Return types9636643
Ref: library/ctypes ctypes-return-types9636832
Ref: 2ec79636832
Ref: library/ctypes return-types9636832
Ref: 2ec89636832
Node: Passing pointers or passing parameters by reference9639957
Ref: library/ctypes ctypes-passing-pointers9640109
Ref: 2ecc9640109
Ref: library/ctypes passing-pointers-or-passing-parameters-by-reference9640109
Ref: 2ecd9640109
Node: Structures and unions9641201
Ref: library/ctypes ctypes-structures-unions9641381
Ref: 2ecf9641381
Ref: library/ctypes structures-and-unions9641381
Ref: 2ed09641381
Ref: library/ctypes ctypes-structureunion-alignment-byte-order9643475
Ref: 2ed29643475
Node: Structure/union alignment and byte order9643800
Ref: library/ctypes structure-union-alignment-and-byte-order9643964
Ref: 2ed39643964
Node: Bit fields in structures and unions9645005
Ref: library/ctypes bit-fields-in-structures-and-unions9645154
Ref: 2ed89645154
Ref: library/ctypes ctypes-bit-fields-in-structures-unions9645154
Ref: 2ed99645154
Node: Arrays9645748
Ref: library/ctypes arrays9645865
Ref: 2eda9645865
Ref: library/ctypes ctypes-arrays9645865
Ref: 2edb9645865
Node: Pointers9647154
Ref: library/ctypes ctypes-pointers9647252
Ref: 2edc9647252
Ref: library/ctypes pointers9647252
Ref: 2edd9647252
Node: Type conversions9649911
Ref: library/ctypes ctypes-type-conversions9650019
Ref: 2edf9650019
Ref: library/ctypes type-conversions9650019
Ref: 2ee09650019
Node: Incomplete Types9652635
Ref: library/ctypes ctypes-incomplete-types9652747
Ref: 2ee29652747
Ref: library/ctypes incomplete-types9652747
Ref: 2ee39652747
Node: 回呼函式9654361
Ref: library/ctypes callback-functions9654492
Ref: 2ee49654492
Ref: library/ctypes ctypes-callback-functions9654492
Ref: 2ee59654492
Node: Accessing values exported from dlls9658345
Ref: library/ctypes accessing-values-exported-from-dlls9658469
Ref: 2ee89658469
Ref: library/ctypes ctypes-accessing-values-exported-from-dlls9658469
Ref: 2ee99658469
Node: Surprises9661124
Ref: library/ctypes ctypes-surprises9661261
Ref: 2eec9661261
Ref: library/ctypes surprises9661261
Ref: 2eed9661261
Node: Variable-sized data types9663430
Ref: library/ctypes ctypes-variable-sized-data-types9663523
Ref: 2eee9663523
Ref: library/ctypes variable-sized-data-types9663523
Ref: 2eef9663523
Node: ctypes reference9664926
Ref: library/ctypes ctypes-ctypes-reference9665044
Ref: 2ef19665044
Ref: library/ctypes ctypes-reference9665044
Ref: 2ef29665044
Node: Finding shared libraries9665355
Ref: library/ctypes ctypes-finding-shared-libraries9665465
Ref: 2ef39665465
Ref: library/ctypes finding-shared-libraries9665465
Ref: 2ef49665465
Node: Loading shared libraries9668036
Ref: library/ctypes ctypes-loading-shared-libraries9668172
Ref: 2ef59668172
Ref: library/ctypes loading-shared-libraries9668172
Ref: 2ef69668172
Ref: library/ctypes ctypes CDLL9668375
Ref: 98d9668375
Ref: library/ctypes ctypes OleDLL9669500
Ref: 16759669500
Ref: library/ctypes ctypes WinDLL9670339
Ref: 16769670339
Ref: library/ctypes ctypes PyDLL9670911
Ref: 16779670911
Ref: library/ctypes ctypes PyDLL _handle9674748
Ref: 2efc9674748
Ref: library/ctypes ctypes PyDLL _name9674827
Ref: 2efd9674827
Ref: library/ctypes ctypes LibraryLoader9675173
Ref: 2efe9675173
Ref: library/ctypes ctypes LibraryLoader LoadLibrary9675632
Ref: 2eaa9675632
Ref: Loading shared libraries-Footnote-19677210
Ref: Loading shared libraries-Footnote-29677276
Node: Foreign functions9677322
Ref: library/ctypes ctypes-foreign-functions9677453
Ref: 2eff9677453
Ref: library/ctypes foreign-functions9677453
Ref: 2f009677453
Ref: library/ctypes ctypes _FuncPtr9677867
Ref: 2f019677867
Ref: library/ctypes ctypes _FuncPtr restype9678169
Ref: 2ec99678169
Ref: library/ctypes ctypes _FuncPtr argtypes9678843
Ref: 2ec19678843
Ref: library/ctypes ctypes _FuncPtr errcheck9680103
Ref: 2ecb9680103
Ref: library/ctypes ctypes ArgumentError9681084
Ref: 2f029681084
Node: Function prototypes9681721
Ref: library/ctypes ctypes-function-prototypes9681845
Ref: 2f039681845
Ref: library/ctypes function-prototypes9681845
Ref: 2f049681845
Ref: library/ctypes ctypes CFUNCTYPE9682422
Ref: 2ee69682422
Ref: library/ctypes ctypes WINFUNCTYPE9682931
Ref: 2ee79682931
Ref: library/ctypes ctypes PYFUNCTYPE9683283
Ref: 2f059683283
Node: Utility functions9688741
Ref: library/ctypes ctypes-utility-functions9688858
Ref: 2f069688858
Ref: library/ctypes utility-functions9688858
Ref: 2f079688858
Ref: library/ctypes ctypes addressof9688917
Ref: 2f089688917
Ref: library/ctypes ctypes alignment9689158
Ref: 2f099689158
Ref: library/ctypes ctypes byref9689316
Ref: 2ece9689316
Ref: library/ctypes ctypes cast9689828
Ref: 2ee19689828
Ref: library/ctypes ctypes create_string_buffer9690120
Ref: 2ebc9690120
Ref: library/ctypes ctypes create_unicode_buffer9690930
Ref: 18d49690930
Ref: library/ctypes ctypes DllCanUnloadNow9691754
Ref: 2f0a9691754
Ref: library/ctypes ctypes DllGetClassObject9691997
Ref: 2f0b9691997
Ref: library/ctypes ctypes util find_library9692255
Ref: cf09692255
Ref: library/ctypes ctypes util find_msvcrt9692645
Ref: 2f0c9692645
Ref: library/ctypes ctypes FormatError9693099
Ref: 2f0d9693099
Ref: library/ctypes ctypes GetLastError9693336
Ref: 2eca9693336
Ref: library/ctypes ctypes get_errno9693608
Ref: 2ef89693608
Ref: library/ctypes ctypes get_last_error9693856
Ref: 2efa9693856
Ref: library/ctypes ctypes memmove9694127
Ref: 2f0e9694127
Ref: library/ctypes ctypes memset9694369
Ref: 2f0f9694369
Ref: library/ctypes ctypes POINTER9694620
Ref: 15e09694620
Ref: library/ctypes ctypes pointer9694845
Ref: 15df9694845
Ref: library/ctypes ctypes resize9695152
Ref: 2ef09695152
Ref: library/ctypes ctypes set_errno9695488
Ref: 2ef99695488
Ref: library/ctypes ctypes set_last_error9695798
Ref: 2efb9695798
Ref: library/ctypes ctypes sizeof9696131
Ref: 2f109696131
Ref: library/ctypes ctypes string_at9696300
Ref: 2f119696300
Ref: library/ctypes ctypes WinError9696614
Ref: 2f129696614
Ref: library/ctypes ctypes wstring_at9697148
Ref: 2f139697148
Node: Data types9697508
Ref: library/ctypes ctypes-data-types9697631
Ref: 2f149697631
Ref: library/ctypes data-types9697631
Ref: 2f159697631
Ref: library/ctypes ctypes _CData9697676
Ref: 2f169697676
Ref: library/ctypes ctypes _CData from_buffer9698312
Ref: 2f189698312
Ref: library/ctypes ctypes _CData from_buffer_copy9698904
Ref: 2f199698904
Ref: library/ctypes ctypes _CData from_address9699454
Ref: 2f1a9699454
Ref: library/ctypes ctypes _CData from_param9699800
Ref: 2ec69699800
Ref: library/ctypes ctypes _CData in_dll9700359
Ref: 2eea9700359
Ref: library/ctypes ctypes _CData _b_base_9700655
Ref: 2f1b9700655
Ref: library/ctypes ctypes _CData _b_needsfree_9700957
Ref: 2f1c9700957
Ref: library/ctypes ctypes _CData _objects9701128
Ref: 2f179701128
Node: Fundamental data types<2>9701437
Ref: library/ctypes ctypes-fundamental-data-types-29701564
Ref: 2f1d9701564
Ref: library/ctypes id19701564
Ref: 2f1e9701564
Ref: library/ctypes ctypes _SimpleCData9701633
Ref: 2f1f9701633
Ref: library/ctypes ctypes _SimpleCData value9702107
Ref: 2f209702107
Ref: library/ctypes ctypes c_byte9703466
Ref: 16739703466
Ref: library/ctypes ctypes c_char9703679
Ref: 2eb29703679
Ref: library/ctypes ctypes c_char_p9703920
Ref: 15e19703920
Ref: library/ctypes ctypes c_double9704215
Ref: 17fd9704215
Ref: library/ctypes ctypes c_longdouble9704345
Ref: 17fe9704345
Ref: library/ctypes ctypes c_float9704593
Ref: 2ebb9704593
Ref: library/ctypes ctypes c_int9704721
Ref: 2ea69704721
Ref: library/ctypes ctypes c_int89704986
Ref: 2f219704986
Ref: library/ctypes ctypes c_int169705110
Ref: 2f229705110
Ref: library/ctypes ctypes c_int329705237
Ref: 2f239705237
Ref: library/ctypes ctypes c_int649705362
Ref: 2f249705362
Ref: library/ctypes ctypes c_long9705492
Ref: 2ea79705492
Ref: library/ctypes ctypes c_longlong9705657
Ref: 2eb89705657
Ref: library/ctypes ctypes c_short9705836
Ref: 2eb49705836
Ref: library/ctypes ctypes c_size_t9706003
Ref: 2eba9706003
Ref: library/ctypes ctypes c_ssize_t9706078
Ref: 11d49706078
Ref: library/ctypes ctypes c_time_t9706183
Ref: 16de9706183
Ref: library/ctypes ctypes c_ubyte9706287
Ref: 16749706287
Ref: library/ctypes ctypes c_uint9706502
Ref: 2eb69706502
Ref: library/ctypes ctypes c_uint89706772
Ref: 2f259706772
Ref: library/ctypes ctypes c_uint169706900
Ref: 2f269706900
Ref: library/ctypes ctypes c_uint329707031
Ref: 2f279707031
Ref: library/ctypes ctypes c_uint649707160
Ref: 2f289707160
Ref: library/ctypes ctypes c_ulong9707294
Ref: 2eb79707294
Ref: library/ctypes ctypes c_ulonglong9707462
Ref: 2eb99707462
Ref: library/ctypes ctypes c_ushort9707644
Ref: 2eb59707644
Ref: library/ctypes ctypes c_void_p9707814
Ref: 15e39707814
Ref: library/ctypes ctypes c_wchar9707978
Ref: 2eb39707978
Ref: library/ctypes ctypes c_wchar_p9708244
Ref: 15e29708244
Ref: library/ctypes ctypes c_bool9708452
Ref: 2eb19708452
Ref: library/ctypes ctypes HRESULT9708667
Ref: 2ef79708667
Ref: library/ctypes ctypes py_object9708829
Ref: 13a59708829
Node: Structured data types9709219
Ref: library/ctypes ctypes-structured-data-types9709355
Ref: 2f299709355
Ref: library/ctypes structured-data-types9709355
Ref: 2f2a9709355
Ref: library/ctypes ctypes Union9709422
Ref: 15779709422
Ref: library/ctypes ctypes BigEndianUnion9709521
Ref: 172b9709521
Ref: library/ctypes ctypes LittleEndianUnion9709664
Ref: 172c9709664
Ref: library/ctypes ctypes BigEndianStructure9709813
Ref: 2ed69709813
Ref: library/ctypes ctypes LittleEndianStructure9709935
Ref: 2ed79709935
Ref: library/ctypes ctypes Structure9710205
Ref: 154d9710205
Ref: library/ctypes ctypes Structure _fields_9710630
Ref: 2ed19710630
Ref: library/ctypes ctypes Structure _pack_9712221
Ref: 2ed49712221
Ref: library/ctypes ctypes Structure _align_9712583
Ref: 2ed59712583
Ref: library/ctypes ctypes Structure _anonymous_9712842
Ref: 2f2b9712842
Node: Arrays and pointers9715195
Ref: library/ctypes arrays-and-pointers9715297
Ref: 2f2c9715297
Ref: library/ctypes ctypes-arrays-pointers9715297
Ref: 2f2d9715297
Ref: library/ctypes ctypes Array9715360
Ref: 19309715360
Ref: library/ctypes ctypes Array _length_9715875
Ref: 2f2e9715875
Ref: library/ctypes ctypes Array _type_9716101
Ref: 2f2f9716101
Ref: library/ctypes ctypes ARRAY9716296
Ref: 27b9716296
Ref: library/ctypes ctypes _Pointer9716590
Ref: 2f309716590
Ref: library/ctypes ctypes _Pointer _type_9717247
Ref: 2f319717247
Ref: library/ctypes ctypes _Pointer contents9717314
Ref: 2ede9717314
Node: 並行執行 Concurrent Execution9717501
Ref: library/concurrency doc9717693
Ref: 2f329717693
Ref: library/concurrency concurrency9717693
Ref: 2f339717693
Ref: library/concurrency concurrent-execution9717693
Ref: 2f349717693
Node: threading --- 基於執行緒的平行性9718855
Ref: library/threading doc9719025
Ref: 2f359719025
Ref: library/threading module-threading9719025
Ref: d69719025
Ref: library/threading threading-thread-based-parallelism9719025
Ref: 2f369719025
Ref: library/threading threading active_count9720902
Ref: 2dc9720902
Ref: library/threading threading current_thread9721191
Ref: 2db9721191
Ref: library/threading threading excepthook9721587
Ref: 7ef9721587
Ref: library/threading threading __excepthook__9722920
Ref: 7ee9722920
Ref: library/threading threading get_ident9723194
Ref: 10f39723194
Ref: library/threading threading get_native_id9723584
Ref: 9e19723584
Ref: library/threading threading enumerate9724134
Ref: 17a89724134
Ref: library/threading threading main_thread9724516
Ref: f759724516
Ref: library/threading threading settrace9724741
Ref: 7ec9724741
Ref: library/threading threading settrace_all_threads9725006
Ref: 46f9725006
Ref: library/threading threading gettrace9725369
Ref: 7ea9725369
Ref: library/threading threading setprofile9725495
Ref: 7ed9725495
Ref: library/threading threading setprofile_all_threads9725766
Ref: 4709725766
Ref: library/threading threading getprofile9726135
Ref: 7eb9726135
Ref: library/threading threading stack_size9726268
Ref: 2f379726268
Ref: library/threading threading TIMEOUT_MAX9727589
Ref: 2f389727589
Ref: threading --- 基於執行緒的平行性-Footnote-19728941
Node: Thread-Local Data9729010
Ref: library/threading thread-local-data9729128
Ref: 2f399729128
Ref: library/threading threading local9729478
Ref: 166d9729478
Ref: Thread-Local Data-Footnote-19729744
Node: Thread Objects9729821
Ref: library/threading id19729960
Ref: 2f3a9729960
Ref: library/threading thread-objects9729960
Ref: 2f3b9729960
Ref: library/threading threading Thread9732612
Ref: 8f09732612
Ref: library/threading threading Thread start9734043
Ref: 2c019734043
Ref: library/threading threading Thread run9734416
Ref: 9e09734416
Ref: library/threading meth-thread-join9735231
Ref: 2f3c9735231
Ref: library/threading threading Thread join9735231
Ref: 117c9735231
Ref: library/threading threading Thread name9736496
Ref: 2da9736496
Ref: library/threading threading Thread getName9736711
Ref: 2f3d9736711
Ref: library/threading threading Thread setName9736739
Ref: 2d99736739
Ref: library/threading threading Thread ident9736919
Ref: 2b2b9736919
Ref: library/threading threading Thread native_id9737304
Ref: 9e29737304
Ref: library/threading threading Thread is_alive9738116
Ref: 8f19738116
Ref: library/threading threading Thread daemon9738454
Ref: 2d89738454
Ref: library/threading threading Thread isDaemon9739045
Ref: 2f3e9739045
Ref: library/threading threading Thread setDaemon9739074
Ref: 2d79739074
Node: Lock Objects9739258
Ref: library/threading id29739392
Ref: 2f3f9739392
Ref: library/threading lock-objects9739392
Ref: 2f409739392
Ref: library/threading threading Lock9740801
Ref: 156d9740801
Ref: library/threading threading Lock acquire9741203
Ref: 63e9741203
Ref: library/threading threading Lock release9742536
Ref: 12579742536
Ref: library/threading threading Lock locked9743021
Ref: 2f429743021
Node: RLock 物件9743103
Ref: library/threading id39743240
Ref: 2f439743240
Ref: library/threading rlock-objects9743240
Ref: 2f449743240
Ref: library/threading threading RLock9744593
Ref: 2be9744593
Ref: library/threading threading RLock acquire9745116
Ref: e1f9745116
Ref: library/threading threading RLock release9747100
Ref: 2f459747100
Node: Condition Objects9747797
Ref: library/threading condition-objects9747939
Ref: 2f469747939
Ref: library/threading id49747939
Ref: 2f479747939
Ref: library/threading threading Condition9751052
Ref: 10ee9751052
Ref: library/threading threading Condition acquire9751594
Ref: 2f489751594
Ref: library/threading threading Condition release9751806
Ref: 2f499751806
Ref: library/threading threading Condition wait9751989
Ref: 17b49751989
Ref: library/threading threading Condition wait_for9753517
Ref: 2f4a9753517
Ref: library/threading threading Condition notify9754491
Ref: 16e19754491
Ref: library/threading threading Condition notify_all9755391
Ref: 2d59755391
Node: Semaphore Objects9755807
Ref: library/threading id59755950
Ref: 2f4b9755950
Ref: library/threading semaphore-objects9755950
Ref: 2f4c9755950
Ref: library/threading threading Semaphore9756649
Ref: 10ef9756649
Ref: library/threading threading Semaphore acquire9757339
Ref: 11ec9757339
Ref: library/threading threading Semaphore release9758632
Ref: 2f4d9758632
Ref: library/threading threading BoundedSemaphore9759007
Ref: 10f09759007
Node: Semaphore 範例9759564
Ref: library/threading semaphore-example9759634
Ref: 2f4e9759634
Ref: library/threading semaphore-examples9759634
Ref: 2f4f9759634
Node: Event Objects9760496
Ref: library/threading event-objects9760635
Ref: 2f509760635
Ref: library/threading id69760635
Ref: 2f519760635
Ref: library/threading threading Event9761037
Ref: 10f19761037
Ref: library/threading threading Event is_set9761432
Ref: 2d69761432
Ref: library/threading threading Event set9761604
Ref: 2f529761604
Ref: library/threading threading Event clear9761832
Ref: 2f539761832
Ref: library/threading threading Event wait9762061
Ref: 12ba9762061
Node: Timer Objects9762789
Ref: library/threading id79762926
Ref: 2f549762926
Ref: library/threading timer-objects9762926
Ref: 2f559762926
Ref: library/threading threading Timer9763675
Ref: 10f29763675
Ref: library/threading threading Timer cancel9764123
Ref: 2f569764123
Node: Barrier Objects9764311
Ref: library/threading barrier-objects9764494
Ref: 2f579764494
Ref: library/threading threading Barrier9765451
Ref: 117b9765451
Ref: library/threading threading Barrier wait9765796
Ref: 2f589765796
Ref: library/threading threading Barrier reset9766946
Ref: 2f599766946
Ref: library/threading threading Barrier abort9767383
Ref: 2f5a9767383
Ref: library/threading threading Barrier parties9767873
Ref: 2f5b9767873
Ref: library/threading threading Barrier n_waiting9767962
Ref: 2f5c9767962
Ref: library/threading threading Barrier broken9768057
Ref: 2f5d9768057
Ref: library/threading threading BrokenBarrierError9768171
Ref: 117d9768171
Node: Using locks conditions and semaphores in the with statement9768346
Ref: library/threading using-locks-conditions-and-semaphores-in-the-with-statement9768507
Ref: 2f5e9768507
Ref: library/threading with-locks9768507
Ref: 2f419768507
Node: multiprocessing --- 以行程為基礎的平行性9769354
Ref: library/multiprocessing doc9769612
Ref: 2f5f9769612
Ref: library/multiprocessing module-multiprocessing9769612
Ref: 869769612
Ref: library/multiprocessing multiprocessing-process-based-parallelism9769612
Ref: 2f609769612
Ref: multiprocessing --- 以行程為基礎的平行性-Footnote-19770248
Node: 簡介<7>9770321
Ref: library/multiprocessing introduction9770438
Ref: 2f619770438
Node: Process 類別9772362
Ref: library/multiprocessing the-process-class9772457
Ref: 2f629772457
Node: Contexts and start methods9773630
Ref: library/multiprocessing contexts-and-start-methods9773770
Ref: 2f659773770
Ref: library/multiprocessing multiprocessing-start-methods9773770
Ref: 2aa9773770
Ref: Contexts and start methods-Footnote-19779190
Node: Exchanging objects between processes9779255
Ref: library/multiprocessing exchanging-objects-between-processes9779414
Ref: 2f679779414
Node: Synchronization between processes9781315
Ref: library/multiprocessing synchronization-between-processes9781479
Ref: 2f699781479
Node: Sharing state between processes9782199
Ref: library/multiprocessing sharing-state-between-processes9782350
Ref: 2f6a9782350
Node: Using a pool of workers9785448
Ref: library/multiprocessing using-a-pool-of-workers9785557
Ref: 2f749785557
Node: Reference<2>9788852
Ref: library/multiprocessing reference9789000
Ref: 2f759789000
Node: Process 與例外9789484
Ref: library/multiprocessing process-and-exceptions9789575
Ref: 2f769789575
Ref: library/multiprocessing multiprocessing Process9789635
Ref: afd9789635
Ref: library/multiprocessing multiprocessing Process run9791137
Ref: 2f669791137
Ref: library/multiprocessing multiprocessing Process start9791943
Ref: 2f639791943
Ref: library/multiprocessing multiprocessing Process join9792188
Ref: 2f799792188
Ref: library/multiprocessing multiprocessing Process name9792908
Ref: 2f779792908
Ref: library/multiprocessing multiprocessing Process is_alive9793364
Ref: 2f7b9793364
Ref: library/multiprocessing multiprocessing Process daemon9793600
Ref: 2f789793600
Ref: library/multiprocessing multiprocessing Process pid9794476
Ref: 2f7c9794476
Ref: library/multiprocessing multiprocessing Process exitcode9794598
Ref: 2f7a9794598
Ref: library/multiprocessing multiprocessing Process authkey9795193
Ref: 2f7d9795193
Ref: library/multiprocessing multiprocessing Process sentinel9795722
Ref: 107a9795722
Ref: library/multiprocessing multiprocessing Process terminate9796356
Ref: 2f7f9796356
Ref: library/multiprocessing multiprocessing Process kill9797164
Ref: afc9797164
Ref: library/multiprocessing multiprocessing Process close9797322
Ref: afb9797322
Ref: library/multiprocessing multiprocessing ProcessError9798617
Ref: 2f809798617
Ref: library/multiprocessing multiprocessing BufferTooShort9798726
Ref: 2f819798726
Ref: library/multiprocessing multiprocessing AuthenticationError9799032
Ref: 2f829799032
Ref: library/multiprocessing multiprocessing TimeoutError9799133
Ref: 2f839799133
Node: Pipes and Queues9799240
Ref: library/multiprocessing pipes-and-queues9799356
Ref: 2f849799356
Ref: library/multiprocessing multiprocessing Pipe9803055
Ref: 2f689803055
Ref: library/multiprocessing multiprocessing Queue9803604
Ref: 17019803604
Ref: library/multiprocessing multiprocessing Queue qsize9804202
Ref: 2f8f9804202
Ref: library/multiprocessing multiprocessing Queue empty9804544
Ref: 14ee9804544
Ref: library/multiprocessing multiprocessing Queue full9804831
Ref: 2f909804831
Ref: library/multiprocessing multiprocessing Queue put9805026
Ref: 19429805026
Ref: library/multiprocessing multiprocessing Queue put_nowait9805841
Ref: 2f919805841
Ref: library/multiprocessing multiprocessing Queue get9805924
Ref: 19439805924
Ref: library/multiprocessing multiprocessing Queue get_nowait9806710
Ref: 2f8c9806710
Ref: library/multiprocessing multiprocessing Queue close9806957
Ref: 17029806957
Ref: library/multiprocessing multiprocessing Queue join_thread9807253
Ref: 2f929807253
Ref: library/multiprocessing multiprocessing Queue cancel_join_thread9807802
Ref: 2f8d9807802
Ref: library/multiprocessing multiprocessing SimpleQueue9808946
Ref: 8b99808946
Ref: library/multiprocessing multiprocessing SimpleQueue close9809083
Ref: 8ba9809083
Ref: library/multiprocessing multiprocessing SimpleQueue empty9809394
Ref: 14ef9809394
Ref: library/multiprocessing multiprocessing SimpleQueue get9809584
Ref: 2f939809584
Ref: library/multiprocessing multiprocessing SimpleQueue put9809662
Ref: 2f949809662
Ref: library/multiprocessing multiprocessing JoinableQueue9809729
Ref: 2f859809729
Ref: library/multiprocessing multiprocessing JoinableQueue task_done9809950
Ref: 2f889809950
Ref: library/multiprocessing multiprocessing JoinableQueue join9810638
Ref: 2f959810638
Ref: Pipes and Queues-Footnote-19811142
Node: Miscellaneous<2>9811206
Ref: library/multiprocessing miscellaneous9811323
Ref: 2f969811323
Ref: library/multiprocessing multiprocessing active_children9811372
Ref: 2f979811372
Ref: library/multiprocessing multiprocessing cpu_count9811583
Ref: f129811583
Ref: library/multiprocessing multiprocessing current_process9812315
Ref: 2f989812315
Ref: library/multiprocessing multiprocessing parent_process9812510
Ref: 2f999812510
Ref: library/multiprocessing multiprocessing freeze_support9812777
Ref: 2f9a9812777
Ref: library/multiprocessing multiprocessing get_all_start_methods9813811
Ref: f0c9813811
Ref: library/multiprocessing multiprocessing get_context9814164
Ref: 2a89814164
Ref: library/multiprocessing multiprocessing get_start_method9814642
Ref: f0d9814642
Ref: library/multiprocessing multiprocessing set_executable9815407
Ref: 170a9815407
Ref: library/multiprocessing multiprocessing set_forkserver_preload9815949
Ref: 15f89815949
Ref: library/multiprocessing multiprocessing set_start_method9816658
Ref: 2a99816658
Ref: Miscellaneous<2>-Footnote-19817768
Node: Connection Objects9817833
Ref: library/multiprocessing connection-objects9817960
Ref: 2f9b9817960
Ref: library/multiprocessing multiprocessing connection Connection9818277
Ref: 15a29818277
Ref: library/multiprocessing multiprocessing connection Connection send9818328
Ref: 2f9d9818328
Ref: library/multiprocessing multiprocessing connection Connection recv9818655
Ref: 2f9e9818655
Ref: library/multiprocessing multiprocessing connection Connection fileno9818948
Ref: 2f9f9818948
Ref: library/multiprocessing multiprocessing connection Connection close9819048
Ref: 2fa09819048
Ref: library/multiprocessing multiprocessing connection Connection poll9819200
Ref: 2fa19819200
Ref: library/multiprocessing multiprocessing connection Connection send_bytes9819687
Ref: 2fa29819687
Ref: library/multiprocessing multiprocessing connection Connection recv_bytes9820146
Ref: 2fa39820146
Ref: library/multiprocessing multiprocessing connection Connection recv_bytes_into9820785
Ref: 2fa49820785
Ref: library/multiprocessing multiprocessing-recv-pickle-security9822598
Ref: 2fa59822598
Node: Synchronization primitives9823282
Ref: library/multiprocessing synchronization-primitives9823416
Ref: 2fa69823416
Ref: library/multiprocessing multiprocessing Barrier9823784
Ref: 2f739823784
Ref: library/multiprocessing multiprocessing BoundedSemaphore9823946
Ref: 2f719823946
Ref: library/multiprocessing multiprocessing Condition9824446
Ref: 2f729824446
Ref: library/multiprocessing multiprocessing Event9824775
Ref: 17669824775
Ref: library/multiprocessing multiprocessing Lock9824856
Ref: 2f6e9824856
Ref: library/multiprocessing multiprocessing Lock acquire9825700
Ref: 2fa79825700
Ref: library/multiprocessing multiprocessing Lock release9827226
Ref: 2fa89827226
Ref: library/multiprocessing multiprocessing RLock9827595
Ref: 2f6f9827595
Ref: library/multiprocessing multiprocessing RLock acquire9828327
Ref: 2fa99828327
Ref: library/multiprocessing multiprocessing RLock release9829974
Ref: 2faa9829974
Ref: library/multiprocessing multiprocessing Semaphore9830951
Ref: 2f709830951
Ref: Synchronization primitives-Footnote-19831814
Node: 共享的 ctypes 物件9831878
Ref: library/multiprocessing shared-ctypes-objects9832002
Ref: 2fab9832002
Ref: library/multiprocessing multiprocessing Value9832178
Ref: 2f6b9832178
Ref: library/multiprocessing multiprocessing Array9833601
Ref: 2f6c9833601
Node: multiprocessing sharedctypes 模組9835030
Ref: library/multiprocessing module-multiprocessing sharedctypes9835125
Ref: 8c9835125
Ref: library/multiprocessing the-multiprocessing-sharedctypes-module9835125
Ref: 2fac9835125
Ref: library/multiprocessing multiprocessing sharedctypes RawArray9835748
Ref: 2fad9835748
Ref: library/multiprocessing multiprocessing sharedctypes RawValue9836573
Ref: 2faf9836573
Ref: library/multiprocessing multiprocessing sharedctypes Array9837351
Ref: 2fae9837351
Ref: library/multiprocessing multiprocessing sharedctypes Value9838112
Ref: 2fb09838112
Ref: library/multiprocessing multiprocessing sharedctypes copy9838857
Ref: 2fb19838857
Ref: library/multiprocessing multiprocessing sharedctypes synchronized9839017
Ref: dd79839017
Node: Managers9842017
Ref: library/multiprocessing managers9842128
Ref: 2fb29842128
Ref: library/multiprocessing multiprocessing-managers9842128
Ref: 2f899842128
Ref: library/multiprocessing multiprocessing Manager9842478
Ref: c619842478
Ref: library/multiprocessing module-multiprocessing managers9842797
Ref: 899842797
Ref: library/multiprocessing multiprocessing managers BaseManager9842986
Ref: 2fb49842986
Ref: library/multiprocessing multiprocessing managers BaseManager start9844425
Ref: 2fb59844425
Ref: library/multiprocessing multiprocessing managers BaseManager get_server9844660
Ref: 2fb79844660
Ref: library/multiprocessing multiprocessing managers BaseManager connect9845204
Ref: 2fb99845204
Ref: library/multiprocessing multiprocessing managers BaseManager shutdown9845485
Ref: 2fb69845485
Ref: library/multiprocessing multiprocessing managers BaseManager register9845721
Ref: 2fba9845721
Ref: library/multiprocessing multiprocessing managers BaseManager address9848022
Ref: 2fb89848022
Ref: library/multiprocessing multiprocessing managers SyncManager9848544
Ref: 2fb39848544
Ref: library/multiprocessing multiprocessing managers SyncManager Barrier9848985
Ref: 2fbd9848985
Ref: library/multiprocessing multiprocessing managers SyncManager BoundedSemaphore9849177
Ref: 2fbe9849177
Ref: library/multiprocessing multiprocessing managers SyncManager Condition9849333
Ref: 2fbf9849333
Ref: library/multiprocessing multiprocessing managers SyncManager Event9849695
Ref: 2fc09849695
Ref: library/multiprocessing multiprocessing managers SyncManager Lock9849822
Ref: 2fc19849822
Ref: library/multiprocessing multiprocessing managers SyncManager Namespace9849947
Ref: 2fc29849947
Ref: library/multiprocessing multiprocessing managers SyncManager Queue9850072
Ref: 2c199850072
Ref: library/multiprocessing multiprocessing managers SyncManager RLock9850204
Ref: 2fc39850204
Ref: library/multiprocessing multiprocessing managers SyncManager Semaphore9850330
Ref: 2fc49850330
Ref: library/multiprocessing multiprocessing managers SyncManager Array9850472
Ref: 2fc59850472
Ref: library/multiprocessing multiprocessing managers SyncManager Value9850571
Ref: 2fc69850571
Ref: library/multiprocessing multiprocessing managers SyncManager dict9850716
Ref: 2fc79850716
Ref: library/multiprocessing multiprocessing managers SyncManager list9850897
Ref: 2fc89850897
Ref: library/multiprocessing multiprocessing managers Namespace9851302
Ref: 2f6d9851302
Node: Customized managers9852143
Ref: library/multiprocessing customized-managers9852238
Ref: 2fc99852238
Node: Using a remote manager9853008
Ref: library/multiprocessing using-a-remote-manager9853103
Ref: 2fca9853103
Node: Proxy Objects9855244
Ref: library/multiprocessing multiprocessing-proxy-objects9855345
Ref: c609855345
Ref: library/multiprocessing proxy-objects9855345
Ref: 2fcb9855345
Ref: library/multiprocessing multiprocessing managers BaseProxy9858631
Ref: 2fbb9858631
Ref: library/multiprocessing multiprocessing managers BaseProxy _callmethod9858753
Ref: 2fbc9858753
Ref: library/multiprocessing multiprocessing managers BaseProxy _getvalue9860318
Ref: 2fcc9860318
Ref: library/multiprocessing multiprocessing managers BaseProxy __repr__9860478
Ref: 2fcd9860478
Ref: library/multiprocessing multiprocessing managers BaseProxy __str__9860564
Ref: 2fce9860564
Node: Cleanup9860669
Ref: library/multiprocessing cleanup9860726
Ref: 2fcf9860726
Node: Process Pools9861015
Ref: library/multiprocessing module-multiprocessing pool9861129
Ref: 8a9861129
Ref: library/multiprocessing process-pools9861129
Ref: 2fd09861129
Ref: library/multiprocessing multiprocessing pool Pool9861290
Ref: f0e9861290
Ref: library/multiprocessing multiprocessing pool Pool apply9864085
Ref: 2fd39864085
Ref: library/multiprocessing multiprocessing pool Pool apply_async9864456
Ref: 2fd49864456
Ref: library/multiprocessing multiprocessing pool Pool map9865308
Ref: 107e9865308
Ref: library/multiprocessing multiprocessing pool Pool map_async9866093
Ref: 107f9866093
Ref: library/multiprocessing multiprocessing pool Pool imap9866948
Ref: 2fd69866948
Ref: library/multiprocessing multiprocessing pool Pool imap_unordered9867660
Ref: 2fd79867660
Ref: library/multiprocessing multiprocessing pool Pool starmap9867982
Ref: 107b9867982
Ref: library/multiprocessing multiprocessing pool Pool starmap_async9868337
Ref: 107c9868337
Ref: library/multiprocessing multiprocessing pool Pool close9868692
Ref: 2fd19868692
Ref: library/multiprocessing multiprocessing pool Pool terminate9868879
Ref: 2fd29868879
Ref: library/multiprocessing multiprocessing pool Pool join9869113
Ref: 2fd89869113
Ref: library/multiprocessing multiprocessing pool AsyncResult9869557
Ref: 2fd59869557
Ref: library/multiprocessing multiprocessing pool AsyncResult get9869716
Ref: 2fd99869716
Ref: library/multiprocessing multiprocessing pool AsyncResult wait9870081
Ref: 2fda9870081
Ref: library/multiprocessing multiprocessing pool AsyncResult ready9870205
Ref: 2fdb9870205
Ref: library/multiprocessing multiprocessing pool AsyncResult successful9870282
Ref: 2fdc9870282
Node: Listeners and Clients9871563
Ref: library/multiprocessing listeners-and-clients9871683
Ref: 2fdd9871683
Ref: library/multiprocessing module-multiprocessing connection9871683
Ref: 879871683
Ref: library/multiprocessing multiprocessing-listeners-clients9871683
Ref: 2f9c9871683
Ref: library/multiprocessing multiprocessing connection deliver_challenge9872219
Ref: 2fde9872219
Ref: library/multiprocessing multiprocessing connection answer_challenge9872623
Ref: 2fdf9872623
Ref: library/multiprocessing multiprocessing connection Client9872935
Ref: 2fe09872935
Ref: library/multiprocessing multiprocessing connection Listener9873697
Ref: 15a19873697
Ref: library/multiprocessing multiprocessing connection Listener accept9875458
Ref: 15569875458
Ref: library/multiprocessing multiprocessing connection Listener close9875740
Ref: 2fe29875740
Ref: library/multiprocessing multiprocessing connection Listener address9876040
Ref: 2fe39876040
Ref: library/multiprocessing multiprocessing connection Listener last_accepted9876133
Ref: 2fe49876133
Ref: library/multiprocessing multiprocessing connection wait9876546
Ref: 10799876546
Node: Address Formats9880563
Ref: library/multiprocessing address-formats9880636
Ref: 2fe59880636
Ref: library/multiprocessing multiprocessing-address-formats9880636
Ref: 2fe19880636
Node: Authentication keys9881350
Ref: library/multiprocessing authentication-keys9881464
Ref: 2fe69881464
Ref: library/multiprocessing multiprocessing-auth-keys9881464
Ref: 2f7e9881464
Node: Logging9882648
Ref: library/multiprocessing logging9882769
Ref: 2fe79882769
Ref: library/multiprocessing multiprocessing get_logger9883037
Ref: 2fe89883037
Ref: library/multiprocessing multiprocessing log_to_stderr9883550
Ref: 2fe99883550
Node: multiprocessing dummy 模組9884655
Ref: library/multiprocessing module-multiprocessing dummy9884748
Ref: 889884748
Ref: library/multiprocessing the-multiprocessing-dummy-module9884748
Ref: 2fea9884748
Ref: library/multiprocessing multiprocessing pool ThreadPool9885262
Ref: 18139885262
Node: Programming guidelines9887022
Ref: library/multiprocessing multiprocessing-programming9887171
Ref: 2f649887171
Ref: library/multiprocessing programming-guidelines9887171
Ref: 2feb9887171
Node: All start methods9887419
Ref: library/multiprocessing all-start-methods9887542
Ref: 2fec9887542
Ref: All start methods-Footnote-19893624
Ref: All start methods-Footnote-29893688
Ref: All start methods-Footnote-39893752
Node: The spawn and forkserver start methods9893816
Ref: library/multiprocessing the-spawn-and-forkserver-start-methods9893939
Ref: 2fed9893939
Ref: library/multiprocessing multiprocessing-safe-main-import9894740
Ref: 2fee9894740
Node: 範例<19>9896009
Ref: library/multiprocessing examples9896137
Ref: 2fef9896137
Ref: library/multiprocessing multiprocessing-examples9896137
Ref: 2f8e9896137
Node: multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取9905045
Ref: library/multiprocessing shared_memory doc9905279
Ref: 2ff09905279
Ref: library/multiprocessing shared_memory module-multiprocessing shared_memory9905279
Ref: 8b9905279
Ref: library/multiprocessing shared_memory multiprocessing-shared-memory-shared-memory-for-direct-access-across-processes9905279
Ref: 2ff19905279
Ref: library/multiprocessing shared_memory multiprocessing shared_memory SharedMemory9906756
Ref: 154f9906756
Ref: library/multiprocessing shared_memory multiprocessing shared_memory SharedMemory close9909887
Ref: 2ff39909887
Ref: library/multiprocessing shared_memory multiprocessing shared_memory SharedMemory unlink9910364
Ref: 2ff49910364
Ref: library/multiprocessing shared_memory multiprocessing shared_memory SharedMemory buf9910984
Ref: 2ff59910984
Ref: library/multiprocessing shared_memory multiprocessing shared_memory SharedMemory name9911079
Ref: 2ff69911079
Ref: library/multiprocessing shared_memory multiprocessing shared_memory SharedMemory size9911171
Ref: 2ff79911171
Ref: library/multiprocessing shared_memory multiprocessing managers SharedMemoryManager9914241
Ref: 2ff29914241
Ref: library/multiprocessing shared_memory multiprocessing managers SharedMemoryManager SharedMemory9915481
Ref: 2ff89915481
Ref: library/multiprocessing shared_memory multiprocessing managers SharedMemoryManager ShareableList9915666
Ref: 2ff99915666
Ref: library/multiprocessing shared_memory multiprocessing shared_memory ShareableList9917477
Ref: 18729917477
Ref: library/multiprocessing shared_memory multiprocessing shared_memory ShareableList count9919982
Ref: 2ffa9919982
Ref: library/multiprocessing shared_memory multiprocessing shared_memory ShareableList index9920059
Ref: 2ffb9920059
Ref: library/multiprocessing shared_memory multiprocessing shared_memory ShareableList format9920217
Ref: 2ffc9920217
Ref: library/multiprocessing shared_memory multiprocessing shared_memory ShareableList shm9920359
Ref: 2ffd9920359
Ref: multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取-Footnote-19922881
Ref: multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取-Footnote-29922971
Ref: multiprocessing shared_memory --- 對於共享記憶體的跨行程直接存取-Footnote-39922998
Node: concurrent 套件9923054
Ref: library/concurrent doc9923279
Ref: 2ffe9923279
Ref: library/concurrent the-concurrent-package9923279
Ref: 2fff9923279
Node: concurrent futures --- 啟動平行任務9923431
Ref: library/concurrent futures doc9923607
Ref: 30009923607
Ref: library/concurrent futures concurrent-futures-launching-parallel-tasks9923607
Ref: 30019923607
Ref: library/concurrent futures module-concurrent futures9923607
Ref: 1a9923607
Ref: concurrent futures --- 啟動平行任務-Footnote-19924626
Ref: concurrent futures --- 啟動平行任務-Footnote-29924712
Node: Executor 物件9924799
Ref: library/concurrent futures executor-objects9924919
Ref: 30039924919
Ref: library/concurrent futures concurrent futures Executor9924968
Ref: 30029924968
Ref: library/concurrent futures concurrent futures Executor submit9925139
Ref: a259925139
Ref: library/concurrent futures concurrent futures Executor map9925532
Ref: d8a9925532
Ref: library/concurrent futures concurrent futures Executor shutdown9926879
Ref: 8929926879
Node: ThreadPoolExecutor9928846
Ref: library/concurrent futures threadpoolexecutor9928994
Ref: 30049928994
Ref: library/concurrent futures concurrent futures ThreadPoolExecutor9930070
Ref: 6e69930070
Node: ThreadPoolExecutor 範例9932383
Ref: library/concurrent futures id19932463
Ref: 30069932463
Ref: library/concurrent futures threadpoolexecutor-example9932463
Ref: 114a9932463
Node: ProcessPoolExecutor9933667
Ref: library/concurrent futures processpoolexecutor9933813
Ref: 30079933813
Ref: library/concurrent futures concurrent futures ProcessPoolExecutor9934581
Ref: 8939934581
Node: ProcessPoolExecutor 範例9938007
Ref: library/concurrent futures id29938089
Ref: 30099938089
Ref: library/concurrent futures processpoolexecutor-example9938089
Ref: 114b9938089
Node: Future 物件9938991
Ref: library/concurrent futures future-objects9939131
Ref: 300a9939131
Ref: library/concurrent futures concurrent futures Future9939318
Ref: 11499939318
Ref: library/concurrent futures concurrent futures Future cancel9939516
Ref: 300b9939516
Ref: library/concurrent futures concurrent futures Future cancelled9939752
Ref: 300c9939752
Ref: library/concurrent futures concurrent futures Future running9939851
Ref: 300d9939851
Ref: library/concurrent futures concurrent futures Future done9939957
Ref: 300e9939957
Ref: library/concurrent futures concurrent futures Future result9940063
Ref: 300f9940063
Ref: library/concurrent futures concurrent futures Future exception9940645
Ref: 30109940645
Ref: library/concurrent futures concurrent futures Future add_done_callback9941236
Ref: 30119941236
Ref: library/concurrent futures concurrent futures Future set_running_or_notify_cancel9941964
Ref: 30129941964
Ref: library/concurrent futures concurrent futures Future set_result9942858
Ref: 30139942858
Ref: library/concurrent futures concurrent futures Future set_exception9943224
Ref: 30149943224
Node: 模組函式9943631
Ref: library/concurrent futures module-functions9943764
Ref: 30159943764
Ref: library/concurrent futures concurrent futures wait9943805
Ref: 17659943805
Ref: library/concurrent futures concurrent futures FIRST_COMPLETED9945031
Ref: 30169945031
Ref: library/concurrent futures concurrent futures FIRST_EXCEPTION9945281
Ref: 30179945281
Ref: library/concurrent futures concurrent futures ALL_COMPLETED9945735
Ref: 30189945735
Ref: library/concurrent futures concurrent futures as_completed9945879
Ref: 15419945879
Ref: 模組函式-Footnote-19946822
Node: 例外類別9946864
Ref: library/concurrent futures exception-classes9946975
Ref: 30199946975
Ref: library/concurrent futures concurrent futures CancelledError9947016
Ref: 97e9947016
Ref: library/concurrent futures concurrent futures TimeoutError9947102
Ref: 301a9947102
Ref: library/concurrent futures concurrent futures BrokenExecutor9947343
Ref: 301b9947343
Ref: library/concurrent futures concurrent futures InvalidStateError9947576
Ref: 14ff9947576
Ref: library/concurrent futures concurrent futures thread BrokenThreadPool9947726
Ref: 30059947726
Ref: library/concurrent futures concurrent futures process BrokenProcessPool9947965
Ref: 30089947965
Node: subprocess --- 子行程管理9948307
Ref: library/subprocess doc9948491
Ref: 301c9948491
Ref: library/subprocess module-subprocess9948491
Ref: c19948491
Ref: library/subprocess subprocess-subprocess-management9948491
Ref: 301d9948491
Ref: subprocess --- 子行程管理-Footnote-19949679
Ref: subprocess --- 子行程管理-Footnote-29949749
Node: Using the subprocess Module9949791
Ref: library/subprocess using-the-subprocess-module9949915
Ref: 301e9949915
Ref: library/subprocess subprocess run9950218
Ref: b2c9950218
Ref: library/subprocess subprocess CompletedProcess9954775
Ref: e159954775
Ref: library/subprocess subprocess CompletedProcess args9954909
Ref: 30239954909
Ref: library/subprocess subprocess CompletedProcess returncode9955028
Ref: 30249955028
Ref: library/subprocess subprocess CompletedProcess stdout9955299
Ref: 30259955299
Ref: library/subprocess subprocess CompletedProcess stderr9955727
Ref: 30269955727
Ref: library/subprocess subprocess CompletedProcess check_returncode9955966
Ref: 30279955966
Ref: library/subprocess subprocess DEVNULL9956133
Ref: 10e79956133
Ref: library/subprocess subprocess PIPE9956381
Ref: b2d9956381
Ref: library/subprocess subprocess STDOUT9956647
Ref: 30209956647
Ref: library/subprocess subprocess SubprocessError9956856
Ref: 30289956856
Ref: library/subprocess subprocess TimeoutExpired9956984
Ref: 30229956984
Ref: library/subprocess subprocess TimeoutExpired cmd9957140
Ref: 30299957140
Ref: library/subprocess subprocess TimeoutExpired timeout9957223
Ref: 302a9957223
Ref: library/subprocess subprocess TimeoutExpired output9957280
Ref: 302b9957280
Ref: library/subprocess subprocess TimeoutExpired stdout9957660
Ref: 302c9957660
Ref: library/subprocess subprocess TimeoutExpired stderr9957752
Ref: 302d9957752
Ref: library/subprocess subprocess CalledProcessError9958214
Ref: 12b89958214
Ref: library/subprocess subprocess CalledProcessError returncode9958473
Ref: 302f9958473
Ref: library/subprocess subprocess CalledProcessError cmd9958638
Ref: 30309958638
Ref: library/subprocess subprocess CalledProcessError output9958721
Ref: 30319958721
Ref: library/subprocess subprocess CalledProcessError stdout9958889
Ref: 30329958889
Ref: library/subprocess subprocess CalledProcessError stderr9958981
Ref: 30339958981
Node: Frequently Used Arguments9959276
Ref: library/subprocess frequently-used-arguments9959391
Ref: 301f9959391
Ref: library/subprocess id19959391
Ref: 30349959391
Node: Popen Constructor9963545
Ref: library/subprocess popen-constructor9963678
Ref: 30399963678
Ref: library/subprocess subprocess Popen9963973
Ref: 17d9963973
Ref: Popen Constructor-Footnote-19981538
Node: 例外<6>9981598
Ref: library/subprocess exceptions9981697
Ref: 304a9981697
Node: 安全性注意事項9982945
Ref: library/subprocess security-considerations9983091
Ref: 30389983091
Ref: library/subprocess subprocess-security9983091
Ref: 304b9983091
Ref: 安全性注意事項-Footnote-19984195
Ref: 安全性注意事項-Footnote-29984265
Node: Popen Objects9984321
Ref: library/subprocess popen-objects9984461
Ref: 304d9984461
Ref: library/subprocess subprocess Popen poll9984578
Ref: 304e9984578
Ref: library/subprocess subprocess Popen wait9984738
Ref: c8b9984738
Ref: library/subprocess subprocess Popen communicate9985746
Ref: 30219985746
Ref: library/subprocess subprocess Popen send_signal9987494
Ref: 134c9987494
Ref: library/subprocess subprocess Popen terminate9987881
Ref: 134a9987881
Ref: library/subprocess subprocess Popen kill9988100
Ref: 134b9988100
Ref: library/subprocess subprocess Popen args9988406
Ref: 304f9988406
Ref: library/subprocess subprocess Popen stdin9988586
Ref: 30359988586
Ref: library/subprocess subprocess Popen stdout9989024
Ref: 30369989024
Ref: library/subprocess subprocess Popen stderr9989534
Ref: 30379989534
Ref: library/subprocess subprocess Popen pid9990305
Ref: 30509990305
Ref: library/subprocess subprocess Popen returncode9990484
Ref: 18ac9990484
Node: Windows Popen Helpers9990979
Ref: library/subprocess windows-popen-helpers9991118
Ref: 30519991118
Ref: library/subprocess subprocess STARTUPINFO9991272
Ref: 303d9991272
Ref: library/subprocess subprocess STARTUPINFO dwFlags9991690
Ref: 30529991690
Ref: library/subprocess subprocess STARTUPINFO hStdInput9992001
Ref: 30539992001
Ref: library/subprocess subprocess STARTUPINFO hStdOutput9992320
Ref: 30559992320
Ref: library/subprocess subprocess STARTUPINFO hStdError9992626
Ref: 30569992626
Ref: library/subprocess subprocess STARTUPINFO wShowWindow9992929
Ref: 30579992929
Ref: library/subprocess subprocess STARTUPINFO lpAttributeList9993418
Ref: bb59993418
Ref: Windows Popen Helpers-Footnote-19994670
Ref: Windows Popen Helpers-Footnote-29994742
Ref: Windows Popen Helpers-Footnote-39994814
Node: Windows Constants9994903
Ref: library/subprocess windows-constants9994978
Ref: 305a9994978
Ref: library/subprocess subprocess STD_INPUT_HANDLE9995100
Ref: 305b9995100
Ref: library/subprocess subprocess STD_OUTPUT_HANDLE9995239
Ref: 305c9995239
Ref: library/subprocess subprocess STD_ERROR_HANDLE9995389
Ref: 305d9995389
Ref: library/subprocess subprocess SW_HIDE9995537
Ref: 30599995537
Ref: library/subprocess subprocess STARTF_USESTDHANDLES9995628
Ref: 30549995628
Ref: library/subprocess subprocess STARTF_USESHOWWINDOW9995861
Ref: 30589995861
Ref: library/subprocess subprocess STARTF_FORCEONFEEDBACK9996016
Ref: 305e9996016
Ref: library/subprocess subprocess STARTF_FORCEOFFFEEDBACK9996312
Ref: 305f9996312
Ref: library/subprocess subprocess CREATE_NEW_CONSOLE9996524
Ref: 303e9996524
Ref: library/subprocess subprocess CREATE_NEW_PROCESS_GROUP9996671
Ref: 303f9996671
Ref: library/subprocess subprocess ABOVE_NORMAL_PRIORITY_CLASS9996996
Ref: 30409996996
Ref: library/subprocess subprocess BELOW_NORMAL_PRIORITY_CLASS9997204
Ref: 30419997204
Ref: library/subprocess subprocess HIGH_PRIORITY_CLASS9997411
Ref: 30429997411
Ref: library/subprocess subprocess IDLE_PRIORITY_CLASS9997601
Ref: 30439997601
Ref: library/subprocess subprocess NORMAL_PRIORITY_CLASS9997801
Ref: 30449997801
Ref: library/subprocess subprocess REALTIME_PRIORITY_CLASS9998006
Ref: 30459998006
Ref: library/subprocess subprocess CREATE_NO_WINDOW9998540
Ref: 30469998540
Ref: library/subprocess subprocess DETACHED_PROCESS9998726
Ref: 30479998726
Ref: library/subprocess subprocess CREATE_DEFAULT_ERROR_MODE9998982
Ref: 30489998982
Ref: library/subprocess subprocess CREATE_BREAKAWAY_FROM_JOB9999386
Ref: 30499999386
Node: Older high-level API9999587
Ref: library/subprocess call-function-trio9999765
Ref: 30609999765
Ref: library/subprocess older-high-level-api9999765
Ref: 30619999765
Ref: library/subprocess subprocess call10000013
Ref: b2e10000013
Ref: library/subprocess subprocess check_call10001396
Ref: 302e10001396
Ref: library/subprocess subprocess check_output10003059
Ref: f6410003059
Node: Replacing Older Functions with the subprocess Module10005585
Ref: library/subprocess replacing-older-functions-with-the-subprocess-module10005775
Ref: 306210005775
Ref: library/subprocess subprocess-replacements10005775
Ref: 112210005775
Node: Replacing /bin/sh shell command substitution10006933
Ref: library/subprocess replacing-bin-sh-shell-command-substitution10007099
Ref: 306310007099
Node: Replacing shell pipeline10007305
Ref: library/subprocess replacing-shell-pipeline10007499
Ref: 306410007499
Node: Replacing os system10008150
Ref: library/subprocess replacing-os-system10008329
Ref: 306510008329
Node: Replacing the os spawn family10009279
Ref: library/subprocess replacing-the-os-spawn-family10009472
Ref: 306610009472
Node: Replacing os popen os popen2 os popen310010105
Ref: library/subprocess replacing-os-popen-os-popen2-os-popen310010321
Ref: 306710010321
Node: Replacing functions from the popen2 module10011616
Ref: library/subprocess replacing-functions-from-the-popen2-module10011794
Ref: 306810011794
Node: Legacy Shell Invocation Functions10013110
Ref: library/subprocess legacy-shell-invocation-functions10013286
Ref: 306910013286
Ref: library/subprocess subprocess getstatusoutput10013650
Ref: f6510013650
Ref: library/subprocess subprocess getoutput10014960
Ref: 170010014960
Node: 註解10015506
Ref: library/subprocess notes10015621
Ref: 306a10015621
Node: Converting an argument sequence to a string on Windows10015789
Ref: library/subprocess converting-an-argument-sequence-to-a-string-on-windows10015923
Ref: 306b10015923
Ref: library/subprocess converting-argument-sequence10015923
Ref: 303a10015923
Ref: library/subprocess disable-vfork10017082
Ref: 306c10017082
Node: 停用 vfork 或 posix_spawn10017082
Ref: library/subprocess disable-posix-spawn10017216
Ref: 306d10017216
Ref: library/subprocess disabling-use-of-vfork-or-posix-spawn10017216
Ref: 306e10017216
Node: sched --- 事件排程器10018533
Ref: library/sched doc10018724
Ref: 306f10018724
Ref: library/sched module-sched10018724
Ref: ad10018724
Ref: library/sched sched-event-scheduler10018724
Ref: 307010018724
Ref: library/sched sched scheduler10018973
Ref: 10bf10018973
Ref: sched --- 事件排程器-Footnote-110020943
Node: 排程器物件10021008
Ref: library/sched id110021085
Ref: 307110021085
Ref: library/sched scheduler-objects10021085
Ref: 307210021085
Ref: library/sched sched scheduler enterabs10021192
Ref: 10c110021192
Ref: library/sched sched scheduler enter10021972
Ref: 10c010021972
Ref: library/sched sched scheduler cancel10022346
Ref: 183210022346
Ref: library/sched sched scheduler empty10022518
Ref: 307310022518
Ref: library/sched sched scheduler run10022607
Ref: 10be10022607
Ref: library/sched sched scheduler queue10023594
Ref: 307410023594
Node: queue --- 同步佇列 synchronized queue 類別10023866
Ref: library/queue doc10024055
Ref: 307510024055
Ref: library/queue module-queue10024055
Ref: a410024055
Ref: library/queue queue-a-synchronized-queue-class10024055
Ref: 307610024055
Ref: library/queue queue Queue10025367
Ref: 131c10025367
Ref: library/queue queue LifoQueue10025691
Ref: 213310025691
Ref: library/queue queue PriorityQueue10026001
Ref: 213410026001
Ref: library/queue queue SimpleQueue10026912
Ref: b0e10026912
Ref: library/queue queue Empty10027062
Ref: 2f8a10027062
Ref: library/queue queue Full10027251
Ref: 2f8b10027251
Ref: library/queue queue ShutDown10027427
Ref: 22010027427
Ref: queue --- 同步佇列 synchronized queue 類別-Footnote-110027711
Node: 佇列物件10027776
Ref: library/queue queue-objects10027900
Ref: 307b10027900
Ref: library/queue queueobjects10027900
Ref: 307c10027900
Ref: library/queue queue Queue qsize10028070
Ref: 307d10028070
Ref: library/queue queue Queue empty10028263
Ref: 307e10028263
Ref: library/queue queue Queue full10028551
Ref: 307f10028551
Ref: library/queue queue Queue put10028837
Ref: 307910028837
Ref: library/queue queue Queue put_nowait10029494
Ref: 307a10029494
Ref: library/queue queue Queue get10029579
Ref: 307710029579
Ref: library/queue queue Queue get_nowait10030604
Ref: 307810030604
Ref: library/queue queue Queue task_done10030809
Ref: 2f8610030809
Ref: library/queue queue Queue join10031520
Ref: 2f8710031520
Node: Terminating queues10032565
Ref: library/queue terminating-queues10032632
Ref: 308010032632
Ref: library/queue queue Queue shutdown10032783
Ref: 21f10032783
Node: SimpleQueue 物件10033401
Ref: library/queue simplequeue-objects10033525
Ref: 308110033525
Ref: library/queue queue SimpleQueue qsize10033649
Ref: 308210033649
Ref: library/queue queue SimpleQueue empty10033793
Ref: 308310033793
Ref: library/queue queue SimpleQueue put10033992
Ref: 308410033992
Ref: library/queue queue SimpleQueue put_nowait10034769
Ref: 308510034769
Ref: library/queue queue SimpleQueue get10034916
Ref: 308610034916
Ref: library/queue queue SimpleQueue get_nowait10035501
Ref: 308710035501
Node: contextvars --- 情境變數10035964
Ref: library/contextvars doc10036159
Ref: 308810036159
Ref: library/contextvars contextvars-context-variables10036159
Ref: 308910036159
Ref: library/contextvars module-contextvars10036159
Ref: 1d10036159
Ref: contextvars --- 情境變數-Footnote-110036993
Node: Context Variables10037035
Ref: library/contextvars context-variables10037151
Ref: 308d10037151
Ref: library/contextvars contextvars ContextVar10037206
Ref: 308a10037206
Ref: library/contextvars contextvars ContextVar name10037914
Ref: 308f10037914
Ref: library/contextvars contextvars ContextVar get10038040
Ref: 308e10038040
Ref: library/contextvars contextvars ContextVar set10038527
Ref: 309010038527
Ref: library/contextvars contextvars ContextVar reset10038923
Ref: 309210038923
Ref: library/contextvars contextvars Token10039447
Ref: 309110039447
Ref: library/contextvars contextvars Token var10039722
Ref: 309310039722
Ref: library/contextvars contextvars Token old_value10039857
Ref: 309410039857
Ref: library/contextvars contextvars Token MISSING10040146
Ref: 309510040146
Node: Manual Context Management10040236
Ref: library/contextvars manual-context-management10040376
Ref: 309610040376
Ref: library/contextvars contextvars copy_context10040447
Ref: 308b10040447
Ref: library/contextvars contextvars Context10040923
Ref: 308c10040923
Ref: library/contextvars contextvars Context run10041516
Ref: 14fa10041516
Ref: library/contextvars contextvars Context copy10042943
Ref: 309710042943
Ref: library/contextvars contextvars Context get10043386
Ref: 309810043386
Ref: library/contextvars contextvars Context keys10043828
Ref: 309910043828
Ref: library/contextvars contextvars Context values10043919
Ref: 309a10043919
Ref: library/contextvars contextvars Context items10044020
Ref: 309b10044020
Node: asyncio support10044159
Ref: library/contextvars asyncio-support10044273
Ref: 309c10044273
Node: _thread --- 低階執行緒 API10045828
Ref: library/_thread doc10045966
Ref: 309d10045966
Ref: library/_thread module-_thread10045966
Ref: 210045966
Ref: library/_thread thread-low-level-threading-api10045966
Ref: 309e10045966
Ref: library/_thread thread error10046697
Ref: 309f10046697
Ref: library/_thread thread LockType10046864
Ref: 30a010046864
Ref: library/_thread thread start_new_thread10046928
Ref: 17a10046928
Ref: library/_thread thread interrupt_main10047914
Ref: 7e710047914
Ref: library/_thread thread exit10048747
Ref: 30a110048747
Ref: library/_thread thread allocate_lock10048879
Ref: 30a210048879
Ref: library/_thread thread get_ident10049023
Ref: 30a310049023
Ref: library/_thread thread get_native_id10049383
Ref: 30a410049383
Ref: library/_thread thread stack_size10049896
Ref: 30a510049896
Ref: library/_thread thread TIMEOUT_MAX10051031
Ref: 30a610051031
Ref: library/_thread thread lock acquire10051281
Ref: 30a710051281
Ref: library/_thread thread lock release10052289
Ref: 30a810052289
Ref: library/_thread thread lock locked10052412
Ref: 30a910052412
Node: Networking and Interprocess Communication10053757
Ref: library/ipc doc10053949
Ref: 30aa10053949
Ref: library/ipc ipc10053949
Ref: 30ab10053949
Ref: library/ipc networking-and-interprocess-communication10053949
Ref: 30ac10053949
Node: asyncio --- 非同步 I/O10054936
Ref: library/asyncio doc10055077
Ref: 30ad10055077
Ref: library/asyncio asyncio-asynchronous-i-o10055077
Ref: 30ae10055077
Ref: library/asyncio module-asyncio10055077
Ref: 810055077
Ref: library/asyncio asyncio-cli10056810
Ref: 30b910056810
Node: Runners 執行器10057918
Ref: library/asyncio-runner doc10058021
Ref: 30ba10058021
Ref: library/asyncio-runner runners10058021
Ref: 30bb10058021
Ref: Runners 執行器-Footnote-110058464
Node: 運行一個 asyncio 程式10058540
Ref: library/asyncio-runner running-an-asyncio-program10058652
Ref: 30bc10058652
Ref: library/asyncio-runner asyncio run10058721
Ref: 42310058721
Node: Runner context manager10060407
Ref: library/asyncio-runner runner-context-manager10060558
Ref: 30be10060558
Ref: library/asyncio-runner asyncio Runner10060623
Ref: 5a510060623
Ref: library/asyncio-runner asyncio Runner run10061765
Ref: 15a510061765
Ref: library/asyncio-runner asyncio Runner close10062260
Ref: 30bf10062260
Ref: library/asyncio-runner asyncio Runner get_loop10062483
Ref: 30c010062483
Node: Handling Keyboard Interruption10062925
Ref: library/asyncio-runner handling-keyboard-interruption10063040
Ref: 30c110063040
Node: 協程與任務10064530
Ref: library/asyncio-task doc10064648
Ref: 30c210064648
Ref: library/asyncio-task coroutines-and-tasks10064648
Ref: 30c310064648
Node: 協程<3>10065105
Ref: library/asyncio-task coroutine10065185
Ref: 30af10065185
Ref: library/asyncio-task coroutines10065185
Ref: 30c410065185
Ref: 協程<3>-Footnote-110068459
Node: Awaitables10068538
Ref: library/asyncio-task asyncio-awaitables10068641
Ref: 30c510068641
Ref: library/asyncio-task awaitables10068641
Ref: 30c610068641
Node: Creating Tasks10071189
Ref: library/asyncio-task creating-tasks10071300
Ref: 30c710071300
Ref: library/asyncio-task asyncio create_task10071456
Ref: 5a110071456
Ref: Creating Tasks-Footnote-110073470
Node: Task Cancellation10073543
Ref: library/asyncio-task task-cancellation10073655
Ref: 30c810073655
Node: Task Groups10074725
Ref: library/asyncio-task task-groups10074831
Ref: 30c910074831
Ref: library/asyncio-task taskgroups10074831
Ref: 30ca10074831
Ref: library/asyncio-task asyncio TaskGroup10074998
Ref: 19b10074998
Ref: library/asyncio-task asyncio TaskGroup create_task10075264
Ref: 1a210075264
Node: Sleeping10079212
Ref: library/asyncio-task sleeping10079327
Ref: 30cb10079327
Ref: library/asyncio-task asyncio sleep10079366
Ref: a1210079366
Ref: library/asyncio-task asyncio-example-sleep10079855
Ref: 30cc10079855
Node: Running Tasks Concurrently10080507
Ref: library/asyncio-task running-tasks-concurrently10080629
Ref: 30cd10080629
Ref: library/asyncio-task asyncio gather10080704
Ref: 5a210080704
Ref: library/asyncio-task asyncio-example-gather10082425
Ref: 30ce10082425
Node: Eager Task Factory10084528
Ref: library/asyncio-task eager-task-factory10084669
Ref: 30cf10084669
Ref: library/asyncio-task id210084669
Ref: 30d010084669
Ref: library/asyncio-task asyncio eager_task_factory10084728
Ref: 41e10084728
Ref: library/asyncio-task asyncio create_eager_task_factory10085872
Ref: 41f10085872
Node: Shielding From Cancellation10086540
Ref: library/asyncio-task shielding-from-cancellation10086663
Ref: 30d110086663
Ref: library/asyncio-task asyncio shield10086740
Ref: a1310086740
Node: Timeouts10088395
Ref: library/asyncio-task timeouts10088518
Ref: 30d210088518
Ref: library/asyncio-task asyncio timeout10088557
Ref: 5a310088557
Ref: library/asyncio-task asyncio Timeout10090301
Ref: 15c510090301
Ref: library/asyncio-task asyncio Timeout when10090781
Ref: 30d410090781
Ref: library/asyncio-task asyncio Timeout reschedule10090953
Ref: 30d310090953
Ref: library/asyncio-task asyncio Timeout expired10091058
Ref: 30d510091058
Ref: library/asyncio-task asyncio timeout_at10091899
Ref: 172710091899
Ref: library/asyncio-task asyncio wait_for10092513
Ref: 5a410092513
Ref: library/asyncio-task asyncio-example-waitfor10093311
Ref: 30d610093311
Node: Waiting Primitives10094144
Ref: library/asyncio-task waiting-primitives10094258
Ref: 30d710094258
Ref: library/asyncio-task asyncio wait10094317
Ref: 42610094317
Ref: library/asyncio-task asyncio FIRST_COMPLETED10095520
Ref: 30d810095520
Ref: library/asyncio-task asyncio FIRST_EXCEPTION10095831
Ref: 30d910095831
Ref: library/asyncio-task asyncio ALL_COMPLETED10096354
Ref: 30da10096354
Ref: library/asyncio-task asyncio as_completed10096898
Ref: 19010096898
Node: Running in Threads10099731
Ref: library/asyncio-task running-in-threads10099866
Ref: 30db10099866
Ref: library/asyncio-task asyncio to_thread10099925
Ref: 88d10099925
Node: Scheduling From Other Threads10102137
Ref: library/asyncio-task scheduling-from-other-threads10102267
Ref: 30dc10102267
Ref: library/asyncio-task asyncio run_coroutine_threadsafe10102348
Ref: 82610102348
Node: Introspection10103774
Ref: library/asyncio-task introspection10103897
Ref: 30de10103897
Ref: library/asyncio-task asyncio current_task10103946
Ref: 42410103946
Ref: library/asyncio-task asyncio all_tasks10104223
Ref: 8fa10104223
Ref: library/asyncio-task asyncio iscoroutine10104481
Ref: 42510104481
Node: Task Object10104604
Ref: library/asyncio-task task-object10104689
Ref: 30df10104689
Ref: library/asyncio-task asyncio Task10104734
Ref: 48010104734
Ref: library/asyncio-task asyncio Task done10107494
Ref: 30e310107494
Ref: library/asyncio-task asyncio Task result10107710
Ref: 30e410107710
Ref: library/asyncio-task asyncio Task exception10108195
Ref: 30e610108195
Ref: library/asyncio-task asyncio Task add_done_callback10108680
Ref: 30e710108680
Ref: library/asyncio-task asyncio Task remove_done_callback10108995
Ref: 30e810108995
Ref: library/asyncio-task asyncio Task get_stack10109293
Ref: 30e910109293
Ref: library/asyncio-task asyncio Task print_stack10110289
Ref: 166110110289
Ref: library/asyncio-task asyncio Task get_coro10110781
Ref: 97f10110781
Ref: library/asyncio-task asyncio Task get_context10111195
Ref: 30ea10111195
Ref: library/asyncio-task asyncio Task get_name10111360
Ref: 98210111360
Ref: library/asyncio-task asyncio Task set_name10111634
Ref: 98110111634
Ref: library/asyncio-task asyncio Task cancel10111970
Ref: 19d10111970
Ref: library/asyncio-task asyncio-example-task-cancel10113052
Ref: 30eb10113052
Ref: library/asyncio-task asyncio Task cancelled10114307
Ref: 30e010114307
Ref: library/asyncio-task asyncio Task uncancel10114606
Ref: 1a110114606
Ref: library/asyncio-task asyncio Task cancelling10116908
Ref: 1a010116908
Node: 串流10117714
Ref: library/asyncio-stream doc10117863
Ref: 30ec10117863
Ref: library/asyncio-stream asyncio-streams10117863
Ref: 30b010117863
Ref: library/asyncio-stream streams10117863
Ref: 30ed10117863
Ref: library/asyncio-stream asyncio-example-stream10118237
Ref: 30ee10118237
Ref: library/asyncio-stream asyncio open_connection10118951
Ref: abb10118951
Ref: library/asyncio-stream asyncio start_server10120159
Ref: library/asyncio-stream asyncio open_unix_connection10121666
Ref: 30f210121666
Ref: library/asyncio-stream asyncio start_unix_server10122583
Ref: 30f410122583
Ref: 串流-Footnote-110123611
Node: StreamReader10123687
Ref: library/asyncio-stream streamreader10123763
Ref: 30f510123763
Ref: library/asyncio-stream asyncio StreamReader10123810
Ref: 17c810123810
Ref: library/asyncio-stream asyncio StreamReader feed_eof10124190
Ref: 30f610124190
Ref: library/asyncio-stream asyncio StreamReader read10124252
Ref: 30f710124252
Ref: library/asyncio-stream asyncio StreamReader readline10124942
Ref: 30f810124942
Ref: library/asyncio-stream asyncio StreamReader readexactly10125289
Ref: c2210125289
Ref: library/asyncio-stream asyncio StreamReader readuntil10125630
Ref: 19a10125630
Ref: library/asyncio-stream asyncio StreamReader at_eof10126914
Ref: 30fb10126914
Node: StreamWriter10127051
Ref: library/asyncio-stream streamwriter10127146
Ref: 30fc10127146
Ref: library/asyncio-stream asyncio StreamWriter10127193
Ref: 15fc10127193
Ref: library/asyncio-stream asyncio StreamWriter write10127461
Ref: 30fd10127461
Ref: library/asyncio-stream asyncio StreamWriter writelines10127816
Ref: 30fe10127816
Ref: library/asyncio-stream asyncio StreamWriter close10128237
Ref: 30f010128237
Ref: library/asyncio-stream asyncio StreamWriter can_write_eof10128485
Ref: 30ff10128485
Ref: library/asyncio-stream asyncio StreamWriter write_eof10128652
Ref: 310010128652
Ref: library/asyncio-stream asyncio StreamWriter transport10128770
Ref: 310110128770
Ref: library/asyncio-stream asyncio StreamWriter get_extra_info10128843
Ref: 310210128843
Ref: library/asyncio-stream asyncio StreamWriter drain10129007
Ref: 16b110129007
Ref: library/asyncio-stream asyncio StreamWriter start_tls10129530
Ref: 5a910129530
Ref: library/asyncio-stream asyncio StreamWriter is_closing10130527
Ref: ab010130527
Ref: library/asyncio-stream asyncio StreamWriter wait_closed10130669
Ref: aaf10130669
Node: 範例<20>10131005
Ref: library/asyncio-stream examples10131079
Ref: 30ef10131079
Node: 使用串流的 TCP echo 客戶端10131283
Ref: library/asyncio-stream asyncio-tcp-echo-client-streams10131407
Ref: 310310131407
Ref: library/asyncio-stream tcp-echo-client-using-streams10131407
Ref: 310410131407
Node: 使用串流的 TCP echo 伺服器10132192
Ref: library/asyncio-stream asyncio-tcp-echo-server-streams10132343
Ref: 310610132343
Ref: library/asyncio-stream tcp-echo-server-using-streams10132343
Ref: 310710132343
Node: 獲取 HTTP 標頭10133383
Ref: library/asyncio-stream get-http-headers10133555
Ref: 310910133555
Node: 註冊一個使用串流來等待資料的開放 socket10134829
Ref: library/asyncio-stream asyncio-example-create-connection-streams10134958
Ref: 310a10134958
Ref: library/asyncio-stream register-an-open-socket-to-wait-for-data-using-streams10134958
Ref: 310b10134958
Node: 同步化原始物件 Synchronization Primitives10136374
Ref: library/asyncio-sync doc10136517
Ref: 310f10136517
Ref: library/asyncio-sync asyncio-sync10136517
Ref: 30b310136517
Ref: library/asyncio-sync synchronization-primitives10136517
Ref: 311010136517
Ref: 同步化原始物件 Synchronization Primitives-Footnote-110137659
Node: Lock10137732
Ref: library/asyncio-sync lock10137835
Ref: 311110137835
Ref: library/asyncio-sync asyncio Lock10137866
Ref: a1410137866
Ref: library/asyncio-sync asyncio Lock acquire10138555
Ref: 311210138555
Ref: library/asyncio-sync asyncio Lock release10139033
Ref: 311310139033
Ref: library/asyncio-sync asyncio Lock locked10139271
Ref: 311410139271
Node: Event10139365
Ref: library/asyncio-sync event10139486
Ref: 311510139486
Ref: library/asyncio-sync asyncio Event10139519
Ref: a1510139519
Ref: library/asyncio-sync asyncio-example-sync-event10140094
Ref: 311910140094
Ref: library/asyncio-sync asyncio Event wait10140724
Ref: 311810140724
Ref: library/asyncio-sync asyncio Event set10140951
Ref: 311610140951
Ref: library/asyncio-sync asyncio Event clear10141078
Ref: 311710141078
Ref: library/asyncio-sync asyncio Event is_set10141283
Ref: 311a10141283
Node: Condition10141370
Ref: library/asyncio-sync condition10141496
Ref: 311b10141496
Ref: library/asyncio-sync asyncio Condition10141537
Ref: a1610141537
Ref: library/asyncio-sync asyncio Condition acquire10142692
Ref: 311c10142692
Ref: library/asyncio-sync asyncio Condition notify10142893
Ref: 157010142893
Ref: library/asyncio-sync asyncio Condition locked10143254
Ref: 311d10143254
Ref: library/asyncio-sync asyncio Condition notify_all10143344
Ref: 311e10143344
Ref: library/asyncio-sync asyncio Condition release10143740
Ref: 311f10143740
Ref: library/asyncio-sync asyncio Condition wait10143915
Ref: 159b10143915
Ref: library/asyncio-sync asyncio Condition wait_for10144665
Ref: 312010144665
Node: Semaphore10145031
Ref: library/asyncio-sync semaphore10145168
Ref: 312110145168
Ref: library/asyncio-sync asyncio Semaphore10145209
Ref: a1710145209
Ref: library/asyncio-sync asyncio Semaphore acquire10146313
Ref: 159c10146313
Ref: library/asyncio-sync asyncio Semaphore locked10146577
Ref: 312310146577
Ref: library/asyncio-sync asyncio Semaphore release10146673
Ref: 312210146673
Node: BoundedSemaphore10146998
Ref: library/asyncio-sync boundedsemaphore10147133
Ref: 312410147133
Ref: library/asyncio-sync asyncio BoundedSemaphore10147188
Ref: a1810147188
Node: Barrier10147581
Ref: library/asyncio-sync barrier10147698
Ref: 312510147698
Ref: library/asyncio-sync asyncio Barrier10147735
Ref: 5a610147735
Ref: library/asyncio-sync asyncio-example-barrier10148355
Ref: 312710148355
Ref: library/asyncio-sync asyncio Barrier wait10149224
Ref: 312610149224
Ref: library/asyncio-sync asyncio Barrier reset10150301
Ref: 312810150301
Ref: library/asyncio-sync asyncio Barrier abort10150601
Ref: 312910150601
Ref: library/asyncio-sync asyncio Barrier parties10150917
Ref: 312a10150917
Ref: library/asyncio-sync asyncio Barrier n_waiting10151004
Ref: 312b10151004
Ref: library/asyncio-sync asyncio Barrier broken10151121
Ref: 312c10151121
Ref: library/asyncio-sync asyncio BrokenBarrierError10151235
Ref: 5a710151235
Node: 子行程10151709
Ref: library/asyncio-subprocess doc10151859
Ref: 312d10151859
Ref: library/asyncio-subprocess asyncio-subprocess10151859
Ref: 30b110151859
Ref: library/asyncio-subprocess subprocesses10151859
Ref: 312e10151859
Ref: library/asyncio-subprocess asyncio-example-subprocess-shell10152139
Ref: 312f10152139
Ref: 子行程-Footnote-110153411
Ref: 子行程-Footnote-210153490
Node: 建立子行程10153574
Ref: library/asyncio-subprocess creating-subprocesses10153653
Ref: 313110153653
Ref: library/asyncio-subprocess asyncio create_subprocess_exec10153701
Ref: a1a10153701
Ref: library/asyncio-subprocess asyncio create_subprocess_shell10154298
Ref: a1b10154298
Ref: 建立子行程-Footnote-110155839
Node: 常數<6>10155909
Ref: library/asyncio-subprocess constants10156026
Ref: 313a10156026
Ref: library/asyncio-subprocess asyncio subprocess PIPE10156059
Ref: 313b10156059
Ref: library/asyncio-subprocess asyncio subprocess STDOUT10156493
Ref: 313f10156493
Ref: library/asyncio-subprocess asyncio subprocess DEVNULL10156681
Ref: 314010156681
Node: Interacting with Subprocesses10156964
Ref: library/asyncio-subprocess interacting-with-subprocesses10157057
Ref: 314110157057
Ref: library/asyncio-subprocess asyncio subprocess Process10157388
Ref: 313210157388
Ref: library/asyncio-subprocess asyncio subprocess Process wait10158353
Ref: 314210158353
Ref: library/asyncio-subprocess asyncio subprocess Process communicate10158864
Ref: 162d10158864
Ref: library/asyncio-subprocess asyncio subprocess Process send_signal10160212
Ref: 14eb10160212
Ref: library/asyncio-subprocess asyncio subprocess Process terminate10160628
Ref: 314510160628
Ref: library/asyncio-subprocess asyncio subprocess Process kill10160910
Ref: 314610160910
Ref: library/asyncio-subprocess asyncio subprocess Process stdin10161148
Ref: 313c10161148
Ref: library/asyncio-subprocess asyncio subprocess Process stdout10161300
Ref: 313d10161300
Ref: library/asyncio-subprocess asyncio subprocess Process stderr10161455
Ref: 313e10161455
Ref: library/asyncio-subprocess asyncio subprocess Process pid10161949
Ref: 314710161949
Ref: library/asyncio-subprocess asyncio subprocess Process returncode10162179
Ref: 314410162179
Node: 子行程與線程10162526
Ref: library/asyncio-subprocess asyncio-subprocess-threads10162629
Ref: 314310162629
Ref: library/asyncio-subprocess subprocess-and-threads10162629
Ref: 314810162629
Node: 範例<21>10163480
Ref: library/asyncio-subprocess examples10163583
Ref: 313010163583
Ref: library/asyncio-subprocess asyncio-example-create-subprocess-exec10163761
Ref: 314a10163761
Node: 佇列 Queues10164564
Ref: library/asyncio-queue doc10164675
Ref: 314c10164675
Ref: library/asyncio-queue asyncio-queues10164675
Ref: 30b210164675
Ref: library/asyncio-queue queues10164675
Ref: 314d10164675
Ref: 佇列 Queues-Footnote-110165370
Node: Queue10165444
Ref: library/asyncio-queue queue10165540
Ref: 314f10165540
Ref: library/asyncio-queue asyncio Queue10165573
Ref: a1910165573
Ref: library/asyncio-queue asyncio Queue maxsize10166184
Ref: 315210166184
Ref: library/asyncio-queue asyncio Queue empty10166258
Ref: 315310166258
Ref: library/asyncio-queue asyncio Queue full10166365
Ref: 315410166365
Ref: library/asyncio-queue asyncio Queue get10166615
Ref: 315010166615
Ref: library/asyncio-queue asyncio Queue get_nowait10166936
Ref: 315510166936
Ref: library/asyncio-queue asyncio Queue join10167086
Ref: d6e10167086
Ref: library/asyncio-queue asyncio Queue put10167611
Ref: 315710167611
Ref: library/asyncio-queue asyncio Queue put_nowait10167899
Ref: 315810167899
Ref: library/asyncio-queue asyncio Queue qsize10168075
Ref: 315110168075
Ref: library/asyncio-queue asyncio Queue shutdown10168147
Ref: 19610168147
Ref: library/asyncio-queue asyncio Queue task_done10168818
Ref: d6f10168818
Node: Priority Queue（優先佇列）10169597
Ref: library/asyncio-queue priority-queue10169712
Ref: 315a10169712
Ref: library/asyncio-queue asyncio PriorityQueue10169793
Ref: 315b10169793
Node: LIFO Queue10169999
Ref: library/asyncio-queue lifo-queue10170118
Ref: 315c10170118
Ref: library/asyncio-queue asyncio LifoQueue10170161
Ref: 315d10170161
Node: 例外<7>10170280
Ref: library/asyncio-queue exceptions10170377
Ref: 315e10170377
Ref: library/asyncio-queue asyncio QueueEmpty10170410
Ref: 315610170410
Ref: library/asyncio-queue asyncio QueueFull10170545
Ref: 315910170545
Ref: library/asyncio-queue asyncio QueueShutDown10170710
Ref: 19710170710
Node: 範例<22>10170895
Ref: library/asyncio-queue examples10170973
Ref: 314e10170973
Ref: library/asyncio-queue asyncio-example-queue-dist10171006
Ref: 315f10171006
Node: 例外<8>10172743
Ref: library/asyncio-exceptions doc10172857
Ref: 316010172857
Ref: library/asyncio-exceptions asyncio-exceptions10172857
Ref: 316110172857
Ref: library/asyncio-exceptions exceptions10172857
Ref: 316210172857
Ref: library/asyncio-exceptions asyncio TimeoutError10173002
Ref: 164210173002
Ref: library/asyncio-exceptions asyncio CancelledError10173248
Ref: 19e10173248
Ref: library/asyncio-exceptions asyncio InvalidStateError10173609
Ref: 30e510173609
Ref: library/asyncio-exceptions asyncio SendfileNotAvailableError10173817
Ref: 316310173817
Ref: library/asyncio-exceptions asyncio IncompleteReadError10173995
Ref: 182210173995
Ref: library/asyncio-exceptions asyncio IncompleteReadError expected10174192
Ref: 316410174192
Ref: library/asyncio-exceptions asyncio IncompleteReadError partial10174276
Ref: 30f910174276
Ref: library/asyncio-exceptions asyncio LimitOverrunError10174369
Ref: 30fa10174369
Ref: library/asyncio-exceptions asyncio LimitOverrunError consumed10174545
Ref: 316510174545
Ref: 例外<8>-Footnote-110174650
Node: 事件迴圈10174729
Ref: library/asyncio-eventloop doc10174837
Ref: 316610174837
Ref: library/asyncio-eventloop asyncio-event-loop10174837
Ref: d1f10174837
Ref: library/asyncio-eventloop event-loop10174837
Ref: 316710174837
Ref: library/asyncio-eventloop asyncio get_running_loop10175567
Ref: aae10175567
Ref: library/asyncio-eventloop asyncio get_event_loop10175850
Ref: 2a310175850
Ref: library/asyncio-eventloop asyncio set_event_loop10176815
Ref: 16cf10176815
Ref: library/asyncio-eventloop asyncio new_event_loop10176928
Ref: 30bd10176928
Ref: 事件迴圈-Footnote-110178052
Ref: 事件迴圈-Footnote-210178126
Node: 事件迴圈方法10178206
Ref: library/asyncio-eventloop asyncio-event-loop-methods10178294
Ref: 316e10178294
Ref: library/asyncio-eventloop event-loop-methods10178294
Ref: 316910178294
Node: 啟動和停止迴圈10178801
Ref: library/asyncio-eventloop running-and-stopping-the-loop10178904
Ref: 316f10178904
Ref: library/asyncio-eventloop asyncio loop run_until_complete10178962
Ref: c1e10178962
Ref: library/asyncio-eventloop asyncio loop run_forever10179252
Ref: 317010179252
Ref: library/asyncio-eventloop asyncio loop stop10179935
Ref: c2310179935
Ref: library/asyncio-eventloop asyncio loop is_running10179989
Ref: 317110179989
Ref: library/asyncio-eventloop asyncio loop is_closed10180090
Ref: d6a10180090
Ref: library/asyncio-eventloop asyncio loop close10180181
Ref: 317210180181
Ref: library/asyncio-eventloop asyncio loop shutdown_asyncgens10180500
Ref: c2410180500
Ref: library/asyncio-eventloop asyncio loop shutdown_default_executor10181129
Ref: 88c10181129
Node: 排程回呼函式10182017
Ref: library/asyncio-eventloop scheduling-callbacks10182156
Ref: 317310182156
Ref: library/asyncio-eventloop asyncio loop call_soon10182209
Ref: aa710182209
Ref: library/asyncio-eventloop asyncio loop call_soon_threadsafe10182871
Ref: aa810182871
Ref: library/asyncio-eventloop asyncio-pass-keywords10183490
Ref: 317410183490
Ref: 排程回呼函式-Footnote-110183984
Node: 排程延遲的回呼函式10184026
Ref: library/asyncio-eventloop asyncio-delayed-calls10184168
Ref: 317510184168
Ref: library/asyncio-eventloop scheduling-delayed-callbacks10184168
Ref: 317610184168
Ref: library/asyncio-eventloop asyncio loop call_later10184374
Ref: aa910184374
Ref: library/asyncio-eventloop asyncio loop call_at10185439
Ref: aaa10185439
Ref: library/asyncio-eventloop asyncio loop time10186136
Ref: 317710186136
Ref: 排程延遲的回呼函式-Footnote-110186550
Ref: 排程延遲的回呼函式-Footnote-210186592
Node: 建立 Futures 和 Tasks10186634
Ref: library/asyncio-eventloop creating-futures-and-tasks10186776
Ref: 317810186776
Ref: library/asyncio-eventloop asyncio loop create_future10186844
Ref: c2010186844
Ref: library/asyncio-eventloop asyncio loop create_task10187165
Ref: 98010187165
Ref: library/asyncio-eventloop asyncio loop set_task_factory10187970
Ref: d6c10187970
Ref: library/asyncio-eventloop asyncio loop get_task_factory10188448
Ref: d6d10188448
Node: 打開網路連線10188567
Ref: library/asyncio-eventloop opening-network-connections10188703
Ref: 317910188703
Ref: library/asyncio-eventloop asyncio loop create_connection10188756
Ref: 5a810188756
Ref: library/asyncio-eventloop asyncio loop create_datagram_endpoint10194960
Ref: 6d710194960
Ref: library/asyncio-eventloop asyncio loop create_unix_connection10198197
Ref: 30f310198197
Ref: 打開網路連線-Footnote-110199180
Ref: 打開網路連線-Footnote-210199239
Node: 建立網路伺服器10199298
Ref: library/asyncio-eventloop creating-network-servers10199422
Ref: 318210199422
Ref: library/asyncio-eventloop loop-create-server10199480
Ref: 30b410199480
Ref: library/asyncio-eventloop asyncio loop create_server10199480
Ref: ab610199480
Ref: library/asyncio-eventloop asyncio loop create_unix_server10203782
Ref: 19410203782
Ref: library/asyncio-eventloop asyncio loop connect_accepted_socket10204975
Ref: abd10204975
Node: 傳輸檔案10206426
Ref: library/asyncio-eventloop transferring-files10206542
Ref: 318410206542
Ref: library/asyncio-eventloop asyncio loop sendfile10206585
Ref: 318510206585
Node: TLS 升級10207570
Ref: library/asyncio-eventloop tls-upgrade10207686
Ref: 318610207686
Ref: library/asyncio-eventloop asyncio loop start_tls10207727
Ref: aac10207727
Node: 監視檔案描述器10209548
Ref: library/asyncio-eventloop watching-file-descriptors10209678
Ref: 318710209678
Ref: library/asyncio-eventloop asyncio loop add_reader10209736
Ref: 310e10209736
Ref: library/asyncio-eventloop asyncio loop remove_reader10209916
Ref: 318810209916
Ref: library/asyncio-eventloop asyncio loop add_writer10210082
Ref: 318910210082
Ref: library/asyncio-eventloop asyncio loop remove_writer10210365
Ref: 318a10210365
Node: 直接使用 socket 物件10210615
Ref: library/asyncio-eventloop working-with-socket-objects-directly10210738
Ref: 318c10210738
Ref: library/asyncio-eventloop asyncio loop sock_recv10211088
Ref: bb810211088
Ref: library/asyncio-eventloop asyncio loop sock_recv_into10211531
Ref: aad10211531
Ref: library/asyncio-eventloop asyncio loop sock_recvfrom10211816
Ref: 5ab10211816
Ref: library/asyncio-eventloop asyncio loop sock_recvfrom_into10212126
Ref: 5ac10212126
Ref: library/asyncio-eventloop asyncio loop sock_sendall10212472
Ref: bb910212472
Ref: library/asyncio-eventloop asyncio loop sock_sendto10213131
Ref: 5aa10213131
Ref: library/asyncio-eventloop asyncio loop sock_connect10213414
Ref: d7010213414
Ref: library/asyncio-eventloop asyncio loop sock_accept10214014
Ref: bba10214014
Ref: library/asyncio-eventloop asyncio loop sock_sendfile10214746
Ref: ab110214746
Node: DNS10215896
Ref: library/asyncio-eventloop dns10216010
Ref: 318d10216010
Ref: library/asyncio-eventloop asyncio loop getaddrinfo10216039
Ref: bbb10216039
Ref: library/asyncio-eventloop asyncio loop getnameinfo10216203
Ref: bbc10216203
Node: 使用管道10217012
Ref: library/asyncio-eventloop working-with-pipes10217111
Ref: 318e10217111
Ref: library/asyncio-eventloop asyncio loop connect_read_pipe10217154
Ref: 313610217154
Ref: library/asyncio-eventloop asyncio loop connect_write_pipe10217720
Ref: 313710217720
Node: Unix 訊號10218542
Ref: library/asyncio-eventloop unix-signals10218683
Ref: 319110218683
Ref: library/asyncio-eventloop loop-add-signal-handler10218726
Ref: 30b610218726
Ref: library/asyncio-eventloop asyncio loop add_signal_handler10218726
Ref: 319210218726
Ref: library/asyncio-eventloop asyncio loop remove_signal_handler10219463
Ref: 319310219463
Node: 在執行緒池或行程池中執行程式碼10219771
Ref: library/asyncio-eventloop executing-code-in-thread-or-process-pools10219916
Ref: 319410219916
Ref: library/asyncio-eventloop asyncio loop run_in_executor10220014
Ref: 88e10220014
Ref: library/asyncio-eventloop asyncio loop set_default_executor10222634
Ref: 6e710222634
Node: 錯誤處理 API10222942
Ref: library/asyncio-eventloop error-handling-api10223094
Ref: 319510223094
Ref: library/asyncio-eventloop asyncio loop set_exception_handler10223201
Ref: 319610223201
Ref: library/asyncio-eventloop asyncio loop get_exception_handler10224026
Ref: c2110224026
Ref: library/asyncio-eventloop asyncio loop default_exception_handler10224215
Ref: 319810224215
Ref: library/asyncio-eventloop asyncio loop call_exception_handler10224558
Ref: 319710224558
Node: 啟用除錯模式10225568
Ref: library/asyncio-eventloop enabling-debug-mode10225690
Ref: 319910225690
Ref: library/asyncio-eventloop asyncio loop get_debug10225743
Ref: d6910225743
Ref: library/asyncio-eventloop asyncio loop set_debug10225983
Ref: d6810225983
Ref: library/asyncio-eventloop asyncio loop slow_callback_duration10226186
Ref: 319a10226186
Node: 運行子行程10226462
Ref: library/asyncio-eventloop running-subprocesses10226559
Ref: 319b10226559
Ref: library/asyncio-eventloop loop-subprocess-exec10227059
Ref: 30b510227059
Ref: library/asyncio-eventloop asyncio loop subprocess_exec10227059
Ref: 313310227059
Ref: library/asyncio-eventloop asyncio loop subprocess_shell10230456
Ref: 313410230456
Ref: 運行子行程-Footnote-110231617
Node: 回呼處理10231687
Ref: library/asyncio-eventloop callback-handles10231797
Ref: 316a10231797
Ref: library/asyncio-eventloop asyncio Handle10231840
Ref: 19a910231840
Ref: library/asyncio-eventloop asyncio Handle get_context10231984
Ref: 319e10231984
Ref: library/asyncio-eventloop asyncio Handle cancel10232133
Ref: 319f10232133
Ref: library/asyncio-eventloop asyncio Handle cancelled10232251
Ref: abe10232251
Ref: library/asyncio-eventloop asyncio TimerHandle10232374
Ref: 166f10232374
Ref: library/asyncio-eventloop asyncio TimerHandle when10232570
Ref: aba10232570
Node: Server 物件10232826
Ref: library/asyncio-eventloop server-objects10232936
Ref: 316b10232936
Ref: library/asyncio-eventloop asyncio Server10233214
Ref: ab510233214
Ref: library/asyncio-eventloop asyncio Server close10233860
Ref: 30f110233860
Ref: library/asyncio-eventloop asyncio Server close_clients10234221
Ref: 19810234221
Ref: library/asyncio-eventloop asyncio Server abort_clients10234589
Ref: 19910234589
Ref: library/asyncio-eventloop asyncio Server get_loop10235031
Ref: ab410235031
Ref: library/asyncio-eventloop asyncio Server start_serving10235154
Ref: ab710235154
Ref: library/asyncio-eventloop asyncio Server serve_forever10235729
Ref: ab810235729
Ref: library/asyncio-eventloop asyncio Server is_serving10236572
Ref: ab910236572
Ref: library/asyncio-eventloop asyncio Server wait_closed10236711
Ref: 15c410236711
Ref: library/asyncio-eventloop asyncio Server sockets10236842
Ref: bbd10236842
Ref: library/asyncio-eventloop asyncio-event-loops10237171
Ref: 31a110237171
Node: 事件迴圈實作10237171
Ref: library/asyncio-eventloop asyncio-event-loop-implementations10237279
Ref: 31a210237279
Ref: library/asyncio-eventloop event-loop-implementations10237279
Ref: 316c10237279
Ref: library/asyncio-eventloop asyncio SelectorEventLoop10237514
Ref: 5ad10237514
Ref: library/asyncio-eventloop asyncio ProactorEventLoop10238130
Ref: 5ae10238130
Ref: library/asyncio-eventloop asyncio EventLoop10238411
Ref: 15f110238411
Ref: library/asyncio-eventloop asyncio AbstractEventLoop10238722
Ref: 90310238722
Ref: 事件迴圈實作-Footnote-110238994
Node: 範例<23>10239080
Ref: library/asyncio-eventloop examples10239166
Ref: 316d10239166
Node: 使用 call_soon 的 Hello World 範例10239764
Ref: library/asyncio-eventloop asyncio-example-lowlevel-helloworld10239895
Ref: 31a310239895
Ref: library/asyncio-eventloop hello-world-with-call-soon10239895
Ref: 31a410239895
Node: 使用 call_later 顯示目前日期10240654
Ref: library/asyncio-eventloop asyncio-example-call-later10240836
Ref: 31a510240836
Ref: library/asyncio-eventloop display-the-current-date-with-call-later10240836
Ref: 31a610240836
Node: 監聽檔案描述器以進行讀取事件10241764
Ref: library/asyncio-eventloop asyncio-example-watch-fd10241954
Ref: 310d10241954
Ref: library/asyncio-eventloop watch-a-file-descriptor-for-read-events10241954
Ref: 31a710241954
Node: 設定 SIGINT 和 SIGTERM 的訊號處理程式10243235
Ref: library/asyncio-eventloop asyncio-example-unix-signals10243380
Ref: 31a810243380
Ref: library/asyncio-eventloop set-signal-handlers-for-sigint-and-sigterm10243380
Ref: 31a910243380
Node: Futures10244298
Ref: library/asyncio-future doc10244412
Ref: 31aa10244412
Ref: library/asyncio-future asyncio-futures10244412
Ref: 30b810244412
Ref: library/asyncio-future futures10244412
Ref: 31ab10244412
Ref: Futures-Footnote-110244781
Node: Future 函式10244896
Ref: library/asyncio-future future-functions10244978
Ref: 31ac10244978
Ref: library/asyncio-future asyncio isfuture10245025
Ref: 31ad10245025
Ref: library/asyncio-future asyncio ensure_future10245377
Ref: c1d10245377
Ref: library/asyncio-future asyncio wrap_future10246647
Ref: 17c710246647
Node: Future 物件<2>10246995
Ref: library/asyncio-future future-object10247077
Ref: 31ae10247077
Ref: library/asyncio-future asyncio Future10247124
Ref: b7410247124
Ref: library/asyncio-future asyncio Future result10248160
Ref: 31af10248160
Ref: library/asyncio-future asyncio Future set_result10248804
Ref: 30e110248804
Ref: library/asyncio-future asyncio Future set_exception10249009
Ref: 30e210249009
Ref: library/asyncio-future asyncio Future done10249223
Ref: 31b010249223
Ref: library/asyncio-future asyncio Future cancelled10249534
Ref: 31b110249534
Ref: library/asyncio-future asyncio Future add_done_callback10249831
Ref: aab10249831
Ref: library/asyncio-future asyncio Future remove_done_callback10250792
Ref: 16c710250792
Ref: library/asyncio-future asyncio Future cancel10251010
Ref: 171f10251010
Ref: library/asyncio-future asyncio Future exception10251339
Ref: 31b210251339
Ref: library/asyncio-future asyncio Future get_loop10251791
Ref: ab310251791
Ref: library/asyncio-future asyncio-example-future10251924
Ref: 31b310251924
Ref: Future 物件<2>-Footnote-110254050
Node: 傳輸與協定10254092
Ref: library/asyncio-protocol doc10254202
Ref: 31b410254202
Ref: library/asyncio-protocol asyncio-transports-protocols10254202
Ref: 30b710254202
Ref: library/asyncio-protocol transports-and-protocols10254202
Ref: 31b510254202
Node: Transports10256530
Ref: library/asyncio-protocol asyncio-transport10256610
Ref: 317b10256610
Ref: library/asyncio-protocol transports10256610
Ref: 31b610256610
Ref: Transports-Footnote-110257349
Node: Transports Hierarchy10257428
Ref: library/asyncio-protocol transports-hierarchy10257518
Ref: 31bd10257518
Ref: library/asyncio-protocol asyncio BaseTransport10257581
Ref: 31b810257581
Ref: library/asyncio-protocol asyncio WriteTransport10257711
Ref: 319010257711
Ref: library/asyncio-protocol asyncio ReadTransport10258043
Ref: 318f10258043
Ref: library/asyncio-protocol asyncio Transport10258371
Ref: 31b910258371
Ref: library/asyncio-protocol asyncio DatagramTransport10258975
Ref: 16af10258975
Ref: library/asyncio-protocol asyncio SubprocessTransport10259219
Ref: 319d10259219
Node: Base Transport10259546
Ref: library/asyncio-protocol base-transport10259665
Ref: 31be10259665
Ref: library/asyncio-protocol asyncio BaseTransport close10259716
Ref: 317e10259716
Ref: library/asyncio-protocol asyncio BaseTransport is_closing10260143
Ref: c1f10260143
Ref: library/asyncio-protocol asyncio BaseTransport get_extra_info10260250
Ref: a3f10260250
Ref: library/asyncio-protocol asyncio BaseTransport set_protocol10262404
Ref: 31c310262404
Ref: library/asyncio-protocol asyncio BaseTransport get_protocol10262589
Ref: 31c410262589
Node: Read-only Transports10262667
Ref: library/asyncio-protocol read-only-transports10262787
Ref: 31c510262787
Ref: library/asyncio-protocol asyncio ReadTransport is_reading10262850
Ref: abf10262850
Ref: library/asyncio-protocol asyncio ReadTransport pause_reading10262983
Ref: ac110262983
Ref: library/asyncio-protocol asyncio ReadTransport resume_reading10263348
Ref: ac010263348
Node: Write-only Transports10263682
Ref: library/asyncio-protocol write-only-transports10263807
Ref: 31c610263807
Ref: library/asyncio-protocol asyncio WriteTransport abort10263872
Ref: 31a010263872
Ref: library/asyncio-protocol asyncio WriteTransport can_write_eof10264209
Ref: 31c710264209
Ref: library/asyncio-protocol asyncio WriteTransport get_write_buffer_size10264366
Ref: 31c910264366
Ref: library/asyncio-protocol asyncio WriteTransport get_write_buffer_limits10264493
Ref: d6b10264493
Ref: library/asyncio-protocol asyncio WriteTransport set_write_buffer_limits10264809
Ref: 31ca10264809
Ref: library/asyncio-protocol asyncio WriteTransport write10266219
Ref: 31cd10266219
Ref: library/asyncio-protocol asyncio WriteTransport writelines10266418
Ref: 162a10266418
Ref: library/asyncio-protocol asyncio WriteTransport write_eof10266702
Ref: 31c810266702
Node: Datagram Transports10266989
Ref: library/asyncio-protocol datagram-transports10267115
Ref: 31ce10267115
Ref: library/asyncio-protocol asyncio DatagramTransport sendto10267176
Ref: 19510267176
Ref: library/asyncio-protocol asyncio DatagramTransport abort10267786
Ref: 31cf10267786
Node: Subprocess Transports10268126
Ref: library/asyncio-protocol asyncio-subprocess-transports10268222
Ref: 313810268222
Ref: library/asyncio-protocol subprocess-transports10268222
Ref: 31d010268222
Ref: library/asyncio-protocol asyncio SubprocessTransport get_pid10268287
Ref: 31d110268287
Ref: library/asyncio-protocol asyncio SubprocessTransport get_pipe_transport10268385
Ref: 31d210268385
Ref: library/asyncio-protocol asyncio SubprocessTransport get_returncode10269131
Ref: 31d310269131
Ref: library/asyncio-protocol asyncio SubprocessTransport kill10269365
Ref: 31d410269365
Ref: library/asyncio-protocol asyncio SubprocessTransport send_signal10269633
Ref: 31d610269633
Ref: library/asyncio-protocol asyncio SubprocessTransport terminate10269792
Ref: 31d510269792
Ref: library/asyncio-protocol asyncio SubprocessTransport close10270118
Ref: 31d710270118
Node: Protocols10270342
Ref: library/asyncio-protocol asyncio-protocol10270441
Ref: 317a10270441
Ref: library/asyncio-protocol protocols10270441
Ref: 31b710270441
Ref: Protocols-Footnote-110271233
Node: Base Protocols10271311
Ref: library/asyncio-protocol base-protocols10271393
Ref: 31d810271393
Ref: library/asyncio-protocol asyncio BaseProtocol10271444
Ref: 31ba10271444
Ref: library/asyncio-protocol asyncio Protocol10271537
Ref: 31bb10271537
Ref: library/asyncio-protocol asyncio BufferedProtocol10271671
Ref: a4010271671
Ref: library/asyncio-protocol asyncio DatagramProtocol10271828
Ref: 67310271828
Ref: library/asyncio-protocol asyncio SubprocessProtocol10271945
Ref: 319c10271945
Node: Base Protocol10272112
Ref: library/asyncio-protocol base-protocol10272222
Ref: 31d910272222
Ref: library/asyncio-protocol asyncio BaseProtocol connection_made10272545
Ref: 317c10272545
Ref: library/asyncio-protocol asyncio BaseProtocol connection_lost10272799
Ref: 31bf10272799
Ref: library/asyncio-protocol asyncio BaseProtocol pause_writing10273342
Ref: 31cb10273342
Ref: library/asyncio-protocol asyncio BaseProtocol resume_writing10273456
Ref: 31cc10273456
Node: Streaming Protocols10273918
Ref: library/asyncio-protocol streaming-protocols10274042
Ref: 31da10274042
Ref: library/asyncio-protocol asyncio Protocol data_received10274452
Ref: 169010274452
Ref: library/asyncio-protocol asyncio Protocol eof_received10275131
Ref: 31db10275131
Node: Buffered Streaming Protocols10275991
Ref: library/asyncio-protocol buffered-streaming-protocols10276120
Ref: 31dc10276120
Ref: library/asyncio-protocol asyncio BufferedProtocol get_buffer10276813
Ref: 31dd10276813
Ref: library/asyncio-protocol asyncio BufferedProtocol buffer_updated10277286
Ref: 31de10277286
Ref: library/asyncio-protocol asyncio BufferedProtocol eof_received10277487
Ref: 31df10277487
Node: Datagram Protocols10278057
Ref: library/asyncio-protocol datagram-protocols10278187
Ref: 31e010278187
Ref: library/asyncio-protocol asyncio DatagramProtocol datagram_received10278385
Ref: 31e110278385
Ref: library/asyncio-protocol asyncio DatagramProtocol error_received10278650
Ref: 31e210278650
Node: Subprocess Protocols10279583
Ref: library/asyncio-protocol asyncio-subprocess-protocols10279676
Ref: 313910279676
Ref: library/asyncio-protocol subprocess-protocols10279676
Ref: 31e310279676
Ref: library/asyncio-protocol asyncio SubprocessProtocol pipe_data_received10279914
Ref: 16c910279914
Ref: library/asyncio-protocol asyncio SubprocessProtocol pipe_connection_lost10280187
Ref: 31e410280187
Ref: library/asyncio-protocol asyncio SubprocessProtocol process_exited10280397
Ref: 16c810280397
Node: 範例<24>10280613
Ref: library/asyncio-protocol examples10280693
Ref: 31bc10280693
Node: TCP Echo Server10280942
Ref: library/asyncio-protocol asyncio-example-tcp-echo-server-protocol10281028
Ref: 310810281028
Ref: library/asyncio-protocol tcp-echo-server10281028
Ref: 31e510281028
Node: TCP Echo Client10282301
Ref: library/asyncio-protocol asyncio-example-tcp-echo-client-protocol10282411
Ref: 310510282411
Ref: library/asyncio-protocol tcp-echo-client10282411
Ref: 31e610282411
Node: UDP Echo Server10283968
Ref: library/asyncio-protocol asyncio-udp-echo-server-protocol10284078
Ref: 318110284078
Ref: library/asyncio-protocol udp-echo-server10284078
Ref: 31e710284078
Node: UDP Echo Client10285214
Ref: library/asyncio-protocol asyncio-udp-echo-client-protocol10285336
Ref: 318010285336
Ref: library/asyncio-protocol udp-echo-client10285336
Ref: 31e810285336
Node: Connecting Existing Sockets10286868
Ref: library/asyncio-protocol asyncio-example-create-connection10287018
Ref: 310c10287018
Ref: library/asyncio-protocol connecting-existing-sockets10287018
Ref: 31e910287018
Node: loop subprocess_exec and SubprocessProtocol10288929
Ref: library/asyncio-protocol asyncio-example-subprocess-proto10289055
Ref: 314b10289055
Ref: library/asyncio-protocol loop-subprocess-exec-and-subprocessprotocol10289055
Ref: 31ea10289055
Node: Policies10291366
Ref: library/asyncio-policy doc10291481
Ref: 31eb10291481
Ref: library/asyncio-policy asyncio-policies10291481
Ref: 316810291481
Ref: library/asyncio-policy policies10291481
Ref: 31ec10291481
Node: Getting and Setting the Policy10292412
Ref: library/asyncio-policy asyncio-policy-get-set10292510
Ref: 31ed10292510
Ref: library/asyncio-policy getting-and-setting-the-policy10292510
Ref: 31f210292510
Ref: library/asyncio-policy asyncio get_event_loop_policy10292683
Ref: 31f310292683
Ref: library/asyncio-policy asyncio set_event_loop_policy10292775
Ref: 31f410292775
Node: Policy Objects10292954
Ref: library/asyncio-policy asyncio-policy-objects10293077
Ref: 31f010293077
Ref: library/asyncio-policy policy-objects10293077
Ref: 31f510293077
Ref: library/asyncio-policy asyncio AbstractEventLoopPolicy10293196
Ref: 31f110293196
Ref: library/asyncio-policy asyncio AbstractEventLoopPolicy get_event_loop10293292
Ref: 31f610293292
Ref: library/asyncio-policy asyncio AbstractEventLoopPolicy set_event_loop10293578
Ref: 31f710293578
Ref: library/asyncio-policy asyncio AbstractEventLoopPolicy new_event_loop10293683
Ref: 31f810293683
Ref: library/asyncio-policy asyncio AbstractEventLoopPolicy get_child_watcher10293828
Ref: 2a210293828
Ref: library/asyncio-policy asyncio AbstractEventLoopPolicy set_child_watcher10294103
Ref: 2a110294103
Ref: library/asyncio-policy asyncio-policy-builtin10294295
Ref: 31ee10294295
Ref: library/asyncio-policy asyncio DefaultEventLoopPolicy10294348
Ref: 31f910294348
Ref: library/asyncio-policy asyncio WindowsSelectorEventLoopPolicy10295041
Ref: 31fa10295041
Ref: library/asyncio-policy asyncio WindowsProactorEventLoopPolicy10295247
Ref: 31fb10295247
Node: Process Watchers10295453
Ref: library/asyncio-policy asyncio-watchers10295561
Ref: 314910295561
Ref: library/asyncio-policy process-watchers10295561
Ref: 31fc10295561
Ref: library/asyncio-policy asyncio get_child_watcher10296429
Ref: 2a010296429
Ref: library/asyncio-policy asyncio set_child_watcher10296569
Ref: 29f10296569
Ref: library/asyncio-policy asyncio AbstractChildWatcher10297034
Ref: 29d10297034
Ref: library/asyncio-policy asyncio AbstractChildWatcher add_child_handler10297076
Ref: 31fd10297076
Ref: library/asyncio-policy asyncio AbstractChildWatcher remove_child_handler10297469
Ref: 31fe10297469
Ref: library/asyncio-policy asyncio AbstractChildWatcher attach_loop10297720
Ref: 16d010297720
Ref: library/asyncio-policy asyncio AbstractChildWatcher is_active10297984
Ref: 31ff10297984
Ref: library/asyncio-policy asyncio AbstractChildWatcher close10298222
Ref: 320010298222
Ref: library/asyncio-policy asyncio ThreadedChildWatcher10298416
Ref: 42210298416
Ref: library/asyncio-policy asyncio MultiLoopChildWatcher10298889
Ref: 29b10298889
Ref: library/asyncio-policy asyncio SafeChildWatcher10299588
Ref: 29e10299588
Ref: library/asyncio-policy asyncio FastChildWatcher10300214
Ref: 29c10300214
Ref: library/asyncio-policy asyncio PidfdChildWatcher10300717
Ref: 42010300717
Node: Custom Policies10301309
Ref: library/asyncio-policy asyncio-custom-policies10301394
Ref: 31ef10301394
Ref: library/asyncio-policy custom-policies10301394
Ref: 320110301394
Node: 平臺支援10302003
Ref: library/asyncio-platforms doc10302109
Ref: 320210302109
Ref: library/asyncio-platforms asyncio-platform-support10302109
Ref: 318b10302109
Ref: library/asyncio-platforms platform-support10302109
Ref: 320310302109
Node: 所有平台10302398
Ref: library/asyncio-platforms all-platforms10302479
Ref: 320410302479
Node: Windows<72>10302634
Ref: library/asyncio-platforms windows10302733
Ref: 320510302733
Ref: Windows<72>-Footnote-110304557
Ref: Windows<72>-Footnote-210304722
Node: Windows 的子行程支援10304785
Ref: library/asyncio-platforms asyncio-windows-subprocess10304859
Ref: 313510304859
Ref: library/asyncio-platforms subprocess-support-on-windows10304859
Ref: 320710304859
Node: macOS<45>10305205
Ref: library/asyncio-platforms macos10305283
Ref: 320810305283
Node: 擴充10305918
Ref: library/asyncio-extending doc10306033
Ref: 320a10306033
Ref: library/asyncio-extending extending10306033
Ref: 320b10306033
Node: Writing a Custom Event Loop10306507
Ref: library/asyncio-extending writing-a-custom-event-loop10306622
Ref: 320c10306622
Node: Future and Task private constructors10307341
Ref: library/asyncio-extending future-and-task-private-constructors10307486
Ref: 320d10307486
Ref: library/asyncio-extending asyncio Future __init__10308050
Ref: 320e10308050
Ref: library/asyncio-extending asyncio Task __init__10308184
Ref: 320f10308184
Node: Task lifetime support10308492
Ref: library/asyncio-extending task-lifetime-support10308601
Ref: 321010308601
Ref: library/asyncio-extending asyncio _register_task10308837
Ref: 321110308837
Ref: library/asyncio-extending asyncio _unregister_task10308982
Ref: 321210308982
Ref: library/asyncio-extending asyncio _enter_task10309157
Ref: 321310309157
Ref: library/asyncio-extending asyncio _leave_task10309413
Ref: 321410309413
Node: 高階 API 索引10309635
Ref: library/asyncio-api-index doc10309755
Ref: 81c10309755
Ref: library/asyncio-api-index high-level-api-index10309755
Ref: 321510309755
Node: 任務 Tasks10310130
Ref: library/asyncio-api-index tasks10310221
Ref: 321610310221
Node: 佇列 Queues<2>10314424
Ref: library/asyncio-api-index queues10314546
Ref: 321710314546
Node: 子行程 Subprocesses10315435
Ref: library/asyncio-api-index subprocesses10315559
Ref: 321810315559
Node: 串流 Streams10316164
Ref: library/asyncio-api-index streams10316297
Ref: 321910316297
Node: 同步化 Synchronization10317690
Ref: library/asyncio-api-index synchronization10317810
Ref: 321a10317810
Node: 例外<9>10319255
Ref: library/asyncio-api-index exceptions10319352
Ref: 321b10319352
Node: 低階 API 索引10320102
Ref: library/asyncio-llapi-index doc10320237
Ref: 321c10320237
Ref: library/asyncio-llapi-index low-level-api-index10320237
Ref: 321d10320237
Node: 獲取事件迴圈10320460
Ref: library/asyncio-llapi-index obtaining-the-event-loop10320562
Ref: 321e10320562
Node: 事件迴圈方法<2>10321657
Ref: library/asyncio-llapi-index event-loop-methods10321774
Ref: 321f10321774
Node: 傳輸10334226
Ref: library/asyncio-llapi-index transports10334331
Ref: 322010334331
Node: 協定10340129
Ref: library/asyncio-llapi-index protocols10340234
Ref: 322110340234
Node: 事件迴圈 Policies10343598
Ref: library/asyncio-llapi-index event-loop-policies10343688
Ref: 322210343688
Node: 使用 asyncio 開發10344494
Ref: library/asyncio-dev doc10344603
Ref: 322310344603
Ref: library/asyncio-dev asyncio-dev10344603
Ref: 322410344603
Ref: library/asyncio-dev developing-with-asyncio10344603
Ref: 322510344603
Node: 除錯模式10345243
Ref: library/asyncio-dev asyncio-debug-mode10345377
Ref: 1c5110345377
Ref: library/asyncio-dev debug-mode10345377
Ref: 322610345377
Node: 並行性和多執行緒 Concurrency and Multithreading10347099
Ref: library/asyncio-dev asyncio-multithreading10347263
Ref: 30dd10347263
Ref: library/asyncio-dev concurrency-and-multithreading10347263
Ref: 322910347263
Node: 執行阻塞的程式10349654
Ref: library/asyncio-dev asyncio-handle-blocking10349818
Ref: 322a10349818
Ref: library/asyncio-dev running-blocking-code10349818
Ref: 322b10349818
Node: 日誌記錄10350283
Ref: library/asyncio-dev asyncio-logger10350437
Ref: 322710350437
Ref: library/asyncio-dev logging10350437
Ref: 322c10350437
Node: 偵測從未被等待的 never-awaited 協程10350926
Ref: library/asyncio-dev asyncio-coroutine-not-scheduled10351106
Ref: 322810351106
Ref: library/asyncio-dev detect-never-awaited-coroutines10351106
Ref: 322e10351106
Node: 偵測從未被獲取的 never-retrieved 例外10352140
Ref: library/asyncio-dev detect-never-retrieved-exceptions10352299
Ref: 322f10352299
Ref: 偵測從未被獲取的 never-retrieved 例外-Footnote-110353954
Node: socket --- 低階網路介面10354019
Ref: library/socket doc10354211
Ref: 323010354211
Ref: library/socket module-socket10354211
Ref: b810354211
Ref: library/socket socket-low-level-networking-interface10354211
Ref: 323110354211
Ref: socket --- 低階網路介面-Footnote-110355666
Node: Socket 系列家族10355732
Ref: library/socket socket-families10355841
Ref: 323210355841
Ref: library/socket host-port10357035
Ref: 323310357035
Ref: Socket 系列家族-Footnote-110367430
Ref: Socket 系列家族-Footnote-210367472
Node: 模組內容<4>10367517
Ref: library/socket module-contents10367648
Ref: 323a10367648
Node: 例外<10>10367825
Ref: library/socket exceptions10367905
Ref: 323b10367905
Ref: library/socket socket error10367936
Ref: ff810367936
Ref: library/socket socket herror10368128
Ref: 323c10368128
Ref: library/socket socket gaierror10368748
Ref: 165510368748
Ref: library/socket socket timeout10369348
Ref: 7d810369348
Ref: 例外<10>-Footnote-110369978
Node: 常數<7>10370020
Ref: library/socket constants10370118
Ref: 323e10370118
Ref: library/socket socket AF_UNIX10370300
Ref: 172410370300
Ref: library/socket socket AF_INET10370327
Ref: 172210370327
Ref: library/socket socket AF_INET610370354
Ref: 172310370354
Ref: library/socket socket AF_UNSPEC10370670
Ref: 318310370670
Ref: library/socket socket SOCK_STREAM10370883
Ref: 128610370883
Ref: library/socket socket SOCK_DGRAM10370914
Ref: 128510370914
Ref: library/socket socket SOCK_RAW10370944
Ref: 323f10370944
Ref: library/socket socket SOCK_RDM10370972
Ref: 324010370972
Ref: library/socket socket SOCK_SEQPACKET10371000
Ref: 324110371000
Ref: library/socket socket SOCK_CLOEXEC10371303
Ref: bb210371303
Ref: library/socket socket SOCK_NONBLOCK10371335
Ref: bb110371335
Ref: library/socket socket-unix-constants10371750
Ref: 317f10371750
Ref: library/socket socket SOMAXCONN10371767
Ref: e0110371767
Ref: library/socket socket AF_CAN10374388
Ref: 323410374388
Ref: library/socket socket PF_CAN10374414
Ref: 324210374414
Ref: library/socket socket CAN_BCM10374755
Ref: f4510374755
Ref: library/socket socket CAN_RAW_FD_FRAMES10375183
Ref: e6c10375183
Ref: library/socket socket CAN_RAW_JOIN_FILTERS10375598
Ref: 8d510375598
Ref: library/socket socket CAN_ISOTP10375899
Ref: 323510375899
Ref: library/socket socket CAN_J193910376150
Ref: 8d610376150
Ref: library/socket socket AF_DIVERT10376385
Ref: 324310376385
Ref: library/socket socket PF_DIVERT10376414
Ref: 324410376414
Ref: library/socket socket AF_PACKET10376640
Ref: 323610376640
Ref: library/socket socket PF_PACKET10376669
Ref: 324510376669
Ref: library/socket socket ETH_P_ALL10376885
Ref: 16ab10376885
Ref: library/socket socket AF_RDS10377234
Ref: 324610377234
Ref: library/socket socket PF_RDS10377260
Ref: 324710377260
Ref: library/socket socket SOL_RDS10377286
Ref: 324810377286
Ref: library/socket socket SIO_RCVALL10377528
Ref: 324910377528
Ref: library/socket socket SIO_KEEPALIVE_VALS10377558
Ref: 324a10377558
Ref: library/socket socket SIO_LOOPBACK_FAST_PATH10377596
Ref: c7b10377596
Ref: library/socket socket AF_ALG10378016
Ref: c7e10378016
Ref: library/socket socket SOL_ALG10378042
Ref: 324b10378042
Ref: library/socket socket AF_VSOCK10378211
Ref: b1910378211
Ref: library/socket socket IOCTL_VM_SOCKETS_GET_LOCAL_CID10378239
Ref: 324c10378239
Ref: library/socket socket AF_LINK10378455
Ref: f4610378455
Ref: library/socket socket has_ipv610378554
Ref: 324d10378554
Ref: library/socket socket BDADDR_ANY10378688
Ref: 324e10378688
Ref: library/socket socket BDADDR_LOCAL10378718
Ref: 324f10378718
Ref: library/socket socket HCI_FILTER10378989
Ref: 325010378989
Ref: library/socket socket HCI_TIME_STAMP10379019
Ref: 325110379019
Ref: library/socket socket HCI_DATA_DIR10379053
Ref: 325210379053
Ref: library/socket socket AF_QIPCRTR10379323
Ref: 323710379323
Ref: library/socket socket SCM_CREDS210379516
Ref: 325310379516
Ref: library/socket socket LOCAL_CREDS10379546
Ref: 325410379546
Ref: library/socket socket LOCAL_CREDS_PERSISTENT10379577
Ref: 325510379577
Ref: library/socket socket SO_INCOMING_CPU10380014
Ref: 325610380014
Ref: library/socket socket AF_HYPERV10380234
Ref: 323810380234
Ref: library/socket socket HV_PROTOCOL_RAW10380263
Ref: 325710380263
Ref: library/socket socket HVSOCKET_CONNECT_TIMEOUT10380298
Ref: 325810380298
Ref: library/socket socket HVSOCKET_CONNECT_TIMEOUT_MAX10380342
Ref: 325910380342
Ref: library/socket socket HVSOCKET_CONNECTED_SUSPEND10380390
Ref: 325a10380390
Ref: library/socket socket HVSOCKET_ADDRESS_FLAG_PASSTHRU10380436
Ref: 325b10380436
Ref: library/socket socket HV_GUID_ZERO10380486
Ref: 325c10380486
Ref: library/socket socket HV_GUID_WILDCARD10380518
Ref: 325d10380518
Ref: library/socket socket HV_GUID_BROADCAST10380554
Ref: 325e10380554
Ref: library/socket socket HV_GUID_CHILDREN10380591
Ref: 325f10380591
Ref: library/socket socket HV_GUID_LOOPBACK10380627
Ref: 326010380627
Ref: library/socket socket HV_GUID_PARENT10380663
Ref: 326110380663
Ref: library/socket socket-ethernet-types10380846
Ref: 16ac10380846
Ref: library/socket socket ETHERTYPE_ARP10380846
Ref: 326210380846
Ref: library/socket socket ETHERTYPE_IP10380879
Ref: 326310380879
Ref: library/socket socket ETHERTYPE_IPV610380911
Ref: 326410380911
Ref: library/socket socket ETHERTYPE_VLAN10380945
Ref: 326510380945
Ref: library/socket socket SHUT_RD10381113
Ref: 326610381113
Ref: library/socket socket SHUT_WR10381140
Ref: 326710381140
Ref: library/socket socket SHUT_RDWR10381167
Ref: 326810381167
Ref: 常數<7>-Footnote-110381366
Ref: 常數<7>-Footnote-210381418
Ref: 常數<7>-Footnote-310381464
Node: 函式<7>10381544
Ref: library/socket functions10381623
Ref: 326a10381623
Node: 建立 sockets10381716
Ref: library/socket creating-sockets10381800
Ref: 326b10381800
Ref: library/socket socket socket10381911
Ref: d4710381911
Ref: library/socket socket socketpair10384454
Ref: b9c10384454
Ref: library/socket socket create_connection10385186
Ref: 61810385186
Ref: library/socket socket create_server10386682
Ref: 9cf10386682
Ref: library/socket socket has_dualstack_ipv610388471
Ref: 9d010388471
Ref: library/socket socket fromfd10388666
Ref: 326d10388666
Ref: library/socket socket fromshare10389549
Ref: bae10389549
Ref: library/socket socket SocketType10389800
Ref: 326f10389800
Node: 其他函式<2>10389955
Ref: library/socket other-functions10390039
Ref: 327010390039
Ref: library/socket socket close10390156
Ref: b1710390156
Ref: library/socket socket getaddrinfo10390428
Ref: 165410390428
Ref: library/socket socket getfqdn10393136
Ref: 167f10393136
Ref: library/socket socket gethostbyname10393751
Ref: 327110393751
Ref: library/socket socket gethostbyname_ex10394394
Ref: 17d010394394
Ref: library/socket socket gethostname10395181
Ref: 2a1110395181
Ref: library/socket socket gethostbyaddr10395601
Ref: 17cf10395601
Ref: library/socket socket getnameinfo10396341
Ref: 15be10396341
Ref: library/socket socket getprotobyname10397112
Ref: 327210397112
Ref: library/socket socket getservbyname10397600
Ref: 327310397600
Ref: library/socket socket getservbyport10398051
Ref: 327410398051
Ref: library/socket socket ntohl10398491
Ref: 327510398491
Ref: library/socket socket ntohs10398746
Ref: 82410398746
Ref: library/socket socket htonl10399118
Ref: 327610399118
Ref: library/socket socket htons10399373
Ref: 82310399373
Ref: library/socket socket inet_aton10399745
Ref: 90510399745
Ref: library/socket socket inet_ntoa10400670
Ref: 327710400670
Ref: library/socket socket inet_pton10401484
Ref: 90610401484
Ref: library/socket socket inet_ntop10402267
Ref: f4710402267
Ref: library/socket socket CMSG_LEN10403243
Ref: 193d10403243
Ref: library/socket socket CMSG_SPACE10403921
Ref: 193c10403921
Ref: library/socket socket getdefaulttimeout10404818
Ref: 326e10404818
Ref: library/socket socket setdefaulttimeout10405094
Ref: 323d10405094
Ref: library/socket socket sethostname10405380
Ref: 10d410405380
Ref: library/socket socket if_nameindex10405709
Ref: 9d110405709
Ref: library/socket socket if_nametoindex10406513
Ref: 9d210406513
Ref: library/socket socket if_indextoname10406970
Ref: 9d310406970
Ref: library/socket socket send_fds10407429
Ref: 8d710407429
Ref: library/socket socket recv_fds10407911
Ref: 8d810407911
Ref: 其他函式<2>-Footnote-110408505
Ref: 其他函式<2>-Footnote-210408556
Ref: 其他函式<2>-Footnote-310408600
Node: Socket 物件10408659
Ref: library/socket id110408795
Ref: 327810408795
Ref: library/socket socket-objects10408795
Ref: 326c10408795
Ref: library/socket socket socket accept10409142
Ref: d4810409142
Ref: library/socket socket socket bind10409904
Ref: 14a810409904
Ref: library/socket socket socket close10410248
Ref: cea10410248
Ref: library/socket socket socket connect10411244
Ref: d4910411244
Ref: library/socket socket socket connect_ex10412352
Ref: 14a710412352
Ref: library/socket socket socket detach10412972
Ref: 11b410412972
Ref: library/socket socket socket dup10413215
Ref: 327910413215
Ref: library/socket socket socket fileno10413435
Ref: 327a10413435
Ref: library/socket socket socket get_inheritable10413794
Ref: ea210413794
Ref: library/socket socket socket getpeername10414054
Ref: 31c010414054
Ref: library/socket socket socket getsockname10414392
Ref: 31c110414392
Ref: library/socket socket socket getsockopt10414638
Ref: c7c10414638
Ref: library/socket socket socket getblocking10415388
Ref: b1610415388
Ref: library/socket socket socket gettimeout10415602
Ref: 327b10415602
Ref: library/socket socket socket ioctl10415849
Ref: c7a10415849
Ref: library/socket socket socket listen10416482
Ref: e0010416482
Ref: library/socket socket socket makefile10416946
Ref: 113710416946
Ref: library/socket socket socket recv10418092
Ref: d4a10418092
Ref: library/socket socket socket recvfrom10418971
Ref: d4b10418971
Ref: library/socket socket socket recvmsg10419908
Ref: d4c10419908
Ref: library/socket socket socket recvmsg_into10423822
Ref: 10d310423822
Ref: library/socket socket socket recvfrom_into10425460
Ref: 12b210425460
Ref: library/socket socket socket recv_into10425997
Ref: 12b110425997
Ref: library/socket socket socket send10426448
Ref: d4d10426448
Ref: library/socket socket socket sendall10427261
Ref: d4e10427261
Ref: library/socket socket socket sendto10428234
Ref: d4f10428234
Ref: library/socket socket socket sendmsg10429067
Ref: 41d10429067
Ref: library/socket socket socket sendmsg_afalg10431241
Ref: c7f10431241
Ref: library/socket socket socket sendfile10431568
Ref: dff10431568
Ref: library/socket socket socket set_inheritable10432475
Ref: ea310432475
Ref: library/socket socket socket setblocking10432653
Ref: 2a2810432653
Ref: library/socket socket socket settimeout10433189
Ref: 323910433189
Ref: library/socket socket socket setsockopt10433923
Ref: c7d10433923
Ref: library/socket socket socket shutdown10435041
Ref: 326910435041
Ref: library/socket socket socket share10435395
Ref: baf10435395
Ref: library/socket socket socket family10436260
Ref: 327f10436260
Ref: library/socket socket socket type10436312
Ref: bb310436312
Ref: library/socket socket socket proto10436360
Ref: 328010436360
Ref: Socket 物件-Footnote-110436449
Ref: Socket 物件-Footnote-210436491
Ref: Socket 物件-Footnote-310436533
Ref: Socket 物件-Footnote-410436583
Ref: Socket 物件-Footnote-510436657
Ref: Socket 物件-Footnote-610436701
Ref: Socket 物件-Footnote-710436743
Ref: Socket 物件-Footnote-810436787
Ref: Socket 物件-Footnote-910436829
Ref: Socket 物件-Footnote-1010436871
Ref: Socket 物件-Footnote-1110436916
Ref: Socket 物件-Footnote-1210436961
Ref: Socket 物件-Footnote-1310437004
Ref: Socket 物件-Footnote-1410437047
Ref: Socket 物件-Footnote-1510437090
Ref: Socket 物件-Footnote-1610437133
Node: Notes on socket timeouts10437184
Ref: library/socket notes-on-socket-timeouts10437315
Ref: 328110437315
Ref: library/socket socket-timeouts10437315
Ref: 327e10437315
Node: Timeouts and the connect method10438686
Ref: library/socket timeouts-and-the-connect-method10438817
Ref: 328210438817
Node: Timeouts and the accept method10439292
Ref: library/socket timeouts-and-the-accept-method10439423
Ref: 328310439423
Node: 範例<25>10440164
Ref: library/socket example10440273
Ref: 328410440273
Ref: library/socket socket-example10440273
Ref: 328510440273
Ref: 範例<25>-Footnote-110447990
Node: ssl --- socket 物件的 TLS/SSL 包裝器10448049
Ref: library/ssl doc10448244
Ref: 328610448244
Ref: library/ssl module-ssl10448244
Ref: bb10448244
Ref: library/ssl ssl-tls-ssl-wrapper-for-socket-objects10448244
Ref: 328710448244
Ref: ssl --- socket 物件的 TLS/SSL 包裝器-Footnote-110451074
Ref: ssl --- socket 物件的 TLS/SSL 包裝器-Footnote-210451137
Node: 函式、常數與例外10451179
Ref: library/ssl functions-constants-and-exceptions10451302
Ref: 328810451302
Node: Socket 建立10451485
Ref: library/ssl socket-creation10451580
Ref: 328910451580
Node: 語境建立10453104
Ref: library/ssl context-creation10453218
Ref: 328a10453218
Ref: library/ssl ssl create_default_context10453357
Ref: 13a10453357
Ref: 語境建立-Footnote-110457200
Ref: 語境建立-Footnote-210457259
Ref: 語境建立-Footnote-310457304
Node: 例外<11>10457363
Ref: library/ssl exceptions10457476
Ref: 328f10457476
Ref: library/ssl ssl SSLError10457507
Ref: 121210457507
Ref: library/ssl ssl SSLError library10458003
Ref: 10e010458003
Ref: library/ssl ssl SSLError reason10458276
Ref: 10e110458276
Ref: library/ssl ssl SSLZeroReturnError10458513
Ref: 329010458513
Ref: library/ssl ssl SSLWantReadError10458783
Ref: e0b10458783
Ref: library/ssl ssl SSLWantWriteError10459046
Ref: e0c10459046
Ref: library/ssl ssl SSLSyscallError10459310
Ref: 329210459310
Ref: library/ssl ssl SSLEOFError10459600
Ref: 164610459600
Ref: library/ssl ssl SSLCertVerificationError10459842
Ref: b2010459842
Ref: library/ssl ssl SSLCertVerificationError verify_code10459996
Ref: 329310459996
Ref: library/ssl ssl SSLCertVerificationError verify_message10460086
Ref: 329410460086
Ref: library/ssl ssl CertificateError10460173
Ref: 329510460173
Node: 隨機產生10460365
Ref: library/ssl random-generation10460478
Ref: 329610460478
Ref: library/ssl ssl RAND_bytes10460519
Ref: 4c810460519
Ref: library/ssl ssl RAND_status10461192
Ref: 17c910461192
Ref: library/ssl ssl RAND_add10461514
Ref: 329710461514
Ref: 隨機產生-Footnote-110461941
Ref: 隨機產生-Footnote-210462035
Node: 認證處理10462094
Ref: library/ssl certificate-handling10462206
Ref: 329810462206
Ref: library/ssl ssl cert_time_to_seconds10462247
Ref: e0d10462247
Ref: library/ssl ssl get_server_certificate10463128
Ref: 7e010463128
Ref: library/ssl ssl DER_cert_to_PEM_cert10464235
Ref: 329a10464235
Ref: library/ssl ssl PEM_cert_to_DER_cert10464412
Ref: 329b10464412
Ref: library/ssl ssl get_default_verify_paths10464587
Ref: f4c10464587
Ref: library/ssl ssl enum_certificates10465401
Ref: f5710465401
Ref: library/ssl ssl enum_crls10466304
Ref: f5810466304
Ref: 認證處理-Footnote-110466923
Node: 常數<8>10466982
Ref: library/ssl constants10467073
Ref: 329c10467073
Ref: library/ssl ssl CERT_NONE10467239
Ref: 329d10467239
Ref: library/ssl ssl CERT_OPTIONAL10467803
Ref: 329e10467803
Ref: library/ssl ssl CERT_REQUIRED10468497
Ref: 328c10468497
Ref: library/ssl ssl VerifyMode10469380
Ref: 32a010469380
Ref: library/ssl ssl VERIFY_DEFAULT10469503
Ref: f5110469503
Ref: library/ssl ssl VERIFY_CRL_CHECK_LEAF10469735
Ref: f5210469735
Ref: library/ssl ssl VERIFY_CRL_CHECK_CHAIN10470168
Ref: f5310470168
Ref: library/ssl ssl VERIFY_X509_STRICT10470368
Ref: 13c10470368
Ref: library/ssl ssl VERIFY_ALLOW_PROXY_CERTS10470550
Ref: 17de10470550
Ref: library/ssl ssl VERIFY_X509_TRUSTED_FIRST10470718
Ref: 32a110470718
Ref: library/ssl ssl VERIFY_X509_PARTIAL_CHAIN10470969
Ref: 13b10470969
Ref: library/ssl ssl VerifyFlags10471316
Ref: 32a210471316
Ref: library/ssl ssl PROTOCOL_TLS10471449
Ref: 328e10471449
Ref: library/ssl ssl PROTOCOL_TLS_CLIENT10471912
Ref: 81510471912
Ref: library/ssl ssl PROTOCOL_TLS_SERVER10472177
Ref: 81610472177
Ref: library/ssl ssl PROTOCOL_SSLv2310472348
Ref: 32a310472348
Ref: library/ssl ssl PROTOCOL_SSLv310472499
Ref: 329910472499
Ref: library/ssl ssl PROTOCOL_TLSv110473051
Ref: 32a410473051
Ref: library/ssl ssl PROTOCOL_TLSv1_110473227
Ref: f4a10473227
Ref: library/ssl ssl PROTOCOL_TLSv1_210473496
Ref: f4b10473496
Ref: library/ssl ssl OP_ALL10473765
Ref: 32a510473765
Ref: library/ssl ssl OP_NO_SSLv210473997
Ref: 7dd10473997
Ref: library/ssl ssl OP_NO_SSLv310474264
Ref: 7de10474264
Ref: library/ssl ssl OP_NO_TLSv110474524
Ref: 32a610474524
Ref: library/ssl ssl OP_NO_TLSv1_110474935
Ref: 32a710474935
Ref: library/ssl ssl OP_NO_TLSv1_210475285
Ref: 32a810475285
Ref: library/ssl ssl OP_NO_TLSv1_310475635
Ref: 17a910475635
Ref: library/ssl ssl OP_NO_RENEGOTIATION10476142
Ref: 32a910476142
Ref: library/ssl ssl OP_CIPHER_SERVER_PREFERENCE10476432
Ref: 10e210476432
Ref: library/ssl ssl OP_SINGLE_DH_USE10476674
Ref: 32aa10476674
Ref: library/ssl ssl OP_SINGLE_ECDH_USE10476910
Ref: 32ab10476910
Ref: library/ssl ssl OP_ENABLE_MIDDLEBOX_COMPAT10477150
Ref: 32ac10477150
Ref: library/ssl ssl OP_NO_COMPRESSION10477425
Ref: 10df10477425
Ref: library/ssl ssl Options10477605
Ref: 32ad10477605
Ref: library/ssl ssl OP_NO_TICKET10477699
Ref: 32ae10477699
Ref: library/ssl ssl OP_IGNORE_UNEXPECTED_EOF10477800
Ref: 7db10477800
Ref: library/ssl ssl OP_ENABLE_KTLS10477974
Ref: 169a10477974
Ref: library/ssl ssl OP_LEGACY_SERVER_CONNECT10478635
Ref: 168010478635
Ref: library/ssl ssl HAS_ALPN10478798
Ref: e0810478798
Ref: library/ssl ssl HAS_NEVER_CHECK_COMMON_NAME10478987
Ref: 32af10478987
Ref: library/ssl ssl HAS_ECDH10479204
Ref: 32b010479204
Ref: library/ssl ssl HAS_SNI10479455
Ref: 32b110479455
Ref: library/ssl ssl HAS_NPN10479623
Ref: 32b210479623
Ref: library/ssl ssl HAS_SSLv210479928
Ref: 32b310479928
Ref: library/ssl ssl HAS_SSLv310480047
Ref: 32b410480047
Ref: library/ssl ssl HAS_TLSv110480166
Ref: 32b510480166
Ref: library/ssl ssl HAS_TLSv1_110480285
Ref: b2910480285
Ref: library/ssl ssl HAS_TLSv1_210480406
Ref: 32b610480406
Ref: library/ssl ssl HAS_TLSv1_310480527
Ref: 32b710480527
Ref: library/ssl ssl HAS_PSK10480648
Ref: 32b810480648
Ref: library/ssl ssl CHANNEL_BINDING_TYPES10480770
Ref: 32b910480770
Ref: library/ssl ssl OPENSSL_VERSION10480978
Ref: 11b610480978
Ref: library/ssl ssl OPENSSL_VERSION_INFO10481176
Ref: 11b710481176
Ref: library/ssl ssl OPENSSL_VERSION_NUMBER10481380
Ref: 11b810481380
Ref: library/ssl ssl ALERT_DESCRIPTION_HANDSHAKE_FAILURE10481643
Ref: 32ba10481643
Ref: library/ssl ssl ALERT_DESCRIPTION_INTERNAL_ERROR10481695
Ref: 32bb10481695
Ref: library/ssl ssl AlertDescription10482071
Ref: 32bc10482071
Ref: library/ssl ssl Purpose SERVER_AUTH10482216
Ref: f5510482216
Ref: library/ssl ssl Purpose CLIENT_AUTH10482497
Ref: f5610482497
Ref: library/ssl ssl SSLErrorNumber10482787
Ref: 32bd10482787
Ref: library/ssl ssl TLSVersion10482922
Ref: 32be10482922
Ref: library/ssl ssl TLSVersion MINIMUM_SUPPORTED10483141
Ref: 32bf10483141
Ref: library/ssl ssl TLSVersion MAXIMUM_SUPPORTED10483183
Ref: 32c010483183
Ref: library/ssl ssl TLSVersion SSLv310483374
Ref: 32c110483374
Ref: library/ssl ssl TLSVersion TLSv110483404
Ref: 32c210483404
Ref: library/ssl ssl TLSVersion TLSv1_110483434
Ref: 32c310483434
Ref: library/ssl ssl TLSVersion TLSv1_210483466
Ref: 32c410483466
Ref: library/ssl ssl TLSVersion TLSv1_310483498
Ref: 32c510483498
Ref: 常數<8>-Footnote-110483784
Ref: 常數<8>-Footnote-210483843
Ref: 常數<8>-Footnote-310483902
Ref: 常數<8>-Footnote-410483980
Ref: 常數<8>-Footnote-510484039
Node: SSL Sockets10484132
Ref: library/ssl ssl-sockets10484276
Ref: 32c610484276
Ref: library/ssl ssl SSLSocket10484319
Ref: 88f10484319
Ref: library/ssl ssl SSLSocket read10486654
Ref: e1010486654
Ref: library/ssl ssl SSLSocket write10487485
Ref: e1110487485
Ref: library/ssl ssl SSLSocket do_handshake10488706
Ref: e0f10488706
Ref: library/ssl ssl SSLSocket getpeercert10489453
Ref: f5a10489453
Ref: library/ssl ssl SSLSocket get_verified_chain10492971
Ref: 14cf10492971
Ref: library/ssl ssl SSLSocket get_unverified_chain10493280
Ref: 14d010493280
Ref: library/ssl ssl SSLSocket cipher10493474
Ref: 31c210493474
Ref: library/ssl ssl SSLSocket shared_ciphers10493758
Ref: e0e10493758
Ref: library/ssl ssl SSLSocket compression10494237
Ref: 10de10494237
Ref: library/ssl ssl SSLSocket get_channel_binding10494583
Ref: 10dd10494583
Ref: library/ssl ssl SSLSocket selected_alpn_protocol10495214
Ref: e0710495214
Ref: library/ssl ssl SSLSocket selected_npn_protocol10495625
Ref: 81710495625
Ref: library/ssl ssl SSLSocket unwrap10496048
Ref: 32c710496048
Ref: library/ssl ssl SSLSocket verify_client_post_handshake10496471
Ref: 9d610496471
Ref: library/ssl ssl SSLSocket version10497352
Ref: e0a10497352
Ref: library/ssl ssl SSLSocket pending10497765
Ref: 32c910497765
Ref: library/ssl ssl SSLSocket context10497903
Ref: 32c810497903
Ref: library/ssl ssl SSLSocket server_side10498030
Ref: 32ca10498030
Ref: library/ssl ssl SSLSocket server_hostname10498199
Ref: b2310498199
Ref: library/ssl ssl SSLSocket session10498700
Ref: 32cb10498700
Ref: library/ssl ssl SSLSocket session_reused10499055
Ref: 32cc10499055
Ref: SSL Sockets-Footnote-110499157
Ref: SSL Sockets-Footnote-210499216
Node: SSL Contexts10499275
Ref: library/ssl ssl-contexts10499407
Ref: 32cd10499407
Ref: library/ssl ssl SSLContext10499753
Ref: 27610499753
Ref: library/ssl ssl SSLContext cert_store_stats10504734
Ref: f4e10504734
Ref: library/ssl ssl SSLContext load_cert_chain10505140
Ref: 27710505140
Ref: library/ssl ssl SSLContext load_default_certs10506756
Ref: f5410506756
Ref: library/ssl ssl SSLContext load_verify_locations10507576
Ref: e8f10507576
Ref: library/ssl ssl SSLContext get_ca_certs10508898
Ref: f4f10508898
Ref: library/ssl ssl SSLContext get_ciphers10509531
Ref: c8510509531
Ref: library/ssl ssl SSLContext set_default_verify_paths10510835
Ref: f4d10510835
Ref: library/ssl ssl SSLContext set_ciphers10511298
Ref: 32cf10511298
Ref: library/ssl ssl SSLContext set_alpn_protocols10511900
Ref: e0610511900
Ref: library/ssl ssl SSLContext set_npn_protocols10512538
Ref: 2d310512538
Ref: library/ssl ssl SSLContext sni_callback10513275
Ref: 17d810513275
Ref: library/ssl ssl SSLContext set_servername_callback10515910
Ref: f5910515910
Ref: library/ssl ssl SSLContext load_dh_params10516584
Ref: 10db10516584
Ref: library/ssl ssl SSLContext set_ecdh_curve10517127
Ref: 10dc10517127
Ref: library/ssl ssl SSLContext wrap_socket10517853
Ref: 4c910517853
Ref: library/ssl ssl SSLContext sslsocket_class10520746
Ref: 32d010520746
Ref: library/ssl ssl SSLContext wrap_bio10521041
Ref: b2610521041
Ref: library/ssl ssl SSLContext sslobject_class10521773
Ref: 32d110521773
Ref: library/ssl ssl SSLContext session_stats10522065
Ref: 32d210522065
Ref: library/ssl ssl SSLContext check_hostname10522530
Ref: 329f10522530
Ref: library/ssl ssl SSLContext keylog_filename10524048
Ref: 328d10524048
Ref: library/ssl ssl SSLContext maximum_version10524491
Ref: b2810524491
Ref: library/ssl ssl SSLContext minimum_version10525346
Ref: b2710525346
Ref: library/ssl ssl SSLContext num_tickets10525556
Ref: 32d310525556
Ref: library/ssl ssl SSLContext options10525786
Ref: 7dc10525786
Ref: library/ssl ssl SSLContext post_handshake_auth10526510
Ref: 9d510526510
Ref: library/ssl ssl SSLContext protocol10527324
Ref: 32d410527324
Ref: library/ssl ssl SSLContext hostname_checks_common_name10527457
Ref: b2110527457
Ref: library/ssl ssl SSLContext security_level10527885
Ref: 32d510527885
Ref: library/ssl ssl SSLContext verify_flags10528057
Ref: f5010528057
Ref: library/ssl ssl SSLContext verify_mode10528588
Ref: 328b10528588
Ref: library/ssl ssl SSLContext set_psk_client_callback10529051
Ref: 32d610529051
Ref: library/ssl ssl SSLContext set_psk_server_callback10531054
Ref: 32d710531054
Ref: SSL Contexts-Footnote-110532940
Ref: SSL Contexts-Footnote-210533094
Ref: SSL Contexts-Footnote-310533178
Ref: SSL Contexts-Footnote-410533262
Ref: SSL Contexts-Footnote-510533416
Ref: SSL Contexts-Footnote-610533500
Ref: SSL Contexts-Footnote-710533584
Ref: SSL Contexts-Footnote-810533672
Ref: SSL Contexts-Footnote-910533737
Ref: SSL Contexts-Footnote-1010533796
Ref: SSL Contexts-Footnote-1110533875
Ref: SSL Contexts-Footnote-1210533935
Ref: SSL Contexts-Footnote-1310534012
Ref: SSL Contexts-Footnote-1410534090
Node: Certificates10534176
Ref: library/ssl certificates10534307
Ref: 32d810534307
Ref: library/ssl ssl-certificates10534307
Ref: 32ce10534307
Ref: Certificates-Footnote-110536632
Node: Certificate chains10536691
Ref: library/ssl certificate-chains10536782
Ref: 32d910536782
Node: CA certificates10538047
Ref: library/ssl ca-certificates10538175
Ref: 32da10538175
Node: Combined key and certificate10538757
Ref: library/ssl combined-key-and-certificate10538891
Ref: 32db10538891
Node: Self-signed certificates10539507
Ref: library/ssl self-signed-certificates10539617
Ref: 32dc10539617
Node: 範例<26>10541315
Ref: library/ssl examples10541463
Ref: 32dd10541463
Node: Testing for SSL support10541586
Ref: library/ssl testing-for-ssl-support10541686
Ref: 32de10541686
Node: Client-side operation10542000
Ref: library/ssl client-side-operation10542130
Ref: 32df10542130
Node: Server-side operation10546866
Ref: library/ssl server-side-operation10546964
Ref: 32e010546964
Node: Notes on non-blocking sockets10548961
Ref: library/ssl notes-on-non-blocking-sockets10549118
Ref: 32e110549118
Ref: library/ssl ssl-nonblocking10549118
Ref: 329110549118
Node: Memory BIO Support<2>10552001
Ref: library/ssl memory-bio-support10552159
Ref: 32e210552159
Ref: library/ssl ssl SSLObject10553271
Ref: b2510553271
Ref: library/ssl ssl MemoryBIO10556924
Ref: e0410556924
Ref: library/ssl ssl MemoryBIO pending10557053
Ref: 32e310557053
Ref: library/ssl ssl MemoryBIO eof10557149
Ref: 32e410557149
Ref: library/ssl ssl MemoryBIO read10557276
Ref: 32e510557276
Ref: library/ssl ssl MemoryBIO write10557434
Ref: 32e610557434
Ref: library/ssl ssl MemoryBIO write_eof10557716
Ref: 32e710557716
Node: SSL session10558008
Ref: library/ssl ssl-session10558163
Ref: 32e810558163
Ref: library/ssl ssl SSLSession10558231
Ref: c8410558231
Ref: library/ssl ssl SSLSession id10558309
Ref: 32e910558309
Ref: library/ssl ssl SSLSession time10558330
Ref: 32ea10558330
Ref: library/ssl ssl SSLSession timeout10558353
Ref: 32eb10558353
Ref: library/ssl ssl SSLSession ticket_lifetime_hint10558379
Ref: 32ec10558379
Ref: library/ssl ssl SSLSession has_ticket10558418
Ref: 32ed10558418
Node: Security considerations<2>10558447
Ref: library/ssl security-considerations10558588
Ref: 32ee10558588
Ref: library/ssl ssl-security10558588
Ref: 317d10558588
Node: Best defaults10558723
Ref: library/ssl best-defaults10558820
Ref: 32ef10558820
Node: 手動設定10559977
Ref: library/ssl manual-settings10560099
Ref: 32f010560099
Node: 驗證憑證10560207
Ref: library/ssl verifying-certificates10560289
Ref: 32f110560289
Node: 協定版本10561452
Ref: library/ssl protocol-versions10561559
Ref: 32f210561559
Node: Cipher selection10562369
Ref: library/ssl cipher-selection10562455
Ref: 32f310562455
Ref: Cipher selection-Footnote-110563109
Node: Multi-processing10563193
Ref: library/ssl multi-processing10563293
Ref: 32f410563293
Node: TLS 1 310563814
Ref: library/ssl ssl-tlsv1-310563935
Ref: b2410563935
Ref: library/ssl tls-1-310563935
Ref: 32f510563935
Ref: TLS 1 3-Footnote-110566025
Ref: TLS 1 3-Footnote-210566091
Ref: TLS 1 3-Footnote-310566150
Ref: TLS 1 3-Footnote-410566209
Ref: TLS 1 3-Footnote-510566268
Ref: TLS 1 3-Footnote-610566327
Ref: TLS 1 3-Footnote-710566386
Ref: TLS 1 3-Footnote-810566462
Ref: TLS 1 3-Footnote-910566521
Node: select --- 等待 I/O 完成10566579
Ref: library/select doc10566776
Ref: 32f610566776
Ref: library/select module-select10566776
Ref: af10566776
Ref: library/select select-waiting-for-i-o-completion10566776
Ref: 32f710566776
Ref: library/select select error10567924
Ref: ff910567924
Ref: library/select select devpoll10568106
Ref: f3810568106
Ref: library/select select epoll10568819
Ref: f3610568819
Ref: library/select select poll10570294
Ref: 2a9910570294
Ref: library/select select kqueue10570611
Ref: 15c810570611
Ref: library/select select kevent10570941
Ref: 32fc10570941
Ref: library/select select select10571216
Ref: d4610571216
Ref: library/select select PIPE_BUF10573474
Ref: 11a210573474
Ref: select --- 等待 I/O 完成-Footnote-110574157
Ref: select --- 等待 I/O 完成-Footnote-210574199
Node: /dev/poll Polling Objects10574241
Ref: library/select dev-poll-polling-objects10574384
Ref: 32fe10574384
Ref: library/select devpoll-objects10574384
Ref: 32f810574384
Ref: library/select select devpoll close10574750
Ref: f3a10574750
Ref: library/select select devpoll closed10574863
Ref: f3b10574863
Ref: library/select select devpoll fileno10574969
Ref: f3910574969
Ref: library/select select devpoll register10575091
Ref: 32ff10575091
Ref: library/select select devpoll modify10576072
Ref: 330010576072
Ref: library/select select devpoll unregister10576280
Ref: 330110576280
Ref: library/select select devpoll poll10576637
Ref: d4210576637
Ref: /dev/poll Polling Objects-Footnote-110577777
Node: Edge and Level Trigger Polling epoll Objects10577819
Ref: library/select edge-and-level-trigger-polling-epoll-objects10577986
Ref: 330210577986
Ref: library/select epoll-objects10577986
Ref: 32f910577986
Ref: library/select select epoll close10580847
Ref: f3710580847
Ref: library/select select epoll closed10580936
Ref: 330310580936
Ref: library/select select epoll fileno10581010
Ref: 330410581010
Ref: library/select select epoll fromfd10581098
Ref: 330510581098
Ref: library/select select epoll register10581188
Ref: 330610581188
Ref: library/select select epoll modify10581288
Ref: 330710581288
Ref: library/select select epoll unregister10581373
Ref: 8fe10581373
Ref: library/select select epoll poll10581564
Ref: d4310581564
Ref: Edge and Level Trigger Polling epoll Objects-Footnote-110581964
Node: Polling Objects10582006
Ref: library/select poll-objects10582162
Ref: 32fa10582162
Ref: library/select polling-objects10582162
Ref: 330810582162
Ref: library/select select poll register10582737
Ref: 330910582737
Ref: library/select select poll modify10584713
Ref: 330a10584713
Ref: library/select select poll unregister10585014
Ref: 330b10585014
Ref: library/select select poll poll10585403
Ref: d4510585403
Ref: Polling Objects-Footnote-110586546
Node: Kqueue Objects10586588
Ref: library/select id110586714
Ref: 330c10586714
Ref: library/select kqueue-objects10586714
Ref: 32fb10586714
Ref: library/select select kqueue close10586763
Ref: 330d10586763
Ref: library/select select kqueue closed10586854
Ref: 330e10586854
Ref: library/select select kqueue fileno10586930
Ref: 330f10586930
Ref: library/select select kqueue fromfd10587019
Ref: 331010587019
Ref: library/select select kqueue control10587110
Ref: d4410587110
Ref: Kqueue Objects-Footnote-110587759
Node: Kevent Objects10587801
Ref: library/select id210587903
Ref: 331110587903
Ref: library/select kevent-objects10587903
Ref: 32fd10587903
Ref: library/select select kevent ident10588018
Ref: 331210588018
Ref: library/select select kevent filter10588315
Ref: 331310588315
Ref: library/select select kevent flags10590092
Ref: 331410590092
Ref: library/select select kevent fflags10591751
Ref: 331510591751
Ref: library/select select kevent data10595494
Ref: 331610595494
Ref: library/select select kevent udata10595547
Ref: 331710595547
Node: selectors --- 高階 I/O 多工10595599
Ref: library/selectors doc10595801
Ref: 331810595801
Ref: library/selectors module-selectors10595801
Ref: b010595801
Ref: library/selectors selectors-high-level-i-o-multiplexing10595801
Ref: 331910595801
Ref: selectors --- 高階 I/O 多工-Footnote-110596120
Node: 簡介<8>10596189
Ref: library/selectors introduction10596285
Ref: 331a10596285
Node: Classes<3>10597603
Ref: library/selectors classes10597718
Ref: 331d10597718
Ref: library/selectors selectors EVENT_READ10598296
Ref: 331e10598296
Ref: library/selectors selectors EVENT_WRITE10598387
Ref: 331f10598387
Ref: library/selectors selectors SelectorKey10598464
Ref: 332010598464
Ref: library/selectors selectors SelectorKey fileobj10598743
Ref: 332110598743
Ref: library/selectors selectors SelectorKey fd10598804
Ref: 332210598804
Ref: library/selectors selectors SelectorKey events10598864
Ref: 332310598864
Ref: library/selectors selectors SelectorKey data10598952
Ref: 332410598952
Ref: library/selectors selectors BaseSelector10599115
Ref: 331b10599115
Ref: library/selectors selectors BaseSelector register10599790
Ref: 332510599790
Ref: library/selectors selectors BaseSelector unregister10600444
Ref: 332610600444
Ref: library/selectors selectors BaseSelector modify10601064
Ref: b7b10601064
Ref: library/selectors selectors BaseSelector select10601658
Ref: 332710601658
Ref: library/selectors selectors BaseSelector close10602955
Ref: 332810602955
Ref: library/selectors selectors BaseSelector get_key10603173
Ref: 332910603173
Ref: library/selectors selectors BaseSelector get_map10603460
Ref: 332a10603460
Ref: library/selectors selectors DefaultSelector10603728
Ref: 331c10603728
Ref: library/selectors selectors SelectSelector10603937
Ref: 320610603937
Ref: library/selectors selectors PollSelector10604025
Ref: b7d10604025
Ref: library/selectors selectors EpollSelector10604110
Ref: b7c10604110
Ref: library/selectors selectors EpollSelector fileno10604196
Ref: 332b10604196
Ref: library/selectors selectors DevpollSelector10604336
Ref: b7e10604336
Ref: library/selectors selectors DevpollSelector fileno10604426
Ref: 332c10604426
Ref: library/selectors selectors KqueueSelector10604596
Ref: 320910604596
Ref: library/selectors selectors KqueueSelector fileno10604685
Ref: 332d10604685
Ref: Classes<3>-Footnote-110604863
Node: 範例<27>10604905
Ref: library/selectors examples10605002
Ref: 332e10605002
Node: signal --- 設定非同步事件的處理函式10606023
Ref: library/signal doc10606236
Ref: 332f10606236
Ref: library/signal module-signal10606236
Ref: b410606236
Ref: library/signal signal-set-handlers-for-asynchronous-events10606236
Ref: 333010606236
Ref: signal --- 設定非同步事件的處理函式-Footnote-110606690
Node: General rules10606756
Ref: library/signal general-rules10606877
Ref: 333110606877
Node: Execution of Python signal handlers10607844
Ref: library/signal execution-of-python-signal-handlers10607957
Ref: 333310607957
Node: Signals and threads10609275
Ref: library/signal id110609388
Ref: 333510609388
Ref: library/signal signals-and-threads10609388
Ref: 333610609388
Node: 模組內容<5>10609858
Ref: library/signal module-contents10609998
Ref: 333710609998
Ref: library/signal signal Signals10610600
Ref: 333b10610600
Ref: library/signal signal Handlers10610747
Ref: 333c10610747
Ref: library/signal signal Sigmasks10610911
Ref: 333d10610911
Ref: library/signal signal SIG_DFL10611302
Ref: 172610611302
Ref: library/signal signal SIG_IGN10611636
Ref: 172510611636
Ref: library/signal signal SIGABRT10611759
Ref: 1c4d10611759
Ref: library/signal signal SIGALRM10611830
Ref: 333e10611830
Ref: library/signal signal SIGBREAK10611937
Ref: 333f10611937
Ref: library/signal signal SIGBUS10612051
Ref: 1c4e10612051
Ref: library/signal signal SIGCHLD10612151
Ref: 2ad510612151
Ref: library/signal signal SIGCLD10612258
Ref: 334010612258
Ref: library/signal signal SIGCONT10612366
Ref: 2ae310612366
Ref: library/signal signal SIGFPE10612484
Ref: 1c4c10612484
Ref: library/signal signal SIGHUP10612722
Ref: 334110612722
Ref: library/signal signal SIGILL10612869
Ref: 1c4f10612869
Ref: library/signal signal SIGINT10612923
Ref: 7e810612923
Ref: library/signal signal SIGKILL10613055
Ref: 334210613055
Ref: library/signal signal SIGPIPE10613186
Ref: 333210613186
Ref: library/signal signal SIGSEGV10613346
Ref: 1c4b10613346
Ref: library/signal signal SIGSTKFLT10613426
Ref: 176710613426
Ref: library/signal signal SIGTERM10613775
Ref: 134d10613775
Ref: library/signal signal SIGUSR110613829
Ref: 334310613829
Ref: library/signal signal SIGUSR210613922
Ref: 334410613922
Ref: library/signal signal SIGWINCH10614015
Ref: 334510614015
Ref: library/signal signal CTRL_C_EVENT10614675
Ref: 12f510614675
Ref: library/signal signal CTRL_BREAK_EVENT10614906
Ref: 12f610614906
Ref: library/signal signal NSIG10615145
Ref: 170310615145
Ref: library/signal signal ITIMER_REAL10615299
Ref: 334710615299
Ref: library/signal signal ITIMER_VIRTUAL10615433
Ref: 334810615433
Ref: library/signal signal ITIMER_PROF10615581
Ref: 334910615581
Ref: library/signal signal SIG_BLOCK10615922
Ref: 333810615922
Ref: library/signal signal SIG_UNBLOCK10616109
Ref: 333910616109
Ref: library/signal signal SIG_SETMASK10616305
Ref: 333a10616305
Ref: library/signal signal ItimerError10616560
Ref: 334a10616560
Ref: library/signal signal alarm10617082
Ref: 334d10617082
Ref: library/signal signal getsignal10617714
Ref: 15a410617714
Ref: library/signal signal strsignal10618284
Ref: 194410618284
Ref: library/signal signal valid_signals10618584
Ref: 334610618584
Ref: library/signal signal pause10618827
Ref: 334e10618827
Ref: library/signal signal raise_signal10619204
Ref: 170710619204
Ref: library/signal signal pidfd_send_signal10619337
Ref: 8cf10619337
Ref: library/signal signal pthread_kill10619825
Ref: 10ca10619825
Ref: library/signal signal pthread_sigmask10621054
Ref: 10c910621054
Ref: library/signal signal setitimer10622485
Ref: 334b10622485
Ref: library/signal signal getitimer10623499
Ref: 334c10623499
Ref: library/signal signal set_wakeup_fd10623654
Ref: b1410623654
Ref: library/signal signal siginterrupt10625841
Ref: 10ce10625841
Ref: library/signal signal signal10626434
Ref: 10cd10626434
Ref: library/signal signal sigpending10627938
Ref: 10cb10627938
Ref: library/signal signal sigwait10628399
Ref: 10cc10628399
Ref: library/signal signal sigwaitinfo10628970
Ref: d5110628970
Ref: library/signal signal sigtimedwait10630234
Ref: d5010630234
Ref: 模組內容<5>-Footnote-110631003
Ref: 模組內容<5>-Footnote-210631054
Ref: 模組內容<5>-Footnote-310631109
Ref: 模組內容<5>-Footnote-410631154
Ref: 模組內容<5>-Footnote-510631199
Ref: 模組內容<5>-Footnote-610631245
Ref: 模組內容<5>-Footnote-710631291
Ref: 模組內容<5>-Footnote-810631337
Ref: 模組內容<5>-Footnote-910631382
Ref: 模組內容<5>-Footnote-1010631428
Ref: 模組內容<5>-Footnote-1110631486
Ref: 模組內容<5>-Footnote-1210631539
Ref: 模組內容<5>-Footnote-1310631591
Ref: 模組內容<5>-Footnote-1410631647
Ref: 模組內容<5>-Footnote-1510631700
Ref: 模組內容<5>-Footnote-1610631747
Ref: 模組內容<5>-Footnote-1710631798
Ref: 模組內容<5>-Footnote-1810631846
Ref: 模組內容<5>-Footnote-1910631898
Ref: 模組內容<5>-Footnote-2010631941
Ref: 模組內容<5>-Footnote-2110631994
Node: 範例<28>10632037
Ref: library/signal examples10632179
Ref: 334f10632179
Ref: library/signal signal-example10632179
Ref: 335010632179
Node: Note on SIGPIPE10633135
Ref: library/signal note-on-sigpipe10633300
Ref: 335110633300
Ref: Note on SIGPIPE-Footnote-110634746
Node: Note on Signal Handlers and Exceptions10634790
Ref: library/signal handlers-and-exceptions10634936
Ref: 216710634936
Ref: library/signal note-on-signal-handlers-and-exceptions10634936
Ref: 335210634936
Node: mmap --- 記憶體映射檔案的支援10637543
Ref: library/mmap doc10637716
Ref: 335310637716
Ref: library/mmap mmap-memory-mapped-file-support10637716
Ref: 335410637716
Ref: library/mmap module-mmap10637716
Ref: 8310637716
Ref: library/mmap mmap mmap10640319
Ref: 1f010640319
Ref: library/mmap mmap mmap close10645935
Ref: 335a10645935
Ref: library/mmap mmap mmap closed10646146
Ref: 335b10646146
Ref: library/mmap mmap mmap find10646249
Ref: 335c10646249
Ref: library/mmap mmap mmap flush10646677
Ref: a3b10646677
Ref: library/mmap mmap mmap madvise10647564
Ref: 9ac10647564
Ref: library/mmap mmap mmap move10648132
Ref: 335e10648132
Ref: library/mmap mmap mmap read10648410
Ref: 107710648410
Ref: library/mmap mmap mmap read_byte10648860
Ref: 335f10648860
Ref: library/mmap mmap mmap readline10649008
Ref: 336010649008
Ref: library/mmap mmap mmap resize10649233
Ref: 335910649233
Ref: library/mmap mmap mmap rfind10650095
Ref: 336110650095
Ref: library/mmap mmap mmap seek10650525
Ref: 1f210650525
Ref: library/mmap mmap mmap seekable10651007
Ref: 1f110651007
Ref: library/mmap mmap mmap size10651177
Ref: 335810651177
Ref: library/mmap mmap mmap tell10651316
Ref: 336210651316
Ref: library/mmap mmap mmap write10651403
Ref: 336310651403
Ref: library/mmap mmap mmap write_byte10652096
Ref: 336410652096
Node: MADV_* Constants10652459
Ref: library/mmap madv-constants10652572
Ref: 336510652572
Ref: library/mmap madvise-constants10652572
Ref: 335d10652572
Ref: library/mmap mmap MADV_NORMAL10652625
Ref: 336610652625
Ref: library/mmap mmap MADV_RANDOM10652654
Ref: 336710652654
Ref: library/mmap mmap MADV_SEQUENTIAL10652683
Ref: 336810652683
Ref: library/mmap mmap MADV_WILLNEED10652716
Ref: 336910652716
Ref: library/mmap mmap MADV_DONTNEED10652747
Ref: 336a10652747
Ref: library/mmap mmap MADV_REMOVE10652778
Ref: 336b10652778
Ref: library/mmap mmap MADV_DONTFORK10652807
Ref: 336c10652807
Ref: library/mmap mmap MADV_DOFORK10652838
Ref: 336d10652838
Ref: library/mmap mmap MADV_HWPOISON10652867
Ref: 336e10652867
Ref: library/mmap mmap MADV_MERGEABLE10652898
Ref: 336f10652898
Ref: library/mmap mmap MADV_UNMERGEABLE10652930
Ref: 337010652930
Ref: library/mmap mmap MADV_SOFT_OFFLINE10652964
Ref: 337110652964
Ref: library/mmap mmap MADV_HUGEPAGE10652999
Ref: 337210652999
Ref: library/mmap mmap MADV_NOHUGEPAGE10653030
Ref: 337310653030
Ref: library/mmap mmap MADV_DONTDUMP10653063
Ref: 337410653063
Ref: library/mmap mmap MADV_DODUMP10653094
Ref: 337510653094
Ref: library/mmap mmap MADV_FREE10653123
Ref: 337610653123
Ref: library/mmap mmap MADV_NOSYNC10653150
Ref: 337710653150
Ref: library/mmap mmap MADV_AUTOSYNC10653179
Ref: 337810653179
Ref: library/mmap mmap MADV_NOCORE10653210
Ref: 337910653210
Ref: library/mmap mmap MADV_CORE10653239
Ref: 337a10653239
Ref: library/mmap mmap MADV_PROTECT10653266
Ref: 337b10653266
Ref: library/mmap mmap MADV_FREE_REUSABLE10653296
Ref: 337c10653296
Ref: library/mmap mmap MADV_FREE_REUSE10653332
Ref: 337d10653332
Node: MAP_* 常數10653574
Ref: library/mmap id110653687
Ref: 337e10653687
Ref: library/mmap map-constants10653687
Ref: 335710653687
Ref: library/mmap mmap MAP_SHARED10653730
Ref: 335610653730
Ref: library/mmap mmap MAP_PRIVATE10653758
Ref: 335510653758
Ref: library/mmap mmap MAP_32BIT10653787
Ref: 159710653787
Ref: library/mmap mmap MAP_ALIGNED_SUPER10653814
Ref: 165810653814
Ref: library/mmap mmap MAP_ANON10653849
Ref: 337f10653849
Ref: library/mmap mmap MAP_ANONYMOUS10653875
Ref: 338010653875
Ref: library/mmap mmap MAP_CONCEAL10653906
Ref: 165910653906
Ref: library/mmap mmap MAP_DENYWRITE10653935
Ref: 338110653935
Ref: library/mmap mmap MAP_EXECUTABLE10653966
Ref: 338210653966
Ref: library/mmap mmap MAP_HASSEMAPHORE10653998
Ref: 159210653998
Ref: library/mmap mmap MAP_JIT10654032
Ref: 159410654032
Ref: library/mmap mmap MAP_NOCACHE10654057
Ref: 159310654057
Ref: library/mmap mmap MAP_NOEXTEND10654086
Ref: 159110654086
Ref: library/mmap mmap MAP_NORESERVE10654116
Ref: 159010654116
Ref: library/mmap mmap MAP_POPULATE10654147
Ref: 184a10654147
Ref: library/mmap mmap MAP_RESILIENT_CODESIGN10654177
Ref: 159510654177
Ref: library/mmap mmap MAP_RESILIENT_MEDIA10654217
Ref: 159610654217
Ref: library/mmap mmap MAP_STACK10654254
Ref: 338310654254
Ref: library/mmap mmap MAP_TPRO10654281
Ref: 159a10654281
Ref: library/mmap mmap MAP_TRANSLATED_ALLOW_EXECUTE10654307
Ref: 159810654307
Ref: library/mmap mmap MAP_UNIX0310654353
Ref: 159910654353
Node: 網際網路資料處理10655299
Ref: library/netdata doc10655492
Ref: 338410655492
Ref: library/netdata internet-data-handling10655492
Ref: 338510655492
Ref: library/netdata netdata10655492
Ref: 338610655492
Node: email --- 郵件和 MIME 處理套件10656297
Ref: library/email doc10656439
Ref: 338710656439
Ref: library/email email-an-email-and-mime-handling-package10656439
Ref: 338810656439
Ref: library/email module-email10656439
Ref: 3210656439
Ref: email --- 郵件和 MIME 處理套件-Footnote-110663063
Ref: email --- 郵件和 MIME 處理套件-Footnote-210663137
Ref: email --- 郵件和 MIME 處理套件-Footnote-310663196
Ref: email --- 郵件和 MIME 處理套件-Footnote-410663255
Ref: email --- 郵件和 MIME 處理套件-Footnote-510663314
Ref: email --- 郵件和 MIME 處理套件-Footnote-610663373
Ref: email --- 郵件和 MIME 處理套件-Footnote-710663432
Ref: email --- 郵件和 MIME 處理套件-Footnote-810663491
Ref: email --- 郵件和 MIME 處理套件-Footnote-910663550
Node: email message：表示電子郵件訊息10663609
Ref: library/email message doc10663771
Ref: 338910663771
Ref: library/email message email-message-representing-an-email-message10663771
Ref: 338a10663771
Ref: library/email message module-email message10663771
Ref: 3b10663771
Ref: library/email message email message EmailMessage10666226
Ref: 26010666226
Ref: library/email message email message EmailMessage as_string10666708
Ref: 338d10666708
Ref: library/email message email message EmailMessage __str__10668545
Ref: 338f10668545
Ref: library/email message email message EmailMessage as_bytes10669002
Ref: 339010669002
Ref: library/email message email message EmailMessage __bytes__10670166
Ref: 339110670166
Ref: library/email message email message EmailMessage is_multipart10670342
Ref: 339210670342
Ref: library/email message email message EmailMessage set_unixfrom10671017
Ref: 339310671017
Ref: library/email message email message EmailMessage get_unixfrom10671237
Ref: 339510671237
Ref: library/email message email message EmailMessage __len__10672365
Ref: 339710672365
Ref: library/email message email message EmailMessage __contains__10672463
Ref: 339810672463
Ref: library/email message email message EmailMessage __getitem__10672853
Ref: 339910672853
Ref: library/email message email message EmailMessage __setitem__10673568
Ref: 339c10673568
Ref: library/email message email message EmailMessage __delitem__10674602
Ref: 339d10674602
Ref: library/email message email message EmailMessage keys10674824
Ref: 339610674824
Ref: library/email message email message EmailMessage values10674916
Ref: 339e10674916
Ref: library/email message email message EmailMessage items10675004
Ref: 339f10675004
Ref: library/email message email message EmailMessage get10675133
Ref: 33a010675133
Ref: library/email message email message EmailMessage get_all10675481
Ref: 339a10675481
Ref: library/email message email message EmailMessage add_header10675718
Ref: 33a110675718
Ref: library/email message email message EmailMessage replace_header10677684
Ref: 33a210677684
Ref: library/email message email message EmailMessage get_content_type10677990
Ref: 33a310677990
Ref: library/email message email message EmailMessage get_content_maintype10678870
Ref: 33a510678870
Ref: library/email message email message EmailMessage get_content_subtype10679074
Ref: 33a610679074
Ref: library/email message email message EmailMessage get_default_type10679265
Ref: 33a410679265
Ref: library/email message email message EmailMessage set_default_type10679585
Ref: 33a710679585
Ref: library/email message email message EmailMessage set_param10680027
Ref: 33a810680027
Ref: library/email message email message EmailMessage del_param10681646
Ref: 33aa10681646
Ref: library/email message email message EmailMessage get_filename10682082
Ref: 33ab10682082
Ref: library/email message email message EmailMessage get_boundary10682621
Ref: 33ad10682621
Ref: library/email message email message EmailMessage set_boundary10682985
Ref: 33ae10682985
Ref: library/email message email message EmailMessage get_content_charset10683653
Ref: 33b010683653
Ref: library/email message email message EmailMessage get_charsets10683955
Ref: 33b110683955
Ref: library/email message email message EmailMessage is_attachment10684648
Ref: 33b210684648
Ref: library/email message email message EmailMessage get_content_disposition10685003
Ref: 33b410685003
Ref: library/email message email message EmailMessage walk10685478
Ref: 33b510685478
Ref: library/email message email message EmailMessage get_body10687489
Ref: 33b610687489
Ref: library/email message email message EmailMessage iter_attachments10689604
Ref: 33b710689604
Ref: library/email message email message EmailMessage iter_parts10690572
Ref: 33b810690572
Ref: library/email message email message EmailMessage get_content10690785
Ref: 33b910690785
Ref: library/email message email message EmailMessage set_content10691195
Ref: 17ab10691195
Ref: library/email message email message EmailMessage make_related10691605
Ref: 33bc10691605
Ref: library/email message email message EmailMessage make_alternative10692093
Ref: 33bd10692093
Ref: library/email message email message EmailMessage make_mixed10692612
Ref: 33be10692612
Ref: library/email message email message EmailMessage add_related10693151
Ref: 33bf10693151
Ref: library/email message email message EmailMessage add_alternative10693908
Ref: 33c110693908
Ref: library/email message email message EmailMessage add_attachment10694598
Ref: 33c210694598
Ref: library/email message email message EmailMessage clear10695583
Ref: 33c310695583
Ref: library/email message email message EmailMessage clear_content10695664
Ref: 33c410695664
Ref: library/email message email message EmailMessage preamble10695925
Ref: 33c510695925
Ref: library/email message email message EmailMessage epilogue10697184
Ref: 33c610697184
Ref: library/email message email message EmailMessage defects10697527
Ref: 33c710697527
Ref: library/email message email message MIMEPart10697766
Ref: ede10697766
Ref: email message：表示電子郵件訊息-Footnote-110698146
Ref: email message：表示電子郵件訊息-Footnote-210698219
Ref: email message：表示電子郵件訊息-Footnote-310698416
Ref: email message：表示電子郵件訊息-Footnote-410698475
Ref: email message：表示電子郵件訊息-Footnote-510698534
Ref: email message：表示電子郵件訊息-Footnote-610698593
Ref: email message：表示電子郵件訊息-Footnote-710698652
Ref: email message：表示電子郵件訊息-Footnote-810698711
Ref: email message：表示電子郵件訊息-Footnote-910698770
Ref: email message：表示電子郵件訊息-Footnote-1010698829
Ref: email message：表示電子郵件訊息-Footnote-1110698889
Ref: email message：表示電子郵件訊息-Footnote-1210698949
Ref: email message：表示電子郵件訊息-Footnote-1310699009
Node: email parser：剖析電子郵件訊息10699069
Ref: library/email parser doc10699276
Ref: 33c810699276
Ref: library/email parser email-parser-parsing-email-messages10699276
Ref: 33c910699276
Ref: library/email parser module-email parser10699276
Ref: 4510699276
Ref: email parser：剖析電子郵件訊息-Footnote-110701664
Node: FeedParser API10701736
Ref: library/email parser feedparser-api10701845
Ref: 33cb10701845
Ref: library/email parser email parser BytesFeedParser10703138
Ref: 116310703138
Ref: library/email parser email parser BytesFeedParser feed10704339
Ref: 33cc10704339
Ref: library/email parser email parser BytesFeedParser close10704774
Ref: 33cd10704774
Ref: library/email parser email parser FeedParser10705014
Ref: 33ca10705014
Node: Parser API10705473
Ref: library/email parser parser-api10705607
Ref: 33ce10705607
Ref: library/email parser email parser BytesParser10706339
Ref: 116410706339
Ref: library/email parser email parser BytesParser parse10707000
Ref: 33cf10707000
Ref: library/email parser email parser BytesParser parsebytes10708040
Ref: 33d010708040
Ref: library/email parser email parser BytesHeaderParser10708548
Ref: 105510708548
Ref: library/email parser email parser Parser10708770
Ref: 113610708770
Ref: library/email parser email parser Parser parse10709108
Ref: 33d110709108
Ref: library/email parser email parser Parser parsestr10709546
Ref: 33d210709546
Ref: library/email parser email parser HeaderParser10709975
Ref: 105610709975
Ref: library/email parser email message_from_bytes10710374
Ref: 116110710374
Ref: library/email parser email message_from_binary_file10710840
Ref: 116210710840
Ref: library/email parser email message_from_string10711314
Ref: 33d310711314
Ref: library/email parser email message_from_file10711706
Ref: 33d410711706
Ref: Parser API-Footnote-110712425
Ref: Parser API-Footnote-210712484
Node: Additional notes10712543
Ref: library/email parser additional-notes10712654
Ref: 33d510712654
Node: email generator：產生 MIME 文件10714196
Ref: library/email generator doc10714390
Ref: 33d610714390
Ref: library/email generator email-generator-generating-mime-documents10714390
Ref: 33d710714390
Ref: library/email generator module-email generator10714390
Ref: 3710714390
Ref: library/email generator email generator BytesGenerator10716458
Ref: 116710716458
Ref: library/email generator email generator BytesGenerator flatten10718364
Ref: 33d910718364
Ref: library/email generator email generator BytesGenerator clone10720187
Ref: 33dc10720187
Ref: library/email generator email generator BytesGenerator write10720386
Ref: 33da10720386
Ref: library/email generator email generator Generator10721436
Ref: 116610721436
Ref: library/email generator email generator Generator flatten10723280
Ref: 33dd10723280
Ref: library/email generator email generator Generator clone10725039
Ref: 33df10725039
Ref: library/email generator email generator Generator write10725225
Ref: 33de10725225
Ref: library/email generator email generator DecodedGenerator10726135
Ref: c3e10726135
Ref: email generator：產生 MIME 文件-Footnote-110727552
Ref: email generator：產生 MIME 文件-Footnote-210727628
Ref: email generator：產生 MIME 文件-Footnote-310728135
Ref: email generator：產生 MIME 文件-Footnote-410728187
Ref: email generator：產生 MIME 文件-Footnote-510728246
Ref: email generator：產生 MIME 文件-Footnote-610728298
Node: email policy Policy Objects10728357
Ref: library/email policy doc10728548
Ref: 33e010728548
Ref: library/email policy email-policy-policy-objects10728548
Ref: 33e110728548
Ref: library/email policy module-email policy10728548
Ref: 4610728548
Ref: library/email policy email policy Policy10734519
Ref: 104d10734519
Ref: library/email policy email policy Policy max_line_length10735343
Ref: 338e10735343
Ref: library/email policy email policy Policy linesep10735646
Ref: 33e210735646
Ref: library/email policy email policy Policy cte_type10735910
Ref: 33db10735910
Ref: library/email policy email policy Policy raise_on_defect10737014
Ref: 33e410737014
Ref: library/email policy email policy Policy mangle_from_10737255
Ref: d9c10737255
Ref: library/email policy email policy Policy message_factory10737577
Ref: c3f10737577
Ref: library/email policy email policy Policy verify_generated_headers10737851
Ref: 1c310737851
Ref: library/email policy email policy Policy clone10738694
Ref: 104f10738694
Ref: library/email policy email policy Policy handle_defect10739180
Ref: 33e710739180
Ref: library/email policy email policy Policy register_defect10739659
Ref: 33e510739659
Ref: library/email policy email policy Policy header_max_count10740352
Ref: 33e810740352
Ref: library/email policy email policy Policy header_source_parse10741414
Ref: 33e910741414
Ref: library/email policy email policy Policy header_store_parse10742423
Ref: 33ea10742423
Ref: library/email policy email policy Policy header_fetch_parse10743184
Ref: 33eb10743184
Ref: library/email policy email policy Policy fold10744007
Ref: 33ec10744007
Ref: library/email policy email policy Policy fold_binary10744719
Ref: 33e310744719
Ref: library/email policy email policy EmailPolicy10745053
Ref: 105110745053
Ref: library/email policy email policy EmailPolicy utf810745887
Ref: d9e10745887
Ref: library/email policy email policy EmailPolicy refold_source10746276
Ref: 33d810746276
Ref: library/email policy email policy EmailPolicy header_factory10747065
Ref: 33ed10747065
Ref: library/email policy email policy EmailPolicy content_manager10747673
Ref: edf10747673
Ref: library/email policy email policy EmailPolicy header_max_count10748382
Ref: 33ef10748382
Ref: library/email policy email policy EmailPolicy header_source_parse10748588
Ref: 33f110748588
Ref: library/email policy email policy EmailPolicy header_store_parse10748969
Ref: 33f210748969
Ref: library/email policy email policy EmailPolicy header_fetch_parse10749450
Ref: 33f310749450
Ref: library/email policy email policy EmailPolicy fold10749876
Ref: 156b10749876
Ref: library/email policy email policy EmailPolicy fold_binary10751035
Ref: 33f410751035
Ref: library/email policy email policy default10751855
Ref: 338c10751855
Ref: library/email policy email policy SMTP10752067
Ref: 33f510752067
Ref: library/email policy email policy SMTPUTF810752271
Ref: 33f610752271
Ref: library/email policy email policy HTTP10752687
Ref: 33f710752687
Ref: library/email policy email policy strict10752881
Ref: 33f810752881
Ref: library/email policy email policy Compat3210754261
Ref: 104e10754261
Ref: library/email policy email policy Compat32 mangle_from_10754795
Ref: 33f910754795
Ref: library/email policy email policy Compat32 header_source_parse10754981
Ref: 33fa10754981
Ref: library/email policy email policy Compat32 header_store_parse10755362
Ref: 33fb10755362
Ref: library/email policy email policy Compat32 header_fetch_parse10755468
Ref: 33fc10755468
Ref: library/email policy email policy Compat32 fold10755710
Ref: 33fd10755710
Ref: library/email policy email policy Compat32 fold_binary10756053
Ref: 33fe10756053
Ref: library/email policy email policy compat3210756583
Ref: c4010756583
Ref: email policy Policy Objects-Footnote-110756802
Ref: email policy Policy Objects-Footnote-210756874
Ref: email policy Policy Objects-Footnote-310756933
Ref: email policy Policy Objects-Footnote-410756992
Ref: email policy Policy Objects-Footnote-510757051
Ref: email policy Policy Objects-Footnote-610757110
Ref: email policy Policy Objects-Footnote-710757169
Ref: email policy Policy Objects-Footnote-810757228
Ref: email policy Policy Objects-Footnote-910757297
Ref: email policy Policy Objects-Footnote-1010757356
Ref: email policy Policy Objects-Footnote-1110757416
Ref: email policy Policy Objects-Footnote-1210757476
Node: email errors：例外和缺陷類別10757536
Ref: library/email errors doc10757732
Ref: 33ff10757732
Ref: library/email errors email-errors-exception-and-defect-classes10757732
Ref: 340010757732
Ref: library/email errors module-email errors10757732
Ref: 3610757732
Ref: library/email errors email errors MessageError10758015
Ref: 340110758015
Ref: library/email errors email errors MessageParseError10758253
Ref: 340210758253
Ref: library/email errors email errors HeaderParseError10758527
Ref: 33af10758527
Ref: library/email errors email errors BoundaryError10759167
Ref: 340310759167
Ref: library/email errors email errors MultipartConversionError10759244
Ref: 340410759244
Ref: library/email errors email errors HeaderWriteError10759977
Ref: 33e610759977
Ref: library/email errors email errors MessageDefect10760106
Ref: 340710760106
Ref: library/email errors email errors HeaderDefect10760274
Ref: 340810760274
Ref: email errors：例外和缺陷類別-Footnote-110763138
Ref: email errors：例外和缺陷類別-Footnote-210763210
Node: email headerregistry：自訂標頭物件10763269
Ref: library/email headerregistry doc10763479
Ref: 340910763479
Ref: library/email headerregistry email-headerregistry-custom-header-objects10763479
Ref: 340a10763479
Ref: library/email headerregistry module-email headerregistry10763479
Ref: 3910763479
Ref: library/email headerregistry email headerregistry BaseHeader10765236
Ref: 339b10765236
Ref: library/email headerregistry email headerregistry BaseHeader name10765550
Ref: 340d10765550
Ref: library/email headerregistry email headerregistry BaseHeader defects10765794
Ref: 340e10765794
Ref: library/email headerregistry email headerregistry BaseHeader max_count10766150
Ref: 33f010766150
Ref: library/email headerregistry email headerregistry BaseHeader fold10766664
Ref: 340f10766664
Ref: library/email headerregistry email headerregistry UnstructuredHeader10768853
Ref: 340c10768853
Ref: library/email headerregistry email headerregistry DateHeader10769929
Ref: 341010769929
Ref: library/email headerregistry email headerregistry DateHeader datetime10770289
Ref: 341110770289
Ref: library/email headerregistry email headerregistry AddressHeader10771855
Ref: 341210771855
Ref: library/email headerregistry email headerregistry AddressHeader groups10772140
Ref: 341310772140
Ref: library/email headerregistry email headerregistry AddressHeader addresses10772452
Ref: 341610772452
Ref: library/email headerregistry email headerregistry SingleAddressHeader10773607
Ref: 341810773607
Ref: library/email headerregistry email headerregistry SingleAddressHeader address10773749
Ref: 341910773749
Ref: library/email headerregistry email headerregistry MIMEVersionHeader10774278
Ref: 341a10774278
Ref: library/email headerregistry email headerregistry MIMEVersionHeader version10774671
Ref: 341b10774671
Ref: library/email headerregistry email headerregistry MIMEVersionHeader major10774795
Ref: 341c10774795
Ref: library/email headerregistry email headerregistry MIMEVersionHeader minor10774869
Ref: 341d10774869
Ref: library/email headerregistry email headerregistry ParameterizedMIMEHeader10774943
Ref: 341e10774943
Ref: library/email headerregistry email headerregistry ParameterizedMIMEHeader params10775323
Ref: 33a910775323
Ref: library/email headerregistry email headerregistry ContentTypeHeader10775417
Ref: 341f10775417
Ref: library/email headerregistry email headerregistry ContentTypeHeader content_type10775569
Ref: 342010775569
Ref: library/email headerregistry email headerregistry ContentTypeHeader maintype10775672
Ref: 342110775672
Ref: library/email headerregistry email headerregistry ContentTypeHeader subtype10775699
Ref: 342210775699
Ref: library/email headerregistry email headerregistry ContentDispositionHeader10775725
Ref: 342310775725
Ref: library/email headerregistry email headerregistry ContentDispositionHeader content_disposition10775891
Ref: 342410775891
Ref: library/email headerregistry email headerregistry ContentTransferEncoding10776025
Ref: 342510776025
Ref: library/email headerregistry email headerregistry ContentTransferEncoding cte10776141
Ref: 342610776141
Ref: library/email headerregistry email headerregistry HeaderRegistry10776307
Ref: 340b10776307
Ref: library/email headerregistry email headerregistry HeaderRegistry map_to_type10778027
Ref: 342710778027
Ref: library/email headerregistry email headerregistry HeaderRegistry __getitem__10778362
Ref: 342810778362
Ref: library/email headerregistry email headerregistry HeaderRegistry __call__10778485
Ref: 342910778485
Ref: library/email headerregistry email headerregistry Address10779125
Ref: 341710779125
Ref: library/email headerregistry email headerregistry Address display_name10779971
Ref: 342a10779971
Ref: library/email headerregistry email headerregistry Address username10780194
Ref: 342b10780194
Ref: library/email headerregistry email headerregistry Address domain10780311
Ref: 342c10780311
Ref: library/email headerregistry email headerregistry Address addr_spec10780388
Ref: 342d10780388
Ref: library/email headerregistry email headerregistry Address __str__10780603
Ref: 342e10780603
Ref: library/email headerregistry email headerregistry Group10781042
Ref: 341410781042
Ref: library/email headerregistry email headerregistry Group display_name10781582
Ref: 341510781582
Ref: library/email headerregistry email headerregistry Group addresses10781834
Ref: 342f10781834
Ref: library/email headerregistry email headerregistry Group __str__10781979
Ref: 343010781979
Ref: email headerregistry：自訂標頭物件-Footnote-110782432
Ref: email headerregistry：自訂標頭物件-Footnote-210782513
Ref: email headerregistry：自訂標頭物件-Footnote-310782581
Ref: email headerregistry：自訂標頭物件-Footnote-410782640
Ref: email headerregistry：自訂標頭物件-Footnote-510782699
Ref: email headerregistry：自訂標頭物件-Footnote-610782758
Ref: email headerregistry：自訂標頭物件-Footnote-710782817
Ref: email headerregistry：自訂標頭物件-Footnote-810782876
Ref: email headerregistry：自訂標頭物件-Footnote-910782935
Ref: email headerregistry：自訂標頭物件-Footnote-1010782994
Ref: email headerregistry：自訂標頭物件-Footnote-1110783054
Ref: email headerregistry：自訂標頭物件-Footnote-1210783114
Ref: email headerregistry：自訂標頭物件-Footnote-1310783174
Ref: email headerregistry：自訂標頭物件-Footnote-1410783234
Ref: email headerregistry：自訂標頭物件-Footnote-1510783294
Ref: email headerregistry：自訂標頭物件-Footnote-1610783354
Ref: email headerregistry：自訂標頭物件-Footnote-1710783414
Node: email contentmanager：管理 MIME 內容10783474
Ref: library/email contentmanager doc10783662
Ref: 343110783662
Ref: library/email contentmanager email-contentmanager-managing-mime-content10783662
Ref: 343210783662
Ref: library/email contentmanager module-email contentmanager10783662
Ref: 3410783662
Ref: library/email contentmanager email contentmanager ContentManager10783911
Ref: 343310783911
Ref: library/email contentmanager email contentmanager ContentManager get_content10784201
Ref: 33ba10784201
Ref: library/email contentmanager email contentmanager ContentManager set_content10785035
Ref: 33bb10785035
Ref: library/email contentmanager email contentmanager ContentManager add_get_handler10786627
Ref: 343510786627
Ref: library/email contentmanager email contentmanager ContentManager add_set_handler10786819
Ref: 343710786819
Ref: email contentmanager：管理 MIME 內容-Footnote-110787184
Ref: email contentmanager：管理 MIME 內容-Footnote-210787265
Node: Content Manager Instances10787333
Ref: library/email contentmanager content-manager-instances10787436
Ref: 343910787436
Ref: library/email contentmanager email contentmanager raw_data_manager10787777
Ref: 33ee10787777
Ref: library/email contentmanager email contentmanager get_content10788509
Ref: 343610788509
Ref: library/email contentmanager email contentmanager set_content10789093
Ref: 343810789093
Ref: Content Manager Instances-Footnote-110793392
Node: email：範例10793451
Ref: library/email examples doc10793672
Ref: 343a10793672
Ref: library/email examples email-examples10793672
Ref: ee010793672
Ref: library/email examples id110793672
Ref: 343b10793672
Ref: email：範例-Footnote-110808298
Ref: email：範例-Footnote-210808356
Node: email message Message Representing an email message using the compat32 API10808438
Ref: library/email compat32-message doc10808676
Ref: 343c10808676
Ref: library/email compat32-message compat32-message10808676
Ref: 338b10808676
Ref: library/email compat32-message email-message-message-representing-an-email-message-using-the-compat32-api10808676
Ref: 343d10808676
Ref: library/email compat32-message email message Message10811232
Ref: 26110811232
Ref: library/email compat32-message email message Message as_string10811758
Ref: eda10811758
Ref: library/email compat32-message email message Message __str__10813886
Ref: 343e10813886
Ref: library/email compat32-message email message Message as_bytes10814051
Ref: edb10814051
Ref: library/email compat32-message email message Message __bytes__10815609
Ref: edc10815609
Ref: library/email compat32-message email message Message is_multipart10815816
Ref: 33b310815816
Ref: library/email compat32-message email message Message set_unixfrom10816482
Ref: 343f10816482
Ref: library/email compat32-message email message Message get_unixfrom10816620
Ref: 344010816620
Ref: library/email compat32-message email message Message attach10816775
Ref: 33c010816775
Ref: library/email compat32-message email message Message get_payload10817393
Ref: 116510817393
Ref: library/email compat32-message email message Message set_payload10820040
Ref: 344110820040
Ref: library/email compat32-message email message Message set_charset10820502
Ref: 344210820502
Ref: library/email compat32-message email message Message get_charset10822261
Ref: 344310822261
Ref: library/email compat32-message email message Message __len__10823709
Ref: 344510823709
Ref: library/email compat32-message email message Message __contains__10823807
Ref: 168210823807
Ref: library/email compat32-message email message Message __getitem__10824177
Ref: 344610824177
Ref: library/email compat32-message email message Message __setitem__10824710
Ref: 344810824710
Ref: library/email compat32-message email message Message __delitem__10825265
Ref: 344910825265
Ref: library/email compat32-message email message Message keys10825487
Ref: 344410825487
Ref: library/email compat32-message email message Message values10825579
Ref: 344a10825579
Ref: library/email compat32-message email message Message items10825667
Ref: 344b10825667
Ref: library/email compat32-message email message Message get10825796
Ref: 344c10825796
Ref: library/email compat32-message email message Message get_all10826109
Ref: 344710826109
Ref: library/email compat32-message email message Message add_header10826346
Ref: 344d10826346
Ref: library/email compat32-message email message Message replace_header10828313
Ref: 344e10828313
Ref: library/email compat32-message email message Message get_content_type10828602
Ref: 344f10828602
Ref: library/email compat32-message email message Message get_content_maintype10829456
Ref: 345110829456
Ref: library/email compat32-message email message Message get_content_subtype10829660
Ref: 345210829660
Ref: library/email compat32-message email message Message get_default_type10829851
Ref: 345010829851
Ref: library/email compat32-message email message Message set_default_type10830171
Ref: 345310830171
Ref: library/email compat32-message email message Message get_params10830458
Ref: 345410830458
Ref: library/email compat32-message email message Message get_param10831512
Ref: 345510831512
Ref: library/email compat32-message email message Message set_param10833506
Ref: edd10833506
Ref: library/email compat32-message email message Message del_param10834771
Ref: 345710834771
Ref: library/email compat32-message email message Message set_type10835212
Ref: 345810835212
Ref: library/email compat32-message email message Message get_filename10836083
Ref: 345910836083
Ref: library/email compat32-message email message Message get_boundary10836622
Ref: 345a10836622
Ref: library/email compat32-message email message Message set_boundary10836986
Ref: 345b10836986
Ref: library/email compat32-message email message Message get_content_charset10837801
Ref: 345c10837801
Ref: library/email compat32-message email message Message get_charsets10838289
Ref: 345d10838289
Ref: library/email compat32-message email message Message get_content_disposition10838991
Ref: d9d10838991
Ref: library/email compat32-message email message Message walk10839354
Ref: 345e10839354
Ref: library/email compat32-message email message Message preamble10841472
Ref: 345f10841472
Ref: library/email compat32-message email message Message epilogue10842731
Ref: 346010842731
Ref: library/email compat32-message email message Message defects10843127
Ref: 346110843127
Ref: email message Message Representing an email message using the compat32 API-Footnote-110843402
Ref: email message Message Representing an email message using the compat32 API-Footnote-210843461
Ref: email message Message Representing an email message using the compat32 API-Footnote-310843520
Ref: email message Message Representing an email message using the compat32 API-Footnote-410843579
Ref: email message Message Representing an email message using the compat32 API-Footnote-510843638
Ref: email message Message Representing an email message using the compat32 API-Footnote-610843697
Ref: email message Message Representing an email message using the compat32 API-Footnote-710843756
Ref: email message Message Representing an email message using the compat32 API-Footnote-810843815
Ref: email message Message Representing an email message using the compat32 API-Footnote-910843874
Ref: email message Message Representing an email message using the compat32 API-Footnote-1010843933
Ref: email message Message Representing an email message using the compat32 API-Footnote-1110843993
Ref: email message Message Representing an email message using the compat32 API-Footnote-1210844053
Node: email mime：從頭開始建立電子郵件和 MIME 物件10844113
Ref: library/email mime doc10844367
Ref: 346210844367
Ref: library/email mime email-mime-creating-email-and-mime-objects-from-scratch10844367
Ref: 346310844367
Ref: library/email mime module-email mime10844367
Ref: 3c10844367
Ref: library/email mime module-email mime base10845592
Ref: 3f10845592
Ref: library/email mime email mime base MIMEBase10845592
Ref: 346410845592
Ref: library/email mime module-email mime nonmultipart10846740
Ref: 4310846740
Ref: library/email mime email mime nonmultipart MIMENonMultipart10846740
Ref: 340510846740
Ref: library/email mime module-email mime multipart10847239
Ref: 4210847239
Ref: library/email mime email mime multipart MIMEMultipart10847239
Ref: 346510847239
Ref: library/email mime module-email mime application10848559
Ref: 3d10848559
Ref: library/email mime email mime application MIMEApplication10848559
Ref: 346610848559
Ref: library/email mime module-email mime audio10849916
Ref: 3e10849916
Ref: library/email mime email mime audio MIMEAudio10849916
Ref: 346710849916
Ref: library/email mime module-email mime image10851485
Ref: 4010851485
Ref: library/email mime email mime image MIMEImage10851485
Ref: 340610851485
Ref: library/email mime module-email mime message10853134
Ref: 4110853134
Ref: library/email mime email mime message MIMEMessage10853134
Ref: 346810853134
Ref: library/email mime module-email mime text10853825
Ref: 4410853825
Ref: library/email mime email mime text MIMEText10853825
Ref: d9f10853825
Ref: email mime：從頭開始建立電子郵件和 MIME 物件-Footnote-110855464
Node: email header：國際化標頭10855532
Ref: library/email header doc10855746
Ref: 346910855746
Ref: library/email header email-header-internationalized-headers10855746
Ref: 346a10855746
Ref: library/email header module-email header10855746
Ref: 3810855746
Ref: library/email header email header Header10858418
Ref: 17ac10858418
Ref: library/email header email header Header append10860286
Ref: 346b10860286
Ref: library/email header email header Header encode10861621
Ref: 346c10861621
Ref: library/email header email header Header __str__10863248
Ref: 346d10863248
Ref: library/email header email header Header __eq__10863745
Ref: 346e10863745
Ref: library/email header email header Header __ne__10863881
Ref: 346f10863881
Ref: library/email header email header decode_header10864105
Ref: 105210864105
Ref: library/email header email header make_header10864760
Ref: 105310864760
Ref: email header：國際化標頭-Footnote-110865457
Ref: email header：國際化標頭-Footnote-210865529
Ref: email header：國際化標頭-Footnote-310865588
Ref: email header：國際化標頭-Footnote-410865646
Ref: email header：國際化標頭-Footnote-510865705
Ref: email header：國際化標頭-Footnote-610865764
Ref: email header：國際化標頭-Footnote-710865823
Ref: email header：國際化標頭-Footnote-810865882
Ref: email header：國際化標頭-Footnote-910865941
Ref: email header：國際化標頭-Footnote-1010866000
Ref: email header：國際化標頭-Footnote-1110866060
Ref: email header：國際化標頭-Footnote-1210866120
Ref: email header：國際化標頭-Footnote-1310866180
Ref: email header：國際化標頭-Footnote-1410866240
Ref: email header：國際化標頭-Footnote-1510866300
Node: email charset：表示字元集合10866360
Ref: library/email charset doc10866542
Ref: 347010866542
Ref: library/email charset email-charset-representing-character-sets10866542
Ref: 347110866542
Ref: library/email charset module-email charset10866542
Ref: 3310866542
Ref: library/email charset email charset Charset10867274
Ref: da010867274
Ref: library/email charset email charset Charset input_charset10868800
Ref: 347210868800
Ref: library/email charset email charset Charset header_encoding10869053
Ref: 347310869053
Ref: library/email charset email charset Charset body_encoding10869436
Ref: 347410869436
Ref: library/email charset email charset Charset output_charset10869708
Ref: 347510869708
Ref: library/email charset email charset Charset input_codec10870044
Ref: 347610870044
Ref: library/email charset email charset Charset output_codec10870255
Ref: 347710870255
Ref: library/email charset email charset Charset get_body_encoding10870564
Ref: 347810870564
Ref: library/email charset email charset Charset get_output_charset10871281
Ref: 347910871281
Ref: library/email charset email charset Charset header_encode10871485
Ref: 347a10871485
Ref: library/email charset email charset Charset header_encode_lines10871693
Ref: 347b10871693
Ref: library/email charset email charset Charset body_encode10872126
Ref: 347c10872126
Ref: library/email charset email charset Charset __str__10872458
Ref: 347d10872458
Ref: library/email charset email charset Charset __eq__10872617
Ref: 347e10872617
Ref: library/email charset email charset Charset __ne__10872753
Ref: 347f10872753
Ref: library/email charset email charset add_charset10873047
Ref: 348010873047
Ref: library/email charset email charset add_alias10874366
Ref: 348210874366
Ref: library/email charset email charset add_codec10874688
Ref: 348110874688
Ref: email charset：表示字元集合-Footnote-110875078
Node: email encoders：編碼器10875151
Ref: library/email encoders doc10875329
Ref: 348310875329
Ref: library/email encoders email-encoders-encoders10875329
Ref: 348410875329
Ref: library/email encoders module-email encoders10875329
Ref: 3510875329
Ref: library/email encoders email encoders encode_quopri10876930
Ref: 348510876930
Ref: library/email encoders email encoders encode_base6410877268
Ref: 348610877268
Ref: library/email encoders email encoders encode_7or8bit10877633
Ref: 348710877633
Ref: library/email encoders email encoders encode_noop10877858
Ref: 348810877858
Ref: email encoders：編碼器-Footnote-110878034
Ref: email encoders：編碼器-Footnote-210878108
Node: email utils：雜項工具10878254
Ref: library/email utils doc10878425
Ref: 348910878425
Ref: library/email utils email-utils-miscellaneous-utilities10878425
Ref: 348a10878425
Ref: library/email utils module-email utils10878425
Ref: 4710878425
Ref: library/email utils email utils localtime10878695
Ref: 2a610878695
Ref: library/email utils email utils make_msgid10879280
Ref: 348b10879280
Ref: library/email utils email utils quote10880170
Ref: 348c10880170
Ref: library/email utils email utils unquote10880347
Ref: 33ac10880347
Ref: library/email utils email utils parseaddr10880615
Ref: 1c510880615
Ref: library/email utils email utils formataddr10881174
Ref: 113310881174
Ref: library/email utils email utils getaddresses10881849
Ref: 1c410881849
Ref: library/email utils email utils parsedate10882689
Ref: 348d10882689
Ref: library/email utils email utils parsedate_tz10883315
Ref: 178110883315
Ref: library/email utils email utils parsedate_to_datetime10883891
Ref: 105810883891
Ref: library/email utils email utils mktime_tz10884771
Ref: 348e10884771
Ref: library/email utils email utils formatdate10885006
Ref: 13d510885006
Ref: library/email utils email utils format_datetime10885951
Ref: 105710885951
Ref: library/email utils email utils decode_rfc223110886635
Ref: 348f10886635
Ref: library/email utils email utils encode_rfc223110886733
Ref: 349010886733
Ref: library/email utils email utils collapse_rfc2231_value10887129
Ref: 345610887129
Ref: library/email utils email utils decode_params10887979
Ref: 349110887979
Ref: email utils：雜項工具-Footnote-110888246
Ref: email utils：雜項工具-Footnote-210888317
Ref: email utils：雜項工具-Footnote-310888376
Ref: email utils：雜項工具-Footnote-410888435
Ref: email utils：雜項工具-Footnote-510888494
Ref: email utils：雜項工具-Footnote-610888553
Ref: email utils：雜項工具-Footnote-710888826
Ref: email utils：雜項工具-Footnote-810888885
Ref: email utils：雜項工具-Footnote-910888944
Ref: email utils：雜項工具-Footnote-1010889003
Ref: email utils：雜項工具-Footnote-1110889063
Ref: email utils：雜項工具-Footnote-1210889123
Node: email iterators：疊代器10889183
Ref: library/email iterators doc10889319
Ref: 349210889319
Ref: library/email iterators email-iterators-iterators10889319
Ref: 349310889319
Ref: library/email iterators module-email iterators10889319
Ref: 3a10889319
Ref: library/email iterators email iterators body_line_iterator10889716
Ref: 349410889716
Ref: library/email iterators email iterators typed_subpart_iterator10890290
Ref: 349510890290
Ref: library/email iterators email iterators _structure10891006
Ref: 349610891006
Ref: email iterators：疊代器-Footnote-110892422
Node: json --- JSON 編碼器與解碼器10892498
Ref: library/json doc10892694
Ref: 349710892694
Ref: library/json json-json-encoder-and-decoder10892694
Ref: 349810892694
Ref: library/json module-json10892694
Ref: 7610892694
Ref: json --- JSON 編碼器與解碼器-Footnote-110897258
Ref: json --- JSON 編碼器與解碼器-Footnote-210897331
Ref: json --- JSON 編碼器與解碼器-Footnote-310897356
Ref: json --- JSON 編碼器與解碼器-Footnote-410897415
Ref: json --- JSON 編碼器與解碼器-Footnote-510897474
Ref: json --- JSON 編碼器與解碼器-Footnote-610897565
Ref: json --- JSON 編碼器與解碼器-Footnote-710897614
Ref: json --- JSON 編碼器與解碼器-Footnote-810897861
Node: 基本用法<2>10897887
Ref: library/json basic-usage10898004
Ref: 349a10898004
Ref: library/json json dump10898045
Ref: ceb10898045
Ref: library/json json dumps10901757
Ref: cec10901757
Ref: library/json json load10902560
Ref: c5b10902560
Ref: library/json json loads10905687
Ref: 8f910905687
Ref: 基本用法<2>-Footnote-110906576
Node: 編碼器與解碼器10906608
Ref: library/json encoders-and-decoders10906744
Ref: 349e10906744
Ref: library/json json JSONDecoder10906800
Ref: cee10906800
Ref: library/json json-to-py-table10907039
Ref: 349d10907039
Ref: library/json json JSONDecoder decode10910079
Ref: 349f10910079
Ref: library/json json JSONDecoder raw_decode10910334
Ref: 34a010910334
Ref: library/json json JSONEncoder10910690
Ref: ced10910690
Ref: library/json py-to-json-table10910978
Ref: 349b10910978
Ref: library/json json JSONEncoder default10915459
Ref: 349c10915459
Ref: library/json json JSONEncoder encode10916172
Ref: 34a110916172
Ref: library/json json JSONEncoder iterencode10916404
Ref: 34a210916404
Ref: 編碼器與解碼器-Footnote-110916723
Node: 例外<12>10916755
Ref: library/json exceptions10916919
Ref: 34a310916919
Ref: library/json json JSONDecodeError10916950
Ref: dc610916950
Ref: library/json json JSONDecodeError msg10917069
Ref: 34a410917069
Ref: library/json json JSONDecodeError doc10917136
Ref: 34a510917136
Ref: library/json json JSONDecodeError pos10917203
Ref: 34a610917203
Ref: library/json json JSONDecodeError lineno10917285
Ref: 34a710917285
Ref: library/json json JSONDecodeError colno10917356
Ref: 34a810917356
Node: 合規性與互通性（Interoperability）10917456
Ref: library/json standard-compliance-and-interoperability10917617
Ref: 34a910917617
Ref: 合規性與互通性（Interoperability）-Footnote-110918671
Ref: 合規性與互通性（Interoperability）-Footnote-210918730
Node: 字元編碼格式10918821
Ref: library/json character-encodings10918952
Ref: 34aa10918952
Node: 正負無限與非數值10920252
Ref: library/json infinite-and-nan-number-values10920416
Ref: 34ab10920416
Node: 物件內重複的名稱10921125
Ref: library/json repeated-names-within-an-object10921310
Ref: 34ac10921310
Node: 位於頂層的非物件及非列表值10921782
Ref: library/json top-level-non-object-non-array-values10921955
Ref: 34ad10921955
Ref: 位於頂層的非物件及非列表值-Footnote-110922519
Ref: 位於頂層的非物件及非列表值-Footnote-210922578
Node: 實作限制10922637
Ref: library/json implementation-limitations10922777
Ref: 34ae10922777
Node: 命令列介面<3>10923605
Ref: library/json command-line-interface10923747
Ref: 34af10923747
Ref: library/json json-commandline10923747
Ref: 349910923747
Ref: library/json module-json tool10923747
Ref: 7710923747
Ref: 命令列介面<3>-Footnote-110924650
Node: 命令列選項<3>10924719
Ref: library/json command-line-options10924792
Ref: 34b110924792
Ref: library/json cmdoption-json tool-arg-infile10924840
Ref: 34b210924840
Ref: library/json cmdoption-json tool-arg-outfile10925333
Ref: 34b310925333
Ref: library/json cmdoption-json tool-sort-keys10925469
Ref: 34b010925469
Ref: library/json cmdoption-json tool-no-ensure-ascii10925586
Ref: 34b410925586
Ref: library/json cmdoption-json tool-json-lines10925746
Ref: 34b510925746
Ref: library/json cmdoption-json tool-indent10925864
Ref: 34b610925864
Ref: library/json cmdoption-json tool-tab10925864
Ref: 34b710925864
Ref: library/json cmdoption-json tool-no-indent10925864
Ref: 34b810925864
Ref: library/json cmdoption-json tool-compact10925864
Ref: 34b910925864
Ref: library/json cmdoption-json tool-h10925988
Ref: 34ba10925988
Ref: library/json cmdoption-json tool-help10925988
Ref: 34bb10925988
Node: mailbox --- 以各種格式操作郵件信箱10926053
Ref: library/mailbox doc10926262
Ref: 34bc10926262
Ref: library/mailbox mailbox-manipulate-mailboxes-in-various-formats10926262
Ref: 34bd10926262
Ref: library/mailbox module-mailbox10926262
Ref: 7f10926262
Ref: mailbox --- 以各種格式操作郵件信箱-Footnote-110927103
Node: Mailbox 物件10927170
Ref: library/mailbox id110927289
Ref: 34be10927289
Ref: library/mailbox mailbox-objects10927289
Ref: 34bf10927289
Ref: library/mailbox mailbox Mailbox10927344
Ref: 11e510927344
Ref: library/mailbox mailbox Mailbox add10930129
Ref: 11e410930129
Ref: library/mailbox mailbox Mailbox remove10930918
Ref: 34c010930918
Ref: library/mailbox mailbox Mailbox __delitem__10930948
Ref: 34c410930948
Ref: library/mailbox mailbox Mailbox discard10930983
Ref: 34c110930983
Ref: library/mailbox mailbox Mailbox __setitem__10931528
Ref: 34c510931528
Ref: library/mailbox mailbox Mailbox iterkeys10932412
Ref: 34c610932412
Ref: library/mailbox mailbox Mailbox keys10932498
Ref: 34c710932498
Ref: library/mailbox mailbox Mailbox itervalues10932660
Ref: 34c810932660
Ref: library/mailbox mailbox Mailbox __iter__10932691
Ref: 34c910932691
Ref: library/mailbox mailbox Mailbox values10933180
Ref: 34ca10933180
Ref: library/mailbox mailbox Mailbox iteritems10933346
Ref: 34cb10933346
Ref: library/mailbox mailbox Mailbox items10933767
Ref: 34cc10933767
Ref: library/mailbox mailbox Mailbox get10933960
Ref: 34cd10933960
Ref: library/mailbox mailbox Mailbox __getitem__10934001
Ref: 34ce10934001
Ref: library/mailbox mailbox Mailbox get_message10934576
Ref: 34cf10934576
Ref: library/mailbox mailbox Mailbox get_bytes10934865
Ref: 11e710934865
Ref: library/mailbox mailbox Mailbox get_string10935100
Ref: 11e810935100
Ref: library/mailbox mailbox Mailbox get_file10935439
Ref: 11e610935439
Ref: library/mailbox mailbox Mailbox __contains__10936470
Ref: 34d010936470
Ref: library/mailbox mailbox Mailbox __len__10936604
Ref: 34d110936604
Ref: library/mailbox mailbox Mailbox clear10936687
Ref: 34d210936687
Ref: library/mailbox mailbox Mailbox pop10936763
Ref: 34d310936763
Ref: library/mailbox mailbox Mailbox popitem10937201
Ref: 34d410937201
Ref: library/mailbox mailbox Mailbox update10937717
Ref: 34d510937717
Ref: library/mailbox mailbox Mailbox flush10938421
Ref: 34d610938421
Ref: library/mailbox mailbox Mailbox lock10938706
Ref: 34c210938706
Ref: library/mailbox mailbox Mailbox unlock10939125
Ref: 34c310939125
Ref: library/mailbox mailbox Mailbox close10939205
Ref: 34d810939205
Node: Mailbox 物件<2>10939504
Ref: library/mailbox mailbox-maildir10939592
Ref: 34d910939592
Ref: library/mailbox maildir-objects10939592
Ref: 34da10939592
Ref: library/mailbox mailbox Maildir10939647
Ref: 35310939647
Ref: library/mailbox mailbox Maildir colon10941771
Ref: 34dc10941771
Ref: library/mailbox mailbox Maildir list_folders10942580
Ref: 34dd10942580
Ref: library/mailbox mailbox Maildir get_folder10942668
Ref: 34de10942668
Ref: library/mailbox mailbox Maildir add_folder10942902
Ref: 34e010942902
Ref: library/mailbox mailbox Maildir remove_folder10943053
Ref: 34e110943053
Ref: library/mailbox mailbox Maildir clean10943295
Ref: 34e310943295
Ref: library/mailbox mailbox Maildir get_flags10943531
Ref: 15cc10943531
Ref: library/mailbox mailbox Maildir set_flags10944332
Ref: 15cd10944332
Ref: library/mailbox mailbox Maildir add_flag10945081
Ref: 15ce10945081
Ref: library/mailbox mailbox Maildir remove_flag10945591
Ref: 15cf10945591
Ref: library/mailbox mailbox Maildir get_info10946112
Ref: 15ca10946112
Ref: library/mailbox mailbox Maildir set_info10946838
Ref: 15cb10946838
Ref: library/mailbox mailbox Maildir add10947634
Ref: 34eb10947634
Ref: library/mailbox mailbox Maildir __setitem__10947665
Ref: 34e810947665
Ref: library/mailbox mailbox Maildir update10947709
Ref: 34ec10947709
Ref: library/mailbox mailbox Maildir flush10948121
Ref: 34ed10948121
Ref: library/mailbox mailbox Maildir lock10948256
Ref: 34ee10948256
Ref: library/mailbox mailbox Maildir unlock10948281
Ref: 34ef10948281
Ref: library/mailbox mailbox Maildir close10948414
Ref: 34f010948414
Ref: library/mailbox mailbox Maildir get_file10948605
Ref: 34f110948605
Ref: Mailbox 物件<2>-Footnote-110949136
Ref: Mailbox 物件<2>-Footnote-210949185
Node: mbox 物件10949229
Ref: library/mailbox mailbox-mbox10949335
Ref: 34f210949335
Ref: library/mailbox mbox-objects10949335
Ref: 34f310949335
Ref: library/mailbox mailbox mbox10949384
Ref: 157510949384
Ref: library/mailbox mailbox mbox get_file10950784
Ref: 34f410950784
Ref: library/mailbox mailbox mbox lock10951004
Ref: 34f510951004
Ref: library/mailbox mailbox mbox unlock10951029
Ref: 34f610951029
Ref: mbox 物件-Footnote-110951604
Ref: mbox 物件-Footnote-210951664
Ref: mbox 物件-Footnote-310951716
Node: MH 物件10951794
Ref: library/mailbox mailbox-mh10951895
Ref: 34f710951895
Ref: library/mailbox mh-objects10951895
Ref: 34f810951895
Ref: library/mailbox mailbox MH10951940
Ref: 15ae10951940
Ref: library/mailbox mailbox MH list_folders10953472
Ref: 34fa10953472
Ref: library/mailbox mailbox MH get_folder10953560
Ref: 34fb10953560
Ref: library/mailbox mailbox MH add_folder10953790
Ref: 34fc10953790
Ref: library/mailbox mailbox MH remove_folder10953937
Ref: 34fd10953937
Ref: library/mailbox mailbox MH get_sequences10954179
Ref: 34fe10954179
Ref: library/mailbox mailbox MH set_sequences10954356
Ref: 34ff10954356
Ref: library/mailbox mailbox MH pack10954594
Ref: 350010954594
Ref: library/mailbox mailbox MH remove10955011
Ref: 350110955011
Ref: library/mailbox mailbox MH __delitem__10955041
Ref: 350210955041
Ref: library/mailbox mailbox MH discard10955076
Ref: 350310955076
Ref: library/mailbox mailbox MH lock10955285
Ref: 350410955285
Ref: library/mailbox mailbox MH unlock10955310
Ref: 350510955310
Ref: library/mailbox mailbox MH get_file10955684
Ref: 350610955684
Ref: library/mailbox mailbox MH flush10955876
Ref: 350710955876
Ref: library/mailbox mailbox MH close10956006
Ref: 350810956006
Ref: MH 物件-Footnote-110956465
Ref: MH 物件-Footnote-210956501
Node: Babyl 物件10956546
Ref: library/mailbox babyl-objects10956647
Ref: 350910956647
Ref: library/mailbox mailbox-babyl10956647
Ref: 350a10956647
Ref: library/mailbox mailbox Babyl10956698
Ref: 350b10956698
Ref: library/mailbox mailbox Babyl get_labels10958263
Ref: 350d10958263
Ref: library/mailbox mailbox Babyl get_file10958792
Ref: 350e10958792
Ref: library/mailbox mailbox Babyl lock10959312
Ref: 350f10959312
Ref: library/mailbox mailbox Babyl unlock10959337
Ref: 351010959337
Ref: Babyl 物件-Footnote-110959729
Ref: Babyl 物件-Footnote-210959773
Node: MMDF 物件10959851
Ref: library/mailbox mailbox-mmdf10959934
Ref: 351110959934
Ref: library/mailbox mmdf-objects10959934
Ref: 351210959934
Ref: library/mailbox mailbox MMDF10959983
Ref: 157610959983
Ref: library/mailbox mailbox MMDF get_file10961230
Ref: 351410961230
Ref: library/mailbox mailbox MMDF lock10961450
Ref: 351510961450
Ref: library/mailbox mailbox MMDF unlock10961475
Ref: 351610961475
Ref: MMDF 物件-Footnote-110961910
Ref: MMDF 物件-Footnote-210961970
Node: Message 物件10962013
Ref: library/mailbox mailbox-message-objects10962151
Ref: 351710962151
Ref: library/mailbox message-objects10962151
Ref: 351810962151
Ref: library/mailbox mailbox Message10962206
Ref: 11e910962206
Ref: Message 物件-Footnote-110964245
Node: MaildirMessage 物件10964304
Ref: library/mailbox mailbox-maildirmessage10964403
Ref: 351910964403
Ref: library/mailbox maildirmessage-objects10964403
Ref: 351a10964403
Ref: library/mailbox mailbox MaildirMessage10964472
Ref: 34db10964472
Ref: library/mailbox mailbox MaildirMessage get_subdir10966299
Ref: 351b10966299
Ref: library/mailbox mailbox MaildirMessage set_subdir10966807
Ref: 351c10966807
Ref: library/mailbox mailbox MaildirMessage get_flags10966970
Ref: 34e410966970
Ref: library/mailbox mailbox MaildirMessage set_flags10967438
Ref: 34e510967438
Ref: library/mailbox mailbox MaildirMessage add_flag10967542
Ref: 34e610967542
Ref: library/mailbox mailbox MaildirMessage remove_flag10967888
Ref: 34e710967888
Ref: library/mailbox mailbox MaildirMessage get_date10968235
Ref: 351d10968235
Ref: library/mailbox mailbox MaildirMessage set_date10968391
Ref: 351e10968391
Ref: library/mailbox mailbox MaildirMessage get_info10968556
Ref: 34e910968556
Ref: library/mailbox mailbox MaildirMessage set_info10968771
Ref: 34ea10968771
Node: mboxMessage 物件10971504
Ref: library/mailbox mailbox-mboxmessage10971628
Ref: 351f10971628
Ref: library/mailbox mboxmessage-objects10971628
Ref: 352010971628
Ref: library/mailbox mailbox mboxMessage10971691
Ref: 339410971691
Ref: library/mailbox mailbox mboxMessage get_from10973464
Ref: 352110973464
Ref: library/mailbox mailbox mboxMessage set_from10973687
Ref: 352210973687
Ref: library/mailbox mailbox mboxMessage get_flags10974217
Ref: 352310974217
Ref: library/mailbox mailbox mboxMessage set_flags10974565
Ref: 352410974565
Ref: library/mailbox mailbox mboxMessage add_flag10974856
Ref: 352510974856
Ref: library/mailbox mailbox mboxMessage remove_flag10975076
Ref: 352610975076
Node: MHMessage 物件10978008
Ref: library/mailbox mailbox-mhmessage10978130
Ref: 352710978130
Ref: library/mailbox mhmessage-objects10978130
Ref: 352810978130
Ref: library/mailbox mailbox MHMessage10978191
Ref: 34f910978191
Ref: library/mailbox mailbox MHMessage get_sequences10979152
Ref: 352910979152
Ref: library/mailbox mailbox MHMessage set_sequences10979275
Ref: 352a10979275
Ref: library/mailbox mailbox MHMessage add_sequence10979383
Ref: 352b10979383
Ref: library/mailbox mailbox MHMessage remove_sequence10979513
Ref: 352c10979513
Node: BabylMessage 物件10981338
Ref: library/mailbox babylmessage-objects10981460
Ref: 352d10981460
Ref: library/mailbox mailbox-babylmessage10981460
Ref: 352e10981460
Ref: library/mailbox mailbox BabylMessage10981527
Ref: 350c10981527
Ref: library/mailbox mailbox BabylMessage get_labels10982883
Ref: 352f10982883
Ref: library/mailbox mailbox BabylMessage set_labels10982966
Ref: 353010982966
Ref: library/mailbox mailbox BabylMessage add_label10983066
Ref: 353110983066
Ref: library/mailbox mailbox BabylMessage remove_label10983163
Ref: 353210983163
Ref: library/mailbox mailbox BabylMessage get_visible10983268
Ref: 353310983268
Ref: library/mailbox mailbox BabylMessage set_visible10983434
Ref: 353410983434
Ref: library/mailbox mailbox BabylMessage update_visible10983783
Ref: 353510983783
Node: MMDFMessage 物件10986177
Ref: library/mailbox mailbox-mmdfmessage10986274
Ref: 353610986274
Ref: library/mailbox mmdfmessage-objects10986274
Ref: 353710986274
Ref: library/mailbox mailbox MMDFMessage10986339
Ref: 351310986339
Ref: library/mailbox mailbox MMDFMessage get_from10987996
Ref: 353810987996
Ref: library/mailbox mailbox MMDFMessage set_from10988219
Ref: 353910988219
Ref: library/mailbox mailbox MMDFMessage get_flags10988749
Ref: 353a10988749
Ref: library/mailbox mailbox MMDFMessage set_flags10989097
Ref: 353b10989097
Ref: library/mailbox mailbox MMDFMessage add_flag10989388
Ref: 353c10989388
Ref: library/mailbox mailbox MMDFMessage remove_flag10989608
Ref: 353d10989608
Node: 例外<13>10992541
Ref: library/mailbox exceptions10992675
Ref: 353e10992675
Ref: library/mailbox mailbox Error10992782
Ref: 353f10992782
Ref: library/mailbox mailbox NoSuchMailboxError10992873
Ref: 34df10992873
Ref: library/mailbox mailbox NotEmptyError10993177
Ref: 34e210993177
Ref: library/mailbox mailbox ExternalClashError10993336
Ref: 34d710993336
Ref: library/mailbox mailbox FormatError10993646
Ref: 354010993646
Node: 範例<29>10993840
Ref: library/mailbox examples10993951
Ref: 354110993951
Ref: library/mailbox mailbox-examples10993951
Ref: 354210993951
Node: mimetypes --- 將檔案名稱對映到 MIME 類型10996215
Ref: library/mimetypes doc10996446
Ref: 354310996446
Ref: library/mimetypes mimetypes-map-filenames-to-mime-types10996446
Ref: 354410996446
Ref: library/mimetypes module-mimetypes10996446
Ref: 8210996446
Ref: library/mimetypes mimetypes guess_type10997340
Ref: 1ed10997340
Ref: library/mimetypes mimetypes guess_file_type10998814
Ref: 1ec10998814
Ref: library/mimetypes mimetypes guess_all_extensions10999143
Ref: 179810999143
Ref: library/mimetypes mimetypes guess_extension10999738
Ref: 354610999738
Ref: library/mimetypes mimetypes init11000477
Ref: 354511000477
Ref: library/mimetypes mimetypes read_mime_types11001449
Ref: 184511001449
Ref: library/mimetypes mimetypes add_type11001824
Ref: 354811001824
Ref: library/mimetypes mimetypes inited11002279
Ref: 354911002279
Ref: library/mimetypes mimetypes knownfiles11002451
Ref: 354711002451
Ref: library/mimetypes mimetypes suffix_map11002663
Ref: 354a11002663
Ref: library/mimetypes mimetypes encodings_map11003015
Ref: 354b11003015
Ref: library/mimetypes mimetypes types_map11003116
Ref: 354c11003116
Ref: library/mimetypes mimetypes common_types11003209
Ref: 354d11003209
Ref: mimetypes --- 將檔案名稱對映到 MIME 類型-Footnote-111003745
Ref: mimetypes --- 將檔案名稱對映到 MIME 類型-Footnote-211003814
Node: MimeTypes 物件11003885
Ref: library/mimetypes id111003988
Ref: 354e11003988
Ref: library/mimetypes mimetypes-objects11003988
Ref: 354f11003988
Ref: library/mimetypes mimetypes MimeTypes11004233
Ref: 146911004233
Ref: library/mimetypes mimetypes MimeTypes suffix_map11004916
Ref: 355211004916
Ref: library/mimetypes mimetypes MimeTypes encodings_map11005395
Ref: 355311005395
Ref: library/mimetypes mimetypes MimeTypes types_map11005605
Ref: 355411005605
Ref: library/mimetypes mimetypes MimeTypes types_map_inv11005938
Ref: 355511005938
Ref: library/mimetypes mimetypes MimeTypes guess_extension11006285
Ref: 355611006285
Ref: library/mimetypes mimetypes MimeTypes guess_type11006463
Ref: 193e11006463
Ref: library/mimetypes mimetypes MimeTypes guess_file_type11006629
Ref: 355711006629
Ref: library/mimetypes mimetypes MimeTypes guess_all_extensions11006843
Ref: 355811006843
Ref: library/mimetypes mimetypes MimeTypes read11007031
Ref: 355011007031
Ref: library/mimetypes mimetypes MimeTypes readfp11007344
Ref: 355111007344
Ref: library/mimetypes mimetypes MimeTypes read_windows_registry11007675
Ref: 355911007675
Ref: library/mimetypes mimetypes MimeTypes add_type11008016
Ref: 355a11008016
Node: base64 --- Base16、Base32、Base64、Base85 資料編碼11008507
Ref: library/base64 doc11008743
Ref: 355b11008743
Ref: library/base64 base64-base16-base32-base64-base85-data-encodings11008743
Ref: 355c11008743
Ref: library/base64 module-base6411008743
Ref: a11008743
Ref: library/base64 base64 b64encode11010345
Ref: 355d11010345
Ref: library/base64 base64 b64decode11011034
Ref: 18ab11011034
Ref: library/base64 base64 standard_b64encode11012022
Ref: 355e11012022
Ref: library/base64 base64 standard_b64decode11012202
Ref: 355f11012202
Ref: library/base64 base64 urlsafe_b64encode11012398
Ref: 356011012398
Ref: library/base64 base64 urlsafe_b64decode11012736
Ref: 356111012736
Ref: library/base64 base64 b32encode11013055
Ref: 356211013055
Ref: library/base64 base64 b32decode11013210
Ref: fc811013210
Ref: library/base64 base64 b32hexencode11014108
Ref: 78711014108
Ref: library/base64 base64 b32hexdecode11014315
Ref: 78811014315
Ref: library/base64 base64 b16encode11014727
Ref: 356311014727
Ref: library/base64 base64 b16decode11014882
Ref: 356411014882
Ref: library/base64 base64 a85encode11015333
Ref: ec211015333
Ref: library/base64 base64 a85decode11016269
Ref: ec311016269
Ref: library/base64 base64 b85encode11017057
Ref: ec411017057
Ref: library/base64 base64 b85decode11017441
Ref: ec511017441
Ref: library/base64 base64 z85encode11017673
Ref: 13411017673
Ref: library/base64 base64 z85decode11017917
Ref: 13511017917
Ref: library/base64 base64 decode11018176
Ref: 356511018176
Ref: library/base64 base64 decodebytes11018487
Ref: 8f811018487
Ref: library/base64 base64 encode11018698
Ref: 356611018698
Ref: library/base64 base64 encodebytes11019212
Ref: 8f711019212
Ref: base64 --- Base16、Base32、Base64、Base85 資料編碼-Footnote-111019923
Ref: base64 --- Base16、Base32、Base64、Base85 資料編碼-Footnote-211019989
Ref: base64 --- Base16、Base32、Base64、Base85 資料編碼-Footnote-311020048
Ref: base64 --- Base16、Base32、Base64、Base85 資料編碼-Footnote-411020107
Ref: base64 --- Base16、Base32、Base64、Base85 資料編碼-Footnote-511020166
Ref: base64 --- Base16、Base32、Base64、Base85 資料編碼-Footnote-611020225
Ref: base64 --- Base16、Base32、Base64、Base85 資料編碼-Footnote-711020284
Ref: base64 --- Base16、Base32、Base64、Base85 資料編碼-Footnote-811020343
Ref: base64 --- Base16、Base32、Base64、Base85 資料編碼-Footnote-911020402
Ref: base64 --- Base16、Base32、Base64、Base85 資料編碼-Footnote-1011020461
Ref: base64 --- Base16、Base32、Base64、Base85 資料編碼-Footnote-1111020502
Ref: base64 --- Base16、Base32、Base64、Base85 資料編碼-Footnote-1211020543
Ref: base64 --- Base16、Base32、Base64、Base85 資料編碼-Footnote-1311020603
Node: 安全性注意事項<2>11020663
Ref: library/base64 base64-security11020781
Ref: 356711020781
Ref: library/base64 security-considerations11020781
Ref: 356811020781
Ref: 安全性注意事項<2>-Footnote-111021430
Ref: 安全性注意事項<2>-Footnote-211021489
Node: binascii --- 在二進位制和 ASCII 之間轉換11021548
Ref: library/binascii doc11021787
Ref: 356911021787
Ref: library/binascii binascii-convert-between-binary-and-ascii11021787
Ref: 356a11021787
Ref: library/binascii module-binascii11021787
Ref: c11021787
Ref: library/binascii binascii a2b_uu11022786
Ref: 356b11022786
Ref: library/binascii binascii b2a_uu11023034
Ref: ac511023034
Ref: library/binascii binascii a2b_base6411023405
Ref: 152111023405
Ref: library/binascii binascii b2a_base6411024062
Ref: c2611024062
Ref: library/binascii binascii a2b_qp11024404
Ref: 356c11024404
Ref: library/binascii binascii b2a_qp11024699
Ref: 356d11024699
Ref: library/binascii binascii crc_hqx11025465
Ref: 6d811025465
Ref: library/binascii binascii crc3211025768
Ref: 158c11025768
Ref: library/binascii binascii b2a_hex11026439
Ref: 22f011026439
Ref: library/binascii binascii hexlify11026501
Ref: 356e11026501
Ref: library/binascii binascii a2b_hex11027679
Ref: 22f111027679
Ref: library/binascii binascii unhexlify11027717
Ref: 194d11027717
Ref: library/binascii binascii Error11028243
Ref: fc911028243
Ref: library/binascii binascii Incomplete11028344
Ref: 356f11028344
Ref: binascii --- 在二進位制和 ASCII 之間轉換-Footnote-111028805
Ref: binascii --- 在二進位制和 ASCII 之間轉換-Footnote-211028864
Ref: binascii --- 在二進位制和 ASCII 之間轉換-Footnote-311028923
Node: quopri --- 編碼和解碼 MIME 可列印字元資料11028982
Ref: library/quopri doc11029155
Ref: 357011029155
Ref: library/quopri module-quopri11029155
Ref: a511029155
Ref: library/quopri quopri-encode-and-decode-mime-quoted-printable-data11029155
Ref: 357111029155
Ref: library/quopri quopri decode11029831
Ref: 22f311029831
Ref: library/quopri quopri encode11030319
Ref: 22f211030319
Ref: library/quopri quopri decodestring11030998
Ref: 357211030998
Ref: library/quopri quopri encodestring11031199
Ref: 357311031199
Ref: quopri --- 編碼和解碼 MIME 可列印字元資料-Footnote-111031657
Ref: quopri --- 編碼和解碼 MIME 可列印字元資料-Footnote-211031723
Ref: quopri --- 編碼和解碼 MIME 可列印字元資料-Footnote-311031782
Ref: quopri --- 編碼和解碼 MIME 可列印字元資料-Footnote-411031841
Ref: quopri --- 編碼和解碼 MIME 可列印字元資料-Footnote-511031900
Node: Structured Markup Processing Tools11031959
Ref: library/markup doc11032152
Ref: 357411032152
Ref: library/markup markup11032152
Ref: 357511032152
Ref: library/markup structured-markup-processing-tools11032152
Ref: 357611032152
Node: html --- 超連結標記語言 HTML 支援11033640
Ref: library/html doc11033812
Ref: 357711033812
Ref: library/html html-hypertext-markup-language-support11033812
Ref: 357811033812
Ref: library/html module-html11033812
Ref: 6111033812
Ref: library/html html escape11034065
Ref: faf11034065
Ref: library/html html unescape11034550
Ref: 8fb11034550
Ref: html --- 超連結標記語言 HTML 支援-Footnote-111035223
Node: html parser --- 簡單的 HTML 和 XHTML 剖析器11035296
Ref: library/html parser doc11035521
Ref: 357911035521
Ref: library/html parser html-parser-simple-html-and-xhtml-parser11035521
Ref: 357a11035521
Ref: library/html parser module-html parser11035521
Ref: 6311035521
Ref: library/html parser html parser HTMLParser11035920
Ref: 81a11035920
Ref: html parser --- 簡單的 HTML 和 XHTML 剖析器-Footnote-111036999
Node: HTML 剖析器應用程式範例11037070
Ref: library/html parser example-html-parser-application11037215
Ref: 357b11037215
Node: HTMLParser 方法11038410
Ref: library/html parser htmlparser-methods11038574
Ref: 357c11038574
Ref: library/html parser html parser HTMLParser feed11038687
Ref: 357d11038687
Ref: library/html parser html parser HTMLParser close11038957
Ref: 357e11038957
Ref: library/html parser html parser HTMLParser reset11039285
Ref: 357f11039285
Ref: library/html parser html parser HTMLParser getpos11039415
Ref: 358011039415
Ref: library/html parser html parser HTMLParser get_starttag_text11039513
Ref: 358111039513
Ref: library/html parser html parser HTMLParser handle_starttag11039994
Ref: 358311039994
Ref: library/html parser html parser HTMLParser handle_endtag11040694
Ref: 358411040694
Ref: library/html parser html parser HTMLParser handle_startendtag11040873
Ref: 358211040873
Ref: library/html parser html parser HTMLParser handle_data11041261
Ref: 358511041261
Ref: library/html parser html parser HTMLParser handle_entityref11041448
Ref: 358611041448
Ref: library/html parser html parser HTMLParser handle_charref11041744
Ref: 358711041744
Ref: library/html parser html parser HTMLParser handle_comment11042159
Ref: 358811042159
Ref: library/html parser html parser HTMLParser handle_decl11042677
Ref: 358911042677
Ref: library/html parser html parser HTMLParser handle_pi11042956
Ref: 358a11042956
Ref: library/html parser html parser HTMLParser unknown_decl11043546
Ref: 358b11043546
Node: 範例<30>11043831
Ref: library/html parser examples11043954
Ref: 358c11043954
Ref: library/html parser htmlparser-examples11043954
Ref: 358d11043954
Node: html entities --- HTML 一般實體的定義11047354
Ref: library/html entities doc11047553
Ref: 358e11047553
Ref: library/html entities html-entities-definitions-of-html-general-entities11047553
Ref: 358f11047553
Ref: library/html entities module-html entities11047553
Ref: 6211047553
Ref: library/html entities html entities html511047924
Ref: 106c11047924
Ref: library/html entities html entities entitydefs11048351
Ref: 359211048351
Ref: library/html entities html entities name2codepoint11048474
Ref: 359011048474
Ref: library/html entities html entities codepoint2name11048584
Ref: 359111048584
Ref: html entities --- HTML 一般實體的定義-Footnote-111048743
Ref: html entities --- HTML 一般實體的定義-Footnote-211048816
Node: XML 處理模組11048925
Ref: library/xml doc11049120
Ref: 359311049120
Ref: library/xml module-xml11049120
Ref: 10711049120
Ref: library/xml xml11049120
Ref: 359411049120
Ref: library/xml xml-processing-modules11049120
Ref: 359511049120
Ref: XML 處理模組-Footnote-111050383
Node: XML 漏洞11050444
Ref: library/xml id111050533
Ref: 359811050533
Ref: library/xml xml-vulnerabilities11050533
Ref: 359611050533
Ref: XML 漏洞-Footnote-111056112
Ref: XML 漏洞-Footnote-211056175
Ref: XML 漏洞-Footnote-311056228
Ref: XML 漏洞-Footnote-411056281
Ref: XML 漏洞-Footnote-511056344
Ref: XML 漏洞-Footnote-611056391
Ref: XML 漏洞-Footnote-711056461
Node: defusedxml 套件11056506
Ref: library/xml defusedxml-package11056595
Ref: 359711056595
Ref: library/xml the-defusedxml-package11056595
Ref: 359911056595
Ref: defusedxml 套件-Footnote-111057037
Node: xml etree cElementTree --- ElementTree XML API11057082
Ref: library/xml etree elementtree doc11057270
Ref: 359a11057270
Ref: library/xml etree elementtree module-xml etree ElementTree11057270
Ref: 10c11057270
Ref: library/xml etree elementtree xml-etree-elementtree-the-elementtree-xml-api11057270
Ref: 359b11057270
Ref: xml etree cElementTree --- ElementTree XML API-Footnote-111058149
Node: 教學<2>11058231
Ref: library/xml etree elementtree tutorial11058344
Ref: 359c11058344
Node: XML tree and elements11058759
Ref: library/xml etree elementtree xml-tree-and-elements11058845
Ref: 359d11058845
Node: 剖析 XML11059423
Ref: library/xml etree elementtree elementtree-parsing-xml11059551
Ref: 359e11059551
Ref: library/xml etree elementtree parsing-xml11059551
Ref: 359f11059551
Node: Pull API for non-blocking parsing11062022
Ref: library/xml etree elementtree elementtree-pull-parsing11062157
Ref: f9511062157
Ref: library/xml etree elementtree pull-api-for-non-blocking-parsing11062157
Ref: 35a111062157
Node: Finding interesting elements11064262
Ref: library/xml etree elementtree finding-interesting-elements11064404
Ref: 35a411064404
Node: 改動 XML 檔案11065642
Ref: library/xml etree elementtree modifying-an-xml-file11065773
Ref: 35a911065773
Node: Building XML documents11068705
Ref: library/xml etree elementtree building-xml-documents11068835
Ref: 35ad11068835
Node: Parsing XML with Namespaces11069204
Ref: library/xml etree elementtree parsing-xml-with-namespaces11069308
Ref: 35af11069308
Ref: Parsing XML with Namespaces-Footnote-111071619
Ref: Parsing XML with Namespaces-Footnote-211071671
Node: XPath 支援11071723
Ref: library/xml etree elementtree elementtree-xpath11071857
Ref: b5411071857
Ref: library/xml etree elementtree xpath-support11071857
Ref: 35b011071857
Ref: XPath 支援-Footnote-111072213
Node: 範例<31>11072249
Ref: library/xml etree elementtree example11072339
Ref: 35b111072339
Node: Supported XPath syntax11073350
Ref: library/xml etree elementtree supported-xpath-syntax11073440
Ref: 35b211073440
Node: Reference<3>11078385
Ref: library/xml etree elementtree reference11078526
Ref: 35b311078526
Node: 函式<8>11078598
Ref: library/xml etree elementtree elementtree-functions11078656
Ref: 35b411078656
Ref: library/xml etree elementtree functions11078656
Ref: 35b511078656
Ref: library/xml etree elementtree xml etree ElementTree canonicalize11078689
Ref: 35b611078689
Ref: library/xml etree elementtree xml etree ElementTree Comment11081063
Ref: 35b711081063
Ref: library/xml etree elementtree xml etree ElementTree dump11081746
Ref: 35b811081746
Ref: library/xml etree elementtree xml etree ElementTree fromstring11082214
Ref: 35a011082214
Ref: library/xml etree elementtree xml etree ElementTree fromstringlist11082571
Ref: 116911082571
Ref: library/xml etree elementtree xml etree ElementTree indent11082979
Ref: 35ba11082979
Ref: library/xml etree elementtree xml etree ElementTree iselement11083505
Ref: 35bb11083505
Ref: library/xml etree elementtree xml etree ElementTree iterparse11083717
Ref: 25811083717
Ref: library/xml etree elementtree xml etree ElementTree parse11085846
Ref: 35bc11085846
Ref: library/xml etree elementtree xml etree ElementTree ProcessingInstruction11086188
Ref: 35bd11086188
Ref: library/xml etree elementtree xml etree ElementTree register_namespace11086914
Ref: 116a11086914
Ref: library/xml etree elementtree xml etree ElementTree SubElement11087343
Ref: 35ae11087343
Ref: library/xml etree elementtree xml etree ElementTree tostring11087911
Ref: f9611087911
Ref: library/xml etree elementtree xml etree ElementTree tostringlist11088994
Ref: f9711088994
Ref: library/xml etree elementtree xml etree ElementTree XML11090249
Ref: 35b911090249
Ref: library/xml etree elementtree xml etree ElementTree XMLID11090637
Ref: 35be11090637
Ref: 函式<8>-Footnote-111091110
Ref: 函式<8>-Footnote-211091151
Ref: 函式<8>-Footnote-311091452
Node: XInclude support11091753
Ref: library/xml etree elementtree elementtree-xinclude11091894
Ref: 35bf11091894
Ref: library/xml etree elementtree xinclude-support11091894
Ref: 35c011091894
Ref: XInclude support-Footnote-111092258
Node: 範例<32>11092298
Ref: library/xml etree elementtree id311092361
Ref: 35c111092361
Node: Reference<4>11094161
Ref: library/xml etree elementtree id411094281
Ref: 35c211094281
Node: 函式<9>11094503
Ref: library/xml etree elementtree elementinclude-functions11094584
Ref: 35c311094584
Ref: library/xml etree elementtree id511094584
Ref: 35c411094584
Ref: library/xml etree elementtree module-xml etree ElementInclude11094617
Ref: 10b11094617
Ref: library/xml etree elementtree xml etree ElementInclude default_loader11094617
Ref: 35c511094617
Ref: library/xml etree elementtree xml etree ElementInclude include11095202
Ref: 35c611095202
Node: Element 物件11096072
Ref: library/xml etree elementtree element-objects11096180
Ref: 35c711096180
Ref: library/xml etree elementtree elementtree-element-objects11096180
Ref: 35c811096180
Ref: library/xml etree elementtree xml etree ElementTree Element11096229
Ref: 2e211096229
Ref: library/xml etree elementtree xml etree ElementTree Element tag11096712
Ref: 12e211096712
Ref: library/xml etree elementtree xml etree ElementTree Element text11096854
Ref: 35a711096854
Ref: library/xml etree elementtree xml etree ElementTree Element tail11096876
Ref: 35c911096876
Ref: library/xml etree elementtree xml etree ElementTree Element attrib11097985
Ref: 35ca11097985
Ref: library/xml etree elementtree xml etree ElementTree Element clear11098524
Ref: 35cb11098524
Ref: library/xml etree elementtree xml etree ElementTree Element get11098717
Ref: 35a811098717
Ref: library/xml etree elementtree xml etree ElementTree Element items11098905
Ref: 35cc11098905
Ref: library/xml etree elementtree xml etree ElementTree Element keys11099074
Ref: 35cd11099074
Ref: library/xml etree elementtree xml etree ElementTree Element set11099216
Ref: 35aa11099216
Ref: library/xml etree elementtree xml etree ElementTree Element append11099387
Ref: 35ab11099387
Ref: library/xml etree elementtree xml etree ElementTree Element extend11099621
Ref: 116b11099621
Ref: library/xml etree elementtree xml etree ElementTree Element find11099852
Ref: 35a611099852
Ref: library/xml etree elementtree xml etree ElementTree Element findall11100274
Ref: 35a511100274
Ref: library/xml etree elementtree xml etree ElementTree Element findtext11100693
Ref: 35ce11100693
Ref: library/xml etree elementtree xml etree ElementTree Element insert11101297
Ref: 35cf11101297
Ref: library/xml etree elementtree xml etree ElementTree Element iter11101508
Ref: 12e311101508
Ref: library/xml etree elementtree xml etree ElementTree Element iterfind11102000
Ref: 116c11102000
Ref: library/xml etree elementtree xml etree ElementTree Element itertext11102334
Ref: 116d11102334
Ref: library/xml etree elementtree xml etree ElementTree Element makeelement11102559
Ref: 35d011102559
Ref: library/xml etree elementtree xml etree ElementTree Element remove11102782
Ref: 35ac11102782
Ref: Element 物件-Footnote-111105532
Node: ElementTree 物件11105575
Ref: library/xml etree elementtree elementtree-elementtree-objects11105686
Ref: 35d111105686
Ref: library/xml etree elementtree elementtree-objects11105686
Ref: 35d211105686
Ref: library/xml etree elementtree xml etree ElementTree ElementTree11105743
Ref: 8f211105743
Ref: library/xml etree elementtree xml etree ElementTree ElementTree _setroot11106096
Ref: 35d311106096
Ref: library/xml etree elementtree xml etree ElementTree ElementTree find11106345
Ref: 35d411106345
Ref: library/xml etree elementtree xml etree ElementTree ElementTree findall11106484
Ref: 35d511106484
Ref: library/xml etree elementtree xml etree ElementTree ElementTree findtext11106629
Ref: 35d611106629
Ref: library/xml etree elementtree xml etree ElementTree ElementTree getroot11106790
Ref: 35d711106790
Ref: library/xml etree elementtree xml etree ElementTree ElementTree iter11106870
Ref: 35d811106870
Ref: library/xml etree elementtree xml etree ElementTree ElementTree iterfind11107140
Ref: 35d911107140
Ref: library/xml etree elementtree xml etree ElementTree ElementTree parse11107320
Ref: 35da11107320
Ref: library/xml etree elementtree xml etree ElementTree ElementTree write11107666
Ref: f9811107666
Ref: ElementTree 物件-Footnote-111110436
Node: QName 物件11110737
Ref: library/xml etree elementtree elementtree-qname-objects11110852
Ref: 35db11110852
Ref: library/xml etree elementtree qname-objects11110852
Ref: 35dc11110852
Ref: library/xml etree elementtree xml etree ElementTree QName11110897
Ref: 35dd11110897
Node: TreeBuilder 物件11111411
Ref: library/xml etree elementtree elementtree-treebuilder-objects11111524
Ref: 35de11111524
Ref: library/xml etree elementtree treebuilder-objects11111524
Ref: 35df11111524
Ref: library/xml etree elementtree xml etree ElementTree TreeBuilder11111581
Ref: 9f811111581
Ref: library/xml etree elementtree xml etree ElementTree TreeBuilder close11112700
Ref: 35e011112700
Ref: library/xml etree elementtree xml etree ElementTree TreeBuilder data11112862
Ref: 35e111112862
Ref: library/xml etree elementtree xml etree ElementTree TreeBuilder end11113026
Ref: 116e11113026
Ref: library/xml etree elementtree xml etree ElementTree TreeBuilder start11113159
Ref: 188711113159
Ref: library/xml etree elementtree xml etree ElementTree TreeBuilder comment11113361
Ref: 35e211113361
Ref: library/xml etree elementtree xml etree ElementTree TreeBuilder pi11113559
Ref: 35e311113559
Ref: library/xml etree elementtree xml etree ElementTree TreeBuilder doctype11113894
Ref: a3a11113894
Ref: library/xml etree elementtree xml etree ElementTree TreeBuilder start_ns11114220
Ref: 35e411114220
Ref: library/xml etree elementtree xml etree ElementTree TreeBuilder end_ns11114616
Ref: 35e511114616
Ref: library/xml etree elementtree xml etree ElementTree C14NWriterTarget11114865
Ref: 35e611114865
Ref: TreeBuilder 物件-Footnote-111115416
Node: XMLParser 物件11115457
Ref: library/xml etree elementtree elementtree-xmlparser-objects11115578
Ref: 35e711115578
Ref: library/xml etree elementtree xmlparser-objects11115578
Ref: 35e811115578
Ref: library/xml etree elementtree xml etree ElementTree XMLParser11115631
Ref: 9f711115631
Ref: library/xml etree elementtree xml etree ElementTree XMLParser close11116343
Ref: 35ea11116343
Ref: library/xml etree elementtree xml etree ElementTree XMLParser feed11116599
Ref: 35e911116599
Ref: library/xml etree elementtree xml etree ElementTree XMLParser flush11116691
Ref: 25411116691
Ref: XMLParser 物件-Footnote-111119329
Node: XMLPullParser 物件11119630
Ref: library/xml etree elementtree elementtree-xmlpullparser-objects11119743
Ref: 35eb11119743
Ref: library/xml etree elementtree xmlpullparser-objects11119743
Ref: 35ec11119743
Ref: library/xml etree elementtree xml etree ElementTree XMLPullParser11119804
Ref: f9411119804
Ref: library/xml etree elementtree xml etree ElementTree XMLPullParser feed11120493
Ref: 35a211120493
Ref: library/xml etree elementtree xml etree ElementTree XMLPullParser flush11120575
Ref: 25511120575
Ref: library/xml etree elementtree xml etree ElementTree XMLPullParser close11121434
Ref: 35ed11121434
Ref: library/xml etree elementtree xml etree ElementTree XMLPullParser read_events11121745
Ref: 35a311121745
Node: 例外<14>11123469
Ref: library/xml etree elementtree exceptions11123557
Ref: 35ee11123557
Ref: library/xml etree elementtree xml etree ElementTree ParseError11123590
Ref: 121011123590
Ref: library/xml etree elementtree xml etree ElementTree ParseError code11123919
Ref: 35ef11123919
Ref: library/xml etree elementtree xml etree ElementTree ParseError position11124121
Ref: 35f011124121
Node: xml dom --- Document 物件模型 API11124256
Ref: library/xml dom doc11124468
Ref: 35f111124468
Ref: library/xml dom module-xml dom11124468
Ref: 10811124468
Ref: library/xml dom xml-dom-the-document-object-model-api11124468
Ref: 35f211124468
Ref: xml dom --- Document 物件模型 API-Footnote-111127912
Ref: xml dom --- Document 物件模型 API-Footnote-211127989
Ref: xml dom --- Document 物件模型 API-Footnote-311128055
Ref: xml dom --- Document 物件模型 API-Footnote-411128102
Node: 模組內容<6>11128148
Ref: library/xml dom module-contents11128264
Ref: 35f511128264
Ref: library/xml dom xml dom registerDOMImplementation11128364
Ref: 35f611128364
Ref: library/xml dom xml dom getDOMImplementation11128810
Ref: 35f311128810
Ref: library/xml dom xml dom EMPTY_NAMESPACE11129717
Ref: 35f711129717
Ref: library/xml dom xml dom XML_NAMESPACE11129992
Ref: 35f811129992
Ref: library/xml dom xml dom XMLNS_NAMESPACE11130151
Ref: 35f911130151
Ref: library/xml dom xml dom XHTML_NAMESPACE11130339
Ref: 35fa11130339
Ref: 模組內容<6>-Footnote-111131076
Ref: 模組內容<6>-Footnote-211131121
Ref: 模組內容<6>-Footnote-311131178
Node: Objects in the DOM11131216
Ref: library/xml dom dom-objects11131352
Ref: 35fb11131352
Ref: library/xml dom objects-in-the-dom11131352
Ref: 35fc11131352
Node: DOMImplementation 物件11135861
Ref: library/xml dom dom-implementation-objects11135961
Ref: 35fd11135961
Ref: library/xml dom domimplementation-objects11135961
Ref: 360711135961
Ref: library/xml dom xml dom DOMImplementation hasFeature11136313
Ref: 360811136313
Ref: library/xml dom xml dom DOMImplementation createDocument11136492
Ref: 360911136492
Ref: library/xml dom xml dom DOMImplementation createDocumentType11137012
Ref: 360a11137012
Node: Node Objects11137320
Ref: library/xml dom dom-node-objects11137444
Ref: 35fe11137444
Ref: library/xml dom node-objects11137444
Ref: 360b11137444
Ref: library/xml dom xml dom Node nodeType11137561
Ref: 360c11137561
Ref: library/xml dom xml dom Node parentNode11137981
Ref: 360d11137981
Ref: library/xml dom xml dom Node attributes11138387
Ref: 360e11138387
Ref: library/xml dom xml dom Node previousSibling11138597
Ref: 360f11138597
Ref: library/xml dom xml dom Node nextSibling11139078
Ref: 361011139078
Ref: library/xml dom xml dom Node childNodes11139341
Ref: 361111139341
Ref: library/xml dom xml dom Node firstChild11139457
Ref: 361211139457
Ref: library/xml dom xml dom Node lastChild11139591
Ref: 361311139591
Ref: library/xml dom xml dom Node localName11139723
Ref: 361411139723
Ref: library/xml dom xml dom Node prefix11139884
Ref: 361511139884
Ref: library/xml dom xml dom Node namespaceURI11140049
Ref: 361611140049
Ref: library/xml dom xml dom Node nodeName11140209
Ref: 361711140209
Ref: library/xml dom xml dom Node nodeValue11140643
Ref: 361811140643
Ref: library/xml dom xml dom Node hasAttributes11140874
Ref: 361911140874
Ref: library/xml dom xml dom Node hasChildNodes11140965
Ref: 361a11140965
Ref: library/xml dom xml dom Node isSameNode11141057
Ref: 361b11141057
Ref: library/xml dom xml dom Node appendChild11141684
Ref: 361c11141684
Ref: library/xml dom xml dom Node insertBefore11141892
Ref: 361d11141892
Ref: library/xml dom xml dom Node removeChild11142231
Ref: 361e11142231
Ref: library/xml dom xml dom Node replaceChild11142519
Ref: 361f11142519
Ref: library/xml dom xml dom Node normalize11142733
Ref: 362011142733
Ref: library/xml dom xml dom Node cloneNode11142950
Ref: 362111142950
Node: NodeList 物件11143094
Ref: library/xml dom dom-nodelist-objects11143213
Ref: 35ff11143213
Ref: library/xml dom nodelist-objects11143213
Ref: 362211143213
Ref: library/xml dom xml dom NodeList item11143690
Ref: 362311143690
Ref: library/xml dom xml dom NodeList length11143917
Ref: 362411143917
Node: DocumentType 物件11144584
Ref: library/xml dom documenttype-objects11144707
Ref: 362511144707
Ref: library/xml dom dom-documenttype-objects11144707
Ref: 360011144707
Ref: library/xml dom xml dom DocumentType publicId11145332
Ref: 362611145332
Ref: library/xml dom xml dom DocumentType systemId11145495
Ref: 362711145495
Ref: library/xml dom xml dom DocumentType internalSubset11145668
Ref: 362811145668
Ref: library/xml dom xml dom DocumentType name11145918
Ref: 362911145918
Ref: library/xml dom xml dom DocumentType entities11146044
Ref: 362a11146044
Ref: library/xml dom xml dom DocumentType notations11146424
Ref: 362b11146424
Node: Document Objects11146800
Ref: library/xml dom document-objects11146923
Ref: 362c11146923
Ref: library/xml dom dom-document-objects11146923
Ref: 360111146923
Ref: library/xml dom xml dom Document documentElement11147170
Ref: 362d11147170
Ref: library/xml dom xml dom Document createElement11147261
Ref: 362e11147261
Ref: library/xml dom xml dom Document createElementNS11147550
Ref: 362f11147550
Ref: library/xml dom xml dom Document createTextNode11147901
Ref: 363011147901
Ref: library/xml dom xml dom Document createComment11148120
Ref: 363111148120
Ref: library/xml dom xml dom Document createProcessingInstruction11148341
Ref: 363211148341
Ref: library/xml dom xml dom Document createAttribute11148613
Ref: 363311148613
Ref: library/xml dom xml dom Document createAttributeNS11148920
Ref: 363411148920
Ref: library/xml dom xml dom Document getElementsByTagName11149308
Ref: 363511149308
Ref: library/xml dom xml dom Document getElementsByTagNameNS11149482
Ref: 363611149482
Node: Element Objects11149751
Ref: library/xml dom dom-element-objects11149867
Ref: 360211149867
Ref: library/xml dom element-objects11149867
Ref: 363711149867
Ref: library/xml dom xml dom Element tagName11150008
Ref: 363811150008
Ref: library/xml dom xml dom Element getElementsByTagName11150152
Ref: 363911150152
Ref: library/xml dom xml dom Element getElementsByTagNameNS11150265
Ref: 363a11150265
Ref: library/xml dom xml dom Element hasAttribute11150396
Ref: 363b11150396
Ref: library/xml dom xml dom Element hasAttributeNS11150510
Ref: 363c11150510
Ref: library/xml dom xml dom Element getAttribute11150674
Ref: 363d11150674
Ref: library/xml dom xml dom Element getAttributeNode11150887
Ref: 363e11150887
Ref: library/xml dom xml dom Element getAttributeNS11151008
Ref: 363f11151008
Ref: library/xml dom xml dom Element getAttributeNodeNS11151266
Ref: 364011151266
Ref: library/xml dom xml dom Element removeAttribute11151420
Ref: 364111151420
Ref: library/xml dom xml dom Element removeAttributeNode11151578
Ref: 364311151578
Ref: library/xml dom xml dom Element removeAttributeNS11151770
Ref: 364411151770
Ref: library/xml dom xml dom Element setAttribute11151979
Ref: 364511151979
Ref: library/xml dom xml dom Element setAttributeNode11152071
Ref: 364611152071
Ref: library/xml dom xml dom Element setAttributeNodeNS11152415
Ref: 364811152415
Ref: library/xml dom xml dom Element setAttributeNS11152788
Ref: 364911152788
Node: Attr Objects11153024
Ref: library/xml dom attr-objects11153143
Ref: 364a11153143
Ref: library/xml dom dom-attr-objects11153143
Ref: 360311153143
Ref: library/xml dom xml dom Attr name11153258
Ref: 364b11153258
Ref: library/xml dom xml dom Attr localName11153367
Ref: 364c11153367
Ref: library/xml dom xml dom Attr prefix11153518
Ref: 364d11153518
Ref: library/xml dom xml dom Attr value11153635
Ref: 364e11153635
Node: NamedNodeMap 物件11153757
Ref: library/xml dom dom-attributelist-objects11153876
Ref: 364f11153876
Ref: library/xml dom namednodemap-objects11153876
Ref: 365011153876
Ref: library/xml dom xml dom NamedNodeMap length11153991
Ref: 365111153991
Ref: library/xml dom xml dom NamedNodeMap item11154064
Ref: 365211154064
Node: Comment Objects11154545
Ref: library/xml dom comment-objects11154681
Ref: 365311154681
Ref: library/xml dom dom-comment-objects11154681
Ref: 360411154681
Ref: library/xml dom xml dom Comment data11154853
Ref: 365411154853
Node: Text and CDATASection Objects11155068
Ref: library/xml dom dom-text-objects11155213
Ref: 360511155213
Ref: library/xml dom text-and-cdatasection-objects11155213
Ref: 365511155213
Ref: library/xml dom xml dom Text data11155707
Ref: 365611155707
Node: ProcessingInstruction 物件11156199
Ref: library/xml dom dom-pi-objects11156339
Ref: 360611156339
Ref: library/xml dom processinginstruction-objects11156339
Ref: 365711156339
Ref: library/xml dom xml dom ProcessingInstruction target11156547
Ref: 365811156547
Ref: library/xml dom xml dom ProcessingInstruction data11156712
Ref: 365911156712
Node: 例外<15>11156847
Ref: library/xml dom dom-exceptions11156949
Ref: 365a11156949
Ref: library/xml dom exceptions11156949
Ref: 365b11156949
Ref: library/xml dom xml dom DOMException11157618
Ref: 365c11157618
Ref: library/xml dom xml dom DomstringSizeErr11157777
Ref: 365d11157777
Ref: library/xml dom xml dom HierarchyRequestErr11158029
Ref: 365e11158029
Ref: library/xml dom xml dom IndexSizeErr11158165
Ref: 365f11158165
Ref: library/xml dom xml dom InuseAttributeErr11158304
Ref: 364711158304
Ref: library/xml dom xml dom InvalidAccessErr11158465
Ref: 366011158465
Ref: library/xml dom xml dom InvalidCharacterErr11158595
Ref: 366111158595
Ref: library/xml dom xml dom InvalidModificationErr11158950
Ref: 366211158950
Ref: library/xml dom xml dom InvalidStateErr11159061
Ref: 366311159061
Ref: library/xml dom xml dom NamespaceErr11159201
Ref: 366411159201
Ref: library/xml dom xml dom NotFoundErr11159407
Ref: 364211159407
Ref: library/xml dom xml dom NotSupportedErr11159635
Ref: 366511159635
Ref: library/xml dom xml dom NoDataAllowedErr11159774
Ref: 366611159774
Ref: library/xml dom xml dom NoModificationAllowedErr11159899
Ref: 366711159899
Ref: library/xml dom xml dom SyntaxErr11160062
Ref: 366811160062
Ref: library/xml dom xml dom WrongDocumentErr11160154
Ref: 366911160154
Ref: 例外<15>-Footnote-111163191
Node: Conformance11163236
Ref: library/xml dom conformance11163348
Ref: 366a11163348
Ref: library/xml dom dom-conformance11163348
Ref: 35f411163348
Node: Type Mapping11163605
Ref: library/xml dom dom-type-mapping11163690
Ref: 366b11163690
Ref: library/xml dom type-mapping11163690
Ref: 366c11163690
Node: Accessor Methods11164517
Ref: library/xml dom accessor-methods11164602
Ref: 366d11164602
Ref: library/xml dom dom-accessor-methods11164602
Ref: 366e11164602
Node: xml dom minidom --- 最小的 DOM 實作11166458
Ref: library/xml dom minidom doc11166670
Ref: 366f11166670
Ref: library/xml dom minidom module-xml dom minidom11166670
Ref: 10911166670
Ref: library/xml dom minidom xml-dom-minidom-minimal-dom-implementation11166670
Ref: 367011166670
Ref: library/xml dom minidom xml dom minidom parse11167980
Ref: 367111167980
Ref: library/xml dom minidom xml dom minidom parseString11168547
Ref: 367211168547
Ref: xml dom minidom --- 最小的 DOM 實作-Footnote-111171104
Ref: xml dom minidom --- 最小的 DOM 實作-Footnote-211171180
Node: DOM 物件11171227
Ref: library/xml dom minidom dom-objects11171333
Ref: 367311171333
Ref: library/xml dom minidom minidom-objects11171333
Ref: 367411171333
Ref: library/xml dom minidom xml dom minidom Node unlink11171564
Ref: 367511171564
Ref: library/xml dom minidom xml dom minidom Node writexml11172340
Ref: 367611172340
Ref: library/xml dom minidom xml dom minidom Node toxml11173568
Ref: 143611173568
Ref: library/xml dom minidom xml dom minidom Node toprettyxml11174365
Ref: 143711174365
Ref: DOM 物件-Footnote-111175094
Node: DOM 範例11175487
Ref: library/xml dom minidom dom-example11175630
Ref: 367711175630
Ref: library/xml dom minidom id211175630
Ref: 367811175630
Node: minidom and the DOM standard11177658
Ref: library/xml dom minidom minidom-and-dom11177782
Ref: 367911177782
Ref: library/xml dom minidom minidom-and-the-dom-standard11177782
Ref: 367a11177782
Node: xml dom pulldom --- 支援建置部分 DOM 樹11180430
Ref: library/xml dom pulldom doc11180637
Ref: 367b11180637
Ref: library/xml dom pulldom module-xml dom pulldom11180637
Ref: 10a11180637
Ref: library/xml dom pulldom xml-dom-pulldom-support-for-building-partial-dom-trees11180637
Ref: 367c11180637
Ref: library/xml dom pulldom xml dom pulldom PullDom11183328
Ref: 367e11183328
Ref: library/xml dom pulldom xml dom pulldom SAX2DOM11183450
Ref: 368011183450
Ref: library/xml dom pulldom xml dom pulldom parse11183572
Ref: 368111183572
Ref: library/xml dom pulldom xml dom pulldom parseString11184162
Ref: 368311184162
Ref: library/xml dom pulldom xml dom pulldom default_bufsize11184312
Ref: 368411184312
Ref: xml dom pulldom --- 支援建置部分 DOM 樹-Footnote-111184626
Node: DOMEventStream 物件11184702
Ref: library/xml dom pulldom domeventstream-objects11184806
Ref: 368511184806
Ref: library/xml dom pulldom id111184806
Ref: 368611184806
Ref: library/xml dom pulldom xml dom pulldom DOMEventStream11184867
Ref: 6d911184867
Ref: library/xml dom pulldom xml dom pulldom DOMEventStream getEvent11185034
Ref: 368711185034
Ref: library/xml dom pulldom xml dom pulldom DOMEventStream expandNode11185526
Ref: 367d11185526
Ref: library/xml dom pulldom xml dom pulldom DOMEventStream reset11186240
Ref: 368811186240
Node: xml sax --- SAX2 剖析器支援11186267
Ref: library/xml sax doc11186485
Ref: 368911186485
Ref: library/xml sax module-xml sax11186485
Ref: 11011186485
Ref: library/xml sax xml-sax-support-for-sax2-parsers11186485
Ref: 368a11186485
Ref: library/xml sax xml sax make_parser11187550
Ref: 194111187550
Ref: library/xml sax xml sax parse11188044
Ref: 190a11188044
Ref: library/xml sax xml sax parseString11188637
Ref: e3e11188637
Ref: library/xml sax xml sax SAXException11190552
Ref: 369011190552
Ref: library/xml sax xml sax SAXParseException11191420
Ref: 368e11191420
Ref: library/xml sax xml sax SAXNotRecognizedException11191828
Ref: 369111191828
Ref: library/xml sax xml sax SAXNotSupportedException11192127
Ref: 369211192127
Ref: xml sax --- SAX2 剖析器支援-Footnote-111193136
Ref: xml sax --- SAX2 剖析器支援-Footnote-211193213
Node: SAXException 物件11193248
Ref: library/xml sax sax-exception-objects11193336
Ref: 369311193336
Ref: library/xml sax saxexception-objects11193336
Ref: 369411193336
Ref: library/xml sax xml sax SAXException getMessage11193472
Ref: 369511193472
Ref: library/xml sax xml sax SAXException getException11193582
Ref: 369611193582
Node: xml sax handler --- SAX 處理函式的基本類別11193686
Ref: library/xml sax handler doc11193895
Ref: 369711193895
Ref: library/xml sax handler module-xml sax handler11193895
Ref: 11111193895
Ref: library/xml sax handler xml-sax-handler-base-classes-for-sax-handlers11193895
Ref: 369811193895
Ref: library/xml sax handler xml sax handler ContentHandler11194592
Ref: 367f11194592
Ref: library/xml sax handler xml sax handler DTDHandler11194833
Ref: 369911194833
Ref: library/xml sax handler xml sax handler EntityResolver11195019
Ref: 369a11195019
Ref: library/xml sax handler xml sax handler ErrorHandler11195302
Ref: 368d11195302
Ref: library/xml sax handler xml sax handler LexicalHandler11195577
Ref: 80011195577
Ref: library/xml sax handler xml sax handler feature_namespaces11195869
Ref: 369b11195869
Ref: library/xml sax handler xml sax handler feature_namespace_prefixes11196195
Ref: 369c11196195
Ref: library/xml sax handler xml sax handler feature_string_interning11196626
Ref: 369d11196626
Ref: library/xml sax handler xml sax handler feature_validation11197043
Ref: 369e11197043
Ref: library/xml sax handler xml sax handler feature_external_ges11197384
Ref: 368c11197384
Ref: library/xml sax handler xml sax handler feature_external_pes11197699
Ref: 369f11197699
Ref: library/xml sax handler xml sax handler all_features11198082
Ref: 36a011198082
Ref: library/xml sax handler xml sax handler property_lexical_handler11198152
Ref: 36a111198152
Ref: library/xml sax handler xml sax handler property_declaration_handler11198474
Ref: 36a211198474
Ref: library/xml sax handler xml sax handler property_dom_node11198834
Ref: 36a311198834
Ref: library/xml sax handler xml sax handler property_xml_string11199226
Ref: 36a411199226
Ref: library/xml sax handler xml sax handler all_properties11199496
Ref: 36a511199496
Ref: xml sax handler --- SAX 處理函式的基本類別-Footnote-111199750
Node: ContentHandler 物件11199826
Ref: library/xml sax handler content-handler-objects11199961
Ref: 36a611199961
Ref: library/xml sax handler contenthandler-objects11199961
Ref: 36a711199961
Ref: library/xml sax handler xml sax handler ContentHandler setDocumentLocator11200211
Ref: 36a811200211
Ref: library/xml sax handler xml sax handler ContentHandler startDocument11201284
Ref: 36a911201284
Ref: library/xml sax handler xml sax handler ContentHandler endDocument11201562
Ref: 36aa11201562
Ref: library/xml sax handler xml sax handler ContentHandler startPrefixMapping11201930
Ref: 36ab11201930
Ref: library/xml sax handler xml sax handler ContentHandler endPrefixMapping11203132
Ref: 36ac11203132
Ref: library/xml sax handler xml sax handler ContentHandler startElement11203475
Ref: 14b111203475
Ref: library/xml sax handler xml sax handler ContentHandler endElement11204116
Ref: 14b211204116
Ref: library/xml sax handler xml sax handler ContentHandler startElementNS11204344
Ref: 36ae11204344
Ref: library/xml sax handler xml sax handler ContentHandler endElementNS11205332
Ref: 36b011205332
Ref: library/xml sax handler xml sax handler ContentHandler characters11205605
Ref: 14b311205605
Ref: library/xml sax handler xml sax handler ContentHandler ignorableWhitespace11206634
Ref: 36b111206634
Ref: library/xml sax handler xml sax handler ContentHandler processingInstruction11207301
Ref: 36b211207301
Ref: library/xml sax handler xml sax handler ContentHandler skippedEntity11207761
Ref: 36b311207761
Node: DTDHandler 物件11208261
Ref: library/xml sax handler dtd-handler-objects11208426
Ref: 36b411208426
Ref: library/xml sax handler dtdhandler-objects11208426
Ref: 36b511208426
Ref: library/xml sax handler xml sax handler DTDHandler notationDecl11208547
Ref: 36b611208547
Ref: library/xml sax handler xml sax handler DTDHandler unparsedEntityDecl11208654
Ref: 36b711208654
Node: EntityResolver 物件11208792
Ref: library/xml sax handler entity-resolver-objects11208955
Ref: 36b811208955
Ref: library/xml sax handler entityresolver-objects11208955
Ref: 36b911208955
Ref: library/xml sax handler xml sax handler EntityResolver resolveEntity11209018
Ref: 36ba11209018
Node: ErrorHandler 物件11209286
Ref: library/xml sax handler errorhandler-objects11209453
Ref: 36bb11209453
Ref: library/xml sax handler sax-error-handler11209453
Ref: 36bc11209453
Ref: library/xml sax handler xml sax handler ErrorHandler error11210104
Ref: 36bd11210104
Ref: library/xml sax handler xml sax handler ErrorHandler fatalError11210473
Ref: 36be11210473
Ref: library/xml sax handler xml sax handler ErrorHandler warning11210659
Ref: 36bf11210659
Node: LexicalHandler 物件11211004
Ref: library/xml sax handler lexical-handler-objects11211141
Ref: 36c011211141
Ref: library/xml sax handler lexicalhandler-objects11211141
Ref: 36c111211141
Ref: library/xml sax handler xml sax handler LexicalHandler comment11211742
Ref: 36c211211742
Ref: library/xml sax handler xml sax handler LexicalHandler startDTD11211896
Ref: 36c311211896
Ref: library/xml sax handler xml sax handler LexicalHandler endDTD11212054
Ref: 36c411212054
Ref: library/xml sax handler xml sax handler LexicalHandler startCDATA11212134
Ref: 36c511212134
Ref: library/xml sax handler xml sax handler LexicalHandler endCDATA11212328
Ref: 36c611212328
Node: xml sax saxutils --- SAX 工具程式11212417
Ref: library/xml sax utils doc11212638
Ref: 36c711212638
Ref: library/xml sax utils module-xml sax saxutils11212638
Ref: 11211212638
Ref: library/xml sax utils xml-sax-saxutils-sax-utilities11212638
Ref: 36c811212638
Ref: library/xml sax utils xml sax saxutils escape11213026
Ref: 36c911213026
Ref: library/xml sax utils xml sax saxutils unescape11213675
Ref: 36ca11213675
Ref: library/xml sax utils xml sax saxutils quoteattr11214140
Ref: 36cb11214140
Ref: library/xml sax utils xml sax saxutils XMLGenerator11215047
Ref: 36cc11215047
Ref: library/xml sax utils xml sax saxutils XMLFilterBase11215905
Ref: 36cd11215905
Ref: library/xml sax utils xml sax saxutils prepare_input_source11216326
Ref: 36ce11216326
Ref: xml sax saxutils --- SAX 工具程式-Footnote-111216820
Node: xml sax xmlreader --- XML 剖析器的介面11216897
Ref: library/xml sax reader doc11217125
Ref: 36d011217125
Ref: library/xml sax reader module-xml sax xmlreader11217125
Ref: 11311217125
Ref: library/xml sax reader xml-sax-xmlreader-interface-for-xml-parsers11217125
Ref: 36d111217125
Ref: library/xml sax reader xml sax xmlreader XMLReader11217612
Ref: 368211217612
Ref: library/xml sax reader xml sax xmlreader IncrementalParser11217709
Ref: 36d211217709
Ref: library/xml sax reader xml sax xmlreader Locator11218835
Ref: 368f11218835
Ref: library/xml sax reader xml sax xmlreader InputSource11219169
Ref: e3d11219169
Ref: library/xml sax reader xml sax xmlreader AttributesImpl11219938
Ref: 36d311219938
Ref: library/xml sax reader xml sax xmlreader AttributesNSImpl11220538
Ref: 36d411220538
Ref: xml sax xmlreader --- XML 剖析器的介面-Footnote-111221293
Node: XMLReader 物件11221371
Ref: library/xml sax reader id111221501
Ref: 36d511221501
Ref: library/xml sax reader xmlreader-objects11221501
Ref: 36d611221501
Ref: library/xml sax reader xml sax xmlreader XMLReader parse11221624
Ref: 36cf11221624
Ref: library/xml sax reader xml sax xmlreader XMLReader getContentHandler11222206
Ref: 36d711222206
Ref: library/xml sax reader xml sax xmlreader XMLReader setContentHandler11222303
Ref: 36d811222303
Ref: library/xml sax reader xml sax xmlreader XMLReader getDTDHandler11222486
Ref: 36d911222486
Ref: library/xml sax reader xml sax xmlreader XMLReader setDTDHandler11222575
Ref: 36da11222575
Ref: library/xml sax reader xml sax xmlreader XMLReader getEntityResolver11222742
Ref: 36db11222742
Ref: library/xml sax reader xml sax xmlreader XMLReader setEntityResolver11222839
Ref: 36dc11222839
Ref: library/xml sax reader xml sax xmlreader XMLReader getErrorHandler11223131
Ref: 36dd11223131
Ref: library/xml sax reader xml sax xmlreader XMLReader setErrorHandler11223224
Ref: 36de11223224
Ref: library/xml sax reader xml sax xmlreader XMLReader setLocale11223428
Ref: 36df11223428
Ref: library/xml sax reader xml sax xmlreader XMLReader getFeature11223794
Ref: 36e011223794
Ref: library/xml sax reader xml sax xmlreader XMLReader setFeature11224076
Ref: 368b11224076
Ref: library/xml sax reader xml sax xmlreader XMLReader getProperty11224365
Ref: 36e111224365
Ref: library/xml sax reader xml sax xmlreader XMLReader setProperty11224656
Ref: 36e211224656
Node: IncrementalParser 物件11224950
Ref: library/xml sax reader incremental-parser-objects11225104
Ref: 36e311225104
Ref: library/xml sax reader incrementalparser-objects11225104
Ref: 36e411225104
Ref: library/xml sax reader xml sax xmlreader IncrementalParser feed11225258
Ref: 36e511225258
Ref: library/xml sax reader xml sax xmlreader IncrementalParser close11225334
Ref: 36e611225334
Ref: library/xml sax reader xml sax xmlreader IncrementalParser reset11225573
Ref: 36e711225573
Node: Locator Objects11225835
Ref: library/xml sax reader id211225991
Ref: 36e811225991
Ref: library/xml sax reader locator-objects11225991
Ref: 36e911225991
Ref: library/xml sax reader xml sax xmlreader Locator getColumnNumber11226102
Ref: 36ea11226102
Ref: library/xml sax reader xml sax xmlreader Locator getLineNumber11226205
Ref: 36eb11226205
Ref: library/xml sax reader xml sax xmlreader Locator getPublicId11226304
Ref: 36ec11226304
Ref: library/xml sax reader xml sax xmlreader Locator getSystemId11226398
Ref: 36ed11226398
Node: InputSource 物件11226492
Ref: library/xml sax reader input-source-objects11226648
Ref: 36ee11226648
Ref: library/xml sax reader inputsource-objects11226648
Ref: 36ef11226648
Ref: library/xml sax reader xml sax xmlreader InputSource setPublicId11226705
Ref: 36f011226705
Ref: library/xml sax reader xml sax xmlreader InputSource getPublicId11226812
Ref: 36f111226812
Ref: library/xml sax reader xml sax xmlreader InputSource setSystemId11226920
Ref: 36f211226920
Ref: library/xml sax reader xml sax xmlreader InputSource getSystemId11227027
Ref: 36f311227027
Ref: library/xml sax reader xml sax xmlreader InputSource setEncoding11227135
Ref: 36f411227135
Ref: library/xml sax reader xml sax xmlreader InputSource getEncoding11227521
Ref: 36f511227521
Ref: library/xml sax reader xml sax xmlreader InputSource setByteStream11227615
Ref: 36f611227615
Ref: library/xml sax reader xml sax xmlreader InputSource getByteStream11228048
Ref: 36f711228048
Ref: library/xml sax reader xml sax xmlreader InputSource setCharacterStream11228256
Ref: 36f811228256
Ref: library/xml sax reader xml sax xmlreader InputSource getCharacterStream11228570
Ref: 36f911228570
Node: The Attributes Interface11228671
Ref: library/xml sax reader attributes-objects11228838
Ref: 36ad11228838
Ref: library/xml sax reader the-attributes-interface11228838
Ref: 36fa11228838
Ref: library/xml sax reader xml sax xmlreader Attributes getLength11229168
Ref: 36fb11229168
Ref: library/xml sax reader xml sax xmlreader Attributes getNames11229244
Ref: 36fc11229244
Ref: library/xml sax reader xml sax xmlreader Attributes getType11229322
Ref: 36fd11229322
Ref: library/xml sax reader xml sax xmlreader Attributes getValue11229447
Ref: 36fe11229447
Node: The AttributesNS Interface11229531
Ref: library/xml sax reader attributes-ns-objects11229671
Ref: 36af11229671
Ref: library/xml sax reader the-attributesns-interface11229671
Ref: 36ff11229671
Ref: library/xml sax reader xml sax xmlreader AttributesNS getValueByQName11230004
Ref: 370011230004
Ref: library/xml sax reader xml sax xmlreader AttributesNS getNameByQName11230098
Ref: 370111230098
Ref: library/xml sax reader xml sax xmlreader AttributesNS getQNameByName11230221
Ref: 370211230221
Ref: library/xml sax reader xml sax xmlreader AttributesNS getQNames11230342
Ref: 370311230342
Node: xml parsers expat --- 使用 Expat 進行快速 XML 剖析11230433
Ref: library/pyexpat doc11230615
Ref: 370411230615
Ref: library/pyexpat module-xml parsers expat11230615
Ref: 10d11230615
Ref: library/pyexpat xml-parsers-expat-fast-xml-parsing-using-expat11230615
Ref: 370511230615
Ref: library/pyexpat xml parsers expat ExpatError11231667
Ref: 121111231667
Ref: library/pyexpat xml parsers expat error11231870
Ref: 370711231870
Ref: library/pyexpat xml parsers expat XMLParserType11231950
Ref: 370811231950
Ref: library/pyexpat xml parsers expat ErrorString11232149
Ref: 370a11232149
Ref: library/pyexpat xml parsers expat ParserCreate11232270
Ref: 370911232270
Ref: xml parsers expat --- 使用 Expat 進行快速 XML 剖析-Footnote-111234691
Ref: xml parsers expat --- 使用 Expat 進行快速 XML 剖析-Footnote-211234992
Node: XMLParser 物件<2>11235025
Ref: library/pyexpat id211235165
Ref: 370b11235165
Ref: library/pyexpat xmlparser-objects11235165
Ref: 370c11235165
Ref: library/pyexpat xml parsers expat xmlparser Parse11235271
Ref: 370d11235271
Ref: library/pyexpat xml parsers expat xmlparser ParseFile11235649
Ref: 370e11235649
Ref: library/pyexpat xml parsers expat xmlparser SetBase11235867
Ref: 370f11235867
Ref: library/pyexpat xml parsers expat xmlparser GetBase11236283
Ref: 371311236283
Ref: library/pyexpat xml parsers expat xmlparser GetInputContext11236479
Ref: 371411236479
Ref: library/pyexpat xml parsers expat xmlparser ExternalEntityParserCreate11236762
Ref: 371511236762
Ref: library/pyexpat xml parsers expat xmlparser SetParamEntityParsing11237275
Ref: 371811237275
Ref: library/pyexpat xml parsers expat xmlparser UseForeignDTD11237640
Ref: 371911237640
Ref: library/pyexpat xml parsers expat xmlparser SetReparseDeferralEnabled11238627
Ref: 25711238627
Ref: library/pyexpat xml parsers expat xmlparser GetReparseDeferralEnabled11240135
Ref: 25611240135
Ref: library/pyexpat xml parsers expat xmlparser buffer_size11240363
Ref: 371c11240363
Ref: library/pyexpat xml parsers expat xmlparser buffer_text11240622
Ref: 142d11240622
Ref: library/pyexpat xml parsers expat xmlparser buffer_used11241165
Ref: 371e11241165
Ref: library/pyexpat xml parsers expat xmlparser ordered_attributes11241435
Ref: 371611241435
Ref: library/pyexpat xml parsers expat xmlparser specified_attributes11241924
Ref: 371711241924
Ref: library/pyexpat xml parsers expat xmlparser ErrorByteIndex11242728
Ref: 371f11242728
Ref: library/pyexpat xml parsers expat xmlparser ErrorCode11242811
Ref: 372011242811
Ref: library/pyexpat xml parsers expat xmlparser ErrorColumnNumber11243039
Ref: 372111243039
Ref: library/pyexpat xml parsers expat xmlparser ErrorLineNumber11243128
Ref: 372211243128
Ref: library/pyexpat xml parsers expat xmlparser CurrentByteIndex11243618
Ref: 372311243618
Ref: library/pyexpat xml parsers expat xmlparser CurrentColumnNumber11243704
Ref: 372411243704
Ref: library/pyexpat xml parsers expat xmlparser CurrentLineNumber11243796
Ref: 372511243796
Ref: library/pyexpat xml parsers expat xmlparser XmlDeclHandler11244206
Ref: 372611244206
Ref: library/pyexpat xml parsers expat xmlparser StartDoctypeDeclHandler11244815
Ref: 371a11244815
Ref: library/pyexpat xml parsers expat xmlparser EndDoctypeDeclHandler11245368
Ref: 371b11245368
Ref: library/pyexpat xml parsers expat xmlparser ElementDeclHandler11245534
Ref: 372711245534
Ref: library/pyexpat xml parsers expat xmlparser AttlistDeclHandler11245748
Ref: 372811245748
Ref: library/pyexpat xml parsers expat xmlparser StartElementHandler11246652
Ref: 372911246652
Ref: library/pyexpat xml parsers expat xmlparser EndElementHandler11247047
Ref: 372a11247047
Ref: library/pyexpat xml parsers expat xmlparser ProcessingInstructionHandler11247138
Ref: 372b11247138
Ref: library/pyexpat xml parsers expat xmlparser CharacterDataHandler11247252
Ref: 371d11247252
Ref: library/pyexpat xml parsers expat xmlparser UnparsedEntityDeclHandler11247917
Ref: 371211247917
Ref: library/pyexpat xml parsers expat xmlparser EntityDeclHandler11248310
Ref: 372e11248310
Ref: library/pyexpat xml parsers expat xmlparser NotationDeclHandler11249045
Ref: 371111249045
Ref: library/pyexpat xml parsers expat xmlparser StartNamespaceDeclHandler11249336
Ref: 372f11249336
Ref: library/pyexpat xml parsers expat xmlparser EndNamespaceDeclHandler11249614
Ref: 373011249614
Ref: library/pyexpat xml parsers expat xmlparser CommentHandler11250135
Ref: 373111250135
Ref: library/pyexpat xml parsers expat xmlparser StartCdataSectionHandler11250321
Ref: 372c11250321
Ref: library/pyexpat xml parsers expat xmlparser EndCdataSectionHandler11250558
Ref: 372d11250558
Ref: library/pyexpat xml parsers expat xmlparser DefaultHandler11250651
Ref: 373211250651
Ref: library/pyexpat xml parsers expat xmlparser DefaultHandlerExpand11250936
Ref: 373311250936
Ref: library/pyexpat xml parsers expat xmlparser NotStandaloneHandler11251174
Ref: 373411251174
Ref: library/pyexpat xml parsers expat xmlparser ExternalEntityRefHandler11251694
Ref: 371011251694
Node: ExpatError 例外11252750
Ref: library/pyexpat expaterror-exceptions11252909
Ref: 373511252909
Ref: library/pyexpat expaterror-objects11252909
Ref: 370611252909
Ref: library/pyexpat xml parsers expat ExpatError code11253041
Ref: 373611253041
Ref: library/pyexpat xml parsers expat ExpatError lineno11253683
Ref: 373911253683
Ref: library/pyexpat xml parsers expat ExpatError offset11253807
Ref: 373a11253807
Node: 範例<33>11253945
Ref: library/pyexpat example11254111
Ref: 373b11254111
Ref: library/pyexpat expat-example11254111
Ref: 373c11254111
Node: Content Model Descriptions11255205
Ref: library/pyexpat content-model-descriptions11255375
Ref: 373d11255375
Ref: library/pyexpat expat-content-models11255375
Ref: 373e11255375
Ref: library/pyexpat module-xml parsers expat model11255375
Ref: 10f11255375
Node: Expat error constants11257238
Ref: library/pyexpat expat-error-constants11257389
Ref: 373f11257389
Ref: library/pyexpat expat-errors11257389
Ref: 374011257389
Ref: library/pyexpat module-xml parsers expat errors11257389
Ref: 10e11257389
Ref: library/pyexpat xml parsers expat errors codes11257977
Ref: 373811257977
Ref: library/pyexpat xml parsers expat errors messages11258118
Ref: 373711258118
Ref: library/pyexpat xml parsers expat errors XML_ERROR_ASYNC_ENTITY11258275
Ref: 374111258275
Ref: library/pyexpat xml parsers expat errors XML_ERROR_ATTRIBUTE_EXTERNAL_ENTITY_REF11258336
Ref: 374211258336
Ref: library/pyexpat xml parsers expat errors XML_ERROR_BAD_CHAR_REF11258539
Ref: 374311258539
Ref: library/pyexpat xml parsers expat errors XML_ERROR_BINARY_ENTITY_REF11258732
Ref: 374411258732
Ref: library/pyexpat xml parsers expat errors XML_ERROR_DUPLICATE_ATTRIBUTE11258908
Ref: 374511258908
Ref: library/pyexpat xml parsers expat errors XML_ERROR_INCORRECT_ENCODING11259035
Ref: 374611259035
Ref: library/pyexpat xml parsers expat errors XML_ERROR_INVALID_TOKEN11259102
Ref: 374711259102
Ref: library/pyexpat xml parsers expat errors XML_ERROR_JUNK_AFTER_DOC_ELEMENT11259318
Ref: 374811259318
Ref: library/pyexpat xml parsers expat errors XML_ERROR_MISPLACED_XML_PI11259469
Ref: 374911259469
Ref: library/pyexpat xml parsers expat errors XML_ERROR_NO_ELEMENTS11259624
Ref: 374a11259624
Ref: library/pyexpat xml parsers expat errors XML_ERROR_NO_MEMORY11259801
Ref: 374b11259801
Ref: library/pyexpat xml parsers expat errors XML_ERROR_PARAM_ENTITY_REF11259915
Ref: 374c11259915
Ref: library/pyexpat xml parsers expat errors XML_ERROR_PARTIAL_CHAR11260051
Ref: 374d11260051
Ref: library/pyexpat xml parsers expat errors XML_ERROR_RECURSIVE_ENTITY_REF11260166
Ref: 374e11260166
Ref: library/pyexpat xml parsers expat errors XML_ERROR_SYNTAX11260370
Ref: 374f11260370
Ref: library/pyexpat xml parsers expat errors XML_ERROR_TAG_MISMATCH11260478
Ref: 375011260478
Ref: library/pyexpat xml parsers expat errors XML_ERROR_UNCLOSED_TOKEN11260600
Ref: 375111260600
Ref: library/pyexpat xml parsers expat errors XML_ERROR_UNDEFINED_ENTITY11260786
Ref: 375211260786
Ref: library/pyexpat xml parsers expat errors XML_ERROR_UNKNOWN_ENCODING11260914
Ref: 375311260914
Ref: library/pyexpat xml parsers expat errors XML_ERROR_UNCLOSED_CDATA_SECTION11261034
Ref: 375411261034
Ref: library/pyexpat xml parsers expat errors XML_ERROR_EXTERNAL_ENTITY_HANDLING11261150
Ref: 375511261150
Ref: library/pyexpat xml parsers expat errors XML_ERROR_NOT_STANDALONE11261223
Ref: 375611261223
Ref: library/pyexpat xml parsers expat errors XML_ERROR_UNEXPECTED_STATE11261484
Ref: 375711261484
Ref: library/pyexpat xml parsers expat errors XML_ERROR_ENTITY_DECLARED_IN_PE11261549
Ref: 375811261549
Ref: library/pyexpat xml parsers expat errors XML_ERROR_FEATURE_REQUIRES_XML_DTD11261619
Ref: 375911261619
Ref: library/pyexpat xml parsers expat errors XML_ERROR_CANT_CHANGE_FEATURE_ONCE_PARSING11261927
Ref: 375a11261927
Ref: library/pyexpat xml parsers expat errors XML_ERROR_UNBOUND_PREFIX11262202
Ref: 375b11262202
Ref: library/pyexpat xml parsers expat errors XML_ERROR_UNDECLARING_PREFIX11262346
Ref: 375c11262346
Ref: library/pyexpat xml parsers expat errors XML_ERROR_INCOMPLETE_PE11262509
Ref: 375d11262509
Ref: library/pyexpat xml parsers expat errors XML_ERROR_XML_DECL11262625
Ref: 375e11262625
Ref: library/pyexpat xml parsers expat errors XML_ERROR_TEXT_DECL11262739
Ref: 375f11262739
Ref: library/pyexpat xml parsers expat errors XML_ERROR_PUBLICID11262877
Ref: 376011262877
Ref: library/pyexpat xml parsers expat errors XML_ERROR_SUSPENDED11263001
Ref: 376111263001
Ref: library/pyexpat xml parsers expat errors XML_ERROR_NOT_SUSPENDED11263225
Ref: 376211263225
Ref: library/pyexpat xml parsers expat errors XML_ERROR_ABORTED11263379
Ref: 376311263379
Ref: library/pyexpat xml parsers expat errors XML_ERROR_FINISHED11263493
Ref: 376411263493
Ref: library/pyexpat xml parsers expat errors XML_ERROR_SUSPEND_PE11263739
Ref: 376511263739
Ref: library/pyexpat xml parsers expat errors XML_ERROR_RESERVED_PREFIX_XML11263798
Ref: 376611263798
Ref: library/pyexpat xml parsers expat errors XML_ERROR_RESERVED_PREFIX_XMLNS11263986
Ref: 376711263986
Ref: library/pyexpat xml parsers expat errors XML_ERROR_RESERVED_NAMESPACE_URI11264150
Ref: 376811264150
Ref: library/pyexpat xml parsers expat errors XML_ERROR_INVALID_ARGUMENT11264362
Ref: 376911264362
Ref: library/pyexpat xml parsers expat errors XML_ERROR_NO_BUFFER11264485
Ref: 376a11264485
Ref: library/pyexpat xml parsers expat errors XML_ERROR_AMPLIFICATION_LIMIT_BREACH11264601
Ref: 376b11264601
Node: 網路協定 Internet protocols 及支援11264783
Ref: library/internet doc11264967
Ref: 376c11264967
Ref: library/internet internet11264967
Ref: 376d11264967
Ref: library/internet internet-protocols-and-support11264967
Ref: 376e11264967
Node: webbrowser --- 方便的網頁瀏覽器控制器11267189
Ref: library/webbrowser doc11267362
Ref: 376f11267362
Ref: library/webbrowser module-webbrowser11267362
Ref: fd11267362
Ref: library/webbrowser webbrowser-convenient-web-browser-controller11267362
Ref: 377011267362
Ref: library/webbrowser webbrowser Error11269969
Ref: 377211269969
Ref: library/webbrowser webbrowser open11270097
Ref: 377111270097
Ref: library/webbrowser webbrowser open_new11270989
Ref: 377311270989
Ref: library/webbrowser webbrowser open_new_tab11271246
Ref: 377411271246
Ref: library/webbrowser webbrowser get11271511
Ref: 377511271511
Ref: library/webbrowser webbrowser register11271735
Ref: 377611271735
Ref: webbrowser --- 方便的網頁瀏覽器控制器-Footnote-111278142
Ref: webbrowser --- 方便的網頁瀏覽器控制器-Footnote-211278212
Node: Browser Controller Objects11278345
Ref: library/webbrowser browser-controller-objects11278456
Ref: 377711278456
Ref: library/webbrowser browser-controllers11278456
Ref: 377811278456
Ref: library/webbrowser webbrowser controller name11278636
Ref: 27911278636
Ref: library/webbrowser webbrowser controller open11278710
Ref: 377911278710
Ref: library/webbrowser webbrowser controller open_new11278970
Ref: 377a11278970
Ref: library/webbrowser webbrowser controller open_new_tab11279189
Ref: 377b11279189
Node: wsgiref --- WSGI 工具與參考實作11279398
Ref: library/wsgiref doc11279607
Ref: 377c11279607
Ref: library/wsgiref module-wsgiref11279607
Ref: 10011279607
Ref: library/wsgiref wsgiref-wsgi-utilities-and-reference-implementation11279607
Ref: 377d11279607
Ref: wsgiref --- WSGI 工具與參考實作-Footnote-111281417
Ref: wsgiref --- WSGI 工具與參考實作-Footnote-211281481
Ref: wsgiref --- WSGI 工具與參考實作-Footnote-311281523
Node: wsgiref util -- WSGI 環境工具11281560
Ref: library/wsgiref module-wsgiref util11281719
Ref: 10511281719
Ref: library/wsgiref wsgiref-util-wsgi-environment-utilities11281719
Ref: 377e11281719
Ref: library/wsgiref wsgiref util guess_scheme11282175
Ref: 378011282175
Ref: library/wsgiref wsgiref util request_uri11282753
Ref: 378111282753
Ref: library/wsgiref wsgiref util application_uri11283065
Ref: 378211283065
Ref: library/wsgiref wsgiref util shift_path_info11283287
Ref: 378311283287
Ref: library/wsgiref wsgiref util setup_testing_defaults11284776
Ref: 378411284776
Ref: library/wsgiref wsgiref util is_hop_by_hop11286378
Ref: 15bf11286378
Ref: library/wsgiref wsgiref util FileWrapper11286554
Ref: 6da11286554
Ref: wsgiref util -- WSGI 環境工具-Footnote-111287721
Ref: wsgiref util -- WSGI 環境工具-Footnote-211287763
Ref: wsgiref util -- WSGI 環境工具-Footnote-311287805
Ref: wsgiref util -- WSGI 環境工具-Footnote-411287847
Ref: wsgiref util -- WSGI 環境工具-Footnote-511287889
Node: wsgiref headers -- WSGI 回應標頭工具11287948
Ref: library/wsgiref module-wsgiref headers11288176
Ref: 10211288176
Ref: library/wsgiref wsgiref-headers-wsgi-response-header-tools11288176
Ref: 378611288176
Ref: library/wsgiref wsgiref headers Headers11288406
Ref: e3a11288406
Ref: library/wsgiref wsgiref headers Headers get_all11290431
Ref: 378711290431
Ref: library/wsgiref wsgiref headers Headers add_header11290860
Ref: 378811290860
Ref: wsgiref headers -- WSGI 回應標頭工具-Footnote-111291921
Node: wsgiref simple_server -- 一個簡單的 WSGI HTTP 伺服器11291963
Ref: library/wsgiref module-wsgiref simple_server11292199
Ref: 10311292199
Ref: library/wsgiref wsgiref-simple-server-a-simple-wsgi-http-server11292199
Ref: 378911292199
Ref: library/wsgiref wsgiref simple_server make_server11292821
Ref: 378a11292821
Ref: library/wsgiref wsgiref simple_server demo_app11293631
Ref: 378b11293631
Ref: library/wsgiref wsgiref simple_server WSGIServer11294036
Ref: 378c11294036
Ref: library/wsgiref wsgiref simple_server WSGIServer set_app11294796
Ref: 378e11294796
Ref: library/wsgiref wsgiref simple_server WSGIServer get_app11294923
Ref: 378f11294923
Ref: library/wsgiref wsgiref simple_server WSGIRequestHandler11295268
Ref: 379011295268
Ref: library/wsgiref wsgiref simple_server WSGIRequestHandler get_environ11295906
Ref: 379111295906
Ref: library/wsgiref wsgiref simple_server WSGIRequestHandler get_stderr11296337
Ref: 379211296337
Ref: library/wsgiref wsgiref simple_server WSGIRequestHandler handle11296493
Ref: 379311296493
Ref: wsgiref simple_server -- 一個簡單的 WSGI HTTP 伺服器-Footnote-111296733
Ref: wsgiref simple_server -- 一個簡單的 WSGI HTTP 伺服器-Footnote-211296775
Node: wsgiref validate --- WSGI 符合性檢查11296817
Ref: library/wsgiref module-wsgiref validate11297061
Ref: 10611297061
Ref: library/wsgiref wsgiref-validate-wsgi-conformance-checker11297061
Ref: 379411297061
Ref: library/wsgiref wsgiref validate validator11297890
Ref: 379511297890
Ref: wsgiref validate --- WSGI 符合性檢查-Footnote-111300003
Ref: wsgiref validate --- WSGI 符合性檢查-Footnote-211300045
Ref: wsgiref validate --- WSGI 符合性檢查-Footnote-311300104
Node: wsgiref handlers -- 伺服器 / 閘道基本類別11300146
Ref: library/wsgiref module-wsgiref handlers11300386
Ref: 10111300386
Ref: library/wsgiref wsgiref-handlers-server-gateway-base-classes11300386
Ref: 379611300386
Ref: library/wsgiref wsgiref handlers CGIHandler11300755
Ref: 379711300755
Ref: library/wsgiref wsgiref handlers IISCGIHandler11301448
Ref: 379911301448
Ref: library/wsgiref wsgiref handlers BaseCGIHandler11302869
Ref: 379811302869
Ref: library/wsgiref wsgiref handlers SimpleHandler11303647
Ref: 379a11303647
Ref: library/wsgiref wsgiref handlers BaseHandler11304568
Ref: 18f511304568
Ref: library/wsgiref wsgiref handlers BaseHandler run11304877
Ref: 37a011304877
Ref: library/wsgiref wsgiref handlers BaseHandler _write11305189
Ref: 379e11305189
Ref: library/wsgiref wsgiref handlers BaseHandler _flush11305490
Ref: 379f11305490
Ref: library/wsgiref wsgiref handlers BaseHandler get_stdin11305730
Ref: 379b11305730
Ref: library/wsgiref wsgiref handlers BaseHandler get_stderr11305905
Ref: 379c11305905
Ref: library/wsgiref wsgiref handlers BaseHandler add_cgi_vars11306082
Ref: 379d11306082
Ref: library/wsgiref wsgiref handlers BaseHandler wsgi_multithread11306541
Ref: 37a311306541
Ref: library/wsgiref wsgiref handlers BaseHandler wsgi_multiprocess11306793
Ref: 37a411306793
Ref: library/wsgiref wsgiref handlers BaseHandler wsgi_run_once11307047
Ref: 37a511307047
Ref: library/wsgiref wsgiref handlers BaseHandler os_environ11307266
Ref: 37a611307266
Ref: library/wsgiref wsgiref handlers BaseHandler server_software11307652
Ref: 37a711307652
Ref: library/wsgiref wsgiref handlers BaseHandler get_scheme11308217
Ref: 37a911308217
Ref: library/wsgiref wsgiref handlers BaseHandler setup_environ11308493
Ref: 37aa11308493
Ref: library/wsgiref wsgiref handlers BaseHandler log_exception11309089
Ref: 37ac11309089
Ref: library/wsgiref wsgiref handlers BaseHandler traceback_limit11309540
Ref: 37ad11309540
Ref: library/wsgiref wsgiref handlers BaseHandler error_output11309726
Ref: 37ae11309726
Ref: library/wsgiref wsgiref handlers BaseHandler error_status11310657
Ref: 37af11310657
Ref: library/wsgiref wsgiref handlers BaseHandler error_headers11310843
Ref: 37b011310843
Ref: library/wsgiref wsgiref handlers BaseHandler error_body11311112
Ref: 37b111311112
Ref: library/wsgiref wsgiref handlers BaseHandler wsgi_file_wrapper11311444
Ref: 37ab11311444
Ref: library/wsgiref wsgiref handlers BaseHandler sendfile11311721
Ref: 37b211311721
Ref: library/wsgiref wsgiref handlers BaseHandler origin_server11312153
Ref: 37a811312153
Ref: library/wsgiref wsgiref handlers BaseHandler http_version11312660
Ref: 37b311312660
Ref: library/wsgiref wsgiref handlers read_environ11312858
Ref: 115111312858
Ref: wsgiref handlers -- 伺服器 / 閘道基本類別-Footnote-111313716
Ref: wsgiref handlers -- 伺服器 / 閘道基本類別-Footnote-211313758
Ref: wsgiref handlers -- 伺服器 / 閘道基本類別-Footnote-311313800
Ref: wsgiref handlers -- 伺服器 / 閘道基本類別-Footnote-411313842
Ref: wsgiref handlers -- 伺服器 / 閘道基本類別-Footnote-511313884
Node: wsgiref types -- 用於靜態型別檢查的 WSGI 型別11313926
Ref: library/wsgiref module-wsgiref types11314135
Ref: 10411314135
Ref: library/wsgiref wsgiref-types-wsgi-types-for-static-type-checking11314135
Ref: 37b411314135
Ref: library/wsgiref wsgiref types StartResponse11314380
Ref: 37b511314380
Ref: library/wsgiref wsgiref types WSGIEnvironment11314530
Ref: 377f11314530
Ref: library/wsgiref wsgiref types WSGIApplication11314628
Ref: 37b611314628
Ref: library/wsgiref wsgiref types InputStream11314741
Ref: 37a111314741
Ref: library/wsgiref wsgiref types ErrorStream11314854
Ref: 37a211314854
Ref: library/wsgiref wsgiref types FileWrapper11314967
Ref: 378511314967
Ref: wsgiref types -- 用於靜態型別檢查的 WSGI 型別-Footnote-111315201
Ref: wsgiref types -- 用於靜態型別檢查的 WSGI 型別-Footnote-211315243
Ref: wsgiref types -- 用於靜態型別檢查的 WSGI 型別-Footnote-311315313
Ref: wsgiref types -- 用於靜態型別檢查的 WSGI 型別-Footnote-411315355
Ref: wsgiref types -- 用於靜態型別檢查的 WSGI 型別-Footnote-511315421
Ref: wsgiref types -- 用於靜態型別檢查的 WSGI 型別-Footnote-611315487
Node: 範例<34>11315571
Ref: library/wsgiref examples11315721
Ref: 37b711315721
Node: urllib --- URL 處理模組11318439
Ref: library/urllib doc11318658
Ref: 37b811318658
Ref: library/urllib module-urllib11318658
Ref: f111318658
Ref: library/urllib urllib-url-handling-modules11318658
Ref: 37b911318658
Ref: urllib --- URL 處理模組-Footnote-111319235
Node: urllib request --- 用來開啟 URLs 的可擴充函式庫11319299
Ref: library/urllib request doc11319531
Ref: 37ba11319531
Ref: library/urllib request module-urllib request11319531
Ref: f411319531
Ref: library/urllib request urllib-request-extensible-library-for-opening-urls11319531
Ref: 37bb11319531
Ref: library/urllib request urllib request urlopen11320634
Ref: 27511320634
Ref: library/urllib request urllib request install_opener11324395
Ref: 37c211324395
Ref: library/urllib request urllib request build_opener11324849
Ref: 37c311324849
Ref: library/urllib request urllib request pathname2url11325993
Ref: 37cb11325993
Ref: library/urllib request urllib request url2pathname11326287
Ref: 37cc11326287
Ref: library/urllib request urllib request getproxies11326556
Ref: 37bc11326556
Ref: library/urllib request urllib request Request11327713
Ref: f7b11327713
Ref: library/urllib request urllib request OpenerDirector11332259
Ref: 37c011332259
Ref: library/urllib request urllib request BaseHandler11332479
Ref: 37c411332479
Ref: library/urllib request urllib request HTTPDefaultErrorHandler11332639
Ref: 37c611332639
Ref: library/urllib request urllib request HTTPRedirectHandler11332832
Ref: 37c711332832
Ref: library/urllib request urllib request HTTPCookieProcessor11332918
Ref: 37ce11332918
Ref: library/urllib request urllib request ProxyHandler11333021
Ref: 18d511333021
Ref: library/urllib request urllib request HTTPPasswordMgr11334109
Ref: 37cf11334109
Ref: library/urllib request urllib request HTTPPasswordMgrWithDefaultRealm11334227
Ref: 37d011334227
Ref: library/urllib request urllib request HTTPPasswordMgrWithPriorAuth11334469
Ref: e3611334469
Ref: library/urllib request urllib request AbstractBasicAuthHandler11334858
Ref: 17be11334858
Ref: library/urllib request urllib request HTTPBasicAuthHandler11336201
Ref: 37d311336201
Ref: library/urllib request urllib request ProxyBasicAuthHandler11336665
Ref: 37d411336665
Ref: library/urllib request urllib request AbstractDigestAuthHandler11337005
Ref: 188611337005
Ref: library/urllib request urllib request HTTPDigestAuthHandler11337415
Ref: 37d511337415
Ref: library/urllib request urllib request ProxyDigestAuthHandler11338275
Ref: 37d611338275
Ref: library/urllib request urllib request HTTPHandler11338616
Ref: 37c511338616
Ref: library/urllib request urllib request HTTPSHandler11338702
Ref: 11bb11338702
Ref: library/urllib request urllib request FileHandler11339029
Ref: 37c911339029
Ref: library/urllib request urllib request DataHandler11339093
Ref: f7a11339093
Ref: library/urllib request urllib request FTPHandler11339183
Ref: 37c811339183
Ref: library/urllib request urllib request CacheFTPHandler11339243
Ref: 162611339243
Ref: library/urllib request urllib request UnknownHandler11339373
Ref: 37c111339373
Ref: library/urllib request urllib request HTTPErrorProcessor11339464
Ref: 37ca11339464
Ref: urllib request --- 用來開啟 URLs 的可擴充函式庫-Footnote-111340321
Ref: urllib request --- 用來開啟 URLs 的可擴充函式庫-Footnote-211340395
Ref: urllib request --- 用來開啟 URLs 的可擴充函式庫-Footnote-311340446
Ref: urllib request --- 用來開啟 URLs 的可擴充函式庫-Footnote-411340505
Ref: urllib request --- 用來開啟 URLs 的可擴充函式庫-Footnote-511340564
Node: Request Objects11340623
Ref: library/urllib request id111340763
Ref: 37d711340763
Ref: library/urllib request request-objects11340763
Ref: 37d811340763
Ref: library/urllib request urllib request Request full_url11341032
Ref: f7d11341032
Ref: library/urllib request urllib request Request type11341322
Ref: 37d911341322
Ref: library/urllib request urllib request Request host11341370
Ref: 37da11341370
Ref: library/urllib request urllib request Request origin_req_host11341494
Ref: 37db11341494
Ref: library/urllib request urllib request Request selector11341586
Ref: 37dc11341586
Ref: library/urllib request urllib request Request data11341747
Ref: f7e11341747
Ref: library/urllib request urllib request Request unverifiable11342001
Ref: 37dd11342001
Ref: library/urllib request urllib request Request method11342128
Ref: f7c11342128
Ref: library/urllib request urllib request Request get_method11342828
Ref: 110211342828
Ref: library/urllib request urllib request Request add_header11343246
Ref: 37cd11343246
Ref: library/urllib request urllib request Request add_unredirected_header11343926
Ref: 37de11343926
Ref: library/urllib request urllib request Request has_header11344052
Ref: 37df11344052
Ref: library/urllib request urllib request Request remove_header11344193
Ref: f8011344193
Ref: library/urllib request urllib request Request get_full_url11344368
Ref: 37e011344368
Ref: library/urllib request urllib request Request set_proxy11344523
Ref: 37e111344523
Ref: library/urllib request urllib request Request get_header11344774
Ref: 37e211344774
Ref: library/urllib request urllib request Request header_items11344940
Ref: 37e311344940
Ref: Request Objects-Footnote-111345297
Node: OpenerDirector 物件11345356
Ref: library/urllib request opener-director-objects11345523
Ref: 37e411345523
Ref: library/urllib request openerdirector-objects11345523
Ref: 37e511345523
Ref: library/urllib request urllib request OpenerDirector add_handler11345651
Ref: 37e611345651
Ref: library/urllib request urllib request OpenerDirector open11347148
Ref: f7f11347148
Ref: library/urllib request urllib request OpenerDirector error11347831
Ref: 37eb11347831
Node: BaseHandler 物件11349623
Ref: library/urllib request base-handler-objects11349801
Ref: 37ee11349801
Ref: library/urllib request basehandler-objects11349801
Ref: 37ef11349801
Ref: library/urllib request urllib request BaseHandler add_parent11350037
Ref: 37f011350037
Ref: library/urllib request urllib request BaseHandler close11350116
Ref: 37f111350116
Ref: library/urllib request urllib request BaseHandler parent11350494
Ref: 37f211350494
Ref: library/urllib request urllib request BaseHandler default_open11350645
Ref: 37ec11350645
Ref: library/urllib request protocol-open11351339
Ref: 37e711351339
Ref: library/urllib request urllib request BaseHandler unknown_open11351710
Ref: 37ed11351710
Ref: library/urllib request urllib request BaseHandler http_error_default11352122
Ref: 37f311352122
Ref: library/urllib request http-error-nnn11352930
Ref: 37e811352930
Ref: library/urllib request protocol-request11353434
Ref: 37e911353434
Ref: library/urllib request protocol-response11353848
Ref: 37ea11353848
Node: HTTPRedirectHandler 物件11354438
Ref: library/urllib request http-redirect-handler11354621
Ref: 37f411354621
Ref: library/urllib request httpredirecthandler-objects11354621
Ref: 37f511354621
Ref: library/urllib request urllib request HTTPRedirectHandler redirect_request11355120
Ref: 37f611355120
Ref: library/urllib request urllib request HTTPRedirectHandler http_error_30111356204
Ref: 37f711356204
Ref: library/urllib request urllib request HTTPRedirectHandler http_error_30211356461
Ref: 37f811356461
Ref: library/urllib request urllib request HTTPRedirectHandler http_error_30311356626
Ref: 37f911356626
Ref: library/urllib request urllib request HTTPRedirectHandler http_error_30711356795
Ref: 37fa11356795
Ref: library/urllib request urllib request HTTPRedirectHandler http_error_30811357055
Ref: 37fb11357055
Ref: HTTPRedirectHandler 物件-Footnote-111357380
Ref: HTTPRedirectHandler 物件-Footnote-211357439
Node: HTTPCookieProcessor 物件11357498
Ref: library/urllib request http-cookie-processor11357682
Ref: 37fc11357682
Ref: library/urllib request httpcookieprocessor-objects11357682
Ref: 37fd11357682
Ref: library/urllib request urllib request HTTPCookieProcessor cookiejar11357817
Ref: 37fe11357817
Node: ProxyHandler 物件11357942
Ref: library/urllib request proxy-handler11358122
Ref: 380011358122
Ref: library/urllib request proxyhandler-objects11358122
Ref: 380111358122
Node: HTTPPasswordMgr 物件11358596
Ref: library/urllib request http-password-mgr11358785
Ref: 37d111358785
Ref: library/urllib request httppasswordmgr-objects11358785
Ref: 380211358785
Ref: library/urllib request urllib request HTTPPasswordMgr add_password11358967
Ref: 380311358967
Ref: library/urllib request urllib request HTTPPasswordMgr find_user_password11359314
Ref: 174411359314
Node: HTTPPasswordMgrWithPriorAuth 物件11359688
Ref: library/urllib request http-password-mgr-with-prior-auth11359889
Ref: 37d211359889
Ref: library/urllib request httppasswordmgrwithpriorauth-objects11359889
Ref: 380411359889
Ref: library/urllib request urllib request HTTPPasswordMgrWithPriorAuth add_password11360139
Ref: 380511360139
Ref: library/urllib request urllib request HTTPPasswordMgrWithPriorAuth find_user_password11360553
Ref: 380611360553
Ref: library/urllib request urllib request HTTPPasswordMgrWithPriorAuth update_authenticated11360712
Ref: 380711360712
Ref: library/urllib request urllib request HTTPPasswordMgrWithPriorAuth is_authenticated11360908
Ref: 174511360908
Node: AbstractBasicAuthHandler 物件11361074
Ref: library/urllib request abstract-basic-auth-handler11361280
Ref: 380811361280
Ref: library/urllib request abstractbasicauthhandler-objects11361280
Ref: 380911361280
Ref: library/urllib request urllib request AbstractBasicAuthHandler http_error_auth_reqed11361361
Ref: 380a11361361
Node: HTTPBasicAuthHandler 物件11362181
Ref: library/urllib request http-basic-auth-handler11362380
Ref: 380b11362380
Ref: library/urllib request httpbasicauthhandler-objects11362380
Ref: 380c11362380
Ref: library/urllib request urllib request HTTPBasicAuthHandler http_error_40111362455
Ref: 380d11362455
Node: ProxyBasicAuthHandler 物件11362602
Ref: library/urllib request proxy-basic-auth-handler11362802
Ref: 380e11362802
Ref: library/urllib request proxybasicauthhandler-objects11362802
Ref: 380f11362802
Ref: library/urllib request urllib request ProxyBasicAuthHandler http_error_40711362879
Ref: 381011362879
Node: AbstractDigestAuthHandler 物件11363037
Ref: library/urllib request abstract-digest-auth-handler11363238
Ref: 381111363238
Ref: library/urllib request abstractdigestauthhandler-objects11363238
Ref: 381211363238
Ref: library/urllib request urllib request AbstractDigestAuthHandler http_error_auth_reqed11363323
Ref: 381311363323
Node: HTTPDigestAuthHandler 物件11363700
Ref: library/urllib request http-digest-auth-handler11363902
Ref: 381411363902
Ref: library/urllib request httpdigestauthhandler-objects11363902
Ref: 381511363902
Ref: library/urllib request urllib request HTTPDigestAuthHandler http_error_40111363979
Ref: 381611363979
Node: ProxyDigestAuthHandler 物件11364137
Ref: library/urllib request proxy-digest-auth-handler11364325
Ref: 381711364325
Ref: library/urllib request proxydigestauthhandler-objects11364325
Ref: 381811364325
Ref: library/urllib request urllib request ProxyDigestAuthHandler http_error_40711364404
Ref: 381911364404
Node: HTTPHandler 物件11364563
Ref: library/urllib request http-handler-objects11364742
Ref: 381a11364742
Ref: library/urllib request httphandler-objects11364742
Ref: 381b11364742
Ref: library/urllib request urllib request HTTPHandler http_open11364799
Ref: 381c11364799
Node: HTTPSHandler 物件11364941
Ref: library/urllib request https-handler-objects11365109
Ref: 381d11365109
Ref: library/urllib request httpshandler-objects11365109
Ref: 381e11365109
Ref: library/urllib request urllib request HTTPSHandler https_open11365168
Ref: 381f11365168
Node: FileHandler 物件11365313
Ref: library/urllib request file-handler-objects11365481
Ref: 382011365481
Ref: library/urllib request filehandler-objects11365481
Ref: 382111365481
Ref: library/urllib request urllib request FileHandler file_open11365538
Ref: 382211365538
Node: DataHandler 物件11365837
Ref: library/urllib request data-handler-objects11366003
Ref: 382311366003
Ref: library/urllib request datahandler-objects11366003
Ref: 382411366003
Ref: library/urllib request urllib request DataHandler data_open11366060
Ref: 382511366060
Ref: DataHandler 物件-Footnote-111366616
Node: FTPHandler 物件11366675
Ref: library/urllib request ftp-handler-objects11366845
Ref: 382611366845
Ref: library/urllib request ftphandler-objects11366845
Ref: 382711366845
Ref: library/urllib request urllib request FTPHandler ftp_open11366900
Ref: 382811366900
Node: CacheFTPHandler 物件11367048
Ref: library/urllib request cacheftp-handler-objects11367221
Ref: 382911367221
Ref: library/urllib request cacheftphandler-objects11367221
Ref: 382a11367221
Ref: library/urllib request urllib request CacheFTPHandler setTimeout11367399
Ref: 382b11367399
Ref: library/urllib request urllib request CacheFTPHandler setMaxConns11367492
Ref: 382c11367492
Node: UnknownHandler 物件11367592
Ref: library/urllib request unknown-handler-objects11367773
Ref: 382d11367773
Ref: library/urllib request unknownhandler-objects11367773
Ref: 382e11367773
Ref: library/urllib request urllib request UnknownHandler unknown_open11367836
Ref: 382f11367836
Node: HTTPErrorProcessor 物件11367927
Ref: library/urllib request http-error-processor-objects11368096
Ref: 383011368096
Ref: library/urllib request httperrorprocessor-objects11368096
Ref: 383111368096
Ref: library/urllib request urllib request HTTPErrorProcessor http_response11368167
Ref: 383211368167
Ref: library/urllib request urllib request HTTPErrorProcessor https_response11368637
Ref: 383311368637
Node: 範例<35>11368800
Ref: library/urllib request examples11368964
Ref: 383411368964
Ref: library/urllib request urllib-request-examples11368964
Ref: 383511368964
Ref: library/urllib request urllib-examples11374500
Ref: 383711374500
Node: Legacy interface11375992
Ref: library/urllib request legacy-interface11376158
Ref: 383811376158
Ref: library/urllib request urllib request urlretrieve11376389
Ref: 383911376389
Ref: library/urllib request urllib request urlcleanup11379054
Ref: 18dc11379054
Ref: library/urllib request urllib request URLopener11379212
Ref: 2e011379212
Ref: library/urllib request urllib request URLopener open11380709
Ref: 383c11380709
Ref: library/urllib request urllib request URLopener open_unknown11381212
Ref: 383d11381212
Ref: library/urllib request urllib request URLopener retrieve11381324
Ref: 18f311381324
Ref: library/urllib request urllib request URLopener version11382858
Ref: 383b11382858
Ref: library/urllib request urllib request FancyURLopener11383175
Ref: 2e111383175
Ref: library/urllib request urllib request FancyURLopener prompt_user_passwd11384916
Ref: 383e11384916
Ref: Legacy interface-Footnote-111385456
Node: urllib request Restrictions11385515
Ref: library/urllib request urllib-request-restrictions11385662
Ref: 383f11385662
Node: urllib response --- Response classes used by urllib11388225
Ref: library/urllib request module-urllib response11388470
Ref: f511388470
Ref: library/urllib request urllib-response-response-classes-used-by-urllib11388470
Ref: 384011388470
Ref: library/urllib request urllib response addinfourl11388932
Ref: 37bd11388932
Ref: library/urllib request urllib response addinfourl url11388972
Ref: 384111388972
Ref: library/urllib request urllib response addinfourl headers11389101
Ref: 384211389101
Ref: library/urllib request urllib response addinfourl status11389237
Ref: 384311389237
Ref: library/urllib request urllib response addinfourl geturl11389338
Ref: 384411389338
Ref: library/urllib request urllib response addinfourl info11389445
Ref: 384511389445
Ref: library/urllib request urllib response addinfourl code11389564
Ref: 384611389564
Ref: library/urllib request urllib response addinfourl getcode11389679
Ref: 384711389679
Node: urllib parse --- 將 URL 剖析成元件11389800
Ref: library/urllib parse doc11390040
Ref: 384811390040
Ref: library/urllib parse module-urllib parse11390040
Ref: f311390040
Ref: library/urllib parse urllib-parse-parse-urls-into-components11390040
Ref: 384911390040
Ref: urllib parse --- 將 URL 剖析成元件-Footnote-111392016
Ref: urllib parse --- 將 URL 剖析成元件-Footnote-211392088
Ref: urllib parse --- 將 URL 剖析成元件-Footnote-311392147
Node: URL Parsing11392206
Ref: library/urllib parse url-parsing11392323
Ref: 384a11392323
Ref: library/urllib parse urllib parse urlparse11392496
Ref: 2df11392496
Ref: library/urllib parse urllib parse parse_qs11400401
Ref: 25f11400401
Ref: library/urllib parse urllib parse parse_qsl11402574
Ref: 25e11402574
Ref: library/urllib parse urllib parse urlunparse11404597
Ref: 14c911404597
Ref: library/urllib parse urllib parse urlsplit11404997
Ref: ce611404997
Ref: library/urllib parse urllib parse urlunsplit11409597
Ref: 14c811409597
Ref: library/urllib parse urllib parse urljoin11410039
Ref: e3811410039
Ref: library/urllib parse urllib parse urldefrag11411365
Ref: 11e011411365
Ref: library/urllib parse urllib parse unwrap11412708
Ref: 384d11412708
Ref: URL Parsing-Footnote-111413054
Ref: URL Parsing-Footnote-211413113
Ref: URL Parsing-Footnote-311413172
Ref: URL Parsing-Footnote-411413231
Ref: URL Parsing-Footnote-511413293
Node: URL parsing security11413352
Ref: library/urllib parse id111413505
Ref: 384e11413505
Ref: library/urllib parse url-parsing-security11413505
Ref: 384c11413505
Ref: URL parsing security-Footnote-111414963
Ref: URL parsing security-Footnote-211415025
Node: Parsing ASCII Encoded Bytes11415084
Ref: library/urllib parse id211415250
Ref: 384f11415250
Ref: library/urllib parse parsing-ascii-encoded-bytes11415250
Ref: 11e211415250
Node: Structured Parse Results11417374
Ref: library/urllib parse structured-parse-results11417531
Ref: 385011417531
Ref: library/urllib parse urlparse-result-object11417531
Ref: 384b11417531
Ref: library/urllib parse urllib parse urllib parse SplitResult geturl11417948
Ref: 385111417948
Ref: library/urllib parse urllib parse DefragResult11419072
Ref: 385211419072
Ref: library/urllib parse urllib parse ParseResult11419334
Ref: 385411419334
Ref: library/urllib parse urllib parse SplitResult11419606
Ref: 385611419606
Ref: library/urllib parse urllib parse DefragResultBytes11420012
Ref: 385311420012
Ref: library/urllib parse urllib parse ParseResultBytes11420276
Ref: 385511420276
Ref: library/urllib parse urllib parse SplitResultBytes11420578
Ref: 385711420578
Node: URL Quoting11420872
Ref: library/urllib parse url-quoting11420993
Ref: 385811420993
Ref: library/urllib parse urllib parse quote11421394
Ref: b4a11421394
Ref: library/urllib parse urllib parse quote_plus11422760
Ref: 11e111422760
Ref: library/urllib parse urllib parse quote_from_bytes11423251
Ref: 16ca11423251
Ref: library/urllib parse urllib parse unquote11423542
Ref: 168911423542
Ref: library/urllib parse urllib parse unquote_plus11424319
Ref: 385911424319
Ref: library/urllib parse urllib parse unquote_to_bytes11424657
Ref: 168a11424657
Ref: library/urllib parse urllib parse urlencode11425088
Ref: e3711425088
Ref: URL Quoting-Footnote-111428982
Ref: URL Quoting-Footnote-211429041
Ref: URL Quoting-Footnote-311429100
Ref: URL Quoting-Footnote-411429137
Ref: URL Quoting-Footnote-511429196
Ref: URL Quoting-Footnote-611429255
Ref: URL Quoting-Footnote-711429314
Ref: URL Quoting-Footnote-811429373
Ref: URL Quoting-Footnote-911429432
Node: urllib error --- urllib request 引發的例外類別11429491
Ref: library/urllib error doc11429726
Ref: 385a11429726
Ref: library/urllib error module-urllib error11429726
Ref: f211429726
Ref: library/urllib error urllib-error-exception-classes-raised-by-urllib-request11429726
Ref: 385b11429726
Ref: library/urllib error urllib error URLError11430190
Ref: 37bf11430190
Ref: library/urllib error urllib error URLError reason11430371
Ref: 385c11430371
Ref: library/urllib error urllib error HTTPError11430633
Ref: f8111430633
Ref: library/urllib error urllib error HTTPError url11430984
Ref: 385d11430984
Ref: library/urllib error urllib error HTTPError code11431066
Ref: 385e11431066
Ref: library/urllib error urllib error HTTPError reason11431308
Ref: 386011431308
Ref: library/urllib error urllib error HTTPError headers11431427
Ref: f8211431427
Ref: library/urllib error urllib error HTTPError fp11431612
Ref: 386111431612
Ref: library/urllib error urllib error ContentTooShortError11431715
Ref: 383a11431715
Ref: library/urllib error urllib error ContentTooShortError content11431948
Ref: 386211431948
Ref: urllib error --- urllib request 引發的例外類別-Footnote-111432067
Ref: urllib error --- urllib request 引發的例外類別-Footnote-211432139
Node: urllib robotparser --- robots txt 的剖析器11432198
Ref: library/urllib robotparser doc11432413
Ref: 386311432413
Ref: library/urllib robotparser module-urllib robotparser11432413
Ref: f611432413
Ref: library/urllib robotparser urllib-robotparser-parser-for-robots-txt11432413
Ref: 386411432413
Ref: library/urllib robotparser urllib robotparser RobotFileParser11432978
Ref: ca411432978
Ref: library/urllib robotparser urllib robotparser RobotFileParser set_url11433162
Ref: 386511433162
Ref: library/urllib robotparser urllib robotparser RobotFileParser read11433252
Ref: 386611433252
Ref: library/urllib robotparser urllib robotparser RobotFileParser parse11433348
Ref: 19a811433348
Ref: library/urllib robotparser urllib robotparser RobotFileParser can_fetch11433414
Ref: 386711433414
Ref: library/urllib robotparser urllib robotparser RobotFileParser mtime11433612
Ref: 386811433612
Ref: library/urllib robotparser urllib robotparser RobotFileParser modified11433821
Ref: 386911433821
Ref: library/urllib robotparser urllib robotparser RobotFileParser crawl_delay11433941
Ref: 386a11433941
Ref: library/urllib robotparser urllib robotparser RobotFileParser request_rate11434301
Ref: 386b11434301
Ref: library/urllib robotparser urllib robotparser RobotFileParser site_maps11434722
Ref: 194711434722
Ref: urllib robotparser --- robots txt 的剖析器-Footnote-111435610
Node: http --- HTTP 模組11435689
Ref: library/http doc11435887
Ref: 386c11435887
Ref: library/http http-http-modules11435887
Ref: 386d11435887
Ref: library/http module-http11435887
Ref: 6411435887
Ref: library/http http HTTPStatus11436718
Ref: 8a511436718
Ref: http --- HTTP 模組-Footnote-111437467
Node: HTTP 狀態碼11437540
Ref: library/http http-status-codes11437637
Ref: 386e11437637
Ref: library/http id111437637
Ref: 386f11437637
Ref: HTTP 狀態碼-Footnote-111451866
Ref: HTTP 狀態碼-Footnote-211451950
Ref: HTTP 狀態碼-Footnote-311452009
Ref: HTTP 狀態碼-Footnote-411452068
Ref: HTTP 狀態碼-Footnote-511452127
Ref: HTTP 狀態碼-Footnote-611452186
Ref: HTTP 狀態碼-Footnote-711452245
Ref: HTTP 狀態碼-Footnote-811452304
Ref: HTTP 狀態碼-Footnote-911452363
Ref: HTTP 狀態碼-Footnote-1011452422
Ref: HTTP 狀態碼-Footnote-1111452482
Ref: HTTP 狀態碼-Footnote-1211452542
Ref: HTTP 狀態碼-Footnote-1311452602
Ref: HTTP 狀態碼-Footnote-1411452662
Ref: HTTP 狀態碼-Footnote-1511452722
Ref: HTTP 狀態碼-Footnote-1611452782
Ref: HTTP 狀態碼-Footnote-1711452842
Ref: HTTP 狀態碼-Footnote-1811452902
Ref: HTTP 狀態碼-Footnote-1911452962
Ref: HTTP 狀態碼-Footnote-2011453022
Ref: HTTP 狀態碼-Footnote-2111453082
Ref: HTTP 狀態碼-Footnote-2211453142
Ref: HTTP 狀態碼-Footnote-2311453202
Ref: HTTP 狀態碼-Footnote-2411453262
Ref: HTTP 狀態碼-Footnote-2511453322
Ref: HTTP 狀態碼-Footnote-2611453382
Ref: HTTP 狀態碼-Footnote-2711453442
Ref: HTTP 狀態碼-Footnote-2811453502
Ref: HTTP 狀態碼-Footnote-2911453562
Ref: HTTP 狀態碼-Footnote-3011453622
Ref: HTTP 狀態碼-Footnote-3111453682
Ref: HTTP 狀態碼-Footnote-3211453742
Ref: HTTP 狀態碼-Footnote-3311453802
Ref: HTTP 狀態碼-Footnote-3411453862
Ref: HTTP 狀態碼-Footnote-3511453922
Ref: HTTP 狀態碼-Footnote-3611453982
Ref: HTTP 狀態碼-Footnote-3711454042
Ref: HTTP 狀態碼-Footnote-3811454102
Ref: HTTP 狀態碼-Footnote-3911454162
Ref: HTTP 狀態碼-Footnote-4011454222
Ref: HTTP 狀態碼-Footnote-4111454282
Ref: HTTP 狀態碼-Footnote-4211454342
Ref: HTTP 狀態碼-Footnote-4311454402
Ref: HTTP 狀態碼-Footnote-4411454462
Ref: HTTP 狀態碼-Footnote-4511454522
Ref: HTTP 狀態碼-Footnote-4611454582
Ref: HTTP 狀態碼-Footnote-4711454642
Ref: HTTP 狀態碼-Footnote-4811454702
Ref: HTTP 狀態碼-Footnote-4911454762
Ref: HTTP 狀態碼-Footnote-5011454822
Ref: HTTP 狀態碼-Footnote-5111454882
Ref: HTTP 狀態碼-Footnote-5211454942
Ref: HTTP 狀態碼-Footnote-5311455002
Ref: HTTP 狀態碼-Footnote-5411455062
Ref: HTTP 狀態碼-Footnote-5511455122
Ref: HTTP 狀態碼-Footnote-5611455182
Ref: HTTP 狀態碼-Footnote-5711455242
Ref: HTTP 狀態碼-Footnote-5811455302
Ref: HTTP 狀態碼-Footnote-5911455362
Ref: HTTP 狀態碼-Footnote-6011455422
Ref: HTTP 狀態碼-Footnote-6111455482
Ref: HTTP 狀態碼-Footnote-6211455542
Ref: HTTP 狀態碼-Footnote-6311455602
Node: HTTP 狀態分類11455662
Ref: library/http http-status-category11455779
Ref: 387011455779
Ref: library/http http HTTPMethod11457376
Ref: 387111457376
Ref: HTTP 狀態分類-Footnote-111458190
Ref: HTTP 狀態分類-Footnote-211458249
Ref: HTTP 狀態分類-Footnote-311458308
Ref: HTTP 狀態分類-Footnote-411458367
Ref: HTTP 狀態分類-Footnote-511458426
Node: HTTP 方法11458485
Ref: library/http http-methods11458579
Ref: 387211458579
Ref: library/http id211458579
Ref: 387311458579
Ref: HTTP 方法-Footnote-111460965
Ref: HTTP 方法-Footnote-211461049
Ref: HTTP 方法-Footnote-311461108
Ref: HTTP 方法-Footnote-411461167
Ref: HTTP 方法-Footnote-511461226
Ref: HTTP 方法-Footnote-611461285
Ref: HTTP 方法-Footnote-711461344
Ref: HTTP 方法-Footnote-811461403
Ref: HTTP 方法-Footnote-911461462
Ref: HTTP 方法-Footnote-1011461521
Node: http client --- HTTP 協定用戶端11461581
Ref: library/http client doc11461763
Ref: 387411461763
Ref: library/http client http-client-http-protocol-client11461763
Ref: 387511461763
Ref: library/http client module-http client11461763
Ref: 6511461763
Ref: library/http client http client HTTPConnection11462607
Ref: ae411462607
Ref: library/http client http client HTTPSConnection11464173
Ref: ae511464173
Ref: library/http client http client HTTPResponse11465836
Ref: 106811465836
Ref: library/http client http client parse_headers11466213
Ref: 194f11466213
Ref: library/http client http client HTTPException11467166
Ref: 387911467166
Ref: library/http client http client NotConnected11467314
Ref: 387a11467314
Ref: library/http client http client InvalidURL11467399
Ref: 387b11467399
Ref: library/http client http client UnknownProtocol11467549
Ref: 387c11467549
Ref: library/http client http client UnknownTransferEncoding11467637
Ref: 387d11467637
Ref: library/http client http client UnimplementedFileMode11467733
Ref: 387e11467733
Ref: library/http client http client IncompleteRead11467827
Ref: 387f11467827
Ref: library/http client http client ImproperConnectionState11467914
Ref: 388011467914
Ref: library/http client http client CannotSendRequest11468010
Ref: 388111468010
Ref: library/http client http client CannotSendHeader11468110
Ref: 388211468110
Ref: library/http client http client ResponseNotReady11468209
Ref: 388311468209
Ref: library/http client http client BadStatusLine11468308
Ref: 388411468308
Ref: library/http client http client LineTooLong11468478
Ref: 388511468478
Ref: library/http client http client RemoteDisconnected11468653
Ref: daf11468653
Ref: library/http client http client HTTP_PORT11469132
Ref: 388611469132
Ref: library/http client http client HTTPS_PORT11469231
Ref: 388711469231
Ref: library/http client http client responses11469333
Ref: 388811469333
Ref: http client --- HTTP 協定用戶端-Footnote-111469786
Ref: http client --- HTTP 協定用戶端-Footnote-211469857
Ref: http client --- HTTP 協定用戶端-Footnote-311469908
Node: HTTPConnection 物件11469967
Ref: library/http client httpconnection-objects11470089
Ref: 388911470089
Ref: library/http client id111470089
Ref: 388a11470089
Ref: library/http client http client HTTPConnection request11470218
Ref: c5011470218
Ref: library/http client http client HTTPConnection getresponse11473774
Ref: dae11473774
Ref: library/http client http client HTTPConnection set_debuglevel11474267
Ref: 388b11474267
Ref: library/http client http client HTTPConnection set_tunnel11474671
Ref: 11c011474671
Ref: library/http client http client HTTPConnection get_proxy_response_headers11476347
Ref: 15ff11476347
Ref: library/http client http client HTTPConnection connect11476628
Ref: 388c11476628
Ref: library/http client http client HTTPConnection close11476989
Ref: 388d11476989
Ref: library/http client http client HTTPConnection blocksize11477068
Ref: 388e11477068
Ref: library/http client http client HTTPConnection putrequest11477357
Ref: 388f11477357
Ref: library/http client http client HTTPConnection putheader11477906
Ref: 389011477906
Ref: library/http client http client HTTPConnection endheaders11478241
Ref: c5111478241
Ref: library/http client http client HTTPConnection send11479612
Ref: 389111479612
Ref: HTTPConnection 物件-Footnote-111479985
Ref: HTTPConnection 物件-Footnote-211480058
Ref: HTTPConnection 物件-Footnote-311480131
Ref: HTTPConnection 物件-Footnote-411480204
Ref: HTTPConnection 物件-Footnote-511480272
Ref: HTTPConnection 物件-Footnote-611480330
Node: HTTPResponse 物件11480389
Ref: library/http client httpresponse-objects11480530
Ref: 389211480530
Ref: library/http client id211480530
Ref: 389311480530
Ref: library/http client http client HTTPResponse read11480939
Ref: 164a11480939
Ref: library/http client http client HTTPResponse readinto11481052
Ref: 106911481052
Ref: library/http client http client HTTPResponse getheader11481241
Ref: 389411481241
Ref: library/http client http client HTTPResponse getheaders11481624
Ref: 389511481624
Ref: library/http client http client HTTPResponse fileno11481711
Ref: 389611481711
Ref: library/http client http client HTTPResponse msg11481803
Ref: 387711481803
Ref: library/http client http client HTTPResponse version11482019
Ref: 389711482019
Ref: library/http client http client HTTPResponse url11482137
Ref: 389811482137
Ref: library/http client http client HTTPResponse headers11482264
Ref: 389911482264
Ref: library/http client http client HTTPResponse status11482400
Ref: 389a11482400
Ref: library/http client http client HTTPResponse reason11482471
Ref: 37be11482471
Ref: library/http client http client HTTPResponse debuglevel11482544
Ref: 389b11482544
Ref: library/http client http client HTTPResponse closed11482736
Ref: 389c11482736
Ref: library/http client http client HTTPResponse geturl11482814
Ref: 389d11482814
Ref: library/http client http client HTTPResponse info11482924
Ref: 389e11482924
Ref: library/http client http client HTTPResponse getcode11483036
Ref: 389f11483036
Node: 範例<36>11483150
Ref: library/http client examples11483288
Ref: 38a011483288
Node: HTTPMessage 物件11486169
Ref: library/http client httpmessage-objects11486279
Ref: 38a111486279
Ref: library/http client id311486279
Ref: 38a211486279
Ref: library/http client http client HTTPMessage11486336
Ref: 387611486336
Node: ftplib --- FTP 協定用戶端11486558
Ref: library/ftplib doc11486751
Ref: 38a311486751
Ref: library/ftplib ftplib-ftp-protocol-client11486751
Ref: 38a411486751
Ref: library/ftplib module-ftplib11486751
Ref: 5411486751
Ref: ftplib --- FTP 協定用戶端-Footnote-111488536
Ref: ftplib --- FTP 協定用戶端-Footnote-211488602
Ref: ftplib --- FTP 協定用戶端-Footnote-311488660
Node: 參考11488719
Ref: library/ftplib ftplib-reference11488792
Ref: 38a511488792
Ref: library/ftplib reference11488792
Ref: 38a611488792
Node: FTP 物件11488886
Ref: library/ftplib ftp-objects11488962
Ref: 38a711488962
Ref: library/ftplib id111488962
Ref: 38a811488962
Ref: library/ftplib ftplib FTP11489003
Ref: 89f11489003
Ref: library/ftplib ftplib FTP set_debuglevel11491788
Ref: 38aa11491788
Ref: library/ftplib ftplib FTP connect11492272
Ref: 38a911492272
Ref: library/ftplib ftplib FTP getwelcome11493535
Ref: 38ab11493535
Ref: library/ftplib ftplib FTP login11493734
Ref: 38ac11493734
Ref: library/ftplib ftplib FTP abort11494670
Ref: 38ad11494670
Ref: library/ftplib ftplib FTP sendcmd11494796
Ref: 38ae11494796
Ref: library/ftplib ftplib FTP voidcmd11495031
Ref: 38af11495031
Ref: library/ftplib ftplib FTP retrbinary11495426
Ref: 38b111495426
Ref: library/ftplib ftplib FTP retrlines11496433
Ref: 38b311496433
Ref: library/ftplib ftplib FTP set_pasv11497096
Ref: 38b411497096
Ref: library/ftplib ftplib FTP storbinary11497258
Ref: 129d11497258
Ref: library/ftplib ftplib FTP storlines11498394
Ref: 38b511498394
Ref: library/ftplib ftplib FTP transfercmd11498878
Ref: 38b211498878
Ref: library/ftplib ftplib FTP ntransfercmd11500055
Ref: 38b611500055
Ref: library/ftplib ftplib FTP mlsd11500367
Ref: 105c11500367
Ref: library/ftplib ftplib FTP nlst11501052
Ref: 105d11501052
Ref: library/ftplib ftplib FTP dir11501459
Ref: 105e11501459
Ref: library/ftplib ftplib FTP rename11502118
Ref: 38b711502118
Ref: library/ftplib ftplib FTP delete11502237
Ref: 38b811502237
Ref: library/ftplib ftplib FTP cwd11502507
Ref: 38ba11502507
Ref: library/ftplib ftplib FTP mkd11502588
Ref: 38bb11502588
Ref: library/ftplib ftplib FTP pwd11502672
Ref: 38bc11502672
Ref: library/ftplib ftplib FTP rmd11502754
Ref: 38bd11502754
Ref: library/ftplib ftplib FTP size11502845
Ref: 38be11502845
Ref: library/ftplib ftplib FTP quit11503139
Ref: 38bf11503139
Ref: library/ftplib ftplib FTP close11503507
Ref: 38c011503507
Ref: FTP 物件-Footnote-111503945
Ref: FTP 物件-Footnote-211504003
Ref: FTP 物件-Footnote-311504062
Ref: FTP 物件-Footnote-411504120
Node: FTP_TLS 物件11504179
Ref: library/ftplib ftp-tls-objects11504276
Ref: 38c111504276
Ref: library/ftplib ftplib FTP_TLS11504325
Ref: 8a011504325
Ref: library/ftplib ftplib FTP_TLS ssl_version11507928
Ref: 38c311507928
Ref: library/ftplib ftplib FTP_TLS auth11508044
Ref: 38c411508044
Ref: library/ftplib ftplib FTP_TLS ccc11508412
Ref: 105b11508412
Ref: library/ftplib ftplib FTP_TLS prot_p11508666
Ref: 38c211508666
Ref: library/ftplib ftplib FTP_TLS prot_c11508733
Ref: 38c511508733
Ref: FTP_TLS 物件-Footnote-111508855
Ref: FTP_TLS 物件-Footnote-211508914
Ref: FTP_TLS 物件-Footnote-311508972
Node: 模組變數11509031
Ref: library/ftplib module-variables11509109
Ref: 38c611509109
Ref: library/ftplib ftplib error_reply11509152
Ref: 38b011509152
Ref: library/ftplib ftplib error_temp11509242
Ref: 38c711509242
Ref: library/ftplib ftplib error_perm11509387
Ref: 38b911509387
Ref: library/ftplib ftplib error_proto11509532
Ref: 38c811509532
Ref: library/ftplib ftplib all_errors11509699
Ref: 38c911509699
Node: poplib --- POP3 協定用戶端11510197
Ref: library/poplib doc11510387
Ref: 38ca11510387
Ref: library/poplib module-poplib11510387
Ref: 9a11510387
Ref: library/poplib poplib-pop3-protocol-client11510387
Ref: 38cb11510387
Ref: library/poplib poplib POP311511653
Ref: 8c911511653
Ref: library/poplib poplib POP3_SSL11512543
Ref: 8ca11512543
Ref: library/poplib poplib error_proto11514057
Ref: 113511514057
Ref: poplib --- POP3 協定用戶端-Footnote-111514694
Ref: poplib --- POP3 協定用戶端-Footnote-211514760
Ref: poplib --- POP3 協定用戶端-Footnote-311514819
Ref: poplib --- POP3 協定用戶端-Footnote-411514878
Ref: poplib --- POP3 協定用戶端-Footnote-511514937
Node: POP3 物件11514999
Ref: library/poplib id111515098
Ref: 38cc11515098
Ref: library/poplib pop3-objects11515098
Ref: 38cd11515098
Ref: library/poplib poplib POP3 set_debuglevel11515325
Ref: 38ce11515325
Ref: library/poplib poplib POP3 getwelcome11515788
Ref: 38cf11515788
Ref: library/poplib poplib POP3 capa11515879
Ref: f1f11515879
Ref: library/poplib poplib POP3 user11516068
Ref: 38d011516068
Ref: library/poplib poplib POP3 pass_11516186
Ref: 38d111516186
Ref: library/poplib poplib POP3 apop11516381
Ref: 38d211516381
Ref: library/poplib poplib POP3 rpop11516499
Ref: 38d311516499
Ref: library/poplib poplib POP3 stat11516618
Ref: 38d411516618
Ref: library/poplib poplib POP3 list11516750
Ref: 38d511516750
Ref: library/poplib poplib POP3 retr11516942
Ref: 38d611516942
Ref: library/poplib poplib POP3 dele11517105
Ref: 38d711517105
Ref: library/poplib poplib POP3 rset11517383
Ref: 38d811517383
Ref: library/poplib poplib POP3 noop11517458
Ref: 38d911517458
Ref: library/poplib poplib POP3 quit11517534
Ref: 113411517534
Ref: library/poplib poplib POP3 top11517624
Ref: 38da11517624
Ref: library/poplib poplib POP3 uidl11518157
Ref: 38db11518157
Ref: library/poplib poplib POP3 utf811518441
Ref: df011518441
Ref: library/poplib poplib POP3 stls11518651
Ref: f2011518651
Ref: POP3 物件-Footnote-111519452
Ref: POP3 物件-Footnote-211519511
Ref: POP3 物件-Footnote-311519570
Node: POP3 範例11519629
Ref: library/poplib id211519728
Ref: 38dc11519728
Ref: library/poplib pop3-example11519728
Ref: 38dd11519728
Node: imaplib --- IMAP4 協定客戶端11520236
Ref: library/imaplib doc11520428
Ref: 38de11520428
Ref: library/imaplib imaplib-imap4-protocol-client11520428
Ref: 38df11520428
Ref: library/imaplib module-imaplib11520428
Ref: 6a11520428
Ref: library/imaplib imaplib IMAP411521246
Ref: 8a811521246
Ref: library/imaplib imaplib IMAP4 error11522442
Ref: 38e011522442
Ref: library/imaplib imaplib IMAP4 abort11522582
Ref: 38e111522582
Ref: library/imaplib imaplib IMAP4 readonly11522841
Ref: 38e211522841
Ref: library/imaplib imaplib IMAP4_SSL11523193
Ref: 8a911523193
Ref: library/imaplib imaplib IMAP4_stream11524583
Ref: 8ab11524583
Ref: library/imaplib imaplib Internaldate2tuple11524854
Ref: 38e311524854
Ref: library/imaplib imaplib Int2AP11525102
Ref: 38e411525102
Ref: library/imaplib imaplib ParseFlags11525248
Ref: 38e511525248
Ref: library/imaplib imaplib Time2Internaldate11525367
Ref: 38e611525367
Ref: imaplib --- IMAP4 協定客戶端-Footnote-111526703
Ref: imaplib --- IMAP4 協定客戶端-Footnote-211526770
Ref: imaplib --- IMAP4 協定客戶端-Footnote-311526829
Node: IMAP4 物件11526888
Ref: library/imaplib id111526991
Ref: 38e711526991
Ref: library/imaplib imap4-objects11526991
Ref: 38e811526991
Ref: library/imaplib imaplib IMAP4 append11528483
Ref: 38e911528483
Ref: library/imaplib imaplib IMAP4 authenticate11528587
Ref: 38ea11528587
Ref: library/imaplib imaplib IMAP4 check11529420
Ref: 38eb11529420
Ref: library/imaplib imaplib IMAP4 close11529484
Ref: 8ad11529484
Ref: library/imaplib imaplib IMAP4 copy11529669
Ref: 38ec11529669
Ref: library/imaplib imaplib IMAP4 create11529781
Ref: 38ed11529781
Ref: library/imaplib imaplib IMAP4 delete11529859
Ref: 38ee11529859
Ref: library/imaplib imaplib IMAP4 deleteacl11529937
Ref: 38ef11529937
Ref: library/imaplib imaplib IMAP4 enable11530047
Ref: db311530047
Ref: library/imaplib imaplib IMAP4 expunge11530366
Ref: 38f011530366
Ref: library/imaplib imaplib IMAP4 fetch11530614
Ref: 38f111530614
Ref: library/imaplib imaplib IMAP4 getacl11530894
Ref: 38f211530894
Ref: library/imaplib imaplib IMAP4 getannotation11531048
Ref: 38f311531048
Ref: library/imaplib imaplib IMAP4 getquota11531249
Ref: 38f411531249
Ref: library/imaplib imaplib IMAP4 getquotaroot11531420
Ref: 38f511531420
Ref: library/imaplib imaplib IMAP4 list11531608
Ref: 38f611531608
Ref: library/imaplib imaplib IMAP4 login11531877
Ref: 38f711531877
Ref: library/imaplib imaplib IMAP4 login_cram_md511532010
Ref: 38f811532010
Ref: library/imaplib imaplib IMAP4 logout11532270
Ref: 38f911532270
Ref: library/imaplib imaplib IMAP4 lsub11532465
Ref: 38fa11532465
Ref: library/imaplib imaplib IMAP4 myrights11532755
Ref: 38fb11532755
Ref: library/imaplib imaplib IMAP4 namespace11532874
Ref: 38fc11532874
Ref: library/imaplib imaplib IMAP4 noop11532963
Ref: 38fd11532963
Ref: library/imaplib imaplib IMAP4 open11533023
Ref: 8aa11533023
Ref: library/imaplib imaplib IMAP4 partial11533964
Ref: 390211533964
Ref: library/imaplib imaplib IMAP4 proxyauth11534141
Ref: 390311534141
Ref: library/imaplib imaplib IMAP4 read11534291
Ref: 38fe11534291
Ref: library/imaplib imaplib IMAP4 readline11534407
Ref: 38ff11534407
Ref: library/imaplib imaplib IMAP4 recent11534519
Ref: 390411534519
Ref: library/imaplib imaplib IMAP4 rename11534674
Ref: 390511534674
Ref: library/imaplib imaplib IMAP4 response11534782
Ref: 390611534782
Ref: library/imaplib imaplib IMAP4 search11534940
Ref: 390711534940
Ref: library/imaplib imaplib IMAP4 select11535616
Ref: 390811535616
Ref: library/imaplib imaplib IMAP4 send11535911
Ref: 390011535911
Ref: library/imaplib imaplib IMAP4 setacl11536129
Ref: 390911536129
Ref: library/imaplib imaplib IMAP4 setannotation11536292
Ref: 390a11536292
Ref: library/imaplib imaplib IMAP4 setquota11536481
Ref: 390b11536481
Ref: library/imaplib imaplib IMAP4 shutdown11536652
Ref: 390111536652
Ref: library/imaplib imaplib IMAP4 socket11536839
Ref: 390c11536839
Ref: library/imaplib imaplib IMAP4 sort11536925
Ref: 390d11536925
Ref: library/imaplib imaplib IMAP4 starttls11537869
Ref: 11bd11537869
Ref: library/imaplib imaplib IMAP4 status11538396
Ref: 390e11538396
Ref: library/imaplib imaplib IMAP4 store11538492
Ref: 390f11538492
Ref: library/imaplib imaplib IMAP4 subscribe11539671
Ref: 391011539671
Ref: library/imaplib imaplib IMAP4 thread11539742
Ref: 391111539742
Ref: library/imaplib imaplib IMAP4 uid11540871
Ref: 391211540871
Ref: library/imaplib imaplib IMAP4 unsubscribe11541189
Ref: 391311541189
Ref: library/imaplib imaplib IMAP4 unselect11541266
Ref: 8ac11541266
Ref: library/imaplib imaplib IMAP4 xatom11541663
Ref: 391411541663
Ref: library/imaplib imaplib IMAP4 PROTOCOL_VERSION11541867
Ref: 391511541867
Ref: library/imaplib imaplib IMAP4 debug11541999
Ref: 391611541999
Ref: library/imaplib imaplib IMAP4 utf8_enabled11542199
Ref: db411542199
Ref: IMAP4 物件-Footnote-111542476
Ref: IMAP4 物件-Footnote-211542535
Ref: IMAP4 物件-Footnote-311542594
Ref: IMAP4 物件-Footnote-411542653
Ref: IMAP4 物件-Footnote-511542712
Ref: IMAP4 物件-Footnote-611542771
Node: IMAP4 範例11542830
Ref: library/imaplib id211542933
Ref: 391711542933
Ref: library/imaplib imap4-example11542933
Ref: 391811542933
Node: smtplib --- SMTP 協定用戶端11543435
Ref: library/smtplib doc11543635
Ref: 391911543635
Ref: library/smtplib module-smtplib11543635
Ref: b711543635
Ref: library/smtplib smtplib-smtp-protocol-client11543635
Ref: 391a11543635
Ref: library/smtplib smtplib SMTP11544278
Ref: 8d111544278
Ref: library/smtplib smtplib SMTP_SSL11546857
Ref: 8d211546857
Ref: library/smtplib smtplib LMTP11548317
Ref: 8d311548317
Ref: library/smtplib smtplib SMTPException11549218
Ref: f4311549218
Ref: library/smtplib smtplib SMTPServerDisconnected11549469
Ref: 391d11549469
Ref: library/smtplib smtplib SMTPResponseException11549694
Ref: 391e11549694
Ref: library/smtplib smtplib SMTPSenderRefused11550056
Ref: 391f11550056
Ref: library/smtplib smtplib SMTPRecipientsRefused11550290
Ref: 392011550290
Ref: library/smtplib smtplib SMTPDataError11550560
Ref: 392111550560
Ref: library/smtplib smtplib SMTPConnectError11550653
Ref: 391b11550653
Ref: library/smtplib smtplib SMTPHeloError11550771
Ref: 392211550771
Ref: library/smtplib smtplib SMTPNotSupportedError11550855
Ref: 18ce11550855
Ref: library/smtplib smtplib SMTPAuthenticationError11550996
Ref: 392311550996
Ref: smtplib --- SMTP 協定用戶端-Footnote-111551711
Ref: smtplib --- SMTP 協定用戶端-Footnote-211551778
Ref: smtplib --- SMTP 協定用戶端-Footnote-311551836
Ref: smtplib --- SMTP 協定用戶端-Footnote-411551895
Ref: smtplib --- SMTP 協定用戶端-Footnote-511551954
Ref: smtplib --- SMTP 協定用戶端-Footnote-611552012
Node: SMTP 物件11552071
Ref: library/smtplib id111552171
Ref: 392411552171
Ref: library/smtplib smtp-objects11552171
Ref: 392511552171
Ref: library/smtplib smtplib SMTP set_debuglevel11552271
Ref: dfa11552271
Ref: library/smtplib smtplib SMTP docmd11552620
Ref: 392611552620
Ref: library/smtplib smtplib SMTP connect11553270
Ref: 18cf11553270
Ref: library/smtplib smtplib SMTP helo11553961
Ref: 392711553961
Ref: library/smtplib smtplib SMTP ehlo11554421
Ref: 392811554421
Ref: library/smtplib smtplib SMTP ehlo_or_helo_if_needed11555326
Ref: 392a11555326
Ref: library/smtplib smtplib SMTP has_extn11555666
Ref: 392911555666
Ref: library/smtplib smtplib SMTP verify11555861
Ref: 392b11555861
Ref: library/smtplib smtplib SMTP login11556282
Ref: 392c11556282
Ref: library/smtplib smtplib SMTP auth11557857
Ref: df911557857
Ref: library/smtplib smtplib SMTP starttls11560086
Ref: 10d111560086
Ref: library/smtplib smtplib SMTP sendmail11561577
Ref: dfb11561577
Ref: library/smtplib smtplib SMTP send_message11565052
Ref: dfc11565052
Ref: library/smtplib smtplib SMTP quit11567125
Ref: 391c11567125
Ref: SMTP 物件-Footnote-111567588
Ref: SMTP 物件-Footnote-211567646
Ref: SMTP 物件-Footnote-311567705
Ref: SMTP 物件-Footnote-411567764
Ref: SMTP 物件-Footnote-511567822
Ref: SMTP 物件-Footnote-611567880
Node: SMTP 範例11567939
Ref: library/smtplib id211568039
Ref: 392d11568039
Ref: library/smtplib smtp-example11568039
Ref: 392e11568039
Ref: SMTP 範例-Footnote-111569444
Node: uuid --- RFC 4122 定義的 UUID 物件11569502
Ref: library/uuid doc11569716
Ref: 392f11569716
Ref: library/uuid module-uuid11569716
Ref: f811569716
Ref: library/uuid uuid-uuid-objects-according-to-rfc-412211569716
Ref: 393011569716
Ref: library/uuid uuid SafeUUID11570823
Ref: 393211570823
Ref: library/uuid uuid SafeUUID safe11570878
Ref: 393311570878
Ref: library/uuid uuid SafeUUID unsafe11571008
Ref: 393411571008
Ref: library/uuid uuid SafeUUID unknown11571099
Ref: 393511571099
Ref: library/uuid uuid UUID11571194
Ref: a0411571194
Ref: library/uuid uuid UUID bytes11573322
Ref: 393711573322
Ref: library/uuid uuid UUID bytes_le11573464
Ref: 393811573464
Ref: library/uuid uuid UUID fields11573634
Ref: 393911573634
Ref: library/uuid uuid UUID time_low11573985
Ref: 393a11573985
Ref: library/uuid uuid UUID time_mid11574179
Ref: 393b11574179
Ref: library/uuid uuid UUID time_hi_version11574386
Ref: 393c11574386
Ref: library/uuid uuid UUID clock_seq_hi_variant11574591
Ref: 393d11574591
Ref: library/uuid uuid UUID clock_seq_low11574783
Ref: 393e11574783
Ref: library/uuid uuid UUID node11574973
Ref: 393f11574973
Ref: library/uuid uuid UUID time11575170
Ref: 394011575170
Ref: library/uuid uuid UUID clock_seq11575369
Ref: 394111575369
Ref: library/uuid uuid UUID hex11575482
Ref: 394211575482
Ref: library/uuid uuid UUID int11575574
Ref: 393611575574
Ref: library/uuid uuid UUID urn11575640
Ref: 394311575640
Ref: library/uuid uuid UUID variant11575722
Ref: 394411575722
Ref: library/uuid uuid UUID version11575963
Ref: 394911575963
Ref: library/uuid uuid UUID is_safe11576094
Ref: b4d11576094
Ref: library/uuid uuid getnode11576301
Ref: b4e11576301
Ref: library/uuid uuid uuid111577266
Ref: b4f11577266
Ref: library/uuid uuid uuid311577573
Ref: 164711577573
Ref: library/uuid uuid uuid411577806
Ref: 393111577806
Ref: library/uuid uuid uuid511577869
Ref: 164811577869
Ref: library/uuid uuid NAMESPACE_DNS11578194
Ref: 394a11578194
Ref: library/uuid uuid NAMESPACE_URL11578344
Ref: 394b11578344
Ref: library/uuid uuid NAMESPACE_OID11578445
Ref: 394c11578445
Ref: library/uuid uuid NAMESPACE_X50011578550
Ref: 394d11578550
Ref: library/uuid uuid RESERVED_NCS11578785
Ref: 394511578785
Ref: library/uuid uuid RFC_412211578855
Ref: 394611578855
Ref: library/uuid uuid RESERVED_MICROSOFT11578938
Ref: 394711578938
Ref: library/uuid uuid RESERVED_FUTURE11579020
Ref: 394811579020
Ref: uuid --- RFC 4122 定義的 UUID 物件-Footnote-111579467
Ref: uuid --- RFC 4122 定義的 UUID 物件-Footnote-211579531
Ref: uuid --- RFC 4122 定義的 UUID 物件-Footnote-311579590
Ref: uuid --- RFC 4122 定義的 UUID 物件-Footnote-411579649
Ref: uuid --- RFC 4122 定義的 UUID 物件-Footnote-511579708
Ref: uuid --- RFC 4122 定義的 UUID 物件-Footnote-611579767
Ref: uuid --- RFC 4122 定義的 UUID 物件-Footnote-711579826
Node: 命令列的用法11579885
Ref: library/uuid command-line-usage11579998
Ref: 394e11579998
Ref: library/uuid uuid-cli11579998
Ref: 3ea11579998
Ref: library/uuid cmdoption-uuid-h11580255
Ref: 394f11580255
Ref: library/uuid cmdoption-uuid-help11580255
Ref: 395011580255
Ref: library/uuid cmdoption-uuid-u11580316
Ref: 395111580316
Ref: library/uuid cmdoption-uuid-uuid11580338
Ref: 395211580338
Ref: library/uuid cmdoption-uuid-n11580453
Ref: 395311580453
Ref: library/uuid cmdoption-uuid-namespace11580480
Ref: 395411580480
Ref: library/uuid cmdoption-uuid-N11580786
Ref: 395511580786
Ref: library/uuid cmdoption-uuid-name11580808
Ref: 395611580808
Node: 範例<37>11580946
Ref: library/uuid example11581086
Ref: 395711581086
Ref: library/uuid uuid-example11581086
Ref: 395811581086
Node: 命令列的範例11582332
Ref: library/uuid command-line-example11582445
Ref: 395911582445
Ref: library/uuid uuid-cli-example11582445
Ref: 395a11582445
Node: socketserver --- 用於網路伺服器的框架11582812
Ref: library/socketserver doc11583024
Ref: 395b11583024
Ref: library/socketserver module-socketserver11583024
Ref: b911583024
Ref: library/socketserver socketserver-a-framework-for-network-servers11583024
Ref: 395c11583024
Ref: library/socketserver socketserver TCPServer11583530
Ref: 12b311583530
Ref: library/socketserver socketserver UDPServer11584003
Ref: 395f11584003
Ref: library/socketserver socketserver UnixStreamServer11584307
Ref: 396011584307
Ref: library/socketserver socketserver UnixDatagramServer11584421
Ref: 396111584421
Ref: socketserver --- 用於網路伺服器的框架-Footnote-111586748
Node: Server Creation Notes11586820
Ref: library/socketserver server-creation-notes11586948
Ref: 396511586948
Ref: library/socketserver socketserver ForkingMixIn11587720
Ref: b1b11587720
Ref: library/socketserver socketserver ThreadingMixIn11587758
Ref: b1c11587758
Ref: library/socketserver socketserver ThreadingMixIn block_on_close11588418
Ref: ba411588418
Ref: library/socketserver socketserver ThreadingMixIn daemon_threads11588806
Ref: 396711588806
Ref: library/socketserver socketserver ForkingTCPServer11589333
Ref: 396811589333
Ref: library/socketserver socketserver ForkingUDPServer11589375
Ref: 396911589375
Ref: library/socketserver socketserver ThreadingTCPServer11589417
Ref: 396a11589417
Ref: library/socketserver socketserver ThreadingUDPServer11589461
Ref: 396611589461
Ref: library/socketserver socketserver ForkingUnixStreamServer11589505
Ref: 396b11589505
Ref: library/socketserver socketserver ForkingUnixDatagramServer11589554
Ref: 396c11589554
Ref: library/socketserver socketserver ThreadingUnixStreamServer11589605
Ref: 396d11589605
Ref: library/socketserver socketserver ThreadingUnixDatagramServer11589656
Ref: 396e11589656
Node: Server Objects11592009
Ref: library/socketserver server-objects11592169
Ref: 397011592169
Ref: library/socketserver socketserver BaseServer11592220
Ref: 10d611592220
Ref: library/socketserver socketserver BaseServer fileno11592620
Ref: 397311592620
Ref: library/socketserver socketserver BaseServer handle_request11592893
Ref: 12b611592893
Ref: library/socketserver socketserver BaseServer serve_forever11593493
Ref: 10d811593493
Ref: library/socketserver socketserver BaseServer service_actions11594144
Ref: 10d711594144
Ref: library/socketserver socketserver BaseServer shutdown11594447
Ref: 193b11594447
Ref: library/socketserver socketserver BaseServer server_close11594729
Ref: 396411594729
Ref: library/socketserver socketserver BaseServer address_family11594815
Ref: 397711594815
Ref: library/socketserver socketserver BaseServer RequestHandlerClass11595021
Ref: 397211595021
Ref: library/socketserver socketserver BaseServer server_address11595176
Ref: 397111595176
Ref: library/socketserver socketserver BaseServer socket11595596
Ref: 397811595596
Ref: library/socketserver socketserver BaseServer allow_reuse_address11595779
Ref: 397911595779
Ref: library/socketserver socketserver BaseServer request_queue_size11595990
Ref: 397a11595990
Ref: library/socketserver socketserver BaseServer socket_type11596474
Ref: 397b11596474
Ref: library/socketserver socketserver BaseServer timeout11596664
Ref: 12b411596664
Ref: library/socketserver socketserver BaseServer finish_request11597165
Ref: 397c11597165
Ref: library/socketserver socketserver BaseServer get_request11597382
Ref: 397411597382
Ref: library/socketserver socketserver BaseServer handle_error11597610
Ref: ce811597610
Ref: library/socketserver socketserver BaseServer handle_timeout11598060
Ref: 12b511598060
Ref: library/socketserver socketserver BaseServer process_request11598499
Ref: 397611598499
Ref: library/socketserver socketserver BaseServer server_activate11598870
Ref: 395e11598870
Ref: library/socketserver socketserver BaseServer server_bind11599113
Ref: 395d11599113
Ref: library/socketserver socketserver BaseServer verify_request11599265
Ref: 397511599265
Node: Request Handler Objects11599846
Ref: library/socketserver request-handler-objects11599995
Ref: 397d11599995
Ref: library/socketserver socketserver BaseRequestHandler11600064
Ref: 396211600064
Ref: library/socketserver socketserver BaseRequestHandler setup11600419
Ref: 397e11600419
Ref: library/socketserver socketserver BaseRequestHandler handle11600614
Ref: 396311600614
Ref: library/socketserver socketserver BaseRequestHandler finish11601329
Ref: 398211601329
Ref: library/socketserver socketserver BaseRequestHandler request11601608
Ref: 397f11601608
Ref: library/socketserver socketserver BaseRequestHandler client_address11601741
Ref: 398011601741
Ref: library/socketserver socketserver BaseRequestHandler server11601860
Ref: 398111601860
Ref: library/socketserver socketserver StreamRequestHandler11601958
Ref: c8111601958
Ref: library/socketserver socketserver DatagramRequestHandler11602004
Ref: 396f11602004
Ref: library/socketserver socketserver DatagramRequestHandler rfile11602253
Ref: 398311602253
Ref: library/socketserver socketserver DatagramRequestHandler wfile11602415
Ref: 398411602415
Node: 範例<38>11602687
Ref: library/socketserver examples11602813
Ref: 398511602813
Node: socketserver TCPServer 範例11603008
Ref: library/socketserver socketserver-tcpserver-example11603122
Ref: 398611603122
Node: socketserver UDPServer 範例11606358
Ref: library/socketserver socketserver-udpserver-example11606500
Ref: 398711606500
Node: Asynchronous Mixins11608113
Ref: library/socketserver asynchronous-mixins11608217
Ref: 398811608217
Node: http server — HTTP 伺服器11610563
Ref: library/http server doc11610770
Ref: 398911610770
Ref: library/http server http-server-http-servers11610770
Ref: 398a11610770
Ref: library/http server module-http server11610770
Ref: 6811610770
Ref: library/http server http server HTTPServer11611737
Ref: 378d11611737
Ref: library/http server http server ThreadingHTTPServer11612091
Ref: ae811612091
Ref: library/http server http server BaseHTTPRequestHandler11612642
Ref: 106511612642
Ref: library/http server http server BaseHTTPRequestHandler client_address11613629
Ref: 398c11613629
Ref: library/http server http server BaseHTTPRequestHandler server11613766
Ref: 398d11613766
Ref: library/http server http server BaseHTTPRequestHandler close_connection11613832
Ref: 398e11613832
Ref: library/http server http server BaseHTTPRequestHandler requestline11614064
Ref: 399011614064
Ref: library/http server http server BaseHTTPRequestHandler command11614376
Ref: 399111614376
Ref: library/http server http server BaseHTTPRequestHandler path11614477
Ref: 399211614477
Ref: library/http server http server BaseHTTPRequestHandler request_version11614748
Ref: 399311614748
Ref: library/http server http server BaseHTTPRequestHandler headers11614881
Ref: 387811614881
Ref: library/http server http server BaseHTTPRequestHandler rfile11615305
Ref: 399511615305
Ref: library/http server http server BaseHTTPRequestHandler wfile11615454
Ref: 399611615454
Ref: library/http server http server BaseHTTPRequestHandler server_version11615890
Ref: 399711615890
Ref: library/http server http server BaseHTTPRequestHandler sys_version11616174
Ref: 399811616174
Ref: library/http server http server BaseHTTPRequestHandler error_message_format11616426
Ref: 399a11616426
Ref: library/http server http server BaseHTTPRequestHandler error_content_type11616784
Ref: 399b11616784
Ref: library/http server http server BaseHTTPRequestHandler protocol_version11616961
Ref: 399c11616961
Ref: library/http server http server BaseHTTPRequestHandler MessageClass11617552
Ref: 399411617552
Ref: library/http server http server BaseHTTPRequestHandler responses11617787
Ref: 385f11617787
Ref: library/http server http server BaseHTTPRequestHandler handle11618350
Ref: 399f11618350
Ref: library/http server http server BaseHTTPRequestHandler handle_one_request11618650
Ref: 398f11618650
Ref: library/http server http server BaseHTTPRequestHandler handle_expect_10011618848
Ref: 39a011618848
Ref: library/http server http server BaseHTTPRequestHandler send_error11619359
Ref: ef311619359
Ref: library/http server http server BaseHTTPRequestHandler send_response11620485
Ref: 39a111620485
Ref: library/http server http server BaseHTTPRequestHandler send_header11621291
Ref: 399d11621291
Ref: library/http server http server BaseHTTPRequestHandler send_response_only11621862
Ref: 399e11621862
Ref: library/http server http server BaseHTTPRequestHandler end_headers11622284
Ref: 106611622284
Ref: library/http server http server BaseHTTPRequestHandler flush_headers11622582
Ref: 106711622582
Ref: library/http server http server BaseHTTPRequestHandler log_request11622756
Ref: 39a311622756
Ref: library/http server http server BaseHTTPRequestHandler log_error11623053
Ref: 39a411623053
Ref: library/http server http server BaseHTTPRequestHandler log_message11623298
Ref: 39a511623298
Ref: library/http server http server BaseHTTPRequestHandler version_string11623787
Ref: 399911623787
Ref: library/http server http server BaseHTTPRequestHandler date_time_string11623999
Ref: 39a211623999
Ref: library/http server http server BaseHTTPRequestHandler log_date_time_string11624387
Ref: 39a611624387
Ref: library/http server http server BaseHTTPRequestHandler address_string11624498
Ref: 39a711624498
Ref: library/http server http server SimpleHTTPRequestHandler11624739
Ref: ae711624739
Ref: library/http server http server SimpleHTTPRequestHandler server_version11625519
Ref: 39aa11625519
Ref: library/http server http server SimpleHTTPRequestHandler extensions_map11625677
Ref: 39ab11625677
Ref: library/http server http server SimpleHTTPRequestHandler do_HEAD11626174
Ref: 39a911626174
Ref: library/http server http server SimpleHTTPRequestHandler do_GET11626462
Ref: 39a811626462
Ref: library/http server http-server-cli11629016
Ref: ef411629016
Ref: library/http server http server CGIHTTPRequestHandler11630456
Ref: 28111630456
Ref: library/http server http server CGIHTTPRequestHandler cgi_directories11631647
Ref: 39ac11631647
Ref: library/http server http server CGIHTTPRequestHandler do_POST11631884
Ref: 39ad11631884
Ref: http server — HTTP 伺服器-Footnote-111633329
Ref: http server — HTTP 伺服器-Footnote-211633400
Ref: http server — HTTP 伺服器-Footnote-311633459
Ref: http server — HTTP 伺服器-Footnote-411633518
Node: 安全性注意事項<3>11633589
Ref: library/http server http-server-security11633680
Ref: 398b11633680
Ref: library/http server security-considerations11633680
Ref: 39ae11633680
Node: http cookies --- HTTP 狀態管理11634310
Ref: library/http cookies doc11634520
Ref: 39af11634520
Ref: library/http cookies http-cookies-http-state-management11634520
Ref: 39b011634520
Ref: library/http cookies module-http cookies11634520
Ref: 6711634520
Ref: library/http cookies http cookies CookieError11635902
Ref: 39b111635902
Ref: library/http cookies http cookies BaseCookie11636066
Ref: 39b211636066
Ref: library/http cookies http cookies SimpleCookie11636456
Ref: 194911636456
Ref: http cookies --- HTTP 狀態管理-Footnote-111637311
Ref: http cookies --- HTTP 狀態管理-Footnote-211637383
Ref: http cookies --- HTTP 狀態管理-Footnote-311637442
Ref: http cookies --- HTTP 狀態管理-Footnote-411637501
Ref: http cookies --- HTTP 狀態管理-Footnote-511637560
Node: Cookie 物件11637619
Ref: library/http cookies cookie-objects11637725
Ref: 39b611637725
Ref: library/http cookies id111637725
Ref: 39b711637725
Ref: library/http cookies http cookies BaseCookie value_decode11637772
Ref: 39b411637772
Ref: library/http cookies http cookies BaseCookie value_encode11638043
Ref: 39b511638043
Ref: library/http cookies http cookies BaseCookie output11638494
Ref: 39b811638494
Ref: library/http cookies http cookies BaseCookie js_output11638860
Ref: 39b911638860
Ref: library/http cookies http cookies BaseCookie load11639139
Ref: 39b311639139
Node: Morsel 物件11639421
Ref: library/http cookies id211639546
Ref: 39ba11639546
Ref: library/http cookies morsel-objects11639546
Ref: 39bb11639546
Ref: library/http cookies http cookies Morsel11639593
Ref: bab11639593
Ref: library/http cookies http cookies Morsel expires11639824
Ref: 39bc11639824
Ref: library/http cookies http cookies Morsel path11639854
Ref: 39bd11639854
Ref: library/http cookies http cookies Morsel comment11639881
Ref: 39be11639881
Ref: library/http cookies http cookies Morsel domain11639911
Ref: 39bf11639911
Ref: library/http cookies http cookies Morsel secure11639971
Ref: 39c011639971
Ref: library/http cookies http cookies Morsel version11640000
Ref: 39c111640000
Ref: library/http cookies http cookies Morsel httponly11640030
Ref: 133e11640030
Ref: library/http cookies http cookies Morsel samesite11640061
Ref: 39c211640061
Ref: library/http cookies http cookies Morsel value11640989
Ref: ba911640989
Ref: library/http cookies http cookies Morsel coded_value11641046
Ref: baa11641046
Ref: library/http cookies http cookies Morsel key11641148
Ref: ba811641148
Ref: library/http cookies http cookies Morsel set11641202
Ref: bac11641202
Ref: library/http cookies http cookies Morsel isReservedKey11641311
Ref: 39c311641311
Ref: library/http cookies http cookies Morsel output11641422
Ref: 39c411641422
Ref: library/http cookies http cookies Morsel js_output11641762
Ref: 39c511641762
Ref: library/http cookies http cookies Morsel OutputString11642036
Ref: 39c611642036
Ref: library/http cookies http cookies Morsel update11642248
Ref: e6b11642248
Ref: library/http cookies http cookies Morsel copy11642546
Ref: e6a11642546
Ref: library/http cookies http cookies Morsel setdefault11642699
Ref: 39c711642699
Ref: Morsel 物件-Footnote-111642915
Ref: Morsel 物件-Footnote-211642974
Ref: Morsel 物件-Footnote-311643033
Ref: Morsel 物件-Footnote-411643092
Node: 範例<39>11643151
Ref: library/http cookies cookie-example11643254
Ref: 39c811643254
Ref: library/http cookies example11643254
Ref: 39c911643254
Node: http cookiejar --- HTTP 客戶端的 Cookie 處理11644902
Ref: library/http cookiejar doc11645124
Ref: 39ca11645124
Ref: library/http cookiejar http-cookiejar-cookie-handling-for-http-clients11645124
Ref: 39cb11645124
Ref: library/http cookiejar module-http cookiejar11645124
Ref: 6611645124
Ref: library/http cookiejar http cookiejar LoadError11646677
Ref: 39cc11646677
Ref: library/http cookiejar http cookiejar CookieJar11647064
Ref: 37ff11647064
Ref: library/http cookiejar http cookiejar FileCookieJar11647541
Ref: 39cd11647541
Ref: library/http cookiejar http cookiejar CookiePolicy11648378
Ref: 39ce11648378
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy11648539
Ref: 191711648539
Ref: library/http cookiejar http cookiejar Cookie11650360
Ref: 39d311650360
Ref: http cookiejar --- HTTP 客戶端的 Cookie 處理-Footnote-111652041
Ref: http cookiejar --- HTTP 客戶端的 Cookie 處理-Footnote-211652115
Ref: http cookiejar --- HTTP 客戶端的 Cookie 處理-Footnote-311652174
Ref: http cookiejar --- HTTP 客戶端的 Cookie 處理-Footnote-411652233
Ref: http cookiejar --- HTTP 客戶端的 Cookie 處理-Footnote-511652292
Ref: http cookiejar --- HTTP 客戶端的 Cookie 處理-Footnote-611652351
Ref: http cookiejar --- HTTP 客戶端的 Cookie 處理-Footnote-711652410
Ref: http cookiejar --- HTTP 客戶端的 Cookie 處理-Footnote-811652469
Ref: http cookiejar --- HTTP 客戶端的 Cookie 處理-Footnote-911652528
Ref: http cookiejar --- HTTP 客戶端的 Cookie 處理-Footnote-1011652587
Ref: http cookiejar --- HTTP 客戶端的 Cookie 處理-Footnote-1111652647
Ref: http cookiejar --- HTTP 客戶端的 Cookie 處理-Footnote-1211652707
Node: CookieJar 與 FileCookieJar 物件11652767
Ref: library/http cookiejar cookie-jar-objects11652956
Ref: 39d411652956
Ref: library/http cookiejar cookiejar-and-filecookiejar-objects11652956
Ref: 39d511652956
Ref: library/http cookiejar http cookiejar CookieJar add_cookie_header11653227
Ref: 39d611653227
Ref: library/http cookiejar http cookiejar CookieJar extract_cookies11654139
Ref: 39d711654139
Ref: library/http cookiejar http cookiejar CookieJar set_policy11655367
Ref: 39d911655367
Ref: library/http cookiejar http cookiejar CookieJar make_cookies11655471
Ref: 39da11655471
Ref: library/http cookiejar http cookiejar CookieJar set_cookie_if_ok11655758
Ref: 39db11655758
Ref: library/http cookiejar http cookiejar CookieJar set_cookie11655881
Ref: 39dc11655881
Ref: library/http cookiejar http cookiejar CookieJar clear11656030
Ref: 39dd11656030
Ref: library/http cookiejar http cookiejar CookieJar clear_session_cookies11656535
Ref: 39de11656535
Ref: library/http cookiejar http cookiejar FileCookieJar save11657176
Ref: 39df11657176
Ref: library/http cookiejar http cookiejar FileCookieJar load11658029
Ref: 39cf11658029
Ref: library/http cookiejar http cookiejar FileCookieJar revert11658594
Ref: 39d011658594
Ref: library/http cookiejar http cookiejar FileCookieJar filename11658991
Ref: 39e011658991
Ref: library/http cookiejar http cookiejar FileCookieJar delayload11659125
Ref: 39e111659125
Node: FileCookieJar subclasses and co-operation with web browsers11659543
Ref: library/http cookiejar file-cookie-jar-classes11659760
Ref: 39d111659760
Ref: library/http cookiejar filecookiejar-subclasses-and-co-operation-with-web-browsers11659760
Ref: 39e211659760
Ref: library/http cookiejar http cookiejar MozillaCookieJar11659988
Ref: 39e311659988
Ref: library/http cookiejar http cookiejar LWPCookieJar11660801
Ref: 39e411660801
Ref: FileCookieJar subclasses and co-operation with web browsers-Footnote-111661281
Node: CookiePolicy 物件11661340
Ref: library/http cookiejar cookie-policy-objects11661549
Ref: 39e511661549
Ref: library/http cookiejar cookiepolicy-objects11661549
Ref: 39e611661549
Ref: library/http cookiejar http cookiejar CookiePolicy set_ok11661698
Ref: 39d811661698
Ref: library/http cookiejar http cookiejar CookiePolicy return_ok11662024
Ref: 39e711662024
Ref: library/http cookiejar http cookiejar CookiePolicy domain_return_ok11662353
Ref: 39e811662353
Ref: library/http cookiejar http cookiejar CookiePolicy path_return_ok11663731
Ref: 39e911663731
Ref: library/http cookiejar http cookiejar CookiePolicy netscape11664180
Ref: 39ea11664180
Ref: library/http cookiejar http cookiejar CookiePolicy rfc296511664250
Ref: 39eb11664250
Ref: library/http cookiejar http cookiejar CookiePolicy hide_cookie211664322
Ref: 39ec11664322
Ref: CookiePolicy 物件-Footnote-111664864
Ref: CookiePolicy 物件-Footnote-211664923
Node: DefaultCookiePolicy 物件11664982
Ref: library/http cookiejar default-cookie-policy-objects11665148
Ref: 39ed11665148
Ref: library/http cookiejar defaultcookiepolicy-objects11665148
Ref: 39ee11665148
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy blocked_domains11667463
Ref: 39ef11667463
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy set_blocked_domains11667574
Ref: 39f011667574
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy is_blocked11667688
Ref: 39f111667688
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy allowed_domains11667836
Ref: 39f211667836
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy set_allowed_domains11667972
Ref: 39f311667972
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy is_not_allowed11668106
Ref: 39f411668106
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy rfc2109_as_netscape11668446
Ref: 39d211668446
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy strict_domain11669030
Ref: 39f511669030
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy strict_rfc2965_unverifiable11669327
Ref: 39f611669327
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy strict_ns_unverifiable11669702
Ref: 39f711669702
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy strict_ns_domain11669848
Ref: 39f811669848
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy strict_ns_set_initial_dollar11670026
Ref: 39f911670026
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy strict_ns_set_path11670178
Ref: 39fa11670178
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy DomainStrictNoDots11670495
Ref: 39fb11670495
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy DomainStrictNonDomain11670731
Ref: 39fc11670731
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy DomainRFC2965Match11671074
Ref: 39fd11671074
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy DomainLiberal11671308
Ref: 39fe11671308
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy DomainStrict11671453
Ref: 39ff11671453
Ref: DefaultCookiePolicy 物件-Footnote-111671601
Ref: DefaultCookiePolicy 物件-Footnote-211671660
Ref: DefaultCookiePolicy 物件-Footnote-311671719
Ref: DefaultCookiePolicy 物件-Footnote-411671778
Ref: DefaultCookiePolicy 物件-Footnote-511671837
Ref: DefaultCookiePolicy 物件-Footnote-611671896
Ref: DefaultCookiePolicy 物件-Footnote-711671955
Node: Cookie 物件<2>11672014
Ref: library/http cookiejar cookie-objects11672171
Ref: 3a0011672171
Ref: library/http cookiejar http cookiejar Cookie version11672930
Ref: 3a0111672930
Ref: library/http cookiejar http cookiejar Cookie name11673281
Ref: 3a0211673281
Ref: library/http cookiejar http cookiejar Cookie value11673336
Ref: 3a0311673336
Ref: library/http cookiejar http cookiejar Cookie port11673413
Ref: 3a0411673413
Ref: library/http cookiejar http cookiejar Cookie domain11673541
Ref: 3a0511673541
Ref: library/http cookiejar http cookiejar Cookie path11673600
Ref: 3a0611673600
Ref: library/http cookiejar http cookiejar Cookie secure11673692
Ref: 3a0711673692
Ref: library/http cookiejar http cookiejar Cookie expires11673796
Ref: 3a0811673796
Ref: library/http cookiejar http cookiejar Cookie discard11673946
Ref: 3a0a11673946
Ref: library/http cookiejar http cookiejar Cookie comment11674020
Ref: 3a0b11674020
Ref: library/http cookiejar http cookiejar Cookie comment_url11674150
Ref: 3a0c11674150
Ref: library/http cookiejar http cookiejar Cookie rfc210911674294
Ref: 3a0d11674294
Ref: library/http cookiejar http cookiejar Cookie port_specified11674697
Ref: 3a0e11674697
Ref: library/http cookiejar http cookiejar Cookie domain_specified11674873
Ref: 3a0f11674873
Ref: library/http cookiejar http cookiejar Cookie domain_initial_dot11674979
Ref: 3a1011674979
Ref: library/http cookiejar http cookiejar Cookie has_nonstandard_attr11675232
Ref: 3a1111675232
Ref: library/http cookiejar http cookiejar Cookie get_nonstandard_attr11675346
Ref: 3a1211675346
Ref: library/http cookiejar http cookiejar Cookie set_nonstandard_attr11675508
Ref: 3a1311675508
Ref: library/http cookiejar http cookiejar Cookie is_expired11675680
Ref: 3a0911675680
Ref: Cookie 物件<2>-Footnote-111675973
Ref: Cookie 物件<2>-Footnote-211676032
Ref: Cookie 物件<2>-Footnote-311676091
Ref: Cookie 物件<2>-Footnote-411676150
Node: 範例<40>11676209
Ref: library/http cookiejar examples11676331
Ref: 3a1411676331
Ref: 範例<40>-Footnote-111677778
Node: xmlrpc --- XMLRPC 伺服器與用戶模組11677837
Ref: library/xmlrpc doc11678066
Ref: 3a1511678066
Ref: library/xmlrpc xmlrpc-xmlrpc-server-and-client-modules11678066
Ref: 3a1611678066
Node: xmlrpc client --- XML-RPC 客戶端存取11678607
Ref: library/xmlrpc client doc11678828
Ref: 3a1711678828
Ref: library/xmlrpc client module-xmlrpc client11678828
Ref: 11411678828
Ref: library/xmlrpc client xmlrpc-client-xml-rpc-client-access11678828
Ref: 3a1811678828
Ref: library/xmlrpc client xmlrpc client ServerProxy11679907
Ref: 9fa11679907
Ref: xmlrpc client --- XML-RPC 客戶端存取-Footnote-111687394
Ref: xmlrpc client --- XML-RPC 客戶端存取-Footnote-211687467
Ref: xmlrpc client --- XML-RPC 客戶端存取-Footnote-311687561
Ref: xmlrpc client --- XML-RPC 客戶端存取-Footnote-411687617
Ref: xmlrpc client --- XML-RPC 客戶端存取-Footnote-511687677
Node: ServerProxy 物件11687723
Ref: library/xmlrpc client id111687846
Ref: 3a1c11687846
Ref: library/xmlrpc client serverproxy-objects11687846
Ref: 3a1d11687846
Ref: library/xmlrpc client xmlrpc client ServerProxy system listMethods11688498
Ref: 3a1e11688498
Ref: library/xmlrpc client xmlrpc client ServerProxy system methodSignature11688661
Ref: 3a1f11688661
Ref: library/xmlrpc client xmlrpc client ServerProxy system methodHelp11689677
Ref: 3a2011689677
Node: 日期時間物件11690750
Ref: library/xmlrpc client datetime-objects11690896
Ref: 3a2111690896
Ref: library/xmlrpc client id211690896
Ref: 3a2211690896
Ref: library/xmlrpc client xmlrpc client DateTime11690949
Ref: 135111690949
Ref: library/xmlrpc client xmlrpc client DateTime decode11691259
Ref: 3a2311691259
Ref: library/xmlrpc client xmlrpc client DateTime encode11691354
Ref: 3a2411691354
Node: Binary Objects11692433
Ref: library/xmlrpc client binary-objects11692574
Ref: 3a2511692574
Ref: library/xmlrpc client id311692574
Ref: 3a2611692574
Ref: library/xmlrpc client xmlrpc client Binary11692625
Ref: 3a1911692625
Ref: library/xmlrpc client xmlrpc client Binary data11692843
Ref: 3a2711692843
Ref: library/xmlrpc client xmlrpc client Binary decode11693146
Ref: 3a2811693146
Ref: library/xmlrpc client xmlrpc client Binary encode11693283
Ref: 3a2911693283
Ref: Binary Objects-Footnote-111694523
Node: Fault Objects11694594
Ref: library/xmlrpc client fault-objects11694737
Ref: 3a2a11694737
Ref: library/xmlrpc client id411694737
Ref: 3a2b11694737
Ref: library/xmlrpc client xmlrpc client Fault11694786
Ref: 3a1a11694786
Ref: library/xmlrpc client xmlrpc client Fault faultCode11694954
Ref: 3a2c11694954
Ref: library/xmlrpc client xmlrpc client Fault faultString11695027
Ref: 3a2d11695027
Node: ProtocolError 物件11695984
Ref: library/xmlrpc client protocol-error-objects11696129
Ref: 3a2e11696129
Ref: library/xmlrpc client protocolerror-objects11696129
Ref: 3a2f11696129
Ref: library/xmlrpc client xmlrpc client ProtocolError11696190
Ref: 3a1b11696190
Ref: library/xmlrpc client xmlrpc client ProtocolError url11696464
Ref: 3a3011696464
Ref: library/xmlrpc client xmlrpc client ProtocolError errcode11696538
Ref: 3a3111696538
Ref: library/xmlrpc client xmlrpc client ProtocolError errmsg11696591
Ref: 3a3211696591
Ref: library/xmlrpc client xmlrpc client ProtocolError headers11696667
Ref: 3a3311696667
Node: MultiCall 物件11697402
Ref: library/xmlrpc client multicall-objects11697549
Ref: 3a3411697549
Ref: library/xmlrpc client xmlrpc client MultiCall11697728
Ref: 3a3511697728
Ref: MultiCall 物件-Footnote-111699435
Node: 便捷的函式11699614
Ref: library/xmlrpc client convenience-functions11699764
Ref: 3a3611699764
Ref: library/xmlrpc client xmlrpc client dumps11699812
Ref: 3a3711699812
Ref: library/xmlrpc client xmlrpc client loads11700521
Ref: 13a211700521
Node: Example of Client Usage11701382
Ref: library/xmlrpc client example-of-client-usage11701550
Ref: 3a3811701550
Ref: library/xmlrpc client xmlrpc-client-example11701550
Ref: 3a3911701550
Node: Example of Client and Server Usage11702857
Ref: library/xmlrpc client example-of-client-and-server-usage11703001
Ref: 3a3a11703001
Node: xmlrpc server --- 基本 XML-RPC 伺服器11703136
Ref: library/xmlrpc server doc11703354
Ref: 3a3c11703354
Ref: library/xmlrpc server module-xmlrpc server11703354
Ref: 11511703354
Ref: library/xmlrpc server xmlrpc-server-basic-xml-rpc-servers11703354
Ref: 3a3d11703354
Ref: library/xmlrpc server xmlrpc server SimpleXMLRPCServer11704186
Ref: 3a3e11704186
Ref: library/xmlrpc server xmlrpc server CGIXMLRPCRequestHandler11705709
Ref: 3a3f11705709
Ref: library/xmlrpc server xmlrpc server SimpleXMLRPCRequestHandler11706359
Ref: 12bb11706359
Ref: xmlrpc server --- 基本 XML-RPC 伺服器-Footnote-111706846
Node: SimpleXMLRPCServer 物件11706919
Ref: library/xmlrpc server simple-xmlrpc-servers11707055
Ref: 3a4011707055
Ref: library/xmlrpc server simplexmlrpcserver-objects11707055
Ref: 3a4111707055
Ref: library/xmlrpc server xmlrpc server SimpleXMLRPCServer register_function11707287
Ref: 3a4211707287
Ref: library/xmlrpc server xmlrpc server SimpleXMLRPCServer register_instance11708048
Ref: 3a4311708048
Ref: library/xmlrpc server xmlrpc server SimpleXMLRPCServer register_introspection_functions11709661
Ref: 3a4411709661
Ref: library/xmlrpc server xmlrpc server SimpleXMLRPCServer register_multicall_functions11709870
Ref: 3a4511709870
Ref: library/xmlrpc server xmlrpc server SimpleXMLRPCRequestHandler rpc_paths11709999
Ref: 3a4611709999
Node: SimpleXMLRPCServer 範例11710411
Ref: library/xmlrpc server id111710498
Ref: 3a4711710498
Ref: library/xmlrpc server simplexmlrpcserver-example11710498
Ref: 3a3b11710498
Node: CGIXMLRPCRequestHandler11715008
Ref: library/xmlrpc server cgixmlrpcrequesthandler11715178
Ref: 3a4811715178
Ref: library/xmlrpc server xmlrpc server CGIXMLRPCRequestHandler register_function11715362
Ref: 3a4911715362
Ref: library/xmlrpc server xmlrpc server CGIXMLRPCRequestHandler register_instance11716128
Ref: 3a4a11716128
Ref: library/xmlrpc server xmlrpc server CGIXMLRPCRequestHandler register_introspection_functions11717013
Ref: 3a4b11717013
Ref: library/xmlrpc server xmlrpc server CGIXMLRPCRequestHandler register_multicall_functions11717226
Ref: 3a4c11717226
Ref: library/xmlrpc server xmlrpc server CGIXMLRPCRequestHandler handle_request11717365
Ref: 3a4d11717365
Node: Documenting XMLRPC server11717953
Ref: library/xmlrpc server documenting-xmlrpc-server11718120
Ref: 3a4e11718120
Ref: library/xmlrpc server xmlrpc server DocXMLRPCServer11718448
Ref: 18c311718448
Ref: library/xmlrpc server xmlrpc server DocCGIXMLRPCRequestHandler11718925
Ref: 3a4f11718925
Ref: library/xmlrpc server xmlrpc server DocXMLRPCRequestHandler11719061
Ref: 3a5011719061
Node: DocXMLRPCServer 物件11719381
Ref: library/xmlrpc server doc-xmlrpc-servers11719551
Ref: 3a5111719551
Ref: library/xmlrpc server docxmlrpcserver-objects11719551
Ref: 3a5211719551
Ref: library/xmlrpc server xmlrpc server DocXMLRPCServer set_server_title11719984
Ref: 3a5311719984
Ref: library/xmlrpc server xmlrpc server DocXMLRPCServer set_server_name11720170
Ref: 3a5411720170
Ref: library/xmlrpc server xmlrpc server DocXMLRPCServer set_server_documentation11720388
Ref: 3a5511720388
Node: DocCGIXMLRPCRequestHandler11720644
Ref: library/xmlrpc server doccgixmlrpcrequesthandler11720780
Ref: 3a5611720780
Ref: library/xmlrpc server xmlrpc server DocCGIXMLRPCRequestHandler set_server_title11721231
Ref: 3a5711721231
Ref: library/xmlrpc server xmlrpc server DocCGIXMLRPCRequestHandler set_server_name11721428
Ref: 3a5811721428
Ref: library/xmlrpc server xmlrpc server DocCGIXMLRPCRequestHandler set_server_documentation11721657
Ref: 3a5911721657
Node: ipaddress --- IPv4/IPv6 操作函式庫11721924
Ref: library/ipaddress doc11722092
Ref: 3a5a11722092
Ref: library/ipaddress ipaddress-ipv4-ipv6-manipulation-library11722092
Ref: 3a5b11722092
Ref: library/ipaddress module-ipaddress11722092
Ref: 7411722092
Ref: ipaddress --- IPv4/IPv6 操作函式庫-Footnote-111723084
Node: Convenience factory functions11723153
Ref: library/ipaddress convenience-factory-functions11723279
Ref: 3a5d11723279
Ref: library/ipaddress ipaddress ip_address11723482
Ref: 3a5e11723482
Ref: library/ipaddress ipaddress ip_network11724065
Ref: 3a5f11724065
Ref: library/ipaddress ipaddress ip_interface11724778
Ref: 3a6011724778
Node: IP Addresses11725633
Ref: library/ipaddress ip-addresses11725790
Ref: 3a6111725790
Node: Address objects11725933
Ref: library/ipaddress address-objects11726040
Ref: 3a6211726040
Ref: library/ipaddress ipaddress IPv4Address11726479
Ref: 1e111726479
Ref: library/ipaddress ipaddress IPv4Address version11727764
Ref: 3a6411727764
Ref: library/ipaddress ipaddress IPv4Address max_prefixlen11727869
Ref: 3a6511727869
Ref: library/ipaddress ipaddress IPv4Address compressed11728204
Ref: 3a6611728204
Ref: library/ipaddress ipaddress IPv4Address exploded11728233
Ref: 3a6711728233
Ref: library/ipaddress ipaddress IPv4Address packed11728719
Ref: 3a6811728719
Ref: library/ipaddress ipaddress IPv4Address reverse_pointer11728953
Ref: 3a6911728953
Ref: library/ipaddress ipaddress IPv4Address is_multicast11729497
Ref: 3a6a11729497
Ref: library/ipaddress ipaddress IPv4Address is_private11729661
Ref: 153d11729661
Ref: library/ipaddress ipaddress IPv4Address is_global11731306
Ref: f0211731306
Ref: library/ipaddress ipaddress IPv4Address is_unspecified11732216
Ref: 3a6c11732216
Ref: library/ipaddress ipaddress IPv4Address is_reserved11732367
Ref: 3a6d11732367
Ref: library/ipaddress ipaddress IPv4Address is_loopback11732462
Ref: 3a6e11732462
Ref: library/ipaddress ipaddress IPv4Address is_link_local11732611
Ref: 3a6f11732611
Ref: library/ipaddress ipaddress IPv4Address ipv6_mapped11732743
Ref: 1e011732743
Ref: library/ipaddress ipaddress IPv4Address __format__11732921
Ref: 3a7011732921
Ref: library/ipaddress ipaddress IPv6Address11734171
Ref: 1e211734171
Ref: library/ipaddress ipaddress IPv6Address compressed11735545
Ref: 3a7111735545
Ref: library/ipaddress ipaddress IPv6Address exploded11735851
Ref: 3a7211735851
Ref: library/ipaddress ipaddress IPv6Address packed11736136
Ref: 3a7311736136
Ref: library/ipaddress ipaddress IPv6Address reverse_pointer11736161
Ref: 14c711736161
Ref: library/ipaddress ipaddress IPv6Address version11736195
Ref: 3a7411736195
Ref: library/ipaddress ipaddress IPv6Address max_prefixlen11736221
Ref: 3a7511736221
Ref: library/ipaddress ipaddress IPv6Address is_multicast11736253
Ref: 3a7611736253
Ref: library/ipaddress ipaddress IPv6Address is_private11736284
Ref: 153e11736284
Ref: library/ipaddress ipaddress IPv6Address is_global11736313
Ref: 153f11736313
Ref: library/ipaddress ipaddress IPv6Address is_unspecified11736374
Ref: 3a7711736374
Ref: library/ipaddress ipaddress IPv6Address is_reserved11736407
Ref: 3a7811736407
Ref: library/ipaddress ipaddress IPv6Address is_loopback11736437
Ref: 152811736437
Ref: library/ipaddress ipaddress IPv6Address is_link_local11736467
Ref: 3a7911736467
Ref: library/ipaddress ipaddress IPv6Address is_site_local11736499
Ref: 3a7a11736499
Ref: library/ipaddress ipaddress IPv6Address ipv4_mapped11736842
Ref: 3a6b11736842
Ref: library/ipaddress ipaddress IPv6Address scope_id11737111
Ref: 8b311737111
Ref: library/ipaddress ipaddress IPv6Address sixtofour11737406
Ref: 3a7b11737406
Ref: library/ipaddress ipaddress IPv6Address teredo11737693
Ref: 3a7c11737693
Ref: library/ipaddress ipaddress IPv6Address __format__11738004
Ref: 3a7d11738004
Ref: Address objects-Footnote-111738196
Ref: Address objects-Footnote-211738255
Ref: Address objects-Footnote-311738314
Ref: Address objects-Footnote-411738416
Ref: Address objects-Footnote-511738518
Ref: Address objects-Footnote-611738620
Ref: Address objects-Footnote-711738722
Ref: Address objects-Footnote-811738781
Ref: Address objects-Footnote-911738840
Ref: Address objects-Footnote-1011738899
Ref: Address objects-Footnote-1111738959
Ref: Address objects-Footnote-1211739019
Ref: Address objects-Footnote-1311739079
Ref: Address objects-Footnote-1411739139
Ref: Address objects-Footnote-1511739199
Ref: Address objects-Footnote-1611739259
Ref: Address objects-Footnote-1711739319
Ref: Address objects-Footnote-1811739379
Ref: Address objects-Footnote-1911739439
Node: Conversion to Strings and Integers11739499
Ref: library/ipaddress conversion-to-strings-and-integers11739627
Ref: 3a7e11739627
Node: Operators<2>11740251
Ref: library/ipaddress operators11740355
Ref: 3a7f11740355
Node: Comparison operators11740620
Ref: library/ipaddress comparison-operators11740718
Ref: 3a8011740718
Node: Arithmetic operators11741312
Ref: library/ipaddress arithmetic-operators11741410
Ref: 3a8111741410
Node: IP Network definitions11741913
Ref: library/ipaddress ip-network-definitions11742058
Ref: 3a8211742058
Node: Prefix net mask and host mask11742768
Ref: library/ipaddress prefix-net-mask-and-host-mask11742880
Ref: 3a8311742880
Node: Network objects11743550
Ref: library/ipaddress network-objects11743683
Ref: 3a8411743683
Ref: library/ipaddress ipaddress IPv4Network11744141
Ref: 1e311744141
Ref: library/ipaddress ipaddress IPv4Network version11746555
Ref: 3a8611746555
Ref: library/ipaddress ipaddress IPv4Network max_prefixlen11746581
Ref: 3a8711746581
Ref: library/ipaddress ipaddress IPv4Network is_multicast11746712
Ref: 3a8811746712
Ref: library/ipaddress ipaddress IPv4Network is_private11746743
Ref: 3a8911746743
Ref: library/ipaddress ipaddress IPv4Network is_unspecified11746772
Ref: 3a8a11746772
Ref: library/ipaddress ipaddress IPv4Network is_reserved11746805
Ref: 3a8b11746805
Ref: library/ipaddress ipaddress IPv4Network is_loopback11746835
Ref: 3a8c11746835
Ref: library/ipaddress ipaddress IPv4Network is_link_local11746865
Ref: 3a8d11746865
Ref: library/ipaddress ipaddress IPv4Network network_address11747054
Ref: 3a8e11747054
Ref: library/ipaddress ipaddress IPv4Network broadcast_address11747225
Ref: 3a8f11747225
Ref: library/ipaddress ipaddress IPv4Network hostmask11747419
Ref: 3a9011747419
Ref: library/ipaddress ipaddress IPv4Network netmask11747510
Ref: 3a9111747510
Ref: library/ipaddress ipaddress IPv4Network with_prefixlen11747599
Ref: 3a9211747599
Ref: library/ipaddress ipaddress IPv4Network compressed11747632
Ref: 3a9311747632
Ref: library/ipaddress ipaddress IPv4Network exploded11747661
Ref: 3a9411747661
Ref: library/ipaddress ipaddress IPv4Network with_netmask11747959
Ref: 3a9511747959
Ref: library/ipaddress ipaddress IPv4Network with_hostmask11748087
Ref: 3a9611748087
Ref: library/ipaddress ipaddress IPv4Network num_addresses11748217
Ref: 3a9711748217
Ref: library/ipaddress ipaddress IPv4Network prefixlen11748306
Ref: 3a9811748306
Ref: library/ipaddress ipaddress IPv4Network hosts11748384
Ref: 3a9911748384
Ref: library/ipaddress ipaddress IPv4Network overlaps11749381
Ref: 3a9a11749381
Ref: library/ipaddress ipaddress IPv4Network address_exclude11749553
Ref: 3a9b11749553
Ref: library/ipaddress ipaddress IPv4Network subnets11750159
Ref: e4211750159
Ref: library/ipaddress ipaddress IPv4Network supernet11751707
Ref: e4311751707
Ref: library/ipaddress ipaddress IPv4Network subnet_of11752513
Ref: 3a9c11752513
Ref: library/ipaddress ipaddress IPv4Network supernet_of11752812
Ref: 3a9d11752812
Ref: library/ipaddress ipaddress IPv4Network compare_networks11753117
Ref: 3a9e11753117
Ref: library/ipaddress ipaddress IPv6Network11753799
Ref: 1e411753799
Ref: library/ipaddress ipaddress IPv6Network version11755603
Ref: 3a9f11755603
Ref: library/ipaddress ipaddress IPv6Network max_prefixlen11755629
Ref: 3aa011755629
Ref: library/ipaddress ipaddress IPv6Network is_multicast11755661
Ref: 3aa111755661
Ref: library/ipaddress ipaddress IPv6Network is_private11755692
Ref: 3aa211755692
Ref: library/ipaddress ipaddress IPv6Network is_unspecified11755721
Ref: 3aa311755721
Ref: library/ipaddress ipaddress IPv6Network is_reserved11755754
Ref: 3aa411755754
Ref: library/ipaddress ipaddress IPv6Network is_loopback11755784
Ref: 3aa511755784
Ref: library/ipaddress ipaddress IPv6Network is_link_local11755814
Ref: 3aa611755814
Ref: library/ipaddress ipaddress IPv6Network network_address11755846
Ref: 3aa711755846
Ref: library/ipaddress ipaddress IPv6Network broadcast_address11755880
Ref: 3aa811755880
Ref: library/ipaddress ipaddress IPv6Network hostmask11755916
Ref: 3aa911755916
Ref: library/ipaddress ipaddress IPv6Network netmask11755943
Ref: 3aaa11755943
Ref: library/ipaddress ipaddress IPv6Network with_prefixlen11755969
Ref: 3aab11755969
Ref: library/ipaddress ipaddress IPv6Network compressed11756002
Ref: 3aac11756002
Ref: library/ipaddress ipaddress IPv6Network exploded11756031
Ref: 3aad11756031
Ref: library/ipaddress ipaddress IPv6Network with_netmask11756058
Ref: 3aae11756058
Ref: library/ipaddress ipaddress IPv6Network with_hostmask11756089
Ref: 3aaf11756089
Ref: library/ipaddress ipaddress IPv6Network num_addresses11756121
Ref: 3ab011756121
Ref: library/ipaddress ipaddress IPv6Network prefixlen11756153
Ref: 3ab111756153
Ref: library/ipaddress ipaddress IPv6Network hosts11756181
Ref: 3ab211756181
Ref: library/ipaddress ipaddress IPv6Network overlaps11756631
Ref: 3ab311756631
Ref: library/ipaddress ipaddress IPv6Network address_exclude11756666
Ref: 3ab411756666
Ref: library/ipaddress ipaddress IPv6Network subnets11756710
Ref: 3ab511756710
Ref: library/ipaddress ipaddress IPv6Network supernet11756772
Ref: 3ab611756772
Ref: library/ipaddress ipaddress IPv6Network subnet_of11756835
Ref: 3ab711756835
Ref: library/ipaddress ipaddress IPv6Network supernet_of11756871
Ref: 3ab811756871
Ref: library/ipaddress ipaddress IPv6Network compare_networks11756909
Ref: 3ab911756909
Ref: library/ipaddress ipaddress IPv6Network is_site_local11757051
Ref: 3aba11757051
Node: Operators<3>11757225
Ref: library/ipaddress id111757320
Ref: 3abb11757320
Node: Logical operators11757613
Ref: library/ipaddress logical-operators11757697
Ref: 3abc11757697
Node: Iteration11757902
Ref: library/ipaddress iteration11758030
Ref: 3abd11758030
Node: Networks as containers of addresses11758858
Ref: library/ipaddress networks-as-containers-of-addresses11758960
Ref: 3abe11758960
Node: Interface objects11759418
Ref: library/ipaddress interface-objects11759579
Ref: 3abf11759579
Ref: library/ipaddress ipaddress IPv4Interface11759727
Ref: 171311759727
Ref: library/ipaddress ipaddress IPv4Interface ip11760144
Ref: 3ac011760144
Ref: library/ipaddress ipaddress IPv4Interface network11760387
Ref: 3ac111760387
Ref: library/ipaddress ipaddress IPv4Interface with_prefixlen11760641
Ref: 3ac211760641
Ref: library/ipaddress ipaddress IPv4Interface with_netmask11760906
Ref: 3ac311760906
Ref: library/ipaddress ipaddress IPv4Interface with_hostmask11761176
Ref: 3ac411761176
Ref: library/ipaddress ipaddress IPv6Interface11761445
Ref: 171411761445
Ref: library/ipaddress ipaddress IPv6Interface ip11761862
Ref: 3ac511761862
Ref: library/ipaddress ipaddress IPv6Interface network11761883
Ref: 3ac611761883
Ref: library/ipaddress ipaddress IPv6Interface with_prefixlen11761909
Ref: 3ac711761909
Ref: library/ipaddress ipaddress IPv6Interface with_netmask11761942
Ref: 3ac811761942
Ref: library/ipaddress ipaddress IPv6Interface with_hostmask11761973
Ref: 3ac911761973
Node: Operators<4>11762144
Ref: library/ipaddress id211762210
Ref: 3aca11762210
Node: Logical operators<2>11762472
Ref: library/ipaddress id311762541
Ref: 3acb11762541
Node: Other Module Level Functions11763198
Ref: library/ipaddress other-module-level-functions11763354
Ref: 3acc11763354
Ref: library/ipaddress ipaddress v4_int_to_packed11763499
Ref: 3acd11763499
Ref: library/ipaddress ipaddress v6_int_to_packed11763971
Ref: 3ace11763971
Ref: library/ipaddress ipaddress summarize_address_range11764278
Ref: e4411764278
Ref: library/ipaddress ipaddress collapse_addresses11765155
Ref: e4511765155
Ref: library/ipaddress ipaddress get_mixed_type_key11765734
Ref: 3acf11765734
Node: Custom Exceptions11766327
Ref: library/ipaddress custom-exceptions11766457
Ref: 3ad011766457
Ref: library/ipaddress ipaddress AddressValueError11766628
Ref: 3a6311766628
Ref: library/ipaddress ipaddress NetmaskValueError11766728
Ref: 3a8511766728
Node: 多媒體服務11766829
Ref: library/mm doc11766988
Ref: 3ad111766988
Ref: library/mm mmedia11766988
Ref: 3ad211766988
Ref: library/mm multimedia-services11766988
Ref: 3ad311766988
Node: wave --- 讀寫 WAV 檔案11767344
Ref: library/wave doc11767468
Ref: 3ad411767468
Ref: library/wave module-wave11767468
Ref: fb11767468
Ref: library/wave wave-read-and-write-wav-files11767468
Ref: 3ad511767468
Ref: library/wave wave open11767990
Ref: 8ef11767990
Ref: library/wave wave Error11769105
Ref: 3ad811769105
Ref: wave --- 讀寫 WAV 檔案-Footnote-111769284
Node: Wave_read 物件11769348
Ref: library/wave id111769453
Ref: 3ad911769453
Ref: library/wave wave-read-objects11769453
Ref: 3ada11769453
Ref: library/wave wave Wave_read11769504
Ref: 29711769504
Ref: library/wave wave Wave_read close11769642
Ref: 3ad611769642
Ref: library/wave wave Wave_read getnchannels11769793
Ref: 3adb11769793
Ref: library/wave wave Wave_read getsampwidth11769918
Ref: 3adc11769918
Ref: library/wave wave Wave_read getframerate11770021
Ref: 3add11770021
Ref: library/wave wave Wave_read getnframes11770085
Ref: 3ade11770085
Ref: library/wave wave Wave_read getcomptype11770150
Ref: 3adf11770150
Ref: library/wave wave Wave_read getcompname11770251
Ref: 3ae011770251
Ref: library/wave wave Wave_read getparams11770418
Ref: 3ae111770418
Ref: library/wave wave Wave_read readframes11770632
Ref: 3ae211770632
Ref: library/wave wave Wave_read rewind11770755
Ref: 3ae311770755
Ref: library/wave wave Wave_read getmarkers11770971
Ref: 3ae411770971
Ref: library/wave wave Wave_read getmark11771238
Ref: 3ae511771238
Ref: library/wave wave Wave_read setpos11771638
Ref: 3ae611771638
Ref: library/wave wave Wave_read tell11771723
Ref: 3ae711771723
Node: Wave_write 物件11771797
Ref: library/wave id211771902
Ref: 3ae811771902
Ref: library/wave wave-write-objects11771902
Ref: f8c11771902
Ref: library/wave wave Wave_write11771955
Ref: 29811771955
Ref: library/wave wave Wave_write close11772959
Ref: 3ad711772959
Ref: library/wave wave Wave_write setnchannels11773253
Ref: 3aeb11773253
Ref: library/wave wave Wave_write setsampwidth11773330
Ref: 3aec11773330
Ref: library/wave wave Wave_write setframerate11773418
Ref: 3aed11773418
Ref: library/wave wave Wave_write setnframes11773610
Ref: 3ae911773610
Ref: library/wave wave Wave_write setcomptype11773817
Ref: 3aee11773817
Ref: library/wave wave Wave_write setparams11773964
Ref: 3aea11773964
Ref: library/wave wave Wave_write tell11774200
Ref: 3aef11774200
Ref: library/wave wave Wave_write writeframesraw11774387
Ref: f8d11774387
Ref: library/wave wave Wave_write writeframes11774567
Ref: f8e11774567
Node: colorsys --- 顏色系統間的轉換11775131
Ref: library/colorsys doc11775255
Ref: 3af011775255
Ref: library/colorsys colorsys-conversions-between-color-systems11775255
Ref: 3af111775255
Ref: library/colorsys module-colorsys11775255
Ref: 1811775255
Ref: library/colorsys colorsys rgb_to_yiq11776181
Ref: 3af211776181
Ref: library/colorsys colorsys yiq_to_rgb11776277
Ref: 3af311776277
Ref: library/colorsys colorsys rgb_to_hls11776373
Ref: 15fe11776373
Ref: library/colorsys colorsys hls_to_rgb11776469
Ref: 3af411776469
Ref: library/colorsys colorsys rgb_to_hsv11776565
Ref: 3af511776565
Ref: library/colorsys colorsys hsv_to_rgb11776661
Ref: 3af611776661
Ref: colorsys --- 顏色系統間的轉換-Footnote-111776960
Node: 國際化11777028
Ref: library/i18n doc11777158
Ref: 3af711777158
Ref: library/i18n i18n11777158
Ref: 3af811777158
Ref: library/i18n internationalization11777158
Ref: 3af911777158
Node: gettext --- 多語言國際化服務11777602
Ref: library/gettext doc11777719
Ref: 3afa11777719
Ref: library/gettext gettext-multilingual-internationalization-services11777719
Ref: 3afb11777719
Ref: library/gettext module-gettext11777719
Ref: 5911777719
Ref: gettext --- 多語言國際化服務-Footnote-111778631
Node: GNU gettext API11778698
Ref: library/gettext gnu-gettext-api11778810
Ref: 3afc11778810
Ref: library/gettext gettext bindtextdomain11779354
Ref: 3afd11779354
Ref: library/gettext gettext textdomain11779924
Ref: 3aff11779924
Ref: library/gettext gettext gettext11780168
Ref: 13d411780168
Ref: library/gettext gettext dgettext11780435
Ref: 3b0011780435
Ref: library/gettext gettext ngettext11780573
Ref: 3b0111780573
Ref: library/gettext gettext dngettext11781282
Ref: 3b0211781282
Ref: library/gettext gettext pgettext11781434
Ref: 99911781434
Ref: library/gettext gettext dpgettext11781483
Ref: 3b0311781483
Ref: library/gettext gettext npgettext11781541
Ref: 3b0411781541
Ref: library/gettext gettext dnpgettext11781603
Ref: 3b0511781603
Ref: GNU gettext API-Footnote-111782418
Ref: GNU gettext API-Footnote-211782898
Node: Class-based API11782963
Ref: library/gettext class-based-api11783128
Ref: 3b0611783128
Ref: library/gettext gettext find11783658
Ref: 3b0811783658
Ref: library/gettext gettext translation11785105
Ref: a1c11785105
Ref: library/gettext gettext install11786332
Ref: a1d11786332
Ref: Class-based API-Footnote-111787357
Node: The NullTranslations class11787421
Ref: library/gettext the-nulltranslations-class11787533
Ref: 3b0b11787533
Ref: library/gettext gettext NullTranslations11787978
Ref: 3b0911787978
Ref: library/gettext gettext NullTranslations _parse11788375
Ref: 3b0d11788375
Ref: library/gettext gettext NullTranslations add_fallback11788686
Ref: 3b0c11788686
Ref: library/gettext gettext NullTranslations gettext11788949
Ref: 3b0e11788949
Ref: library/gettext gettext NullTranslations ngettext11789147
Ref: 3b0f11789147
Ref: library/gettext gettext NullTranslations pgettext11789399
Ref: 3b1011789399
Ref: library/gettext gettext NullTranslations npgettext11789659
Ref: 3b1111789659
Ref: library/gettext gettext NullTranslations info11789934
Ref: 3b1211789934
Ref: library/gettext gettext NullTranslations charset11790060
Ref: 3b1311790060
Ref: library/gettext gettext NullTranslations install11790149
Ref: 3b0a11790149
Node: The GNUTranslations class11791340
Ref: library/gettext the-gnutranslations-class11791492
Ref: 3b1411791492
Ref: library/gettext gettext GNUTranslations11792987
Ref: 3b0711792987
Ref: library/gettext gettext GNUTranslations gettext11793108
Ref: 3b1511793108
Ref: library/gettext gettext GNUTranslations ngettext11793515
Ref: 3b1611793515
Ref: library/gettext gettext GNUTranslations pgettext11794439
Ref: 3b1711794439
Ref: library/gettext gettext GNUTranslations npgettext11794915
Ref: 3b1811794915
Ref: The GNUTranslations class-Footnote-111795562
Node: Solaris message catalog support11795620
Ref: library/gettext solaris-message-catalog-support11795769
Ref: 3b1911795769
Node: The Catalog constructor11796018
Ref: library/gettext the-catalog-constructor11796133
Ref: 3b1a11796133
Node: Internationalizing your programs and modules11796789
Ref: library/gettext i18n-howto11796948
Ref: 3b1b11796948
Ref: library/gettext internationalizing-your-programs-and-modules11796948
Ref: 3b1c11796948
Ref: Internationalizing your programs and modules-Footnote-111800523
Ref: Internationalizing your programs and modules-Footnote-211800556
Node: Localizing your module11800599
Ref: library/gettext localizing-your-module11800738
Ref: 3b1d11800738
Node: Localizing your application11801323
Ref: library/gettext localizing-your-application11801500
Ref: 3b1e11801500
Node: Changing languages on the fly11802228
Ref: library/gettext changing-languages-on-the-fly11802404
Ref: 3b1f11802404
Node: Deferred translations11803083
Ref: library/gettext deferred-translations11803223
Ref: 3b2011803223
Node: 致謝<9>11805455
Ref: library/gettext acknowledgements11805590
Ref: 3b2111805590
Node: locale --- 國際化服務11805977
Ref: library/locale doc11806094
Ref: 3b2211806094
Ref: library/locale locale-internationalization-services11806094
Ref: 3b2311806094
Ref: library/locale module-locale11806094
Ref: 7a11806094
Ref: library/locale locale Error11806788
Ref: 3b2411806788
Ref: library/locale locale setlocale11806911
Ref: 2bb11806911
Ref: library/locale locale localeconv11808086
Ref: ba511808086
Ref: library/locale locale nl_langinfo11816384
Ref: 3b2811816384
Ref: library/locale locale CODESET11816903
Ref: 3b2911816903
Ref: library/locale locale D_T_FMT11817039
Ref: 3b2a11817039
Ref: library/locale locale D_FMT11817238
Ref: 3b2b11817238
Ref: library/locale locale T_FMT11817428
Ref: 3b2c11817428
Ref: library/locale locale T_FMT_AMPM11817618
Ref: 3b2d11817618
Ref: library/locale locale DAY_111817767
Ref: 3b2e11817767
Ref: library/locale locale DAY_211817797
Ref: 3b2f11817797
Ref: library/locale locale DAY_311817827
Ref: 3b3011817827
Ref: library/locale locale DAY_411817857
Ref: 3b3111817857
Ref: library/locale locale DAY_511817887
Ref: 3b3211817887
Ref: library/locale locale DAY_611817917
Ref: 3b3311817917
Ref: library/locale locale DAY_711817947
Ref: 3b3411817947
Ref: library/locale locale ABDAY_111818238
Ref: 3b3511818238
Ref: library/locale locale ABDAY_211818270
Ref: 3b3611818270
Ref: library/locale locale ABDAY_311818302
Ref: 3b3711818302
Ref: library/locale locale ABDAY_411818334
Ref: 3b3811818334
Ref: library/locale locale ABDAY_511818366
Ref: 3b3911818366
Ref: library/locale locale ABDAY_611818398
Ref: 3b3a11818398
Ref: library/locale locale ABDAY_711818430
Ref: 3b3b11818430
Ref: library/locale locale MON_111818528
Ref: 3b3c11818528
Ref: library/locale locale MON_211818558
Ref: 3b3d11818558
Ref: library/locale locale MON_311818588
Ref: 3b3e11818588
Ref: library/locale locale MON_411818618
Ref: 3b3f11818618
Ref: library/locale locale MON_511818648
Ref: 3b4011818648
Ref: library/locale locale MON_611818678
Ref: 3b4111818678
Ref: library/locale locale MON_711818708
Ref: 3b4211818708
Ref: library/locale locale MON_811818738
Ref: 3b4311818738
Ref: library/locale locale MON_911818768
Ref: 3b4411818768
Ref: library/locale locale MON_1011818798
Ref: 3b4511818798
Ref: library/locale locale MON_1111818829
Ref: 3b4611818829
Ref: library/locale locale MON_1211818860
Ref: 3b4711818860
Ref: library/locale locale ABMON_111818935
Ref: 3b4811818935
Ref: library/locale locale ABMON_211818967
Ref: 3b4911818967
Ref: library/locale locale ABMON_311818999
Ref: 3b4a11818999
Ref: library/locale locale ABMON_411819031
Ref: 3b4b11819031
Ref: library/locale locale ABMON_511819063
Ref: 3b4c11819063
Ref: library/locale locale ABMON_611819095
Ref: 3b4d11819095
Ref: library/locale locale ABMON_711819127
Ref: 3b4e11819127
Ref: library/locale locale ABMON_811819159
Ref: 3b4f11819159
Ref: library/locale locale ABMON_911819191
Ref: 3b5011819191
Ref: library/locale locale ABMON_1011819223
Ref: 3b5111819223
Ref: library/locale locale ABMON_1111819256
Ref: 3b5211819256
Ref: library/locale locale ABMON_1211819289
Ref: 3b5311819289
Ref: library/locale locale RADIXCHAR11819378
Ref: 3b5411819378
Ref: library/locale locale THOUSEP11819484
Ref: 3b5511819484
Ref: library/locale locale YESEXPR11819606
Ref: 3b5611819606
Ref: library/locale locale NOEXPR11819791
Ref: 3b5711819791
Ref: library/locale locale CRNCYSTR11820252
Ref: 3b5811820252
Ref: library/locale locale ERA11820521
Ref: 3b5911820521
Ref: library/locale locale ERA_D_T_FMT11821296
Ref: 3b5a11821296
Ref: library/locale locale ERA_D_FMT11821470
Ref: 3b5b11821470
Ref: library/locale locale ERA_T_FMT11821635
Ref: 3b5c11821635
Ref: library/locale locale ALT_DIGITS11821800
Ref: 3b5d11821800
Ref: library/locale locale getdefaultlocale11821936
Ref: 2ba11821936
Ref: library/locale locale getlocale11823211
Ref: 2bd11823211
Ref: library/locale locale getpreferredencoding11823686
Ref: 4df11823686
Ref: library/locale locale getencoding11824764
Ref: 2bc11824764
Ref: library/locale locale normalize11825536
Ref: 3b6111825536
Ref: library/locale locale strcoll11825954
Ref: 3b6211825954
Ref: library/locale locale strxfrm11826271
Ref: 3b6411826271
Ref: library/locale locale format_string11826613
Ref: 4c311826613
Ref: library/locale locale currency11827311
Ref: 3b6511827311
Ref: library/locale locale str11827954
Ref: 3b6611827954
Ref: library/locale locale delocalize11828141
Ref: dcb11828141
Ref: library/locale locale localize11828319
Ref: 3b6711828319
Ref: library/locale locale atof11828537
Ref: 3b6811828537
Ref: library/locale locale atoi11828759
Ref: 3b6911828759
Ref: library/locale locale LC_CTYPE11828888
Ref: 3b5f11828888
Ref: library/locale locale LC_COLLATE11829557
Ref: 3b6311829557
Ref: library/locale locale LC_TIME11829752
Ref: 3b6a11829752
Ref: library/locale locale LC_MONETARY11829905
Ref: 3b2711829905
Ref: library/locale locale LC_MESSAGES11830080
Ref: 3b6b11830080
Ref: library/locale locale LC_NUMERIC11830504
Ref: 3b2511830504
Ref: library/locale locale LC_ALL11830829
Ref: 3b5e11830829
Ref: library/locale locale CHAR_MAX11831256
Ref: 3b2611831256
Ref: locale --- 國際化服務-Footnote-111832110
Ref: locale --- 國際化服務-Footnote-211832176
Ref: locale --- 國際化服務-Footnote-311832235
Ref: locale --- 國際化服務-Footnote-411832294
Ref: locale --- 國際化服務-Footnote-511832336
Node: Background details hints tips and caveats11832378
Ref: library/locale background-details-hints-tips-and-caveats11832543
Ref: 3b6c11832543
Node: For extension writers and programs that embed Python11834744
Ref: library/locale embedding-locale11834944
Ref: 3b6d11834944
Ref: library/locale for-extension-writers-and-programs-that-embed-python11834944
Ref: 3b6e11834944
Node: Access to message catalogs11835739
Ref: library/locale access-to-message-catalogs11835889
Ref: 3b6f11835889
Ref: library/locale locale-gettext11835889
Ref: 3b7011835889
Ref: library/locale locale gettext11835962
Ref: 3b7111835962
Ref: library/locale locale dgettext11835996
Ref: 3b7211835996
Ref: library/locale locale dcgettext11836039
Ref: 3b7311836039
Ref: library/locale locale textdomain11836093
Ref: 3b7411836093
Ref: library/locale locale bindtextdomain11836133
Ref: 3b7511836133
Ref: library/locale locale bind_textdomain_codeset11836182
Ref: 3b7611836182
Node: 程式框架11837161
Ref: library/frameworks doc11837336
Ref: 3b7711837336
Ref: library/frameworks frameworks11837336
Ref: 3b7811837336
Ref: library/frameworks program-frameworks11837336
Ref: 3b7911837336
Node: turtle --- 龜圖學 Turtle graphics11837850
Ref: library/turtle doc11837991
Ref: 3b7a11837991
Ref: library/turtle module-turtle11837991
Ref: ea11837991
Ref: library/turtle turtle-turtle-graphics11837991
Ref: 3b7b11837991
Ref: turtle --- 龜圖學 Turtle graphics-Footnote-111838686
Node: 介紹11838752
Ref: library/turtle introduction11838851
Ref: 3b7c11838851
Ref: 介紹-Footnote-111839089
Node: Get started11839142
Ref: library/turtle get-started11839259
Ref: 3b7d11839259
Node: 教學<3>11840435
Ref: library/turtle turtle-tutorial11840552
Ref: 3b7e11840552
Ref: library/turtle tutorial11840552
Ref: 3b7f11840552
Node: 啟動一個烏龜環境11840771
Ref: library/turtle starting-a-turtle-environment11840862
Ref: 3b8011840862
Node: 基本繪圖11841153
Ref: library/turtle basic-drawing11841280
Ref: 3b8111841280
Node: Pen control11841909
Ref: library/turtle pen-control11841999
Ref: 3b8211841999
Node: The turtle's position11842327
Ref: library/turtle the-turtle-s-position11842417
Ref: 3b8311842417
Node: Making algorithmic patterns11842854
Ref: library/turtle making-algorithmic-patterns11842948
Ref: 3b8411842948
Node: How to11843919
Ref: library/turtle how-to11844050
Ref: 3b8511844050
Ref: library/turtle turtle-how-to11844050
Ref: 3b8611844050
Node: Get started as quickly as possible11844317
Ref: library/turtle get-started-as-quickly-as-possible11844434
Ref: 3b8711844434
Ref: library/turtle note11845184
Ref: 3b8911845184
Node: Use the turtle module namespace11845452
Ref: library/turtle use-the-turtle-module-namespace11845609
Ref: 3b8a11845609
Node: Use turtle graphics in a script11846269
Ref: library/turtle use-turtle-graphics-in-a-script11846427
Ref: 3b8b11846427
Node: Use object-oriented turtle graphics11847117
Ref: library/turtle use-object-oriented-turtle-graphics11847235
Ref: 3b8c11847235
Node: Turtle graphics reference11848458
Ref: library/turtle turtle-graphics-reference11848635
Ref: 3b8f11848635
Node: Turtle methods11848955
Ref: library/turtle turtle-methods11849070
Ref: 3b9011849070
Node: Methods of TurtleScreen/Screen11852082
Ref: library/turtle methods-of-turtlescreen-screen11852197
Ref: 3bdd11852197
Node: Methods of RawTurtle/Turtle and corresponding functions11853519
Ref: library/turtle methods-of-rawturtle-turtle-and-corresponding-functions11853748
Ref: 3bfc11853748
Node: Turtle motion11854160
Ref: library/turtle turtle-motion11854293
Ref: 3bfd11854293
Ref: library/turtle turtle forward11854342
Ref: 3b8811854342
Ref: library/turtle turtle fd11854380
Ref: 3b9111854380
Ref: library/turtle turtle back11854810
Ref: 3b9411854810
Ref: library/turtle turtle bk11854845
Ref: 3b9311854845
Ref: library/turtle turtle backward11854878
Ref: 3b9211854878
Ref: library/turtle turtle right11855240
Ref: 3b9511855240
Ref: library/turtle turtle rt11855273
Ref: 3b9611855273
Ref: library/turtle turtle left11855731
Ref: 3b9711855731
Ref: library/turtle turtle lt11855763
Ref: 3b9811855763
Ref: library/turtle turtle goto11856218
Ref: 3b9911856218
Ref: library/turtle turtle setpos11856254
Ref: 3b9a11856254
Ref: library/turtle turtle setposition11856292
Ref: 3b9b11856292
Ref: library/turtle turtle teleport11857035
Ref: 162411857035
Ref: library/turtle turtle setx11858033
Ref: 3b9c11858033
Ref: library/turtle turtle sety11858347
Ref: 3b9d11858347
Ref: library/turtle turtle setheading11858660
Ref: 3b9e11858660
Ref: library/turtle turtle seth11858701
Ref: 3b9f11858701
Ref: library/turtle turtle home11859509
Ref: 3ba011859509
Ref: library/turtle turtle circle11859930
Ref: 3ba111859930
Ref: library/turtle turtle dot11861299
Ref: 3ba211861299
Ref: library/turtle turtle stamp11861839
Ref: 3ba311861839
Ref: library/turtle turtle clearstamp11862174
Ref: 3ba411862174
Ref: library/turtle turtle clearstamps11862676
Ref: 3ba511862676
Ref: library/turtle turtle undo11863177
Ref: 3ba611863177
Ref: library/turtle turtle speed11863500
Ref: 3ba711863500
Node: Tell Turtle's state11864469
Ref: library/turtle tell-turtle-s-state11864635
Ref: 3bff11864635
Ref: library/turtle turtle position11864696
Ref: 3ba811864696
Ref: library/turtle turtle pos11864727
Ref: 3ba911864727
Ref: library/turtle turtle towards11864895
Ref: 3baa11864895
Ref: library/turtle turtle xcor11865436
Ref: 3bab11865436
Ref: library/turtle turtle ycor11865712
Ref: 3bac11865712
Ref: library/turtle turtle heading11865995
Ref: 3bad11865995
Ref: library/turtle turtle distance11866239
Ref: 3bae11866239
Node: Settings for measurement11866818
Ref: library/turtle settings-for-measurement11866985
Ref: 3c0011866985
Ref: library/turtle turtle degrees11867056
Ref: 3baf11867056
Ref: library/turtle turtle radians11867672
Ref: 3bb011867672
Node: Pen control<2>11867995
Ref: library/turtle id111868155
Ref: 3c0111868155
Node: Drawing state11868283
Ref: library/turtle drawing-state11868369
Ref: 3c0211868369
Ref: library/turtle turtle pendown11868418
Ref: 3bb111868418
Ref: library/turtle turtle pd11868448
Ref: 3bb211868448
Ref: library/turtle turtle down11868473
Ref: 3bb311868473
Ref: library/turtle turtle penup11868548
Ref: 3bb411868548
Ref: library/turtle turtle pu11868576
Ref: 3bb511868576
Ref: library/turtle turtle up11868601
Ref: 3bb611868601
Ref: library/turtle turtle pensize11868675
Ref: 3bb711868675
Ref: library/turtle turtle width11868715
Ref: 3bb811868715
Ref: library/turtle turtle pen11869165
Ref: 3bb911869165
Ref: library/turtle turtle isdown11871007
Ref: 3bba11871007
Node: Color control11871253
Ref: library/turtle color-control11871355
Ref: 3c0311871355
Ref: library/turtle turtle pencolor11871404
Ref: 3bbc11871404
Ref: library/turtle turtle fillcolor11873006
Ref: 3bbd11873006
Ref: library/turtle turtle color11874516
Ref: 3bbb11874516
Node: Filling11875712
Ref: library/turtle filling11875821
Ref: 3c0411875821
Ref: library/turtle turtle filling11875858
Ref: 3bbe11875858
Ref: library/turtle turtle begin_fill11876115
Ref: 3bbf11876115
Ref: library/turtle turtle end_fill11876210
Ref: 3bc011876210
Node: More drawing control11876755
Ref: library/turtle more-drawing-control11876842
Ref: 3c0511876842
Ref: library/turtle turtle reset11876905
Ref: 3bc111876905
Ref: library/turtle turtle clear11877349
Ref: 3bc211877349
Ref: library/turtle turtle write11877549
Ref: 3bc311877549
Node: Turtle state11878292
Ref: library/turtle turtle-state11878440
Ref: 3c0611878440
Node: Visibility11878527
Ref: library/turtle visibility11878605
Ref: 3c0711878605
Ref: library/turtle turtle hideturtle11878648
Ref: 3bc611878648
Ref: library/turtle turtle ht11878681
Ref: 3bc711878681
Ref: library/turtle turtle showturtle11878932
Ref: 3bc411878932
Ref: library/turtle turtle st11878965
Ref: 3bc511878965
Ref: library/turtle turtle isvisible11879057
Ref: 3bc811879057
Node: Appearance11879332
Ref: library/turtle appearance11879410
Ref: 3c0811879410
Ref: library/turtle turtle shape11879453
Ref: 3bc911879453
Ref: library/turtle turtle resizemode11880092
Ref: 3bca11880092
Ref: library/turtle turtle shapesize11881017
Ref: 3bcb11881017
Ref: library/turtle turtle turtlesize11881107
Ref: 3bcc11881107
Ref: library/turtle turtle shearfactor11882068
Ref: 3bcd11882068
Ref: library/turtle turtle tilt11882722
Ref: 3bce11882722
Ref: library/turtle turtle tiltangle11883152
Ref: 6c911883152
Ref: library/turtle turtle shapetransform11883864
Ref: 3bcf11883864
Ref: library/turtle turtle get_shapepoly11884872
Ref: 3bd011884872
Node: Using events11885241
Ref: library/turtle using-events11885397
Ref: 3c0911885397
Ref: library/turtle turtle onrelease11886283
Ref: 3bd211886283
Ref: library/turtle turtle ondrag11887280
Ref: 3bd311887280
Node: Special Turtle methods11888141
Ref: library/turtle special-turtle-methods11888300
Ref: 3c0a11888300
Ref: library/turtle turtle begin_poly11888367
Ref: 3bd411888367
Ref: library/turtle turtle end_poly11888508
Ref: 3bd511888508
Ref: library/turtle turtle get_poly11888697
Ref: 3bd611888697
Ref: library/turtle turtle clone11889097
Ref: 3bd711889097
Ref: library/turtle turtle getturtle11889292
Ref: 3bd811889292
Ref: library/turtle turtle getpen11889324
Ref: 3bd911889324
Ref: library/turtle turtle getscreen11889586
Ref: 3bda11889586
Ref: library/turtle turtle setundobuffer11889890
Ref: 3bdb11889890
Ref: library/turtle turtle undobufferentries11890321
Ref: 3bdc11890321
Node: Compound shapes11890479
Ref: library/turtle compound-shapes11890617
Ref: 3c0c11890617
Ref: library/turtle compoundshapes11890617
Ref: 3c0d11890617
Node: Methods of TurtleScreen/Screen and corresponding functions11891650
Ref: library/turtle methods-of-turtlescreen-screen-and-corresponding-functions11891868
Ref: 3c1011891868
Node: Window control11892348
Ref: library/turtle window-control11892483
Ref: 3c1111892483
Ref: library/turtle turtle bgcolor11892534
Ref: 3bde11892534
Ref: library/turtle turtle bgpic11892939
Ref: 3bdf11892939
Ref: library/turtle turtle clearscreen11893807
Ref: 3be011893807
Ref: library/turtle turtle resetscreen11894314
Ref: 3be111894314
Ref: library/turtle turtle screensize11894411
Ref: 3be211894411
Ref: library/turtle turtle setworldcoordinates11895298
Ref: 3be311895298
Node: Animation control11896258
Ref: library/turtle animation-control11896421
Ref: 3c1211896421
Ref: library/turtle turtle delay11896478
Ref: 3be411896478
Ref: library/turtle turtle tracer11896909
Ref: 3be511896909
Ref: library/turtle turtle update11897600
Ref: 3be611897600
Node: Using screen events11897770
Ref: library/turtle using-screen-events11897932
Ref: 3c1311897932
Ref: library/turtle turtle listen11897993
Ref: 3be711897993
Ref: library/turtle turtle onkey11898226
Ref: 3be811898226
Ref: library/turtle turtle onkeyrelease11898262
Ref: 3be911898262
Ref: library/turtle turtle onkeypress11898866
Ref: 3bea11898866
Ref: library/turtle turtle onclick11899451
Ref: 3bd111899451
Ref: library/turtle turtle onscreenclick11899501
Ref: 3beb11899501
Ref: library/turtle turtle ontimer11900677
Ref: 3bec11900677
Ref: library/turtle turtle mainloop11901151
Ref: 3bed11901151
Ref: library/turtle turtle done11901182
Ref: 3bee11901182
Node: Input methods11901504
Ref: library/turtle input-methods11901677
Ref: 3c1411901677
Ref: library/turtle turtle textinput11901726
Ref: 17c511901726
Ref: library/turtle turtle numinput11902194
Ref: 17c611902194
Node: Settings and special methods11903125
Ref: library/turtle settings-and-special-methods11903337
Ref: 3c1511903337
Ref: library/turtle turtle mode11903416
Ref: 3bef11903416
Ref: library/turtle turtle colormode11904581
Ref: 3bf011904581
Ref: library/turtle turtle getcanvas11905213
Ref: 3bf111905213
Ref: library/turtle turtle getshapes11905462
Ref: 3bf211905462
Ref: library/turtle turtle register_shape11905654
Ref: 3bf311905654
Ref: library/turtle turtle addshape11905707
Ref: 3bf411905707
Ref: library/turtle turtle turtles11906666
Ref: 3bf511906666
Ref: library/turtle turtle window_height11906830
Ref: 3bf611906830
Ref: library/turtle turtle window_width11906965
Ref: 3bf711906965
Node: Methods specific to Screen not inherited from TurtleScreen11907097
Ref: library/turtle methods-specific-to-screen-not-inherited-from-turtlescreen11907287
Ref: 3c1611907287
Ref: library/turtle screenspecific11907287
Ref: 3c1711907287
Ref: library/turtle turtle bye11907428
Ref: 3bf811907428
Ref: library/turtle turtle exitonclick11907493
Ref: 3bf911907493
Ref: library/turtle turtle setup11907925
Ref: 3bfa11907925
Ref: library/turtle turtle title11909231
Ref: 3bfb11909231
Node: Public classes11909489
Ref: library/turtle public-classes11909661
Ref: 3c1811909661
Ref: library/turtle turtle RawTurtle11909712
Ref: 3c1911909712
Ref: library/turtle turtle RawPen11909750
Ref: 3c1a11909750
Ref: library/turtle turtle Turtle11910012
Ref: 3c1c11910012
Ref: library/turtle turtle TurtleScreen11910205
Ref: 3c0b11910205
Ref: library/turtle turtle Screen11910395
Ref: 3b8e11910395
Ref: library/turtle turtle ScrolledCanvas11910491
Ref: 3c1b11910491
Ref: library/turtle turtle Shape11910781
Ref: 3c0e11910781
Ref: library/turtle turtle Shape addcomponent11911555
Ref: 3c0f11911555
Ref: library/turtle turtle Vec2D11912149
Ref: 3bfe11912149
Node: 解釋<2>11912679
Ref: library/turtle explanation11912815
Ref: 3c1d11912815
Ref: library/turtle turtle-explanation11912815
Ref: 3b8d11912815
Node: Help and configuration11914231
Ref: library/turtle help-and-configuration11914380
Ref: 3c1e11914380
Node: How to use help11914572
Ref: library/turtle how-to-use-help11914705
Ref: 3c1f11914705
Node: Translation of docstrings into different languages11917023
Ref: library/turtle translation-of-docstrings-into-different-languages11917200
Ref: 3c2011917200
Ref: library/turtle turtle write_docstringdict11917504
Ref: 3c2111917504
Node: How to configure Screen and Turtles11918524
Ref: library/turtle how-to-configure-screen-and-turtles11918677
Ref: 3c2211918677
Node: turtledemo --- Demo scripts11921478
Ref: library/turtle module-turtledemo11921642
Ref: eb11921642
Ref: library/turtle turtledemo-demo-scripts11921642
Ref: 3c2311921642
Node: Changes since Python 2 611927473
Ref: library/turtle changes-since-python-2-611927639
Ref: 3c2411927639
Node: Changes since Python 3 011928677
Ref: library/turtle changes-since-python-3-011928807
Ref: 3c2511928807
Node: cmd --- 以列為導向的指令直譯器支援11930061
Ref: library/cmd doc11930242
Ref: 3c2611930242
Ref: library/cmd cmd-support-for-line-oriented-command-interpreters11930242
Ref: 3c2711930242
Ref: library/cmd module-cmd11930242
Ref: 1211930242
Ref: library/cmd cmd Cmd11930690
Ref: 15c011930690
Ref: cmd --- 以列為導向的指令直譯器支援-Footnote-111932349
Node: Cmd 物件11932412
Ref: library/cmd cmd-objects11932526
Ref: 3c2911932526
Ref: library/cmd id111932526
Ref: 3c2a11932526
Ref: library/cmd cmd Cmd cmdloop11932621
Ref: 3c2b11932621
Ref: library/cmd cmd Cmd do_help11934686
Ref: 15ac11934686
Ref: library/cmd cmd Cmd onecmd11935219
Ref: 3c2e11935219
Ref: library/cmd cmd Cmd emptyline11935810
Ref: 3c3111935810
Ref: library/cmd cmd Cmd default11936008
Ref: 3c3011936008
Ref: library/cmd cmd Cmd completedefault11936205
Ref: 3c3211936205
Ref: library/cmd cmd Cmd columnize11936427
Ref: 176911936427
Ref: library/cmd cmd Cmd precmd11936663
Ref: 3c2f11936663
Ref: library/cmd cmd Cmd postcmd11937142
Ref: 3c2d11937142
Ref: library/cmd cmd Cmd preloop11937775
Ref: 3c3311937775
Ref: library/cmd cmd Cmd postloop11937969
Ref: 3c3411937969
Ref: library/cmd cmd Cmd prompt11938253
Ref: 3c3511938253
Ref: library/cmd cmd Cmd identchars11938319
Ref: 3c3611938319
Ref: library/cmd cmd Cmd lastcmd11938411
Ref: 3c3711938411
Ref: library/cmd cmd Cmd cmdqueue11938481
Ref: 3c3811938481
Ref: library/cmd cmd Cmd intro11938729
Ref: 3c2c11938729
Ref: library/cmd cmd Cmd doc_header11938880
Ref: 3c3911938880
Ref: library/cmd cmd Cmd misc_header11938997
Ref: 3c3a11938997
Ref: library/cmd cmd Cmd undoc_header11939213
Ref: 3c3b11939213
Ref: library/cmd cmd Cmd ruler11939426
Ref: 3c3c11939426
Ref: library/cmd cmd Cmd use_rawinput11939597
Ref: 3c2811939597
Node: Cmd Example11940070
Ref: library/cmd cmd-example11940184
Ref: 3c3d11940184
Ref: library/cmd id211940184
Ref: 3c3e11940184
Node: shlex --- 簡單的語法分析11945533
Ref: library/shlex doc11945669
Ref: 3c3f11945669
Ref: library/shlex module-shlex11945669
Ref: b211945669
Ref: library/shlex shlex-simple-lexical-analysis11945669
Ref: 3c4011945669
Ref: library/shlex shlex split11946178
Ref: 4e111946178
Ref: library/shlex shlex join11946771
Ref: 9cb11946771
Ref: library/shlex shlex quote11947228
Ref: 10c411947228
Ref: library/shlex shlex-quote-warning11947454
Ref: 304c11947454
Ref: library/shlex shlex shlex11949080
Ref: c7411949080
Ref: shlex --- 簡單的語法分析-Footnote-111951304
Node: shlex 物件11951369
Ref: library/shlex id111951471
Ref: 3c4411951471
Ref: library/shlex shlex-objects11951471
Ref: 3c4511951471
Ref: library/shlex shlex shlex get_token11951571
Ref: 3c4611951571
Ref: library/shlex shlex shlex push_token11951934
Ref: 3c4711951934
Ref: library/shlex shlex shlex read_token11952016
Ref: 3c4911952016
Ref: library/shlex shlex shlex sourcehook11952255
Ref: 3c4a11952255
Ref: library/shlex shlex shlex push_source11953790
Ref: 3c4c11953790
Ref: library/shlex shlex shlex pop_source11954093
Ref: 3c4d11954093
Ref: library/shlex shlex shlex error_leader11954292
Ref: 3c4e11954292
Ref: library/shlex shlex shlex commenters11955021
Ref: 3c4111955021
Ref: library/shlex shlex shlex wordchars11955240
Ref: 3c4311955240
Ref: library/shlex shlex shlex whitespace11955933
Ref: 3c5011955933
Ref: library/shlex shlex shlex escape11956128
Ref: 3c5111956128
Ref: library/shlex shlex shlex quotes11956290
Ref: 3c5211956290
Ref: library/shlex shlex shlex escapedquotes11956572
Ref: 3c5311956572
Ref: library/shlex shlex shlex whitespace_split11956798
Ref: 3c4f11956798
Ref: library/shlex shlex shlex infile11957326
Ref: 3c4211957326
Ref: library/shlex shlex shlex instream11957554
Ref: 3c5411957554
Ref: library/shlex shlex shlex source11957676
Ref: 3c4b11957676
Ref: library/shlex shlex shlex debug11958262
Ref: 3c5511958262
Ref: library/shlex shlex shlex lineno11958523
Ref: 3c5611958523
Ref: library/shlex shlex shlex token11958616
Ref: 3c5711958616
Ref: library/shlex shlex shlex eof11958730
Ref: 3c4811958730
Ref: library/shlex shlex shlex punctuation_chars11958903
Ref: 18d611958903
Node: Parsing Rules11959307
Ref: library/shlex parsing-rules11959452
Ref: 3c5811959452
Ref: library/shlex shlex-parsing-rules11959452
Ref: 3c5911959452
Node: Improved Compatibility with Shells11961471
Ref: library/shlex improved-compatibility-with-shells11961595
Ref: 3c5a11961595
Ref: library/shlex improved-shell-compatibility11961595
Ref: c7511961595
Node: 以 Tk 打造圖形使用者介面 Graphical User Interfaces11964430
Ref: library/tk doc11964608
Ref: 3c5b11964608
Ref: library/tk graphical-user-interfaces-with-tk11964608
Ref: 3c5c11964608
Ref: library/tk tkinter11964608
Ref: 3c5d11964608
Ref: 以 Tk 打造圖形使用者介面 Graphical User Interfaces-Footnote-111966380
Node: tkinter --- Tcl/Tk 的 Python 介面11966432
Ref: library/tkinter doc11966620
Ref: 3c5e11966620
Ref: library/tkinter module-tkinter11966620
Ref: d911966620
Ref: library/tkinter tkinter-python-interface-to-tcl-tk11966620
Ref: 3c5f11966620
Ref: tkinter --- Tcl/Tk 的 Python 介面-Footnote-111969527
Ref: tkinter --- Tcl/Tk 的 Python 介面-Footnote-211969604
Ref: tkinter --- Tcl/Tk 的 Python 介面-Footnote-311969632
Ref: tkinter --- Tcl/Tk 的 Python 介面-Footnote-411969672
Ref: tkinter --- Tcl/Tk 的 Python 介面-Footnote-511969729
Ref: tkinter --- Tcl/Tk 的 Python 介面-Footnote-611969756
Ref: tkinter --- Tcl/Tk 的 Python 介面-Footnote-711969793
Ref: tkinter --- Tcl/Tk 的 Python 介面-Footnote-811969885
Ref: tkinter --- Tcl/Tk 的 Python 介面-Footnote-911969937
Node: Architecture11969996
Ref: library/tkinter architecture11970105
Ref: 3c6011970105
Ref: Architecture-Footnote-111972429
Node: Tkinter Modules11972469
Ref: library/tkinter tkinter-modules11972609
Ref: 3c6211972609
Ref: library/tkinter tkinter Tk11972936
Ref: 152a11972936
Ref: library/tkinter tkinter Tk tk11975083
Ref: 3c6411975083
Ref: library/tkinter tkinter Tk master11975379
Ref: 3c6511975379
Ref: library/tkinter tkinter Tk children11975946
Ref: 3c6611975946
Ref: library/tkinter tkinter Tcl11976153
Ref: 3c6311976153
Ref: library/tkinter module-_tkinter11977754
Ref: 311977754
Node: Tkinter Life Preserver11978663
Ref: library/tkinter tkinter-life-preserver11978806
Ref: 3c6711978806
Node: A Hello World Program11979662
Ref: library/tkinter a-hello-world-program11979772
Ref: 3c6811979772
Node: Important Tk Concepts11981225
Ref: library/tkinter important-tk-concepts11981382
Ref: 3c6911981382
Node: Understanding How Tkinter Wraps Tcl/Tk11982724
Ref: library/tkinter understanding-how-tkinter-wraps-tcl-tk11982889
Ref: 3c6a11982889
Node: How do I ? What option does ?11985030
Ref: library/tkinter how-do-i-what-option-does11985212
Ref: 3c6b11985212
Node: Navigating the Tcl/Tk Reference Manual11986950
Ref: library/tkinter navigating-the-tcl-tk-reference-manual11987085
Ref: 3c6c11987085
Ref: Navigating the Tcl/Tk Reference Manual-Footnote-111989151
Ref: Navigating the Tcl/Tk Reference Manual-Footnote-211989208
Ref: Navigating the Tcl/Tk Reference Manual-Footnote-311989267
Ref: Navigating the Tcl/Tk Reference Manual-Footnote-411989320
Ref: Navigating the Tcl/Tk Reference Manual-Footnote-511989376
Ref: Navigating the Tcl/Tk Reference Manual-Footnote-611989435
Node: Threading model11989489
Ref: library/tkinter threading-model11989632
Ref: 3c6111989632
Node: Handy Reference11992644
Ref: library/tkinter handy-reference11992778
Ref: 3c6d11992778
Node: Setting Options11993032
Ref: library/tkinter setting-options11993118
Ref: 3c6e11993118
Ref: library/tkinter tkinter-setting-options11993118
Ref: 3c6f11993118
Ref: Setting Options-Footnote-111996348
Node: The Packer11996395
Ref: library/tkinter the-packer11996504
Ref: 3c7011996504
Node: Packer Options11998144
Ref: library/tkinter packer-options11998263
Ref: 3c7111998263
Node: Coupling Widget Variables11998961
Ref: library/tkinter coupling-widget-variables11999088
Ref: 3c7211999088
Node: The Window Manager12001289
Ref: library/tkinter the-window-manager12001422
Ref: 3c7312001422
Node: Tk Option Data Types12002807
Ref: library/tkinter tk-option-data-types12002934
Ref: 3c7412002934
Node: Bindings and Events12005990
Ref: library/tkinter bindings-and-events12006118
Ref: 3c7512006118
Ref: library/tkinter id212006118
Ref: 3c7612006118
Ref: Bindings and Events-Footnote-112008963
Node: The index Parameter12009009
Ref: library/tkinter the-index-parameter12009123
Ref: 3c7712009123
Node: Images12011051
Ref: library/tkinter images12011137
Ref: 3c7812011137
Ref: Images-Footnote-112012432
Node: File Handlers12012467
Ref: library/tkinter file-handlers12012577
Ref: 3c7912012577
Ref: library/tkinter tkinter-file-handlers12012577
Ref: 3c7a12012577
Ref: library/tkinter tkinter Widget tk createfilehandler12013517
Ref: 3c7b12013517
Ref: library/tkinter tkinter Widget tk deletefilehandler12013952
Ref: 3c7c12013952
Ref: library/tkinter tkinter READABLE12014034
Ref: 3c7d12014034
Ref: library/tkinter tkinter WRITABLE12014064
Ref: 3c7e12014064
Ref: library/tkinter tkinter EXCEPTION12014094
Ref: 3c7f12014094
Node: tkinter colorchooser --- 顏色選擇對話框12014172
Ref: library/tkinter colorchooser doc12014409
Ref: 3c8012014409
Ref: library/tkinter colorchooser module-tkinter colorchooser12014409
Ref: da12014409
Ref: library/tkinter colorchooser tkinter-colorchooser-color-choosing-dialog12014409
Ref: 3c8112014409
Ref: library/tkinter colorchooser tkinter colorchooser Chooser12014875
Ref: 3c8212014875
Ref: library/tkinter colorchooser tkinter colorchooser askcolor12014942
Ref: 3c8412014942
Ref: tkinter colorchooser --- 顏色選擇對話框-Footnote-112015328
Node: tkinter font --- Tkinter 字型包裝器12015409
Ref: library/tkinter font doc12015627
Ref: 3c8512015627
Ref: library/tkinter font module-tkinter font12015627
Ref: de12015627
Ref: library/tkinter font tkinter-font-tkinter-font-wrapper12015627
Ref: 3c8612015627
Ref: library/tkinter font tkinter font NORMAL12015999
Ref: 3c8712015999
Ref: library/tkinter font tkinter font BOLD12016031
Ref: 3c8812016031
Ref: library/tkinter font tkinter font ITALIC12016061
Ref: 3c8912016061
Ref: library/tkinter font tkinter font ROMAN12016093
Ref: 3c8a12016093
Ref: library/tkinter font tkinter font Font12016125
Ref: 180d12016125
Ref: library/tkinter font tkinter font Font actual12017575
Ref: 3c8b12017575
Ref: library/tkinter font tkinter font Font cget12017666
Ref: 3c8c12017666
Ref: library/tkinter font tkinter font Font config12017746
Ref: 3c8d12017746
Ref: library/tkinter font tkinter font Font copy12017825
Ref: 3c8e12017825
Ref: library/tkinter font tkinter font Font measure12017896
Ref: 3c8f12017896
Ref: library/tkinter font tkinter font Font metrics12018130
Ref: 3c9012018130
Ref: library/tkinter font tkinter font families12018704
Ref: 3c9112018704
Ref: library/tkinter font tkinter font names12018804
Ref: 3c9212018804
Ref: library/tkinter font tkinter font nametofont12018888
Ref: 180f12018888
Ref: tkinter font --- Tkinter 字型包裝器-Footnote-112019106
Node: Tkinter 對話框12019178
Ref: library/dialog doc12019393
Ref: 3c9312019393
Ref: library/dialog tkinter-dialogs12019393
Ref: 3c9412019393
Node: tkinter simpledialog --- 標準 Tkinter 輸入對話框12019753
Ref: library/dialog module-tkinter simpledialog12019916
Ref: e112019916
Ref: library/dialog tkinter-simpledialog-standard-tkinter-input-dialogs12019916
Ref: 3c9512019916
Ref: library/dialog tkinter simpledialog askfloat12020311
Ref: 3c9612020311
Ref: library/dialog tkinter simpledialog askinteger12020375
Ref: 181012020375
Ref: library/dialog tkinter simpledialog askstring12020441
Ref: 3c9712020441
Ref: library/dialog tkinter simpledialog Dialog12020619
Ref: 3c9812020619
Ref: library/dialog tkinter simpledialog Dialog body12020722
Ref: 3c9912020722
Ref: library/dialog tkinter simpledialog Dialog buttonbox12020874
Ref: 3c9a12020874
Ref: tkinter simpledialog --- 標準 Tkinter 輸入對話框-Footnote-112021045
Node: tkinter filedialog --- File selection dialogs12021126
Ref: library/dialog module-tkinter filedialog12021346
Ref: dd12021346
Ref: library/dialog tkinter-filedialog-file-selection-dialogs12021346
Ref: 3c9b12021346
Ref: tkinter filedialog --- File selection dialogs-Footnote-112021778
Node: Native Load/Save Dialogs12021857
Ref: library/dialog native-load-save-dialogs12021963
Ref: 3c9c12021963
Ref: library/dialog tkinter filedialog askopenfile12022966
Ref: 3c9d12022966
Ref: library/dialog tkinter filedialog askopenfiles12023031
Ref: 3c9e12023031
Ref: library/dialog tkinter filedialog asksaveasfile12023224
Ref: 3ca012023224
Ref: library/dialog tkinter filedialog askopenfilename12023391
Ref: 3ca212023391
Ref: library/dialog tkinter filedialog askopenfilenames12023450
Ref: 3ca312023450
Ref: library/dialog tkinter filedialog asksaveasfilename12023659
Ref: 3ca412023659
Ref: library/dialog tkinter filedialog askdirectory12023802
Ref: 3ca512023802
Ref: library/dialog tkinter filedialog Open12024026
Ref: 3c9f12024026
Ref: library/dialog tkinter filedialog SaveAs12024087
Ref: 3ca112024087
Ref: library/dialog tkinter filedialog Directory12024409
Ref: 3ca612024409
Ref: library/dialog tkinter filedialog FileDialog12024644
Ref: 3ca712024644
Ref: library/dialog tkinter filedialog FileDialog cancel_command12024752
Ref: 3ca812024752
Ref: library/dialog tkinter filedialog FileDialog dirs_double_event12024855
Ref: 3ca912024855
Ref: library/dialog tkinter filedialog FileDialog dirs_select_event12024961
Ref: 3caa12024961
Ref: library/dialog tkinter filedialog FileDialog files_double_event12025060
Ref: 3cab12025060
Ref: library/dialog tkinter filedialog FileDialog files_select_event12025162
Ref: 3cac12025162
Ref: library/dialog tkinter filedialog FileDialog filter_command12025264
Ref: 3cad12025264
Ref: library/dialog tkinter filedialog FileDialog get_filter12025352
Ref: 3cae12025352
Ref: library/dialog tkinter filedialog FileDialog get_selection12025438
Ref: 3caf12025438
Ref: library/dialog tkinter filedialog FileDialog go12025522
Ref: 3cb012025522
Ref: library/dialog tkinter filedialog FileDialog ok_event12025664
Ref: 3cb112025664
Ref: library/dialog tkinter filedialog FileDialog quit12025751
Ref: 3cb212025751
Ref: library/dialog tkinter filedialog FileDialog set_filter12025836
Ref: 3cb312025836
Ref: library/dialog tkinter filedialog FileDialog set_selection12025908
Ref: 3cb412025908
Ref: library/dialog tkinter filedialog LoadFileDialog12026003
Ref: 3cb512026003
Ref: library/dialog tkinter filedialog LoadFileDialog ok_command12026168
Ref: 3cb612026168
Ref: library/dialog tkinter filedialog SaveFileDialog12026309
Ref: 3cb712026309
Ref: library/dialog tkinter filedialog SaveFileDialog ok_command12026476
Ref: 3cb812026476
Node: tkinter commondialog --- Dialog window templates12026688
Ref: library/dialog module-tkinter commondialog12026844
Ref: db12026844
Ref: library/dialog tkinter-commondialog-dialog-window-templates12026844
Ref: 3cb912026844
Ref: library/dialog tkinter commondialog Dialog12027236
Ref: 3c8312027236
Ref: library/dialog tkinter commondialog Dialog show12027302
Ref: 3cba12027302
Ref: tkinter commondialog --- Dialog window templates-Footnote-112027506
Node: tkinter messagebox --- Tkinter 訊息提示12027587
Ref: library/tkinter messagebox doc12027808
Ref: 3cbb12027808
Ref: library/tkinter messagebox module-tkinter messagebox12027808
Ref: df12027808
Ref: library/tkinter messagebox tkinter-messagebox-tkinter-message-prompts12027808
Ref: 3cbc12027808
Ref: library/tkinter messagebox tkinter messagebox Message12028481
Ref: 3cc112028481
Ref: library/tkinter messagebox tkinter messagebox Message show12030297
Ref: 3cc612030297
Ref: library/tkinter messagebox tkinter messagebox showinfo12030539
Ref: 3cc712030539
Ref: library/tkinter messagebox tkinter messagebox showwarning12030717
Ref: 3cc812030717
Ref: library/tkinter messagebox tkinter messagebox showerror12030879
Ref: 3cc912030879
Ref: library/tkinter messagebox tkinter messagebox askquestion12031058
Ref: 3cca12031058
Ref: library/tkinter messagebox tkinter messagebox askokcancel12031290
Ref: 3ccb12031290
Ref: library/tkinter messagebox tkinter messagebox askretrycancel12031550
Ref: 3ccc12031550
Ref: library/tkinter messagebox tkinter messagebox askyesno12031816
Ref: 3cce12031816
Ref: library/tkinter messagebox tkinter messagebox askyesnocancel12032059
Ref: 3ccf12032059
Ref: library/tkinter messagebox messagebox-buttons12032369
Ref: 3cc212032369
Ref: library/tkinter messagebox tkinter messagebox ABORT12032395
Ref: 3cd012032395
Ref: library/tkinter messagebox tkinter messagebox RETRY12032443
Ref: 3ccd12032443
Ref: library/tkinter messagebox tkinter messagebox IGNORE12032491
Ref: 3cd112032491
Ref: library/tkinter messagebox tkinter messagebox OK12032541
Ref: 3cbd12032541
Ref: library/tkinter messagebox tkinter messagebox CANCEL12032583
Ref: 3cbe12032583
Ref: library/tkinter messagebox tkinter messagebox YES12032633
Ref: 3cbf12032633
Ref: library/tkinter messagebox tkinter messagebox NO12032677
Ref: 3cc012032677
Ref: library/tkinter messagebox messagebox-types12032718
Ref: 3cc512032718
Ref: library/tkinter messagebox tkinter messagebox ABORTRETRYIGNORE12032750
Ref: 3cd212032750
Ref: library/tkinter messagebox tkinter messagebox OKCANCEL12033045
Ref: 3cd312033045
Ref: library/tkinter messagebox tkinter messagebox RETRYCANCEL12033188
Ref: 3cd412033188
Ref: library/tkinter messagebox tkinter messagebox YESNO12033345
Ref: 3cd512033345
Ref: library/tkinter messagebox tkinter messagebox YESNOCANCEL12033479
Ref: 3cd612033479
Ref: library/tkinter messagebox messagebox-icons12033651
Ref: 3cc312033651
Ref: library/tkinter messagebox tkinter messagebox ERROR12033668
Ref: 3cd712033668
Ref: library/tkinter messagebox tkinter messagebox INFO12033716
Ref: 3cc412033716
Ref: library/tkinter messagebox tkinter messagebox QUESTION12033762
Ref: 3cd812033762
Ref: library/tkinter messagebox tkinter messagebox WARNING12033816
Ref: 3cd912033816
Ref: tkinter messagebox --- Tkinter 訊息提示-Footnote-112033904
Node: tkinter scrolledtext --- 捲動文字小工具12033983
Ref: library/tkinter scrolledtext doc12034215
Ref: 3cda12034215
Ref: library/tkinter scrolledtext module-tkinter scrolledtext12034215
Ref: e012034215
Ref: library/tkinter scrolledtext tkinter-scrolledtext-scrolled-text-widget12034215
Ref: 3cdb12034215
Ref: library/tkinter scrolledtext tkinter scrolledtext ScrolledText12035119
Ref: 3cdc12035119
Ref: library/tkinter scrolledtext tkinter scrolledtext ScrolledText frame12035186
Ref: 3cdd12035186
Ref: library/tkinter scrolledtext tkinter scrolledtext ScrolledText vbar12035280
Ref: 3cde12035280
Ref: tkinter scrolledtext --- 捲動文字小工具-Footnote-112035373
Node: tkinter dnd --- 拖放支援12035454
Ref: library/tkinter dnd doc12035680
Ref: 3cdf12035680
Ref: library/tkinter dnd module-tkinter dnd12035680
Ref: dc12035680
Ref: library/tkinter dnd tkinter-dnd-drag-and-drop-support12035680
Ref: 3ce012035680
Ref: library/tkinter dnd tkinter dnd DndHandler12037154
Ref: 3ce212037154
Ref: library/tkinter dnd tkinter dnd DndHandler cancel12037343
Ref: 3ce312037343
Ref: library/tkinter dnd tkinter dnd DndHandler finish12037426
Ref: 3ce412037426
Ref: library/tkinter dnd tkinter dnd DndHandler on_motion12037520
Ref: 3ce512037520
Ref: library/tkinter dnd tkinter dnd DndHandler on_release12037646
Ref: 3ce612037646
Ref: library/tkinter dnd tkinter dnd dnd_start12037752
Ref: 3ce112037752
Ref: tkinter dnd --- 拖放支援-Footnote-112037941
Node: tkinter ttk --- Tk 主題化小工具12038012
Ref: library/tkinter ttk doc12038200
Ref: 3ce712038200
Ref: library/tkinter ttk module-tkinter ttk12038200
Ref: e212038200
Ref: library/tkinter ttk tkinter-ttk-tk-themed-widgets12038200
Ref: 3ce812038200
Ref: tkinter ttk --- Tk 主題化小工具-Footnote-112039118
Ref: tkinter ttk --- Tk 主題化小工具-Footnote-212039189
Node: 使用 Ttk12039242
Ref: library/tkinter ttk using-ttk12039346
Ref: 3ce912039346
Ref: 使用 Ttk-Footnote-112040493
Node: Ttk Widgets12040557
Ref: library/tkinter ttk ttk-widgets12040676
Ref: 3cea12040676
Node: Widget12041784
Ref: library/tkinter ttk widget12041901
Ref: 3cf012041901
Node: 標準選項12042208
Ref: library/tkinter ttk standard-options12042297
Ref: 3cf112042297
Node: Scrollable Widget Options12043819
Ref: library/tkinter ttk scrollable-widget-options12043930
Ref: 3cf212043930
Node: Label Options12044958
Ref: library/tkinter ttk label-options12045072
Ref: 3cf312045072
Node: 相容性選項12047403
Ref: library/tkinter ttk compatibility-options12047505
Ref: 3cf412047505
Node: Widget States12047964
Ref: library/tkinter ttk widget-states12048063
Ref: 3cf612048063
Node: ttk Widget12049546
Ref: library/tkinter ttk ttk-widget12049621
Ref: 3cf712049621
Ref: library/tkinter ttk tkinter ttk Widget12049808
Ref: 3cee12049808
Ref: library/tkinter ttk tkinter ttk Widget identify12049840
Ref: 3cf812049840
Ref: library/tkinter ttk tkinter ttk Widget instate12050083
Ref: 3cf912050083
Ref: library/tkinter ttk tkinter ttk Widget state12050425
Ref: 3cf512050425
Node: Combobox12050813
Ref: library/tkinter ttk combobox12050926
Ref: 3cfa12050926
Node: 選項12051620
Ref: library/tkinter ttk options12051694
Ref: 3cfb12051694
Node: Virtual events12053940
Ref: library/tkinter ttk virtual-events12054035
Ref: 3cfc12054035
Node: ttk Combobox12054215
Ref: library/tkinter ttk ttk-combobox12054295
Ref: 3cfd12054295
Ref: library/tkinter ttk tkinter ttk Combobox12054342
Ref: 3ceb12054342
Ref: library/tkinter ttk tkinter ttk Combobox current12054376
Ref: 3cfe12054376
Ref: library/tkinter ttk tkinter ttk Combobox get12054652
Ref: 3cff12054652
Ref: library/tkinter ttk tkinter ttk Combobox set12054731
Ref: 3d0012054731
Node: Spinbox12054815
Ref: library/tkinter ttk spinbox12054930
Ref: 3d0112054930
Node: 選項<2>12055688
Ref: library/tkinter ttk id112055767
Ref: 3d0212055767
Node: Virtual events<2>12058134
Ref: library/tkinter ttk id212058233
Ref: 3d0312058233
Node: ttk Spinbox12058441
Ref: library/tkinter ttk ttk-spinbox12058522
Ref: 3d0412058522
Ref: library/tkinter ttk tkinter ttk Spinbox12058567
Ref: b3b12058567
Ref: library/tkinter ttk tkinter ttk Spinbox get12058600
Ref: 3d0512058600
Ref: library/tkinter ttk tkinter ttk Spinbox set12058678
Ref: 3d0612058678
Node: Notebook12058761
Ref: library/tkinter ttk notebook12058879
Ref: 3d0712058879
Node: 選項<3>12059235
Ref: library/tkinter ttk id312059309
Ref: 3d0812059309
Node: Tab Options12060377
Ref: library/tkinter ttk tab-options12060475
Ref: 3d0912060475
Node: Tab Identifiers12062321
Ref: library/tkinter ttk tab-identifiers12062422
Ref: 3d0b12062422
Node: 虛擬事件12062944
Ref: library/tkinter ttk id412063046
Ref: 3d0d12063046
Node: ttk Notebook12063182
Ref: library/tkinter ttk ttk-notebook12063260
Ref: 3d0e12063260
Ref: library/tkinter ttk tkinter ttk Notebook12063307
Ref: 3cec12063307
Ref: library/tkinter ttk tkinter ttk Notebook add12063341
Ref: 3d0f12063341
Ref: library/tkinter ttk tkinter ttk Notebook forget12063608
Ref: 3d1012063608
Ref: library/tkinter ttk tkinter ttk Notebook hide12063746
Ref: 3d1112063746
Ref: library/tkinter ttk tkinter ttk Notebook identify12064056
Ref: 3d1212064056
Ref: library/tkinter ttk tkinter ttk Notebook index12064198
Ref: 3d0c12064198
Ref: library/tkinter ttk tkinter ttk Notebook insert12064373
Ref: 3d1312064373
Ref: library/tkinter ttk tkinter ttk Notebook select12064736
Ref: 3d1412064736
Ref: library/tkinter ttk tkinter ttk Notebook tab12065050
Ref: 3d1512065050
Ref: library/tkinter ttk tkinter ttk Notebook tabs12065396
Ref: 3d1612065396
Ref: library/tkinter ttk tkinter ttk Notebook enable_traversal12065484
Ref: 3d0a12065484
Node: Progressbar12066311
Ref: library/tkinter ttk progressbar12066431
Ref: 3d1712066431
Node: 選項<4>12066870
Ref: library/tkinter ttk id512066951
Ref: 3d1812066951
Node: ttk Progressbar12068622
Ref: library/tkinter ttk ttk-progressbar12068703
Ref: 3d1912068703
Ref: library/tkinter ttk tkinter ttk Progressbar12068756
Ref: 3ced12068756
Ref: library/tkinter ttk tkinter ttk Progressbar start12068793
Ref: 3d1a12068793
Ref: library/tkinter ttk tkinter ttk Progressbar step12069061
Ref: 3d1b12069061
Ref: library/tkinter ttk tkinter ttk Progressbar stop12069206
Ref: 3d1c12069206
Node: Separator12069391
Ref: library/tkinter ttk separator12069511
Ref: 3d1d12069511
Node: 選項<5>12069739
Ref: library/tkinter ttk id612069794
Ref: 3d1e12069794
Node: Sizegrip12070133
Ref: library/tkinter ttk sizegrip12070250
Ref: 3d1f12070250
Node: Platform-specific notes12070600
Ref: library/tkinter ttk platform-specific-notes12070681
Ref: 3d2012070681
Node: Bugs12070937
Ref: library/tkinter ttk bugs12071018
Ref: 3d2112071018
Node: Treeview12071285
Ref: library/tkinter ttk treeview12071404
Ref: 3d2212071404
Node: 選項<6>12072756
Ref: library/tkinter ttk id712072831
Ref: 3d2612072831
Node: Item Options12075204
Ref: library/tkinter ttk item-options12075299
Ref: 3d2712075299
Node: Tag Options12076350
Ref: library/tkinter ttk tag-options12076454
Ref: 3d2812076454
Node: Column Identifiers12077099
Ref: library/tkinter ttk column-identifiers12077206
Ref: 3d2312077206
Node: 虛擬事件<2>12078073
Ref: library/tkinter ttk id812078181
Ref: 3d2912078181
Node: ttk Treeview12079002
Ref: library/tkinter ttk ttk-treeview12079083
Ref: 3d2b12079083
Ref: library/tkinter ttk tkinter ttk Treeview12079130
Ref: a3712079130
Ref: library/tkinter ttk tkinter ttk Treeview bbox12079164
Ref: 3d2c12079164
Ref: library/tkinter ttk tkinter ttk Treeview get_children12079599
Ref: 3d2d12079599
Ref: library/tkinter ttk tkinter ttk Treeview set_children12079765
Ref: 3d2e12079765
Ref: library/tkinter ttk tkinter ttk Treeview column12080151
Ref: 3d2f12080151
Ref: library/tkinter ttk tkinter ttk Treeview delete12081375
Ref: 3d3012081375
Ref: library/tkinter ttk tkinter ttk Treeview detach12081521
Ref: 3d3112081521
Ref: library/tkinter ttk tkinter ttk Treeview exists12081832
Ref: 3d3212081832
Ref: library/tkinter ttk tkinter ttk Treeview focus12081942
Ref: 3d2a12081942
Ref: library/tkinter ttk tkinter ttk Treeview heading12082131
Ref: 3d3312082131
Ref: library/tkinter ttk tkinter ttk Treeview identify12083114
Ref: 3d3412083114
Ref: library/tkinter ttk tkinter ttk Treeview identify_row12083351
Ref: 3d3512083351
Ref: library/tkinter ttk tkinter ttk Treeview identify_column12083446
Ref: 3d3612083446
Ref: library/tkinter ttk tkinter ttk Treeview identify_region12083607
Ref: 3d3712083607
Ref: library/tkinter ttk tkinter ttk Treeview identify_element12084243
Ref: 3d3812084243
Ref: library/tkinter ttk tkinter ttk Treeview index12084371
Ref: 3d3912084371
Ref: library/tkinter ttk tkinter ttk Treeview insert12084497
Ref: 3d3a12084497
Ref: library/tkinter ttk tkinter ttk Treeview item12085371
Ref: 3d3b12085371
Ref: library/tkinter ttk tkinter ttk Treeview move12085749
Ref: 3d3c12085749
Ref: library/tkinter ttk tkinter ttk Treeview next12086184
Ref: 3d3d12086184
Ref: library/tkinter ttk tkinter ttk Treeview parent12086332
Ref: 3d3e12086332
Ref: library/tkinter ttk tkinter ttk Treeview prev12086479
Ref: 3d3f12086479
Ref: library/tkinter ttk tkinter ttk Treeview reattach12086632
Ref: 3d4012086632
Ref: library/tkinter ttk tkinter ttk Treeview see12086741
Ref: 3d4112086741
Ref: library/tkinter ttk tkinter ttk Treeview selection12086993
Ref: a3612086993
Ref: library/tkinter ttk tkinter ttk Treeview selection_set12087239
Ref: a3812087239
Ref: library/tkinter ttk tkinter ttk Treeview selection_add12087442
Ref: 3d4212087442
Ref: library/tkinter ttk tkinter ttk Treeview selection_remove12087638
Ref: 3d4312087638
Ref: library/tkinter ttk tkinter ttk Treeview selection_toggle12087839
Ref: 3d4412087839
Ref: library/tkinter ttk tkinter ttk Treeview set12088062
Ref: 3d4512088062
Ref: library/tkinter ttk tkinter ttk Treeview tag_bind12088427
Ref: 3d4612088427
Ref: library/tkinter ttk tkinter ttk Treeview tag_configure12088695
Ref: 3d4712088695
Ref: library/tkinter ttk tkinter ttk Treeview tag_has12089124
Ref: 3d4812089124
Ref: library/tkinter ttk tkinter ttk Treeview xview12089409
Ref: 3d2412089409
Ref: library/tkinter ttk tkinter ttk Treeview yview12089505
Ref: 3d2512089505
Node: Ttk Styling12089599
Ref: library/tkinter ttk ttk-styling12089701
Ref: 3d4912089701
Ref: library/tkinter ttk ttkstyling12089701
Ref: 3cef12089701
Ref: library/tkinter ttk tkinter ttk Style12090286
Ref: 23e12090286
Ref: library/tkinter ttk tkinter ttk Style configure12090376
Ref: 3d4a12090376
Ref: library/tkinter ttk tkinter ttk Style map12091103
Ref: 182012091103
Ref: library/tkinter ttk tkinter ttk Style lookup12092368
Ref: 3d4b12092368
Ref: library/tkinter ttk tkinter ttk Style layout12092889
Ref: 3d4c12092889
Ref: library/tkinter ttk tkinter ttk Style element_create12094201
Ref: 23d12094201
Ref: library/tkinter ttk tkinter ttk Style element_names12099521
Ref: 3d4e12099521
Ref: library/tkinter ttk tkinter ttk Style element_options12099626
Ref: 3d4f12099626
Ref: library/tkinter ttk tkinter ttk Style theme_create12099729
Ref: 3d5012099729
Ref: library/tkinter ttk tkinter ttk Style theme_settings12100142
Ref: 3d5112100142
Ref: library/tkinter ttk tkinter ttk Style theme_names12101600
Ref: 3d5212101600
Ref: library/tkinter ttk tkinter ttk Style theme_use12101675
Ref: 3d5312101675
Ref: Ttk Styling-Footnote-112101972
Node: Layouts12102034
Ref: library/tkinter ttk layouts12102089
Ref: 3d4d12102089
Ref: library/tkinter ttk layout12103157
Ref: 3d5412103157
Node: IDLE<62>12103158
Ref: library/idle doc12103309
Ref: 3d5512103309
Ref: library/idle id112103309
Ref: 3d5612103309
Ref: library/idle idle12103309
Ref: fb612103309
Ref: IDLE<62>-Footnote-112104269
Node: 目錄12104334
Ref: library/idle menus12104416
Ref: 3d5712104416
Node: File menu Shell and Editor12105698
Ref: library/idle file-menu-shell-and-editor12105802
Ref: 3d5812105802
Node: Edit menu Shell and Editor12107642
Ref: library/idle edit-menu-shell-and-editor12107785
Ref: 3d5912107785
Node: Format menu Editor window only12109580
Ref: library/idle format-menu12109724
Ref: 3d5c12109724
Ref: library/idle format-menu-editor-window-only12109724
Ref: 3d5d12109724
Node: Run menu Editor window only12111093
Ref: library/idle run-menu-editor-window-only12111239
Ref: 3d5e12111239
Ref: library/idle run-module12111318
Ref: 3d5f12111318
Ref: library/idle run-custom12111810
Ref: 3d6112111810
Ref: library/idle check-module12112070
Ref: 3d6012112070
Ref: library/idle python-shell12112414
Ref: 3d6212112414
Node: Shell menu Shell window only12112476
Ref: library/idle shell-menu-shell-window-only12112620
Ref: 3d6312112620
Node: Debug menu Shell window only12113137
Ref: library/idle debug-menu-shell-window-only12113283
Ref: 3d6412113283
Node: Options menu Shell and Editor12114239
Ref: library/idle options-menu-shell-and-editor12114385
Ref: 3d6512114385
Node: Window menu Shell and Editor12116002
Ref: library/idle window-menu-shell-and-editor12116146
Ref: 3d6812116146
Node: Help menu Shell and Editor12116338
Ref: library/idle help-menu-shell-and-editor12116466
Ref: 3d6912116466
Node: Context menus12117186
Ref: library/idle context-menus12117277
Ref: 3d6b12117277
Node: Editing and Navigation12118481
Ref: library/idle editing-and-navigation12118598
Ref: 3d6c12118598
Ref: library/idle id212118598
Ref: 3d6d12118598
Node: Editor windows12118839
Ref: library/idle editor-windows12118933
Ref: 3d6e12118933
Node: Key bindings12119547
Ref: library/idle key-bindings12119671
Ref: 3d6f12119671
Node: Automatic indentation12121021
Ref: library/idle automatic-indentation12121149
Ref: 3d7012121149
Node: Search and Replace12121729
Ref: library/idle search-and-replace12121856
Ref: 3d7112121856
Node: Completions12122190
Ref: library/idle completions12122304
Ref: 3d5a12122304
Ref: library/idle id312122304
Ref: 3d7212122304
Node: Calltips12124922
Ref: library/idle calltips12125030
Ref: 3d5b12125030
Ref: library/idle id412125030
Ref: 3d7312125030
Node: Code Context12126640
Ref: library/idle code-context12126749
Ref: 3d6712126749
Ref: library/idle id512126749
Ref: 3d7412126749
Node: Shell window12127637
Ref: library/idle shell-window12127749
Ref: 3d7512127749
Node: Text colors12129388
Ref: library/idle text-colors12129479
Ref: 3d7612129479
Node: Startup and Code Execution12130512
Ref: library/idle startup-and-code-execution12130643
Ref: 3d7712130643
Node: 命令列用法<2>12131786
Ref: library/idle command-line-usage12131891
Ref: 3d7812131891
Node: Startup failure12132920
Ref: library/idle startup-failure12133051
Ref: 3d7912133051
Node: Running user code12136225
Ref: library/idle running-user-code12136358
Ref: 3d7a12136358
Node: User output in Shell12139138
Ref: library/idle user-output-in-shell12139287
Ref: 3d7b12139287
Node: Developing tkinter applications12142357
Ref: library/idle developing-tkinter-applications12142517
Ref: 3d7c12142517
Node: Running without a subprocess12143766
Ref: library/idle running-without-a-subprocess12143897
Ref: 3d7d12143897
Node: Help and Preferences12145277
Ref: library/idle help-and-preferences12145393
Ref: 3d7e12145393
Node: Help sources12145540
Ref: library/idle help-sources12145637
Ref: 3d6a12145637
Ref: library/idle id612145637
Ref: 3d7f12145637
Node: Setting preferences12146495
Ref: library/idle preferences12146614
Ref: 3d6612146614
Ref: library/idle setting-preferences12146614
Ref: 3d8012146614
Node: IDLE on macOS12147621
Ref: library/idle idle-on-macos12147738
Ref: 3d8112147738
Node: Extensions12147997
Ref: library/idle extensions12148086
Ref: 3d8212148086
Node: idlelib12148437
Ref: library/idle idlelib12148518
Ref: 3d8312148518
Ref: library/idle module-idlelib12148518
Ref: 6912148518
Ref: idlelib-Footnote-112149142
Ref: idlelib-Footnote-212149207
Node: 開發工具12149249
Ref: library/development doc12149436
Ref: 3d8412149436
Ref: library/development development12149436
Ref: 3d8512149436
Ref: library/development development-tools12149436
Ref: 3d8612149436
Node: typing --- 支援型別提示12151486
Ref: library/typing doc12151619
Ref: 3d8712151619
Ref: library/typing typing-support-for-type-hints12151619
Ref: 3d8812151619
Ref: library/typing module-typing12151694
Ref: ed12151694
Ref: typing --- 支援型別提示-Footnote-112154039
Ref: typing --- 支援型別提示-Footnote-212154105
Ref: typing --- 支援型別提示-Footnote-312154157
Ref: typing --- 支援型別提示-Footnote-412154224
Ref: typing --- 支援型別提示-Footnote-512154281
Node: Python 型別系統的技術規範12154330
Ref: library/typing relevant-peps12154451
Ref: 3d8912154451
Ref: library/typing specification-for-the-python-type-system12154451
Ref: 3d8a12154451
Ref: Python 型別系統的技術規範-Footnote-112154702
Node: 型別別名12154766
Ref: library/typing id212154903
Ref: 3d8b12154903
Ref: library/typing type-aliases12154903
Ref: 3fa12154903
Node: NewType12156429
Ref: library/typing distinct12156554
Ref: 3d8c12156554
Ref: library/typing newtype12156554
Ref: 3d8d12156554
Ref: NewType-Footnote-112159595
Node: 註釋 callable 物件12159637
Ref: library/typing annotating-callable-objects12159756
Ref: 3d8e12159756
Ref: library/typing annotating-callables12159756
Ref: 240312159756
Ref: 註釋 callable 物件-Footnote-112162858
Node: 泛型12162900
Ref: library/typing generics12163030
Ref: 1e5612163030
Ref: library/typing id312163030
Ref: 3d9012163030
Node: 註釋元組 tuple12164364
Ref: library/typing annotating-tuples12164493
Ref: 3d9112164493
Ref: library/typing id412164493
Ref: 3d9212164493
Node: 類別物件的型別12166901
Ref: library/typing the-type-of-class-objects12167060
Ref: 3d9312167060
Ref: library/typing type-of-class-objects12167060
Ref: 3d9412167060
Node: Annotating generators and coroutines12168741
Ref: library/typing annotating-generators-and-coroutines12168909
Ref: 240412168909
Ref: library/typing id512168909
Ref: 3d9612168909
Node: 使用者定義泛型型別12171474
Ref: library/typing user-defined-generic-types12171631
Ref: 3d9712171631
Ref: library/typing user-defined-generics12171631
Ref: 47612171631
Ref: 使用者定義泛型型別-Footnote-112177399
Node: Any 型別12177441
Ref: library/typing the-any-type12177605
Ref: 3d9912177605
Node: 標稱 nominal 子型別 vs 結構子型別12180245
Ref: library/typing nominal-vs-structural-subtyping12180397
Ref: 3d9a12180397
Ref: 標稱 nominal 子型別 vs 結構子型別-Footnote-112182057
Ref: 標稱 nominal 子型別 vs 結構子型別-Footnote-212182099
Ref: 標稱 nominal 子型別 vs 結構子型別-Footnote-312182141
Node: 模組內容<7>12182183
Ref: library/typing module-contents12182363
Ref: 3d9b12182363
Node: 特別型別原語 primitive12182693
Ref: library/typing special-typing-primitives12182791
Ref: 3d9c12182791
Node: 特別型別12182985
Ref: library/typing special-types12183083
Ref: 3d9d12183083
Ref: library/typing typing Any12183213
Ref: 65112183213
Ref: library/typing typing AnyStr12183634
Ref: 29312183634
Ref: library/typing typing LiteralString12185429
Ref: 56e12185429
Ref: library/typing typing Never12186709
Ref: 64d12186709
Ref: library/typing typing NoReturn12186734
Ref: 3d9f12186734
Ref: library/typing typing Self12188003
Ref: 56b12188003
Ref: library/typing typing TypeAlias12189889
Ref: 76d12189889
Ref: 特別型別-Footnote-112191490
Ref: 特別型別-Footnote-212191532
Ref: 特別型別-Footnote-312191574
Ref: 特別型別-Footnote-412191624
Ref: 特別型別-Footnote-512191666
Node: 特別型式12191708
Ref: library/typing special-forms12191854
Ref: 3da012191854
Ref: library/typing typing Union12192027
Ref: 5e112192027
Ref: library/typing typing Optional12193274
Ref: 65812193274
Ref: library/typing typing Concatenate12194088
Ref: 76812194088
Ref: library/typing typing Literal12196381
Ref: 7f912196381
Ref: library/typing typing ClassVar12197626
Ref: 24b12197626
Ref: library/typing typing Final12198865
Ref: 24c12198865
Ref: library/typing typing Required12199669
Ref: 56812199669
Ref: library/typing typing NotRequired12199934
Ref: 56912199934
Ref: library/typing typing ReadOnly12200156
Ref: 14512200156
Ref: library/typing typing Annotated12200690
Ref: 8e112200690
Ref: library/typing typing TypeIs12206026
Ref: 14712206026
Ref: library/typing typing TypeGuard12209823
Ref: 14812209823
Ref: library/typing typing Unpack12212249
Ref: 152312212249
Ref: 特別型式-Footnote-112213956
Ref: 特別型式-Footnote-212213998
Ref: 特別型式-Footnote-312214040
Ref: 特別型式-Footnote-412214082
Ref: 特別型式-Footnote-512214124
Ref: 特別型式-Footnote-612214166
Ref: 特別型式-Footnote-712214208
Ref: 特別型式-Footnote-812214250
Ref: 特別型式-Footnote-912214292
Ref: 特別型式-Footnote-1012214334
Ref: 特別型式-Footnote-1112214377
Node: Building generic types and type aliases12214420
Ref: library/typing building-generic-types-and-type-aliases12214578
Ref: 3da212214578
Ref: library/typing typing Generic12215089
Ref: 150c12215089
Ref: library/typing typevar12216295
Ref: 3d9812216295
Ref: library/typing typing TypeVar12216295
Ref: 14112216295
Ref: library/typing typing-constrained-typevar12219731
Ref: 3d9e12219731
Ref: library/typing typing TypeVar __name__12220349
Ref: 3da312220349
Ref: library/typing typing TypeVar __covariant__12220418
Ref: 3da412220418
Ref: library/typing typing TypeVar __contravariant__12220523
Ref: 3da512220523
Ref: library/typing typing TypeVar __infer_variance__12220646
Ref: 3da612220646
Ref: library/typing typing TypeVar __bound__12220812
Ref: 3da712220812
Ref: library/typing typing TypeVar __constraints__12221157
Ref: 3da812221157
Ref: library/typing typing TypeVar __default__12221550
Ref: 3da912221550
Ref: library/typing typing TypeVar has_default12221729
Ref: 3daa12221729
Ref: library/typing typevartuple12222373
Ref: 3da112222373
Ref: library/typing typing TypeVarTuple12222373
Ref: 14312222373
Ref: library/typing typing TypeVarTuple __name__12226638
Ref: 3dab12226638
Ref: library/typing typing TypeVarTuple __default__12226713
Ref: 3dac12226713
Ref: library/typing typing TypeVarTuple has_default12226898
Ref: 3dad12226898
Ref: library/typing typing ParamSpec12227532
Ref: 14212227532
Ref: library/typing typing ParamSpec args12230018
Ref: 3daf12230018
Ref: library/typing typing ParamSpec kwargs12230041
Ref: 3db012230041
Ref: library/typing typing ParamSpec __name__12230802
Ref: 3db112230802
Ref: library/typing typing ParamSpec __default__12230881
Ref: 3db212230881
Ref: library/typing typing ParamSpec has_default12231070
Ref: 3db312231070
Ref: library/typing typing ParamSpecArgs12232317
Ref: 76a12232317
Ref: library/typing typing ParamSpecKwargs12232350
Ref: 76b12232350
Ref: library/typing typing TypeAliasType12233067
Ref: 3fb12233067
Ref: library/typing typing TypeAliasType __name__12233368
Ref: 3db412233368
Ref: library/typing typing TypeAliasType __module__12233528
Ref: 3db512233528
Ref: library/typing typing TypeAliasType __type_params__12233715
Ref: 3db612233715
Ref: library/typing typing TypeAliasType __value__12234083
Ref: 3db712234083
Ref: Building generic types and type aliases-Footnote-112234674
Ref: Building generic types and type aliases-Footnote-212234716
Ref: Building generic types and type aliases-Footnote-312234758
Ref: Building generic types and type aliases-Footnote-412234800
Ref: Building generic types and type aliases-Footnote-512234842
Ref: Building generic types and type aliases-Footnote-612234884
Ref: Building generic types and type aliases-Footnote-712234926
Node: Other special directives12234968
Ref: library/typing other-special-directives12235105
Ref: 3db812235105
Ref: library/typing typing NamedTuple12235331
Ref: 29112235331
Ref: library/typing typing NewType12238484
Ref: c9c12238484
Ref: library/typing typing NewType __module__12238926
Ref: 3db912238926
Ref: library/typing typing NewType __name__12239011
Ref: 3dba12239011
Ref: library/typing typing NewType __supertype__12239075
Ref: 3dbb12239075
Ref: library/typing typing Protocol12239270
Ref: 24912239270
Ref: library/typing typing runtime_checkable12240507
Ref: 3e912240507
Ref: library/typing typing TypedDict12243157
Ref: 14612243157
Ref: library/typing typing TypedDict __total__12247604
Ref: 3dbc12247604
Ref: library/typing typing TypedDict __required_keys__12248665
Ref: 3dbd12248665
Ref: library/typing typing TypedDict __optional_keys__12248734
Ref: 3dbe12248734
Ref: library/typing typing TypedDict __readonly_keys__12250546
Ref: 3dbf12250546
Ref: library/typing typing TypedDict __mutable_keys__12250785
Ref: 3dc012250785
Ref: Other special directives-Footnote-112252118
Ref: Other special directives-Footnote-212252160
Ref: Other special directives-Footnote-312252202
Ref: Other special directives-Footnote-412252244
Node: 協定<2>12252286
Ref: library/typing protocols12252417
Ref: 3dc112252417
Ref: library/typing typing SupportsAbs12252565
Ref: 3dc212252565
Ref: library/typing typing SupportsBytes12252692
Ref: 58c12252692
Ref: library/typing typing SupportsComplex12252781
Ref: 58b12252781
Ref: library/typing typing SupportsFloat12252874
Ref: 3dc312252874
Ref: library/typing typing SupportsIndex12252963
Ref: 9e912252963
Ref: library/typing typing SupportsInt12253080
Ref: 9e812253080
Ref: library/typing typing SupportsRound12253165
Ref: 3dc412253165
Node: ABCs for working with IO12253296
Ref: library/typing abcs-for-working-with-io12253417
Ref: 3dc512253417
Ref: library/typing typing IO12253488
Ref: 6cf12253488
Ref: library/typing typing TextIO12253510
Ref: 3dc612253510
Ref: library/typing typing BinaryIO12253536
Ref: 3dc712253536
Node: 函式與裝飾器12253756
Ref: library/typing functions-and-decorators12253889
Ref: 3dc812253889
Ref: library/typing typing cast12253942
Ref: 3dae12253942
Ref: library/typing typing assert_type12254239
Ref: 65012254239
Ref: library/typing typing assert_never12255328
Ref: 64c12255328
Ref: library/typing typing reveal_type12256737
Ref: 64f12256737
Ref: library/typing typing dataclass_transform12257929
Ref: 47b12257929
Ref: library/typing overload12263939
Ref: 3dc912263939
Ref: library/typing typing overload12263939
Ref: 3d8f12263939
Ref: library/typing typing get_overloads12265466
Ref: 65312265466
Ref: library/typing typing clear_overloads12266139
Ref: 65412266139
Ref: library/typing typing final12266337
Ref: 65212266337
Ref: library/typing typing no_type_check12267612
Ref: 65912267612
Ref: library/typing typing no_type_check_decorator12268098
Ref: 29212268098
Ref: library/typing typing override12268562
Ref: 3f112268562
Ref: library/typing typing type_check_only12269909
Ref: 3dca12269909
Ref: 函式與裝飾器-Footnote-112270615
Ref: 函式與裝飾器-Footnote-212270687
Ref: 函式與裝飾器-Footnote-312270729
Ref: 函式與裝飾器-Footnote-412270771
Ref: 函式與裝飾器-Footnote-512270813
Node: Introspection helpers12270855
Ref: library/typing introspection-helpers12270973
Ref: 3dcb12270973
Ref: library/typing typing get_type_hints12271038
Ref: 65712271038
Ref: library/typing typing get_origin12273544
Ref: 9ea12273544
Ref: library/typing typing get_args12274333
Ref: 82212274333
Ref: library/typing typing get_protocol_members12274973
Ref: 24812274973
Ref: library/typing typing is_protocol12275429
Ref: 24a12275429
Ref: library/typing typing is_typeddict12275736
Ref: 7fa12275736
Ref: library/typing typing ForwardRef12276183
Ref: 174812276183
Ref: library/typing typing NoDefault12276796
Ref: 24712276796
Ref: Introspection helpers-Footnote-112277186
Ref: Introspection helpers-Footnote-212277228
Node: 常數<9>12277270
Ref: library/typing constant12277385
Ref: 3dcc12277385
Ref: library/typing typing TYPE_CHECKING12277418
Ref: c9b12277418
Ref: library/typing generic-concrete-collections12278432
Ref: 3dcd12278432
Ref: 常數<9>-Footnote-112278468
Node: 棄用的別名12278510
Ref: library/typing deprecated-aliases12278595
Ref: 3dce12278595
Ref: library/typing id612278595
Ref: 3dcf12278595
Ref: 棄用的別名-Footnote-112280139
Node: 內建型別的別名12280181
Ref: library/typing aliases-to-built-in-types12280293
Ref: 3dd012280293
Ref: library/typing corresponding-to-built-in-types12280293
Ref: 3dd112280293
Ref: library/typing typing Dict12280351
Ref: 3dd212280351
Ref: library/typing typing List12280790
Ref: 3dd312280790
Ref: library/typing typing Set12281252
Ref: 3dd412281252
Ref: library/typing typing FrozenSet12281704
Ref: 3dd512281704
Ref: library/typing typing Tuple12281981
Ref: 3dd612281981
Ref: library/typing typing Type12282345
Ref: 3d9512282345
Ref: 內建型別的別名-Footnote-112282780
Ref: 內建型別的別名-Footnote-212282822
Ref: 內建型別的別名-Footnote-312282864
Ref: 內建型別的別名-Footnote-412282906
Ref: 內建型別的別名-Footnote-512282948
Ref: 內建型別的別名-Footnote-612282990
Node: collections 中型別的別名12283032
Ref: library/typing aliases-to-types-in-collections12283184
Ref: 3dd712283184
Ref: library/typing corresponding-to-types-in-collections12283184
Ref: 3dd812283184
Ref: library/typing typing DefaultDict12283269
Ref: 3dd912283269
Ref: library/typing typing OrderedDict12283624
Ref: 3dda12283624
Ref: library/typing typing ChainMap12283977
Ref: 3ddb12283977
Ref: library/typing typing Counter12284303
Ref: 3ddc12284303
Ref: library/typing typing Deque12284617
Ref: 3ddd12284617
Ref: collections 中型別的別名-Footnote-112284951
Ref: collections 中型別的別名-Footnote-212284993
Ref: collections 中型別的別名-Footnote-312285035
Ref: collections 中型別的別名-Footnote-412285077
Ref: collections 中型別的別名-Footnote-512285119
Node: Aliases to other concrete types12285161
Ref: library/typing aliases-to-other-concrete-types12285331
Ref: 3dde12285331
Ref: library/typing other-concrete-types12285331
Ref: 3ddf12285331
Ref: library/typing typing Pattern12285416
Ref: 6d012285416
Ref: library/typing typing Match12285443
Ref: 3de012285443
Ref: library/typing typing Text12286018
Ref: 2dd12286018
Ref: library/typing abstract-base-classes12286777
Ref: 3de112286777
Ref: Aliases to other concrete types-Footnote-112286813
Node: collections abc 中容器 ABC 的別名12286855
Ref: library/typing aliases-to-container-abcs-in-collections-abc12287042
Ref: 3de212287042
Ref: library/typing corresponding-to-collections-in-collections-abc12287042
Ref: 3de312287042
Ref: library/typing typing AbstractSet12287145
Ref: 3de412287145
Ref: library/typing typing ByteString12287416
Ref: 2b812287416
Ref: library/typing typing Collection12287766
Ref: c9a12287766
Ref: library/typing typing Container12288103
Ref: 3de512288103
Ref: library/typing typing ItemsView12288386
Ref: 3de612288386
Ref: library/typing typing KeysView12288711
Ref: 3de712288711
Ref: library/typing typing Mapping12289009
Ref: 3de812289009
Ref: library/typing typing MappingView12289305
Ref: 3de912289305
Ref: library/typing typing MutableMapping12289586
Ref: 3dea12289586
Ref: library/typing typing MutableSequence12289886
Ref: 3deb12289886
Ref: library/typing typing MutableSet12290183
Ref: 3dec12290183
Ref: library/typing typing Sequence12290471
Ref: 3ded12290471
Ref: library/typing typing ValuesView12290773
Ref: 3dee12290773
Ref: collections abc 中容器 ABC 的別名-Footnote-112291114
Ref: collections abc 中容器 ABC 的別名-Footnote-212291156
Ref: collections abc 中容器 ABC 的別名-Footnote-312291198
Ref: collections abc 中容器 ABC 的別名-Footnote-412291240
Ref: collections abc 中容器 ABC 的別名-Footnote-512291282
Ref: collections abc 中容器 ABC 的別名-Footnote-612291324
Ref: collections abc 中容器 ABC 的別名-Footnote-712291366
Ref: collections abc 中容器 ABC 的別名-Footnote-812291408
Ref: collections abc 中容器 ABC 的別名-Footnote-912291450
Ref: collections abc 中容器 ABC 的別名-Footnote-1012291492
Ref: collections abc 中容器 ABC 的別名-Footnote-1112291535
Ref: collections abc 中容器 ABC 的別名-Footnote-1212291578
Node: Aliases to asynchronous ABCs in collections abc12291621
Ref: library/typing aliases-to-asynchronous-abcs-in-collections-abc12291817
Ref: 3def12291817
Ref: library/typing asynchronous-programming12291817
Ref: 3df012291817
Ref: library/typing typing Coroutine12291942
Ref: 184c12291942
Ref: library/typing typing AsyncGenerator12292490
Ref: 152012292490
Ref: library/typing typing AsyncIterable12293131
Ref: 3df112293131
Ref: library/typing typing AsyncIterator12293454
Ref: 3df212293454
Ref: library/typing typing Awaitable12293783
Ref: 3df312293783
Ref: Aliases to asynchronous ABCs in collections abc-Footnote-112294130
Ref: Aliases to asynchronous ABCs in collections abc-Footnote-212294172
Ref: Aliases to asynchronous ABCs in collections abc-Footnote-312294214
Ref: Aliases to asynchronous ABCs in collections abc-Footnote-412294256
Ref: Aliases to asynchronous ABCs in collections abc-Footnote-512294298
Node: Aliases to other ABCs in collections abc12294340
Ref: library/typing aliases-to-other-abcs-in-collections-abc12294521
Ref: 3df412294521
Ref: library/typing corresponding-to-other-types-in-collections-abc12294521
Ref: 3df512294521
Ref: library/typing typing Iterable12294632
Ref: 3df612294632
Ref: library/typing typing Iterator12294912
Ref: 3df712294912
Ref: library/typing typing Callable12295193
Ref: 76912295193
Ref: library/typing typing Generator12295781
Ref: 151f12295781
Ref: library/typing typing Hashable12296388
Ref: 49b12296388
Ref: library/typing typing Reversible12296579
Ref: 3df812296579
Ref: library/typing typing Sized12296864
Ref: 49c12296864
Ref: Aliases to other ABCs in collections abc-Footnote-112297082
Ref: Aliases to other ABCs in collections abc-Footnote-212297124
Ref: Aliases to other ABCs in collections abc-Footnote-312297166
Ref: Aliases to other ABCs in collections abc-Footnote-412297208
Ref: Aliases to other ABCs in collections abc-Footnote-512297250
Ref: Aliases to other ABCs in collections abc-Footnote-612297292
Node: contextlib ABC 的別名12297334
Ref: library/typing aliases-to-contextlib-abcs12297459
Ref: 3df912297459
Ref: library/typing context-manager-types12297459
Ref: 3dfa12297459
Ref: library/typing typing ContextManager12297535
Ref: c3512297535
Ref: library/typing typing AsyncContextManager12298254
Ref: 151d12298254
Ref: contextlib ABC 的別名-Footnote-112299035
Ref: contextlib ABC 的別名-Footnote-212299077
Node: Deprecation Timeline of Major Features12299119
Ref: library/typing deprecation-timeline-of-major-features12299247
Ref: 3dfb12299247
Ref: Deprecation Timeline of Major Features-Footnote-112301982
Ref: Deprecation Timeline of Major Features-Footnote-212302024
Ref: Deprecation Timeline of Major Features-Footnote-312302079
Ref: Deprecation Timeline of Major Features-Footnote-412302134
Ref: Deprecation Timeline of Major Features-Footnote-512302189
Ref: Deprecation Timeline of Major Features-Footnote-612302231
Ref: Deprecation Timeline of Major Features-Footnote-712302287
Node: pydoc --- 文件產生器與線上幫助系統12302343
Ref: library/pydoc doc12302504
Ref: 3dfc12302504
Ref: library/pydoc module-pydoc12302504
Ref: a312302504
Ref: library/pydoc pydoc-documentation-generator-and-online-help-system12302504
Ref: 3dfd12302504
Ref: pydoc --- 文件產生器與線上幫助系統-Footnote-112307367
Node: Python 開發模式12307432
Ref: library/devmode doc12307605
Ref: 3dff12307605
Ref: library/devmode devmode12307605
Ref: 1dd12307605
Ref: library/devmode python-development-mode12307605
Ref: 3e0012307605
Node: Python 開發模式的影響12308157
Ref: library/devmode effects-of-the-python-development-mode12308272
Ref: 3e0112308272
Node: ResourceWarning 範例12311703
Ref: library/devmode resourcewarning-example12311857
Ref: 3e0212311857
Node: 檔案描述器的錯誤範例12313688
Ref: library/devmode bad-file-descriptor-error-example12313805
Ref: 3e0312313805
Ref: 檔案描述器的錯誤範例-Footnote-112315339
Node: doctest --- 測試互動式 Python 範例12315404
Ref: library/doctest doc12315562
Ref: 3e0412315562
Ref: library/doctest doctest-test-interactive-python-examples12315562
Ref: 3e0512315562
Ref: library/doctest module-doctest12315562
Ref: 3112315562
Ref: doctest --- 測試互動式 Python 範例-Footnote-112319644
Node: Simple Usage Checking Examples in Docstrings12319711
Ref: library/doctest doctest-simple-testmod12319887
Ref: 3e0612319887
Ref: library/doctest simple-usage-checking-examples-in-docstrings12319887
Ref: 3e0712319887
Node: Simple Usage Checking Examples in a Text File12321660
Ref: library/doctest doctest-simple-testfile12321857
Ref: 3e0912321857
Ref: library/doctest simple-usage-checking-examples-in-a-text-file12321857
Ref: 3e0a12321857
Node: How It Works12324201
Ref: library/doctest doctest-how-it-works12324364
Ref: 3e0c12324364
Ref: library/doctest how-it-works12324364
Ref: 3e0d12324364
Node: Which Docstrings Are Examined?12325013
Ref: library/doctest doctest-which-docstrings12325139
Ref: 3e0e12325139
Ref: library/doctest which-docstrings-are-examined12325139
Ref: 3e0f12325139
Node: How are Docstring Examples Recognized?12326633
Ref: library/doctest doctest-finding-examples12326797
Ref: 3e1012326797
Ref: library/doctest how-are-docstring-examples-recognized12326797
Ref: 3e1112326797
Node: What's the Execution Context?12329907
Ref: library/doctest doctest-execution-context12330063
Ref: 3e1512330063
Ref: library/doctest what-s-the-execution-context12330063
Ref: 3e1612330063
Node: What About Exceptions?12330771
Ref: library/doctest doctest-exceptions12330901
Ref: 3e1712330901
Ref: library/doctest what-about-exceptions12330901
Ref: 3e1812330901
Ref: library/doctest option-flags-and-directives12335444
Ref: 3e1912335444
Ref: What About Exceptions?-Footnote-112335481
Node: 可選旗標12335681
Ref: library/doctest doctest-options12335792
Ref: ed712335792
Ref: library/doctest option-flags12335792
Ref: 3e1a12335792
Ref: library/doctest doctest DONT_ACCEPT_TRUE_FOR_112336404
Ref: 3e1b12336404
Ref: library/doctest doctest DONT_ACCEPT_BLANKLINE12337030
Ref: 3e1c12337030
Ref: library/doctest doctest NORMALIZE_WHITESPACE12337485
Ref: 3e1212337485
Ref: library/doctest doctest ELLIPSIS12337977
Ref: 13d912337977
Ref: library/doctest doctest IGNORE_EXCEPTION_DETAIL12338410
Ref: 129c12338410
Ref: library/doctest doctest SKIP12339872
Ref: 3e1d12339872
Ref: library/doctest doctest COMPARISON_FLAGS12340382
Ref: 3e1e12340382
Ref: library/doctest doctest REPORT_UDIFF12340554
Ref: 13da12340554
Ref: library/doctest doctest REPORT_CDIFF12340712
Ref: 13db12340712
Ref: library/doctest doctest REPORT_NDIFF12340874
Ref: 13dc12340874
Ref: library/doctest doctest REPORT_ONLY_FIRST_FAILURE12341340
Ref: 3e1f12341340
Ref: library/doctest doctest FAIL_FAST12341921
Ref: ed812341921
Ref: library/doctest doctest REPORTING_FLAGS12342388
Ref: 3e2012342388
Ref: library/doctest doctest register_optionflag12342643
Ref: 3e2112342643
Node: Directives12343129
Ref: library/doctest directives12343227
Ref: 3e2412343227
Ref: library/doctest doctest-directives12343227
Ref: 3e1312343227
Ref: library/doctest grammar-token-doctest-directive12343450
Ref: 3e2512343450
Ref: library/doctest grammar-token-doctest-directive_options12343514
Ref: 3e2612343514
Ref: library/doctest grammar-token-doctest-directive_option12343586
Ref: 3e2712343586
Ref: library/doctest grammar-token-doctest-on_or_off12343649
Ref: 3e2812343649
Ref: library/doctest grammar-token-doctest-directive_option_name12343690
Ref: 3e2912343690
Node: 警告<2>12345785
Ref: library/doctest doctest-warnings12345862
Ref: 3e2a12345862
Ref: library/doctest warnings12345862
Ref: 3e2b12345862
Node: 基礎 API12347575
Ref: library/doctest basic-api12347705
Ref: 3e2c12347705
Ref: library/doctest doctest-basic-api12347705
Ref: 3e0812347705
Ref: library/doctest doctest testfile12348089
Ref: 3e0b12348089
Ref: library/doctest doctest testmod12352014
Ref: 13d812352014
Ref: library/doctest doctest run_docstring_examples12353736
Ref: 3e2e12353736
Node: Unittest API12354712
Ref: library/doctest doctest-unittest-api12354842
Ref: 3e2f12354842
Ref: library/doctest unittest-api12354842
Ref: 3e3012354842
Ref: library/doctest doctest DocFileSuite12355611
Ref: 3e3212355611
Ref: library/doctest doctest DocTestSuite12359443
Ref: d9912359443
Ref: library/doctest doctest failureException12361331
Ref: 3e3312361331
Ref: library/doctest doctest set_unittest_reportflags12363013
Ref: 3e3412363013
Node: Advanced API12364185
Ref: library/doctest advanced-api12364314
Ref: 3e3512364314
Ref: library/doctest doctest-advanced-api12364314
Ref: 3e3612364314
Node: DocTest 物件12366465
Ref: library/doctest doctest-doctest12366551
Ref: 3e3812366551
Ref: library/doctest doctest-objects12366551
Ref: 3e3912366551
Ref: library/doctest doctest DocTest12366600
Ref: 15aa12366600
Ref: library/doctest doctest DocTest examples12367017
Ref: 3e3a12367017
Ref: library/doctest doctest DocTest globs12367189
Ref: 3e3b12367189
Ref: library/doctest doctest DocTest name12367521
Ref: 3e3c12367521
Ref: library/doctest doctest DocTest filename12367711
Ref: 3e3d12367711
Ref: library/doctest doctest DocTest lineno12367945
Ref: 16e412367945
Ref: library/doctest doctest DocTest docstring12368220
Ref: 3e3e12368220
Node: Example 物件12368416
Ref: library/doctest doctest-example12368531
Ref: 3e3f12368531
Ref: library/doctest example-objects12368531
Ref: 3e4012368531
Ref: library/doctest doctest Example12368580
Ref: 3e3712368580
Ref: library/doctest doctest Example source12369020
Ref: 3e4112369020
Ref: library/doctest doctest Example want12369259
Ref: 3e4212369259
Ref: library/doctest doctest Example exc_msg12369603
Ref: 3e4312369603
Ref: library/doctest doctest Example lineno12370082
Ref: 3e4412370082
Ref: library/doctest doctest Example indent12370310
Ref: 3e4512370310
Ref: library/doctest doctest Example options12370496
Ref: 3e4612370496
Node: DocTestFinder 物件12370903
Ref: library/doctest doctest-doctestfinder12371024
Ref: 3e4712371024
Ref: library/doctest doctestfinder-objects12371024
Ref: 3e4812371024
Ref: library/doctest doctest DocTestFinder12371085
Ref: 152612371085
Ref: library/doctest doctest DocTestFinder find12372225
Ref: 15fb12372225
Node: DocTestParser 物件12374333
Ref: library/doctest doctest-doctestparser12374459
Ref: 3e4912374459
Ref: library/doctest doctestparser-objects12374459
Ref: 3e4a12374459
Ref: library/doctest doctest DocTestParser12374520
Ref: 3e1412374520
Ref: library/doctest doctest DocTestParser get_doctest12374755
Ref: 3e4b12374755
Ref: library/doctest doctest DocTestParser get_examples12375150
Ref: 3e4c12375150
Ref: library/doctest doctest DocTestParser parse12375488
Ref: 3e4d12375488
Node: TestResults objects12375884
Ref: library/doctest testresults-objects12376010
Ref: 3e4e12376010
Ref: library/doctest doctest TestResults12376071
Ref: 3e4f12376071
Ref: library/doctest doctest TestResults failed12376124
Ref: 3e5012376124
Ref: library/doctest doctest TestResults attempted12376184
Ref: 3e5112376184
Ref: library/doctest doctest TestResults skipped12376250
Ref: 1c112376250
Node: DocTestRunner 物件12376346
Ref: library/doctest doctest-doctestrunner12376472
Ref: 3e5212376472
Ref: library/doctest doctestrunner-objects12376472
Ref: 3e5312376472
Ref: library/doctest doctest DocTestRunner12376533
Ref: 3e2312376533
Ref: library/doctest doctest DocTestRunner report_start12378969
Ref: 3e5412378969
Ref: library/doctest doctest DocTestRunner report_success12379467
Ref: 3e5512379467
Ref: library/doctest doctest DocTestRunner report_failure12379999
Ref: 3e5712379999
Ref: library/doctest doctest DocTestRunner report_unexpected_exception12380521
Ref: 3e5612380521
Ref: library/doctest doctest DocTestRunner run12381195
Ref: 1bf12381195
Ref: library/doctest doctest DocTestRunner summarize12382248
Ref: 3e2d12382248
Ref: library/doctest doctest DocTestRunner tries12382707
Ref: 3e5812382707
Ref: library/doctest doctest DocTestRunner failures12382772
Ref: 3e5912382772
Ref: library/doctest doctest DocTestRunner skips12382837
Ref: 1c012382837
Node: OutputChecker 物件12382934
Ref: library/doctest doctest-outputchecker12383032
Ref: 3e5a12383032
Ref: library/doctest outputchecker-objects12383032
Ref: 3e5b12383032
Ref: library/doctest doctest OutputChecker12383093
Ref: 3e2212383093
Ref: library/doctest doctest OutputChecker check_output12383590
Ref: 3e5c12383590
Ref: library/doctest doctest OutputChecker output_difference12384067
Ref: 3e5d12384067
Node: Debugging12384382
Ref: library/doctest debugging12384506
Ref: 3e5e12384506
Ref: library/doctest doctest-debugging12384506
Ref: 3e5f12384506
Ref: library/doctest doctest script_from_examples12386602
Ref: 3e6212386602
Ref: library/doctest doctest testsource12387587
Ref: 3e6312387587
Ref: library/doctest doctest debug12388378
Ref: 3e6112388378
Ref: library/doctest doctest debug_src12389465
Ref: 3e6512389465
Ref: library/doctest doctest DebugRunner12390335
Ref: 3e6012390335
Ref: library/doctest doctest DocTestFailure12391111
Ref: 3e6712391111
Ref: library/doctest doctest DocTestFailure test12391460
Ref: 3e6812391460
Ref: library/doctest doctest DocTestFailure example12391580
Ref: 3e6912391580
Ref: library/doctest doctest DocTestFailure got12391660
Ref: 3e6a12391660
Ref: library/doctest doctest UnexpectedException12391727
Ref: 3e6612391727
Ref: library/doctest doctest UnexpectedException test12392077
Ref: 3e6b12392077
Ref: library/doctest doctest UnexpectedException example12392202
Ref: 3e6c12392202
Ref: library/doctest doctest UnexpectedException exc_info12392287
Ref: 3e6d12392287
Node: Soapbox12392445
Ref: library/doctest doctest-soapbox12392548
Ref: 3e6e12392548
Ref: library/doctest soapbox12392548
Ref: 3e6f12392548
Node: unittest --- 單元測試框架12396378
Ref: library/unittest doc12396555
Ref: 3e7012396555
Ref: library/unittest module-unittest12396555
Ref: ef12396555
Ref: library/unittest unittest-unit-testing-framework12396555
Ref: 3e7112396555
Ref: unittest --- 單元測試框架-Footnote-112399709
Ref: unittest --- 單元測試框架-Footnote-212399787
Ref: unittest --- 單元測試框架-Footnote-312399880
Ref: unittest --- 單元測試框架-Footnote-412399913
Ref: unittest --- 單元測試框架-Footnote-512399977
Ref: unittest --- 單元測試框架-Footnote-612400035
Ref: unittest --- 單元測試框架-Footnote-712400065
Ref: unittest --- 單元測試框架-Footnote-812400097
Ref: unittest --- 單元測試框架-Footnote-912400141
Node: 簡單範例12400175
Ref: library/unittest basic-example12400308
Ref: 3e7312400308
Ref: library/unittest unittest-minimal-example12400308
Ref: 3e7412400308
Node: 命令執行列介面 Command-Line Interface12403175
Ref: library/unittest command-line-interface12403349
Ref: 3e7612403349
Ref: library/unittest unittest-command-line-interface12403349
Ref: 3e7712403349
Node: 命令列模式選項12404739
Ref: library/unittest command-line-options12404841
Ref: 3e7912404841
Ref: library/unittest cmdoption-unittest-b12404944
Ref: 12c612404944
Ref: library/unittest cmdoption-unittest-buffer12404944
Ref: 3e7a12404944
Ref: library/unittest cmdoption-unittest-c12405216
Ref: 12c712405216
Ref: library/unittest cmdoption-unittest-catch12405216
Ref: 3e7b12405216
Ref: library/unittest cmdoption-unittest-f12405518
Ref: 12c912405518
Ref: library/unittest cmdoption-unittest-failfast12405518
Ref: 3e7d12405518
Ref: library/unittest cmdoption-unittest-k12405604
Ref: 3e7e12405604
Ref: library/unittest cmdoption-unittest-locals12406316
Ref: 3e7f12406316
Ref: library/unittest cmdoption-unittest-durations12406383
Ref: 3e8012406383
Node: Test Discovery（測試探索）12406829
Ref: library/unittest test-discovery12407011
Ref: 3e8112407011
Ref: library/unittest unittest-test-discovery12407011
Ref: 3e7812407011
Ref: library/unittest cmdoption-unittest-discover-v12407899
Ref: 3e8212407899
Ref: library/unittest cmdoption-unittest-discover-verbose12407899
Ref: 3e8312407899
Ref: library/unittest cmdoption-unittest-discover-s12407958
Ref: 3e8412407958
Ref: library/unittest cmdoption-unittest-discover-start-directory12407958
Ref: 3e8512407958
Ref: library/unittest cmdoption-unittest-discover-p12408057
Ref: 3e8612408057
Ref: library/unittest cmdoption-unittest-discover-pattern12408057
Ref: 3e8712408057
Ref: library/unittest cmdoption-unittest-discover-t12408156
Ref: 3e8812408156
Ref: library/unittest cmdoption-unittest-discover-top-level-directory12408156
Ref: 3e8912408156
Node: Organizing test code12410541
Ref: library/unittest organizing-test-code12410701
Ref: 3e8b12410701
Ref: library/unittest organizing-tests12410701
Ref: 3e7512410701
Node: Re-using old test code12415460
Ref: library/unittest legacy-unit-tests12415624
Ref: 3e8c12415624
Ref: library/unittest re-using-old-test-code12415624
Ref: 3e8d12415624
Node: Skipping tests and expected failures12417163
Ref: library/unittest skipping-tests-and-expected-failures12417352
Ref: 3e8e12417352
Ref: library/unittest unittest-skipping12417352
Ref: 3e8f12417352
Ref: library/unittest unittest skip12420502
Ref: 18de12420502
Ref: library/unittest unittest skipIf12420648
Ref: 3e9212420648
Ref: library/unittest unittest skipUnless12420752
Ref: 3e9312420752
Ref: library/unittest unittest expectedFailure12420864
Ref: 3e9112420864
Ref: library/unittest unittest SkipTest12421171
Ref: f8712421171
Node: Distinguishing test iterations using subtests12421659
Ref: library/unittest distinguishing-test-iterations-using-subtests12421847
Ref: 3e9412421847
Ref: library/unittest subtests12421847
Ref: f8512421847
Node: Classes and functions12424433
Ref: library/unittest classes-and-functions12424610
Ref: 3e9512424610
Ref: library/unittest unittest-contents12424610
Ref: 3e9612424610
Node: Test cases12424811
Ref: library/unittest test-cases12424902
Ref: 3e9712424902
Ref: library/unittest testcase-objects12424902
Ref: 3e9812424902
Ref: library/unittest unittest TestCase12424945
Ref: 3f412424945
Ref: library/unittest unittest TestCase setUp12426265
Ref: 12cd12426265
Ref: library/unittest unittest TestCase tearDown12426642
Ref: 12ce12426642
Ref: library/unittest unittest TestCase setUpClass12427416
Ref: 9f212427416
Ref: library/unittest unittest TestCase tearDownClass12427857
Ref: 12cb12427857
Ref: library/unittest unittest TestCase run12428307
Ref: 10ff12428307
Ref: library/unittest unittest TestCase skipTest12428932
Ref: 3e9012428932
Ref: library/unittest unittest TestCase subTest12429191
Ref: f8412429191
Ref: library/unittest unittest TestCase debug12429744
Ref: 179712429744
Ref: library/unittest assert-methods12429979
Ref: 3e7212429979
Ref: library/unittest unittest TestCase assertEqual12433829
Ref: 4cd12433829
Ref: library/unittest unittest TestCase assertNotEqual12434687
Ref: 4ce12434687
Ref: library/unittest unittest TestCase assertTrue12434866
Ref: 4cb12434866
Ref: library/unittest unittest TestCase assertFalse12434911
Ref: 4cc12434911
Ref: library/unittest unittest TestCase assertIs12435412
Ref: 12cf12435412
Ref: library/unittest unittest TestCase assertIsNot12435464
Ref: 12d012435464
Ref: library/unittest unittest TestCase assertIsNone12435639
Ref: 122212435639
Ref: library/unittest unittest TestCase assertIsNotNone12435686
Ref: 122312435686
Ref: library/unittest unittest TestCase assertIn12435825
Ref: 12d812435825
Ref: library/unittest unittest TestCase assertNotIn12435881
Ref: 12d912435881
Ref: library/unittest unittest TestCase assertIsInstance12436035
Ref: 12d112436035
Ref: library/unittest unittest TestCase assertNotIsInstance12436090
Ref: 12d212436090
Ref: library/unittest unittest TestCase assertRaises12439277
Ref: 4d112439277
Ref: library/unittest unittest TestCase assertRaisesRegex12440979
Ref: 4d312440979
Ref: library/unittest unittest TestCase assertWarns12441958
Ref: 10fd12441958
Ref: library/unittest unittest TestCase assertWarnsRegex12443650
Ref: 10fe12443650
Ref: library/unittest unittest TestCase assertLogs12444575
Ref: 7fd12444575
Ref: library/unittest unittest TestCase records12445651
Ref: 3e9c12445651
Ref: library/unittest unittest TestCase output12445791
Ref: 3e9d12445791
Ref: library/unittest unittest TestCase assertNoLogs12446338
Ref: 7fc12446338
Ref: library/unittest unittest TestCase assertAlmostEqual12449912
Ref: 4cf12449912
Ref: library/unittest unittest TestCase assertNotAlmostEqual12450010
Ref: 4d012450010
Ref: library/unittest unittest TestCase assertGreater12451070
Ref: 12d312451070
Ref: library/unittest unittest TestCase assertGreaterEqual12451127
Ref: 12d412451127
Ref: library/unittest unittest TestCase assertLess12451189
Ref: 12d512451189
Ref: library/unittest unittest TestCase assertLessEqual12451243
Ref: 12d612451243
Ref: library/unittest unittest TestCase assertRegex12451610
Ref: 4d212451610
Ref: library/unittest unittest TestCase assertNotRegex12451663
Ref: 4d412451663
Ref: library/unittest unittest TestCase assertCountEqual12452394
Ref: 11c212452394
Ref: library/unittest type-specific-methods12453055
Ref: 3e9b12453055
Ref: library/unittest unittest TestCase addTypeEqualityFunc12453372
Ref: 12dc12453372
Ref: library/unittest unittest TestCase assertMultiLineEqual12456114
Ref: 12d712456114
Ref: library/unittest unittest TestCase assertSequenceEqual12456531
Ref: 122112456531
Ref: library/unittest unittest TestCase assertListEqual12457158
Ref: 121f12457158
Ref: library/unittest unittest TestCase assertTupleEqual12457217
Ref: 122012457217
Ref: library/unittest unittest TestCase assertSetEqual12457667
Ref: 121d12457667
Ref: library/unittest unittest TestCase assertDictEqual12458121
Ref: 121e12458121
Ref: library/unittest other-methods-and-attrs12458481
Ref: 3e9f12458481
Ref: library/unittest unittest TestCase fail12458572
Ref: 3ea012458572
Ref: library/unittest unittest TestCase failureException12458715
Ref: 3e9e12458715
Ref: library/unittest unittest TestCase longMessage12459123
Ref: 12ca12459123
Ref: library/unittest unittest TestCase maxDiff12459860
Ref: 11c312459860
Ref: library/unittest unittest TestCase countTestCases12460553
Ref: 3ea112460553
Ref: library/unittest unittest TestCase defaultTestResult12460735
Ref: 3e9a12460735
Ref: library/unittest unittest TestCase id12461167
Ref: 3ea212461167
Ref: library/unittest unittest TestCase shortDescription12461362
Ref: 3ea312461362
Ref: library/unittest unittest TestCase addCleanup12461976
Ref: a2412461976
Ref: library/unittest unittest TestCase enterContext12462584
Ref: 65e12462584
Ref: library/unittest unittest TestCase doCleanups12462913
Ref: 12cc12462913
Ref: library/unittest unittest TestCase addClassCleanup12463569
Ref: 9f112463569
Ref: library/unittest unittest TestCase enterClassContext12464245
Ref: 65f12464245
Ref: library/unittest unittest TestCase doClassCleanups12464596
Ref: 3ea412464596
Ref: library/unittest unittest IsolatedAsyncioTestCase12465302
Ref: 2de12465302
Ref: library/unittest unittest IsolatedAsyncioTestCase loop_factory12465516
Ref: 3ea512465516
Ref: library/unittest unittest IsolatedAsyncioTestCase asyncSetUp12465769
Ref: 3ea612465769
Ref: library/unittest unittest IsolatedAsyncioTestCase asyncTearDown12466208
Ref: 3ea712466208
Ref: library/unittest unittest IsolatedAsyncioTestCase addAsyncCleanup12467053
Ref: 3ea812467053
Ref: library/unittest unittest IsolatedAsyncioTestCase enterAsyncContext12467211
Ref: 66012467211
Ref: library/unittest unittest IsolatedAsyncioTestCase run12467576
Ref: 3ea912467576
Ref: library/unittest unittest FunctionTestCase12469312
Ref: 160512469312
Node: Grouping tests12469790
Ref: library/unittest grouping-tests12469915
Ref: 3eaa12469915
Ref: library/unittest testsuite-objects12469915
Ref: 3eab12469915
Ref: library/unittest unittest TestSuite12469966
Ref: d9a12469966
Ref: library/unittest unittest TestSuite addTest12470914
Ref: 3eac12470914
Ref: library/unittest unittest TestSuite addTests12471034
Ref: 3ead12471034
Ref: library/unittest unittest TestSuite run12471410
Ref: 3eae12471410
Ref: library/unittest unittest TestSuite debug12471713
Ref: 3eaf12471713
Ref: library/unittest unittest TestSuite countTestCases12471986
Ref: 3eb012471986
Ref: library/unittest unittest TestSuite __iter__12472150
Ref: fcc12472150
Node: Loading and running tests12473579
Ref: library/unittest loading-and-running-tests12473685
Ref: 3eb112473685
Ref: library/unittest unittest TestLoader12473758
Ref: 27012473758
Ref: library/unittest unittest TestLoader errors12474252
Ref: e3012474252
Ref: library/unittest unittest TestLoader loadTestsFromTestCase12474718
Ref: 27212474718
Ref: library/unittest unittest TestLoader loadTestsFromModule12475267
Ref: 27112475267
Ref: library/unittest unittest TestLoader loadTestsFromName12476653
Ref: 12da12476653
Ref: library/unittest unittest TestLoader loadTestsFromNames12478439
Ref: 3eb312478439
Ref: library/unittest unittest TestLoader getTestCaseNames12478725
Ref: 27312478725
Ref: library/unittest unittest TestLoader discover12478928
Ref: f8812478928
Ref: library/unittest unittest TestLoader testMethodPrefix12482188
Ref: 3eb412482188
Ref: library/unittest unittest TestLoader sortTestMethodsUsing12482471
Ref: 3eb512482471
Ref: library/unittest unittest TestLoader suiteClass12482679
Ref: 12db12482679
Ref: library/unittest unittest TestLoader testNamePatterns12482971
Ref: 3eb612482971
Ref: library/unittest unittest TestResult12483682
Ref: 110012483682
Ref: library/unittest unittest TestResult errors12484548
Ref: 3eb712484548
Ref: library/unittest unittest TestResult failures12484775
Ref: 3eb812484775
Ref: library/unittest unittest TestResult skipped12485056
Ref: 3eb912485056
Ref: library/unittest unittest TestResult expectedFailures12485251
Ref: 3eba12485251
Ref: library/unittest unittest TestResult unexpectedSuccesses12485490
Ref: 3ebb12485490
Ref: library/unittest unittest TestResult collectedDurations12485652
Ref: 160b12485652
Ref: library/unittest unittest TestResult shouldStop12485859
Ref: 3ebc12485859
Ref: library/unittest unittest TestResult testsRun12485990
Ref: 3ebe12485990
Ref: library/unittest unittest TestResult buffer12486066
Ref: 3ebf12486066
Ref: library/unittest unittest TestResult failfast12486514
Ref: 3ec212486514
Ref: library/unittest unittest TestResult tb_locals12486698
Ref: 3ec312486698
Ref: library/unittest unittest TestResult wasSuccessful12486845
Ref: 3ec412486845
Ref: library/unittest unittest TestResult stop12487180
Ref: 3ebd12487180
Ref: library/unittest unittest TestResult startTest12488140
Ref: 3ec012488140
Ref: library/unittest unittest TestResult stopTest12488239
Ref: 3ec112488239
Ref: library/unittest unittest TestResult startTestRun12488374
Ref: 12de12488374
Ref: library/unittest unittest TestResult stopTestRun12488495
Ref: 12df12488495
Ref: library/unittest unittest TestResult addError12488614
Ref: 179a12488614
Ref: library/unittest unittest TestResult addFailure12489079
Ref: 179912489079
Ref: library/unittest unittest TestResult addSuccess12489535
Ref: 3ec512489535
Ref: library/unittest unittest TestResult addSkip12489677
Ref: 179b12489677
Ref: library/unittest unittest TestResult addExpectedFailure12489971
Ref: 3ec612489971
Ref: library/unittest unittest TestResult addUnexpectedSuccess12490395
Ref: 3ec712490395
Ref: library/unittest unittest TestResult addSubTest12490699
Ref: 179c12490699
Ref: library/unittest unittest TestResult addDuration12491373
Ref: 164512491373
Ref: library/unittest unittest TextTestResult12491619
Ref: 4d512491619
Ref: library/unittest unittest defaultTestLoader12492014
Ref: 3eb212492014
Ref: library/unittest unittest TextTestRunner12492271
Ref: 164412492271
Ref: library/unittest unittest TextTestRunner _makeResult12493663
Ref: 3ec912493663
Ref: library/unittest unittest TextTestRunner run12494314
Ref: 3eca12494314
Ref: library/unittest unittest main12494676
Ref: f8612494676
Node: load_tests Protocol12497604
Ref: library/unittest id112497685
Ref: 3e8a12497685
Ref: library/unittest load-tests-protocol12497685
Ref: 3e3112497685
Node: Class and Module Fixtures12500351
Ref: library/unittest class-and-module-fixtures12500498
Ref: 3e9912500498
Node: setUpClass and tearDownClass12502382
Ref: library/unittest setupclass-and-teardownclass12502511
Ref: 3ecb12502511
Node: setUpModule and tearDownModule12503425
Ref: library/unittest setupmodule-and-teardownmodule12503554
Ref: 3ecc12503554
Ref: library/unittest unittest addModuleCleanup12504167
Ref: 9f012504167
Ref: library/unittest unittest enterModuleContext12504745
Ref: 66112504745
Ref: library/unittest unittest doModuleCleanups12505077
Ref: 174112505077
Node: Signal Handling12505695
Ref: library/unittest signal-handling12505812
Ref: 3e7c12505812
Ref: library/unittest unittest installHandler12507044
Ref: 3ecd12507044
Ref: library/unittest unittest registerResult12507286
Ref: 3ece12507286
Ref: library/unittest unittest removeResult12507778
Ref: 3ecf12507778
Ref: library/unittest unittest removeHandler12507998
Ref: 12c812507998
Node: unittest mock — mock 物件函式庫12508386
Ref: library/unittest mock doc12508552
Ref: 3ed012508552
Ref: library/unittest mock module-unittest mock12508552
Ref: f012508552
Ref: library/unittest mock unittest-mock-mock-object-library12508552
Ref: 3ed112508552
Ref: unittest mock — mock 物件函式庫-Footnote-112510241
Ref: unittest mock — mock 物件函式庫-Footnote-212510314
Node: 快速導引12510353
Ref: library/unittest mock quick-guide12510460
Ref: 3ed212510460
Node: Mock 類別12515723
Ref: library/unittest mock the-mock-class12515847
Ref: 3ed612515847
Ref: library/unittest mock unittest mock Mock12516815
Ref: 9ef12516815
Ref: library/unittest mock unittest mock Mock assert_called12520065
Ref: c9f12520065
Ref: library/unittest mock unittest mock Mock assert_called_once12520347
Ref: ca012520347
Ref: library/unittest mock unittest mock Mock assert_called_with12520973
Ref: 192712520973
Ref: library/unittest mock unittest mock Mock assert_called_once_with12521359
Ref: 3edd12521359
Ref: library/unittest mock unittest mock Mock assert_any_call12522013
Ref: 3ede12522013
Ref: library/unittest mock unittest mock Mock assert_has_calls12522683
Ref: 15a012522683
Ref: library/unittest mock unittest mock Mock assert_not_called12523573
Ref: e3212523573
Ref: library/unittest mock unittest mock Mock reset_mock12524039
Ref: ca112524039
Ref: library/unittest mock unittest mock Mock mock_add_spec12525125
Ref: 3ee012525125
Ref: library/unittest mock unittest mock Mock attach_mock12525472
Ref: 150212525472
Ref: library/unittest mock unittest mock Mock configure_mock12525766
Ref: 3edc12525766
Ref: library/unittest mock unittest mock Mock __dir__12526982
Ref: 3ee212526982
Ref: library/unittest mock unittest mock Mock _get_child_mock12527308
Ref: 3ee412527308
Ref: library/unittest mock unittest mock Mock called12527713
Ref: 3ee512527713
Ref: library/unittest mock unittest mock Mock call_count12528001
Ref: 3ee612528001
Ref: library/unittest mock unittest mock Mock return_value12528306
Ref: 3edb12528306
Ref: library/unittest mock unittest mock Mock side_effect12529092
Ref: 3ed912529092
Ref: library/unittest mock unittest mock Mock call_args12531547
Ref: 188412531547
Ref: library/unittest mock unittest mock Mock call_args_list12533273
Ref: 3ee712533273
Ref: library/unittest mock unittest mock Mock method_calls12534263
Ref: 3ee112534263
Ref: library/unittest mock unittest mock Mock mock_calls12535009
Ref: 3edf12535009
Ref: library/unittest mock unittest mock Mock __class__12536524
Ref: 3ee912536524
Ref: library/unittest mock unittest mock NonCallableMock12537252
Ref: 3ed712537252
Ref: library/unittest mock unittest mock PropertyMock12539705
Ref: 3eea12539705
Ref: library/unittest mock unittest mock AsyncMock12541577
Ref: 9ee12541577
Ref: library/unittest mock unittest mock AsyncMock assert_awaited12544294
Ref: 3eeb12544294
Ref: library/unittest mock unittest mock AsyncMock assert_awaited_once12545000
Ref: 3eec12545000
Ref: library/unittest mock unittest mock AsyncMock assert_awaited_with12545551
Ref: 3eed12545551
Ref: library/unittest mock unittest mock AsyncMock assert_awaited_once_with12546212
Ref: 3eee12546212
Ref: library/unittest mock unittest mock AsyncMock assert_any_await12546911
Ref: 3eef12546911
Ref: library/unittest mock unittest mock AsyncMock assert_has_awaits12547531
Ref: 3ef012547531
Ref: library/unittest mock unittest mock AsyncMock assert_not_awaited12548638
Ref: 3ef112548638
Ref: library/unittest mock unittest mock AsyncMock reset_mock12548804
Ref: 3ef212548804
Ref: library/unittest mock unittest mock AsyncMock await_count12549053
Ref: 3ef312549053
Ref: library/unittest mock unittest mock AsyncMock await_args12549473
Ref: 3ef412549473
Ref: library/unittest mock unittest mock AsyncMock await_args_list12550070
Ref: 188312550070
Ref: library/unittest mock unittest mock ThreadingMock12550742
Ref: 3ef512550742
Ref: library/unittest mock unittest mock ThreadingMock wait_until_called12551450
Ref: 3ef712551450
Ref: library/unittest mock unittest mock ThreadingMock wait_until_any_call_with12552003
Ref: 3ef812552003
Ref: library/unittest mock unittest mock ThreadingMock DEFAULT_TIMEOUT12552602
Ref: 3ef612552602
Ref: Mock 類別-Footnote-112552909
Node: 呼叫12553301
Ref: library/unittest mock calling12553376
Ref: 3ef912553376
Node: 刪除屬性12556554
Ref: library/unittest mock deleting-attributes12556664
Ref: 3efa12556664
Ref: library/unittest mock id212556664
Ref: 3efb12556664
Node: Mock 名稱與名稱屬性12557434
Ref: library/unittest mock mock-names-and-the-name-attribute12557567
Ref: 3efc12557567
Node: 如同屬性一般附加 mock12558117
Ref: library/unittest mock attaching-mocks-as-attributes12558229
Ref: 3efd12558229
Node: Patchers12560071
Ref: library/unittest mock the-patchers12560217
Ref: 3efe12560217
Node: patch12560844
Ref: library/unittest mock patch12560915
Ref: 3eff12560915
Ref: library/unittest mock unittest mock patch12561064
Ref: e3412561064
Node: patch object12569798
Ref: library/unittest mock patch-object12569888
Ref: 3f0112569888
Ref: library/unittest mock unittest mock patch object12569933
Ref: 18bb12569933
Node: patch dict12571397
Ref: library/unittest mock patch-dict12571496
Ref: 3f0212571496
Ref: library/unittest mock unittest mock patch dict12571539
Ref: 18f812571539
Node: patch multiple12575533
Ref: library/unittest mock patch-multiple12575650
Ref: 3f0412575650
Ref: library/unittest mock unittest mock patch multiple12575701
Ref: 3f0512575701
Node: patch 方法：啟動與停止12578407
Ref: library/unittest mock patch-methods-start-and-stop12578532
Ref: 3f0612578532
Ref: library/unittest mock start-and-stop12578532
Ref: 3f0712578532
Ref: library/unittest mock unittest mock patch stopall12581269
Ref: 3f0812581269
Node: patch 內建函式12581379
Ref: library/unittest mock id412581501
Ref: 3f0912581501
Ref: library/unittest mock patch-builtins12581501
Ref: 3f0a12581501
Node: TEST_PREFIX12581826
Ref: library/unittest mock id512581946
Ref: 3f0b12581946
Ref: library/unittest mock test-prefix12581946
Ref: 3f0312581946
Node: 巢狀使用 Patch 裝飾器12582794
Ref: library/unittest mock nesting-patch-decorators12582912
Ref: 3f0c12582912
Node: 該 patch 何處12583789
Ref: library/unittest mock id612583940
Ref: 3f0012583940
Ref: library/unittest mock where-to-patch12583940
Ref: 3ed312583940
Node: Patch 描述器與代理物件 Proxy Objects12585690
Ref: library/unittest mock patching-descriptors-and-proxy-objects12585804
Ref: 3f0d12585804
Ref: Patch 描述器與代理物件 Proxy Objects-Footnote-112586229
Node: MagicMock 以及魔術方法支援12586354
Ref: library/unittest mock magicmock-and-magic-method-support12586504
Ref: 3f0e12586504
Node: Mock 魔術方法12586634
Ref: library/unittest mock magic-methods12586741
Ref: 3ed412586741
Ref: library/unittest mock mocking-magic-methods12586741
Ref: 3f0f12586741
Ref: Mock 魔術方法-Footnote-112590635
Ref: Mock 魔術方法-Footnote-212590834
Node: Magic Mock12590939
Ref: library/unittest mock magic-mock12591046
Ref: 3f1112591046
Ref: library/unittest mock unittest mock MagicMock12591187
Ref: e3312591187
Ref: library/unittest mock unittest mock NonCallableMagicMock12591634
Ref: 3ed812591634
Node: 輔助函式<2>12594894
Ref: library/unittest mock helpers12595088
Ref: 3f1212595088
Node: sentinel（哨兵）12595295
Ref: library/unittest mock sentinel12595383
Ref: 3f1312595383
Ref: library/unittest mock unittest mock sentinel12595442
Ref: b4712595442
Node: DEFAULT12596535
Ref: library/unittest mock default12596636
Ref: 3f1412596636
Ref: library/unittest mock unittest mock DEFAULT12596673
Ref: 3eda12596673
Node: call12596922
Ref: library/unittest mock call12597018
Ref: 3f1512597018
Ref: library/unittest mock unittest mock call12597049
Ref: 18d312597049
Ref: library/unittest mock unittest mock call call_list12597595
Ref: 3f1612597595
Ref: library/unittest mock calls-as-tuples12598496
Ref: 3ee812598496
Node: create_autospec12600057
Ref: library/unittest mock create-autospec12600149
Ref: 3f1712600149
Ref: library/unittest mock unittest mock create_autospec12600202
Ref: 14fb12600202
Node: ANY12601502
Ref: library/unittest mock any12601600
Ref: 3f1812601600
Ref: library/unittest mock unittest mock ANY12601629
Ref: 18d112601629
Node: FILTER_DIR12602719
Ref: library/unittest mock filter-dir12602811
Ref: 3f1912602811
Ref: library/unittest mock unittest mock FILTER_DIR12602854
Ref: 3ee312602854
Node: mock_open12604806
Ref: library/unittest mock mock-open12604925
Ref: 3f1a12604925
Ref: library/unittest mock unittest mock mock_open12604966
Ref: 160612604966
Ref: mock_open-Footnote-112607701
Node: Autospeccing（自動規格）12607726
Ref: library/unittest mock auto-speccing12607846
Ref: 3ed512607846
Ref: library/unittest mock autospeccing12607846
Ref: 3f1b12607846
Ref: Autospeccing（自動規格）-Footnote-112616217
Node: 密封 mock12616420
Ref: library/unittest mock sealing-mocks12616522
Ref: 3f1c12616522
Ref: library/unittest mock unittest mock seal12616565
Ref: b4812616565
Node: side_effect、return_value 和 wraps 的優先順序12617305
Ref: library/unittest mock order-of-precedence-of-side-effect-return-value-and-wraps12617456
Ref: 3f1d12617456
Node: unittest mock --- 入門指南12621308
Ref: library/unittest mock-examples doc12621498
Ref: 3f1e12621498
Ref: library/unittest mock-examples unittest-mock-getting-started12621498
Ref: 3f1f12621498
Ref: library/unittest mock-examples getting-started12621600
Ref: 3f2012621600
Node: 使用 Mock 的方式12621673
Ref: library/unittest mock-examples using-mock12621785
Ref: 3f2112621785
Node: 使用 Mock 來 patching 方法12622254
Ref: library/unittest mock-examples mock-patching-methods12622387
Ref: 3f2212622387
Node: 對物件的方法呼叫使用 mock12623971
Ref: library/unittest mock-examples mock-for-method-calls-on-an-object12624127
Ref: 3f2312624127
Node: Mock 類別<2>12625289
Ref: library/unittest mock-examples mocking-classes12625431
Ref: 3f2412625431
Node: 命名你的 mock12626408
Ref: library/unittest mock-examples naming-your-mocks12626533
Ref: 3f2512626533
Node: 追蹤所有呼叫12626955
Ref: library/unittest mock-examples tracking-all-calls12627090
Ref: 3f2612627090
Node: 設定回傳值和屬性12628400
Ref: library/unittest mock-examples setting-return-values-and-attributes12628542
Ref: 3f2712628542
Node: 透過 mock 引發例外12630030
Ref: library/unittest mock-examples raising-exceptions-with-mocks12630193
Ref: 3f2812630193
Node: Side effect 函式以及可疊代物件12630541
Ref: library/unittest mock-examples side-effect-functions-and-iterables12630709
Ref: 3f2912630709
Node: Mock 非同步可疊代物件12631731
Ref: library/unittest mock-examples mocking-asynchronous-iterators12631904
Ref: 3f2a12631904
Node: Mock 非同步情境管理器12632439
Ref: library/unittest mock-examples mocking-asynchronous-context-manager12632599
Ref: 3f2b12632599
Node: 從現有物件建立 mock12633477
Ref: library/unittest mock-examples creating-a-mock-from-an-existing-object12633651
Ref: 3f2c12633651
Node: 使用 side_effect 回傳各別檔案內容12635295
Ref: library/unittest mock-examples using-side-effect-to-return-per-file-content12635431
Ref: 3f2d12635431
Node: Patch 裝飾器12636274
Ref: library/unittest mock-examples patch-decorators12636407
Ref: 3f2e12636407
Node: 更多範例12641590
Ref: library/unittest mock-examples further-examples12641693
Ref: 3f2f12641693
Ref: library/unittest mock-examples id112641693
Ref: 3f3012641693
Node: Mock 鍊接呼叫12642259
Ref: library/unittest mock-examples mocking-chained-calls12642348
Ref: 3f3112642348
Node: 部分 mocking12645489
Ref: library/unittest mock-examples partial-mocking12645607
Ref: 3f3212645607
Ref: 部分 mocking-Footnote-112647625
Node: Mock 產生器方法12647726
Ref: library/unittest mock-examples mocking-a-generator-method12647869
Ref: 3f3312647869
Ref: Mock 產生器方法-Footnote-112648923
Node: 對每個測試方法應用相同的 patch12649222
Ref: library/unittest mock-examples applying-the-same-patch-to-every-test-method12649393
Ref: 3f3412649393
Node: Mock Unbound Methods （未繫結方法）12651662
Ref: library/unittest mock-examples mocking-unbound-methods12651843
Ref: 3f3512651843
Node: 使用 mock 檢查多個呼叫12653532
Ref: library/unittest mock-examples checking-multiple-calls-with-mock12653689
Ref: 3f3612653689
Node: 應對可變引數12655248
Ref: library/unittest mock-examples coping-with-mutable-arguments12655381
Ref: 3f3712655381
Node: 巢狀使用 Patch12659436
Ref: library/unittest mock-examples nesting-patches12659571
Ref: 3f3812659571
Node: 使用 MagicMock 來 mock 字典12661414
Ref: library/unittest mock-examples mocking-a-dictionary-with-magicmock12661557
Ref: 3f3912661557
Node: Mock 子類別及其屬性12664148
Ref: library/unittest mock-examples mock-subclasses-and-their-attributes12664306
Ref: 3f3a12664306
Ref: Mock 子類別及其屬性-Footnote-112666289
Ref: Mock 子類別及其屬性-Footnote-212666454
Ref: Mock 子類別及其屬性-Footnote-312666512
Node: 使用 patch dict 來 mock import12666593
Ref: library/unittest mock-examples mocking-imports-with-patch-dict12666764
Ref: 3f3b12666764
Node: 追蹤呼叫順序與更簡潔的呼叫斷言12669460
Ref: library/unittest mock-examples tracking-order-of-calls-and-less-verbose-call-assertions12669629
Ref: 3f3c12669629
Node: 更複雜的引數匹配12672811
Ref: library/unittest mock-examples more-complex-argument-matching12672938
Ref: 3f3d12672938
Ref: 更複雜的引數匹配-Footnote-112675937
Ref: 更複雜的引數匹配-Footnote-212675980
Node: test --- Python 的回歸測試 regression tests 套件12676102
Ref: library/test doc12676299
Ref: 3f3e12676299
Ref: library/test module-test12676299
Ref: cb12676299
Ref: library/test test-regression-tests-package-for-python12676299
Ref: 3f3f12676299
Node: 撰寫 test 套件的單元測試12677718
Ref: library/test writing-tests12677885
Ref: 3f4012677885
Ref: library/test writing-unit-tests-for-the-test-package12677885
Ref: 3f4112677885
Node: 使用命令列介面執行測試12682439
Ref: library/test module-test regrtest12682606
Ref: cc12682606
Ref: library/test regrtest12682606
Ref: faa12682606
Ref: library/test running-tests-using-the-command-line-interface12682606
Ref: 3f4212682606
Node: test support --- Python 測試套件的工具12684506
Ref: library/test module-test support12684733
Ref: cd12684733
Ref: library/test test-support-utilities-for-the-python-test-suite12684733
Ref: 3f4312684733
Ref: library/test test support TestFailed12685193
Ref: 3f4412685193
Ref: library/test test support ResourceDenied12685407
Ref: 3f4512685407
Ref: library/test test support verbose12685684
Ref: 3f4712685684
Ref: library/test test support is_jython12685906
Ref: 3f4812685906
Ref: library/test test support is_android12686006
Ref: 3f4912686006
Ref: library/test test support unix_shell12686096
Ref: 3f4a12686096
Ref: library/test test support LOOPBACK_TIMEOUT12686195
Ref: 18b812686195
Ref: library/test test support INTERNET_TIMEOUT12686787
Ref: 18b912686787
Ref: library/test test support SHORT_TIMEOUT12687286
Ref: 17b112687286
Ref: library/test test support LONG_TIMEOUT12687666
Ref: 18ba12687666
Ref: library/test test support PGO12688172
Ref: 3f4c12688172
Ref: library/test test support PIPE_MAX_SIZE12688272
Ref: 3f4d12688272
Ref: library/test test support Py_DEBUG12688422
Ref: 3f4e12688422
Ref: library/test test support SOCK_MAX_SIZE12688629
Ref: 3f5012688629
Ref: library/test test support TEST_SUPPORT_DIR12688781
Ref: 3f5112688781
Ref: library/test test support TEST_HOME_DIR12688889
Ref: 3f5212688889
Ref: library/test test support TEST_DATA_DIR12688975
Ref: 3f5312688975
Ref: library/test test support MAX_Py_ssize_t12689070
Ref: 3f5412689070
Ref: library/test test support max_memuse12689183
Ref: 3f5512689183
Ref: library/test test support real_max_memuse12689348
Ref: 3f5712689348
Ref: library/test test support MISSING_C_DOCSTRINGS12689522
Ref: 3f5812689522
Ref: library/test test support HAVE_DOCSTRINGS12689811
Ref: 3f5912689811
Ref: library/test test support TEST_HTTP_URL12690085
Ref: 3f5a12690085
Ref: library/test test support ALWAYS_EQ12690196
Ref: 3f5b12690196
Ref: library/test test support NEVER_EQ12690314
Ref: 3f5c12690314
Ref: library/test test support LARGEST12690468
Ref: 3f5d12690468
Ref: library/test test support SMALLEST12690604
Ref: 3f5e12690604
Ref: library/test test support busy_retry12690794
Ref: 3f5f12690794
Ref: library/test test support sleeping_retry12691434
Ref: 3f6012691434
Ref: library/test test support is_resource_enabled12692294
Ref: 3f6112692294
Ref: library/test test support python_is_optimized12692524
Ref: 3f6212692524
Ref: library/test test support with_pymalloc12692660
Ref: 3f6312692660
Ref: library/test test support requires12692749
Ref: 3f4612692749
Ref: library/test test support sortdict12693118
Ref: 3f6412693118
Ref: library/test test support findfile12693208
Ref: 3f6512693208
Ref: library/test test support get_pagesize12693578
Ref: 3f6612693578
Ref: library/test test support setswitchinterval12693684
Ref: 3f6712693684
Ref: library/test test support check_impl_detail12693908
Ref: 3f6812693908
Ref: library/test test support set_memlimit12694422
Ref: 3f5612694422
Ref: library/test test support record_original_stdout12694578
Ref: 3f6912694578
Ref: library/test test support get_original_stdout12694742
Ref: 3f6a12694742
Ref: library/test test support args_from_interpreter_flags12694911
Ref: 3f6b12694911
Ref: library/test test support optim_args_from_interpreter_flags12695098
Ref: 3f6c12695098
Ref: library/test test support captured_stdin12695278
Ref: 3f6d12695278
Ref: library/test test support captured_stdout12695321
Ref: 3f6e12695321
Ref: library/test test support captured_stderr12695365
Ref: 18fb12695365
Ref: library/test test support disable_faulthandler12696086
Ref: 3f6f12696086
Ref: library/test test support gc_collect12696208
Ref: 3f7012696208
Ref: library/test test support disable_gc12696542
Ref: 3f7112696542
Ref: library/test test support swap_attr12696721
Ref: 3f7212696721
Ref: library/test test support swap_item12697300
Ref: 3f7312697300
Ref: library/test test support flush_std_streams12697877
Ref: 3f7412697877
Ref: library/test test support print_warning12698151
Ref: 3f7512698151
Ref: library/test test support wait_process12698423
Ref: 187812698423
Ref: library/test test support calcobjsize12698936
Ref: 3f7712698936
Ref: library/test test support calcvobjsize12699167
Ref: 3f7812699167
Ref: library/test test support checksizeof12699403
Ref: 3f7a12699403
Ref: library/test test support anticipate_failure12699572
Ref: 3f7b12699572
Ref: library/test test support system_must_validate_cert12699832
Ref: 3f7c12699832
Ref: library/test test support run_with_locale12699983
Ref: 3f7d12699983
Ref: library/test test support run_with_tz12700341
Ref: 3f7e12700341
Ref: library/test test support requires_freebsd_version12700501
Ref: 3f7f12700501
Ref: library/test test support requires_linux_version12700713
Ref: 3f8012700713
Ref: library/test test support requires_mac_version12700920
Ref: 3f8112700920
Ref: library/test test support requires_gil_enabled12701124
Ref: 3f8212701124
Ref: library/test test support requires_IEEE_75412701298
Ref: 3f8312701298
Ref: library/test test support requires_zlib12701405
Ref: 3f8412701405
Ref: library/test test support requires_gzip12701516
Ref: 3f8512701516
Ref: library/test test support requires_bz212701626
Ref: 3f8612701626
Ref: library/test test support requires_lzma12701733
Ref: 3f8712701733
Ref: library/test test support requires_resource12701843
Ref: 3f8812701843
Ref: library/test test support requires_docstrings12701963
Ref: 3f8912701963
Ref: library/test test support requires_limited_api12702084
Ref: 3f8a12702084
Ref: library/test test support cpython_only12702222
Ref: 3f8b12702222
Ref: library/test test support impl_detail12702316
Ref: 3f8c12702316
Ref: library/test test support no_tracing12702544
Ref: 3f8d12702544
Ref: library/test test support refcount_test12702665
Ref: 3f8e12702665
Ref: library/test test support bigmemtest12702967
Ref: 3f8f12702967
Ref: library/test test support bigaddrspacetest12703716
Ref: 3f9012703716
Ref: library/test test support check_syntax_error12703815
Ref: 3f9112703815
Ref: library/test test support open_urlresource12704366
Ref: 3f9212704366
Ref: library/test test support reap_children12704493
Ref: 3f9312704493
Ref: library/test test support get_attribute12704765
Ref: 3f9412704765
Ref: library/test test support catch_unraisable_exception12704925
Ref: 18dd12704925
Ref: library/test test support load_package_tests12705814
Ref: 3f9512705814
Ref: library/test test support detect_api_mismatch12706439
Ref: 3f9612706439
Ref: library/test test support patch12706885
Ref: 3f9712706885
Ref: library/test test support run_in_subinterp12707219
Ref: 3f9812707219
Ref: library/test test support check_free_after_iterating12707385
Ref: 3f9912707385
Ref: library/test test support missing_compiler_executable12707540
Ref: 3f9a12707540
Ref: library/test test support check__all__12707860
Ref: 184e12707860
Ref: library/test test support skip_if_broken_multiprocessing_synchronize12709666
Ref: 184f12709666
Ref: library/test test support check_disallow_instantiation12709957
Ref: 3f9b12709957
Ref: library/test test support adjust_int_max_str_digits12710163
Ref: 3f9c12710163
Ref: library/test test support SuppressCrashReport12710621
Ref: 3f9d12710621
Ref: library/test test support SaveSignals12711114
Ref: 3fa012711114
Ref: library/test test support SaveSignals save12711246
Ref: 3fa112711246
Ref: library/test test support SaveSignals restore12711392
Ref: 3fa212711392
Ref: library/test test support Matcher12711531
Ref: 3fa312711531
Ref: library/test test support Matcher matches12711565
Ref: 3fa412711565
Ref: library/test test support Matcher match_value12711678
Ref: 3fa512711678
Ref: test support --- Python 測試套件的工具-Footnote-112711853
Node: test support socket_helper --- 用於 socket 測試的工具12711933
Ref: library/test module-test support socket_helper12712171
Ref: d212712171
Ref: library/test test-support-socket-helper-utilities-for-socket-tests12712171
Ref: 3fa612712171
Ref: library/test test support socket_helper IPV6_ENABLED12712417
Ref: 3fa712712417
Ref: library/test test support socket_helper find_unused_port12712550
Ref: 3fa812712550
Ref: library/test test support socket_helper bind_port12713869
Ref: 3fa912713869
Ref: library/test test support socket_helper bind_unix_socket12714812
Ref: 3faa12714812
Ref: library/test test support socket_helper skip_unless_bind_unix_socket12714993
Ref: 3fab12714993
Ref: library/test test support socket_helper transient_internet12715161
Ref: 3f4b12715161
Node: test support script_helper --- 用於 Python 執行測試的工具12715432
Ref: library/test module-test support script_helper12715712
Ref: d112715712
Ref: library/test test-support-script-helper-utilities-for-the-python-execution-tests12715712
Ref: 3fac12715712
Ref: library/test test support script_helper interpreter_requires_environment12715954
Ref: 3fad12715954
Ref: library/test test support script_helper run_python_until_end12716913
Ref: 3fae12716913
Ref: library/test test support script_helper assert_python_ok12717272
Ref: 3faf12717272
Ref: library/test test support script_helper assert_python_failure12717886
Ref: 3fb012717886
Ref: library/test test support script_helper spawn_python12718301
Ref: 3fb112718301
Ref: library/test test support script_helper kill_python12718612
Ref: 3fb212718612
Ref: library/test test support script_helper make_script12718766
Ref: 3fb312718766
Ref: library/test test support script_helper make_zip_script12719073
Ref: 3fb412719073
Ref: library/test test support script_helper make_pkg12719440
Ref: 3fb512719440
Ref: library/test test support script_helper make_zip_pkg12719631
Ref: 3fb612719631
Node: test support bytecode_helper --- 用於測試位元組碼能正確產生的支援工具12720159
Ref: library/test module-test support bytecode_helper12720442
Ref: ce12720442
Ref: library/test test-support-bytecode-helper-support-tools-for-testing-correct-bytecode-generation12720442
Ref: 3fb712720442
Ref: library/test test support bytecode_helper BytecodeTestCase12720781
Ref: 3fb812720781
Ref: library/test test support bytecode_helper BytecodeTestCase get_disassembly_as_string12720941
Ref: 3fb912720941
Ref: library/test test support bytecode_helper BytecodeTestCase assertInBytecode12721050
Ref: 3fba12721050
Ref: library/test test support bytecode_helper BytecodeTestCase assertNotInBytecode12721230
Ref: 3fbb12721230
Node: test support threading_helper --- Utilities for threading tests12721385
Ref: library/test module-test support threading_helper12721654
Ref: d312721654
Ref: library/test test-support-threading-helper-utilities-for-threading-tests12721654
Ref: 3fbc12721654
Ref: library/test test support threading_helper join_thread12721920
Ref: 3fbd12721920
Ref: library/test test support threading_helper reap_threads12722140
Ref: 3fbe12722140
Ref: library/test test support threading_helper start_threads12722279
Ref: 3fbf12722279
Ref: library/test test support threading_helper threading_cleanup12722685
Ref: 3fc012722685
Ref: library/test test support threading_helper threading_setup12722921
Ref: 3fc112722921
Ref: library/test test support threading_helper wait_threads_exit12723047
Ref: 3fc212723047
Ref: library/test test support threading_helper catch_threading_exception12723218
Ref: 3fc312723218
Node: test support os_helper --- 用於 os 測試的工具12724174
Ref: library/test module-test support os_helper12724416
Ref: d012724416
Ref: library/test test-support-os-helper-utilities-for-os-tests12724416
Ref: 3fc412724416
Ref: library/test test support os_helper FS_NONASCII12724632
Ref: 3fc512724632
Ref: library/test test support os_helper SAVEDCWD12724747
Ref: 3fc612724747
Ref: library/test test support os_helper TESTFN12724836
Ref: 3fc712724836
Ref: library/test test support os_helper TESTFN_NONASCII12725038
Ref: 3fc812725038
Ref: library/test test support os_helper TESTFN_UNENCODABLE12725423
Ref: 3fc912725423
Ref: library/test test support os_helper TESTFN_UNDECODABLE12725673
Ref: 3fca12725673
Ref: library/test test support os_helper TESTFN_UNICODE12725925
Ref: 3fcb12725925
Ref: library/test test support os_helper EnvironmentVarGuard12726028
Ref: 135012726028
Ref: library/test test support os_helper FakePath12726489
Ref: 3fcc12726489
Ref: library/test test support os_helper EnvironmentVarGuard set12726752
Ref: 3fcd12726752
Ref: library/test test support os_helper EnvironmentVarGuard unset12726899
Ref: 3fce12726899
Ref: library/test test support os_helper can_symlink12726994
Ref: 3fcf12726994
Ref: library/test test support os_helper can_xattr12727138
Ref: 3fd012727138
Ref: library/test test support os_helper change_cwd12727275
Ref: 3fd112727275
Ref: library/test test support os_helper create_empty_file12727642
Ref: 3fd212727642
Ref: library/test test support os_helper fd_count12727792
Ref: 3fd312727792
Ref: library/test test support os_helper fs_is_case_insensitive12727889
Ref: 3fd412727889
Ref: library/test test support os_helper make_bad_fd12728045
Ref: 3fd512728045
Ref: library/test test support os_helper rmdir12728212
Ref: 3fd612728212
Ref: library/test test support os_helper rmtree12728518
Ref: 3fd712728518
Ref: library/test test support os_helper skip_unless_symlink12728859
Ref: 3fd812728859
Ref: library/test test support os_helper skip_unless_xattr12728998
Ref: 3fd912728998
Ref: library/test test support os_helper temp_cwd12729121
Ref: 3fda12729121
Ref: library/test test support os_helper temp_dir12729766
Ref: 3fdb12729766
Ref: library/test test support os_helper temp_umask12730216
Ref: 3fdc12730216
Ref: library/test test support os_helper unlink12730336
Ref: 3fdd12730336
Node: test support import_helper --- 用於 import 測試的工具12730579
Ref: library/test module-test support import_helper12730822
Ref: cf12730822
Ref: library/test test-support-import-helper-utilities-for-import-tests12730822
Ref: 3fde12730822
Ref: library/test test support import_helper forget12731062
Ref: 3fdf12731062
Ref: library/test test support import_helper import_fresh_module12731245
Ref: 17b012731245
Ref: library/test test support import_helper import_module12732851
Ref: 3fe012732851
Ref: library/test test support import_helper modules_setup12733470
Ref: 3fe112733470
Ref: library/test test support import_helper modules_cleanup12733578
Ref: 3fe212733578
Ref: library/test test support import_helper unload12733754
Ref: 3fe312733754
Ref: library/test test support import_helper make_legacy_pyc12733856
Ref: 3fe412733856
Ref: library/test test support import_helper CleanImport12734203
Ref: 3fe512734203
Ref: library/test test support import_helper DirsOnSysPath12734594
Ref: 3fe612734594
Ref: test support import_helper --- 用於 import 測試的工具-Footnote-112735152
Ref: test support import_helper --- 用於 import 測試的工具-Footnote-212735194
Node: test support warnings_helper --- 用於 warnings 測試的工具12735236
Ref: library/test module-test support warnings_helper12735418
Ref: d412735418
Ref: library/test test-support-warnings-helper-utilities-for-warnings-tests12735418
Ref: 3fe712735418
Ref: library/test test support warnings_helper ignore_warnings12735670
Ref: 3fe812735670
Ref: library/test test support warnings_helper check_no_resource_warning12736181
Ref: 3fe912736181
Ref: library/test test support warnings_helper check_syntax_warning12736469
Ref: 3fea12736469
Ref: library/test test support warnings_helper check_warnings12737285
Ref: 3feb12737285
Ref: library/test test support warnings_helper WarningsRecorder12740334
Ref: 3fec12740334
Node: 除錯與效能分析12740526
Ref: library/debug doc12740674
Ref: 3fed12740674
Ref: library/debug debugging-and-profiling12740674
Ref: 3fee12740674
Ref: library/audit_events audit-events12741160
Ref: 177312741160
Node: 稽核事件表12741670
Ref: library/audit_events doc12741775
Ref: 3fef12741775
Ref: library/audit_events audit-events-table12741775
Ref: 3ff012741775
Ref: 稽核事件表-Footnote-112800325
Node: bdb --- 偵錯器框架12800367
Ref: library/bdb doc12800518
Ref: 400f12800518
Ref: library/bdb bdb-debugger-framework12800518
Ref: 401012800518
Ref: library/bdb module-bdb12800518
Ref: b12800518
Ref: library/bdb bdb BdbQuit12800830
Ref: 401112800830
Ref: library/bdb bdb Breakpoint12800983
Ref: 401212800983
Ref: library/bdb bdb Breakpoint deleteMe12801925
Ref: 401912801925
Ref: library/bdb bdb Breakpoint enable12802141
Ref: 401a12802141
Ref: library/bdb bdb Breakpoint disable12802212
Ref: 401b12802212
Ref: library/bdb bdb Breakpoint bpformat12802285
Ref: 401c12802285
Ref: library/bdb bdb Breakpoint bpprint12802682
Ref: 401d12802682
Ref: library/bdb bdb Breakpoint file12802918
Ref: 401512802918
Ref: library/bdb bdb Breakpoint line12802993
Ref: 401e12802993
Ref: library/bdb bdb Breakpoint temporary12803105
Ref: 401f12803105
Ref: library/bdb bdb Breakpoint cond12803224
Ref: 401812803224
Ref: library/bdb bdb Breakpoint funcname12803336
Ref: 401612803336
Ref: library/bdb bdb Breakpoint enabled12803480
Ref: 402012803480
Ref: library/bdb bdb Breakpoint bpbynumber12803578
Ref: 401312803578
Ref: library/bdb bdb Breakpoint bplist12803693
Ref: 401412803693
Ref: library/bdb bdb Breakpoint ignore12803844
Ref: 402112803844
Ref: library/bdb bdb Breakpoint hits12803932
Ref: 401712803932
Ref: library/bdb bdb Bdb12804045
Ref: 129512804045
Ref: library/bdb bdb Bdb canonic12804836
Ref: 402212804836
Ref: library/bdb bdb Bdb reset12805215
Ref: 402312805215
Ref: library/bdb bdb Bdb trace_dispatch12805407
Ref: 402512805407
Ref: library/bdb bdb Bdb dispatch_line12806807
Ref: 402612806807
Ref: library/bdb bdb Bdb dispatch_call12807284
Ref: 402812807284
Ref: library/bdb bdb Bdb dispatch_return12807768
Ref: 402a12807768
Ref: library/bdb bdb Bdb dispatch_exception12808260
Ref: 402c12808260
Ref: library/bdb bdb Bdb is_skipped_line12808917
Ref: 402e12808917
Ref: library/bdb bdb Bdb stop_here12809037
Ref: 402f12809037
Ref: library/bdb bdb Bdb break_here12809165
Ref: 403012809165
Ref: library/bdb bdb Bdb break_anywhere12809473
Ref: 403212809473
Ref: library/bdb bdb Bdb user_call12809689
Ref: 402912809689
Ref: library/bdb bdb Bdb user_line12809990
Ref: 402712809990
Ref: library/bdb bdb Bdb user_return12810184
Ref: 402b12810184
Ref: library/bdb bdb Bdb user_exception12810350
Ref: 402d12810350
Ref: library/bdb bdb Bdb do_clear12810518
Ref: 403312810518
Ref: library/bdb bdb Bdb set_step12810803
Ref: 403412810803
Ref: library/bdb bdb Bdb set_next12810873
Ref: 403512810873
Ref: library/bdb bdb Bdb set_return12810970
Ref: 403612810970
Ref: library/bdb bdb Bdb set_until12811060
Ref: 403712811060
Ref: library/bdb bdb Bdb set_trace12811245
Ref: 403812811245
Ref: library/bdb bdb Bdb set_continue12811571
Ref: 403a12811571
Ref: library/bdb bdb Bdb set_quit12811744
Ref: 402412811744
Ref: library/bdb bdb Bdb set_break12812162
Ref: 403b12812162
Ref: library/bdb bdb Bdb clear_break12812525
Ref: 403c12812525
Ref: library/bdb bdb Bdb clear_bpbynumber12812690
Ref: 403d12812690
Ref: library/bdb bdb Bdb clear_all_file_breaks12812919
Ref: 403e12812919
Ref: library/bdb bdb Bdb clear_all_breaks12813073
Ref: 403f12813073
Ref: library/bdb bdb Bdb get_bpbynumber12813209
Ref: 404012813209
Ref: library/bdb bdb Bdb get_break12813560
Ref: 404112813560
Ref: library/bdb bdb Bdb get_breaks12813699
Ref: 404212813699
Ref: library/bdb bdb Bdb get_file_breaks12813853
Ref: 404312813853
Ref: library/bdb bdb Bdb get_all_breaks12813991
Ref: 404412813991
Ref: library/bdb bdb Bdb get_stack12814197
Ref: 404512814197
Ref: library/bdb bdb Bdb format_stack_entry12814488
Ref: 404612814488
Ref: library/bdb bdb Bdb run12815058
Ref: 404712815058
Ref: library/bdb bdb Bdb runeval12815288
Ref: 404812815288
Ref: library/bdb bdb Bdb runctx12815516
Ref: 404912815516
Ref: library/bdb bdb Bdb runcall12815652
Ref: a2112815652
Ref: library/bdb bdb checkfuncname12815821
Ref: 404a12815821
Ref: library/bdb bdb effective12816272
Ref: 403112816272
Ref: library/bdb bdb set_trace12817038
Ref: 403912817038
Ref: bdb --- 偵錯器框架-Footnote-112817185
Node: faulthandler --- 傾印 Python 回溯12817248
Ref: library/faulthandler doc12817411
Ref: 404b12817411
Ref: library/faulthandler faulthandler-dump-the-python-traceback12817411
Ref: 404c12817411
Ref: library/faulthandler module-faulthandler12817411
Ref: 4e12817411
Node: Dumping the traceback12819793
Ref: library/faulthandler dumping-the-traceback12819916
Ref: 404d12819916
Ref: library/faulthandler faulthandler dump_traceback12819979
Ref: da412819979
Node: Fault handler state12820401
Ref: library/faulthandler fault-handler-state12820571
Ref: 404e12820571
Ref: library/faulthandler faulthandler enable12820630
Ref: c4512820630
Ref: library/faulthandler faulthandler disable12821478
Ref: 405012821478
Ref: library/faulthandler faulthandler is_enabled12821617
Ref: 405112821617
Node: Dumping the tracebacks after a timeout12821702
Ref: library/faulthandler dumping-the-tracebacks-after-a-timeout12821889
Ref: 405212821889
Ref: library/faulthandler faulthandler dump_traceback_later12821986
Ref: da512821986
Ref: library/faulthandler faulthandler cancel_dump_traceback_later12823010
Ref: 405312823010
Node: Dumping the traceback on a user signal12823132
Ref: library/faulthandler dumping-the-traceback-on-a-user-signal12823327
Ref: 405412823327
Ref: library/faulthandler faulthandler register12823424
Ref: da312823424
Ref: library/faulthandler faulthandler unregister12824051
Ref: 405512824051
Node: Issue with file descriptors12824324
Ref: library/faulthandler faulthandler-fd12824491
Ref: 404f12824491
Ref: library/faulthandler issue-with-file-descriptors12824491
Ref: 405612824491
Node: 範例<41>12824959
Ref: library/faulthandler example12825079
Ref: 405712825079
Node: pdb --- The Python Debugger12825619
Ref: library/pdb doc12825778
Ref: 405812825778
Ref: library/pdb debugger12825778
Ref: 405912825778
Ref: library/pdb module-pdb12825778
Ref: 9412825778
Ref: library/pdb pdb-the-python-debugger12825778
Ref: 405a12825778
Ref: library/pdb pdb run12829612
Ref: 3e6412829612
Ref: library/pdb pdb runeval12830302
Ref: 405f12830302
Ref: library/pdb pdb runcall12830613
Ref: 406012830613
Ref: library/pdb pdb set_trace12830926
Ref: 21a12830926
Ref: library/pdb pdb post_mortem12831486
Ref: 134812831486
Ref: library/pdb pdb pm12831775
Ref: 21c12831775
Ref: library/pdb pdb Pdb12832110
Ref: 8c712832110
Ref: library/pdb pdb Pdb run12833499
Ref: 406112833499
Ref: library/pdb pdb Pdb runeval12833559
Ref: 406212833559
Ref: library/pdb pdb Pdb runcall12833624
Ref: 406312833624
Ref: library/pdb pdb Pdb set_trace12833675
Ref: 406412833675
Ref: pdb --- The Python Debugger-Footnote-112833842
Ref: pdb --- The Python Debugger-Footnote-212833905
Ref: pdb --- The Python Debugger-Footnote-312833947
Node: Debugger Commands12834076
Ref: library/pdb debugger-commands12834157
Ref: 405c12834157
Ref: library/pdb id212834157
Ref: 406512834157
Ref: library/pdb pdbcommand-help12837643
Ref: 406812837643
Ref: library/pdb pdbcommand-where12838036
Ref: 406912838036
Ref: library/pdb pdbcommand-down12838236
Ref: 406a12838236
Ref: library/pdb pdbcommand-up12838375
Ref: 406b12838375
Ref: library/pdb pdbcommand-break12838511
Ref: 406c12838511
Ref: library/pdb pdbcommand-tbreak12839635
Ref: 406d12839635
Ref: library/pdb pdbcommand-clear12839846
Ref: 406e12839846
Ref: library/pdb pdbcommand-disable12840143
Ref: 406f12840143
Ref: library/pdb pdbcommand-enable12840466
Ref: 407012840466
Ref: library/pdb pdbcommand-ignore12840554
Ref: 407112840554
Ref: library/pdb pdbcommand-condition12840956
Ref: 407212840956
Ref: library/pdb pdbcommand-commands12841249
Ref: 407312841249
Ref: library/pdb pdbcommand-step12842884
Ref: 405d12842884
Ref: library/pdb pdbcommand-next12843069
Ref: 405e12843069
Ref: library/pdb pdbcommand-until12843467
Ref: 407712843467
Ref: library/pdb pdbcommand-return12843861
Ref: 407412843861
Ref: library/pdb pdbcommand-continue12843948
Ref: 405b12843948
Ref: library/pdb pdbcommand-jump12844048
Ref: 407512844048
Ref: library/pdb pdbcommand-list12844474
Ref: 406612844474
Ref: library/pdb pdbcommand-ll12845220
Ref: 407812845220
Ref: library/pdb pdbcommand-args12845400
Ref: 407912845400
Ref: library/pdb pdbcommand-p12845505
Ref: f1912845505
Ref: library/pdb pdbcommand-pp12845766
Ref: 407a12845766
Ref: library/pdb pdbcommand-whatis12845927
Ref: 407b12845927
Ref: library/pdb pdbcommand-source12846000
Ref: 407c12846000
Ref: library/pdb pdbcommand-display12846124
Ref: 407d12846124
Ref: library/pdb pdbcommand-undisplay12847578
Ref: 407e12847578
Ref: library/pdb pdbcommand-interact12847791
Ref: 407f12847791
Ref: library/pdb debugger-aliases12848690
Ref: 406712848690
Ref: library/pdb pdbcommand-alias12848690
Ref: 408012848690
Ref: library/pdb pdbcommand-unalias12849800
Ref: 408112849800
Ref: library/pdb pdbcommand-012849871
Ref: 408212849871
Ref: library/pdb pdbcommand-run12850358
Ref: 408312850358
Ref: library/pdb pdbcommand-restart12850389
Ref: 408412850389
Ref: library/pdb pdbcommand-quit12850724
Ref: 407612850724
Ref: library/pdb pdbcommand-debug12850818
Ref: 408512850818
Ref: library/pdb pdbcommand-retval12851006
Ref: 408612851006
Ref: library/pdb pdbcommand-exceptions12851104
Ref: 21d12851104
Node: Python 的分析器12852444
Ref: library/profile doc12852616
Ref: 408712852616
Ref: library/profile profile12852616
Ref: 408812852616
Ref: library/profile the-python-profilers12852616
Ref: 408912852616
Ref: Python 的分析器-Footnote-112853041
Ref: Python 的分析器-Footnote-212853108
Node: Introduction to the profilers12853174
Ref: library/profile introduction-to-the-profilers12853289
Ref: 408a12853289
Ref: library/profile profiler-introduction12853289
Ref: 408b12853289
Node: Instant User's Manual12854772
Ref: library/profile instant-user-s-manual12854933
Ref: 408c12854933
Ref: library/profile profile-instant12854933
Ref: 408d12854933
Ref: library/profile profile-cli12857805
Ref: 408f12857805
Node: profile and cProfile Module Reference12861121
Ref: library/profile module-cProfile12861268
Ref: 2012861268
Ref: library/profile profile-and-cprofile-module-reference12861268
Ref: 409312861268
Ref: library/profile module-profile12861379
Ref: 9d12861379
Ref: library/profile profile run12861473
Ref: 409412861473
Ref: library/profile profile runctx12862106
Ref: 409512862106
Ref: library/profile profile Profile12862501
Ref: 98712862501
Ref: library/profile profile Profile enable12864075
Ref: 409612864075
Ref: library/profile profile Profile disable12864176
Ref: 409712864176
Ref: library/profile profile Profile create_stats12864277
Ref: 409812864277
Ref: library/profile profile Profile print_stats12864421
Ref: 409912864421
Ref: library/profile profile Profile dump_stats12864909
Ref: 409a12864909
Ref: library/profile profile Profile run12865016
Ref: 409b12865016
Ref: library/profile profile Profile runctx12865094
Ref: 409c12865094
Ref: library/profile profile Profile runcall12865251
Ref: a2012865251
Node: The Stats Class12865596
Ref: library/profile profile-stats12865754
Ref: 409d12865754
Ref: library/profile the-stats-class12865754
Ref: 409e12865754
Ref: library/profile module-pstats12865888
Ref: 9e12865888
Ref: library/profile pstats Stats12865888
Ref: 408e12865888
Ref: library/profile pstats Stats strip_dirs12867148
Ref: 409112867148
Ref: library/profile pstats Stats add12867966
Ref: 409f12867966
Ref: library/profile pstats Stats dump_stats12868459
Ref: 40a012868459
Ref: library/profile pstats Stats sort_stats12868840
Ref: 409012868840
Ref: library/profile pstats Stats reverse_order12874247
Ref: 40a112874247
Ref: library/profile pstats Stats print_stats12874533
Ref: 409212874533
Ref: library/profile pstats Stats print_callers12875977
Ref: 40a212875977
Ref: library/profile pstats Stats print_callees12877093
Ref: 40a312877093
Ref: library/profile pstats Stats get_stats_profile12877474
Ref: 40a412877474
Node: What Is Deterministic Profiling?12878019
Ref: library/profile deterministic-profiling12878146
Ref: 40a512878146
Ref: library/profile what-is-deterministic-profiling12878146
Ref: 40a612878146
Node: 限制12879938
Ref: library/profile limitations12880056
Ref: 40a712880056
Ref: library/profile profile-limitations12880056
Ref: 40a812880056
Node: 校正12881909
Ref: library/profile calibration12882015
Ref: 40a912882015
Ref: library/profile profile-calibration12882015
Ref: 40aa12882015
Node: Using a custom timer12883684
Ref: library/profile profile-timers12883775
Ref: 40ab12883775
Ref: library/profile using-a-custom-timer12883775
Ref: 40ac12883775
Node: timeit --- 測量小量程式片段的執行時間12886220
Ref: library/timeit doc12886413
Ref: 40ad12886413
Ref: library/timeit module-timeit12886413
Ref: d812886413
Ref: library/timeit timeit-measure-execution-time-of-small-code-snippets12886413
Ref: 40ae12886413
Ref: timeit --- 測量小量程式片段的執行時間-Footnote-112887139
Node: 基礎範例<2>12887205
Ref: library/timeit basic-examples12887329
Ref: 40b112887329
Node: Python 介面12888505
Ref: library/timeit id112888656
Ref: 40b312888656
Ref: library/timeit python-interface12888656
Ref: 40b012888656
Ref: library/timeit timeit timeit12888763
Ref: e2212888763
Ref: library/timeit timeit repeat12889196
Ref: 40b412889196
Ref: library/timeit timeit default_timer12889749
Ref: 40b612889749
Ref: library/timeit timeit Timer12890023
Ref: 143312890023
Ref: library/timeit timeit Timer timeit12891386
Ref: c9412891386
Ref: library/timeit timeit Timer autorange12892294
Ref: c9312892294
Ref: library/timeit timeit Timer repeat12892936
Ref: 40b512892936
Ref: library/timeit timeit Timer print_exc12894018
Ref: 40b712894018
Node: 命令列介面<4>12894578
Ref: library/timeit command-line-interface12894724
Ref: 40b812894724
Ref: library/timeit timeit-command-line-interface12894724
Ref: 40af12894724
Ref: library/timeit cmdoption-timeit-n12894943
Ref: 40b912894943
Ref: library/timeit cmdoption-timeit-number12894943
Ref: 40ba12894943
Ref: library/timeit cmdoption-timeit-r12895008
Ref: 40bb12895008
Ref: library/timeit cmdoption-timeit-repeat12895008
Ref: 40bc12895008
Ref: library/timeit cmdoption-timeit-s12895083
Ref: 40bd12895083
Ref: library/timeit cmdoption-timeit-setup12895083
Ref: 40be12895083
Ref: library/timeit cmdoption-timeit-p12895184
Ref: 40bf12895184
Ref: library/timeit cmdoption-timeit-process12895184
Ref: 40c012895184
Ref: library/timeit cmdoption-timeit-u12895427
Ref: 40c112895427
Ref: library/timeit cmdoption-timeit-unit12895427
Ref: 40c212895427
Ref: library/timeit cmdoption-timeit-v12895590
Ref: 40c312895590
Ref: library/timeit cmdoption-timeit-verbose12895590
Ref: 40c412895590
Ref: library/timeit cmdoption-timeit-h12895693
Ref: 40c512895693
Ref: library/timeit cmdoption-timeit-help12895693
Ref: 40c612895693
Node: 範例<42>12896831
Ref: library/timeit examples12896955
Ref: 40c712896955
Ref: library/timeit timeit-examples12896955
Ref: 40b212896955
Node: trace --- 追蹤或追查 Python 陳述式執行12900453
Ref: library/trace doc12900664
Ref: 40c812900664
Ref: library/trace module-trace12900664
Ref: e612900664
Ref: library/trace trace-trace-or-track-python-statement-execution12900664
Ref: 40c912900664
Ref: trace --- 追蹤或追查 Python 陳述式執行-Footnote-112901390
Ref: trace --- 追蹤或追查 Python 陳述式執行-Footnote-212901455
Node: Command-Line Usage12901496
Ref: library/trace command-line-usage12901630
Ref: 40ca12901630
Ref: library/trace trace-cli12901630
Ref: 40cb12901630
Ref: library/trace cmdoption-trace-help12901983
Ref: 40cc12901983
Ref: library/trace cmdoption-trace-version12902033
Ref: 40cd12902033
Node: Main options12902251
Ref: library/trace main-options12902336
Ref: 40ce12902336
Ref: library/trace cmdoption-trace-c12902713
Ref: 40d112902713
Ref: library/trace cmdoption-trace-count12902713
Ref: 40d212902713
Ref: library/trace cmdoption-trace-t12902966
Ref: 40d012902966
Ref: library/trace cmdoption-trace-trace12902966
Ref: 40d612902966
Ref: library/trace cmdoption-trace-l12903033
Ref: 40cf12903033
Ref: library/trace cmdoption-trace-listfuncs12903033
Ref: 40d712903033
Ref: library/trace cmdoption-trace-r12903123
Ref: 40d812903123
Ref: library/trace cmdoption-trace-report12903123
Ref: 40d912903123
Ref: library/trace cmdoption-trace-T12903317
Ref: 40da12903317
Ref: library/trace cmdoption-trace-trackcalls12903317
Ref: 40db12903317
Node: Modifiers12903419
Ref: library/trace modifiers12903520
Ref: 40dc12903520
Ref: library/trace cmdoption-trace-f12903559
Ref: 40d412903559
Ref: library/trace cmdoption-trace-file12903559
Ref: 40dd12903559
Ref: library/trace cmdoption-trace-C12903716
Ref: 40d312903716
Ref: library/trace cmdoption-trace-coverdir12903716
Ref: 40de12903716
Ref: library/trace cmdoption-trace-m12903906
Ref: 40df12903906
Ref: library/trace cmdoption-trace-missing12903906
Ref: 40e012903906
Ref: library/trace cmdoption-trace-s12904034
Ref: 40e112904034
Ref: library/trace cmdoption-trace-summary12904034
Ref: 40e212904034
Ref: library/trace cmdoption-trace-R12904184
Ref: 40d512904184
Ref: library/trace cmdoption-trace-no-report12904184
Ref: 40e312904184
Ref: library/trace cmdoption-trace-g12904405
Ref: 40e412904405
Ref: library/trace cmdoption-trace-timing12904405
Ref: 40e512904405
Node: Filters12904526
Ref: library/trace filters12904606
Ref: 40e612904606
Ref: library/trace cmdoption-trace-ignore-module12904688
Ref: 40e712904688
Ref: library/trace cmdoption-trace-ignore-dir12904877
Ref: 40e812904877
Node: Programmatic Interface12905080
Ref: library/trace programmatic-interface12905214
Ref: 40e912905214
Ref: library/trace trace-api12905214
Ref: 40ea12905214
Ref: library/trace trace Trace12905279
Ref: 40eb12905279
Ref: library/trace trace Trace run12906191
Ref: 40ec12906191
Ref: library/trace trace Trace runctx12906433
Ref: 40ed12906433
Ref: library/trace trace Trace runfunc12906747
Ref: a2212906747
Ref: library/trace trace Trace results12906940
Ref: 40ee12906940
Ref: library/trace trace CoverageResults12907249
Ref: 40ef12907249
Ref: library/trace trace CoverageResults update12907414
Ref: 40f012907414
Ref: library/trace trace CoverageResults write_results12907532
Ref: 40f112907532
Node: tracemalloc --- 追蹤記憶體配置12908878
Ref: library/tracemalloc doc12909030
Ref: 40f212909030
Ref: library/tracemalloc module-tracemalloc12909030
Ref: e812909030
Ref: library/tracemalloc tracemalloc-trace-memory-allocations12909030
Ref: 40f312909030
Ref: tracemalloc --- 追蹤記憶體配置-Footnote-112910354
Node: 範例<43>12910425
Ref: library/tracemalloc examples12910521
Ref: 40f412910521
Node: Display the top 1012910664
Ref: library/tracemalloc display-the-top-1012910757
Ref: 40f512910757
Node: Compute differences12912241
Ref: library/tracemalloc compute-differences12912378
Ref: 40f712912378
Node: Get the traceback of a memory block12914568
Ref: library/tracemalloc get-the-traceback-of-a-memory-block12914697
Ref: 40fa12914697
Node: Pretty top12917329
Ref: library/tracemalloc pretty-top12917430
Ref: 40fb12917430
Node: Record the current and peak size of all traced memory blocks12919892
Ref: library/tracemalloc record-the-current-and-peak-size-of-all-traced-memory-blocks12919999
Ref: 40fc12919999
Node: API12921693
Ref: library/tracemalloc api12921789
Ref: 40fe12921789
Node: 函式<10>12921955
Ref: library/tracemalloc functions12922026
Ref: 40ff12922026
Ref: library/tracemalloc tracemalloc clear_traces12922057
Ref: 410012922057
Ref: library/tracemalloc tracemalloc get_object_traceback12922197
Ref: 1a5e12922197
Ref: library/tracemalloc tracemalloc get_traceback_limit12922604
Ref: 410212922604
Ref: library/tracemalloc tracemalloc get_traced_memory12922925
Ref: 40fd12922925
Ref: library/tracemalloc tracemalloc reset_peak12923128
Ref: 8df12923128
Ref: library/tracemalloc tracemalloc get_tracemalloc_memory12923765
Ref: 410412923765
Ref: library/tracemalloc tracemalloc is_tracing12923960
Ref: 410512923960
Ref: library/tracemalloc tracemalloc start12924193
Ref: 1c3d12924193
Ref: library/tracemalloc tracemalloc stop12925555
Ref: 410112925555
Ref: library/tracemalloc tracemalloc take_snapshot12925987
Ref: 410312925987
Node: DomainFilter12926683
Ref: library/tracemalloc domainfilter12926769
Ref: 410912926769
Ref: library/tracemalloc tracemalloc DomainFilter12926814
Ref: c9812926814
Ref: library/tracemalloc tracemalloc DomainFilter inclusive12926981
Ref: 410a12926981
Ref: library/tracemalloc tracemalloc DomainFilter domain12927278
Ref: 410b12927278
Node: Filter12927380
Ref: library/tracemalloc filter12927461
Ref: 410c12927461
Ref: library/tracemalloc tracemalloc Filter12927496
Ref: 410d12927496
Ref: library/tracemalloc tracemalloc Filter domain12928351
Ref: 410e12928351
Ref: library/tracemalloc tracemalloc Filter inclusive12928619
Ref: 410f12928619
Ref: library/tracemalloc tracemalloc Filter lineno12929048
Ref: 411112929048
Ref: library/tracemalloc tracemalloc Filter filename_pattern12929197
Ref: 411012929197
Ref: library/tracemalloc tracemalloc Filter all_frames12929308
Ref: 411212929308
Node: Frame12929712
Ref: library/tracemalloc frame12929789
Ref: 411412929789
Ref: library/tracemalloc tracemalloc Frame12929822
Ref: 411512929822
Ref: library/tracemalloc tracemalloc Frame filename12929971
Ref: 411612929971
Ref: library/tracemalloc tracemalloc Frame lineno12930031
Ref: 411712930031
Node: Snapshot12930092
Ref: library/tracemalloc snapshot12930172
Ref: 411812930172
Ref: library/tracemalloc tracemalloc Snapshot12930211
Ref: 410812930211
Ref: library/tracemalloc tracemalloc Snapshot compare_to12930390
Ref: 410712930390
Ref: library/tracemalloc tracemalloc Snapshot dump12931118
Ref: 40f812931118
Ref: library/tracemalloc tracemalloc Snapshot filter_traces12931254
Ref: 411f12931254
Ref: library/tracemalloc tracemalloc Snapshot load12931929
Ref: 40f912931929
Ref: library/tracemalloc tracemalloc Snapshot statistics12932062
Ref: 40f612932062
Ref: library/tracemalloc tracemalloc Snapshot traceback_limit12933258
Ref: 411312933258
Ref: library/tracemalloc tracemalloc Snapshot traces12933474
Ref: 412012933474
Node: Statistic12933766
Ref: library/tracemalloc statistic12933854
Ref: 412512933854
Ref: library/tracemalloc tracemalloc Statistic12933895
Ref: 412112933895
Ref: library/tracemalloc tracemalloc Statistic count12934120
Ref: 411d12934120
Ref: library/tracemalloc tracemalloc Statistic size12934192
Ref: 412212934192
Ref: library/tracemalloc tracemalloc Statistic traceback12934276
Ref: 412312934276
Node: StatisticDiff12934405
Ref: library/tracemalloc statisticdiff12934490
Ref: 412612934490
Ref: library/tracemalloc tracemalloc StatisticDiff12934539
Ref: 411912934539
Ref: library/tracemalloc tracemalloc StatisticDiff count12934840
Ref: 412712934840
Ref: library/tracemalloc tracemalloc StatisticDiff count_diff12935011
Ref: 411c12935011
Ref: library/tracemalloc tracemalloc StatisticDiff size12935230
Ref: 411b12935230
Ref: library/tracemalloc tracemalloc StatisticDiff size_diff12935423
Ref: 411a12935423
Ref: library/tracemalloc tracemalloc StatisticDiff traceback12935654
Ref: 411e12935654
Node: Trace12935785
Ref: library/tracemalloc trace12935870
Ref: 412812935870
Ref: library/tracemalloc tracemalloc Trace12935903
Ref: 412412935903
Ref: library/tracemalloc tracemalloc Trace domain12936131
Ref: 412912936131
Ref: library/tracemalloc tracemalloc Trace size12936406
Ref: 412a12936406
Ref: library/tracemalloc tracemalloc Trace traceback12936487
Ref: 412b12936487
Node: Traceback12936616
Ref: library/tracemalloc traceback12936679
Ref: 412c12936679
Ref: library/tracemalloc tracemalloc Traceback12936720
Ref: b3d12936720
Ref: library/tracemalloc tracemalloc Traceback total_nframe12937646
Ref: 410612937646
Ref: library/tracemalloc tracemalloc Traceback format12937950
Ref: b3e12937950
Node: 軟體封裝與發布12939021
Ref: library/distribution doc12939178
Ref: 412e12939178
Ref: library/distribution software-packaging-and-distribution12939178
Ref: 412f12939178
Ref: 軟體封裝與發布-Footnote-112939753
Node: ensurepip --- pip 安裝器的初始建置 bootstrapping12939778
Ref: library/ensurepip doc12939928
Ref: 413012939928
Ref: library/ensurepip ensurepip-bootstrapping-the-pip-installer12939928
Ref: 413112939928
Ref: library/ensurepip module-ensurepip12939928
Ref: 4b12939928
Ref: ensurepip --- pip 安裝器的初始建置 bootstrapping-Footnote-112941580
Ref: ensurepip --- pip 安裝器的初始建置 bootstrapping-Footnote-212941646
Node: 命令列介面<5>12941688
Ref: library/ensurepip command-line-interface12941818
Ref: 413212941818
Node: 模組 API12943329
Ref: library/ensurepip module-api12943459
Ref: 413312943459
Ref: library/ensurepip ensurepip version12943566
Ref: 413412943566
Ref: library/ensurepip ensurepip bootstrap12943693
Ref: 3ffa12943693
Node: venv --- 建立虛擬環境12945267
Ref: library/venv doc12945481
Ref: 413512945481
Ref: library/venv module-venv12945481
Ref: f912945481
Ref: library/venv venv-creation-of-virtual-environments12945481
Ref: 413612945481
Ref: library/venv venv-def12945671
Ref: 413712945671
Ref: library/venv venv-intro12945671
Ref: 413812945671
Ref: venv --- 建立虛擬環境-Footnote-112947843
Ref: venv --- 建立虛擬環境-Footnote-212947905
Ref: venv --- 建立虛擬環境-Footnote-312947943
Ref: venv --- 建立虛擬環境-Footnote-412947985
Node: 建立虛擬環境<2>12948113
Ref: library/venv creating-virtual-environments12948231
Ref: 413912948231
Ref: 建立虛擬環境<2>-Footnote-112953455
Node: 虛擬環境如何運作12953510
Ref: library/venv how-venvs-work12953643
Ref: 413a12953643
Ref: library/venv venv-explanation12953643
Ref: 3f312953643
Node: API<2>12957590
Ref: library/venv api12957736
Ref: 413c12957736
Ref: library/venv venv-api12957736
Ref: e9612957736
Ref: library/venv venv EnvBuilder12957967
Ref: 24f12957967
Ref: library/venv venv EnvBuilder create12960362
Ref: 413e12960362
Ref: library/venv venv EnvBuilder ensure_directories12961625
Ref: 413f12961625
Ref: library/venv venv EnvBuilder create_configuration12964324
Ref: 414012964324
Ref: library/venv venv EnvBuilder setup_python12964462
Ref: 414112964462
Ref: library/venv venv EnvBuilder setup_scripts12964828
Ref: 414212964828
Ref: library/venv venv EnvBuilder upgrade_dependencies12964977
Ref: 414512964977
Ref: library/venv venv EnvBuilder post_setup12965351
Ref: 414312965351
Ref: library/venv venv EnvBuilder install_scripts12966343
Ref: 414412966343
Ref: library/venv venv EnvBuilder create_git_ignore_file12967555
Ref: 413d12967555
Ref: library/venv venv create12967874
Ref: 25012967874
Node: An example of extending EnvBuilder12968495
Ref: library/venv an-example-of-extending-envbuilder12968608
Ref: 414612968608
Ref: An example of extending EnvBuilder-Footnote-112978753
Node: zipapp —-- 管理可執行的 Python zip 封存檔案12978800
Ref: library/zipapp doc12978949
Ref: 414712978949
Ref: library/zipapp module-zipapp12978949
Ref: 11612978949
Ref: library/zipapp zipapp-manage-executable-python-zip-archives12978949
Ref: 414812978949
Ref: zipapp —-- 管理可執行的 Python zip 封存檔案-Footnote-112979696
Node: 基本範例12979762
Ref: library/zipapp basic-example12979896
Ref: 414b12979896
Node: 命令執行列介面12980294
Ref: library/zipapp command-line-interface12980447
Ref: 414c12980447
Ref: library/zipapp zipapp-command-line-interface12980447
Ref: 414912980447
Ref: library/zipapp cmdoption-zipapp-o12980932
Ref: 414d12980932
Ref: library/zipapp cmdoption-zipapp-output12980932
Ref: 414e12980932
Ref: library/zipapp cmdoption-zipapp-p12981429
Ref: 414f12981429
Ref: library/zipapp cmdoption-zipapp-python12981429
Ref: 415012981429
Ref: library/zipapp cmdoption-zipapp-m12981705
Ref: 415112981705
Ref: library/zipapp cmdoption-zipapp-main12981705
Ref: 415212981705
Ref: library/zipapp cmdoption-zipapp-c12982122
Ref: 415312982122
Ref: library/zipapp cmdoption-zipapp-compress12982122
Ref: 415412982122
Ref: library/zipapp cmdoption-zipapp-info12982399
Ref: 415512982399
Ref: library/zipapp cmdoption-zipapp-h12982602
Ref: 415612982602
Ref: library/zipapp cmdoption-zipapp-help12982602
Ref: 415712982602
Node: Python API12982670
Ref: library/zipapp python-api12982821
Ref: 415812982821
Ref: library/zipapp zipapp-python-api12982821
Ref: 414a12982821
Ref: library/zipapp zipapp create_archive12982909
Ref: b5712982909
Ref: library/zipapp zipapp get_interpreter12986674
Ref: 415912986674
Node: 範例<44>12987029
Ref: library/zipapp examples12987185
Ref: 415a12987185
Ref: library/zipapp zipapp-examples12987185
Ref: 415b12987185
Node: Specifying the Interpreter12988550
Ref: library/zipapp specifying-the-interpreter12988740
Ref: 415c12988740
Ref: library/zipapp zipapp-specifying-the-interpreter12988740
Ref: 415d12988740
Node: Creating Standalone Applications with zipapp12989947
Ref: library/zipapp creating-standalone-applications-with-zipapp12990168
Ref: 415e12990168
Node: Caveats12991871
Ref: library/zipapp caveats12991959
Ref: 415f12991959
Node: The Python Zip Application Archive Format12992696
Ref: library/zipapp the-python-zip-application-archive-format12992882
Ref: 416012992882
Node: Python Runtime 服務12994773
Ref: library/python doc12994932
Ref: 416112994932
Ref: library/python python12994932
Ref: 416212994932
Ref: library/python python-runtime-services12994932
Ref: 416312994932
Node: sys --- 系統特定的參數與函式12996342
Ref: library/sys doc12996492
Ref: 416412996492
Ref: library/sys module-sys12996492
Ref: c312996492
Ref: library/sys sys-system-specific-parameters-and-functions12996492
Ref: 416512996492
Ref: library/sys sys abiflags12996821
Ref: a0712996821
Ref: library/sys sys addaudithook12997182
Ref: 3ff112997182
Ref: library/sys sys argv12999367
Ref: 11fd12999367
Ref: library/sys auditing13000302
Ref: 17bd13000302
Ref: library/sys sys audit13000302
Ref: 187313000302
Ref: library/sys sys base_exec_prefix13001674
Ref: 413b13001674
Ref: library/sys sys base_prefix13002321
Ref: 3afe13002321
Ref: library/sys sys byteorder13002958
Ref: 207813002958
Ref: library/sys sys builtin_module_names13003216
Ref: 1b6313003216
Ref: library/sys sys call_tracing13003554
Ref: 173713003554
Ref: library/sys sys copyright13004075
Ref: 416613004075
Ref: library/sys sys _clear_type_cache13004185
Ref: 156713004185
Ref: library/sys sys _clear_internal_caches13004626
Ref: 156613004626
Ref: library/sys sys _current_frames13004863
Ref: 13a013004863
Ref: library/sys sys _current_exceptions13005719
Ref: 46913005719
Ref: library/sys sys breakpointhook13006426
Ref: a7d13006426
Ref: library/sys sys _debugmallocstats13008322
Ref: 416713008322
Ref: library/sys sys dllhandle13008789
Ref: 416813008789
Ref: library/sys sys displayhook13008910
Ref: 148e13008910
Ref: library/sys sys dont_write_bytecode13010433
Ref: 416913010433
Ref: library/sys sys _emscripten_info13010832
Ref: 170613010832
Ref: library/sys sys _emscripten_info emscripten_version13011049
Ref: 416a13011049
Ref: library/sys sys _emscripten_info runtime13011206
Ref: 416b13011206
Ref: library/sys sys _emscripten_info pthreads13011391
Ref: 416c13011391
Ref: library/sys sys _emscripten_info shared_memory13011513
Ref: 416d13011513
Ref: library/sys sys pycache_prefix13011705
Ref: 94813011705
Ref: library/sys sys excepthook13012680
Ref: 7af13012680
Ref: library/sys sys __breakpointhook__13014042
Ref: 416e13014042
Ref: library/sys sys __displayhook__13014077
Ref: 416f13014077
Ref: library/sys sys __excepthook__13014109
Ref: 417013014109
Ref: library/sys sys __unraisablehook__13014140
Ref: 417113014140
Ref: library/sys sys exception13014654
Ref: 63113014654
Ref: library/sys sys exc_info13015122
Ref: 63013015122
Ref: library/sys sys exec_prefix13016119
Ref: 37d13016119
Ref: library/sys sys executable13017043
Ref: 38313017043
Ref: library/sys sys exit13017346
Ref: 12dd13017346
Ref: library/sys sys flags13019000
Ref: 63213019000
Ref: library/sys sys flags debug13019171
Ref: 417213019171
Ref: library/sys sys flags inspect13019373
Ref: 417313019373
Ref: library/sys sys flags interactive13019577
Ref: 417413019577
Ref: library/sys sys flags isolated13019774
Ref: 417513019774
Ref: library/sys sys flags optimize13019973
Ref: 417613019973
Ref: library/sys sys flags dont_write_bytecode13020203
Ref: 417713020203
Ref: library/sys sys flags no_user_site13020396
Ref: 417813020396
Ref: library/sys sys flags no_site13020591
Ref: 417913020591
Ref: library/sys sys flags ignore_environment13020802
Ref: 417a13020802
Ref: library/sys sys flags verbose13020990
Ref: 417b13020990
Ref: library/sys sys flags bytes_warning13021196
Ref: 417c13021196
Ref: library/sys sys flags quiet13021387
Ref: 417d13021387
Ref: library/sys sys flags hash_randomization13021600
Ref: 417e13021600
Ref: library/sys sys flags dev_mode13021790
Ref: 19a713021790
Ref: library/sys sys flags utf8_mode13022032
Ref: 417f13022032
Ref: library/sys sys flags safe_path13022236
Ref: 21b13022236
Ref: library/sys sys flags int_max_str_digits13022444
Ref: 215813022444
Ref: library/sys sys flags warn_default_encoding13022783
Ref: 418013022783
Ref: library/sys sys float_info13023749
Ref: 18f013023749
Ref: library/sys sys float_info epsilon13024695
Ref: 418213024695
Ref: library/sys sys float_info dig13025400
Ref: 418313025400
Ref: library/sys sys float_info mant_dig13025913
Ref: 418413025913
Ref: library/sys sys float_info max13026407
Ref: 418513026407
Ref: library/sys sys float_info max_exp13026792
Ref: 418613026792
Ref: library/sys sys float_info max_10_exp13027294
Ref: 418713027294
Ref: library/sys sys float_info min13027794
Ref: 418813027794
Ref: library/sys sys float_info min_exp13028605
Ref: 418913028605
Ref: library/sys sys float_info min_10_exp13029097
Ref: 418a13029097
Ref: library/sys sys float_info radix13029493
Ref: 418b13029493
Ref: library/sys sys float_info rounds13029864
Ref: 418c13029864
Ref: library/sys sys float_repr_style13032761
Ref: 128d13032761
Ref: library/sys sys getallocatedblocks13033304
Ref: f6813033304
Ref: library/sys sys getunicodeinternedsize13033944
Ref: 418d13033944
Ref: library/sys sys getandroidapilevel13034084
Ref: b3013034084
Ref: library/sys sys getdefaultencoding13034424
Ref: 418e13034424
Ref: library/sys sys getdlopenflags13034565
Ref: 147e13034565
Ref: library/sys sys getfilesystemencoding13034873
Ref: c0013034873
Ref: library/sys sys getfilesystemencodeerrors13036271
Ref: c8d13036271
Ref: library/sys sys get_int_max_str_digits13037011
Ref: 215a13037011
Ref: library/sys sys getrefcount13037237
Ref: 418f13037237
Ref: library/sys sys getrecursionlimit13038005
Ref: 46b13038005
Ref: library/sys sys getsizeof13038315
Ref: 166c13038315
Ref: library/sys sys getswitchinterval13039263
Ref: 8ed13039263
Ref: library/sys sys _getframe13039427
Ref: 68413039427
Ref: library/sys sys _getframemodulename13040073
Ref: 167213040073
Ref: library/sys sys getprofile13040771
Ref: 134e13040771
Ref: library/sys sys gettrace13040870
Ref: 134f13040870
Ref: library/sys sys getwindowsversion13041296
Ref: c8e13041296
Ref: library/sys sys get_asyncgen_hooks13043818
Ref: 173813043818
Ref: library/sys sys get_coroutine_origin_tracking_depth13044427
Ref: b3113044427
Ref: library/sys sys hash_info13044779
Ref: fa013044779
Ref: library/sys sys hash_info width13044991
Ref: 419213044991
Ref: library/sys sys hash_info modulus13045075
Ref: 207e13045075
Ref: library/sys sys hash_info inf13045171
Ref: 419313045171
Ref: library/sys sys hash_info nan13045262
Ref: 419413045262
Ref: library/sys sys hash_info imag13045340
Ref: 419513045340
Ref: library/sys sys hash_info algorithm13045447
Ref: 419613045447
Ref: library/sys sys hash_info hash_bits13045574
Ref: 419713045574
Ref: library/sys sys hash_info seed_bits13045670
Ref: 419813045670
Ref: library/sys sys hexversion13045871
Ref: 419913045871
Ref: library/sys sys implementation13046769
Ref: 4bb13046769
Ref: library/sys sys int_info13048972
Ref: 122b13048972
Ref: library/sys sys int_info bits_per_digit13049141
Ref: 419b13049141
Ref: library/sys sys int_info sizeof_digit13049324
Ref: 419c13049324
Ref: library/sys sys int_info default_max_str_digits13049434
Ref: 215913049434
Ref: library/sys sys int_info str_digits_check_threshold13049617
Ref: 419d13049617
Ref: library/sys sys __interactivehook__13050009
Ref: f6a13050009
Ref: library/sys sys intern13050559
Ref: 126e13050559
Ref: library/sys sys _is_gil_enabled13051336
Ref: 419e13051336
Ref: library/sys sys is_finalizing13051511
Ref: a3213051511
Ref: library/sys sys last_exc13051771
Ref: 46513051771
Ref: library/sys sys _is_interned13052346
Ref: 23513052346
Ref: library/sys sys last_type13052614
Ref: 46613052614
Ref: library/sys sys last_value13052640
Ref: 46713052640
Ref: library/sys sys last_traceback13052667
Ref: 46813052667
Ref: library/sys sys maxsize13052898
Ref: 115d13052898
Ref: library/sys sys maxunicode13053120
Ref: fef13053120
Ref: library/sys sys meta_path13053519
Ref: cd213053519
Ref: library/sys sys modules13054819
Ref: 186e13054819
Ref: library/sys sys orig_argv13055429
Ref: 7e413055429
Ref: library/sys sys path13055905
Ref: 37f13055905
Ref: library/sys sys path_hooks13057174
Ref: fc713057174
Ref: library/sys sys path_importer_cache13057467
Ref: 58813057467
Ref: library/sys sys platform13057874
Ref: a3013057874
Ref: library/sys sys platlibdir13060201
Ref: 8dc13060201
Ref: library/sys sys prefix13061207
Ref: 38113061207
Ref: library/sys sys ps113061840
Ref: 1c4713061840
Ref: library/sys sys ps213061860
Ref: 1c4813061860
Ref: library/sys sys setdlopenflags13062338
Ref: 10b713062338
Ref: library/sys sys set_int_max_str_digits13062934
Ref: 16c113062934
Ref: library/sys sys setprofile13063169
Ref: 146d13063169
Ref: library/sys sys setrecursionlimit13065562
Ref: 46a13065562
Ref: library/sys sys setswitchinterval13066345
Ref: 8ee13066345
Ref: library/sys sys settrace13066912
Ref: 146e13066912
Ref: library/sys sys set_asyncgen_hooks13071640
Ref: 151a13071640
Ref: library/sys sys set_coroutine_origin_tracking_depth13072755
Ref: b3213072755
Ref: library/sys sys activate_stack_trampoline13073578
Ref: 41613073578
Ref: library/sys sys deactivate_stack_trampoline13073944
Ref: 41713073944
Ref: library/sys sys is_stack_trampoline_active13074192
Ref: 41813074192
Ref: library/sys sys _enablelegacywindowsfsencoding13074371
Ref: 28e13074371
Ref: library/sys sys stdin13075329
Ref: 4e213075329
Ref: library/sys sys stdout13075351
Ref: a7913075351
Ref: library/sys sys stderr13075374
Ref: 8dd13075374
Ref: library/sys sys __stdin__13078531
Ref: 41a113078531
Ref: library/sys sys __stdout__13078557
Ref: 275f13078557
Ref: library/sys sys __stderr__13078584
Ref: 3f7613078584
Ref: library/sys sys stdlib_module_names13079551
Ref: 7e513079551
Ref: library/sys sys thread_info13080292
Ref: 10e913080292
Ref: library/sys sys thread_info name13080411
Ref: 41a213080411
Ref: library/sys sys thread_info lock13080766
Ref: 41a313080766
Ref: library/sys sys thread_info version13081057
Ref: 41a413081057
Ref: library/sys sys tracebacklimit13081251
Ref: 14cd13081251
Ref: library/sys sys unraisablehook13081617
Ref: 1dc13081617
Ref: library/sys sys version13083447
Ref: 15c13083447
Ref: library/sys sys api_version13083851
Ref: 41a513083851
Ref: library/sys sys version_info13084041
Ref: 64513084041
Ref: library/sys sys warnoptions13084662
Ref: 37b13084662
Ref: library/sys sys winver13084882
Ref: 41a613084882
Ref: library/sys sys _xoptions13085524
Ref: 1c4113085524
Ref: library/sys c9913086312
Ref: 418113086312
Ref: sys --- 系統特定的參數與函式-Footnote-113086510
Ref: sys --- 系統特定的參數與函式-Footnote-213086552
Ref: sys --- 系統特定的參數與函式-Footnote-313086594
Ref: sys --- 系統特定的參數與函式-Footnote-413086636
Ref: sys --- 系統特定的參數與函式-Footnote-513086741
Ref: sys --- 系統特定的參數與函式-Footnote-613086783
Ref: sys --- 系統特定的參數與函式-Footnote-713086825
Ref: sys --- 系統特定的參數與函式-Footnote-813086867
Ref: sys --- 系統特定的參數與函式-Footnote-913086909
Ref: sys --- 系統特定的參數與函式-Footnote-1013086951
Ref: sys --- 系統特定的參數與函式-Footnote-1113086994
Ref: sys --- 系統特定的參數與函式-Footnote-1213087037
Ref: sys --- 系統特定的參數與函式-Footnote-1313087080
Ref: sys --- 系統特定的參數與函式-Footnote-1413087123
Ref: sys --- 系統特定的參數與函式-Footnote-1513087166
Ref: sys --- 系統特定的參數與函式-Footnote-1613087247
Ref: sys --- 系統特定的參數與函式-Footnote-1713087290
Ref: sys --- 系統特定的參數與函式-Footnote-1813087333
Node: sys monitoring --- Execution event monitoring13087376
Ref: library/sys monitoring doc13087584
Ref: 41a713087584
Ref: library/sys monitoring module-sys monitoring13087584
Ref: c413087584
Ref: library/sys monitoring sys-monitoring-execution-event-monitoring13087584
Ref: 41a813087584
Node: Tool identifiers13088593
Ref: library/sys monitoring tool-identifiers13088706
Ref: 41a913088706
Node: Registering and using tools13089263
Ref: library/sys monitoring registering-and-using-tools13089343
Ref: 41ac13089343
Ref: library/sys monitoring sys monitoring use_tool_id13089418
Ref: 41ad13089418
Ref: library/sys monitoring sys monitoring free_tool_id13089673
Ref: 41ae13089673
Ref: library/sys monitoring sys monitoring get_tool13090087
Ref: 41af13090087
Node: 事件13090588
Ref: library/sys monitoring events13090735
Ref: 41aa13090735
Ref: library/sys monitoring monitoring-event-BRANCH13090803
Ref: 41b013090803
Ref: library/sys monitoring monitoring-event-CALL13090901
Ref: 153a13090901
Ref: library/sys monitoring monitoring-event-C_RAISE13091011
Ref: 41b113091011
Ref: library/sys monitoring monitoring-event-C_RETURN13091173
Ref: 41b213091173
Ref: library/sys monitoring monitoring-event-EXCEPTION_HANDLED13091325
Ref: 41b313091325
Ref: library/sys monitoring monitoring-event-INSTRUCTION13091419
Ref: 41b413091419
Ref: library/sys monitoring monitoring-event-JUMP13091524
Ref: 41b513091524
Ref: library/sys monitoring monitoring-event-LINE13091637
Ref: 41b613091637
Ref: library/sys monitoring monitoring-event-PY_RESUME13091802
Ref: 41b713091802
Ref: library/sys monitoring monitoring-event-PY_RETURN13091973
Ref: 41b813091973
Ref: library/sys monitoring monitoring-event-PY_START13092150
Ref: 41b913092150
Ref: library/sys monitoring monitoring-event-PY_THROW13092319
Ref: 41ba13092319
Ref: library/sys monitoring monitoring-event-PY_UNWIND13092433
Ref: 41bb13092433
Ref: library/sys monitoring monitoring-event-PY_YIELD13092550
Ref: 41bc13092550
Ref: library/sys monitoring monitoring-event-RAISE13092724
Ref: 14e213092724
Ref: library/sys monitoring monitoring-event-RERAISE13092871
Ref: 41be13092871
Ref: library/sys monitoring monitoring-event-STOP_ITERATION13093017
Ref: 41bd13093017
Ref: library/sys monitoring monitoring-event-NO_EVENTS13093569
Ref: 41c013093569
Node: Local events13093893
Ref: library/sys monitoring local-events13093969
Ref: 41c113093969
Node: 輔助事件13094455
Ref: library/sys monitoring ancillary-events13094552
Ref: 41c213094552
Node: 其他事件13094983
Ref: library/sys monitoring other-events13095092
Ref: 41c313095092
Node: The STOP_ITERATION event13095411
Ref: library/sys monitoring the-stop-iteration-event13095499
Ref: 41bf13095499
Ref: The STOP_ITERATION event-Footnote-113096142
Node: Turning events on and off13096223
Ref: library/sys monitoring turning-events-on-and-off13096372
Ref: 41c413096372
Node: Setting events globally13096729
Ref: library/sys monitoring setting-events-globally13096845
Ref: 41c513096845
Ref: library/sys monitoring sys monitoring get_events13096995
Ref: 41c613096995
Ref: library/sys monitoring sys monitoring set_events13097123
Ref: 41c713097123
Node: Per code object events13097371
Ref: library/sys monitoring per-code-object-events13097508
Ref: 41c813097508
Ref: library/sys monitoring sys monitoring get_local_events13097838
Ref: 41ca13097838
Ref: library/sys monitoring sys monitoring set_local_events13097980
Ref: 41cb13097980
Node: 停用事件13098399
Ref: library/sys monitoring disabling-events13098504
Ref: 41cc13098504
Ref: library/sys monitoring sys monitoring DISABLE13098547
Ref: 41cd13098547
Ref: library/sys monitoring sys monitoring restart_events13099162
Ref: 41ce13099162
Node: 註冊回呼函式13099322
Ref: library/sys monitoring callbacks13099456
Ref: 41ab13099456
Ref: library/sys monitoring registering-callback-functions13099456
Ref: 41cf13099456
Ref: library/sys monitoring sys monitoring register_callback13099549
Ref: 41d013099549
Node: 回呼函式引數13100247
Ref: library/sys monitoring callback-function-arguments13100320
Ref: 41d113100320
Ref: library/sys monitoring sys monitoring MISSING13100373
Ref: 41d213100373
Node: sysconfig --- 提供 Python 設定資訊的存取13102057
Ref: library/sysconfig doc13102252
Ref: 41d313102252
Ref: library/sysconfig module-sysconfig13102252
Ref: c513102252
Ref: library/sysconfig sysconfig-provide-access-to-python-s-configuration-information13102252
Ref: 41d413102252
Ref: sysconfig --- 提供 Python 設定資訊的存取-Footnote-113102918
Node: Configuration variables13102984
Ref: library/sysconfig configuration-variables13103120
Ref: 41d513103120
Ref: library/sysconfig sysconfig get_config_vars13103608
Ref: fcf13103608
Ref: library/sysconfig sysconfig get_config_var13103977
Ref: fce13103977
Node: Installation paths13104416
Ref: library/sysconfig id113104572
Ref: 41d613104572
Ref: library/sysconfig installation-paths13104572
Ref: 63513104572
Node: User scheme13106906
Ref: library/sysconfig sysconfig-user-scheme13107050
Ref: 1c4913107050
Ref: library/sysconfig user-scheme13107050
Ref: 41d713107050
Node: posix_user13107575
Ref: library/sysconfig posix-user13107649
Ref: 41d813107649
Node: nt_user13108493
Ref: library/sysconfig nt-user13108594
Ref: 41d913108594
Node: osx_framework_user13109426
Ref: library/sysconfig osx-framework-user13109508
Ref: 41da13109508
Node: Home scheme13110348
Ref: library/sysconfig home-scheme13110487
Ref: 41db13110487
Ref: library/sysconfig sysconfig-home-scheme13110487
Ref: 41dc13110487
Node: posix_home13110956
Ref: library/sysconfig posix-home13111014
Ref: 41dd13111014
Node: Prefix scheme13111864
Ref: library/sysconfig prefix-scheme13112010
Ref: 41de13112010
Ref: library/sysconfig sysconfig-prefix-scheme13112010
Ref: 41df13112010
Node: posix_prefix13113339
Ref: library/sysconfig posix-prefix13113412
Ref: 41e013113412
Node: nt13114341
Ref: library/sysconfig nt13114414
Ref: 41e113114414
Node: 安裝路徑函式13115255
Ref: library/sysconfig installation-path-functions13115405
Ref: 41e213115405
Ref: library/sysconfig sysconfig get_scheme_names13115543
Ref: 41e313115543
Ref: library/sysconfig sysconfig get_default_scheme13115679
Ref: 172813115679
Ref: library/sysconfig sysconfig get_preferred_scheme13116035
Ref: 63613116035
Ref: library/sysconfig sysconfig _get_preferred_schemes13116623
Ref: 41e413116623
Ref: library/sysconfig sysconfig get_path_names13117288
Ref: 41e513117288
Ref: library/sysconfig sysconfig get_path13117425
Ref: 12c213117425
Ref: library/sysconfig sysconfig get_paths13118656
Ref: 11dc13118656
Node: 其他函式<3>13119279
Ref: library/sysconfig other-functions13119448
Ref: 41e613119448
Ref: library/sysconfig sysconfig get_python_version13119491
Ref: 11db13119491
Ref: library/sysconfig sysconfig get_platform13119650
Ref: 11da13119650
Ref: library/sysconfig sysconfig is_python_build13120656
Ref: 2d413120656
Ref: library/sysconfig sysconfig parse_config_h13120945
Ref: 41e713120945
Ref: library/sysconfig sysconfig get_config_h_filename13121337
Ref: 41e813121337
Ref: library/sysconfig sysconfig get_makefile_filename13121428
Ref: 41e913121428
Node: 將 sysconfig 作為腳本使用13121517
Ref: library/sysconfig sysconfig-cli13121659
Ref: 41ea13121659
Ref: library/sysconfig using-sysconfig-as-a-script13121659
Ref: 41eb13121659
Node: builtins --- 內建物件13122738
Ref: library/builtins doc13122922
Ref: 41ec13122922
Ref: library/builtins builtins-built-in-objects13122922
Ref: 41ed13122922
Ref: library/builtins module-builtins13122922
Ref: e13122922
Node: __main__ --- 頂層程式碼環境13124291
Ref: library/__main__ doc13124451
Ref: 41ee13124451
Ref: library/__main__ main-top-level-code-environment13124451
Ref: 41ef13124451
Ref: library/__main__ module-__main__13124451
Ref: 113124451
Node: __name__ == '__main__'13125213
Ref: library/__main__ name-equals-main13125346
Ref: 41f013125346
Ref: library/__main__ name-main13125346
Ref: 41f113125346
Node: 什麼是「頂層程式碼環境」？13126141
Ref: library/__main__ what-is-the-top-level-code-environment13126271
Ref: 41f213126271
Node: 慣用 Idiomatic 用法13128168
Ref: library/__main__ idiomatic-usage13128334
Ref: 41f313128334
Node: 打包時須考慮的事情13130269
Ref: library/__main__ packaging-considerations13130387
Ref: 41f413130387
Ref: 打包時須考慮的事情-Footnote-113131757
Ref: 打包時須考慮的事情-Footnote-213131786
Node: Python 套件中的 __main__ py13131824
Ref: library/__main__ main-py-in-python-packages13131981
Ref: 41f513131981
Node: 慣用 Idiomatic 用法<2>13133287
Ref: library/__main__ id113133381
Ref: 41f613133381
Node: import __main__13134756
Ref: library/__main__ import-main13134882
Ref: 41f713134882
Node: warnings --- 警告控制13137964
Ref: library/warnings doc13138127
Ref: 41f813138127
Ref: library/warnings module-warnings13138127
Ref: fa13138127
Ref: library/warnings warnings-warning-control13138127
Ref: 41f913138127
Ref: warnings --- 警告控制-Footnote-113140421
Node: Warning Categories13140489
Ref: library/warnings id113140597
Ref: 41fd13140597
Ref: library/warnings warning-categories13140597
Ref: 219013140597
Node: The Warnings Filter13144592
Ref: library/warnings the-warnings-filter13144741
Ref: 41fe13144741
Ref: library/warnings warning-filter13144741
Ref: 86e13144741
Node: Describing Warning Filters13147878
Ref: library/warnings describing-warning-filters13147991
Ref: 1c3b13147991
Ref: library/warnings id213147991
Ref: 41ff13147991
Node: Default Warning Filter13149713
Ref: library/warnings default-warning-filter13149864
Ref: 420013149864
Ref: library/warnings id313149864
Ref: 420113149864
Node: Overriding the default filter13150958
Ref: library/warnings overriding-the-default-filter13151074
Ref: 420213151074
Ref: library/warnings warning-disable13151074
Ref: 420313151074
Node: Temporarily Suppressing Warnings13152509
Ref: library/warnings temporarily-suppressing-warnings13152656
Ref: 420413152656
Ref: library/warnings warning-suppress13152656
Ref: 420513152656
Node: Testing Warnings13153672
Ref: library/warnings testing-warnings13153846
Ref: 420613153846
Ref: library/warnings warning-testing13153846
Ref: 420713153846
Node: Updating Code For New Versions of Dependencies13155908
Ref: library/warnings updating-code-for-new-versions-of-dependencies13156069
Ref: 420813156069
Ref: library/warnings warning-ignored13156069
Ref: 3ec813156069
Node: Available Functions13157454
Ref: library/warnings available-functions13157625
Ref: 420913157625
Ref: library/warnings warning-functions13157625
Ref: 420a13157625
Ref: library/warnings warnings warn13157684
Ref: 148813157684
Ref: library/warnings warnings warn_explicit13160257
Ref: ca713160257
Ref: library/warnings warnings showwarning13161432
Ref: 41fc13161432
Ref: library/warnings warnings formatwarning13162068
Ref: 191b13162068
Ref: library/warnings warnings filterwarnings13162498
Ref: 141413162498
Ref: library/warnings warnings simplefilter13163172
Ref: 66613163172
Ref: library/warnings warnings resetwarnings13163606
Ref: 41fb13163606
Ref: library/warnings warnings deprecated13163872
Ref: 14413163872
Ref: Available Functions-Footnote-113165731
Node: Available Context Managers13165773
Ref: library/warnings available-context-managers13165889
Ref: 420b13165889
Ref: library/warnings warnings catch_warnings13165964
Ref: 52a13165964
Node: dataclasses --- Data Classes13167557
Ref: library/dataclasses doc13167738
Ref: 420c13167738
Ref: library/dataclasses dataclasses-data-classes13167738
Ref: 420d13167738
Ref: library/dataclasses module-dataclasses13167738
Ref: 2713167738
Ref: dataclasses --- Data Classes-Footnote-113169397
Ref: dataclasses --- Data Classes-Footnote-213169468
Ref: dataclasses --- Data Classes-Footnote-313169510
Node: 模組內容<8>13169552
Ref: library/dataclasses module-contents13169661
Ref: 420e13169661
Ref: library/dataclasses dataclasses dataclass13169702
Ref: 1af13169702
Ref: library/dataclasses dataclasses field13179465
Ref: 192613179465
Ref: library/dataclasses dataclasses Field13183903
Ref: 213213183903
Ref: library/dataclasses dataclasses fields13184654
Ref: 164113184654
Ref: library/dataclasses dataclasses asdict13185031
Ref: 162213185031
Ref: library/dataclasses dataclasses astuple13186071
Ref: 162c13186071
Ref: library/dataclasses dataclasses make_dataclass13186798
Ref: 164313186798
Ref: library/dataclasses dataclasses replace13188586
Ref: 15f413188586
Ref: library/dataclasses dataclasses is_dataclass13190082
Ref: 177513190082
Ref: library/dataclasses dataclasses MISSING13190559
Ref: 421013190559
Ref: library/dataclasses dataclasses KW_ONLY13190664
Ref: 420f13190664
Ref: library/dataclasses dataclasses FrozenInstanceError13191609
Ref: 421213191609
Ref: 模組內容<8>-Footnote-113191917
Ref: 模組內容<8>-Footnote-213191972
Node: Post-init processing13192027
Ref: library/dataclasses id113192157
Ref: 421313192157
Ref: library/dataclasses post-init-processing13192157
Ref: 421413192157
Ref: library/dataclasses dataclasses __post_init__13192218
Ref: 421113192218
Node: 類別變數13193975
Ref: library/dataclasses class-variables13194109
Ref: 421513194109
Ref: library/dataclasses dataclasses-class-variables13194109
Ref: 421613194109
Ref: 類別變數-Footnote-113194657
Node: Init-only variables13194699
Ref: library/dataclasses dataclasses-init-only-variables13194825
Ref: 421713194825
Ref: library/dataclasses init-only-variables13194825
Ref: 421813194825
Node: 凍結實例13196054
Ref: library/dataclasses dataclasses-frozen13196174
Ref: 421913196174
Ref: library/dataclasses frozen-instances13196174
Ref: 421a13196174
Node: 繼承13196759
Ref: library/dataclasses dataclasses-inheritance13196910
Ref: 421b13196910
Ref: library/dataclasses inheritance13196910
Ref: 421c13196910
Node: Re-ordering of keyword-only parameters in __init__13197952
Ref: library/dataclasses re-ordering-of-keyword-only-parameters-in-init13198109
Ref: 421d13198109
Node: 預設工廠函式13199364
Ref: library/dataclasses default-factory-functions13199530
Ref: 421e13199530
Node: 可變預設值13200128
Ref: library/dataclasses mutable-default-values13200267
Ref: 421f13200267
Node: Descriptor-typed fields13202270
Ref: library/dataclasses descriptor-typed-fields13202382
Ref: 422013202382
Node: contextlib --- Utilities for with-statement contexts13204350
Ref: library/contextlib doc13204532
Ref: 422113204532
Ref: library/contextlib contextlib-utilities-for-with-statement-contexts13204532
Ref: 422213204532
Ref: library/contextlib module-contextlib13204532
Ref: 1c13204532
Ref: contextlib --- Utilities for with-statement contexts-Footnote-113205193
Node: Utilities13205263
Ref: library/contextlib utilities13205393
Ref: 422313205393
Ref: library/contextlib contextlib AbstractContextManager13205465
Ref: c3413205465
Ref: library/contextlib contextlib AbstractAsyncContextManager13205956
Ref: acf13205956
Ref: library/contextlib contextlib contextmanager13206471
Ref: 119a13206471
Ref: library/contextlib contextlib asynccontextmanager13209476
Ref: ace13209476
Ref: library/contextlib contextlib closing13211718
Ref: 282a13211718
Ref: library/contextlib contextlib aclosing13212957
Ref: 79113212957
Ref: library/contextlib simplifying-support-for-single-optional-context-managers13214072
Ref: 422413214072
Ref: library/contextlib contextlib nullcontext13214072
Ref: 79213214072
Ref: library/contextlib contextlib suppress13215787
Ref: eca13215787
Ref: library/contextlib contextlib redirect_stdout13217356
Ref: d8e13217356
Ref: library/contextlib contextlib redirect_stderr13218828
Ref: d8d13218828
Ref: library/contextlib contextlib chdir13219090
Ref: 5b113219090
Ref: library/contextlib contextlib ContextDecorator13219817
Ref: 119913219817
Ref: library/contextlib contextlib AsyncContextDecorator13222259
Ref: 79313222259
Ref: library/contextlib contextlib ExitStack13223350
Ref: acd13223350
Ref: library/contextlib contextlib ExitStack enter_context13225348
Ref: 57813225348
Ref: library/contextlib contextlib ExitStack push13225924
Ref: 422613225924
Ref: library/contextlib contextlib ExitStack callback13226810
Ref: a2613226810
Ref: library/contextlib contextlib ExitStack pop_all13227266
Ref: 422713227266
Ref: library/contextlib contextlib ExitStack close13228314
Ref: 422813228314
Ref: library/contextlib contextlib AsyncExitStack13228602
Ref: ad013228602
Ref: library/contextlib contextlib AsyncExitStack enter_async_context13228970
Ref: 57b13228970
Ref: library/contextlib contextlib AsyncExitStack push_async_exit13229307
Ref: 422a13229307
Ref: library/contextlib contextlib AsyncExitStack push_async_callback13229486
Ref: a2713229486
Ref: library/contextlib contextlib AsyncExitStack aclose13229652
Ref: 422913229652
Node: Examples and Recipes<2>13230265
Ref: library/contextlib examples-and-recipes13230454
Ref: 422b13230454
Node: Supporting a variable number of context managers13230902
Ref: library/contextlib supporting-a-variable-number-of-context-managers13231061
Ref: 422c13231061
Node: Catching exceptions from __enter__ methods13232101
Ref: library/contextlib catching-exceptions-from-enter-methods13232311
Ref: 422d13232311
Node: Cleaning up in an __enter__ implementation13233455
Ref: library/contextlib cleaning-up-in-an-enter-implementation13233668
Ref: 422e13233668
Node: Replacing any use of try-finally and flag variables13235569
Ref: library/contextlib replacing-any-use-of-try-finally-and-flag-variables13235787
Ref: 422f13235787
Node: Using a context manager as a function decorator13238295
Ref: library/contextlib using-a-context-manager-as-a-function-decorator13238462
Ref: 423013238462
Ref: Using a context manager as a function decorator-Footnote-113240287
Node: Single use reusable and reentrant context managers13240329
Ref: library/contextlib single-use-reusable-and-reentrant-cms13240500
Ref: ecc13240500
Ref: library/contextlib single-use-reusable-and-reentrant-context-managers13240500
Ref: 423113240500
Node: Reentrant context managers13242036
Ref: library/contextlib reentrant-cms13242183
Ref: 422513242183
Ref: library/contextlib reentrant-context-managers13242183
Ref: 423213242183
Node: Reusable context managers13243714
Ref: library/contextlib reusable-cms13243861
Ref: 423313243861
Ref: library/contextlib reusable-context-managers13243861
Ref: 423413243861
Node: abc --- 抽象基底類別13246531
Ref: library/abc doc13246714
Ref: 423513246714
Ref: library/abc abc-abstract-base-classes13246714
Ref: 423613246714
Ref: library/abc module-abc13246714
Ref: 413246714
Ref: library/abc abc ABC13247718
Ref: ebb13247718
Ref: library/abc abc ABCMeta13248505
Ref: ebc13248505
Ref: library/abc abc ABCMeta register13249273
Ref: 102a13249273
Ref: library/abc abc ABCMeta __subclasshook__13249929
Ref: 240113249929
Ref: library/abc abc abstractmethod13252714
Ref: 102713252714
Ref: library/abc abc abstractclassmethod13255630
Ref: 102813255630
Ref: library/abc abc abstractstaticmethod13256329
Ref: 102913256329
Ref: library/abc abc abstractproperty13257029
Ref: 102613257029
Ref: library/abc abc get_cache_token13258364
Ref: eba13258364
Ref: library/abc abc update_abstractmethods13258746
Ref: 423713258746
Ref: abc --- 抽象基底類別-Footnote-113259379
Ref: abc --- 抽象基底類別-Footnote-213259442
Ref: abc --- 抽象基底類別-Footnote-313259484
Ref: abc --- 抽象基底類別-Footnote-413259526
Node: atexit --- 退出處理函式13259637
Ref: library/atexit doc13259825
Ref: 423813259825
Ref: library/atexit atexit-exit-handlers13259825
Ref: 423913259825
Ref: library/atexit module-atexit13259825
Ref: 913259825
Ref: library/atexit atexit register13260790
Ref: 82113260790
Ref: library/atexit atexit unregister13262264
Ref: 423a13262264
Node: atexit 範例13262923
Ref: library/atexit atexit-example13263002
Ref: 423b13263002
Ref: library/atexit id113263002
Ref: 423c13263002
Node: traceback --- 列印或取得堆疊回溯 stack traceback13264261
Ref: library/traceback doc13264460
Ref: 423d13264460
Ref: library/traceback module-traceback13264460
Ref: e713264460
Ref: library/traceback traceback-print-or-retrieve-a-stack-traceback13264460
Ref: 423e13264460
Ref: library/traceback traceback print_tb13265491
Ref: e2913265491
Ref: library/traceback traceback print_exception13266436
Ref: 7f313266436
Ref: library/traceback traceback print_exc13267951
Ref: 178213267951
Ref: library/traceback traceback print_last13268115
Ref: 423f13268115
Ref: library/traceback traceback print_stack13268397
Ref: e2a13268397
Ref: library/traceback traceback extract_tb13268957
Ref: 424013268957
Ref: library/traceback traceback extract_stack13269596
Ref: 424513269596
Ref: library/traceback traceback format_list13269907
Ref: 424613269907
Ref: library/traceback traceback format_exception_only13270414
Ref: 7f213270414
Ref: library/traceback traceback format_exception13271785
Ref: 7f113271785
Ref: library/traceback traceback format_exc13272517
Ref: 424713272517
Ref: library/traceback traceback format_tb13272675
Ref: 412d13272675
Ref: library/traceback traceback format_stack13272785
Ref: 424813272785
Ref: library/traceback traceback clear_frames13272904
Ref: f7713272904
Ref: library/traceback traceback walk_stack13273147
Ref: e2513273147
Ref: library/traceback traceback walk_tb13273463
Ref: e2613273463
Ref: traceback --- 列印或取得堆疊回溯 stack traceback-Footnote-113273898
Node: TracebackException 物件13273967
Ref: library/traceback tracebackexception-objects13274114
Ref: 424a13274114
Ref: library/traceback traceback TracebackException13274346
Ref: 24113274346
Ref: library/traceback traceback TracebackException __cause__13275617
Ref: 424c13275617
Ref: library/traceback traceback TracebackException __context__13275722
Ref: 424b13275722
Ref: library/traceback traceback TracebackException exceptions13275841
Ref: 424e13275841
Ref: library/traceback traceback TracebackException __suppress_context__13276117
Ref: 424d13276117
Ref: library/traceback traceback TracebackException __notes__13276250
Ref: 424f13276250
Ref: library/traceback traceback TracebackException stack13276557
Ref: 425013276557
Ref: library/traceback traceback TracebackException exc_type13276647
Ref: 24213276647
Ref: library/traceback traceback TracebackException exc_type_str13276762
Ref: 24013276762
Ref: library/traceback traceback TracebackException filename13276893
Ref: 425113276893
Ref: library/traceback traceback TracebackException lineno13276991
Ref: 425213276991
Ref: library/traceback traceback TracebackException end_lineno13277089
Ref: 425313277089
Ref: library/traceback traceback TracebackException text13277274
Ref: 425413277274
Ref: library/traceback traceback TracebackException offset13277363
Ref: 425513277363
Ref: library/traceback traceback TracebackException end_offset13277480
Ref: 425613277480
Ref: library/traceback traceback TracebackException msg13277674
Ref: 425713277674
Ref: library/traceback traceback TracebackException from_exception13277755
Ref: 425813277755
Ref: library/traceback traceback TracebackException print13278138
Ref: 64913278138
Ref: library/traceback traceback TracebackException format13278346
Ref: 425913278346
Ref: library/traceback traceback TracebackException format_exception_only13278797
Ref: 24313278797
Node: StackSummary 物件13279827
Ref: library/traceback stacksummary-objects13280002
Ref: 425a13280002
Ref: library/traceback traceback StackSummary13280165
Ref: e2713280165
Ref: library/traceback traceback StackSummary extract13280201
Ref: 424913280201
Ref: library/traceback traceback StackSummary from_list13281191
Ref: 425b13281191
Ref: library/traceback traceback StackSummary format13281495
Ref: 425c13281495
Ref: library/traceback traceback StackSummary format_frame_summary13282125
Ref: 64813282125
Node: FrameSummary 物件13282529
Ref: library/traceback framesummary-objects13282697
Ref: 425d13282697
Ref: library/traceback traceback FrameSummary13282881
Ref: e2813282881
Ref: library/traceback traceback FrameSummary filename13283740
Ref: 424113283740
Ref: library/traceback traceback FrameSummary lineno13283940
Ref: 424213283940
Ref: library/traceback traceback FrameSummary name13284027
Ref: 424313284027
Ref: library/traceback traceback FrameSummary line13284160
Ref: 424413284160
Node: Traceback Examples13284366
Ref: library/traceback traceback-example13284506
Ref: 425e13284506
Ref: library/traceback traceback-examples13284506
Ref: 425f13284506
Node: __future__ --- Future 陳述式定義13289939
Ref: library/__future__ doc13290165
Ref: 426013290165
Ref: library/__future__ future-future-statement-definitions13290165
Ref: 426113290165
Ref: library/__future__ module-__future__13290165
Ref: 013290165
Ref: __future__ --- Future 陳述式定義-Footnote-113291533
Node: 模組內容<9>13291603
Ref: library/__future__ module-contents13291692
Ref: 426213291692
Ref: library/__future__ future-classes13294919
Ref: 426313294919
Ref: library/__future__ future__ _Feature13294919
Ref: 203d13294919
Ref: library/__future__ future__ _Feature getOptionalRelease13295572
Ref: 426413295572
Ref: library/__future__ future__ _Feature getMandatoryRelease13295691
Ref: 426513295691
Ref: library/__future__ future__ _Feature compiler_flag13296217
Ref: 203e13296217
Ref: 模組內容<9>-Footnote-113296759
Ref: 模組內容<9>-Footnote-213296801
Ref: 模組內容<9>-Footnote-313296843
Ref: 模組內容<9>-Footnote-413296885
Ref: 模組內容<9>-Footnote-513296927
Ref: 模組內容<9>-Footnote-613296969
Ref: 模組內容<9>-Footnote-713297011
Ref: 模組內容<9>-Footnote-813297053
Ref: 模組內容<9>-Footnote-913297095
Ref: 模組內容<9>-Footnote-1013297682
Ref: 模組內容<9>-Footnote-1113297725
Node: gc --- 垃圾回收器介面 Garbage Collector interface13297768
Ref: library/gc doc13297967
Ref: 426613297967
Ref: library/gc gc-garbage-collector-interface13297967
Ref: 426713297967
Ref: library/gc module-gc13297967
Ref: 5613297967
Ref: library/gc gc enable13298936
Ref: 426813298936
Ref: library/gc gc disable13298996
Ref: 426913298996
Ref: library/gc gc isenabled13299057
Ref: 426a13299057
Ref: library/gc gc collect13299143
Ref: 16b13299143
Ref: library/gc gc set_debug13300258
Ref: 426b13300258
Ref: library/gc gc get_debug13300507
Ref: 426c13300507
Ref: library/gc gc get_objects13300579
Ref: 7a713300579
Ref: library/gc gc get_stats13301204
Ref: 1cd13301204
Ref: library/gc gc set_threshold13301791
Ref: 1cb13301791
Ref: library/gc gc get_count13303039
Ref: 1cc13303039
Ref: library/gc gc get_threshold13303156
Ref: 1ca13303156
Ref: library/gc gc get_referrers13303294
Ref: 7a813303294
Ref: library/gc gc get_referents13304234
Ref: 7a913304234
Ref: library/gc gc is_tracked13304928
Ref: 12a213304928
Ref: library/gc gc is_finalized13305703
Ref: 8a213305703
Ref: library/gc gc freeze13306200
Ref: ade13306200
Ref: library/gc gc unfreeze13306977
Ref: adf13306977
Ref: library/gc gc get_freeze_count13307121
Ref: ae013307121
Ref: library/gc gc garbage13307330
Ref: 115913307330
Ref: library/gc gc callbacks13308201
Ref: 106113308201
Ref: library/gc gc DEBUG_STATS13309449
Ref: 426e13309449
Ref: library/gc gc DEBUG_COLLECTABLE13309583
Ref: 426f13309583
Ref: library/gc gc DEBUG_UNCOLLECTABLE13309666
Ref: 115a13309666
Ref: library/gc gc DEBUG_SAVEALL13310040
Ref: 426d13310040
Ref: library/gc gc DEBUG_LEAK13310247
Ref: 427013310247
Ref: gc --- 垃圾回收器介面 Garbage Collector interface-Footnote-113310486
Ref: gc --- 垃圾回收器介面 Garbage Collector interface-Footnote-213310540
Node: inspect --- 檢視活動物件13310582
Ref: library/inspect doc13310785
Ref: 427113310785
Ref: library/inspect inspect-inspect-live-objects13310785
Ref: 427213310785
Ref: library/inspect module-inspect13310864
Ref: 7213310864
Ref: inspect --- 檢視活動物件-Footnote-113311998
Node: Types and members13312065
Ref: library/inspect inspect-types13312173
Ref: 18ae13312173
Ref: library/inspect types-and-members13312173
Ref: 427313312173
Ref: library/inspect inspect getmembers13329217
Ref: 175813329217
Ref: library/inspect inspect getmembers_static13329828
Ref: 5ef13329828
Ref: library/inspect inspect getmodulename13330565
Ref: ce013330565
Ref: library/inspect inspect ismodule13331224
Ref: 427513331224
Ref: library/inspect inspect isclass13331317
Ref: 427613331317
Ref: library/inspect inspect ismethod13331454
Ref: 427713331454
Ref: library/inspect inspect isfunction13331568
Ref: 427813331568
Ref: library/inspect inspect isgeneratorfunction13331744
Ref: 16d613331744
Ref: library/inspect inspect isgenerator13332210
Ref: 427913332210
Ref: library/inspect inspect iscoroutinefunction13332309
Ref: 43913332309
Ref: library/inspect inspect markcoroutinefunction13333151
Ref: 43713333151
Ref: library/inspect inspect iscoroutine13333740
Ref: dbc13333740
Ref: library/inspect inspect isawaitable13333926
Ref: dbd13333926
Ref: library/inspect inspect isasyncgenfunction13334400
Ref: 16d713334400
Ref: library/inspect inspect isasyncgen13335089
Ref: 427a13335089
Ref: library/inspect inspect istraceback13335317
Ref: 427b13335317
Ref: library/inspect inspect isframe13335413
Ref: 427c13335413
Ref: library/inspect inspect iscode13335501
Ref: 427d13335501
Ref: library/inspect inspect isbuiltin13335595
Ref: 427e13335595
Ref: library/inspect inspect ismethodwrapper13335729
Ref: 5f013335729
Ref: library/inspect inspect isroutine13336032
Ref: 14de13336032
Ref: library/inspect inspect isabstract13336162
Ref: 427f13336162
Ref: library/inspect inspect ismethoddescriptor13336269
Ref: 14dd13336269
Ref: library/inspect inspect isdatadescriptor13337466
Ref: 428013337466
Ref: library/inspect inspect isgetsetdescriptor13338097
Ref: 428113338097
Ref: library/inspect inspect ismemberdescriptor13338439
Ref: 428213338439
Node: 取得原始碼13338793
Ref: library/inspect inspect-source13338959
Ref: 428313338959
Ref: library/inspect retrieving-source-code13338959
Ref: 428413338959
Ref: library/inspect inspect getdoc13339007
Ref: 99e13339007
Ref: library/inspect inspect getcomments13339511
Ref: 3dfe13339511
Ref: library/inspect inspect getfile13339929
Ref: 19aa13339929
Ref: library/inspect inspect getmodule13340161
Ref: 16e913340161
Ref: library/inspect inspect getsourcefile13340319
Ref: 16ea13340319
Ref: library/inspect inspect getsourcelines13340618
Ref: 428513340618
Ref: library/inspect inspect getsource13341329
Ref: 14ca13341329
Ref: library/inspect inspect cleandoc13341876
Ref: 15ad13341876
Node: Introspecting callables with the Signature object13342285
Ref: library/inspect inspect-signature-object13342449
Ref: 428613342449
Ref: library/inspect introspecting-callables-with-the-signature-object13342449
Ref: 428713342449
Ref: library/inspect inspect signature13342780
Ref: 6dc13342780
Ref: library/inspect inspect Signature13345346
Ref: 1b313345346
Ref: library/inspect inspect Signature empty13346456
Ref: 428a13346456
Ref: library/inspect inspect Signature parameters13346573
Ref: 428813346573
Ref: library/inspect inspect Signature return_annotation13347061
Ref: 428b13347061
Ref: library/inspect inspect Signature bind13347269
Ref: 150d13347269
Ref: library/inspect inspect Signature bind_partial13347547
Ref: 428c13347547
Ref: library/inspect inspect Signature replace13347924
Ref: 428913347924
Ref: library/inspect inspect Signature format13348798
Ref: 428d13348798
Ref: library/inspect inspect Signature from_callable13349212
Ref: 6de13349212
Ref: library/inspect inspect Parameter13349926
Ref: 1b413349926
Ref: library/inspect inspect Parameter empty13350337
Ref: 428f13350337
Ref: library/inspect inspect Parameter name13350465
Ref: 429013350465
Ref: library/inspect inspect Parameter default13350921
Ref: 429113350921
Ref: library/inspect inspect Parameter annotation13351109
Ref: 429213351109
Ref: library/inspect inspect Parameter kind13351294
Ref: 429313351294
Ref: library/inspect inspect Parameter kind description13354192
Ref: 429413354192
Ref: library/inspect inspect Parameter replace13354733
Ref: 428e13354733
Ref: library/inspect inspect BoundArguments13355865
Ref: 100a13355865
Ref: library/inspect inspect BoundArguments arguments13356068
Ref: 8b113356068
Ref: library/inspect inspect BoundArguments args13356910
Ref: 429513356910
Ref: library/inspect inspect BoundArguments kwargs13357058
Ref: 429613357058
Ref: library/inspect inspect BoundArguments signature13357204
Ref: 429713357204
Ref: library/inspect inspect BoundArguments apply_defaults13357299
Ref: dbb13357299
Ref: Introspecting callables with the Signature object-Footnote-113358272
Node: 類別與函式13358314
Ref: library/inspect classes-and-functions13358478
Ref: 429813358478
Ref: library/inspect inspect-classes-functions13358478
Ref: 429913358478
Ref: library/inspect inspect getclasstree13358526
Ref: 429a13358526
Ref: library/inspect inspect getfullargspec13359103
Ref: 6dd13359103
Ref: library/inspect inspect getargvalues13361461
Ref: e6013361461
Ref: library/inspect inspect formatargvalues13361966
Ref: e6113361966
Ref: library/inspect inspect getmro13362436
Ref: 429b13362436
Ref: library/inspect inspect getcallargs13362794
Ref: e5f13362794
Ref: library/inspect inspect getclosurevars13364155
Ref: 106f13364155
Ref: library/inspect inspect unwrap13364867
Ref: eff13364867
Ref: library/inspect inspect get_annotations13365598
Ref: 7b713365598
Node: 直譯器堆疊13368494
Ref: library/inspect inspect-stack13368639
Ref: 429c13368639
Ref: library/inspect the-interpreter-stack13368639
Ref: 429d13368639
Ref: library/inspect inspect FrameInfo13368944
Ref: 5f213368944
Ref: library/inspect inspect FrameInfo frame13368975
Ref: 429e13368975
Ref: library/inspect inspect FrameInfo filename13369071
Ref: 429f13369071
Ref: library/inspect inspect FrameInfo lineno13369214
Ref: 42a013369214
Ref: library/inspect inspect FrameInfo function13369377
Ref: 42a113369377
Ref: library/inspect inspect FrameInfo code_context13369507
Ref: 42a213369507
Ref: library/inspect inspect FrameInfo index13369670
Ref: 42a313369670
Ref: library/inspect inspect FrameInfo positions13369799
Ref: 42a413369799
Ref: library/inspect inspect Traceback13370331
Ref: 5f313370331
Ref: library/inspect inspect Traceback filename13370362
Ref: 42a613370362
Ref: library/inspect inspect Traceback lineno13370508
Ref: 42a713370508
Ref: library/inspect inspect Traceback function13370674
Ref: 42a813370674
Ref: library/inspect inspect Traceback code_context13370807
Ref: 42a913370807
Ref: library/inspect inspect Traceback index13370973
Ref: 42aa13370973
Ref: library/inspect inspect Traceback positions13371102
Ref: 42ab13371102
Ref: library/inspect inspect getframeinfo13373028
Ref: 5f513373028
Ref: library/inspect inspect getouterframes13373291
Ref: 5f613373291
Ref: library/inspect inspect getinnerframes13373882
Ref: 5f713373882
Ref: library/inspect inspect currentframe13374470
Ref: 68513374470
Ref: library/inspect inspect stack13374853
Ref: 5f813374853
Ref: library/inspect inspect trace13375337
Ref: 5f913375337
Node: Fetching attributes statically13375912
Ref: library/inspect fetching-attributes-statically13376108
Ref: 42ac13376108
Ref: library/inspect inspect getattr_static13376690
Ref: 43c13376690
Node: Current State of Generators Coroutines and Asynchronous Generators13378493
Ref: library/inspect current-state-of-generators-coroutines-and-asynchronous-generators13378696
Ref: 42ad13378696
Ref: library/inspect inspect getgeneratorstate13379178
Ref: 11ce13379178
Ref: library/inspect inspect getcoroutinestate13379571
Ref: dbf13379571
Ref: library/inspect inspect getasyncgenstate13380185
Ref: 43a13380185
Ref: library/inspect inspect getgeneratorlocals13381024
Ref: 107013381024
Ref: library/inspect inspect getcoroutinelocals13381886
Ref: dbe13381886
Ref: library/inspect inspect getasyncgenlocals13382122
Ref: 43b13382122
Node: Code Objects Bit Flags13382408
Ref: library/inspect code-objects-bit-flags13382593
Ref: 42ae13382593
Ref: library/inspect inspect-module-co-flags13382593
Ref: 1e1b13382593
Ref: library/inspect inspect CO_OPTIMIZED13382763
Ref: 42af13382763
Ref: library/inspect inspect CO_NEWLOCALS13382852
Ref: 42b013382852
Ref: library/inspect inspect CO_VARARGS13383003
Ref: 42b113383003
Ref: library/inspect inspect CO_VARKEYWORDS13383113
Ref: 42b213383113
Ref: library/inspect inspect CO_NESTED13383227
Ref: 42b313383227
Ref: library/inspect inspect CO_GENERATOR13383323
Ref: 42b413383323
Ref: library/inspect inspect CO_COROUTINE13383500
Ref: 42b513383500
Ref: library/inspect inspect CO_ITERABLE_COROUTINE13383739
Ref: 42b613383739
Ref: library/inspect inspect CO_ASYNC_GENERATOR13384056
Ref: 42b713384056
Ref: Code Objects Bit Flags-Footnote-113384705
Ref: Code Objects Bit Flags-Footnote-213384747
Ref: Code Objects Bit Flags-Footnote-313384789
Node: Buffer flags13384831
Ref: library/inspect buffer-flags13384968
Ref: 42b813384968
Ref: library/inspect inspect BufferFlags13385015
Ref: 40613385015
Ref: library/inspect inspect BufferFlags SIMPLE13385327
Ref: 42ba13385327
Ref: library/inspect inspect BufferFlags WRITABLE13385352
Ref: 42bb13385352
Ref: library/inspect inspect BufferFlags FORMAT13385379
Ref: 42bc13385379
Ref: library/inspect inspect BufferFlags ND13385404
Ref: 42bd13385404
Ref: library/inspect inspect BufferFlags STRIDES13385425
Ref: 42be13385425
Ref: library/inspect inspect BufferFlags C_CONTIGUOUS13385451
Ref: 42bf13385451
Ref: library/inspect inspect BufferFlags F_CONTIGUOUS13385482
Ref: 42c013385482
Ref: library/inspect inspect BufferFlags ANY_CONTIGUOUS13385513
Ref: 42c113385513
Ref: library/inspect inspect BufferFlags INDIRECT13385546
Ref: 42c213385546
Ref: library/inspect inspect BufferFlags CONTIG13385573
Ref: 42c313385573
Ref: library/inspect inspect BufferFlags CONTIG_RO13385598
Ref: 42c413385598
Ref: library/inspect inspect BufferFlags STRIDED13385626
Ref: 42c513385626
Ref: library/inspect inspect BufferFlags STRIDED_RO13385652
Ref: 42c613385652
Ref: library/inspect inspect BufferFlags RECORDS13385681
Ref: 42c713385681
Ref: library/inspect inspect BufferFlags RECORDS_RO13385707
Ref: 42c813385707
Ref: library/inspect inspect BufferFlags FULL13385736
Ref: 42c913385736
Ref: library/inspect inspect BufferFlags FULL_RO13385759
Ref: 42ca13385759
Ref: library/inspect inspect BufferFlags READ13385785
Ref: 42cb13385785
Ref: library/inspect inspect BufferFlags WRITE13385808
Ref: 42cc13385808
Node: 命令列介面<6>13385861
Ref: library/inspect command-line-interface13385967
Ref: 42cd13385967
Ref: library/inspect inspect-module-cli13385967
Ref: efe13385967
Ref: library/inspect cmdoption-inspect-details13386325
Ref: 42ce13386325
Node: site --- Site-specific configuration hook13386432
Ref: library/site doc13386570
Ref: 42cf13386570
Ref: library/site module-site13386570
Ref: b513386570
Ref: library/site site-site-specific-configuration-hook13386570
Ref: 42d013386570
Ref: site --- Site-specific configuration hook-Footnote-113391463
Node: sitecustomize13391527
Ref: library/site module-sitecustomize13391640
Ref: b613391640
Ref: library/site sitecustomize13391640
Ref: 42d213391640
Node: usercustomize13392404
Ref: library/site module-usercustomize13392548
Ref: f713392548
Ref: library/site usercustomize13392548
Ref: 42d313392548
Node: Readline configuration13393354
Ref: library/site readline-configuration13393501
Ref: 42d513393501
Ref: library/site rlcompleter-config13393501
Ref: f6c13393501
Node: 模組內容<10>13394167
Ref: library/site module-contents13394319
Ref: 42d613394319
Ref: library/site site PREFIXES13394362
Ref: 42d713394362
Ref: library/site site ENABLE_USER_SITE13394445
Ref: 42d413394445
Ref: library/site site USER_SITE13394885
Ref: 1c3713394885
Ref: library/site site USER_BASE13395498
Ref: 12b013395498
Ref: library/site site main13396058
Ref: 1c3813396058
Ref: library/site site addsitedir13396399
Ref: 42d813396399
Ref: library/site site getsitepackages13396618
Ref: 11d613396618
Ref: library/site site getuserbase13396752
Ref: 11d713396752
Ref: library/site site getusersitepackages13396997
Ref: 11d813396997
Node: 命令列介面<7>13397397
Ref: library/site command-line-interface13397518
Ref: 42d913397518
Ref: library/site site-commandline13397518
Ref: 42da13397518
Ref: library/site cmdoption-site-user-base13398047
Ref: 42db13398047
Ref: library/site cmdoption-site-user-site13398121
Ref: 42dc13398121
Ref: 命令列介面<7>-Footnote-113398850
Node: 自訂 Python 直譯器13398892
Ref: library/custominterp doc13399042
Ref: 42dd13399042
Ref: library/custominterp custom-python-interpreters13399042
Ref: 42de13399042
Ref: library/custominterp custominterp13399042
Ref: 42df13399042
Node: code --- 直譯器基底類別13399658
Ref: library/code doc13399791
Ref: 42e013399791
Ref: library/code code-interpreter-base-classes13399791
Ref: 42e113399791
Ref: library/code module-code13399791
Ref: 1313399791
Ref: library/code code InteractiveInterpreter13400195
Ref: 14cc13400195
Ref: library/code code InteractiveConsole13400726
Ref: 227a13400726
Ref: library/code code interact13401283
Ref: 15d013401283
Ref: library/code code compile_command13402214
Ref: 42e413402214
Ref: code --- 直譯器基底類別-Footnote-113403496
Node: Interactive Interpreter Objects13403560
Ref: library/code interactive-interpreter-objects13403694
Ref: 42e513403694
Ref: library/code interpreter-objects13403694
Ref: 42e613403694
Ref: library/code code InteractiveInterpreter runsource13403777
Ref: 42e713403777
Ref: library/code code InteractiveInterpreter runcode13405064
Ref: 42e913405064
Ref: library/code code InteractiveInterpreter showsyntaxerror13405523
Ref: 42e813405523
Ref: library/code code InteractiveInterpreter showtraceback13405993
Ref: d7613405993
Ref: library/code code InteractiveInterpreter write13406372
Ref: 42ea13406372
Node: Interactive Console Objects13406592
Ref: library/code console-objects13406726
Ref: 42eb13406726
Ref: library/code interactive-console-objects13406726
Ref: 42ec13406726
Ref: library/code code InteractiveConsole interact13406990
Ref: 42e313406990
Ref: library/code code InteractiveConsole push13407835
Ref: 42ed13407835
Ref: library/code code InteractiveConsole resetbuffer13408541
Ref: 42ee13408541
Ref: library/code code InteractiveConsole raw_input13408650
Ref: 42e213408650
Node: codeop --- 編譯 Python 程式碼13409011
Ref: library/codeop doc13409144
Ref: 42ef13409144
Ref: library/codeop codeop-compile-python-code13409144
Ref: 42f013409144
Ref: library/codeop module-codeop13409144
Ref: 1513409144
Ref: library/codeop codeop compile_command13410097
Ref: 16cd13410097
Ref: library/codeop codeop Compile13411516
Ref: 42f113411516
Ref: library/codeop codeop CommandCompiler13411913
Ref: 42f213411913
Ref: codeop --- 編譯 Python 程式碼-Footnote-113412331
Node: 引入模組13412397
Ref: library/modules doc13412545
Ref: 42f313412545
Ref: library/modules importing-modules13412545
Ref: 42f413412545
Ref: library/modules modules13412545
Ref: 42f513412545
Node: zipimport --- 從 Zip 封存檔案匯入模組13413637
Ref: library/zipimport doc13413777
Ref: 42f613413777
Ref: library/zipimport module-zipimport13413777
Ref: 11813413777
Ref: library/zipimport zipimport-import-modules-from-zip-archives13413777
Ref: 42f713413777
Ref: library/zipimport zipimport ZipImportError13415963
Ref: 42f813415963
Ref: zipimport --- 從 Zip 封存檔案匯入模組-Footnote-113416245
Ref: zipimport --- 從 Zip 封存檔案匯入模組-Footnote-213416314
Ref: zipimport --- 從 Zip 封存檔案匯入模組-Footnote-313416382
Ref: zipimport --- 從 Zip 封存檔案匯入模組-Footnote-413416424
Ref: zipimport --- 從 Zip 封存檔案匯入模組-Footnote-513416466
Node: zipimporter 物件13416508
Ref: library/zipimport id113416628
Ref: 42f913416628
Ref: library/zipimport zipimporter-objects13416628
Ref: 42fa13416628
Ref: library/zipimport zipimport zipimporter13416747
Ref: 42fb13416747
Ref: library/zipimport zipimport zipimporter create_module13417383
Ref: 80313417383
Ref: library/zipimport zipimport zipimporter exec_module13417629
Ref: 2e413417629
Ref: library/zipimport zipimport zipimporter find_spec13417788
Ref: 80213417788
Ref: library/zipimport zipimport zipimporter get_code13417970
Ref: 42fc13417970
Ref: library/zipimport zipimport zipimporter get_data13418149
Ref: 42fd13418149
Ref: library/zipimport zipimport zipimporter get_filename13418429
Ref: 42fe13418429
Ref: library/zipimport zipimport zipimporter get_source13418692
Ref: 42ff13418692
Ref: library/zipimport zipimport zipimporter is_package13418980
Ref: 430013418980
Ref: library/zipimport zipimport zipimporter load_module13419189
Ref: 2e313419189
Ref: library/zipimport zipimport zipimporter invalidate_caches13419541
Ref: 80413419541
Ref: library/zipimport zipimport zipimporter archive13419721
Ref: 430113419721
Ref: library/zipimport zipimport zipimporter prefix13419849
Ref: 430213419849
Node: 範例<45>13420253
Ref: library/zipimport examples13420373
Ref: 430313420373
Ref: library/zipimport zipimport-examples13420373
Ref: 430413420373
Node: pkgutil --- 套件擴充工具程式13421065
Ref: library/pkgutil doc13421261
Ref: 430513421261
Ref: library/pkgutil module-pkgutil13421261
Ref: 9713421261
Ref: library/pkgutil pkgutil-package-extension-utility13421261
Ref: 430613421261
Ref: library/pkgutil pkgutil ModuleInfo13421546
Ref: cf213421546
Ref: library/pkgutil pkgutil extend_path13421712
Ref: 14d813421712
Ref: library/pkgutil pkgutil find_loader13423314
Ref: 2ad13423314
Ref: library/pkgutil pkgutil get_importer13424006
Ref: 430713424006
Ref: library/pkgutil pkgutil get_loader13424544
Ref: 2ae13424544
Ref: library/pkgutil pkgutil iter_importers13425297
Ref: 113213425297
Ref: library/pkgutil pkgutil iter_modules13426011
Ref: cf113426011
Ref: library/pkgutil pkgutil walk_packages13426816
Ref: ba613426816
Ref: library/pkgutil pkgutil get_data13428298
Ref: 430813428298
Ref: library/pkgutil pkgutil resolve_name13429295
Ref: 430a13429295
Ref: pkgutil --- 套件擴充工具程式-Footnote-113431003
Ref: pkgutil --- 套件擴充工具程式-Footnote-213431070
Ref: pkgutil --- 套件擴充工具程式-Footnote-313431112
Ref: pkgutil --- 套件擴充工具程式-Footnote-413431154
Ref: pkgutil --- 套件擴充工具程式-Footnote-513431196
Ref: pkgutil --- 套件擴充工具程式-Footnote-613431238
Ref: pkgutil --- 套件擴充工具程式-Footnote-713431280
Ref: pkgutil --- 套件擴充工具程式-Footnote-813431322
Ref: pkgutil --- 套件擴充工具程式-Footnote-913431364
Ref: pkgutil --- 套件擴充工具程式-Footnote-1013431406
Node: modulefinder --- 搜尋腳本所使用的模組13431472
Ref: library/modulefinder doc13431661
Ref: 430b13431661
Ref: library/modulefinder module-modulefinder13431661
Ref: 8413431661
Ref: library/modulefinder modulefinder-find-modules-used-by-a-script13431661
Ref: 430c13431661
Ref: library/modulefinder modulefinder AddPackagePath13432139
Ref: 430d13432139
Ref: library/modulefinder modulefinder ReplacePackage13432275
Ref: 430e13432275
Ref: library/modulefinder modulefinder ModuleFinder13432421
Ref: 190913432421
Ref: library/modulefinder modulefinder ModuleFinder report13433019
Ref: 431013433019
Ref: library/modulefinder modulefinder ModuleFinder run_script13433193
Ref: 430f13433193
Ref: library/modulefinder modulefinder ModuleFinder modules13433322
Ref: 431113433322
Ref: modulefinder --- 搜尋腳本所使用的模組-Footnote-113433545
Node: ModuleFinder 的用法範例13433617
Ref: library/modulefinder example-usage-of-modulefinder13433729
Ref: 431313433729
Ref: library/modulefinder modulefinder-example13433729
Ref: 431213433729
Node: runpy --- 定位並執行 Python 模組13435042
Ref: library/runpy doc13435225
Ref: 431413435225
Ref: library/runpy module-runpy13435225
Ref: ac13435225
Ref: library/runpy runpy-locating-and-executing-python-modules13435225
Ref: 431513435225
Ref: library/runpy runpy run_module13436236
Ref: 171113436236
Ref: library/runpy runpy run_path13439646
Ref: 16413439646
Ref: runpy --- 定位並執行 Python 模組-Footnote-113444048
Ref: runpy --- 定位並執行 Python 模組-Footnote-213444113
Ref: runpy --- 定位並執行 Python 模組-Footnote-313444155
Ref: runpy --- 定位並執行 Python 模組-Footnote-413444197
Ref: runpy --- 定位並執行 Python 模組-Footnote-513444239
Ref: runpy --- 定位並執行 Python 模組-Footnote-613444281
Ref: runpy --- 定位並執行 Python 模組-Footnote-713444323
Ref: runpy --- 定位並執行 Python 模組-Footnote-813444365
Node: importlib --- import 的實作13444407
Ref: library/importlib doc13444609
Ref: 431613444609
Ref: library/importlib importlib-the-implementation-of-import13444609
Ref: 431713444609
Ref: library/importlib module-importlib13444609
Ref: 6b13444609
Ref: importlib --- import 的實作-Footnote-113445246
Node: 簡介<9>13445325
Ref: library/importlib introduction13445420
Ref: 431813445420
Ref: 簡介<9>-Footnote-113447680
Ref: 簡介<9>-Footnote-213447732
Ref: 簡介<9>-Footnote-313447774
Ref: 簡介<9>-Footnote-413447816
Ref: 簡介<9>-Footnote-513447858
Ref: 簡介<9>-Footnote-613447900
Ref: 簡介<9>-Footnote-713447942
Ref: 簡介<9>-Footnote-813447984
Ref: 簡介<9>-Footnote-913448026
Ref: 簡介<9>-Footnote-1013448068
Ref: 簡介<9>-Footnote-1113448111
Ref: 簡介<9>-Footnote-1213448154
Ref: 簡介<9>-Footnote-1313448197
Node: 函式<11>13448240
Ref: library/importlib functions13448400
Ref: 431913448400
Ref: library/importlib importlib __import__13448431
Ref: 100e13448431
Ref: library/importlib importlib import_module13448739
Ref: 4bc13448739
Ref: library/importlib importlib invalidate_caches13450066
Ref: bb713450066
Ref: library/importlib importlib reload13450693
Ref: 4bd13450693
Node: importlib abc -- Abstract base classes related to import13453916
Ref: library/importlib importlib-abc-abstract-base-classes-related-to-import13454114
Ref: 431a13454114
Ref: library/importlib module-importlib abc13454114
Ref: 6c13454114
Ref: library/importlib importlib abc MetaPathFinder13454904
Ref: 81313454904
Ref: library/importlib importlib abc MetaPathFinder find_spec13455115
Ref: 80d13455115
Ref: library/importlib importlib abc MetaPathFinder invalidate_caches13455860
Ref: 431b13455860
Ref: library/importlib importlib abc PathEntryFinder13456272
Ref: 81413456272
Ref: library/importlib importlib abc PathEntryFinder find_spec13456708
Ref: 81113456708
Ref: library/importlib importlib abc PathEntryFinder invalidate_caches13457347
Ref: 431c13457347
Ref: library/importlib importlib abc Loader13457647
Ref: e6913457647
Ref: library/importlib importlib abc Loader create_module13458073
Ref: c5513458073
Ref: library/importlib importlib abc Loader exec_module13458473
Ref: 80f13458473
Ref: library/importlib importlib abc Loader load_module13458938
Ref: 80e13458938
Ref: library/importlib importlib abc ResourceLoader13462346
Ref: b8e13462346
Ref: library/importlib importlib abc ResourceLoader get_data13462730
Ref: 430913462730
Ref: library/importlib importlib abc InspectLoader13463412
Ref: ef713463412
Ref: library/importlib importlib abc InspectLoader get_code13463597
Ref: ef813463597
Ref: library/importlib importlib abc InspectLoader get_source13464180
Ref: efb13464180
Ref: library/importlib importlib abc InspectLoader is_package13464760
Ref: 431e13464760
Ref: library/importlib importlib abc InspectLoader source_to_code13465129
Ref: db713465129
Ref: library/importlib importlib abc InspectLoader exec_module13465769
Ref: fb313465769
Ref: library/importlib importlib abc InspectLoader load_module13465898
Ref: 431f13465898
Ref: library/importlib importlib abc ExecutionLoader13466074
Ref: 432013466074
Ref: library/importlib importlib abc ExecutionLoader get_filename13466322
Ref: 432113466322
Ref: library/importlib importlib abc FileLoader13466867
Ref: 101413466867
Ref: library/importlib importlib abc FileLoader name13467364
Ref: 432213467364
Ref: library/importlib importlib abc FileLoader path13467444
Ref: 432313467444
Ref: library/importlib importlib abc FileLoader load_module13467510
Ref: 432413467510
Ref: library/importlib importlib abc FileLoader get_filename13467692
Ref: 432513467692
Ref: library/importlib importlib abc FileLoader get_data13467786
Ref: 432613467786
Ref: library/importlib importlib abc SourceLoader13467907
Ref: 432713467907
Ref: library/importlib importlib abc SourceLoader path_stats13469003
Ref: 112413469003
Ref: library/importlib importlib abc SourceLoader path_mtime13469781
Ref: 112313469781
Ref: library/importlib importlib abc SourceLoader set_data13470314
Ref: 432813470314
Ref: library/importlib importlib abc SourceLoader get_code13470827
Ref: 432913470827
Ref: library/importlib importlib abc SourceLoader exec_module13470950
Ref: fb413470950
Ref: library/importlib importlib abc SourceLoader load_module13471093
Ref: 432a13471093
Ref: library/importlib importlib abc SourceLoader get_source13471283
Ref: fc413471283
Ref: library/importlib importlib abc SourceLoader is_package13471410
Ref: 432b13471410
Ref: library/importlib importlib abc ResourceReader13471813
Ref: aa013471813
Ref: library/importlib importlib abc ResourceReader open_resource13473657
Ref: 432c13473657
Ref: library/importlib importlib abc ResourceReader resource_path13473918
Ref: 432d13473918
Ref: library/importlib importlib abc ResourceReader is_resource13474154
Ref: 432e13474154
Ref: library/importlib importlib abc ResourceReader contents13474368
Ref: 194a13474368
Ref: library/importlib importlib abc Traversable13475237
Ref: 178713475237
Ref: library/importlib importlib abc Traversable name13475678
Ref: 432f13475678
Ref: library/importlib importlib abc Traversable iterdir13475793
Ref: 433013475793
Ref: library/importlib importlib abc Traversable is_dir13475895
Ref: 433113475895
Ref: library/importlib importlib abc Traversable is_file13475997
Ref: 433213475997
Ref: library/importlib importlib abc Traversable joinpath13476095
Ref: 433313476095
Ref: library/importlib importlib abc Traversable __truediv__13476196
Ref: 433413476196
Ref: library/importlib importlib abc Traversable open13476306
Ref: 433513476306
Ref: library/importlib importlib abc Traversable read_bytes13476662
Ref: 433613476662
Ref: library/importlib importlib abc Traversable read_text13476743
Ref: 433713476743
Ref: library/importlib importlib abc TraversableResources13476835
Ref: 178513476835
Ref: library/importlib importlib abc TraversableResources files13477605
Ref: 433813477605
Ref: importlib abc -- Abstract base classes related to import-Footnote-113477793
Ref: importlib abc -- Abstract base classes related to import-Footnote-213477866
Ref: importlib abc -- Abstract base classes related to import-Footnote-313477908
Ref: importlib abc -- Abstract base classes related to import-Footnote-413477950
Ref: importlib abc -- Abstract base classes related to import-Footnote-513477992
Node: importlib machinery -- Importers and path hooks13478034
Ref: library/importlib importlib-machinery-importers-and-path-hooks13478266
Ref: 433913478266
Ref: library/importlib module-importlib machinery13478266
Ref: 6d13478266
Ref: library/importlib importlib machinery SOURCE_SUFFIXES13478594
Ref: 4b813478594
Ref: library/importlib importlib machinery DEBUG_BYTECODE_SUFFIXES13478762
Ref: 433a13478762
Ref: library/importlib importlib machinery OPTIMIZED_BYTECODE_SUFFIXES13479020
Ref: 433b13479020
Ref: library/importlib importlib machinery BYTECODE_SUFFIXES13479278
Ref: 4ba13479278
Ref: library/importlib importlib machinery EXTENSION_SUFFIXES13479559
Ref: 4b913479559
Ref: library/importlib importlib machinery all_suffixes13479733
Ref: 427413479733
Ref: library/importlib importlib machinery BuiltinImporter13480167
Ref: c5613480167
Ref: library/importlib importlib machinery FrozenImporter13480731
Ref: fc213480731
Ref: library/importlib importlib machinery WindowsRegistryFinder13481150
Ref: cd113481150
Ref: library/importlib importlib machinery PathFinder13481631
Ref: fc613481631
Ref: library/importlib importlib machinery PathFinder find_spec13481947
Ref: fb213481947
Ref: library/importlib importlib machinery PathFinder invalidate_caches13483106
Ref: bb613483106
Ref: library/importlib importlib machinery FileFinder13483709
Ref: 101313483709
Ref: library/importlib importlib machinery FileFinder path13485013
Ref: 433c13485013
Ref: library/importlib importlib machinery FileFinder find_spec13485083
Ref: e6813485083
Ref: library/importlib importlib machinery FileFinder invalidate_caches13485260
Ref: 433d13485260
Ref: library/importlib importlib machinery FileFinder path_hook13485340
Ref: 433e13485340
Ref: library/importlib importlib machinery SourceFileLoader13485787
Ref: 101513485787
Ref: library/importlib importlib machinery SourceFileLoader name13486082
Ref: 433f13486082
Ref: library/importlib importlib machinery SourceFileLoader path13486169
Ref: 434013486169
Ref: library/importlib importlib machinery SourceFileLoader is_package13486232
Ref: 434113486232
Ref: library/importlib importlib machinery SourceFileLoader path_stats13486361
Ref: 434213486361
Ref: library/importlib importlib machinery SourceFileLoader set_data13486498
Ref: 434313486498
Ref: library/importlib importlib machinery SourceFileLoader load_module13486637
Ref: ccf13486637
Ref: library/importlib importlib machinery SourcelessFileLoader13486954
Ref: 101613486954
Ref: library/importlib importlib machinery SourcelessFileLoader name13487429
Ref: 434413487429
Ref: library/importlib importlib machinery SourcelessFileLoader path13487510
Ref: 434513487510
Ref: library/importlib importlib machinery SourcelessFileLoader is_package13487575
Ref: 434613487575
Ref: library/importlib importlib machinery SourcelessFileLoader get_code13487701
Ref: 434713487701
Ref: library/importlib importlib machinery SourcelessFileLoader get_source13487837
Ref: 434813487837
Ref: library/importlib importlib machinery SourcelessFileLoader load_module13487976
Ref: cd013487976
Ref: library/importlib importlib machinery ExtensionFileLoader13488268
Ref: c5713488268
Ref: library/importlib importlib machinery ExtensionFileLoader name13488936
Ref: 434913488936
Ref: library/importlib importlib machinery ExtensionFileLoader path13489010
Ref: 434a13489010
Ref: library/importlib importlib machinery ExtensionFileLoader create_module13489074
Ref: 434b13489074
Ref: library/importlib importlib machinery ExtensionFileLoader exec_module13489253
Ref: 434c13489253
Ref: library/importlib importlib machinery ExtensionFileLoader is_package13489413
Ref: 434d13489413
Ref: library/importlib importlib machinery ExtensionFileLoader get_code13489594
Ref: 434e13489594
Ref: library/importlib importlib machinery ExtensionFileLoader get_source13489703
Ref: 434f13489703
Ref: library/importlib importlib machinery ExtensionFileLoader get_filename13489819
Ref: efc13489819
Ref: library/importlib importlib machinery NamespaceLoader13489931
Ref: ef913489931
Ref: library/importlib importlib machinery ModuleSpec13490584
Ref: 1d5a13490584
Ref: library/importlib importlib machinery ModuleSpec name13491425
Ref: 245313491425
Ref: library/importlib importlib machinery ModuleSpec loader13491605
Ref: 245113491605
Ref: library/importlib importlib machinery ModuleSpec origin13491780
Ref: 435013491780
Ref: library/importlib importlib machinery ModuleSpec submodule_search_locations13492227
Ref: 435113492227
Ref: library/importlib importlib machinery ModuleSpec loader_state13492722
Ref: 435213492722
Ref: library/importlib importlib machinery ModuleSpec cached13492948
Ref: 435313492948
Ref: library/importlib importlib machinery ModuleSpec parent13493212
Ref: 1ed713493212
Ref: library/importlib importlib machinery ModuleSpec has_location13493471
Ref: 435413493471
Ref: library/importlib importlib machinery AppleFrameworkLoader13493754
Ref: 1d5913493754
Ref: library/importlib importlib machinery AppleFrameworkLoader name13497056
Ref: 435513497056
Ref: library/importlib importlib machinery AppleFrameworkLoader path13497130
Ref: 435613497130
Ref: importlib machinery -- Importers and path hooks-Footnote-113497256
Ref: importlib machinery -- Importers and path hooks-Footnote-213497336
Ref: importlib machinery -- Importers and path hooks-Footnote-313497378
Ref: importlib machinery -- Importers and path hooks-Footnote-413497420
Ref: importlib machinery -- Importers and path hooks-Footnote-513497462
Node: importlib util -- Utility code for importers13497504
Ref: library/importlib importlib-util-utility-code-for-importers13497690
Ref: 435713497690
Ref: library/importlib module-importlib util13497690
Ref: 7113497690
Ref: library/importlib importlib util MAGIC_NUMBER13498013
Ref: 4b713498013
Ref: library/importlib importlib util cache_from_source13498255
Ref: 2cf13498255
Ref: library/importlib importlib util source_from_cache13500154
Ref: 4be13500154
Ref: library/importlib importlib util decode_source13500777
Ref: efa13500777
Ref: library/importlib importlib util resolve_name13501047
Ref: 8af13501047
Ref: library/importlib importlib util find_spec13501945
Ref: 2af13501945
Ref: library/importlib importlib util module_from_spec13502836
Ref: db813502836
Ref: library/importlib importlib util spec_from_loader13503469
Ref: 81213503469
Ref: library/importlib importlib util spec_from_file_location13503922
Ref: c5813503922
Ref: library/importlib importlib util source_hash13504401
Ref: 435813504401
Ref: library/importlib importlib util _incompatible_extension_module_restrictions13504671
Ref: 435913504671
Ref: library/importlib importlib util LazyLoader13505783
Ref: c5413505783
Ref: library/importlib importlib util LazyLoader factory13507266
Ref: 435a13507266
Ref: importlib util -- Utility code for importers-Footnote-113507829
Ref: importlib util -- Utility code for importers-Footnote-213507903
Ref: importlib util -- Utility code for importers-Footnote-313507945
Ref: importlib util -- Utility code for importers-Footnote-413507987
Ref: importlib util -- Utility code for importers-Footnote-513508029
Ref: importlib util -- Utility code for importers-Footnote-613508071
Ref: importlib util -- Utility code for importers-Footnote-713508113
Node: 範例<46>13508155
Ref: library/importlib examples13508285
Ref: 435b13508285
Ref: library/importlib importlib-examples13508285
Ref: 435c13508285
Node: Importing programmatically13508574
Ref: library/importlib importing-programmatically13508692
Ref: 435d13508692
Node: Checking if a module can be imported13508923
Ref: library/importlib checking-if-a-module-can-be-imported13509082
Ref: 435e13509082
Node: Importing a source file directly13509995
Ref: library/importlib importing-a-source-file-directly13510153
Ref: 435f13510153
Node: Implementing lazy imports13510682
Ref: library/importlib implementing-lazy-imports13510826
Ref: 436013510826
Node: Setting up an importer13511545
Ref: library/importlib setting-up-an-importer13511694
Ref: 436113511694
Node: Approximating importlib import_module13513270
Ref: library/importlib approximating-importlib-import-module13513385
Ref: 436213513385
Node: importlib resources -- Package resource reading opening and access13514885
Ref: library/importlib resources doc13515102
Ref: 436313515102
Ref: library/importlib resources importlib-resources-package-resource-reading-opening-and-access13515102
Ref: 436413515102
Ref: library/importlib resources module-importlib resources13515102
Ref: 6f13515102
Ref: library/importlib resources importlib resources Anchor13517049
Ref: 436513517049
Ref: library/importlib resources importlib resources files13517248
Ref: 43513517248
Ref: library/importlib resources importlib resources as_file13518280
Ref: 43413518280
Ref: importlib resources -- Package resource reading opening and access-Footnote-113519115
Ref: importlib resources -- Package resource reading opening and access-Footnote-213519204
Ref: importlib resources -- Package resource reading opening and access-Footnote-313519275
Ref: importlib resources -- Package resource reading opening and access-Footnote-413519369
Ref: importlib resources -- Package resource reading opening and access-Footnote-513519441
Node: Functional API13519518
Ref: library/importlib resources functional-api13519635
Ref: 436613519635
Ref: library/importlib resources importlib-resources-functional13519635
Ref: 436713519635
Ref: library/importlib resources importlib resources open_binary13520875
Ref: 1d213520875
Ref: library/importlib resources importlib resources open_text13521356
Ref: 1d313521356
Ref: library/importlib resources importlib resources read_binary13522298
Ref: 1d513522298
Ref: library/importlib resources importlib resources read_text13522706
Ref: 1d613522706
Ref: library/importlib resources importlib resources path13523572
Ref: 1d413523572
Ref: library/importlib resources importlib resources is_resource13524557
Ref: 1d113524557
Ref: library/importlib resources importlib resources contents13525022
Ref: 1d713525022
Node: importlib resources abc -- 資源的抽象基底類別13525721
Ref: library/importlib resources abc doc13525954
Ref: 436813525954
Ref: library/importlib resources abc importlib-resources-abc-abstract-base-classes-for-resources13525954
Ref: 436913525954
Ref: library/importlib resources abc module-importlib resources abc13525954
Ref: 7013525954
Ref: library/importlib resources abc importlib resources abc ResourceReader13526217
Ref: 431d13526217
Ref: library/importlib resources abc importlib resources abc ResourceReader open_resource13528043
Ref: 436a13528043
Ref: library/importlib resources abc importlib resources abc ResourceReader resource_path13528304
Ref: 436b13528304
Ref: library/importlib resources abc importlib resources abc ResourceReader is_resource13528540
Ref: 436c13528540
Ref: library/importlib resources abc importlib resources abc ResourceReader contents13528754
Ref: 436d13528754
Ref: library/importlib resources abc importlib resources abc Traversable13529623
Ref: 1d813529623
Ref: library/importlib resources abc importlib resources abc Traversable name13529910
Ref: 436e13529910
Ref: library/importlib resources abc importlib resources abc Traversable iterdir13530025
Ref: 436f13530025
Ref: library/importlib resources abc importlib resources abc Traversable is_dir13530115
Ref: 437013530115
Ref: library/importlib resources abc importlib resources abc Traversable is_file13530211
Ref: 437113530211
Ref: library/importlib resources abc importlib resources abc Traversable joinpath13530303
Ref: 437213530303
Ref: library/importlib resources abc importlib resources abc Traversable __truediv__13531415
Ref: 437313531415
Ref: library/importlib resources abc importlib resources abc Traversable open13531561
Ref: 437413531561
Ref: library/importlib resources abc importlib resources abc Traversable read_bytes13531917
Ref: 437513531917
Ref: library/importlib resources abc importlib resources abc Traversable read_text13531992
Ref: 437613531992
Ref: library/importlib resources abc importlib resources abc TraversableResources13532078
Ref: 2a713532078
Ref: library/importlib resources abc importlib resources abc TraversableResources files13532601
Ref: 437713532601
Ref: importlib resources abc -- 資源的抽象基底類別-Footnote-113532789
Node: importlib metadata -- 存取套件的元資料13532873
Ref: library/importlib metadata doc13533093
Ref: 437813533093
Ref: library/importlib metadata importlib-metadata-accessing-package-metadata13533093
Ref: 437913533093
Ref: library/importlib metadata module-importlib metadata13533093
Ref: 6e13533093
Ref: library/importlib metadata using13533093
Ref: 437a13533093
Ref: importlib metadata -- 存取套件的元資料-Footnote-113535363
Ref: importlib metadata -- 存取套件的元資料-Footnote-213535451
Ref: importlib metadata -- 存取套件的元資料-Footnote-313535535
Ref: importlib metadata -- 存取套件的元資料-Footnote-413535613
Ref: importlib metadata -- 存取套件的元資料-Footnote-513535698
Ref: importlib metadata -- 存取套件的元資料-Footnote-613535783
Ref: importlib metadata -- 存取套件的元資料-Footnote-713535821
Ref: importlib metadata -- 存取套件的元資料-Footnote-813535913
Ref: importlib metadata -- 存取套件的元資料-Footnote-913535982
Node: Overview<2>13536058
Ref: library/importlib metadata overview13536178
Ref: 437b13536178
Ref: Overview<2>-Footnote-113537717
Node: Functional API<2>13537801
Ref: library/importlib metadata functional-api13537943
Ref: 438013537943
Node: Entry points13538239
Ref: library/importlib metadata entry-points13538335
Ref: 26713538335
Ref: library/importlib metadata id213538335
Ref: 438113538335
Ref: Entry points-Footnote-113541043
Ref: Entry points-Footnote-213541115
Node: Distribution metadata13541183
Ref: library/importlib metadata distribution-metadata13541309
Ref: 438213541309
Ref: library/importlib metadata metadata13541309
Ref: 437c13541309
Ref: Distribution metadata-Footnote-113542453
Ref: Distribution metadata-Footnote-213542537
Ref: Distribution metadata-Footnote-313542579
Node: Distribution versions13542684
Ref: library/importlib metadata distribution-versions13542816
Ref: 438313542816
Ref: library/importlib metadata version13542816
Ref: 437d13542816
Ref: Distribution versions-Footnote-113543070
Node: Distribution files13543154
Ref: library/importlib metadata distribution-files13543290
Ref: 438413543290
Ref: library/importlib metadata files13543290
Ref: 437e13543290
Ref: Distribution files-Footnote-113544864
Ref: Distribution files-Footnote-213544948
Node: Distribution requirements13545045
Ref: library/importlib metadata distribution-requirements13545199
Ref: 438513545199
Ref: library/importlib metadata requirements13545199
Ref: 437f13545199
Ref: library/importlib metadata package-distributions13545476
Ref: 7b413545476
Ref: Distribution requirements-Footnote-113545513
Node: Mapping import to distribution packages13545597
Ref: library/importlib metadata import-distribution-package-mapping13545724
Ref: 438613545724
Ref: library/importlib metadata mapping-import-to-distribution-packages13545724
Ref: 438713545724
Ref: Mapping import to distribution packages-Footnote-113546351
Ref: Mapping import to distribution packages-Footnote-213546435
Ref: Mapping import to distribution packages-Footnote-313546513
Node: Distributions13546575
Ref: library/importlib metadata distributions13546728
Ref: 7b513546728
Ref: library/importlib metadata id913546728
Ref: 438813546728
Ref: Distributions-Footnote-113547909
Ref: Distributions-Footnote-213547993
Ref: Distributions-Footnote-313548035
Node: Distribution Discovery13548127
Ref: library/importlib metadata distribution-discovery13548293
Ref: 438913548293
Ref: Distribution Discovery-Footnote-113548959
Node: Extending the search algorithm13549043
Ref: library/importlib metadata extending-the-search-algorithm13549187
Ref: 438a13549187
Ref: Extending the search algorithm-Footnote-113551038
Node: Example13551122
Ref: library/importlib metadata example13551196
Ref: 438b13551196
Node: The initialization of the sys path module search path13554485
Ref: library/sys_path_init doc13554642
Ref: 438c13554642
Ref: library/sys_path_init sys-path-init13554642
Ref: 1b6413554642
Ref: library/sys_path_init the-initialization-of-the-sys-path-module-search-path13554642
Ref: 438d13554642
Node: Virtual environments13558147
Ref: library/sys_path_init virtual-environments13558276
Ref: 438f13558276
Node: _pth files13558866
Ref: library/sys_path_init pth-files13559019
Ref: 439013559019
Node: Embedded Python13560173
Ref: library/sys_path_init embedded-python13560297
Ref: 439113560297
Node: Python 語言服務13560737
Ref: library/language doc13560885
Ref: 439213560885
Ref: library/language language13560885
Ref: 439313560885
Ref: library/language python-language-services13560885
Ref: 439413560885
Node: ast --- 抽象語法樹 Abstract Syntax Trees13562046
Ref: library/ast doc13562196
Ref: 439513562196
Ref: library/ast ast-abstract-syntax-trees13562196
Ref: 439613562196
Ref: library/ast module-ast13562196
Ref: 713562196
Ref: ast --- 抽象語法樹 Abstract Syntax Trees-Footnote-113563319
Node: 抽象文法 Abstract Grammar13563382
Ref: library/ast abstract-grammar13563520
Ref: 439813563520
Ref: library/ast id113563520
Ref: 439913563520
Node: 節點 Node 類別13570938
Ref: library/ast node-classes13571101
Ref: 439a13571101
Ref: library/ast ast AST13571158
Ref: 18c13571158
Ref: library/ast ast AST _fields13571903
Ref: 439b13571903
Ref: library/ast ast AST _field_types13572626
Ref: 18d13572626
Ref: library/ast ast AST lineno13573015
Ref: 439c13573015
Ref: library/ast ast AST col_offset13573039
Ref: 439d13573039
Ref: library/ast ast AST end_lineno13573067
Ref: 439e13573067
Ref: library/ast ast AST end_col_offset13573095
Ref: 439f13573095
Ref: 節點 Node 類別-Footnote-113576660
Node: 根節點13576718
Ref: library/ast ast-root-nodes13576806
Ref: 43a113576806
Ref: library/ast root-nodes13576806
Ref: 43a213576806
Ref: library/ast ast Module13576842
Ref: 43a313576842
Ref: library/ast ast Expression13577531
Ref: 43a513577531
Ref: library/ast ast Interactive13577919
Ref: 43a713577919
Ref: library/ast ast FunctionType13578674
Ref: 43a813578674
Ref: 根節點-Footnote-113579686
Node: 文本 Literals13579728
Ref: library/ast literals13579831
Ref: 43a913579831
Ref: library/ast ast Constant13579884
Ref: 29a13579884
Ref: library/ast ast FormattedValue13580387
Ref: 43aa13580387
Ref: library/ast ast JoinedStr13581215
Ref: 15e513581215
Ref: library/ast ast List13582192
Ref: 43ab13582192
Ref: library/ast ast Tuple13582225
Ref: 43ac13582225
Ref: library/ast ast Set13583082
Ref: 43ae13583082
Ref: library/ast ast Dict13583462
Ref: 185f13583462
Node: 變數13584243
Ref: library/ast variables13584349
Ref: 43af13584349
Ref: library/ast ast Name13584380
Ref: 184113584380
Ref: library/ast ast Load13584520
Ref: 18a13584520
Ref: library/ast ast Store13584541
Ref: 43ad13584541
Ref: library/ast ast Del13584563
Ref: 43b013584563
Ref: library/ast ast Starred13585383
Ref: 43b113585383
Node: 運算式<2>13586185
Ref: library/ast ast-expressions13586285
Ref: 43a613586285
Ref: library/ast expressions13586285
Ref: 43b313586285
Ref: library/ast ast Expr13586321
Ref: 43b413586321
Ref: library/ast ast UnaryOp13586944
Ref: 43a013586944
Ref: library/ast ast UAdd13587094
Ref: 43b813587094
Ref: library/ast ast USub13587115
Ref: 43b913587115
Ref: library/ast ast Not13587136
Ref: 43ba13587136
Ref: library/ast ast Invert13587156
Ref: 43bb13587156
Ref: library/ast ast BinOp13587509
Ref: 18d213587509
Ref: library/ast ast Add13587949
Ref: 43bc13587949
Ref: library/ast ast Sub13587969
Ref: 43bd13587969
Ref: library/ast ast Mult13587989
Ref: 43be13587989
Ref: library/ast ast Div13588010
Ref: 43bf13588010
Ref: library/ast ast FloorDiv13588030
Ref: 43c013588030
Ref: library/ast ast Mod13588055
Ref: 43c113588055
Ref: library/ast ast Pow13588075
Ref: 43c213588075
Ref: library/ast ast LShift13588095
Ref: 43c313588095
Ref: library/ast ast RShift13588118
Ref: 43c413588118
Ref: library/ast ast BitOr13588141
Ref: 43c513588141
Ref: library/ast ast BitXor13588163
Ref: 43c613588163
Ref: library/ast ast BitAnd13588186
Ref: 43c713588186
Ref: library/ast ast MatMult13588209
Ref: 43c813588209
Ref: library/ast ast BoolOp13588265
Ref: 43c913588265
Ref: library/ast ast And13588896
Ref: 43cb13588896
Ref: library/ast ast Or13588916
Ref: 43ca13588916
Ref: library/ast ast Compare13588967
Ref: 43cc13588967
Ref: library/ast ast Eq13589579
Ref: 43cd13589579
Ref: library/ast ast NotEq13589598
Ref: 43ce13589598
Ref: library/ast ast Lt13589620
Ref: 43cf13589620
Ref: library/ast ast LtE13589639
Ref: 43d013589639
Ref: library/ast ast Gt13589659
Ref: 43d113589659
Ref: library/ast ast GtE13589678
Ref: 43d213589678
Ref: library/ast ast Is13589698
Ref: 43d313589698
Ref: library/ast ast IsNot13589717
Ref: 43d413589717
Ref: library/ast ast In13589739
Ref: 43d513589739
Ref: library/ast ast NotIn13589758
Ref: 43d613589758
Ref: library/ast ast Call13589812
Ref: 43b213589812
Ref: library/ast ast keyword13590925
Ref: 43d813590925
Ref: library/ast ast IfExp13591102
Ref: 43d913591102
Ref: library/ast ast Attribute13591596
Ref: 43d713591596
Ref: library/ast ast NamedExpr13592169
Ref: 43da13592169
Node: 下標 Subscripting13592881
Ref: library/ast subscripting13592988
Ref: 43dc13592988
Ref: library/ast ast Subscript13593049
Ref: 43dd13593049
Ref: library/ast ast Slice13593942
Ref: 43de13593942
Node: 綜合運算式 comprehensions13594529
Ref: library/ast comprehensions13594636
Ref: 43df13594636
Ref: library/ast ast ListComp13594716
Ref: 43e013594716
Ref: library/ast ast SetComp13594759
Ref: 43e113594759
Ref: library/ast ast GeneratorExp13594801
Ref: 43e213594801
Ref: library/ast ast DictComp13594848
Ref: 43e313594848
Ref: library/ast ast comprehension13596764
Ref: 43e413596764
Node: 陳述式13599777
Ref: library/ast ast-statements13599883
Ref: 43a413599883
Ref: library/ast statements13599883
Ref: 43e513599883
Ref: library/ast ast Assign13599919
Ref: 43db13599919
Ref: library/ast ast Assign type_comment13600255
Ref: 43e613600255
Ref: library/ast ast AnnAssign13601180
Ref: 43e713601180
Ref: library/ast ast AugAssign13603398
Ref: 43e813603398
Ref: library/ast ast Raise13604138
Ref: 43e913604138
Ref: library/ast ast Assert13604670
Ref: 43ea13604670
Ref: library/ast ast Delete13605078
Ref: 43eb13605078
Ref: library/ast ast Pass13605595
Ref: 43ec13605595
Ref: library/ast ast TypeAlias13605780
Ref: 15dc13605780
Node: 引入 imports13606491
Ref: library/ast imports13606551
Ref: 43ee13606551
Ref: library/ast ast Import13606604
Ref: 43ef13606604
Ref: library/ast ast ImportFrom13607017
Ref: 43f013607017
Ref: library/ast ast alias13607736
Ref: 17c113607736
Node: 流程控制13608255
Ref: library/ast control-flow13608378
Ref: 43f113608378
Ref: library/ast ast If13608523
Ref: 43f213608523
Ref: library/ast ast For13609759
Ref: 43f313609759
Ref: library/ast ast For type_comment13610289
Ref: 43f413610289
Ref: library/ast ast While13610998
Ref: 43f513610998
Ref: library/ast ast Break13611676
Ref: 43f613611676
Ref: library/ast ast Continue13611698
Ref: 43f713611698
Ref: library/ast ast Try13612703
Ref: 43f813612703
Ref: library/ast ast TryStar13614278
Ref: 43fa13614278
Ref: library/ast ast ExceptHandler13615272
Ref: 43f913615272
Ref: library/ast ast With13616421
Ref: 43fb13616421
Ref: library/ast ast With type_comment13616628
Ref: 43fd13616628
Ref: library/ast ast withitem13616747
Ref: 43fc13616747
Node: 模式匹配 pattern matching13618052
Ref: library/ast pattern-matching13618194
Ref: 43fe13618194
Ref: library/ast ast Match13618275
Ref: 43ff13618275
Ref: library/ast ast match_case13618553
Ref: 440013618553
Ref: library/ast ast MatchValue13620504
Ref: 440113620504
Ref: library/ast ast MatchSingleton13621423
Ref: 440213621423
Ref: library/ast ast MatchSequence13622289
Ref: 440313622289
Ref: library/ast ast MatchStar13623429
Ref: 440413623429
Ref: library/ast ast MatchMapping13624997
Ref: 440513624997
Ref: library/ast ast MatchClass13626839
Ref: 440613626839
Ref: library/ast ast MatchAs13629652
Ref: 440713629652
Ref: library/ast ast MatchOr13631259
Ref: 440813631259
Node: 型別參數 type parameters13632484
Ref: library/ast ast-type-params13632635
Ref: 43ed13632635
Ref: library/ast type-parameters13632635
Ref: 440913632635
Ref: library/ast ast TypeVar13632791
Ref: 440a13632791
Ref: library/ast ast ParamSpec13633965
Ref: 440b13633965
Ref: library/ast ast TypeVarTuple13635331
Ref: 440c13635331
Node: 函式和類別定義13636528
Ref: library/ast function-and-class-definitions13636665
Ref: 440d13636665
Ref: library/ast ast FunctionDef13636723
Ref: 160413636723
Ref: library/ast ast FunctionDef type_comment13637328
Ref: 440f13637328
Ref: library/ast ast Lambda13637507
Ref: 43b513637507
Ref: library/ast ast arguments13638100
Ref: 440e13638100
Ref: library/ast ast arg13638785
Ref: 441013638785
Ref: library/ast ast arg type_comment13638990
Ref: 441113638990
Ref: library/ast ast Return13640534
Ref: 441213640534
Ref: library/ast ast Yield13640783
Ref: 43b613640783
Ref: library/ast ast YieldFrom13640813
Ref: 43b713640813
Ref: library/ast ast Global13641493
Ref: 441313641493
Ref: library/ast ast Nonlocal13641524
Ref: 441413641524
Ref: library/ast ast ClassDef13642170
Ref: 160213642170
Ref: 函式和類別定義-Footnote-113643831
Node: async 和 await13643873
Ref: library/ast async-and-await13643973
Ref: 441513643973
Ref: library/ast ast AsyncFunctionDef13644025
Ref: 160313644025
Ref: library/ast ast Await13644304
Ref: 441613644304
Ref: library/ast ast AsyncFor13644930
Ref: 441713644930
Ref: library/ast ast AsyncWith13644998
Ref: 441813644998
Node: ast 輔助程式13645609
Ref: library/ast ast-helpers13645761
Ref: 441913645761
Ref: library/ast ast parse13645954
Ref: 18e13645954
Ref: library/ast ast unparse13648928
Ref: 88a13648928
Ref: library/ast ast literal_eval13649497
Ref: bbf13649497
Ref: library/ast ast get_docstring13651165
Ref: 196013651165
Ref: library/ast ast get_source_segment13651642
Ref: 97b13651642
Ref: library/ast ast fix_missing_locations13652104
Ref: 441b13652104
Ref: library/ast ast increment_lineno13652571
Ref: 169913652571
Ref: library/ast ast copy_location13652777
Ref: 441c13652777
Ref: library/ast ast iter_fields13653049
Ref: 441d13653049
Ref: library/ast ast iter_child_nodes13653205
Ref: 441e13653205
Ref: library/ast ast walk13653378
Ref: 441f13653378
Ref: library/ast ast NodeVisitor13653601
Ref: a1013653601
Ref: library/ast ast NodeVisitor visit13653900
Ref: 442013653900
Ref: library/ast ast NodeVisitor generic_visit13654163
Ref: 442113654163
Ref: library/ast ast NodeVisitor visit_Constant13654468
Ref: a1113654468
Ref: library/ast ast NodeTransformer13655071
Ref: 442213655071
Ref: library/ast ast dump13656806
Ref: 88913656806
Ref: ast 輔助程式-Footnote-113659043
Ref: ast 輔助程式-Footnote-213659085
Ref: ast 輔助程式-Footnote-313659127
Node: 編譯器旗標<2>13659169
Ref: library/ast ast-compiler-flags13659321
Ref: 203c13659321
Ref: library/ast compiler-flags13659321
Ref: 442313659321
Ref: library/ast ast PyCF_ALLOW_TOP_LEVEL_AWAIT13659460
Ref: 442413659460
Ref: library/ast ast PyCF_ONLY_AST13659649
Ref: 439713659649
Ref: library/ast ast PyCF_OPTIMIZED_AST13659765
Ref: 442513659765
Ref: library/ast ast PyCF_TYPE_COMMENTS13659960
Ref: 441a13659960
Ref: 編譯器旗標<2>-Footnote-113660191
Ref: 編譯器旗標<2>-Footnote-213660233
Node: 命令列用法<3>13660275
Ref: library/ast ast-cli13660402
Ref: 442613660402
Ref: library/ast command-line-usage13660402
Ref: 442713660402
Ref: library/ast cmdoption-ast-h13660642
Ref: 442813660642
Ref: library/ast cmdoption-ast-help13660642
Ref: 442913660642
Ref: library/ast cmdoption-ast-m13660703
Ref: 442a13660703
Ref: library/ast cmdoption-ast-mode13660725
Ref: 442b13660725
Ref: library/ast cmdoption-ast-no-type-comments13660859
Ref: 442c13660859
Ref: library/ast cmdoption-ast-a13660925
Ref: 442d13660925
Ref: library/ast cmdoption-ast-include-attributes13660925
Ref: 442e13660925
Ref: library/ast cmdoption-ast-i13661009
Ref: 442f13661009
Ref: library/ast cmdoption-ast-indent13661033
Ref: 443013661033
Ref: 命令列用法<3>-Footnote-113662063
Ref: 命令列用法<3>-Footnote-213662111
Ref: 命令列用法<3>-Footnote-313662178
Ref: 命令列用法<3>-Footnote-413662252
Ref: 命令列用法<3>-Footnote-513662291
Node: symtable --- 存取編譯器的符號表13662328
Ref: library/symtable doc13662538
Ref: 443113662538
Ref: library/symtable module-symtable13662538
Ref: c213662538
Ref: library/symtable symtable-access-to-the-compiler-s-symbol-tables13662538
Ref: 443213662538
Ref: symtable --- 存取編譯器的符號表-Footnote-113663103
Node: 產生符號表13663171
Ref: library/symtable generating-symbol-tables13663287
Ref: 443313663287
Ref: library/symtable symtable symtable13663333
Ref: 18f213663333
Node: 檢查符號表13663594
Ref: library/symtable examining-symbol-tables13663740
Ref: 443513663740
Ref: library/symtable symtable SymbolTableType13663786
Ref: 150013663786
Ref: library/symtable symtable SymbolTableType MODULE13663908
Ref: 443613663908
Ref: library/symtable symtable SymbolTableType FUNCTION13663994
Ref: 443713663994
Ref: library/symtable symtable SymbolTableType CLASS13664086
Ref: 443813664086
Ref: library/symtable symtable SymbolTableType ANNOTATION13664262
Ref: 443913664262
Ref: library/symtable symtable SymbolTableType TYPE_ALIAS13664403
Ref: 443a13664403
Ref: library/symtable symtable SymbolTableType TYPE_PARAMETERS13664519
Ref: 443b13664519
Ref: library/symtable symtable SymbolTableType TYPE_VARIABLE13664684
Ref: 443c13664684
Ref: library/symtable symtable SymbolTable13665050
Ref: 443413665050
Ref: library/symtable symtable SymbolTable get_type13665199
Ref: 150113665199
Ref: library/symtable symtable SymbolTable get_id13665858
Ref: 443d13665858
Ref: library/symtable symtable SymbolTable get_name13665922
Ref: 443e13665922
Ref: library/symtable symtable SymbolTable get_lineno13666510
Ref: 443f13666510
Ref: library/symtable symtable SymbolTable is_optimized13666608
Ref: 444013666608
Ref: library/symtable symtable SymbolTable is_nested13666725
Ref: 444113666725
Ref: library/symtable symtable SymbolTable has_children13666830
Ref: 444213666830
Ref: library/symtable symtable SymbolTable get_identifiers13667004
Ref: 444413667004
Ref: library/symtable symtable SymbolTable lookup13667174
Ref: 444513667174
Ref: library/symtable symtable SymbolTable get_symbols13667286
Ref: 444613667286
Ref: library/symtable symtable SymbolTable get_children13667388
Ref: 444313667388
Ref: library/symtable symtable Function13667467
Ref: 444713667467
Ref: library/symtable symtable Function get_parameters13667590
Ref: 444813667590
Ref: library/symtable symtable Function get_locals13667697
Ref: 444913667697
Ref: library/symtable symtable Function get_globals13667811
Ref: 444a13667811
Ref: library/symtable symtable Function get_nonlocals13667927
Ref: 444b13667927
Ref: library/symtable symtable Function get_frees13668050
Ref: 444c13668050
Ref: library/symtable symtable Class13668171
Ref: 444d13668171
Ref: library/symtable symtable Class get_methods13668282
Ref: 2c013668282
Ref: library/symtable symtable Symbol13669499
Ref: 15c913669499
Ref: library/symtable symtable Symbol get_name13669641
Ref: 444e13669641
Ref: library/symtable symtable Symbol is_referenced13669707
Ref: 444f13669707
Ref: library/symtable symtable Symbol is_imported13669816
Ref: 445013669816
Ref: library/symtable symtable Symbol is_parameter13669931
Ref: 445113669931
Ref: library/symtable symtable Symbol is_global13670030
Ref: 445213670030
Ref: library/symtable symtable Symbol is_nonlocal13670123
Ref: 193113670123
Ref: library/symtable symtable Symbol is_declared_global13670221
Ref: 12b913670221
Ref: library/symtable symtable Symbol is_local13670353
Ref: 445313670353
Ref: library/symtable symtable Symbol is_annotated13670460
Ref: 445413670460
Ref: library/symtable symtable Symbol is_free13670589
Ref: 445513670589
Ref: library/symtable symtable Symbol is_assigned13670746
Ref: 445613670746
Ref: library/symtable symtable Symbol is_namespace13670856
Ref: 445713670856
Ref: library/symtable symtable Symbol get_namespaces13671491
Ref: 445813671491
Ref: library/symtable symtable Symbol get_namespace13671590
Ref: 445913671590
Node: Command-Line Usage<2>13671794
Ref: library/symtable command-line-usage13671916
Ref: 445a13671916
Ref: library/symtable symtable-cli13671916
Ref: 445b13671916
Node: token --- 與 Python 剖析樹一起使用的常數13672270
Ref: library/token doc13672470
Ref: 445c13672470
Ref: library/token module-token13672470
Ref: e313672470
Ref: library/token token-constants-used-with-python-parse-trees13672470
Ref: 445d13672470
Ref: library/token token tok_name13673177
Ref: 445e13673177
Ref: library/token token ISTERMINAL13673397
Ref: 445f13673397
Ref: library/token token ISNONTERMINAL13673482
Ref: 446013673482
Ref: library/token token ISEOF13673574
Ref: 446113673574
Ref: library/token token ENDMARKER13673703
Ref: 446213673703
Ref: library/token token NAME13673732
Ref: 446313673732
Ref: library/token token NUMBER13673756
Ref: 446413673756
Ref: library/token token STRING13673782
Ref: 446513673782
Ref: library/token token NEWLINE13673808
Ref: 446613673808
Ref: library/token token INDENT13673835
Ref: 446713673835
Ref: library/token token DEDENT13673861
Ref: 446813673861
Ref: library/token token LPAR13673887
Ref: 446913673887
Ref: library/token token RPAR13673944
Ref: 446a13673944
Ref: library/token token LSQB13674001
Ref: 446b13674001
Ref: library/token token RSQB13674058
Ref: 446c13674058
Ref: library/token token COLON13674115
Ref: 446d13674115
Ref: library/token token COMMA13674173
Ref: 446e13674173
Ref: library/token token SEMI13674231
Ref: 446f13674231
Ref: library/token token PLUS13674288
Ref: 447013674288
Ref: library/token token MINUS13674345
Ref: 447113674345
Ref: library/token token STAR13674403
Ref: 447213674403
Ref: library/token token SLASH13674460
Ref: 447313674460
Ref: library/token token VBAR13674518
Ref: 447413674518
Ref: library/token token AMPER13674575
Ref: 447513674575
Ref: library/token token LESS13674633
Ref: 447613674633
Ref: library/token token GREATER13674690
Ref: 447713674690
Ref: library/token token EQUAL13674750
Ref: 447813674750
Ref: library/token token DOT13674808
Ref: 447913674808
Ref: library/token token PERCENT13674864
Ref: 447a13674864
Ref: library/token token LBRACE13674924
Ref: 447b13674924
Ref: library/token token RBRACE13674983
Ref: 447c13674983
Ref: library/token token EQEQUAL13675042
Ref: 447d13675042
Ref: library/token token NOTEQUAL13675103
Ref: 447e13675103
Ref: library/token token LESSEQUAL13675165
Ref: 447f13675165
Ref: library/token token GREATEREQUAL13675228
Ref: 448013675228
Ref: library/token token TILDE13675294
Ref: 448113675294
Ref: library/token token CIRCUMFLEX13675352
Ref: 448213675352
Ref: library/token token LEFTSHIFT13675415
Ref: 448313675415
Ref: library/token token RIGHTSHIFT13675478
Ref: 448413675478
Ref: library/token token DOUBLESTAR13675542
Ref: 448513675542
Ref: library/token token PLUSEQUAL13675606
Ref: 448613675606
Ref: library/token token MINEQUAL13675669
Ref: 448713675669
Ref: library/token token STAREQUAL13675731
Ref: 448813675731
Ref: library/token token SLASHEQUAL13675794
Ref: 448913675794
Ref: library/token token PERCENTEQUAL13675858
Ref: 448a13675858
Ref: library/token token AMPEREQUAL13675924
Ref: 448b13675924
Ref: library/token token VBAREQUAL13675988
Ref: 448c13675988
Ref: library/token token CIRCUMFLEXEQUAL13676051
Ref: 448d13676051
Ref: library/token token LEFTSHIFTEQUAL13676120
Ref: 448e13676120
Ref: library/token token RIGHTSHIFTEQUAL13676189
Ref: 448f13676189
Ref: library/token token DOUBLESTAREQUAL13676259
Ref: 449013676259
Ref: library/token token DOUBLESLASH13676329
Ref: 449113676329
Ref: library/token token DOUBLESLASHEQUAL13676394
Ref: 449213676394
Ref: library/token token AT13676465
Ref: 449313676465
Ref: library/token token ATEQUAL13676520
Ref: 449413676520
Ref: library/token token RARROW13676581
Ref: 449513676581
Ref: library/token token ELLIPSIS13676641
Ref: 449613676641
Ref: library/token token COLONEQUAL13676704
Ref: 449713676704
Ref: library/token token EXCLAMATION13676768
Ref: 449813676768
Ref: library/token token OP13676832
Ref: 449913676832
Ref: library/token token TYPE_IGNORE13676854
Ref: 449a13676854
Ref: library/token token TYPE_COMMENT13676885
Ref: 449b13676885
Ref: library/token token SOFT_KEYWORD13676917
Ref: 449c13676917
Ref: library/token token FSTRING_START13676949
Ref: 449d13676949
Ref: library/token token FSTRING_MIDDLE13676982
Ref: 449e13676982
Ref: library/token token FSTRING_END13677016
Ref: 449f13677016
Ref: library/token token COMMENT13677047
Ref: 44a013677047
Ref: library/token token NL13677074
Ref: 44a113677074
Ref: library/token token ERRORTOKEN13677096
Ref: 44a213677096
Ref: library/token token N_TOKENS13677126
Ref: 44a313677126
Ref: library/token token NT_OFFSET13677154
Ref: 44a413677154
Ref: library/token token ENCODING13677655
Ref: 44a513677655
Ref: token --- 與 Python 剖析樹一起使用的常數-Footnote-113678785
Node: keyword --- 檢驗 Python 關鍵字13678850
Ref: library/keyword doc13679050
Ref: 44a613679050
Ref: library/keyword keyword-testing-for-python-keywords13679050
Ref: 44a713679050
Ref: library/keyword module-keyword13679050
Ref: 7813679050
Ref: library/keyword keyword iskeyword13679365
Ref: 209e13679365
Ref: library/keyword keyword kwlist13679480
Ref: 44a813679480
Ref: library/keyword keyword issoftkeyword13679720
Ref: 44a913679720
Ref: library/keyword keyword softkwlist13679870
Ref: 44aa13679870
Ref: keyword --- 檢驗 Python 關鍵字-Footnote-113680183
Node: tokenize --- Tokenizer for Python source13680250
Ref: library/tokenize doc13680430
Ref: 44ab13680430
Ref: library/tokenize module-tokenize13680430
Ref: e413680430
Ref: library/tokenize tokenize-tokenizer-for-python-source13680430
Ref: 44ac13680430
Ref: tokenize --- Tokenizer for Python source-Footnote-113681701
Node: Tokenizing Input13681769
Ref: library/tokenize tokenizing-input13681892
Ref: 44ad13681892
Ref: library/tokenize tokenize tokenize13681999
Ref: 48113681999
Ref: library/tokenize tokenize generate_tokens13683442
Ref: 48213683442
Ref: library/tokenize tokenize untokenize13684204
Ref: 154c13684204
Ref: library/tokenize tokenize detect_encoding13685146
Ref: 274413685146
Ref: library/tokenize tokenize open13686140
Ref: 274313686140
Ref: library/tokenize tokenize TokenError13686309
Ref: 4e813686309
Ref: Tokenizing Input-Footnote-113686628
Ref: Tokenizing Input-Footnote-213686670
Node: Command-Line Usage<3>13686712
Ref: library/tokenize command-line-usage13686854
Ref: 44ae13686854
Ref: library/tokenize tokenize-cli13686854
Ref: 44af13686854
Ref: library/tokenize cmdoption-tokenize-h13687119
Ref: 44b013687119
Ref: library/tokenize cmdoption-tokenize-help13687119
Ref: 44b113687119
Ref: library/tokenize cmdoption-tokenize-e13687181
Ref: 44b213687181
Ref: library/tokenize cmdoption-tokenize-exact13687181
Ref: 44b313687181
Node: 範例<47>13687373
Ref: library/tokenize examples13687490
Ref: 44b413687490
Node: tabnanny --- 偵測不良縮排13691977
Ref: library/tabnanny doc13692161
Ref: 44b513692161
Ref: library/tabnanny module-tabnanny13692161
Ref: c713692161
Ref: library/tabnanny tabnanny-detection-of-ambiguous-indentation13692161
Ref: 44b613692161
Ref: library/tabnanny tabnanny check13692641
Ref: 44b713692641
Ref: library/tabnanny tabnanny verbose13693087
Ref: 44b813693087
Ref: library/tabnanny tabnanny filename_only13693267
Ref: 44b913693267
Ref: library/tabnanny tabnanny NannyNag13693473
Ref: 44ba13693473
Ref: library/tabnanny tabnanny process_tokens13693651
Ref: 44bb13693651
Ref: tabnanny --- 偵測不良縮排-Footnote-113693956
Node: pyclbr --- Python 模組瀏覽器支援13694024
Ref: library/pyclbr doc13694209
Ref: 44bc13694209
Ref: library/pyclbr module-pyclbr13694209
Ref: a213694209
Ref: library/pyclbr pyclbr-python-module-browser-support13694209
Ref: 44bd13694209
Ref: library/pyclbr pyclbr readmodule13694897
Ref: 7cf13694897
Ref: library/pyclbr pyclbr readmodule_ex13695506
Ref: 7d013695506
Ref: pyclbr --- Python 模組瀏覽器支援-Footnote-113696561
Node: 函式物件13696627
Ref: library/pyclbr function-objects13696737
Ref: 44be13696737
Ref: library/pyclbr pyclbr-function-objects13696737
Ref: 44bf13696737
Ref: library/pyclbr pyclbr Function13696778
Ref: 44c013696778
Ref: library/pyclbr pyclbr Function file13696932
Ref: 44c113696932
Ref: library/pyclbr pyclbr Function module13697017
Ref: 44c213697017
Ref: library/pyclbr pyclbr Function name13697109
Ref: 44c313697109
Ref: library/pyclbr pyclbr Function lineno13697169
Ref: 44c413697169
Ref: library/pyclbr pyclbr Function parent13697262
Ref: 44c513697262
Ref: library/pyclbr pyclbr Function children13697413
Ref: 44c613697413
Ref: library/pyclbr pyclbr Function is_async13697582
Ref: 44c713697582
Node: Class Objects13697764
Ref: library/pyclbr class-objects13697874
Ref: 44c813697874
Ref: library/pyclbr pyclbr-class-objects13697874
Ref: 44c913697874
Ref: library/pyclbr pyclbr Class13697921
Ref: 44ca13697921
Ref: library/pyclbr pyclbr Class file13698108
Ref: 44cb13698108
Ref: library/pyclbr pyclbr Class module13698190
Ref: 44cc13698190
Ref: library/pyclbr pyclbr Class name13698279
Ref: 44cd13698279
Ref: library/pyclbr pyclbr Class lineno13698336
Ref: 44ce13698336
Ref: library/pyclbr pyclbr Class parent13698429
Ref: 44cf13698429
Ref: library/pyclbr pyclbr Class children13698576
Ref: 44d013698576
Ref: library/pyclbr pyclbr Class super13698733
Ref: 44d113698733
Ref: library/pyclbr pyclbr Class methods13699091
Ref: 44d213699091
Node: py_compile — 編譯 Python 來源檔案13699316
Ref: library/py_compile doc13699517
Ref: 44d313699517
Ref: library/py_compile module-py_compile13699517
Ref: a113699517
Ref: library/py_compile py-compile-compile-python-source-files13699517
Ref: 44d413699517
Ref: library/py_compile py_compile PyCompileError13700131
Ref: 44d513700131
Ref: library/py_compile py_compile compile13700257
Ref: 9c913700257
Ref: library/py_compile py_compile PycInvalidationMode13703986
Ref: 44d613703986
Ref: library/py_compile py_compile PycInvalidationMode TIMESTAMP13704411
Ref: 44d813704411
Ref: library/py_compile py_compile PycInvalidationMode CHECKED_HASH13704690
Ref: 44d713704690
Ref: library/py_compile py_compile PycInvalidationMode UNCHECKED_HASH13704933
Ref: 44d913704933
Ref: py_compile — 編譯 Python 來源檔案-Footnote-113705478
Ref: py_compile — 編譯 Python 來源檔案-Footnote-213705548
Ref: py_compile — 編譯 Python 來源檔案-Footnote-313705590
Ref: py_compile — 編譯 Python 來源檔案-Footnote-413705632
Ref: py_compile — 編譯 Python 來源檔案-Footnote-513705674
Node: Command-Line Interface<3>13705716
Ref: library/py_compile command-line-interface13705819
Ref: 44da13705819
Ref: library/py_compile py-compile-cli13705819
Ref: 44db13705819
Ref: library/py_compile cmdoption-python-m-py_compile-arg-file13706248
Ref: 44dc13706248
Ref: library/py_compile cmdoption-python-m-py_compile13706279
Ref: 44dd13706279
Ref: library/py_compile cmdoption-python-m-py_compile-q13706431
Ref: 44de13706431
Ref: library/py_compile cmdoption-python-m-py_compile-quiet13706431
Ref: 44df13706431
Node: compileall --- 位元組編譯 Python 函式庫13706723
Ref: library/compileall doc13706924
Ref: 44e013706924
Ref: library/compileall compileall-byte-compile-python-libraries13706924
Ref: 44e113706924
Ref: library/compileall module-compileall13706924
Ref: 1913706924
Ref: compileall --- 位元組編譯 Python 函式庫-Footnote-113707737
Node: Command-line use13707807
Ref: library/compileall command-line-use13707932
Ref: 44e213707932
Ref: library/compileall compileall-cli13707932
Ref: 44e313707932
Ref: library/compileall cmdoption-compileall-arg-directory13708081
Ref: 44e413708081
Ref: library/compileall cmdoption-compileall-arg-file13708107
Ref: 44e513708107
Ref: library/compileall cmdoption-compileall-l13708355
Ref: 44e613708355
Ref: library/compileall cmdoption-compileall-f13708505
Ref: 44e713708505
Ref: library/compileall cmdoption-compileall-q13708576
Ref: 44e813708576
Ref: library/compileall cmdoption-compileall-d13708760
Ref: 44e913708760
Ref: library/compileall cmdoption-compileall-s13709113
Ref: 44ea13709113
Ref: library/compileall cmdoption-compileall-p13709142
Ref: 44eb13709142
Ref: library/compileall cmdoption-compileall-x13709318
Ref: 44ec13709318
Ref: library/compileall cmdoption-compileall-i13709491
Ref: 44ed13709491
Ref: library/compileall cmdoption-compileall-b13709693
Ref: 44ee13709693
Ref: library/compileall cmdoption-compileall-r13710019
Ref: 44ef13710019
Ref: library/compileall cmdoption-compileall-j13710289
Ref: 44f013710289
Ref: library/compileall cmdoption-compileall-invalidation-mode13710476
Ref: 44f113710476
Ref: library/compileall cmdoption-compileall-o13711275
Ref: 44f213711275
Ref: library/compileall cmdoption-compileall-e13711468
Ref: 44f313711468
Ref: library/compileall cmdoption-compileall-hardlink-dupes13711548
Ref: 44f413711548
Ref: Command-line use-Footnote-113712831
Node: Public functions13712873
Ref: library/compileall public-functions13712998
Ref: 44f513712998
Ref: library/compileall compileall compile_dir13713051
Ref: aca13713051
Ref: library/compileall compileall compile_file13717138
Ref: d8713717138
Ref: library/compileall compileall compile_path13720100
Ref: d8813720100
Ref: Public functions-Footnote-113721788
Ref: Public functions-Footnote-213721830
Node: dis --- Python bytecode 的反組譯器13721872
Ref: library/dis doc13722073
Ref: 44f613722073
Ref: library/dis dis-disassembler-for-python-bytecode13722073
Ref: 44f713722073
Ref: library/dis module-dis13722073
Ref: 3013722073
Ref: dis --- Python bytecode 的反組譯器-Footnote-113724681
Node: Command-line interface13724744
Ref: library/dis command-line-interface13724868
Ref: 44f813724868
Ref: library/dis dis-cli13724868
Ref: 44f913724868
Ref: library/dis cmdoption-dis-h13725093
Ref: 44fa13725093
Ref: library/dis cmdoption-dis-help13725093
Ref: 44fb13725093
Ref: library/dis cmdoption-dis-C13725153
Ref: 44fc13725153
Ref: library/dis cmdoption-dis-show-caches13725153
Ref: 44fd13725153
Ref: library/dis cmdoption-dis-O13725216
Ref: 1bb13725216
Ref: library/dis cmdoption-dis-show-offsets13725216
Ref: 44fe13725216
Node: Bytecode analysis13725452
Ref: library/dis bytecode-analysis13725603
Ref: 44ff13725603
Ref: library/dis dis Bytecode13725845
Ref: ed213725845
Ref: library/dis dis Bytecode from_traceback13727333
Ref: ed413727333
Ref: library/dis dis Bytecode codeobj13727579
Ref: 450013727579
Ref: library/dis dis Bytecode first_line13727642
Ref: 450113727642
Ref: library/dis dis Bytecode dis13727738
Ref: ed313727738
Ref: library/dis dis Bytecode info13727929
Ref: 450213727929
Node: Analysis functions13728465
Ref: library/dis analysis-functions13728622
Ref: 450313728622
Ref: library/dis dis code_info13728926
Ref: 11d113728926
Ref: library/dis dis show_code13729463
Ref: ed013729463
Ref: library/dis dis dis13729925
Ref: ad813729925
Ref: library/dis dis disassemble13732388
Ref: ed113732388
Ref: library/dis dis get_instructions13733589
Ref: 1bc13733589
Ref: library/dis dis findlinestarts13734707
Ref: 450413734707
Ref: library/dis dis findlabels13735406
Ref: 450513735406
Ref: library/dis dis stack_effect13735574
Ref: ed513735574
Ref: Analysis functions-Footnote-113736488
Node: Python Bytecode Instructions13736530
Ref: library/dis bytecodes13736688
Ref: 55613736688
Ref: library/dis python-bytecode-instructions13736688
Ref: 450613736688
Ref: library/dis dis Instruction13736922
Ref: 1bd13736922
Ref: library/dis dis Instruction opcode13736990
Ref: 450713736990
Ref: library/dis dis Instruction opname13737185
Ref: 450913737185
Ref: library/dis dis Instruction baseopcode13737255
Ref: 450a13737255
Ref: library/dis dis Instruction baseopname13737409
Ref: 450b13737409
Ref: library/dis dis Instruction arg13737570
Ref: 450d13737570
Ref: library/dis dis Instruction oparg13737664
Ref: 450e13737664
Ref: library/dis dis Instruction argval13737726
Ref: 450f13737726
Ref: library/dis dis Instruction argrepr13737812
Ref: 451013737812
Ref: library/dis dis Instruction offset13737945
Ref: 451113737945
Ref: library/dis dis Instruction start_offset13738031
Ref: 451213738031
Ref: library/dis dis Instruction cache_offset13738244
Ref: 451313738244
Ref: library/dis dis Instruction end_offset13738343
Ref: 451413738343
Ref: library/dis dis Instruction starts_line13738438
Ref: 451513738438
Ref: library/dis dis Instruction line_number13738549
Ref: 451613738549
Ref: library/dis dis Instruction is_jump_target13738678
Ref: 451713738678
Ref: library/dis dis Instruction jump_target13738784
Ref: 451813738784
Ref: library/dis dis Instruction positions13738919
Ref: 451913738919
Ref: library/dis dis Positions13739422
Ref: 42a513739422
Ref: library/dis dis Positions lineno13739535
Ref: 451a13739535
Ref: library/dis dis Positions end_lineno13739560
Ref: 451b13739560
Ref: library/dis dis Positions col_offset13739589
Ref: 451c13739589
Ref: library/dis dis Positions end_col_offset13739618
Ref: 451d13739618
Ref: library/dis opcode-NOP13739984
Ref: 451e13739984
Ref: library/dis opcode-POP_TOP13740116
Ref: 451f13740116
Ref: library/dis opcode-END_FOR13740197
Ref: 452013740197
Ref: library/dis opcode-END_SEND13740374
Ref: 452113740374
Ref: library/dis opcode-COPY13740510
Ref: 6ad13740510
Ref: library/dis opcode-SWAP13740721
Ref: 6ae13740721
Ref: library/dis opcode-CACHE13740882
Ref: 69c13740882
Ref: library/dis opcode-UNARY_NEGATIVE13741717
Ref: 452213741717
Ref: library/dis opcode-UNARY_NOT13741792
Ref: 15ea13741792
Ref: library/dis opcode-UNARY_INVERT13741964
Ref: 452313741964
Ref: library/dis opcode-GET_ITER13742037
Ref: 452413742037
Ref: library/dis opcode-GET_YIELD_FROM_ITER13742111
Ref: 452513742111
Ref: library/dis opcode-TO_BOOL13742351
Ref: 15e713742351
Ref: library/dis opcode-BINARY_OP13742868
Ref: 6aa13742868
Ref: library/dis opcode-BINARY_SUBSCR13743107
Ref: 163f13743107
Ref: library/dis opcode-STORE_SUBSCR13743254
Ref: 172013743254
Ref: library/dis opcode-DELETE_SUBSCR13743424
Ref: 452613743424
Ref: library/dis opcode-BINARY_SLICE13743561
Ref: 48713743561
Ref: library/dis opcode-STORE_SLICE13743772
Ref: 48813743772
Ref: library/dis opcode-GET_AWAITABLE13744028
Ref: 173b13744028
Ref: library/dis opcode-GET_AITER13744652
Ref: 452713744652
Ref: library/dis opcode-GET_ANEXT13744867
Ref: 452813744867
Ref: library/dis opcode-END_ASYNC_FOR13745074
Ref: a4d13745074
Ref: library/dis opcode-CLEANUP_THROW13745557
Ref: 48b13745557
Ref: library/dis opcode-BEFORE_ASYNC_WITH13745919
Ref: 452913745919
Ref: library/dis opcode-SET_ADD13746203
Ref: 452a13746203
Ref: library/dis opcode-LIST_APPEND13746355
Ref: 452b13746355
Ref: library/dis opcode-MAP_ADD13746516
Ref: a4f13746516
Ref: library/dis opcode-RETURN_VALUE13747122
Ref: 16aa13747122
Ref: library/dis opcode-RETURN_CONST13747214
Ref: 49113747214
Ref: library/dis opcode-YIELD_VALUE13747352
Ref: 15bb13747352
Ref: library/dis opcode-SETUP_ANNOTATIONS13747742
Ref: cfb13747742
Ref: library/dis opcode-POP_EXCEPT13748042
Ref: 452c13748042
Ref: library/dis opcode-RERAISE13748262
Ref: 452d13748262
Ref: library/dis opcode-PUSH_EXC_INFO13748618
Ref: 6a613748618
Ref: library/dis opcode-CHECK_EXC_MATCH13748858
Ref: 6af13748858
Ref: library/dis opcode-CHECK_EG_MATCH13749120
Ref: 6a513749120
Ref: library/dis opcode-WITH_EXCEPT_START13749577
Ref: 452e13749577
Ref: library/dis opcode-LOAD_ASSERTION_ERROR13750111
Ref: 90b13750111
Ref: library/dis opcode-LOAD_BUILD_CLASS13750277
Ref: 452f13750277
Ref: library/dis opcode-BEFORE_WITH13750416
Ref: 6b113750416
Ref: library/dis opcode-GET_LEN13750839
Ref: 453013750839
Ref: library/dis opcode-MATCH_MAPPING13750939
Ref: 453113750939
Ref: library/dis opcode-MATCH_SEQUENCE13751260
Ref: 453213751260
Ref: library/dis opcode-MATCH_KEYS13751674
Ref: 6b713751674
Ref: library/dis opcode-STORE_NAME13752139
Ref: 453313752139
Ref: library/dis opcode-DELETE_NAME13752423
Ref: 453513752423
Ref: library/dis opcode-UNPACK_SEQUENCE13752589
Ref: 173d13752589
Ref: library/dis opcode-UNPACK_EX13752881
Ref: 453613752881
Ref: library/dis opcode-STORE_ATTR13753840
Ref: 173c13753840
Ref: library/dis opcode-DELETE_ATTR13754078
Ref: 453713754078
Ref: library/dis opcode-STORE_GLOBAL13754285
Ref: 453413754285
Ref: library/dis opcode-DELETE_GLOBAL13754391
Ref: 453813754391
Ref: library/dis opcode-LOAD_CONST13754493
Ref: 453913754493
Ref: library/dis opcode-LOAD_NAME13754579
Ref: 453a13754579
Ref: library/dis opcode-LOAD_LOCALS13754775
Ref: 49013754775
Ref: library/dis opcode-LOAD_FROM_DICT_OR_GLOBALS13755040
Ref: 48f13755040
Ref: library/dis opcode-BUILD_TUPLE13755433
Ref: 453b13755433
Ref: library/dis opcode-BUILD_LIST13755759
Ref: 453c13755759
Ref: library/dis opcode-BUILD_SET13755851
Ref: 453d13755851
Ref: library/dis opcode-BUILD_MAP13755941
Ref: 15dd13755941
Ref: library/dis opcode-BUILD_CONST_KEY_MAP13756315
Ref: cf813756315
Ref: library/dis opcode-BUILD_STRING13756637
Ref: cf713756637
Ref: library/dis opcode-LIST_EXTEND13756802
Ref: 453e13756802
Ref: library/dis opcode-SET_UPDATE13756971
Ref: 453f13756971
Ref: library/dis opcode-DICT_UPDATE13757137
Ref: 454013757137
Ref: library/dis opcode-DICT_MERGE13757306
Ref: 454113757306
Ref: library/dis opcode-LOAD_ATTR13757447
Ref: 48613757447
Ref: library/dis opcode-LOAD_SUPER_ATTR13758382
Ref: 48413758382
Ref: library/dis opcode-COMPARE_OP13759453
Ref: 90d13759453
Ref: library/dis opcode-IS_OP13759830
Ref: 454213759830
Ref: library/dis opcode-CONTAINS_OP13759960
Ref: 454313759960
Ref: library/dis opcode-IMPORT_NAME13760096
Ref: 454413760096
Ref: library/dis opcode-IMPORT_FROM13760516
Ref: 454513760516
Ref: library/dis opcode-JUMP_FORWARD13760765
Ref: 14d313760765
Ref: library/dis opcode-JUMP_BACKWARD13760845
Ref: 6b013760845
Ref: library/dis opcode-JUMP_BACKWARD_NO_INTERRUPT13760979
Ref: 6a213760979
Ref: library/dis opcode-POP_JUMP_IF_TRUE13761139
Ref: 15e813761139
Ref: library/dis opcode-POP_JUMP_IF_FALSE13761670
Ref: 15e913761670
Ref: library/dis opcode-POP_JUMP_IF_NOT_NONE13762204
Ref: 16fc13762204
Ref: library/dis opcode-POP_JUMP_IF_NONE13762585
Ref: 16fb13762585
Ref: library/dis opcode-FOR_ITER13762958
Ref: 165313762958
Ref: library/dis opcode-LOAD_GLOBAL13763369
Ref: 15e413763369
Ref: library/dis opcode-LOAD_FAST13763613
Ref: 454613763613
Ref: library/dis opcode-LOAD_FAST_CHECK13763920
Ref: 48d13763920
Ref: library/dis opcode-LOAD_FAST_AND_CLEAR13764169
Ref: 48c13764169
Ref: library/dis opcode-STORE_FAST13764467
Ref: 15eb13764467
Ref: library/dis opcode-DELETE_FAST13764575
Ref: 454713764575
Ref: library/dis opcode-MAKE_CELL13764658
Ref: 6a313764658
Ref: library/dis opcode-LOAD_DEREF13764832
Ref: 454813764832
Ref: library/dis opcode-LOAD_FROM_DICT_OR_DEREF13765111
Ref: 48e13765111
Ref: library/dis opcode-STORE_DEREF13765617
Ref: 454913765617
Ref: library/dis opcode-DELETE_DEREF13765856
Ref: 454a13765856
Ref: library/dis opcode-COPY_FREE_VARS13766143
Ref: 6a113766143
Ref: library/dis opcode-RAISE_VARARGS13766365
Ref: 454b13766365
Ref: library/dis opcode-CALL13766834
Ref: 6ab13766834
Ref: library/dis opcode-CALL_KW13767602
Ref: 15de13767602
Ref: library/dis opcode-CALL_FUNCTION_EX13768434
Ref: cfa13768434
Ref: library/dis opcode-PUSH_NULL13769112
Ref: 6ac13769112
Ref: library/dis opcode-MAKE_FUNCTION13769316
Ref: cf913769316
Ref: library/dis opcode-SET_FUNCTION_ATTRIBUTE13769786
Ref: 454c13769786
Ref: library/dis opcode-BUILD_SLICE13770497
Ref: 454d13770497
Ref: library/dis opcode-EXTENDED_ARG13770966
Ref: 16a813770966
Ref: library/dis opcode-CONVERT_VALUE13771303
Ref: 454e13771303
Ref: library/dis opcode-FORMAT_SIMPLE13771779
Ref: 454f13771779
Ref: library/dis opcode-FORMAT_SPEC13772045
Ref: 455013772045
Ref: library/dis opcode-MATCH_CLASS13772357
Ref: 6b613772357
Ref: library/dis opcode-RESUME13773072
Ref: 6a713773072
Ref: library/dis opcode-RETURN_GENERATOR13773808
Ref: 69f13773808
Ref: library/dis opcode-SEND13774102
Ref: 6a013774102
Ref: library/dis opcode-HAVE_ARGUMENT13774467
Ref: 43013774467
Ref: library/dis opcode-CALL_INTRINSIC_113775320
Ref: 48913775320
Ref: library/dis opcode-CALL_INTRINSIC_213778648
Ref: 48a13778648
Ref: library/dis opcode-SETUP_FINALLY13780691
Ref: 455113780691
Ref: library/dis opcode-SETUP_CLEANUP13780955
Ref: 455213780955
Ref: library/dis opcode-SETUP_WITH13781360
Ref: 455313781360
Ref: library/dis opcode-POP_BLOCK13781790
Ref: 455413781790
Ref: library/dis opcode-JUMP13781943
Ref: 455513781943
Ref: library/dis opcode-JUMP_NO_INTERRUPT13781961
Ref: 171e13781961
Ref: library/dis opcode-LOAD_CLOSURE13782128
Ref: 15e613782128
Ref: library/dis opcode-LOAD_METHOD13782417
Ref: bc613782417
Node: Opcode collections13782551
Ref: library/dis id113782682
Ref: 455613782682
Ref: library/dis opcode-collections13782682
Ref: 450813782682
Ref: library/dis dis opname13783034
Ref: 450c13783034
Ref: library/dis dis opmap13783123
Ref: 455713783123
Ref: library/dis dis cmp_op13783201
Ref: 455813783201
Ref: library/dis dis hasarg13783272
Ref: 27d13783272
Ref: library/dis dis hasconst13783378
Ref: 455913783378
Ref: library/dis dis hasfree13783456
Ref: 455a13783456
Ref: library/dis dis hasname13783780
Ref: 455b13783780
Ref: library/dis dis hasjump13783867
Ref: 455c13783867
Ref: library/dis dis haslocal13784004
Ref: 455d13784004
Ref: library/dis dis hascompare13784088
Ref: 455e13784088
Ref: library/dis dis hasexc13784167
Ref: 43113784167
Ref: library/dis dis hasjrel13784279
Ref: 455f13784279
Ref: library/dis dis hasjabs13784460
Ref: 456013784460
Node: pickletools --- pickle 開發者的工具13784637
Ref: library/pickletools doc13784782
Ref: 456113784782
Ref: library/pickletools module-pickletools13784782
Ref: 9613784782
Ref: library/pickletools pickletools-tools-for-pickle-developers13784782
Ref: 456213784782
Ref: pickletools --- pickle 開發者的工具-Footnote-113785462
Node: 命令列用法<4>13785533
Ref: library/pickletools command-line-usage13785653
Ref: 456313785653
Ref: library/pickletools pickletools-cli13785653
Ref: 456413785653
Node: 命令列選項<4>13786575
Ref: library/pickletools command-line-options13786648
Ref: 456513786648
Ref: library/pickletools cmdoption-pickletools-a13786696
Ref: 456613786696
Ref: library/pickletools cmdoption-pickletools-annotate13786696
Ref: 456713786696
Ref: library/pickletools cmdoption-pickletools-o13786786
Ref: 456813786786
Ref: library/pickletools cmdoption-pickletools-output13786786
Ref: 456913786786
Ref: library/pickletools cmdoption-pickletools-l13786871
Ref: 456a13786871
Ref: library/pickletools cmdoption-pickletools-indentlevel13786871
Ref: 456b13786871
Ref: library/pickletools cmdoption-pickletools-m13786951
Ref: 456c13786951
Ref: library/pickletools cmdoption-pickletools-memo13786951
Ref: 456d13786951
Ref: library/pickletools cmdoption-pickletools-p13787042
Ref: 456e13787042
Ref: library/pickletools cmdoption-pickletools-preamble13787042
Ref: 456f13787042
Node: 程式化介面13787193
Ref: library/pickletools programmatic-interface13787313
Ref: 457013787313
Ref: library/pickletools pickletools dis13787361
Ref: c6a13787361
Ref: library/pickletools pickletools genops13788099
Ref: 457113788099
Ref: library/pickletools pickletools optimize13788485
Ref: 277a13788485
Node: MS Windows 特有服務13788748
Ref: library/windows doc13788901
Ref: 457213788901
Ref: library/windows ms-windows-specific-services13788901
Ref: 457313788901
Ref: library/windows mswin-specific-services13788901
Ref: 1d3313788901
Node: msvcrt --- MS VC++ runtime 提供的有用例程13789291
Ref: library/msvcrt doc13789442
Ref: 457413789442
Ref: library/msvcrt module-msvcrt13789442
Ref: 8513789442
Ref: library/msvcrt msvcrt-useful-routines-from-the-ms-vc-runtime13789442
Ref: 457513789442
Node: File Operations13790442
Ref: library/msvcrt file-operations13790562
Ref: 457613790562
Ref: library/msvcrt msvcrt-files13790562
Ref: 457713790562
Ref: library/msvcrt msvcrt locking13790613
Ref: 3ffd13790613
Ref: library/msvcrt msvcrt LK_LOCK13791280
Ref: 457813791280
Ref: library/msvcrt msvcrt LK_RLCK13791307
Ref: 457913791307
Ref: library/msvcrt msvcrt LK_NBLCK13791550
Ref: 457a13791550
Ref: library/msvcrt msvcrt LK_NBRLCK13791578
Ref: 457b13791578
Ref: library/msvcrt msvcrt LK_UNLCK13791709
Ref: 457c13791709
Ref: library/msvcrt msvcrt setmode13791818
Ref: 457d13791818
Ref: library/msvcrt msvcrt open_osfhandle13792055
Ref: 3ffe13792055
Ref: library/msvcrt msvcrt get_osfhandle13792709
Ref: 3ffc13792709
Node: Console I/O13792971
Ref: library/msvcrt console-i-o13793115
Ref: 457e13793115
Ref: library/msvcrt msvcrt-console13793115
Ref: 457f13793115
Ref: library/msvcrt msvcrt kbhit13793158
Ref: 458013793158
Ref: library/msvcrt msvcrt getch13793280
Ref: 458113793280
Ref: library/msvcrt msvcrt getwch13793759
Ref: 136313793759
Ref: library/msvcrt msvcrt getche13793869
Ref: 458213793869
Ref: library/msvcrt msvcrt getwche13794014
Ref: 136413794014
Ref: library/msvcrt msvcrt putch13794126
Ref: 458313794126
Ref: library/msvcrt msvcrt putwch13794228
Ref: 136513794228
Ref: library/msvcrt msvcrt ungetch13794350
Ref: 458413794350
Ref: library/msvcrt msvcrt ungetwch13794559
Ref: 458513794559
Node: Other Functions13794685
Ref: library/msvcrt msvcrt-other13794805
Ref: 458613794805
Ref: library/msvcrt other-functions13794805
Ref: 458713794805
Ref: library/msvcrt msvcrt heapmin13794856
Ref: 458813794856
Ref: library/msvcrt msvcrt set_error_mode13795047
Ref: 458913795047
Ref: library/msvcrt msvcrt OUT_TO_DEFAULT13795417
Ref: 458b13795417
Ref: library/msvcrt msvcrt OUT_TO_STDERR13795560
Ref: 458c13795560
Ref: library/msvcrt msvcrt OUT_TO_MSGBOX13795690
Ref: 458d13795690
Ref: library/msvcrt msvcrt REPORT_ERRMODE13795817
Ref: 458a13795817
Ref: library/msvcrt msvcrt CrtSetReportMode13795953
Ref: 458e13795953
Ref: library/msvcrt msvcrt CrtSetReportFile13796339
Ref: 458f13796339
Ref: library/msvcrt msvcrt CRT_WARN13796734
Ref: 459113796734
Ref: library/msvcrt msvcrt CRT_ERROR13796849
Ref: 459213796849
Ref: library/msvcrt msvcrt CRT_ASSERT13796967
Ref: 459313796967
Ref: library/msvcrt msvcrt CRTDBG_MODE_DEBUG13797024
Ref: 459413797024
Ref: library/msvcrt msvcrt CRTDBG_MODE_FILE13797120
Ref: 459013797120
Ref: library/msvcrt msvcrt CRTDBG_MODE_WNDW13797339
Ref: 459513797339
Ref: library/msvcrt msvcrt CRTDBG_REPORT_MODE13797499
Ref: 459613797499
Ref: library/msvcrt msvcrt CRT_ASSEMBLY_VERSION13797593
Ref: 12ec13797593
Ref: library/msvcrt msvcrt VC_ASSEMBLY_PUBLICKEYTOKEN13797705
Ref: 12ed13797705
Ref: library/msvcrt msvcrt LIBRARIES_ASSEMBLY_NAME_PREFIX13797836
Ref: 12ee13797836
Node: winreg --- Windows 註冊表存取13797973
Ref: library/winreg doc13798175
Ref: 459713798175
Ref: library/winreg module-winreg13798175
Ref: fe13798175
Ref: library/winreg winreg-windows-registry-access13798175
Ref: 459813798175
Ref: library/winreg exception-changed13798584
Ref: 459a13798584
Node: 函式<12>13798810
Ref: library/winreg functions13798910
Ref: 459b13798910
Ref: library/winreg id113798910
Ref: 459c13798910
Ref: library/winreg winreg CloseKey13798986
Ref: 459d13798986
Ref: library/winreg winreg ConnectRegistry13799307
Ref: 400113799307
Ref: library/winreg winreg CreateKey13799999
Ref: 400213799999
Ref: library/winreg winreg CreateKeyEx13800966
Ref: 12ef13800966
Ref: library/winreg winreg DeleteKey13802311
Ref: 400313802311
Ref: library/winreg winreg DeleteKeyEx13803061
Ref: 12f013803061
Ref: library/winreg winreg DeleteValue13804341
Ref: 400413804341
Ref: library/winreg winreg EnumKey13804711
Ref: 400513804711
Ref: library/winreg winreg EnumValue13805378
Ref: 400613805378
Ref: library/winreg winreg ExpandEnvironmentStrings13806643
Ref: 136613806643
Ref: library/winreg winreg FlushKey13806996
Ref: 45a413806996
Ref: library/winreg winreg LoadKey13807812
Ref: 400713807812
Ref: library/winreg winreg OpenKey13809006
Ref: 400813809006
Ref: library/winreg winreg OpenKeyEx13809077
Ref: 45a713809077
Ref: library/winreg winreg QueryInfoKey13810153
Ref: 400a13810153
Ref: library/winreg winreg QueryValue13811048
Ref: 400b13811048
Ref: library/winreg winreg QueryValueEx13811922
Ref: 400c13811922
Ref: library/winreg winreg SaveKey13812798
Ref: 400d13812798
Ref: library/winreg winreg SetValue13813840
Ref: 400e13813840
Ref: library/winreg winreg SetValueEx13815023
Ref: 169113815023
Ref: library/winreg winreg DisableReflectionKey13816273
Ref: 12f113816273
Ref: library/winreg winreg EnableReflectionKey13816907
Ref: 12f213816907
Ref: library/winreg winreg QueryReflectionKey13817418
Ref: 12f313817418
Ref: 函式<12>-Footnote-113817924
Ref: 函式<12>-Footnote-213818001
Node: 常數<10>13818078
Ref: library/winreg constants13818210
Ref: 45ac13818210
Ref: library/winreg id213818210
Ref: 45ad13818210
Node: HKEY_* Constants13818388
Ref: library/winreg hkey-constants13818473
Ref: 459f13818473
Ref: library/winreg id313818473
Ref: 45ae13818473
Ref: library/winreg winreg HKEY_CLASSES_ROOT13818526
Ref: 45af13818526
Ref: library/winreg winreg HKEY_CURRENT_USER13818779
Ref: 45b013818779
Ref: library/winreg winreg HKEY_LOCAL_MACHINE13819084
Ref: 45a613819084
Ref: library/winreg winreg HKEY_USERS13819310
Ref: 45a513819310
Ref: library/winreg winreg HKEY_PERFORMANCE_DATA13819521
Ref: 45b113819521
Ref: library/winreg winreg HKEY_CURRENT_CONFIG13819790
Ref: 45b213819790
Ref: library/winreg winreg HKEY_DYN_DATA13819927
Ref: 45b313819927
Node: Access Rights13820021
Ref: library/winreg access-rights13820126
Ref: 45a113820126
Ref: library/winreg id413820126
Ref: 45b413820126
Ref: library/winreg winreg KEY_ALL_ACCESS13820237
Ref: 45b513820237
Ref: library/winreg winreg KEY_WRITE13820528
Ref: 45a013820528
Ref: library/winreg winreg KEY_READ13820683
Ref: 45a813820683
Ref: library/winreg winreg KEY_EXECUTE13820864
Ref: 45bb13820864
Ref: library/winreg winreg KEY_QUERY_VALUE13820938
Ref: 45b613820938
Ref: library/winreg winreg KEY_SET_VALUE13821028
Ref: 45aa13821028
Ref: library/winreg winreg KEY_CREATE_SUB_KEY13821121
Ref: 45b713821121
Ref: library/winreg winreg KEY_ENUMERATE_SUB_KEYS13821213
Ref: 45b813821213
Ref: library/winreg winreg KEY_NOTIFY13821315
Ref: 45b913821315
Ref: library/winreg winreg KEY_CREATE_LINK13821451
Ref: 45ba13821451
Ref: Access Rights-Footnote-113821584
Node: 64-bit Specific13821661
Ref: library/winreg bit-access-rights13821726
Ref: 45bc13821726
Ref: library/winreg bit-specific13821726
Ref: 45bd13821726
Ref: library/winreg winreg KEY_WOW64_64KEY13821845
Ref: 45a213821845
Ref: library/winreg winreg KEY_WOW64_32KEY13822035
Ref: 45be13822035
Ref: 64-bit Specific-Footnote-113822261
Node: Value Types13822333
Ref: library/winreg id513822413
Ref: 45bf13822413
Ref: library/winreg value-types13822413
Ref: 45ab13822413
Ref: library/winreg winreg REG_BINARY13822508
Ref: 45c013822508
Ref: library/winreg winreg REG_DWORD13822570
Ref: 45c113822570
Ref: library/winreg winreg REG_DWORD_LITTLE_ENDIAN13822621
Ref: 45c213822621
Ref: library/winreg winreg REG_DWORD_BIG_ENDIAN13822755
Ref: 45c313822755
Ref: library/winreg winreg REG_EXPAND_SZ13822840
Ref: 45a313822840
Ref: library/winreg winreg REG_LINK13822971
Ref: 45c413822971
Ref: library/winreg winreg REG_MULTI_SZ13823031
Ref: 18e313823031
Ref: library/winreg winreg REG_NONE13823199
Ref: 45c513823199
Ref: library/winreg winreg REG_QWORD13823257
Ref: ca913823257
Ref: library/winreg winreg REG_QWORD_LITTLE_ENDIAN13823338
Ref: 45c613823338
Ref: library/winreg winreg REG_RESOURCE_LIST13823499
Ref: 45c713823499
Ref: library/winreg winreg REG_FULL_RESOURCE_DESCRIPTOR13823574
Ref: 45c813823574
Ref: library/winreg winreg REG_RESOURCE_REQUIREMENTS_LIST13823649
Ref: 45c913823649
Ref: library/winreg winreg REG_SZ13823732
Ref: 45a913823732
Ref: Value Types-Footnote-113823827
Node: Registry Handle Objects13823904
Ref: library/winreg handle-object13824017
Ref: 459913824017
Ref: library/winreg registry-handle-objects13824017
Ref: 45ca13824017
Ref: library/winreg winreg PyHKEY Close13825176
Ref: 459e13825176
Ref: library/winreg winreg PyHKEY Detach13825308
Ref: 400913825308
Ref: library/winreg winreg PyHKEY __enter__13825911
Ref: 45cb13825911
Ref: library/winreg winreg PyHKEY __exit__13825943
Ref: 45cc13825943
Node: winsound --- Windows 的聲音播放介面13826338
Ref: library/winsound doc13826483
Ref: 45cd13826483
Ref: library/winsound module-winsound13826483
Ref: ff13826483
Ref: library/winsound winsound-sound-playing-interface-for-windows13826483
Ref: 45ce13826483
Ref: library/winsound winsound Beep13826813
Ref: cab13826813
Ref: library/winsound winsound PlaySound13827197
Ref: cad13827197
Ref: library/winsound winsound MessageBeep13827767
Ref: cac13827767
Ref: library/winsound winsound SND_FILENAME13828370
Ref: 45cf13828370
Ref: library/winsound winsound SND_ALIAS13828505
Ref: 45d013828505
Ref: library/winsound winsound SND_LOOP13830125
Ref: 45d213830125
Ref: library/winsound winsound SND_MEMORY13830314
Ref: 45d413830314
Ref: library/winsound winsound SND_PURGE13830680
Ref: 45d513830680
Ref: library/winsound winsound SND_ASYNC13830844
Ref: 45d313830844
Ref: library/winsound winsound SND_NODEFAULT13830942
Ref: 45d113830942
Ref: library/winsound winsound SND_NOSTOP13831067
Ref: 45d613831067
Ref: library/winsound winsound SND_NOWAIT13831149
Ref: 45d713831149
Ref: library/winsound winsound MB_ICONASTERISK13831311
Ref: 45d813831311
Ref: library/winsound winsound MB_ICONEXCLAMATION13831392
Ref: 45d913831392
Ref: library/winsound winsound MB_ICONHAND13831480
Ref: 45da13831480
Ref: library/winsound winsound MB_ICONQUESTION13831554
Ref: 45db13831554
Ref: library/winsound winsound MB_OK13831636
Ref: 45dc13831636
Node: Unix 特有服務13831707
Ref: library/unix doc13831862
Ref: 45dd13831862
Ref: library/unix unix13831862
Ref: 45de13831862
Ref: library/unix unix-specific-services13831862
Ref: 45df13831862
Node: posix --- 最常見的 POSIX 系統呼叫13832667
Ref: library/posix doc13832794
Ref: 45e013832794
Ref: library/posix module-posix13832794
Ref: 9b13832794
Ref: library/posix posix-the-most-common-posix-system-calls13832794
Ref: 45e113832794
Node: 對大檔案 Large File 的支援13833973
Ref: library/posix large-file-support13834120
Ref: 45e213834120
Ref: library/posix posix-large-files13834120
Ref: 45e313834120
Node: 值得注意的模組內容13835054
Ref: library/posix notable-module-contents13835201
Ref: 45e413835201
Ref: library/posix posix-contents13835201
Ref: 45e513835201
Ref: library/posix posix environ13835389
Ref: 45e613835389
Node: pwd --- 密碼資料庫13836431
Ref: library/pwd doc13836590
Ref: 45e713836590
Ref: library/pwd module-pwd13836590
Ref: a013836590
Ref: library/pwd pwd-the-password-database13836590
Ref: 45e813836590
Ref: library/pwd pwd getpwuid13838747
Ref: 193613838747
Ref: library/pwd pwd getpwnam13838844
Ref: 303c13838844
Ref: library/pwd pwd getpwall13838938
Ref: 45e913838938
Node: grp --- 群組資料庫13839135
Ref: library/grp doc13839288
Ref: 45ea13839288
Ref: library/grp grp-the-group-database13839288
Ref: 45eb13839288
Ref: library/grp module-grp13839288
Ref: 5c13839288
Ref: library/grp grp getgrgid13840873
Ref: ccd13840873
Ref: library/grp grp getgrnam13841171
Ref: 303b13841171
Ref: library/grp grp getgrall13841345
Ref: 45ec13841345
Node: termios --- POSIX 風格 tty 控制13841545
Ref: library/termios doc13841704
Ref: 45ed13841704
Ref: library/termios module-termios13841704
Ref: ca13841704
Ref: library/termios termios-posix-style-tty-control13841704
Ref: 45ee13841704
Ref: library/termios termios tcgetattr13842712
Ref: 156c13842712
Ref: library/termios termios tcsetattr13843288
Ref: 15f313843288
Ref: library/termios termios TCSANOW13843565
Ref: 45ef13843565
Ref: library/termios termios TCSADRAIN13843641
Ref: 45f013843641
Ref: library/termios termios TCSAFLUSH13843744
Ref: 45f113843744
Ref: library/termios termios tcsendbreak13843889
Ref: 45f213843889
Ref: library/termios termios tcdrain13844099
Ref: 45f313844099
Ref: library/termios termios tcflush13844220
Ref: 45f413844220
Ref: library/termios termios tcflow13844476
Ref: 45f513844476
Ref: library/termios termios tcgetwinsize13844754
Ref: 45f613844754
Ref: library/termios termios tcsetwinsize13844996
Ref: 45f713844996
Ref: termios --- POSIX 風格 tty 控制-Footnote-113845599
Node: 範例<48>13845646
Ref: library/termios example13845728
Ref: 45f813845728
Ref: library/termios termios-example13845728
Ref: 45f913845728
Node: tty --- 終端機控制函式13846481
Ref: library/tty doc13846640
Ref: 45fa13846640
Ref: library/tty module-tty13846640
Ref: e913846640
Ref: library/tty tty-terminal-control-functions13846640
Ref: 45fb13846640
Ref: library/tty tty cfmakeraw13847048
Ref: 15c713847048
Ref: library/tty tty cfmakecbreak13847270
Ref: 156f13847270
Ref: library/tty tty setraw13847835
Ref: 15c613847835
Ref: library/tty tty setcbreak13848305
Ref: 156e13848305
Ref: tty --- 終端機控制函式-Footnote-113849288
Node: pty --- 偽終端工具13849351
Ref: library/pty doc13849513
Ref: 45fc13849513
Ref: library/pty module-pty13849513
Ref: 9f13849513
Ref: library/pty pty-pseudo-terminal-utilities13849513
Ref: 45fd13849513
Ref: library/pty pty fork13850162
Ref: 165a13850162
Ref: library/pty pty openpty13850748
Ref: 2b013850748
Ref: library/pty pty spawn13851025
Ref: f2513851025
Ref: pty --- 偽終端工具-Footnote-113853281
Node: 範例<49>13853344
Ref: library/pty example13853414
Ref: 45fe13853414
Ref: 範例<49>-Footnote-113854627
Node: fcntl --- fcntl 和 ioctl 系統呼叫13854673
Ref: library/fcntl doc13854837
Ref: 45ff13854837
Ref: library/fcntl fcntl-the-fcntl-and-ioctl-system-calls13854837
Ref: 460013854837
Ref: library/fcntl module-fcntl13854837
Ref: 4f13854837
Ref: library/fcntl fcntl fcntl13858265
Ref: 327c13858265
Ref: library/fcntl fcntl ioctl13859719
Ref: 13e513859719
Ref: library/fcntl fcntl flock13862055
Ref: 3ffb13862055
Ref: library/fcntl fcntl lockf13862578
Ref: 135a13862578
Ref: library/fcntl fcntl LOCK_UN13862916
Ref: 460113862916
Ref: library/fcntl fcntl LOCK_SH13862985
Ref: 460213862985
Ref: library/fcntl fcntl LOCK_EX13863051
Ref: 460313863051
Ref: library/fcntl fcntl LOCK_NB13863121
Ref: 460413863121
Ref: fcntl --- fcntl 和 ioctl 系統呼叫-Footnote-113865423
Ref: fcntl --- fcntl 和 ioctl 系統呼叫-Footnote-213865468
Ref: fcntl --- fcntl 和 ioctl 系統呼叫-Footnote-313865513
Node: resource --- 資源使用資訊13865558
Ref: library/resource doc13865737
Ref: 460513865737
Ref: library/resource module-resource13865737
Ref: aa13865737
Ref: library/resource resource-resource-usage-information13865737
Ref: 460613865737
Ref: library/resource resource error13866242
Ref: 460713866242
Ref: resource --- 資源使用資訊-Footnote-113866511
Node: Resource Limits13866553
Ref: library/resource resource-limits13866659
Ref: 460813866659
Ref: library/resource resource RLIM_INFINITY13867539
Ref: 460913867539
Ref: library/resource resource getrlimit13867645
Ref: 460a13867645
Ref: library/resource resource setrlimit13867937
Ref: 3f9e13867937
Ref: library/resource resource prlimit13869098
Ref: f2c13869098
Ref: library/resource resource RLIMIT_CORE13870700
Ref: 3f9f13870700
Ref: library/resource resource RLIMIT_CPU13870963
Ref: 460c13870963
Ref: library/resource resource RLIMIT_FSIZE13871325
Ref: 460d13871325
Ref: library/resource resource RLIMIT_DATA13871423
Ref: 460e13871423
Ref: library/resource resource RLIMIT_STACK13871514
Ref: 460f13871514
Ref: library/resource resource RLIMIT_RSS13871713
Ref: 461013871713
Ref: library/resource resource RLIMIT_NPROC13871833
Ref: 461113871833
Ref: library/resource resource RLIMIT_NOFILE13871938
Ref: 460b13871938
Ref: library/resource resource RLIMIT_OFILE13872054
Ref: 461213872054
Ref: library/resource resource RLIMIT_MEMLOCK13872139
Ref: 461313872139
Ref: library/resource resource RLIMIT_VMEM13872239
Ref: 461413872239
Ref: library/resource resource RLIMIT_AS13872392
Ref: 461513872392
Ref: library/resource resource RLIMIT_MSGQUEUE13872515
Ref: f2d13872515
Ref: library/resource resource RLIMIT_NICE13872705
Ref: f2e13872705
Ref: library/resource resource RLIMIT_RTPRIO13872901
Ref: f2f13872901
Ref: library/resource resource RLIMIT_RTTIME13873061
Ref: f3013873061
Ref: library/resource resource RLIMIT_SIGPENDING13873319
Ref: f3113873319
Ref: library/resource resource RLIMIT_SBSIZE13873494
Ref: f3213873494
Ref: library/resource resource RLIMIT_SWAP13873789
Ref: f3313873789
Ref: library/resource resource RLIMIT_NPTS13874164
Ref: f3413874164
Ref: library/resource resource RLIMIT_KQUEUES13874335
Ref: 17eb13874335
Ref: Resource Limits-Footnote-113874557
Ref: Resource Limits-Footnote-213874606
Ref: Resource Limits-Footnote-313874655
Node: Resource Usage13874722
Ref: library/resource resource-usage13874828
Ref: 461613874828
Ref: library/resource resource getrusage13874943
Ref: 139e13874943
Ref: library/resource resource getpagesize13879441
Ref: 461713879441
Ref: library/resource resource RUSAGE_SELF13879744
Ref: 461813879744
Ref: library/resource resource RUSAGE_CHILDREN13879947
Ref: 461913879947
Ref: library/resource resource RUSAGE_BOTH13880149
Ref: 461a13880149
Ref: library/resource resource RUSAGE_THREAD13880349
Ref: 461b13880349
Ref: Resource Usage-Footnote-113880584
Node: syslog --- Unix syslog 函式庫例程13880633
Ref: library/syslog doc13880765
Ref: 461c13880765
Ref: library/syslog module-syslog13880765
Ref: c613880765
Ref: library/syslog syslog-unix-syslog-library-routines13880765
Ref: 461d13880765
Ref: library/syslog syslog syslog13881385
Ref: 4e613881385
Ref: library/syslog syslog openlog13882843
Ref: 4e413882843
Ref: library/syslog syslog closelog13884192
Ref: 4e513884192
Ref: library/syslog syslog setlogmask13885045
Ref: 3fff13885045
Ref: library/syslog syslog LOG_EMERG13885652
Ref: 462013885652
Ref: library/syslog syslog LOG_ALERT13885681
Ref: 462113885681
Ref: library/syslog syslog LOG_CRIT13885710
Ref: 462213885710
Ref: library/syslog syslog LOG_ERR13885738
Ref: 462313885738
Ref: library/syslog syslog LOG_WARNING13885765
Ref: 462413885765
Ref: library/syslog syslog LOG_NOTICE13885796
Ref: 462513885796
Ref: library/syslog syslog LOG_INFO13885826
Ref: 461e13885826
Ref: library/syslog syslog LOG_DEBUG13885854
Ref: 462613885854
Ref: library/syslog syslog LOG_AUTH13885921
Ref: 462713885921
Ref: library/syslog syslog LOG_AUTHPRIV13885949
Ref: 462813885949
Ref: library/syslog syslog LOG_CRON13885981
Ref: 462913885981
Ref: library/syslog syslog LOG_DAEMON13886009
Ref: 462a13886009
Ref: library/syslog syslog LOG_FTP13886039
Ref: 462b13886039
Ref: library/syslog syslog LOG_INSTALL13886066
Ref: 462c13886066
Ref: library/syslog syslog LOG_KERN13886097
Ref: 462d13886097
Ref: library/syslog syslog LOG_LAUNCHD13886125
Ref: 462e13886125
Ref: library/syslog syslog LOG_LPR13886156
Ref: 462f13886156
Ref: library/syslog syslog LOG_MAIL13886183
Ref: 463013886183
Ref: library/syslog syslog LOG_NETINFO13886211
Ref: 463113886211
Ref: library/syslog syslog LOG_NEWS13886242
Ref: 463213886242
Ref: library/syslog syslog LOG_RAS13886270
Ref: 463313886270
Ref: library/syslog syslog LOG_REMOTEAUTH13886297
Ref: 463413886297
Ref: library/syslog syslog LOG_SYSLOG13886331
Ref: 463513886331
Ref: library/syslog syslog LOG_USER13886361
Ref: 461f13886361
Ref: library/syslog syslog LOG_UUCP13886389
Ref: 463613886389
Ref: library/syslog syslog LOG_LOCAL013886417
Ref: 463713886417
Ref: library/syslog syslog LOG_LOCAL113886447
Ref: 463813886447
Ref: library/syslog syslog LOG_LOCAL213886477
Ref: 463913886477
Ref: library/syslog syslog LOG_LOCAL313886507
Ref: 463a13886507
Ref: library/syslog syslog LOG_LOCAL413886537
Ref: 463b13886537
Ref: library/syslog syslog LOG_LOCAL513886567
Ref: 463c13886567
Ref: library/syslog syslog LOG_LOCAL613886597
Ref: 463d13886597
Ref: library/syslog syslog LOG_LOCAL713886627
Ref: 463e13886627
Ref: library/syslog syslog LOG_PID13887085
Ref: 463f13887085
Ref: library/syslog syslog LOG_CONS13887112
Ref: 464013887112
Ref: library/syslog syslog LOG_NDELAY13887140
Ref: 464113887140
Ref: library/syslog syslog LOG_ODELAY13887170
Ref: 464213887170
Ref: library/syslog syslog LOG_NOWAIT13887200
Ref: 464313887200
Ref: library/syslog syslog LOG_PERROR13887230
Ref: 464413887230
Node: 範例<50>13887448
Ref: library/syslog examples13887533
Ref: 464513887533
Node: 簡單範例<2>13887607
Ref: library/syslog simple-example13887669
Ref: 464613887669
Node: 模組命令列介面13888167
Ref: library/cmdline doc13888320
Ref: 464713888320
Ref: library/cmdline modules-command-line-interface-cli13888320
Ref: 464813888320
Node: 已被取代的模組13889762
Ref: library/superseded doc13889922
Ref: 464913889922
Ref: library/superseded superseded13889922
Ref: 464a13889922
Ref: library/superseded superseded-modules13889922
Ref: 464b13889922
Node: getopt --- 用於命令列選項的 C 風格剖析器13890337
Ref: library/getopt doc13890494
Ref: 464c13890494
Ref: library/getopt getopt-c-style-parser-for-command-line-options13890494
Ref: 464d13890494
Ref: library/getopt module-getopt13890494
Ref: 5713890494
Ref: library/getopt getopt getopt13891679
Ref: 142613891679
Ref: library/getopt getopt gnu_getopt13893866
Ref: 142513893866
Ref: library/getopt getopt GetoptError13894444
Ref: 464e13894444
Ref: library/getopt getopt error13895021
Ref: 464f13895021
Ref: getopt --- 用於命令列選項的 C 風格剖析器-Footnote-113897459
Node: optparse --- 命令列選項剖析器13897525
Ref: library/optparse doc13897682
Ref: 465013897682
Ref: library/optparse module-optparse13897682
Ref: 9013897682
Ref: library/optparse optparse-parser-for-command-line-options13897682
Ref: 465113897682
Ref: optparse --- 命令列選項剖析器-Footnote-113900595
Node: 背景13900663
Ref: library/optparse background13900761
Ref: 465213900761
Ref: library/optparse optparse-background13900761
Ref: 465313900761
Node: 術語13901231
Ref: library/optparse optparse-terminology13901310
Ref: 465413901310
Ref: library/optparse terminology13901310
Ref: 465513901310
Node: What are options for?13905121
Ref: library/optparse optparse-what-options-for13905243
Ref: 465613905243
Ref: library/optparse what-are-options-for13905243
Ref: 465713905243
Node: What are positional arguments for?13906913
Ref: library/optparse optparse-what-positional-arguments-for13907020
Ref: 465813907020
Ref: library/optparse what-are-positional-arguments-for13907020
Ref: 465913907020
Node: 教學<4>13908342
Ref: library/optparse optparse-tutorial13908464
Ref: 465a13908464
Ref: library/optparse tutorial13908464
Ref: 465b13908464
Node: Understanding option actions13911068
Ref: library/optparse optparse-understanding-option-actions13911167
Ref: 466013911167
Ref: library/optparse understanding-option-actions13911167
Ref: 466113911167
Node: The store action13911755
Ref: library/optparse optparse-store-action13911892
Ref: 466313911892
Ref: library/optparse the-store-action13911892
Ref: 466413911892
Node: Handling boolean flag options13914077
Ref: library/optparse handling-boolean-flag-options13914199
Ref: 466513914199
Ref: library/optparse optparse-handling-boolean-options13914199
Ref: 466613914199
Node: Other actions13915079
Ref: library/optparse optparse-other-actions13915199
Ref: 466713915199
Ref: library/optparse other-actions13915199
Ref: 466813915199
Node: Default values13915654
Ref: library/optparse default-values13915760
Ref: 466c13915760
Ref: library/optparse optparse-default-values13915760
Ref: 466d13915760
Node: Generating help13917649
Ref: library/optparse generating-help13917767
Ref: 466e13917767
Ref: library/optparse optparse-generating-help13917767
Ref: 466f13917767
Node: Grouping Options13921907
Ref: library/optparse grouping-options13921975
Ref: 467013921975
Ref: library/optparse optparse OptionGroup13922306
Ref: 467113922306
Ref: library/optparse optparse OptionParser get_option_group13925805
Ref: 467213925805
Node: Printing a version string13926073
Ref: library/optparse optparse-printing-version-string13926204
Ref: 467313926204
Ref: library/optparse printing-a-version-string13926204
Ref: 467413926204
Ref: library/optparse optparse OptionParser print_version13927088
Ref: 467513927088
Ref: library/optparse optparse OptionParser get_version13927462
Ref: 467713927462
Node: How optparse handles errors13927606
Ref: library/optparse how-optparse-handles-errors13927745
Ref: 467813927745
Ref: library/optparse optparse-how-optparse-handles-errors13927745
Ref: 467913927745
Node: Putting it all together13929829
Ref: library/optparse optparse-putting-it-all-together13929934
Ref: 467a13929934
Ref: library/optparse putting-it-all-together13929934
Ref: 467b13929934
Node: Reference Guide13930850
Ref: library/optparse optparse-reference-guide13930982
Ref: 466a13930982
Ref: library/optparse reference-guide13930982
Ref: 467c13930982
Node: Creating the parser13931344
Ref: library/optparse creating-the-parser13931445
Ref: 467d13931445
Ref: library/optparse optparse-creating-parser13931445
Ref: 467e13931445
Ref: library/optparse optparse OptionParser13931590
Ref: 143c13931590
Node: Populating the parser13934597
Ref: library/optparse optparse-populating-parser13934723
Ref: 468013934723
Ref: library/optparse populating-the-parser13934723
Ref: 468113934723
Node: Defining options13936007
Ref: library/optparse defining-options13936131
Ref: 468213936131
Ref: library/optparse optparse-defining-options13936131
Ref: 468313936131
Ref: library/optparse optparse OptionParser add_option13936547
Ref: 2b9e13936547
Ref: library/optparse optparse Values13938630
Ref: 2ba013938630
Node: Option attributes13939873
Ref: library/optparse option-attributes13939999
Ref: 468713939999
Ref: library/optparse optparse-option-attributes13939999
Ref: 468813939999
Ref: library/optparse optparse Option13940056
Ref: 468413940056
Ref: library/optparse optparse Option action13940675
Ref: 465c13940675
Ref: library/optparse optparse Option type13940902
Ref: 465d13940902
Ref: library/optparse optparse Option dest13941125
Ref: 465e13941125
Ref: library/optparse optparse Option default13941465
Ref: 468a13941465
Ref: library/optparse optparse Option nargs13941654
Ref: 468c13941654
Ref: library/optparse optparse Option const13941891
Ref: 466913941891
Ref: library/optparse optparse Option choices13941998
Ref: 468d13941998
Ref: library/optparse optparse Option callback13942119
Ref: 468e13942119
Ref: library/optparse optparse Option callback_args13942348
Ref: 468f13942348
Ref: library/optparse optparse Option callback_kwargs13942381
Ref: 469013942381
Ref: library/optparse optparse Option help13942542
Ref: 465f13942542
Ref: library/optparse optparse Option metavar13942887
Ref: 469113942887
Node: Standard option actions13943087
Ref: library/optparse optparse-standard-option-actions13943218
Ref: 468513943218
Ref: library/optparse standard-option-actions13943218
Ref: 469213943218
Node: Standard option types13951300
Ref: library/optparse optparse-standard-option-types13951429
Ref: 468913951429
Ref: library/optparse standard-option-types13951429
Ref: 469313951429
Node: 剖析引數<2>13952907
Ref: library/optparse optparse-parsing-arguments13953057
Ref: 468613953057
Ref: library/optparse parsing-arguments13953057
Ref: 469413953057
Ref: library/optparse optparse OptionParser parse_args13953209
Ref: 143d13953209
Node: Querying and manipulating your option parser13954592
Ref: library/optparse optparse-querying-manipulating-option-parser13954746
Ref: 469513954746
Ref: library/optparse querying-and-manipulating-your-option-parser13954746
Ref: 469613954746
Ref: library/optparse optparse OptionParser disable_interspersed_args13955053
Ref: 2b9f13955053
Ref: library/optparse optparse OptionParser enable_interspersed_args13955841
Ref: 469713955841
Ref: library/optparse optparse OptionParser get_option13956047
Ref: 469813956047
Ref: library/optparse optparse OptionParser has_option13956220
Ref: 469913956220
Ref: library/optparse optparse OptionParser remove_option13956396
Ref: 469a13956396
Node: Conflicts between options13956782
Ref: library/optparse conflicts-between-options13956931
Ref: 469b13956931
Ref: library/optparse optparse-conflicts-between-options13956931
Ref: 467f13956931
Node: Cleanup<2>13959388
Ref: library/optparse cleanup13959505
Ref: 469d13959505
Ref: library/optparse optparse-cleanup13959505
Ref: 469e13959505
Node: 其他方法13959916
Ref: library/optparse optparse-other-methods13959999
Ref: 469f13959999
Ref: library/optparse other-methods13959999
Ref: 46a013959999
Ref: library/optparse optparse OptionParser set_usage13960095
Ref: 46a113960095
Ref: library/optparse optparse OptionParser print_usage13960384
Ref: 467613960384
Ref: library/optparse optparse OptionParser get_usage13960720
Ref: 46a213960720
Ref: library/optparse optparse OptionParser set_defaults13960858
Ref: 468b13960858
Node: Option Callbacks13962022
Ref: library/optparse option-callbacks13962163
Ref: 46a313962163
Ref: library/optparse optparse-option-callbacks13962163
Ref: 466b13962163
Node: Defining a callback option13963376
Ref: library/optparse defining-a-callback-option13963488
Ref: 46a413963488
Ref: library/optparse optparse-defining-callback-option13963488
Ref: 46a513963488
Node: How callbacks are called13965708
Ref: library/optparse how-callbacks-are-called13965857
Ref: 46a613965857
Ref: library/optparse optparse-how-callbacks-called13965857
Ref: 46a713965857
Node: Raising errors in a callback13968464
Ref: library/optparse optparse-raising-errors-in-callback13968622
Ref: 46a813968622
Ref: library/optparse raising-errors-in-a-callback13968622
Ref: 46a913968622
Node: Callback example 1 trivial callback13969100
Ref: library/optparse callback-example-1-trivial-callback13969271
Ref: 46aa13969271
Ref: library/optparse optparse-callback-example-113969271
Ref: 46ab13969271
Node: Callback example 2 check option order13969717
Ref: library/optparse callback-example-2-check-option-order13969909
Ref: 46ac13969909
Ref: library/optparse optparse-callback-example-213969909
Ref: 46ad13969909
Node: Callback example 3 check option order generalized13970465
Ref: library/optparse callback-example-3-check-option-order-generalized13970666
Ref: 46ae13970666
Ref: library/optparse optparse-callback-example-313970666
Ref: 46af13970666
Node: Callback example 4 check arbitrary condition13971439
Ref: library/optparse callback-example-4-check-arbitrary-condition13971637
Ref: 46b013971637
Ref: library/optparse optparse-callback-example-413971637
Ref: 46b113971637
Node: Callback example 5 fixed arguments13972429
Ref: library/optparse callback-example-5-fixed-arguments13972615
Ref: 46b213972615
Ref: library/optparse optparse-callback-example-513972615
Ref: 46b313972615
Node: Callback example 6 variable arguments13973685
Ref: library/optparse callback-example-6-variable-arguments13973818
Ref: 46b413973818
Ref: library/optparse optparse-callback-example-613973818
Ref: 46b513973818
Node: Extending optparse13975915
Ref: library/optparse extending-optparse13976051
Ref: 46b613976051
Ref: library/optparse optparse-extending-optparse13976051
Ref: 466213976051
Node: Adding new types13976388
Ref: library/optparse adding-new-types13976486
Ref: 46b713976486
Ref: library/optparse optparse-adding-new-types13976486
Ref: 46b813976486
Ref: library/optparse optparse Option TYPES13976778
Ref: 46b913976778
Ref: library/optparse optparse Option TYPE_CHECKER13976934
Ref: 46ba13976934
Node: Adding new actions13979954
Ref: library/optparse adding-new-actions13980052
Ref: 46bb13980052
Ref: library/optparse optparse-adding-new-actions13980052
Ref: 46bc13980052
Ref: library/optparse optparse Option ACTIONS13981139
Ref: 46bd13981139
Ref: library/optparse optparse Option STORE_ACTIONS13981212
Ref: 46be13981212
Ref: library/optparse optparse Option TYPED_ACTIONS13981298
Ref: 46bf13981298
Ref: library/optparse optparse Option ALWAYS_TYPED_ACTIONS13981384
Ref: 46c013981384
Node: 例外<16>13984676
Ref: library/optparse exceptions13984787
Ref: 46c113984787
Ref: library/optparse optparse OptionError13984820
Ref: 2ba113984820
Ref: library/optparse optparse OptionConflictError13984958
Ref: 469c13984958
Ref: library/optparse optparse OptionValueError13985083
Ref: 2ba213985083
Ref: library/optparse optparse BadOptionError13985203
Ref: 46c213985203
Ref: library/optparse optparse AmbiguousOptionError13985305
Ref: 46c313985305
Ref: library/security_warnings security-warnings13985415
Ref: 46c413985415
Node: 安全性注意事項<4>13985415
Ref: library/security_warnings doc13985545
Ref: 46c513985545
Ref: library/security_warnings security-considerations13985545
Ref: 46c613985545
Ref: 安全性注意事項<4>-Footnote-113987212
Node: 擴充和嵌入 Python 直譯器13987271
Ref: extending/index doc13987425
Ref: 46c713987425
Ref: extending/index extending-and-embedding-the-python-interpreter13987425
Ref: 46c813987425
Ref: extending/index extending-index13987425
Ref: 1ae113987425
Node: 推薦的第三方工具13988740
Ref: extending/index recommended-third-party-tools13988878
Ref: 46c913988878
Ref: 推薦的第三方工具-Footnote-113989527
Ref: 推薦的第三方工具-Footnote-213989555
Ref: 推薦的第三方工具-Footnote-313989591
Ref: 推薦的第三方工具-Footnote-413989620
Ref: 推薦的第三方工具-Footnote-513989654
Node: 不使用第三方工具建立擴充13989727
Ref: extending/index creating-extensions-without-third-party-tools13989936
Ref: 46ca13989936
Node: 以 C 或 C++ 擴充 Python13990509
Ref: extending/extending doc13990651
Ref: 46cb13990651
Ref: extending/extending extending-intro13990651
Ref: 46cc13990651
Ref: extending/extending extending-python-with-c-or-c13990651
Ref: 46cd13990651
Ref: 以 C 或 C++ 擴充 Python-Footnote-113992565
Node: 一個簡單範例13992602
Ref: extending/extending a-simple-example13992725
Ref: 46ce13992725
Ref: extending/extending extending-simpleexample13992725
Ref: 46cf13992725
Ref: 一個簡單範例-Footnote-113996555
Node: Intermezzo Errors and Exceptions13996704
Ref: extending/extending extending-errors13996848
Ref: 46d013996848
Ref: extending/extending intermezzo-errors-and-exceptions13996848
Ref: 46d113996848
Node: 回到範例14003689
Ref: extending/extending back-to-the-example14003868
Ref: 46d414003868
Ref: extending/extending backtoexample14003868
Ref: 46d514003868
Node: The Module's Method Table and Initialization Function14005503
Ref: extending/extending methodtable14005673
Ref: 46d714005673
Ref: extending/extending the-module-s-method-table-and-initialization-function14005673
Ref: 46d814005673
Ref: The Module's Method Table and Initialization Function-Footnote-114011427
Node: Compilation and Linkage14011469
Ref: extending/extending compilation14011658
Ref: 46db14011658
Ref: extending/extending compilation-and-linkage14011658
Ref: 46dc14011658
Node: Calling Python Functions from C14013124
Ref: extending/extending calling-python-functions-from-c14013304
Ref: 46de14013304
Ref: extending/extending callingpython14013304
Ref: 46df14013304
Node: Extracting Parameters in Extension Functions14019965
Ref: extending/extending extracting-parameters-in-extension-functions14020164
Ref: 46e314020164
Ref: extending/extending parsetuple14020164
Ref: 46e014020164
Node: Keyword Parameters for Extension Functions14022792
Ref: extending/extending keyword-parameters-for-extension-functions14022985
Ref: 46e414022985
Ref: extending/extending parsetupleandkeywords14022985
Ref: 46e514022985
Node: Building Arbitrary Values14025659
Ref: extending/extending building-arbitrary-values14025824
Ref: 46e614025824
Ref: extending/extending buildvalue14025824
Ref: 46e714025824
Node: Reference Counts14027910
Ref: extending/extending refcounts14028058
Ref: 46e114028058
Ref: extending/extending reference-counts14028058
Ref: 46e814028058
Node: Reference Counting in Python14032482
Ref: extending/extending refcountsinpython14032587
Ref: 46e914032587
Ref: extending/extending reference-counting-in-python14032587
Ref: 46ea14032587
Ref: Reference Counting in Python-Footnote-114034945
Ref: Reference Counting in Python-Footnote-214035065
Node: Ownership Rules14035235
Ref: extending/extending ownership-rules14035357
Ref: 46eb14035357
Ref: extending/extending ownershiprules14035357
Ref: 46ec14035357
Node: Thin Ice14037807
Ref: extending/extending thin-ice14037912
Ref: 46f114037912
Ref: extending/extending thinice14037912
Ref: 46f214037912
Node: NULL 指標14041150
Ref: extending/extending null-pointers14041231
Ref: 46f414041231
Ref: extending/extending nullpointers14041231
Ref: 46f514041231
Ref: NULL 指標-Footnote-114042836
Node: Writing Extensions in C++14042966
Ref: extending/extending cplusplus14043130
Ref: 46f614043130
Ref: extending/extending writing-extensions-in-c14043130
Ref: 46f714043130
Node: Providing a C API for an Extension Module14043849
Ref: extending/extending providing-a-c-api-for-an-extension-module14043988
Ref: 46f814043988
Ref: extending/extending using-capsules14043988
Ref: 12ea14043988
Node: Defining Extension Types Tutorial14052768
Ref: extending/newtypes_tutorial doc14052959
Ref: 172f14052959
Ref: extending/newtypes_tutorial defining-extension-types-tutorial14052959
Ref: 46fa14052959
Ref: extending/newtypes_tutorial defining-new-types14052959
Ref: 46fb14052959
Node: The Basics14053603
Ref: extending/newtypes_tutorial dnt-basics14053736
Ref: 46fc14053736
Ref: extending/newtypes_tutorial the-basics14053736
Ref: 46fd14053736
Node: Adding data and methods to the Basic example14062718
Ref: extending/newtypes_tutorial adding-data-and-methods-to-the-basic-example14062904
Ref: 470314062904
Ref: Adding data and methods to the Basic example-Footnote-114078828
Ref: Adding data and methods to the Basic example-Footnote-214078921
Node: Providing finer control over data attributes14079056
Ref: extending/newtypes_tutorial providing-finer-control-over-data-attributes14079268
Ref: 470b14079268
Ref: Providing finer control over data attributes-Footnote-114088794
Node: Supporting cyclic garbage collection14089168
Ref: extending/newtypes_tutorial supporting-cyclic-garbage-collection14089359
Ref: 470d14089359
Ref: Supporting cyclic garbage collection-Footnote-114099708
Node: Subclassing other types14099882
Ref: extending/newtypes_tutorial subclassing-other-types14100020
Ref: 470f14100020
Node: Defining Extension Types Assorted Topics14105145
Ref: extending/newtypes doc14105338
Ref: 471214105338
Ref: extending/newtypes defining-extension-types-assorted-topics14105338
Ref: 471314105338
Ref: extending/newtypes new-types-topics14105338
Ref: 471414105338
Ref: extending/newtypes dnt-type-methods14105435
Ref: 471514105435
Node: Finalization and De-allocation14110179
Ref: extending/newtypes finalization-and-de-allocation14110314
Ref: 471614110314
Ref: Finalization and De-allocation-Footnote-114113811
Node: Object Presentation14113853
Ref: extending/newtypes object-presentation14114017
Ref: 471814114017
Node: Attribute Management14115672
Ref: extending/newtypes attribute-management14115823
Ref: 471b14115823
Node: Generic Attribute Management14117370
Ref: extending/newtypes generic-attribute-management14117498
Ref: 470814117498
Ref: extending/newtypes id114117498
Ref: 471c14117498
Node: Type-specific Attribute Management14121063
Ref: extending/newtypes type-specific-attribute-management14121191
Ref: 472114121191
Node: Object Comparison14122953
Ref: extending/newtypes object-comparison14123110
Ref: 472414123110
Node: Abstract Protocol Support14124891
Ref: extending/newtypes abstract-protocol-support14125050
Ref: 472714125050
Node: Weak Reference Support14130755
Ref: extending/newtypes weak-reference-support14130913
Ref: 472c14130913
Ref: extending/newtypes weakref-support14130913
Ref: 243414130913
Node: More Suggestions14132204
Ref: extending/newtypes more-suggestions14132328
Ref: 472d14132328
Node: 建立 C 與 C++ 擴充套件14133296
Ref: extending/building doc14133494
Ref: 472e14133494
Ref: extending/building building14133494
Ref: 46dd14133494
Ref: extending/building building-c-and-c-extensions14133494
Ref: 472f14133494
Ref: extending/building c PyInit_modulename14134010
Ref: 473014134010
Ref: extending/building install-index14135233
Ref: e9a14135233
Ref: 建立 C 與 C++ 擴充套件-Footnote-114135330
Node: Building C and C++ Extensions with setuptools14135372
Ref: extending/building building-c-and-c-extensions-with-setuptools14135483
Ref: 473314135483
Ref: extending/building setuptools-index14135483
Ref: e9b14135483
Node: 建置 Windows 上的 C 和 C++ 擴充14135846
Ref: extending/windows doc14135995
Ref: 473414135995
Ref: extending/windows building-c-and-c-extensions-on-windows14135995
Ref: 473514135995
Ref: extending/windows building-on-windows14135995
Ref: 1d3714135995
Node: A Cookbook Approach14137253
Ref: extending/windows a-cookbook-approach14137392
Ref: 473614137392
Ref: extending/windows win-cookbook14137392
Ref: 473714137392
Ref: A Cookbook Approach-Footnote-114138021
Node: Differences Between Unix and Windows14138099
Ref: extending/windows differences-between-unix-and-windows14138269
Ref: 473814138269
Ref: extending/windows dynamic-linking14138269
Ref: 473914138269
Node: Using DLLs in Practice14141180
Ref: extending/windows using-dlls-in-practice14141322
Ref: 473a14141322
Ref: extending/windows win-dlls14141322
Ref: 473b14141322
Node: 在更大的應用程式中嵌入 CPython 運行環境 runtime14142853
Ref: extending/index embedding-the-cpython-runtime-in-a-larger-application14143029
Ref: 473c14143029
Node: 在其它 App 內嵌入 Python14143456
Ref: extending/embedding doc14143585
Ref: 473d14143585
Ref: extending/embedding embedding14143585
Ref: 1d4f14143585
Ref: extending/embedding embedding-python-in-another-application14143585
Ref: 473e14143585
Node: Very High Level Embedding14145897
Ref: extending/embedding high-level-embedding14146042
Ref: 474114146042
Ref: extending/embedding very-high-level-embedding14146042
Ref: 474214146042
Node: Beyond Very High Level Embedding An overview14148376
Ref: extending/embedding beyond-very-high-level-embedding-an-overview14148544
Ref: 474314148544
Ref: extending/embedding lower-level-embedding14148544
Ref: 474414148544
Node: Pure Embedding14150263
Ref: extending/embedding id114150431
Ref: 474514150431
Ref: extending/embedding pure-embedding14150431
Ref: 474614150431
Node: Extending Embedded Python14155047
Ref: extending/embedding extending-embedded-python14155194
Ref: 474914155194
Ref: extending/embedding extending-with-embedding14155194
Ref: 474a14155194
Node: Embedding Python in C++14157174
Ref: extending/embedding embedding-python-in-c14157352
Ref: 474b14157352
Ref: extending/embedding embeddingincplusplus14157352
Ref: 474c14157352
Node: Compiling and Linking under Unix-like systems14157724
Ref: extending/embedding compiling14157868
Ref: 474714157868
Ref: extending/embedding compiling-and-linking-under-unix-like-systems14157868
Ref: 474d14157868
Node: Python/C API 參考手冊14160061
Ref: c-api/index doc14160196
Ref: 474f14160196
Ref: c-api/index c-api-index14160196
Ref: 1ae214160196
Ref: c-api/index python-c-api-reference-manual14160196
Ref: 475014160196
Node: 簡介<10>14161052
Ref: c-api/intro doc14161148
Ref: 475114161148
Ref: c-api/intro api-intro14161148
Ref: 475214161148
Ref: c-api/intro introduction14161148
Ref: 475314161148
Node: 編寫標準14162472
Ref: c-api/intro coding-standards14162566
Ref: 475414162566
Ref: 編寫標準-Footnote-114162947
Node: 引入檔案 include files14162989
Ref: c-api/intro api-includes14163107
Ref: 72814163107
Ref: c-api/intro include-files14163107
Ref: 475514163107
Node: 有用的巨集14165503
Ref: c-api/intro useful-macros14165639
Ref: 475614165639
Ref: c-api/intro c PyMODINIT_FUNC14165898
Ref: 144214165898
Ref: c-api/intro c Py_ABS14166684
Ref: 475714166684
Ref: c-api/intro c Py_ALWAYS_INLINE14166775
Ref: 17b914166775
Ref: c-api/intro c Py_CHARMASK14167705
Ref: 475814167705
Ref: c-api/intro c Py_DEPRECATED14167888
Ref: a4714167888
Ref: c-api/intro c Py_GETENV14168143
Ref: 475914168143
Ref: c-api/intro c Py_MAX14168334
Ref: 475a14168334
Ref: c-api/intro c Py_MEMBER_SIZE14168446
Ref: 475b14168446
Ref: c-api/intro c Py_MIN14168598
Ref: 475c14168598
Ref: c-api/intro c Py_NO_INLINE14168710
Ref: 17ba14168710
Ref: c-api/intro c Py_STRINGIFY14169005
Ref: 475d14169005
Ref: c-api/intro c Py_UNREACHABLE14169160
Ref: b5c14169160
Ref: c-api/intro c Py_UNUSED14170227
Ref: 161914170227
Ref: c-api/intro c PyDoc_STRVAR14170435
Ref: 187614170435
Ref: c-api/intro c PyDoc_STR14171063
Ref: 171014171063
Ref: 有用的巨集-Footnote-114171617
Ref: 有用的巨集-Footnote-214171682
Ref: 有用的巨集-Footnote-314171724
Node: 物件、型別和參照計數14171766
Ref: c-api/intro api-objects14171886
Ref: 475e14171886
Ref: c-api/intro objects-types-and-reference-counts14171886
Ref: 475f14171886
Node: 參照計數14173243
Ref: c-api/intro api-refcounts14173337
Ref: 476014173337
Ref: c-api/intro reference-counts14173337
Ref: 476114173337
Node: 參照計數詳細資訊14176756
Ref: c-api/intro api-refcountdetails14176829
Ref: 476214176829
Ref: c-api/intro reference-count-details14176829
Ref: 476314176829
Node: 型別14183513
Ref: c-api/intro api-types14183607
Ref: 476614183607
Ref: c-api/intro types14183607
Ref: 476714183607
Ref: c-api/intro c Py_ssize_t14183990
Ref: a0314183990
Ref: 型別-Footnote-114184403
Node: 例外<17>14184445
Ref: c-api/intro api-exceptions14184565
Ref: 476814184565
Ref: c-api/intro exceptions14184565
Ref: 476914184565
Node: 嵌入式Python14190276
Ref: c-api/intro api-embedding14190378
Ref: 476b14190378
Ref: c-api/intro embedding-python14190378
Ref: 476c14190378
Node: 除錯建置14193370
Ref: c-api/intro api-debugging14193453
Ref: 476e14193453
Ref: c-api/intro debugging-builds14193453
Ref: 476f14193453
Ref: c-api/intro c Py_DEBUG14193997
Ref: 3f4f14193997
Node: C API 穩定性14195037
Ref: c-api/stable doc14195167
Ref: 477014195167
Ref: c-api/stable c-api-stability14195167
Ref: 477114195167
Ref: c-api/stable stable14195167
Ref: 4f914195167
Ref: C API 穩定性-Footnote-114196721
Ref: C API 穩定性-Footnote-214196763
Node: 不穩定的 C API14196818
Ref: c-api/stable id114196933
Ref: 477314196933
Ref: c-api/stable unstable-c-api14196933
Ref: 4ed14196933
Node: 穩定的應用程式二進位介面14197456
Ref: c-api/stable stable-application-binary-interface14197598
Ref: 477414197598
Node: 受限 C API14197970
Ref: c-api/stable id214198074
Ref: 477514198074
Ref: c-api/stable limited-c-api14198074
Ref: 31814198074
Ref: c-api/stable c Py_LIMITED_API14198339
Ref: 35a14198339
Node: 穩定 ABI14199172
Ref: c-api/stable id314199311
Ref: 477614199311
Ref: c-api/stable stable-abi14199311
Ref: 477714199311
Node: 受限 API 範圍和性能14200314
Ref: c-api/stable limited-api-scope-and-performance14200464
Ref: 477814200464
Node: 受限 API 注意事項14201473
Ref: c-api/stable limited-api-caveats14201604
Ref: 477a14201604
Node: 平台注意事項14203152
Ref: c-api/stable platform-considerations14203296
Ref: 477b14203296
Ref: c-api/stable stable-abi-platform14203296
Ref: 477214203296
Node: 受限 API 的內容14203827
Ref: c-api/stable contents-of-limited-api14203926
Ref: 477c14203926
Ref: c-api/stable limited-api-list14203926
Ref: 73e14203926
Node: The Very High Level Layer14239524
Ref: c-api/veryhigh doc14239659
Ref: 48df14239659
Ref: c-api/veryhigh the-very-high-level-layer14239659
Ref: 48e014239659
Ref: c-api/veryhigh veryhigh14239659
Ref: 48e114239659
Ref: c-api/veryhigh c Py_Main14240686
Ref: bcc14240686
Ref: c-api/veryhigh c Py_BytesMain14241692
Ref: 96514241692
Ref: c-api/veryhigh c PyRun_AnyFile14241926
Ref: 48e514241926
Ref: c-api/veryhigh c PyRun_AnyFileFlags14242149
Ref: 48e714242149
Ref: c-api/veryhigh c PyRun_AnyFileEx14242389
Ref: 48e814242389
Ref: c-api/veryhigh c PyRun_AnyFileExFlags14242616
Ref: 48e614242616
Ref: c-api/veryhigh c PyRun_SimpleString14243276
Ref: 473f14243276
Ref: c-api/veryhigh c PyRun_SimpleStringFlags14243501
Ref: 48ea14243501
Ref: c-api/veryhigh c PyRun_SimpleFile14244187
Ref: 474014244187
Ref: c-api/veryhigh c PyRun_SimpleFileEx14244416
Ref: 48eb14244416
Ref: c-api/veryhigh c PyRun_SimpleFileExFlags14244636
Ref: 180b14244636
Ref: c-api/veryhigh c PyRun_InteractiveOne14245315
Ref: 48ec14245315
Ref: c-api/veryhigh c PyRun_InteractiveOneFlags14245521
Ref: 48ed14245521
Ref: c-api/veryhigh c PyRun_InteractiveLoop14246263
Ref: 48e914246263
Ref: c-api/veryhigh c PyRun_InteractiveLoopFlags14246471
Ref: 48ee14246471
Ref: c-api/veryhigh c PyOS_InputHook14246917
Ref: 52b14246917
Ref: c-api/veryhigh c PyOS_ReadlineFunctionPointer14247537
Ref: 52c14247537
Ref: c-api/veryhigh c PyRun_String14248656
Ref: 18e014248656
Ref: c-api/veryhigh c PyRun_StringFlags14248931
Ref: 48ef14248931
Ref: c-api/veryhigh c PyRun_File14249610
Ref: 48f014249610
Ref: c-api/veryhigh c PyRun_FileEx14249932
Ref: 48f214249932
Ref: c-api/veryhigh c PyRun_FileFlags14250245
Ref: 48f314250245
Ref: c-api/veryhigh c PyRun_FileExFlags14250571
Ref: 48f114250571
Ref: c-api/veryhigh c Py_CompileString14251152
Ref: 82914251152
Ref: c-api/veryhigh c Py_CompileStringFlags14251468
Ref: 48f414251468
Ref: c-api/veryhigh c Py_CompileStringObject14251770
Ref: 48f614251770
Ref: c-api/veryhigh c Py_CompileStringExFlags14252920
Ref: 48f514252920
Ref: c-api/veryhigh c PyEval_EvalCode14253305
Ref: 82a14253305
Ref: c-api/veryhigh c PyEval_EvalCodeEx14253683
Ref: 166b14253683
Ref: c-api/veryhigh c PyEval_EvalFrame14254416
Ref: 47ce14254416
Ref: c-api/veryhigh c PyEval_EvalFrameEx14254702
Ref: fd114254702
Ref: c-api/veryhigh c PyEval_MergeCompilerFlags14255442
Ref: 48f714255442
Ref: c-api/veryhigh c Py_eval_input14255632
Ref: 48e214255632
Ref: c-api/veryhigh c Py_file_input14255787
Ref: 48e314255787
Ref: c-api/veryhigh c Py_single_input14256070
Ref: 48e414256070
Ref: c-api/veryhigh c PyCompilerFlags14256293
Ref: a4414256293
Ref: c-api/veryhigh c PyCompilerFlags cf_flags14256833
Ref: 48f814256833
Ref: c-api/veryhigh c PyCompilerFlags cf_feature_version14256899
Ref: 48f914256899
Ref: c-api/veryhigh c CO_FUTURE_DIVISION14257275
Ref: 48fa14257275
Ref: The Very High Level Layer-Footnote-114257488
Node: 參照計數<2>14257530
Ref: c-api/refcounting doc14257662
Ref: 48fb14257662
Ref: c-api/refcounting countingrefs14257662
Ref: 48fc14257662
Ref: c-api/refcounting reference-counting14257662
Ref: 48fd14257662
Ref: c-api/refcounting c Py_REFCNT14257766
Ref: 84e14257766
Ref: c-api/refcounting c Py_SET_REFCNT14258511
Ref: 84f14258511
Ref: c-api/refcounting c Py_INCREF14258925
Ref: 51414258925
Ref: c-api/refcounting c Py_XINCREF14259746
Ref: a0814259746
Ref: c-api/refcounting c Py_NewRef14259970
Ref: 83e14259970
Ref: c-api/refcounting c Py_XNewRef14260668
Ref: 83f14260668
Ref: c-api/refcounting c Py_DECREF14260981
Ref: 51514260981
Ref: c-api/refcounting c Py_XDECREF14262446
Ref: 73314262446
Ref: c-api/refcounting c Py_CLEAR14262688
Ref: 51e14262688
Ref: c-api/refcounting c Py_IncRef14263429
Ref: 48bb14263429
Ref: c-api/refcounting c Py_DecRef14263679
Ref: 48b414263679
Ref: c-api/refcounting c Py_SETREF14263920
Ref: 51f14263920
Ref: c-api/refcounting c Py_XSETREF14264658
Ref: 52014264658
Ref: 參照計數<2>-Footnote-114265015
Ref: 參照計數<2>-Footnote-214265057
Node: 例外處理14265099
Ref: c-api/exceptions doc14265212
Ref: 48fe14265212
Ref: c-api/exceptions exception-handling14265212
Ref: 48ff14265212
Ref: c-api/exceptions exceptionhandling14265212
Ref: 41fa14265212
Node: Printing and clearing14267506
Ref: c-api/exceptions printing-and-clearing14267603
Ref: 490014267603
Ref: c-api/exceptions c PyErr_Clear14267660
Ref: fd414267660
Ref: c-api/exceptions c PyErr_PrintEx14267832
Ref: 47c214267832
Ref: c-api/exceptions c PyErr_Print14268767
Ref: 184714268767
Ref: c-api/exceptions c PyErr_WriteUnraisable14268887
Ref: 32814268887
Ref: c-api/exceptions c PyErr_FormatUnraisable14269871
Ref: 32714269871
Ref: c-api/exceptions c PyErr_DisplayException14270383
Ref: 3ca14270383
Node: Raising exceptions14270664
Ref: c-api/exceptions raising-exceptions14270786
Ref: 490114270786
Ref: c-api/exceptions c PyErr_SetString14271024
Ref: 52214271024
Ref: c-api/exceptions c PyErr_SetObject14271532
Ref: 52114271532
Ref: c-api/exceptions c PyErr_Format14271801
Ref: e5314271801
Ref: c-api/exceptions c PyErr_FormatV14272312
Ref: e5214272312
Ref: c-api/exceptions c PyErr_SetNone14272686
Ref: 47ca14272686
Ref: c-api/exceptions c PyErr_BadArgument14272853
Ref: 47bf14272853
Ref: c-api/exceptions c PyErr_NoMemory14273152
Ref: 46d314273152
Ref: c-api/exceptions c PyErr_SetFromErrno14273490
Ref: 46d214273490
Ref: c-api/exceptions c PyErr_SetFromErrnoWithFilenameObject14274424
Ref: 47c614274424
Ref: c-api/exceptions c PyErr_SetFromErrnoWithFilenameObjects14274964
Ref: 47c714274964
Ref: c-api/exceptions c PyErr_SetFromErrnoWithFilename14275441
Ref: 161414275441
Ref: c-api/exceptions c PyErr_SetFromWindowsErr14275839
Ref: 47c814275839
Ref: c-api/exceptions c PyErr_SetExcFromWindowsErr14276752
Ref: 47c314276752
Ref: c-api/exceptions c PyErr_SetFromWindowsErrWithFilename14277143
Ref: 161614277143
Ref: c-api/exceptions c PyErr_SetExcFromWindowsErrWithFilenameObject14277780
Ref: 47c414277780
Ref: c-api/exceptions c PyErr_SetExcFromWindowsErrWithFilenameObjects14278379
Ref: 47c514278379
Ref: c-api/exceptions c PyErr_SetExcFromWindowsErrWithFilename14278854
Ref: 161514278854
Ref: c-api/exceptions c PyErr_SetImportError14279291
Ref: ce514279291
Ref: c-api/exceptions c PyErr_SetImportErrorSubclass14279828
Ref: cbd14279828
Ref: c-api/exceptions c PyErr_SyntaxLocationObject14280252
Ref: 490214280252
Ref: c-api/exceptions c PyErr_SyntaxLocationEx14280660
Ref: 47cc14280660
Ref: c-api/exceptions c PyErr_SyntaxLocation14281019
Ref: 47cb14281019
Ref: c-api/exceptions c PyErr_BadInternalCall14281240
Ref: 47c014281240
Node: Issuing warnings14281584
Ref: c-api/exceptions issuing-warnings14281713
Ref: 490314281713
Ref: c-api/exceptions c PyErr_WarnEx14282608
Ref: 13b814282608
Ref: c-api/exceptions c PyErr_WarnExplicitObject14283791
Ref: 490514283791
Ref: c-api/exceptions c PyErr_WarnExplicit14284333
Ref: 161d14284333
Ref: c-api/exceptions c PyErr_WarnFormat14284769
Ref: 47cd14284769
Ref: c-api/exceptions c PyErr_ResourceWarning14285132
Ref: cbe14285132
Node: Querying the error indicator14285520
Ref: c-api/exceptions querying-the-error-indicator14285649
Ref: 490614285649
Ref: c-api/exceptions c PyErr_Occurred14285720
Ref: 17f414285720
Ref: c-api/exceptions c PyErr_ExceptionMatches14286597
Ref: 476a14286597
Ref: c-api/exceptions c PyErr_GivenExceptionMatches14286924
Ref: 47c114286924
Ref: c-api/exceptions c PyErr_GetRaisedException14287364
Ref: 3bc14287364
Ref: c-api/exceptions c PyErr_SetRaisedException14288215
Ref: 3bf14288215
Ref: c-api/exceptions c PyErr_Fetch14288586
Ref: 3bb14288586
Ref: c-api/exceptions c PyErr_Restore14289652
Ref: 3be14289652
Ref: c-api/exceptions c PyErr_NormalizeException14290817
Ref: 3bd14290817
Ref: c-api/exceptions c PyErr_GetHandledException14291874
Ref: 71314291874
Ref: c-api/exceptions c PyErr_SetHandledException14292685
Ref: 71414292685
Ref: c-api/exceptions c PyErr_GetExcInfo14293366
Ref: 71614293366
Ref: c-api/exceptions c PyErr_SetExcInfo14294344
Ref: 71514294344
Node: Signal Handling<2>14295527
Ref: c-api/exceptions signal-handling14295655
Ref: 490714295655
Ref: c-api/exceptions c PyErr_CheckSignals14295700
Ref: 40d14295700
Ref: c-api/exceptions c PyErr_SetInterrupt14296958
Ref: 47c914296958
Ref: c-api/exceptions c PyErr_SetInterruptEx14297313
Ref: 84214297313
Ref: c-api/exceptions c PySignal_SetWakeupFd14298398
Ref: 134914298398
Node: 例外類別<2>14299064
Ref: c-api/exceptions exception-classes14299176
Ref: 490814299176
Ref: c-api/exceptions c PyErr_NewException14299211
Ref: 120214299211
Ref: c-api/exceptions c PyErr_NewExceptionWithDoc14300200
Ref: 120114300200
Node: 例外物件14300659
Ref: c-api/exceptions exception-objects14300778
Ref: 490914300778
Ref: c-api/exceptions c PyException_GetTraceback14300813
Ref: 47d414300813
Ref: c-api/exceptions c PyException_SetTraceback14301208
Ref: 18ef14301208
Ref: c-api/exceptions c PyException_GetContext14301424
Ref: 47d314301424
Ref: c-api/exceptions c PyException_SetContext14301868
Ref: 47d614301868
Ref: c-api/exceptions c PyException_GetCause14302199
Ref: 47d214302199
Ref: c-api/exceptions c PyException_SetCause14302588
Ref: 47d514302588
Ref: c-api/exceptions c PyException_GetArgs14303053
Ref: 51014303053
Ref: c-api/exceptions c PyException_SetArgs14303275
Ref: 51114303275
Ref: c-api/exceptions c PyUnstable_Exc_PrepReraiseStar14303473
Ref: 490a14303473
Node: Unicode Exception Objects14304417
Ref: c-api/exceptions unicode-exception-objects14304538
Ref: 490b14304538
Ref: c-api/exceptions unicodeexceptions14304538
Ref: 490c14304538
Ref: c-api/exceptions c PyUnicodeDecodeError_Create14304685
Ref: 487614304685
Ref: c-api/exceptions c PyUnicodeDecodeError_GetEncoding14305158
Ref: 487714305158
Ref: c-api/exceptions c PyUnicodeEncodeError_GetEncoding14305253
Ref: 487f14305253
Ref: c-api/exceptions c PyUnicodeDecodeError_GetObject14305495
Ref: 487914305495
Ref: c-api/exceptions c PyUnicodeEncodeError_GetObject14305588
Ref: 488114305588
Ref: c-api/exceptions c PyUnicodeTranslateError_GetObject14305681
Ref: 488814305681
Ref: c-api/exceptions c PyUnicodeDecodeError_GetStart14305922
Ref: 487b14305922
Ref: c-api/exceptions c PyUnicodeEncodeError_GetStart14306015
Ref: 488314306015
Ref: c-api/exceptions c PyUnicodeTranslateError_GetStart14306108
Ref: 488a14306108
Ref: c-api/exceptions c PyUnicodeDecodeError_SetStart14306430
Ref: 487e14306430
Ref: c-api/exceptions c PyUnicodeEncodeError_SetStart14306522
Ref: 488614306522
Ref: c-api/exceptions c PyUnicodeTranslateError_SetStart14306614
Ref: 488d14306614
Ref: c-api/exceptions c PyUnicodeDecodeError_GetEnd14306886
Ref: 487814306886
Ref: c-api/exceptions c PyUnicodeEncodeError_GetEnd14306975
Ref: 488014306975
Ref: c-api/exceptions c PyUnicodeTranslateError_GetEnd14307064
Ref: 488714307064
Ref: c-api/exceptions c PyUnicodeDecodeError_SetEnd14307376
Ref: 487c14307376
Ref: c-api/exceptions c PyUnicodeEncodeError_SetEnd14307464
Ref: 488414307464
Ref: c-api/exceptions c PyUnicodeTranslateError_SetEnd14307552
Ref: 488b14307552
Ref: c-api/exceptions c PyUnicodeDecodeError_GetReason14307816
Ref: 487a14307816
Ref: c-api/exceptions c PyUnicodeEncodeError_GetReason14307909
Ref: 488214307909
Ref: c-api/exceptions c PyUnicodeTranslateError_GetReason14308002
Ref: 488914308002
Ref: c-api/exceptions c PyUnicodeDecodeError_SetReason14308243
Ref: 487d14308243
Ref: c-api/exceptions c PyUnicodeEncodeError_SetReason14308338
Ref: 488514308338
Ref: c-api/exceptions c PyUnicodeTranslateError_SetReason14308433
Ref: 488c14308433
Node: Recursion Control14308710
Ref: c-api/exceptions recursion14308838
Ref: 490d14308838
Ref: c-api/exceptions recursion-control14308838
Ref: 490e14308838
Ref: c-api/exceptions c Py_EnterRecursiveCall14309270
Ref: 91714309270
Ref: c-api/exceptions c Py_LeaveRecursiveCall14310193
Ref: 91814310193
Ref: c-api/exceptions c Py_ReprEnter14310908
Ref: 48bd14310908
Ref: c-api/exceptions c Py_ReprLeave14311717
Ref: 48be14311717
Node: Standard Exceptions14311954
Ref: c-api/exceptions standard-exceptions14312084
Ref: 490f14312084
Ref: c-api/exceptions standardexceptions14312084
Ref: 491014312084
Ref: Standard Exceptions-Footnote-114325240
Ref: Standard Exceptions-Footnote-214325300
Ref: Standard Exceptions-Footnote-314325360
Ref: Standard Exceptions-Footnote-414325420
Ref: Standard Exceptions-Footnote-514325480
Ref: Standard Exceptions-Footnote-614325540
Ref: Standard Exceptions-Footnote-714325582
Node: Standard Warning Categories14325711
Ref: c-api/exceptions standard-warning-categories14325815
Ref: 491114325815
Ref: c-api/exceptions standardwarningcategories14325815
Ref: 490414325815
Ref: Standard Warning Categories-Footnote-114328925
Node: 工具14328993
Ref: c-api/utilities doc14329129
Ref: 491214329129
Ref: c-api/utilities id114329129
Ref: 491314329129
Ref: c-api/utilities utilities14329129
Ref: 491414329129
Node: 作業系統工具14329694
Ref: c-api/sys doc14329776
Ref: 491514329776
Ref: c-api/sys operating-system-utilities14329776
Ref: 491614329776
Ref: c-api/sys os14329776
Ref: 491714329776
Ref: c-api/sys c PyOS_FSPath14329821
Ref: cbf14329821
Ref: c-api/sys c Py_FdIsInteractive14330461
Ref: 491814330461
Ref: c-api/sys c PyOS_BeforeFork14331004
Ref: b6614331004
Ref: c-api/sys c PyOS_AfterFork_Parent14331622
Ref: b6714331622
Ref: c-api/sys c PyOS_AfterFork_Child14332332
Ref: 3c314332332
Ref: c-api/sys c PyOS_AfterFork14333322
Ref: 3c214333322
Ref: c-api/sys c PyOS_CheckStack14333808
Ref: 171b14333808
Ref: c-api/sys c PyOS_sighandler_t14334323
Ref: 483014334323
Ref: c-api/sys c PyOS_getsig14334425
Ref: 14ac14334425
Ref: c-api/sys c PyOS_setsig14334714
Ref: 14ad14334714
Ref: c-api/sys c Py_DecodeLocale14335069
Ref: b6e14335069
Ref: c-api/sys c Py_EncodeLocale14337388
Ref: b6f14337388
Node: 系統函式14339152
Ref: c-api/sys system-functions14339255
Ref: 491a14339255
Ref: c-api/sys systemfunctions14339255
Ref: 491b14339255
Ref: c-api/sys c PySys_GetObject14339538
Ref: 35d14339538
Ref: c-api/sys c PySys_SetObject14339820
Ref: 486714339820
Ref: c-api/sys c PySys_ResetWarnOptions14340125
Ref: 37a14340125
Ref: c-api/sys c PySys_WriteStdout14340493
Ref: 486914340493
Ref: c-api/sys c PySys_WriteStderr14341396
Ref: 486814341396
Ref: c-api/sys c PySys_FormatStdout14341607
Ref: 486514341607
Ref: c-api/sys c PySys_FormatStderr14341924
Ref: 486414341924
Ref: c-api/sys c PySys_GetXOptions14342165
Ref: 486614342165
Ref: c-api/sys c PySys_Audit14342523
Ref: 32114342523
Ref: c-api/sys c PySys_AuditTuple14343852
Ref: 32014343852
Ref: c-api/sys c PySys_AddAuditHook14344196
Ref: 3ff214344196
Ref: c-api/sys c Py_AuditHookFunction14345813
Ref: 491c14345813
Ref: 系統函式-Footnote-114346320
Node: 行程控制14346362
Ref: c-api/sys process-control14346462
Ref: 491e14346462
Ref: c-api/sys processcontrol14346462
Ref: 491f14346462
Ref: c-api/sys c Py_FatalError14346497
Ref: 92714346497
Ref: c-api/sys c Py_Exit14347273
Ref: cf514347273
Ref: c-api/sys c Py_AtExit14347671
Ref: 48b214347671
Node: 引入模組<2>14348365
Ref: c-api/import doc14348477
Ref: 492014348477
Ref: c-api/import importing14348477
Ref: 492114348477
Ref: c-api/import importing-modules14348477
Ref: 492214348477
Ref: c-api/import c PyImport_ImportModule14348512
Ref: 38914348512
Ref: c-api/import c PyImport_ImportModuleNoBlock14348821
Ref: 38814348821
Ref: c-api/import c PyImport_ImportModuleEx14349483
Ref: 113d14349483
Ref: c-api/import c PyImport_ImportModuleLevelObject14350230
Ref: 47e914350230
Ref: c-api/import c PyImport_ImportModuleLevel14351071
Ref: 113c14351071
Ref: c-api/import c PyImport_Import14351542
Ref: 136a14351542
Ref: c-api/import c PyImport_ReloadModule14352114
Ref: 47ea14352114
Ref: c-api/import c PyImport_AddModuleRef14352432
Ref: 2ec14352432
Ref: c-api/import c PyImport_AddModuleObject14353427
Ref: 47e014353427
Ref: c-api/import c PyImport_AddModule14353798
Ref: 2ed14353798
Ref: c-api/import c PyImport_ExecCodeModule14354052
Ref: 47e114354052
Ref: c-api/import c PyImport_ExecCodeModuleEx14356053
Ref: 47e214356053
Ref: c-api/import c PyImport_ExecCodeModuleObject14356496
Ref: 47e314356496
Ref: c-api/import c PyImport_ExecCodeModuleWithPathnames14357146
Ref: 47e414357146
Ref: c-api/import c PyImport_GetMagicNumber14357906
Ref: 113b14357906
Ref: c-api/import c PyImport_GetMagicTag14358292
Ref: 47e514358292
Ref: c-api/import c PyImport_GetModuleDict14358643
Ref: 47e614358643
Ref: c-api/import c PyImport_GetModule14358926
Ref: b5a14358926
Ref: c-api/import c PyImport_GetImporter14359356
Ref: 161314359356
Ref: c-api/import c PyImport_ImportFrozenModuleObject14360072
Ref: 47e814360072
Ref: c-api/import c PyImport_ImportFrozenModule14360708
Ref: 47e714360708
Ref: c-api/import c _frozen14360961
Ref: 71914360961
Ref: c-api/import c PyImport_FrozenModules14361591
Ref: 2eeb14361591
Ref: c-api/import c PyImport_AppendInittab14362004
Ref: 16a614362004
Ref: c-api/import c _inittab14362589
Ref: 492314362589
Ref: c-api/import c _inittab name14362919
Ref: 492414362919
Ref: c-api/import c _inittab initfunc14363018
Ref: 492514363018
Ref: c-api/import c PyImport_ExtendInittab14363170
Ref: 16a714363170
Ref: 引入模組<2>-Footnote-114363979
Node: 資料 marshal 的支援14364021
Ref: c-api/marshal doc14364148
Ref: 492614364148
Ref: c-api/marshal data-marshalling-support14364148
Ref: 492714364148
Ref: c-api/marshal marshalling-utils14364148
Ref: 492814364148
Ref: c-api/marshal c PyMarshal_WriteLongToFile14364890
Ref: 73a14364890
Ref: c-api/marshal c PyMarshal_WriteObjectToFile14365325
Ref: 73b14365325
Ref: c-api/marshal c PyMarshal_WriteObjectToString14365651
Ref: 73d14365651
Ref: c-api/marshal c PyMarshal_ReadLongFromFile14365986
Ref: 492914365986
Ref: c-api/marshal c PyMarshal_ReadShortFromFile14366323
Ref: 492a14366323
Ref: c-api/marshal c PyMarshal_ReadObjectFromFile14366663
Ref: 492b14366663
Ref: c-api/marshal c PyMarshal_ReadLastObjectFromFile14367020
Ref: 492c14367020
Ref: c-api/marshal c PyMarshal_ReadObjectFromString14367808
Ref: 73c14367808
Node: 剖析引數與建置數值14368220
Ref: c-api/arg doc14368356
Ref: 492d14368356
Ref: c-api/arg arg-parsing14368356
Ref: 84d14368356
Ref: c-api/arg parsing-arguments-and-building-values14368356
Ref: 492e14368356
Node: Parsing arguments14368964
Ref: c-api/arg parsing-arguments14369069
Ref: 492f14369069
Node: Strings and buffers14369780
Ref: c-api/arg arg-parsing-string-and-buffers14369868
Ref: 2e814369868
Ref: c-api/arg strings-and-buffers14369868
Ref: 493014369868
Ref: c-api/arg c-arg-borrowed-buffer14371147
Ref: 493114371147
Node: 數字14380470
Ref: c-api/arg numbers14380579
Ref: 493214380579
Node: 其他物件14382726
Ref: c-api/arg other-objects14382826
Ref: 493414382826
Ref: c-api/arg o-ampersand14383642
Ref: 493514383642
Node: API 函式14388150
Ref: c-api/arg api-functions14388235
Ref: 493614388235
Ref: c-api/arg c PyArg_ParseTuple14388272
Ref: 51714388272
Ref: c-api/arg c PyArg_VaParse14388612
Ref: 477e14388612
Ref: c-api/arg c PyArg_ParseTupleAndKeywords14388887
Ref: 2e914388887
Ref: c-api/arg c PyArg_VaParseTupleAndKeywords14389990
Ref: 2ea14389990
Ref: c-api/arg c PyArg_ValidateKeywordArguments14390329
Ref: 477f14390329
Ref: c-api/arg c PyArg_Parse14390674
Ref: 18e914390674
Ref: c-api/arg c PyArg_UnpackTuple14391349
Ref: 147614391349
Ref: c-api/arg c PY_CXX_CONST14393334
Ref: 2eb14393334
Node: Building values14393754
Ref: c-api/arg building-values14393859
Ref: 493714393859
Ref: c-api/arg c Py_BuildValue14393908
Ref: 84c14393908
Ref: c-api/arg c Py_VaBuildValue14401629
Ref: 48c014401629
Node: 字串轉換與格式化14401934
Ref: c-api/conversion doc14402056
Ref: 493814402056
Ref: c-api/conversion string-conversion14402056
Ref: 493914402056
Ref: c-api/conversion string-conversion-and-formatting14402056
Ref: 493a14402056
Ref: c-api/conversion c PyOS_snprintf14402167
Ref: 147914402167
Ref: c-api/conversion c PyOS_vsnprintf14402462
Ref: 147a14402462
Ref: c-api/conversion c PyOS_strtoul14404115
Ref: 483214404115
Ref: c-api/conversion c PyOS_strtol14405151
Ref: 483114405151
Ref: c-api/conversion c PyOS_string_to_double14405674
Ref: 122d14405674
Ref: c-api/conversion c PyOS_double_to_string14407269
Ref: 482f14407269
Ref: c-api/conversion c PyOS_stricmp14408817
Ref: 493b14408817
Ref: c-api/conversion c PyOS_strnicmp14409013
Ref: 493c14409013
Ref: 字串轉換與格式化-Footnote-114409274
Ref: 字串轉換與格式化-Footnote-214409322
Ref: 字串轉換與格式化-Footnote-314409371
Ref: 字串轉換與格式化-Footnote-414409418
Node: PyHash API14409464
Ref: c-api/hash doc14409569
Ref: 493d14409569
Ref: c-api/hash pyhash-api14409569
Ref: 493e14409569
Ref: c-api/hash c Py_hash_t14409698
Ref: 11fc14409698
Ref: c-api/hash c Py_uhash_t14409799
Ref: 493f14409799
Ref: c-api/hash c PyHASH_MODULUS14409901
Ref: 155f14409901
Ref: c-api/hash c PyHASH_BITS14410037
Ref: 156014410037
Ref: c-api/hash c PyHASH_MULTIPLIER14410162
Ref: 151614410162
Ref: c-api/hash c PyHASH_INF14410288
Ref: 156114410288
Ref: c-api/hash c PyHASH_IMAG14410398
Ref: 156214410398
Ref: c-api/hash c PyHash_FuncDef14410524
Ref: 494014410524
Ref: c-api/hash c PyHash_FuncDef name14410632
Ref: 494214410632
Ref: c-api/hash c PyHash_FuncDef hash_bits14410732
Ref: 494314410732
Ref: c-api/hash c PyHash_FuncDef seed_bits14410841
Ref: 494414410841
Ref: c-api/hash c PyHash_GetFuncDef14410974
Ref: 494114410974
Ref: c-api/hash c Py_HashPointer14411250
Ref: 32e14411250
Ref: c-api/hash c PyObject_GenericHash14411557
Ref: 32f14411557
Ref: PyHash API-Footnote-114411952
Ref: PyHash API-Footnote-214412005
Node: Reflection14412047
Ref: c-api/reflection doc14412164
Ref: 494514412164
Ref: c-api/reflection id114412164
Ref: 494614412164
Ref: c-api/reflection reflection14412164
Ref: 494714412164
Ref: c-api/reflection c PyEval_GetBuiltins14412199
Ref: 34814412199
Ref: c-api/reflection c PyEval_GetLocals14412589
Ref: 34a14412589
Ref: c-api/reflection c PyEval_GetGlobals14414110
Ref: 34914414110
Ref: c-api/reflection c PyEval_GetFrame14414476
Ref: 16bf14414476
Ref: c-api/reflection c PyEval_GetFrameBuiltins14414782
Ref: 34514414782
Ref: c-api/reflection c PyEval_GetFrameLocals14415139
Ref: 34714415139
Ref: c-api/reflection c PyEval_GetFrameGlobals14415764
Ref: 34614415764
Ref: c-api/reflection c PyEval_GetFuncName14416164
Ref: 47d014416164
Ref: c-api/reflection c PyEval_GetFuncDesc14416390
Ref: 47cf14416390
Ref: Reflection-Footnote-114416829
Node: 編解碼器註冊表和支援函式14416871
Ref: c-api/codec doc14416990
Ref: 494814416990
Ref: c-api/codec codec-registry14416990
Ref: cdc14416990
Ref: c-api/codec codec-registry-and-support-functions14416990
Ref: 494914416990
Ref: c-api/codec c PyCodec_Register14417067
Ref: 47a614417067
Ref: c-api/codec c PyCodec_Unregister14417392
Ref: 83b14417392
Ref: c-api/codec c PyCodec_KnownEncoding14417775
Ref: 47a414417775
Ref: c-api/codec c PyCodec_Encode14418020
Ref: 3c814418020
Ref: c-api/codec c PyCodec_Decode14418560
Ref: 3c714418560
Node: 編解碼器查找 API14419194
Ref: c-api/codec codec-lookup-api14419350
Ref: 494a14419350
Ref: c-api/codec c PyCodec_Encoder14419664
Ref: 47a014419664
Ref: c-api/codec c PyCodec_Decoder14419869
Ref: 479f14419869
Ref: c-api/codec c PyCodec_IncrementalEncoder14420074
Ref: 47a314420074
Ref: c-api/codec c PyCodec_IncrementalDecoder14420344
Ref: 47a214420344
Ref: c-api/codec c PyCodec_StreamReader14420614
Ref: 47a914420614
Ref: c-api/codec c PyCodec_StreamWriter14420896
Ref: 47aa14420896
Node: 用於 Unicode 編碼錯誤處理程式的註冊 API14421178
Ref: c-api/codec registry-api-for-unicode-encoding-error-handlers14421334
Ref: 494b14421334
Ref: c-api/codec c PyCodec_RegisterError14421446
Ref: 47a714421446
Ref: c-api/codec c PyCodec_LookupError14422480
Ref: 47a514422480
Ref: c-api/codec c PyCodec_StrictErrors14422818
Ref: 47ab14422818
Ref: c-api/codec c PyCodec_IgnoreErrors14423006
Ref: 47a114423006
Ref: c-api/codec c PyCodec_ReplaceErrors14423212
Ref: 47a814423212
Ref: c-api/codec c PyCodec_XMLCharRefReplaceErrors14423432
Ref: 47ac14423432
Ref: c-api/codec c PyCodec_BackslashReplaceErrors14423664
Ref: 479e14423664
Ref: c-api/codec c PyCodec_NameReplaceErrors14423931
Ref: e5114423931
Node: PyTime C API14424212
Ref: c-api/time doc14424343
Ref: 13f14424343
Ref: c-api/time pytime-c-api14424343
Ref: 494c14424343
Node: Types14424688
Ref: c-api/time types14424766
Ref: 494e14424766
Ref: c-api/time c PyTime_t14424797
Ref: 33014424797
Ref: c-api/time c PyTime_MIN14425324
Ref: 33114425324
Ref: c-api/time c PyTime_MAX14425415
Ref: 33214425415
Node: Clock Functions14425506
Ref: c-api/time clock-functions14425612
Ref: 494f14425612
Ref: c-api/time c PyTime_Monotonic14426319
Ref: 33414426319
Ref: c-api/time c PyTime_PerfCounter14426482
Ref: 33614426482
Ref: c-api/time c PyTime_Time14426654
Ref: 33814426654
Node: Raw Clock Functions14426813
Ref: c-api/time raw-clock-functions14426934
Ref: 495014426934
Ref: c-api/time c PyTime_MonotonicRaw14427418
Ref: 33514427418
Ref: c-api/time c PyTime_PerfCounterRaw14427600
Ref: 33714427600
Ref: c-api/time c PyTime_TimeRaw14427786
Ref: 33914427786
Node: Conversion functions14427958
Ref: c-api/time conversion-functions14428055
Ref: 495114428055
Ref: c-api/time c PyTime_AsSecondsDouble14428116
Ref: 33314428116
Node: 對 Perf Map 的支援14428335
Ref: c-api/perfmaps doc14428421
Ref: 495214428421
Ref: c-api/perfmaps perfmaps14428421
Ref: 495314428421
Ref: c-api/perfmaps support-for-perf-maps14428421
Ref: 495414428421
Ref: c-api/perfmaps c PyUnstable_PerfMapState_Init14429068
Ref: 163914429068
Ref: c-api/perfmaps c PyUnstable_WritePerfMapEntry14429910
Ref: 163814429910
Ref: c-api/perfmaps c PyUnstable_PerfMapState_Fini14430709
Ref: 163a14430709
Ref: 對 Perf Map 的支援-Footnote-114431247
Ref: 對 Perf Map 的支援-Footnote-214431304
Node: 抽象物件層 Abstract Objects Layer14431428
Ref: c-api/abstract doc14431567
Ref: 495514431567
Ref: c-api/abstract abstract14431567
Ref: 472814431567
Ref: c-api/abstract abstract-objects-layer14431567
Ref: 495614431567
Node: 物件協定14432323
Ref: c-api/object doc14432445
Ref: 495714432445
Ref: c-api/object object14432445
Ref: 495814432445
Ref: c-api/object object-protocol14432445
Ref: 495914432445
Ref: c-api/object c Py_GetConstant14432480
Ref: 34014432480
Ref: c-api/object c Py_CONSTANT_NONE14433157
Ref: 495a14433157
Ref: c-api/object c Py_CONSTANT_FALSE14433363
Ref: 495b14433363
Ref: c-api/object c Py_CONSTANT_TRUE14433568
Ref: 495c14433568
Ref: c-api/object c Py_CONSTANT_ELLIPSIS14433777
Ref: 495d14433777
Ref: c-api/object c Py_CONSTANT_NOT_IMPLEMENTED14433994
Ref: 495e14433994
Ref: c-api/object c Py_CONSTANT_ZERO14434198
Ref: 495f14434198
Ref: c-api/object c Py_CONSTANT_ONE14434393
Ref: 496014434393
Ref: c-api/object c Py_CONSTANT_EMPTY_STR14434595
Ref: 496114434595
Ref: c-api/object c Py_CONSTANT_EMPTY_BYTES14434794
Ref: 496214434794
Ref: c-api/object c Py_CONSTANT_EMPTY_TUPLE14434992
Ref: 496314434992
Ref: c-api/object c Py_GetConstantBorrowed14435311
Ref: 34114435311
Ref: c-api/object c Py_NotImplemented14435851
Ref: 496414435851
Ref: c-api/object c Py_RETURN_NOTIMPLEMENTED14436037
Ref: 496514436037
Ref: c-api/object c Py_PRINT_RAW14436273
Ref: 496614436273
Ref: c-api/object c PyObject_Print14436567
Ref: 14e414436567
Ref: c-api/object c PyObject_HasAttrWithError14436947
Ref: 2fc14436947
Ref: c-api/object c PyObject_HasAttrStringWithError14437336
Ref: 2fe14437336
Ref: c-api/object c PyObject_HasAttr14437721
Ref: 2fd14437721
Ref: c-api/object c PyObject_HasAttrString14438312
Ref: 2ff14438312
Ref: c-api/object c PyObject_GetAttr14439062
Ref: 2f414439062
Ref: c-api/object c PyObject_GetAttrString14439578
Ref: 2f514439578
Ref: c-api/object c PyObject_GetOptionalAttr14440078
Ref: 2f214440078
Ref: c-api/object c PyObject_GetOptionalAttrString14440802
Ref: 2f314440802
Ref: c-api/object c PyObject_GenericGetAttr14441207
Ref: 483a14441207
Ref: c-api/object c PyObject_SetAttr14441874
Ref: 484214441874
Ref: c-api/object c PyObject_SetAttrString14442458
Ref: 14f414442458
Ref: c-api/object c PyObject_GenericSetAttr14443390
Ref: 483b14443390
Ref: c-api/object c PyObject_DelAttr14444088
Ref: 161a14444088
Ref: c-api/object c PyObject_DelAttrString14444399
Ref: 14f514444399
Ref: c-api/object c PyObject_GenericGetDict14445205
Ref: 183c14445205
Ref: c-api/object c PyObject_GenericSetDict14445953
Ref: 483c14445953
Ref: c-api/object c _PyObject_GetDictPtr14446299
Ref: 496714446299
Ref: c-api/object c PyObject_RichCompare14446715
Ref: 472614446715
Ref: c-api/object c PyObject_RichCompareBool14447441
Ref: 18a714447441
Ref: c-api/object c PyObject_Format14447985
Ref: 483914447985
Ref: c-api/object c PyObject_Repr14448430
Ref: fd214448430
Ref: c-api/object c PyObject_ASCII14448975
Ref: 483314448975
Ref: c-api/object c PyObject_Str14449511
Ref: fd314449511
Ref: c-api/object c PyObject_Bytes14450110
Ref: 483514450110
Ref: c-api/object c PyObject_IsSubclass14450592
Ref: e4914450592
Ref: c-api/object c PyObject_IsInstance14451606
Ref: e4814451606
Ref: c-api/object c PyObject_Hash14452631
Ref: 3cb14452631
Ref: c-api/object c PyObject_HashNotImplemented14453040
Ref: 133414453040
Ref: c-api/object c PyObject_IsTrue14453468
Ref: 483f14453468
Ref: c-api/object c PyObject_Not14453751
Ref: 484114453751
Ref: c-api/object c PyObject_Type14454027
Ref: 484414454027
Ref: c-api/object c PyObject_TypeCheck14454726
Ref: 17fa14454726
Ref: c-api/object c PyObject_Size14454949
Ref: 484314454949
Ref: c-api/object c PyObject_Length14455014
Ref: 484014455014
Ref: c-api/object c PyObject_LengthHint14455384
Ref: fa514455384
Ref: c-api/object c PyObject_GetItem14455843
Ref: 2f914455843
Ref: c-api/object c PyObject_SetItem14456169
Ref: 476414456169
Ref: c-api/object c PyObject_DelItem14456557
Ref: 483714456557
Ref: c-api/object c PyObject_Dir14456833
Ref: 483814456833
Ref: c-api/object c PyObject_GetIter14457421
Ref: 483e14457421
Ref: c-api/object c PyObject_GetAIter14457844
Ref: 483d14457844
Ref: c-api/object c PyObject_GetTypeData14458401
Ref: 4ef14458401
Ref: c-api/object c PyType_GetTypeDataSize14458869
Ref: 4f014458869
Ref: c-api/object c PyObject_GetItemData14459556
Ref: 4f214459556
Ref: c-api/object c PyObject_VisitManagedDict14459897
Ref: 31914459897
Ref: c-api/object c PyObject_ClearManagedDict14460210
Ref: 31a14460210
Ref: 物件協定-Footnote-114460522
Ref: 物件協定-Footnote-214460564
Node: 呼叫協定 Call Protocol14460606
Ref: c-api/call doc14460749
Ref: 496e14460749
Ref: c-api/call call14460749
Ref: 52914460749
Ref: c-api/call call-protocol14460749
Ref: 496f14460749
Node: tp_call 協定14461000
Ref: c-api/call the-tp-call-protocol14461103
Ref: 497014461103
Node: Vectorcall 協定14461865
Ref: c-api/call the-vectorcall-protocol14461993
Ref: 497214461993
Ref: c-api/call vectorcall14461993
Ref: 4f814461993
Ref: c-api/call c vectorcallfunc14463755
Ref: 4fd14463755
Ref: c-api/call c PY_VECTORCALL_ARGUMENTS_OFFSET14464820
Ref: 50314464820
Ref: Vectorcall 協定-Footnote-114465993
Node: 遞迴控制14466035
Ref: c-api/call recursion-control14466131
Ref: 497414466131
Node: Vectorcall 支援 API14466528
Ref: c-api/call vectorcall-support-api14466624
Ref: 497514466624
Ref: c-api/call c PyVectorcall_NARGS14466683
Ref: 4fb14466683
Ref: c-api/call c PyVectorcall_Function14467102
Ref: 497614467102
Ref: c-api/call c PyVectorcall_Call14467598
Ref: 4fc14467598
Node: 物件呼叫 API14468205
Ref: c-api/call capi-call14468335
Ref: 497114468335
Ref: c-api/call object-calling-api14468335
Ref: 497714468335
Ref: c-api/call c PyObject_Call14472932
Ref: 36314472932
Ref: c-api/call c PyObject_CallNoArgs14473596
Ref: 36214473596
Ref: c-api/call c PyObject_CallOneArg14474054
Ref: 91c14474054
Ref: c-api/call c PyObject_CallObject14474427
Ref: 46e214474427
Ref: c-api/call c PyObject_CallFunction14474922
Ref: 36514474922
Ref: c-api/call c PyObject_CallMethod14475738
Ref: 36614475738
Ref: c-api/call c PyObject_CallFunctionObjArgs14476593
Ref: 483614476593
Ref: c-api/call c PyObject_CallMethodObjArgs14477121
Ref: 190214477121
Ref: c-api/call c PyObject_CallMethodNoArgs14477672
Ref: 497814477672
Ref: c-api/call c PyObject_CallMethodOneArg14478039
Ref: 497914478039
Ref: c-api/call c PyObject_Vectorcall14478432
Ref: 50114478432
Ref: c-api/call c PyObject_VectorcallDict14479014
Ref: 497a14479014
Ref: c-api/call c PyObject_VectorcallMethod14479662
Ref: 50214479662
Node: 呼叫支援 API14480745
Ref: c-api/call call-support-api14480849
Ref: 497c14480849
Ref: c-api/call c PyCallable_Check14480896
Ref: 479414480896
Node: 數字協定14481161
Ref: c-api/number doc14481304
Ref: 497d14481304
Ref: c-api/number number14481304
Ref: 497e14481304
Ref: c-api/number number-protocol14481304
Ref: 497f14481304
Ref: c-api/number c PyNumber_Check14481339
Ref: a0914481339
Ref: c-api/number c PyNumber_Add14481633
Ref: 481214481633
Ref: c-api/number c PyNumber_Subtract14481944
Ref: 482c14481944
Ref: c-api/number c PyNumber_Multiply14482265
Ref: 482514482265
Ref: c-api/number c PyNumber_MatrixMultiply14482585
Ref: e5714482585
Ref: c-api/number c PyNumber_FloorDivide14482981
Ref: 481614482981
Ref: c-api/number c PyNumber_TrueDivide14483299
Ref: 482d14483299
Ref: c-api/number c PyNumber_Remainder14483906
Ref: 482a14483906
Ref: c-api/number c PyNumber_Divmod14484227
Ref: 481514484227
Ref: c-api/number c PyNumber_Power14484562
Ref: 482914484562
Ref: c-api/number c PyNumber_Negative14485076
Ref: 482614485076
Ref: c-api/number c PyNumber_Positive14485358
Ref: 482814485358
Ref: c-api/number c PyNumber_Absolute14485624
Ref: 481114485624
Ref: c-api/number c PyNumber_Invert14485905
Ref: 482314485905
Ref: c-api/number c PyNumber_Lshift14486193
Ref: 482414486193
Ref: c-api/number c PyNumber_Rshift14486530
Ref: 482b14486530
Ref: c-api/number c PyNumber_And14486868
Ref: 481314486868
Ref: c-api/number c PyNumber_Xor14487195
Ref: 482e14487195
Ref: c-api/number c PyNumber_Or14487530
Ref: 482714487530
Ref: c-api/number c PyNumber_InPlaceAdd14487849
Ref: 481714487849
Ref: c-api/number c PyNumber_InPlaceSubtract14488229
Ref: 482014488229
Ref: c-api/number c PyNumber_InPlaceMultiply14488619
Ref: 481b14488619
Ref: c-api/number c PyNumber_InPlaceMatrixMultiply14489009
Ref: e5814489009
Ref: c-api/number c PyNumber_InPlaceFloorDivide14489474
Ref: 481914489474
Ref: c-api/number c PyNumber_InPlaceTrueDivide14489875
Ref: 482114489875
Ref: c-api/number c PyNumber_InPlaceRemainder14490551
Ref: 481e14490551
Ref: c-api/number c PyNumber_InPlacePower14490941
Ref: 481d14490941
Ref: c-api/number c PyNumber_InPlaceLshift14491587
Ref: 481a14491587
Ref: c-api/number c PyNumber_InPlaceRshift14491987
Ref: 481f14491987
Ref: c-api/number c PyNumber_InPlaceAnd14492388
Ref: 481814492388
Ref: c-api/number c PyNumber_InPlaceXor14492778
Ref: 482214492778
Ref: c-api/number c PyNumber_InPlaceOr14493176
Ref: 481c14493176
Ref: c-api/number c PyNumber_Long14493564
Ref: a0a14493564
Ref: c-api/number c PyNumber_Float14493870
Ref: a0b14493870
Ref: c-api/number c PyNumber_Index14494176
Ref: 83714494176
Ref: c-api/number c PyNumber_ToBase14494622
Ref: 16ef14494622
Ref: c-api/number c PyNumber_AsSsize_t14495143
Ref: 481414495143
Ref: c-api/number c PyIndex_Check14495955
Ref: 92e14495955
Node: 序列協定14496263
Ref: c-api/sequence doc14496392
Ref: 498014496392
Ref: c-api/sequence sequence14496392
Ref: 498114496392
Ref: c-api/sequence sequence-protocol14496392
Ref: 498214496392
Ref: c-api/sequence c PySequence_Check14496427
Ref: 484814496427
Ref: c-api/sequence c PySequence_Size14496887
Ref: 195814496887
Ref: c-api/sequence c PySequence_Length14496954
Ref: 485214496954
Ref: c-api/sequence c PySequence_Concat14497225
Ref: 484914497225
Ref: c-api/sequence c PySequence_Repeat14497551
Ref: 485414497551
Ref: c-api/sequence c PySequence_InPlaceConcat14497899
Ref: 484f14497899
Ref: c-api/sequence c PySequence_InPlaceRepeat14498295
Ref: 485014498295
Ref: c-api/sequence c PySequence_GetItem14498706
Ref: 195914498706
Ref: c-api/sequence c PySequence_GetSlice14499008
Ref: 484e14499008
Ref: c-api/sequence c PySequence_SetItem14499366
Ref: 195a14499366
Ref: c-api/sequence c PySequence_DelItem14499907
Ref: 195b14499907
Ref: c-api/sequence c PySequence_SetSlice14500166
Ref: 485514500166
Ref: c-api/sequence c PySequence_DelSlice14500485
Ref: 484c14500485
Ref: c-api/sequence c PySequence_Count14500794
Ref: 484b14500794
Ref: c-api/sequence c PySequence_Contains14501171
Ref: 484a14501171
Ref: c-api/sequence c PySequence_Index14501513
Ref: 485114501513
Ref: c-api/sequence c PySequence_List14501821
Ref: 485314501821
Ref: c-api/sequence c PySequence_Tuple14502187
Ref: 485614502187
Ref: c-api/sequence c PySequence_Fast14502646
Ref: 484d14502646
Ref: c-api/sequence c PySequence_Fast_GET_SIZE14503391
Ref: 498414503391
Ref: c-api/sequence c PySequence_Fast_GET_ITEM14503810
Ref: 498514503810
Ref: c-api/sequence c PySequence_Fast_ITEMS14504107
Ref: 498614504107
Ref: c-api/sequence c PySequence_ITEM14504521
Ref: 498714504521
Node: 對映協定14504888
Ref: c-api/mapping doc14505020
Ref: 498814505020
Ref: c-api/mapping mapping14505020
Ref: 498914505020
Ref: c-api/mapping mapping-protocol14505020
Ref: 498a14505020
Ref: c-api/mapping c PyMapping_Check14505173
Ref: 480114505173
Ref: c-api/mapping c PyMapping_Size14505584
Ref: 195c14505584
Ref: c-api/mapping c PyMapping_Length14505650
Ref: 480214505650
Ref: c-api/mapping c PyMapping_GetItemString14505893
Ref: 2fa14505893
Ref: c-api/mapping c PyMapping_GetOptionalItem14506230
Ref: 2f714506230
Ref: c-api/mapping c PyMapping_GetOptionalItemString14506917
Ref: 2f814506917
Ref: c-api/mapping c PyMapping_SetItemString14507311
Ref: 480314507311
Ref: c-api/mapping c PyMapping_DelItem14507616
Ref: 498b14507616
Ref: c-api/mapping c PyMapping_DelItemString14507740
Ref: 498c14507740
Ref: c-api/mapping c PyMapping_HasKeyWithError14507973
Ref: 30014507973
Ref: c-api/mapping c PyMapping_HasKeyStringWithError14508332
Ref: 30214508332
Ref: c-api/mapping c PyMapping_HasKey14508705
Ref: 30114508705
Ref: c-api/mapping c PyMapping_HasKeyString14509297
Ref: 30314509297
Ref: c-api/mapping c PyMapping_Keys14509968
Ref: b6314509968
Ref: c-api/mapping c PyMapping_Values14510278
Ref: b6414510278
Ref: c-api/mapping c PyMapping_Items14510581
Ref: b6514510581
Node: 疊代器協議14510946
Ref: c-api/iter doc14511094
Ref: 498d14511094
Ref: c-api/iter iterator14511094
Ref: 498e14511094
Ref: c-api/iter iterator-protocol14511094
Ref: 498f14511094
Ref: c-api/iter c PyIter_Check14511178
Ref: 17f714511178
Ref: c-api/iter c PyAIter_Check14511458
Ref: 477d14511458
Ref: c-api/iter c PyIter_Next14511745
Ref: 47ed14511745
Ref: c-api/iter c PySendResult14512728
Ref: 499014512728
Ref: c-api/iter c PyIter_Send14512871
Ref: 83c14512871
Node: 緩衝協定 Buffer Protocol14513487
Ref: c-api/buffer doc14513614
Ref: 499114513614
Ref: c-api/buffer buffer-protocol14513614
Ref: 499214513614
Ref: c-api/buffer bufferobjects14513614
Ref: 36714513614
Node: Buffer structure14516155
Ref: c-api/buffer buffer-structure14516265
Ref: 499414516265
Ref: c-api/buffer id114516265
Ref: 499514516265
Ref: c-api/buffer c Py_buffer14517336
Ref: 6fc14517336
Ref: c-api/buffer c Py_buffer buf14517466
Ref: 499714517466
Ref: c-api/buffer c Py_buffer obj14517934
Ref: 499914517934
Ref: c-api/buffer c Py_buffer len14518577
Ref: 499a14518577
Ref: c-api/buffer c Py_buffer readonly14519195
Ref: 499c14519195
Ref: c-api/buffer c Py_buffer itemsize14519371
Ref: 499d14519371
Ref: c-api/buffer c Py_buffer format14520306
Ref: 499e14520306
Ref: c-api/buffer c Py_buffer ndim14520634
Ref: 49a114520634
Ref: c-api/buffer c Py_buffer shape14521064
Ref: 49a014521064
Ref: c-api/buffer c Py_buffer strides14521635
Ref: 499814521635
Ref: c-api/buffer c Py_buffer suboffsets14522179
Ref: 49a214522179
Ref: c-api/buffer c Py_buffer internal14523089
Ref: 49a514523089
Ref: c-api/buffer c PyBUF_MAX_NDIM14523481
Ref: 49a314523481
Node: Buffer request types14523748
Ref: c-api/buffer buffer-request-types14523881
Ref: 42b914523881
Ref: c-api/buffer id214523881
Ref: 49a614523881
Node: request-independent fields14524489
Ref: c-api/buffer request-independent-fields14524596
Ref: 49a714524596
Node: readonly format14524864
Ref: c-api/buffer readonly-format14525004
Ref: 49a814525004
Ref: c-api/buffer c PyBUF_WRITABLE14525055
Ref: 132814525055
Ref: c-api/buffer c PyBUF_FORMAT14525389
Ref: 499f14525389
Node: shape strides suboffsets14525967
Ref: c-api/buffer shape-strides-suboffsets14526100
Ref: 49a914526100
Ref: c-api/buffer c PyBUF_INDIRECT14526638
Ref: 49aa14526638
Ref: c-api/buffer c PyBUF_STRIDES14526831
Ref: 49ab14526831
Ref: c-api/buffer c PyBUF_ND14527015
Ref: 49ac14527015
Ref: c-api/buffer c PyBUF_SIMPLE14527208
Ref: 499b14527208
Node: contiguity requests14527311
Ref: c-api/buffer contiguity-requests14527446
Ref: 49ad14527446
Ref: c-api/buffer c PyBUF_C_CONTIGUOUS14528056
Ref: 132914528056
Ref: c-api/buffer c PyBUF_F_CONTIGUOUS14528311
Ref: 132a14528311
Ref: c-api/buffer c PyBUF_ANY_CONTIGUOUS14528568
Ref: 49ae14528568
Node: compound requests14528965
Ref: c-api/buffer compound-requests14529067
Ref: 49af14529067
Ref: c-api/buffer c PyBUF_FULL14529942
Ref: 49b014529942
Ref: c-api/buffer c PyBUF_FULL_RO14530274
Ref: 49b114530274
Ref: c-api/buffer c PyBUF_RECORDS14530604
Ref: 49b214530604
Ref: c-api/buffer c PyBUF_RECORDS_RO14530936
Ref: 49b314530936
Ref: c-api/buffer c PyBUF_STRIDED14531263
Ref: 49b414531263
Ref: c-api/buffer c PyBUF_STRIDED_RO14531596
Ref: 49b514531596
Ref: c-api/buffer c PyBUF_CONTIG14531923
Ref: 49b614531923
Ref: c-api/buffer c PyBUF_CONTIG_RO14532256
Ref: 49b714532256
Node: Complex arrays14532451
Ref: c-api/buffer complex-arrays14532592
Ref: 49a414532592
Node: NumPy-style shape and strides14532798
Ref: c-api/buffer numpy-style-shape-and-strides14532925
Ref: 49b814532925
Node: PIL-style shape strides and suboffsets14534805
Ref: c-api/buffer pil-style-shape-strides-and-suboffsets14534932
Ref: 49b914534932
Node: Buffer-related functions14536158
Ref: c-api/buffer buffer-related-functions14536270
Ref: 49ba14536270
Ref: c-api/buffer c PyObject_CheckBuffer14536339
Ref: 36814536339
Ref: c-api/buffer c PyObject_GetBuffer14536687
Ref: 36914536687
Ref: c-api/buffer c PyBuffer_Release14537703
Ref: 36a14537703
Ref: c-api/buffer c PyBuffer_SizeFromFormat14538235
Ref: 6fe14538235
Ref: c-api/buffer c PyBuffer_IsContiguous14538549
Ref: 70214538549
Ref: c-api/buffer c PyBuffer_GetPointer14538974
Ref: 6fd14538974
Ref: c-api/buffer c PyBuffer_FromContiguous14539293
Ref: 70014539293
Ref: c-api/buffer c PyBuffer_ToContiguous14539682
Ref: 6ff14539682
Ref: c-api/buffer c PyObject_CopyData14540166
Ref: 70114540166
Ref: c-api/buffer c PyBuffer_FillContiguousStrides14540472
Ref: 70314540472
Ref: c-api/buffer c PyBuffer_FillInfo14540919
Ref: 70414540919
Node: 具體物件層14541955
Ref: c-api/concrete doc14542127
Ref: 49bb14542127
Ref: c-api/concrete concrete14542127
Ref: 49bc14542127
Ref: c-api/concrete concrete-objects-layer14542127
Ref: 49bd14542127
Node: 基礎物件14542964
Ref: c-api/concrete fundamental14543049
Ref: 49bf14543049
Ref: c-api/concrete fundamental-objects14543049
Ref: 49c014543049
Node: 型別物件14543206
Ref: c-api/type doc14543287
Ref: 49c114543287
Ref: c-api/type type-objects14543287
Ref: 49c214543287
Ref: c-api/type typeobjects14543287
Ref: 49c314543287
Ref: c-api/type c PyTypeObject14543326
Ref: a4814543326
Ref: c-api/type c PyType_Type14543533
Ref: 4f314543533
Ref: c-api/type c PyType_Check14543749
Ref: 18a214543749
Ref: c-api/type c PyType_CheckExact14543993
Ref: 18a314543993
Ref: c-api/type c PyType_ClearCache14544220
Ref: 487314544220
Ref: c-api/type c PyType_GetFlags14544389
Ref: 185614544389
Ref: c-api/type c PyType_GetDict14544935
Ref: 161b14544935
Ref: c-api/type c PyType_Modified14545658
Ref: 16f714545658
Ref: c-api/type c PyType_AddWatcher14545961
Ref: 50a14545961
Ref: c-api/type c PyType_ClearWatcher14546315
Ref: 49c414546315
Ref: c-api/type c PyType_Watch14546784
Ref: 50b14546784
Ref: c-api/type c PyType_WatchCallback14547485
Ref: 49c514547485
Ref: c-api/type c PyType_HasFeature14547842
Ref: 185514547842
Ref: c-api/type c PyType_IS_GC14548035
Ref: 49c614548035
Ref: c-api/type c PyType_IsSubtype14548224
Ref: 487414548224
Ref: c-api/type c PyType_GenericAlloc14548630
Ref: a0e14548630
Ref: c-api/type c PyType_GenericNew14549023
Ref: 470114549023
Ref: c-api/type c PyType_Ready14549363
Ref: 72214549363
Ref: c-api/type c PyType_GetName14550261
Ref: 6f614550261
Ref: c-api/type c PyType_GetQualName14550559
Ref: 6f714550559
Ref: c-api/type c PyType_GetFullyQualifiedName14550885
Ref: 33d14550885
Ref: c-api/type c PyType_GetModuleName14551302
Ref: 33e14551302
Ref: c-api/type c PyType_GetSlot14551593
Ref: 84014551593
Ref: c-api/type c PyType_GetModule14552292
Ref: 91214552292
Ref: c-api/type c PyType_GetModuleState14553240
Ref: 91314553240
Ref: c-api/type c PyType_GetModuleByDef14553839
Ref: 34214553839
Ref: c-api/type c PyUnstable_Type_AssignVersionTag14554593
Ref: 49c914554593
Node: Creating Heap-Allocated Types14555129
Ref: c-api/type creating-heap-allocated-types14555207
Ref: 49ca14555207
Ref: c-api/type c PyType_FromMetaclass14555363
Ref: 4f614555363
Ref: c-api/type c PyType_FromModuleAndSpec14557792
Ref: 4f714557792
Ref: c-api/type c PyType_FromSpecWithBases14558697
Ref: 52414558697
Ref: c-api/type c PyType_FromSpec14559442
Ref: 52314559442
Ref: c-api/type c PyType_Spec14560124
Ref: 161814560124
Ref: c-api/type c PyType_Spec name14560274
Ref: 49cb14560274
Ref: c-api/type c PyType_Spec basicsize14560402
Ref: 4ee14560402
Ref: c-api/type c PyType_Spec itemsize14561021
Ref: 49cc14561021
Ref: c-api/type c PyType_Spec flags14562148
Ref: 49cd14562148
Ref: c-api/type c PyType_Spec slots14562396
Ref: 49ce14562396
Ref: c-api/type c PyType_Slot14562634
Ref: 487514562634
Ref: c-api/type c PyType_Slot slot14562846
Ref: 49c714562846
Ref: c-api/type c PyType_Slot pfunc14565424
Ref: 49d814565424
Node: None 物件14565630
Ref: c-api/none doc14565711
Ref: 49d914565711
Ref: c-api/none noneobject14565711
Ref: 49da14565711
Ref: c-api/none the-none-object14565711
Ref: 49db14565711
Ref: c-api/none c Py_None14566020
Ref: 46d614566020
Ref: c-api/none c Py_RETURN_NONE14566262
Ref: 13de14566262
Node: 數值物件14566343
Ref: c-api/concrete numeric-objects14566449
Ref: 49dc14566449
Ref: c-api/concrete numericobjects14566449
Ref: 49dd14566449
Node: 整數物件14566598
Ref: c-api/long doc14566693
Ref: 49de14566693
Ref: c-api/long integer-objects14566693
Ref: 49df14566693
Ref: c-api/long longobjects14566693
Ref: 49e014566693
Ref: c-api/long c PyLongObject14566971
Ref: 52e14566971
Ref: c-api/long c PyLong_Type14567187
Ref: 480014567187
Ref: c-api/long c PyLong_Check14567441
Ref: 49e114567441
Ref: c-api/long c PyLong_CheckExact14567629
Ref: 49e214567629
Ref: c-api/long c PyLong_FromLong14567827
Ref: 173e14567827
Ref: c-api/long c PyLong_FromUnsignedLong14568285
Ref: 18c614568285
Ref: c-api/long c PyLong_FromSsize_t14568557
Ref: 47fc14568557
Ref: c-api/long c PyLong_FromSize_t14568819
Ref: 18c814568819
Ref: c-api/long c PyLong_FromLongLong14569067
Ref: 173f14569067
Ref: c-api/long c PyLong_FromUnsignedLongLong14569317
Ref: 18c714569317
Ref: c-api/long c PyLong_FromDouble14569603
Ref: 8e614569603
Ref: c-api/long c PyLong_FromString14569858
Ref: 47fd14569858
Ref: c-api/long c PyLong_FromUnicodeObject14571191
Ref: 85f14571191
Ref: c-api/long c PyLong_FromVoidPtr14571437
Ref: 47fe14571437
Ref: c-api/long c PyLong_FromNativeBytes14571741
Ref: 33b14571741
Ref: c-api/long c PyLong_FromUnsignedNativeBytes14572417
Ref: 33c14572417
Ref: c-api/long c PyLong_AsLong14572955
Ref: 31614572955
Ref: c-api/long c PyLong_AsInt14573617
Ref: 31514573617
Ref: c-api/long c PyLong_AsLongAndOverflow14573868
Ref: 11ff14573868
Ref: c-api/long c PyLong_AsLongLong14574763
Ref: 47f614574763
Ref: c-api/long c PyLong_AsLongLongAndOverflow14575444
Ref: 11fe14575444
Ref: c-api/long c PyLong_AsSsize_t14576393
Ref: 47f814576393
Ref: c-api/long c PyLong_AsUnsignedLong14576848
Ref: 47f914576848
Ref: c-api/long c PyLong_AsSize_t14577298
Ref: 47f714577298
Ref: c-api/long c PyLong_AsUnsignedLongLong14577726
Ref: 122c14577726
Ref: c-api/long c PyLong_AsUnsignedLongMask14578327
Ref: 47fa14578327
Ref: c-api/long c PyLong_AsUnsignedLongLongMask14579070
Ref: 18eb14579070
Ref: c-api/long c PyLong_AsDouble14579848
Ref: 47f514579848
Ref: c-api/long c PyLong_AsVoidPtr14580258
Ref: 47fb14580258
Ref: c-api/long c PyLong_AsNativeBytes14580723
Ref: 33a14580723
Ref: c-api/long c PyLong_AsNativeBytes Py_ASNATIVEBYTES_DEFAULTS14584869
Ref: 49e314584869
Ref: c-api/long c PyLong_AsNativeBytes Py_ASNATIVEBYTES_BIG_ENDIAN14585049
Ref: 49e414585049
Ref: c-api/long c PyLong_AsNativeBytes Py_ASNATIVEBYTES_LITTLE_ENDIAN14585229
Ref: 49e514585229
Ref: c-api/long c PyLong_AsNativeBytes Py_ASNATIVEBYTES_NATIVE_ENDIAN14585406
Ref: 49e614585406
Ref: c-api/long c PyLong_AsNativeBytes Py_ASNATIVEBYTES_UNSIGNED_BUFFER14585585
Ref: 49e714585585
Ref: c-api/long c PyLong_AsNativeBytes Py_ASNATIVEBYTES_REJECT_NEGATIVE14585762
Ref: 49e814585762
Ref: c-api/long c PyLong_AsNativeBytes Py_ASNATIVEBYTES_ALLOW_INDEX14585935
Ref: 49e914585935
Ref: c-api/long c PyLong_GetInfo14587882
Ref: 47ff14587882
Ref: c-api/long c PyUnstable_Long_IsCompact14588293
Ref: 52f14588293
Ref: c-api/long c PyUnstable_Long_CompactValue14589086
Ref: 53014589086
Node: Boolean（布林）物件14589542
Ref: c-api/bool doc14589681
Ref: 49ea14589681
Ref: c-api/bool boolean-objects14589681
Ref: 49eb14589681
Ref: c-api/bool boolobjects14589681
Ref: 49ec14589681
Ref: c-api/bool c PyBool_Type14589979
Ref: 478114589979
Ref: c-api/bool c PyBool_Check14590231
Ref: 49ef14590231
Ref: c-api/bool c Py_False14590390
Ref: 49ed14590390
Ref: c-api/bool c Py_True14590611
Ref: 49ee14590611
Ref: c-api/bool c Py_RETURN_FALSE14590829
Ref: 13e014590829
Ref: c-api/bool c Py_RETURN_TRUE14590907
Ref: 13df14590907
Ref: c-api/bool c PyBool_FromLong14590983
Ref: 478014590983
Node: 浮點數（Floating-Point）物件14591215
Ref: c-api/float doc14591354
Ref: 49f014591354
Ref: c-api/float floating-point-objects14591354
Ref: 49f114591354
Ref: c-api/float floatobjects14591354
Ref: 49f214591354
Ref: c-api/float c PyFloatObject14591436
Ref: 49f314591436
Ref: c-api/float c PyFloat_Type14591561
Ref: 47dd14591561
Ref: c-api/float c PyFloat_Check14591825
Ref: 49f414591825
Ref: c-api/float c PyFloat_CheckExact14592023
Ref: 49f514592023
Ref: c-api/float c PyFloat_FromString14592231
Ref: 47dc14592231
Ref: c-api/float c PyFloat_FromDouble14592496
Ref: 47db14592496
Ref: c-api/float c PyFloat_AsDouble14592725
Ref: a0c14592725
Ref: c-api/float c PyFloat_AS_DOUBLE14593362
Ref: 49f614593362
Ref: c-api/float c PyFloat_GetInfo14593524
Ref: 135e14593524
Ref: c-api/float c PyFloat_GetMax14593851
Ref: 135c14593851
Ref: c-api/float c PyFloat_GetMin14594014
Ref: 135d14594014
Node: Pack and Unpack functions14594216
Ref: c-api/float pack-and-unpack-functions14594313
Ref: 49f714594313
Node: Pack functions14595612
Ref: c-api/float pack-functions14595713
Ref: 49f814595713
Ref: c-api/float c PyFloat_Pack214596487
Ref: 70914596487
Ref: c-api/float c PyFloat_Pack414596627
Ref: 70a14596627
Ref: c-api/float c PyFloat_Pack814596769
Ref: 70b14596769
Node: Unpack functions14596911
Ref: c-api/float unpack-functions14597012
Ref: 49f914597012
Ref: c-api/float c PyFloat_Unpack214597763
Ref: 70c14597763
Ref: c-api/float c PyFloat_Unpack414597906
Ref: 70d14597906
Ref: c-api/float c PyFloat_Unpack814598051
Ref: 70e14598051
Node: 複數物件14598196
Ref: c-api/complex doc14598301
Ref: 49fa14598301
Ref: c-api/complex complex-number-objects14598301
Ref: 49fb14598301
Ref: c-api/complex complexobjects14598301
Ref: 49fc14598301
Node: 作為 C 結構的複數14598639
Ref: c-api/complex complex-numbers-as-c-structures14598750
Ref: 49fd14598750
Ref: c-api/complex c Py_complex14599023
Ref: 493314599023
Ref: c-api/complex c Py_complex real14599231
Ref: 49fe14599231
Ref: c-api/complex c Py_complex imag14599268
Ref: 49ff14599268
Ref: c-api/complex c _Py_c_sum14599443
Ref: 4a0014599443
Ref: c-api/complex c _Py_c_diff14599621
Ref: 4a0114599621
Ref: c-api/complex c _Py_c_neg14599803
Ref: 4a0214599803
Ref: c-api/complex c _Py_c_prod14599975
Ref: 4a0314599975
Ref: c-api/complex c _Py_c_quot14600157
Ref: 4a0414600157
Ref: c-api/complex c _Py_c_pow14600443
Ref: 4a0514600443
Node: 作為 Python 物件的複數14600766
Ref: c-api/complex complex-numbers-as-python-objects14600877
Ref: 4a0614600877
Ref: c-api/complex c PyComplexObject14600947
Ref: 4a0714600947
Ref: c-api/complex c PyComplex_Type14601065
Ref: 47ae14601065
Ref: c-api/complex c PyComplex_Check14601315
Ref: 4a0814601315
Ref: c-api/complex c PyComplex_CheckExact14601531
Ref: 4a0914601531
Ref: c-api/complex c PyComplex_FromCComplex14601754
Ref: 4a0a14601754
Ref: c-api/complex c PyComplex_FromDoubles14601996
Ref: 47ad14601996
Ref: c-api/complex c PyComplex_RealAsDouble14602309
Ref: 158d14602309
Ref: c-api/complex c PyComplex_ImagAsDouble14603002
Ref: 158e14603002
Ref: c-api/complex c PyComplex_AsCComplex14603704
Ref: 135f14603704
Node: 序列物件14604479
Ref: c-api/concrete sequence-objects14604585
Ref: 4a0b14604585
Ref: c-api/concrete sequenceobjects14604585
Ref: 4a0c14604585
Node: 位元組物件 Bytes Objects14605029
Ref: c-api/bytes doc14605156
Ref: 4a0d14605156
Ref: c-api/bytes bytes-objects14605156
Ref: 4a0e14605156
Ref: c-api/bytes bytesobjects14605156
Ref: 4a0f14605156
Ref: c-api/bytes c PyBytesObject14605349
Ref: 73614605349
Ref: c-api/bytes c PyBytes_Type14605465
Ref: 478e14605465
Ref: c-api/bytes c PyBytes_Check14605717
Ref: 132214605717
Ref: c-api/bytes c PyBytes_CheckExact14605902
Ref: 4a1014605902
Ref: c-api/bytes c PyBytes_FromString14606103
Ref: 478c14606103
Ref: c-api/bytes c PyBytes_FromStringAndSize14606439
Ref: 132314606439
Ref: c-api/bytes c PyBytes_FromFormat14606833
Ref: 192f14606833
Ref: c-api/bytes c PyBytes_FromFormatV14610521
Ref: 478a14610521
Ref: c-api/bytes c PyBytes_FromObject14610803
Ref: 478b14610803
Ref: c-api/bytes c PyBytes_Size14611044
Ref: 478d14611044
Ref: c-api/bytes c PyBytes_GET_SIZE14611215
Ref: 4a1114611215
Ref: c-api/bytes c PyBytes_AsString14611357
Ref: 82b14611357
Ref: c-api/bytes c PyBytes_AS_STRING14612010
Ref: 4a1214612010
Ref: c-api/bytes c PyBytes_AsStringAndSize14612149
Ref: 478714612149
Ref: c-api/bytes c PyBytes_Concat14613219
Ref: 478814613219
Ref: c-api/bytes c PyBytes_ConcatAndDel14613748
Ref: 478914613748
Ref: c-api/bytes c _PyBytes_Resize14614105
Ref: 154814614105
Ref: 位元組物件 Bytes Objects-Footnote-114614860
Ref: 位元組物件 Bytes Objects-Footnote-214614986
Ref: 位元組物件 Bytes Objects-Footnote-314615112
Ref: 位元組物件 Bytes Objects-Footnote-414615238
Ref: 位元組物件 Bytes Objects-Footnote-514615364
Ref: 位元組物件 Bytes Objects-Footnote-614615490
Ref: 位元組物件 Bytes Objects-Footnote-714615616
Ref: 位元組物件 Bytes Objects-Footnote-814615742
Node: 位元組陣列物件 Byte Array Objects14615868
Ref: c-api/bytearray doc14616033
Ref: 4a1314616033
Ref: c-api/bytearray byte-array-objects14616033
Ref: 4a1414616033
Ref: c-api/bytearray bytearrayobjects14616033
Ref: 4a1514616033
Ref: c-api/bytearray c PyByteArrayObject14616129
Ref: 4a1614616129
Ref: c-api/bytearray c PyByteArray_Type14616258
Ref: 478614616258
Node: 型別檢查巨集14616590
Ref: c-api/bytearray type-check-macros14616711
Ref: 4a1714616711
Ref: c-api/bytearray c PyByteArray_Check14616760
Ref: 4a1814616760
Ref: c-api/bytearray c PyByteArray_CheckExact14616979
Ref: 4a1914616979
Node: 直接 API 函式14617203
Ref: c-api/bytearray direct-api-functions14617339
Ref: 4a1a14617339
Ref: c-api/bytearray c PyByteArray_FromObject14617388
Ref: 132414617388
Ref: c-api/bytearray c PyByteArray_FromStringAndSize14617731
Ref: 132514617731
Ref: c-api/bytearray c PyByteArray_Concat14618064
Ref: 478314618064
Ref: c-api/bytearray c PyByteArray_Size14618390
Ref: 478514618390
Ref: c-api/bytearray c PyByteArray_AsString14618599
Ref: 478214618599
Ref: c-api/bytearray c PyByteArray_Resize14618869
Ref: 478414618869
Node: 巨集14619059
Ref: c-api/bytearray macros14619168
Ref: 4a1b14619168
Ref: c-api/bytearray c PyByteArray_AS_STRING14619280
Ref: 4a1c14619280
Ref: c-api/bytearray c PyByteArray_GET_SIZE14619425
Ref: 4a1d14619425
Node: Unicode 物件與編解碼器14619592
Ref: c-api/unicode doc14619751
Ref: 113814619751
Ref: c-api/unicode unicode-objects-and-codecs14619751
Ref: 4a1e14619751
Ref: c-api/unicode unicodeobjects14619751
Ref: 4a1f14619751
Node: Unicode 物件14619901
Ref: c-api/unicode unicode-objects14620005
Ref: 4a2014620005
Ref: Unicode 物件-Footnote-114620875
Ref: Unicode 物件-Footnote-214620917
Node: Unicode Type14620959
Ref: c-api/unicode unicode-type14621059
Ref: 4a2114621059
Ref: c-api/unicode c Py_UCS414621191
Ref: 110e14621191
Ref: c-api/unicode c Py_UCS214621218
Ref: 110d14621218
Ref: c-api/unicode c Py_UCS114621245
Ref: 110c14621245
Ref: c-api/unicode c Py_UNICODE14621568
Ref: 3b814621568
Ref: c-api/unicode c PyASCIIObject14621977
Ref: 110f14621977
Ref: c-api/unicode c PyCompactUnicodeObject14622010
Ref: 111014622010
Ref: c-api/unicode c PyUnicodeObject14622052
Ref: 73814622052
Ref: c-api/unicode c PyUnicode_Type14622368
Ref: 48ae14622368
Ref: c-api/unicode c PyUnicode_Check14622740
Ref: 4a2214622740
Ref: c-api/unicode c PyUnicode_CheckExact14622923
Ref: 4a2314622923
Ref: c-api/unicode c PyUnicode_READY14623109
Ref: 3c914623109
Ref: c-api/unicode c PyUnicode_GET_LENGTH14623342
Ref: 85914623342
Ref: c-api/unicode c PyUnicode_1BYTE_DATA14623619
Ref: 111414623619
Ref: c-api/unicode c PyUnicode_2BYTE_DATA14623706
Ref: 111514623706
Ref: c-api/unicode c PyUnicode_4BYTE_DATA14623793
Ref: 111614623793
Ref: c-api/unicode c PyUnicode_1BYTE_KIND14624207
Ref: 111814624207
Ref: c-api/unicode c PyUnicode_2BYTE_KIND14624242
Ref: 111914624242
Ref: c-api/unicode c PyUnicode_4BYTE_KIND14624277
Ref: 111a14624277
Ref: c-api/unicode c PyUnicode_KIND14624477
Ref: 111714624477
Ref: c-api/unicode c PyUnicode_DATA14624809
Ref: 111314624809
Ref: c-api/unicode c PyUnicode_WRITE14625045
Ref: 111d14625045
Ref: c-api/unicode c PyUnicode_READ14625607
Ref: 111b14625607
Ref: c-api/unicode c PyUnicode_READ_CHAR14625901
Ref: 111c14625901
Ref: c-api/unicode c PyUnicode_MAX_CHAR_VALUE14626245
Ref: 111e14626245
Ref: c-api/unicode c PyUnicode_IsIdentifier14626613
Ref: 18a114626613
Node: Unicode Character Properties14627020
Ref: c-api/unicode unicode-character-properties14627167
Ref: 4a2414627167
Ref: c-api/unicode c Py_UNICODE_ISSPACE14627431
Ref: 180814627431
Ref: c-api/unicode c Py_UNICODE_ISLOWER14627572
Ref: 4a2514627572
Ref: c-api/unicode c Py_UNICODE_ISUPPER14627712
Ref: 4a2614627712
Ref: c-api/unicode c Py_UNICODE_ISTITLE14627853
Ref: 4a2714627853
Ref: c-api/unicode c Py_UNICODE_ISLINEBREAK14627993
Ref: 4a2814627993
Ref: c-api/unicode c Py_UNICODE_ISDECIMAL14628137
Ref: 4a2914628137
Ref: c-api/unicode c Py_UNICODE_ISDIGIT14628272
Ref: 4a2a14628272
Ref: c-api/unicode c Py_UNICODE_ISNUMERIC14628403
Ref: 4a2b14628403
Ref: c-api/unicode c Py_UNICODE_ISALPHA14628538
Ref: 4a2c14628538
Ref: c-api/unicode c Py_UNICODE_ISALNUM14628680
Ref: 4a2d14628680
Ref: c-api/unicode c Py_UNICODE_ISPRINTABLE14628824
Ref: 4a2e14628824
Ref: c-api/unicode c Py_UNICODE_TOLOWER14629482
Ref: 4a2f14629482
Ref: c-api/unicode c Py_UNICODE_TOUPPER14629607
Ref: 4a3014629607
Ref: c-api/unicode c Py_UNICODE_TOTITLE14629732
Ref: 4a3114629732
Ref: c-api/unicode c Py_UNICODE_TODECIMAL14629857
Ref: 4a3214629857
Ref: c-api/unicode c Py_UNICODE_TODIGIT14630076
Ref: 4a3314630076
Ref: c-api/unicode c Py_UNICODE_TONUMERIC14630289
Ref: 4a3414630289
Ref: c-api/unicode c Py_UNICODE_IS_SURROGATE14630540
Ref: 4a3514630540
Ref: c-api/unicode c Py_UNICODE_IS_HIGH_SURROGATE14630663
Ref: 4a3614630663
Ref: c-api/unicode c Py_UNICODE_IS_LOW_SURROGATE14630796
Ref: 4a3714630796
Ref: c-api/unicode c Py_UNICODE_JOIN_SURROGATES14630927
Ref: 4a3814630927
Node: Creating and accessing Unicode strings14631319
Ref: c-api/unicode creating-and-accessing-unicode-strings14631469
Ref: 4a3914631469
Ref: c-api/unicode c PyUnicode_New14631653
Ref: 85014631653
Ref: c-api/unicode c PyUnicode_FromKindAndData14632167
Ref: 111114632167
Ref: c-api/unicode c PyUnicode_FromStringAndSize14632965
Ref: 48a814632965
Ref: c-api/unicode c PyUnicode_FromString14633633
Ref: 474814633633
Ref: c-api/unicode c PyUnicode_FromFormat14633877
Ref: 33f14633877
Ref: c-api/unicode c PyUnicode_FromFormatV14646822
Ref: 51a14646822
Ref: c-api/unicode c PyUnicode_FromObject14647107
Ref: 48a714647107
Ref: c-api/unicode c PyUnicode_FromEncodedObject14647561
Ref: 48a614647561
Ref: c-api/unicode c PyUnicode_GetLength14648372
Ref: 85814648372
Ref: c-api/unicode c PyUnicode_CopyCharacters14648621
Ref: 85a14648621
Ref: c-api/unicode c PyUnicode_Fill14649110
Ref: 112714649110
Ref: c-api/unicode c PyUnicode_WriteChar14649601
Ref: 110b14649601
Ref: c-api/unicode c PyUnicode_ReadChar14650234
Ref: 110a14650234
Ref: c-api/unicode c PyUnicode_Substring14650665
Ref: 85b14650665
Ref: c-api/unicode c PyUnicode_AsUCS414651077
Ref: 111214651077
Ref: c-api/unicode c PyUnicode_AsUCS4Copy14651609
Ref: 86014651609
Node: Locale Encoding14652059
Ref: c-api/unicode locale-encoding14652201
Ref: 4a3b14652201
Ref: c-api/unicode c PyUnicode_DecodeLocaleAndSize14652335
Ref: b7014652335
Ref: c-api/unicode c PyUnicode_DecodeLocale14653570
Ref: 489814653570
Ref: c-api/unicode c PyUnicode_EncodeLocale14653924
Ref: b7114653924
Ref: Locale Encoding-Footnote-114655171
Ref: Locale Encoding-Footnote-214655213
Node: File System Encoding14655255
Ref: c-api/unicode file-system-encoding14655373
Ref: 4a3c14655373
Ref: c-api/unicode c PyUnicode_FSConverter14655740
Ref: cc014655740
Ref: c-api/unicode c PyUnicode_FSDecoder14656491
Ref: 51d14656491
Ref: c-api/unicode c PyUnicode_DecodeFSDefaultAndSize14657093
Ref: 489614657093
Ref: c-api/unicode c PyUnicode_DecodeFSDefault14657651
Ref: 161714657651
Ref: c-api/unicode c PyUnicode_EncodeFSDefault14658102
Ref: 195714658102
Ref: File System Encoding-Footnote-114658812
Ref: File System Encoding-Footnote-214658854
Node: wchar_t 支援14658896
Ref: c-api/unicode wchar-t-support14658990
Ref: 4a3d14658990
Ref: c-api/unicode c PyUnicode_FromWideChar14659092
Ref: 112614659092
Ref: c-api/unicode c PyUnicode_AsWideChar14659526
Ref: 195d14659526
Ref: c-api/unicode c PyUnicode_AsWideCharString14660523
Ref: 86114660523
Node: Built-in Codecs14661658
Ref: c-api/unicode built-in-codecs14661797
Ref: 4a3e14661797
Ref: c-api/unicode builtincodecs14661797
Ref: 4a3a14661797
Node: Generic Codecs14663072
Ref: c-api/unicode generic-codecs14663165
Ref: 4a3f14663165
Ref: c-api/unicode c PyUnicode_Decode14663249
Ref: 18e714663249
Ref: c-api/unicode c PyUnicode_AsEncodedString14663825
Ref: 488f14663825
Node: UTF-8 編解碼器14664385
Ref: c-api/unicode utf-8-codecs14664506
Ref: 4a4014664506
Ref: c-api/unicode c PyUnicode_DecodeUTF814664592
Ref: 48a214664592
Ref: c-api/unicode c PyUnicode_DecodeUTF8Stateful14664947
Ref: 16a214664947
Ref: c-api/unicode c PyUnicode_AsUTF8String14665508
Ref: 112814665508
Ref: c-api/unicode c PyUnicode_AsUTF8AndSize14665862
Ref: 83d14665862
Ref: c-api/unicode c PyUnicode_AsUTF814667067
Ref: b6214667067
Node: UTF-32 編解碼器14667339
Ref: c-api/unicode utf-32-codecs14667465
Ref: 4a4114667465
Ref: c-api/unicode c PyUnicode_DecodeUTF3214667554
Ref: 489e14667554
Ref: c-api/unicode c PyUnicode_DecodeUTF32Stateful14668754
Ref: 489f14668754
Ref: c-api/unicode c PyUnicode_AsUTF32String14669434
Ref: 489114669434
Node: UTF-16 編解碼器14669825
Ref: c-api/unicode utf-16-codecs14669951
Ref: 4a4214669951
Ref: c-api/unicode c PyUnicode_DecodeUTF1614670040
Ref: 489c14670040
Ref: c-api/unicode c PyUnicode_DecodeUTF16Stateful14671324
Ref: 489d14671324
Ref: c-api/unicode c PyUnicode_AsUTF16String14672013
Ref: 489014672013
Node: UTF-7 編解碼器14672404
Ref: c-api/unicode utf-7-codecs14672532
Ref: 4a4314672532
Ref: c-api/unicode c PyUnicode_DecodeUTF714672618
Ref: 48a014672618
Ref: c-api/unicode c PyUnicode_DecodeUTF7Stateful14672973
Ref: 48a114672973
Node: Unicode-Escape Codecs14673536
Ref: c-api/unicode unicode-escape-codecs14673670
Ref: 4a4414673670
Ref: c-api/unicode c PyUnicode_DecodeUnicodeEscape14673777
Ref: 48a314673777
Ref: c-api/unicode c PyUnicode_AsUnicodeEscapeString14674155
Ref: 112914674155
Node: Raw-Unicode-Escape Codecs14674522
Ref: c-api/unicode raw-unicode-escape-codecs14674658
Ref: 4a4514674658
Ref: c-api/unicode c PyUnicode_DecodeRawUnicodeEscape14674777
Ref: 489b14674777
Ref: c-api/unicode c PyUnicode_AsRawUnicodeEscapeString14675162
Ref: 112a14675162
Node: Latin-1 編解碼器14675536
Ref: c-api/unicode latin-1-codecs14675669
Ref: 4a4614675669
Ref: c-api/unicode c PyUnicode_DecodeLatin114675874
Ref: 489714675874
Ref: c-api/unicode c PyUnicode_AsLatin1String14676238
Ref: 112b14676238
Node: ASCII 編解碼器14676596
Ref: c-api/unicode ascii-codecs14676724
Ref: 4a4714676724
Ref: c-api/unicode c PyUnicode_DecodeASCII14676880
Ref: 489414676880
Ref: c-api/unicode c PyUnicode_AsASCIIString14677236
Ref: 112c14677236
Node: Character Map Codecs14677591
Ref: c-api/unicode character-map-codecs14677722
Ref: 4a4814677722
Ref: c-api/unicode c PyUnicode_DecodeCharmap14678202
Ref: 489514678202
Ref: c-api/unicode c PyUnicode_AsCharmapString14679093
Ref: 488e14679093
Ref: c-api/unicode c PyUnicode_Translate14679866
Ref: 48ad14679866
Node: MBCS codecs for Windows14680765
Ref: c-api/unicode mbcs-codecs-for-windows14680893
Ref: 4a4914680893
Ref: c-api/unicode c PyUnicode_DecodeMBCS14681253
Ref: 489914681253
Ref: c-api/unicode c PyUnicode_DecodeMBCSStateful14681645
Ref: 489a14681645
Ref: c-api/unicode c PyUnicode_AsMBCSString14682211
Ref: 112d14682211
Ref: c-api/unicode c PyUnicode_EncodeCodePage14682597
Ref: 112e14682597
Node: Methods & Slots14683086
Ref: c-api/unicode methods-slots14683185
Ref: 4a4a14683185
Node: Methods and Slot Functions14683236
Ref: c-api/unicode methods-and-slot-functions14683352
Ref: 4a4b14683352
Ref: c-api/unicode unicodemethodsandslots14683352
Ref: 4a4c14683352
Ref: c-api/unicode c PyUnicode_Concat14683675
Ref: 113914683675
Ref: c-api/unicode c PyUnicode_Split14683904
Ref: 48ab14683904
Ref: c-api/unicode c PyUnicode_Splitlines14684426
Ref: 48ac14684426
Ref: c-api/unicode c PyUnicode_Join14684834
Ref: 113a14684834
Ref: c-api/unicode c PyUnicode_Tailmatch14685117
Ref: 85d14685117
Ref: c-api/unicode c PyUnicode_Find14685579
Ref: 48a414685579
Ref: c-api/unicode c PyUnicode_FindChar14686193
Ref: 85e14686193
Ref: c-api/unicode c PyUnicode_Count14686974
Ref: 489314686974
Ref: c-api/unicode c PyUnicode_Replace14687297
Ref: 48a914687297
Ref: c-api/unicode c PyUnicode_Compare14687708
Ref: 85c14687708
Ref: c-api/unicode c PyUnicode_EqualToUTF8AndSize14688076
Ref: 31c14688076
Ref: c-api/unicode c PyUnicode_EqualToUTF814688654
Ref: 31d14688654
Ref: c-api/unicode c PyUnicode_CompareWithASCIIString14689043
Ref: 120014689043
Ref: c-api/unicode c PyUnicode_RichCompare14689548
Ref: 48aa14689548
Ref: c-api/unicode c PyUnicode_Format14690211
Ref: 48a514690211
Ref: c-api/unicode c PyUnicode_Contains14690493
Ref: 489214690493
Ref: c-api/unicode c PyUnicode_InternInPlace14690822
Ref: 85614690822
Ref: c-api/unicode c PyUnicode_InternFromString14692198
Ref: 14f214692198
Node: Tuple（元組）物件14693138
Ref: c-api/tuple doc14693280
Ref: 4a4d14693280
Ref: c-api/tuple tuple-objects14693280
Ref: 4a4e14693280
Ref: c-api/tuple tupleobjects14693280
Ref: 4a4f14693280
Ref: c-api/tuple c PyTupleObject14693341
Ref: 491d14693341
Ref: c-api/tuple c PyTuple_Type14693457
Ref: 487214693457
Ref: c-api/tuple c PyTuple_Check14693709
Ref: 4a5014693709
Ref: c-api/tuple c PyTuple_CheckExact14693883
Ref: 4a5114693883
Ref: c-api/tuple c PyTuple_New14694068
Ref: 36414694068
Ref: c-api/tuple c PyTuple_Pack14694311
Ref: 487014694311
Ref: c-api/tuple c PyTuple_Size14694743
Ref: 487114694743
Ref: c-api/tuple c PyTuple_GET_SIZE14694990
Ref: 4a5214694990
Ref: c-api/tuple c PyTuple_GetItem14695126
Ref: 46ed14695126
Ref: c-api/tuple c PyTuple_GET_ITEM14695756
Ref: 4a5314695756
Ref: c-api/tuple c PyTuple_GetSlice14695965
Ref: 486f14695965
Ref: c-api/tuple c PyTuple_SetItem14696417
Ref: 46ee14696417
Ref: c-api/tuple c PyTuple_SET_ITEM14696934
Ref: 30514696934
Ref: c-api/tuple c _PyTuple_Resize14697549
Ref: 147b14697549
Node: Struct Sequence Objects14698463
Ref: c-api/tuple id114698598
Ref: 4a5414698598
Ref: c-api/tuple struct-sequence-objects14698598
Ref: 115714698598
Ref: c-api/tuple c PyStructSequence_NewType14698906
Ref: 486214698906
Ref: c-api/tuple c PyStructSequence_InitType14699327
Ref: fa414699327
Ref: c-api/tuple c PyStructSequence_InitType214699503
Ref: fa314699503
Ref: c-api/tuple c PyStructSequence_Desc14699771
Ref: b6114699771
Ref: c-api/tuple c PyStructSequence_Desc name14699960
Ref: 4a5514699960
Ref: c-api/tuple c PyStructSequence_Desc doc14700048
Ref: 4a5614700048
Ref: c-api/tuple c PyStructSequence_Desc fields14700158
Ref: 4a5714700158
Ref: c-api/tuple c PyStructSequence_Desc n_in_sequence14700321
Ref: 4a5814700321
Ref: c-api/tuple c PyStructSequence_Field14700450
Ref: b6014700450
Ref: c-api/tuple c PyStructSequence_Field name14700865
Ref: 4a5914700865
Ref: c-api/tuple c PyStructSequence_Field doc14701072
Ref: 4a5a14701072
Ref: c-api/tuple c PyStructSequence_UnnamedField14701164
Ref: 92614701164
Ref: c-api/tuple c PyStructSequence_New14701424
Ref: 486114701424
Ref: c-api/tuple c PyStructSequence_GetItem14701764
Ref: 486014701764
Ref: c-api/tuple c PyStructSequence_GET_ITEM14702159
Ref: 4a5b14702159
Ref: c-api/tuple c PyStructSequence_SetItem14702456
Ref: 486314702456
Ref: c-api/tuple c PyStructSequence_SET_ITEM14702977
Ref: 4a5c14702977
Node: List（串列）物件14703237
Ref: c-api/list doc14703340
Ref: 4a5d14703340
Ref: c-api/list list-objects14703340
Ref: 4a5e14703340
Ref: c-api/list listobjects14703340
Ref: 4a5f14703340
Ref: c-api/list c PyListObject14703399
Ref: 498314703399
Ref: c-api/list c PyList_Type14703521
Ref: 471114703521
Ref: c-api/list c PyList_Check14703764
Ref: 4a6014703764
Ref: c-api/list c PyList_CheckExact14703952
Ref: 4a6114703952
Ref: c-api/list c PyList_New14704145
Ref: 476514704145
Ref: c-api/list c PyList_Size14704914
Ref: 138714704914
Ref: c-api/list c PyList_GET_SIZE14705120
Ref: 4a6214705120
Ref: c-api/list c PyList_GetItemRef14705262
Ref: 31214705262
Ref: c-api/list c PyList_GetItem14705798
Ref: 31314705798
Ref: c-api/list c PyList_GET_ITEM14706107
Ref: 477914706107
Ref: c-api/list c PyList_SetItem14706309
Ref: 46ef14706309
Ref: c-api/list c PyList_SET_ITEM14706791
Ref: 30614706791
Ref: c-api/list c PyList_Insert14707409
Ref: 47f114707409
Ref: c-api/list c PyList_Append14707760
Ref: 47ee14707760
Ref: c-api/list c PyList_GetSlice14708065
Ref: 47f014708065
Ref: c-api/list c PyList_SetSlice14708488
Ref: 47f314708488
Ref: c-api/list c PyList_Extend14708967
Ref: 32914708967
Ref: c-api/list c PyList_Clear14709408
Ref: 32a14709408
Ref: c-api/list c PyList_Sort14709780
Ref: 47f414709780
Ref: c-api/list c PyList_Reverse14710027
Ref: 47f214710027
Ref: c-api/list c PyList_AsTuple14710255
Ref: 47ef14710255
Node: 容器物件14710520
Ref: c-api/concrete container-objects14710629
Ref: 4a6314710629
Ref: c-api/concrete mapobjects14710629
Ref: 4a6414710629
Node: 字典物件14710708
Ref: c-api/dict doc14710790
Ref: 4a6514710790
Ref: c-api/dict dictionary-objects14710790
Ref: 4a6614710790
Ref: c-api/dict dictobjects14710790
Ref: 4a6714710790
Ref: c-api/dict c PyDictObject14710829
Ref: 38c14710829
Ref: c-api/dict c PyDict_Type14710934
Ref: 47bc14710934
Ref: c-api/dict c PyDict_Check14711176
Ref: 49be14711176
Ref: c-api/dict c PyDict_CheckExact14711347
Ref: 4a6814711347
Ref: c-api/dict c PyDict_New14711538
Ref: 47ba14711538
Ref: c-api/dict c PyDictProxy_New14711739
Ref: 47b214711739
Ref: c-api/dict c PyDict_Clear14712121
Ref: 47b314712121
Ref: c-api/dict c PyDict_Contains14712275
Ref: 31014712275
Ref: c-api/dict c PyDict_ContainsString14712615
Ref: 30f14712615
Ref: c-api/dict c PyDict_Copy14712887
Ref: 36014712887
Ref: c-api/dict c PyDict_SetItem14713104
Ref: 46f014713104
Ref: c-api/dict c PyDict_SetItemString14713512
Ref: 14f314713512
Ref: c-api/dict c PyDict_DelItem14713822
Ref: 47b414713822
Ref: c-api/dict c PyDict_DelItemString14714207
Ref: 47b514714207
Ref: c-api/dict c PyDict_GetItemRef14714492
Ref: 30a14714492
Ref: c-api/dict c PyDict_GetItem14715129
Ref: 35b14715129
Ref: c-api/dict c PyDict_GetItemWithError14715868
Ref: 30c14715868
Ref: c-api/dict c PyDict_GetItemString14716276
Ref: 35c14716276
Ref: c-api/dict c PyDict_GetItemStringRef14716983
Ref: 30b14716983
Ref: c-api/dict c PyDict_SetDefault14717352
Ref: 30e14717352
Ref: c-api/dict c PyDict_SetDefaultRef14717948
Ref: 30d14717948
Ref: c-api/dict c PyDict_Pop14719042
Ref: 32b14719042
Ref: c-api/dict c PyDict_PopString14719772
Ref: 32c14719772
Ref: c-api/dict c PyDict_Items14720054
Ref: 47b614720054
Ref: c-api/dict c PyDict_Keys14720287
Ref: 47b714720287
Ref: c-api/dict c PyDict_Values14720518
Ref: 47be14720518
Ref: c-api/dict c PyDict_Size14720757
Ref: 47bb14720757
Ref: c-api/dict c PyDict_Next14720979
Ref: 150514720979
Ref: c-api/dict c PyDict_Merge14723348
Ref: 47b814723348
Ref: c-api/dict c PyDict_Update14723928
Ref: 47bd14723928
Ref: c-api/dict c PyDict_MergeFromSeq214724388
Ref: 47b914724388
Ref: c-api/dict c PyDict_AddWatcher14725117
Ref: 50814725117
Ref: c-api/dict c PyDict_ClearWatcher14725477
Ref: 4a6a14725477
Ref: c-api/dict c PyDict_Watch14725778
Ref: 50914725778
Ref: c-api/dict c PyDict_Unwatch14726102
Ref: 4a6b14726102
Ref: c-api/dict c PyDict_WatchEvent14726514
Ref: 4a6c14726514
Ref: c-api/dict c PyDict_WatchCallback14726826
Ref: 4a6d14726826
Node: 集合物件14729095
Ref: c-api/set doc14729177
Ref: 4a6e14729177
Ref: c-api/set set-objects14729177
Ref: 4a6f14729177
Ref: c-api/set setobjects14729177
Ref: 4a7014729177
Ref: c-api/set c PySetObject14729951
Ref: 4a7114729951
Ref: c-api/set c PySet_Type14730593
Ref: 485914730593
Ref: c-api/set c PyFrozenSet_Type14730792
Ref: 47de14730792
Ref: c-api/set c PySet_Check14731154
Ref: 4a7214731154
Ref: c-api/set c PyFrozenSet_Check14731318
Ref: 4a7314731318
Ref: c-api/set c PyAnySet_Check14731494
Ref: 4a7414731494
Ref: c-api/set c PySet_CheckExact14731699
Ref: 84114731699
Ref: c-api/set c PyAnySet_CheckExact14731902
Ref: 4a7514731902
Ref: c-api/set c PyFrozenSet_CheckExact14732118
Ref: 4a7614732118
Ref: c-api/set c PySet_New14732304
Ref: 13b214732304
Ref: c-api/set c PyFrozenSet_New14732805
Ref: 13b314732805
Ref: c-api/set c PySet_Size14733391
Ref: 13b714733391
Ref: c-api/set c PySet_GET_SIZE14733756
Ref: 4a7714733756
Ref: c-api/set c PySet_Contains14733898
Ref: 13b614733898
Ref: c-api/set c PySet_Add14734453
Ref: 13b414734453
Ref: c-api/set c PySet_Discard14735245
Ref: 13b514735245
Ref: c-api/set c PySet_Pop14735856
Ref: 485814735856
Ref: c-api/set c PySet_Clear14736292
Ref: 485714736292
Node: 函式物件<2>14736584
Ref: c-api/concrete function-objects14736696
Ref: 4a7814736696
Ref: c-api/concrete otherobjects14736696
Ref: 4a7914736696
Node: 函式物件 Function Objects14737019
Ref: c-api/function doc14737151
Ref: 4a7a14737151
Ref: c-api/function function-objects14737151
Ref: 4a7b14737151
Ref: c-api/function id114737151
Ref: 4a7c14737151
Ref: c-api/function c PyFunctionObject14737277
Ref: 50714737277
Ref: c-api/function c PyFunction_Type14737348
Ref: 4a7d14737348
Ref: c-api/function c PyFunction_Check14737568
Ref: 4a7e14737568
Ref: c-api/function c PyFunction_New14737790
Ref: 4a7f14737790
Ref: c-api/function c PyFunction_NewWithQualName14738403
Ref: 4a8014738403
Ref: c-api/function c PyFunction_GetCode14738907
Ref: 4a8114738907
Ref: c-api/function c PyFunction_GetGlobals14739067
Ref: 4a8214739067
Ref: c-api/function c PyFunction_GetModule14739233
Ref: 4a8314739233
Ref: c-api/function c PyFunction_GetDefaults14739610
Ref: 4a8414739610
Ref: c-api/function c PyFunction_SetDefaults14739846
Ref: 4a8514739846
Ref: c-api/function c PyFunction_SetVectorcall14740114
Ref: 50614740114
Ref: c-api/function c PyFunction_GetClosure14740443
Ref: 4a8614740443
Ref: c-api/function c PyFunction_SetClosure14740675
Ref: 4a8714740675
Ref: c-api/function c PyFunction_GetAnnotations14740958
Ref: 16bd14740958
Ref: c-api/function c PyFunction_SetAnnotations14741187
Ref: 4a8814741187
Ref: c-api/function c PyFunction_AddWatcher14741449
Ref: 4a8914741449
Ref: c-api/function c PyFunction_ClearWatcher14741828
Ref: 4a8a14741828
Ref: c-api/function c PyFunction_WatchEvent14742194
Ref: 4a8b14742194
Ref: c-api/function c PyFunction_WatchCallback14742521
Ref: 4a8c14742521
Node: 實例方法物件 Instance Method Objects14744730
Ref: c-api/method doc14744898
Ref: 4a8d14744898
Ref: c-api/method instance-method-objects14744898
Ref: 4a8e14744898
Ref: c-api/method instancemethod-objects14744898
Ref: 4a8f14744898
Ref: c-api/method c PyInstanceMethod_Type14745224
Ref: 4a9014745224
Ref: c-api/method c PyInstanceMethod_Check14745412
Ref: 4a9114745412
Ref: c-api/method c PyInstanceMethod_New14745650
Ref: 4a9214745650
Ref: c-api/method c PyInstanceMethod_Function14745899
Ref: 4a9314745899
Ref: c-api/method c PyInstanceMethod_GET_FUNCTION14746074
Ref: 4a9414746074
Node: 方法物件 Method Objects14746299
Ref: c-api/method id114746449
Ref: 4a9514746449
Ref: c-api/method method-objects14746449
Ref: 4a9614746449
Ref: c-api/method c PyMethod_Type14746705
Ref: 4a9714746705
Ref: c-api/method c PyMethod_Check14746897
Ref: 4a9814746897
Ref: c-api/method c PyMethod_New14747113
Ref: 4a9914747113
Ref: c-api/method c PyMethod_Function14747452
Ref: 4a9a14747452
Ref: c-api/method c PyMethod_GET_FUNCTION14747607
Ref: 4a9b14747607
Ref: c-api/method c PyMethod_Self14747800
Ref: 4a9c14747800
Ref: c-api/method c PyMethod_GET_SELF14747945
Ref: 4a9d14747945
Node: Cell 物件14748130
Ref: c-api/cell doc14748253
Ref: 4a9e14748253
Ref: c-api/cell cell-objects14748253
Ref: 6a414748253
Ref: c-api/cell id114748253
Ref: 4a9f14748253
Ref: c-api/cell c PyCellObject14748850
Ref: 4aa014748850
Ref: c-api/cell c PyCell_Type14748922
Ref: 4aa114748922
Ref: c-api/cell c PyCell_Check14749017
Ref: 4aa214749017
Ref: c-api/cell c PyCell_New14749192
Ref: 4aa314749192
Ref: c-api/cell c PyCell_Get14749380
Ref: 4aa414749380
Ref: c-api/cell c PyCell_GET14749634
Ref: 4aa514749634
Ref: c-api/cell c PyCell_Set14749852
Ref: 4aa614749852
Ref: c-api/cell c PyCell_SET14750221
Ref: 85314750221
Node: 程式碼物件14750472
Ref: c-api/code doc14750585
Ref: 4aa714750585
Ref: c-api/code code-objects14750585
Ref: 4aa814750585
Ref: c-api/code codeobjects14750585
Ref: 55914750585
Ref: c-api/code c PyCodeObject14750789
Ref: 71b14750789
Ref: c-api/code c PyCode_Type14750955
Ref: 4aa914750955
Ref: c-api/code c PyCode_Check14751114
Ref: 4aaa14751114
Ref: c-api/code c PyCode_GetNumFree14751253
Ref: 4aab14751253
Ref: c-api/code c PyUnstable_Code_GetFirstFree14751388
Ref: 35e14751388
Ref: c-api/code c PyUnstable_Code_New14751936
Ref: 4aac14751936
Ref: c-api/code c PyUnstable_Code_NewWithPosOnlyArgs14753368
Ref: 4aad14753368
Ref: c-api/code c PyCode_NewEmpty14754576
Ref: 12e514754576
Ref: c-api/code c PyCode_Addr2Line14754918
Ref: 82d14754918
Ref: c-api/code c PyCode_Addr2Location14755319
Ref: 55814755319
Ref: c-api/code c PyCode_GetCode14755797
Ref: 71c14755797
Ref: c-api/code c PyCode_GetVarnames14756379
Ref: 71d14756379
Ref: c-api/code c PyCode_GetCellvars14756731
Ref: 71e14756731
Ref: c-api/code c PyCode_GetFreevars14757128
Ref: 71f14757128
Ref: c-api/code c PyCode_AddWatcher14757479
Ref: 50c14757479
Ref: c-api/code c PyCode_ClearWatcher14757838
Ref: 50d14757838
Ref: c-api/code c PyCodeEvent14758195
Ref: 4aae14758195
Ref: c-api/code c PyCode_WatchCallback14758378
Ref: 4aaf14758378
Ref: 程式碼物件-Footnote-114760200
Node: Extra information14760282
Ref: c-api/code extra-information14760375
Ref: 4ab014760375
Ref: c-api/code c PyUnstable_Eval_RequestCodeExtraIndex14760748
Ref: 4ab114760748
Ref: c-api/code c PyUnstable_Code_GetExtra14761785
Ref: 4ab214761785
Ref: c-api/code c PyUnstable_Code_SetExtra14762559
Ref: 4ab314762559
Node: 其他物件<2>14763216
Ref: c-api/concrete other-objects14763307
Ref: 4ab414763307
Node: 檔案物件 File Objects14763775
Ref: c-api/file doc14763873
Ref: 4ab514763873
Ref: c-api/file file-objects14763873
Ref: 4ab614763873
Ref: c-api/file fileobjects14763873
Ref: 4ab714763873
Ref: c-api/file c PyFile_FromFd14764419
Ref: 47d714764419
Ref: c-api/file c PyObject_AsFileDescriptor14765424
Ref: 483414765424
Ref: c-api/file c PyFile_GetLine14765849
Ref: 47d814765849
Ref: c-api/file c PyFile_SetOpenCodeHook14766668
Ref: 162714766668
Ref: c-api/file c Py_OpenCodeHookFunction14766908
Ref: 4ab814766908
Ref: c-api/file c PyFile_WriteObject14768056
Ref: 47d914768056
Ref: c-api/file c PyFile_WriteString14768486
Ref: 47da14768486
Node: 模組物件14768735
Ref: c-api/module doc14768871
Ref: 4ab914768871
Ref: c-api/module module-objects14768871
Ref: 4aba14768871
Ref: c-api/module moduleobjects14768871
Ref: 4abb14768871
Ref: c-api/module c PyModule_Type14768910
Ref: 481014768910
Ref: c-api/module c PyModule_Check14769168
Ref: 4abc14769168
Ref: c-api/module c PyModule_CheckExact14769331
Ref: 4abd14769331
Ref: c-api/module c PyModule_NewObject14769514
Ref: 480e14769514
Ref: c-api/module c PyModule_New14770249
Ref: 480d14770249
Ref: c-api/module c PyModule_GetDict14770519
Ref: 480a14770519
Ref: c-api/module c PyModule_GetNameObject14771145
Ref: 480c14771145
Ref: c-api/module c PyModule_GetName14771554
Ref: 480b14771554
Ref: c-api/module c PyModule_GetState14771771
Ref: 92414771771
Ref: c-api/module c PyModule_GetDef14772055
Ref: 480914772055
Ref: c-api/module c PyModule_GetFilenameObject14772341
Ref: 3c114772341
Ref: c-api/module c PyModule_GetFilename14772830
Ref: 3c014772830
Node: 初始化 C 模組14773299
Ref: c-api/module initializing-c-modules14773387
Ref: 4abe14773387
Ref: c-api/module initializing-modules14773387
Ref: 473114773387
Ref: c-api/module c PyModuleDef14774004
Ref: 92114774004
Ref: c-api/module c PyModuleDef m_base14774307
Ref: 4abf14774307
Ref: c-api/module c PyModuleDef m_name14774430
Ref: 4ac014774430
Ref: c-api/module c PyModuleDef m_doc14774511
Ref: 4ac114774511
Ref: c-api/module c PyModuleDef m_size14774679
Ref: 92314774679
Ref: c-api/module c PyModuleDef m_methods14775656
Ref: 4ac214775656
Ref: c-api/module c PyModuleDef m_slots14775891
Ref: 4ac314775891
Ref: c-api/module c PyModuleDef m_slots m_reload14776285
Ref: 4ac514776285
Ref: c-api/module c PyModuleDef m_traverse14776351
Ref: 91e14776351
Ref: c-api/module c PyModuleDef m_clear14777090
Ref: 91f14777090
Ref: c-api/module c PyModuleDef m_free14778159
Ref: 92014778159
Ref: 初始化 C 模組-Footnote-114779049
Node: Single-phase initialization14779091
Ref: c-api/module single-phase-initialization14779208
Ref: 4ac714779208
Ref: c-api/module c PyModule_Create14779483
Ref: 46da14779483
Ref: c-api/module c PyModule_Create214779769
Ref: 480814779769
Node: Multi-phase initialization14780581
Ref: c-api/module id114780742
Ref: 4ac814780742
Ref: c-api/module multi-phase-initialization14780742
Ref: 473214780742
Ref: c-api/module c PyModuleDef_Init14782316
Ref: 480614782316
Ref: c-api/module c PyModuleDef_Slot14782838
Ref: 4ac414782838
Ref: c-api/module c PyModuleDef_Slot slot14782875
Ref: 4ac914782875
Ref: c-api/module c PyModuleDef_Slot value14782982
Ref: 4aca14782982
Ref: c-api/module c Py_mod_create14783208
Ref: 4acb14783208
Ref: c-api/module c Py_mod_create create_module14783402
Ref: 4acc14783402
Ref: c-api/module c Py_mod_exec14784831
Ref: 92214784831
Ref: c-api/module c Py_mod_exec exec_module14785104
Ref: 4acd14785104
Ref: c-api/module c Py_mod_multiple_interpreters14785289
Ref: 4ace14785289
Ref: c-api/module c Py_MOD_MULTIPLE_INTERPRETERS_NOT_SUPPORTED14785378
Ref: 4acf14785378
Ref: c-api/module c Py_MOD_MULTIPLE_INTERPRETERS_SUPPORTED14785515
Ref: 4ad014785515
Ref: c-api/module c Py_MOD_PER_INTERPRETER_GIL_SUPPORTED14785751
Ref: 4ad214785751
Ref: c-api/module c Py_mod_gil14786344
Ref: 13d14786344
Ref: c-api/module c Py_mod_gil Py_MOD_GIL_USED14786415
Ref: 4ad314786415
Ref: c-api/module c Py_mod_gil Py_MOD_GIL_NOT_USED14786608
Ref: 4ad414786608
Ref: Multi-phase initialization-Footnote-114787303
Ref: Multi-phase initialization-Footnote-214787345
Node: Low-level module creation functions14787387
Ref: c-api/module low-level-module-creation-functions14787536
Ref: 4ad514787536
Ref: c-api/module c PyModule_FromDefAndSpec14787915
Ref: e5414787915
Ref: c-api/module c PyModule_FromDefAndSpec214788301
Ref: e5514788301
Ref: c-api/module c PyModule_ExecDef14789058
Ref: e5614789058
Ref: c-api/module c PyModule_SetDocString14789305
Ref: 480f14789305
Ref: c-api/module c PyModule_AddFunctions14789714
Ref: 480714789714
Node: 支援的函式14790472
Ref: c-api/module support-functions14790586
Ref: 4ad614790586
Ref: c-api/module c PyModule_AddObjectRef14790863
Ref: 30814790863
Ref: c-api/module c PyModule_Add14792725
Ref: 30714792725
Ref: c-api/module c PyModule_AddObject14793308
Ref: 30914793308
Ref: c-api/module c PyModule_AddIntConstant14794750
Ref: 14aa14794750
Ref: c-api/module c PyModule_AddStringConstant14795281
Ref: 14ab14795281
Ref: c-api/module c PyModule_AddIntMacro14795887
Ref: 136114795887
Ref: c-api/module c PyModule_AddStringMacro14796245
Ref: 136014796245
Ref: c-api/module c PyModule_AddType14796341
Ref: 91914796341
Ref: c-api/module c PyUnstable_Module_SetGIL14796811
Ref: 15d14796811
Node: 模組查找14797670
Ref: c-api/module module-lookup14797758
Ref: 4ad714797758
Ref: c-api/module c PyState_FindModule14798171
Ref: 485e14798171
Ref: c-api/module c PyState_AddModule14798707
Ref: 485d14798707
Ref: c-api/module c PyState_RemoveModule14799745
Ref: 485f14799745
Node: 疊代器（Iterator）物件14800090
Ref: c-api/iterator doc14800232
Ref: 4ad814800232
Ref: c-api/iterator id114800232
Ref: 4ad914800232
Ref: c-api/iterator iterator-objects14800232
Ref: 4ada14800232
Ref: c-api/iterator c PySeqIter_Type14800654
Ref: 484714800654
Ref: c-api/iterator c PySeqIter_Check14800937
Ref: 4adb14800937
Ref: c-api/iterator c PySeqIter_New14801092
Ref: 484614801092
Ref: c-api/iterator c PyCallIter_Type14801422
Ref: 479314801422
Ref: c-api/iterator c PyCallIter_Check14801683
Ref: 4adc14801683
Ref: c-api/iterator c PyCallIter_New14801840
Ref: 479214801840
Node: Descriptor（描述器）物件14802326
Ref: c-api/descriptor doc14802468
Ref: 4add14802468
Ref: c-api/descriptor descriptor-objects14802468
Ref: 4ade14802468
Ref: c-api/descriptor id114802468
Ref: 4adf14802468
Ref: c-api/descriptor c PyProperty_Type14802658
Ref: 484514802658
Ref: c-api/descriptor c PyDescr_NewGetSet14802812
Ref: 47b014802812
Ref: c-api/descriptor c PyDescr_NewMember14803003
Ref: 47b114803003
Ref: c-api/descriptor c PyDescr_NewMethod14803192
Ref: 189014803192
Ref: c-api/descriptor c PyDescr_NewWrapper14803381
Ref: 4ae014803381
Ref: c-api/descriptor c PyDescr_NewClassMethod14803547
Ref: 47af14803547
Ref: c-api/descriptor c PyDescr_IsData14803736
Ref: 17f814803736
Ref: c-api/descriptor c PyWrapper_New14804015
Ref: 48b114804015
Node: 切片物件14804166
Ref: c-api/slice doc14804296
Ref: 4ae114804296
Ref: c-api/slice id114804296
Ref: 4ae214804296
Ref: c-api/slice slice-objects14804296
Ref: 4ae314804296
Ref: c-api/slice c PySlice_Type14804337
Ref: 485c14804337
Ref: c-api/slice c PySlice_Check14804544
Ref: 4ae414804544
Ref: c-api/slice c PySlice_New14804702
Ref: 485b14804702
Ref: c-api/slice c PySlice_GetIndices14805281
Ref: 485a14805281
Ref: c-api/slice c PySlice_GetIndicesEx14806045
Ref: 3c414806045
Ref: c-api/slice c PySlice_Unpack14808046
Ref: 3c514808046
Ref: c-api/slice c PySlice_AdjustIndices14808721
Ref: 3c614808721
Node: Ellipsis Object14809271
Ref: c-api/slice ellipsis-object14809335
Ref: 4ae514809335
Ref: c-api/slice c Py_Ellipsis14809386
Ref: 4ae614809386
Ref: c-api/memoryview memoryview-objects14809671
Ref: 499614809671
Node: MemoryView 物件14809671
Ref: c-api/memoryview doc14809788
Ref: 4ae714809788
Ref: c-api/memoryview id114809788
Ref: 4ae814809788
Ref: c-api/memoryview c PyMemoryView_FromObject14809997
Ref: 480414809997
Ref: c-api/memoryview c PyBUF_READ14810432
Ref: 158614810432
Ref: c-api/memoryview c PyBUF_WRITE14810499
Ref: 158714810499
Ref: c-api/memoryview c PyMemoryView_FromMemory14810567
Ref: 110914810567
Ref: c-api/memoryview c PyMemoryView_FromBuffer14810962
Ref: 70514810962
Ref: c-api/memoryview c PyMemoryView_GetContiguous14811337
Ref: 480514811337
Ref: c-api/memoryview c PyMemoryView_Check14811962
Ref: 4ae914811962
Ref: c-api/memoryview c PyMemoryView_GET_BUFFER14812195
Ref: 4aea14812195
Ref: c-api/memoryview c PyMemoryView_GET_BASE14812509
Ref: 4aeb14812509
Node: 弱參照物件<2>14812897
Ref: c-api/weakref doc14813013
Ref: 4aec14813013
Ref: c-api/weakref weak-reference-objects14813013
Ref: 4aed14813013
Ref: c-api/weakref weakrefobjects14813013
Ref: 4aee14813013
Ref: c-api/weakref c PyWeakref_Check14813312
Ref: 4aef14813312
Ref: c-api/weakref c PyWeakref_CheckRef14813467
Ref: 4af014813467
Ref: c-api/weakref c PyWeakref_CheckProxy14813610
Ref: 4af114813610
Ref: c-api/weakref c PyWeakref_NewRef14813751
Ref: 175314813751
Ref: c-api/weakref c PyWeakref_NewProxy14814580
Ref: 48b014814580
Ref: c-api/weakref c PyWeakref_GetRef14815413
Ref: 2f014815413
Ref: c-api/weakref c PyWeakref_GetObject14815951
Ref: 2f114815951
Ref: c-api/weakref c PyWeakref_GET_OBJECT14816692
Ref: 38a14816692
Ref: c-api/weakref c PyObject_ClearWeakRefs14816998
Ref: 51c14816998
Ref: c-api/weakref c PyUnstable_Object_ClearWeakRefsNoCallbacks14817383
Ref: 150614817383
Node: Capsules<2>14818312
Ref: c-api/capsule doc14818423
Ref: 4af214818423
Ref: c-api/capsule capsules14818423
Ref: 245e14818423
Ref: c-api/capsule id114818423
Ref: 4af314818423
Ref: c-api/capsule c PyCapsule14818593
Ref: 120b14818593
Ref: c-api/capsule c PyCapsule_Destructor14819038
Ref: 479514819038
Ref: c-api/capsule c PyCapsule_CheckExact14819353
Ref: 4af414819353
Ref: c-api/capsule c PyCapsule_New14819506
Ref: 46f914819506
Ref: c-api/capsule c PyCapsule_GetPointer14820471
Ref: 479914820471
Ref: c-api/capsule c PyCapsule_GetDestructor14820977
Ref: 479714820977
Ref: c-api/capsule c PyCapsule_GetContext14821469
Ref: 479614821469
Ref: c-api/capsule c PyCapsule_GetName14821914
Ref: 479814821914
Ref: c-api/capsule c PyCapsule_Import14822351
Ref: 177014822351
Ref: c-api/capsule c PyCapsule_IsValid14822897
Ref: 12e914822897
Ref: c-api/capsule c PyCapsule_SetContext14823711
Ref: 479a14823711
Ref: c-api/capsule c PyCapsule_SetDestructor14823982
Ref: 479b14823982
Ref: c-api/capsule c PyCapsule_SetName14824282
Ref: 479c14824282
Ref: c-api/capsule c PyCapsule_SetPointer14824701
Ref: 479d14824701
Node: Frame 物件14825005
Ref: c-api/frame doc14825124
Ref: 4af514825124
Ref: c-api/frame frame-objects14825124
Ref: 4af614825124
Ref: c-api/frame c PyFrameObject14825167
Ref: 72d14825167
Ref: c-api/frame c PyFrame_Type14825712
Ref: 72b14825712
Ref: c-api/frame c PyFrame_Check14825993
Ref: 72914825993
Ref: c-api/frame c PyFrame_GetBack14826210
Ref: 72a14826210
Ref: c-api/frame c PyFrame_GetBuiltins14826492
Ref: 70f14826492
Ref: c-api/frame c PyFrame_GetCode14826773
Ref: 72e14826773
Ref: c-api/frame c PyFrame_GetGenerator14827117
Ref: 71014827117
Ref: c-api/frame c PyFrame_GetGlobals14827545
Ref: 71114827545
Ref: c-api/frame c PyFrame_GetLasti14827824
Ref: 71214827824
Ref: c-api/frame c PyFrame_GetVar14828031
Ref: 50e14828031
Ref: c-api/frame c PyFrame_GetVarString14828506
Ref: 50f14828506
Ref: c-api/frame c PyFrame_GetLocals14828778
Ref: 35f14828778
Ref: c-api/frame c PyFrame_GetLineNumber14829462
Ref: 72f14829462
Ref: Frame 物件-Footnote-114829729
Node: Internal Frames14829771
Ref: c-api/frame internal-frames14829835
Ref: 4af714829835
Ref: c-api/frame c _PyInterpreterFrame14829936
Ref: 4af814829936
Ref: c-api/frame c PyUnstable_InterpreterFrame_GetCode14830062
Ref: 4af914830062
Ref: c-api/frame c PyUnstable_InterpreterFrame_GetLasti14830504
Ref: 4afa14830504
Ref: c-api/frame c PyUnstable_InterpreterFrame_GetLine14830901
Ref: 4afb14830901
Ref: Internal Frames-Footnote-114831357
Node: 產生器 Generator 物件14831399
Ref: c-api/gen doc14831534
Ref: 4afc14831534
Ref: c-api/gen gen-objects14831534
Ref: 4afd14831534
Ref: c-api/gen generator-objects14831534
Ref: 4afe14831534
Ref: c-api/gen c PyGenObject14831846
Ref: 4b0114831846
Ref: c-api/gen c PyGen_Type14831921
Ref: 4b0214831921
Ref: c-api/gen c PyGen_Check14832021
Ref: 4b0314832021
Ref: c-api/gen c PyGen_CheckExact14832210
Ref: 4b0414832210
Ref: c-api/gen c PyGen_New14832405
Ref: 4aff14832405
Ref: c-api/gen c PyGen_NewWithQualName14832680
Ref: 4b0014832680
Node: Coroutine（協程）物件14833086
Ref: c-api/coro doc14833227
Ref: 4b0514833227
Ref: c-api/coro coro-objects14833227
Ref: e7214833227
Ref: c-api/coro coroutine-objects14833227
Ref: 4b0614833227
Ref: c-api/coro c PyCoroObject14833410
Ref: 4b0714833410
Ref: c-api/coro c PyCoro_Type14833488
Ref: 4b0814833488
Ref: c-api/coro c PyCoro_CheckExact14833591
Ref: 4b0914833591
Ref: c-api/coro c PyCoro_New14833788
Ref: 4b0a14833788
Node: 情境變數物件14834206
Ref: c-api/contextvars doc14834336
Ref: 4b0b14834336
Ref: c-api/contextvars context-variables-objects14834336
Ref: 4b0c14834336
Ref: c-api/contextvars contextvarsobjects14834336
Ref: a9b14834336
Ref: c-api/contextvars contextvarsobjects-pointertype-change14834387
Ref: bcd14834387
Ref: c-api/contextvars c PyContext14834928
Ref: 4b0d14834928
Ref: c-api/contextvars c PyContextVar14835046
Ref: 4b0e14835046
Ref: c-api/contextvars c PyContextToken14835170
Ref: 4b0f14835170
Ref: c-api/contextvars c PyContext_Type14835291
Ref: 4b1014835291
Ref: c-api/contextvars c PyContextVar_Type14835401
Ref: 4b1114835401
Ref: c-api/contextvars c PyContextToken_Type14835523
Ref: 4b1214835523
Ref: c-api/contextvars c PyContext_CheckExact14835673
Ref: 4b1314835673
Ref: c-api/contextvars c PyContextVar_CheckExact14835857
Ref: 4b1414835857
Ref: c-api/contextvars c PyContextToken_CheckExact14836047
Ref: 4b1514836047
Ref: c-api/contextvars c PyContext_New14836279
Ref: 4b1614836279
Ref: c-api/contextvars c PyContext_Copy14836458
Ref: 4b1714836458
Ref: c-api/contextvars c PyContext_CopyCurrent14836670
Ref: 4b1814836670
Ref: c-api/contextvars c PyContext_Enter14836875
Ref: 4b1914836875
Ref: c-api/contextvars c PyContext_Exit14837046
Ref: 4b1a14837046
Ref: c-api/contextvars c PyContextVar_New14837302
Ref: 4b1b14837302
Ref: c-api/contextvars c PyContextVar_Get14837725
Ref: 4b1c14837725
Ref: c-api/contextvars c PyContextVar_Set14838346
Ref: 4b1d14838346
Ref: c-api/contextvars c PyContextVar_Reset14838631
Ref: 4b1e14838631
Ref: 情境變數物件-Footnote-114838965
Node: DateTime 物件14839030
Ref: c-api/datetime doc14839151
Ref: 4b1f14839151
Ref: c-api/datetime datetime-objects14839151
Ref: 4b2014839151
Ref: c-api/datetime datetimeobjects14839151
Ref: 494d14839151
Ref: c-api/datetime c PyDateTime_Date14839644
Ref: 4b2114839644
Ref: c-api/datetime c PyDateTime_DateTime14839761
Ref: 4b2214839761
Ref: c-api/datetime c PyDateTime_Time14839886
Ref: 4b2314839886
Ref: c-api/datetime c PyDateTime_Delta14840003
Ref: 4b2414840003
Ref: c-api/datetime c PyDateTime_DateType14840143
Ref: 4b2514840143
Ref: c-api/datetime c PyDateTime_DateTimeType14840366
Ref: 4b2614840366
Ref: c-api/datetime c PyDateTime_TimeType14840601
Ref: 4b2714840601
Ref: c-api/datetime c PyDateTime_DeltaType14840824
Ref: 4b2814840824
Ref: c-api/datetime c PyDateTime_TZInfoType14841091
Ref: 4b2914841091
Ref: c-api/datetime c PyDateTime_TimeZone_UTC14841378
Ref: b6a14841378
Ref: c-api/datetime c PyDate_Check14841597
Ref: 4b2a14841597
Ref: c-api/datetime c PyDate_CheckExact14841847
Ref: 4b2b14841847
Ref: c-api/datetime c PyDateTime_Check14842053
Ref: 4b2c14842053
Ref: c-api/datetime c PyDateTime_CheckExact14842313
Ref: 4b2d14842313
Ref: c-api/datetime c PyTime_Check14842526
Ref: 4b2e14842526
Ref: c-api/datetime c PyTime_CheckExact14842775
Ref: 4b2f14842775
Ref: c-api/datetime c PyDelta_Check14842981
Ref: 4b3014842981
Ref: c-api/datetime c PyDelta_CheckExact14843233
Ref: 4b3114843233
Ref: c-api/datetime c PyTZInfo_Check14843441
Ref: 4b3214843441
Ref: c-api/datetime c PyTZInfo_CheckExact14843696
Ref: 4b3314843696
Ref: c-api/datetime c PyDate_FromDate14843932
Ref: 4b3414843932
Ref: c-api/datetime c PyDateTime_FromDateAndTime14844141
Ref: 4b3514844141
Ref: c-api/datetime c PyDateTime_FromDateAndTimeAndFold14844450
Ref: 4b3614844450
Ref: c-api/datetime c PyTime_FromTime14844829
Ref: 4b3714844829
Ref: c-api/datetime c PyTime_FromTimeAndFold14845064
Ref: 4b3814845064
Ref: c-api/datetime c PyDelta_FromDSU14845371
Ref: 4b3914845371
Ref: c-api/datetime c PyTimeZone_FromOffset14845748
Ref: b6814845748
Ref: c-api/datetime c PyTimeZone_FromOffsetAndName14846017
Ref: b6914846017
Ref: c-api/datetime c PyDateTime_GET_YEAR14846546
Ref: 4b3a14846546
Ref: c-api/datetime c PyDateTime_GET_MONTH14846643
Ref: 4b3b14846643
Ref: c-api/datetime c PyDateTime_GET_DAY14846756
Ref: 4b3c14846756
Ref: c-api/datetime c PyDateTime_DATE_GET_HOUR14847054
Ref: 4b3d14847054
Ref: c-api/datetime c PyDateTime_DATE_GET_MINUTE14847175
Ref: 4b3e14847175
Ref: c-api/datetime c PyDateTime_DATE_GET_SECOND14847298
Ref: 4b3f14847298
Ref: c-api/datetime c PyDateTime_DATE_GET_MICROSECOND14847416
Ref: 4b4014847416
Ref: c-api/datetime c PyDateTime_DATE_GET_FOLD14847548
Ref: 4b4114847548
Ref: c-api/datetime c PyDateTime_DATE_GET_TZINFO14847693
Ref: 83914847693
Ref: c-api/datetime c PyDateTime_TIME_GET_HOUR14848048
Ref: 4b4214848048
Ref: c-api/datetime c PyDateTime_TIME_GET_MINUTE14848165
Ref: 4b4314848165
Ref: c-api/datetime c PyDateTime_TIME_GET_SECOND14848284
Ref: 4b4414848284
Ref: c-api/datetime c PyDateTime_TIME_GET_MICROSECOND14848398
Ref: 4b4514848398
Ref: c-api/datetime c PyDateTime_TIME_GET_FOLD14848526
Ref: 4b4614848526
Ref: c-api/datetime c PyDateTime_TIME_GET_TZINFO14848667
Ref: 83a14848667
Ref: c-api/datetime c PyDateTime_DELTA_GET_DAYS14849025
Ref: 4b4714849025
Ref: c-api/datetime c PyDateTime_DELTA_GET_SECONDS14849192
Ref: 4b4814849192
Ref: c-api/datetime c PyDateTime_DELTA_GET_MICROSECONDS14849349
Ref: 4b4914849349
Ref: c-api/datetime c PyDateTime_FromTimestamp14849561
Ref: 4b4a14849561
Ref: c-api/datetime c PyDate_FromTimestamp14849856
Ref: 191414849856
Node: 型別提示物件14850129
Ref: c-api/typehints doc14850223
Ref: 4b4b14850223
Ref: c-api/typehints objects-for-type-hinting14850223
Ref: 4b4c14850223
Ref: c-api/typehints typehintobjects14850223
Ref: 4b4d14850223
Ref: c-api/typehints c Py_GenericAlias14850447
Ref: 48b514850447
Ref: c-api/typehints c Py_GenericAliasType14851867
Ref: 48b614851867
Node: Initialization Finalization and Threads14852158
Ref: c-api/init doc14852314
Ref: 4b4e14852314
Ref: c-api/init initialization14852314
Ref: 4b4f14852314
Ref: c-api/init initialization-finalization-and-threads14852314
Ref: 4b5014852314
Node: Python 初始化之前14852857
Ref: c-api/init before-python-initialization14852994
Ref: 4b5114852994
Ref: c-api/init pre-init-safe14852994
Ref: b6c14852994
Node: Global configuration variables14854900
Ref: c-api/init global-conf-vars14855089
Ref: 4b5214855089
Ref: c-api/init global-configuration-variables14855089
Ref: 4b5714855089
Ref: c-api/init c Py_BytesWarningFlag14855561
Ref: 39f14855561
Ref: c-api/init c Py_DebugFlag14856092
Ref: 39114856092
Ref: c-api/init c Py_DontWriteBytecodeFlag14856552
Ref: 3a514856552
Ref: c-api/init c Py_FrozenFlag14857055
Ref: 3a114857055
Ref: c-api/init c Py_HashRandomizationFlag14857526
Ref: 3ab14857526
Ref: c-api/init c Py_IgnoreEnvironmentFlag14858099
Ref: 3a314858099
Ref: c-api/init c Py_InspectFlag14858586
Ref: 39914858586
Ref: c-api/init c Py_InteractiveFlag14859182
Ref: 39714859182
Ref: c-api/init c Py_IsolatedFlag14859475
Ref: 3ae14859475
Ref: c-api/init c Py_LegacyWindowsFSEncodingFlag14859989
Ref: 3b014859989
Ref: c-api/init c Py_LegacyWindowsStdioFlag14860743
Ref: 3b214860743
Ref: c-api/init c Py_NoSiteFlag14861382
Ref: 39d14861382
Ref: c-api/init c Py_NoUserSiteDirectory14862006
Ref: 3a714862006
Ref: c-api/init c Py_OptimizeFlag14862512
Ref: 39b14862512
Ref: c-api/init c Py_QuietFlag14862887
Ref: 39514862887
Ref: c-api/init c Py_UnbufferedStdioFlag14863317
Ref: 3a914863317
Ref: c-api/init c Py_VerboseFlag14863764
Ref: 39314863764
Ref: Global configuration variables-Footnote-114864479
Ref: Global configuration variables-Footnote-214864521
Node: Initializing and finalizing the interpreter14864563
Ref: c-api/init initializing-and-finalizing-the-interpreter14864753
Ref: 4b5814864753
Ref: c-api/init c Py_Initialize14864854
Ref: 85114864854
Ref: c-api/init c Py_InitializeEx14866066
Ref: 48bc14866066
Ref: c-api/init c Py_IsInitialized14866522
Ref: 476d14866522
Ref: c-api/init c Py_IsFinalizing14866833
Ref: 31414866833
Ref: c-api/init c Py_FinalizeEx14867097
Ref: cbc14867097
Ref: c-api/init c Py_Finalize14869583
Ref: 12e614869583
Node: Process-wide parameters14869781
Ref: c-api/init process-wide-parameters14869985
Ref: 4b5914869985
Ref: c-api/init c Py_SetProgramName14870046
Ref: 153214870046
Ref: c-api/init c Py_GetProgramName14871211
Ref: 38414871211
Ref: c-api/init c Py_GetPrefix14871831
Ref: 38014871831
Ref: c-api/init c Py_GetExecPrefix14872987
Ref: 37c14872987
Ref: c-api/init c Py_GetProgramFullPath14875545
Ref: 38214875545
Ref: c-api/init c Py_GetPath14876363
Ref: 37e14876363
Ref: c-api/init c Py_GetVersion14877445
Ref: 48ba14877445
Ref: c-api/init c Py_GetPlatform14878094
Ref: 48b914878094
Ref: c-api/init c Py_GetCopyright14878726
Ref: 48b814878726
Ref: c-api/init c Py_GetCompiler14879150
Ref: 48b714879150
Ref: c-api/init c Py_GetBuildInfo14879579
Ref: 139f14879579
Ref: c-api/init c PySys_SetArgvEx14880035
Ref: 153314880035
Ref: c-api/init c PySys_SetArgv14882475
Ref: 153414882475
Ref: c-api/init c Py_SetPythonHome14883320
Ref: 153114883320
Ref: c-api/init c Py_GetPythonHome14884153
Ref: 38514884153
Ref: Process-wide parameters-Footnote-114884839
Node: Thread State and the Global Interpreter Lock14884908
Ref: c-api/init thread-state-and-the-global-interpreter-lock14885092
Ref: 4b5a14885092
Ref: c-api/init threads14885092
Ref: 4b5b14885092
Node: Releasing the GIL from extension code14886621
Ref: c-api/init releasing-the-gil-from-extension-code14886774
Ref: 4b5c14886774
Node: Non-Python created threads14888649
Ref: c-api/init gilstate14888830
Ref: 4b5d14888830
Ref: c-api/init non-python-created-threads14888830
Ref: 4b5e14888830
Node: Cautions about fork14890581
Ref: c-api/init cautions-about-fork14890735
Ref: 4b5f14890735
Ref: c-api/init fork-and-threads14890735
Ref: 491914890735
Node: 高階 API14892652
Ref: c-api/init high-level-api14892790
Ref: 4b6014892790
Ref: c-api/init c PyInterpreterState14892954
Ref: 86214892954
Ref: c-api/init c PyThreadState14893628
Ref: 73114893628
Ref: c-api/init c PyThreadState interp14893866
Ref: 4b6114893866
Ref: c-api/init c PyEval_InitThreads14893975
Ref: 153514893975
Ref: c-api/init c PyEval_SaveThread14894551
Ref: 37314894551
Ref: c-api/init c PyEval_RestoreThread14894917
Ref: 37414894917
Ref: c-api/init c PyThreadState_Get14895692
Ref: 31f14895692
Ref: c-api/init c PyThreadState_GetUnchecked14896074
Ref: 31e14896074
Ref: c-api/init c PyThreadState_Swap14896456
Ref: 486c14896456
Ref: c-api/init c PyGILState_Ensure14896884
Ref: 37614896884
Ref: c-api/init c PyGILState_Release14898658
Ref: 37714898658
Ref: c-api/init c PyGILState_GetThisThreadState14899184
Ref: 47df14899184
Ref: c-api/init c PyGILState_Check14899631
Ref: 4b6214899631
Ref: c-api/init c Py_BEGIN_ALLOW_THREADS14900364
Ref: 46f314900364
Ref: c-api/init c Py_END_ALLOW_THREADS14900719
Ref: a3114900719
Ref: c-api/init c Py_BLOCK_THREADS14901051
Ref: 48b314901051
Ref: c-api/init c Py_UNBLOCK_THREADS14901280
Ref: 48bf14901280
Node: 低階 API14901544
Ref: c-api/init low-level-api14901654
Ref: 4b6314901654
Ref: c-api/init c PyInterpreterState_New14901859
Ref: 3ff514901859
Ref: c-api/init c PyInterpreterState_Clear14902256
Ref: 3ff414902256
Ref: c-api/init c PyInterpreterState_Delete14902595
Ref: 47eb14902595
Ref: c-api/init c PyThreadState_New14902926
Ref: 486b14902926
Ref: c-api/init c PyThreadState_Clear14903284
Ref: 151514903284
Ref: c-api/init c PyThreadState_Delete14903665
Ref: 18a414903665
Ref: c-api/init c PyThreadState_DeleteCurrent14903969
Ref: 18d814903969
Ref: c-api/init c PyThreadState_GetFrame14904305
Ref: 73214904305
Ref: c-api/init c PyThreadState_GetID14904761
Ref: 91614904761
Ref: c-api/init c PyThreadState_GetInterpreter14905049
Ref: 91514905049
Ref: c-api/init c PyThreadState_EnterTracing14905360
Ref: 6f814905360
Ref: c-api/init c PyThreadState_LeaveTracing14905617
Ref: 6f914905617
Ref: c-api/init c PyInterpreterState_Get14905960
Ref: 37814905960
Ref: c-api/init c PyInterpreterState_GetID14906338
Ref: b6d14906338
Ref: c-api/init c PyInterpreterState_GetDict14906688
Ref: 47ec14906688
Ref: c-api/init c _PyFrameEvalFunction14907273
Ref: 71a14907273
Ref: c-api/init c _PyInterpreterState_GetEvalFrameFunc14907821
Ref: 189214907821
Ref: c-api/init c _PyInterpreterState_SetEvalFrameFunc14908093
Ref: 189314908093
Ref: c-api/init c PyThreadState_GetDict14908360
Ref: 486a14908360
Ref: c-api/init c PyThreadState_SetAsyncExc14908907
Ref: b6b14908907
Ref: c-api/init c PyEval_AcquireThread14909727
Ref: 37514909727
Ref: c-api/init c PyEval_ReleaseThread14910878
Ref: 47d114910878
Ref: 低階 API-Footnote-114911525
Ref: 低階 API-Footnote-214911567
Node: Sub-interpreter support14911609
Ref: c-api/init id114911796
Ref: 4b6414911796
Ref: c-api/init sub-interpreter-support14911796
Ref: 52d14911796
Ref: c-api/init c PyInterpreterConfig14912723
Ref: 51314912723
Ref: c-api/init c PyInterpreterConfig use_main_obmalloc14913012
Ref: 4b6614913012
Ref: c-api/init c PyInterpreterConfig allow_fork14913454
Ref: 4b6a14913454
Ref: c-api/init c PyInterpreterConfig allow_exec14913794
Ref: 4b6b14913794
Ref: c-api/init c PyInterpreterConfig allow_threads14914194
Ref: 4b6c14914194
Ref: c-api/init c PyInterpreterConfig allow_daemon_threads14914387
Ref: 4b6d14914387
Ref: c-api/init c PyInterpreterConfig check_multi_interp_extensions14914673
Ref: 4b6714914673
Ref: c-api/init c PyInterpreterConfig gil14915202
Ref: 4b6814915202
Ref: c-api/init c PyInterpreterConfig_DEFAULT_GIL14915356
Ref: 4b6e14915356
Ref: c-api/init c PyInterpreterConfig_SHARED_GIL14915517
Ref: 4b6f14915517
Ref: c-api/init c PyInterpreterConfig_OWN_GIL14915629
Ref: 4b6914915629
Ref: c-api/init c Py_NewInterpreterFromConfig14915879
Ref: 40214915879
Ref: c-api/init c Py_NewInterpreter14920224
Ref: 16b914920224
Ref: c-api/init c Py_EndInterpreter14920701
Ref: 176214920701
Ref: Sub-interpreter support-Footnote-114921504
Node: A Per-Interpreter GIL14921546
Ref: c-api/init a-per-interpreter-gil14921652
Ref: 4b7114921652
Ref: A Per-Interpreter GIL-Footnote-114923696
Node: Bugs and caveats14923738
Ref: c-api/init bugs-and-caveats14923844
Ref: 4b7014923844
Node: Asynchronous Notifications14925441
Ref: c-api/init asynchronous-notifications14925605
Ref: 4b7214925605
Ref: c-api/init c Py_AddPendingCall14925850
Ref: 92514925850
Node: Profiling and Tracing14927999
Ref: c-api/init profiling14928157
Ref: 4b7314928157
Ref: c-api/init profiling-and-tracing14928157
Ref: 4b7414928157
Ref: c-api/init c Py_tracefunc14928836
Ref: 4b7514928836
Ref: c-api/init c PyTrace_CALL14931181
Ref: 4b7614931181
Ref: c-api/init c PyTrace_EXCEPTION14931569
Ref: 4b7714931569
Ref: c-api/init c PyTrace_LINE14932177
Ref: 4b7814932177
Ref: c-api/init c PyTrace_RETURN14932477
Ref: 4b7914932477
Ref: c-api/init c PyTrace_C_CALL14932628
Ref: 4b7a14932628
Ref: c-api/init c PyTrace_C_EXCEPTION14932788
Ref: 4b7b14932788
Ref: c-api/init c PyTrace_C_RETURN14932955
Ref: 4b7c14932955
Ref: c-api/init c PyTrace_OPCODE14933108
Ref: 4b7d14933108
Ref: c-api/init c PyEval_SetProfile14933446
Ref: 146b14933446
Ref: c-api/init c PyEval_SetProfileAllThreads14934124
Ref: 50414934124
Ref: c-api/init c PyEval_SetTrace14934634
Ref: 146c14934634
Ref: c-api/init c PyEval_SetTraceAllThreads14935310
Ref: 50514935310
Node: Reference tracing14935807
Ref: c-api/init reference-tracing14935964
Ref: 4b7e14935964
Ref: c-api/init c PyRefTracer14936037
Ref: 4b7f14936037
Ref: c-api/init c PyRefTracer_CREATE14936601
Ref: 4b8014936601
Ref: c-api/init c PyRefTracer_DESTROY14936763
Ref: 4b8114936763
Ref: c-api/init c PyRefTracer_SetTracer14936928
Ref: 34314936928
Ref: c-api/init c PyRefTracer_GetTracer14937710
Ref: 34414937710
Node: Advanced Debugger Support14938151
Ref: c-api/init advanced-debugger-support14938315
Ref: 4b8214938315
Ref: c-api/init advanced-debugging14938315
Ref: 4b8314938315
Ref: c-api/init c PyInterpreterState_Head14938457
Ref: 146f14938457
Ref: c-api/init c PyInterpreterState_Main14938623
Ref: 4b6514938623
Ref: c-api/init c PyInterpreterState_Next14938745
Ref: 147014938745
Ref: c-api/init c PyInterpreterState_ThreadHead14938957
Ref: 147114938957
Ref: c-api/init c PyThreadState_Next14939209
Ref: 147214939209
Node: Thread Local Storage Support14939466
Ref: c-api/init thread-local-storage14939639
Ref: 4b8414939639
Ref: c-api/init thread-local-storage-support14939639
Ref: 4b8514939639
Node: Thread Specific Storage TSS API14940799
Ref: c-api/init thread-specific-storage-api14940957
Ref: a8114940957
Ref: c-api/init thread-specific-storage-tss-api14940957
Ref: 4b8614940957
Ref: c-api/init c Py_tss_t14941338
Ref: a8214941338
Ref: c-api/init c Py_tss_NEEDS_INIT14941782
Ref: 4b8714941782
Ref: Thread Specific Storage TSS API-Footnote-114942056
Node: Dynamic Allocation14942098
Ref: c-api/init dynamic-allocation14942199
Ref: 4b8814942199
Ref: c-api/init c PyThread_tss_alloc14942479
Ref: 3cd14942479
Ref: c-api/init c PyThread_tss_free14942779
Ref: 3cf14942779
Node: 方法14943270
Ref: c-api/init methods14943371
Ref: 4b8914943371
Ref: c-api/init c PyThread_tss_is_created14943671
Ref: 486e14943671
Ref: c-api/init c PyThread_tss_create14943928
Ref: 486d14943928
Ref: c-api/init c PyThread_tss_delete14944411
Ref: 3d514944411
Ref: c-api/init c PyThread_tss_set14944907
Ref: 3d114944907
Ref: c-api/init c PyThread_tss_get14945232
Ref: 3d314945232
Node: 執行緒局部儲存 Thread Local Storage TLS API：14945531
Ref: c-api/init thread-local-storage-api14945689
Ref: a8014945689
Ref: c-api/init thread-local-storage-tls-api14945689
Ref: 4b8a14945689
Ref: c-api/init c PyThread_create_key14946356
Ref: 3cc14946356
Ref: c-api/init c PyThread_delete_key14946446
Ref: 3ce14946446
Ref: c-api/init c PyThread_set_key_value14946544
Ref: 3d014946544
Ref: c-api/init c PyThread_get_key_value14946657
Ref: 3d214946657
Ref: c-api/init c PyThread_delete_key_value14946759
Ref: 3d414946759
Ref: c-api/init c PyThread_ReInitTLS14946863
Ref: 3d614946863
Node: Synchronization Primitives14946953
Ref: c-api/init synchronization-primitives14947092
Ref: 4b8b14947092
Ref: c-api/init c PyMutex14947212
Ref: 14014947212
Ref: c-api/init c PyMutex_Lock14947838
Ref: 34b14947838
Ref: c-api/init c PyMutex_Unlock14948138
Ref: 4b5614948138
Node: Python Critical Section API14948365
Ref: c-api/init id214948455
Ref: 4b8c14948455
Ref: c-api/init python-critical-section-api14948455
Ref: 4b8d14948455
Ref: c-api/init c Py_BEGIN_CRITICAL_SECTION14950515
Ref: 4a6914950515
Ref: c-api/init c Py_END_CRITICAL_SECTION14950914
Ref: 4b8f14950914
Ref: c-api/init c Py_BEGIN_CRITICAL_SECTION214951226
Ref: 4b8e14951226
Ref: c-api/init c Py_END_CRITICAL_SECTION214951765
Ref: 4b9014951765
Node: Python 初始化設定14952081
Ref: c-api/init_config doc14952237
Ref: 4b9114952237
Ref: c-api/init_config init-config14952237
Ref: 37214952237
Ref: c-api/init_config python-initialization-configuration14952237
Ref: 4b9214952237
Ref: Python 初始化設定-Footnote-114953697
Node: 範例<51>14953739
Ref: c-api/init_config example14953833
Ref: 4b9514953833
Node: PyWideStringList14954838
Ref: c-api/init_config pywidestringlist14954949
Ref: 4b9614954949
Ref: c-api/init_config c PyWideStringList14954998
Ref: 95214954998
Ref: c-api/init_config c PyWideStringList_Append14955195
Ref: 96314955195
Ref: c-api/init_config c PyWideStringList_Insert14955421
Ref: 96414955421
Ref: c-api/init_config c PyWideStringList length14955878
Ref: 4b9714955878
Ref: c-api/init_config c PyWideStringList items14955961
Ref: 4b9814955961
Node: PyStatus14956026
Ref: c-api/init_config pystatus14956138
Ref: 4b9914956138
Ref: c-api/init_config c PyStatus14956171
Ref: 95114956171
Ref: c-api/init_config c PyStatus exitcode14956396
Ref: 4b9a14956396
Ref: c-api/init_config c PyStatus err_msg14956491
Ref: 4b9b14956491
Ref: c-api/init_config c PyStatus func14956564
Ref: 4b9c14956564
Ref: c-api/init_config c PyStatus_Ok14956718
Ref: 96214956718
Ref: c-api/init_config c PyStatus_Error14956798
Ref: 95c14956798
Ref: c-api/init_config c PyStatus_NoMemory14956984
Ref: 96114956984
Ref: c-api/init_config c PyStatus_Exit14957104
Ref: 95e14957104
Ref: c-api/init_config c PyStatus_Exception14957263
Ref: 95d14957263
Ref: c-api/init_config c PyStatus_IsError14957492
Ref: 95f14957492
Ref: c-api/init_config c PyStatus_IsExit14957586
Ref: 96014957586
Ref: c-api/init_config c Py_ExitStatusException14957678
Ref: 96614957678
Node: PyPreConfig14958620
Ref: c-api/init_config pypreconfig14958753
Ref: 4b9d14958753
Ref: c-api/init_config c PyPreConfig14958792
Ref: 95014958792
Ref: c-api/init_config c PyPreConfig_InitPythonConfig14958919
Ref: 95b14958919
Ref: c-api/init_config c PyPreConfig_InitIsolatedConfig14959105
Ref: 95a14959105
Ref: c-api/init_config c PyPreConfig allocator14959319
Ref: 4b9e14959319
Ref: c-api/init_config c PyPreConfig configure_locale14961113
Ref: 4ba014961113
Ref: c-api/init_config c PyPreConfig coerce_c_locale14961482
Ref: 4ba114961482
Ref: c-api/init_config c PyPreConfig coerce_c_locale_warn14961809
Ref: 4ba214961809
Ref: c-api/init_config c PyPreConfig dev_mode14962002
Ref: 4ba314962002
Ref: c-api/init_config c PyPreConfig isolated14962205
Ref: 4ba514962205
Ref: c-api/init_config c PyPreConfig legacy_windows_fs_encoding14962374
Ref: 3b114962374
Ref: c-api/init_config c PyPreConfig parse_argv14962992
Ref: 4ba614962992
Ref: c-api/init_config c PyPreConfig use_environment14963382
Ref: 4ba714963382
Ref: c-api/init_config c PyPreConfig utf8_mode14963607
Ref: 3b514963607
Node: Preinitialize Python with PyPreConfig14964024
Ref: c-api/init_config c-preinit14964157
Ref: 3b6014964157
Ref: c-api/init_config preinitialize-python-with-pypreconfig14964157
Ref: 4ba814964157
Ref: c-api/init_config c Py_PreInitialize14964646
Ref: 3b614964646
Ref: c-api/init_config c Py_PreInitializeFromBytesArgs14964844
Ref: 96814964844
Ref: c-api/init_config c Py_PreInitializeFromArgs14965202
Ref: 96714965202
Node: PyConfig14967137
Ref: c-api/init_config pyconfig14967287
Ref: 4ba914967287
Ref: c-api/init_config c PyConfig14967320
Ref: 37114967320
Ref: c-api/init_config c PyConfig_InitPythonConfig14967552
Ref: 95514967552
Ref: c-api/init_config c PyConfig_InitIsolatedConfig14967711
Ref: 95414967711
Ref: c-api/init_config c PyConfig_SetString14967874
Ref: 95914967874
Ref: c-api/init_config c PyConfig_SetBytesString14968144
Ref: 95814968144
Ref: c-api/init_config c PyConfig_SetArgv14968457
Ref: 95614968457
Ref: c-api/init_config c PyConfig_SetBytesArgv14968771
Ref: 95714968771
Ref: c-api/init_config c PyConfig_SetWideStringList14969138
Ref: 18ea14969138
Ref: c-api/init_config c PyConfig_Read14969443
Ref: 73414969443
Ref: c-api/init_config c PyConfig_Clear14970782
Ref: 95314970782
Ref: c-api/init_config c PyConfig argv14971904
Ref: 38e14971904
Ref: c-api/init_config c PyConfig safe_path14972925
Ref: 71714972925
Ref: c-api/init_config c PyConfig base_exec_prefix14973805
Ref: 4baa14973805
Ref: c-api/init_config c PyConfig base_executable14974065
Ref: 4bac14974065
Ref: c-api/init_config c PyConfig base_prefix14974474
Ref: 4bad14974474
Ref: c-api/init_config c PyConfig buffered_stdio14974719
Ref: 3aa14974719
Ref: c-api/init_config c PyConfig bytes_warning14975143
Ref: 3a014975143
Ref: c-api/init_config c PyConfig warn_default_encoding14975596
Ref: 4bb014975596
Ref: c-api/init_config c PyConfig code_debug_ranges14975924
Ref: 4bb114975924
Ref: c-api/init_config c PyConfig check_hash_pycs_mode14976408
Ref: 4bb214976408
Ref: c-api/init_config c PyConfig configure_c_stdio14977076
Ref: 4baf14977076
Ref: c-api/init_config c PyConfig dev_mode14977631
Ref: 4ba414977631
Ref: c-api/init_config c PyConfig dump_refs14977937
Ref: 4bb314977937
Ref: c-api/init_config c PyConfig exec_prefix14978358
Ref: 4bab14978358
Ref: c-api/init_config c PyConfig executable14978721
Ref: 37014978721
Ref: c-api/init_config c PyConfig faulthandler14979050
Ref: 4bb414979050
Ref: c-api/init_config c PyConfig filesystem_encoding14979410
Ref: 3b314979410
Ref: c-api/init_config c PyConfig filesystem_errors14980643
Ref: 3b414980643
Ref: c-api/init_config c PyConfig hash_seed14981318
Ref: 3ad14981318
Ref: c-api/init_config c PyConfig use_hash_seed14981368
Ref: 3ac14981368
Ref: c-api/init_config c PyConfig home14981781
Ref: 38614981781
Ref: c-api/init_config c PyConfig import_time14982140
Ref: 4bb514982140
Ref: c-api/init_config c PyConfig inspect14982401
Ref: 39a14982401
Ref: c-api/init_config c PyConfig install_signal_handlers14982997
Ref: 86314982997
Ref: c-api/init_config c PyConfig interactive14983164
Ref: 39814983164
Ref: c-api/init_config c PyConfig int_max_str_digits14983376
Ref: 4bb614983376
Ref: c-api/init_config c PyConfig cpu_count14984271
Ref: 4bb714984271
Ref: c-api/init_config c PyConfig isolated14984768
Ref: 3af14984768
Ref: c-api/init_config c PyConfig legacy_windows_stdio14985768
Ref: 36f14985768
Ref: c-api/init_config c PyConfig malloc_stats14986373
Ref: 4bb814986373
Ref: c-api/init_config c PyConfig platlibdir14986765
Ref: 184014986765
Ref: c-api/init_config c PyConfig pythonpath_env14987580
Ref: 4bb914987580
Ref: c-api/init_config c PyConfig module_search_paths14987930
Ref: 36d14987930
Ref: c-api/init_config c PyConfig module_search_paths_set14988005
Ref: 59314988005
Ref: c-api/init_config c PyConfig optimization_level14988536
Ref: 39c14988536
Ref: c-api/init_config c PyConfig orig_argv14989039
Ref: 83814989039
Ref: c-api/init_config c PyConfig parse_argv14989717
Ref: 182b14989717
Ref: c-api/init_config c PyConfig parser_debug14990619
Ref: 39214990619
Ref: c-api/init_config c PyConfig pathconfig_warnings14991103
Ref: 3a214991103
Ref: c-api/init_config c PyConfig prefix14991526
Ref: 4bae14991526
Ref: c-api/init_config c PyConfig program_name14991866
Ref: 38f14991866
Ref: c-api/init_config c PyConfig pycache_prefix14992609
Ref: 4bba14992609
Ref: c-api/init_config c PyConfig quiet14993082
Ref: 39614993082
Ref: c-api/init_config c PyConfig run_command14993354
Ref: 4bbb14993354
Ref: c-api/init_config c PyConfig run_filename14993542
Ref: 4bbc14993542
Ref: c-api/init_config c PyConfig run_module14994009
Ref: 4bbe14994009
Ref: c-api/init_config c PyConfig run_presite14994196
Ref: 4bbf14994196
Ref: c-api/init_config c PyConfig show_ref_count14994698
Ref: 4bc014994698
Ref: c-api/init_config c PyConfig site_import14995062
Ref: 39e14995062
Ref: c-api/init_config c PyConfig skip_source_first_line14995726
Ref: 4bbd14995726
Ref: c-api/init_config c PyConfig stdio_encoding14996107
Ref: 36e14996107
Ref: c-api/init_config c PyConfig stdio_errors14996157
Ref: 41a014996157
Ref: c-api/init_config c PyConfig tracemalloc14997062
Ref: 4bc114997062
Ref: c-api/init_config c PyConfig perf_profiling14997421
Ref: 4bc214997421
Ref: c-api/init_config c PyConfig use_environment14998115
Ref: 3a414998115
Ref: c-api/init_config c PyConfig user_site_directory14998443
Ref: 3a814998443
Ref: c-api/init_config c PyConfig verbose14998844
Ref: 39414998844
Ref: c-api/init_config c PyConfig warnoptions14999460
Ref: 36b14999460
Ref: c-api/init_config c PyConfig write_bytecode15000306
Ref: 3a615000306
Ref: c-api/init_config c PyConfig xoptions15000774
Ref: 36c15000774
Ref: PyConfig-Footnote-115001399
Ref: PyConfig-Footnote-215001441
Node: Initialization with PyConfig15001483
Ref: c-api/init_config initialization-with-pyconfig15001618
Ref: 4bc315001618
Ref: c-api/init_config c Py_InitializeFromConfig15001723
Ref: 39015001723
Node: Isolated Configuration15005365
Ref: c-api/init_config init-isolated-conf15005512
Ref: 4b9415005512
Ref: c-api/init_config isolated-configuration15005512
Ref: 4bc415005512
Node: Python Configuration15006279
Ref: c-api/init_config init-python-config15006423
Ref: 4b9315006423
Ref: c-api/init_config python-configuration15006423
Ref: 4bc515006423
Ref: Python Configuration-Footnote-115007055
Ref: Python Configuration-Footnote-215007097
Node: Python Path Configuration15007139
Ref: c-api/init_config init-path-config15007271
Ref: 85215007271
Ref: c-api/init_config python-path-configuration15007271
Ref: 4bc615007271
Node: Py_RunMain15011023
Ref: c-api/init_config py-runmain15011149
Ref: 4bc715011149
Ref: c-api/init_config c Py_RunMain15011192
Ref: 96915011192
Node: Py_GetArgcArgv15011790
Ref: c-api/init_config py-getargcargv15011941
Ref: 4bc815011941
Ref: c-api/init_config c Py_GetArgcArgv15011992
Ref: 185815011992
Node: Multi-Phase Initialization Private Provisional API15012191
Ref: c-api/init_config multi-phase-initialization-private-provisional-api15012323
Ref: 4bc915012323
Ref: c-api/init_config c _Py_InitializeMain15013497
Ref: 4bca15013497
Ref: Multi-Phase Initialization Private Provisional API-Footnote-115015498
Ref: Multi-Phase Initialization Private Provisional API-Footnote-215015540
Node: 記憶體管理15015582
Ref: c-api/memory doc15015728
Ref: 4bcb15015728
Ref: c-api/memory memory15015728
Ref: 4b9f15015728
Ref: c-api/memory memory-management15015728
Ref: 4bcc15015728
Node: 總覽<2>15016094
Ref: c-api/memory memoryoverview15016181
Ref: 4bcd15016181
Ref: c-api/memory overview15016181
Ref: 4bce15016181
Node: Allocator Domains15020090
Ref: c-api/memory allocator-domains15020206
Ref: 4bcf15020206
Ref: c-api/memory id115020257
Ref: 4bd015020257
Node: Raw Memory Interface15022046
Ref: c-api/memory raw-memory-interface15022168
Ref: 4bd215022168
Ref: c-api/memory c PyMem_RawMalloc15022611
Ref: 32315022611
Ref: c-api/memory c PyMem_RawCalloc15023062
Ref: 32415023062
Ref: c-api/memory c PyMem_RawRealloc15023628
Ref: 32515023628
Ref: c-api/memory c PyMem_RawFree15024441
Ref: 32615024441
Node: 記憶體介面15024916
Ref: c-api/memory memory-interface15025038
Ref: 4bd315025038
Ref: c-api/memory memoryinterface15025038
Ref: 4bd415025038
Ref: c-api/memory c PyMem_Malloc15025529
Ref: c0d15025529
Ref: c-api/memory c PyMem_Calloc15025951
Ref: e4f15025951
Ref: c-api/memory c PyMem_Realloc15026510
Ref: fd515026510
Ref: c-api/memory c PyMem_Free15027282
Ref: 13b015027282
Ref: c-api/memory c PyMem_New15027821
Ref: 149315027821
Ref: c-api/memory c PyMem_Resize15028057
Ref: 4bd515028057
Ref: c-api/memory c PyMem_Del15028504
Ref: 149415028504
Node: Object allocators15029085
Ref: c-api/memory object-allocators15029212
Ref: 4bd615029212
Ref: c-api/memory c PyObject_Malloc15029897
Ref: c0f15029897
Ref: c-api/memory c PyObject_Calloc15030325
Ref: e5015030325
Ref: c-api/memory c PyObject_Realloc15030890
Ref: 13b115030890
Ref: c-api/memory c PyObject_Free15031682
Ref: c0c15031682
Node: Default Memory Allocators15032131
Ref: c-api/memory default-memory-allocators15032270
Ref: 1c5215032270
Ref: c-api/memory id215032270
Ref: 4bd815032270
Node: Customize Memory Allocators15034764
Ref: c-api/memory customize-memory-allocators15034929
Ref: 4bd715034929
Ref: c-api/memory id315034929
Ref: 4bd915034929
Ref: c-api/memory c PyMemAllocatorEx15035023
Ref: e7015035023
Ref: c-api/memory c PyMemAllocatorDomain15036858
Ref: 4bd115036858
Ref: c-api/memory c PYMEM_DOMAIN_RAW15036958
Ref: 1c5315036958
Ref: c-api/memory c PYMEM_DOMAIN_MEM15037199
Ref: c1015037199
Ref: c-api/memory c PYMEM_DOMAIN_OBJ15037429
Ref: c0e15037429
Ref: c-api/memory c PyMem_GetAllocator15037671
Ref: 4b5415037671
Ref: c-api/memory c PyMem_SetAllocator15037841
Ref: 53115037841
Ref: c-api/memory c PyMem_SetupDebugHooks15039764
Ref: c1115039764
Node: Debug hooks on the Python memory allocators15039912
Ref: c-api/memory debug-hooks-on-the-python-memory-allocators15040074
Ref: 4bda15040074
Ref: c-api/memory pymem-debug-hooks15040074
Ref: 1c5515040074
Node: The pymalloc allocator15045306
Ref: c-api/memory pymalloc15045463
Ref: cb615045463
Ref: c-api/memory the-pymalloc-allocator15045463
Ref: 4bdb15045463
Node: Customize pymalloc Arena Allocator15046577
Ref: c-api/memory customize-pymalloc-arena-allocator15046670
Ref: 4bdc15046670
Ref: c-api/memory c PyObjectArenaAllocator15046782
Ref: 4bdd15046782
Ref: c-api/memory c PyObject_GetArenaAllocator15047794
Ref: 4b5515047794
Ref: c-api/memory c PyObject_SetArenaAllocator15047918
Ref: 4b5315047918
Node: The mimalloc allocator15048042
Ref: c-api/memory mimalloc15048173
Ref: 1c5415048173
Ref: c-api/memory the-mimalloc-allocator15048173
Ref: 4bde15048173
Node: tracemalloc C API15048530
Ref: c-api/memory tracemalloc-c-api15048649
Ref: 4bdf15048649
Ref: c-api/memory c PyTraceMalloc_Track15048725
Ref: b5d15048725
Ref: c-api/memory c PyTraceMalloc_Untrack15049135
Ref: b5e15049135
Node: 範例<52>15049424
Ref: c-api/memory examples15049512
Ref: 4be015049512
Ref: c-api/memory memoryexamples15049512
Ref: 4be115049512
Node: Object Implementation Support15051416
Ref: c-api/objimpl doc15051564
Ref: 4be215051564
Ref: c-api/objimpl newtypes15051564
Ref: 4be315051564
Ref: c-api/objimpl object-implementation-support15051564
Ref: 4be415051564
Node: 在 heap 上分配物件15052048
Ref: c-api/allocation doc15052165
Ref: 4be515052165
Ref: c-api/allocation allocating-objects15052165
Ref: 4be615052165
Ref: c-api/allocation allocating-objects-on-the-heap15052165
Ref: 4be715052165
Ref: c-api/allocation c _PyObject_New15052224
Ref: 4be815052224
Ref: c-api/allocation c _PyObject_NewVar15052331
Ref: 4be915052331
Ref: c-api/allocation c PyObject_Init15052472
Ref: a0d15052472
Ref: c-api/allocation c PyObject_InitVar15052917
Ref: 185715052917
Ref: c-api/allocation c PyObject_New15053249
Ref: 92915053249
Ref: c-api/allocation c PyObject_NewVar15053689
Ref: 92a15053689
Ref: c-api/allocation c PyObject_Del15054361
Ref: 144015054361
Ref: c-api/allocation c _Py_NoneStruct15054756
Ref: 4bea15054756
Node: 通用物件結構15055064
Ref: c-api/structures doc15055205
Ref: 4beb15055205
Ref: c-api/structures common-object-structures15055205
Ref: 4bec15055205
Ref: c-api/structures common-structs15055205
Ref: 4bed15055205
Node: Base object types and macros15055530
Ref: c-api/structures base-object-types-and-macros15055643
Ref: 4bee15055643
Ref: c-api/structures c PyObject15056149
Ref: 31115056149
Ref: c-api/structures c PyVarObject15056841
Ref: 3f7915056841
Ref: c-api/structures c PyObject_HEAD15057335
Ref: 127115057335
Ref: c-api/structures c PyObject_VAR_HEAD15057597
Ref: 4bef15057597
Ref: c-api/structures c Py_Is15057899
Ref: 84415057899
Ref: c-api/structures c Py_IsNone15058135
Ref: 84515058135
Ref: c-api/structures c Py_IsTrue15058370
Ref: 84615058370
Ref: c-api/structures c Py_IsFalse15058605
Ref: 84715058605
Ref: c-api/structures c Py_TYPE15058848
Ref: 72415058848
Ref: c-api/structures c Py_IS_TYPE15059267
Ref: 171a15059267
Ref: c-api/structures c Py_SET_TYPE15059486
Ref: 72515059486
Ref: c-api/structures c Py_SIZE15059626
Ref: 72615059626
Ref: c-api/structures c Py_SET_SIZE15059973
Ref: 72715059973
Ref: c-api/structures c PyObject_HEAD_INIT15060113
Ref: 4bf015060113
Ref: c-api/structures c PyVarObject_HEAD_INIT15060332
Ref: 4bf115060332
Node: 實作函式與方法15060617
Ref: c-api/structures implementing-functions-and-methods15060778
Ref: 4bf215060778
Ref: c-api/structures c PyCFunction15060834
Ref: 13e215060834
Ref: c-api/structures c PyCFunctionWithKeywords15061459
Ref: 479115061459
Ref: c-api/structures c PyCFunctionFast15061893
Ref: 478f15061893
Ref: c-api/structures c PyCFunctionFastWithKeywords15062310
Ref: 479015062310
Ref: c-api/structures c PyCMethod15062863
Ref: 70815062863
Ref: c-api/structures c PyMethodDef15063355
Ref: 144615063355
Ref: c-api/structures c PyMethodDef ml_name15063563
Ref: 471e15063563
Ref: c-api/structures c PyMethodDef ml_meth15063640
Ref: 4bf515063640
Ref: c-api/structures c PyMethodDef ml_flags15063743
Ref: 4bf615063743
Ref: c-api/structures c PyMethodDef ml_doc15063851
Ref: 4bf715063851
Ref: c-api/structures c METH_VARARGS15064588
Ref: 147815064588
Ref: c-api/structures c METH_KEYWORDS15065103
Ref: 46d915065103
Ref: c-api/structures meth-varargs-meth-keywords15065357
Ref: 4bf315065357
Ref: c-api/structures c METH_FASTCALL15065794
Ref: 151b15065794
Ref: c-api/structures meth-fastcall-meth-keywords15066293
Ref: 4bf415066293
Ref: c-api/structures c METH_METHOD15066961
Ref: 91415066961
Ref: c-api/structures meth-method-meth-fastcall-meth-keywords15067109
Ref: 158415067109
Ref: c-api/structures c METH_NOARGS15067634
Ref: 144315067634
Ref: c-api/structures c METH_O15068196
Ref: 147715068196
Ref: c-api/structures c METH_CLASS15068791
Ref: 144415068791
Ref: c-api/structures c METH_STATIC15069068
Ref: 144515069068
Ref: c-api/structures c METH_COEXIST15069457
Ref: 13e115069457
Ref: c-api/structures c PyCMethod_New15070128
Ref: 17f015070128
Ref: c-api/structures c PyCFunction_NewEx15071271
Ref: 189115071271
Ref: c-api/structures c PyCFunction_New15071528
Ref: 17f615071528
Node: Accessing attributes of extension types15071786
Ref: c-api/structures accessing-attributes-of-extension-types15071910
Ref: 4bf815071910
Ref: c-api/structures c PyMemberDef15072009
Ref: 4f515072009
Ref: c-api/structures c PyMemberDef name15072361
Ref: 4bf915072361
Ref: c-api/structures c PyMemberDef type15072568
Ref: 471f15072568
Ref: c-api/structures c PyMemberDef offset15072720
Ref: 4bfa15072720
Ref: c-api/structures c PyMemberDef flags15072875
Ref: 472015072875
Ref: c-api/structures c PyMemberDef doc15073005
Ref: 4bfc15073005
Ref: c-api/structures pymemberdef-offsets15073551
Ref: 49d215073551
Ref: c-api/structures c PyMember_GetOne15074675
Ref: 53315074675
Ref: c-api/structures c PyMember_SetOne15075126
Ref: 53415075126
Node: Member flags15075703
Ref: c-api/structures member-flags15075812
Ref: 4bfe15075812
Ref: c-api/structures pymemberdef-flags15075812
Ref: 4bfb15075812
Ref: c-api/structures c Py_READONLY15075927
Ref: 53715075927
Ref: c-api/structures c Py_AUDIT_READ15075976
Ref: 53815075976
Ref: c-api/structures c Py_RELATIVE_OFFSET15076090
Ref: 4f415076090
Node: Member types15077325
Ref: c-api/structures member-types15077471
Ref: 4bff15077471
Ref: c-api/structures pymemberdef-types15077471
Ref: 156915077471
Ref: c-api/structures c Py_T_BYTE15078358
Ref: 4c0015078358
Ref: c-api/structures c Py_T_SHORT15078592
Ref: 4c0115078592
Ref: c-api/structures c Py_T_INT15078823
Ref: 53515078823
Ref: c-api/structures c Py_T_LONG15079057
Ref: 4c0215079057
Ref: c-api/structures c Py_T_LONGLONG15079294
Ref: 4c0315079294
Ref: c-api/structures c Py_T_UBYTE15079524
Ref: 4c0415079524
Ref: c-api/structures c Py_T_UINT15079756
Ref: 4c0515079756
Ref: c-api/structures c Py_T_USHORT15079991
Ref: 4c0615079991
Ref: c-api/structures c Py_T_ULONG15080223
Ref: 4c0715080223
Ref: c-api/structures c Py_T_ULONGLONG15080460
Ref: 4c0815080460
Ref: c-api/structures c Py_T_PYSSIZET15080692
Ref: 4c0915080692
Ref: c-api/structures c Py_T_FLOAT15080922
Ref: 4c0a15080922
Ref: c-api/structures c Py_T_DOUBLE15081158
Ref: 53615081158
Ref: c-api/structures c Py_T_BOOL15081391
Ref: 4c0b15081391
Ref: c-api/structures c Py_T_STRING15081632
Ref: 4bfd15081632
Ref: c-api/structures c Py_T_STRING_INPLACE15081878
Ref: 4c0c15081878
Ref: c-api/structures c Py_T_CHAR15082106
Ref: 4c0d15082106
Ref: c-api/structures c Py_T_OBJECT_EX15082349
Ref: 53a15082349
Ref: c-api/structures c T_OBJECT15083217
Ref: 53915083217
Ref: c-api/structures c T_NONE15083433
Ref: 53b15083433
Node: Defining Getters and Setters15083523
Ref: c-api/structures defining-getters-and-setters15083648
Ref: 4c0e15083648
Ref: c-api/structures c PyGetSetDef15083725
Ref: b5f15083725
Ref: c-api/structures c PyGetSetDef name15083966
Ref: 4c0f15083966
Ref: c-api/structures c PyGetSetDef get15084033
Ref: 4c1015084033
Ref: c-api/structures c PyGetSetDef set15084127
Ref: 4c1115084127
Ref: c-api/structures c PyGetSetDef doc15084294
Ref: 4c1215084294
Ref: c-api/structures c PyGetSetDef closure15084369
Ref: 4c1315084369
Ref: c-api/structures c getter15084507
Ref: 48ca15084507
Ref: c-api/structures c setter15084899
Ref: 48d815084899
Node: 型別物件<2>15085386
Ref: c-api/typeobj doc15085527
Ref: 4c1415085527
Ref: c-api/typeobj type-objects15085527
Ref: 4c1515085527
Ref: c-api/typeobj type-structs15085527
Ref: 93115085527
Node: Quick Reference15086759
Ref: c-api/typeobj quick-reference15086858
Ref: 4c1715086858
Node: "tp slots"15086966
Ref: c-api/typeobj tp-slots15087046
Ref: 4c1815087046
Ref: c-api/typeobj tp-slots-table15087046
Ref: 4c1915087046
Ref: "tp slots"-Footnote-115100295
Ref: "tp slots"-Footnote-215100607
Node: sub-slots15101379
Ref: c-api/typeobj id315101481
Ref: 4c2415101481
Ref: c-api/typeobj sub-slots15101481
Ref: 4c1b15101481
Node: slot typedefs15111817
Ref: c-api/typeobj slot-typedefs15111900
Ref: 4c5415111900
Ref: c-api/typeobj slot-typedefs-table15111900
Ref: 4c1a15111900
Node: PyTypeObject Definition15119767
Ref: c-api/typeobj pytypeobject-definition15119889
Ref: 4c5615119889
Node: PyObject Slots15123029
Ref: c-api/typeobj pyobject-slots15123153
Ref: 4c5715123153
Ref: c-api/typeobj c PyObject ob_refcnt15123588
Ref: 84315123588
Ref: c-api/typeobj c PyObject ob_type15124183
Ref: 470215124183
Node: PyVarObject Slots15125360
Ref: c-api/typeobj pyvarobject-slots15125479
Ref: 4c5815125479
Ref: c-api/typeobj c PyVarObject ob_size15125534
Ref: 48af15125534
Node: PyTypeObject Slots15125923
Ref: c-api/typeobj pytypeobject-slots15126040
Ref: 4c5915126040
Ref: c-api/typeobj c PyTypeObject tp_name15126387
Ref: 17f515126387
Ref: c-api/typeobj c PyTypeObject tp_basicsize15128135
Ref: 92b15128135
Ref: c-api/typeobj c PyTypeObject tp_itemsize15128225
Ref: 1e4615128225
Ref: c-api/typeobj c PyTypeObject tp_dealloc15130938
Ref: 470415130938
Ref: c-api/typeobj c PyTypeObject tp_vectorcall_offset15133468
Ref: 497315133468
Ref: c-api/typeobj c PyTypeObject tp_getattr15135393
Ref: 472215135393
Ref: c-api/typeobj c PyTypeObject tp_setattr15136169
Ref: 472315136169
Ref: c-api/typeobj c PyTypeObject tp_as_async15136965
Ref: e7115136965
Ref: c-api/typeobj c PyTypeObject tp_repr15137543
Ref: 471915137543
Ref: c-api/typeobj c PyTypeObject tp_as_number15138521
Ref: 92f15138521
Ref: c-api/typeobj c PyTypeObject tp_as_sequence15138961
Ref: 4c1c15138961
Ref: c-api/typeobj c PyTypeObject tp_as_mapping15139412
Ref: 4c1d15139412
Ref: c-api/typeobj c PyTypeObject tp_hash15139858
Ref: 472b15139858
Ref: c-api/typeobj c PyTypeObject tp_call15141589
Ref: 4ff15141589
Ref: c-api/typeobj c PyTypeObject tp_str15142018
Ref: 471a15142018
Ref: c-api/typeobj c PyTypeObject tp_getattro15142992
Ref: 15ec15142992
Ref: c-api/typeobj c PyTypeObject tp_setattro15143910
Ref: 471d15143910
Ref: c-api/typeobj c PyTypeObject tp_as_buffer15144954
Ref: 92d15144954
Ref: c-api/typeobj c PyTypeObject tp_flags15145393
Ref: 17c015145393
Ref: c-api/typeobj c Py_TPFLAGS_HEAPTYPE15147365
Ref: 85415147365
Ref: c-api/typeobj c Py_TPFLAGS_BASETYPE15148170
Ref: 470a15148170
Ref: c-api/typeobj c Py_TPFLAGS_READY15148447
Ref: 4c5f15148447
Ref: c-api/typeobj c Py_TPFLAGS_READYING15148640
Ref: 4c6015148640
Ref: c-api/typeobj c Py_TPFLAGS_HAVE_GC15148842
Ref: 72015148842
Ref: c-api/typeobj c Py_TPFLAGS_DEFAULT15149862
Ref: 46ff15149862
Ref: c-api/typeobj c Py_TPFLAGS_METHOD_DESCRIPTOR15150201
Ref: 497b15150201
Ref: c-api/typeobj c Py_TPFLAGS_MANAGED_DICT15151131
Ref: 31b15151131
Ref: c-api/typeobj c Py_TPFLAGS_MANAGED_WEAKREF15151792
Ref: 50015151792
Ref: c-api/typeobj c Py_TPFLAGS_ITEMS_AT_END15152114
Ref: 4f115152114
Ref: c-api/typeobj c Py_TPFLAGS_LONG_SUBCLASS15152782
Ref: 4c6115152782
Ref: c-api/typeobj c Py_TPFLAGS_LIST_SUBCLASS15152827
Ref: 4c6215152827
Ref: c-api/typeobj c Py_TPFLAGS_TUPLE_SUBCLASS15152872
Ref: 4c6315152872
Ref: c-api/typeobj c Py_TPFLAGS_BYTES_SUBCLASS15152918
Ref: 4c6415152918
Ref: c-api/typeobj c Py_TPFLAGS_UNICODE_SUBCLASS15152964
Ref: 4c6515152964
Ref: c-api/typeobj c Py_TPFLAGS_DICT_SUBCLASS15153012
Ref: 4c6615153012
Ref: c-api/typeobj c Py_TPFLAGS_BASE_EXC_SUBCLASS15153057
Ref: 4c6715153057
Ref: c-api/typeobj c Py_TPFLAGS_TYPE_SUBCLASS15153106
Ref: 4c6815153106
Ref: c-api/typeobj c Py_TPFLAGS_HAVE_FINALIZE15153668
Ref: 3ba15153668
Ref: c-api/typeobj c Py_TPFLAGS_HAVE_VECTORCALL15154050
Ref: 4fa15154050
Ref: c-api/typeobj c Py_TPFLAGS_IMMUTABLETYPE15154608
Ref: 38d15154608
Ref: c-api/typeobj c Py_TPFLAGS_DISALLOW_INSTANTIATION15154977
Ref: 52815154977
Ref: c-api/typeobj c Py_TPFLAGS_MAPPING15156107
Ref: 17a615156107
Ref: c-api/typeobj c Py_TPFLAGS_SEQUENCE15156958
Ref: 17a715156958
Ref: c-api/typeobj c Py_TPFLAGS_VALID_VERSION_TAG15157810
Ref: 4c6915157810
Ref: c-api/typeobj c PyTypeObject tp_doc15158144
Ref: 470015158144
Ref: c-api/typeobj c PyTypeObject tp_traverse15158473
Ref: 72115158473
Ref: c-api/typeobj c PyTypeObject tp_clear15162621
Ref: 471715162621
Ref: c-api/typeobj c PyTypeObject tp_richcompare15166525
Ref: 472515166525
Ref: c-api/typeobj c Py_LT15167517
Ref: 496815167517
Ref: c-api/typeobj c Py_LE15167619
Ref: 496915167619
Ref: c-api/typeobj c Py_EQ15167722
Ref: 496a15167722
Ref: c-api/typeobj c Py_NE15167825
Ref: 496b15167825
Ref: c-api/typeobj c Py_GT15167928
Ref: 496c15167928
Ref: c-api/typeobj c Py_GE15168030
Ref: 496d15168030
Ref: c-api/typeobj c Py_RETURN_RICHCOMPARE15168164
Ref: b5b15168164
Ref: c-api/typeobj c PyTypeObject tp_weaklistoffset15169432
Ref: 92c15169432
Ref: c-api/typeobj c PyTypeObject tp_iter15170969
Ref: 145c15170969
Ref: c-api/typeobj c PyTypeObject tp_iternext15171498
Ref: 145d15171498
Ref: c-api/typeobj c PyTypeObject tp_methods15172342
Ref: 470915172342
Ref: c-api/typeobj c PyTypeObject tp_members15172877
Ref: 470715172877
Ref: c-api/typeobj c PyTypeObject tp_getset15173446
Ref: 470c15173446
Ref: c-api/typeobj c PyTypeObject tp_base15174007
Ref: 471015174007
Ref: c-api/typeobj c PyTypeObject tp_dict15175331
Ref: 161c15175331
Ref: c-api/typeobj c PyTypeObject tp_descr_get15176850
Ref: 4c1e15176850
Ref: c-api/typeobj c PyTypeObject tp_descr_set15177182
Ref: 17f915177182
Ref: c-api/typeobj c PyTypeObject tp_dictoffset15177611
Ref: 49d115177611
Ref: c-api/typeobj c PyTypeObject tp_init15179513
Ref: 52715179513
Ref: c-api/typeobj c PyTypeObject tp_alloc15180981
Ref: 470615180981
Ref: c-api/typeobj c PyTypeObject tp_new15181697
Ref: 52515181697
Ref: c-api/typeobj c PyTypeObject tp_free15183437
Ref: 470515183437
Ref: c-api/typeobj c PyTypeObject tp_is_gc15184170
Ref: 4c1f15184170
Ref: c-api/typeobj c PyTypeObject tp_bases15185356
Ref: 4c2015185356
Ref: c-api/typeobj c PyTypeObject tp_mro15186112
Ref: 49d415186112
Ref: c-api/typeobj c PyTypeObject tp_cache15186598
Ref: 49d515186598
Ref: c-api/typeobj c PyTypeObject tp_subclasses15186764
Ref: 51815186764
Ref: c-api/typeobj c PyTypeObject tp_weaklist15187224
Ref: 49d615187224
Ref: c-api/typeobj c PyTypeObject tp_del15187814
Ref: 4c2115187814
Ref: c-api/typeobj c PyTypeObject tp_version_tag15187960
Ref: 4c2215187960
Ref: c-api/typeobj c PyTypeObject tp_finalize15188152
Ref: a4915188152
Ref: c-api/typeobj c PyTypeObject tp_vectorcall15190448
Ref: 49d315190448
Ref: c-api/typeobj c PyTypeObject tp_watched15191001
Ref: 4c2315191001
Ref: PyTypeObject Slots-Footnote-115191165
Ref: PyTypeObject Slots-Footnote-215191207
Ref: PyTypeObject Slots-Footnote-315191249
Ref: PyTypeObject Slots-Footnote-415191292
Node: Static Types15191334
Ref: c-api/typeobj id415191444
Ref: 4c6a15191444
Ref: c-api/typeobj static-types15191444
Ref: 72315191444
Node: Heap Types15192349
Ref: c-api/typeobj heap-types15192432
Ref: 90915192432
Ref: c-api/typeobj id515192432
Ref: 4c6b15192432
Node: Number Object Structures15192935
Ref: c-api/typeobj number-object-structures15193083
Ref: 4c6c15193083
Ref: c-api/typeobj number-structs15193083
Ref: 4c5b15193083
Ref: c-api/typeobj c PyNumberMethods15193148
Ref: 138b15193148
Ref: c-api/typeobj c PyNumberMethods nb_add15195599
Ref: 49c815195599
Ref: c-api/typeobj c PyNumberMethods nb_subtract15195689
Ref: 4c2b15195689
Ref: c-api/typeobj c PyNumberMethods nb_multiply15195784
Ref: 4c2d15195784
Ref: c-api/typeobj c PyNumberMethods nb_remainder15195879
Ref: 4c2f15195879
Ref: c-api/typeobj c PyNumberMethods nb_divmod15195975
Ref: 4c3115195975
Ref: c-api/typeobj c PyNumberMethods nb_power15196068
Ref: 4c3215196068
Ref: c-api/typeobj c PyNumberMethods nb_negative15196161
Ref: 4c3415196161
Ref: c-api/typeobj c PyNumberMethods nb_positive15196255
Ref: 4c3515196255
Ref: c-api/typeobj c PyNumberMethods nb_absolute15196349
Ref: 4c3615196349
Ref: c-api/typeobj c PyNumberMethods nb_bool15196443
Ref: 4c3715196443
Ref: c-api/typeobj c PyNumberMethods nb_invert15196521
Ref: 4c3815196521
Ref: c-api/typeobj c PyNumberMethods nb_lshift15196613
Ref: 4c3915196613
Ref: c-api/typeobj c PyNumberMethods nb_rshift15196706
Ref: 4c3b15196706
Ref: c-api/typeobj c PyNumberMethods nb_and15196799
Ref: 4c3d15196799
Ref: c-api/typeobj c PyNumberMethods nb_xor15196889
Ref: 4c3f15196889
Ref: c-api/typeobj c PyNumberMethods nb_or15196979
Ref: 4c4115196979
Ref: c-api/typeobj c PyNumberMethods nb_int15197068
Ref: 4c4315197068
Ref: c-api/typeobj c PyNumberMethods nb_reserved15197157
Ref: 4c4415197157
Ref: c-api/typeobj c PyNumberMethods nb_float15197224
Ref: 4c4515197224
Ref: c-api/typeobj c PyNumberMethods nb_inplace_add15197315
Ref: 4c2a15197315
Ref: c-api/typeobj c PyNumberMethods nb_inplace_subtract15197413
Ref: 4c2c15197413
Ref: c-api/typeobj c PyNumberMethods nb_inplace_multiply15197516
Ref: 4c2e15197516
Ref: c-api/typeobj c PyNumberMethods nb_inplace_remainder15197619
Ref: 4c3015197619
Ref: c-api/typeobj c PyNumberMethods nb_inplace_power15197723
Ref: 4c3315197723
Ref: c-api/typeobj c PyNumberMethods nb_inplace_lshift15197824
Ref: 4c3a15197824
Ref: c-api/typeobj c PyNumberMethods nb_inplace_rshift15197925
Ref: 4c3c15197925
Ref: c-api/typeobj c PyNumberMethods nb_inplace_and15198026
Ref: 4c3e15198026
Ref: c-api/typeobj c PyNumberMethods nb_inplace_xor15198124
Ref: 4c4015198124
Ref: c-api/typeobj c PyNumberMethods nb_inplace_or15198222
Ref: 4c4215198222
Ref: c-api/typeobj c PyNumberMethods nb_floor_divide15198319
Ref: 4c4615198319
Ref: c-api/typeobj c PyNumberMethods nb_true_divide15198418
Ref: 4c4815198418
Ref: c-api/typeobj c PyNumberMethods nb_inplace_floor_divide15198516
Ref: 4c4715198516
Ref: c-api/typeobj c PyNumberMethods nb_inplace_true_divide15198623
Ref: 4c4915198623
Ref: c-api/typeobj c PyNumberMethods nb_index15198729
Ref: 138a15198729
Ref: c-api/typeobj c PyNumberMethods nb_matrix_multiply15198820
Ref: 4c4a15198820
Ref: c-api/typeobj c PyNumberMethods nb_inplace_matrix_multiply15198922
Ref: 4c4b15198922
Node: Mapping Object Structures15199032
Ref: c-api/typeobj mapping-object-structures15199191
Ref: 4c6d15199191
Ref: c-api/typeobj mapping-structs15199191
Ref: 4c5d15199191
Ref: c-api/typeobj c PyMappingMethods15199258
Ref: 472a15199258
Ref: c-api/typeobj c PyMappingMethods mp_length15199432
Ref: 4c4c15199432
Ref: c-api/typeobj c PyMappingMethods mp_subscript15199728
Ref: 183015199728
Ref: c-api/typeobj c PyMappingMethods mp_ass_subscript15200127
Ref: 4c4d15200127
Node: Sequence Object Structures15200625
Ref: c-api/typeobj sequence-object-structures15200784
Ref: 4c6e15200784
Ref: c-api/typeobj sequence-structs15200784
Ref: 4c5c15200784
Ref: c-api/typeobj c PySequenceMethods15200853
Ref: 472915200853
Ref: c-api/typeobj c PySequenceMethods sq_length15201006
Ref: 49d015201006
Ref: c-api/typeobj c PySequenceMethods sq_concat15201352
Ref: 4c4e15201352
Ref: c-api/typeobj c PySequenceMethods sq_repeat15201659
Ref: 4c4f15201659
Ref: c-api/typeobj c PySequenceMethods sq_item15201980
Ref: 182f15201980
Ref: c-api/typeobj c PySequenceMethods sq_ass_item15202743
Ref: 4c5015202743
Ref: c-api/typeobj c PySequenceMethods sq_contains15203238
Ref: 4c5115203238
Ref: c-api/typeobj c PySequenceMethods sq_inplace_concat15203581
Ref: 4c5215203581
Ref: c-api/typeobj c PySequenceMethods sq_inplace_repeat15204136
Ref: 4c5315204136
Node: Buffer Object Structures15204704
Ref: c-api/typeobj buffer-object-structures15204861
Ref: 4c6f15204861
Ref: c-api/typeobj buffer-structs15204861
Ref: 499315204861
Ref: c-api/typeobj c PyBufferProcs15204926
Ref: 49d715204926
Ref: c-api/typeobj c PyBufferProcs bf_getbuffer15205162
Ref: 70615205162
Ref: c-api/typeobj c PyBufferProcs bf_releasebuffer15207056
Ref: 70715207056
Node: Async Object Structures15208202
Ref: c-api/typeobj async-object-structures15208351
Ref: 4c7015208351
Ref: c-api/typeobj async-structs15208351
Ref: 4c5a15208351
Ref: c-api/typeobj c PyAsyncMethods15208437
Ref: 49cf15208437
Ref: c-api/typeobj c PyAsyncMethods am_await15208856
Ref: 4c2515208856
Ref: c-api/typeobj c PyAsyncMethods am_aiter15209250
Ref: 4c2615209250
Ref: c-api/typeobj c PyAsyncMethods am_anext15209650
Ref: 4c2715209650
Ref: c-api/typeobj c PyAsyncMethods am_send15209964
Ref: 4c2815209964
Node: Slot Type typedefs15210286
Ref: c-api/typeobj id615210421
Ref: 4c5515210421
Ref: c-api/typeobj slot-type-typedefs15210421
Ref: 4c7115210421
Ref: c-api/typeobj c allocfunc15210474
Ref: 48c115210474
Ref: c-api/typeobj c destructor15211548
Ref: 48c515211548
Ref: c-api/typeobj c freefunc15211661
Ref: 4ac615211661
Ref: c-api/typeobj c newfunc15211745
Ref: 48d015211745
Ref: c-api/typeobj c initproc15211958
Ref: 48cc15211958
Ref: c-api/typeobj c reprfunc15212155
Ref: 48d415212155
Ref: c-api/typeobj c getattrfunc15212325
Ref: 48c615212325
Ref: c-api/typeobj c setattrfunc15212545
Ref: 48d615212545
Ref: c-api/typeobj c getattrofunc15212844
Ref: 48c715212844
Ref: c-api/typeobj c setattrofunc15213122
Ref: 48d715213122
Ref: c-api/typeobj c descrgetfunc15213479
Ref: 48c315213479
Ref: c-api/typeobj c descrsetfunc15213709
Ref: 48c415213709
Ref: c-api/typeobj c hashfunc15213921
Ref: 48cb15213921
Ref: c-api/typeobj c richcmpfunc15214092
Ref: 48d515214092
Ref: c-api/typeobj c getiterfunc15214305
Ref: 48c915214305
Ref: c-api/typeobj c iternextfunc15214478
Ref: 48ce15214478
Ref: c-api/typeobj c lenfunc15214656
Ref: 48cf15214656
Ref: c-api/typeobj c getbufferproc15214794
Ref: 48c815214794
Ref: c-api/typeobj c releasebufferproc15214971
Ref: 48d315214971
Ref: c-api/typeobj c unaryfunc15215148
Ref: 48dd15215148
Ref: c-api/typeobj c binaryfunc15215287
Ref: 48c215215287
Ref: c-api/typeobj c sendfunc15215450
Ref: 4c2915215450
Ref: c-api/typeobj c ternaryfunc15215638
Ref: 48db15215638
Ref: c-api/typeobj c ssizeargfunc15215825
Ref: 48d915215825
Ref: c-api/typeobj c ssizeobjargproc15215991
Ref: 48da15215991
Ref: c-api/typeobj c objobjproc15216164
Ref: 48d215216164
Ref: c-api/typeobj c objobjargproc15216309
Ref: 48d115216309
Node: 範例<53>15216480
Ref: c-api/typeobj examples15216619
Ref: 4c7215216619
Ref: c-api/typeobj typedef-examples15216619
Ref: 4c1615216619
Node: 循環垃圾回收的支援15221984
Ref: c-api/gcsupport doc15222096
Ref: 4c7315222096
Ref: c-api/gcsupport supporting-cycle-detection15222096
Ref: 4c5e15222096
Ref: c-api/gcsupport supporting-cyclic-garbage-collection15222096
Ref: 4c7415222096
Ref: c-api/gcsupport c PyObject_GC_New15224420
Ref: a4515224420
Ref: c-api/gcsupport c PyObject_GC_NewVar15224592
Ref: a4615224592
Ref: c-api/gcsupport c PyUnstable_Object_GC_NewWithExtraData15224776
Ref: 163715224776
Ref: c-api/gcsupport c PyObject_GC_Resize15225795
Ref: 163c15225795
Ref: c-api/gcsupport c PyObject_GC_Track15226179
Ref: 147415226179
Ref: c-api/gcsupport c PyObject_IS_GC15226620
Ref: 92815226620
Ref: c-api/gcsupport c PyObject_GC_IsTracked15226869
Ref: 91a15226869
Ref: c-api/gcsupport c PyObject_GC_IsFinalized15227257
Ref: 91b15227257
Ref: c-api/gcsupport c PyObject_GC_Del15227648
Ref: 147315227648
Ref: c-api/gcsupport c PyObject_GC_UnTrack15227861
Ref: 147515227861
Ref: c-api/gcsupport c visitproc15228582
Ref: 48de15228582
Ref: c-api/gcsupport c traverseproc15229202
Ref: 48dc15229202
Ref: c-api/gcsupport c Py_VISIT15230020
Ref: 470e15230020
Ref: c-api/gcsupport c inquiry15230600
Ref: 48cd15230600
Node: Controlling the Garbage Collector State15231227
Ref: c-api/gcsupport controlling-the-garbage-collector-state15231371
Ref: 4c7515231371
Ref: c-api/gcsupport c PyGC_Collect15231557
Ref: 93215231557
Ref: c-api/gcsupport c PyGC_Enable15232127
Ref: 84815232127
Ref: c-api/gcsupport c PyGC_Disable15232405
Ref: 84915232405
Ref: c-api/gcsupport c PyGC_IsEnabled15232686
Ref: 84a15232686
Node: Querying Garbage Collector State15232981
Ref: c-api/gcsupport querying-garbage-collector-state15233125
Ref: 4c7615233125
Ref: c-api/gcsupport c PyUnstable_GC_VisitObjects15233310
Ref: 4c7715233310
Ref: c-api/gcsupport c gcvisitobjects_t15234113
Ref: 4c7815234113
Node: API 和 ABI 版本管理15234602
Ref: c-api/apiabiversion doc15234751
Ref: 4c7915234751
Ref: c-api/apiabiversion api-and-abi-versioning15234751
Ref: 4c7a15234751
Ref: c-api/apiabiversion apiabiversion15234751
Ref: 419a15234751
Ref: c-api/apiabiversion c PY_MAJOR_VERSION15235080
Ref: 4c7b15235080
Ref: c-api/apiabiversion c PY_MINOR_VERSION15235154
Ref: 4c7c15235154
Ref: c-api/apiabiversion c PY_MICRO_VERSION15235228
Ref: 4c7d15235228
Ref: c-api/apiabiversion c PY_RELEASE_LEVEL15235302
Ref: 4c7e15235302
Ref: c-api/apiabiversion c PY_RELEASE_SERIAL15235507
Ref: 4c7f15235507
Ref: c-api/apiabiversion c PY_VERSION_HEX15235612
Ref: 6fb15235612
Ref: c-api/apiabiversion c Py_Version15237533
Ref: 6fa15237533
Ref: API 和 ABI 版本管理-Footnote-115237955
Node: Monitoring C API15238028
Ref: c-api/monitoring doc15238175
Ref: 4c8015238175
Ref: c-api/monitoring monitoring15238175
Ref: 41c915238175
Ref: c-api/monitoring monitoring-c-api15238175
Ref: 4c8115238175
Node: Generating Execution Events15238429
Ref: c-api/monitoring generating-execution-events15238543
Ref: 4c8215238543
Ref: c-api/monitoring c PyMonitoringState15239478
Ref: 4c8315239478
Ref: c-api/monitoring c PyMonitoring_FirePyStartEvent15239842
Ref: 4c8415239842
Ref: c-api/monitoring c PyMonitoring_FirePyResumeEvent15239999
Ref: 4c8515239999
Ref: c-api/monitoring c PyMonitoring_FirePyReturnEvent15240158
Ref: 4c8615240158
Ref: c-api/monitoring c PyMonitoring_FirePyYieldEvent15240335
Ref: 4c8715240335
Ref: c-api/monitoring c PyMonitoring_FireCallEvent15240510
Ref: 4c8815240510
Ref: c-api/monitoring c PyMonitoring_FireLineEvent15240706
Ref: 4c8915240706
Ref: c-api/monitoring c PyMonitoring_FireJumpEvent15240868
Ref: 4c8a15240868
Ref: c-api/monitoring c PyMonitoring_FireBranchEvent15241043
Ref: 4c8b15241043
Ref: c-api/monitoring c PyMonitoring_FireCReturnEvent15241222
Ref: 4c8c15241222
Ref: c-api/monitoring c PyMonitoring_FirePyThrowEvent15241397
Ref: 4c8d15241397
Ref: c-api/monitoring c PyMonitoring_FireRaiseEvent15241642
Ref: 4c8e15241642
Ref: c-api/monitoring c PyMonitoring_FireCRaiseEvent15241882
Ref: 4c8f15241882
Ref: c-api/monitoring c PyMonitoring_FireReraiseEvent15242125
Ref: 4c9015242125
Ref: c-api/monitoring c PyMonitoring_FireExceptionHandledEvent15242369
Ref: 4c9115242369
Ref: c-api/monitoring c PyMonitoring_FirePyUnwindEvent15242633
Ref: 4c9215242633
Ref: c-api/monitoring c PyMonitoring_FireStopIterationEvent15242880
Ref: 4c9315242880
Node: Managing the Monitoring State15243295
Ref: c-api/monitoring managing-the-monitoring-state15243388
Ref: 4c9415243388
Node: 安裝 Python 模組15243591
Ref: installing/index doc15243719
Ref: 4c9515243719
Ref: installing/index installing-index15243719
Ref: e9915243719
Ref: installing/index installing-python-modules15243719
Ref: 4c9615243719
Ref: 安裝 Python 模組-Footnote-115244816
Node: 關鍵術語15244894
Ref: installing/index key-terms15244987
Ref: 4c9715244987
Ref: 關鍵術語-Footnote-115246973
Ref: 關鍵術語-Footnote-215246998
Ref: 關鍵術語-Footnote-315247027
Ref: 關鍵術語-Footnote-415247059
Node: 基本用法<3>15247139
Ref: installing/index basic-usage15247257
Ref: 4c9815247257
Ref: 基本用法<3>-Footnote-115248799
Ref: 基本用法<3>-Footnote-215248836
Node: 我該如何 ？15248885
Ref: installing/index how-do-i15249012
Ref: 4c9915249012
Node: 在 Python 3 4 之前的 Python 版本中安裝 pip？15249515
Ref: installing/index install-pip-in-versions-of-python-prior-to-python-3-415249670
Ref: 4c9a15249670
Ref: 在 Python 3 4 之前的 Python 版本中安裝 pip？-Footnote-115250100
Node: 只為目前的使用者安裝套件？15250187
Ref: installing/index install-packages-just-for-the-current-user15250383
Ref: 4c9b15250383
Node: 安裝科學的 Python 套件？15250610
Ref: installing/index install-scientific-python-packages15250802
Ref: 4c9c15250802
Ref: 安裝科學的 Python 套件？-Footnote-115251230
Ref: 安裝科學的 Python 套件？-Footnote-215251276
Node: 平行安裝多個 Python 版本並使用它們？15251322
Ref: installing/index work-with-multiple-versions-of-python-installed-in-parallel15251466
Ref: 4c9d15251466
Node: 常見的安裝問題15252437
Ref: installing/index common-installation-issues15252540
Ref: 4c9e15252540
Node: 在 Linux 上安裝套件至系統 Python15252744
Ref: installing/index installing-into-the-system-python-on-linux15252865
Ref: 4c9f15252865
Node: 未安裝 pip15253411
Ref: installing/index pip-not-installed15253579
Ref: 4ca015253579
Ref: 未安裝 pip-Footnote-115253825
Node: 安裝二進制擴充 binary extension15253951
Ref: installing/index installing-binary-extensions15254069
Ref: 4ca115254069
Ref: 安裝二進制擴充 binary extension-Footnote-115254940
Ref: 安裝二進制擴充 binary extension-Footnote-215254986
Node: Python 如何達成任務15255035
Ref: howto/index doc15255157
Ref: 4ca215255157
Ref: howto/index python-howtos15255157
Ref: 4ca315255157
Node: 遷移延伸模組到 Python 315256282
Ref: howto/cporting doc15256413
Ref: 4ca415256413
Ref: howto/cporting cporting-howto15256413
Ref: 127415256413
Ref: howto/cporting porting-extension-modules-to-python-315256413
Ref: 4ca515256413
Ref: 遷移延伸模組到 Python 3-Footnote-115257170
Ref: 遷移延伸模組到 Python 3-Footnote-215257221
Ref: 遷移延伸模組到 Python 3-Footnote-315257278
Ref: 遷移延伸模組到 Python 3-Footnote-415257306
Node: Curses Programming with Python15257353
Ref: howto/curses doc15257520
Ref: 4ca615257520
Ref: howto/curses curses-howto15257520
Ref: 2c8215257520
Ref: howto/curses curses-programming-with-python15257520
Ref: 4ca715257520
Node: What is curses?15257933
Ref: howto/curses what-is-curses15258064
Ref: 4ca815258064
Ref: What is curses?-Footnote-115260400
Ref: What is curses?-Footnote-215260440
Node: Python curses 模組15260484
Ref: howto/curses the-python-curses-module15260556
Ref: 4ca915260556
Node: Starting and ending a curses application15261363
Ref: howto/curses starting-and-ending-a-curses-application15261519
Ref: 4caa15261519
Node: Windows and Pads15264776
Ref: howto/curses windows-and-pads15264932
Ref: 4cab15264932
Node: Displaying Text15269476
Ref: howto/curses displaying-text15269607
Ref: 4cac15269607
Node: Attributes and Color15273390
Ref: howto/curses attributes-and-color15273462
Ref: 4cad15273462
Node: 使用者輸入15277984
Ref: howto/curses user-input15278119
Ref: 4cae15278119
Ref: 使用者輸入-Footnote-115281930
Node: For More Information15281970
Ref: howto/curses for-more-information15282081
Ref: 4caf15282081
Ref: For More Information-Footnote-115283570
Ref: For More Information-Footnote-215283607
Ref: For More Information-Footnote-315283671
Ref: For More Information-Footnote-415283715
Ref: For More Information-Footnote-515283777
Ref: For More Information-Footnote-615283829
Node: 描述器 Descriptor 指南15283900
Ref: howto/descriptor doc15284097
Ref: 4cb015284097
Ref: howto/descriptor descriptor-guide15284097
Ref: 4cb115284097
Ref: howto/descriptor descriptorhowto15284097
Ref: 145a15284097
Node: Primer15285257
Ref: howto/descriptor primer15285362
Ref: 4cb215285362
Node: Simple example A descriptor that returns a constant15285704
Ref: howto/descriptor simple-example-a-descriptor-that-returns-a-constant15285822
Ref: 4cb315285822
Node: Dynamic lookups15287280
Ref: howto/descriptor dynamic-lookups15287425
Ref: 4cb415287425
Node: Managed attributes15288821
Ref: howto/descriptor managed-attributes15288931
Ref: 4cb515288931
Node: Customized names15291568
Ref: howto/descriptor customized-names15291679
Ref: 4cb615291679
Node: Closing thoughts15294012
Ref: howto/descriptor closing-thoughts15294096
Ref: 4cb715294096
Node: Complete Practical Example15295462
Ref: howto/descriptor complete-practical-example15295594
Ref: 4cb815295594
Node: Validator class15295857
Ref: howto/descriptor validator-class15295961
Ref: 4cb915295961
Node: Custom validators15296985
Ref: howto/descriptor custom-validators15297119
Ref: 4cba15297119
Ref: Custom validators-Footnote-115299710
Node: Practical application15299779
Ref: howto/descriptor practical-application15299889
Ref: 4cbb15299889
Node: Technical Tutorial15301274
Ref: howto/descriptor technical-tutorial15301423
Ref: 4cbc15301423
Node: 摘要15301848
Ref: howto/descriptor abstract15301945
Ref: 4cbd15301945
Node: Definition and introduction15302254
Ref: howto/descriptor definition-and-introduction15302375
Ref: 4cbe15302375
Node: 描述器協定15303595
Ref: howto/descriptor descriptor-protocol15303743
Ref: 4cbf15303743
Node: Overview of descriptor invocation15304960
Ref: howto/descriptor overview-of-descriptor-invocation15305108
Ref: 4cc015305108
Node: Invocation from an instance15305743
Ref: howto/descriptor invocation-from-an-instance15305899
Ref: 4cc115305899
Node: Invocation from a class15308374
Ref: howto/descriptor invocation-from-a-class15308518
Ref: 4cc215308518
Ref: Invocation from a class-Footnote-115309090
Node: Invocation from super15309163
Ref: howto/descriptor invocation-from-super15309307
Ref: 4cc315309307
Ref: Invocation from super-Footnote-115309933
Ref: Invocation from super-Footnote-215310006
Node: Summary of invocation logic15310086
Ref: howto/descriptor summary-of-invocation-logic15310234
Ref: 4cc415310234
Node: Automatic name notification15311197
Ref: howto/descriptor automatic-name-notification15311334
Ref: 4cc515311334
Ref: Automatic name notification-Footnote-115312207
Node: ORM 範例15312280
Ref: howto/descriptor orm-example15312381
Ref: 4cc615312381
Ref: ORM 範例-Footnote-115314388
Ref: ORM 範例-Footnote-215314460
Node: Pure Python Equivalents15314513
Ref: howto/descriptor pure-python-equivalents15314627
Ref: 4cc715314627
Node: Properties15315100
Ref: howto/descriptor properties15315200
Ref: 4cc815315200
Node: Functions and methods15318069
Ref: howto/descriptor functions-and-methods15318194
Ref: 4cc915318194
Node: Kinds of methods15321436
Ref: howto/descriptor kinds-of-methods15321565
Ref: 4cca15321565
Node: Static methods15322802
Ref: howto/descriptor static-methods15322923
Ref: 4ccb15322923
Node: Class methods15325029
Ref: howto/descriptor class-methods15325162
Ref: 4ccc15325162
Node: Member objects and __slots__15327218
Ref: howto/descriptor member-objects-and-slots15327328
Ref: 4ccd15327328
Ref: Member objects and __slots__-Footnote-115334951
Node: 使用 GDB 來為 C API 擴充功能和 CPython 內部偵錯15335007
Ref: howto/gdb_helpers doc15335184
Ref: 4cce15335184
Ref: howto/gdb_helpers debugging-c-api-extensions-and-cpython-internals-with-gdb15335184
Ref: 4ccf15335184
Ref: howto/gdb_helpers gdb15335184
Ref: 4cd015335184
Ref: 使用 GDB 來為 C API 擴充功能和 CPython 內部偵錯-Footnote-115336464
Ref: 使用 GDB 來為 C API 擴充功能和 CPython 內部偵錯-Footnote-215336500
Node: 先決條件15336554
Ref: howto/gdb_helpers prerequisites15336711
Ref: 4cd115336711
Node: 使用從原始碼建置的 Python 進行設定15337375
Ref: howto/gdb_helpers setup-with-python-built-from-source15337512
Ref: 4cd215337512
Node: 從 Linux 發行版設定 Python15338286
Ref: howto/gdb_helpers setup-for-python-from-a-linux-distro15338423
Ref: 4cd315338423
Node: 使用偵錯建置與使用開發模式15339016
Ref: howto/gdb_helpers using-the-debug-build-and-development-mode15339212
Ref: 4cd415339212
Node: 使用 python-gdb 擴充功能15339850
Ref: howto/gdb_helpers using-the-python-gdb-extension15340060
Ref: 4cd515340060
Node: 漂亮列印器15340340
Ref: howto/gdb_helpers pretty-printers15340438
Ref: 4cd615340438
Node: py-list15344841
Ref: howto/gdb_helpers py-list15344965
Ref: 4cd715344965
Node: py-up 和 py-down15345823
Ref: howto/gdb_helpers py-up-and-py-down15345937
Ref: 4cd815345937
Node: py-bt15350555
Ref: howto/gdb_helpers py-bt15350670
Ref: 4cd915350670
Node: py-print15352895
Ref: howto/gdb_helpers py-print15353002
Ref: 4cda15353002
Node: py-locals15353730
Ref: howto/gdb_helpers py-locals15353823
Ref: 4cdb15353823
Node: 與 GDB 指令一起使用15354708
Ref: howto/gdb_helpers use-with-gdb-commands15354870
Ref: 4cdc15354870
Node: Enum HOWTO15360868
Ref: howto/enum doc15361036
Ref: 4cdd15361036
Ref: howto/enum enum-howto15361036
Ref: 4cde15361036
Ref: howto/enum id115361036
Ref: 4cdf15361036
Ref: howto/enum enum-basic-tutorial15361067
Ref: 249015361067
Node: Programmatic access to enumeration members and their attributes15366961
Ref: howto/enum enum-advanced-tutorial15367115
Ref: 249115367115
Ref: howto/enum programmatic-access-to-enumeration-members-and-their-attributes15367115
Ref: 4ce015367115
Node: Duplicating enum members and values15367863
Ref: howto/enum duplicating-enum-members-and-values15368060
Ref: 4ce115368060
Node: Ensuring unique enumeration values15369290
Ref: howto/enum ensuring-unique-enumeration-values15369446
Ref: 4ce215369446
Node: Using automatic values15369998
Ref: howto/enum using-automatic-values15370131
Ref: 4ce315370131
Node: Iteration<2>15371057
Ref: howto/enum iteration15371162
Ref: 4ce415371162
Node: 比較15372424
Ref: howto/enum comparisons15372553
Ref: 4ce515372553
Node: Allowed members and attributes of enumerations15373656
Ref: howto/enum allowed-members-and-attributes-of-enumerations15373800
Ref: 4ce715373800
Node: Restricted Enum subclassing15375904
Ref: howto/enum restricted-enum-subclassing15376059
Ref: 4ceb15376059
Node: Dataclass support15377174
Ref: howto/enum dataclass-support15377291
Ref: 4ced15377291
Ref: howto/enum enum-dataclass-support15377291
Ref: 168715377291
Node: Pickling15378657
Ref: howto/enum pickling15378764
Ref: 4cee15378764
Node: Functional API<3>15379700
Ref: howto/enum functional-api15379810
Ref: 4ce815379810
Node: Derived Enumerations15383198
Ref: howto/enum derived-enumerations15383331
Ref: 4cef15383331
Node: IntEnum15383464
Ref: howto/enum intenum15383544
Ref: 4ce615383544
Node: StrEnum15384665
Ref: howto/enum strenum15384761
Ref: 4cf015384761
Node: IntFlag15385068
Ref: howto/enum intflag15385161
Ref: 4cf115385161
Node: Flag15387531
Ref: howto/enum flag15387626
Ref: 4cf215387626
Node: 其他<2>15389921
Ref: howto/enum others15390000
Ref: 4cf315390000
Node: When to use __new__ vs __init__15391990
Ref: howto/enum new-vs-init15392140
Ref: 4cea15392140
Ref: howto/enum when-to-use-new-vs-init15392140
Ref: 4cf415392140
Node: Finer Points15393415
Ref: howto/enum finer-points15393495
Ref: 4cf515393495
Node: Supported __dunder__ names15393844
Ref: howto/enum supported-dunder-names15393952
Ref: 4cf615393952
Node: Supported _sunder_ names15394365
Ref: howto/enum supported-sunder-names15394497
Ref: 4cf715394497
Node: _Private__names15396527
Ref: howto/enum private-names15396649
Ref: 4cf915396649
Node: Enum member type15396817
Ref: howto/enum enum-member-type15396968
Ref: 4cfa15396968
Node: Creating members that are mixed with other data types15397449
Ref: howto/enum creating-members-that-are-mixed-with-other-data-types15397626
Ref: 4cfb15397626
Node: Boolean value of Enum classes and members15398159
Ref: howto/enum boolean-value-of-enum-classes-and-members15398345
Ref: 4cfc15398345
Node: Enum classes with methods15398904
Ref: howto/enum enum-classes-with-methods15399062
Ref: 4cfd15399062
Node: Combining members of Flag15399602
Ref: howto/enum combining-members-of-flag15399743
Ref: 4cfe15399743
Node: Flag and IntFlag minutia15400305
Ref: howto/enum flag-and-intflag-minutia15400412
Ref: 4cff15400412
Node: How are Enums and Flags different?15402939
Ref: howto/enum enum-class-differences15403082
Ref: 249315403082
Ref: howto/enum how-are-enums-and-flags-different15403082
Ref: 4d0015403082
Node: Enum Classes15403417
Ref: howto/enum enum-classes15403521
Ref: 4d0115403521
Node: Flag Classes15404071
Ref: howto/enum flag-classes15404210
Ref: 4d0215404210
Node: Enum Members aka instances15404576
Ref: howto/enum enum-members-aka-instances15404715
Ref: 4d0315404715
Node: Flag Members15405097
Ref: howto/enum flag-members15405215
Ref: 4d0415405215
Node: Enum Cookbook15405849
Ref: howto/enum enum-cookbook15405981
Ref: 249215405981
Ref: howto/enum id215405981
Ref: 4d0515405981
Node: Omitting values15406445
Ref: howto/enum omitting-values15406530
Ref: 4d0615406530
Node: 使用 auto15407318
Ref: howto/enum using-auto15407403
Ref: 4d0715407403
Node: 使用 object15407655
Ref: howto/enum using-object15407775
Ref: 4d0815407775
Node: Using a descriptive string15408422
Ref: howto/enum using-a-descriptive-string15408553
Ref: 4d0915408553
Node: Using a custom __new__15408840
Ref: howto/enum using-a-custom-new15408949
Ref: 4d0a15408949
Node: OrderedEnum15410797
Ref: howto/enum orderedenum15410908
Ref: 4cec15410908
Node: DuplicateFreeEnum15412088
Ref: howto/enum duplicatefreeenum15412198
Ref: 4d0b15412198
Node: MultiValueEnum15413280
Ref: howto/enum multivalueenum15413385
Ref: 4cf815413385
Node: Planet15413968
Ref: howto/enum planet15414066
Ref: 4ce915414066
Node: TimePeriod15415115
Ref: howto/enum enum-time-period15415190
Ref: 24ab15415190
Ref: howto/enum timeperiod15415190
Ref: 4d0c15415190
Node: Subclassing EnumType15415805
Ref: howto/enum enumtype-examples15415894
Ref: 249915415894
Ref: howto/enum subclassing-enumtype15415894
Ref: 4d0d15415894
Node: 函式編程 HOWTO15416158
Ref: howto/functional doc15416293
Ref: 4d0e15416293
Ref: howto/functional functional-howto15416293
Ref: 4d0f15416293
Ref: howto/functional functional-programming-howto15416293
Ref: 4d1015416293
Node: 簡介<11>15417040
Ref: howto/functional introduction15417123
Ref: 4d1115417123
Node: Formal provability15421781
Ref: howto/functional formal-provability15421865
Ref: 4d1315421865
Node: Modularity15423761
Ref: howto/functional modularity15423883
Ref: 4d1415423883
Node: Ease of debugging and testing15424286
Ref: howto/functional ease-of-debugging-and-testing15424403
Ref: 4d1515424403
Node: Composability15425132
Ref: howto/functional composability15425230
Ref: 4d1615425230
Node: Iterators15425947
Ref: howto/functional functional-howto-iterators15426084
Ref: 4d1215426084
Ref: howto/functional iterators15426084
Ref: 4d1715426084
Node: Data Types That Support Iterators15429425
Ref: howto/functional data-types-that-support-iterators15429504
Ref: 4d1815429504
Node: Generator expressions and list comprehensions15431462
Ref: howto/functional generator-expressions-and-list-comprehensions15431599
Ref: 4d1915431599
Node: Generators15436131
Ref: howto/functional generators15436274
Ref: 4d1a15436274
Ref: Generators-Footnote-115440111
Node: Passing values into a generator15440192
Ref: howto/functional passing-values-into-a-generator15440270
Ref: 4d1b15440270
Ref: Passing values into a generator-Footnote-115444209
Node: 內建函式<2>15444251
Ref: howto/functional built-in-functions15444365
Ref: 4d1c15444365
Ref: 內建函式<2>-Footnote-115448375
Node: itertools 模組15448429
Ref: howto/functional the-itertools-module15448549
Ref: 4d1d15448549
Node: 建立新的疊代器15449271
Ref: howto/functional creating-new-iterators15449383
Ref: 4d1e15449383
Node: Calling functions on elements15452048
Ref: howto/functional calling-functions-on-elements15452187
Ref: 4d1f15452187
Node: Selecting elements15452997
Ref: howto/functional selecting-elements15453137
Ref: 4d2015453137
Node: Combinatoric functions15454624
Ref: howto/functional combinatoric-functions15454752
Ref: 4d2115454752
Node: Grouping elements15457077
Ref: howto/functional grouping-elements15457178
Ref: 4d2215457178
Node: functools 模組15458722
Ref: howto/functional the-functools-module15458868
Ref: 4d2315458868
Node: operator 模組15462443
Ref: howto/functional the-operator-module15462511
Ref: 4d2415462511
Node: Small functions and the lambda expression15463304
Ref: howto/functional small-functions-and-the-lambda-expression15463471
Ref: 4d2515463471
Node: Revision History and Acknowledgements15466306
Ref: howto/functional revision-history-and-acknowledgements15466470
Ref: 4d2615466470
Node: References<2>15467247
Ref: howto/functional references15467361
Ref: 4d2715467361
Node: General15467464
Ref: howto/functional general15467545
Ref: 4d2815467545
Node: Python-specific15468609
Ref: howto/functional python-specific15468718
Ref: 4d2915468718
Ref: Python-specific-Footnote-115469184
Ref: Python-specific-Footnote-215469235
Ref: Python-specific-Footnote-315469288
Node: Python 說明文件15469341
Ref: howto/functional python-documentation15469434
Ref: 4d2a15469434
Ref: Python 說明文件-Footnote-115469830
Ref: Python 說明文件-Footnote-215469872
Node: 如何使用 Logging 模組15469914
Ref: howto/logging doc15470055
Ref: 4d2b15470055
Ref: howto/logging id115470055
Ref: 4d2c15470055
Ref: howto/logging logging-howto15470055
Ref: 4d2d15470055
Ref: howto/logging logging-basic-tutorial15470170
Ref: 118d15470170
Node: 基礎 Logging 指南15470570
Ref: howto/logging basic-logging-tutorial15470689
Ref: 4d2f15470689
Node: 什麼時候使用 logging15471394
Ref: howto/logging when-to-use-logging15471508
Ref: 4d3015471508
Node: 一個簡單範例<2>15475504
Ref: howto/logging a-simple-example15475644
Ref: 4d3115475644
Ref: howto/logging howto-minimal-example15475644
Ref: 4d3215475644
Node: Logging to a file15476875
Ref: howto/logging logging-to-a-file15477010
Ref: 4d3315477010
Node: Logging variable data15480066
Ref: howto/logging logging-variable-data15480221
Ref: 4d3415480221
Node: Changing the format of displayed messages15481038
Ref: howto/logging changing-the-format-of-displayed-messages15481212
Ref: 4d3515481212
Node: Displaying the date/time in messages15482202
Ref: howto/logging displaying-the-date-time-in-messages15482365
Ref: 4d3615482365
Ref: Displaying the date/time in messages-Footnote-115483412
Node: Next Steps15483471
Ref: howto/logging next-steps15483584
Ref: 4d3715483584
Node: Advanced Logging Tutorial15484521
Ref: howto/logging advanced-logging-tutorial15484666
Ref: 4d3815484666
Ref: howto/logging logging-advanced-tutorial15484666
Ref: 118e15484666
Node: Logging Flow15488027
Ref: howto/logging logging-flow15488117
Ref: 4d3915488117
Node: Loggers15488312
Ref: howto/logging loggers15488419
Ref: 4d3a15488419
Node: Handlers15492692
Ref: howto/logging handler-basic15492797
Ref: 4d3b15492797
Ref: howto/logging handlers15492797
Ref: 4d3c15492797
Node: Formatters15494868
Ref: howto/logging formatters15494985
Ref: 4d3e15494985
Ref: howto/logging logging logging Formatter __init__15495431
Ref: 4d3f15495431
Node: Configuring Logging15497124
Ref: howto/logging configuring-logging15497277
Ref: 4d4015497277
Node: What happens if no configuration is provided15503826
Ref: howto/logging what-happens-if-no-configuration-is-provided15504002
Ref: 4d4115504002
Node: Configuring Logging for a Library15505251
Ref: howto/logging configuring-logging-for-a-library15505399
Ref: 4d4215505399
Ref: howto/logging library-config15505399
Ref: 2c2b15505399
Node: Logging Levels<2>15508240
Ref: howto/logging logging-levels15508379
Ref: 4d4315508379
Node: Custom Levels15511230
Ref: howto/logging custom-levels15511297
Ref: 2bf715511297
Ref: howto/logging id215511297
Ref: 4d4415511297
Node: Useful Handlers15512008
Ref: howto/logging id315512154
Ref: 4d4515512154
Ref: howto/logging useful-handlers15512154
Ref: 4d3d15512154
Node: Exceptions raised during logging15516175
Ref: howto/logging exceptions-raised-during-logging15516339
Ref: 4d4615516339
Ref: howto/logging logging-exceptions15516339
Ref: 4d4715516339
Node: Using arbitrary objects as messages15517512
Ref: howto/logging arbitrary-object-messages15517674
Ref: 2be315517674
Ref: howto/logging using-arbitrary-objects-as-messages15517674
Ref: 4d4815517674
Node: 最佳化<17>15518286
Ref: howto/logging optimization15518431
Ref: 4d4915518431
Node: 其他資源<2>15522067
Ref: howto/logging other-resources15522168
Ref: 4d4a15522168
Ref: howto/logging tutorial-ref-links15522168
Ref: 4d2e15522168
Node: Logging Cookbook15522499
Ref: howto/logging-cookbook doc15522649
Ref: 4d4b15522649
Ref: howto/logging-cookbook id115522649
Ref: 4d4c15522649
Ref: howto/logging-cookbook logging-cookbook15522649
Ref: 118f15522649
Node: Using logging in multiple modules15524718
Ref: howto/logging-cookbook using-logging-in-multiple-modules15524842
Ref: 4d4e15524842
Node: Logging from multiple threads15528414
Ref: howto/logging-cookbook logging-from-multiple-threads15528579
Ref: 4d4f15528579
Node: Multiple handlers and formatters15530324
Ref: howto/logging-cookbook multiple-handlers-and-formatters15530488
Ref: 4d5015530488
Node: Logging to multiple destinations15532645
Ref: howto/logging-cookbook logging-to-multiple-destinations15532805
Ref: 4d5115532805
Ref: howto/logging-cookbook multiple-destinations15532805
Ref: 4d5215532805
Node: Custom handling of levels15535968
Ref: howto/logging-cookbook custom-handling-of-levels15536124
Ref: 4d5315536124
Ref: howto/logging-cookbook custom-level-handling15536124
Ref: 4d5415536124
Node: Configuration server example15541994
Ref: howto/logging-cookbook configuration-server-example15542150
Ref: 4d5515542150
Node: Dealing with handlers that block15543710
Ref: howto/logging-cookbook blocking-handlers15543894
Ref: 322d15543894
Ref: howto/logging-cookbook dealing-with-handlers-that-block15543894
Ref: 4d5615543894
Node: Sending and receiving logging events across a network15548071
Ref: howto/logging-cookbook network-logging15548279
Ref: 4d5715548279
Ref: howto/logging-cookbook sending-and-receiving-logging-events-across-a-network15548279
Ref: 4d5815548279
Node: Running a logging socket listener in production15553812
Ref: howto/logging-cookbook running-a-logging-socket-listener-in-production15553949
Ref: 4d5915553949
Ref: Running a logging socket listener in production-Footnote-115557463
Ref: Running a logging socket listener in production-Footnote-215557495
Ref: Running a logging socket listener in production-Footnote-315557567
Ref: Running a logging socket listener in production-Footnote-415557597
Node: Adding contextual information to your logging output15557669
Ref: howto/logging-cookbook adding-contextual-information-to-your-logging-output15557863
Ref: 4d5a15557863
Ref: howto/logging-cookbook context-info15557863
Ref: 2bea15557863
Node: Using LoggerAdapters to impart contextual information15558958
Ref: howto/logging-cookbook using-loggeradapters-to-impart-contextual-information15559155
Ref: 4d5b15559155
Node: Using objects other than dicts to pass contextual information15562414
Ref: howto/logging-cookbook using-objects-other-than-dicts-to-pass-contextual-information15562565
Ref: 4d5c15562565
Node: Using Filters to impart contextual information15563027
Ref: howto/logging-cookbook filters-contextual15563224
Ref: 2bdf15563224
Ref: howto/logging-cookbook using-filters-to-impart-contextual-information15563224
Ref: 4d5d15563224
Node: Use of contextvars15567027
Ref: howto/logging-cookbook use-of-contextvars15567212
Ref: 4d5e15567212
Node: Imparting contextual information in handlers15576786
Ref: howto/logging-cookbook imparting-contextual-information-in-handlers15576967
Ref: 4d5f15576967
Node: Logging to a single file from multiple processes15577912
Ref: howto/logging-cookbook logging-to-a-single-file-from-multiple-processes15578094
Ref: 4d6015578094
Ref: howto/logging-cookbook multiple-processes15578094
Ref: 4d6115578094
Node: Using concurrent futures ProcessPoolExecutor15588590
Ref: howto/logging-cookbook using-concurrent-futures-processpoolexecutor15588779
Ref: 4d6215588779
Node: Deploying Web applications using Gunicorn and uWSGI15589785
Ref: howto/logging-cookbook deploying-web-applications-using-gunicorn-and-uwsgi15589974
Ref: 4d6315589974
Ref: Deploying Web applications using Gunicorn and uWSGI-Footnote-115590634
Ref: Deploying Web applications using Gunicorn and uWSGI-Footnote-215590664
Node: Using file rotation15590717
Ref: howto/logging-cookbook using-file-rotation15590891
Ref: 4d6415590891
Node: Use of alternative formatting styles15592794
Ref: howto/logging-cookbook format-styles15592941
Ref: 4d6515592941
Ref: howto/logging-cookbook use-of-alternative-formatting-styles15592941
Ref: 4d6615592941
Node: Customizing LogRecord15600065
Ref: howto/logging-cookbook custom-logrecord15600253
Ref: 4d6715600253
Ref: howto/logging-cookbook customizing-logrecord15600253
Ref: 4d6815600253
Node: Subclassing QueueHandler and QueueListener- a ZeroMQ example15604156
Ref: howto/logging-cookbook subclassing-queuehandler-and-queuelistener-a-zeromq-example15604367
Ref: 4d6915604367
Ref: howto/logging-cookbook zeromq-handlers15604367
Ref: 4d6a15604367
Node: Subclass QueueHandler15604567
Ref: howto/logging-cookbook subclass-queuehandler15604716
Ref: 4d6b15604716
Node: Subclass QueueListener15606017
Ref: howto/logging-cookbook subclass-queuelistener15606166
Ref: 4d6c15606166
Node: Subclassing QueueHandler and QueueListener- a pynng example15606905
Ref: howto/logging-cookbook pynng-handlers15607136
Ref: 4d6d15607136
Ref: howto/logging-cookbook subclassing-queuehandler-and-queuelistener-a-pynng-example15607136
Ref: 4d6e15607136
Ref: Subclassing QueueHandler and QueueListener- a pynng example-Footnote-115607760
Ref: Subclassing QueueHandler and QueueListener- a pynng example-Footnote-215607800
Node: Subclass QueueListener<2>15607833
Ref: howto/logging-cookbook id315607987
Ref: 4d6f15607987
Node: Subclass QueueHandler<2>15609963
Ref: howto/logging-cookbook id415610117
Ref: 4d7015610117
Node: An example dictionary-based configuration15613829
Ref: howto/logging-cookbook an-example-dictionary-based-configuration15614062
Ref: 4d7115614062
Ref: An example dictionary-based configuration-Footnote-115615994
Ref: An example dictionary-based configuration-Footnote-215616080
Node: Using a rotator and namer to customize log rotation processing15616166
Ref: howto/logging-cookbook cookbook-rotator-namer15616380
Ref: 2c3815616380
Ref: howto/logging-cookbook using-a-rotator-and-namer-to-customize-log-rotation-processing15616380
Ref: 4d7215616380
Node: A more elaborate multiprocessing example15617781
Ref: howto/logging-cookbook a-more-elaborate-multiprocessing-example15618007
Ref: 4d7315618007
Node: Inserting a BOM into messages sent to a SysLogHandler15627631
Ref: howto/logging-cookbook inserting-a-bom-into-messages-sent-to-a-sysloghandler15627826
Ref: 4d7415627826
Ref: Inserting a BOM into messages sent to a SysLogHandler-Footnote-115629983
Ref: Inserting a BOM into messages sent to a SysLogHandler-Footnote-215630042
Ref: Inserting a BOM into messages sent to a SysLogHandler-Footnote-315630111
Ref: Inserting a BOM into messages sent to a SysLogHandler-Footnote-415630170
Node: Implementing structured logging15630229
Ref: howto/logging-cookbook implementing-structured-logging15630420
Ref: 4d7515630420
Node: Customizing handlers with dictConfig15632954
Ref: howto/logging-cookbook custom-handlers15633154
Ref: 4d7615633154
Ref: howto/logging-cookbook customizing-handlers-with-dictconfig15633154
Ref: 4d7715633154
Node: Using particular formatting styles throughout your application15638346
Ref: howto/logging-cookbook formatting-styles15638550
Ref: 2bd315638550
Ref: howto/logging-cookbook using-particular-formatting-styles-throughout-your-application15638550
Ref: 4d7815638550
Node: Using LogRecord factories15640552
Ref: howto/logging-cookbook using-logrecord-factories15640713
Ref: 4d7915640713
Node: Using custom message objects15641687
Ref: howto/logging-cookbook using-custom-message-objects15641848
Ref: 4d7a15641848
Node: Configuring filters with dictConfig15644552
Ref: howto/logging-cookbook configuring-filters-with-dictconfig15644751
Ref: 4d7b15644751
Ref: howto/logging-cookbook filters-dictconfig15644751
Ref: 4d7c15644751
Node: Customized exception formatting15647712
Ref: howto/logging-cookbook custom-format-exception15647874
Ref: 4d7d15647874
Ref: howto/logging-cookbook customized-exception-formatting15647874
Ref: 4d7e15647874
Node: Speaking logging messages15649935
Ref: howto/logging-cookbook speaking-logging-messages15650122
Ref: 4d7f15650122
Ref: howto/logging-cookbook spoken-messages15650122
Ref: 4d8015650122
Node: Buffering logging messages and outputting them conditionally15652272
Ref: howto/logging-cookbook buffered-logging15652476
Ref: 4d8115652476
Ref: howto/logging-cookbook buffering-logging-messages-and-outputting-them-conditionally15652476
Ref: 4d8215652476
Node: Sending logging messages to email with buffering15658044
Ref: howto/logging-cookbook buffered-smtp15658271
Ref: 4d8315658271
Ref: howto/logging-cookbook sending-logging-messages-to-email-with-buffering15658271
Ref: 4d8415658271
Node: Formatting times using UTC GMT via configuration15661837
Ref: howto/logging-cookbook formatting-times-using-utc-gmt-via-configuration15662049
Ref: 4d8515662049
Ref: howto/logging-cookbook utc-formatting15662049
Ref: 4d8615662049
Node: Using a context manager for selective logging15663950
Ref: howto/logging-cookbook context-manager15664148
Ref: 4d8715664148
Ref: howto/logging-cookbook using-a-context-manager-for-selective-logging15664148
Ref: 4d8815664148
Node: A CLI application starter template15668710
Ref: howto/logging-cookbook a-cli-application-starter-template15668880
Ref: 4d8915668880
Ref: howto/logging-cookbook starter-template15668880
Ref: 4d8a15668880
Node: A Qt GUI for logging15674855
Ref: howto/logging-cookbook a-qt-gui-for-logging15675018
Ref: 4d8b15675018
Ref: howto/logging-cookbook qt-gui15675018
Ref: 4d8c15675018
Ref: A Qt GUI for logging-Footnote-115685319
Ref: A Qt GUI for logging-Footnote-215685346
Ref: A Qt GUI for logging-Footnote-315685388
Node: Logging to syslog with RFC5424 support15685428
Ref: howto/logging-cookbook logging-to-syslog-with-rfc5424-support15685600
Ref: 4d8d15685600
Ref: Logging to syslog with RFC5424 support-Footnote-115689326
Ref: Logging to syslog with RFC5424 support-Footnote-215689385
Node: How to treat a logger like an output stream15689444
Ref: howto/logging-cookbook how-to-treat-a-logger-like-an-output-stream15689613
Ref: 4d8e15689613
Node: Patterns to avoid15694277
Ref: howto/logging-cookbook patterns-to-avoid15694423
Ref: 4d8f15694423
Node: Opening the same log file multiple times15694975
Ref: howto/logging-cookbook opening-the-same-log-file-multiple-times15695146
Ref: 4d9015695146
Node: Using loggers as attributes in a class or passing them as parameters15697063
Ref: howto/logging-cookbook using-loggers-as-attributes-in-a-class-or-passing-them-as-parameters15697306
Ref: 4d9115697306
Node: Adding handlers other than NullHandler to a logger in a library15697988
Ref: howto/logging-cookbook adding-handlers-other-than-nullhandler-to-a-logger-in-a-library15698216
Ref: 4d9215698216
Node: Creating a lot of loggers15698654
Ref: howto/logging-cookbook creating-a-lot-of-loggers15698805
Ref: 4d9315698805
Node: Other resources15699358
Ref: howto/logging-cookbook cookbook-ref-links15699452
Ref: 4d4d15699452
Ref: howto/logging-cookbook other-resources15699452
Ref: 4d9415699452
Node: 如何使用正規表示式15699816
Ref: howto/regex doc15699964
Ref: 4d9515699964
Ref: howto/regex regex-howto15699964
Ref: 21c915699964
Ref: howto/regex regular-expression-howto15699964
Ref: 4d9615699964
Node: 簡介<12>15700393
Ref: howto/regex introduction15700491
Ref: 4d9715700491
Node: Simple Patterns15701989
Ref: howto/regex simple-patterns15702121
Ref: 4d9815702121
Node: Matching Characters15702610
Ref: howto/regex matching-characters15702706
Ref: 4d9915702706
Node: Repeating Things15707328
Ref: howto/regex repeating-things15707424
Ref: 4d9a15707424
Node: Using Regular Expressions15712476
Ref: howto/regex using-regular-expressions15712616
Ref: 4d9b15712616
Node: Compiling Regular Expressions15713105
Ref: howto/regex compiling-regular-expressions15713225
Ref: 4d9c15713225
Node: The Backslash Plague15714432
Ref: howto/regex id115714579
Ref: 4d9d15714579
Ref: howto/regex the-backslash-plague15714579
Ref: 4d9e15714579
Node: Performing Matches15717455
Ref: howto/regex performing-matches15717598
Ref: 4d9f15717598
Node: Module-Level Functions<2>15723125
Ref: howto/regex module-level-functions15723265
Ref: 4da015723265
Node: Compilation Flags15724457
Ref: howto/regex compilation-flags15724570
Ref: 4da115724570
Node: More Pattern Power15731689
Ref: howto/regex more-pattern-power15731831
Ref: 4da315731831
Node: More Metacharacters15732190
Ref: howto/regex id215732281
Ref: 4da415732281
Ref: howto/regex more-metacharacters15732281
Ref: 4da215732281
Node: Grouping15736928
Ref: howto/regex grouping15737058
Ref: 4da515737058
Node: Non-capturing and Named Groups15740514
Ref: howto/regex non-capturing-and-named-groups15740645
Ref: 4da615740645
Node: Lookahead Assertions15745741
Ref: howto/regex lookahead-assertions15745855
Ref: 4da715745855
Node: Modifying Strings15749492
Ref: howto/regex modifying-strings15749624
Ref: 4da815749624
Node: Splitting Strings15750612
Ref: howto/regex splitting-strings15750713
Ref: 4da915750713
Node: Search and Replace<2>15753021
Ref: howto/regex search-and-replace15753122
Ref: 4daa15753122
Node: Common Problems15757598
Ref: howto/regex common-problems15757720
Ref: 4dab15757720
Node: Use String Methods15758152
Ref: howto/regex use-string-methods15758250
Ref: 4dac15758250
Node: match versus search15759954
Ref: howto/regex match-versus-search15760085
Ref: 4dad15760085
Node: Greedy versus Non-Greedy15761711
Ref: howto/regex greedy-versus-non-greedy15761840
Ref: 4dae15761840
Node: Using re VERBOSE15763750
Ref: howto/regex using-re-verbose15763851
Ref: 4daf15763851
Node: Feedback15765370
Ref: howto/regex feedback15765466
Ref: 4db015765466
Node: Socket 程式設計指南15766231
Ref: howto/sockets doc15766375
Ref: 4db115766375
Ref: howto/sockets socket-howto15766375
Ref: 327d15766375
Ref: howto/sockets socket-programming-howto15766375
Ref: 4db215766375
Node: Sockets15767004
Ref: howto/sockets sockets15767101
Ref: 4db315767101
Node: 歷史15768341
Ref: howto/sockets history15768391
Ref: 4db415768391
Node: 建立一個 Socket15768954
Ref: howto/sockets creating-a-socket15769079
Ref: 4db515769079
Node: IPC15772383
Ref: howto/sockets ipc15772442
Ref: 4db615772442
Node: 使用一個 Socket15772945
Ref: howto/sockets using-a-socket15773075
Ref: 4db715773075
Node: 二進位資料15779299
Ref: howto/sockets binary-data15779370
Ref: 4db815779370
Ref: 二進位資料-Footnote-115780831
Node: 結束連線15780891
Ref: howto/sockets disconnecting15781022
Ref: 4db915781022
Node: Sockets 何時銷毀15782540
Ref: howto/sockets when-sockets-die15782609
Ref: 4dba15782609
Node: 非阻塞的 Sockets15783425
Ref: howto/sockets non-blocking-sockets15783528
Ref: 4dbb15783528
Node: 排序技法15787578
Ref: howto/sorting doc15787708
Ref: 4dbc15787708
Ref: howto/sorting sorting-techniques15787708
Ref: 4dbd15787708
Ref: howto/sorting sortinghowto15787708
Ref: 205a15787708
Node: 基礎排序15788522
Ref: howto/sorting sorting-basics15788615
Ref: 4dbe15788615
Node: 鍵函式 key functions15789390
Ref: howto/sorting key-functions15789549
Ref: 4dbf15789549
Node: Operator Module Functions and Partial Function Evaluation15791447
Ref: howto/sorting operator-module-functions-and-partial-function-evaluation15791609
Ref: 4dc015791609
Ref: Operator Module Functions and Partial Function Evaluation-Footnote-115793400
Node: 升冪與降冪15793444
Ref: howto/sorting ascending-and-descending15793613
Ref: 4dc115793613
Node: 排序穩定性與複合排序15794095
Ref: howto/sorting sort-stability-and-complex-sorts15794258
Ref: 4dc215794258
Ref: 排序穩定性與複合排序-Footnote-115795860
Ref: 排序穩定性與複合排序-Footnote-215795926
Node: 裝飾-排序-移除裝飾 decorate-sort-undecorate15795972
Ref: howto/sorting decorate-sort-undecorate15796153
Ref: 4dc315796153
Ref: 裝飾-排序-移除裝飾 decorate-sort-undecorate-Footnote-115797798
Node: 比較函式 comparison functions15797858
Ref: howto/sorting comparison-functions15798021
Ref: 4dc415798021
Ref: 比較函式 comparison functions-Footnote-115798875
Node: 雜項說明15798962
Ref: howto/sorting odds-and-ends15799087
Ref: 4dc515799087
Ref: 雜項說明-Footnote-115801265
Node: Partial Sorts15801307
Ref: howto/sorting partial-sorts15801390
Ref: 4dc615801390
Node: Unicode HOWTO15802473
Ref: howto/unicode doc15802622
Ref: 4dc715802622
Ref: howto/unicode id115802622
Ref: 4dc815802622
Ref: howto/unicode unicode-howto15802622
Ref: 123b15802622
Node: Introduction to Unicode15803003
Ref: howto/unicode introduction-to-unicode15803109
Ref: 4dc915803109
Node: 定義15803236
Ref: howto/unicode definitions15803320
Ref: 4dca15803320
Ref: 定義-Footnote-115806307
Node: Encodings15806364
Ref: howto/unicode encodings15806470
Ref: 4dcb15806470
Node: References<3>15810115
Ref: howto/unicode references15810206
Ref: 4dcc15810206
Ref: References<3>-Footnote-115811075
Ref: References<3>-Footnote-215811107
Ref: References<3>-Footnote-315811148
Ref: References<3>-Footnote-415811200
Ref: References<3>-Footnote-515811247
Ref: References<3>-Footnote-615811421
Ref: References<3>-Footnote-715811478
Node: Python's Unicode Support15811522
Ref: howto/unicode python-s-unicode-support15811669
Ref: 4dcd15811669
Node: The String Type15812030
Ref: howto/unicode the-string-type15812134
Ref: 4dce15812134
Node: Converting to Bytes15815232
Ref: howto/unicode converting-to-bytes15815383
Ref: 4dcf15815383
Node: Unicode Literals in Python Source Code15817225
Ref: howto/unicode unicode-literals-in-python-source-code15817379
Ref: 4dd015817379
Ref: Unicode Literals in Python Source Code-Footnote-115819470
Node: Unicode Properties15819512
Ref: howto/unicode unicode-properties15819664
Ref: 4dd115819664
Ref: Unicode Properties-Footnote-115821395
Node: Comparing Strings15821465
Ref: howto/unicode comparing-strings15821606
Ref: 4dd215821606
Node: Unicode Regular Expressions15824418
Ref: howto/unicode unicode-regular-expressions15824554
Ref: 4dd315824554
Node: References<4>15825687
Ref: howto/unicode id215825797
Ref: 4dd415825797
Ref: References<4>-Footnote-115826547
Ref: References<4>-Footnote-215826643
Ref: References<4>-Footnote-315826695
Node: Reading and Writing Unicode Data15826764
Ref: howto/unicode reading-and-writing-unicode-data15826898
Ref: 4dd515826898
Node: Unicode filenames15830574
Ref: howto/unicode unicode-filenames15830708
Ref: 4dd615830708
Node: Tips for Writing Unicode-aware Programs15833161
Ref: howto/unicode tips-for-writing-unicode-aware-programs15833317
Ref: 4dd715833317
Node: Converting Between File Encodings15834678
Ref: howto/unicode converting-between-file-encodings15834824
Ref: 4dd815834824
Node: Files in an Unknown Encoding15835591
Ref: howto/unicode files-in-an-unknown-encoding15835737
Ref: 4dd915835737
Node: References<5>15836634
Ref: howto/unicode id315836764
Ref: 4dda15836764
Ref: References<5>-Footnote-115837370
Ref: References<5>-Footnote-215837442
Ref: References<5>-Footnote-315837547
Node: 致謝<10>15837616
Ref: howto/unicode acknowledgements15837717
Ref: 4ddb15837717
Node: 如何使用 urllib 套件取得網路資源15838219
Ref: howto/urllib2 doc15838371
Ref: 4ddc15838371
Ref: howto/urllib2 howto-fetch-internet-resources-using-the-urllib-package15838371
Ref: 4ddd15838371
Ref: howto/urllib2 urllib-howto15838371
Ref: 383615838371
Ref: 如何使用 urllib 套件取得網路資源-Footnote-115838730
Node: 簡介<13>15838769
Ref: howto/urllib2 introduction15838889
Ref: 4dde15838889
Ref: 簡介<13>-Footnote-115840282
Ref: 簡介<13>-Footnote-215840399
Node: 從 URL 取得資源15840458
Ref: howto/urllib2 fetching-urls15840606
Ref: 4ddf15840606
Node: Data15842825
Ref: howto/urllib2 data15842902
Ref: 4de015842902
Ref: Data-Footnote-115845546
Node: Headers15845615
Ref: howto/urllib2 headers15845692
Ref: 4de115845692
Ref: Headers-Footnote-115847202
Ref: Headers-Footnote-215847230
Ref: Headers-Footnote-315847440
Ref: Headers-Footnote-415847555
Node: Handling Exceptions15847674
Ref: howto/urllib2 handling-exceptions15847827
Ref: 4de315847827
Node: URLError15848329
Ref: howto/urllib2 urlerror15848411
Ref: 4de415848411
Node: HTTPError15848962
Ref: howto/urllib2 httperror15849067
Ref: 4de515849067
Ref: HTTPError-Footnote-115849932
Node: Error Codes15849991
Ref: howto/urllib2 error-codes15850048
Ref: 4de615850048
Ref: Error Codes-Footnote-115854801
Node: Wrapping it Up15854860
Ref: howto/urllib2 wrapping-it-up15854948
Ref: 4de715854948
Node: Number 115855180
Ref: howto/urllib2 number-115855256
Ref: 4de815855256
Node: Number 215855883
Ref: howto/urllib2 number-215855959
Ref: 4de915855959
Node: info and geturl15856491
Ref: howto/urllib2 info-and-geturl15856644
Ref: 4de215856644
Ref: info and geturl-Footnote-115857566
Node: Openers and Handlers15857604
Ref: howto/urllib2 openers-and-handlers15857758
Ref: 4dea15857758
Node: Basic Authentication15859400
Ref: howto/urllib2 id515859546
Ref: 4deb15859546
Ref: Basic Authentication-Footnote-115862933
Node: Proxies15863050
Ref: howto/urllib2 proxies15863194
Ref: 4dec15863194
Ref: Proxies-Footnote-115864218
Ref: Proxies-Footnote-215864520
Ref: Proxies-Footnote-315864637
Node: Sockets and Layers15864804
Ref: howto/urllib2 sockets-and-layers15864937
Ref: 4ded15864937
Node: 註解<2>15865956
Ref: howto/urllib2 footnotes15866073
Ref: 4dee15866073
Node: Argparse 教學15866153
Ref: howto/argparse doc15866314
Ref: 4def15866314
Ref: howto/argparse argparse-tutorial15866314
Ref: 2b4415866314
Ref: howto/argparse id115866314
Ref: 4df015866314
Node: 概念15866998
Ref: howto/argparse concepts15867080
Ref: 4df115867080
Node: 基本用法<4>15869025
Ref: howto/argparse the-basics15869137
Ref: 4df215869137
Node: 位置引數的介紹15870279
Ref: howto/argparse introducing-positional-arguments15870406
Ref: 4df315870406
Node: 可選引數的介紹15873527
Ref: howto/argparse introducing-optional-arguments15873672
Ref: 4df415873672
Node: 短選項15876575
Ref: howto/argparse short-options15876642
Ref: 4df515876642
Node: 組合位置引數和可選引數15877354
Ref: howto/argparse combining-positional-and-optional-arguments15877493
Ref: 4df615877493
Node: 更進階一點15885464
Ref: howto/argparse getting-a-little-more-advanced15885610
Ref: 4df715885610
Node: 指定不明確的引數15887551
Ref: howto/argparse id215887657
Ref: 4df815887657
Ref: howto/argparse specifying-ambiguous-arguments15887657
Ref: 2b7415887657
Node: 相互衝突的選項15888557
Ref: howto/argparse conflicting-options15888663
Ref: 4df915888663
Node: 如何翻譯 argparse 輸出15891649
Ref: howto/argparse how-to-translate-the-argparse-output15891768
Ref: 4dfa15891768
Ref: 如何翻譯 argparse 輸出-Footnote-115893443
Node: 結論15893476
Ref: howto/argparse conclusion15893571
Ref: 4dfb15893571
Node: ipaddress 模組介紹15893816
Ref: howto/ipaddress doc15893975
Ref: 4dfc15893975
Ref: howto/ipaddress an-introduction-to-the-ipaddress-module15893975
Ref: 4dfd15893975
Ref: howto/ipaddress ipaddress-howto15893975
Ref: 3a5c15893975
Node: Creating Address/Network/Interface objects15894607
Ref: howto/ipaddress creating-address-network-interface-objects15894761
Ref: 4dfe15894761
Node: A Note on IP Versions15895179
Ref: howto/ipaddress a-note-on-ip-versions15895305
Ref: 4dff15895305
Node: IP Host Addresses15896085
Ref: howto/ipaddress ip-host-addresses15896232
Ref: 4e0015896232
Node: 定義網路15897413
Ref: howto/ipaddress defining-networks15897554
Ref: 4e0115897554
Node: Host Interfaces15899892
Ref: howto/ipaddress host-interfaces15900007
Ref: 4e0215900007
Node: Inspecting Address/Network/Interface Objects15901004
Ref: howto/ipaddress inspecting-address-network-interface-objects15901197
Ref: 4e0315901197
Node: Networks as lists of Addresses15903537
Ref: howto/ipaddress networks-as-lists-of-addresses15903702
Ref: 4e0415903702
Node: Comparisons<2>15904497
Ref: howto/ipaddress comparisons15904655
Ref: 4e0515904655
Node: Using IP Addresses with other modules15905012
Ref: howto/ipaddress using-ip-addresses-with-other-modules15905188
Ref: 4e0615905188
Node: Getting more detail when instance creation fails15905615
Ref: howto/ipaddress getting-more-detail-when-instance-creation-fails15905768
Ref: 4e0715905768
Node: 使用 DTrace 和 SystemTap 檢測 CPython15907820
Ref: howto/instrumentation doc15908004
Ref: 4e0815908004
Ref: howto/instrumentation instrumentation15908004
Ref: c1315908004
Ref: howto/instrumentation instrumenting-cpython-with-dtrace-and-systemtap15908004
Ref: 4e0915908004
Node: 啟用靜態標記15909137
Ref: howto/instrumentation enabling-the-static-markers15909263
Ref: 4e0a15909263
Node: 靜態 DTrace 探針15913404
Ref: howto/instrumentation static-dtrace-probes15913562
Ref: 4e0b15913562
Node: 靜態 SystemTap 標記15915944
Ref: howto/instrumentation static-systemtap-markers15916105
Ref: 4e0c15916105
Node: 可用的靜態標記15918104
Ref: howto/instrumentation available-static-markers15918262
Ref: 4e0d15918262
Node: SystemTap Tapsets15920598
Ref: howto/instrumentation systemtap-tapsets15920743
Ref: 4e0e15920743
Node: 範例<54>15922281
Ref: howto/instrumentation examples15922396
Ref: 4e0f15922396
Node: Python 對 Linux perf 分析器的支援15923686
Ref: howto/perf_profiling doc15923878
Ref: 163b15923878
Ref: howto/perf_profiling perf-profiling15923878
Ref: 17515923878
Ref: howto/perf_profiling python-support-for-the-linux-perf-profiler15923878
Ref: 4e1015923878
Ref: Python 對 Linux perf 分析器的支援-Footnote-115931636
Node: 如何啟用 perf 分析支援15931673
Ref: howto/perf_profiling how-to-enable-perf-profiling-support15931813
Ref: 4e1115931813
Node: 如何獲得最佳結果15932872
Ref: howto/perf_profiling how-to-obtain-the-best-results15933055
Ref: 4e1215933055
Node: How to work without frame pointers15933813
Ref: howto/perf_profiling how-to-work-without-frame-pointers15933957
Ref: 4e1315933957
Node: 註釋 annotation 最佳實踐15936947
Ref: howto/annotations doc15937115
Ref: 4e1415937115
Ref: howto/annotations annotations-best-practices15937115
Ref: 4e1515937115
Ref: howto/annotations annotations-howto15937115
Ref: 77d15937115
Node: 在 Python 3 10 及更高版本中存取物件的註釋字典15938375
Ref: howto/annotations accessing-the-annotations-dict-of-an-object-in-python-3-10-and-newer15938572
Ref: 4e1615938572
Node: 在 Python 3 9 及更早版本中存取物件的註釋字典15940108
Ref: howto/annotations accessing-the-annotations-dict-of-an-object-in-python-3-9-and-older15940341
Ref: 4e1715940341
Node: 手動取消字串化註釋15942662
Ref: howto/annotations manually-un-stringizing-stringized-annotations15942889
Ref: 4e1815942889
Ref: 手動取消字串化註釋-Footnote-115945073
Node: 任何 Python 版本中 __annotations__ 的最佳實踐15945115
Ref: howto/annotations best-practices-for-annotations-in-any-python-version15945310
Ref: 4e1915945310
Node: __annotations__ 奇異之處15945947
Ref: howto/annotations annotations-quirks15946106
Ref: 4e1a15946106
Node: 隔離擴充模組15947747
Ref: howto/isolating-extensions doc15947902
Ref: 4e1b15947902
Ref: howto/isolating-extensions isolating-extension-modules15947902
Ref: 4e1c15947902
Ref: howto/isolating-extensions isolating-extensions-howto15947902
Ref: 4ad115947902
Node: Who should read this15948604
Ref: howto/isolating-extensions who-should-read-this15948697
Ref: 4e1d15948697
Node: 背景<2>15948935
Ref: howto/isolating-extensions background15949083
Ref: 4e1e15949083
Node: Enter Per-Module State15950672
Ref: howto/isolating-extensions enter-per-module-state15950772
Ref: 4e1f15950772
Node: Isolated Module Objects15951931
Ref: howto/isolating-extensions isolated-module-objects15952061
Ref: 4e2015952061
Node: Surprising Edge Cases15953098
Ref: howto/isolating-extensions surprising-edge-cases15953197
Ref: 4e2215953197
Node: Making Modules Safe with Multiple Interpreters15954209
Ref: howto/isolating-extensions making-modules-safe-with-multiple-interpreters15954350
Ref: 4e2315954350
Node: Managing Global State15954669
Ref: howto/isolating-extensions managing-global-state15954807
Ref: 4e2115954807
Node: Managing Per-Module State15955763
Ref: howto/isolating-extensions managing-per-module-state15955959
Ref: 4e2515955959
Ref: Managing Per-Module State-Footnote-115957631
Node: Opt-Out Limiting to One Module Object per Process15957705
Ref: howto/isolating-extensions opt-out-limiting-to-one-module-object-per-process15957914
Ref: 4e2415957914
Node: Module State Access from Functions15958608
Ref: howto/isolating-extensions module-state-access-from-functions15958783
Ref: 4e2615958783
Node: Heap Types<2>15959565
Ref: howto/isolating-extensions heap-types15959708
Ref: 4e2715959708
Node: Changing Static Types to Heap Types15961355
Ref: howto/isolating-extensions changing-static-types-to-heap-types15961468
Ref: 4e2815961468
Node: Defining Heap Types15962444
Ref: howto/isolating-extensions defining-heap-types15962593
Ref: 4e2915962593
Node: Garbage-Collection Protocol15963246
Ref: howto/isolating-extensions garbage-collection-protocol15963392
Ref: 4e2a15963392
Node: tp_traverse in Python 3 8 and lower15964480
Ref: howto/isolating-extensions tp-traverse-in-python-3-8-and-lower15964610
Ref: 4e2b15964610
Node: Delegating tp_traverse15965378
Ref: howto/isolating-extensions delegating-tp-traverse15965536
Ref: 4e2c15965536
Node: Defining tp_dealloc15966344
Ref: howto/isolating-extensions defining-tp-dealloc15966489
Ref: 4e2d15966489
Node: Not overriding tp_free15967257
Ref: howto/isolating-extensions not-overriding-tp-free15967401
Ref: 4e2e15967401
Node: Avoiding PyObject_New15967608
Ref: howto/isolating-extensions avoiding-pyobject-new15967724
Ref: 4e2f15967724
Node: Module State Access from Classes15968515
Ref: howto/isolating-extensions module-state-access-from-classes15968682
Ref: 4e3015968682
Node: Module State Access from Regular Methods15969253
Ref: howto/isolating-extensions module-state-access-from-regular-methods15969450
Ref: 4e3115969450
Node: Module State Access from Slot Methods Getters and Setters15971955
Ref: howto/isolating-extensions module-state-access-from-slot-methods-getters-and-setters15972148
Ref: 4e3215972148
Node: Lifetime of the Module State15973579
Ref: howto/isolating-extensions lifetime-of-the-module-state15973723
Ref: 4e3315973723
Node: Open Issues15974266
Ref: howto/isolating-extensions open-issues15974354
Ref: 4e3415974354
Ref: Open Issues-Footnote-115974658
Node: Per-Class Scope15974726
Ref: howto/isolating-extensions per-class-scope15974831
Ref: 4e3515974831
Node: Lossless Conversion to Heap Types15975124
Ref: howto/isolating-extensions lossless-conversion-to-heap-types15975229
Ref: 4e3615975229
Node: timer file descriptor HOWTO15975467
Ref: howto/timerfd doc15975630
Ref: 4e3715975630
Ref: howto/timerfd timer-file-descriptor-howto15975630
Ref: 4e3815975630
Ref: howto/timerfd timerfd-howto15975630
Ref: 4e3915975630
Node: Examples<2>15975824
Ref: howto/timerfd examples15975899
Ref: 4e3a15975899
Node: The Python 2 3 Method Resolution Order15984705
Ref: howto/mro doc15984892
Ref: 4e3b15984892
Ref: howto/mro python-2-3-mro15984892
Ref: 141515984892
Ref: howto/mro the-python-2-3-method-resolution-order15984892
Ref: 4e3c15984892
Ref: The Python 2 3 Method Resolution Order-Footnote-115986487
Node: The beginning15986534
Ref: howto/mro the-beginning15986661
Ref: 4e3d15986661
Ref: The beginning-Footnote-115991238
Ref: The beginning-Footnote-215991375
Node: The C3 Method Resolution Order15991487
Ref: howto/mro the-c3-method-resolution-order15991633
Ref: 4e3e15991633
Node: 範例<55>15993965
Ref: howto/mro examples15994126
Ref: 4e3f15994126
Node: Bad Method Resolution Orders15999657
Ref: howto/mro bad-method-resolution-orders15999795
Ref: 4e4015999795
Ref: Bad Method Resolution Orders-Footnote-116006044
Node: The end16006228
Ref: howto/mro the-end16006365
Ref: 4e4116006365
Node: Resources16009540
Ref: howto/mro resources16009640
Ref: 4e4216009640
Node: C API Extension Support for Free Threading16009675
Ref: howto/free-threading-extensions doc16009826
Ref: 4e4316009826
Ref: howto/free-threading-extensions c-api-extension-support-for-free-threading16009826
Ref: 4e4416009826
Ref: howto/free-threading-extensions freethreading-extensions-howto16009826
Ref: 4e4516009826
Node: Identifying the Free-Threaded Build in C16010478
Ref: howto/free-threading-extensions identifying-the-free-threaded-build-in-c16010627
Ref: 4e4616010627
Node: Module Initialization16011055
Ref: howto/free-threading-extensions module-initialization16011235
Ref: 4e4716011235
Node: Multi-Phase Initialization16011729
Ref: howto/free-threading-extensions multi-phase-initialization16011849
Ref: 4e4816011849
Node: Single-Phase Initialization16012522
Ref: howto/free-threading-extensions single-phase-initialization16012642
Ref: 4e4916012642
Node: General API Guidelines16013482
Ref: howto/free-threading-extensions general-api-guidelines16013641
Ref: 4e4a16013641
Node: Container Thread Safety16014462
Ref: howto/free-threading-extensions container-thread-safety16014544
Ref: 4e4c16014544
Node: PyDict_Next16014879
Ref: howto/free-threading-extensions id116014950
Ref: 4e4d16014950
Ref: howto/free-threading-extensions pydict-next16014950
Ref: 4e4e16014950
Node: Borrowed References16015438
Ref: howto/free-threading-extensions borrowed-references16015598
Ref: 4e4f16015598
Ref: howto/free-threading-extensions id216015653
Ref: 4e4b16015653
Ref: Borrowed References-Footnote-116018287
Node: Memory Allocation APIs16018339
Ref: howto/free-threading-extensions memory-allocation-apis16018502
Ref: 4e5016018502
Node: Thread State and GIL APIs16019236
Ref: howto/free-threading-extensions thread-state-and-gil-apis16019415
Ref: 4e5116019415
Node: Protecting Internal Extension State16020381
Ref: howto/free-threading-extensions protecting-internal-extension-state16020585
Ref: 4e5216020585
Ref: Protecting Internal Extension State-Footnote-116021341
Node: Building Extensions for the Free-Threaded Build16021407
Ref: howto/free-threading-extensions building-extensions-for-the-free-threaded-build16021577
Ref: 4e5316021577
Ref: Building Extensions for the Free-Threaded Build-Footnote-116022169
Ref: Building Extensions for the Free-Threaded Build-Footnote-216022211
Ref: Building Extensions for the Free-Threaded Build-Footnote-316022256
Node: Limited C API and Stable ABI16022335
Ref: howto/free-threading-extensions limited-c-api-and-stable-abi16022467
Ref: 4e5416022467
Ref: Limited C API and Stable ABI-Footnote-116023166
Node: Windows<73>16023227
Ref: howto/free-threading-extensions windows16023359
Ref: 4e5516023359
Ref: Windows<73>-Footnote-116024829
Node: Python 常見問題16024882
Ref: faq/index doc16024999
Ref: 4e5616024999
Ref: faq/index faq-index16024999
Ref: 1c0a16024999
Ref: faq/index python-frequently-asked-questions16024999
Ref: 4e5716024999
Node: 一般的 Python 常見問答集16025396
Ref: faq/general doc16025520
Ref: 4e5816025520
Ref: faq/general general-python-faq16025520
Ref: 4e5916025520
Node: 一般資訊16025649
Ref: faq/general general-information16025767
Ref: 4e5a16025767
Node: 什麼是 Python？16026699
Ref: faq/general what-is-python16026811
Ref: 4e5b16026811
Ref: 什麼是 Python？-Footnote-116027850
Node: 什麼是 Python 軟體基金會？16027902
Ref: faq/general what-is-the-python-software-foundation16028067
Ref: 4e5c16028067
Ref: 什麼是 Python 軟體基金會？-Footnote-116028646
Node: 使用 Python 時有任何版權限制嗎？16028692
Ref: faq/general are-there-copyright-restrictions-on-the-use-of-python16028882
Ref: 4e5d16028882
Ref: 使用 Python 時有任何版權限制嗎？-Footnote-116029673
Ref: 使用 Python 時有任何版權限制嗎？-Footnote-216029720
Node: 當初為什麼 Python 會被創造出來？16029767
Ref: faq/general why-was-python-created-in-the-first-place16029957
Ref: 4e5e16029957
Node: 什麼是 Python 擅長的事情？16032099
Ref: faq/general what-is-python-good-for16032294
Ref: 4e5f16032294
Ref: 什麼是 Python 擅長的事情？-Footnote-116033160
Node: Python 的版本編號系統是如何運作的？16033185
Ref: faq/general faq-version-numbering-scheme16033383
Ref: 4e6016033383
Ref: faq/general how-does-the-python-version-numbering-scheme-work16033383
Ref: 4e6116033383
Ref: Python 的版本編號系統是如何運作的？-Footnote-116035477
Ref: Python 的版本編號系統是如何運作的？-Footnote-216035551
Node: 我要如何得到 Python 的原始碼複本？16035593
Ref: faq/general how-do-i-obtain-a-copy-of-the-python-source16035800
Ref: 4e6216035800
Ref: 我要如何得到 Python 的原始碼複本？-Footnote-116036556
Node: 我要如何取得 Python 的說明文件？16036599
Ref: faq/general how-do-i-get-documentation-on-python16036816
Ref: 4e6316036816
Ref: 我要如何取得 Python 的說明文件？-Footnote-116037338
Node: 我從來沒有寫過程式，有沒有 Python 的教學？16037370
Ref: faq/general i-ve-never-programmed-before-is-there-a-python-tutorial16037599
Ref: 4e6416037599
Ref: 我從來沒有寫過程式，有沒有 Python 的教學？-Footnote-116037959
Node: 有沒有 Python 專屬的新聞群組或郵件討論群？16038011
Ref: faq/general is-there-a-newsgroup-or-mailing-list-devoted-to-python16038240
Ref: 4e6516038240
Ref: 有沒有 Python 專屬的新聞群組或郵件討論群？-Footnote-116039149
Ref: 有沒有 Python 專屬的新聞群組或郵件討論群？-Footnote-216039210
Node: 如何取得 Python 的 beta 測試版本？16039291
Ref: faq/general how-do-i-get-a-beta-test-version-of-python16039514
Ref: 4e6616039514
Ref: 如何取得 Python 的 beta 測試版本？-Footnote-116040070
Node: 如何提交 Python 的錯誤報告和修補程式？16040107
Ref: faq/general how-do-i-submit-bug-reports-and-patches-for-python16040333
Ref: 4e6716040333
Ref: 如何提交 Python 的錯誤報告和修補程式？-Footnote-116040722
Node: 是否有關於 Python 的任何已出版文章可供參考？16040759
Ref: faq/general are-there-any-published-articles-about-python-that-i-can-reference16040973
Ref: 4e6816040973
Ref: 是否有關於 Python 的任何已出版文章可供參考？-Footnote-116041513
Node: 有沒有關於 Python 的書？16041549
Ref: faq/general are-there-any-books-on-python16041752
Ref: 4e6916041752
Node: www python org 的真實位置在哪裡？16042153
Ref: faq/general where-in-the-world-is-www-python-org-located16042325
Ref: 4e6a16042325
Ref: www python org 的真實位置在哪裡？-Footnote-116042573
Node: 為什麼要取名為 Python？16042602
Ref: faq/general why-is-it-called-python16042800
Ref: 4e6b16042800
Ref: 為什麼要取名為 Python？-Footnote-116043186
Node: 我需要喜歡「Monty Python 的飛行馬戲團」嗎？16043237
Ref: faq/general do-i-have-to-like-monty-python-s-flying-circus16043384
Ref: 4e6c16043384
Node: 在真實世界中的 Python16043542
Ref: faq/general python-in-the-real-world16043660
Ref: 4e6d16043660
Node: Python 的穩定性如何？16044053
Ref: faq/general how-stable-is-python16044186
Ref: 4e6e16044186
Ref: Python 的穩定性如何？-Footnote-116045261
Ref: Python 的穩定性如何？-Footnote-216045303
Ref: Python 的穩定性如何？-Footnote-316045345
Node: 有多少人在使用 Python？16045387
Ref: faq/general how-many-people-are-using-python16045588
Ref: 4e6f16045588
Node: 有沒有任何重要的專案使用 Python 完成開發？16046089
Ref: faq/general have-any-significant-projects-been-done-in-python16046308
Ref: 4e7016046308
Ref: 有沒有任何重要的專案使用 Python 完成開發？-Footnote-116046986
Ref: 有沒有任何重要的專案使用 Python 完成開發？-Footnote-216047038
Ref: 有沒有任何重要的專案使用 Python 完成開發？-Footnote-316047067
Ref: 有沒有任何重要的專案使用 Python 完成開發？-Footnote-416047096
Node: Python 未來預期會有哪些新的開發？16047127
Ref: faq/general what-new-developments-are-expected-for-python-in-the-future16047371
Ref: 4e7116047371
Ref: Python 未來預期會有哪些新的開發？-Footnote-116047932
Node: 對 Python 提出不相容的變更建議是否適當？16048002
Ref: faq/general is-it-reasonable-to-propose-incompatible-changes-to-python16048254
Ref: 4e7216048254
Ref: 對 Python 提出不相容的變更建議是否適當？-Footnote-116049027
Node: Python 對於入門的程式設計師而言是否為好的語言？16049069
Ref: faq/general is-python-a-good-language-for-beginning-programmers16049266
Ref: 4e7316049266
Ref: Python 對於入門的程式設計師而言是否為好的語言？-Footnote-116053063
Ref: Python 對於入門的程式設計師而言是否為好的語言？-Footnote-216053114
Node: 程式開發常見問答集16053176
Ref: faq/programming doc16053339
Ref: 4e7416053339
Ref: faq/programming programming-faq16053339
Ref: 4e7516053339
Node: 常見問題16053576
Ref: faq/programming general-questions16053673
Ref: 4e7616053673
Node: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？16054095
Ref: faq/programming is-there-a-source-code-level-debugger-with-breakpoints-single-stepping-etc16054304
Ref: 4e7716054304
Ref: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？-Footnote-116055678
Ref: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？-Footnote-216055750
Ref: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？-Footnote-316055794
Ref: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？-Footnote-416055847
Ref: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？-Footnote-516055893
Ref: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？-Footnote-616055942
Ref: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？-Footnote-716055981
Ref: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？-Footnote-816056011
Ref: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？-Footnote-916056068
Node: 有沒有工具能夠幫忙找 bug 或執行靜態分析？16056111
Ref: faq/programming are-there-tools-to-help-find-bugs-or-perform-static-analysis16056385
Ref: 4e7816056385
Ref: 有沒有工具能夠幫忙找 bug 或執行靜態分析？-Footnote-116056748
Ref: 有沒有工具能夠幫忙找 bug 或執行靜態分析？-Footnote-216056802
Ref: 有沒有工具能夠幫忙找 bug 或執行靜態分析？-Footnote-316056844
Ref: 有沒有工具能夠幫忙找 bug 或執行靜態分析？-Footnote-416056875
Ref: 有沒有工具能夠幫忙找 bug 或執行靜態分析？-Footnote-516056907
Node: 如何從 Python 腳本建立獨立的二進位檔案？16056948
Ref: faq/programming faq-create-standalone-binary16057185
Ref: 4e7916057185
Ref: faq/programming how-can-i-create-a-stand-alone-binary-from-a-python-script16057185
Ref: 4e7a16057185
Ref: 如何從 Python 腳本建立獨立的二進位檔案？-Footnote-116058863
Ref: 如何從 Python 腳本建立獨立的二進位檔案？-Footnote-216058928
Ref: 如何從 Python 腳本建立獨立的二進位檔案？-Footnote-316058956
Ref: 如何從 Python 腳本建立獨立的二進位檔案？-Footnote-416058989
Ref: 如何從 Python 腳本建立獨立的二進位檔案？-Footnote-516059042
Ref: 如何從 Python 腳本建立獨立的二進位檔案？-Footnote-616059094
Ref: 如何從 Python 腳本建立獨立的二進位檔案？-Footnote-716059143
Node: Python 程式碼是否有編碼標準或風格指南？16059175
Ref: faq/programming are-there-coding-standards-or-a-style-guide-for-python-programs16059344
Ref: 4e7b16059344
Ref: Python 程式碼是否有編碼標準或風格指南？-Footnote-116059566
Node: 核心語言16059608
Ref: faq/programming core-language16059729
Ref: 4e7c16059729
Node: 為什麼當變數有值時，我仍得到錯誤訊息 UnboundLocalError？16061095
Ref: faq/programming faq-unboundlocalerror16061283
Ref: 1eb216061283
Ref: faq/programming why-am-i-getting-an-unboundlocalerror-when-the-variable-has-a-value16061283
Ref: 4e7d16061283
Node: Python 的區域變數和全域變數有什麼規則？16063208
Ref: faq/programming what-are-the-rules-for-local-and-global-variables-in-python16063487
Ref: 4e7e16063487
Node: Why do lambdas defined in a loop with different values all return the same result?16064351
Ref: faq/programming why-do-lambdas-defined-in-a-loop-with-different-values-all-return-the-same-result16064591
Ref: 4e7f16064591
Node: 如何跨模組共享全域變數？16066485
Ref: faq/programming how-do-i-share-global-variables-across-modules16066729
Ref: 4e8016066729
Node: What are the "best practices" for using import in a module?16067504
Ref: faq/programming what-are-the-best-practices-for-using-import-in-a-module16067712
Ref: 4e8116067712
Node: Why are default values shared between objects?16070490
Ref: faq/programming why-are-default-values-shared-between-objects16070737
Ref: 4e8216070737
Node: How can I pass optional or keyword parameters from one function to another?16073120
Ref: faq/programming how-can-i-pass-optional-or-keyword-parameters-from-one-function-to-another16073364
Ref: 4e8316073364
Node: 引數 arguments 和參數 parameters 有什麼區別？16073949
Ref: faq/programming faq-argument-vs-parameter16074196
Ref: 4e8416074196
Ref: faq/programming what-is-the-difference-between-arguments-and-parameters16074196
Ref: 4e8516074196
Node: 為什麼更改 list 'y' 也會更改 list 'x'？16074880
Ref: faq/programming why-did-changing-list-y-also-change-list-x16075120
Ref: 4e8616075120
Node: How do I write a function with output parameters call by reference ?16078519
Ref: faq/programming how-do-i-write-a-function-with-output-parameters-call-by-reference16078753
Ref: 4e8716078753
Node: How do you make a higher order function in Python?16081146
Ref: faq/programming how-do-you-make-a-higher-order-function-in-python16081366
Ref: 4e8816081366
Node: 如何在 Python 中複製物件？16082932
Ref: faq/programming how-do-i-copy-an-object-in-python16083123
Ref: 4e8916083123
Node: 如何找到物件的方法或屬性？16083532
Ref: faq/programming how-can-i-find-the-methods-or-attributes-of-an-object16083718
Ref: 4e8a16083718
Node: 我的程式碼如何發現物件的名稱？16084001
Ref: faq/programming how-can-my-code-discover-the-name-of-an-object16084199
Ref: 4e8b16084199
Node: What's up with the comma operator's precedence?16085765
Ref: faq/programming what-s-up-with-the-comma-operator-s-precedence16085972
Ref: 4e8c16085972
Node: 是否有等效於 C 的 "? " 三元運算子？16086534
Ref: faq/programming is-there-an-equivalent-of-c-s-ternary-operator16086752
Ref: 4e8d16086752
Node: Is it possible to write obfuscated one-liners in Python?16087303
Ref: faq/programming is-it-possible-to-write-obfuscated-one-liners-in-python16087537
Ref: 4e8e16087537
Node: What does the slash / in the parameter list of a function mean?16089048
Ref: faq/programming faq-positional-only-arguments16089225
Ref: 204e16089225
Ref: faq/programming what-does-the-slash-in-the-parameter-list-of-a-function-mean16089225
Ref: 4e8f16089225
Node: 數字和字串16090325
Ref: faq/programming numbers-and-strings16090448
Ref: 4e9016090448
Node: 如何指定十六進位和八進位整數？16091213
Ref: faq/programming how-do-i-specify-hexadecimal-and-octal-integers16091351
Ref: 4e9116091351
Node: 為什麼 -22 // 10 回傳 -3？16091963
Ref: faq/programming why-does-22-10-return-316092168
Ref: 4e9216092168
Node: How do I get int literal attribute instead of SyntaxError?16092926
Ref: faq/programming how-do-i-get-int-literal-attribute-instead-of-syntaxerror16093119
Ref: 4e9316093119
Node: 如何將字串轉換為數字？16093705
Ref: faq/programming how-do-i-convert-a-string-to-a-number16093899
Ref: 4e9416093899
Node: 如何將數字轉換為字串？16095193
Ref: faq/programming how-do-i-convert-a-number-to-a-string16095363
Ref: 4e9516095363
Node: How do I modify a string in place?16095902
Ref: faq/programming how-do-i-modify-a-string-in-place16096086
Ref: 4e9616096086
Node: How do I use strings to call functions/methods?16096940
Ref: faq/programming how-do-i-use-strings-to-call-functions-methods16097174
Ref: 4e9716097174
Node: Is there an equivalent to Perl's chomp for removing trailing newlines from strings?16098492
Ref: faq/programming is-there-an-equivalent-to-perl-s-chomp-for-removing-trailing-newlines-from-strings16098730
Ref: 4e9816098730
Node: Is there a scanf or sscanf equivalent?16099487
Ref: faq/programming is-there-a-scanf-or-sscanf-equivalent16099747
Ref: 4e9916099747
Node: 'UnicodeDecodeError' 或 'UnicodeEncodeErro' 錯誤是什麼意思？16100390
Ref: faq/programming what-does-unicodedecodeerror-or-unicodeencodeerror-error-mean16100624
Ref: 4e9a16100624
Node: Can I end a raw string with an odd number of backslashes?16100817
Ref: faq/programming can-i-end-a-raw-string-with-an-odd-number-of-backslashes16101004
Ref: 4e9b16101004
Ref: faq/programming faq-programming-raw-string-backslash16101004
Ref: 1b0116101004
Node: Performance<4>16102285
Ref: faq/programming performance16102418
Ref: 4e9c16102418
Node: 我的程式太慢了。我該如何加快速度？16102596
Ref: faq/programming my-program-is-too-slow-how-do-i-speed-it-up16102775
Ref: 4e9d16102775
Ref: 我的程式太慢了。我該如何加快速度？-Footnote-116105653
Ref: 我的程式太慢了。我該如何加快速度？-Footnote-216105680
Node: What is the most efficient way to concatenate many strings together?16105745
Ref: faq/programming efficient-string-concatenation16105924
Ref: 4e9e16105924
Ref: faq/programming what-is-the-most-efficient-way-to-concatenate-many-strings-together16105924
Ref: 4e9f16105924
Node: Sequences Tuples/Lists16106894
Ref: faq/programming sequences-tuples-lists16107018
Ref: 4ea016107018
Node: How do I convert between tuples and lists?16107768
Ref: faq/programming how-do-i-convert-between-tuples-and-lists16107902
Ref: 4ea116107902
Node: What's a negative index?16108747
Ref: faq/programming what-s-a-negative-index16108940
Ref: 4ea216108940
Node: How do I iterate over a sequence in reverse order?16109518
Ref: faq/programming how-do-i-iterate-over-a-sequence-in-reverse-order16109710
Ref: 4ea316109710
Node: How do you remove duplicates from a list?16110057
Ref: faq/programming how-do-you-remove-duplicates-from-a-list16110269
Ref: 4ea416110269
Node: How do you remove multiple items from a list16111094
Ref: faq/programming how-do-you-remove-multiple-items-from-a-list16111291
Ref: 4ea516111291
Node: How do you make an array in Python?16111839
Ref: faq/programming how-do-you-make-an-array-in-python16112035
Ref: 4ea616112035
Ref: How do you make an array in Python?-Footnote-116113065
Node: How do I create a multidimensional list?16113092
Ref: faq/programming faq-multidimensional-list16113305
Ref: 208716113305
Ref: faq/programming how-do-i-create-a-multidimensional-list16113305
Ref: 4ea716113305
Ref: How do I create a multidimensional list?-Footnote-116114538
Node: How do I apply a method or function to a sequence of objects?16114565
Ref: faq/programming how-do-i-apply-a-method-or-function-to-a-sequence-of-objects16114818
Ref: 4ea816114818
Node: Why does a_tuple[i] += ['item'] raise an exception when the addition works?16115397
Ref: faq/programming faq-augmented-assignment-tuple-error16115687
Ref: 1e8a16115687
Ref: faq/programming why-does-a-tuple-i-item-raise-an-exception-when-the-addition-works16115687
Ref: 4ea916115687
Node: I want to do a complicated sort can you do a Schwartzian Transform in Python?16118906
Ref: faq/programming i-want-to-do-a-complicated-sort-can-you-do-a-schwartzian-transform-in-python16119187
Ref: 4eaa16119187
Node: How can I sort one list by values from another list?16119668
Ref: faq/programming how-can-i-sort-one-list-by-values-from-another-list16119865
Ref: 4eab16119865
Node: 物件16120460
Ref: faq/programming objects16120579
Ref: 4eac16120579
Node: 什麼是類別 class ？16121818
Ref: faq/programming what-is-a-class16121921
Ref: 4ead16121921
Node: 什麼是方法 method ？16122661
Ref: faq/programming what-is-a-method16122786
Ref: 4eae16122786
Node: What is self?16123109
Ref: faq/programming what-is-self16123292
Ref: 4eaf16123292
Node: How do I check if an object is an instance of a given class or of a subclass of it?16123747
Ref: faq/programming how-do-i-check-if-an-object-is-an-instance-of-a-given-class-or-of-a-subclass-of-it16123923
Ref: 4eb116123923
Node: What is delegation?16126216
Ref: faq/programming what-is-delegation16126463
Ref: 4eb216126463
Node: How do I call a method defined in a base class from a derived class that extends it?16128312
Ref: faq/programming how-do-i-call-a-method-defined-in-a-base-class-from-a-derived-class-that-extends-it16128546
Ref: 4eb316128546
Node: How can I organize my code to make it easier to change the base class?16129167
Ref: faq/programming how-can-i-organize-my-code-to-make-it-easier-to-change-the-base-class16129441
Ref: 4eb416129441
Node: How do I create static class data and static class methods?16129991
Ref: faq/programming how-do-i-create-static-class-data-and-static-class-methods16130234
Ref: 4eb516130234
Node: How can I overload constructors or methods in Python?16131799
Ref: faq/programming how-can-i-overload-constructors-or-methods-in-python16132037
Ref: 4eb616132037
Node: I try to use __spam and I get an error about _SomeClassName__spam16132947
Ref: faq/programming i-try-to-use-spam-and-i-get-an-error-about-someclassname-spam16133196
Ref: 4eb716133196
Node: My class defines __del__ but it is not called when I delete the object16134396
Ref: faq/programming my-class-defines-del-but-it-is-not-called-when-i-delete-the-object16134646
Ref: 4eb816134646
Node: How do I get a list of all instances of a given class?16136580
Ref: faq/programming how-do-i-get-a-list-of-all-instances-of-a-given-class16136815
Ref: 4eb916136815
Node: Why does the result of id appear to be not unique?16137154
Ref: faq/programming why-does-the-result-of-id-appear-to-be-not-unique16137383
Ref: 4eba16137383
Node: 我什麼時候可以依靠 is 運算子進行識別性測試？16138274
Ref: faq/programming when-can-i-rely-on-identity-tests-with-the-is-operator16138506
Ref: 4ebb16138506
Ref: 我什麼時候可以依靠 is 運算子進行識別性測試？-Footnote-116141579
Node: 子類別如何控制不可變實例中存儲的資料？16141621
Ref: faq/programming how-can-a-subclass-control-what-data-is-stored-in-an-immutable-instance16141830
Ref: 4ebc16141830
Node: 如何快取方法呼叫？16143259
Ref: faq/programming faq-cache-method-calls16143395
Ref: 261416143395
Ref: faq/programming how-do-i-cache-method-calls16143395
Ref: 4ebd16143395
Node: 模組<5>16146334
Ref: faq/programming modules16146422
Ref: 4ebe16146422
Node: 如何建立 pyc 檔案？16146861
Ref: faq/programming how-do-i-create-a-pyc-file16146975
Ref: 4ebf16146975
Ref: 如何建立 pyc 檔案？-Footnote-116149541
Node: 如何找到當前模組名稱？16149583
Ref: faq/programming how-do-i-find-the-current-module-name16149761
Ref: 4ec016149761
Node: How can I have modules that mutually import each other?16150298
Ref: faq/programming how-can-i-have-modules-that-mutually-import-each-other16150514
Ref: 4ec116150514
Node: __import__ 'x y z' 回傳 <module 'x'>，那我怎麼得到 z？16152468
Ref: faq/programming import-x-y-z-returns-module-x-how-do-i-get-z16152756
Ref: 4ec216152756
Node: 當我編輯需要引入的模組並重新引入它時，更動沒有反應出來。為什麼會這樣？16153044
Ref: faq/programming when-i-edit-an-imported-module-and-reimport-it-the-changes-don-t-show-up-why-does-this-happen16153268
Ref: 4ec316153268
Node: 設計和歷史常見問答集16154675
Ref: faq/design doc16154845
Ref: 4ec416154845
Ref: faq/design design-and-history-faq16154845
Ref: 4ec516154845
Node: 為什麼 Python 使用縮排將陳述式進行分組？16157449
Ref: faq/design why-does-python-use-indentation-for-grouping-of-statements16157644
Ref: 4ec616157644
Node: 為什麼我會從簡單的數學運算得到奇怪的結果？16159194
Ref: faq/design why-am-i-getting-strange-results-with-simple-arithmetic-operations16159437
Ref: 4ec716159437
Node: 為何浮點數運算如此不精確？16159585
Ref: faq/design why-are-floating-point-calculations-so-inaccurate16159810
Ref: 4ec816159810
Node: 為什麼 Python 字串不可變動？16161173
Ref: faq/design why-are-python-strings-immutable16161410
Ref: 4ec916161410
Node: 為何「self」在方法 method 定義和呼叫時一定要明確使用？16161955
Ref: faq/design why-must-self-be-used-explicitly-in-method-definitions-and-calls16162216
Ref: 4eca16162216
Ref: faq/design why-self16162216
Ref: 4eb016162216
Node: 為何我不能在運算式 expression 中使用指派運算？16164359
Ref: faq/design id216164705
Ref: 4ecb16164705
Ref: faq/design why-can-t-i-use-an-assignment-in-an-expression16164705
Ref: 1b5516164705
Ref: 為何我不能在運算式 expression 中使用指派運算？-Footnote-116165095
Node: 為何 Python 對於一些功能實作使用方法（像是 list index ），另一些使用函式（像是 len list ）？16165137
Ref: faq/design why-does-python-use-methods-for-some-functionality-e-g-list-index-but-functions-for-other-e-g-len-list16165478
Ref: 4ecc16165478
Node: 為何 join 是字串方法而非串列 list 或元組 tuple 方法？16166700
Ref: faq/design why-is-join-a-string-method-instead-of-a-list-or-tuple-method16167002
Ref: 4ecd16167002
Node: 例外處理有多快？16168572
Ref: faq/design how-fast-are-exceptions16168806
Ref: 4ece16168806
Node: 為什麼 Python 內沒有 switch 或 case 陳述式？16169631
Ref: faq/design why-isn-t-there-a-switch-or-case-statement-in-python16169888
Ref: 4ecf16169888
Node: 為何不能在直譯器上模擬執行緒，而要使用作業系統的特定實作方式？16171221
Ref: faq/design can-t-you-emulate-threads-in-the-interpreter-instead-of-relying-on-an-os-specific-thread-implementation16171501
Ref: 4ed016171501
Ref: 為何不能在直譯器上模擬執行緒，而要使用作業系統的特定實作方式？-Footnote-116172056
Node: 為何 lambda 運算式不能包含陳述式？16172112
Ref: faq/design why-can-t-lambda-expressions-contain-statements16172409
Ref: 4ed116172409
Node: Python 可以被編譯成機器語言、C 語言或其他種語言嗎？16173160
Ref: faq/design can-python-be-compiled-to-machine-code-c-or-some-other-language16173395
Ref: 4ed216173395
Ref: Python 可以被編譯成機器語言、C 語言或其他種語言嗎？-Footnote-116173773
Ref: Python 可以被編譯成機器語言、C 語言或其他種語言嗎？-Footnote-216173801
Node: Python 如何管理記憶體？16173833
Ref: faq/design how-does-python-manage-memory16174081
Ref: 4ed316174081
Ref: Python 如何管理記憶體？-Footnote-116175733
Ref: Python 如何管理記憶體？-Footnote-216175764
Node: 為何 CPython 不使用更多傳統的垃圾回收機制？16175793
Ref: faq/design why-doesn-t-cpython-use-a-more-traditional-garbage-collection-scheme16176035
Ref: 4ed416176035
Node: 當 CPython 結束時，為何所有的記憶體不會被釋放？16176897
Ref: faq/design why-isn-t-all-memory-freed-when-cpython-exits16177175
Ref: 4ed516177175
Node: 為何要把元組 tuple 和串列 list 分成兩個資料型態？16177824
Ref: faq/design why-are-there-separate-tuple-and-list-data-types16178090
Ref: 4ed616178090
Node: 串列 list 在 CPython 中是怎麼實作的？16179200
Ref: faq/design how-are-lists-implemented-in-cpython16179456
Ref: 4ed716179456
Node: 字典 dictionaries 在 CPython 中是怎麼實作的？16180215
Ref: faq/design how-are-dictionaries-implemented-in-cpython16180446
Ref: 4ed816180446
Node: 為何字典的鍵一定是不可變的？16181296
Ref: faq/design why-must-dictionary-keys-be-immutable16181529
Ref: 4ed916181529
Node: 為何 list sort 不是回傳排序過的串列？16185320
Ref: faq/design why-doesn-t-list-sort-return-the-sorted-list16185575
Ref: 4eda16185575
Node: 如何在 Python 中指定和強制使用一個介面規範 interface spec ？16186329
Ref: faq/design how-do-you-specify-and-enforce-an-interface-spec-in-python16186569
Ref: 4edb16186569
Node: 為何沒有 goto 語法？16188792
Ref: faq/design why-is-there-no-goto16189034
Ref: 4edc16189034
Node: 為何純字串 r-string 不能以反斜線結尾？16190128
Ref: faq/design why-can-t-raw-strings-r-strings-end-with-a-backslash16190345
Ref: 4edd16190345
Node: 為何 Python 沒有屬性賦值的 with 陳述式？16191331
Ref: faq/design why-doesn-t-python-have-a-with-statement-for-attribute-assignments16191574
Ref: 4ede16191574
Node: 為何產生器 generator 不支援 with 陳述式？16193907
Ref: faq/design why-don-t-generators-support-the-with-statement16194157
Ref: 4edf16194157
Node: 為何 if、while、def、class 陳述式裡需要冒號？16194614
Ref: faq/design why-are-colons-required-for-the-if-while-def-class-statements16194870
Ref: 4ee016194870
Node: 為何 Python 允許在串列和元組末端加上逗號？16195547
Ref: faq/design why-does-python-allow-commas-at-the-end-of-lists-and-tuples16195741
Ref: 4ee116195741
Node: 函式庫和擴充功能的常見問題16196704
Ref: faq/library doc16196875
Ref: 4ee216196875
Ref: faq/library library-and-extension-faq16196875
Ref: 4ee316196875
Node: 常見函式問題16197168
Ref: faq/library general-library-questions16197283
Ref: 4ee416197283
Node: 我如何找到執行任務 X 的模組或應用程式？16197822
Ref: faq/library how-do-i-find-a-module-or-application-to-perform-task-x16198008
Ref: 4ee516198008
Ref: 我如何找到執行任務 X 的模組或應用程式？-Footnote-116198569
Ref: 我如何找到執行任務 X 的模組或應用程式？-Footnote-216198594
Node: 哪裡可以找到 math py socket py regex py 等 來源檔案？16198625
Ref: faq/library where-is-the-math-py-socket-py-regex-py-etc-source-file16198864
Ref: 4ee616198864
Node: 我如何使 Python script 執行在 Unix？16199630
Ref: faq/library how-do-i-make-a-python-script-executable-on-unix16199866
Ref: 4ee716199866
Node: 是否有適用於 Python 的 curses/termcap 套件？16201313
Ref: faq/library is-there-a-curses-termcap-package-for-python16201538
Ref: 4ee816201538
Ref: 是否有適用於 Python 的 curses/termcap 套件？-Footnote-116202333
Node: Python 中是否有等同於 C 的 onexit 的函式？16202393
Ref: faq/library is-there-an-equivalent-to-c-s-onexit-in-python16202622
Ref: 4ee916202622
Node: 為什麼我的信號處理程式不起作用？16202840
Ref: faq/library why-don-t-my-signal-handlers-work16203006
Ref: 4eea16203006
Node: 常見課題16203335
Ref: faq/library common-tasks16203468
Ref: 4eeb16203468
Node: 如何測試 Python 程式或元件？16203656
Ref: faq/library how-do-i-test-a-python-program-or-component16203799
Ref: 4eec16203799
Node: How do I create documentation from doc strings?16205707
Ref: faq/library how-do-i-create-documentation-from-doc-strings16205900
Ref: 4eed16205900
Ref: How do I create documentation from doc strings?-Footnote-116206276
Ref: How do I create documentation from doc strings?-Footnote-216206316
Node: How do I get a single keypress at a time?16206351
Ref: faq/library how-do-i-get-a-single-keypress-at-a-time16206497
Ref: 4eee16206497
Node: 執行緒16206741
Ref: faq/library threads16206871
Ref: 4eef16206871
Node: 如何使用執行緒編寫程式？16207170
Ref: faq/library how-do-i-program-using-threads16207312
Ref: 4ef016207312
Node: 我的執行緒似乎都沒有運行：為什麼？16207620
Ref: faq/library none-of-my-threads-seem-to-run-why16207828
Ref: 4ef116207828
Node: How do I parcel out work among a bunch of worker threads?16209382
Ref: faq/library how-do-i-parcel-out-work-among-a-bunch-of-worker-threads16209606
Ref: 4ef216209606
Node: What kinds of global value mutation are thread-safe?16212202
Ref: faq/library what-kinds-of-global-value-mutation-are-thread-safe16212411
Ref: 4ef316212411
Node: 不能擺脫全局直譯器鎖嗎？16213912
Ref: faq/library can-t-we-get-rid-of-the-global-interpreter-lock16214055
Ref: 4ef416214055
Ref: 不能擺脫全局直譯器鎖嗎？-Footnote-116217022
Ref: 不能擺脫全局直譯器鎖嗎？-Footnote-216217064
Ref: 不能擺脫全局直譯器鎖嗎？-Footnote-316217107
Node: 輸入與輸出16217167
Ref: faq/library input-and-output16217329
Ref: 4ef516217329
Node: 如何刪除檔案？（以及其他檔案問題 ）16217938
Ref: faq/library how-do-i-delete-a-file-and-other-file-questions16218072
Ref: 4ef616218072
Node: 如何複製檔案？16219318
Ref: faq/library how-do-i-copy-a-file16219509
Ref: 4ef716219509
Ref: 如何複製檔案？-Footnote-116219975
Ref: 如何複製檔案？-Footnote-216220046
Node: 如何讀取（或寫入）二進位制資料？16220098
Ref: faq/library how-do-i-read-or-write-binary-data16220303
Ref: 4ef816220303
Node: I can't seem to use os read on a pipe created with os popen ; why?16221486
Ref: faq/library i-can-t-seem-to-use-os-read-on-a-pipe-created-with-os-popen-why16221707
Ref: 4ef916221707
Node: 如何存取序列 RS232 連接埠？16222226
Ref: faq/library how-do-i-access-the-serial-rs232-port16222466
Ref: 4efa16222466
Ref: 如何存取序列 RS232 連接埠？-Footnote-116222802
Node: 為什麼關閉 sys stdout stdin stderr 並沒有真正關閉它？16222845
Ref: faq/library why-doesn-t-closing-sys-stdout-stdin-stderr-really-close-it16223010
Ref: 4efb16223010
Node: 網路 Network /網際網路 Internet 程式16224199
Ref: faq/library network-internet-programming16224361
Ref: 4efc16224361
Node: Python 有哪些 WWW 工具？16224731
Ref: faq/library what-www-tools-are-there-for-python16224901
Ref: 4efd16224901
Node: 我應該使用什麼模組來輔助產生 HTML？16225341
Ref: faq/library what-module-should-i-use-to-help-with-generating-html16225558
Ref: 4efe16225558
Ref: 我應該使用什麼模組來輔助產生 HTML？-Footnote-116225780
Node: 如何從 Python 腳本發送郵件？16225832
Ref: faq/library how-do-i-send-mail-from-a-python-script16226077
Ref: 4eff16226077
Node: How do I avoid blocking in the connect method of a socket?16227399
Ref: faq/library how-do-i-avoid-blocking-in-the-connect-method-of-a-socket16227585
Ref: 4f0016227585
Ref: How do I avoid blocking in the connect method of a socket?-Footnote-116228863
Node: 資料庫16228892
Ref: faq/library databases16229054
Ref: 4f0116229054
Node: Python 中是否有任何資料庫套件的介面？16229208
Ref: faq/library are-there-any-interfaces-to-database-packages-in-python16229365
Ref: 4f0216229365
Ref: Python 中是否有任何資料庫套件的介面？-Footnote-116229853
Node: How do you implement persistent objects in Python?16229910
Ref: faq/library how-do-you-implement-persistent-objects-in-python16230067
Ref: 4f0316230067
Node: 數學和數值16230466
Ref: faq/library mathematics-and-numerics16230575
Ref: 4f0416230575
Node: 如何在 Python 中生成隨機數？16230670
Ref: faq/library how-do-i-generate-random-numbers-in-python16230760
Ref: 4f0516230760
Node: 擴充/嵌入常見問題集16231642
Ref: faq/extending doc16231827
Ref: 4f0616231827
Ref: faq/extending extending-embedding-faq16231827
Ref: 4f0716231827
Node: 我可以在 C 中建立自己的函式嗎？16233241
Ref: faq/extending can-i-create-my-own-functions-in-c16233407
Ref: 4f0816233407
Node: 我可以在 C++ 中建立自己的函式嗎？16233738
Ref: faq/extending id216233952
Ref: 4f0916233952
Node: 寫 C 很難；還有其他選擇嗎？16234345
Ref: faq/extending c-wrapper-software16234558
Ref: 4f0a16234558
Ref: faq/extending writing-c-is-hard-are-there-any-alternatives16234558
Ref: 4f0b16234558
Ref: 寫 C 很難；還有其他選擇嗎？-Footnote-116235287
Ref: 寫 C 很難；還有其他選擇嗎？-Footnote-216235314
Ref: 寫 C 很難；還有其他選擇嗎？-Footnote-316235381
Ref: 寫 C 很難；還有其他選擇嗎？-Footnote-416235410
Ref: 寫 C 很難；還有其他選擇嗎？-Footnote-516235452
Ref: 寫 C 很難；還有其他選擇嗎？-Footnote-616235489
Ref: 寫 C 很難；還有其他選擇嗎？-Footnote-716235546
Node: 如何從 C 執行任意 Python 陳述式？16235585
Ref: faq/extending how-can-i-execute-arbitrary-python-statements-from-c16235808
Ref: 4f0c16235808
Node: How can I evaluate an arbitrary Python expression from C?16236325
Ref: faq/extending how-can-i-evaluate-an-arbitrary-python-expression-from-c16236550
Ref: 4f0d16236550
Node: 如何從 Python 物件中提取 C 值？16236866
Ref: faq/extending how-do-i-extract-c-values-from-a-python-object16237104
Ref: 4f0e16237104
Node: 如何使用 Py_BuildValue 建立任意長度的元組？16238323
Ref: faq/extending how-do-i-use-py-buildvalue-to-create-a-tuple-of-arbitrary-length16238540
Ref: 4f0f16238540
Node: 如何從 C 呼叫物件的方法？16238721
Ref: faq/extending how-do-i-call-an-object-s-method-from-c16238985
Ref: 4f1016238985
Node: 我如何捕捉 PyErr_Print 的輸出（或任何印出到 stdout/stderr 的東西）？16240163
Ref: faq/extending how-do-i-catch-the-output-from-pyerr-print-or-anything-that-prints-to-stdout-stderr16240417
Ref: 4f1116240417
Node: 如何從 C 存取用 Python 編寫的模組？16241604
Ref: faq/extending how-do-i-access-a-module-written-in-python-from-c16241868
Ref: 4f1216241868
Node: How do I interface to C++ objects from Python?16242676
Ref: faq/extending how-do-i-interface-to-c-objects-from-python16242930
Ref: 4f1316242930
Node: 我使用安裝檔案新增了一個模組，但 make 失敗了；為什麼？16243500
Ref: faq/extending i-added-a-module-using-the-setup-file-and-the-make-fails-why16243737
Ref: 4f1416243737
Node: 如何為擴充套件除錯？16244093
Ref: faq/extending how-do-i-debug-an-extension16244383
Ref: 4f1516244383
Node: 我想在我的 Linux 系統上編譯一個 Python 模組，但是缺少一些檔案。為什麼？16244935
Ref: faq/extending i-want-to-compile-a-python-module-on-my-linux-system-but-some-files-are-missing-why16245207
Ref: 4f1616245207
Node: 如何從「無效輸入」區分出「不完整輸入」？16245699
Ref: faq/extending how-do-i-tell-incomplete-input-from-invalid-input16246012
Ref: 4f1716246012
Node: 如何找到未定義的 g++ 符號 __builtin_new 或 __pure_virtual？16246958
Ref: faq/extending how-do-i-find-undefined-g-symbols-builtin-new-or-pure-virtual16247282
Ref: 4f1816247282
Node: Can I create an object class with some methods implemented in C and others in Python e g through inheritance ?16247664
Ref: faq/extending can-i-create-an-object-class-with-some-methods-implemented-in-c-and-others-in-python-e-g-through-inheritance16247919
Ref: 4f1916247919
Node: 在 Windows 使用 Python 的常見問答集16248479
Ref: faq/windows doc16248661
Ref: 4f1a16248661
Ref: faq/windows python-on-windows-faq16248661
Ref: 4f1b16248661
Ref: faq/windows windows-faq16248661
Ref: 4f1c16248661
Node: 如何在 Windows 作業系統裡運行 Python 程式？16249365
Ref: faq/windows faq-run-program-under-windows16249549
Ref: 4f1d16249549
Ref: faq/windows how-do-i-run-a-python-program-under-windows16249549
Ref: 4f1e16249549
Node: 如何使 Python 腳本可以執行？16252954
Ref: faq/windows how-do-i-make-python-scripts-executable16253209
Ref: 4f1f16253209
Node: 為什麼 Python 有時需要這麼長的時間才能開始？16253753
Ref: faq/windows why-does-python-sometimes-take-so-long-to-start16253996
Ref: 4f2016253996
Node: 如何從 Python 腳本製作可執行檔？16254859
Ref: faq/windows how-do-i-make-an-executable-from-a-python-script16255096
Ref: 4f2116255096
Node: * pyd 檔是否與 DLL 相同？16255330
Ref: faq/windows is-a-pyd-file-the-same-as-a-dll16255555
Ref: 4f2216255555
Node: 如何將 Python 嵌入 Windows 應用程式中？16256567
Ref: faq/windows how-can-i-embed-python-into-a-windows-application16256811
Ref: 4f2316256811
Node: 如何防止編輯器在我的 Python 原始碼中插入 tab？16261305
Ref: faq/windows how-do-i-keep-editors-from-inserting-tabs-into-my-python-source16261565
Ref: 4f2416261565
Ref: 如何防止編輯器在我的 Python 原始碼中插入 tab？-Footnote-116262434
Node: 如何在不阻塞的情況下檢查 keypress？16262476
Ref: faq/windows how-do-i-check-for-a-keypress-without-blocking16262751
Ref: 4f2516262751
Node: 如何解決遺漏 api-ms-win-crt-runtime-l1-1-0 dll 的錯誤？16263124
Ref: faq/windows how-do-i-solve-the-missing-api-ms-win-crt-runtime-l1-1-0-dll-error16263327
Ref: 4f2616263327
Ref: 如何解決遺漏 api-ms-win-crt-runtime-l1-1-0 dll 的錯誤？-Footnote-116263826
Node: 圖形使用者介面常見問答集16263884
Ref: faq/gui doc16264106
Ref: 4f2716264106
Ref: faq/gui graphic-user-interface-faq16264106
Ref: 4f2816264106
Node: 圖形使用者介面 GUI 的常見問題16264336
Ref: faq/gui general-gui-questions16264489
Ref: 4f2916264489
Node: Python 有哪些 GUI 套件？16264580
Ref: faq/gui what-gui-toolkits-exist-for-python16264759
Ref: 4f2a16264759
Ref: Python 有哪些 GUI 套件？-Footnote-116265443
Ref: Python 有哪些 GUI 套件？-Footnote-216265485
Ref: Python 有哪些 GUI 套件？-Footnote-316265512
Ref: Python 有哪些 GUI 套件？-Footnote-416265591
Node: Tkinter 的問答16265673
Ref: faq/gui tkinter-questions16265802
Ref: 4f2b16265802
Node: 如何凍結 Tkinter 應用程式？16266102
Ref: faq/gui how-do-i-freeze-tkinter-applications16266249
Ref: 4f2c16266249
Node: 是否可以在等待 I/O 時處理 Tk 事件？16266837
Ref: faq/gui can-i-have-tk-events-handled-while-waiting-for-i-o16267063
Ref: 4f2d16267063
Node: 我無法讓鍵繫結 key binding 在 Tkinter 中作用：為什麼？16267563
Ref: faq/gui i-can-t-get-key-bindings-to-work-in-tkinter-why16267744
Ref: 4f2e16267744
Node: 「為什麼 Python 被安裝在我的機器上？」常見問答集16268370
Ref: faq/installed doc16268539
Ref: 4f2f16268539
Ref: faq/installed why-is-python-installed-on-my-computer-faq16268539
Ref: 4f3016268539
Node: 什麼是 Python？<2>16268815
Ref: faq/installed what-is-python16268996
Ref: 4f3116268996
Ref: 什麼是 Python？<2>-Footnote-116269500
Node: 為什麼 Python 被安裝在我的機器上?16269552
Ref: faq/installed why-is-python-installed-on-my-machine16269777
Ref: 4f3216269777
Node: 我能夠自行刪除 Python 嗎？16270762
Ref: faq/installed can-i-delete-python16270956
Ref: 4f3316270956
Node: 已棄用項目16271742
Ref: deprecations/index doc16271843
Ref: 4f3416271843
Ref: deprecations/index deprecations16271843
Ref: 4f3516271843
Node: Python 3 14 中待移除的項目<3>16272213
Ref: deprecations/index pending-removal-in-python-3-1416272346
Ref: 4f3616272346
Ref: Python 3 14 中待移除的項目<3>-Footnote-116277526
Ref: Python 3 14 中待移除的項目<3>-Footnote-216277581
Ref: Python 3 14 中待移除的項目<3>-Footnote-316277636
Ref: Python 3 14 中待移除的項目<3>-Footnote-416277691
Ref: Python 3 14 中待移除的項目<3>-Footnote-516277746
Ref: Python 3 14 中待移除的項目<3>-Footnote-616277802
Ref: Python 3 14 中待移除的項目<3>-Footnote-716277857
Ref: Python 3 14 中待移除的項目<3>-Footnote-816277912
Ref: Python 3 14 中待移除的項目<3>-Footnote-916277967
Ref: Python 3 14 中待移除的項目<3>-Footnote-1016278022
Ref: Python 3 14 中待移除的項目<3>-Footnote-1116278079
Ref: Python 3 14 中待移除的項目<3>-Footnote-1216278135
Ref: Python 3 14 中待移除的項目<3>-Footnote-1316278191
Ref: Python 3 14 中待移除的項目<3>-Footnote-1416278234
Ref: Python 3 14 中待移除的項目<3>-Footnote-1516278291
Node: Python 3 15 中待移除的項目<3>16278347
Ref: deprecations/index pending-removal-in-python-3-1516278525
Ref: 4f3716278525
Ref: Python 3 15 中待移除的項目<3>-Footnote-116281690
Ref: Python 3 15 中待移除的項目<3>-Footnote-216281745
Ref: Python 3 15 中待移除的項目<3>-Footnote-316281801
Ref: Python 3 15 中待移除的項目<3>-Footnote-416281857
Ref: Python 3 15 中待移除的項目<3>-Footnote-516281913
Node: Python 3 16 中待移除的項目<2>16281969
Ref: deprecations/index pending-removal-in-python-3-1616282147
Ref: 4f3816282147
Ref: Python 3 16 中待移除的項目<2>-Footnote-116282633
Node: 未來版本中的待移除項目<3>16282689
Ref: deprecations/index pending-removal-in-future-versions16282852
Ref: 4f3916282852
Ref: 未來版本中的待移除項目<3>-Footnote-116289524
Ref: 未來版本中的待移除項目<3>-Footnote-216289579
Ref: 未來版本中的待移除項目<3>-Footnote-316289634
Ref: 未來版本中的待移除項目<3>-Footnote-416289690
Ref: 未來版本中的待移除項目<3>-Footnote-516289746
Ref: 未來版本中的待移除項目<3>-Footnote-616289801
Node: C API 的棄用項目16289856
Ref: deprecations/index c-api-deprecations16289974
Ref: 4f3a16289974
Node: Python 3 14 中待移除的項目<4>16290259
Ref: deprecations/index id116290398
Ref: 4f3b16290398
Ref: Python 3 14 中待移除的項目<4>-Footnote-116293626
Ref: Python 3 14 中待移除的項目<4>-Footnote-216293668
Ref: Python 3 14 中待移除的項目<4>-Footnote-316293724
Node: Python 3 15 中待移除的項目<4>16293779
Ref: deprecations/index id216293963
Ref: 4f3c16293963
Node: 未來版本中的待移除項目<4>16295245
Ref: deprecations/index id316295384
Ref: 4f3d16295384
Node: 術語表16297619
Ref: glossary doc16297725
Ref: 4f3e16297725
Ref: glossary glossary16297725
Ref: 1ae316297725
Ref: glossary id116297725
Ref: 4f3f16297725
Ref: glossary term-016297749
Ref: 15016297749
Ref: glossary term-16297923
Ref: 15116297923
Ref: glossary term-abstract-base-class16298324
Ref: 114e16298324
Ref: glossary term-annotation16299254
Ref: 3fe16299254
Ref: glossary term-argument16299929
Ref: 3ef16299929
Ref: glossary term-asynchronous-context-manager16301338
Ref: 57916301338
Ref: glossary term-asynchronous-generator16301628
Ref: 1f1416301628
Ref: glossary term-asynchronous-generator-iterator16302451
Ref: 419116302451
Ref: glossary term-asynchronous-iterable16303288
Ref: d1e16303288
Ref: glossary term-asynchronous-iterator16303576
Ref: 19116303576
Ref: glossary term-attribute16304020
Ref: 237916304020
Ref: glossary term-awaitable16304612
Ref: 19316304612
Ref: glossary term-BDFL16304869
Ref: 4f4216304869
Ref: glossary term-binary-file16304997
Ref: 1b8b16304997
Ref: glossary term-borrowed-reference16305579
Ref: 2ef16305579
Ref: glossary term-bytes-like-object16306357
Ref: cd416306357
Ref: glossary term-bytecode16307359
Ref: 16d16307359
Ref: glossary term-callable16308173
Ref: 27d416308173
Ref: glossary term-callback16308586
Ref: 27f716308586
Ref: glossary term-class16308725
Ref: 183416308725
Ref: glossary term-class-variable16308915
Ref: 4f4316308915
Ref: glossary term-complex-number16309085
Ref: 4f4416309085
Ref: glossary term-context-manager16309826
Ref: 57616309826
Ref: glossary term-context-variable16310075
Ref: 4f4516310075
Ref: glossary term-contiguous16310583
Ref: 210316310583
Ref: glossary term-coroutine16311192
Ref: 43816311192
Ref: glossary term-coroutine-function16311534
Ref: d1d16311534
Ref: glossary term-CPython16311868
Ref: 69916311868
Ref: glossary term-decorator16312118
Ref: 6d516312118
Ref: glossary term-descriptor16312816
Ref: 1e4716312816
Ref: glossary term-dictionary16313686
Ref: 4f4616313686
Ref: glossary term-dictionary-comprehension16313938
Ref: 4f4716313938
Ref: glossary term-dictionary-view16314329
Ref: 23f616314329
Ref: glossary term-docstring16314769
Ref: 1ffd16314769
Ref: glossary term-duck-typing16315175
Ref: 4f4016315175
Ref: glossary term-EAFP16315994
Ref: 2a6616315994
Ref: glossary term-expression16316455
Ref: 1e5c16316455
Ref: glossary term-extension-module16316972
Ref: 438e16316972
Ref: glossary term-f-string16317134
Ref: 3dc16317134
Ref: glossary term-file-object16317335
Ref: 115b16317335
Ref: glossary term-file-like-object16318147
Ref: 246a16318147
Ref: glossary term-filesystem-encoding-and-error-handler16318250
Ref: 4e016318250
Ref: glossary term-finder16319221
Ref: 1eca16319221
Ref: glossary term-floor-division16319695
Ref: 8e816319695
Ref: glossary term-free-threading16320117
Ref: 42d116320117
Ref: glossary term-function16320412
Ref: 1f2f16320412
Ref: glossary term-function-annotation16320752
Ref: 1b3b16320752
Ref: glossary term-__future__16321414
Ref: d5316321414
Ref: glossary term-garbage-collection16322064
Ref: 181c16322064
Ref: glossary term-generator16322454
Ref: 100416322454
Ref: glossary term-generator-iterator16323036
Ref: b8516323036
Ref: glossary term-generator-expression16323457
Ref: 4f4916323457
Ref: glossary term-generic-function16323886
Ref: 99516323886
Ref: glossary term-generic-type16324275
Ref: 3df16324275
Ref: glossary term-GIL16324688
Ref: 13e16324688
Ref: glossary term-global-interpreter-lock16324772
Ref: 12e16324772
Ref: glossary term-hash-based-pyc16326089
Ref: 4f4a16326089
Ref: glossary term-hashable16326335
Ref: 5b516326335
Ref: glossary term-IDLE16327447
Ref: 4f4b16327447
Ref: glossary term-immortal16327683
Ref: 419016327683
Ref: glossary term-immutable16328034
Ref: 1b0216328034
Ref: glossary term-import-path16328410
Ref: 1ecc16328410
Ref: glossary term-importing16328835
Ref: 1ebe16328835
Ref: glossary term-importer16328995
Ref: 1ecb16328995
Ref: glossary term-interactive16329172
Ref: 14d16329172
Ref: glossary term-interpreted16329672
Ref: 4f4c16329672
Ref: glossary term-interpreter-shutdown16330160
Ref: 13316330160
Ref: glossary term-iterable16330894
Ref: 11bf16330894
Ref: glossary term-iterator16332195
Ref: 19216332195
Ref: glossary term-key-function16333708
Ref: dab16333708
Ref: glossary term-keyword-argument16334920
Ref: cb916334920
Ref: glossary term-lambda16335011
Ref: 261616335011
Ref: glossary term-LBYL16335244
Ref: 4f4816335244
Ref: glossary term-list16335947
Ref: 4f4d16335947
Ref: glossary term-list-comprehension16336224
Ref: 67216336224
Ref: glossary term-loader16336704
Ref: 15a816336704
Ref: glossary term-locale-encoding16337072
Ref: 22716337072
Ref: glossary term-magic-method16337576
Ref: 3f1016337576
Ref: glossary term-mapping16337690
Ref: 115416337690
Ref: glossary term-meta-path-finder16338122
Ref: 101116338122
Ref: glossary term-metaclass16338481
Ref: 1e5d16338481
Ref: glossary term-method16339249
Ref: 4f4116339249
Ref: glossary term-method-resolution-order16339628
Ref: 205c16339628
Ref: glossary term-module16339929
Ref: 155516339929
Ref: glossary term-module-spec16340239
Ref: 419f16340239
Ref: glossary term-MRO16340425
Ref: 343416340425
Ref: glossary term-mutable16340510
Ref: 1b0716340510
Ref: glossary term-named-tuple16340686
Ref: 5f416340686
Ref: glossary term-namespace16341978
Ref: 1b5b16341978
Ref: glossary term-namespace-package16342718
Ref: 1b6c16342718
Ref: glossary term-nested-scope16343144
Ref: 204116343144
Ref: glossary term-new-style-class16343679
Ref: 276d16343679
Ref: glossary term-object16344102
Ref: 4f4e16344102
Ref: glossary term-optimized-scope16344324
Ref: 16116344324
Ref: glossary term-package16344855
Ref: 1ec116344855
Ref: glossary term-parameter16345238
Ref: 1dee16345238
Ref: glossary positional-only-parameter16345826
Ref: a2816345826
Ref: glossary keyword-only-parameter16346186
Ref: 28516346186
Ref: glossary term-path-entry16347610
Ref: 1edf16347610
Ref: glossary term-path-entry-finder16347839
Ref: 101216347839
Ref: glossary term-path-entry-hook16348236
Ref: 1ee116348236
Ref: glossary term-path-based-finder16348529
Ref: 1ecf16348529
Ref: glossary term-path-like-object16348718
Ref: ac216348718
Ref: glossary term-PEP16349327
Ref: 4f4f16349327
Ref: glossary term-portion16349938
Ref: 1ec516349938
Ref: glossary term-positional-argument16350167
Ref: cba16350167
Ref: glossary term-provisional-API16350258
Ref: aa616350258
Ref: glossary term-provisional-package16351183
Ref: fe416351183
Ref: glossary term-Python-300016351285
Ref: 4f5016351285
Ref: glossary term-Pythonic16351452
Ref: 4f5116351452
Ref: glossary term-qualified-name16352133
Ref: 184316352133
Ref: glossary term-reference-count16353009
Ref: 46fe16353009
Ref: glossary term-regular-package16353585
Ref: 1ec316353585
Ref: glossary term-REPL16353815
Ref: 14e16353815
Ref: glossary term-__slots__16353943
Ref: 58316353943
Ref: glossary term-sequence16354303
Ref: 49916354303
Ref: glossary term-set-comprehension16355465
Ref: 4f5216355465
Ref: glossary term-single-dispatch16355832
Ref: 99616355832
Ref: glossary term-slice16356007
Ref: 205916356007
Ref: glossary term-soft-deprecated16356391
Ref: 1ee16356391
Ref: glossary term-special-method16356981
Ref: 17ae16356981
Ref: glossary term-statement16357271
Ref: 265e16357271
Ref: glossary term-static-type-checker16357583
Ref: 25216357583
Ref: glossary term-strong-reference16357844
Ref: 2ee16357844
Ref: glossary term-text-encoding16358450
Ref: 205416358450
Ref: glossary term-text-file16358983
Ref: 1b8a16358983
Ref: glossary term-triple-quoted-string16359669
Ref: 4f5316359669
Ref: glossary term-type16360167
Ref: 183516360167
Ref: glossary term-type-alias16360418
Ref: 3e016360418
Ref: glossary term-type-hint16361032
Ref: 1e5816361032
Ref: glossary term-universal-newlines16361687
Ref: ce116361687
Ref: glossary term-variable-annotation16362059
Ref: cfc16362059
Ref: glossary term-virtual-environment16362808
Ref: 1c0416362808
Ref: glossary term-virtual-machine16363140
Ref: 333416363140
Ref: glossary term-Zen-of-Python16363349
Ref: 4f5416363349
Ref: 術語表-Footnote-116363611
Ref: 術語表-Footnote-216363653
Ref: 術語表-Footnote-316363695
Ref: 術語表-Footnote-416363737
Ref: 術語表-Footnote-516363779
Ref: 術語表-Footnote-616363821
Ref: 術語表-Footnote-716363863
Ref: 術語表-Footnote-816363905
Ref: 術語表-Footnote-916363947
Ref: 術語表-Footnote-1016363989
Ref: 術語表-Footnote-1116364028
Ref: 術語表-Footnote-1216364071
Ref: 術語表-Footnote-1316364114
Ref: 術語表-Footnote-1416364157
Ref: 術語表-Footnote-1516364189
Ref: 術語表-Footnote-1616364232
Ref: 術語表-Footnote-1716364275
Ref: 術語表-Footnote-1816364318
Ref: 術語表-Footnote-1916364361
Ref: 術語表-Footnote-2016364404
Ref: 術語表-Footnote-2116364447
Ref: 術語表-Footnote-2216364490
Ref: 術語表-Footnote-2316364533
Ref: 術語表-Footnote-2416364576
Ref: 術語表-Footnote-2516364619
Ref: 術語表-Footnote-2616364662
Ref: 術語表-Footnote-2716364705
Ref: 術語表-Footnote-2816364748
Ref: 術語表-Footnote-2916364791
Ref: 術語表-Footnote-3016364834
Ref: 術語表-Footnote-3116364877
Ref: 術語表-Footnote-3216364920
Ref: 術語表-Footnote-3316364963
Ref: 術語表-Footnote-3416365023
Ref: 術語表-Footnote-3516365066
Ref: 術語表-Footnote-3616365109
Ref: 術語表-Footnote-3716365152
Ref: 術語表-Footnote-3816365195
Ref: 術語表-Footnote-3916365238
Node: 關於這些說明文件16365281
Ref: about doc16365388
Ref: 4f5516365388
Ref: about about-these-documents16365388
Ref: 4f5616365388
Ref: 關於這些說明文件-Footnote-116366240
Ref: 關於這些說明文件-Footnote-216366276
Ref: 關於這些說明文件-Footnote-316366325
Node: Python 文件的貢獻者們16366366
Ref: about contributors-to-the-python-documentation16366455
Ref: 4f5716366455
Ref: Python 文件的貢獻者們-Footnote-116366857
Node: 處理錯誤 Bug16366919
Ref: bugs doc16367029
Ref: 4f5816367029
Ref: bugs dealing-with-bugs16367029
Ref: 4f5916367029
Ref: bugs reporting-bugs16367029
Ref: 474e16367029
Node: 說明文件的錯誤16367528
Ref: bugs documentation-bugs16367643
Ref: 4f5b16367643
Ref: 說明文件的錯誤-Footnote-116369084
Ref: 說明文件的錯誤-Footnote-216369138
Ref: 說明文件的錯誤-Footnote-316369190
Ref: 說明文件的錯誤-Footnote-416369276
Ref: 說明文件的錯誤-Footnote-516369321
Ref: 說明文件的錯誤-Footnote-616369397
Node: 使用 Python 問題追蹤系統16369460
Ref: bugs using-the-python-issue-tracker16369612
Ref: 4f5c16369612
Ref: bugs using-the-tracker16369612
Ref: 23316369612
Ref: 使用 Python 問題追蹤系統-Footnote-116371791
Ref: 使用 Python 問題追蹤系統-Footnote-216371854
Node: 開始讓自己貢獻 Python16371920
Ref: bugs contributing-to-python16372042
Ref: 4f5a16372042
Ref: bugs getting-started-contributing-to-python-yourself16372042
Ref: 4f5d16372042
Ref: 開始讓自己貢獻 Python-Footnote-116372518
Ref: 開始讓自己貢獻 Python-Footnote-216372555
Node: 版權宣告16372631
Ref: copyright doc16372732
Ref: 4f5e16372732
Ref: copyright copyright16372732
Ref: 4f5f16372732
Node: 沿革與授權16373236
Ref: license doc16373340
Ref: 4f6116373340
Ref: license history-and-license16373340
Ref: 4f6016373340
Ref: license id116373340
Ref: 4f6216373340
Node: 軟體沿革16373503
Ref: license history-of-the-software16373635
Ref: 4f6316373635
Node: 關於存取或以其他方式使用 Python 的合約條款16378095
Ref: license terms-and-conditions-for-accessing-or-otherwise-using-python16378269
Ref: 4f6416378269
Node: 用於 PYTHON 3 13 0rc2 的 PSF 授權合約16379415
Ref: license psf-license16379609
Ref: 4f6516379609
Ref: license psf-license-agreement-for-python-release16379609
Ref: 4f6816379609
Node: 用於 PYTHON 2 0 的 BEOPEN COM 授權合約16382323
Ref: license beopen-com-license-agreement-for-python-2-016382567
Ref: 4f6916382567
Node: 用於 PYTHON 1 6 1 的 CNRI 授權合約16385260
Ref: license cnri-license-agreement-for-python-1-6-116385508
Ref: 4f6a16385508
Node: 用於 PYTHON 0 9 0 至 1 2 的 CWI 授權合約16389683
Ref: license cwi-license-agreement-for-python-0-9-0-through-1-216389960
Ref: 4f6b16389960
Node: 用於 PYTHON 3 13 0rc2 說明文件內程式碼的 ZERO-CLAUSE BSD 授權16391218
Ref: license bsd016391445
Ref: 4f6616391445
Ref: license zero-clause-bsd-license-for-code-in-the-python-release-documentation16391445
Ref: 4f6c16391445
Node: 被收錄軟體的授權與致謝16392250
Ref: license licenses-and-acknowledgements-for-incorporated-software16392403
Ref: 4f6d16392403
Ref: license otherlicenses16392403
Ref: 4f6716392403
Node: Mersenne Twister16393066
Ref: license mersenne-twister16393171
Ref: 4f6e16393171
Node: Sockets<2>16395473
Ref: license sockets16395610
Ref: 4f6f16395610
Node: 非同步 socket 服務16397442
Ref: license asynchronous-socket-services16397576
Ref: 4f7016397576
Node: Cookie 管理16398785
Ref: license cookie-management16398921
Ref: 4f7116398921
Node: 執行追蹤16400114
Ref: license execution-tracing16400255
Ref: 4f7216400255
Node: UUencode 與 UUdecode 函式16401486
Ref: license uuencode-and-uudecode-functions16401636
Ref: 4f7316401636
Node: XML 遠端程序呼叫16403202
Ref: license xml-remote-procedure-calls16403350
Ref: 4f7416403350
Node: test_epoll16404847
Ref: license test-epoll16404980
Ref: 4f7516404980
Node: Select kqueue16406231
Ref: license select-kqueue16406351
Ref: 4f7616406351
Node: SipHash2416407886
Ref: license siphash2416408011
Ref: 4f7716408011
Node: strtod 與 dtoa16409178
Ref: license strtod-and-dtoa16409300
Ref: 4f7816409300
Node: OpenSSL<2>16410685
Ref: license openssl16410803
Ref: 4f7916410803
Node: expat16421721
Ref: license expat16421830
Ref: 4f7a16421830
Node: libffi16423246
Ref: license libffi16423352
Ref: 4f7b16423352
Node: zlib<3>16424738
Ref: license zlib16424846
Ref: 4f7c16424846
Node: cfuhash16426086
Ref: license cfuhash16426196
Ref: 4f7d16426196
Node: libmpdec16428006
Ref: license libmpdec16428130
Ref: 4f7e16428130
Node: W3C C14N 測試套件16429747
Ref: license w3c-c14n-test-suite16429872
Ref: 4f7f16429872
Node: mimalloc16431759
Ref: license mimalloc16431887
Ref: 4f8016431887
Ref: license mimalloc-license16431887
Ref: 34e16431887
Node: asyncio<12>16433100
Ref: license asyncio16433237
Ref: 4f8116433237
Ref: asyncio<12>-Footnote-116434586
Node: Global Unbounded Sequences GUS16434644
Ref: license global-unbounded-sequences-gus16434764
Ref: 4f8216434764
Ref: Global Unbounded Sequences GUS-Footnote-116436442
Node: Python 模組索引16436520
Node: 索引16454882
Ref: library/asyncio audit_event_cpython_run_stdin_018410943
Ref: 3ff318410944
Ref: using/cmdline audit_event_cpython_run_stdin_118410946
Ref: 3ff918410948
Ref: library/time audit_event_time_sleep_018410950
Ref: using/cmdline audit_event_cpython_run_stdin_018410952
Ref: 400018410954
Ref: 3ff718410956
Ref: library/_thread start_new_thread18410958
Ref: using/cmdline audit_event_cpython_run_file_018410960
Ref: 3ff818410962
Ref: 3ff618410964

End Tag Table


Local Variables:
coding: utf-8
End:
